diff --git a/marked/F/T-REC-F.1-199803-I_PDF-E/raw.md b/marked/F/T-REC-F.1-199803-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..dbc0d51f207fe4e168e400342bf1edcf7d536516
--- /dev/null
+++ b/marked/F/T-REC-F.1-199803-I_PDF-E/raw.md
@@ -0,0 +1,1981 @@
+
+
+![ITU logo: A globe with the letters ITU and a lightning bolt.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+ITU logo: A globe with the letters ITU and a lightning bolt.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.1**
+
+(03/98)
+
+# **SERIES F: NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+Telegraph service – Operating methods for the  
+international public telegram service
+
+## --- **Operational provisions for the international public telegram service**
+
+ITU-T Recommendation F.1
+
+(Previously CCITT Recommendation)
+
+---
+
+## ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                        |                 |
+|------------------------------------------------------------------------|-----------------|
+| TELEGRAPH SERVICE                                                      | F.1–F.109       |
+| <b>Operating methods for the international public telegram service</b> | <b>F.1–F.19</b> |
+| The gentex network                                                     | F.20–F.29       |
+| Message switching                                                      | F.30–F.39       |
+| The international telemessage service                                  | F.40–F.58       |
+| The international telex service                                        | F.59–F.89       |
+| Statistics and publications on international telegraph services        | F.90–F.99       |
+| Scheduled and leased communication services                            | F.100–F.104     |
+| Phototelegraph service                                                 | F.105–F.109     |
+| MOBILE SERVICE                                                         | F.110–F.159     |
+| Mobile services and multdestination satellite services                 | F.110–F.159     |
+| TELEMATIC SERVICES                                                     | F.160–F.399     |
+| Public facsimile service                                               | F.160–F.199     |
+| Teletex service                                                        | F.200–F.299     |
+| Videotex service                                                       | F.300–F.349     |
+| General provisions for telematic services                              | F.350–F.399     |
+| MESSAGE HANDLING SERVICES                                              | F.400–F.499     |
+| DIRECTORY SERVICES                                                     | F.500–F.549     |
+| DOCUMENT COMMUNICATION                                                 | F.550–F.599     |
+| Document communication                                                 | F.550–F.579     |
+| Programming communication interfaces                                   | F.580–F.599     |
+| DATA TRANSMISSION SERVICES                                             | F.600–F.699     |
+| AUDIOVISUAL SERVICES                                                   | F.700–F.799     |
+| ISDN SERVICES                                                          | F.800–F.849     |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                                   | F.850–F.899     |
+| HUMAN FACTORS                                                          | F.900–F.999     |
+
+*For further details, please refer to ITU-T List of Recommendations.*
+
+## **ITU-T RECOMMENDATION F.1**
+
+## **OPERATIONAL PROVISIONS FOR THE INTERNATIONAL PUBLIC TELEGRAM SERVICE**
+
+###### **Source**
+
+ITU-T Recommendation F.1 was revised by ITU-T Study Group 2 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 9th of March 1998.
+
+### FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the 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.
+
+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
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The 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, the 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 1998
+
+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 the ITU.
+
+### CONTENTS
+
+###### Page
+
+|                                                                                        |    |
+|----------------------------------------------------------------------------------------|----|
+| DIVISION A – GENERAL PROVISIONS APPLYING TO ALL METHODS OF WORKING.....                | 2  |
+| I. Hours of service of offices .....                                                   | 2  |
+| 1 Duration and closing of service – Legal time.....                                    | 2  |
+| II. Classification of correspondence in the international public telegram service..... | 2  |
+| 1 Telegrams and special services .....                                                 | 2  |
+| 1.1 Obligatory telegrams .....                                                         | 2  |
+| 1.2 Optional telegrams and special services.....                                       | 3  |
+| III. Preparation and handing in of telegrams.....                                      | 4  |
+| 1 General .....                                                                        | 4  |
+| 2 Characters that may be used for the preparation of telegrams.....                    | 4  |
+| 3 Order of arrangement of the various parts of a telegram.....                         | 5  |
+| 4 Heading .....                                                                        | 5  |
+| 5 The address part.....                                                                | 6  |
+| 5.1 The service indications.....                                                       | 6  |
+| 5.2 General provisions for the address .....                                           | 6  |
+| 5.3 Full postal address.....                                                           | 7  |
+| 5.4 Registered address.....                                                            | 8  |
+| 5.5 Telephonic address.....                                                            | 8  |
+| 5.6 Telex and facsimile addresses .....                                                | 9  |
+| 5.6.1 Telex address.....                                                               | 9  |
+| 5.6.2 Facsimile address .....                                                          | 9  |
+| 5.7 Poste restante or télégraphe restant address .....                                 | 9  |
+| 5.8 Post office box address.....                                                       | 9  |
+| 6 The text part .....                                                                  | 10 |
+| 6.1 The text.....                                                                      | 10 |
+| 6.2 The signature .....                                                                | 10 |
+| 6.3 Long telegrams .....                                                               | 10 |
+| 7 Cancellation of telegrams at the request of the sender .....                         | 11 |
+| IV. Counting of words .....                                                            | 11 |
+| 1 General provisions.....                                                              | 11 |
+
+|       | <b>Page</b>                                                                                                |
+|-------|------------------------------------------------------------------------------------------------------------|
+| 2     | Counting the number of chargeable words..... 12                                                            |
+| 3     | Indication of the number of words in the preamble line ..... 12                                            |
+| 4     | Irregularities in the counting of words ..... 12                                                           |
+| V.    | Routing and retransmission of telegrams ..... 12                                                           |
+| VI.   | Transmission of telegrams..... 13                                                                          |
+| 1     | Order of transmission of telegrams ..... 13                                                                |
+| 2     | Order of transmission of the various parts of a telegram ..... 13                                          |
+| 3     | Transmission of the heading..... 13                                                                        |
+| 4     | Transmission of the other parts of a telegram ..... 14                                                     |
+| 5     | Reception..... 14                                                                                          |
+| 6     | Errors and interruptions..... 14                                                                           |
+| VII.  | Interruption of telegram communications ..... 15                                                           |
+| 1     | Diversion of telegrams ..... 15                                                                            |
+| VIII. | Delivery at destination..... 15                                                                            |
+| 1     | General provisions..... 15                                                                                 |
+| 2     | Methods of delivery..... 16                                                                                |
+| 3     | Non-delivery and delayed delivery..... 17                                                                  |
+| IX.   | Obligatory telegrams ..... 18                                                                              |
+| 1     | Telegrams relating to the safety of life (SVH) ..... 18                                                    |
+| 2     | Government telegrams and telegrams relative to the application of the United Nations Charter..... 18       |
+| 3     | Telegrams concerning persons protected in time of war by the Geneva Conventions of 12 August 1949 ..... 20 |
+| 4     | Ordinary private telegrams..... 20                                                                         |
+| 5     | Telegraph service correspondence..... 21                                                                   |
+| 6     | Meteorological telegrams ..... 21                                                                          |
+| X.    | Optional telegrams ..... 21                                                                                |
+| 1     | Postal financial telegrams..... 21                                                                         |
+| 2     | Letter telegrams..... 21                                                                                   |
+| 3     | Privilege telegrams ..... 22                                                                               |
+
+|                                                                                               | <b>Page</b> |
+|-----------------------------------------------------------------------------------------------|-------------|
+| XI. Special services .....                                                                    | 22          |
+| 1 General provisions.....                                                                     | 22          |
+| 2 Urgent transmission and delivery.....                                                       | 22          |
+| 3 De luxe form.....                                                                           | 23          |
+| XII. Stoppage of telegrams .....                                                              | 23          |
+| 1 Transmission of certain telegrams as of right – Notification of stoppage.....               | 23          |
+| XIII. Archives.....                                                                           | 23          |
+| 1 Archives.....                                                                               | 23          |
+| 2 Inspection of original forms of telegrams – Supplying copies of telegrams.....              | 24          |
+| <b>DIVISION B – OPERATIONAL PROVISIONS APPLYING TO MORSE AND<br/>SOUNDER WORKING.....</b>     | <b>25</b>   |
+| I. Morse code .....                                                                           | 25          |
+| 1 Morse code signals .....                                                                    | 25          |
+| 2 Spacing and length of the signals.....                                                      | 26          |
+| 3 Transmission of signs for which there is no corresponding signal<br>in the Morse code ..... | 26          |
+| 3.2 Multiplication sign .....                                                                 | 26          |
+| 3.3 Percentage or per thousand sign.....                                                      | 26          |
+| 3.4 Inverted commas (quotation marks).....                                                    | 26          |
+| 3.5 Minute and second signs .....                                                             | 27          |
+| 4 Transmission of groups of figures and letters, of ordinal numbers or of fractions ....      | 27          |
+| II. General transmission rules .....                                                          | 27          |
+| III. Transmission of telegrams with identical text.....                                       | 28          |
+| 1 Identical texts .....                                                                       | 28          |
+| IV. Transmission irregularities – Service notes.....                                          | 28          |
+| V. Checking the number of words transmitted – Acknowledgement of receipt.....                 | 29          |
+| 1 Checking the number of words transmitted .....                                              | 29          |
+| 2 Acknowledgement of receipt.....                                                             | 29          |
+| VI. Transmission procedures.....                                                              | 29          |
+
+|                                                                                                                   |    |
+|-------------------------------------------------------------------------------------------------------------------|----|
+| DIVISION C – OPERATIONAL PROVISIONS APPLYING TO PRINTING TELEGRAPH SYSTEMS.....                                   | 31 |
+| I. Transmission signals .....                                                                                     | 31 |
+| 1 Transmission signals of International Telegraph Alphabet No. 2.....                                             | 31 |
+| 2 Transmission of signs for which there is no corresponding signal in the telegraph alphabet .....                | 32 |
+| 3 Transmission of ordinal numbers, groups of figures and letters or of numbers that include fractions .....       | 32 |
+| II. General provisions for transmission of telegrams.....                                                         | 33 |
+| 1 Calling .....                                                                                                   | 33 |
+| 2 Transmission with running series of numbers.....                                                                | 33 |
+| III. General provisions for reception .....                                                                       | 33 |
+| IV. Special provisions for point-to-point operations .....                                                        | 34 |
+| 1 Transmission of telegrams to tape-printing systems .....                                                        | 34 |
+| 2 Transmission of telegrams to page-printing systems .....                                                        | 34 |
+| 3 Reception.....                                                                                                  | 36 |
+| V. Special provisions for gentex operations.....                                                                  | 37 |
+| 1 General provisions.....                                                                                         | 37 |
+| 2 Answer-back codes.....                                                                                          | 37 |
+| 3 Responsibility of transmitting or receiving stations.....                                                       | 37 |
+| 4 Procedures before transmission of a telegram.....                                                               | 37 |
+| 5 Transmission of telegrams.....                                                                                  | 38 |
+| 6 Reception of telegrams.....                                                                                     | 39 |
+| 7 Abnormal conditions before transmission.....                                                                    | 39 |
+| 8 Abnormal conditions during transmission .....                                                                   | 39 |
+| 9 Traffic between gentex offices equipped with page-printing teleprinters.....                                    | 40 |
+| 10 Interworking between tape-printing and page-printing teleprinters.....                                         | 41 |
+| 11 Special transmission procedures for use with format converters and/or automatic error correction devices ..... | 41 |
+| 12 Service advices (A) and use of codes .....                                                                     | 41 |
+| VI. Interworking between the telegram retransmission system and the gentex network .                              | 44 |
+
+|                                                                                                             | <b>Page</b> |
+|-------------------------------------------------------------------------------------------------------------|-------------|
+| DIVISION D – TELEGRAPH SERVICE CORRESPONDENCE.....                                                          | 47          |
+| I.    Telegraph service correspondence.....                                                                 | 47          |
+| 1    Definitions.....                                                                                       | 47          |
+| II.   Service telegrams and service advices .....                                                           | 47          |
+| 1    General provisions.....                                                                                | 47          |
+| 2    Service telegrams .....                                                                                | 48          |
+| 3    Service advices.....                                                                                   | 48          |
+| 3.1    General provisions.....                                                                              | 48          |
+| 3.2    Procedure.....                                                                                       | 48          |
+| 3.2.1    End-to-end servicing .....                                                                         | 48          |
+| 3.2.2    Follow-on service advices.....                                                                     | 48          |
+| 3.2.3    Return service advices.....                                                                        | 49          |
+| 3.3    Wording.....                                                                                         | 49          |
+| 3.4    Repetition of a telegram .....                                                                       | 49          |
+| III.  Examples of format and wording of service correspondence.....                                         | 50          |
+| DIVISION E – OPERATIONAL PROVISIONS APPLYING TO INTERNATIONAL<br>FACSIMILE TRANSMISSIONS OF TELEGRAMS ..... | 52          |
+| 1    General provisions.....                                                                                | 52          |
+| 2    Preparation of telegrams for transmission.....                                                         | 52          |
+| 3    Routing and retransmission of telegrams .....                                                          | 53          |
+| 4    Delivery at destination.....                                                                           | 53          |
+| 5    Service correspondence.....                                                                            | 53          |
+| 6    Archives.....                                                                                          | 53          |
+
+
+
+## Recommendation F.1
+
+## OPERATIONAL PROVISIONS FOR THE INTERNATIONAL PUBLIC TELEGRAM SERVICE
+
+*(Geneva, 1992; revised in 1998)*
+
+### Introductory notes
+
+1 Telegram examples given in this Recommendation are only intended to illustrate the correct formatting of telegrams. Groups such as gentex answer-back codes, channel indicators, telegram identification groups, destination indicators, origin indicators and postal codes do not necessarily reflect current usage or routing arrangements in the telegraph offices concerned.
+
+2 Letters, figures and signs that are transmitted electrically are shown in bold font:  
+**TLX420216.**
+
+3 The telegram service is part of bureau services as described in Recommendation F.18.
+
+4 The term Recognized Operating Agency (ROA) is defined in the International Telecommunication Constitution (Geneva, 1992). For the purpose of this Recommendation, an ROA is, in effect, any individual, company, corporation or governmental agency that operates an international telecommunication service that carry public correspondence (as defined in the Constitution). Each ROA is authorized by an ITU Member, which imposes certain obligations on the ROA. (For further details, see the Constitution.)
+
+### **DIVISION A**
+
+### **GENERAL PROVISIONS APPLYING TO ALL METHODS OF WORKING**
+
+#### **I. Hours of service of offices**
+
+##### **1 Duration and closing of service – Legal time**
+
+- A1 1.1 Each Administration shall fix the hours during which its offices shall be open for international service.
+- A2 1.2 International communications established between important offices shall, so far as practicable, work without interruption.
+- A3 1.3 In relations between offices that are permanently open, the closing of daily sessions shall take place at a time agreed upon between the offices concerned.
+- A4 1.4 In relations between offices that are not permanently open, a terminal office may not close before having exchanged all outstanding international telegrams with an office that is open later and before having obtained confirmation that all telegrams have been received.
+- A5 1.5 Between two directly communicating offices in different countries, close of work may take place only by agreement between these offices. If these offices have different hours of closing, the office that closes earlier shall request the close of work. If they have the same closing time, the close of work shall be requested by the office of the country, the capital of which has a longitude to the east of the other capital.
+- A6 1.6 Offices shall use the legal time of their country or of their zone.
+
+#### **II. Classification of correspondence in the international public telegram service**
+
+##### **1 Telegrams and special services**
+
+###### **1.1 Obligatory telegrams**
+
+- A7 1.1.1 The following classes of telegrams shall be accepted in the international public telegram service (for the application of service indications, see A39 to A45):
+
+|                                                                                                   | SERVICE INDICATION                 |
+|---------------------------------------------------------------------------------------------------|------------------------------------|
+| Telegrams relating to the safety of life                                                          | <b>SVH</b>                         |
+| Telegrams relative to the application of the United Nations Charter                               | <b>ETATPRIORITE</b>                |
+| Government telegrams                                                                              | <b>ETAT</b> or <b>ETATPRIORITE</b> |
+| Meteorological telegrams                                                                          | <b>OBS</b>                         |
+| Telegrams concerning persons protected in time of war by the Geneva Conventions of 12 August 1949 | <b>RCT</b>                         |
+| Ordinary private telegrams                                                                        |                                    |
+| Service telegrams or advices                                                                      | <b>A</b>                           |
+
+###### 1.2 Optional telegrams and special services
+
+A8 1.2.1 Administrations have the option of admitting the telegrams listed in A10 and telegrams with the special services listed in A11.
+
+A9 1.2.2 However, Administrations that do not admit the telegrams listed in A10 and/or telegrams with the special services listed in A11 in their own services, must let them pass in transit except in case of suspension of service provided for in Article 20 of the Convention (Nairobi, 1982 [1]).
+
+A10 1.2.3 *Optional telegrams*
+
+|                                     | SERVICE INDICATION |
+|-------------------------------------|--------------------|
+| Postal financial services telegrams | <b>POSTFIN</b>     |
+| Letter telegrams                    | <b>LT</b>          |
+| Government letter telegrams         | <b>LTF</b>         |
+| Privilege telegrams                 | <b>CONFERENCE</b>  |
+
+A11 1.2.4 *Special services*
+
+|                                                        |                                       |
+|--------------------------------------------------------|---------------------------------------|
+| Urgent transmission and delivery                       | <b>URGENT</b>                         |
+| De luxe form                                           | <b>LX</b>                             |
+| De luxe form of condolence                             | <b>LXDEUIL</b>                        |
+| Period of retention of radiotelegrams at land stations | <b>Jx</b><br>(x = number of days)     |
+| Telephone delivery                                     | <b>TFx</b><br>(x = telephone number)  |
+| Telex delivery                                         | <b>TLXx</b><br>(x = telex number)     |
+| Facsimile delivery                                     | <b>FAXx</b><br>(x = facsimile number) |
+
+#### III. Preparation and handing in of telegrams
+
+##### 1 General
+
+- A12 1.1 In principle, the text and the signature of a telegram may be written in any language (see A14 and A101).
+- A13 1.2 They may equally be expressed in some other form based on the use of those characters mentioned in A15 to A19, A101 to A103.
+- A14 1.3 Exceptionally, where Members of the ITU find it necessary not to admit private telegrams in secret language, the provisions of Recommendation F.4 shall apply. Government and service telegrams may be expressed in secret language in all relations. The French, English and Spanish languages at least shall also be admitted in all relations as plain language.
+
+##### 2 Characters that may be used for the preparation of telegrams
+
+- A15 2.1 The original telegram must be written in characters that are used in the country of origin and that have an equivalent in the table of telegraph signals given below:
+- A16 2.1.1 Letters: 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
+- A17 2.1.2 Figures: 1 2 3 4 5 6 7 8 9 0
+- A18 2.1.3 Punctuation marks and miscellaneous signs:
+- |                                    |   |
+|------------------------------------|---|
+| Full stop                          | . |
+| Comma                              | , |
+| Colon or division sign             | : |
+| Question mark                      | ? |
+| Apostrophe                         | , |
+| Cross or addition sign             | + |
+| Hyphen or dash or subtraction sign | – |
+| Fraction bar or division sign      | / |
+| Double hyphen                      | = |
+| Left-hand bracket (parenthesis)    | ( |
+| Right-hand bracket (parenthesis)   | ) |
+- A19 2.2 The cross sign (+) used as a sign of addition may be utilized in a group but not as an isolated sign.
+- A20 2.3 Every footnote, insertion, erasure, elimination or correction must be approved by the sender or his representative.
+- A21 2.4 As some expressions such as  $30^a$ ,  $30^{me}$ ,  $1^\circ$ ,  $2^\circ$ ,  $\diamond B$ , cannot be reproduced by all instruments, senders must substitute an equivalent that can be telegraphed; thus, for example, for the expressions quoted above: **30 POWER A** (or **30 A**), **TRENTIEME**, **PRIMO**, **SECUNDO**, **B IN DIAMOND**, etc.
+- A22 2.5 However, if the expressions  $30^a$ ,  $30^b$ , etc., 30 *bis*, 30 *ter*, etc., 30 I, 30 II, etc., 30A, 30B, etc.,  $30^1$ ,  $30^2$ , etc., indicating a house number, appear in the address, the accepting officer shall separate the main number from the number qualifying it, or from the accompanying letters or digits, by a fraction bar. These expressions shall consequently be
+
+transmitted in the following form in the address of a telegram: **30/A, 30/B, etc., 30/BIS, 30/TER, etc., 30/1, 30/2, etc., 30/A, 30/B, etc., 30/1, 30/2, etc.**
+
+##### **3 Order of arrangement of the various parts of a telegram**
+
+- A23 3.1 Every telegram must have a heading, which shall include the information needed for identification and, if necessary, for the routing of the telegram.
+- A24 3.2 The other parts of which a telegram may consist must be arranged as follows:
+- A25 3.2.1 the address (including the service indications, if any);
+- A26 3.2.2 the text (including the signature, if any).
+
+##### **4 Heading**
+
+- A27 4.1 The heading of a telegram consists of the lines listed in A28 to A30:
+- A28 4.2 the *numbering line* containing the information to identify the telegram (for example the originating office number) or telegram identification group and the serial and/or reference numbers used in transmitting the telegram. The numbering of telegrams to be transmitted over international circuits depends on the particular mode of operation employed. See B55 to B66, C21 to C25 and Recommendation F.31 (see 2.1/F.31 to 2.3/F.31 and 5.4/F.31).
+- A29 4.3 the *pilot line* (where this is required) prepared in accordance with Recommendation F.31 (see 2.1/F.31 to 2.3/F.31 and 5.4/F.31).
+- A30 4.4 the *preamble line* which consists of:
+- A31 4.4.1 the official name of the office of origin which shall not be abbreviated. If necessary, the name of the office of origin may be suffixed by particulars intended to distinguish it from other offices of the locality. Such a suffix should be joined to the name of office of origin by a fraction bar;
+
+Examples: **VISEU/VIRIATO  
+BERLIN/19**
+
+- A32 4.4.1.1 when a telegram is:
+  - a) telephoned;
+  - b) sent in by telex;
+  - c) deleted;
+  - d) sent in by facsimile.
+
+to a telegraph office (ROSTOCK, for example) by a customer located somewhere (WISMAR, for example), the office of origin may be transmitted as follows:
+
+- a) **ROSTOCK/TF**
+  - b) **ROSTOCK/TLX**
+  - c) **deleted**
+  - d) **ROSTOCK/FAX**
+- A33 4.4.2 The number of chargeable and actual words (see A115 to A117).
+- A34 4.4.3 The date and time of handing in of the telegram. The date and time shall be shown by two groups of figures, the first indicating the day of the month and the second consisting of a group of four figures (**0001 to 2400**) indicating the hours and minutes (see A6).
+
+- A35 4.4.4 Service instructions, if any.
+- A36 4.4.4.1 A service instruction is an instruction added to a telegram by the office of origin or by another office to give additional information about the telegram.
+- A37 4.4.4.2 Examples of service instructions and the abbreviated form in which they may be indicated are shown in the following list:
+- |                                        |                                  |
+|----------------------------------------|----------------------------------|
+| Correction follows (see A166, A167)    | <b>CTF</b>                       |
+| Telegram sent a second time (see A169) | <b>AMPLIATION</b>                |
+| Division of a telegram (see A111)      | <b>PART/1 x, PART/2 x, . . .</b> |
+- A38 4.4.4.3 These instructions are placed at the end of the preamble line.
+
+##### 5 The address part
+
+###### 5.1 The service indications
+
+- A39 5.1.1 Service indications, if any, shall be shown separately in the first line of the address part. The service indications on a telegram:
+- A40 a) identify it as within a particular class of telegram;
+- A41 b) denote a special service requested by the sender.
+- A42 5.1.2 Service indications may be written by the sender in full or abbreviated form. If necessary, the accepting officer shall substitute the appropriate service indications shown in A7, A10 and A11.
+- A43 5.1.3 The service indications identifying the class of telegram are shown in A7 and A10.
+- A44 5.1.4 If there are several service indications in a telegram, the service indication identifying class shall come first, for example **LT LX**.
+- A45 5.1.5 Exceptionally, the service indication **URGENT**, if present, shall precede the indication of class, for example **URGENT RCT**.
+
+###### 5.2 General provisions for the address
+
+- A46 5.2.1 The address must contain all the particulars necessary to ensure delivery of the telegram to the addressee without inquiries or requests for information. In all cases of insufficient address the telegram shall be accepted only at the risk of the sender, if he insists on sending it, and he has also to bear the consequences.
+- A47 5.2.2 With three exceptions, every address, to be admissible, must contain at least two words, the first designating the addressee and the second the name of the telegraph office of destination. The exceptions are:
+- A48 a) **SVH** telegrams (see A203);
+- A49 b) **POSTFIN** telegrams (see A236 to A240);
+- A50 c) Service advices (see D35).
+- A51 5.2.3 The following categories of address are permitted:
+- A52 a) full postal address;
+- A53 b) registered address;
+- A54 c) telephonic address;
+- A55 d) telex address;
+
+- A56 e) deleted;
+- A57 f) facsimile address;
+- A58 g) *poste restante* or *télégraphe restant* address;
+- A59 h) post office box address.
+- A60 5.2.4 When a telegram is addressed to a person at the address of another, the address must contain, immediately after the name of the actual addressee, the expression *chez*, *care of* or other equivalent expression.
+- A61 5.2.5 When the destination is not served by international communication circuits, A182 shall be observed.
+- A62 5.2.6 The name of the telegraph office of destination should be placed after the words in the address that designate the addressee and where given, his residence. It should be written as the last address line. The List of Telegraph Offices can be used to support the spelling of the name of offices.
+- A63 5.2.7 If necessary, this name may be suffixed by particulars intended to distinguish it from other offices of the locality. Such a suffix should be joined to the name of the office of destination by a fraction bar:
+- Example: **BORDEAUX/SAINTPROJET**
+- A64 5.2.8 The name of the place given as the destination, or land station chosen for the transmission of a radiotelegram must be followed either by the name of the state, province or country or by other particulars that are considered adequate for the forwarding of the telegram. The same course shall be followed when there are several offices of the same name and the sender is not in a position to furnish definite information from which the official designation of the locality can be identified. In either case, the telegram shall be accepted only at the risk of the sender.
+- A65 5.2.9 In radiotelegrams the name of the destination mobile station should be written as it appears in the appropriate ITU List [2], [3], or, if not so listed, the call sign or other particulars should also be given, if necessary.
+- A66 5.2.10 If the address does not conform with A47 to A50, A64 and A65, the telegram shall be refused.
+
+###### 5.3 Full postal address
+
+- A67 5.3.1 The full postal address must, as a general rule, include:
+- A68 a) the designation of the addressee;
+- A69 b) the name of the street, boulevard, avenue, etc. of his abode together, if available, with the number;
+- A70 c) the name of the office of destination, followed by a fraction bar and the name of country.
+- A71 5.3.2 The name of the telegraph office of destination should be supplemented by the postal code whenever possible placed according to the requirements of the country of destination. The postal code should be enclosed in brackets by the accepting office.
+- A72 5.3.3 In the absence of the particulars mentioned in A69, the address must state, so far as possible, the occupation of the addressee or give any other useful information.
+- A73 5.3.4 Even for small localities, the designation of the addressee must be supplemented, so far as possible, by further particulars for the guidance of the delivery office.
+
+A74 5.3.5 Surnames, given (christian) names, names of firms and particulars of abode shall be accepted as the sender writes them. Any other particulars in the address should be written in the language or languages of the destination country.
+
+The official name of the office of destination shall not be abbreviated.
+
+A75 5.3.6 The address may thus appear as follows:
+
+**URGENT**
+
+**MRS MARIA JACINTA**
+
+**C/O VITOR E COMPANHIA LIMITADA**
+
+**RUA VASCO DA GAMA 232**
+
+**PORTO COVO**
+
+**(7520) SINES**
+
+A76 5.3.7 In telegrams for China, the Chinese phonetic alphabet, groups of four figures or groups of three roman characters may be used to designate the name and abode of the addressee.
+
+###### **5.4 Registered address**
+
+A77 5.4.1 A registered address is one in which the full address (excluding the office of destination) is replaced by a single simplified indication.
+
+A78 5.4.2 The address may thus appear as follows:
+
+**INOCRAM**
+
+**LISBOA**
+
+A79 5.4.3 Such an address is registered in the destination country and represents the full address of the addressee and, if necessary, instructions for the delivery of his telegrams.
+
+A80 5.4.4 The right to delivery of telegrams so addressed shall be subject to arrangements between the addressee and the telegraph office of destination.
+
+A81 5.4.5 When, exceptionally, the registered address is followed by an additional indication **ATTENTION** or any other equivalent and/or the name of a third person, it should normally only be used to reconstitute the full address of the addressee.
+
+###### **5.5 Telephonic address**
+
+A82 5.5.1 If the sender desires his telegram to be delivered by telephone, the service indication **TFx** (x being the telephone number of the addressee with, if necessary, the name or access number of the network), shall be indicated before the address (the name of the addressee and the office of destination may be sufficient).
+
+A83 5.5.2 The address may thus appear as follows:
+
+**TF873455**
+
+or
+
+**TFDEWILGEN234**
+
+**WILLI SCHUTZ**
+
+**DE VRIES**
+
+**HAMBURG**
+
+**HEERENVEEN**
+
+###### 5.6 Telex and facsimile addresses
+
+###### 5.6.1 Telex address
+
+A84 5.6.1.1 If the sender desires his telegram to be delivered by telex, the service indication **TLXx** (x being the number of the addressee's telex station), shall be indicated before the address (name of the addressee and the office of destination may be sufficient).
+
+A85 5.6.1.2 The address may thus appear as follows:
+
+**TLX200745  
+MARIE DUBOIS  
+PARIS**
+
+A86-A87 Deleted
+
+###### 5.6.2 Facsimile address
+
+A88 5.6.2.1 If the sender desires his telegram to be delivered by facsimile, the service indication **FAXx** (x being the facsimile number of the addressee), shall be indicated before the address (the name of the addressee and the office of destination may be sufficient).
+
+A89 5.6.2.2 The address may thus appear as follows:
+
+|                      |    |                          |
+|----------------------|----|--------------------------|
+| <b>FAX622266</b>     | or | <b>FAXCAVERNAES92143</b> |
+| <b>PIERRE WENGER</b> |    | <b>CARLA SOFIA</b>       |
+| <b>BERNE</b>         |    | <b>VISEU</b>             |
+
+###### 5.7 Poste restante or télégraphe restant address
+
+A90 5.7.1 The address of telegrams intended to be delivered to a *poste restante* or *télégraphe restant* must be composed of:
+
+A91 a) the name of the addressee including, where possible, his given (christian) name or initials;
+
+A92 b) the words *poste restante*, *télégraphe restant* (or the equivalent in a language of the destination country); and
+
+A93 c) the name of the telegraph office of destination.
+
+A94 5.7.2 Administrations who do not admit telegrams with *poste restante* or *télégraphe restant* as part of the address shall inform other Administrations through the medium of the General Secretariat.
+
+A95 5.7.3 Initials alone, figures, given (christian) name only, fictitious names or arbitrary signs of any kind shall not be allowed in the address.
+
+###### 5.8 Post office box address
+
+A96 5.8.1 A post office box address must be composed of:
+
+A97 a) the name of the addressee;
+
+A98 b) the designation *boîte postale* (or its equivalent in a language of the destination country) followed by the box number; and
+
+A99 c) the name of the telegraph office of destination.
+
+A100 5.8.2 The name of the office to which the addressee's post office box belongs should, if necessary, be supplemented by particulars to distinguish it from other local offices.
+
+For example: **DUPONT**
+
+**BOITE POSTALE 275**
+
+**PARIS/24**
+
+##### **6 The text part**
+
+###### **6.1 The text**
+
+A101 6.1.1 Each telegram must contain a text that contains at least one character.
+
+A102 6.1.2 The text of a telegram must be continuous (no blank lines, etc.), using only the characters specified in A15 to A22.
+
+A103 6.1.3 When important figures or words appear in the text, it is desirable for the sender to repeat them (or the critical parts of them) in order to allow the addressee to detect possible errors in transmission. The sender may give the repetition immediately after the relevant group (followed by a space) either in brackets or preceded by the word **REPEAT**. Alternatively, figures may be spelt.
+
+For example: **1500 (1500)**
+
+**1500 REPEAT 1500**
+
+**FIFTEEN HUNDRED (1500)**
+
+**PAY MR. M. KAUFNER (M. KAUFNER)**
+
+**NOT REPEAT NOT**
+
+###### **6.2 The signature**
+
+A104 6.2.1 A signature shall not be compulsory. It may be written by the sender in any form.
+
+###### **6.3 Long telegrams**
+
+A105 6.3.1 For transmission purposes a telegram is normally limited to 400 actual words.
+
+A106 6.3.2 Except in relations where a bilateral agreement to the contrary exists, telegrams handed in with more than 400 actual words shall be divided prior to transmission into separate telegrams each of 400 actual words, plus one telegram for the remainder, unless this remainder is less than 50 words.
+
+A107 6.3.3 This division shall be made by the Administration; it shall not be the sender's responsibility.
+
+A108 6.3.4 When the original telegram has been divided, the resulting telegrams shall:
+
+A109 6.3.4.1 be transmitted in accordance with the relevant procedure outlined in Recommendations F.1 and F.31;
+
+A110 6.3.4.2 bear the same telegram identification group;
+
+A111 6.3.4.3 contain identical preamble lines (i.e. showing the same office of origin, the chargeable/actual words for the complete original telegram, date and time), but with the addition of the service instruction **PART** followed by a fraction bar, the number of the part of the original telegram, a space and the number of actual words in that part (e.g. **PART/1 400, PART/2 400 and PART/3 79**);
+
+example: **ZCZC AZA123 ESI4567**
+
+**NZXX CV AASV 402**
+
+**SYDNEY/TF 489/486 3 1530 PART/1 400**
+
+**ZCZC AZA125 ESI4567**
+
+**NZXX CV AASV 087**
+
+**SYDNEY/TF 489/486 3 1530 PART/2 86**
+
+A112 6.3.4.4 include in the pilot line (where applicable) a special tariff indicator **V** and the number of chargeable words for that part only.
+
+A113 6.3.4.5 All parts of a divided telegram shall be transmitted to the country of destination using the same routing and in sequential order.
+
+##### **7 Cancellation of telegrams at the request of the sender**
+
+A114 7.1 The sender of a telegram or his authorized representative may, on establishing his status and identity, cancel his telegram only if it has not been transmitted by the office of origin. After transmission has taken place, the addressee can only be notified of the cancellation of the telegram by means of another telegram from the sender.
+
+#### **IV. Counting of words**
+
+##### **1 General provisions**
+
+A115 1.1 In the counting words, a distinction shall be made between:
+
+A116 1.1.1 the number of actual words – each separate word, group of characters or single character that is preceded and followed by a space (or by either the start or the end of a line) shall be counted as one actual word;
+
+A117 1.1.2 the number of chargeable words – the provisions for counting the number of chargeable words are shown in A124 to A126.
+
+A118 1.2 Everything that the sender asks to have transmitted shall be chargeable, with the exception of the name of the code used for the wording of a secret language telegram, when this information is required by the origin or the destination country.
+
+A119 1.3 The following, however, shall not be included in the number of actual and chargeable words nor shall they be transmitted:
+
+A120 1.3.1 dashes used only to separate on the sender's copy the different words or groups;
+
+A121 1.3.2 other isolated signs, unless the sender has specifically requested their transmission.
+
+A122 1.4 The heading (see A30 to A44) shall not be included in the number of actual and chargeable words.
+
+A123 1.5 Service indications (if any) shall be included in the number of chargeable words in all chargeable telegrams and in the number of actual words in all telegrams.
+
+##### **2 Counting the number of chargeable words**
+
+A124 2.1 Words, groups of characters or single characters;
+
+A125 2.1.1 not exceeding ten characters shall be counted as one chargeable word each;
+
+A126 2.1.2 exceeding ten characters shall be counted at the rate of one chargeable word for each ten characters or part thereof.
+
+##### **3 Indication of the number of words in the preamble line**
+
+A127 3.1 When the number of chargeable words is the same as the number of actual words it shall be shown as a single number.
+
+A128 3.2 When the number of chargeable words is different from the number of actual words, both shall be shown, separated by a fraction bar. The number of chargeable words shall be shown first.
+
+##### **4 Irregularities in the counting of words**
+
+A129 4.1 Except for the case of telegrams originated by a mobile station, the counting of words by the office of origin shall be decisive both for transmission and for the international accounts.
+
+A130 4.2 In the case of a telegram originated by a mobile station, the counting of words by the land station is decisive.
+
+A131 4.3 Nevertheless, a transit office or the office of destination shall be entitled to call the attention of the office of origin (or, in the case of a telegram originated by a mobile station, the land station) to counting irregularities.
+
+A132 4.4 A transit office may not suspend transmission of a telegram because of irregularities in the counting of words.
+
+#### **V. Routing and retransmission of telegrams**
+
+A133 1.1 The routing of telegrams shall be in accordance with the routing list for the relevant network and mode of operation.
+
+A133A The transmission can be character-coded or image-coded.
+
+The following networks can be used:
+
+- a) the gentex network;
+- b) dedicated circuits;
+- c) the telex network;
+- d) the Public Switched Telephone Network (PSTN);
+- e) the Integrated Services Digital Network (ISDN);
+- f) the Circuit Switched Public Data Network (CSPDN);
+- g) the Packed Switched Public Data Network (PSPDN).
+
+- A134 1.2 In interworking between telegraph offices and between telegraph offices and bureau offices, the transmission and the routing of telegrams shall be in accordance with the mode of operation as agreed by the ROAs.
+- A135 1.3 Each ROA decides by which network and route the telegram shall be transmitted or retransmitted.
+
+#### VI. Transmission of telegrams
+
+##### 1 Order of transmission of telegrams
+
+- A136 1.1 The transmission of telegrams shall take place in the following order except where technically impracticable:
+- A137 1.1.1 telegrams relating to the safety of life;
+- A138 1.1.2 telegrams relative to the application of the United Nations Charter;
+- A139 1.1.3 government telegrams with priority;
+- A140 1.1.4 meteorological telegrams;
+- A141 1.1.5 ordinary private telegrams and **RCT** telegrams when urgent transmission and delivery have been requested;
+- A142 1.1.6 service telegrams and service advices;
+- A143 1.1.7 government telegrams, ordinary private telegrams, and **RCT** telegrams;
+- A144 1.1.8 letter telegrams (including government letter telegrams).
+- A145 1.2 Every office that receives, on an international circuit, a telegram presented as an **SVH** telegram, a government telegram (see also A215 and A216), a service telegram or a meteorological telegram shall forward it as such.
+- A146 1.3 Except where technically impracticable, telegrams having the same priority shall be transmitted by the sending office in the order of their time of handing in, and by transit offices in the order of their time of receipt.
+- A147 1.4 At transit offices, originating telegrams and transit telegrams to be transmitted over the same routes shall, except where technically impracticable, be placed together and transmitted according to the time of handing in or receipt, subject to the order laid down in A136 to A146.
+
+##### 2 Order of transmission of the various parts of a telegram
+
+- A148 2.1 The various parts of a telegram shall be transmitted as follows:
+- A149 2.1.1 the heading;
+- A150 2.1.2 the address part (including the service indications if any);
+- A151 2.1.3 the text part (including the signature, if any).
+
+##### 3 Transmission of the heading
+
+- A152 3.1 The provisions regarding the formation of the heading of a telegram are given in A27 to A38. Following the transmission of the numbering line and the pilot line (if required), the various parts of the preamble line shall be transmitted in the following order:
+
+- A153 3.1.1 the name of the office of origin;
+- A154 3.1.2 the number of words;
+- A155 3.1.3 the date and time of handing in of the telegram;
+- A156 3.1.4 any service instructions.
+
+##### **4 Transmission of the other parts of a telegram**
+
+- A157 4.1 Every telegram must be transmitted as received from the sender and/or accepted by the office of origin, subject to the conditions mentioned in A101 and A102.
+- A158 4.2 With the exception of service indications, which must always be transmitted in the form shown in A7, A10 or A11, and in cases settled by agreement between the various Administrations, the use of any abbreviations whatsoever and alterations of any kind shall be prohibited.
+
+##### **5 Reception**
+
+- A159 5.1 With the exception of mobile radio stations, no office may refuse to receive telegrams offered by a sending office, whatever their destination. However, in the case of a manifest irregularity, the operator shall point it out to the sending office by service advice. The responsibility for the telegram then reverts to the telegraph office of origin.
+- A160 5.2 Each received telegram should be considered by the receiving office to be a telegram sent by the sending office on purpose. When the receiving office is not the office of destination, the telegram shall be retransmitted to:
+  - the destination office, when it is located in the same country as the office receiving it;
+  - the destination office, when the office of destination is not in the same country as the receiving office but it can be retransmitted unambiguously.
+- A161 5.3 When the telegram cannot be transmitted unambiguously, the telegraph office of origin must be informed by a service advice, indicating the reason. The responsibility for the telegram then reverts to the telegraph office of origin.
+- A162 5.4 A telegram must not be refused or delayed because of irregularities. The telegram must be accepted and then, if necessary, a service advice sent to the office of origin requesting rectification.
+- A163 5.5 As soon as possible after reception, in each telegram the number of words received shall be compared with the number of actual words shown in the preamble line.
+- A164 5.6 Where, in accordance with A103, the sender has included repeated groups in the text part, the receiving office is not required to check such groups.
+
+##### **6 Errors and interruptions**
+
+- A165 6.1 When operators are in doubt as to the accuracy of the transmission or reception, they shall give or request the partial or complete repetition of telegrams that they have either sent or received by a service advice.
+- A166 6.2 Telegrams containing obvious errors can be retained only in cases where the rectifications can be obtained quickly. They must be retransmitted without delay with the
+
+service instruction **CTF** at the end of the preamble line. This instruction is supplemented by information about the nature of the rectification; for example, **CTF FOURTH**, meaning that the fourth word of the text will be corrected. Immediately after the retransmission of the telegram, the rectification shall be requested by service advice.
+
+- A167 6.3 If, through interruption or any other cause, it is not practicable to give or receive the repetition [or acknowledgement of receipt (see B48)], this circumstance shall not prevent the office that has received the telegrams from sending them on, the service instruction **CTF** being inserted at the end of the preamble line, any necessary correction following later.
+- A168 6.4 In cases of interruption, the receiving office shall immediately request the completion of an unfinished telegram and, when necessary, give an acknowledgement of receipt (see B48), either by another direct circuit if there is one in service or, if not, by a service advice, forwarded by whatever means is available.
+- A169 6.5 When the transmission of a telegram has not been completed or the acknowledgement of receipt is not received within a reasonable time, the telegram shall be transmitted afresh with the service instruction **AMPLIATION** (see A38). The meaning of this service instruction, **AMPLIATION**, may be indicated on the addressee's copy by the destination office.
+- A170 6.6 Where this second transmission is made by a route other than that used originally for forwarding the telegram, only the second transmission must be included in the international accounts. The sending office shall then make the necessary arrangements with the offices concerned, by service advice, with the object of excluding the original transmission of the telegram from the international accounts.
+
+#### VII. Interruption of telegram communications
+
+##### 1 Diversion of telegrams
+
+- A171 1.1 When the ordinary telegram communications are found to be interrupted, the office beyond which the interruption occurs or an office situated further back having at its disposal alternative routes shall forward the telegrams immediately by one of these routes or, failing that, by post (whenever practicable by registered letter) or by special messenger.
+
+#### VIII. Delivery at destination
+
+##### 1 General provisions
+
+- A172 1.1 The addressee of a telegram must prove his identity when requested to do so by the office of destination.
+- A173 1.2 On the telegram delivered to the addressee the following information from the preamble line of the telegram handed in at the office of origin shall always be given:
+- A174 1.2.1 the name of the office of origin;
+- A175 1.2.2 the number of words;
+- A176 1.2.3 the date and the time of handing in;
+- A177 1.2.4 those service instructions that reach the office of destination.
+
+##### 2 Methods of delivery
+
+- A178 2.1 Administrations shall notify the General Secretariat of the methods they normally use for delivery and quality of service (maximum delay for 95% of telegrams) for publication in the *Information for the Operation of the International Telegraph, Data Transmission and Telematic Services* [4].
+- A179 2.2 Telegrams shall be delivered by any means available according to their addresses, either to a private house, office, business house, etc., of the addressee, or to a place where he is living or staying temporarily (hotel, etc.) or to a *télégraphe restant*, a *poste restante* or to a post office box.
+- A180 2.3 Telegrams shall be delivered to the addressee by telephone, telex, teletex or facsimile as far as practicable where this method of delivery has been requested, unless the regulations of the destination Administration are contrary to such a procedure or unless the addressee has specifically requested that his telegrams should not be delivered by telephone, telex or facsimile.
+- A181 2.4 Telegrams may also be delivered by telephone, telex or facsimile in accordance with conditions laid down by the Administrations.
+- A182 2.5 Telegrams addressed to localities not served by international telecommunication circuits may be delivered to their address from a telegraph office of the country in which the place of destination is situated, either by post or, if these services exist, by express or by airmail. Nevertheless, delivery may be effected by such means from a telegraph office of another country when the destination country is not connected to the international telecommunication system.
+- A183 2.6 Telegrams shall be delivered or forwarded to their destination in the order of their receipt and priority, except in the cases specified for the delivery of letter telegrams. **SVH** telegrams as well as government telegrams with priority or telegrams relative to the application of the United Nations Charter shall be delivered without delay.
+- A184 2.7 Telegrams addressed to places in the locality served by the telegraph office shall be delivered without delay to their addresses subject to the limitation imposed by the working hours of delivery offices. Telegrams received during the night may be delivered immediately if they bear the service indication **URGENT**.
+- A185 2.8 Telegrams may be delivered either to the addressee, to an adult member of his family, to any person in his service, to his lodgers or guests, or to the receptionist at the hotel or the house, unless the addressee has designated in writing a special representative.
+- A186 2.9 If at the address indicated the messenger finds no one willing to accept the telegram on behalf of the addressee, a notice shall be left at the address, and the telegram shall be taken back to the office, to be delivered to the addressee or his representative upon application. However when there is no doubt regarding the address of the addressee, telegrams may be placed in his letter box if there is also no doubt that the addressee will empty his box within a reasonable period. When the addressee, after being notified of the arrival of a telegram, does not take delivery within a period not exceeding 48 hours (excluding weekends and official holidays), action shall be taken to notify the office of origin of the delay in delivery in accordance with A191 to A193.
+- A187 2.10 Telegrams that have to be placed as *poste restante*, in a post office box or forwarded by post shall be handed without delay to the postal service by the telegraph office of destination.
+
+- A188 2.11 Telegrams addressed *poste restante*, post office box or delivered by post shall, with respect to delivery and period of retention, be subject to the same rules as postal correspondence. As regards non-delivery they shall be subject to the provisions relative to the non-delivery of telegrams.
+- A189 2.12 When a telegram is addressed *télégraphe restant* it shall be claimed at the telegraph counter by the addressee or his duly authorized representative who shall, if so requested, prove his identity.
+- A190 2.13 Telegrams to be delivered to passengers in a ship may be delivered to the representatives of the ship. If the ship is entering port, the telegram shall be delivered preferably to the addressee himself, before disembarkation where practicable, and where it does not entail additional expense (for boat hire, for example).
+
+##### 3 Non-delivery and delayed delivery
+
+- A191 3.1 When a telegram cannot be delivered, the office of destination shall send, with the minimum delay, a service advice to the office of origin stating the cause of the non-delivery. (For a layout of this telegram, see D43.)
+- A192 3.2 The address repeated in the service advice shall also include the name of the office of destination if this information is considered necessary. According to the circumstances, this advice shall be completed with the reason for non-delivery.
+- A193 3.3 When a telegram with *télégraphe restant*, *poste restante* or post office box delivery, or a telegram to be delivered to an hotel, club, shipping or tourist agency, etc. has not been claimed by the addressee and is returned to the telegraph service, the office of destination shall without delay notify non-delivery to the office of origin.
+- A194 3.4 The office of origin shall check the address and, if it has been altered, rectify it at once by a reply advice. The service advice shall contain any instructions necessary to correct any errors (for layout of this telegram, see D44).
+- A195 3.5 If practicable, when a transit office receives a service advice of non-delivery, it shall check the address from the transit form of the original telegram and, if it observes an error, shall itself transmit to the office of destination the correction. If it does not observe an error, it shall transmit the service advice to the office of origin (see D32).
+- A196 3.6 If the address has not been altered, the office of origin, whenever practicable, shall communicate the service advice of non-delivery to the sender. Failure to communicate this advice or delay in doing so shall not give a right to the refund of the charge paid for the telegram.
+- A197 3.7 The addressee of a service advice of non-delivery may complete, rectify or confirm the address of the original telegram only by means of a service advice.
+- A198 3.8 If, after the service advice of non-delivery has been sent, the telegram is claimed by the addressee, or if the office of destination is able to deliver the telegram without having received a correcting advice, it shall transmit to the office of origin a second service advice advising details of the delivery (for layout of this telegram, see D45).
+- A199 3.9 The service advice of delivery shall be communicated to the sender, if he was notified of the non-delivery.
+- A200 3.10 When it has not been possible to deliver a telegram to the addressee within a minimum period of 14 days from the date of its receipt at the office of destination, such a telegram may be disposed of, subject to the national regulations of the destination country.
+
+#### IX. Obligatory telegrams
+
+##### 1 Telegrams relating to the safety of life (SVH)
+
+- A201 1.1 In accordance with Article 25 of the Convention [1], telegrams relating to the safety of life on land, at sea, in the air or in outer space, and exceptionally urgent epidemiological telegrams of the World Health Organization shall have absolute priority over all other telegrams.
+- A202 1.2 **SVH** telegrams, whether sent by an authority or private person, must refer to the safety of life in cases of exceptional urgency which are obviously of general interest.
+- A203 1.3 Exceptionally, an **SVH** telegram may be accepted without the name of an addressee.
+- A204 1.4 **SVH** telegrams sent by the Headquarters of the World Health Organization or by the regional epidemiological centres of that Organization shall be certified as really being telegrams of exceptional urgency relating to the safety of life.
+- A205 1.5 The service indication **SVH** shall be shown before the address. No service indications other than **SVH** shall be admitted in safety of life telegrams. This service indication shall be included in the telegram:
+- A206 1.5.1 by the office of origin in the case of an **SVH** telegram handed in at a telegraph office;
+- A207 1.5.2 by the receiving land station in the case of an **SVH** telegram following a distress signal from a ship or an aircraft.
+
+##### 2 Government telegrams and telegrams relative to the application of the United Nations Charter
+
+- A208 2.1 Government telegrams are, according to the definition of the Convention [1], telegrams originating with any of the authorities specified below:
+- the Head of a State;
+  - the Head of a government and members of a government;
+  - Commanders-in-Chief of military forces, land, sea or air;
+  - diplomatic or consular agents;
+  - the Secretary-General of the United Nations; Heads of the principal organs of the United Nations<sup>1</sup>;
+  - the International Court of Justice.
+- A209 2.1.1 Replies to government telegrams shall also be regarded as government telegrams.
+- A210 2.2 Government telegrams must bear the seal or stamp of the authority that sends them. This shall not be required when the authenticity of the telegram is not in doubt.
+- A211 2.3 The right to send a reply as a government telegram shall be established by the production of the original government telegram.
+
+---
+
+<sup>1</sup> However, the Heads of the specialized agencies of the United Nations are not included among the authorities entitled to send government telegrams (see Resolution No. 40 of the Plenipotentiary Conference of the International Telecommunication Union, Nairobi, 1982 [1]).
+
+- A212 2.4 The telegrams of consular agents carrying on private business shall only be regarded as government telegrams when they are addressed to an official person. Telegrams that do not fulfil this condition shall, however, be accepted by telegraph offices and transmitted as government telegrams, but these offices shall at once report the matter to their Administration.
+- A213 2.5 In government telegrams for which the sender does not request priority, the service indication **ETAT** shall be shown before the address.
+- A214 2.6 In government telegrams for which the sender desires priority, the service indication **ETATPRIORITE** shall be shown before the address.
+- A215 2.7 Exceptionally, and subject to the application of the provisions of Articles 25 and 36 of the Convention [1], Administrations shall take the necessary steps to secure a special priority for telegrams relative to the application of the provisions of Chapters VI, VII and VIII of the United Nations Charter, exchanged in an emergency, between the following persons:
+- the President of the Security Council;
+  - the President of the General Assembly;
+  - the Secretary-General of the United Nations;
+  - the Chairman of the Military Staff Committee;
+  - the Chairman of a regional sub-committee of the Military Staff Committee;
+  - a representative to the Security Council or to the General Assembly;
+  - a Member of the Military Staff Committee;
+  - the Chairman or the Principal Secretary of a committee set up by the Security Council or the General Assembly;
+  - a person performing a mission on behalf of the United Nations;
+  - a head of State;
+  - a minister member of a Government;
+  - the Administrative Head of a trust territory designated as a strategic area.
+- A216 2.7.1 Such telegrams, which do not fall under the class of government telegrams, shall be regarded as government telegrams and shall be accepted only if they bear the personal authorization of one of the officials mentioned above.
+- A217 2.7.2 The service indication **ETATPRIORITE** shall be shown before the address.
+- A218 2.8 Where special arrangements or regional arrangements concluded under Articles 31 and 32 of the Convention [1] exist regarding accounting for **ETATPRIORITE** and **ETAT** telegrams, the identity of the government or of the organization should appear in the preamble line using, wherever possible, the two letters of the destination indicator designating the government of the country concerned (or the two letters identifying the organization) followed by a space and the abbreviation **GOVT**.
+- A219 2.9 When a request has been made for the routing of a government telegram by a prescribed route, and such request has been accepted, the telegram may not be transmitted by a route other than the requested route unless the sender, duly consulted, has authorized such procedure.
+- A220 2.10 The authorities entitled under the Convention [1] to send government telegrams may send letter telegrams with the service indication **LTF**.
+
+A221 2.11 If difficulties arise in the routing of an **ETATPRIORITE** telegram which may delay its delivery to the addressee or if delivery is jeopardized because of exceptional circumstances, the sending office if possible or the office of destination shall inform the office of origin without delay.
+
+##### 3 Telegrams concerning persons protected in time of war by the Geneva Conventions of 12 August 1949
+
+A222 3.1 In the following telegrams, the service indication **RCT** shall be shown before the address:
+
+A223 3.1.1 telegrams addressed to prisoners of war, civilian internees or their representatives (prisoners' representatives, internee committees) by recognized relief societies assisting war victims<sup>2</sup>;
+
+A224 3.1.2 telegrams that prisoners of war and civilian internees are permitted to send or those sent by their representatives (prisoners' representatives, internee committees) in the course of their duties under the Convention<sup>2</sup>;
+
+A225 3.1.3 telegrams sent in the course of their duties under the Conventions by the national information bureaux or the Central Information Agency for which provision is made in the Geneva Conventions, or by delegations of such bureaux or Agency, concerning prisoners of war, civilians who are interned or whose liberty is restricted, or the death of military personnel or civilians in the course of hostilities<sup>3</sup>.
+
+A226 3.2 In telegrams bearing the service indication **RCT**, the only special service that shall be admitted is urgent transmission and delivery (**URGENT**) (if this service is admitted by the origin and destination countries).
+
+A227 3.3 Telegrams sent by prisoners of war, civilian internees or their representatives shall bear the official stamp of the camp or the signature of the camp commandant or one of his deputies.
+
+A228 3.4 Telegrams sent by the national information bureaux and the Central Information Agency for which provision is made in the Geneva Conventions, or by delegations thereof, as well as telegrams sent by recognized relief societies assisting war victims, shall bear the official stamp of the bureau, agency, delegation or society that sends them.
+
+##### 4 Ordinary private telegrams
+
+A229 4.1 Ordinary private telegrams are obligatory telegrams other than those bearing the service indications **SVH**, **ETAT**, **ETATPRIORITE**, **A**, **OBS** or **RCT**. Ordinary private telegrams may be attributed special services in which case the relevant service indications in A11 should be shown before the address.
+
+---
+
+<sup>2</sup> Article 71, paragraph 2; Article 74, paragraph 5 and Article 81, paragraph 4 of the Geneva Convention of 12 August 1949, relative to the Treatment of Prisoners of War; Article 104, paragraph 3; Article 107, paragraph 2 and Article 110, paragraph 5 of the Geneva Convention of 12 August 1949, relative to the Protection of Civilian Persons in Time of War.
+
+<sup>3</sup> Articles 122, 123 and 124 of the Geneva Convention of 12 August 1949, relative to the Treatment of Prisoners of War, Articles 136, 140 and 141 of the Geneva Convention of 12 August 1949, relative to the Protection of Civilian Persons in Time of War.
+
+##### 5 Telegraph service correspondence
+
+- A230 5.1 Telegraph service correspondence consists of service telegrams and service advices (see Division D and Recommendation F.17).
+
+##### 6 Meteorological telegrams
+
+- A231 6.1 The term *meteorological telegram* denotes a telegram sent by an official meteorological service or by a station in official relation with such a service, and addressed to such a service or to such a station, and which consists solely of meteorological observations or forecasts. A telegram of this kind must always be regarded as drawn up in plain language.
+- A232 6.2 The service indication **OBS** shall be shown before the address. No service indication other than **OBS** shall be admitted in meteorological telegrams.
+- A233 6.3 On request by the accepting officer, the sender must affirm that the text of his telegram fulfils the conditions prescribed for meteorological telegrams.
+
+#### X. Optional telegrams
+
+##### 1 Postal financial telegrams
+
+- A234 1.1 The issue, wording of the text and payment of money orders and postal cheques are regulated by the Universal Postal Union, even when they are transmitted by telegraph.
+- A235 1.2 Money orders and postal cheques transmitted by telegraph are called "**POSTFIN** telegrams". The handling of **POSTFIN** telegrams between Administrations admitting them shall be subject to the same rules as other telegrams.
+- A236 1.3 **POSTFIN** telegrams shall bear the service indication **POSTFIN** as the first line of the address part. Only the service indication **URGENT** may precede the service indication **POSTFIN**.
+- A237 1.4 Any postal service indications (**AVIS PAIEMENT**, **AVIS INSCRIPTION** and **PAIEMENT MAIN PROPRE**) shall be shown on the second line of the address part.
+- A238 1.5 The office of destination shall be shown as the last line of the address part.
+- A239 1.6 If the locality in which the post office of payment is situated has no telegraph office, the **POSTFIN** telegram must bear the name of the post office of payment and that of the telegraph office which serves it.
+- A240 1.7 Examples of the format of **POSTFIN** telegrams are given in C47 and C48.
+
+##### 2 Letter telegrams
+
+- A241 2.1 Letter telegrams are telegrams for which special provisions concerning accounting rates, priority of transmission, and delivery are applied.
+- A242 2.2 Administrations that do not accept and deliver letter telegrams must admit them in transit.
+
+- A243 2.3 Letter telegrams bearing the service indication **LTF** shall be subject, as regards transmission and delivery, to the same conditions as **LT** telegrams. As regards acceptance, they shall be subject to the same conditions as government telegrams.
+- A244 2.4 However, the provisions of Article 19 of the Convention [1] (see A259 to A265), relating to stoppage of telegrams, shall not apply to government letter telegrams (**LTF**).
+- A245 2.5 As regards acceptance, transmission and delivery, letter telegrams shall be subject to the limitations set out in A246 to A248.
+- A246 2.6 Radiotelegrams shall not be admitted as letter telegrams.
+- A247 2.7 The only special service admitted in letter telegrams shall be de luxe form (**LX** or **LXDEUIL**).
+- A248 2.8 Letter telegrams are as a matter of course delivered by post.
+
+##### 3 Privilege telegrams
+
+- A249 3.1 Privilege telegrams (**CONFERENCE**) may be exchanged during the conferences and meetings of the ITU, in accordance with Recommendation D.193, which specifies limits on the number and length of such telegrams in certain cases.
+- A250 3.2 Special services apart from **TFx**, **TLXx** and **FAXx** shall not be admitted in privilege telegrams. Exceptionally, however, Heads of delegations or their deputies and members of the Administrative Council may exchange such telegrams with urgent transmission and delivery.
+
+#### XI. Special services
+
+##### 1 General provisions
+
+- A251 1.1 The provisions that form the subject of the other Chapters shall apply in their entirety to telegrams with special services, subject to the modifications prescribed in A253 to A258.
+- A252 1.2 In the application of A253 to A258, the special services offered to the public may be combined subject to the class of the telegram and the acceptance of the special services in question by the Administrations of the office of origin and the office of destination.
+
+##### 2 Urgent transmission and delivery
+
+- A253 2.1 The sender of an ordinary private telegram may obtain priority in transmission and delivery by requesting the special service urgent transmission and delivery (**URGENT**). The service indication **URGENT** shall be shown before the address.
+- A254 2.2 Telegrams with urgent transmission and delivery shall be transmitted with the priority indicated in A124 to A135. Their precedences among themselves shall be settled by the time of their handing in at the office of origin and receipt at transit offices except where technically impracticable.
+- A255 2.3 Administrations that accept telegrams with urgent transmission and delivery only in transit must admit them among telegrams of the same origin and destination either on the
+
+circuits where there is direct transmission across their territory or in their retransmitting offices.
+
+##### **3 De luxe form**
+
+- A256 3.1 The sender of a telegram may request the de luxe service for his telegram, which will then be delivered on a special de luxe form and/or in a special envelope.
+- A257 3.2 When the sender wishes the de luxe service to be used, the service indication **LX** should be shown before the address of telegrams sent on joyful occasions; for telegrams sent on an occasion of mourning, the service indication **LXDEUIL** should be used.
+- A258 3.3 The service shall be organized by special arrangements between the Administrations concerned, regarding in particular, the different occasions on which these telegrams may be used.
+
+#### **XII. Stoppage of telegrams**
+
+##### **1 Transmission of certain telegrams as of right – Notification of stoppage**
+
+- A259 1.1 The right to stop transmission of certain private telegrams as provided for in Article 19<sup>4</sup> [1] of the Convention shall be exercised by the terminal or transit telegraph offices subject to reference to the appropriate authority, which shall decide without appeal.
+- A260 1.2 SVH telegrams, government telegrams and service telegrams shall be entitled to transmission as of right. Telegraph offices shall exercise no control over these telegrams.
+- A261-A264 Deleted.
+- A265 1.3 The origin Administration of the telegrams must be notified of the stoppage of any telegram.
+
+#### **XIII. Archives**
+
+##### **1 Archives**
+
+- A266 1.1 The original or facsimile copies of telegrams and the relevant documents relating to handing in, transmission (if practicable) and delivery, which should be retained by the Administrations, shall be preserved with all precautions necessary to ensure secrecy, until the accounts relative thereto are settled and, in any case, for at least six months counted
+
+##### --- **4 Article 19 of the Convention – Stoppage of Telecommunications**
+
+1. Members reserve the right to stop the transmission of any private telegram which may appear dangerous to the security of the State or contrary to their laws, to public order or to decency, provided that they immediately notify the office of origin of the stoppage of any such telegram or any part thereof, except when such notifications may appear dangerous to the security of the State.
+2. Members also reserve the right to cut off any other private telecommunications which may appear dangerous to the security of the State or contrary to their laws, to public order or to decency.
+
+from the month after that in which the telegram was handed in. Administrations may preserve the information by any other means, e.g. magnetic or electronic records.
+
+A267 1.2 However, should an Administration deem it desirable to destroy such documents before the above-mentioned period, and hence is not in a position to carry out an enquiry in respect of the services for which it is responsible, such Administration shall bear all the consequences both as regards refund of charges and any difference in international accounts that might otherwise have been observed.
+
+##### **2 Inspection of original forms of telegrams – Supplying copies of telegrams**
+
+A268 2.1 Subject to the exceptions contemplated in Article 22 (No. 137) of the Convention [1], originals or copies of telegrams may be shown only to the sender or the addressee, after verification of his identity, or to the authorized representative of one of them.
+
+A269 2.2 During the minimum period fixed for preservation of the records, the sender and the addressee of a telegram or their authorized representatives shall have the right to obtain certified copies or photocopies:
+
+A270 2.2.1 of this telegram;
+
+A271 2.2.2 of the delivery copy, if this copy or a duplicate of it has been preserved by the destination Administration.
+
+A272 2.3 Administrations may fix a charge for copies and photocopies of originals or of copies delivered in accordance with A268 to A271.
+
+A273 2.4 Administrations shall not be bound to show or to furnish copies or photocopies of the documents mentioned above unless the senders, the addressees or their authorized representatives furnish the particulars necessary for tracing the telegrams to which their requests relate.
+
+### DIVISION B
+
+### OPERATIONAL PROVISIONS APPLYING TO MORSE AND SOUNDER WORKING
+
+#### I. Morse code
+
+##### 1 Morse code signals
+
+B1 1.1 The following are the written characters that may be used and the corresponding Morse code signals:
+
+B2 1.1.1 *Letters*
+
+|            |       |   |      |   |       |
+|------------|-------|---|------|---|-------|
+| a          | .-    | i | ..   | r | .-.   |
+| b          | -...  | j | .--- | s | ...   |
+| c          | -. -. | k | -. - | t | -     |
+| d          | -..   | l | .-.. | u | ..-   |
+| e          | .     | m | --   | v | ...-  |
+| accented e | ..-.. | n | -. . | w | .--   |
+| f          | ..-.  | o | ---  | x | -..-  |
+| g          | --.   | p | .--. | y | -. -- |
+| h          | ....  | q | --.- | z | --..  |
+
+B3 1.1.2 *Figures*
+
+|   |       |   |       |
+|---|-------|---|-------|
+| 1 | .---- | 6 | -.... |
+| 2 | ..--- | 7 | --... |
+| 3 | ...-- | 8 | --..  |
+| 4 | ....- | 9 | ----. |
+| 5 | ..... | 0 | ----- |
+
+B4 1.1.3 *Punctuation marks and miscellaneous signs*
+
+|                                                                                                        |         |         |
+|--------------------------------------------------------------------------------------------------------|---------|---------|
+| Full stop (period) .....                                                                               | [.]     | .-.-.-  |
+| Comma .....                                                                                            | [,]     | --..--  |
+| Colon or division sign .....                                                                           | [:]     | ---...  |
+| Question mark (note of interrogation or request for repetition of a transmission not understood) ..... | [?]     | ..--..  |
+| Apostrophe .....                                                                                       | [']     | .----   |
+| Hyphen or dash or subtraction sign .....                                                               | [-]     | -....-  |
+| Fraction bar or division sign .....                                                                    | [/]     | -. -.   |
+| Left-hand bracket (parenthesis) .....                                                                  | [(]     | -. --.  |
+| Right-hand bracket (parenthesis) .....                                                                 | [)]     | -. --.- |
+| Inverted commas (quotation marks) (before and after the words) .....                                   | [ " " ] | .-.-.-  |
+| Double hyphen .....                                                                                    | [=]     | -....-  |
+| Understood .....                                                                                       |         | ...-    |
+
+|                                                 |           |
+|-------------------------------------------------|-----------|
+| Error (eight dots)                              | ........  |
+| Cross or addition sign                          | [+] .-.-. |
+| Invitation to transmit                          | -.-       |
+| Wait                                            | .-...     |
+| End of work                                     | ...-.-    |
+| Starting signal (to precede every transmission) | -.-.-     |
+| Multiplication sign                             | [×] -..-  |
+
+##### 2 Spacing and length of the signals
+
+- B5 2.1 A dash is equal to three dots.
+- B6 2.2 The space between the signals forming the same letter is equal to one dot.
+- B7 2.3 The space between two letters is equal to three dots.
+- B8 2.4 The space between two words is equal to seven dots.
+- B9 2.5 On the Wheatstone instrument, where perforators are used, the space between two letters shall be equal to one *centre hole* perforation and the space between two words shall be equal to three *centre holes*.
+
+##### 3 Transmission of signs for which there is no corresponding signal in the Morse code
+
+- B10 3.1 Signs that have no corresponding signal in the Morse code, but that are acceptable in the writing of telegrams, shall be sent as follows:
+
+###### 3.2 Multiplication sign
+
+- B11 3.2.1 For the multiplication sign, the signal corresponding to the letter X shall be transmitted.
+
+###### 3.3 Percentage or per thousand sign
+
+- B12 3.3.1 To indicate the signal % or ‰, the figure **0**, the fraction bar and the figures **0** or **00** shall be transmitted successively (i.e. **0/0**, **0/00**).
+- B13 3.3.2 A whole number, a fractional number, or a fraction, followed by a % or ‰ sign, shall be transmitted by joining up the whole number, the fraction number, or the fraction to the % or ‰ by a single hyphen.
+
+Examples: For 2%, transmit **2-0/0**, and not **20/0**.
+
+For  $4\frac{1}{2}$ ‰, transmit **4-1/2-0/00**, and not **41/20/00**.
+
+##### 3.4 Inverted commas (quotation marks)
+
+- B14 3.4.1 The special signal for inverted commas shall be transmitted before and after the word or words. However, where code converters are used, the apostrophe may be transmitted twice before and twice after the word or words to signal inverted commas (quotation marks).
+
+##### 3.5 Minute and second signs
+
+- B15 3.5.1 To transmit the minute (') or second (") signs, when such signs follow figures – for example 1'15" – the apostrophe signal (. - - - - .) must be used once or twice as appropriate. The signal (. - . . - .) reserved for inverted commas may not be used for the second sign.
+
+##### 4 Transmission of groups of figures and letters, of ordinal numbers or of fractions
+
+- B16 4.1 A group consisting of figures and letters shall be transmitted without spaces between figures and letters.
+- B17 4.2 Ordinal numbers composed of figures and letters, 30<sup>me</sup>, 25<sup>th</sup>, etc., shall be transmitted in the form **30ME**, **25TH**, etc.
+- B18 4.3 A number that includes a fraction shall be transmitted with the fraction linked to the whole number by a single hyphen.
+
+Example: For 1<sup>3</sup>/<sub>4</sub>, transmit **1-3/4**, and not **13/4**.  
+For <sup>3</sup>/<sub>4</sub> 8, transmit **3/4-8**, and not **3/48**.  
+For 363<sup>1</sup>/<sub>2</sub> 4 5642, transmit **363-1/2 4 5642**, and not **3631/2 4 5642**.
+
+#### II. General transmission rules
+
+- B19 **1** All correspondence between two offices shall begin with the call signal.
+- B20 1.1 For calling, the calling office shall transmit the call sign (not more than twice) of the office required, the word **DE** followed by its own call sign, the appropriate service abbreviation to indicate a priority telegram, an indication of the reason for the call and the signal – . – unless there are special rules peculiar to the type of apparatus used. The call shall always be made at hand speed.
+- B21 **2** The office called must reply immediately by transmitting the call sign of the calling station, the word **DE** followed by its own call sign and the signal – . –
+- B22 2.1 If the office called is unable to receive, it shall give the *wait* signal. If it expects the wait to exceed ten minutes, the reason and probable duration shall be given.
+- B23 2.2 When an office called does not reply, the call may be repeated at suitable intervals.
+- B24 2.3 When the office called does not reply to the repeated call, the condition of the circuit must be examined.
+- B25 **3** The double hyphen (– . . . –) shall be transmitted either to separate:
+- B26 3.1 the preamble from the service indications;
+- B27 3.2 the service indications from each other;
+- B28 3.3 the service indications from the address;
+- B29 3.4 the office of destination from the text;
+- B30 3.5 the text from the signature.
+- B31 **4** A transmission, once begun, may not be interrupted to give place to a communication of higher priority except in a case of absolute urgency.
+
+- B32 5 Every telegram shall be terminated with a cross signal (.-.-.).
+- B33 6 The end of the transmission shall be indicated by the cross signal (.-.-.) followed by the *invitation to transmit* signal **K** (-.-.).
+- B34 7 The end of work shall be indicated by the office that transmitted the last telegram. The correct indication is the *end of work* signal (.-.-.).
+
+#### III. Transmission of telegrams with identical text
+
+##### 1 Identical texts
+
+- B35 1.1 When an office has to transmit to the same office more than five telegrams having identical texts and comprising more than 50 actual words, it may transmit the text once only. In that case, the text shall be transmitted in the first telegram only, and the text of all the telegrams with identical text that follow shall be replaced by the words **TEXT NR . . .** (number of first telegram).
+- B36 1.2 This procedure necessitates the transmission in succession of all telegrams with identical text.
+- B37 1.3 The receiving office must be informed of the transmission of telegrams with identical text by a service note on the following lines:  
+... **TELEGRAMS WITH IDENTICAL TEXT FOLLOW**
+- B38 1.4 When reception is possible by means of perforated tape, the receiving office should be informed in ample time to allow it to receive telegrams with identical text by tape.
+
+#### IV. Transmission irregularities – Service notes
+
+- B39 1 To indicate *wait*, the corresponding signal (.-...) shall be transmitted.
+- B40 2 If the sending operator becomes aware of an error, he shall stop, give the error signal (.....), repeat the last word correctly transmitted, and continue the transmission.
+- B41 3 If it is necessary to interrupt the transmission for any reason, the procedure shall be as follows until transmission stops.
+- B42 3.1 Morse simplex, transmit a series of dots.
+- B43 3.2 Morse duplex, transmit the letters **BK**.
+- B44 3.3 Once transmission has been stopped, the receiving operator shall repeat the last word correctly received followed by a question mark. The sending operator shall resume transmission from that word.
+- B45 3.4 If a repetition is asked for after a long interruption, the telegram and the part of the telegram in question must be precisely indicated.
+- B46 4 Service notes **XQ** can be interposed between telegrams of a series.
+
+#### V. Checking the number of words transmitted – Acknowledgement of receipt
+
+##### 1 Checking the number of words transmitted
+
+- B47 1.1 Where the receiving operator finds a discrepancy between the number of actual words shown in the preamble line and the number received, he shall notify the sending operator by indicating the number of words received, followed by the first character of each word (example: **17 WDS J C R B 2 D . . .** etc.). If the sending operator has simply made an error in transmitting the number of words, he shall reply **ADMITTED** and indicate the actual number of words (example: **17 ADMITTED**); if not, he shall rectify the passage found to be incorrect according to the initials received. In both cases, he shall interrupt, if necessary, the transmission of the initials as soon as he is able to rectify or confirm the number of words.
+
+##### 2 Acknowledgement of receipt
+
+- B48 2.1 After the verification of the number of words and the rectification of any errors, the receiving office shall acknowledge to the sending office the receipt of the telegram or telegrams forming the series.
+- B49 2.2 A single telegram shall be acknowledged by the letter **R** followed by the number of the telegram received, for example: **R 436**.
+- B50 2.3 For an **SVH** telegram, a government telegram with priority, or a telegram relative to the application of the United Nations Charter, receipt shall be acknowledged in the form: **R 436 SVH** or **R 436 ETAT**.
+- B51 2.4 For a series of telegrams, the letter **R** shall be given with the number of telegrams received, and also the first and last numbers of the series, for example, **R 6 157 162**.
+- B52 2.5 If the series includes **SVH** telegrams or government telegrams with priority, the acknowledgement of receipt shall be supplemented by the numbers of these telegrams thus:  
+**R 6 157 162 INCLUDING 159 SVH 161 ETAT**
+- B53 2.6 In every case, the acknowledgement of receipt must be transmitted immediately in the following form:  
+**LR 683 MISSING 680 RETAINED 665** [This acknowledgement of receipt contains the last received (**683**), the number **680** missing and the number **665** retained.]
+- B54 2.7 The sending operator must request the acknowledgement of receipt immediately after the transmission of an **SVH** telegram, a government telegram with priority or a telegram relative to the application of the United Nations Charter. In such cases, the acknowledgement of receipt shall take the following form:  
+**LR SVH 683**
+
+#### VI. Transmission procedures
+
+- B55 1 Transmission may be conducted as follows, according to the volume of traffic:
+- B56 1.1 alternate transmission of telegrams;
+- B57 1.2 alternate transmission in series.
+
+- B58 2 In alternate transmission, the receiving office shall not have the right to interrupt the transmission to give place to a communication of higher priority, except in cases of absolute urgency, (see B31).
+- B59 3 The exchange of telegrams in alternate order between two offices in direct communication shall follow the rules concerning the order of transmission.
+- B60 3.1 A telegram of higher priority in order of transmission shall not count in the alternate order.
+- B61 3.2 The office that has just finished a transmission shall have the right to continue when it has telegrams awaiting transmission or when telegrams reach it that are entitled to priority over those that the office in communication has to transmit, unless the latter has already begun its transmission.
+- B62 3.3 When an office has finished transmitting, the office that has just received shall transmit in its turn; if the latter has nothing to transmit, the former shall continue to send its traffic. If neither has anything to transmit, the offices shall exchange the *end of work* signal.
+- B63 4 When traffic so justifies, and subject to agreement between the offices in communication, telegrams shall be exchanged in series alternately.
+- B64 4.1 Telegrams of the same series shall be considered as forming a single transmission. However, each correctly received telegram shall be retained at the receiving position until the next but one telegram begins or for the time normally required to transmit a telegram of average length.
+- B65 4.2 Each series shall comprise a maximum of five telegrams. Nevertheless, every telegram containing more than 100 words on the Morse instrument or more than 150 words on sound-reading instruments shall count as a series or terminate a series already in course of transmission.
+- B66 4.3 The sending office shall end a series in course of transmission when it has only letter telegrams to send. It shall not resume transmission until the office with which it is working has no more telegrams of higher priority on hand.
+
+### DIVISION C
+
+### OPERATIONAL PROVISIONS APPLYING TO PRINTING TELEGRAPH SYSTEMS
+
+#### I. Transmission signals
+
+##### 1 Transmission signals of International Telegraph Alphabet No. 2
+
+- C1 1.1 Figure 1 shows the signals of the International Telegraph Alphabet No. 2.
+- C2 1.2 In the interests of speed and efficiency in the movement of telegraph traffic, the use of the five-unit code is recommended in accordance with International Telegraph Alphabet No. 2 as defined in Recommendation S.1. However, this provision need not apply to Administrations which by mutual agreement have made other arrangements in respect of a particular circuit or network. In such cases, the Administrations concerned could provide suitable facilities for converting from their method of operation to the five-unit code of International Telegraph Alphabet No. 2 whenever it becomes desirable to interconnect with offices using the latter system.
+- C3 1.3 The graphic characters that have a corresponding signal in International Telegraph Alphabet No. 2 are those shown in A16, A17 and A18.
+- C4 1.4 The coding of the printed characters and control characters conforming to Recommendation S.1 is set out in Figure 1.
+
+![Figure 1/F.1: International Telegraph Alphabet No. 2 (as shown on perforated tape). The image shows a strip of paper tape with five rows of potential perforations. Black dots represent holes. Below the tape is a table mapping these hole patterns to characters in 'Figure case' and 'Letter case'.](74448f9178da618d823e5a5dadc56fb5_img.jpg)
+
+|   |   |   |   |   |   |   |   |   |   |    |    |    |    |    |    |    |    |    |    |    |    |    |    |    |    |    |    |    |    |    |    |    |
+|---|---|---|---|---|---|---|---|---|---|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|
+|   | 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 | 26 | 27 | 28 | 29 | 30 | 31 | 32 |
+| 1 | – | ? | : | ⊠ | 3 |   |   | 8 | ⍿ | (  | )  | .  | ,  | 9  | 0  | 1  | 4  | '  | 5  | 7  | =  | 2  | /  | 6  | +  |    | <  | ≡  | ↓  | ↑  | △  | □  |
+| A | 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  |    |    |    |    |    |    |
+
+● Represents a perforation in the paper tape (Z condition or stop polarity)  
+1 Figure case  
+A Letter case  
+⊠ or ✦ *Who are you?* in the international telex and gentex services. The combinations Nos. 6, 7 and 8 in the figure case are available for national usage.  
+⍿ Audible signal (bell)  
+< Carriage return  
+≡ Line feed  
+↓ Letter-shift  
+↑ Figure-shift  
+△ or → Space  
+□ Unperforated tape or start polarity (not normally used)
+
+Figure 1/F.1: International Telegraph Alphabet No. 2 (as shown on perforated tape). The image shows a strip of paper tape with five rows of potential perforations. Black dots represent holes. Below the tape is a table mapping these hole patterns to characters in 'Figure case' and 'Letter case'.
+
+T0102440-92
+
+**Figure 1/F.1 – International Telegraph Alphabet No. 2 (as shown on perforated tape)**
+
+- C5 1.4.1 To indicate a blank, the signal space shall be transmitted.
+
+- C6 1.4.2 To indicate a transmission error, proceed as per C94.  
+C7 1.4.3 To indicate wait, the characters **MOM** shall be transmitted.
+
+##### 2 Transmission of signs for which there is no corresponding signal in the telegraph alphabet
+
+- C8 2.1 Signs that have no corresponding signal in a telegraph alphabet but are acceptable in the writing of telegrams shall be sent in such a way as not to distort the meaning and taking into account the possibilities offered by the telegraph alphabet as follows.
+- C9 2.1.1 *Percentage sign (%)*: Successively transmit the figure **0**, the fraction bar and the figure **0** (example: **0/0**).
+- C10 2.1.2 *Per thousand sign (‰)*: The ‰ sign shall be indicated by transmitting the figure **0** followed by the fraction bar and the figures **00** (example: **0/00**).
+- C11 2.1.3 *Combination of numbers and % or ‰*: A whole number, a fractional number, or a fraction, followed by a % or a ‰ sign, shall be transmitted by joining up the whole number, the fractional number or the fraction to the % or ‰ sign by a dash.
+- Examples: For 2% transmit **2-0/0**, and not **20/0**.  
+For 4½‰, transmit **4-1/2-0/00**, and not **41/20/00**.
+- C12 2.1.4 *Inverted commas (quotation marks) (")*: Transmit the apostrophe (') twice at the beginning and end of the text within the inverted commas (" ").
+- C13 2.1.5 *Minute (') and second (") signs*: The minute sign and the second sign shall be transmitted by means of the apostrophe sign, transmitted once for the minute sign, and twice for the second sign.
+
+##### 3 Transmission of ordinal numbers, groups of figures and letters or of numbers that include fractions
+
+- C14 3.1 Ordinal numbers composed of figures and letters: 30<sup>me</sup>, 25<sup>th</sup>, etc., shall be transmitted in the form of **30ME**, **25TH**, etc.
+- C15 3.2 Letters or groups of letters followed by letters or figures placed above or below the line shall be transmitted in the form substituted for them by the sender.
+- C16 3.3 Groups consisting of figures and letters must be transmitted as set forth in the telegram.
+- Examples: 3B is transmitted as **3B**.  
+AG 25 is transmitted as **AG 25**.
+- C17 3.4 A number that includes a fraction shall be transmitted with the fraction linked to the whole number by a single hyphen.
+- Examples: For 1¾, transmit **1-3/4**, and not **13/4**.  
+For ¾ 8, transmit **3/4-8**, and not **3/48**.  
+For 363½ 4 5642, transmit **363-1/2 4 5642**, and not **3631/2 4 5642**.
+
+#### II. General provisions for transmission of telegrams
+
+##### 1 Calling
+
+- C18 1.1 Correspondence between two offices shall begin with the call signal. However, on circuits operated by start-stop apparatus, unless a different arrangement has been made, the apparatus must be connected in such a way that the transmitting office may start transmission of telegrams without a special call or previous notice to the receiving office.
+- C19 1.2 A transmission, once begun, may not be interrupted to give place to a communication of higher priority except in case of absolute urgency.
+- C20 1.3 Before transmission of a telegram actually begins, the condition of the circuit and the availability of the receiving apparatus shall be checked. To this end, in the systems that allow it, the signals *figure-shift* and *D* (or Who are you?) shall be transmitted. When the correspondent's answer-back code has been correctly received, the answer-back code of the transmitting station shall be transmitted.
+
+##### 2 Transmission with running series of numbers
+
+- C21 2.1 Each Administration shall have the right to number in series telegrams to be transmitted over international circuits. In each case it shall notify its intention to the Administrations concerned.
+- C22 2.2 The serial number shall be transmitted at the beginning in the numbering line. Administrations shall each decide as far as it is concerned, whether the office number shall be transmitted. If so, it will be included in the numbering line.
+- C23 2.3 When serial numbers are used, all telegrams shall be numbered in unbroken series. A special series may be used for each section or circuit by agreement between the Administrations concerned. This series shall then differ from the series used for the other sections or circuits by distinguishing figures or a prefix composed of letters.
+- C24 2.4 Offices in correspondence shall agree upon the start and finish of the series of numbers and upon the periodicity of the start of the cycle.
+- C25 2.5 In all cases, telegrams that are to be diverted shall receive new serial numbers.
+- C26 2.6 When the receiving office observes that a serial number is missing, it must inform the sending office at once in order that the necessary inquiries may be made.
+- C27 2.7 When it is necessary to strike out a serial number that has already been used, the transmitting office shall inform the receiving office by service advice.
+
+#### III. General provisions for reception
+
+- C28 1 When reception is unintelligible, the operator shall act according to the special rules given for the different methods of operation (see C49 to C55 and C79 to C87).
+- C29 2 If there is a discrepancy between the number of actual words shown in the preamble line and the number received or any other irregularities, the operator shall act according to the special provisions given for the different methods of operation (see C52 to C55 and Recommendation F.31).
+
+C30 3 When any discrepancy or irregularity does not arise from a mistake in transmission, the rectification can only be made by agreement reached, if necessary, by service advice between the office of origin and the office in correspondence. Failing such agreement, the number of words indicated by the office of origin or any other irregularity shall be admitted, the telegram being forwarded, meanwhile, with the service instruction "Correction to follow . . ." transmitted in the abbreviated form [example: **CTF . . . WORD(S)**], the meaning of which shall be indicated by the office of destination on the copy delivered to the addressee. The correction shall be requested by service advice from the office of origin by the office that has inserted the service instruction **CTF . . .**
+
+#### IV. Special provisions for point-to-point operations
+
+##### 1 Transmission of telegrams to tape-printing systems
+
+C31 1.1 The double hyphen (=), which is always preceded by a space but must never be followed by a space, shall be transmitted either to separate:
+
+C32 1.1.1 the preamble line from the service indications;
+
+C33 1.1.2 the service indications from each other;
+
+C34 1.1.3 the service indications from the address;
+
+C35 1.1.4 the office of destination from the preceding parts of the address;
+
+C36 1.1.5 the office of destination from the text;
+
+C37 1.1.6 the text from the signature.
+
+C38 1.2 Each telegram shall be terminated by a cross (+). The cross must always be preceded and followed by a space.
+
+C39 1.3 If the sending operator becomes aware of an error, he shall proceed as in C94.
+
+C40 1.4 Example of format to be used in tape-printing systems:
+
+**MOH143<sup>1</sup> KIEV 12 18 0830<sup>2</sup> =URGENT =KARL MUELLER  
+ROSSMARKT 13/1 =HAMBURG =WIR KOMMEN SCHON HEUTE  
+ABEND =KARIN +**
+
+<sup>1</sup> Distinguishing letters and/or serial number (see C21 to C27).
+
+<sup>2</sup> Preamble line, the parts referred to in A30 to A38.
+
+##### 2 Transmission of telegrams to page-printing systems
+
+C41 2.1 When page-printing teleprinters are used for reception, the transmitting office or offices should transmit traffic to the receiving office without error according to the layouts shown in the C46 to C48.
+
+C42 2.2 Every line must consist of not more than 69 printing characters (including spaces), except for the address in which lines should not exceed 43 (and preferably no more than 30) printing characters.
+
+C43 2.3 The transmitting operator should transmit each word as a whole and should avoid dividing words between the end of one line and the beginning of the next.
+
+C44 2.4 The sending office should eliminate errors before transmission.
+
+C45 2.5 When preparing telegrams in page format that may be circulated over the gentex network or via the telegram retransmission system, the additional provisions contained in C56 to C115 should be observed.
+
+C46 2.6 Example: Ordinary private telegram
+
+← ≡
+
+**ZCZC LPA264 LGE906 PLG408** ← ≡<sup>1</sup>
+
+**FRXX CO GBLG 020** ← ≡<sup>2</sup>
+
+**LONDON/LG 20 26 1405** ← ≡ ≡ ≡<sup>3</sup>
+
+**DUPONT** ← ≡
+
+**15 RUE DE LA REPUBLIQUE** ← ≡
+
+**NANTES** ← ≡ ≡ ≡
+
+**JOHN AND SUE LEAVE BY ROAD TODAY EXPECTED TO ARRIVE** ← ≡
+
+**EARLY TOMORROW** ← ≡
+
+**DAD** ← ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡<sup>4</sup>
+
+**NNNN**<sup>5</sup>
+
+<sup>1</sup> Distinguishing letters and/or serial number (C21 to C27).
+
+<sup>2</sup> The pilot line may be omitted when transmitting to systems that do not demand it.
+
+<sup>3</sup> Preamble line, the parts referred to in A30 to A38.
+
+<sup>4</sup> Minimum of five spaces before the signature.
+
+<sup>5</sup> Ten letter-shifts follow NNNN, except in relations that do not require them.
+
+C47 2.7 Example: POSTFIN telegram with postal service indications<sup>1</sup>
+
+← ≡
+
+**ZCZC AKW112 MDT8067** ← ≡
+
+**INBY CJ GBMT 024** ← ≡<sup>2</sup>
+
+**LONDON/MT 24 26 1130** ← ≡ ≡ ≡
+
+**POSTFIN** ← ≡
+
+**AVIS PAIEMENT** ← ≡
+
+**BOMBAY** ← ≡ ≡ ≡
+
+**MANDAT 2793 BRADFORD 10610 GB MOHD YOUNAS** ← ≡
+
+**500 (FIVE HUNDRED) RUPEES** ← ≡
+
+**MONSIEUR JEAN DE BIASE 74 APOLLO BUNDO** ← ≡
+
+**HAPPY BIRTHDAY** ← ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
+
+NNNN<sup>3</sup>
+
+<sup>1</sup> **POSTFIN** telegrams are under study within the UPU.
+
+<sup>2</sup> The pilot line may be omitted when transmitting to systems that do not demand it.
+
+<sup>3</sup> Ten letter-shifts follow **NNNN** except in relations that do not require them.
+
+C48 2.8 Example: POSTFIN telegram containing a postal cheque order
+
+← ≡
+
+**ZCZC ABC123 BBAA8371** ← ≡
+
+**FRPA CJ CHBX 018** ← ≡<sup>1</sup>
+
+**BERN/1/SCHANZENPOST 18/17 15 1105** ← ≡ ≡ ≡
+
+**POSTFIN** ← ≡
+
+**AVIS INSCRIPTION** ← ≡
+
+**PARIS** ← ≡ ≡ ≡
+
+**VIREMENT 34688 ANTON SCHMIDT 30-53998 BERNE** ← ≡
+
+**500 (CINQ CENTS) FRANCS FRANCAIS** ← ≡
+
+**PIERRE DUBOIS 56-231089** ←
+
+NNNN<sup>2</sup>
+
+<sup>1</sup> The pilot line may be omitted when transmitting to systems that do not demand it.
+
+<sup>2</sup> Ten letter-shifts follow **NNNN** except in relations that do not require them.
+
+##### 3 Reception
+
+C49 3.1 When reception is unintelligible the receiving operator shall interrupt the transmitting office or cause the transmission to be interrupted.
+
+C50 3.2 To interrupt transmission from an office, transmit a succession of letters **T** or figures **5** or, on duplex circuits, transmit a call followed by the abbreviation **BK** and an audible signal which may be repeatedly transmitted.
+
+C51 3.3 When interrupting the transmitting office, the reason for the interruption shall be given (paper mutilated, etc.) and the number of the last telegram correctly received (**LR . . .**) shall be indicated.
+
+C52 3.4 If there is a difference between the number of actual words shown in the preamble line and the number received, the operator shall send a service advice to the transmitting office, indicating the serial number of the telegram in question, the abbreviation **CK**, the number of words received, and the first character of each word. In telegrams with more than ten actual words, it is admissible to indicate each fifth or tenth actual word instead of the character of each word. In this case the indicated words shall be preceded by the abbreviation **FVS** (fives) or **TNS** (tens) respectively. For the words behind the last indicated fives or tens, the first character of each word shall be given. If the sending operator has simply made an error in transmitting the number of words, he shall reply by a
+
+service advice indicating and confirming the actual number of words; if not, he shall rectify by an appropriate service advice the passage found to be incorrect according to the words and/or character of the words received.
+
+- C53 3.5 In the case of reception by a tape-printing system, the reason for the interruption may also be followed by the last word, to which a question mark must be added, or the number of the last telegram correctly received (**LR . . .**).
+- C54 3.5.1 The sending operator shall go back and continue the transmission from that word or telegram, after having been instructed to continue by **GA, RPT AA . . .**, etc.
+- C55 3.6 In the case of reception by a page-printing system, the sending operator shall always go back and continue the transmission from the last telegram correctly received.
+
+#### V. Special provisions for gentex operations
+
+##### 1 General provisions
+
+- C56 1.1 The gentex network is made up of telegraph offices of the countries participating in the service (gentex offices), of switching centres and of telegraph channels connecting the offices to switching centres and the switching centres to one another. Either tape-printing or page-printing teleprinters are used for transmission and reception.
+- C57 1.2 When page-printing teleprinters are provided for the transmission and/or reception of telegrams the particular provisions and the format of C88 to C90 must be observed.
+
+##### 2 Answer-back codes
+
+- C58 2.1 The answer-back code used in the gentex service shall be in conformity with Recommendation F.21.
+
+##### 3 Responsibility of transmitting or receiving stations
+
+- C59 3.1 The operator in the calling station is primarily responsible for the transmission of telegrams. If a telegram fails to arrive or if its text is mutilated, he will have to prove that he has followed the correct procedure.
+- C60 3.2 He can provide this proof by producing the original of the telegram, the local record if there is one and by verifying that the called station's answer-back code was received without error.
+- C61 3.3 The operator manning a position is responsible for seeing that there is enough paper in the machine, that the inking system is fully serviceable, and that the machine is switched to *engaged* while the ribbon and paper are being replaced. Furthermore, the operator of the receiving station shall eliminate any erroneous passages.
+
+##### 4 Procedures before transmission of a telegram
+
+- C62 4.1 At the calling station, the telegram may be provided with a reference number, which will be transmitted before the preamble line and will serve as an additional means of identifying the telegram if required.
+
+- C63 4.2 To set up the call with the required office, the operator of the calling station proceeds, according to the rules of his network, to obtain the required number, which is made up of:
+- the prefix giving access to the called country from the calling station;
+  - the number of the called office.
+- C64 4.3 Having set up the call, the operator at the calling station brings into operation the answer-back device in the station obtained, together with that of his own station when these two operations are not automatically controlled by the equipment in the calling or called country. The operator at the calling station checks the answer-back code he obtains against that of the required office and, if they correspond, he then begins to transmit the telegram.
+- C65 4.4 If the answer-back code received is not the code expected, the reason may be one of the following:
+- C66 4.4.1 the answer-back code belongs to an overflow position which can receive the telegram; transmission of the telegram can therefore begin;
+- C67 4.4.2 a wrong station has been obtained. The operator sends the signal **BK**, gives the clearing signal, and again tries to put the call through to the office required.
+- C68 4.5 Should this fresh attempt end in reception of the answer-back code of a position which is not an overflow position and does not belong to the office required, the operator shall proceed in accordance with C76 and C77.
+- C69 4.6 If the calling station receives the busy signal, the call shall be repeated after approximately two minutes. If the second call is unsuccessful, a third call shall be made after a further two minutes. If the busy signal is again received, telegrams shall be diverted to that telegraph office in the same country shown in the routing list as the office required in such cases.
+- C70 4.7 When a call is sent to a gentex office in a country providing diversion to an overflow position, connection with the required gentex office or an overflow position may be delayed. The operator of the calling station is informed thereof by reception of **MOM**. He will then await subsequent routing of his call.
+
+##### **5 Transmission of telegrams**
+
+- C71 5.1 When communication has been established with the desired telegraph office or with an overflow position, the telegram shall be transmitted in the manner described in C31 to C40 or C88 to C90.
+- C72 5.2 After transmission of the telegram, the operator obtains the answer-back code of the called station and then transmits his own. The operator of the calling station then gives the clearing signal.
+- C73 5.3 For interconnection between a gentex office and a telegram retransmission centre see C102 to C115.
+- C74 5.4 When a calling station has several telegrams for the same office, once the calling station has made contact with that office, the operator checks the answer-back code in accordance with C64, and then transmits the telegrams one after the other taking into account C71 and, if appropriate, C102 to C115. In this case, one exchange of the answer-back codes takes place between the end of one telegram and the beginning of the following one.
+
+##### 6 Reception of telegrams
+
+- C75 6.1 The called station checks each telegram received in accordance with the provisions of A159 to A164. If correction is necessary a request must be sent by service advice to the transmitting office. When receiving from a telegram retransmission centre the request must be sent as prescribed in Recommendation F.31 (see 6.2/F.31).
+
+##### 7 Abnormal conditions before transmission
+
+- C76 7.1 Should the operator of a calling station notice, during the setting up of a call, anything that seems to him due to faulty lines or equipment, he shall give the clearing signal.
+- C77 7.2 After approximately two minutes, he shall try to call again. If, once again, there are abnormal conditions he shall give the clearing signal, record the abnormal conditions on the telegram or telegrams and dispose of it or them by an alternative route. He shall then report the fault.
+- C78 7.3 Should a mutilated answer-back code be received, or should there be no answer-back code at all, the operator shall give the clearing signal and proceed as in C77.
+
+##### 8 Abnormal conditions during transmission
+
+- C79 8.1 If the operator at the called station notes any errors in the text of a telegram that is being received, he shall send letters **T** or figures **5** repeatedly until transmission stops. He shall then send **MUT RPT AA . . .** [or possibly, the reference number (**SRL NR**) or the handing-in number (**TG NR**) of the first mutilated telegram when a series of telegrams is being received] and the last correctly received word or group. The operator at the calling station shall recommence transmission at the requested place.
+- C80 8.2 Should a completely mutilated text be received, including mutilation of the answer-back code of the calling station, an operator noticing this before the call is broken off shall stop the transmission by sending letters **T** or figures **5** repeatedly until transmission stops. He shall then send **MUT RPT ALL**.
+- C81 8.3 If the operator at the called station cannot stop a transmission, or if the text received when the transmission is resumed continues to be mutilated, he shall send the clearing signal.
+- C82 8.4 After transmission if the answer-back code of the called station is not received or is incorrectly received at the end of transmission of a telegram, the operator of the calling station then gives the clearing signal.
+- C83 8.5 The calling station then proceeds once more to call the required office and recommences transmission of the telegram including the service instruction **AMPLIATION** at the end of the preamble line.
+- C84 8.6 The procedure described under C83 above is also applied when the call is accidentally interrupted during transmission by the calling station.
+- C85 8.7 If a call is accidentally interrupted during transmission, or if a call has been cleared after transmission of **BK**, the called office holds the texts received until the calling office resumes transmission. If transmission is not resumed within twenty minutes, the called office sends a service advice to the calling office, requesting any corrections or repetitions that may be necessary.
+
+- C86 8.8 When a completely mutilated text is received, and the answer-back code of the calling station is also mutilated, if the call has already been cleared, the received text shall be kept for enquiry purposes. The name of the receiving station and the time of receipt shall be marked on the form. Since the receiving station cannot, in such circumstances, transmit a request to the transmitting station, the telegram will be lost if the transmitting station has failed to notice the fault.
+- C87 8.9 Shortage of paper can in certain teleprinters cause the clearing signal to be sent automatically. A break in the tape or faulty tape feed shall, where possible, give rise to a local signal if the clearing signal is not sent automatically.
+
+##### 9 Traffic between gentex offices equipped with page-printing teleprinters
+
+- C88 9.1 Provisions C41 to C48 or C89 and C90 should be followed, the format being slightly modified to meet the requirements of the gentex service.
+
+- C89 9.1.1 Example:
+
+☒ ← ≡<sup>1</sup>
+
+16250Z OSLO N ← ≡
+
+4071TC FFM D ← ≡
+
+ZCZC 18 ← ≡<sup>2</sup>
+
+NOOO CO DPFF 013 ← ≡<sup>3</sup>
+
+FRANKFURT AM MAIN/9 13/12 25 0935 ← ≡ ≡ ≡
+
+INTERFER ← ≡
+
+OSLO ← ≡ ≡ ≡
+
+ARRIVING WEDNESDAY KLM FLIGHT 308 KINDLY ← ≡
+
+ARRANGE HOTEL RESERVATION ← ≡
+
+JUDY ← ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡<sup>4</sup>
+
+NNNN ☒ ← ≡<sup>1,5</sup>
+
+16250Z OSLO N ← ≡
+
+4071TC FFM D
+
+<sup>1</sup> Method of operating in accordance with C65. The symbol ☒ indicates the *Who are you?* signal.
+
+<sup>2</sup> Transmission serial number.
+
+<sup>3</sup> The pilot line may be omitted when transmitting to systems that do not demand it.
+
+<sup>4</sup> Minimum of five spaces before the signature.
+
+<sup>5</sup> Ten letter-shifts follow NNNN except in relations that do not require them.
+
+- C90 9.2 Administrations may nevertheless mutually agree to ignore the provision that the transmission should be free of errors.
+
+##### 10 Interworking between tape-printing and page-printing teleprinters
+
+- C91 10.1 When tape-printing teleprinters are used to transmit page format, they should generally be equipped in accordance with Recommendation S.5 and operated in accordance with C41 to C48. When page-printing teleprinters are used to transmit towards tape-printing teleprinters, C41 to C48 or C89 and C90 should be followed.
+
+##### 11 Special transmission procedures for use with format converters and/or automatic error correction devices
+
+- C92 11.1 Besides the transmission procedure laid down in C71, it is admissible:
+- C93 11.1.1 that gentex offices equipped with tape-printing teleprinters may use the double hyphen (=, combination No. 22, figure case) whenever the carriage-return and line-feed signals (combinations Nos. 27 and 28) are used in the format C41 to C48 (notwithstanding C31 to C37). No space is shown between the double hyphen(s) and the following word. These offices will also have to transmit five spaces before the signature;
+- C94 11.1.2 that gentex offices, whether equipped with page- or tape-printing teleprinters, may signal **XXXXX** (at least five times the letter X without spacing) joined to the erroneous word, followed immediately by the retransmission correctly of the erroneous word.
+- C95 11.2 If a space has been transmitted after the erroneous word, the automatic error correction device will not suppress the error; if in this case error-free reception is necessary, the telegram will have to be cancelled by transmitting the expression **ANUL** space **ANUL** and ten double hyphens. The telegram in question must then be transmitted again including all the exchanges of answer-back codes.
+- C96 11.3 By mutual agreement between Administrations, the foregoing procedures may also be adopted when format converters or error-correcting devices are not employed in order to enable operators to observe a uniform transmission procedure.
+
+##### 12 Service advices (A) and use of codes
+
+- C97 12.1 When a telegram is sent on, marked **CTF**, the sending office shall be informed of the fact by a service advice (**A**).
+- C98 12.2 Service advices shall preferably make use of the codes listed in C101 and in the list of additional five letter codes which should be published as an Annex to the ITU Operational Bulletin.
+- C99 12.3 The codes listed in C101 shall also be used when, in exceptional circumstances, operators have to communicate while a call is still connected.
+- C100 12.4 Deleted.
+- C101 12.5 *Service codes and abbreviations to be used in gentex operation*
+
+| ABBREVIATION      | MEANING                 |
+|-------------------|-------------------------|
+| <b>ABS</b>        | Telegraph office closed |
+| <b>ADRS</b>       | Address                 |
+| <b>ANH</b>        | Congestion              |
+| <b>ANUL . . .</b> | Delete . . .            |
+
+|                   |                                                                          |
+|-------------------|--------------------------------------------------------------------------|
+| <b>BK</b>         | I cut off                                                                |
+| <b>CALL NR</b>    | National call number of a gentex office                                  |
+| <b>CCT</b>        | Circuit                                                                  |
+| <b>CFM</b>        | Please confirm/I confirm                                                 |
+| <b>CI</b>         | Conversation impossible                                                  |
+| <b>CK</b>         | Please check number of words                                             |
+| <b>CLA</b>        | Class of telegram                                                        |
+| <b>CRV</b>        | How do you receive?                                                      |
+| <b>CTF</b>        | Correction to follow                                                     |
+| <b>DBL</b>        | Double word(s)                                                           |
+| <b>DEB</b>        | Overflow position                                                        |
+| <b>DER</b>        | Out of order                                                             |
+| <b>DER MOM</b>    | Bad reception, do not cut off, we are testing the line                   |
+| <b>DETR . . .</b> | I am re-routing to . . ./Re-route to . . ./Alternative route             |
+| <b>DIF</b>        | Different                                                                |
+| <b>DTE</b>        | Date of handing-in                                                       |
+| <b>FIG</b>        | Figure(s)                                                                |
+| <b>FVS</b>        | Fives                                                                    |
+| <b>GA</b>         | You may transmit                                                         |
+| <b>IND</b>        | Answer-back code                                                         |
+| <b>INQ</b>        | Position specializing in the handling of service notes and advices       |
+| <b>LTR</b>        | Letter(s)                                                                |
+| <b>MNS</b>        | Minutes                                                                  |
+| <b>MOM</b>        | Please wait!                                                             |
+| <b>MOM PPR</b>    | Please wait! I have paper trouble                                        |
+| <b>MUT</b>        | Mutilated                                                                |
+| <b>NA BK</b>      | Correspondence with this telegraph office is not admitted.<br>I cut off. |
+| <b>NC</b>         | No circuit                                                               |
+| <b>NCH</b>        | Number changed                                                           |
+| <b>NOT R</b>      | Not received                                                             |
+| <b>NP</b>         | The called number is not/no longer in use                                |
+| <b>NR</b>         | Number                                                                   |
+| <b>OCC</b>        | Busy                                                                     |
+
+|                                         |                                                                                                          |
+|-----------------------------------------|----------------------------------------------------------------------------------------------------------|
+| <b>O/D</b>                              | Telegraph office of destination                                                                          |
+| <b>OK</b>                               | Agreed                                                                                                   |
+| <b>OMTD</b>                             | Omitted                                                                                                  |
+| <b>O/O</b>                              | Telegraph office of handing-in                                                                           |
+| <b>PBL</b>                              | Preamble of telegram                                                                                     |
+| <b>PPR</b>                              | Paper                                                                                                    |
+| <b>QGA</b>                              | May I transmit?                                                                                          |
+| <b>QOK</b>                              | Do you agree?                                                                                            |
+| <b>R . . .</b>                          | Received . . .                                                                                           |
+| <b>RAFSO</b>                            | Second application                                                                                       |
+| <b>RAP</b>                              | I shall call you again                                                                                   |
+| <b>RDI</b>                              | Redirected call                                                                                          |
+| <b>REF . . .</b>                        | With reference to . . .                                                                                  |
+| <b>ROUTE</b>                            | Route to . . ./I am routing to . . ./Route                                                               |
+| <b>RPFR</b>                             | Please prepare your reperforator                                                                         |
+| <b>RPFR TXT</b>                         | Prepare your reperforator because of long or difficult text or because of telegrams having the same text |
+| <b>RPT</b>                              | Repeat please/I repeat                                                                                   |
+| <b>RPT AA . . .</b>                     | Repeat all after . .                                                                                     |
+| <b>RPT AB . . .</b>                     | Repeat all before . .                                                                                    |
+| <b>RPT ALL</b>                          | Repeat the whole telegram                                                                                |
+| <b>RPT BN . . .</b>                     | Repeat all between . . . and . .                                                                         |
+| <b>RPT SRL NR . . .</b>                 | Repeat reference number given by the transmitting office . .                                             |
+| <b>RPT TG NR</b>                        | Repeat telegram number                                                                                   |
+| <b>RPT TXT</b>                          | Repeat text                                                                                              |
+| <b>RPT WA . . .</b>                     | Repeat word after . .                                                                                    |
+| <b>RPT WB . . .</b>                     | Repeat word before . .                                                                                   |
+| <b>SIG</b>                              | Signature                                                                                                |
+| <b>SRL NR</b>                           | Reference number given by a gentex transmitting office                                                   |
+| <b>SVIN</b>                             | Service indication                                                                                       |
+| <b>SVP</b>                              | Please                                                                                                   |
+| <b>T (in either shift)<br/>repeated</b> | Stop your transmission                                                                                   |
+| <b>TCHN</b>                             | Technical service/I shall advise the technical service                                                   |
+| <b>TEST MSG</b>                         | Please send a test message                                                                               |
+
+|              |                                                           |
+|--------------|-----------------------------------------------------------|
+| <b>TG</b>    | Telegram                                                  |
+| <b>TG NR</b> | Telegram number given by the handing-in office            |
+| <b>TNS</b>   | Tens                                                      |
+| <b>TPLE</b>  | Triple word(s)                                            |
+| <b>TPR</b>   | Teleprinter                                               |
+| <b>TXT</b>   | Text                                                      |
+| <b>UTCOD</b> | Use the gentex code                                       |
+| <b>W</b>     | Word(s)                                                   |
+| <b>WEFXU</b> | Waiting reply to our service advice                       |
+| <b>WTG</b>   | We are waiting/I am waiting                               |
+| <b>XXXXX</b> | Error signal                                              |
+| <b>+?</b>    | I have finished my transmission. Do you wish to transmit? |
+
+#### **VI. Interworking between the telegram retransmission system and the gentex network**
+
+- C102 1.1 The special provisions for gentex operation (C56 to C101), except as specified below, will be applied to traffic between gentex telegraph offices and telegram retransmission centres in both directions.
+- C103 1.2 Administrations will designate the gentex offices open to traffic with telegram retransmission centres and will publish this information in the *Routing Table for Offices Taking Part in the Gentex Service* [6] (Recommendation F.93) and in the *List of Indicators for the Telegram Retransmission System and Telex Network Identification Codes* [7] (Recommendations F.32 and F.69).
+- C104 1.3 The format and arrangements described in Recommendation F.31 shall apply except that channel sequence numbering is not applicable in either direction on the channels connecting the two systems.
+- C105 1.4 In the direction gentex to telegram retransmission system, the telegram identification group, which will immediately follow the start-of-message signal, shall be composed of two letters identifying the originating country or Administration (in accordance with Recommendations F.32 and F.69), the call-number of the gentex office followed by one or two letters identifying the gentex position and the serial number of the telegram which that position is transmitting. The group shall not include a space nor exceed 15 printing characters.
+- C106 1.5 In the direction telegram retransmission system to gentex, all preceding channel sequence numbers and the telegram identification group will be transmitted.
+- C107 1.6 The transmission of each telegram should be immediately preceded and followed by the exchange of the answer-back codes.
+- C108 1.7 By mutual agreement of the Administrations concerned, the gentex call number of the office of destination may be entered into the pilot line immediately following the number of chargeable words and separated from it by a space.
+
+- C109 1.8 *Exceptions to provisions C31 to C101*
+- C110 1.8.1 The signals, service codes and abbreviations (bell signal, **RPFR**, **MOM**, etc.) proper to the gentex service to announce or to draw attention to an abnormal situation must not be used.
+- C111 1.8.2 Except where otherwise agreed, only the clearing signal may be used to interrupt transmission. In this case, the calling station shall recommence transmission at the beginning of the interrupted telegram.
+- C112 1.8.3 An error noted after the end-of-message signal **NNNN** has been sent will be corrected by sending a service advice.
+- C113 1.8.4 Except where otherwise agreed, the answer-back code of the receiving station correctly received at the end of transmission serves as proof of reception for all classes of telegrams.
+- C114 1.8.5 Repetition of a telegram that has already been completely transmitted will be effected in the form of a service advice (see D25 to D32 and D39).
+- C115 1.9 *Example of the recommended format for transmission between the gentex network and the telegram retransmission system*
+
+☒ ← ≡
+
+**1299RC NYC UI** ← ≡
+
+**4144A DARMST D** ← ≡
+
+**ZCZC DP4144A154** ← ≡<sup>1</sup>
+
+**UINY HL DPDA 027** ← ≡<sup>2</sup>
+
+**JUGENHEIM A D BERGSTRASSE 27/24 12 1926** ← ≡ ≡ ≡
+
+**LT** ← ≡
+
+**MISS GISELLA COHEN** ← ≡
+
+**67 BROADSTREET** ← ≡
+
+**NEWYORK(10004)** ← ≡ ≡ ≡
+
+**1000 DOLLARS CABLED TO NEWYORK THROUGH SWISS** ← ≡
+
+**BANK CORPORATION STOP PLEASE CABLE IF NOT** ← ≡
+
+**RECEIVED LOVE** ← ≡
+
+**DADDY** ← <sup>3</sup>
+
+NNNN ← ≡<sup>4,5</sup>
+
+1299RC NYC UI ← ≡
+
+4144A DARMST D
+
+- 1 In the direction gentex to telegram retransmission system, only the telegram identification group shall be transmitted. In the direction telegram retransmission system to gentex, all preceding channel sequence numbers and the telegram identification group will be transmitted.
+- 2 The pilot line may be omitted when transmitting to systems that do not demand it.
+- 3 Minimum of five spaces before the signature.
+- 4 Ten letter-shifts follow NNNN, except in relations that do not require them.
+- 5 The symbol  $\boxtimes$  indicates the *Who are you?* signal.
+
+### **DIVISION D** **TELEGRAPH SERVICE CORRESPONDENCE**
+
+#### **I. Telegraph service correspondence**
+
+##### **1 Definitions**
+
+- D1 1.1 *Service telegrams* are telegrams that relate to public international telecommunication and are exchanged between:
+- D2 1.1.1 Administrations;
+- D3 1.1.2 Recognized operating agencies;
+- D4 1.1.3 Administrations and recognized operating agencies;
+- D5 1.1.4 Administrations and recognized operating agencies on the one hand and the Secretary-General of the ITU on the other hand.
+- D6 1.2 *Service advices* relate to details of service or to the working of circuits and telegraph offices and to transmission of traffic. They shall be exchanged between telegraph offices. They may also be initiated by the sender or addressee of any telegram to give instructions or to obtain information about that telegram.
+
+#### **II. Service telegrams and service advices**
+
+##### **1 General provisions**
+
+- D7 1.1 Service telegrams and service advices must be used only where essential and must be worded as briefly as possible. Telegraph offices and all persons authorized to use service telegrams shall take all necessary steps to restrict, so far as practicable, the number and length of those telegrams (see C98).
+- D8 1.2 Service telegrams may be exchanged between Administrations and recognized operating agencies on the one hand and the Secretary-General of the ITU, the Chairman of the Administrative Council of the ITU, the Director of the TSB, the Director of the BR and all persons authorized to use service telegrams on the other hand relating to the official business of the ITU.
+- D9 1.3 They shall be expressed in any of the working languages of the ITU<sup>5</sup> unless the Administrations concerned have agreed to use another language.
+- D10 1.4 Service telegrams and service advices shall be denoted by the service indication: **A**.
+- D11 1.5 The priority of transmission of service telegrams and service advices is shown in A136 to A144.
+
+---
+
+<sup>5</sup> The possible difficulties that might arise for certain Administrations due to the use of Spanish language in service advices will be considered further by Study Group 2.
+
+##### **2 Service telegrams**
+
+- D12 2.1 Service telegrams must contain in the preamble line the name of the office of origin, the number of actual words and the date and time of issue or handing in. Service telegrams may have a signature (see D40).
+- D13 2.2 Service telegrams must bear a registered address (see A77).
+
+##### **3 Service advices**
+
+###### **3.1 General provisions**
+
+- D14 3.1.1 The object of a service advice concerning a telegram already transmitted or in course of transmission is in most cases either to correct an error or to give instructions about the telegram. Such service advices are initiated by one of the offices having taken part in the transmission of the original telegram.
+- D15 3.1.2 During the minimum period for preservation of records, after first, if necessary, establishing their status and identity, the sender or the addressee (or their authorized representative) of any telegram that has been transmitted may, by service advice, either:
+- a) give instructions as to the delivery of the telegram following receipt of a service advice notifying its non-delivery; or
+  - b) have information obtained as to the identity of the sender.
+
+###### **3.2 Procedure**
+
+###### **3.2.1 End-to-end servicing**
+
+- D16 3.2.1.1 End-to-end servicing is a mode of operation in which the service advices are passed between the office of origin and the office of destination of the relevant telegram without interception at transit offices for the purposes of adding the serial and/or the channel sequence numbers of the original telegram as references.
+- D17 3.2.1.2 This mode of operation should be used whenever practicable.
+
+###### **3.2.2 Follow-on service advices**
+
+- D18 3.2.2.1 A follow-on service advice is a voluntary correction or inquiry initiated by the office of origin of the subject telegram. The originating office shall quote as reference the following particulars of the original telegram:
+- D19 a) the serial numbers shown in the numbering line together with the date (the number(s) and date in one group separated by a fraction bar);
+- D20 b) the service indications (if any);
+- D21 c) the name of the addressee;
+- D22 d) the address (excluding the office of destination);
+- D23 e) the signature (if any).
+- D24 3.2.2.2 The service advice should, as far as practicable, be forwarded on the same route as the original telegram. Transit offices may add their own serial number to the references given.
+
+###### **3.2.3 Return service advices**
+
+- D25 3.2.3.1 A return service advice is a notification or an enquiry (request service advice) initiated by the office receiving a telegram or a reply (reply service advice) to a service advice received.
+- D26 3.2.3.2 Return service advices (except reply service advices, see D30) shall quote as references the following particulars of the original telegram:
+- D27 a) all the serial numbers shown in the numbering line together with the date (the number(s) and date in one group separated by a fraction bar);
+- D28 b) service indications (if any);
+- D29 c) the name of the addressee.
+- D30 3.2.3.3 In reply service advices, the reference numbers and the date should be those of the request service advice followed by a space and the references of the subject telegram given in the request service advice.
+- D31 3.2.3.4 Return service advices shall be addressed to the office of origin of the subject telegram or the request service advice.
+- D32 3.2.3.5 Any transit office that can, without inconvenience or delay, collect the information needed for acting on the service advice shall do so; otherwise, it shall send the service advice on to its destination.
+
+##### **3.3 Wording**
+
+- D33 3.3.1 Service advices must contain in the preamble line the name of the office of origin, the number of actual words and the date and time of issue (see D41).
+- D34 3.3.1.1 Offices may add to the name of the office of origin the name, in abbreviated form, of the branch issuing the service advice.
+- D35 3.3.1.2 The address part of a service advice shall include the service indication **A** and the name of the office of destination with, if necessary, the additions mentioned in D34 if any (see D42).
+- D36 3.3.2 The text of a service advice shall quote all particulars necessary to facilitate the tracing of the subject telegram in accordance with D18 to D23 and D25 to D30.
+- D37 3.3.3 Service advices shall preferably make use of the codes listed in the ITU Operational Bulletin (for general use) or in C101 (mainly for gentex operation). Additional codes may be used by bilateral agreement.
+- D38 3.3.4 Examples of format and wording of service advices are shown in D41 to D45.
+
+###### **3.4 Repetition of a telegram**
+
+- D39 3.4.1 Where a repetition of an individual telegram is required by an office using the special provisions for the telegram retransmission system, the request shall be included in a service advice to the office sending the series (or the office of origin, if appropriate). The repetition should be included in the text of a reply service advice deleting any start-of-message and end-of-message signals on the subject telegram.
+
+#### III. Examples of format and wording of service correspondence
+
+D40 Service telegram (see D12 and D13)
+
+← ≡
+
+**ZCZC ALI402 SVC711** ← ≡
+
+**PCSV CN HXSV 000** ← ≡
+
+**HONGKONG x 6 0838** ← ≡ ≡ ≡
+
+**A** ← ≡
+
+**INOCRAM** ← ≡ ≡ ≡
+
+**LISBON** ← ≡ ≡ ≡
+
+**text** ← ≡
+
+**signature** ← ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
+
+NNNN (ten letter-shifts)
+
+D41 Service advice (see D33)
+
+← ≡
+
+**ZCZC GHA444 SVC529** ← ≡
+
+**GBBM CN HXSV 000** ← ≡
+
+**HONGKONG x 6 0840** ← ≡ ≡ ≡
+
+**A** ← ≡
+
+**BIRMINGHAM** ← ≡ ≡ ≡
+
+**text** ← ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
+
+NNNN (ten letter-shifts)
+
+D42 Service advice (see D34 and D35)
+
+← ≡
+
+**ZCZC LBA123 SG42** ← ≡
+
+**INBY CN GBLB 000** ← ≡
+
+**LONDON/MRC x 4 1030** ← ≡ ≡ ≡
+
+**A** ← ≡
+
+**BOMBAY** ← ≡ ≡ ≡
+
+**text** ← ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
+
+NNNN (ten letter-shifts)
+
+x indicates number of actual words.
+
+D43 Advice of non-delivery (see A191)
+
+← ≡
+
+**ZCZC ASV632 LHZ221 QLH53** ← ≡
+
+**GJBA CN GBLH 000** ← ≡
+
+**LONDON/LH 7 19 1841** ← ≡ ≡ ≡
+
+**A** ← ≡
+
+**BAHRAIN** ← ≡ ≡ ≡
+
+**ZLH082/VSA197/COF5259/19TH JOHNSTON ← ≡**  
+**14/A VICTORIASTREET RUCOS ←**
+
+NNNN (ten letter-shifts)
+
+D44 Correction of address (see A194)
+
+← ≡
+
+**ZCZC ZLH971 VSA197 LD39 ← ≡**
+
+**GBLH CN GJBA 000 ← ≡**
+
+**BAHRAIN 8 20 1005 ←**
+
+**A ← ≡**
+
+**LONDON/LH ←**
+
+**ASV632/LHZ221/QLH53/19TH ZLH082/VSA197/COF5259/19TH ← ≡**  
+**JOHNSTON JEHAT 144/A VICTORIASTREET ←**
+
+NNNN (ten letter-shifts)
+
+D45 Non-delivery problem solved (see A198)
+
+← ≡
+
+**ZCZC HGA456 LDC222 QLD12 ← ≡**
+
+**HXSV CN GBLD 000 ← ≡**
+
+**LONDON/LD 5 19 1145 ←**
+
+**A ← ≡**
+
+**HONGKONG ←**
+
+**CLD234/GHB197/CA2653/18TH SCHMIDT PYSAT ←**
+
+NNNN (ten letter-shifts)
+
+### DIVISION E
+
+### OPERATIONAL PROVISIONS APPLYING TO INTERNATIONAL FACSIMILE TRANSMISSIONS OF TELEGRAMS
+
+#### 1 General provisions
+
+- E1 1.1 This division complements the general and service provisions for the International Public Telegram Service in Divisions A and D. It defines the recommended arrangements where facsimile transmission links, rather than printing telegraph systems (Division C) or Morse and sounder working (Division B), are used to carry telegrams internationally.
+- E2 1.2 In order to meet the specific possible conditions applying to international facsimile transmission of telegrams, for the purposes of this Recommendation, the term *telegram* should be considered as being a message:
+- that is, in principle, word-based (see A115 to A132);
+  - that would normally be capable of being character-coded in accordance with A15 to A22.
+- E3 1.3 On the international path a distinction is made between the international bureaufax and telegrams services. In this Division, rather than facsimile providing specific service features perceived by the user (as in bureaufax), it is merely the technical means of transmission of a telegram on part or all of the international path<sup>6</sup>.
+
+#### 2 Preparation of telegrams for transmission
+
+- E4 2.1 In principle, the provisions in A12 to A132 apply relating to the preparation and handing in of telegrams and to the counting of words, but the provisions and variations in E5 to E11 below apply where bilaterally agreed.
+- E5 2.2 The telegram shall contain:
+- a heading (A27 to A38);
+  - an address part (A39 to A100); and
+  - a text part (A101 to A104).
+- E6 2.3 The arrangements of these parts (and hence their order of transmission by facsimile) may vary, depending for example on the structure of the forms for accepting telegrams in the origin country. However, this arrangement should facilitate delivery at the destination and provide a clear presentation to the addressee.
+- E7 2.4 A facsimile transmittal sheet, as defined in Recommendation F.170, may be used.
+- E8 2.5 Where the form accepted from the originator is transmitted internationally by facsimile, the general provisions in Recommendation F.170 (clause 2/F.170) should be applied, regarding page, size, margins, contrast, adequate definition and colours or
+
+---
+
+<sup>6</sup> Nevertheless, the bureaufax and telegram services for serve similar market needs. Hence, as noted in Recommendation F.18, harmonization of the bureaufax and telegram services has a number of advantages. However, the methods and degrees of harmonization depend to a large extent on national implementation which is a matter for the ROAs and/or service providers concerned. (See Recommendation F.170 regarding the operational aspects of the intentional bureaufax service.)
+
+half-tones in the original. it is the sending office's responsibility to ensure that these conditions are met to enable a clear black and white reproduction on reception.
+
+E9 2.6 Where these conditions are not met, the telegram should be refused. The bureaufax service instruction **RE** (*risques expediteur or sender's risk*) should not be used in the telegram service.
+
+E10 2.7 Where the end-to-end transmission is by facsimile, the contents of a telegram may also contain graphic or other characters outside the normal character set of telegrams (A15 to A22). In cases of end-to-end transmission by facsimile, special bilateral agreements may apply to harmonize the treatment of such telegrams for word-counting and related purposes.
+
+E11 2.8 The provisions relating to long telegrams (A105 to A113) may be waived.
+
+#### 3 **Routing and retransmission of telegrams**
+
+E12 3.1 While A133, A133A and A135 apply, it should be noted that the choice of international transmission mode is not necessarily the same in each direction. For example, in any international relation it may be agreed that the facsimile be used in one direction and printing telegraph in the other.
+
+E13 3.2 Appropriate steps should be taken to provide reasonable protection against the loss, corruption or excessive delay of telegrams transmitted internationally by facsimile.
+
+#### 4 **Delivery at destination**
+
+E14 4.1 The delivery of telegrams at destination should be generally in accordance with A172 to A200, noting the possible operational difficulties in providing telex (**TLXx**) delivery of telegrams received by facsimile.
+
+E15 4.2 However, where bilaterally agreed, the bureaufax service provisions (clause 6/F.170) may be applied for the delivery at destination of telegrams transmitted internationally by facsimile.
+
+#### 5 **Service correspondence**
+
+E16 5.1 Division D lays down the provisions concerning service correspondence in the international public telegram service.
+
+E17 5.2 Provided the provisions on reciprocal arrangements in Recommendation F.17 are respected, the bureaufax service (clause 7/F.170) may be used to handle service correspondence.
+
+#### 6 **Archives**
+
+E18 6.1 While A266 normally requires retention of copies of telegrams for six months, this period may be reduced to [four] weeks (from the date of handing in) for telegrams accepted or transmitted by facsimile.
+
+E19 6.2 Along the lines indicated in clause 7/F.170 for the bureaufax service, the individual service providers concerned may agree on suitable arrangements other than those in A166 to A273 and E18 to answer any queries subsequent to the transmission of a telegram by facsimile, in particular any queries affecting the international accounts.
+
+## **Bibliography**
+
+- [1] International Telecommunication Convention, Nairobi, 1982.
+- [2] List of telegraph offices open for international service, ITU, Geneva.
+- [3] List of coast stations, List IV, Part IV, Volume I, ITU, Geneva.
+- [4] General Information relating to the Operation of the International Telegraph, Data Transmission and Telematic Services, (facsimile, teletex, videotex, etc.) ITU, Geneva.
+- [5] Codes and abbreviations for the use of the international telecommunication services, ITU, Geneva.
+- [6] Routing table for offices taking part in the gentex service, ITU, Geneva.
+- [7] List of indicators for the telegram retransmission system and telex network identification codes, ITU, Geneva.
+
+# ITU-T RECOMMENDATIONS SERIES
+
+|                 |                                                                                                                                |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of the 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                                              |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                |
+| Series G        | Transmission systems and media, digital systems and networks                                                                   |
+| Series H        | Audiovisual and multimedia systems                                                                                             |
+| Series I        | Integrated services digital network                                                                                            |
+| Series J        | 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                                                                                              |
+| Series Z        | Programming languages                                                                                                          |
\ No newline at end of file
diff --git a/marked/F/T-REC-F.110-199607-I_PDF-E/raw.md b/marked/F/T-REC-F.110-199607-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..2a758b4458eea5b8838e4bd436557753fece5756
--- /dev/null
+++ b/marked/F/T-REC-F.110-199607-I_PDF-E/raw.md
@@ -0,0 +1,952 @@
+
+
+![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt striking across it, symbolizing global communication.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.110**
+
+(07/96)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Mobile service – Mobile services and multdestination  
+satellite services
+
+---
+
+**Operational provision for the maritime mobile  
+service**
+
+ITU-T Recommendation F.110
+
+(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 F.110 was revised by ITU-T Study Group 1 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 19th of July 1996.
+
+---
+
+# NOTE
+
+In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+© ITU 1996
+
+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 the ITU.
+
+# CONTENTS
+
+|                                                                                                                                                | <i>Page</i> |
+|------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| DIVISION A – GENERAL.....                                                                                                                      | 1           |
+| 1 Scope.....                                                                                                                                   | 1           |
+| 2 References.....                                                                                                                              | 1           |
+| 3 Definitions.....                                                                                                                             | 2           |
+| 4 Order of priority .....                                                                                                                      | 2           |
+| 5 Limitations .....                                                                                                                            | 3           |
+| 6 Service hours .....                                                                                                                          | 3           |
+| DIVISION B – RADIOTELEGRAMS .....                                                                                                              | 4           |
+| 1 Preparation and handing-in of radiotelegrams .....                                                                                           | 4           |
+| 1.1 Indication of station of origin .....                                                                                                      | 4           |
+| 1.2 Use of accounting authority identification codes by mobile stations .....                                                                  | 4           |
+| 1.3 Time of handing-in .....                                                                                                                   | 4           |
+| 1.4 Address .....                                                                                                                              | 4           |
+| 2 Counting of words.....                                                                                                                       | 5           |
+| 3 Routing of radiotelegrams.....                                                                                                               | 5           |
+| 4 Transmission of radiotelegrams .....                                                                                                         | 5           |
+| 4.1 Routine repetition .....                                                                                                                   | 5           |
+| 4.2 Doubtful reception .....                                                                                                                   | 6           |
+| 4.3 Long distance radiocommunications .....                                                                                                    | 6           |
+| 4.4 Routine retransmission by mobile stations .....                                                                                            | 7           |
+| 4.5 Period of retention of radiotelegrams at land stations.....                                                                                | 7           |
+| 5 Advice of non-delivery .....                                                                                                                 | 8           |
+| 6 Radiomarine letters .....                                                                                                                    | 8           |
+| 7 Special services .....                                                                                                                       | 8           |
+| 8 Special conditions relating to the maritime mobile-satellite service.....                                                                    | 8           |
+| DIVISION C – RADIOTELEX .....                                                                                                                  | 9           |
+| 1 General.....                                                                                                                                 | 9           |
+| 1.1 Routing of calls.....                                                                                                                      | 9           |
+| 1.2 Information to be supplied, as necessary by the calling party .....                                                                        | 9           |
+| 1.3 Call duration .....                                                                                                                        | 9           |
+| 1.4 Validity of requests.....                                                                                                                  | 10          |
+| 1.5 Exchange of radiotelegrams by radiotelex.....                                                                                              | 10          |
+| 2 Traffic from mobile stations to subscribers of the international telex service .....                                                         | 10          |
+| 2.1 Automatic operation .....                                                                                                                  | 10          |
+| 2.2 Single-operator operation .....                                                                                                            | 10          |
+| 2.3 Semi-automatic operation .....                                                                                                             | 10          |
+| 2.4 Manual operation.....                                                                                                                      | 10          |
+| 2.5 Store-and-forward service .....                                                                                                            | 10          |
+| 2.6 Operational procedures.....                                                                                                                | 11          |
+| 3 Traffic from subscribers of the international telex service-to-mobile stations.....                                                          | 11          |
+| 3.1 Fully automatic operation .....                                                                                                            | 11          |
+| 3.2 Single-operator operation (direct access by a calling telex subscriber to a foreign land station) .....                                    | 11          |
+| 3.3 Semi-automatic operation (access by a calling subscriber to one's international centre for the establishment of a direct connection) ..... | 12          |
+| 3.4 Manual operation.....                                                                                                                      | 12          |
+| 3.5 Store-and-forward.....                                                                                                                     | 12          |
+
+|                                    | <i>Page</i>                                                                                                                                |    |
+|------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|----|
+| 4                                  | Traffic exchanged between mobile stations .....                                                                                            | 13 |
+| 5                                  | Radiomaritime telex letter .....                                                                                                           | 13 |
+| 5.1                                | Definition .....                                                                                                                           | 13 |
+| 5.2                                | Operational procedures .....                                                                                                               | 13 |
+| 6                                  | Special provisions for the maritime mobile-satellite telex service .....                                                                   | 13 |
+| 6.1                                | Procedures for calls from subscribers of the international telex service to a mobile earth station ...                                     | 13 |
+| 6.2                                | Procedures for calls from MES to subscribers of the international telex service .....                                                      | 13 |
+| 6.3                                | Procedures for MES-to-MES calls .....                                                                                                      | 14 |
+| 6.4                                | Instructions for maritime mobile-satellite telex service .....                                                                             | 14 |
+| DIVISION D – RADIOTELEPHONE .....  |                                                                                                                                            | 15 |
+| 1                                  | General .....                                                                                                                              | 15 |
+| 1.1                                | Language to be used .....                                                                                                                  | 15 |
+| 1.2                                | Priority .....                                                                                                                             | 15 |
+| 1.3                                | Routing of calls .....                                                                                                                     | 15 |
+| 1.4                                | Information to be supplied, as necessary, by the calling party .....                                                                       | 15 |
+| 1.5                                | Call duration .....                                                                                                                        | 16 |
+| 1.6                                | Validity of requests .....                                                                                                                 | 16 |
+| 1.7                                | Exchange of radiotelegrams by radiotelephony .....                                                                                         | 16 |
+| 2                                  | Traffic from mobile stations to telephone subscribers .....                                                                                | 16 |
+| 2.1                                | Automatic operation .....                                                                                                                  | 16 |
+| 2.2                                | Single-operator operation .....                                                                                                            | 16 |
+| 2.3                                | Semi-automatic operation .....                                                                                                             | 17 |
+| 2.4                                | Manual operation .....                                                                                                                     | 17 |
+| 2.5                                | Operational procedures .....                                                                                                               | 17 |
+| 3                                  | Traffic from telephone subscribers to mobile stations .....                                                                                | 17 |
+| 3.1                                | Fully automatic operation .....                                                                                                            | 17 |
+| 3.2                                | Single-operator operation (direct access by a calling subscriber to a foreign land station) .....                                          | 17 |
+| 3.3                                | Semi-automatic procedure (access by a calling subscriber to one's international centre for the establishment of a direct connection) ..... | 18 |
+| 3.4                                | Manual operation .....                                                                                                                     | 18 |
+| 4                                  | Traffic exchanged between mobile stations .....                                                                                            | 19 |
+| 5                                  | Special provisions for the maritime mobile-satellite telephone service .....                                                               | 19 |
+| 5.1                                | Procedures for calls from subscribers of a terrestrial telephone network to a mobile earth station ..                                      | 19 |
+| 5.2                                | Procedures for calls from MES to subscribers of the terrestrial telephone networks .....                                                   | 19 |
+| 5.3                                | Procedures for MES-to-MES calls .....                                                                                                      | 20 |
+| 5.4                                | Instruction for maritime mobile-satellite telephone service .....                                                                          | 20 |
+| DIVISION E – RADIOTELEXOGRAM ..... |                                                                                                                                            | 21 |
+| 1                                  | General .....                                                                                                                              | 21 |
+| 1.1                                | Definition .....                                                                                                                           | 21 |
+| 1.2                                | Provision of service .....                                                                                                                 | 21 |
+| 1.3                                | Validity of requests .....                                                                                                                 | 21 |
+| 2                                  | Operational procedures .....                                                                                                               | 21 |
+| Bibliography .....                 |                                                                                                                                            | 22 |
+
+# **OPERATIONAL PROVISION FOR THE MARITIME MOBILE SERVICE**
+
+*(revised in 1996)*
+
+## **DIVISION A – GENERAL**
+
+### **1 Scope**
+
+**A1 1.1** This Recommendation provides for all aspects of operation of the radiotelegram service, the radiotelex service, the radiotelephone service and the radiotelexogram service in terms of both communications via maritime mobile satellite, and radio media of HF, MF, VHF and UHF<sup>1)</sup>.
+
+### **2 References**
+
+**A2 2.1** 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.
+
+- CCITT Recommendation E.105 (1992), *International telephone service*.
+- ITU-T Recommendation E.141 (1993), *Instructions for the international telephone service*.
+- CCITT Recommendation E.164 (1991), *Numbering plan for the ISDN era*.
+- CCITT Recommendation F.1 (1992), *Operational provisions for the international public telegram service*.
+- CCITT Recommendation F.17 (1992), *Operational aspects of service communications*.
+- CCITT Recommendation F.60 (1992), *Operational provisions for the international telex service*.
+- ITU-T Recommendation F.69 (1994), *The international telex service – Service and operational provisions of telex destination codes and telex network identification codes*.
+- ITU-T Recommendation F.72 (1993), *The international telex service – General principles and operational aspects of a store and forward facility*.
+- CCITT Recommendation F.111 (1991), *Principles of service for mobile systems*.
+- CCITT Recommendation F.120 (1988), *Ship station identification for VHF/UHF and maritime mobile-satellite services*.
+- ITU-T Recommendation D.90 (1995), *Charging, billing, international accounting and settlement in the maritime mobile service*.
+
+---
+
+<sup>1)</sup> This Recommendation constitutes part of a *Manual for Use by the Maritime Mobile and Maritime Mobile-Satellite Services* defined in *Radio Regulations*.
+
+### 3 Definitions
+
+- A3 3.1 For the purposes of this CCITT Recommendation, the following terms have the meanings defined below:
+- A4 3.1.1 **controlling operator:** The controlling operator is the first land-based operator handling the radiotelegram, radiotelex call or radiotelephone call in the direction from the mobile station.
+- A5 3.1.2 **accounting authority identification code:** An accounting authority identification code is assigned to each accounting authority (defined in the *International Telecommunication Regulations* [1]). In effect the accounting authority acts as a billing intermediary between mobile stations and ROAs.
+- A6 3.1.3 **recognized operating agency (ROA):** The term is defined in *the International Telecommunication Constitution* (Geneva, 1992) [2]. For the purpose of this CCITT Recommendation an ROA is, in effect, any individual, company, corporation or governmental agency that operates an international telecommunication service to carry public correspondence (as defined in the Constitution). Each ROA is authorized by an ITU Member, which imposes certain obligations on the ROA. (For further details, see the *Constitution*.)
+- A7 3.1.4 **land stations:** A station in the mobile service not intended to be used while in motion.
+- A8 3.1.5 **land earth station:** An earth station in the mobile-satellite service located at a specified fixed point or within a specified inland area to provide a feeder link for the mobile-satellite service.
+- A9 3.1.6 **mobile stations:** A station in the mobile service intended to be used while in motion or during halts at an unspecified point.
+- A10 3.1.7 **mobile earth station:** An earth station in the mobile-satellite service intended to be used while in motion or during halts at unspecified points.
+- A11 3.1.8 The term *land station/land earth station* and *mobile station/mobile earth station* should imply *coast station/coast earth station* and *ship station/ship earth station*, respectively used in the *Radio Regulations* [3].
+- A12 3.1.9 **ship station identity:** Ship's identification  $X_1, X_2 \dots X_n$  identifying the ship uniquely. The ship station identity may be transmitted on the radio path.
+- A13 3.1.10 **coast station identity:** The coast station identification  $X_1, X_2 \dots X_n$  transmitted on the radio path.
+- A14 3.1.11 **mobile station number:** The number that identifies a mobile station for access from a public network and forms part of the international number to be dialled or keyed by a public network subscriber.
+
+### 4 Order of priority
+
+- A15 4.1 The order of priority for communications in the maritime mobile service shall be as follows, except where impracticable in a fully automated system in which, nevertheless, communications described in A16 shall receive priority:
+- A16 a) distress calls, distress messages and distress traffic;
+- A17 b) communications preceded by the urgency signal;
+
+- A18 c) communications preceded by the safety signal;
+- A19 d) communications relating to radio direction-finding;
+- A20 e) communications relating to the navigation and safe movement of aircraft engaged in search and rescue operations;
+- A21 f) communications relating to the navigation, movements and need of ships, aircraft and weather observations messages destined for an official meteorological service;
+- A22 g) radiotelegrams relative to the application of the United Nations Charter (**ETATPRIORITE**);
+- A23 h) government radiotelegrams with priority (**ETATPRIORITE**) and government calls for which priority has been expressly requested;
+- A24 i) ordinary private radiotelegrams and **RCT** radiotelegrams for which urgent transmission and delivery has been requested;
+- A25 j) service communications relating to the operation<sup>2)</sup> of the telecommunication service or to communications previously exchanged;
+- A26 k) government communications other than those shown in A29 ordinary private communications and **RCT** radiotelegrams;
+- A27 l) radiomaritime letters.
+
+### 5 Limitations
+
+- A28 5.1 The duration of distress calls is not limited.
+- A29 5.2 Except in the automatic operation, the duration of private communications, and of government communications as the case may be, may be limited under certain circumstances (e.g. congestion or fault conditions). The ROAs concerned may agree to limit the duration of these communications.
+- A30 5.3 If the duration of services is limited, the caller shall be informed when calls are about to be connected, that it will be cut off after due time.
+
+### 6 Service hours
+
+- A31 6.1 While the services of most land stations are continuous, certain land stations may have a service of limited duration. It is recommended, therefore, to refer to the *List of Coast Stations* [4].
+- A32 6.2 The working hours of a mobile station in the maritime mobile service are dependent on the categories of ship stations as defined in the Radio Regulations. It is recommended to refer to the *List of Ship Stations* [5] as appropriate.
+
+---
+
+2) For the operational aspects of service telecommunications, see Recommendation F.17, which describes basic principles, acceptable content for service telecommunications and the principle of reciprocity regarding both service providers and services. More detailed provisions for specific telecommunication services may be found in Recommendations F.105, F.1 and F.60.
+
+## DIVISION B – RADIOTELEGRAMS
+
+### 1 Preparation and handing-in of radiotelegrams
+
+#### 1.1 Indication of station of origin
+
+- B1 1.1.1 When, because of duplication of names, the name of a station is followed by its call sign/ship station identity, the latter shall be joined to the name of the station by a fraction bar.
+
+Examples<sup>3)</sup>: **OREGON/OZOC** (not **OREGONOZOC**);
+
+**ROSE/DDOR** (not **ROSEDDOR**).
+
+- B2 1.1.2 When a land station retransmits a radiotelegram received from a mobile station, it shall transmit, as office of origin, the name of the mobile station in which the radiotelegram originated as this name appears in the *List of Ship Stations* [5], followed by its own name. Where appropriate, B1 shall also apply.
+- B3 1.1.3 In order to avoid any confusion with a telegraph office or a fixed station of the same name, the land station may, if desirable, complete the indication of the name of the mobile station of origin by the word **SHIP** or **AIRCRAFT**, placed before the station of origin.
+
+#### 1.2 Use of accounting authority identification codes by mobile stations
+
+- B4 1.2.1 The mobile station operator should, as a standard operating procedure, give the Accounting Authority Identification Code (AAIC) at the end of the preamble line. If the AAIC is missing, the land station operator should request **QRC**.
+
+#### 1.3 Time of handing-in
+
+- B5 1.3.1 In the transmission of radiotelegrams originating in a mobile station, the date and time of handing-in at this station are given by two groups of figures in the preamble line, the first indicating the day of the month (1 to 31) and the second consisting of a group of figures (0001 to 2400) indicating the hours and the minutes.
+- B6 1.3.2 The time of handing-in is indicated in Coordinated Universal Time (UTC).
+
+NOTE – For practical operating purposes, UTC may be considered as equivalent to Greenwich Mean Time (GMT).
+
+#### 1.4 Address
+
+- B7 1.4.1 The address of radiotelegrams destined for mobile stations should be as complete as possible and must include:
+- B8 a) the name or the designation of the addressee, with supplementary particulars, if necessary;
+- B9 b) the name of the mobile station followed, when necessary, by its call sign/ship station identity, the latter joined by a fraction bar to the name of the station as shown in the *List of Ship Stations* [5];
+- B10 c) the name of the land station through which the radiotelegram is to be forwarded, as it appears in the *List of Coast Stations* [4].
+- B11 1.4.2 If the mobile station does not appear in the *List of Ship Stations* [5], the sender should, if possible, indicate the nationality and route followed by the mobile station.
+
+---
+
+<sup>3)</sup> In the provision regarding the non-voice services, letters, figures and signs that are transmitted electrically are shown in bold font.
+
+**B12**    **1.4.3**    However, the name and call sign/ship station identity required under B10 may be replaced, at the risk of the sender, by particulars of the passage made by such a mobile station, indicated by the names of the ports or airports of departure and of destination, or by any equivalent indication.
+
+**B13**    **1.4.4**    Mobile stations may add to the name of the office of destination:
+
+- the name of the territorial subdivision; and/or
+- the destination country,
+
+if it is doubtful whether, without such addition, the radiotelegram could be correctly routed without difficulty.
+
+**B14**    **1.4.5**    The controlling operator retains or deletes the particulars in B13 or further amends the name of the office of destination as is necessary or sufficient for forwarding the radiotelegram to its proper destination.
+
+### **2 Counting of words**
+
+**B15**    **2.1**    The word count of the office of origin is decisive in the case of radiotelegrams destined for mobile stations, and that of the controlling operator is decisive in the case of radiotelegrams originating in mobile stations.
+
+**B16**    **2.2**    If two land stations participate in the handling of a radiotelegram, the decision of the controlling operator accepting the radiotelegram from the originating mobile station will prevail and will be valid for international accounting.
+
+### **3 Routing of radiotelegrams**
+
+**B17**    **3.1**    Radiotelegrams, originating in or destined to a mobile station should be routed via the land station that is considered most suitable in relation to the mobile station concerned in terms of the coverage and of the land station and radio conditions.
+
+**B18**    **3.2**    However, to expedite or to facilitate the routing of radiotelegrams to a land station, a mobile station may transmit them to another mobile station. The latter shall dispose of such radiotelegrams in the same manner as if they originated with itself (see B39 to B42).
+
+**B19**    **3.3**    If the sender of a radiotelegram handed in at a mobile station has indicated the land station to which the radiotelegram be sent, the mobile station shall, in order to effect this transmission to the land station indicated, wait, if necessary until the conditions specified in B17 and B18 are fulfilled.
+
+**B20**    **3.4**    In order to facilitate disposal of traffic, and subject to such conditions as individual ROAs may apply, land stations may, in exceptional circumstances and with discretion, without incurring additional charges, exchange radiotelegrams and service telegrams relating thereto.
+
+### **4 Transmission of radiotelegrams**
+
+#### **4.1 Routine repetition**
+
+**B21A**    **4.1.1**    Routine repetition means the repetition of isolated figures and mixed groups containing figures in the address and text parts. Any such repetition should be given after the text part and be preceded by the code **COL**.
+
+**B21B**    **4.1.2**    In view of CCITT Recommendation F.1 (A103) routine repetition may be used between land station and mobile station at the discretion of the sending station where the transmission conditions warrant it.
+
+**B21C**    **4.1.3**    Where a mobile station gives a routine repetition, the land station shall use the repeated groups to check the received address and text parts, but should not retransmit the routine repetition.
+
+#### 4.2 Doubtful reception
+
+B22 4.2.1 In the mobile service, when communication becomes difficult, the two stations in communication should make every effort to complete the radiotelegram in course of transmission. The receiving station may request not more than two repetitions of a radiotelegram of which the reception is doubtful.
+
+B23 4.2.2 If this triple transmission is ineffective, the radiotelegram is kept on hand in case a favourable opportunity for completing its transmission occurs.
+
+B24 4.2.3 If the transmitting station considers that it will not be possible to re-establish communications with the receiving station within twenty-four hours, it proceeds as follows:
+
+B25 4.2.4 If the transmitting station is a mobile station, it immediately informs the sender of the reason for the non-transmission of his radiotelegram. The sender may then request:
+
+B26 a) that the radiotelegram be transmitted through another land station or through other mobile stations; or
+
+B27 b) that the radiotelegram be held until it can be transmitted without additional charge; or
+
+B28 c) that the radiotelegram be cancelled.
+
+B29 4.2.5 If the transmitting station is a land station, it applies the provision of B43 to B52 to the radiotelegram.
+
+B30 4.2.6 When a mobile station subsequently transmits a radiotelegram thus held to the land station that incompletely received it, this new transmission must bear the service instruction **AMPLIATION** at the end of the preamble line of the radiotelegram.
+
+B31 4.2.7 However, if the radiotelegram is transmitted to another land station operated by the same ROA, the new transmission must bear, at the end of the preamble line, the service instruction **AMPLIATION VIA ...** (insert here the call sign/coast station identity of the land station to which the radiotelegram was transmitted in the first instance) and the ROA in question may claim only the charges relating to a single transmission.
+
+B32 4.2.8 The other land station, which thus forwards the radiotelegram, may claim from the mobile station of origin any additional charges resulting from the transmission of the radiotelegram between itself and the office of destination.
+
+B33 4.2.9 When the land station designated in the address as the station by which the radiotelegram is to be forwarded cannot reach the destination mobile station and has reason to believe that such mobile station is within the service area of another land station of the ROA by which it is operated, it may, if no additional charge is incurred thereby, forward the radiotelegram to this other land station.
+
+B34 4.2.10 A station of the mobile service that has received a radiotelegram and has been unable to acknowledge its receipt in the usual way must take the first favourable opportunity to give such acknowledgement.
+
+B35 4.2.11 When the acknowledgement of receipt of a radiotelegram transmitted between mobile station and land station cannot be given directly, it is forwarded through another mobile or land station by service advice (see Recommendation F.1, Division D) if the latter is able to communicate with the station that has transmitted the radiotelegram in question. In any case, no additional charge shall result.
+
+#### 4.3 Long distance radiocommunications
+
+B36 4.3.1 An ROA may organize a long-distance radiocommunication service between land station and mobile stations, with deferred acknowledgement of receipt or without any acknowledgement of receipt.
+
+B37 4.3.2 Each ROA designates the land station or stations participating in the long-distance radio service. An indication to this effect shall appear in the *List of Coast Stations* [4].
+
+B38 4.3.3 When there is doubt about the accuracy of any part of a radiotelegram transmitted under either of the systems mentioned in B36, the indication doubtful reception is entered on the copy delivered to the addressee, and the doubtful words or groups of words are underlined. If words are missing, blanks are left in the places where these words should be.
+
+#### 4.4 Routine retransmission by mobile stations
+
+B39 4.4.1 When a land station cannot reach the mobile station for which a radiotelegram is destined, the land station may, in order to forward the radiotelegram to its destination, have recourse to the help of another mobile station provided that the latter consents. The radiotelegram is then transmitted to this other mobile station. The help of the latter is given free of charge.
+
+B40 4.4.2 The same provision is also applicable to traffic from mobile stations to land stations, when necessary.
+
+B41 4.4.3 The station assisting in the free retransmission in accordance with B39 and B40 must enter the service abbreviation **QSP** ... (name or call sign/ship station identity of the mobile station) at the end of the preamble line of the radiotelegram.
+
+B42 4.4.4 In order that a radiotelegram thus forwarded may be considered as having reached its destination, the station that has made use of this indirect route must have obtained the regular acknowledgement of receipt, either direct or by an indirect route, from the mobile station for which the radiotelegram was destined or from the land station to which it was to be forwarded, as the case may be.
+
+#### 4.5 Period of retention of radiotelegrams at land stations
+
+B43 4.5.1 When it has not been possible for a land station to transmit a radiotelegram to a mobile station by the morning of the fifth day (not including the day of handing-in), the land station treats the radiotelegram as undelivered and notifies the office of origin accordingly.
+
+B44 4.5.2 The sender of a radiotelegram destined for a mobile station may specify the number of days during which the land station may hold the radiotelegram. In that case, the service indication **Jx** (x days), specifying the number of days (ten at the most) exclusive of the day of handing-in of the radiotelegram, shall be shown before the address. When it has not been possible for a land station to transmit a radiotelegram bearing the service indication **Jx** within the prescribed period, the land station treats the radiotelegram as undelivered and informs the office of origin accordingly.
+
+B45 4.5.3 The periods mentioned in B43 and B44 shall be ignored if the land station is sure that the mobile station will soon come within its service area.
+
+B46 4.5.4 On the other hand, the lapse of those periods is not awaited when the land station is sure that the mobile station, being in course of a voyage, either has definitely left its service area or will not enter it.
+
+B47 4.5.5 If there is reason to believe that no other land station of the ROA by which it is operated is or will be in touch with it, the land station cancels the radiotelegram as far as concerns the section between itself and the mobile station and informs the office of origin, which notifies the sender.
+
+B48 4.5.6 In the contrary case, the land station forwards the radiotelegram to the land station believed to be in touch with the mobile station, provided, however, that no additional charge results therefrom.
+
+B49 4.5.7 The land station that carries out the redirection alters the address of the radiotelegram by placing after the name of the mobile station that of the new land station charged with the transmission and adding at the end of the preamble line the service instruction **REDIRECTED FROM ... RADIO**, which must be transmitted throughout the course of the radiotelegram.
+
+B50 4.5.8 If, within the limits of the requisite period of retention of radiotelegrams, the land station that has redirected a radiotelegram to another land station is subsequently in a position to transmit the radiotelegram direct to the destination mobile station, it does so by inserting the service instruction **AMPLIATION** at the end of the preamble line.
+
+B51 4.5.9 It shall then transmit to the land station to which the radiotelegram had been redirected a service advice informing the latter of the transmission of the said radiotelegram.
+
+B52 4.5.10 When a radiotelegram cannot be transmitted to a mobile station owing to the arrival of the latter in a port near the land station, the latter station may, according to circumstances, forward the radiotelegram to the mobile station by other means of communication, at the same time informing the office of origin by service advice of the delivery.
+
+### 5 Advice of non-delivery
+
+- B53 5.1** When, for any reason, a radiotelegram originating in a mobile station and destined for a place on land cannot be delivered to the addressee, a service advice of non-delivery is addressed to the land station or the telegraph office that received the radiotelegram.
+- B54 5.2** After checking the address, the land station forwards the service advice, when possible, to the mobile station, if necessary by way of another land station of the same country or of a neighbouring country, as far as existing conditions or special agreements permit.
+- B55 5.3** When a radiotelegram received at a mobile station cannot be delivered, that station so informs the office or mobile station of origin by a service advice.
+- B56 5.4** In the case of a radiotelegram originating on land, this service advice is sent, whenever possible, to the land station through which the radiotelegram passed, or, if necessary, to another land station of the same country or of a neighbouring country, as far as existing conditions or special arrangements permit.
+- B57 5.5** In such cases the name or call sign/ship station identity of the station from which the radiotelegram was received is quoted.
+
+### 6 Radiomaritime letters
+
+- B58 6.1** An ROA may organize a service of radiomaritime letters between mobile stations and its land stations.
+- B59 6.2** Such correspondence is transmitted by radio between mobile and land stations.
+- B60 6.3** They may be forwarded on the land section:
+- B61 a)** wholly or partly by post (ordinary or airmail);
+- B62 b)** exceptionally by telefax or other electronic means, but with low priority.
+- B63 6.4** Routine retransmission by mobile stations of radiomaritime letters is not permitted.
+- B64 6.5** Radiomaritime letters shall be addressed only to places in the country in which the land station is situated, unless the *List of Coast Stations* [4] indicates that the station concerned will accept such traffic for onward transmission by post to places in other countries.
+- B65 6.6** Radiomaritime letters bear the service indication **SLT**. This indication precedes the address.
+- B66 6.7** Except as otherwise provided in B58 to B68, radiomaritime letters may be accepted, taking into account ITU-T CCITT Recommendations relating to letter telegrams if the telegram service is used to convey radiomaritime letters.
+- B67 6.8** The address must enable delivery to be effected without enquiry or requests for information. Registered or abbreviated code addresses may be accepted where B62 above applies, exceptionally, radiomaritime letters are forwarded by means of telegram on the land section.
+- B68 6.9** Radiomaritime letters rank, for radio transmission, after ordinary radiotelegrams on hand. Those that have not been transmitted within 24 hours of handing-in are sent concurrently with ordinary radiotelegrams.
+
+### 7 Special services
+
+- B69 7.1** Telegrams with special services of urgent transmission and de luxe form are admitted, provided that the ROAs concerned accept them.
+
+### 8 Special conditions relating to the maritime mobile-satellite service
+
+- B70 8.1** In the maritime mobile-satellite service radiotelegrams should normally be transmitted by radiotelex only.
+- B71 8.2** The radiotelegram service in B70 should be arranged in such a way that automatic retransmission is possible.
+
+## **DIVISION C – RADIOTELEX**
+
+### **1 General**
+
+#### **1.1 Routing of calls**
+
+**C1 1.1.1** A radiotelex call, originating in or destined to a mobile station should be set up via the land station that is considered to be most suitable in relation to the mobile station concerned in terms of the coverage and of the land stations and radio conditions.
+
+**C2 1.1.2** For radiotelex calls in the direction from land station to mobile station, originator should give, if possible, the approximate geographical position and should also indicate the land station to be used unless the ROA has established a specific route to be followed. Such requests should be respected as far as is practicable.
+
+**C3 1.1.3** For radiotelex calls in the direction from mobile station to land station, the mobile station may call a particular land station it desires to use. This land station should either handle the call itself or advise the mobile station to use another land station that is more suitable.
+
+#### **1.2 Information to be supplied, as necessary by the calling party**
+
+**C4 1.2.1** Calls from a subscriber of the international telex service to a mobile station:
+
+- a) international telex number and/or answer-back code of the calling telex subscriber;
+- b) telex number or mobile station number of the destination mobile station;
+- c) name or call sign/ship station identity of the destination mobile station;
+- d) international telex number and/or name of the land station to be used, or the approximate geographical position of the destination mobile station;
+- e) priority when specifically requested.
+
+**C5 1.2.2** Calls from a mobile station to a subscriber of the international telex service:
+
+- a) telex number or mobile station number of the calling mobile station;
+- b) the Accounting Authority Identification Code (AAIC) in accordance with CCITT Recommendation D.90 in the single-operator or manual operation;
+- c) destination country and/or network;
+- d) telex number and/or answer-back code of the destination telex subscriber;
+- e) priority when specifically requested.
+
+**C5A 1.2.3** C4 and C5 above apply to mobile station-to-mobile stations calls as appropriate.
+
+#### **1.3 Call duration**
+
+**C6 1.3.1** The chargeable duration of a call will be fixed at the end of the call:
+
+- a) by the controlling operator for a call originating from a mobile station;
+- b) for a call originating in the international telex service;
+  - by the land station operator in either manual or single-operator operation;
+  - by the operator of the international position of the originating country in the semi-automatic operation.
+
+**C7 1.3.2** For a call originating from a mobile station and where two land stations participate in the handling of the call, the decision of the controlling operator who has accepted the call from the originating mobile station shall prevail.
+
+C8      1.3.3      Should service difficulties be experienced in the course of a call, the chargeable duration shall be reduced automatically or manually to the total time during which transmission conditions were satisfactory, taking into account ITU-T Recommendations (F.60 and F.61).
+
+#### 1.4      **Validity of requests**
+
+C9      1.4.1      For a call to a mobile station where it becomes obvious that the required mobile station cannot be reached by the land station, the originating telex subscriber should be informed as soon as possible in order to have the opportunity to have the call cancelled if required. In any event, the caller should be informed no later than in the morning of the second day following the day on which the call request was made.
+
+C10     1.4.2      In the automatic service any information concerning unsuccessful call attempts shall be provided to the calling subscriber using the service signal format described in Recommendation F.60. The period of validity for store-and-forward messages in the automatic service shall be in accordance with Recommendation F.72.
+
+#### 1.5      **Exchange of radiotelegrams by radiotelex**
+
+C11     1.5.1      Stations of the maritime mobile service that are equipped for radiotelex may transmit and receive radiotelegrams by means of radiotelex.
+
+C12     1.5.2      Stations of the maritime mobile-satellite service should normally transmit and receive radiotelegrams by means of radiotelex only.
+
+### 2      **Traffic from mobile stations to subscribers of the international telex service**
+
+#### 2.1      **Automatic operation**
+
+C13     2.1.1      Whenever possible, fully automatic procedures should be used.
+
+C14     2.1.2      For a call originating from a mobile station and after connection with the desired land station is established, the mobile station should forward the international telex number, including the telex destination code in accordance with Recommendation F.69. The selection procedures for calls from a mobile station in the maritime mobile-satellite service to a subscriber of the international telex service are described in clause 6 of Division C.
+
+#### 2.2      **Single-operator operation**
+
+C15     2.2.1      The land station operator should select the destination telex subscriber directly via the international telex network if fully automatic procedures (C13) are not possible.
+
+#### 2.3      **Semi-automatic operation**
+
+C16     2.3.1      The destination telex subscriber should be automatically selected if fully automatic procedures (C13) or single operator procedures (C15) cannot be applied.
+
+#### 2.4      **Manual operation**
+
+C17     2.4.1      The land station operator should apply manual procedures if fully automatic (C13), single-operator (C15) or semi-automatic (C16) procedures are not possible.
+
+#### 2.5      **Store-and-forward service**
+
+C17A    2.5.1      The mobile station should transmit the message to the land station using automatic procedures. The land station should forward the message via the international telex network to the destination telex subscriber.
+
+C17B    2.5.2      The procedures for store-and-forward in the operation international telex network, as laid down in Recommendations F.72, U.80 and U.81, should be taken into account.
+
+#### **2.6 Operational procedures**
+
+**C18 2.6.1** The manual, semi-automatic and fully automatic procedures for the international telex service, as laid down in Recommendations F.60 and F.61, should be taken into account.
+
+### **3 Traffic from subscribers of the international telex service-to-mobile stations**
+
+#### **3.1 Fully automatic operation**
+
+**C19 3.1.1** Whenever possible fully automatic procedures should be used.
+
+**C20 3.1.2** A subscriber of the international telex service should forward the international telex number of the destination mobile station including the mobile station number and if necessary the telex destination code of the ocean region in which the mobile station is thought to be located. The call will then be routed, through an appropriate land station to the destination mobile station. The selection procedures for calls from a subscriber of the international telex service to mobile earth station are described in clause 6 of Division C.
+
+**C21 3.1.3** If the originating telex subscriber, for some technical reason, cannot use fully automatic procedures to establish contact with the mobile station, semi-automatic (C35) or single-operator (C24) procedures should be used.
+
+**C22 3.1.4** On international telex links a destination code in accordance with Recommendation F.69 will be used unless otherwise agreed bilaterally.
+
+**C23 3.1.5** Normal telex procedure should be forwarded once the connection between the subscriber of the international telex service and the mobile service and the mobile station has been established.
+
+#### **3.2 Single-operator operation (direct access by a calling telex subscriber to a foreign land station)**
+
+##### **3.2.1 Booking**
+
+**C24 3.2.1.1** If automatic operation (C19) is not possible and where an ROA allows its subscribers to book a call directly with a land station in another country, the originating telex subscriber should select the desired foreign land station, when known, using automatic procedures and submit the call details to the land station operator.
+
+**C25 3.2.1.2** The charges fixed by the land station operator should be levied on the calling subscriber through international accounting.
+
+**C26 3.2.1.3** In addition to the information in C4, the calling subscriber should designate the originating national telex network.
+
+**C27 3.2.1.4** As an alternative to C25 and C26, a land station may accept direct calls from foreign subscribers in other countries provided that the calling telex subscriber supplies the name and address of a party in the country in which the land station is located who will take responsibility for the payment of charges.
+
+**C28 3.2.1.5** The procedures described in C25 and C27 may only be applied when an appropriate bilateral agreement exists between the two ROAs concerned. If such an agreement does not exist, the land station should refuse such calls to avoid accounting difficulties.
+
+**C29 3.2.1.6** In C24 and C27 above, the call to the foreign land station will be charged as an ordinary international telex call for its entire duration, regardless of whether it merely serves the purpose of booking the radiotelex call or whether the land station can extend the connection to the mobile station without having to recall the originating subscriber.
+
+##### **3.2.2 Setting-up**
+
+**C30 3.2.2.1** When the connection to the destination mobile station can be immediately established, the originating telex subscriber should be released by the land station. When appropriate, the land station operator should recall the originating telex subscriber using automatic procedures. In this particular case, the country in which the land station is located is to be considered as the outgoing country for the call.
+
+**C31 3.2.2.2** In case C30, the land station should include in the maritime bill:
+
+- a) the landline charge;
+- b) the land station charge.
+
+**C32 3.2.2.3** When the connection to the destination mobile station can be immediately established, the maritime bill made out by the land station operator should include only the land station charge.
+
+**C33 3.2.2.4** All information regarding collection of charges for single-operator calls (see C15) should be submitted by the land station ROA on a regular basis to be determined by the ROAs involved.
+
+**C34 3.2.2.5** The methods to be used in collecting the charges are described in Recommendation D.90.
+
+#### **3.3 Semi-automatic operation (access by a calling subscriber to one's international centre for the establishment of a direct connection)**
+
+**C35 3.3.1** If fully automatic (C19) or single-operator (C24) procedures are not possible, the telex operator of the outgoing international centre should receive the booking and selects the mobile station directly. The procedures of Recommendation F.60 should be applied.
+
+#### **3.4 Manual operation**
+
+##### **3.4.1 Booking**
+
+**C36 3.4.1.1** If fully automatic (C19), single-operator (C24) or semi-automatic (C35) procedures are not available, the originating telex subscriber should make his booking at the international telex centre of the outgoing country or network.
+
+**C37 3.4.1.2** Where conditions permit, the international telex position should select directly the appropriate foreign land station. Alternatively, the international telex position of the outgoing country or network should contact the international telex position in the country or network in which the desired land station is located for the necessary assistance to obtain contact with the land station.
+
+##### **3.4.2 Setting-up**
+
+**C38 3.4.2.1** The land station operator will establish a connection with the originating telex subscriber either directly or with the assistance of the own international telex position in the country of the land station.
+
+**C39 3.4.2.2** Within 24 hours of the call's termination, the land station shall pass the following information to the international telex position of the origin country, where it is recorded for charging and accounting purposes:
+
+- a) the calling subscriber's telex number;
+- b) the mobile station's call sign/ship station identity;
+- c) the chargeable duration of the call;
+- d) the land station charge to be collected.
+
+#### **3.5 Store-and-forward**
+
+**C39A 3.5.1** The originating telex subscriber should select the appropriate land station and deposit the message using the procedures desired in Recommendations F.72 and U.80.
+
+### 4 Traffic exchanged between mobile stations
+
+C39B 4.1 Provisions from C13 to C39A apply to traffic exchanged between mobile stations.
+
+### 5 Radiomarine telex letter
+
+#### 5.1 Definition
+
+C40 5.1.1 **Radiomarine telex letter:** A message sent by radiotelex direct from a mobile station to a selected land station or to a selected public telegraph office for delivery by mail or any other appropriate means.
+
+#### 5.2 Operational procedures
+
+C41 5.2.1 The mobile station should select the access code allocated for the radiomarine telex letter service, or the access code allocated for the fully automatic telex service followed, if appropriate, by the telex number of the selected land station telegraph office.
+
+C42 5.2.2 The mobile station should supply the following information:
+
+- international telex number of the mobile station or mobile station number (as provided in Recommendation F.125);
+- the Accounting Authority Identification Code (AAIC);
+- destination name and address;
+- the words "RADIOMARITIME TELEX LETTER".
+
+### 6 Special provisions for the maritime mobile-satellite telex service
+
+#### 6.1 Procedures for calls from subscribers of the international telex service to a mobile earth station
+
+C43 6.1.1 To establish a call from subscribers of the international telex service to Mobile Earth Stations (MES), the calling telex subscriber should select the telex destination code of the appropriate satellite region followed by the mobile station number.
+
+C44 6.1.2 The originating telex subscriber, when calling an MES, should input the following selection information, plus any necessary prefix and end-of-selection signal:
+
+**58STX<sub>1</sub> ..... X<sub>n</sub>**
+
+where:
+
+**58S** is the telex destination code in accordance with Recommendation F.69 (S = 1, 2, 3 or 4);
+
+**T** is the T-digit in accordance with Recommendation F.125; and
+
+**X<sub>1</sub> ..... X<sub>n</sub>** are part of the MES identity in accordance with Recommendation F.125.
+
+To meet the requirements of the international telex service and in particular the signalling conditions specified in Recommendations U.11 and U.12, the Inmarsat mobile station number should not contain more than 9 digits.
+
+#### 6.2 Procedures for calls from MES to subscribers of the international telex service
+
+##### 6.2.1 Setting up a communication channel
+
+C45 6.2.1.1 The necessary communication channel should be set up in accordance with the procedures established by the appropriate satellite organization.
+
+##### 6.2.2 Information to be provided
+
+**C46** **6.2.2.1** The MES should provide all information necessary for setting up the call to the destination telex subscriber. Such information may include:
+
+- international telex number of the destination telex subscriber;
+- desired land earth station whether or not the land earth station is located in the country of the called telex subscriber;
+- supplementary service requests.
+
+The information in a) is required for all calls. The information in b) and c) may be required on some calls, e.g. if the user requests a specific routing of the call or if specific service characteristics are to be applied.
+
+##### 6.2.3 Calling a subscriber of the international telex service
+
+**C47** **6.2.3.1** The MES should select the access code 00 followed by the full international telex number of the destination telex subscriber. Hence the numbering sequence selected by MES should be of the form:
+
+**00 <F.69> <national telex number>+**
+
+where:
+
+|                                      |                                                                             |
+|--------------------------------------|-----------------------------------------------------------------------------|
+| <b>00</b>                            | Access code for automatic call                                              |
+| <b>&lt;F.69&gt;</b>                  | 2- or 3-digit telex destination code in accordance with Recommendation F.69 |
+| <b>&lt;national telex number&gt;</b> | National number of the destination telex subscriber                         |
+| <b>+</b>                             | End of selection                                                            |
+
+**C48** **6.2.3.2** It may be possible to select specific supplementary services associated with the call by use of access codes other than 00, for example:
+
+|                                                                  |                                                                             |
+|------------------------------------------------------------------|-----------------------------------------------------------------------------|
+| <b>A<sub>1</sub>A<sub>2</sub></b>                                | Access code including supplementary service requests                        |
+| <b>&lt;F.69&gt;</b>                                              | 2- or 3-digit telex destination code in accordance with Recommendation F.69 |
+| <b>&lt;national telex number&gt; N<sub>1</sub>-N<sub>n</sub></b> | National number of the destination telex subscriber                         |
+| <b>+</b>                                                         | End of selection                                                            |
+
+**C49** **6.2.3.3** The operational procedures should permit the MES to choose land earth stations through which the call is to be routed, for example, in order to minimize call charges.
+
+**C50** **6.2.3.4** The provision of C3 notwithstanding, the land earth station called should always handle the call whenever a MES is within the coverage area of the land earth station.
+
+#### 6.3 Procedures for MES-to-MES calls
+
+**C51** **6.3.1** A MES participating in the mobile satellite telex service may send a message to another MES. Selection procedures for MES-to-MES calls which are carried by the international telex service should be similar to those for calls from a MES to subscribers of the international telex service as described in C47. This format will be used whether or not the MESs are in the same satellite region.
+
+**C52** **6.3.2** The procedures for calls between MESs in the same satellite region, or in satellite regions served by the same LES and which do not utilize the international telex service are not the subject for international standardization.
+
+#### 6.4 Instructions for maritime mobile-satellite telex service
+
+**C53** **6.4.1** The general principles laid down in Recommendation F.60 apply also to the maritime mobile-satellite telex service. The instructions should contain the full procedures.
+
+## **DIVISION D – RADIOTELEPHONE**
+
+### **1 General**
+
+#### **1.1 Language to be used**
+
+**D1 1.1.1** Where applicable and where language difficulties exist, the abbreviations and signals in related provisions of *Radio Regulations* [3] should be used in radiotelephone communications between land stations and mobile stations.
+
+#### **1.2 Priority**
+
+**D2 1.2.1** Apart from the general order of priority shown in **A15 to A27**, radiotelephone calls shall have precedence in the terrestrial network, so far as possible, over other telephone calls of the same class.
+
+#### **1.3 Routing of calls**
+
+**D3 1.3.1** A radiotelephone call, originating in or destined to a mobile station, should be set up via the land station that is considered to be the most suitable in relation to the mobile station concerned in terms of the coverage and of the land station and radio condition.
+
+**D4 1.3.2** For radiotelephone calls in the direction from land station to mobile station, the caller should give the one approximate geographical position if possible and may also indicate the land station to be used unless the ROA has established a specific route to be followed. Such requests should be respected as far as is practicable.
+
+**D5 1.3.3** For radiotelephone calls in the direction from mobile station to land station, the mobile station may call a land station it desires to use. This land station shall either handle the call itself or advise the mobile station to use another land station that is more suitable.
+
+#### **1.4 Information to be supplied, as necessary, by the calling party**
+
+**D6 1.4.1** Calls from a telephone subscriber to a mobile station:
+
+- a) complete telephone number of the calling subscriber;
+- b) appropriate identification of the mobile station;
+- c) name of the land station to be used or the approximate geographical position of the destination mobile station;
+- d) name of the called party, if applicable. All calls to mobile stations in the maritime mobile service are treated as personal calls, with the possible exception of the maritime mobile-satellite service;
+- e) priority when specifically requested.
+
+**D7 1.4.2** Call from a mobile station to a telephone subscriber:
+
+- a) appropriate identification of the mobile station;
+- b) the Accounting Authority Identification Code (AAIC) in accordance with Recommendation D.90 in the single-operator or manual operation;
+- c) the information specified in Article 63 of the *Instructions for the International Telephone Service*;
+- d) priority when specifically requested.
+
+**D7A 1.4.3** D6 and D7 above apply to mobile station-to-mobile station calls as appropriate.
+
+#### **1.5 Call duration**
+
+**D8 1.5.1** The chargeable duration of a call shall be fixed at the end of the call:
+
+- a) by the controlling operator for a call originating from a mobile station;
+- b) for a call originating in the terrestrial telephone network;
+  - by the land station operator in manual or single-operator operation;
+  - by the operator of the international position of the outgoing country in the semi-automatic operation.
+
+**D9 1.5.2** For a call originating from a mobile station where two land stations participate in the handling of the call, decision of the controlling operator that has accepted the call from the originating mobile station shall prevail.
+
+**D10 1.5.3** Should service difficulties be experienced in the course of a call, the chargeable duration shall be reduced automatically or manually to the total time during which transmission conditions were satisfactory, taking into account ITU-T Recommendations.
+
+#### **1.6 Validity of requests**
+
+**D11 1.6.1** If not cancelled by the caller or refused by the called party, requests for calls from land to mobile stations:
+
+- a) in the VHF and MF bands shall remain valid until 0800 local time on the day following the day on which the request was made;
+- b) in the HF band shall remain valid until 0800 local time on the second day following the day on which the request was made.
+
+**D12 1.6.2** However, if it becomes obvious that the required mobile station is outside the coverage area of the land station, the caller shall be informed as soon as possible in order to have the call cancelled.
+
+**D13 1.6.3** All requests for calls from mobile to land stations shall be cancelled where the call is not immediately attended to or on completion of the successive attempts provided for by the rules of each ROA, unless there has been an express request to the contrary by the calling mobile station, which shall be able to determine the waiting period for listening in on the land station frequency with a view to making a further attempt to set up the call.
+
+#### **1.7 Exchange of radiotelegrams by radiotelephony**
+
+**D14 1.7.1** Stations of the maritime mobile service that are equipped for radiotelephony may transmit and receive radiotelegrams by means of radiotelephony. Stations of the maritime mobile-satellite service should normally transmit and receive radiotelegrams by means of radiotelex only.
+
+### **2 Traffic from mobile stations to telephone subscribers**
+
+#### **2.1 Automatic operation**
+
+**D15 2.1.1** Whenever possible, fully automatic procedures should be used.
+
+**D16 2.1.2** For a call originating from a mobile station and after connection with the desired land station has been established, the mobile station should forward the appropriate telephone country code (Recommendation E.164) and the number of the subscriber of an ROA's telephone network. The selection procedures for calls in the maritime mobile-satellite service, see clause 4 of Division D.
+
+#### **2.2 Single-operator operation**
+
+**D17 2.2.1** The land station operator should select the called subscriber directly via the automatic telephone networks if automatic procedures (D15) are not possible.
+
+#### **2.3 Semi-automatic operation**
+
+**D18 2.3.1** The called telephone subscriber should be automatically selected by a telephone operator in the country in which land station is situated if fully automatic (D15) or single-operator (D17) procedures cannot be applied.
+
+#### **2.4 Manual operation**
+
+**D19 2.4.1** The land station operator should apply manual procedures if fully automatic (D15), single-operator (D17) or semi-automatic (D18) procedures are not possible.
+
+#### **2.5 Operational procedures**
+
+**D20 2.5.1** The fully automatic, semi-automatic and manual procedures for the terrestrial telephone network, as laid down in Recommendations E.105 and E.140 and the *Instructions for the International Telephone Service* [6] should be taken into account.
+
+### **3 Traffic from telephone subscribers to mobile stations**
+
+#### **3.1 Fully automatic operation**
+
+**D21 3.1.1** Whenever possible, fully automatic procedures should be used.
+
+**D22 3.1.2** The subscriber of an ROA's telephone network should select the appropriate international telephone number, which would include the mobile station number. The call routing will be determined by the appropriate country code which is chosen and which will form part of the international telephone number (see D41). The call will then be routed through an appropriate land station to the destination mobile station. The selection procedures for calls from a subscriber of the international telephone service are described in clause 5 of Division D.
+
+**D23 3.1.3** If the calling subscriber, for some technical reason, cannot use fully automatic procedures to establish contact with mobile station, semi-automatic or single operator procedures should be used.
+
+#### **3.2 Single-operator operation (direct access by a calling subscriber to a foreign land station)**
+
+##### **3.2.1 Booking**
+
+**D24 3.2.1.1** If fully automatic operation is not possible and where an appropriate bilateral agreement between ROA's allows its subscriber to book a call directly with a land station in another country, the calling telephone subscriber should select desired foreign land station, where known, using automatic procedures and submit the call details to the land station operator. If such an agreement does not exist, the land station should refuse such calls to avoid accounting difficulties.
+
+**D25 3.2.1.2** The charges fixed by the land station operator should be levied on the calling subscriber through international accounting.
+
+**D26 3.2.1.3** In addition to the information in D6, the calling subscriber must designate his country and national telephone number.
+
+**D27 3.2.1.4** As an alternative to D25, land stations may accept direct calls from telephone subscribers in other countries provided that the calling telephone subscriber supplies the name and address of a party in the country, in which the land station is located, who will take responsibility for the payment of charges.
+
+**D28 3.2.1.5** The procedures described in D25 and D27 may only be applied when an appropriate bilateral agreement exists between the two ROAs concerned.
+
+**D29 3.2.1.6** D24 and D27 above, the call to the foreign land station will be charged as an ordinary international telephone call for its entire duration, regardless of whether it merely serves the purpose of booking the radiotelephone call or whether the land station can extend the connection to the mobile station without having to recall the originating subscriber.
+
+##### **3.2.2 Setting-up**
+
+**D30 3.2.2.1** When demand operation cannot be used, the calling telephone subscriber will be disconnected by the land station. When the land station operator then recalls the caller using automatic direct selection, the land station country is considered as the outgoing country for the call.
+
+**D31 3.2.2.2** In case D30, the land station includes in the maritime bill:
+
+- a) the land-line charge;
+- b) the land station charge.
+
+**D32 3.2.2.3** When demand operation has been used, the maritime bill made out by land station operator includes only:
+
+- the land station charge.
+
+**D33 3.2.2.4** All information regarding collection of charges for single-operator calls (see D17) should be submitted by the land station ROA on a regular basis to be determined by the ROAs involved.
+
+**D34 3.2.2.5** The methods to be used in collecting the charges are described in Recommendation D.90.
+
+#### **3.3 Semi-automatic procedure (access by a calling subscriber to one's international centre for the establishment of a direct connection)**
+
+**D35 3.3.1** If automatic (D21) or single-operator (D24) procedures are not possible, the telephone operator of the international centre of the outgoing country receives the booking and selects the mobile station directly. Normal international semi-automatic telephone procedures shall be applied.
+
+#### **3.4 Manual operation**
+
+##### **3.4.1 Booking**
+
+**D36 3.4.1.1** If automatic (D21), single-operator (D24) or semi-automatic (D35) procedures cannot be applied, the subscriber should make his booking at an international centre in the outgoing country.
+
+**D37 3.4.1.2** If conditions permit, an international position should select the foreign land station in question directly. Otherwise an international position in the land station country should be selected to give the necessary assistance to obtain contact with the land station in question. Alternatively, the international telephone position of the outgoing country or network should contact the international telephone position in the country of network in which the desired land station is located for the necessary assistance to obtain contact with the land station.
+
+##### **3.4.2 Setting-up**
+
+**D38 3.4.2.1** The land station operator will establish a connection with the originating telephone subscriber either directly or with the assistance of his own international telephone position.
+
+**D39 3.4.2.2** After the termination of the call, the land station shall pass the following information to the international telephone position of the country of origin, where it is recorded for charging and accounting purposes:
+
+- a) the calling subscriber's telephone number;
+- b) the mobile station's name and/or appropriate identification;
+- c) the chargeable duration of the call;
+- d) the land station charge to be collected.
+
+**D40 3.4.2.3** Alternatively all information regarding collection of charges should be submitted to the caller's ROA on a regular basis to be determined by the ROAs involved.
+
+### **4 Traffic exchanged between mobile stations**
+
+**D40A 4.1** Provisions from D15 to D40 apply to traffic exchanged between mobile stations as appropriate.
+
+### **5 Special provisions for the maritime mobile-satellite telephone service**
+
+#### **5.1 Procedures for calls from subscribers of a terrestrial telephone network to a mobile earth station**
+
+**D41** To establish a call from a telephone subscriber to a Mobile Earth Station (MES), the calling telephone subscriber should select the international mobile number appropriate to the mobile system being accessed. The international mobile number may vary according to the maritime mobile-satellite system offering the service. Where the system provides service on the basis of individual satellite regions, the originating subscriber should select the international mobile number which will contain the telephone country code for the appropriate satellite region followed by the MES number. Where the system offers service on the basis Single Network Access Code operation (SNAC), the originating subscriber should select the international mobile number which will contain the appropriate telephone country code for worldwide access followed by the MES number.
+
+**D42** The selection information for the Inmarsat systems providing service on the basis of either satellite regions or SNAC operation may be located in CCITT Recommendation E.215.
+
+#### **5.2 Procedures for calls from MES to subscribers of the terrestrial telephone networks**
+
+##### **5.2.1 Setting up a communication channel**
+
+**D43** The necessary communication channel should be set up in accordance with the procedures established by the appropriate satellite organization.
+
+##### **5.2.2 Information to be provided**
+
+**D44** The MES should provide all information necessary for setting up the call to the called subscriber:
+
+- a) called party address international telephone number of the called subscriber including any prefix;
+- b) desired land earth station whether or not the land earth station is located in the country of the called subscriber;
+- c) selection of a specific ROA (for further study);
+- d) bearer service/teleservice characteristics, including supplementary service requests.
+
+The information in a) is required for all calls. The information in b) and c) may be required on some calls, e.g. if the user requests a specific routing of the call or if specific service characteristics are to be applied.
+
+##### **5.2.3 Calling a telephone subscriber**
+
+**D45 5.2.3.1** The MES should select the prefix 00 followed by the full international telephone or ISDN number of the called telephone subscriber. Hence, the numbering sequence selected by a MES should be of the form:
+
+$$00I_1I_2I_3N_1 \dots N_n$$
+
+where:
+
+**00** Prefix for automatic call
+
+**$I_1I_2I_3$**  1-, 2- or 3-digit country code in accordance with Recommendation E.164
+
+**$N_1 \dots N_n$**  National (subscriber) telephone number
+
+**D46**    **5.2.3.2**   It may also be possible to select specific services associated with the call by use of prefixed numbers other than 00. For example:
+
+**P<sub>1</sub>P<sub>2</sub>**            Prefix
+
+**I<sub>1</sub>I<sub>2</sub>I<sub>3</sub>**            1-, 2- or 3-digit country code in accordance with Recommendation E.164
+
+**N<sub>1</sub> ... N<sub>n</sub>**        National (subscriber) telephone number
+
+**D47**    **5.2.3.3**   The operational procedures should allow the MES to choose the land earth station through which the call is to be routed, for example, in order to minimize call charges.
+
+**D48**    **5.2.3.4**   The provision of D5 notwithstanding, the land earth station called should always handle itself the ship-to-shore call whenever the calling ship earth station is within the coverage area of the land earth station.
+
+##### **5.2.4    Access to special destination, services or facilities**
+
+**D49**    **5.2.4.1**   The MES will have access to a special destination, service or facility by selecting a special prefix otherwise allocated.
+
+**D50**    **5.2.4.2**   Each ROA may decide which special destinations, services or facilities to provide, where they are to be located and how the call would be routed.
+
+**D51**    **5.2.4.3**   An example of general selection sequence will be as follows:
+
+$$D_1D_2I_1I_2I_3X_1X_2$$
+
+where:
+
+**D<sub>1</sub>D<sub>2</sub>**            Prefix, identifying the category and type of special destinations, service or facilities
+
+**I<sub>1</sub>I<sub>2</sub>I<sub>3</sub>**            Optional country code
+
+**X<sub>1</sub>X<sub>2</sub>**            Other optional digits
+
+#### **5.3    Procedures for MES-to-MES calls**
+
+**D52**    **5.3.1**    A MES participating in the mobile satellite telephone service may send a call to another MES. Selection procedures for MES-to-MES calls which are carried by the ROA's telephone service should be similar to those for calls from a MES to telephone subscriber, as described in D44. This format will be used whether or not MESs are in the same satellite region.
+
+**D53**    **5.3.2**    Each ROA operating a land earth station may decide whether to switch ship-to-ship traffic within satellite region at the land earth station or at an international telephone exchange. The procedures for calls between MESs in the same satellite region, or in satellite regions served by the same land earth station and which do not utilize the ROA's telephone service are not the subject of international standardization.
+
+#### **5.4    Instruction for maritime mobile-satellite telephone service**
+
+**D54**    **5.4.1**    For telephone subscribers the general principles laid down in Recommendation E.120 apply also to the maritime mobile-satellite telephone service. The instructions should contain the full selection procedures.
+
+## **DIVISION E – RADIOTELEXOGRAM**
+
+### **1 General**
+
+#### **1.1 Definition**
+
+- E1**    **1.1.1**    A **radiotelexogram** is a message sent by telex or telefax direct from an originator subscriber to a foreign land station for transmission to a mobile station or a message sent from a mobile station to a land station for transmission directly to a telefax or telex subscriber (see Note in E5).
+
+#### **1.2 Provision of service**
+
+- E2**    **1.2.1**    Operating, charging and accounting procedures should be subject to a bilateral agreement between the ROAs concerned. If such an agreement does not exist, the land station should refuse such radiotelexograms in the shore-to-ship direction.
+- E3**    **1.2.2**    Alternatively, land stations may accept radiotelexograms from foreign originators provided that the calling subscriber supplies the name and address of a party in the land station country that will take responsibility for the payment of charges.
+
+#### **1.3 Validity of requests**
+
+- E4**    **1.3.1**    If it becomes obvious that the required mobile station is outside the coverage area of the land station, the originator shall be informed as soon as possible in order to have the radiotelexogram cancelled.
+
+### **2 Operational procedures**
+
+- E5**    **2.1**    The transmission of radiotelexograms should be in accordance with Divisions **B** and **C** or other ITU-T Recommendations as appropriate except as specified below or where varied through bilateral agreement.
+
+NOTE – A radiotelexogram is different from a radiotelex or telefax call. In particular, a radiotelexogram is normally transmitted between the mobile station and the land station as a radiotelegram by Morse telegraphy or by radiotelephony.
+
+- E6**    **2.2**    Information to be supplied to the land station, as necessary, by the originator.
+
+#### **E7**    **2.2.1**    Radiotelexogram to a mobile station:
+
+- a) international telex number and/or answer-back code or the telefax number of the calling subscriber;
+- b) the date and time of origin;
+- c) the word RADIOTELEXOGRAM;
+- d) name or designation of the addressee with supplementary particulars if necessary;
+- e) the name of the mobile station followed, when necessary, by its call sign/ship station identity or where this is not known, the particulars of the passage made by the mobile station;
+- f) any specific delivery instructions.
+
+#### **E8**    **2.2.2**    Radiotelexogram from a mobile station:
+
+- a) name and/or call sign/ship station identity of the mobile station;
+- b) identification of the accounting authority;
+- c) the date and time of origin;
+- d) the word RADIOTELEXOGRAM;
+- e) destination country and/or network;
+- f) called subscriber's telex number and answer-back code or telefax number.
+
+## **Bibliography**
+
+- [1] *International Telecommunication Regulations*, ITU, Geneva, 1992.
+- [2] *International Telecommunication Constitutions*, ITU, Geneva, 1992.
+- [3] *Radio Regulations*, ITU, Geneva, 1994.
+- [4] *List of Coast Stations*, ITU, Geneva, 1993.
+- [5] *List of Ship Stations*, ITU, Geneva, 1995.
+- [6] *Instructions for the International telephone service*, ITU, Geneva, 1993.
\ No newline at end of file
diff --git a/marked/F/T-REC-F.122-198811-I_PDF-E/raw.md b/marked/F/T-REC-F.122-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..e8869dcdb21001caab210aeee59e4768f5c9d13b
--- /dev/null
+++ b/marked/F/T-REC-F.122-198811-I_PDF-E/raw.md
@@ -0,0 +1,379 @@
+
+
+![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**
+
+**F.122**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**OPERATIONS AND QUALITY OF SERVICE  
+MOBILE SERVICE**
+
+---
+
+**OPERATIONAL PROCEDURES FOR  
+THE MARITIME SATELLITE DATA  
+TRANSMISSION SERVICE**
+
+**ITU-T Recommendation F.122**
+
+(Extract from the *Blue Book*)
+
+---
+
+# NOTES
+
+1 ITU-T Recommendation F.122 was published in Fascicle II.4 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.
+
+# **OPERATIONAL PROCEDURES FOR THE MARITIME SATELLITE DATA TRANSMISSION SERVICE**
+
+## **1 Introduction**
+
+1.1 The purpose of this Recommendation is:
+
+- a) to standardize the procedures for subscribers of a public data network (PDN) calling ship earth stations in the Maritime Satellite Data Transmission Service;
+- b) to standardize the procedures for calling subscribers of a PDN from ship earth stations using the packet switched data transmission service defined in Recommendations X.25 and X.352;
+- c) to standardize the procedures for calling subscribers of a PDN from ship earth stations by accessing packet assembly/disassembly facilities (PAD) as defined in Recommendation X.351.
+
+*Note 1* - This Recommendation does not cover data calls passed through the international public switched telephone network other than those which are accessed through PADs designed in accordance with Recommendation X.351.
+
+*Note 2* - Procedures for subscribers of a PDN calling a ship earth station by accessing a PAD are for further study.
+
+1.2 Related CCITT Recommendations are:
+
+- E.200/F.110 Operational provisions for the maritime mobile service.
+- E.210/F.120 Ship station identification for VHF/UHF and Maritime Mobile-Satellite Services.
+- E.215 Telephone/ISDN numbering plan for the Mobile-Satellite Service of INMARSAT.
+- E.216 Selection procedure for the INMARSAT mobile-satellite telephone and ISDN services.
+- F.125 Telex numbering plan for the Mobile-Satellite Service of INMARSAT.
+- F.126 Selection procedures for the INMARSAT Mobile-Satellite Telex Service.
+- X.1 International user classes of service in public data networks and ISDNs.
+- X.2 International data transmission services and optional user facilities in public data networks.
+- X.96 Call progress signals in public data networks.
+- X.121 International numbering plan for public data networks.
+- X.180 Administrative arrangements for international closed user groups (CUGs).
+- X.300 General principles and arrangements for interworking between public data networks, and between public data networks and other public networks.
+- X.350 General interworking requirements to be met for data transmission in the international public mobile satellite systems.
+- X.351 Special requirements to be met for packet assembly/disassembly facilities (PADS) located at or in association with coast earth stations in the Maritime Satellite Service.
+- X.352 Interworking between packet switched public data networks and the public maritime mobile satellite data transmission system.
+- X.353 Routing principles for interworking public maritime mobile satellite data transmission systems in the public data network.
+
+1.3 The following basic considerations were taken into account when formulating this Recommendation:
+
+- a) Each ship is allocated a unique 9-digit INMARSAT mobile number.
+
+*Note* - The first generation maritime mobile satellite (INMARSAT) system also caters for a 7-digit INMARSAT mobile number beginning with digit 1.
+
+- b) The routing principles to be used for data transmission to and from ships are as defined in Recommendation X.353.
+
+- c) The procedures to be used on board ships when accessing a subscriber of a PDN should be as similar as possible to the procedures used on PDNs.
+  - d) The Maritime Satellite Service is international in nature and international procedures will be adopted to provide access to this service. For some purposes, a maritime satellite data transmission system can be regarded as analogous to a national network and the ship earth stations as subscribers within that network.
+  - e) The procedures used on board the ship when accessing a subscriber of a PDN should be the same in all coast earth stations.
+- 1.4 The following basic access methods are defined for the Maritime Satellite Data Transmission Service:
+- a) access using the packet mode in accordance with draft Recommendation X.352;
+  - b) access using packet assembly/disassembly facilities (PADS) in accordance with Recommendation X.351.
+- 1.5 Ships may form part of a closed user group (CUG) in accordance with Recommendation X.180. It should be noted that a ship being part of a CUG should be known as such in all coast earth stations.
+
+The International Maritime Satellite Organization (INMARSAT) should be charged with the responsibility of acting as the coordinating Administration (see Recommendation X.180) for ship earth stations wanting to form CUGS. The application from ships to join or cease membership of a CUG should be forwarded through INMARSAT who should then inform the coordinating Administration of the CUG in accordance with Recommendation X.180.
+
+For each CUG the same index identifying the CUG by a calling ship earth station (see Recommendation X.300) should be used in all coast earth stations in order to simplify the calling procedures. The index should be coordinated through INMARSAT.
+
+1.6 Permanent virtual circuits (PVC) would require a permanent circuit between a ship earth station and the coast earth station. The PVC service should not normally be offered to ship earth stations (see also Recommendations X.2 and X.350).
+
+## 2 Procedures for ship originated calls
+
+### 2.1 Access to packet switched PDNs
+
+#### 2.1.1 Calling a subscriber of a PDN
+
+2.1.1.1 The coast earth station through which the call is to be set up is selected by procedures defined within the INMARSAT system.
+
+2.1.1.2 The ship board subscriber should select a prefix followed by the full international number of the called DTE. Hence, the numbering sequence selected by a ship board subscriber will be as shown in Table 1/F.122 or, where an integrated numbering system exists within a country, as shown in Table 2/F.122.
+
+TABLE 1/F.122
+
+|                                   |                                  |
+|-----------------------------------|----------------------------------|
+| 0                                 | Prefix                           |
+| DNIC                              | Data network identification code |
+| N <sub>1</sub> ... N <sub>n</sub> | Network terminal number          |
+
+TABLE 2/F.122
+
+|                                   |                      |
+|-----------------------------------|----------------------|
+| 0                                 | Prefix               |
+| DCC                               | Data country code    |
+| N <sub>1</sub> ... N <sub>n</sub> | National data number |
+
+See also Recommendations X.121 and X.350.
+
+2.1.1.3 The calling DTE address of the ship board DTE should always be inserted and have the following format:
+
+$$TX_1, X_2 \dots X_8 Y$$
+
+where  $TX_1, X_2 \dots X_8$  is the INMARSAT mobile number as defined in Recommendation F.125 and Y is an optional digit identifying a specific DTE on board the ship. If the ship is equipped with only one DTE, the digit Y should be omitted. The calling DTE address should not include the prefix and the DNIC allocated to the ocean area in which the ship earth station is located at the time of the call.
+
+2.1.1.4 Selection of facilities on a call-by-call basis should be in accordance with Recommendations X.25 and X.300. The facilities that may be offered on a call-by-call basis are given in Recommendation X.2. A given facility may not be offered in all coast earth stations.
+
+User facilities that have to be agreed for a contractual period are also listed in Recommendation X.2. The application for a given facility should be made with the Administrations operating coast earth stations providing access to public packet switched data networks. The availability of user facilities on the various coast earth stations should be coordinated and be disseminated to ships by INMARSAT; however, the decision to implement a given user facility should be made by each coast earth station owner.
+
+Further study is required to determine which user facilities and/or other user parameters should be offered on all coast earth stations.
+
+*Note* - Separate provisions apply to closed user groups as described in § 1.5 above.
+
+#### 2.1.2 Use of data transmission prefixes
+
+2.1.2.1 Annex A to Recommendation F.126 defines data transmission prefixes for accessing special terminations. The general called DTE address format when accessing such a termination will be as shown in Table 3/F.122.
+
+TABLE 3/F.122
+
+|                                   |                                                             |
+|-----------------------------------|-------------------------------------------------------------|
+| P <sub>1</sub> P <sub>2</sub>     | Two-digit prefix defined in Annex A to Recommendation F.126 |
+| A <sub>1</sub> ... A <sub>k</sub> | Optional digits                                             |
+
+Optional digits may be a data country code (DCC), a data network identification code (DNIC) or other additional digits.
+
+2.1.2.2 The calling DTE address should have the format defined in § 2.1.1.3 above.
+
+2.1.2.3 Selection of facilities, if required, should be as defined in § 2.1.1.4 above.
+
+2.1.2.4 The use of some prefixes could be barred to some customers.
+
+2.1.2.5 The prefix will be sent on the radio path to the coast earth station but would not be used outside the satellite system. The prefix will be converted at the coast earth station, if required, to the data number associated with the appropriate destination.
+
+#### 2.1.3 Ship-to-ship calls
+
+For ship-to-ship calls the called DTE address should have the composition shown in Table 4/F.122.
+
+TABLE 4/F.122
+
+|   |                                                   |                                                  |
+|---|---------------------------------------------------|--------------------------------------------------|
+| 0 |                                                   | Prefix                                           |
+|   | 111S                                              | DNIC allocated to the Maritime Satellite Service |
+|   | TX <sub>1</sub> X <sub>2</sub> ... X <sub>8</sub> | INMARSAT mobile number                           |
+|   | Y                                                 | Optional digit to designate a particular DTE     |
+
+The digit S determines the ocean area in which the called ship is located. The values for the digit S are given in Recommendation X.121. The digit Y identifies a specific DTE on board the ship.
+
+#### 2.1.4 Call progress signals and diagnostic codes
+
+Call progress signals and diagnostic codes may be received in accordance with § 8.2 of Recommendation X.350.
+
+#### 2.1.5 CCITT standardized services
+
+Ships should have full access to CCITT standardized services offered on public data networks such as Teletex, Videotex, and facsimile in accordance with relevant F and S Series Recommendations.
+
+### 2.2 Access to PADs
+
+2.2.1 Ships with start-stop mode DTEs may be offered access to packet switched public data networks through PADs.
+
+PADs associated with coast earth stations are defined in Recommendation X.351. These PADs are defined in such a way that identical procedures may be used when working towards PADs located at different coast earth stations.
+
+*Note* - Ships may also access a national PAD in a country, but in such cases special procedures only applicable for that PAD would be required. Only PADs designed in accordance with Recommendation X.351 are considered in this Recommendation.
+
+#### 2.2.2 Telephone access procedure
+
+The coast earth station at which the PAD is located is selected in accordance with INMARSAT procedures for telephone calls. The start-stop mode DTE on board the ship would use telephone procedures in order to access a PAD. When the telephone circuit has been established, i.e. when the dial tone is heard, the following digits have to be dialled:
+
+20            Prefix
+
+X<sub>1</sub> X<sub>2</sub>    Digits indicating required data rate
+
+Recommendation X.351 specifies that the following data rates and types of modem for full duplex operation will be supported by the PAD:
+
+- Recommendation V.21, 300 bit/s;
+- Recommendation V.22, 1200 bit/s;
+- Recommendation V.23, 75/1200 bit/s.
+
+The specific modes of operation of the modems are given in Recommendation X.351, § 1.1.
+
+The number to be dialled for each of these data rates is given in Table 5/F.122.
+
+TABLE 5/F.122
+
+| Data rate (bit/s) | Dialling sequence |
+|-------------------|-------------------|
+| 300               | 2002              |
+| 1200              | 2003              |
+| 75/1200           | 2011              |
+
+The PAD may support other data rates on an optional basis. For such data rates the dialling information will be as given in Table 2/X.351.
+
+The dialling sequences 2050 through 2099 are reserved for national use and may be used for access to for example Videotex data bases via the PAD.
+
+#### 2.2.3 *Data access procedures*
+
+The call control procedures to be used during set-up and clearing of the data connection and the data transfer protocol are given in Recommendation X.351.
+
+The basic elements of the procedure are:
+
+First the DTE accesses the PAD by sending a service request signal consisting of the characters “.” (full stop) and “CR” (carriage return) corresponding to the characters 2/14 0/13 of International Alphabet No. 5 (see Recommendation T.50 for a description of International Alphabet No. 5.
+
+The PAD will respond by returning a PAD identification signal, the composition of which is left to the Administration operating the PAD.
+
+The DTE shall then send, as soon as possible, a signal, i.e. a string of characters, called the selection PAD command signal. This signal is composed as shown in Annex A. The purpose of this signal is:
+
+- to provide the PAD with the address of the called DTE; and
+- to provide the PAD with the identity of the calling DTE.
+
+When the call has been extended to the called DTE, the character string COM will be received from the PAD.
+
+At this stage the system enters into the data transfer phase.
+
+The call set-up procedure outlined above may be operated manually or be programmed into the DTE.
+
+During call set-up and during the data transfer phase, the DTE may receive PAD service signals as defined in Recommendation X.28. These signals may indicate various call failures.
+
+Recommendation X.351 also allows other procedures to be used during call set-up. See that Recommendation for further details.
+
+#### 2.2.4 *Standard profile and profile selection*
+
+In order to operate a PAD, a number of PAD parameters must be specified. A general list of PAD parameters is contained in Recommendation X.3.
+
+The PAD defined in Recommendation X.351 offers an initial standard profile with PAD parameter values as given in Table 3/X.351. This standard profile permits a data transfer protocol based on International Alphabet No. 5.
+
+The characters 1/0 (DLE), 1/1 (DC1) and 1/3 (DC3) are used for control purposes and can therefore not be passed transparently through the PAD. The character 1/0 (DLE) is interpreted by the PAD as an escape from the data transfer phase. Therefore, this character is used in order to enable commands to be sent to the PAD. For the various commands that can be used during the data transfer phase, see Recommendation X.28.
+
+The initial standard profile offers the following capabilities:
+
+- by using the character 1/0 (DLE) commands can be sent to the PAD;
+- the PAD can at any time send service signals to the DTE;
+
+- the DTE can use characters in order to indicate when a data packet shall be sent from the PAD into the data network;
+- the DTE may use the characters 1/1 (DC1) and 1/3 (DC3) for flow control.
+
+The profile does not permit the PAD to provide for any editing functions. Characters which are entered into the PAD are not echoed to the DTE. This has been done because the echoed character will be delayed by approximately 0.6 seconds, thus reducing the character rate to less than two characters per second. The echo mode should therefore not be used. If echo is required, it should be generated locally in the DTE.
+
+A transparent profile or any other profile standardized in Recommendation X.28 may be selected as soon as the data transfer phase is entered by procedures defined in Recommendations X.28 and X.351. The transparent profile will allow octets of data to be passed transparently between the two DTEs. When operating in this mode, the on-board DTE cannot recall the PAD, nor can the PAD send any service signals to the on-board DTE. Therefore, a data transfer protocol must exist between the two DTEs for proper call control.
+
+The various PAD parameters which can be selected by the DTE are given in Recommendation X.3. It should be noted that some of these parameters may not be implemented on all PADS.
+
+Since DTEs may treat the parity bit included in the data octets differently when International Alphabet No. 5 is used, Recommendation X.351 specifies the means by which this problem can be resolved.
+
+#### 2.2.5 Clearing of calls
+
+At the end of the call the user at the on-board DTE should make sure that the satellite telephone circuit is properly cleared. The PAD may include provisions for clearing the circuit but this may delay the clearing for several minutes. During this time, the user on-board is still being charged for the use of a maritime satellite telephone circuit.
+
+## 3 Procedures for shore-to-ship calls
+
+### 3.1 Calls to ships with DTEs operating in the packet mode
+
+3.1.1 A subscriber of a PDN calling a ship equipped with DTEs operating in the packet mode will select a numbering sequence as shown in Table 6/F.122.
+
+3.1.2 The numbering sequence requires the subscriber to know the satellite coverage area in which the ship is located in order to select the S digit. The values for the digits are given in Recommendation X.121.
+
+TABLE 6/F.122
+
+|   |     |   |                                                   |                                                     |
+|---|-----|---|---------------------------------------------------|-----------------------------------------------------|
+| P |     |   |                                                   | International prefix (if required)                  |
+|   | 111 |   |                                                   | Martitime data country code                         |
+|   |     | S |                                                   | Ocean area code                                     |
+|   |     |   | TX <sub>1</sub> X <sub>2</sub> ... X <sub>8</sub> | INMARSAT mobile number                              |
+|   |     |   |                                                   | Y      Optional digit to designate a particular DTE |
+
+3.1.3 Facility selection will follow the normal procedures used in the PDN of origin.
+
+3.1.4 The calling subscriber should be aware of the long two-way transmission delay (approximately 0.6 seconds) on the maritime satellite circuit. This implies that acknowledgement signals may be delayed more than for terrestrial connections.
+
+3.1.5 Call progress signals and diagnostic codes may be received in accordance with Recommendation X.350, § 8. 1.
+
+3.1.6 When accessing a ship for CCITT standardized services such as Teletex, Videotex and facsimile, the calling subscriber should make sure before initiating the call that the called ship is equipped with the appropriate termination.
+
+### 3.2 Calls to ships with DTEs operating in the start-stop mode
+
+For further study.
+
+## 4 Group calls
+
+Group calls to ship earth stations are calls comprising a message sent simultaneously to all ships within a predetermined group. The group numbering scheme is given in Annex B of Recommendation F.125.
+
+Group calls using direct access through a PDN will not be permitted.
+
+Other means for setting up group calls through public data networks, e.g. by using a message handling system (MHS), are for further study.
+
+## ANNEX A
+
+(to Recommendation F.122)
+
+### Format of selection PAD command signal for maritime satellite applications
+
+#### A.1 General format
+
+The general format of the selection PAD command signal is given in Recommendation X.28 and is composed as shown in Figure A-1/F.122.
+
+![](b28af4985cdef1e519e3aaf26561dcb3_img.jpg)
+
+Beginning of signal  
+↓
+
+|                         |   |  |   |                         |   |                           |                 |
+|-------------------------|---|--|---|-------------------------|---|---------------------------|-----------------|
+| Facility request signal | , |  | , | Facility request signal | – | Called DTE address signal | (CR)<br>or<br>+ |
+|-------------------------|---|--|---|-------------------------|---|---------------------------|-----------------|
+
+FIGURE A-1/F.122
+
+The character 2/12 (,) is used as a separator between facility request signals and the character 2/13 (–) is used as a separator between the facility request block and the called DTE address signal. The selection PAD command signal is terminated by either of the characters 0/13 (CR) or 2/11 (+).
+
+The facility request block must contain the network user identification (NUI) facility request signal. Other facility request signals are optional.
+
+If the PAD receives a selection PAD command signal with a separator character 2/12 (,) followed by an empty facility request field, the signal will be accepted provided that the other fields of the signal are accepted.
+
+The inclusion of user data in the selection PAD command signals is for further study.
+
+#### A.2 Network user identification (NUI) facility request signal
+
+##### A.2.1 Format of the NUI facility request signal
+
+The NUI facility request signal shall have the format of Figure A-2/F.122 and be sent in the order shown.
+
+Beginning of signal
+
+↓
+
+|   |                                                                 |               |
+|---|-----------------------------------------------------------------|---------------|
+| N | 9 digit INMARSAT mobile number<br>(Recommendations E.215/F.125) | Mnemonic code |
+|---|-----------------------------------------------------------------|---------------|
+
+FIGURE A-2/F.122
+
+N is the character 4/14 (N) of International Alphabet No. 5. The mnemonic code of the NUI facility request signal may consist of 1 to 4 characters in columns 2 to 7 of International Alphabet No. 5, except 2/0 (SP), 7/15 (DEL), 2/13 (-), 2/12 (,) and 2/11 (+).
+
+##### A.2.2 *Validation of the NUI facility request signal*
+
+The coast earth station will check the general authorization of the calling ship for access to the INMARSAT system. Therefore, validation of the NUI facility request signal may be limited to the mnemonic code. However, the possibility of fraudulent calling would be reduced if the ship station identity is also included in the validation.
+
+The ship station identity may also be used for identifying the calling ship for charging purposes, and for insertion of the calling DTE in the call request packet.
+
+#### A.3 *Composition of the called DTE address signal*
+
+#### A.3.1 *Calls to a DTE of a PDN*
+
+The called DTE address signal shall consist of the prefix 0 followed by the full international number of the called DTE. This applies also when the called DTE is located in the same country as the maritime PAD.
+
+#### A.3.2 *Calls to special destinations*
+
+Annex A of Recommendation X.350 defines two-digit prefixes for access to special destinations. For calls to such destinations the called DTE address shall consist of the two-digit prefix, optionally followed by additional digits.
+
+### A.4 *Optional facilities*
+
+Facilities to be offered in a maritime PAD is to be determined by the Administration concerned.
+
+The shipboard DTE may request available facilities in accordance with the procedures given in Recommendation X.28.
\ No newline at end of file
diff --git a/marked/F/T-REC-F.130-198811-I_PDF-E/raw.md b/marked/F/T-REC-F.130-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..78c8793f72fac8a53b1f108c2f63b9244512b01d
--- /dev/null
+++ b/marked/F/T-REC-F.130-198811-I_PDF-E/raw.md
@@ -0,0 +1,86 @@
+
+
+![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**
+
+**F.130**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**OPERATIONS AND QUALITY OF SERVICE  
+MOBILE SERVICE**
+
+---
+
+**MARITIME ANSWER - BACK CODES**
+
+**ITU-T Recommendation F.130**
+
+(Extract from the *Blue Book*)
+
+---
+
+# NOTES
+
+1 ITU-T Recommendation F.130 was published in Fascicle II.4 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.
+
+# **MARITIME ANSWER-BACK CODES**
+
+The CCITT,
+
+*considering*
+
+(a) that it is technically feasible to interconnect certain radiocommunication systems in the Maritime Mobile Service<sup>1)</sup> with the international telex network in order to provide a radiotelex service between ships and telex subscribers, in accordance with Recommendation F.110;
+
+(b) that Recommendation F.60 specifies the operational provisions for the international telex service, and in particular, for the composition of answer-back codes;
+
+(c) that, since no single Administration is responsible for the allocation of answer-back codes to ships in the way that such codes are administered in individual national telex networks, some rules further to those set down in Recommendation F.60 are desirable, for example to facilitate automatic operation in the ship-to-shore direction and to simplify the handling of inquiries concerning calls to or from ships;
+
+(d) that, to the extent possible, the alphabetic portion of maritime answer-back codes should provide a means for detecting possible mutilation of the numerical portion, particularly in the case of ship-to-shore calls where it may be used for charging and accounting purposes,
+
+*unanimously declares*
+
+that, at least in cases where interconnection with the international telex network is desired, answer-back codes generated by teleprinters (or equivalent terminal devices) on ships shall comply with the following requirements.
+
+**1** Regardless of the transmission medium used (e.g. maritime-mobile satellite, HF "direct printing", VHF), the answer-back code, as printed out for a distant subscriber, shall include the following three components in the order indicated:
+
+- a) the "ship station's number" of 6, 7, 8 or 9 digits (see § 2 below);
+- b) the "ship's (abbreviated) name" of 4 letters (see § 3 below);
+- c) the letter X, preceded by a space, as a "telex network identification code" reserved for mobile stations (see Recommendation F.68).
+
+**2** The 6, 7, 8 or 9 digits of the ship station's number are those allocated by the licensing Administration in accordance with Recommendation F.120 but with the final 3, 2 or 1 zeroes deleted for 6, 7 or 8-digit numbers respectively.
+
+**3** The letters comprising the ship's (abbreviated) name [§ 1b) above] should be chosen with the guidance and under the control of the licensing Administration with a view not only to identifying the ship (or the company, or the fleet, as is most appropriate) in a clear manner for a distant subscriber, but also to providing a means for checking the ship station's number as recorded in the answer-back code. The name should not include shifts, figures or signs. Where a ship has been allocated a 6, 7 or 8-digit number, in principle the ship's (abbreviated) name should not need to be changed when the numbering plan is modified to incorporate 7, 8 or 9-digit numbers.
+
+**4** The series of twenty combinations in International Telegraph Alphabet No. 2 comprising the answer-back code shall be allocated as follows:
+
+---
+
+<sup>1)</sup> As in Recommendation F.110 and F.111, the term Maritime Mobile Service is intended to include also the Maritime Mobile-Satellite Service.
+
+- a) figure-shift, or (if permanently fitted) letter-shift;
+- b) carriage-return;
+- c) line-feed;
+- d) the ship station's number, or (if a letter-shift is fitted in the first position) figure-shift followed by the ship station's number;
+- e) letter-shift;
+- f) space, which should however be omitted if both the ship station's number consists of 8 digits and a letter-shift is fitted in the first position;
+- g) the ship's (abbreviated) name;
+- h) space;
+- i) if necessary, a letter-shift or letter-shifts to bring the total number of combinations in the answer-back code up to twenty;
+- j) the letter X;
+- k) letter-shift (if permanently fitted).
+
+5 The technical requirements for answer-back generators are laid down in Recommendation S.6.
+
+6 In accordance with Recommendation S.6, it is preferred that teleprinters having all 20 positions in the answer-back which are freely assignable should be used in the future, i.e. where the first position is a figure-shift and the last the letter X. In the meantime, teleprinters that have a letter-shift permanently fitted in the first and last positions of the answer-back code may be used where the ship station's number does not exceed 8 digits.
\ No newline at end of file
diff --git a/marked/F/T-REC-F.131-198811-I_PDF-E/raw.md b/marked/F/T-REC-F.131-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..efe7ac505d645aab95bcf9c5d1e682aec1e17855
--- /dev/null
+++ b/marked/F/T-REC-F.131-198811-I_PDF-E/raw.md
@@ -0,0 +1,69 @@
+
+
+![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**
+
+**F.131**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**OPERATIONS AND QUALITY OF SERVICE  
+MOBILE SERVICE**
+
+---
+
+**RADIOTELEX SERVICE CODES**
+
+**ITU-T Recommendation F.131**
+
+(Extract from the *Blue Book*)
+
+---
+
+# NOTES
+
+1 ITU-T Recommendation F.131 was published in Fascicle II.4 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.
+
+# **RADIOTELEX SERVICE CODES**
+
+The CCITT,
+
+*considering*
+
+(a) that it is technically feasible to interconnect certain radiocommunication systems in the Maritime Mobile Service and the Maritime Mobile-Satellite Service with the international telex network in order to provide a radiotelex service between ships and telex subscribers in accordance with Recommendation F. 110;
+
+(b) that Recommendation F.60 specifies the code expressions used for service correspondence in the international telex service;
+
+(c) that whilst it is desirable for the same service code expressions to be used in the radiotelex service as in the international telex service, because of the nature of the service the reasons for the uses of these codes may vary;
+
+(d) that agreement as to the circumstances when specific codes are used is desirable,
+
+*recommends the following*
+
+(1) In general for shore-to-ship calls the telex service codes specified in Recommendation F.60 should be used. However, the telex service codes listed below should be used by the radiotelex service in the following circumstances:
+
+- ABS** – *Absent subscriber/office closed* (to be used when radio contact cannot be established, i.e. radio equipment is faulty, the ship is outside the coverage area or the terminal is turned off);
+- DER** – *Out of order* (to be used when the radio path and associated handshaking procedure is accomplished normally but the teleprinter fails to respond to the **WRU** signals);
+- NC** – *No circuits* (to be used when congestion occurs in either the network or switching equipment);
+- NP** – *The called party is not or is no longer a subscriber* (to be used when the ship number received is invalid);
+- NA** – *Correspondence with this subscriber is not admitted* (to be used if the ship's number is barred or if unauthorized group calls are attempted);
+- OCC** – *Subscriber engaged* (to be used if the ship station is engaged)
+
+*Note* – See also Recommendation U.61 [1].
+
+(2) For ship-to-shore calls all service codes generated in the international telex service, as specified in Recommendation F.60, should be capable of being returned and presented to the calling ship subscriber.
+
+# **Reference**
+
+- [1] CCITT Recommendation *Detailed requirements to be met in interfacing the international telex network with maritime satellite systems*, Recommendation U.61.
\ No newline at end of file
diff --git a/marked/F/T-REC-F.19-199610-I_PDF-E/raw.md b/marked/F/T-REC-F.19-199610-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..86c318b0e68c1261632069773bcd3f1aae098ee5
--- /dev/null
+++ b/marked/F/T-REC-F.19-199610-I_PDF-E/raw.md
@@ -0,0 +1,199 @@
+
+
+![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
+
+**F.19**
+
+(10/1996)
+
+**SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES**
+
+Telegraph service – Operating methods for the  
+international public telegram service
+
+---
+
+**Collection and dissemination of official service  
+information**
+
+ITU-T Recommendation F.19
+
+---
+
+# ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                        |                 |
+|------------------------------------------------------------------------|-----------------|
+| <b>TELEGRAPH SERVICE</b>                                               |                 |
+| <b>Operating methods for the international public telegram service</b> | <b>F.1–F.19</b> |
+| The gentex network                                                     | F.20–F.29       |
+| Message switching                                                      | F.30–F.39       |
+| The international telemessage service                                  | F.40–F.58       |
+| The international telex service                                        | F.59–F.89       |
+| Statistics and publications on international telegraph services        | F.90–F.99       |
+| Scheduled and leased communication services                            | F.100–F.104     |
+| Phototelegraph service                                                 | F.105–F.109     |
+| <b>MOBILE SERVICE</b>                                                  |                 |
+| Mobile services and multdestination satellite services                 | F.110–F.159     |
+| <b>TELEMATIC SERVICES</b>                                              |                 |
+| Public facsimile service                                               | F.160–F.199     |
+| Teletex service                                                        | F.200–F.299     |
+| Videotex service                                                       | F.300–F.349     |
+| General provisions for telematic services                              | F.350–F.399     |
+| <b>MESSAGE HANDLING SERVICES</b>                                       |                 |
+| <b>DIRECTORY SERVICES</b>                                              |                 |
+| <b>DOCUMENT COMMUNICATION</b>                                          |                 |
+| Document communication                                                 | F.550–F.579     |
+| Programming communication interfaces                                   | F.580–F.599     |
+| <b>DATA TRANSMISSION SERVICES</b>                                      |                 |
+| <b>AUDIOVISUAL SERVICES</b>                                            |                 |
+| <b>ISDN SERVICES</b>                                                   |                 |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                            |                 |
+| <b>HUMAN FACTORS</b>                                                   |                 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## **ITU-T Recommendation F.19**
+
+## **COLLECTION AND DISSEMINATION OF OFFICIAL SERVICE INFORMATION**
+
+### **Source**
+
+ITU-T Recommendation C.2 was revised by ITU-T Study Group 1 (1993-1996) and approved by WTSC on 18 October 1996. It was then renumbered by ITU-T Study Group 2 (2001-2004) as F.19 on 25 January 2002 without further modifications.
+
+## 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 Conference (WTSC), 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 WTSC 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 Service information requirements .....                           | 1    |
+| 2 Collection of data for <i>official</i> service information ..... | 2    |
+| 3 TSB administrative support.....                                  | 2    |
+
+
+
+## **COLLECTION AND DISSEMINATION OF OFFICIAL SERVICE INFORMATION**
+
+*(Approved as ITU-T C.2 in Helsinki, 1993; revised in Geneva, 1996, renumbered as F.19 in 2002)*
+
+The ITU-T,
+
+*considering*
+
+- a) Article 1 of the *Constitution* (Geneva, 1992) and Article 15 of the *Convention* (Geneva, 1992);
+- b) Article 8 of the *International Telecommunication Regulations* (Melbourne, 1988);
+- c) Resolution 21 adopted by the World Telecommunication Standardization Conference (Helsinki, 1993) and the results of the ITU-T studies undertaken pursuant to that Resolution;
+- d) Resolutions 39, 65 and 66 adopted by the Plenipotentiary Conference of the International Telecommunication Union (Kyoto, 1994),
+
+*recognizing*
+
+- a) that the TSB's collection and dissemination of official service information of an administrative, operational, tariff and statistical nature (hereinafter referred to as *official service information*) assists Administrations and ROAs in their efficient administration and provision respectively of international telecommunication services;
+- b) that the *ITU Operational Bulletin* has provided an effective method of promulgating much of this type of information;
+- c) that the decision for the ITU-T to collect and to disseminate official service information should be taken with a view to cost-effectiveness as regards the burden both:
+  - on Administrations and ROAs in providing the information; and
+  - on the TSB in the preparation and dissemination of that information;
+- d) that ROAs also exchange information of an operational nature directly among themselves, and that in some cases (e.g. where many ROAs are affected) some standardization of the content and/or format of the information exchanged may be desirable,
+
+*recommends*
+
+that the following general principles should be applied regarding the collection and dissemination of service information, particularly the *official service information* disseminated by the TSB.
+
+### **1 Service information requirements**
+
+**1.1** Whenever a Study Group identifies a new requirement (or the need for a major change in the existing arrangements) for collection and dissemination of service information:
+
+- a) it should consider whether the relevant ROAs (and/or Administrations) should communicate such service information among themselves directly; or
+- b) if ITU involvement is desired, the Director of the TSB shall be consulted concerning the justification for that involvement, taking into account the perceived market needs, ITU budget considerations, and any other ITU administrative implications before proceeding.
+
+**1.2** In cases a) and b), the requirement should be laid down within ITU-T Recommendations. The relevant Recommendation should specify unambiguously and at least in general terms the nature of the different types of information required. Where appropriate, it may also specify the format, periodicity, entry into effect, and/or procedures for updating the relevant service information.
+
+**1.3** In case a), the information exchanged is not regarded as *official* service information. Nevertheless, in some cases it may be appropriate to specify that each source ROA (or Administration) should supply a copy of the information or a summary of it to the TSB.
+
+1.4 Each Study Group responsible for the maintenance of such Recommendations shall review the relevant provisions at least once towards the end of each period between two WTSCs.
+
+### 2 Collection of data for *official* service information
+
+2.1 The Director of the TSB should request Administrations and/or ROAs to supply official service information, or any changes to previously supplied information, for dissemination in accordance with the provisions of the relevant Recommendations. The form of the request should be designed to minimize the effort required of the Administrations and/or ROAs in providing the information requested.
+
+2.2 Administrations (and/or ROAs) should reply to such requests for information, to the extent practicable, in a timely fashion and in accordance with national arrangements, taking due account of the confidentiality of possibly commercially sensitive information.
+
+2.3 Upon receipt of a request for official service information, Administrations may elect (on a *case-by-case* basis or an *until-further-notice* basis), in accordance with national practice, to make arrangements to collate replies from their ROAs. Any Administration exercising such election shall notify the Director of the TSB. Absent such election and notification, the TSB should expect individual replies from the ROAs. In processing the individual replies, the TSB shall consider them as emanating from an ROA duly authorized by the relevant Member (or its Administration) to offer the relevant telecommunication service(s) to which the request for information pertains.
+
+### 3 TSB administrative support
+
+3.1 The Director of the TSB provides advice and support to the various Study Groups responsible for the Recommendations requiring the collection and dissemination of official service information, in particular as outlined in 1.1, 2.1 and 2.3 above.
+
+3.2 In addition, and in view of the responsibilities vested in his office, the Director makes suitable arrangements:
+
+- a) to establish and to keep up to date, for each Study Group, a list of those Recommendations that require the collection and dissemination of official service information;
+- b) to submit such a list to each Study Group concerned on request, and in any case at least twelve months prior to a WTSC, for possible revision (amendments, additions and/or deletions) in the light of operational experience;
+- c) to ensure that the method of disseminating official service information reflects technical developments in the means of collecting and exchanging such information and that the most appropriate and economic solutions are adopted, while taking due account of the needs of countries where electronic access to ITU databases, for example, is not yet available;
+- d) to establish and to keep up to date on the basis of the responses returned, a list of the relevant service and/or network providers that have provided the official service information and whether their status is that of an Administration, ROA or other entity.
+
+
+
+## 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                                              |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                |
+| 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/F/T-REC-F.190-199208-I_PDF-E/raw.md b/marked/F/T-REC-F.190-199208-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c427e7830af3cd47b8e573b1652becbcf052ad25
--- /dev/null
+++ b/marked/F/T-REC-F.190-199208-I_PDF-E/raw.md
@@ -0,0 +1,172 @@
+
+
+![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
+
+**CCITT**
+
+**F.190**
+
+THE INTERNATIONAL  
+TELEGRAPH AND TELEPHONE  
+CONSULTATIVE COMMITTEE
+
+(08/92)
+
+**TELEMATIC, DATA TRANSMISSION,  
+ISDN BROADBAND, UPT  
+AND TELECONFERENCE SERVICES:  
+OPERATIONS AND QUALITY OF SERVICE**
+
+---
+
+**OPERATIONAL PROVISIONS FOR THE  
+INTERNATIONAL FACSIMILE SERVICE  
+BETWEEN PUBLIC BUREAUX AND  
+SUBSCRIBER STATIONS AND VICE VERSA  
+(BUREAUFAX-TELEFAX AND VICE VERSA)**
+
+**Recommendation F.190**
+
+---
+
+![CCITT logo: A globe with the letters CCITT.](84a1d09fb489061482111515543b60dc_img.jpg)
+
+CCITT logo: A globe with the letters CCITT.
+
+Geneva, 1992
+
+# FOREWORD
+
+The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT 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 Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988).
+
+Recommendation F.190 was revised by Study Group I and was approved under the Resolution No. 2 procedure on the 4th of August 1992.
+
+## --- CCITT NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized private operating agency.
+
+
+
+## Recommendation F.190
+
+## OPERATIONAL PROVISIONS FOR THE INTERNATIONAL FACSIMILE SERVICE BETWEEN PUBLIC BUREAUX<sup>1)</sup> AND SUBSCRIBER STATIONS AND VICE VERSA (BUREAUFAX-TELEFAX AND VICE VERSA)
+
+*(revised 1992)*
+
+### 1 General
+
+1.1 Recommendation F.160 lays down general provisions for all forms of international public facsimile services. The specific provisions concerning international public facsimile service between public bureaux (bureaufax) and between subscriber stations are contained in Recommendations F.170, F.171, F.180, F.182 and F.184.
+
+1.2 With a view of increasing the flexibility and range of these facsimile services, this Recommendation deals with the international transmission of facsimile documents:
+
+- a) from a public bureau to a subscriber facsimile station (public-to-private); and
+- b) from a subscriber facsimile station to a public bureau (private-to-public).
+
+1.3 Since the methods of operation do not involve the participation of a public bureau at both ends of the connection, the quality of reproduction and speed of delivery normally available in the conventional bureaufax service may not be attainable.
+
+1.4 In accordance with Recommendation F.170, facsimile terminals should have automatic operation of the called station. The operational procedures applicable in relations between the different types of stations are set out in the relevant Recommendations in the T-Series.
+
+1.5 The relevant tariff provisions may be found in Recommendation D.73.
+
+### 2 “Public-to-private” transmission
+
+2.1 Except where contrary provisions are published by the terminal Administrations concerned, “public-to-private” facsimile transmission is permitted.
+
+2.2 The accepting public bureau should ask the sender of the document or his authorized representative for the following information before accepting the document for transmission:
+
+- a) the CCITT group of the destination subscriber's facsimile terminal;
+- b) the destination facsimile terminal call number.
+
+On accepting the facsimile document, the public bureau can use, if appropriate, the bureaufax transmittal sheet in accordance with Recommendation F.170 and provide the necessary information in the corresponding boxes.
+
+2.3 In those cases where:
+
+- a) the accepting public bureau considers that the quality of the document to be transmitted is unsuitable for satisfactory facsimile transmission; or
+- b) the sender is unsure of the CCITT group of the destination facsimile machine,
+
+---
+
+<sup>1)</sup> Public bureaux may be offices of telecommunication or of postal administrations.
+
+the document will be sent only if the sender accepts the possible risk of non-delivery or of unsatisfactory quality on reception. In effect, the same provisions apply as for **RISQUES EXPEDITEUR** in the bureaufax service (see Recommendation F.170). If b) above applies, or if, after several attempts within a maximum duration of 3 hours from the time of acceptance of the facsimile document, the destination subscriber facsimile terminal cannot be reached, the sender should be given the option of transmission by means of the normal bureaufax service (where available) in accordance with Recommendation F.170, at the tariffs applicable to that service.
+
+*Note* – During an interim period for gaining the greatest possible operational experience, the Administrations should apply the same procedure if they know that the receiving facsimile machine operates automatically.
+
+### 3 “Private-to-public” transmission
+
+3.1 Except where contrary provisions are published by the terminal Administrations concerned, “private-to-public” facsimile transmission is permitted.
+
+3.2 Facsimile documents received by a public bureau from a subscriber station in another country are handled and delivered to the addressee in accordance with appropriate methods laid down by the destination Administration. The provisions of Recommendations F.170, §§ 6.1, 6.3, 6.4 and 6.5 may be applied.
+
+3.3 The sending subscriber shall provide the receiving public bureau with sufficient information for processing his facsimile documents; to that end the subscriber should use a transmittal sheet in accordance with Figure 1/F.190. Administrations should encourage the use of such forms by informing subscribers of their availability. The sending subscriber may insert his logo, company name, etc., in free spaces on the transmittal sheet.
+
+3.4 If the sending subscriber does not use a transmittal sheet as in § 3.3, he shall provide the receiving public bureau with at least the following information:
+
+- a) the call number of his facsimile terminal;
+- b) the number of pages of the document, in accordance with Recommendation F.170, § 3.2.1, item 4);
+- c) the addressee's address, in accordance with Recommendation F.170, § 3.2.1, item 8), as well as the addressee's telephone, telex or teletex numbers if necessary.
+
+It is advisable for the sending subscriber also to give his address, in accordance with Recommendation F.170, § 3.2.1, item 9).
+
+3.5 On receipt of the facsimile document, the receiving bureau should contact the addressee in order to reach agreement on the mode of delivery and the charging.
+
+3.6 The receiving bureau may contact the sending subscriber if the copy received is of unsatisfactory quality.
+
+3.7 In the event of non-delivery owing to incomplete address information or for other reasons (e.g., when the receiving bureau cannot establish contact with the addressee even though the address is complete, or when the document is not collected by the addressee), the receiving bureau may contact the sending subscriber. The facsimile document received and/or other relevant information, should be kept on file in accordance with the national regulations in force.
+
+![Diagram of a transmittal sheet for a private-to-public telefacsimile transmission. The sheet is divided into several boxes for sender and addressee information. Dimensions are given in mm: total height 148, total width 210 (80 + 10 + 90 + 15). Box heights from top to bottom are 45, 15, 42, and 15 mm. The top section contains 'PRIVATE ® PUBLIC' and transmission details. Boxes 1-5 are for sender's telefax, document number, page count, transmission date, and receipt date. Box 6 is for delivery mode instructions. Box 7 is for the addressee's address, and box 8 is for the sender's address.](547f726730e589392f239257a833ede3_img.jpg)
+
+PRIVATE ® PUBLIC
+
+Transmission from a subscriber station to a public bureau
+
+A charge may be collected from the addressee
+
+|                                                                    |                               |
+|--------------------------------------------------------------------|-------------------------------|
+| 1. Sender's telefax No.                                            | 2. Document number            |
+| 3. No. of pages                                                    | 4. Date of transmission       |
+|                                                                    | 5. Date (and time) of receipt |
+| <input type="checkbox"/> 6. Delivery mode and service instructions |                               |
+| 7. Addressee's address (including postal code)                     |                               |
+| 8. Sender's address (including postal code)                        |                               |
+
+Dimensions: 148 (height), 210 a) (width: 80 + 10 + 90 + 15). Box heights: 45, 15, 42, 15.
+
+T0102690-92
+
+Diagram of a transmittal sheet for a private-to-public telefacsimile transmission. The sheet is divided into several boxes for sender and addressee information. Dimensions are given in mm: total height 148, total width 210 (80 + 10 + 90 + 15). Box heights from top to bottom are 45, 15, 42, and 15 mm. The top section contains 'PRIVATE ® PUBLIC' and transmission details. Boxes 1-5 are for sender's telefax, document number, page count, transmission date, and receipt date. Box 6 is for delivery mode instructions. Box 7 is for the addressee's address, and box 8 is for the sender's address.
+
+a) North American standard: 216 mm.
+
+Note 1 – Boxes 2, 5 and 6 are to be filled in by the receiving public bureau.
+
+Note 2 – The information in box 8 (sender) is optional. When given, it must appear in the left-hand part of the transmittal sheet.
+
+Note 3 – The addressee's address should include the telephone, telex or teletex number if necessary.
+
+Note 4 – The number of pages given in box 3 must be in accordance with Recommendation F.170, § 3.2.1, item 4).
+
+Note 5 – Concerning box 6, the following delivery modes may be requested by the addressee, in so far as they are offered by the destination Administration (for definitions, see Annex A to Recommendation F.170):
+
+|          |                                                                       |                                                                |
+|----------|-----------------------------------------------------------------------|----------------------------------------------------------------|
+| <b>A</b> | Ordinary mail                                                         | Courrier ordinaire                                             |
+| <b>B</b> | Special delivery                                                      | Porteur spécial                                                |
+| <b>C</b> | EMS (express mail service)                                            | EMS (service de courrier exprès)                               |
+| <b>D</b> | Counter collection                                                    | Retrait au guichet                                             |
+| <b>E</b> | Counter collection with telephone advice to the indicated call number | Retrait au guichet avec avis téléphonique au numéro indiqué    |
+| <b>F</b> | Telefax (with call number and CCITT group when known)                 | Téléfax (avec numéro d'appel et, s'il est connu, groupe CCITT) |
+| <b>G</b> | Counter collection with telex advice to the indicated call number     | Retrait au guichet avec avis télex au numéro indiqué           |
+| <b>H</b> | Counter collection with teletex advice to the indicated call number   | Retrait au guichet avec avis télétex au numéro indiqué         |
+
+Other modes of delivery may be offered by the destination Administration.
+
+FIGURE 1/F.190  
+**Measurements, locations and designations of the various parts of the transmittal sheet in accordance with § 3.3**
\ No newline at end of file
diff --git a/marked/F/T-REC-F.401-199208-I_PDF-E/raw.md b/marked/F/T-REC-F.401-199208-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..56b4527205e637c02bbf42fea0175a8e57a33725
--- /dev/null
+++ b/marked/F/T-REC-F.401-199208-I_PDF-E/raw.md
@@ -0,0 +1,900 @@
+
+
+![ITU logo: A globe with the letters ITU and a lightning bolt.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+ITU logo: A globe with the letters ITU and a lightning bolt.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**CCITT**
+
+**F.401**
+
+THE INTERNATIONAL  
+TELEGRAPH AND TELEPHONE  
+CONSULTATIVE COMMITTEE
+
+(08/92)
+
+**MESSAGE HANDLING SERVICES**
+
+**OPERATIONS AND DEFINITION OF SERVICE**
+
+---
+
+**MESSAGE HANDLING SERVICES:  
+NAMING AND ADDRESSING FOR PUBLIC  
+MESSAGE HANDLING SERVICES**
+
+![CCITT logo: A globe with the letters CCITT.](84a1d09fb489061482111515543b60dc_img.jpg)
+
+CCITT logo: A globe with the letters CCITT.
+
+**Recommendation F.401**
+
+---
+
+# FOREWORD
+
+The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT 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 Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988).
+
+Recommendation F.401 was revised by Study Group I and was approved under the Resolution No. 2 procedure on the 4th of August 1992.
+
+# --- CCITT NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized private operating agency.
+
+# **MESSAGE HANDLING SERVICES: NAMING AND ADDRESSING FOR PUBLIC MESSAGE HANDLING SERVICES**
+
+*(revised, 1992)*
+
+# **CONTENTS**
+
+# *Introduction*
+
+- 1 *Scope*
+- 2 *References*
+- 3 *Definitions*
+- 4 *Abbreviations*
+- 5 *Conventions*
+- 6 *Naming and addressing in message handling*
+  - 6.1 O/R addresses
+  - 6.2 Distribution list names
+  - 6.3 Directory names
+- 7 *Length of attributes*
+- 8 *Principles for the allocation of O/R names and O/R addresses*
+- 9 *Use of O/R names*
+  - 9.1 General
+  - 9.2 Character repertoires
+  - 9.3 Specific rules
+  - 9.4 Support of forms of O/R addresses
+
+*Annex A – List of alpha-2 country codes*
+
+*Annex B – Representation of O/R addresses for human usage*
+
+*Annex C – Format for notification of ADMD names*
+
+# **Introduction**
+
+The establishment in various countries of message handling services in association with public networks creates the need to produce Recommendations covering the aspects of public message handling services. Naming and addressing is a key area for the application and the provision of public message handling services on a global scale.
+
+# 1 Scope
+
+This Recommendation specifies naming and addressing aspects for public message handling services which are described in other Recommendations of the F-Series. It also establishes some principles for the allocation of originator/recipient O/R addresses.
+
+# 2 References
+
+- CCITT Rec. E.164, *Numbering plan for the ISDN era*, 1991.
+- CCITT Rec. F.400, *Message handling services: Message handling system and service overview*, 1992.
+- CCITT Rec. F.410, *Message handling services: The public message transfer service*, 1992.
+- CCITT Rec. F.415, *Message handling services: Intercommunication with public physical delivery services*, 1988.
+- CCITT Rec. F.420, *Message handling services: The public interpersonal messaging service*, 1992.
+- CCITT Rec. F.421, *Message handling services: Intercommunication between the IPM service and the telex service*, 1988.
+- CCITT Rec. F.422, *Message handling services: Intercommunication between the IPM service and the teletex service*, 1988.
+- CCITT Rec. F.423, *Message handling services: Intercommunication between the IPM service and telefax services*, 1992.
+- CCITT Rec. F.435, *Message handling services: electronic data interchange messaging service*, 1991.
+- CCITT Rec. F.440, *Message handling services: The voice messaging service*, 1992.
+- CCITT Rec. F.500, *International public directory services*, 1992.
+- CCITT Rec. T.61 (1992), *Character repertoire and coded character sets for the international teletex service*, 1988.
+- CCITT Rec. X.121, *International numbering plan for public data networks*, 1992.
+- Other CCITT Recs. of the X.400-Series (1993), *Message handling systems*, 1993.
+- CCITT Rec. X.402, *Message handling systems: Overall architecture*, 1993.
+- CCITT Recs. of the X.500-Series, *Directory systems*, 1992.
+- CCITT Rec. X.660<sup>1)</sup>, *Procedures for the operation of OSI registration authorities: General procedures*.
+- ISO 3166 (1988) (plus amendments), *Codes for the representation of names of countries*, 1988.
+
+# 3 Definitions
+
+For the purposes of this Recommendation the definitions given in Recommendation F.400 apply. See also Annex A of Recommendation F.400.
+
+# 4 Abbreviations
+
+|      |                                  |
+|------|----------------------------------|
+| ADMD | Administration management domain |
+| DCC  | Data country code                |
+| DDA  | Domain defined attribute         |
+| DL   | Distribution list                |
+
+---
+
+<sup>1)</sup> Presently at the stage of draft.
+
+|      |                                        |
+|------|----------------------------------------|
+| IA5  | International Alphabet No. 5           |
+| IPM  | Interpersonal messaging                |
+| ITA2 | International Telegraph Alphabet No. 2 |
+| MD   | Management domain                      |
+| MH   | Message handling                       |
+| MHE  | Message handling environment           |
+| MHS  | Message handling system                |
+| MT   | Message transfer                       |
+| O/R  | Originator/recipient                   |
+| OU   | Organizational unit                    |
+| PO   | Post office                            |
+| PD   | Physical delivery                      |
+| PRMD | Private management domain              |
+| PSAP | Presentation service access point      |
+| RPOA | Recognized private operating agency    |
+| UPU  | Universal Postal Union                 |
+
+Abbreviations and labels used in Annex B are explained in the annex itself.
+
+# 5 Conventions
+
+In this Recommendation the expression “Administration” is used for shortness to indicate a telecommunication Administration, a recognized private operating agency (RPOA), and, in the case of intercommunication with public physical delivery service, a postal Administration.
+
+# 6 Naming and addressing in message handling
+
+Naming and addressing in message handling have to ensure that users can define the source and the destination of messages in an unambiguous way. The organizational mapping of message handling systems, and the structure of management domains (see Recommendation F.400), together with a set of naming conventions, are the means to establish a uniform and compatible environment for the exchange of messages between any users of the message handling environment. Only those attributes need appear in an O/R address that are required to reach a recipient.
+
+Names and addresses are allocated by the responsible naming authority. These authorities are asked to notify the Director of the CCITT of the names of their ADMDs and of some additional information (name and address of the public service provider, name of the services, etc.) for subsequent publication in the ITU *Operational Bulletin* (see Annex C for the format of the notification and also Recommendation X.660).
+
+In message handling systems (MHS), the principal entity that requires naming is the user (the originator and the recipient of messages). In addition, distribution lists (DLs) have names for their own identification and use in the context of MHS. Users of MHS and DLs are identified by O/R names. (The prefix “O/R” recognizes the fact that the user can be acting as either the originator or the recipient of a message.) An O/R name comprises a directory name, an O/R address or both. Every user or DL has one or more O/R names.
+
+## 6.1 O/R addresses
+
+An O/R address contains information that enables the MHS to identify a user in order to deliver a message or return a notification. DLs are also identified by an O/R address.
+
+An O/R address is comprised of a set of information called attributes. Recommendation X.402 specifies a set of standard attributes from which O/R addresses can be constructed. Standard attributes, the structure of attribute lists
+
+and their syntax and semantics are defined in Recommendation X.402. In addition to standard attributes, and so as to cater for existing messaging systems, there are domain defined attributes whose syntax and semantics are specified by management domains. They are applicable for an interim period.
+
+Various forms of O/R addresses are defined, each serving its own purpose. These forms and their purpose are as follows:
+
+- *Mnemonic O/R address*: Provides a user friendly means of identifying users in the absence of a directory. It may also be used for identifying a distribution list.
+- *Terminal O/R address*: Provides a means of identifying users with terminals belonging to various networks.
+- *Numeric O/R address*: Provides a means of identifying users with numeric keypads.
+- *Postal O/R address*: Provides a means of identifying originators and recipients of messages and notifications, for physical delivery.
+
+It is up to the management domain concerned to decide which name forms it wants to use. Corresponding parties should be made aware of the applicable name space (i.e. the repertoire of names).
+
+### 6.1.1 *Mnemonic O/R address*
+
+This form of O/R address provides addresses that mnemonically identifies a user or a DL relative to the administration management domain (ADMD) through which the user is accessed. At least one of the conditional attributes following the domain name(s) has to be present. A PRMD name is present only if the user concerned belongs to that domain. If an organizational unit is present, the organization name has to be present as well.
+
+The mnemonic O/R address consists of:
+
+- Country name
+- Administration domain name
+- [Private domain name]
+- [Organization name]
+- [Organizational unit name]
+- [Personal name]
+- [Common name]
+- [[Domain defined attributes ]]
+
+*Note* – Attributes in square brackets are conditional. Double square brackets indicate an attribute not belonging to the standard attribute list and may not be required for global addressing.
+
+### 6.1.2 *Terminal O/R address*
+
+This form of O/R address provides a means for addressing a terminal with its network address, conditionally with the country name, the domain name(s), a terminal identifier, the terminal type and domain defined attributes. If an organizational unit is present, the organization name has to be present as well.
+
+The terminal O/R address consists of:
+
+- [Country name]
+- [Administration domain name]  
+[Private domain name]
+- Network address
+- [Terminal identifier]
+- [Terminal type]
+- [[Domain defined attributes]]
+- {Common name}
+
+- {Organization name}
+- {Organizational unit names}
+- {personal name}
+- {unformatted postal address}
+
+*Note 1* – Attributes in square brackets are conditional. Double square brackets indicate an attribute not belonging to the standard attribute list and may not be required for global addressing.
+
+*Note 2* – Domain defined attributes should be present only if the country name and the Administration management domain name are present.
+
+*Note 3* – Network addresses allocated by a domain need to be unambiguous and thus can only be assigned once. Country name and administration management name attributes have to be present when more than one domain is providing service for the address concerned.
+
+*Note 4* – Attributes in braces are intended to be used for rendering of the address information (making it visible) on the receiving terminal but not for addressing or routing purposes.
+
+The network address is composed of digits from the X.121 numbering plan (including escape codes) or the E.164 numbering plan.
+
+The conditional terminal identifier might be, for example, a telex answerback string or a teletex terminal identifier.
+
+The conditional terminal type might be, for example, a telex, a teletex, a G3 facsimile, a G4 facsimile, an IA5, or a videotex terminal.
+
+### 6.1.3 *Numeric O/R address*
+
+This form of O/R address provides addresses that can be entered from devices equipped only with numeric keypads. It identifies numerically a user relative to the ADM D through which the user is accessed.
+
+The numeric O/R address consists of:
+
+- Country name
+- Administration domain name
+- [Private domain name]
+- Numeric user identifier
+- [[Domain defined attributes]]
+
+*Note 1* – Attributes in square brackets are conditional. Double square brackets indicate an attribute not belonging to the standard attribute list and may not be required for global addressing.
+
+*Note 2* – Numeric values are assumed for all attributes. Countries may be named with DCCs (see Recommendation X.121). An ADM D name would require the allocation of a numeric alias name.
+
+*Note 3* – This form could also be used for a videotex user number.
+
+*Note 4* – The numeric user identifier may use a check digit for validation purposes.
+
+### 6.1.4 *Postal O/R address*
+
+This form of O/R address provides for the identification of a user by means of his postal address, together with the country name(s), and the domain name(s), and the PD service name through which he is accessed.
+
+See also Recommendation F.415.
+
+*Version 1 – Unformatted postal O/R address:*
+
+- Physical delivery country name
+- Country name
+- Administration domain name
+- [Private domain name]
+- [Physical delivery service name]
+- Unformatted postal address
+
+Sufficient address components have to be supplied in the unformatted postal address in order to enable the PD service to route, distribute and deliver the physical message properly.
+
+*Version 2 – Formatted postal O/R address:*
+
+- Physical delivery country name
+- Country name
+- Administration domain name
+- [Private domain name]
+- [Physical delivery service name]
+- Postal code
+- Set of formatted postal address attributes
+
+There is no defined order in the set of formatted postal O/R address attributes. These attributes are:
+
+- *Postal O/R address components:*
+  - a) [Physical delivery personal name]
+  - b) [Physical delivery organization name]
+- *Physical delivery address components:*
+  - a) [Street address]
+  - b) [P.O. box address]
+  - c) [Poste restante address]
+  - d) [Unique postal name]
+- *Physical delivery office address components:*
+  - a) Physical delivery office name
+  - b) [Physical delivery office number]
+  - c) [Local postal attributes]
+- *Other postal address components:*
+  - a) [Extension of postal O/R address components]
+  - b) [Extension of physical delivery address components]
+
+*Note – Attributes in square brackets are conditional.*
+
+Sufficient attributes have to be provided in order to enable the PD service to route, distribute and deliver the physical message properly.
+
+For the description of formatted postal O/R address attributes, see Annex A of Recommendation F.400 and for the length see § 7 of this Recommendation.
+
+## 6.2 *Distribution list names*
+
+In the context of message handling, names of distribution lists (making use of the common name attribute) are used to identify the point of expansion of a message using a distribution list, such list containing a set of O/R addresses or further distribution list names. See Recommendation F.400.
+
+Care should be taken in the choice of distribution list names to ensure that users are aware that they are addressing a distribution list.
+
+*Note* – For naming of distribution lists, the attribute common name may be used. Names of distribution lists should clearly indicate their purpose.
+
+## 6.3 *Directory names*
+
+In the context of message handling, a directory name can be used to retrieve the required O/R address from a directory. See Recommendations F.400 and F.500. The directory may be provided by local functions.
+
+# 7 **Length of attributes**
+
+The coding is specified in the Recommendations of the X.400 series.
+
+The O/R address shall allow the following information:
+
+## - *Country name*
+
+The Alpha-2 country code listed in Annex A or the DCC from Recommendation X.121 can be used as the country name. Maximum 3 characters.
+
+## - *Physical delivery country name*
+
+The same conditions as for *country name* apply.
+
+## - *Physical delivery service name*
+
+Maximum 16 characters.
+
+## - *Administration domain name*
+
+Maximum 16 characters. The Numeric O/R address form assumes allocation of numeric country and administration management domain names.
+
+*Note 1* – If the national option of to use the “space” character for all ADMDs of a country is applied, it should not have any implication on unique global addressing and on routing, accounting or other general international requirements.
+
+*Note 2* – National use of the characters “space” and “0” as ADMD name attributes may have an impact on international messaging. A domain may define the list of ADMD names or PRMD names it wants to accept, depending:
+
+- a) on the naming policy applied; and
+- b) on commercial considerations.
+
+Bilateral agreements between domains may be required for the arrangement chosen.
+
+## - *Private domain name*
+
+Maximum 16 characters.
+
+*Note 3* – Global uniqueness of the private domain name attribute can be assured by allocating values relative to the ADMD name. PRMD names may be the same even when they are used in conjunction with more than one ADMD, because the country name attribute makes the O/R addresses using these attributes unique. National practices may provide for allocation of PRMD names relative to the country name attribute (when registration is performed by the ADMD concerned or by a centralized national registration authority).
+
+## - *Organization name*
+
+Maximum 64 characters.
+
+- *Organizational unit(s)*  
+Maximum 32 characters each.
+- *Personal name*  
+Maximum length is the sum of the maxima of the parts (64 characters).
+  - a) *Surname* – maximum 40 characters.
+  - b) *Given name* – maximum 16 characters.
+  - c) *Initials* (optional) – maximum 5 characters (for further study).
+  - d) *Generation qualifier* (optional) – maximum 3 characters.
+- *Distribution list name*  
+Maximum length of the *common name* applies.
+- *Common name*  
+Maximum 64 characters.
+- *Domain defined attributes*  
+Maximum four separate attributes. Maximum length for “type” 8 and for “value” 128 characters.
+- *Network address*  
+Maximum 14 + 1 digits, including the prefix (see Recommendation X.121).  
+*Note* – The classification and maximum value may change to accommodate other addressing schemes.
+- *Terminal identifier*  
+Maximum 24 characters.
+- *Numeric user identifier*  
+Maximum 32 digits.
+- *Unformatted postal address (version 1)*  
+Up to 6 lines with a maximum of 30 characters in each line (see Note). In the case of transit mail, the last line is reserved for the name of the country of the final physical destination.  
+*Note* – The number of characters specified refers to characters to be printed (including spaces).
+- *Formatted postal address (version 2)*  
+The formatted postal address attributes and their constraints are (for the description of these attributes see Annex A of Recommendation F.400).
+- *Postal O/R address components* (see Note 2)  
+Physical delivery personal name (see Note 3): 30 characters (see Note 1).  
+Physical delivery organization name (see Note 3): 30 characters (see Note 1).
+- *Physical delivery address components* (see Note 2)  
+Street address: 30 characters (see Note 1).  
+P.O. box address: 30 characters (see Note 1).  
+Poste restante address: 30 characters (see Note 1).  
+Unique postal name: 30 characters (see Note 1).
+- *Physical delivery office address components*  
+Physical delivery office name: x number of characters (see Notes 1 and 4).  
+Physical delivery office number: y number of characters (see Notes 1 and 4).  
+Local postal attributes: z number of characters (see Notes 1 and 4).
+
+- *Other postal address components*
+
+Extension of O/R address components (see Note 5): 30 characters (see Note 1).
+
+Extension of physical delivery address components (see Note 6): 30 characters (see Note 1).
+
+The overall constraints are 6 lines of attributes with a maximum of 30 characters in each line (see Note 1). In the case of transit mail, the last line is reserved for the name of the receiving country of the final physical destination.
+
+*Note 1* – The number of characters specified refers to characters to be printed (including spaces).
+
+*Note 2* – At least one of the following attributes should be used.
+
+*Note 3* – Physical delivery personal name and physical delivery organization name are free form names and have different length from personal name and organization name.
+
+*Note 4* – These attributes have to be printed in one line, in some countries together with the postal code. Thus  $x + y + z$  is a maximum of 30 characters including the delimiting spaces and the postal code if printed on the same line.
+
+*Note 5* – May be used to extend the postal O/R address components.
+
+*Note 6* – May be used to extend the physical delivery address components.
+
+# **8 Principles for the allocation of O/R names and O/R addresses**
+
+8.1 The naming authority of the country responsible for administration management domain names will ensure the designation of an unambiguous name to each ADMD of message handling services in that country.
+
+8.2 Each ADMD is responsible for the administration of names of private management domains associated with it.
+
+*Note* – For PRMDs intercommunicating with more than one ADMD, registration with each ADMD will assure uniqueness of O/R addresses used. National practices may provide for registration on a country level.
+
+8.3 Each management domain (MD) is responsible for allocating unambiguous addresses to users below the level of the MD name(s) for the purpose of using message handling services.
+
+8.4 A distribution list shall only be given a name which is clearly indicating to the user its intent. Names or O/R addresses shall only be included in a publicly accessible distribution list when the permission of the owner of the information is given and national rules for security are respected.
+
+# **9 Use of O/R names**
+
+## **9.1 *General***
+
+With the help of O/R names a user can send messages via the MHS. Users may get support from their user agent in the use of O/R names. The latter is a local matter.
+
+## **9.2 *Character repertoires***
+
+The character repertoire allowed in O/R names are either printable, numeric or teletex repertoires (for more detail see Recommendation X.402).
+
+The printable character repertoire is shown in Table 1/F.401.
+
+The numeric character repertoire comprises the digits 0 to 9 and space, and is a subset of the printable character repertoire (see Table 1/F.401).
+
+For the teletex repertoire see Recommendation T.61. In general the teletex repertoire may also be used internationally.
+
+The use of an extended character repertoire within a management domain is a local matter.
+
+TABLE 1/F.401
+
+### **Printable character repertoire for O/R names**
+
+| Designation       | Graphic representation |
+|-------------------|------------------------|
+| Uppercase letters | A, B ..... Z           |
+| Lowercase letters | a, b ..... z           |
+| Digits            | 0, 1 ..... 9           |
+| Space             | (space)                |
+| Apostrophe        | '                      |
+| Left parenthesis  | (                      |
+| Right parenthesis | )                      |
+| Plus sign         | +                      |
+| Comma             | ,                      |
+| Hyphen            | -                      |
+| Full stop         | .                      |
+| Solidus           | /                      |
+| Colon             | :                      |
+| Equals sign       | =                      |
+| Question mark     | ?                      |
+
+*Note* – According to Recommendation X.208, this repertoire is called a printable string type. All these characters are available in ITA2 (as far as letters are concerned, only in uppercase or lowercase).
+
+## 9.3 *Specific rules*
+
+Rules for postal O/R addresses, see §§ 2 and 3 and Recommendation F.415.
+
+Management domains will not allow O/R names, that differ only by the number of “space” characters, either at the beginning or the end of any of their attributes, to identify different users.
+
+Additionally MDs will consider the occurrence of contiguous space characters in an O/R address attribute value to be the same as a single space character.
+
+MDs will not allow O/R names, that differ only by small letter/capital letter distinctions, to identify different users.
+
+## 9.4 *Support of forms of O/R addresses*
+
+Each MHS shall support all the name address forms in the incoming direction for transmitting purposes. It is the decision of the management of a domain which name forms are allocated to the users of that domain. In the outgoing direction the originating domain needs to use the name forms the destination domain applies. The way in which names are inputted by, or presented to, the subscriber is a local matter.
+
+# ANNEX A (to Recommendation F.401)
+
+(This annex does not form an integral part of this Recommendation)
+
+## **List of Alpha-2 country codes**
+
+*Note* – Source: ISO 3166. Current edition (1988) at time of printing. The latest published edition from ISO should be applied.
+
+|                                |    |                              |    |
+|--------------------------------|----|------------------------------|----|
+| Afghanistan                    | AF | Comoros                      | KM |
+| Albania                        | AL | Congo                        | CG |
+| Algeria                        | DZ | Cook Islands                 | CK |
+| American Samoa                 | AS | Costa Rica                   | CR |
+| Andorra                        | AD | Côte d'Ivoire                | CI |
+| Angola                         | AO | Cuba                         | CU |
+| Anguilla                       | AI | Cyprus                       | CY |
+| Antarctica                     | AQ | Czechoslovakia               | CS |
+| Antigua and Barbuda            | AG |                              |    |
+| Argentina                      | AR | Denmark                      | DK |
+| Aruba                          | AW | Djibouti                     | DJ |
+| Australia                      | AU | Dominica                     | DM |
+| Austria                        | AT | Dominican Republic           | DO |
+|                                |    |                              |    |
+| Bahamas                        | BS | East Timor                   | TP |
+| Bahrain                        | BH | Ecuador                      | EC |
+| Bangladesh                     | BD | Egypt                        | EG |
+| Barbados                       | BB | El Salvador                  | SV |
+| Belgium                        | BE | Equatorial Guinea            | GQ |
+| Belize                         | BZ | Ethiopia                     | ET |
+| Benin                          | BJ |                              |    |
+| Bermuda                        | BM | Falkland Islands (Malvinas)  | FK |
+| Bhutan                         | BT | Faeroe Islands               | FO |
+| Bolivia                        | BO | Fiji                         | FJ |
+| Botswana                       | BW | Finland                      | FI |
+| Bouvet Island                  | BV | France                       | FR |
+| Brazil                         | BR | French Guiana                | GF |
+| British Indian Ocean Territory | IO | French Polynesia             | PF |
+| British Virgin Islands         | VG | French Southern Territories  | TF |
+| Brunei Darussalam              | BN |                              |    |
+| Bulgaria                       | BG | Gabon                        | GA |
+| Burkina Faso                   | BF | Gambia                       | GM |
+| Burma                          | BU | Germany, Federal Republic of | DE |
+| Burundi                        | BI | Ghana                        | GH |
+| Byelorussian SR                | BY | Gibraltar                    | GI |
+|                                |    | Greece                       | GR |
+| Cameroon                       | CM | Greenland                    | GL |
+| Canada                         | CA | Grenada                      | GD |
+| Cape Verde                     | CV | Guadeloupe                   | GP |
+| Cayman Islands                 | KY | Guam                         | GU |
+| Central African Republic       | CF | Guatemala                    | GT |
+| Chad                           | TD | Guinea                       | GN |
+| Chile                          | CL | Guinea-Bissau                | GW |
+| China                          | CN | Guyana                       | GY |
+| Christmas Islands              | CX |                              |    |
+| Cocos (Keeling) Islands        | CC | Haiti                        | HT |
+| Colombia                       | CO | Heard and Mc Donald Islands  | HM |
+
+|                                               |    |                                  |    |
+|-----------------------------------------------|----|----------------------------------|----|
+| Honduras                                      | HN | Nigeria                          | NG |
+| Hong Kong                                     | HK | Niue                             | NU |
+| Hungary                                       | HU | Norfolk Island                   | NF |
+|                                               |    | Northern Mariana Islands         | MP |
+| Iceland                                       | IS | Norway                           | NO |
+| India                                         | IN |                                  |    |
+| Indonesia                                     | ID | Oman                             | OM |
+| Iran, Islamic Republic of                     | IR |                                  |    |
+| Iraq                                          | IQ | Pakistan                         | PK |
+| Ireland                                       | IE | Palau                            | PW |
+| Israel                                        | IL | Panama                           | PA |
+| Italy                                         | IT | Papua New Guinea                 | PG |
+|                                               |    | Paraguay                         | PY |
+| Jamaica                                       | JM | Peru                             | PE |
+| Japan                                         | JP | Philippines                      | PH |
+| Jordan                                        | JO | Pitcairn                         | PN |
+|                                               |    | Poland                           | PL |
+| Kampuchea, Democratic                         | KH | Portugal                         | PT |
+| Kenya                                         | KE | Puerto Rico                      | PR |
+| Kiribati                                      | KI |                                  |    |
+| Korea, Democratic People's Republic of        | KP | Qatar                            | QA |
+| Korea, Republic of                            | KR |                                  |    |
+| Kuwait                                        | KW | Réunion                          | RE |
+|                                               |    | Romania                          | RO |
+| Lao People's Democratic Republic              | LA | Rwanda                           | RW |
+| Lebanon                                       | LB |                                  |    |
+| Lesotho                                       | LS | St. Helena                       | SH |
+| Liberia                                       | LR | Saint. Kitts-Nevis               | KN |
+| Libyan Arab Jamahiriya                        | LY | Saint Lucia                      | LC |
+| Liechtenstein                                 | LI | St. Pierre and Miquelon          | PM |
+| Luxembourg                                    | LU | Saint Vincent and the Grenadines | VC |
+|                                               |    | Samoa                            | WS |
+| Macau                                         | MO | San Marino                       | SM |
+| Madagascar                                    | MG | Sao Tome and Principe            | ST |
+| Malawi                                        | MW | Saudi Arabia                     | SA |
+| Malaysia                                      | MY | Senegal                          | SN |
+| Maldives                                      | MV | Seychelles                       | SC |
+| Mali                                          | ML | Sierra Leone                     | SL |
+| Malta                                         | MT | Singapore                        | SG |
+| Marshall Islands                              | MH | Solomon Islands                  | SB |
+| Martinique                                    | MQ | Somalia                          | SO |
+| Mauritania                                    | MR | South Africa                     | ZA |
+| Mauritius                                     | MU | Spain                            | ES |
+| Mexico                                        | MX | Sri Lanka                        | LK |
+| Micronesia                                    | FM | Sudan                            | SD |
+| Monaco                                        | MC | Suriname                         | SR |
+| Mongolia                                      | MN | Svalbard and Jan Mayen Islands   | SJ |
+| Montserrat                                    | MS | Swaziland                        | SZ |
+| Morocco                                       | MA | Sweden                           | SE |
+| Mozambique                                    | MZ | Switzerland                      | CH |
+|                                               |    | Syrian Arab Republic             | SY |
+| Namibia                                       | NA |                                  |    |
+| Nauru                                         | NR | Taiwan, Province of China        | TW |
+| Nepal                                         | NP | Tanzania, United Republic of     | TZ |
+| Netherlands                                   | NL | Thailand                         | TH |
+| Netherlands Antilles                          | AN | Togo                             | TG |
+| Neutral Zone (between Saudia Arabia and Iraq) | NT | Tokelau                          | TK |
+| New Caledonia                                 | NC | Tonga                            | TO |
+| New Zealand                                   | NZ | Trinidad and Tobago              | TT |
+| Nicaragua                                     | NI | Tunisia                          | TN |
+| Niger                                         | NE | Turkey                           | TR |
+
+|                                      |    |                           |    |
+|--------------------------------------|----|---------------------------|----|
+| Turks and Caicos Islands             | TC | Venezuela                 | VE |
+| Tuvalu                               | TV | Viet Nam                  | VN |
+|                                      |    | Virgin Islands, U.S.      | VI |
+| Uganda                               | UG |                           |    |
+| Ukrainian SSR                        | UA | Wallis and Futuna Islands | WF |
+| United Arab Emirates                 | AE | Western Sahara            | EH |
+| United Kingdom                       | GB |                           |    |
+| United States                        | US | Yemen                     | YE |
+| United States Minor Outlying Islands | UM | Yemen, Democratic         | YD |
+| Uruguay                              | UY | Yugoslavia                | YU |
+| USSR                                 | SU |                           |    |
+|                                      |    | Zaire                     | ZR |
+| Vanuatu                              | VU | Zambia                    | ZM |
+| Vatican City State (Holy See)        | VA | Zimbabwe                  | ZW |
+
+# ANNEX B (to Recommendation F.401)
+
+## **Representation of O/R addresses for human usage<sup>1)</sup>**
+
+(This annex does not form an integral part of this Recommendation)
+
+## **B.1      Purpose**
+
+An O/R address consists of a set of attribute values taken from a total of 31 possible attributes. In order to represent visually an address to a human user, and to enable the user to enter the address into a user interface, each attribute value needs to be associated with the correct attribute type. Many of the full attribute types given in Recommendation X.402 are too long for convenient usage on paper or a screen. There is a need for a format which allows attributes to be represented concisely, e.g. on a business card.
+
+This annex specifies how addresses can be expressed concisely using labels to represent the attribute types. There are three categories of attributes: those standard mnemonic attributes which are most likely to be found in O/R addresses represented for human exchange (e.g. on business cards), those used in physical delivery addresses, and other specialized attributes (including domain defined attributes). In order to provide a format which is as concise as possible, many of the labels are single characters. This also makes them less language dependent.
+
+Subsection B.3 specifies the format for the representation of addresses, and § B.4 specifies the characteristics necessary for user interfaces which are intended to be used in conjunction with this format.
+
+## **B.2      Scope**
+
+A labelled format for the communication of O/R addresses to human users is specified. The format consists of a set of pairs of labels and attribute-values. The characteristics of a user interface which are necessary to accept addresses given in this format are also specified.
+
+<sup>1)</sup> This Annex is aligned with ISO/IEC 10021-2, Annex F(DAM) and is referenced in Recommendation X.402
+
+In addition, a self-explanatory format suitable for use where there is more space, e.g. in printed material and in the user interface, is specified.
+
+## B.3 *Format*
+
+### B.3.1 *General*
+
+Some systems are capable of accepting messages when certain optional attributes of the recipient's O/R address [e.g. organizational units (OUs)] are omitted by the originator. In these circumstances it is normally preferable to use the shortest acceptable form of the address when representing the address for human usage.
+
+*Note 1* – OUs should only be used to disambiguate users with the same surname if this cannot be achieved by the use of other name attributes (given name, initials, or generation qualifier). The use of additional OUs for this purpose has the disadvantage that the user's O/R name will change if the naming of the OUs changes, or if the user moves to a different OU.
+
+Where national usage permits a single space value for the ADMD in an address, this may be represented in the address either by omitting the ADMD attribute, or showing the ADMD attribute with no value or the value of a space.
+
+*Note 2* – When sending messages internationally, there may be difficulties in reaching a recipient if a single space ADMD name is specified.
+
+If the attributes of an O/R address include characters from an extended character set, human users who do not normally use the same extended character set may have difficulty representing the O/R address or entering it into their messaging system.
+
+### B.3.2 *Labelled format*
+
+#### B.3.2.1 *Syntax*
+
+O/R addresses in labelled format consist of delimited pairs of labels and values in the syntax <label>“=”<value>. The labels for each attribute are specified in Tables B-1/F.401, B-2/F.401 and B-3/F.401. (The physical delivery attributes in Table B-2/F.401 are included for completeness.) The label and its value are either separated by the character “=”, or by the space between two columns in a table. The value is supplied by the human user and is case insensitive.
+
+If label-value pairs appear in sequence on a line, they are separated by delimiters. The delimiter character may be either “;” or “/”, but only one of these can be used in one O/R address. If the value of any attribute contains the delimiter character, this is represented by a pair of delimiter characters. If the value of the first attribute contains the alternate delimiter character, this is represented by a pair of alternate delimiter characters.
+
+*Note* – When the label-value pairs appear in sequence on a line, the use of upper case for labels and lower case for the values makes the format clearer for the user.
+
+If an identifier is required to preface a labelled address, it is recommended that “X.400” be used.
+
+If an address is entirely composed of attributes contained in Table B-1/F.401, it is recommended that the sequence of attributes in the address be that given in Table B-1/F.401. If this sequence is incompatible with normal cultural conventions, an alternative sequence may be adopted for representations of addresses which are primarily intended for use within that culture.
+
+TABLE B-1/F.401
+
+##### **Standard attributes of the mnemonic address form**
+
+| Attribute type                        | Abbreviation | Label<br>(where necessary) |
+|---------------------------------------|--------------|----------------------------|
+| Given name                            | Given name   | G                          |
+| Initials                              | Initials     | I                          |
+| Surname                               | Surname      | S                          |
+| Generation qualifier                  | Generation   | Q                          |
+| Common name                           | Common name  | CN                         |
+| Organization                          | Organization | O                          |
+| Organizational unit 1                 | Org.Unit.1   | OU1                        |
+| Organizational unit 2                 | Org.Unit.2   | OU2                        |
+| Organizational unit 3                 | Org.Unit.3   | OU3                        |
+| Organizational unit 4                 | Org.Unit.4   | OU4                        |
+| Private management domain name        | PRMD         | P                          |
+| Administration management domain name | ADMD         | A                          |
+| Country                               | Country      | C                          |
+
+TABLE B-2/F.401
+
+###### **Physical delivery attributes**
+
+| Attribute type                                    | Abbreviation     | Label<br>(where necessary) |
+|---------------------------------------------------|------------------|----------------------------|
+| Physical delivery personal name                   | PD-PN            | PD-PN                      |
+| Extension of postal O/R address components        | PD-ext.delivery  | PD-EA                      |
+| Extension of physical delivery address components | PD-ext.address   | PD-ED                      |
+| Physical delivery office number                   | PD-office number | PD-OFN                     |
+| Physical delivery office name                     | PD-office        | PD-OF                      |
+| Physical delivery organization name               | PD-O             | PD-O                       |
+| Street address                                    | PD-street        | PD-S                       |
+| Unformatted postal address                        | PD-address       | PD-A                       |
+| Unique postal name                                | PD-unique        | PD-U                       |
+| Local postal attributes                           | PD-local         | PD-L                       |
+| Postal restante address                           | PD-restante      | PD-R                       |
+| Post office box address                           | PD-box           | PD-B                       |
+| Postal code                                       | PD-code          | PD-PC                      |
+| Physical delivery service name                    | PD-service       | PD-SN                      |
+| Physical delivery country name                    | PD-C             | PD-C                       |
+
+TABLE B-3/F.401
+
+###### **Other attributes**
+
+| Attribute type           | Abbreviation  | Label<br>(where necessary) |
+|--------------------------|---------------|----------------------------|
+| X.121 network address    | X.121         | X.121                      |
+| E.164 network address    | E.164         | E.164                      |
+| PSAP network address     | PSAP          | PSAP                       |
+| User agent numeric ID    | N-ID          | N-ID                       |
+| Terminal identifier      | T-ID          | T-ID                       |
+| Terminal type            | T-TY          | T-TY                       |
+| Domain defined attribute | DDA:<type> a) | DDA:<type> a)              |
+
+a) The notation <type> identifies the type of domain defined attribute.
+
+*Example* – X.400: G=john; S=smith; O=a bank ltd; P=abl; A=snomail; C=aq
+
+This address may also be laid out as a table:
+
+G John  
+ S Smith  
+ O A Bank Ltd  
+ P ABL  
+ A Snomail  
+ C AQ
+
+#### B.3.2.2 Terminal type
+
+There are currently six terminal types, and if international consistency is required, the following specific abbreviations should be used to represent the values for these types: tlx, ttx, g3fax, g4fax, ia5 and vtx.
+
+#### B.3.2.3 Domain defined attribute
+
+The label for a domain defined attribute (DDA) consists of “DDA:” followed by the DDA type. If an address includes more than one DDA of the same type, it is assumed that the DDAs are intended to be processed in the sequence in which they are represented.
+
+*Example* – DDA:RFC-822=fred(a)widget.co.uk; O=gateway; P=abc; C=gb
+
+If the <type> of a DDA type includes the character “=”, it is represented by “==”.
+
+### B.3.3 Self-explanatory format
+
+The self-explanatory format may be used when space is available. It consists of a list of the attribute types, either in full or abbreviated. The attribute types or abbreviations may be in any language, but each attribute type or abbreviation in Table B-1/F.401 is followed by the specified label. If English language abbreviations are used, they should be those given in Tables B-1/F.401, B-2/F.401 and B-3/F.401.
+
+If an address is entirely composed of attributes contained in Table B-1/F.401, it is recommended that the sequence of attributes in the address is that given in Table B-1/F.401. If this sequence is incompatible with normal cultural conventions, an alternative sequence may be adopted for representations of addresses which are primarily intended for use within that culture.
+
+#### *Example 1 – Using attribute types in the Norwegian language*
+
+|                           |           |
+|---------------------------|-----------|
+| Fornavn (G)               | Per       |
+| Etternavn (S)             | Hansen    |
+| Organisasjon (O)          | Teledir   |
+| Organisasjonsenhet (OU1)  | Forskning |
+| Privat domene (P)         | Tele      |
+| Administrasjonsdomene (A) | Telemax   |
+| Land (C)                  | NO        |
+
+#### *Example 2 – Using attribute types and abbreviations in the English language*
+
+|                  |            |
+|------------------|------------|
+| Given name (G)   | John       |
+| Surname (S)      | Smith      |
+| Organization (O) | A Bank Ltd |
+| Org. Unit (OU1)  | IT Dept    |
+| Org. Unit (OU2)  | MSG Group  |
+| PRMD (P)         | ABL        |
+| ADMD (A)         | Snomail    |
+| Country (C)      | AQ         |
+
+## B.4 *User interface*
+
+This subsection specifies the characteristics of a user interface which are necessary to enable a user to input O/R addresses represented in either of the formats specified in § B.3.
+
+It is necessary for the user interface to be able to accept any valid combination of attributes from Tables B-1/F.401, B-2/F.401 and B-3/F.401.
+
+If the user interface lists the attributes given in Table B-1/F.401, it is recommended that either the sequence used in Table B-1/F.401 should be used, or if this sequence is incompatible with normal cultural conventions, an alternative sequence may be adopted for representations of addresses which are primarily intended for use within that culture.
+
+If the user omits the ADMD attribute, or omits the value for the ADMD attribute, the ADMD value to be used is a single space provided that the country specified in the O/R address permits use of the single space value for ADMDS.
+
+Where an interface accepts an O/R address as a single string (e.g. in a command line interface), it is necessary to accept any valid labelled format address allowing the user to enter either of the valid delimiters. The interface should not require the attributes to be specified in any particular order.
+
+*Note* – For some existing command line interfaces, it may be necessary to enclose the whole labelled format address in quotes.
+
+If any other type of interface is provided (e.g. a prompting or form-fill interface), it is necessary to provide a means which enables the user to easily associate the identity of each attribute with the labels specified in Tables B-1/F.401, B-2/F.401 and B-3/F.401.
+
+*Note 1* – One way to associate the identity of each attribute with the labels is to follow the name or abbreviation for each attribute with the label in brackets, for example:
+
+|                          |
+|--------------------------|
+| Given name (G)           |
+| Initials (I)             |
+| Surname (S)              |
+| Generation qualifier (Q) |
+| Common name (CN)         |
+| Organization (O)         |
+
+Organizational unit 1 (OU1)  
+Organizational unit 2 (OU2)  
+Organizational unit 3 (OU3)  
+Organizational unit 4 (OU4)  
+Private management domain name (P)  
+Administration management domain name (A)  
+Country (C)
+
+*Note 2* – Many users may have difficulty copying an address presented as a table (either in labelled or self-explanatory format) into a command line interface which uses delimiters.
+
+*Note 3* – For form-fill style interfaces, user performance will be optimized when the interface most closely resembles the format of the supplied address with the same sequence of attributes using the same attribute types or labels.
+
+### B.4.1 *Examples of application*
+
+*Example 1* – The Norwegian user of a command line interface receives a business card containing the following O/R address:
+
+G=john; S=smith; O=a bank ltd; P=abl; A=snomail; C=aq
+
+The command line interface enables the user to type in the address exactly as presented on the card.
+
+*Example 2* – The Norwegian user of a form-fill interface receives the same business card. The form on the screen includes the following field names:
+
+Fornavn (G)  
+Etternavn (S)  
+Organisasjon (O)  
+Privat domene (P)  
+Administrasjonsdomene (A)  
+Land (C)
+
+The user is able to fill in the form by associating the single letter labels on the business card with the same labels in brackets after the Norwegian names of the attributes on the screen. (For form-fill input, the delimiters are not used.)
+
+*Example 3* – The English speaking user of a command line interface receives a document quoting the following O/R address:
+
+|                           |           |
+|---------------------------|-----------|
+| Fornavn (G)               | Per       |
+| Etternavn (S)             | Hansen    |
+| Organisasjon (O)          | Teledir   |
+| Organisasjonsenhet (OU1)  | Forskning |
+| Privat domene (P)         | Tele      |
+| Administrasjonsdomene (A) | Telemax   |
+| Land (C)                  | NO        |
+
+The user has been trained how to use the interface, and can correctly enter the address either as:
+
+g=per;s=hansen;o=teledir;ou1=forskning;p=tele;a=telemax;c=no
+
+or as:
+
+g=per/s=hansen/o=teledir/ou1=forskning/p=tele/a=telemax/c=no
+
+(The input supplied by the human user is not case sensitive.)
+
+# ANNEX C (to Recommendation F.401)
+
+## **Format for notification of ADMD names**
+
+(This annex does not form an integral part of this Recommendation)
+
+<Address of the organization providing the information>
+
+To be sent to: Director  
+CCITT  
+Place des Nations  
+1211 GENEVA 20  
+Switzerland
+
+## C.1 *Notification of X.400 ADMD name*
+
+The information is provided for the purpose of making ADMD names available for reference, and for potential service providers to obtain contact addresses for interconnection arrangements on a bilateral basis.
+
+| Provision of X.400 message handling services          |     |    |                  |
+|-------------------------------------------------------|-----|----|------------------|
+| Service name (MT):                                    |     |    | } As appropriate |
+| Service name (IPM):                                   |     |    |                  |
+| Service name (...):                                   |     |    |                  |
+| ADMD name:                                            |     |    |                  |
+| Country <sup>a)</sup>                                 |     |    |                  |
+| Contact address:<br>(Postal address)                  |     |    |                  |
+| Telephone:                                            |     |    |                  |
+| Telefax:                                              |     |    |                  |
+| Telex:                                                |     |    |                  |
+| X.400:                                                |     |    |                  |
+| HELPDESK<br>available? <sup>b)</sup><br>(check one)   | Yes | No |                  |
+| AUTOANSWER<br>available? <sup>b)</sup><br>(check one) | Yes | No |                  |
+
+<sup>a)</sup> Use Alpha-2 country codes of Annex A.
+
+<sup>b)</sup> It is proposed to provide two O/R-addresses, namely HELPDESK and AUTOANSWER (together with no other attributes than country and domain names).
+
+*Example 1* – S=helpdesk; A=arcom; C=ch;
+
+*Example 2* – S=autoanswer; A=dbp; C=de
+
+*Note* – National practices may impose coordination before sending notification to the ITU.
\ No newline at end of file
diff --git a/marked/F/T-REC-F.421-198811-I_PDF-E/raw.md b/marked/F/T-REC-F.421-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..873054594babb9eb818bc1d5e852d6f0a693dc43
--- /dev/null
+++ b/marked/F/T-REC-F.421-198811-I_PDF-E/raw.md
@@ -0,0 +1,520 @@
+
+
+![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. A lightning bolt symbol is positioned to the right of the globe.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.421**
+
+# **OPERATIONS AND QUALITY OF SERVICE MESSAGE HANDLING SERVICES** ---
+
+## **MESSAGE HANDLING SERVICES: INTERCOMMUNICATION BETWEEN THE IPM SERVICE AND THE TELEX SERVICE**
+
+**ITU-T Recommendation F.421**
+
+(Extract from the *Blue Book*)
+
+---
+
+## NOTES
+
+1 ITU-T Recommendation F.421 was published in Fascicle II.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.
+
+### Recommendation F.421<sup>1)</sup>
+
+## MESSAGE HANDLING SERVICES: INTERCOMMUNICATION BETWEEN THE IPM SERVICE AND THE TELEX SERVICE
+
+The establishment in various countries of message handling service in association with public networks creates the need to produce Recommendations covering the aspects of public message handling services.
+
+The CCITT,
+
+*considering*
+
+- (a) the need for public message handling services;
+- (b) the strategic and commercial importance of standardization of message handling services;
+- (c) the urgent need for intercommunication arrangements for existing telematic services, and other services with public message handling services;
+- (d) the need for a clear distinction between the responsibilities to be allocated to service providers and those of subscribers and/or users;
+- (e) the need for establishing international compatibility between different messaging systems;
+- (f) the growth of the installed base of terminals and personal computers with the ability to access message handling systems;
+- (g) that several F-series Recommendations describe public message handling services;
+- (h) that certain X, T and U-series Recommendations cover relevant aspects of systems used for the provision of messaging services;
+- (i) that Recommendations F.60 and F.69 define the service requirements for the telex service;
+- (j) that Recommendation F.72 defines international telex store-and-forward;
+- (k) that the U-series Recommendations define the technical requirements for the telex service;
+- (l) that Recommendation U.204 defines the technical requirements for the intercommunication between the IPM service and the telex service;
+
+*unanimously declares*
+
+that operational procedures for intercommunication between the public interpersonal messaging service and the telex service shall be in accordance with this Recommendation.
+
+## CONTENTS
+
+- 1 *Scope*
+- 2 *Introduction*
+- 3 *Service outline*
+- 4 *Operational procedures*
+  - 4.1 IPM service to telex service direction
+  - 4.2 Telex service to IPM service direction
+  - 4.3 Construction of the IP-message
+
+---
+
+<sup>1)</sup> This Recommendation is the same as Recommendation F.75 of which only the title appears in Fascicle II.4.
+
+*Annex A* – Abbreviations
+
+*Annex B* – Actions to be taken by the PTLXAU/examples
+
+*Annex C* – IPM message to telex
+
+*Annex D* – Telex message to IPM
+
+## 1 Scope
+
+1.1 This Recommendation describes the general, operational and service procedures for the provision of intercommunication between the public interpersonal messaging service and the telex service.
+
+1.2 The intercommunication is based on store-and-forward principles which allow users of one service to exchange messages with the users of the other service.
+
+# 2 Introduction
+
+The IPM service is a messaging service which may be provided on a variety of networks and allows several forms of addresses, whereas the telex service provides direct connection between subscribers in the telex network.
+
+Therefore, to match dissimilar characteristics of the two services, it is necessary to provide intercommunication via a public telex access unit (PTLXAU). In both IPM service to telex service, and telex service to IPM service directions, the complete message is deposited in the PTLXAU for onward transmission.
+
+In general the selection procedures for the telex subscriber will be two-stage; however, where the destination IPM service user is assigned a numeric address that is part of the national telex numbering plan of the destination country, one-stage selection procedures may be used.
+
+## 3 Service outline
+
+3.1 Communication between subscribers of the telex service and the IPM service is on store-and-forward basis; thus conversational mode interworking between users is not applicable.
+
+3.2 Public access to the IPM service for telex subscribers and delivery of messages to telex subscribers from IPM service users is provided by means of a PTLXAU.
+
+3.3 The PTLXAU belongs to the IPM service.
+
+3.4 In the IPM service to telex service direction, the IPM service retains the responsibility for the message until delivery to the telex subscriber has been completed.
+
+3.5 In the telex service to IPM service direction, the IPM service is responsible for the delivery of the message to the IPM service user, once the input is completed under normal conditions.
+
+3.6 In both IPM service to telex service direction and telex service to IPM service direction, the international connection should be via the international telex network, as shown in Figure 1/F.421.
+
+![Diagram illustrating the model for service intercommunication between Country A and Country B. Country A contains a 'Telex service' oval with two 'Telex network' boxes separated by a dashed vertical line labeled 'International boundary'. Country B contains an 'IPM service' oval with a 'PTLXAU' box. A solid horizontal line connects the second 'Telex network' in Country A to the 'PTLXAU' in Country B. A small text 'CCITT - 0100740-89' is at the bottom right.](8e85c350ee10ead46f7834b148b8b7d3_img.jpg)
+
+The diagram shows two countries, Country A and Country B, separated by an international boundary. Country A contains a 'Telex service' represented by an oval enclosing two 'Telex network' boxes. The international boundary is a dashed vertical line between these two boxes. Country B contains an 'IPM service' represented by an oval enclosing a 'PTLXAU' box. A solid horizontal line connects the second 'Telex network' in Country A to the 'PTLXAU' in Country B. The text 'CCITT - 0100740-89' is located at the bottom right of the diagram.
+
+Diagram illustrating the model for service intercommunication between Country A and Country B. Country A contains a 'Telex service' oval with two 'Telex network' boxes separated by a dashed vertical line labeled 'International boundary'. Country B contains an 'IPM service' oval with a 'PTLXAU' box. A solid horizontal line connects the second 'Telex network' in Country A to the 'PTLXAU' in Country B. A small text 'CCITT - 0100740-89' is at the bottom right.
+
+FIGURE 1/F.421
+
+Model for service intercommunication
+
+3.7 Where two Administrations offer an IPM service, the international boundary may be placed within the IPM service by bilateral agreement. In this configuration, however, international telex connections should continue to be established via the international telex network.
+
+## 4 Operational procedures
+
+### 4.1 *IPM service to telex service direction*
+
+4.1.1 Messages from an IPM service user to a telex subscriber are sent as normal IP-message with the appropriate IPM elements of service, in accordance with Recommendation F.420.
+
+4.1.2 When a message is received by the PTLXAU, the message content will be converted into the format and character repertoire defined for the telex service. This may result in loss of information if the IPM service user does not conform to these defined rules.
+
+*Note* – The conversion process may take place in the message transfer system (MTS) associated with the PTLXAU.
+
+4.1.3 The PTLXAU shall be responsible for the action to be taken for IPM elements of service received in accordance with Recommendation F.420. Annex B shows examples of IPM elements of service together with proposed actions to be taken by the PTLXAU.
+
+4.1.4 Call establishment by and delivery of the message to the telex subscriber should be in accordance with Recommendations F.72 and U.204.
+
+4.1.5 The IP-message sent to the called telex subscriber shall be preceded by a PTLXAU identification. The content of this identification is a national matter but should include the service code “CI”, the code expression “IPM”, and the telex network identification code in accordance with Recommendation F.69, e.g. “CI → IPM → CH”.
+
+4.1.6 A general layout of an IP-message delivered to the telex service is shown in Annex C.
+
+4.1.7 The elements of service related to the IP-message heading shall be converted into printable text. The language of this text is a national matter. The PTLXAU shall transmit the originator O/R address to the called telex subscriber in the form necessary for recall, in accordance with the indications of Table 2/F.421 (see example in Annex C).
+
+4.1.8 In order to help the telex recipients to recall the originator, the PTLXAU could transmit, as the first element of the message heading, some information as guidance. The contents of this field is a national matter, but when used should be called “FOR RECALL” (see Annex C).
+
+4.1.9 Upon delivery of the message to the telex subscriber, a delivery notification should be sent back to the originating IPM service user if requested. In the event of non-delivery of the message to the telex subscriber, a non-delivery notification shall be sent back to the IPM service user (unless the IPM user has requested prevention of non-delivery notification).
+
+### 4.2 *Telex service to IPM service direction*
+
+In this direction, Administrations may implement either or both one-stage and two-stage call set-up procedures.
+
+#### 4.2.1 *One-stage selection*
+
+4.2.1.1 Where one-stage call set-up procedures are used, the number assigned to a user in the IPM service must appear to be part of the national telex numbering plan.
+
+4.2.1.2 The length of the number assigned to the IPM service user shall be in accordance with the relevant U-series signalling Recommendations.
+
+4.2.1.3 The procedures for message transfer within the IPM service, e.g. mapping of the assigned number to an O/R address, are a national matter and not covered by this Recommendation.
+
+4.2.1.4 The call shall be established using normal telex call set-up procedures.
+
+4.2.1.5 The telex number received by the PTLXAU from the telex network shall be verified by the IPM service as being proper to a registered IPM service user. If the verification fails:
+
+- a) where the PTLXAU is provided by the Administration which also provides all or part of the telex network, the service signal NP may be returned;
+- b) where the PTLXAU is not provided by the Administration which also provides all or part of the telex network, the procedures to be applied shall be in accordance with Recommendation F.74.
+
+4.2.1.6 The answerback returned to the calling telex subscriber at call establishment and also during the text input stage shall contain the national telex number assigned to the IPM service user.
+
+4.2.1.7 The call shall be cleared using normal telex call clearing procedures.
+
+4.2.1.8 When the message cannot be delivered to the IPM service user, a non-delivery notification shall be returned to the telex subscriber. The procedures for establishing the calling telex address are specified in Recommendation U.204.
+
+4.2.1.9 The non-delivery notification returned to the originating telex subscriber should contain a reference consisting of the telex address of the IPM service user and time and date of submission to the PTLXAU.
+
+4.2.1.10 The action to be taken when a non-delivery notification cannot be returned to the calling telex subscriber is for further study.
+
+4.2.1.11 The format of notifications and the procedures for their delivery should be in accordance with Recommendation U.204.
+
+4.2.1.12 The use of IPM elements of service by the telex subscriber is for further study.
+
+#### 4.2.2 *Two-stage selection*
+
+4.2.2.1 The telex subscribers shall use normal telex call procedures to access the PTLXAU which is allocated a telex number that is part of the national telex numbering plan of the country in which the PTLXAU is located.
+
+4.2.2.2 Procedures for access to the PTLXAU shall follow Recommendation U.204.
+
+4.2.2.3 A service identifier may be input before the O/R address(es) of the first message. It may allow the Administrations to provide intercommunication with several services through only one PTLXAU (see Tables 1/F.421, 3/F.421 and Annex D).
+
+4.2.2.4 The PTLXAU shall be able to accommodate the following O/R address forms:
+
+- Mnemonic O/R address;
+- Terminal O/R address;
+- Numeric O/R address;
+
+as specified in Recommendation F.401. The O/R address should be input in accordance with the requirements of Recommendation U.204.
+
+It is the responsibility of the originating telex subscriber to be aware of the required attributes specific to the domain of the called IPM service user. Each attribute of the O/R address shall be identified and delimited. The complete O/R address shall be terminated with an end-of-address (EOA) indicator.
+
+The structure of the service identifier and the address input is shown in Table 1/F.421.
+
+Each attribute of the address structure shall be contained in one line.
+
+Each address attribute and the service shall be identified by a code expression according to Tables 2/F.421 and 3/F.421.
+
+4.2.2.5 Under normal conditions, the message input will be terminated by an end of message (EOM) or an end of transmission (EOT) signal. In case where no EOM or EOT signal is received, the PTLXAU shall forward any input received prior to call disconnect with the added text "THIS MESSAGE MAY BE INCOMPLETE". Annex D shows a general layout applicable in case of submission of message(s) to the PTLXAU by the telex subscriber.
+
+4.2.2.6 Except as defined in 4.2.2.5 above, the action to be taken when abnormal conditions are encountered during message input shall be in accordance with Recommendation U.204.
+
+TABLE 1/F.421
+
+#### **Telex service to IPM service address structure**
+
+|                                       |
+|---------------------------------------|
+| Service identifier                    |
+| Address attribute identifier <value>  |
+| .                                     |
+| .                                     |
+| .                                     |
+| Address attribute identifier <value>  |
+| End of single O/R address (+)         |
+| [Next O/R address(es)]                |
+| [Request for IPM elements of service] |
+| End of address(es) (BT)               |
+| [Request for delivery notification]   |
+
+*Note – [ ] indicates optional attributes.*
+
+TABLE 2/F.421
+
+#### **Code expressions for address attribute identifiers**
+
+| Address attribute                              | Format        |
+|------------------------------------------------|---------------|
+| Country name                                   | CTN → <value> |
+| Administration domain name                     | ADM → <value> |
+| Private domain name                            | PRI → <value> |
+| Organization name                              | ORG → <value> |
+| Organisation unit name(s)                      | OUN → <value> |
+| Personal name                                  |               |
+| – Surname                                      | SUR → <value> |
+| – Given name                                   | GIV → <value> |
+| – Initials                                     | INI → <value> |
+| – Generation qualifier                         | GEN → <value> |
+| – Common name                                  | COM → <value> |
+| Numeric user identifier                        | NUS → <value> |
+| Terminal type and network address<br>for telex |               |
+| teletex                                        | TLX → <value> |
+| fascimile                                      | TTX → <value> |
+| videotex                                       | FAX → <value> |
+| Domain defined attribute(s)                    | VTX → <value> |
+| – Type                                         | DDT → <value> |
+| – Value                                        | DDV → <value> |
+
+*Note 1 – The symbol → equals a space .*
+
+*Note 2 – Allowed attribute values are specified in Recommendation F.401.*
+
+TABLE 3/F.421
+
+##### **Code expression for the service identifier**
+
+| Service                         | Format |
+|---------------------------------|--------|
+| Interpersonal messaging service | IPM    |
+
+4.2.2.7 During the input stage of the address, the PTLXAU shall validate, as a minimum, the following O/R address formats, as specified by the domain:
+
+- The existence of mandatory attributes.
+- The existence of non-allowed attributes.
+- The minimum and maximum allowed number of characters in each attribute.
+- The existence of non-allowed characters in an attribute.
+
+Where applicable, the existence/non-existence of non-significant character(s) preceding or following the attribute values shall not prevent validation.
+
+Despite the acceptance by the PTLXAU of the submitted O/R address, there is no guarantee that the message will be subsequently delivered and, in this case, the originating telex subscriber will be charged for a message which was not delivered. It is therefore desirable that a means of verifying the existence of the O/R address be provided and the method of achieving this is left for further study.
+
+4.2.2.8 The service principles for delivery and non-delivery notifications should be in accordance with Recommendation F.72. The format of the notification messages is defined in Recommendation U.204. Delivery notification may be requested as a code expression following the end of address signal.
+
+### 4.3 *Construction of the IP-message*
+
+The message received by the PTLXAU shall be delivered to the IPM user(s) in accordance with following rules.
+
+#### 4.3.1 *P2 body part*
+
+The received message, excluding the recipient address(es), shall form the body of the IP-message. All the received characters shall be delivered except the WRU signals.
+
+#### 4.3.2 *Recipient O/R address*
+
+All recognized O/R addresses shall be assumed as primary recipients. By default, these primary recipients will not be disclosed to each other.
+
+#### 4.3.3 *Originator indication*
+
+The calling telex subscriber address shall be converted by the PTLXAU into the format of a terminal O/R address and shall be placed in the originator indication element of service field.
+
+#### 4.3.4 *Subject indication*
+
+The PTLXAU shall generate the element of service which will cause TELEX to appear in the subject indication element of service field.
+
+#### 4.3.5 *IP-message identification*
+
+The content of the message reference information returned to the calling telex subscriber shall also be used as the unique identifier in the IP-message identification element of service field.
+
+#### 4.3.6 *Grade of delivery selection*
+
+The PTLXAU shall set the grade of delivery selection element of service to the value URGENT.
+
+#### 4.3.7 *Conversion prohibition in case of loss of information*
+
+The use of the element of service – conversion prohibition in case of loss of information – is for further study.
+
+#### 4.3.8 *Disclosure of other recipients*
+
+This element of service shall be set by the PTLXAU when the originating telex subscriber requests the disclosure of other recipients. The procedures for requesting this disclosure are defined in Recommendation U.204.
+
+#### 4.3.9 *Deferred delivery*
+
+This element of service shall be set by the PTLXAU when the originating telex subscriber requests deferred delivery of his message. The procedures for requesting deferred delivery are defined in Recommendation U.204.
+
+*Note* – The code expressions to be used for the selection of the elements of service described in §§ 4.3.8 and 4.3.9 by the telex subscriber, are shown in Table 4/F.421.
+
+TABLE 4/F.421
+
+##### **Code expressions for the use of IPM elements of service**
+
+| IPM element of service         | Format                |
+|--------------------------------|-----------------------|
+| Disclosure of other recipients | DUR                   |
+| Deferred delivery              | DEF → <value>         |
+| Delivery notification          | BT, ACK <sup>a)</sup> |
+
+<sup>a)</sup> The request for delivery notification may be given together with the code for end of adresse (es) (BT) if delivery notification is required.
+
+*Note* – The symbol → equals a space.
+
+#### 4.3.10 *Other elements of service*
+
+Elements of service of the basic IPM service other than those specified above shall be set by the PTLXAU in accordance with the requirements of the domain to which it belongs.
+
+## ANNEX A (to Recommendation F.421)
+
+### **Abbreviations**
+
+|        |                                                     |
+|--------|-----------------------------------------------------|
+| A/B    | Answerback                                          |
+| ACK    | Request for Delivery Notification Signal            |
+| ADM    | Administration Management Domain                    |
+| BT     | End of Address(es) Signal                           |
+| CI     | Conversation Impossible                             |
+| COM    | Common Name                                         |
+| CTN    | Country Name                                        |
+| DDT    | Domain Defined Attribute Type                       |
+| DDV    | Domain Defined Attribute Value                      |
+| DEF    | Deferred Delivery                                   |
+| DUR    | Disclosure of other Recipients                      |
+| EOA    | End of Address                                      |
+| EOM    | End of Message                                      |
+| EOT    | End of Transaction                                  |
+| FAX    | Facsimile                                           |
+| GEN    | Generation Qualifier                                |
+| GIV    | Given Name                                          |
+| I      | Initials                                            |
+| IP     | Interpersonal                                       |
+| IPM    | Interpersonal Messaging                             |
+| MT     | Message Transfer                                    |
+| MTS    | Message Transfer System                             |
+| NP     | The called party is not, or no longer, a subscriber |
+| NUS    | Numeric User Identifier                             |
+| O/R    | Originator/Recipient                                |
+| ORG    | Organization Name                                   |
+| OUN    | Organization Unit Name(s)                           |
+| P2     | IPM Protocol                                        |
+| PRI    | Private Domain Name                                 |
+| PTLXAU | Public Telex Access Unit                            |
+| SUR    | Surname                                             |
+| TID    | Terminal Identifier                                 |
+| TLX    | Telex                                               |
+| TTX    | Teletex                                             |
+| UTC    | Universal Coordinated Time                          |
+| VTX    | Videotex                                            |
+| WRU    | Who Are You                                         |
+| +      | End of Single O/R Address signal                    |
+| →      | Space                                               |
+
+*Note 1* – For a glossary of terms see Annex A to Recommendation F.400.
+
+*Note 2* – For references see Recommendation F.400.
+
+## ANNEX B (to Recommendation F.421)
+
+### **Actions to be taken by the PTLXAU/examples**
+
+Basic IPM elements of service and essential optional IPM user facilities which have to be processed by the PTLXAU in the case where a message is sent from the IPM service to the telex service direction (Table B-1/F.421).
+
+TABLE B-1/F.421
+
+| Reference<br>Rec. F.400<br>Annex B | Elements of service             | Action to be taken                                                                      | Examples                          |
+|------------------------------------|---------------------------------|-----------------------------------------------------------------------------------------|-----------------------------------|
+| B.5                                | Authorizing users indication    | Display in message heading                                                              | Authority : → <value>             |
+| B.6                                | Auto-forwarded indication       | Ignore                                                                                  |                                   |
+| B.8                                | Blind copy recipient indication | Display the O/R descriptor information of the blind copy recipient(s)                   | BCC → <value>                     |
+| B.9                                | Body part encryption indication | The PTLXAU shall send a non-delivery notification to the originator                     |                                   |
+| B.12                               | Content type indication         | National matter for content types different than P2                                     |                                   |
+| B.13                               | Conversion prohibition          | If ITA2, ignore. Otherwise the PTLXAU generates a non-delivery notification             |                                   |
+| B.15                               | Converted indication            | Ignore                                                                                  |                                   |
+| B.18                               | Cross referencing indication    | Display in message heading                                                              | Reference → <value>               |
+| B.21                               | Delivery notification           | The PTLXAU shall send a delivery notification to the originator                         |                                   |
+| B.22                               | Delivery time stamp indication  | Ignore                                                                                  |                                   |
+| B.25                               | Disclosure of other recipients  | Disclose all recipients                                                                 |                                   |
+| B.26                               | DL expansion history indication | Ignore                                                                                  |                                   |
+| B.29                               | Expiry date indication          | Display in message heading                                                              | Message invalid after : → <value> |
+| B.31                               | Forwarded IP-message indication | the PTLXAU shall build a message heading for each IP-message contained in the body part |                                   |
+| B.32                               | Grade of delivery selection     | National matter                                                                         |                                   |
+| B.34                               | Implicit conversion             | Convert to telex according to Rec. X.408                                                |                                   |
+| B.35                               | Importance indication           | Display in message heading                                                              | Message importance: → <value>     |
+| B.37                               | IP-message identification       | display in message heading                                                              | Message reference: → <value>      |
+| B.38                               | Language indication             | Ignore                                                                                  |                                   |
+| B.39                               | Latest delivery designation     | National matter                                                                         |                                   |
+
+TABLE B-1/F.421 (cont.)
+
+| References<br>Rec. F.400<br>Annex B | Elements of message                           | Action to be taken                                                                                                      | Examples                                                         |
+|-------------------------------------|-----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|
+| B.41                                | Message identification                        | Ignore                                                                                                                  |                                                                  |
+| B.45                                | Multi-destination delivery                    | Deliver the message to all recipients                                                                                   |                                                                  |
+| B.46                                | Multi-part body                               | Messages containing not supported body parts are not delivered. Send back a non-delivery notification to the originator |                                                                  |
+| B.47                                | Non-delivery notification                     | The PTLXAU shall generate a delivery report                                                                             |                                                                  |
+| B.48                                | Non-receipt notification request              | Ignore                                                                                                                  |                                                                  |
+| B.52                                | Obsoleting indication                         |                                                                                                                         | Obsoletes: → <value>                                             |
+| B.54                                | Original encoded information types indication | Ignore                                                                                                                  |                                                                  |
+| B.55                                | Originator indication                         | Ignore                                                                                                                  |                                                                  |
+| B.56                                | Originator request alternate recipient        | National matter                                                                                                         |                                                                  |
+| B.62                                | Primary and copy recipients indication        | Display the O/R descriptor information of the recipient(s) in the message heading                                       | TO: → <value><br>TO: → <value><br>CC: → <value><br>CC: → <value> |
+| B.63                                | Probe                                         | National matter                                                                                                         |                                                                  |
+| B.67                                | Receipt notification request indication       | Ignore                                                                                                                  |                                                                  |
+| B.72                                | Reply request indication                      | Display in message heading                                                                                              | Reply → requested →<br>by → sender                               |
+| B.73                                | Replying IP – message indication              | Display in message heading                                                                                              | Reply to message: →<br><value>                                   |
+| B.80                                | Sensibility indication                        | Display in message heading just above text of body                                                                      |                                                                  |
+| B.88                                | Subject indication                            | Display in message heading just above text of body                                                                      | Subject: → <value>                                               |
+| B.89                                | Submission time stamp                         | Display in message heading                                                                                              | Submitted: → <value><br>→ UTC                                    |
+| B.90                                | Typed body                                    | Ignore                                                                                                                  |                                                                  |
+
+Note – The symbol → equals a space.
+
+## ANNEX C
+
+(to Recommendation F.421)
+
+### IPM message to telex
+
+General layout of a message originated by an IPM service user and delivered by the PTLXAU to a telex subscriber.
+
+![Diagram showing the general layout of an IPM message to a telex subscriber. A vertical double-headed arrow on the left is labeled 'Telex call'. On the right, a box labeled 'IP message' contains several nested boxes. From top to bottom, these are: 'Exchange of answerbacks between telex subscriber and PTLXAU', 'For recall "text and O/R addresses"', 'PTLXAU identifier', 'Message heading', 'Body', and another 'Exchange of answerbacks'.](cab0834804fb031b43865554cc8d06ab_img.jpg)
+
+Diagram illustrating the general layout of an IPM message to a telex subscriber. The diagram shows a vertical stack of components within an "IP message" box, corresponding to a "Telex call".
+
+- A vertical double-headed arrow on the left is labeled **Telex call**.
+- The main content area on the right is labeled **IP message** and consists of the following sequence:
+  - Exchange of answerbacks between telex subscriber and PTLXAU
+  - Box: For recall “text and O/R addresses”
+  - Box: PTLXAU identifier
+  - Large Box containing:
+    - Box: Message heading
+    - Box: Body
+  - Exchange of answerbacks between telex subscriber and PTLXAU
+
+CCITT – 0100750-89
+
+Diagram showing the general layout of an IPM message to a telex subscriber. A vertical double-headed arrow on the left is labeled 'Telex call'. On the right, a box labeled 'IP message' contains several nested boxes. From top to bottom, these are: 'Exchange of answerbacks between telex subscriber and PTLXAU', 'For recall "text and O/R addresses"', 'PTLXAU identifier', 'Message heading', 'Body', and another 'Exchange of answerbacks'.
+
+Display of the originator O/R address related information to the telex user in the message heading:
+
+a) Two-stage selection:
+
+FROM:→ GIV→francois  
+SUR→maurer  
+ORG→swiss→ptt  
+ADM→arcom400  
+CTN→ch
+
+b) One-stage selection:
+
+FROM:→(F.74 A/B)
+
+## ANNEX D
+
+(to Recommendation F.421)
+
+### **Telex message to IPM**
+
+(Two-stage selection)
+
+General layout of a message originated by a telex subscriber using the two-stage selection, submitted to the PTLXAU for delivery to the IPM service.
+
+![Sequence diagram of a telex call showing message structure and exchange of answerbacks.](a26e142d3df5bef41a84a9dd099d7825_img.jpg)
+
+```
+
+        graph TD
+        A[Exchange of answerbacks between telex subscriber and PTLXAU] --> B[Input of service identifier and O/R address(es) according to Table 1/F.421]
+        subgraph "First message"
+        B --> C[Code expressions "DUR", "DEF" or "ACK" (only if elements of service B19, B.21 or B.25 are requested)]
+        C --> D[Text of the message]
+        D --> E[EOM signal]
+        end
+        subgraph "Follow-up message(s)"
+        E --> F[Input of service identifier and O/R address(es) according to Table 1/F.421]
+        F --> G[Code expressions "DUR", "DEF" or "ACK" (only if elements of service B19, B.21 or B.25 are requested)]
+        G --> H[Text of the message]
+        H --> I[EOM signal]
+        I --> J[EOT signal]
+        end
+        J --> K[Exchange of answerbacks between telex subscriber and PTLXAU]
+    
+```
+
+CCITT - 0100760-89
+
+Sequence diagram of a telex call showing message structure and exchange of answerbacks.
\ No newline at end of file
diff --git a/marked/F/T-REC-F.511-201404-I_PDF-E/raw.md b/marked/F/T-REC-F.511-201404-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..7601bf5a3585bfb728062c4167141731e767a578
--- /dev/null
+++ b/marked/F/T-REC-F.511-201404-I_PDF-E/raw.md
@@ -0,0 +1,1732 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.511**
+
+(04/2014)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Directory services
+
+---
+
+**Directory service – Support of tag-based  
+identification services**
+
+Recommendation ITU-T F.511
+
+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 F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| <b>TELEGRAPH SERVICE</b>                                        |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| <b>MOBILE SERVICE</b>                                           |                    |
+| Mobile services and multdestination satellite services          | F.110–F.159        |
+| <b>TELEMATIC SERVICES</b>                                       |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| <b>MESSAGE HANDLING SERVICES</b>                                | F.400–F.499        |
+| <b>DIRECTORY SERVICES</b>                                       | <b>F.500–F.549</b> |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | F.600–F.699        |
+| <b>AUDIOVISUAL SERVICES</b>                                     | F.700–F.799        |
+| <b>ISDN SERVICES</b>                                            | F.800–F.849        |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | F.850–F.899        |
+| <b>HUMAN FACTORS</b>                                            | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## Recommendation ITU-T F.511
+
+# Directory service – Support of tag-based identification services
+
+## Summary
+
+Recommendation ITU-T F.511 provides guidance for the use of directory services to support tag-based identification applications by reference to the directory capabilities specified in the ITU-T X.500 series of Recommendations | ISO/IEC 9594 (all parts), and in the lightweight directory access protocol (LDAP) specifications as developed within Internet Engineering Task Force (IETF). A tag is also called an automatic identification and data capture (AIDC) media. It holds an identifier that identifies the item to which the AIDC media is affixed or associated. The directory may be used to store information associated with the AIDC media.
+
+This Recommendation identifies two cases: one case is where the identifier is used as a whole to access a centralized directory, and the other case is where the structure of the identifier is explored to access distributed directory systems, when it is not feasible for a specific environment to hold all relevant information in a single directory. In the latter situation the top-level information could be held by some types of independent service providers, while the company and/or item-related information may be held by the information owner.
+
+The primary focus is on radio frequency identification (RFID) tags as specified in the GS1 EPCglobal specifications and in ISO and ISO/IEC International Standards.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.511    | 2014-04-06 | 17          | <a href="http://handle.itu.int/11.1002/1000/12143">11.1002/1000/12143</a> |
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                                      | 3  |
+| 3.1  | Terms defined elsewhere .....                                                          | 3  |
+| 3.2  | Terms defined in this Recommendation .....                                             | 4  |
+| 4    | Abbreviations and acronyms .....                                                       | 4  |
+| 5    | Conventions .....                                                                      | 6  |
+| 6    | Involved standards organizations .....                                                 | 6  |
+| 6.1  | GS1 EPCglobal.....                                                                     | 6  |
+| 6.2  | ISO and ISO/IEC .....                                                                  | 6  |
+| 7    | AIDC media and associated information.....                                             | 7  |
+| 8    | Access to associated information using directory technology.....                       | 7  |
+| 9    | Unique item identifier (UII) and electronic product code (EPC) .....                   | 8  |
+| 9.1  | General .....                                                                          | 8  |
+| 9.2  | Electronic product code (EPC) types .....                                              | 9  |
+| 9.3  | Unique item identifier (UII) types .....                                               | 9  |
+| 9.4  | Global uniqueness of EPCs and UIIs .....                                               | 9  |
+| 10   | Locating associated information for centralized AIDC identification applications ..... | 9  |
+| 10.1 | Search using EPC in a centralized environment.....                                     | 10 |
+| 10.2 | Search using UII together with AFI in a centralized environment.....                   | 11 |
+| 11   | Issues for a distributed AIDC environment .....                                        | 11 |
+| 12   | EPC and UII formatting and URN subtree structure .....                                 | 13 |
+| 12.1 | EPC and UII formatting information.....                                                | 13 |
+| 12.2 | EPC and UII represented by URN directory subtrees .....                                | 14 |
+| 13   | EPC/UII format information.....                                                        | 17 |
+| 13.1 | EPC/UII format DIT subtree .....                                                       | 17 |
+| 13.2 | EPC format information .....                                                           | 17 |
+| 13.3 | UII format information .....                                                           | 17 |
+| 14   | Support of ITU-T Y.2213 .....                                                          | 19 |
+| 14.1 | General .....                                                                          | 19 |
+| 14.2 | Multiple user groups for same EPC or UII.....                                          | 20 |
+| 14.3 | Reverse identifier resolution.....                                                     | 20 |
+| 14.4 | Location-based information.....                                                        | 20 |
+| 14.5 | Avoidance of single-point-of-failure .....                                             | 20 |
+
+|                                                                                       | Page |
+|---------------------------------------------------------------------------------------|------|
+| Appendix I – Use of OIDs in an RFID environment .....                                 | 21   |
+| I.1    Introduction .....                                                             | 21   |
+| I.2    OID used in the ISO environment .....                                          | 21   |
+| I.3    ISO/IEC 15459 OID structure vs. data identifiers/application identifiers ..... | 22   |
+| Appendix II – Introduction to ITU-T X.500-series/LDAP concepts .....                  | 23   |
+| II.1   Directory entries and their content .....                                      | 23   |
+| II.2   Directory information tree (DIT).....                                          | 23   |
+| II.3   Directory subtrees.....                                                        | 23   |
+| II.4   Distinguished names and URNs .....                                             | 24   |
+| II.5   Directory search operation .....                                               | 24   |
+| II.6   Entry information selection .....                                              | 25   |
+| II.7   Pointers to other directories (referrals).....                                 | 25   |
+| Appendix III – Introduction to RFID tag structure .....                               | 26   |
+| III.1  Scope of appendix .....                                                        | 26   |
+| III.2  ISO/IEC 18000-6C and ISO/IEC 18000-3m3 RFID tag structure .....                | 26   |
+| III.3  Bank '00'B (reserved memory) .....                                             | 26   |
+| III.4  Bank '01'B (UII/EPC memory).....                                               | 27   |
+| III.5  Bank '10'B (TID memory).....                                                   | 27   |
+| III.6  Bank '11'B (user memory).....                                                  | 28   |
+| Appendix IV – Overview of EPC types.....                                              | 30   |
+| IV.1   Scope of appendix .....                                                        | 30   |
+| IV.2   Structure of serialized global trade item number (SGTIN) EPC types .....       | 30   |
+| IV.3   Structure of serial shipping container code (SSCC) EPC types .....             | 31   |
+| IV.4   Structure of serialized global location number (SGLN) EPC types.....           | 32   |
+| IV.5   Structure of global returnable asset identifier (GRAI) EPC types .....         | 32   |
+| IV.6   Structure of global individual asset identifier (GIAI) EPC types.....          | 33   |
+| IV.7   Structure of global service relation number (GSRN) EPC types .....             | 33   |
+| IV.8   Structure of global document type identifier (GDTI) EPC types.....             | 33   |
+| Appendix V – Example of retrieving EPC format information .....                       | 35   |
+| Appendix VI – Overview of ISO/IEC 15459 UII types.....                                | 38   |
+| VI.1   Overview .....                                                                 | 38   |
+| VI.2   Data identifier field.....                                                     | 38   |
+| VI.3   Issuing agency codes (IAC).....                                                | 39   |
+| VI.4   Company identification number (CIN) .....                                      | 40   |
+| VI.5   Remaining fields.....                                                          | 40   |
+| Appendix VII – Examples of retrieving UII format information.....                     | 41   |
+| VII.1  Scope of appendix .....                                                        | 41   |
+| VII.2  IAC=UN (Dun and Bradstreet) .....                                              | 41   |
+| VII.3  IAC=J example (UPU) .....                                                      | 42   |
+
+|                                                 | <b>Page</b> |
+|-------------------------------------------------|-------------|
+| Appendix VIII – The format attribute type ..... | 44          |
+| VIII.1 Introduction .....                       | 44          |
+| VIII.2 EPC format information .....             | 44          |
+| VIII.3 UII format information .....             | 44          |
+| Bibliography.....                               | 46          |
+
+
+
+# Recommendation ITU-T F.511
+
+# Directory service – Support of tag-based identification services
+
+## 1 Scope
+
+The scope of this Recommendation is to provide sufficient information for the use of directories to support tag-based identification applications without having to study the details of the many specifications on tag-based identification. It describes how this support may be provided using systems supporting the ITU-T X.500 | ISO/IEC 9594 series of Recommendations. The capabilities required are primarily limited to those that are also supported by the lightweight directory access protocol (LDAP) specifications.
+
+NOTE 1 – Use of LDAP-based systems provides low-cost solutions.
+
+For environments that are more complex this Recommendation also provides guidance on how directory responsibilities may be split between general service providers and information owners.
+
+This Recommendation is only concerned with tag-based identification as related to automatic identification and data capture (AIDC) media as specified in numerous ISO/IEC and ISO International Standards and in GS1 specifications. This Recommendation is limited to the following types of AIDC media:
+
+- The ISO/IEC 18000-6C tag type as defined in [ISO/IEC 18000-63]. This tag type is identical to the GS1 Class 1 Gen 2 tag type.
+- The ISO/IEC 18000-3 Mode 3 tag type as defined in [ISO/IEC 18000-3].
+
+NOTE 2 – Support for other types of AIDC media may be added in the future.
+
+## 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 X.500-series] Recommendation ITU-T X.5xx (2012) | ISO/IEC 9594-x:2014 series,  
+*Information technology – Open Systems Interconnection – The Directory.*
+- [ITU-T X.500] Recommendation ITU-T X.500 (2012) | ISO/IEC 9594-1:2014, *Information technology – Open Systems Interconnection – The Directory: Overview of concepts, models and services.*
+- [ITU-T X.501] Recommendation ITU-T X.501 (2012) | ISO/IEC 9594-2:2014, *Information technology – Open Systems Interconnection – The Directory: Models.*
+- [ITU-T X.509] Recommendation ITU-T X.509 (2012) | ISO/IEC 9594-8:2014, *Information technology – Open Systems Interconnection – The Directory: Public-key and attribute certificate frameworks.*
+- [ITU-T X.511] Recommendation ITU-T X.511 (2012) | ISO/IEC 9594-3:2014, *Information technology – Open Systems Interconnection – The Directory: Abstract service definition.*
+
+- [ITU-T X.518] Recommendation ITU-T X.518 (2012) | ISO/IEC 9594-4:2014, *Information technology – Open Systems Interconnection – The Directory: Procedures for distributed operation.*
+- [ITU-T X.519] Recommendation ITU-T X.519 (2012) | ISO/IEC 9594-5:2014, *Information technology – Open Systems Interconnection – The Directory: Protocol specifications.*
+- [ITU-T X.520] Recommendation ITU-T X.520 (2012) | ISO/IEC 9594-6:2014, *Information technology – Open Systems Interconnection – The Directory: Selected attribute types.*
+- [ITU-T X.521] Recommendation ITU-T X.521 (2012) | ISO/IEC 9594-7:2014, *Information technology – Open Systems Interconnection – The Directory: Selected object classes.*
+- [ITU-T X.525] Recommendation ITU-T X.525 (2012) | ISO/IEC 9594-9:2014, *Information technology – Open Systems Interconnection – The Directory: Replication.*
+- [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 Y.2213] Recommendation ITU-T Y.2213 (2008), *NGN service requirements and capabilities for network aspects of applications and services using tag-based identification.*
+- [IETF RFC 3061] IETF RFC 3061 (2001), *A URN Namespace of Object Identifiers.*
+- [IETF RFC 4510] IETF RFC 4510 (2006), *Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map.*
+- [IETF RFC 4511] IETF RFC 4511 (2006), *Lightweight Directory Access Protocol (LDAP): The Protocol.*
+- [IETF RFC 4516] IETF RFC 4516 (2006), *Lightweight Directory Access Protocol (LDAP): Uniform Resource Locator.*
+- [IETF RFC 5134] IETF RFC 5134 (2008), *A Uniform Resource Name Namespace for the EPCglobal Electronic Product Code (EPC) and Related Standards.*
+- [ISO/IEC 15459 S] ISO/IEC 15459 all parts, *Information technology – Unique identifiers.*
+- [ISO/IEC 15459-1] ISO/IEC 15459-1:2006, *Information technology – Unique identifiers – Part 1: Unique identifiers for transport units.*
+- [ISO/IEC 15459-2] ISO/IEC 15459-2:2006, *Information technology – Unique identifiers – Part 2: Registration procedures.*
+- [ISO/IEC 15459-3] ISO/IEC 15459-3:2006, *Information technology – Unique identifiers – Part 3: Common rules for unique identifiers.*
+- [ISO/IEC 15459-4] ISO/IEC 15459-4:2008, *Information technology – Unique identifiers – Part 4: Individual items.*
+- [ISO/IEC 15459-5] ISO/IEC 15459-5:2007, *Information technology – Unique identifiers – Part 5: Unique identifiers for returnable transport items (RTIs).*
+- [ISO/IEC 15459-6] ISO/IEC 15459-6:2007, *Information technology – Unique identifiers – Part 6: Unique identifier for product groupings.*
+
+- [ISO/IEC 15961-1] ISO/IEC 15961-1:2013, *Information technology – Radio frequency identification (RFID) for item management: Data protocol – Part 1: Application interface.*
+- [ISO 17363] ISO 17363:2013, *Supply chain applications of RFID – Freight containers.*
+- [ISO 17364] ISO 17364:2013, *Supply chain applications of RFID – Returnable transport items (RTIs) and returnable packaging items (RPIs).*
+- [ISO 17365] ISO 17365:2013, *Supply chain applications of RFID – Transport units.*
+- [ISO 17366] ISO 17366:2013, *Supply chain applications of RFID – Product packaging.*
+- [ISO 17367] ISO 17367:2013, *Supply chain applications of RFID – Product tagging.*
+- [ISO/IEC 18000-3] ISO/IEC 18000-3:2010, *Information technology – Radio frequency identification for item management – Part 3: Parameters for air interface communications at 13,56 MHz.*
+- [ISO/IEC 18000-6] ISO/IEC 18000-6:2013, *Information technology – Radio frequency identification for item management – Part 6: Parameters for air interface communications at 860 MHz to 960 MHz General.*
+- [ISO/IEC 18000-63] ISO/IEC 18000-63:2013, *Information technology – Radio frequency identification for item management – Part 6: Parameters for air interface communications at 860 MHz to 960 MHz Type C.*
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 attribute** [ITU-T X.501]: Information of a particular type. Entries are composed of attributes.
+
+**3.1.2 attribute type** [ITU-T X.501]: That component of an attribute which indicates the class of information given by that attribute.
+
+**3.1.3 attribute value** [ITU-T X.501]: A particular instance of the class of information indicated by an attribute type.
+
+**3.1.4 attribute value assertion** [ITU-T X.501]: A proposition, which may be true, false, or undefined, according to the specified matching rules for the type, concerning the presence in an entry of an attribute value of a particular type.
+
+**3.1.5 directory information base (DIB)** [ITU-T X.501]: The complete set of information to which the Directory provides access, and which includes all of the pieces of information which can be read or manipulated using the operations of the Directory.
+
+**3.1.6 directory information tree (DIT)** [ITU-T X.501]: The DIB considered as a tree, whose vertices (other than the root) are the Directory entries.
+
+NOTE – The term "DIT" is used instead of "DIB" only in contexts where the tree structure of the information is relevant.
+
+**3.1.7 distinguished name (of an entry)** [ITU-T X.501]: The name of an entry which is formed from the sequence of the relative distinguished names (RDNs) of the entry and each of its superior entries. Every object entry, alias entry and subentry has precisely one distinguished name.
+
+**3.1.8 filter** [ITU-T X.511]: An assertion about the presence or value of certain attributes of an entry in order to limit the scope of a search.
+
+**3.1.9 filter item** [ITU-T X.511]: A filter item is an assertion about the presence or value(s) of attributes in the entry under test.
+
+**3.1.10 identifier** [b-ITU-T Y.2091]: An identifier is a series of digits, characters and symbols or any other form of data used to identify subscriber(s), user(s), network element(s), function(s), network entity(ies) providing services/applications, or other entities (e.g., physical or logical objects). Identifiers can be used for registration or authorization. They can be either public to all networks, shared between a limited number of networks or private to a specific network (private IDs are normally not disclosed to third parties).
+
+**3.1.11 relative distinguished name (RDN)** [ITU-T X.501]: A set of one or more attribute type and value pairs, each of which matches a distinct distinguished attribute value of the entry.
+
+### **3.2 Terms defined in this Recommendation**
+
+This Recommendation defines the following terms:
+
+**3.2.1 associated information:** This is the information external to an AIDC media that is associated with the identifier on the AIDC media. The associated information may be a movie, information about a parcel, manufacture contact information, product specification, or it could be anything else.
+
+**3.2.2 automatic identification and data capture (AIDC):** Data input without typing. Data is captured automatically usually using equipment such as barcode readers, magnetic-stripe readers, RFID tag readers, etc.
+
+**3.2.3 automatic identification and data capture (AIDC) client system:** A component that formats information retrieved by an ID terminal into either a DAP request or an LDAP request.
+
+**3.2.4 automatic identification and data capture (AIDC) media:** A media that may hold information that has been retrieved using AIDC techniques.
+
+**3.2.5 electronic product code (EPC):** Information typically encoded in a radio frequency identification tag to uniquely identify a physical object (e.g. a unique item identifier (UII)).
+
+**3.2.6 EPCglobal environment:** The context within GS1 EPCglobal specifications for generating radio frequency identification – automatic identification and data capture (RFID-AIDC) media specifications.
+
+**3.2.7 identity (ID) terminal:** A device with a data reading and optional writing capability which reads (and optionally writes) identifier(s) and possible application data from/to an automatic identification and data capture (AIDC) media. It is a common term for radio frequency identification (RFID) tag readers, barcode readers, etc.
+
+**3.2.8 ISO environment:** The context established by ISO or ISO/IEC for generating automatic identification and data capture (AIDC) media specification.
+
+**3.2.9 ITU-T X.500 system:** An infrastructure consisting of one or more interconnected directory system agents (DSAs) and zero or more lightweight directory access protocol (LDAP) servers.
+
+**3.2.10 RFID tag:** Automatic identification and data capture (AIDC) media that can be queried by means of a suitably modulated inductive or radiating electromagnetic signal to transfer information to a centralized tag-based information system. (in some specifications this is also called an RF tag).
+
+**3.2.11 unique item identifier (UII):** An identifier as defined in the ISO environment and which is unique within a specific context.
+
+## **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+AFI            Application Family Identifier
+
+|       |                                                    |
+|-------|----------------------------------------------------|
+| AI    | Application Identifier                             |
+| AIDC  | Automatic Identification and Data Capture          |
+| ASCII | American Standard Code for Information Interchange |
+| ASN.1 | Abstract Syntax Notation One                       |
+| CAGE  | Commercial And Governmental Entity                 |
+| CFR   | Code of Federal Regulations                        |
+| CIN   | Company Identification Number                      |
+| CRC   | Cyclic Redundancy Check                            |
+| DAP   | Directory Access Protocol                          |
+| DI    | Data Identifier                                    |
+| DIB   | Directory Information Base                         |
+| DIT   | Directory Information Tree                         |
+| DoD   | Department Of Defence                              |
+| DSA   | Directory System Agent                             |
+| DSFID | Data Storage Format Identifier                     |
+| DUA   | Directory User Agent                               |
+| EDI   | Electronic Data Interchange                        |
+| EOT   | End Of Transmission                                |
+| EPC   | Electronic Product Code                            |
+| GDTI  | Global Document Type Identifier                    |
+| GIAI  | Global Individual Asset Identifier                 |
+| GID   | General Identifier                                 |
+| GRAI  | Global Returnable Asset Identifier                 |
+| GSRN  | Global Service Relation Number                     |
+| IAC   | Issuing Agency Code                                |
+| ID    | Identity                                           |
+| LDAP  | Lightweight Directory Access Protocol              |
+| MDID  | Mask-Designer Identification Code                  |
+| NEN   | Nederlands Normalisatie-instituut                  |
+| NCAGE | NATO Commercial And Governmental Entity            |
+| NGN   | Next-Generation Network                            |
+| OID   | Object Identifier                                  |
+| RAID  | Redundant Arrays of Inexpensive Disks              |
+| RDN   | Relative Distinguished Name                        |
+| RFID  | Radio Frequency Identification                     |
+| RTI   | Returnable Transport Item                          |
+| SGLN  | Serialized Global Location Number                  |
+
+|       |                                     |
+|-------|-------------------------------------|
+| SGTIN | Serialized Global Trade Item Number |
+| SSCC  | Serial Shipping Container Code      |
+| SSL   | Secure Socket Layer                 |
+| TID   | Tag Identifier                      |
+| TLS   | Transport Layer Security            |
+| TMN   | Tag Model Number                    |
+| UII   | Unique Item Identifier              |
+| URI   | Uniform Resource Identifier         |
+| URL   | Uniform Resource Locator            |
+| URN   | Uniform Resource Name               |
+| VIN   | Vehicle Identification Number       |
+| XML   | extensible Markup Language          |
+| XPC   | extended Protocol Control           |
+
+## 5 Conventions
+
+The term ITU-T X.500 system is used to denote an infrastructure consisting of one or more ITU-T X.500 directory service agents (DSAs) and zero or more lightweight directory access protocol (LDAP) servers, where a DSA provides the access point for an accessing client. The term LDAP server is used to denote a system according to [IETF RFC 4510]. A directory system is either an ITU-T X.500 system or a single LDAP server.
+
+NOTE – A DSA is a directory server that follows the specifications in the ITU-T X.500 series of Recommendations [ITU-T X.500-series].
+
+The ITU-T X.500 directory specifications are used to denote the specifications as given by [ITU-T X.500-series].
+
+[ITU-T X.680] notations for character strings, hexadecimal strings and binary strings are used by this Recommendation, i.e., a character string, including a pure numeric string, is surrounded by double quotes (e.g., "string" or "12345"), a hexadecimal string is surrounded by single quotes followed by the letter H (e.g., 'A1'H) and a binary string is surrounded by single quotes followed by the letter B (e.g., '1010 0001'B). A binary number is just given as a figure without quotes.
+
+## 6 Involved standards organizations
+
+### 6.1 GS1 EPCglobal
+
+GS1 is a significant organization in the development of AIDC specifications. GS1, formerly called EAN International, adopted the name GS1 in 2005. It is an international not-for-profit association. There are GS1 member organizations in many countries.
+
+EPCglobal is part of GS1 and leads the development of industry-driven standards for the Electronic Product Code™ (EPC) to support the use of radio frequency identification (RFID).
+
+### 6.2 ISO and ISO/IEC
+
+ISO/IEC JTC 1/SC 31 is the major standards-setting body in AIDC standardization and is responsible for a large number of international standards in the AIDC area.
+
+ISO TC 104 and ISO TC 122 are other committees involved in AIDC standardization.
+
+## 7 AIDC media and associated information
+
+AIDC is a technique where information is stored on some kind of media called an AIDC media. Examples of AIDC media are radio frequency identification (RFID) tags, barcodes, smart cards, etc. NOTE – Only RFID tags are the subject of this Recommendation. However, to prepare for other types of tags, the term AIDC media is used in many places as a synonym for RFID tag.
+
+There are two types of specifications for AIDC media: those as defined by GS1 EPCglobal and others as defined by ISO/IEC or ISO.
+
+An AIDC media is affixed or associated with some item and holds a unique identification of that item (or a unique identification of the type of item).
+
+The AIDC media may contain some information beyond the identifier, but more substantial external information may be associated with an AIDC media. Such information could be:
+
+- description of the item
+- manufacturing information
+- price
+- position of the item, such as postal address, coordinates or other location information
+- customs information.
+
+This information must be available in some information system and accessed based on the identifier of the AIDC media.
+
+There are other standards that cover similar considerations as made by this Recommendation, such as:
+
+- [b-ITU-T F.771] gives some high-level specification for how information retrieved from an AIDC media may be transformed in such a way that multimedia information may be retrieved from some repository.
+- [b-ITU-T H.621] defines a system architecture for multimedia information access. The model defined in this Recommendation can be mapped in the model defined in [b-ITU-T H.621] with the difference that the identification scheme for access can be deducted from the AIDC media information without additional access, as required by [b-ITU-T H.621].
+- [b-ITU-T H.642.1] defines an alternative identification scheme for accessing multimedia information.
+
+## 8 Access to associated information using directory technology
+
+Information associated with an AIDC media may be stored in a directory infrastructure. In some cases, the associated information may be huge, such as a movie, and the directory may then provide the uniform resource locator (URL) for that information.
+
+![Diagram illustrating the AIDC use of directory technology. An AIDC media (represented by a hexagon) is read by an ID terminal (represented by a hexagon with signal waves). The ID terminal is connected to an AIDC client system (represented by a box containing 'DUA or LDAP client'). The AIDC client system is connected to a Directory infrastructure (represented by a yellow oval containing three server icons). The diagram shows a flow from left to right: AIDC media -> ID terminal -> AIDC client system -> Directory infrastructure. A label 'F.511(14)_F01' is present at the bottom right of the diagram.](fa859e4e468bfb2710a94527f2c504af_img.jpg)
+
+Diagram illustrating the AIDC use of directory technology. An AIDC media (represented by a hexagon) is read by an ID terminal (represented by a hexagon with signal waves). The ID terminal is connected to an AIDC client system (represented by a box containing 'DUA or LDAP client'). The AIDC client system is connected to a Directory infrastructure (represented by a yellow oval containing three server icons). The diagram shows a flow from left to right: AIDC media -> ID terminal -> AIDC client system -> Directory infrastructure. A label 'F.511(14)\_F01' is present at the bottom right of the diagram.
+
+**Figure 1 – AIDC use of directory technology**
+
+Figure 1 shows how the identifier on an AIDC media may be used to access a directory infrastructure to retrieve the information associated with the AIDC media. The identifier is read from the AIDC media and forwarded to the directory, typically within a search operation, to retrieve the associated information.
+
+The AIDC client system is some intermediate system that takes the information from the identity (ID) terminal (e.g., a RFID tag reader) and converts that information into a directory request acting either as an LDAP client or as a directory user agent (DUA).
+
+NOTE – DUA is a directory client using the directory access protocol (DAP) according to the specifications in [ITU-T X.500-series].
+
+The AIDC client system could be integrated in the ID terminal or it could be a separate system, e.g., a lap-top computer.
+
+A directory system may be an LDAP system consisting of a single LDAP server or it may be an ITU-T X.500 system defined as an interconnection of one or more DSAs and zero or more LDAP servers.
+
+Appendix II provides an introduction to [ITU-T X.500-series]/LDAP and contains sufficient material to obtain a reasonable understanding of the specification principles established by this Recommendation.
+
+## 9 Unique item identifier (UII) and electronic product code (EPC)
+
+### 9.1 General
+
+An AIDC media that holds an identifier in the EPCglobal environment is called an electronic product code (EPC) and in the ISO environment it is called a unique item identifier (UII).
+
+As stated in the scope clause, only the RFID tag type defined as ISO/IEC 18000-6C or as ISO/IEC 18000-3 Mode 3 is considered by this Recommendation. Appendix III gives an overview of this tag type.
+
+As described in Appendix III, such a tag type has a bit, called the toggle switch that indicates whether the tag contains an EPC or a UII.
+
+EPCs and UIIs have structures that allow them to be globally unique.
+
+An EPC or a UII is a series of characters or bit fields with an implied hierarchical structure. As an example, some fields may denote a manufacturer; some fields may denote a type of product; and another field may be a serial number.
+
+### 9.2 Electronic product code (EPC) types
+
+The different EPC formats are described in Appendix IV.
+
+The first eight bits of an EPC is the header and indicates the EPC type. An escape mechanism is defined that allows multi-octet headers to be defined in the future.
+
+### 9.3 Unique item identifier (UII) types
+
+In the ISO environment many different UII types are defined and others will be further defined in the future. A UII is characterized by having an associated field called the application family identifier (AFI). The AFI field is not part of the actual UII. It is a one-octet field. There is an escape mechanism defined to provide multiple-octet AFIs in the future.
+
+AFIs are allocated to UII types by ISO/IEC JTC 1/SC 31 for items (physical and virtual) not being persons, while ISO/IEC JTC 1/SC 17 is concerned with personal identification.
+
+### 9.4 Global uniqueness of EPCs and UIIs
+
+An EPC, as identified by the toggle switch (see clause 9.1), is globally unique.
+
+Many different ISO or ISO/IEC committees define UII types. Accordingly, there is no guaranty that a particular UII is globally unique in itself. A UII may only be unique within a specific environment or application. Additional information is necessary to ensure global uniqueness. AFI may be read from the ID-tag or otherwise, as available. AFI together with UII provides a globally unique identification within the context of RFID tags. A reference to the specification defining the UII format is another way to achieve uniqueness.
+
+NOTE – Alternatively to using AFI, an object identifier (OID) may be encoded on the RFID tag. Such an OID together with the UII also provides a globally unique identification.
+
+## 10 Locating associated information for centralized AIDC identification applications
+
+This Recommendation identifies two distinct scenarios:
+
+- a) A particular tag-based identification application may be limited, e.g., to a limited geographical area and it may be under a single management entity. All the information associated with the AIDC media is held by a single directory system (which could be a distributed ITU-T X.500 system). In this environment, the use of directory technology becomes rather straight forward as discussed in the remainder of this clause.
+- b) The situation becomes considerably more complicated when a tag-based identification application is highly distributed and several different user groups access the information associated with the AIDC media. An example could be goods produced at different location, packed in containers, transferred by trucks or trains to container docks and then carried by ship to some distant location. Containers are then forwarded by trucks or trains to the final destinations, from where the goods are distributed to different recipients. Several user groups may need to access the information associated with the AIDC media, such as the manufacturers, the different shipping companies, the custom authorities, the recipients of the goods, etc. A suggestion on how to handle this more complex information situation is given in clause 11.
+
+### 10.1 Search using EPC in a centralized environment
+
+![Diagram illustrating the search process using EPC in a centralized environment. An ID terminal reads an RFID tag via AIDC media to obtain an EPC. The EPC is forwarded as a search argument to an ITU-T X.500/LDAP directory server. The server searches a database for an entry with the EPC attribute. The entry may contain epcInUrn, contentUrl, <content>, or tagLocation. The server returns the result to the ID terminal.](ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg)
+
+The diagram shows the flow of information for a search using EPC. On the left, an 'AIDC media' icon (a hexagon with signal waves) and an 'ID terminal' icon (a hexagon) are shown. An arrow labeled 'EPC' points from the ID terminal to a central 'ITU-T X.500/LDAP' server block. Above this arrow, 'Attribute value assertions' and 'Filter: epc' are indicated. The server block has an arrow pointing to a 'Data base' cylinder on the right. Inside the data base, an 'Entry' box contains the following attributes: 'epc', 'epcInUrn', 'contentUrl or <content>', and 'tagLocation'. An arrow points from the data base back to the server, and another arrow points from the server back to the ID terminal. This return arrow is labeled with '<content> | contentUrl' and '(epcInUrn, tagLocation)'. The text 'F.511(14)\_F02' is located at the bottom right of the diagram.
+
+Diagram illustrating the search process using EPC in a centralized environment. An ID terminal reads an RFID tag via AIDC media to obtain an EPC. The EPC is forwarded as a search argument to an ITU-T X.500/LDAP directory server. The server searches a database for an entry with the EPC attribute. The entry may contain epcInUrn, contentUrl, , or tagLocation. The server returns the result to the ID terminal.
+
+**Figure 2 – Search using complete EPC as the search argument**
+
+Figure 2 illustrates the case where an ID terminal reads an ISO/IEC 18000-6C RFID tag (GS1 Class 1 Gen 2 tag type) to obtain EPC. EPC is forwarded as the argument of a directory request. The directory will search the database to locate an entry that holds an attribute of type **epc** with the same value as presented in the argument. This entry may hold either the information associated with the RFID tag or it may hold a URL in an attribute of type **contentUrl** pointing to the location where the associated information might be found. Alternatively, a pointer to another directory location may be provided in the form of a referral, e.g., to another directory server (ITU-T X.500 DSA or LDAP server).
+
+The associated information may take many shapes. The information may be composed of several directory attributes of different types. The directory specifications have defined a large number of different attribute types for general use. New attribute types may be defined as required. This is normal for directories.
+
+If, for some reason, the EPC is wanted in a uniform resource name (URN) format, a ready-made URN could be stored in the located entry and can be returned in an attribute of type **epcInUrn**.
+
+Other information may also be available and provided, such as location information in the form of postal address, shipping company or in the form of coordinates provided in an attribute of type **tagLocation**.
+
+### 10.2 Search using UII together with AFI in a centralized environment
+
+![Diagram illustrating the retrieval of information using AFI and UII values in a centralized environment. An ID terminal reads an RFID tag (AIDC media) to get the AFI and UII. These are forwarded to an ITU-T X.500/LDAP directory system via a filter (tagAfi and uii). The directory system searches a Data base for an Entry containing attributes: tagOid, tagAfi, uii, uiiInUrn, contentUrl or <content>, and tagLocation. The result is returned to the ID terminal as <content> | contentUrl [uiiInUrn, tagOid, tagLocation].](7f25db95ce3916c0e09803b861a2f7bc_img.jpg)
+
+The diagram shows the flow of information retrieval. On the left, an 'AIDC media' (represented by a hexagon) and an 'ID terminal' (represented by a hexagon) are shown with radio waves between them. An arrow labeled 'AFI + UII' points from the ID terminal to a central 'ITU-T X.500/LDAP' box. Above this arrow, 'Attribute value assertions' points to 'Filter: tagAfi and uii'. The 'ITU-T X.500/LDAP' box is connected to a 'Data base' (represented by a cylinder). Inside the 'Data base' is an 'Entry' box containing the following attributes: 'tagOid', 'tagAfi', 'uii', 'uiiInUrn', 'contentUrl or <content>', and 'tagLocation'. An arrow points from the 'ITU-T X.500/LDAP' box back to the ID terminal, labeled with '<content> | contentUrl [uiiInUrn, tagOid, tagLocation]'. The label 'F.511(14)\_F03' is at the bottom right.
+
+Diagram illustrating the retrieval of information using AFI and UII values in a centralized environment. An ID terminal reads an RFID tag (AIDC media) to get the AFI and UII. These are forwarded to an ITU-T X.500/LDAP directory system via a filter (tagAfi and uii). The directory system searches a Data base for an Entry containing attributes: tagOid, tagAfi, uii, uiiInUrn, contentUrl or , and tagLocation. The result is returned to the ID terminal as  | contentUrl [uiiInUrn, tagOid, tagLocation].
+
+**Figure 3 – Retrieval of information using AFI and UII values**
+
+Figure 3 illustrates the case where an ID terminal reads an ISO/IEC 18000-3m3 or ISO/IEC 18000-6C RFID tag to get the AFI and the UII. The tuple (AFI, UII) are forwarded in the filter of a search request. The search will locate the entry that holds those two values in the attributes of type **tagAfi** and **uii**. As discussed clause 8, this entry may hold different types of additional information. As an example, an attribute of type **uiiInUrn** may hold a URN representing the UII.
+
+If an object identifier is defined for the tag type in question, the object identifier may be available in the entry in an attribute of type **tagOid** and may be retrieved if relevant.
+
+NOTE – If an OID has been read from the RFID tag, it may be used instead of the AFI for the directory search.
+
+## 11 Issues for a distributed AIDC environment
+
+There are more complex environments than those described in clause 10. In an environment with many organizations involved, it may not be feasible to hold all information in a single directory system. Several companies and organizations might be interested in the same information held by some common information provider, but companies might still want to hold company specific information in their own systems. As an example, manufacturers will keep details on their products in their own database, which may or may not be an ITU-T X.500/LDAP directory system. Different organizations in the supply chain would need to obtain that information. In some environments, a cascade of directory systems may be applied, as is illustrated in Figure 4.
+
+
+
+## **12 EPC and UII formatting and URN subtree structure**
+
+### **12.1 EPC and UII formatting information**
+
+#### **12.1.1 Formatting information requirements**
+
+Formatting information about EPC or UII is required if:
+
+- EPCs and UIIs are used in a distributed environment, as discussed in clause 11;
+- a higher level of information, such as manufacturer information, is required rather than information about the particular item;
+- there is need to convert the RFID encoded EPC/UII to a printed character representation; and/or
+- there is need to convert the RFID encoded EPC/UII to a globally unique URN.
+
+An AIDC client system may have sufficient built-in knowledge of the different EPC and/or UII formats to make such a conversion. However, this requires the AIDC client system to be loaded with that type of information and they have to be periodically updated to keep-up with new or updated EPC and UII types. Storing formatting information in a directory will simplify AIDC client systems and their maintenance.
+
+This Recommendation considers two types of entries:
+
+- a) entries representing particular EPCs and UIIs. Such entries form URN subtrees as shown in clause 12.2;
+- b) entries that hold formatting information about EPC and UII types. Such entries form URN subtrees as shown in clause 13.
+
+#### **12.1.2 EPC formats**
+
+EPC types are quite complicated when it comes to converting a bit-encoded EPC to either a character-encoded EPC (a GS1 element string) or a URN representation. This is specified in more details in Appendix IV.
+
+All EPC types have the following in common except for a type called general identifier (GID):
+
+- a) An eight-bit header that uniquely identifies the EPC type (the header length may be extended in the future).
+- b) A three-bit filter field indicating some characteristics of item identified by the EPC, such as a retail trade item, a standard trade item grouping, a single shipping/consumer trade item, etc.
+- c) A three-bit partition field giving some partitioning information.
+- d) A company prefix identifying the company associated with the RFID tag.
+
+#### **12.1.3 ISO/IEC 15459 formats**
+
+The ISO/IEC 15459 standard (all parts) specify rules for unique item identification by requiring an issuing agency code (IAC) and company identification number (CIN) to be the first part the actual UII.
+
+NOTE – The data identifier (DI) is not part of the UII.
+
+![Figure 5 shows three diagrams of ISO/IEC 15459 UII formats. Each format is a horizontal bar divided into colored segments. The first format has segments for DI (Data identifier), IAC (Issuing agency code), Company identification number (CIN), and Serial number. The second format adds a Part number segment. The third format adds a Qualifier segment. Arrows point from the labels 'Data identifier' and 'Issuing agency code' to their respective segments in each format. A small code 'F.511(14)_F05' is in the bottom right of the third diagram.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg)
+
+The figure illustrates three variations of the ISO/IEC 15459 UII format. Each format is represented by a horizontal bar divided into colored segments. The first format consists of four segments: DI (Data identifier), IAC (Issuing agency code), Company identification number (CIN), and Serial number. The second format adds a Part number segment between the CIN and Serial number. The third format adds a Qualifier segment between the Part number and Serial number. In all three formats, an arrow labeled 'Data identifier' points to the DI segment, and an arrow labeled 'Issuing agency code' points to the IAC segment. A small code 'F.511(14)\_F05' is present in the bottom right of the third diagram.
+
+Figure 5 shows three diagrams of ISO/IEC 15459 UII formats. Each format is a horizontal bar divided into colored segments. The first format has segments for DI (Data identifier), IAC (Issuing agency code), Company identification number (CIN), and Serial number. The second format adds a Part number segment. The third format adds a Qualifier segment. Arrows point from the labels 'Data identifier' and 'Issuing agency code' to their respective segments in each format. A small code 'F.511(14)\_F05' is in the bottom right of the third diagram.
+
+**Figure 5 – ISO/IEC 15459 UII formats**
+
+Figure 5 illustrates the different formats of UIIs as defined by [ISO/IEC 15459 S]. The fields are described in detail in Appendix VI.
+
+### 12.2 EPC and UII represented by URN directory subtrees
+
+#### 12.2.1 URN directory subtrees
+
+Annex G of [ITU-T X.520] describes how a URN may be represented in a directory, where each URN component is represented by a directory entry. These entries have a superior and subordinate relationship corresponding to the URN structure. As related URNs have the upper level components in common, they may share entries. A set of URNs may in this way be reflected by a directory subtree (More information on directory information trees (DIT) and directory subtrees can be found in Appendix II.)
+
+The **urn:c** attribute type is used for naming of entries representing URNs, i.e., this attribute type is used for the relative distinguished name (RDN) for the entry, where the value is the corresponding URN component.
+
+By using a subtree structure, the information associated with a URN, or possibly a truncated URN, may be obtained by a simple read operation.
+
+NOTE 1 – LDAP does not have a read operation, but it can imitate a read operation using a simplified search operation.
+
+NOTE 2 – A truncated URN is a URN where the last component(s) have been removed allowing reading an entry higher in the URN subtree.
+
+#### 12.2.2 URN subtree for EPCs
+
+![Figure 6 – URN DIT subtree for EPC. The diagram shows a hierarchical tree structure. The root node is 'urnC= "epc"'. Below it is 'urnC= "id"'. The third level consists of seven nodes: 'urnC= "sgtin"', 'urnC= "sscc"', 'urnC= "sgln"', 'urnC= "grai"', 'urnC= "giai"', 'urnC= "gsrn"', and 'urnC= "gdti"'. The fourth level, labeled 'Company prefix level', shows three nodes under 'sgtin', all with 'urnC= "793591651"'. The fifth level, labeled 'Item reference level', shows three nodes under the first company prefix: 'urnC= "9179"', 'urnC= "9180"', and 'urnC= "9181"'. The sixth level, labeled 'Serial number level', shows three nodes under the first item reference: 'urnC= "793591651"', 'urnC= "793591652"', and 'urnC= "793591653"'. Ellipses indicate additional levels and nodes. A label 'F.511(14)_F06' is in the bottom right.](365b54f616aff249b4e6c0edafdcb9b3_img.jpg)
+
+Figure 6 – URN DIT subtree for EPC. The diagram shows a hierarchical tree structure. The root node is 'urnC= "epc"'. Below it is 'urnC= "id"'. The third level consists of seven nodes: 'urnC= "sgtin"', 'urnC= "sscc"', 'urnC= "sgln"', 'urnC= "grai"', 'urnC= "giai"', 'urnC= "gsrn"', and 'urnC= "gdti"'. The fourth level, labeled 'Company prefix level', shows three nodes under 'sgtin', all with 'urnC= "793591651"'. The fifth level, labeled 'Item reference level', shows three nodes under the first company prefix: 'urnC= "9179"', 'urnC= "9180"', and 'urnC= "9181"'. The sixth level, labeled 'Serial number level', shows three nodes under the first item reference: 'urnC= "793591651"', 'urnC= "793591652"', and 'urnC= "793591653"'. Ellipses indicate additional levels and nodes. A label 'F.511(14)\_F06' is in the bottom right.
+
+Figure 6 – URN DIT subtree for EPC
+
+The URN structure for EPC is specified in [b-GS1TAGDAT]. Figure 6 illustrates the structure URN subtree structure for EPCs.
+
+- The root of this subtree is an entry with the RDN value "epc".
+- The second level of the subtree is an entry with the RDN value "id".
+- The third level of the subtree consists of entries each with the RDN value "sgtin", "sscc", "sgln", "grai", "giai", "gsrn" or "gdti", as appropriate (see Appendix IV).
+- The remaining levels of the subtree represent the company prefixes, the item references for each of the company prefix entries, and finally the serial numbers for each of the item reference entries. All these entries have RDNs with appropriate values.
+
+The following is an example of an EPC URN:
+
+"urn:epc:id:sgtin:793591651.2917.ThisIsASerialNumber".
+
+#### 12.2.3 Possible URN DIT subtree for UIIs
+
+The URN structure specified by this Recommendation is primarily intended for directory use, but it could also be a general structure for the URN representation of an UII.
+
+To ensure global uniqueness, it is suggested to use the URN representation as specified in [ITU-T X.520] for URNs for UIIs in accordance with [ISO/IEC 15459 S].
+
+Figure 7 shows a possible URN subtree for an RFID application.
+
+The root of this subtree is an entry with the RDN value "iso" indicating that it is part of the ISO URN name space.
+
+The second level of the subtree is an entry with the RDN value "std" indicating that it the standard subspace that is used.
+
+The third level of the subtree is an entry with the RDN value "iso-iec" indicating that the standard is an ISO/IEC standard.
+
+The fourth level of the subtree is an entry with the RDN value "15459" indicating that we are considering UIIs defined by [ISO/IEC 15459 S].
+
+The fifth level of the example subtree is an entry with the RDN value "25S" identifying the data identifier (see for example clause 12.1.3 and Appendix VI).
+
+![Figure 7: Example of URN DIT subtree for UIIs. The diagram shows a hierarchical tree structure of URN entries. The root is 'urnC="iso"', followed by 'urnC="std"'. The third level branches into 'urnC="iso"', 'urnC="iso-iec"', and 'urnC="iso-ieee"'. The fourth level is 'urnC="15459"'. The fifth level, labeled 'Data identifier level', branches into 'urnC="25B"', 'urnC="25P"', 'urnC="25S"', 'urnC="J"', 'urnC="1J"', 'urnC="2J"', and 'urnC="3J"'. The sixth level, labeled 'Issuing agency code level', branches into 'urnC="J"', 'urnC="KDK"', 'urnC="OD"', 'urnC="SI"', 'urnC="UN"', and 'urnC="VIB"'. The seventh level, labeled 'Company identification number level', branches into 'urnC="123456789"', 'urnC="234567890"', and 'urnC="345678901"'. The eighth level, labeled 'Serial number level', branches into 'urnC="MH803120000001"', 'urnC="MH803120000002"', and 'urnC="MH803120000003"'. Ellipses indicate additional levels and entries. A label 'F.511(14)_F07' is in the bottom right.](366a77fdefb0097b3289b4a011911390_img.jpg)
+
+Figure 7: Example of URN DIT subtree for UIIs. The diagram shows a hierarchical tree structure of URN entries. The root is 'urnC="iso"', followed by 'urnC="std"'. The third level branches into 'urnC="iso"', 'urnC="iso-iec"', and 'urnC="iso-ieee"'. The fourth level is 'urnC="15459"'. The fifth level, labeled 'Data identifier level', branches into 'urnC="25B"', 'urnC="25P"', 'urnC="25S"', 'urnC="J"', 'urnC="1J"', 'urnC="2J"', and 'urnC="3J"'. The sixth level, labeled 'Issuing agency code level', branches into 'urnC="J"', 'urnC="KDK"', 'urnC="OD"', 'urnC="SI"', 'urnC="UN"', and 'urnC="VIB"'. The seventh level, labeled 'Company identification number level', branches into 'urnC="123456789"', 'urnC="234567890"', and 'urnC="345678901"'. The eighth level, labeled 'Serial number level', branches into 'urnC="MH803120000001"', 'urnC="MH803120000002"', and 'urnC="MH803120000003"'. Ellipses indicate additional levels and entries. A label 'F.511(14)\_F07' is in the bottom right.
+
+Figure 7 – Example of URN DIT subtree for UIIs
+
+The sixth level of the example URN subtree is the issuing agency code (IAC) level. The RDN has an IAC value as allocated by the issuing agency.
+
+The next level is the company identification number (CIN). The naming attribute **urnC** takes as value the IAC allocated to the company in question.
+
+The final levels are for the fields following the CIN level. The RDN for each entry takes as value of the field in question as allocated by the company.
+
+An example is shown below in Figure 8.
+
+![Figure 8: URN structure for ISO/IEC 15459 UII. The diagram shows a URN string: 'urn:iso:std:iso-iec:15459:25S.UN.043325711.MH803120000001'. Arrows point from labels to parts of the string: 'Data identifier (DI)' points to '25S', 'Issuing agency code (IAC)' points to 'UN', and 'Company identification number (CIN)' points to '043325711'. A bracket labeled 'Serial/part number' points to 'MH803120000001'. A label 'F.511(14)_F08' is in the bottom right.](19a5f0db57a21a0e82a7f326083e96fd_img.jpg)
+
+Figure 8: URN structure for ISO/IEC 15459 UII. The diagram shows a URN string: 'urn:iso:std:iso-iec:15459:25S.UN.043325711.MH803120000001'. Arrows point from labels to parts of the string: 'Data identifier (DI)' points to '25S', 'Issuing agency code (IAC)' points to 'UN', and 'Company identification number (CIN)' points to '043325711'. A bracket labeled 'Serial/part number' points to 'MH803120000001'. A label 'F.511(14)\_F08' is in the bottom right.
+
+Figure 8 – URN structure for ISO/IEC 15459 UII
+
+An example of a directory distinguished name for such an item could be:
+
+DN = { urnC="iso", urnC="std", urnC="iso-iec", urnC=15459, urnC="25S", urnC="UN",  
+urnC="043325711", urnC="MH80310000001" }
+
+## 13 EPC/UII format information
+
+### 13.1 EPC/UII format DIT subtree
+
+In order to access EPC/UII format information, the format information has to be stored in a directory subtree. The format information for EPC is provided using the same subtree structure as for UIIs. This is illustrated in Figure 9.
+
+NOTE – This does not necessarily mean that both sets of entries are in the same directory system.
+
+![Figure 9: Possible structure of a DIT subtree for holding format information. The diagram shows a hierarchical tree structure starting from a 'Root of directory information tree (DIT)' marked with a yellow star. The tree branches into two main paths. The left path starts with 'urnCobj' urnC='epc', followed by 'urnCobj' urnC='id', then 'urnCobj' urnC='sgtin', 'urnCobj' urnC='sscc', 'urnCobj' urnC='sgln', and so on. The right path starts with 'urnCobj' urnC='iso', followed by 'urnCobj' urnC='std', then 'urnCobj' urnC='iso', 'urnCobj' urnC='iso-iec', 'urnCobj' urnC='iso-ieee', and so on. Both paths lead to a common level of entries including 'urnCobj' urnC='0', 'urnCobj' urnC='1', 'urnCobj' urnC='6', 'urnCobj' urnC='15459', 'urnCobj' urnC='25B', 'urnCobj' urnC='25P', 'urnCobj' urnC='25S', 'urnCobj' urnC='J', 'urnCobj' urnC='1J', 'urnCobj' urnC='2J', 'urnCobj' urnC='3J', and so on. The final level shown includes 'urnCobj' urnC='J', 'urnCobj' urnC='KDK', 'urnCobj' urnC='OD', 'urnCobj' urnC='SI', 'urnCobj' urnC='UN', 'urnCobj' urnC='VIB', and so on. The diagram is labeled F.511(14)_F09.](e354b57563dae469c00b412b2abdf765_img.jpg)
+
+Root of directory information tree (DIT)
+
+"urnCobj" urnC="epc"
+
+"urnCobj" urnC="iso"
+
+"urnCobj" urnC="id"
+
+"urnCobj" urnC="std"
+
+"urnCobj" urnC="sgtin" "urnCobj" urnC="sscc" "urnCobj" urnC="sgln" . . .
+
+"urnCobj" urnC="iso" "urnCobj" urnC="iso-iec" "urnCobj" urnC="iso-ieee"
+
+"urnCobj" urnC="0" "urnCobj" urnC="1" . . . "urnCobj" urnC="6"
+
+"urnCobj" urnC="15459"
+
+"urnCobj" urnC="25B" "urnCobj" urnC="25P" "urnCobj" urnC="25S" "urnCobj" urnC="J" "urnCobj" urnC="1J" "urnCobj" urnC="2J" "urnCobj" urnC="3J" . . .
+
+. . . "urnCobj" urnC="J" "urnCobj" urnC="KDK" "urnCobj" urnC="OD" "urnCobj" urnC="SI" "urnCobj" urnC="UN" "urnCobj" urnC="VIB" . . .
+
+F.511(14)\_F09
+
+Figure 9: Possible structure of a DIT subtree for holding format information. The diagram shows a hierarchical tree structure starting from a 'Root of directory information tree (DIT)' marked with a yellow star. The tree branches into two main paths. The left path starts with 'urnCobj' urnC='epc', followed by 'urnCobj' urnC='id', then 'urnCobj' urnC='sgtin', 'urnCobj' urnC='sscc', 'urnCobj' urnC='sgln', and so on. The right path starts with 'urnCobj' urnC='iso', followed by 'urnCobj' urnC='std', then 'urnCobj' urnC='iso', 'urnCobj' urnC='iso-iec', 'urnCobj' urnC='iso-ieee', and so on. Both paths lead to a common level of entries including 'urnCobj' urnC='0', 'urnCobj' urnC='1', 'urnCobj' urnC='6', 'urnCobj' urnC='15459', 'urnCobj' urnC='25B', 'urnCobj' urnC='25P', 'urnCobj' urnC='25S', 'urnCobj' urnC='J', 'urnCobj' urnC='1J', 'urnCobj' urnC='2J', 'urnCobj' urnC='3J', and so on. The final level shown includes 'urnCobj' urnC='J', 'urnCobj' urnC='KDK', 'urnCobj' urnC='OD', 'urnCobj' urnC='SI', 'urnCobj' urnC='UN', 'urnCobj' urnC='VIB', and so on. The diagram is labeled F.511(14)\_F09.
+
+Figure 9 – Possible structure of a DIT subtree for holding format information
+
+### 13.2 EPC format information
+
+#### 13.2.1 Storing and accessing EPC format information
+
+The EPC format information may then be identified by the following URN:
+
+"urn:spc:id:<header>.<partition>"
+
+where the <header> is the EPC header.
+
+For a given combination of EPC header and partition value the length of the company prefix is fixed. The complete format information may be obtained by a single access and returned in an attribute of type **epcFormat**. The **epcFormat** attribute type is defined in [ITU-T X.520] and for easy reference is described in Appendix VIII.
+
+There are eleven different EPC types each with seven different partition values. Seventy-seven directory entries will be required for holding all the EPC format information.
+
+### 13.3 UII format information
+
+While it is possible for an EPC to obtain all the necessary format information using a single access, it becomes more complex for UIIs due to the greater diversity and the many organizations involved. The complete format of an UII is not necessarily determined by a single committee or organization.
+
+It is quite straightforward to isolate the DI and the IAC fields of UII if the encoding is known:
+
+– For AFI values 'A1'H to 'AA'H, as allocated to [ISO/IEC 15459 S], a six-bit encoding is used.
+
+The part of the URN for the UII up to and including the IAC is as follows:
+
+"urn:iso:std:iso-iec:15459:<di>.<iac>"
+
+The length of CIN (or its equivalent) is determined by the IAC. However, it cannot be assumed that the length of CIN is fixed for a particular IAC. As an example, the Universal Postal Union (UPU) specifies the CIN field (called the issuer code) to be either two or three characters long.
+
+![Diagram illustrating the retrieval of EPC format information. On the left, a vertical stack of three 'uiiFormat' boxes is shown, each with three dots above it. Below these is a horizontal line with three green boxes. Arrows point from each 'uiiFormat' box and the third green box to a vertical orange bar on the right labeled 'UII'. Each arrow is labeled 'Entry for UII field'. The label 'F.511(14)_F10' is at the bottom right.](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg)
+
+Diagram illustrating the retrieval of EPC format information. On the left, a vertical stack of three 'uiiFormat' boxes is shown, each with three dots above it. Below these is a horizontal line with three green boxes. Arrows point from each 'uiiFormat' box and the third green box to a vertical orange bar on the right labeled 'UII'. Each arrow is labeled 'Entry for UII field'. The label 'F.511(14)\_F10' is at the bottom right.
+
+**Figure 10 – Retrieving EPC format information**
+
+To cope with this situation, a result of a search operation may be an attribute of type **uiiFormat** returned to the AIDC client system to give a recommendation on how a subsequent search should be performed. The **uiiFormat** attribute type is described in Appendix VIII.
+
+It may not always be possible, or necessary, to get the complete format information. By knowing the DI, IAC and CIN values, the company is identified and it may be possible to obtain a reference, e.g., a URL, to the site of the company, where a complete search may be performed. Alternatively, additional formatting information may be returned in order to navigate to the wanted information.
+
+To ease the following more detailed description, the variable **UIIpointer** is introduced.
+
+- 1) The first access by the AIDC client system is a search using the distinguished name corresponding to "urn: iso:std:iso-iec:15459:<di>.<iac>" as the **baseObject**, a **scope** equal to **baseObject** and an empty filter (an emulated read). The **UIIpointer** is set to the first character after the IAC in the UII. Two cases are considered depending on the returned result:
+  - a) If the result is an attribute of type **uiiFormat**, a search is performed following the recommendation given in that attribute. The characters to be used in the filter are taken from the UII starting from the **UIIpointer**.
+  - b) If the issuing agency has its own site, the result in addition to an attribute of type **uiiFormat** could include an attribute of type **ldapURL** pointing to that site. A search is performed using the recommendations in the attribute of type **uiiFormat** against this new site. The characters to be used in the filter are taken from the UII starting from the **UIIpointer**.
+- 2) The result from the latest search may return zero or more entries. Zero entries are returned in the case of an error situation where it not possible to resolve the UII. When entries are returned, the distinguished names are returned together with the entries. Such a distinguished
+
+name minus the last component is the distinguished name of the base object for the performed search. The last component of the distinguished name is the relative distinguished name (RDN) for the entry. The RDN is actually formed by the same attribute that was the target for the search filter (the naming attribute). The RDN can also be used to construct the next component of the corresponding URN for the entry.
+
+If only a single entry is returned and this attribute holds a single value, the next URN component is finally resolved and the **UIIpointer** is updated with the number of characters in that component.
+
+If only a single entry is returned, but the naming attributes holds multiple values, it is checked what values the search filter matched. The longest one of these values determines the number to be added to the **UIIpointer**.
+
+Four cases are considered depending on the returned result from 1) above:
+
+- a) If the result is a complete result, the process is complete. This would be the case if the attribute of type **uiiFormat** in the previous search specified that the complete UII to be specified in the filter or if the UII has been completely resolved into components (the updated **UIIpointer** points to the end of transmission (EOT)).
+  - b) If the result is an attribute of type **uiiFormat**, a search is performed according to the value of that attribute.
+  - c) If the result is both an attribute of type **ldapURL** and an attribute of type **uiiFormat**, the search filter is constructed as in b), above, and the search is performed against the site identified by the **ldapURL**.
+- 3) Step 2) is repeated until a final result is returned.
+
+## 14 Support of ITU-T Y.2213
+
+[ITU-T Y.2213] specifies different levels of support:
+
+- a) Forward identifier resolution, which means resolving the identifier into associated information.
+- b) Reverse identifier resolution, which means resolving the associated information into the corresponding identifier.
+- c) One-to-many associations between an identifier and information of different types vs one-to-one association. One-to-many associations allow users to access association information depending on the type of user. Manufacturers, retailers or consumers may access different types of associated information based on the same identifier.
+
+Next-generation networks (NGNs) require protection against a single point of failure.
+
+### 14.1 General
+
+In the simple case, there is a one-to-one relationship between a tag and its associated information, but there are more complicated cases as outlined in [ITU-T Y.2213].
+
+Different users may want to access different information for the same tag information. For example, manufacturers may use identifiers for production planning while retailers may use the same identifiers for store inventory management, and consumers may use the same identifiers for product information retrieval.
+
+Some users may be interested in information about a particular item; others may be interested type information, while others again may want information about the organization that produced the item.
+
+[ITU-T Y.2213] identifies the requirement to retrieve tag information based on the information associated with the tag (reverse identifier resolution).
+
+[ITU-T Y.2213] also identifies a requirement for having location information as part of the information associated with a tag.
+
+### 14.2 Multiple user groups for same EPC or UII
+
+Different user groups may require different associated information even for the same EPC or UII. There are different ways this may be achieved:
+
+- Use of access control: Different contents may be held by different attributes. By use of access control, a particular user group will only get access to information relevant for that user group. Likewise, if the returned information is a URL to the content, different URLs may be held by the same attribute. By use of access control down to value level, only the relevant URL will be returned.
+
+NOTE – LDAP does not have access control specifications, although many LDAP implementations have proprietary access control.
+
+- It is possible in a directory request to specify what attributes are to be returned. Different user groups may specify different attributes to be returned.
+- Different user groups may access different directory systems. This will require that some information be duplicated among these systems.
+
+### 14.3 Reverse identifier resolution
+
+Clause 7.2 of [ITU-T Y.2213] specifies a requirement for reverse resolution i.e., finding the identifier of an object and its location from the associated information. Reverse identification only makes sense if the associated information is only relevant for a single identifier.
+
+If the directory provides the associated information, the entry holding that information may also hold attributes describing the tag information
+
+### 14.4 Location-based information
+
+Clause 7.6 of [ITU-T Y.2213] specifies the requirements for location-based service support.
+
+The location of a tag may be provided in an attribute of type `tagLocation`.
+
+### 14.5 Avoidance of single-point-of-failure
+
+Avoiding single-point-of-failure has many aspects outside the scope of these directory specifications, such as:
+
+- duplication of networks following different physical routes
+- use of redundant arrays of inexpensive disks (RAID) technology
+- back-up of databases.
+
+All these techniques are well established, known and deployed by responsible organizations as needed.
+
+Replication is another way to prevent single point of failure. [ITU-T X.525] defines protocols and procedures for replication of information. LDAP does not include a specification for replication, but many LDAP implementation have proprietary replication solutions.
+
+# Appendix I
+
+## Use of OIDs in an RFID environment
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## I.1 Introduction
+
+[ISO/IEC 15459 S] and [ISO/IEC 15961-1] introduces the possibility to add OIDs to RFID tags and thereby provide an additional technique to create unique identities. Although this possibility exists there is no requirement that OIDs are actually encoded on the RFID tags.
+
+This appendix gives an overview of the RFID OID structure.
+
+## I.2 OID used in the ISO environment
+
+As indicated, AFIs are allocated from a flat name space requiring a single authority for the allocation of values for different purposes. OIDs were invented to circumvent this problem. Here the allocation of values may be delegated. Delegation may go down to specific standards activities. An OID together with an ISO UII provides a global unique identification.
+
+![Figure I.1 – ISO/RFID object identifier structure. A hierarchical tree diagram showing the structure of OIDs. The root node is labeled 'Root'. It branches into three main paths: 'itu-t(0)', 'iso(1)', and 'joined-iso-itu-t(2)'. The 'iso(1)' path leads to 'standard(0)', which then branches into '10891', 'iso15459(15459) supply chain', and 'rfid-data-protocol(15961)'. The 'iso15459(15459) supply chain' path further branches into 'transport unit', 'product packaging', and 'returnable transportation'. The 'rfid-data-protocol(15961)' path branches into 'xxx(8)', 'ean-ucc(9)', 'di(10)', 'upu(11)', and 'iata(12)'. The 'joined-iso-itu-t(2)' path leads to 'tag-based(27)', which then branches into '(0) ... (n)'.](f2ea0f64a770b22b902820457d262265_img.jpg)
+
+```
+graph TD; Root((Root)) --- itu-t(0); Root --- iso(1); Root --- joined-iso-itu-t(2); iso(1) --- standard(0); standard(0) --- 10891; standard(0) --- iso15459(15459)[iso15459(15459) supply chain]; standard(0) --- rfid-data-protocol(15961); iso15459(15459) --- transport_unit[transport unit]; iso15459(15459) --- product_packaging[product packaging]; iso15459(15459) --- returnable_transportation[returnable transportation]; rfid-data-protocol(15961) --- xxx(8); rfid-data-protocol(15961) --- ean-ucc(9); rfid-data-protocol(15961) --- di(10); rfid-data-protocol(15961) --- upu(11); rfid-data-protocol(15961) --- iata(12); joined-iso-itu-t(2) --- tag-based(27); tag-based(27) --- zero_to_n["(0) ... (n)"];
+```
+
+F.511(14)\_Fl.1
+
+Figure I.1 – ISO/RFID object identifier structure. A hierarchical tree diagram showing the structure of OIDs. The root node is labeled 'Root'. It branches into three main paths: 'itu-t(0)', 'iso(1)', and 'joined-iso-itu-t(2)'. The 'iso(1)' path leads to 'standard(0)', which then branches into '10891', 'iso15459(15459) supply chain', and 'rfid-data-protocol(15961)'. The 'iso15459(15459) supply chain' path further branches into 'transport unit', 'product packaging', and 'returnable transportation'. The 'rfid-data-protocol(15961)' path branches into 'xxx(8)', 'ean-ucc(9)', 'di(10)', 'upu(11)', and 'iata(12)'. The 'joined-iso-itu-t(2)' path leads to 'tag-based(27)', which then branches into '(0) ... (n)'.
+
+**Figure I.1 – ISO/RFID object identifier structure**
+
+Figure I.1 shows examples of OID assignments. OIDs, or at least the upper level arcs, are allocated by International Standards and/or ITU-T Recommendations.
+
+[b-ISO/TS 10891] defines OID RFIDs for freight containers.
+
+[ISO/IEC 15459 S] define the following OIDs:
+
+- {1 0 15459 1} is an OID for transport units.
+- {1 0 15459 4} is an OID for product tagging.
+- {1 0 15459 5} is an OID for returnable transportation.
+
+[ISO/IEC 15961] defines the following OIDs:
+
+- {1 0 15961 8} is an OID for the data format used for libraries according to ISO/IEC 28560-2 "Information and documentation – RFID in libraries – Part 2: Encoding based on ISO/IEC 15962".
+
+- {1 0 15961 9} is an OID for data format used when all the data on the RFID tag complies with GS1 as referred to in ISO/IEC 15418 "Information technology – Automatic identification and data capture techniques – GS1 Application Identifiers and ASC MH 10 Data Identifiers and maintenance".
+- {1 0 15961 10} is an OID for data format used when all the data on the RFID tag complies with the Data Identifier standard (as referred to in [b-ISO/IEC 15418]).
+- {1 0 15961 11} is an OID for the Universal Postal Union.
+- {1 0 15961 12} is an OID for International Air Transport Association (IATA). IATA may further define sub-arcs for specific purposes. As an example, sub-arc 1 is used for IATA baggage identification code.
+
+[b-ITU-T X.668] specifies an OID structure for possible use by tag-based applications. It defines a structure requiring only three arcs to save storage on RFID tags. New RFID applications may choose to apply for an arc within this structure. Current applications may choose to convert to this OID structure.
+
+## I.3 ISO/IEC 15459 OID structure vs. data identifiers/application identifiers
+
+![A hierarchical tree diagram showing the ISO/IEC 15459 OID structure. The root is 'iso(1) standard(0) iso15459(15459) supply chain'. It branches into three main paths: 1. 'transport unit' which further branches into GS1 AI 00, MH10 DI J, MH10 DI 1J, MH10 DI 2J, MH10 DI 3J, MH10 DI 4J, MH10 DI 5J, and MH10 DI 6J. 2. 'product packaging' which branches into GS1 AI 8004, GS1 AI 01 + 21, MH10 DI 25S or 3I, MH10 DI 25P + S, and No mapping. 3. 'returnable transportation' which branches into GS1 AI 8003 and MH10 DI 25B. A label 'F.511(14)_FI.2' is at the bottom right.](dd5771673aececa53d42ece89218299d_img.jpg)
+
+```
+
+graph TD
+    Root["iso(1) standard(0) iso15459(15459)  
+supply chain"]
+    Root -- 1 --> TU["transport unit"]
+    Root -- 4 --> PP["product packaging"]
+    Root -- 5 --> RT["returnable transportation"]
+    
+    TU -- 1 --> TU1["GS1 AI  
+00"]
+    TU -- 2 --> TU2["MH10  
+DI J"]
+    TU -- 3 --> TU3["MH10  
+DI 1J"]
+    TU -- 4 --> TU4["MH10  
+DI 2J"]
+    TU -- 5 --> TU5["MH10  
+DI 3J"]
+    TU -- 6 --> TU6["MH10  
+DI 4J"]
+    TU -- 7 --> TU7["MH10  
+DI 5J"]
+    TU -- 8 --> TU8["MH10  
+DI 6J"]
+    
+    PP -- 2 --> PP2["GS1 AI  
+8004"]
+    PP -- 3 --> PP3["GS1 AI  
+01 + 21"]
+    PP -- 4 --> PP4["MH10  
+DI 25S or 3I"]
+    PP -- 6 --> PP6["MH10  
+DI 25P + S"]
+    PP -- 7 --> PP7["No  
+mapping"]
+    
+    RT -- 1 --> RT1["GS1 AI  
+8003"]
+    RT -- 3 --> RT3["MH10  
+DI 25B"]
+    
+    F511["F.511(14)_FI.2"]
+  
+```
+
+A hierarchical tree diagram showing the ISO/IEC 15459 OID structure. The root is 'iso(1) standard(0) iso15459(15459) supply chain'. It branches into three main paths: 1. 'transport unit' which further branches into GS1 AI 00, MH10 DI J, MH10 DI 1J, MH10 DI 2J, MH10 DI 3J, MH10 DI 4J, MH10 DI 5J, and MH10 DI 6J. 2. 'product packaging' which branches into GS1 AI 8004, GS1 AI 01 + 21, MH10 DI 25S or 3I, MH10 DI 25P + S, and No mapping. 3. 'returnable transportation' which branches into GS1 AI 8003 and MH10 DI 25B. A label 'F.511(14)\_FI.2' is at the bottom right.
+
+Figure I.2 – ISO/IEC 15459 OID structure with DI and AI indications
+
+Figure I.2 shows how the OID branch for [ISO/IEC 15459] parts is further branching out for different purposes.
+
+For [ISO/IEC 15459 S], an OID is defined for each data identifier (DI) and for each GS1 application identifier (AI).
+
+# Appendix II
+
+## Introduction to ITU-T X.500-series/LDAP concepts
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### II.1 Directory entries and their content
+
+A directory system holds the information in so-called entries. An entry holds information about a particular physical or logical object. Within this Recommendation an object may be the item to which an AIDC media is affixed or it may be a single field within an EPC or UII.
+
+The information in entries is held by so-called directory attributes (or just attributes). An attribute is of a defined type, where the type is indicated by an OID and the value syntax is part of the attribute type specification.
+
+In addition to an OID, an attribute type has a textual identifier that is a representation of the OID. This textual identifier is used in this Recommendation when referring to a particular attribute type.
+
+Directory systems are open ended systems that can be adapted to handle diverse information types. Neither [ITU-T X.500-series] nor [IETF RFC 4511] (LDAP) need any extension to support new types of information, except for the definition of some new attribute types for holding these types of information. No extensions to the basic protocols are needed.
+
+A directory is built to store and provide many types of information, such postal address, other location information, shipping information, etc. Both [ITU-T X.500-series] and [IETF RFC 4511] (LDAP) define general useable attribute types to be used by any application. Attribute information is returned as required.
+
+The required number of interactions with the directory infrastructure is quite limited and in some cases a single interaction is sufficient.
+
+Directory systems have well-proven security functions allowing, for example, strong authentication of accessing clients, protection of information, etc.
+
+### II.2 Directory information tree (DIT)
+
+The directory information within a directory system is conceptually stored in a DIT where the individual vertices are directory entries. The DIT reflects the hierarchical nature of things. As an example, a country is divided into localities and large organizations. Locations may again be subdivided into smaller localities down to smaller companies and private persons. A large organization may be divided into organizational units possibly in several levels down to the individuals.
+
+EPCs and UIIs have also hierarchical structures and the EPC/UII fields may therefore be represented by directory entries.
+
+### II.3 Directory subtrees
+
+A directory subtree is a set of entries which themselves constitute a tree structure, but where the subtree root typically is different from the root of the DIT and the leaves of the subtree may not coincide with leaves of the DIT.
+
+### II.4 Distinguished names and URNs
+
+[ITU-T X.500-series] and [IETF RFC 4511] (LDAP) both have the concept of distinguished name. A distinguished name reflects the hierarchical nature of objects. Entries in the DIT reflect the hierarchical structure of the objects they represent. A distinguished name is comprised of a number of components. Each level of the DIT adds a new component to a distinguished name. This component for an entry is called the relative distinguished name (RDN) for the entry. The distinguished name for an entry is therefore the sequence of RDNs from the DIT root down to and including the entry in question.
+
+An RDN is an {attribute type, attribute value} pair, i.e., that one of the values of an attribute is used for the RDN for an entry.
+
+NOTE – An RDN may actually consist of multiple {attribute type, attribute value} pairs; however, this is not relevant for this Recommendation.
+
+URNs also have a hierarchical structure, which means that it is rather straight forward to map a URN onto a corresponding distinguished name. This is detailed in Annex G of [ITU-T X.520].
+
+### II.5 Directory search operation
+
+#### II.5.1 Search filter
+
+Directory systems have extensive search capabilities allowing several search criteria to be expressed in a single filter used for interrogating the directory database. Each entry within the scope (see clause II.5.3) is checked against the filter. This filter is composed of filter items, where each filter item is an assertion about, and an attribute of, a specific type. If that assertion is proved satisfied, the filter item yields TRUE. Filter item may combined to an arbitrary complex filter using a recursive definition and by using the logical operators **and**, **or** and **not**. An entry is returned to the requester if the combined filter yields TRUE using the normal rules for Boolean algebra.
+
+Filter items take many forms; however, in this Recommendation it is only necessary to consider attribute value assertions. An attribute assertion is a slightly modified form of an attribute. Only equality assertions are relevant.
+
+#### II.5.2 Search base object
+
+To avoid searching the whole DIT for every search operation, it is required to specify the distinguished name of an entry from where the search operation is to start. The distinguished name may be empty signalling that the search operation shall start at the DIT root.
+
+#### II.5.3 Search scope
+
+The search scope specifies the range of the search operation. It takes one of the following values:
+
+- **baseObject**, meaning that only the base object is to be search for match. By specifying an empty filter, this corresponds to a read operation. This is how LDAP emulates a read operation.
+- **oneLevel**, meaning that only the entries immediately subordinate to the base object are to be searched.
+- **wholeSubtree**, meaning that the base object and all its subordinate entries are to be searched.
+
+### **II.6 Entry information selection**
+
+By default, when a directory entry has been selected for return to the AIDC client system, all information available in that entry will be returned (subject to access control restrictions). However, when issuing an interrogation request, it is possible to specify what attribute types are to be returned. Therefore it is possible to limit the returned result to what the AIDC client system intends to process.
+
+### **II.7 Pointers to other directories (referrals)**
+
+Both [ITU-T X.500-series] and [IETF RFC 4511] (LDAP) have the concept of referrals, which is a way for a directory server to signal that other directory servers are able to further progress a request. This will also include information about how to access that directory server.
+
+An LDAP referral is a URL where the scheme (the first part of a URL) is "ldap".
+
+# Appendix III
+
+## Introduction to RFID tag structure
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## III.1 Scope of appendix
+
+The purpose of this appendix is to give a short tutorial on the structure of RFID tags and to isolate those information types that are of interest from the point of view of directory support.
+
+## III.2 ISO/IEC 18000-6C and ISO/IEC 18000-3m3 RFID tag structure
+
+![Diagram of ISO/IEC 18000-6C and ISO/IEC 18000-3m3 memory structure showing four banks: '11'B [User], '10'B TID, '01'B UII/EPC, and '00'B Reserved. The '11'B bank contains RFU and DSFID. The '10'B bank contains TID. The '01'B bank contains Extended protocol control, UII/EPC, Protocol control, and CRC-16. The '00'B bank contains Access password and Kill password. A legend defines UII as Unique item identifier and EPC as Electronic product code. A note indicates that [ ] denotes optional fields.](a1890b9a9b85f13e67ed59bbad623659_img.jpg)
+
+Memory banks
+
+|       |          |                                                                      |
+|-------|----------|----------------------------------------------------------------------|
+| '11'B | [User]   | ⋮<br>RFU<br>DSFID                                                    |
+| '10'B | TID      | ⋮<br>TID<br>TID                                                      |
+| '01'B | UII/EPC  | [Extended protocol control]<br>UII/EPC<br>Protocol control<br>CRC-16 |
+| '00'B | Reserved | ⋮<br>Access password<br>Kill password                                |
+
+[ ] = Optional
+
+UII = Unique item identifier  
+EPC = Electronic product code
+
+F.511(14)\_FIII.1
+
+Diagram of ISO/IEC 18000-6C and ISO/IEC 18000-3m3 memory structure showing four banks: '11'B [User], '10'B TID, '01'B UII/EPC, and '00'B Reserved. The '11'B bank contains RFU and DSFID. The '10'B bank contains TID. The '01'B bank contains Extended protocol control, UII/EPC, Protocol control, and CRC-16. The '00'B bank contains Access password and Kill password. A legend defines UII as Unique item identifier and EPC as Electronic product code. A note indicates that [ ] denotes optional fields.
+
+Figure III.1 – ISO/IEC 18000-6C and ISO/IEC 18000-3m3, memory structure
+
+The following RFID tag types are considered:
+
+- The ISO/IEC 18000-6C tag type as defined in [ISO/IEC 18000-6]. This tag type is identical to the GS1 Class 1 Gen 2 tag type.
+- The ISO/IEC 18000-3 Mode 3 tag type as defined in [ISO/IEC 18000-3].
+
+The two tag types have the same memory structure, but uses different frequency ranges on the air interface. The tag structure is shown in Figure III.1.
+
+The tag memory is logically separated into four distinct banks as shown in Figure III.1 and is discussed in the following clauses.
+
+### III.3 Bank '00'B (reserved memory)
+
+The reserved memory contains the kill and/or access passwords, if passwords are implemented on the tag. The kill password protects against setting the tag out of function or reusing the tag for some new purpose (recommission). The access password controls read and write access to the tag.
+
+### III.4 Bank '01'B (UII/EPC memory)
+
+![Diagram of Memory bank '01'B (UII/EPC memory) showing fields: Cyclic redundancy check (16 bits), Length (5 bits), Protocol control, Length in words (of 16 bits), AFI (ISO), Attribute (EPC) (8 bits), UII/EPC, Zero fill to word boundary, Extended protocol control (XPC), and Hazardous material (EPC).](85e2327652d513a7fee8fdbf97ad06f1_img.jpg)
+
+The diagram illustrates the structure of Memory bank '01'B. It begins with a 16-bit Cyclic redundancy check (CRC) field, followed by a 5-bit Length field. The Protocol control section follows, which includes a 1-bit User memory indicator, a 1-bit XPC indicator, and a 1-bit Toggle bit (0 = EPC/1 = ISO). The remaining 3 bits of the Protocol control are part of the AFI (ISO) or Attribute (EPC) (8 bits) subfield. The Length in words (of 16 bits) field indicates the length of the UII/EPC field. The UII/EPC field contains an electronic product code (EPC) if the toggle bit is 0, or a unique item identifier (UII) if the toggle bit is 1. A 1-bit Hazardous material (EPC) indicator is also present. The Zero fill to word boundary field ensures the UII/EPC field is aligned to a 16-bit word boundary. Finally, the Extended protocol control (XPC) field is present if the XPC indicator is set.
+
+Diagram of Memory bank '01'B (UII/EPC memory) showing fields: Cyclic redundancy check (16 bits), Length (5 bits), Protocol control, Length in words (of 16 bits), AFI (ISO), Attribute (EPC) (8 bits), UII/EPC, Zero fill to word boundary, Extended protocol control (XPC), and Hazardous material (EPC).
+
+Figure III.2 – Memory bank '01'B (UII/EPC memory)
+
+The UII memory bank is illustrated in Figure III.2 and it has the following fields:
+
+- The cyclic redundancy check field, which protects the protocol control and the UII/EPC fields.
+- The protocol control field with the following content:
+  - The length field holds the length of the UII/EPC field in 16 bits words.
+  - The user memory indicator indicates whether there is any information in the user memory bank. If the bit is set, the user memory bank is present and formatted with information. Otherwise, the indicator is not set.
+  - The extended protocol control (XPC) indicator is set if the extended protocol control field is present and not all-zero.
+  - Toggle bit with a value zero indicates that the tag is formatted according to the GS1 specifications. A value one indicates that the tag is formatted according to ISO/IEC or ISO specifications.
+  - If the toggle bit is one, the AFI/attribute subfield holds an AFI (see clause 10.2). If the toggle bit is zero, the AFI/attribute subfield holds an 8 bit attribute (do not confuse with directory attributes). Only the least significant bit is defined. If that bit is set to '1'B, it indicates that the tag is affixed hazardous material.
+- The UII/EPC field holds an electronic product code (EPC) if the toggle bit is set to '0'B and a unique item identifier (UII) if the toggle bit is set to '1'B.
+- The Extended Protocol Control field is present if the tag supports recommissioning or supports sensors and batteries.
+
+### III.5 Bank '10'B (TID memory)
+
+![Diagram of Memory bank '10'B (TID memory) showing fields: Allocation class 'E2'H (8 bits), MDID (12 bits), Tag model number (TMN) (12 bits), and Extented information (22 octets).](a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg)
+
+The diagram illustrates the structure of Memory bank '10'B (TID memory). It consists of four main fields: Allocation class 'E2'H (8 bits), MDID (12 bits), Tag model number (TMN) (12 bits), and Extented information (22 octets). A legend indicates that a value of 0 in the Allocation class field signifies a non-extended TID, while a value of 1 signifies an extended TID.
+
+Diagram of Memory bank '10'B (TID memory) showing fields: Allocation class 'E2'H (8 bits), MDID (12 bits), Tag model number (TMN) (12 bits), and Extented information (22 octets).
+
+Figure III.3 – Memory bank '10'B (TID memory)
+
+The unique tag identifier (TID) occupies Bank '10' as illustrated in Figure III.3.
+
+The TID provides tag manufacturer information, i.e., it provides information about the tag itself, as opposed to the item to which the tag is affixed.
+
+There are different formats for the TID, e.g., for different types of tags. The TID format to be used for tags according to ISO/IEC 18000-6C and ISO/IEC 18000-3m3 is shown in Figure III.3. The structure of this tag is defined in [b-ISO/IEC 15963].
+
+The first 8 bits of the TID is the allocation class indicating the type of TID. An allocation class for an ISO/IEC 18000-6C and ISO/IEC 18000-3m3 tag is 'E2'H ('1110 0010'B).
+
+The mask-designer identification code (MDID) field holds a code identifying the manufacture of the tag, while the tag model number (TMN) indicates a tag from that manufacture with particular characteristics.
+
+An extended TID holds additional information within the extension (see [b-ISO/IEC 15963]) including a serial number. [b-GSITAGDATA] specifies that for a particular MDID/TMN combination, all tags with that combination shall have identical values in the extension, except for the serial number.
+
+A TID may be held in a directory by an attribute of type **tagTID**, as defined in [ITU-T X.520].
+
+When loading information about a tag into a directory, the TID could also be included. When reading a tag and finding that the TID on the tag is different from the one in the directory, it can be concluded that the item to which the tag is affixed is a counterfeit item.
+
+### III.6 Bank '11'B (user memory)
+
+![Diagram of Memory bank '11'B (user memory) structure. The diagram shows a horizontal bar representing the memory bank. The first octet is labeled 'DSFID ISO/IEC 15961'. Above the bar, a double-headed arrow labeled 'DSFID ISO/IEC 15961' spans the first octet, and another double-headed arrow labeled 'ISO/IEC 15962' spans the remaining part. Below the bar, the first octet is divided into four nibbles. The first nibble is labeled 'Access-method', the second is 'Reserved', and the third and fourth are collectively labeled 'Data-format'. The remaining part of the bar is labeled 'Formatted data'. A small label 'F.511(14)_FIII.4' is at the bottom right of the bar.](c85b57b2414f341860dfc338e1cf2509_img.jpg)
+
+Diagram of Memory bank '11'B (user memory) structure. The diagram shows a horizontal bar representing the memory bank. The first octet is labeled 'DSFID ISO/IEC 15961'. Above the bar, a double-headed arrow labeled 'DSFID ISO/IEC 15961' spans the first octet, and another double-headed arrow labeled 'ISO/IEC 15962' spans the remaining part. Below the bar, the first octet is divided into four nibbles. The first nibble is labeled 'Access-method', the second is 'Reserved', and the third and fourth are collectively labeled 'Data-format'. The remaining part of the bar is labeled 'Formatted data'. A small label 'F.511(14)\_FIII.4' is at the bottom right of the bar.
+
+**Figure III.4 – Memory bank '11'B (user memory)**
+
+User memory is optional.
+
+The first octet is the data storage format identifier (DSFID), while the remaining part of the memory bank holds formatted data.
+
+The first two bits of DSFID indicate the access-method, i.e., how the formatted information is accessed:
+
+- 0: No-Directory
+- 1: Directory
+- 2: Packed-Objects
+- 3: Tag-Data-Profile
+
+The next bit is reserved.
+
+The remaining five bits are used for specifying the Data-format:
+
+- 0: Not formatted
+- 1: Data elements identified by full OIDs
+- 2: Root OID encoded on tag
+- 3-28: Open environment – Root OID always {1 0 15961 <data format>}
+- 29: Closed environment – 15961-1/15962 encoded – Root OID always {1 0 15961 0}
+- 30: Closed environment – not 15961-1/15962 encoded
+- 31: Indicates additional octet.
+
+NOTE – There is a mechanism to extend the DSFID to more than one octet, which will allow additional values for the Access-Method and the Data-Format.
+
+The encoding of user memory locations after the DSFID shall be as defined in [b-ISO/IEC 15962].
+
+# Appendix IV
+
+## Overview of EPC types
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## IV.1 Scope of appendix
+
+## IV.2 Structure of serialized global trade item number (SGTIN) EPC types
+
+The SGTIN EPC types are considered in detail to illustrate how to convert a bit-encoded EPC to a URN or to a character encoded representation (GS1 element string) by using knowledge of the format of the bit-encoded EPC.
+
+![Figure IV.1: Format of SGTIN EPC types. The diagram shows two bit structures: SGTIN-96 and SGTIN-198. Both start with a Header ('30'H for SGTIN-96, '36'H for SGTIN-198), followed by Filter (F) and Partition (P) bits. The next 44 bits are split between Company prefix and Indicator digit and item reference, with the boundary dependent on the partition value. The remaining bits are the Serial number (38 bits for SGTIN-96, 140 bits for SGTIN-198).](5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg)
+
+Figure IV.1 illustrates the bit structure of SGTIN EPC types. It shows two variants: SGTIN-96 and SGTIN-198. Both structures begin with a Header (30'H for SGTIN-96, 36'H for SGTIN-198), followed by a Filter (F) bit and a Partition (P) bit. The next 44 bits are shared between the Company prefix and the Indicator digit and item reference, with the boundary between these two fields being dependent on the partition value. The remaining bits are the Serial number. For SGTIN-96, the Serial number is 38 bits long, while for SGTIN-198, it is 140 bits long. The diagram also includes labels for 'Filter', 'Partition', and 'Boundary dependent on partition value'.
+
+Figure IV.1: Format of SGTIN EPC types. The diagram shows two bit structures: SGTIN-96 and SGTIN-198. Both start with a Header ('30'H for SGTIN-96, '36'H for SGTIN-198), followed by Filter (F) and Partition (P) bits. The next 44 bits are split between Company prefix and Indicator digit and item reference, with the boundary dependent on the partition value. The remaining bits are the Serial number (38 bits for SGTIN-96, 140 bits for SGTIN-198).
+
+Figure IV.1 – Format of SGTIN EPC types
+
+Figure IV.1 shows the format of an SGTIN EPC. There are two different types of SGTIN, one type with a bit length of 96 (SGTIN-96) and another one with a bit length of 128 (SGTIN-128). An EPC of one of these types identifies a physical object for sale.
+
+The header values in Figure IV.1 indicate that the EPC types are SGTIN-96 and SGTIN-198.
+
+Three fields identify the actual item, namely the company prefix, the indicator digit/item reference (type of item) and serial number. The combined length of company prefix and indicator digit/item reference fields is always 44 bits for an SGTIN, but the boundary between the two fields is dependent on the partition value. These three fields are considered unsigned binary fields that shall be converted to numeric characters in the character-encoded format.
+
+The conversion between the bit-encoding and the character-encoding of an SGTIN EPC is illustrated in Figure IV.2.
+
+![Figure IV.2: Relationship between bit-encoded and character encoded SGTIN EPC. The diagram shows the conversion from a bit encoding URN sequence to a GS1 element string. The bit encoding includes Company prefix, Indicator digit, Item reference, and Serial number. The GS1 element string includes the Indicator digit, Company prefix, Item reference, Check digit, and Serial number, with specific delimiters like (01) and (21).](1b2ad37940c441d410002c05ff71c7c5_img.jpg)
+
+Figure IV.2 illustrates the relationship between the bit-encoded and character-encoded SGTIN EPC. The bit encoding URN sequence consists of the Company prefix, Indicator digit, Item reference, and Serial number. The GS1 element string is a character-encoded representation that includes the Indicator digit, Company prefix, Item reference, Check digit, and Serial number, with specific delimiters like (01) and (21). The diagram shows the mapping of these fields from the bit encoding to the character encoding.
+
+Figure IV.2: Relationship between bit-encoded and character encoded SGTIN EPC. The diagram shows the conversion from a bit encoding URN sequence to a GS1 element string. The bit encoding includes Company prefix, Indicator digit, Item reference, and Serial number. The GS1 element string includes the Indicator digit, Company prefix, Item reference, Check digit, and Serial number, with specific delimiters like (01) and (21).
+
+Figure IV.2 – Relationship between bit-encoded and character encoded SGTIN EPC
+
+The partition field indirectly indicates the length of the company prefix, *e.g.*, a zero partition value corresponds to a company prefix length of 40 bits, a partition value of one corresponds to a length of 37 bits, and so on. [b-GS1TAGDATA] provides tables giving the relationship between partition values and length of the company prefix. Varied EPC types have generally different tables, although EPC types of the same "family" like SGTIN may share a single table. Table V.1 gives an example of this.
+
+[b-GS1TAGDATA] also specifies how a binary field is converted to character string. As an example, the bits making up a company prefix are considered an unsigned integer to be converted into a corresponding numeric character representation. In other cases, the serial number for SGTIN-128, for example, is a series of seven bit bytes, each representing a character according to [b-ISO/IEC 646].
+
+When creating a GS1 element string, the characters have to be shifted around, some additional characters and a check digit are added. Figure IV.2 illustrates that the first digit of the indicator digit/item reference field after conversion from bit-encoding to character-encoding shall be moved to the front of the character string.
+
+In front of some fields, additional information is added indicating the types of fields when converted into GS1 element string.
+
+NOTE – 01 is a so-called application identifier (AI). This particular AI signals that what follows is a global trade item number (GTIN), while the AI 21 signals that what follows is a serial number. The AIs are surrounded by parenthesis.
+
+When creating a URN, the indicator digit shall not be moved and the check digit shall not be created, *i.e.*, the bit encoding and the URN have the same components in the same order.
+
+Other EPC UII types have different formats, but it is common for all of the types that the formatting information may be conveyed in an attribute of type **epcFormat** as defined in [ITU-T X.520]. A description of this attribute type is given in Appendix V.
+
+### IV.3 Structure of serial shipping container code (SSCC) EPC types
+
+![Figure IV.3: Format of SSCC EPC types. The diagram shows a horizontal block representing the SSCC-96 bit structure. From left to right: Header '31'H (8 bits), Filter (labeled 'F', 3 bits), Partition (labeled 'P', 3 bits), Company prefix, Extension/serial reference, and (Reserved) 24 zero bits. Above the blocks, arrows indicate bit lengths: the Company prefix and Extension/serial reference combined are 58 bits, and the Reserved section is 24 bits. An arrow below indicates the boundary between Company prefix and Extension/serial reference is 'Boundary dependent on partition value'.](f1091147d93cee4dfa88498610e395a7_img.jpg)
+
+Figure IV.3: Format of SSCC EPC types. The diagram shows a horizontal block representing the SSCC-96 bit structure. From left to right: Header '31'H (8 bits), Filter (labeled 'F', 3 bits), Partition (labeled 'P', 3 bits), Company prefix, Extension/serial reference, and (Reserved) 24 zero bits. Above the blocks, arrows indicate bit lengths: the Company prefix and Extension/serial reference combined are 58 bits, and the Reserved section is 24 bits. An arrow below indicates the boundary between Company prefix and Extension/serial reference is 'Boundary dependent on partition value'.
+
+Figure IV.3 – Format of SSCC EPC types
+
+![Figure IV.4: Relationship between bit-encoded and character encoded SSCC EPC. The diagram shows two rows. The top row is 'Bit encoding URN sequence' containing blocks for 'Company prefix', 'Extension digit', and 'Serial reference' (the latter two enclosed in a dashed box), followed by a 'Reserved' block. The bottom row is 'GS1 element string' starting with '(00)', followed by 'Extension digit' (moved from its position in the top row), 'Company prefix', 'Serial reference', and a new 'Check digit' block. Lines with arrows show the mapping of fields from the top row to the bottom row.](b560268ea8f6526970f23f0da225b099_img.jpg)
+
+Figure IV.4: Relationship between bit-encoded and character encoded SSCC EPC. The diagram shows two rows. The top row is 'Bit encoding URN sequence' containing blocks for 'Company prefix', 'Extension digit', and 'Serial reference' (the latter two enclosed in a dashed box), followed by a 'Reserved' block. The bottom row is 'GS1 element string' starting with '(00)', followed by 'Extension digit' (moved from its position in the top row), 'Company prefix', 'Serial reference', and a new 'Check digit' block. Lines with arrows show the mapping of fields from the top row to the bottom row.
+
+Figure IV.4 – Relationship between bit-encoded and character encoded SSCC EPC
+
+The serial shipping container code (SSCC) EPC type identifies a shipping container. One EPC type is defined as SSCC-96. Figures IV.3 and IV.4 illustrate how conversion is performed for a SSCC EPC type. It follows the same principles as described in clause 13.1.1.
+
+### IV.4 Structure of serialized global location number (SGLN) EPC types
+
+![Diagram showing the format of SGLN EPC types SGLN-96 and SGLN-195. Both types include a Header ('32'H for SGLN-96, '39'H for SGLN-195), Filter (F), Partition (P), Company prefix (41 bits), Location reference, and Extension. The boundary between Location reference and Extension is dependent on the partition value. For SGLN-96, the Extension is 41 bits. For SGLN-195, the Extension is 140 bits.](67114ecf6da13c97a89aeff0d86885d5_img.jpg)
+
+The diagram illustrates the structure of two SGLN EPC types. Both share a common header structure: a 4-bit Header ('32'H for SGLN-96, '39'H for SGLN-195), a 1-bit Filter (F), and a 1-bit Partition (P). The remaining 96 bits (for SGLN-96) or 195 bits (for SGLN-195) are divided into a 41-bit Company prefix, a Location reference, and an Extension field. The boundary between the Location reference and the Extension field is dependent on the partition value. For SGLN-96, the Extension field is 41 bits. For SGLN-195, the Extension field is 140 bits.
+
+| EPC Type | Header | F     | P     | Company prefix (41 bits) | Location reference | Extension |
+|----------|--------|-------|-------|--------------------------|--------------------|-----------|
+| SGLN-96  | '32'H  | 1 bit | 1 bit | 41 bits                  | Variable           | 41 bits   |
+| SGLN-195 | '39'H  | 1 bit | 1 bit | 41 bits                  | Variable           | 140 bits  |
+
+F.511(14)\_FIV.5
+
+Diagram showing the format of SGLN EPC types SGLN-96 and SGLN-195. Both types include a Header ('32'H for SGLN-96, '39'H for SGLN-195), Filter (F), Partition (P), Company prefix (41 bits), Location reference, and Extension. The boundary between Location reference and Extension is dependent on the partition value. For SGLN-96, the Extension is 41 bits. For SGLN-195, the Extension is 140 bits.
+
+Figure IV.5 – Format of SGLN EPC type
+
+Two EPC types are defined for SGLN as SGLN-96 and SGLN-195. There is no digit shifting. The GS1 element string is prefixed with the AI value "(414)". The extension field may be omitted in the GS1 element string, in which case the check digit is added to the end of the string. If the extension field is included, it is prefixed with the AI value "(254)". The check digit is inserted between the location reference field and the extension field.
+
+### IV.5 Structure of global returnable asset identifier (GRAI) EPC types
+
+![Diagram showing the format of GRAI EPC types GRAI-96 and GRAI-170. Both types include a Header ('32'H for GRAI-96, '39'H for GRAI-170), Filter (F), Partition (P), Company prefix (44 bits), Asset type, and Serial. The boundary between Asset type and Serial is dependent on the partition value. For GRAI-96, the Serial is 38 bits. For GRAI-170, the Serial is 112 bits.](0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg)
+
+The diagram illustrates the structure of two GRAI EPC types. Both share a common header structure: a 4-bit Header ('32'H for GRAI-96, '39'H for GRAI-170), a 1-bit Filter (F), and a 1-bit Partition (P). The remaining 96 bits (for GRAI-96) or 170 bits (for GRAI-170) are divided into a 44-bit Company prefix, an Asset type, and a Serial field. The boundary between the Asset type and the Serial field is dependent on the partition value. For GRAI-96, the Serial field is 38 bits. For GRAI-170, the Serial field is 112 bits.
+
+| EPC Type | Header | F     | P     | Company prefix (44 bits) | Asset type | Serial   |
+|----------|--------|-------|-------|--------------------------|------------|----------|
+| GRAI-96  | '32'H  | 1 bit | 1 bit | 44 bits                  | Variable   | 38 bits  |
+| GRAI-170 | '39'H  | 1 bit | 1 bit | 44 bits                  | Variable   | 112 bits |
+
+F.511(14)\_FIV.6
+
+Diagram showing the format of GRAI EPC types GRAI-96 and GRAI-170. Both types include a Header ('32'H for GRAI-96, '39'H for GRAI-170), Filter (F), Partition (P), Company prefix (44 bits), Asset type, and Serial. The boundary between Asset type and Serial is dependent on the partition value. For GRAI-96, the Serial is 38 bits. For GRAI-170, the Serial is 112 bits.
+
+Figure IV.6 – Format of GRAI EPC types
+
+Two EPC types are defined for GRAI as GRAI-96 and GRAI-170. There is no digit shifting. The GS1 element string is prefixed with the AI value "(8003)" followed by an additional "0" numeric character. The check digit is inserted between the asset type field and the serial field.
+
+### IV.6 Structure of global individual asset identifier (GIAI) EPC types
+
+![Diagram showing the format of GIAI EPC types (GIAI-96 and GIAI-202).](70a863dc6cd47bac82c12162a9479aac_img.jpg)
+
+The diagram illustrates the structure of two GIAI EPC types. Both types share a common header and control field structure: a 4-bit Header ('34'H for GIAI-96 and '38'H for GIAI-202), followed by a 1-bit Filter (F) and a 1-bit Partition (P). The remaining bits are divided into a Company prefix and an Individual asset reference. For GIAI-96, the total length is 96 bits, with 82 bits allocated to the Company prefix and Individual asset reference. For GIAI-202, the total length is 202 bits, with 188 bits allocated to the Company prefix and Individual asset reference. The boundary between the Company prefix and the Individual asset reference is dependent on the partition value.
+
+| EPC Type | Header | Filter (F) | Partition (P) | Company prefix | Individual asset reference | Total Bits |
+|----------|--------|------------|---------------|----------------|----------------------------|------------|
+| GIAI-96  | '34'H  | 1          | 1             | 82             | 8                          | 96         |
+| GIAI-202 | '38'H  | 1          | 1             | 188            | 14                         | 202        |
+
+F.511(14)\_FIV.7
+
+Diagram showing the format of GIAI EPC types (GIAI-96 and GIAI-202).
+
+Figure IV.7 – Format of GIAI EPC types
+
+Two EPC types are defined for global individual asset identifier (GIAI) as GIAI-96 and GIAI-202. There is no digit shifting. The GS1 element string is prefixed with the AI value "(8004)".
+
+### IV.7 Structure of global service relation number (GSRN) EPC types
+
+![Diagram showing the format of GSRN EPC types (GSRN-96).](34b047489058d6400b412cd0ae2334ba_img.jpg)
+
+The diagram illustrates the structure of the GSRN-96 EPC type. It consists of a 4-bit Header ('2D'H), a 1-bit Filter (F), and a 1-bit Partition (P). The remaining 90 bits are divided into a Company prefix (58 bits), a Service reference (24 bits), and a (Reserved) 24 zero bits. The boundary between the Company prefix and the Service reference is dependent on the partition value.
+
+| EPC Type | Header | Filter (F) | Partition (P) | Company prefix | Service reference | (Reserved) | Total Bits |
+|----------|--------|------------|---------------|----------------|-------------------|------------|------------|
+| GSRN-96  | '2D'H  | 1          | 1             | 58             | 24                | 24         | 96         |
+
+F.511(14)\_FIV.8
+
+Diagram showing the format of GSRN EPC types (GSRN-96).
+
+Figure IV.8 – Format of GSRN EPC types
+
+One EPC type is defined for global service relation number (GSRN) as GSRN-96. There is no digit shifting. The GS1 element string is prefixed with the AI value "(8018)".
+
+### IV.8 Structure of global document type identifier (GDTI) EPC types
+
+![Diagram showing the format of GDTI EPC types (GDTI-96 and GDTI-113).](e94cbc0895c6914a2bb53f150ab7495e_img.jpg)
+
+The diagram illustrates the structure of two GDTI EPC types. Both types share a common header and control field structure: a 4-bit Header ('2C'H for GDTI-96 and '2A'H for GDTI-113), followed by a 1-bit Filter (F) and a 1-bit Partition (P). The remaining bits are divided into a Company prefix, a Document type, and a Serial. For GDTI-96, the total length is 96 bits, with 41 bits allocated to the Company prefix and Document type, and 41 bits allocated to the Serial. For GDTI-113, the total length is 113 bits, with 41 bits allocated to the Company prefix and Document type, and 58 bits allocated to the Serial. The boundary between the Company prefix and the Document type is dependent on the partition value.
+
+| EPC Type | Header | Filter (F) | Partition (P) | Company prefix | Document type | Serial | Total Bits |
+|----------|--------|------------|---------------|----------------|---------------|--------|------------|
+| GDTI-96  | '2C'H  | 1          | 1             | 41             | 41            | 14     | 96         |
+| GDTI-113 | '2A'H  | 1          | 1             | 41             | 41            | 31     | 113        |
+
+F.511(14)\_FIV.9
+
+Diagram showing the format of GDTI EPC types (GDTI-96 and GDTI-113).
+
+Figure IV.9 – Format of GDTI EPC types
+
+Two EPC types are defined for global document type identifier (GDTI) as GDTI-96 and GDTI-113. There is no digit shifting. The GS1 element string is prefixed with the AI value "(8004)". A check digit is added between the document type field and the serial field.
+
+# Appendix V
+
+## Example of retrieving EPC format information
+
+(This appendix does not form an integral part of this Recommendation.)
+
+An example is used to illustrate how EPC format information may be retrieved. The EPC type SGTIN-198 with header value '36'H and partition value three is used in this example. The URN for the format information for that EPC type may be expressed as:
+
+"urn:spc:id:sgtin.3"
+
+An entry addressed by this URN will have an attribute of type **epcFormat** with the following value expressed in extensible markup language (XML) notation.
+
+```
+<fields>
+  <field>
+    <bits>30</bits>
+    <charField>
+      <characters>9</characters>
+    </charField>
+    <result><numericPad/></result>
+    <gs1Key>(01)</gs1Key>
+  </field>
+  <field>
+    <bits>14</bits>
+    <charField>
+      <characters>4</characters>
+    </charField>
+    <result><numericPad/></result>
+  </field>
+  <field>
+    <bits>140</bits>
+    <charField>
+      <characters>20</characters>
+    </charField>
+    <result><alpha7bits></result>
+    <gs1Key>(21)</gs1Key>
+  </field>
+</fields>
+<digitShift>10</digitShift>
+<checkCalc>13</checkCalc>
+<urnPrefix>urn:epc:id:sgtin:</urnPrefix>
+```
+
+This value states that the EPC consists of three fields beyond the header, filter and the partition fields. According to [b-GS1TAGDATA] (see Table V.1) a partition field value of three means:
+
+- The first field is 30 bits and once converted represents nine numeric characters padded in the front with zeroes if necessary. The GS1 Key "(01)" has to be added in front if a GS1 element string is produced.
+- The second field is 14 bits long and once converted represents four numeric characters padded in the front with zeroes, if necessary.
+- The third field is always 140 bits long and consists of seven bits bytes each representing a seven bits character as defined by [b-ISO/IEC 646].
+
+As the indicator digit is the first digit of the second field, it has number 10. In case a GS1 element string is produced, this digit has to be moved to the front of field one.
+
+The check digit is placed after the first two fields and therefore gets position number 14 and is calculated over all the characters in front of it (excluding the GS1 key).
+
+In case a GS1 element string is produced, the GS1 key "(21)" has to be added in front of the third field.
+
+In case a pure identity EPC URI is produced, it shall be prefixed with "urn:epc:id:sgtin:".
+
+The following is an example of EPC in binary encoding to be converted to a GS1 element string and to a pure identity EPC URI:
+
+'0011011000001110111101001101001111110110001100110101100101101010011010001101001111001110010011110011100000110100111101110101110110111000101100101111001000000000'B
+
+The first eight bits are the header. They have the value '0011 0110'B, which indicates that the EPC is an SGTIN-198.
+
+The next three bits field is the filter field and has the value 000 followed by the partition field with the value '011'B (decimal 3).
+
+As the partition field specifies the partitioning of the two first fields, it is necessary to consult the partition table for SGTIN as shown in Table V.1.
+
+**Table V.1 – Partition table for SGTIN**
+
+| Partition value | Company prefix |            | Indicator digit and item reference |        |
+|-----------------|----------------|------------|------------------------------------|--------|
+|                 | Bits (M)       | Digits (L) | Bits (N)                           | Digits |
+| 0               | 40             | 12         | 4                                  | 1      |
+| 1               | 37             | 11         | 7                                  | 2      |
+| 2               | 34             | 10         | 10                                 | 3      |
+| 3               | 30             | 9          | 14                                 | 4      |
+| 4               | 27             | 8          | 17                                 | 5      |
+| 5               | 24             | 7          | 20                                 | 6      |
+| 6               | 20             | 6          | 24                                 | 7      |
+
+The serial number for SGTIN-96 has a fixed length of 38 bits. When converted to numeric characters, the maximum value is 274.877.906.943. If the result exceeds that value, the UII is invalid.
+
+The serial number for SGTIN-198 has a fixed length of 140 bits allowing for 20 seven-bit ASCII characters.
+
+Having removed the header, the filter and the partition bits, the remaining bit stream has to be converted based on the format information from the **epcFormat** attribute value shown in Appendix VIII.
+
+'10111101001101001111110110001100110101100101101010011010001101001111001110010011110011100000110100111101110101110110111000101100101111001000000000'B
+
+- The first field is 30 bits long ('101111010011010011111101100011'B). When treated as an unsigned integer, this bit string is converted into the numeric characters: 793591651. As this field now consists of nine numeric characters, it does not have to be padded in the front with zeroes.
+- The second field is 14 bits long ('00110101100101'B). When treated as an unsigned number, this bit string is converted into numeric characters: 2917. As this field now consists of four numeric characters, it does not have to be padded in the front with zeroes.
+
+- c) The third field is 140 bits long or 20 bytes of seven bits ('1010100'B '1101000'B' 1101001'B '1110011'B '1001001'B '1110011'B '1000001'B '1010011'B '1100101'B '1110010'B '1101001'B '1100001'B '1101100'B '1001110'B '1110101'B '1101101'B '1100010'B '1100101'B '1110010'B '0000000'B). The first nineteen blocks are converted into alphanumeric characters (yielding "ThisIsASerialNumber"). The last block is all zero bits and therefore ignored.
+
+When concatenated, the converted fields consist of 32 characters numbered from 1 to 32:
+
+7935916512917ThisIsASerialNumber.
+
+The 10th character has to be move to the front:
+
+2793591651917ThisIsASerialNumber.
+
+The 13 first characters are now used to yield the check digit:
+
+$(3 \times 2 + 7 + 3 \times 9 + 3 + 3 \times 5 + 9 + 3 \times 1 + 6 + 3 \times 5 + 1 + 3 \times 9 + 1 + 3 \times 7) = 141$  subtracted from 150 equals nine, which is the check digit (see [b-GS1TAGDATA]).
+
+The resulting GS1 element string is "(01) 27935916519179 (21) ThisIsASerialNumber"
+
+If the pure identity URI is to be generated, the **urnPrefix** is concatenated with the fields as generated within a) b) and c) above with full stops inserted, which results in:
+
+"urn:epc:id:sgtin:793591651.2917.ThisIsASerialNumber"
+
+# Appendix VI
+
+## Overview of ISO/IEC 15459 UII types
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## VI.1 Overview
+
+This appendix provides a short description of the different fields of ISO/IEC 15459 UII types for the purpose this Recommendation.
+
+All the fields are in 6 bits character encoding using a limited character repertoire from [b-ISO/IEC 646] consisting of 0-9 and A-Z.
+
+## VI.2 Data identifier field
+
+A data identifier (DI) is a string of characters that define the general category or intended use of the data that follows. The string consists of either a single character alone or a character prefixed by one to three numeric characters.
+
+The American National Standards Institute (ANSI) registers DIs as part of the [b-MH10.8.2] standardization and they are listed in [b-ISO/IEC 15418].
+
+The following is a list of DIs relevant for [ISO/EC 15459 S].
+
+- I: Exclusive assignment – Vehicle identification number (VIN) as defined in the U.S. under 49 code of federal regulations (CFR), §§ 565 and internationally by [b-ISO 3779]. (These are completely compatible data structures)
+- J: Unique licence plate number. Maximum field is 35 alphanumeric characters.
+- 1J: Unique licence plate number assigned to a transport unit which is the lowest level of packaging, the unbreakable unit. Maximum field is 35 alphanumeric characters.
+- 2J: Unique licence plate number assigned to a transport unit which contains multiple packages. Maximum field is 35 alphanumeric characters.
+- 3J: Unique licence plate number assigned to a transport unit which is the lowest level of packaging, the unbreakable unit and which has electronic data interchange (EDI) data associated with the unit. Maximum field is 35 alphanumeric characters.
+- 4J: Unique licence plate number assigned to a transport unit which contains multiple packages and which is associated with EDI data. Maximum field is 35 alphanumeric characters.
+- 5J: Unique licence plate number assigned to a mixed transport unit containing different items on a single customer transaction and may or may not have associated EDI data. Maximum field is 20 alphanumeric characters.
+- 6J: Unique licence plate number assigned to a master transport unit containing like items on a single customer transaction and may or may not have associated EDI data. Max field 20 alphanumeric characters.
+- 1P: Item identification code assigned by the supplier
+- 25B: Identification of a party to a transaction in which the data format consists of two concatenated segments. The first segment is the unique code assigned to an issuing agency by the Netherlands Normalisatie-instituut (NEN) in accordance with [ISO/IEC 15459]; the second segment is a unique entity identification assigned in accordance with rules established by the issuing agency. This identification is followed by a supplier assigned serial number to a returnable transport item (RTI). The Maximum field is 35 alphanumeric characters.
+
+- 25K: Global unique identification of groupings of transport units assigned by the carrier, defined as:  
+ Identification of a party to a transaction as identified in 18V, followed by the bill of lading or waybill or shipment identification code assigned by that party.
+- 26K: Global unique identification of groupings of transport units assigned by the shipper, defined as:  
+ Identification of a party to a transaction as identified in 18V, followed by the Bill of Lading or Waybill or Shipment Identification Code assigned by that party.
+- 25P: Identification of a party to a transaction in which the data format consists of two concatenated segments. The first segment is the unique code assigned to an issuing agency by NEN in accordance with [ISO/IEC 15459-S], the second segment is a unique entity identification assigned in accordance with rules established by the issuing agency. This identification is followed by a supplier assigned a part number. The maximum field is 35 alphanumeric characters.
+- S: A serial number or code assigned by the supplier to an entity for its lifetime, (e.g., a computer serial number, a traceability number, a contract tool identification).
+- 25S: Identification of a party to a transaction in which the data format consists of two concatenated segments. The first segment is the unique code assigned to an issuing agency by NEN in accordance with [ISO/IEC 15459 S], the second segment is a unique entity identification assigned in accordance with rules established by the issuing agency. This identification is followed by a supplier assigned serial number. The max field 35 is alphanumeric characters.
+- 25T: Identification of a party to a transaction as identified in 18V, followed by the supplier assigned a traceability number.
+- 17V: U.S. DoD CAGE Code
+- 18V: Identification of a party to a transaction in which the data format consists of two concatenated segments. The first segment is the unique code assigned to an issuing agency by NEN in accordance with [ISO/IEC 15459 S], the second segment is a unique entity identification assigned in accordance with rules established by the issuing agency.
+
+## VI.3 Issuing agency codes (IAC)
+
+Different agencies, called issuing agencies, may define codes for organizations, companies, institutions, etc. Each issuing agency is allocated an issuing IAC. Such IACs are allocated by a registration authority, which currently is NEN (Nederlands Normalisatie-instituut).
+
+The rules for registering IACs are specified in [ISO/IEC 15459-2].
+
+The following is a short description of the rules for defining IACs.
+
+A single character A to J may be assigned to non-profit international organizations. Examples are:
+
+- D – NATO AC/135
+- J – Universal Postal Union
+
+A single letter K followed by a two-character country code for national public administrations. Examples are:
+
+- KKR – Korea Institute of Distribution and Logistics
+
+A two-letter code starting with L to U for other agencies. Examples are:
+
+- OD – ODETTE EUROPE (auto industry)
+
+A three-letter code starting with V to Z for other agencies. Examples are:
+
+– VIB – IBM
+
+## **VI.4 Company identification number (CIN)**
+
+The issuing agency allocates CINs to organizations. The issuing agency determines the length of the CINs within its authority. CIN is the common term for companies or organizations responsible for the remaining fields (by NATO, this is called CAGE or NCAGE Code; by the Universal Postal Union (UPU) called the issuer code; etc.).
+
+### **VI.5 Remaining fields**
+
+The remaining fields are allocated by the organization to which a CIN is allocated. There is no general rule for how the field lengths relate to each other.
+
+# Appendix VII
+
+## Examples of retrieving UII format information
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## VII.1 Scope of appendix
+
+This appendix illustrates how the UII format is retrieved.
+
+## VII.2 IAC=UN (Dun and Bradstreet)
+
+Let us assume the following:
+
+UII = "UN043325711MH803120000001"
+
+where the UII is encoded using six-bit characters.
+
+As the IAC starts with "U", it is known that the IAC consists of two characters and has therefore the value "UN".
+
+The initial part of the URN for IAC=UN is:
+
+"urn:iso:std:iso-iec:15459.25S.UN"
+
+The corresponding distinguished name is:
+
+{ urnC="iso", urnC="std", urnC="iso=iec", urnC="15459", unrC="25S", urnC="UN" }
+
+This distinguished name is used to read the addressed entry and it is assumed that the result is an attribute of type **uiiFormat** with the following value.
+
+```
+<Uiiformat>
+  <subset>baseObject</subset>
+  <next>
+    <length>9</length>
+  </next>
+</Uiiformat>
+```
+
+This value indicates that the next level (the CIN) is always nine characters long. Accordingly, the CIN is "043325711".
+
+The URN is updated to include the value of the CIN:
+
+"urn:iso:std:iso-iec:15459:UN. 043325711"
+
+As no filter is supplied, and the **subset** is suggested to be **baseObject**, the next operation should be a search with an empty filter, a subset equal to **baseObject** and a base object name corresponding to the above URN.
+
+An **ldapUrl** may be returned together with an attribute of type **uiiFormat** with the following value:
+
+```
+<Uiiformat>
+  <subset>wholeSubtree</subset>
+  <next>
+    <filter>
+      <item>
+        <type>1.2.3.4.5</type>
+      </item>
+    </filter>
+  </next>
+</Uiiformat>
+```
+
+It can be assumed that the result also included an attribute of type **ldapURL** pointing to the site of the identified organization. A complete search is performed at that site, i.e., an empty distinguished name
+
+is used as a base object and the filter is an attribute value assertion of type `uii` with the complete `UII` as value. The result is the return of information about the item to which the RFID tag is attached.
+
+## VII.3 IAC=J example (UPU)
+
+In the case of an IAC equals J, the issuing agency is the Universal Postal Union (UPU). In this case, the CIN (or the issuer code according to UPU) field is either two or three characters long.
+
+Let us assume the following:
+
+`UII = "JDKA01NR0C09602291710C0AB5A4"`
+
+As the IAC starts with "J", it is known that the IAC consists of one character.
+
+The initial part of the URN for IAC=J is:
+
+`"urn:iso:std:iso-iec:15459:J"`
+
+This distinguished name corresponding to this URN is used to read the addressed entry. It can then be assumed that the result is an attribute of type `uiiFormat` with the following value.
+
+```
+<Uiiformat>
+  <subset>oneLevel</subset>
+  <next>
+    <filter>
+      <or>
+        <item>
+          <type>2.5.4.89</type>
+          <length>2</length>
+        </item>
+        <item>
+          <type>2.5.4.89</type>
+          <length>3</length>
+        </item>
+      </or>
+    </filter>
+  </next>
+</Uiiformat>
+```
+
+Based on that value, a search is generated with the base object as the same as for the previous search and with a subset stating `oneLevel`. A filter is generated with two attribute value assertions against an attribute of type `urnC`, one with the two characters "DK" and the other with the three characters "DKA". These two attribute value assertions are OR'ed, which means that an entry will be returned if an entry has an attribute of type `urnC` with either the value "DK" or "DKA". If there is an entry immediately subordinate to the base object with an attribute of type `urnC` with two values, which happen to be "DK" and "DKA" and no other immediately subordinate entry has any of those values, the search will then return the single entry that matches the filter together with the attribute with the two values and the distinguished name of the entry. The last component of that distinguished name has the value "DKA", which then goes into the URN corresponding to the entry, this means that the URN is:
+
+`"urn:iso:std:iso-iec:15459:J.DKA"`
+
+The used filter is now checked against the returned attribute of type `urnC` and both values satisfy the filter. The `UIIpointer` is now updated with the length of the longest attribute value, which is three.
+
+If the returned entry also contains an attribute of type `uiiFormat` with the following value:
+
+```
+<Uiiformat>
+  <subset>baseObject</subset>
+  <next>
+    <length>2</length>
+  </next>
+</Uiiformat>
+```
+
+The next component of the URN is two characters long with the value "01". The URN is now:
+
+"urn:iso:std:iso-iec:15459:J.DKA.01"
+
+This distinguished name corresponding to this URN name is now used to read the addressed entry and it will be assumed that the result is an attribute of type **ldapURL** pointing to a new site and an attribute of type **uiiFormat** with the following value.
+
+```
+<Uiiformat>
+  <baseObject>urn:abc.def.ghi</baseObject>
+  <subset>wholeSubtree</subset>
+  <next>
+    <filter>
+      <item>
+        <type>1.2.3.4.5</type>
+      </item>
+    </filter>
+  </next>
+</Uiiformat>
+```
+
+A search is now performed against the new site using the base object as specified and using a subset that dictates searching all entries in the subtree having its root in the entry corresponding to the specified URN. An attribute value assertion has to be generated against the attribute of type {1.2.3.4.5} using the whole UII as value. The result is the information about the item to which the RFID tag is affixed.
+
+# Appendix VIII
+
+## The format attribute type
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## VIII.1 Introduction
+
+This appendix provides a tutorial overview of the directory attribute types used to provide RFID format information.
+
+## VIII.2 EPC format information
+
+An attribute of the **epcFormat** attribute type specifies how an EPC bit string may be partitioned into components.
+
+An EPC consists of a number of fields. Only the formats of the fields following the header, the filter and the partition fields are considered. For each of the subsequent fields the following information is provided:
+
+- a) The length of the field in number of bits.
+- b) The limitation on the resulting character string:
+  - the maximum number of characters to which the bit string may be converted; or
+  - if the string consists of all numeric characters, the value shall not exceed a specified value.
+- c) The specifications for the resulting string shall result in either:
+  - the string shall consist of numeric characters and shall be prefixed with '0's to pad the string to the maximum length, as specified in b):  
+the string shall consist of numeric characters without padding; or
+  - the string shall consist of alphanumeric characters limited to the ASCII character set.
+
+The following information is independent of the individual fields:
+
+- a) The number of the resulting octet that needs to be shifted to the front in case of a character representation of the EPC.
+- b) A check digit to be added.
+- c) To make a URN globally unique a prefix has to be added. The prefix has the format "urn:epc:id:<epc scheme>:", where "<epc scheme>" is either "sgtin", "ssec", "sgln", "grai", "giai", "gdti", "gsrn", "gid" or "usdod".
+
+## VIII.3 UII format information
+
+An attribute of the **uiiFormat** attribute type specifies how to return information related to an UII string by specifying how a subsequent search should be performed. It is assumed that the UII has been resolved down to a specific point, and that some of the subsequent characters constitute the next field. This means that the distinguished name of the entry corresponding to the latest UII field is resolved and that the RDN corresponding to the subsequent UII field is to be determined. This is done by finding the value of the subsequent field to be used as the RDN value for the entry representing the subsequent field.
+
+A value of this attribute type has the following syntax expressed in ASN.1 terms:
+
+```
+UiFormat ::= SEQUENCE {  
+  baseObject URI,  
+  subset      ENUMERATE {  
+    baseObject (0),  
+    oneLevel   (1),  
+    wholeSubtree (2) } DEFAULT baseObject,  
+  next        CHOICE {  
+    length    INTEGER,  
+    filter    UiFilter } }  
+  
+UiFilter ::= CHOICE {  
+  item [0]  UiItem,  
+  and  [1]  SET OF UiFilter,  
+  or   [2]  SET OF UiFilter,  
+  not  [3]  UiFilter }  
+  
+UiItem ::= SEQUENCE {  
+  type    ATTRIBUTE.&id OPTIONAL,  
+  length INTEGER      OPTIONAL }
+```
+
+The **baseObject** component shall contain the URN corresponding to the base object of the search. If this component is absent, the search is suggested to start at the root.
+
+The **subset** component gives a recommendation as to how to fill the **subset** component of the **Filter** in a subsequent search operation. **baseObject** specifies that the search shall only be performed against the base object. **oneLevel** specifies that only the entries immediately subordinate to the base object are to be searched. **wholeSubtree** specifies that all entries in the subtree having the base object as root are to be searched.
+
+The **next** component gives some information about the next field of the UII:
+
+- The choice **length** subcomponent shall be taken if the length of the following UII field has a fixed length and the subcomponent signals the length in characters.
+- The choice **filter** shall be taken if the following UII field does not have a fixed length. It provides guidance on how filter items should be constructed to explore the actual length of the next UII field. The **UiFilter** data type has a recursive structure similar to the structure of the **Filter** data type as defined by [ITU-T X.511] allowing for specification for a filter of arbitrary complexity.
+
+The recommendation for a particular filter item is given by the **UiItem** data type
+
+- i) the **type** subcomponent specifies the attribute type to be used in the attribute value assertion; and
+- ii) the **length** subcomponent specifies how many characters are to be used as the value of the attribute value assertion.
+
+NOTE – Only in rare circumstances will the full power of this rather complicated attribute type be used. It will only come in use when there is no, or little, discipline on how UIIs are constructed. In the case the next UII field has a fixed length, the value of the attribute gives the number of characters to be used for the next RDN. By adding this RDN to the distinguished name at hand, the entry representing the entry of the subsequent field may be read. As another example: If the length of the subsequent field is either two or three characters long, the value of the **uiiFormat** attribute indicates that two filter items should be constructed, one filter item consisting of two characters and another of three characters. These two filter items should then be OR'ed in the filter for locating the entry that corresponds to the subsequent field.
+
+# Bibliography
+
+- [b-ITU-T F.771] Recommendation ITU-T F.771 (2008), *Service description and requirements for multimedia information access triggered by tag-based identification.*
+- [b-ITU-T H.621] Recommendation ITU-T H.621 (2008), *Architecture of a system for multimedia information access triggered by tag-based identification.*
+- [b-ITU-T H.642.1] Recommendation ITU-T H.642.1 (2012), *Multimedia information access triggered by tag-based identification – Identification scheme.*
+- [b-ITU-T Y.2091] Recommendation ITU-T Y.2091 (2007), *Next Generation Networks – Frameworks and functional architecture models Terms and definitions for Next Generation Networks.*
+- [b-ISO/IEC 646] ISO 646:1991, *Information processing – ISO 7-bit coded character set for information interchange.*
+- [b-ISO 3779] ISO 3779:2009, *Road vehicles – Vehicle identification number (VIN) – Content and structure.*
+- [b-ISO/IEC 15418] ISO/IEC 15418:2009, *Information technology – Automatic identification and data capture techniques – GS1 Application Identifiers and ASC MH10 Data Identifiers and maintenance.*
+- [b-ISO/IEC 15962] ISO/IEC 15962:2013, *Information technology – Radio frequency identification (RFID) for item management – Data protocol: data encoding rules and logical memory functions.*
+- [b-ISO/IEC 15963] ISO/IEC 15963:2009, *Information technology – Radio frequency identification for item management – Unique identification for RF tags.*
+- [b-GS1TAGDATA] GS1 EPCglobal, *EPC Tag Data Standard*, Version 1.5.
+- [b-GS1GS] GS1 General Specification, Version 10, Issue 1, Jan-2010.
+- [b-MH10.8.2] MH10.8.2, *Data Identifier & Application Identifier Standard.*
+
+
+
+# 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           |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                             |
+| 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/F/T-REC-F.600-200404-I_PDF-E/raw.md b/marked/F/T-REC-F.600-200404-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..b50cb7ece28c320ec3a11eae9cc94acab34172aa
--- /dev/null
+++ b/marked/F/T-REC-F.600-200404-I_PDF-E/raw.md
@@ -0,0 +1,486 @@
+
+
+![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
+
+# **F.600**
+
+(04/2004)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Data transmission services
+
+---
+
+**Service and operational principles for public  
+data transmission service**
+
+ITU-T Recommendation F.600
+
+---
+
+# ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| <b>TELEGRAPH SERVICE</b>                                        |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| <b>MOBILE SERVICE</b>                                           |                    |
+| Mobile services and multidestination satellite services         | F.110–F.159        |
+| <b>TELEMATIC SERVICES</b>                                       |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| <b>MESSAGE HANDLING SERVICES</b>                                | F.400–F.499        |
+| <b>DIRECTORY SERVICES</b>                                       | F.500–F.549        |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | <b>F.600–F.699</b> |
+| <b>AUDIOVISUAL SERVICES</b>                                     | F.700–F.799        |
+| <b>ISDN SERVICES</b>                                            | F.800–F.849        |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | F.850–F.899        |
+| <b>HUMAN FACTORS</b>                                            | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# **ITU-T Recommendation F.600**
+
+# **Service and operational principles for public data transmission service**
+
+## **Summary**
+
+This Recommendation contains the general service and operational principles to be followed for the international public data transmission service. The general model of international public data transmission service is outlined. This Recommendation includes important aspects of data transmission service – addressing, quality of service, call progress signals, multicast operation, user classes of service and optional user facilities. The general provisions between Administrations and the general provisions between the Administration and the customer are also described.
+
+The overview of the interrelationship between the relevant Recommendations necessary for offering data transmission service is in the scope of this Recommendation.
+
+###### **Source**
+
+ITU-T Recommendation F.600 was approved on 29 April 2004 by ITU-T Study Group 17 (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                                                                | 2    |
+| 3 Terminology                                                               | 4    |
+| 4 Abbreviations                                                             | 4    |
+| 5 General model of international PDTS                                       | 4    |
+| 6 Addressing aspects                                                        | 5    |
+| 7 Quality of service                                                        | 6    |
+| 8 Call progress signals                                                     | 6    |
+| 9 Multicast operation                                                       | 6    |
+| 10 User classes of service, categories of access                            | 6    |
+| 11 Optional user facilities                                                 | 7    |
+| 12 Data compression and security                                            | 7    |
+| 13 Administrative arrangements for international Closed User Groups         | 7    |
+| 14 Administrative arrangements for international Permanent Virtual Circuits | 7    |
+| 15 Charging principles                                                      | 7    |
+| 16 Duration of service                                                      | 8    |
+| 17 Outages                                                                  | 8    |
+| 18 Service calls                                                            | 8    |
+| 19 General provisions between Administrations                               | 8    |
+| 20 General provisions between Administration and customer                   | 8    |
+
+
+
+# Service and operational principles for public data transmission service
+
+## **1 Scope**
+
+**1.1** The establishment in various countries of public data networks creates the need to produce Recommendations to facilitate the provision of international public data transmission services. This Recommendation lays down the general service and operational principles to be followed for international data transmission services.
+
+This Recommendation provides an overview of interrelationship between the relevant Recommendations necessary for establishing, maintaining and offering the public data transmission service.
+
+**1.2** Public Data Transmission Service (PDTS) is a service established by an Administration and provides exchange of data between service users.
+
+NOTE – In this Recommendation, the expression "Administration" is used to indicate both a telecommunication administration and a Recognized Operating Agency (ROA). An international PDTS may be provided through the interworking of national Public Data Networks (PDNs) and Integrated Services Digital Networks (ISDNs). Public data networks are established and operated by the Administration for the specific purpose of providing data transmission service.
+
+**1.3** Public data networks and public data transmission services do not include the Data Terminal Equipment (DTE). Therefore, additional capabilities arise because DTEs do not belong to PDNs and PDTSs. PDTS is assumed to be equivalent to the bearer service (see the definition of bearer service in ITU-T Recs I.112 and I.230). Public Data Networks in Open Systems Interconnection (OSI) environments typically provide three lower layers: physical layer, data link layer and network layer (see ITU-T Recs X.200 | ISO/IEC 7498-1 and X.300).
+
+Various services based on PDTS may be operated by Administrations. Those services are assumed to be equivalent to teleservices (refer to ITU-T Recs I.112 and I.240 for the definition of teleservice). See Figure 1.
+
+**1.4** Four types of data transmission services are identified: circuit switched, packet switched, frame relay and leased circuit PDTS. Those services are based on Circuit-Switched Public Data Networks (CSPDNs), Packet-Switched Public Data Networks (PSPDNs), Frame Relay Public Data Networks (FRPDNs) and Leased Circuits.
+
+**1.5** This Recommendation does not cover international leased circuit PDNs. Also, this Recommendation does not cover public data transmission services offered by Integrated Services Digital Networks (ISDNs). Access to PDTS in one country through the Public Switched Telephone Network (PSTN) in another country is also out of the scope of this Recommendation. This Recommendation does not cover data transmission possibilities provided by IP-based networks or data transmission possibilities provided by modems on Public Switched Telephone Network (PSTN).
+
+![Diagram illustrating the environment for data transmission service. It shows two Data Terminal Equipment (DTE) units connected to a central Data network via User/network interfaces. Each interface connects to a Data Circuit-Terminating Equipment (DCE) which is part of the Data network. The Data network provides a Data transmission service (bearer service) between the two User/network interfaces. Teleservices (facsimile service, computer service, etc.) are shown as being provided by the Data network to the DTEs. The diagram is labeled F.600_F01.](3121ebddccf183ca63bb9781be440a7e_img.jpg)
+
+```
+
+graph LR
+    subgraph DTE_Left [DTE]
+        L_DTE[ ]
+    end
+    subgraph Network [Data network]
+        L_DCE[DCE] --- R_DCE[DCE]
+    end
+    subgraph DTE_Right [DTE]
+        R_DTE[ ]
+    end
+    L_DTE --- L_IF(( ))
+    L_IF --- L_DCE
+    R_DCE --- R_IF(( ))
+    R_IF --- R_DTE
+    
+    L_IF -.->|User/network interface| L_IF
+    R_IF -.->|User/network interface| R_IF
+    
+    L_IF <==>|Data transmission service  
+(bearer service)| R_IF
+    L_DTE <==>|Teleservices  
+facsimile service, computer service, etc.| R_DTE
+
+```
+
+Diagram illustrating the environment for data transmission service. It shows two Data Terminal Equipment (DTE) units connected to a central Data network via User/network interfaces. Each interface connects to a Data Circuit-Terminating Equipment (DCE) which is part of the Data network. The Data network provides a Data transmission service (bearer service) between the two User/network interfaces. Teleservices (facsimile service, computer service, etc.) are shown as being provided by the Data network to the DTEs. The diagram is labeled F.600\_F01.
+
+DTE Data terminal equipment (subscriber's terminal, teleservice server, etc.)  
+DCE Data circuit-terminating equipment
+
+**Figure 1/F.600 – The environment for data transmission 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 Recommendation E.116 (1997), *International telecommunication charge card service*.
+- ITU-T Recommendation E.164 (1997), *The international public telecommunication numbering plan*.
+- ITU-T Recommendation F.17 (1992), *Operational aspects of service telecommunications*.
+- ITU-T Recommendation I.112 (1993), *Vocabulary of terms for ISDNs*.
+- ITU-T Recommendation I.230 (1988), *Definition of bearer service categories*.
+- ITU-T Recommendation I.240 (1988), *Definition of teleservices*.
+- ITU-T Recommendation X.1 (2000), *International user classes of service in, and categories of access to, public data networks and Integrated Services Digital Networks (ISDNs)*.
+- ITU-T Recommendation X.2 (2000), *International data transmission services and optional user facilities in public data networks and ISDNs*.
+- ITU-T Recommendation X.6 (1997), *Multicast service definition*, plus Amendment 1 (2000), *Frame relay PVC multicast service definition*.
+- ITU-T Recommendation X.7 (2004), *Technical characteristics of data transmission services*.
+- ITU-T Recommendation X.92 (1988), *Hypothetical reference connections for public synchronous data networks*.
+- ITU-T Recommendation X.96 (2000), *Call progress signals in public data networks*.
+
+- ITU-T Recommendation X.110 (2002), *International routing principles and routing plan for Public Data Networks.*
+- ITU-T Recommendation X.111 (2003), *Principles for the routing of international frame relay traffic.*
+- ITU-T Recommendation X.115 (1995), *Definition of address translation capability in public data networks.*
+- ITU-T Recommendation X.116 (1996), *Address translation registration and resolution protocol.*
+- ITU-T Recommendation X.121 (2000), *International numbering plan for public data networks.*
+- ITU-T Recommendation X.130 (1988), *Call processing delays in public data networks when providing international synchronous circuit-switched data services.*
+- ITU-T Recommendation X.131 (1988), *Call blocking in public data networks when providing international synchronous circuit-switched data services.*
+- ITU-T Recommendation X.135 (1997), *Speed of service (delay and throughput) performance values for public data networks when providing international packet-switched services.*
+- ITU-T Recommendation X.136 (1997), *Accuracy and dependability performance values for public data networks when providing international packet-switched services.*
+- ITU-T Recommendation X.137 (1997), *Availability performance values for public data networks when providing international packet-switched services.*
+- ITU-T Recommendation X.144 (2003), *User information transfer performance parameters for public frame relay data networks.*
+- ITU-T Recommendation X.145 (2003), *Connection establishment and disengagement performance parameters for public Frame Relay data networks providing SVC services.*
+- ITU-T Recommendation X.146 (2000), *Performance objectives and quality of service classes applicable to frame relay.*
+- ITU-T Recommendation X.147 (2003), *Frame Relay network availability.*
+- ITU-T Recommendation X.180 (1988), *Administrative arrangements for international Closed User Groups (CUGs).*
+- ITU-T Recommendation X.181 (1988), *Administrative arrangements for the provision of international permanent virtual circuits (PVCs).*
+- ITU-T Recommendation X.200 (1994) | ISO/IEC 7498-1:1994, *Information technology – Open Systems Interconnection – Basic reference model: The basic model.*
+- ITU-T Recommendation X.272 (2000), *Data compression and privacy over frame relay networks.*
+- ITU-T Recommendation X.300 (1996), *General principles for interworking between public networks and between public networks and other networks for the provision of data transmission services.*
+- ITU-T Recommendation X.371/Y.1402 (2001), *General arrangements for interworking between Public Data Networks and the Internet.*
+
+## 3 Terminology
+
+The definitions of terms used in this Recommendation are in ITU-T Rec. X.7.
+
+NOTE – Within this Recommendation the term "Frame Relay Public Data Network (FRPDN)" is used. Some other Recommendations use the term "Public Frame Relay Data Network (PFRDN)". Both terms have absolutely the same meaning.
+
+## 4 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+|       |                                       |
+|-------|---------------------------------------|
+| CSPDN | Circuit-Switched Public Data Network  |
+| CUG   | Closed User Group                     |
+| DCE   | Data Circuit-terminating Equipment    |
+| DTE   | Data Terminal Equipment               |
+| FRPDN | Frame Relay Public Data Network       |
+| IDSE  | International Data Switching Exchange |
+| ISDN  | Integrated Services Digital Network   |
+| OSI   | Open Systems Interconnection          |
+| PSPDN | Packet-Switched Public Data Network   |
+| PDN   | Public Data Network                   |
+| PDTS  | Public Data Transmission Service      |
+| PSTN  | Public Switched Telephone Network     |
+| PVC   | Permanent Virtual Circuit             |
+| ROA   | Recognized Operating Agency           |
+
+## 5 General model of international PDTS
+
+**5.1** An international PDTS is based on an interconnection of national PDTSs. Such an interconnection is achieved with the interconnection of International Data Switching Exchanges (IDSEs) in relevant countries. The route for a call consists of three parts (see Figure 2):
+
+- an originating national network part, from calling DTE to originating IDSE through the originating national PDN;
+- an international network part, from the originating IDSE to the destination IDSE;
+- a destination national network part, from the destination IDSE to the called DTE through the destination national PDN.
+
+![Diagram illustrating the components of an international call. The diagram shows a sequence of components from left to right: Calling DTE, Original national network part (containing a National network and an IDSE), International network part (containing an International link), Destination national network part (containing an IDSE and a National network), and Called DTE. A double-headed arrow at the bottom indicates 'The route for an international call'. A legend at the bottom left defines DTE as Data terminal equipment and IDSE as International data switching exchange. The label F.600_F02 is in the bottom right corner.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+```
+
+graph LR
+    A[Calling DTE] --- B[Original national network part]
+    subgraph B [Original national network part]
+        B1[National network] --- B2[IDSE]
+    end
+    B2 --- C[International link]
+    subgraph C [International network part]
+        C1[International link]
+    end
+    C1 --- D[Destination national network part]
+    subgraph D [Destination national network part]
+        D1[IDSE] --- D2[National network]
+    end
+    D2 --- E[Called DTE]
+
+```
+
+The diagram illustrates the components of an international call. It shows a sequence of components from left to right: Calling DTE, Original national network part (containing a National network and an IDSE), International network part (containing an International link), Destination national network part (containing an IDSE and a National network), and Called DTE. A double-headed arrow at the bottom indicates 'The route for an international call'. A legend at the bottom left defines DTE as Data terminal equipment and IDSE as International data switching exchange. The label F.600\_F02 is in the bottom right corner.
+
+Diagram illustrating the components of an international call. The diagram shows a sequence of components from left to right: Calling DTE, Original national network part (containing a National network and an IDSE), International network part (containing an International link), Destination national network part (containing an IDSE and a National network), and Called DTE. A double-headed arrow at the bottom indicates 'The route for an international call'. A legend at the bottom left defines DTE as Data terminal equipment and IDSE as International data switching exchange. The label F.600\_F02 is in the bottom right corner.
+
+**Figure 2/F.600 – Components of an international call**
+
+**5.2** Various types of PDNs (and/or other networks) may interwork within a national network part. The originating national network part and the destination national network part may be different types of PDNs (or other networks). The international network part may consist of interworked IDSEs belonging to different networks of various countries. See ITU-T Recs X.1 and X.7 for possible interworking between networks providing data transmission. See ITU-T Rec. X.371/Y.1402 for interworking between PDNs and the Internet.
+
+**5.3** The planning of originating and destination PDNs is a national matter. Planning of originating and destination traffic routes is also a national matter. However, the quality of service of an international PDTs has to be taken into account when planning national PDNs, originating and destination traffic routes.
+
+The planning of international traffic routes is the responsibility of the concerned Administrations and is subject to bilateral agreement.
+
+**5.4** Interworked national PDNs may be interconnected directly or via intermediate countries. For PSPDNs, FRPDNs and CSPDNs, routing principles of international data traffic are outlined in ITU-T Recs X.110 and X.111.
+
+**5.5** Administrations should compile information concerning service parameters of their networks for dissemination upon the request of the interested Administrations to enable the selection of the PDN for interworking and the planning of such interworking.
+
+**5.6** The total connection should comply with ITU-T Rec. X.92 for PSPDN and CSPDN. Hypothetical Reference Connections for FRPDNs are for further study.
+
+**5.7** Access to a national PDTs may be either *direct access* (without any intermediate switched network) or *port access* (via an intermediate switched network). Planning of access is a national matter. Access to a destination national PDTs via a PSTN or an ISDN of an originating country should be referred to as port access.
+
+**5.8** General aspects of PDTs including technical characteristics of PDTs in PDNs are outlined in ITU-T Rec. X.7.
+
+## **6 Addressing aspects**
+
+**6.1** Numbering in PDNs should comply with the International Numbering Plan specified in ITU-T Rec. X.121. PDNs may identify some DTEs by numbers from the E.164 numbering plan. FRPDNs may use either the X.121 or E.164 numbering plans.
+
+**6.2** Customers of PSPDNs and FRPDNs may use (where provided) alternative addressing, which does not correspond to the requirements of ITU-T Recs X.121 and E.164, for example some kinds of user-friendly addresses such as mnemonic addresses. In this case, PSPDN and FRPDN should have an address translation service which enables the PDNs to route calls to the proper X.121/E.164 address when the called address is out of the scope of X.121/E.164 addressing. Usage of the address translation service within the national PDNs is a national matter. Offering address translation capability in an international PDTS requires special provisions agreed between the Administrations concerned.
+
+**6.3** The definition of the address translation capability is outlined in ITU-T Recs X.115 and X.116.
+
+## **7 Quality of service**
+
+**7.1** Quality of service of an international PDTS is a subject of common responsibility of the Administrations concerned. Quality of service of a national network part is the responsibility of each relevant Administration. Quality of service of an international network part is the responsibility of the concerned (including transit) Administrations.
+
+**7.2** Apportioning of quality of service parameter values (national and international portions) should comply with ITU-T Recs X.135, X.136 and X.137 for PSPDN; ITU-T Recs X.130, X.131 for CSPDN; ITU-T Recs X.144, X.145, X.146 and X.147 for FRPDN.
+
+**7.3** Apportioning of quality of service parameter values of international network part is subject to agreement between all Administrations involved in the provision of international network part.
+
+## **8 Call progress signals**
+
+**8.1** Call progress signals inform the caller about the progress of the call including the circumstances which may have prevented the connection.
+
+**8.2** Call progress signals for CSPDN, PSPDN and FRPDN are defined in ITU-T Rec. X.96.
+
+## **9 Multicast operation**
+
+**9.1** Multicast service facilitates the provision of point-to-multipoint (multicast) data service. Using a multicast service, the customer (sender) must first establish a connection to the entity called multicast server, and after that data units are transferred by multicast server to other participants of the multicast service (receivers).
+
+**9.2** Establishment of national multicast services and methods of establishing multicast services (inside or outside the national PDN), etc., are a national matter. Establishment of international multicast services (establishing of international multicast groups, principles of interworking of national multicast servers) is subject to agreement between concerned Administrations.
+
+**9.3** Multicast services in PSPDN and FRPDN are defined in ITU-T Rec. X.6.
+
+## **10 User classes of service, categories of access**
+
+**10.1** PDTSs offer to users so-called "basic user facilities". Basic user facilities are defined by user classes of service and categories of access.
+
+**10.2** User class of service is a category of PDTS in which the DTE operation mode, data signalling rate, call control signalling rates and code structure (in start-stop mode) are standardized.
+
+**10.3** User classes of service within the national PDTS is a national matter; user classes of service provided internationally are subject to agreement between the concerned Administrations. Nationally and internationally provided user classes of service may not coincide.
+
+**10.4** Category of access identifies the method by which the DTE gains access to a specific data transmission service. Direct or port access may be used. Usage of category of access is a national matter.
+
+**10.5** User classes of service and categories of access are outlined in ITU-T Rec. X.1.
+
+## **11 Optional user facilities**
+
+**11.1** Optional user facilities modify or complement basic user facilities. An optional user facility cannot be offered to a user as a stand-alone facility; it may be offered only in association with a basic user facility.
+
+**11.2** Optional user facilities for international PDTS are outlined in ITU-T Rec. X.2.
+
+**11.3** Concerned Administrations should procure internationally all the essential user facilities (see ITU-T Rec. X.2). Additional optional user facilities may or may not be provided.
+
+## **12 Data compression and security**
+
+Techniques for data compression and security may be provided in FRPDNs according to ITU-T Rec. X.272.
+
+## **13 Administrative arrangements for international Closed User Groups**
+
+**13.1** Closed User Group (CUG) facilities (example of an optional user facility) enable users for access to/from users having one or more of these facilities. The basic facility enables customers to belong to one or more CUGs and to make/receive calls only to/from other customers in the same CUG.
+
+**13.2** Concerned Administrations should observe the following when managing CUGs:
+
+- For each international CUG, a "responsible subscriber" has to be nominated. Such a nomination is subject to agreement between all participants of the CUG.
+- The Administration of the country hosting the "responsible subscriber" (coordinating Administration) shall act as a controlling and coordinating Administration for that CUG and shall carry out discussions with the responsible subscriber about changes to the CUG. The coordinating Administration shall also be responsible for the allocation of international CUG numbers.
+
+**13.3** Administrative arrangements for international CUGs are defined in ITU-T Rec. X.180.
+
+## **14 Administrative arrangements for international Permanent Virtual Circuits**
+
+**14.1** The international application of the Permanent Virtual Circuit (PVC) service is subject to agreement between the concerned Administrations. Subscribers to be connected to an international PVC shall nominate a "responsible subscriber". That subscriber is responsible for all organizational matters relating to the international PVC.
+
+**14.2** The Administration of the country hosting the responsible subscriber (source Administration) shall act as a controlling and coordinating Administration for that international PVC and shall carry out the discussions with the responsible subscriber about any changes to the international PVC.
+
+**14.3** Provisions of the international PVC are defined in ITU-T Rec. X.181.
+
+## **15 Charging principles**
+
+Charging principles for PDNs are defined in ITU-T D-series Recommendations.
+
+## **16 Duration of service**
+
+International PDTSS are, in principle, continuously available. Duration of the service should not be limited, unless this contravenes national law.
+
+## **17 Outages**
+
+**17.1** Administrations may temporarily withdraw the whole or part of the service from operation for the purpose of maintenance and enhancements necessary to ensure that the service is kept in a proper working condition.
+
+**17.2** Administrations shall endeavour to minimize the impact of such service withdrawals. It is the responsibility of an Administration planning to withdraw a service to notify other concerned Administrations. Aspects relating to network availability and service outages for PSPDNs and FRPDNs are covered in ITU-T Recs X.137 and X.147 respectively.
+
+## **18 Service calls**
+
+**18.1** Service telecommunications should be established among the interested Administrations to facilitate the exchange of information necessary to administer and maintain services, network management, accounting, handling of customer complaints, etc.
+
+**18.2** Administrations are encouraged to make service telecommunications free of charge.
+
+**18.3** Aspects of service telecommunications are laid down in ITU-T Rec. F.17.
+
+## **19 General provisions between Administrations**
+
+**19.1** The international PDTSS should be operated in the automatic mode.
+
+**19.2** Administrations should reach mutual agreement on the information needed to be exchanged to sustain the international PDTSS and facilities offered. Administrations are not obliged to offer internationally all facilities available nationally.
+
+**19.3** Administrations should reach mutual agreement on the upgrading, enhancement and expansion of the service. Each Administration should supply the concerned Administrations with a number of copies of its subscriber directories (see below).
+
+## **20 General provisions between Administration and customer**
+
+**20.1** The Administration should inform the customers about the data transmission services available internationally. This should include information on:
+
+- service offered, including user classes of service, categories of access, optional user facilities;
+- charges;
+- quality of service expected, including priority and service classes;
+- call progress signals, error messages, diagnostic codes and their meaning;
+- fault reporting procedures;
+- procedures for resolving disputes including billing disputes;
+- directory facilities;
+- other information relating to service problems.
+
+**20.2** Customers may select user classes of service, categories of access, optional user facilities, priority and service classes.
+
+**20.3** Administrations must assist customers with the changing capabilities of the services offered. Customer Help Facility should be established. The exact organization of Customer Help Facility is a national matter, but at least the following customer assistance should be offered:
+
+- availability of services;
+- information and notification on planned outages;
+- directory service.
+
+**20.4** The International Telecommunication Charge Card Service allows the holder of a telecommunication charge card to make use of a variety of services provided by the card acceptor (i.e., the public data network from which services are being obtained) and to have the charges billed to the customer's account by the card issuer. The scope of public data transmission services for which the card applies will be subject to agreements between the card issuer and card acceptor.
+
+This Recommendation specifically entails the use of a telecommunication charge card issued by an ROA in compliance with ITU-T Rec. E.116.
+
+The use of the International Telecommunication Charge Card Service in a public data network depends on agreements between the card acceptors and card issuers. Major items to be covered may include:
+
+- types of service for which cards may be used;
+- basis for settlement of service charges and surcharges;
+- prevention of fraudulent use of cards;
+- procedures for uncollectible and unbillable services.
+
+**20.5** Directory services available to the customers should be in accordance with national laws and regulations regarding the suitability of publication of the information and the form in which it is published. Directories may be issued in form of printed materials. Electronic directories are also recommended.
+
+**20.6** Printed directories for international use should be updated at least once a year. Customers may decide to be excluded from the directory. The page size should not be larger than an A4 format. The directory for international use should be set in roman letters. The number published shall be the one that the calling customer must transmit to obtain the called customer. The directory normally has to be written in a language used in the country; use of explanatory notes in whatever official ITU language is recommended.
+
+**20.7** Electronic directories should be accessed from a DTE of the data network providing the PDTS. Access from other DTEs is also encouraged. Principles of electronic directories for PDTSs (e.g., according ITU-T X.500-series Recommendations) are for further study.
+
+
+
+
+
+# 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                                              |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                |
+| 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 * 2 5 8 5 3 *](97fe9069356cc2a84e8e70673e405958_img.jpg)
+
+A barcode consisting of vertical black lines of varying widths. Below the barcode, the text "\* 2 5 8 5 3 \*" is printed.
+
+Barcode with the number \* 2 5 8 5 3 \*
\ No newline at end of file
diff --git a/marked/F/T-REC-F.64-198811-I_PDF-E/raw.md b/marked/F/T-REC-F.64-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..ca0258a06963dc241716093c9b3c002478dec9a7
--- /dev/null
+++ b/marked/F/T-REC-F.64-198811-I_PDF-E/raw.md
@@ -0,0 +1,297 @@
+
+
+![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**
+
+**F.64**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+# **OPERATIONS AND QUALITY OF SERVICE TELEGRAPH SERVICES** ---
+
+## **DETERMINATION OF THE NUMBER OF INTERNATIONAL TELEX CIRCUITS REQUIRED TO CARRY A GIVEN VOLUME OF TRAFFIC**
+
+**ITU-T Recommendation F.64**
+
+(Extract from the *Blue Book*)
+
+---
+
+### NOTES
+
+1 ITU-T Recommendation F.64 was published in Fascicle II.4 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.
+
+### Recommendation F.64
+
+## DETERMINATION OF THE NUMBER OF INTERNATIONAL TELEX CIRCUITS REQUIRED TO CARRY A GIVEN VOLUME OF TRAFFIC
+
+The CCITT,
+
+*considering*
+
+(a) that it is essential to provide an adequate number of circuits between two telex networks in order to provide the rapid service stipulated in Recommendation F.60;
+
+(b) that the use of tables for the determination of the number of circuits as a function of the traffic to be dealt with during the busy hour is an established practice in all Administrations, and is a convenient means of indicating a standard;
+
+(c) that international telex circuits may be selected either at manual positions, or via automatic switching equipment, particularly where subscriber-to-subscriber selection is employed between two networks;
+
+*unanimously declares*
+
+(1) that Administrations should use Tables 1/F.64 or 2/F.64 below, according to the system of selection employed (i.e. manual selection or automatic selection) in the international service;
+
+(2) Administrations should aim for full availability of circuits on intercontinental and ARQ radio routes operated with signalling in accordance with Recommendations U.1, U.11, U.12 and U.20. Where an Administration is unable to provide the full availability, it should provide an availability to achieve not less than 90% of the full availability capacity relative to the number of circuits on the route at a grade of service of one in 50.
+
+### 1 Introduction
+
+1.1 Table 1/F.64 shows values for manual traffic carried. If for the purpose of design (as distinct from the maintenance of rapid service) it is desired to obtain values for offered traffic in erlangs, these may be determined by adding the respective values of lost traffic to the figures for carried traffic in Table 1/F.64.
+
+1.2 Table 1/F.64 is directly applicable only to full-availability groups of circuits that are operated either wholly as bothway circuits, or wholly as unidirectional circuits.
+
+1.3 Tables 2/F.64 shows values for traffic offered in the automatic service and is directly applicable to full-availability groups and groups with availabilities between 10 and 50.
+
+Given the traffic offered (A) in erlangs and the availability (K), the number of circuits required to provide a loss probability (B) of 0.02 may be determined from Table 2/F.64. Groups of up to 200 circuits and availabilities of 10, 20, 30, 50 and N circuits (N circuits corresponding to full availability) are covered. The method of applying the table is shown in Figure 1/F.64.
+
+1.4 Where groups of circuits are divided into bothway and unidirectional components, the division and number of circuits in each component will be agreed between Administrations.
+
+TABLE 1/F.64
+
+#### Traffic capacity table for manually selected telex circuits (Note 1)
+
+| Number of circuits | Average intensity for traffic carried in the busy hour, expressed in erlangs, for a grade of service (probability of loss) of: |                  |                  |
+|--------------------|--------------------------------------------------------------------------------------------------------------------------------|------------------|------------------|
+|                    | 1 in 10 (Note 2)                                                                                                               | 1 in 30 (Note 3) | 1 in 50 (Note 3) |
+| <i>a</i>           | <i>b</i>                                                                                                                       | <i>c</i>         | <i>d</i>         |
+| 1                  | 0.2                                                                                                                            | 0.066            | 0.034            |
+| 2                  | 0.9                                                                                                                            | 0.43             | 0.33             |
+| 3                  | 1.5                                                                                                                            | 0.89             | 0.76             |
+| 4                  | 2.3                                                                                                                            | 1.49             | 1.29             |
+| 5                  | 3.2                                                                                                                            | 2.17             | 1.92             |
+| 6                  |                                                                                                                                | 2.92             | 2.67             |
+| 7                  |                                                                                                                                | 3.77             | 3.44             |
+| 8                  |                                                                                                                                | 4.66             | 4.25             |
+| 9                  |                                                                                                                                | 5.56             | 5.09             |
+| 10                 |                                                                                                                                | 6.47             | 5.93             |
+| 11                 |                                                                                                                                | 7.39             | 6.79             |
+| 12                 |                                                                                                                                | 8.31             | 7.67             |
+| 13                 |                                                                                                                                | 9.24             | 8.57             |
+| 14                 |                                                                                                                                | 10.2             | 9.48             |
+| 15                 |                                                                                                                                | 11.1             | 10.4             |
+| 16                 |                                                                                                                                | 12.1             | 11.3             |
+| 17                 |                                                                                                                                | 13.0             | 12.3             |
+| 18                 |                                                                                                                                | 13.9             | 13.2             |
+| 19                 |                                                                                                                                | 14.9             | 14.1             |
+| 20                 |                                                                                                                                | 15.9             | 15.0             |
+
+*Note 1* – Table 1/F.64 makes allowance for the manual operator to continue the search for a free line over the group of circuits concerned for a period of 30 seconds if all are engaged, after which the search is abandoned and the call suspended.
+
+*Note 2* – Column *b* of Table 1/F.64 will, in general, only be used in respect of small groups of circuits of considerable length, having due regard to the desire to provide a rapid service, as well as to economic considerations.
+
+*Note 3* – In all other cases the figures of column *c* shall be used in preference to those of column *d*.
+
+Image: Figure 1/F.64: An example for using Table 2/F.64. The diagram shows a grid with axes for Number of circuits (N) and Availability (K). Arrows indicate the flow from the axes to the corresponding values in the table.
+
+| K \ N      | 10    | <b>[K]</b> Availability              | 50    | N     |
+|------------|-------|--------------------------------------|-------|-------|
+| <b>[N]</b> |       |                                      |       |       |
+| 100        | 64.0  |                                      | 84.1  | 88.0  |
+| 102        | 65.3  |                                      | 85.9  | 89.9  |
+| 104        | 66.5  |                                      | 87.6  | 91.9  |
+| 106        | 67.8  |                                      | 89.4  | 93.8  |
+| <b>[N]</b> |       |                                      |       |       |
+| Circuits   |       | <b>[A]</b> Traffic offered (erlangs) |       |       |
+| 196        | 125.4 |                                      | 170.4 | 182.2 |
+| 198        | 126.7 |                                      | 172.2 | 184.2 |
+| 200        | 128.0 |                                      | 174.1 | 186.2 |
+
+FIGURE 1/F.64
+
+An example for using Table 2/F.64
+
+TABLE 2/F.64
+
+#### Traffic capacity table for automatic circuits
+
+| K  | 10    | 20   | 30   | 50   | ... N |
+|----|-------|------|------|------|-------|
+| N  | <hr/> |      |      |      |       |
+|    | A     |      |      |      |       |
+| 1  |       |      |      |      | 0.02  |
+| 2  |       |      |      |      | 0.22  |
+| 3  |       |      |      |      | 0.60  |
+| 4  |       |      |      |      | 1.09  |
+| 5  |       |      |      |      | 1.66  |
+| 6  |       |      |      |      | 2.28  |
+| 7  |       |      |      |      | 2.94  |
+| 8  |       |      |      |      | 3.63  |
+| 9  |       |      |      |      | 4.34  |
+| 10 | 5.08  |      |      |      | 5.08  |
+| 11 | 5.68  |      |      |      | 5.84  |
+| 12 | 6.29  |      |      |      | 6.61  |
+| 13 | 6.90  |      |      |      | 7.40  |
+| 14 | 7.52  |      |      |      | 8.20  |
+| 15 | 8.15  |      |      |      | 9.01  |
+| 16 | 8.77  |      |      |      | 9.83  |
+| 17 | 9.40  |      |      |      | 10.7  |
+| 18 | 10.0  |      |      |      | 11.5  |
+| 19 | 10.7  |      |      |      | 12.3  |
+| 20 | 11.3  | 13.2 |      |      | 13.2  |
+| 21 | 12.0  | 13.9 |      |      | 14.0  |
+| 22 | 12.6  | 14.7 |      |      | 14.9  |
+| 23 | 13.3  | 15.4 |      |      | 15.8  |
+| 24 | 13.9  | 16.2 |      |      | 16.6  |
+| 25 | 14.6  | 16.9 |      |      | 17.5  |
+| 26 | 15.2  | 17.7 |      |      | 18.4  |
+| 27 | 15.9  | 18.4 |      |      | 19.3  |
+| 28 | 16.5  | 19.2 |      |      | 20.2  |
+| 29 | 17.2  | 19.9 |      |      | 21.0  |
+| 30 | 17.8  | 20.7 | 21.9 |      | 21.9  |
+| 31 | 18.5  | 21.5 | 22.7 |      | 22.8  |
+| 32 | 19.2  | 22.2 | 23.5 |      | 23.7  |
+| 33 | 19.8  | 23.0 | 24.3 |      | 24.6  |
+| 34 | 20.5  | 23.8 | 25.1 |      | 25.5  |
+| 35 | 21.1  | 24.6 | 26.0 |      | 26.4  |
+| 36 | 21.8  | 25.3 | 26.8 |      | 27.3  |
+| 37 | 22.5  | 26.1 | 27.6 |      | 28.3  |
+| 38 | 23.1  | 26.9 | 28.4 |      | 29.2  |
+| 39 | 23.8  | 27.7 | 29.2 |      | 30.1  |
+| 40 | 24.4  | 28.4 | 30.0 |      | 31.0  |
+| 41 | 25.1  | 29.2 | 30.8 |      | 31.9  |
+| 42 | 25.8  | 30.0 | 31.7 |      | 32.8  |
+| 43 | 26.4  | 30.8 | 32.5 |      | 33.8  |
+| 44 | 27.1  | 31.6 | 33.3 |      | 34.7  |
+| 45 | 27.8  | 32.3 | 34.1 |      | 35.6  |
+| 46 | 28.4  | 33.1 | 34.9 |      | 36.5  |
+| 47 | 29.1  | 33.9 | 35.8 |      | 37.5  |
+| 48 | 29.8  | 34.7 | 36.6 |      | 38.4  |
+| 49 | 30.4  | 35.5 | 37.4 |      | 39.3  |
+| 50 | 31.1  | 36.3 | 38.2 | 40.3 | 40.3  |
+
+TABLE 2/F.64
+
+*(cont'd)*
+
+| K   |   | 10   | 20   | 30   | 50   | ... N |
+|-----|---|------|------|------|------|-------|
+| N   |   |      |      |      |      |       |
+|     | A |      |      |      |      |       |
+| 50  |   | 31.1 | 36.3 | 38.2 | 40.3 | 40.3  |
+| 51  |   | 31.8 | 37.1 | 39.1 | 41.1 | 41.2  |
+| 52  |   | 32.4 | 37.9 | 39.9 | 42.0 | 42.1  |
+| 53  |   | 33.1 | 38.7 | 40.7 | 42.8 | 43.1  |
+| 54  |   | 33.8 | 39.4 | 41.6 | 43.7 | 44.0  |
+| 55  |   | 34.4 | 40.2 | 42.4 | 44.6 | 44.9  |
+| 56  |   | 35.1 | 41.0 | 43.2 | 45.4 | 45.9  |
+| 57  |   | 35.7 | 41.8 | 44.1 | 46.3 | 46.8  |
+| 58  |   | 36.4 | 42.6 | 44.9 | 47.2 | 47.8  |
+| 59  |   | 37.1 | 43.4 | 45.7 | 48.0 | 48.7  |
+| 60  |   | 37.7 | 44.2 | 46.6 | 48.9 | 49.6  |
+| 61  |   | 38.4 | 45.0 | 47.4 | 49.8 | 50.6  |
+| 62  |   | 39.1 | 45.8 | 48.2 | 50.6 | 51.5  |
+| 63  |   | 39.7 | 46.6 | 49.1 | 51.5 | 52.5  |
+| 64  |   | 40.4 | 47.4 | 49.9 | 52.4 | 53.4  |
+| 65  |   | 41.0 | 48.2 | 50.8 | 53.3 | 54.4  |
+| 66  |   | 41.7 | 49.0 | 51.6 | 54.1 | 55.3  |
+| 67  |   | 42.4 | 49.8 | 52.4 | 55.0 | 56.3  |
+| 68  |   | 43.0 | 50.6 | 53.3 | 55.9 | 57.2  |
+| 69  |   | 43.7 | 51.4 | 54.1 | 56.7 | 58.2  |
+| 70  |   | 44.4 | 52.2 | 55.0 | 57.6 | 59.1  |
+| 71  |   | 45.0 | 53.0 | 55.8 | 58.5 | 60.1  |
+| 72  |   | 45.7 | 53.8 | 56.6 | 59.4 | 61.0  |
+| 73  |   | 46.3 | 54.6 | 57.5 | 60.2 | 62.0  |
+| 74  |   | 47.0 | 55.4 | 58.3 | 61.1 | 62.9  |
+| 75  |   | 47.6 | 56.2 | 59.2 | 62.0 | 63.9  |
+| 76  |   | 48.3 | 57.0 | 60.0 | 62.9 | 64.9  |
+| 77  |   | 49.0 | 57.8 | 60.9 | 63.8 | 65.8  |
+| 78  |   | 49.6 | 58.6 | 61.7 | 64.6 | 66.8  |
+| 79  |   | 50.3 | 59.4 | 62.6 | 65.5 | 67.7  |
+| 80  |   | 50.9 | 60.2 | 63.4 | 66.4 | 68.7  |
+| 81  |   | 51.6 | 61.0 | 64.3 | 67.3 | 69.6  |
+| 82  |   | 52.2 | 61.8 | 65.1 | 68.2 | 70.6  |
+| 83  |   | 52.9 | 62.6 | 66.0 | 69.0 | 71.6  |
+| 84  |   | 53.6 | 63.4 | 66.8 | 69.9 | 72.5  |
+| 85  |   | 54.2 | 64.2 | 67.6 | 70.8 | 73.5  |
+| 86  |   | 54.9 | 65.0 | 68.5 | 71.7 | 74.5  |
+| 87  |   | 55.5 | 65.9 | 69.3 | 72.6 | 75.4  |
+| 88  |   | 56.2 | 66.7 | 70.2 | 73.5 | 76.4  |
+| 89  |   | 56.8 | 67.5 | 71.0 | 74.3 | 77.3  |
+| 90  |   | 57.5 | 68.3 | 71.9 | 75.2 | 78.3  |
+| 91  |   | 58.1 | 69.1 | 72.7 | 76.1 | 79.3  |
+| 92  |   | 58.8 | 69.9 | 73.6 | 77.0 | 80.2  |
+| 93  |   | 59.4 | 70.7 | 74.4 | 77.9 | 81.2  |
+| 94  |   | 60.1 | 71.5 | 75.3 | 78.8 | 82.2  |
+| 95  |   | 60.7 | 72.3 | 76.2 | 79.7 | 83.1  |
+| 96  |   | 61.4 | 73.1 | 77.0 | 80.5 | 84.1  |
+| 97  |   | 62.0 | 73.9 | 77.9 | 81.4 | 85.1  |
+| 98  |   | 62.7 | 74.7 | 78.7 | 82.3 | 86.0  |
+| 99  |   | 63.3 | 75.5 | 79.6 | 83.2 | 87.0  |
+| 100 |   | 64.0 | 76.3 | 80.4 | 84.1 | 88.0  |
+
+TABLE 2/F.64
+
+*(concluded)*
+
+| K   |   | 10    | 20    | 30    | 50    | ... N |
+|-----|---|-------|-------|-------|-------|-------|
+| N   |   |       |       |       |       |       |
+| 100 | A | 64.0  | 76.3  | 80.4  | 84.1  | 88.0  |
+| 102 |   | 65.3  | 77.9  | 82.1  | 85.9  | 89.9  |
+| 104 |   | 66.5  | 79.6  | 83.8  | 87.6  | 91.9  |
+| 106 |   | 67.8  | 81.2  | 85.5  | 89.4  | 93.8  |
+| 108 |   | 69.1  | 82.8  | 87.3  | 91.2  | 95.7  |
+| 110 |   | 70.4  | 84.4  | 89.0  | 93.0  | 97.7  |
+| 112 |   | 71.7  | 86.0  | 90.7  | 94.8  | 99.6  |
+| 114 |   | 72.9  | 87.6  | 92.4  | 96.6  | 101.6 |
+| 116 |   | 74.2  | 89.3  | 94.1  | 98.3  | 103.5 |
+| 118 |   | 75.5  | 90.9  | 95.8  | 100.1 | 105.5 |
+| 120 |   | 76.8  | 92.5  | 97.5  | 101.9 | 107.4 |
+| 122 |   | 78.1  | 94.1  | 99.3  | 103.7 | 109.4 |
+| 124 |   | 79.3  | 95.7  | 101.0 | 105.5 | 111.3 |
+| 126 |   | 80.6  | 97.3  | 102.7 | 107.3 | 113.3 |
+| 128 |   | 81.9  | 99.0  | 104.4 | 109.1 | 115.2 |
+| 130 |   | 83.2  | 100.6 | 106.1 | 110.9 | 117.2 |
+| 132 |   | 84.5  | 102.2 | 107.9 | 112.7 | 119.1 |
+| 134 |   | 85.7  | 103.8 | 109.6 | 114.5 | 121.1 |
+| 136 |   | 87.0  | 105.4 | 111.3 | 116.3 | 123.1 |
+| 138 |   | 88.3  | 107.0 | 113.0 | 118.1 | 125.0 |
+| 140 |   | 89.6  | 108.7 | 114.7 | 119.9 | 127.0 |
+| 142 |   | 90.8  | 110.3 | 116.5 | 121.7 | 128.9 |
+| 144 |   | 92.1  | 111.9 | 118.2 | 123.5 | 130.9 |
+| 146 |   | 93.4  | 113.5 | 119.9 | 125.3 | 132.9 |
+| 148 |   | 94.7  | 115.1 | 121.6 | 127.1 | 134.8 |
+| 150 |   | 96.0  | 116.7 | 123.4 | 128.9 | 136.8 |
+| 152 |   | 97.2  | 118.3 | 125.1 | 130.7 | 138.8 |
+| 154 |   | 98.5  | 120.0 | 126.8 | 132.5 | 140.7 |
+| 156 |   | 99.8  | 121.6 | 128.5 | 134.3 | 142.7 |
+| 158 |   | 101.1 | 123.2 | 130.3 | 136.1 | 144.7 |
+| 160 |   | 102.4 | 124.8 | 132.0 | 137.9 | 146.6 |
+| 162 |   | 103.6 | 126.4 | 133.7 | 139.7 | 148.6 |
+| 164 |   | 104.9 | 128.0 | 135.4 | 141.5 | 150.6 |
+| 166 |   | 106.2 | 129.6 | 137.2 | 143.3 | 152.6 |
+| 168 |   | 107.5 | 131.2 | 138.9 | 145.1 | 154.5 |
+| 170 |   | 108.8 | 132.9 | 140.6 | 146.9 | 156.5 |
+| 172 |   | 110.0 | 134.5 | 142.3 | 148.7 | 158.5 |
+| 174 |   | 111.3 | 136.1 | 144.1 | 150.5 | 160.4 |
+| 176 |   | 112.6 | 137.7 | 145.8 | 152.3 | 162.4 |
+| 178 |   | 113.9 | 139.3 | 147.5 | 154.1 | 164.4 |
+| 180 |   | 115.2 | 140.9 | 149.2 | 155.9 | 166.4 |
+| 182 |   | 116.4 | 142.5 | 151.0 | 157.7 | 168.3 |
+| 184 |   | 117.7 | 144.1 | 152.7 | 159.6 | 170.3 |
+| 186 |   | 119.0 | 145.7 | 154.4 | 161.4 | 172.3 |
+| 188 |   | 120.3 | 147.3 | 156.2 | 163.2 | 174.3 |
+| 190 |   | 121.6 | 148.9 | 157.9 | 165.0 | 176.3 |
+| 192 |   | 122.8 | 150.6 | 159.6 | 166.8 | 178.2 |
+| 194 |   | 124.1 | 152.2 | 161.3 | 168.6 | 180.2 |
+| 196 |   | 125.4 | 153.8 | 163.1 | 170.4 | 182.2 |
+| 198 |   | 126.7 | 155.4 | 164.8 | 172.2 | 184.2 |
+| 200 |   | 128.0 | 157.0 | 166.5 | 174.1 | 186.2 |
\ No newline at end of file
diff --git a/marked/F/T-REC-F.65-198811-I_PDF-E/raw.md b/marked/F/T-REC-F.65-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..36821c03946baf4373d4d598daa8da2979f0fd6d
--- /dev/null
+++ b/marked/F/T-REC-F.65-198811-I_PDF-E/raw.md
@@ -0,0 +1,53 @@
+
+
+![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**
+
+**F.65**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**OPERATIONS AND QUALITY OF SERVICE  
+TELEGRAPH SERVICES**
+
+---
+
+**TIME - TO - ANSWER BY OPERATORS  
+AT INTERNATIONAL TELEX POSITIONS**
+
+**ITU-T Recommendation F.65**
+
+(Extract from the *Blue Book*)
+
+---
+
+# NOTES
+
+1          ITU-T Recommendation F.65 was published in Fascicle II.4 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.
+
+# **Recommendation F.65**
+
+## **TIME-TO-ANSWER BY OPERATORS AT INTERNATIONAL TELEX POSITIONS**
+
+The CCITT,
+
+*considering*
+
+- (a) that a rapid answer to calling signals by the operators at incoming international telex positions is essential to ensure a rapid telex service;
+- (b) that a rapid answer is a very important factor in the efficient utilization of international telex circuits;
+- (c) that the time-to-answer has a direct effect on the costs of staffing and of switchboard provision;
+
+*unanimously declares*
+
+that, wherever possible, Administrations should give priority to the answering of incoming calling signals at international terminal exchanges and should endeavour to ensure that 95% of calls are answered within 30 seconds.
\ No newline at end of file
diff --git a/marked/F/T-REC-F.69-199406-I_PDF-E/raw.md b/marked/F/T-REC-F.69-199406-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..f08d717c5b24e8b1a80731ee96bc75fb24c8e948
--- /dev/null
+++ b/marked/F/T-REC-F.69-199406-I_PDF-E/raw.md
@@ -0,0 +1,219 @@
+
+
+![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**
+
+**F.69**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+(06/94)
+
+# **OPERATIONS AND QUALITY OF SERVICE TELEGRAPH SERVICES** ---
+
+# **THE INTERNATIONAL TELEX SERVICE – SERVICE AND OPERATIONAL PROVISIONS OF TELEX DESTINATION CODES AND TELEX NETWORK IDENTIFICATION CODES**
+
+**ITU-T Recommendation F.69**
+
+(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 F.69 was revised by ITU-T Study Group 1 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 1st of June 1994.
+
+---
+
+## NOTE
+
+In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## CONTENTS
+
+|                                                                   | <i>Page</i> |
+|-------------------------------------------------------------------|-------------|
+| 1 Introduction .....                                              | 1           |
+| 2 Scope .....                                                     | 1           |
+| 3 List of associated Recommendations .....                        | 1           |
+| 4 Definitions.....                                                | 1           |
+| 5 Functions of the Telex Destination Code .....                   | 1           |
+| 6 General principles of structure of telex destination code ..... | 2           |
+| 7 Structure of the telex network identification code .....        | 3           |
+| 8 Procedures for allocation of codes .....                        | 4           |
+
+# **SUMMARY**
+
+The interconnection of the networks of the countries and recognized operating agencies participating in the international telex service requires the development of a standardized mechanism for the routing of calls between subscribers in a transparent manner. This is achieved through the use of a telex destination code which is used for routing purposes in international exchanges. Telex destination codes may also be used within national telex networks or at international gateway exchanges for recording call details for billing and accounting purposes, or sometimes for other purposes such as segregating particular types of traffic. Furthermore, the service requirement enabling the identification of the called subscriber and thereby giving assurance of correct connection is achieved by the inclusion of a telex network identification code in the answerbacks of subscribers of the international telex service in addition to the subscribers national telex number.
+
+This Recommendation describes the procedures to be followed in the allocation of telex destination codes and telex network identification codes. The means of promulgation publication, and date of entry into effect of code allocations are also identified.
+
+## **THE INTERNATIONAL TELEX SERVICE – SERVICE AND OPERATIONAL PROVISIONS OF TELEX DESTINATION CODES AND TELEX NETWORK IDENTIFICATION CODES**
+
+*(revised, 1994)*
+
+## **1 Introduction**
+
+The interconnection of the networks of the countries and recognized operating agencies (ROA) participating in the international telex service requires the development of a standardized mechanism for the routing of calls between subscribers in a transparent manner. This is achieved through the use of a telex destination code which is used for routing purposes in international exchanges. Telex destination codes may also be used within national telex networks or at international gateway exchanges for recording call details for billing and accounting purposes, or sometimes for other purposes such as segregating particular types of traffic. Furthermore, the service requirement enabling the identification of the called subscriber and thereby giving assurance of correct connection is achieved by the inclusion of a telex network identification code in the answerbacks of subscribers of the international telex service in addition to the subscribers national telex number.
+
+## **2 Scope**
+
+This Recommendation describes the procedures to be followed in the allocation of telex destination codes and telex network identification codes. The means of promulgation, publication, and date of entry into effect of code allocations are also identified.
+
+## **3 List of associated Recommendations**
+
+This Recommendation should be read in association with the following Recommendations:
+
+- Recommendation F.31 *Telegram Retransmission System.*
+- Recommendation F.59 *General Characteristics of the International Telex Service.*
+- Recommendation F.60 *Operational Provisions for the International Telex Service.*
+- Recommendation F.68 *Establishment of the automatic Intercontinental Telex Network.*
+- Recommendation F.96 *Telegram Destination Indicators.*
+- Recommendation R.79 *Automatic Tests of Transmission Quality on Telegraph Circuits between Switching Centres.*
+- Recommendation U.7 *Numbering Schemes for Automatic Switching networks.*
+- Recommendation U.11 *Telex and Gentex Signalling on Intercontinental Circuits used for Intercontinental Automatic Transit Traffic (Type C Signalling).*
+- Recommendation U.74 *Extraction of Telex Selection Information from a Calling Telex Answerback.*
+
+## **4 Definitions**
+
+The terms “telex destination code” and “telex network identification code” are defined in Recommendation F.68.
+
+## **5 Functions of the Telex Destination Code**
+
+**5.1** There are many Recommendations dealing with the international telex service, several of them being many years in existence. In all cases, reference to “telex” needs to be understood to refer exclusively to the international telex service which is described in Recommendations F.59 and F.60.
+
+**5.2** Recommendation F.60 states that “The networks of the countries participating in the international telex service shall, as far as possible, be directly connected and shall thereby constitute the international telex network”. The telex destination codes referenced in this Recommendation are, therefore, primarily used for routing purposes within international telex exchanges within the originating network and any transit network, but see also clause 1. In accordance with U-Series signalling Recommendations, the destination network may also request the receipt of the complete international telex number (which includes the telex destination code) on terminating traffic.
+
+**5.3** Any revision to an existing code allocation requires adjustments to be made normally not in the network which has requested the change/allocation but in all other networks which comprise the international telex network. Accordingly, this procedure results in telex destination codes being of relevance primarily to originating and transit networks, and only rarely to destination networks. As the international telex service is now recognised as a mature service having evolved over many years, and some networks may use spare codes for purposes other than as stated herein, caution needs to be exercised in the future allocation of codes for emerging new networks.
+
+**5.4** One of the unique characteristics of the international telex service is the ability to assure connection to the addressed party through the automatic return of the called subscriber answerback sequence on call set-up. The format of the answerback is specified in Recommendation F.60. This standardized structure is also used to determine the (recall) telex address by an analysis of the answerback of the calling telex subscriber in accordance with the rules laid down in Recommendation U.74 when messages are being forwarded either via a store and forward unit or in some interworking cases. Therefore, there is a firm requirement for a telex network identification code to be always associated with a telex destination code in order to fully characterize the network of any telex subscriber.
+
+**5.5** For operational reasons, unallocated telex destination codes are sometimes used by ROAs for both national and international applications, the latter being on the basis of bilateral agreement or multilateral agreement(s). While the use of such codes internationally is discouraged except in the case of temporary expediency, such use, as well as ROAs' national applications, should be taken into account when selecting new codes for allocation.
+
+## **6 General principles of structure of telex destination code**
+
+**6.1** The U-Series signalling Recommendations permit a maximum of 12 selection digits to be signalled across an international link. Accordingly, in establishing the initial plan for telex destination codes, it was necessary to decide whether these codes should always comprise three digits, or whether they could be made up of two or three digits.
+
+**6.2** The advantages of uniform three-digit codes were seen to be:
+
+- i) by allocating the same size code to all countries, difficulties would not arise as to the relative importance of the various countries with regard to the international telex service;
+- ii) uniform codes afford some simplification of the design of exchanges;
+- iii) for the European system a uniform three-digit system could be readily compiled by adding a uniform digit to the range of two-digit codes already in use at the time by a number of European Administrations.
+
+**6.3** The advantages of a mixed two or three-digit arrangement were seen to be:
+
+- i) the use of shorter length codes reduced the risk of errors by calling subscribers;
+- ii) the storage capacity of registers could be kept to a minimum by allocating shorter codes to systems having long subscribers' numbers;
+- iii) the holding time of circuits could be kept to a minimum;
+- iv) the maximum number of digits to be examined for routing and other purposes could be kept to a minimum by allocating shorter codes to systems in which the first two digits of a subscriber's number have to be examined in accordance with Recommendation U.7. Similarly, where a country had more than one international exchange the allocation of a shorter code would enable the routing of traffic to be controlled by the examination of a minimum number of digits.
+
+**6.4** A mixed environment of two-digit and three-digit destination codes was seen to have the most advantages, and was adopted as the basis for this Recommendation.
+
+**6.5** The following principles apply to the allocation of the first digit:
+
+0 – not to be used as first digit;
+
+1 – see 6.8 and 6.9;
+
+2 – North America and adjacent areas;
+
+3 – South America and adjacent areas;
+
+4 – Europe and adjacent areas;
+
+5 – Europe and adjacent areas and maritime-satellite services;
+
+6 – Europe and adjacent areas;
+
+7 – Pacific and adjacent areas;
+
+8 – Middle East, Far East and adjacent areas;
+
+9 – Africa, Near East and adjacent areas.
+
+## NOTES
+
+1 The geographical boundaries of the continents have not been rigidly followed to permit maximum flexibility within the code system.
+
+2 In relations using Type C signalling (see Recommendation U.11) code 000 may be used for retest signalling purposes in accordance with Recommendation R.79.
+
+3 In case of the assignment of codes to a maritime mobile-satellite system, a three-digit code could exceptionally be assigned to each ocean area of the satellite system.
+
+**6.6** The number of two-digit codes available is rather restricted. It is undesirable to allocate these to serve individual networks in countries where several networks exist but do not have a co-ordinated internal numbering scheme;
+
+**6.7** It is not advisable to allocate all possible two-digit codes, so as to maintain some flexibility to allow future development to be taken into account. Accordingly, all new allocations will be of three digits in order to maximise the use of the available spare telex destination codes.
+
+**6.8** The first digit 1 was initially reserved for special services, which led to its uncoordinated use in a variety of national and international applications in different networks. In all future networks and as soon as practicable in existing networks, it should be possible to allocate the 1 series for destination codes for international purposes.
+
+**6.9** A block of ten destination codes (160-169) has been set aside to cover the particular needs for access to maritime mobile HF and MF radiotelex services. The choice of code or codes for these applications is left to individual ROAs for use by their own subscribers and/or (after suitable bilateral arrangements have been reached) by subscribers of other ROAs for transit calls.
+
+NOTE – It is recognized that some ROAs use various codes in the 160-169 series at present for national and international applications.
+
+## **7 Structure of the telex network identification code**
+
+**7.1** The telex network identification code (TNIC) consists of either one or two letters in accordance with Recommendation F.68.
+
+**7.2** In the case of two-letter TNICs, the code should be the same as the first two characters of the destination indicator of their country or network for the telegram retransmission system in accordance with Recommendation F.31, as noted in Recommendations F.68 and F.96.
+
+**7.3** In principle, no further single-letter TNICs should be allocated.
+
+## 8 Procedures for allocation of codes
+
+8.1 The Administration of a ROA wishing to take part in the international automatic telex service should apply to the Director of the TSB for the assignment of an *available* three-digit destination code and a two-letter TNIC. In its request, it may indicate the available three-digit code preferred. Where the numbering scheme for the appropriate region is exhausted, a code from a proximate region may be allocated.
+
+8.2 In all cases, such requests should be referred to the Chairman of Study Group 1 for guidance on technical and operational issues, taking account of possible future requirements. The procedures to be followed are given in Figure 1.
+
+8.3 It is the responsibility of the TSB:
+
+- to carry out the necessary discussion with the applicant Administration;
+- to ensure that the Chairman of Study Group 1 is satisfied that any technical and operational requirements have been covered before final allocation of the relevant destination and network identification codes.
+
+8.4 Additions and changes that are accepted will be published in the ITU *Operational Bulletin*. They will become effective on the first day of the third month following publication.
+
+8.5 The list of allocated and spare telex destination codes, including the corresponding telex network identification codes, will be published periodically in the *Operational Bulletin*.
+
+![Flowchart for the allocation and publication of telex destination codes and telex network identification codes. The process starts with a request received in TSB, followed by discussions, passing details to Study Group 1, seeking guidance from expert groups, identifying issues, replying to TSB, reaching an agreement, informing the applicant, and finally publishing the updated list. There are feedback loops to discussions at various stages.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg)
+
+```
+
+graph TD
+    A[Request received in TSB for allocation/change of code(s)] --> B[Details passed by TSB to Study Group 1 Chairman a)]
+    B --> C[Study Group 1 Chairman a) seeks guidance from Study Group 1 expert group(s) on proposal b)]
+    C --> D{Have any technical/ operational issues been identified by expert group?}
+    D -- Yes --> E[Study Group 1 Chairman a) reverts to TSB with guidance on resolution of any identified operational or technical issues]
+    D -- No --> F[Study Group 1 Chairman a) replies accordingly to the TSB]
+    E --> G[TSB/Applicant discussions]
+    G --> H{Agreement?}
+    H -- Yes --> I[TSB informs applicant and announces code allocation in Operational Bulletin]
+    H -- No --> J[Relevant Study Group 1 expert group to inform the next meeting of Study Group 1 (Working Party) on work]
+    I --> K[TSB to publish updated list of allocated and spare codes periodically in Operational Bulletin]
+    J --> A
+    G --> A
+    E -.->|Normally 15 working days|> G
+  
+```
+
+T0103390-94/d01
+
+a) Or Chairman's delegated representative.  
+ b) To be done in consultation with expert group nominated by Study Group 1 for such tasks.
+
+Flowchart for the allocation and publication of telex destination codes and telex network identification codes. The process starts with a request received in TSB, followed by discussions, passing details to Study Group 1, seeking guidance from expert groups, identifying issues, replying to TSB, reaching an agreement, informing the applicant, and finally publishing the updated list. There are feedback loops to discussions at various stages.
+
+FIGURE 1/F.69  
+**Scheme for the allocation and publication of telex destination codes and telex network identification codes**
\ No newline at end of file
diff --git a/marked/F/T-REC-F.70-198811-I_PDF-E/raw.md b/marked/F/T-REC-F.70-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..9547ce9f51154dabe0e447fde83b3013c1fe0fe6
--- /dev/null
+++ b/marked/F/T-REC-F.70-198811-I_PDF-E/raw.md
@@ -0,0 +1,176 @@
+
+
+![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. A lightning bolt symbol is positioned to the right of the globe.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**F.70**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**OPERATIONS AND QUALITY OF SERVICE  
+TELEGRAPH SERVICES**
+
+---
+
+**EVALUATING THE QUALITY OF  
+THE INTERNATIONAL TELEX SERVICE**
+
+**ITU-T Recommendation F.70**
+
+(Extract from the *Blue Book*)
+
+---
+
+# NOTES
+
+1 ITU-T Recommendation F.70 was published in Fascicle II.4 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.
+
+## **EVALUATING THE QUALITY OF THE INTERNATIONAL TELEX SERVICE**
+
+## **1 Introduction**
+
+1.1 The Quality of Service is a measure of the perceived performance of the telex network. The perception of the service performance varies between that of the calling subscriber, the origin Administration, the destination Administration and the called subscriber. For example, national network difficulties in reaching the origin international exchange will usually be noticed only by the calling subscriber. However, if the origin or destination Administration automatically retries to reach the wanted subscriber following an unsuccessful call attempt, these reattempts are not seen by that part of the network that precedes it. Conversely, a called subscriber is unaware of the number of times that call attempts are being made to his number, if his machine is busy or out of order.
+
+1.2 The main criteria of service performance from the users' viewpoint are:
+
+- a) the ease in establishing a connection;
+- b) the retention of the established connection;
+- c) the satisfactory transmission quality;
+- d) the integrity of billing.
+
+1.3 Where possible, the critical areas of service performance should be measured in a manner that provides both origin and destination Administrations with comparable data. For example, arrangements to ensure concurrency of the periods of observation by the two Administrations involved in each given relation is of great importance. These measurement should, if possible, show the performance as perceived in the originating network and in the destination network.
+
+1.4 Where a subscriber number is found to be "hard to reach" (HTR), then, if possible, this number should be separately identified to allow the origin and destination Administrations mutually to analyze the cause of the problem.
+
+## **2 Method of measuring quality of service**
+
+2.1 Administrations should draw up a programme for telex observations designed to evaluate the quality of the service given to subscribers in their automatic and semi-automatic international services.
+
+2.2 Where Administrations have equipment that automatically records details of calls, this information may be used to compile details of network performance.
+
+2.3 In order to provide compatible data between the origin and destination networks, where possible, Administrations should measure the perceived performance in the origin network (e.g., at the entry point to the international gateway exchange if applicable) in addition to the performance at the international interface looking towards the destination network.
+
+## **3 Analysis of results**
+
+3.1 Administrations should exchange data on a bilaterally agreed basis, commensurate with their operational requirements and, in principle, at least once every six months.
+
+3.2 The results may then be analyzed as shown below (see also Table 1/F.70):
+
+- a) Check effective rate to the destination compared with the average to all destinations.
+- b) Check the current rate versus the performance as measured in the past.
+- c) Check the performance with results obtained by other Administrations to the same destination.
+- d) If the performance has suddenly degraded, perform a detailed analysis where possible, monitor circuit group performance and analyze the performance on a destination code basis. The degradation on a circuit group could be caused by a faulty circuit which, when seized, fails to successfully switch a call.
+
+3.3 Administrations should investigate any HTR report (greater than 50 unsuccessful attempts to one number within a day could be defined as being HTR).
+
+3.3.1 Where national regulatory arrangements allow, Administrations should check that automatic terminal equipment complies with Recommendation U.40. Where poor terminal operating procedures exist, customers should be referred to the guidelines annexed to Recommendation F.60.
+
+3.3.2 The destination Administration should proceed as follows:
+
+3.3.2.1 **OCC** : the called subscriber should be advised that his telex machine is very busy and that extra machines (or terminations) may be necessary.
+
+3.3.2.2 **DER** : is this still a working service? If not, the service signal should be changed to **NP** or **NCH**. If the service is still working, the customer should be asked if the machine is being disabled, e.g., by switching off the power. If a computer interface is being used, is the telex machine being correctly switched in when the computer is taken off-line?
+
+3.3.2.3 **NP/NCH** : consult the origin Administration and ask it to take the matter up with the calling subscriber.
+
+3.3.2.4 Answerback failure:
+
+- a) Where answerback failure occurs, the reasons should be investigated by the destination Administration.
+- b) Where a calling automatic terminal fails to interpret the answerback correctly, the reasons should be investigated by the origin Administration.
+
+3.4 Where possible, Administrations should also investigate and report as necessary when frequent cases of clearing from the destination network occurs after charging commences, since a likely cause in such cases is a transmission fault during the text transmission.
+
+3.5 Regular discussion should take place with other Administrations, on a bilateral basis, with a view towards improving the mutual network performance.
+
+## 4 Explanation of terms used in Table 1/F.70
+
+### 4.1 *Effective call*
+
+An effective call is defined as a call for which a charge was made or that was successfully completed to a service position. Where possible, measurements should be corrected to take account of any calls for which the charge has been adjusted.
+
+### 4.2 *Ineffective call*
+
+Any calls or call attempts that did not result in an effective call.
+
+### 4.3 *Chargeable time*
+
+Duration between the call-connected signal and recognition of the clearing of a call, less 5 to 7 seconds (see Recommendation F.61).
+
+### 4.4 *Call set-up time*
+
+The time between circuit seizure and the receipt of a call-connected or service signal. This time will not be the same on the national and the international sides of the exchange.
+
+### 4.5 *PTS failure*
+
+The proceed-to-select signal has not been received within a nominated period after a call signal has been sent to the next exchange.
+
+### 4.6 *Service signals*
+
+(ABS, DER, NA, NC, NCH, NP, OCC) are defined in Recommendation F.60, § 4.1.
+
+TABLE 1/F.70
+
+#### **International telex service observations**
+
+ADMINISTRATION:
+
+TRAFFIC OUTGOING FROM: TO
+
+PERIOD OF OBSERVATION: UTC TO UTC
+
+ROUTE BUSY HOUR: UTC TO UTC
+
+| Number of observations                                  |                                          | Point of observation     |                          |                          |                          |
+|---------------------------------------------------------|------------------------------------------|--------------------------|--------------------------|--------------------------|--------------------------|
+| National side                                           | International side<br>(Includes retries) | National side            |                          | International side       |                          |
+|                                                         |                                          | Average this destination | Average all destinations | Average this destination | Average all destinations |
+| Effective calls                                         | Percentage                               |                          |                          |                          |                          |
+|                                                         | Chargeable time (min. sec.)              |                          |                          |                          |                          |
+|                                                         | Call setup time (min. sec.)              |                          |                          |                          |                          |
+| Ineffective calls                                       | Percentage                               |                          |                          |                          |                          |
+|                                                         | Call setup time (min. sec.)              |                          |                          |                          |                          |
+| Analysis of ineffective calls (Expressed as percentage) |                                          |                          |                          |                          |                          |
+| Outgoing circuit selected                               | PTS Failure                              |                          |                          |                          |                          |
+|                                                         | OCC Signal received                      |                          |                          |                          |                          |
+|                                                         | DER Signal received                      |                          |                          |                          |                          |
+|                                                         | NP Signal received                       |                          |                          |                          |                          |
+|                                                         | ABS Signal received                      |                          |                          |                          |                          |
+|                                                         | NC Signal from distant network           |                          |                          |                          |                          |
+|                                                         | NA Signal received                       |                          |                          |                          |                          |
+|                                                         | NCH Signal received                      |                          |                          |                          |                          |
+|                                                         | Other service signals                    |                          |                          |                          |                          |
+|                                                         | No answer back after call connect        |                          |                          |                          |                          |
+|                                                         | Clear by caller before call connect      |                          |                          |                          |                          |
+|                                                         | No call connect (time out)               |                          |                          |                          |                          |
+|                                                         | Cut off during call setup                |                          |                          |                          |                          |
+|                                                         | Wrong number reached                     |                          |                          |                          |                          |
+|                                                         | Others (specify)                         |                          |                          |                          |                          |
+| No outgoing circuit selected                            | Incomplete number                        |                          |                          |                          |                          |
+|                                                         | Clearing before complete number          |                          |                          |                          |                          |
+|                                                         | Lack of outgoing circuits                |                          |                          |                          |                          |
+
+THE FOLLOWING NUMBERS WERE IDENTIFIED AS HARD TO REACH TELEX SUBSCRIBERS:  
+ SERVICE SIGNAL RECEIVED ON INTERNATIONAL SIDE
+
+| Called number | OCC | DER | ABS | NS | Others (specify) |
+|---------------|-----|-----|-----|----|------------------|
+|               |     |     |     |    |                  |
+|               |     |     |     |    |                  |
+|               |     |     |     |    |                  |
+|               |     |     |     |    |                  |
+|               |     |     |     |    |                  |
+|               |     |     |     |    |                  |
+|               |     |     |     |    |                  |
+
+*Note – An explanation of terms is given in § 4.*
\ No newline at end of file
diff --git a/marked/F/T-REC-F.700-200011-I_PDF-E/raw.md b/marked/F/T-REC-F.700-200011-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..55fd91fd2ee898142c4468d1fb6bfd51faf375ed
--- /dev/null
+++ b/marked/F/T-REC-F.700-200011-I_PDF-E/raw.md
@@ -0,0 +1,1938 @@
+
+
+![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
+
+**F.700**
+
+(11/2000)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Audiovisual services
+
+---
+
+**Framework Recommendation for multimedia  
+services**
+
+ITU-T Recommendation F.700
+
+(Formerly CCITT Recommendation)
+
+---
+
+# ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| <b>TELEGRAPH SERVICE</b>                                        |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| <b>MOBILE SERVICE</b>                                           |                    |
+| Mobile services and multdestination satellite services          | F.110–F.159        |
+| <b>TELEMATIC SERVICES</b>                                       |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| <b>MESSAGE HANDLING SERVICES</b>                                | F.400–F.499        |
+| <b>DIRECTORY SERVICES</b>                                       | F.500–F.549        |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | F.600–F.699        |
+| <b>AUDIOVISUAL SERVICES</b>                                     | <b>F.700–F.799</b> |
+| <b>ISDN SERVICES</b>                                            | F.800–F.849        |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | F.850–F.899        |
+| <b>HUMAN FACTORS</b>                                            | F.900–F.999        |
+
+*For further details, please refer to ITU-T List of Recommendations.*
+
+# **FRAMEWORK RECOMMENDATION FOR MULTIMEDIA SERVICES**
+
+## **Summary**
+
+This Recommendation provides a methodology for constructing multimedia services which is timely and responsive to the needs of both the End-User and Service Provider. This methodology is based on a modular approach using a set of network independent building blocks or other communications capabilities being developed within ITU-T.
+
+The methodology is intended for use in developing a series of General Service Recommendations which combine the required modular elements in order to build generic services.
+
+###### **Source**
+
+ITU-T Recommendation F.700 was revised by ITU-T Study Group 16 (2001-2004) and was approved under the WTSC Resolution No. 1 procedure on 17 November 2000.
+
+## FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the 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.
+
+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
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The 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, the 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 2000
+
+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 the ITU.
+
+## CONTENTS
+
+###### Page
+
+|                                               |                                                                                     |    |
+|-----------------------------------------------|-------------------------------------------------------------------------------------|----|
+| 1                                             | Introduction.....                                                                   | 1  |
+| 1.1                                           | Scope.....                                                                          | 1  |
+| 1.2                                           | Definitions .....                                                                   | 1  |
+| 1.3                                           | Multimedia service development methodology .....                                    | 2  |
+| 1.3.1                                         | Communication capabilities .....                                                    | 3  |
+| 1.3.2                                         | Multimedia service recommendations .....                                            | 3  |
+| 1.4                                           | Multimedia services reference model .....                                           | 3  |
+| 1.5                                           | Functional model of the service platform .....                                      | 4  |
+| 1.6                                           | Application of the reference and functional models to the service description ..... | 4  |
+| 2                                             | Communication Capabilities.....                                                     | 5  |
+| 2.1                                           | Communication tasks.....                                                            | 6  |
+| 2.1.1                                         | Method of describing communication tasks .....                                      | 6  |
+| 2.1.2                                         | Attribute considerations.....                                                       | 6  |
+| 2.1.3                                         | Provisional list of communication tasks .....                                       | 7  |
+| 2.1.4                                         | Description of generic communication tasks.....                                     | 8  |
+| 2.2                                           | Media components .....                                                              | 12 |
+| 2.3                                           | Middleware service elements.....                                                    | 13 |
+| 2.4                                           | Supplementary services.....                                                         | 14 |
+| 3                                             | Service description process.....                                                    | 15 |
+| 3.1                                           | Framework .....                                                                     | 15 |
+| 3.2                                           | Service profiles .....                                                              | 18 |
+| 3.3                                           | Quality of service .....                                                            | 18 |
+| 3.4                                           | Generic service descriptions .....                                                  | 18 |
+| 3.5                                           | Derivation of specific services.....                                                | 19 |
+| 3.6                                           | Elaboration of service description .....                                            | 19 |
+| 3.7                                           | Intercommunication among service categories .....                                   | 20 |
+| Annex A – Media components descriptions ..... |                                                                                     | 20 |
+| A.1                                           | Media component audio.....                                                          | 20 |
+| A.1.1                                         | Definition.....                                                                     | 20 |
+| A.1.2                                         | Description.....                                                                    | 20 |
+| A.1.3                                         | Quality aspects .....                                                               | 21 |
+| A.1.4                                         | Intercommunication .....                                                            | 21 |
+| A.2                                           | Media component video.....                                                          | 22 |
+| A.2.1                                         | Definition.....                                                                     | 22 |
+| A.2.2                                         | Description.....                                                                    | 22 |
+
+|                                                  | <b>Page</b> |
+|--------------------------------------------------|-------------|
+| A.2.3 Quality aspects .....                      | 23          |
+| A.2.4 Intercommunication .....                   | 24          |
+| A.2.5 Description of the static aspects .....    | 24          |
+| A.2.6 Description of the dynamic aspects .....   | 24          |
+| A.3 Media component text .....                   | 24          |
+| A.3.1 Definition .....                           | 24          |
+| A.3.2 Description .....                          | 24          |
+| A.3.3 Quality Aspects .....                      | 25          |
+| A.3.4 Intercommunication .....                   | 25          |
+| A.4 Media component graphics .....               | 25          |
+| A.4.1 Definition .....                           | 25          |
+| A.4.2 Description .....                          | 26          |
+| A.4.3 Quality aspects .....                      | 26          |
+| A.4.4 Intercommunication .....                   | 26          |
+| A.4.5 Description of static aspects .....        | 26          |
+| A.4.6 Description of dynamic aspects .....       | 26          |
+| A.5 Media component still pictures .....         | 26          |
+| A.5.1 Definition .....                           | 26          |
+| A.5.2 Description .....                          | 26          |
+| A.5.3 Quality aspects .....                      | 27          |
+| A.5.4 Intercommunication .....                   | 27          |
+| A.5.5 Description of static aspects .....        | 27          |
+| A.5.6 Description of dynamic aspects .....       | 27          |
+| A.6 Media component data .....                   | 27          |
+| A.6.1 Definition .....                           | 27          |
+| A.6.2 Description .....                          | 28          |
+| A.6.3 Quality aspects .....                      | 28          |
+| A.6.4 Intercommunication .....                   | 28          |
+| A.6.5 Description of static aspects .....        | 28          |
+| A.6.6 Description of dynamic aspects .....       | 28          |
+| Annex B – Communication tasks descriptions ..... | 29          |
+| B.1 Communication task conversing .....          | 29          |
+| B.1.1 Definition .....                           | 29          |
+| B.1.2 Description .....                          | 29          |
+| B.1.3 Quality aspects .....                      | 29          |
+| B.1.4 Intercommunication .....                   | 29          |
+| B.1.5 Static aspects .....                       | 30          |
+| B.2 Communication task conferencing .....        | 30          |
+| B.2.1 Definition .....                           | 30          |
+
+|                                                                  | <b>Page</b> |
+|------------------------------------------------------------------|-------------|
+| B.2.2 Description.....                                           | 30          |
+| B.2.3 Quality aspects.....                                       | 31          |
+| B.2.4 Intercommunication.....                                    | 31          |
+| B.2.5 Description of the static aspects .....                    | 32          |
+| B.3 Communication task distributing.....                         | 32          |
+| B.3.1 Definition.....                                            | 32          |
+| B.3.2 Description.....                                           | 32          |
+| B.3.3 Quality aspects.....                                       | 33          |
+| B.3.4 Intercommunication.....                                    | 33          |
+| B.3.5 Static aspects.....                                        | 33          |
+| B.4 Communication task sending.....                              | 33          |
+| B.4.1 Definition.....                                            | 33          |
+| B.4.2 Description.....                                           | 34          |
+| B.4.3 Quality aspects.....                                       | 34          |
+| B.4.4 Intercommunication.....                                    | 34          |
+| B.4.5 Static aspects.....                                        | 34          |
+| B.5 Communication task receiving .....                           | 35          |
+| B.5.1 Definition.....                                            | 35          |
+| B.5.2 Description.....                                           | 35          |
+| B.5.3 Quality aspects.....                                       | 35          |
+| B.5.4 Intercommunication.....                                    | 36          |
+| B.5.5 Static aspects.....                                        | 36          |
+| B.6 Communication task collecting .....                          | 36          |
+| B.6.1 Definition.....                                            | 36          |
+| B.6.2 Description.....                                           | 36          |
+| B.6.3 Quality aspects.....                                       | 37          |
+| B.6.4 Intercommunication.....                                    | 37          |
+| B.6.5 Static aspects.....                                        | 37          |
+| Annex C – Middleware service elements descriptions .....         | 38          |
+| C.1 Middleware service element <i>Conversation Control</i> ..... | 38          |
+| C.1.1 Definition.....                                            | 38          |
+| C.1.2 Description.....                                           | 38          |
+| C.1.3 Control functions .....                                    | 38          |
+| C.1.4 Implementation.....                                        | 38          |
+| C.2 Middleware service element <i>Conference Control</i> .....   | 38          |
+| C.2.1 Definition.....                                            | 38          |
+| C.2.2 Description.....                                           | 38          |
+| C.2.3 Control functions .....                                    | 39          |
+| C.2.4 Implementation .....                                       | 41          |
+
+|                                                                          | <b>Page</b> |
+|--------------------------------------------------------------------------|-------------|
+| Annex D – Glossary .....                                                 | 42          |
+| Appendix I – Multimedia medical consultation.....                        | 44          |
+| I.1    Prose description.....                                            | 44          |
+| I.2    Application scenario .....                                        | 44          |
+| I.2.1    Full multimedia support capability.....                         | 44          |
+| I.2.2    Restricted multimedia support capability .....                  | 45          |
+| I.3    Implementation notes.....                                         | 46          |
+| I.3.1    Related applications.....                                       | 46          |
+| I.3.2    Associated applications .....                                   | 46          |
+| I.3.3    Security/privacy .....                                          | 46          |
+| I.3.4    Service flexibility.....                                        | 46          |
+| I.3.5    Performance trade-offs .....                                    | 46          |
+| Appendix II – Harmonization of multimedia services and applications..... | 47          |
+
+# **FRAMEWORK RECOMMENDATION FOR MULTIMEDIA SERVICES**
+
+*(revised in 2000)*
+
+# **1 Introduction**
+
+## **1.1 Scope**
+
+This Recommendation provides a methodology for constructing multimedia services which is timely and responsive to the needs of both the End-User and Service Provider. This methodology is based on a modular approach using a set of network independent building blocks or other communications capabilities being developed within ITU-T.
+
+The methodology described in this Recommendation is intended for use in developing a series of General Service Recommendations which combine the required modular elements in order to build generic services (e.g. for Multimedia Conferencing Service, Multimedia Distribution Service, etc.). These Recommendations provide functional descriptions of services that are independent from the networks that support them. Because different networks may have different performance and bring different constraints, a related series of network specific Recommendations describe the way the services are adapted on each particular network.
+
+The service descriptions are not intended to impose a particular and detailed way of offering the services, but to provide the minimum set of functions and performance parameters necessary for achieving a sufficient quality of service and for insuring communication between users served by different service providers. Manufacturers and service providers are free to offer additional functions and enhanced quality of service.
+
+## **1.2 Definitions**
+
+Information in curly brackets indicates source of definitions when other than F.700. Additional information is contained in Annex D.
+
+**1.2.1 application:** An application is a set of activities performed to respond to the needs of the users in a given situation for purposes such as business, education, personal communication or entertainment. It implies software and hardware utilization could be performed in a fully or partially automatic way and could be accessed locally or remotely. In the last case, it requests use of telecommunication services.
+
+**1.2.2 communication task:** A communication task is a functional entity of a multimedia service that performs communication features. It handles a set of media components in a synchronized way in order to convey and control complex information types.
+
+**1.2.3 media component:** Media components are those parts of a communication service which provide the communication capabilities related to a single information type. They provide the necessary functions for user information handling, such as information capture, presentation, storage, transfer and post-processing. As the information types differ considerably in their basic elements, the specific functions also differ from information type to information type.
+
+**1.2.4 medium (Plural Media) {MHEG}:** A means by which information is perceived, expressed, stored or transmitted. The term is to be avoided in its stand-alone form. To be unambiguous it should only be used in expressions such as perception medium, representation medium, presentation medium, storage medium, transmission medium, etc.
+
+**1.2.5 multimedia {MHEG}:** The term multimedia is an adjective and must be attached to a noun which provides the context. For example, multimedia service or application, multimedia terminal, multimedia network and multimedia presentation.
+
+**1.2.6 multimedia application:** A multimedia application is an application that requests the handling of two or more representation media (information types) simultaneously which constitute a common information space. Examples are cooperative document editing, long distance meetings, remote surveillance, medical document remote analysis and teletraining.
+
+**1.2.7 multimedia representation {MHEG}:** The property of handling several types of representation media.
+
+**1.2.8 multimedia service:** Multimedia services are telecommunication services that handle two or more types of media in a synchronized way from the user's point of view. A multimedia service may involve multiple parties, multiple connections, and the addition or deletion of resources and users within a single communication session.
+
+**1.2.9 presentation {MHEG}:** A state which is ready for human perception.
+
+**1.2.10 presentation medium:** The means for presenting information to the user, commonly known as an output device, such as a screen, printer or loudspeaker.
+
+NOTE – Presentation is not to be confused with the OSI Presentation Layer.
+
+**1.2.11 representation:** The process of reproducing information for human perception.
+
+**1.2.12 representation medium:** The type of the information in its coded form, ready for transmission. Examples of representation media are:
+
+| <i>Representation media</i> | <i>Possible coded forms</i>                                                         |
+|-----------------------------|-------------------------------------------------------------------------------------|
+| characters or text          | ASCII, EBCDIC                                                                       |
+| graphics                    | CEPT, NAPLPS or CAPTAIN videotex, CGM                                               |
+| audio                       | TSS, G.711, MIDI, future MPEG/Audio standard                                        |
+| still picture               | Fax Group 3, Group 4, JPEG standard                                                 |
+| moving picture (video)      | ITU-T Recommendation H.261, H.262, H.263 or Sequence<br>ITU-R Recommendation BT.601 |
+
+NOTE – The representation medium is defined independently of the direction of transmission (i.e. to or from the user or between equipment). Each representation medium may be used both for input or output. For example, character representation may be used both for text display and for text input from a keyboard; graphics may be used both for graphic display and graphic input; audio or pictures may be used both for reproduction and for capture.
+
+**1.2.13 telecommunication service:** A telecommunication service is a set of telecommunication capabilities that works in a complementary and cooperative way in order to let users perform applications.
+
+## **1.3 Multimedia service development methodology**
+
+Multimedia services may be seen from different points of view.
+
+From the end user's point of view, a multimedia telecommunication service is the combination of telecommunication capabilities required to support a particular multimedia application. Such a service is usually considered to be independent of the network(s) providing these capabilities.
+
+From the Network Provider's point of view, a multimedia telecommunication service is a combination or set of combinations of two or more media components (e.g. audio, video, graphics, etc.) within a particular network environment in such a way as to produce a new telecommunication
+
+service. This telecommunication service is considered to be fully dependent on the specific capabilities of the networks utilized.
+
+Additionally, the user wishes to have the same type of presentation and mode of operation for all services needed to support similar applications; and the Service or Network provider desires to have common protocols and interfaces to accommodate interoperability for a variety of technical implementations.
+
+### 1.3.1 Communication capabilities
+
+Communication capabilities are the fundamental sets of communication tasks, media components and integration mechanisms required to develop the complex spectrum of multimedia services. Control and processing functions are also needed for assembling these capabilities into a service and adapting the signals.
+
+### 1.3.2 Multimedia service recommendations
+
+The description of a multimedia service can be accomplished from the basic communication capabilities by utilizing the procedures specified in clause 2. The methodology for describing these generic service architectures in a series of general ITU-T service Recommendations is described in clause 3. This process can best be summarized by a modular reference model organized in four levels as discussed in 1.4. Appropriate modular elements from the communication plane and the control plane, as shown in 1.5, are tied together to build various services.
+
+## 1.4 Multimedia services reference model
+
+Following a modular approach the reference model is organized in four levels. Figure 1 shows the application level on top of the three service platform levels.
+
+### 1) *Application level*
+
+The level at which the essential functional characteristics of an end-user application are described from the end user's point of view irrespective of the underlying technical aspects of the services or particular network solution.
+
+### 2) *Service level*
+
+The level at which the basic set of communication services or support tools required to satisfy the functional requirements of the application layer are identified. The overall service principles (for performance, quality of service, security, charging, intercommunication) are defined and described.
+
+A service is built up by combining communication tasks and organizing their interaction. The service level may contain a description of how to find where end-users and terminals are located.
+
+### 3) *Communication task level*
+
+The level at which the specific communication tasks required to build the services are defined and described. A communication task is a functional entity of a multimedia service which performs its communication features. It handles a set of media components in a synchronized way, in order to convey and control complex information types.
+
+### 4) *Media component level*
+
+The level at which the multimedia aspects of the services are made apparent through the identification and description of the individual (monomedia) components related to a single information type, such as audio, video, etc.
+
+![Figure 1/F.700 – Multimedia services reference model. The diagram shows a funnel-shaped structure representing the reference model. At the top, a box labeled 'Multimedia applications' has five arrows pointing down into the top of the funnel. The funnel is divided into three horizontal sections labeled from top to bottom: 'Application level', 'Service level', and 'Communication task level'. Below the funnel, there is a fourth section labeled 'Media component level'. To the left of the funnel, a vertical double-headed arrow spans from the top to the bottom, labeled 'Service platform'. The text 'T0104790-99' is at the bottom right of the funnel.](d4af765160d04ecef538e5066006dc77_img.jpg)
+
+Figure 1/F.700 – Multimedia services reference model. The diagram shows a funnel-shaped structure representing the reference model. At the top, a box labeled 'Multimedia applications' has five arrows pointing down into the top of the funnel. The funnel is divided into three horizontal sections labeled from top to bottom: 'Application level', 'Service level', and 'Communication task level'. Below the funnel, there is a fourth section labeled 'Media component level'. To the left of the funnel, a vertical double-headed arrow spans from the top to the bottom, labeled 'Service platform'. The text 'T0104790-99' is at the bottom right of the funnel.
+
+**Figure 1/F.700 – Multimedia services reference model**
+
+## 1.5 Functional model of the service platform
+
+In addition to the modular elements in these levels, control and processing functions are required for operating the service. These functions may be considered as lying in a different plane that interacts with all three levels of the communication plane (service level, communication task level, media component level). They are also organized in modular entities, the Middleware Service Elements (MSEs). See Figure 2.
+
+![](1439cb942d9e363bbb3161b5540dd8c6_img.jpg)
+
+**Service platform**
+
+| <b>Communication plane</b> | <b>Control and processing plane</b> |
+|----------------------------|-------------------------------------|
+| services                   | Middleware service elements         |
+| communication tasks        |                                     |
+| media components           |                                     |
+
+**Figure 2/F.700 – Functional model of the service platform**
+
+## 1.6 Application of the reference and functional models to the service description
+
+Services call upon tasks for acting on the various media components, in order to handle them and combine them in specific ways appropriate for the application. The functions required by a service are distributed between the 3 levels according to the following principles. The relationship between the services, the communication tasks and the media components is illustrated in Figure 3 of clause 2:
+
+- at the service level, the general functions related to the call and to the type of service;
+- at the communication task level, the functions related to the configuration, the time aspects, the linking of media components, e.g. transfer, storage, multipoint aspects, switching or multiplexing signals;
+
+- at the media component level, the functions related to each independent medium, such as capture, coding, presentation, quality aspects.
+
+The service platform also uses Middleware service elements that control the various levels in the communication plane or perform appropriate processing of the transmitted information. These MSEs may thus interact with a specific level (e.g. with the service level for call establishment, charging, security; with the communication task level for procedures, control of data switching or data combining processes, chair control, facility control; with media component level for transcoding, filtering), or they may interact with two levels or even possibly with all levels (e.g. for intercommunication).
+
+# 2 Communication Capabilities
+
+The multimedia services reference model (Figure 1) shows the applications on top of the service platform. It further indicates that the service platform can be decomposed into three levels: the service level describing the overall aspects, the communication task level describing the communication related aspects, and the media component level dealing with the user information handling (multimedia) aspects. Each of these levels has different aspects including static, dynamic and control. This Recommendation currently concentrates on the static aspects. The dynamic aspects are for further study, unless explicitly defined in this Recommendation in particular in the MSEs.
+
+From the end-user point of view, the communication tasks and the media components form the basic set of communication capabilities from which all multimedia telecommunication services can be constructed.
+
+Figure 3 shows the hierarchy of the service platform as well as the relations among the communication tasks and the media components.
+
+![A hierarchical diagram showing the relationship between a generic multimedia service, communication tasks, and media components. At the top is 'Generic multimedia service'. Below it are 'Communication Task A' (solid box) and 'Communication Task B' (dashed box). Task A is connected to 'Media component 1' and 'Media component 2' (both solid ovals) by solid lines. Task B is connected to 'Media component 3' and 'Media component 4' (both dashed ovals) by dashed lines. There are also dashed lines from Task A to Media component 3 and from Task B to Media component 2. A legend at the bottom left shows a solid line for 'Mandatory' and a dashed line for 'Optional'. A small code 'T0104810-99' is at the bottom right of the diagram.](ddc7460821484f1ae2835c67955c554c_img.jpg)
+
+```
+graph TD; GMS[Generic multimedia service] -- Mandatory --> CTA[Communication Task A]; GMS -.-> CTB[Communication Task B]; CTA -- Mandatory --> MC1((Media component 1)); CTA -- Mandatory --> MC2((Media component 2)); CTA -.-> MC3((Media component 3)); CTB -.-> MC3; CTB -.-> MC2; CTB -- Mandatory --> MC4((Media component 4));
+```
+
+Legend:  
+—— Mandatory  
+- - - - Optional
+
+T0104810-99
+
+A hierarchical diagram showing the relationship between a generic multimedia service, communication tasks, and media components. At the top is 'Generic multimedia service'. Below it are 'Communication Task A' (solid box) and 'Communication Task B' (dashed box). Task A is connected to 'Media component 1' and 'Media component 2' (both solid ovals) by solid lines. Task B is connected to 'Media component 3' and 'Media component 4' (both dashed ovals) by dashed lines. There are also dashed lines from Task A to Media component 3 and from Task B to Media component 2. A legend at the bottom left shows a solid line for 'Mandatory' and a dashed line for 'Optional'. A small code 'T0104810-99' is at the bottom right of the diagram.
+
+**Figure 3/F.700 – Application of the reference model to the description of a generic multimedia service**
+
+## 2.1 Communication tasks
+
+Starting from the users' requirements in a top-down approach, a multimedia service can first be decomposed into a set of communication tasks, each of them being, separately or not, manipulated by the user and/or the service provider. Conversely, in a bottom-up approach starting from the media components, a communication task can be viewed as a means of bringing together the media components that are related to each other for the purpose of the service.
+
+### 2.1.1 Method of describing communication tasks
+
+The static properties of a communication task are described using attributes and values. The following attributes and possible values have been identified (other attributes are for further study). See Table 1.
+
+**Table 1/F.700 – Communication task attributes**
+
+| Attributes                     | Possible values                                                                                                                                                                                                                                                                                                                                                                                                  |
+|--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Communication configuration    | Point-point/point-multipoint/<br>multipoint-point/multipoint-multipoint                                                                                                                                                                                                                                                                                                                                          |
+| Symmetry of information flow   | Unidirectional/bidirectional-symmetric/bidirectional-asymmetric                                                                                                                                                                                                                                                                                                                                                  |
+| Transmission control entity    | Source/sink/source and sink/third party                                                                                                                                                                                                                                                                                                                                                                          |
+| Communication delay            | Real-time<br>Near-real-time<br>Non-real-time<br>Specified time                                                                                                                                                                                                                                                                                                                                                   |
+| Mandatory media components     | Audio/video/text/still picture/graphics/data                                                                                                                                                                                                                                                                                                                                                                     |
+| Optional media components      | Audio/video/text/still picture/graphics/data/<br>none                                                                                                                                                                                                                                                                                                                                                            |
+| Media component interrelations | 1) Synchronization between:<br>a) audio and video (lip synchronism, location related synchronism);<br>b) audio and text (voice synthesis);<br>c) text and video/still picture/graphics (subtitles synchronized with images);<br>d) graphics and audio.<br>2) Symmetry between media components of the same type to allow for bidirectionality.<br>3) Conversion between information types (or media components). |
+| Time continuity                | Isochronous/non-isochronous                                                                                                                                                                                                                                                                                                                                                                                      |
+
+### 2.1.2 Attribute considerations
+
+Some attributes are described hereafter.
+
+#### 2.1.2.1 Time aspects
+
+The time aspects are described by two attributes: communication delay and time continuity. See Table 2.
+
+The communication delay may have four possible values:
+
+- real-time, i.e. a fraction of a second; this applies for instance to a conversation, or to some video games where user actions have to show immediately on the screen;
+- near-real-time, i.e. a few seconds; this applies for instance to retrieval services where the user is waiting for an answer from the system; the acceptable delay depends upon the complexity of the request and the length of the answer;
+- non-real-time; this would apply to the storage of information, for instance to archiving or to the storage of a message, where the action can be done within any reasonable but non-critical delay;
+- specified time, i.e. at a future exactly defined time or during a future period of time; this could apply for instance to some types of near video on demand, where the user could ask in advance for a film to be sent to him at some future given time, or to a retrieval service where, for a complex request that would take some time for the research or the handling of data, the system would call back later at a given time; it could also apply to messages sent during the night period when the tariff would be lower; similarly, a non-urgent message requiring some human intervention at the receiving end could be sent at any time during office hours.
+
+The time continuity has the attribute values "isochronous" or "non-isochronous." Isochronous transmission is necessary if the user terminal equipment has no buffering capabilities, or if the capturing device does not tolerate interruptions or variations in transmission speed or does not have a large enough storage capacity.
+
+**Table 2/F.700 – Table characterizing the relationship between communication delay and time continuity**
+
+| Communication delay                                                                 | Service examples                     |                               |
+|-------------------------------------------------------------------------------------|--------------------------------------|-------------------------------|
+|                                                                                     | Isochronous                          | Non-isochronous               |
+| Real-time                                                                           | Conversation                         | N/A                           |
+| Near-real-time                                                                      | On-line audiovisual retrieval (Note) | On-line data retrieval (Note) |
+| Non-real-time                                                                       | Near video on demand                 | Data messaging                |
+| Specified time                                                                      | Audiovisual messaging (Note)         | Audiovisual messaging (Note)  |
+| NOTE – Isochronicity depends on the terminal device storage and capture capacities. |                                      |                               |
+
+#### 2.1.2.2 Transmission control entity
+
+User information is always transmitted from the source(s) to the sink(s). Usually, one of the users acting as source or sink will control the information transfer, i.e. start and stop it. However, some applications may require a third party to initiate the information transmission.
+
+### 2.1.3 Provisional list of communication tasks
+
+Communication tasks may be derived by combining the attributes "communication configuration", "symmetry of information flow", and "transmission control entity". Six combinations are identified in Table 3 as meaningful. Communication tasks may be further distinguished by other attributes such as time aspects. Others may also be meaningful (e.g. tasks using third party control).
+
+**Table 3/F.700 – Provisional list of communication tasks**
+
+| Communication configuration | Communication tasks for three types of information flow |                                  |                                |
+|-----------------------------|---------------------------------------------------------|----------------------------------|--------------------------------|
+|                             | Bidirectional                                           | Unidirectional source controlled | Unidirectional sink controlled |
+| Point-to-point              | Conversing                                              | Sending                          | Receiving                      |
+| Point-to-multipoint         |                                                         | Distributing                     |                                |
+| Multipoint-to-point         |                                                         |                                  | Collecting                     |
+| Multipoint-to-multipoint    | Conferencing                                            |                                  |                                |
+
+### 2.1.4 Description of generic communication tasks
+
+Brief prose descriptions and the descriptions of the static aspects of the six generic communication tasks are presented here for illustration of the concept. These generic communication tasks include the complete set of functionalities (superset), without any of the restrictions that may occur when the service is offered to customers on a specific network.
+
+Detailed descriptions are presented in Annex B.
+
+Figure 4 is the key to the symbols in the figures in this subclause:
+
+![Figure 4/F.700 – Key to following figures. It shows three symbols: a circle labeled 'user (sink or source)', a square labeled 'transmission control entity', and an arrow labeled 'arrows indicate the flow of information'. Below the symbols is the code T0104820-99.](41a438d7e4adc17c3a4005e7c9500091_img.jpg)
+
+Figure 4/F.700 – Key to following figures. It shows three symbols: a circle labeled 'user (sink or source)', a square labeled 'transmission control entity', and an arrow labeled 'arrows indicate the flow of information'. Below the symbols is the code T0104820-99.
+
+**Figure 4/F.700 – Key to following figures**
+
+#### 2.1.4.1 Generic communication task conversing
+
+###### Prose description
+
+The generic communication task conversing provides for point-to-point real-time (isochronous) exchange of information between two users. The users may be humans or machines. The information may be monomedium as well as multimedia. See Figure 5.
+
+![Figure 5/F.700 – Generic task conversing. It shows two squares, each containing a circle, representing users. A double-headed arrow connects the two squares, indicating bidirectional information flow. Below the diagram is the code T0104830-99.](96b0240f56d14453b5da05ec30fd5c6e_img.jpg)
+
+Figure 5/F.700 – Generic task conversing. It shows two squares, each containing a circle, representing users. A double-headed arrow connects the two squares, indicating bidirectional information flow. Below the diagram is the code T0104830-99.
+
+**Figure 5/F.700 – Generic task conversing**
+
+###### Attributes
+
+###### Values
+
+|                               |                                         |
+|-------------------------------|-----------------------------------------|
+| Communication configuration:  | point-to-point                          |
+| Symmetry of information flow: | bidirectional                           |
+| Transmission control entity:  | source and sink                         |
+| Mandatory media components:   | all are possible, and an option is none |
+
+- Optional media components: all are possible, and an option is none
+- Communication delay: real-time
+- Time continuity: isochronous
+- Media component interrelations:
+- symmetry between media components of the same type to allow for bidirectionality;
+  - synchronization between:
+    - audio and video (lip synchronism, location related synchronism);
+    - audio and text (voice synthesis);
+    - text and video/picture/graphics (subtitles synchronized with images).
+
+#### 2.1.4.2 Generic communication task conferencing
+
+##### Prose description
+
+The generic communication task conferencing provides for multipoint real-time exchange of information among multiple users. The users may be humans or machines. The information may be monomedium as well as multimedia. See Figure 6.
+
+![Diagram showing three nodes arranged in a triangle, connected by bidirectional arrows, representing a generic task conferencing setup. The nodes are represented by circles inside squares. The bottom right node is labeled T0104840-99.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg)
+
+```
+
+graph TD
+    A(( )) --> B(( ))
+    B --> A
+    B --> C(( ))
+    C --> B
+    C --> A
+    A --> C
+    style A fill:#fff,stroke:#000
+    style B fill:#fff,stroke:#000
+    style C fill:#fff,stroke:#000
+    subgraph T0104840-99
+    C
+    end
+  
+```
+
+Diagram showing three nodes arranged in a triangle, connected by bidirectional arrows, representing a generic task conferencing setup. The nodes are represented by circles inside squares. The bottom right node is labeled T0104840-99.
+
+Figure 6/F.700 – Generic task conferencing
+
+##### Attributes
+
+###### Values
+
+- |                                 |                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Communication configuration:    | multipoint-to-multipoint                                                                                                                                                                                                                                                                                                           |
+| Symmetry of information flow:   | bidirectional                                                                                                                                                                                                                                                                                                                      |
+| Transmission control entity:    | source and sink                                                                                                                                                                                                                                                                                                                    |
+| Mandatory media components:     | all are possible, and an option is none                                                                                                                                                                                                                                                                                            |
+| Optional media components:      | all are possible, and an option is none                                                                                                                                                                                                                                                                                            |
+| Communication delay:            | real-time                                                                                                                                                                                                                                                                                                                          |
+| Time continuity:                | isochronous                                                                                                                                                                                                                                                                                                                        |
+| Media component interrelations: |                                                                                                                                                                                                                                                                                                                                    |
+| –                               | symmetry between media components of the same type to allow for bidirectionality;                                                                                                                                                                                                                                                  |
+| –                               | synchronization between: <ul style="list-style-type: none"> <li>• audio and video (lip synchronism, location related synchronism);</li> <li>• audio and text (voice synthesis);</li> <li>• text and video/picture/graphics (subtitles synchronized with images);</li> <li>• synchronization between audio and graphics.</li> </ul> |
+
+#### 2.1.4.3 Generic communication task sending
+
+##### Prose description
+
+The generic communication task sending provides for point-to-point real-time and non-real-time transfer of information from one user to another with the information source being the controlling entity. The users may be humans or machines. The information may be monomedium as well as multimedia. See Figure 7.
+
+![Diagram of generic task sending showing a square source connected to a single circular destination labeled T0104850-99.](4356776ca004ecba5d599667a155d7d4_img.jpg)
+
+A diagram showing a square on the left connected by a horizontal arrow pointing to a circle on the right. Below the circle is the text 'T0104850-99'.
+
+Diagram of generic task sending showing a square source connected to a single circular destination labeled T0104850-99.
+
+Figure 7/F.700 – Generic task sending
+
+##### Attributes
+
+###### Values
+
+|                                 |                                         |
+|---------------------------------|-----------------------------------------|
+| Communication configuration:    | point-to-point                          |
+| Symmetry of information flow:   | unidirectional                          |
+| Transmission control entity:    | source                                  |
+| Mandatory media components:     | all are possible, and an option is none |
+| Optional media components:      | all are possible, and an option is none |
+| Media component interrelations: | synchronization is possible             |
+| Communication delay:            | all are possible                        |
+| Time continuity:                | all are possible                        |
+
+#### 2.1.4.4 Generic communication task distributing
+
+##### Prose description
+
+The generic communication task distributing provides for the transfer of information from one user to (more than one) other users with the information source being the controlling entity. The users may be humans or machines. The information may be monomedium as well as multimedia. See Figure 8.
+
+![Diagram of generic task distributing showing a square source connected to three circular destinations, with the bottom one labeled T0104860-99.](e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg)
+
+A diagram showing a square on the left with three arrows pointing to three circles on the right, arranged vertically. Below the bottom circle is the text 'T0104860-99'.
+
+Diagram of generic task distributing showing a square source connected to three circular destinations, with the bottom one labeled T0104860-99.
+
+Figure 8/F.700 – Generic task distributing
+
+| <b>Attributes</b>               | <b>Values</b>                           |
+|---------------------------------|-----------------------------------------|
+| Communication configuration:    | point-to-multipoint                     |
+| Symmetry of information flow:   | unidirectional                          |
+| Transmission control entity:    | source                                  |
+| Mandatory media components:     | all are possible, and an option is none |
+| Optional media components:      | all are possible, and an option is none |
+| Media component interrelations: | synchronization is possible             |
+| Communication delay:            | all are possible                        |
+| Time continuity:                | all are possible                        |
+
+#### 2.1.4.5 Generic communication task receiving
+
+##### Prose description
+
+The generic communication task receiving provides for point-to-point transfer of information from one user to another user with the information sink being the controlling entity. The users may be humans or machines. The information may be monomedium as well as multimedia. See Figure 9.
+
+![Diagram of generic task receiving showing a square (sink) receiving information from a circle (source).](10781f43062bf3e9601a1e086710556c_img.jpg)
+
+The diagram shows a square on the left and a circle on the right. A horizontal arrow points from the circle to the square, indicating the direction of information flow. Below the circle is the text 'T0104870-99'.
+
+Diagram of generic task receiving showing a square (sink) receiving information from a circle (source).
+
+**Figure 9/F.700 – Generic task receiving**
+
+| <b>Attributes</b>               | <b>Values</b>                           |
+|---------------------------------|-----------------------------------------|
+| Communication configuration:    | point-to-point                          |
+| Symmetry of information flow:   | unidirectional                          |
+| Transmission control entity:    | sink                                    |
+| Mandatory media components:     | all are possible, and an option is none |
+| Optional media components:      | all are possible, and an option is none |
+| Media component interrelations: | synchronization is possible             |
+| Communication delay:            | all are possible                        |
+| Time continuity:                | all are possible                        |
+
+#### 2.1.4.6 Generic communication task collecting
+
+##### Prose description
+
+The generic communication task collecting provides for the transfer of information from (more than one) user to another with the information sink being the controlling entity. The users may be humans or machines. The information may be monomedium as well as multimedia. See Figure 10.
+
+![Diagram of a generic communication task collecting. A central square box on the left has three arrows pointing to three separate circular nodes on the right, arranged vertically. This represents a multipoint-to-point communication configuration.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg)
+
+Diagram of a generic communication task collecting. A central square box on the left has three arrows pointing to three separate circular nodes on the right, arranged vertically. This represents a multipoint-to-point communication configuration.
+
+T0104880-99
+
+**Figure 10/F.700 – Generic communication task collecting**
+
+##### **Attributes**
+
+##### **Values**
+
+|                                 |                                         |
+|---------------------------------|-----------------------------------------|
+| Communication configuration:    | multipoint-to-point                     |
+| Symmetry of information flow:   | unidirectional                          |
+| Transmission control entity:    | sink                                    |
+| Mandatory media components:     | all are possible, and an option is none |
+| Optional media components:      | all are possible, and an option is none |
+| Media component interrelations: | synchronization is possible             |
+| Communication delay:            | all are possible                        |
+| Time continuity:                | all are possible                        |
+
+Additional *generic* communication tasks are for further study.
+
+Dynamic aspects of communication tasks are for further study.
+
+## **2.2 Media components**
+
+A media component provides the specific information handling functions related to a single information type. The following are examples of information types suited for information presentation to human users: text, audio, graphics, still images and video. This list is non-exhaustive.
+
+NOTE – There may be some telecommunication services supporting multimedia applications, the description of which may not use media components.
+
+Generic media components are not restricted to a particular implementation but include all possible quality levels and options. They are used in the description of generic services that are not offered as such to customers: the specific services offered to customers are implemented on a given network with some limitations that narrow the range of choices.
+
+The following generic media components support the information types listed above: text, audio, graphics, still picture and video. Generic media components to support other information types are for further study.
+
+Quality aspects are, from the user's viewpoint, strongly related to the options among which the user may choose when specifying the appropriate specific media component. Therefore the description of the generic media components includes all functionalities and standards related to the information type. When a specific service is offered to a customer, the available media components usually contain only a subset of these functionalities.
+
+Each media component provides the communication capabilities related to its single information type. It allows for the capture and representation of information, its transfer from originating user(s) to destination user(s), its presentation to human users, processing, filing and retrieval. Detailed descriptions of each media component are in Annex A:
+
+- Generic media component text.
+- Generic media component audio.
+- Generic media component graphics.
+- Generic media component still image.
+- Generic media component motion video.
+- Generic media component data.
+
+## **2.3      Middleware service elements**
+
+The MSEs contain all the control features and the processing functions associated with the service and communication task levels, possibly but not necessarily with the media component level (for instance the coding and decoding process belongs to the media component). Each service uses several MSEs, and a given MSE may be used by different services.
+
+An MSE is a completely independent modular entity. However an MSE may call upon another MSE when particular functions are required. For instance security functions provided by an MSE may be used by other MSEs, e.g. for authentication before accessing a document or performing a task or for encryption of a confidential document. MSEs may also exchange data (e.g. call control may need data from the directory).
+
+The control features are usually embodied in protocols independent from the transmission systems. Their functional descriptions are independent from the basic protocol, but the set of specific commands and messages associated with the protocol has to support the required functions.
+
+Table 4 shows a list of generic and specific functions, and the associated MSEs. This list is not limitative and other MSEs may be added if the need arises. Moreover some of the MSEs may have to be split if some of the functions they include are used independently.
+
+**Table 4/F.700 – List of functions and corresponding MSEs**
+
+| <b>Generic functions</b> | <b>Specific functions</b>       | <b>MSEs</b>          |
+|--------------------------|---------------------------------|----------------------|
+| security                 | authentication/non- repudiation | security             |
+|                          | privacy                         |                      |
+|                          | integrity                       |                      |
+| directory                |                                 | directory            |
+| reservation              |                                 | reservation          |
+| call control             | call set-up                     | call control         |
+|                          | in-call modification            |                      |
+|                          | quality negotiation             |                      |
+| charging and billing     |                                 | charging and billing |
+| media selection          |                                 | media selection      |
+| conference control       | conference management           | conference control   |
+|                          | multipoint protocol             |                      |
+| searching                | browsing, navigation            | retrieval control    |
+| mailing                  | sending mail                    | mail control         |
+|                          | retrieving mail                 |                      |
+| polling                  |                                 | poll control         |
+| application control      | navigation in a document        | application control  |
+|                          | device control                  |                      |
+| processing               | selection                       | processing           |
+|                          | assembly                        |                      |
+|                          | translation                     |                      |
+|                          | media conversion                |                      |
+| storage                  |                                 | storage              |
+| replication              |                                 | replication          |
+| intercommunication       |                                 | intercommunication   |
+
+The MSEs may also be paralleled with the concept of middleware developed in the context of the GII (global information infrastructure) which is defined as the set of mediation functions relating applications to the underlying networks. The list of Middleware functions is very close to the list of MSE functions.
+
+## **2.4 Supplementary services**
+
+Supplementary services are offered to users in conjunction with basic telecommunication services, and they provide users with enhanced or optional communication capabilities. The use of supplementary services in relation to multimedia services described in accordance with this Recommendation may be possible.
+
+# **3 Service description process**
+
+## **3.1 Framework**
+
+Service descriptions have two stages:
+
+- 1) a generic description independent of networks; and
+- 2) a generic description for the network on which the service is to be offered.
+
+The framework for the Recommendations on multimedia services is illustrated in Figure 11.
+
+The service Recommendations in this framework are related to the technical Recommendations in two ways: the use of the technical building blocks defined in these Recommendations such as protocols and coding algorithms, in order to construct the communication capabilities, i.e. the communication tasks and the media components; conversely, they define the service requirements on the equipment, the attributes, the functions and the performance that the technical Recommendations will then have to reflect. Thus a constant dialogue is necessary between the relevant study groups or Questions, in order to obtain the best compromise between, on the one hand, the functions and quality of service desired by the users, and on the other hand the technical constraints and the cost of the implementation. Figure 12 shows the relationships among the service Recommendations and the technical Recommendations.
+
+![](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg)
+
+|                         |                                                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                          |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------------------------------|------|------------------------------------|-----|---------------------------------|-----|-------------------------|-----|--------------------|
+| User's view             | General descriptions                                                                                                                                                                                                                                                                                           | <div style="border: 1px solid black; border-radius: 10px; padding: 5px; display: inline-block;">         F.700 – Multimedia services<br/>         Annex A: Media components<br/>         Annex B: Communication tasks<br/>         Annex C: Middleware service elements       </div>                                     |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+|                         |                                                                                                                                                                                                                                                                                                                | <div style="border: 1px solid black; border-radius: 10px; padding: 5px;">         F.702<br/>Multimedia conference services<br/> <table style="width:100%; border: 1px solid black;"> <tr> <td style="border-right: 1px solid black;">Profiles<br/>AGCS</td> <td>Profiles<br/>VCS</td> <td>...</td> </tr> </table> </div> | Profiles<br>AGCS | Profiles<br>VCS | ...                                                                                                                                                         | <div style="border: 1px solid black; border-radius: 10px; padding: 5px;">         F.703<br/>Multimedia conversational services<br/> <table style="width:100%; border: 1px solid black;"> <tr> <td style="border-right: 1px solid black;">Profiles<br/>VPS</td> <td>...</td> </tr> </table> </div> | Profiles<br>VPS                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | ... | <div style="border: 1px solid black; border-radius: 10px; padding: 5px;">         F.MDS<br/>Multimedia distribution services<br/> <table style="width:100%; border: 1px solid black;"> <tr> <td>Profiles<br/>MDS</td> </tr> </table> </div> | Profiles<br>MDS | <div style="border: 1px solid black; border-radius: 10px; padding: 5px;">         F.MRS<br/>Multimedia retrieval services<br/> <table style="width:100%; border: 1px solid black;"> <tr> <td style="border-right: 1px solid black;">Profiles<br/>AVIS</td> <td>Profiles<br/>ADM</td> </tr> </table> </div> | Profiles<br>AVIS           | Profiles<br>ADM | <div style="border: 1px solid black; border-radius: 10px; padding: 5px;">         F.MMS<br/>Multimedia message services<br/> <table style="width:100%; border: 1px solid black;"> <tr> <td>Profiles<br/>...</td> </tr> </table> </div> | Profiles<br>... | <div style="border: 1px solid black; border-radius: 10px; padding: 5px;">         F.MCLS<br/>Multimedia collection services<br/> <table style="width:100%; border: 1px solid black;"> <tr> <td>Profiles<br/>...</td> </tr> </table> </div> | Profiles<br>... |                                |      |                                    |     |                                 |     |                         |     |                    |
+| Profiles<br>AGCS        | Profiles<br>VCS                                                                                                                                                                                                                                                                                                | ...                                                                                                                                                                                                                                                                                                                      |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+| Profiles<br>VPS         | ...                                                                                                                                                                                                                                                                                                            |                                                                                                                                                                                                                                                                                                                          |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+| Profiles<br>MDS         |                                                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                          |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+| Profiles<br>AVIS        | Profiles<br>ADM                                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                          |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+| Profiles<br>...         |                                                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                          |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+| Profiles<br>...         |                                                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                          |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+| Network Operator's view | ISDN                                                                                                                                                                                                                                                                                                           | <div style="border: 1px solid black; border-radius: 10px; padding: 5px;">         F.731<br/>MCS on ISDN<br/> <table style="width:100%; border: 1px solid black;"> <tr> <td style="border-right: 1px solid black;">Profiles<br/>AGCS</td> <td>Profiles<br/>VCS</td> <td>...</td> </tr> </table> </div>                    | Profiles<br>AGCS | Profiles<br>VCS | ...                                                                                                                                                         | <div style="border: 1px solid black; border-radius: 10px; padding: 5px; text-align: center;">         F.MCVS.1<br/>MCVS<br/>on<br/>ISDN       </div>                                                                                                                                              | <table style="border: 1px solid black; padding: 5px; width: 100%;"> <tr><td>ADM</td><td>Teleadministration service</td></tr> <tr><td>AGCS</td><td>Audiographic conference service</td></tr> <tr><td>AVIS</td><td>Audiovisual interactive services</td></tr> <tr><td>MCS</td><td>Multimedia conference services</td></tr> <tr><td>MCVS</td><td>Multimedia conversational services</td></tr> <tr><td>MDS</td><td>Multimedia distribution service</td></tr> <tr><td>VCS</td><td>Videoconference service</td></tr> <tr><td>VPS</td><td>Videophone service</td></tr> </table> |     |                                                                                                                                                                                                                                             |                 | ADM                                                                                                                                                                                                                                                                                                        | Teleadministration service | AGCS            | Audiographic conference service                                                                                                                                                                                                        | AVIS            | Audiovisual interactive services                                                                                                                                                                                                           | MCS             | Multimedia conference services | MCVS | Multimedia conversational services | MDS | Multimedia distribution service | VCS | Videoconference service | VPS | Videophone service |
+|                         | Profiles<br>AGCS                                                                                                                                                                                                                                                                                               | Profiles<br>VCS                                                                                                                                                                                                                                                                                                          | ...              |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+|                         | ADM                                                                                                                                                                                                                                                                                                            | Teleadministration service                                                                                                                                                                                                                                                                                               |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+|                         | AGCS                                                                                                                                                                                                                                                                                                           | Audiographic conference service                                                                                                                                                                                                                                                                                          |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+|                         | AVIS                                                                                                                                                                                                                                                                                                           | Audiovisual interactive services                                                                                                                                                                                                                                                                                         |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+| MCS                     | Multimedia conference services                                                                                                                                                                                                                                                                                 |                                                                                                                                                                                                                                                                                                                          |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+| MCVS                    | Multimedia conversational services                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                          |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+| MDS                     | Multimedia distribution service                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                          |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+| VCS                     | Videoconference service                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                                                                                                                                                          |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+| VPS                     | Videophone service                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                          |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+| B-ISDN                  | <div style="border: 1px solid black; border-radius: 10px; padding: 5px;">         F.732<br/>MCS on B-ISDN<br/> <table style="width:100%; border: 1px solid black;"> <tr> <td style="border-right: 1px solid black;">Profiles<br/>AGCS</td> <td>Profiles<br/>VCS</td> <td>...</td> </tr> </table> </div>        | Profiles<br>AGCS                                                                                                                                                                                                                                                                                                         | Profiles<br>VCS  | ...             | <div style="border: 1px solid black; border-radius: 10px; padding: 5px; text-align: center;">         F.MCVS.2<br/>MCVS<br/>on<br/>B-ISDN       </div>      |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+| Profiles<br>AGCS        | Profiles<br>VCS                                                                                                                                                                                                                                                                                                | ...                                                                                                                                                                                                                                                                                                                      |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+| PSTN                    | <div style="border: 1px solid black; border-radius: 10px; padding: 5px;">         F.MCS.3<br/>MCS on PSTN<br/> <table style="width:100%; border: 1px solid black;"> <tr> <td style="border-right: 1px solid black;">Profiles<br/>AGCS</td> <td>Profiles<br/>VCS</td> <td>...</td> </tr> </table> </div>        | Profiles<br>AGCS                                                                                                                                                                                                                                                                                                         | Profiles<br>VCS  | ...             | <div style="border: 1px solid black; border-radius: 10px; padding: 5px; text-align: center;">         F.MCVS.3<br/>MCVS<br/>on<br/>PSTN       </div>        |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+| Profiles<br>AGCS        | Profiles<br>VCS                                                                                                                                                                                                                                                                                                | ...                                                                                                                                                                                                                                                                                                                      |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+| Mobiles                 | <div style="border: 1px solid black; border-radius: 10px; padding: 5px;">         F.MCS.4<br/>MCS for mobiles<br/> <table style="width:100%; border: 1px solid black;"> <tr> <td style="border-right: 1px solid black;">Profiles<br/>AGCS</td> <td>Profiles<br/>VCS</td> <td>...</td> </tr> </table> </div>    | Profiles<br>AGCS                                                                                                                                                                                                                                                                                                         | Profiles<br>VCS  | ...             | <div style="border: 1px solid black; border-radius: 10px; padding: 5px; text-align: center;">         F.MCVS.4<br/>MCVS<br/>for<br/>Mobiles       </div>    |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+| Profiles<br>AGCS        | Profiles<br>VCS                                                                                                                                                                                                                                                                                                | ...                                                                                                                                                                                                                                                                                                                      |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+| IP networks             | <div style="border: 1px solid black; border-radius: 10px; padding: 5px;">         F.MCS.5<br/>MCS on IP networks<br/> <table style="width:100%; border: 1px solid black;"> <tr> <td style="border-right: 1px solid black;">Profiles<br/>AGCS</td> <td>Profiles<br/>VCS</td> <td>...</td> </tr> </table> </div> | Profiles<br>AGCS                                                                                                                                                                                                                                                                                                         | Profiles<br>VCS  | ...             | <div style="border: 1px solid black; border-radius: 10px; padding: 5px; text-align: center;">         F.MCVS.5<br/>MCVS<br/>on<br/>IP networks       </div> |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+| Profiles<br>AGCS        | Profiles<br>VCS                                                                                                                                                                                                                                                                                                | ...                                                                                                                                                                                                                                                                                                                      |                  |                 |                                                                                                                                                             |                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |     |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                                                                                                                                            |                            |                 |                                                                                                                                                                                                                                        |                 |                                                                                                                                                                                                                                            |                 |                                |      |                                    |     |                                 |     |                         |     |                    |
+
+T1607230-99
+
+**Figure 11/F.700 – Framework for the Recommendations on multimedia services**
+
+![Diagram illustrating the relationship between service and technical descriptions in Recommendation F.700. It is divided into four quadrants. The top-left shows service descriptions and network-independent recommendations. The top-right shows network-specific recommendations for ISDN, B-ISDN, PSTN, Mobiles, and Packets. The bottom-left lists technical descriptions by category (Protocols, Coding, Video, Text, Audio). The bottom-right maps network types to specific technical standards for terminals, multipoint, signalling, multiplexing, and call control. Arrows indicate the relationships and mappings between these elements.](a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg)
+
+| <div style="text-align: center; margin-bottom: 10px;">Network independent Recommendations</div> <div style="position: relative; height: 300px;"> <div style="position: absolute; left: 10px; top: 10px; border: 1px solid black; padding: 5px; width: 250px;"> <b>F.700</b><br/>           Service description<br/>           Communication capabilities:<br/> <div style="display: flex; justify-content: space-around; margin-top: 10px;"> <div style="border: 1px solid black; padding: 2px;">MSEs</div> <div style="border: 1px solid black; padding: 2px;">Communication<br/>tasks</div> <div style="border: 1px solid black; padding: 2px;">Media<br/>components</div> </div> </div> <div style="position: absolute; right: 10px; top: 10px; border: 1px solid black; padding: 5px;">           F.MDS<br/>F.MRS<br/>F.MCVS = F.703<br/>F.MCS = F.702<br/> <div style="border: 1px solid black; margin-top: 5px; padding: 2px;">Generic<br/>multimedia<br/>services</div> </div> </div> |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | <div style="text-align: center; margin-bottom: 10px;">Network specific Recommendations</div> <table border="0" style="width: 100%; text-align: center;"> <tr> <th>ISDN</th> <th>B-ISDN</th> <th>PSTN</th> <th>Mobiles</th> <th>Packets</th> </tr> <tr> <td><div style="border: 1px solid black;">F.MDS.1<br/>F.MRS.1<br/>F.MCV.1<br/>F.MCS.1<br/>= F.731</div></td> <td><div style="border: 1px solid black;">F.MDS.2<br/>F.MRS.2<br/>F.MCV.2<br/>F.MCS.2<br/>= F.732</div></td> <td><div style="border: 1px solid black;">F.MDS.3<br/>F.MRS.3<br/>F.MCV.3<br/>F.MCS.3</div></td> <td><div style="border: 1px solid black;">F.MDS.4<br/>F.MRS.4<br/>F.MCV.4<br/>F.MCS.4</div></td> <td><div style="border: 1px solid black;">F.MDS.5<br/>F.MRS.5<br/>F.MCV.5<br/>F.MCS.5</div></td> </tr> </table> |                                                                                         |                                                                                                                                                                    |                            |       | ISDN                                                                                                                                                                                                             | B-ISDN | PSTN | Mobiles                                           | Packets                                                                                                                                                            | <div style="border: 1px solid black;">F.MDS.1<br/>F.MRS.1<br/>F.MCV.1<br/>F.MCS.1<br/>= F.731</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | <div style="border: 1px solid black;">F.MDS.2<br/>F.MRS.2<br/>F.MCV.2<br/>F.MCS.2<br/>= F.732</div> | <div style="border: 1px solid black;">F.MDS.3<br/>F.MRS.3<br/>F.MCV.3<br/>F.MCS.3</div> | <div style="border: 1px solid black;">F.MDS.4<br/>F.MRS.4<br/>F.MCV.4<br/>F.MCS.4</div> | <div style="border: 1px solid black;">F.MDS.5<br/>F.MRS.5<br/>F.MCV.5<br/>F.MCS.5</div> |                                                   |                                                             |                                                   |                                                   |                                                   |                            |                                                             |                                                   |                                                   |                                                   |                                                   |            |                                                             |                                                   |                                                   |                                                   |                                                   |                       |                                                   |                                                                 |                                                   |                                                   |                                                     |           |                                                   |                                                    |                                                  |                                                     |              |      |        |      |         |         |  |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|------|---------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|---------------------------------------------------|-------------------------------------------------------------|---------------------------------------------------|---------------------------------------------------|---------------------------------------------------|----------------------------|-------------------------------------------------------------|---------------------------------------------------|---------------------------------------------------|---------------------------------------------------|---------------------------------------------------|------------|-------------------------------------------------------------|---------------------------------------------------|---------------------------------------------------|---------------------------------------------------|---------------------------------------------------|-----------------------|---------------------------------------------------|-----------------------------------------------------------------|---------------------------------------------------|---------------------------------------------------|-----------------------------------------------------|-----------|---------------------------------------------------|----------------------------------------------------|--------------------------------------------------|-----------------------------------------------------|--------------|------|--------|------|---------|---------|--|
+| ISDN                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | B-ISDN                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | PSTN                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Mobiles                                                                                 | Packets                                                                                                                                                            |                            |       |                                                                                                                                                                                                                  |        |      |                                                   |                                                                                                                                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                                                     |                                                                                         |                                                                                         |                                                                                         |                                                   |                                                             |                                                   |                                                   |                                                   |                            |                                                             |                                                   |                                                   |                                                   |                                                   |            |                                                             |                                                   |                                                   |                                                   |                                                   |                       |                                                   |                                                                 |                                                   |                                                   |                                                     |           |                                                   |                                                    |                                                  |                                                     |              |      |        |      |         |         |  |
+| <div style="border: 1px solid black;">F.MDS.1<br/>F.MRS.1<br/>F.MCV.1<br/>F.MCS.1<br/>= F.731</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | <div style="border: 1px solid black;">F.MDS.2<br/>F.MRS.2<br/>F.MCV.2<br/>F.MCS.2<br/>= F.732</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | <div style="border: 1px solid black;">F.MDS.3<br/>F.MRS.3<br/>F.MCV.3<br/>F.MCS.3</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | <div style="border: 1px solid black;">F.MDS.4<br/>F.MRS.4<br/>F.MCV.4<br/>F.MCS.4</div> | <div style="border: 1px solid black;">F.MDS.5<br/>F.MRS.5<br/>F.MCV.5<br/>F.MCS.5</div>                                                                            |                            |       |                                                                                                                                                                                                                  |        |      |                                                   |                                                                                                                                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                                                     |                                                                                         |                                                                                         |                                                                                         |                                                   |                                                             |                                                   |                                                   |                                                   |                            |                                                             |                                                   |                                                   |                                                   |                                                   |            |                                                             |                                                   |                                                   |                                                   |                                                   |                       |                                                   |                                                                 |                                                   |                                                   |                                                     |           |                                                   |                                                    |                                                  |                                                     |              |      |        |      |         |         |  |
+| <div style="transform: rotate(-90deg); white-space: nowrap; margin-top: 100px;">Technical descriptions</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | <table border="0" style="width: 100%;"> <tr> <td>Protocols</td> <td>Coding</td> <td>Video</td> <td>Text</td> <td>Audio</td> </tr> <tr> <td><div style="border: 1px solid black;">T.120</div><br/><div style="border: 1px solid black;">T.130</div><br/><div style="border: 1px solid black;">T.140</div><br/><div style="border: 1px solid black;">H.248</div></td> <td></td> <td></td> <td><div style="border: 1px solid black;">T.140</div></td> <td><div style="border: 1px solid black;">G.729<br/>G.728<br/>G.723<br/>G.722<br/>G.711</div><br/><div style="border: 1px solid black;">H.263<br/>H.262<br/>H.261</div></td> </tr> </table> | Protocols                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | Coding                                                                                  | Video                                                                                                                                                              | Text                       | Audio | <div style="border: 1px solid black;">T.120</div><br><div style="border: 1px solid black;">T.130</div><br><div style="border: 1px solid black;">T.140</div><br><div style="border: 1px solid black;">H.248</div> |        |      | <div style="border: 1px solid black;">T.140</div> | <div style="border: 1px solid black;">G.729<br/>G.728<br/>G.723<br/>G.722<br/>G.711</div><br><div style="border: 1px solid black;">H.263<br/>H.262<br/>H.261</div> | <table border="0" style="width: 100%; text-align: center;"> <tr> <td><div style="border: 1px solid black;">H.320</div></td> <td><div style="border: 1px solid black;">H.321<br/>H.310</div></td> <td><div style="border: 1px solid black;">H.324</div></td> <td><div style="border: 1px solid black;">H.32M</div></td> <td><div style="border: 1px solid black;">H.323</div></td> <td style="text-align: left;">Terminals or<br/>end-points</td> </tr> <tr> <td><div style="border: 1px solid black;">H.243<br/>H.231</div></td> <td><div style="border: 1px solid black;">H.247</div></td> <td><div style="border: 1px dashed black;">N.A.</div></td> <td><div style="border: 1px dashed black;">N.A.</div></td> <td><div style="border: 1px solid black;">H.332</div></td> <td style="text-align: left;">Multipoint</td> </tr> <tr> <td><div style="border: 1px solid black;">H.242<br/>H.230</div></td> <td><div style="border: 1px solid black;">H.245</div></td> <td><div style="border: 1px solid black;">H.245</div></td> <td><div style="border: 1px solid black;">H.245</div></td> <td><div style="border: 1px solid black;">H.245</div></td> <td style="text-align: left;">In-band<br/>signalling</td> </tr> <tr> <td><div style="border: 1px solid black;">H.221</div></td> <td><div style="border: 1px solid black;">H.222.1<br/>H.222.0</div></td> <td><div style="border: 1px solid black;">H.223</div></td> <td><div style="border: 1px solid black;">H.223</div></td> <td rowspan="2"><div style="border: 1px solid black;">H.225.0</div></td> <td style="text-align: left;">Multiplex</td> </tr> <tr> <td><div style="border: 1px solid black;">Q.931</div></td> <td><div style="border: 1px solid black;">Q.2931</div></td> <td><div style="border: 1px solid black;">Q.23</div></td> <td><div style="border: 1px dashed black;">Q. ...</div></td> <td style="text-align: left;">Call control</td> </tr> <tr> <th>ISDN</th> <th>B-ISDN</th> <th>PSTN</th> <th>Mobiles</th> <th>Packets</th> <td></td> </tr> </table> |                                                                                                     |                                                                                         |                                                                                         |                                                                                         | <div style="border: 1px solid black;">H.320</div> | <div style="border: 1px solid black;">H.321<br/>H.310</div> | <div style="border: 1px solid black;">H.324</div> | <div style="border: 1px solid black;">H.32M</div> | <div style="border: 1px solid black;">H.323</div> | Terminals or<br>end-points | <div style="border: 1px solid black;">H.243<br/>H.231</div> | <div style="border: 1px solid black;">H.247</div> | <div style="border: 1px dashed black;">N.A.</div> | <div style="border: 1px dashed black;">N.A.</div> | <div style="border: 1px solid black;">H.332</div> | Multipoint | <div style="border: 1px solid black;">H.242<br/>H.230</div> | <div style="border: 1px solid black;">H.245</div> | <div style="border: 1px solid black;">H.245</div> | <div style="border: 1px solid black;">H.245</div> | <div style="border: 1px solid black;">H.245</div> | In-band<br>signalling | <div style="border: 1px solid black;">H.221</div> | <div style="border: 1px solid black;">H.222.1<br/>H.222.0</div> | <div style="border: 1px solid black;">H.223</div> | <div style="border: 1px solid black;">H.223</div> | <div style="border: 1px solid black;">H.225.0</div> | Multiplex | <div style="border: 1px solid black;">Q.931</div> | <div style="border: 1px solid black;">Q.2931</div> | <div style="border: 1px solid black;">Q.23</div> | <div style="border: 1px dashed black;">Q. ...</div> | Call control | ISDN | B-ISDN | PSTN | Mobiles | Packets |  |
+| Protocols                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Coding                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Video                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Text                                                                                    | Audio                                                                                                                                                              |                            |       |                                                                                                                                                                                                                  |        |      |                                                   |                                                                                                                                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                                                     |                                                                                         |                                                                                         |                                                                                         |                                                   |                                                             |                                                   |                                                   |                                                   |                            |                                                             |                                                   |                                                   |                                                   |                                                   |            |                                                             |                                                   |                                                   |                                                   |                                                   |                       |                                                   |                                                                 |                                                   |                                                   |                                                     |           |                                                   |                                                    |                                                  |                                                     |              |      |        |      |         |         |  |
+| <div style="border: 1px solid black;">T.120</div><br><div style="border: 1px solid black;">T.130</div><br><div style="border: 1px solid black;">T.140</div><br><div style="border: 1px solid black;">H.248</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | <div style="border: 1px solid black;">T.140</div>                                       | <div style="border: 1px solid black;">G.729<br/>G.728<br/>G.723<br/>G.722<br/>G.711</div><br><div style="border: 1px solid black;">H.263<br/>H.262<br/>H.261</div> |                            |       |                                                                                                                                                                                                                  |        |      |                                                   |                                                                                                                                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                                                     |                                                                                         |                                                                                         |                                                                                         |                                                   |                                                             |                                                   |                                                   |                                                   |                            |                                                             |                                                   |                                                   |                                                   |                                                   |            |                                                             |                                                   |                                                   |                                                   |                                                   |                       |                                                   |                                                                 |                                                   |                                                   |                                                     |           |                                                   |                                                    |                                                  |                                                     |              |      |        |      |         |         |  |
+| <div style="border: 1px solid black;">H.320</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | <div style="border: 1px solid black;">H.321<br/>H.310</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | <div style="border: 1px solid black;">H.324</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | <div style="border: 1px solid black;">H.32M</div>                                       | <div style="border: 1px solid black;">H.323</div>                                                                                                                  | Terminals or<br>end-points |       |                                                                                                                                                                                                                  |        |      |                                                   |                                                                                                                                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                                                     |                                                                                         |                                                                                         |                                                                                         |                                                   |                                                             |                                                   |                                                   |                                                   |                            |                                                             |                                                   |                                                   |                                                   |                                                   |            |                                                             |                                                   |                                                   |                                                   |                                                   |                       |                                                   |                                                                 |                                                   |                                                   |                                                     |           |                                                   |                                                    |                                                  |                                                     |              |      |        |      |         |         |  |
+| <div style="border: 1px solid black;">H.243<br/>H.231</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | <div style="border: 1px solid black;">H.247</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | <div style="border: 1px dashed black;">N.A.</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | <div style="border: 1px dashed black;">N.A.</div>                                       | <div style="border: 1px solid black;">H.332</div>                                                                                                                  | Multipoint                 |       |                                                                                                                                                                                                                  |        |      |                                                   |                                                                                                                                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                                                     |                                                                                         |                                                                                         |                                                                                         |                                                   |                                                             |                                                   |                                                   |                                                   |                            |                                                             |                                                   |                                                   |                                                   |                                                   |            |                                                             |                                                   |                                                   |                                                   |                                                   |                       |                                                   |                                                                 |                                                   |                                                   |                                                     |           |                                                   |                                                    |                                                  |                                                     |              |      |        |      |         |         |  |
+| <div style="border: 1px solid black;">H.242<br/>H.230</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | <div style="border: 1px solid black;">H.245</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | <div style="border: 1px solid black;">H.245</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | <div style="border: 1px solid black;">H.245</div>                                       | <div style="border: 1px solid black;">H.245</div>                                                                                                                  | In-band<br>signalling      |       |                                                                                                                                                                                                                  |        |      |                                                   |                                                                                                                                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                                                     |                                                                                         |                                                                                         |                                                                                         |                                                   |                                                             |                                                   |                                                   |                                                   |                            |                                                             |                                                   |                                                   |                                                   |                                                   |            |                                                             |                                                   |                                                   |                                                   |                                                   |                       |                                                   |                                                                 |                                                   |                                                   |                                                     |           |                                                   |                                                    |                                                  |                                                     |              |      |        |      |         |         |  |
+| <div style="border: 1px solid black;">H.221</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | <div style="border: 1px solid black;">H.222.1<br/>H.222.0</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | <div style="border: 1px solid black;">H.223</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | <div style="border: 1px solid black;">H.223</div>                                       | <div style="border: 1px solid black;">H.225.0</div>                                                                                                                | Multiplex                  |       |                                                                                                                                                                                                                  |        |      |                                                   |                                                                                                                                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                                                     |                                                                                         |                                                                                         |                                                                                         |                                                   |                                                             |                                                   |                                                   |                                                   |                            |                                                             |                                                   |                                                   |                                                   |                                                   |            |                                                             |                                                   |                                                   |                                                   |                                                   |                       |                                                   |                                                                 |                                                   |                                                   |                                                     |           |                                                   |                                                    |                                                  |                                                     |              |      |        |      |         |         |  |
+| <div style="border: 1px solid black;">Q.931</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | <div style="border: 1px solid black;">Q.2931</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | <div style="border: 1px solid black;">Q.23</div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | <div style="border: 1px dashed black;">Q. ...</div>                                     |                                                                                                                                                                    | Call control               |       |                                                                                                                                                                                                                  |        |      |                                                   |                                                                                                                                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                                                     |                                                                                         |                                                                                         |                                                                                         |                                                   |                                                             |                                                   |                                                   |                                                   |                            |                                                             |                                                   |                                                   |                                                   |                                                   |            |                                                             |                                                   |                                                   |                                                   |                                                   |                       |                                                   |                                                                 |                                                   |                                                   |                                                     |           |                                                   |                                                    |                                                  |                                                     |              |      |        |      |         |         |  |
+| ISDN                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | B-ISDN                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | PSTN                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Mobiles                                                                                 | Packets                                                                                                                                                            |                            |       |                                                                                                                                                                                                                  |        |      |                                                   |                                                                                                                                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                                                     |                                                                                         |                                                                                         |                                                                                         |                                                   |                                                             |                                                   |                                                   |                                                   |                            |                                                             |                                                   |                                                   |                                                   |                                                   |            |                                                             |                                                   |                                                   |                                                   |                                                   |                       |                                                   |                                                                 |                                                   |                                                   |                                                     |           |                                                   |                                                    |                                                  |                                                     |              |      |        |      |         |         |  |
+
+MSEs Middleware service elements
+
+Diagram illustrating the relationship between service and technical descriptions in Recommendation F.700. It is divided into four quadrants. The top-left shows service descriptions and network-independent recommendations. The top-right shows network-specific recommendations for ISDN, B-ISDN, PSTN, Mobiles, and Packets. The bottom-left lists technical descriptions by category (Protocols, Coding, Video, Text, Audio). The bottom-right maps network types to specific technical standards for terminals, multipoint, signalling, multiplexing, and call control. Arrows indicate the relationships and mappings between these elements.
+
+T1607220-99
+
+Figure 12/F.700 – Illustration of the relationship among service and technical descriptions
+
+## **3.2 Service profiles**
+
+The description of generic services leaves them with a large degree of flexibility so that they may support a wide variety of present and future applications. However, it is necessary to ensure that the user obtains a known and homogeneous set of quality levels and standard options that will meet his expectations and the requirements of his application.
+
+Profiles of generic services identify areas of commonality from a customer viewpoint between terminals and server equipment in order to ensure at least a minimum level of communication. Conformance to a profile ensures intercommunication with other terminals to the same profile. A terminal or a server may conform to one or several profile(s), and may have capabilities beyond those embodied in the profile(s).
+
+A profile is defined by a set of communication tasks and media components, with a specified quality level for each component and possible standard options. Different profiles of a generic service type may define different services of that type or different instances of the same service (e.g. different quality levels).
+
+## **3.3 Quality of service**
+
+Quality of service is very important for the user and can be essential in many applications. The levels of quality for the various media component attribute values are specified in the profile descriptions. Other quality/performance parameters are defined at the communication task level, or at the service level.
+
+The following are examples of quality parameters:
+
+- at the media component level: image resolution;
+- at the communication task level: differential delay for synchronization of audio and video;
+- at the service level: response time for call establishment.
+
+## **3.4 Generic service descriptions**
+
+A generic service is described using service principles (for example, performance, quality of service, security, charging, intercommunications), communication tasks and media components from Annexes A, B and C. Specific instances of the service may be defined as profiles of the generic service and described in the corresponding subclause. The generic service Recommendations should contain the following parts.
+
+### **Service description outline**
+
+- 1 Introduction
+- 2 Definitions
+- 3 Terminology
+- 4 Description
+- 4.1 General description
+- 4.2 Functional model
+- 4.3 Configuration
+- 4.4 Terminal aspects
+- 4.5 Applications
+- 5 Static aspects (see Note)
+
+- 5.1 Service level
+- 5.2 Communication task level
+- 5.3 Media component level
+- 6 Dynamic aspects
+- 6.1 Activation phase
+- 6.2 Communication phase
+- 6.3 Termination phase
+- 7 Service profiles
+- 8 Interworking and intercommunication
+
+NOTE – Static aspects include considerations of quality of service, security, and charging aspects applicable to each level of the reference model.
+
+## **3.5 Derivation of specific services**
+
+Network specific services are related to a particular network. Recommendations for such services should be very short and contain only those specifications that differ among networks, together with any part not covered in the generic Recommendation. Typically these Recommendations will contain complements to a few sections of the generic Recommendation, such as service profiles, interworking and intercommunication requisites, and a table of attributes for each profile.
+
+NOTE – Network specific Recommendations for ISDN will result in a Stage 1 description. See Recommendation I.130.
+
+## **3.6 Elaboration of service description**
+
+The elaboration of the service Recommendations should proceed from the users' needs, expressed in one or more scripts. From these scripts the user requirements are derived and translated into the various elements on which the description is based: a functional model, general functionalities, lists of communication tasks and media components, quality levels, static and dynamic aspects of the service, and finally service profiles; each script may lead to one or several service profiles adapted to variations in the situations or scenarios it describes, and to various possible compromises between cost and quality of service.
+
+The Recommendations obtained through this process should be network independent. Even if some scripts may lead to requirements which can be satisfied by only one type of network (e.g. mobility), the generic services should cover a wide range of applications, related to different scripts and different sets of requirements. Implementation of the service will of course have to use an existing network, and thus network specific complementary Recommendations will also be necessary, as described in 3.5.
+
+A generic service usually leads to several specific services defined by different profiles. This means that new specific services may be defined by simply adding new profiles, usually derived from a new script. This mechanism will provide an efficient means for describing new services rapidly, without requiring the long drafting process of a new Recommendation.
+
+NOTE – Although scripts are the preferred means for describing the users' needs, difficulties which may arise in deriving them or in submitting them to the user community should not unduly delay the drafting and approval of the service Recommendations. If necessary, knowledge of a service or its usage may be derived through other means, such as field trials, implementation of specific instances of the service or of similar services.
+
+## **3.7 Intercommunication among service categories**
+
+Intercommunication is a desirable feature in many cases. At the lowest level, it is achieved between terminals and allows a user to make different types of calls or answer different types of calls from the same terminal. It allows the user to avoid having several terminals which are cumbersome and expensive. A possible limitation may be the increased cost and complexity of the terminal or its insufficient quality. For instance, the screen for the basic conversational service of a low bit rate videophone could display text, but not with a sufficient quality for reading a commercial document.
+
+At a higher level, the intercommunication between services may allow the user to combine the functions offered by different types of services and thus increase the range of possible applications. For instance, retrieving a document through a retrieval service is a useful enhancement to a conference service.
+
+# **ANNEX A**
+
+## **Media components descriptions**
+
+## **A.1 Media component audio**
+
+#### **A.1.1 Definition**
+
+The media component audio allows for the capture and representation of information, its transfer from originating user(s) to destination user(s), its presentation to human user(s), processing, filing and retrieval. Audio includes speech, usually transmitted in real-time, i.e. at the speed at which it was produced and with a limited delay.
+
+#### **A.1.2 Description**
+
+##### **A.1.2.1 General description**
+
+In the media component audio, a source produces an audio signal which then may be coded, compressed, stored and transmitted. At the other end, the signal is decoded and presented to a human user. Depending upon the type of service, five levels of quality are defined:
+
+- A(-1): sound signal with minimum quality to allow the presence of the speaker to be detected;
+- A0: minimum sound quality, sufficient for understanding speech from various speakers; the quality should be at least as good as that obtained with G.711 or G.728 codecs;
+- A1: 7 kHz speech quality, at least equivalent to that of a G.722 codec operating at 48 kbit/s;
+- A2: 15 kHz broadcast quality sound/speech, at least equivalent to that of a J.41 codec;
+- A3: 20 kHz hi-fi or CD quality.
+
+Option: The sound may optionally be stereo, including two sound signals for the right and left ears (note that the two signals are not independent and that some coding schemes might use the redundancy to reduce the bit rate). Level A3 usually entails multiple sound channels.
+
+##### **A.1.2.2 Additional facilities**
+
+Various auxiliary features may be offered either as an inherent part of the media component or as a specific function of the terminal. They include:
+
+- auxiliary or multiple audio sources (e.g. multiple microphones in a teleconference room);
+- audio tape recording/transmission or other audio recording equipment;
+- various information on the source of the sound, e.g. identification of the speaker in a conference;
+
+- audible tones or announcements related to the service or the application, for instance for user guidance.
+
+Audio muting may be possible in specific cases. A visible indicator of muting shall appear on the muted terminal.
+
+This short list is not exhaustive and may be extended due to the needs of specific services or applications.
+
+##### A.1.2.3 Requirements for various audiovisual services
+
+The levels of audio quality required for various services are the following:
+
+| Service                  | A0 | A1 | A2 | A3 |
+|--------------------------|----|----|----|----|
+| PSTN videotelephone      | X  |    |    |    |
+| Mobile videotelephone    | X  | X  |    |    |
+| ISDN videotelephone      | X  | X  |    |    |
+| Desktop videotelephone   | X  | X  |    |    |
+| Audiographic conference  | X  | X  | X  |    |
+| Videoconference          |    | X  | X  |    |
+| Video surveillance       | X  | X  |    |    |
+| Audio/video distribution |    |    | X  | X  |
+| Multimedia retrieval     | X  | X  | X  | X  |
+
+This table is not exhaustive; its main purpose is to illustrate the use of the different levels of quality, and particularly the fact that a given service may be offered at different quality levels.
+
+#### A.1.3 Quality aspects
+
+##### A.1.3.1 Audio quality
+
+The minimum audio quality for most audiovisual/multimedia services is that of ordinary telephony, i.e. the quality that allows a reasonable ease for understanding speech from a variety of possible speakers. This must be maintained even in interworking or intercommunication situations. For most services, however, the audio quality objectives are generally much higher, ranging from a good comfort for listening to speech to the highest quality in reproducing music or other sounds. The requirements will be specified according to the desired quality level.
+
+##### A.1.3.2 Echo
+
+Echo occurs in bidirectional audio connections and may seriously impair the audio quality. Efficient echo control should therefore be provided in bidirectional equipment. Interworking/intercommunication situations should also be considered because different terminal design and/or transmission parameters may cause additional difficulties for echo suppression.
+
+##### A.1.3.3 Overall delay
+
+The overall delay is defined as the sum of the transmission delay and the characteristic delay of the terminals (and of other equipment such as transcoders or MCUs when applicable). This delay should be kept within specific limits in accordance with the specific services.
+
+#### A.1.4 Intercommunication
+
+The various audiovisual/multimedia services should as much as possible be able to intercommunicate, particularly when they are used for the same type of applications. This is usually achieved by a fall-back mechanism that retains only the common media components and for each of them the lower quality level.
+
+Intercommunication should be achieved at least between levels used for the same types of applications and/or services, namely between levels A0, A1 and A2 for speech, and between levels A2 and A3 for high quality audio. Intercommunication should also be possible between different implementations of the same level (for instance, between the same services offered on different networks).
+
+### **A.2 Media component video**
+
+#### **A.2.1 Definition**
+
+The media component video for the capture and representation of information, its transfer from originating user(s) to destination user(s), its presentation to human user(s), processing, filing and retrieval. The requirement is that under normal conditions for the service there is adequate representation of fluid movement. Thus the required temporal performance depends upon the amount of movement in the usual type of scene handled by the service. Similarly, the required resolution is dependent upon the type of picture usually transmitted for the service.
+
+#### **A.2.2 Description**
+
+##### **A.2.2.1 General description**
+
+In the media component video, a video source produces a video signal carrying a moving picture, which may be then coded, compressed, stored and transmitted. At the other end, the signal is decoded and presented on a screen. Depending upon the type of service, the following levels of quality are defined:
+
+V(-1): video signal sufficient to allow movement to be detected;
+
+V0: minimum videophone quality, sufficient for showing the head of one person so that his identity and his facial expressions may be recognized; the amount of movement that can be tolerated without degraded temporal performance is very limited; the corresponding range for spatial resolution is from SQIF to QCIF (Note 2);
+
+V1: basic videophone quality, sufficient for showing a head and shoulder view of one person while being able to observe the lips movements; the amount of movements is limited to those of a seated person in a normal conversation (Note 1); the corresponding maximum spatial resolution is QCIF, Quarter Common Intermediate Format (Note 2);
+
+V2: basic videoconference quality, allowing a small group of three seated persons to be shown simultaneously; the amount of movements is limited to those of a normal discussion; the corresponding maximum spatial resolution is CIF, Common Intermediate Format (Note 2);
+
+V3: television broadcasting quality (ITU-R Recommendation BT.601);
+
+V4: high definition television quality.
+
+NOTE 1 – The smoothness of the movement in the displayed image depends on the ability of the system to convey rapid changes; the amount of information which has to be transmitted will of course increase with the area of the picture affected and the speed of the movement. It is generally considered that in a normal videophone or videoconference environment, only part of the picture will be moving and that any fast movement will be limited to a very small portion of the image. Some degradation of the picture quality such as jerkiness, blurring or other artifacts may be allowed during the brief and exceptional instants when these conditions are not met.
+
+NOTE 2 – A CIF video signal provides a spatial resolution of 288 lines with 352 picture elements per line for the chrominance, and 144 lines with 176 picture elements per line for the luminance; a QCIF video signal provides a spatial resolution of 144 lines with 176 picture elements per line for the luminance, 288 lines with 352 picture elements per line for the chrominance; a SQCIF video signal provides a spatial resolution of 96 lines with 128 picture elements per line for the luminance, 48 lines with 64 picture elements per line for the chrominance.
+
+##### A.2.2.2 Additional facilities
+
+Various auxiliary features may be offered either as an inherent part of the media component or as a specific function of the terminal. They include:
+
+- higher resolution still pictures or graphics;
+- split-screen techniques;
+- auxiliary or multiple video sources (e.g. multiple cameras in a videoconference);
+- videotape recording/transmission or other video recording equipment;
+- far end source control, e.g. zooming and/or panning of a far end camera;
+- self view (for some services, means must be provided for displaying the outgoing picture, either permanently or by substituting it on the screen to the incoming picture);
+- various information on the source of the picture, shown for example as text below the picture.
+
+Suspending the video image should be possible in all conversational and conference services, i.e. any participant should be able to prevent his or her image from being transmitted. A suspended image should be replaced by an adequate notice.
+
+This list is not exhaustive and may be extended due to the needs of specific services or applications.
+
+If there are several local image sources, then an indication should be given of which one is sent out.
+
+##### A.2.2.3 Requirements for various audiovisual services
+
+The levels of video quality required for various services are the following:
+
+| Service                 | V0 | V1 | V2 | V3 | V4 |
+|-------------------------|----|----|----|----|----|
+| PSTN videotelephone     | X  |    |    |    |    |
+| Mobile videotelephone   | X  | X  | X  |    |    |
+| ISDN videotelephone     |    | X  | X  |    |    |
+| Desk-top videotelephone |    | X  | X  |    |    |
+| Videoconference         |    | X  | X  | X  |    |
+| Video surveillance      |    | X  | X  | X  |    |
+| Video distribution      |    |    |    | X  | X  |
+| Video retrieval         |    |    |    | X  | X  |
+
+This table is not exhaustive; its main purpose is to illustrate the use of the different levels of quality, and particularly the fact that a given service may be offered at different quality levels.
+
+#### A.2.3 Quality aspects
+
+##### A.2.3.1 Video quality
+
+Video quality is a measure of the ability of a video transmission system to accurately reproduce moving scenes. Video quality objectives are generally expressed in terms of spatial and temporal resolution, but other parameters may also be relevant (e.g. distortion, signal loss or errors). The requirements will be specified according to the desired quality level.
+
+Aspect ratio should be described together with the spatial resolution.
+
+The number of possible different colours must still be studied.
+
+##### **A.2.3.2 Recovery time**
+
+The recovery time is the time necessary for a picture to build up when the video source is changed. It is an important parameter for multipoint conference services and should be kept low enough so as not to disturb the meeting.
+
+##### **A.2.3.3 Overall delay**
+
+The overall delay is defined as the sum of the transmission delay and the characteristic delay of the terminals, i.e. the delay introduced by the terminals when there is no movement or only very small movements in the transmitted image (e.g. when only the lips and eyes of the users are moving). The subjective effect of this delay on the quality of service has to be taken into account because an excessive value may impair user acceptability. The requirements depend on the specific service.
+
+#### **A.2.4 Intercommunication**
+
+The various audiovisual/multimedia services should as much as possible be able to intercommunicate, particularly when they are used for the same type of application. This is usually achieved by a fall-back mechanism to the lower quality level.
+
+Intercommunication should be achieved between levels V1 and V2, and between levels V3 and V4.
+
+Levels V0 and V1 are both used for videophone services, and therefore intercommunication is desirable.
+
+#### **A.2.5 Description of the static aspects**
+
+For further study.
+
+#### **A.2.6 Description of the dynamic aspects**
+
+For further study.
+
+### **A.3 Media component text**
+
+#### **A.3.1 Definition**
+
+The media component text allows for the capture and representation of information, its transfer from originating user(s) to destination user(s), its presentation to human user(s), processing, filing and retrieval.
+
+#### **A.3.2 Description**
+
+##### **A.3.2.1 General description**
+
+Text is a representation medium consisting of formatted characters. It is stored and transmitted as a sequence of codes. Although it may be displayed on the same screen as video and still pictures, it requires decoding into specific fonts for presentation to the user, whether on the screen or on paper. The input is through a keyboard. The output may be a printer or a screen.
+
+The following levels of quality are defined:
+
+T0: minimum quality, basic alphabet and punctuation, no formatting or choice of font;
+
+T0 *bis*: videotex quality, basic alphabet and punctuation, basic graphic character set, no formatting or choice of font;
+
+T1: Usable text conversation quality characterized by:
+
+Font support for ISO-10646-1 Language area Latin-1 plus the target language area for the implementation.
+
+No more than 1 corrupted, dropped or marked missing character per 100.
+
+Delay from character input in the transmitter to display in the receiver shorter than 2 s.
+
+- T2: Good text conversation quality characterized by:  
+ Font support for all characters in ISO-10646-1.  
+ No more than 1 corrupted, dropped or marked missing character per 500.  
+ Delay from character input in the transmitter to display in the receiver shorter than 1 s.
+
+##### A.3.2.2 Additional facilities
+
+The user may be given control over text through editing and presentation functions. He may also be able to insert graphics, still pictures or animated pictures within the text.
+
+##### A.3.2.3 Requirements for various audiovisual services
+
+When text is the support for conversational services, the timing aspects of text entry and display are critical. Text may be transmitted and displayed in near real time, as text is entered. It may also be transmitted only after specific end-of-sentence action or on a specific send request. In a conversation between two users, the near real-time conversation is important for optimized benefit of the conversation. For multi-user conferences, a sentence based transmission may be more relevant in an open discussion, while for a subtitled speech, the real-time text transmission is preferred.
+
+For retrieval services, it may be accepted to transmit and display a whole page of text in one operation.
+
+For conversation, editing may be reduced to "new line", "erase last character", while the editing for information retrieval should contain a possibility to replace text anywhere on the page and add various formatting effects to any part of text. Annotations that stand out distinctly are also desirable.
+
+The levels of text quality required for various services are the following:
+
+| Service            | T0 | T0 bis | T1 | T2 |
+|--------------------|----|--------|----|----|
+| Telex              | X  |        |    |    |
+| Videotex           |    | X      |    |    |
+| Text telephony     |    |        | X  | X  |
+| Total Conversation |    |        |    | X  |
+| Messaging services |    |        | X  | X  |
+| Retrieval services |    |        | X  | X  |
+
+#### A.3.3 Quality Aspects
+
+The quality of text depends mainly upon the capabilities for formatting and using different types of fonts and special characters. When no error correction is made, for instance in conversation, text quality is also measured in terms of corrupted characters, dropped characters and characters replaced by the missing text marker (see ITU-T Recommendation T.140).
+
+#### A.3.4 Intercommunication
+
+The characters with their formatting may be decoded and assembled into bit maps which can then be handled as still pictures, e.g. as facsimile pages.
+
+### A.4 Media component graphics
+
+#### A.4.1 Definition
+
+The media component graphics allows for the capture and representation of information, its transfer from originating user(s) to destination user(s), its presentation to human user(s), processing, filing and retrieval. This media component allows graphic pictures to be captured and transmitted as
+
+geometrical objects whose positions, shapes and colours are coded so that they can be reproduced in a distant terminal.
+
+#### **A.4.2 Description**
+
+##### **A.4.2.1 General description**
+
+Graphics is a representation medium consisting of geometrical objects featured by their positions, shapes and colours. It is stored and transmitted as a set of codes and parameters. Although it may be displayed on the same screen as video and still pictures, it requires decoding into specific geometrical figures for presentation to the user, whether on a screen or on paper.
+
+The input may be through a graphics tablet, an electronic pencil, some other two-dimensional transducer or a dedicated graphic software on a microcomputer or workstation. The output device may be a printer or a screen.
+
+##### **A.4.2.2 Additional facilities**
+
+For further study.
+
+##### **A.4.2.3 Requirements for audiovisual services**
+
+For further study.
+
+#### **A.4.3 Quality aspects**
+
+The intrinsic quality of the graphic depends on the number and the complexity of the objects that can be generated, the precision of their dimensions and positions, the number of possible colours. The overall quality perceived by the user depends also on the resolution of the input and output systems.
+
+#### **A.4.4 Intercommunication**
+
+The graphic objects may be decoded and assembled into bit maps which can then be handled as still pictures.
+
+#### **A.4.5 Description of static aspects**
+
+For further study.
+
+#### **A.4.6 Description of dynamic aspects**
+
+For further study.
+
+### **A.5 Media component still pictures**
+
+#### **A.5.1 Definition**
+
+The media component still picture allows for the capture and representation of information, its transfer from originating user(s) to destination user(s), its presentation to human user(s), processing, filing and retrieval.
+
+#### **A.5.2 Description**
+
+##### **A.5.2.1 General description**
+
+Still pictures is a pixel-based representation medium. They are initially digitized as bit maps, i.e. as one or several bits allocated to each pixel and coding for its colour. The simplest bit map has one bit per pixel indicating whether it is black or white; several bits per pixel are required to code for grey levels, and for a colour picture, each of the three basic colours has to be coded for. Because of the large volume of data generated, the data is then usually compressed by using the correlation between different parts of the picture and often by accepting a limited amount of degradation through loss of
+
+information. Depending upon the application, the same types of transducers as for video may be used (cameras, screens), or scanners and printers. Two types of standards exist presently:
+
+- facsimile standards which in the basic versions have only two levels, black and white (1 bit per pixel before compression), but can be extended to grey levels or to colour;
+- general still pictures coding schemes such as T.81 (ISO-JPEG) and T.82 (ISO-JBIG) with various possible sets of parameters or profiles.
+
+The contents of the still pictures may also be text and graphics, and basic facsimile is indeed designed for that purpose, but the patterns in the picture are not identified as such and thus cannot be modified. It should also be noted that at the final presentation stage, whether on screen or on paper, text and graphics are usually converted to a bit map, i.e. to a still picture.
+
+##### **A.5.2.2 Additional facilities**
+
+**Pointer** – A pointer facility allows a small graphic object to be superimposed on the picture; the size, shape and colour of this object may be fixed, or chosen between predetermined models or transmitted when opening the facility; it may be moved on the picture by one of the users and its position is sent in real-time to the distant terminal(s) for display. The interface through which the presenter moves the pointer is an implementation matter (for instance, a mouse, a joystick, an electronic pen, etc.). The role of the presenter is allocated to one terminal at a time, but may be moved from one terminal to the other.
+
+##### **A.5.2.3 Requirements for various audiovisual services**
+
+For further study.
+
+#### **A.5.3 Quality aspects**
+
+The quality of the picture may be defined by the number of pixels and the number of possible colours. If the picture is compressed for storage or transmission, then defects may be generated that will degrade the quality of the picture. The assessment of the resulting quality is for further study.
+
+#### **A.5.4 Intercommunication**
+
+Intercommunication with video: a still picture may be repeated and handled as a video sequence.
+
+Intercommunication with text: if the still picture represents characters, it may be converted into text by character recognition software.
+
+#### **A.5.5 Description of static aspects**
+
+For further study.
+
+#### **A.5.6 Description of dynamic aspects**
+
+For further study.
+
+### **A.6 Media component data**
+
+#### **A.6.1 Definition**
+
+The media component data allows for the capture and representation of information, its transfer from originating user(s) to destination user(s), its presentation to human user(s), processing, filing and retrieval. Data consists of a sequence of bits. It is often organized in files, i.e. in finite sequences.
+
+#### **A.6.2 Description**
+
+##### **A.6.2.1 General description**
+
+Two types of files may be defined depending upon their contents:
+
+- software files, used to store or to download software;
+- data files, i.e. finite sequences of bits arranged according to a set of rules and associated with a given software, which is needed to generate it, modify it or use it.
+
+Data files are not a media component according to the F.700 definition, because they are not associated with any unique perception medium, but they may support various types of media components for storage and transmission purposes. They are commonly used for text or graphics, but they may also support still pictures or short sequences of sound or moving pictures. They may also contain data for various applications.
+
+##### **A.6.2.2 Additional facilities**
+
+###### **Local facilities**
+
+The associated software is usually able to perform various functions such as generating, modifying, deleting parts, etc.
+
+###### **Remote operations**
+
+Specific software may also allow remote operation, such as cooperative data handling or retrieval in a remote database.
+
+##### **A.6.2.3 Requirements for various audiovisual services**
+
+For further study.
+
+#### **A.6.3 Quality aspects**
+
+For further study.
+
+#### **A.6.4 Intercommunication**
+
+Media components may be converted into data files through an appropriate software. Conversely, these files may be converted back into the original media component or to another media component. For instance, text or graphics may be converted into a bit map, i.e. a still picture. A still picture may also be extracted from a file containing a short video sequence.
+
+#### **A.6.5 Description of static aspects**
+
+For further study.
+
+#### **A.6.6 Description of dynamic aspects**
+
+For further study.
+
+## Communication tasks descriptions
+
+### **B.1 Communication task conversing**
+
+#### **B.1.1 Definition**
+
+The generic communication task conversing provides for point-to-point real-time (isochronous) exchange of information between two users. The users may be humans or machines. The information may be monomedium as well as multimedia.
+
+#### **B.1.2 Description**
+
+The communication task conversing provides the basic means for a conversation between two users in different locations. In the case of human users, it uses the media component audio and, when required by the service, the media component video, each of them with different possible levels of quality. When both of them are present, they may be synchronized so that visual and aural perception of events will appear to the distant user as fitting together naturally, and in particular so that the movement of the lips will match the sound of the voice. Other synchronization requirements are supported as well.
+
+The communication is usually symmetrical, but this is not mandatory. For instance, when one of the users wants to show the details of some object, he may transmit pictures with a higher quality level than he receives, if the system supports this configuration.
+
+### **B.1.3 Quality aspects**
+
+##### **B.1.3.1 Audio and video quality**
+
+The quality levels for each media components are defined separately (see Annex A). The correlation between them results from the requirements of the application and the limitations of the system (for instance, a fixed overall bit rate may impose a choice between audio and video quality).
+
+##### **B.1.3.2 Synchronization**
+
+When video and audio are present, they should be synchronized, in particular in order to ensure apparent lip synchronization. The required precision of the synchronization depends upon the quality levels of the service components and is of the order of a few tens of milliseconds. The exact values are for further study.
+
+When the overall delays are different for various media components, they have to be aligned on the longer delay.
+
+When the differential delays in various parts of the connection are implementation dependent, they should be aligned separately within each part, or the relevant information should be transferred for final adjustment in the receiving terminal.
+
+NOTE – In applications where synchronization is not essential, the user should be able to disable the mechanism.
+
+#### **B.1.4 Intercommunication**
+
+Intercommunication is achieved at the media component level, independently for each of them but without destroying their synchronization. Media components may be dropped if they are not available in both terminals.
+
+#### B.1.5 Static aspects
+
+The static aspects of communication tasks are described using the following attributes in Table B.1.
+
+**Table B.1/F.700 – Communication task conversing attributes**
+
+| Attribute                     | Value                                                                                                                                                                                                                                                                  |
+|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Configuration                 | Point-to-point                                                                                                                                                                                                                                                         |
+| Symmetry                      | Bidirectional                                                                                                                                                                                                                                                          |
+| Response time                 | Real-time, near-real-time                                                                                                                                                                                                                                              |
+| Time continuity               | Isochronous                                                                                                                                                                                                                                                            |
+| Mandatory media components    | All are possible, and an option is none                                                                                                                                                                                                                                |
+| Optional media components     | All are possible, and an option is none                                                                                                                                                                                                                                |
+| Media component interrelation | – Synchronization between: <ul style="list-style-type: none"><li>• audio and video (lip synchronism, location related synchronism)</li><li>• audio and text (voice synthesis)</li><li>• text and video/picture/graphics (subtitles synchronized with images)</li></ul> |
+
+### B.2 Communication task conferencing
+
+#### B.2.1 Definition
+
+The generic communication task conferencing provides for multipoint real-time exchange of information among multiple users. The users may be humans or machines. The information may be monomedium as well as multimedia. It includes the control functions required for chairing a conference or controlling the use of a facility.
+
+#### B.2.2 Description
+
+##### B.2.2.1 General description
+
+The communication task conferencing provides the basic means for various types of meetings of groups of users distributed in two or more locations. In the case of human users, it will usually use the media component audio, and optionally video and/or other media components, each of them with different possible levels of quality. When video is present, it is synchronized with audio from the same location so that visual and auditory perception of events will appear to the distant user as fitting together naturally and, in particular, so that the movement of the lips will match the sound of the voice.
+
+The use of this communication task for computer conferences is for further study.
+
+##### B.2.2.2 Operation of the various media components
+
+###### B.2.2.2.1 Audio
+
+The sounds from the various terminals may be mixed, switched, or a combination of both. In the mixing mode, each terminal receives the sound from all other terminals except its own sound (thus avoiding echo). When many terminals are present, it is advisable for users to mute their microphones (i.e. prevent the sound from being transmitted) when they are not speaking in order to reduce the addition of noises and the risk of unwanted perturbations. For the same purpose, some systems may limit, possibly to one only, the number of audio sources simultaneously received by a terminal. How the sources are selected is described in a subsequent subclause.
+
+###### **B.2.2.2.2 Video**
+
+In the basic mode, the video is switched so that only one picture is transmitted to each terminal. In more elaborate modes, several pictures are used. They can be separate pictures, or combined as several windows on the same screen. In the "continuous presence" mode, all locations can be viewed permanently. The number of locations can then be at most equal to the number of available windows plus one. If the number of locations is larger, this mode of operation is not possible and some switching is necessary for selecting the sources of the pictures displayed in each location.
+
+###### **B.2.2.2.3 Other media components**
+
+Data channels may be used to transmit still pictures, text, graphics, or other types of data. Circuit-oriented data channels only allow point-to-point transmission between terminals of the conference or broadcasting from one terminal at a time. Packet-oriented channels are more flexible; they may be shared by several sources at a time and with different types of data simultaneously. Limitations may however also occur from other resources that cannot be shared or from saturation of the transmission channel when the amount of data transferred takes up a large part of the available bit rate. Creation, presentation, representation and processing of these information types may be done using either the same or different functions and devices.
+
+##### **B.2.2.3 Control functions**
+
+The control functions required for managing the conference are described in C.1, middleware service element conference control.
+
+#### **B.2.3 Quality aspects**
+
+##### **B.2.3.1 Media components quality**
+
+The quality levels for the various service components may be defined separately. The correlation among them results from the requirements of the application and the limitations of the system (for instance, a fixed overall bit rate may impose a choice between audio and video quality, and reduce the quality when transfer of several information types occurs).
+
+##### **B.2.3.2 Synchronization**
+
+When video is present, it should be synchronized with the audio from the same source, in particular in order to ensure apparent lip synchronism. The synchronism should be maintained over the various paths that the signals may follow to reach the different terminals in the conference. When the differential delays in various parts of the connections are implementation dependent, they should be aligned separately within each part, or the relevant information should be transferred for final adjustment in the receiving terminals.
+
+#### **B.2.4 Intercommunication**
+
+Intercommunication is achieved at the media components level, independently for audio, video and data. Audio is always present, the video and other media components may be dropped if they are not available in all terminals. When audio and video are present, synchronization should be maintained between them with audio.
+
+Alternately, different status may be given to the terminals: a primary status to those terminals supporting the media components and functions selected for the conference with the appropriate quality levels, a secondary status for terminals that do not meet these requirements and will then only be able to participate with some of the components and functions.
+
+#### B.2.5 Description of the static aspects
+
+The static aspects of communication tasks are described using the following attributes in Table B.2.
+
+**Table B.2/F.700 – Communication task conferencing attributes**
+
+| Attribute                      | Value                                                                                                                                                                                                                                                                                                                           |
+|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Configuration                  | Multipoint-to-multipoint                                                                                                                                                                                                                                                                                                        |
+| Symmetry of information flow   | Bidirectional                                                                                                                                                                                                                                                                                                                   |
+| Response time aspect           | Real-time or near-real-time                                                                                                                                                                                                                                                                                                     |
+| Time continuity                | Isochronous for audio and video<br>Non-isochronous for other media components                                                                                                                                                                                                                                                   |
+| Mandatory media components     | All are possible, and an option is none                                                                                                                                                                                                                                                                                         |
+| Optional media components      | All are possible, and an option is none                                                                                                                                                                                                                                                                                         |
+| Media components interrelation | – Synchronization between: <ul style="list-style-type: none"><li>• audio and video (lip synchronism, location related synchronism);</li><li>• audio and text (voice synthesis);</li><li>• text and video/picture/graphics (subtitles synchronized with images);</li><li>• synchronization between audio and graphics.</li></ul> |
+
+### B.3 Communication task distributing
+
+#### B.3.1 Definition
+
+The communication task distributing provides for the transfer of information from one user to (more than one) other users with the information source being the controlling entity. The users may be humans or machines. The information may be monomedium as well as multimedia.
+
+#### B.3.2 Description
+
+##### B.3.2.1 General description
+
+The communication task distributing provides the basic means to support all kinds of point-to-multipoint applications by providing the capabilities to transmit information to more than one other user or to storage.
+
+The information distributed to other users or storage (representing the information sinks) may be monomedium as well as multimedia, thus meaning that the use of one or some or all of the media components described in Annex A may be required. Requirements for any interrelation between any of them, e.g. any synchronization requirements, will be supported.
+
+The communication, i.e. the exchange of user information (user plane) is unidirectional, whereas necessary control information (control plane) may be exchanged in both ways.
+
+##### **B.3.2.2 Operation of the various media components**
+
+##### **B.3.2.3 Control functions**
+
+#### **B.3.3 Quality aspects**
+
+##### **B.3.3.1 Media component quality**
+
+The quality levels for each media component are defined separately (see Annex A). The correlation between them results from the requirements of the application and the limitations of the system (for instance, a fixed overall bit rate may impose a choice between audio and video quality).
+
+##### **B.3.3.2 Synchronization**
+
+When video and audio are present, they should be synchronized, in particular to ensure lip synchronization. The required precision of synchronization depends on the quality levels of the media components and is of the order of a few tens of milliseconds. The exact values are for further study.
+
+When the overall delays are different for various media components, they have to be aligned on the longer delay.
+
+When differential delays in various parts of the connection are implementation dependent, they should be aligned separately within each part, or the relevant information should be transferred for the final adjustment in the receiving terminal.
+
+#### **B.3.4 Intercommunication**
+
+Intercommunication is achieved at the media component level, independently for each but without destroying synchronization. Media components may be dropped if they are not available in all terminals.
+
+#### **B.3.5 Static aspects**
+
+The static aspects of communication tasks are described using the following attributes in Table B.3.
+
+**Table B.3/F.700 – Communication task distributing attributes**
+
+| <b>Attribute</b>              | <b>Value</b>                            |
+|-------------------------------|-----------------------------------------|
+| Configuration                 | Point-to-multipoint                     |
+| Symmetry                      | Unidirectional                          |
+| Response time                 | All are possible                        |
+| Time continuity               | All are possible                        |
+| Mandatory media components    | All are possible, and an option is none |
+| Optional media components     | All are possible, and an option is none |
+| Media component interrelation | Synchronization possible                |
+
+### **B.4 Communication task sending**
+
+#### **B.4.1 Definition**
+
+The generic communication task sending provides for point-to-point real-time and non-real-time transfer of information from one user to another with the information source being the controlling entity. The users may be humans or machines. The information may be monomedium as well as multimedia.
+
+#### **B.4.2 Description**
+
+##### **B.4.2.1 General description**
+
+The communication task sending provides the basic means to support all kinds of messaging applications by providing the capabilities to transmit information to another user or to storage.
+
+The information sent to the other user or to storage (representing the information sink) may be monomedium as well as multimedia, thus meaning that the use of one or some or all of the media components described in Annex A may be required. Requirements for any interrelation among any of them, e.g. any synchronization requirements, will be supported.
+
+The communication, i.e. the exchange of user information (user plane) is unidirectional, while the necessary control information (control plane) may be exchanged in both ways.
+
+##### **B.4.2.2 Operation of the various media components**
+
+##### **B.4.2.3 Control functions**
+
+#### **B.4.3 Quality aspects**
+
+##### **B.4.3.1 Media component quality**
+
+The quality levels for the various service components may be defined separately (see Annex A). The correlation among them results from the requirements of the application and the limitations of the system.
+
+##### **B.4.3.2 Synchronization**
+
+When video and audio are present, they should be synchronized, in particular in order to ensure apparent lip synchronicity.
+
+When the overall delays are different for the various information types, they have to be aligned on the longer delay.
+
+When different delays in various parts of the communication are implementation dependent, they should be aligned separately within each part, or the relevant information should be transferred for final adjustment in the receiving terminal.
+
+#### **B.4.4 Intercommunication**
+
+Intercommunication is achieved at the media component level independently for each media component but supporting synchronization and other interrelation requirements. Media components may be dropped if they are not available in all terminals.
+
+#### **B.4.5 Static aspects**
+
+The static aspects of the communication task sending are described using the following attributes in Table B.4.
+
+**Table B.4/F.700 – Communication task sending attributes**
+
+| <b>Attribute</b>              | <b>Value</b>                            |
+|-------------------------------|-----------------------------------------|
+| Configuration                 | Point-to-point                          |
+| Symmetry                      | Unidirectional                          |
+| Response time                 | All are possible                        |
+| Time continuity               | All are possible                        |
+| Mandatory media components    | All are possible, and an option is none |
+| Optional media components     | All are possible, and an option is none |
+| Media component interrelation | Synchronization possible                |
+
+### **B.5 Communication task receiving**
+
+#### **B.5.1 Definition**
+
+The generic communication task receiving provides for point-to-point transfer of information from one user to another user with the information sink being the controlling entity. The users may be humans or machines. The information may be monomedium as well as multimedia.
+
+#### **B.5.2 Description**
+
+##### **B.5.2.1 General description**
+
+The generic communication task receiving provides part of the basic means to support any kind of retrieval aspects of an application by providing the capabilities to get information from some kind of store into which some other user has previously put the information using the communication tasks sending or distributing (see Annex B).
+
+The information received from the store (representing the information source) may be monomedium as well as multimedia, thus meaning that the use of one or some or all of the media components described in Annex A may be necessary. Requirements for any interrelation among any of them, e.g. synchronization with media components audio or video and text, or any kind of conditional relation, will be supported.
+
+The communication, i.e. the exchange of user information (user plane) is unidirectional, whereas necessary control information (control plane) may be exchanged in both ways.
+
+#### **B.5.3 Quality aspects**
+
+##### **B.5.3.1 Media component quality**
+
+The quality of each media component is defined separately (see Annex A).
+
+##### **B.5.3.2 Synchronization**
+
+Synchronization requirements and their required precision depend on the application to be supported by the multimedia service requiring the communication task receiving.
+
+Overall delays may be different for the various information types. They will be aligned on the longer delay.
+
+When different delays in various parts of the communication are implementation dependent, they should be aligned separately within each part, or the relevant information should be transferred for final adjustment in the receiving terminal.
+
+#### **B.5.4 Intercommunication**
+
+Intercommunication is achieved at the media component level independently for each media component but supporting synchronization and other interrelation requirements.
+
+#### **B.5.5 Static aspects**
+
+The static aspects of the communication task sending are described using the following attributes in Table B.5.
+
+**Table B.5/F.700 – Communication task receiving attributes**
+
+| <b>Attribute</b>              | <b>Value</b>                            |
+|-------------------------------|-----------------------------------------|
+| Configuration                 | Point-to-point                          |
+| Symmetry                      | Unidirectional                          |
+| Information control entity    | Sink                                    |
+| Response time                 | All are possible                        |
+| Time continuity               | All are possible                        |
+| Mandatory media components    | All are possible, and an option is none |
+| Optional media components     | All are possible, and an option is none |
+| Media component interrelation | Synchronization possible                |
+
+### **B.6 Communication task collecting**
+
+#### **B.6.1 Definition**
+
+The communication task collecting provides for the transfer of information from (more than one) users to one user with the information sink being the controlling entity. The users may be humans or machines. The information may be monomedium as well as multimedia.
+
+The information sources are anticipated to be machines whereas the controlling information sink may be a person or a machine. The user information may be monomedium as well as multimedia.
+
+#### **B.6.2 Description**
+
+##### **B.6.2.1 General description**
+
+The generic communication task collecting provides part of the basic means of supporting any polling system but providing the capabilities to get information from some kind of store into which other users have previously placed the information, possibly using the communication tasks sending or distributing (see Annex B).
+
+The information received from the store (information source) may be monomedium as well as multimedia, thus meaning that the use of media components described in Annex A may be required. Requirements for any interrelation among any of them will be supported.
+
+With regard to each of the relations between the information sink and one of the information sources, the communication, i.e. the exchange of user information (user plane) is unidirectional, whereas the necessary control information (control plane) may be exchanged in both ways.
+
+##### **B.6.2.2 Operation of the various media components**
+
+###### **B.6.2.2.1 Audio**
+
+When the collecting user is simultaneously collecting audio information from more than one information source, it should be possible to present the collected information.
+
+###### **B.6.2.2.2 Video**
+
+When the collecting user is simultaneously collecting video information from more than one information source, it should be possible to present the collected information.
+
+##### **B.6.2.3 Control functions**
+
+###### **B.6.2.3.1 General aspects**
+
+Requests for transmission of information are issued by the information sink to the information source, which is expected to send an immediate response indicating whether the information is available.
+
+In the conducted mode, a positive response is immediately transferred into a message initiating the information transfer.
+
+###### **B.6.2.3.2 Navigation**
+
+Navigation functions allow the collecting user to select the information to be transferred from the information offered. This requires further study.
+
+#### **B.6.3 Quality aspects**
+
+##### **B.6.3.1 Media component quality**
+
+The quality levels for each media component are defined separately (see Annex A).
+
+##### **B.6.3.2 Synchronization**
+
+Synchronization requirements and their required precision depend on the application to be supported by the multimedia service requiring the communication task collecting. Overall delays may be different for the various information types. They may need to be aligned on the longer delay.
+
+When differential delays in various parts of the communication are implementation dependent, then they should be aligned separately within each part, or the relevant information should be transferred for final adjustment in the receiving terminal.
+
+#### **B.6.4 Intercommunication**
+
+Intercommunication is achieved at the media component level, independently for each media component but supporting synchronization and other interrelational requirements.
+
+#### **B.6.5 Static aspects**
+
+The static aspects of the communication task sending are described using the following attributes in Table B.6.
+
+**Table B.6/F.700 – Communication task collecting attributes**
+
+| <b>Attribute</b>               | <b>Value</b>                            |
+|--------------------------------|-----------------------------------------|
+| Configuration                  | Multipoint-to-point                     |
+| Symmetry                       | Unidirectional                          |
+| Information controlling entity | Sink                                    |
+| Time aspects                   | All are possible                        |
+| Time continuity                | All are possible                        |
+| Mandatory media components     | All are possible, and an option is none |
+| Optional media components      | All are possible, and an option is none |
+| Media component interrelation  | Synchronization possible                |
+
+# ANNEX C
+
+## Middleware service elements descriptions
+
+## C.1 Middleware service element *Conversation Control*
+
+#### C.1.1 Definition
+
+The generic middleware service element *Conversation Control* provides the control functions for point-to-point real-time exchange of information between two users
+
+#### C.1.2 Description
+
+The generic middleware service element *Conversation Control* provides the basic means for managing various types of conversations. It is related to the generic communication task conversing described in B.1. It controls the operation of the various media components, allowing appropriate channels to be opened and used between the terminals.
+
+#### C.1.3 Control functions
+
+At the beginning of the call, the terminals exchange information on their capabilities and a common mode of communication is chosen. This is usually an automatic process, but the users may intervene when several modes are available or if they want to avoid the use of one or more media components (for instance a user may not want his image to be sent out, or he may want to limit the bandwidth in order to reduce the cost).
+
+During the course of the communication, a change of mode may also be initiated, adding or suppressing a media component or changing the bandwidths allocated to the various media components.
+
+#### C.1.4 Implementation
+
+There are two possible levels of complexity for the control functions:
+
+- Level 1 uses only the basic signals in the control channel of the multiplex, with limitations in the capacity of the channel and in the available commands.
+- Level 2 uses a packet-oriented data channel with a multilevel protocol defined in the T.120 series of Recommendations on which control data and user data are multiplexed; it is more flexible and offers enhanced control capabilities for optional functions.
+
+NOTE – For ISDN, the level 1 channel is defined in Recommendations H.221 and H.230, supporting the procedures of H.242. On other networks equivalent Recommendations are H.222.0 and H.245.
+
+## C.2 Middleware service element *Conference Control*
+
+#### C.2.1 Definition
+
+The generic middleware service element *Conference Control* provides the control functions for multipoint real-time exchange of information among multiple users. It includes the control functions required for chairing a conference or controlling the use of a facility.
+
+#### C.2.2 Description
+
+##### C.2.2.1 General description
+
+The middleware service element *Conference Control* provides the basic means for managing various types of meetings of groups of users distributed in two or more locations. It is related to the generic communication task conferencing described in B.2. It controls the operation of the various media components, allowing each terminal to transmit them when appropriate and deciding how they will be combined, multiplexed or switched for transmission to each terminal. To this end it elaborates the
+
+control and indication signals exchanged among the terminals and MCUs, and it sends them to the appropriate site.
+
+The use of this MSE for computer conferences is for further study.
+
+##### **C.2.2.2 Operation of the various media components**
+
+The operation of the various media components is described in B.2.2.2. It depends upon the type of medium, the available transmission channels and the capabilities of the MCUs for combining the signals. The control functions vary accordingly.
+
+#### **C.2.3 Control functions**
+
+##### **C.2.3.1 General aspects**
+
+In a multipoint configuration, several terminals are liable to transmit or try to transmit at the same time, and control functions are required to arbitrate between them whenever limitations exist on the number of signals simultaneously handled by various parts of the system. Requests for transmission (explicit or implicit) are received by the control system of the conference, which takes appropriate action in response.
+
+Two modes of control are defined:
+
+- 1) An unconducted mode in which all actions are automatic responses from the system: All terminals then have equal rights for transmitting on the channels allocated to the various media and for issuing commands to the control system; they may however temporarily acquire exclusive rights for using a given facility (e.g. by requesting an appropriate token from the control system, or by starting to use the facility while it is free, or otherwise).
+- 2) A conducted mode in which some of the requests are forwarded to a specific terminal (the control terminal) and action is taken according to the commands from that terminal: This mode is only optional, but its availability is desirable for the management of conferences with many participants or with elaborate terminals. Control terminals may be conferred three types of privileges, either separately or jointly:
+  - a) access control, i.e. management of the conference call (call control); this function belongs to the service level and is described in Recommendation F.702;
+  - b) chair control, i.e. management of the media audio and video components in order to give the floor to the various participants;
+  - c) facility control, i.e. management of a facility and the related corresponding data channel and resources.
+
+In the simpler systems, these functions may be merged, but it is preferable to keep them separate. They can usually be transferred from one terminal to another through a token or by some other method.
+
+##### **C.2.3.2 Audio and video**
+
+The control of audio and video signals uses various schemes depending on the mode for each component. In the continuous presence mode, audio and video from all other locations are permanently available on each site and no control is needed for these two components. In all other cases, selection is necessary for one component or for both. The criteria for this selection are the requests sent by the terminals and the level of the sounds from these terminals, which is monitored when automatic switching is performed.
+
+###### 1) *Unconducted mode*
+
+In basic systems, each terminal receives the sounds from all other terminals and only one video signal. The video channels are then voice switched, i.e. the image from the terminal with the loudest sound (the speaker) is broadcast to all other terminals. A suitable delay
+
+and/or threshold avoid repeated switching which would be uncomfortable for the users, especially if the codec requires some time for building up a new picture. The speaker may receive the video from the previous speaker, or cyclically the video from the other terminals, or he may be able to select the picture he wants to receive, depending on implementation.
+
+Any participant may optionally make a request to select the video from a specific source, and if the system supports this function, he will receive it when available (limitations may arise from the conference system or from the transmission paths).
+
+Any participant can have his video broadcast to every terminal, provided there is no similar request active. This overrides all previous commands for selecting the video received, but subsequent requests for video selection will be accepted, only subject to availability of the requested signals.
+
+If the system is able to simultaneously convey the video from several terminals, then various schemes are possible. For instance, the latest speakers may be displayed, or only the present speaker with other pictures selected by the user, or any other combination. This is left to the implementor, but the picture of the present speaker should always be included unless the user expressly makes another choice.
+
+If voice is also switched, then it is submitted to the same rules.
+
+###### 2) *Conducted mode: chair control*
+
+The chairman controls who has the floor: if one or both of the audio and video signals are switched, he decides whose picture and/or voice will be broadcast. When a participant wants to speak, he has to send a request for the floor which the conference control system forwards to the chairman, who may send back commands to grant it or deny it. Giving the floor to a terminal means that the system broadcasts to all other terminals those of the video and audio signals that are switched. Another terminal may request signals from some specific source to be sent to it instead, and the system will comply whenever possible; reasons for denial might be that this function is not supported by the system, that it has been prohibited (for instance, a buyer in an auction sale may want to be identified only by the auctioneer), or that the requested signal is not available.
+
+If the signals from several sources can be transferred and presented simultaneously, then usually only one of them is controlled by the chairman; the other one(s) may be, for instance, allocated to the previous speaker(s), or to the chairman or selected by the user.
+
+In the continuous presence mode, there is usually no chair control on the audio and video because there is no switching, although the chairman might be able to mute a distant terminal.
+
+##### C.2.3.3 Other information types
+
+Control of transmission of other information types is dependent on the type of channel that supports it: on a circuit-oriented channel, only one terminal can transmit at a time and control of the channel is required; packet-oriented channels are more flexible and control functions are already embedded in the associated protocol, but control of other resources may still be required. Thus, three modes may be defined: two with allocation of resources and one with shared resources.
+
+###### 1) *Unconducted mode with allocation of resources*
+
+Only one terminal at a time is able to transmit (or possibly a limited number of terminals). To resolve possible conflicts between terminals, the control system allocates resources to one terminal at a time (or to a limited number of terminals). Terminals may send requests for transmission to the control system of the conference, which allocates in response the appropriate resources if they are available (this process may be implicit if the terminal itself detects the availability of resources and takes them up by starting to transmit). If the attempt
+
+fails, the terminal may renew its request later on or the control system may set up a queuing mechanism (Note 1).
+
+###### 2) *Conducted mode: facility control*
+
+The facility controller manages a given facility, which can be, for instance, still pictures, or telewriting, or file transfer; requests for its use are forwarded to him by the control system, which waits for his decision before allocating the corresponding resources. He may also interrupt the use of the facility and hand it over to another participant (Note 1).
+
+When several information types are present, a token is allocated for each independent type; if two types of data are mutually exclusive (for instance, if they use the same fixed channel or the same equipment), then they will share the same token.
+
+###### 3) *Shared resources*
+
+Terminals share a common transmission medium and other common resources which they may use simultaneously (Note 2); in this case they may transmit freely at any time. In case of congestion or if the receiving terminals are already engaged, the transmitter will have to try again, or the message may be stored and forwarded later on.
+
+NOTE 1 – Permission to transmit may be represented by a token. In the unconducted mode, it may be acquired on request while it is free, and should be released when no longer needed. When a terminal has the token, other terminals may also be able to issue a request for it to the owner who may reject it, hand out the token or simply release it. In the conducted mode, the token is allocated by commands from the facility controller.
+
+NOTE 2 – A common transmission medium may also be used in the other modes (with allocation of resources) where it adds flexibility for the simultaneous transfer of several information types and for the control functions.
+
+##### C.2.3.4 Operational aspects
+
+At the beginning of the conference, the default mode is usually non-conducted. Any terminal may then issue a request for taking on a control function and it will be granted.
+
+The chairman will often also take on the role of conference controller, but there are cases when he may not be willing or able to do so (for instance, the chairman of a company will probably want to leave this task to a secretary; similarly, in the case of remote teaching or remote lecturing, the teacher or lecturer will chair the conference while the convener will control the conference and screen the participants when they call). Thus the two functions may need to be split, either in the terminal equipment when both are in the same location, or in the conference control system if they are distant. The same considerations apply to the control of the facilities.
+
+When two or more control responsibilities are jointly allocated, it should be possible to leave some of them idle, i.e. let them revert to the unconducted mode. Control over facilities for which the chair terminal has sent no command should remain idle. This will ensure that facilities that the chairman (or controller) is not willing or able to control can still be used by other participants, in particular optional facilities not present in the chair terminal.
+
+##### C.2.3.5 Private conference/conference splitting
+
+It may be possible to split the conference into two (or more) sub-conferences, if the conference system supports it. It may also be possible to send various information types to one participant or to a group of participants inside the conference. The conditions for this are for further study.
+
+#### C.2.4 Implementation
+
+The control functions are distributed among the terminals and MCUs. Control signals are exchanged among them for this purpose. The MCU (or one of the MCUs when several are present) usually has the leading role in the management of the conference.
+
+There are two possible levels of complexity for the control functions:
+
+- Level 1 uses only the basic signals in the control channel of the multiplex, with limitations in the capacity of the channel and in the available commands.
+- Level 2 uses a packet-oriented data channel with a multilevel protocol defined in the T.120 series of Recommendations on which control data and user data are multiplexed; it is more flexible and offers enhanced control capabilities.
+
+NOTE – For ISDN, the level 1 channel is defined in Recommendations H.221 and H.230, supporting the procedures of Recommendation H.242 and, for multipoint operation, of Recommendation H.243. On other networks equivalent Recommendations are H.222.0 and H.245.
+
+# ANNEX D
+
+## Glossary
+
+The sources of the definitions will be indicated as follows:
+
+{AVI-2} Future ISO standard on AVI scripts in ISO/SC 29/WG 12-MHEG
+
+{F.710} ITU-T Recommendation F.710
+
+{F.711} ITU-T Recommendation F.711
+
+{F.720} ITU-T Recommendation F.720
+
+{F.730} ITU-T Recommendation F.730
+
+{F.740} ITU-T Recommendation F.740
+
+{I.374} ITU-T Recommendation I.374
+
+{MHEG} ISO standard MHEG CD 13522-1
+
+**D.1 audiographic conference service {F.711}:** Is an international service, offered by Administrations, enabling participants to conduct a real-time conference in which audio signals are exchanged together with non-voice graphics information except for motion video.
+
+**D.2 author {F.740}:** The role who mainly creates and validates applications or updates and supplies them to the information manager for their distribution.
+
+**D.3 AVI audiovisual interactive:** This acronym is widely used in standards work in the area of real-time interactive multimedia and hypermedia applications.
+
+**D.4 AVI script {AVI-2}:** Formulation of the logical structure which defines the sequencing and semantic relationships between multimedia and hypermedia objects for the purpose of making them available to a user.
+
+**D.5 AVI scriptware {AVI-2}:** Data interchange format that identifies one or several scripts together with the relevant processes, multimedia and hypermedia objects necessary for the interchange of a complete and consistent package.
+
+**D.6 AVI service {AVI-2}:** Generic retrieval service which provides users with facilities for the controlled interchange of AVI scriptware. See also Recommendation F.740.
+
+**D.7 editing {F.740}:** Creation of applications, including design, use of media, development, verification, modification, updating and validation before the applications become available to the users.
+
+**D.8 execution {F.740}:** Application usage after installation, user interface management, monitoring usage implementation and, where appropriate, upstream connection with an information management system or directly with an editing system in case of an implementation in progress.
+
+**D.9 hypermedia {MHEG}**: The ability to access monomedia and multimedia information by navigating across links.
+
+NOTE – The specialized MHEG links defined in the MHEG standard are not general purpose document links as defined by HyperODA or HyTime.
+
+**D.10 information management {F.740}**: Application management, including storage, classification, catalogue creation and management, retriever and preparer management, tariffs, monitoring usage processing, context recovery management, etc.
+
+**D.11 information manager {F.740}**: The role who mainly defines or modifies user access authorization and tariffing, then provides the execution process with the applications to be executed or their updates.
+
+**D.12 interchange medium {F.740}**: The type of means to interchange data; it can be either a storage, a transmission medium or a combination.
+
+NOTE – Interchange medium can be used to indicate either storage or transmission medium.
+
+**D.13 multimedia object {MHEG}**: A composed object consisting of various different types of related temporal and logical content intended for presentation to a user.
+
+**D.14 perception medium {MHEG}**: The nature of the information as perceived by the user. Examples of auditory perception: speech, noise, music. Examples of visual perception: text, drawings and moving scene.
+
+**D.15 preparer {F.740}**: The role who mainly selects, installs, personalizes and concatenates the applications as well as following up their execution.
+
+**D.16 rendition {F.720}**: The ability of the receiving entity to reproduce motion from transmitted video.
+
+**D.17 retriever {F.740}**: The role who mainly consults the application by interacting with the presentation process.
+
+**D.18 role {F.740}**: Either a person who activates, or a process which has been designed by a person in order to activate a functionality of an AVI application.
+
+**D.19 teleconference service {F.710}**: Is the service that provides the necessary arrangements for a real-time conferencing among single individuals or groups of individuals at two or more locations, by means of telecommunication networks.
+
+The concept of conferencing implies that the exchange of speech signals is always provided for as a basic facility. The use of supplementary facilities, for the exchange of signals other than speech, is to be determined by the conference participants.
+
+For the interconnection of terminal equipment at three or more locations, a specific interconnection facility is required, namely the Multipoint Control Unit (MCU), to which all locations are connected individually. The MCU provides proper distribution of the various signals among the connected locations and takes part in maintaining the proper procedures among the connected terminals.
+
+The TCS is a real-time service which can be divided according to the following categories: audiographic conference service and videoconference service.
+
+**D.20 transmission medium {MHEG}**: The type of physical means to transmit data. For example, twisted pairs, coaxial cable, optical fibres and radio link.
+
+**D.21 videoconference service {F.730}**: Is an audiovisual conversational teleconference service providing bidirectional real-time transfer of voice and moving colour pictures between groups of users in two or more separate locations. The minimum requirement is that under normal conditions the picture information transmitted is sufficient for adequate representation of fluid movements of two or more persons in a typical meeting situation displayed in head and shoulders view.
+
+Although the moving picture information is the essential part of the service, other types of information, such as high resolution still pictures, text or data may also be exchanged.
+
+**D.22 videotelephony service {F.720}:** Is an audiovisual conversational teleservice providing bidirectional symmetric real-time transfer of voice and moving colour pictures between two locations (person-to-person) via the networks involved. The minimum requirement is that under normal conditions the picture information transmitted is sufficient for the adequate representation of fluid movements of a person displayed in head and shoulders view.
+
+# APPENDIX I
+
+## Multimedia medical consultation
+
+## I.1 Prose description
+
+Medical consultation involves interactive multimedia communications between medical experts located at two or more separate locations. This communication is generally initiated by a doctor desiring to discuss a particular patient's case with subject matter experts and may occur between the doctor and one consultant only, or may require an interactive conference arrangement between the doctor and several consultants simultaneously.
+
+In the course of the consultation, information may also be required from remote databases containing the patient's medical files; from one or more diagnostic test centres in the form of X-rays, sonograms, electrocardiographs or similar medical images; or from a reference library containing technical information, illustrative medical images, or other supporting material required to facilitate the consultation. This material may be textual, aural, graphical or imagery in nature and may be stored in a multimedia format.
+
+Participants in the consultation may be located in an office or medical facility having access to the full range of broadband multimedia telecommunications capabilities; or located in a moving vehicle, on a golf course, or at some other remote location having limited communications access. In order to accommodate all eventualities, provisions for dynamic resource arbitration and allocation, both during "call" initiation and while the "call" is in progress, are required to ensure that the more important aspects of the interaction are fully satisfied.
+
+## I.2 Application scenario
+
+This scenario is provided in two parts to better represent the wide range of communication environments within which a multimedia medical consultation could take place.
+
+### I.2.1 Full multimedia support capability
+
+Dr. "X" is a world recognized authority on bone structure and is widely consulted by other doctors on a frequent basis. Usually, this consultation takes place in Dr. "X"'s office where he has a state-of-the-art multimedia communications terminal with a large high definition video display. A typical consultation might proceed in the following manner:
+
+Stage 1 – Dr. "X" is called by Dr. "Y" via videophone requesting consultation regarding a patient suffering from multiple fractures of the upper foot resulting from an automobile accident. After briefly covering the nature of the injury, Dr. "Y" transmits the patient's examination chart. The full screen video image on Dr. "X"'s screen immediately changes to a two-partition representation depicting the patient's chart in the left half and a reduced video image of Dr. "Y" in the right half.
+
+Stage 2 – Dr. "Y" is on duty in the emergency room of a local hospital and, after discussing the general aspects of the case with Dr. "X" in a face-to-face videophone presentation, switches to his handheld remote videophone camera in order to provide Dr. "X" with a visual survey of the damaged foot.
+
+Stage 3 – With the visual inspection completed, Dr. "X" requests transmission of the X-rays depicting the damaged area taken from different orientations. The two-partition screen presentation is quickly divided into four partitions, one for each of the X-rays to be transmitted.
+
+Stage 4 – After careful scrutiny, Dr. "X" selects the partition which gives the best view of the upper ankle area where most of the serious damage appears to have occurred. The partitioned screen is quickly replaced with a full screen, high resolution depiction of the selected image, enabling Dr. "X" to make a more detailed inspection of the area of interest.
+
+Stage 5 – Careful examination of the tarsal bone structure indicates considerable damage to the tibialis posterior tendon and associated muscle area, a complicating factor which requires the assistance of a third specialist. With the consent of Dr. "Y", Dr. "X" initiates a videoconference call to Dr. "Z", a specialist in tendon reconstruction.
+
+Stage 6 – After advising Dr. "Z" of the nature of the emergency, the three doctors continue discussion of the case. As the videoconference progresses, the patient's examination chart, medical files, X-rays and other reference information are brought into the conference as required, either through the transmission of additional data or recovered from local "memory" if previously transmitted.
+
+Stage 7 – At the end of the conference, Dr. "Y" thanks Drs. "X" and "Z" for their assistance and terminates the consultation.
+
+### **I.2.2 Restricted multimedia support capability**
+
+A week later, another emergency occurs, this time involving a patient whose foot has been crushed in a logging accident. Dr. "Y" again calls Dr. "X" for consultation. While Dr. "X" is available for consultation, it is his day off and all calls are automatically routed either to his home terminal or his portable terminal, depending upon the doctor's location at any particular point in time. In this case, Dr. "X" happens to be on the golf course, accessible from the portable terminal in his golf cart.
+
+In general, the consultation proceeds in a manner similar to that of the previous week. However, due to size limitations placed on the portable terminal and the reduced bandwidth available through the mobile network, service expectations are modified and focused on the more important aspects of the interaction. The less important features are relegated to a nice-to-have but non-essential category. With this in mind, the consultation proceeds in the following manner:
+
+Stage 1 – Dr. "Y" initiates a videophone call to Dr. "X" to request consultation. Since Dr. "X" is now using his portable terminal, he has elected to receive calls in the "voice only" mode. The network, complying with this service request, establishes the initial connection for voice communication only.
+
+Stage 2 – After advising Dr. "X" of the circumstances surrounding the emergency, Dr. "Y" asks Dr. "X" to switch his terminal to videophone operation in order to visually survey the area of injury. Dr. "Y", recognizing that Dr. "X" is communicating from a portable terminal, bypasses the normal full field view camera on his videophone terminal and activates the handheld remote scanner, holding the camera steady in the vicinity of the injury to compensate for the reduced "motion" response characteristics of Dr. "X"'s portable terminal.
+
+Stage 3 – With visual inspection completed, Dr. "X" requests transmission of an X-ray for the orientation he feels will best portray the extent of damage. To compensate for the size of the portable video display and the reduced transmission rate, Dr. "X" has purchased an enhanced storage feature for his basic portable multimedia terminal in order to capture the considerable amount of data required for high resolution X-rays. In addition, he is willing to accept longer transmission delay in order to obtain the necessary image resolution.
+
+Stage 4 – After careful scrutiny of the damaged area, Dr. "X" requests transmission of an additional X-ray which he hopes will depict the damaged area to better advantage. He elects not to choose a split screen presentation due to the small size of the portable video display, but to take advantage of the local data storage and image manipulation features, which allow him to zoom in on areas of
+
+particular interest and to change from one locally stored image to the other at near "office" response times.
+
+Stage 5 – Careful examination of the injury again indicates the need for additional consultation with Dr. "Z" regarding the extensive damage which has occurred to the tendons in the vicinity of the ankle. With the consent of Dr. "Y", Dr. "X" places a voice only conference call to Dr. "Z".
+
+Stage 6 – After advising Dr. "Z" of the nature of the emergency and that he is calling from a mobile terminal, Dr. "X" asks Dr. "Y" to initiate a three-way videoconference to further discuss the case. In order to make maximum use of the bandwidth available for the more important imagery data, Dr. "X" elects to join the videoconference in the AUDIOGRAPHICS-only mode (audio plus still image and graphics). As the videoconference progresses, X-ray and other visual information is brought into the conference as required, either through the transmission of additional data or recovered from local memory if the information had been previously sent.
+
+Stage 7 – At the end of the teleconference, Dr. "Y" again thanks both Drs. "X" and "Z" for their assistance and terminates the consultation.
+
+## **I.3 Implementation notes**
+
+### **I.3.1 Related applications**
+
+This Application is closely related to REMOTE MEDICAL DIAGNOSTICS, but differs with respect to the time urgency of the interaction, the terminal facilities and transmission resources available, and the principal media of information interchange.
+
+### **I.3.2 Associated applications**
+
+AUTOMATED ACCOUNTING AND BILLING for the consultants' time, and a permanent record of the interaction (AUTOMATIC ARCHIVAL) are desirable adjuncts to this application.
+
+### **I.3.3 Security/privacy**
+
+The communications associated with this application are privileged in nature and require access to databases containing confidential information protected by privacy laws in most locations.
+
+### **I.3.4 Service flexibility**
+
+There is a need for automated service mechanisms which will allow for:
+
+- 1) initial "call" establishment at the highest common denominator of service capabilities shared by all participants; and
+- 2) the dynamic and selective modification of service parameters during "call" progress.
+
+### **I.3.5 Performance trade-offs**
+
+The primary media components are VOICE and IMAGERY. Resolution requirements for the medical images take precedence over the associated increase in transmission delay. For portable terminal applications, resolution also takes precedence over the area of spatial coverage as long as mechanisms are provided for selecting the boundaries of the area to be viewed.
+
+The consultation may be conducted in either a full-motion video or still-frame audiographic mode of operation, depending upon the terminal and transmission capabilities available to the participants.
+
+# APPENDIX II
+
+## Harmonization of multimedia services and applications
+
+In the monomedia era, the telecommunication services, like telephony, telefax, videotelephony and videoconference, were developed. However, in the multimedia era, many kinds of applications were and will be developed and standardized by other standardization bodies, in addition to ITU-T. To facilitate end use, services and applications should be harmonized between ITU-T and other standardization bodies. In order to harmonize those services and applications, ITU-T and other standardization bodies should exchange the opinions of specific topics, concepts and technology, by liaison aspects officially or unofficially. Figure II.1 represents that process:
+
+![Diagram illustrating the harmonization of multimedia services and applications. It shows the flow from User requirements and Technology trends into ITU-T (SG 1 and SGs), then through TSAG to Forums and Consortia.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg)
+
+The diagram illustrates the harmonization process. On the left, two inputs, 'User requirements' and 'Technology trends', point into a large box labeled 'ITU-T'. Inside this box, 'User requirements' points to a sub-box labeled 'SG 1', and 'Technology trends' points to a sub-box labeled 'SGs'. From the 'ITU-T' box, an arrow points to a central box labeled 'TSAG'. From the 'TSAG' box, an arrow points to a large box on the right labeled 'Forums and Consortia'. Below the 'Forums and Consortia' box, the text 'T0104910-95' is visible.
+
+Diagram illustrating the harmonization of multimedia services and applications. It shows the flow from User requirements and Technology trends into ITU-T (SG 1 and SGs), then through TSAG to Forums and Consortia.
+
+**Figure II.1/F.700 – Harmonization of multimedia services and applications**
+
+
+
+# ITU-T RECOMMENDATIONS SERIES
+
+|                 |                                                                                                                                |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of the 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                                              |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                |
+| Series G        | Transmission systems and media, digital systems and networks                                                                   |
+| Series H        | Audiovisual and multimedia systems                                                                                             |
+| Series I        | Integrated services digital network                                                                                            |
+| Series J        | 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/F/T-REC-F.701-200011-I_PDF-E/raw.md b/marked/F/T-REC-F.701-200011-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..9e6f2015f2a31d9bf542b537b950e71985c7f2c6
--- /dev/null
+++ b/marked/F/T-REC-F.701-200011-I_PDF-E/raw.md
@@ -0,0 +1,415 @@
+
+
+![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
+
+**F.701**
+
+(11/2000)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Audiovisual services
+
+---
+
+**Guideline Recommendation for identifying  
+multimedia service requirements**
+
+ITU-T Recommendation F.701
+
+(Formerly CCITT Recommendation)
+
+---
+
+# ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+### **TELEGRAPH SERVICE**
+
+|                                                                 |             |
+|-----------------------------------------------------------------|-------------|
+| Operating methods for the international public telegram service | F.1–F.19    |
+| The gentex network                                              | F.20–F.29   |
+| Message switching                                               | F.30–F.39   |
+| The international telemessage service                           | F.40–F.58   |
+| The international telex service                                 | F.59–F.89   |
+| Statistics and publications on international telegraph services | F.90–F.99   |
+| Scheduled and leased communication services                     | F.100–F.104 |
+| Phototelegraph service                                          | F.105–F.109 |
+
+## **MOBILE SERVICE**
+
+|                                                         |             |
+|---------------------------------------------------------|-------------|
+| Mobile services and multidestination satellite services | F.110–F.159 |
+|---------------------------------------------------------|-------------|
+
+### **TELEMATIC SERVICES**
+
+|                                           |             |
+|-------------------------------------------|-------------|
+| Public facsimile service                  | F.160–F.199 |
+| Teletex service                           | F.200–F.299 |
+| Videotex service                          | F.300–F.349 |
+| General provisions for telematic services | F.350–F.399 |
+
+### **MESSAGE HANDLING SERVICES**
+
+F.400–F.499
+
+## **DIRECTORY SERVICES**
+
+F.500–F.549
+
+### **DOCUMENT COMMUNICATION**
+
+|                                      |             |
+|--------------------------------------|-------------|
+| Document communication               | F.550–F.579 |
+| Programming communication interfaces | F.580–F.599 |
+
+### **DATA TRANSMISSION SERVICES**
+
+F.600–F.699
+
+### **AUDIOVISUAL SERVICES**
+
+**F.700–F.799**
+
+## **ISDN SERVICES**
+
+F.800–F.849
+
+## **UNIVERSAL PERSONAL TELECOMMUNICATION**
+
+F.850–F.899
+
+### **HUMAN FACTORS**
+
+F.900–F.999
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# **Guideline Recommendation for identifying multimedia service requirements**
+
+## **Summary**
+
+This Recommendation provides guidelines for describing user requirements that are to be used as the basis for constructing new multimedia services. These guidelines are primarily intended to support the Multimedia service development methodology described in ITU-T Recommendation F.700. However, they can also be used as the basis for a structured dialogue between End-Users and Service Providers in order to arrive at a responsive service solution when applicable ITU-T service Recommendations are not yet available.
+
+## **Source**
+
+ITU-T Recommendation F.701 was prepared by ITU-T Study Group 16 (2001-2004) and was approved under the World Telecommunication Standardization Assembly Resolution No. 1 procedure on 17 November 2000.
+
+# FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the 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 Assembly (WTSA), 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 WTSA Resolution No. 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
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The 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, the 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 2001
+
+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 the ITU.
+
+# CONTENTS
+
+|                                                                | Page |
+|----------------------------------------------------------------|------|
+| 1 Scope.....                                                   | 1    |
+| 2 Definitions .....                                            | 1    |
+| 3 Multimedia service development methodology.....              | 1    |
+| 3.1 Application scripts .....                                  | 2    |
+| 3.2 Communication capabilities .....                           | 2    |
+| 3.3 Middleware service elements.....                           | 2    |
+| 3.4 Multimedia service Recommendations.....                    | 2    |
+| 4 Application Scripts .....                                    | 2    |
+| 4.1 Introduction.....                                          | 2    |
+| 4.2 Prose description.....                                     | 3    |
+| 4.3 Functional model of an application.....                    | 3    |
+| 4.4 Application matrix .....                                   | 4    |
+| 4.5 Summary.....                                               | 4    |
+| 5 Harmonization of Application Scripts with other bodies ..... | 4    |
+| Appendix I – Definitions.....                                  | 5    |
+| Appendix II – Multimedia medical consultation.....             | 5    |
+| II.1 Prose Description.....                                    | 5    |
+| II.2 Application Scenario.....                                 | 5    |
+| II.2.1 Full multimedia support capability.....                 | 6    |
+| II.2.2 Restricted multimedia support capability .....          | 6    |
+| II.3 Implementation notes.....                                 | 7    |
+| II.3.1 Related applications.....                               | 7    |
+| II.3.2 Associated applications .....                           | 7    |
+| II.3.3 Security/privacy .....                                  | 7    |
+| II.3.4 Service flexibility.....                                | 8    |
+| II.3.5 Performance trade-offs .....                            | 8    |
+
+
+
+## **Guideline Recommendation for identifying multimedia service requirements**
+
+# **1 Scope**
+
+This Recommendation provides guidelines for describing user requirements that are to be used as the basis for constructing new multimedia services. These guidelines are primarily intended to support the Multimedia service development methodology described in ITU-T Recommendation F.700. However, they can also be used as the basis for a structured dialogue between End-Users and Service Providers in order to arrive at a responsive service solution when applicable ITU-T service Recommendations are not yet available.
+
+# **2 Definitions**
+
+For the purpose of this ITU-T Recommendation the terms defined in Recommendation F.700 will apply. The definitions of some important terms are reproduced in Appendix I for user convenience.
+
+# **3 Multimedia service development methodology**
+
+A detailed methodology for developing Multimedia services is described in Recommendation F.700. Figure 1 provides an overview of this methodology and shows how end-user requirements are inserted into the service development process through the use of Application Scripts. The construction of these Scripts from End-User requirements is described in the remaining clauses of this Recommendation.
+
+![Figure 1/F.701 – Multimedia service development methodology flowchart](9791722d75115ddcc599b07d7bc35d73_img.jpg)
+
+The diagram illustrates the multimedia service development methodology. At the center is an oval labeled "Service description process". To its left, a box labeled "Middleware Service Elements" has an arrow pointing to the central process. Above the central process, a stack of three boxes labeled "Application scripts" has an arrow pointing down to the process. Below the central process, a box labeled "Description of communication capabilities" has an arrow pointing up to the process. This box contains two sub-boxes: "Communication Tasks" and "Media Components". To the right of the central process, an arrow points to a box labeled "Generic multimedia service Recommendations". Above this box is a stack of three boxes labeled "F.Mxx", "F.MDS", and "F.MCS". The text "T0106070-00" is located below the "Generic multimedia service Recommendations" box.
+
+Figure 1/F.701 – Multimedia service development methodology flowchart
+
+**Figure 1/F.701 – Multimedia service development methodology**
+
+## **3.1 Application scripts**
+
+An application script is a document that describes the essential characteristics of an End-User application so as to facilitate identification and evaluation of the multimedia communication capabilities required to support it. The script, when properly validated, provides the baseline requirements for new multimedia services. The procedure for developing and validating application scripts is described in clause 4.
+
+## **3.2 Communication capabilities**
+
+Communication capabilities are the fundamental sets of communication tasks, media components and integration mechanisms required to develop the complex spectrum of multimedia services. The procedure for translating the application script into the required communications capabilities is described in ITU-T Recommendation F.700. Procedures are also identified for launching the development of new communications capabilities when required to more fully support emerging user needs.
+
+## **3.3 Middleware service elements**
+
+The middleware service elements contain all the control features and the processing functions associated with the service. They interact with the various communication capabilities in order to control them or to process the user information.
+
+## **3.4 Multimedia service Recommendations**
+
+The translation of a particular application script into a description of the required multimedia service can be accomplished directly from the basic communication capabilities by utilizing the procedures specified in ITU-T Recommendation F.700. However, this process can be simplified in many cases by recognizing that a significant number of end-user applications utilize just a few combinations of multimedia communication means. The methodology for describing these generic service architectures in a series of general ITU-T service Recommendations is also described in ITU-T Recommendation F.700.
+
+# **4 Application Scripts**
+
+## **4.1 Introduction**
+
+An application script describes the essential characteristics of an end-user application in a manner designed to facilitate identification and evaluation of the required multimedia communications support capabilities. This is accomplished by first describing the application from the end user's point of view and then translating this description into a form more useful for technical evaluation. The procedures for constructing an application script are described in 4.2 through 4.4.
+
+Ideally, an application selected for the scripting process should represent a broad grouping of individual end-user applications which have the same essential functional characteristics and for which there appears to be a need for the development of a new multimedia service, service arrangement or enhanced service capability.
+
+Differences between specific applications within this broad grouping can be represented by the specific values assigned to a particular requirement attribute. Examples are shown in 4.4. The procedures for validating the results of the scripting process are described in clause 5.
+
+## 4.2 Prose description
+
+The prose description of an application provides a comprehensive statement of its scope and functional characteristics, together with the user's expectations for the quality of service. This description is written in a language understandable to the end user, who need not be aware of the technical aspects of the underlying service or supporting communications networks.
+
+The prose description may be augmented by an application scenario and a set of implementation notes which further describe the application, highlighting those aspects which might otherwise remain unclear. A sample prose description, with associated application scenario and implementation notes, is provided in Appendix I.
+
+## 4.3 Functional model of an application
+
+The functional model provides a pictorial representation of the essential functional elements identified in the prose description. This representation is presented from the perspective of the application, rather than from the supporting service or network, and contains only those elements visible to the end user. Figure 2 provides the functional model for the prose description contained in Appendix II.
+
+![Figure 2/F.701 – A sample functional model of an application (medical consultation). The diagram shows a central 'Shared information space' rectangle connected to three 'Consultant' circles (1, 2, 3) above it, an 'Initiator' circle below it, and four external entities: 'Public medical information database' (left), 'Public medical records database' (right), 'Billing' (bottom-left), and 'Archival' (bottom-right). Arrows indicate bidirectional interactions between the central space and each entity.](367926125450c2bc3f4bdca9d59a62ba_img.jpg)
+
+```
+graph TD; C1((Consultant 1)) <--> SIS[Shared information space]; C2((Consultant 2)) <--> SIS; C3((Consultant 3)) <--> SIS; SIS <--> P1[Public medical information database]; SIS <--> P2[Public medical records database]; SIS <--> B[Billing]; SIS <--> I((Initiator)); SIS <--> A[Archival];
+```
+
+T0106080-00
+
+Figure 2/F.701 – A sample functional model of an application (medical consultation). The diagram shows a central 'Shared information space' rectangle connected to three 'Consultant' circles (1, 2, 3) above it, an 'Initiator' circle below it, and four external entities: 'Public medical information database' (left), 'Public medical records database' (right), 'Billing' (bottom-left), and 'Archival' (bottom-right). Arrows indicate bidirectional interactions between the central space and each entity.
+
+**Figure 2/F.701 – A sample functional model of an application (medical consultation)**
+
+The principle characteristics to be depicted in the model are:
+
+- the shared information space in which the interaction takes place;
+- the functional role of the major participants;
+- the required supporting information resources;
+- the type and configuration of the various interactions; and
+- the need to interface associated application processes.
+
+While there is no standard symbology for constructing the functional model, care should be taken to select a form of presentation that reflects the essential functional elements of the application in a clear and concise way.
+
+## 4.4 Application matrix
+
+An application matrix maps user requirements onto technical functionalities. The principles for developing attribute tables are the following:
+
+- 1) Application matrices are intended to facilitate the mapping of user needs with technical functionalities in an easily understandable form.
+- 2) Application matrices enable the evaluation of service functionalities in a systematic and compact form.
+- 3) Application matrices facilitate assessing the importance of functionalities in regard to user needs.
+
+Table 1 shows as an example a part of an application matrix:
+
+**Table 1/F.701 – Application matrix template**
+
+| User needs                   | Technical functionalities                  |                       |                         |
+|------------------------------|--------------------------------------------|-----------------------|-------------------------|
+|                              | Differential delay between audio and video | Image repetition rate | Image resolution        |
+| Lip reading (with head view) | < 100 ms                                   | > 20 pictures/s       | QCIF (178 × 144 pixels) |
+| Sign language                | –                                          | > 20 pictures/s       | CIF (358 × 288 pixels)  |
+
+The following are examples of user needs:
+
+- discussion of a jointly viewed document;
+- the need to move around;
+- the need to scrutinize fine details of a presented object.
+
+The following are examples of functionalities the applications may require:
+
+- shared viewing space for images;
+- cordless communication access;
+- high resolution image transfer.
+
+The development of the matrix requires further study.
+
+## 4.5 Summary
+
+A script may include a prose description, an application scenario, implementation notes and an application matrix. (or several matrices for different environments or different times in the communication). Some scripts may contain only part of those elements.
+
+# 5 Harmonization of Application Scripts with other bodies
+
+Application scripts can be developed by the ITU or by other standards organizations, industry fora, consortia, user groups or individual end users. An application script, before being used as the basis for launching a new service development or evaluation effort by the ITU-T, should be discussed with the end user community if possible or reasonable. This discussion should take place between the relevant study groups and those organizations that have been identified as most representative of relevant end user interests, in accordance with ITU-T policies and procedures (see ITU-T Recommendation A.4).
+
+# APPENDIX I
+
+## Definitions
+
+Definitions taken from ITU-T Recommendation F.700.
+
+**I.1 application:** An Application is a set of activities performed to respond to the needs of the users in a given situation for purposes such as business, education, personal communication or entertainment. It implies software and hardware utilization, could be performed in a fully or partially automatic way and could be accessed locally or remotely. In the last case, it requests use of telecommunication services.
+
+**I.2 multimedia {MHEG}:** The term multimedia is an adjective which means relative to two or more media; it must be attached to a noun which provides the context. For example, multimedia service or application, multimedia terminal, multimedia network and multimedia presentation.
+
+**I.3 multimedia application:** A Multimedia Application is an application that requests the handling of two or more representation media (information types) simultaneously, which constitute a common information space. Examples are cooperative document editing, long distance meetings, remote surveillance, medical document remote analysis and teletraining.
+
+**I.4 multimedia service:** Multimedia services are telecommunication services that handle two or more types of media in a synchronized way from the user's point of view. A multimedia service may involve multiple parties, multiple connections, and the addition or deletion of resources and users within a single communication session.
+
+# APPENDIX II
+
+## Multimedia medical consultation
+
+## II.1 Prose Description
+
+Medical consultation involves interactive multimedia communications between medical experts located at two or more separate locations. This communication is generally initiated by a doctor desiring to discuss a particular patient's case with subject matter experts and may occur between the doctor and one consultant only, or may require an interactive conference arrangement between the doctor and several consultants simultaneously.
+
+In the course of the consultation, information may also be required from remote databases containing the patient's medical files; from one or more diagnostic test centres in the form of X-rays, sonograms, electrocardiographs or similar medical images; or from a reference library containing technical information, illustrative medical images, or other supporting material required to facilitate the consultation. This material may be textual, aural, graphical or imagery in nature and may be stored in a multimedia format.
+
+Participants in the consultation may be located in an office or medical facility having access to the full range of broadband multimedia telecommunications capabilities; or located in a moving vehicle, on a golf course, or at some other remote location having limited communications access. In order to accommodate all eventualities, provisions for dynamic resource arbitration and allocation, both during "call" initiation and while the "call" is in progress, are required to ensure that the more important aspects of the interaction are fully satisfied.
+
+## II.2 Application Scenario
+
+This scenario is provided in two parts to better represent the wide range of communication environments within which a multimedia medical consultation could take place.
+
+### II.2.1 Full multimedia support capability
+
+Dr. "X" is a world recognized authority on bone structure and is widely consulted by other doctors on a frequent basis. Usually, this consultation takes place in Dr. "X"'s office where he has a state-of-the-art multimedia communications terminal with a large high definition video display. A typical consultation might proceed in the following manner:
+
+Stage 1 – Dr. "X" is called by Dr. "Y" via videophone requesting consultation regarding a patient suffering from multiple fractures of the upper foot resulting from an automobile accident. After briefly covering the nature of the injury, Dr. "Y" transmits the patient's examination chart. The full screen video image on Dr. "X"'s screen immediately changes to a two-partition representation depicting the patient's chart in the left half and a reduced video image of Dr. "Y" in the right half.
+
+Stage 2 – Dr. "Y" is on duty in the emergency room of a local hospital and, after discussing the general aspects of the case with Dr. "X" in a face-to-face videophone presentation, switches to his handheld remote videophone camera in order to provide Dr. "X" with a visual survey of the damaged foot.
+
+Stage 3 – With the visual inspection completed, Dr. "X" requests transmission of the X-rays depicting the damaged area taken from different orientations. The two-partition screen presentation is quickly divided into four partitions, one for each of the X-rays to be transmitted.
+
+Stage 4 – After careful scrutiny, Dr. "X" selects the partition which gives the best view of the upper ankle area where most of the serious damage appears to have occurred. The partitioned screen is quickly replaced with a full screen, high resolution depiction of the selected image, enabling Dr. "X" to make a more detailed inspection of the area of interest.
+
+Stage 5 – Careful examination of the tarsal bone structure indicates considerable damage to the tibialis posterior tendon and associated muscle area, a complicating factor which requires the assistance of a third specialist. With the consent of Dr. "Y", Dr. "X" initiates a videoconference call to Dr. "Z", a specialist in tendon reconstruction.
+
+Stage 6 – After advising Dr. "Z" of the nature of the emergency, the three doctors continue discussion of the case. As the videoconference progresses, the patient's examination chart, medical files, X-rays and other reference information are brought into the conference as required, either through the transmission of additional data or recovered from local "memory" if previously transmitted.
+
+Stage 7 – At the end of the conference, Dr. "Y" thanks Drs. "X" and "Z" for their assistance and terminates the consultation.
+
+### II.2.2 Restricted multimedia support capability
+
+A week later, another emergency occurs, this time involving a patient whose foot has been crushed in a logging accident. Dr. "Y" again calls Dr. "X" for consultation. While Dr. "X" is available for consultation, it is his day off and all calls are automatically routed either to his home terminal or his portable terminal, depending upon the doctor's location at any particular point in time. In this case, Dr. "X" happens to be on the golf course, accessible from the portable terminal in his golf cart.
+
+In general, the consultation proceeds in a manner similar to that of the previous week. However, due to size limitations placed on the portable terminal and the reduced bandwidth available through the mobile network, service expectations are modified and focused on the more important aspects of the interaction. The less important features are relegated to a nice-to-have but non-essential category. With this in mind, the consultation proceeds in the following manner:
+
+Stage 1 – Dr "Y" initiates a videophone call to Dr "X" to request consultation. Since Dr. "X" is now using his portable terminal, he has elected to receive calls in the "voice only" mode. The network, complying with this service request, establishes the initial connection for voice communication only.
+
+Stage 2 – After advising Dr. "X" of the circumstances surrounding the emergency, Dr. "Y" asks Dr. "X" to switch his terminal to videophone operation in order to visually survey the area of injury. Dr. "Y", recognizing that Dr. "X" is communicating from a portable terminal, bypasses the normal full field view camera on his videophone terminal and activates the handheld remote scanner, holding the camera steady in the vicinity of the injury to compensate for the reduced "motion" response characteristics of Dr. "X"'s portable terminal.
+
+Stage 3 – With visual inspection completed, Dr. "X" requests transmission of an X-ray for the orientation he feels will best portray the extent of damage. To compensate for the size of the portable video display and the reduced transmission rate, Dr. "X" has purchased an enhanced storage feature for his basic portable multimedia terminal in order to capture the considerable amount of data required for high resolution X-rays. In addition, he is willing to accept longer transmission delay in order to obtain the necessary image resolution.
+
+Stage 4 – After careful scrutiny of the damaged area, Dr. "X" requests transmission of an additional X-ray which he hopes will depict the damaged area to better advantage. He elects not to choose a split screen presentation due to the small size of the portable video display, but to take advantage of the local data storage and image manipulation features, which allow him to zoom in on areas of particular interest and to change from one locally stored image to the other at near "office" response times.
+
+Stage 5 – Careful examination of the injury again indicates the need for additional consultation with Dr. "Z" regarding the extensive damage which has occurred to the tendons in the vicinity of the ankle. With the consent of Dr. "Y", Dr. "X" places a voice only conference call to Dr. "Z".
+
+Stage 6 – After advising Dr. "Z" of the nature of the emergency and that he is calling from a mobile terminal, Dr. "X" asks Dr. "Y" to initiate a three-way videoconference to further discuss the case. In order to make maximum use of the bandwidth available for the more important imagery data, Dr. "X" elects to join the videoconference in the AUDIOGRAPHICS-only mode (audio plus still image and graphics). As the videoconference progresses, X-ray and other visual information is brought into the conference as required, either through the transmission of additional data or recovered from local memory if the information had been previously sent.
+
+Stage 7 – At the end of the teleconference, Dr. "Y" again thanks both Drs. "X" and "Z" for their assistance and terminates the consultation.
+
+## **II.3 Implementation notes**
+
+### **II.3.1 Related applications**
+
+This Application is closely related to REMOTE MEDICAL DIAGNOSTICS, but differs with respect to the time urgency of the interaction, the terminal facilities and transmission resources available, and the principal media of information interchange.
+
+### **II.3.2 Associated applications**
+
+AUTOMATED ACCOUNTING AND BILLING for the consultants' time, and a permanent record of the interaction (AUTOMATIC ARCHIVAL) are desirable adjuncts to this application.
+
+### **II.3.3 Security/privacy**
+
+The communications associated with this application are privileged in nature and require access to databases containing confidential information protected by privacy laws in most locations.
+
+### **II.3.4 Service flexibility**
+
+There is a need for automated service mechanisms which will allow for:
+
+- 1) initial "call" establishment at the highest common denominator of service capabilities shared by all participants; and
+- 2) the dynamic and selective modification of service parameters during "call" progress.
+
+#### **II.3.5 Performance trade-offs**
+
+The primary media components are VOICE and IMAGERY. Resolution requirements for the medical images take precedence over the associated increase in transmission delay. For portable terminal applications, resolution also takes precedence over the area of spatial coverage as long as mechanisms are provided for selecting the boundaries of the area to be viewed.
+
+The consultation may be conducted in either a full-motion video or still-frame audiographic mode of operation, depending upon the terminal and transmission capabilities available to the participants.
+
+
+
+# **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                                              |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                |
+| Series G        | Transmission systems and media, digital systems and networks                                                                   |
+| Series H        | Audiovisual and multimedia systems                                                                                             |
+| Series I        | Integrated services digital network                                                                                            |
+| Series J        | 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/F/T-REC-F.71-198811-I_PDF-E/raw.md b/marked/F/T-REC-F.71-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..58859c387bb183aa55995d996b3fc7cf16089c90
--- /dev/null
+++ b/marked/F/T-REC-F.71-198811-I_PDF-E/raw.md
@@ -0,0 +1,74 @@
+
+
+![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**
+
+**F.71**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+# **OPERATIONS AND QUALITY OF SERVICE TELEGRAPH SERVICES** ---
+
+# **INTERCONNECTION OF PRIVATE TELEPRINTER NETWORKS WITH THE TELEX NETWORK**
+
+**ITU-T Recommendation F.71**
+
+(Extract from the *Blue Book*)
+
+---
+
+## NOTES
+
+1 ITU-T Recommendation F.71 was published in Fascicle II.4 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.
+
+## **INTERCONNECTION OF PRIVATE TELEPRINTER NETWORKS WITH THE TELEX NETWORK**
+
+The CCITT,
+
+*considering*
+
+- (a) the operational provisions for the international telex service laid down in Recommendation F.60;
+- (b) that in various countries possessing public telex networks there also exist numerous private teleprinter networks using their own exchanges and conforming with the national regulations of the country concerned;
+- (c) that the owners of these private networks are frequently substantial users of the telex service employing multiple subscriber lines;
+- (d) that, consequently, it is very desirable to allow the through-connection of calls between teleprinters connected to private exchanges and those connected to the public telex network;
+- (e) that in the telephone service the ability to establish calls between stations connected to private and public exchanges has long been available;
+- (f) that the operation of the international public telex service must be neither hampered nor limited by private exchanges and hence the conditions for interconnection of the two types of network should be standardized,
+
+*declares the following*
+
+- 1 Any terminal in a private network that may be directly connected (circuit switched) to a terminal in the international telex network must conform to the relevant requirements for terminals in the telex network as laid down in the Series F and S Recommendations.
+- 2 A private network must not be allowed to provide communication between two external telex stations. For the provisions concerning interconnection between international leased circuits and the telex network, see Recommendation D.1 [1].
+- 3 Where a private network uses a message store-and-forward system, it may be authorized to accept and deliver messages from and to the public network. The signals from the private network must always conform with the telex network's signalling standards.
+- 4 When a private network connected to the telex network offers an external caller the facility of selecting a given extension directly, this should be clearly indicated in the public telex directory.
+- 5 Either two-stage or single stage selection may be used as a means of automatic selection of a subsidiary station in the private network by an external caller.
+- 6 For two-stage selection the following provisions should be applied:
+  - 1) The first stage of the selection should designate the called private network, using a conventional national subscriber number. Following the normal telex procedure, this sequence should start the selection process, resulting in the caller's being connected to a teleprinter (or any other appropriate device in the private network) that is ready to record a message. For networks where the called telex subscriber's answer-back is tripped automatically, this answer-back code must designate and be common to the whole of the private network concerned.
+  - 2) Application of the second stage by the calling telex subscriber is optional. The selection sequence used to designate a particular extension station may have a special composition for the network that is quite independent of the national telex numbering scheme, but it must always consist of teleprinter characters.
+
+- 3) If the caller wishes to use the second stage of selection, he advises the private network by sending the sequence **XVXV** (combination 24, 22, 24 and 22 successively), to which the network responds with a proceed-to-select signal  $\leftarrow \equiv \downarrow \text{GA} \rightarrow$  (combinations 27, 28, 29, 7, 1 and 31 successively).
+- 4) This optional second stage of selection is ignored by the telex network. The corresponding selection time in the private network is charged in the same way as a telex call. The composition of the answer-back codes transmitted, where appropriate, after the second stage of selection may therefore be left to the discretion of the subscriber.
+
+7 Where single-stage selection is used for connection to extension stations, the following provisions should be applied.
+
+- 1) The single sequence used to select an extension station must be in the form of a national subscriber number, comprising a number to designate the called private network followed by further digits to specify the particular station required. When the caller sends this full sequence of digits, through-connection to the required extension is achieved, first by selection in the public network then in the private network. For networks where the called telex subscriber's answer-back is automatically tripped, the answer-back sent when the complete connection has been set up is specific to the selected extension.
+- 2) If the caller wishes to communicate, not with any specific subsidiary extension, but with a teleprinter (or any other appropriate device in the private network) that is ready to record a message, the selection sequence should consist of the number designating the private network followed by the figure **0**.
+- 3) If the caller only sends a selection sequence specifying the private network (i.e. neither **0**, nor a specific extension number nor an end-of-selection signal is added), the call should be automatically diverted after a period of 10 s to a main station.
+- 4) If the caller specifies a particular extension station that is engaged or otherwise unavailable, the call should be automatically diverted to a main station.
+- 5) With single-stage selection, the answer-back codes for all stations, including extension stations, must comply with the requirements in Recommendation F.60 for the composition of telex answer-back codes.
+
+8 In the event that the external caller fails either partially or totally to meet the requirements of the procedures of a private teleprinter network as in §§ 3 to 7 above, the call should be intercepted by, or directed to, an enquiry teleprinter (or any other appropriate device) in the private network. On no account must the call be terminated by the private network if the procedures are not followed.
+
+## Reference
+
+- [1] CCITT Recommendation *General principles for the lease of international (continental and intercontinental) private leased telecommunication circuits*, Rec. D.1.
\ No newline at end of file
diff --git a/marked/F/T-REC-F.72-199610-I_PDF-E/raw.md b/marked/F/T-REC-F.72-199610-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..994e9031e381102ac0a4020f661aeaeeb76f50ac
--- /dev/null
+++ b/marked/F/T-REC-F.72-199610-I_PDF-E/raw.md
@@ -0,0 +1,733 @@
+
+
+![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
+
+**F.72**
+
+(10/96)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Telegraph service – The international telex service
+
+---
+
+**The international telex service – General  
+principles and operational aspects of a store  
+and forward facility**
+
+ITU-T Recommendation F.72
+
+(Previously CCITT Recommendation)
+
+---
+
+# ITU-T F-SERIES RECOMMENDATIONS NON-TELEPHONE TELECOMMUNICATION SERVICES
+
+|                                                                 |                  |
+|-----------------------------------------------------------------|------------------|
+| TELEGRAPH SERVICE                                               | F.1–F.109        |
+| Operating methods for the international public telegram service | F.1–F.19         |
+| The gentex network                                              | F.20–F.29        |
+| Message switching                                               | F.30–F.39        |
+| The international telemessage service                           | F.40–F.58        |
+| <b>The international telex service</b>                          | <b>F.59–F.89</b> |
+| Statistics and publications on international telegraph services | F.90–F.99        |
+| Scheduled and leased communication services                     | F.100–F.104      |
+| Phototelegraph service                                          | F.105–F.109      |
+| MOBILE SERVICE                                                  | F.110–F.159      |
+| Mobile services and multdestination satellite services          | F.110–F.159      |
+| TELEMATIC SERVICES                                              | F.160–F.399      |
+| Public facsimile service                                        | F.160–F.199      |
+| Teletex service                                                 | F.200–F.299      |
+| Videotex service                                                | F.300–F.349      |
+| General provisions for telematic services                       | F.350–F.399      |
+| MESSAGE HANDLING SERVICES                                       | F.400–F.499      |
+| DIRECTORY SERVICES                                              | F.500–F.549      |
+| DOCUMENT COMMUNICATION                                          | F.550–F.599      |
+| Document communication                                          | F.550–F.579      |
+| Programming communication interfaces                            | F.580–F.599      |
+| DATA TRANSMISSION SERVICES                                      | F.600–F.699      |
+| AUDIOVISUAL SERVICES                                            | F.700–F.799      |
+| ISDN SERVICES                                                   | F.800–F.849      |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850–F.899      |
+| HUMAN FACTORS                                                   | F.900–F.999      |
+
+*For further details, please refer to ITU-T List of Recommendations.*
+
+## 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 F.72 was revised by ITU-T Study Group 1 (1993-1996) and was approved by the WTSC (Geneva, 9-18 October 1996).
+
+---
+
+## NOTE
+
+In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+© ITU 1997
+
+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 the ITU.
+
+## CONTENTS
+
+|      |                                                           | <i>Page</i> |
+|------|-----------------------------------------------------------|-------------|
+| 1    | Scope.....                                                | 1           |
+| 2    | General .....                                             | 1           |
+| 3    | Service requirements .....                                | 3           |
+| 3.1  | Message identification .....                              | 3           |
+| 3.2  | Service signals .....                                     | 3           |
+| 3.3  | Duration of message storage .....                         | 3           |
+| 3.4  | Maximum message length and duration .....                 | 3           |
+| 3.5  | Store full indication .....                               | 4           |
+| 3.6  | End of transaction and end of message signal .....        | 4           |
+| 3.7  | Input transaction accepted .....                          | 5           |
+| 3.8  | Message security .....                                    | 5           |
+| 3.9  | Advice of non-delivery/delivery .....                     | 5           |
+| 3.10 | Call records .....                                        | 5           |
+| 3.11 | Incomplete message .....                                  | 6           |
+| 4    | Facilities .....                                          | 6           |
+| 4.1  | Single address .....                                      | 6           |
+| 4.2  | Multi-address .....                                       | 6           |
+| 4.3  | Follow-on messages .....                                  | 6           |
+| 4.4  | Classes of delivery .....                                 | 6           |
+| 4.5  | Cancellation .....                                        | 6           |
+| 4.6  | Address correction .....                                  | 6           |
+| 5    | Quality of Service .....                                  | 7           |
+| 5.1  | Loss probability in the store and forward procedure ..... | 7           |
+| 5.2  | Error protection .....                                    | 7           |
+| 5.3  | Duration of service .....                                 | 7           |
+| 5.4  | Number of circuits .....                                  | 7           |
+| 5.5  | Minimum storage capacity .....                            | 7           |
+| 6    | Access principles .....                                   | 7           |
+| 7    | Access procedures .....                                   | 7           |
+| 7.1  | General .....                                             | 7           |
+| 7.2  | Access from a telex subscriber .....                      | 8           |
+| 7.3  | Service request .....                                     | 8           |
+| 7.4  | Message input .....                                       | 8           |
+| 8    | Contents of the address line .....                        | 8           |
+| 8.1  | Address line .....                                        | 8           |
+| 9    | Abnormal conditions during message input .....            | 10          |
+| 10   | Message status enquiry .....                              | 10          |
+| 10.1 | General procedures .....                                  | 10          |
+| 10.2 | Status enquiry information field content .....            | 10          |
+| 10.3 | The status report .....                                   | 10          |
+| 10.4 | Status report field content .....                         | 10          |
+| 11   | Delivery procedure .....                                  | 11          |
+| 11.7 | Procedures for delivery of messages .....                 | 11          |
+| 12   | Notification procedures .....                             | 14          |
+| 12.1 | Types of notification .....                               | 14          |
+| 12.2 | Notification delivery procedures .....                    | 14          |
+
+|                                                                    | <i>Page</i> |
+|--------------------------------------------------------------------|-------------|
+| 13    Delivery retry procedures.....                               | 14          |
+| 13.3    Recorded message from the called subscriber .....          | 14          |
+| 14    Contents of delivery/non-delivery notifications .....        | 14          |
+| 15    Internationally interconnected store and forward units ..... | 14          |
+
+
+
+# **THE INTERNATIONAL TELEX SERVICE – GENERAL PRINCIPLES AND OPERATIONAL ASPECTS OF A STORE AND FORWARD FACILITY**
+
+*(Melbourne, 1988; revised Helsinki, 1993 and Geneva, 1996)*
+
+The ITU-T
+
+*considering*
+
+- (a) that telex store and forward is included in Recommendation F.63 as an additional facility within the international telex service;
+- (b) that telex store and forward facilities have been and are being introduced by many countries;
+- (c) that a requirement for access via the international telex service from an originator in one country to a telex store and forward facility in another country has been identified;
+- (d) that a store and forward facility in one country may be interconnected with the store and forward facility in another country via Message Handling Services in accordance with F- and X-Series Recommendations,
+
+*unanimously declares*
+
+that the general principles and operational aspects described in this Recommendation should be adopted for the provision of store and forward as an additional facility within the international telex service.
+
+## **1 Scope**
+
+1.1 This Recommendation is one of a series which define telex store and forward facilities. The other Recommendations are:
+
+- Recommendation U.80 – International telex store and forward – Access from a telex subscriber.
+- Recommendation U.81 – International telex store and forward – Delivery to a telex subscriber.
+
+1.2 The service requirements and Quality of Service provisions along with the single address facility and classes of delivery specified in this Recommendation are essential for the store and forward facility. The other facilities are optional and will be provided at the discretion of the Administration operating the Store and Forward Unit (SFU).
+
+## **2 General**
+
+2.1 Within the store and forward facility, communication between terminals is on a store and forward basis via the SFU, thus conversational mode connection between terminals is not provided.
+
+2.2 The following two types of configuration have been identified as shown in Figure 1:
+
+- a) *International store and forward* is where a subscriber in Country A accesses the store and forward unit in Country B for the transmission of messages to that country.
+- b) *Interconnected store and forward* is where the store and forward unit in Country A is connected to the store and forward unit in Country B for the transmission of messages between the two countries.
+
+![Diagram a) Case of international store and forward. It shows a flow from a Telex originator in Country A, through a Telex network, to an SFU in Country B, and finally to an Addressee in Country B. A 'Message deposit' is indicated at the international boundary.](3121ebddccf183ca63bb9781be440a7e_img.jpg)
+
+The diagram illustrates the flow of a message in an international store and forward scenario. On the left, in Country A, a 'Telex originator' sends a message to a 'Telex network'. A horizontal line labeled 'Message deposit' crosses the 'International boundary' and points to a circle labeled 'SFU' in Country B. From the 'SFU', an arrow labeled 'Message delivery' points to the 'Addressee' in Country B. The 'Telex network' in Country B is also connected to the 'Addressee'.
+
+Diagram a) Case of international store and forward. It shows a flow from a Telex originator in Country A, through a Telex network, to an SFU in Country B, and finally to an Addressee in Country B. A 'Message deposit' is indicated at the international boundary.
+
+a) Case of international store and forward
+
+![Diagram b) Case of interconnected store and forward. It shows a flow from a Telex originator in Country A, through a Telex network, to an SFU, then to a central 'Message handling services' block across the international boundary, then to another SFU, and finally to an Addressee in Country B. A 'Message transfer' is indicated between the two SFUs.](990567efebf979be51f56d1150012c9d_img.jpg)
+
+The diagram illustrates the flow of a message in an interconnected store and forward scenario. On the left, in Country A, a 'Telex originator' sends a message to a 'Telex network', which then connects to an 'SFU'. A 'Message deposit' arrow points to this 'SFU'. From the 'SFU', the message goes to a 'Message handling services' block. A double-headed arrow labeled 'Message transfer' spans across the 'International boundary' between the 'Message handling services' in Country A and another 'SFU' in Country B. From this 'SFU', a 'Message delivery' arrow points to the 'Addressee' in Country B. The 'Telex network' in Country B is also connected to the 'Addressee'.
+
+Diagram b) Case of interconnected store and forward. It shows a flow from a Telex originator in Country A, through a Telex network, to an SFU, then to a central 'Message handling services' block across the international boundary, then to another SFU, and finally to an Addressee in Country B. A 'Message transfer' is indicated between the two SFUs.
+
+b) Case of interconnected store and forward
+
+Figure 1/F.72 – General model for the deployment of SFUs
+
+2.3 Whilst the Recommendation addresses international and interconnected store and forward, the delivery procedures can be used for international traffic from a national SFU.
+
+### 2.4 Limitations of access to a store and forward facility
+
+2.4.1 The configurations identified in 2.2 will be provided on the basis of bilateral agreements between the Administrations concerned.
+
+2.4.2 An Administration operating an SFU should be responsible for the barring of international access from unauthorized users and for barring unauthorized types of call such as transit calls to specific countries. The method of barring shall be the responsibility of the Administration operating the SFU and is beyond the scope of this Recommendation.
+
+2.4.3 It may also be necessary for Administrations to make provision to selectively block access to SFUs in other countries.
+
+## **3 Service requirements**
+
+### **3.1 Message identification**
+
+The SFU will provide to the subscriber a unique message reference readily identifiable for every message, comprising:
+
+- a) the date and time of message input as provided to the originating telex subscriber in accordance with Recommendation U.80; and
+- b) the message reference number as allocated and provided to the originating telex subscriber at the time of input of the message.
+
+### **3.2 Service signals**
+
+#### **3.2.1 Service signals received by the SFU**
+
+All standardized telex service signals (see Recommendation F.60 for a list of code expressions and appropriate U-Series Recommendations for their format) must be recognized by the SFU. The retry procedure will be according to the principles of Recommendation U.40. It is desirable that the SFU attempt to interpret non-standard service signal and continue with the appropriate procedure. If the SFU is unable to interpret a non-standard service signal, the SFU should give a non-delivery notification to the calling subscriber and repeat the service signal in the format received.
+
+#### **3.2.2 Code expressions sent by the SFU**
+
+The following code expressions may be generated by the SFU:
+
+- |     |                                                                                        |
+|-----|----------------------------------------------------------------------------------------|
+| ADD | Please input your international telex number                                           |
+| BMC | No end of message or end of transmission received, therefore message cancelled         |
+| IAB | Invalid answerback from destination (only sent as part of a non-delivery notification) |
+| IMA | Input message acknowledgement                                                          |
+| ITD | Input transaction accepted for delivery                                                |
+| ITR | Input transactions rejected                                                            |
+| LDE | Maximum acceptable message length or duration has been exceeded                        |
+| OCC | Store full, SFU unavailable                                                            |
+| REJ | Address rejected                                                                       |
+| TMA | Maximum number of addresses exceeded                                                   |
+
+### **3.3 Duration of message storage**
+
+The retry procedure applied by the SFU should be in accordance with the principles of Recommendation U.40. However, the period for which the SFU should retain responsibility for the message should not exceed 24 hours from time of input. If delivery has not been effected, the procedure as in 3.9 should apply.
+
+### **3.4 Maximum message length and duration**
+
+**3.4.1** All SFUs should have sufficient capacity to accept at least 24 000 characters per single message. Exceptionally, some SFUs may set this limit at 12 000 characters or even lower. Subscribers should therefore be advised by their Administrations as to the maximum message length accepted by those SFUs to which they have access.
+
+**3.4.2** In the case of interconnected SFUs, the maximum acceptable message length of the SFUs should be agreed to by the Administrations operating the SFUs.
+
+**3.4.3** The maximum input duration for a single transaction should be two hours.
+
+**3.4.4** If the maximum acceptable message length or duration is reached, the sender should be advised by sending to him the service code LDE. Prior to sending the service code LDE, an attempt should be made to stop his transmission by sending the letter T, repeatedly in accordance with Recommendation S.4.
+
+**3.4.5** After sending the service code LDE, the SFU will wait for the End of Message signal (EOM) or End of Transaction signal (EOT) and proceed in accordance with 3.6.
+
+### **3.5 Store full indication**
+
+Messages should cease to be accepted when the level of store capacity is reduced to a predetermined state to ensure that any messages in the process of being transmitted to the unit can be accepted in their entirety, bearing in mind the provisions of 3.4. The unit will return the service code OCC in response to attempts to access the unit for message input.
+
+### **3.6 End of transaction and end of message signal**
+
+**3.6.1** At the end of each transaction, an End of Transaction (EOT) signal is required. This signal is +++. However, for follow-on messages, an End of Message (EOM) signal is required at the end of each individual message. The functions of these signals are described in Table 1.
+
+**Table 1/F.72 – Functions of end of message and end of transaction signals**
+
+| <b>Sequence</b> | <b>Mnemonic</b> | <b>Function</b>                                                                                                                                                                                              | <b>Action by SFU</b>                                                                                                                                                                            |
+|-----------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| NNNN            | EOM             | Used to separate different messages (end of message) deposited in the SFU during the same transaction for delivery to different addresses or groups of addresses.                                            | 1) Enables follow-on calls to be provided by the SFU.<br>2) Will result in force clearing by the SFU and cancellation of the message(s) if not followed by either an address or the EOT signal. |
+| NNNNACK         | EOM(ACK)        | Used to request Input Message Acknowledgement (IMA) of previously deposited messages, to separate messages, and to request a follow-on call.                                                                 | As for EOM, except that messages already acknowledged will be delivered whatever the subsequent action by either the subscriber or the SFU.                                                     |
+| +++             | EOT             | End of transaction signal, used to indicate to the SFU that the transaction has been completed and also to request message reference information for previously submitted messages not already acknowledged. | Provides message reference information and initiates clearing.                                                                                                                                  |
+
+**3.6.2** If there is a stop in transmission for 30 seconds without receipt of either an EOM or EOT signal, the code expression GA should be sent to the subscriber.
+
+**3.6.3** If the EOM/EOT signal is not received, or transmission does not resume within a further 30 seconds, the SFU shall initiate the clear down procedure.
+
+**3.6.4** The incomplete message should either be cancelled or, optionally, sent to an operator assistance position.
+
+**3.6.5** If the message is to be cancelled before clearing the connection, the SFU should inform the subscriber that no EOM/EOT signal has been received by sending the code expression BMC.
+
+**3.6.6** In the event of clear down by the caller without an EOM or EOT signal, the incomplete message(s) will be processed as in 3.6.4.
+
+### **3.7 Input transaction accepted**
+
+On receipt of an EOT signal, the SFU should send an input transaction accepted for delivery signal (ITD) notifying the subscriber that the message(s) has/have been accepted and that delivery will be attempted. Delivery should be attempted even if the call is cleared before the ITD is sent. The ITD should be followed by the message reference(s) and, if applicable, number of messages.
+
+### **3.8 Message security**
+
+#### **3.8.1 Message acceptance**
+
+**3.8.1.1** The SFU should only accept messages for delivery to destination addresses served by that SFU. Any messages for other destinations should be refused with code expression NA for the reason of non-delivery.
+
+**3.8.1.2** The SFU should not accept message input unless acceptable identification of the originating subscriber has been received at call set-up in accordance with Recommendations U.74 and U.80.
+
+**3.8.1.3** The SFU may validate the called address(es). If this validation is unsuccessful for all addresses, the message should be rejected and the code expression ITR should be returned (see Recommendation U.80). However, positive validation result does not guarantee that the message can be delivered to the given address.
+
+#### **3.8.2 Expected answerback comparison**
+
+Subscribers may provide all or part of the expected answerback to enable the SFU to validate the answerback received in order to enhance message security. This information should be compared with the answerback received by the SFU at call set-up to the destination subscriber and, if found not to be in compliance, the message should not be delivered.
+
+A non-delivery notification should be given to the originating subscriber including the code expression IAB and optionally repeating the destination answerback actually received. The method used for checking the answerback is the responsibility of the Administration operating the SFU. If the subscriber does not provide the expected answerback, the SFU may provide validation by comparing the called party's national telex number with the received answerback.
+
+### **3.9 Advice of non-delivery/delivery**
+
+**3.9.1** Automatic advice of non-delivery should be given to the subscriber as soon as the delivery retry procedure in accordance with Recommendation U.40 has been terminated. In the case of multi-address messages, advice of non-delivery may be issued on a per message or per address basis, the former being preferred when the retry procedure has been completed for all of the specified addresses. If an advice of non-delivery cannot be delivered, it should be sent to a manual assistance position associated with the SFU. Normal telex operator calling procedures must be observed when attempting manually-assisted advice of non-delivery.
+
+**3.9.2** Automatic advice of delivery is preferred. However, it will be provided at the discretion of the Administrations operating the SFU service.
+
+**3.9.3** In the case of interconnected store and forward, the destination SFU should pass all delivery, non-delivery and status information to the originating SFU from which advice will be sent to the originating subscriber.
+
+**3.9.4** The provision of a periodic (e.g. daily) notification or journal may be considered as an adequate form of delivery, non-delivery and status information.
+
+**3.9.5** Notification of message delivery/non-delivery may be on a per message or per address basis. This Recommendation assumes that notification will be returned, as a minimum, on a per message basis.
+
+### **3.10 Call records**
+
+Records of effective and ineffective calls should be maintained and forwarded to the origin Administration at regular intervals (at least once per month) for general accounting, billing, and statistical purposes. The Administrations should agree bilaterally on the format and method of information transfer.
+
+### 3.11 Incomplete message
+
+In the case of partial delivery of a message by the SFU, the header "Possible duplicate message" should be appended to the message at subsequent delivery.
+
+## 4 Facilities
+
+### 4.1 Single address
+
+This is where a message is sent via an SFU to another telex subscriber addressee and is a minimum requirement. In addition, messages may also be sent to subscribers of other services (e.g. Teletex, Videotex) in accordance with Recommendation U.80.
+
+### 4.2 Multi-address
+
+4.2.1 A multi-address message is where a common text is sent to two or more addresses. This facility should be provided only for addresses in the same country as the destination SFU and requires bilateral agreement.
+
+4.2.2 The acceptable number of individual addresses for any one message will be decided by the Administrations operating the SFU but should be at least 20.
+
+4.2.3 If the maximum acceptable number of addresses is exceeded, the SFU shall clear the communication after sending the code expression TMA.
+
+### 4.3 Follow-on messages
+
+This facility enables the subscriber to enter more than one message into storage without clearing, each message being preceded by a different header, and is considered to be highly desirable. At the completion of the transaction, the unit should advise the sender of the number of messages received. Each separate message must have a unique reference number. See also 3.6.1.
+
+### 4.4 Classes of delivery
+
+The following three classes of delivery have been identified; one or more of these should be offered by Administrations:
+
+- a) *Normal delivery* – The SFU attempts to deliver the message as soon as operationally feasible after receipt.
+- b) *Deferred delivery* – The delay can be either:
+  - i) set by the Administration offering the SFU facility;
+  - ii) set by the calling subscriber, such that the delivery of the message is not attempted until after the expiration of the indicated delay.
+- c) *Time limited delivery* – Where the SFU attempts to deliver the message as soon as operationally feasible up to a customer – specified time limit not exceeding 24 hours.
+
+These classes of delivery should be offered on a per address basis.
+
+### 4.5 Cancellation
+
+The facility whereby the originating subscriber may cancel a message after it has been accepted by the SFU is not permitted.
+
+### 4.6 Address correction
+
+When provided, the facility whereby the originating subscriber can correct an address during input should be implemented in accordance with Recommendation U.80.
+
+## **5 Quality of Service**
+
+### **5.1 Loss probability in the store and forward procedure**
+
+**5.1.1** The introduction of an SFU into the international telex network should not increase, on a per address basis, the probability of message loss or corruption.
+
+**5.1.2** In international store and forward, the unique identification of each message should enable the system to provide information as to the status of any message upon interrogation.
+
+**5.1.3** In the event of system failure, all accepted messages should be traceable. However, if messages have to be cancelled, the originating subscriber should be informed.
+
+### **5.2 Error protection**
+
+The overall error protection should be in accordance with Recommendation F.10 and the error rate should therefore not be greater than 3 in 100 000.
+
+### **5.3 Duration of service**
+
+The automatic service should be continuous.
+
+### **5.4 Number of circuits**
+
+Where international store and forward exists, the amount of traffic generated and received by the SFU should be considered when determining the number of international circuits in conformity with Recommendation F.64. However, the actual number of circuits will depend on the capacity of the SFU. Care must be taken that routes are not congested by the SFU. Such factors as the time difference between the countries concerned need to be taken into account.
+
+### **5.5 Minimum storage capacity**
+
+The storage capacity will vary from unit to unit according to the volume of traffic. However, it should be sufficient to provide a grade of service not less than that of the international telex service provided by that Administration.
+
+## **6 Access principles**
+
+**6.1** The procedure defined in this clause is a two-stage selection procedure whereby the calling telex subscriber gains access to a foreign SFU in the first stage of selection and either inputs the called address(es) and message, or requests a status report, in the second stage of selection, after the return of a call-connect by the called SFU.
+
+**6.2** Message input from both manual and automatic emitting devices should be accommodated.
+
+**6.3** The telex address of the originating telex subscriber should be determined in accordance with Recommendation U.74. It should be noted, however, that not all answerbacks follow the preferred sequence described in Recommendation F.60 and allowance should be made for this condition.
+
+**6.4** A different access code should be used depending on the desired mode of operation; either message input or status enquiry.
+
+## **7 Access procedures**
+
+### **7.1 General**
+
+**7.1.1** Two basic access procedures should be provided:
+
+- a) *Interactive operation* – Input from manual calling terminals, where the SFU may return prompt signals.
+
+- b) *Non-interactive operation* – Either input from automatic emitting devices or from subscribers' terminals, where prompt signals from the SFU are not required or are input from another SFU (detection of this type of access will rely on the identification of the calling SFU answerback).
+
+### **7.2 Access from a telex subscriber**
+
+**7.2.1** The originating telex subscriber should establish a call to the SFU by means of normal telex procedures.
+
+**7.2.2** Figure 2 shows the recommended procedures for message deposit in the SFU. The protocol to be followed between the originating telex subscriber and the SFU should be in accordance with Recommendation U.80.
+
+### **7.3 Service request**
+
+#### **7.3.1 Interactive service request**
+
+The originating telex subscriber should be recognized as interactive by the omission of the non-interactive service request (see 7.3.2).
+
+#### **7.3.2 Non-interactive service request**
+
+The originating telex subscriber should indicate that the transmission is from an automatic terminal by commencing the procedure with the non-interactive service request (characters CI).
+
+### **7.4 Message input**
+
+**7.4.1** Provision should be made for both single and multi-addressed calls.
+
+**7.4.2** The SFU should only accept messages for delivery to destination addresses served by that SFU.
+
+**7.4.3** An attention information field may be provided by the SFU to convey the name and address of the recipient.
+
+**7.4.4** The desired class of delivery should be selectable on a destination address basis.
+
+**7.4.5** A message reference number may be returned to the originating subscriber immediately after the date and time information and before message input. In addition, it must be returned after the ITD signal at the end of the transaction. The reference number should comprise up to six numeric characters and cycle through consecutively for follow-on messages within the same transaction with accommodation being made for at least the last two or three digits for this purpose.
+
+**7.4.6** Characters received in the message text with the exception of the WRU signal should be transmitted transparently by the SFU.
+
+**7.4.7** The ITD should be returned to the originating subscriber to indicate that the SFU has accepted the message on receipt of the EOT. Alternatively, an Input Message Acknowledgement signal (IMA) will be sent on receipt of an EOM (ACK) signal.
+
+## **8 Contents of the address line**
+
+### **8.1 Address line**
+
+**8.1.1** Each address to which the message is to be delivered should be provided by the originating subscriber in the address line.
+
+**8.1.2** The address line information may consist of up to five fields:
+
+- a) address to be called;
+- b) expected answerback or part thereof;
+- c) attention information;
+- d) delivery indication;
+- e) Positive Delivery Notification (PDN) request.
+
+![Flowchart showing the general procedure for message deposit into an SFU. The process starts with 'Call set-up to SFU', followed by 'Identification of calling terminal by SFU'. It then enters a loop of 'Input of address(es)' and 'Input of characters'. Decision diamonds check for 'EOM received?', 'EOM (ACK) received?', and 'EOT received?'. If 'EOM received?' is Yes, it loops back to 'Input of address(es)'. If 'EOM (ACK) received?' is Yes, it loops back to 'Input of address(es)'. If 'EOT received?' is Yes, it leads to 'ITD'. If 'EOT received?' is No, it checks 'Clear from caller within 30 seconds?'. If Yes, it leads to 'ITD'. If No, it leads to 'GA'. 'GA' leads to 'Resumption of char. input within 30 seconds?'. If Yes, it loops back to the entry point of the input loop. If No, it leads to 'BMC', which leads to 'Message cancelled by SFU'. Both 'Message cancelled by SFU' and 'ITD' lead to 'Clear by SFU'.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg)
+
+```
+
+graph TD
+    A[Call set-up to SFU] --> B[Identification of calling terminal by SFU]
+    B --> C[/Input of address(es)/]
+    C --> D[/Input of characters/]
+    D --> E{EOM received?}
+    E -- Yes --> C
+    E -- No --> F{EOM (ACK) received?}
+    F -- Yes --> C
+    F -- No --> G{EOT received?}
+    G -- Yes --> H[/ITD/]
+    G -- No --> I{Clear from caller within 30 seconds?}
+    I -- Yes --> H
+    I -- No --> J[/GA/]
+    J --> K{Resumption of char. input within 30 seconds?}
+    K -- Yes --> D
+    K -- No --> L[/BMC/]
+    L --> M[Message cancelled by SFU]
+    M --> N[Clear by SFU]
+    H --> N
+  
+```
+
+Flowchart showing the general procedure for message deposit into an SFU. The process starts with 'Call set-up to SFU', followed by 'Identification of calling terminal by SFU'. It then enters a loop of 'Input of address(es)' and 'Input of characters'. Decision diamonds check for 'EOM received?', 'EOM (ACK) received?', and 'EOT received?'. If 'EOM received?' is Yes, it loops back to 'Input of address(es)'. If 'EOM (ACK) received?' is Yes, it loops back to 'Input of address(es)'. If 'EOT received?' is Yes, it leads to 'ITD'. If 'EOT received?' is No, it checks 'Clear from caller within 30 seconds?'. If Yes, it leads to 'ITD'. If No, it leads to 'GA'. 'GA' leads to 'Resumption of char. input within 30 seconds?'. If Yes, it loops back to the entry point of the input loop. If No, it leads to 'BMC', which leads to 'Message cancelled by SFU'. Both 'Message cancelled by SFU' and 'ITD' lead to 'Clear by SFU'.
+
+T0102090-92/d02
+
+Figure 2/F.72 – General procedure for message deposit into an SFU
+
+**8.1.3** Each field within an address line and also each address line should be delimited in accordance with Recommendation U.80.
+
+**8.1.4** All fields within an address line except for 8.1.2 a) are optional and may be omitted at the discretion of the originating subscriber.
+
+**8.1.5** The address line(s) should be delimited from the message text by an End of Address (EOA) signal +.
+
+**8.1.6** In general, non-telex addresses should be input in accordance with Recommendation U.80, including the relevant service identifier (e.g. TTX, VTX, PDA)
+
+## **9 Abnormal conditions during message input**
+
+Abnormal conditions encountered during message input should be handled in accordance with Recommendation U.80.
+
+## **10 Message status enquiry**
+
+### **10.1 General procedures**
+
+**10.1.1** A message status enquiry facility should be provided internationally to provide information only in response to a status request from the originator. This message status enquiry point will be accessed by a separate access code to that used for message input.
+
+**10.1.2** When the SFU automatically provides advice of delivery and non-delivery, or a request for positive delivery can be indicated, then the provision of status enquiry facilities is optional.
+
+**10.1.3** Status enquiry information should be maintained preferably for 72 hours.
+
+**10.1.4** The answerback of the message originator should be used for identification and therefore needs to be retained by the SFU for this purpose.
+
+**10.1.5** In the case of multi-address messages, status information may be requested on:
+
+- a) all addresses associated with a message reference number;
+- b) addresses which have not yet received the message;
+- c) addresses specified by the originating telex subscriber.
+
+### **10.2 Status enquiry information field content**
+
+**10.2.1** The status enquiry should contain the following fields:
+
+- a) message reference information;
+- b) a status request;
+- c) address(es).
+
+**10.2.2** The status request indicates the information required (see 10.2.1).
+
+**10.2.3** The address(es) field, see 8.1.2 a), should only be included when status information has been requested for specific addresses.
+
+### **10.3 The status report**
+
+**10.3.1** The status report format should be consistent with the delivery/non-delivery notification advice format as described in Recommendation U.81.
+
+### **10.4 Status report field content**
+
+**10.4.1** The status report should contain the following fields where applicable for each address:
+
+- a) message reference number;
+- b) selection information;
+- c) expected answerback or part thereof;
+
+- d) notification, i.e. not delivered or delivered;
+- e) received answerback;
+- f) reason for non-delivery;
+- g) date and time of delivery;
+- h) duration of call.
+
+**10.4.2** The information contained in fields 10.4.1 e), g) and h) will only be included in a delivery notification whilst the information in field 10.4.1 f) will only be included in a non-delivery notification.
+
+**10.4.3** The information contained in field 10.4.1 f) should indicate to the subscriber the reason why the SFU has been unable to deliver the message to the address detailed in field 10.4.1 b). This information should describe the reason for failure on the latest or final attempt.
+
+**10.4.3.1** When a service signal is received by the SFU, this information shall be placed in the reason field.
+
+**10.4.3.2** Other reasons for non-delivery are:
+
+- a) Wrong answerback received from destination.
+
+The reason field content should be IAB (see 3.2.2).
+
+- b) Clear received by the SFU during message transmission.
+
+The reason field content should be PREM CLR.
+
+- c) Interruption of message transmission caused by receipt of characters at the SFU.
+
+The reason field content should be INTERRUPTED.
+
+- d) Address validation failure.
+
+The reason field content should be REJ.
+
+## **11      Delivery procedure**
+
+The technical aspects of message delivery are described in Recommendation U.81.
+
+**11.1** Clauses 11, 12 and 13 describe procedures for the delivery of international telex messages by an SFU and comprise the following:
+
+- a) message delivery procedures;
+- b) notification procedures;
+- c) delivery retry procedures.
+
+**11.2** The procedures should apply to all classes of message delivery.
+
+**11.3** The priority and time of message delivery should be the responsibility of the SFU that has accepted the input message for delivery.
+
+**11.4** In the case of international interworking between the SFUs, the priority and time of message delivery may be controlled by the originating or destination SFU subject to bilateral agreement between the Administrations concerned.
+
+**11.5** The term “delivery of messages” applies to the forwarding of messages, which were input into an SFU by an originating telex subscriber, to a telex subscriber over the international telex network.
+
+**11.6** The term “notification” applies to the forwarding of an advice of delivery/non-delivery of a message to the originating telex subscriber over an international telex circuit.
+
+### **11.7    Procedures for delivery of messages**
+
+**11.7.1** The sequence of the message forwarding procedure is illustrated in Figure 3.
+
+![Flowchart of the message delivery procedure (Figure 3/F.72). The process starts with 'Call set-up' (11.8.1), followed by 'Called party answerback taken'. A decision 'Called subscriber answerback valid? a)' (11.8.2) follows. If 'No', it goes to 'Ineffective call'. If 'Yes', it proceeds through 'Send SFU identity' (11.8.3), 'Send message identity' (11.8.4), 'Send originating subscriber answerback' (11.8.5), 'Send message text' (11.8.6), and 'Answerback of called subscriber'. A decision 'Answerback comparison?' (11.8.7) follows. If 'No', it goes to 'Ineffective call'. If 'Yes', it proceeds to 'Originating subscriber's answerback' (11.8.8) and 'SFU clear' (11.8.9). Both 'SFU clear' (11.8.9) and 'Ineffective call' lead to 'Notification of delivery/ non-delivery'. A decision 'Delivery retries?' (Recommendation U.40) is shown for the 'Ineffective call' path. A dashed line connects 'Send message text' (11.8.6) to a decision 'See 11.8.6.2', which then leads to the 'Delivery retries?' decision.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg)
+
+```
+
+graph TD
+    11.8.1[11.8.1 Call set-up] --> 11.8.2{11.8.2 Called subscriber answerback valid? a)}
+    11.8.2 -- No --> Ineffective[Ineffective call]
+    11.8.2 -- Yes --> 11.8.3[11.8.3 Send SFU identity]
+    11.8.3 --> 11.8.4[11.8.4 Send message identity]
+    11.8.4 --> 11.8.5[11.8.5 Send originating subscriber answerback]
+    11.8.5 --> 11.8.6[11.8.6 Send message text]
+    11.8.6 --> 11.8.7{11.8.7 Answerback comparison?}
+    11.8.7 -- No --> Ineffective
+    11.8.7 -- Yes --> 11.8.8[11.8.8 Originating subscriber's answerback]
+    11.8.8 --> 11.8.9[11.8.9 SFU clear]
+    11.8.9 --> Notification[Notification of delivery/ non-delivery]
+    Ineffective --> SFUclear[SFU clear]
+    SFUclear --> DeliveryRetries{Delivery retries? (Recommendation U.40)}
+    DeliveryRetries -- Yes --> CallSetUp[Call set-up]
+    DeliveryRetries -- No --> Notification
+    11.8.6 -.-> See11.8.6.2{See 11.8.6.2}
+    See11.8.6.2 -- Yes --> DeliveryRetries
+  
+```
+
+Flowchart of the message delivery procedure (Figure 3/F.72). The process starts with 'Call set-up' (11.8.1), followed by 'Called party answerback taken'. A decision 'Called subscriber answerback valid? a)' (11.8.2) follows. If 'No', it goes to 'Ineffective call'. If 'Yes', it proceeds through 'Send SFU identity' (11.8.3), 'Send message identity' (11.8.4), 'Send originating subscriber answerback' (11.8.5), 'Send message text' (11.8.6), and 'Answerback of called subscriber'. A decision 'Answerback comparison?' (11.8.7) follows. If 'No', it goes to 'Ineffective call'. If 'Yes', it proceeds to 'Originating subscriber's answerback' (11.8.8) and 'SFU clear' (11.8.9). Both 'SFU clear' (11.8.9) and 'Ineffective call' lead to 'Notification of delivery/ non-delivery'. A decision 'Delivery retries?' (Recommendation U.40) is shown for the 'Ineffective call' path. A dashed line connects 'Send message text' (11.8.6) to a decision 'See 11.8.6.2', which then leads to the 'Delivery retries?' decision.
+
+a) If requested by the originator.
+
+T0103230-93/d03
+
+Figure 3/F.72 – Message delivery procedure
+
+**11.8** The components of message forwarding procedures are as follows:
+
+#### **11.8.1 Call set-up**
+
+- a) Establishment of a connection by an SFU over the international telex network should use normal telex procedures. If a call connect signal is not received, the call attempt should be terminated and a retry made in accordance with Recommendation U.40.
+- b) If service signals are received during the call set-up cycle, the SFU should act in accordance with Recommendation U.40.
+
+#### **11.8.2 Called subscriber answerback validation**
+
+**11.8.2.1** To ensure security of delivery, the answerback of the called subscriber should be compared with the expected answerback of the called subscriber, if supplied by the originating telex subscriber.
+
+**11.8.2.2** One erroneous character displacement shall be tolerated in the validation process of the called subscriber's answerback.
+
+#### **11.8.3 SFU identification**
+
+The SFU identification should consist of the answerback sequence of the SFU, formatted in accordance with Recommendation F.60 and optionally preceded by the code expression CI.
+
+#### **11.8.4 Message identification**
+
+The SFU shall transmit to the called subscriber a message identification sequence issued at the time of input of the message in accordance with 3.1.
+
+#### **11.8.5 Answerback of originating telex subscriber**
+
+The answerback of the originating telex subscriber as received at the time of message deposit should then be sent to the called subscriber where this has been found to conform to Recommendation F.60. Otherwise, the telex SFU shall attach to the answerback of the originating telex subscriber the telex address as determined at the time of message deposit in accordance with Recommendation U.80. These two fields shall be separated by the character / , as follows:
+
+TRANS A LSA/23123456
+
+#### **11.8.6 Message text**
+
+**11.8.6.1** The SFU should transmit to the called subscriber any message header information together with the stored message in the format in which it was originated by the calling subscriber. The EOM/EOT separators and the WRU signal shall not be transmitted.
+
+**11.8.6.2** If any signal is received on the backward path during the message text delivery, transmission of the message should be stopped for two seconds. If during that time further signals or a clearing condition is received, the call shall be cleared, message delivery deemed unsuccessful and action taken in accordance with 3.9. If no further signals are received on the backward path during that time, transmission of the message shall be resumed.
+
+#### **11.8.7 Called subscriber answerback comparison**
+
+Following message transmission, the answerback of the called subscriber should be taken and compared with that received at the start of message delivery. If they are the same, the delivery of the message shall be deemed successful. Otherwise, the answerback of the called subscriber shall be taken again for comparison. If there is a second mismatch, the delivery of the message should be considered as unsuccessful and further delivery attempts shall be made in accordance with clause 13.
+
+#### **11.8.8 Answerback of originating telex subscriber**
+
+The answerback of the originating subscriber shall then be sent to the called subscriber.
+
+#### **11.8.9 Call clearing sequence**
+
+Following the transmission of its answerback, the SFU should clear the call using normal telex clearing procedures. However, in the case of delivery to a Teletex destination, clearing procedures should be in accordance with Recommendations F.201 and U.201.
+
+## **12 Notification procedures**
+
+### **12.1 Types of notification**
+
+The types of notification are shown in 3.9.
+
+### **12.2 Notification delivery procedures**
+
+**12.2.1** Status reports should be returned in response to a status request.
+
+**12.2.2** All other types of notification should be delivered using the procedure described for telex message forwarding in 11.7 and 11.8.
+
+**12.2.3** To ensure security of delivery of the notification, the answerback of the called subscriber should be compared with the answerback of the originating subscriber received at the time of message input.
+
+## **13 Delivery retry procedures**
+
+**13.1** The principles of Recommendation U.40 should be applied for all delivery/notification retry requirements.
+
+**13.2** The action to be taken when a notification cannot be delivered should be the responsibility of the Administration operating the SFU as described in 3.9.
+
+### **13.3 Recorded message from the called subscriber**
+
+**13.3.1** If the recorded message is followed by clear, the message shall be considered undeliverable.
+
+**13.3.2** The action to be taken by the SFU if the recorded message is not followed by a clear is for further study.
+
+## **14 Contents of delivery/non-delivery notifications**
+
+**14.1** The delivery/non-delivery notification should contain the same fields as shown for the status report in 10.4.1.
+
+## **15 Internationally interconnected store and forward units**
+
+The international interconnection of telex SFUs should be implemented using the procedures and functions of the Message Handling Services in accordance with the F.400-Series of Recommendations.
+
+# ITU-T RECOMMENDATIONS SERIES
+
+- Series A Organization of the work of the 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 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 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 communication
+- Series Z Programming languages
\ No newline at end of file
diff --git a/marked/F/T-REC-F.720-199208-I_PDF-E/raw.md b/marked/F/T-REC-F.720-199208-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..27f77b7c9127dac0eee5bb75d1ff578dc631e211
--- /dev/null
+++ b/marked/F/T-REC-F.720-199208-I_PDF-E/raw.md
@@ -0,0 +1,392 @@
+
+
+![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
+
+**CCITT**
+
+THE INTERNATIONAL  
+TELEGRAPH AND TELEPHONE  
+CONSULTATIVE COMMITTEE
+
+**F.720**
+
+(08/92)
+
+**TELEMATIC, DATA TRANSMISSION,  
+ISDN BROADBAND, UPT AND  
+TELECONFERENCE SERVICES:**
+
+**OPERATIONS AND QUALITY OF SERVICE**
+
+---
+
+**VIDEOTELEPHONY SERVICES – GENERAL**
+
+![CCITT logo: A globe with the letters CCITT.](84a1d09fb489061482111515543b60dc_img.jpg)
+
+CCITT logo: A globe with the letters CCITT.
+
+**Recommendation F.720**
+
+---
+
+# FOREWORD
+
+The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT 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 Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988).
+
+Recommendation F.720 was prepared by Study Group I and was approved under the Resolution No. 2 procedure on the 4th of August 1992.
+
+---
+
+# CCITT NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication Administration and a recognized private operating agency.
+
+# **VIDEOTELEPHONY SERVICES – GENERAL**
+
+(1992)
+
+The CCITT,
+
+*considering*
+
+- (a) that videotelephony services have been introduced in pilot form in various network environments in a number of countries;
+- (b) that videotelephony services are liable to be demanded by users around the whole world;
+- (c) that users will expect an acceptable minimum Quality of Service;
+- (d) that users will expect an ease of use comparable to ordinary telephony;
+- (e) that users will expect a high level of interoperability with other audiovisual services and with telephony,
+
+*adopts*
+
+the subsequent Recommendation dealing with the general description for videotelephony services.
+
+The relevant attributes and values are incorporated as part of each dedicated service description.
+
+# **CONTENTS**
+
+- 1 *Introduction*
+- 2 *Definition*
+- 3 *Description*
+- 4 *Procedures*
+- 5 *Network aspects*
+- 6 *Terminal aspects*
+- 7 *Quality of Service*
+- 8 *Interworking and intercommunication requirements*
+
+# **1 Introduction**
+
+The purpose of this Recommendation is to define and describe the general features and attributes of the videotelephony service regardless of the network environment where the service might be provided. The videotelephony service is classified in the following two main categories:
+
+- videotelephony service for narrow-band networks;
+- videotelephony service for broadband networks.
+
+The intention is to assign a dedicated Recommendation for each type of videotelephony service in specific networks. The dedicated Recommendation is due to contain a description in detail of the service concerned with all relevant characteristics and attributes. Recommendation F.721 covers the basic videotelephony service in the Integrated services digital network (ISDN) due to this classification. Dedicated service Recommendations for higher quality videotelephony services are for further study. The higher quality videotelephony service will not necessarily employ any fixed information transfer rate as variable bit rate coding may be used. The classification of videotelephony services is depicted in Figure 1/F.720.
+
+![A hierarchical diagram titled 'Classification of videotelephony services'. At the top level, a box labeled 'Videotelephony services' is enclosed in a dashed rectangle labeled '(Recommendation F.720)'. Below this box, two lines branch down to two separate boxes: 'Videotelephony for narrowband networks' on the left and 'Videotelephony for broadband networks' on the right. Below the 'narrowband' box, a line leads to a box labeled 'Videotelephony teleservice for ISDN (Recommendation F.721)'. Below the 'broadband' box, a line leads to a box labeled 'Broadband videotelephony services (Recommendation F.722)'. In the center, between the two bottom boxes, is a box labeled 'Note 2'.](2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg)
+
+```
+
+graph TD
+    subgraph F720 [Recommendation F.720]
+        VS[Videotelephony services]
+    end
+    VS --> VNN[Videotelephony for narrowband networks]
+    VS --> VBN[Videotelephony for broadband networks]
+    VNN --> VTISDN[Videotelephony teleservice for ISDN Recommendation F.721]
+    VBN --> BVS[Broadband videotelephony services Recommendation F.722]
+    Note2[Note 2]
+    VTISDN --- Note2 --- BVS
+  
+```
+
+A hierarchical diagram titled 'Classification of videotelephony services'. At the top level, a box labeled 'Videotelephony services' is enclosed in a dashed rectangle labeled '(Recommendation F.720)'. Below this box, two lines branch down to two separate boxes: 'Videotelephony for narrowband networks' on the left and 'Videotelephony for broadband networks' on the right. Below the 'narrowband' box, a line leads to a box labeled 'Videotelephony teleservice for ISDN (Recommendation F.721)'. Below the 'broadband' box, a line leads to a box labeled 'Broadband videotelephony services (Recommendation F.722)'. In the center, between the two bottom boxes, is a box labeled 'Note 2'.
+
+T0102080-92
+
+*Note 1* – In broadband ISDN the service offerings may also comprise videotelephony services using low bit rates.
+
+*Note 2* – In the future, videotelephony services may be provided also other networks requiring new dedicated service Recommendations.
+
+FIGURE 1/F.720  
+**Classification of videotelephony services**
+
+# 2 Definition
+
+**Videotelephony service** is an audiovisual conversational teleservice providing bidirectional symmetric real-time transfer of voice and moving colour pictures between two locations (person-to-person) via the networks involved. The minimum requirement is that under normal conditions the picture information transmitted is sufficient for the adequate representation of fluid movements of a person displayed in head and shoulders view (see Note).
+
+*Note* – The smoothness of the movements in the reproduced picture is essentially dependent on the amount of motion with respect to the transfer rate of transmitted picture information. The above requirements are supposed to be met under such conditions where the amount of motion is limited or the throughput is high enough not to impair the received picture. Degradation is likely to appear as increased blurring and jerkiness in the reproduced picture. Besides this, other artifacts may occur.
+
+# 3 Description
+
+## 3.1 General description
+
+The plain videotelephony service includes only the basic user requirements, namely speech and motion picture with essential controls and indications; the service can be enhanced with options providing auxiliary facilities such as transmission of high resolution still images of documents, photographs, drawings, charts, objects, etc. (see Note).
+
+*Note* – Speech supported only by still picture transmission and/or telewriting is not considered as a part of the videotelephony service. This type of communication may either be considered as a separate audiovisual service or as a form of audiographic conference service in a point-to-point configuration.
+
+The videotelephony service is likely to be used in much the same way as the ordinary telephone service for individual communication, the enhancement being in the visibility of the communicating parties which implies a number of possible new applications.
+
+An essential feature of the service is that it is always provided in conjunction with ordinary telephony allowing the user to intercommunicate with all kinds of audiovisual services by using merely the speech communication facility of a videotelephone terminal. In other words, videotelephone terminals must be capable of supporting telephony.
+
+A videotelephony service may also be used in applications such as communication of speech – and hearing – impaired persons using sign language and remote surveillance where the speech communication facility is of minor importance.
+
+In case the service is provided in a network and terminal environment which offers a number of different quality levels depending, among others, on the transmission medium used and respective charging, it must be possible for the user to select the level/mode of operation and/or type of videotelephony service he/she wishes and also change it during the call if provided by the network or supported by the terminals. The latter option may be provided as a supplementary service.
+
+Two different types of call shall be possible:
+
+- point-to-point calls;
+- multipoint calls (see Note).
+
+*Note* – For multipoint calls a unit for mixing speech signals and/or combining video signals is required. This will be defined in another context later.
+
+## 3.2 *Description of various videotelephony services*
+
+Two primary videotelephony service categories have been identified, for narrow-band networks and for broadband networks. The principle features of either type of service are described below.
+
+### 3.2.1 *Videotelephony service for narrow-band networks*
+
+The videotelephony service for narrow-band networks provides end-to-end communication of moving colour pictures with spatial resolution, temporal resolution and quality equivalent to that obtainable by coding the video signal according to Recommendation H.261 (QCIF and CIF format).
+
+The videotelephone service may be optionally enhanced by facilities such as the transfer of still pictures, graphics, text and end-to-end control messages.
+
+A basic videotelephone teleservice for the narrow-band ISDN has been fully standardized according to Recommendations I.210 and I.240. The stage 1 description for the videotelephony teleservice for ISDN is contained in Recommendation F.721.
+
+In the future, basic videotelephony services for other narrow-band networks (e.g. radio mobile networks, private networks) could be envisaged.
+
+### 3.2.2 *Videotelephony service for broadband networks*
+
+The videotelephony service for broadband networks provides end-to-end communication of moving colour pictures with high spatial and temporal resolution and video quality equivalent to conventional TV standards (PAL, SECAM, NTSC) or better and enhanced voice/sound quality, possibly stereo transmission and optionally facilities for the transfer of still pictures, graphics, text and end-to-end control messages.
+
+## 3.3 *Applications related to videotelephony*
+
+The videotelephony service can be utilized in a broad range of applications depending on the Quality of Service for audio and/or video that can be achieved in different types of services.
+
+A videotelephony service employing the bearer capabilities of broadband networks is expected to meet the needs of the subsequently listed applications. Because of the high video quality, this service provides, besides the means for face-to-face dialogue, the possibility to transfer any kind of moving scenes. Also pictures of three-dimensional objects, graphic material, e.g., sketches, drawings, photographs and documents containing text and graphics can be transferred without any restrictions. Commercial and domestic scenes, instruction procedures and films can be transferred to the communication partner.
+
+The constraints imposed by limited transfer capability of narrow-band networks on spatial and temporal image resolutions make certain types of communication less applicable to the videotelephony service for narrow-band networks.
+
+Taking into account the aspects mentioned above, the following principle applications of videotelephony are possible among others:
+
+- a) face-to-face dialogues involving at least head-and-shoulder images;
+- b) dialogue including interactive viewing of documents such as sketches, diagrams or charts and objects that can be shown on the screen;
+- c) access of the user to videoconferences;
+- d) remote video surveillance;
+- e) communication between hearing and speech impaired persons using the sign language.
+
+Based on these examples, other enhanced videotelephone applications may also emerge.
+
+The user should be given the possibility to select the essential parameters best suiting his specific application. For instance, in applications b) high spatial resolution is required and on the other hand in e), good motion tolerance is important. Moreover, the transfer rate used for audio should be selectable, in particular when it has charging or video quality implications.
+
+## 3.4 *Supplementary services and enhancements*
+
+The same spectrum of supplementary services supporting telephony is in principle applicable for videotelephony.
+
+Other supplementary services or enhancements, dedicated to videotelephony, e.g. videotelephony conference services, are for further study. Relevant enhancements are those supporting the transfer of high resolution still pictures and graphics information in a variety of formats like digitized video or other standard document formats. A paper/film scanner or video frame capture may be used as an image input source. Besides this, the possibility to access electronic mail or videotex services with a videotelephone terminal may be supported.
+
+## 3.5 *Specific terminology*
+
+*Fall back:* Procedures performed either by the network or by the calling terminal that allows the calling user to be connected in any case with the called user at any terminal where the call is offered (3.1 kHz telephone terminal or videotelephone terminal).
+
+# 4 **Procedures**
+
+## 4.1 *General*
+
+The call control procedures should be from the user's point of view as simple as for ordinary telephony in order to achieve good acceptance. The audible signalling tones must have the same meaning as for telephony. Visual guidance with the aid of the videotelephone terminal display may play an important role in the invocation and operation of the service.
+
+## 4.2 *Provision/withdrawal*
+
+Provision of the service will be by arrangement with the relevant Administration.
+
+## 4.3 *Normal procedures*
+
+### 4.3.1 *Activation/deactivation/registration*
+
+Not applicable.
+
+### 4.3.2 *Invocation and operation*
+
+#### 4.3.2.1 *Call request*
+
+The call set-up must be available for the user as a single operation, preferably not different from that for telephony.
+
+As a user option, the terminal can instead be set such that video communication is established only when requested by the users. If a call attempt involves more than one transmission channel, and not all transmission channels are available for the call (for whatever reasons), the call shall still proceed with the best level of video quality available. It must be possible for the user to select the transmission rate or other relevant parameters affecting on the service quality and respective service and tariff class.
+
+Call set-up from the user's point of view can be optionally executed by initiating first the voice communication and adding the videocommunication after the connection has been established.
+
+#### 4.3.2.2 *Call release*
+
+In general, the procedure for disconnecting a videotelephone call shall be the same as for ordinary telephony. Speech and image shall be disconnected simultaneously.
+
+#### 4.3.2.3 *Change of service*
+
+During a single call the change of service can be executed unrestricted as desired by the users with the aid of in-call modification procedures if provided by the network. A change of selected audiovisual capabilities is provided by in-band signalling and protocols.
+
+#### 4.3.2.4 *Videotelephony conference call*
+
+Conference facilities supporting the videotelephony service are necessary either in the network and/or at the user premises.
+
+The procedures and functions are for further study.
+
+#### 4.3.2.5 *Controls and indications*
+
+### 4.3.3 *User guidance*
+
+User guidance can take place in the form of dialogue between the system and the user: information concerning the status of the call can be displayed on the screen or on another possible display of a videotelephone terminal (both the calling and called party can apply). Guidance may be based on the display of alphanumeric characters in a selectable language, or by other visual means accompanied by appropriate audible announcements taking into account the needs of hearing and speech impaired users.
+
+The audible call progress signals used in any videotelephony service shall comply with those of ordinary telephony. Visual counterparts of the audible call progress signals should be defined and standardized.
+
+It must be possible for both the calling and called party to switch on and off the outgoing picture without disconnecting the connection allocated for video transmission. In case the outgoing picture is suppressed, a predetermined substitutional pictogram should be displayed on the screen of the remote terminal.
+
+Using a specific control, a user should be able to display the outgoing picture on the screen of the videotelephone terminal, either prior to call set-up or during the call (self view).
+
+### 4.3.4 *Auxiliary functionalities*
+
+It should be possible to display the picture of the communicating parties on the screen of either terminal, although not necessarily simultaneously.
+
+Hands-free and loudspeaking modes are desirable and may be provided in videotelephone terminals.
+
+Besides the suppression of the outgoing video information, it should be possible to mute the audio channel as desired by the user. The other party may receive an indication on the activated muting.
+
+## 4.4 *Exceptional procedures*
+
+In case of decreasing of service quality (e.g. due to high error rate or other network reasons) appropriate indication should be given for both parties, even if the problems concern only one direction.
+
+# 5 **Network aspects**
+
+For further study.
+
+# 6 **Terminal aspect**
+
+## 6.1 *General systems requirements*
+
+In order to perform the basic functions necessary for the videotelephony service the terminal equipment must include devices capable of:
+
+- capturing participant's picture(s);
+- displaying remote user's picture(s);
+- capturing audio;
+- reproducing audio;
+- audio coding;
+- video coding;
+- management of network interfaces.
+
+The terminal equipment also includes devices capable of performing the following functions:
+
+- user control;
+- user indication;
+- self view;
+- testing.
+
+Terminals intended to be used in multipoint connections may need additional basic functions related to multipoint operation. These functions are for further study.
+
+## 6.2 *Videotelephone terminal equipment*
+
+The basic videotelephone terminal equipment may include only the basic elements listed in 6.1.
+
+Possible enhancements to the equipment are:
+
+- orientable camera and zoom;
+- still picture camera;
+- interfaces for an additional camera, an additional screen or a video recorder;
+- remote control of a distant camera for some specific applications;
+- keyboard for the videotex service;
+- telewriting.
+
+This list is not exhaustive and is only given as a set of examples. As a general rule, the number of controls that a user has to operate should be kept to a minimum. Training should not be necessary for using the terminal. Clear and concise instructions should be given, for instance on the screen, especially for the supplementary services with which the user may not be very familiar.
+
+# 7 Quality of Service
+
+## 7.1 Picture quality
+
+Picture quality is a measure of the ability of a video transmission system to accurately reproduce moving scenes. Video quality objectives are generally expressed in terms of spatial and temporal resolution. Optimization and more accurate definition of the picture quality requires further study.
+
+The recovery time for pictures built-up when the video source is changed should be low enough not to impair the service quality. Further studies are required.
+
+### 7.1.1 Videotelephony service for narrow-band networks
+
+Optimization and more accurate definition of the picture quality including motion tolerance require further study (see Note).
+
+*Note* – The urgent need to accomplish both subjective and objective methods to evaluate the quality of a heavily compressed motion picture is widely identified.
+
+### 7.1.2 Videotelephony service for broadband networks
+
+Picture quality must be at least as that of high quality domestic TV-receivers (see among others, CCIR Recommendation R.601).
+
+## 7.2 Audio quality
+
+The minimum speech quality must be as good as that of ordinary PCM telephony based on either A-law or  $\mu$ -law encoding (at least no significant impairment is allowed with regard to Recommendation G.711).
+
+Efficient echo control must be provided in the local facilities as echoes may seriously impair the audio quality.
+
+## 7.3 Synchronization of speech and lip movement (lip synchronization)
+
+Lip synchronizm must be ensured. There should be no subjectively discernible difference of the speech signal with regard to the video.
+
+## 7.4 Overall delay
+
+The overall delay is defined to consist of the one-way delay of the transmission path and the characteristic delay of a videotelephone terminal. Characteristic delay of a videotelephone terminal is the delay introduced by the terminal when only lips and eyes of the talking user are moving.
+
+The overall effect on quality by the delays introduced by videocodecs and transmission facilities needs to be taken into account in the service because increased delays may impair the user acceptability.
+
+Maximum allowable delay including the maximum number of satellite hops are left for further study.
+
+For videotelephony services using separated digital channels it is possible that one or more channels are routed via terrestrial paths while the other(s) is (are) routed via satellite. In these cases the resynchronization is performed by the terminal. The Quality of Service is the same as if all channels were routed via satellite.
+
+## 7.5 Sensitivity to transmission errors
+
+The maximum allowable degradation of service due to transmission errors needs to be defined. Further study required.
+
+# 8 Interworking and intercommunication requirements
+
+The following interworking/intercommunication situations have been identified:
+
+- intercommunication with 3.1 kHz and 7 kHz telephony services;
+- intercommunication between videotelephony services on same and different networks;
+- intercommunication with other audio and visual services.
+
+## 8.1 Intercommunication/interworking with telephony services
+
+### 8.1.1 General principles
+
+Considering:
+
+- the fact that at the beginning of the introduction of the videotelephony service the number of videotelephone subscribers is negligible compared with the number of telephone subscribers;
+- that a user may have only one type of audiovisual terminal such as videotelephone, 7 kHz telephone or 3.1 kHz telephone,
+
+as a conclusion, a fundamental requirement must be met in order to avoid the situation where videotelephone subscribers can only communicate in a kind of closed user group. Therefore, it is essential, as a default procedure, that every videotelephone subscriber be able to reach from his videotelephone terminal every telephone subscriber.
+
+This condition must be met regardless of the technology applied in the local exchange to which the telephone subscriber is connected. This can lead to interworking or intercommunication situations.
+
+From the user's point of view, a very important attribute of the intercommunication/interworking solutions is a short call set-up delay. Therefore, when a solution is being developed, the set-up delay should be considered as a high priority performance characteristic.
+
+If in case of intercommunication, a videotelephone communication cannot be provided, a telephone call should be initiated. If then no call can be established, an appropriate cause indication shall be given to the calling user.
+
+Every telephone terminal must be able to reach every videotelephone terminal and vice versa. This requirement implies that a videotelephone terminal will be a multiservice terminal supporting also telephone calls as well as videotelephone calls.
+
+### 8.1.2 Description
+
+Terminals for all videotelephony service classes and cases shall, in any case, support voice encoding in accordance with Recommendation G.711 (A-law and  $\mu$ -law). A videotelephony service may include additional speech encoding as a basic or optional feature depending on the precise service and mode.
+
+Videotelephony service shall intercommunicate with 3.1 kHz, 7 kHz or possibly 15 kHz telephony. The following cases are considered essential:
+
+- 1) Under the user's control, videotelephony requesting outgoing calls shall be able to initiate:
+  - videotelephone calls;
+  - ordinary 3.1 kHz telephone calls;
+  - telephone calls with extended bandwidth of 7 kHz or possibly 15 kHz, if supported by the terminal of the calling party.
+- 2) For incoming calls, a videotelephone terminal shall be able to respond on a default basis to:
+  - videotelephone calls;
+  - ordinary 3.1 kHz telephone calls;
+  - telephone calls with extended bandwidth of 7 kHz or possibly 15 kHz, if supported by the terminal of the called party.
+
+## 8.2 *Intercommunication between videotelephony services on different networks*
+
+Intercommunication between videotelephony services on the existing and future networks should also be provided. Further studies are required.
+
+## 8.3 *Intercommunication with other audiovisual services*
+
+G.711 telephony is the minimum requirement of intercommunication between all types of audiovisual services. Intercommunication or interworking with various types of videoconferencing should be provided. The audiovisual quality is in this case the best common mode. Further studies are required.
\ No newline at end of file
diff --git a/marked/F/T-REC-F.731-199707-I_PDF-E/raw.md b/marked/F/T-REC-F.731-199707-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..97e585bd52bc0b5778349f12178df90b675abad6
--- /dev/null
+++ b/marked/F/T-REC-F.731-199707-I_PDF-E/raw.md
@@ -0,0 +1,271 @@
+
+
+![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
+
+**F.731**
+
+(07/97)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Audiovisual services
+
+---
+
+**Multimedia conference services in the ISDN**
+
+ITU-T Recommendation F.731
+
+(Previously CCITT Recommendation)
+
+---
+
+# ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1–F.109          |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| MOBILE SERVICE                                                  | F.110–F.159        |
+| Mobile services and multdestination satellite services          | F.110–F.159        |
+| TELEMATIC SERVICES                                              | F.160–F.399        |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400–F.499        |
+| DIRECTORY SERVICES                                              | F.500–F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550–F.599        |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600–F.699        |
+| <b>AUDIOVISUAL SERVICES</b>                                     | <b>F.700–F.799</b> |
+| ISDN SERVICES                                                   | F.800–F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850–F.899        |
+| HUMAN FACTORS                                                   | F.900–F.999        |
+
+*For further details, please refer to ITU-T List of Recommendations.*
+
+# **ITU-T RECOMMENDATION F.731**
+
+# **MULTIMEDIA CONFERENCE SERVICES IN THE ISDN**
+
+## **Source**
+
+ITU-T Recommendation F.731 was prepared by ITU-T Study Group 16 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 10th of July 1997.
+
+## FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the 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.
+
+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
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The 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, the ITU had/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 1997
+
+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 the ITU.
+
+## CONTENTS
+
+|                                                    | Page |
+|----------------------------------------------------|------|
+| 1 Introduction .....                               | 1    |
+| 4.3 Configuration.....                             | 1    |
+| 4.4 Roles of the participants .....                | 1    |
+| 4.5 Terminal aspects.....                          | 1    |
+| 6.2.7 Conference management procedures .....       | 2    |
+| 7.2 List of service profiles .....                 | 2    |
+| 8 Interworking/intercommunication.....             | 2    |
+| 9 Attributes values.....                           | 3    |
+| 9.1 General .....                                  | 3    |
+| 9.2 Service independent attributes.....            | 3    |
+| 9.3 Service specific attributes.....               | 4    |
+| Annex A – Multipoint Conference Units (MCUs) ..... | 5    |
+
+
+
+# **MULTIMEDIA CONFERENCE SERVICES IN THE ISDN**
+
+*(Geneva, 1997)*
+
+## **1 Introduction**
+
+This Recommendation describes the Multimedia Conference Services supported by an ISDN. It relies on Recommendation F.702 for the main body of the description, and only gives the specific complements relevant to the ISDN, which derive from its capabilities and its limitations. Thus when reading this Recommendation, it is necessary to refer back to Recommendation F.702. The numbers of the clauses are those of Recommendation F.702, and thus they do not form a continuous sequence because only a few clauses need a specific complement for the ISDN. In addition there is a new clause 9 on the attributes for the various profiles.
+
+### **4.3 Configuration**
+
+In the ISDN, all connections are bidirectional symmetric. When several B-channels are used, they are synchronized through the frame alignment process of Recommendation H.221, so that a single composite channel is formed, where audio, video, data and control signals are multiplexed and are allocated specific subchannels. Data and enhanced control signals may be multiplexed in a common packet subchannel supporting the T.120-Series protocol (whereas basic control signals are in the BAS channel of Recommendation H.221).
+
+The various possible configurations supported by these connections are as follows:
+
+- a) point-to-point between two terminals;
+- b) multichannel multipoint for the continuous presence mode;
+- c) shared channel around one or more MCUs: the audio channels are mixed, the data signals are multiplexed (if present) in a common T.120 subchannel; this is the usual mode in the case of an audiographic conference or of CDH without video (see 7.1/F.702); when video is present, the pictures from the different sources are combined into a single picture with several windows;
+- d) switched multipoint operation: the audio signals or the video signals or both are switched in the MCU(s); this is the usual mode for the videoconference service, with mixed audio and a single switched video picture; multiple switched video subpictures are for further study.
+
+### **4.4 Roles of the participants**
+
+The basic control signals in the BAS channel allocate the roles of Chairman and controller jointly; they can only be separated inside the terminal equipment. The T.120-Series protocol allows separate allocation of call control, chair control and facility control.
+
+### **4.5 Terminal aspects**
+
+The normal audio mode for conferencing services is wideband audio conforming to Recommendation G.722. A G.711 codec should also be present for interworking purposes. G.728 coding may also be used in interworking or fallback situations, or temporarily to leave a larger bandwidth to the video or to the data subchannels, e.g. while showing an object or transmitting a document.
+
+Video codecs should conform to Recommendation H.261. The possible use of higher quality codecs is for further study.
+
+#### **6.2.7 Conference management procedures**
+
+All terminals should conform to the procedures in Recommendation H.242. Multipoint procedures are those of Recommendation H.243.
+
+Media components other than audio and video should be transmitted on a common data subchannel supporting the T.120-Series protocol.
+
+### **7.2 List of service profiles**
+
+The following service profiles may be offered over an ISDN.
+
+- 1) *Videoconference services*
+  - Profiles 1a: Basic videoconference service on two B-channels; terminals should conform to Recommendation H.320;
+  - Profiles 1b: Standard videoconference service on six B-channels (or one H0-channel); terminals should conform to Recommendation H.320;
+  - Profile 1c: Enhanced videoconference service; for further study;
+  - Profile 1d: High quality videoconference service; for further study.
+- 2) *Audiographic conference services*
+  - Profiles 2: All audiographic conference services use wideband audio conforming to Recommendation G.722 and a data subchannel supporting the T.120-Series protocol.
+- 3) *Cooperative document handling services*
+  - Profiles 3: All cooperative document handling services have audio to one or more of the Recommendations G.711, G.722, G.728; they have a data subchannel supporting the T.120-Series protocol, and in particular T.127 for file transfer; other data functions are for further study; H.261 video is optional.
+- 4) *Videophone conference supplementary services*
+  - Profile 4b: Basic videophone conference supplementary service; this supplementary service applies to basic videophone terminals on one or two B-channels, and does not require any specific enhancements to the terminals; these terminals conform to Recommendation H.320, have G.728 and/or G.722 audio codecs (and G.711 for interworking purposes) and H.261 video codecs; on two B-channels, the profile is the same as Profile 1a except that G.722 coding is only optional instead of mandatory.
+
+## **8 Interworking/intercommunication**
+
+All terminals have the media component audio. The basic common audio mode is G.722. However, some videophone terminals (and possibly some CDH terminals) may not have that capability; in that case G.711 is used, or alternatively G.728 if all terminals in the conference have that capability.
+
+For the media component video, all terminals which support it use H.261 coding. They will always be able to communicate with this coding algorithm, by aligning the bit rate of the video subchannel on the lowest bit rate. If the resulting quality is not sufficient, then a higher bit rate may be chosen, with some terminals relegated to secondary status and participating with sound (and possibly data) only.
+
+For the other media components, all terminals using them have a common data subchannel with the T.120 protocol. The bit rate of the subchannel will be aligned on the terminal with the lowest bit rate capability. However, this does not imply that all terminals will have a common media component. For instance a group of participants may be able to exchange facsimile while another group (overlapping or not) may exchange still pictures.
+
+## 9 Attributes values
+
+### 9.1 General
+
+In the ISDN, only point-to-point independent channels can be established. When several B-channels are used in a connection, they are based on separate independent calls and synchronized in-band. Similarly, in a multipoint configuration, each connection between a terminal and an MCU or between two MCUs is an independent point-to-point connection. The same also applies for H0-channels.
+
+When two or more B- (or H0-) channels are needed to support a connection, one of them supports the audio and BAS control subchannels; the call for establishing this channel is referred to as Call 1. Except when otherwise stated, the values of the attributes are the same for Call 1 and for the other calls involved in the connection.
+
+### 9.2 Service independent attributes
+
+The following attribute values are applicable to all multimedia conference service profiles.
+
+#### 1) *Low layer attributes*
+
+|   | Attributes                     | Values                                                                                                             |
+|---|--------------------------------|--------------------------------------------------------------------------------------------------------------------|
+| 1 | Transfer mode                  | Circuit                                                                                                            |
+| 2 | Transfer rate                  | 64 kbit/s                                                                                                          |
+| 3 | Transfer capability            | Call 1: unrestricted digital information with tones/announcements<br>Other calls: unrestricted digital information |
+| 4 | Structure                      | 7 kHz integrity                                                                                                    |
+| 5 | Establishment of communication | Demand or reservation                                                                                              |
+| 6 | Symmetry                       | Bidirectional symmetric                                                                                            |
+| 7 | Configuration of call          | Point-to-point                                                                                                     |
+
+#### 2) *Access attributes*
+
+|     | <b>Attributes</b>                    | <b>Values</b>                                                |
+|-----|--------------------------------------|--------------------------------------------------------------|
+| 8   | Access channel and rate              | D(16) or D(64) for signalling,<br>B(64) for user information |
+| 9.1 | Signalling access protocol, Layer 1  | Rec. I.430/I.431                                             |
+| 9.2 | Signalling access protocol, Layer 2  | Rec. Q.921                                                   |
+| 9.3 | Signalling access protocol, Layer 3  | Rec. Q.931                                                   |
+| 9.4 | Information access protocol, Layer 1 | Rec. H.221                                                   |
+| 9.5 | Information access protocol, Layer 2 | Rec. H.230                                                   |
+| 9.6 | Information access protocol, Layer 3 | Rec. H.242, Rec. H.243                                       |
+
+### **9.3 Service specific attributes**
+
+The following attribute values are applicable to the communication as a whole, even when two or more separate calls are established in the network to support the required connection. They are generally dependent upon the multimedia conference service profiles.
+
+#### 3) *High layer attributes*
+
+|    | <b>Attributes</b>          | <b>Values</b>                                                                                                                                                                                |
+|----|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 10 | Type of user information   | Audio (in Call 1 only) + video<br>and/or data                                                                                                                                                |
+| 11 | Layer 4 protocol functions |                                                                                                                                                                                              |
+| 12 | Layer 5 protocol functions |                                                                                                                                                                                              |
+| 13 | Layer 6 protocol functions | Rec. G.711, Rec. G.722 or<br>Rec. G.728 for audio<br>Rec. H.261 for video (profiles 1, 4,<br>optional for profile 3)<br>T.120-Series for data (profiles 2, 3,<br>optional for profiles 1, 4) |
+| 14 | Layer 7 protocol functions |                                                                                                                                                                                              |
+
+#### 4) *General attributes*
+
+|    | <b>Attributes</b>                             | <b>Values</b>                                                                                                                                                                                                                        |
+|----|-----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 15 | Supplementary services provided               | For further study                                                                                                                                                                                                                    |
+| 16 | Quality of service                            | Audio: 7 kHz telephony for profiles 1, 2 telephone quality for profiles 3, 4<br>Video: see 5.3.2.2/F.702<br>Synchronization of audio and video: no subjectively discernible delay between sound and image<br>Data: for further study |
+| 17 | Intercommunication/interworking possibilities | With other multimedia conference services<br>with videophone service<br>with telephony<br>with other services: for further study                                                                                                     |
+| 18 | Operation and commercial aspects              | For further study                                                                                                                                                                                                                    |
+
+## ANNEX A
+
+### **Multipoint Conference Units (MCUs)**
+
+MCUs shall conform to Recommendation H.231 and use the procedures of Recommendation H.243.
+
+In a conference, all connections have the same overall bit rate and the same allocation of bit rates to the audio, video and data subchannels, whether between a terminal and an MCU or between MCUs. The exception to this is the connection to a terminal with secondary status, which cannot use all the subchannels and may thus be connected at a smaller bit rate. The possibility of additional or broader subchannels on inter-MCU connections is for further study.
+
+
+
+# ITU-T RECOMMENDATIONS SERIES
+
+- Series A Organization of the work of the 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 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 communication
+- Series Z Programming languages
\ No newline at end of file
diff --git a/marked/F/T-REC-F.733-200509-I_PDF-E/raw.md b/marked/F/T-REC-F.733-200509-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..ef19ea628ff61eed41d1d03dcbe481c08f86b8a3
--- /dev/null
+++ b/marked/F/T-REC-F.733-200509-I_PDF-E/raw.md
@@ -0,0 +1,546 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.733**
+
+(09/2005)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Audiovisual services
+
+---
+
+**Service description and requirements for  
+multimedia conference services over IP  
+networks**
+
+ITU-T Recommendation F.733
+
+# ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+## **TELEGRAPH SERVICE**
+
+|                                                                 |             |
+|-----------------------------------------------------------------|-------------|
+| Operating methods for the international public telegram service | F.1-F.19    |
+| The gentex network                                              | F.20-F.29   |
+| Message switching                                               | F.30-F.39   |
+| The international telemessage service                           | F.40-F.58   |
+| The international telex service                                 | F.59-F.89   |
+| Statistics and publications on international telegraph services | F.90-F.99   |
+| Scheduled and leased communication services                     | F.100-F.104 |
+| Phototelegraph service                                          | F.105-F.109 |
+
+## **MOBILE SERVICE**
+
+|                                                        |             |
+|--------------------------------------------------------|-------------|
+| Mobile services and multdestination satellite services | F.110-F.159 |
+|--------------------------------------------------------|-------------|
+
+## **TELEMATIC SERVICES**
+
+|                                           |             |
+|-------------------------------------------|-------------|
+| Public facsimile service                  | F.160-F.199 |
+| Teletex service                           | F.200-F.299 |
+| Videotex service                          | F.300-F.349 |
+| General provisions for telematic services | F.350-F.399 |
+
+## **MESSAGE HANDLING SERVICES**
+
+F.400-F.499
+
+## **DIRECTORY SERVICES**
+
+F.500-F.549
+
+## **DOCUMENT COMMUNICATION**
+
+|                                      |             |
+|--------------------------------------|-------------|
+| Document communication               | F.550-F.579 |
+| Programming communication interfaces | F.580-F.599 |
+
+## **DATA TRANSMISSION SERVICES**
+
+F.600-F.699
+
+## **AUDIOVISUAL SERVICES**
+
+**F.700-F.799**
+
+## **ISDN SERVICES**
+
+F.800-F.849
+
+## **UNIVERSAL PERSONAL TELECOMMUNICATION**
+
+F.850-F.899
+
+## **HUMAN FACTORS**
+
+F.900-F.999
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# **Service description and requirements for multimedia conference services over IP networks**
+
+## **Summary**
+
+The purpose of this Recommendation is to define the multimedia conference services based on IP networks. The service provides real-time communication between several users in different locations over an IP network. The service description, functional model, application scenarios and requirements of the IP multimedia conference services are provided. The IP multimedia conference service is one class of the generic services identified in ITU-T Rec. F.702, and its description follows the methodology described in ITU-T Rec. F.701. The requirements for the IP multimedia conference services are derived from the scenarios for different applications the said services can support. Therefore, the services requirements accommodate the demands of different kinds of users and assist in enabling intercommunications between the services systems provided by different telecom operators, or between the equipment manufactured by different manufacturers.
+
+###### **Source**
+
+ITU-T Recommendation F.733 was approved on 13 September 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 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 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   | Definitions .....                                | 1  |
+| 4   | Convention.....                                  | 2  |
+| 5   | Prose description.....                           | 2  |
+| 6   | Application functional model .....               | 3  |
+| 6.1 | Functional model .....                           | 3  |
+| 6.2 | Multimedia conference mode .....                 | 4  |
+| 6.3 | User roles.....                                  | 4  |
+| 7   | Scenarios.....                                   | 5  |
+| 7.1 | Multimedia interactive conference .....          | 5  |
+| 7.2 | Multicast conference .....                       | 7  |
+| 7.3 | Mixed mode conference .....                      | 7  |
+| 8   | Requirements of IP multimedia conference .....   | 8  |
+| 8.1 | User requirements.....                           | 8  |
+| 8.2 | Application requirements .....                   | 9  |
+| 8.3 | Numbering requirements .....                     | 9  |
+| 8.4 | Security requirements.....                       | 9  |
+| 8.5 | Authentication and accounting requirements ..... | 10 |
+| 8.6 | QoS requirements .....                           | 10 |
+| 9   | Interworking and intercommunication .....        | 10 |
+| 9.1 | Terminals with different capabilities.....       | 10 |
+| 9.2 | Terminals in different networks .....            | 10 |
+| 9.3 | Different IP multimedia conference systems ..... | 11 |
+
+
+
+# Service description and requirements for multimedia conference services over IP networks
+
+# 1 Scope
+
+This Recommendation describes the multimedia conference service system over IP networks, its application scenarios and service 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.
+
+## 2.1 Normative references
+
+None.
+
+## 2.2 Informative references
+
+- ITU-T Recommendation F.700 (2000), *Framework Recommendation for multimedia services*.
+- ITU-T Recommendation F.701 (2000), *Guideline Recommendation for identifying multimedia service requirements*.
+- ITU-T Recommendation F.702 (1996), *Multimedia conference services*.
+- ITU-T H-Series Recommendations – Supplement 1 (1999), *Application profile – Sign language and lip-reading real-time conversation using low bit-rate video communication*.
+
+# 3 Definitions
+
+This Recommendation defines the following terms:
+
+**3.1 chairman:** the user who chairs the meeting and manages the conference.
+
+**3.2 communication mode:** a communication mode is defined by the various channels supporting the media used for the conference. Changes in communication mode may occur during the course of the conference, in order to set up or eliminate one of the media, or to change its quality level and thus the bit-rate allocation. The mode change may be used for instance to temporarily add a channel for transmitting still pictures.
+
+**3.3 conference convener:** The user who has organized the conference.
+
+**3.4 centralized multipoint conference:** A centralized multipoint conference is one in which all participating terminals communicate in a point-to-point fashion with special control or processing facilities.
+
+**3.5 decentralized multipoint conference:** A decentralized multipoint conference is one in which the participating terminals multicast their audio, video and text to all other participating terminals.
+
+**3.6 IP multimedia conference service:** A type of multimedia conference service based on IP network that utilizes networks for control and media transfer.
+
+**3.7 multicast conference:** A multicast conference is one in which there is one transmitter of media streams and many receivers. There is no bidirectional transmission of control or media streams. Such conferences may be implemented using network transport multicast facilities, if available.
+
+**3.8 multipoint interactive conference:** A multipoint interactive conference is one in which all participants are transmitters and receivers. There is bidirectional transmission of control or media streams. Such conferences should be implemented using special control or processing facilities, if available.
+
+**3.9 multimedia conference service:** A multimedia conference service provides real-time transmission of voice together with motion video, real time text and/or various types of multimedia information between groups of users in two or more locations.
+
+**3.10 muting:** Preventing sound to be transmitted from a terminal equipment.
+
+**3.11 presenter:** The participant in a conference who controls the visual information being actively discussed.
+
+# 4 Convention
+
+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.
+
+# 5 Prose description
+
+An IP multimedia conference system provides real-time communication between several users in different locations, combining the audio, video and real-time text information of the participants, and other multimedia information if needed.
+
+The service can be bidirectional, and provide for interconnection of two or more multimedia conference terminals on an equal basis; it can also be unidirectional, where part of the terminals can only receive, while others can only send. If there are two or more terminals in the conference, equipment that can provide multimedia information control and exchange is needed. Network side equipment that can manage and control the conference, and provide authentication and billing is also necessary.
+
+The multimedia conference services may be provided after prior arrangement with a service provider, or they may be generally available. The conference connection can be established by a user or by a management system.
+
+The location of a multimedia conference participant could be anywhere where the network is accessible, e.g., meeting room, office, home, or even on the highway. The participants take part in the meeting by means of a multimedia conference terminal. The terminals may access the network by wire or wireless means. There are three types of terminal:
+
+- Hardware-based terminals, which include two sub-types of terminal:
+  - a) Special conference terminals for studios dedicated to and equipped for multimedia conferences;
+  - b) Portable terminals which are only used on a part-time basis for teleconferencing and which can be moved from one place to another.
+
+- Software-based terminals running on computers.
+- Other types of terminals, e.g., POTS terminals, could also be used in the conference. Although there are certain limitations regarding their capability to send and receive different types of information used in a multimedia conference call, they are at least able to exchange speech, allowing their users to take part in the discussion.
+
+# 6 Application functional model
+
+## 6.1 Functional model
+
+![Figure 1/F.733 – The multimedia conference functional model. The diagram shows the functional architecture of a multimedia conference system. At the top, an 'AAA' (Authentication, Authorization, Accounting) block is connected to a 'Conference management & control' block via a thick double-headed arrow (AAA information streams). The 'Conference management & control' block is connected to a 'Voice/video/data switch & process' block via a dashed double-headed arrow (Conference management & control information streams). Below the 'Conference management & control' block, a 'user' block is connected via a dash-dot double-headed arrow (User's conference management message). The 'user' block is also connected to an 'IP multimedia conference terminal' block via a dashed double-headed arrow. The 'IP multimedia conference terminal' block is connected to a 'Voice/video/data switch & process' block via a solid double-headed arrow (Multimedia information streams). The 'Voice/video/data switch & process' block is connected to an 'interworking' block via a thick double-headed arrow. The 'interworking' block is connected to an 'Other multimedia conference terminal' block via a thick double-headed arrow. A horizontal dashed line labeled 'IP-based network' separates the network functions (above the line) from the user functions (below the line). A label 'a' is placed near the 'interworking' block. A legend at the bottom left defines the line types: solid for Multimedia information streams, dashed for Conference management & control information streams, dash-dot for User's conference management message, and thick for AAA information streams. The label 'F.733_F01' is in the bottom right corner.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+Figure 1/F.733 – The multimedia conference functional model. The diagram shows the functional architecture of a multimedia conference system. At the top, an 'AAA' (Authentication, Authorization, Accounting) block is connected to a 'Conference management & control' block via a thick double-headed arrow (AAA information streams). The 'Conference management & control' block is connected to a 'Voice/video/data switch & process' block via a dashed double-headed arrow (Conference management & control information streams). Below the 'Conference management & control' block, a 'user' block is connected via a dash-dot double-headed arrow (User's conference management message). The 'user' block is also connected to an 'IP multimedia conference terminal' block via a dashed double-headed arrow. The 'IP multimedia conference terminal' block is connected to a 'Voice/video/data switch & process' block via a solid double-headed arrow (Multimedia information streams). The 'Voice/video/data switch & process' block is connected to an 'interworking' block via a thick double-headed arrow. The 'interworking' block is connected to an 'Other multimedia conference terminal' block via a thick double-headed arrow. A horizontal dashed line labeled 'IP-based network' separates the network functions (above the line) from the user functions (below the line). A label 'a' is placed near the 'interworking' block. A legend at the bottom left defines the line types: solid for Multimedia information streams, dashed for Conference management & control information streams, dash-dot for User's conference management message, and thick for AAA information streams. The label 'F.733\_F01' is in the bottom right corner.
+
+**Figure 1/F.733 – The multimedia conference functional model**
+
+The IP multimedia conference functional model is shown in Figure 1. Multimedia conference terminals can access IP-based networks with several kinds of modes, e.g., LAN, WLAN, xDSL, PLMN, and PSTN.
+
+Network functions above the dashed line constitute an IP multimedia conference service platform directly related with users:
+
+- a) Conference Management and Control Function: it can initiate an immediate conference according to the user's demand, or accept the user's conference reservation and allocate the system resource.
+- b) Multimedia Switch and Process Function: it provides control functions to the conference, switches and processes the audio, video and text, and/or data streams.
+- c) Interworking function: other multimedia conference terminals can access the IP multimedia conference network via the interworking function.
+- d) Authentication, Authorization and Accounting (AAA): it provides the Conference Management and Control Function with the user's identification information, and processes accounting information from the Conference Management and Control Function.
+
+## 6.2 Multimedia conference mode
+
+Two types of basic multimedia conferences service modes are addressed in this Recommendation. Other types are left to the creativity of the service providers and equipment manufacturers.
+
+### a) *Multipoint interactive conference mode*
+
+In this mode, all participating terminals communicate in a point-to-point fashion, possibly with the involvement of the Multimedia Switch & Process Function. The centralized multipoint conference, and the decentralized multipoint conference are two examples.
+
+### b) *Multicast conference mode*
+
+In this mode, only one terminal in the conference transfers local multimedia information streams to the Multimedia Switch & Process Function, but does not receive them. Other terminals in the conference only receive the information from Multimedia Switch & Process Function but do not transfer information themselves.
+
+## 6.3 User roles
+
+According to their different roles in the conference, users can be identified as a Conference Controller, Conference Chairman and Conference Participant.
+
+A Conference Convener can initiate a conference on demand or reserve a conference. The conference convener is also the conference controller. The accounting information is bound to the role of Conference Convener. The role of Conference Controller can be moved to another user or terminal. The basic<sup>1</sup> functions include:
+
+- a) Reserving a conference;
+- b) Cancelling/modifying the reservation;
+- c) Initiating a conference on demand;
+- d) Terminating the conference;
+- e) Inviting a new participant;
+- f) Accepting a new participant;
+- g) Disconnecting a participant from the conference.
+
+Controller's advanced<sup>1</sup> functions include:
+
+- a) Splitting the conference;
+- b) Extending the conference.
+
+During a conference, a participant can apply to be chairman. A chairman is responsible for its management. Basic functions are:
+
+- a) Managing the conference;
+- b) Displaying him or herself, or one of the other participants, on the terminal screens.
+
+The chairman's advanced functions include:
+
+- a) Giving the floor to a participant;
+- b) Ensuring the conference terminals broadcast in turn;
+- c) Muting another terminal;
+- d) Organizing or allowing a private conversation;
+
+---
+
+<sup>1</sup> In this Recommendation, "basic" refers to a mandatory requirement, while "advanced" refers to a suggested but optional feature or procedure.
+
+- e) Controlling data transfer;
+- f) Controlling remote equipment.
+
+The conference participant's basic functions include:
+
+- a) Participation in the conference;
+- b) Muting local microphones.
+
+The conference participant's advanced functions include:
+
+- a) Requesting to be nominated as chairman;
+- b) Requesting the floor;
+- c) Receiving certain indicative information, such as site and time;
+- d) Initiating a data conference, such as remote collaboration and transferring of files;
+- e) Recording the conference.
+
+# **7 Scenarios**
+
+This clause describes typical service scenarios illustrating the multimedia conference service and deriving its service requirements.
+
+## **7.1 Multimedia interactive conference**
+
+### **7.1.1 Formal conference**
+
+TTP is a big international company. Annually, a highly formal conference is held to sum up the year's work on the 10th December. S is the CEO of the company who makes a report on all aspects of the company to the board of directors. The directorate consists of 5 members. Generally, these directors are located in different locations. Their offices are equipped with special conference terminals. Usually, the year-end reporting conference progresses in the following way:
+
+Step 1: Reserve the conference. Conventionally, the CEO's secretary submits information such as the starting time, the duration of the conference, participants, the bandwidth, codec and text requirement to the multimedia conferencing system in advance. Since this conference is very formal, the bandwidth is set to the largest value that the system supports, in order to achieve a high resolution of images.
+
+Step 2: As the scheduled time approaches, the conferencing system calls each reserved terminal. S's secretary, together with the other six formal participants, participates in the conference to log the conference. He may only listen but may not take the floor. There is also a typing interpreter booked for the meeting because C has a hearing impairment and needs to have simultaneous text support to be sure he perceives everything correctly. When the conference is established, director A applies to be the chairman, and then begins to moderate the conference.
+
+Step 3: The chairman lets the CEO of the company speak. S has organized the contents into PPT formats. When he begins to report, all participants' screens are divided into two parts. The PPT is on the background while a movable window is displaying S who is speaking on the foreground. The chairman thinks that the picture is not clear enough, nor the voice loud enough. He then adjusts S's camera and the microphone to ensure everyone sees and hears S clearly. The typed interpretation of the speaker appears in a text window directly under the video image.
+
+Step 4: Director B is confused by a figure in the presentation. He then presses the floor key. When A receives the request, he notifies S to pause, and lets B speak. Then all participants, except B, can see B, while B sees his previous speaker's picture, that is, the picture of S. When B finishes speaking, S takes the floor again. S then answers the question and sends the related report forms to other participants to make the problem clear.
+
+Step 5: The typing interpreter listens in on the conference and types on a chord keyboard at normal talking speed. C can perceive the conference very well by combining the hearing, the good quality, smooth video that provides the possibility for lip reading, and the types interpretation. C asks to make a short comment and the chairman gives him the floor to make an important comment from his long experience in the company.
+
+Step 6: Since S's speech is longer than planned, the reserved time will soon run out after the discussion. The chairman extends the conference by half an hour. When S finishes speaking, the chairman changes the conference to voice control mode. Text control mode may be also supported. The person who takes floor is displayed on the screens of other participants. But the participants feel uncomfortable with this mode, so the chairman applies six sub-pictures. The participants can then see each other.
+
+Step 7: After the discussion, the chairman begins to make a summary. The video is changed to display the chairman only. A praises the company's achievement, and points out what should be improved. Then A cancels his chairmanship, and they chat at random.
+
+Step 8: The conference is over. The participants say good-bye to each other. The conference is terminated automatically after everyone has left.
+
+Step 9: After the conference, the typed interpretation is kept for the secretary who will draw up the formal minutes of the meeting.
+
+### **7.1.2 Discussion conference**
+
+While the year-end conference is in progress, the engineers of the company, located in different places, are discussing their new product via the multimedia conference system. They use portable desktop terminals. The conference progresses in the following way:
+
+Step 1: John is in charge of the new product. Since he is going to introduce the new product, he uses the special conference terminal located in the assembly room, whose performance is better than others. First, he calls the other twenty engineers named B, C, D, E, etc., who are in charge of the different aspects of the product. Each engineer has a terminal. Due to the capability restriction of the other desktop terminals, the bandwidth is lower. The resolution of the picture is not as high as on John's special conference terminal, but the picture is still clear enough.
+
+Step 2: John introduces the product to others, and shows the sample. Because the other twenty terminals could not display all the details of the product, John transfers some photos to show details more clearly.
+
+Step 3: The discussion begins after John has finished his introduction. The meeting is then split into four sub-conferences. All sub-conferences use voice control mode so the participants can speak freely and at the same time send text or graphics.
+
+Step 4: Fifteen minutes later, the discussion is finished. The four sub-conferences are combined into one conference. The majority of the participants agree that the initial requirement for the new product has been accomplished, and put forward some suggestions for what should be improved. However, engineer C considers that they should hear the suggestions of the marketing people. John, as the convener of the conference, then invites two marketing people named Aa and Bb to join the discussion. Aa and Bb accept the invitation.
+
+Step 5: Aa and Bb ask various questions and receive the relevant information. They put forward their suggestions on the marketing aspect and leave. John sums up all the suggestions and compiles a file. All participants modify this file with the file coordination function. John then makes plans for the next step according to the final file.
+
+Step 6: John announces the conference is over. After John leaves, the conference is terminated.
+
+### 7.1.3 Family chatting
+
+John goes back home after a full day work. He decides to call his parents to discuss the New Year holiday plan.
+
+Step 1: John initiates a videophone call to his parents. The call rate is not high considering the terminal's capability and cost. Although the image resolution is low, they can still see each other clearly. A small text window is visible below the video, for the real-time text component.
+
+Step 2: After exchanging conventional greetings, they begin to talk about the plan for the coming holiday. John's daughter Sasa calls John during their discussion. John tells Sasa that he is talking about their holiday plan with her grandparents, and Sasa asks to join in the discussion. Sasa joins the call after John's parents have agreed. Since Sasa is using a mobile terminal, she chooses to receive the call in the "voice only" mode.
+
+Step 3: John's father had a stroke a couple of years ago. It affected his speech. So, when he wants to contribute to the discussion, he types in the text area and the text appears nearly character-by-character on the participants' terminals. All appreciate sharing his experience of an earlier trip to China and his hints on the wonderful nature trips to be made in the Sichuan and Tibet areas.
+
+Step 4: The result to the New Year's plan discussion is that John's family will travel to China, and back to the house of their grandparents, the day before Christmas Day, for a party. John then invites his sister Lindy to join the conference call because she is in China on business. They have not seen each other for a long time, so John asks the system to change the picture mode. Sasa joins the conference with audiographics-only mode (audio plus still-image and graphics).
+
+Step 5: When they talk about the travel issue, Lindy announces that she has taken many photos in China. She then shows these pictures, together with text annotation, to the others. All the terminals display Lindy's photos. They continue their discussion based on these pictures. Finally, they decide that the destinations of the trip shall be Beijing and Tibet. John types a link to a travel information site where they can all get information to continue their planning after the call.
+
+Step 6: After the holiday arrangement is decided, John ends the family discussion.
+
+## 7.2 Multicast conference
+
+The following is an education scenario.
+
+In order to increase the whole corporation's ability to face increasing market competition, TTP's management department decides to give a market education seminar to the department managers. A famous marketing expert is responsible for the seminar. The expert is very busy so he makes a videodisc on the seminar. The organizer holds a multicasting meeting for the educational seminar.
+
+Step 1: Before the seminar begins, the educational organizer calls all the managers;
+
+Step 2: The organizer plays the videodisc. The audience, each located in his/her own office, receives the educational seminar;
+
+Step 3: The meeting is terminated after the videodisc is over.
+
+## 7.3 Mixed mode conference
+
+The following scenario is on a new product release situation.
+
+After the discussion on the TTP's new product, several modifications have been made. John who is responsible for the new product has decided it can be now released. Several means are used to release the new product. There are four target groups for the product release. The members of the first group are the relevant persons inside the company. Those from the second group are the major customers of the company. Those from the third group are the customers who registered by Internet after receiving advertisements of the product's release. Those from the fourth group are anonymous
+
+customers who watch the product release via Internet multicast. The first two classes of customers have full privileges to participate in the conference. The third class of customers can take the floor with the chairman's permission. The last class of customers can only observe, but they can leave messages on the bulletin board system.
+
+Step 1: Before the product is released, John calls all who comprise the first three classes of customers, and begins the broadcast through the Internet.
+
+Step 2: At the beginning, John shows and introduces the new product to everyone and makes a detailed presentation. During this procedure, John answers some questions from the second class of customers.
+
+Step 3: After the product presentation is completed, John answers questions from the third class of customers and replies to the messages on the bulletin board from the fourth class of customers.
+
+Step 4: The product release presentation is very successful. Both the major customers and the registered customers are satisfied with the product and the release presentation. A month later, John's colleague David retrieves and replays John's product release from the storage system and derives many good ideas for his own product release from it.
+
+# **8 Requirements of IP multimedia conference**
+
+## **8.1 User requirements**
+
+Basic requirements:
+
+- The user can initiate a multipoint conference on demand, or reserve a conference in several ways. For example, the user can reserve a conference or initiate an instant conference from the terminal, or login the conference management server and submit the conference information, or call the service provider operator;
+- Interactive audio, video and text in real-time, clear and smooth voice and video;
+- Users can access a multimedia conference from anywhere, if necessary;
+- Users can participate in the conference in different roles: convener (controller), chairman, participant, auditors and anonymous participants.
+
+Advanced requirements:
+
+- Users can request conference prolongation and conference termination ahead of the scheduled termination time during the conference;
+- Multi-subpictures can be displayed on the terminal's screen, and terminals can distribute multiple videos to display on several screens;
+- Terminals can join a multimedia conference with different codecs and different rates;
+- Data transfer function should be supported, e.g., document sharing, coordination, electronic white bulletin and slide demo etc., can be used;
+- Users can control remote terminals, such as the camera, microphone, etc.;
+- Conference can be multicast according to the controller's demand;
+- One conference can be split into several subconferences, and each subconference can be held as an individual conference under the control of the controller;
+- New participants can join or be invited into the ongoing conference, and each terminal may be disconnected from the conference at any time;
+- The means to participate in the conference and to handle the terminals and services can be provided to people with disabilities;
+- Users can retrieve and replay the archived conference.
+
+## 8.2 Application requirements
+
+Basic requirements:
+
+- Reserved conference and conference on-demand can be held automatically according to the user's requests;
+- Voice, video and text streams can be exchanged and processed, and QoS guarantee should be provided;
+- Various access methods are allowed, such as xDSL, Ethernet, WLAN, GSM, and 3G;
+- Different roles of the participants and different conference control modes are supported including voice control mode, chairman control mode, and text control mode, etc.
+
+Advanced requirements:
+
+- The system can schedule and manage conference resources automatically;
+- One or more streaming channels can be provided, and can be set up on demand;
+- The multimedia conference network can handle different codecs and different rates in one conference;
+- Remote device control should be supported;
+- Data transmission is supported, such as real-time text, document sharing, cooperation, bulletin board and slide demo;
+- The system can broadcast to one of the conference terminals according to the conference controller's request;
+- The system can support splitting a conference into several subconferences according to the conference controller's request;
+- The system can disconnect or invite terminals at any time, if necessary;
+- The conference can be archived, researched and reviewed.
+
+## 8.3 Numbering requirements
+
+To authorize a user, he/she should be assigned a unique identification number accompanied by other necessary information. The number should be used as the destination indication when the user is called, and as the identification for accounting. It should support the mobility of user terminals when necessary.
+
+## 8.4 Security requirements
+
+The security of a multimedia conference should be ensured: different security levels may be provided according to the user requirement. There are three classes of security:
+
+- a) user authentication and access security;
+- b) call security;
+- c) media stream encryption.
+
+When convening a conference with security, the following contents should be included:
+
+- 1) The convener should designate whether the meeting is security-supported or not when reserving a meeting, and the level of security should also be designated;
+- 2) For the conference on-demand, the security requirement and its level should also be submitted.
+
+## **8.5 Authentication and accounting requirements**
+
+The system should accept the authorized user's access to a multimedia conference network, and provide authorized application to the user.
+
+The system should not only collect and transfer accounting data of the multimedia conference service user accurately, but also provide multiple, alternative-accounting modes for different application scenarios.
+
+## **8.6 QoS requirements**
+
+Time delay, jitter and packets loss due to the IP network are the main effects to QoS. The network and terminal equipment for the multimedia conference service should be capable of real-time multimedia information processing, and of maintaining clarity and smoothness of the voice, moving picture and real-time text. The equipment should also be able to receive and process other data formats properly.
+
+# **9 Interworking and intercommunication**
+
+Three types of interworking or intercommunication may be related to the IP multimedia conference service:
+
+- interworking and intercommunication between terminals with different capabilities;
+- interworking and intercommunication between terminals in different networks (PSTN, ISDN, etc.);
+- interworking and intercommunication between different IP multimedia conference systems.
+
+## **9.1 Terminals with different capabilities**
+
+Terminals with different characteristics and capabilities may be connected in a multimedia conference. Three ways of interworking or intercommunication may then be provided:
+
+- use of a common mode which every terminal in the call can handle; this will decrease the quality and functionalities to those of the terminal with the lowest quality level for each media component; however, communication is always possible because all terminals have at least the basic audio capability;
+- use of their normal mode for the terminals supporting higher quality levels, with partial functionalities only for the terminals with lower quality levels, which are thus given a secondary status; for instance, some terminals may have audio and video while others may have audio capability only; it may also happen that terminals have different and incompatible data capabilities, and thus cannot be used;
+- transcoding and rate matching in the media exchange and process so that each terminal receives and transmits the signals it is able to handle.
+
+## **9.2 Terminals in different networks**
+
+The multimedia conference system should accept terminals in different networks (for example, visual telephone terminals over ISDN, visual telephone terminals over GSTN, Visual telephone terminals over mobile radio). That means that, when different terminals access, the multimedia system supports the network protocol translation. The requirements for this type of interoperation are:
+
+- audio format and code conversion;
+- video format and code conversion;
+- text format conversion;
+- data protocol conversion;
+
+- bit stream conversion;
+- call control signalling conversion.
+
+## **9.3 Different IP multimedia conference systems**
+
+There are many IP multimedia conference systems now available. Intercommunication is needed if the terminals are located in different service systems. The requirements for this type of intercommunication should support:
+
+- authentication between different systems;
+- system security;
+- shared system resources;
+- accounting between different 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           |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                             |
+| 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/F/T-REC-F.740-199308-I_PDF-E/raw.md b/marked/F/T-REC-F.740-199308-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..544b606063922910e25f25b3bcfaa99ce341e19e
--- /dev/null
+++ b/marked/F/T-REC-F.740-199308-I_PDF-E/raw.md
@@ -0,0 +1,406 @@
+
+
+![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
+
+**F.740**
+
+(08/93)
+
+**OPERATIONS AND QUALITY OF SERVICE  
+AUDIOVISUAL SERVICE**
+
+---
+
+**AUDIOVISUAL INTERACTIVE SERVICES**
+
+**ITU-T Recommendation F.740**
+
+(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 F.740 was prepared by ITU-T Study Group 1 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 31st of August 1993.
+
+---
+
+# NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+# CONTENTS
+
+|                                                          | <i>Page</i> |
+|----------------------------------------------------------|-------------|
+| 1 Introduction .....                                     | 1           |
+| 2 Definition of the AVI Service .....                    | 1           |
+| 3 Description of the AVI Service .....                   | 2           |
+| 3.1 AVI general aspects .....                            | 2           |
+| 3.2 The main roles .....                                 | 2           |
+| 3.3 Their functional needs .....                         | 2           |
+| 3.4 Terminal aspects .....                               | 4           |
+| 3.5 Terms and definitions .....                          | 4           |
+| 4 Procedures .....                                       | 5           |
+| 5 Charging principles .....                              | 5           |
+| 5.1 General .....                                        | 5           |
+| 5.2 Networks capabilities for charging .....             | 6           |
+| 6 Quality of service .....                               | 6           |
+| 6.1 Network optimization .....                           | 6           |
+| 6.2 Media quality .....                                  | 6           |
+| 6.3 Security .....                                       | 6           |
+| 7 Interworking and intercommunication requirements ..... | 6           |
+| Annex A – Examples of multimedia application.....        | 7           |
+
+
+
+# **AUDIOVISUAL INTERACTIVE SERVICES**
+
+*(Geneva, 1993)*
+
+The ITU-T,
+
+*considering*
+
+- (a) the existing (draft) documents on Audiovisual Interactive systems and protocols in SG 8;
+- (b) the state of the art of standardization of multimedia and hypermedia information in ISO;
+- (c) the need for handling audiovisual information of various types, namely text, graphics, still images and moving pictures on telecommunication networks;
+- (d) the need of having this audiovisual information shared by a various range of users supplying, managing or retrieving applications controlling it, and thus, using a wide and complex range of functions;
+- (e) that users are justified to demand an acceptable minimum quality of service;
+- (f) the current setting up of both pilot and operational AVI Services in the fields of education, marketing help, entertainment, etc.,
+
+*adopts*
+
+the subsequent Recommendation dealing with the General Description for Audiovisual Interactive Service (AVIS).
+
+# **1 Introduction**
+
+The purpose of this Recommendation is to define and describe, from the user's point of view, the general features and attributes of the AVI Service, regardless of the network environment where the service might be provided.
+
+# **2 Definition of the AVI Service**
+
+An AVI Service is a service which provides, through appropriate access by standardized procedures, users of terminals or workstations with information which consists of various input and output presentation elements, possibly combined, such as:
+
+- texts;
+- graphics;
+- pictures;
+- audio sequences;
+- video sequences.
+
+A range of functions may be supplied to the user such as:
+
+- simple retrieval;
+- interactive consultation;
+- re-arrangement of the assembling of elements;
+- modification of the elements themselves.
+
+The AVI Service also covers other service aspects related to the creation and management of the information.
+
+It is considered that the operation requires the participation of a number of organizations. The whole set of functionalities offered by the AVI Service is usually carried out via telecommunications networks.
+
+The AVI Service is essentially an asymmetrical service in which a single service provider is providing the service to several users. Additionally, rerouting from one service provider to another one may be offered.
+
+The users of an AVI Service may be equipped with an heterogeneous set of terminals or workstations.
+
+# 3 Description of the AVI Service
+
+### 3.1 AVI general aspects
+
+Several types of users will be allowed to access the AVI Service. Different rights should be given to them. As an example, an author will need to make use of enhanced functions given by his AVI terminal operating system and allowing him the access to remote systems when necessary via telecommunication networks whereas a simple retriever will remain more passive and simply need to consult the contents proposed by the AVI application.
+
+The information life cycle varies according to the type of application and can have different values on a scale from short to long.
+
+Three entities need to exchange information. Therefore, to set up an AVI application, telecommunications will be used.
+
+### 3.2 The main roles
+
+The AVI Service provides with facilities to fulfil the requirements of the users involved in creating, exchanging, modifying, managing and executing AVI applications.
+
+The users of the AVI Service may have several roles:
+
+- author;
+- information manager;
+- preparer;
+- retriever,
+
+dealing with the following families of functions:
+
+- editing functions;
+- information management functions;
+- execution and retrieval functions.
+
+According to the users' needs, various and numerous exchanges will be set up between systems or subsystems providing with the functions.
+
+An AVI Service can be illustrated as in the Figure:
+
+![Diagram of an AVI service architecture showing roles and functions.](e23c9577e177bf077bac8951a775dd90_img.jpg)
+
+The diagram illustrates the architecture of an AVI service. It features a central 'Information Management' block. Above this block is the 'Information Manager' role, connected by a vertical line. To the left is the 'Author' role, connected by a horizontal line. To the right are the 'Preparer' and 'Retriever' roles, also connected by horizontal lines. Inside the 'Information Management' block, there are three sub-functions: 'Editing', 'Execution', and 'Exchange'. 'Editing' and 'Execution' are at the bottom, connected by a horizontal double-headed arrow. 'Exchange' is at the top, with arrows pointing to it from both 'Editing' and 'Execution'. The entire diagram is enclosed in a grey rectangular background.
+
+Diagram of an AVI service architecture showing roles and functions.
+
+T0102510-92/d01
+
+FIGURE 1/F.740  
+An AVI service
+
+### 3.3 Their functional needs
+
+Each of the various roles has specific functional requirements with regards to the first three families of functions identified i.e. editing, information management, execution.
+
+As the respective locations of entities assuring roles and systems supplying functions may be distant, exchange functions should be activated as well.
+
+Table 1 hereafter, breaks down the needs of the four categories of roles according to the three families of functions.
+
+TABLE 1/F.740
+
+#### **Roles versus functional requirements**
+
+| Functions           |                                                                                                                                                                                                                                                                                                                  |                                                                                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                      |
+|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Roles               | Editing                                                                                                                                                                                                                                                                                                          | Information Management                                                                                                                                                                                                                                                                                                                         | Execution                                                                                                                                                                                            |
+| Author              | <ul style="list-style-type: none"> <li>– AVI creation or updating</li> <li>– Creation of the catalogue for AVIs already edited</li> <li>– Modification of AVIs already edited</li> <li>– Validation and transmission to information management system</li> <li>– Concatenation of AVIs already edited</li> </ul> | <ul style="list-style-type: none"> <li>– Management of edited AVIs and updates</li> <li>– Usage follow-up, trace processing</li> <li>– Statistics and payment</li> </ul>                                                                                                                                                                       | <ul style="list-style-type: none"> <li>– Debugging of AVIs</li> <li>– Experimentation using a sample user group</li> </ul>                                                                           |
+| Information Manager | <ul style="list-style-type: none"> <li>– Consultation of catalogues of AVIs already edited</li> <li>– Transmission to information management of AVIs already edited or their updates</li> </ul>                                                                                                                  | <ul style="list-style-type: none"> <li>– Creation and maintenance of catalogue for AVIs ready for management</li> <li>– Storage of AVIs and updates</li> <li>– Implementation of a pricing policy</li> <li>– Delivery management (profile verification)</li> <li>– Retriever and preparer management (access control, billing, ...)</li> </ul> | <ul style="list-style-type: none"> <li>– Collection of execution traces and recovery context</li> </ul>                                                                                              |
+| Preparer            |                                                                                                                                                                                                                                                                                                                  | <ul style="list-style-type: none"> <li>– Choice of AVIs already managed</li> <li>– Negotiation of configuration, parameters and installation on real supports as required</li> <li>– Sending of retriever usage follow-up</li> </ul>                                                                                                           | <ul style="list-style-type: none"> <li>– Reception and installation of AVIs and updates</li> <li>– Verification of correct installation</li> <li>– Collection of traces generated by AVIs</li> </ul> |
+| Retriever           |                                                                                                                                                                                                                                                                                                                  | <ul style="list-style-type: none"> <li>– Choice of AVIs already managed</li> <li>– Usage follow-up</li> <li>– Recovery management</li> </ul>                                                                                                                                                                                                   | <ul style="list-style-type: none"> <li>– Choice of AVIs already installed</li> <li>– Recovery management (Note)</li> <li>– AVI usage</li> </ul>                                                      |
+
+NOTE – A retriever may recover an AVI, later after its interruption, in the same context of usage.  
+Two concrete examples of AVI applications are given in Annex A.
+
+### 3.4 Terminal aspects
+
+Terminal equipment needs to provide with a set of functions such as:
+
+- display of text, graphics, still images preferably in colour and optionally moving images;
+- reproduction of sound;
+- acquisition of user interactions.
+
+All these functions should make use of appropriate standards defined or being defined in ISO IEC/JTC 1 and ITU-T.
+
+Terminals will be connected to appropriate networks by making use of interfaces and protocols defined in ITU-T.
+
+Terminals are equipped with a minimum set of items, namely a keypad, mouse, monitor and loudspeaker.
+
+### 3.5 Terms and definitions
+
+#### 3.5.1 Specific terminology
+
+For the purpose of this Recommendation, the following definitions apply:
+
+**role:** The role is either a person who activates, or a process which has been designed by a person in order to activate a functionality of an AVI application.
+
+**retriever:** The role who mainly consults the application by interacting with the presentation process.
+
+**preparer:** The role who mainly selects, installs, personalizes and concatenates the applications as well as following up their execution.
+
+**information manager:** The role who mainly defines or modifies user access authorization and tariffing, then provides the execution process with the applications to be executed or their updates.
+
+**author:** The role who mainly creates and validates applications or updates and supplies them to the information manager for their distribution.
+
+**editing:** Creation of applications, including design, use of media, development, verification, modification, updating and validation before the applications become available to the users.
+
+**information management:** Application management, including storage, classification, catalogue creation and management, retriever and preparer management, tariffication, monitoring usage processing, context recovery management, etc.
+
+**execution:** Application usage after installation, user interface management, monitoring usage implementation and, where appropriate, upstream connection with an information management system or directly with an editing system in case of an implementation in progress.
+
+**AVI application:** An AVI application is a dedicated use of the AVI Service to satisfy a particular requirement. An AVI application contains at least structural and presentation elements.
+
+The presentation elements are either input or output objects of various nature. They may be of monomedia, multimedia or hypermedia type.
+
+The execution of an AVI application consists in activating scriptware transferred as part of the application and forming its structural elements. These scriptware may perform, among others, the following functions:
+
+- references to and links between objects;
+- global control of events;
+- requests for traces;
+- check-points management for navigation and warm-state recovery;
+- invocation of external processes and data;
+- references to other scriptware;
+- response analysis.
+
+**AVI terminal:** The particular configuration of an AVI terminal will depend on the role which will use it. As an example, an author will make use of a scanner on his AVI terminal whereas a retriever will need to consult one or several contents by simply reproducing them on his AVI terminal.
+
+**update:** Part of an application which results from the comparison between a given version of an application with a previous one.
+
+#### 3.5.2 Terms and definitions shared with ISO IEC JTC 1/SC 29/WG 12-MHEG
+
+**multimedia (representation):** The property of handling several types of representation media.
+
+The term multimedia is an adjective, it must be used attached to a noun which helps defining the context; multimedia service or application, multimedia terminal, multimedia network, multimedia presentation.
+
+In the MHEG standard, multimedia is used in the sense of multiple representation media. "Multimedia" starts with two types of representation media in a piece of information and thus a remote processing service or videotex when using only a usual keyboard and a purely textual display cannot be said multimedia as involving only one type of medium (character or text type), although in both directions, to and from the user (the service is interactive, not multimedia).
+
+**hypermedia:** The ability to access monomedia and multimedia information by interaction with explicit links.
+
+*Example* – a set of linked photographic pictures with associated sound sequences showing the famous buildings in a given town together with different views of each building; the pictures and sounds will be accessed through navigation along the predefined links within the object.
+
+**object:** Coded representation of a finite independent self-defined piece of information that can be manipulated as a whole by applications and interchanged as one unit. The information can be of multiple different types: content, projector, basic, generic input, spatio-temporal composite, clock, conditional action set and null.
+
+NOTE – This definition is not restricted to digitally coded objects, there could also be analogue objects such as videodisc sequence.
+
+**script:** Specification of how one or more objects are to be presented to, or input from a user.
+
+**scriptware (script software):** Software that realizes a script, including both informative data and associated data about how the information is to be handled/presented.
+
+## 4 Procedures
+
+It is essential that the access to the service, from the user's point of view, should be offered via a common look-and-feel for any user on any kind of implementation of it.
+
+A guidance, taking the shape of a dialogue between the user and the system operating the application, will offer the user indications and controls information.
+
+## 5 Charging principles
+
+### 5.1 General
+
+Depending on the kind of applications offered by the service or the kind of users, namely author, information manager or retriever and general public or professional accessing it, various charging principles should have to be set up.
+
+As an example, a general public user accessing an application offered by the service via a public and unattended equipment should access this service free of charge, whereas an author should subscribe to a private subscribers group and additionally, pay for the retrieval of the available information.
+
+An essential requirement is that charging must correspond to the service offered taking into account the nature of both users and applications accessed by them.
+
+### **5.2 Networks capabilities for charging**
+
+This Recommendation does not cover detailed charging principles which are to be defined in other contexts.
+
+The network should be able to charge for the use of the service on the following basis:
+
+- no charging; or
+- pay per call; and/or
+- pay per duration; and/or
+- pay per volume of transmitted information; and/or
+- pay per item.
+
+A combination of these capabilities should be set up.
+
+## **6 Quality of service**
+
+### **6.1 Network optimization**
+
+According to the different application requirements, the service will make use of the most appropriate network configuration.
+
+### **6.2 Media quality**
+
+Different applications will have a wide range of media requirements. As the AVI Service definition is independent of any application, the AVI Service will cover a generic part of them.
+
+### **6.3 Security**
+
+An AVI Service should provide the information owners with a secured environment preventing users from illegal uses of exchanged information.
+
+Security aspects are of three categories:
+
+- protection from external violations during information exchanges;
+- protection of AVI applications against use of illegal copies;
+- protection of systems themselves against unauthorized use.
+
+## **7 Interworking and intercommunication requirements**
+
+As an AVI Service does not depend on a specific network, interworking requirements have not been taken into account.
+
+Intercommunication with user-to-machine (information-type) services:
+
+The AVI Service may have to intercommunicate with the videotex service in so far as this last one defines terminals operation and access to remote databases for information retrieval purposes.
+
+Intercommunication with user-to-user (conversational-type) services:
+
+Conversational services, namely videotelephony, videoconference and audiographic conference make use of real or non real-time data transfer onto users' terminals.
+
+This facility will be used to allow intercommunication between the AVI Service and so-called conversational ones.
+
+# **Annex A** (to Recommendation F.740)
+
+## **Examples of multimedia application** (This annex forms an integral part of this Recommendation)
+
+### **A.1 Introduction**
+
+The two following examples show that the AVI Service uses three important entities which have the same role although their respective names are different:
+
+- author, creator and education author;
+- information wholesaler and educational publisher;
+- information retailer and school system.
+
+The two examples explained in this annex do not intend to be exhaustive, but aim only at showing the need for modeling an AVI Service.
+
+### **A.2 Multimedia information booth application**
+
+![Diagram of the multimedia information booth application showing the flow from Creator to Information Wholesaler, then to Information Retailer, and finally to Information Consumer across four regions.](8e14350b4b669119a3bdfca7869110ca_img.jpg)
+
+The diagram illustrates the flow of information in a multimedia information booth application. At the top, the **INFORMATION WHOLESALER (Information Manager)** is represented by a box containing a cylinder icon. Below it, the **CREATOR (Author)** is shown with four categories: **SKIING** (Sound, video, ...), **SALES** (Still images, text), **ADVERTISING** (Graphics, text), and **NEWS** (Still images). An arrow points from the Creator to the Information Wholesaler. To the right, the **INFORMATION RETAILER (Preparer)** is shown with four regions: **Region 1**, **Region 2**, **Region 3**, and **Region 4**. An arrow points from the Information Wholesaler to the Information Retailer. Below the regions, the **INFORMATION CONSUMER (Retriever)** is shown with four boxes, each receiving an arrow from one of the regions. Below these boxes, the categories **NEWS**, **ADVERTISING**, **SALES**, and **SKIING** are listed. A dashed arrow points from the Creator to the Information Consumer. The text **T0102520-92/d02** is located at the bottom right of the diagram.
+
+Diagram of the multimedia information booth application showing the flow from Creator to Information Wholesaler, then to Information Retailer, and finally to Information Consumer across four regions.
+
+NOTE – Author, information manager, preparer and retriever refer to roles which comply to the description of the AVI Service made in clause 3.
+
+**FIGURE A.1/F.740**  
+**Multimedia information booth application**
+
+#### **A.2.1 General description of the usage**
+
+A multimedia information booth service will aim at providing multimedia booths spread throughout and installed in public areas with various kinds of update information such as news, hotel reservations, entertainment, etc. To achieve this, a full range of systems will be used going from the design to collection, distribution and retrieval of information.
+
+Three entities are included in the multimedia information booth service:
+
+- **Creator (or author)** – Building multimedia applications such as news, advertising, sales, skiing;
+- **Information wholesaler** – Storing the information and managing them;
+- **Information retailer** – Distributing at a regional level the information to consumers.
+
+#### **A.2.2 Characteristics of the multimedia information application**
+
+##### **A.2.2.1 Characteristics of a service access**
+
+It provides with multi applications for many publicly available multimedia workstations like text, graphics, audio sequences, video sequences, touch screen, etc. The service access is opened 24 hours per day. Its geographic distribution allows to reach consumers in several public places. A consumer may buy things like tickets and therefore, a booth may offer a possibility of paid service. Data access may be done either local or remote. Due to the type of information, the information life cycle is short or very short and there is a high frequency of updating. Retrieval sessions are short. Terminals are installed in public places for public use and consequently they must be robust. A consumer must use the service by himself, and unattended, therefore multilingual aspect improves the service. No skill is required to use this service.
+
+##### **A.2.2.2 Information wholesaler characteristics**
+
+He is a professional and commissions new works. He must be a manager and a wholesale dealer in information. He is in charge of maintaining information. He has a “legal responsibility”. A skill in database is required.
+
+##### **A.2.2.3 Author characteristics**
+
+He is a professional author with a skill level in design and may work on one or more topics. He works in an “office” environment.
+
+##### **A.2.2.4 Information retailer characteristics**
+
+He distributes information and therefore a skill in telecommunication is required for him.
+
+### **A.3 Educational application**
+
+#### **A.3.1 General description of the usage**
+
+An educational service is used by schools to acquire and, later on, to distribute educational courses to students and tutors. As in the previous example many entities will intervene in the service.
+
+The educational service is based on three entities:
+
+- education author creates different applications like geography, mathematics, zoology;
+- education publisher sends commissions to education author to create applications, stores and manages them;
+- school system distributes the different applications to the two types of users: student and tutor.
+
+![Diagram of Educational application architecture showing roles and data flow.](af7916c89a458fdab6c3f443217388ae_img.jpg)
+
+The diagram illustrates the flow of educational information. On the left, an **EDUCATIONAL AUTHOR (Author)** is shown with a box containing a cylinder icon. Below this box are three categories of content: **GEOGRAPHY** (Images, sound, graphics), **MATHEMATICS** (Text, graphics), and **ZOOLOGY** (Video, sound). An arrow points from the Author box to the **EDUCATIONAL PUBLISHER (Information Manager)** box at the top center. From the Publisher box, an arrow points to a stack of four boxes representing **SCHOOL SYSTEM (Preparer)**, labeled **School system 1**, **School system 2**, **School system 3**, and **School system 4**. A dashed arrow points from the Author's content categories to the School system 1 box. Below School system 1 are two boxes: **TUTOR (Retriever)** and **STUDENT (Retriever)**. Double-headed arrows connect both the Tutor and Student boxes to the School system 1 box. Below these boxes is a list of subjects: **ZOOLOGY**, **MATHEMATICS**, and **GEOGRAPHY**. A small code **T0102530-92/d03** is located near the Student box.
+
+Diagram of Educational application architecture showing roles and data flow.
+
+NOTE – Author, information manager, preparer and retriever refer to roles which comply to the description of the AVI Service made in clause 3.
+
+FIGURE A.2/F.740  
+**Educational application**
+
+#### A.3.2 Characteristics
+
+The two kind of users have some characteristics in common. Particularly, educational materials will be protected against illegal copy and utilization. Both users will see the same types of information: text, graphics, video sequences, audio sequences, etc.
+
+Some characteristics may be different. The tutor uses this system only at his office (during office hours) and students may use it during much more extended hours. The skill to use equipments will be medium for the tutor and basic for the student. The tutor will have a medium skill in using equipment because of his medium level workstation due to the different functionalities. Some tracks will be necessary to follow the student progress, and for the tutor course report (grades). Generally, sessions of use will be long. In case of interruption, it will be important to have a warm state recovery to start a new session at the same state when the user stopped. Other characteristics are involved for only the tutor. Information has a real-time aspect in case of on-line help. Because of the perennity of the educational material the information life cycle will be medium or long. A student may have to pay for this service. A student's terminal is composed of a low cost equipment because of its basic functionalities (only one single connection, may be remote execution...). This aspect is not critical for a tutor.
\ No newline at end of file
diff --git a/marked/F/T-REC-F.740.1-201911-I_PDF-E/raw.md b/marked/F/T-REC-F.740.1-201911-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..fae3ea21bbd1123ce8404f1476ed8e0b6a407c03
--- /dev/null
+++ b/marked/F/T-REC-F.740.1-201911-I_PDF-E/raw.md
@@ -0,0 +1,360 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.740.1**
+
+(11/2019)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Multimedia services
+
+---
+
+**Requirements for an information service of  
+objects in museums**
+
+Recommendation ITU-T F.740.1
+
+![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 F-SERIES RECOMMENDATIONS NON-TELEPHONE TELECOMMUNICATION SERVICES
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| MOBILE SERVICE                                                  |                    |
+| Mobile services and multdestination satellite services          | F.110–F.159        |
+| TELEMATIC SERVICES                                              |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400–F.499        |
+| DIRECTORY SERVICES                                              | F.500–F.549        |
+| DOCUMENT COMMUNICATION                                          |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600–F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700–F.799</b> |
+| ISDN SERVICES                                                   | F.800–F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850–F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.740.1
+
+## Requirements for an information service of objects in museums
+
+## Summary
+
+Recommendation ITU-T F.740.1 describes the requirements for an information service of objects in museums (ISOM). It also describes the scenarios for ISOM and the capabilities of key components of this information service, i.e., information collection unit, information storage unit, customized information presentation unit and information analysis unit. This information service can improve museum users' experience by collecting information about the exhibits and other related information from different parties and showing all the information in appropriate ways.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.740.1  | 2019-11-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/14101">11.1002/1000/14101</a> |
+
+## Keywords
+
+Information consumer, information provider, objects in museum.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                               | 1    |
+| 4 Abbreviations and acronyms .....                                          | 1    |
+| 5 Conventions .....                                                         | 1    |
+| 6 Overview.....                                                             | 1    |
+| 7 Scenarios for ISOM .....                                                  | 3    |
+| 7.1 Scenario 1: Visitors using multimedia devices .....                     | 3    |
+| 7.2 Scenario 2: Hearing impaired visitors with graphics/video devices ..... | 3    |
+| 7.3 Scenario 3: Visually impaired visitors with assistive devices.....      | 3    |
+| 8 Requirements for ISOM .....                                               | 3    |
+| 8.1 General requirements.....                                               | 3    |
+| 8.2 Requirements for information collection.....                            | 3    |
+| 8.3 Requirements for information storage.....                               | 4    |
+| 8.4 Requirements for customized information presentation.....               | 4    |
+| 8.5 Requirements for information analysis .....                             | 4    |
+| 9 Key components of ISOM .....                                              | 4    |
+| 9.1 Information collection unit .....                                       | 5    |
+| 9.2 Information storage unit .....                                          | 5    |
+| 9.3 Customized information presentation unit .....                          | 5    |
+| 9.4 Information analysis unit.....                                          | 5    |
+| 10 Security considerations .....                                            | 6    |
+| Bibliography.....                                                           | 7    |
+
+
+
+# **Recommendation ITU-T F.740.1**
+
+## **Requirements for an information service of objects in museums**
+
+# **1 Scope**
+
+This Recommendation describes requirements for an information service of objects in museums (ISOM). This Recommendation covers the following:
+
+- scenarios for ISOM
+- requirements of ISOM
+- key components and their functionalities.
+
+## **2 References**
+
+None.
+
+## **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:
+
+ISOM Information Service of Objects in Museums
+
+## **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**
+
+Traditionally, visiting a museum involves simply acquiring official information about the exhibited objects which is provided by the exhibitor using displayed text, graphics, animation, photos, sound and video. In fact, as shown in Figure 6-1, there might also exist other information generated and/or provided by other information providers. For example, researchers may discover some new findings related to the exhibited object. If the exhibited object is donated, the donator may have
+
+some stories about the object, such as, how he/she got it and why he/she decided to donate it. Even the visitors may have their own feelings and stories about the object, e.g., they may have seen another similar object in another place, to share with others [b-Nancy] [b-Angelina]. By gathering and presenting all these materials as a whole [b-Reinhard] [b-Chiayen] [b-Cesare], it is possible to form a museum community which breaks down the barriers between the museum's curators, researchers and visitors.
+
+![Diagram illustrating various sources of information about an exhibited object. A central image of a decorative square tile is surrounded by five contributors: Researcher (New findings), Museum (Official information), Donator (My stories), Visitor (My feelings), and Objects in museums. Arrows point from each contributor to the central object.](2ee59e629035d641140e55f4d215b0d7_img.jpg)
+
+The diagram shows a central image of a decorative square tile. Surrounding it are five contributors, each with an arrow pointing to the central object:
+
+- Researcher**: Associated with "New findings". The image shows a person working at a site.
+- Museum**: Associated with "Official information". The image shows a modern museum building.
+- Donator**: Associated with "My stories". The image shows hands holding a small red box.
+- Visitor**: Associated with "My feelings". The image shows a person taking a photo of an object.
+- Objects in museums**: A label with arrows pointing to the central object from the bottom.
+
+F.740.1(19)\_F6-1
+
+Diagram illustrating various sources of information about an exhibited object. A central image of a decorative square tile is surrounded by five contributors: Researcher (New findings), Museum (Official information), Donator (My stories), Visitor (My feelings), and Objects in museums. Arrows point from each contributor to the central object.
+
+**Figure 6-1 – Various sources of information about an exhibited object**
+
+In addition to the information about exhibits, there is also a lot of guidance information that can help information consumers, such as, visitors and researchers. For example, visitors should book the tickets and check transportation information before they go to the museum. When they arrive at the museum, they may have a better experience by following the recommended visiting route. It is also very useful to get information about the alarms, escape routes and emergency exits in case of emergencies such as fires or earthquakes. On the other hand, visitors may also like to provide feedback impressions about the exhibitions and the museum tour.
+
+For the visitors, it is useful to access all the information related to the exhibited objects and their visit to the museum. Visitors can use both their own multimedia devices and the public multimedia devices provided by the museum to access all this information. Considering there are many physically disabled visitors, the provided information should be adapted for ease of use. For example, the audio materials provided by the museum should be converted to text for hearing-impaired visitors. The video, text and graphics should also be converted to a form which is convenient for visually impaired visitors. Assistance information, such as barrier-free itineraries, should also be provided to impaired visitors.
+
+Above all, to improve their experiences, visitors need an information service of objects in museums (ISOM) which collects information about the exhibits and other related information from different parties and displays all this information in appropriate ways. The ISOM allows all related parties to contribute their knowledge, including adding, modifying and deleting related information. The ISOM provides an easier way to find information and exchange ideas among various parties. It can also be helpful before and after visiting the museum. This Recommendation presents the requirements of an information service of objects in museums as well as the key components and their functionalities.
+
+## **7 Scenarios for ISOM**
+
+### **7.1 Scenario 1: Visitors using multimedia devices**
+
+Visitors can use both their own multimedia devices and public multimedia devices provided by the museum to access the ISOM. The ISOM can be personalized to present a visitor with an experience customized to his/her specific interests, such as showing the information users are interested in based on users' locations. Before the visitors go to the museum, they can book the tickets, check travel routes and learn information about the exhibition provided by various entities through ISOM. When they arrive at the museum, in addition to information about the exhibited objects, visitors can also get information about the museum facilities, the itineraries which are recommended based on the visitors' interests, alarm information and escape routes and emergency exits in case of an emergency. They can also upload materials about the exhibition to ISOM (such as pictures, stories, impressions and reflections) and give feedback to the museum as well as to other visitors.
+
+### **7.2 Scenario 2: Hearing impaired visitors with graphics/video devices**
+
+The ISOM collects information from different parties. When hearing impaired visitors access the ISOM using their own devices or the public devices provided by the museum, the ISOM convert the audio part of the information to text and present it to them.
+
+### **7.3 Scenario 3: Visually impaired visitors with assistive devices**
+
+The ISOM collects information from different parties. When visually impaired visitors use their own devices or the public devices provided by the museum to access the ISOM, the ISOM converts the video, text and graphic materials to forms which can be displayed by the assistive devices such as refreshable braille displays and screen readers. The ISOM also provides visitors with information about barrier-free facilities and guides them on routes based on their location information.
+
+# **8 Requirements for ISOM**
+
+This clause presents the requirements for ISOM.
+
+### **8.1 General requirements**
+
+GEN-01: An ISOM is required to collect information about the exhibited objects.
+
+GEN-02: An ISOM is recommended to collect other related information, such as traffic, touring and weather information.
+
+GEN-03: An ISOM is required to store information collected from different parties.
+
+GEN-04: An ISOM is required to support customized information presentation.
+
+GEN-05: An ISOM is required to support information analysis.
+
+### **8.2 Requirements for information collection**
+
+IC-01: An ISOM is required to collect information about the objects-in-display in various formats, such as text, picture, audio and video.
+
+IC-02: An ISOM is required to provide methods to collect official information about exhibits from the museum.
+
+IC-03: An ISOM is required to support collecting information about visiting in the museum including barrier-free facilities, safety protection system, location system and monitoring system of the museum.
+
+IC-04: An ISOM is recommended to provide a method to collect information about other assistance information from third parties, such as the transportation suggestions for getting to the museum.
+
+IC-05: An ISOM is recommended to provide methods for visitors to contribute their own feedbacks about the exhibits, such as the photos taken by them, their stories about exhibits.
+
+IC-06: An ISOM is recommended to support collecting information about exhibited objects from third parties, such as archaeologists, artists and other researchers.
+
+### **8.3 Requirements for information storage**
+
+IS-01: An ISOM is required to store information about exhibited objects offered by different parties, such as the museum, visitors and researchers.
+
+IS-02: An ISOM is required to store other related information, such as facilities information provided by the museum and transportation information provided by the public transportation companies.
+
+IS-03: An ISOM is required to provide methods to manage information storage, such as creating, deleting and updating.
+
+### **8.4 Requirements for customized information presentation**
+
+IP-01: An ISOM is required to provide an interface for unified information accessing by visitors.
+
+IP-02: An ISOM is required to present information about exhibited objects and other related information requested by visitors.
+
+IP-03: An ISOM is required to provide information in the formats specified by visitors.
+
+IP-04: An ISOM is recommended to provide synthesized assistance information to visitors, such as visiting suggestions based on visitors' interests and their locations, and escape routes based on visitors' locations in case of an emergency.
+
+IP-05: An ISOM is required to provide an interface for visitors to access the services provided by the museum, such as booking tickets.
+
+IP-06: An ISOM is recommended to provide an interface to visitors to access the services provided by third parties, such as search engines.
+
+## **8.5 Requirements for information analysis**
+
+IA-01: An ISOM is required to analyse the feedbacks from visitors and provide the reports to the museum.
+
+IA-02: An ISOM can optionally provide the reports to third parties.
+
+# **9 Key components of ISOM**
+
+This clause describes the key components of ISOM. Figure 9-1 shows an example of the functional framework of an ISOM. An ISOM consists of five functional components: an information collection unit, an information storage unit, a customized information presentation unit and an information analysis unit. The ISOM collects information about exhibited objects and other related information from different parties, such as the museum, visitors and third parties, which is stored for further processing. The ISOM presents the information requested by the visitor and presents it in the format specified by the visitor. It can also provide analysis reports to the museum and third parties if applicable.
+
+![Figure 9-1 – Example functional framework of ISOM. The diagram shows a hierarchical functional structure. At the top, 'Third parties' (Info. on exhibit/exhibition, Service, Feedback) and 'Museum' (Safety protection system, Location system, Monitoring system, Facilities in the museum, Official info. on exhibit/exhibition, Booking system, Feedback) are connected via double-headed arrows to a central dashed box. Inside the dashed box, the 'Information collection unit' receives input from the Museum and sends it to the 'Information storage unit'. The 'Information storage unit' then feeds into the 'Customized information presentation unit' and the 'Information analysis unit'. The 'Information analysis unit' sends feedback to the 'Third parties'. At the bottom, the 'Information storage unit' is connected to a row of 'Terminal device' boxes: Multi-media device, Audio device, Graphics device, Video device, and Assistant device for disabled. The label 'F.740.1(19)_F9-1' is in the bottom right corner.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+Figure 9-1 – Example functional framework of ISOM. The diagram shows a hierarchical functional structure. At the top, 'Third parties' (Info. on exhibit/exhibition, Service, Feedback) and 'Museum' (Safety protection system, Location system, Monitoring system, Facilities in the museum, Official info. on exhibit/exhibition, Booking system, Feedback) are connected via double-headed arrows to a central dashed box. Inside the dashed box, the 'Information collection unit' receives input from the Museum and sends it to the 'Information storage unit'. The 'Information storage unit' then feeds into the 'Customized information presentation unit' and the 'Information analysis unit'. The 'Information analysis unit' sends feedback to the 'Third parties'. At the bottom, the 'Information storage unit' is connected to a row of 'Terminal device' boxes: Multi-media device, Audio device, Graphics device, Video device, and Assistant device for disabled. The label 'F.740.1(19)\_F9-1' is in the bottom right corner.
+
+**Figure 9-1 – Example functional framework of ISOM**
+
+### 9.1 Information collection unit
+
+The information collection unit is responsible for collecting information from museums, museum visitors as well as third parties. It collects official information about the exhibited objects from the museum, supplementary information about the objects from third parties such archaeologists, and user generated contents, including photos taken by visitors, their stories and feedbacks. It can also collect information about the facilities such barrier-free facilities of the museum and other assistance information from third parties, such as transportation suggestions to get to the museum.
+
+### 9.2 Information storage unit
+
+The information storage unit is responsible for storing the information gathered by the information collection unit, including information about exhibited objects offered by different parties, such as the museum, museum visitors and researchers, as well as other related information, such as facilities information provided by the museum and transportation information provided by the public transportation companies. It also provides methods to manage information storage, such as creating, deleting and updating.
+
+### 9.3 Customized information presentation unit
+
+The information presentation unit is responsible for providing an interface for unified information accessing by visitors. It presents the information requested by the visitor and presents it in the format specified by the visitor. It should convert the formats of data stored to the format appropriate for the visitors. For example, audio information should be converted to text for hearing impaired visitors. It can also provide synthesized assistance information to visitors, such as visit suggestions based on visitors' interests and their locations and escape route information based on visitors' locations in case of an emergency. It also provides interfaces to visitors to access the services provided by the museum such as booking tickets, and other services provided by third parties, such as search engine services.
+
+### 9.4 Information analysis unit
+
+The information analysis unit is responsible for analysing the feedbacks from visitors and other contents generated by visitors. Analysis reports will be generated according to the requirements of
+
+the museum. Such analysis reports can also be provided to the third parties wholly or partially as appropriate.
+
+## **10 Security considerations**
+
+It is recommended that ITU-T X-series, ITU-T Y-series and ITU-T M-series security Recommendations be taken into consideration. These include access control, authentication, data confidentiality, communications security, data integrity, availability and privacy.
+
+## Bibliography
+
+- [b-Angelina] Angelina R., Jerry W., Lynda K., Sebastian C. (2006), *How will social media affect museum communication?* In Proceedings of Nordic Digital Excellence in Museums (NODEM), Oslo, Norway.
+- [b-Cesare] Cesare R., Oliviero S., Massimo Z., Michael K., Antonio K. (2004), *The museum visit: generating seamless personalized presentations on multiple devices.* In Proceedings of the 9th international conference on Intelligent user interfaces. ACM.
+- [b-Chiayen] Chiayen C., Baorong C., Posen H. (2014), *Multimedia augmented reality information system for museum guidance.* Personal and ubiquitous computing 18.2: 315-322.
+- [b-Nancy] Nancy P. (2010), *Digital: Museum as platform, curator as champion, in the age of social media.* Curator: The Museum Journal 53.1: 35-43.
+- [b-Reinhard] Reinhard O., Marcus S. (1999), *A nomadic information system for adaptive exhibition guidance.* Archives and museum informatics 13.2: 127-138.
+
+
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.740.12-202512-I_PDF-E/raw.md b/marked/F/T-REC-F.740.12-202512-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..ca9f952f9766fe70ccce27684e906d5fd2275459
--- /dev/null
+++ b/marked/F/T-REC-F.740.12-202512-I_PDF-E/raw.md
@@ -0,0 +1,528 @@
+
+
+# Recommendation **ITU-T F.740.12 (12/2025)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+---
+
+## **Metadata for a cultural relics and artworks tracing system based on distributed ledger technology**
+
+![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 overlaid on the globe.
+
+ITU logo
+
+## ITU-T F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.740.12
+
+# Metadata for a cultural relics and artworks tracing system based on distributed ledger technology
+
+## Summary
+
+Recommendation ITU-T F.740.12 outlines the metadata framework for a cultural relics and artworks tracing system (CRATS) based on distributed ledger technology (DLT). CRATS aims to enhance the traceability, security and transparency of cultural relics and artworks (CRA) throughout their lifecycle. The framework consists of three core components: the universally recognized digital identity (URDI) component, the multidimensional description (MD) component, and the full lifecycle record (FLR) component. These components collectively support the recording of events throughout a CRA object's lifecycle, such as provenance tracking, inventory management, insurance management, market monitoring, etc., ensuring all associated data for CRA is archived in an immutable, timestamped evidence chain.
+
+This Recommendation is applicable to cultural institutions, digital platforms, and related entities engaged in the registration, management, or monitoring of cultural relics and artworks (CRA) using a distributed ledger technology (DLT) based tracing system.
+
+Implementation-specific details such as blockchain platform configuration, cryptographic algorithms, consensus mechanisms, or user-interface designs are outside the scope of this Recommendation.
+
+## History\*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.740.12 | 2025-12-14 | 21          | 11.1002/1000/16573 |
+
+## Keywords
+
+Artworks, cultural relics, cultural relics and artworks tracing system, distributed ledger technology, metadata.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <https://www.itu.int/ITU-T/ipr/>.
+
+© 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.....     | 2    |
+| 4 Abbreviations and acronyms .....                | 2    |
+| 5 Conventions .....                               | 2    |
+| 6 CRATS workflow .....                            | 2    |
+| 7 Metadata for CRATS.....                         | 5    |
+| 7.1 An overview of the metadata for CRATS .....   | 5    |
+| 7.2 Universally recognized digital identity ..... | 5    |
+| 7.3 Multidimensional description component .....  | 7    |
+| 7.4 Full lifecycle record.....                    | 9    |
+| Annex A – The main material of CRA .....          | 11   |
+| Annex B – Full lifecycle record type .....        | 16   |
+| Bibliography.....                                 | 19   |
+
+
+
+# Recommendation ITU-T F.740.12
+
+## Metadata for a cultural relics and artworks tracing system based on distributed ledger technology
+
+## 1 Scope
+
+This Recommendation is to define the metadata framework for cultural relics and artworks tracing system (CRATS). It specifies universally recognized digital identity (URDI), multidimensional description (MD), and the full lifecycle record (FLR) required to create a unique, immutable, and verifiable digital identity and a traceable lifecycle record for each cultural relics and artworks (CRA).
+
+The scope of this Recommendation includes:
+
+- 1) Cultural relics and artworks tracing system workflow.
+- 2) Metadata for a cultural relics and artworks tracing 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.
+
+- [ISO 639] ISO 639:2023, *Code for individual languages and language groups*.
+- [ISO 8601-1] ISO 8601-1:2019, *Date and time – Representations for information interchange – Part 1: Basic rules*.
+- [ISO 80000-1] ISO 80000-1:2022, *Quantities and units – Part 1: General*.
+- [ISO 80000-3] ISO 80000-3:2019, *Quantities and units – Part 3: Space and time*.
+- [ISO 80000-4] ISO 80000-4:2019, *Quantities and units – Part 4: Mechanics*.
+
+# 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+- 3.1.1 blockchain** [b-ITU-T F.751.0]: A type of distributed ledger that is composed of digitally recorded data arranged as a successively growing chain of blocks with each block cryptographically linked and hardened against tampering and revision.
+- 3.1.2 distributed ledger technology (DLT)** [b-ITU-T F.751.0]: Technology enabling large groups of nodes in distributed ledger networks to reach agreement and record information without the need for a central authority.
+- 3.1.3 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 cultural relics and artworks:** Tangible and movable objects of historical, artistic, archaeological or cultural value that represent human creativity or heritage.
+
+**3.2.2 full lifecycle record:** A tamper-evident metadata component that logs, timestamps and anchors all critical transactional events associated with an object of cultural relics and artworks throughout its existence.
+
+**3.2.3 market monitoring:** The continuous observation, analysis and recording of market activities related to cultural relics and artworks, such as auctions and private sales, to ensure transparency, and prevent fraud or manipulation.
+
+**3.2.4 multidimensional description:** Multidimensional description is culturally contextual information that enriches the universal digital identity of cultural relics and artworks by providing diverse interpretations and associations from various cultural perspectives.
+
+**3.2.5 provenance tracking:** The systematic documentation and verification of the chronological history of ownership, custody, location, condition, etc. of an object of cultural relics and artworks from its origin to the present.
+
+**3.2.6 universally recognized digital identity:** A standardized digital identifier for cultural relics and artworks, derived from immutable, objectively verifiable attributes (e.g., material composition, creation era, etc.).
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|       |                                             |
+|-------|---------------------------------------------|
+| CRA   | Cultural Relics and Artworks                |
+| CRATS | Cultural Relics and Artworks Tracing System |
+| DLT   | Distributed Ledger Technology               |
+| FLR   | Full Lifecycle Record                       |
+| MD    | Multidimensional Description                |
+| URDI  | Universally Recognized Digital Identity     |
+
+# 5 Conventions
+
+None.
+
+# 6 CRATS workflow
+
+The lack of a unified system and metadata standards for CRA data recording and tracking gives rise to difficulties in the cross-platform circulation and sharing of CRA information. Cultural relics and artworks tracing system (CRATS) is designed to meet the requirements for consistent digital management and traceability of CRA across institutions and systems, thereby supporting collaboration among museums, digital platforms and other cultural entities.
+
+CRATS uses a DLT-based system to provide secure, transparent and standardized management of a CRA object. Data for CRA is organized through a metadata framework, with participating institutions such as museums registering new artifacts by creating digital identities and uploading detailed descriptions. This Recommendation specifies the metadata applicable to CRA information circulating within the CRATS system. The CRATS system shall be implemented using distributed ledger technology (DLT) in order to take advantage of its technical characteristics, namely decentralization,
+
+immutability and transparency. These characteristics are intended to support the sharing and interoperability of data for CRA across different entities and platforms. Throughout each CRA object's lifecycle, any state changes, such as transfers or restorations, are recorded via registered user terminals, while observers can query but not alter records, ensuring oversight and data for CRA integrity. The system also manages personal and organizational profiles and every action, such as registration and update is immutably logged on the blockchain, making the entire history and status of each CRA object traceable, verifiable and protected against tampering.
+
+The system's workflow is shown in Figure 1.
+
+The workflow of the CRATS system comprises three primary roles: participants, CRATS and observers. Participants shall register through a user terminal by providing personal or organizational information. Upon registration, participants register CRA data for the purpose of generating digital identities and multidimensional descriptions of CRA. The recording of data changes for CRA within the system shall be managed through a metadata framework to maintain complete lifecycle records of CRA information. The CRATS entity is responsible for processing such information. Both participants and observers may submit queries of data for CRA to the CRATS system. The CRATS system shall process these queries and facilitate the transmission of CRA information accordingly. The overall process is implemented on the basis of distributed ledger technology (DLT), in order to ensure decentralization, immutability and transparency in data handling for CRA.
+
+![Figure 1 – CRATS workflow diagram showing interactions between Participant, CRATS, and Observer roles, supported by Distributed ledger technology.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+The diagram illustrates the CRATS workflow involving three main roles: Participant, CRATS, and Observer, supported by Distributed ledger technology (DLT).
+
+- Participant:**
+  - Registration:** Uses a "Registered user terminal" to send "User registration" to CRATS.
+  - State change:** Provides "CRA unstructured data" to CRATS for "CRA data registration" and "CRA data change recording".
+  - Query:** Sends a "User query" to CRATS, which responds with "CRA data query".
+- CRATS:**
+  - Manages "Personal/Organizational information" via "User login" from the Observer.
+  - Processes CRA data into three components: "Universally recognized digital identity", "Multidimensional description", and "Full lifecycle record".
+  - Handles "CRA data query" from the Observer and "User query" from the Participant.
+  - Facilitates "CRA information transmission" to the DLT layer.
+- Observer:**
+  - Performs "User login" to access CRATS.
+  - Sends "CRA data query" to CRATS and receives "User query" in response.
+- Distributed ledger technology (DLT):**
+  - Consists of three smart contracts: "Consensus-based digital identity management smart contract", "Multidimensional description component management smart contract", and "Full lifecycle record management smart contract".
+  - Receives "CRA information transmission" from CRATS.
+
+Figure 1 – CRATS workflow diagram showing interactions between Participant, CRATS, and Observer roles, supported by Distributed ledger technology.
+
+F.740.12(25)
+
+**Figure 1 – CRATS workflow**
+
+Figure 2 illustrates the workflow for registering data for CRA. In this workflow, a participant begins by registering their user information within the CRATS. Next, the participant submits a digital identity record for a CRA object, ensuring each object is uniquely identified on the blockchain. They then provide an MD record, detailing various attributes such as provenance, physical characteristics, historical context, etc. The current state information of the object, such as location, condition, or ownership, is also recorded. Finally, all submitted data for CRA and changes are committed to the blockchain as evidence records, creating an immutable and verifiable history for each CRA object.
+
+This process ensures that every step of registration is securely documented, traceable and protected against tampering.
+
+![Figure 2 – CRA data registration workflow diagram](f4fdd410cdb84df81274da55721e56fb_img.jpg)
+
+The diagram illustrates the CRA data registration workflow. It features two main components: a 'Participant' on the left, represented by a rounded rectangle, and 'CRATS' on the right, represented by a rectangle. Six horizontal arrows point from the Participant to CRATS, representing the following steps: 'Register user information', 'Submit CRA digital identity', 'Record multidimensional description', 'Record CRA state information', 'Commit evidence record', and a final unlabeled arrow. The label 'F.740.12(25)' is positioned at the bottom right of the diagram.
+
+Figure 2 – CRA data registration workflow diagram
+
+**Figure 2 – CRA data registration workflow**
+
+Figure 3 illustrates the workflow for recording changes in the data for CRA. In this workflow, a participant initiates updates to the records of a CRA object by submitting state changes to its digital identity, MD, or current state information. These updates may include modifications to ownership details, physical attributes, provenance, condition, location, etc. Once the changes are made, all updated information is committed to the blockchain as evidence records. This ensures that every alteration in the object's status is securely logged, creating an immutable and transparent history that supports traceability, accountability and protection against unauthorized modifications.
+
+![Figure 3 – CRA data change recording workflow diagram](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg)
+
+The diagram illustrates the CRA data change recording workflow. It features two main components: a 'Participant' on the left, represented by a rounded rectangle, and 'CRATS' on the right, represented by a rectangle. Five horizontal arrows point from the Participant to CRATS, representing the following steps: 'Change CRA digital identity', 'Change multidimensional description', 'Change CRA state information', 'Commit evidence record', and a final unlabeled arrow. The label 'F.740.12(25)' is positioned at the bottom right of the diagram.
+
+Figure 3 – CRA data change recording workflow diagram
+
+**Figure 3 – CRA data change recording workflow**
+
+Figure 4 illustrates the workflow for querying data for CRA. In this workflow, an observer interacts with the CRATS by submitting a query request to access information stored on the blockchain. Upon receiving the request, the system returns relevant data for CRA, including the digital identity, MD and current state information of a CRA object. This process allows observers, such as auditors, regulators, or researchers, to retrieve comprehensive and up-to-date records without altering any data for CRA, ensuring transparency, accountability and secure access to the verified information.
+
+![Figure 4 – CRA data query workflow diagram showing the interaction between an Observer and CRATS. The Observer sends a 'Submit query request' to CRATS. CRATS returns four pieces of information: 'Return CRA digital identity', 'Return multidimensional description', 'Return CRA state information', and 'F.740.12(25)'.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+```
+
+graph LR
+    Observer[Observer] -- "Submit query request" --> CRATS[CRATS]
+    CRATS -- "Return CRA digital identity" --> Observer
+    CRATS -- "Return multidimensional description" --> Observer
+    CRATS -- "Return CRA state information" --> Observer
+    CRATS -- "F.740.12(25)" --> Observer
+  
+```
+
+Figure 4 – CRA data query workflow diagram showing the interaction between an Observer and CRATS. The Observer sends a 'Submit query request' to CRATS. CRATS returns four pieces of information: 'Return CRA digital identity', 'Return multidimensional description', 'Return CRA state information', and 'F.740.12(25)'.
+
+Figure 4 – CRA data query workflow
+
+# 7 Metadata for CRATS
+
+## 7.1 An overview of the metadata for CRATS
+
+Metadata is fundamental to the effective tracing and management of CRA in a DLT-based system. It specifies the essential elements needed to uniquely identify, describe and monitor each object throughout its lifecycle, encompassing attributes such as provenance, physical characteristics, ownership history, condition assessments and exhibition records. By establishing authoritative and rigorous metadata standards, this chapter provides the foundation for transparent, verifiable and consistent documentation, facilitating secure information sharing and reliable traceability across institutions and platforms.
+
+## 7.2 Universally recognized digital identity
+
+A standardized digital identifier for CRA, derived from immutable, objectively verifiable attributes (e.g., material composition, creation era, etc.). This identity establishes a culture-agnostic foundation recognized across institutional and national boundaries, enabling tamper-proof authentication within CRATS.
+
+The elements of universally recognized digital identity (URDI) are given in Table 1.
+
+Table 1 – Elements of URDI
+
+| Element_name  | Data type | Description                                                                                                                                                               | Controlled vocabulary | Mandatory (M) or optional (O) |
+|---------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------------------|
+| object_id     | Integer   | The object_id represents the ID of the CRA object, long integer, unique and increasing, with a maximum length of 20.                                                      | No                    | M                             |
+| object_name   | String    | A string denoting the name of the CRA object.                                                                                                                             | No                    | M                             |
+| language_code | String    | It represents the language for the value of the artifact metadata field. It can be selected according to the language of the data source for CRA. Refer to the [ISO 639]. | Yes                   | M                             |
+| material      | String    | A string describing the main material forming the CRA object.                                                                                                             | Yes                   | M                             |
+
+**Table 1 – Elements of URDI**
+
+| <b>Element_name</b> | <b>Data type</b> | <b>Description</b>                                                                                                                                                          | <b>Controlled vocabulary</b> | <b>Mandatory (M) or optional (O)</b> |
+|---------------------|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--------------------------------------|
+|                     |                  | The value shall be taken from Table A.1 or may refer to an other_material_id in Table A.2 if no suitable material exists in Table A.1.                                      |                              |                                      |
+| techniques          | String           | A string listing any production or manufacturing skills and processes used in creating the CRA object.                                                                      | No                           | O                                    |
+| current_location    | String           | A string indicating the current physical location of the CRA object.                                                                                                        | No                           | M                                    |
+| creation_location   | String           | A string specifying the location where the CRA object was created or originated.                                                                                            | No                           | M                                    |
+| creator_name        | String           | A string that refers to the name or pseudonym of the person who created the CRA object.                                                                                     | No                           | O                                    |
+| object_description  | String           | A string providing detailed information on the physical and visual characteristics of the CRA object, as well as any identifying features.                                  | No                           | O                                    |
+| subject             | String           | A string describing the main theme or message conveyed by the CRA object, whether abstract or figurative, including the narrative or iconographic content.                  | No                           | O                                    |
+| dimension           | String           | A string representing the physical dimensions of the CRA object, expressed in accordance with the definitions and conventions specified in [ISO 80000-1] and [ISO 80000-3]. | Yes                          | M                                    |
+| mass                | String           | A string indicating the mass of the CRA object, expressed in accordance with the definitions and conventions specified in                                                   | Yes                          | M                                    |
+
+**Table 1 – Elements of URDI**
+
+| <b>Element_name</b>     | <b>Data type</b> | <b>Description</b>                                                                                                                                                                      | <b>Controlled vocabulary</b> | <b>Mandatory (M) or optional (O)</b> |
+|-------------------------|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--------------------------------------|
+|                         |                  | [ISO 80000-1] and [ISO 80000-4].                                                                                                                                                        |                              |                                      |
+| quantity                | Integer          | An integer specifying the number of objects in the CRA set or series.                                                                                                                   | No                           | M                                    |
+| created_time            | String           | A string representing the time or historical period associated with the creation of the CRA object, formatted according to [ISO 8601-1], and using the anno domini (AD) chronology.     | Yes                          | O                                    |
+| styles/groups/movements | String           | A string providing a description that links the CRA object to a specific style, historical period, group, school, or movement, based on the characteristics depicted in the CRA object. | No                           | O                                    |
+| inscriptions or marks   | String           | A string detailing any distinguishing physical marks, letters, texts, annotations, or labels affixed or applied to the CRA object.                                                      | No                           | O                                    |
+| current_condition       | String           | A string assessing the physical state, characteristics and completeness of the CRA object at a specific point in time.                                                                  | No                           | O                                    |
+
+## 7.3 Multidimensional description component
+
+Multidimensional description (MD) refers to the information that provides a comprehensive, contextual understanding of a CRA object from various cultural perspectives. This includes information about the object's attributes across different cultures, related objects and associated knowledge. These multidimensional data elements for CRA enrich the object's information by offering diverse interpretations, thus complementing the URDI. The MD provides a more complete representation of a CRA object within its broader cultural and historical context.
+
+The elements of MD are given in Table 2.
+
+**Table 2 – Elements of MD**
+
+| <b>Element_name</b>        | <b>Data type</b> | <b>Description</b>                                                                                                                                                             | <b>Controlled vocabulary</b> | <b>Mandatory (M) or optional (O)</b> |
+|----------------------------|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--------------------------------------|
+| object_id                  | Int              | Object_id represents the ID of the CRA object, long integer, unique and increasing, with a maximum length of 20.                                                               | No                           | M                                    |
+| language_code              | String           | It represents the language for the value of the artifact metadata field. It can be selected according to the language of the data source for CRA. Refer to [ISO 639] standard. | Yes                          | M                                    |
+| record_entity              | String           | A string identifying the entity that initiates the recording of information related to the CRA object on the blockchain.                                                       | No                           | M                                    |
+| record_time                | Datetime         | A datetime value indicating the exact time when the additional information about the CRA object was recorded.                                                                  | No                           | M                                    |
+| record_location            | String           | A string indicating the location of the entity that recorded the additional information about the artifact.                                                                    | No                           | M                                    |
+| record_purpose_description | String           | A string that provides a detailed explanation of the purpose or rationale behind recording the additional information.                                                         | No                           | M                                    |
+| additional_name            | String           | A string indicating names used across different cultures for the same CRA object.                                                                                              | No                           | O                                    |
+| additional_category        | String           | A string representing the category or classification assigned to the CRA object in different cultural contexts or systems.                                                     | No                           | O                                    |
+| additional_periods         | String           | A string denoting the historical periods associated with the CRA object, as used in                                                                                            | No                           | O                                    |
+
+**Table 2 – Elements of MD**
+
+| <b>Element_name</b>                | <b>Data type</b> | <b>Description</b>                                                                                                                                  | <b>Controlled vocabulary</b> | <b>Mandatory (M) or optional (O)</b> |
+|------------------------------------|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--------------------------------------|
+|                                    |                  | different cultural or historical contexts.                                                                                                          |                              |                                      |
+| additional_styles/groups/movements | String           | A string that describes the art styles, groups, or movements to which the CRA object is linked, as recognized in various cultural contexts.         | No                           | O                                    |
+| related_objects                    | String           | A string describing other CRA objects that are related to the one being described.                                                                  | No                           | O                                    |
+| cultural_context                   | String           | A string that provides information about the culture, nation, or country, or the cultural background in which the CRA object exists or was created. | No                           | O                                    |
+| related_knowledge                  | String           | A string that encompasses information about people, events, research, terminology and other relevant data associated with the CRA object.           | No                           | O                                    |
+
+Some metadata in the MD component can be mapped with the corresponding metadata in the URDI component, for example:
+
+- a) The MD field additional\_periods corresponds to the URDI field created\_time.
+- b) The MD field additional\_name corresponds to the URDI field object\_name.
+- c) The MD fields additional\_styles, additional\_groups and additional\_movements correspond to the URDI fields styles, groups and movements, respectively.
+
+## **7.4 Full lifecycle record**
+
+A tamper-evident metadata component that logs, timestamps and anchors all critical transactional events associated with a CRA object throughout its existence. This includes provenance tracking (creation, circulation, restoration, exhibition and other activities), inventory management, compliance, insurance management, market monitoring, etc. By converting these events into DLT-validated cryptographic proofs, full lifecycle record (FLR) establishes an immutable evidence chain that extends the CRA static identity with dynamic operational historicity.
+
+The elements of FLR are given in Table 3.
+
+**Table 3 – Elements of FLR**
+
+| <b>Element_name</b>     | <b>Data type</b> | <b>Description</b>                                                                                                                                                                                                                                                                          | <b>Controlled vocabulary</b> | <b>Mandatory (M) or optional (O)</b> |
+|-------------------------|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--------------------------------------|
+| object_id               | Int              | Object_id represents the ID of the CRA object, long integer, unique and increasing, with a maximum length of 20.                                                                                                                                                                            | No                           | M                                    |
+| object_owner            | String           | A string representing the individual or institution that holds the rights to possess and control the CRA object. This right is called ownership.                                                                                                                                            | No                           | M                                    |
+| object_holder           | String           | A string referring to the individual or institution that physically possesses or temporarily controls the CRA object. This entity may not necessarily hold ownership rights.                                                                                                                | No                           | M                                    |
+| relevant third party    | String           | A string identifying regulatory bodies, certification agencies, or entities involved in enforcing compliance, auditing transactions, or resolving disputes related to the CRA object.                                                                                                       | No                           | O                                    |
+| FLR_type                | String           | A string describing the type of FLR. The value is required to be selected from the sub-category code specified in Table B.1, which defines the FLR type classification within the CRATS framework, or from the other_FLR_id specified in Table B.2 if no suitable type exists in Table B.1. | Yes                          | M                                    |
+| record_data_location    | String           | A string representing the location where the event took place, such as the venue or institution hosting the event.                                                                                                                                                                          | No                           | M                                    |
+| record_data_date        | Date             | A date representing the specific time when an event in the full lifecycle of the CRA object occurred.                                                                                                                                                                                       | No                           | M                                    |
+| record_data_description | String           | A string providing a detailed description of the FLR. This may include provenance tracking, inventory management, compliance, insurance management, market monitoring, or other related information.                                                                                        | No                           | O                                    |
+
+## Annex A
+
+### The main material of CRA
+
+(This annex forms an integral part of this Recommendation.)
+
+Table A.1 specifies the classification of the main materials used in cultural relics and artworks (CRA). This classification defines a controlled vocabulary intended to ensure consistent representation of material types across different CRA objects. The categories include inorganic materials, organic materials, composite materials, digital works and an "other" category for unclassified or emerging materials. Each category is further subdivided into sub-categories to provide a more specific classification. The sub-category code is required to be used as the data value of the "material" element in Table 1 elements of URDI, in accordance with the controlled vocabulary defined in this Recommendation.
+
+**Table A.1 – Main material of CRA**
+
+| Category code | Category  | Sub-category code | Sub-category | Examples of CRA                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------|-----------|-------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>NOG</b>    | Inorganic | <b>NOG-01</b>     | Ceramics     | Ceramics encompasses earthenware and porcelain, formed by processing clay and other natural minerals through proportioning, crushing, shaping and high-temperature firing, resulting in a hard material. Among the CRA artifacts, there are ceramics such as: Tang Sancai pottery, Chinese porcelain, ancient Greek amphorae, Egyptian faience beads, Roman terra sigillata, Persian lusterware, Iznik ware, Meissen porcelain, etc.                       |
+| <b>NOG</b>    | Inorganic | <b>NOG-02</b>     | Glass        | Glass is an inorganic amorphous solid featuring a disordered atomic structure, formation via rapid melt cooling to avoid crystallization, and a reversible rigid-to-viscous transition at the glass transition temperature. Among the CRA artifacts, there are glasses such as: Egyptian faience, Roman glass vessels, Beijing glass, Islamic glass lamps, Venetian glass, Egyptian glass inlays, Byzantine glass mosaics, Baccarat, Lalique, Murano, etc. |
+| <b>NOG</b>    | Inorganic | <b>NOG-03</b>     | Metals       | Metals are crystalline materials with delocalized electrons that enable high electrical/thermal conductivity, malleability, ductility and characteristic luster. Among the CRA artifacts, there are metal works such as: Chinese bronze vessels, Greek bronze helmets, Roman silver coins,                                                                                                                                                                 |
+
+**Table A.1 – Main material of CRA**
+
+| <b>Category code</b> | <b>Category</b> | <b>Sub-category code</b> | <b>Sub-category</b> | <b>Examples of CRA</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|----------------------|-----------------|--------------------------|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                      |                 |                          |                     | African iron tools, Celtic shields, Indian gold jewellery, etc.                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>NOG</b>           | Inorganic       | <b>NOG-04</b>            | Minerals & pigments | Artifacts decorated with mineral-based pigments typically feature surfaces coloured through application of these ground minerals, as opposed to objects wholly sculpted from pigment material. The following typology categorizes key artifacts by function and cultural context: Lascaux cave in France, Altamira in Spain, aboriginal Australian art, Egyptian & Mesopotamian painted potteries, black-figure potteries from Greek & Roman, wall paintings and tomb paintings from China & Egypt, Chinese Tangka paintings, etc. |
+| <b>NOG</b>           | Inorganic       | <b>NOG-05</b>            | Plaster & mortar    | Plaster, a smooth paste applied as a protective or decorative coating to architectural surfaces (e.g., walls, ceilings), cures into a hard, durable layer. Mortar, in contrast, serves primarily as a binding agent for masonry. Key artifacts by function and cultural context: Plaster was integral to diverse cultural traditions, including Roman frescoes, Egyptian tomb paintings, Greek stucco reliefs, Chinese tomb murals, Islamic decorative plasterwork, Mesoamerican stucco murals, etc.                               |
+| <b>NOG</b>           | Inorganic       | <b>NOG-06</b>            | Stone               | Naturally occurring, inorganic solids with definite chemical composition and crystalline structure quartz, such as: Feldspar, Mica, Calcite, Diamond, etc. Among the CRA artifacts, there are stone works such as: Egyptian limestone statues, Greek marble sculptures, Roman stone inscriptions, Indian sandstone reliefs, Chinese jade carvings, Mayan stelae, etc.                                                                                                                                                              |
+| <b>NOG</b>           | Inorganic       | <b>NOG-07</b>            | Other inorganic     | This category covers inorganic materials not otherwise classified in the preceding sub-categories (e.g., ceramics, glass, metals, minerals & pigments, plaster & mortar, stone). It serves as a placeholder for materials of inorganic origin that do not clearly                                                                                                                                                                                                                                                                  |
+
+**Table A.1 – Main material of CRA**
+
+| <b>Category code</b> | <b>Category</b> | <b>Sub-category code</b> | <b>Sub-category</b>     | <b>Examples of CRA</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|----------------------|-----------------|--------------------------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                      |                 |                          |                         | fit existing types or represent newly identified material.                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>OG</b>            | Organic         | <b>OG-01</b>             | Plant materials         | Plant materials are materials derived directly from plants, encompassing both living and non-living matter, in natural or processed states, widely employed for the CRA objects, such as: Chinese calligraphy and Chinese painting, European illuminated manuscripts, Egyptian papyrus work, Indian palm leaf manuscripts, African woven baskets, etc.                                                                                                                                              |
+| <b>OG</b>            | Organic         | <b>OG-02</b>             | Animal-derived products | Animal-derived products are materials derived directly from non-human animals, encompassing raw or processed organic matter obtained from their bodies, utilized across scientific, artistic and historical domains. The CRA objects that have been handed down from history, such as: horn cups, parchment /vellum manuscripts, ivory carvings, etc.                                                                                                                                               |
+| <b>OG</b>            | Organic         | <b>OG-03</b>             | Other organic           | This category includes organic materials not covered by the previous sub-categories (e.g., plant or animal-derived products). It may encompass newly discovered or synthetic organic material derived from biological sources, or materials whose classification remains uncertain.                                                                                                                                                                                                                 |
+| <b>CP</b>            | Composite       | <b>CP-01</b>             | Multi-material          | In the context of cultural heritage and art conservation, multi-material refers to an artifact, artwork, or object intentionally crafted from two or more distinct materials (organic, inorganic, synthetic, or composite) that are integrated structurally, functionally, or decoratively. Among the CRA artefacts, such as Chinese lacquered wood with gold inlay, Indian ivory inlaid into wood furniture, Roman mosaic floors, Islamic metalwork with enamel, African beadwork on leather, etc. |
+| <b>CP</b>            | Composite       | <b>CP-02</b>             | Mixed media             | The term as a formal art classification emerged in the mid-20th century. It refers to artworks created by intentionally combining two or more                                                                                                                                                                                                                                                                                                                                                       |
+
+**Table A.1 – Main material of CRA**
+
+| <b>Category code</b> | <b>Category</b> | <b>Sub-category code</b> | <b>Sub-category</b> | <b>Examples of CRA</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|----------------------|-----------------|--------------------------|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                      |                 |                          |                     | distinct artistic mediums on a single support (e.g., canvas, paper, board), where the juxtaposition of materials becomes an essential aspect of the work's conceptual, textural, or aesthetic expression. Unlike traditional single-medium works (e.g., oil painting), mixed media embraces hybridity and material experimentation as central to its practice. This technique was employed by artists such as: Pablo Picasso, Georges Braque, Kurt Schwitters, Max Ernst, Robert Rauschenberg and many more.                                                                                                                                                                                              |
+| <b>CP</b>            | Composite       | <b>CP-03</b>             | Other composite     | This category encompasses composite or mixed material not defined in the previous sub-categories (e.g., multi-material, mixed media). It is intended to record hybrid compositions or structurally integrated material that exhibits composite characteristics but does not conform to established categories.                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>DG</b>            | Digital         | <b>DG-01</b>             | Digital works       | Digital art refers to artistic practices where computational technologies serve as the primary medium, tool, or conceptual framework for creation, display, or distribution. It is characterized by: binary logic: artworks generated, processed, or stored as digital data (0s/1s); algorithmic agency: use of code, algorithms, AI, or interactive systems; immateriality: existence as mutable data, distinct from physical artifacts. Among the CRA works, such as: Ben Laposky's work named "oscillons", works from JODI, Amiga paintings from Andy Warhol, etc. From the 2000s to the present, digital art has evolved through the democratization of AI/VR tools and the emergence of NFT markets. |
+| <b>DG</b>            | Digital         | <b>DG-02</b>             | Other digital works | This category refers to digital or computationally based CRA works that are not represented by the preceding sub-category (digital works). It covers emerging or                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+**Table A.1 – Main material of CRA**
+
+| <b>Category code</b> | <b>Category</b> | <b>Sub-category code</b> | <b>Sub-category</b>                | <b>Examples of CRA</b>                                                                                                                    |
+|----------------------|-----------------|--------------------------|------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|
+|                      |                 |                          |                                    | experimental forms of digital expression.                                                                                                 |
+| <b>OTH</b>           | Other           | <b>OTH-01</b>            | Unclassified or emerging materials | Materials that are not included in the above categories. When this category is selected, additional details may be recorded in Table A.2. |
+
+Table A.2 defines an open structure that allows the registration of additional materials not listed in Table A.1. Each record represents a material categorized under "other" in Table A.1 and is identified by a unique other\_material\_id.
+
+**Table A.2 – Other material of CRA**
+
+| <b>Element_name</b> | <b>Data type</b> | <b>Description</b>                                                                                                                                                                                        |
+|---------------------|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| other_material_id   | String           | A unique identifier is assigned to each additional material. The identifier shall follow the format "OM-XXXX", where "XXXX" represents a sequential alphanumeric code assigned by the registering system. |
+| other_material_name | String           | Free-text name of a material not represented in Table A.1 (the controlled vocabulary).                                                                                                                    |
+
+NOTE – Table A.2 provides flexibility for CRATS users to record new materials not listed in Table A.1.
+
+## Annex B
+
+### Full lifecycle record type
+
+(This annex forms an integral part of this Recommendation.)
+
+Table B.1 defines the classification of full lifecycle record (FLR) types applicable to CRA within the CRATS framework. This classification establishes a controlled vocabulary that enables consistent representation of lifecycle event types, including identity creation, physical state changes, knowledge and authentication updates, provenance and rights management, exhibitions and publications. Each category is further subdivided into sub-categories to provide a more specific classification. The sub-category code is required to be used as the data value of the "FLR type" element in Table 3 elements of FLR, in accordance with the controlled vocabulary defined in this Recommendation.
+
+**Table B.1 – FLR type**
+
+| Category code | Category              | Sub-category code | Sub-category                         | Description                                                                                                                                   |
+|---------------|-----------------------|-------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>IC</b>     | Identity creation     | <b>IC-01</b>      | Initial on-chain registration        | Captures the object's foundational digital record on-chain, including cryptographic hashes of key metadata, establishing its unique identity. |
+| <b>IC</b>     | Identity creation     | <b>IC-02</b>      | Digital twin association             | Documents the secure linkage between a physical object and its digital representation (token), using technical and physical evidence.         |
+| <b>IC</b>     | Identity creation     | <b>IC-03</b>      | Physical identifier assignment       | Records the assignment of a unique physical identifier (barcode, RFID, microchip, etc.) for traceability and authentication.                  |
+| <b>PC</b>     | Physical state change | <b>PC-01</b>      | Condition report update              | Logs any observed changes in the object's physical state, with timestamped documentation and report hash.                                     |
+| <b>PC</b>     | Physical state change | <b>PC-02</b>      | Restoration & conservation treatment | Details interventions for stabilization, restoration, or conservation, recording methods, materials and outcomes.                             |
+| <b>PC</b>     | Physical state change | <b>PC-03</b>      | Scientific analysis record           | Registers results of scientific analyses, providing hashes of reports and linking findings to the object's history.                           |
+
+**Table B.1 – FLR type**
+
+| <b>Category code</b> | <b>Category</b>            | <b>Sub-category code</b> | <b>Sub-category</b>                 | <b>Description</b>                                                                                                                 |
+|----------------------|----------------------------|--------------------------|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|
+| <b>PC</b>            | Physical state change      | <b>PC-04</b>             | Component change                    | Documents the addition, removal, or replacement of any separable or integral component, including reasons and responsible parties. |
+| <b>PC</b>            | Physical state change      | <b>PC-05</b>             | Relocation/movement record          | Tracks the movement or relocation of the object, including packing, transport and chain of custody.                                |
+| <b>PC</b>            | Physical state change      | <b>PC-06</b>             | Official declaration of destruction | Confirms the object's complete destruction, including supporting evidence.                                                         |
+| <b>KA</b>            | Knowledge & authentication | <b>KA-01</b>             | Change in attribution               | Updates the recognized creator, origin, or school based on new research or expert consensus.                                       |
+| <b>KA</b>            | Knowledge & authentication | <b>KA-02</b>             | Authenticity verification           | Records authoritative conclusions on authenticity, with certificate hashes stored on-chain.                                        |
+| <b>KA</b>            | Knowledge & authentication | <b>KA-03</b>             | Correction of dating                | Revises the estimated creation date based on new research or evidence.                                                             |
+| <b>KA</b>            | Knowledge & authentication | <b>KA-04</b>             | Historical context update           | Adds or updates information about the object's historical, cultural, or social significance.                                       |
+| <b>PR</b>            | Provenance & rights        | <b>PR-01</b>             | Transfer of ownership               | Documents every change in ownership, specifying the nature of transfer, to build a transparent provenance trail.                   |
+| <b>PR</b>            | Provenance & rights        | <b>PR-02</b>             | Loan & return                       | Records temporary transfers for exhibitions or research, detailing institutions, exhibition titles, periods and returns.           |
+| <b>PR</b>            | Provenance & rights        | <b>PR-03</b>             | Usage rights licensing              | Registers the granting or licensing of rights related to the object's image, reproduction, or commercial use.                      |
+
+**Table B.1 – FLR type**
+
+| <b>Category code</b> | <b>Category</b>          | <b>Sub-category code</b> | <b>Sub-category</b>                  | <b>Description</b>                                                                                                                        |
+|----------------------|--------------------------|--------------------------|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>PR</b>            | Provenance & rights      | <b>PR-04</b>             | Official declaration of loss/theft   | Records the formal declaration of loss or theft by the owner or authorities, enabling global alerts and recovery efforts.                 |
+| <b>PR</b>            | Provenance & rights      | <b>PR-05</b>             | Repatriation/restitution             | Records the return of the object to its country, community, or rightful owner as part of the restitution or settlement.                   |
+| <b>EP</b>            | Exhibition & publication | <b>EP-01</b>             | Exhibition history                   | Catalogues all public exhibitions featuring the object, including venues, dates, curators and themes.                                     |
+| <b>EP</b>            | Exhibition & publication | <b>EP-02</b>             | Publication record                   | Lists academic publications, catalogues, articles, or media where the object is featured.                                                 |
+| <b>EP</b>            | Exhibition & publication | <b>EP-03</b>             | Media appearance                     | Documents appearances in mass media, expanding the object's public reach and cultural impact.                                             |
+| <b>OTH</b>           | Other                    | <b>OTH-01</b>            | Unclassified or emerging event types | FLR types that are not included in the above categories. When this category is selected, additional details may be recorded in Table B.2. |
+
+Table B.2 defines an open structure that allows the registration of additional FLR types not listed in Table B.1. Each record represents a FLR type categorized under "other" in Table B.1 and is identified by a unique other\_FLR\_id.
+
+**Table B.2 – Other FLR type**
+
+| <b>Element_name</b> | <b>Data type</b> | <b>Description</b>                                                                                                                                                                                          |
+|---------------------|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| other_FLR_id        | String           | A unique identifier is assigned to each additional FLR type. The identifier shall follow the format "OFLR-XXXX", where "XXXX" represents a sequential alphanumeric code assigned by the registering system. |
+| other_FLR_type      | String           | Free-text name of an FLR type not represented in Table B.1 (the controlled vocabulary).                                                                                                                     |
+
+NOTE – Table B.2 provides flexibility for CRATS users to record new FLR types not listed in Table B.1.
+
+## Bibliography
+
+- [b-ITU-T F.751.0] Recommendation ITU-T F.751.0 (2020), *Requirements for distributed ledger systems.*
+- [b-ITU-T X.1255] Recommendation ITU-T X.1255 (2013), *Framework for discovery of identity management information.*
+
+
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.742-202503-I_PDF-E/raw.md b/marked/F/T-REC-F.742-202503-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..07731f07fdc37c332340b17f70a7264715522523
--- /dev/null
+++ b/marked/F/T-REC-F.742-202503-I_PDF-E/raw.md
@@ -0,0 +1,530 @@
+
+
+Recommendation
+
+**ITU-T F.742 (V2) (03/2025)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+---
+
+**Service description and requirements for  
+distance learning 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 globe with white latitude and longitude lines, and the letters 'ITU' in a bold, blue, sans-serif font overlaid on the globe.
+
+ITU logo
+
+# ITU-T F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.742 (V2)
+
+## Service description and requirements for distance learning services
+
+## Summary
+
+Recommendation ITU-T F.742 (V2) specifies the service description and requirements for distance learning services. Compared to the first edition (2005), this 2025 edition mainly includes the addition of "use cases and scenarios for distance learning service providers", and virtual reality, mixed reality and augmented reality equipment as learner tools. An overall revision is also done, and the content is restructured.
+
+## History \*
+
+| Edition | Recommendation   | Approval   | Study Group | Unique ID          |
+|---------|------------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.742      | 2005-09-13 | 16          | 11.1002/1000/8589  |
+| 2.0     | ITU-T F.742 (V2) | 2025-03-16 | 21          | 11.1002/1000/16250 |
+
+## Keywords
+
+Distance learning, personal learning material database, requirement, use case.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <https://www.itu.int/ITU-T/ipr/>.
+
+© 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 Reference .....                                                      | 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 .....                                                    | 2    |
+| 6 Overview.....                                                        | 3    |
+| 7 The reference model of distance learning services.....               | 3    |
+| 8 Use cases and scenarios for distance learning consumers .....        | 4    |
+| 8.1 Real-time interactive distance learning applications.....          | 4    |
+| 8.2 Real-time non-interactive distance learning applications.....      | 6    |
+| 8.3 No-real-time distance learning applications.....                   | 6    |
+| 9 Use cases and scenarios for distance learning service providers..... | 7    |
+| 9.1 Distance learning resources management applications .....          | 7    |
+| 9.2 Distance learning administration management applications .....     | 8    |
+| 10 Requirements .....                                                  | 8    |
+| 10.1 General requirements.....                                         | 8    |
+| 10.2 Requirements for consumers .....                                  | 9    |
+| 10.3 Account requirements.....                                         | 9    |
+| 10.4 Navigation-related requirements .....                             | 10   |
+| 10.5 Synchronization/display-related requirements .....                | 10   |
+| 10.6 Security authentication-related requirements .....                | 10   |
+| 10.7 Authority-related requirements .....                              | 10   |
+| 10.8 Accounting-related requirements .....                             | 10   |
+| 10.9 Quality of service (QoS)-related requirements.....                | 10   |
+| 11 Implementation notes.....                                           | 10   |
+| Bibliography.....                                                      | 11   |
+
+
+
+# Recommendation ITU-T F.742 (V2)
+
+## Service description and requirements for distance learning services
+
+## 1 Scope
+
+This Recommendation specifies the service description and requirements for distance learning services. It is intended to support the multimedia framework for distance learning services [b-ITU-T F.742.2].
+
+## 2 Reference
+
+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 audio-visual multicasting** [b-ITU-T F.741]: When users request the same content at the same time, the audio-visual on-demand services platform lists them in the same multicasting group. The system sends the requested content media streaming to that multicasting group address, then the users within the same group may receive the same requested content.
+
+**3.1.2 audio-visual on-demand** [b-ITU-T F.741]: A kind of network-delivered service that offers the functionality of the home VCR (as play only) without having to get a copy of the chosen material.
+
+**3.1.3 broadcast conference** [b-ITU-T H.323]: A broadcast conference is one in which there is one transmitter of media streams and many receivers. There is no bidirectional transmission of control or media streams. Such conferences may be implemented using network transport multicast facilities, if available.
+
+**3.1.4 broadcast panel conference** [b-ITU-T H.323]: A broadcast panel conference is a combination of a multipoint conference and a broadcast conference. In this conference, several terminals are engaged in a multipoint conference, while many other terminals are only receiving the media streams. There is bidirectional transmission between the terminals in the multipoint portion of the conference and no bidirectional transmission between them and the listening terminals.
+
+**3.1.5 videoconference service** [b-ITU-T F.700]: An audio-visual conference service providing bidirectional realtime-transfer of voice, motion video and real-time text between groups of users in two or more separate locations. Although the audio and motion video information are the essential part of the service, other types of information, such as high resolution still pictures or graphics may also be exchanged.
+
+### 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 distance learning services system (DLSS):** A collection of multimedia service systems with an integrated management system, an integrated authentication, authorization and accounting system to support a part or all kinds of distance learning services.
+
+**3.2.2 individual instruction:** A form of distance learning in which a teacher (or another learner) explains or answers the questions asked by a learner located at a different place through telecommunication networks.
+
+**3.2.3 multi-role learning/team learning:** Learners (of the collective learner entity) who operate as a team on different roles.
+
+**3.2.4 self-paced learning:** A form of distance learning in which learners find a solution to a question given by a teacher, or others, by searching information related to the question from learning resources, analysing the information and giving solutions to the question at their own pace, with or without the help of others.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                   |
+|------|-----------------------------------|
+| AI   | Artificial Intelligence           |
+| AR   | Augmented Reality                 |
+| DLSS | Distance Learning Services System |
+| DRM  | Digital Right Management          |
+| IP   | Internet Protocol                 |
+| MR   | Mixed Reality                     |
+| PC   | Personal Computer                 |
+| PDA  | Personal Digital Assistant        |
+| PPT  | Power Point Presentation          |
+| PSTN | Public Switched Telephone Network |
+| QoS  | Quality of Service                |
+| STU  | Set Top Unit                      |
+| TV   | Television                        |
+| VR   | Virtual Reality                   |
+
+## 5 Conventions
+
+In this Recommendation:
+
+The expression "is required" 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 which is not absolutely required. Thus, this requirement need not be present to claim conformance with this Recommendation.
+
+The expression "can optionally" and "may" 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 this Recommendation.
+
+## 6 Overview
+
+Distance learning involves interactive and non-interactive multimedia communications between learners and learning resources located at two or more separate locations. The aims of learners who use distance learning services may be to obtain some degree certificates based on the degree standards, to receive training given by employers, or to learn special knowledge independently. The distance learning services may be teacher-centred learning services that are similar to traditional physically face-to-face classroom learning, individual instruction, self-paced learning, multi-role learning/team learning, etc.
+
+In the course of distance learning, information may be required from remote databases containing the learning resources, or from live lectures. The material may be textual, aural, graphical, or video in nature and may be stored in a multimedia format. The information can be delivered in point-to-point, point-to-multipoint or multipoint-to-multipoint configuration.
+
+Participants in the distance learning may be located in classrooms equipped with related facilities, offices, homes or other places, such as on trains, where they are able to access a distance learning service system. Learners may learn in real-time with or without interaction with others, following a curriculum schedule or in non-real time by themselves on demand. The equipment that learners use may be a personal computer (PC); personal digital assistant (PDA); mobile phone; virtual reality (VR), mixed reality (MR), augmented reality (AR) equipment; or even a television (TV) set with set top unit (STU). Learners can change their equipment without interruption while they are learning, with the assistance of a distance learning services system (DLSS).
+
+## 7 The reference model of distance learning services
+
+The reference model of distance learning services is shown in Figure 7-1. It is composed of distance learning service providers (DLSS), and consumers/learners. Consumers/learners enrol in a course, a college or a university, acquire learning resources, attend in a virtual class, do and hand in homework, take an exam, etc. through DLSS, while learning service providers may use DLSS to manage, such as provide, create, modify, send or store, learning resources, and use DLSS to administrate, such as create virtual classrooms, arrange curriculum, and manage learning procedures, etc.
+
+The learning resources include live courses given by teachers (visual classes), the digital video recordings of live courses stored in DLSS, courseware produced by courseware creators based on the course materials given by teachers, digital knowledge (visual library, visual laboratory), digital news, etc. The networks which deliver the learning resources among teachers, learners, courseware creators, academic administrators and DLSS may be Internet protocol (IP)-based networks, satellite communication networks, mobile communication networks, public switched telephone network (PSTN), etc.
+
+![Figure 7-1: Reference model of distance learning services. The diagram shows a central rectangular box labeled 'Distance learning services system (DLSS)' connected by lines to two oval shapes on either side. The left oval is labeled 'Distance learning service providers' and the right oval is labeled 'Consumers/ Learners'. Below the diagram, the text 'F.742(V2)(25)' is visible.](0b87abe67b21a93777287649c33e755d_img.jpg)
+
+```
+graph LR; A([Distance learning service providers]) --- B[Distance learning services system (DLSS)]; B --- C([Consumers/ Learners]);
+```
+
+F.742(V2)(25)
+
+Figure 7-1: Reference model of distance learning services. The diagram shows a central rectangular box labeled 'Distance learning services system (DLSS)' connected by lines to two oval shapes on either side. The left oval is labeled 'Distance learning service providers' and the right oval is labeled 'Consumers/ Learners'. Below the diagram, the text 'F.742(V2)(25)' is visible.
+
+**Figure 7-1 – Reference model of distance learning services**
+
+This Recommendation focuses on the use cases and scenario descriptions of distance learning services and requirements for the distance learning service system. The descriptions of the network layer and access layer are outside the scope of this Recommendation.
+
+Teachers and learners both can both utilize the DLSS in the same way during real-time teacher-centred distance learning applications. They can both be consumers/learners of DLSS. In this case, the teacher and learners have similar requirements for the DLSS. This type of user can be defined as the consumer (including learners and teachers).
+
+The teachers, academic administrators or courseware creators deliver the digital form of educational materials and contribute to the distance learning resources. There are users of a DLSS who have the authorization to contribute and update the DLSS's distance resource database with new materials that both teachers and learners can access, such as syllabus design, course setting, course schedule, administration records and student grade records, etc. This type of user is to be defined as the distance learning service provider.
+
+## **8 Use cases and scenarios for distance learning consumers**
+
+### **8.1 Real-time interactive distance learning applications**
+
+#### **8.1.1 Case 1: real-time interactive teaching-centred distance learning**
+
+Real-time interactive teacher-centred distance learning applications are similar to the non-electronic, traditional physically face-to-face classroom education except that the teacher and learners are in different places.
+
+##### **Case implementation**
+
+- The visual classroom establishment
+
+The learners and the teacher receive the curriculum schedule in advance with the assistance of DLSS. Before the lecture begins, the teacher and the learners register to attend the lecture or course on the videoconference service system in DLSS. The videoconference service system sets up a multipoint videoconference environment between the teacher and learners located in two or more locations. If some learners who do not have interactive terminals want to attend the course by only watching the lecture, they can request to attend the lecture by joining the videoconference as receivers only. For them, the environment becomes a broadcast panel conference. Some learners may be students from abroad, from different provinces with different dialects, or unable to hear or understand the audio version of the language used by the teacher. They can request audio to be translated into text and/or appropriate audio in the language they want and have the translated text and/or audio synchronized with the speaker's video shown on their screens.
+
+- The teacher teaching while learners listening
+
+The teacher gives the lecture, and the learners receive the data in either one or other combination of video, audio or text in their respective locations. With the assistance of smart classrooms, in which the teacher gives the lecture, featuring a digital human, the learners may receive and see the teacher, who gives the lecture, in digital human form.
+
+- Question and answer
+
+If a learner in the virtual classroom wishes to ask a question, a request command can be sent to the teacher. If the teacher agrees to the learner's request, the teacher controls the system to let all the other learners see or listen to that particular learner asking the questions and see or hear the teacher's answer. The teacher can ask a learner a question and let the learner answer while the other learners can listen and see the learner and the teacher. After the teacher answers that learner's questions or the teacher wants to continue the lecture, the system can be controlled to return to the teacher-centred mode.
+
+- Learning materials showing
+
+If the teacher wants to show the learners certain material (in text, image, audio or video), the teacher may write it on a blackboard, hold up an image or obtain stored information from audio-visual on-demand service systems, or web-based service systems within the DLSS. At the same time, the learners may get the information from the teacher or obtain it directly from the same learning resources. Learners can see both the teacher and the information on one
+
+screen, or the information can be divided into separate boxes on the same screen, or two different screens could be utilized.
+
+- Quiz questions assignment and answer submission
+
+The teacher may assign quiz questions and allow the learners to submit their answers electronically within a specified period during the course. The teacher can assign different quiz questions to different learners. With the assistance of DLSS, learners can answer the questions by typing the answers on their terminals and then sending to the DLSS, or by answering the questions on papers then scanning and sending the answer sheets to the DLSS. The teacher can see all the learners' answers or see the answer results with the assistance of artificial intelligence (AI) system within the DLSS.
+
+- Course stop
+
+The teacher can stop the lecture, close the videoconference and disconnect the learners.
+
+#### **8.1.2 Case 2: real-time interactive individual instruction**
+
+Real-time interactive individual instruction is similar to traditional physically face-to-face individual instruction except that the person who asks the question and the answerer are located in different locations.
+
+##### **Case implementation**
+
+- Individual instruction between two persons
+
+The learner establishes a connection with the answerer using a videoconference service system within the DLSS. The learner asks the questions, and the answerer responds. If the learner and the answerer use different languages, the DLSS handles translation between them and provides text synchronized with the speaker's video on the screen. During this process, either party may obtain additional information from learning resources using an audio-visual on-demand service system or a web-based service system within the DLSS. The information they obtain may be in different languages, with or without text synchronized with the video. If both want to discuss a single document, they can optionally co-edit the document at the same time using co-editing tools provided by the DLSS. If they are not able to find a solution to the problem, they can invite others to join their discussion by setting up an ad hoc videoconference connection. In this case, it becomes a team learning case. After they finish the discussion, they close the connection(s).
+
+- Individual instruction between a learner and an intelligent machine
+
+For some Q&A cases, when a learner asks questions to the DLSS, the DLSS can optionally answer the learner in text, audio or video by intelligent machine with the assistance of AI.
+
+#### **8.1.3 Case 3: real-time interactive team learning**
+
+This case is similar to the case 1 in clause 8.1.2, except that the interactions are between a team of participants. In this case, a participant may have multiple roles. In other words, a participant's role may be that of an answerer at times, and that of a learner at other times. The communication environment is recommended to be an interactive conference service system, along with an audio-visual on-demand service system and/or a web-based service system within the DLSS. If the learners and the answerer use different languages, the DLSS handles translation between them and provides text synchronized with the speaker's video on the screens. If they want to discuss a single document, they can optionally co-edit one document simultaneously using co-editing tools or the data conference system provided by the DLSS.
+
+### 8.2 Real-time non-interactive distance learning applications
+
+Real-time non-interactive distance learning applications are a form of teacher-centred distance learning. In this situation, the learners and the teacher are located in different places, but the learners are unable to interact with the teacher during the course.
+
+#### Case implementation
+
+- The visual classroom establishment
+
+According to the curriculum schedule, the learners connect with the teacher and receive the course through a broadcast conference service system, or they have joined a broadcasting group to receive the course via an audio-visual multicasting service system. If the learners and the teacher use different languages, the DLSS handles translation between them and provides text synchronized with the speaker's video on the screens.
+
+- The teacher teaching and learning material showing
+
+The teacher teaches as in a traditional physically face-to-face classroom setting, except that there is no interaction between the learners and the teacher. During the course, the teacher may show the learners some information by writing it or retrieving it from learning resources stored in an audio-visual on-demand service system or a web-based service system. The information obtained may be in a different language, with or without text synchronized with the video.
+
+- Exiting course
+
+The teacher ends the course, and the learners are disconnected from the broadcasting videoconference service system and/or exit the broadcasting group of the audio-visual on-demand service system.
+
+### 8.3 No-real-time distance learning applications
+
+Non-real-time distance learning applications include asynchronous, teacher-centred distance learning, individual instruction, team learning, and self-paced learning applications.
+
+#### 8.3.1 Case 1: no-real-time teacher-centred distance learning
+
+When learners cannot attend a class according to the curriculum schedule for various reasons, they may obtain that course using an audio-visual on-demand service system within the DLSS at any time later, if it is stored in a learning resource of the DLSS. In this case, the learner cannot interact with the teacher in real time. However, the learner can submit questions to the web-based service system within the DLSS and receive answers later. The learner can send control commands, such as fast forward, reverse, pause and stop.
+
+##### Case implementation
+
+- Teacher-centred course recorded searching
+
+Learners who want to learn a specific course and have missed it search for the learning resource with the assistance of the navigation system (using of metadata) of an audio-visual on-demand service system within the DLSS. They can choose the language to be used, with or without text synchronized with the video, and can also choose to have sign language support.
+
+- Learner learning by watching streaming course information
+
+After the learner finds the course, the navigation system sends the address of the learning resource where the lecture is stored. The learner receives the multimedia course information and learns by watching the received information. While learning, the learner can send commands such as pause, forward, reverse and stop, on demand.
+
+- Exiting from learning
+
+The course ends, the learner exits the system.
+
+#### **8.3.2 Case 2: no-real-time individual instruction and team learning**
+
+When learners and teachers are not able to or do not want to engage in real-time individual instruction, they can use a bulletin board system (BBS) or e-mail systems for individual instruction and team learning.
+
+Students ask questions by sending them electronically to the teacher or another individual who answers later through the DLSS.
+
+#### **8.3.3 Case 3: no-real-time self-paced**
+
+When a person is seeking a solution to a particular problem or wishes to acquire some special knowledge, they can do so by using an audio-visual on-demand service system, or a web-based system of the DLSS.
+
+Learners can remotely search for learning material in video, still images, text, and audio that they are interested in from learning resource of the DLSS, on demand. Learners learn by watching the recorded materials they select. They can control the delivery (fast forward, reverse, pause and stop) of the content. They can also store the selected material in local storage for later review, if permitted. After finishing learning, learners exit the system.
+
+## **9 Use cases and scenarios for distance learning service providers**
+
+### **9.1 Distance learning resources management applications**
+
+#### **9.1.1 Case 1: distance learning resources creating**
+
+Courseware creators or teachers create courseware by recording live virtual classes, permitted with minor modification based on suggestions from the teachers who give the classes, and then send and store them in the learning resources of DLSS. Teachers or courseware creators make teaching/learning material, such as courseware used in virtual classes, homework used by learners, and teaching reference material (in slide show, file, audio, video, text, etc.) for use by teachers and learners with the assistance of tools within DLSS.
+
+##### **Case implementation**
+
+- A courseware creator accesses a live virtual course, and records the virtual course, permitted in advance, in audio or video during the virtual course. The courseware is processed, a name is added for the recording of the virtual course, and it is uploaded to a suitable place in the learning resource of DLSS.
+- Courseware creators or teachers create courseware, quiz questions, etc. (in slide show, file, video, text, etc.) to be used in classes using the tools provided by DLSS. Teachers upload reference materials (in slide show, files, video, text, etc.) to be used in classes to the learning resources of DLSS.
+
+#### **9.1.2 Case 2: electrical learning resource identification allocation**
+
+Courseware creators allocate identifiers for each learning resource.
+
+Learning resource manager makes the resource identity allocation and identity numbering rules of learning resources. The learning resource manager allocates identifiers to learning resources based on the rules.
+
+#### **9.1.3 Case 3: electrical learning resource navigation**
+
+Courseware creators make an electronic learning resource guide for users.
+
+The learning resource manager creates the presentation methods of learning resource guide to facilitate the users. Users can browse the learning materials by searching keywords or using the learning resource guide.
+
+#### **9.1.4 Case 4: personal learning material database providing**
+
+DLSS creates a customer's personal learning material database.
+
+The customer's historical learning materials, including but not limited to books, courseware learned, homework, etc., or recommends learning references such as reference books, related course guides, etc. based on the customer's interest or application, are collected with the assistance of AI system of DLSS.
+
+### **9.2 Distance learning administration management applications**
+
+#### **9.2.1 Case 1: customer management**
+
+Academic administrators manage teachers' names, subject, timetables, and learners' names, genders, classes and grades in school.
+
+Academic administrators create different user account for different kinds of users (teacher, learner, courseware creator), and assign different authorities to different users. Users fill in their own personal information on their account. Academic administrator manages user timetable, subject, and learning states, etc.
+
+#### **9.2.2 Case 2: curriculum developing**
+
+Academic administrators develop and modify the curriculum.
+
+An academic administrator develops curriculum and prepares different timetables for each learner based on the learner's choices, modifies and notifies the changes to the personal timetable through the DLSS.
+
+#### **9.2.3 Case 3: learner attendance logging**
+
+DLSS logs the customers' and distance learning providers' activities on DLSS, such as attending visual classes. Academic administrators or teachers check the learners who attend the virtual classes or access learning resources.
+
+DLSS takes charge of logging the applications of users, including accessing time, leaving time, accessing classes and learning resource. DLSS authorizes learners to browse their own learning log and authorizes teachers to browse their students' learning log.
+
+#### **9.2.4 Case 4: statistical tables creating**
+
+Academic administrators or teachers produce all kinds of statistical tables such as learner attendance, examination results, learner enrolment statistical tables.
+
+Academic administrators, teachers or learners request statistical tables, such as learner attendance, examination results. The DLSS returns the related statistical tables to the requesters.
+
+## **10 Requirements**
+
+### **10.1 General requirements**
+
+GR-01: A DLSS is required to consist of the functions of at least one of the four systems; a videoconference service system, an audio-visual on-demand- service system, a data conference service system and a web-based service system.
+
+GR-02: A DLSS is recommended to provide uniform authentication and authorization services to end-users and allow users to use related learning materials once they have passed authentication.
+
+GR-03: A DLSS is recommended to provide real-time and/or non-real-time distance learning services.
+
+GR-04: A DLSS is recommended to provide point-to-point, point-to-multipoint and multipoint-to-multipoint services.
+
+GR-05: A DLSS is recommended to provide AI assistance tools, such as courseware creation tools, file editing tools, and statistical table creating tools.
+
+### **10.2 Requirements for consumers**
+
+CR-01: A DLSS is recommended to provide various mechanisms to provide all forms of distance learning services on demand.
+
+CR-02: A DLSS is recommended to enable the provision of distance learning services to special groups of consumers, such as a closed user group of registered students of a university.
+
+CR-03: A DLSS is recommended to allow teachers/learners to access it by using different terminals such as PDA, PC, AR, MR, VR equipment, TV plus STU, and mobile phones.
+
+CR-04: A DLSS is recommended to allow learners to use distance learning services following curriculum schedules, or on demand.
+
+CR-05: A DLSS is recommended to allow learners to reuse learning materials: e.g., by storing learning materials locally, being able to replay them, or sharing them with others for discussion at a designated time.
+
+CR-06: A DLSS is recommended to allow learners to use two or more terminals to view a live lecture and other learning materials or to view a live lecture, other students and other learning materials on the same screen with synchronization.
+
+CR-07: A DLSS is recommended to allow teachers/learners to search curriculum schedules, learning materials and personal information, e.g., user's enrolment and course grade information.
+
+CR-08: A DLSS is recommended to allow teachers/learners to change their terminals while they receive services without obvious interruption of the services; for example, they can change their terminals from PCs to mobile phones.
+
+CR-09: A DLSS is recommended to allow teachers/learners to control non-real-time learning materials on demand, by means of fast forward, reverse, pause and stop.
+
+CR-10: A DLSS is recommended to allow listening-only learners to participate in interactive distance learning courses.
+
+CR-11: A DLSS is recommended to allow learners to pose questions and receive answers from an intelligent machine.
+
+CR-12: A DLSS is recommended to allow learners to choose if they want to use different languages, sign language and text synchronized with video with lip-reading requirements as stipulated in [b-ITU-T H Suppl.1].
+
+### **10.3 Account requirements**
+
+AR-01: A DLSS is recommended to assign a unique account to users and provide different permission controls to different users.
+
+AR-02: A DLSS is recommended to allow users to use a single account to conduct instant messages, group voice/video calls, live streaming, file exchanges and e-mailing across different organizations.
+
+### **10.4 Navigation-related requirements**
+
+NR-01: A DLSS is recommended to provide mechanisms to help users find learning materials or access course schedules.
+
+NR-02: A DLSS is recommended to provide the navigation information including the course name, and the languages which can be provided in audio and text synchronized with the video.
+
+### **10.5 Synchronization/display-related requirements**
+
+SYNR-01: A DLSS is recommended to provide synchronization/display mechanisms to synchronize several live videos or a live video with sign language, text synchronized with the live video, and pre-stored learning materials.
+
+### **10.6 Security authentication-related requirements**
+
+SECR-01: DLSS is recommended to provide security authentication to users, including consumers and distance learning service providers, using their unique identification names.
+
+### **10.7 Authority-related requirements**
+
+AUR-01: The DLSS is recommended to adopt some digital right management (DRM) methods to protect the copyrights of learning resources.
+
+AUR-02: The DLSS is recommended to provide mechanisms to ensure the security of user information and resources.
+
+### **10.8 Accounting-related requirements**
+
+ACR-01: The DLSS is recommended to provide different accounting policies, such as accounting for a closed user group, accounting based on usage duration, or accounting based on the number of courses accessed, based on the different types of applications.
+
+### **10.9 Quality of service (QoS)-related requirements**
+
+QR-01: The DLSS is recommended to provide video and audio information that are clear and free of perceptible asynchrony between audio and video and text.
+
+QR-02: The DLSS is recommended to ensure that text-based learning material displayed on terminals are clearly readable.
+
+QR-03: The DLSS is recommended to ensure that the display learning materials provided in video, audio, text, still image, and handwriting is synchronized on the consumer terminals.
+
+QR-04: The DLSS is recommended to respond to requests for learning material within reasonable time.
+
+## **11 Implementation notes**
+
+Distance learning applications are closely related to videoconferencing, audio-visual on-demand, IPTV and web-based applications, but differ in that their primary purpose is teaching and learning. The information involved relates to learning resources and learning records, and the participants are teachers and learners.
+
+## Bibliography
+
+- [b-[ITU-T F.700](#)] Recommendation ITU-T F.700 (2000), *Framework Recommendation for multimedia services*.
+- [b-[ITU-T F.741](#)] Recommendation ITU-T F.741 (2005), *Service description and requirements for audiovisual on-demand services*.
+- [b-[ITU-T F.742.2](#)] Recommendation ITU-T F.742.2 (2024), *Functional architecture for distance learning services*.
+- [b-[ITU-T H.323](#)] Recommendation ITU-T H.323 (V8) (2022), *Packet-based multimedia communications systems*.
+- [b-[ITU-T H Suppl.1](#)] H-series Recommendations – Supplement 1 (1999), *Application profile – Sign language and lip-reading real-time conversation using low bit-rate video communication*.
+- [b-IEEE 1484.1-2003] IEEE 1484.1-2003, *IEEE Standard for Learning Technology – Learning Technology Systems Architecture (LTSA)*.
+
+
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.742.1-202212-I_PDF-E/raw.md b/marked/F/T-REC-F.742.1-202212-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..317a531c24f4cbac8de590844d91166b7b20c491
--- /dev/null
+++ b/marked/F/T-REC-F.742.1-202212-I_PDF-E/raw.md
@@ -0,0 +1,509 @@
+
+
+# Recommendation **ITU-T F.742.1 (12/2022)**
+
+SERIES F: Non-telephone telecommunication services  
+Multimedia services
+
+## --- **Requirements for smart class systems based on artificial intelligence**
+
+![ITU logo](390120de4fe440c42fea8154fcaad334_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 F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| <b>TELEGRAPH SERVICE</b>                                        |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international teletext service                              | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| <b>MOBILE SERVICE</b>                                           |                    |
+| Mobile services and multdestination satellite services          | F.110–F.159        |
+| <b>TELEMATIC SERVICES</b>                                       |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| <b>MESSAGE HANDLING SERVICES</b>                                | F.400–F.499        |
+| <b>DIRECTORY SERVICES</b>                                       | F.500–F.549        |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | F.600–F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700–F.799</b> |
+| <b>ISDN SERVICES</b>                                            | F.800–F.849        |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | F.850–F.899        |
+| <b>ACCESSIBILITY AND HUMAN FACTORS</b>                          | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.742.1
+
+# Requirements for smart class systems based on artificial intelligence
+
+## Summary
+
+Recommendation ITU-T F.742.1 describes application scenarios and requirements for smart class system based on artificial intelligence, including application scenarios, service requirements, management requirements, and security considerations.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.742.1  | 2022-12-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/15184">11.1002/1000/15184</a> |
+
+## Keywords
+
+Artificial intelligence, education, smart class system.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 of smart class systems based on artificial intelligence .....                | 2  |
+| 7   | Typical application scenarios of smart class systems .....                            | 3  |
+| 7.1 | Intelligent study preparation pre-class .....                                         | 4  |
+| 7.2 | Intelligent lecture preparation pre-class .....                                       | 4  |
+| 7.3 | Learning aid during the class stage .....                                             | 4  |
+| 7.4 | Portrait of learning status in class.....                                             | 4  |
+| 7.5 | Teaching effect analysis after class .....                                            | 5  |
+| 7.6 | Learning effect analysis after class .....                                            | 5  |
+| 8   | Service requirements of smart class systems based on artificial intelligence .....    | 5  |
+| 8.1 | Requirements for class interaction .....                                              | 6  |
+| 8.2 | Requirements for objective analysis.....                                              | 6  |
+| 8.3 | Requirements for intelligent push of course resources .....                           | 7  |
+| 8.4 | Requirements for display of teaching and learning results .....                       | 7  |
+| 8.5 | Requirements for resource generation.....                                             | 7  |
+| 8.6 | Requirements for auxiliary tools .....                                                | 9  |
+| 9   | Management requirements of smart class systems based on artificial intelligence ..... | 9  |
+| 10  | Security considerations .....                                                         | 10 |
+|     | Appendix I – A reference architecture for smart class systems .....                   | 11 |
+|     | Bibliography .....                                                                    | 12 |
+
+
+
+# Recommendation ITU-T F.742.1
+
+# Requirements for smart class systems based on artificial intelligence
+
+## 1 Scope
+
+This Recommendation specifies requirements for smart class systems (SCSs) based on artificial intelligence (AI), which specifically describe the scenarios and requirements.
+
+The scope of this Recommendation includes:
+
+- typical application scenarios;
+- service requirements;
+- management requirements;
+- security considerations.
+
+# 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 context** [b-ITU-T Y.2002]: The information that can be used to characterize the environment of a user.
+
+NOTE – Context information may include where the user is, what resources (devices, access points, noise level, bandwidth, etc.,) are near the user, at what time the user is moving, the interaction history between person and objects, etc. According to specific applications, context information can be updated.
+
+**3.1.2 device** [b-ITU-T Y.4000]: With regard to the Internet of things, this is a piece of equipment with the mandatory capabilities of communication and the optional capabilities of sensing, actuation, data capture, data storage and data processing.
+
+**3.1.3 machine learning (ML)** [b-ITU-T Y.3172]: Processes that enable computational systems to understand data and gain knowledge from it without necessarily being explicitly programmed.
+
+**3.1.4 machine learning model** [b-ITU-T Y.3172]: Model created by applying machine learning techniques to data to learn from.
+
+NOTE 1 – A machine learning model is used to generate predictions (e.g., regression, classification, clustering) on new (untrained) data.
+
+NOTE 2 – A machine learning model may be encapsulated in a deployable fashion in the form of a software (e.g., virtual machine, container) or the hardware component (e.g., IoT device).
+
+NOTE 3 – Machine learning techniques include learning algorithms (e.g., learning the function that maps input data attributes to output data).
+
+**3.1.5 machine learning database** [b-ITU-T Y.3174]: A component which stores data related to machine learning in the machine learning overlay.
+
+**3.1.6 speech to text** [b-ITU-T H.862.3]: The process of converting speech input into digital text.
+
+**3.1.7 text to speech** [b-ITU-T H.862.3]: The process of converting digital text input into speech.
+
+## **3.2 Terms defined in this Recommendation**
+
+This Recommendation defines the following term:
+
+**3.2.1 smart class system (SCS)**: A system including hardware and software that is used to: aid instruction; manage hardware, software and data resources of teaching and learning devices; and analyse teaching effectiveness.
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|          |                                              |
+|----------|----------------------------------------------|
+| AI       | Artificial Intelligence                      |
+| AR       | Augmented Reality                            |
+| IMT-2020 | International Mobile Telecommunications-2020 |
+| IoT      | Internet of Things                           |
+| ML       | Machine Learning                             |
+| MR       | Mixed Reality                                |
+| SCS      | Smart Class System                           |
+| STT      | Speech to Text                               |
+| TTS      | Text to Speech                               |
+| TV       | Television                                   |
+| VR       | Virtual Reality                              |
+
+# **5 Conventions**
+
+The following conventions are used in this Recommendation:
+
+- The phrase "**is required to**" indicates a requirement that must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed.
+- The phrase "**is recommended to**" indicates a requirement that is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance.
+- The phrase "**can optionally**" indicates a 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 or service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification.
+
+# **6 Overview of smart class systems based on artificial intelligence**
+
+With the application of multimedia and information and communication technologies to traditional methods, the effect and quality of teaching has been improved, but it still faces some problems.
+
+- Existing methods for checking attendance are difficult to meet the actual needs of its management, while occupying class time and affecting teaching efficiency. There is a need for high accuracy and efficient methods for checking attendance to assist class management.
+
+- Low efficiency of teacher lecture preparations. In the traditional way, teachers and students do not interact. Teachers prepare lectures according to syllabus, and students follow textbooks before class. This leads to teachers not being able to know whether students have prepared well. It is also difficult for teachers to gain insight into the weaknesses of student preparations and to carry out targeted educational activities.
+- Cramming method of teaching. In the traditional teaching model, knowledge is taught by teachers through blackboards or multimedia devices and students listen passively during class.
+- Low efficiency of absorption. The information that is shared by teachers through blackboards or multimedia devices is passively received by students during the class. There is a lack of interaction between teachers and students. This force-feeding method cannot stimulate student initiative and creativity.
+- Inefficient analysis of teaching effectiveness. Teachers cannot know what students have captured and retained after class immediately. It is also difficult for teachers to check the study progress of each student in real time.
+- Outdated teaching equipment. Auxiliary teaching equipment plays an important role in class. As time goes by, much teaching equipment cannot keep up with the changing needs of AI.
+
+Therefore, there are still many educational activities that need to be improved. In the era of AI, its integration, along with big data technology, into education has been strengthened. AI, which is at the cutting edge of innovation, is considered as an effective way to help human solve problems. By utilizing advanced teaching equipment, and collecting, and analysing educational data, AI can assist teachers or students in enhancing lecture preparation, as well as improving both methods and effectiveness of teaching at each stage of the class.
+
+SCS is designed to improve lecture preparation, enhance interaction between teachers and students and promote teaching quality. Based on AI technology, SCS is an efficient way to reduce the teaching workload, provide a vivid learning environment, develop teaching abilities and performance of teachers and cultivate individual learning styles of students.
+
+SCS is an intelligent system based on AI, big data, cloud computing, Internet of things (IoT) and other intelligent information technologies and helps construct an intelligent teaching and learning service environment, providing resource services, interactive services and teaching tools.
+
+# 7 Typical application scenarios of smart class systems
+
+SCS promotes the transformation from learning knowledge to generating wisdom by creating a student-centred intelligent learning environment and developing intelligent teaching applications. Firstly, based on the intelligent environment, the intelligent application endows the teaching and learning data with educational significance and becomes valuable teaching and learning information through the collection, aggregation, mining and analysis of teaching and learning data. Through collaborative cognition and processing, the information about teaching and learning is transformed into teaching and learning knowledge. Teaching and learning knowledge can then be flexibly applied in teaching and learning activities, and gradually improve the teaching quality of teachers and the learning quality of students. Finally, promote the development of smart classes dominated by data intelligence and AI.
+
+SCS introduces technology into classes, turns the traditional class into one that is information based, interactive, and meets the students' interest points and personality needs. SCS starts from smart learning and smart teaching at the same time to achieve pre-class preparation, in-class learning and after-class consolidation and promotion. The application scenarios of teaching and learning processes based on SCS can be found in Figure 7-1.
+
+![Figure 7-1: Application scenarios of teaching and learning process based on smart class systems. The diagram shows a central circle labeled 'SCS' surrounded by three concentric rings: 'Learning' (inner), 'Teaching' (middle), and 'Pre-class', 'In-class', and 'After-class' (outer). Six application scenarios are shown in circles around the outer ring, connected by dashed arrows: 'Intelligent study preparation' (Pre-class), 'Intelligent lecture preparation' (Pre-class), 'Learning aid in class' (In-class), 'Portrait of learning status' (In-class), 'Teaching effect analysis' (After-class), and 'Learning effect analysis' (After-class). A small label 'F.742.1(22)' is at the bottom right.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg)
+
+Figure 7-1: Application scenarios of teaching and learning process based on smart class systems. The diagram shows a central circle labeled 'SCS' surrounded by three concentric rings: 'Learning' (inner), 'Teaching' (middle), and 'Pre-class', 'In-class', and 'After-class' (outer). Six application scenarios are shown in circles around the outer ring, connected by dashed arrows: 'Intelligent study preparation' (Pre-class), 'Intelligent lecture preparation' (Pre-class), 'Learning aid in class' (In-class), 'Portrait of learning status' (In-class), 'Teaching effect analysis' (After-class), and 'Learning effect analysis' (After-class). A small label 'F.742.1(22)' is at the bottom right.
+
+**Figure 7-1 – Application scenarios of teaching and learning process based on smart class systems**
+
+## 7.1 Intelligent study preparation pre-class
+
+SCS provides some contents and tasks that students can learn independently before class and push the resource to students to provide them with space for independent thinking. For example, providing attractive resources, videos and pictures for study courses can stimulate student interest in learning. At the same time, SCS can send pre-class questions to students, and the system will automatically generate data analysis reports based on student learning status. SCS can accurately analyse student learning and recommend relevant consolidation exercises to students based on analysis results, thereby developing teaching strategies.
+
+## 7.2 Intelligent lecture preparation pre-class
+
+SCS intelligently analyses the feedback of student preparation for class and help teachers identify the weaknesses within it, so that teachers can organize teaching centred on student learning. SCS can use the knowledge map to assist teachers to complete the preparation. The system can recommend the same type of information, such as the lesson plan, course explanation and homework, to improve the teaching efficiency of the teacher. The map-based search can also return the desired content more accurately.
+
+## 7.3 Learning aid during the class stage
+
+With the help of SCS, teachers can present vivid and attractive cartoons of knowledge, e.g., physics experiment, chemical change, biological growth. Students can also use optical character recognition technology to extract text information. Furthermore, these text materials are collated into electronic notes by mobile phone or other intelligent terminal devices.
+
+Based on network communication devices, holographic projection technology, as well as light and sound technology, SCS combines real scenes and virtual backgrounds for teaching. An SCS can provide real-time display, lossless transmission of teaching processes, and enable interaction between teachers and students on the same screen when they are in different places.
+
+SCS can help achieve management of teaching resources. When students or teachers are limited by location or time, teachers and students can watch and discuss the courses through SCS.
+
+## 7.4 Portrait of learning status in class
+
+SCS can analyse individual differences among students, e.g., their ability and style of learning, and help improve their abilities depending on student gender, age, grade, habits, etc., and design
+
+personalized learning methods to improve their ability. SCS can also predict student' performance through historical learning data.
+
+## 7.5 Teaching effect analysis after class
+
+After class, teachers can release questions about the class through SCS and guide students to participate in answering questions. Based on this, SCS can help teachers analyse which parts of knowledge are not fully understood by students, evaluate teacher teaching ability, and provide reasonable teaching suggestions.
+
+At the same time, SCS can help teachers analyse the teaching process, take student achievements as labels, analyse the correlation between different teaching methods and knowledge mastery, and recommend different teaching methods to teachers according to different knowledge point.
+
+## 7.6 Learning effect analysis after class
+
+After class, SCS carries out tests to: analyse which parts of knowledge are not fully understood by students; automatically sorts out and summarize the questions on which students make mistakes; and evaluates the learning effect on students. At the same time, with the information collected in class, SCS can evaluate student learning status and help students know their learning level and whether the learning strategies are useful. Based on student historical learning data to generate student portraits, SCS can analyse their levels from qualitative and quantitative perspectives (such as different subjects, different difficulties), and thus propose different reviews, a preview plan, learning suggestions and even occupation planning.
+
+# 8 Service requirements of smart class systems based on artificial intelligence
+
+SCS helps change educational concepts of teachers, reconstructs learning processes of students in and out of class, and promotes student active and personalized learning under the guidance of teachers. Through a new generation of information technology, such as big data and AI, SCS achieves intelligent correction of the results of the work. SCS can run alongside teaching, analyse dynamically and evaluate data diagnostically in the learning process, to form a precise learning analysis report to help teachers understand the learning situation of students or their class. From the perspective of the technical level, SCS includes six major modules: class interaction; objective analysis; intelligent push of course resources; display of teaching and learning results; resource generation; and auxiliary tools. Each module and main technologies are shown in Figure 8-1. This clause provides the general requirements and recommendations for SCS service.
+
+![Diagram of the main technical modules of smart class systems (SCS). The central element is a circular arrow labeled 'SCS'. Six modules are arranged around it: Class interaction, Objective analysis, Intelligent push of course resources, Display of teaching and learning results, Resource generation, and Auxiliary tools. Each module has associated features described in text.](c78c2eefd86269d1740ab85a916f24f2_img.jpg)
+
+The diagram illustrates the main technical modules of smart class systems (SCS). At the center is a circular arrow labeled "SCS". Surrounding this center are six rectangular boxes, each representing a module. Clockwise from the top, the modules and their associated features are:
+
+- Class interaction**: Answer race, random selection, specify an answer
+- Objective analysis**: Single-choice questions, multiple-choice questions, blank filling questions, true-false questions, short answer questions
+- Intelligent push of course resources**: Uploading and downloading of pictures, real-time video display
+- Display of teaching and learning results**: Display diverse works, learning results of individuals or groups, highlight the learning results
+- Resource generation**: Record resources in the process of teaching and learning, conduct course review
+- Auxiliary tools**: Auxiliary teaching devices, automatic adjustment table and chair, recording devices, timer
+
+F.742.1(22)
+
+Diagram of the main technical modules of smart class systems (SCS). The central element is a circular arrow labeled 'SCS'. Six modules are arranged around it: Class interaction, Objective analysis, Intelligent push of course resources, Display of teaching and learning results, Resource generation, and Auxiliary tools. Each module has associated features described in text.
+
+**Figure 8-1 – Main technical modules of smart class systems**
+
+## 8.1 Requirements for class interaction
+
+Participation in a class aims to build a harmonious and democratic atmosphere through the interaction of teachers, students and teaching equipment, so that all levels of learners in the classroom can be actively involved in curriculum-related learning events. The requirements and recommendations for class interaction are as follows.
+
+- SCS is recommended to support multiple ways of class interaction through different question-answer strategies. Based on the teaching situation, teachers can adopt an appropriate classroom interactive strategy to effectively regulate student participation in the class.
+- SCS is recommended for the recognition of blackboard writing by teachers and student handwriting, and suggestions for learning or teaching.
+- SCS is recommended to support interaction through a variety of terminal devices such as: personal computers; pads; mobile phones; television (TV); virtual reality (VR) augmented reality (AR) or mixed reality (MR) equipment; and holographic equipment.
+- SCS is recommended to provide real time, reliable and user-friendly speech-to-text (STT) and text-to-speech (TTS) services by utilizing natural language processing. STT and TTS help communication between students and teachers.
+- STT and TTS are recommended to be editable and automatic error correction.
+
+## 8.2 Requirements for objective analysis
+
+The purpose of objective analysis is to examine student mastery of knowledge and understand the teaching situation of teachers. The requirements and recommendations for objective analysis are as follows.
+
+- SCS is recommended to support the analysis of student preparation for class, identify student weaknesses in knowledge (misunderstanding, beyond comprehension, etc.,) and provide teachers with reasonable lecture preparation suggestions.
+- SCS is recommended to design single- and multiple-choice questions to help teachers examine student mastery of the class.
+- By analysing the knowledge contained in each option, SCS is recommended to assist teachers to understand the learning situation of students, and provide support for effectively promoting the cooperation of learning groups.
+- Through the overall answer, SCS is recommended to help teachers determine student completion of the corresponding problems (such as how many students are participating in learning) and mastery of the course (such as the learning effectiveness of the students).
+- SCS can optionally provide questions of the "fill in the blank", true-false and short answer types. For these kinds of questions, SCS can optionally handle student feedback in vocal form, pictures and text, and SCS can optionally provide teachers with an evaluation of student answers.
+- SCS is recommended to grade examination papers and work results, analyse results after class and form a precise learning analysis report to help teachers understand the learning situation of students or class.
+- SCS is recommended to automatically identify and summarize the questions where students make mistakes.
+- SCS is recommended to utilize an AI algorithm to help students set an individual learning plan or training performance model to predict their future learning situation based on fundamental data, learning data and other characteristic dimensions.
+- SCS is recommended to support the analysis of teacher preparation for class, identify weaknesses in teaching and provide reasonable teaching materials, as well as lecture preparation suggestions.
+
+## **8.3 Requirements for intelligent push of course resources**
+
+SCS assists teachers and students to pass on course resources intelligently. It mainly includes intelligent push methods such as uploading and downloading of pictures, as well as real-time video display. The requirements and recommendations for intelligent push of course resources are as follows.
+
+- SCS is recommended to recognize educational materials, evaluating their level and recommend them to appropriate students.
+- SCS is recommended to support the following four intelligent course resources push strategies:
+  - Teachers and students can send homework or submit works through one click.
+  - Generate the teaching and learning resources by taking pictures or recording through the learning terminal.
+  - The student learning process or effectiveness are presented through taking pictures, and evidence collection, presentation and discussion of results with typical characteristics.
+  - In the process of teaching, teachers can present and share specific teaching sessions or learning results through videos.
+- SCS is recommended to build a personalized knowledge map based on the actual situation of each student, and rely on the construction of the knowledge map to push personalized exercise questions for each student, reduce the time spent on repetitive and invalid questions, and improve learning efficiency.
+- SCS is recommended to support the search function by entering audio, image, video or text of educational materials and specific text, image or video is returned.
+
+## **8.4 Requirements for display of teaching and learning results**
+
+SCS displays diverse works showing the results of student lessons or discussions. SCS helps teachers to comprehensively and quickly understand in a timely fashion the learning process, knowledge internalization and learning results of all students, and provide data support to optimize and adjust teaching strategies.
+
+The requirements and recommendations for display of teaching and learning results are as follows.
+
+- SCS is recommended to analyse the learning results of individuals or groups, including the display of different types of results to expand student thinking. By selecting representative student work, the advantages and deficiencies of SCS can be analysed to promote teaching and learning.
+- SCS is recommended to highlight learning results according to level. SCS is recommended to support the following three highlight strategies.
+  - Highlight excellent results pre-set by teachers, make full use of their demonstration role, and let students understand the typical characteristics of such achievements.
+  - Highlight creative and characteristic achievements and guide students to expand their thinking.
+  - Pay attention to imperfect results, and analyse the reasons for work that is not well completed, to help students to cover learning gaps in a better way.
+
+## **8.5 Requirements for resource generation**
+
+SCS generates teaching resources through one click. It can automatically record resources in the process of teaching and learning in the form of pictures, PDF manuscripts or videos (mainly graphic materials or operation videos displayed on a teacher's screen). SCS is recommended to realize the following three purposes through resource generation:
+
+- help students conduct course review after class;
+- enable students to use resources for personalized tutoring;
+- assist teachers to build a teaching process library, and provide effective materials for the construction of education and teaching resources.
+
+The requirements and recommendations for resource generation are given in clauses 8.5.1 to 8.5.4.
+
+#### **8.5.1 Requirements for data preparation**
+
+The requirements and recommendations for data preparation are as follows:
+
+- SCS is recommended to provide electronic textbooks and materials such as audio, image, video and text;
+- SCS can optionally provide teaching materials such as: VR, AR or MR content; holographic content; flash animation; stickers; music and sound;
+- SCS can optionally provide curriculum information and scheduling, as well as student and teacher attendance information;
+- SCS can optionally provide recording information of teacher lectures, blackboard writing and multimedia teaching;
+- SCS can optionally provide live broadcast and on-demand lecture resources;
+- SCS can optionally provide the knowledge map of data on student learning, teacher teaching and curriculum;
+- SCS is recommended to provide storage space for building machine-learning (ML) databases to store data including audio, images, video, text and knowledge maps.
+
+NOTE 1 – Educational materials can be uploaded and downloaded through different protocols.
+
+NOTE 2 – The SCS data can be opened and shared to ML services and can be accessed only in the SCS. Specification of mechanisms for SCS data openness lie outside the scope of this Recommendation.
+
+#### **8.5.2 Requirements for data pre-processing**
+
+The requirements and recommendations for data pre-processing are as follows:
+
+- SCS is recommended to support the intelligent collection of curriculum resource data in multiple scenarios and multiple teaching modes;
+- SCS is required to support the pre-processing of education materials, such as separating teaching video into frames and extracting key frames;
+- SCS is required to support the recognition and classification of educational videos;
+- SCS is recommended to support multi-dimensional analysis of educational video, including subjects, scenes, objects, labels, voices, text and faces;
+- SCS is recommended to support statistical functions and provide visualized control systems, which can present class conditions through dynamic statistics.
+
+#### **8.5.3 Requirements for model training and deployment**
+
+The requirements and recommendations for model training and deployment are as follows:
+
+- SCS is recommended to support the training of ML models based on an educational ML database;
+- SCS is recommended to support the indication of ML model-training status;
+- SCS is recommended to support the deployment and inference of ML model.
+
+#### **8.5.4 Requirements for data security**
+
+The requirements and recommendations for data security are as follows:
+
+- SCS is required to provide a security and personally identifiable information protection mechanism on collected data;
+- SCS is required to authorize and authenticate access to class data;
+- SCS is required to authorize and authenticate when training and deploying AI capabilities.
+
+### **8.6 Requirements for auxiliary tools**
+
+The requirements and recommendations for auxiliary tools are given in clauses 8.6.1 to 8.6.5.
+
+#### **8.6.1 Requirements for course auxiliary devices**
+
+- SCS is recommended to provide course auxiliary devices for teaching and learning, such as an intelligent timer, intelligent screen and intelligent dictionary pen. The auxiliary devices provide teachers and students with assistance for teaching and learning.
+- Course auxiliary devices of SCS can optionally provide teachers and students with VR, AR or MR and holographic interactive services.
+
+#### **8.6.2 Requirements for recording devices**
+
+- SCS lecture-recording devices (voice recorder, camera, etc.) can optionally acquire data from teacher and student blackboard writing, voices and videos on the premise of ensuring data security.
+
+#### **8.6.3 Requirements for smart tables and chairs**
+
+- SCS is recommended to provide tables and chairs that are flexible to move and can automatically adjust height and tilt angle according to student's height, body mass or sitting position.
+
+#### **8.6.4 Requirements for classroom environment**
+
+- SCS is recommended to automatically adjust temperature, humidity, brightness and other classroom conditions to enhance learning and teaching effects.
+
+#### **8.6.5 Requirements for compatibility**
+
+- SCS is required to support the access by various terminal hardware devices, e.g., a PC; pad; mobile phone; TV; VR, AR or MR equipment and holographic equipment.
+- SCS is recommended to support various operating system platforms.
+- SCS is recommended to be compatible with various browsers.
+
+# **9 Management requirements of smart class systems based on artificial intelligence**
+
+- SCS is recommended to check attendance through face recognition technology, and complete statistics of student attendance results before teaching starts.
+- SCS is recommended to support enquiry into attendance data of students and courses.
+- SCS is recommended to support multi-dimensional data analysis based on departmental or class attendance data.
+- SCS is required to support the management of basic information about teachers and students, including its creation, deletion, modification, searching and browsing, and specify the operation permissions for this function.
+- SCS is required to analyse and display education management information, such as the number of teachers and students, and shows the current teaching progress.
+- SCS is recommended to intelligently generate management suggestions or guidance for education management.
+
+## **10 Security considerations**
+
+This Recommendation describes requirements for SCSs based on AI supported by IMT-2020 and beyond; therefore, general security requirements and mechanisms specified for Internet protocol-based networks and a high-level architecture framework for ML should be applied, see [b-ITU-T Y.3101] and [b-ITU-T Y.3172]. The security mechanisms such as authentication, authority, accounting and encryption should be adopted to ensure SCS security.
+
+## Appendix I
+
+### A reference architecture for smart class systems
+
+(This appendix does not form an integral part of this Recommendation.)
+
+SCS is an intelligent system based on AI, big data, cloud computing, IoT and other intelligent information technologies. It is mainly composed of smart cloud service, a smart platform, smart teaching, learning and management terminal and smart environment terminal. A reference architecture for SCS is depicted in Figure I.1.
+
+- Smart cloud services provide resource management, micro-course management, open courses, online teaching and learning, and online research, etc., based on cloud service.
+- The smart platform is equipped with intelligent centres for classroom communication, data, control and competence.
+- Smart terminals include intelligent teaching, learning and management terminals, such as the teacher's intelligent terminal, the students' intelligent terminal, intelligent management terminals and the parents' intelligent terminal.
+- Smart environment terminals mainly include intelligent hardware facilities and intelligent software equipment. SCS constructs an intelligent teaching and learning service environment, providing resource services, interactive services and teaching tools.
+
+![Reference architecture for smart class systems diagram](33a8f3f01dfa8bce75d23017855a13c5_img.jpg)
+
+The diagram illustrates the reference architecture for smart class systems, organized into three horizontal layers connected by double-headed arrows.
+
+- Top Layer: Smart cloud service** (represented by a cloud icon). It contains six functional blocks: Resource management, Microlecture management, Open course, Online learning, Online teaching, and Online researching.
+- Middle Layer:** Consists of two main components connected by a horizontal double-headed arrow.
+  - Smart platform** (represented by a monitor icon). It includes four centres: Communication centre, Data centre, Control centre, and Competence centre. Below these are four supporting functions: Intelligent algorithm Storage, Search centre Data analysis, Intelligent communication Knowledge base.
+  - Smart environment terminal** (represented by icons of a laptop, tablet, and smartphone). It includes two components: Intelligent hardware and Intelligent software.
+- Bottom Layer: Smart teaching, learning and management terminal** (enclosed in a dashed box). It contains four intelligent terminals connected sequentially by horizontal double-headed arrows:
+  - Teachers' intelligent terminal**: Microlecture, Interaction, Recording, Evaluation.
+  - Students' intelligent terminal**: Microlecture, Interaction, Notes, Evaluation.
+  - Intelligent management terminal**: Teaching effect evaluation, Learning effect evaluation.
+  - Parents' intelligent terminal**: Communication between family and school, Exchange experience.
+
+Reference architecture for smart class systems diagram
+
+F.742.1(22)
+
+**Figure I.1 – Reference architecture for smart class systems**
+
+SCS is designed to improve lecture preparation, enhance interaction between teachers and students and promote teaching quality. Based on AI technology, SCS is an efficient way to reduce the teaching workload, provide a vivid learning environment, develop teaching abilities and performance, and cultivate individual learning styles of students.
+
+## Bibliography
+
+- [b-ITU-T H.862.3] Recommendation ITU-T H.862.3 (2020), *Requirements of the voice management interface for human-care services.*
+- [b-ITU-T Y.2002] Recommendation ITU-T Y.2002 (2009), *Overview of ubiquitous networking and of its support in NGN.*
+- [b-ITU-T Y.3101] Recommendation ITU-T Y.3101 (2018), *Requirements of the IMT-2020 network.*
+- [b-ITU-T Y.3172] Recommendation ITU-T Y.3172 (2019), *Architectural framework for machine learning in future networks including IMT-2020.*
+- [b-ITU-T Y.3174] Recommendation ITU-T Y.3174 (2020), *Framework for data handling to enable machine learning in future networks including IMT-2020.*
+- [b-ITU-T Y.4000] Recommendation ITU-T Y.4000/Y.2060 (2012), *Overview of the Internet of things.*
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.742.2-202401-I_PDF-E/raw.md b/marked/F/T-REC-F.742.2-202401-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..f7b0c5d7175a6b9dd8148155f31ad481b92d3d0a
--- /dev/null
+++ b/marked/F/T-REC-F.742.2-202401-I_PDF-E/raw.md
@@ -0,0 +1,380 @@
+
+
+# Recommendation **ITU-T F.742.2 (01/2024)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+## --- **Functional architecture for distance learning 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 grid lines and the letters 'ITU' in a bold, blue, sans-serif font.
+
+ITU logo
+
+## ITU-T F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.742.2
+
+# Functional architecture for distance learning services
+
+## Summary
+
+Recommendation ITU-T F.742.2 specifies the functional architecture for distance learning services.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.742.2  | 2024-01-13 | 16          | 11.1002/1000/15760 |
+
+## Keywords
+
+Collaboration, distant learning, intelligent analysis, massive online course.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                               | 1    |
+| 6 Overview.....                                                   | 2    |
+| 7 Functional architecture .....                                   | 2    |
+| 8 Functional entities.....                                        | 3    |
+| 8.1 Real-time interactive distance learning applications .....    | 3    |
+| 8.2 Non-real-time distance learning applications .....            | 4    |
+| 8.3 Learning management application .....                         | 4    |
+| 8.4 Real-time non-interactive distance learning applications..... | 4    |
+| 8.5 Authentication and authorization .....                        | 5    |
+| 8.6 User management .....                                         | 5    |
+| 8.7 Resource management.....                                      | 5    |
+| 8.8 Multimedia control .....                                      | 5    |
+| 9 Reference points .....                                          | 5    |
+| 10 Information flow .....                                         | 6    |
+| 10.1 User accesses learning resource .....                        | 6    |
+| 10.2 User contributes content to learning resource .....          | 6    |
+| Bibliography.....                                                 | 7    |
+
+
+
+# Recommendation ITU-T F.742.2
+
+## Functional architecture for distance learning services
+
+## 1 Scope
+
+This Recommendation specifies a functional architecture for distance learning services.
+
+The scope of this Recommendation includes:
+
+- Functional architecture for distance learning services, including specification of capability sets, functional entities and reference points.
+- Information flow for distance learning services, including user management, service interaction, etc.
+
+## 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 term defined elsewhere:
+
+**3.1.1 resource** [b-IETF RFC 3986]: This specification does not limit the scope of what might be a resource; rather, the term "resource" is used in a general sense for whatever might be identified by a uniform resource identifier (URI).
+
+### 3.2 Terms defined in this Recommendation
+
+None.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+ICT Information and Communication Technology
+
+ID Identifier
+
+URI Uniform Resource Identifier
+
+## 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. 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
+
+Distance learning services use information and communication technologies (ICTs) for education delivery. With the support of networks, learning can be anywhere, anytime. With the facilitation of cloud computing, education can be multimedia enabled, customized and widely shared, and third parties can actively participate in the activities for education content provision and software development based on distance learning ICT infrastructures.
+
+Distance learning is beneficial for remote locations where educational resources are relatively scarce.
+
+The use of distance learning is also vitally important as it helps prevent contagious diseases from spreading in schools and training institutes during pandemic times.
+
+Distance learning services are composed of audio, video and message communication. Besides that, they also include service features like screen sharing. Aside from communication between human beings, it also allows users to interact with learning programs and digital learning content.
+
+Also, apps and content feed to distance learning may come from different suppliers, applicable to different age levels. Thus, user management and third-party management are required to be specified to meet the operational requirements.
+
+The architectural design of distance learning system should consider supporting all the features mentioned above.
+
+Regarding the scalability of distance learning services, from a virtual classroom that supports dozens of students to a very large-scale online lecture that accommodates thousands of students, the architectural design is quite different, and a different network infrastructure is required.
+
+## 7 Functional architecture
+
+Figure 7-1 shows the functional architecture for distance learning.
+
+![Functional architecture for distance learning diagram showing four layers: Application, Control, Resource, and User, connected by interfaces IF1, IF2, IF3, IF4, and IF5 through a central Network cloud.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg)
+
+The diagram illustrates the functional architecture for distance learning, organized into four layers separated by interfaces (IF1, IF2, IF3, IF4, IF5) and a central Network cloud.
+
+- Application layer:** Contains five modules: Learning management application, Real-time interactive distance learning applications, Real-time non-interactive distance learning applications, Non-real-time distance learning applications, and Business and institutional applications.
+- Control layer:** Contains four modules: Authentication and authorization, Resource manager, Multimedia control, and User manager.
+- Resource layer:** Contains two modules: Learning resources repository and Third party resource.
+- User layer:** Contains three modules: Distance learning service provider, Consumer/learner, and Guardian.
+
+Interfaces and connections:
+
+- IF1:** Connects the User layer to the Network cloud.
+- IF2:** Connects the Application layer to the Control layer.
+- IF3:** Connects the Control layer to the Resource layer.
+- IF4:** Connects the Control layer to the Network cloud.
+- IF5:** Connects the Control layer to the Network cloud.
+
+F.742.2(24)
+
+Functional architecture for distance learning diagram showing four layers: Application, Control, Resource, and User, connected by interfaces IF1, IF2, IF3, IF4, and IF5 through a central Network cloud.
+
+**Figure 7-1 – Functional architecture for distance learning**
+
+The functional capabilities of the layers in the distance learning architecture are as follows:
+
+- **Application layer:** The application layer contains five modules, which include real-time interactive distance learning applications, real-time non-interactive distance learning applications, non-real-time distance learning applications, business/institutional applications, and learning management applications. These modules provide several applications for distance learners, educators and guardians, such as virtual classrooms, online quizzes, group discussion, lecture broadcasting, attendance check, homework assignment and exam grading.
+- **Control layer:** The control layer contains four modules, which include user management, authentication and authorization, resource management, and multimedia control. These modules provide several functions such as instant message, address book, video call, cloud storage management and third-party open platform.
+- **Resource layer:** learning resource repository and third-party resource, for example as specified in [b-IETF RFC 3986], provide educational content for the functional layer.
+- **User layer:** The user layer contains distance learning service providers, consumers/learners, and guardians.
+
+## 8 Functional entities
+
+### 8.1 Real-time interactive distance learning applications
+
+In order to provide real-time virtual distance learning services for the users, this module should have the following functions:
+
+RIDL-01: Provide a platform where educators can share their knowledge with learners via video or audio meeting room, web pages and other kinds of digital form educational material.
+
+RIDL-02: Provide a platform that allows users to communicate via instant messages, text messages, group voice/video calls, live streaming and file exchanges across different organizations.
+
+RIDL-03: Provide a platform to set up and manage online screen sharing, digital whiteboarding, attendance register, real-time co-annotation, and polling for the virtual or hybrid classroom.
+
+### **8.2 Non-real-time distance learning applications**
+
+In order to provide non real-time distance learning services for the learner, the module should have the following functions:
+
+NRDL-01: Provide a platform where educators can share their knowledge with learners via e-books, recorded video files, web pages and other kinds of digital form educational material.
+
+NRDL-02: Provide a unified platform that allows users to communicate via text messages, forum, bulletin boards, file exchanges and e-mailing across different organizations.
+
+NRDL-03: Provide a function where the learner could submit their assignment and complete examinations or quizzes.
+
+NRDL-04: Provide a function for educators and guardians to view the learners' exam scores.
+
+NRDL-05: Provide a platform to manage and push notifications and announcements within the school or across different organizations, for example, between the Department of education and schools.
+
+### **8.3 Learning management application**
+
+In order to manage education services by the educator and learner, the module should have the following functions:
+
+LM-01: Provide a function to develop curricula, such as syllabus design, course setting, course schedule and learning materials preparation.
+
+LM-02: Provide a function for creating online assignments and tracking study progress.
+
+LM-03: Provide a tool for creating quizzes and exams from the question repository which can be reused in different quizzes.
+
+LM-04: Provide a tool for sharing or uploading course materials like syllabus, reference files or class rules.
+
+LM-05: Provide a personalized dashboard for learners to establish their personal study tracking, course enrolment and view exam scores.
+
+LM-06: Provide a tool for the educator to distribute quizzes, exams or assignments to the selected learners from the resource repository.
+
+LM-07: Provide a grading tool for the educator to grade an assignment or exam, and for leaving personalized feedback for each assignment or exam.
+
+LM-08: Provide a tool for educators to review selected learners' statistical performance using graphic display.
+
+### **8.4 Real-time non-interactive distance learning applications**
+
+In order to provide real-time non-interactive distance learning services for the users, the communication service should have the following functions:
+
+RNDL-01: Provide a platform that allows users to conduct live streaming, file exchanges and e-mailing across different organizations.
+
+### **8.5 Authentication and authorization**
+
+In order to provide authentication and authorization functions for resource management and user management, this module should have the following functions:
+
+AA-01: Provide the access control mechanism to user management and third party authentication.
+
+AA-02: Provide the authorization for third party resources and learning resource repository via resource management.
+
+AA-03: Provide a mechanism to manage the log.
+
+### **8.6 User management**
+
+User management provides management of learners' and educators' profiles. It should have the following functions:
+
+UM-01: Provide permission control to set privileges for different users.
+
+UM-02: Provide user profile management that includes the following profile content:
+
+- User role: educator, student or guardian (father or mother);
+- User information: name, gender and user ID;
+- Educational information: campus, period (kindergarten, primary school, middle school, high school), grade and class ID.
+
+### **8.7 Resource management**
+
+In order to manage the resource from the learning resource repository and third party resources, this module should have the following functions:
+
+RM-01: Manage the educational resource within the learning resource repository and third party resources, such as searching, browsing, uploading, deleting, editing and downloading educational content.
+
+RM-02: Provide a function for third party organizations to develop more educational applications, contents and functionalities.
+
+### **8.8 Multimedia control**
+
+In order to provide the multimedia control function for the application layer, this module should have the following function:
+
+MC-01: Provide multimedia capabilities, such as group voice/video conference, online group communication, online screen sharing, online streaming, session recording, file downloading/uploading and file sharing.
+
+## **9 Reference points**
+
+A description of reference points for distance learning, as shown in Figure 7-1, is provided below:
+
+IF1: Interface 1 supports communication between the user layer and the control layer. It enables the user to interact with service modules to utilize various education services.
+
+IF2: Interface 2 supports communication between the application layer and the control layer. It enables the functional layer's modules to provide essential functions for the control layer.
+
+IF3: Interface 3 supports communication between the control layer and the resource layer. It enables the functional layer to access the resources both within and outside the organization.
+
+IF4: Interface 4 is used to receive the access request from user management and provide access to user management.
+
+IF5: Interface 5 is used to provide resource authorization for the resource management function.
+
+## **10 Information flow**
+
+### **10.1 User accesses learning resource**
+
+Step 1: The learner or educator accesses the learning service function in the control layer as a user via IF1.
+
+Step 2: The learning service function requests the educational material from the resource management function via IF2.
+
+Step 3: The resource management function ingests the designated educational material from the learning resource repository via IF3 and establishes access to the user.
+
+### **10.2 User contributes content to learning resource**
+
+Step 1: The educator accesses the learning management service function in the service layer as a user via IF1 to request an educational material upload.
+
+Step 2: The resource management function allocates the educational material via IF3 in the learning resource repository and returns the result to the learning management service function.
+
+## Bibliography
+
+[b-IETF RFC 3986] IETF RFC 3986 (2005), *Uniform Resource Identifier (URI): Generic Syntax*.
+
+
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.743.12-202106-I_PDF-E/raw.md b/marked/F/T-REC-F.743.12-202106-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..99fb1b3db46f5df433f2038d1c73243c3ae827d3
--- /dev/null
+++ b/marked/F/T-REC-F.743.12-202106-I_PDF-E/raw.md
@@ -0,0 +1,428 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.743.12**
+
+(06/2021)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Multimedia services
+
+---
+
+**Requirements for edge computing in video  
+surveillance**
+
+Recommendation ITU-T F.743.12
+
+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 white, bold, sans-serif font superimposed on the globe.
+
+ITU logo
+
+# ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| <b>TELEGRAPH SERVICE</b>                                        |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| <b>MOBILE SERVICE</b>                                           |                    |
+| Mobile services and multdestination satellite services          | F.110–F.159        |
+| <b>TELEMATIC SERVICES</b>                                       |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| <b>MESSAGE HANDLING SERVICES</b>                                | F.400–F.499        |
+| <b>DIRECTORY SERVICES</b>                                       | F.500–F.549        |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | F.600–F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700–F.799</b> |
+| <b>ISDN SERVICES</b>                                            | F.800–F.849        |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | F.850–F.899        |
+| <b>ACCESSIBILITY AND HUMAN FACTORS</b>                          | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## Recommendation ITU-T F.743.12
+
+# Requirements for edge computing in video surveillance
+
+## Summary
+
+Recommendation ITU-T F.743.12 defines the requirements for edge computing in video surveillance. Edge computing is a distributed computing paradigm aimed at providing various computing services at the edge of the network, and it brings computation and data storage closer to the data source or the location where it is needed, to improve response time and save bandwidth. By using the edge computing technology, the video surveillance system can perform intelligent video analysis and store data near the network premises units. And the edge computing platform provides the management capabilities of the edge resources and functional components to the video surveillance system. It can improve the video processing efficiency and quality of services and reduce the infrastructure cost of the video surveillance system. This Recommendation describes the application scenarios and requirements for edge computing in the video surveillance system.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.743.12 | 2021-06-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/14680">11.1002/1000/14680</a> |
+
+## Keywords
+
+Edge computing, requirements, scenarios, video surveillance.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                                       | 2 |
+| 5   | Conventions .....                                                                                      | 2 |
+| 6   | Scenarios.....                                                                                         | 2 |
+| 6.1 | Video analysis based on edge computing servers .....                                                   | 2 |
+| 6.2 | Collaborative computing based on intelligent premises units (IPUs) and<br>edge computing servers ..... | 3 |
+| 6.3 | Collaborative edge-cloud computing .....                                                               | 3 |
+| 6.4 | Regional PU/IPU management based on edge computing servers .....                                       | 4 |
+| 6.5 | Video storage.....                                                                                     | 4 |
+| 6.6 | Resource, task, and algorithm management.....                                                          | 4 |
+| 7   | Requirements for edge computing in video surveillance .....                                            | 4 |
+| 7.1 | User requirements.....                                                                                 | 4 |
+| 7.2 | Service requirements .....                                                                             | 5 |
+| 7.3 | Security requirements .....                                                                            | 6 |
+| 7.4 | Management requirements .....                                                                          | 7 |
+| 7.5 | Scalability requirements .....                                                                         | 8 |
+| 7.6 | Reliability requirements .....                                                                         | 8 |
+| 7.7 | Performance requirements.....                                                                          | 8 |
+|     | Bibliography.....                                                                                      | 9 |
+
+
+
+# Requirements for edge computing in video surveillance
+
+# 1 Scope
+
+Edge computing technology can support efficient video processing and storage at the network edge of the video surveillance system, to improve the quality of services and reduce the infrastructure cost. This Recommendation describes the application scenarios and requirements for edge computing in the 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.
+
+None.
+
+# 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 unit** [b-ITU-T H.626V2]: 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.3 premises unit** [b-ITU-T H.626V2]: 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.4 service** [b-ITU-T Y.101]: A structure set of capabilities intended to support applications.
+
+**3.1.5 video surveillance system** [b-ITU-T H.626V2]: 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.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 edge computing platform supporting video surveillance**: A geographically distributed computing paradigm, in which various servers at the edge of the network are ubiquitously networked to collaboratively provide the elastic computation, communication, and storage services to video surveillance applications. By constructing the edge computing layer between the premises units and the remote video surveillance centre, the multimedia data can be processed and stored in the
+
+networked edge servers, which is close to the data sources. It can also effectively meet the demands of real-time or latency-sensitive video surveillance applications, and notably ease the network bandwidth bottleneck, in comparison with the centralized computing paradigm.
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|       |                                                       |
+|-------|-------------------------------------------------------|
+| CU    | Customer Unit                                         |
+| ECPVS | Edge Computing Platform supporting Video Surveillance |
+| IPU   | Intelligent Premises Unit                             |
+| IVS   | Intelligent Video Surveillance                        |
+| PTZ   | Pan/Tilt/Zoom                                         |
+| PU    | Premises Unit                                         |
+| VS    | Video Surveillance                                    |
+
+# **5 Conventions**
+
+In this Recommendation:
+
+- The keywords "is required to" indicate a requirement that 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 that is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance.
+
+# **6 Scenarios**
+
+This clause describes the various scenarios for edge computing in video surveillance (VS).
+
+## **6.1 Video analysis based on edge computing servers**
+
+### **Case 1: Traffic flow analysis**
+
+The intelligent video surveillance (IVS) system can be used by the traffic department for monitoring the traffic flow situation. The traffic flow analysis function component is deployed in the edge computing servers for the IVS system. When a traffic administrator needs to obtain the traffic flow situation of some key road sections, they can configure the traffic flow analysis function of the related regional edge servers to process the related surveillance video streams.
+
+Step 1: The user logs into the IVS system through the customer unit (CU), chooses some premises units (PUs) which are deployed at the interested key road sections and configures the traffic flow analysis function. They then submit the traffic flow analysis request to the IVS system.
+
+Step 2: After receiving the request, the IVS system authenticates the user information, and configures the traffic flow analysis function of the corresponding edge computing servers. The IVS system then responds to the CU with the information of the traffic flow analysis function.
+
+Step 3: The edge servers pull the video streams from the corresponding PUs, perform the traffic flow analysis function online, and then sends the analysis results to the IVS system which are finally shown to the user.
+
+### **Case 2: Abnormal event analysis**
+
+The traffic administration department can use the IVS system to find an abnormal event in the work area. For example, the vehicle violation detection function component is deployed in the edge
+
+computing servers for the IVS system, which then automatically detects the illegal parking event and notifies the traffic administrator.
+
+Step 1: The user logs into the IVS system through the CU, chooses some PUs which are deployed at the interested regions and configures the illegal parking detection function. They then submit the request to the IVS system.
+
+Step 2: After receiving the request, the IVS system authenticates the user information, and configures the illegal parking detection function of the corresponding edge computing servers. The IVS system then responds to the CU with the information of the illegal parking detection function.
+
+Step 3: The edge servers pull the video streams from the corresponding PUs, perform the illegal parking detection function online, and then sends the analysis results to the IVS system which are finally shown to the user.
+
+### **Case 3: Surveillance video preprocessing**
+
+The edge computing servers in the IVS system can support online video preprocessing such as pixel brightness transformation, geometric transformation, image smoothing, and edge detection. The output of the video preprocessing can be used for the accurate understanding of video content. However, the video preprocessing algorithms are quite different for the different video analysis functions. Thus, the administrator of the system can configure the video preprocessing functions in the edge computing servers according to further demand of video analysis.
+
+## **6.2 Collaborative computing based on intelligent premises units (IPUs) and edge computing servers**
+
+Currently, many intelligent premises units (IPUs) deployed on the roadside have vehicle structuring functions, e.g., vehicle detection, vehicle colour recognition, and vehicle type recognition. Meanwhile, the intelligent vehicle retrieval function component deployed in the edge computing servers can be configured according to the user's request.
+
+Step 1: The user logs into the IVS system through the CU. Sets several functional parameters such as the channel numbers of the related IPUs with the vehicle structuring function, and the picture of the target vehicle, and then sends the online vehicle retrieval request to the IVS system.
+
+Step 2: After receiving the request, the IVS system authenticates the user information, and analyses the key features of the target vehicle in the picture.
+
+Step 3: The IVS system configures the related IPUs and the online vehicle retrieval function in the related edge computing servers, and then sends the detected features of the target vehicle to the edge computing servers.
+
+Step 4: After loading the vehicle retrieval function, the edge IPUs detect the features of the vehicle in the surveillance video streams, and then the detected results are transmitted to the edge computing servers for real-time vehicle retrieval. If the features of the received data from the IPUs match the attributes of the target vehicle successfully, the retrieval results are sent back to the IVS system which notifies the user instantly.
+
+## **6.3 Collaborative edge-cloud computing**
+
+### **Case 1: Collaborative edge-cloud retrieval**
+
+Owing to the limited resources and data of the edge devices, the video processing results of the edge computing servers can be transmitted to the remote cloud computing platform for further analysis. For example, Tom is an administrator of an IVS system. In the case of vehicle retrieval, when Tom logs into the IVS system through the CU, he can set the channel numbers of the PUs for vehicle retrieval. The edge computing servers can detect the vehicles in the monitoring video streams after loading the vehicle detection function, and then the detected vehicle pictures are transmitted to the
+
+remote cloud platform for real-time vehicle retrieval. The remote cloud platform can compare the vehicle pictures from the edge computing platform with samples in the vehicle database and send back the retrieval results to the IVS system.
+
+### **Case 2: Collaborative edge-cloud alarm linkage**
+
+The VS system allows users to configure the collaborative edge-cloud alarm linkage. When the edge computing server reports an alarm event, the remote cloud computing platform performs the associated actions, such as recording, sending messages, and sending emails.
+
+#### **Case 3: Collaborative edge-cloud data subscription**
+
+The remote cloud computing platform can subscribe to the intelligent video metadata and the service alarm data generated by the edge computing platform. If the subscribed data is generated on the edge computing platform, it will be sent to the cloud computing platform directly.
+
+## **6.4 Regional PU/IPU management based on edge computing servers**
+
+The edge computing servers are usually deployed at the video surveillance (VS) network edge close to the PU/IPU. Once the VS system has been deployed, the edge computing servers can automatically discover the regional PUs/IPUs within the local network, and then connect with the central management platform of the VS system. For example, Tom is an administrator of a VS system. When Tom logs into the VS system through the CU, he can set the region name of each edge computing server and the channel name of each PU/IPU within the management region of the edge server. The edge computing server can provide the related interfaces for the management of the regional PUs/IPUs, such as addition, deletion, modification, searching browsing, pan/tilt/zoom (PTZ) control, local data storage and management, media distribution for the regional PUs/IPUs.
+
+## **6.5 Video storage**
+
+The edge computing server can access its regional PUs/IPUs, and the video data captured by the PUs/IPUs can be stored in the local edge computing server instead of being stored in the remote central management platform or the cloud storage system. When Tom logs into the VS system through the CU, he can replay the history video files stored in the edge computing server according to the channel name of the PU/IPU and the video start time. The edge computing server can provide the related interfaces for the playback of the history video files, such as fast-forward, fast-backward, pause, stop, and volume adjustment.
+
+## **6.6 Resource, task, and algorithm management**
+
+The edge computing platform can manage the video processing algorithms stored in it. A video processing task is a running instance of a video processing algorithm. The resources of the edge computing server, including computing and storage resources, etc., can be allocated to the video tasks deployed on it flexibly, and the video tasks can be deployed on the edge computing server dynamically. The edge computing platform can manage the resources of distributed edge servers remotely and configure the video processing tasks on demand, which can reduce operation and maintenance costs.
+
+# **7 Requirements for edge computing in video surveillance**
+
+## **7.1 User requirements**
+
+- USR-001: An edge computing platform supporting video surveillance (ECPVS) is required to support the registration and de-registration of the end user, and the end user can view and modify the personal information.
+
+- USR-002: An ECPVS is required to support the end user login and logout from the platform conveniently. The username and password are required when an end user logs into the platform.
+- USR-003: An ECPVS is recommended to support the end user view of the user access logs or other platform logs.
+- USR-004: An ECPVS is required to support the end user view of the information of the edge computing server, including name, status, capabilities, location, and other information of the edge computing server.
+- USR-005: An ECPVS is required to support the end user use the different platform services, including video storage and playback, video distribution, video processing, resource management, task management, and algorithm management through the graphical user interface or application programming interfaces.
+
+## 7.2 Service requirements
+
+### 7.2.1 Video analysis service requirements
+
+- SER-001: An ECPVS is recommended to support the video analysis. The video analysis components deployed in the edge computing server can receive the video streams from PUs/IPUs and perform the analysis functions online and process the video files stored in the local edge computing server offline.
+- SER-002: An ECPVS is recommended to support the management of the video processing algorithm repository, including algorithm addition, algorithm modification, and algorithm deletion. The video processing algorithm repository is a subsystem in the ECPVS, which is used for the algorithm storage and can be accessed by the corresponding management interfaces.
+- SER-003: An ECPVS is recommended to support the management of the video processing tasks in the edge computing servers, such as creation, pause, restart, and deletion. And an ECPVS is recommended to support the concurrent running of multiple video processing tasks.
+- SER-004: An ECPVS is recommended to support the view of the progress of the video analysis tasks.
+- SER-005: An ECPVS is recommended to support the view of the status of the resource utilized by the video analysis tasks.
+- SER-006: An ECPVS is recommended to support the view of the log files which record the operations of the video analysis tasks.
+
+### 7.2.2 Collaborative computing service requirements
+
+- SER-007: An ECPVS is recommended to support the collaborative end-edge computing based on the IPUs and edge computing servers. The intelligent video collaborative computing components deployed in the edge computing server can further analyse the results processed by the IPUs collaboratively.
+- SER-008: An ECPVS is recommended to support the collaborative edge-cloud computing mode. The video processing results output by the intelligent analysis components deployed in edge servers can be further analysed by the intelligent cloud computing platform collaboratively.
+- SER-009: An ECPVS is recommended to support the alarm linkage between the edge computing platform and the remote cloud computing platform. Consequently, the remote cloud computing platform can perform the associated actions, such as recording, sending messages, or emails when an alarm event is generated by the edge computing platform.
+
+- SER-010: An ECPVS is recommended to support the subscription of the intelligent video metadata and the service alarm data from the other computing platform.
+- SER-011: An ECPVS is recommended to support the management of the intelligent video collaborative computing tasks, such as creation, pause, restart, and deletion.
+- SER-012: An ECPVS is recommended to support the view of the progress of the intelligent video collaborative computing tasks.
+- SER-013: An ECPVS is recommended to support the view of the status of the resource utilized by the collaborative computing tasks.
+- SER-014: An ECPVS is recommended to support the view of the log files which record the operations of the collaborative computing tasks.
+
+### **7.2.3 Regional PU/IPU management service requirements**
+
+- SER-015: An ECPVS is recommended to support the management of the regional PUs/IPUs, such as addition, deletion, modification, searching, browsing, PTZ control of regional PUs/IPUs, and media distribution for regional PUs/IPUs.
+- SER-016: An ECPVS is recommended to support the view of the log files which record the operations of the regional PU/IPU management service.
+
+### **7.2.4 Video storage service requirements**
+
+- SER-017: An ECPVS is recommended to support the storage of the surveillance video captured by the regional PUs/IPUs.
+- SER-018: An ECPVS is recommended to support the video data management capabilities, including browsing, searching, playback, download, and deletion of the locally stored video files.
+- SER-019: An ECPVS is recommended to support the configuration for the local video storage, including setting the time for recording video, setting the time for video retention, etc.
+
+## **7.3 Security requirements**
+
+### **7.3.1 Authentication security requirements**
+
+- SEC-001: An ECPVS is required to provide the mechanisms for authentication and authorization, and it is required to only permit the authorized users to access the platform and use the platform services. An ECPVS is required to forbid an unauthorized user to handle any resources of the platform.
+- SEC-002: An ECPVS is required to support the multi-level user rights management and implement the fine-grained user group authority control.
+
+### **7.3.2 Access security requirements**
+
+- SEC-003: An ECPVS is required to operate in the environment where network address translation (NAT) and/or firewall devices are present. It is recommended to utilize the specified firewalls, gatekeepers, and other network devices to ensure the security for access to some special edge computing services.
+
+### **7.3.3 Content security requirements**
+
+- SEC-004: An ECPVS is required to ensure the security of the stored video files, the results of the video processing, etc.
+- SEC-005: An ECPVS is required to protect user privacy.
+- SEC-006: An ECPVS is recommended to support the addition of the digital watermark in the video of the specified cameras.
+
+- SEC-007: An ECPVS is recommended to support the media transmission encryption including video streaming encryption and image encryption during media transmission.
+
+### **7.3.4 System security requirements**
+
+- SEC-008: An ECPVS is required to have the capability of resisting various attacks.
+- SEC-009: An ECPVS is required to provide the mechanisms for troubleshooting. It is required that a structural single-node problem be avoided (i.e., a problem at a single node should not cause the failure of the entire platform).
+
+## **7.4 Management requirements**
+
+### **7.4.1 Resource management requirements**
+
+- MAN-001: An ECPVS is required to provide the unified management of the edge computing servers.
+- MAN-002: An ECPVS is recommended to support the resource management of the edge computing servers, such as computing resources, and storage resources. The resources can be allocated and withdrawn flexibly according to the service requests.
+- MAN-003: An ECPVS is recommended to monitor, record, search, and display the operational status of the resources.
+
+### **7.4.2 Tasks management requirements**
+
+- MAN-004: An ECPVS is recommended to support the dynamic task deployment in the edge computing servers, and the edge computing tasks can be installed and uninstalled flexibly according to the service requests.
+- MAN-005: An ECPVS is recommended to support the computing task management, including configuration, addition, deletion, migration, search, and browsing of the edge computing tasks.
+- MAN-006: An ECPVS is recommended to monitor, record, search, and display the status of the edge computing tasks.
+
+### **7.4.3 Algorithm management requirements**
+
+- MAN-007: An ECPVS is recommended to support the algorithm management, including addition, deletion, update, search, and browsing of the edge computing algorithms in the video algorithm repository. The video processing algorithms are usually stored in the video algorithm repository subsystem which can be accessed by the corresponding interfaces.
+
+### **7.4.4 Service management requirements**
+
+- MAN-008: An ECPVS is recommended to provide the capabilities of selecting the specific invoking location of various services among the edge computing servers.
+- MAN-009: An ECPVS is recommended to provide the various computing service subscription means for users and the capabilities of querying, viewing, and modifying their subscription information of the edge computing services.
+- MAN-010: An ECPVS is recommended to provide the capability of accounting, billing, and charging for the edge computing service operation.
+- MAN-011: An ECPVS is recommended to provide the various alternative accounting modes, and to support flexible combination of payment modes, billing modes, billing cycles, preferential pricing, etc.
+
+### **7.4.5 System management requirements**
+
+- MAN-012: An ECPVS is required to provide the unified system management interface which can be called conveniently.
+
+- MAN-013: An ECPVS is recommended to provide the graphical user interface.
+
+## **7.5 Scalability requirements**
+
+- SCA-001: An ECPVS is required to provide resource scalability. When the edge computing servers are increased or decreased, the edge computing capability of the ECPVS is increased or decreased accordingly, and the platform services are uninterrupted.
+- SCA-002: An ECPVS is recommended to provide the resource scalability for each specific edge computing task. The computing and storage resources of individual edge computing tasks can be increased or decreased according to the user's demand.
+
+## **7.6 Reliability requirements**
+
+- REL-001: An ECPVS is required to ensure the reliability of the edge computing services. When some edge computing servers have failed, the other edge computing servers should be guaranteed to operate normally, and the corresponding edge computing services can be used normally.
+- REL-002: An ECPVS is recommended to support the continuous video data transmission after network interruption to ensure that the video is not be lost.
+- REL-003: An ECPVS is required to support the autonomy ability of the edge computing server to continue its service when the edge computing server is disconnected from the central management platform due to unreliable network condition. While the network condition improves, the connection between the central management platform and the edge computing server will be established and the data of both sides will be synchronized again.
+
+## **7.7 Performance requirements**
+
+- PER-001: An ECPVS is required to support the concurrent user operations. The system can serve many users simultaneously while ensuring the quality of service.
+- PER-002: An ECPVS is required to support the concurrent execution of the different tasks while ensuring task execution efficiency.
+
+## Bibliography
+
+- [b-ITU-T H.626V2] Recommendation ITU-T H.626 (2019), *Architectural requirements for a video surveillance system.*
+- [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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.743.13-202203-I_PDF-E/raw.md b/marked/F/T-REC-F.743.13-202203-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..bfb9670ac08c7f7e28ab115df094482d5018d307
--- /dev/null
+++ b/marked/F/T-REC-F.743.13-202203-I_PDF-E/raw.md
@@ -0,0 +1,448 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.743.13**
+
+(03/2022)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Multimedia services
+
+---
+
+**Requirements for the cooperation of multiple  
+edge gateways**
+
+Recommendation ITU-T F.743.13
+
+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 F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| <b>TELEGRAPH SERVICE</b>                                        |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| <b>MOBILE SERVICE</b>                                           |                    |
+| Mobile services and multdestination satellite services          | F.110–F.159        |
+| <b>TELEMATIC SERVICES</b>                                       |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| <b>MESSAGE HANDLING SERVICES</b>                                | F.400–F.499        |
+| <b>DIRECTORY SERVICES</b>                                       | F.500–F.549        |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | F.600–F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700–F.799</b> |
+| <b>ISDN SERVICES</b>                                            | F.800–F.849        |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | F.850–F.899        |
+| <b>ACCESSIBILITY AND HUMAN FACTORS</b>                          | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## Recommendation ITU-T F.743.13
+
+## Requirements for the cooperation of multiple edge gateways
+
+## Summary
+
+Recommendation ITU-T F.743.13 describes the requirements for a function that enables the cooperation of multiple edge gateways (CMEG) to complete complex tasks. It also describes the required capabilities and requirements of key components. The CEMG function can support the information exchanging among multiple edge gateways and deal with gateway failure cooperatively. It can also specify the central gateway which is responsible for selecting a cooperative gateway for each gateway, which in turn monitors the status of its partner gateway and manages the cooperative data and devices.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.743.13 | 2022-03-16 | 16          | <a href="http://handle.itu.int/11.1002/1000/14954">11.1002/1000/14954</a> |
+
+## Keywords
+
+Cooperation, gateway failure, multiple edge gateways.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                  | 2    |
+| 5 Conventions .....                                 | 2    |
+| 6 Overview .....                                    | 2    |
+| 7 Key components of the CMEG function .....         | 3    |
+| 8 Requirements for CMEG.....                        | 4    |
+| 8.1 General requirements.....                       | 4    |
+| 8.2 Requirements for the central role function..... | 5    |
+| 8.3 Requirements for the selection function.....    | 5    |
+| 8.4 Requirements for the control function.....      | 5    |
+| 8.5 Requirements for the monitoring function .....  | 5    |
+| 8.6 Requirements for management function .....      | 6    |
+| 9 Security considerations.....                      | 6    |
+| Appendix I – Scenarios.....                         | 7    |
+| Bibliography.....                                   | 8    |
+
+
+
+## Recommendation ITU-T F.743.13
+
+## Requirements for the cooperation of multiple edge gateways
+
+## 1 Scope
+
+This Recommendation describes requirements for a function that enables the cooperation of multiple edge gateways. This Recommendation covers the following:
+
+- key components and functionalities;
+- requirements of the cooperation of multiple edge gateways.
+
+## 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.2201] Recommendation ITU-T Y.2201 (2009), *Requirements and capabilities for ITU-T NGN*.
+
+[ITU-T Y.2701] Recommendation ITU-T Y.2701 (2007), *Security requirements for NGN release 1*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 augmented reality** [b-ITU-T J.301]: A type of mixed reality where graphical elements are integrated into the real world in order to enhance user experience and enrich information.
+
+**3.1.2 Internet of Things** [b-ITU-T Y.2060]: A global infrastructure for the information society, enabling advanced services by interconnecting (physical and virtual) things based on existing and evolving interoperable information and communication technologies.
+
+NOTE 1 – Through the exploitation of identification, data capture, processing and communication capabilities, the IoT makes full use of things to offer services to all kinds of applications, whilst ensuring that security and privacy requirements are fulfilled.
+
+NOTE 2 – From a broader perspective, the IoT can be perceived as a vision with technological and societal implications.
+
+**3.1.3 network functions virtualization** [b-ITU-T L.1361]: Principle of separating network functions from the hardware they run on by using virtual hardware abstraction.
+
+**3.1.4 quality of service** [b-ITU-R BT.1833]: The collective effect of service performance which determines the degree of satisfaction of a user of the service.
+
+**3.1.5 virtual machine** [b-ITU-T Q.1743]: A software program that simulates a hypothetical computer central processing unit. The programs executed by a virtual machine are represented as byte codes, which are primitive operations for this hypothetical computer.
+
+### 3.2 Terms defined in this Recommendation
+
+None
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                       |
+|------|---------------------------------------|
+| AR   | Augmented Reality                     |
+| CMEG | Cooperation of Multiple Edge Gateways |
+| IoT  | Internet of Things                    |
+| NFV  | Network Functions Virtualization      |
+| QoS  | Quality of Service                    |
+| VM   | Virtual Machine                       |
+
+## 5 Conventions
+
+In this Recommendation:
+
+- The keywords "is required to" indicate a requirement that 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 that is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance.
+
+## 6 Overview
+
+With the technological development of user devices, such as smartphones, laptops, Internet of Things (IoT) devices, wearable devices and connected vehicles, many computationally intensive applications are emerging, such as face recognition, augmented reality (AR) services and self-driving [b-Pavel]. Due to limited computation and battery resources of user devices, cloud computing has been developed to provide computing power and storage to help user devices with their computationally sensitive applications. However, the long propagation latency between user devices to the cloud, limits the quality of service (QoS) for some latency-sensitive applications, for example, autonomous driving [b-Yuyi].
+
+To reduce the response time and handle the rapidly increasing amount of data, it is a trend to offload some or all of the computing tasks to the edge network. Leveraging the computation resources and storage of gateways close to the user devices can provide high performance for computation-intensive and latency-sensitive applications. Using recent advancements in network functions virtualization (NFV), edge gateways can perform a service by creating a virtual machine (VM) for that service.
+
+As shown in Figure 6-1, the cloud has vast computing resources but it is far away from the users, while edge gateways are much closer to the users and have a certain amount of computing resources. When there are large numbers of edge gateways in some scenarios, they can cooperate with each other to provide more computing resources to the users and help each other.
+
+![Figure 6-1: An illustration of providing services using cloud and edge gateways. The diagram shows three layers: Cloud (Data platform), Edge gateway (Wireless, Wired, Wireless), and User equipment (Smartphone, Laptop, Connected vehicles, Health care, Smart home). Vertical arrows indicate 'Distance to user' from 'Far' to 'Near'.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg)
+
+```
+
+graph TD
+    subgraph Cloud
+    DP[Data platform]
+    end
+    
+    I((Internet))
+    
+    subgraph Edge_Gateway_Layer [Edge gateway]
+    WEG1[Wireless edge gateway]
+    WiredEG[Wired edge gateway]
+    WEG2[Wireless edge gateway]
+    end
+    
+    subgraph User_Equipment_Layer [User equipment]
+    SP[Smartphone]
+    L[Laptop]
+    CV[Connected vehicles]
+    HC[Health care]
+    SH[Smart home]
+    end
+
+    DP <--> I
+    I <--> WiredEG
+    WEG1 --- User_Equipment_Layer
+    WiredEG --- User_Equipment_Layer
+    WEG2 --- User_Equipment_Layer
+
+```
+
+The diagram illustrates a three-tier architecture for service provision. At the top, the 'Cloud' layer contains a 'Data platform' connected to the 'Internet'. The middle 'Edge gateway' layer consists of three units: a 'Wireless edge gateway', a 'Wired edge gateway', and another 'Wireless edge gateway'. The bottom 'User equipment' layer includes icons for a 'Smartphone', 'Laptop', 'Connected vehicles' (car, bus), 'Health care' (doctor, medical bag), and a 'Smart home' (house with gear). Vertical double-headed arrows connect the Data platform to the Internet, the Internet to the edge gateways, and the edge gateways to the user equipment. On the left, dashed vertical arrows label the layers: 'Cloud', 'Edge gateway', and 'User equipment'. On the right, a solid vertical arrow labeled 'Distance to user' points from 'Far' at the top to 'Near' at the bottom. The reference 'F.743.13(22)' is noted at the bottom right.
+
+Figure 6-1: An illustration of providing services using cloud and edge gateways. The diagram shows three layers: Cloud (Data platform), Edge gateway (Wireless, Wired, Wireless), and User equipment (Smartphone, Laptop, Connected vehicles, Health care, Smart home). Vertical arrows indicate 'Distance to user' from 'Far' to 'Near'.
+
+**Figure 6-1 – An illustration of providing services using cloud and edge gateways**
+
+Four service scenarios are given in the appendix for informational purposes.
+
+## 7 Key components of the CMEG function
+
+This clause addresses the capabilities of the key components of the CMEG function.
+
+![Figure 7-1: Illustration of the CMEG function. It shows a network of gateways (A-G) with central roles (A and B) and cooperation relations. A legend defines 'Cooperation relation' as a dashed arrow and 'Connection relation' as a solid arrow.](367926125450c2bc3f4bdca9d59a62ba_img.jpg)
+
+```
+
+graph TD
+    A[Gateway A  
+assuming the central role  
+of the CMEG function  
+(Coop. of C)]
+    B[Gateway B  
+assuming the CMEG standby  
+central role  
+(Coop. of A)]
+    C[C  
+(Coop. of E and F)]
+    D[D]
+    E[E  
+(Coop. of D)]
+    F[F  
+(Coop. of B and G)]
+    G[G]
+
+    A --- B
+    A --- C
+    B --- F
+    C --- E
+    C --- F
+    E --- D
+    F --- G
+
+    A -.-> B
+    C -.-> A
+    E -.-> C
+    D -.-> E
+    F -.-> B
+    G -.-> F
+
+```
+
+This diagram shows the CMEG function across a network of gateways. Gateway A is the central role, and Gateway B is the standby central role. Gateways are represented by icons of a router and a server. Solid lines represent 'Connection relations', and dashed lines represent 'Cooperation relations'. Gateway A (Coop. of C) is connected to Gateway B (Coop. of A) and Gateway C (Coop. of E and F). Gateway B is connected to Gateway F (Coop. of B and G). Gateway C is connected to Gateway E (Coop. of D), which is connected to Gateway D. Gateway F is connected to Gateway G. The reference 'F.743.13(22)' is noted at the bottom right. A legend at the bottom left defines the arrow types: 'Cooperation relation' (dashed) and 'Connection relation' (solid).
+
+Figure 7-1: Illustration of the CMEG function. It shows a network of gateways (A-G) with central roles (A and B) and cooperation relations. A legend defines 'Cooperation relation' as a dashed arrow and 'Connection relation' as a solid arrow.
+
+**Figure 7-1 – Illustration of the CMEG function**
+
+Figure 7-1 shows an illustration of several edge gateways with CMEG function and each gateway connects to different user devices.
+
+In this system, one edge gateway will take on the central role of the CMEG function and another gateway will take on the CMEG standby central role. These two gateways are selected based on their status, such as storage capacity, processing speed, average bandwidth, operating stability, and other parameters. The gateway assuming the central role will assign a cooperative gateway to each edge gateway based on the collected status of each edge gateway, such as location, energy situation, communication capability, etc. The cooperative gateway of an edge gateway is responsible for monitoring its status and backing up its data. For example, in Figure 7-1, E is the cooperative gateway for D and C is the cooperative gateway for E and F.
+
+![Diagram showing the key components of the CMEG function. A large rounded rectangle contains five stacked boxes labeled from top to bottom: Central-Role function, Selection function, Control function, Monitoring function, and Management function. Below these boxes, the text 'CMEG function' is centered within the large rectangle.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg)
+
+The diagram illustrates the key components of the CMEG function. It consists of a large rounded rectangle containing five stacked boxes, each representing a functional unit. From top to bottom, these are: Central-Role function, Selection function, Control function, Monitoring function, and Management function. Below the boxes, the text 'CMEG function' is centered within the large rectangle.
+
+Diagram showing the key components of the CMEG function. A large rounded rectangle contains five stacked boxes labeled from top to bottom: Central-Role function, Selection function, Control function, Monitoring function, and Management function. Below these boxes, the text 'CMEG function' is centered within the large rectangle.
+
+F.743.13(22)
+
+**Figure 7-2 – Key components of the CMEG function**
+
+As shown in Figure 7-2, the core of the CMEG function is the gateway cooperation. To handle gateway cooperation, CMEG has four key functional units, namely, central role, selection, control, monitoring and management unit.
+
+The central-role function is responsible for gathering various information about the edge gateways and assigning a cooperative gateway for each gateway.
+
+The selection function is responsible for calculating its quality score, which represents its suitability for taking on the central role, based on the state of the gateway such as the parameters of its storage capacity, processing speed, average bandwidth and operating stability, and selecting appropriate gateways for the CMEG function, including identifying one gateway to assume the central role and another one for backup and assigning a cooperative gateway to each gateway.
+
+The control function is responsible for controlling the cooperative relationship between gateways, including establishing/releasing the cooperative relationship.
+
+The monitoring function is responsible for monitoring the activity status of the cooperative gateway.
+
+The management function is responsible for managing the cooperative data and user devices of the cooperative gateway if necessary.
+
+## **8 Requirements for CMEG**
+
+This clause addresses the requirements for CMEG.
+
+### **8.1 General requirements**
+
+GEN-01: The CMEG function is required to support the exchange of information between multiple edge gateways, including control information and data.
+
+GEN-02: The CMEG function is recommended to enable multiple edge gateways to cooperate on computational tasks.
+
+GEN-03: The CMEG function is required to enable multiple edge gateways to cooperate in case of gateway failures.
+
+GEN-04: The CMEG function is recommended to support the cooperative management of computing, storage, and communication resources across edge gateways.
+
+### **8.2 Requirements for the central role function**
+
+CR-01: The central role function is required to gather various information about the edge gateways, including the connectivity relationships between them.
+
+CR-02: The central role function is required to assign a cooperative gateway to each gateway. The selected cooperating gateway should meet the predefined requirements, e.g., distance requirements.
+
+CR-03: The central role function is required to assign a new cooperative gateway for one gateway, if the previously assigned cooperative gateway fails for an extended period of time.
+
+CR-04: The central role function is required to assign a new cooperative gateway to a gateway if the previously assigned cooperative gateway feeds back that it does not have enough resources to support cooperation.
+
+### **8.3 Requirements for the selection function**
+
+SU-01: The selection function of each gateway is required to calculate its quality score.
+
+SU-02: The selection function of each gateway is required to exchange its Q value with the neighbouring gateways.
+
+SU-03: The selection function of each gateway is required to select one gateway that will assume the central role based on the Q values collected from all the neighbouring gateways, using a common policy and algorithm.
+
+SU-04: The selection function of each gateway can optionally send Q values to a third party (e.g., a cloud platform), which will determine the gateways that will take on the central and standby roles.
+
+### **8.4 Requirements for the control function**
+
+CU-01: The control function of each gateway is required to receive assignment instructions from a central role for its cooperative gateway.
+
+CU-02: The control function of each gateway is required to establish a connection with its cooperative gateway assigned by the central role and inform the other party of its resource requirements.
+
+CU-03: After receiving the resource requirements from its cooperative gateway, the control function of this gateway is required to determine whether to establish a partnership or refuse to establish a partnership, depending on its own resources.
+
+CU-04: The control function of each gateway is required to request the central role to assign a new cooperative gateway if the previous one refuses to establish a partnership.
+
+### **8.5 Requirements for the monitoring function**
+
+MU-01: The monitoring function of each gateway is required to monitor the active status of its cooperative gateway, actively or passively.
+
+MU-02: The monitoring function of each gateway is required to inform the central role in time if its cooperative gateway is offline.
+
+MU-03: The monitoring function of the central role is required to determine whether a gateway is temporarily offline or permanently offline.
+
+### **8.6 Requirements for management function**
+
+MU-01: The management function of each gateway is required to back up the data of its cooperative gateway.
+
+MU-02: The management function of each gateway is required to delete the backup data stored locally of its cooperative gateway at the request of the latter.
+
+MU-03: In case its cooperating gateway is offline, the management function of this gateway is recommended to send backup data of its cooperative gateway to the data platform.
+
+MU-04: In case its cooperating gateway is offline for an extended period of time, the management function of this gateway is recommended to negotiate with the devices originally managed by the cooperative gateway and if possible, become the gateway to which they are connected.
+
+## **9 Security considerations**
+
+It is recommended that the security requirements of [ITU-T Y.2201], [ITU-T Y.2701], and applicable ITU-T X-series, ITU-T Y-series, and ITU-T M-series security Recommendations be taken into consideration, which includes access control, authentication, data confidentiality, communications security, data integrity, availability and privacy.
+
+## **Appendix I**
+
+## **Scenarios**
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Four typical service scenarios are described here, in which multiple edge gateways cooperate with each other supported by the CMEG function defined in this Recommendation.
+
+1. A service for one user is split into multiple sub-tasks which are accomplished by multiple edge gateways in collaboration, and the results of the sub-tasks are returned to the user.
+2. A service requires data collected from multiple locations. The data is collected and pre-processed by multiple edge gateways, and the results are then sent to the data platform. For example, an environmental monitoring service needs to collect data from multiple locations. Multiple IoT devices are connected to several gateways. These edge gateways cooperate with each other to collect data and pre-process these data as required.
+3. A service needs to collect data from one set of devices and needs to trigger another set of devices connected to another edge gateway. For example, a fire monitoring service collects data from smoke detectors. If the edge gateway determines that a fire has occurred, it needs to notify a fire door connected to another edge gateway, triggering a fire alarm and closing the door at the same time.
+4. Many edge gateways work in store-and-forward mode where they collect and store data in advance and report it to the platform when needed. The collected data might be lost due to the failure of the edge gateway. If one gateway has one backup gateway, referred to as a cooperative gateway in this Recommendation, to back up the collected data, when it fails, its cooperative gateway will discover the failure and upload the backup data on its behalf.
+
+## Bibliography
+
+- [b-ITU-T J.301] Recommendation ITU-T J.301 (2014), *Requirements for augmented reality smart television systems.*
+- [b-ITU-T L.1361] Recommendation ITU-T L.1361 (2018), *Measurement method for energy efficiency of network functions virtualization.*
+- [b-ITU-T Q.1743] Recommendation ITU-T Q.1743 (2016), *IMT-Advanced references to Release 11 of LTE-Advanced evolved packet core network.*
+- [b-ITU-T Y.2060] Recommendation ITU-T Y.4000/Y.2060 (2012), *Overview of the Internet of things.*
+- [b-ITU-R BT.1833] Recommendation ITU-T BT.1833 (2014), *Broadcasting of multimedia and data applications for mobile reception by handheld receivers.*
+- [b-Pavel] Pavel, M., and Zdenek, B. (2017), *Mobile edge computing: A survey on architecture and computation offloading.* IEEE Communications Surveys & Tutorials.  
+<<https://ieeexplore.ieee.org/document/7879258>>
+- [b-Yuyi] Yuyi, M., Changsheng, You., Jun, Zhang., Kaibin, Huang., and Khaled, B. L. (2017), *Mobile Edge Computing: Survey and Research Outlook.*  
+<[https://www.researchgate.net/publication/312061424\\_Mobile\\_Edge\\_Computing\\_Survey\\_and\\_Research\\_Outlook](https://www.researchgate.net/publication/312061424_Mobile_Edge_Computing_Survey_and_Research_Outlook)>
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.743.14-202203-I_PDF-E/raw.md b/marked/F/T-REC-F.743.14-202203-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..077522c1648573a4ff50d7027700727207910a10
--- /dev/null
+++ b/marked/F/T-REC-F.743.14-202203-I_PDF-E/raw.md
@@ -0,0 +1,376 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.743.14**
+
+(03/2022)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Multimedia services
+
+---
+
+**Requirements for video distribution systems**
+
+Recommendation ITU-T F.743.14
+
+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 white, bold, sans-serif font superimposed on the globe.
+
+ITU logo
+
+# ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| <b>TELEGRAPH SERVICE</b>                                        |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| <b>MOBILE SERVICE</b>                                           |                    |
+| Mobile services and multdestination satellite services          | F.110–F.159        |
+| <b>TELEMATIC SERVICES</b>                                       |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| <b>MESSAGE HANDLING SERVICES</b>                                | F.400–F.499        |
+| <b>DIRECTORY SERVICES</b>                                       | F.500–F.549        |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | F.600–F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700–F.799</b> |
+| <b>ISDN SERVICES</b>                                            | F.800–F.849        |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | F.850–F.899        |
+| <b>ACCESSIBILITY AND HUMAN FACTORS</b>                          | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.743.14
+
+# Requirements for video distribution systems
+
+## Summary
+
+Recommendation ITU-T F.743.14 describes the requirements and application scenarios for video distribution systems. A video distribution system is an Internet application system that is built based on the underlying content delivery network, and can provide the video collection, distribution and viewing functions for Internet users without any system development.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.743.14 | 2022-03-16 | 16          | <a href="http://handle.itu.int/11.1002/1000/14955">11.1002/1000/14955</a> |
+
+## Keywords
+
+Live streaming, requirements, video distribution, video on demand.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                                   | 1    |
+| 4 Abbreviations and acronyms .....                                              | 1    |
+| 5 Conventions .....                                                             | 2    |
+| 6 Introduction .....                                                            | 2    |
+| 7 Requirements for video distribution system.....                               | 3    |
+| 7.1 User requirements.....                                                      | 3    |
+| 7.2 Service requirements .....                                                  | 4    |
+| 7.3 Security requirements .....                                                 | 5    |
+| 7.4 Quality of service (QoS) and quality of experience (QoE) requirements ..... | 6    |
+| 7.5 Accounting, charging and billing requirements .....                         | 6    |
+| 7.6 Other requirements .....                                                    | 6    |
+| Appendix I – Application scenarios for video distribution system.....           | 7    |
+| I.1 Online education.....                                                       | 7    |
+| I.2 Online corporate event .....                                                | 7    |
+| I.3 Live sports event.....                                                      | 8    |
+| I.4 Live e-commerce event .....                                                 | 8    |
+| Bibliography.....                                                               | 9    |
+
+
+
+# Recommendation ITU-T F.743.14
+
+## Requirements for video distribution systems
+
+# 1 Scope
+
+This Recommendation describes the requirements and application scenarios for video distribution systems.
+
+# 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 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 delivery network** [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 live streaming** [b-ITU-T Y.2084]: A video service in which a continuous stream flows in real-time from the service provider to the terminal device and the user cannot control the temporal order in which content is played.
+
+**3.1.4 service** [b-ITU-T Y.101]: A structured set of capabilities intended to support applications.
+
+**3.1.5 video on demand** [b-ITU-T Y.1910]: A service in which the end user can, on demand, select and view 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).
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 video distribution system (VDS)**: An Internet application system that is built based on the video delivery networking platform such as CDN, and which can provide video collection, distribution and viewing functions for Internet users without any system development.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|     |                           |
+|-----|---------------------------|
+| CDN | Content Delivery Network  |
+| QoE | Quality of Experience     |
+| QoS | Quality of Service        |
+| VDS | Video Distribution System |
+| VOD | Video On Demand           |
+
+# 5 Conventions
+
+In this Recommendation:
+
+- The keywords "is required to" indicate a requirement that 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 that is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance.
+
+# 6 Introduction
+
+For distributing video on the Internet, users can use the content delivery network (CDN defined in [ITU-T Y.2019]) or other improved video delivery networking platforms. Though it can avoid the technically complex implementation and operation of video delivery services from the video source to the destination, users need to also develop their own network video applications with the service capabilities provided by the video delivery networking platform. Therefore, it requires users to have the ability of system development. There is a time-consuming development process before users can access the video distribution application.
+
+VDS is an Internet application system that is built based on the video delivery networking platform such as CDN, and can provide the video collection, distribution and viewing functions for Internet users without any system development. Compared with the traditional video delivery platform such as CDN, VDS enables the users to carry out their video distribution business needs immediately and conveniently and avoid the complex application development and testing process. Figure 1 shows the reference model of VDS. As an Internet application system, to support a wider range of application scenarios, VDS needs to support the common functions and services including account management, live streaming, video on demand (VOD), video recording and storage, video playback, content audit, charging and billing, system operation and maintenance, etc. In addition, an external interactive messaging system is usually used to cooperate with the video distribution system to support instant messaging and comments for video content. The VDS administrator can create a video broadcasting channel or publish a VOD according to the application requirements and use the VDS to distribute the video on the Internet. The audience can then watch the video content produced by the administrator through the VDS.
+
+![Figure 1 – Reference model for video distribution systems. The diagram shows a central 'Video distribution system' (VDS) connected to an 'Interactive message system' at the top and a 'CDN' at the bottom. The VDS is divided into two main functional blocks: 'Account management, Charging and billing, Content audit, Video recording and storage' and 'Video service management unit' (containing 'Live stream management', 'Video on demand management', and 'System operation and maintenance'). The VDS is accessed by a 'VDS administrator' (left) and a 'VDS audience' (right). The administrator manages 'Online education', 'Live sport events', 'Online corporate events', and 'Live E-commerce events'. The audience also views these same categories. The CDN consists of a 'CDN centre node' connected to two 'CDN regional nodes', which are further connected to four 'CDN edge nodes'.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg)
+
+Figure 1 – Reference model for video distribution systems. The diagram shows a central 'Video distribution system' (VDS) connected to an 'Interactive message system' at the top and a 'CDN' at the bottom. The VDS is divided into two main functional blocks: 'Account management, Charging and billing, Content audit, Video recording and storage' and 'Video service management unit' (containing 'Live stream management', 'Video on demand management', and 'System operation and maintenance'). The VDS is accessed by a 'VDS administrator' (left) and a 'VDS audience' (right). The administrator manages 'Online education', 'Live sport events', 'Online corporate events', and 'Live E-commerce events'. The audience also views these same categories. The CDN consists of a 'CDN centre node' connected to two 'CDN regional nodes', which are further connected to four 'CDN edge nodes'.
+
+F.743.14(22)
+
+**Figure 1 – Reference model for video distribution systems**
+
+# 7 Requirements for video distribution system
+
+## 7.1 User requirements
+
+Users can be divided into different roles, administrator, sub-administrator, and audience. Users of different roles participate in different parts of the system, so they have different requirements. The administrator can manage live video channels, VOD and sub-administrators. The sub-administrator can also manage live video channels and VOD, but they must have the corresponding authorities assigned by the administrator and the audience can watch videos through the system.
+
+### 7.1.1 Administrator requirements
+
+- USR-1: A VDS is required to support the registration and de-registration of the administrator through the interface provided by the system.
+- USR-2: A VDS is required to support the administrator to login and logout from the system conveniently. The username and password are required when the administrator logs into the system.
+- USR-3: A VDS is required to support the administrator to view and modify personal information, including name, password, identity information, etc.
+- USR-4: A VDS is required to support the administrator to manage the live video channels, including addition, deletion, modification, browsing, retrieval, audit and ban. The information of a live channel usually includes the name, introduction, watching conditions, start and end time, etc.
+- USR-5: A VDS is required to support the administrator to broadcast the live video through a created live video channel by using the video capturing and transmission devices.
+- USR-6: A VDS is recommended to support the administrator to get the real-time monitoring information of the live channels through the interface provided by the system, including the number of online audiences, the total number of viewings, etc.
+
+- USR-7: A VDS is required to support the administrator to manage the VOD, including addition, deletion, modification, browsing, retrieval, audit and ban. The information of a VOD usually includes the name, introduction, watching conditions, etc.
+- USR-8: A VDS is recommended to support the administrator to get the statistical viewing information of the VOD through the interface provided by the system, including the total number of viewings, etc.
+- USR-9: A VDS is required to support the administrator to manage the accounts of the sub-administrators, including addition, deletion, modification, browsing, retrieval and access control.
+- USR-10: A VDS is recommended to support the administrator to audit the interactive instant messages for the live video channel and the comments for the VOD.
+
+### **7.1.2 Sub-administrator requirements**
+
+- USR-11: A VDS is required to support the sub-administrator to login and logout from the system conveniently. The username and password are required when a sub-admin-user logs into the system.
+- USR-12: A VDS is required to support the sub-administrator to view and modify the personal information, including name, password, identity information, etc.
+- USR-13: A VDS is required to support the sub-administrator to manage the live video channels, broadcast the live video, and manage the VOD when the sub-administrator has the corresponding authorities assigned by the administrator.
+
+### **7.1.3 Audience requirements**
+
+- USR-14: A VDS is required to support the registration and de-registration of the audience through the interface provided by the system.
+- USR-15: A VDS is required to support the audience to login and logout from the system conveniently. The username and password are required when an audience logs into the system.
+- USR-16: A VDS is required to support the audience to watch the live broadcast video and the VOD.
+- USR-17: A VDS is recommended to support the bit rate conversion processing for the live video stream and the VOD to meet the reasonable heterogeneous viewing needs of different audiences in the different network environments.
+- USR-18: A VDS is recommended to support the interactive instant message function for the live broadcast channel and the comment function for the VOD.
+- USR-19: A VDS is recommended to support the report function from the audience when the live broadcast channel or the VOD contains the undesirable information.
+- USR-20: A VDS is recommended to support the content recommendation function of live video channels and the VOD for the audience according to their location and preference information.
+
+## **7.2 Service requirements**
+
+- SRV-1: A VDS is required to support the registration and de-registration of the user through the interface provided by the system.
+- SRV-2: A VDS is required to support the live video distribution from the video capturing devices to the audience viewing devices.
+- SRV-3: A VDS is required to support the VOD.
+- SRV-4: A VDS is required to support the storage and management of the video files.
+
+- SRV-5: A VDS is recommended to support the information collection and display of the live video channels and VOD, such as the number of online audiences, the total number of views, etc.
+- SRV-6: A VDS is recommended to support the transcoding of the live video stream, and the corresponding transcoding templates and configuration are provided.
+- SRV-7: A VDS is recommended to support the transcoding of the video files uploaded for the VOD, and the corresponding transcoding templates and configuration are provided.
+- SRV-8: A VDS is recommended to support the storage and playback of the live video stream.
+- SRV-9: A VDS is recommended to support the instant message interaction for the live broadcast channel and the comment for the VOD.
+- SRV-10: A VDS is recommended to support the audit and report the content of the live video channels and VOD.
+- SRV-11: A VDS is recommended to support the audit and report the instant message for the live broadcast channel and the comment for the VOD.
+- SRV-12: A VDS is recommended to support the content recommendation for the live video channels and the VOD.
+
+## **7.3 Security requirements**
+
+### **7.3.1 Access security requirements**
+
+- SEC-1: A VDS is required to provide the mechanisms for authentication and authorization. It is required to provide different interfaces for the users of different roles. Only the authorized user is allowed to access the corresponding part of the system and use the related function.
+- SEC-2: A VDS is required to provide the mechanisms for viewing condition certification. The audience should be checked whether they can watch the video according to the viewing conditions set by the system administrator.
+- SEC-3: A VDS is required to forbid an unauthorized user to push the live video stream to the system or publish the VOD through the system.
+
+### **7.3.2 Content security requirements**
+
+- SEC-4: A VDS is recommended to provide the security mechanisms for the video stream and stored video, such as video encryption, to ensure the integrity and secrecy of the video data.
+- SEC-5: A VDS is recommended to provide the mechanisms to protect the copyrights of the video streams and stored videos.
+- SEC-6: A VDS is recommended to provide the logo addition function for the live video stream and the VOD resources to maintain the copyright of the initiator of live broadcast and the uploader of the VOD resources.
+- SEC-7: A VDS is recommended to provide the detection and prevention function for the sensitive elements of the video content.
+
+### **7.3.3 System security requirements**
+
+- SEC-8: A VDS is required to protect user privacy. The password and other private information should be encrypted in the system.
+- SEC-9: A VDS is required to have a certain ability to resist vicious attacks.
+- SEC-10: A VDS is required to have the capability of disaster recovery. The system is recommended to use a hot backup to ensure the continuity of system running.
+- SEC-11: A VDS is recommended to provide the troubleshooting mechanism.
+
+## **7.4 Quality of service (QoS) and quality of experience (QoE) requirements**
+
+- QoS-1: A VDS is recommended to implement the QoS strategies on the application layer or on the transmission layer, or both. In cases of delay, jitter, sequence error and packet loss, the system is able to recover and repair the impairments and adjust the data stream in response to the changes in the network bandwidth.
+- QoS-2: A VDS is required to provide high-quality video transmission. When the live video or the recorded video is played, the images and the voice are required to be clear and fluent, and the multimedia is required to be synchronized.
+- QoS-3: A VDS is recommended to support the low end-to-end delay transmission of a live stream from the video capturing device to the audience viewing device, including time taken by encoding, network transmission, decoding and display.
+- QoS-4: A VDS is recommended to support the video frame rate with no lower than 25 frames/s (FPS).
+- QoS-5: A VDS is required to respond rapidly to the user's operation.
+- QoS-6: A VDS is required to provide enough storage space for recording and uploading video.
+
+## **7.5 Accounting, charging and billing requirements**
+
+- ACB-1: A VDS is recommended to provide the capability of accounting, charging, and billing for the system operation.
+- ACB-2: A VDS is recommended to support the view of the network traffic statistics and consumption bill details for the usage of the system services and provide the online payment channel for subscribing to the system services.
+
+## **7.6 Other requirements**
+
+- OTH-1: A VDS is required to support the scalability. When the resources of the system are increased, the system service capability is increased accordingly.
+- OTH-2: A VDS is required to support the concurrent user operations. The system can serve a large number of users simultaneously while ensuring the quality of service.
+- OTH-3: A VDS is recommended to minimize the resource costs for distribution and coding while maintaining the quality of service.
+
+## Appendix I
+
+### Application scenarios for video distribution system
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### I.1 Online education
+
+#### Case 1: Live online course
+
+The VDS can support the multi-person live course for teachers and students in different places through the Internet and enable online interaction effectively between them. Jack is an English teacher, and many of the students are not in the same city. Jack hopes to be able to teach online to bring together students from across the globe for the English course. Jack subscribes to the VDS service and plans to teach online through live broadcast. When Jack logs into the VDS, Jack can choose to create a live channel for the online English course. Jack needs to set name of the live channel, introduction, scale, start and end time and other basic information. To ensure that only the authenticated students can watch the live streaming course, Jack needs to set the viewing conditions of the live broadcast. When Jack starts the course live broadcast, the media capturing and transmission devices are required to produce the media stream of course content. Bob is one of Jack's students. Bob needs to enter the live channel and complete the authentication before watching the live broadcast. Also all the authenticated students can step into the online class at the same time anywhere and start learning. Moreover, the students can view the playback of the online course video recorded in the VDS.
+
+#### Case 2: Course on demand
+
+The VDS can provide the course playback based on the video on demand service for students to learn on their own, at their own pace, or on their own schedule. Jack records the English video course in advance and builds the VOD course in the following steps. Firstly, Jack logs into the VDS. Secondly, Jack chooses to create a new video-on-demand course and sets the name, introduction and other basic information of the course. In addition, Jack also needs to set the course viewing conditions to ensure that only the authenticated students can watch the video. Finally, Jack uploads the course video to the VD system and publishes it online. After the authentication of the VDS, Bob can watch the course on demand at any time. The VDS can also provide friendly interactive functions for the VOD courses at the viewing site, such as fast-forward, fast-backward, pause and stop.
+
+### I.2 Online corporate event
+
+#### Case 1: Product launch
+
+The VDS can support the online product launch for companies on the Internet. A company decides to launch a new product in the market. In order to better promote the product, the company plans to hold an online product launch to allow more people to watch the new product launch event at the same time. Concretely, the company can use the video distribution service provided by the VDS to create a live video channel for the product launch event. The administrator of the system needs to set the name, scale, introduction, start and end time, and other related information of the live broadcast channel. At the launch event site, several cameras can capture the live video from different perspectives, and a video switching and distribution device connected to the cameras can select a live video stream and push it to the created video channel of the VDS. Anyone from all over the world can watch the live broadcast of the online product launch through the VDS. Meanwhile, the VDS can forward the live streaming to the third-party video distribution platform to further increase the exposure of the product launch event.
+
+#### **Case 2: Employee training**
+
+The VDS can support online employee training for companies on the Internet when employees are in different places. Jack is an administrator of a large company with branches in different cities. Jack wants to give employees who are in different cities the latest skills training and hopes to be able to train online so that they can be trained offsite. Jack subscribes to the VDS service and logs into the VD system to create a live channel. Jack also needs to set the name of the live video channel, scale, introduction, start and end time and other basic information about the live channel. In addition, Jack needs to set the identity information of the employees who can watch this live training video in the system. Michael is the presenter of this training course. When Michael starts the live course broadcast, a set of video capturing and transmission device is required to transmit the live training stream to the video channel created in the VDS. Bob is an employee of the company. After passing the system authentication, Bob can watch the live training broadcast at the viewing site of the VDS. Meanwhile, Jack and/or Michael can view the instant audience information during the live broadcast, such as online users, comments about the training, etc.
+
+### **I.3 Live sports event**
+
+The VDS can support live video sharing for sports events. Smith is an organizer of a basketball game, and Smith wants to share the live game videos captured from different perspectives simultaneously on the Internet. Smith logs into the VDS, creates four live video channels for the game broadcast, and sets the name, introduction, start and end time, and other related information of the basketball game. When the game begins, four sets of video capturing and transmission devices around the playing field are used to push the multi-view game video streams to the corresponding video channels of the VDS simultaneously. Then, anyone who is interested in the basketball game can watch the live game video through the VDS. Moreover, Smith can choose the current best-view video channel from the four shared live video streams to watch the game.
+
+### **I.4 Live e-commerce event**
+
+The VDS can provide a live broadcast service for e-commerce participants to help them better promote their products online. Selina is a clothing e-commerce practitioner, and Selena's online store has many latest women's fashion clothing collections. Since the picture of the product gives very little information, Selina wants to use live video to introduce more details about the products and show how well put the clothes can be for the potential customers. Selena logs into the VDS, creates a live video channel, and sets the name, introduction, start and end time, product web link, and other basic information about the clothing e-commerce channel. A set of video capturing and transmission device is used to push the live video stream to the created channel of the VSS, and Selina can introduce and show the products to the visitors of the online shop through the system. Consequently, the visitors can learn more about the details of the products by watching the live e-commerce event, and conveniently buy the interesting products in Selina's online store linked by the video channel webpage.
+
+## Bibliography
+
+- [b-ITU-T Y.101] Recommendation ITU-T Y.101 (2000), *Global Information Infrastructure terminology: Terms and definitions.*
+- [b-ITU-T Y.1910] Recommendation ITU-T Y.1910 (2008), *IPTV functional architecture.*
+- [b-ITU-T Y.2084] Recommendation ITU-T Y.2084 (2015), *Distributed service networking content distribution functions.*
+
+
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.743.20-202008-I_PDF-E/raw.md b/marked/F/T-REC-F.743.20-202008-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..25b2da1c09aaf1bd58411e84ea8a7553649d4443
--- /dev/null
+++ b/marked/F/T-REC-F.743.20-202008-I_PDF-E/raw.md
@@ -0,0 +1,329 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.743.20**
+
+(08/2020)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Multimedia services
+
+---
+
+**Assessment framework for big data  
+infrastructure**
+
+Recommendation ITU-T F.743.20
+
+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.
+
+ITU logo
+
+International  
+Telecommunication  
+Union
+
+# ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| <b>TELEGRAPH SERVICE</b>                                        |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| <b>MOBILE SERVICE</b>                                           |                    |
+| Mobile services and multdestination satellite services          | F.110–F.159        |
+| <b>TELEMATIC SERVICES</b>                                       |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| <b>MESSAGE HANDLING SERVICES</b>                                | F.400–F.499        |
+| <b>DIRECTORY SERVICES</b>                                       | F.500–F.549        |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | F.600–F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700–F.799</b> |
+| <b>ISDN SERVICES</b>                                            | F.800–F.849        |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | F.850–F.899        |
+| <b>ACCESSIBILITY AND HUMAN FACTORS</b>                          | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.743.20
+
+## Assessment framework for big data infrastructure
+
+## Summary
+
+Recommendation ITU-T F.743.20 provides an assessment framework of big data infrastructure, which includes functional metrics, performance metrics, scalability metrics, security metrics, operation metrics and compatibility metrics.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.743.20 | 2020-08-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/14325">11.1002/1000/14325</a> |
+
+## Keywords
+
+Assessment framework, big data infrastructure.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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..... | 1 |
+| 4  | Abbreviations and acronyms .....              | 2 |
+| 5  | Conventions .....                             | 2 |
+| 6  | Overview .....                                | 2 |
+| 7  | Function metrics .....                        | 3 |
+| 8  | Performance metrics .....                     | 4 |
+| 9  | Scalability metrics .....                     | 4 |
+| 10 | Security metrics .....                        | 4 |
+| 11 | Operation metrics.....                        | 4 |
+| 12 | Compatibility metrics .....                   | 5 |
+
+
+
+# Recommendation ITU-T F.743.20
+
+## Assessment framework for big data infrastructure
+
+## 1 Scope
+
+This Recommendation defines the assessment framework for big data infrastructure system, which can be applied to design, development, testing, evaluation and acceptance of big data platforms. The scope of this Recommendation includes:
+
+- Function metrics in big data infrastructure,
+- Performance metrics in big data infrastructure,
+- Scalability metrics in big data infrastructure,
+- Security metrics in big data infrastructure,
+- Operation metrics in big data infrastructure,
+- Compatibility metrics in big data infrastructure.
+
+## 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 Q.3930] Recommendation ITU-T Q.3930 (2012), *Performance testing of distributed systems – Concepts and terminology*.
+
+[ITU-T Y.3500] Recommendation ITU-T Y.3500 (2014) | ISO/IEC 17788: 2014, *Information technology – Cloud computing – Overview and vocabulary*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 cloud service user:** Natural person, or entity acting on their behalf, associated with a **cloud service customer** that uses **cloud services**.
+
+NOTE – Examples of such entities include devices and applications.
+
+**3.1.2 tenant** [ITU-T Y.3500]: One or more cloud service users sharing access to a set of physical and virtual resources.
+
+**3.1.3 multi-tenancy** [ITU-T Y.3500]: Allocation of physical or virtual resources such that multiple tenants and their computations and data are isolated from and inaccessible to one another.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 distributed system:** A system composed of several computers connected by the network. Different computers transmit information through the network for communication and cooperation related to computing tasks.
+
+- 3.2.2 batch computing:** The process of automatically process stored data in units of data sets.
+- 3.2.3 distributed computing:** The invention relates to a computing mode involving a storage layer and a processing layer for implementing a multi-type programming algorithm model.
+- 3.2.4 distributed data processing:** The process of distributing data operations to each node of a computer network for performing calculation.
+- 3.2.5 distributed file system:** The file management system distributed on multiple nodes that can be managed, and the communication and data transmission between nodes that can be carried out through the network in the distributed system.
+- 3.2.6 NoSQL database:** The general name of non-relational database management system, including key values, columns, file, and graph database management system and so on. In a non-relational database management system, data is not organized in a relational model.
+- 3.2.7 scale out:** The process of using an integrated group of individual resources as a single system.
+- 3.2.8 streaming data:** Data generated from a continuously running data source through an interface.
+- 3.2.9 structured data:** A data representation in which the structure of each record assembled from data elements is consistent and can be effectively described using a relational model.
+- 3.2.10 unstructured data:** Data that does not have a predefined model or is not organized in a defined manner.
+
+## 4 Abbreviations and acronyms
+
+This Recommendations uses the following abbreviations and acronyms:
+
+|       |                            |
+|-------|----------------------------|
+| JDBC  | Java Database Connectivity |
+| NoSQL | Not Only SQL               |
+| ODBC  | Open Database Connectivity |
+| SQL   | Structural Query Language  |
+
+## 5 Conventions
+
+In this Recommendation, the following conventions are used:
+
+- 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 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 Overview
+
+Big data infrastructure is a software service based on a distributed system. It can store many types of data, through the distributed system to complete the rapid processing of the data, so as to support the implementation of the upper data application. At the same time, it also has the ability of operation, security management and resource scheduling. The reference framework shown in Figure 1 is
+
+required to include functions like: distributed storage, batch computing, SQL engine, resource scheduling, operation, and security management.
+
+It is recommended for the reference framework to contain NoSQL databases.
+
+![Figure 1: Big data infrastructure reference framework diagram. The diagram shows a layered architecture. At the top is 'Applications'. Below it is a large box labeled 'Big data infrastructure' which contains a dashed box with 'SQL engine', 'NoSQL databases', 'Batch computing', and 'Distributed storage'. To the left of this dashed box is 'Resource scheduling' and to the right is 'Operation/security management'. At the bottom is a 'Data' layer with boxes for 'TEXT', 'IMAGE', 'VIDEO', 'CSV', and '...'. Double-headed arrows connect 'Applications' to the 'Big data infrastructure' box, the 'Big data infrastructure' box to the 'Data' layer, and various components within the 'Big data infrastructure' box. A label 'F.743.20(20)_F01' is at the bottom right.](562f471e8153729557e6a4ee6343c32c_img.jpg)
+
+Figure 1: Big data infrastructure reference framework diagram. The diagram shows a layered architecture. At the top is 'Applications'. Below it is a large box labeled 'Big data infrastructure' which contains a dashed box with 'SQL engine', 'NoSQL databases', 'Batch computing', and 'Distributed storage'. To the left of this dashed box is 'Resource scheduling' and to the right is 'Operation/security management'. At the bottom is a 'Data' layer with boxes for 'TEXT', 'IMAGE', 'VIDEO', 'CSV', and '...'. Double-headed arrows connect 'Applications' to the 'Big data infrastructure' box, the 'Big data infrastructure' box to the 'Data' layer, and various components within the 'Big data infrastructure' box. A label 'F.743.20(20)\_F01' is at the bottom right.
+
+**Figure 1 – Big data infrastructure reference framework**
+
+In order to ensure the successful implementation of big data application, it is necessary to establish the assessment framework of big data infrastructure taking into account six aspects, so as to verify the capability range of big data infrastructure. These six aspects shown in Figure 2 are the metrics such as function metrics, performance metrics, scalability metrics, security metrics, operation metrics and compatibility metrics.
+
+![Figure 2: Metrics for big data infrastructure assessments diagram. A central circle is labeled 'Big data infrastructure'. Six arrows point outwards from this circle to labels: 'Function metrics' (top), 'Performance metrics' (top-right), 'Scalability metrics' (right), 'Security metrics' (bottom), 'Operation metrics' (bottom-left), and 'Compatibility metrics' (top-left). A label 'F.743.20(20)_F02' is at the bottom right.](367926125450c2bc3f4bdca9d59a62ba_img.jpg)
+
+Figure 2: Metrics for big data infrastructure assessments diagram. A central circle is labeled 'Big data infrastructure'. Six arrows point outwards from this circle to labels: 'Function metrics' (top), 'Performance metrics' (top-right), 'Scalability metrics' (right), 'Security metrics' (bottom), 'Operation metrics' (bottom-left), and 'Compatibility metrics' (top-left). A label 'F.743.20(20)\_F02' is at the bottom right.
+
+**Figure 2 – Metrics for big data infrastructure assessments**
+
+## 7 Function metrics
+
+Big data infrastructure is required to have basic functions to process data, including:
+
+- Data import: The infrastructure is required to support data loading from an external data source into distributed storage.
+
+- Data storage: The infrastructure is required to support distributed storage of massive data, provide multi-copy storage capacity, be able to achieve high data storage persistence, and support a variety of data formats and compression algorithms.
+- Batch computing: The infrastructure is required to support data processing in units of data sets, which include data transformations and data analysis.
+
+Big data infrastructure is recommended to have other functions to process data, including:
+
+- Streaming data import: The infrastructure is recommended to support streaming data loading from an external data source into distributed storage and import tasks can be executed in a scheduled manner or immediately.
+- Streaming data processing: The infrastructure is recommended to support real-time data processing, where the data is continuous and boundless and can be processed item by item.
+- Data storage management: The infrastructure is recommended to support management of data storage, where data can be classified according to the user-defined policy.
+
+## 8 Performance metrics
+
+Big data infrastructure is recommended to meet the performance requirements of distributed systems [ITU-T Q.3930]. It is recommended to disclose the details of the performance indicators including:
+
+- Effective storage space: The infrastructure is recommended to disclose the effective storage space and measurement of this indicator.
+- Batch task execution time: The infrastructure is recommended to disclose the execution time and test environment of a batch task in a particular scenario.
+
+If a big data infrastructure provides NoSQL databases, it is recommended to disclose read-write performance and a test environment of NoSQL databases in the particular scenario.
+
+## 9 Scalability metrics
+
+Big data infrastructure is required to have the ability of online horizontal expansion. The performance increases while the number of nodes increases.
+
+Big data infrastructure is recommended to have the ability of on-line horizontal shrinkage.
+
+## 10 Security metrics
+
+Big data infrastructure is required to have security protection to prevent malicious access and attacks, which includes:
+
+- Identity authentication: The infrastructure is required to identify different users.
+- Authority management: The infrastructure is required to support authority management with different roles and systems.
+- Data encryption and decryption: The infrastructure is required to support data encryption and decryption in multiple ways.
+- Audit: The infrastructure is required to support logging audit with different operations.
+
+## 11 Operation metrics
+
+Big data infrastructure is required to have operation management capabilities, which includes:
+
+- Deployment capabilities: The infrastructure is required to support automatic deployment with a visual interface.
+- Cluster management: The infrastructure is required to support operation on clusters with a visual interface.
+
+- User management: The infrastructure is required to support creation, modification and deletion of users and user groups, assignment of different roles and permissions, and modification of user passwords and user information.
+- Fault management: The infrastructure is required to support distinction of alarm levels, configuration of alarm thresholds, and alarm notification through visual interfaces, e-mail, or SMS.
+- Resource monitoring: The infrastructure is required to support visual resource monitoring to check the software and hardware configuration, system performance and resource usage of each module of the system.
+- Job monitoring: The infrastructure is required to support visual monitoring of status, resource usage and log information on jobs.
+- Configuration management: The infrastructure is required to support configuration of a system, including configuration viewing and modification.
+- Log management: The infrastructure is required to support viewing, retrieving, and downloading the logs of the system.
+- Upgrade: The infrastructure is required to support software upgrade without downtime.
+- Multi-tenancy management: The infrastructure is required to support the ability to allocate and schedule computing resources for multiple different tenants and ensure that computing resources for different tenants are isolated from each other.
+
+## **12 Compatibility metrics**
+
+Big data infrastructure is required to support a development interface for applications, which includes:
+
+- Interfaces for JDBC and ODBC.
+- Support for SQL syntax, including data types, operators, functions, etc.
+
+
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.743.26-202406-I_PDF-E/raw.md b/marked/F/T-REC-F.743.26-202406-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..07f7652362c194b70f62da7678ab8fd66d283491
--- /dev/null
+++ b/marked/F/T-REC-F.743.26-202406-I_PDF-E/raw.md
@@ -0,0 +1,359 @@
+
+
+# Recommendation **ITU-T F.743.26 (06/2024)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+---
+
+## **Technical requirements of cloud gaming platform based on IMT-2020 mobile edge computing**
+
+![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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.743.26
+
+# Technical requirements of cloud gaming platform based on IMT-2020 mobile edge computing
+
+## Summary
+
+Recommendation ITU-T F.743.26 specifies the technical requirements of cloud gaming platform based on IMT-2020 mobile edge computing. It defines the deployment, technical requirements for operations functionality within the cloud gaming platform, technical requirements for service capability functionality within the cloud gaming platform, technical requirements for cloud computing platform and network, and security requirements. The Recommendation aims to utilize the technical advantages of IMT-2020 mobile edge computing to provide a reference for the development and deployment of the cloud gaming platform.
+
+## History\*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.743.26 | 2024-06-13 | 16          | 11.1002/1000/15906 |
+
+## Keywords
+
+Central cloud, cloud gaming platform, deployment, edge cloud, mobile edge computing.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                                                        | 2    |
+| 4 Abbreviations and acronyms .....                                                                   | 2    |
+| 5 Conventions .....                                                                                  | 3    |
+| 6 Overview .....                                                                                     | 3    |
+| 7 Cloud gaming platform deployment.....                                                              | 4    |
+| 7.1 Cloud gaming platform deployment based on MEC.....                                               | 4    |
+| 7.2 Cloud gaming platform deployment based on public cloud sinking.....                              | 5    |
+| 8 Technical requirements for service capability functionality within the cloud gaming platform ..... | 5    |
+| 9 Technical requirements for operations functionality within the cloud gaming platform .....         | 6    |
+| 10 Technical requirements for cloud computing platform and network .....                             | 6    |
+| 10.1 Technical requirements for central cloud .....                                                  | 6    |
+| 10.2 Technical requirements for edge cloud .....                                                     | 6    |
+| 10.3 Technical requirements for traffic diversion based on MEC .....                                 | 7    |
+| 10.4 Technical requirements for traffic diversion based on public cloud sinking .                    | 7    |
+| 11 Security requirements .....                                                                       | 7    |
+| Bibliography.....                                                                                    | 8    |
+
+
+
+# Technical requirements of cloud gaming platform based on IMT-2020 mobile edge computing
+
+# 1 Scope
+
+This Recommendation describes the technical requirements of cloud gaming platform based on international mobile telecommunications for 2020 (IMT-2020) mobile edge computing.
+
+The scope of this Recommendation includes:
+
+- Cloud gaming platform deployment.
+- Technical requirements for operations functionality within the cloud gaming platform.
+- Technical requirements for service capability functionality within the cloud gaming platform.
+- Technical requirements for cloud computing platform and network.
+- Security 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 F.743.17] Recommendation ITU-T F.743.17 (2022), *Requirements for cloud gaming systems*.
+- [ITU-T X.1815] Recommendation ITU-T X.1815 (2023), *Security guidelines and requirements for IMT-2020 edge computing services*.
+- [3GPP TS 23.501] 3GPP TS 23.501 V18.5.0 (2024), *System Architecture for the 5G System (5GS); Stage 2 (Release 18)*.
+- [ETSI GS MEC 003] ETSI GS MEC 003 V3.2.1 (2024), *Multi-Access Edge Computing (MEC); Framework and Reference Architecture*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 cloud gaming** [ITU-T F.743.17]: A way of playing the game on a cloud server. In the "cloud gaming" mode, game storage, computing, rendering, and so on are completed in the cloud, players can experience high-quality games through any terminal, anytime anywhere.
+
+**3.1.2 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.
+
+**3.1.3 cloud service** [b-ITU-T Y.3500]: One or more capabilities offered via cloud computing (3.1.2) invoked using a defined interface.
+
+**3.1.4 IMT-2020** [b-ITU-T Y.3100]: (Based on [b-ITU-R M.2083]) Systems, system components, and related technologies that provide far more enhanced capabilities than those described in [b-ITU-R M.1645].
+
+**3.1.5 IMT-2020 system** [ITU-T X.1815]: 3GPP system consisting of the IMT-2020 access network (AN), IMT-2020 core network and user equipment (UE).
+
+## **3.2 Terms defined in this Recommendation**
+
+This Recommendation defines the following terms:
+
+**3.2.1 cloud gaming instance:** A virtual machine instance that contains the necessary environment for one game to run in the cloud, including central processing unit (CPU), graphic processing unit (GPU), memory, storage and network.
+
+**3.2.2 executable game:** The game package which is generated after installing a game on a virtual machine, including program files, resource files, configuration files and other essential components for the game to run.
+
+**3.2.3 game cloudification:** The process and technology that involve uploading a game from local storage to a cloud gaming instance, generating an executable game, and uploading it to the file server for distribution across multiple edge cloud nodes.
+
+**3.2.4 public cloud sinking:** A process that involves transferring cloud computing resources from the central cloud to edge nodes that are located closer to users.
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|          |                                                  |
+|----------|--------------------------------------------------|
+| AAC      | Advanced Audio Coding                            |
+| AN       | Access Network                                   |
+| CGS      | Cloud Gaming Service                             |
+| CPU      | Central Processing Unit                          |
+| GPU      | Graphic Processing Unit                          |
+| IMT-2020 | International Mobile Telecommunications for 2020 |
+| MEC      | Multi-access Edge Computing                      |
+| MEO      | MEC Orchestrator                                 |
+| MEP      | MEC Platform                                     |
+| MEPM     | MEP Manager                                      |
+| NEF      | Network Exposure Function                        |
+| OSS      | Operations Support System                        |
+| PCF      | Policy Control Function                          |
+| QoS      | Quality of Service                               |
+| (R)AN    | (Radio) Access Network                           |
+| UE       | User Equipment                                   |
+| UPF      | User Plane Function                              |
+| VIM      | Virtualization Infrastructure Manager            |
+
+# 5 Conventions
+
+In this Recommendation:
+
+The keywords "is required" indicate a requirement which must be strictly followed and from which no deviation is permitted if the conformance to this document is to be claimed.
+
+The keywords "is recommended" indicate a requirement which is recommended but not absolutely required. Thus, this requirement needn't be present to claim conformance.
+
+Requirements are identified using the following conventions:
+
+- Requirement number xx in clause n is of the form R-n-xx.
+- Recommended requirement number yy in clause n is of the form RR-n-yy.
+- Requirement number xx in subclause n.m is of the form R-n.m-xx.
+- Recommended requirement number yy in subclause n.m is of the form RR-n.m-yy.
+
+# 6 Overview
+
+This Recommendation specifies the content shown in the right part of Figure 1, and it mainly references the content within the red dashed box, which is based on [ITU-T F.743.17]. To enhance the user experience, improve operational efficiency, and increase flexibility, it is essential to specify the requirements of operations functionality and service capability functionality within the cloud gaming platform. The cloud gaming platform includes, but is not limited to, these two functionalities. The other functionalities are beyond the scope of this Recommendation. In the Recommendation, the network specifically refers to the IMT-2020 network.
+
+![Figure 1: Functionality of cloud gaming platform based on IMT-2020 mobile edge computing. The diagram shows a hierarchy of components. At the top is the 'Cloud gaming user'. Below it, 'Cloud gaming service provider' and 'Cloud gaming developer' are grouped under 'CGS'. Arrows show 'Game distribution' from CGS to the user, 'Basic ability' from the platform provider to the service provider, and 'Game content' from the developer to the platform provider. The 'Cloud gaming platform provider' is in a red dashed box and receives 'Infrastructure' from the 'Cloud computing platform and network' at the bottom. To the right, a detailed view of the 'Cloud gaming platform' shows 'Service capability functionality' (Rendering, Encoding, Streaming) and 'Operations functionality' (Instances management, Archives management, Games management, Scheduling management, and ellipsis).](a234352dfaccdc24745c88eef7724cc6_img.jpg)
+
+The diagram illustrates the functional architecture of a cloud gaming platform. At the top, the 'Cloud gaming user' interacts with the 'Cloud gaming service provider' and 'Cloud gaming developer' (collectively labeled 'CGS') via 'Game distribution'. The 'Cloud gaming service provider' receives 'Basic ability' from the 'Cloud gaming platform provider', while the 'Cloud gaming developer' provides 'Game content' to it. The 'Cloud gaming platform provider' is supported by 'Infrastructure' from the 'Cloud computing platform and network'. A red dashed box highlights the 'Cloud gaming platform provider' and its associated 'Cloud gaming service provider' and 'Cloud gaming developer'. To the right, a detailed view of the 'Cloud gaming platform' shows two main functional areas: 'Service capability functionality' (which includes Rendering, Encoding, and Streaming) and 'Operations functionality' (which includes Instances management, Archives management, Games management, Scheduling management, and other functions indicated by an ellipsis). The entire platform is supported by the 'Cloud computing platform and IMT-2020 based network' at the base.
+
+Figure 1: Functionality of cloud gaming platform based on IMT-2020 mobile edge computing. The diagram shows a hierarchy of components. At the top is the 'Cloud gaming user'. Below it, 'Cloud gaming service provider' and 'Cloud gaming developer' are grouped under 'CGS'. Arrows show 'Game distribution' from CGS to the user, 'Basic ability' from the platform provider to the service provider, and 'Game content' from the developer to the platform provider. The 'Cloud gaming platform provider' is in a red dashed box and receives 'Infrastructure' from the 'Cloud computing platform and network' at the bottom. To the right, a detailed view of the 'Cloud gaming platform' shows 'Service capability functionality' (Rendering, Encoding, Streaming) and 'Operations functionality' (Instances management, Archives management, Games management, Scheduling management, and ellipsis).
+
+**Figure 1 – Functionality of cloud gaming platform based on IMT-2020 mobile edge computing**
+
+The service capability functionality needs to support rendering, encoding and streaming. The rendering capability refers to rendering game content into images. The encoding capability involves encoding the rendered images and audio data. The streaming capability refers to transmitting the encoded stream to the user's device.
+
+The operations functionality includes instances management, games management, archives management, and scheduling management. Instances management is responsible for managing the status and allocation of cloud gaming instances. Games management is responsible for game cloudification and updates. Archives management is responsible for managing user game progress and data. Scheduling management is responsible for providing a range of scheduling strategies and allocating appropriate cloud gaming instances based on these scheduling strategies.
+
+The cloud computing platform typically provides both central and edge cloud services. The service capability functionality is deployed at the network edge, with a focus on crucial technologies that directly impact gaming performance. The operations functionality is deployed in a centralized location to primarily handle operational tasks and improve overall management efficiency.
+
+IMT-2020 network provides traffic diversion. The cloud gaming platform utilizes this capability to schedule game users to appropriate edge cloud nodes, thereby enhancing gaming performance and user experience.
+
+# 7 Cloud gaming platform deployment
+
+## 7.1 Cloud gaming platform deployment based on multi-access edge computing (MEC)
+
+The cloud gaming platform deployment, which is based on multi-access edge computing (MEC), is shown in Figure 2. The left part of the deployment mainly references the IMT-2020 system based on [3GPP TS 23.501], while the right part follows the MEC system defined in [ETSI GS MEC 003].
+
+![Figure 2: Cloud gaming platform deployment based on MEC. The diagram shows the architecture of the cloud gaming platform. On the left, the IMT-2020 core network (containing NEF, PCF, and UPF) is connected to a UE via an (R)AN. The core network connects to the MEC system through reference points N33, N5, and N6. The MEC system contains the following functional elements: OSS (Operations functionality), MEO, MEC host (Service capability functionality, MEP, and Virtualization infrastructure), MEPM, and VIM. Reference points Mm1 through Mm7 are shown between these elements. Mm1 is between OSS and MEO; Mm2 is between OSS and MEPM; Mm3 is between MEO and MEPM; Mm4 is between MEO and VIM; Mm5 is between Service capability functionality and MEPM; Mp1 is between Service capability functionality and MEP; Mm6 is between MEPM and VIM; and Mm7 is between Virtualization infrastructure and VIM. A label F.743.26(24) is present at the bottom right of the diagram.](053f1077d592e6622cd21dc4bb4cb366_img.jpg)
+
+Figure 2: Cloud gaming platform deployment based on MEC. The diagram shows the architecture of the cloud gaming platform. On the left, the IMT-2020 core network (containing NEF, PCF, and UPF) is connected to a UE via an (R)AN. The core network connects to the MEC system through reference points N33, N5, and N6. The MEC system contains the following functional elements: OSS (Operations functionality), MEO, MEC host (Service capability functionality, MEP, and Virtualization infrastructure), MEPM, and VIM. Reference points Mm1 through Mm7 are shown between these elements. Mm1 is between OSS and MEO; Mm2 is between OSS and MEPM; Mm3 is between MEO and MEPM; Mm4 is between MEO and VIM; Mm5 is between Service capability functionality and MEPM; Mp1 is between Service capability functionality and MEP; Mm6 is between MEPM and VIM; and Mm7 is between Virtualization infrastructure and VIM. A label F.743.26(24) is present at the bottom right of the diagram.
+
+Figure 2 – Cloud gaming platform deployment based on MEC
+
+The MEC system contains the following functional elements: MEC host, operation support system (OSS), MEC orchestrator (MEO), virtualization infrastructure manager (VIM), MEC platform (MEP) manager (MEPM) and the reference points between them. These functional elements are specified in [ETSI GS MEC 003]. The operations functionality is deployed in the OSS. The service capability functionality is deployed in the MEC host, and the MEP within the host provides support through the Mp1 reference point to ensure running of cloud gaming. The MEC host contains MEC platform (MEP) and virtualization infrastructure. In terms of deployment location, MEPM can be deployed together with MEC host on the edge or with network element in a relatively centralized location.
+
+The user plane function (UPF) can be flexibly deployed on the network edge, while the policy control function (PCF) can be centrally deployed. UPF implements the data plane function of IMT-2020 edge computing, and the MEC host provides the operating environment for the cloud gaming platform. Depending on the application scenario, the UPF and MEC host can be deployed separately or together.
+
+The MEC system and the UPF are connected through the N6 [3GPP TS 23.501] interface, which enables data transmission between them. The implementation of cloud gaming utilizes IMT-2020 network capabilities, general information technology capabilities and industry-specific capabilities through the Mp1 [ETSI GS MEC 003] interface. The MEC system requires two additional interactions with the IMT-2020 network. The first one is an interaction with PCF through the N5 [3GPP TS 23.501] interface, and the second one is an interaction with the network exposure function (NEF) through the N33 [3GPP TS 23.501] interface.
+
+The user equipment (UE) contains all terminals that run cloud gaming and are connected to IMT-2020 core network via the (radio) access network ((R)AN). The (R)AN is the wireless access layer that manages wireless communication connections. The UPF is connected to the (R)AN and is responsible for processing game data transmitted by cloud gaming terminals.
+
+## 7.2 Cloud gaming platform deployment based on public cloud sinking
+
+The deployment of the cloud gaming platform based on public cloud sinking is shown in Figure 3. The left part is based on the IMT-2020 system, which is mainly defined by 3GPP. The right side is based on public cloud sinking. The operations functionality is deployed in the central cloud. Additionally, the service capability functionality is deployed in the edge cloud. The central cloud and the edge cloud interact and collaborate through the network.
+
+![Diagram of cloud gaming platform deployment based on public cloud sinking. The diagram shows three main components: UE, (R)AN, and IMT-2020 core network on the left, and Edge cloud and Central cloud on the right. The UE is connected to the (R)AN, which is connected to the IMT-2020 core network. The IMT-2020 core network contains NEF, PCF, and UPF. The UPF is connected to the Edge cloud via the N6 interface. The NEF is connected to the Edge cloud via the N33 interface. The Edge cloud contains Service capability functionality, Edge cloud service, and Edge cloud infrastructure. The Central cloud contains Operations functionality, Central cloud service, and Central cloud infrastructure. The Edge cloud and Central cloud are connected to each other.](7e670a2b556b53ea9002dfff3a420e08_img.jpg)
+
+The diagram illustrates the architecture for cloud gaming platform deployment based on public cloud sinking. On the far left, the User Equipment (UE) is connected to the (Radio) Access Network ((R)AN). The (R)AN is connected to the IMT-2020 core network. Inside the IMT-2020 core network, there are three main components: Network Exposure Function (NEF), Policy Control Function (PCF), and User Plane Function (UPF). The UPF is connected to the Edge cloud via the N6 interface. The NEF is connected to the Edge cloud via the N33 interface. The Edge cloud is a large box containing three sub-components: Service capability functionality, Edge cloud service, and Edge cloud infrastructure. To the right of the Edge cloud is the Central cloud, which also contains three sub-components: Operations functionality, Central cloud service, and Central cloud infrastructure. A horizontal line connects the Edge cloud and the Central cloud, indicating their interaction. At the bottom right of the diagram, there is a label 'F.743.26(24)'.
+
+Diagram of cloud gaming platform deployment based on public cloud sinking. The diagram shows three main components: UE, (R)AN, and IMT-2020 core network on the left, and Edge cloud and Central cloud on the right. The UE is connected to the (R)AN, which is connected to the IMT-2020 core network. The IMT-2020 core network contains NEF, PCF, and UPF. The UPF is connected to the Edge cloud via the N6 interface. The NEF is connected to the Edge cloud via the N33 interface. The Edge cloud contains Service capability functionality, Edge cloud service, and Edge cloud infrastructure. The Central cloud contains Operations functionality, Central cloud service, and Central cloud infrastructure. The Edge cloud and Central cloud are connected to each other.
+
+**Figure 3 – Cloud gaming platform deployment based on public cloud sinking**
+
+The edge cloud exchanges data with the UPF through the N6 interface. The only way for the edge cloud to access the capabilities of the IMT-2020 network is to interact with NEF through the N33 interface.
+
+# 8 Technical requirements for service capability functionality within the cloud gaming platform
+
+- R-8-01: The service capability functionality is required to support game rendering. This functionality can perform operations and graphics rendering in the cloud and generate real-time game video streams.
+
+- R-8-02: The service capability functionality is required to support encoding. This functionality should provide multiple audio and video codec capabilities, such as advanced audio coding (AAC) [b-ISO/IEC 13818-7], H.264 [b-ITU-T H.264], etc. Additionally, the codec configuration should be adjustable based on operational strategy, terminal user settings and network transmission quality.
+- R-8-03: The service capability functionality is required to support streaming media transmission technology. During data transmission, this functionality has the capability to automatically adjust audio and video encoding bit rates, network bandwidth and packet strategies.
+- RR-8-01: The service capability functionality is recommended to support basic strategies for mitigating weak network conditions to ensure a high-quality gaming experience. This functionality needs to balance factors such as image quality and smoothness, while optimizing for network issues like packet loss, jitter and delay.
+
+# **9 Technical requirements for operations functionality within the cloud gaming platform**
+
+- R-9-01: The operations functionality is required to manage the state of cloud gaming instances and their transitions. This platform should allocate idle cloud gaming instances based on user requests.
+- R-9-02: The operations functionality is required to support dynamic allocation of cloud gaming instance types. This platform should allocate suitable edge cloud instance types based on different business requirements.
+- R-9-03: The operations functionality is required to support a variety of scheduling strategies, including load balancing, geographical location and historical record.
+- R-9-04: The operations functionality is required to support game cloudification.
+- R-9-05: The operations functionality is required to support regular checks for game version updates. If updates are available, the updated game will be cloudified again.
+- R-9-06: The operations functionality is required to provide interfaces for uploading game archives of users, downloading saved archives, and querying archive status.
+- RR-9-01: The operations functionality is recommended to support the unified management archive for users on various terminal devices, which enables the storage, backup and retrieval of game archives.
+
+# **10 Technical requirements for cloud computing platform and network**
+
+## **10.1 Technical requirements for central cloud**
+
+- R-10.1-01: The central cloud is required to support the unified management of edge cloud nodes and dynamically adjust different types of edge cloud nodes based on regional demands.
+- R-10.1-02: The central cloud is required to support dynamic allocation of edge cloud. The central cloud accepts the request from the user and schedules it to the appropriate edge cloud.
+- RR-10.1-01: The central cloud is recommended to support overall resource management, edge business arrangement, the centralized operation and maintenance.
+
+## **10.2 Technical requirements for edge cloud**
+
+- R-10.2-01: Each edge cloud is required to cover one or more cities. For megacities and cities with mass users, multiple edge clouds can be built.
+- R-10.2-02: The edge cloud is required to support network access and be able to connect to the IMT-2020 network at a minimum.
+
+- RR-10.2-01: The edge cloud is recommended to have the network access capability of multiple telecom carriers.
+- RR-10.2-02: The edge cloud is recommended to support the reuse of computing power. When edge cloud resources are idle, their computing power can be shared with users in other scenarios, thus reducing construction costs.
+
+## **10.3 Technical requirements for traffic diversion based on MEC**
+
+- R-10.3-01: Traffic diversion is required to be implemented through the MEC platform.
+- R-10.3-02: When game users switch between MEC services, the MEO is required to perform context migration and inform the cloud gaming platform to switch service nodes.
+- RR-10.3-01: The wireless bandwidth and latency are recommended to be guaranteed by using quality of service (QoS), which can be invoked through the N5 or N33 interfaces.
+
+## **10.4 Technical requirements for traffic diversion based on public cloud sinking**
+
+- R-10.4-01: Traffic diversion is required to be implemented to access the IMT-2020 core network capabilities through the N33 interface.
+- R-10.4-02: When game users migrate between edge cloud nodes, the cloud gaming platform itself is required to detect the migration and implement it to access the IMT-2020 core network capabilities through the N33 interface.
+- RR-10.4-01: The wireless bandwidth and latency are recommended to be guaranteed by using QoS through the N33 interface.
+
+# **11 Security requirements**
+
+The security requirements for IMT-2020 edge computing services specified in [ITU-T X.1815], including those for the infrastructure layer, the network layer, and the edge application layer, are applicable to this Recommendation.
+
+## Bibliography
+
+- [b-ITU-T H.264] Recommendation ITU-T H.264 (2024), *Advanced video coding for generic audiovisual services.*
+- [b-ITU-T Y.3100] Recommendation ITU-T Y.3100 (2017), *Terms and definitions for IMT-2020 network.*
+- [b-ITU-T Y.3500] Recommendation ITU-T Y.3500 (2014), *Information technology – Cloud computing – Overview and vocabulary.*
+- [b-ITU-R M.1645] Recommendation ITU-R M.1645 (2003), *Framework and overall objectives of the future development of IMT-2000 and systems beyond IMT-2000.*
+- [b-ITU-R M.2083] Recommendation ITU-R M.2083 (2015), *IMT Vision – Framework and overall objectives of the future development of IMT for 2020 and beyond.*
+- [b-ISO/IEC 13818-7] ISO/IEC 13818-7 (2006), *Information technology – Generic coding of moving pictures and associated audio information – Part 7: Advanced Audio Coding (AAC).*
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.743.4-201703-I_PDF-E/raw.md b/marked/F/T-REC-F.743.4-201703-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..f7f4ed0d251de415747c8c63ff62cf365031cd7f
--- /dev/null
+++ b/marked/F/T-REC-F.743.4-201703-I_PDF-E/raw.md
@@ -0,0 +1,507 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.743.4**
+
+(03/2017)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Multimedia services
+
+---
+
+**Functional requirements for virtual content  
+delivery networks**
+
+Recommendation ITU-T F.743.4
+
+ITU-T
+
+![ITU logo: A globe with a red lightning bolt, next to the text '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 "International Telecommunication Union" is written in a blue, sans-serif font.
+
+ITU logo: A globe with a red lightning bolt, next to the text 'International Telecommunication Union'.
+
+# ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| <b>TELEGRAPH SERVICE</b>                                        |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| <b>MOBILE SERVICE</b>                                           |                    |
+| Mobile services and multdestination satellite services          | F.110–F.159        |
+| <b>TELEMATIC SERVICES</b>                                       |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| <b>MESSAGE HANDLING SERVICES</b>                                | F.400–F.499        |
+| <b>DIRECTORY SERVICES</b>                                       | F.500–F.549        |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | F.600–F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700–F.799</b> |
+| <b>ISDN SERVICES</b>                                            | F.800–F.849        |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | F.850–F.899        |
+| <b>ACCESSIBILITY AND HUMAN FACTORS</b>                          | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.743.4
+
+# Functional requirements for virtual content delivery networks
+
+## Summary
+
+Recommendation ITU-T F.743.4 gives an overview and the requirements for a virtual content delivery network (VCDN). Appendix I provides two use cases to show how to apply VCDN scenario.
+
+Compared with the traditional content delivery network (CDN) service provisioning defined in Recommendations ITU-T Y.1901 and ITU-T Y.2019, VCDN is a new paradigm using cloud computing, network virtualization and software defined networking (SDN) technology for content delivery for various multimedia services, providing a CDN infrastructure according to vendors' needs. This Recommendation specifies the requirements for VCDN, including requirements on service provision, physical resource management, virtual resource management, VCDN logically isolated network partition (LINP) management, service management, backbone network and security consideration.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.743.4  | 2017-03-01 | 16          | <a href="http://handle.itu.int/11.1002/1000/13178">11.1002/1000/13178</a> |
+
+## Keywords
+
+Cloud computing, content delivery network, SDN, streaming service, virtualisation.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 within this Recommendation.....                      | 2    |
+| 4 Abbreviations and acronyms .....                                     | 2    |
+| 5 Conventions .....                                                    | 2    |
+| 6 Background.....                                                      | 2    |
+| 7 Overview of VCDN .....                                               | 3    |
+| 8 Objectives .....                                                     | 4    |
+| 9 Requirements .....                                                   | 4    |
+| 9.1 Service provision requirements .....                               | 4    |
+| 9.2 Physical resource management requirements.....                     | 5    |
+| 9.3 Virtual resource requirements .....                                | 5    |
+| 9.4 VCDN LINP requirements .....                                       | 7    |
+| 9.5 Service management requirements.....                               | 8    |
+| 10 Backbone network requirements .....                                 | 9    |
+| 11 Security considerations .....                                       | 9    |
+| Appendix I – Use cases for VCDN .....                                  | 11   |
+| I.1 Use case 1: the number of users is rapidly rising in one area..... | 11   |
+| I.2 Use case 2: one node is broken.....                                | 12   |
+| Bibliography.....                                                      | 14   |
+
+
+
+# Recommendation ITU-T F.743.4
+
+## Functional requirements for virtual content delivery networks
+
+## 1 Scope
+
+This Recommendation describes the functional requirements for a virtual content delivery network (VCDN). The scope of this Recommendation covers:
+
+- An overview of VCDN concept and the objectives of VCDN.
+- The requirements for applying VCDN on service provision, all kinds of resources of VCDN, and security considerations.
+
+## 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.1901] Recommendation ITU-T Y.1901 (2009), *Requirements for the support of IPTV services*.
+- [ITU-T Y.2019] Recommendation ITU-T Y.2019 (2010), *Content delivery functional architecture in NGN*.
+- [ITU-T Y.3011] Recommendation ITU-T Y.3011 (2012), *Framework of network virtualization for future networks*.
+- [ITU-T Y.3300] Recommendation ITU-T Y.3300 (2014), *Framework of software-defined networking*.
+- [ITU-T Y.3500] Recommendation ITU-T Y.3500 (2014) *Information technology – Cloud computing – Overview and vocabulary*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 logically isolated network partition (LINP)** [ITU-T Y.3011]: A network that is composed of multiple virtual resources which is isolated from other LINPs.
+
+**3.1.2 network virtualization** [ITU-T Y.3011]: A technology that enables the creation of logically isolated network partitions over shared physical networks so that heterogeneous collection of multiple virtual networks can simultaneously coexist over the shared networks. This includes the aggregation of multiple resources in a provider and appearing as a single resource.
+
+**3.1.3 virtual resource** [ITU-T Y.3011]: An abstraction of physical or logical resource, which may have different characteristics from the physical or logical resource and whose capability may be not bound to the capability of the physical or logical resource.
+
+**3.1.4 software-defined networking** [ITU-T Y.3300]: A set of techniques that enables to directly program, orchestrate, control and manage network resources, which facilitates the design, delivery and operation of network services in a dynamic and scalable manner.
+
+**3.1.5 cloud computing** [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.
+
+### 3.2 Terms defined within this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 virtual content delivery network**: A content delivery network using virtualisation technology that enables the allocation of virtual storage, virtual machines, and network resources according to vendors' requirements in a dynamic and scalable manner.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                               |
+|------|-----------------------------------------------|
+| AAA  | Authentication, Authorization, and Accounting |
+| ACL  | Access Control List                           |
+| CPU  | Central Processing Unit                       |
+| I/O  | Input/Output                                  |
+| LINP | Logically Isolated Network Partition          |
+| OS   | Operating System                              |
+| QoS  | Quality of Service                            |
+| SDN  | Software Defined Networking                   |
+| SLA  | Service Level Agreement                       |
+| VCDN | Virtual Content Delivery Network              |
+| VLAN | Virtual Local Area Network                    |
+
+## 5 Conventions
+
+In this Recommendation, the following conventions are used:
+
+- The keywords "is required" 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 the specification.
+
+## 6 Background
+
+With the development of Internet technology, the network traffic resulting from audio and video services grows exponentially. In the future Internet, video services will be mainstream. A content delivery network (CDN) is technically a comprehensive solution to handle the increased demand for
+
+services. Existing CDN architectures face the challenges of a dramatic increase in video service traffic, as well as additional construction and maintenance costs provided to various multi-vendor services. How to sufficiently take advantage of the resource of CDN to provide flexible and superior service is an important issue to be resolved.
+
+The essential character of virtualisation technology is the elastic allocation of resources. A virtual content distribution network (VCDN) uses virtualization technology to make a unified resource pool, to provide the infrastructure of CDN according to the vendors' need. VCDN uses the management interface to monitor CDNs' load.
+
+VCDN can realize accurate infrastructure distribution and elastic resource scheduling. VCDN can integrate the resources of CDN, reduce construction cost and improve the scalability.
+
+## 7 Overview of VCDN
+
+Virtual CDN provides content delivery service to multiple vendors. VCDN utilizes a set of techniques including cloud computing, network virtualization and software defined networking (SDN) to dynamically control and manage the computing and network resources, which improves scalability, flexibility and availability.
+
+Figure 1 illustrates the basic concept of VCDN.
+
+![Diagram illustrating the VCDN concept, showing layers for LINP management, Resource management, Network controller, and the underlying physical and virtual resource layers across multiple nodes.](dbe553cf16dd14073b89a8263a428664_img.jpg)
+
+The diagram illustrates the VCDN concept across several layers. At the top, three colored ovals represent LINP 1 (blue), LINP 2 (red), and LINP 3 (yellow). Below this, two nodes, Node 1 and Node 2, are shown. Each node contains a 'Logical isolation' layer with colored ovals, a 'Virtual resource' layer with server icons, and a 'Physical resource' layer with server icons. On the left, three management boxes—'LINP management', 'Resource management', and 'Network controller'—are connected via double-headed arrows to the corresponding layers. At the bottom, a 'Backbone network' consisting of several switches is connected to 'End users' (represented by computer icons) through both nodes. The diagram is labeled F.743.4(17)\_F01 in the bottom right corner.
+
+Diagram illustrating the VCDN concept, showing layers for LINP management, Resource management, Network controller, and the underlying physical and virtual resource layers across multiple nodes.
+
+Figure 1 – VCDN concept
+
+A typical CDN providing good performance content delivery service generally consists of many nodes which are located in different areas close to the end user. The nodes are deployed as physical resources such as servers, storage and switches. The physical resources are converted into virtual
+
+resources such as virtual machines, virtual storage and virtual switches, which form a virtual resources pool utilizing virtualization technology. In order to provide service to multiple vendors in a single physical CDN, virtual resources are aggregated and isolated according to vendors' service requirements. Every logically isolated network partition allocated to a specific customer is called a logically isolated network partition (LINP). A VCDN LINP is an aggregation of virtual resources in all the nodes.
+
+The LINP is managed by LINP management which controls and configures the LINP in terms of VCDN vendors' requirement. The virtual resources and physical resources are managed by resources management. When the requirements of a LINP are changing, the LINP management requires resource management to perform functions such as adding or diminishing the virtual resources to the LINP, moving virtual resources from one node to the other node. When resource management is required to adjust backbone network performance, the resource management requires that network controller performs functions such as optimize routing, expanding bandwidth, etc. Note that the backbone network may support software defined networking (SDN) functions.
+
+## 8 Objectives
+
+Virtual CDN is a paradigm using cloud computing, network virtualization and SDN technology for content delivery for various multimedia services. VCDN provides a scalable and elastic CDN function pool of shareable physical or virtual resources to multiple vendors with self-service provisioning and administration on demand. See [b-ETSI-GS-NFV001].
+
+The following are the advantages of applying VCDN:
+
+- Suitable for providing service to multiple vendors.  
+VCDN provides on-demand CDN resource provisioning, which dynamically provides resources according to VCDN vendors' needs. So it is more suitable for providing service multiple vendors.
+- Rapid and flexible adaptation to the requirement of vendors.  
+VCDN provides rapid provisioning of service to adapt to vendors' demands by dynamically changing its configurations and re-allocating virtual resources.
+- Increased availability and usage efficiency.  
+VCDN increases the availability and efficiency in the usage of resources by assigning resources to vendors from a large pool of virtual resources.
+- Reduced investment of CDN provider.  
+VCDN is capable of expanding or reducing its virtual resources to accommodate heavier or lighter workloads. All the resources located in different areas are shared, instead of the physical resources in a certain area which can only be used by the service distributed in that area. Allocating virtual resources increases capability with lower cost than adding physical resources.
+- Increased resiliency and robustness.  
+VCDN is totally deployed in virtualization of network and computing resources, it can implement service chaining without limitation of physical networks.
+
+## 9 Requirements
+
+This clause addresses the requirements for VCDN.
+
+### 9.1 Service provision requirements
+
+VCDN service provision requirements include basic content delivery service provision requirements and special requirements for implementation of virtual CDN. Basic content delivery service provision
+
+requirements are provided in [ITU-T Y.1901], [ITU-T Y.2019] and [b-ETSI-TS-182019]. The related requirements are detailed in clause 6.6.4.1 "Content delivery" of [ITU-T Y.1901] and clause 8 "Content delivery requirements" of [ITU-T Y.2019].
+
+The special requirements for implementation of virtual CDN are as follows:
+
+- The virtual CDN is required to support providing various multi-vendor services.
+- The virtual CDN is required to support legacy CDN service provision, including content downloading, delivery of multiple audio streams, accelerating web page presenting and so on.
+- The virtual CDN is required to support that multiple virtual resources of multiple VCDN vendors be logically isolated from each other.
+- The virtual CDN optionally provides different priority levels for different VCDN vendors according to their service level agreement (SLA).
+- The virtual CDN is required to support dynamic change of its configuration and re-allocation of virtual resources according to VCDN vendors' requirements.
+
+### **9.2 Physical resource management requirements**
+
+Physical resource management enables the configuration of all physical resources used in the VCDN, such as storage, servers and networks used by different VCDN vendors. The requirements for the physical resource management are as follows:
+
+- The physical resource management is recommended to provide the capabilities of managing, configuring, controlling, and monitoring all physical resources for virtual resource management.
+- The physical resource management is recommended to provide diagnostic mechanisms for trouble-shooting to help identify the causes of physical resources failures.
+- The physical resource management is recommended to provide information obtained through the diagnostic mechanisms (e.g., expected recovery time) to virtual resource management.
+- The physical resource management is recommended to detect new physical resources automatically as they are added to the network.
+- The physical resource management is recommended to provide authentication, authorization, and accounting (AAA) mechanisms.
+
+### **9.3 Virtual resource requirements**
+
+#### **9.3.1 Virtual machine requirements**
+
+Physical servers can be abstracted into virtual machines (VMs) in VCDN. Virtual machines provide service functions of CDN, such as media service, load balance service, statistical service and network management. A virtual machine pool is composed of many single virtual machines, the VCDN LINP can utilize the VM in a virtual machine pool according to the requirements of VCDN vendors. The requirements for the virtual machine are as follows.
+
+- The virtual machine is required to provide a virtualized and isolated computing environment for each operating system (OS).
+- The virtual machine is required to support migration of virtual machines between different physical computing machines.
+- The virtual machine's central processing unit (CPU) is required to support virtualization, which allows running multiple virtual CPUs (vCPU) on a single physical CPU.
+- The virtual machine's vCPUs' computing capability can optionally be specified as a fraction of a physical CPU.
+
+- The virtual machine's memory is required to support virtualization, which allows memory allocation and memory release when the virtual machine activates and shutdowns.
+- The virtual machine is required for the hypervisor to support input/output (I/O) virtualization capabilities.
+- The virtual machine is required to be capable of using virtual I/O devices abstracted from the physical I/O devices.
+- The virtual machine's physical network interface is required to support virtualization, where the physical network interface can be virtualized into multiple virtual network interfaces.
+- The virtual machine's physical network interface is required to support virtualization; different virtual machines can be grouped into one virtual local network.
+- The virtual machine can optionally be duplicated to create a new virtual machine with the same configuration.
+- The virtual machine is recommended to support the static and dynamic migration of a virtual machine.
+
+#### 9.3.2 Virtual storage requirements
+
+Physical storage devices can be converted into virtual storage in VCDN. Virtual storage provides the storage function of CDN, such as storing media files and databases. The VCDN LINP can utilize the virtual storage according to the requirements of VCDN vendors. The requirements for the virtual storage are as follows:
+
+- Virtual storage is recommended to provide the capability for the VCDN application to store content by ignoring the difference of storage resources at the physical level, such as storage network architecture, storage (read/write) protocols, physical storage medium, etc.
+- Virtual storage is recommended to provide the capability for the VCDN to dynamically adjust its virtual storage resources according to application requirements. For example to change its storage space, file migration, etc.
+- Virtual storage is required to provide storage interfaces, such as structured data-sharing access interfaces, block storage interfaces or file system interfaces as well as access data path interfaces.
+- Virtual storage is required to provide the capabilities for user authentication and authorization.
+- Virtual storage is required to provide basic configuration capabilities, including storage domain configuration, file system namespace configuration, storage resources configuration and local file system configuration.
+- Virtual storage is recommended to provide performance monitoring and statistics (e.g., disk I/O speed, disk space usage, CPU utilization, memory utilization, job completion).
+- Virtual storage is recommended to provide storage migration functions. Based on migration policies, data can be migrated between different storage devices, which can be local storage or shared storage.
+- Virtual storage is recommended to provide storage backup functions. Backup can be applied at block level and file level storage.
+
+#### 9.3.3 Virtual CDN network requirements
+
+A virtual CDN network provides network functions in one CDN node. Virtual CDN network functions are the functions of the specified intranet network which is applied to access and interconnect servers in one CDN node, instead of backbone network which is connected to other CDN nodes. A virtual CDN network provides network functions such as IP address allocation, virtual local
+
+area network (VLAN) allocation, and virtual switching, among other functions. The requirements for virtual CDN network are as follows:
+
+- A virtual CDN network is recommended to support the dynamic migration of virtual machines. The related resources of virtual machines can be migrated with virtual machines migration. The service cannot be interrupted during virtual machine migration.
+- A virtual CDN network is recommended to provide elastic addressing for different virtual machines. It is recommended to support public IP address and private IP address mapping.
+- A virtual CDN network is recommended to support the isolation of the logical network among virtual machines, such as establishment of a VLAN network.
+- A virtual CDN network is recommended to support different security policies for particular virtual machines, such as access control list (ACL) and firewalls, etc.
+- A virtual CDN network is recommended to support different quality of service (QoS) and bandwidth policies for different virtual machines.
+- A virtual CDN network is recommended to support traffic monitoring and traffic statistics among virtual machines and network ports.
+
+#### **9.3.4 Software resource provisioning requirements**
+
+The software resources include the software for deploying virtual resource, and the software in support of service implementation. The requirements for the software resource are as follows:
+
+- The software resource provisioning is recommended to provide a functionality to configure all virtual resources to support operations automated provisioning and deployment.
+- The software resource provisioning is recommended to support automated deployment according to the service requirement, which can promote provisioning efficiency.
+- The software resource provisioning is recommended to be easy to be programmed and understood.
+- The software resource management is recommended to be unified, including capabilities for licence information registration, allocation, recovery, expiration notification and metering.
+
+#### **9.3.5 Virtual resource management**
+
+The virtual resources management enables VCDN LINP operators to apply management policies to a VCDN LINP. The requirements for the LINP management are as follows:
+
+- The virtual resource management is recommended to provide physical-to-physical resources mapping and physical-to-virtual resources mapping management.
+- The virtual resource management is recommended to provide the secure isolation in addition to conventional control plane and data plane isolation among LINPs.
+- The virtual resource management is recommended to support topology awareness to allow the virtual resources to effectively interact with each other during the construction of LINPs.
+- The virtual resource management is recommended to adjust the capability of LINPs according to the changes of requirements and the reconfiguration.
+- The virtual resources management is recommended to build cloud infrastructure resource pools, and to support service implementation.
+
+### **9.4 VCDN LINP requirements**
+
+#### **9.4.1 VCDN LINP function requirements**
+
+The VCDN LINP is an aggregation of virtual resources in all the nodes. A VCDN LINP is created by the LINP manager and generated by using virtualized resources. The requirements for the VCDN LINPs are as follows:
+
+- The VCDN LINP is recommended to be created and that it inherits appropriate control rights from the virtual resources manager controlling all virtual resources.
+- The VCDN LINP is recommended to consist of a set of virtual resources that are independently manageable partition of physical resources.
+- The VCDN LINP is recommended to abstract specific physical resources. The vendors can access the capabilities of virtual resources by using abstracted interfaces to deliver content.
+- The VCDN LINP is recommended to be isolated from each other. LINPs may not mutually interfere with each other in terms of performance, security, and namespace. Any single LINP may not cause disruptions to other LINPs or physical networks.
+- The VCDN LINP is recommended to be flexibly allocated, reclaimed and released according to the requirement of VCDN. It can automatically maximize the accommodation of multiple LINPs on physical resources and optimize the usage of the physical resources.
+
+#### **9.4.2 VCDN LINP management requirements**
+
+The VCDN LINP management enables VCDN LINP operators to apply management policies to a VCDN LINP. The requirements for the LINP management are as follows:
+
+- The VCDN LINP management is recommended to align the allocation of virtual and physical resources in a LINP.
+- The VCDN LINP management is recommended to reconfigure a LINP by reallocating virtual resources to the LINP so that the LINP operator can adapt the LINP profile to changes in service properties.
+- The VCDN LINP management is recommended to terminate a LINP and release all the virtual resources that are no longer needed.
+- The VCDN LINP management is recommended to provide independently managing LINP which is isolated from others.
+- The VCDN LINP management is recommended to provide visible management operations such as monitoring, fault detection, topology awareness and reconfiguration, resource discovery/allocation/scheduling and customized control.
+- The VCDN LINP management is recommended to provide abstracting the information of physical resources and supporting the simplified or the higher level interfaces for resource control.
+- The VCDN LINP management is recommended to provide constructing or reconfiguring a LINP.
+- The VCDN LINP management is recommended to optimize a LINP so that the LINP can be controlled and managed efficiently to adapt to all kinds of changes, such as traffic fluctuation and network congestion.
+- The VCDN LINP management is recommended to provide authentication and authorization to achieve safe and secure operations of VCDN LINPs.
+
+### **9.5 Service management requirements**
+
+VCDN service management enables a VCDN provider to support service provisioning to VCDN vendors:
+
+- The virtual CDN is required to support providing a VCDN customer management system. The VCDN provider can add or remove vendors, clarify vendors group, customer's credit management and contract management, etc.
+- The virtual CDN is required to support customer self-service portal. VCDN vendors can manage and operate VCDN service by themselves through customer self-service portal.
+
+- The virtual CDN is required to support authentication, authorization, and accounting (AAA) mechanism. The mechanism is recommended to be executed before a VCDN provider or a VCDN customer entity accesses the management entity.
+- The virtual CDN optionally provides vendors with the possibility to submit VCDN service requirement, such as storage and server capacity, content delivery areas, terminal client condition.
+- The virtual CDN optionally provides vendors with the possibility to manage content, including ingest contents to the LINP, remove contents, updated contents, etc.
+- The virtual CDN optionally provides vendors with the possibility to query VCDN service statistics, such as the usage of storage, number of times that the contents have been downloaded, number of online clients, etc.
+- The virtual CDN optionally provides system statistics. It supports various statistics mode, such as usage of storage, total flow, number of nodes.
+
+## 10 Backbone network requirements
+
+VCDN resource management communicates with the backbone network in accordance with VCDN customer requirements, including traffic changes, node migrations and SLA changes. As opposed to the VCDN network, the backbone network is defined as the network that inter-connects all nodes of the VCDN, instead of the intra network of a specific VCDN node. The backbone network is required to transfer content data from VCDN nodes to end users. The backbone network is required to support the software defined networking (SDN) function. The network controller can adjust performance according to resource management requirements. Resource management requires the network controller to perform functions such as routing optimization and expansion of bandwidth, among others. The requirements for a virtual CDN network are as follows:
+
+- Backbone network is required to provide a functionality to discover the underlying network topology to see how the network devices (e.g., SDN-enabled switches and routers) connect to each other.
+- Backbone network is required to provide functionalities for programmability, abstraction, and the orchestration of the SDN devices.
+- Backbone network is required to provide a functionality to collect network information about the capability of the network devices and network information including status of forwarding tables, routing policies, and network topologies.
+- Backbone network is required to provide a functionality to monitor status (e.g., failure, overload) of network devices.
+- Backbone network is required to provide a connectivity between VCDN nodes. By means of this connectivity, a superior node can interwork with the subordinate VCDN nodes to request contents that the nodes do not have, including transfer of virtual machines between connected nodes.
+- Backbone network is required to provide the service level agreement capability according to the requirement of VCDN vendors. The SLA requirements (including QoS) of a VCDN customer for a given content delivery service are expected to be met by appropriate interworking with selected VCDN nodes, even in the event of service performance degradation or a disaster.
+
+## 11 Security considerations
+
+Since a VCDN consists of virtual resources that are available to multiple vendors, security issues regarding network virtualization can be raised. Every customer can administer their own LINP. LINP has some network virtualization properties, such as flexibility, configurability, network abstraction and so on. So those kind of properties can cause unexpected security and privacy issues.
+
+Therefore, the following security issues should be considered to mitigate potential security problems. Security and privacy issues should be considered during planning and designing network virtualization solutions. The issues can include security and privacy requirements of VCDN vendors, VCDN providers and end users. In order to prevent malicious access, the AAA functions are essential to operate LINPs. In addition, it is necessary to keep monitoring the security and privacy of data and applications that are implemented and deployed in VCDN LINPs.
+
+## Appendix I
+
+### Use cases for VCDN
+
+(This appendix does not form an integral part of this Recommendation.)
+
+The traditional CDN model for distributing content is based on cache servers located at the edge of the network (those closest to the end users) for delivering content to end users in a reliable and timely manner. Generally, the capacity and service function of physical devices are deployed according to the requirement of the users in that area.
+
+There are some disadvantages that come with this model. When service demand is dramatically and tentatively raised in area A, the CDN operator only adds physical cache servers to meet the requirement, while the workload of cache servers in the B area are very low, but they could not be shared with the cache servers in area A. However, when the service demand is decreased in area A, the load of cache servers becomes low. In that case, it comes at a higher operational cost for CDN operators..
+
+Virtual CDN can deal with the issues mentioned above. VCDN uses virtualization technology to virtualize cache servers in any area. VCDN service provider ensures service sustainability and flexibly to manage their networks according to service demands without complexity. Distribution resources are not limited in its own local area of users, if the resource of virtual machine overloads in area A, while the load of virtual machine in area B is low. The central controller gets the message and logically distributes some of area B's virtual machine resources to area A to service users in area A. In addition, the central controller also distributes some network capacity to area A, such as bandwidth or superior QoS.
+
+### I.1 Use case 1: the number of users is rapidly rising in one area
+
+This use case is illustrated in Figure I.1. A VCDN vendor provides a popular service, so the number of users is dramatically rising. However, the storage and distribution resources of the node of that area are insufficient. Hence, VCDN allocates some virtual resources to the node from another node. At the same time, the VCDN informs the SDN enabled network controller to allocate the network resource via the content delivery paths, which can guarantee quality of delivery contents service.
+
+- 1) The number of users is dramatically rising when some new services which are popular are provided to the area.
+- 2) The customer of the VCDN notices this issue and needs more content delivery resources. The VCDN resource management and LINP management find there is no more resources in node 1 which is the best node to provide service in the area.
+- 3) But more resources are unused in node 2. So some virtual resources identified as N2V3 are allocated to provide service to the area.
+- 4) At the same time, SDN enabled network controller is required to provide a better network path for providing delivery content service from node 2 to the users in the area.
+- 5) The network controller allocates a best path to the service according to the topology information to guarantee the quality of service. Users can also receive best service from node 2.
+
+NOTE – The identification in the node ellipse, which is described as NxVx in Figures I.1 and I.2, represents the virtual resources allocated by LINP management. This means that it is located in the specific node and the number of virtual resource. Letter "N" represents the node and letter "V" represents the virtual resource. The numbers after letters "N" and "V" represents the resource number. For example, N2V3 indicates that it belongs to node 2, and that it is the third virtual resource.
+
+![Diagram of Figure I.1 showing network management and user distribution. At the top, three management boxes are connected in a chain: 'Resource management' (2) -> 'LINP management' (4) -> 'Network controller'. Below them are two nodes: 'Node 2' (3) containing virtual nodes N2V1, N2V2, and N2V3; and 'Node 1' containing virtual nodes NIV1, NIV2, NIV3, and NIV4. Both nodes are connected to a central 'Backbone network' (5) which consists of five interconnected switches. Below the backbone network are two groups of 'End users'. A callout bubble (1) next to the right group of users states 'The number of users is rising rapidly'. Green dashed lines connect the nodes to the backbone network, and red dashed lines connect the backbone network to the end users. A small label 'F.743.4(17)_FI.1' is in the bottom right corner.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg)
+
+Diagram of Figure I.1 showing network management and user distribution. At the top, three management boxes are connected in a chain: 'Resource management' (2) -> 'LINP management' (4) -> 'Network controller'. Below them are two nodes: 'Node 2' (3) containing virtual nodes N2V1, N2V2, and N2V3; and 'Node 1' containing virtual nodes NIV1, NIV2, NIV3, and NIV4. Both nodes are connected to a central 'Backbone network' (5) which consists of five interconnected switches. Below the backbone network are two groups of 'End users'. A callout bubble (1) next to the right group of users states 'The number of users is rising rapidly'. Green dashed lines connect the nodes to the backbone network, and red dashed lines connect the backbone network to the end users. A small label 'F.743.4(17)\_FI.1' is in the bottom right corner.
+
+**Figure I.1 – Use case 1: The number of users is rapidly rising in one area**
+
+### I.2 Use case 2: one node is broken
+
+This use case is illustrated in Figure I.2.
+
+When the hardware, software and network of a certain node fails, this leads to content delivery service disruption. VCDN then allocates the service of the node to another node. At the same time, the VCDN informs the SDN enabled network controller to allocate the network resource via the content delivery paths, which can guarantee quality of delivery contents service.
+
+- 1) Node 1 is broken for some reason.
+- 2) The VCDN resource management and LINP management detect it.
+- 3) Virtual resources identified as N2V3 and N2V4 in node 2 are allocated to provide service taking place node 1.
+- 4) At the same time, SDN enabled network controller is required to provide a better network path for providing delivery content service from node 2 to the users in the area.
+- 5) Network controller allocates a best path to the service according to topology information to guarantee the quality of service. Users can also receive best service from node 2.
+
+![Network diagram showing a broken node (Node 1) and its impact on end users. The diagram includes Resource management, LINP management, Network controller, Node 1, Node 2, a Backbone network, and End users. Node 1 is marked as broken, and its failure is shown affecting the network paths to end users.](9c6461e1e94afae4dec455e69a2ce152_img.jpg)
+
+The diagram illustrates a network architecture with the following components and connections:
+
+- Management Layer:** At the top, three boxes are connected in a chain: **Resource management** (②) — **LINP management** (④) — **Network controller**. Dashed lines connect **Resource management** and **LINP management** to both **Node 1** and **Node 2**. The **Network controller** is connected to **Node 1**.
+- Nodes:**
+  - Node 1** (①) is a cloud containing four sub-components: **N1V1** (yellow), **N1V2** (yellow), **N1V3** (blue), and **N1V4** (blue). A red starburst icon next to it says "The node is broken".
+  - Node 2** (③) is a cloud containing four sub-components: **N2V1** (blue), **N2V2** (yellow), **N2V3** (yellow), and **N2V4** (yellow).
+- Backbone network:** A central cloud (⑤) labeled "Backbone network" contains five router icons. A red dashed line connects a router on the left (receiving input from **Node 2**) to a router on the right (connected to **Node 1**). A green dashed line also connects the left router to the **End users** below **Node 2**.
+- End users:**
+  - Below **Node 2**, an oval labeled "End users" contains icons of two desktop computers and one laptop. It is connected to the left router in the backbone network by a green dashed line.
+  - Below **Node 1**, an oval labeled "End users" contains icons of two desktop computers, one laptop, and one tablet. It is connected to the right router in the backbone network by a green dashed line. A red dashed line with an arrow points from the right router to this group of users, indicating a failed or degraded connection due to the broken node.
+
+Network diagram showing a broken node (Node 1) and its impact on end users. The diagram includes Resource management, LINP management, Network controller, Node 1, Node 2, a Backbone network, and End users. Node 1 is marked as broken, and its failure is shown affecting the network paths to end users.
+
+F.743.4(17)\_FI.2
+
+Figure I.2 – Use case 2: One node is broken
+
+## Bibliography
+
+- [b-ETSI-GS-NFV001] ETSI GS NFW 001 V1.1.1 (2013), *Network Functions Virtualisation (NFV); Use Cases.*  
+<[http://www.etsi.org/deliver/etsi\\_gs/NFV/001\\_099/001/01.01.01\\_60/gs\\_NFV001v010101p.pdf](http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf)>
+- [b-ETSI-TS-182019] ETSI TS 182 019 V.3.12 (2011), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Content Delivery Network (CDN) Architecture.*  
+<[http://www.etsi.org/deliver/etsi\\_ts/182000\\_182099/182019/03.01.02\\_60/ts\\_182019v030102p.pdf](http://www.etsi.org/deliver/etsi_ts/182000_182099/182019/03.01.02_60/ts_182019v030102p.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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.743.7-201905-I_PDF-E/raw.md b/marked/F/T-REC-F.743.7-201905-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..e0f4d65750a68199875217f7b00059f7efe23ed8
--- /dev/null
+++ b/marked/F/T-REC-F.743.7-201905-I_PDF-E/raw.md
@@ -0,0 +1,391 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.743.7**
+
+(05/2019)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Multimedia services
+
+---
+
+**Requirements for big data-enhanced visual  
+surveillance services**
+
+Recommendation ITU-T F.743.7
+
+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 through it. The letters "ITU" are prominently displayed in blue and red.
+
+ITU logo
+
+International  
+Telecommunication  
+Union
+
+# ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| <b>TELEGRAPH SERVICE</b>                                        |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| <b>MOBILE SERVICE</b>                                           |                    |
+| Mobile services and multidestination satellite services         | F.110–F.159        |
+| <b>TELEMATIC SERVICES</b>                                       |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| <b>MESSAGE HANDLING SERVICES</b>                                | F.400–F.499        |
+| <b>DIRECTORY SERVICES</b>                                       | F.500–F.549        |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | F.600–F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700–F.799</b> |
+| <b>ISDN SERVICES</b>                                            | F.800–F.849        |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | F.850–F.899        |
+| <b>ACCESSIBILITY AND HUMAN FACTORS</b>                          | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## Recommendation ITU-T F.743.7
+
+## Requirements for big data-enhanced visual surveillance services
+
+## Summary
+
+Recommendation ITU-T F.743.7 specifies requirements for visual surveillance enhanced by big data (VSBD) services. It promotes the value of visual surveillance services by using big data analytics method and tools. Massive video, event and sensing data are analysed to support enhanced visual surveillance services, including video retrieval, event detection and status prediction.
+
+Recommendation ITU-T F.743.7 provides application scenarios, service requirements, functional requirements, performance and security requirements for VSBD services.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.743.7  | 2019-05-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/13897">11.1002/1000/13897</a> |
+
+## Keywords
+
+Big data, requirement, visual surveillance.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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..... | 1    |
+| 4 Abbreviations and acronyms .....            | 1    |
+| 5 Conventions .....                           | 1    |
+| 6 Application scenarios.....                  | 2    |
+| 6.1 Intelligent video retrieval .....         | 2    |
+| 6.2 Intelligent event detection .....         | 2    |
+| 6.3 Status prediction .....                   | 2    |
+| 7 Service requirements .....                  | 2    |
+| 7.1 Video retrieval.....                      | 2    |
+| 7.2 Statistical analytics .....               | 3    |
+| 7.3 Behaviour analytics .....                 | 3    |
+| 7.4 Status prediction .....                   | 3    |
+| 7.5 Event analytics.....                      | 3    |
+| 7.6 Data mining and analytics .....           | 3    |
+| 7.7 Import of special analytics model.....    | 4    |
+| 7.8 Visual display .....                      | 4    |
+| 8 Functional requirements .....               | 4    |
+| 8.1 Data collection requirement .....         | 4    |
+| 8.2 Data-processing requirement.....          | 4    |
+| 8.3 Data storage requirement.....             | 5    |
+| 9 Performance requirements .....              | 5    |
+| 10 Security requirements .....                | 5    |
+| Bibliography.....                             | 6    |
+
+
+
+## Recommendation ITU-T F.743.7
+
+## Requirements for big data-enhanced visual surveillance services
+
+# 1 Scope
+
+This Recommendation specifies requirements for big data-enhanced visual surveillance service.
+
+The scope of this Recommendation includes:
+
+- application scenarios;
+- service requirements;
+- functional requirements;
+- performance requirements;
+- security requirements.
+
+# 2 References
+
+None.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following term defined elsewhere:
+
+**3.1.1 visual surveillance** [b-ITU-T F.743]: A telecommunication service focusing on video (but including audio) application technology, which is used to remotely capture multimedia (such as audio, video, image, alarm signals, etc.) and present them to the end user in a friendly manner, based on a managed broadband network with quality, security and reliability ensured.
+
+## 3.2 Terms defined in this Recommendation
+
+None.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+ETL Extract-Transform-Load
+
+ML Machine Learning
+
+PTZ Pan/Tilt Zoom
+
+VSBD Visual Surveillance enhanced by Big Data
+
+# 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 Application scenarios**
+
+## **6.1 Intelligent video retrieval**
+
+It is difficult for traditional video surveillance to retrieve a specific object in massive video data. However, a user can use text, picture or video as input to search in a large number of videos according to the various characteristics of the objects in visual surveillance enhanced by big data (VSBD). Two examples follow.
+
+- a. Using the image of the target person as input, users can quickly search for similar objects in massive videos according to the facial, clothing colour distribution or body features of the image.
+- b. Using characteristic information such as licence plate, vehicle type, colour, brand type or body feature of the target vehicle as input, users can retrieve similar objects in multiple videos with the trajectories displayed.
+
+## **6.2 Intelligent event detection**
+
+VSBD can automatically identify specific events (fire, fake licence plate, etc.) that users are interested in based on various data. The data can be derived from multiple video sources or video and sensor data combinations. The criteria for identifying specific events can be predefined rules or models learned from machine learning (ML).
+
+For example, VSBD can detect a fire disaster by analysing the related real-time videos as well as sensing data from smoke detectors and temperature sensors in areas of concern to users.
+
+## **6.3 Status prediction**
+
+The value of traditional video surveillance data has not been explored. VSBD can effectively exploit the value of historical data. It can extract a large amount of effective information from video surveillance data and be used in many aspects of prediction. For example, according to the data collected by cameras, VSBD can analyse the rules and forecast future traffic flow in order to achieve efficient traffic control.
+
+# **7 Service requirements**
+
+## **7.1 Video retrieval**
+
+### **7.1.1 Object retrieval**
+
+SRV001: VSBD is required to support various conditional retrieval inputs and search objects in massive video data across cameras by different abstract features rapidly.
+
+SRV002: VSBD is required to support continuous video capture for selected objects.
+
+SRV003: VSBD is required to adapt automatically despite scenarios, illumination, camera angles and position.
+
+### **7.1.2 Event retrieval**
+
+SRV004: VSBD is required to support retrieval of the characteristics for particular events, such as people gathering in time and space. A VSDB is required to support the statistics for the selected range of alarm events.
+
+### **7.1.3 Integrated retrieval**
+
+SRV005: VSBD is recommended to support real-time and historical trajectories video retrieval from real-time video and historical database by the conditions of time, space, hot events, features marks and object people or vehicles.
+
+## **7.2 Statistical analytics**
+
+SRV006: VSBD is required to support data collection for vehicle classification, trajectory tracking and monitoring, and registration location.
+
+SRV007: VSBD is required to support data collection of the flow of vehicle or people in certain locations or time periods, and output the alarm information according to the results from big data analytics.
+
+SRV008: VSBD is required to support using big data-processing capabilities to identify suspected fake plate vehicles from the massive licence plate data captured every day.
+
+SRV009: VSBD is required to support identification of trailing vehicles from video data features.
+
+## **7.3 Behaviour analytics**
+
+SRV010: VSBD is required to support people behaviour analytics, such as trajectory reappearance and frequent entry and exit.
+
+SRV011: VSBD is required to support vehicle behaviour analytics, such as fake plate vehicle scanning, first time appearance within the specified range, one vehicle multiple plates, similar licence plate differentiation, frequent overtaking, trajectory reappearance, vehicles travelling together and user-defined collision.
+
+## **7.4 Status prediction**
+
+SRV012: VSBD is required to support the display of different kinds of status predictions, such as the incidence of certain types of criminal case trend prediction, for decision aids through statistical analytics from huge network-wide data.
+
+## **7.5 Event analytics**
+
+SRV013: VSBD is required to find valuable clues from massive historical cases.
+
+SRV014: VSBD is required to support analytics of specific events from a large number of video data and alarm information.
+
+## **7.6 Data mining and analytics**
+
+SRV015: VSBD is required to support the retrieval of system metadata, data mining and analytics function.
+
+SRV016: VSBD is required to support integration of non-video data, mine events correlation and production mode, so as to increase the value of video data.
+
+## **7.7 Import of special analytics model**
+
+SRV017: VSBD is required to support import of the special analytics model that is to computerize, streamline and populate the analytics thinking method and process from the expert manual work and provide a unified interface to system users.
+
+SRV018: VSBD is required to provide methods for analytics to system users to increase the application value of the video surveillance system through encapsulation of the analytics model.
+
+## **7.8 Visual display**
+
+SRV019: VSBD is required to display highly efficient retrieval comparison results.
+
+SRV020: VSBD is required to improve the practicability of the video data by integrated display with a third-party platform, such as the intelligence analytics platform and the emergency processing platform.
+
+# **8 Functional requirements**
+
+## **8.1 Data collection requirement**
+
+### **8.1.1 Real-time data**
+
+FUN001: VSBD is required to support collection of real-time audio and video data from premises units.
+
+FUN002: VSBD is required to support collection of real-time data of pan/tilt zoom (PTZ) control messages.
+
+### **8.1.2 Non-real-time data**
+
+FUN003: VSBD is required to support analysis of events (intrusion, stranded, etc.) and use of the resulting information.
+
+FUN004: VSBD is required to support collection of alarming information.
+
+FUN005: VSBD is recommended to support acquisition and analysis of historical case information databases.
+
+FUN006: VSBD is recommended to support acquisition and use of characteristic image databases (crime picture, etc.).
+
+FUN007: VSBD can optionally support use of digital map information databases.
+
+FUN008: VSBD can optionally support using traffic signal databases.
+
+## **8.2 Data-processing requirement**
+
+Based on computer image-processing technology and image recognition algorithm, a visual surveillance system based on big data application can have the capability to understand and analyse the content of videos or images, generate description information from the content in a structured or semi-structured description language, and provide the basis for video big data analytics and application.
+
+### **8.2.1 Image processing and recognition requirement**
+
+FUN009: VSBD is required to extract key frames from videos and restructure the synthesis of new videos.
+
+FUN010: VSBD is recommended to automatically monitor moving objects in videos, extract object trajectories, and combine them into concentrated videos optimally.
+
+FUN011: VSBD is recommended to unify the format and structures of object information in the video in a timely fashion, and extract important information from objects in the video as the meta-data to save, such as colour, people/car classification and perimeter prevention rules.
+
+### **8.2.2 Parallel computing or distributed processing requirement**
+
+FUN012: VSBD is required to support parallel computing or distributed processing technology, so as to provide real-time batch processing and extract-transform-load (ETL) operations.
+
+## **8.3 Data storage requirement**
+
+FUN013: VSBD is required to support persistent storage and operations for massive data.
+
+FUN014: VSBD is required to support storage of various types of structured data, including image index information, vehicle characteristics, human characteristic information, facial feature information and all kinds of characteristic information for the subject research-analytics.
+
+FUN015: VSBD is required to support the storage of a feature-related object image or video in order to assist display and analytics in characteristic information retrieval processes.
+
+FUN016: VSBD is recommended to support localized storage with external or auxiliary data sources.
+
+# **9 Performance requirements**
+
+PRF001: VSBD is required to support object detection index: minimum detectable object size, detection rate, miss rate, error recognition rate and recognition speed.
+
+PRF002: VSBD is required to support analytical prediction: prediction accuracy, mistaken correlated event rate.
+
+PRF003: VSBD is required to support intelligent analytics of high-throughput real-time video. The average processing and response time is recommended to be less than 1 s.
+
+PRF004: VSBD is required to support parallel analytics of single videos by loading multiple algorithms.
+
+# **10 Security requirements**
+
+SEC001: VSBD is required to support security of the video data itself, including data confidentiality, data integrity and authentication.
+
+SEC002: VSBD is required to support security of data protection including the data security during storage and transmission processes.
+
+# Bibliography
+
+- [b-ITU-T F.743] Recommendation ITU-T F.743 (2009), *Requirements and service description for visual surveillance*.
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.743.8-201905-I_PDF-E/raw.md b/marked/F/T-REC-F.743.8-201905-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..df7585a2f1b8c02dceb6446f71e21d9d8faafed7
--- /dev/null
+++ b/marked/F/T-REC-F.743.8-201905-I_PDF-E/raw.md
@@ -0,0 +1,428 @@
+
+
+International Telecommunication Union
+
+# **ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+# **F.743.8**
+
+(05/2019)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Multimedia services
+
+---
+
+**Requirements for a cloud computing platform  
+supporting a visual surveillance system**
+
+Recommendation ITU-T F.743.8
+
+**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 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 F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| <b>TELEGRAPH SERVICE</b>                                        |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| <b>MOBILE SERVICE</b>                                           |                    |
+| Mobile services and multdestination satellite services          | F.110–F.159        |
+| <b>TELEMATIC SERVICES</b>                                       |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| <b>MESSAGE HANDLING SERVICES</b>                                | F.400–F.499        |
+| <b>DIRECTORY SERVICES</b>                                       | F.500–F.549        |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | F.600–F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700–F.799</b> |
+| <b>ISDN SERVICES</b>                                            | F.800–F.849        |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | F.850–F.899        |
+| <b>ACCESSIBILITY AND HUMAN FACTORS</b>                          | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.743.8
+
+# Requirements for a cloud computing platform supporting a visual surveillance system
+
+## Summary
+
+Recommendation ITU-T F.743.8 specifies the requirements for a cloud computing platform supporting visual surveillance. Cloud computing is an emerging technology aimed at providing various computing services over the Internet. Using virtualization technology, a cloud computing platform realizes a ubiquitous and flexible shared resources pool that can be rapidly provisioned and released with minimal management effort or service-provider interaction based on the needs of users. By using the cloud computing technology, the visual surveillance system can conveniently manage various functional components and services, such as video distribution, video transcoding and intelligent video processing. This Recommendation provides the application scenarios and requirements for a cloud computing platform supporting a visual surveillance system.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.743.8  | 2019-05-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/13898">11.1002/1000/13898</a> |
+
+## Keywords
+
+Cloud computing, requirements, scenarios, visual surveillance.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                                   | 1    |
+| 4 Abbreviations and acronyms .....                                              | 1    |
+| 5 Conventions .....                                                             | 2    |
+| 6 Scenarios.....                                                                | 2    |
+| 6.1 Video distribution.....                                                     | 2    |
+| 6.2 Video transcoding.....                                                      | 2    |
+| 6.3 Online intelligent video processing.....                                    | 3    |
+| 6.4 Offline intelligent video processing .....                                  | 4    |
+| 7 Requirements for cloud computing platform supporting visual surveillance..... | 5    |
+| 7.1 User requirements.....                                                      | 5    |
+| 7.2 Service requirements .....                                                  | 5    |
+| 7.3 Security requirements .....                                                 | 6    |
+| 7.4 Management requirements .....                                               | 7    |
+| 7.5 Scalability requirements .....                                              | 7    |
+| 7.6 Reliability requirements .....                                              | 8    |
+| 7.7 Performance requirements.....                                               | 8    |
+| Bibliography.....                                                               | 9    |
+
+
+
+# Recommendation ITU-T F.743.8
+
+## Requirements for a cloud computing platform supporting a visual surveillance system
+
+# 1 Scope
+
+This Recommendation specifies the application scenarios and requirements for a cloud computing platform supporting a visual surveillance system.
+
+# 2 References
+
+None.
+
+# 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 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.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.
+
+**3.1.4 customer unit** [b-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 mobile customer unit (M\_CU)** [b-ITU-T H.626.1]: Mobile client software installed in a customer's mobile devices. The M\_CU is used to initiate the service and provide customers with video viewing.
+
+**3.1.6 premises unit** [b-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.7 visual surveillance** [b-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 signals, 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:
+
+CU Customer Unit
+
+|      |                                     |
+|------|-------------------------------------|
+| IVS  | Intelligent Visual Surveillance     |
+| MCU  | Mobile Customer Unit                |
+| MSU  | Media Storage Unit                  |
+| PU   | Premises Unit                       |
+| VS   | Visual Surveillance                 |
+| VSCC | Visual Surveillance Cloud Computing |
+
+# 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.
+
+# 6 Scenarios
+
+This clause describes typical scenarios illustrating the cloud computing platform supporting visual surveillance and deriving its service requirements.
+
+## 6.1 Video distribution
+
+The cloud computing platform in a visual surveillance (VS) system can support large-scale real-time video forwarding. For example, many surveillance cameras are deployed in the Great Wall Scenic Area, and the remote monitoring function of the cameras is open to the public. If users wants to see current images of the Great Wall remotely, they can view the network video information on their local devices through the cloud-based real-time video distribution function.
+
+Step 1: Users enter the customer unit (CU) which supports remote live video viewing of the Great Wall Scenic Area, and submit their request to the VS system.
+
+Step 2: After receiving a video-viewing request, the VS system authenticates the user information, and obtains the related information from a video-forwarding function unit that is deployed on the cloud computing platform. The cloud computing platform can dynamically create or destroy the video-forwarding function according to current user requests. The VS system then responds to the CU with the information about the video-forwarding function on the cloud computing platform.
+
+Step 3: After receiving the VS system response, the CU sends a video-viewing request to the cloud computing platform.
+
+Step 4: The cloud computing platform obtains the video stream from the corresponding camera, and then forwards the video stream to the CU.
+
+## 6.2 Video transcoding
+
+The cloud computing platform in a VS system can support video-transcoding functions, e.g., code rate transformation and video format conversion. The traffic department of a city has deployed a large-scale VS system in the city streets with high-definition network cameras. Users want to view the current traffic situation on their way home with their mobile phones. Due to the limited bandwidth of mobile devices and mobile data traffic limits, high-definition surveillance video needs to be transcoded to low-resolution video before forwarding to the CU. The video-transcoding operation can be carried out on the cloud computing platform.
+
+Step 1: Users log into the VS system via their mobile customer unit (MCU), and select the appropriate network camera. The MCU then sends a video-viewing request to the VS system with the video format description.
+
+Step 2: After receiving the video-viewing request, the VS system authenticates the user information, and obtains the related information from a video-forwarding function unit that is deployed on the cloud computing platform. The VS system then responds to the MCU with the information from the video-forwarding function in the cloud computing platform.
+
+Step 3: After receiving the response of the VS system, the MCU sends a video-viewing request to the cloud computing platform.
+
+Step 4: The cloud computing platform obtains the video stream from the corresponding camera. Then, according to the video format description of the MCU, the surveillance video stream is transcoded by the video-transcoding component deployed in the cloud computing platform. The cloud computing platform can dynamically create and destroy the video-forwarding function according to the current requests of the MCU. After that, the transcoded video stream is sent to the MCU.
+
+## **6.3 Online intelligent video processing**
+
+### **6.3.1 Case 1: Traffic flow analysis**
+
+The traffic department of a city has deployed an intelligent visual surveillance (IVS) system for city roads. The system administrator is responsible for operating the IVS system to carry out traffic management tasks. The work of the administrator is to monitor real-time traffic flow of key road sections in the traffic rush hour. A traffic flow analysis function can be developed based on computer vision technology, and is virtualized as functional components in the cloud computing platform. When a user needs to obtain the traffic flow situation of certain road sections, the system can call the traffic flow analysis function to process the relevant surveillance video streams.
+
+Step 1: Users log into the IVS system through the CU. They choose certain surveillance cameras that are deployed on key road sections of interest and set the traffic flow analysis function. They then submit traffic flow analysis requests to the IVS system.
+
+Step 2: After receiving the traffic flow analysis request, the IVS system authenticates the user information, and obtains the relevant information from the traffic flow analysis function that is deployed on the cloud computing platform. The cloud computing platform can dynamically create and destroy the traffic flow analysis function components according to current user requests. The IVS system then responds to the CU with the information from the traffic flow analysis function.
+
+Step 3: After receiving the response of the IVS system, the CU sends the request to the cloud computing platform.
+
+Step 4: The cloud computing platform obtains the relevant video streams from the corresponding cameras, online processes the video streams and then sends the real-time traffic flow analysis results back to the CU.
+
+### **6.3.2 Case 2: Perimeter prevention**
+
+An electricity company uses an IVS system to monitor key power transmission equipment deployed in a city. Surveillance cameras are deployed around the power transmission equipment and the IVS system online analyses the captured surveillance video by calling the perimeter prevention function. Once someone approaches the power transmission equipment, the IVS system generates an alarm message to alert the user to the exception. The perimeter prevention function is virtualized as functional components in the cloud computing platform, and can be dynamically created and destroyed according to current user requests. The working step of the online perimeter prevention scenario is similar to that of the online traffic flow analysis scenario.
+
+## 6.4 Offline intelligent video processing
+
+### 6.4.1 Case 1: Human recognition
+
+A public security department has deployed an IVS system in a city street. The system administrator is responsible for operating the IVS system to carry out public security tasks. When there is a robbery in front of a bank, the administrator reviews the relevant surveillance video captured by the cameras deployed around the bank and obtains a picture of the robber. To find the escape route of the robber as soon as possible, the administrator uses the intelligent human recognition function of the IVS system to process the massive related historical surveillance video. The intelligent human recognition function can be virtualized as functional components in the cloud computing platform and can be dynamically created according to user demand.
+
+Step 1: Users log into the IVS system through the CU. To quickly find robber information in the massive surveillance video data, the user needs to set several functional parameters, such as the camera channel numbers, the time period of interest in the historical video and the picture of the robber, and then sends an intelligent human recognition request to the IVS system.
+
+Step 2: After receiving the human recognition request, the IVS system authenticates the user information, requests the cloud computing platform to create the intelligent human recognition function, and then responds to the CU with the information from the intelligent human recognition function.
+
+Step 3: After receiving the response of the IVS system, the CU sends the request to the cloud computing platform.
+
+Step 4: The cloud computing platform downloads the relevant video files from the media storage unit (MSU), processes the video files in parallel and then sends the human recognition results back to the CU.
+
+Step 5: When the intelligent human recognition task finishes, the cloud computing platform destroys the intelligent human recognition function to release the corresponding resources.
+
+### 6.4.2 Case 2: Video synopsis
+
+The IVS system deployed by a public security department produces massive surveillance video continuously and the cost of data storage is high. However, the public security department is usually interested in moving objects in the surveillance video. Therefore, to save storage space, surveillance video is usually processed to generate synopsis video before long-term storage. The objective of video synopsis is to shorten the video time by reorganizing moving video objects in temporal and spatial dimensions. For example, by using the video synopsis operation, a 24 h surveillance video file is transformed into a 30 min video file that contains all moving objects in the original video file. The intelligent video synopsis function can be virtualized as functional components in the cloud computing platform, and can be dynamically created according to user demand.
+
+Step 1: Users log into the IVS system through the CU, and set several functional parameters of the video synopsis, such as the camera channel numbers, the time period of interest in the historical video and the density of the objects. Then users send an intelligent video synopsis request to the IVS system.
+
+Step 2: After receiving the video synopsis request, the IVS system authenticates the user information, requests the cloud computing platform to create the intelligent video synopsis function and then responds to the CU with the information from the intelligent video synopsis function.
+
+Step 3: After receiving the response of the IVS system, the CU sends the request to the cloud computing platform.
+
+Step 4: The cloud computing platform downloads the relevant video files from the MSU, processes the video files in parallel and then uploads the video synopsis results back to the MSU.
+
+Step 5: When the intelligent video synopsis task finishes, the cloud computing platform destroys the intelligent video synopsis function to release the corresponding resources.
+
+# **7 Requirements for cloud computing platform supporting visual surveillance**
+
+## **7.1 User requirements**
+
+There are two types of user: cloud computing service consumers and cloud computing service providers.
+
+### **7.1.1 Cloud computing service consumer requirements**
+
+- USR-01: A visual surveillance cloud computing (VSCC) platform is required to support registration and de-registration of the end user through the interface provided by the system and the end user can view and modify personal information.
+- USR-02: A VSCC platform is required to support convenient end-user login to and logout from the system. A username and password are required when an end user logs into the system.
+- USR-03: A VSCC platform is recommended to support end-user view of the user access logs or other system logs.
+- USR-04: A VSCC platform is recommended to support real-time surveillance video distribution.
+- USR-05: A VSCC platform is recommended to support the online or offline surveillance video-transcoding function.
+- USR-06: A VSCC platform is recommended to support online or offline intelligent surveillance video analysis functions.
+- USR-07: A VSCC platform is required to support the configuration of computing resources for video surveillance tasks on demand.
+- USR-08: A VSCC platform is required to support the user view of the status of user computing tasks and computing resources.
+
+### **7.1.2 Cloud computing service provider requirements**
+
+- USR-09: A VSCC platform is required to support convenient provider login to and logout from the system. The provider name and password are required when logging into the system.
+- USR-10: A VSCC platform is required to support the provider view of the system operating status from the beginning to now, including the system computing resource occupancy rate, the remaining computing resources of the system, the computing resource occupancy rate of individual users and the remaining computing resources of individual users.
+- USR-11: A VSCC platform is required to support flexible computing resource assignment for individual users.
+
+## **7.2 Service requirements**
+
+### **7.2.1 Online intelligent video processing service requirements**
+
+- SER-01: A VSCC platform is recommended to support online intelligent video processing. The video processing components deployed on a VSCC platform can receive video streams from premises units (PUs) and process the video in real time.
+- SER-02: A VSCC platform is recommended to support online management of video processing tasks, such as creation, pause, restart and deletion.
+- SER-03: A VSCC platform is recommended to view the progress of online video processing tasks.
+
+- SER-04: A VSCC platform is recommended to view the status of resources utilized by online intelligent video processing tasks.
+- SER-05: A VSCC platform is recommended to support the viewing of log files that record the operations of online intelligent video processing tasks.
+
+### **7.2.2 Offline intelligent video processing service requirements**
+
+- SER-06: A VSCC platform is recommended to support offline intelligent video processing. The video processing components deployed on the VSCC platform can download the video files from the MSU and carry out their batch processing.
+- SER-07: A VSCC platform is recommended to support offline management of video processing tasks, such as creation, pause, restart and deletion.
+- SER-08: A VSCC platform is recommended to view the progress of offline video processing tasks.
+- SER-09: A VSCC platform is recommended to view the status of resources utilized by offline intelligent video processing tasks.
+- SER-10: A VSCC platform is recommended to support the viewing of log files that record the operations of offline intelligent video processing tasks.
+
+### **7.2.3 Video transcoding**
+
+- SER-11: A VSCC platform is recommended to support video transcoding. The video-transcoding components deployed on the VSCC platform can receive video streams from PUs and transcode the video in real time. In addition, the video-transcoding components can download video files from the MSU and carry out their transcoding in batches.
+- SER-12: A VSCC platform is recommended to support the management of video-transcoding tasks, e.g., creation, pause, restart and deletion.
+- SER-13: A VSCC platform is recommended to view the progress of video-transcoding tasks.
+- SER-14: A VSCC platform is recommended to view the status of resources utilized by video-transcoding tasks.
+- SER-15: A VSCC platform is recommended to support the viewing of log files that record the operations of video-transcoding tasks.
+
+## **7.3 Security requirements**
+
+### **7.3.1 Authentication security requirements**
+
+- SEC-01: A VSCC platform is required to provide the mechanisms for authentication and authorization, and to permit only authorized users to access the system and use system services. A VSCC platform is required to forbid unauthorized users to handle any system resources.
+
+### **7.3.2 Access security requirements**
+
+- SEC-02: A VSCC platform is required to operate in an environment where network address translation (NAT) or firewall devices are present. It is recommended to utilize specified firewalls, gatekeepers and other network devices to ensure security for access to some special cloud computing services.
+
+### **7.3.3 Content security requirements**
+
+- SEC-03: A VSCC platform is recommended to ensure the security of processed video data, the results of the video processing, etc.
+- SEC-04: A VSCC platform is required to protect user privacy.
+
+### **7.3.4 System security requirements**
+
+- SEC-05: A VSCC platform is required to have the capability to resist various attacks.
+- SEC-06: A VSCC platform is required to provide troubleshooting mechanisms. It is required that a structural single-node problem be avoided (i.e., a problem at a single node should not cause failure of the entire system).
+
+## **7.4 Management requirements**
+
+### **7.4.1 Resources management requirements**
+
+- MAN-01: A VSCC platform is required to support resource management of the cloud computing platform. Resources can be increased and decreased flexibly according to service requests.
+
+### **7.4.2 Equipment management requirements**
+
+- MAN-02: A VSCC platform is required to provide unified management of the computing equipment.
+
+### **7.4.3 Service management requirements**
+
+- MAN-03: A VSCC platform is required to provide various computing service subscription means for users, and to provide the capabilities to query, view and modify their subscription information.
+- MAN-04: A VSCC platform is recommended to provide the capability of accounting, charging and billing for the computing service operation.
+- MAN-05: A VSCC platform is recommended to provide various alternative accounting modes, and to support flexible combination of payment modes, billing modes, billing cycles, preferential pricing, etc.
+
+### **7.4.4 System management requirements**
+
+- MAN-06: A VSCC platform is required to provide a unified system management interface that can be called conveniently.
+- MAN-07: A VSCC platform is required to provide a visual interface for users.
+
+### **7.4.5 Operation management requirements**
+
+- MAN-08: A VSCC platform is required to monitor, record and display the running status of the system.
+- MAN-09: A VSCC platform is required to monitor, record and display usage of cloud computing cluster resources.
+
+## **7.5 Scalability requirements**
+
+- SCA-01: A VSCC platform is required to provide computing resource scalability. When computing equipment is increased or decreased in the system, the computing capacity of the VSCC platform is increased or decreased accordingly, and the system service is uninterrupted.
+- SCA-02: A VSCC platform is required to provide computing resources scalability for users. The computing resources of individual users can be increased or decreased according to each user's demand.
+- SCA-03: A VSCC platform is required to provide user scalability. The number of supported users can be increased or decreased dynamically.
+
+## **7.6 Reliability requirements**
+
+- REL-01: A VSCC platform is required to ensure service reliability. When computing equipment fails or the system network operation is abnormal, the system service can be used normally.
+
+## **7.7 Performance requirements**
+
+- PER-01: A VSCC platform is required to support concurrent user operations. The system can serve a large number of users simultaneously, while ensuring service quality.
+
+## Bibliography
+
+- [b-ITU-T H.626] Recommendation ITU-T H.626 (2011), *Architectural requirements for visual surveillance*.
+- [b-ITU-T H.626.1] Recommendation ITU-T H.626.1 (2013), *Architecture for mobile visual surveillance*.
+- [b-ITU-T M.60] Recommendation ITU-T M.60 (1993), *Maintenance terminology and definitions*.
+- [b-ITU-T Y.3500] Recommendation ITU-T Y.3500 (2014), *Information technology – Cloud computing – Overview and vocabulary*.
+- [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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.743.9-201905-I_PDF-E/raw.md b/marked/F/T-REC-F.743.9-201905-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..1ee0c2266836cae52be02e0bb428dd6caec657be
--- /dev/null
+++ b/marked/F/T-REC-F.743.9-201905-I_PDF-E/raw.md
@@ -0,0 +1,444 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.743.9**
+
+(05/2019)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Multimedia services
+
+---
+
+**Use cases and requirements for a multimedia  
+content delivery network**
+
+Recommendation ITU-T F.743.9
+
+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. 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 F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| <b>TELEGRAPH SERVICE</b>                                        |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| <b>MOBILE SERVICE</b>                                           |                    |
+| Mobile services and multdestination satellite services          | F.110–F.159        |
+| <b>TELEMATIC SERVICES</b>                                       |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| <b>MESSAGE HANDLING SERVICES</b>                                | F.400–F.499        |
+| <b>DIRECTORY SERVICES</b>                                       | F.500–F.549        |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | F.600–F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700–F.799</b> |
+| <b>ISDN SERVICES</b>                                            | F.800–F.849        |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | F.850–F.899        |
+| <b>ACCESSIBILITY AND HUMAN FACTORS</b>                          | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.743.9
+
+# Use cases and requirements for a multimedia content delivery network
+
+## Summary
+
+Recommendation ITU-T F.743.9 illustrates a content delivery network (CDN), and defines use cases for a multimedia CDN in two categories: content delivery and capability, as well as the requirements for a CDN.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.743.9  | 2019-05-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/13899">11.1002/1000/13899</a> |
+
+## Keywords
+
+Multimedia content delivery network, requirement, use case.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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..... | 1    |
+| 4 Abbreviations and acronyms .....            | 1    |
+| 5 Convention.....                             | 2    |
+| 6 Background.....                             | 2    |
+| 7 Use cases.....                              | 3    |
+| 7.1 Content delivery use cases.....           | 3    |
+| 7.2 Capability use cases.....                 | 5    |
+| 8 Requirements .....                          | 5    |
+| 8.1 General requirements.....                 | 5    |
+| 8.2 Service-oriented requirements .....       | 6    |
+| 8.3 Requirement for security .....            | 6    |
+| Bibliography.....                             | 8    |
+
+
+
+# Recommendation ITU-T F.743.9
+
+## Use cases and requirements for a multimedia content delivery network
+
+## 1 Scope
+
+This Recommendation specifies a content delivery network (CDN), and describes use cases for multimedia CDN in two categories: content delivery and capability use cases, as well as the requirements for multimedia CDN.
+
+## 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.5] Recommendation ITU-T F.743.5 (2018), *Framework and interfaces for multimedia content delivery network*.
+
+# 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.
+
+**3.1.2 content delivery network** [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 dynamic content** [ITU-T F.743.5]: Contents created on demand while a user dynamically operates a web application.
+
+**3.1.4 static content** [ITU-T F.743.5]: Content that changes infrequently. This type of content is not changed with the requests of users.
+
+## 3.2 Terms defined in this Recommendation
+
+None.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|     |                          |
+|-----|--------------------------|
+| CDN | Content Delivery Network |
+| IP  | Internet Protocol        |
+| QoE | Quality of Experience    |
+| QoS | Quality of Service       |
+
+# 5 Convention
+
+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.
+
+## 6 Background
+
+Nowadays, the Internet has become an important network infrastructure for delivering content. Because of the best effort nature of the Internet, quality of service (QoS) and quality of experience (QoE) provided by content services are not able to meet consumers' content quality expectations, which is aggravated by the rapid growth of the number of Internet users and Internet content providers. Both content consumers and content providers seek content service QoS and QoE improvements. Meanwhile, traffic related to content services will meet its bandwidth bottleneck of backbone networks and investment in information technology infrastructure by content providers will become greater and greater. Therefore, CDN technology is the most appropriate solution for wide adoption in the current market.
+
+Typically, a CDN consists of functions for content distribution and control, content delivery, content routing and redirection and management. For the high-level framework of multimedia CDN, see clause 8.2 of [ITU-T F.743.5].
+
+A networking sketch of a CDN is shown in Figure 6-1.
+
+![Diagram illustrating a content delivery network (CDN) architecture. A central 'CDN' oval contains 'Content routing', 'Storage and distribution', 'Edge server 1', 'Edge server n', and 'Usage record'. External components include 'Resource server', 'Billing system', 'User 1', and 'User n'. Arrows show data flow: Resource server to Storage and distribution; Storage and distribution to Edge servers; Content routing to Edge servers; Edge servers to Usage record; Usage record to Billing system and Resource server; User 1 and User n to Edge servers.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg)
+
+```
+
+graph TD
+    subgraph CDN
+        CR[Content routing]
+        SD[Storage and distribution]
+        ES1[Edge server 1]
+        ESn[Edge server n]
+        UR[Usage record]
+    end
+    RS[Resource server]
+    BS[Billing system]
+    U1[User 1]
+    Un[User n]
+
+    RS --> SD
+    SD --> ES1
+    SD --> ESn
+    CR --> ES1
+    CR --> ESn
+    ES1 --> UR
+    ESn --> UR
+    UR --> BS
+    UR --> RS
+    U1 --> ES1
+    Un --> ESn
+  
+```
+
+F.743.9(19)\_F6-1
+
+Diagram illustrating a content delivery network (CDN) architecture. A central 'CDN' oval contains 'Content routing', 'Storage and distribution', 'Edge server 1', 'Edge server n', and 'Usage record'. External components include 'Resource server', 'Billing system', 'User 1', and 'User n'. Arrows show data flow: Resource server to Storage and distribution; Storage and distribution to Edge servers; Content routing to Edge servers; Edge servers to Usage record; Usage record to Billing system and Resource server; User 1 and User n to Edge servers.
+
+**Figure 6-1 – Illustration of content delivery network**
+
+Basically, the original content provided by a content provider on the resource server should be ingested into the storage and distribution system first and then be pushed to the edge servers, according to the CDN operator strategy. While an end-user requests specific content, that request would be redirected by the content routing server to a CDN edge server that is close to that end-user and is able to provide a content consumption service. When the content is consumed on the edge server, content usage information will be collected by the usage record server and then transferred to both the billing system handled by the CDN operator and the resource server handled by the content provider.
+
+A CDN can provide services for a single or several content providers. The types of content delivered by a CDN may be static content, dynamic content or a mixture of the two, based on requirements.
+
+## 7 Use cases
+
+## 7.1 Content delivery use cases
+
+#### 7.1.1 Static content delivery
+
+##### 7.1.1.1 Static web page browsing, file downloading and audio/video on demand
+
+In these use cases, a CDN distributes static content from the original server to its edge nodes based on the distribution policy between the content provider and the CDN service provider. When an end-user requests relevant content, the content routing server of a CDN redirects the request to an edge node close to that end-user based on pre-defined strategies and the edge node delivers the content to the end-user.
+
+These use cases are suitable for:
+
+- browsing static content, such as images, words, animations and audio/video content;
+- downloading files, such as articles, electronic books, application software and system software;
+- audio/video on demand, such as movies, TV programmes, music and songs.
+
+##### **7.1.1.2 Content upload**
+
+In this use case, end-users in different locations can upload their own content to the resource servers of one content provider via the nearest edge node selected by the CDN. This use case can accelerate user-generated content upload and distribution.
+
+#### **7.1.2 Dynamic content delivery**
+
+##### **7.1.2.1 Dynamic web content delivery**
+
+In this use case, a CDN chooses the most appropriate transmission path to deliver dynamic content, which is created during the use of an application.
+
+This use case is suitable for, but not limited to, delivery of dynamic content created by a certain application, such as active server pages, hypertext preprocessor pages, Java server pages and Java pages.
+
+##### **7.1.2.2 Live content distribution**
+
+In this use case, live content can be distributed to multiple edge nodes by a CDN, then delivered to a large number of end-users to save the bandwidths of backbone networks and provide better QoE when the multicast network is not available.
+
+This use case is suitable for, but not limited to, movie or music broadcast, live and advertisement broadcast and live text content distribution services.
+
+#### **7.1.3 Mixed content distribution**
+
+The CDN can also provide a distribution service for a mixture of static and dynamic contents. In this case, static content can be distributed and stored in the CDN edge nodes as normal. Dynamic content can be retrieved from its original source by choosing an optimal routing path based on relevant strategies. The CDN then synchronizes dynamic and relevant static contents, displaying them on end-user terminals.
+
+#### **7.1.4 Virtual private content delivery network**
+
+Some content providers or companies may have special requirements for their content distribution, using a private CDN solution within a specific area over a given period of time. They want control and management of the private CDN themselves, without their own CDN solutions.
+
+In this use case, CDN providers can provide virtual private CDNs to their customers by creating certain logical CDN partitions from the entire CDN resource, e.g., a combination of certain CDN hardware and software resources, with sufficient capabilities based on customer demand.
+
+#### **7.1.5 Authentication acceleration**
+
+For security issues, authentication, such as that for a user identifier, needs to be processed by the original resource server, which increases the pressures of processing on that server and backbone networks.
+
+In this use case, relevant authentication can be processed in a CDN, instead of the original resource server, subject to agreement between the CDN and content providers. This solution can accelerate authentication and reduce access pressure on the original resource.
+
+This use case is suitable for, but not limited to, hypertext transfer protocol secure services.
+
+#### **7.1.6 Services across different networks**
+
+In this use case, services provided by a content provider can be accessed by end-users from a CDN across different networks, such as a fixed or mobile network, or the CDNs provided by different CDN operators.
+
+## **7.2 Capability use cases**
+
+#### **7.2.1 Content processing**
+
+In this use case, content processing services, such as image reformation, audio-visual content transcoding, popular content updating and small file converging, are provided by redundant data-processing capabilities within a CDN.
+
+#### **7.2.2 Statistic or monitoring service**
+
+In this use case, a CDN can provide statistical results of content access and report possible safety threats within a period of time by analysing end user access log data, according to content provider requirements. A CDN can also provide report network traffic status to network operators by analysing the network traffic data of their carrier networks, which is collected when it provides content delivery services.
+
+#### **7.2.3 Resource rental services**
+
+In this use case, a CDN is able to store or cache user digital resources in their CDN nodes based on user requirements by using redundant storage resources. This use case includes, but is not limited to, content storage or caching services and pre-located storage or caching services.
+
+# **8 Requirements**
+
+## **8.1 General requirements**
+
+### **8.1.1 Requirements for delivering various types of content**
+
+GR01: A CDN is recommended to have the capabilities of delivering various types of content, such as text, picture, audio-video and cartoon.
+
+GR02: A CDN is recommended to have the capability of delivering static, dynamic or mixed content.
+
+### **8.1.2 Requirements for accessing by multiple types of device**
+
+GR03: A CDN is recommended to have access capabilities by multiple types of device, e.g., personal computer, intelligent mobile device, personal assistant device and television with set top box.
+
+#### **8.1.3 Requirements for supporting multiple protocols**
+
+GR04: A CDN is recommended to have capabilities to support multiple protocols.
+
+### **8.1.4 Requirements for content delivery network service, and node management and maintenance**
+
+GR05: A CDN is recommended to have capabilities to maintain and manage the relevant status of services or nodes, e.g., connection quality and node status.
+
+#### **8.1.5 Requirements for probing the carrier networks**
+
+GR06: A CDN is optionally to have capabilities of probing carrier network performance to improve service quality.
+
+#### **8.1.6 Requirements for content cache or storage**
+
+GR07: A CDN is required to have capabilities to store or cache content within its service coverage area based on a pre-defined storage or cache policy.
+
+#### **8.1.7 Requirements for request routing**
+
+GR08: A CDN is recommended to have capabilities to redirect requests to edge nodes nearby end-users.
+
+CR09: A CDN is recommended to have capabilities to select the most appropriate routing path, such as the best connection quality and shortest path.
+
+## **8.2 Service-oriented requirements**
+
+#### **8.2.1 Requirements for synchronization of mixed content delivery**
+
+SOR01: A CDN is recommended to have capabilities to keep static and dynamic contents synchronous.
+
+### **8.2.2 Requirements for providing virtual private content delivery network**
+
+SOR02: A CDN can optionally have capabilities to insulate a logical partition from CDN resources and to provide a virtual private CDN independently.
+
+#### **8.2.3 Requirements for original authentication acceleration**
+
+SOR03: A CDN can optionally have capabilities to provide an original authentication proxy granted by the original content source based on relevant agreements between the CDN and original content providers.
+
+#### **8.2.4 Requirements for providing services across different networks**
+
+SOR04: A CDN can optionally connect to different networks, such as the fixed and mobile networks, or the CDNs provided by different CDN operators.
+
+#### **8.2.5 Requirements for content processing services**
+
+SOR05: A CDN can optionally have capabilities to transfer the content format from one content processing service to another, e.g., different content coding, size and resolution.
+
+SOR06: A CDN can optionally have capabilities to encrypt content based on content provider demand.
+
+#### **8.2.6 Requirements for statistical analysis services**
+
+SOR07: A CDN can optionally have capabilities to analyse statistically services provided by content providers.
+
+#### **8.2.7 Requirements for the reporting of network performances**
+
+SOR08: A CDN can optionally have capabilities to analyse network performance and to provide statistical performance reports about the networks.
+
+#### **8.2.8 Requirements for providing resource rental services**
+
+SOR09: A CDN can optionally have capability to provide its data storage or caching spaces to consumers.
+
+## **8.3 Requirement for security**
+
+### **8.3.1 Security requirements for contents**
+
+SR01: A CDN is required to provide measures to guarantee consistency of content data when content is delivered from the content resource to the user.
+
+SR02: A CDN is required to provide measures to prevent unauthorized access to the content delivered.
+
+SR03: A CDN can optionally provide a digital rights management service when needed.
+
+#### **8.3.2 Security requirements for components of multimedia content delivery network**
+
+SR04: A CDN is recommended to provide measures to prevent its components from attacking and invading.
+
+SR05: A CDN is recommended to configure redundancy to maintain services if certain components become unavailable.
+
+#### **8.3.3 Security and privacy requirements for user information**
+
+SR06: A CDN is required to provide measures to prevent private user and service provider information of, such as username, password and content consumed, from unauthorized exposure.
+
+## Bibliography
+
+- [b-ITU-T H.780] Recommendation ITU-T H.780 (2012), *Digital signage: Service requirements and IPTV-based architecture.*
+- [b-ITU-T Y.2084] Recommendation ITU-T Y.2084 (2015), *Distributed service networking content distribution functions.*
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.746-201206-I_PDF-E/raw.md b/marked/F/T-REC-F.746-201206-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..1a00b47898dc59bec04fe1be48febcafd78c4c9b
--- /dev/null
+++ b/marked/F/T-REC-F.746-201206-I_PDF-E/raw.md
@@ -0,0 +1,567 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.746**
+
+(06/2012)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Audiovisual services
+
+# --- **Requirements of multimedia optimization control components**
+
+Recommendation ITU-T F.746
+
+![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 F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| <b>TELEGRAPH SERVICE</b>                                        |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| <b>MOBILE SERVICE</b>                                           |                    |
+| Mobile services and multdestination satellite services          | F.110–F.159        |
+| <b>TELEMATIC SERVICES</b>                                       |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| <b>MESSAGE HANDLING SERVICES</b>                                | F.400–F.499        |
+| <b>DIRECTORY SERVICES</b>                                       | F.500–F.549        |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | F.600–F.699        |
+| <b>AUDIOVISUAL SERVICES</b>                                     | <b>F.700–F.799</b> |
+| <b>ISDN SERVICES</b>                                            | F.800–F.849        |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | F.850–F.899        |
+| <b>HUMAN FACTORS</b>                                            | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.746
+
+# Requirements of multimedia optimization control components
+
+## Summary
+
+Recommendation ITU-T F.746 defines multimedia optimization control components (MOCCs), which can provide guidance services to multimedia applications and services in the process of service node selection, traffic optimization, performance enhancement, etc. This Recommendation specifies the MOCC requirements and defines a MOCC functional model. Some typical MOCC deployment scenarios are also described.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group |
+|---------|----------------|------------|-------------|
+| 1.0     | ITU-T F.746    | 2012-06-29 | 16          |
+
+## Keywords
+
+Control component, multimedia applications, multimedia services, optimization.
+
+# 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                       | 1    |
+| 4 Abbreviations.....                                                | 2    |
+| 5 Overview .....                                                    | 2    |
+| 6 Functional architecture .....                                     | 2    |
+| 7 Requirements .....                                                | 4    |
+| 7.1 General requirements.....                                       | 4    |
+| 7.2 MOCC service discovery requirements.....                        | 4    |
+| 7.3 Transport information collection requirements .....             | 5    |
+| 7.4 Interaction and information exchange requirements .....         | 5    |
+| 7.5 Security requirements .....                                     | 5    |
+| Appendix I – MOCC deployment scenarios .....                        | 6    |
+| I.1 MOCC deployment in distributed file share services systems..... | 6    |
+| I.2 MOCC deployment in the streaming services systems .....         | 10   |
+| I.3 MOCC deployment in NAT traversal and media relay .....          | 14   |
+
+
+
+# Requirements of multimedia optimization control components
+
+# 1 Scope
+
+The multimedia optimization control components (MOCCs) defined in this Recommendation are assistance entities which can obtain reliable information from the underlying network. This sort of information can be fed to multimedia applications and services and used as guidance services in the process of service node selection, data traffic optimization and performance enhancement. The MOCC component is located between the multimedia applications and services layer and the network layer. MOCC entities will not be involved in actual data relay and transmission.
+
+The MOCC components can be deployed either in distributed multimedia systems or traditional client-server systems. They can be used in various networks such as NGN [ITU-T Y.2012], internet and other distributed systems.
+
+This Recommendation specifies requirements according to some typical scenarios.
+
+# 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.700] Recommendation ITU-T F.700 (2000), *Framework Recommendation for multimedia services*.
+- [ITU-T F.701] Recommendation ITU-T F.701 (2000), *Guideline Recommendation for identifying multimedia service requirements*.
+- [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 does not use any terms defined elsewhere.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 supernode:** A peer in the overlay network that offers services, including message routing, to other members or clients of the overlay network.
+
+**3.2.2 tracker:** An index server that can assist in the communication between peers in some peer-to-peer file sharing and multimedia systems by collecting information of file replicas and then providing the corresponding information to the resource demanders to initiate a download.
+
+# 4 Abbreviations
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                            |
+|------|--------------------------------------------|
+| AS   | Autonomous System                          |
+| CDN  | Content Delivery Network                   |
+| DOS  | Denial of Service                          |
+| ID   | Identity                                   |
+| IP   | Internet Protocol                          |
+| IPv4 | Internet Protocol version 4                |
+| IPv6 | Internet Protocol version 6                |
+| ISP  | Internet Service Provider                  |
+| MOCC | Multimedia Optimization Control Component  |
+| NAT  | Network Address Translation                |
+| NGN  | Next Generation Network                    |
+| NLRF | Node Location Resolution Function          |
+| P2P  | Peer to Peer                               |
+| PoP  | Point of Presence                          |
+| RASF | Resource Awareness and Statistics Function |
+| TCP  | Transmission Control Protocol              |
+| VoIP | Voice over Internet Protocol               |
+
+# 5 Overview
+
+Due to the evolution of network and multimedia technologies, multimedia services are developing rapidly both on the system scale and on the volume of users, especially for services on the Internet. In contrast with traditional centralized service provision models, more and more services and applications tend to be deployed as distributed models, meaning that the data are transmitted along the paths established among nodes distributed across the whole network. Web content distribution, P2P streaming and P2P file sharing are typical examples of distributed models. For most distributed networks, each node should select one or more service providing nodes from a set of candidates to acquire the desired resources. However, under the end-to-end principle, applications and underlying networks are separated except on the end nodes. Therefore, the "selection" might be random, since the applications may not have the reliable information from transport networks such as topology, congestion status and network address translation (NAT) installation. Sometimes, nodes may cross several network boundaries to fetch the desired resources, thus generating a large amount of costly cross-ISP traffic.
+
+MOCCs defined in this Recommendation are complementary entities that can collect reliable information from the underlying network, analyse it and provide guidance services to the multimedia applications and services (see [ITU-T F.700] and [ITU-T F.701]) in the process of service node selection, data traffic optimization and performance enhancement.
+
+# 6 Functional architecture
+
+Conceptually, multimedia optimization control components are located between the application and service layer and the network layer. The MOCC functional model is illustrated in Figure 1. It is composed of an MOCC server and MOCC clients.
+
+The MOCC server, which resides on the network side, is responsible for collecting and analysing the information from the underlying transport network, and for providing the processed information to multimedia services and applications and to the MOCC client. The MOCC server consists of an entrance component, a node location resolution function (NLRF) and a resource awareness and statistics function (RASF).
+
+![Figure 1 – Functional architecture for multimedia optimization control components. The diagram shows a central 'MOCC server' block containing 'MOCC entrance', 'Node location resolution function (NLRF)', and 'Resource awareness and statistics function (RASF)'. Above it, 'Multimedia services/applications' connect via interface I_a. Below the server, 'Underlying transport networks' connect via interface I_b. To the left, an 'End-user' block contains a 'MOCC client' which connects to the server via interface I_c. To the right, 'Other networks' connect via interface I_d. A thick horizontal line with diagonal hatching separates the server from the underlying transport networks. The label F.746(12)_F01 is in the bottom right corner.](acfc53eca625d62b38aa2563efa95c3e_img.jpg)
+
+Figure 1 – Functional architecture for multimedia optimization control components. The diagram shows a central 'MOCC server' block containing 'MOCC entrance', 'Node location resolution function (NLRF)', and 'Resource awareness and statistics function (RASF)'. Above it, 'Multimedia services/applications' connect via interface I\_a. Below the server, 'Underlying transport networks' connect via interface I\_b. To the left, an 'End-user' block contains a 'MOCC client' which connects to the server via interface I\_c. To the right, 'Other networks' connect via interface I\_d. A thick horizontal line with diagonal hatching separates the server from the underlying transport networks. The label F.746(12)\_F01 is in the bottom right corner.
+
+**Figure 1 – Functional architecture for multimedia optimization control components**
+
+The functions of MOCC server components are as follows:
+
+- **MOCC entrance component:** The MOCC entrance component provides registration and service discovery functions for NLRF, RASF and the MOCC client. NLRF and RASF should register its address, policies, server status and other information with the MOCC entrance component. In order to select the optimum service providing nodes, since there might be multiple MOCC servers in the network, the client should be first authenticated to the MOCC entrance component, which will be responsible for providing the client with the address of the most promising NLRF and RASF. The MOCC entrance component has interfaces with NLRF, RASF, as well as the MOCC clients.
+- **NLRF and RASF:** NLRF and RASF can provide the guidance service or node selection service to applications by collecting and analysing the information of the underlying network. In practice, the NLRF and RASF can be implemented in one physical MOCC server. Network operators can deploy multiple MOCC servers with multiple instances of NLRF and RASF. The information of NLRF and RASF can be maintained by the MOCC entrance component. Some policies may be set for the clients to access NLRF and RASF.
+
+By collecting the information of the underlying network in real time, the MOCC servers could obtain reliable information, such as static topology of the whole network (maintained by NLRF) or dynamic network status (maintained by RASF).
+
+- **Network deployment information:** This information is relatively stable, for example, link capacities, node locations and adjacency relationships of the service nodes, and NAT installations. Furthermore, basic information of the service nodes and some policies enforced by the carriers may also be included in network deployment information. This kind of information is collected and maintained by NLRF.
+- **Network resource status information:** This information includes bandwidth-related data, congestion status of links, etc. This kind of information is more dynamic than network deployment information and can be used as a basis for load balancing and traffic optimization. This kind of information is collected and maintained by RASF.
+
+The MOCC client is embedded in the end user device and is responsible for communicating with the MOCC server to acquire information (through interface  $I_c$  in Figure 1) for multimedia service and application optimization.
+
+Multimedia optimization control components (MOCC server and MOCC client) have interfaces with the multimedia service and application control entities ( $I_a$  in Figure 1), by which the multimedia system can acquire the necessary information from the transport network layer. In addition, those components should have interfaces with the transport network layer ( $I_b$  in Figure 1), through which they can collect and analyse the transport information according to the requirements of the given service.
+
+# 7 Requirements
+
+## 7.1 General requirements
+
+**GEN-110:** The MOCC can be installed on centralized servers, or can be installed on multiple servers across the whole network. In any case, it should provide an interface to multimedia applications and services. The network information provided by the MOCC component should be accurate and reliable.
+
+**GEN-120:** Under the P2P application context, according to the particular mechanism, the MOCC server should be able to be queried by the normal peers as well as by the P2P index servers. MOCCs should be suitable for different P2P systems and protocols, a general interface should be defined between MOCC and those applications.
+
+**GEN-130:** MOCCs should be able to process massive requests from the applications with reasonable and acceptable response time. Specific performance requirements shall be fulfilled. Those requirements may include, amongst others, response time, efficiency, and query precision.
+
+**GEN-140:** MOCCs are independent from specific multimedia systems and they should not have any impact on the implementation and performance of the multimedia services when guidance services are unavailable or MOCC components fail.
+
+**GEN-150:** MOCC services provided by different service providers or network operators should be able to interoperate with one another.
+
+**GEN-160:** Information of the underlying network provided by the MOCC services should be maintained in the local entities of the multimedia system, so as to reduce the network load caused by the frequent queries.
+
+**GEN-170:** MOCCs should have a mechanism to protect the user privacy, some essential network operator information, and sensitive information collected from the bearer networks. It should also have a mechanism to protect themselves against DOS attacks.
+
+## 7.2 MOCC service discovery requirements
+
+**SDR-110:** Public MOCC servers are necessary to help address and policy registration.
+
+**SDR-120:** MOCC clients should be authenticated before attempting to query MOCC servers.
+
+**SDR-130:** MOCC clients should cache the replies from MOCC servers and avoid sending replicated query requests. This method helps lowering the processing burden on the MOCC server caused by the translation from IP addresses to network location identification. However, it should be noted that cache may be unreasonable in mobile scenarios.
+
+**SDR-140:** To clearly define the discovery procedure, specification of discovery interface and corresponding protocol should be standardized.
+
+## **7.3 Transport information collection requirements**
+
+Information of the underlying network that should be collected by MOCC servers includes *inter alia*:
+
+**TIC-110:** Network topology includes network domain, network location properties, neighbourhood relationship, bandwidth between domains, route costs, etc. Network location properties should include network operator name, AS number, PoP, IP prefix, IP address, etc.
+
+**TIC-120:** Alternatives of network operator's traffic engineering policy (network policy).
+
+**TIC-130:** Network static information, such as network capacities, locations and adjacency relationships of the service node and the endpoints, the NAT installations and so on.
+
+**TIC-140:** Network dynamic information, such as the bandwidth-related information, the congestion status of the links and so on.
+
+## **7.4 Interaction and information exchange requirements**
+
+**IIE-110:** Information exchanged between the MOCC client and MOCC server may include information such as access authentication, network location search, network distance search, and network capacity search.
+
+**IIE-120:** In the interaction between MOCC client and MOCC entrance, the MOCC client sends a request including information about itself such as identification or IP address to MOCC server; MOCC entrance replies one or more MOCC server's address to the authorized client.
+
+**IIE-130:** In the interaction between MOCC server and MOCC entrance, the MOCC entrance should have MOCC server's address and policies information; this should be controlled by the network operator. MOCC entrance should be able to query the MOCC server's status, including busy, failure, and normal.
+
+**IIE-140:** Within the MOCC server, interaction of information includes transport network information synchronization and client request forwarding.
+
+## **7.5 Security requirements**
+
+**SEC-110:** MOCC server should keep the network information and content secret, and it should take measures to protect the privacy of the MOCC client end users.
+
+**SEC-120:** Appropriate methods should be deployed to prevent attacks targeted at MOCC servers.
+
+**SEC-130:** An authentication mechanism should be used between the MOCC server and network operator in order to establish a trust relationship between these two entities.
+
+# Appendix I
+
+## MOCC deployment scenarios
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### I.1 MOCC deployment in distributed file share services systems
+
+#### I.1.1 General description
+
+Distributed file sharing applications are very common in the Internet and have developed rapidly in recent years. Their prominent advantages are high efficiency and reliability because the services and resources are distributed across the whole network so that each peer can acquire different file replicas from multiple candidates. Therefore, file exchanging is becoming more flexible than before. Among these file sharing systems, the most prevalent method is to use P2P overlay technologies to implement file sharing applications amongst the peers in networks. Depending on whether the P2P overlay network is used for control message propagation or for data transmission, the P2P file sharing systems can be classified into two categories.
+
+**Category A:** In the first category, the P2P overlay network is only used for control message propagation: Namely, search and response messages are propagated along paths in this overlay network. However, once the search results are available, real data transmission occurs directly between the peers on the underlying physical network, regardless of the overlay network. In this category, searching is the most important architectural issue. According to the different search mechanisms, we can further divide the distributed file-sharing systems in this category into three subtypes:
+
+- **Centralized directory model:** This means that all the files or resources are indexed in a centralized server or a handful of centralized servers.
+- **Fully decentralized model:** This means that all the directory services and resources are fully decentralized on every peer of the whole network. Distributed search algorithms often use flooding query method to look for file information.
+- **Hybrid model:** This is the combination of the above two types. One implementation is to divide the peers in the network into several groups, and in each group, the node with good performance and high bandwidth will be selected as the directory server, which is typically called a supernode. It is responsible for the maintenance of the whole directory of the group and connects to other supernodes from the overlay network being used for searching.
+
+**Category B:** In the second category, the peers form a cooperative overlay network for data exchange. Data blocks are transmitted along paths in this overlay network.
+
+On the application side, deployment of the MOCC functionalities may happen at different levels. For example, in a completely decentralized network, selection of the best sources is totally up to the user. In Category B P2P systems, central elements such as trackers or servers act as mediators. Therefore, in the former case, improvement would require modification in applications, while in the latter case, it could be implemented just in some central elements. The following clause presents and analyses the scenarios using the different file sharing system types.
+
+#### I.1.2 Scenario 1: Centralized or hybrid model
+
+**Description:** The scenario in Figure I.1 fits within either the centralized or the hybrid model, in which the centralized index server or the supernode can serve as mediator for the end users. User A wants to download a resource R. In this scenario, it assumes that the centralized server or the supernodes only provide the index service to the nodes, which won't provide any policies regarding the traffic optimization to the users.
+
+**Pre-condition:** A number of copies of resource R are scattered in the network. In the centralized model, all the resources are indexed in the centralized server. In the hybrid model, the supernode indexes all the resources located in directly connected non-supernode peers. The centralized server or all the supernodes are authorized to use the MOCC service. NLRF and RASF have already been registered to the MOCC entrance component, which has created the corresponding records in turn.
+
+![Figure I.1 – File sharing systems scenario using MOCC service. The diagram is divided into two parts: (a) Centralized model and (b) Hybrid model. Both parts show a 'Service/application stratum' at the top containing 'MOCC entrance', 'NLRF', and 'RASF' components. Below this is a 'Bearer network information' cloud. In (a), a 'Centralized server' is connected to the cloud and three 'User' nodes. In (b), three 'Supernode' nodes are connected to the cloud, each connected to one or more 'User' nodes. Arrows indicate data flow between the strata and the network information cloud, and between the cloud and the servers/supernodes.](4e4be0bd8b235167902f2c03e41da651_img.jpg)
+
+Figure I.1 – File sharing systems scenario using MOCC service. The diagram is divided into two parts: (a) Centralized model and (b) Hybrid model. Both parts show a 'Service/application stratum' at the top containing 'MOCC entrance', 'NLRF', and 'RASF' components. Below this is a 'Bearer network information' cloud. In (a), a 'Centralized server' is connected to the cloud and three 'User' nodes. In (b), three 'Supernode' nodes are connected to the cloud, each connected to one or more 'User' nodes. Arrows indicate data flow between the strata and the network information cloud, and between the cloud and the servers/supernodes.
+
+(a) Centralized model
+
+(b) Hybrid model
+
+F.746(12)\_FI.1
+
+**Figure I.1 – File sharing systems scenario using MOCC service**
+
+In this scenario:
+
+- 1) The centralized server or supernodes send the MOCC matching request to the MOCC entrance component, which includes the addresses of the centralized server or the supernodes. On receiving the requests, the MOCC entrance component will then authenticate them to identify if they are legal clients.
+- 2) After the authentication, the MOCC entrance component will look up for the authorized MOCC servers (RASF, NLRF) for the centralized server or supernodes and then send the addresses and server information in the response messages to the centralized server or supernodes.
+- 3) Upon receiving the messages, the server or the supernodes will cache those MOCC servers' information and then send the access request to the MOCC servers including their addresses and other authentication information until the authentication is succeeded.
+- 4) A user sends a search request to a centralized index server or its responsible supernode, say S.
+- 5) S executes the search (either searches a centralized database in case of the centralized model or initiates a search among the supernodes in the case of the hybrid model) and obtains the list of nodes that can satisfy the search request.
+- 6) S sends the transport network statistics query request to NLRF or RASF including the list of nodes mentioned above as well as the requesting node.
+- 7) NLRF or RASF ranks the list of nodes based on its knowledge of the carrier network status and returns the ranked list of nodes to S.
+
+- 8) S can return the ranked list of nodes to the requesting user or, alternatively, can choose the top ranked K nodes to return to the user.
+- 9) The user uses the ranked list of nodes to initiate the real file downloading. The user can request different ranges from different nodes to boost the downloading speed.
+
+#### I.1.3 Scenario 2: Decentralized scenario
+
+**Description:** The scenario in Figure I.2 illustrates the fully distributed file sharing system model, in which all resources are distributed in every peer of the whole network.
+
+**Pre-condition:** A number of copies of resource are scattered in the network. There is no centralized indexing server to index the resources. User A wants to download a resource R. All or a part of the users are authorized to use the MOCC service. NLRF and RASF have already been registered to the MOCC entrance component, which has created the corresponding records in turn.
+
+![Diagram of Figure I.2 showing the file sharing system scenario using MOCC service in the fully distributed model. The diagram is divided into three horizontal layers. The top layer, 'Service/application stratum', contains a 'MOCC entrance' box connected by a double-headed arrow to a dashed box containing 'NLRF' and 'RASF' boxes. The middle layer is a cloud labeled 'Bearer network information', connected to the top layer by double-headed arrows. The bottom layer shows five 'User' icons (laptops) connected to the 'Bearer network information' cloud. A small label 'F.746(12)_FI.2' is at the bottom right.](bd671b21db63e6fdb2196e9b18502aac_img.jpg)
+
+Diagram of Figure I.2 showing the file sharing system scenario using MOCC service in the fully distributed model. The diagram is divided into three horizontal layers. The top layer, 'Service/application stratum', contains a 'MOCC entrance' box connected by a double-headed arrow to a dashed box containing 'NLRF' and 'RASF' boxes. The middle layer is a cloud labeled 'Bearer network information', connected to the top layer by double-headed arrows. The bottom layer shows five 'User' icons (laptops) connected to the 'Bearer network information' cloud. A small label 'F.746(12)\_FI.2' is at the bottom right.
+
+**Figure I.2 – File sharing systems scenario using MOCC service in the fully distributed model**
+
+In this scenario:
+
+- 1) The user sends the MOCC matching request to the MOCC entrance component, which includes its address, etc. On receiving the request, the MOCC entrance component will then authenticate the user to identify if they are legal clients.
+- 2) After the authentication, the MOCC entrance component will look up for the authorized MOCC servers (RASF, NLRF) for the user, and then send the addresses and server information in the response messages to the user.
+- 3) Upon receiving the messages, the user will cache those MOCC servers' information and then send the access request to the MOCC servers, which include its address and other authentication information until the authentication is succeeded.
+- 4) The user initiates a search request to the system.
+- 5) The system returns a list of nodes that can satisfy the search request to the user.
+- 6) The user sends the transport network statistics query request to NLRF or RASF, including the list of nodes mentioned above.
+- 7) NLRF or RASF ranks the list of nodes based on its knowledge of the carrier network status, and returns the ranked list of nodes to the user.
+- 8) The user uses the ranked list of nodes to initiate the real file downloading. The user can request different ranges from different nodes to accelerate the downloading speed.
+
+#### I.1.4 Scenario 3: P2P with real data exchange among peers
+
+**Description:** The scenario in Figure I.3 illustrates file downloading in P2P system with data exchange among peers. User 1 is looking for the "seed" for a particular movie in this kind of P2P network. Trackers 1 and 2 are connected to the MOCC service. Since the algorithms and mechanisms vary in different kinds of hybrid file sharing systems, the tracker capabilities in those systems are diversified. This scenario assumes that Trackers 1 and 2 only provide the collection and index services to the nodes, which will not provide any policies regarding the traffic optimization to the users.
+
+**Pre-condition:** The "seed" (.torrent) file has been already published and the file information has been registered in Trackers 1 and 2. Trackers 1 and 2 are responsible for the maintenance of status of all the peers in its group and nodes-selection of the given resources. All the trackers in Category B P2P system are authorized to use the MOCC service. NLRF and RASF have already registered with the MOCC entrance component, which has in turn created the corresponding records. Trackers 1 and 2 are authorized to use the MOCC services to optimize their node selection.
+
+![Diagram illustrating the file sharing application optimization scenario using MOCC services. The diagram shows a hierarchy of components: at the top, a 'MOCC entrance' box is connected to a dashed box containing 'NLRF' and 'RASF' components. This dashed box is connected to a 'Bearer network information' box. Below the MOCC entrance, 'Tracker 1' and 'Tracker 2' are shown as server icons. Both trackers have bidirectional arrows connecting them to the MOCC entrance. 'User 1' is shown as a client icon connected to 'Tracker 1'. There are also icons representing other peers connected to both 'Tracker 1' and 'Tracker 2'. A label 'F.746(12)_Fl.3' is present in the bottom right corner of the diagram area.](7efae06af3af43ffe5d4b956a679cf54_img.jpg)
+
+Diagram illustrating the file sharing application optimization scenario using MOCC services. The diagram shows a hierarchy of components: at the top, a 'MOCC entrance' box is connected to a dashed box containing 'NLRF' and 'RASF' components. This dashed box is connected to a 'Bearer network information' box. Below the MOCC entrance, 'Tracker 1' and 'Tracker 2' are shown as server icons. Both trackers have bidirectional arrows connecting them to the MOCC entrance. 'User 1' is shown as a client icon connected to 'Tracker 1'. There are also icons representing other peers connected to both 'Tracker 1' and 'Tracker 2'. A label 'F.746(12)\_Fl.3' is present in the bottom right corner of the diagram area.
+
+**Figure I.3 – File sharing application optimization scenario using MOCC services**
+
+In this scenario:
+
+- 1) Trackers 1 and 2 send the MOCC matching request to the MOCC entrance component, which includes the Tracker ID, addresses, etc. On receiving the requests, the MOCC entrance component will try to authenticate those trackers to identify if they are legal clients.
+- 2) After the authentication, the MOCC entrance component will look up for the authorized MOCC servers (RASF, NLRF) for those trackers, and then send the addresses and server information in the response messages to the trackers.
+- 3) Upon receiving the messages, Tracker 1 and 2 will cache that MOCC server information and then send an access request to the MOCC servers until the authentication is successful. The access request includes tracker ID, address and other authentication information.
+- 4) User 1 gets one "seed" (.torrent) of the movie, which includes the available tracker information. User 1 sends the connect attempts to those trackers on the list one by one until one successful connection has been established between it and a tracker, say Tracker 1.
+- 5) Corresponding to the given movie, Tracker 1 retrieves a huge list of candidate peers, which are recorded storing one or more replicas. In the normal Category B P2P operation, the tracker will send the list to User 1, who will then randomly choose some of the candidate peers. However, with the aid of the MOCC server, that selection can be optimized.
+
+- 6) Tracker 1 will send the transport network statistics query request, which includes the information of those candidate peers. The type of request can be one or a combination of: network location query request, network distance query request and network resources status query request. Those requests are preceded by NLRP and RASP, respectively.
+- 7) According to the different query requests, NLRP and RASP will then inquire about the bearer network information services, which can be implemented by the MOCC itself or can be provided by some practical entities such as RACF. In some cases, within certain policy boundaries, network information services can be provided by the network operators.
+- 8) MOCC servers send the results to the trackers to initiate the node selection optimization.
+- 9) The tracker sends the optimized node list to User 1.
+- 10) User 1 will send a TCP connect request to the nodes on the list. After successful connections have been established, a handshake procedure will be performed among those peers. After that, those peers use "interested", "not interested", "choke", "unchoke" to exchange the attitude of resource sharing.
+- 11) The Category B P2P file transfer begins.
+- 12) The TCP connections tear down among the peers after the file has been fully downloaded.
+
+### I.2 MOCC deployment in the streaming services systems
+
+#### I.2.1 General description
+
+The conventional centralized client/server-based streaming media system has some inherent limitations that make it impossible to be widely deployed, such as server performance bottleneck and single point of failure. Comparing to the client/server-based system, streaming media systems based on distributed content delivery networks can somehow improve the service capability. However, there are still issues (such as expensive hardware deployment, high bandwidth cost and complicated device management and scalability) that add to the complexity and cost of implementations.
+
+Another radical way to improve the scalability of the streaming services is based on P2P technology. However, systems based on P2P-based streaming services cannot guarantee user experience. Factors include long start-time, topology inconsistency, instability induced by fast user turn-over ("churn") and NAT-deployment issues.
+
+The deployment of MOCC in P2P networks is to some extent helpful for solving those inherent problems. For example, RASP can record every resource contained by the node and NLRP can give the location information about the resource requested by any node.
+
+#### I.2.2 Scenario for P2P streaming media systems
+
+P2P file sharing systems have become common in the Internet. P2P technologies bring revolutionary changes to the network content distribution model and make it possible that the comprehensive streaming media applications become practical in the Internet.
+
+P2P streaming media systems use P2P technologies to alleviate the server load and optimize the service capability. Based on the type of data distribution method, most of the P2P streaming systems can be classified into two subtypes:
+
+- **Tree-based system:** This kind of P2P streaming system implements a tree-based content distribution, and the tree is in the application layer and rooted at the content sources. In principle, each node receives data from a parent node, which might be the source or a peer. If peers do not change frequently, then the systems require little message overhead since the packets are forwarded from node to node without the need for extra messages. However, in high-churn environments (i.e., fast turnover of peers in the tree), the tree must be continuously destroyed and rebuilt, which produces considerable control message overhead.
+
+- **Mesh-based system:** In this kind of P2P streaming system, each node contacts a subset of peers to obtain a number of chunks. Every node needs to know which chunks are owned by its peers and explicitly "pulls" the chunks it needs. This type of scheme involves overhead, due in part to the exchange of buffer maps between nodes (i.e., nodes advertise the set of chunks they have) and in part to the "pull" process (i.e., each node sends a request to receive the chunks). Each node relies on multiple peers to retrieve content and as a consequence mesh-based systems offer good resilience to node failure.
+
+Both tree-based and mesh-based systems have advantages in particular scenarios, but neither can completely overcome the challenges of the dynamic peer-to-peer environments. A strong advantage for mesh-based systems is their simplicity, but they have a trade-off between overhead and latency: if nodes choose to send notifications upon every segment arrival, then the overhead will increase; on the other hand, periodic notifications containing buffer maps reduce the overhead but increase latency. A tree-based system does not suffer from this trade-off, but has to face the inherent instability of dynamic environments and bandwidth underutilization.
+
+The deployment of MOCC in P2P streaming media systems can make the node acquire the information about the overlay network and its neighbours, which is useful to determine the status of the network and the correlative peers so as to make the right data schedule and relationship selection.
+
+##### **1.2.2.1 Scenario for tree-based systems**
+
+Tree-based systems have well-organized overlay structures (typically trees) for delivering data, with each data packet being disseminated using the same structure. Nodes on the structure have well-defined relationships, such as "parent-child" relationships in trees. Tree-based systems are typically push-based, i.e., when a node receives a data packet, it also forwards the copies of the packet to each of its children. Since all data packets follow this structure, it becomes critical to ensure that the structure is optimized to offer good performance to all receivers. Furthermore, the structure must be well-maintained, as nodes randomly join and leave the group. In particular, if a node crashes or otherwise stops performing adequately, all of its children in the tree will stop receiving packets, and the tree must be repaired. In addition, loop avoidance is an important issue that must be addressed when constructing tree-based structures in the streaming services system.
+
+**Description:** The scenario in Figure I.4 illustrates a tree-based system in which there is an application layer streaming tree with ten peers. In this scenario, it assumes that there are two peers at level 1 and receiving video directly from the server, four peers at level 2 receive video from their parents at level 1, and three of them forward received video to four peers at the bottom level.
+
+![Figure I.4: Tree-based system scenario using MOCC service with a single application layer multicast tree. The diagram shows a 'Service/application stratum' at the top containing 'MOCC entrance', 'NLRF', and 'RASF'. Below it is a 'Bearer network' cloud. A 'Server' is connected to the bearer network and to 'Peer 0'. 'Peer 0' is connected to 'Peer 2' and 'Peer 3'. 'Peer 2' is connected to 'Peer 6' and 'Peer 7'. 'Peer 3' is connected to 'Peer 8'. 'Peer 8' is connected to 'Peer 4'. 'Peer 4' is connected to 'Peer 1'. 'Peer 1' is connected to 'Peer 5'. 'Peer 5' is connected to 'Peer 9'. A thick orange line represents the multicast tree path: Server -> Peer 0 -> Peer 2 -> Peer 6 -> Peer 7 -> Peer 3 -> Peer 8 -> Peer 4 -> Peer 1 -> Peer 5 -> Peer 9. Peer 0 is circled in blue, and Peer 8 is circled in green. The label 'F.746(12)_FI.4' is at the bottom right.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg)
+
+Figure I.4: Tree-based system scenario using MOCC service with a single application layer multicast tree. The diagram shows a 'Service/application stratum' at the top containing 'MOCC entrance', 'NLRF', and 'RASF'. Below it is a 'Bearer network' cloud. A 'Server' is connected to the bearer network and to 'Peer 0'. 'Peer 0' is connected to 'Peer 2' and 'Peer 3'. 'Peer 2' is connected to 'Peer 6' and 'Peer 7'. 'Peer 3' is connected to 'Peer 8'. 'Peer 8' is connected to 'Peer 4'. 'Peer 4' is connected to 'Peer 1'. 'Peer 1' is connected to 'Peer 5'. 'Peer 5' is connected to 'Peer 9'. A thick orange line represents the multicast tree path: Server -> Peer 0 -> Peer 2 -> Peer 6 -> Peer 7 -> Peer 3 -> Peer 8 -> Peer 4 -> Peer 1 -> Peer 5 -> Peer 9. Peer 0 is circled in blue, and Peer 8 is circled in green. The label 'F.746(12)\_FI.4' is at the bottom right.
+
+**Figure I.4 – Tree-based system scenario using MOCC service with a single application layer multicast tree**
+
+**Pre-condition:** The video files are sent along the established tree for the server to the last level peer. In this scenario, every peer will periodically send its overlay information to RASF, which includes next level peers, upper level peers, multicast tree ID, upload and download bandwidth, level ID, etc. The server or all the tree member peers are authorized to use the MOCC service. NLRF and RASF have already been registered to the MOCC entrance component, which has created the corresponding records in turn.
+
+In this scenario:
+
+- The MOCC servers are distributed in the network; therefore, each node who wants to use the MOCC functions should get access to the corresponding ones for the topologies information querying.
+- Together with the server, users belonging to the same session form an application-level multicast tree which is called a base tree, and the whole video file contained by the server is called a base stream. The members of the base tree periodically send the necessary information to MOCC entities, such as its parent and children, bandwidth, base stream information, etc. to renew the topology-related information for each one. When a new client wants to join the tree, for example, Peer 8, it will query the MOCC servers on the most suitable tree member (using some parent selection algorithm), and then it will join this tree.
+- Furthermore, if e.g., Peer 0 wants to leave the tree, it can send notification to the MOCC servers, in turn, the MOCC entities will notify Peer 0's parent and children and start to direct the repair for the tree.
+
+##### I.2.2.2 Scenario for mesh-based systems
+
+In a mesh-based P2P streaming system as illustrated in Figure I.5, peers are not confined to a comparative static topology. Instead, the peer relationships are established or terminated based on the content availability and bandwidth availability on peers. In the mesh-based structure, peers will dynamically connect to a subset of random peers in the system and will periodically exchange information about their data availability. Video content is pulled by a peer from its neighbours who have already obtained the content. Since multiple neighbours are maintained at any given moment,
+
+mesh-based video streaming systems are highly robust to peer churns. However, users may suffer from video playback quality degradation ranging from low video bit rates, long start-up delays, to frequent playback freezes because different data packets may traverse different routes to reach the users (this will also make it difficult to predict the variation of dynamic peer relationships).
+
+**Description:** Similar to P2P file sharing systems like Category B P2P, a mesh streaming system has a tracker to keep track of the active peers in the video session. Trackers 1 and 2 are all connected to the MOCC service. In this scenario, Trackers 1 and 2 provide index service for peers.
+
+**Pre-condition:** The video file has been already published and the file information has been registered in Trackers 1 and 2. Trackers 1 and 2 are responsible for the track of status of all the peers in its group and nodes-selection of the given resources. All the trackers in this system are authorized to use the MOCC service. NLRF and RASF have already registered to the MOCC entrance component, which have created the corresponding records in turn. Trackers 1 and 2 are authorized to use the MOCC services to optimize their nodes selection.
+
+![Diagram of a mesh-based system using MOCC service. The diagram is divided into three horizontal layers. The top layer, 'Service/application stratum', contains a 'MOCC entrance' box connected to a dashed box containing 'NLRF' and 'RASF' boxes. The middle layer is a cloud labeled 'Bearer network'. The bottom layer shows two trackers, 'Tracker 1' and 'Tracker 2', connected to each other and to the 'MOCC entrance' via the 'Bearer network'. Tracker 1 is connected to four peers: 'Peer 0', 'Peer 1', 'Peer 2', and 'Peer 3'. Tracker 2 is connected to four peers: 'Peer 4', 'Peer 5', 'Peer 6', and 'Peer 7'. Peers 0, 1, 2, and 3 are interconnected in a mesh. Peers 4, 5, 6, and 7 are also interconnected in a mesh. A label 'F.746(12)_FI.5' is present near Peer 6.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg)
+
+Diagram of a mesh-based system using MOCC service. The diagram is divided into three horizontal layers. The top layer, 'Service/application stratum', contains a 'MOCC entrance' box connected to a dashed box containing 'NLRF' and 'RASF' boxes. The middle layer is a cloud labeled 'Bearer network'. The bottom layer shows two trackers, 'Tracker 1' and 'Tracker 2', connected to each other and to the 'MOCC entrance' via the 'Bearer network'. Tracker 1 is connected to four peers: 'Peer 0', 'Peer 1', 'Peer 2', and 'Peer 3'. Tracker 2 is connected to four peers: 'Peer 4', 'Peer 5', 'Peer 6', and 'Peer 7'. Peers 0, 1, 2, and 3 are interconnected in a mesh. Peers 4, 5, 6, and 7 are also interconnected in a mesh. A label 'F.746(12)\_FI.5' is present near Peer 6.
+
+**Figure I.5 – Scenario of the mesh-based system using MOCC service**
+
+In this scenario:
+
+- The MOCC servers are distributed in the network; therefore, each tracker who wants to use the MOCC functions should get access to the corresponding ones for the topologies information querying.
+- When one peer (for example Peer 3) joins the streaming session, Tracker 1 can query the network statistics information from the MOCC servers, which can be one or a combination of: network locations, network distance, network resources status query, etc. Tracker 1 then accordingly makes optimized active peers selections with the aid of the topologies information NLRF & RASF have been provided. After receiving an initial list of active peers, Peer 3 tries to make connections to some remote peers on the list and, after obtaining enough neighbours, Peer 3 will then start to exchange video content with its neighbours.
+
+### I.3 MOCC deployment in NAT traversal and media relay
+
+#### I.3.1 General description
+
+Many real-time communication services are using the distributed model, which can allow the users to establish direct media flows such as video, audio, text, etc. Unlike the client-server model, every host in a P2P network can act at the same time as server and client, and its peers are more or less equal. Therefore, the main problem for P2P applications in a NAT environment is that NATed peers are usually not reachable for arbitrary peers. Unsolicited connection requests from outside are denied by the NAT device because the requests are sent to the public internet address of the gateway and the NAT device has no clue to which internal address the request should be forwarded.
+
+![Diagram illustrating MOCC deployment in a hierarchical NATed environment. The diagram shows a hierarchy of NAT devices (NAT1 to NAT5) connected to the Internet. NAT1 is the root NAT with a public IP 202.112.100.100. NAT2, NAT3, NAT4, and NAT5 are connected to NAT1. Various nodes (Node A, Node B, Node C, Node D) and users (User A, User B, User C, User D) are connected to these NATs. A 'MOCC entrance' is connected to the Internet via 'NLRF' and 'RASF' components. A 'Bearer network information' box is shown in the Internet cloud. An inset on the right shows a list of NATs and their associated users: Node C (NAT3, USER = {User D}), Node D (NAT1, USER = {}), Node A (NAT2, USER = {}), Node B (NAT5, USER = {}), and NAT4 (USER = {User A, User C}).](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg)
+
+The diagram illustrates a hierarchical NAT environment. At the top, the Internet cloud contains a 'Bearer network information' box. Below it, NAT1 (public IP 202.112.100.100) is connected to the Internet. NAT1 has three internal interfaces: 10.10.1.\* connected to NAT2, 10.10.1.103 connected to NAT3, and 192.168.1.2 connected to NAT4. NAT2 (internal IP 10.10.1.100) is connected to Node D (internal IP 192.168.1.\*). NAT3 (internal IP 10.10.1.102) is connected to Node C (internal IP 172.24.1.\*). NAT4 (internal IP 192.168.1.1) is connected to Node A (internal IP 10.10.1.\*), User A, and User C. NAT5 (internal IP 10.10.1.\*) is connected to User D and Node B (internal IP 10.10.1.\*). A 'MOCC entrance' is connected to the Internet via 'NLRF' and 'RASF' components. An inset on the right shows a list of NATs and their associated users:
+
+- Node C: (NAT3, USER = {User D})
+- Node D: (NAT1, USER = {})
+- Node A: (NAT2, USER = {})
+- Node B: (NAT5, USER = {})
+- NAT4: (USER = {User A, User C})
+
+Diagram illustrating MOCC deployment in a hierarchical NATed environment. The diagram shows a hierarchy of NAT devices (NAT1 to NAT5) connected to the Internet. NAT1 is the root NAT with a public IP 202.112.100.100. NAT2, NAT3, NAT4, and NAT5 are connected to NAT1. Various nodes (Node A, Node B, Node C, Node D) and users (User A, User B, User C, User D) are connected to these NATs. A 'MOCC entrance' is connected to the Internet via 'NLRF' and 'RASF' components. A 'Bearer network information' box is shown in the Internet cloud. An inset on the right shows a list of NATs and their associated users: Node C (NAT3, USER = {User D}), Node D (NAT1, USER = {}), Node A (NAT2, USER = {}), Node B (NAT5, USER = {}), and NAT4 (USER = {User A, User C}).
+
+Figure I.6 – Illustration of MOCC deployed in the hierarchical NATed environment
+
+On the other hand, the peer-selecting methods in some P2P algorithms are somewhat random, which does not take the topology issues into consideration. This is especially the case when there are many NAT devices in the network and it is hard to get accurate estimation of those NATed peers connected to the Internet. Therefore, it might happen that in some systems the traffic is iteratively routed or takes a detour in case of the same-root NAT.
+
+In a general sense, the network resource controlled by one single NAT is within the boundary from its internal interface to the external interface of the lower-level NAT connected to it. There are no other NAT devices within this area, which is defined as the current network in this Recommendation. Regarding one NAT, the upper-level network, current network and lower-level network can be regarded as the directed edges, which compose the topology of the multi-level NATs deployment in a network. The NAT device whose external interface was configured with the global unique public address is called the root NAT (NAT1) as shown in Figure I.6. Along the edge, if there is one path from NAT1 to NAT2, then NAT1 can be called the same-root upper level NAT
+
+of NAT2; and meanwhile if there is another path from NAT1 to NAT3, then NAT2 and NAT3 are called same-root NAT to one another.
+
+According to the ownership of the NAT devices, the same-root NAT scenario can be divided into the following three categories:
+
+**Scenario 1:** In this scenario, all the NAT devices are deployed and maintained by the network operators, and the end users are not allowed to connect their own NATs to the network. One example of this scenario is the enterprise network.
+
+**Scenario 2:** In this scenario, there is one or more same-root NAT deployed, among which the lowest-level NATs are deployed by some users at liberty. This is very common in the campus network or public internet.
+
+**Scenario 3:** This scenario can be found in some broadband access provider network. There are some third-party NAT devices deployed in the operators' network, by which it can provide the access services to the end-users. In this scenario, users can deploy their own NAT devices as well.
+
+This clause discusses the above three scenarios respectively, which is illustrated with the example of the P2P VoIP system.
+
+The network deployment information collected by MOCC can provide assistance to solve this problem. For example, the address-related information of NAT can be used to implement the NAT traversal. On the other hand, to enhance the performance, it can help to find the best relay path, such as by minimizing the NATs in the path or discovering the same-root NATs.
+
+#### **I.3.2 Scenario 1: Unified NAT deployment by the network operators**
+
+**Description:** The scenario in Figure I.7 illustrates the deployment of MOCC functionalities into one P2P VoIP system. In this scenario, User D wishes to establish a call with User A. MOCC functionalities have been deployed into this system.
+
+**Pre-condition:** The P2P nodes in this system are authorized to use the MOCC service. NLRF and RASF have already registered to the MOCC entrance component, which has created the corresponding records in turn. User A and User D are registered to its corresponding bootstrapping servers.
+
+In this scenario:
+
+- 1) User D wants to establish a call with User A. First, it will send the location query request to its service node to acquire the address of User A.
+- 2) According to the UserID carried in the request message, the service node will then retrieve the IP address and NodeID of User A. The service node will then send the response message to User D, which includes the necessary information of User A.
+- 3) User D sends the session initiate request to the service node, which carries the address of User A.
+- 4) The simplest way for the service node to process this request is to choose some nodes along the path from User D to User A for the media relay. One possible path may be User D → Node C → Node D → User A. However, with the aid of the MOCC server, that selection can be optimized.
+- 5) The service node will send the network topology query request to the NLRF, which includes the information of those candidate nodes.
+- 6) NLRF will then inquire about the bearer network information services, which can be implemented by the MOCC itself or be provided by some practical entities such as RACF, or in some cases, within certain policy boundaries, those information services can be provided by the network operators, and then send the result to the service node.
+
+- 7) From the topology information, it was found that Node A and User A are under the same NAT, therefore the path can be established from User D → Node A → User A.
+
+![Diagram illustrating the scenario of P2P Application NAT traversal using MOCC service. The diagram shows a hierarchy of NAT devices (NAT1 to NAT5) connected to the Internet. NAT1 is connected to the Internet and has a public IP 202.112.100.100. NAT1 is connected to NAT2 (10.10.1.100) and NAT3 (172.24.1.*). NAT2 is connected to NAT4 (192.168.1.1) and NAT5 (192.168.1.2). NAT4 is connected to User A (10.10.1.*) and Node A. NAT5 is connected to Node D (10.10.1.*) and Node B. NAT3 is connected to Node C (10.10.1.102) and User D. The Internet cloud contains 'Bearer network information'. Above the Internet cloud, the MOCC entrance is connected to NLRF and RASF components.](08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg)
+
+Diagram illustrating the scenario of P2P Application NAT traversal using MOCC service. The diagram shows a hierarchy of NAT devices (NAT1 to NAT5) connected to the Internet. NAT1 is connected to the Internet and has a public IP 202.112.100.100. NAT1 is connected to NAT2 (10.10.1.100) and NAT3 (172.24.1.\*). NAT2 is connected to NAT4 (192.168.1.1) and NAT5 (192.168.1.2). NAT4 is connected to User A (10.10.1.\*) and Node A. NAT5 is connected to Node D (10.10.1.\*) and Node B. NAT3 is connected to Node C (10.10.1.102) and User D. The Internet cloud contains 'Bearer network information'. Above the Internet cloud, the MOCC entrance is connected to NLRF and RASF components.
+
+**Figure I.7 – Scenario of P2P Application NAT traversal using MOCC service**
+
+#### I.3.3 Scenario 2: The lowest-level NATs are connected and owned by the users
+
+**Description:** The scenario in Figure I.8 illustrates the deployment of MOCC functionalities in a P2P VoIP system. MOCC functionalities have been deployed into this system. NAT-U1/U2/U3/U4 are owned and connected by the end-users, which remain unknown to the network operators.
+
+**Pre-condition:** The P2P nodes in this system are authorized to use the MOCC service. NLRF and RASF have already registered to the MOCC entrance component, which have created the corresponding records in turn. All the users are registered to its corresponding bootstrapping servers.
+
+In this scenario:
+
+- 1) The bootstrapping server is deployed in each level of this NAT topology, from the root NAT to the operator's lowest-level NATs, to which the user-owned NAT are connected. In this way, the NLRF can collect all the topology information of the end users.
+- 2) User A, User C and User D send the register request to the bootstrapping server in the current network of NAT2.
+- 3) Upon receiving those messages, the bootstrapping server will compare the address information carried in the IP headers and message payloads. If the information doesn't match, then it will determine that those users are behind the unknown NAT devices. And meanwhile it will store the address mapping information and send the message upwards level by level, until it reached the bootstrapping server in the public network.
+- 4) According to the topology information stored in each bootstrapping server, the topology view will be computed and generated by the NLRF component.
+
+- 5) User C wants to establish a call with User A. First, it will send the location query request to its service node to acquire the address of User A.
+- 6) The service node will send the network topology query request to the NLRF, which includes the information of User A and User C.
+- 7) NLRF will then query the bearer network information services, from the topology information. If it is found that User A and User C are under the same NAT, Node A can be selected as the optimum service node to assist the communication between User A and User C.
+- 8) After the path optimization, the media can be established from User A to User C.
+- 9) In this way, the unwanted traffic in the P2P system can be reduced, and the resources of the corresponding service node can be optimized as well.
+
+![Diagram illustrating network topology and NAT configurations for a P2P system. At the top, a MOCC entrance connects to a dashed box containing NLRF and RASF. An inset box shows a network topology with Node C, Node D, Node B, and Node A. Node C is connected to Node D and Node B. Node D is connected to Node A. Node B is connected to Node A. Associated with these nodes are state boxes: Node C: (-, USER = {}), Node D: (NAT3, USER = {User D}), Node B: (NAT1, USER = {}), Node A: (NAT2, USER = {User A, User C}). The main diagram shows the Internet cloud connected to a 'Bearer network information' box. Below the Internet, there are several NATs and nodes: NAT1 (public IP 202.112.100.100, private IP 10.10.1.*), NAT2 (public IP 10.10.1.100, private IP 192.168.1.*), NAT-U1 (private IP 192.168.1.2), NAT-U2 (private IP 192.168.1.2), NAT3 (public IP 202.112.200.100, private IP 10.10.1.*), NAT-U3 (private IP 10.10.1.101), and NAT-U4 (private IP 10.10.1.102). Nodes are connected as follows: Node D to NAT1; Node A to NAT2; Node C to NAT3; User A to NAT-U1; User C to NAT-U2; Node B to NAT-U4; User D to NAT-U3. Dashed green lines represent bearer network information paths between the Internet cloud and various nodes and NATs.](365b54f616aff249b4e6c0edafdcb9b3_img.jpg)
+
+Diagram illustrating network topology and NAT configurations for a P2P system. At the top, a MOCC entrance connects to a dashed box containing NLRF and RASF. An inset box shows a network topology with Node C, Node D, Node B, and Node A. Node C is connected to Node D and Node B. Node D is connected to Node A. Node B is connected to Node A. Associated with these nodes are state boxes: Node C: (-, USER = {}), Node D: (NAT3, USER = {User D}), Node B: (NAT1, USER = {}), Node A: (NAT2, USER = {User A, User C}). The main diagram shows the Internet cloud connected to a 'Bearer network information' box. Below the Internet, there are several NATs and nodes: NAT1 (public IP 202.112.100.100, private IP 10.10.1.\*), NAT2 (public IP 10.10.1.100, private IP 192.168.1.\*), NAT-U1 (private IP 192.168.1.2), NAT-U2 (private IP 192.168.1.2), NAT3 (public IP 202.112.200.100, private IP 10.10.1.\*), NAT-U3 (private IP 10.10.1.101), and NAT-U4 (private IP 10.10.1.102). Nodes are connected as follows: Node D to NAT1; Node A to NAT2; Node C to NAT3; User A to NAT-U1; User C to NAT-U2; Node B to NAT-U4; User D to NAT-U3. Dashed green lines represent bearer network information paths between the Internet cloud and various nodes and NATs.
+
+**Figure I.8 – The lowest-level NATs are connected and owned by the users**
+
+
+
+
+
+# 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           |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                             |
+| 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/F/T-REC-F.746.13-202203-I_PDF-E/raw.md b/marked/F/T-REC-F.746.13-202203-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..4e5068d5de9dc52d1ee24898594e4880e4bbadd3
--- /dev/null
+++ b/marked/F/T-REC-F.746.13-202203-I_PDF-E/raw.md
@@ -0,0 +1,609 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+**F.746.13**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+(03/2022)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Multimedia services
+
+---
+
+**Requirements for smart speaker-based  
+intelligent multimedia communication systems**
+
+Recommendation ITU-T F.746.13
+
+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, blue, sans-serif font superimposed on the globe.
+
+ITU logo
+
+# ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| <b>TELEGRAPH SERVICE</b>                                        |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| <b>MOBILE SERVICE</b>                                           |                    |
+| Mobile services and multdestination satellite services          | F.110–F.159        |
+| <b>TELEMATIC SERVICES</b>                                       |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| <b>MESSAGE HANDLING SERVICES</b>                                | F.400–F.499        |
+| <b>DIRECTORY SERVICES</b>                                       | F.500–F.549        |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | F.600–F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700–F.799</b> |
+| <b>ISDN SERVICES</b>                                            | F.800–F.849        |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | F.850–F.899        |
+| <b>ACCESSIBILITY AND HUMAN FACTORS</b>                          | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## Recommendation ITU-T F.746.13
+
+# Requirements for smart speaker-based intelligent multimedia communication systems
+
+## Summary
+
+Recommendation ITU-T F.746.13 specifies requirements for intelligent multimedia communication for various types of smart speaker, including those for the reference architecture, smart devices, signalling and platforms, as well as giving a few typical scenario examples. Recommendation ITU-T F.746.13 also specifies requirements for eliminating differences in multimedia communication and access management of heterogeneous devices, to simplify the construction complexity of intelligent multimedia communication systems (IMCSs), to improve the security and reliability of signalling and multimedia data transmission between smart speakers and IMCSs, with a view to finally guaranteeing high-quality multimedia communication service.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.746.13 | 2022-03-16 | 16          | <a href="http://handle.itu.int/11.1002/1000/14960">11.1002/1000/14960</a> |
+
+## Keywords
+
+Intelligent, multimedia communication system, requirements, smart speaker.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                    | 2  |
+| 4          | Abbreviations and acronyms .....                             | 2  |
+| 5          | Conventions .....                                            | 3  |
+| 6          | Overview of intelligent multimedia communication system..... | 3  |
+| 7          | Smart device requirement .....                               | 4  |
+| 7.1        | Hardware requirement .....                                   | 4  |
+| 7.2        | Software requirements .....                                  | 5  |
+| 7.3        | Artificial intelligent interaction requirement.....          | 6  |
+| 8          | Signalling requirement .....                                 | 7  |
+| 8.1        | Codec requirement.....                                       | 7  |
+| 8.2        | Transmission engine requirement.....                         | 7  |
+| 8.3        | Media streaming requirement.....                             | 7  |
+| 8.4        | Security requirement .....                                   | 7  |
+| 9          | Platform requirement .....                                   | 7  |
+| 9.1        | Communication requirements .....                             | 7  |
+| 9.2        | Application requirement.....                                 | 9  |
+| 9.3        | Operational requirement.....                                 | 9  |
+| Appendix I | – Typical use cases and scenarios.....                       | 11 |
+| I.1        | Family communication.....                                    | 11 |
+| I.2        | Family and community security .....                          | 11 |
+| I.3        | Hotel service.....                                           | 11 |
+|            | Bibliography.....                                            | 12 |
+
+
+
+# **Requirements for smart speaker-based intelligent multimedia communication systems**
+
+# **1 Scope**
+
+This Recommendation specifies requirements for smart speaker-based intelligent multimedia communication systems (IMCSs). This Recommendation describes scenarios and requirements for the entire system to support multimedia communication capabilities over smart devices such as smart speakers.
+
+The scope of this Recommendation includes:
+
+- requirements for smart devices to access IMCSs, including those for multimedia, artificial intelligence (AI) interaction and signalling;
+- requirements for platforms for IMCSs, including those for communications, applications and operations;
+- requirements for security considerations of IMCSs, including those for access control, as well as calling management and transport encryption;
+- typical use cases and application scenarios of IMCSs.
+
+# **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] Recommendation ITU-T G.711 (1988), *Pulse code modulation (PCM) of voice frequencies*.
+- [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 H.264] Recommendation ITU-T H.264 (2021), *Advanced video coding for generic audiovisual services*.
+- [ITU-T H.265] Recommendation ITU-T H.265 (2021), *High efficiency video coding*.
+- [3GPP TS 24.229] 3GPP TS 24.229 V17.6.1 (2022-03), *3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP multimedia call control protocol based on session initiation protocol (SIP) and session description protocol (SDP): Stage 3 (Release 17)*.
+- [ETSI EN 301 703] ETSI EN 301 703 V7.0.2 (1999), *Digital cellular telecommunications system (Phase 2+); Adaptive multi-rate (AMR); Speech processing functions; General description (GSM 06.71 Version 7.0.2 Release 1998)*.
+- [IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A transport protocol for real-time applications*.
+- [IETF RFC 4566] IETF RFC 4566 (2006), *SDP: Session description protocol*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 automatic speech recognition (ASR)** [b-ITU-T F.745]: 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). [b-ITU-T P.10]
+
+**3.1.2 smart speaker** [b-ITU-T Y.4204]: A speaker that is capable of anything beyond just emitting sound.
+
+NOTE – Typically, smart speaker refers to an artificial intelligence speaker that utilizes voice recognition technology and is equipped with Internet connectivity.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 intelligent voice interaction:** A technology that is capable of giving appropriate voice feedback according to natural language input by using the speech recognition ability embedded in a terminal or deployed in cloud.
+
+**3.2.2 IP multimedia subsystem:** An architectural framework for delivering multimedia services over the Internet protocol that is specified in [b-ETSI TS 123 228].
+
+**3.2.3 smart display:** A smart speaker with a screen to display multimedia information.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|        |                                        |
+|--------|----------------------------------------|
+| AI     | Artificial Intelligence                |
+| AMR    | Adaptive Multi-Rate                    |
+| AMR-WB | Adaptive Multi-Rate Wideband           |
+| ASR    | Automatic Speech Recognition           |
+| BCLK   | Base Clock                             |
+| IMS    | Internet protocol Multimedia Subsystem |
+| ID     | Identifier                             |
+| IP     | Internet Protocol                      |
+| LRCK   | Left Right Channel Clock               |
+| MCLK   | Master Clock                           |
+| MIC    | Microphone                             |
+| NLP    | Natural Language Processing            |
+| PBX    | Private Branch exchange                |
+| PCMA   | Pulse Code Modulation A-law algorithm  |
+| PCMU   | Pulse Code Modulation U-law algorithm  |
+| RTCP   | Real-time Transport Control Protocol   |
+| RTP    | Real-time Transport Protocol           |
+
+|      |                                     |
+|------|-------------------------------------|
+| SDK  | Software Development Kit            |
+| SDP  | Session Description Protocol        |
+| SIP  | Session Initiation Protocol         |
+| SRTP | Secure Real-time Transport Protocol |
+| TV   | Television                          |
+| WLAN | Wireless Local Area Network         |
+
+# 5 Conventions
+
+In this Recommendation:
+
+- The phrase "is required to" indicates a requirement that must be strictly followed and from which no deviation is permitted if conformity to this Recommendation is to be claimed.
+- The phrase "is recommended" indicates a requirement that is recommended but which is not absolutely required. Thus this requirement need not be present to claim conformity.
+
+# 6 Overview of intelligent multimedia communication system
+
+Figure 6-1 shows that the system contains an architecture of three layers named: smart device; application; and network. Clauses 7 to 9 provide requirements on three aspects: smart device; multimedia communication platform; and security issues. The network requirement currently lies outside the scope of this Recommendation, it is left for further study. In Appendix I, some typical use cases and scenarios are further described.
+
+The AI interaction module includes:
+
+- AI capabilities for communication purposes;
+- differentiation calling initiation from home automation control;
+- text or voice-based recognition.
+
+![Figure 6-1: Example of intelligent multimedia communication system architecture. The diagram shows three domains: Smart device domain, Application domain, and Network domain. The Smart device domain contains a 'Smart device' box with 'Multimedia processing', 'AI interaction', and 'Signalling processing' modules. It connects via an 'IP access node' to the Application domain. The Application domain contains a 'Multimedia communication service platform' box with 'Operation module', 'Application module', and 'Communication module'. The 'Communication module' connects to the Network domain, which contains 'BOSS' and 'IMS network' boxes. The reference F.746.13(22) is shown at the bottom right.](a234352dfaccdc24745c88eef7724cc6_img.jpg)
+
+Figure 6-1: Example of intelligent multimedia communication system architecture. The diagram shows three domains: Smart device domain, Application domain, and Network domain. The Smart device domain contains a 'Smart device' box with 'Multimedia processing', 'AI interaction', and 'Signalling processing' modules. It connects via an 'IP access node' to the Application domain. The Application domain contains a 'Multimedia communication service platform' box with 'Operation module', 'Application module', and 'Communication module'. The 'Communication module' connects to the Network domain, which contains 'BOSS' and 'IMS network' boxes. The reference F.746.13(22) is shown at the bottom right.
+
+Figure 6-1 – Example of intelligent multimedia communication system architecture
+
+# 7 Smart device requirement
+
+In general, smart speakers are capable of supporting multimedia communication if they meet the hardware, software and AI interaction requirements in clauses 7.1 to 7.3, which are summarized based on observation of large-scale online services.
+
+## 7.1 Hardware requirement
+
+For smart speakers, if the operating system is Linux the following requirements are recommended.
+
+- a) The available space of the flash is required to be larger than 20 Mbyte, and the tool chain e.g., compiler GCC 5.0 or above, is required.
+- b) The compilation environment is required to support C++ version 11.0, and the underlying audio driver is required to support advanced Linux sound architecture.
+
+For smart speakers with an Android operating system, the following requirements are recommended.
+
+- a) Android version 4.2 or above is required.
+- b) The capacity for storing the driver program is recommended to be greater than 9.4 Mbyte.
+- c) The flash capacity is recommended to be more than 67 Mbyte.
+
+### 7.1.1 Requirements of camera and screen for smart display
+
+Table 7-1 lists additional requirements that are recommended for smart display to give a better user experience if multimedia communication is supported.
+
+**Table 7-1 – Additional requirements of smart display**
+
+| Functional blocks |            | Requirements             |
+|-------------------|------------|--------------------------|
+| Pixels of camera  |            | no less than 2 Mpixels   |
+| Display           | resolution | 800 × 480 and above      |
+|                   | size       | not less than 3.9 inches |
+|                   | touch mode | multiple types of touch  |
+
+### 7.1.2 Requirements of wireless local area network interface
+
+The wireless local area network (WLAN) interface is required to comply with IEEE 802.11 a/b/g/n protocol standards, and the interface of WLAN is recommended to support 802.11ax (WiFi6) protocols [b-IEEE 802.11ax] or 802.11ac protocols [b-IEEE 802.11].
+
+The frequency spectrum is required to support 2.4 GHz (according to requirements for mainstream products in the market), and the frequency spectrum is recommended to support 5 GHz.
+
+It is required to support IPv4, IPv6 protocols.
+
+### 7.1.3 Additional requirements
+
+Table 7-2 lists requirements for the speaker and microphone (MIC).
+
+**Table 7-2 – Additional requirements of speaker and microphone**
+
+|         |                         | Smart Speaker without screen                               | Smart display      |
+|---------|-------------------------|------------------------------------------------------------|--------------------|
+| Speaker | Power of single speaker | no less than 2 W                                           | no less than 2 W   |
+|         | Quantity                | no less than one                                           |                    |
+|         | Requirement             | full spectrum                                              |                    |
+| Audio   | Frequency response      | 120-16 kHz (–6 dB)                                         |                    |
+|         | S/N                     | no less than 75 dB                                         | no less than 75 dB |
+| MIC     | Sensitivity             | –26 dBFS @94 dB SPL@ 1 kHz<br>–38 dBV/Pa @94 dB SPL@ 1 kHz |                    |
+|         | S/N                     | no less than 62 dB                                         |                    |
+|         | Material                | silicon microphone                                         |                    |
+|         | Quantity                | no less than two in home or hotel scenarios                |                    |
+
+A list of acoustic requirements for a smart speaker follows.
+
+- a) MIC consistency should be kept within  $\pm 3$  dB.
+- b) The airtightness of the entire MIC is required to meet the requirement that the difference of amplitude frequency response between the blocked case and unblocked case is not less than 15 dB.
+- c) The frequency response of the speaker is about 120-16 kHz.
+- d) The resonant frequency in the high frequency range should be greater than 8 kHz.
+
+Table 3 lists additional requirements of a MIC array.
+
+**Table 7-3 – Additional requirements of microphone array**
+
+| Category                  | Requirements                                                                                                 |
+|---------------------------|--------------------------------------------------------------------------------------------------------------|
+| Instruction & calculation | Floating-point computation                                                                                   |
+|                           | 4 500 Dhrystone million instructions executed per second                                                     |
+| I2S interface             | Left right channel clock (LRCK): 44.1 kHz<br>Base clock (BCLK): 6.144 MHz<br>Master clock (MCLK): 12.288 MHz |
+|                           | Left alignment, most significant bit                                                                         |
+|                           | 16 bits, 32-bit wide                                                                                         |
+|                           | BCLK and MCLK clock synchronization                                                                          |
+|                           |                                                                                                              |
+| I2C interface             | Bit-rate no greater than 100 kbit/s                                                                          |
+|                           | Write operations exceeding 40 bytes                                                                          |
+| RAM occupied              | No more than 50 Mbyte                                                                                        |
+| ROM occupied              | No more than 25 Mbyte                                                                                        |
+| Audio re-sampling         | Support analogue audio data re-sampling                                                                      |
+
+## 7.2 Software requirements
+
+Software requirements can be classified into three categories for: a) the smart speaker side; b) access protocols between smart speakers and the platform; c) adaptation between smart speakers and applications.
+
+The software requirements for smart speaker include those for underlying software design, supporting protocols, operating system, security function and management.
+
+The software requirements of access protocols between smart speaker and platform mainly relate to those for service and management.
+
+In order to support communication with the platform, it is required for smart speakers to be able to pre-set a specific software development kit (SDK). With ready-made capability, services such as terminal management, access control and other security control can be achieved.
+
+Manufacturers are required to have the ability to develop embedded software or firmware for their systems to be able to adapt to the SDK and to upgrade and maintain subsequent versions of the software.
+
+## 7.3 Artificial intelligent interaction requirement
+
+Smart speakers that are capable of supporting multimedia communication are required to support the intelligent interaction requirements, such as voice wake-up and voice recognition, as well as multimedia application interaction requirements, such as quick response and multiple rounds of dialogue (at least two rounds of dialogue and application query).
+
+![Diagram of intelligent interaction process showing the flow from voice input through voice recognition, natural language understanding, AI core module, AI cloud, control command and execution, natural language generation, and speech synthesis to voice output.](d4af765160d04ecef538e5066006dc77_img.jpg)
+
+```
+
+graph LR
+    VI[Voice input] --> VR[Voice recognition]
+    VR --> NLU[Natural language understanding]
+    NLU --> ACM[AI core module]
+    NLU --> AC[AI cloud]
+    AC <--> ACM
+    ACM --> CCE[Control, command and execution, i.e., dialogue, multimedia play]
+    CCE <--> ACM
+    ACM --> NLG[Natural language generation]
+    NLG --> SS[Speech synthesis]
+    SS --> VO[Voice output]
+  
+```
+
+F.746.13(22)
+
+Diagram of intelligent interaction process showing the flow from voice input through voice recognition, natural language understanding, AI core module, AI cloud, control command and execution, natural language generation, and speech synthesis to voice output.
+
+**Figure 7-1 – Diagram of intelligent interaction process**
+
+To support the functions previously listed, the intelligent interaction process is required to include the following modules or to provide similar functions:
+
+- a) voice recognition: converting voice signals into text signals;
+- b) natural language understanding: extracting key information from text signals;
+- c) AI core module: being responsible for dialogue management based on key information or completing the execution of corresponding control commands and generating further feedback information;
+- d) AI cloud: being used to communicate with the AI core module to deal with AI inference tasks;
+- e) natural language generation: generating text signals according to feedback information from the AI core module;
+- f) Speech synthesis: converting text signals into speech signals and generating a synthetic voice.
+
+### 7.3.1 Artificial intelligence-based voice user interaction
+
+A voice trigger that enables users to invoke a speech recognition engine by saying a specific phrase is required.
+
+ASR is required to support basic operation over smart speakers. It is recommended to support far-field ASR [b-Haeb-Umbach] over 3.5 m.
+
+### 7.3.2 Artificial intelligence-based operation interface
+
+In general, key interaction is supported by most smart speakers. Some smart displays can support multitouch interaction on screens. With the development of AI technologies, it is necessary to support multimedia communication over smart devices. For example, natural language processing (NLP) [b-Guida], used to help understand user voice intention, is required to support multimedia interaction in the data corpus. Here, standard language is recommended, and dialect is not compulsory in the first stage.
+
+#### 7.3.3 Artificial intelligence-based assistance tips
+
+Consideration of advanced intelligent interaction services, such as hand gesture recognition and scene detection, is also recommended to provide a better human-computer interaction experience. With the development of more advanced AI technologies, there can be more mechanisms for users.
+
+# 8 Signalling requirement
+
+Signalling requirements of smart speakers that have multimedia communication access capability include those for a codec, transmission engine and media streaming.
+
+## 8.1 Codec requirement
+
+To meet coding and decoding requirements, the following coding and decoding methods, including pulse code modulation A-law algorithm (PCMA) and pulse code modulation U-law algorithm (PCMU) [ITU-T G.711], adaptive multi-rate (AMR) [ETSI EN 301 703] and adaptive multi-rate wideband (AMR-WB) [ITU-T G.722.2] must be supported.
+
+First, to access the Internet protocol (IP) multimedia subsystem (IMS) core network, the corresponding coding methods can be used to complete audio coding, decoding, packaging and disassembling package. Second, support for a variety of video encoding methods, such as VP8 [b-IETF RFC 6386], [ITU-T H.264], [ITU-T H.265] and other video encoding standards, is required. Third, ability to process captured original video in advance to eliminate the effect of ambient light on it is also required. Moreover, adaptation of the code rate to network jitter, delay and packet loss is required to achieve better performance.
+
+## 8.2 Transmission engine requirement
+
+It is necessary to ensure the safety of transmissions. Commonly used methods are:
+
+- a) solving network traversal issues in peer-to-peer transmissions; and
+- b) encryption of audio and video information using SRTP [b-IETF RFC 3711].
+
+## 8.3 Media streaming requirement
+
+For media streaming requirements, support for the real-time transport protocol (RTP) and real-time transport control protocol (RTCP) [IETF RFC 3550] is necessary by smart speakers.
+
+## 8.4 Security requirement
+
+For smart speakers with multimedia communication capability, it is recommended that security requirements include those in clauses 8.1 to 8.3, including encryption of transmission and content. This Recommendation also specifies additional security requirements.
+
+# 9 Platform requirement
+
+## 9.1 Communication requirements
+
+The communication module is required to realize the following functions: registration management; business management; calling database management; monitoring management; call management, media agent and IMS agent.
+
+### 9.1.1 Registration management
+
+The function of registration management is required to support:
+
+- a) allocation of the corresponding phone number according to the pre-allocated unique identifier (ID) for a smart speaker device, such as a mobile equipment identity;
+- b) configuration of different formats of phone number for smart speakers, including but not limited to fixed number or mobile phone number;
+- c) management of multiple types of smart speakers simultaneously, and conversion of signalling according to operators' requirements;
+- d) registration of the corresponding phone number on the IMS for smart speakers, and handling signalling transmission and media stream transmission during a call;
+- e) recording of the registration status of pre-allocated ID and telecommunication number, and other information;
+- f) initiation of signalling such as session initiation protocol (SIP) and SDP ([b-IETF RFC 3261], [3GPP TS 24.229] and [IETF RFC 4566]).
+
+### **9.1.2 Business management**
+
+Deployment of the calling configuration, such as call sequence schedule, simultaneous vibration, sequential vibration and number regulation, should be supported.
+
+### **9.1.3 Calling database management**
+
+The function of calling database management is required to support:
+
+- a) generation of a calling database after each call;
+- b) collection of statistics, billing, verification and other calling-related data functions.
+
+#### **9.1.4 Monitoring management**
+
+The function of monitoring management is required to support:
+
+- a) recording of the operating status of each component in the communication module;
+- b) retrieval, monitoring, alarm and analysis based on the operating status of each component in the communication module.
+
+#### **9.1.5 Signalling controller**
+
+The function of signalling controller is required to:
+
+- a) be supported in the IMS system, for which it should use SIP signalling to realize authentication for smart speakers and servers, signalling routing, session control (simultaneous vibration, sequential vibration, session management and control), media control, multiple device control, and other functions;
+- b) support SIP and SDP according to [3GPP TS 24.229] and [IETF RFC 4566].
+
+#### **9.1.6 Media agent**
+
+The function of media agent is required to support:
+
+- a) establishment of media links between smart speakers and additional functions, including video synthesis, audio mixing, transcoding and data forwarding;
+- b) the following codecs: PCMA/PCMU [ITU-T G.711], AMR [ETSI EN 301 703] and AMR-WB [ITU-T G.722.2];
+- c) the codec in [ITU-T H.264].
+
+#### **9.1.7 Internet protocol multimedia subsystem agent**
+
+The function of an IMS agent is required to support:
+
+- a) the establishment, modification and release of multimedia communication service;
+- b) signalling, receiving and forwarding between the signalling controller and the IMS system;
+- c) signalling conversion and routing;
+- d) signalling interaction using SIP and SDP [3GPP TS 24.229] and [IETF RFC 4566];
+- e) RTP and RTCP [IETF RFC 3550] to support multimedia communication.
+
+## **9.2 Application requirement**
+
+The application module is required to manage: accounts; logins; and calling.
+
+### **9.2.1 Account management**
+
+The function of account management is required to support:
+
+- a) storage of phone numbers, authentication passwords and other account-associated information when the service is activated;
+- b) enquiries of service plan information;
+
+- c) the maintenance and management of smart speaker information, including device serial number and authentication information.
+
+### **9.2.2 Login management**
+
+The function of login management is required to support:
+
+- a) acquisition of configuration information, including business configuration, account information, authentication account number and authentication password during the login procedure;
+- b) synchronously recording of device login operations.
+
+### **9.2.3 Calling management**
+
+The function of call management is required to support:
+
+- a) phone number querying and corresponding name display;
+- b) telephone address list management;
+- c) the maintenance and management of calling rules, including timeout, calling transfer and calling sequence.
+
+## **9.3 Operational requirement**
+
+The operation module is required to realize the following functions: platform configuration; business configuration; operation and maintenance management.
+
+### **9.3.1 Platform configuration**
+
+The function of platform configuration is required to support:
+
+- a) software management of the platform, including service registration and discovery, configuration centre, service gateway, and service degradation;
+- b) the configuration of hardware equipment, including load balancing and message clustering.
+
+### **9.3.2 Business configuration**
+
+The function of business configuration is required to support:
+
+- a) service configuration, including account type, authentication method, account data verification, data synchronization, and some others;
+- b) configuration of calling rules, white list for controlling users and other daily operational management.
+
+### **9.3.3 Operation and maintenance management**
+
+Several operation and maintenance functions, including containerized automatic deployment, resource status monitoring, log monitoring management and real-time service alarms should be supported.
+
+# Appendix I
+
+## Typical use cases and scenarios
+
+(This appendix does not form an integral part of this Recommendation.)
+
+The typical IMCS has been deployed by China Mobile with AI-based multimedia calls (AICall), which has now served 5.6 million registered users all over China. The activity ratio of AICall has improved by over 200% when compared to that of legacy fixed lines.
+
+### I.1 Family communication
+
+The smart speaker-based multimedia communication service can be used in family communication scenarios to satisfy a variety of communication demands, such as realizing high-quality audio or video communication on multiform devices with different scene sizes.
+
+It is convenient that the embedded AI speech recognition function helps people realize different interactions, such as intelligent voice interaction, keyless operation as well as wake-up and calling anyone in the family. When people use voice over long-term evolution to call these multiform devices at home, all devices, including television (TV), with smart displays respond with video or audio calls subsequently or simultaneously. People can answer calls on TV to experience the high definition and immersive calling service or directly on smart speakers for easy usage.
+
+### I.2 Family and community security
+
+For traditional communities, demands on the ability of audio or video communication are getting urgent for common surveillance devices, such as home pads and peephole video doorbells. A variety of multiform smart devices can easily enjoy services via remote internal upgrade with a specific SDK.
+
+Existing smart devices, such as TVs, speakers and phones, can be used to link with home pads and peephole doorbells to provide high-quality video calls and other interactive services.
+
+### I.3 Hotel service
+
+The smart speaker-based multimedia services are suitable for smart hotel scenarios. Use of multiform smart terminals integrated with IMS, cloud private branch exchange (PBX) and AI technologies, can provide users with intelligent customer service, information queries and other special services.
+
+Various smart terminals in hotel rooms can be used to make cross-network and cross-domain calls with the help of intelligent voice interaction. In addition, users can also contact the hotel reception via these smart terminals as well as to receiving some specific services such as wake-up calls, renewal confirmation, cleaning, maintenance and meal delivery.
+
+# Bibliography
+
+- [b-ITU-T F.745] Recommendation ITU-T F.745 (2016), *Functional requirements for network-based speech-to-speech translation services*.
+- [b-ITU-T P.10] Recommendation ITU-T P.10/G.100 (2017), *Vocabulary for performance, quality of service and quality of experience*.
+- [b-ITU-T Y.4204] Recommendation ITU-T Y.4204 (2019), *Accessibility requirements for the Internet of things applications and services*.
+- [b-ETSI TS 123 228] Technical Specification ETSI TS 123 228 V17.3.0 (2022), *Digital cellular telecommunications system (Phase 2+) (GSM);Universal Mobile Telecommunications System (UMTS);LTE; IP Multimedia Subsystem (IMS);Stage 2 (3GPP TS 23.228 version 17.3.0 Release 17)*.
+- [b-IEEE 802.11] IEEE 802.11-2016,<sup>1</sup> *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-IEEE 802.11ax] IEEE 8802.11ax-2021, *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 Amendment 1: Enhancements for high-efficiency WLAN*.
+- [b-IETF RFC 3261] IETF RFC 3261 (2002), *SIP: Session initiation protocol*.
+- [b-IETF RFC 3711] IETF RFC 3711 (2004), *The secure real-time transport protocol (SRTP)*.
+- [b-IETF RFC 6386] IETF RFC 6386 (2011), *VP8 data format and decoding guide*.
+- [b-Guida] Guida, G., Mauri, G. (1986). Evaluation of natural language processing systems: Issues and approaches. *Proc. IEEE*. **74** (7), pp. 1026-1035.
+- [b-Haeb-Umbach] Haeb-Umbach, R., Heymann, J., Drude, L., Watanabe, S., Delcroix, M., Nakatani, T. (2021). Far-field automatic speech recognition. *Proc. IEEE*. **109**(2), pp. 124-148.
+
+---
+
+<sup>1</sup> Superseded.
+
+
+
+
+
+## **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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.746.14-202212-I_PDF-E/raw.md b/marked/F/T-REC-F.746.14-202212-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..de5cd8e3c306ff20acfdc489d7ac49314c52d249
--- /dev/null
+++ b/marked/F/T-REC-F.746.14-202212-I_PDF-E/raw.md
@@ -0,0 +1,559 @@
+
+
+# Recommendation **ITU-T F.746.14 (12/2022)**
+
+SERIES F: Non-telephone telecommunication services  
+Multimedia services
+
+---
+
+## **Requirements and reference framework for cloud virtual reality systems**
+
+![ITU logo](390120de4fe440c42fea8154fcaad334_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 F-SERIES RECOMMENDATIONS NON-TELEPHONE TELECOMMUNICATION SERVICES
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| MOBILE SERVICE                                                  |                    |
+| Mobile services and multdestination satellite services          | F.110–F.159        |
+| TELEMATIC SERVICES                                              |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400–F.499        |
+| DIRECTORY SERVICES                                              | F.500–F.549        |
+| DOCUMENT COMMUNICATION                                          |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600–F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700–F.799</b> |
+| ISDN SERVICES                                                   | F.800–F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850–F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.746.14
+
+## Requirements and reference framework for cloud virtual reality systems
+
+## Summary
+
+Cloud virtual reality based on 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.
+
+Recommendation ITU-T F.746.14 focuses on the overall requirements of cloud virtual reality systems and the related requirements of each layer including content requirements, network requirements, control requirements, resource requirements and terminal requirements, as well as the reference framework for related high-level functions.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.746.14 | 2022-12-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/15188">11.1002/1000/15188</a> |
+
+## Keywords
+
+Cloud virtual reality, reference framework, requirements, virtual reality.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....        | 1    |
+| 4 Abbreviations and acronyms .....                   | 1    |
+| 5 Conventions .....                                  | 2    |
+| 6 Overview .....                                     | 2    |
+| 7 Reference framework of cloud VR systems .....      | 3    |
+| 8 Requirements of cloud virtual reality systems..... | 4    |
+| 8.1 General requirements.....                        | 4    |
+| 8.2 Content layer .....                              | 5    |
+| 8.3 Control layer.....                               | 5    |
+| 8.4 Resource layer .....                             | 6    |
+| 8.5 Terminals.....                                   | 6    |
+| 8.6 Network.....                                     | 7    |
+| 8.7 Operation, administration and management.....    | 8    |
+| 8.8 Security.....                                    | 8    |
+| Appendix I – Use cases.....                          | 9    |
+| I.1 Cloud VR game .....                              | 9    |
+| I.2 Cloud VR live broadcast .....                    | 10   |
+| I.3 Cloud VR education .....                         | 11   |
+| Bibliography.....                                    | 13   |
+
+
+
+# Recommendation ITU-T F.746.14
+
+## Requirements and reference framework for cloud virtual reality systems
+
+# 1 Scope
+
+This Recommendation specifies the requirements and reference framework for cloud virtual reality systems.
+
+The scope of this Recommendation includes:
+
+- 1) overview of cloud virtual reality systems;
+- 2) reference framework for cloud virtual reality systems;
+- 3) requirements for cloud virtual reality systems.
+
+# 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.1631] Recommendation ITU-T J.1631 (2021), *Functional requirements of E2E network platforms to enhance the delivery of cloud-VR services over integrated broadband cable networks*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following term defined elsewhere:
+
+**3.1.1 degree of freedom (DoF)** [b-ITU-T G.1035]: Represents the ways an object can move within a space, which is a key element in helping create an immersive environment for a user.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 operations latency:** 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.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|     |                                        |
+|-----|----------------------------------------|
+| 2D  | Two Dimensions                         |
+| 3D  | Three Dimensions                       |
+| 3I  | Immersion, Interaction and Imagination |
+| API | Application Programming Interface      |
+| ARM | Application Resource Manager           |
+
+|          |                                          |
+|----------|------------------------------------------|
+| ATW      | Asynchronous Time Warp                   |
+| CDN      | Content Delivery Network                 |
+| Cloud VR | Cloud Virtual Reality                    |
+| CPU      | Central Processing Unit                  |
+| 3DoF     | Three Degrees of Freedom                 |
+| E2E      | End-to-End                               |
+| FOV      | Field of View                            |
+| FTTH     | Fibre To The Home                        |
+| GPU      | Graphic Processing Unit                  |
+| HMD      | Head-mounted Display                     |
+| OAM      | Operation, Administration and Management |
+| QoE      | Quality of Experience                    |
+| SDK      | Software Development Kit                 |
+| VR       | Virtual Reality                          |
+| WDM      | Wavelength Division Multiplexing         |
+
+# 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.
+
+# 6 Overview
+
+Cloud virtual reality (cloud VR) is a new method for providing service of virtual reality based on cloud capabilities, which comprehensively uses cloud computing, rendering, audio and video processing and other multimedia technologies. Cloud VR continues and enhances VR related immersion, interaction and imagination (3I) attributes.
+
+Cloud VR has a processing method based on cloud unified content storage and cloud logical computing, which is different from VR terminal mode that finishes logic computing, graphics rendering, and content storage by VR terminals. For the implementation of cloud VR, there are several ways used for graphics rendering, and audio and video processing, such as cloud and terminal collaboration, and terminal alone.
+
+There are many kinds of cloud VR application scenarios, which have different classifications.
+
+- From the industry dimension, cloud VR application scenarios are divided into personal consumption-level scenarios and enterprise-level scenarios. Personal consumption-level scenarios include video-on-demand, live broadcast, games, social networking, education and other analogous fields. Enterprise-level scenarios include military, medical, construction, industrial manufacturing and other analogous fields.
+- From the interaction dimension, cloud VR application scenarios are divided into weak interaction scenarios and strong interaction scenarios. Weak interaction scenarios are mainly VR video services, including VR videos, and VR live broadcasts. Strong interactive
+
+scenarios usually involve cloud real-time rendering, and interaction with virtual environments or objects, including VR games, VR education, VR fitness, VR social and VR industrial manufacturing.
+
+Two level services and two types of interaction services need different service, network and terminal capabilities, and service logic processing in cloud VR.
+
+Use cases of the cloud VR services are discussed in Appendix I.
+
+# 7 Reference framework of cloud VR systems
+
+Figure 7-1 shows the reference framework for cloud VR systems. The cloud VR systems implement cloud-based operations through various types of application contents and through various services at the resource layer supported by the control layer, and delivers cloud VR contents to different types of terminals through the network to complete the entire service process.
+
+![Figure 7-1: Reference framework for cloud VR systems. The diagram shows a five-layer architecture: Content layer (Games, Videos, Cartoons, Music, ...), Control layer (Technology integration, Content distribution), Resource layer (Cloud resources), Network layer, and Terminal layer (PC VR HMD, Integrated VR HMD, Split VR HMD, ...). Security is on the left, and Cloud VR OA&M is on the right. F.746.14(22) is noted at the bottom right.](367926125450c2bc3f4bdca9d59a62ba_img.jpg)
+
+The diagram illustrates the reference framework for cloud VR systems. It consists of five horizontal layers stacked vertically, flanked by two vertical bars. The left bar is labeled 'Security'. The right bar is labeled 'Cloud VR OA&M'. The layers are: 1. Content layer: contains 'Games', 'Videos', 'Cartoons', 'Music', and '...'. 2. Control layer: contains 'Technology integration' and 'Content distribution'. 3. Resource layer: contains 'Cloud resources'. 4. Network layer: a single empty box. 5. Terminal layer: contains 'PC VR HMD', 'Integrated VR HMD', 'Split VR HMD', and '...'. At the bottom right of the diagram, the text 'F.746.14(22)' is present.
+
+Figure 7-1: Reference framework for cloud VR systems. The diagram shows a five-layer architecture: Content layer (Games, Videos, Cartoons, Music, ...), Control layer (Technology integration, Content distribution), Resource layer (Cloud resources), Network layer, and Terminal layer (PC VR HMD, Integrated VR HMD, Split VR HMD, ...). Security is on the left, and Cloud VR OA&M is on the right. F.746.14(22) is noted at the bottom right.
+
+**Figure 7-1 – Reference framework for cloud VR systems**
+
+The content layer provides various types of application content, including cloud VR games, cloud VR videos, cloud VR cartoons and cloud VR music. According to the industry application perspective, the content of the cloud VR system can divide into cloud VR education, cloud VR fitness, cloud VR social, cloud VR industrial manufacturing, etc.
+
+The control layer provides cloud VR-related capabilities, including technology integration and content distribution:
+
+- The cloud VR technology integration provides audio and video encoding, transcoding, graphics rendering, streaming issuance, control response, and other specified service capabilities for weak and strong interaction services using general cloud resource pool capabilities.
+- The cloud VR content distribution provides distribution of processed cloud VR content from a cloud resource to a corresponding cloud VR user/terminal.
+
+The resource layer provides general hardware computing resources such as central processing units (CPUs) and graphic processing units (GPUs) for cloud VR, and basic software capabilities such as virtual machines, containers or application virtualization.
+
+The network layer provides the communication capabilities for other layers, operation, administration and management (OAM), the users and providers.
+
+The terminal layer receive/send cloud VR related data from/to the cloud, performs partial local processing/computing, and displays the cloud VR content based on the support of software and hardware. There are mainly three types of terminals for cloud VR systems, including PC VR head-mounted display (HMD), integrated VR HMD and split VR HMD:
+
+- PC VR HMD provides basic VR related device capabilities that include display, manipulation, sensing and other capabilities, but has no computing capability for complex media and service logic processing which is provided by PCs or proprietary game consoles.
+- Integrated VR HMD provides all VR related device capabilities that include basic capabilities and computing capability.
+- Split VR device provides basic VR related device capabilities, but has no computing capability which is provided by mobile terminals, such as mobile phones.
+
+The cloud VR OAM provides centralized operating, management and maintenance functions in terms of content, technology integration, and terminals, including user authentication, content introduction, cloud VR technical capability access, and cloud VR terminal management.
+
+Cloud VR provides multi-dimensional security mechanisms, such as the securities of cloud operation, service, data and user experience.
+
+# **8 Requirements of cloud virtual reality systems**
+
+### **8.1 General requirements**
+
+#### **8.1.1 Audio-visual**
+
+The overall audio-visual quality of the cloud VR systems is closely related to the content image/sound quality, computing/coding capabilities, network transmission quality, and terminal secondary processing/display capabilities. It is based on the final presentation of the user's image, sound and interaction requirements.
+
+AV-01: It is recommended to have three-dimensional properties, and its presentation method is not limited to true three dimensions (3D) display or two dimensions (2D) picture synthesis 3D, etc.
+
+AV-02: The image quality is required to reference standard [ITU-T J.1631] FEP related requirements.
+
+AV-03: It is recommended to meet the same refresh rate of the cloud VR terminal's display.
+
+#### **8.1.2 Interaction**
+
+IA-01: It is required to have smooth human-computer interaction.
+
+IA-02: It is required to have acceptable operations latency. In general, the terminal side collects control instructions and uploads them to the cloud through the network, and then the cloud completes the processing and sends the relevant results to the terminal through the network, and finally the terminal side completes the process of corresponding content and output results.
+
+IA-03: It is required to meet three degrees of freedom (3DoF) capability, and support at least one common control method, such as handle, joystick, gesture and voice.
+
+#### **8.1.3 Compatibility**
+
+CB-01: It is required to be compatible with general cloud computing resource pools.
+
+CB-02: It is required to be compatible with various cloud VR technology solutions.
+
+CB-03: It is required to support various VR contents, such as cloud VR content released on the Steam online game platform.
+
+CB-04: It is required to be compatible with network access methods that meet the transmission conditions.
+
+CB-05: It is required to be compatible with various types and different brands of VR terminals that meet the capability requirements.
+
+### **8.2 Content layer**
+
+The quality of cloud VR content is directly related to cloud VR 3I properties. The requirements for cloud VR content are as follows:
+
+CT-01: The content is required to transplant to the cloud and run based on the cloud.
+
+CT-02: It is recommended to have a flexible output method, which can be switched between panoramic and field of view (FOV) modes.
+
+## **8.3 Control layer**
+
+#### **8.3.1 The common requirements of the control layer**
+
+CP-01: The deployment server is required to support general cloud resource pool forms such as physical machines and virtual machines.
+
+CP-02: It is required to support system recovery after software and hardware failures, including data backup/recovery and service node switching. The main types of server failures include plugging and unplugging hard disks, network disconnection, shutdown and restarting.
+
+- With the cooperation of hardware and software, it is required to provide the ability to manage system failures.
+- The design life is required to be greater than 10 years.
+- The fault is required to be isolated in the module (e.g., the service node, etc.).
+- The overall service capability is required to have 7\*24 hours stable operation performance and 99.9% availability.
+- The downtime for failures is required to not exceed 2 hours within three months.
+- Short-term failures of related servers and other equipment are required to not cause alarms and service data.
+
+CP-03: It is required to have flexible scalability to support the seamless addition of service nodes and the operation of servers in the nodes as the service carrying requirements increase, so as to improve the carrying capacity.
+
+CP-04: Compatibility requirements:
+
+- It is required to have the ability to be compatible with the software version. When the software version is upgraded or revised, it has the ability to be compatible with the cloud VR application content previously based on it.
+- It is required to have the ability to be compatible with application content developed based on the general VR framework.
+
+#### **8.3.2 Technology integration**
+
+TI-01: It is required to build cloud VR technical services based on the cloud resource pool.
+
+TI-02: It is required to build cloud VR technology services nodes based on edge nodes.
+
+TI-03: It is recommended to have the ability of GPU-based video encoding.
+
+TI-04: It is required to have the functions such as seamless migration of services and data security assurance.
+
+TI-05: It is required to have the ability to interface with the cloud VR operation services to provide cloud VR technical integration services.
+
+TI-06: It is required to have functions such as docking with cloud VR terminals, obtaining control instructions, and calling audio and video decoding capabilities.
+
+TI-07: For VR weak interactive services, it is required to provide functions such as cloud transcoding, content distribution and content delivery network (CDN) resource scheduling.
+
+TI-08: For VR strong interactive services, it is required to provide at least one method based on virtual machines, containers, and application virtualization to build parallel cloud VR instances:
+
+- It is required to support cloud-based drivers, including rendering driver, video low-latency compression coding and video streaming transmission.
+- Each cloud rendering server or virtual machine is required to have the capability of multi-application rendering parallelism. For rendering services that can run/stream processing with single-core CPU and single-core GPU, it has the parallel operation capability of the smallest cores between CPU and GPU.
+- It is required to achieve a one-to-one correspondence between the number of picture frames and the corresponding picture sound data collection, and the time difference is recommended to not exceed 100 ms.
+
+#### 8.3.3 Content distribution
+
+Cloud VR content distribution has an interface with cloud VR operation, which provides cloud VR content aggregation, recommendation and distribution functions.
+
+CD-01: It is required to provide an effective cloud VR content download or online operation path.
+
+CD-02: It is required to provide a CDN function for cloud VR video service.
+
+CD-03: It is required to provide storage capabilities that match the distribution of cloud VR content.
+
+## 8.4 Resource layer
+
+CR-01: It is required to provide generic physical or virtual CPU, GPU, storage, network card and other hardware resources.
+
+- It is required to provide generic software systems, including safe operating systems, hardware drivers and general graphics interfaces.
+- It is required to provide compliant virtual machines, containers or application virtualizations and other concurrent reuse mechanisms of software and hardware resources.
+
+CR-02: It is required to provide general cloud resource pool configuration, expansion, migration, management and other functions.
+
+CR-03: It is required to provide data storage, and data backup.
+
+CR-04: It is required to provide secure and reliable virtual machines, containers or application virtualizations, one-click migration, and a secure data synchronization mechanism.
+
+## 8.5 Terminals
+
+#### 8.5.1 Hardware
+
+HW-01: It is required to use general CPU architecture such as X86, ARM and others, with complete computing, rendering, storage and other processing capabilities for cloud VR service.
+
+HW-02: It is required to have enough calculation ability, including CPU and GPU.
+
+HW-03: It is required to have enough storage capacity.
+
+HW-04: It is required to provide 2K or more, dual-screen near-eye display capability.
+
+HW-05: It is required to provide 3DOF capability, and is recommended to provide the above 3DOF capability.
+
+HW-06: It is required to provide one or more effective control devices, including handles and VR helmet buttons.
+
+HW-07: It is recommended to provide relevant optical equipment for accurate spatial positioning.
+
+HW-08: It is required to have network access capability above 100 M.
+
+#### **8.5.2 Software**
+
+SW-01: It is recommended to use common operating systems such as Windows, Linux, Android and Harmony.
+
+SW-02: It is required to install hardware drivers.
+
+SW-03: It is required to have the ability to access the different cloud VR layers.
+
+- It is required to support cloud VR user management, authentication, and charging functions through connecting with the different cloud VR layers.
+- It is required to support functions such as receiving cloud VR service audio and video streams and uploading control commands.
+- It is required to support cloud VR content push, update and release functions through connecting with the different cloud VR layers.
+
+SW-04: It is recommended to support multiple codecs, such as H.264, H.265, AVI, and VP9, and also support two or more at the same time.
+
+SW-05: It is required to support the function of a near-eye 3D display.
+
+SW-06: The overall terminal operation delay and processing delay are recommended to be less than 40 ms, of which the asynchronous time warp (ATW) is required to be less than 20 ms, and the graphics and audio data decoding is recommended to be less than 20 ms.
+
+### **8.6 Network**
+
+CN-01: The bandwidth is required to reference standard [ITU-T J.1631] FEP related requirements.
+
+CN-02: The latency is required to be less than or equal to 100 ms. For strong-interaction VR service, it is recommended that the manipulation latency is less than or equal to 50 ms.
+
+CN-03: The packet loss rate is required to less than or equal to  $10^{-4}$  ([ITU-T J.1631] FEP). For strong-interaction VR service, the packet loss rate is recommended to be less than or equal to  $10^{-5}$ .
+
+CN-04: For wired access, it is recommended to use fibre to the home (FTTH) access technology.
+
+CN-05: For wireless cellular access, it is recommended to use 5G and above network access standards.
+
+CN-06: Access delay is required to be less than or equal to 5 ms, and is recommended to be less than or equal to 2 ms.
+
+CN-07: It is recommended to support deterministic network access guarantees for cloud VR services such as bandwidth and delay.
+
+CN-08: It is recommended to provide network guarantee mechanisms such as link path selection and network acceleration.
+
+CN-09: It is recommended to use optical fibre or wavelength division multiplexing (WDM) direct connection between cloud VR edge computing nodes to reduce the delay of multi-person remote interaction.
+
+CN-10: Inside the cloud data centre, a 1 Gbit/s or more network interconnection is required, and 10 Gbit/s or more is recommended.
+
+## **8.7 Operation, administration and management**
+
+CO-01: It is required to have the ability to provide cloud VR operation and management based on a cloud basic resource pool or general server.
+
+CO-02: It is required to have the ability to centralize the management and scheduling of resources in the underlying cloud resource pool.
+
+CO-03: It is required to have the ability to interface with various VR applications, including the ability to import and release VR applications.
+
+CO-04: It is required to have the ability to connect the cloud VR technology integration service.
+
+CO-05: It is required to have service authentication and service invocation/removal capabilities of different cloud VR technical integration services.
+
+CO-06: It is required to have complete user authentication, service billing, data analysis, operation and maintenance, etc.
+
+CO-07: It is required to have the ability to interface with cloud VR terminals, complete user authentication, content synchronization, and charging functions.
+
+CO-08: It is recommended to adopt software development kit (SDK), application programming interface (API) and other forms to provide the capability of a built-in cloud VR terminal for operational capability.
+
+## **8.8 Security**
+
+SR-01: It is required to have the ability to divide security domains according to service nodes, deploy firewalls, intrusion detection, abnormal traffic detection and filtering and other measures.
+
+SR-02: It is required to have anti-virus capabilities and process (logical) security assurance, including access rights restrictions, security audits and other functions.
+
+SR-03: It is required to have the ability to ensure the service security through user management, authority management, log management, etc.
+
+SR-04: It is required to have security protection capabilities for metadata, user access data, business operation data, etc., and use encryption technology to encrypt important data transmitted on the Internet.
+
+SR-05: It is required to have corresponding measures to prevent and deal with simulator sickness, including fatigue, sweating, vertigo and nausea.
+
+## Appendix I
+
+### Use cases
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Through cloud computing, compared with the VR terminal mode, cloud VR has the advantages of enhanced service capability, reduced terminal operation pressure and centralized distribution of content, so as to deduce a variety of rich and colourful use case types.
+
+In order to show the characteristics of cloud VR strong interaction scenarios and cloud VR weak interaction scenarios, this appendix selects typical use cases such as cloud VR games and cloud VR live broadcasts. At the same time, cloud VR education with strong and weak interaction attributes is selected as a typical use case.
+
+Cloud VR game and cloud VR live broadcast serve as as personal consumption-level service representatives, while cloud VR education serves as as an enterprise-level service representative.
+
+### I.1 Cloud VR game
+
+Figure I.1 shows a schematic diagram of cloud VR game. A cloud VR game is a typical use case of cloud VR due to its smooth control experience and multi-person real-time interaction mechanism. Unlike cloud VR video that can use the terminal, CDN and other caching mechanisms to alleviate the experience of problems caused by network instability, cloud VR game needs to complete the transmission of high-capacity media streams and remote control commands from the cloud to the terminal in real time and efficiently.
+
+In terms of content, game content providers are required to inject panoramic game content with exquisite visual effects such as stereoscopic high-definition pictures, etc. In terms of platforms, high-end GPU cluster servers are required to provide functions such as game running, graphics rendering, and audio and video capture/encoding. In the network related to cloud VR game, it is necessary to provide high-bandwidth, low-latency, and low-packet-loss stable data transmission services. In terms of the terminal, it is necessary to accept high-definition graphics data issued by the cloud, and collect corresponding operating instructions data and upload it to the cloud to complete the overall business service process.
+
+![Schematic diagram of cloud VR game architecture showing three layers: content, platform, and terminal.](fa859e4e468bfb2710a94527f2c504af_img.jpg)
+
+The diagram illustrates the architecture of a cloud VR game, organized into three horizontal layers:
+
+- The content of Cloud VR game:** At the top, a rectangular box contains "Game1 Game 2 ... Game n". A blue line descends from this box to the central management system.
+- The platform of Cloud VR game:** This layer consists of a central cloud labeled "Central management system" connected to three edge nodes labeled "Edge node 1", "Edge node 2", and "Edge node n" (with an ellipsis between nodes 2 and n). Below these nodes is a large cloud labeled "Network transmission guarantee such as high bandwidth, low delay and low packet loss".
+- The terminal of Cloud VR game:** At the bottom, three VR headsets are shown, labeled "VR terminal 1", "VR terminal 2", and "VR terminal n" (with an ellipsis between terminals 2 and n). Blue lines labeled "Network transmission" connect the large network transmission cloud to each VR terminal.
+
+F.746.14(22)
+
+Schematic diagram of cloud VR game architecture showing three layers: content, platform, and terminal.
+
+**Figure I.1 – Schematic diagram of cloud VR game**
+
+Cloud VR game requires high-end GPU servers as the foundation for cloud operations. Through mechanisms such as virtual machines and containers, a server has the ability to carry multiple services. This mechanism has the problem of multiple users repeatedly processing common game graphics data resources, and it also puts pressure on the overall carrying capacity of the cloud. In order to solve the above problems, it is necessary to adopt technological innovations such as multi-user cloud computing resources and multi-dimensional sharing of cloud data resources to avoid the waste of multi-processing of general game graphics.
+
+### I.2 Cloud VR live broadcast
+
+Figure I.2 shows a schematic diagram of cloud VR live broadcast. Cloud VR live broadcast, firstly uses VR technology to achieve panoramic view shooting and surround-sound capture of content. It then uses high-performance servers at the edge nodes close to the live broadcast site to complete the stitching and optimization of audio and video streams. Then through the CDN system, with the help of ultra-high bandwidth's network it realizes multi-user-oriented audio and video distribution. The end user completes the online viewing of the corresponding live broadcast through the VR terminal.
+
+![Schematic diagram of cloud VR live broadcast showing the flow from multiple VR live broadcasts through edge stitching optimization, a CDN platform, and network transmission to multiple VR terminals.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg)
+
+The diagram illustrates the architecture of a cloud VR live broadcast system. At the top, a box contains "VR live broadcast 1 VR live broadcast 2 ... VR live broadcast n", labeled "The content of Cloud VR live broadcast". This content flows into a cloud labeled "Edge stitching optimization", which is part of "The platform of Cloud VR live broadcast". Below this is a "CDN" cloud. The platform connects to a large cloud labeled "Network transmission guarantee such as high bandwidth". From this cloud, multiple lines labeled "Network transmission" lead to VR terminals labeled "VR terminal 1", "VR terminal 2", "...", and "VR terminal n", collectively labeled "The terminal of Cloud VR live broadcast". A small code "F.746.14(22)" is visible near the bottom right.
+
+Schematic diagram of cloud VR live broadcast showing the flow from multiple VR live broadcasts through edge stitching optimization, a CDN platform, and network transmission to multiple VR terminals.
+
+**Figure I.2 – Schematic diagram of cloud VR live broadcast**
+
+Cloud VR live broadcast is one of the more complex cloud VR video applications. However, because of its online viewing mode, the interaction process only reflects operations such as switching of the focus range and viewing of digital information, and does not involve more complex real-time interaction and so it belongs to cloud VR weak interaction scenarios. At the same time, during the video watching process, modes such as CDN and VR terminal caching can be used to reduce the impact of live broadcast effects caused by network fluctuations, and at the same time reduce the burden of low network latency. If a corresponding virtual image is added to the cloud VR live screen and a real-time interaction mechanism is provided, its attribute is not only a video viewing mode, but a video plus real-time animation interaction mode, which also requires lower network latency.
+
+### I.3 Cloud VR education
+
+Figure I.3 shows a schematic diagram of cloud VR education. Cloud VR education is an application of the cloud VR industry. Online distance education is carried out through cloud VR technology, which has attributes such as intuition, fun and fairness. Especially for countries and regions with uneven distribution of educational resources, the cloud VR education method can concentrate high-quality educational resources to provide more school students with the same quality of teaching services, and promote overall education equity.
+
+Cloud VR education has two mutually integrated service modes. One is the mode of directly playing VR education videos online, which belongs to the cloud VR weak interactive service; the other is panoramic simulation education, where the cloud presents a dynamic virtual image based
+
+on the educational content and provides real-time interactive functions which belong to the cloud VR strong interactive service.
+
+![Schematic diagram of cloud VR education showing the flow from content providers through a central management system, edge nodes, and a network transmission layer to multiple VR terminals.](ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg)
+
+The diagram illustrates the architecture of cloud VR education. At the top, two rectangular boxes represent the content sources: "Cloud VR panoramic simulation education" and "Cloud VR education video". These are connected by lines to a central cloud labeled "Central management system". Above this connection is the label "The content of Cloud VR education".
+
+The "Central management system" is connected to a row of edge nodes: "Edge node 1", "Edge node 2", an ellipsis, and "Edge node n". To the right of "Edge node n" is a "CDN" (Content Delivery Network) represented by two clouds. This entire layer is labeled "The platform of Cloud VR education".
+
+Below the edge nodes is a large horizontal oval representing the "Network transmission" layer, with the text "Network transmission guarantee such as high bandwidth, low delay and low packet loss" inside. This layer is connected to the edge nodes above and to the VR terminals below.
+
+At the bottom, three VR terminal icons are shown, labeled "VR terminal 1", "VR terminal 2", an ellipsis, and "VR terminal n". These are connected to the network transmission layer. Below them is the label "The terminal of Cloud VR education".
+
+F.746.14(22)
+
+Schematic diagram of cloud VR education showing the flow from content providers through a central management system, edge nodes, and a network transmission layer to multiple VR terminals.
+
+**Figure I.3 – Schematic diagram of cloud VR education**
+
+In most cloud VR education scenarios, the above two methods exist at the same time, so cloud VR also has the attributes of strong and weak interaction at the same time. For cloud VR education-related technical details, implementation processes, and functional composition, further analysis and clarification of recommendations are needed.
+
+## Bibliography
+
+- [b-ITU-T G.1035] Recommendation ITU-T G.1035 (2021), *Influencing factors on quality of experience for virtual reality 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.746.15-202212-I_PDF-E/raw.md b/marked/F/T-REC-F.746.15-202212-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..e0019dfe368f7f80fd0ea79f71f507f3df7b13c3
--- /dev/null
+++ b/marked/F/T-REC-F.746.15-202212-I_PDF-E/raw.md
@@ -0,0 +1,519 @@
+
+
+# Recommendation **ITU-T F.746.15 (12/2022)**
+
+SERIES F: Non-telephone telecommunication services  
+Multimedia services
+
+---
+
+## **Requirements for smart broadband network gateway in multimedia content transmission**
+
+![ITU logo](390120de4fe440c42fea8154fcaad334_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 F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+### **TELEGRAPH SERVICE**
+
+|                                                                 |             |
+|-----------------------------------------------------------------|-------------|
+| Operating methods for the international public telegram service | F.1–F.19    |
+| The gentex network                                              | F.20–F.29   |
+| Message switching                                               | F.30–F.39   |
+| The international telemessage service                           | F.40–F.58   |
+| The international telex service                                 | F.59–F.89   |
+| Statistics and publications on international telegraph services | F.90–F.99   |
+| Scheduled and leased communication services                     | F.100–F.104 |
+| Phototelegraph service                                          | F.105–F.109 |
+
+### **MOBILE SERVICE**
+
+|                                                        |             |
+|--------------------------------------------------------|-------------|
+| Mobile services and multdestination satellite services | F.110–F.159 |
+|--------------------------------------------------------|-------------|
+
+### **TELEMATIC SERVICES**
+
+|                                           |             |
+|-------------------------------------------|-------------|
+| Public facsimile service                  | F.160–F.199 |
+| Teletex service                           | F.200–F.299 |
+| Videotex service                          | F.300–F.349 |
+| General provisions for telematic services | F.350–F.399 |
+
+### **MESSAGE HANDLING SERVICES**
+
+|  |             |
+|--|-------------|
+|  | F.400–F.499 |
+|--|-------------|
+
+### **DIRECTORY SERVICES**
+
+|  |             |
+|--|-------------|
+|  | F.500–F.549 |
+|--|-------------|
+
+### **DOCUMENT COMMUNICATION**
+
+|                                      |             |
+|--------------------------------------|-------------|
+| Document communication               | F.550–F.579 |
+| Programming communication interfaces | F.580–F.599 |
+
+### **DATA TRANSMISSION SERVICES**
+
+|  |             |
+|--|-------------|
+|  | F.600–F.699 |
+|--|-------------|
+
+### **MULTIMEDIA SERVICES**
+
+|  |                    |
+|--|--------------------|
+|  | <b>F.700–F.799</b> |
+|--|--------------------|
+
+### **ISDN SERVICES**
+
+|  |             |
+|--|-------------|
+|  | F.800–F.849 |
+|--|-------------|
+
+## **UNIVERSAL PERSONAL TELECOMMUNICATION**
+
+|  |             |
+|--|-------------|
+|  | F.850–F.899 |
+|--|-------------|
+
+## **ACCESSIBILITY AND HUMAN FACTORS**
+
+|  |             |
+|--|-------------|
+|  | F.900–F.999 |
+|--|-------------|
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.746.15
+
+# Requirements for smart broadband network gateway in multimedia content transmission
+
+## Summary
+
+Recommendation ITU-T F.746.15 specifies requirements for smart broadband network gateway (BNG) in multimedia content transmission, and specifically describes the functional requirements and architecture, security requirements, typical application scenarios and use cases.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                                 |
+|---------|----------------|------------|-------------|--------------------------------------------------------------------------------------------|
+| 1.0     | ITU-T F.746.15 | 2022-12-14 | 16          | <a href="http://www.itu.int/publications/record/11.1002/1000/15189">11.1002/1000/15189</a> |
+
+## Keywords
+
+Interactive experience, network, smart BNG, timeliness.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                               | 1    |
+| 4 Abbreviations and acronyms .....                                          | 1    |
+| 5 Conventions .....                                                         | 2    |
+| 6 Introduction of smart BNG based on artificial intelligence.....           | 3    |
+| 7 Functional requirements and architecture of smart BNG .....               | 3    |
+| 7.1 Overview of smart BNG for multimedia application scenarios .....        | 3    |
+| 7.2 Sub-functions in the layered functional architecture of smart BNG ..... | 4    |
+| 8 Security requirements of smart BNG .....                                  | 6    |
+| Appendix I – Scenarios for smart broadband network gateway .....            | 8    |
+| I.1 Smart class scenario of smart BNG.....                                  | 8    |
+| I.2 Smart family scenario of smart BNG .....                                | 9    |
+| I.3 Smart industry scenario of smart BNG .....                              | 10   |
+| Appendix II – Use cases for smart broadband network gateway.....            | 12   |
+| Bibliography.....                                                           | 15   |
+
+
+
+# Recommendation ITU-T F.746.15
+
+## Requirements for smart broadband network gateway in multimedia content transmission
+
+## 1 Scope
+
+This Recommendation specifies requirements for smart broadband network gateway (BNG) in multimedia content transmission, and specifically describes the functional requirements and architecture, security requirements, typical application scenarios and use cases.
+
+The scope of this Recommendation includes:
+
+- Functional requirements and architecture of smart BNG;
+- Security requirements of smart BNG.
+
+## 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 M.3080] Recommendation ITU-T M.3080 (2021), *Framework of artificial intelligence enhanced telecom operation and management (AITOM)*.
+
+[ITU-T M.3400] Recommendation ITU-T M.3400 (2000), *TMN management functions*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following term defined elsewhere:
+
+**3.1.1 broadband network gateway (BNG)** [b-ITU-T Q.3315]: The access point to the provider's IP network for wireline broadband services.
+
+### 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+None.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|     |                                     |
+|-----|-------------------------------------|
+| 4G  | 4th-Generation Mobile Communication |
+| 5G  | 5th-Generation Mobile Communication |
+| AGV | Automated Guided Vehicle            |
+| AI  | Artificial Intelligence             |
+| AR  | Augmented Reality                   |
+
+|       |                                                             |
+|-------|-------------------------------------------------------------|
+| ARP   | Address Resolution Protocol                                 |
+| BNG   | Broadband Network Gateway                                   |
+| CPU   | Central Processing Unit                                     |
+| DI    | Digital Input                                               |
+| DO    | Digital Output                                              |
+| DSL   | Digital Subscriber Line                                     |
+| EPON  | Ethernet Passive Optical Network                            |
+| FCAPS | Fault, Configuration, Accounting, Performance, and Security |
+| FE    | Fast Ethernet                                               |
+| GE    | Gigabit Ethernet                                            |
+| GPON  | Gigabit Passive Optical Network                             |
+| GRE   | Generic Routing Encapsulation                               |
+| IP    | Internet Protocol                                           |
+| IPSec | Internet Protocol Security                                  |
+| IPTV  | Internet Protocol Television                                |
+| IS-IS | Intermediate System-to-Intermediate System                  |
+| ITMS  | Integrated Terminal Management System                       |
+| LoRa  | Long Range                                                  |
+| NAT   | Network Address Translation                                 |
+| OSPF  | Open Shortest Path First                                    |
+| PON   | Passive Optical Network                                     |
+| RIP   | Routing Information Protocol                                |
+| USB   | Universal Serial Bus                                        |
+| VLAN  | Virtual Local Area Network                                  |
+| VPN   | Virtual Private Network                                     |
+| VR    | Virtual Reality                                             |
+| VxLAN | Visual extensible Local Area Network                        |
+| 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 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.
+
+## 6 Introduction of smart BNG based on artificial intelligence
+
+Smart BNG is designed to improve the speed of multimedia resources transmission and enhance the interaction experience of users. The smart BNG, based on artificial intelligence and advanced hardware equipment, can analyse user preferences and store user data to provide better service for smart family, enterprise and industry scenarios.
+
+Traditional BNG mainly provides network access functions for users. Compared to traditional BNG, smart BNG with an artificial intelligence (AI) computing chip supports the AI model inference function and enhances transmission capability for multimedia content. In addition, smart BNG can support intelligent scenarios, including but not limited to smart education, family and industry scenarios. Smart BNG can install related AI platforms or applications for different scenarios to support intelligent functions.
+
+From a functional perspective traditional BNG can be divided into a data gateway, multimedia gateway and collective control gateway. The data gateway is mainly used for data throughput and for providing delivery support for network protocols. The multimedia gateway supports audio and video content transmission. The collective control gateway supports home control and security service management on the network. Smart BNG has the basic functions of these three gateways, and also enhances these functions based on AI technology for different scenarios.
+
+## 7 Functional requirements and architecture of smart BNG
+
+Clause 7.1 provides an overview of the smart BNG for multimedia application scenarios, and clause 7.2 describes the layered functional architecture of smart BNG.
+
+### 7.1 Overview of smart BNG for multimedia application scenarios
+
+As is shown in Figure 1, the smart BNG is required to support different multimedia application scenarios, including smart industry, smart family, smart class and other scenarios. Therefore, the smart BNG is required to support the access of multiple multimedia devices and multiple ways to access the cloud, which stores multimedia content.
+
+![Figure 1 – Overview of smart BNG. The diagram shows a hierarchical structure. At the top is a cloud labeled 'Cloud (Content of smart industry, smart family, smart class, ...)'. Below the cloud is a large box labeled 'Smart BNG' which contains five stacked layers: 'Platform application layer', 'AI containerized functional component layer', 'Management and forwarding layer', 'Network interface layer', and 'Hardware infrastructure layer'. Below the Smart BNG box is another box labeled 'Multimedia devices'. A vertical line connects the cloud to the Smart BNG box, and another vertical line connects the Smart BNG box to the Multimedia devices box. The text 'F.746.15(22)' is at the bottom right of the diagram.](a234352dfaccdc24745c88eef7724cc6_img.jpg)
+
+F.746.15(22)
+
+Figure 1 – Overview of smart BNG. The diagram shows a hierarchical structure. At the top is a cloud labeled 'Cloud (Content of smart industry, smart family, smart class, ...)'. Below the cloud is a large box labeled 'Smart BNG' which contains five stacked layers: 'Platform application layer', 'AI containerized functional component layer', 'Management and forwarding layer', 'Network interface layer', and 'Hardware infrastructure layer'. Below the Smart BNG box is another box labeled 'Multimedia devices'. A vertical line connects the cloud to the Smart BNG box, and another vertical line connects the Smart BNG box to the Multimedia devices box. The text 'F.746.15(22)' is at the bottom right of the diagram.
+
+**Figure 1 – Overview of smart BNG**
+
+### 7.2 Sub-functions in the layered functional architecture of smart BNG
+
+Figure 2 outlines the sub-functions in the layered functional architecture of the smart BNG.
+
+![Figure 2 – Sub-functional architecture of smart BNG. The diagram shows five layers: Platform application layer, AI containerized functional component layer, Management and forwarding layer, Network interface layer, and Hardware infrastructure layer. A legend at the bottom indicates that solid boxes represent function blocks and dashed boxes represent logic layers.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg)
+
+The diagram illustrates the sub-functional architecture of a smart BNG, organized into five layers:
+
+- Platform application layer:** Contains function blocks for Management platform, IPTV platform, AR/VR platform, and others (....).
+- AI containerized functional component layer:** Divided into two logic layers. The first logic layer, 'AI function set for application scenarios', includes function blocks for Smart industry, Smart family, Smart class, and others (...). The second logic layer, 'AI key technologies', includes function blocks for Image processing, Text processing, Voice processing, and others (...).
+- Management and forwarding layer:** Divided into two logic layers. The first logic layer, 'Management control', includes function blocks for FCAPS, Management interface, AI, Digital twin, and others (...). The second logic layer, 'Data forwarding', includes function blocks for Routing protocol, Tunnel technology, IP technology, and others (...).
+- Network interface layer:** Contains function blocks for USB, ZigBee, Bluetooth, Lora, FE/GE, DI/DO, Third-party, PON, DSL, LAN, WAN, Wi-Fi, 5G/4G, Peripherals, and others (...).
+- Hardware infrastructure layer:** Contains function blocks for CPU, Memory, AI computing chip, Codec chip, Network adapter, and others (...).
+
+Legend: Function block Logic layer
+
+F.746.15(22)
+
+Figure 2 – Sub-functional architecture of smart BNG. The diagram shows five layers: Platform application layer, AI containerized functional component layer, Management and forwarding layer, Network interface layer, and Hardware infrastructure layer. A legend at the bottom indicates that solid boxes represent function blocks and dashed boxes represent logic layers.
+
+**Figure 2 – Sub-functional architecture of smart BNG**
+
+#### 7.2.1 Hardware infrastructure layer
+
+The hardware infrastructure layer is aimed at supporting the basic environment for smart BNG. These hardware infrastructures add AI capabilities on the basis of the universal broadband network gateway. This layer includes the following hardware requirements:
+
+- 1) **Central processing unit (CPU):** The CPU is required to be capable of FP32 floating-point operations at least, so that the CPU can read the model data with higher precision into the memory without losing precision.
+- 2) **Memory:** It is required that the memory is sufficient to support the loading of large model files, the loading of inference data, and support high-speed reading and loading of large model files.
+- 3) **AI computing chip:** In order to ensure the AI model has a low inference delay, the smart BNG is required to use a dedicated chip to support the inference acceleration calculation function of the deep learning model based on the neural network.
+- 4) **Codec chip:** To reduce the load and occupancy of the CPU, the smart BNG is required to support a hardware codec chip to process multimedia data stored in smart BNG.
+- 5) **Network adapter:** The smart BNG is required to support high-bandwidth network cards to satisfy the transmission of large multimedia data.
+
+#### 7.2.2 Network interface layer
+
+The network interface layer is aimed at providing multiple interfaces of the smart BNG to support multiple access methods for the network and users. This layer includes the following requirements:
+
+- 1) **Wired access:** The smart BNG is required to support wired access to the network and provide wired access for users. Common wired access methods include passive optical network (PON) i.e., Ethernet passive optical network (EPON)/gigabit passive optical network (GPON), digital subscriber line (DSL), wide area network (WAN), local area network (LAN) and other methods.
+- 2) **Wireless access:** The smart BNG is required to support wireless access to the network and provide wireless access for users. Common wireless access methods include 5G/4G, WiFi, ZigBee, Lora, Bluetooth and other methods.
+- 3) **Third-party interface:** The smart BNG is required to support specific interfaces for special scenarios or applications to access some peripherals, such as voice interface, video interface and so on.
+
+#### 7.2.3 Management and forwarding layer
+
+As the BNG is required to be managed by a network management system and forward multimedia data from cloud to users, the BNG is required to support management control function and data forwarding function.
+
+The management control function mainly includes fault management, configuration management, accounting management, performance management, security management and interfaces between different management systems. For requirements of fault management, configuration management, accounting management, performance management, and security management refer to clauses 5, 6, 7, 8, and 9 of [ITU-T M.3400].
+
+The data forwarding function mainly includes routing protocols such as open shortest path first (OSPF), routing information protocol (RIP), intermediate system-to-intermediate system (IS-IS), etc., tunnel technology such as virtual extensible local area network (VxLAN), Internet protocol security (IPSec), generic routing encapsulation (GRE), etc., IP technology such as network address translation (NAT), etc., and other network communication technologies.
+
+The smart BNG is also required to support the above functions. In addition, it can use AI, digital twin, and other new technologies to enhance management functions. For requirements of AI enhanced telecom, operation and management, refer to [ITU-T M.3080].
+
+#### 7.2.4 AI containerized functional component layer
+
+The smart BNG is required to provide AI containerized functional components for different application scenarios. There are two types of components; AI functional components for application scenarios, and AI key technologies functional components.
+
+##### 7.2.4.1 AI function set for application scenarios
+
+These scenario functional components are composed of multiple AI functions based on different scenarios. AI application scenarios mainly include the following scenario functional components:
+
+- 1 **Smart industry scenario components:** This functional component is aimed at providing an AI function set related to the smart industry scenario. This scenario mainly includes machine vision, automated guided vehicle (AGV), augmented reality (AR) of equipment and other AI technologies.
+- 2 **Smart family scenario components:** This functional component is aimed at providing an AI function set related to the smart family scenario. This scenario mainly includes voice recognition for controlling furniture, face recognition for security, virtual reality (VR) for immersive movie viewing and other AI technologies.
+
+- 3      **Smart class scenario components:** This functional component is aimed at providing an AI function set related to the smart class scenario. This scenario mainly includes holographic projection for distance education, motion analysis for students, AR for auxiliary teaching and other AI technologies.
+
+Different application scenarios are based on different AI technologies and AI models. The smart BNG is required to support general AI functions for these scenarios, and these AI functions can be re-developed for special applications.
+
+##### 7.2.4.2 AI key technologies
+
+The AI key technology functional components are composed of general AI functions. These components mainly include the following AI functions:
+
+- 1)      **Image processing:** This functional component is aimed at providing AI technologies for image processing. It mainly includes image recognition, object detection, behaviour analysis and other AI technologies.
+- 2)      **Text processing:** This functional component is aimed at providing natural language processing for text processing. It mainly includes semantic analysis, keyword extraction and other AI technologies.
+- 3)      **Voice processing:** This functional component is aimed at providing AI technologies for voice processing. It mainly includes voice recognition, automatic interaction, voice synthesis and other AI technologies.
+
+Different applications are based on different AI technologies and AI models. The smart BNG is required to support multiple AI key technologies, and these technologies can be used in combination according to different requirements. These AI technologies can be used to train different AI models.
+
+#### 7.2.5 Platform application layer
+
+The platform application layer is aimed at supporting multimedia applications through smart BNG. The following platforms are recommended to be supported:
+
+- 1)      **Network management platform:** The smart BNG is required to be managed by upstream equipment or by a system such as integrated terminal management system (ITMS).
+- 2)      **IPTV platform:** The smart BNG is required to support Internet protocol television (IPTV) business for smart family scenario.
+- 3)      **AR/VR platform:** The smart BNG is required to support AR/VR business for smart family and smart industrial scenarios.
+
+The smart BNG is required to support general multimedia platforms, and the platform can be re-developed for special applications.
+
+## 8 Security requirements of smart BNG
+
+The smart BNG is recommended to support following security functions:
+
+- 1)      **Basic firewall function:** The smart BNG is recommended to support the opening and closing of protocol ports, and the protocols corresponding to pre-set common ports (such as 80, 8080, 21, 23, etc.).
+- 2)      **Access control function:** The smart BNG is recommended to support the implementation of corresponding access control policies based on parameters such as source/destination MAC address, IP quintuple, and time period.
+- 3)      **Content filtering function:** The smart BNG is recommended to filter content based on URL and keyword. It is also required to support setting black and white lists and implementing import and export operations.
+
+- 4) **Preventing ARP attack function:** The smart BNG is recommended to support MAC address and static binding with IP addresses and address resolution protocol (ARP) broadcast storm suppression function.
+- 5) **Content encryption and decryption function:** The smart BNG is recommended to support encryption and decryption of transmission content as requirements of users.
+
+## Appendix I
+
+### Scenarios for smart broadband network gateway
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This appendix describes the typical scenarios of smart BNG. The typical scenarios include but are not limited to class, family and industry.
+
+### I.1 Smart class scenario of smart BNG
+
+Smart BNG can assist in many types of interactive classrooms, and help teachers better understand students. The smart BNG is recommended to support following interactive classrooms:
+
+- 1) **Physical interactive classroom:** It means that teachers and students carry out teaching activities in a physical classroom. The smart BNG can support various forms of interactions, including video system, voice system and other multimedia systems.
+- 2) **Online interactive classroom:** This teaching mode is not limited by time and space. Through the smart BNG, video, voice, image and other multimedia content can be transmitted between two or more different classrooms.
+- 3) **Cloud classroom:** This teaching mode can carry both physical classroom and online classroom, and support teaching cross-regional in real-time. The education system is deployed in the cloud, and delivers the education resources to the classroom through the smart BNG.
+
+![Diagram illustrating the deployment situation of smart BNG in a smart class scenario. At the top, an 'Education platform' cloud contains 'Live streaming', 'AI model training', and 'VPN networking' components. Below it, a 'Wide area network' cloud is connected via a dashed red VPN link. At the bottom, two 'Classroom' boxes are shown. Each classroom contains a 'Smart BNG' connected to a 'Teaching facility' (laptop) and a 'Camera'. The Smart BNGs are connected to the Wide area network via dashed red VPN links and solid black Logical links. A legend at the bottom indicates that solid lines represent Logical links and dashed red lines represent VPN links. The diagram is labeled F.746.15(22).](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg)
+
+Diagram illustrating the deployment situation of smart BNG in a smart class scenario. At the top, an 'Education platform' cloud contains 'Live streaming', 'AI model training', and 'VPN networking' components. Below it, a 'Wide area network' cloud is connected via a dashed red VPN link. At the bottom, two 'Classroom' boxes are shown. Each classroom contains a 'Smart BNG' connected to a 'Teaching facility' (laptop) and a 'Camera'. The Smart BNGs are connected to the Wide area network via dashed red VPN links and solid black Logical links. A legend at the bottom indicates that solid lines represent Logical links and dashed red lines represent VPN links. The diagram is labeled F.746.15(22).
+
+Figure I.1 – The deployment situation of smart BNG in smart class scenario
+
+Figure I.1 shows the deployment situation of smart BNG in a smart class scenario. There are many smart terminals in the class, including tablets, screen projection equipment, electronic whiteboard and others. These teaching facilities and cameras in a classroom are connected with smart BNG. The AI model training is deployed on the education cloud platform. This module gets data through the smart BNG and trains related AI models, and includes handwriting recognition, and behaviour analysis to help teachers correct homework and understand students. The AI models are sent to smart BNG to do edge inference for smart terminal applications. Different classrooms connect with each other through smart BNG to build a virtual private network (VPN) link. Since the IP addresses of the smart BNG for school are private network addresses, they are allocated by the VPN networking module deployed on the education cloud platform. Through VPN links, the education application on cloud can send to multiple classrooms located in different regions.
+
+### I.2 Smart family scenario of smart BNG
+
+Multimedia applications are provided to the family through smart BNG. The smart BNG is recommended to support following applications for smart family:
+
+- 1) **Smart home:** The furniture has WI-FI modules which can be connected with smart BNG, and they can be controlled by a unified control panel or an application on mobile terminal. The furniture includes television, stereo, air conditioner, light and others. Users can control the furniture through a control panel, application or voice messages, and control messages are sent to furniture through smart BNG.
+- 2) **Family entertainment:** With the development of network and IT technology, people can experience cloud games and VR/AR games in the home. These games are rendered in the smart family cloud platform, and smart BNG unzips these videos. People play VR/AR, cloud games without any high-performance processor and graphics card, they just need gaming equipment to experience these games.
+- 3) **Health and security:** A camera in the home can monitor the elderly at home. If something unexpected happens, the security system will notify the family as soon as possible. If a stranger breaks into the house, it also can send out a warning alarm to protect personal and property safety.
+
+![Diagram illustrating the deployment situation of smart BNG in a smart family scenario. At the top, a cloud labeled 'Smart family platform' contains three service boxes: 'VR/AR games', 'IPTV', and 'Smart home service'. Below this is a cloud labeled 'Wide area network'. At the bottom, a dashed box labeled 'Home' contains several devices: 'IPTV', 'VR/AR game' (represented by a headset icon), 'Smart BNG' (represented by a router icon), 'Mobile terminal' (represented by a smartphone icon), 'Family security' (represented by a camera icon), and 'PC' (represented by a laptop icon). All devices in the 'Home' box are connected to the 'Smart BNG'. A double-headed arrow connects the 'Smart family platform' cloud to the 'Wide area network' cloud, which in turn connects to the 'Smart BNG' in the 'Home' box.](fa859e4e468bfb2710a94527f2c504af_img.jpg)
+
+Diagram illustrating the deployment situation of smart BNG in a smart family scenario. At the top, a cloud labeled 'Smart family platform' contains three service boxes: 'VR/AR games', 'IPTV', and 'Smart home service'. Below this is a cloud labeled 'Wide area network'. At the bottom, a dashed box labeled 'Home' contains several devices: 'IPTV', 'VR/AR game' (represented by a headset icon), 'Smart BNG' (represented by a router icon), 'Mobile terminal' (represented by a smartphone icon), 'Family security' (represented by a camera icon), and 'PC' (represented by a laptop icon). All devices in the 'Home' box are connected to the 'Smart BNG'. A double-headed arrow connects the 'Smart family platform' cloud to the 'Wide area network' cloud, which in turn connects to the 'Smart BNG' in the 'Home' box.
+
+**Figure I.2 – The deployment situation of smart BNG in a smart family scenario**
+
+Figure I.2 shows the deployment situation of a smart BNG in a smart family scenario. There are many smart terminals in the home, including IPTV, screen projection equipment, VR/AR equipment and others. These smart terminals and cameras in the home are connected with smart BNG. The VR/AR games and IPTV are deployed on the smart family cloud platform. This module renders VR/AR games, and sends them to game terminals through smart BNG. The content of IPTV is sent to smart BNG to provide service. The smart family cloud platform can provide other services, including health monitoring, security, and so on.
+
+### I.3 Smart industry scenario of smart BNG
+
+Multimedia applications are provided to industry through smart BNG. The smart BNG is recommended to support following applications for smart industry:
+
+- 1) **Machine vision:** The camera in industry can collect image data and upload data to a smart industry cloud platform to train AI models through smart BNG. After training, these AI models are sent to corresponding equipment. The AI models can be used in object sorting, quality inspection, object measurement and other industry applications. The smart BNG do inference based on AI trained models for these applications.
+- 2) **Smart office service:** The smart office services are deployed in the smart industry cloud platform. And the branches can use these services through smart BNG. These services can be used directly on the cloud, or can be downloaded locally.
+- 3) **Security:** Cameras in industry can monitor staff working. If something dangerous happens, the security system will notify the whole industry as soon as possible, and it also can send out a warning alarm to protect personal and property safety.
+
+![Diagram illustrating the deployment situation of smart BNG in a smart industry scenario. A central 'Wide area network' cloud is connected to three sites: Site A, Site B, and Site C. Site A and Site C each have a 'Smart BNG' connected to three computers. Site B has a 'Smart BNG' connected to a 'Camera' and three computers. Above the central cloud is a 'Smart industry platform' cloud containing 'Smart office service', 'AI model training', and 'VPN orchestrator' modules. Control links (blue dashed lines with arrows) connect the platform to the central cloud and the Smart BNGs at Sites A and C. VPN links (red dashed lines) connect the Smart BNGs at Sites A, B, and C through the central cloud. Logical links (solid black lines) connect the Smart BNGs to the terminals at each site. A legend at the bottom identifies the link types: solid line for Logical link, dashed red line for VPN link, and dashed blue line with arrow for Control link. The text 'F.746.15(22)' is in the bottom right corner.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg)
+
+Diagram illustrating the deployment situation of smart BNG in a smart industry scenario. A central 'Wide area network' cloud is connected to three sites: Site A, Site B, and Site C. Site A and Site C each have a 'Smart BNG' connected to three computers. Site B has a 'Smart BNG' connected to a 'Camera' and three computers. Above the central cloud is a 'Smart industry platform' cloud containing 'Smart office service', 'AI model training', and 'VPN orchestrator' modules. Control links (blue dashed lines with arrows) connect the platform to the central cloud and the Smart BNGs at Sites A and C. VPN links (red dashed lines) connect the Smart BNGs at Sites A, B, and C through the central cloud. Logical links (solid black lines) connect the Smart BNGs to the terminals at each site. A legend at the bottom identifies the link types: solid line for Logical link, dashed red line for VPN link, and dashed blue line with arrow for Control link. The text 'F.746.15(22)' is in the bottom right corner.
+
+**Figure I.3 – The deployment situation of smart BNG in smart industry scenario**
+
+Figure I.3 shows the deployment situation of smart BNG in a smart industry scenario. The terminals used in industry include cameras, computers, AGVs, and other equipment. These terminals are connected with the smart BNG. The AI model training is deployed on the industry cloud platform. This module gets data through smart BNG and trains related AI models for various applications to improve production. The AI models are sent to smart BNG to do edge inference for image identification applications. Different branches connect with each other through smart BNG to build VPN links. If the IP addresses of the company are public network addresses, they can build VPN links directly. Otherwise, VPN links can be built by cloud as in the smart class scenario. The VPN orchestrator deployed on the industry cloud platform can manage VPN links based on control links.
+
+## Appendix II
+
+### Use cases for smart broadband network gateway
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Appendix II describes use cases for smart broadband network gateway.
+
+Table II.1 describes live streaming in a smart education scenario.
+
+**Table II.1 – Live streaming in education scenario**
+
+| Title                      | Live streaming in a smart education scenario                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Description                | <p>Live video is a kind of teaching method in a smart education scenario. The education platform forwards live streaming from different sources through VPN tunnels among the smart BNGs. With VPN tunnels the platform sends living streaming by multicast instead of unicast. The process consists of the following three steps:</p> <ol style="list-style-type: none"> <li>1) The education platform gets live video streaming from different sources by unicast;</li> <li>2) It builds VPN tunnels among multiple smart BNGs;</li> <li>3) The platform sends the living streaming through tunnels with multicast and the smart BNGs receive streaming from VPN tunnels.</li> </ol> |
+| Roles                      | Network service provider, live video sources, classes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| Figure (optional)          | <img alt="Diagram of live streaming in a smart education scenario. At the top, an 'Education platform' cloud contains 'Education video library', 'Live streaming engine', and 'VPN network'. It is connected to three 'Live video source' boxes. Below it, a 'Wide area network' cloud is connected via dashed red lines to two 'Smart BNG' units. Each 'Smart BNG' is connected to a 'Live streaming receiver' box. The 'Smart BNG' and 'Live streaming receiver' are grouped into 'Classroom 1' and 'Classroom 2' dashed boxes. The label F.746.15(22) is in the bottom right." data-bbox="582 1093 1428 1753" src="b03533cc9198ad21d619252486969839_img.jpg"/>                      |
+| Pre-conditions (optional)  | The VPN among the smart BNGs and the education platform should be built.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| Post-conditions (optional) |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+Table II.2 describes a family VR/AR games use case in a smart family scenario.
+
+**Table II.2 – Family VR/AR games in smart family scenario**
+
+| Title                      | Family VR/AR games in smart family scenario                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Description                | <p>The smart BNG has an intelligent and open system to run various kinds of applications and it also supports VR/AR games in a family scenario. The smart family platform provides the VR/AR game service and rendering service. The smart BNG runs VR/AR game applications and provides computing resources to support VR/AR streaming handling. The process consists of the following two steps:</p> <ol style="list-style-type: none"> <li>1) The smart BNG installs the VR/AR game application and it links VR/AR terminals via Wi-Fi.</li> <li>2) The smart family platform sends VR/AR game rendered video streaming to the smart BNG and the VR/AR application installed in the BNG handles the streaming and sends to the terminal according to the related command.</li> </ol>                                                                                                                                                               |
+| Roles                      | Network service provider, family VR/AR games provider, player                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| Figure (optional)          | <img alt="Diagram illustrating the architecture of family VR/AR games in a smart family scenario. At the top, a light blue cloud labeled 'Smart family platform' contains two boxes: 'VR/AR games service' and 'Rendering engine'. Below it, a dark blue cloud labeled 'Wide area network' is connected via a double-headed arrow. At the bottom, a dashed box labeled 'Home' contains a 'Smart BNG' (represented by a router icon), a 'VR/AR game application' (represented by a box), and a person wearing a VR headset. The Smart BNG is connected to the Wide area network and to the VR/AR game application. The VR/AR game application is connected to the person wearing the VR headset. A Wi-Fi symbol indicates a connection between the Smart BNG and the VR headset. The reference 'F.746.15(22)' is shown in the bottom right corner of the diagram area." data-bbox="738 869 1276 1753" src="04b5df354878bcb2868795f8dbdf2726_img.jpg"/> |
+| Pre-conditions (optional)  | The VR/AR game applications can be installed in the smart BNG.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| Post-conditions (optional) |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+Table II.3 describes AI model training for machine vision in an industry scenario.
+
+**Table II.3 – AI model training for machine vision in industry scenario**
+
+| Title                      | AI model training for machine vision in industry scenario                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Description                | <p>In machine vision use case (such as industrial quality inspection, intelligent picking, etc.), the machine vision AI model needs to be trained when new samples appear.</p> <p>The smart industry platform has different components including AI platform environment, AI model library and vision model training engine, etc. The smart industry platform provides computing resources for machine vision AI model training. The process consists of the following three steps:</p> <ol style="list-style-type: none"> <li>1) The samples are produced for machine vision AI model training at the production site. The smart BNG collects all samples and sends them to the smart industry platform through a VPN between smart BNG and the platform.</li> <li>2) The smart industry platform trains the machine vision AI model after receiving the production samples.</li> <li>3) The platform sends the trained vision inference model to the smart BNG, and the smart BNG uses the AI model to do inference for productions.</li> </ol> |
+| Roles                      | Network service provider, smart industry platform vendor, industry manufacturer.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| Figure (optional)          | <img alt="Diagram illustrating the AI model training architecture. At the top, a light blue cloud labeled 'Smart industry platform' contains three boxes: 'AI platform', 'AI model library', and 'Vision model training engine'. Below it, a dark blue cloud labeled 'Wide area network' is connected via a red dashed double-headed arrow. At the bottom, a dashed box labeled 'Production site' contains a 'Smart BNG' (represented by a router icon) connected to two boxes: 'Samples collection' and 'Vision inference'. A red dashed double-headed arrow connects the Smart BNG to the Wide area network cloud." data-bbox="737 1012 1276 1881" src="dfe0567f7f23e65eac31fd8a281ea347_img.jpg"/> <p style="text-align: right;">F.746.15(22)</p>                                                                                                                                                                                                                                                                                              |
+| Pre-conditions (optional)  | The VPN between the smart BNG and the smart industry platform should be built.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| Post-conditions (optional) |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+## Bibliography
+
+[b-ITU-T Q.3315] Recommendation ITU-T Q.3315 (2015), *Signalling requirements for flexible network service combination on broadband network gateway*.
+
+
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.746.19-202512-I_PDF-E/raw.md b/marked/F/T-REC-F.746.19-202512-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..671609734a7c17f624c836939de89c18142eec39
--- /dev/null
+++ b/marked/F/T-REC-F.746.19-202512-I_PDF-E/raw.md
@@ -0,0 +1,560 @@
+
+
+Recommendation
+
+**ITU-T F.746.19 (12/2025)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+---
+
+**Requirements for conversion and collaboration methods in a hybrid work environment**
+
+![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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.746.19
+
+## Requirements for conversion and collaboration methods in a hybrid work environment
+
+## Summary
+
+Hybrid work environments refer to a method of collaboration among users in different physical locations. With the recent spread of epidemics such as COVID-19, non-face-to-face meetings and remote work are becoming more popular, and it is expected that they will continue in a hybrid way even though the epidemic has decreased or dissipated in the future.
+
+However, hybrid work environment can lead to a lack of mutual understanding when conducting a conversation, and a discussion based on false facts can lead to inappropriate conclusions. In addition, there are cases where it is difficult to prepare minutes because the other party's exact intention is not understood.
+
+The purpose of Recommendation ITU-T F.746.19 is to improve hybrid work methods through artificial intelligence technology to improve the efficiency and accuracy of conversation in a hybrid environment.
+
+## History\*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.746.19 | 2025-12-14 | 21          | 11.1002/1000/16579 |
+
+## Keywords
+
+Conversation system, hybrid work environment.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <https://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                        | 1  |
+| 4    | Abbreviations and acronyms .....                                                                  | 1  |
+| 5    | Conventions .....                                                                                 | 1  |
+| 6    | Background.....                                                                                   | 2  |
+| 7    | Comparison of typical face-to-face meeting and hybrid work environment .....                      | 3  |
+| 7.1  | Agenda.....                                                                                       | 3  |
+| 7.2  | Discussion.....                                                                                   | 3  |
+| 7.3  | Meeting minutes .....                                                                             | 3  |
+| 7.4  | Minutes sharing .....                                                                             | 3  |
+| 8    | Benefits of real-time document co-authoring in a hybrid work environment .....                    | 4  |
+| 8.1  | Traditional document co-authoring .....                                                           | 4  |
+| 8.2  | Real-time document co-authoring with emotion .....                                                | 4  |
+| 8.3  | Benefits of document co-authoring .....                                                           | 4  |
+| 9    | General requirements of conversation and collaboration methods in a hybrid work environment ..... | 5  |
+| 9.1  | Functional requirements .....                                                                     | 5  |
+| 9.2  | Non-functional requirements .....                                                                 | 5  |
+| 9.3  | Asynchronous communication requirements .....                                                     | 6  |
+| 10   | Requirements of components for real-time document co-authoring function.....                      | 7  |
+| 10.1 | Master view .....                                                                                 | 7  |
+| 10.2 | User view (individual view) .....                                                                 | 7  |
+| 10.3 | Reflection of real-time modifications.....                                                        | 7  |
+| 10.4 | Revision alert for original author's wording.....                                                 | 7  |
+| 10.5 | Reflection of personal status .....                                                               | 7  |
+| 10.6 | Definition of personal status.....                                                                | 7  |
+| 11   | Hybrid work environment workflow .....                                                            | 8  |
+| 11.1 | Real-time document co-authoring .....                                                             | 8  |
+| 11.2 | Hybrid meeting environment.....                                                                   | 9  |
+| 11.3 | Speech recognition .....                                                                          | 9  |
+| 11.4 | Face recognition .....                                                                            | 9  |
+| 11.5 | Speaker identification.....                                                                       | 9  |
+| 11.6 | Question and dialogue processing .....                                                            | 9  |
+| 11.7 | Emotion analysis .....                                                                            | 10 |
+
+|                                    | Page |
+|------------------------------------|------|
+| 11.8 Statistical analysis .....    | 10   |
+| 11.9 Authentication .....          | 10   |
+| 11.10 Domain knowledge-based ..... | 10   |
+| 11.11 Guest book.....              | 10   |
+
+# Recommendation ITU-T F.746.19
+
+## Requirements for conversion and collaboration methods in a hybrid work environment
+
+# 1 Scope
+
+This Recommendation includes:
+
+- Requirements for conducting a hybrid work environment.
+- Use cases regarding the meeting method for a hybrid work environment.
+- Definition of the meeting workflow for a hybrid work environment.
+
+## 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.3] Recommendation ITU-T F.746.3 (2015), *Intelligent question answering service framework*.
+
+[IEEE P3300] IEEE P3300 (2022), *Moving Picture Audio and Data Coding by Artificial Intelligence (MPAI) Technical Specification Multimodal Conversion Version 1.2*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+None.
+
+### 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 hybrid work:** A flexible working model where employees split their time between a physical workplace and a remote location.
+
+NOTE – Examples of a remote location are the employee's home or another workspace.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviation and acronym:
+
+KB Knowledge Base
+
+UI User Interface
+
+VPN Virtual Private 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**" 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 Background
+
+With the recent spread of epidemics such as COVID-19, non-face-to-face meetings and remote work are becoming more popular, and it is expected that they will continue in a hybrid way even though the epidemic decreases or dissipates in the future. In response to this situation, this Recommendation identifies requirements and provides guidance to overcome these issues.
+
+Traditional remote workers have simply accessed the company's internal systems via a virtual private network (VPN), etc., and have used online meeting tools when holding meetings.
+
+However, this work approach is not perfectly efficient. Additionally, not only is it difficult to determine whether the stakeholders have empathy for the issue, but it is difficult to check the work efficiency and status. Moreover, it is not easy to respond to the issue from the point of view of the stakeholders who manage the team or a specific task.
+
+For example, a person may want to share and explain some discussion issues with only a shared screen during an online meeting. However, in this way it is not easy to understand the workflow or contextual information of the discussion. These issues can eventually produce an incorrect conclusion. Accordingly, there is a need for better working methods in which the participants and stakeholders can correctly understand the work environment and empathize with any discussion issues when they arise. Clause 7 presents a comparison between traditional meetings and meetings conducted in a hybrid environment.
+
+Figure 1 illustrates how on-site and remote workers collaborate within a hybrid work environment through an artificial intelligence (AI)-assisted meeting system and real-time document co-authoring.
+
+![Diagram illustrating a hybrid work environment. On the left, an 'On-site worker' icon is shown. In the center, a box labeled 'Hybrid meeting' contains icons for 'Co-authoring with emotion' and 'Meeting minutes and distribution'. On the right, a 'Remote worker' icon is shown. Double-headed arrows connect the On-site worker to the Hybrid meeting box, and the Hybrid meeting box to the Remote worker. A small text 'F.746.19(25)' is visible at the bottom right of the diagram.](731f533b0599c8e42a063f06e4332045_img.jpg)
+
+The diagram shows a central box labeled "Hybrid meeting" containing three items: "Co-authoring with emotion" (represented by a document and pencil icon), "Meeting minutes and distribution" (represented by a document icon), and a video call icon at the top. To the left of this box is an "On-site worker" icon (a person at a desk). To the right is a "Remote worker" icon (a person with a laptop and signal waves). Double-headed arrows connect the On-site worker to the Hybrid meeting box, and the Hybrid meeting box to the Remote worker. A small text "F.746.19(25)" is visible at the bottom right of the diagram.
+
+Diagram illustrating a hybrid work environment. On the left, an 'On-site worker' icon is shown. In the center, a box labeled 'Hybrid meeting' contains icons for 'Co-authoring with emotion' and 'Meeting minutes and distribution'. On the right, a 'Remote worker' icon is shown. Double-headed arrows connect the On-site worker to the Hybrid meeting box, and the Hybrid meeting box to the Remote worker. A small text 'F.746.19(25)' is visible at the bottom right of the diagram.
+
+**Figure 1 – Conversation in a hybrid work environment**
+
+Hybrid work differs from conventional remote work by enabling on-site and remote participants to engage in simultaneous and seamless communication, fostering more effective real-time collaboration. This structure enables real-time collaboration between on-site and remote participants
+
+by integrating AI-based models for speech, emotion, and domain knowledge analysis, ensuring consistent understanding and efficient workflow management.
+
+## 7 Comparison of typical face-to-face meeting and hybrid work environment
+
+A typical meeting consists of elements such as agenda, discussions, minutes, and sharing, as shown in Figure 2. These are basic components. The basic components can be implemented as hybrid work methods through input/output mechanisms due to the artificial intelligence requirements subdivided in clause 9.
+
+There are technical differences between the typical meeting and a hybrid work environment. In a hybrid work environment, factors such as fact-checking based on domain knowledge, speaker identification, authentication, and emotion recognition, which are introduced in clause 8, are added.
+
+![Figure 2: Basic components of typical meeting. A flowchart showing four stages: Agenda, Discussion, Meeting minutes, and Minutes sharing. Each stage is in a box with an icon below it: Agenda (hand with pen on clipboard), Discussion (speech bubble), Meeting minutes (stack of papers), and Minutes sharing (person with laptop and speech bubble).](7a0db9703b68b3d06cdaeefc084c0006_img.jpg)
+
+```
+graph LR; A[Agenda] --> B[Discussion]; B --> C[Meeting minutes]; C --> D[Minutes sharing];
+```
+
+Figure 2: Basic components of typical meeting. A flowchart showing four stages: Agenda, Discussion, Meeting minutes, and Minutes sharing. Each stage is in a box with an icon below it: Agenda (hand with pen on clipboard), Discussion (speech bubble), Meeting minutes (stack of papers), and Minutes sharing (person with laptop and speech bubble).
+
+Figure 2 – Basic components of typical meeting
+
+### 7.1 Agenda
+
+The agenda of the meeting is set before the meeting starts. It can also identify the topic by using words or phrases that are frequently repeated within the meeting. A suitable domain is selected according to the agenda, and it is possible to check whether the content of the speech is consistent with the topic of the meeting through the model within the domain.
+
+### 7.2 Discussion
+
+When a discussion starts during the meeting, the knowledge base (KB) is used to check whether the speaker's statements are factually accurate. If not, a note requesting reconfirmation can be added to the meeting minutes.
+
+### 7.3 Meeting minutes
+
+Minutes are important outcomes that record the contents of the meeting so that the main points can be addressed. In this proposal, it is easy to manage the history by collecting and recording speaker separation recognition, summary of main contents, nuances of the speaker, speaking time, etc.
+
+The detailed user interface (UI) of the meeting minutes can be suggested through further detailed work afterwards.
+
+### 7.4 Minutes sharing
+
+The meeting minutes are automatically distributed to all attendees based on the guestbook, and if the person in charge and the deadline for handling is specified in the meeting minutes, important matters are notified to the person in charge to prevent omissions and improve work accuracy.
+
+## **8 Benefits of real-time document co-authoring in a hybrid work environment**
+
+This clause discusses the distinction between traditional paperwork and real-time document co-authoring. It also highlights the advantages of co-authoring documents in real time within a hybrid environment.
+
+### **8.1 Traditional document co-authoring**
+
+Traditional document co-authoring involves one person working on a document at a time. While the document can be shared with others, simultaneous collaboration is not possible.
+
+Since then, due to the popularization of the cloud, joint editing has become possible by updating files on the server, but it has not been easy to obtain accurate feedback and contextual information from each other.
+
+### **8.2 Real-time document co-authoring with emotion**
+
+Real-time document co-authoring enables multiple people to collaborate on a document simultaneously. Users can view the document in real time and observe changes made by others. Additionally, the emotional state of the original author and other users is identified and stored as metadata along with the text, facilitating effective communication. To enhance contextual understanding and improve interpretation of collaborative intent, the concept of personal status is introduced, capturing users' emotional and cognitive states as part of the co-authoring metadata.
+
+### **8.3 Benefits of document co-authoring**
+
+The advantages of collaborative document editing can be summarized as follows.
+
+#### **8.3.1 Enhanced collaboration**
+
+Real-time co-authoring of documents enhances collaboration among employees. Users can work simultaneously on documents, view changes made by others, share ideas, provide feedback, and complete documents faster and more efficiently.
+
+#### **8.3.2 Increased productivity**
+
+Real-time co-authoring of documents helps improve employee productivity. Users can collaborate on documents simultaneously, reducing the time required to complete them.
+
+#### **8.3.3 Improved communication**
+
+Real-time co-authoring of documents enhances communication between employees. Simultaneous collaboration and visibility of changes made by others help prevent misunderstandings.
+
+#### **8.3.4 Increased flexibility**
+
+Real-time co-authoring of documents provides flexibility for employees. They can work on documents from home while others work from the office, allowing them to complete documents without being constrained by commuting times.
+
+The conversation and collaboration methods requirements necessary to realize these advantages are as follows.
+
+Figure 3 illustrates the concept of co-authoring, showing that co-authoring depicts a collaborative editing space where stakeholders can review content, provide comments, and express emotional feedback. This figure demonstrates an integrated environment that supports efficient collaboration and communication during document authoring.
+
+![Figure 3: A screenshot of a document snippet illustrating co-authoring. At the top, there are three icons: a smiling face with heart eyes, a neutral face, and a face with wide eyes. Below the icons is a text box containing the following text: 'This is sample test for co-authoring. Every stakeholder can review the content and provide comments including emotional feedback. This method is highly effective for collaborating with multiple stakeholders during the document authoring process.' The text 'provide comments' and 'multiple stakeholders' are underlined. The entire image is enclosed in a blue border.](967c30813761a8952ecc5e16bf42ea45_img.jpg)
+
+Figure 3: A screenshot of a document snippet illustrating co-authoring. At the top, there are three icons: a smiling face with heart eyes, a neutral face, and a face with wide eyes. Below the icons is a text box containing the following text: 'This is sample test for co-authoring. Every stakeholder can review the content and provide comments including emotional feedback. This method is highly effective for collaborating with multiple stakeholders during the document authoring process.' The text 'provide comments' and 'multiple stakeholders' are underlined. The entire image is enclosed in a blue border.
+
+F.746.19(25)
+
+**Figure 3 – Co-authoring in a hybrid work environment**
+
+## **9 General requirements of conversation and collaboration methods in a hybrid work environment**
+
+The conversation and collaboration methods are recommended to enable seamless real-time communication, facilitating both synchronous and asynchronous collaboration. The detailed requirements are as follows.
+
+### **9.1 Functional requirements**
+
+To ensure the system meets the intended operational objectives and delivers value to its users, it is recommended to define and implement the following functional requirements. These requirements focus on the specific features and behaviours the system must support to facilitate effective communication and collaboration in a hybrid work environment.
+
+#### **9.1.1 Real-time communication**
+
+It is recommended to include features that allow for smooth and uninterrupted live interactions. This should encompass high-quality video calls, instant messaging with minimal latency, efficient file sharing capabilities, and comprehensive user status indicators, such as showing whether a user is online, offline, or busy, ensuring real-time awareness among participants.
+
+#### **9.1.2 Access controls and notifications**
+
+It is recommended to implement access controls that are dynamically based on user roles, such as administrative privileges or regular user permissions. Furthermore, the system is recommended to allow users to customize their notification preferences to reduce distractions and improve usability based on individual needs or organizational policies.
+
+#### **9.1.3 Multi-platform compatibility**
+
+It is recommended to ensure that the system operates smoothly and consistently across various platforms and devices, including desktops, laptops, smartphones, and tablets, providing a uniform experience regardless of the hardware or operating system being used.
+
+### **9.2 Non-functional requirements**
+
+To enhance overall performance and usability, it is recommended to adhere to the following non-functional requirements:
+
+#### **9.2.1 Performance optimization**
+
+It is recommended to be optimized to ensure quick and efficient responses, minimizing delays even during peak usage periods.
+
+#### **9.2.2 Scalability**
+
+It is recommended to design the system to handle an increasing number of users or concurrent sessions without compromising performance or reliability.
+
+#### **9.2.3 Security**
+
+The system is recommended to implement robust security measures, including end-to-end encryption, multi-factor authentication, and regular security updates to protect user data and prevent unauthorized access.
+
+#### **9.2.4 Compliance**
+
+It is recommended to ensure that the system adheres to all relevant legal and regulatory standards, including data privacy laws and industry-specific compliance requirements.
+
+#### **9.2.5 Accessibility and usability**
+
+It is recommended to incorporate features that promote accessibility for a diverse range of users, including those with disabilities. This should include an intuitive interface, assistive technology support, and a modular architecture that facilitates straightforward maintenance, updates, and the addition of new features.
+
+### **9.3 Asynchronous communication requirements**
+
+For communication that does not occur in real time, it is recommended to provide robust support for asynchronous collaboration. This includes features like cloud-based file sharing that allows easy access from multiple locations, maintaining a comprehensive and searchable history of past conversations, and seamless integration with other widely used collaboration tools to ensure continuity and efficiency in workflows.
+
+#### **9.3.1 Standardized template utilization**
+
+Standardized template utilization is recommended to maintain consistency.
+
+#### **9.3.2 Summary and action items inclusion**
+
+Every communication is recommended to include a core summary and a list of action items.
+
+#### **9.3.3 Centralized document repository**
+
+Centralized document repository can optionally store all asynchronous communication materials.
+
+#### **9.3.4 Searchable format**
+
+A searchable format is required to ensure that documents and messages are stored in a text-based format.
+
+#### **9.3.5 Categorization and tagging system**
+
+Categorization and tagging system are required to organize documents and communication material.
+
+#### **9.3.6 Feedback and participation encouragement**
+
+Feedback and participation functions are recommended to be provided.
+
+#### **9.3.7 Feedback system**
+
+Asynchronous communication system is recommended to provide functionalities for submitting opinions, questions, and feedback.
+
+#### **9.3.8 Updates and reminder system**
+
+Updates and reminder system is recommended to provide updates on project progress, significant milestones, and changes.
+
+# **10 Requirements of components for real-time document co-authoring function**
+
+A hybrid work environment is a working approach that combines traditional offline work with digital technology, and it is gradually gaining importance. In such an environment, collaborative document authoring refers to the process of multiple members within an organization working together to create, edit, and manage documents. To carry out these tasks, it is required to define the requirements of the components.
+
+### **10.1 Master view**
+
+The master view is required to allow monitoring of the master's operations. Users can observe the actions of the master and provide feedback, ensuring project quality and correctness.
+
+### **10.2 User view (individual view)**
+
+The user view is required to enable real-time concurrent document co-authoring, allowing each person to co-author the document by performing activities such as writing, editing, and deleting within their own view.
+
+### **10.3 Reflection of real-time modifications**
+
+Co-authoring in a hybrid work environment is required to reflect real-time changes, additions, and deletions made by multiple users instantly.
+
+### **10.4 Revision alert for original author's wording**
+
+The co-authoring function in a hybrid work environment is required to send an alert to the original author when another user modifies their text. The final document is required to be revised only upon the original author's acceptance of the modifications.
+
+### **10.5 Reflection of personal status**
+
+Co-authoring documents in a hybrid work environment is required to store each user's personal status during initial sentence creation, correction, and deletion, along with the text, as metadata containing semantic information. This allows contextual information to be retained, even if a third party views the document. It is particularly useful for understanding personal status in documents such as movie or drama scenarios or scripts.
+
+### **10.6 Definition of personal status**
+
+A data type representing the ensemble of information internal to a person expressed by 3 factors (cognitive state, emotion, social attitude) conveyed by one or more modalities (speech, face, and gesture).
+
+#### **10.6.1 Limit of personal status**
+
+Personal status is a subjective and complex phenomenon that is challenging to define and standardize universally, given variations among individuals and cultures. In the context of document co-authoring, the emotions referred to herein pertain to the fundamental emotions to be employed. However, it is required to be noted that the definition of personal status can optionally undergo partial modifications influenced by psychology and other factors.
+
+#### **10.6.2 Personal status items for real-time document co-authoring**
+
+Table 1 categorizes personal status as defined in [IEEE P3300], specifically reclassified for use during collaborative document co-authoring.
+
+**Table 1 – Personal status items for document co-authoring**
+
+| Category   | Description                                                                                                                       |
+|------------|-----------------------------------------------------------------------------------------------------------------------------------|
+| Positive   | This status is used when feedback or suggestions are based on positive emotions, including satisfaction, happiness, or gratitude. |
+| Negative   | Indicates feedback expressing dissatisfaction, disappointment, or concern, signalling a need for improvement.                     |
+| Neutral    | Represents factual or objective feedback without an emotional tendency, useful for focusing on the essence of the issue.          |
+| Curious    | Used to express curiosity or interest in new ideas or proposals, and may involve questions or requests for further explanation.   |
+| Interested | Indicates interest or enthusiasm for a particular idea or proposal, showing a willingness to actively participate.                |
+
+#### 10.6.3 Definition of factors for personal status
+
+The personal status is recommended to be identified through the analysis of the user's facial expressions, gestures and voice (see Table 2).
+
+**Table 2 – Determining factor item of personal status**
+
+| Data Type          | Description                                                                                    |
+|--------------------|------------------------------------------------------------------------------------------------|
+| Facial expressions | Analysis of facial muscle movements and expressions to interpret emotions.                     |
+| Gestures           | Examination of body movements, hand gestures, and postures to understand emotional cues.       |
+| Voice data         | Evaluation of vocal tone, pitch, volume, and speech patterns to extract emotional information. |
+
+## 11 Hybrid work environment workflow
+
+### 11.1 Real-time document co-authoring
+
+In this workflow (see Figure 4), three users collaboratively edit content in the output document. Each user's emotional state is recorded during creation, editing or deletion of text. The system outputs the final text, emotional context for each revision and a semantic history log capturing both author and editor emotions.
+
+![Diagram of the real-time document co-authoring workflow. On the left, under 'Input', are three users: User 1, User 2, and User 3. User 1 sends 'Create (Text, emotion)' to a central 'Document' box. User 2 sends 'Edit (Text, emotion)' to the 'Document' box. User 3 sends 'Delete (Text, emotion)' to the 'Document' box. On the right, under 'Output', the 'Document' box points to three results: 'Final text', 'Emotion at each text', and 'History tracking information with semantic status'.](c036e2540a94b31357ceb0002f0cacab_img.jpg)
+
+```
+
+graph LR
+    subgraph Input
+        U1((User 1)) -- "Create (Text, emotion)" --> D[Document]
+        U2((User 2)) -- "Edit (Text, emotion)" --> D
+        U3((User 3)) -- "Delete (Text, emotion)" --> D
+    end
+    subgraph Output
+        D --> F[Final text]
+        D --> E[Emotion at each text]
+        D --> H[History tracking information with semantic status]
+    end
+  
+```
+
+Diagram of the real-time document co-authoring workflow. On the left, under 'Input', are three users: User 1, User 2, and User 3. User 1 sends 'Create (Text, emotion)' to a central 'Document' box. User 2 sends 'Edit (Text, emotion)' to the 'Document' box. User 3 sends 'Delete (Text, emotion)' to the 'Document' box. On the right, under 'Output', the 'Document' box points to three results: 'Final text', 'Emotion at each text', and 'History tracking information with semantic status'.
+
+F.746.19(25)
+
+**Figure 4 – Real-time document co-authoring workflow**
+
+### 11.2 Hybrid meeting environment
+
+The structure illustrated in Figure 5 provides an extended representation of the basic meeting components described in clause 7, namely agenda, discussion, meeting minutes and minutes sharing.
+
+![Figure 5 – Hybrid meeting environment workflow diagram](724c7777b608e53be38b12b6fb3c43bc_img.jpg)
+
+The diagram illustrates the hybrid meeting environment workflow. It starts with three input sources: Speech, Face, and Text (Material). Speech is processed by a Speech recognition block to produce Text. Face is processed by a Face recognition block to produce an Image. Both Text and Image are inputs to a Speaker identification block. The Speaker identification block outputs Text to four parallel processing blocks: Question and dialogue processing, Emotion analysis, Statistical analysis, and Authentication. Question and dialogue processing outputs Text (Fact) and Text (Speech) to a Domain knowledge-based block. Emotion analysis outputs Text (Emotion). Statistical analysis outputs Text (Statistical Info.). Authentication outputs an Authentication ID to a Guest book block, which then outputs Text (Participants). All five outputs (Text (Fact), Text (Speech), Text (Emotion), Text (Statistical Info.), and Text (Participants)) are inputs to a Meeting minutes and sharing block. This block outputs Text (Personal), Text (Deadline), and Text (Work items) to a Notification block. The diagram is labeled F.746.19(25).
+
+Figure 5 – Hybrid meeting environment workflow diagram
+
+**Figure 5 – Hybrid meeting environment workflow**
+
+While Figure 2 presents the conceptual framework of a typical meeting process, Figure 5 depicts its technical realization within a hybrid work environment.
+
+### 11.3 Speech recognition
+
+The speech recognition model, as defined in this Recommendation, performs voice signal processing and speaker speech-to-text conversion of meeting participants. It extracts acoustic and linguistic features from captured audio streams and transcribes spoken content into text to support speaker identification, real-time captioning, and meeting minutes generation within a hybrid meeting environment.
+
+### 11.4 Face recognition
+
+The face recognition model, as defined in this Recommendation, performs facial feature detection and identity verification of meeting participants. It extracts facial biometric data from captured images or video frames and matches them against pre-registered profiles to support speaker recognition, authentication, and attendance tracking within a hybrid meeting environment.
+
+### 11.5 Speaker identification
+
+The speaker recognition model, as defined in this Recommendation, identifies and distinguishes speakers from audio input in a hybrid meeting environment. It performs speaker segmentation, emotion recognition, and statistical extraction, producing outputs such as speaker-specific utterance data, emotional states, and quantitative participation metrics. The model supports accurate attribution of dialogue and enhances meeting analytics by combining biometric voice recognition and affective computing techniques. It extracts speech content, emotion recognition, and statistical information for each speaker.
+
+### 11.6 Question and dialogue processing
+
+The question and dialogue processing model, as defined in this Recommendation, performs semantic extraction and dialogue management functions based on [ITU-T F.746.3]. It analyses speech or textual inputs to derive meaning, intent, and context, enabling interactive communication and knowledge retrieval within a hybrid work environment. The model also supports adaptive dialogue flow by maintaining contextual consistency across multiple speakers and sessions.
+
+### 11.7 Emotion analysis
+
+Emotion analysis model, as defined in this Recommendation, analyses speech, text, and non-verbal cues to estimate the emotional state of the speaker at the time of presentation. The model employs acoustic and linguistic features such as pitch, tone, lexical sentiment, and prosody to determine emotional polarity and intensity. This information can be utilized to assess communication dynamics, contextual relevance, and overall engagement within hybrid meetings.
+
+### 11.8 Statistical analysis
+
+The statistical analysis model, as defined in this Recommendation, analyses quantitative indicators derived from speech and visual data to determine the level of participation and concentration of both speakers and listeners. The model applies time-based analysis of speech segments and non-verbal cues such as gaze and facial orientation to derive engagement metrics. It extracts the speaker's speech time and the degree of participation and concentration of the speaker and listener.
+
+### 11.9 Authentication
+
+Authentication model, as defined in this Recommendation, verifies the identity of participants through multimodal data and credential-based validation. Upon successful authentication, a unique identification code is generated and transmitted to the guest book for recording attendance information. This process ensures secure and traceable participation management in hybrid meetings. It extracts the participant's information that can be entered in the guestbook through the issuance of individual identifiers (IDs).
+
+### 11.10 Domain knowledge-based
+
+Domain knowledge-based model, as defined in this Recommendation, verifies the consistency and factual accuracy of meeting contents against a predefined domain knowledge base. The model performs semantic validation to determine whether the ongoing discussion corresponds to the meeting agenda and whether the statements made by speakers are supported by verifiable facts. It applies natural language understanding and entity-matching techniques within the knowledge base to maintain contextual coherence. It verifies whether the current meeting content is suitable for the domain and whether the speaker's content is based on facts.
+
+### 11.11 Guest book
+
+The guest book model, as defined in this Recommendation, manages the authenticated information of meeting participants. It receives identity data from the authentication model and maintains a structured participant record for attendance and access control purposes. The model transfers verified participant information to the *meeting minutes* component to support secure information delivery and role-based authorization. It extracts and delivers participant information to the meeting minutes through participant authentication.
+
+
+
+# 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.746.6-201712-I_PDF-E/raw.md b/marked/F/T-REC-F.746.6-201712-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..f82f56c3b35230de79810018517c57581c04c2ea
--- /dev/null
+++ b/marked/F/T-REC-F.746.6-201712-I_PDF-E/raw.md
@@ -0,0 +1,455 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.746.6**
+
+(12/2017)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Multimedia services
+
+---
+
+**Requirements for a name resolution service in  
+information-centric networks**
+
+Recommendation ITU-T F.746.6
+
+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 "ITU" in a larger, bold font above it.
+
+ITU logo
+
+International  
+Telecommunication  
+Union
+
+# ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+## **TELEGRAPH SERVICE**
+
+|                                                                 |             |
+|-----------------------------------------------------------------|-------------|
+| Operating methods for the international public telegram service | F.1–F.19    |
+| The gentex network                                              | F.20–F.29   |
+| Message switching                                               | F.30–F.39   |
+| The international telemessage service                           | F.40–F.58   |
+| The international telex service                                 | F.59–F.89   |
+| Statistics and publications on international telegraph services | F.90–F.99   |
+| Scheduled and leased communication services                     | F.100–F.104 |
+| Phototelegraph service                                          | F.105–F.109 |
+
+## **MOBILE SERVICE**
+
+|                                                        |             |
+|--------------------------------------------------------|-------------|
+| Mobile services and multdestination satellite services | F.110–F.159 |
+|--------------------------------------------------------|-------------|
+
+## **TELEMATIC SERVICES**
+
+|                                           |             |
+|-------------------------------------------|-------------|
+| Public facsimile service                  | F.160–F.199 |
+| Teletex service                           | F.200–F.299 |
+| Videotex service                          | F.300–F.349 |
+| General provisions for telematic services | F.350–F.399 |
+
+## **MESSAGE HANDLING SERVICES**
+
+|  |             |
+|--|-------------|
+|  | F.400–F.499 |
+|--|-------------|
+
+## **DIRECTORY SERVICES**
+
+|  |             |
+|--|-------------|
+|  | F.500–F.549 |
+|--|-------------|
+
+## **DOCUMENT COMMUNICATION**
+
+|                                      |             |
+|--------------------------------------|-------------|
+| Document communication               | F.550–F.579 |
+| Programming communication interfaces | F.580–F.599 |
+
+## **DATA TRANSMISSION SERVICES**
+
+|  |             |
+|--|-------------|
+|  | F.600–F.699 |
+|--|-------------|
+
+## **MULTIMEDIA SERVICES**
+
+|  |                    |
+|--|--------------------|
+|  | <b>F.700–F.799</b> |
+|--|--------------------|
+
+## **ISDN SERVICES**
+
+|  |             |
+|--|-------------|
+|  | F.800–F.849 |
+|--|-------------|
+
+## **UNIVERSAL PERSONAL TELECOMMUNICATION**
+
+|  |             |
+|--|-------------|
+|  | F.850–F.899 |
+|--|-------------|
+
+## **ACCESSIBILITY AND HUMAN FACTORS**
+
+|  |             |
+|--|-------------|
+|  | F.900–F.999 |
+|--|-------------|
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.746.6
+
+# Requirements for a name resolution service in information-centric networks
+
+## Summary
+
+Recommendation ITU-T F.746.6 describes the requirements for a flexible name resolution service in information-centric networks (ICN). It also describes the functional modules, i.e., name resolution service access control module, namespace management module, interoperation module and resolution engine module, of name resolution service in ICN. The name resolution service can support name resolution for any particular ICN instance independently. It also can facilitate interoperation between ICN instances with their own namespaces.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.746.6  | 2017-12-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/13428">11.1002/1000/13428</a> |
+
+## Keywords
+
+Information-centric networks, name resolution.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                                                      | 2    |
+| 6 Motivation.....                                                                                        | 2    |
+| 7 Functional modules of name resolution service in ICN .....                                             | 3    |
+| 7.1 Name resolution service access control module.....                                                   | 3    |
+| 7.2 Namespace management module .....                                                                    | 3    |
+| 7.3 Interoperation module .....                                                                          | 4    |
+| 7.4 Resolution engine module .....                                                                       | 4    |
+| 8 Requirements for name resolution service in ICN .....                                                  | 4    |
+| 8.1 General requirements.....                                                                            | 4    |
+| 8.2 Requirements for NRS access control module .....                                                     | 4    |
+| 8.3 Requirements for namespace management module .....                                                   | 4    |
+| 8.4 Requirements for interoperation module.....                                                          | 4    |
+| 8.5 Requirements for resolution engine module.....                                                       | 5    |
+| 9 Security consideration .....                                                                           | 5    |
+| Annex A – Scenarios for name resolution services in ICN .....                                            | 6    |
+| A.1 Scenario of providing name resolution service for two ICN instances<br>independently .....           | 6    |
+| A.2 Scenario of providing name resolution service for interoperation between<br>two ICN instances.....   | 6    |
+| Appendix I – Survey of name resolution schemes used in Internet and information-centric<br>networks..... | 8    |
+| Bibliography.....                                                                                        | 9    |
+
+
+
+# Recommendation ITU-T F.746.6
+
+## Requirements for a name resolution service in information-centric networks
+
+## 1 Scope
+
+This Recommendation describes the requirements for a flexible name resolution service for information-centric networks (ICN). It defines the key functional modules for name resolution service in ICN. This Recommendation covers the following:
+
+- capabilities of name resolution service in ICN;
+- requirements for name resolution service in ICN;
+- scenarios of name resolution service for ICN instances.
+
+## 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 networks*.
+
+[ITU-T Y.3033] Recommendation ITU-T Y.3033 (2014), *Framework of data aware networking for future networks*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following term defined elsewhere:
+
+**3.1.1 future network (FN)** [b-ITU-T Y.3001]: A network able to provide services, capabilities, and facilities difficult to provide using existing network technologies. A future network is either:
+
+- a) A new component network or an enhanced version of an existing one, or
+- b) A heterogeneous collection of new component networks or of new and existing component networks that is operated as a single network.
+
+NOTE 1 – The plural form "Future Networks" (FNs) is used to show that there may be more than one network that fits the definition of a future network.
+
+NOTE 2 – A network of type b may also include networks of type a.
+
+NOTE 3 – The label assigned to the final federation may, or may not, include the word "future", depending on its nature relative to any preceding network and similarities thereto.
+
+NOTE 4 – The word "difficult" does not preclude some current technologies from being used in future networks.
+
+NOTE 5 – In the context of this Recommendation, the word "new" applied to a component network means that the component network is able to provide services, capabilities, and facilities that are difficult or impossible to provide using existing network technologies.
+
+### 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 name resolution:** The process by which, given an initial name and an initial naming context, an association between a name and the entity designated by the initial name can be found (adapted from [b-ITU-T X.902]).
+
+NOTE – The name resolution process does not necessarily provide sufficient information to interact with the designated entity.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                |
+|------|--------------------------------|
+| DNS  | Domain Name System             |
+| GNRS | Global Name Resolution Service |
+| GUID | Globally Unique Identifier     |
+| ICN  | Information-Centric Networks   |
+| NAT  | Network Address Translation    |
+| NDN  | Named Data Networking          |
+| NRS  | Name Resolution Service        |
+
+## 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.
+- 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 Motivation
+
+Information-centric networks (ICN) is a promising technology for future Internet design with which a user can directly obtain a content object by its name (or identification) without specifying the location of the content object. In recent years, various ICN solutions have been proposed with their own namespaces such as named data networking (NDN) [b-Jacobson], MobilityFirst [b-Seskar] and publish subscribe Internet technology (PURSUIT) [b-Fotiou].
+
+To identify different objects from their associated names, a name resolution service is needed. Different name resolution schemes are adopted for different ICN solutions, such as the rendezvous system in PURSUIT [b-Fotiou] and global name resolution service (GNRS) system in MobilityFirst [b-Seskar]. Various name resolution schemes differ from each other from the perspectives of resolution policies and management mechanisms. The comparison of resolution policies and management mechanisms among various existing name resolution schemes in the current Internet and ICN are shown in Table I.1 (see Appendix I).
+
+As described in [ITU-T F.746.4], each solution has its own pros and cons and is best suited to some particular application requirements. Different ICN service providers may deploy their own ICN instances with their own namespaces on top of the same physical network.
+
+To support the coexistence of various ICN instances on the same physical network, and to enable the potential interoperation among different ICN instances that employ different namespaces, a flexible name resolution service for information-centric networks is needed. This name resolution service provides dynamic resolution that allows the administrator of ICN instances to flexibly specify namespaces with their private naming schemes and resolution policies. Furthermore, this name resolution service is required to support any particular ICN instance independently, which means that internal-mapping relationships between multiple namespaces of the same ICN instance are maintained independently. It is also recommended that this name resolution service facilitate interoperation between different ICN instances with their own namespaces, which means the cross-mapping relationships between the multiple namespaces belonging to different ICN instances will be maintained.
+
+## 7 Functional modules of name resolution service in ICN
+
+As shown in Figure 7-1, the name resolution service in ICN includes four functional modules: name resolution service (NRS) access control module, namespace management module, resolution engine module and interoperation module. This clause addresses the capabilities of these functional modules.
+
+![Diagram of functional modules of name resolution service in ICN](7a0db9703b68b3d06cdaeefc084c0006_img.jpg)
+
+The diagram illustrates the functional modules of the name resolution service in ICN. At the top, a box labeled 'Administrators of ICN instances' is connected to a central dashed box. Inside this dashed box, labeled 'Functional modules of name resolution service' on the right, are four modules: 'NRS access control module' at the top, 'Namespace management module' and 'Interoperation module' in the middle, and 'Resolution engine module' at the bottom. The 'NRS access control module' is connected to both the 'Administrators of ICN instances' and the 'Resolution engine module'. The 'Namespace management module' and 'Interoperation module' are connected to each other and to the 'Resolution engine module'. At the bottom, a box labeled 'Users of name resolution service' is connected to the 'Resolution engine module'. The diagram is labeled F.746.6(17)\_F7-1.
+
+Diagram of functional modules of name resolution service in ICN
+
+Figure 7-1 – Functional modules of name resolution service
+
+### 7.1 Name resolution service access control module
+
+The NRS access control module offers the capabilities of authentication and authorization. As there are multiple ICN instances coexisting in the same physical network, to safeguard the sensitive namespace information of each ICN instance, the administrators of the ICN instances must be authenticated and authorized to explore the capabilities provided by the namespace management module and interoperation module.
+
+### 7.2 Namespace management module
+
+The namespace management module is responsible for enabling the administrators of ICN instances flexibly to manage their own namespaces and specify their resolution policies. With this module, an administrator of the ICN instance can define namespaces with a particular naming scheme and indicate the scope of the namespace based on their design principles. The administrator can also create and update the names and the internal-mapping relationships between multiple namespaces of the same ICN instance.
+
+### **7.3 Interoperation module**
+
+An object has different names in different ICN instances. The interoperation module maintains the cross-mapping relationships between the multiple namespaces belonging to different ICN instances. The administrator of the ICN instance can indicate objects to which access by other ICN instance(s) is allowed. The interoperation modules of different ICN instances exchange with each other the names of the objects that can be accessed by other ICN instance(s).
+
+### **7.4 Resolution engine module**
+
+The resolution engine module uses the information and policies maintained in the namespace management module and interoperation module to accomplish the name resolution. When it receives the name resolution requests from NRS users, it queries the internal-mapping relationships provided by namespace management module and cross-mapping relationships provided by interoperation module in turn.
+
+## **8 Requirements for name resolution service in ICN**
+
+This clause addresses the requirements for name resolution service in ICN.
+
+### **8.1 General requirements**
+
+GEN-01: The name resolution service is required to support the name resolution for any particular ICN instance independently.
+
+GEN-02: The name resolution service is required to enable dynamic resolution such that the administrators of ICN instances can flexibly define their own namespace and resolution policies.
+
+GEN-03: The name resolution service is recommended to support interoperation between ICN instances.
+
+### **8.2 Requirements for NRS access control module**
+
+NA-01: The NRS access control module is required to authenticate the validity of the administrators of ICN instances that try to access and update the namespaces maintained by namespace management module.
+
+NA-02: The NRS access control module is required to authorize the administrators of ICN instances to explore the capabilities provided by the namespace management module and interoperation module.
+
+### **8.3 Requirements for namespace management module**
+
+NM-01: The namespace management module is required to enable the administrators of ICN instances to flexibly define their own namespaces with particular naming schemes and indicate the scope of the namespaces based on their design principles.
+
+NM-02: The namespace management module is required to allow the administrators of ICN instances to define their own resolution policies, such as where and how to conduct resolution, the used synchronization cycle, and the adopted algorithms.
+
+NM-03: The namespace management module is required to allow the administrator of an ICN instance to create and update the names and the internal-mapping relationships between multiple namespaces of the same ICN instance.
+
+### **8.4 Requirements for interoperation module**
+
+NI-01: The interoperation modules of ICN instances are recommended to exchange the names of the objects which are allowed to be accessed by other ICN instance(s).
+
+NI-02: The interoperation module is recommended to register the cross-mapping relationships between the multiple namespaces belonging to different ICN instances.
+
+NI-03: The interoperation module is recommended to unregister the cross-mapping relationships between the multiple namespaces belonging to different ICN instances.
+
+NI-04: The interoperation module is recommended to modify cross-mapping relationships between the multiple namespaces belonging to different ICN instances.
+
+### **8.5 Requirements for resolution engine module**
+
+NR-01: The resolution engine module is required to perform the name resolution using the information and policies maintained in the namespace management module and interoperation module.
+
+## **9 Security consideration**
+
+This Recommendation has similar security considerations to those pertinent to data aware networking and aligns with the security requirements specified in [ITU-T Y.3033].
+
+## Annex A
+
+## Scenarios for name resolution services in ICN
+
+(This annex forms an integral part of this Recommendation.)
+
+In ICN, data is requested and located by its name. To deliver the content by name, various name resolution schemes are employed by different ICN solutions. For example, PURSUIT employs a rendezvous system to mapping a content name, i.e., rendezvous identifier and service identifier, to a forwarding identifier. Each solution has its own pros and cons and is best suited to some particular application requirements. Different ICN service providers may deploy their own ICN instances with their own namespaces on top of the same physical network. A flexible name resolution service is needed to support ICN instance deployment. Two scenarios of name resolution service for ICN instances are illustrated, i.e., scenario of providing name resolution service for two ICN instances independently, and scenario of providing name resolution service for interoperation between two ICN instances.
+
+### A.1 Scenario of providing name resolution service for two ICN instances independently
+
+In this scenario, different ICN instances are deployed independently. As shown in Figure A.1, two different ICN instances are supported. There is no interoperation between them and the name resolution services for them are also independent. The interoperation modules are not used.
+
+![Diagram illustrating the scenario of supporting the name resolution for two ICN instances independently. The diagram shows two separate ICN instances, ICN instance 1 and ICN instance 2, each with its own administrators and a set of modules for name resolution. The modules include NRS access control, Namespace management, Interoperation (disabled), and Resolution engine. Each instance is connected to a cloud representing the network, which contains three nodes (routers) marked with a red 'X'.](08441fa90c5fd11994626f662ac13f19_img.jpg)
+
+The diagram illustrates two independent ICN instances. At the top, two boxes represent the 'Administrators of ICN instance 1' and 'Administrators of ICN instance 2'. Below each administrator box is a dashed rectangle containing four modules: 'NRS access control module', 'Namespace management module', 'Interoperation module' (indicated by a dashed border), and 'Resolution engine module'. Below each dashed rectangle is a cloud representing a network, containing three nodes (routers) marked with a red 'X'. Dashed lines connect the 'Resolution engine module' to each of the three nodes in its respective cloud. The clouds are labeled 'ICN instance 1' and 'ICN instance 2'. A small label 'F.746.6(17)\_FA.1' is located at the bottom right of the diagram.
+
+Diagram illustrating the scenario of supporting the name resolution for two ICN instances independently. The diagram shows two separate ICN instances, ICN instance 1 and ICN instance 2, each with its own administrators and a set of modules for name resolution. The modules include NRS access control, Namespace management, Interoperation (disabled), and Resolution engine. Each instance is connected to a cloud representing the network, which contains three nodes (routers) marked with a red 'X'.
+
+Figure A.1 – Scenario of supporting the name resolution for two ICN instances independently
+
+### A.2 Scenario of providing name resolution service for interoperation between two ICN instances
+
+As shown in Figure A.2, the administrators of these two ICN instances specify a set of objects that can be accessed from the other ICN instance. These cross-mapping relationships are maintained in the interoperation modules.
+
+![Diagram illustrating the scenario of interoperation between two ICN instances. Each instance has an administrator, an NRS access control module, a namespace management module, an interoperation module, and a resolution engine module. These modules are connected to a network of switches (represented by circles with red Xs) within the instance. The two instances are connected via a dashed line between their interoperation modules. The diagram is labeled F.746.6(17)_FA.2.](af7916c89a458fdab6c3f443217388ae_img.jpg)
+
+The diagram shows two ICN instances, ICN instance 1 and ICN instance 2, connected via a dashed line between their interoperation modules. Each instance is managed by 'Administrators of ICN instance 1' or 'Administrators of ICN instance 2'. Below the administrators, each instance contains a set of modules: an 'NRS access control module', a 'Namespace management module', an 'Interoperation module', and a 'Resolution engine module'. These modules are connected to a network of switches (represented by circles with red Xs) within the instance. The interoperation module in each instance is connected to the resolution engine module and the namespace management module. The two interoperation modules are connected to each other via a dashed line. The switches in each instance are connected to the resolution engine module and the interoperation module. The diagram is labeled F.746.6(17)\_FA.2.
+
+Diagram illustrating the scenario of interoperation between two ICN instances. Each instance has an administrator, an NRS access control module, a namespace management module, an interoperation module, and a resolution engine module. These modules are connected to a network of switches (represented by circles with red Xs) within the instance. The two instances are connected via a dashed line between their interoperation modules. The diagram is labeled F.746.6(17)\_FA.2.
+
+**Figure A.2 – Scenario of interoperation between two ICN instances**
+
+When a host in ICN instance 1 wants to access an object in ICN instance 2, the resolution engine module finds the resolution results in the interoperation module and returns it to the requesting host. To support the interoperation between two ICN instances, the border switch needs to execute some procedures, e.g., packet translation and protocol adaption, as described in [ITU-T F.746.4]. In order to protect the border switch and guarantee that the message is not tampered with, the device that is responsible for name resolution chooses a trusted border switch. The resolution engine of the device generates a cipher text based on the name of the source host, the name of the destination host, and the identifier of the selected device (the selected border switch). The resolution engine module sends the cipher text to the source host. The source host then uses the cipher text to encapsulate the packets. The selected switch checks the validity of the packets from the source according to the information of the source host. The identifier of the selected switch and cipher text are then used to generate the verification information that is also included in the header of the packets before they are forwarded to the destination host. The cipher text and verification information will be used by the destination host to verify the received packets.
+
+## Appendix I
+
+### Survey of name resolution schemes used in Internet and information-centric networks
+
+(This appendix does not form an integral part of this Recommendation.)
+
+In the current Internet and ICN, various name resolution solutions are proposed. Each name resolution solution employs its own resolution policies and management methods as shown in Table I.1. A name resolution policy specifies how the names are resolved, including the type of resolution (e.g., one-way resolution, or two-way resolution) and the mapping relationship (e.g., one-to-one mapping or one-to-many mapping). The management mechanism is related to where the resolution procedures are performed (e.g., at individual routers or at dedicated servers), and how those nodes performing resolution are organized (e.g., in a distributed way, in a centralized way, or in a hierarchical way). These name resolution solutions employ their own resolution policies, which are static and lacks of flexibility to quickly provision efficient services.
+
+**Table I.1 – Existing name resolution solutions**
+
+| Project                                                     | Namespace                                                                     | Resolution policy                                         | Resolution management                                                                         |
+|-------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------------------------------------------------|-----------------------------------------------------------------------------------------------|
+| Domain name system (DNS) [b-RFC 2136]                       | Domain name (global) → IP Address (global)                                    | One-way resolution<br>One-to-many mapping                 | Dedicated DNS server<br>Hierarchically organized                                              |
+| Network address translation (NAT) [b-RFC 2766]              | Private IP address + Port number ↔ Global IP address + Port number            | Bi-directional resolution<br>One-to-one mapping           | At a gateway                                                                                  |
+| MobilityFirst (Destination Resolution) [b-Seskar]           | (Globally unique identifier)<br>GUID → NA                                     | One-way resolution                                        | At distributed servers.<br>Dynamic updating and late binding.                                 |
+| Named data networking (NDN) [b-Jacobson]                    | Content name (global) → Interface identifier (local);                         | One-way resolution<br>One-to-many mapping                 | At individual router.<br>Pending Interest Table.<br>Distributed: Forwarding information base. |
+| eXpressive Internet architecture (XIA) (Routing) [b-Naylor] | XIA Identifier (global) → Interface identifier (local)                        | One-way resolution                                        | At router.                                                                                    |
+| PURSUIT (Content routing) [b-Fotiou]                        | Rendezvous identifier + Service identifier → Forwarding identifier (Regional) | One-way resolution<br>One-to-many mapping<br>Bloom filter | Dedicated server (Topology management)<br>Hierarchically organized                            |
+
+## Bibliography
+
+- [b-ITU-T X.902] Recommendation ITU-T X.902 (2009), *Information technology – Open Distributed Processing – Reference model: Foundations*.
+- [ITU-T Y.3001] Recommendation ITU-T Y.3001 (2011), *Future networks: Objectives and design goals*.
+- [b-RFC 2136] IETF RFC 2136 (1997), *Dynamic updates in the domain name system (DNS UPDATE)*.
+- [b-RFC 2766] IETF RFC 2766 (2000), *Network address translation-protocol translation (NAT-PT)*.
+- [b-Fotiou] N. Fotiou, D. Trossen, and G.C. Polyzos, *Illustrating a publish-subscribe internet architecture*, Telecommunication Systems, vol. 51, no. 4, pp. 233-245, 2012.
+- [b-Jacobson] V. Jacobson, D.K. Smetters, J.D. Thornton, M.F. Plass, N.H. Briggs, and R.L. Braynard, *Networking named content*, in Proc. of the 5th ACM CoNEXT, New York, USA, 2009, pp. 1-12.
+- [b-Naylor] Naylor D, Mukerjee M.K., Agyapong P, *et al.*, *XIA: architecting a more trustworthy and evolvable internet*, ACM SIGCOMM Computer Communication Review, 2014, 44(3): 50-57.
+- [b-Seskar] I.Seskar, K. Nagaraja, S. Nelson, and D. Raychaudhuri, *Mobility First future internet architecture project*, in Proc. of the 7th ACM AINTEC. New York, USA: ACM, 2011, pp. 1-3.
+
+
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.747.10-202201-I_PDF-E/raw.md b/marked/F/T-REC-F.747.10-202201-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..23b542f329aab949de93eb7fd4f96d63b18184af
--- /dev/null
+++ b/marked/F/T-REC-F.747.10-202201-I_PDF-E/raw.md
@@ -0,0 +1,414 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.747.10**
+
+(01/2022)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Multimedia services
+
+---
+
+**Requirements of distributed ledger systems  
+for secure human factor services**
+
+Recommendation ITU-T F.747.10
+
+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 F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |             |
+|-----------------------------------------------------------------|-------------|
+| <b>TELEGRAPH SERVICE</b>                                        |             |
+| Operating methods for the international public telegram service | F.1–F.19    |
+| The gentex network                                              | F.20–F.29   |
+| Message switching                                               | F.30–F.39   |
+| The international telemessage service                           | F.40–F.58   |
+| The international telex service                                 | F.59–F.89   |
+| Statistics and publications on international telegraph services | F.90–F.99   |
+| Scheduled and leased communication services                     | F.100–F.104 |
+| Phototelegraph service                                          | F.105–F.109 |
+| <b>MOBILE SERVICE</b>                                           |             |
+| Mobile services and multdestination satellite services          | F.110–F.159 |
+| <b>TELEMATIC SERVICES</b>                                       |             |
+| Public facsimile service                                        | F.160–F.199 |
+| Teletex service                                                 | F.200–F.299 |
+| Videotex service                                                | F.300–F.349 |
+| General provisions for telematic services                       | F.350–F.399 |
+| <b>MESSAGE HANDLING SERVICES</b>                                | F.400–F.499 |
+| <b>DIRECTORY SERVICES</b>                                       | F.500–F.549 |
+| <b>DOCUMENT COMMUNICATION</b>                                   |             |
+| Document communication                                          | F.550–F.579 |
+| Programming communication interfaces                            | F.580–F.599 |
+| <b>DATA TRANSMISSION SERVICES</b>                               | F.600–F.699 |
+| <b>MULTIMEDIA SERVICES</b>                                      | F.700–F.799 |
+| <b>ISDN SERVICES</b>                                            | F.800–F.849 |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | F.850–F.899 |
+| <b>ACCESSIBILITY AND HUMAN FACTORS</b>                          | F.900–F.999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.747.10
+
+# Requirements of distributed ledger systems for secure human factor services
+
+## Summary
+
+Recommendation ITU-T F.747.10 provides general requirements and functional capabilities for distributed ledger systems (DLS) for secure human factor services.
+
+This Recommendation describes the requirements for the secure human factor distributed ledger service model, which can solve conflicting goals of privacy protection and big personal human factor data utilization. This Recommendation also includes the functional capabilities for human factor distributed ledger shared nodes to perform machine learning without decryption on encrypted human factor data. However, the computational burden of machine learning for encrypted data may be excessive. To solve this problem, this human factor distributed ledger service model provides procedures for allowing the use of two or more encryption key pairs and notifying the key type. In addition, this Recommendation involves the integrity maintaining requirements for secure human factor services to maintain a safe distributed ledger and, checked from the beginning, to distribute personal human factor information. Therefore, the application of distributed ledger system in the distribution of personal secure human factor information can ensure transparent tracking from the distribution process to the final use path.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.747.10 | 2022-01-17 | 16          | <a href="http://handle.itu.int/11.1002/1000/14644">11.1002/1000/14644</a> |
+
+## Keywords
+
+Distributed ledger service model, privacy protection expansion, secure human factor, transparency tracking.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                                               | 2    |
+| 5 Conventions .....                                                                                              | 2    |
+| 6 Background.....                                                                                                | 3    |
+| 7 General requirements for distributed ledger systems of secure human factor services                            | 3    |
+| 7.1 Functional requirements for public distributed ledger shared nodes.....                                      | 4    |
+| 7.2 Authentication requirements for new participating node .....                                                 | 4    |
+| 7.3 Security requirements for distributed ledger system .....                                                    | 5    |
+| 7.4 Integrity maintaining requirements for a distributed ledger system.....                                      | 5    |
+| 8 Functional capabilities for distributed ledger systems of secure human factor services .....                   | 6    |
+| 8.1 Distributed ledger structure in distribution of personal human factor information .....                      | 6    |
+| 8.2 Two functions in distributed ledger structure in the distribution of personal human factor information ..... | 6    |
+| 8.3 Distributed ledger system maintenance methodologies .....                                                    | 7    |
+| Annex A – Application to secure human factor distributed ledger service model .....                              | 9    |
+| Bibliography.....                                                                                                | 10   |
+
+
+
+# Recommendation ITU-T F.747.10
+
+## Requirements of distributed ledger systems for secure human factor services
+
+# 1 Scope
+
+This Recommendation describes requirements for distributed ledger systems (DLS) for secure human factor services, covering:
+
+- Background;
+- General requirements for DLS for secure human factor services;
+- Functional capabilities for DLS for secure human factor 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 block** [b-ISO 22739]: Structured data comprising block data and a block header.
+- 3.1.2 consensus** [b-ISO 22739]: Agreement among DLT nodes that 1) a transaction is validated and 2) that the distributed ledger contains a consistent set and ordering of validated transactions.
+- 3.1.3 digital signature** [b-ISO 22739]: Data which, when appended to a digital object, enable the user of the digital object to authenticate its origin and integrity.
+- 3.1.4 distributed ledger** [b-ISO 22739]: Ledger that is shared across a set of DLT nodes and synchronized between the DLT nodes using a consensus mechanism.
+- 3.1.5 distributed ledger technology** [b-ISO 22739]: Technology that enables the operation and use of distributed ledgers.
+- 3.1.6 fork** [b-ITU-T TS FG DLT D1.1]: Creation of two or more different versions of a distributed ledger.
+- 3.1.7 hash value** [b-ISO 22739]: String of bits which is the output of a cryptographic hash function.
+- 3.1.8 health** [b-WHO]: A state of physical, mental and social well-being in which disease and infirmity are absent.
+- 3.1.9 ledger** [b-ISO 22739]: Information store that keeps records of transactions that are intended to be final, definitive and immutable.
+- 3.1.10 Merkle tree** [b-NIST]: A data structure where the data is hashed and combined until there is a singular root hash that represents the entire data structure.
+
+- 3.1.11 mining** [b-ITU-T F.751.0]: A reward-seeking activity in some consensus mechanisms.
+- 3.1.12 node** [b-ISO 22739]: Elementary component from which a data structure is built.
+- 3.1.13 public distributed ledger system** [b-ITU-T F.751.0]: DLT system which is accessible to the public for use.
+- 3.1.14 transaction** [b-ISO 22739]: Smallest unit of a work process, which is one or more sequences of actions required to produce an outcome that complies with governing rules.
+
+## **3.2 Terms defined in this Recommendation**
+
+This Recommendation defines the following terms:
+
+- 3.2.1 block depth**: The level of a block appended to the distributed ledger system chain from its the initial block.
+- 3.2.2 electronic human factor records**: The systematized collection of person and population electronically stored human factor information in a digital format.
+- 3.2.3 human factor**: Principles to the design of optimal life-style conditions with regard to human well-being, safety and health, including the development of existing technologies and the acquisition of new ones.
+- NOTE – Adapted from [b-ISO 6385] and [b-Wickens].
+- 3.2.4 personal human factor information**: The information collected by directly measuring the human body and its environments and which is transmitted to personal human factor devices or other devices through a communication network to be used for electronic human factor records.
+- 3.2.5 personal human factor device**: A type of device that measures the human body and its environments, and exchanges information collected with other human factor devices.
+- 3.2.6 secure human factor**: The human factor in information security.
+
+## **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                   |
+|------|-----------------------------------|
+| CPU  | Central Processing Unit           |
+| DLS  | Distributed Ledger Systems        |
+| DLT  | Distributed Ledger Technology     |
+| IP   | Internet Protocol                 |
+| PDLS | Public Distributed Ledger Systems |
+| UUID | Universally Unique Identifier     |
+| VRF  | Verifiable Random Function        |
+
+## **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 or service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with this Recommendation.
+
+## 6 Background
+
+In recent years, personal human factor information has increased dramatically due to the development of personal health collection devices as well as hospital-based personal medical record data. One of the best models for the management and sharing of personal human factor data is the distributed ledger service model. The characteristics of the distributed ledger systems provide reliability using a distributed database with multiple nodes involved, and ensure transparency of the retrieval data using digital signatures and hash values. However, human factor data can be very sensitive in terms of information protection. Therefore, the public distributed ledger service model requires personal human factor information protection requirements (see Figure 1).
+
+![Figure 1 – Human factor distributed ledger service model diagram](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+The diagram illustrates the Human factor distributed ledger service model across three horizontal layers. The top layer, labeled 'Applications', contains five orange rectangular boxes: 'Personal human factor record', 'Electronic health record', 'Clinic trial', 'Well-being and safety management', and 'Person identification'. The middle layer, labeled 'Users', features seven icons representing different user groups: a person, a hospital, a person presenting to others, a building, a smartphone, a person in a wheelchair, and a classical building. The bottom layer, labeled 'Network', is a single green rectangular bar labeled 'PDLS: Public distributed ledger systems'. The text 'F.747.10(22)' is located in the bottom right corner of the diagram area.
+
+Figure 1 – Human factor distributed ledger service model diagram
+
+**Figure 1 – Human factor distributed ledger service model**
+
+This Recommendation describes the security requirements of the human factor distributed ledger service model, which can achieve goals of privacy protection and personal health big data utilization. The Recommendation also introduces the functional requirements of distributed ledger shared nodes to perform machine learning without decryption on encrypted data. It describes the incentive requirements in the distributed ledger service model to improve the quality of life by automating the distribution of health products directly to consumers and producers. The application of distributed ledger technology starts with the ability to track and manage health information production and distribution. In other words, the application of distributed ledger technology in the distribution of personal human factor information can ensure transparent tracking from the distribution process to the final use path. For this reason, individuals represented by individual nodes participating in the distributed ledger system can trust and use the information distributed. In addition, it is possible to provide a method for fundamentally blocking illegal distribution of personal human factor information.
+
+# 7 General requirements for distributed ledger systems of secure human factor services
+
+This clause describes the requirements for a secure distributed ledger movement management procedure that can achieve the conflicting goals of personal information protection and the use of personal human factor information big data. It introduces the functional requirements of a distributed ledger shared node to perform machine learning without decryption on encrypted data. For example, homomorphic encryption is a cryptographic technique that can perform all computations performed by a computer without decryption even in an encrypted state. Even in data analysis including personal information to be protected, machine learning can be optionally performed without personal information leakage or data loss.
+
+## 7.1 Functional requirements for public distributed ledger shared nodes
+
+The following are the functional requirements for public distributed ledger shared nodes:
+
+- Nodes are required to store the data of the distributed ledger chain accumulated from the first block.
+- The completion status is required to be delivered to the other nodes, as a node executes a distributed confirmation algorithm, when the transaction is verified.
+- In order to verify the validity of the distributed ledger generated at each round, the node is required to check the validity of the generated block by comparing it with the target hash value.
+- Each node is required to update and maintain shared data such as the public key list of all other nodes and the distributed ledger.
+- The node is required to propagate the transaction to other nodes until the agreement phase (e.g., transaction confirmation completion) in the transaction verification process.
+- The node is required to encrypt data of a transaction that requires security using the cryptographic keys (e.g., public key certificate [b-ITU-T X.509], homomorphic encryption [b-ISO 18033-6], verifiable random function (VRF) [b-IETF draft-irtf-cfrg-vrf-08] and inform the encryption key type.
+- The node is required to determine whether the decryption is necessary. If the decryption is needed, it decrypts and transmits it to the requesting node. If there is no decryption needed, the node encrypts it with the public key of the request node, and transmits it.
+
+## 7.2 Authentication requirements for new participating node
+
+Existing nodes are recommended to provide the functions outlined in clauses 7.2.1 to 7.2.3, to authenticate new participating nodes in a distributed ledger shared system.
+
+### 7.2.1 Requirements for requesting new node authentication
+
+- The new node is recommended to have at least two pairs of encryption keys to use (e.g., public key certificate [b-ITU-T X.509], homogeneous encryption keys [b-ISO 18033-6] before making a request.
+- The new node is recommended to encrypt the request message with its own private key and to send the encrypted data and its public key together to the node.
+- Each node is recommended to update the list of verified public keys of the new and existing nodes and to store the public key list of the distributed ledger shared system to participate, when the node verifies and transmits the authenticated information.
+
+### 7.2.2 Authentication functional requirements for the node
+
+- The node is recommended to verify the validity by decrypting the encrypted data transmitted from the new participation desired node received together with the public key, to encrypt the verified information and the public key list with the public key of the new node and transmits the encrypted information.
+- The node is recommended to be a list of public keys of all the nodes participating in the distributed ledger shared system and update its corresponding public key list each time it handles authentication of the new node.
+- Each time the node is recommended to update its public key list, it is required to encrypt the public key list with its own private key and send it to all nodes participating in the distributed ledger shared system.
+
+- The node is recommended to permanently store the verified information about the nodes participating in the distributed ledger shared system together with the verification time and the address of the participating node.
+
+### **7.2.3 Requirements for new node authentication verification of existing nodes**
+
+- Existing nodes are recommended to verify the digital signature of the public key list sent by the node and to update it with the new public key list.
+- Existing nodes are recommended to verify the participation of the authenticated new node by checking the new public key list.
+
+## **7.3 Security requirements for distributed ledger system**
+
+Existing nodes are recommended to follow the provisions in this clause.
+
+- Attempts to manipulate information in an existing shared distributed ledger are required to be verified using an electronic signature and rejected in the distributed ledger.
+- Among the main chains used in the distributed ledger system, chains with different contents from the longest chain before an arbitrary b-block depth at the time a new block is created are required to be rejected in the distributed ledger. Here b is a number larger than equal to 1.
+- The data is required to be rejected in the process of creating the distributed ledger, when data with duplicate addresses (e.g., IP, UUID) are added to the distributed ledger system.
+- It is required that the common random source (e.g., cryptographic nonce [b-NIST]) be the same for blocks of any d-block depth. Blocks after d-block depth are required to update the common random source by a g-block depth. When updated, the hash of the newly added block is recommended to be used as a random source.
+
+NOTE – Here d-block and g-block depth means any blocks with depth larger than 1.
+
+- Chains containing blocks with different hash values of previous blocks and Merkle tree root values are required to be rejected in the distributed ledger.
+- If an error node occurs amongst the constituent nodes of the distributed ledger system, the nodes without errors are recommended to be maintained if above the pre-defined consensus level for the DLS.
+
+## **7.4 Integrity maintaining requirements for a distributed ledger system**
+
+Existing nodes are recommended to follow the provisions in this clause.
+
+- Each node is recommended to eliminate an attempt to manipulate information in the existing shared distributed ledger. If such an attack is detected, the number of nodes is recommended to be accumulated to obtain the ratio of the hashing force. It is recommended to compare the current number of block trees with the value of the threshold value to calculate safety and transmit (broadcast) related information and node addresses to all nodes.
+- Each node is recommended to remove the longest chains commonly used in the distributed ledger system and chains with different contents from the distributed ledger system.
+- Each node is recommended to remove the chain containing blocks with different hash values or Merkle tree root values of the previous blocks in the distributed ledger and calculate the accumulated number of nodes that were subject to attacks to determine whether the distributed ledger is safe, and to transmit (broadcast) the relevant information and the address of the node.
+
+- When an error or forgery node occurs among the components of the distributed ledger system, each node is recommended to remove and accumulate the number of nodes attempted to perform an error or attack to obtain a hashing power ratio. In the distributed ledger, the number of secure nodes is recommended to be maintained to be greater than the threshold value and related information and node addresses are recommended to be transmitted (broadcast).
+- Each node is recommended to reject the data in the distributed ledger creation process when new data with duplicate addresses is added to the data of the distributed ledger system.
+
+# 8 Functional capabilities for distributed ledger systems of secure human factor services
+
+As an incentive, it is required to improve the quality of life in a distributed ledger service model by automating direct distribution of personal human factor information. The application of distributed ledger technology starts with the ability to track and manage human factor information production and distribution. In other words, the application of distributed ledger technology in the distribution of personal human factor information can ensure transparent tracking from the distribution process to the final use path. For this reason, individuals represented by individual nodes participating in the distributed ledger system can trust and use the information distributed. In addition, it is possible to provide a method for fundamentally blocking illegal distribution of personal human factor information.
+
+## 8.1 Distributed ledger structure in distribution of personal human factor information
+
+Following the convention, the first transaction of the ledger is a special transaction that starts a new incentive (e.g., virtual coins [b-ITU-T F.751.0]) that will be disbursed to the creator of the ledger. This incentive is rewarded to nodes to maintain a distributed ledger and distributed from the beginning to distribute personal human factor information. The techniques for providing and distributing these incentives are recommended to be agreed in advance because they operate as distributed systems. The reason to continually add a certain number of new incentives is the compensation for nodes (miners) that consume resources to operate the distributed ledger system. These nodes consume central processing unit (CPU) computational power, memory and coins.
+
+## 8.2 Two functions in distributed ledger structure in the distribution of personal human factor information
+
+As a method to reduce the waiting time while increasing the mining speed, a technique of decomposing the structure of the basic distributed ledger into three functions can be optionally used. This can be seen as selecting the main chain in the distributed ledger protocol (e.g., the longest chain selection technique), which leads to the selection of the secure ledger among all ledgers at each depth of the ledger tree. Here, the depth of a ledger is defined as the distance from the origin ledger (the number of connected blocks in the ledger).
+
+In a distributed ledger, the ledger serves three purposes. That is, it serves to elect the captain, add transactions to the main chain, and vote for the ancestor ledger through parent link relationships. In expressing the ledger as a conceptual action, it is divided into two functions (see Figure 2). The proposal function bundles transactions of the same depth in the original ledger tree. The voting function selects the ledger part of the ledger by voting for the same depth of transactions in the ledger tree. The selected ledger takes the partial ledgers of the transactions and forms the final ledger. This voting function operates at the same depth of the ledger tree and creates a parent-child connection. Therefore, the parent-child link of the original ledger tree has two functions that are explicitly separated: 1) Providing some order of ledgers in the transaction part at the same depth, 2) the voting function which helps to vote for each other to screen the ledger. The overall structure of the distributed ledger for the distribution of personal human factor information described below is shown in Figure 2.
+
+Due to the distributed nature of DLS, it faces stability problems. In DLS, each node can record a transaction, but in the end, which node is selected is a result of the consensus algorithm [b-ITU-T F.751.0]. The design of a DLS is required to be taken into consideration as one of the many factors affecting stability, and the distributed ledger is recommended to recover stable service through adaptive processing of the system. In order to solve the stability problem of DLS, the common random source (e.g., cryptographic nonce [b-NIST]) is kept the same for d-block depths, and blocks after d-depths should update the common random source by g-block depths. When updated, the hash of the newly added block is used as a random source. If  $d = 1$ , it is restored to the basic update rule that forks every epoch, most vulnerable to contamination (balanced) attacks. In order to normally increase the security threshold,  $d$  may be increased. When  $d = \infty$ , all blocks use the nonce of the origin block as a common random source. This is the longest chain protocol that does not allow forking, allowing for private prediction of the chain by the contaminated owner of the secret key.
+
+![Figure 2 – Distributed ledger service model structure. The diagram illustrates a hierarchical tree of blocks. Each block is a rectangle containing three blue circles, representing a 'Block (Proposal and voting function)' with 'Transactions'. Solid arrows represent 'Parent-child links' between blocks. Dashed lines connect blocks horizontally at the same level. On the right, two vertical double-headed arrows indicate 'd-block depth: fork delay' for the top three levels and 'g-block depth: fork allowed' for the subsequent levels. A legend at the bottom identifies the block icon, the parent-child link arrow, and the transaction circle. The code 'F.747.10(22)' is in the bottom right corner.](4e4be0bd8b235167902f2c03e41da651_img.jpg)
+
+Figure 2 – Distributed ledger service model structure. The diagram illustrates a hierarchical tree of blocks. Each block is a rectangle containing three blue circles, representing a 'Block (Proposal and voting function)' with 'Transactions'. Solid arrows represent 'Parent-child links' between blocks. Dashed lines connect blocks horizontally at the same level. On the right, two vertical double-headed arrows indicate 'd-block depth: fork delay' for the top three levels and 'g-block depth: fork allowed' for the subsequent levels. A legend at the bottom identifies the block icon, the parent-child link arrow, and the transaction circle. The code 'F.747.10(22)' is in the bottom right corner.
+
+**Figure 2 – Distributed ledger service model structure**
+
+## 8.3 Distributed ledger system maintenance methodologies
+
+This representation of functional separation of a distributed ledger is much more complicated than that of a traditional distributed ledger, but it can improve the performance of the distributed ledger by deriving a faster consensus. This quick consensus deriving function can increase the number of ledgers in the transaction part without compromising the security of the distributed ledger in the proposed function. Therefore, the number of ledgers will be limited only by the capacity of the underlying communication network. The consensus can be optionally confirmed with low latency and high reliability since the voting function of multiple transactions will be voted in parallel to the ledger of the proposal for quick confirmation. The personal human factor information distributed ledger system is easy to manage because the general ledger generation rate has increased tremendously, and the number of partial ledgers of the proposed function per depth can be small.
+
+This distributed ledger system can compromise transparency by concentrating the power of hashing into the proposed function of a specific transaction in the process of selecting the ledger. As shown in Figure 3, if an attacker's hashing power is strong in a specific ledger of the proposed function, it can be very vulnerable to security. Figure 3 shows an example of a chain of ledgers being destroyed
+
+or contaminated by the concentration of the hashing power of an attacker. If an attacker were able to gather more CPU computational power, memory, and coins in one place than all secure nodes, the attacker would have to decide whether to use it to steal honest node incentives or use it to cooperate. It would be necessary to provide an incentive policy so that it would be more beneficial for an attacker to follow the rules than to undermine the transparency of the personal human factor information distributed ledger system. This incentive is required to be adjusted to be distributed across participating nodes. The attacker can provide such a rule that it would be more profitable to associate with all other nodes. This rule is recommended to keep the number of honest nodes above the threshold value (e.g.,  $CD (1 + \alpha)/(\alpha-1)/\log(\alpha)$ ) according to the ratio of the hashing force of the attacker ( $\alpha$ ). Here C and D are capacity and delay of communication networks.
+
+What can be seen from this formula is that if  $\alpha$  is close to 0, the attacker's hashing power is weak, it can be said that there is no problem in the security of distributed ledger systems even if the number of the voter block-tree is a small number. However, if  $\alpha$  is close to 1, that is, if the attacker's hashing power is strong, the number of the voter block-tree should be increased exponentially. At this point, it can be observed that it becomes very vulnerable to security.
+
+![Diagram illustrating pollution prevention in a distributed ledger service model. The diagram shows a tree of blocks, with honest blocks in white and attacker's proposal blocks in red. The diagram is divided into two sections: 'd-block depth: fork delay' and 'g-block depth: fork allowed'. A legend at the bottom defines the symbols: a white rectangle for 'Block (Proposal and voting function)', a blue arrow for 'Parent-child link', a blue circle for 'Transaction', and a red rectangle for 'Attacker's proposal block'. The reference code F.747.10(22) is shown at the bottom right.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg)
+
+The diagram illustrates a block tree structure. At the top, there are three white blocks connected vertically by blue arrows (parent-child links). Each block contains three blue circles (transactions). A dashed vertical line separates the top section from the bottom section. The top section is labeled 'd-block depth: fork delay' and contains three white blocks. The bottom section is labeled 'g-block depth: fork allowed' and contains five white blocks and one red block (attacker's proposal block). The red block is connected to one of the white blocks in the top section. The legend at the bottom shows a white rectangle for 'Block (Proposal and voting function)', a blue arrow for 'Parent-child link', a blue circle for 'Transaction', and a red rectangle for 'Attacker's proposal block'. The reference code F.747.10(22) is shown at the bottom right.
+
+Diagram illustrating pollution prevention in a distributed ledger service model. The diagram shows a tree of blocks, with honest blocks in white and attacker's proposal blocks in red. The diagram is divided into two sections: 'd-block depth: fork delay' and 'g-block depth: fork allowed'. A legend at the bottom defines the symbols: a white rectangle for 'Block (Proposal and voting function)', a blue arrow for 'Parent-child link', a blue circle for 'Transaction', and a red rectangle for 'Attacker's proposal block'. The reference code F.747.10(22) is shown at the bottom right.
+
+**Figure 3 – Example of pollution prevention in distributed ledger service model**
+
+In the process of selecting the proposal block, the function of the block is recommended to be determined by adjusting the power of hashing and coins. At this time, it can be seen that if the attacker's hashing power and coins is strong, the security is very vulnerable. If an attacker could gather more computational power and coins than all honest nodes, a decision would need to be taken whether to use it to steal the benefits of an honest node, or to use it to cooperate. Incentive policies are recommended to be provided so that it would be more beneficial for attackers to adhere to the rules than to undermine the system and the legitimacy of their own wealth. Using a policy that prevents profits from being concentrated on a specific proponent block, this is recommended to involve providing such a rule that attackers would benefit more from allocating with all other nodes.
+
+## Annex A
+
+### Application to secure human factor distributed ledger service model
+
+(This annex forms an integral part of this Recommendation.)
+
+The distributed ledger scenario shown in Figure A.1 can safely and transparently manage not only hospital-centred personal human factor data, but also personal-centred human factor data such as personal health collection devices. In the example of using personal health information sharing in Figure A.1, reliability can be provided by using a distributed ledger in which multiple nodes participate, and digital signatures and hash values can be used to ensure transparency in search data. However, personal human factor data can be very sensitive in terms of data protection. Such sensitive data is registered in an encrypted state using an encryption technique capable of processing big data. The mobility procedure for sensitive personal human factor information follows the requirements and procedures of the distributed ledger shared system in clause 7.2 using an encryption algorithm (see Figure A.1). In addition, the distributed ledger system for personal human factor information is required to be operated to satisfy the requirements for the incentive function in clause 8.3 for activation and maintenance.
+
+![Diagram of Figure A.1 showing the secure distributed ledger service model. It illustrates the interaction between various entities (Enterprise, Hospital, Government, School/Research centre) and a public distributed ledger system. The diagram shows a network of nodes (smartphones) where a new node joins and is authenticated by existing nodes. It depicts a patient requesting encrypted data registration and a doctor requesting safe access using isomorphic encryption. A central server manages the incentive distribution policy. The system relies on 'enough honest nodes' for safety.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg)
+
+Enterprise
+Hospital
+Government
+School/Research centre
+
+Safe sharing of personal human factor information
+
+New node
+Existing nodes
+Existing node (Authenticating)
+Encrypted personal human factor information registration request
+Distributed ledger requires authentication
+Incentive distribution policy
+Request for safe access to personal human factor information using isomorphic encryption techniques, etc.
+Enough honest nodes
+
+Safety for personal human factor information in public distributed ledger system
+
+F.747.10(22)
+
+Diagram of Figure A.1 showing the secure distributed ledger service model. It illustrates the interaction between various entities (Enterprise, Hospital, Government, School/Research centre) and a public distributed ledger system. The diagram shows a network of nodes (smartphones) where a new node joins and is authenticated by existing nodes. It depicts a patient requesting encrypted data registration and a doctor requesting safe access using isomorphic encryption. A central server manages the incentive distribution policy. The system relies on 'enough honest nodes' for safety.
+
+**Figure A.1 – Scenarios for secure distributed ledger service model**
+
+## Bibliography
+
+- [b-ITU-T F.751.0] Recommendation ITU-T F.751.0 (2020), *Requirements for distributed ledger systems*.
+- [b-ITU-T X.509] Recommendation ITU-T X.509 (2019) | ISO/IEC 9594-8:2020, *Information technology – Open Systems Interconnection – The Directory: Public-key and attribute certificate frameworks*.
+- [b-ITU-T TS FG DLT D1.1] Technical Specification ITU-T FG DLT D1.1 (2019), *Distributed ledger technology terms and definitions*.
+- [b-IETF draft-irtf-cfrg-vrf-08] IETF draft-irtf-cfrg-vrf-08 (2020), *Verifiable Random Functions (VRFs)*. <https://tools.ietf.org/html/draft-irtf-cfrg-vrf-08>
+- [b-ISO 6385] ISO 6385:2016, *Ergonomics principles in the design of work systems*.
+- [b-ISO 18033-6] ISO 18033-6:2019, *IT Security techniques – Encryption algorithms – Part 6: Homomorphic encryption*.
+- [b-ISO 22739] ISO 22739:2020, *Blockchain and distributed ledger technologies – Vocabulary*.
+- [b-NIST] NISTIR 8202 (2018). *Blockchain Technology Overview*.
+- [b-WHO] World Health Organization (2006), *Constitution of the World Health Organization – Basic Documents*, Forty-fifth edition, Supplement.
+- [b-Wickens] Wickens, D., Gordon, S., Liu, Y. (1997), *An Introduction to Human Factors Engineering*. pp.2-7. New York, NY: Longman.
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.747.12-202212-I_PDF-E/raw.md b/marked/F/T-REC-F.747.12-202212-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..433f94e1e4af0454e52809120ae932368a2bbd9e
--- /dev/null
+++ b/marked/F/T-REC-F.747.12-202212-I_PDF-E/raw.md
@@ -0,0 +1,437 @@
+
+
+# Recommendation **ITU-T F.747.12 (12/2022)**
+
+SERIES F: Non-telephone telecommunication services  
+Multimedia services
+
+---
+
+## **Requirements for artificial intelligence based machine vision system in smart logistics warehouse**
+
+![ITU logo](390120de4fe440c42fea8154fcaad334_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 F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+### **TELEGRAPH SERVICE**
+
+|                                                                 |             |
+|-----------------------------------------------------------------|-------------|
+| Operating methods for the international public telegram service | F.1–F.19    |
+| The gentex network                                              | F.20–F.29   |
+| Message switching                                               | F.30–F.39   |
+| The international telemessage service                           | F.40–F.58   |
+| The international telex service                                 | F.59–F.89   |
+| Statistics and publications on international telegraph services | F.90–F.99   |
+| Scheduled and leased communication services                     | F.100–F.104 |
+| Phototelegraph service                                          | F.105–F.109 |
+
+### **MOBILE SERVICE**
+
+|                                                        |             |
+|--------------------------------------------------------|-------------|
+| Mobile services and multdestination satellite services | F.110–F.159 |
+|--------------------------------------------------------|-------------|
+
+### **TELEMATIC SERVICES**
+
+|                                           |             |
+|-------------------------------------------|-------------|
+| Public facsimile service                  | F.160–F.199 |
+| Teletex service                           | F.200–F.299 |
+| Videotex service                          | F.300–F.349 |
+| General provisions for telematic services | F.350–F.399 |
+
+### **MESSAGE HANDLING SERVICES**
+
+F.400–F.499
+
+### **DIRECTORY SERVICES**
+
+F.500–F.549
+
+### **DOCUMENT COMMUNICATION**
+
+|                                      |             |
+|--------------------------------------|-------------|
+| Document communication               | F.550–F.579 |
+| Programming communication interfaces | F.580–F.599 |
+
+### **DATA TRANSMISSION SERVICES**
+
+F.600–F.699
+
+### **MULTIMEDIA SERVICES**
+
+**F.700–F.799**
+
+## **ISDN SERVICES**
+
+F.800–F.849
+
+## **UNIVERSAL PERSONAL TELECOMMUNICATION**
+
+F.850–F.899
+
+## **ACCESSIBILITY AND HUMAN FACTORS**
+
+F.900–F.999
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.747.12
+
+# Requirements for artificial intelligence based machine vision system in smart logistics warehouse
+
+## Summary
+
+With the rapid development of industrial automation and logistics technology in accordance with the market demand for high-tech, machine vision technology has begun to enable the automation transformation of logistics warehouse systems. The application of machine vision technology in the field of logistics warehouse has enabled the rapid evolution of goods sorting, goods palletizing and de-palletizing, goods handling and shelf inventory from intensive manual work to intelligence and automation, improving the operational efficiency and management capabilities of logistics warehouse.
+
+Recommendation ITU-T F.747.12 specifies the requirements and framework for artificial intelligence based machine vision system in smart logistics warehouse, and provides use cases. This Recommendation is intended to guide the design and development of machine vision systems in smart logistics warehouse.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.747.12 | 2022-12-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/15193">11.1002/1000/15193</a> |
+
+## Keywords
+
+Artificial intelligence, framework, machine vision system, requirements, smart logistics warehouse.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                                                                     | 1    |
+| 4 Abbreviations and acronyms .....                                                                                | 2    |
+| 5 Conventions .....                                                                                               | 2    |
+| 6 Overview .....                                                                                                  | 2    |
+| 7 Framework.....                                                                                                  | 2    |
+| 8 Requirements .....                                                                                              | 3    |
+| 8.1 Device requirements .....                                                                                     | 3    |
+| 8.2 Service requirements .....                                                                                    | 4    |
+| 8.3 Application requirements .....                                                                                | 6    |
+| Appendix I – Use cases of artificial intelligence based machine vision system in a smart logistics warehouse..... | 8    |
+| I.1 Goods sorting.....                                                                                            | 8    |
+| I.2 Goods palletizing and de-palletizing.....                                                                     | 8    |
+| I.3 Shelf inventory .....                                                                                         | 8    |
+| I.4 Goods handling.....                                                                                           | 9    |
+| I.5 Logistics warehouse environment monitoring .....                                                              | 9    |
+| Bibliography.....                                                                                                 | 10   |
+
+
+
+# Recommendation ITU-T F.747.12
+
+## Requirements for artificial intelligence based machine vision system in smart logistics warehouse
+
+## 1 Scope
+
+This Recommendation specifies requirements and framework for artificial intelligence (AI) based machine vision systems (MVSs) in a smart logistics warehouse (SLW).
+
+The scope of this Recommendation includes:
+
+- overview of AI based MVS in SLW;
+- framework of AI based MVS in SLW;
+- requirements of AI based MVS in SLW.
+
+Use cases of AI based MVS in SLW are provided 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 H.627] Recommendation ITU-T H.627 (2020), *Signalling and protocols for a video surveillance system*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 accuracy** [b-ISO/IEC 2382]: Qualitative measure of the magnitude of error, preferably expressed as a function of the relative error, a high value of this measure corresponding to a small error.
+
+**3.1.2 algorithm** [b-ISO/IEC 11557]: A set of rules for transforming the logical representation of data.
+
+**3.1.3 machine vision** [b-ITU-T F.748.16]: Signal processing to acquire, process and interpret an image or video to support visual analysis for applications, such as automatic inspection, process control and guidance.
+
+### 3.2 Terms defined in this Recommendation
+
+None.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|     |                               |
+|-----|-------------------------------|
+| 2D  | Two Dimensional               |
+| 3D  | Three Dimensional             |
+| AI  | Artificial Intelligence       |
+| AMR | Automated Mobile Robot        |
+| DM  | Data Matrix                   |
+| MVS | Machine Vision System         |
+| OCR | Optical Character Recognition |
+| QR  | Quick Response                |
+| ROI | Region of Interest            |
+| SKU | Stock Keeping Unit            |
+| SLW | Smart Logistics Warehouse     |
+
+# 5 Conventions
+
+In this Recommendation:
+
+- 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.
+
+# 6 Overview
+
+In smart logistics warehouse (SLW), based on the real-time management of the goods, shelves and logistics warehouse environments, artificial intelligence (AI) enabled visual analysis technology is widely used, which greatly improves the work efficiency of SLW. In the process of goods entering and leaving the SLW, the machine vision system (MVS) (e.g., high-resolution industrial cameras) collects and analyses label information of the goods in real-time, and quickly sorts goods according to the variety, material and weight of the goods. At the same time, it can identify abnormal appearance states such as stains, wrinkles and breakages, and can provide event reminders for abnormal goods, label errors and other issues. Through shelf status recognition, the real-time analysis of the shelf situation is carried out to determine whether the shelf is full and whether the goods are placed in a normal state, to realize the intelligent management of the shelf and improve the utilization rate of the shelf. The automated mobile robot (AMR) is responsible for the handling of goods in SLW. AMR's vision system collects ground conditions and surrounding environmental obstacles information, extracts feature information, matches database information, and completes map creation, positioning and navigation, which improves the efficiency of goods transportation. MVS identifies the stacking state of the goods and calculates the grasping pose, and controls such as the mechanical arm to perform the tasks of automatic grasping, palletizing and de-palletizing of the goods. The surveillance camera conducts real-time monitoring of the potential safety hazards in the SLW environment, the loading situation of the transport vehicle, and the use rate of the platform.
+
+# 7 Framework
+
+Figure 1 shows the framework of AI based MVS in SLW.
+
+![Figure 1 – Framework of artificial intelligence based machine vision system in a smart logistics warehouse. The diagram shows three layers: Application layer, Service layer, and Device layer. The Application layer includes goods sorting, palletizing/de-palletizing, handling, shelf inventory, and environment monitoring. The Service layer includes Open capability components (Algorithm and Basic services), Algorithm management components (scheduling, warehouse, training), Algorithm components (localization, measurement, processing, inspection, calibration, identification, alignment, navigation), and Basic components (access, configuration, control, operation and maintenance). The Device layer includes industrial camera, surveillance camera, code reader, AMR, mechanical arm, and others.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg)
+
+|                                        |                                  |                          |                                  |                                            |
+|----------------------------------------|----------------------------------|--------------------------|----------------------------------|--------------------------------------------|
+| <b>Application layer</b>               |                                  |                          |                                  |                                            |
+| Goods sorting                          | Goods palletizing/de-palletizing | Goods handling           | Shelf inventory                  | Logistics warehouse environment monitoring |
+| <b>Service layer</b>                   |                                  |                          |                                  |                                            |
+| <b>Open capability components</b>      |                                  |                          |                                  |                                            |
+| Algorithm capability service           |                                  | Basic capability service |                                  |                                            |
+| <b>Algorithm management components</b> |                                  |                          | <b>Basic components</b>          |                                            |
+| Algorithm scheduling                   | Algorithm warehouse              | Algorithm training       | Device access                    |                                            |
+| <b>Algorithm components</b>            |                                  |                          | Device configuration             |                                            |
+| Target localization                    | Target measurement               | Image processing         | Device control                   |                                            |
+| Target calibration                     | Target identification            | Visual alignment         | Device operation and maintenance |                                            |
+| <b>Device layer</b>                    |                                  |                          |                                  |                                            |
+| Industrial camera                      | Surveillance camera              | Code reader              | AMR                              | Mechanical arm ...                         |
+
+Figure 1 – Framework of artificial intelligence based machine vision system in a smart logistics warehouse. The diagram shows three layers: Application layer, Service layer, and Device layer. The Application layer includes goods sorting, palletizing/de-palletizing, handling, shelf inventory, and environment monitoring. The Service layer includes Open capability components (Algorithm and Basic services), Algorithm management components (scheduling, warehouse, training), Algorithm components (localization, measurement, processing, inspection, calibration, identification, alignment, navigation), and Basic components (access, configuration, control, operation and maintenance). The Device layer includes industrial camera, surveillance camera, code reader, AMR, mechanical arm, and others.
+
+**Figure 1 – Framework of artificial intelligence based machine vision system in a smart logistics warehouse**
+
+The framework of AI based MVS in SLW (hereafter "MVS") consists of three layers: device layer, service layer and application layer.
+
+The device layer represents the devices used for data collection and control in MVS, including industrial cameras, surveillance cameras, code readers, AMRs and mechanical arms, etc.
+
+The service layer consists of four components, known as basic components, algorithm components, algorithm management components and open capability components. Basic components provide basic services for MVS, including device access, device configuration, device control, and device operation and maintenance. The algorithm component provides algorithm services for MVS, including algorithms for target localization, target measurement, image processing, appearance inspection, target calibration, target identification, visual alignment and visual navigation. The algorithm management component provides algorithm-related management services for MVS, including algorithm scheduling, algorithm warehouse management and algorithm training. The open capability component provides interface services for MVS, including algorithm capability services and basic capability services.
+
+The application layer includes service application scenarios such as goods sorting, goods palletizing/de-palletizing, goods handling, shelf inventory, and logistics warehouse environment monitoring.
+
+# 8 Requirements
+
+### 8.1 Device requirements
+
+- MVS is recommended to support data collection, including but not limited to video, image, point cloud, quick response (QR) code and barcode.
+- The industrial camera is recommended to support timed exposure and trigger delay functions.
+
+- The industrial camera is recommended to support region of interest (ROI) functions.
+- The industrial camera is recommended to support the centre horizontal resolution of output image no less than 85% of image height.
+- The code reader is recommended to support barcode format including Code 128, Code 39, etc.
+- The code reader is recommended to support QR code format including QR and data matrix (DM), etc.
+- The surveillance camera is recommended to support intelligent analysis function, including fire and smoke detection, AMR traffic jam detection, etc.
+- AMR is recommended to support QR code navigation and laser navigation.
+- AMR is recommended to support obstacle detection and path planning.
+
+### **8.2 Service requirements**
+
+#### **8.2.1 Requirements of basic components**
+
+- MVS is recommended to support device access, including device manual addition, device retrieve addition, and device deletion.
+- MVS is recommended to support device access protocols [ITU-T H.627].
+- MVS is recommended to support device configuration, including image parameters configuration (frame rate, exposure, gain and gamma), communication parameters configuration and image storage configuration (goods surface original image, goods surface original image cut-out and goods panorama image).
+- MVS is recommended to support device control, including data reading, command issuance, device timing, device restart and device reset.
+- MVS is recommended to support device operation and maintenance, including the management of device files information, device status, device upgrading and device alarm.
+
+#### **8.2.2 Requirements of algorithm components**
+
+- MVS is recommended to support target localization algorithms to locate or detect certain features in the image, including feature matching, grayscale matching, graphic localization, rectangle detection, vertex detection, etc.
+- MVS is recommended to support target calibration algorithms to realize the conversion from image coordinates to actual coordinates, including checkerboard calibration, N-point calibration, distortion calibration, mapping calibration, etc.
+- MVS is recommended to support target measurement algorithms to achieve distance measurement between target object elements in the image, including line-circle measurement, line-line measurement, circle-circle measurement, point-circle measurement, point-line measurement, distance detection, etc.
+- MVS is recommended to support target identification algorithms to realize the identification of target objects in the image, including barcode recognition, QR code recognition, optical character recognition (OCR), etc.
+- MVS is recommended to support image processing algorithms to realize image pre-processing of the target image, including image filtering, image enhancement, distortion correction, graph scaling and graph stitching, etc.
+
+NOTE – When the image has poor contrast, more burrs, more interference and less obvious features, image pre-processing can be considered.
+
+- MVS is recommended to support visual alignment algorithms to calculate the amount of movement (positional movement and angular movement) required from object alignment to the target object, including single-point alignment, point set alignment, line alignment, etc.
+- MVS is recommended to support appearance inspection algorithms to verify and compare target images with standard images to find appearance defects, including detection of printed characters and patterns appearance defects, surface defect detection without texture background, linear edge defect detection, arc edge defect detection, etc.
+- MVS is recommended to support visual navigation algorithms, and to complete the autonomous navigation and positioning of the target object by associating the image information collected by the camera with the actual position of the target object.
+
+#### **8.2.3 Requirements of algorithm management components**
+
+- MVS is recommended to support algorithm scheduling, realizes the scheduling and management of algorithm resources, including algorithm task configuration, algorithm task control (start, execution and cancellation), algorithm time-consuming statistics, and algorithm scheduling result storage.
+- MVS is recommended to support algorithm tasks of adding, deleting, starting and stopping.
+- MVS is recommended to support algorithm task configuration, including data source devices, data formats, algorithm types, algorithm parameters.
+- MVS is recommended to support computing resource management, assign computing resources to algorithm tasks for scheduling, and support viewing computing resource usage situation.
+- MVS is recommended to support algorithm warehouse management, including adding, deleting, modifying and querying.
+- MVS is recommended to support algorithm training, including sample management, model training, and algorithm deployment.
+- MVS is recommended to support sample management, including sample data adding, deleting, modifying and querying.
+- MVS is recommended to support sample data annotation, including annotation data adding, deleting, modifying, and querying.
+- MVS is recommended to support the training task management, including training task adding, deleting, starting, and stopping, and support querying the progress and results of training tasks.
+- MVS is recommended to support model validation and evaluation.
+- MVS is recommended to support algorithm deployment.
+
+#### **8.2.4 Requirements of open capability components**
+
+- MVS is recommended to support algorithm capability services, including algorithm scheduling open capability, algorithm warehouse open capability and algorithm training open capability.
+- MVS is recommended to support basic capability services, including device access open capability, device configuration open capability, device control open capability, and device operation and maintenance open capability.
+
+### **8.3 Application requirements**
+
+#### **8.3.1 Requirements of goods sorting**
+
+- MVS is recommended to support the identification of the appearance, size and quantity of goods during the sorting process, and is not recommended to be restricted by the placement direction. The identification speed of the number of parcels is recommended  $\geq 5\,000$  pieces/hour, and the resolution of goods image collection is recommended  $\geq 6$  million pixels.
+- MVS is recommended to support the measurement of the length, width, height of the goods during the sorting process. The volume measurement range is recommended to support  $150\text{ mm} \times 150\text{ mm} \times 30\text{ mm}$  to  $1\,200\text{ mm} \times 1\,000\text{ mm} \times 700\text{ mm}$  (regular goods), and the measurement and identification accuracy is recommended less than  $\pm 10\text{ mm}$ .
+- MVS is recommended to support simultaneous identification of multiple sides of goods in the process of parcel sorting, and it is recommended to support simultaneous identification of six sides of goods.
+- MVS is recommended to support the identification of barcodes, QR codes and other label information on the surface of the goods during the sorting process. The code reading rate is recommended  $\geq 99\%$ , and the identification speed of a single barcode or QR code is recommended  $\leq 100\text{ ms}$ .
+- MVS is recommended to support the single identification of multi-goods label information during the sorting process.
+- MVS is recommended to support abnormal code identification during the sorting process, including surface dirt, damage, scratches, etc.
+- MVS is recommended to support the identification of abnormal status information, including goods accumulation, blockage and overlapping during the sorting process, and identification accuracy rate is recommended  $\geq 99\%$ .
+- MVS is recommended to support the collection of a complete and clear image of goods during the sorting process, which can clearly identify codes and label information.
+
+#### **8.3.2 Requirements of goods palletizing and de-palletizing**
+
+- MVS is recommended to support automatic identification of multiple stock keeping units (SKUs).
+- MVS is recommended to support the identification of goods abnormal states, including appearance defects, etc.
+- MVS is recommended to support the identification of the stacking method and volume size of the goods.
+- MVS is recommended to support the calculation of accurate grab location, placement location and trajectory location through intelligent algorithms to control the mechanical arm to quickly grab and stack goods.
+
+#### **8.3.3 Requirements of shelf inventory**
+
+- MVS is recommended to support the identification of the number of goods on the shelf.
+- MVS is recommended to support the identification of abnormal information, including dirty and damaged surfaces of goods.
+- MVS is recommended to support the identification of falling goods on the shelf, and is recommended to support the identification of goods that are at risk of falling.
+- MVS is recommended to support the identification of vacant and occupied status of shelves.
+- MVS is recommended to support the identification of shelf storage space volume.
+
+#### **8.3.4 Requirements of goods handling**
+
+- MVS is recommended to support the identification of label information on the surface of the AMR transported goods, the identification accuracy is recommended  $\geq 99\%$ , and the identification speed is recommended  $\leq 500$  ms.
+- MVS is recommended to support the identification of obstacles and environmental information around the AMR.
+- MVS is recommended to support the identification of ground identification mark information.
+- MVS is recommended to support shelf label identification, and the identification accuracy is recommended  $\geq 99\%$ .
+- MVS is recommended to support the automatic planning of handling routes of AMR based on the logistics warehouse map, surrounding obstacles and environmental information.
+
+#### **8.3.5 Requirements of logistics warehouse environment monitoring**
+
+- MVS is recommended to support the identification of abnormal environmental information, including smoke, fire and water leakage, etc.
+- MVS is recommended to support the identification of violent sorting and handling behaviours of workers.
+- MVS is recommended to support the identification of AMR traffic jam.
+- MVS is recommended to support the identification of falling goods during AMR handling.
+- MVS is recommended to support the identification of the accumulation of goods in a specific area.
+- MVS is recommended to support the identification of loaded vehicle information, including colour, licence plate, vehicle brand, etc.
+- MVS is recommended to support the identification of vehicle loading rate, including empty, half and full, etc.
+- MVS is recommended to support the identification of platform usage, including occupied, unoccupied.
+
+## Appendix I
+
+## Use cases of artificial intelligence based machine vision system in a smart logistics warehouse
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Figure I.1 shows a service scenario of smart logistics warehouse.
+
+![A 3D perspective diagram of a smart logistics warehouse. The main area shows a large warehouse floor with high shelves filled with orange boxes. Several yellow AMRs (Automated Mobile Robots) are moving through the aisles. On the left, two white trucks are docked at a loading bay, with a yellow forklift and a platform nearby. A conveyor belt system on the right leads to a 'Goods sorting' area. An inset image in the top right shows a close-up of a robotic arm performing 'Goods palletizing and de-palletizing'. Labels with red leader lines point to various components: 'AMR', 'Shelf', 'Goods', 'Transportation vehicle and platform', 'Goods handling', 'Shelf inventory', and 'Goods sorting'. The code 'F.747.12(22)' is in the bottom right corner.](bd671b21db63e6fdb2196e9b18502aac_img.jpg)
+
+A 3D perspective diagram of a smart logistics warehouse. The main area shows a large warehouse floor with high shelves filled with orange boxes. Several yellow AMRs (Automated Mobile Robots) are moving through the aisles. On the left, two white trucks are docked at a loading bay, with a yellow forklift and a platform nearby. A conveyor belt system on the right leads to a 'Goods sorting' area. An inset image in the top right shows a close-up of a robotic arm performing 'Goods palletizing and de-palletizing'. Labels with red leader lines point to various components: 'AMR', 'Shelf', 'Goods', 'Transportation vehicle and platform', 'Goods handling', 'Shelf inventory', and 'Goods sorting'. The code 'F.747.12(22)' is in the bottom right corner.
+
+**Figure I.1 – Service scenario of smart logistics warehouse**
+
+### I.1 Goods sorting
+
+In the SLW, the sorting of goods is accomplished by industrial cameras that identify the label, size, and appearance of the goods. Fast identification of labels can collect and classify transportation information such as barcodes and QR codes on goods. Identifying the size of goods can provide a volume basis for subsequent shelf placement and vehicle loading. Identifying the appearance of the goods can determine whether there are abnormalities such as damage, dirt, and scratches on the surface of the goods. At the same time, the abnormal state of the sorting process of the goods on the conveyor belt can be identified, such as the accumulation, blockage and falling of goods.
+
+### I.2 Goods palletizing and de-palletizing
+
+In the SLW, MVS (e.g., three-dimensional (3D) cameras) obtain goods depth information and high-definition two-dimensional (2D) images, generate goods appearance point cloud data, complete goods image positioning and segmentation through visual algorithms, and control mechanical arms to grasp, palletize and de-palletize goods. At the same time, according to the preset accumulation type, MVS identifies and verifies the placement method, and identify the appearance defects of the goods.
+
+### I.3 Shelf inventory
+
+In the SLW, the inventory of goods is completed by industrial cameras that identify the vacancy and occupancy status of the shelf, can count the vacancy rate of the shelf, and provide data support for the goods to be placed on the shelf. MVS identifies the volume of the shelf storage space, which can match the size of the goods to place goods and improve the utilization rate of the shelf. MVS identifies the number of goods on the shelf and carry out an inventory of goods. MVS identifies the
+
+surface of the goods on the shelf, such as damage, dirt and other information, to facilitate the judgment of whether there is an abnormality inside the goods. MVS identifies the goods that fall from the shelf or that are at risk of falling to ensure the safety of goods and people.
+
+### **I.4 Goods handling**
+
+In the SLW, the handling of goods is completed by AMR. The MVS of the AMR identifies the label information on the surface of the goods and matches the position of the goods on the shelf or transportation vehicle. The AMR machine vision service identifies the surrounding environment and obstacle information, and plans transportation routes and logistics storage maps. AMR identifies ground material information and judges the arrival area.
+
+### **I.5 Logistics warehouse environment monitoring**
+
+In the SLW, MVS monitors the potential safety hazards of the logistics warehouse environment, including smoke, fire, or water leakage. The MVS monitors the AMR's handling activities, including AMR transportation traffic jams, AMR transportation goods falling, etc. The MVS monitors the accumulation of goods in a specific area, and at the same time monitors the violent sorting and handling behaviour of workers. The MVS collects information on goods transportation vehicles, including vehicle body colour, licence plate, vehicle brand, etc., and collects in-vehicle loading rates to identify empty, half, and full situations.
+
+## Bibliography
+
+- [b-ITU-T F.748.16] Recommendation ITU-T F.748.16 (2022), *Requirements for applications and services in smart manufacturing based on machine vision.*
+- [b-ISO/IEC 2382] ISO/IEC 2382 (2015), *Information technology – Vocabulary.*
+- [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.*
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.747.13-202309-I_PDF-E/raw.md b/marked/F/T-REC-F.747.13-202309-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..107bf565c111fe4cce65b74b191b8320510c7e7d
--- /dev/null
+++ b/marked/F/T-REC-F.747.13-202309-I_PDF-E/raw.md
@@ -0,0 +1,697 @@
+
+
+# Recommendation**ITU-T F.747.13 (09/2023)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+---
+
+# **Requirements and reference framework of cloud-edge collaboration in industrial machine vision 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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.747.13
+
+# Requirements and reference framework of cloud-edge collaboration in industrial machine vision systems
+
+## Summary
+
+Recommendation ITU-T F.747.13 specifies requirements and reference framework of cloud-edge collaboration in industrial machine vision systems and provides use cases. The cloud-edge collaboration is a process (or method) that coordinates cloud computing and edge computing, dynamically allocates required computing, algorithm models, data, or other resources and jointly completes the same tasks (or objectives) agreed in advance. In industrial machine vision systems, cloud-edge collaboration includes resource collaboration (computing, network and storage), service collaboration (data, intelligence and task) and application collaboration (capability and management).
+
+This Recommendation is intended to guide the design and development of industrial machine vision systems.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.747.13 | 2023-09-13 | 16          | 11.1002/1000/15620 |
+
+## Keywords
+
+Cloud-edge collaboration, industrial machine vision systems, reference framework, requirements, use cases.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                                         | 3    |
+| 6 Overview of cloud-edge collaboration in industrial machine vision systems .....           | 3    |
+| 7 Requirements of cloud-edge collaboration in industrial machine vision systems.....        | 6    |
+| 7.1 Requirements of resource collaboration .....                                            | 6    |
+| 7.2 Requirements of service collaboration .....                                             | 7    |
+| 7.3 Requirements of application collaboration.....                                          | 8    |
+| 8 Reference framework of cloud-edge collaboration in industrial machine vision systems..... | 9    |
+| 8.1 Requirements of the cloud layer.....                                                    | 9    |
+| 8.2 Requirements of the edge layer .....                                                    | 11   |
+| Appendix I – Use cases of cloud-edge collaboration in industrial machine vision systems ... | 13   |
+| I.1 Quality inspection.....                                                                 | 13   |
+| I.2 Logistics sorting .....                                                                 | 13   |
+| I.3 Industrial manufacturing robots .....                                                   | 14   |
+| Bibliography.....                                                                           | 15   |
+
+
+
+# Recommendation ITU-T F.747.13
+
+## Requirements and reference framework of cloud-edge collaboration in industrial machine vision systems
+
+# 1 Scope
+
+This Recommendation specifies the requirements and reference framework of cloud-edge collaboration in industrial machine vision systems.
+
+The scope of this Recommendation includes:
+
+- Overview;
+- Requirements; and
+- Reference framework.
+
+Use cases of cloud-edge collaboration in industrial machine vision systems are provided 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.743.22] Recommendation ITU-T F.743.22 (2022), *Requirements and architecture of an algorithm-training system for intelligent video surveillance*.
+
+[ITU-T F.747.12] Recommendation ITU-T F.747.12 (2022), *Requirements for artificial intelligence based machine vision system in smart logistics warehouse*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 algorithm training** [ITU-T F.743.22]: A technology that learns the experience or the environment represented by the input data and upgrades the algorithm.
+
+**3.1.2 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.3 collaboration** [b-ISO 13374-2]: A relation between two objects in a collaboration diagram, indicating that messages can pass back and forth between the objects.
+
+**3.1.4 edge computing** [b-ITU-T Y.3073]: This refers to a strategy to deploy the processing capability at the network edge where end terminals are connected, and to perform the processing of data which is derived from and fed to the end terminals.
+
+**3.1.5 federated machine learning** [b-IEEE 3652.1]: Federated machine learning is a framework or system that enables multiple participants to collaboratively build and use machine learning models without disclosing the raw and private data owned by the participants while achieving good performance.
+
+**3.1.6 homomorphic encryption** [b-ISO/IEC 20009-4]: Symmetric or asymmetric encryption that allows third parties to perform operations on plaintext data while keeping them in encrypted form.
+
+**3.1.7 incremental learning** [b-ISO/IEC 2382]: Multistage adaptive learning in which knowledge learned at one stage is transformed in order to accommodate new knowledge provided at subsequent stages.
+
+**3.1.8 inference** [b-ISO/IEC 2382]: Reasoning by which conclusions are derived from known premises.
+
+**3.1.9 machine vision** [b-ITU-T F.748.16]: Signal processing to acquire, process and interpret an image or video to support visual analysis for applications, such as automatic inspection, process control and guidance.
+
+**3.1.10 orchestration** [b-ISO/IEC TR 30102]: Composition for which there is one particular element used by the composition that oversees and directs the other elements.
+
+NOTE – The element that directs an orchestration by definition is different than the orchestration (composition instance) itself.
+
+**3.1.11 optical character recognition (OCR)** [b-ISO/IEC 22989]: Conversion of images of typed, printed, or handwritten text into machine-encoded text.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 cloud-edge collaboration:** A process (or method) that coordinates cloud computing and edge computing, dynamically allocates required computing, algorithm models, data, or other resources, and jointly completes the same tasks (or objectives) agreed in advance.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                |
+|------|--------------------------------|
+| 3D   | Three-Dimension                |
+| AGV  | Automated Guided Vehicle       |
+| AI   | Artificial Intelligence        |
+| AMR  | Automated Mobile Robot         |
+| CPU  | Central Processing Unit        |
+| ERP  | Enterprise Resource Planning   |
+| FPGA | Field Programmable Gate Array  |
+| GPU  | Graphics Processing Unit       |
+| MES  | Manufacturing Execution System |
+| NPU  | Neural-network Processing Unit |
+| OCR  | Optical Character Recognition  |
+| OCV  | Optical Character Verification |
+
+|      |                              |
+|------|------------------------------|
+| ONNX | Open Neural Network Exchange |
+| QMS  | Quality Management System    |
+| WMS  | Warehouse Management System  |
+
+# 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 needs 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 cloud-edge collaboration in industrial machine vision systems
+
+With the continuous improvement of industrial automation and intelligence requirements, industrial machine vision technology is widely used in intelligent manufacturing, smart logistics warehousing, smart energy and other scenarios. The data-intensive applications and computing intensive applications are continuously increasing, and the powerful computing and network resources of cloud computing collaborative with the high-speed response capability of edge computing can greatly improve the application level of machine vision systems in the industrial field.
+
+Cloud-edge collaboration is a process (or method) that coordinates cloud computing and edge computing, dynamically allocates required computing, algorithm models, data, or other resources, and jointly completes the same tasks (or objectives) agreed in advance.
+
+Cloud computing can achieve global, non-real-time, long-term big data processing and analysis, and can play an important role in the fields of long-term maintenance, service decision support, etc. Edge computing can achieve local, real-time and short-term data processing and analysis, and can better support real-time intelligent decision-making and execution of local services.
+
+The application of cloud-edge collaboration in industrial machine vision systems can optimize the allocation and utilization of resources, achieve effective collaboration of data and computing processes, and strengthen the perception capability of industrial machine vision systems. Real-time data processing can relieve bandwidth pressure, and complete the data perception, analysis, decision-making and evaluation in the whole cycle.
+
+In this Recommendation, the cloud is equivalent to cloud computing, and the edge is equivalent to edge computing.
+
+Typical scenarios of cloud-edge collaboration in industrial machine vision systems (see Appendix I for use cases) include:
+
+## Scenario A: High real-time performance requirements
+
+In the industrial production environment, certain processes require high real-time performance. For example, the defect detection processes use the industrial camera to collect the image of the product surface, analyses whether the product has defects in real-time, and classifies the defective products through the mechanical arm. This requires real-time inference on the edge which closes to the
+
+pipeline. The cloud completes the algorithm training and deploys the algorithm models to the edge. Through cloud-edge collaboration algorithm models achieve efficient and fast iterations that continuously improve the accuracy of defect identification.
+
+## Scenario B: High data security requirements
+
+For enterprises and factories with high requirements for data security, the raw data collected by industrial devices cannot be uploaded to the cloud. The edge deployed in the trusted domain uses technologies such as federated machine learning and homomorphic encryption to upload the processed data (such as intermediate computing results and desensitization data) to the cloud to complete the training, analysis and applications.
+
+Figure 1 shows the conceptual diagram of a cloud-edge collaboration.
+
+![Conceptual diagram of a cloud-edge collaboration showing three levels of collaboration: Application, Service, and Resource between Edge and Cloud layers.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg)
+
+The diagram illustrates the conceptual architecture of cloud-edge collaboration. It consists of two main vertical columns: **Edge** on the left and **Cloud** on the right. Each column is divided into three horizontal layers, each containing specific functional blocks.
+
+- Edge Column:**
+  - Top Layer:** Management, Capability
+  - Middle Layer:** Task, Intelligence, Data
+  - Bottom Layer:** Computing, Network, Storage
+- Cloud Column:**
+  - Top Layer:** Management, Capability
+  - Middle Layer:** Task, Intelligence, Data
+  - Bottom Layer:** Computing, Network, Storage
+
+Three horizontal double-headed arrows connect the corresponding layers between Edge and Cloud, representing different types of collaboration:
+
+- Application collaboration:** Connects the top layers (Management and Capability) of both Edge and Cloud.
+- Service collaboration:** Connects the middle layers (Task, Intelligence, and Data) of both Edge and Cloud.
+- Resource collaboration:** Connects the bottom layers (Computing, Network, and Storage) of both Edge and Cloud.
+
+F.747.13(23)
+
+Conceptual diagram of a cloud-edge collaboration showing three levels of collaboration: Application, Service, and Resource between Edge and Cloud layers.
+
+**Figure 1 – Conceptual diagram of a cloud-edge collaboration**
+
+Cloud-edge collaboration mainly includes resource collaboration, service collaboration and application collaboration.
+
+Resource collaboration is the collaboration of computing, network and storage resources between the cloud and edge. Through the unified management of resources, resource collaboration enriches the types of resource entities, expands the area of resource management, and improves the decision-making capability of resource scheduling. The orchestration and scheduling of resources extend from the resource-rich cloud to the resource-constrained edge, providing an overall view of the resources, so that edge-to-cloud and edge-to-edge resources can be scheduled and collaborated on demand, to optimize the resource utilization from a global perspective.
+
+Service collaboration is the collaboration of tasks, intelligence and data between the cloud and the edge. Based on the resource collaboration and scheduling capabilities between cloud and edge, the service collaboration establishes a multi-layer collaboration of cloud and edge, decomposes large-scale and complex services into tasks, and reasonably plans the storage and transmission of data between cloud and edge. Combined with technologies such as federated machine learning and incremental learning, the orchestrated tasks are allocated to the cloud and edge for joint training and joint inference on-demand, which can realize the mutual extension and collaborative operation of intelligence services between cloud and edge and improve the efficiency and performance.
+
+Application collaboration is the collaboration of management and capability between cloud and edge. Based on the resource and service collaboration between cloud and edge, the application
+
+collaboration realizes the unified registration and access of edge applications, consistently distributes the deployment and centralized full-lifecycle management, including push, installation, update, and the uninstall of applications. Based on the capability hierarchy of cloud and edge, the allocation strategies are designed according to the priority and dependencies of service attributes, while completing the high availability guarantee and live migration of applications to meet the requirements of users.
+
+Figure 2 shows the information interaction model between the cloud and the edge.
+
+![Figure 2 – Information interaction model between cloud and edge. The diagram illustrates the flow of data, results, and algorithm models between Cloud and Edge components. Cloud components include Applications, Algorithm training, Algorithm warehouse, and Algorithm inference. Edge components include Applications, Algorithm warehouse, Algorithm inference, and Data acquisition. Arrows indicate the direction of interaction, labeled (a) through (m).](e9314c83043183351ed74908e9bf2f90_img.jpg)
+
+The diagram shows the information interaction model between cloud and edge. It is divided into two main sections: Cloud and Edge.
+
+- Cloud Section:**
+  - Applications:** A large grey box at the top.
+  - Algorithm training:** A grey box below Applications.
+  - Algorithm warehouse:** A grey box to the right of Algorithm training.
+  - Algorithm inference:** A grey box to the right of Algorithm warehouse.
+- Edge Section:**
+  - Applications:** A grey box on the right side.
+  - Algorithm warehouse:** A grey box on the left side, above Algorithm inference.
+  - Algorithm inference:** A grey box in the middle, below Algorithm warehouse.
+  - Data acquisition:** A grey box at the bottom right.
+  - Algorithm training:** A grey box at the bottom left.
+
+**Interactions (Arrows):**
+
+- (a) Data acquisition → Algorithm inference
+- (b) Data acquisition → Algorithm training
+- (c) Algorithm training → Algorithm warehouse
+- (d) Algorithm inference → Applications
+- (e) Algorithm inference → Applications
+- (f) Algorithm inference → Applications
+- (g) Algorithm inference → Applications
+- (h) Algorithm training → Algorithm warehouse
+- (i) Algorithm warehouse → Algorithm inference
+- (j) Algorithm warehouse → Algorithm warehouse
+- (k) Algorithm warehouse → Algorithm inference
+- (l) Algorithm inference → Algorithm training
+- (m) Algorithm training → Algorithm inference
+
+**Legend:**
+
+- Data (black arrow)
+- Result (red arrow)
+- Algorithm model (blue arrow)
+
+F.747.13(23)
+
+Figure 2 – Information interaction model between cloud and edge. The diagram illustrates the flow of data, results, and algorithm models between Cloud and Edge components. Cloud components include Applications, Algorithm training, Algorithm warehouse, and Algorithm inference. Edge components include Applications, Algorithm warehouse, Algorithm inference, and Data acquisition. Arrows indicate the direction of interaction, labeled (a) through (m).
+
+**Figure 2 – Information interaction model between cloud and edge**
+
+The information interaction between cloud and edge mainly includes the data, results and the algorithm models. In the information interaction model, edge includes data collection/acquisition, algorithm inference, algorithm training, algorithm warehouse, edge application, etc.; cloud includes algorithm training, algorithm warehouse, algorithm inference, cloud application, etc.
+
+Typical information interaction process is as follows:
+
+### **a. Cloud training and edge inference**
+
+- The edge uploads the collected data to the algorithm training unit on cloud for algorithm training unit through (c);
+- The algorithm training unit on cloud performs algorithm training and sends the trained algorithm models to the algorithm warehouse unit on cloud through (h);
+- The algorithm warehouse unit on cloud sends the algorithm models to the algorithm warehouse unit on edge based on requirements through (j);
+- The algorithm warehouse unit on edge deploys the algorithm models to the algorithm inference unit on edge through (k) and starts the inference tasks;
+- The data acquisition unit on edge sends the original data to the algorithm inference unit on edge for inference through (a);
+
+- The algorithm inference unit on edge sends the inference results to the edge application through (e) or uploads the inference results to the cloud application through (g).
+- b. Cloud and edge joint training based on federated machine learning**
+- The edge sends the collected data to the algorithm training unit on edge through (b);
+  - The algorithm training unit on edge performs algorithm training and uploads the intermediate results generated during the training process to the algorithm training unit on cloud through (m);
+  - The algorithm training unit on cloud uses the federated learning framework to aggregate the intermediate results generated by multiple edge to a global algorithm model, and then sends the global algorithm model to the algorithm warehouse unit on cloud through (h).
+- c. Cloud and edge joint training based on incremental learning**
+- The edge uploads the collected data to the algorithm training unit on cloud for algorithm training unit through (c);
+  - The algorithm training unit on cloud performs algorithm training and sends the trained algorithm models to the algorithm warehouse unit on cloud through (h);
+  - The algorithm warehouse unit on cloud sends the algorithm models to the algorithm warehouse unit on edge based on requirements through (j);
+  - The algorithm warehouse unit on edge sends the algorithm models to the algorithm training unit on edge through (i);
+  - The edge sends the collected data to the algorithm training unit on edge through (b);
+  - The algorithm training unit on edge sends the incremental learning algorithm models to the algorithm warehouse unit on edge through (i).
+- d. Cloud and edge joint inference**
+- The algorithm warehouse unit on edge deploys the algorithm models to the algorithm inference unit on edge through (k) and starts the inference tasks;
+  - The data acquisition unit on edge sends the original data to the algorithm inference unit on edge for inference through (a);
+  - The algorithm inference unit on edge uploads the inference results to the cloud application through (g).
+  - The algorithm warehouse unit on the cloud deploys the algorithm models to the algorithm inference unit on the cloud through (i) and starts the inference tasks;
+  - The data acquisition unit on edge uploads the original data to the algorithm inference unit on the cloud for inference through (d);
+  - The algorithm inference unit on the cloud sends the inference results to the cloud application through (f);
+  - The edge and cloud side inference results are aggregated into cloud applications to achieve specific service requirements.
+
+# **7 Requirements of cloud-edge collaboration in industrial machine vision systems**
+
+In this Recommendation, requirements specific to the cloud-edge collaboration in industrial machine vision systems (hereafter "the system") are identified.
+
+## **7.1 Requirements of resource collaboration**
+
+- RRC1: The system is recommended to support the application, reservation and release of resources (computing, storage and network);
+
+- RRC2: The system is recommended to support resources self-discovery, self-maintenance and self-management;
+- RRC3: The system is recommended to support resources reuse mechanisms, including reuse by time and reuse by domain;
+- RRC4: The system is recommended to support resource scheduling between cloud and edge on-demand;
+- RRC5: The system is recommended to support the computing capability model generation, computing resource normalization of heterogeneous computing devices, and provide attribute and status information for scheduling;
+- RRC6: The system is recommended to support resource information modelling and overall view generation of resources scheduling between cloud and edge;
+- RRC7: The system is recommended to support the heterogeneous computing resources virtualization and pooling, computing resources including central processing unit (CPU), graphics processing unit (GPU), neural-network processing unit (NPU) and field programmable gate array (FPGA);
+- RRC8: The system is recommended to support the resource status synchronization between cloud and edge, including the idle and occupied status of computing resources, storage resources and bandwidth resources;
+- RRC9: The system is recommended to support resource fault isolation, performance isolation and security isolation.
+
+## **7.2 Requirements of service collaboration**
+
+### **7.2.1 Requirements of data collaboration**
+
+- RDC1: The system is recommended to support data aggregation, storage, retrieval, invocation and association;
+- RDC2: The system is recommended to support data synchronization between cloud and edge, including structured data, unstructured data and semi-structured data;
+- RDC3: The system is recommended to support unified processing and the conversion of different data formats;
+- RDC4: The system is recommended to support data conversion under different spatiotemporal coordinate systems;
+- RDC5: The system is recommended to support sample data aggregation between cloud and edge;
+- RDC6: The system is recommended to support sample data de-duplication between cloud and edge;
+
+NOTE – The sample data is used for training.
+
+- RDC7: The system is recommended to support redundant, multiple copies, or erasure code data storage;
+- RDC8: The system is recommended to support data compression and encrypted transmission.
+
+### **7.2.2 Requirements of intelligence collaboration**
+
+- RIC1: The system is recommended to support operating machine learning frameworks on cloud and edge, such as TensorFlow and PyTorch;
+- RIC2: The system is recommended to support the algorithm models updating and maintenance on cloud and edge;
+
+- RIC3: The system is recommended to support cloud training with edge inference mode;
+- RIC4: The system is recommended to support the cloud and edge joint inference mode;
+- RIC5: The system is recommended to support unified metadata description of inference results between cloud and edge;
+- RIC6: The system is recommended to support the cloud and edge joint training mode based on federated machine learning;
+- RIC7: The system is recommended to support cloud and edge joint training mode based on incremental learning;
+- RIC8: The system is recommended to support algorithm model lightweight to adapt the computing capabilities on cloud and edge;
+- RIC9: The system is recommended to support the general representation of algorithm models, so that the trained algorithm models can be deployed and operated without conversion between cloud and edge.
+
+### **7.2.3 Requirements of task collaboration**
+
+- RTC1: The system is recommended to support unified tasks scheduling and tasks distribution for execution between cloud and edge;
+- RTC2: The system is recommended to support the tasks migration to the cloud or edge for execution when edge devices have insufficient computing resources or when abnormal conditions occur;
+- RTC3: The system is recommended to support priority definition and resource pre-emption of tasks;
+- RTC4: The system is recommended to support the generation of task scheduling strategies based on task timing, network bandwidth, computing resources and data proximity;
+- RTC5: The system is recommended to support dynamic adjustment, flexible configuration and combined use of task scheduling strategies;
+- RTC6: The system is recommended to support the execution isolation of task instances, to ensure user data security and hardware device safety.
+
+## **7.3 Requirements of application collaboration**
+
+### **7.3.1 Requirements of capability collaboration**
+
+- RCC1: The system is recommended to support unified metadata description of capabilities on cloud and edge;
+- RCC2: The system is recommended to support capabilities convergence and synchronization between cloud and edge;
+- RCC3: The system is recommended to support capabilities, including analysis, enhancement, and retrieval of video and image data;
+- RCC4: The system is recommended to support capabilities, including acquisition, transmission, storage, display and control of multimedia data;
+- RCC5: The system is recommended to support overall view generation of capabilities on cloud and edge.
+
+### **7.3.2 Requirements of management collaboration**
+
+- RMC1: The system is recommended to support the splitting of services into multiple collaborative task execution units for scheduling and operation;
+- RMC1: The system is recommended to support planning collaboration strategies based on service attributes (priorities, dependencies) and cloud and edge capabilities.
+
+# 8 Reference framework of cloud-edge collaboration in industrial machine vision systems
+
+Figure 3 shows the reference framework of cloud-edge collaboration in industrial machine vision systems.
+
+![Figure 3: Reference framework of cloud-edge collaboration in industrial machine vision systems. The diagram shows a hierarchical structure. On the left, a large box labeled 'Industrial machine vision systems' contains three layers: 'Cloud layer', 'Edge layer', and 'Production management systems'. The 'Cloud layer' is divided into 'Application components' (Detection, Identification, Localization, Measurement, ...), 'Intelligent components' (Algorithm scheduling, Algorithm inference, Algorithm training, Algorithm warehouse), and 'Fundamental components' (Visual data management, Task orchestration, Collaboration management, Capability management, Device management, Resource management). The 'Edge layer' is divided into 'Algorithm warehouse', 'Visual data processing', 'Task execution', 'Algorithm inference', 'Visual data acquisition', 'Visual data storage', 'Algorithm training', 'Device management', and 'Resource management'. The 'Production management systems' are shown on the right, connected to the 'Industrial machine vision systems' box, and include MES, WMS, QMS, ERP, and ... (ellipsis).](724c7777b608e53be38b12b6fb3c43bc_img.jpg)
+
+**Industrial machine vision systems**
+
+**Cloud layer**
+
+**Application components**
+
+Detection    Identification    Localization    Measurement    ...
+
+**Intelligent components**
+
+Algorithm scheduling    Algorithm inference  
+Algorithm training    Algorithm warehouse
+
+**Fundamental components**
+
+Visual data management    Task orchestration  
+Collaboration management    Capability management  
+Device management    Resource management
+
+**Edge layer**
+
+Algorithm warehouse    Visual data processing    Task execution  
+Algorithm inference    Visual data acquisition    Visual data storage  
+Algorithm training    Device management    Resource management
+
+**Production management systems**
+
+MES  
+WMS  
+QMS  
+ERP  
+...
+
+F.747.13(23)
+
+Figure 3: Reference framework of cloud-edge collaboration in industrial machine vision systems. The diagram shows a hierarchical structure. On the left, a large box labeled 'Industrial machine vision systems' contains three layers: 'Cloud layer', 'Edge layer', and 'Production management systems'. The 'Cloud layer' is divided into 'Application components' (Detection, Identification, Localization, Measurement, ...), 'Intelligent components' (Algorithm scheduling, Algorithm inference, Algorithm training, Algorithm warehouse), and 'Fundamental components' (Visual data management, Task orchestration, Collaboration management, Capability management, Device management, Resource management). The 'Edge layer' is divided into 'Algorithm warehouse', 'Visual data processing', 'Task execution', 'Algorithm inference', 'Visual data acquisition', 'Visual data storage', 'Algorithm training', 'Device management', and 'Resource management'. The 'Production management systems' are shown on the right, connected to the 'Industrial machine vision systems' box, and include MES, WMS, QMS, ERP, and ... (ellipsis).
+
+**Figure 3 – Reference framework of cloud-edge collaboration in industrial machine vision systems**
+
+The reference framework of cloud-edge collaboration in industrial machine vision systems consists of the cloud layer and edge layer. At the same time, industrial machine vision systems can interact with external production management systems, such as manufacturing execution systems (MES), warehouse management systems (WMS), quality management systems (QMS), enterprise resource planning (ERP), etc.
+
+The cloud layer includes application components, intelligent components and fundamental components. Applications include detection, identification, localization, measurement, etc. Intelligent components include algorithm training, algorithm warehouse, algorithm scheduling and algorithm inference. The fundamental components include visual data management, task orchestration, collaboration management, capability management, device management and resource management.
+
+The edge layer includes algorithm warehouse, algorithm inference, algorithm training, resource management, device management, visual data collection/acquisition, visual data storage, visual data processing and task execution.
+
+The requirements for cloud and edge layers are as follows:
+
+## 8.1 Requirements of the cloud layer
+
+### 8.1.1 Requirements of application components
+
+The requirements of application components on the cloud include:
+
+- RA1: It is recommended to support machine vision applications for industrial fields, such as detection, identification, localization, measurement, etc.;
+
+- RA2: It is recommended to support application management, including push, installation, update and uninstall;
+- RA3: It is recommended to support application disassembly as a service, deploying to the edge in the form of containers;
+- RA4: It is recommended to support multi-tenant application isolation.
+
+### 8.1.2 Requirements of intelligent components
+
+The requirements of intelligent components on the cloud include:
+
+- RICO1: It is recommended to support sample data management and algorithm training [ITU-T F.743.22];
+- RICO2: It is recommended to support multiple algorithm model management in the cloud algorithm warehouse, including addition, deletion and deployment;
+- RICO3: It is recommended to support the management of the edge algorithm warehouse, including querying, deploying and uploading;
+- RICO4: It is recommended to support algorithm inference tasks operation, including start, pause and stop;
+- RICO5: It is recommended to support unified scheduling of algorithm tasks between cloud and edge;
+- RICO6: It is recommended to support the algorithm model in a general format such as open neural network exchange (ONNX) [b-Onnx] format;
+- RICO7: It is recommended to support algorithm model clipping, compression and optimization.
+
+### 8.1.3 Requirements of fundamental components
+
+The requirements of fundamental components on the cloud include:
+
+- RFC1: It is recommended to support the management of the edge including access, control, operation and maintenance;
+- RFC2: It is recommended to support physical resource information aggregation and usage monitoring on cloud and edge;
+- RFC3: It is recommended to support data management by cloud storage;
+- RFC4: It is recommended to support unified management of visual data, including storage, backup and migration;
+- RFC5: It is recommended to support the management of collaboration strategies, including adding, deleting, modifying and querying;
+- RFC6: It is recommended to support the management of task scheduling strategies, including adding, deleting, modifying and checking;
+- RFC7: It is recommended to support the execution of task scheduling strategies, including creating, starting, stopping and deleting tasks on cloud and edge;
+- RFC8: It is recommended to support task operation status querying and resource consumption monitoring;
+- RFC9: It is recommended to support cloud and edge capability aggregation and management, and provide an overall view of the entire domains;
+- RFC10: It is recommended to support computing resource virtualization on the cloud, including CPU, GPU, or other artificial intelligence (AI) accelerating processors;
+- RFC11: It is recommended to support a unified container orchestration framework on cloud and edge, and applications with unified distribution and unified governance.
+
+## **8.2 Requirements of the edge layer**
+
+### **8.2.1 General requirements**
+
+The general requirements on edge include:
+
+- RGR1: It is recommended to support registering to the cloud, reporting edge capabilities to the cloud, and management by cloud;
+- RGR2: It is recommended to support signalling interaction and data sharing with multiple edge devices;
+- RGR3: It is recommended to support offline operation strategies, including autonomous operation and task migration.
+
+### **8.2.2 Requirements of resource management**
+
+The requirements of resource management on edge include:
+
+- RRM1: It is recommended to support edge resource information and usage monitoring;
+- RRM2: It is recommended to support reporting resource information and usage status to the cloud.
+
+### **8.2.3 Requirements of device management**
+
+The requirements of device management on edge include:
+
+- RDM1: It is recommended to support multiple types of edge devices access such as industrial cameras, automated guided vehicles (AGV), automated mobile robots (AMR), mechanical arms, surveillance cameras, code readers, three-dimension (3D) cameras, laser radars, etc.;
+- RDM2: It is recommended to support edge devices configuration, including codec configuration, network configuration and storage configuration;
+- RDM3: It is recommended to support edge devices control, including restarting, upgrading, suspending operation and resuming operations;
+- RDM4: It is recommended to support edge devices event subscription and notification;
+- RDM5: It is recommended to support edge devices operation and maintenance, including status information collection, status abnormality alarm;
+- RDM6: It is recommended to support edge devices detection, including network link detection, video and image quality diagnosis;
+- RDM7: It is recommended to satisfy the device requirements defined in [ITU-T F.747.12].
+
+### **8.2.4 Requirements of algorithm warehouse**
+
+The requirements of algorithm warehouse on edge include:
+
+- RAW1: It is recommended to support multiple algorithm model management, including addition, deletion and deployment;
+- RAW2: It is recommended to support algorithm model deployment to edge devices on-demand.
+
+### **8.2.5 Requirements of algorithm inference**
+
+The requirements of algorithm inference on edge include:
+
+- RAI1: It is recommended to support algorithm inference and cache the inference results locally for task use;
+- RAI2: It is recommended to support reporting inference results to cloud applications;
+
+- RAI3: It is recommended to support common machine vision algorithm models including but not limited to target localization, target measurement, target identification, etc.;
+- RAI4: It is recommended to support the decomposition and allocation of algorithm inference tasks to multiple edge devices.
+
+NOTE – Edge devices jointly complete partial inference tasks to reduce inference pressure.
+
+### **8.2.6 Requirements of algorithm training**
+
+The requirements of algorithm training on edge include:
+
+- RAT1: It is recommended to support algorithm training and storage of the trained algorithm model into the algorithm warehouse;
+- RAT2: It is recommended to support federated machine learning with multi-edge;
+- RAT3: It is recommended to support incremental learning.
+
+### **8.2.7 Requirements of visual data collection**
+
+The requirements of visual data collection on edge include:
+
+- RVDC1: It is recommended to support multiple types of industrial data collection, including video, images and point clouds;
+- RVDC2: It is recommended to support multiple resolutions, including 1 million, 3 million, 5 million, 10 million and 12 million pixels;
+- RVDC3: It is recommended to support multiple pixel depths, including 8 bits, 10 bits, 12 bits and 14 bits;
+- RVDC4: It is recommended to support multiple frame rates, including 5, 10, 50, 100 and 200 frames per second (fps).
+
+### **8.2.8 Requirements of visual data storage**
+
+The requirement of visual data storage on edge includes:
+
+- RVDS1: It is recommended to support expandable storage capacity;
+- RVDS2: It is recommended to support data redundancy protection and backup;
+- RVDS3: It is recommended to support universal data storage formats, such as block storage, file storage and object storage.
+
+### **8.2.9 Requirements of visual data processing**
+
+The requirements of visual data processing on edge include:
+
+- RVDP1: It is recommended to support data pre-processing, including image zooming, image filling, image rotation and image enhancement;
+- RVDP2: It is recommended to support data analysis, including data filtering, data classification and data retrieval;
+- RVDP3: It is recommended to support multi-modal data fusion of multiple edge devices.
+
+#### **8.2.10 Requirements of task execution**
+
+The requirements of task execution on edge include:
+
+- RTE1: It is recommended to support the execution of tasks, such as target localization, target measurement and target identification;
+- RTE2: It is recommended to support reporting task execution status to the cloud;
+- RTE3: It is recommended to support task execution in the form of containers on edge devices;
+- RTE4: It is recommended to support multi-tenant task isolation.
+
+## Appendix I
+
+### Use cases of cloud-edge collaboration in industrial machine vision systems
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Figure I.1 shows the service scenario of cloud-edge collaboration in industrial machine vision systems.
+
+![Diagram illustrating the service scenario of cloud-edge collaboration in industrial machine vision systems. The diagram shows an Industrial environment (represented by a factory floor with conveyor belts) connected to an Industrial machine vision system (containing Cloud and Edge components), which in turn connects to a Production management system. Data flows from the Industrial environment to the Edge, then to the Cloud, and finally to the Production management system. Results flow from the Cloud to the Production management system. Algorithm models flow from the Cloud to the Edge. Control signals flow from the Production management system to the Edge, and from the Edge to the Industrial environment.](10781f43062bf3e9601a1e086710556c_img.jpg)
+
+The diagram illustrates the service scenario of cloud-edge collaboration in industrial machine vision systems. It is divided into three main components: **Industrial environment** (left), **Industrial machine vision system** (center), and **Production management system** (right). The **Industrial machine vision system** contains two sub-components: **Cloud** and **Edge**. The **Industrial environment** sends **Data** (black arrow) to the **Edge**. The **Edge** sends **Result** (red arrow) to the **Cloud**. The **Cloud** sends **Algorithm model** (blue arrow) to the **Edge**. The **Cloud** sends **Result** (red arrow) to the **Production management system**. The **Edge** sends **Control** (green arrow) to the **Industrial environment**. The **Production management system** sends **Control** (green arrow) to the **Edge**. A legend at the bottom indicates: **Data** (black arrow), **Result** (red arrow), **Algorithm model** (blue arrow), and **Control** (green arrow). The diagram is labeled F.747.13(23).
+
+Diagram illustrating the service scenario of cloud-edge collaboration in industrial machine vision systems. The diagram shows an Industrial environment (represented by a factory floor with conveyor belts) connected to an Industrial machine vision system (containing Cloud and Edge components), which in turn connects to a Production management system. Data flows from the Industrial environment to the Edge, then to the Cloud, and finally to the Production management system. Results flow from the Cloud to the Production management system. Algorithm models flow from the Cloud to the Edge. Control signals flow from the Production management system to the Edge, and from the Edge to the Industrial environment.
+
+**Figure I.1 – Service scenario of cloud-edge collaboration in industrial machine vision systems**
+
+The data collected by devices in an industrial production environment can be analysed and processed in real-time at the edge, and the results can be sent to the production management system for decision-making and control. At the same time, the processed data can be uploaded to the cloud to complete the algorithm training, and the cloud deploys the algorithm model to the edge and the industrial devices. The cloud can conduct big data analysis based on data, and the production management system can conduct decision-making and control devices in the industrial production environment based on the results produced by the cloud.
+
+### I.1 Quality inspection
+
+In automated assembly lines, a certain number of defective products are produced in various stages of continuous mass production. To improve the yield rate of manufacturing enterprises, industrial machine vision technology plays a significant role in defective product elimination, quality control and cost control. Industrial cameras and X-ray machines can be used to collect internal and external defects of the products. The collected information on the edge can be identified and analysed at a high speed to determine the defective products. The defect recognition algorithm models are continuously trained and upgraded on the cloud which improves the recognition accuracy. It can be applied to the pharmaceutical industry, electronic component processing industry, precision equipment quality inspection industry, etc.
+
+### I.2 Logistics sorting
+
+[ITU-T F.747.12] defines the general requirements and framework for intelligent logistics warehousing machine vision systems. In the logistics and warehousing industry, massive package information needs to be classified and processed according to the destination or type. This requires industrial cameras' high-speed acquisition of text, barcode, and other information on package surface labels, real-time identification and analysis of label images at the edges, and cloud-completed algorithm training to improve identification accuracy, thereby completing optical character recognition (OCR) and optical character verification (OCV).
+
+## **I.3 Industrial manufacturing robots**
+
+In industrial manufacturing scenarios, the industrial machine vision system can locate the position and direction of the target, compare the target with the specified tolerance, determine the target position, and verify whether the grasping and placement actions are correct. In scenarios such as mechanical arm grabbing and goods handling, real-time path planning at the edge can achieve accurate grabbing and transportation. Big data analysis of data is performed in the cloud, and a grabbing path model and transportation global map are constructed. At the same time, industrial machine vision technology can replace laser, magnetic conductivity and other technologies, greatly reducing costs.
+
+## Bibliography
+
+- [b-ITU-T F.748.16] Recommendation ITU-T F.748.16 (2022), *Requirements for applications and services in smart manufacturing based on machine vision.*
+- [b-ITU-T Y.3073] Recommendation ITU-T Y.3073 (2019), *Framework for service function chaining in information-centric networking.*
+- [b-ITU-T Y.3500] Recommendation ITU-T Y.3500 (2014), *Information technology – Cloud computing – Overview and vocabulary.*
+- [b-IEEE 3652.1] IEEE 3652.1-2020, *IEEE Guide for Architectural Framework and Application of Federated Machine Learning.*  
+<<https://ieeexplore.ieee.org/document/9382202>>
+- [b-ISO 13374-2] ISO 13374-2:2007, *Condition monitoring and diagnostics of machines – Data processing, communication and presentation – Part 2: Data processing.*  
+<<https://www.iso.org/standard/36645.html>>
+- [b-ISO/IEC 20009-4] ISO/IEC 20009-4:2017, *Information technology – Security techniques – Anonymous entity authentication – Part 4: Mechanisms based on weak secrets.*  
+<<https://www.sis.se/produkter/informationsteknik-kontorsutrustning/itsakerhet/isoiec-20009-42017/>>
+- [b-ISO/IEC 22989] ISO/IEC 22989:2022, *Information technology – Artificial intelligence – Artificial intelligence concepts and terminology.*  
+<<https://www.iso.org/standard/74296.html>>
+- [b-ISO/IEC 2382] ISO/IEC 2382:2015, *Information technology – Vocabulary.*  
+<<https://www.iso.org/standard/63598.html>>
+- [b-ISO/IEC TR 30102] ISO/IEC TR 30102:2012, *Information technology – Distributed Application Platforms and Services (DAPS) – General technical principles of Service Oriented Architecture.*  
+<[https://www.iso.org/standard/53222.html#:~:text=ISO%2FIEC%20TR%2030102%3A2012%20describes%20the%20general%20technical%20principles\\_of%20terms%20relevant%20to%20SOA.](https://www.iso.org/standard/53222.html#:~:text=ISO%2FIEC%20TR%2030102%3A2012%20describes%20the%20general%20technical%20principles_of%20terms%20relevant%20to%20SOA.)>
+- [b-Onnx] *Open Neural Network Exchange.*  
+<<https://onnx.ai/>>
+
+
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.747.16-202503-I_PDF-E/raw.md b/marked/F/T-REC-F.747.16-202503-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..52efb0e4850fc259b9f173ae9f8d4834c6ab2f78
--- /dev/null
+++ b/marked/F/T-REC-F.747.16-202503-I_PDF-E/raw.md
@@ -0,0 +1,370 @@
+
+
+# Recommendation **ITU-T F.747.16 (03/2025)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+---
+
+## **Requirements for 3D machine vision-based surface defect detection service of industrial products**
+
+![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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.747.16
+
+# Requirements for 3D machine vision-based surface defect detection service of industrial products
+
+## Summary
+
+Recommendation ITU-T F.747.16 provides the requirements for 3D machine vision-based surface defect detection service of industrial products. Three-dimensional (3D) machine vision can obtain the complete geometric information of the real 3D scene, and the images with depth information can be used to achieve high-precision measurement, detection, positioning, reconstruction, and scene understanding. It can process various types of industrial products that cannot be processed by two-dimensional (2D) machine vision (e.g., highly reflective surfaces and low-contrast surfaces), such as electronic products and printed circuit board (PCB) surface detection, free-form surface optical mirror measurement, and measurement and detection of steel product surfaces or curved surfaces, etc.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.747.16 | 2025-03-16 | 21          | 11.1002/1000/16229 |
+
+## Keywords
+
+3D, defect detection service, machine vision.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <https://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                                           | 1    |
+| 4 Abbreviations and acronyms .....                                                      | 1    |
+| 5 Conventions .....                                                                     | 2    |
+| 6 Overview of 3D machine vision-based surface defect detection service system .....     | 2    |
+| 7 Requirements for 3D machine vision-based surface defect detection service .....       | 3    |
+| 7.1 Requirements for 3D machine vision devices and images.....                          | 3    |
+| 7.2 Requirements for service platform .....                                             | 4    |
+| 7.3 Requirements for application .....                                                  | 5    |
+| 7.4 Others .....                                                                        | 5    |
+| Appendix I – Use cases of 3D machine vision-based surface defect detection service..... | 6    |
+| I.1 Use cases of 3D high-precision detection for planes and curved surfaces.....        | 6    |
+| I.2 Measurement for flatness and geometric tolerance .....                              | 7    |
+| I.3 Detection and grading of steel plates.....                                          | 7    |
+| Bibliography.....                                                                       | 8    |
+
+
+
+# Requirements for 3D machine vision-based surface defect detection service of industrial products
+
+# 1 Scope
+
+This Recommendation presents the requirements for three-dimensional (3D) machine vision-based surface defect detection service of industrial products, especially the requirements for 3D machine vision devices and images, functional and performance requirements of service platform, as well as the presentation and application of detection results.
+
+# 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 algorithm** [b-ISO/IEC 11557]: A set of rules for transforming the logical representation of data.
+
+**3.1.2 machine vision** [b-ITU-T F.748.16]: Signal processing to acquire, process and interpret an image or video to support visual analysis for applications, such as automatic inspection, process control and guidance.
+
+**3.1.3 surface-defect detection** [b-ITU-T F.747.11]: Surface-defect detection refers to the identification of defects on the surface of industrial products, including the location determination, classification and measurement of different types of defects.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 three-dimensional (3D) machine vision**: Signal processing to acquire, process and interpret an image or video with depth information to support real three-dimensional (3D) scene visual analysis for applications, such as measurement, detection, positioning, reconstruction and scene understanding.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+2D Two Dimensional
+
+3C Computer, Communication and Consumer Electronics
+
+|          |                                              |
+|----------|----------------------------------------------|
+| 3D       | Three Dimensional                            |
+| CAD      | Computer Aided Design                        |
+| IMT-2020 | International Mobile Telecommunications-2020 |
+| MEC      | Multi-Access Edge Computing                  |
+| PCB      | Printed Circuit Board                        |
+| ToF      | Time of Flight                               |
+| 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 of 3D machine vision-based surface defect detection service system
+
+Figure 1 shows the layered framework of 3D machine vision-based surface defect detection service system. It includes device layer, network layer, service platform layer and application layer.
+
+![Figure 1 – Layered framework of 3D machine vision-based surface defect detection service system. A block diagram showing four layers: Application layer, Service platform layer, Network layer, and Device layer. Each layer contains specific functional blocks.](5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg)
+
+| Application layer      | Silicon wafer and PCB surface measurement/detection | Free-form surface optical mirror measurement/detection | Steel product surface/curved surface measurement/detection | ....                |
+|------------------------|-----------------------------------------------------|--------------------------------------------------------|------------------------------------------------------------|---------------------|
+| Service platform layer | Service display                                     |                                                        |                                                            |                     |
+|                        | Data process                                        |                                                        | Data analysis                                              |                     |
+|                        | Algorithm/measurement tool library                  |                                                        |                                                            |                     |
+| Network layer          | Cellular network (e.g., IMT-2020)                   |                                                        | Industrial Internet (e.g., optical fibre, WLAN)            |                     |
+| Device layer           | Laser                                               | Imaging devices                                        |                                                            | Auxiliary equipment |
+
+F.747.16(25)
+
+Figure 1 – Layered framework of 3D machine vision-based surface defect detection service system. A block diagram showing four layers: Application layer, Service platform layer, Network layer, and Device layer. Each layer contains specific functional blocks.
+
+**Figure 1 – Layered framework of 3D machine vision-based surface defect detection service system**
+
+The layered functional blocks of the 3D machine vision-based surface defect detection service system are as follows:
+
+- 1) **Device layer.** 3D machine vision device includes lasers, imaging devices and auxiliary equipment, online or offline to obtain 3D images of industrial product surfaces.
+- 2) **Network layer.** This layer includes cellular networks (e.g., international mobile telecommunications-2020 (IMT-2020)) and industrial Internet (e.g., optical fibre and wireless local area network (WLAN)). Its function is to send images and other auxiliary data to the service platform for processing.
+- 3) **Service platform layer.** Its functions include data processing, data analysis, service display, and the related algorithm / measurement tool libraries. The service platform can utilize various algorithms / tools to identify and classify the types and sizes of surface defects (i.e., "what is the defect", "where is the defect", and "how many defects are present"). The server platform should have sufficient computing capabilities and can provide a user-friendly graphical interactive interface to display processing results as images and graphics.
+- 4) **Application layer.** Measurement and detection applications include, but are not limited to, electronic products, printed circuit board (PCB) and semiconductor craft detection, free-form surface mirror measurement, and the measurement and detection of steel product surface or bearing and screw bolt curved surfaces. It even can go inside a container for defect detection.
+
+# 7 Requirements for 3D machine vision-based surface defect detection service
+
+## 7.1 Requirements for 3D machine vision devices and images
+
+3D machine vision devices include lasers, 3D cameras and auxiliary equipment, online or offline to obtain 3D images of industrial product surfaces.
+
+### 7.1.1 Requirements for 3D machine vision devices
+
+MVD-01: 3D machine vision devices are recommended to use one or several technologies, such as binocular technology, spectrum confocal technology, structured light technology and time of flight (ToF) technology, to obtain surface depth information of the measured object.
+
+MVD-02: It is recommended that binocular vision devices can complete calibration, obtain image pairs, match points with the same name, and calculate coordinates based on calibration parameters and phase differences.
+
+MVD-03: It is recommended that emitting structured light devices can complete calibration, obtain light stripe images and extract stripes, calculate 3D coordinates.
+
+MVD-04: It is recommended that emitting encoded light devices can complete calibration, generate encoded patterns, collect encoded images, process and decode, and calculate 3D coordinates.
+
+MVD-05: It is required that 3D machine vision devices can perform non-contact detecting, without damaging the objects / materials surface, and can match online production speed.
+
+MVD-06: It is recommended that a single 3D machine vision device plus other sensors can perceive and record the speed and direction of object movement, and use this to determine the X and Y coordinates, ensuring that the 3D point cloud data coordinates are not deformed relative to the real object.
+
+MVD-07: For multiple 3D machine vision devices, it is required that 3D machine vision devices calibrate each other and establish a unified coordinate conversion system.
+
+MVD-08: It is recommended that 3D machine vision devices support measuring transparent and highly reflective products, and can use backlight to enhance the contour features of products.
+
+MVD-09: It is recommended to use the spectrum confocal technology to obtain surface depth (object distance) information.
+
+### **7.1.2 Requirements for 3D vision images**
+
+VI-01: It is recommended that the encoding technology for 3D images includes spatial encoding, temporal encoding and colour encoding.
+
+VI-02: It is recommended that 3D point cloud data includes 3D coordinates X, Y, Z, as well as reflection intensity and colour information.
+
+VI-03: It is recommended that a three-dimensional grid is used to store and display depth images (image plus depth information).
+
+## **7.2 Requirements for service platform**
+
+The service platform is required to have sufficient computing power to process and analyse data, and be able to provide various algorithms / tools to identify and classify the types and sizes of surface defects, as well as to present surface defects on the 3D model.
+
+DP-01: It is recommended that service platform can provide algorithm tools for data preprocessing (including depth image histogram tools, missing pixel filling tools, depth image filtering tools, pixel mapping tools).
+
+DP-02: It is recommended that service platform can provide point cloud algorithms / measurement tools to complete data processing (including plane fitting tools, height measurement tools, volume measurement tools, section generation tools, point cloud position and size measurement tools, circular hole detection tools, and point cloud ellipse fitting tools).
+
+DP-03: It is recommended that service platform can provide contour algorithms / measurement tools to complete data processing (including point cloud and contour bounding box tools, contour line circle fitting tools, contour geometry measurement tools, contour position and size measurement tools, and contour area tools).
+
+DP-04: It is recommended that the service platform can recognize pits (concave defects with a certain area), scratches (narrow strip concave defects), orange peel (surface undulating defects with aggregation effect), and pockmark (point like defects with aggregation effect) on the surface of the detected object.
+
+DP-05: It is recommended that service platform concatenates and fuses point cloud data from multiple parts of a product, including aligning and concatenating defect location data, denoising, and completing the detection and analysis of the overall surface of the object.
+
+DP-06: It is recommended that service platform can divide the discontinuous areas on the surface of products (such as steel plates), identify the types of discontinuities, and classify surface defects of products based on given standards.
+
+DP-07: It is recommended that service platform be capable of completing measurements, including geometric tolerance (tolerance of form and position), flatness error and discontinuity size.
+
+DP-08: The service platform is required to provide a user-friendly graphical interactive interface to display processing results as images and graphics.
+
+DP-09: It is recommended that service platform can reconstruct a complete product 3D model based on the obtained 3D images, including the shape, size and range of defects in the 3D model; and / or, it can compare the reconstructed model with a computer aided design (CAD) model to understand the differences in contour, volume, and size.
+
+DP-10: It is recommended that service platform can replay or display statistical information on defect types and quantities and generate analysis reports.
+
+## **7.3 Requirements for application**
+
+3D machine vision system is required to quickly obtain high-precision and repeatable measurement data, be able to match the online production speed, and inspect various types of industrial products and complete the detection, positioning, identification and measurement of plane, free-form surface and curved surface defects.
+
+APP-01: It is recommended that 3D machine vision system can achieve 3D fast inspection and measurement (e.g., geometric tolerance, flatness / warpage error and discontinuity size) for precision structural components such as 3C (computer, communication and consumer electronics) products and PCB.
+
+APP-02: It is recommended that 3D machine vision system can detect planes and curved surfaces, including identifying surface dents / scratches / orange peel / pockmark; and measure surface roughness / smoothness, surface shape / contour / size, etc.
+
+APP-03: It is recommended that 3D machine vision system be capable of dividing the discontinuous areas on the surface, identifying the types of discontinuities, and grading surface defects of products based on given standards.
+
+## **7.4 Others**
+
+OTH-01: If the image data generated by 3D machine vision system is large, it is recommended to compress the data, then send it to the service platform.
+
+OTH-02: It is recommended that images generated by 3D machine vision devices be sent to the service platform for processing through wired and / or wireless networks (such as IMT-2020 networks, industrial Internet).
+
+OTH-03: It is recommended to deploy multi-access edge computing (MEC) devices to enhance real-time online processing of 3D data.
+
+## Appendix I
+
+### Use cases of 3D machine vision-based surface defect detection service
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Three-dimensional (3D) machine vision systems can quickly obtain high-precision and repeatable measurement data, and it can match the online production speed. It can detect various types of materials and industrial products, including reflective surfaces and low-contrast surfaces that cannot be processed by two-dimensional (2D) image analysis. It can complete the detection, positioning, identification and measurement of electronic products and printed circuit board (PCB) surface, free-form surface optical mirror, steel product surface / curved surface defects, etc.
+
+### I.1 Use cases of 3D high-precision detection for planes and curved surfaces
+
+Figure I.1 shows a schematic diagram of 3D detection, along with an example of the depth information of automotive glass surface (right image). Different surface depths may be displayed in different ways (e.g., in different colours) on the screen so that people can see the range and location of defects. Figure I.2 presents more examples of 3D machine vision measurement.
+
+![Figure I.1: Schematic diagram of 3D detection and an example of surface depth information. The left side shows a schematic of a laser and camera setup for 3D detection on a curved glass surface. The right side shows a 3D depth map of an automotive glass surface with a color scale indicating depth.](dd330f8b8f6c16eae20c3a676b4eb804_img.jpg)
+
+The figure consists of two parts. The left part is a schematic diagram of a 3D detection setup. It shows a 'Laser' projecting a plane onto an 'Upper surface' of a 'Curved glass'. A 'Camera' is positioned to capture the laser line. Coordinate axes are labeled:  $Xl, Yl, Zl$  for the laser and  $Xc, Yc, Zc$  for the camera. The right part is a 3D depth map of a curved glass surface, with a color scale on the left ranging from 1 (blue) to 14 (red). The map shows a wavy surface with varying depths. A label 'F.747.16(25)' is present in the bottom right corner.
+
+Figure I.1: Schematic diagram of 3D detection and an example of surface depth information. The left side shows a schematic of a laser and camera setup for 3D detection on a curved glass surface. The right side shows a 3D depth map of an automotive glass surface with a color scale indicating depth.
+
+**Figure I.1 – Schematic diagram of 3D detection and an example of surface depth information**
+
+![Figure I.2: Examples of 3D machine vision measurement. The figure shows three different 3D surface measurements: a flat surface with a color gradient, a curved surface with a color gradient, and a complex irregular shape with a color gradient.](624d9669faa18991d525fea5f0e03269_img.jpg)
+
+The figure displays three examples of 3D machine vision measurements. The first example on the left shows a flat surface with a color gradient representing depth. The second example in the middle shows a curved surface with a color gradient. The third example on the right shows a complex, irregular shape (possibly a mechanical part) with a color gradient. All three plots have axes indicating spatial dimensions.
+
+Figure I.2: Examples of 3D machine vision measurement. The figure shows three different 3D surface measurements: a flat surface with a color gradient, a curved surface with a color gradient, and a complex irregular shape with a color gradient.
+
+**Figure I.2 – Examples of 3D machine vision measurement**
+
+Other use cases include high-precision measurement of the depth and spacing of screw thread, micrometer-level measurement of the optical free-form surface (e.g., mirror and lens), and measurement of irregular shape parts to determine whether these products meet the design requirements, whether they have defects, as well as the size and location of defects. The measurement
+
+accuracy can range from 1-50  $\mu\text{m}$ , X-axis resolution can range 1-10  $\mu\text{m}$ , Z-axis resolution can range 1-5  $\mu\text{m}$ , and the repeated positioning accuracy of the displacement table can be less than 1  $\mu\text{m}$ .
+
+### I.2 Measurement for flatness and geometric tolerance
+
+The service system can perform 3D fast online flatness and geometric tolerance measurement for 3C (computer, communication and consumer electronics) and PCB products. The following Figure I.3 presents a schematic diagram of metal card holder flatness and geometric tolerance measurement.
+
+![Figure I.3: Three images showing 3D point cloud data for 3C product components. The first image shows a rectangular metal frame. The second image shows a complex electronic component with circular features. The third image shows a dense grid of points on a flat surface, likely a PCB or metal plate, with a color scale indicating height variations.](0cc86fe8fc37b0edc9581f2af9459a52_img.jpg)
+
+Figure I.3: Three images showing 3D point cloud data for 3C product components. The first image shows a rectangular metal frame. The second image shows a complex electronic component with circular features. The third image shows a dense grid of points on a flat surface, likely a PCB or metal plate, with a color scale indicating height variations.
+
+**Figure I.3 – Examples of detection for 3C product components**
+
+### I.3 Detection and grading of steel plates
+
+By using multiple cameras side by side, surface point cloud data of larger steel plate can be obtained, and this point cloud data can be concatenated and fused to be transformed into a 3D model of the steel plate. The appearance information of the steel plate, including dimensions, natural deformation, and surface discontinuity information, can be visually observed (as shown in Figure I.4), with a measurement accuracy of 0.1 mm. The service platform can divide the discontinuous areas on the surface of steel plates, identify the types of discontinuities, and grade surface defects of products based on given standards.
+
+![Figure I.4: Two images showing 3D appearance information of a steel plate. The left image is a 3D surface plot with a color scale for height, showing a relatively flat surface with some minor deformation. The right image is a surface point cloud image showing a grid of points on a steel plate, with a small depression or defect visible.](c222a9006d6d60a8d81e6ffbfc0e74ad_img.jpg)
+
+Figure I.4: Two images showing 3D appearance information of a steel plate. The left image is a 3D surface plot with a color scale for height, showing a relatively flat surface with some minor deformation. The right image is a surface point cloud image showing a grid of points on a steel plate, with a small depression or defect visible.
+
+**Figure I.4 – Examples of 3D appearance information of steel plate and a surface point cloud image**
+
+## Bibliography
+
+- [b-ITU-T F.747.11] Recommendation ITU-T F.747.11 (2022), *Requirements for intelligent surface-defect detection service in industrial production lines.*
+- [b-ITU-T F.748.16] Recommendation ITU-T F.748.16 (2022), *Requirements for applications and services in smart manufacturing based on machine vision.*
+- [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.*
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.748.11-202008-I_PDF-E/raw.md b/marked/F/T-REC-F.748.11-202008-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..4b6bc7a7bba32a4adc12b3273477eab75ab8dde4
--- /dev/null
+++ b/marked/F/T-REC-F.748.11-202008-I_PDF-E/raw.md
@@ -0,0 +1,485 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.748.11**
+
+(08/2020)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Multimedia services
+
+---
+
+**Metrics and evaluation methods for a deep  
+neural network processor benchmark**
+
+Recommendation ITU-T F.748.11
+
+# ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| <b>TELEGRAPH SERVICE</b>                                        |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| <b>MOBILE SERVICE</b>                                           |                    |
+| Mobile services and multdestination satellite services          | F.110–F.159        |
+| <b>TELEMATIC SERVICES</b>                                       |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| <b>MESSAGE HANDLING SERVICES</b>                                | F.400–F.499        |
+| <b>DIRECTORY SERVICES</b>                                       | F.500–F.549        |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | F.600–F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700–F.799</b> |
+| <b>ISDN SERVICES</b>                                            | F.800–F.849        |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | F.850–F.899        |
+| <b>ACCESSIBILITY AND HUMAN FACTORS</b>                          | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.748.11
+
+# Metrics and evaluation methods for a deep neural network processor benchmark
+
+## Summary
+
+Recommendation ITU-T F.748.11 provides the benchmarking framework, evaluation metrics and methods, and application scenarios for deep neural network processors operating training and inference tasks.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.748.11 | 2020-08-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/14329">11.1002/1000/14329</a> |
+
+## Keywords
+
+Benchmark, cloud, deep neural network processor, metrics, mobile.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                                      | 1    |
+| 4 Abbreviations and acronyms .....                                                 | 2    |
+| 5 Conventions .....                                                                | 2    |
+| 6 Overview of a deep neural network processor benchmark.....                       | 3    |
+| 6.1 Evaluation object .....                                                        | 3    |
+| 6.2 Evaluation principle.....                                                      | 3    |
+| 7 Architecture framework of the deep neural network processor benchmark.....       | 3    |
+| 7.1 Workload .....                                                                 | 4    |
+| 7.2 AI framework .....                                                             | 4    |
+| 7.3 Hardware acceleration SDK .....                                                | 4    |
+| 7.4 Processor hardware system.....                                                 | 4    |
+| 8 Benchmark metrics and evaluation methods for AI chip under training tasks.....   | 5    |
+| 8.1 Metrics .....                                                                  | 5    |
+| 8.2 Benchmark specification .....                                                  | 5    |
+| 9 Benchmark metrics and evaluation methods for AI chip under inference tasks ..... | 5    |
+| 9.1 Metrics .....                                                                  | 5    |
+| 9.2 Benchmark specification .....                                                  | 6    |
+| 10 Benchmark application scenarios .....                                           | 7    |
+| Appendix I – Reference implementations of benchmark application scenarios.....     | 8    |
+
+
+
+# Recommendation ITU-T F.748.11
+
+## Metrics and evaluation methods for a deep neural network processor benchmark
+
+# 1 Scope
+
+This Recommendation provides the benchmarking framework, evaluation metrics and methods, and application scenarios for operating training and inference tasks.
+
+It addresses the following subjects:
+
+- a) Evaluation method of a deep neural network processor benchmark;
+- b) Architecture framework of the deep neural network processor benchmark;
+- c) Metrics of the deep neural network processor benchmark;
+- d) Benchmark application scenarios of the deep neural network processor benchmark;
+
+# 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.3172] Recommendation ITU-T Y.3172 (2019), *Architectural framework for machine learning in future networks including IMT-2020*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following term defined elsewhere:
+
+**3.1.1 machine learning (ML)** [ITU-T Y.3172]: Processes that enable a computational system to understand data and gain knowledge from it without necessarily being explicitly programmed.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 benchmark:** Benchmark is an evaluation method with a long-term application in the entire computer field. Example: As computer architecture advanced, it became more difficult to compare the performance of various computer systems simply by looking at their specifications. Therefore, tests were developed that allowed comparison of different architectures (i.e., providing benchmarks).
+
+**3.2.2 deep neural network processor:** A deep neural network processor is the kind of processor that could accelerate the computing process regarding a deep neural network.
+
+**3.2.3 workload:** Workload is the benchmark test task for measuring and evaluating artificial intelligence chips, that is, the benchmark test program containing a specific AI task.
+
+**3.2.4 test data set:** A subset of the data set which is used to test the model after the model that has been initially verified by the validation data set.
+
+**3.2.5 model operations:** Model operations are the theoretical amount of operations in deep neural networks. For float operations, the unit is the floating point of operations (FLOPs), and for integer operations, the unit is operations (OPs).
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|       |                                         |
+|-------|-----------------------------------------|
+| AI    | Artificial Intelligence                 |
+| API   | Application Programming Interface       |
+| ASIC  | Application-Specific Integrated Circuit |
+| BLEU  | Bilingual Evaluation Understudy         |
+| CNN   | Convolutional Neural Network            |
+| CPU   | Central Processing Unit                 |
+| DNN   | Deep neural network                     |
+| DSP   | Digital Signal Processing               |
+| DUT   | Device under test                       |
+| FLOPs | Floating Point of Operations            |
+| FPGA  | Field Programmable Gate Array           |
+| FPS   | Frame Per Second                        |
+| GPU   | Graphic Processor Unit                  |
+| MAC   | Multiply and Accumulate                 |
+| mAP   | Mean Average Precision                  |
+| NMS   | Non-Maximum Suppression                 |
+| NPU   | Neural Processing Unit                  |
+| OPs   | Operations                              |
+| PSNR  | Peak Signal to Noise Ratio              |
+| ROC   | Receiver Operating Characteristic       |
+| SDK   | Software Development Kit                |
+
+# 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.
+
+# 6 Overview of a deep neural network processor benchmark
+
+## 6.1 Evaluation object
+
+The evaluation object can be a processor for training and inference tasks at the cloud side, such as an acceleration card, an all-in-one, etc. Or a processor for inference tasks at the mobile side, such as a development board, a mobile phone, and a dedicated chip for applications such as security, autonomous driving, and smart speakers.
+
+## 6.2 Evaluation principle
+
+### 6.2.1 Practicality
+
+Benchmarking methods should be able to produce positive results.
+
+### 6.2.2 Fairness
+
+Benchmarking methods should provide a fair comparison by specifying rules and metrics and be based on objective scientific test data during the evaluation process.
+
+### 6.2.3 Reproducibility
+
+When the same detected quantity is detected in different detection environments, the consistency of the measurement results is ensured.
+
+### 6.2.4 Evaluation mechanism
+
+The benchmarking program focuses on the performance of the processor when operating different training/inference tasks using a complete neural network under specified metrics.
+
+### 6.2.5 Test environment
+
+The benchmark test environment consists of three parts as shown in Figure 6-1, which are respectively the test computer, power consumption monitoring and the device under test (DUT). The test computer is connected through the DUT interface. The power software test tool analyses the DUT's feedback's current and voltage results. Benchmark tools calculate the relevant evaluation metrics.
+
+![Diagram of the benchmark test environment showing the connections between a Power consumption monitoring unit, a Computer, and a DUT.](5a24ac755b962fd5f0183f13de0726de_img.jpg)
+
+The diagram illustrates the benchmark test environment. It features three main components: a 'Power consumption monitoring' unit, a 'Computer' (containing 'Power software test tool + benchmark tool'), and a 'DUT' (Device Under Test). The 'Power consumption monitoring' unit is connected to the 'DUT' via a 'Power cable' and to the 'Computer' via a data line. The 'DUT' has 'Negative' and 'Positive' terminals. A 'Data transmission' line connects the 'Computer' to the 'DUT'. The label 'F.748.11(20)\_F6-1' is present in the bottom right corner of the diagram.
+
+Diagram of the benchmark test environment showing the connections between a Power consumption monitoring unit, a Computer, and a DUT.
+
+**Figure 6-1 – Benchmark test environment**
+
+# 7 Architecture framework of the deep neural network processor benchmark
+
+The benchmarking framework is divided into three layers, as shown in Figure 7-1. These are respectively from the bottom to the top: 1) processor hardware system, 2) hardware acceleration software development kit (SDK), 3) artificial intelligence (AI) framework.
+
+![Figure 7-1: Architecture framework of the deep neural network processor benchmark. The diagram shows a flow from 'Input: Workload' to a box containing 'AI framework' and 'Hardware acceleration SDK', which then points to 'Processor hardware system'. An arrow from the processor points to an 'Output: Metrics' box containing Latency, Throughput, Power, Energy efficiency, Accelerator utilization, and ellipsis. The label F.748.11(20)_F7-1 is at the bottom right.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg)
+
+```
+
+graph TD
+    Input[Input: Workload] --> Framework[AI framework  
+Hardware acceleration SDK]
+    Framework --> Processor[Processor hardware system]
+    Processor --> Metrics[Output: Metrics  
+Latency  
+Throughput  
+Power  
+Energy efficiency  
+Accelerator utilization  
+...]
+  
+```
+
+F.748.11(20)\_F7-1
+
+Figure 7-1: Architecture framework of the deep neural network processor benchmark. The diagram shows a flow from 'Input: Workload' to a box containing 'AI framework' and 'Hardware acceleration SDK', which then points to 'Processor hardware system'. An arrow from the processor points to an 'Output: Metrics' box containing Latency, Throughput, Power, Energy efficiency, Accelerator utilization, and ellipsis. The label F.748.11(20)\_F7-1 is at the bottom right.
+
+**Figure 7-1 – Architecture framework of the deep neural network processor benchmark**
+
+As shown in Figure 7-2, according to the deployment location, a benchmark can be divided into cloud side and edge/mobile side and according to the task, it can be divided into training phase and inference phase.
+
+![Figure 7-2: Classification of deep neural network processor benchmark. The diagram shows 'DNN processor benchmark' branching into 'Edge/mobile' and 'Server/cloud'. 'Edge/mobile' leads to 'Inference'. 'Server/cloud' leads to both 'Inference' and 'Training'. The label F.748.11(20)_F7-2 is at the bottom right.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+```
+
+graph LR
+    DNN[DNN processor benchmark] --> Edge[Edge/mobile]
+    DNN --> Server[Server/cloud]
+    Edge --> Inference1[Inference]
+    Server --> Inference2[Inference]
+    Server --> Training[Training]
+  
+```
+
+F.748.11(20)\_F7-2
+
+Figure 7-2: Classification of deep neural network processor benchmark. The diagram shows 'DNN processor benchmark' branching into 'Edge/mobile' and 'Server/cloud'. 'Edge/mobile' leads to 'Inference'. 'Server/cloud' leads to both 'Inference' and 'Training'. The label F.748.11(20)\_F7-2 is at the bottom right.
+
+**Figure 7-2 – Classification of deep neural network processor benchmark**
+
+## 7.1 Workload
+
+Workload consists of test cases that use neural network models to complete training or inference tasks in specified test scenarios.
+
+## 7.2 AI framework
+
+The AI framework is a software framework for implementing relevant artificial intelligence models. It includes training frameworks such as TensorFlow, PyTorch, Caffe, PaddlePaddle and Theano, and inference frameworks such as MACE, SNPE, NCNN, TensorFlow Lite, Caffe2go, MDL, Core ML, and others. These frameworks allow us to build deep learning models to complete training or inference tasks.
+
+## 7.3 Hardware acceleration SDK
+
+The hardware acceleration SDK can support the AI framework upwards, and provide the central processing unit (CPU), graphic processor unit (GPU), digital signal processing (DSP), and neural processing unit (NPU) with required hardware resources for scheduling and use.
+
+## 7.4 Processor hardware system
+
+The processor hardware system can contain physical devices for artificial intelligence computing, including chips such as CPU, GPU, application-specific integrated circuit (ASIC), field programmable gate array (FPGA), etc., as well as computing servers and mobile terminal devices.
+
+# 8 Benchmark metrics and evaluation methods for AI chip under training tasks
+
+## 8.1 Metrics
+
+### 8.1.1 Training time
+
+The training time is generally defined as the time for training a model on a specific data set to achieve the target accuracy, excluding pre-processing and model loading time.
+
+### 8.1.2 Accuracy
+
+Accuracy here refers to the accuracy related to the training set. For specific application scenarios and data sets, given the network structure and hyper-parameter configuration, the accuracy metric is used to check whether the training can reach the specified accuracy after a certain number of iterations (training time).
+
+## 8.2 Benchmark specification
+
+### 8.2.1 Test data set
+
+The test data set discloses the proportion of the training set and the test data set and the data pre-processing method.
+
+### 8.2.2 Model
+
+It is required to unify the hyper-parameters, weights' initialization and the format of weights (fp64, fp32, fp16).
+
+### 8.2.3 Reference implementation
+
+Table 8-1 provides test scenarios, test data sets, target accuracy, and reference models for training benchmarks. All these scenarios are recommended while provided with a training benchmark.
+
+**Table 8-1 – Test scenarios for training**
+
+| Test scenarios | Test data set      | Target accuracy                     | Model       |
+|----------------|--------------------|-------------------------------------|-------------|
+| 10.1           | ImageNet (224x224) | 74.9% Top-1 Accuracy                | ResNet_50   |
+| 10.2           | COCO 2017          | 23% mAP                             | SSD         |
+| 10.2           | COCO 2017          | 0.377 Box min AP, 0.339 Mask min AP | Mask R-CNN  |
+| 10.6           | WMT English-German | 25.0 BLEU                           | Transformer |
+
+## 9 Benchmark metrics and evaluation methods for AI chip under inference tasks
+
+## 9.1 Metrics
+
+### 9.1.1 Inference latency
+
+Inference latency refers to the time that accelerator/processor completes the inference with respect to one sample for a given application scenario with a specific batch size, excluding pre-process and post-process time.
+
+### 9.1.2 Throughput
+
+Throughput is the number of input data samples that is being processed per second. For an image processing task, the unit of throughput is frames per second (FPS).
+
+### 9.1.3 Power consumption
+
+Power consumption refers to the average power consumption of the DUT in the process of inference.
+
+### 9.1.4 Energy efficiency
+
+Energy efficiency refers to the ratio of the throughput with a specific network to the power consumption of the task performed in a given application scenario.
+
+### 9.1.5 Accelerator utilization
+
+Accelerator utilization refers to the ratio of the actual amount of model operations to the theoretical peak performance under the given application scenario.
+
+Accelerator utilization = (throughput \* model operations) / theoretical peak performance.
+
+Taking the convolutional neural network (CNN) as an example, model operations= MAC\*2.
+
+### 9.1.6 Accuracy
+
+The accuracy of the model inference is related to specific tasks and evaluation metrics. See clause 10 for details.
+
+## 9.2 Benchmark specification
+
+### 9.2.1 Test system environment
+
+According to the operating system the test system environment is an environment supported by the device under test (DUT).
+
+### 9.2.2 Acceleration SDK
+
+The acceleration SDK provides the neural network acceleration engine and its detailed description. It provides interface functions including initialization Init (), pre-processing PreProcess (), loading model LoadModel (), running Run (), unloading model UnloadModel () and post processing PostProcess ().
+
+### 9.2.3 Model information
+
+Provides relevant information including model categories, original accuracy, data set, input and output node names, the mean of pre-processing and normalized parameters, tensor information (input and output), channel information (RGB / BGR), and data format (NHWC, etc.).
+
+### 9.2.4 Reference implementation
+
+Table 9-1 provides test scenarios, test data sets, target accuracy, and reference models for an inference benchmark. All these scenarios are recommended while doing a training benchmark.
+
+**Table 9-1– Test scenarios for inference**
+
+| Test scenarios | Test data | Model                                                           |
+|----------------|-----------|-----------------------------------------------------------------|
+| 10.1           | ImageNet  | ResNet_50, ResNet_101, Inception_v4, MobileNet_v1, MobileNet_v2 |
+| 10.2           | COCO 2017 | Faster-RCNN (with FPN), Yolo V3, SSD                            |
+| 10.3           | VOC2012   | Deeplabv3+                                                      |
+| 10.4           | 2017CVPR  | VDSR                                                            |
+| 10.5           | LFW       | DeepID3                                                         |
+
+# 10 Benchmark application scenarios
+
+Deep learning technologies are most commonly applied within vision, language/audio, and commerce. The application scenario indicates specific tasks developed based on these three application areas. For vision, the application scenarios include classification, recognition, and detection, semantic segmentation, etc. For language and audio, application scenarios could be machine translation and speech recognition. For commerce, the recommendation is the most well-known application scenario. Table 10-1 shows the typical application scenarios with related datasets and reference implementations, which are recommended when conducting benchmark test.
+
+**Table 10-1 – Benchmark application scenarios**
+
+| Area           | No.  | Application scenarios | Dataset          | Reference implementation model | Accuracy            |
+|----------------|------|-----------------------|------------------|--------------------------------|---------------------|
+| Vision         | 10.1 | Image classification  | ImageNet         | ResNet/Inception/MobileNet     | Prediction accuracy |
+|                | 10.2 | Object detection      | COCO2017/VOC2012 | SSD/Mask R-CNN/YOLO            | mAP, NMS            |
+|                | 10.3 | Segmentation          | VOC2012          | Deeplabv3+/FCN                 | mIoU                |
+|                | 10.4 | Super-Resolution      | DIV2K            | VGG19/VDSR                     | PSNR,SSIM           |
+|                | 10.5 | Face recognition      | LFW              | VGG-16-Face CNN (224x224)      | Rank1,ROC           |
+| Language/Audio | 10.6 | Translation           | WMT Eng-Germ     | Transformer                    | BLEU                |
+|                | 10.7 | Speech recognition    | LibriSpeech      | Deep Speech 2                  | WER<br>Perplexity   |
+| Commerce       | 10.8 | Recommendation        | MovieLens-20M    | NCF                            | Prediction accuracy |
+
+## Appendix I
+
+### Reference implementations of benchmark application scenarios
+
+Table I.1 gives a reference implementation of benchmark application scenarios.
+
+**Table I.1 – Benchmark test use cases**
+
+| No.  | Application scenarios | Dataset  | Source                                                                                            | Model (input size)        | Source                                                                                                                                                            |
+|------|-----------------------|----------|---------------------------------------------------------------------------------------------------|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 10.1 | Image classification  | ImageNet | <a href="http://www.image-net.org/download-images">http://www.image-net.org/download-images</a>   | ResNet_50 (224x224)       | <a href="https://github.com/KaimingHe/deep-residual-networks">https://github.com/KaimingHe/deep-residual-networks</a>                                             |
+|      |                       |          |                                                                                                   | ResNet-101 (224x224)      | <a href="https://github.com/KaimingHe/deep-residual-networks">https://github.com/KaimingHe/deep-residual-networks</a>                                             |
+|      |                       |          |                                                                                                   | Inception-v3 (299x299)    | <a href="https://github.com/tensorflow/models/tree/master/research/slim">https://github.com/tensorflow/models/tree/master/research/slim</a>                       |
+|      |                       |          |                                                                                                   | MobileNet-v2 (224x224)    | <a href="https://github.com/shicai/MobileNet-Caffe">https://github.com/shicai/MobileNet-Caffe</a>                                                                 |
+| 10.2 | Object detection      | VOC2012  | <a href="http://host.robots.ox.ac.uk/pascal/VOC/">http://host.robots.ox.ac.uk/pascal/VOC/</a>     | ssd_mobilenetv1 (300x300) | <a href="https://github.com/FreeApe/VGG-or-MobileNet-SSD">https://github.com/FreeApe/VGG-or-MobileNet-SSD</a>                                                     |
+|      |                       |          |                                                                                                   | YOLOv3 (320x320)          | <a href="https://github.com/eric612/MobileNet-YOLO">https://github.com/eric612/MobileNet-YOLO</a>                                                                 |
+| 10.3 | Segmentation          | VOC2012  | <a href="http://host.robots.ox.ac.uk/pascal/VOC/">http://host.robots.ox.ac.uk/pascal/VOC/</a>     | FCN (500x500)             | <a href="https://github.com/shelhamer/fcn.berkeleyvision.org/tree/master/voc-fcn8s">https://github.com/shelhamer/fcn.berkeleyvision.org/tree/master/voc-fcn8s</a> |
+| 10.4 | Super-Resolution      | DIV2K    | <a href="https://data.vision.ee.ethz.ch/cvl/DIV2K/">https://data.vision.ee.ethz.ch/cvl/DIV2K/</a> | VDSR (256x256)            | <a href="https://github.com/huangzehao/caffe-vdsr">https://github.com/huangzehao/caffe-vdsr</a>                                                                   |
+| 10.5 | Face recognition      | LFW      | <a href="http://viswww.cs.umass.edu/lfw/">http://viswww.cs.umass.edu/lfw/</a>                     | VGG-16-Face CNN (224x224) | <a href="http://www.robots.ox.ac.uk/~vgg/software/vgg_face/">http://www.robots.ox.ac.uk/~vgg/software/vgg_face/</a>                                               |
+
+**Table I.1 – Benchmark test use cases**
+
+| <b>No.</b> | <b>Application scenarios</b> | <b>Dataset</b> | <b>Source</b>                                                                                     | <b>Model (input size)</b> | <b>Source</b>                                                                                     |
+|------------|------------------------------|----------------|---------------------------------------------------------------------------------------------------|---------------------------|---------------------------------------------------------------------------------------------------|
+| 10.6       | Translation                  | WMT Eng-Germ   | <a href="http://www.statmt.org">http://www.statmt.org</a>                                         | Transformer               | <a href="https://github.com/Kyubyong/transformer">https://github.com/Kyubyong/transformer</a>     |
+| 10.7       | Speech recognition           | Libri Speech   | <a href="http://www.openslr.org/12/">http://www.openslr.org/12/</a>                               | Deep Speech 2             | <a href="https://github.com/yao-matrix/deepSpeech2">https://github.com/yao-matrix/deepSpeech2</a> |
+| 10.8       | Recommendation               | Movie Lens-20M | <a href="https://grouplens.org/datasets/movielens/">https://grouplens.org/datasets/movielens/</a> | NCF                       | <a href="https://github.com/guoyang9/NCF">https://github.com/guoyang9/NCF</a>                     |
+
+
+
+
+
+# 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.748.22-202309-I_PDF-E/raw.md b/marked/F/T-REC-F.748.22-202309-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..99cd10d425ece30ec7d1c59ce54352ae4aafc399
--- /dev/null
+++ b/marked/F/T-REC-F.748.22-202309-I_PDF-E/raw.md
@@ -0,0 +1,441 @@
+
+
+# Recommendation**ITU-T F.748.22 (09/2023)**
+
+SERIES F: Non-telephone telecommunication services  
+Multimedia services
+
+---
+
+## **Functional architecture for feature-based distributed intelligent systems**
+
+![ITU logo](390120de4fe440c42fea8154fcaad334_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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.748.22
+
+## Functional architecture for feature-based distributed intelligent systems
+
+## Summary
+
+Recommendation ITU-T F.748.22 defines the architecture, the functional entities, and the reference points for feature-based distributed intelligent systems.
+
+## History\*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.748.22 | 2023-09-13 | 16          | 11.1002/1000/15621 |
+
+## Keywords
+
+Feature, functional architecture, functional entity, intelligent system, reference point.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                                       | 1    |
+| 4 Abbreviations and acronyms .....                                                  | 1    |
+| 5 Conventions .....                                                                 | 2    |
+| 6 Overview of feature-based intelligent applications .....                          | 2    |
+| 7 A functional architecture for feature-based distributed intelligent systems ..... | 3    |
+| 8 Functional entities.....                                                          | 4    |
+| 8.1 Front-end function set.....                                                     | 4    |
+| 8.2 Data processing function set.....                                               | 5    |
+| 8.3 Algorithm function set.....                                                     | 5    |
+| 8.4 Service control function set .....                                              | 6    |
+| 8.5 Operation function set .....                                                    | 6    |
+| 8.6 Management function set .....                                                   | 6    |
+| 8.7 Security function set.....                                                      | 6    |
+| 8.8 Development function set.....                                                   | 7    |
+| 8.9 Applications.....                                                               | 7    |
+| 9 Reference points .....                                                            | 8    |
+| 9.1 Reference point A1 .....                                                        | 8    |
+| 9.2 Reference point A2.....                                                         | 8    |
+| 9.3 Reference point A3.....                                                         | 8    |
+| 9.4 Reference point A4.....                                                         | 8    |
+| 9.5 Reference point A5.....                                                         | 8    |
+| 9.6 Reference point A6.....                                                         | 8    |
+| 9.7 Reference point A7.....                                                         | 8    |
+| 9.8 Reference point A8.....                                                         | 9    |
+| 9.9 Reference point A9.....                                                         | 9    |
+| Bibliography.....                                                                   | 10   |
+
+
+
+# Recommendation ITU-T F.748.22
+
+## Functional architecture for feature-based distributed intelligent systems
+
+## 1 Scope
+
+This Recommendation defines the architecture, the reference points and the functional entities and their relationships in feature-based distributed intelligent systems (FDIS).
+
+The scope of this Recommendation includes:
+
+- The architecture for feature-based distributed intelligent systems.
+- The functional entities and their relationships with feature-based distributed intelligent systems.
+- The reference points in feature-based distributed intelligent systems.
+
+## 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.748.11] Recommendation ITU-T F.748.11 (2020), *Metrics and evaluation methods for a deep neural network processor benchmark*.
+
+[ITU-T F.748.21] Recommendation ITU-T F.748.21 (2022), *Requirements and framework for feature-based distributed intelligent systems*.
+
+## 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:
+
+|     |                                   |
+|-----|-----------------------------------|
+| API | Application Programming Interface |
+| ASF | Audio Sensor Function             |
+| DPF | Data Preparation Function         |
+
+|      |                                               |
+|------|-----------------------------------------------|
+| DPPF | Data Preprocessing Function                   |
+| DSF  | Data Storage Function                         |
+| FCF  | Feature Compression Function                  |
+| FDF  | Feature Decoding Function                     |
+| FDIS | Feature-based Distributed Intelligent Systems |
+| FEF  | Feature Encoding Function                     |
+| FXF  | Feature Extraction Function                   |
+| IAAF | Intelligent Audio Algorithm Function          |
+| ITS  | Intelligent Traffic Systems                   |
+| IVAF | Intelligent Video Algorithm Function          |
+| NLP  | Natural Language Processing                   |
+| VSF  | Video Sensor Function                         |
+
+## 5 Conventions
+
+In this Recommendation:
+
+Function set: In the context of FDIS architecture, "function set" are defined as a collection of functionalities. It is represented by the following symbol:
+
+![A rounded rectangular box containing the text 'Function Set'.](35a7554182eb055209552843f341a1ae_img.jpg)
+
+A rounded rectangular box containing the text 'Function Set'.
+
+Function: In the context of FDIS architecture, a "function" 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 text 'Function'.](5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg)
+
+A rectangular box containing the text 'Function'.
+
+## 6 Overview of feature-based intelligent applications
+
+Feature-based distributed intelligent systems (FDIS) extract and transmit features instead of original data, i.e., video, audio, text, point cloud, etc. Compared to intelligent systems that are based on original multimedia data, which require a large amount of storage and transmission bandwidth and offer limited technological solutions that use multimedia coding to reduce data volume, FDIS could save bandwidth by extracting only the effective information from multimedia data.
+
+In some latency sensitive intelligent systems, i.e., autonomous driving and industrial detection and control, it is crucial to process the data in real-time. Using features in addition to original data might allow fast searching and other artificial intelligence (AI) tasks. FDIS is able to reduce the latency in some scenarios.
+
+Feature-based intelligent applications are applications that utilize feature data extracted from real-world scenarios for machine learning and processing. FDIS is a type of distributed intelligence system.
+
+## 7 A functional architecture for feature-based distributed intelligent systems
+
+![Figure 1: A functional architecture for feature-based distributed intelligent systems. The diagram shows a layered structure with various function sets and their interconnections. At the top, four dashed boxes represent 'Applications': Intelligent traffic, Smart manufacturing, Smart city, and Smart agriculture. Below this, a central vertical spine connects several function sets. A4 (Service control function set) contains Data storage function, Industrial camera SDK, and Neural network algorithm models. A3 (Algorithm function set) contains Intelligent video algorithm function, Intelligent audio algorithm function, and Natural language processing function. A2 (Data processing function set) contains Feature decoding function, Data storage function, and Data preparation function. A1 (Front-end function set) contains Video sensor function, Audio sensor function, Data preprocessing function, Feature encoding function, Feature extraction function, and Feature compression function. On the left, A6 (Operation function set) contains Data transformation, Data aggregation, Feature selection, and Operation function set. A9 (Development function set) contains Model training, Model validation, Model compression, Model visualization, and Development function set. On the right, A5 (Security function set) contains Data encryption, Data authentication, Data access control, Data integrity checks, Network security, Security monitoring, Data masking, and Data security auditing. A7 (Management function set) contains User management, Resource management, System monitoring, and System log. Arrows indicate data flow and control between these sets, with labels A1 through A9.](acfc53eca625d62b38aa2563efa95c3e_img.jpg)
+
+Figure 1: A functional architecture for feature-based distributed intelligent systems. The diagram shows a layered structure with various function sets and their interconnections. At the top, four dashed boxes represent 'Applications': Intelligent traffic, Smart manufacturing, Smart city, and Smart agriculture. Below this, a central vertical spine connects several function sets. A4 (Service control function set) contains Data storage function, Industrial camera SDK, and Neural network algorithm models. A3 (Algorithm function set) contains Intelligent video algorithm function, Intelligent audio algorithm function, and Natural language processing function. A2 (Data processing function set) contains Feature decoding function, Data storage function, and Data preparation function. A1 (Front-end function set) contains Video sensor function, Audio sensor function, Data preprocessing function, Feature encoding function, Feature extraction function, and Feature compression function. On the left, A6 (Operation function set) contains Data transformation, Data aggregation, Feature selection, and Operation function set. A9 (Development function set) contains Model training, Model validation, Model compression, Model visualization, and Development function set. On the right, A5 (Security function set) contains Data encryption, Data authentication, Data access control, Data integrity checks, Network security, Security monitoring, Data masking, and Data security auditing. A7 (Management function set) contains User management, Resource management, System monitoring, and System log. Arrows indicate data flow and control between these sets, with labels A1 through A9.
+
+F.748.22(23)
+
+**Figure 1 – A functional architecture for feature-based distributed intelligent systems**
+
+A functional architecture for FDIS, as shown in Figure 1, is composed of a front-end function set, a data processing function set, an algorithm function set, applications, a service control function set, an operation function set, a management function set, and a security function set.
+
+The front-end function set (normally mapping to the front-end equipment) has the ability to capture, process, and compress the signal. The front-end function set also has the ability to pre-process, extract features, and encode data.
+
+The data processing function set provides the ability to decode data, store data, and prepare data.
+
+The algorithm function set provides algorithms for machine tasks, data storage, and data evaluation.
+
+The development function set provides the ability of model training, model validation, model compression, and model visualization.
+
+The applications provide the capability to implement machine tasks from the original data and/or from the feature data.
+
+The service control function set provides abilities for users to control the service of the FDIS.
+
+The operation function set provides the ability to manage and monitor the operation status of the system.
+
+The management function set provides the ability to manage different parts of the feature-based distributed intelligent system.
+
+The security function set provides capabilities for system security.
+
+## **8 Functional entities**
+
+### **8.1 Front-end function set**
+
+The front-end function set (normally mapping to the front-end equipment) has the ability to capture, process, and compress the signal. Sensors capture and output the digital signals. Based on the target needs, users can choose which pre-processing methods and which kinds of features to be used for the captured signal. The features are then extracted accordingly and then encoded and sent to the application or service via a network by the front-end equipment. The front-end function set includes the video sensor function, audio sensor function, data preprocessing function, feature extraction function, feature compression function, and feature encoding function.
+
+The video sensor function (VSF) captures the visual signal from the real world in raw format. The VSF could be a camera, camera system, or other imaging device that enables it to detect motion and capture it as a series of still images or video footage. Features could be extracted to detect motion of people or objects without detecting the identity of the people, alerting a user to potential security risks or allowing them to capture footage of an event. VSF could also be used to trigger an alarm or alert when motion is detected. Depending on the configuration, an alarm is triggered manually or automatically, with sensitivity and other settings that are adjusted to meet specific needs.
+
+The audio sensor function (ASF) captures the audio signal from real-world scenarios and processes the signal in raw format. The ASF could be an audio sound transducer, a microphone, microphone systems, or other audio recording devices that detect sound and capture it as audio files. This module is used to detect sound from people or objects without detecting the identity of the people, alerting a user of potential security risks or allowing them to capture recordings of an event. ASF could also trigger an alarm or alert when sound is detected. Depending on the configuration, an alarm is triggered manually or automatically, with sensitivity and other settings that are adjusted to meet specific needs.
+
+The data preprocessing function (DPPF) is responsible for transforming the captured video/audio data to a format that is suitable for subsequent processing required by users. This function supports multiple pre-processing methods, such as down/up-sampling, filtering, denoising, demosaicing, cropping, and format transformation. DPPF prepares data for analysis by cleaning, transforming, and organizing, and comprises auto functions that help deliver an enhanced signal.
+
+The feature extraction function (FXF) is used to extract the relevant and informative features from preprocessed data. However the extracted features may be high dimensional and computationally expensive. Therefore, it can be beneficial to apply a feature compression function to reduce the number of features while maintaining as much information as possible.
+
+The feature compression function (FCF) is used to reduce the data volume of the features by selecting a subset of the informative features, combining or transforming them, or using other techniques to reduce the redundancy in features. It improves the efficiency and performance of the system while maintaining the accuracy and quality of the results. FCF is a process of reducing the size of the extracted features while preserving the same level of accuracy or performance, making it more efficient for storage and analysis. There are a variety of methods for performing feature compression, including principal component analysis, singular value decomposition, and linear discriminant analysis.
+
+The feature encoding function (FEF) consists of feature conversion and a video encoder. It encodes the extracted features into compact binary bitstreams then compresses the feature using a video codec. The feature conversion module transforms data into a format that a traditional video codec can process. When the input is video, the FEF is equal to the video encoder. It is designed to be compatible with the video coding system.
+
+### 8.2 Data processing function set
+
+The data domain provides the ability to process, store, and prepare data for applications or services.
+
+The feature decoding function (FDF) corresponds to the feature compression function (FCF) in the front-end function set and is responsible for decoding/decompressing bitstreams to reconstructed features. These reconstructed features are then prepared and sent to the application or service to perform machine tasks. FDF is the process of converting encoded data back into its original form. This is typically done after the data has been encoded or transformed, such as with feature encoding, feature conversion. FDF restores the original format of the data, which is used for further analysis or display.
+
+The data storage function (DSF) has two responsibilities: managing and storing the compressed bitstream of features in a well-managed file format, which enables random access, fast search, and reorganization of the compressed feature data, and storing the reconstructed features in their original formats suitable for implementing machine tasks. DSF is used to store data in a structured format. This includes storing data in a database or other data storage system. DSF helps to ensure that data is organized and protected, making it easier to access and analyse. DSF is also used to store data in multiple formats, such as text, images, and videos, allowing for more efficient analysis and management.
+
+Lastly, the data preparation function (DPF) prepares the reconstructed feature data for transport to the application domain or service domain. DPF is used to clean, organize, and transform data before it is used for analysis. This module involves cleaning the data of errors or outliers, and transforming and organizing it in a way suitable for analysis. DPF is also used to combine data from different sources to create a dataset. After the data has been prepared, it is used for further analysis and to create predictive models.
+
+### 8.3 Algorithm function set
+
+An algorithm function set is a group of computer algorithms used to process and interpret data. These algorithms are used to create, predict, recognize, analyse or understand the content. Algorithm function sets include algorithms for video, image, audio, natural language processing, and data mining. The algorithms used in a function set will depend on the type of data being processed and the applications.
+
+The intelligent video algorithm function (IVAF) comprises a set of algorithms targeting processing of video data and features extracted from video data. IVAF is a type of computer algorithm used to process and interpret video data. This algorithm is used to detect motion, analyse actions, or recognize objects in a video. The algorithm is also used to create predictive models, such as predicting the outcome of a video or the likelihood of a certain event.
+
+The intelligent audio algorithm function (IAAF) provides algorithms focusing on audio data and features extracted from audio data. IAAF is a type of computer algorithm used to process and interpret audio data. This algorithm is used to detect sound, analyse speech, or recognize words in a recording. The algorithm is also used to create predictive models, such as predicting the outcome of a recording or the likelihood of a certain event.
+
+Natural language processing (NLP) is a field of artificial intelligence (AI) that focuses on enabling machines to understand, interpret, and respond to natural language, such as written or spoken language used by humans in everyday communication. In feature-based intelligent systems, NLP plays a role in identifying relevant features in natural language and using them to make intelligent guesses or decisions. For instance, NLP can help in sentiment analysis where it identifies the emotions that are expressed in a text to determine whether it is positive or negative.
+
+### 8.4 Service control function set
+
+The service control function set provides abilities for users to control the service of the FDIS, including activating services, deactivating services, requesting service access and managing service resources.
+
+A service control function set in FDIS is a set of functions including access registration, access authentication, identification, authorization, location, presence, data flow control and clock synchronization.
+
+### 8.5 Operation function set
+
+The operation function set provides the ability to manage and monitor the operation status of the system, including service performance, resource usage, and operation log, etc.
+
+**Feature selection:** The feature selection module has capabilities including feature categorization management, pre-processing selection, compression selection, feature extraction selection, analysis algorithm selection. It supports users choosing different data pre-processing algorithms, such as down/up-sampling, filtering, denoising, cropping, and different features, defined in [ITU-T F.748.11], to be extracted as well as related feature extraction algorithms, compression algorithms and analysis algorithms.
+
+**Data transformation:** The data transformation module has capabilities including feature format transformation. It supports transforming of different features, defined in [ITU-T F.748.11], to be stored and transmitted for analysis and display.
+
+**Data aggregation:** The data aggregation module has capabilities including feature concatenation, feature layering, feature splitting. It supports concatenate, layer and split features according to the configuration of feature selection, and thus applies to different feature decoding and analysis algorithms.
+
+### 8.6 Management function set
+
+The management function set provides the ability to manage different parts of the feature-based distributed intelligent system, including managing device configurations and resources. It also provides the capability for users to control or customize the system components in order to optimize the system performance or to meet specific requirements. The management functions in FDIS include:
+
+- User management
+- Resource management
+- System monitoring: system configuration, system deployment, system optimization
+- System log.
+
+### 8.7 Security function set
+
+The security function set provides capabilities for system security, such as encryption, data protection, access control, intrusion detection and response. It also provides capabilities to detect malicious behaviours and protect data stored within the system. The security functions in FDIS include:
+
+- Data encryption
+- Data authentication
+- Data access control
+- Data integrity checks
+- Network security
+
+- Security monitoring
+- Data masking
+- Data security auditing.
+
+### **8.8 Development function set**
+
+The development function set involves the process of building a model that can predict outputs based on inputs. This process involves using a training dataset to train the model, which involves adjusting the model's parameters based on the data to improve its accuracy. The model is tested on a separate testing dataset to evaluate how well it performs on new, unseen data. The results of the testing are used to refine the model and improve its accuracy.
+
+Some development functions in a feature-based distributed intelligent system are recommended to include:
+
+- Model training
+- Model validation
+- Model compression
+- Model visualization.
+
+### **8.9 Applications**
+
+The applications implement machine tasks from the feature data. FDIS are employed across various industries and domains to perform complex tasks that require advanced computational capabilities and decision-making skills. Some application functions in a feature-based distributed intelligent system are recommended to include:
+
+**Intelligent traffic:** FDIS can be used to extract features from traffic data such as vehicle speed, density, and volume, and use machine learning algorithms to optimize traffic flow, detect accidents or road closures, and improve safety. Applications of intelligent traffic include traffic management, urban planning, and logistics.
+
+**Smart manufacturing:** FDIS can be used to extract features from manufacturing data such as machine performance, energy usage, and product quality, and use machine learning algorithms to optimize production processes, monitor equipment health, and predict equipment failures. Applications of smart manufacturing include predictive maintenance, quality control, and supply chain optimization.
+
+**Smart city:** FDIS can be applied to analyse and process large amounts of data from various sources to optimize urban infrastructure and improve quality of life. FDIS can be used to extract features from data such as traffic, air quality, and energy consumption, and adopt machine learning algorithms to optimize transportation systems, reduce energy use, and improve public safety. Applications of smart city include traffic management, waste management, energy efficiency, and urban planning. FDIS can help city planners making decisions about infrastructure improvements, reducing energy consumption and greenhouse gas emissions, and improving the quality of life for residents.
+
+**Smart agriculture:** FDIS can be applied to extract features from agricultural data such as soil moisture, temperature, and nutrient levels, and use machine learning algorithms to optimize crop yields, monitor plant health and predict crop diseases. Applications of smart agriculture include precision farming, crop management, and resource conservation. The use of feature-based intelligent systems in agriculture can help farmers make informed decisions about planting, fertilizing, watering and harvesting their crops, leading to increased productivity, cost savings and environmental sustainability.
+
+## **9 Reference points**
+
+### **9.1 Reference point A1**
+
+Reference point A1 lies between the front-end function set and the data processing function set.
+
+It is used to deliver a compressed feature stream from the front-end function set to the data processing function set for data processing and storage.
+
+### **9.2 Reference point A2**
+
+Reference point A2 lies between the data processing function set and the algorithm function set.
+
+It is used to deliver the pre-processed feature stream from data processing function set to the algorithm function set for intelligent analysis.
+
+### **9.3 Reference point A3**
+
+Reference point A3 lies between the algorithm function set and the service control function set.
+
+It is used by the service control function set to monitoring of the status of the algorithm function set, managing and configuring services within the system, enabling the algorithm function set to adjust its algorithms. Appropriate application programming interfaces (APIs) may be used to pass the parameters and configurations into algorithms, and receive the results from the algorithm function set.
+
+### **9.4 Reference point A4**
+
+Reference point A4 lies between the applications and the service control function set.
+
+It is used by the service control function set for providing specific services or applications to end-users through the applications. It is used by the applications to provide service delivery and quality to the service control function set.
+
+### **9.5 Reference point A5**
+
+Reference point A5 lies between the service control function set and the security function set.
+
+It is used by the service control function set for managing and enforcing service-related policies. It is used by the security function set for identifying and preventing security threats.
+
+### **9.6 Reference point A6**
+
+Reference point A6 lies between the service control function set and the operation function set.
+
+It is used by the operation function set for maintaining and diagnosing network components, management of network resources, and providing feedback to the service control function set regarding potential issues or performance degradation of the service control function set.
+
+### **9.7 Reference point A7**
+
+Reference point A7 lies between the service control function set and the management function set.
+
+It is used by the management function set for overseeing, directing the operation of the network, ensuring high-level network governance and effective service delivery, and for providing feedback to the service control function set. It is used by the service control function set to provide information to the management function set regarding current service policies or the status of network resources.
+
+### **9.8 Reference point A8**
+
+Reference point A8 lies between the service control function set and the front-end function set.
+
+It is used by the service control function set to control the access authentication, and authorization of the front-end function set, and to indicate the required types of features.
+
+### **9.9 Reference point A9**
+
+Reference point A9 lies between the algorithm function set and the development function set.
+
+It is used by the development function set to send the optimized model and updated hyper parameter to the algorithm function set.
+
+## Bibliography
+
+- [b-ITU-T F.700] Recommendation ITU-T F.700 (2000), *Framework Recommendation for multimedia services.*
+- [b-ITU-T F.743] Recommendation ITU-T F.743 (V2) (2019), *Requirements and service description for video surveillance.*
+- [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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.748.25-202309-I_PDF-E/raw.md b/marked/F/T-REC-F.748.25-202309-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..f6f5314f26ffa7728447cb8b098bc284949a8ce3
--- /dev/null
+++ b/marked/F/T-REC-F.748.25-202309-I_PDF-E/raw.md
@@ -0,0 +1,757 @@
+
+
+Recommendation
+
+**ITU-T F.748.25 (09/2023)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+---
+
+**Requirements for speech interaction of  
+intelligent customer 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 globe with white grid lines and the letters 'ITU' in a bold, blue, sans-serif font.
+
+ITU logo
+
+# ITU-T F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.748.25
+
+# Requirements for speech interaction of intelligent customer services
+
+## Summary
+
+Recommendation ITU-T F.748.25 describes scenarios, high-level architecture, functional requirements, and performance requirements for speech interaction of intelligent customer services. Some detailed use cases and reference process for the creation of the knowledge base are described in Appendices I and II, respectively.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.748.25 | 2023-09-13 | 16          | 11.1002/1000/15622 |
+
+## Keywords
+
+Artificial intelligence, customer service, requirements, speech interaction, use cases.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                          | 3    |
+| 7 High-level architecture .....                                           | 4    |
+| 8 Requirements .....                                                      | 5    |
+| 8.1 Functional requirements .....                                         | 5    |
+| 8.2 Non-functional requirements.....                                      | 6    |
+| Appendix I Use cases of intelligent customer services.....                | 8    |
+| Appendix II Reference process for the creation of the knowledge base..... | 15   |
+| II.1 Overview .....                                                       | 15   |
+| II.2 Single domain KB establishment .....                                 | 15   |
+| II.3 Cross-domain KB establishment.....                                   | 16   |
+| Bibliography.....                                                         | 17   |
+
+
+
+# Recommendation ITU-T F.748.25
+
+## Requirements for speech interaction of intelligent customer services
+
+## 1 Scope
+
+This Recommendation specifies high-level architecture and requirements for speech interaction of intelligent customer services.
+
+This Recommendation covers the following:
+
+- High-level architecture of speech interaction of intelligent customer service;
+- Functional requirements for speech interaction of intelligent customer service;
+- Performance requirements for speech interaction of intelligent customer 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.
+
+None.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 application** [b-ITU-T Y.2091]: A structured set of capabilities, which provide value-added functionality supported by one or more services, which may be supported by an API interface.
+
+**3.1.2 artificial intelligence (AI)** [b-ITU-T F.749.13]: An interdisciplinary field, usually regarded as a branch of computer science, dealing with models and systems for the performance of functions generally associated with human intelligence, such as reasoning and learning.
+
+**3.1.3 automatic speech recognition (ASR)** [b-ITU-T H.625]: 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).
+
+**3.1.4 knowledge base** [b-ITU-T F.746.3]: 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 provision such as the QA system and search system.
+
+**3.1.5 knowledge graph** [b-IEEE 2807]: Assemblies of knowledge elements and their relations described in a structured form.
+
+**3.1.6 mean opinion score (MOS)** [b-ITU-T P.800]: The mean of opinion scores, i.e., of the values on a predefined scale that subjects assign to their opinion of the performance of the telephone transmission system used either for conversation or for listening to spoken material.
+
+**3.1.7 natural language processing (NLP)** [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.8 text-to-speech synthesis (TTS)** [b-ITU-T P.10/G.100-Amendment 1]: A TTS process generates a speech signal from text codes. It is usually composed of 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 that are used by:
+- an acoustical signal generating part, the synthesizer itself, which generates the audible speech.
+
+**3.1.9 voice recognition** [b-ISO 9241-154]: Capability of a system to identify a specific person's voice.
+
+### **3.2 Terms defined in this Recommendation**
+
+This Recommendation defines the following terms:
+
+**3.2.1 intelligent customer service:** Customer service with intelligent capabilities, which is composed of some or all of the artificial intelligence technology capabilities such as speech recognition, natural language processing, intelligent search, and text-to-speech synthesis.
+
+**3.2.2 multi-factor authentication:** Authentication using two or more factors to achieve authentication.
+
+## **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|     |                                  |
+|-----|----------------------------------|
+| AI  | Artificial Intelligence          |
+| ASR | Automatic Speech Recognition     |
+| CRM | Customer Relationship Management |
+| IVR | Interactive Voice Response       |
+| KB  | Knowledge Base                   |
+| KG  | Knowledge Graph                  |
+| MOS | Mean Opinion Score               |
+| NLP | Natural Language Processing      |
+| TTS | Text-to-Speech                   |
+
+## **5 Conventions**
+
+In this Recommendation:
+
+The keywords "be 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
+
+Intelligent customer service is based on big data and artificial intelligence (AI) technologies such as natural language processing (NLP), machine learning, and large-scale knowledge management. It enables communication between enterprises and users, thereby improving operational efficiency and reducing costs.
+
+Figure 1 shows the speech interaction scenarios of intelligent customer service. These include four major scenarios.
+
+### - Voice navigation scenario
+
+Voice navigation scenario mainly describes the scenarios in which the user speaks the required service through the communication terminal, and the intelligent customer service system interacts with the customer and can quickly and accurately find relevant content for the user and make a voice reply. If the user needs to know more information, the intelligent customer service system can directly transfer the voice stream to the seat, which can provide more detailed services.
+
+### - Intelligent outbound scenario
+
+The intelligent outbound scenario mainly describes the scenarios that communicate with customers according to the preset outbound logic. Through multiple rounds of conversation and vocabulary guidance, it can complete the business function of outbound calls.
+
+### - Operator assistant scenario
+
+Operator assistant scenario mainly describes the scenarios which can obtain customer information through customer relationship management (CRM) and gives prompts to operators on the computer screen in real time to help operators communicate with the customers.
+
+### - Service quality inspection scenario
+
+The service quality inspection scenario mainly describes which system performs online analysis of the voice stream obtained by the call centre in real time through the communication network, or which system downloads the customer service audio recording file for offline analysis and processing to generate the corresponding quality inspection analysis results.
+
+![Diagram illustrating speech interaction scenarios in intelligent customer services. The diagram shows a flow from Customers (represented by icons of people, a smartphone, a telephone, and a computer monitor) to a Call centre, then to an Intelligent customer service system, which is connected to a CRM KB/KG. The Intelligent customer service system is also connected to a Seat (represented by an icon of a person wearing a headset). The Seat is connected to four scenarios: Voice navigation, Intelligent outbound, Operator assistance, and Service quality inspection. The diagram is labeled F.748.25(23).](2ba086df3506f81bae3a9b53725dcfea_img.jpg)
+
+```
+graph TD; Customers[Customers: People, Smartphone, Telephone, Computer] <--> CallCentre[Call centre]; CallCentre <--> IntelligentSystem[Intelligent customer service system]; IntelligentSystem --- CRM[CRM KB/KG]; IntelligentSystem <--> Seat[Seat: Person with Headset]; Seat <--> VoiceNavigation[Voice navigation]; Seat <--> IntelligentOutbound[Intelligent outbound]; Seat <--> OperatorAssistance[Operator assistance]; Seat <--> ServiceQualityInspection[Service quality inspection];
+```
+
+F.748.25(23)
+
+Diagram illustrating speech interaction scenarios in intelligent customer services. The diagram shows a flow from Customers (represented by icons of people, a smartphone, a telephone, and a computer monitor) to a Call centre, then to an Intelligent customer service system, which is connected to a CRM KB/KG. The Intelligent customer service system is also connected to a Seat (represented by an icon of a person wearing a headset). The Seat is connected to four scenarios: Voice navigation, Intelligent outbound, Operator assistance, and Service quality inspection. The diagram is labeled F.748.25(23).
+
+**Figure 1 – Speech interaction scenarios in intelligent customer services**
+
+## 7 High-level architecture
+
+Figure 2 presents the high-level architecture for speech interaction of intelligent customer services according to the use cases.
+
+![Figure 2: High-level architecture for speech interaction of intelligent customer services. The diagram shows a three-layer structure: Applications layer, Services layer, and Network layer, all contained within an 'Intelligent customer service' box. The Applications layer includes Voice navigation, Intelligence outbound, Operator assistance, and Service quality inspection. The Services layer includes Natural language processing, Automatic speech recognition, Text to speech, and KB/KG. The Network layer includes Voice exchange. All three layers are connected to a 'Call centre' box at the bottom via double-headed arrows.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg)
+
+```
+graph TD
+    subgraph ICS [Intelligent customer service]
+        subgraph AL [Applications layer]
+            V[Voice navigation]
+            IO[Intelligence outbound]
+            OA[Operator assistance]
+            SQI[Service quality inspection]
+        end
+        subgraph SL [Services layer]
+            NLP[Natural language processing]
+            ASR[Automatic speech recognition]
+            TTS[Text to speech]
+            KBKG[KB/KG]
+        end
+        subgraph NL [Network layer]
+            VE[Voice exchange]
+        end
+        AL <--> SL
+        SL <--> NL
+    end
+    NL <--> CC[Call centre]
+```
+
+Figure 2: High-level architecture for speech interaction of intelligent customer services. The diagram shows a three-layer structure: Applications layer, Services layer, and Network layer, all contained within an 'Intelligent customer service' box. The Applications layer includes Voice navigation, Intelligence outbound, Operator assistance, and Service quality inspection. The Services layer includes Natural language processing, Automatic speech recognition, Text to speech, and KB/KG. The Network layer includes Voice exchange. All three layers are connected to a 'Call centre' box at the bottom via double-headed arrows.
+
+F.748.25(23)
+
+**Figure 2 – High-level architecture for speech interaction of intelligent customer services**
+
+The high-level architecture for speech interaction of intelligent customer services covers three layers: applications, services and networks. A general description of these three blocks is presented below.
+
+- **Applications layer:** Applications layer is the software for realizing the speech interaction of intelligent customer service. The applications include voice navigation, intelligence outbound, operator assistance and service quality inspection, etc.
+
+A detailed description of the applications can be found in Appendix I.
+
+- **Services layer:** Services layer is the basic AI functional modules for supporting applications. The services include natural language processing (NLP), automatic speech recognition (ASR), text-to-speech synthesis (TTS), and knowledge base (KB)/knowledge graph (KG).
+
+The NLP function uses algorithms to understand and manipulate human language. The NLP function can realize applications of intelligent customer service through algorithms such as intention understanding, named entity recognition, text classification, etc.
+
+The ASR function uses algorithms to convert human speech into text. The ASR function can realize multiple applications in intelligent customer service through single-sentence speech recognition, continuous speech recognition, etc.
+
+The TTS function uses algorithms to synthesize natural-sounding speech in multiple languages. This function can be used in user interaction applications of intelligent customer service.
+
+The KB/KG contains information about words, sentences, and the relationship between knowledge. It describes all the knowledge information and the relationship between each piece of knowledge information used in the intelligent customer service.
+
+- **Network layer:** Network layer is the communication network's capability for voice exchange between the call centre and services layer. The voice exchange supports multimedia voice, voice call in and call out, voice transfer and voice recording functions, etc.
+
+## 8 Requirements
+
+### 8.1 Functional requirements
+
+The functional requirements for intelligent customer service are as follows:
+
+- The speech interaction of intelligent customer service is required to have the ability to recognize keywords in sentences;
+- The speech interaction of intelligent customer service is required to support speech interaction with multiple access channels, and supports one or more speech interaction methods such as fixed telephone network, mobile telephone network, Internet, and other access methods;
+- The presentation of the speech interaction results of the intelligent customer service is required to include the results of TTS, and can optionally include the presentation of information such as text and graphics;
+- The speech interaction of intelligent customer service is recommended to support automatic identification of voice start point and end point;
+- The speech interaction of intelligent customer service can optionally support the dynamically generate guidance and prompt words based on the results of ASR and NLP;
+- The speech interaction of intelligent customer service can optionally support the service quality inspection of operators based on the results of ASR and NLP;
+- The ASR function is recommended to have the ability to recognize continuous speech;
+- The ASR function is recommended to support the language recognition function, that is, to determine the language of the voice based on the user's voice input;
+- The ASR function is recommended to support mixed language recognition, that is, support the recognition of different language words in sentences;
+- The NLP function of intelligent customer service is recommended to support the understanding of abbreviations, aliases, locations and numbers;
+- The NLP function of intelligent customer service is recommended to support the fault-tolerant understanding of typical misleading words;
+- The NLP function of intelligent customer service is recommended to support multiple rounds of dialogue;
+- The NLP function of intelligent customer service can optionally support the understanding of subordinate relationships, the understanding of partial-overall relationships, the understanding of geographic relationships, the understanding of causality, the understanding of sequential relationships, and the understanding of proximal relationships;
+- The TTS function of intelligent customer service is required to support multi-language synthesis and multi-timbre synthesis such as young female voices and young male voices;
+- The TTS function of intelligent customer service can optionally support mixed language and personalized TTS;
+- The purpose of building a KB of intelligent customer service is mainly to organize and manage knowledge according to the business requirements, including keyword libraries, service processes, question templates, or KGs constructed in the form of triples.
+  - a) The KB of intelligent customer service is required to have the function of keyword identification and maintenance according to the business requirements and support the addition, deletion, and modification of characteristic keywords of customer service system services.
+  - b) The KB of intelligent customer service is required to have the maintenance function of static prompts, that is, the guiding prompt function according to the business
+
+requirements, and support the addition, deletion, and modification of static prompting functions of the customer service system services.
+
+- c) The KB of intelligent customer service is required to have the service process maintenance function according to the business requirements, and support the addition, deletion, and modification of the service process of the customer service system.
+- d) The KB of intelligent customer service is required to have the function of editing question templates according to the business requirements, and support the addition, deletion, and modification of semantic expressions of customer service questions.
+- e) The KB of intelligent customer service can optionally support the knowledge construction based on the KG technology in the form of ontology/triple.
+
+– The speech interaction of intelligent customer service that will use voice recognition for authentication, or verification for any use case, especially for critical transactions like services provisioning, financial transactions, or dealing with personal or financial data, is required to consider the implementation of multi-factor authentication beyond voice recognition. This is to protect customers' sensitive information and accounts from voice cloning trials by fraudsters by creating synthetic audio recordings of a person's voice that are often indistinguishable from authentic voices;
+
+– The speech interaction of intelligent customer service is recommended to have the below measures to detect and prevent fraudulent activities such as suspicious account activity, unusual recognition attempts, or transaction patterns during the user verification process:
+
+- a) The system can optionally monitor transactions in real-time to detect any suspicious activity. While machine learning algorithms can optionally be used to analyse patterns of fraudulent behaviour and identify potential fraudsters.
+- b) The system can optionally send alerts to designated personnel when it detects suspicious activity.
+- c) The system can optionally block transactions that have a high-risk score to prevent fraud.
+- d) The system can optionally analyse user behaviour to detect any anomalies or suspicious activity.
+
+### 8.2 Non-functional requirements
+
+#### 8.2.1 Performance requirements
+
+##### 8.2.1.1 Response time of speech interaction
+
+The response time of speech interaction refers to the time between the end of the user input and the return of the result.
+
+The interactive response time calculation method is shown in the formula.
+
+$$T_{ack} = t_r - t_e$$
+
+$T_{ack}$  – Response time
+
+$t_r$  – Result output moment
+
+$t_e$  – Voice input end time
+
+If the speech interaction system supports the recognition result to be returned multiple times,  $t_r$  should be the time when the first part of the recognition result is returned.
+
+In the case of multiple rounds of speech interaction process,  $T_{ack}$  refers to the response time of each round of speech interaction.
+
+In order to ensure the service quality of intelligent customer service,  $T_{ack}$  is recommended to be less than an appropriate threshold.
+
+##### 8.2.1.2 Speech interaction success rate
+
+In the interaction process of the speech interaction system, the user can obtain the result within the predetermined interaction rounds, and it can then be judged that the current rounds of interaction are successful; otherwise, it is judged that these rounds of interaction have failed.
+
+The calculation method of the interaction success rate is as follows:
+
+$$P_s = \frac{S}{S + F} \times 100\%$$
+
+$P_s$  – Interaction success rate
+
+$S$  – The number of successful interactions
+
+$F$  – The number of failed interactions
+
+In order to ensure the service quality of intelligent customer service,  $P_s$  is recommended to be higher than an appropriate threshold.
+
+##### 8.2.1.3 ASR accuracy index
+
+In the speech interaction system, it is recommended that the word accuracy of keyword speech recognition should be calculated in different noise environments (e.g., noise intensity below 50 dB and noise intensity of 60 dB to 65 dB, etc.).
+
+In the speech interaction system, it is recommended that the word accuracy rate of continuous speech recognition should be calculated in, in different noise environments (e.g., noise intensity below 50 dB and noise intensity of 60 dB to 65 dB, etc.).
+
+In order to ensure the service quality of intelligent customer service, it is recommended that the ASR accuracy should be higher than an appropriate threshold.
+
+##### 8.2.1.4 TTS evaluation
+
+TTS test adopts the mean opinion score (MOS) test method for evaluation. Through the result of the intelligent customer service speech synthesis, it tests the difference in sound quality, intelligibility and naturalness between the synthesized speech and the human speech, numerically quantifies the test result with the average MOS score, and then records the average result.
+
+In order to ensure the service quality of intelligent customer service, MOS is recommended to be greater than or equal to an appropriate threshold.
+
+##### 8.2.1.5 NLP accuracy index
+
+The NLP ability is recommended to be tested by various people with multiple rounds. The calculation method for the correct rate of NLP is as follows.
+
+$$R_{ss} = \frac{N_{ss}}{N} \times 100\%$$
+
+$R_{ss}$  – NLP rate
+
+$N_{ss}$  – The number of times the intention and semantic elements are correctly judged
+
+$N$  – The total number of correct texts
+
+In order to ensure the service quality of intelligent customer service,  $R_{ss}$  is recommended to be higher than an appropriate threshold.
+
+## Appendix I
+
+### Use cases of intelligent customer services
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### I.1 Use cases
+
+#### I.1.1 Use cases for full speech interaction of intelligent customer services
+
+The full speech interaction use case means that all the functions are completed by the speech interaction system, and there is no operator participation during the interaction. It may include:
+
+- a) The call centre recognizes the customer's voice input through ASR and NLP technology, then automatically responds to the customer through TTS technology.
+
+![Diagram of full speech interaction of intelligent customer service (Model A)](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg)
+
+The diagram illustrates the workflow of a full speech interaction system. At the top, three icons represent customer input: a smartphone, a fixed telephone, and a computer monitor. Arrows from these icons point to a box containing 'Automatic call distributor' and 'Multimedia gateway'. From this box, an arrow labeled '2' points down to a central box containing 'Computer telephony integrator' and 'IVR'. To the left of this central box is an 'ASR' (Automatic Speech Recognition) block, and to the right is a 'TTS' (Text-to-Speech) block. Below the central box is an 'NLP' (Natural Language Processing) block. Arrows indicate the flow of information: '3' from IVR to ASR, '4' from ASR to Computer telephony integrator, '5' from Computer telephony integrator to NLP, '6' from NLP to IVR, '7' from IVR to TTS, and '8' from TTS to IVR. Finally, an arrow labeled '9' points from the IVR back up to the 'Automatic call distributor / Multimedia gateway' box, and an arrow labeled '10' points from that box to the output icons (smartphone, telephone, computer monitor). A small label 'F.748.25(23)' is in the bottom right corner of the diagram area.
+
+Diagram of full speech interaction of intelligent customer service (Model A)
+
+**Figure I.1 – Example of full speech interaction of intelligent customer service (Model A)**
+
+The description of the workflow is as below:
+
+- 1) The customer calls the call centre using a cell phone, fixed telephone or a computer and speaks according to voice prompts;
+- 2) The automatic call distributor / multimedia gateway of the call centre transfers the speech to the computer telephony integrator / interactive voice response (IVR);
+- 3) IVR transfers the call to the ASR function;
+- 4) The ASR function converts the speech to text and returns the result to the IVR;
+- 5) IVR uses NLP technology to recognize user intent for the text;
+- 6) NLP function returns the result to the IVR;
+- 7) IVR matches the predefined process based on the results of NLP to synthesize the next speech;
+- 8) TTS function returns the speech to the IVR;
+- 9) IVR transfers the speech to the automatic call distributor / multimedia gateway through the call connection;
+
+- 10) The automatic call distributor / multimedia gateway transfers the speech to the customer. Then the customer starts the next round of dialogue.
+- b) Instead of traditional manual telephone return visits and telephone notifications, the standard services of the call centre can be implemented through a dialogue between the robot and the user.
+
+![Diagram of full speech interaction of intelligent customer service (Model B)](bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg)
+
+The diagram illustrates the workflow of an intelligent customer service system (Model B). At the top, three icons represent the customer: a smartphone, a telephone, and a computer monitor. Arrows labeled 5 and 6 point from these icons to a central box containing 'Automatic call distributor' and 'Multimedia gateway'. From this box, an arrow labeled 7 points down to a 'Computer telephony integrator / IVR' box. To the left of the IVR is an 'ASR' (Automatic Speech Recognition) box, connected by arrows 8 and 9. To the right is a 'TTS' (Text-to-Speech) box, connected by arrows 2, 3, and 12. Below the IVR are two boxes: 'NLP' (Natural Language Processing) and 'Service template', connected by arrows 10, 11, and 1 respectively. A small label 'F.748.25(23)' is in the bottom right corner.
+
+Diagram of full speech interaction of intelligent customer service (Model B)
+
+**Figure I.2 – Example of full speech interaction of intelligent customer service (Model B)**
+
+The description of the workflow is as below:
+
+- 1) The service template is pre-installed in the IVR;
+- 2) The call centre initiates a call connection and the IVR requests the TTS function for the service template;
+- 3) The TTS function returns the speech to the IVR;
+- 4) IVR transfers the speech to the automatic call distributor / multimedia gateway through the call connection;
+- 5) The automatic call distributor / multimedia gateway transfers the speech to the customer;
+- 6) The customer answers the call and speaks according to voice prompts;
+- 7) The automatic call distributor / multimedia gateway of the call centre transfers the speech to the computer telephony integrator / IVR;
+- 8) IVR transfers the call to the ASR function;
+- 9) The ASR function converts the speech to text and returns the result to the IVR;
+- 10) IVR uses NLP technology to recognize user intent for the text;
+- 11) NLP function returns the result to IVR;
+- 12) IVR matches the predefined template based on the results of the NLP to the next round of dialogue.
+
+#### I.1.2 Use cases for partial speech interaction of intelligent customer services
+
+Partial speech interaction use cases refers to the participation of the operator throughout the speech interaction process. It may include:
+
+- a) During the speech interaction process, the user cannot obtain the target result, or the target result does not conform to the service specification. The system transfers the interactive session to the operator, and the service will be provided by the operator.
+
+![Diagram illustrating the workflow of partial speech interaction of intelligent customer service (Mode A). The diagram shows a flow from a customer (represented by icons of a cell phone, fixed telephone, and computer) through an Automatic call distributor / Multimedia gateway, then to a Computer telephony integrator / IVR. The IVR interacts with ASR (Automatic Speech Recognition), NLP (Natural Language Processing), and TTS (Text-to-Speech). The IVR also connects to a Seat (operator). The flow is numbered 1 through 12, showing the sequence of interactions: 1) Customer call, 2) Call transfer to integrator, 3) IVR to ASR, 4) ASR to IVR, 5) IVR to NLP, 6) NLP to IVR, 7) IVR to Seat, 8) Seat to IVR, 9) IVR to TTS, 10) TTS to IVR, 11) IVR to gateway, 12) Gateway to customer.](5cab96b2d23174c25919840ecd50aa48_img.jpg)
+
+```
+
+graph TD
+    subgraph Customer [Customer]
+        direction TB
+        C1[Cell phone]
+        C2[Fixed telephone]
+        C3[Computer]
+    end
+    subgraph Gateway [Automatic call distributor / Multimedia gateway]
+        direction LR
+        G1[Automatic call distributor]
+        G2[Multimedia gateway]
+    end
+    subgraph Integrator [Computer telephony integrator / IVR]
+        direction LR
+        I1[Computer telephony integrator]
+        I2[IVR]
+    end
+    ASR[ASR]
+    NLP[NLP]
+    TTS[TTS]
+    Seat[Seat]
+
+    Customer -- 1 --> Gateway
+    Gateway -- 2 --> Integrator
+    Integrator -- 3 --> ASR
+    ASR -- 4 --> Integrator
+    Integrator -- 5 --> NLP
+    NLP -- 6 --> Integrator
+    Integrator -- 7 --> Seat
+    Seat -- 8 --> Integrator
+    Integrator -- 9 --> TTS
+    TTS -- 10 --> Integrator
+    Integrator -- 11 --> Gateway
+    Gateway -- 12 --> Customer
+  
+```
+
+Diagram illustrating the workflow of partial speech interaction of intelligent customer service (Mode A). The diagram shows a flow from a customer (represented by icons of a cell phone, fixed telephone, and computer) through an Automatic call distributor / Multimedia gateway, then to a Computer telephony integrator / IVR. The IVR interacts with ASR (Automatic Speech Recognition), NLP (Natural Language Processing), and TTS (Text-to-Speech). The IVR also connects to a Seat (operator). The flow is numbered 1 through 12, showing the sequence of interactions: 1) Customer call, 2) Call transfer to integrator, 3) IVR to ASR, 4) ASR to IVR, 5) IVR to NLP, 6) NLP to IVR, 7) IVR to Seat, 8) Seat to IVR, 9) IVR to TTS, 10) TTS to IVR, 11) IVR to gateway, 12) Gateway to customer.
+
+**Figure I.3 – Example of partial speech interaction of intelligent customer service (Mode A)**
+
+The description of the workflow is as below:
+
+- 1) The customer calls the call centre using a cell phone, fixed telephone or computer and speaks according to voice prompts;
+  - 2) The automatic call distributor / multimedia gateway of the call centre transfers the speech to the computer telephony integrator / IVR;
+  - 3) IVR transfers the call to the ASR function;
+  - 4) The ASR function converts the speech to text and returns the text to the IVR;
+  - 5) IVR uses NLP technology to recognize user intent for the text;
+  - 6) The NLP function returns the result to the IVR;
+  - 7) IVR cannot match the right process based on the results of NLP and transfers the call to the seat;
+  - 8) The operator communicates with the customer and helps the customer deal with problems;
+  - 9) The operator determines to return the result with the IVR and transfers the call to the IVR. IVR requests the TTS function to synthesize the speech;
+  - 10) The TTS function returns the speech to IVR;
+  - 11) IVR transfers the speech to the automatic call distributor / multimedia gateway through the call connection;
+  - 12) The automatic call distributor / multimedia gateway transfers the speech to the customer.
+- b) Speech interaction system only performs certain functions, such as IVR navigation. That is, the user speaks the specific words, and after the ASR, the speech is transferred to a specific operator for follow-up service.
+
+![Diagram illustrating the workflow of intelligent customer service (Mode B). The process starts with a customer (represented by icons of a smartphone, fixed telephone, and computer) sending input (1) to an 'Automatic call distributor / Multimedia gateway'. This unit then transfers the call (2) to a 'Computer telephony integrator / IVR'. The IVR transfers the call (3) to the 'ASR' (Automatic Speech Recognition) function, which returns the result (4) to the IVR. The IVR then transfers the call (5) to a 'Seat' (operator). The operator communicates (6) with the customer and determines the result (7). The IVR requests the 'TTS' (Text-to-Speech) function (8) to synthesize the speech, which returns the speech (9) to the IVR. Finally, the IVR transfers the call (10) back to the 'Automatic call distributor / Multimedia gateway', which then transfers the speech (10) to the customer.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg)
+
+```
+
+graph TD
+    Customer[Customer: Smartphone, Phone, Computer] -- 1 --> Gateway[Automatic call distributor / Multimedia gateway]
+    Gateway -- 2 --> IVR[Computer telephony integrator / IVR]
+    IVR -- 3 --> ASR[ASR]
+    ASR -- 4 --> IVR
+    IVR -- 5 --> Seat[Seat]
+    Seat -- 6 --> IVR
+    IVR -- 7 --> TTS[TTS]
+    TTS -- 8 --> IVR
+    IVR -- 9 --> Gateway
+    Gateway -- 10 --> Customer
+  
+```
+
+Diagram illustrating the workflow of intelligent customer service (Mode B). The process starts with a customer (represented by icons of a smartphone, fixed telephone, and computer) sending input (1) to an 'Automatic call distributor / Multimedia gateway'. This unit then transfers the call (2) to a 'Computer telephony integrator / IVR'. The IVR transfers the call (3) to the 'ASR' (Automatic Speech Recognition) function, which returns the result (4) to the IVR. The IVR then transfers the call (5) to a 'Seat' (operator). The operator communicates (6) with the customer and determines the result (7). The IVR requests the 'TTS' (Text-to-Speech) function (8) to synthesize the speech, which returns the speech (9) to the IVR. Finally, the IVR transfers the call (10) back to the 'Automatic call distributor / Multimedia gateway', which then transfers the speech (10) to the customer.
+
+F.748.25(23)
+
+**Figure I.4 – Example of partial speech interaction of intelligent customer service (Mode B)**
+
+The description of the workflow is as below:
+
+- 1) The customer calls the call centre using a cell phone, fixed telephone or computer and speaks according to voice prompts;
+- 2) The automatic call distributor / multimedia gateway of the call centre transfers the speech to the computer telephony integrator / IVR;
+- 3) IVR transfers the call to the ASR function;
+- 4) The ASR function converts the speech to text and returns the result to the IVR;
+- 5) IVR matches the right process based on the results of the ASR and transfers the call to the specific seat;
+- 6) The operator communicates with the customer and helps the customer deal with the problems;
+- 7) The operator determines to return the result with IVR and transfers the call to the IVR. IVR requests the TTS function to synthesize the speech;
+- 8) TTS function returns the speech to the IVR;
+- 9) IVR transfers the speech to the automatic call distributor / multimedia gateway through the call connection;
+- 10) The automatic call distributor / multimedia gateway transfers the speech to the customer.
+
+#### I.1.3 Use cases for service quality inspection of intelligent customer services
+
+Traditional service quality inspection requires a lot of workloads. Through ASR and NLP techniques, the operator's service quality can be automatically evaluated.
+
+![Diagram illustrating the workflow for service quality inspection of intelligent customer services. The process starts with a customer (represented by icons of a cell phone, fixed telephone, and computer) making a call (1). The call is routed through an Automatic call distributor / Multimedia gateway (2) to a Computer telephony integrator / IVR (3). The operator (Seat) communicates with the customer (3). The quality inspection function (4) performs quality inspection online/offline according to the voice of the operator. The quality inspection function transfers the voice to the ASR function (5). The quality inspection module supports voice information detection such as speech speed and mute in different roles during the conversation (6). The Inspector (represented by an icon of a person with a headset) receives the output from the ASR function (6).](76b0cd79baaedd942af4dc42f2e764b8_img.jpg)
+
+```
+
+graph TD
+    subgraph Customer_Inputs [ ]
+        direction TB
+        C1[Cell phone icon]
+        C2[Fixed telephone icon]
+        C3[Computer monitor icon]
+    end
+    C1 -- 1 --> ACD[Automatic call distributor]
+    C2 -- 1 --> MG[Multimedia gateway]
+    subgraph ACD_MG [ ]
+        direction LR
+        ACD
+        MG
+    end
+    ACD_MG -- 2 --> CTI_IVR[Computer telephony integrator]
+    subgraph CTI_IVR [ ]
+        direction LR
+        CTI
+        IVR
+    end
+    CTI_IVR -- 3 --> Seat[Seat icon]
+    CTI_IVR -- 4 --> QI[Quality inspection]
+    QI -- 5 --> ASR[ASR]
+    ASR -- 6 --> Inspector[Inspector icon]
+    style Customer_Inputs fill:none,stroke:none
+    style ACD_MG fill:none,stroke:none
+    style CTI_IVR fill:none,stroke:none
+    style Seat fill:none,stroke:none
+    style Inspector fill:none,stroke:none
+    style QI fill:none,stroke:none
+    style ASR fill:none,stroke:none
+  
+```
+
+Diagram illustrating the workflow for service quality inspection of intelligent customer services. The process starts with a customer (represented by icons of a cell phone, fixed telephone, and computer) making a call (1). The call is routed through an Automatic call distributor / Multimedia gateway (2) to a Computer telephony integrator / IVR (3). The operator (Seat) communicates with the customer (3). The quality inspection function (4) performs quality inspection online/offline according to the voice of the operator. The quality inspection function transfers the voice to the ASR function (5). The quality inspection module supports voice information detection such as speech speed and mute in different roles during the conversation (6). The Inspector (represented by an icon of a person with a headset) receives the output from the ASR function (6).
+
+**Figure I.5 – Example of service quality inspection of intelligent customer services**
+
+The description of the workflow is as below:
+
+- 1) The customer calls the call centre using a cell phone, fixed telephone or computer and speaks according to voice prompts;
+- 2) The automatic call distributor / multimedia gateway of the call centre transfers the speech to the computer telephony integrator / IVR;
+- 3) The operator communicates with the customer and helps the customer deal with the problems;
+- 4) The quality inspection function can perform quality inspection online/offline according to the voice of the operator;
+- 5) The quality inspection function transfers the voice to the ASR function;
+- 6) The quality inspection module supports voice information detection such as speech speed and mute in different roles during the conversation.
+
+#### **I.1.4 Use cases for operator assistance of intelligent customer services**
+
+The operator assistance system can identify the conversation between the operators and the customers through ASR technology during the call and capture the key information through the NLP technology. It can then obtain customer information through the CRM and give prompts to operators on the computer screen in real time (including knowledge points and verbal reminders, automated extraction of customer portraits, analysis of customer purchase intentions, etc.) to help operators communicate with the customers.
+
+![Figure I.6 – Example of operator assistance of intelligent customer services. The diagram illustrates a workflow for intelligent customer service. At the top, three icons represent customer contact methods: a smartphone, a fixed telephone, and a computer monitor. An arrow labeled '1' points from these icons to a box containing 'Automatic call distributor' and 'Multimedia gateway'. An arrow labeled '2' points from this box to another box containing 'Computer telephony integrator' and 'IVR'. An arrow labeled '3' points from the 'IVR' component to a 'Seat' icon (representing an operator). An arrow labeled '4' points from the 'Computer telephony integrator' to an 'Operator assistance system' box. From the 'Operator assistance system', an arrow labeled '5' points down to an 'ASR' box, and an arrow labeled '7' points up to an 'NLP' box. From the 'ASR' box, an arrow labeled '6' points back up to the 'Operator assistance system'. From the 'NLP' box, an arrow labeled '9' points down to the 'Operator assistance system', and an arrow labeled '8' points right to a 'Key words recognition' box. From the 'Key words recognition' box, an arrow labeled '10' points down to an oval labeled 'KB/KG'. From the 'KB/KG' oval, an arrow labeled '11' points back to the 'Operator assistance system'. Finally, an arrow points from the 'Operator assistance system' to a computer monitor icon next to the 'Seat' icon.](9c6461e1e94afae4dec455e69a2ce152_img.jpg)
+
+Figure I.6 – Example of operator assistance of intelligent customer services. The diagram illustrates a workflow for intelligent customer service. At the top, three icons represent customer contact methods: a smartphone, a fixed telephone, and a computer monitor. An arrow labeled '1' points from these icons to a box containing 'Automatic call distributor' and 'Multimedia gateway'. An arrow labeled '2' points from this box to another box containing 'Computer telephony integrator' and 'IVR'. An arrow labeled '3' points from the 'IVR' component to a 'Seat' icon (representing an operator). An arrow labeled '4' points from the 'Computer telephony integrator' to an 'Operator assistance system' box. From the 'Operator assistance system', an arrow labeled '5' points down to an 'ASR' box, and an arrow labeled '7' points up to an 'NLP' box. From the 'ASR' box, an arrow labeled '6' points back up to the 'Operator assistance system'. From the 'NLP' box, an arrow labeled '9' points down to the 'Operator assistance system', and an arrow labeled '8' points right to a 'Key words recognition' box. From the 'Key words recognition' box, an arrow labeled '10' points down to an oval labeled 'KB/KG'. From the 'KB/KG' oval, an arrow labeled '11' points back to the 'Operator assistance system'. Finally, an arrow points from the 'Operator assistance system' to a computer monitor icon next to the 'Seat' icon.
+
+F.748.25(23)
+
+**Figure I.6 – Example of operator assistance of intelligent customer services**
+
+The description of the workflow is as below:
+
+- 1) The customer calls the call centre using a cell phone, fixed telephone or computer and speaks according to voice prompts;
+- 2) The automatic call distributor / multimedia gateway of the call centre transfers the speech to the computer telephony integrator / IVR;
+- 3) The operator communicates with the customer and helps the customer deal with the problems;
+- 4) The operator assistance system can give the information to the operator according to the voice of the operator and the customer;
+- 5) The operator assistance system transfers the voice to the ASR function;
+- 6) The ASR function converts the speech to text and returns the text to the operator assistance system;
+- 7) The operator assistance system uses the NLP technology to perform NLP for the text;
+- 8) Key words recognition module performs keywords' detection;
+- 9) The NLP function returns the text and keywords result to the operator assistance system;
+- 10) The operator assistance system obtains customer information from KB/KG;
+- 11) The operator assistance system gives prompts to operators on the computer screen in real time.
+
+#### I.1.5 Use case of a phone-based voice authentication
+
+Use case of a phone-based voice authentication, as an example of using voice recognition within an intelligent customer service.
+
+The below workflow outlines a phone-based voice authentication that uses a combination of identifying information, voice input, and additional authentication factors to granting access to users' accounts or other protected resources.
+
+The description of the workflow is as below:
+
+- a) The user calls the authentication system through IVR using their registered phone number.
+
+- b) The system prompts the user to provide their username or other identifying information such as an account number or national identification number.
+- c) The user provides their username or other identifying information using a voice input.
+- d) The system verifies the user based on the provided information and prompts the user to provide a voice sample for verification.
+- e) The user provides a voice sample for verification.
+- f) If the voice sample matches, the system prompts the user to provide additional authentication factors such as password, or PIN, and a physical security token.
+- g) The user provides the additional authentication factor(s) as requested.
+- h) If all authentication factors are successfully verified, the system grants access to the user's account or other protected resource.
+
+It is worth noting that this is just one example workflow, and the actual implementation may vary depending on the specific requirements and technologies used.
+
+## Appendix II
+
+### Reference process for the creation of the knowledge base
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### II.1 Overview
+
+The construction of the KB of the intelligent customer service system starts with a single domain, and then expands to multiple domains.
+
+![Flowchart illustrating the basic process of a KB establishment. The steps are: 1. Collect and sort out the required knowledge materials in the intelligent customer service system; 2. Establish a single domain KB; 3. Cross-domain knowledge integration; 4. General KB and Cross-domain KB; 5. Intelligent customer service system KB.](a24e89a6fe9bb70c83f8bf5202baba95_img.jpg)
+
+```
+graph TD; A[Collect and sort out the required knowledge materials in the intelligent customer service system] --> B[Establish a single domain KB]; B --> C[Cross-domain knowledge integration]; C --> D[(General KB)]; C --> E[(Cross-domain KB)]; D --> F[(Intelligent customer service system KB)]; E --> F
+```
+
+Flowchart illustrating the basic process of a KB establishment. The steps are: 1. Collect and sort out the required knowledge materials in the intelligent customer service system; 2. Establish a single domain KB; 3. Cross-domain knowledge integration; 4. General KB and Cross-domain KB; 5. Intelligent customer service system KB.
+
+F.748.25(23)
+
+**Figure II.1 – Basic process of a KB establishment**
+
+Figure II.1 describes a basic process example for a knowledge base (KB) creation. First, a single-domain KB is established through natural language technologies such as entity recognition and relation extraction. Then, through knowledge mapping and fusion technologies, cross-domain knowledge integration is realized, and then the general domain KB and cross-domain KB are established.
+
+### II.2 Single domain KB establishment
+
+The intelligent customer service system has accumulated a large number of fuzzy and inaccurate knowledge in the process of use. The existence of these knowledge points is a large amount of incomplete, noisy, fuzzy, random practical application data (involving natural language technology). Therefore, the process of extracting hidden but potentially useful information and knowledge is very important and necessary, so that much historical data that could not be understood before can be used.
+
+The process of single domain knowledge mining is divided into the following steps:
+
+- Keyword libraries construction: Based on the NLP technology, discovering concepts in the domain through entity recognition and syntactic analysis technologies, mining the relationships between concepts, and automatically or semi-automatically constructing domain semantic lexicons based on semantic network technology;
+- Construction of a candidate object: Semantic understanding and induction of concepts in the semantic lexicon, and construction of a candidate object;
+- Submit for manual review: This semi-automatic knowledge mining method effectively speeds up the process of domain KB construction and reduces costs.
+
+### **II.3 Cross-domain KB establishment**
+
+Based on a KB of a single domain, knowledge of a new domain is gradually integrated. Make the KB adjust with the integration of new domain knowledge, adapt it to the requirements of the corresponding multiple domains, and finally realize the integration of a cross-domain knowledge.
+
+- Integration of words in various fields: Merge common words that overlap in the KB of various fields and classify professional words in vertical fields according to different fields.
+- Combination of object classes: To integrate knowledge of the new domain into the existing KB. Firstly, it is necessary to find similar object classes in the existing knowledge by the method of object class matching, and then merge. Object class merging is to integrate multiple object classes together, eliminate overlapping parts and remove inconsistent parts, so that the new object class is more reasonable and can better express the concept of these merged object classes.
+- Combination of knowledge: In addition to the specific professional knowledge content of each domain, there is also a part of knowledge that is common to multiple domains. The general knowledge content in various domains needs to be extracted to form a general KB.
+
+## Bibliography
+
+- [b-ITU-T F.746.3] Recommendation ITU-T F.746.3 (2015), *Intelligent question answering service framework*.
+- [b-ITU-T F.749.13] Recommendation ITU-T F.749.13 (2021), *Framework and requirements for civilian unmanned aerial vehicle flight control using artificial intelligence*.
+- [b-ITU-T H.625] Recommendation ITU-T H.625 (2017), *Architecture for network-based speech-to-speech translation services*.
+- [b-ITU-T P.10/G.100] Recommendation ITU-T P.10/G.100 (2017) – Amendment 1 (2019), *New definitions for inclusion in Recommendation ITU-T P.10/G.100. Vocabulary for performance, quality of service and quality of experience Amendment 1*.
+- [b-ITU-T P.800] Recommendation ITU-T P.800 (1996), *Methods for subjective determination of transmission quality*.
+- [b-ITU-T Y.2091] Recommendation ITU-T Y.2091 (2011), *Terms and definitions for next generation networks*.
+- [b-IEEE 2807] IEEE 2807-2022, *IEEE Standard for Framework of Knowledge Graphs*.  
+<<https://standards.ieee.org/ieee/2807/7525/>>
+- [b-ISO 9241-154] ISO 9241-154:2013, *Ergonomics of human-system interaction – Part 154: Interactive voice response (IVR) applications*.  
+<[https://www.iso.org/standard/52172.html#:~:text=ISO%209241%2D154%3A2013%20gives,ASR\)%20as%20the%20input%20mechanism.](https://www.iso.org/standard/52172.html#:~:text=ISO%209241%2D154%3A2013%20gives,ASR)%20as%20the%20input%20mechanism.)>
+
+
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.748.27-202401-I_PDF-E/raw.md b/marked/F/T-REC-F.748.27-202401-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..e4a549292a5bca92f3911229a1454703afc41547
--- /dev/null
+++ b/marked/F/T-REC-F.748.27-202401-I_PDF-E/raw.md
@@ -0,0 +1,614 @@
+
+
+# Recommendation **ITU-T F.748.27 (01/2024)**
+
+SERIES F: Non-telephone telecommunication services  
+Multimedia services
+
+---
+
+## **Framework and requirements for the construction of 3D intelligent driven digital human application systems**
+
+![ITU logo](390120de4fe440c42fea8154fcaad334_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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.748.27
+
+# Framework and requirements for the construction of 3D intelligent driven digital human application systems
+
+## Summary
+
+Recommendation ITU-T F.748.27 outlines the framework and requirements for the construction of three dimensional (3D) intelligent driven digital human application systems. With the advancement of modelling, driving, rendering and interactive technologies, an increasing number of new services and applications involving 3D intelligent driven digital humans are emerging. It defines the concept, related terms, and fundamental functions of 3D intelligent driven digital human to specify the framework of 3D intelligent driven digital human application systems, including image generation, speech generation, animation generation, interaction processing, multimodal input and output modules with its specified functions and construction requirements. In addition, the Appendix presents some use cases of the workflow of 3D intelligent driven digital human.
+
+### History\*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.748.27 | 2024-01-13 | 16          | 11.1002/1000/15761 |
+
+### Keywords
+
+3D intelligent driven digital human, animation generation module, image generation, interactive processing module, multimodal input module, multimodal output module, speech generation module.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                                                             | 2  |
+| 4          | Abbreviations and acronyms .....                                                                      | 2  |
+| 5          | Conventions .....                                                                                     | 2  |
+| 6          | Overview of 3D intelligent driven digital human application systems .....                             | 3  |
+| 7          | Framework of 3D intelligent driven digital human application systems.....                             | 3  |
+| 8          | Requirements for the construction of 3D intelligent driven digital human application systems.....     | 5  |
+| 8.1        | Image generation .....                                                                                | 5  |
+| 8.2        | Speech generation.....                                                                                | 6  |
+| 8.3        | Animation generation .....                                                                            | 6  |
+| 8.4        | Interactive processing.....                                                                           | 7  |
+| 8.5        | Multimodal input.....                                                                                 | 8  |
+| 8.6        | Multimodal output.....                                                                                | 9  |
+| Appendix I | – Use cases of workflow of 3D intelligent driven digital human application systems.....               | 11 |
+| I.1        | Use case of image generation process for 3D intelligent driven digital human application systems..... | 11 |
+| I.2        | Use case of 3D intelligent driven digital human application systems for news broadcasting .....       | 11 |
+| I.3        | Use case of 3D intelligent driven digital human application systems for intelligent assistant .....   | 12 |
+|            | Bibliography.....                                                                                     | 13 |
+
+
+
+## Framework and requirements for the construction of 3D intelligent driven digital human application systems
+
+## 1 Scope
+
+This Recommendation specifies the framework and requirements for the construction of three dimensional (3D) intelligent driven digital human application systems.
+
+The scope of this Recommendation includes:
+
+- Overview of 3D intelligent driven digital human application systems;
+- Framework of 3D intelligent driven digital human application systems;
+- Requirements of 3D intelligent driven digital human application systems.
+
+## 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.748.15] Recommendation ITU-T F.748.15 (2022), *Framework and metrics for digital human application systems*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 application system** [b-ISO/IEC TR 10032]: A collection of application processes which utilizes the services provided by the human-computer interface, communications facility, and data management system to perform the processing necessary to meet the requirements of the information system.
+
+**3.1.2 digital human** [ITU-T F.748.15]: A computer application that integrates the technologies of computer graphics, computer vision, intelligent speech and natural language processing. It can be used for digital content generation and human-computer interaction to help improve content production efficiency and user experience.
+
+**3.1.3 intelligent driven digital human** [ITU-T F.748.15]: The digital human is driven by a computer system to automatically complete a series of actions by technical means, including text-driven, audio-driven and video-driven.
+
+**3.1.4 text-to-speech synthesis (TTS)** [b-ITU-T P.10]: A TTS process generates a speech signal from text codes. It is usually composed of 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 synthesizer itself which generates the audible speech.
+
+### 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 3D intelligent driven digital human:** An intelligent driven digital human whose graphic content contains information about x, y and z dimensions.
+
+**3.2.2 3D manually modelling:** A modelling method based on specialized three-dimensional (3D) modelling software that manually constructs 3D geometric, material and texture information.
+
+**3.2.3 3D scanning modelling:** A modelling method based on three-dimensional (3D) measurements technology that collects geometric, material, and texture information to reconstruct the object.
+
+**3.2.4 3D intelligent modelling:** A modelling method based on computer vision technology for automatically reconstructing 3D geometric, material, and texture of objects based on two-dimensional images.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                              |
+|------|------------------------------|
+| 3D   | Three Dimensional            |
+| AAC  | Advanced Audio Coding        |
+| ALAC | Apple Lossless Audio Codec   |
+| AO   | Ambient Occlusion            |
+| APE  | Monkey's Audio (format)      |
+| AR   | Augmented Reality            |
+| CNN  | Convolutional neural network |
+| CPU  | Central Processing Unit      |
+| DCC  | Digital Content Creation     |
+| FBX  | FilmBoX                      |
+| FLAC | Free Lossless Audio Codec    |
+| GPU  | Graphics Processing Unit     |
+| IK   | Inverse Kinematics           |
+| LSTM | Long Short-Term Memory       |
+| MA   | Maya ASCII                   |
+| MP3  | MPEG-1 Audio Layer 3         |
+| OBJ  | Object                       |
+| PBR  | Physically Based Rendering   |
+| RNN  | Recurrent Neural Network     |
+| VR   | Virtual Reality              |
+| WAV  | Waveform Audio File Format   |
+
+## 5 Conventions
+
+In this Recommendation:
+
+- The keywords "**is required**" 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.
+
+## 6 Overview of 3D intelligent driven digital human application systems
+
+The 3D intelligent driven digital human is a stereoscopic anthropomorphic image driven by digital technology. It visualizes the digital identity and can replace real people for content production and simple interaction automatically. This technology has found extensive applications in various sectors, including finance, education, media, and social networking. For instance, 3D intelligent driven digital human for news broadcasting can automatically complete the production and output of news video according to a simple manuscript, which can meet the needs of video release on different platforms, greatly improving the production efficiency of media news.
+
+As the 3D intelligent driven digital human evolves into an intelligent assistant, it can provide answers and product recommendations to customers. In addition to one-way content delivery, it can engage in two-way interactions. Therefore, 3D intelligent driven digital human is an important part of the interactive system in the future and will become one of the main forces of value production in the virtual world.
+
+## 7 Framework of 3D intelligent driven digital human application systems
+
+Based on the framework proposed in Figure 1 of [ITU-T F.748.15]. For the construction of 3D intelligent driven digital human application systems, this Recommendation proposes a framework of 3D intelligent driven digital human application systems in Figure 1. It clarifies the requirements for the construction of 3D intelligent driven digital human in terms of image generation, speech generation, animation generation, interactive processing, multimodal input and multimodal output. The coloured boxes in it indicate the contents concerned in this Recommendation. And the dashed box indicates that this section is optional.
+
+![Figure 1: Framework of 3D intelligent driven digital human application systems. The diagram shows a flow from top to bottom: Image generation (Binding: Facial binding, Body binding; Modelling), Speech generation (Text-to-speech synthesis), Animation generation (Intelligent-driven), and Interactive processing (Decision module, Perception module). The Interactive processing module is enclosed in a dashed box. On the right, the Multimodal output module (Real-time rendering, Offline rendering, Rendering engine, Rendering server) receives input from the Animation generation module. The Multimodal input module (Multimodal input) sends input to the Interactive processing module. The Interactive processing module sends output to the Animation generation module. The label F.748.27(24) is at the bottom right.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg)
+
+Figure 1: Framework of 3D intelligent driven digital human application systems. The diagram shows a flow from top to bottom: Image generation (Binding: Facial binding, Body binding; Modelling), Speech generation (Text-to-speech synthesis), Animation generation (Intelligent-driven), and Interactive processing (Decision module, Perception module). The Interactive processing module is enclosed in a dashed box. On the right, the Multimodal output module (Real-time rendering, Offline rendering, Rendering engine, Rendering server) receives input from the Animation generation module. The Multimodal input module (Multimodal input) sends input to the Interactive processing module. The Interactive processing module sends output to the Animation generation module. The label F.748.27(24) is at the bottom right.
+
+**Figure 1 – Framework of 3D intelligent driven digital human application systems**
+
+- **Image generation module:** Generate a drivable 3D model based on modelling and binding. Modelling can use a variety of modelling methods to generate the 3D model of the 3D intelligent driven digital human. Binding the facial and body of the 3D model can achieve subsequent control of it.
+- **Speech generation module:** A module that can enable 3D intelligent driven digital human to speak. Speech synthesis can generate speech based on the algorithms.
+- **Animation generation module:** A module that generates the facial expression and body movement of a 3D intelligent driven digital human. Based on the different driving methods, animation generation modules can be divided into voice-driven, image-driven, and text-driven.
+- **Interactive processing module:** Realizing the interactive ability of the 3D intelligent driven digital human to analyse multimodal input. The perception module realizes the recognition of data from the multimodal input. The decision module realizes the comprehension of user intention and generates decision-making data of 3D intelligent driven digital human. This module is optional.
+- **Multimodal input module:** A module that is used to receive input, including text, voice, image, etc.
+- **Multimodal output module:** A module that presents the output to the user. Including real-time rendering and offline rendering. The rendering capability of this module relies on the rendering engine and the rendering server.
+
+## **8 Requirements for the construction of 3D intelligent driven digital human application systems**
+
+### **8.1 Image generation**
+
+#### **8.1.1 Modelling**
+
+The modelling of 3D intelligent driven digital human should meet the following requirements:
+
+**GM-01:** It is required to generate a 3D model of a digital human.
+
+**GM-02:** It is required that the 3D model supports 3D visualization.
+
+**GM-03:** It is required to enable the creation of various styles of 3D models, such as 3D cartoons, 3D realistic, 3D ultra-realistic, etc.
+
+**GM-04:** It is required that the 3D model includes basic information of the digital human, including the head, limbs, hair, clothing, etc.
+
+**GM-05:** It is required that the 3D model includes geometric, material and texture information.
+
+**GM-06:** It is required to support multiple physically based rendering (PBR) materials for the 3D model, such as albedo, roughness, normal, displacement, ambient occlusion (AO), cavity, curvature, wrinkle and so on.
+
+**GM-07:** It is required that the transition between the key features of the 3D model should be natural and the deformation should be realistic.
+
+NOTE – The transition between the key features of the 3D model refers to changes between each component of a digital human, such as the head and body, the foot and leg, etc.
+
+**GM-08:** It is required to provide support for generating 3D models in multiple formats, such as FilmBoX (FBX), object (OBJ), Maya ASCII (MA), etc.
+
+**GM-09:** It is required for the 3D model to be compatible with various rendering engines.
+
+**GM-10:** It is required for the 3D model to be compatible with various digital content creation (DCC) software.
+
+**GM-11:** It is required to support different modelling methods to build 3D models, including 3D manual modelling, 3D scanning modelling, 3D intelligent modelling, etc.
+
+#### **8.1.2 Binding**
+
+The generated 3D model of a digital human is static, in order to drive its motion it is required to perform facial binding and body binding of it. Binding for a 3D digital human needs to follow one specification, and when a possible restriction on the binding of a 3D digital human is defined, the animations designed for one 3D digital human are deployable to another 3D digital human, see clause 4.8 of [b-ISO/IEC 19774-1].
+
+The facial binding should meet the following requirements:
+
+**FB-01:** It is required to support the binding of the facial bones and facial key feature points of the 3D digital human model.
+
+**FB-02:** It is required to support the splitting and production of the corresponding expressions of the 3D digital human model.
+
+**FB-03:** It is required to support the corresponding construction of the facial control system in the later stage.
+
+**FB-04:** It is required to support real-time driving and manual correction.
+
+Body binding should meet the following requirements:
+
+**BB-01:** It is required to support the construction of the human skeleton of the 3D digital human model.
+
+**BB-02:** It is required to support the binding of 12 joint points of the human body and 5 key points of the head of the 3D digital human model.
+
+**BB-03:** It is required to support the creation of the control system of each part of the human body of the 3D digital human model.
+
+**BB-04:** It is required to support the skin painting of the 3D digital human model.
+
+**BB-05:** It is required to support the muscle modification or muscle and skeleton system construction of the 3D digital human model.
+
+**BB-06:** It is recommended to support the loading of the full-body human inverse kinematics (IK) skeleton.
+
+### 8.2 Speech generation
+
+Speech generation is based on text-to-speech synthesis and it should meet the following requirements:
+
+**SG-01:** It is required to support the synthesis of audio of different genders, such as male or female voices.
+
+**SG-02:** It is required to support the synthesis of audio of different ages, such as children, youth, and elderly voices, etc.
+
+**SG-03:** It is required to support the synthesis of audio with different emotions, such as neutral, sad, happy voices, etc.
+
+**SG-04:** It is required to support the synthesis of the audio in multiple languages, such as Chinese, English, Japanese, Korean, Spanish, etc.
+
+**SG-05:** It is required to support multiple voice styles for different scenarios, such as news, entertainment, emotional, information, and promotional scenarios.
+
+**SG-06:** It is required to support voice-changing that can convert the voice of one person into a specific voice.
+
+**SG-07:** It is required to support the synthesis of singing audios.
+
+**SG-08:** It is recommended to support audio editing capabilities, including speed, tone, volume, and emotional adjustment.
+
+**SG-09:** It is recommended to support text labels for correcting errors and improving the synthesis effect, such as supporting the editing of homophones, symbols, and other elements in the text.
+
+**SG-10:** It is required to support the synthesis of audio in multiple formats to be compatible with different rendering engines, such as waveform audio file format (WAV), free lossless audio codec (FLAC), Monkey's audio (format) (APE), Apple lossless audio codec (ALAC), MPEG-1 audio layer 3 (MP3), advanced audio coding (AAC), Ogg Vorbis, etc.
+
+NOTE – See [b-Audio formats] for a general description of common audio file formats.
+
+**SG-11:** It is required to support the generation of audio time series information and segmented speech fragments while synthesizing the audio.
+
+### 8.3 Animation generation
+
+Animation generation can occur based on the user input text or in response to the text analysed from the user's input. In the latter case, when the user's input is an audio, a typical animation generation method involves the following steps: it is required to obtain the response text and feature information corresponding to the response text according to the audio input by the user. The feature information is blend shape and skeleton parameters used to indicate facial expressions and body motions of 3D digital human. Obtain the feature data corresponding to the response information based on the feature
+
+information. Then, it is required to generate dynamic images of 3D digital human corresponding to the response text according to the feature data.
+
+NOTE – Response information is obtained from the user's audio by interactive processing in clause 8.4.
+
+**AG-01:** It is required that the feature information includes at least one of the emotion information or pronunciation information.
+
+**AG-02:** It is required that the feature data includes at least one of the expression data or lip-shape data. The expression data is determined according to the first blend shape data and the first skeleton data corresponding to the emotion information; the lip-shape data is obtained according to the second blend shape data and the second skeleton data corresponding to the pronunciation information.
+
+**AG-03:** It is required that the skeleton data is determined according to the weighted sum of the initial skeleton data and multiple skeleton data components.
+
+**AG-04:** It is required to obtain the initial weight of the feature data according to the feature information.
+
+**AG-05:** It is required to randomly generate the actual weights of multiple key frames at the corresponding time within the initial weight and the value range defined according to the threshold. The value range includes values that are greater than the difference between the initial weight and the threshold and less than the sum of the initial weight and the threshold.
+
+**AG-06:** It is required that generating the dynamic images of 3D digital human is based on the multiple key frames: smoothing the weighted feature data corresponding to the adjacent key frames to generate non-key frames between the adjacent key frames; the dynamic images are generated in time order according to the key frames and non-key frames and their timestamps.
+
+**AG-07:** It is required to determine the timestamp of the feature data according to the feature information and to generate the actual weight of the corresponding time of the timestamp to generate the actual weight of the corresponding time of multiple key frames.
+
+### **8.4 Interactive processing**
+
+#### **8.4.1 Perception module**
+
+Perception module needs to realize the recognition of multimodal input data by 3D digital human based on the algorithm models. It supports 3D intelligent driven digital human's perception of the user's input.
+
+**PM-01:** It is required to support the recognition of at least one data type, such as text, audio, video, touch/sensing data, etc.
+
+**PM-02:** It is required to support at least one type of recognition capability, such as text recognition, speech recognition, image recognition, etc.
+
+**PM-03:** It is recommended to support text recognition, such as text intention recognition, semantic recognition, etc.
+
+**PM-04:** It is recommended to support speech recognition, such as speech-to-text recognition, voiceprint recognition, age and gender recognition, etc. In some cases, it is required to support specific person speech recognition, non-specific person speech recognition, multi-person speech recognition, etc.
+
+**PM-05:** It is recommended to support image recognition, such as face recognition, gesture recognition, posture recognition, facial emotion recognition, scene recognition, place recognition, etc. In some cases, it is required to support specific person image recognition, non-specific person image recognition, multi-person image recognition, etc.
+
+**PM-06:** It is required to support specific types of 3D digital human image editing. On a limited set, according to the text commands, 3D digital human support text commands are to be editable in dimensions such as hair colour, skin colour and hairstyle.
+
+**PM-07:** It is required to support specific types of 3D digital human action and expression driving. On a limited set, according to the text instructions, audio instructions or video instructions, the 3D digital human can respond to actions and expressions that conform to the instructions.
+
+**PM-08:** It is required to support algorithm models and model structures for various tasks, such as convolutional neural network (CNN), long short-term memory (LSTM), recurrent neural network (RNN), etc.
+
+**PM-09:** It is required a high recognition accuracy rate.
+
+**PM-10:** It is required that the algorithm models can update iteratively.
+
+**PM-11:** It is required for the algorithm models to be robust against abnormal data.
+
+**PM-12:** It is required for the algorithm models to be adapted to different devices, such as servers, hosts, terminal devices, etc.
+
+#### **8.4.2 Decision module**
+
+Decision-making module needs to realize the analysis of perception data by 3D digital human based on the AI model. It includes the following requirements:
+
+**DM-01:** It is required to support the knowledge matching ability of the 3D digital human, such as natural language processing, knowledge graph, dialogue management, big data search, recommendation engine, etc.
+
+**DM-02:** It is required to support the generation of response text based on intent understanding and business knowledge matching.
+
+**DM-03:** It is required to support algorithm models and model structures for various tasks, such as CNN, LSTM, RNN, etc.
+
+**DM-04:** It is required to support multi-decision algorithms that integrate intent understanding and business knowledge matching to realize linkage decision-making.
+
+**DM-05:** It is required a high model recognition accuracy rate.
+
+**DM-06:** It is required that the model can update iteratively.
+
+**DM-07:** It is required for the model to be robust against erroneous data.
+
+**DM-08:** It is required for the model to be adapted to different devices, such as servers, hosts, terminal devices, etc.
+
+### **8.5 Multimodal input**
+
+The input data should meet the following requirements:
+
+**MI-01:** It is required to support at least one of the input data types, such as text, audio, image, etc.
+
+**MI-02:** It is required to support multiple types of input text, such as entered text, imported text files, text converted by third-party systems, etc.
+
+**MI-03:** It is required to support multiple types of input audio, such as audio recorded by real people, synthetic audio, audio that has been processed by voice change, etc.
+
+**MI-04:** It is required to support multiple types of input video, such as recorded video, live video streams, etc.
+
+**MI-05:** It is required to support multiple data formats, such as structured data, semi-structured data, and unstructured data.
+
+**MI-06:** It is recommended to support touch/sensing data input and other types of data input.
+
+### **8.6 Multimodal output**
+
+#### **8.6.1 Real-time rendering**
+
+Real-time rendering should meet the following requirements:
+
+**RR-01:** It is required to support the rendering of the images while performing the 3D image calculation.
+
+**RR-02:** It is required to support multi-resolution rendering of 3D digital human.
+
+**RR-03:** It is required to support the rendering of fusion materials, lighting and physical characteristics.
+
+**RR-04:** It is required to support the transmission of rendering results in the form of video streams.
+
+**RR-05:** It is required to support the rendering quality output of multiple resolutions.
+
+**RR-06:** It is recommended to support real-time adjustment of resolution.
+
+**RR-07:** It is required to have real-time control and real-time interaction capabilities, and low real-time feedback delay of the screen.
+
+**RR-08:** It is required to support real-time face control, real-time body control, real-time hair control and other functions.
+
+**RR-09:** It is recommended to support multi-channel concurrent rendering and can control multiple users in real-time.
+
+**RR-10:** It is recommended to support compatibility with a variety of terminal devices, such as flat panel display devices such as mobile phones, tablets, and computers, virtual reality (VR) / augmented reality (AR) devices and holographic projection devices, etc.
+
+#### **8.6.2 Offline rendering**
+
+Offline rendering should meet the following requirements:
+
+**OR-01:** It is required to support the ability to edit 3D digital human images and voices, such as designing and adjusting their appearance, clothing, and actions according to the application scene to achieve better visual effects.
+
+**OR-02:** It is required to support ultra-high-precision rendering of 3D digital humans.
+
+**OR-03:** It is required to support fine rendering that integrates materials, lighting and physical characteristics.
+
+**OR-04:** It is required to support the rendering quality output of multiple resolutions.
+
+**OR-05:** It is required to support compatibility with a variety of terminal devices, such as mobile phones, tablets, computers and other flat panel display devices, VR devices, and holographic projection devices.
+
+#### **8.6.3 Rendering engine**
+
+For the intelligent driving of 3D digital human, the rendering engine should meet the following requirements:
+
+**RE-01:** It is required to support the import of commonly used 3D digital human model file formats, such as object (OBJ), FilmBoX (FBX), Maya ASCII (MA), etc.
+
+NOTE – See [b-3D formats] for a general description of common 3D file formats.
+
+**RE-02:** It is required to support the adjustment of 3D digital human models, such as face, skin, hair, body, etc.
+
+**RE-03:** It is required to support not less than one kind of operating system, such as Windows, Linux, etc.
+
+**RE-04:** It is required to support offline and real-time rendering.
+
+**RE-05:** It is required to support central processing unit (CPU) / graphics processing unit (GPU) rendering.
+
+**RE-06:** It is required to support cloud rendering.
+
+**RE-07:** It is required to support end-to-end rendering.
+
+**RE-08:** It is recommended to support GPU rendering acceleration.
+
+**RE-09:** It is recommended to support new rendering technologies such as pixel streaming and ray tracing.
+
+#### **8.6.4 Rendering server**
+
+Rendering server is utilized to deliver the rendering engine ensuring high-performance services to meet the rendering requirements of high-precision image quality in 3D intelligent driven digital human.
+
+**RS-01:** It is recommended to use a high-performance server with 64-bit system architecture and multiple CPUs/GPUs.
+
+**RS-02:** It is recommended to adopt the cluster deployment method and cooperate with the load balancing mechanism to achieve high availability of the rendering service.
+
+**RS-03:** It is recommended to have scalability, and scale performance smoothly by adding server instances.
+
+## Appendix I
+
+### Use cases of workflow of 3D intelligent driven digital human application systems
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### I.1 Use case of image generation process for 3D intelligent driven digital human application systems
+
+Figure I.1 depicts the image generation process for 3D intelligent driven digital human application systems.
+
+- The first step is to generate a 3D model of an intelligent driven digital human. The modelling methods include 3D manually modelling, 3D scanning modelling and 3D intelligent modelling, etc. The 3D manually modelling uses modelling software to generate the 3D model. For 3D scanning modelling, the generation of the 3D model relies on a scanning modelling system to capture facial and body data. For 3D intelligent modelling, it realizes the construction of 3D models based on single frame images or video sequences.
+- The second step is to perform character binding on the built 3D model, including the body binding and facial binding.
+
+![Flowchart of the image generation process for 3D intelligent driven digital human application systems.](21ad58fee90f2be50708ff541d225507_img.jpg)
+
+```
+graph BT; subgraph Modelling; M["3D manually modelling/ 3D scanning modelling/ 3D intelligent modelling"]; end; subgraph Binding; B["Body binding", "Facial binding"]; end; Modelling --> Binding;
+```
+
+The diagram illustrates the image generation process. It consists of two main stages: 'Modelling' and 'Binding'. The 'Modelling' stage includes three methods: '3D manually modelling/ 3D scanning modelling/ 3D intelligent modelling'. An arrow points from the 'Modelling' stage to the 'Binding' stage. The 'Binding' stage includes 'Body binding' and 'Facial binding'. The label 'F.748.27(24)' is located at the bottom right of the diagram.
+
+Flowchart of the image generation process for 3D intelligent driven digital human application systems.
+
+Figure I.1 – Image generation process for 3D intelligent driven digital human application systems
+
+### I.2 Use case of 3D intelligent driven digital human application systems for news broadcasting
+
+![Flowchart of the workflow for 3D intelligent driven digital human application systems for news broadcasting.](29f586959675cafdf81cf934954908eb_img.jpg)
+
+```
+graph BT; subgraph Input; MI["Multimodal input"]; end; subgraph Generation; SG["Speech generation<br/>Speech synthesis"]; AG["Animation generation<br/>Text-driven"]; end; subgraph Output; MO["Multimodal output"]; end; Input --> SG; Input --> AG; SG --> MO; AG --> MO;
+```
+
+The diagram illustrates the workflow for 3D intelligent driven digital human application systems for news broadcasting. It starts with 'Multimodal input' at the bottom. This input is processed through two parallel paths: 'Speech generation' (which includes 'Speech synthesis') and 'Animation generation' (which includes 'Text-driven'). Both paths lead to 'Multimodal output' at the top. The label 'F.748.27(24)' is located at the bottom right of the diagram.
+
+Flowchart of the workflow for 3D intelligent driven digital human application systems for news broadcasting.
+
+Figure I.2 – Workflow of 3D intelligent driven digital human application systems for news broadcasting
+
+3D intelligent driven digital human application systems for news broadcasting need to automatically complete content production based on the simple text input.
+
+Figure I.2 depicts the workflow of 3D intelligent driven digital human application systems for news broadcasting.
+
+- First, input a text to the multimodal input module.
+- Second, the speech generation module and animation module works based on the text data from the multimodal input module to generate corresponding speech and animation of 3D intelligent driven digital human.
+- Finally, the multimodal output module does the synthesis and output of the speech and animation.
+
+### I.3 Use case of 3D intelligent driven digital human application systems for intelligent assistant
+
+![Workflow diagram of 3D intelligent driven digital human application systems for intelligent assistant. The flow starts with 'Multimodal input' at the bottom, leading to 'Interactive processing' (containing 'Perception module' and 'Decision module'). From 'Interactive processing', the flow splits into 'Speech generation' (containing 'Speech synthesis') and 'Animation generation' (containing 'Voice-driven', 'Image-driven', and 'Text-driven'). Both modules lead to 'Multimodal output' at the top. A label 'F.748.27(24)' is present near the bottom right of the diagram.](dfe556fea00682b09a59427aaf72051c_img.jpg)
+
+```
+
+graph TD
+    MI[Multimodal input] --> IP[Interactive processing]
+    subgraph IP [Interactive processing]
+        PM[Perception module] --> DM[Decision module]
+    end
+    DM --> SG[Speech generation]
+    DM --> AG[Animation generation]
+    subgraph SG [Speech generation]
+        SS[Speech synthesis]
+    end
+    subgraph AG [Animation generation]
+        VD[Voice-driven]
+        ID[Image-driven]
+        TD[Text-driven]
+    end
+    SG --> MO[Multimodal output]
+    AG --> MO
+  
+```
+
+F.748.27(24)
+
+Workflow diagram of 3D intelligent driven digital human application systems for intelligent assistant. The flow starts with 'Multimodal input' at the bottom, leading to 'Interactive processing' (containing 'Perception module' and 'Decision module'). From 'Interactive processing', the flow splits into 'Speech generation' (containing 'Speech synthesis') and 'Animation generation' (containing 'Voice-driven', 'Image-driven', and 'Text-driven'). Both modules lead to 'Multimodal output' at the top. A label 'F.748.27(24)' is present near the bottom right of the diagram.
+
+**Figure I.3 – Workflow of 3D intelligent driven digital human application systems for intelligent assistant**
+
+3D intelligent driven digital human application systems for intelligent assistant should have the ability to automatically interact with users. For example, providing consulting, data query, business handling and other services.
+
+Figure I.3 depicts the workflow of 3D intelligent driven digital human application systems for intelligent assistant.
+
+- First, the multimodal input module allows multiple data types, such as voice, image, text, somatosensory data, touch data, etc.
+- Second, the intelligent driven model of the interactive processing module enables the 3D intelligent driven digital human to analyse external input and generate decision data for it.
+- Third, the animation generation module and speech generation module work according to the decision data. Among them, according to the different input types, animation generation can be divided into speech driven, image driven, text driven, and speech generation needs to rely on the speech synthesis technology. At the same time, the consistency of the speech and lips of the 3D intelligent driven digital human should be maintained.
+- Finally, speech and animation are synthesized and rendered in real time.
+
+## Bibliography
+
+- [b-ITU-T P.10] Recommendation ITU-T P.10/G.100 (2017), *Vocabulary for performance, quality of service and quality of experience*.
+- [b-ISO/IEC 19774-1] ISO/IEC 19774-1:2019, *Information technology – Computer graphics, image processing and environmental data representation – Part 1: Humanoid animation (HAnim) architecture*.  
+<<https://www.iso.org/standard/64788.html>>
+- [b-ISO/IEC TR 10032] ISO/IEC TR 10032:2003, *Information technology – Reference model of data management*.  
+<[https://www.iso.org/standard/38607.html#:~:text=ISO%2FIEC%20TR%2010032%3A2003%20definitions%20the%20ISO%20Reference%20Model.persistent%20data%20in%20information%20systems.](https://www.iso.org/standard/38607.html#:~:text=ISO%2FIEC%20TR%2010032%3A2003%20definitions%20the%20ISO%20Reference%20Model.persistent%20data%20in%20information%20systems.>)>
+- [b-3D formats] Wikipedia, *List of file formats, 3D graphics*.  
+<[https://en.wikipedia.org/wiki/List\\_of\\_file\\_formats#3D\\_graphics](https://en.wikipedia.org/wiki/List_of_file_formats#3D_graphics)>
+- [b-Audio formats] Wikipedia, *Audio file format*.  
+<[https://en.wikipedia.org/wiki/Audio\\_file\\_format](https://en.wikipedia.org/wiki/Audio_file_format)>
+
+
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.748.32-202410-I_PDF-E/raw.md b/marked/F/T-REC-F.748.32-202410-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..bcc1258f33ddd96610b25c42d1c16be0592a37e3
--- /dev/null
+++ b/marked/F/T-REC-F.748.32-202410-I_PDF-E/raw.md
@@ -0,0 +1,568 @@
+
+
+# Recommendation **ITU-T F.748.32 (10/2024)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+# --- **Requirements and architecture of artificial intelligence (AI)-based detection technologies for multimedia messages**
+
+![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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.748.32
+
+# Requirements and architecture of artificial intelligence (AI)-based detection technologies for multimedia messages
+
+## Summary
+
+Recommendation ITU-T F.748.32 specifies the requirements and architecture of artificial intelligence (AI)-based detection for multimedia messages, including the overall requirements, the functional architecture, detection strategy, detection procedure, as well as some additional considerations.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.748.32 | 2024-10-29 | 16          | 11.1002/1000/16187 |
+
+## Keywords
+
+AI, architecture, detection, multimedia message, requirements.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                           | 2    |
+| 6 AI-based detection framework .....          | 3    |
+| 7 Functional architecture .....               | 3    |
+| 7.1 Functional entities .....                 | 4    |
+| 7.2 Interfaces .....                          | 6    |
+| 8 Message feature algorithm.....              | 7    |
+| 8.1 Text feature algorithm .....              | 7    |
+| 8.2 Audio feature algorithm .....             | 8    |
+| 8.3 Video feature algorithm.....              | 8    |
+| 9 AI-based detection algorithm .....          | 8    |
+| 9.1 Text detection .....                      | 8    |
+| 9.2 Image detection .....                     | 8    |
+| 9.3 Audio detection .....                     | 9    |
+| 9.4 Video detection.....                      | 10   |
+| 9.5 File detection .....                      | 10   |
+| Bibliography.....                             | 11   |
+
+
+
+# Requirements and architecture of artificial intelligence (AI)-based detection technologies for multimedia messages
+
+## 1 Scope
+
+This Recommendation specifies the requirements and architecture of artificial intelligence (AI)-based detection technologies for multimedia messages, including the requirements of using AI technologies to detect text, image, audio, video, file and other types of multimedia message as well as the architecture of general detection signalling, procedure and system.
+
+The scope of this Recommendation includes:
+
+- AI-based detection architecture, including the typical architecture of the detection system, functional components and interfaces;
+- Requirements of AI-based detection methods for different kinds of multimedia messages;
+- Requirements of detection strategies used in reference architecture;
+- Requirements of detection procedure.
+
+## 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 (V15) (2024), *Advanced video coding for generic audiovisual services*.
+
+[IETF RFC 6151] IETF RFC 6151 (2011), *Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms*.
+
+[IETF RFC 6234] IETF RFC 6234 (2011), *US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF)*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 optical character recognition (OCR)** [b-ISO/IEC 22989]: Conversion of images of typed, printed, or handwritten text into machine-encoded text.
+
+**3.1.2 rich communication suite** [b-GSMA RCC.07]: It is used to provide a framework for discoverable and interoperable advanced communication services and detailed specifications for a basic set of such advanced communication services. The functional requirements for these services and the framework components as well as their integration into the client's user experiences are described in [b-GSMA RCC.71].
+
+### 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 message as a platform:** A kind of messaging capabilities established by communication operators to enable industry clients to provide information services in various media formats to their users.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|         |                                              |
+|---------|----------------------------------------------|
+| 3GP     | 3GPP file format                             |
+| A2P     | Application to Person                        |
+| AAC     | Advanced Audio Coding                        |
+| AI      | Artificial Intelligence                      |
+| ADS     | AI-based Detection System                    |
+| AMR     | Adaptive Multi-Rate                          |
+| BS      | Business System                              |
+| ComParE | Computational Paralinguistics challenge      |
+| CNN     | Convolutional Neural Network                 |
+| GeMAPS  | Geneva Minimalistic Acoustic Parameter Set   |
+| JPEG    | Joint Photographic Experts Group             |
+| M4A     | MPEG-4 Audio                                 |
+| MD5     | Message Digest 5                             |
+| MFCC    | Mel-Frequency Cepstral Coefficients          |
+| MPEG-4  | Moving Pictures Experts Group-4              |
+| MP3     | Moving Picture Experts Group Audio Layer III |
+| OCR     | Optical Character Recognition                |
+| P2P     | Person to Person                             |
+| PNG     | Portable Network Graphics                    |
+| RNN     | Recurrent Neural Network                     |
+| SHA     | Secure Hash Algorithm                        |
+| WEBM    | WebMedia                                     |
+
+## 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 AI-based detection framework
+
+The IMT-2020 standards encourage the implementation of a rich communication suite (RCS) in networks. Multimedia messages represent a kind of service that complies with GSMA RCS UP standards, which instructs operators to develop and deploy advanced communication services for customer messages and industry messages.
+
+Since multimedia messages can support a variety of message types which are quite different from traditional ones, including text, image, audio, video, file and other potentially possible message types. On the one hand, it provides users and enterprises with more rich services, on the other side, it brings substantially more challenges and difficulties to message detection technologies. For example, message using message-as-a-platform to implement industry messages, which is an application to person (A2P) message, leads to much more complicated situations especially for message detection strategies.
+
+With a large development of AI technologies using neural networks and deep learning algorithms, it has been applied into many practical tasks of detection, classification and recognition. While facing lots of challenges for multimedia message detection, it is necessary to initiate a new standard on clarifying the requirements and framework of AI-based detection for multimedia messages, including the overall requirements, the general framework, recommended detection strategy, detection procedure, as well as some additional considerations.
+
+## 7 Functional architecture
+
+The architecture shown in Figure 7-1 consists of two systems, which are a business system (BS) and an AI-based detection system (ADS). ADS is a system which detects and determines whether a multimedia message contains any specific information by using different kinds of AI algorithms.
+
+A business system is developed by a carrier to provide various multimedia message services [b-GSMA RCC.07], [b-GSMA RCC.71], such as person to person (P2P) messages and A2P messages. With the aid of AI technologies, an ADS is used to detect and determinate whether a multimedia message contains any specific information.
+
+The functional architecture of ADS presented in Figure 7-1 consists of eight main components, namely, message access unit, message process unit, strategy detection unit, algorithm detection unit, message feature database, data analysis unit, detection result unit, and system management unit.
+
+![Functional architecture of ADS diagram showing the flow of messages and control signals between the Business system (BS) and the AI-based detection system (ADS).](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg)
+
+The diagram illustrates the functional architecture of the AI-based detection system (ADS). On the left, the Business system (BS) contains P2P and A2P components. It sends messages (Ma) to the Message access unit (MAU) within the ADS. The MAU sends messages (Mp) to the Message preprocess unit (MPU). The MPU sends messages (Ad) to the AI-based algorithm detection unit (AADU). The AADU sends detection results (Ar) to the Detection result unit (DRU). The DRU sends detection results (Rr) back to the BS. The System management unit (SMU) sends management signals (Sm, Sd, Am) to the Strategy detection unit (SDU). The SDU sends management signals (Fr) to the Message feature database (MFD). The MFD sends management signals (Mf) to the Data analysis unit (DAU). The DAU sends management signals (Da) to the DRU. The DRU sends management signals (Sr) to the AADU. The legend indicates that dashed lines represent Detection, solid lines represent Function, and dash-dot lines represent Management.
+
+Functional architecture of ADS diagram showing the flow of messages and control signals between the Business system (BS) and the AI-based detection system (ADS).
+
+**Figure 7-1 – Functional architecture of ADS**
+
+### 7.1 Functional entities
+
+#### 7.1.1 MAU: message access unit
+
+Message access unit (MAU) is used to receive both P2P and A2P messages from BS. It is recommended to support the functions of protocol conversion, message parsing, and message delivery for MAU.
+
+- Protocol transfer: converting the external transmission protocol used between BS and ADS to an internal protocol used in the ADS.
+- Message parsing: verifying the correctness of a received message, correctly parse the fields in the message, and obtain the message elements which could be texts, images, audios, videos, files and URLs.
+- Message delivery: support some delivery modes that include the following functional requirements.
+  - Balance: requests are uniformly sent to servers;
+  - Response priority: a request is sent to a server giving the first response;
+  - Message type: the request containing different message types is sent to the corresponding server;
+  - Server performance: the number of requests is proportional to the performance of the server. The higher the performance a server has, the more requests it receives.
+
+#### 7.1.2 MPU: message preprocess unit
+
+Message preprocess unit (MPU) is used to preprocess the message from MAU. It is recommended to support the functions of number location query, user rank query, and special symbol elimination.
+
+- Number geo-location query: identifying the geographic locations of both calling and called numbers.
+- User rank query: inquiring about the user rank in terms of service plan, payment credit, and communication authority.
+- Special symbol elimination: realizing the function of finding and eliminating some special symbols.
+
+#### **7.1.3 SDU: strategy detection unit**
+
+Strategy detection unit (SDU) is used to detect whether the message is specific or not by using different kinds of strategies that may include block list, keyword matching, message fingerprint (cryptographic hash) and behaviour monitor.
+
+- a) Block list: using a block list to identify users who have sent a specific message.
+- b) Keyword matching: using regular expression to search whether the specific keyword exists in the text message.
+- c) Message fingerprint: using fingerprint to identify whether the message is specific or not, especially for image, audio and video messages.
+- d) Behaviour monitor: monitoring the behaviour that includes the send-and-receive frequency, message throughput.
+
+#### **7.1.4 MFD: message feature database**
+
+Message feature database (MFD) is a fingerprint-like feature database of a specific message for different data types. It is recommended to support the functions of calculating, updating and storing the fingerprint-like feature of specific messages.
+
+- a) Message fingerprint: using cryptographic hash algorithm to generate a unique string as a fingerprint.
+- b) Message fingerprint record: storing and maintaining a fingerprint database of specific messages.
+- c) Database update: updating the database at a certain time interval.
+
+#### **7.1.5 AADU: AI-based algorithm detection unit**
+
+Algorithm detection unit is required to use different kinds of AI-based algorithms to detect whether the message is specific or not. It is recommended to support several AI-based algorithms for analysing different types of content such as plain text, image, audio, video and file.
+
+- a) Text: support text classification, text clustering.
+- b) Image: support object detection, image classification, image matching, optical character recognition (OCR).
+- c) Audio: support audio classification, speech text conversion.
+- d) Video: support video content classification.
+- e) File: support extract the elements, such as text, image, audio, video, in the file, and then call the interface of the corresponding AI-based algorithm.
+
+#### **7.1.6 DRU: detection result unit**
+
+Detection result unit (DRU) is used to record detection results from SDU and ADU, and then send them to BS. It is required to extract the element in the specific message and make them into a specific sample library.
+
+#### **7.1.7 DAU: Data analysis unit**
+
+Data analysis unit (DAU) is used to count detection results that are recorded in the DRU. It is recommended to provide several statistical data given as follows.
+
+- a) total number of detected messages
+- b) total number of detected specific messages
+- c) number of specific messages detected by SDU
+- d) number of specific messages detected by ADU
+- e) number of P2P messages with specific information
+
+- f) number of A2P messages with specific information
+- g) precision rate of text detection algorithm
+- h) precision rate of image detection algorithm
+- i) precision rate of audio detection algorithm
+- j) precision rate of video detection algorithm
+- k) precision rate of file detection algorithm
+
+#### 7.1.8 SMU: system management unit
+
+System management unit (SMU) is used to configure the parameters of SDU and ADU. It is recommended to support the following configurations:
+
+- a) Strategy configuration
+  - Block list: support the operation of adding and deleting the number or unique ID in the list
+    - Keyword: support the operation of adding and deleting keyword in the keyword library
+    - Message feature: support adding and deleting feature data in the MFD
+    - Behaviour: support modifying the send-and-receive frequency and the message throughput
+    - Strategy set: support adding and deleting the strategy item into the set
+- b) AI-based algorithm configuration:
+  - Model: support changing the AI-based algorithm model for text, image, audio and video detection
+  - Threshold: support modifying the threshold configured in the algorithm model to meet different detection criterion
+
+### 7.2 Interfaces
+
+#### 7.2.1 Interface Ma: BS-MAU
+
+Interface Ma is between the BS and the MAU.
+
+It is used to send both P2P and A2P messages from the BS to the MAU of ADS.
+
+#### 7.2.2 Interface Mp: MAU-MPU
+
+Interface Mp is between the MAU and the MPU.
+
+After protocol conversion, it is used to deliver messages from the MAU to the MPU in one of the delivery modes mentioned in clause 7.1.1c.
+
+#### 7.2.3 Interface Sd: MPU-SDU
+
+Interface Sd is between the MPU and the SDU.
+
+It is used to send message elements of different data types from the MPU to the SDU.
+
+#### 7.2.4 Interface Fr: SDU-MFD
+
+Interface Fr is between the SDU and the MFD.
+
+It is used to send the message fingerprint request from the SDU to the MFD, and then receive the response.
+
+#### 7.2.5 Interface Sr: SDU-DRU
+
+Interface Sr is between the SDU and the DRU.
+
+It is used to send the strategy detection result from the SDU to the DRU.
+
+#### **7.2.6 Interface Ad: SDU-ADU**
+
+Interface Ad is between the SDU and the AADU.
+
+It is used to send the message elements of different data types from the SDU to the AADU.
+
+#### **7.2.7 Interface Ar: AADU-DRU**
+
+Interface Ar is between the AADU and the DRU.
+
+It is used to send the AI-based algorithm detection result from the AADU to the DRU.
+
+#### **7.2.8 Interface Da: DRU-DAU**
+
+Interface Da is between the DRU and the DAU.
+
+It is used to get detected results from the DRU to the DAU in order to make analysis and statistics.
+
+#### **7.2.9 Interface Mf: DRU-MFD**
+
+Interface Mf is between the DRU and the MFD.
+
+It is used to send the specific message from the DRU to the MFD to calculate the fingerprint and update the MFD.
+
+#### **7.2.10 Interface Sm: SMU-SDU**
+
+Interface Sm is between the SMU and the SDU.
+
+It is used to send the strategy configurations from the SMU to the SDU.
+
+#### **7.2.11 Interface Am: SMU-AADU**
+
+Interface Am is between the SMU and the AADU.
+
+It is used to send the AI-based algorithm configurations from the SMU to the AADU.
+
+#### **7.2.12 Interface Rr: DRU-BS**
+
+Interface Rr is between the DRU and the BS.
+
+It is used to send the detected results of each P2P and A2P message from the DRU to the BS.
+
+## **8 Message feature algorithm**
+
+To avoid the same or similar messages being redundantly detected within a short period, it is required to use the following algorithms to generate a unique feature for each message.
+
+For a text message, image message, audio message or video message, it is required to use a kind of hash algorithms, such as message digest 5 (MD5) [IETF RFC 6151] or secure hash algorithm (SHA) [IETF RFC 6234] to generate its unique feature.
+
+It is recommended to use some additional feature algorithms for a text message, audio message or video message.
+
+### **8.1 Text feature algorithm**
+
+If a text message is a webpage or a document, it is recommended to use MinHash [b-IEEE MinHash] and SimHash [b-IEEE SimHash] to generate its unique feature. The text of a webpage or a document is firstly parsed into many keywords. Each keyword has a weight that is proportional to its frequency of appearance. Then the feature of the text message is given by a feature matrix composed of the encoded keywords or a fixed length string calculated by a series of encoding methods.
+
+### 8.2 Audio feature algorithm
+
+It is recommended to use an audio parameter set to represent the feature of an audio message. The algorithm is used to extract the parameters, such as short-time zero-crossing rate of signal from the time domain, mel-frequency cepstral coefficients (MFCC) from the frequency domain and many other parameters. The audio parameter set commonly used in research and application fields are Geneva minimalistic acoustic parameter set (GeMAPS) [b-IEEE GeMAPS], and computational paralinguistics challenge (ComParE) [b-IEEE ComParE].
+
+### 8.3 Video feature algorithm
+
+It is recommended to use a key frame feature set to represent the feature of a video message. The algorithm is used to extract key frames from a video, such as I-frames [ITU-T H.264], and make a feature set of key frames calculated by MD5 [IETF RFC 6151] or SHA [IETF RFC 6234].
+
+## 9 AI-based detection algorithm
+
+As AI-based detection methods are used for different kinds of rich media types, it is suggested to analyse different requirements for each type of media.
+
+### 9.1 Text detection
+
+Text detection is used to infer whether the content of a text involves specific information.
+
+**TDR-01:** It is required to support text classification to implement text detection.
+
+**TDR-02:** High-performance real-time detection of messages (including emoticons) in text format is required to be supported, including emoji emoticons and symbolic emoticons.
+
+**TDR-03:** Segmented real-time detection or combined real-time detection for MSRP long message is required to be supported.
+
+**TDR-04:** Real-time detection of uppercase and lowercase letters and mixed alphanumeric characters in the text is required to be supported.
+
+**TDR-05:** Detection of website link in text is required to be supported.
+
+The algorithm procedure of text classification is given as follows.
+
+- a) Split a text into words or phrases
+- b) Extract the features of each word or phrase by using convolutional neural network (CNN) or recurrent neural network (RNN) based algorithms
+- c) Concatenate all features to form a feature matrix
+- d) Calculate the probability of the text involving specific information by using an inference model.
+
+### 9.2 Image detection
+
+Image detection is used to infer whether the content of an image involves specific information.
+
+**IDR-01:** It is required to support three types of AI-based algorithms, including object detection, image classification and OCR to implement image detection.
+
+**IDR-02:** The format of the image messages or files for detection is required to include at least Joint Photographic Experts Group (JPEG), JPG, portable network graphics (PNG), and BMP (panoramic picture included).
+
+**IDR-03:** Text or character recognition is required to be supported in real-time detection when there are text graphics in an image message.
+
+#### 9.2.1 Object detection
+
+The algorithm procedure of object detection is given as follows.
+
+- a) Extract the localization and semantic information of one or multiple interest targets in an image by using CNN based algorithm
+- b) Concatenate all features to form a feature matrix
+- c) Use a set of anchor boxes to predict the actual localization of one or multiple interest targets in an image
+- d) Calculate the probability of each detected target involving specific information by using an inference model.
+
+#### 9.2.2 Image classification
+
+The algorithm procedure of image classification is given as follows.
+
+- a) Extract the feature of an image by using CNN based algorithm
+- b) Concatenate the feature to form a feature vector
+- c) Calculate the probability of the image involving specific information by using an inference model.
+
+#### 9.2.3 OCR operation
+
+OCR is implemented by character pattern detection and character recognition. The algorithm procedure of OCR is given as following steps:
+
+- a) Use the step 1, 2, 3 of object detection in 9.2.1 to obtain the character pattern
+- b) Extract the sequence feature of the character pattern by using a RNN based algorithm
+- c) Extract the feature of each character by using CNN based algorithm
+- d) Calculate the probability of the character pattern involving specific information by using text detection.
+
+### 9.3 Audio detection
+
+Audio detection is used to infer whether the content of an audio involves specific information.
+
+**ADR-01:** The format of the audio messages or files for detection is required to include at least 3GPP file format (3GP), Moving Picture Experts Group audio layer III (MP3), Moving Pictures Experts Group-4 (MPEG-4) audio (M4A), advanced audio coding (AAC), and adaptive multi-rate (AMR).
+
+**ADR-02:** It is required to support two types of AI-based algorithms, including audio classification and speech text conversion.
+
+#### 9.3.1 Audio classification
+
+The algorithm procedure of audio classification is given as follows.
+
+- a) Split an audio file into a set of audio clips according to the processing requirements
+- b) Extract the features of the audio or audio clips by using a RNN based algorithm
+- c) Concatenate all features to form a feature matrix
+- d) Calculate the probability of the audio involving specific information by using inference model.
+
+#### 9.3.2 Speech text conversion
+
+The algorithm procedure of speech text conversion is given as follows.
+
+- a) Split a voice file into a set of audio clips according to voice interval if it is necessary
+
+- b) Extract the feature of each audio clip in a time domain and frequency domain to form a set of feature vectors
+- c) Evaluate the score of each feature vector by using acoustic model
+- d) Evaluate the probability that the voice corresponds to a possible phrase sequence by using a language model
+- e) Decode the phrase sequence and make the possible text representation by using an existing dictionary
+- f) Calculate the probability of the audio involving specific information by using text classification.
+
+### **9.4 Video detection**
+
+Video detection is used to infer whether the content of a video involves specific information.
+
+**VDR-01:** The format of the video messages or files for detection should be required to include at least MPEG4, 3GP, and WebMedia (WEBM).
+
+**VDR-02:** Text or character recognition is required to be supported in real-time detection when there are text graphics in video message.
+
+**VDR-03:** Frame sampling parameters in the video may be adjusted according to video size.
+
+**VDR-04:** It is required to support the algorithms introduced in clauses 9.2 and 9.3 to implement video detection.
+
+**VDR-05:** It is required to use either frames or audio of a video for video detection.
+
+**VDR-06:** It is recommended to use I-frames for image classification and audio feature for audio classification.
+
+**VDR-07:** It is recommended to use mixed feature extracted from a set of consecutive frames and their corresponding audio for video detection.
+
+### **9.5 File detection**
+
+File detection is used to infer whether the content of a file involves specific information.
+
+**FDR-01:** It is required to support the algorithms introduced in clauses 9.1 to 9.4 to implement file detection.
+
+## Bibliography
+
+- [b-ISO/IEC 22989] ISO/IEC 22989:2022, Information technology – Artificial intelligence – Artificial intelligence concepts and terminology.  
+<<https://www.iso.org/standard/74296.html>>
+- [b-GSMA RCC.07] GSMA RCC.07 (2022), *Rich Communication Suite - Advanced Communications Services and Client Specification*, Version 13.0, 19 December.  
+<<https://www.gsma.com/newsroom/wp-content/uploads/RCC.07-v13.0-1.pdf>>
+- [b-GSMA RCC.71] GSMA RCC.71 (2022), *RCS Universal Profile Service Definition Document*, Version 2.6.  
+<<https://www.gsma.com/newsroom/wp-content/uploads/RCC.71-v2.6-1.pdf>>
+- [b-IEEE ComParE] B.W. Schuller (2012), *The Computational Paralinguistics Challenge [Social Sciences]*, IEEE Signal Processing Magazine, Volume. 29, Issue. 4, pp. 97-101.  
+<<https://portal.fis.tum.de/en/publications/the-computational-paralinguistics-challenge-social-sciences>>
+- [b-IEEE GeMAPS] Eyben, F., Scherer, K.R., Schuller, B.W., Sundberg, J., Andrè, E., and Busso, C. (2016), *The Geneva Minimalistic Acoustic Parameter Set (GeMAPS) for Voice Research and Affective Computing*, IEEE Transactions on Affective Computing, Volume: 7, Issue 2, pp. 190-202.  
+<<https://ieeexplore.ieee.org/document/7160715>>
+- [b-IEEE MinHash] Broder, A.Z. (1997), *On the resemblance and containment of documents*, IEEE.  
+<<https://ieeexplore.ieee.org/document/666900>>
+- [b-IEEE SimHash] Manku, G.S., Jain, A., and Sarma, A.D (2007), *Detecting near-duplicates for web crawling*, Proceedings of the 16th International Conference on World Wide Web. pp. 141-150.  
+<<https://dl.acm.org/doi/10.1145/1242572.1242592>>
+
+
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.748.33-202410-I_PDF-E/raw.md b/marked/F/T-REC-F.748.33-202410-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..b3f83ade35f7123e9de3f8454de945602ef27d47
--- /dev/null
+++ b/marked/F/T-REC-F.748.33-202410-I_PDF-E/raw.md
@@ -0,0 +1,417 @@
+
+
+# Recommendation **ITU-T F.748.33 (10/2024)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+## --- **Metrics and evaluation methods for image-based re-identification algorithm**
+
+![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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.748.33
+
+# Metrics and evaluation methods for image-based re-identification algorithm
+
+## Summary
+
+Recommendation ITU-T F.748.33 provides a benchmark framework, metrics, requirements for testing datasets and evaluation process of image-based re-identification (Re-ID) algorithms. Image-based Re-ID is a critical task in machine vision systems with a wide range of applications in video surveillance system, intelligent transportation, etc. Owing to the advancement of deep learning, the image-based Re-ID algorithms have achieved impressive progress in academia. However, these state-of-art algorithms may have a significant performance drop when deployed in practical unconstrained scenarios. The existing evaluation method which mainly rely on pre-prepared open-source datasets cannot reflect the real performance of the algorithms in practical applications. It is crucial to have a unified, systematic, and fair evaluation method to comprehensively compare and analyse the diverse algorithms performance for both academia and industry.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.748.33 | 2024-10-29 | 16          | 11.1002/1000/16188 |
+
+## Keywords
+
+Dataset, evaluation, metric, performance, re-identification.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....               | 1    |
+| 4 Abbreviations and acronyms .....                          | 1    |
+| 5 Conventions .....                                         | 2    |
+| 6 Overview .....                                            | 2    |
+| 6.1 Evaluation object.....                                  | 2    |
+| 6.2 Overview of image-based Re-ID algorithm benchmark ..... | 2    |
+| 7 Framework of image-based Re-ID algorithm benchmark.....   | 3    |
+| 7.1 Image-based Re-ID algorithm .....                       | 3    |
+| 7.2 Image-based Re-ID algorithm benchmark .....             | 4    |
+| 7.3 Benchmarking results .....                              | 5    |
+| 8 Metrics of image-based re-identification algorithm .....  | 5    |
+| 8.1 Reliability indicators .....                            | 5    |
+| 8.2 Temporality indicators.....                             | 6    |
+| 9 Requirements for testing dataset.....                     | 6    |
+| 9.1 General requirements.....                               | 6    |
+| 9.2 Requirements for gallery set.....                       | 6    |
+| 9.3 Requirements for query set.....                         | 7    |
+| 10 Evaluation process of image-based Re-ID algorithm.....   | 7    |
+| Bibliography.....                                           | 8    |
+
+
+
+###### Recommendation ITU-T F.748.33
+
+## Metrics and evaluation methods for image-based re-identification algorithm
+
+# 1 Scope
+
+This Recommendation provides the framework of benchmark, metrics, requirements for testing datasets, and evaluation process for image-based reidentification (Re-ID) algorithms.
+
+It addresses the following subjects:
+
+- Overview;
+- Framework of image-based Re-ID algorithm benchmark;
+- Metrics of image-based Re-ID algorithm;
+- Requirements for testing datasets;
+- Evaluation process of image-based Re-ID algorithm.
+
+# 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 benchmarking** [b-ISO 17258]: Activity of comparing objects or practices of interest to each other or against a benchmark to evaluate criteria (or characteristic).
+
+**3.1.2 dataset** [b-ISO 19115]: Identifiable collection of data.
+
+**3.1.3 algorithm** [b-ISO/IEC 11557]: A set of rules for transforming the logical representation of data.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 re-identification**: A technique of retrieving and associating a specific object across multiple scenes and camera views.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+AI Artificial Intelligent
+
+AP Average Precision
+
+|       |                                     |
+|-------|-------------------------------------|
+| AQT   | Average Query Time                  |
+| BMP   | Bitmap                              |
+| CMC   | Cumulative Matching Characteristics |
+| CPU   | Central Processing Unit             |
+| FPGA  | Field Programmable Gate Arrays      |
+| GPU   | Graphics Processing Unit            |
+| JPEG  | Joint Photographic Experts Group    |
+| MAP   | Mean Average Precision              |
+| PNG   | Portable Network Graphics           |
+| Re-ID | Re-identification                   |
+
+# 5 Conventions
+
+- 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 needs 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
+
+## 6.1 Evaluation object
+
+Re-identification (Re-ID) is a technique of retrieving and associating a specific object across multiple scenes and camera views. Multimedia data format, such as image, video, or even a text description can be used to represent the Re-ID object. The evaluation object of this Recommendation focuses on image-based Re-ID, which is the most mature and widely used method in this filed. Given a query object-of-interest and a large set of gallery images, Re-ID algorithm represents each image with a feature embedding, then ranks the gallery images based on similarities of their feature embeddings to the query. This technology breaks through the limitation of single camera, and have a wide range of applications in security, intelligent transportation, etc.
+
+## 6.2 Overview of image-based Re-ID algorithm benchmark
+
+The existing evaluation method typically rely on pre-prepared open-source datasets, which cannot accurately reflect the algorithms' performance in real-world applications. To address this limitation, the image-based Re-ID algorithm benchmark is divided into on-site benchmark and off-site benchmark. The on-site benchmark refers to conducting evaluation on the images which are collected from practical application scenarios. The off-site benchmark refers to conducting evaluation on the open-source datasets. Both categories consist of four core components which are essential to the evaluation process.
+
+- Evaluation environment, which involves the AI framework, related software, and hardware system, to support the implementation and evaluation of image-based Re-ID algorithm. The
+
+environment configuration and acceleration method have a significant impact on the evaluation results.
+
+- Evaluation metrics, which quantify the accuracy and efficiency of the image-based Re-ID algorithm.
+- Testing dataset, which is composed of a query set and a gallery set to provide each evaluation attempt with the same conditions. The query set contains images which are used as reference to search for similar target in gallery set. The gallery set contains a larger set of images which serve as potential matches or candidates for comparison against the query.
+- Evaluation instruments, which include the methods used to produce evaluation results with the prepared metrics, testing dataset, and evaluation environment and the method of analysing the evaluation results. The evaluation instruments are recommended to be transparent, reproducible, and efficient to ensure the benchmarking process can be replicated and verified.
+
+The on-site benchmark and the off-site benchmark differ in the evaluation environment and testing dataset. The on-site benchmark requires selecting hardware equipment which matches the actual scenario and collecting data from real-world applications, which allows for more representative and reliable evaluation results. However, the on-site benchmark requires a high cost and effort for hardware implementation and data processing, and its evaluation process is subject to uncertainties due to factors in actual scenarios. In contrast, the off-site benchmark can reduce the cost of evaluation and make the evaluation process more controllable by using pre-prepared evaluation data and evaluation environment. However, it may not fully cover actual scenarios and may not reflect the performance of algorithms in online scenarios, such as real-time applications.
+
+Therefore, it is recommended to combine on-site benchmark and off-site benchmark based on specific evaluation requirements to achieve a more comprehensive evaluation of algorithm performance.
+
+# 7 Framework of image-based Re-ID algorithm benchmark
+
+Figure 1 illustrates the image-based Re-ID algorithm benchmark framework. For this benchmark, the input is the image-based Re-ID algorithm, and the output is the benchmarking score and report.
+
+![Figure 1 – Framework of image-based Re-ID algorithm benchmark. The diagram shows the flow from input to output through various benchmarking components.](dbe553cf16dd14073b89a8263a428664_img.jpg)
+
+The diagram illustrates the framework of the image-based Re-ID algorithm benchmark. It is structured as follows:
+
+- Input:** A box on the left labeled "Input" containing "Image-based Re-ID algorithm". An arrow points from this box into the main benchmarking framework.
+- Image-based Re-ID algorithm benchmark (Main Framework):** A large box containing several sub-components:
+  - Off-site:** A sub-box containing "Pre-prepared images" → "Data annotations" → "Pre-prepared dataset". An arrow points from "Pre-prepared dataset" to a central "Testing dataset" box.
+  - On-site:** A sub-box containing "Scene images" → "Data annotations" → "Scene dataset". An arrow points from "Scene dataset" to the central "Testing dataset" box.
+  - Testing dataset:** A central box that receives input from both Off-site and On-site datasets.
+  - Evaluation metrics:** A box containing "Reliability" and "Temporality". An arrow points from this box to the "Evaluation environment" box.
+  - Evaluation environment:** A box containing "Deep learning frameworks" and "AI acceleration processors" (which includes CPU, GPU, FPGA, NPU, and others). An arrow points from the "Testing dataset" to this box.
+  - Evaluation instruments:** A box containing "Tools/guides/evaluation methods". An arrow points from this box to the "AI acceleration processors" box.
+- Output:** A box on the right labeled "Output" containing "Score" and "Report". An arrow points from the "Evaluation environment" box to this box.
+
+Figure 1 – Framework of image-based Re-ID algorithm benchmark. The diagram shows the flow from input to output through various benchmarking components.
+
+F.748.33(24)
+
+**Figure 1 – Framework of image-based Re-ID algorithm benchmark**
+
+## 7.1 Image-based Re-ID algorithm
+
+The input Image-based Re-ID algorithm is the evaluation target. To ensure that the image-based Re-ID algorithm can be integrated into the benchmarking framework, produce necessary performance
+
+metrics, and can be compared with other algorithm in a consistent manner, it is recommended to define the following requirements:
+
+- **Algorithm implementation:** The Re-ID algorithm is required to be implemented and available in a format which allows it to be integrated into the evaluation environment. This could be in the form of source code, pre-trained models, or a software package. The key functionalities within the algorithm such as feature extraction and similarity calculation are recommended to be encapsulated into distinct modules to enable ease of use and flexibility.
+- **Compatibility:** The algorithm is required to be compatible with the evaluation infrastructure and frameworks being used. It should be able to work with the specified dataset formats, pre-processing steps, and evaluation instruments.
+- **Training and testing interfaces:** The algorithm is required to provide clear interfaces or functions for training and testing. These interfaces enable the algorithm to be trained on the training data and evaluated on the testing data.
+- **Reproducibility:** The algorithm is recommended to be reproducible, meaning that given the same input and training configuration, it can produce consistent results. This allows for fair comparison with other algorithms and ensures that the evaluation process is reliable.
+- **Documentation:** The algorithm is recommended to be well-documented, providing clear instructions on how to use it, any specific requirements or dependencies, and details about the underlying methodology. This documentation helps in understanding and replicating the algorithm's behaviour during evaluation.
+
+## 7.2 Image-based Re-ID algorithm benchmark
+
+### 7.2.1 Testing dataset
+
+The testing datasets can be divided into on-site dataset and off-site dataset. The on-site dataset is composed of images collected during the evaluation process after annotation. These images are typically captured in real-time or near real-time scenarios, such as surveillance footage or live video streams. The off-site dataset, on the other hand, consists of images that is pre-prepared and annotated before the evaluation. The requirements of testing datasets are described in clause 9.
+
+### 7.2.2 Evaluation metrics
+
+The evaluation metrics include reliability indicators and temporality indicators to provide a comprehensive evaluation of Re-ID algorithm performance. Reliability indicators assess the accuracy and robustness of Re-ID algorithms, while the temporality indicators access the computational efficiency and speed of Re-ID algorithm during inference. The calculation methods of these indicators are described in clause 8.
+
+### 7.2.3 Benchmarking instruments
+
+Evaluation instruments include tools used to measure and assess the performance of image-based Re-ID algorithm. These tools help automate the evaluation process and ensure consistency in performance measurement. It is recommended to support the following functions:
+
+- **Metric calculation:** It is recommended to be capable of calculating the predefined evaluation metrics.
+- **Result generation:** It is recommended to be capable of generating evaluation results in a structured format, such as tables or files, that can be easily interpreted and analysed.
+- **Result analysis:** It is recommended to support the analysis of the evaluation results which including generating statistical summaries, performance curves, or comparative analyses to gain insights into the algorithm's strengths and weaknesses. It is also recommended to support visualizations of the results for easier interpretation.
+
+- **Customizability:** It is recommended to offer customization options to accommodate different evaluation requirements. This can include the ability to select specific subsets of the testing dataset, define evaluation protocols, or adjust parameters for the metrics calculation.
+
+### 7.2.4 Evaluation environments
+
+The evaluation environment is recommended to include the following components:
+
+- **Hardware:** A suitable computing infrastructure is essential for evaluating Re-ID algorithms for both on-site and off-site. This typically includes high-performance central processing units (CPUs), graphics processing units (GPUs), field programmable gate arrays (FPGAs) to handle the computational demands of deep learning models.
+- **Deep learning frameworks:** The deep learning frameworks are used to implement the Re-ID algorithms. These frameworks provide the necessary tools and libraries for model development and evaluation. Additionally, it is recommended to include inference engines to enhance the performance of deep learning model inference on target hardware.
+
+## 7.3 Benchmarking results
+
+The benchmarking results includes the metrics score and report. The report is recommended to clearly record the evaluation process, including dataset details, processing steps, inference configurations, evaluation protocols and results.
+
+# 8 Metrics of image-based re-identification algorithm
+
+## 8.1 Reliability indicators
+
+**CMC:** Cumulative matching characteristics (*CMC*) curve is one of the most commonly used evaluation metrics for image-based re-identification algorithm. It reflects the comprehensive accuracy of the algorithm.
+
+The horizontal axis of the *CMC* curve is *Rank*, and the ordinate axis is the percentage of recognition rate. For each query, the algorithm will rank all the gallery samples according to their distances to the query from smallest to largest. The *Rank* represents the position in the ranked list.
+
+For each query, it has an *ACC* curve which is a step that shifts from 0 to 1 at the point where the correct match appeared. The *ACC* curve is calculated by:
+
+$$ACC = \begin{cases} 1, & \text{if the target is matched} \\ 0, & \text{otherwise} \end{cases} \quad (1)$$
+
+The *CMC* curve is computed by averaging the shifted step functions over all the queries. It is recommended to choose 3 points on the *CMC* curve as key performance indicators, the percentage of recognition rate at *rank-1*, *rank-5* and *rank-10*.
+
+**MAP:** The mean average precision (*MAP*) is a comprehensive indicator that measures the effectiveness of a model across all categories. *MAP* accounts for the precision of retrieval results, considering not only the correctness of the identification but also the ranking order, making it a robust metric for evaluating the overall performance of image-based recognition systems. *MAP* is the mean value of the average precision (*AP*) of each query. *AP* is the average precision of the same query on the datasets, it is an indicator that measures the effectiveness of a model on a single category.
+
+For the image Re-ID algorithm, assume the query dataset has  $N$  images, where  $q_i$  represents the  $i$ -th query, the query dataset is  $Q=\{q_1, q_2, \dots, q_N\}$ . The gallery has  $M$  images, where  $g_i$  represents the  $i$ -th image, the gallery is  $G=\{g_1, g_2, \dots, g_M\}$ .
+
+Firstly, compare the feature vectors of  $q_i$  with the feature vectors of each image in  $G$ , and sorts the gallery dataset from small to large based on distance, the sorted gallery dataset is  $G'_{q_i}$ ,  $G'_{q_i}=\{g'_1, g'_2, \dots, g'_M\}$ . Assuming there are  $K_{q_i}$  images similar to  $q_i$  in  $G$ , which form the similar
+
+dataset  $H$ ,  $H_{qi}=\{h_1, h_2, \dots, h_{K_{qi}}\}$  ( $H_{qi} \in G'_{qi}$ ). The ranking of  $h_j$  in  $H$  is  $r_j$  ( $r_j=j, j \in [1, K_{qi}]$ ), and the ranking of  $h_j$  in  $G'_{qi}$  is  $r'_j$ .
+
+The calculation formula for  $AP$  of  $q_i$  is:
+
+$$AP_i = \frac{1}{K_{qi}} \sum_{j=1}^{K_{qi}} \left( \frac{r_j}{r'_j} \right) \quad (2)$$
+
+Repeat the above process for all queries, and the  $MAP$  calculation formula is:
+
+$$MAP = \frac{1}{N} \sum_{i=1}^N AP_i \quad (3)$$
+
+## 8.2 Temporality indicators
+
+**AQT:** The average query time ( $AQT$ )  $T_{AQT}$  is the average searching time for every query consumed in the dataset. Assuming that the size of query dataset is  $N$ ,  $T_i$  is the algorithm's searching time for the  $i$ -th query, and the  $T_{AQT}$  calculation formula of the algorithm is:
+
+$$T_{AQT} = \frac{1}{N} \sum_{i=1}^N T_i \quad (4)$$
+
+# 9 Requirements for testing dataset
+
+## 9.1 General requirements
+
+The performance of image-based Re-ID algorithms is significantly influenced by the quality and characteristic of the testing datasets which are composed of query set and gallery set. Appropriate and representative testing datasets are critical for fair and object evaluation. Although there is no general method to assess a dataset quality, some requirements and criteria exist to support the selection and generating of testing datasets. The general requirement that is recommended to be satisfied for both query set and gallery set include:
+
+- Data format: It is recommended to support multimedia data formats such as video and image. For video, the recommended compression encoding types are ITU-T H.264 and ITU-T H.265. The image formats are recommended to support bitmap (BMP), Joint Photographic Experts Group (JPEG), portable network graphics (PNG).
+- Dataset scale 1: It is recommended to contain a substantial number of targets.
+- Dataset scale 2: It is recommended to contain multiple samples for each target.
+- Annotation: It is required to provide an identity label for each target. The same target within the query set and the gallery set has identical labels.
+- Scene diversity: It is recommended to collect data from a broad spectrum of real-world scenarios, including indoor, outdoor, daytime, nighttime, sunny, rainy conditions.
+- Noise: It is recommended to contain images with some degree of noise.
+
+## 9.2 Requirements for gallery set
+
+The properties of datasets, such as occlusion, viewpoint, and lighting conditions, can significantly impact the performance of Re-ID algorithms. To achieve a more comprehensive evaluation, it is necessary to establish requirements from different dimensions of dataset properties. The requirements for gallery set include:
+
+- Image resolution: It is recommended to contain images with multiple resolution.
+
+- Image clarity: It is recommended to allow some degree of blurriness such as trailing or shaking but ensure recognizability of the target features.
+- Occlusion: It is recommended to contain images with distributed levels of occlusion, while the target features cannot be completely occluded.
+- Lighting conditions: It is recommended to cover diverse lighting environments, but avoiding extreme highlights, contrasts, and flickering.
+
+## 9.3 Requirements for query set
+
+For Re-ID task, higher image quality standards are typically applied to the query set compared to the gallery set, since the query image serves as the basis for comparison and needs to provide clear and detailed information for accurate identification. The requirements for query set include:
+
+- Image resolution: It is recommended to contain images with high resolution.
+- Image clarity: It is recommended to keep the target features in the image clearly visible.
+- Occlusion: It is recommended to keep the target without occlusion.
+- Lighting conditions: It is recommended to keep a uniform lighting in the target area, without obvious highlights, contrasts, and flickering.
+- Image angle: Based on the research of image angle impact on Re-ID algorithm performance in [b-Sun], it is recommended to provide at least 2 angles of the target (front, back, left, right.).
+
+# 10 Evaluation process of image-based Re-ID algorithm
+
+This clause outlines the evaluation process of image-based Re-ID algorithm based on the evaluation framework, pre-defined metrics, and testing datasets.
+
+## Step 1: Evaluation request submission
+
+Prior to evaluating the Re-ID algorithm, the users are required to determine the evaluation scene and testing dataset for the algorithm, then submit an evaluation request to the benchmark. This request informs the benchmark of the specific evaluation requirements for the requested scene.
+
+- Scene: Scenes are distinguished from the two dimensions: time and regions. Different regions and periods are considered, such as daytime roads, night roads, daytime parks, night parks.
+- Testing dataset: Users have the flexibility to choose both on-site and off-site datasets, which can belong to the same or different scenes.
+
+## Step 2: Dataset preparation
+
+The evaluation benchmark receives the algorithm test request sent by users and retrieves the testing dataset according to the test request. On-site datasets are provided by users and collected from the scene required by users. Off-site datasets are the scene datasets stored by the system. For on-site datasets it is required to undergo pre-processing before evaluation to ensure it is adequately prepared for evaluation, enabling accurate and reliable assessment of the algorithm's performance.
+
+## Step 3: Evaluation environment setup
+
+Before evaluating the algorithm's performance in the scene, the benchmark deploys the evaluation environment according to the configuration file from evaluation request to ensure that all necessary resources are available.
+
+## Step 4: Evaluation execution
+
+Once the configuration is complete, deploy the target algorithm in the evaluation environment and execute it against the chosen testing dataset. The algorithm processes the images to match identities across the query set and gallery set.
+
+## **Step 5: Output report**
+
+After the benchmark completes the evaluation, a report for the algorithm will be generated based on the performance information on the target dataset.
+
+## Bibliography
+
+- [b-ISO 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 17258] ISO 17258:2015, *Statistical methods – Six Sigma – Basic criteria underlying benchmarking for Six Sigma in organisations.*
+- [b-ISO 19115-1] ISO 19115-1:2014, *Geographic information – Metadata – Part 1: Fundamentals.*
+- [b-Sun] Sun, X., & Zheng, L. (2019), *Dissecting person re-identification from the viewpoint of viewpoint. In Proceedings of the IEEE/CVF conference on computer vision and pattern recognition* (pp. 608-617).
+
+
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.748.42-202503-I_PDF-E/raw.md b/marked/F/T-REC-F.748.42-202503-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..0a0aabae0de3b6f1569ef7f9ee02a4ce3035665a
--- /dev/null
+++ b/marked/F/T-REC-F.748.42-202503-I_PDF-E/raw.md
@@ -0,0 +1,412 @@
+
+
+# Recommendation **ITU-T F.748.42 (03/2025)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+## --- **Requirements and framework for virtual tactile interaction 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 circular emblem with a stylized globe and the letters 'ITU' in white.
+
+ITU logo
+
+## ITU-T F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.748.42
+
+# Requirements and framework for virtual tactile interaction systems
+
+## Summary
+
+Recommendation ITU-T F.748.42 provides an overview of virtual tactile interaction systems and specifies the requirements and framework for these systems.
+
+In multimedia applications, the demand for virtual tactile interaction experiences is becoming increasingly significant. By simulating the physical tactile sensations of the real world, users can truly feel the objects in the virtual environment. This not only enriches the content and forms of multimedia applications but also brings users an unprecedented immersive sensory experience.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.748.42 | 2025-03-16 | 21          | 11.1002/1000/16232 |
+
+## Keywords
+
+Immersive sensory experience, multimedia, virtual tactile interaction systems.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <https://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                                  | 1    |
+| 4 Abbreviations and acronyms .....                                             | 2    |
+| 5 Conventions .....                                                            | 2    |
+| 6 Overview of VTIS .....                                                       | 2    |
+| 7 Requirement of VTIS .....                                                    | 3    |
+| 7.1 Tactile signals acquisition .....                                          | 3    |
+| 7.2 Tactile signals exchange.....                                              | 3    |
+| 7.3 Tactile signals preprocessing.....                                         | 4    |
+| 7.4 Tactile data analysis .....                                                | 4    |
+| 7.5 Tactile feedback.....                                                      | 5    |
+| 8 Framework and functional modules of VTIS .....                               | 5    |
+| 8.1 Tactile device.....                                                        | 5    |
+| 8.2 Tactile signals exchange module.....                                       | 6    |
+| 8.3 Tactile data preprocessing module .....                                    | 6    |
+| 8.4 Intelligent tactile data analysis module .....                             | 6    |
+| 8.5 Tactile feedback generation module.....                                    | 6    |
+| 8.6 Personalized tactile settings module.....                                  | 6    |
+| 8.7 Self-learning interaction optimization module.....                         | 6    |
+| Appendix I – Use cases of VTIS.....                                            | 7    |
+| I.1 Use case of VR games integrated with VTIS.....                             | 7    |
+| I.2 Use case of tracheostomy surgery training system integrated with VTIS..... | 8    |
+| Bibliography.....                                                              | 9    |
+
+
+
+# Recommendation ITU-T F.748.42
+
+## Requirements and framework for virtual tactile interaction systems
+
+## 1 Scope
+
+This Recommendation specifies the requirements and framework for virtual tactile interaction system. It addresses the following subjects:
+
+- Requirements of virtual tactile interaction system.
+- Framework and functional modules of virtual tactile interaction system.
+- Use cases of virtual tactile interaction 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.
+
+None.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 algorithm** [b-ITU-T F.740.7]: A set of rules for transforming the logical representation of data.
+
+**3.1.2 machine learning** [b-ITU-T Y.3172]: Processes that enable computational systems to understand data and gain knowledge from it without necessarily being explicitly programmed.
+
+**3.1.3 model** [b-ITU-T F.748.16]: An output created by an algorithm running on training data that can generate an inference or prediction, based on input data.
+
+**3.1.4 tactile** [b-ITU-T H.430.6]: Tactile appertains to touch.
+
+**3.1.5 virtual reality** [b-ITU-T P.1320]: An environment that is fully generated by digital means. To qualify as virtual reality, the virtual environment should differ from the local environment.
+
+### 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 tactile actuation device**: Device used to provide tactile feedback.
+
+**3.2.2 tactile perception device**: Device used to capture and detect tactile information from external environments or users.
+
+**3.2.3 virtual tactile interaction**: Simulating tactile sensation in the real world through devices and technologies enabling users to experience tactile feedback in a virtual environment.
+
+**3.2.4 virtual tactile interaction system**: A set of capabilities and devices integrated in a system that provides basic and common functions for virtual tactile interaction applications.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                    |
+|------|------------------------------------|
+| ML   | Machine Learning                   |
+| TAD  | Tactile Actuation Device           |
+| TPD  | Tactile Perception Device          |
+| VR   | Virtual Reality                    |
+| VTI  | Virtual Tactile Interaction        |
+| VTIS | Virtual Tactile Interaction System |
+
+## 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 of VTIS
+
+Multimedia technology has expanded the scope of information that computers can process. The information processed is no longer limited to text and numbers but also extensively includes images, graphics, videos, and audio. It is no longer confined to a sequential, monotonous, and narrow range. By transforming, combining, and processing the information, it has greatly enriched and enhanced the expressiveness of information, satisfying users' needs in terms of vision and hearing.
+
+Human reception and generation of information primarily occur within five sensory spaces, namely visual, auditory, tactile, olfactory, and gustatory, with the first three accounting for over 95% of the information processed. Although the visual and auditory interaction functions of current multimedia applications have developed relatively maturely, the tactile experience has always been lacking. When using multimedia applications, the lack of tactile interaction may lead to a less rich and authentic experience for users. For instance, in virtual reality (VR) games or the metaverse, virtual tactile interaction (VTI) can enable players to perceive the texture and collisions of objects in a virtual environment, thereby offering a more realistic experience. In many cases, the absence of tactile interaction features prevents users from fully immersing themselves in the virtual world and gaining a richer perception of information within the virtual environment, which in turn restricts the potential for the development of multimedia applications.
+
+To achieve a deeper sense of immersion and a more realistic interactive experience in multimedia applications, virtual tactile interaction systems (VTISs) are particularly important. VTISs are bidirectional and interactive, which is a key feature in realizing immersive experiences. In the direction of tactile data input, users interact with the virtual environment through actions such as touching, pressing, and sliding, and the system can detect and recognize these actions, thereby affecting the corresponding objects or events in multimedia applications. In the direction of tactile data feedback, the system simulates the surface texture, hardness, temperature, and other tactile
+
+experiences of objects through technologies such as vibration, inflation, and temperature changes. This feedback can be responses to user operations or simulations of physical properties in the environment, allowing users to touch and feel target objects in the digital world.
+
+VTISs mainly consist of hardware such as tactile perception devices (TPDs) and tactile actuation devices (TADs), as well as tactile information-processing algorithms. TPD and TAD are typically integrated into the same product, such as tactile gloves. By integrating various sensors, including accelerometer, gyroscopes, and pressure sensors, into tactile gloves or other interactive devices, TPDs collect real-time data on the user's hand movements and positions. TADs provide realistic tactile feedback. Tactile information processing algorithms encompass tactile data preprocessing, intelligent tactile perception analysis, and tactile feedback generation. It is necessary to clean and standardize the collected tactile data, and based on the processed data, conduct intelligent analyses such as gesture recognition, motion analysis, and user intent recognition. These algorithms calculate and convert the tactile information of virtual objects into control signals to achieve authentic tactile feedback.
+
+VTISs break through the sensory experience limitations of sight and hearing, bringing many new possibilities to multimedia application interactions. For instance, VTISs can be applied to fields such as virtual surgical training, remote collaboration, and gaming entertainment, allowing users to have a more realistic experience. Moreover, they can also provide more opportunities for independence and autonomy for people with disabilities, such as perceiving the surrounding environment through tactile information in virtual space or performing daily life operations. Therefore, VTISs are not just a technology or a system, they are the powerful tool that can promote social progress and improve the quality of human life.
+
+## **7 Requirement of VTIS**
+
+### **7.1 Tactile signals acquisition**
+
+The acquisition of tactile signals is a fundamental prerequisite for realizing tactile interaction. In contrast to audio and visual signals captured through devices such as cameras and camcorders in a non-contact manner, tactile signals are primarily gathered through tactile sensors installed on mechanical devices or robots that come into contact with objects. When in contact, these tactile sensors capture attributes of touch, such as the object's position, velocity, force, torque, and deformation.
+
+REQ-TSA-01: It is recommended to support the acquisition of multiple tactile attributes, such as vibration, force, or thermal sensation, to simulate more complex tactile sensations.
+
+REQ-TSA-02: It is recommended to support single-point and multi-point tactile perception acquisition.
+
+REQ-TSA-03: It can optionally support the design of tactile acquisition devices to be ergonomic, fitting the user's body without causing discomfort or fatigue.
+
+REQ-TSA-04: It can optionally support the tactile acquisition devices to have a certain degree of durability and wear resistance, as they may be frequently used.
+
+### **7.2 Tactile signals exchange**
+
+Tactile information will be transmitted between user devices and interactive systems, requiring high stability and reliability to ensure consistent performance during long-term operation.
+
+REQ-TSE-01: It is required to support bidirectional transmission of tactile information.
+
+REQ-TSE-02: It is recommended to support wireless and wired transmission.
+
+REQ-TSE-03: It is recommended to convert and integrate multiple tactile information features to reduce the transmission complexity.
+
+REQ-TSE-04: It is recommended to support the compression of tactile information.
+
+### 7.3 Tactile signals preprocessing
+
+When tactile signals are transmitted, especially in wireless networks, they inevitably encounter various sources of interference. This can result in varying degrees of degradation or even loss of tactile signals at the receiving end. Tactile signals are characterized by their spontaneity and unpredictability, which can lead to temporal misalignment of tactile signals at the receiving end. Additionally, in order to unify data from diverse tactile sources, spanning different time scales or originating from inconsistent sensors, into a consistent standard for further analysis, standardizing data becomes imperative.
+
+REQ-TSP-01: It is required to identify interference originating from external environments or other signal sources. In high-frequency circuits, such as amplifiers and switch circuits, rapid changes in current and voltage can generate dynamic noise. Other factors, including electronic devices, power fluctuations, electromagnetic radiation, and both conducted and radiated signal interference within the radio frequency band, may all contribute to high-frequency noise in the system. Reducing the impact of this high-frequency noise is crucial for protecting vital tactile signal components.
+
+REQ-TSP-02: It is required to identify and address anomalous data points. The focus should be on eliminating outliers, avoiding misleading data points, and improving the overall accuracy of the data.
+
+REQ-TSP-03: It is required to supplement missing tactile data values. For example, if the Weber-Fechner Law is satisfied, the previous value can be used to supplement the current missing value.
+
+REQ-TSP-04: It can optionally conduct time-domain and frequency-domain analysis to understand signal characteristics and frequency components, enhancing the comprehension of tactile signal characteristics.
+
+REQ-TSP-05: If multiple sensors are involved, it is required to ensure temporal synchronization of their data by performing signal alignment.
+
+REQ-TSP-06: When dealing with high-dimensional tactile signals, it is recommended to reduce the dimensions of tactile data to decrease their complexity.
+
+### 7.4 Tactile data analysis
+
+By analysing tactile data, it becomes possible to extract information about tactile attributes of objects such as shape, hardness, surface texture, as well as information about user actions, force exertion, and intentions.
+
+While traditional data analysis methods can address simple classification and regression tasks in tactile sensing, they become intricate when dealing with challenging value-based classification and regression problems that are difficult to model or optimize. In such cases, conventional approaches might yield unsatisfactory outcomes. ML, with its data-driven nature, emerges as a powerful tool to tackle such tasks effectively.
+
+REQ-TDA-01: It is recommended to consider multiple types of tactile data as inputs for a more comprehensive evaluation of the target task.
+
+REQ-TDA-02: It is recommended to consider the scalability of the data analysis system to handle increasing amounts of tactile data and the potential for distributed processing.
+
+REQ-TDA-03: It can optionally support the feedback mechanism to continuously improve the machine learning (ML) models based on new tactile data and user feedback.
+
+REQ-TDA-04: It can optionally support visualization tools and techniques to present the analytical results in an intuitive and easily understandable manner, as well as to provide explanations for the predictions made by the ML models.
+
+### 7.5 Tactile feedback
+
+Tactile feedback refers to the process of delivering tactile stimuli to a target object to achieve information dissemination, interaction, or feedback. Through tactile feedback, users or robots can acquire information about object attributes, environmental cues, or operational outcomes through tactile sensations, thereby enriching and enhancing their perceptual experiences or improving the reliability of task completion.
+
+REQ-TF-01: It is recommended to consider individual differences among users and ensure consistency and adaptability of feedback across different users. Providing adjustable parameters, such as stimulus intensity, frequency, and patterns, is advised to accommodate individual variances and preferences.
+
+REQ-TF-02: It is required to ensure that tactile feedback does not adversely affect the health or safety of the user.
+
+REQ-TF-03: It can optionally provide programmable interfaces, allowing developers to customize tactile feedback based on different application scenarios.
+
+## 8 Framework and functional modules of VTIS
+
+The bidirectional interaction mechanism of the VTIS is depicted in Figure 1. The system comprises key functional components including tactile devices, tactile signals exchange module, tactile data preprocessing module, intelligent tactile data analysis module and tactile feedback generation module.
+
+![Figure 1 – Framework of VTIS. The diagram shows a hierarchical structure of the Virtual Tactile Interaction System (VTIS). At the top is the 'Virtual tactile interaction system' box, which contains three layers: 'Applications layer' (with 'Personalized tactile settings' and 'Self-learning interaction optimization'), 'Services layer' (with 'Tactile data preprocessing', 'Intelligent tactile data analysis', and 'Tactile feedback generation'), and 'Transport layer' (with 'Tactile signals exchange'). Below this is the 'Tactile device' box, which contains 'Tactile perception device' and 'Tactile actuation device'. Bidirectional arrows connect the 'Tactile signals exchange' in the Transport layer to both the 'Tactile perception device' and the 'Tactile actuation device' in the Tactile device box. A small label 'F.748.42(25)' is at the bottom right of the diagram.](8e14350b4b669119a3bdfca7869110ca_img.jpg)
+
+The diagram illustrates the framework of the Virtual Tactile Interaction System (VTIS). It is structured as a hierarchy of layers within a 'Virtual tactile interaction system' box, interacting with a 'Tactile device' box below it.
+
+- Virtual tactile interaction system** (top box) contains:
+  - Applications layer**: Personalized tactile settings, Self-learning interaction optimization.
+  - Services layer**: Tactile data preprocessing, Intelligent tactile data analysis, Tactile feedback generation.
+  - Transport layer**: Tactile signals exchange.
+- Tactile device** (bottom box) contains:
+  - Tactile perception device
+  - Tactile actuation device
+
+Bidirectional arrows connect the 'Tactile signals exchange' in the Transport layer to both the 'Tactile perception device' and the 'Tactile actuation device' in the Tactile device box. A small label 'F.748.42(25)' is at the bottom right of the diagram.
+
+Figure 1 – Framework of VTIS. The diagram shows a hierarchical structure of the Virtual Tactile Interaction System (VTIS). At the top is the 'Virtual tactile interaction system' box, which contains three layers: 'Applications layer' (with 'Personalized tactile settings' and 'Self-learning interaction optimization'), 'Services layer' (with 'Tactile data preprocessing', 'Intelligent tactile data analysis', and 'Tactile feedback generation'), and 'Transport layer' (with 'Tactile signals exchange'). Below this is the 'Tactile device' box, which contains 'Tactile perception device' and 'Tactile actuation device'. Bidirectional arrows connect the 'Tactile signals exchange' in the Transport layer to both the 'Tactile perception device' and the 'Tactile actuation device' in the Tactile device box. A small label 'F.748.42(25)' is at the bottom right of the diagram.
+
+**Figure 1 – Framework of VTIS**
+
+### 8.1 Tactile device
+
+The tactile devices constitute a category of technological apparatuses designed for acquiring and simulating tactile information. They primarily consist of TPDs and TADs. TPDs capture and detect tactile information from external environments or users, such as position, action and force. TADs replicate tactile feedback by stimulating users' sensory systems with forces, torques, vibrations, temperatures, and other stimuli. This facilitates various tactile feedback and interactive experiences or triggers subsequent machine actions. Tactile devices encompass items like tactile gloves, tactile vests, and robotic hands.
+
+### **8.2 Tactile signals exchange module**
+
+The tactile signals exchange modules enable bidirectional transmission of tactile signals. They receive tactile signals from TPDs and deliver tactile feedback or control signals to TADs, ensuring real-time and accurate bidirectional exchange of tactile perception and reproduction. The modules are also capable of converting and processing received tactile signals or signals intended for transmission, to meet the requirements and specifications of the target objects.
+
+### **8.3 Tactile data preprocessing module**
+
+The tactile data preprocessing modules optimize and prepare tactile data before conducting tactile data analysis, enhancing the quality, accuracy, and usability of tactile data. They may encompass signal synchronization, noise filtering, signal enhancement, analogue-to-digital conversion, abnormal data detection and correction.
+
+### **8.4 Intelligent tactile data analysis module**
+
+The intelligent tactile data analysis modules employ ML models to conduct in-depth analysis and gain an understanding of tactile data. They not only address the analysis of single-type tactile signals and simple single-channel scenarios but also achieve intelligent analysis of complex situations involving multi-type tactile signals and multi-channel configurations. With the advancement of tactile sensors, complex interactions have become increasingly prevalent. By leveraging spatial relationship parameters among sensors, integrating tactile signals of target objects from diverse sensors, and neural networks, the modules effectively process multi-type tactile signals and complex situations involving multiple channels.
+
+### **8.5 Tactile feedback generation module**
+
+Building upon the outcomes of tactile data analysis, the tactile feedback generation modules compute and generate suitable tactile stimuli for feedback or control, directed towards the tactile execution devices, to accomplish closed-loop interactions with users, machines, or systems.
+
+### **8.6 Personalized tactile settings module**
+
+The personalized tactile settings modules can support users in personalizing the strength, mode, duration and other parameters of tactile feedback based on their preferences and needs, in order to improve user comfort and satisfaction.
+
+### **8.7 Self-learning interaction optimization module**
+
+The self-learning interaction optimization modules are capable of automatically adjusting the tactile interaction strategy based on the user's operational habits and feedback information, thereby achieving continuous optimization of the tactile interaction experience.
+
+## Appendix I
+
+### Use cases of VTIS
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### I.1 Use case of VR games integrated with VTIS
+
+With the continuous development of VR technology, more and more VR games are emerging and gaining the favour of numerous players. Although the future of VR games is promising, most VR games currently lack VTI, and the content and types of games are still relatively monotonous. The types of games and the ways they are played are also somewhat limited. VTI is an important means to achieve realism in VR games. It can simulate and provide tactile feedback to enhance the immersion and participation of players, thereby increasing the fun of the game.
+
+In VR games, a tactile glove is often required to act as a TPD and a TAD in VTIS. The tactile glove captures the position and motion data of the player's hand, such as the degree of finger bending, pressure, etc. In addition, it can simulate real physical tactile sensations through vibration sensors, weight sensors, and other devices embedded in the glove, allowing players to feel tactile interaction feedback. TADs may not only include tactile gloves but also extend to products such as tactile vests. These devices can enable players to experience richer tactile feedback on the body trunk.
+
+During the process of interaction between the player and the virtual environment, sensors on the tactile gloves collect real-time information about the player's hand gestures, and sensors on the tactile vest collect real-time information about the player's body posture. After receiving this tactile information, the system identifies and classifies different movements based on ML models, achieving real-time tracking and analysis of user posture and movements, and applying the analysis results to the virtual environment.
+
+The virtual environment reacts accordingly when influenced by the player's movements, and the system calculates the interactive tactile feedback based on the effects of the player's actions. For instance, when a player touches a virtual object, pressure and friction are exerted on the target object, which should then provide a corresponding reaction force to the player. That is, after the system recognizes the actions the player applies to the virtual object, it generates the corresponding tactile feedback signals. This may involve simulating various tactile effects such as pressure, vibration, and temperature changes. The generated haptic signals are then output to the player via tactile devices like tactile gloves or tactile vests, offering an immersive experience.
+
+When players enter VR games integrated with VTIS, it feels as if they have transcended time and space and entered a completely digitally constructed other world. Here, you can feel the breeze, the flow of water, and even touch everything in the virtual world. Every jump, every punch, is accompanied by real tactile interaction, making you feel as if you are truly in that world. See Figure I.1.
+
+![Diagram illustrating the interaction between a user and a VR game environment. On the left, a stylized human figure represents the user. On the right, a rectangular box labeled 'VR game' contains three stone statues. An arrow points from the user to the VR game, labeled 'Position, action and force'. Another arrow points from the VR game back to the user, labeled 'Texture, hardness, frictional force and temperature'. Below the VR game box, the text 'Stone statues' is present. In the bottom right corner of the diagram area, the code 'F.748.42(25)' is visible.](e9d825d87c5f85c8dba0664eace96ef4_img.jpg)
+
+The diagram shows a user on the left interacting with a VR game environment on the right. The user is represented by a simple line drawing of a head and shoulders. The VR game environment is a rectangular box containing three stone statues. A double-headed arrow connects the user and the VR game. The top arrow points from the user to the VR game and is labeled "Position, action and force". The bottom arrow points from the VR game to the user and is labeled "Texture, hardness, frictional force and temperature". Below the VR game box, the text "Stone statues" is present. In the bottom right corner of the diagram area, the code "F.748.42(25)" is visible.
+
+Diagram illustrating the interaction between a user and a VR game environment. On the left, a stylized human figure represents the user. On the right, a rectangular box labeled 'VR game' contains three stone statues. An arrow points from the user to the VR game, labeled 'Position, action and force'. Another arrow points from the VR game back to the user, labeled 'Texture, hardness, frictional force and temperature'. Below the VR game box, the text 'Stone statues' is present. In the bottom right corner of the diagram area, the code 'F.748.42(25)' is visible.
+
+Figure I.1 – VR game
+
+### I.2 Use case of tracheostomy surgery training system integrated with VTIS
+
+Tracheostomy, a common surgical procedure, involves making an incision in the neck to insert a tracheal tube, thereby ensuring unobstructed breathing. This procedure is suitable for patients with upper airway obstruction. Additionally, it serves as an adjuvant treatment for patients undergoing major surgeries in the nasal, oral, pharyngeal, laryngeal and neck areas to maintain clearance of the airway. In traditional tracheostomy surgery teaching, medical students typically can gain practical experience by observing surgical videos or participating in actual surgeries. However, due to the unique challenges and risks associated with tracheostomy surgery, this method presents significant drawbacks, making it challenging for medical students to gain sufficient hands-on experience.
+
+The integration of VR with tactile feedback technology has revolutionized tracheostomy surgery training. If VR technology is used without tactile feedback, although it is possible to simulate the tracheostomy scene in a VR virtual environment for medical students to train in, the absence of tactile force perception and interaction during the cutting process will not yield good training results.
+
+By integrating VR with tactile interaction technology, medical students can immerse themselves in a simulated tracheostomy surgery VR environment. When the medical students wield a scalpel or other surgical instruments, the TPD will capture their surgical motion information in real time. The system identifies their operational actions and intentions based on this motion information and generates corresponding tactile feedback. As a result, medical students can feel simulated tactile feedback such as cutting, stanching and the simulated body temperature of the surgical subject during their surgical training. Different postures, varying degrees of force applied during the cut, and the subtle changes in the interaction between surgical instruments and simulated human tissues can all lead to distinct tactile feedback that medical students can feel in real time. This responsive feedback system ensures that the diameter of the simulated tracheostomy adjusts accordingly, reflecting the precision of the students' surgical technique.
+
+VR surgical training with tactile interaction helps medical students experience the sensation of real surgical operations. Repeated training can enhance their muscle memory, thereby better mastering the necessary force and surgical skills, and increasing the success rate in clinical practice. Training in a simulated environment avoids the risks and complications inherent to actual surgeries, ensuring patient safety while providing a safe and controllable environment for medical professionals. Moreover, this method reduces reliance on physical models and teaching equipment, reducing the overall cost of training. See Figure I.2.
+
+![Diagram of the Tracheostomy surgery training system showing a user providing input and receiving feedback from a virtual system.](a26e142d3df5bef41a84a9dd099d7825_img.jpg)
+
+The diagram illustrates the interaction between a user and a tracheostomy surgery training system. On the left, a stylized icon of a person wearing a surgical cap with a cross symbol represents the user. An arrow labeled "Position, action and force" points from the user to a box on the right labeled "Tracheostomy surgery training system". Inside this box is a line drawing of a hand holding a scalpel, making an incision on a neck. A return arrow labeled "Force feedback of cutting and hemostasis, temperature" points from the system box back to the user icon. The text "F.748.42(25)" is located at the bottom right of the system box.
+
+Diagram of the Tracheostomy surgery training system showing a user providing input and receiving feedback from a virtual system.
+
+**Figure I.2 – Tracheostomy surgery training**
+
+## Bibliography
+
+- [b-ITU-T F.740.7] Recommendation ITU-T F.740.7 (2023), *Reference architecture and requirements for a mobile terminal computational photography system.*
+- [b-ITU-T F.748.16] Recommendation ITU-T F.748.16 (2022), *Requirements for applications and services in smart manufacturing based on machine vision.*
+- [b-ITU-T H.430.6] Recommendation ITU-T H.430.6 (2023), *Media transport protocols, signalling information of haptic transmission for immersive live experience (ILE) systems.*
+- [b-ITU-T P.1320] Recommendation ITU-T P.1320 (2022), *Quality of experience assessment of extended reality meetings.*
+- [b-ITU-T Y.3172] Recommendation ITU-T Y.3172 (2019), *Architectural framework for machine learning in future networks including IMT-2020.*
+
+
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.748.44-202503-I_PDF-E/raw.md b/marked/F/T-REC-F.748.44-202503-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..7643c212dd0fb076d7b315edc3299cf7c885b083
--- /dev/null
+++ b/marked/F/T-REC-F.748.44-202503-I_PDF-E/raw.md
@@ -0,0 +1,460 @@
+
+
+# Recommendation
+
+# **ITU-T F.748.44 (03/2025)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+## --- **Assessment criteria for foundation models – Benchmark**
+
+![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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.748.44
+
+## Assessment criteria for foundation models – Benchmark
+
+## Summary
+
+Recommendation ITU-T F.748.44 focuses on the requirements and evaluation methods of foundation models. It covers the overview of the benchmark for foundation models and identifies the requirements and evaluation methods of foundation models. It is important for ensuring consistency, transparency, and comparability across different foundation models, enabling fair evaluations and informed decision-making. It can assist industry participants in analysing and optimizing foundation models, as well as help users build and select products that align with these requirements.
+
+## History\*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.748.44 | 2025-03-16 | 21          | 11.1002/1000/16234 |
+
+## Keywords
+
+Benchmark, evaluation, foundation model.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <https://www.itu.int/ITU-T/ipr/>.
+
+© 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.....      | 1    |
+| 4 Abbreviations and acronyms .....                 | 1    |
+| 5 Conventions .....                                | 2    |
+| 6 Overview of benchmark for foundation models..... | 2    |
+| 6.1 General .....                                  | 2    |
+| 6.2 Testing capabilities.....                      | 2    |
+| 6.3 Testing datasets .....                         | 3    |
+| 6.4 Testing method .....                           | 3    |
+| 6.5 Testing tool.....                              | 5    |
+| 7 Requirements of foundation models.....           | 6    |
+| 7.1 Understanding ability .....                    | 6    |
+| 7.2 Generation ability .....                       | 6    |
+| 7.3 Reasoning ability .....                        | 6    |
+| 7.4 Knowledge ability .....                        | 6    |
+| 7.5 Reliability .....                              | 7    |
+| 7.6 Robustness.....                                | 7    |
+| 8 Evaluation methods of foundation models .....    | 7    |
+| 8.1 Automated evaluation.....                      | 7    |
+| 8.2 Manual evaluation .....                        | 7    |
+| Appendix I – Use cases of benchmark testing .....  | 9    |
+
+
+
+# Recommendation ITU-T F.748.44
+
+## Assessment criteria for foundation models – Benchmark
+
+# 1 Scope
+
+This Recommendation identifies evaluation metrics, datasets, methods and tools for foundation models in benchmark testing. It covers the following aspects:
+
+- Overview of benchmark for foundation models;
+- Requirements of foundation models;
+- Evaluation methods of foundation 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.
+
+None.
+
+# 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:
+
+|      |                                          |
+|------|------------------------------------------|
+| BLEU | Bilingual Evaluation Understudy          |
+| GB   | Gigabyte                                 |
+| GPU  | Graphics Processing Unit                 |
+| MMLU | Massive Multitask Language Understanding |
+| NLP  | Natural Language Processing              |
+| OOD  | Out-Of-Distribution                      |
+| PB   | Petabyte                                 |
+| TB   | Terabyte                                 |
+
+# 5 Conventions
+
+In this Recommendation:
+
+- The keywords "is recommended to" indicate a requirement that is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance.
+
+# 6 Overview of benchmark for foundation models
+
+## 6.1 General
+
+The evaluation of foundation models in practical applications is essential to their successful use. Benchmark testing of the foundation models, which evaluates the performance of foundation models by designing reasonable evaluation tasks and datasets, is currently the most recognizable method. Thus, formulating the criteria and standardizing the benchmark testing, which includes evaluation capabilities, datasets, methods and tools, can help model developers and users to obtain high-quality evaluation results.
+
+Figure 1 provides an overview of benchmark for foundation models. It covers a broad range of testing capabilities, testing methods, testing datasets and testing tools.
+
+![Figure 1: Reference overview of benchmark for foundation models. The diagram shows four main categories: Testing capabilities, Testing method, Testing datasets, and Testing tools. Testing capabilities include scenarios, abilities, tasks, and metrics. Testing method includes analysis, preparation, execution, evaluation, and display. Testing datasets include composition and process requirements. Testing tools include functional and performance requirements.](07b17a620c75522d53916a11e12d1bff_img.jpg)
+
+|                              |                                                       |               |                 |
+|------------------------------|-------------------------------------------------------|---------------|-----------------|
+| <b>Testing capabilities</b>  |                                                       |               |                 |
+| Testing scenarios            | Testing abilities                                     | Testing tasks | Testing metrics |
+| <b>Testing method</b>        | <b>Testing datasets</b>                               |               |                 |
+| Test requirement analysis    | Composition requirements      Process requirements    |               |                 |
+| Test environment preparation |                                                       |               |                 |
+| Test datasets preparation    |                                                       |               |                 |
+| Benchmark test execution     | <b>Testing tools</b>                                  |               |                 |
+| Test result evaluation       | Functional requirements      Performance requirements |               |                 |
+| Test results display         |                                                       |               |                 |
+
+F.748.44(25)
+
+Figure 1: Reference overview of benchmark for foundation models. The diagram shows four main categories: Testing capabilities, Testing method, Testing datasets, and Testing tools. Testing capabilities include scenarios, abilities, tasks, and metrics. Testing method includes analysis, preparation, execution, evaluation, and display. Testing datasets include composition and process requirements. Testing tools include functional and performance requirements.
+
+**Figure 1 – Reference overview of benchmark for foundation models**
+
+## 6.2 Testing capabilities
+
+### 6.2.1 Testing scenarios
+
+The benchmark testing scenarios refer to the specific contexts or environments in which foundation models are tested to evaluate their performance and capabilities across a variety of tasks and conditions. It is recommended to include the general scenarios, application scenarios, security scenarios, and industry scenarios.
+
+### 6.2.2 Testing abilities
+
+The benchmark testing abilities refer to the various aspects or criteria against which the performance of foundation models is evaluated. These abilities cover a range of capabilities that are critical for assessing how well a foundation model can handle different tasks. It is recommended to include the understanding, generation, reasoning, reliability and robustness abilities.
+
+### 6.2.3 Testing tasks
+
+The benchmark testing tasks are a set of standardized evaluations designed to assess the capabilities and performance of foundation models. These tasks are designed to test specific aspects of a model's functionality, such as its ability to understand natural language, make predictions, classify data, or generate content. It is recommended to include the recognition, question answering, translation and summarization tasks.
+
+### 6.2.4 Testing metrics
+
+The benchmark testing metrics are standardized measures used to evaluate the performance of foundation models. These metrics provide a consistent way to compare different models across various tasks and domains.
+
+## 6.3 Testing datasets
+
+### 6.3.1 Composition requirements
+
+The composition of the benchmark test dataset for foundation models is recommended to meet the following requirements:
+
+- a) **Quantity requirements:** It is recommended to ensure that the test datasets are sufficiently large to comprehensively and objectively test the actual performance of foundation models.
+- b) **Type requirements:** It is recommended to ensure a variety of question types to test the performance of foundation models. At least one type of objective question (multiple-choice, multiple-answer, fill-in-the-blank, true/false and subjective question (essay, summary, translation) is recommended to be included.
+- c) **Difficulty requirements:** It is recommended to provide different difficulty levels for questions and add difficulty tags to each test, such as normal or hard.
+
+### 6.3.2 Process requirements
+
+The process of constructing a benchmark test dataset for foundation models is similar to that of a training dataset. It is recommended to include data acquisition, data preprocessing, data formatting, data storage and data labelling management.
+
+## 6.4 Testing method
+
+The test method of benchmark testing in foundations models represents the pipeline which consists of several tasks, including test requirement analysis, test environment preparation, test datasets preparation, benchmark test execution, test result evaluation and test results display.
+
+### 6.4.1 Test requirement analysis
+
+The analysis of testing requirements is the first step in the foundation model testing process. Comprehensive coverage helps ensure the effectiveness of testing activities. It is recommended to include the key aspects of foundation model testing requirements analysis:
+
+- a) **Evaluation objectives:** It is recommended to define the evaluation goals, such as comparing with industry competitors or different internal versions, to specify the corresponding evaluation metrics.
+- b) **Model review:** It is recommended to carefully review model documentation, including specifications and design documents, to understand the model's functionality, inputs, outputs and constraints, and to ensure a consistent understanding by communicating with the development team.
+- c) **Testing plan design:** It is recommended to design the testing plan based on the requirements, including the number of testing rounds, types of inputs for each round and evaluation metrics.
+
+- d) **Testing inputs and outputs analysis:** It is recommended to analyse the test input data, identify different data scenarios that may cause variations in model behaviour, and design corresponding test cases. Determine the expected outputs of the model and design test cases to verify whether the outputs meet expectations.
+- e) **Performance and security analysis:** It is recommended to determine performance metrics such as response time and throughput, and design performance test cases to evaluate the model under different load conditions. It is recommended to identify security requirements, such as data encryption and access control, and design security test cases to verify the model's security capabilities.
+
+### 6.4.2 Test Environment preparation
+
+The analysis of testing requirements for foundation models includes several critical aspects. Key points to focus on are:
+
+- a) **Software and hardware preparation:** It is recommended to prepare the necessary software and hardware environment according to the requirements of the model under test. For interface testing, lower-spec hardware may suffice, but for private deployment of foundation models, high-performance graphics processing units (GPUs) are needed based on the model's parameter size.
+- b) **Testing framework deployment:** It is recommended to use scripts for single, small sample data tests. However, for testing multiple foundation models with significant data volumes, it is recommended to use a testing framework or system, typically deployed on servers.
+- c) **Model deployment:** It is recommended to deploy the model in the hardware environment and perform initial validation of the model's capabilities for private deployments.
+- d) **Testing environment verification:** It is recommended to use a small amount of test data to conduct an overall verification of the testing environment.
+
+### 6.4.3 Test datasets preparation
+
+It is recommended to ensure that the process of constructing test datasets for foundation models follows a similar approach to that of training data and refers to established standards.
+
+### 6.4.4 Benchmark test execution
+
+The execution phase of testing involves inputting test data into the model under test and observing its outputs. Based on practical needs (such as the volume of test data and testing costs), the execution methods can be divided into:
+
+- a) **Single-point execution:** Test data is input sequentially into the model on a single server and the model's output collected. This method is simple but time-consuming.
+- b) **Distributed execution:** The central node divides the testing tasks and distributes them to individual servers for execution, then collects the output from the model through the central node. This method is more complex but has higher testing efficiency.
+
+### 6.4.5 Test result evaluation
+
+It is recommended to use of reasonable metrics to evaluate the foundation model outputs measure performance. The evaluation methods of model outputs can be divided into automated evaluation and manual evaluation, aiming for quantifiable results.
+
+### 6.4.6 Test results display
+
+The benchmark testing results of foundation model are usually presented in a test report, it is recommended to include the following content:
+
+- a) **Evaluation objectives and tasks:** It is recommended to include a definition of the primary goals of the evaluation, including the specific tasks involved and outlining the expected outcomes.
+- b) **Testing environment:** It is recommended to include a description of the datasets used, which include its source, size, text types and topic diversity. It is recommended to detail the training and evaluation set-up, including hyper-parameters, training duration and hardware configuration.
+- c) **Evaluation metrics:** It is recommended to explain the metrics used for assessing performance, covering both automated and manual evaluation methods.
+- d) **Visualized results:** It is recommended to provide detailed quantitative results, including performance across different tasks and datasets. It is recommended to use visualizations such as charts and images to illustrate model performance.
+- e) **Conclusions:** It is recommended to summarize overall findings, including core usability and accuracy scores, and detailed conclusions for specific capabilities.
+
+## 6.5 Testing tool
+
+In this clause, the requirements for the testing tools in the benchmark will be specified.
+
+### 6.5.1 Functional requirements
+
+##### 6.5.1.1 Datasets management
+
+It is recommended to provide functionality for downloading, storing and managing testing datasets, which includes commonly used public datasets and user-defined datasets. The testing tool is recommended to support multiple data formats and organizational structures.
+
+##### 6.5.1.2 Model management
+
+It is recommended to provide management functionality for the foundation models to be tested, which includes the commonly used foundation models and user-defined models.
+
+##### 6.5.1.3 Testing configuration and execution
+
+- a) It is recommended to support user-defined configuration of test tasks, such as the settings for hardware environment, software environment and testing parameters.
+- b) It is recommended to support the splitting and distribution of test datasets and tasks for test execution.
+
+##### 6.5.1.4 Evaluation metrics
+
+It is recommended to support the calculation of multiple evaluation metrics, such as accuracy, recall, F1 score.
+
+##### 6.5.1.5 Testing result display
+
+It is recommended to support the display of testing results, including leaderboard, radar chart and other visualizations.
+
+#### 6.5.2 Performance requirements
+
+##### 6.5.2.1 Test data throughput
+
+It is recommended to support sufficient data throughput, enabling the platform to successfully process a significant amount of test data within a unit of time.
+
+##### 6.5.2.2 Test data storage capacity
+
+It is recommended to support sufficient data storage capacity to accommodate the maximum amount of test data, typically measured in units such as petabyte (PB), terabyte (TB), or gigabyte (GB).
+
+# 7 Requirements of foundation models
+
+## 7.1 Understanding ability
+
+- a) It is recommended to support text classification ability, which refers to a natural language processing (NLP) technique that involves assigning a label or category to a given piece of text.
+- b) It is recommended to support natural language inference ability, which refers to the task of determining whether the given "hypothesis" logically follows from the "premise".
+- c) It is recommended to support semantic understanding ability, which refers to the meaning or understanding of language and its associated concepts.
+
+## 7.2 Generation ability
+
+- a) It is recommended to support summarization, which refers to the generation task that aims to learn a concise abstract for the given sentence.
+- b) It is recommended to support machine translation, which refers to the subfield of computational linguistics that involves the use of foundation models to automatically translate text or speech from one language to another.
+- c) It is recommended to support question answering, which refers to a crucial technology in the field of human-computer interaction, and it has found wide application in scenarios like search engines, intelligent customer service and question answering systems.
+
+## 7.3 Reasoning ability
+
+To effectively tackle reasoning tasks, the foundation model is recommended to not only comprehend the provided information but also utilize reasoning and inference to deduce answers when explicit responses are absent.
+
+- a) **Commonsense reasoning:** Given questions based on common human knowledge, it is recommended to ensure that foundation models can correctly deduce the answers based on the provided information.
+- b) **Causal reasoning:** Given a piece of text, it is recommended to ensure that foundation models can determine the causal relationships among the events.
+- c) **Mathematical reasoning:** It is recommended to assess the foundation model's ability to solve mathematical problems, including arithmetic operations, sets, inequalities, linear algebra, calculus, mathematical applications, complex theorems and other fields.
+
+## 7.4 Knowledge ability
+
+Evaluating the knowledge capabilities of foundation models, with a focus on measuring the model's grasp of various types of knowledge, including the following abilities:
+
+- a) **World knowledge:** It is recommended to assess the foundation model's mastery of diverse knowledge by constructing a question bank that includes world knowledge, such as geography, history and literature.
+- b) **Social commonsense:** It is recommended to evaluate the foundation model's grasp of local knowledge by constructing a question bank that includes topics, such as laws, customs and culture, which reflect social common sense.
+
+- c) **Objective facts:** It is recommended to evaluate the accuracy and objectivity of foundation models by using fact-based questions or statements, such as information related to objective entities.
+
+## 7.5 Reliability
+
+Evaluating the reliability of content generated by foundation models, with a focus on examining the authenticity of the content, including:
+
+- a) **Hallucination:** It is recommended to evaluate the authenticity and objectivity of the content generated by foundation models, including their responses to fictional or misleading questions, as well as their answers to complex reasoning problems accurately.
+- b) **Factuality:** It is recommended to evaluate the ability of foundation models to resist being misled, with a particular focus on assessing whether the content generated by foundation models is easily influenced by the way questions are posed.
+- c) **Real-Time capabilities:** It is recommended to support the evaluation of the effectiveness of foundation models in answering questions requiring up-to-date knowledge, thereby determining their ability to utilize their knowledge base.
+
+## 7.6 Robustness
+
+Robustness studies the stability of a system when facing unexpected inputs. Specifically, out-of-distribution (OOD) and adversarial robustness are two important aspects for robustness.
+
+- a) **Adversarial robustness:** It is recommended to support the detection and evaluation of adversarial attacks on foundation model input at multiple levels, such as character, word, sentence and semantics for text.
+- b) **OOD:** It is recommended to support OOD testing to evaluate the adaptability and resilience of foundation models when handling new, unseen and potentially adversarial data that significantly differs from the original training datasets.
+
+# 8 Evaluation methods of foundation models
+
+## 8.1 Automated evaluation
+
+Automated evaluation uses the standard metrics or indicators to assess the performance of models. Automated evaluation methods of the foundation models can be divided into traditional methods and judge model evaluation.
+
+- a) **Traditional methods:** It is recommended to use a uniform prompt template and objective questions for foundation models, by requiring them to select the most reasonable answer from a given set of options. The selection results are evaluated by comparing the model's answer with the standard answer.
+- b) **Judge model evaluation:** It is recommended to design prompts that include the question, the standard answer and the inference results to the judge foundation models. The judge foundation model evaluates the quality of the response generated by the foundation model to be tested.
+
+## 8.2 Manual evaluation
+
+Due to the randomness in the content generated by foundation models, the aforementioned automated quality assessment methods cannot cover all scenarios, such as subjective evaluation questions without standard answers, where it is impossible to calculate assessment metrics using automated methods. In such cases, it is recommended to use the manual evaluation methods. The manual evaluation methods can be categorized into:
+
+- a) **Expert evaluation:** It is recommended to ensure that the assessment of outputs is supported by domain experts leveraging their experience and knowledge.
+- b) **Sample evaluation:** It is recommended to support the capability to randomly select samples for manual assessment.
+
+In order to ensure the impartiality of evaluation results effectively, it is essential to adhere to certain requirements:
+
+- a) **Diversity:** It is recommended to ensure the selection of evaluators from diverse backgrounds and expertise, accompanied by the provision of detailed task instructions and adequate training.
+- b) **Clarity and consistency:** It is recommended to clearly define each evaluation task and ensure uniform understanding and execution among evaluators.
+- c) **Multidimensional and quantitative metrics:** It is recommended to use various metrics such as accuracy, fluency and relevance, and employ quantifiable metrics to reduce subjectivity.
+
+## Appendix I
+
+## Use cases of benchmark testing
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Evaluation of foundation model is a challenging task with many proposed technical metrics and human evaluation methods. Benchmark testing of foundation models, which involve designing reasonable testing tasks and datasets to evaluate the foundation models objectively and quantitatively, is the most recognizable method in both academia and industry. Figure I.1 shows the pipeline of benchmark testing for foundation models.
+
+![Figure I.1: Pipeline of benchmark testing for foundation models. The diagram illustrates a workflow involving Dataset, Model, and Evaluation components, coordinated by a Benchmark driver. The Dataset component includes a Data loader. The Model component includes Model config and Call API. The Evaluation component includes a clipboard icon. The Benchmark driver orchestrates the flow: Load dataset -> Create prompt -> Run model -> Call post-processor -> Call evaluator. Assets like Prompt constructor and Post-processor are also involved.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg)
+
+The diagram illustrates the pipeline of benchmark testing for foundation models. It is organized into three main horizontal layers: Dataset, Model, and Evaluation, all coordinated by a central Benchmark driver.
+
+- Dataset Layer:** Contains a 'Data loader' which interacts with the 'Load dataset' step in the Benchmark driver.
+- Model Layer:** Contains 'Model config' and 'Call API', which interact with the 'Run model' step in the Benchmark driver.
+- Evaluation Layer:** Contains a clipboard icon representing metrics, which interacts with the 'Call evaluator' step in the Benchmark driver.
+- Benchmark driver:** A central dashed box containing a sequence of steps: 'Load dataset' (receiving from Dataset), 'Create prompt' (sending to Prompt constructor), 'Run model' (sending to Model), 'Call post-processor' (sending to Post-processor), and 'Call evaluator' (sending to Evaluation).
+- Asset Layer:** Contains 'Prompt constructor' and 'Post-processor', which provide input to the 'Create prompt' and 'Call post-processor' steps respectively.
+
+Figure I.1: Pipeline of benchmark testing for foundation models. The diagram illustrates a workflow involving Dataset, Model, and Evaluation components, coordinated by a Benchmark driver. The Dataset component includes a Data loader. The Model component includes Model config and Call API. The Evaluation component includes a clipboard icon. The Benchmark driver orchestrates the flow: Load dataset -> Create prompt -> Run model -> Call post-processor -> Call evaluator. Assets like Prompt constructor and Post-processor are also involved.
+
+F.748.44(25)
+
+Figure I.1 – Pipeline of benchmark testing for foundation models
+
+As shown in Figure I.1, benchmark testing for foundation models includes three key aspects, namely, testing datasets, testing metrics and testing methods. Similar to exams, the testing inputs for the foundation models in benchmark testing are testing datasets. The testing datasets can include multiple question types, such as single choice, multiple choice, question answering and so on. Figure I.2 shows an anatomy example in the massive multitask language understanding (MMLU) benchmark. Additionally, the testing datasets also provide a set of prompts, which are usually added at the beginning of the question, to guide the foundation models to answer the question. Both the prompts and question are inputted to the foundation models. The foundation models can answer the question based on the inference of deep neural networks. For the answer generated by the foundation model, it is necessary to judge its correctness. The evaluation methods can be categorized into automatic methods and manual methods. For objective questions, such as single-choice or multiple-choice, the automated methods can be used. For the subjective questions, the manual methods should be used. Finally, the evaluation results can be calculated according to the testing metrics, such as accuracy, recall, F1 score, bilingual evaluation understudy (BLEU) and so on.
+
+What is the embryological origin of the hyoid bone?  
+(A) The first pharyngeal arch  
+(B) The first and second pharyngeal arches  
+(C) The second pharyngeal arch  
+(D) The second and third pharyngeal arches
+
+F.748.44(25)
+
+Figure I.2 – An anatomy example in MMLU benchmark.
+
+As a result, a high-quality benchmark should not only include testing datasets and metrics, but also define the requirements for the testing method and tools. With the continuous advancement of technology and the expansion of application scenarios, benchmark testing will play a more important role in the future.
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.748.45-202503-I_PDF-E/raw.md b/marked/F/T-REC-F.748.45-202503-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..ef53a3f0c5c56b150710f770a7f88e36df55122c
--- /dev/null
+++ b/marked/F/T-REC-F.748.45-202503-I_PDF-E/raw.md
@@ -0,0 +1,479 @@
+
+
+# Recommendation **ITU-T F.748.45 (03/2025)**
+
+SERIES F: Non-telephone telecommunication services  
+Multimedia services
+
+---
+
+## **Technical requirements and evaluation methods of artificial intelligence (AI)-based code generation in multimedia applications**
+
+![ITU logo](390120de4fe440c42fea8154fcaad334_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 the letters 'ITU' in a bold, blue, sans-serif font. The globe is stylized with a white arrow pointing upwards and to the right, symbolizing global connectivity and communication.
+
+ITU logo
+
+## ITU-T F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.748.45
+
+# Technical requirements and evaluation methods of artificial intelligence (AI)-based code generation in multimedia applications
+
+## Summary
+
+Recommendation ITU-T F.748.45 specifies the technical requirements and evaluation methods during the construction of the code generation based on the foundation model. It aims to guide the code generation ability construction based on the foundation model and provide general user guidelines.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.748.45 | 2025-03-16 | 21          | 11.1002/1000/16235 |
+
+## Keywords
+
+Artificial intelligence, code generation, evaluation, foundation model.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <https://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                                                  | 1  |
+| 4    | Abbreviations and acronyms .....                                                           | 1  |
+| 5    | Conventions .....                                                                          | 1  |
+| 6    | Requirements and evaluation methods of code generation based on the foundation model ..... | 2  |
+| 7    | General capability.....                                                                    | 2  |
+| 7.1  | Code understanding .....                                                                   | 2  |
+| 7.2  | Code generation and completion .....                                                       | 3  |
+| 7.3  | Code transformation .....                                                                  | 4  |
+| 7.4  | Unit test case generation.....                                                             | 4  |
+| 7.5  | Code diagnosis and optimization.....                                                       | 4  |
+| 8    | Specialized scenario capability.....                                                       | 5  |
+| 8.1  | Website development .....                                                                  | 5  |
+| 8.2  | Desktop development .....                                                                  | 5  |
+| 8.3  | Mobile application development .....                                                       | 5  |
+| 8.4  | Artificial intelligence development .....                                                  | 5  |
+| 8.5  | Big data development .....                                                                 | 5  |
+| 9    | Supporting capability.....                                                                 | 6  |
+| 9.1  | Data supporting capability.....                                                            | 6  |
+| 9.2  | Model supporting capability.....                                                           | 6  |
+| 9.3  | Service supporting capability .....                                                        | 7  |
+| 10   | Evaluation methods .....                                                                   | 8  |
+| 10.1 | Evaluation metrics .....                                                                   | 8  |
+| 10.2 | Evaluation methods .....                                                                   | 9  |
+|      | Bibliography.....                                                                          | 10 |
+
+
+
+# Recommendation ITU-T F.748.45
+
+# Technical requirements and evaluation methods of artificial intelligence (AI)-based code generation in multimedia applications
+
+# 1 Scope
+
+This Recommendation specifies the requirements and evaluation methods for a code generation based on the foundation model including four aspects: general capability, specialized scenario capability, supporting capability, and evaluation methods. This Recommendation is applicable to the development and acceptance check of technology and applications of the code generation based on the foundation model in the various walks of life, such as finance, technology, Internet, telecommunications, software, electronic game creation, audio and video processing, image processing, and so on.
+
+# 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 term defined elsewhere:
+
+**3.1.1 artificial intelligence** [b-ITU-T F.749.13]: An interdisciplinary field, usually regarded as a branch of computer science, dealing with models and systems for the performance of functions generally associated with human intelligence, such as reasoning and learning.
+
+### 3.2 Terms defined in this Recommendation
+
+None.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+AI Artificial Intelligence
+
+## 5 Conventions
+
+In this Recommendation:
+
+- The keywords "is recommended to" indicate a requirement that is recommended but which is not absolutely required. Thus, this requirement needs not be present to claim conformance.
+
+## 6 Requirements and evaluation methods of code generation based on the foundation model
+
+Figure 6-1 illustrates the technical structure for code generation ability based on the foundation model. The structure can be divided into four parts, including: supporting capability, general capability, specialized scenario capability, and evaluation methods.
+
+![Figure 6-1: Structure of the requirements and evaluation methods of code generation based on the foundation model. The diagram is a hierarchical tree showing four main categories: Specialized scenario capability, General capability, Supporting capability, and Evaluation methods. Specialized scenario capability includes Website, Desktop, Mobile, AI, and Big data development. General capability includes Code understanding, generation, transformation, testing, and optimization. Supporting capability includes Data, Model, and Service support. Evaluation methods are shown on the right side with metrics for each category.](990567efebf979be51f56d1150012c9d_img.jpg)
+
+| Specialized scenario capability                           |                                                                    |                                                         |                                                                    |                                                               | Evaluation methods |
+|-----------------------------------------------------------|--------------------------------------------------------------------|---------------------------------------------------------|--------------------------------------------------------------------|---------------------------------------------------------------|--------------------|
+| Website development                                       | Desktop development                                                | Mobile application development                          | Artificial intelligence development                                | Big data development                                          |                    |
+| User interface design<br>Content management<br>User login | User interaction handling<br>Content management<br>Data processing | Permission management<br>Log management<br>Message push | Machine learning<br>Computer vision<br>Natural language processing | Data cleaning<br>Data transformation<br>Data analysis queries |                    |
+| Website frontend framework support                        | Desktop framework support                                          | Mobile application framework support                    | Artificial intelligence framework and tool support                 | Language coverage                                             |                    |
+| Website backend framework support                         |                                                                    |                                                         |                                                                    | Big data framework support                                    |                    |
+| General capability                                        |                                                                    |                                                         |                                                                    |                                                               | Evaluation metrics |
+| Code understanding                                        | Code generation and completion                                     | Code transformation                                     | Unit test case generation                                          | Code diagnosis and optimization                               |                    |
+| Supporting capability                                     |                                                                    |                                                         |                                                                    |                                                               | Evaluation methods |
+| Data supporting capability                                | Model supporting capability                                        | Service supporting capability                           |                                                                    |                                                               |                    |
+
+F.748.45(25)
+
+Figure 6-1: Structure of the requirements and evaluation methods of code generation based on the foundation model. The diagram is a hierarchical tree showing four main categories: Specialized scenario capability, General capability, Supporting capability, and Evaluation methods. Specialized scenario capability includes Website, Desktop, Mobile, AI, and Big data development. General capability includes Code understanding, generation, transformation, testing, and optimization. Supporting capability includes Data, Model, and Service support. Evaluation methods are shown on the right side with metrics for each category.
+
+Figure 6-1 – Structure of the requirements and evaluation methods of code generation based on the foundation model
+
+## 7 General capability
+
+### 7.1 Code understanding
+
+Code understanding refers to the ability of a large model to deeply understand the intent of the code and is a key capability of a code generation based on the foundation model. Code understanding usually takes code as input and natural language or its derivatives as output, with the goal of helping developers quickly understand code, including two sub abilities: code interpretation and code annotation.
+
+#### 7.1.1 Code summarization
+
+Code summarization refers to the generation of natural language to interpret input code or code files. Through code summarization, developers can better understand the structure and logic, implementation methods, functionality, and potential issues of the code, thereby quickly locating and solving problems, and improving development efficiency and code quality.
+
+- Input diversity: It is recommended to support generating reasonable natural language summarization content based on multiple inputs, e.g., line level, block level, function/class level, single file level, and multi-file level.
+
+- b) Task diversity: It is recommended to support generating reasonable natural language summarization content based on multiple tasks, e.g., generate more reasonable explanations for code through multiple rounds of dialogue, generate more reasonable explanations based on context, generate a complete and reasonable explanation based on the code file, and generate design documents based on project level code files.
+- c) Language completeness: It is recommended to support mainstream programming languages.
+
+#### 7.1.2 Code annotation
+
+Code annotation refers to the automatic addition of corresponding text comments in the code, which is used to explain the purpose, function, and implementation method of the code. By using code annotation, the readability and maintainability of the code can be improved, helping developers understand the logic and implementation of the code, and providing necessary guidance during code modification and refactoring.
+
+- a) Input diversity: It is recommended to support generating reasonable natural language annotation based on multiple inputs, e.g., line level, block level, function/class level, single file level, and multi-file level.
+- b) Language completeness: It is recommended to support mainstream programming languages.
+
+### 7.2 Code generation and completion
+
+Code generation and completion refers to the ability to automatically generate or complete the code based on the natural language or code input, with the goal of helping developers improve development efficiency, including two sub-abilities: code generation and code completion.
+
+#### 7.2.1 Code generation
+
+Code generation refers to the automatic generation of code based on the natural language or code input during the coding process. Through code generation, it can help developers automatically generate code and reduce technical barriers and development costs.
+
+- a) Task diversity: It is recommended to support generating complete functional code based on multiple tasks, e.g., generating complete functional code snippets (classes or functions) based on the natural language instructions or comments, function/class names, code context, generate complete functional code files (single file) based on the natural language instructions or document content, generate code files (multiple files) with complete logic and functionality based on the natural language instructions or document content.
+- b) Language completeness: It is recommended to support mainstream programming languages.
+
+#### 7.2.2 Code completion
+
+Code completion refers to the automatic completion of missing code based on the input of existing code when writing code. By completing code, developers can reduce spelling errors and search time, and improve coding efficiency.
+
+- a) Task diversity: It is recommended to support completion of code based on the multiple tasks, e.g., complete references by identifying potential references in the current code, complete full names based on incomplete function/class names, complete the remaining content of a line of code based on comments or partial code, complete the remaining content of a code snippet based on comments or partial code snippet, complete the remaining content of a function/class based on comments, or the function/class name and partial code.
+- b) Language completeness: It is recommended to support mainstream programming languages.
+
+### **7.3 Code transformation**
+
+Code transformation refers to the process of rewriting and converting source code to support different programming languages, environments, or architectures, while ensuring its original functionality. Both input and output are code. The goal is to help developers improve the efficiency of quickly converting code.
+
+- a) Coverage of transformation: It is recommended to support code transformation between multiple different programming languages and between different frameworks and environments.
+- b) Task diversity: It is recommended to support conversion of code based on multiple tasks, e.g., performing conversions at line level, block level, function/class level, single file level, and multi-file level.
+
+### **7.4 Unit test case generation**
+
+Unit testing refers to testing the basic components of the software. Unit test case generation refers to the automatic generation of unit test cases for testing a segment of code based on the input code. By generating unit test cases, developers can reduce the time spent writing unit test cases and improve test coverage and testing quality.
+
+- a) Task diversity: It is recommended to support the generation of unit test cases for code based on multiple tasks, e.g., generate unit test cases for code at the function level, generate unit test cases for code at the class level, and generate unit test cases for code at the file level.
+- b) Language completeness: It is recommended to support mainstream programming languages.
+
+### **7.5 Code diagnosis and optimization**
+
+Code diagnosis and optimization refer to the inspection of source code in terms of standardization, accuracy and security, identifying problems, providing repair suggestions, and optimizing them. The goal is to help developers improve code quality, including three sub abilities: code inspection, code repair, and code optimization.
+
+#### **7.5.1 Code diagnosis**
+
+Code diagnosis involves automatically checking inputted code or code files and outputting detected issues. Through code diagnosis, developers can promptly identify various problems within the code.
+
+- a) Input diversity: It is recommended to support diagnosis for code based on multiple inputs, e.g., line-level, block-level, function/class-level, single file-level, and logically related multi-file-level code.
+- b) Task diversity: It is recommended to support diagnosis for code based on multiple tasks, e.g., code standard compliance issues, code smells, syntax errors, logical errors, and security vulnerabilities.
+- c) Language completeness: It is recommended to support mainstream programming languages.
+
+#### **7.5.2 Code repair**
+
+Code repair involves automatically fixing defects in the code based on the results of code inspection. Through code repair, developers can swiftly address issues in the code to enhance its quality.
+
+- a) Input diversity: It is recommended to support repair based on multiple inputs, e.g., line-level, block-level, function/class-level, single file-level, and logically related multi-file-level code.
+- b) Task diversity: It is recommended to support repairing code based on multiple tasks, e.g., syntax errors, logical errors, code smells, and security vulnerabilities.
+- c) Language completeness: It is recommended to support mainstream programming languages.
+
+#### **7.5.3 Code optimization**
+
+Code optimization refers to actively optimizing and generating improved code based on the natural language instructions. Through code optimization, developers can quickly enhance code from multiple dimensions.
+
+- a) Input diversity: It is recommended to support optimization based on multiple inputs, e.g., line-level, block-level, function/class-level, single file-level, and logically related multi-file-level code.
+- b) Task diversity: It is recommended to support optimization based on multiple tasks, e.g., standardization optimization, performance optimization, and code refactoring.
+- c) Language completeness: It is recommended to support mainstream programming languages.
+
+## **8 Specialized scenario capability**
+
+### **8.1 Website development**
+
+- a) Task diversity: It is recommended to support various types of tasks for website development, e.g., user interface design, content management, and user login, based on the foundation model.
+- b) Website frontend framework: It is recommended to support multiple frontend frameworks for website development.
+- c) Website backend framework: It is recommended to support multiple backend development frameworks for website development.
+
+### **8.2 Desktop development**
+
+- a) Task diversity: It is recommended to support various types of tasks for desktop development, e.g., user interaction handling, content management, and data processing, based on the foundation model.
+- b) Desktop framework: It is recommended to support multiple frameworks for desktop development.
+
+### **8.3 Mobile application development**
+
+- a) Task diversity: It is recommended to support various types of tasks for mobile application development, e.g., permission management, log management, and message push, based on the foundation model.
+- b) Mobile application framework: It is recommended to support multiple frameworks for mobile application development.
+
+### **8.4 Artificial intelligence development**
+
+- a) Task diversity: It is recommended to support various types of tasks for artificial intelligence development, e.g., machine learning, computer vision, and natural language processing, based on the foundation model.
+- b) Artificial intelligence framework and tool: It is recommended to support multiple mainstream frameworks and tools for artificial intelligence development.
+
+### **8.5 Big data development**
+
+- a) Task diversity: It is recommended to support various types of tasks for big data development, e.g., user data cleaning, data transformation, and data analysis queries, based on the foundation model.
+- b) Language coverage: It is recommended to support multiple big data development languages.
+
+- c) Big data framework: It is recommended to support multiple processing frameworks for big data development.
+
+## **9 Supporting capability**
+
+### **9.1 Data supporting capability**
+
+#### **9.1.1 Data classification and grading**
+
+- a) Data type: It is recommended that the dataset be the object of data classification and grading, including code data, log data, and text data collected in the process of providing services.
+- b) Data classification: It is recommended that the data classification system be designed according to the business characteristics and technical requirements of the foundation model.
+- c) Data grading: It is recommended that the data grading system be designed according to the business characteristics and technical requirements of the foundation model, and different protection measures should be taken for different grades of data.
+- d) Regular audit: It is recommended that the classification and grading level of the data of the foundation model change due to changes in time, security events, and sensitivity of different business scenarios.
+
+#### **9.1.2 Data security and compliance**
+
+Data security:
+
+- a) Data transmission security: It is recommended that secure encrypted communication protocols be adopted during data transmission to protect the confidentiality and integrity of data.
+- b) Data storage security: It is recommended that data encryption methods be adopted in the data storage process.
+
+Data compliance:
+
+- a) Data source compliance: It is recommended that an establishment of a data source verification mechanism be set up to ensure that the data source is legitimate and compliant.
+- b) Data processing compliance: It is recommended that in the process of data processing, relevant laws, regulations and standards be strictly complied with.
+- c) Data utilization compliance: It is recommended that a review mechanism be set up to ensure lawful data use and compliance.
+
+### **9.2 Model supporting capability**
+
+#### **9.2.1 Accuracy**
+
+- a) Generalization: It is recommended that the foundation model should not overfit the training data.
+- b) Robustness: It is recommended that the model maintains its inference performance and accuracy when facing various challenges.
+- c) Error analysis and optimization: It is recommended that the accuracy of the foundation model be evaluated regularly, and that the accuracy of the model should be continuously improved.
+
+#### **9.2.2 Inference performance**
+
+- a) Single machine reasoning performance: It is recommended that the model have excellent inference performance in the single-node environment.
+
+- b) **Parallel inference performance:** It is recommended that the inference tasks in parallel inference mode should be assigned to multiple computer nodes through distributed technology.
+- c) **Resource utilization and inference cost:** It is recommended that the resource utilization and inference cost be manageable.
+- d) **Stability:** It is recommended that the consistency and reliability of the code model under different environments or long-term operation be stabilized.
+
+### **9.3 Service supporting capability**
+
+#### **9.3.1 Traceability**
+
+- a) **Training traceability:** It is recommended that the training process and metadata information of the foundation model be traceable.
+- b) **Deployment traceability:** It is recommended that the deployment process of the foundation model application services be traceable.
+- c) **Data traceability:** It is recommended that the training data information involved in the foundation model training and fine-tuning be traceable.
+- d) **Model traceability:** It is recommended that the model version and base model version of the foundation model service should be traceable, and the model be versioned.
+- e) **Service traceability:** It is recommended that the service invocation information of the foundation model be traced.
+
+#### **9.3.2 Risk controllability**
+
+- a) **External attack defence:** It is recommended that appropriate security measures be taken to prevent external attacks.
+- b) **Data protection:** It is recommended that relevant measures should be taken to protect user data and intellectual property rights.
+- c) **Dialogue attack defence:** It is recommended that measures should be taken to prevent dialogue attacks during the dialogue process of the foundation model application service.
+- d) **Model output control:** It is recommended that security vulnerability and risk analysis should be conducted on the output results of the foundation model.
+- e) **Continuous optimization:** It is recommended that a model risk assessment mechanism should be established, and risk control should be continuously optimized.
+
+#### **9.3.3 Maintainability**
+
+- a) **Deployment process:** It is recommended that deployment process specifications be established to ensure the correctness of the deployment process of the foundation model.
+- b) **Deployment environment:** It is recommended that deployment environment configuration standards be established to ensure the consistency of the foundation model's dependency on the environment.
+- c) **Deployment mode:** It is recommended to support multiple deployment mode.
+- d) **Operation and maintenance capabilities:** It is recommended to have certain operation and maintenance capabilities for foundation models and their services.
+- e) **High availability guarantee:** It is recommended that various mechanisms be established to ensure the normal operation of the foundation model services and high service quality.
+- f) **Scalability:** It is recommended to have the ability to flexibly shrink and expand resources and optimize and adjust them to provide stable services.
+
+- g) Compatibility: It is recommended that the foundation model be compatible with the business system, operating system, network environment, and hardware environment.
+- h) Feedback and optimization: It is recommended that a continuous improvement mechanism be established.
+
+## 10 Evaluation methods
+
+### 10.1 Evaluation metrics
+
+This part will define the evaluation metrics in the context of code generation based on the foundation models.
+
+#### 10.1.1 Normativity
+
+This metric is recommended to examine whether the generated code meets the requirements of general code norms.
+
+#### 10.1.2 Readability
+
+This metric is recommended to assess if the generated contents' structure is clear and highly readable.
+
+#### 10.1.3 Completeness
+
+This metric is recommended to check whether the generated text includes the function, purpose, main logic, and usage scenario of the code.
+
+#### 10.1.4 pass@k
+
+This metric is recommended to evaluate functional correctness with unit tests to judge the quality of the code generation.
+
+$$pass@k = E_{problems} \left[ 1 - \frac{\binom{n-c}{k}}{\binom{n}{k}} \right]$$
+
+$\binom{n-c}{k}$ : the number of ways to choose  $k$  samples from  $n-c$  incorrect samples
+
+$\binom{n}{k}$ : the number of ways to choose  $k$  samples from  $n$  samples.
+
+#### 10.1.5 CodeBLEU
+
+This metric is recommended to evaluate the similarity between the generated code and the reference code to judge the quality of the code generation.
+
+$$CodeBLEU = \alpha \cdot BLEU + \beta \cdot BLEU_{weight} + \gamma \cdot Match_{ast} + \delta \cdot Match_{df}$$
+
+*BLEU*: the lexical similarity between the hypothesis and reference code by calculating n-gram overlap. It focuses solely on the surface-level token matching without accounting for weighting, syntactic, or semantic information.
+
+*BLUE<sub>weight</sub>*: the weighted n-gram match, obtained by comparing the hypothesis code and the reference code tokens with different weights.
+
+*MATCH<sub>ast</sub>*: the syntactic AST match, exploring the syntactic information of code.
+
+*MATCH<sub>df</sub>*: the semantic data-flow match, considering the semantic similarity between the hypothesis and the reference.
+
+#### 10.1.6 ROUGE
+
+This metric is recommended to evaluate the similarity between the generated text and the reference text to judge the quality of the text generation.
+
+In this formula, recall is calculated after splitting the results generated by the model and the standard results by  $n$ -grams. The appropriate  $n$  is selected, and Rouge- $n$  is calculated as follows.
+
+$$Rouge-n = \frac{\sum_{S \in \{RefText\}} \sum_{gram_n \in S} Count_{match}(gram_n)}{\sum_{S \in \{RefText\}} \sum_{gram_n \in S} Count(gram_n)}$$
+
+$Count(gram_n)$ : the number of  $n$ -grams in the reference text collection.
+
+$Count_{match}(gram_n)$ : the maximum number of  $n$ -grams co-occurring in a candidate summary and a set of reference summaries.
+
+$RefText$ : the reference summary from text testing sets.
+
+### 10.2 Evaluation methods
+
+This part will define the actual method of conducting the evaluation.
+
+#### 10.2.1 Accuracy evaluation methods
+
+The method is to set up test datasets, then compare the generated content with the correct answers, and calculate the accuracy of the generated content using pass@k, CodeBLEU, ROUGE.
+
+#### 10.2.2 Acceptability evaluation methods
+
+The method assesses the acceptability of the generated content through the evaluation of normativity, readability, and completeness by experts.
+
+# Bibliography
+
+- [b-ITU-T F.749.13] Recommendation ITU-T F.749.13 (2021), *Framework and requirements for civilian unmanned aerial vehicle flight control using artificial intelligence.*
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.748.50-202503-I_PDF-E/raw.md b/marked/F/T-REC-F.748.50-202503-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..69b6e71a3089f644c8d66c84a38ba1f99fa4a375
--- /dev/null
+++ b/marked/F/T-REC-F.748.50-202503-I_PDF-E/raw.md
@@ -0,0 +1,380 @@
+
+
+# Recommendation
+
+## **ITU-T F.748.50 (03/2025)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+## --- **Framework and requirements of digital human access interfaces**
+
+![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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.748.50
+
+## Framework and requirements of digital human access interfaces
+
+## Summary
+
+Recommendation ITU-T F.748.50 specifies the framework and technical requirements for the digital human access interfaces in real applications including session connection management, system initialization, digital asset parsing, personalized customization, artificial intelligence (AI) capability invocation, body/facial driven interaction, rendering display and network transmission. This Recommendation can be used to guide relevant parties to implement and deploy digital human access systems in a standardized manner. A well-defined framework allows developers in the application layer to focus on creating user-facing features and use cases, while engineers working on the infrastructure layer can focus on optimizing and improving the underlying technologies.
+
+## History\*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.748.50 | 2025-03-16 | 21          | 11.1002/1000/16240 |
+
+## Keywords
+
+Access interface, access interface framework, access interface requirement, digital human.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <https://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                           | 1    |
+| 4 Abbreviations and acronyms .....                                      | 1    |
+| 5 Conventions .....                                                     | 2    |
+| 6 Digital human access interface framework.....                         | 2    |
+| 7 Requirements for the digital human access interface .....             | 4    |
+| 7.1 Session connection management interface technical requirements..... | 4    |
+| 7.2 System initialization interface technical requirements.....         | 4    |
+| 7.3 Digital asset parsing interface technical requirements .....        | 5    |
+| 7.4 Personalized customization interface technical requirements.....    | 5    |
+| 7.5 AI capability invocation interface technical requirements.....      | 6    |
+| 7.6 Body/facial driven interface technical requirements.....            | 6    |
+| 7.7 Rendering display interface technical requirements.....             | 7    |
+| 7.8 Network transmission interface technical requirements.....          | 7    |
+| Bibliography.....                                                       | 8    |
+
+
+
+# Recommendation ITU-T F.748.50
+
+## Framework and requirements of digital human access interfaces
+
+## 1 Scope
+
+This Recommendation describes the framework and requirements of digital human access interfaces, enabling developers to integrate the capabilities of digital humans into different applications in a standardized manner.
+
+The scope of this Recommendation includes:
+
+- Digital human access interface framework.
+- Requirements for digital human access 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.
+
+None.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following term defined elsewhere:
+
+**3.1.1 digital human** [b-ITU-T F.748.15]: A computer application that integrates the technologies of computer graphics, computer vision, intelligent speech, natural language processing. It can be used for digital content generation and human-computer interaction to help improve content production efficiency and user experience.
+
+### 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 digital human capability**: A service or functionality, such as creation, customization, interaction and rendering, that enables digital humans to operate within a digital environment.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|     |                                   |
+|-----|-----------------------------------|
+| 3D  | Three Dimensional                 |
+| AI  | Artificial Intelligence           |
+| API | Application Programming Interface |
+| CPU | Central Processing Unit           |
+| GPU | Graphics Processing Unit          |
+| RTC | Real-Time Communication           |
+
+|      |                              |
+|------|------------------------------|
+| RTMP | Real-Time Messaging Protocol |
+| SDK  | Software Development Kit     |
+| SSL  | Secure Sockets Layer         |
+| TLS  | Transport Layer Security     |
+
+## 5 Conventions
+
+In this Recommendation:
+
+The keywords "is required" indicate a requirement which must be strictly followed and from which no deviation is permitted if the conformance to this document is to be claimed.
+
+The keywords "is recommended" indicate a requirement which is recommended but not absolutely required. Thus, this requirement needn't be present to claim conformance.
+
+## 6 Digital human access interface framework
+
+The digital-human access interface framework is shown in Figure 1. It is divided into three main layers: application layer, interface layer and infrastructure layer. This Recommendation only focuses on the interface layer.
+
+The application layer accesses the digital human capabilities by calling the interface layer's application programming interface (API). The application layer receives user inputs, which may include modal data such as motion capture data, text, voice and images, and manages the presentation of outputs from the digital human capabilities. It also provides tailored user interfaces for different application scenarios.
+
+The interface layer is responsible for invoking the capabilities provided by the infrastructure layer in a standardized manner. It defines the standard usage patterns and specifies the required functionalities for each module. The interface layer is intended to provide a consistent API for the application layer to interact with, regardless of changes in the underlying infrastructure. It allows for easier updates and improvements to the underlying technologies without disrupting the entire system. It facilitates interoperability between different modules and potentially different software development kit (SDK) suppliers.
+
+The infrastructure layer at the bottom provides the essential foundational elements, including rendering engine, digital resources, artificial intelligence (AI) model and algorithm components, supporting the operations of the upper layers.
+
+![Figure 1 – Digital human access interface framework diagram showing three layers: Applications layer (top, dashed box), Interface layer (middle, solid box), and Infrastructure layer (bottom, dashed box). The Applications layer contains Digital assistant, Digital educator, Virtual streamer, and ... . The Interface layer contains eight modules: Session connection management interface, System initialization interface, Digital asset parsing interface, Personalized customization interface, AI capability invocation interface, Body/facial driven interface, Rendering display interface, and Network transmission interface. The Infrastructure layer contains Supplier 1, Supplier 2, Supplier 3, and Supplier N. Arrows indicate bidirectional flow between the Applications layer and the Interface layer, and between the Interface layer and the Infrastructure layer.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg)
+
+F.748.50(25)
+
+Figure 1 – Digital human access interface framework diagram showing three layers: Applications layer (top, dashed box), Interface layer (middle, solid box), and Infrastructure layer (bottom, dashed box). The Applications layer contains Digital assistant, Digital educator, Virtual streamer, and ... . The Interface layer contains eight modules: Session connection management interface, System initialization interface, Digital asset parsing interface, Personalized customization interface, AI capability invocation interface, Body/facial driven interface, Rendering display interface, and Network transmission interface. The Infrastructure layer contains Supplier 1, Supplier 2, Supplier 3, and Supplier N. Arrows indicate bidirectional flow between the Applications layer and the Interface layer, and between the Interface layer and the Infrastructure layer.
+
+**Figure 1 – Digital human access interface framework**
+
+NOTE – This Recommendation only focuses on the interface layer, shown in the solid-line box. The application layer and the infrastructure layer, which are shown as dashed-line boxes, are not in the scope of this Recommendation.
+
+The interface layer is recommended to contain eight crucial modules that enable the digital human's cognitive and interactive capabilities. The modules are the session connection management interface, system initialization interface, digital asset parsing interface, personalized customization interface, AI capability invocation interface, body/facial driven interface, rendering display interface and network transmission interface modules.
+
+The eight modules are described below:
+
+- Session connection management interface: It manages the establishment, maintenance and termination of connections between the user application and the backend system, ensuring a smooth and stable data flow throughout a session.
+- System initialization interface: It serves to prepare the necessary hardware and software environment for the digital human system, encompassing hardware compatibility checks, loading and initializing renderers, assets and AI models, as well as configuring scenes and animations.
+- Digital asset parsing interface: It is responsible for interpreting and processing digital assets used by the digital human, including interfaces for face model import, body model import, three dimensional (3D) clothes import, 3D hair import and skinning configurations import.
+- Personalized customization interface: It provides functional interfaces related to the specific appearance of the digital human, including face customization, body customization and cloth customization.
+- AI capability invocation interface: It standardizes the process of calling upon various AI models (e.g., natural language processing, decision-making algorithms and face recognition with user approval) to enhance the interaction between users and digital humans.
+- Body/facial driven interface: It includes interfaces for text-to-speech animation, voice/video driven facial animation and video driven skeletal animation.
+- Rendering display interface: It handles the visual output of the digital human system. It defines a flexible and comprehensive set of rendering display methods, including window
+
+management, resolution adjustment, frame control, debugging support, multi-display support and post-processing effects.
+
+- Network transmission interface: It is responsible for data transmission between application frontend and backend servers, including data compression, error correction and optimizing the data flow to ensure smooth operation even under varying network conditions.
+
+## **7 Requirements for the digital human access interface**
+
+### **7.1 Session connection management interface technical requirements**
+
+This interface is a component that ensures the smooth and secure operation of communication sessions between client applications and the backend digital human service. It includes handling authentication, session stability and data security, providing a reliable bridge for data exchange and interaction.
+
+R-7.1-01: The session connection management interface is required to implement secure authentication mechanisms to ensure that only authorized users can establish and maintain communication sessions.
+
+R-7.1-02: The session connection management interface is required to support functionalities for automatic session recovery and reconnection in the event of network instability or unexpected session disconnections, thereby ensuring a continuous and seamless user experience.
+
+R-7.1-03: The session connection management interface is required to encrypt all communications between the client and the server using secure sockets layer (SSL)/ transport layer security (TLS) protocols, safeguarding data security and integrity against potential man-in-the-middle attacks.
+
+RR-7.1-01: The session connection management interface is recommended to include mechanisms for managing session timeouts. This mechanism is used to notify the client upon session termination and clear session states on the server side to maintain operational integrity.
+
+RR-7.1-02: The session connection management interface is recommended to provide comprehensive error handling and log recording features.
+
+### **7.2 System initialization interface technical requirements**
+
+This interface is used to prepare the necessary environment for digital human representation. This interface encompasses a wide array of functions, from hardware detection to the initialization of rendering processes, ensuring that the digital human avatars are rendered correctly and interactively.
+
+R-7.2-01: The system initialization interface is required to detect if the terminal hardware meets the minimum requirements for digital human rendering, including the performance of the central processing unit (CPU), graphics processing unit (GPU) and memory.
+
+R-7.2-02: The system initialization interface is required to load the digital assets of the digital human, including models, textures and animations, ensuring the digital human avatar can be rendered correctly.
+
+R-7.2-03: The system initialization interface is required to initialize the renderer for the digital human, including setting rendering parameters and initializing the rendering pipeline, to prepare for the rendering of the digital human.
+
+R-7.2-04: The system initialization interface is required to set up the virtual scene for the digital human, including environmental lighting, background and camera angles, ensuring the rendering effect of the digital human.
+
+R-7.2-05: The system initialization interface is required to load and initialize the animation system of the digital human, for example, setting the animation playback rate and binding animation controllers.
+
+RR-7.2-01: The system initialization interface is recommended to initialize the interaction system of the digital human, including binding interaction events and setting interaction parameters.
+
+RR-7.2-02: The system initialization interface is recommended to load the AI models required by the digital human, including voice recognition, facial expression recognition and gesture recognition models, to ensure that the digital human can respond to interactions.
+
+RR-7.2-03: The system initialization interface is recommended to output the related initialization results and content to the interaction system for user verification of completeness.
+
+### **7.3 Digital asset parsing interface technical requirements**
+
+This interface is instrumental in enabling digital human applications by efficiently reading, parsing, and converting digital assets into usable data formats. This process is critical for ensuring high-quality rendering, optimal performance and engaging user experience.
+
+R-7.3-01: The digital asset parsing interface is required to support a wide range of asset formats, including the different formats of 3D models, animations, images and audio files, ensuring compatibility and flexibility across different types of digital human assets.
+
+R-7.3-02: The digital asset parsing interface is required to optimize the asset parsing and loading process to minimize application startup time and maximize response speed.
+
+R-7.3-03: The digital asset parsing interface is required to provide mechanisms for hot updates, asset caching, and version control, enabling applications to seamlessly update or modify digital human components without full redeployment.
+
+R-7.3-04: The digital asset parsing interface is required to provide copyright protection, ensuring the secure storage of digital assets to prevent unauthorized access and modification, along with copyright information parsing and verification functions for legal asset usage.
+
+RR-7.3-01: The digital asset parsing interface is recommended to support resource optimization and adaptation to accommodate devices with varying performance levels, including selecting resource versions based on device capabilities and supporting resource compression and decompression to minimize transmission and storage costs.
+
+RR-7.3-02: The digital asset parsing interface is recommended to include detailed error reporting and handling features, providing clear error information and recovery mechanisms, automatic retry loading and fallback to alternative resources, to assist developers in troubleshooting.
+
+### **7.4 Personalized customization interface technical requirements**
+
+The personalized customization interface plays a pivotal role in allowing users and developers to tailor various aspects of a digital human, such as appearance, behaviour and voice, for individual preferences.
+
+R-7.4-01: The personalized customization interface is required to offer a real-time preview feature, allowing users to instantly visualize the effects of their customization choices, thus enhancing user experience by facilitating quick adjustments and decision-making.
+
+R-7.4-02: The personalized customization interface is required to support efficient data processing feature, managing the significant data exchange and processing involved in personalize customization, especially when manipulating 3D models and high-resolution textures, to ensure a smooth customization process and minimized waiting times.
+
+R-7.4-03: The personalized customization interface is required to ensure compatibility and optimal performance across various platforms and devices, to guarantee a comprehensive and satisfactory customization experience for the users.
+
+R-7.4-04: The personalized customization interface is required to provide saving and loading functionality, enabling users to save their personalized customization configurations for future reuse and sharing across devices, supporting the persistent storage of user personalized settings.
+
+RR-7.4-01: The personalized customization interface is recommended to offer customization options, including but not limited to skin colour, hairstyle, eye colour, clothing, accessories and voice.
+
+### **7.5 AI capability invocation interface technical requirements**
+
+This interface is essential for facilitating user interactions with various AI capabilities, requiring swift responses, robust error handling and stringent security measures.
+
+R-7.5-01: The AI capability invocation interface is required to respond quickly to the user inputs to ensure a satisfactory user experience. For text-based interactions, response times should be within a few hundred milliseconds, while voice conversations are required to offer real-time voice recognition and rapid response generation.
+
+R-7.5-02: The AI capability invocation interface is required to have robust error handling capabilities, offering clear feedback and guidance for inputs or requests that are not understood, thus facilitating more effective user interactions.
+
+R-7.5-03: The AI capability invocation interface design is required to prioritize the security of data transmission, storage and processing to safeguard user confidentiality and data integrity.
+
+RR-7.5-01: The AI capability invocation interface is recommended to enable developers to tailor the digital human's behaviour and responses to fit specific use cases, including customizing question and answer sets, dialogue strategies and integrating specialized knowledge bases.
+
+RR-7.5-02: The AI capability invocation interface is recommended to support various input modalities, including text, voice and images, processing them into meaningful commands or queries for the digital human.
+
+RR-7.5-03: The AI capability invocation interface is recommended to facilitate multilingual interactions, featuring automatic language detection, translation and localized responses for global users.
+
+### **7.6 Body/facial driven interface technical requirements**
+
+This interface is crucial for translating human inputs (e.g., voice, expressions, and movements) into corresponding digital human responses and actions, enabling a natural interaction experience.
+
+R-7.6-01: The body/facial driven interface is required to process inputs in real-time and with low latency, ensuring quick response times for a smooth interaction experience. This includes handling voice, expressions and movements with minimal delay.
+
+R-7.6-02: The body/facial driven interface is required to demonstrate high accuracy. This encompasses the ability to accurately parse voice commands across various languages and dialects, as well as facial expressions and motion capture data in different environmental conditions.
+
+R-7.6-03: The body/facial driven interface is required to exhibit a degree of error tolerance, providing accurate responses even when inputs are unclear or partially lost.
+
+R-7.6-04: The body/facial driven interface is required to ensure security and privacy protection. All data transmissions, including voice and video streams, need to be encrypted using secure protocols.
+
+RR-7.6-01: The body/facial driven interface is recommended to support multimodal fusion, that is the integrated processing of multiple inputs to generate natural and accurate interactive responses.
+
+### **7.7     Rendering display interface technical requirements**
+
+This interface is instrumental in rendering digital human components, ensuring compatibility across diverse platforms, optimizing performance and maintaining high-quality output alongside robust security measures.
+
+R-7.7-01: The rendering display interface is required to function across multiple platforms and operating systems, guaranteeing consistent rendering effects across various devices and operating systems, even cloud rendering.
+
+R-7.7-02: The rendering display interface is required to ensure rendering performance, including support for an efficient graphics rendering pipeline, and maintaining rendering frame rates at 30 FPS or higher for a smooth user experience.
+
+R-7.7-03: The rendering display interface is required to provide detailed error reporting and implement recovery mechanisms for rendering errors or exceptions to prevent application disruptions.
+
+RR-7.7-01: The rendering display interface is recommended to support multi-display rendering, enabling seamless visualization across multiple screens for enhanced user experiences.
+
+RR-7.7-02: The rendering display interface is recommended to support high-resolution rendering and incorporate advanced graphical effects, including lighting, shadows, reflections and anti-aliasing, to ensure superior image quality.
+
+### **7.8     Network transmission interface technical requirements**
+
+This interface facilitates the secure and efficient transmission of data between digital human applications and servers, which is critical for handling various types of data, including real-time audio and video streams, motion capture data and AI-driven response outputs.
+
+R-7.8-01: The network transmission interface is required to employ mechanisms (e.g., hashing or digital signatures) to confirm the integrity of transmitted data, ensuring it remains unchanged during transit.
+
+R-7.8-02: The network transmission interface is required to support resume-on-break functionality for large data transmissions, allowing continuation from the last point after a disconnection.
+
+R-7.8-03: The network transmission interface is required to implement automatic retry mechanism to reconnect in case of network instability or failures, adhering to a configurable limit to prevent excessive attempts.
+
+R-7.8-04: The network transmission interface is required to provide users with progress feedback for long-duration data transmission operations to enhance the user experience.
+
+RR-7.8-01: The network transmission interface is recommended to support advanced real-time communication (RTC) functionality for applications necessitating low latency and real-time interaction.
+
+RR-7.8-02: The network transmission interface is recommended to support real-time messaging protocol (RTMP) for applications aimed at large-scale audience distribution.
+
+## Bibliography
+
+- [b-ITU-T F.748.15] Recommendation ITU-T F.748.15 (2022), *Framework and metrics for digital human application 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.748.51-202503-I_PDF-E/raw.md b/marked/F/T-REC-F.748.51-202503-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..af83c4a9c39c32b8521a62eeac904a3962516ef6
--- /dev/null
+++ b/marked/F/T-REC-F.748.51-202503-I_PDF-E/raw.md
@@ -0,0 +1,501 @@
+
+
+# Recommendation **ITU-T F.748.51 (03/2025)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+## --- **Requirements for artificial intelligence-based tactile rendering system in multimedia terminals**
+
+![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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.748.51
+
+# Requirements for artificial intelligence-based tactile rendering system in multimedia terminals
+
+## Summary
+
+Recommendation ITU-T F.748.51 describes the architecture of an artificial intelligence-based tactile rendering system (TRS) for multimedia terminals. It defines a layered system architecture, consisting of the device layer, service layer and application layer. This Recommendation also specifies key requirements related to data management, algorithm design, system stability, and implementation methods. The Recommendation provides guidance for AI-based tactile rendering system in multimedia terminals to facilitate the research and development aimed at creating intelligent, user-centric systems that enhance operational comfort, immersive interaction, and technological innovation.
+
+## History\*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.748.51 | 2025-03-16 | 21          | 11.1002/1000/16241 |
+
+## Keywords
+
+Artificial intelligence (AI), framework, multimedia terminal, requirements, tactile rendering system (TRS).
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <https://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                                                    | 2    |
+| 6 Overview of AI-based tactile rendering systems in multimedia terminals.....                          | 2    |
+| 7 Framework and general process of AI-based tactile rendering systems in<br>multimedia terminals ..... | 3    |
+| 7.1 Framework of AI-based TRS in MTs.....                                                              | 3    |
+| 7.2 General process of AI-based TRS in MTs .....                                                       | 5    |
+| 8 Requirements for AI-based tactile rendering systems in multimedia terminals.....                     | 5    |
+| 8.1 Requirements for data management .....                                                             | 5    |
+| 8.2 Requirements for AI algorithm .....                                                                | 6    |
+| 8.3 Requirements for AI-based tactile rendering stability assurance .....                              | 8    |
+| 8.4 Requirements for implementation equipment .....                                                    | 8    |
+| 8.5 Requirements for tactile rendering implementation methods .....                                    | 8    |
+| 8.6 Requirements for application scenario .....                                                        | 8    |
+| 8.7 Requirements for implementing functionalities .....                                                | 9    |
+| Appendix I – Use cases of an AI-based texture rendering system in multimedia terminal<br>(TRSMT) ..... | 10   |
+| I.1 Use case of virtual games .....                                                                    | 10   |
+| I.2 Use case of medical treatment.....                                                                 | 10   |
+| I.3 Use case of blind assistance .....                                                                 | 11   |
+| I.4 Use case of consumer electronics.....                                                              | 11   |
+| Bibliography.....                                                                                      | 13   |
+
+
+
+# Requirements for artificial intelligence-based tactile rendering system in multimedia terminals
+
+## 1 Scope
+
+This Recommendation describes the requirements and framework of AI-based tactile rendering systems for multimedia terminals. It addresses the following subjects:
+
+The scope of the new work item is proposed to include these aspects:
+
+- Overview of AI-based tactile rendering systems for multimedia terminals;
+- Framework and general process of AI-based tactile rendering systems for multimedia terminals;
+- Requirements for AI-based tactile rendering systems in multimedia terminals.
+
+## 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 artificial intelligence** [b-ITU-T F.749.13]: An interdisciplinary field, usually regarded as a branch of computer science, dealing with models and systems for the performance of functions generally associated with human intelligence, such as reasoning and learning.
+
+**3.1.2 algorithm** [b-ITU-T F.740.7]: A set of rules for transforming the logical representation of data.
+
+**3.1.3 application** [b-ITU-T Y.101]: A structured set of capabilities, which provide value-added functionality supported by one or more services.
+
+**3.1.4 machine learning** [b-ITU-T Y.3172]: Processes that enable computational systems to understand data and gain knowledge from it without necessarily being explicitly programmed.
+
+**3.1.5 model** [b-ITU-T F.748.16]: An output created by an algorithm running on training data that can generate an inference or prediction, based on input data.
+
+**3.1.6 tactile** [b-ITU-T H.430.6]: Tactile appertains to touch.
+
+**3.1.7 virtual reality** [b-ITU-T P.1320]: An environment that is fully generated by digital means. To qualify as virtual reality, the virtual environment should differ from the local environment.
+
+**3.1.8 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 perceptual threshold:** The minimum intensity of a stimulus signal required for users to perceive tactile sensations.
+
+**3.2.2 tactile preconfigured information:** Predetermined tactile feedback generated by the system to maintain continuous and stable tactile rendering when real-time data transmission is interrupted.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|       |                                                 |
+|-------|-------------------------------------------------|
+| AI    | Artificial Intelligence                         |
+| API   | Application Programming Interface               |
+| AR    | Augmented Reality                               |
+| CNN   | Convolutional Neural Network                    |
+| GAN   | Generative Adversarial Network                  |
+| LSTM  | Long Short-Term Memory                          |
+| MT    | Multimedia Terminal                             |
+| MTR   | Multimodal Tactile Rendering                    |
+| TRS   | Texture Rendering System                        |
+| TRSMT | Texture Rendering System in Multimedia Terminal |
+| VR    | Virtual Reality                                 |
+
+## 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 Overview of AI-based tactile rendering systems in multimedia terminals
+
+The advancement of artificial intelligence (AI) has significantly transformed tactile rendering in multimedia terminals (MTs), enabling the creation of more immersive and realistic user experiences. An AI-based texture rendering system (TRS) allows users to interact with virtual environments through highly detailed tactile feedback, enhancing realism and operational comfort.
+
+In traditional tactile rendering approaches, the reliance on physical simulations often results in limited variability and inconsistent spatial experiences. An AI-based TRS addresses these challenges by leveraging machine learning models and vast data repositories to generate realistic tactile feedback dynamically. For example, in online shopping, an AI-driven TRS enables users to "feel" the textures of fabrics or materials through their devices, improving consumer engagement and decision-making.
+
+Furthermore, an AI-based TRS enhances tactile perception, including texture, shape, and roughness. By analysing data in real-time and dynamically adapting the rendering output, these systems improve the user's immersion in digital experiences. Applications in fields like gaming, medical training, and education demonstrate the transformative potential of AI-driven tactile feedback in MTs, making them indispensable tools for both professional and recreational purposes.
+
+The AI-based TRS in multimedia terminals is built on a comprehensive framework designed to provide realistic tactile feedback through three core layers: the device layer, responsible for tactile data collection and feedback delivery; the service layer, which handles data processing, modelling, and mapping tactile inputs to outputs; and the application layer, where customized tactile experiences are integrated into various scenarios such as gaming, medical training, and online shopping. This layered architecture ensures seamless interaction, real-time responsiveness, and adaptability across diverse applications. The system also defines detailed requirements to ensure its functionality and effectiveness. These include a robust data management process for collecting, annotating, and processing tactile data, AI-driven algorithm requirements to map tactile stimuli to perceptions, and mechanisms for stability assurance to address potential disruptions in tactile feedback transmission. Additionally, it outlines the specifications for implementation equipment, such as wearable devices and touchscreens, and recommends multimodal methods like mechanical vibration or electrovibration for tactile rendering. The system is tailored to meet the demands of various application scenarios, ensuring enhanced user experience, real-time performance, and safety. This integrated framework and requirements enable the AI-based TRS to deliver immersive, realistic, and versatile tactile interactions, paving the way for innovative applications across industries.
+
+## **7 Framework and general process of AI-based tactile rendering systems in multimedia terminals**
+
+### **7.1 Framework of AI-based TRS in MTs**
+
+Figure 7-1 shows the framework of AI-based TRS in MTs.
+
+![Figure 7-1 – Framework of AI-based TRS for MTs. The diagram shows three layers: Application layer, Service layer, and Device layer. The Application layer includes Application fields (Medical treatment, Blind assistance, Consumer electronics, Distance education, Skill training, Visual games, ...) and Tactile rendering (Texture roughness, Texture shape, Texture softness, Texture smoothness). The Service layer includes Algorithm components (Image recognition, Image classification, Data classification, Data prediction, Image generation, ...), Algorithm management components (Algorithm warehouse, Algorithm training), and Data preprocessing (Data cleaning, Data annotation, Data transformation, Data association). The Device layer includes Photographic equipment, Signal generator, Computer unit, Positioning device, Touchscreen, LCD, and ...](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg)
+
+The diagram illustrates the framework of AI-based TRS for MTs, organized into three hierarchical layers:
+
+- Application layer**
+  - Application fields**: Medical treatment, Blind assistance, Consumer electronics, Distance education, Skill training, Visual games, ...
+  - Tactile rendering**: Texture roughness, Texture shape, Texture softness, Texture smoothness
+- Service layer**
+  - Algorithm components**: Image recognition, Image classification, Data classification, Data prediction, Image generation, ...
+  - Algorithm management components**: Algorithm warehouse, Algorithm training
+  - Data preprocessing**: Data cleaning, Data annotation, Data transformation, Data association
+- Device layer**
+  - Photographic equipment, Signal generator, Computer unit, Positioning device, Touchscreen, LCD, ...
+
+F.748.51(25)
+
+Figure 7-1 – Framework of AI-based TRS for MTs. The diagram shows three layers: Application layer, Service layer, and Device layer. The Application layer includes Application fields (Medical treatment, Blind assistance, Consumer electronics, Distance education, Skill training, Visual games, ...) and Tactile rendering (Texture roughness, Texture shape, Texture softness, Texture smoothness). The Service layer includes Algorithm components (Image recognition, Image classification, Data classification, Data prediction, Image generation, ...), Algorithm management components (Algorithm warehouse, Algorithm training), and Data preprocessing (Data cleaning, Data annotation, Data transformation, Data association). The Device layer includes Photographic equipment, Signal generator, Computer unit, Positioning device, Touchscreen, LCD, and ...
+
+**Figure 7-1 – Framework of AI-based TRS for MTs**
+
+The framework of AI-based TRS in multimedia terminals (MTs) consists of three layers: the device layer, the service layer and the application layer.
+
+**Device layer:** This is the foundational layer of the system, which provides the hardware components for tactile rendering in multimedia terminals. This layer includes equipment such as photographic equipment, computer units, signal generators, positioning devices, touchscreens, and liquid crystal displays (LCDs). These hardware components work together to support data collection, the generation of tactile feedback signals, and the realization of user interaction interfaces.
+
+**Service layer:** The service layer is responsible for data processing, and algorithm support. It includes data preprocessing, algorithm management components, and algorithm components. Data preprocessing comprises data cleaning, data annotation, data transformation, and data association, ensuring the quality and consistency of the input data. Algorithm management components provide algorithm management functions, achieving algorithm optimization and management through algorithm training and an algorithm warehouse, ensuring the intelligent operation of the system. Algorithm components offer functionalities such as image recognition, image classification, data classification, data prediction, and image generation.
+
+**Application layer:** The application layer focuses on the system's practical tactile rendering capabilities and application scenarios. The tactile rendering functionality supports precise feedback on texture properties such as roughness, shape, softness, and smoothness. The application fields include various areas such as medical treatment, blind assistance, consumer electronics, distance education, skill training, and visual games.
+
+### 7.2 General process of AI-based TRS in MTs
+
+Figure 7-2 shows the general process of AI-based TRS in MTs.
+
+![Flowchart of the general process of AI-based TRS in MTs. The process starts with 'Create dataset' leading to 'Data preprocessing', and 'Threshold experience' leading to 'Stimuli amplitude of the tactile perception'. Both lead to 'Tactile rendering system', which also receives 'Texture data'. The output of 'Tactile rendering system' is 'Stimulus signal', which leads to 'Multimedia terminal tactile rendering'. A reference code F.748.51(25) is shown in the bottom right.](e9314c83043183351ed74908e9bf2f90_img.jpg)
+
+```
+graph LR; A[Create dataset] --> B[Data preprocessing]; C[Threshold experience] --> D[Stimuli amplitude of the tactile perception]; B --> E[Tactile rendering system]; D --> E; F[Texture data] --> E; E --> G[Stimulus signal]; G --> H[Multimedia terminal tactile rendering];
+```
+
+F.748.51(25)
+
+Flowchart of the general process of AI-based TRS in MTs. The process starts with 'Create dataset' leading to 'Data preprocessing', and 'Threshold experience' leading to 'Stimuli amplitude of the tactile perception'. Both lead to 'Tactile rendering system', which also receives 'Texture data'. The output of 'Tactile rendering system' is 'Stimulus signal', which leads to 'Multimedia terminal tactile rendering'. A reference code F.748.51(25) is shown in the bottom right.
+
+**Figure 7-2 – General process of AI-based TRS in MTs**
+
+The general process is as follows:
+
+- Use specialized devices equipped with relevant sensors to collect normal force, acceleration, and other data when moving on textured surfaces to construct a numerical dataset.
+- Use professional photography equipment to capture texture images, and use a surface morphology analyser to generate surface morphology images corresponding to material textures to construct an image dataset.
+- For image data collection, create a dataset containing different image data.
+- Perform data preprocessing, extract data features, and classify them to make the data suitable for subsequent modelling.
+- Determine the thresholds of tactile perception through experiments, including absolute threshold and difference threshold experiments.
+- Obtain the proportional relationship between human texture perception and stimulus amplitude through threshold experiments.
+- Generate corresponding stimulus signals for the tactile data requiring tactile rendering. Transmit the stimulus signals to a multimedia terminal for tactile rendering.
+
+## 8 Requirements for AI-based tactile rendering systems in multimedia terminals
+
+### 8.1 Requirements for data management
+
+Figure 8-1 shows the general process of data management.
+
+![Flowchart of the general process of data management. The process consists of four sequential steps: 'Data collection' -> 'Data preprocessing' -> 'Data annotation' -> 'Dataset'. A reference code F.748.51(25) is shown in the bottom right.](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg)
+
+```
+graph LR; A[Data collection] --> B[Data preprocessing]; B --> C[Data annotation]; C --> D[Dataset];
+```
+
+F.748.51(25)
+
+Flowchart of the general process of data management. The process consists of four sequential steps: 'Data collection' -> 'Data preprocessing' -> 'Data annotation' -> 'Dataset'. A reference code F.748.51(25) is shown in the bottom right.
+
+**Figure 8-1 – General process of data management**
+
+The general progress of data management comprises data collection, data preprocessing, data annotation and dataset.
+
+#### 8.1.1 Requirements for data collection
+
+- For numerical data collection, it is required to use specialized devices equipped with relevant sensors to capture normal force, acceleration, and other data when moving across surface textures.
+- For image data, it is required to use professional photography equipment for image capture and use a surface morphology analyser to generate surface morphology images.
+
+#### **8.1.2 Requirements for data preprocessing**
+
+- Data cleaning is required to handle missing values, outliers, and duplicate data.
+- Data is required to be transformed into suitable formats or units, such as date format conversion.
+- For numerical data, it is recommended to consider data reduction through feature selection or dimensionality reduction.
+- For image data, data reduction through feature selection or dimensionality reduction is recommended.
+
+#### **8.1.3 Requirements for data annotation**
+
+- It is required to define clear annotation rules and standards to ensure consistency.
+- It is recommended that appropriate annotation tools or platforms be chosen to simplify the process.
+- It is required to annotate data according to defined standards using manual, semi-automatic, or automatic methods.
+- It is required to evaluate annotation quality to ensure accuracy and consistency.
+
+#### **8.1.4 Requirements for dataset**
+
+- It is required to save the prepared dataset to suitable storage media such as databases, file systems, or cloud storage.
+- It is required to support multiple data import methods, including databases, local uploads, and application programming interfaces (APIs).
+- It is required to collect datasets from multiple sources, such as public and private datasets.
+- It is recommended to perform feature engineering to extract and generate useful features for modelling.
+- It is required to support batch data import.
+- It is required to support real-time data import.
+- It is required to provide a detailed description of the dataset, including data sources, collection methods, variable definitions, and data formats.
+- It is required to provide download links or APIs for users to access data.
+- It is recommended to set appropriate access permissions to ensure data is accessed only by authorized users.
+- It is recommended to release the dataset on selected platforms and notify potential users.
+- It is required to maintain released datasets by updating and correcting data errors promptly.
+- It is required to regularly release new versions of datasets, including the latest data and updated information.
+
+### **8.2 Requirements for AI algorithm**
+
+#### **8.2.1 Requirements for creating the mapping relationship between tactile stimulus signals and tactile perception**
+
+- It is required to conduct an absolute threshold detection experiment of the tactile stimulus signals on the subjects to determine the minimum stimulus signal intensity that elicits a tactile sensation in the subjects.
+- It is required to conduct a differential threshold experiment on the tactile perception signals on the subjects to determine the minimum stimulus signal intensity interval that causes the subjects to perceive a change in stimulus intensity after a tactile sensation is elicited.
+
+- It is required to conduct tactile stimulus amplitude experiments on the subjects with minimum stimulus signal obtained from absolute threshold experiments as the initial value and the minimum stimulus signal intensity interval obtained from difference threshold experiments as the intensity interval.
+
+NOTE – This is done to determine the corresponding tactile perception intensity for each subject at different stimulus intensities.
+
+- It is required to fit the tactile perception intensity corresponding to the subjects at different stimulus intensities to determine the mapping relationship between the tactile perception intensity and the tactile stimulus signals.
+
+#### **8.2.2 Requirements for implementing tactile rendering based on numerical data**
+
+- It is required to employ machine learning algorithms to train the mapping relationship between numerical tactile data and tactile stimulus signals. The model takes tactile data as input and outputs tactile stimulus signals.
+
+#### **8.2.3 Requirements for implementing tactile rendering for known textures based on image data**
+
+- It is recommended to use a convolutional neural network (CNN) to train the mapping relationship between texture images and material surface topography images.
+- It is required to establish a library of material surface topography textures.
+- It is required to use image recognition algorithms to find the corresponding surface topography images in the image texture library, and then obtain the tactile stimulus signal.
+
+#### **8.2.4 Requirements for implementing tactile rendering for unknown textures based on image data**
+
+- It is required to use generative neural network models, such as generative adversarial networks (GANs), for image generation.
+- It is required to obtain training material texture images and their corresponding surface morphology images.
+
+NOTE – The process involves processing the training material texture images through the generator in the generative neural network model to generate predicted surface topography images corresponding to the training material texture images. The discriminator is used to compare the predicted surface morphology images with the actual surface morphology images. This is done to determine the probability that the predicted surface morphology image is the real surface morphology image corresponding to the training material texture image. Train the discriminator and the generator of the network model using this probability so that the predicted surface morphology images generated by the generator correspond to the real surface morphology images of the training material texture images.
+
+- It is required to obtain the target mapping relationship between surface morphology images and tactile stimulus signals. Subsequently, acquire the tactile stimulus signals corresponding intensity to the material surface morphology images according to the target mapping relationship.
+- To obtain the tactile stimulus signal intensity corresponding to the surface morphology images, firstly it is required to get the texture gradient curve corresponding to the surface morphology images. Next, it is required to obtain the mapping relationship between the texture gradient curve and tactile perception intensity. Finally, it is required to acquire the mapping relationship between tactile perception intensity and tactile stimulus signals.
+- It is required to provide tactile feedback based on stimulus signal intensity to simulate the touch sensation when interacting with the texture.
+
+### **8.3 Requirements for AI-based tactile rendering stability assurance**
+
+The timely and effective reception of tactile information by the receiver is crucial for ensuring the quality of tactile rendering. During the transmission of tactile information, if the transmission network is disrupted by interference, it may result in the loss, errors, or delays of tactile signals at the information-receiving end, leading to interruptions in information perception or unexpected operational issues at the receiving end. It is required to generate tactile preconfigured information based on AI to further ensure the stability of tactile rendering.
+
+- It is required to determine whether the information receiver has received the next frame of tactile information within the preset interval.
+- It is required to determine whether the next frame of tactile information received by the receiver within the preset time is erroneous.
+- The tactile information is required to be decoded and applied to tactile reproduction when the receiver receives the correct tactile information within the preset time.
+- It is required to obtain tactile preconfigured information, when the receiver fails to receive the next frame of tactile information within the preset interval, or receives erroneous information within the preset time.
+- It is required to use artificial intelligence algorithms, such as models like long short-term memory (LSTM) and previous tactile information, to create a generation model for tactile preconfigured information.
+- It is required to decode the tactile preconfigured information and substitute the decoded tactile preconfigured information for the next frame of tactile information for tactile rendering.
+- Various multimedia devices used for implementing tactile rendering is required to have different sets of components and features.
+
+### **8.4 Requirements for implementation equipment**
+
+- Tactile rendering can optionally be achieved using wearable equipment, including tactile gloves, tactile vests, tactile masks, tactile shoes, and other tactile devices. Wearable tactile rendering equipment is required to possess tactile sensors or sensor arrays with high resolution, high sensitivity, high temporal precision, and multiple sensing modalities.
+- Tactile rendering can optionally be achieved using touchscreen equipment. The touchscreen system is required to consist of a driver unit, a processing unit, an interaction unit, and a positioning unit.
+
+### **8.5 Requirements for tactile rendering implementation methods**
+
+- It is recommended to use methods such as mechanical vibration, electrovibration, squeeze film effect, pneumatic braking, etc., to achieve tactile rendering.
+- When combining multiple methods to generate tactile stimulus signals for achieving multimodal tactile rendering, it is required to conduct prior testing of the masking effects between the tactile rendering implementation methods.
+
+### **8.6 Requirements for application scenario**
+
+Tactile rendering can be applied in various scenarios, careful consideration of hardware and technological feasibility, user experience, cost-effectiveness, and safety factors is essential when selecting its application. Appropriate scenarios should meet these requirements to ensure that tactile rendering can truly provide value to users and enhance their experiences.
+
+- As tactile rendering is often used in conjunction with virtual environments such as Virtual Reality (VR) and Augmented Reality (AR). The infrastructure and technology are required to support virtual environments, allowing users to experience authentic tactile sensations.
+- Tactile rendering application is required to use hardware devices to achieve tactile feedback, such as tactile gloves and vibration feedback devices, and these devices are required to adhere to safety standards and comfort considerations.
+- Tactile rendering technology may involve data collection and privacy concerns. The application scenario is required to ensure compliance with privacy policies.
+- The application scenario is recommended to have sufficient computational capabilities to meet the real-time or near-real-time generation of tactile feedback.
+- The application scenario is recommended to possess conditions that provide high reliability and low latency for tactile communication, in order to meet the requirements for transmitting tactile signals and achieving remote tactile rendering functionality.
+
+### 8.7 Requirements for implementing functionalities
+
+The versatility of tactile rendering applications serves as a potent tool for improving user experiences and driving technological innovation.
+
+- It is recommended to apply tactile rendering in virtual reality (VR) and augmented reality (AR) applications. Tactile rendering can enhance users' immersion and interactive experiences. Users can perceive tactile feedback from the virtual world, such as sensing the texture, shape, and movement of objects.
+- It is recommended to apply tactile rendering in remote operation and control, such as controlling robots in hazardous environments. Real-time tactile feedback provided by tactile rendering allows operators to more accurately perceive the conditions of their actions.
+- In the medical field, it is recommended to apply tactile rendering in medical training and surgical simulation. Physicians can experience the tactile sensations of surgical procedures in virtual environments, thereby enhancing training effectiveness and surgical skills.
+- Tactile rendering is recommended to apply in education and training. Tactile rendering can enhance educational experiences, enabling students to gain a deeper understanding of instructional materials. For instance, students can touch and sense the attributes of virtual objects, enhancing their comprehension.
+- It is recommended to apply tactile rendering in entertainment and gaming. Tactile rendering can add interactivity and immersion to entertainment and gaming experiences. Players can feel tactile feedback from in-game objects, actions, and events, enhancing the enjoyment of games.
+- It is recommended to apply tactile rendering in artistic and creative expression, allowing artists to convey emotions and ideas through tactile sensations.
+- Wearable technology is recommended to facilitate more natural human-computer interactions through tactile rendering, as seen in smartwatches, wearable devices, and other applications.
+- It is recommended to apply tactile rendering in assistive technology. For individuals with visual or auditory impairments, tactile rendering can provide supplementary information and sensations, aiding them in better understanding their environment and interacting with the world.
+
+## Appendix I
+
+### Use cases of an AI-based texture rendering system in multimedia terminal (TRSMT)
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### I.1 Use case of virtual games
+
+In this use case (Figure I.1), tactile rendering in virtual games significantly enhances player immersion and the gaming experience. Through tactile feedback technology, game controllers provide real-time tactile responses such as vibrations, pressure, and touch, allowing players to feel every action and event in the game. For example, in racing games, players can feel the vibrations and impacts of different road surfaces, and in shooting games, they can feel the realistic touch of firing and being hit. Additionally, virtual reality (VR) game devices through tactile gloves and touch devices provide richer and more refined tactile feedback, allowing players to touch and feel the shapes, textures, and weights of virtual objects in the virtual environment. This tactile feedback not only enhances the realism and interactivity of the game but also increases player engagement and satisfaction. Overall, the application of tactile rendering in virtual games can bring players an unprecedented immersive experience, greatly enhancing the entertainment and appeal of the games.
+
+![A person wearing a VR headset and holding a controller, interacting with a virtual environment.](a4d009d5dd6a4d83759d6d6538188e23_img.jpg)
+
+A person wearing a VR headset and holding a controller, interacting with a virtual environment. The person is shown from the back, wearing a black VR headset and a black t-shirt. They are holding a white VR controller in their right hand, which is raised towards a virtual display. The display shows a dark, futuristic scene with a car and some glowing blue lines. The person's left hand is also visible, holding another controller.
+
+A person wearing a VR headset and holding a controller, interacting with a virtual environment.
+
+Figure I.1 – Use cases of virtual games
+
+### I.2 Use case of medical treatment
+
+In the medical field, tactile rendering technology significantly improves surgical training and rehabilitation treatment by providing precise tactile feedback. Surgeons can perform surgical simulations using TRSs that replicate the fine tactile sensations experienced during actual surgeries. This helps surgeons enhance their operational accuracy and sensitivity during training, thereby reducing risks in real surgeries. In rehabilitation treatment, tactile rendering devices offer virtual rehabilitation training, guiding patients through specific movements with tactile feedback, and adjusting training plans in real time to promote recovery. Additionally, in telemedicine, doctors can feel patients' physiological feedback through tactile rendering devices, providing more accurate diagnostic opinions. Tactile rendering plays a crucial role in medical treatment, enhancing the precision of medical operations and the effectiveness of treatments (Figure I.2).
+
+![A person wearing a VR headset and holding a robotic arm, interacting with a computer monitor displaying a 3D model of a human organ.](ac852a162572ca8a8c8478c49b571af5_img.jpg)
+
+A person wearing a VR headset and a purple shirt is interacting with a robotic arm. The robotic arm is positioned over a table, and the person is holding a handle on the arm. In the background, a computer monitor displays a 3D model of a human organ, likely for medical training or simulation.
+
+A person wearing a VR headset and holding a robotic arm, interacting with a computer monitor displaying a 3D model of a human organ.
+
+**Figure I.2 – Use cases of medical treatment**
+
+### **I.3 Use case of blind assistance**
+
+Tactile rendering technology shows great potential in the field of blind assistance by providing tactile feedback to help visually impaired individuals better understand and adapt to their surroundings. Navigation assistance systems, connected to smartphones or navigation systems, offer real-time path tactile feedback, ensuring the safe travel of blind individuals. In information reading, tactile rendering devices can convert e-books or text information into tactile signals, allowing blind people to read text by touching the device, greatly facilitating information access. In object recognition, tactile gloves or tactile pads can convert the information captured by cameras into tactile signals, helping blind individuals identify and perceive objects in their environment. These applications significantly improve the autonomy of blind individuals, enhancing their safety and independence (Figure I.3).
+
+![A close-up of a tactile map device, showing a raised, textured surface with a grid pattern, likely used for navigation or information reading.](41245ac07db266bea228735b9e8c8b73_img.jpg)
+
+A close-up of a tactile map device. It features a rectangular, raised surface with a grid-like pattern of small, distinct textures. The device is mounted on a dark, possibly wooden, base. The lighting is focused on the tactile surface, highlighting its intricate details.
+
+A close-up of a tactile map device, showing a raised, textured surface with a grid pattern, likely used for navigation or information reading.
+
+**Figure I.3 – Use cases of tactile map**
+
+### **I.4 Use case of consumer electronics**
+
+In the field of consumer electronics, tactile rendering technology significantly enhances online shopping experiences, particularly for purchasing clothing and other products where material feel is important (Figure I.4). Through advanced tactile feedback systems, consumers can virtually feel the textures and materials of clothing items as if they were physically present in a store. This allows shoppers to experience the softness, roughness, or elasticity of fabrics, providing a more informed decision-making process before making a purchase. For instance, when shopping for a sweater, consumers can feel the warmth and texture of the fabric, ensuring it meets their expectations. This tactile feedback reduces the likelihood of returns and dissatisfaction due to unmet material expectations, ultimately improving customer satisfaction and reducing after-sales service. By integrating tactile rendering into online shopping platforms, retailers can offer a more immersive and interactive shopping experience, leading to higher engagement and potentially increased sales.
+
+![A conceptual illustration of a person interacting with a large, glowing digital interface for online shopping. The interface displays a 3D model of a suit, a 'TEXTURE' percentage (32%), and various data visualizations. A hand is shown touching a glowing surface, with a roll of fabric materializing from the interface.](fbfaa723129f8b8e3be651c6fe7cfab7_img.jpg)
+
+A conceptual illustration of a person interacting with a large, glowing digital interface for online shopping. The interface displays a 3D model of a suit, a 'TEXTURE' percentage (32%), and various data visualizations. A hand is shown touching a glowing surface, with a roll of fabric materializing from the interface.
+
+A conceptual illustration of a person interacting with a large, glowing digital interface for online shopping. The interface displays a 3D model of a suit, a 'TEXTURE' percentage (32%), and various data visualizations. A hand is shown touching a glowing surface, with a roll of fabric materializing from the interface.
+
+**Figure I.4 – Use cases of online shopping**
+
+## Bibliography
+
+- [b-[ITU-T F.740.7](#)] Recommendation ITU-T F.740.7 (2023), *Reference architecture and requirements for a mobile terminal computational photography system.*
+- [b-[ITU-T F.748.16](#)] Recommendation ITU-T F.748.16 (2022), *Requirements for applications and services in smart manufacturing based on machine vision.*
+- [b-[ITU-T F.749.13](#)] Recommendation ITU-T F.749.13 (2021), *Framework and requirements for civilian unmanned aerial vehicle flight control using artificial intelligence.*
+- [b-[ITU-T H.430.6](#)] Recommendation ITU-T H.430.6 (2023), *Media transport protocols, signalling information of haptic transmission for immersive live experience (ILE) systems.*
+- [b-[ITU-T P.1320](#)] Recommendation ITU-T P.1320 (2022), *Quality of experience assessment of extended reality meetings.*
+- [b-[ITU-T Y.101](#)] Recommendation ITU-T Y.101 (2000), *Global Information Infrastructure terminology: Terms and definitions.*
+- [b-[ITU-T Y.3172](#)] Recommendation ITU-T Y.3172 (2019), *Architectural framework for machine learning in future networks including IMT-2020.*
+
+
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.748.59-202512-I_PDF-E/raw.md b/marked/F/T-REC-F.748.59-202512-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..408957e006e2d2db6d3e317e1142a463717cc5c4
--- /dev/null
+++ b/marked/F/T-REC-F.748.59-202512-I_PDF-E/raw.md
@@ -0,0 +1,552 @@
+
+
+# Recommendation **ITU-T F.748.59 (12/2025)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+---
+
+## **Framework and requirements for human-machine interaction-based explainable decision support system**
+
+![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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.748.59
+
+# Framework and requirements for human-machine interaction-based explainable decision support system
+
+## Summary
+
+Recommendation ITU-T F.748.59 defines the framework and requirements for an explainable decision support system based on human-machine interaction.
+
+Recently, generative artificial intelligence (AI) technology has attracted significant attention in the field of information and communications technology (ICT). This technology enables users to ask questions in expert domains and receive reasonably satisfying answers in natural language. However, a major limitation is the lack of explainability – users are not provided with any explanation for the answers generated.
+
+To address this issue and improve question-answering systems in expert domains, explainable decision support system has been designed. This system not only delivers answers but also provides natural language explanations through interaction with human users. User feedback is also incorporated into the system to improve the quality of future responses.
+
+## History\*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.748.59 | 2025-12-14 | 21          | 11.1002/1000/16584 |
+
+## Keywords
+
+Explanation in natural language, human-machine interaction, question answering systems.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <https://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                                                 | 1    |
+| 4 Abbreviations and acronyms .....                                                            | 1    |
+| 5 Conventions .....                                                                           | 2    |
+| 6 Background.....                                                                             | 2    |
+| 7 Framework for explainable decision support system .....                                     | 3    |
+| 7.1 Real-time knowledge learning module.....                                                  | 4    |
+| 7.2 Uncertainty detection module.....                                                         | 5    |
+| 7.3 Reasoning and decision prediction module .....                                            | 6    |
+| 7.4 Explanation in natural language module .....                                              | 6    |
+| 7.5 Context understanding module.....                                                         | 7    |
+| 7.6 Situation understanding module .....                                                      | 7    |
+| 7.7 Situation element and relation extraction module .....                                    | 7    |
+| 7.8 Knowledge summarization and reporting module .....                                        | 7    |
+| 8 Functional characteristics of human-machine interaction .....                               | 8    |
+| 9 Requirements for human-machine interaction in the explainable decision support system ..... | 9    |
+| 9.1 Providing summary and report with explanation .....                                       | 9    |
+| 9.2 Processing of user feedback .....                                                         | 9    |
+| 9.3 Continuous learning.....                                                                  | 9    |
+| 9.4 Interaction through multimodal conversation .....                                         | 9    |
+| 9.5 Multimodal input and output processing.....                                               | 9    |
+| Bibliography.....                                                                             | 10   |
+
+
+
+# Recommendation ITU-T F.748.59
+
+## Framework and requirements for human-machine interaction-based explainable decision support system
+
+# 1 Scope
+
+This Recommendation specifies the framework and requirements for explainable decision support system (EDSS) based on human-machine interaction. The scope of this Recommendation includes:
+
+- Framework for explainable decision support system based on human-machine interaction.
+- Requirements for explainable decision support system based on human-machine interaction.
+
+# 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.3\]](#) Recommendation ITU-T F.746.3 (2015), *Intelligent question answering service framework*.
+
+[\[ITU-T F.746.7\]](#) Recommendation ITU-T F.746.7 (2018), *Metadata for an intelligent question answering service*.
+
+[\[ITU-T F.746.11\]](#) Recommendation ITU-T F.746.11 (2020), *Interfaces for intelligent question answering system*.
+
+# 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+None.
+
+### 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 decision support system (DSS):** An information system that supports decision-making by the user.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|         |                                                         |
+|---------|---------------------------------------------------------|
+| AI      | Artificial Intelligence                                 |
+| BERT    | Bidirectional Encoder Representations from Transformers |
+| ColBERT | Contextualized late interaction over BERT               |
+| DCSR    | Dense Core Sentence Representation                      |
+| DPR     | Dense Passage Representation                            |
+
+|            |                                                      |
+|------------|------------------------------------------------------|
+| DSS        | Decision Support System                              |
+| EDSS       | Explainable Decision Support System                  |
+| ICT        | Information and Communications Technology            |
+| LLM        | Large Language Model                                 |
+| MV-ColBERT | Multi-View Contextualized Late Interaction over BERT |
+| RPA        | Robotic Process Automation                           |
+| SLM        | Small Language Model                                 |
+
+## 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.
+
+In this Recommendation:
+
+- 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'.](07b17a620c75522d53916a11e12d1bff_img.jpg)
+
+A rounded rectangular box containing the word '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)'.](731f533b0599c8e42a063f06e4332045_img.jpg)
+
+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 Background
+
+The intelligent question answering (QA) system is an advanced function to generate answers to a user's question in a natural language [ITU-T F.746.3]. Recently, generative AI technology has been receiving significant attention in the general information and communications technology (ICT) field as well as QA-equipped applications. This technology enables users to ask questions in expert domains and receive reasonably satisfactory answers in natural language [ITU-T F.746.3], [ITU-T F.746.7] and [ITU-T F.746.11] However, a key limitation is that users are not provided with explanations for the answers. Even when the system provides an incorrect answer, users often have no choice but to assume it is correct. Furthermore, there is no way for users to teach the system the correct answer, even when they are confident in their knowledge.
+
+To address these issues and improve question-answering systems, an explainable decision support system has been designed. A decision support system (DSS) is an information system that supports decision-making activities by the user. DSS includes question-answering functions to ask questions
+
+to find the correct answers when making decisions. In addition to only providing answers, the explainable decision support system offers natural language explanations through interactive conversation with human users. User feedbacks are incorporated into the system to enhance the quality of future responses.
+
+The explainable decision support system provides natural language explanations based on expert knowledge supporting decision-making in various specialized fields such as law, finance, counselling and medicine.
+
+- (Counselling field) Used as a counselling artificial intelligence (AI) that can provide explanations in connection with external expertise. A decision support system that explores and infers external expertise such as regulations and product descriptions in real time is applied to the contact centre and utilized as a counselling AI technology.
+- (Financial field) Used as an explainable expert decision-making support technology based on company-specific financial expertise, such as financial regulations and terms and conditions, product descriptions, etc.
+- (Legal field) Used as decision-making support technology required for legal advice and contract review.
+- (Medical field) Used as a report generation technology based on the latest medical knowledge (papers, reports).
+- (Administrative field) Used as an explainable artificial intelligence technology for robotic process automation (RPA).
+
+## 7 Framework for explainable decision support system
+
+Figure 1 illustrates the explainable decision support system with a user interface that supports multimodal input and feedback through a conversation function. Multimodal feedback from the user is incorporated into the decision support system and enabling it to generate more accurate results in response to future inquiries.
+
+The framework is composed of the following core components: decision support system, answers with natural language explanation, expert knowledge, multi-modal conversation-based user feedback and multimodal user input.
+
+The decision support system incorporates several functional modules including real-time knowledge learning, uncertainty detection, reasoning and decision prediction, explanation in natural language, context understanding situation understanding, situation element and relation extraction and finally, knowledge summarization and reporting.
+
+![Framework for explainable decision support system diagram showing layers of functions and their interactions.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg)
+
+The diagram illustrates the framework for an explainable decision support system, organized into four horizontal layers of functions, with external inputs and outputs at the bottom.
+
+- Top Layer: Knowledge summarization and reporting functions (Green box)**
+  - Knowledge summarization function
+  - Reporting function
+- Second Layer from top: Context/Situation understanding functions (Green box) and Reasoning/Prediction/Explanation functions (Green box)**
+  - Context/Situation understanding functions:** Context understanding function, Situation understanding function, Situation element and relation extraction function.
+  - Reasoning/Prediction/Explanation functions:** Reasoning and decision prediction function, Explanation in natural language.
+- Third Layer from top: Uncertainty detection and knowledge learning functions (Green box)**
+  - Realtime knowledge learning function
+  - Uncertainty detection function
+- Bottom Layer: Human input and output processing functions (Blue box)**
+  - Input fusion processing function
+  - Text input processing function
+  - Image input processing function
+  - Gesture input processing function
+  - Table input processing function
+  - Text output functions
+
+**External Inputs and Outputs:**
+
+- Inputs:** Text, Voice, Gesture, Table, and Text (from User question and user feedback/Expert knowledge).
+- Output:** Answer with natural language explanation.
+
+**Legend:**
+
+- Green box: Functions in the scope of this Recommendation
+- Blue box: Functions out of scope of this Recommendation
+- Dashed pink box: Contents of input and output
+- Solid blue arrow: Data flow in the system
+- Dashed blue arrow: Input and output of the system
+
+F.748.59(25)
+
+Framework for explainable decision support system diagram showing layers of functions and their interactions.
+
+**Figure 1 – Framework for explainable decision support system**
+
+### 7.1 Real-time knowledge learning module
+
+In the real-time knowledge learning module, real-world expert knowledge – often dynamic and inherently uncertain – is learned continuously. This knowledge is captured through multimodal user input submitted in the context of problem-solving as illustrated in Figure 2.
+
+In the figure, <person, ride, horse> and <person, pull, cart> have images, where the triplets themselves are represented by images, providing visual knowledge. The first triplet, <person, ride, horse> is represented by green oval rectangle and the second triplet, <person, pull, cart> is represented by an orange oval rectangle. The words on the arrows represent the relation between two elements in the triplet. This module extracts information from input images and utilizes those images to represent visual common-sense knowledge.
+
+![Figure 2: Knowledge from multimodal user input. A diagram showing relationships between 'Person', 'Cart', 'Horse', and 'Thing'. 'Person' (a human being) can 'Pull' a 'Cart' (a heavy open wagon) or 'Ride' a 'Horse' (solid-hoofed herbivorous quadruped). 'Cart' can be 'Pull'ed or used for 'Transport'. 'Horse' can be 'Ride'd or 'Pull'ed. 'Cart' is a 'Thing' (an artifact).](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+**Person**  
+a human being
+
+**Cart**  
+a heavy open wagon usually having two wheels and drawn by an animal
+
+**Horse**  
+solid-hoofed herbivorous quadruped domesticated since prehistoric times
+
+**Thing**  
+an artifact
+
+**Pull**  
+cause to move by pulling
+
+**Ride**  
+sit and travel on the back of animal, usually while controlling its motions
+
+**Transport**  
+move something or somebody around; usually over long distances
+
+F.748.59(25)
+
+Figure 2: Knowledge from multimodal user input. A diagram showing relationships between 'Person', 'Cart', 'Horse', and 'Thing'. 'Person' (a human being) can 'Pull' a 'Cart' (a heavy open wagon) or 'Ride' a 'Horse' (solid-hoofed herbivorous quadruped). 'Cart' can be 'Pull'ed or used for 'Transport'. 'Horse' can be 'Ride'd or 'Pull'ed. 'Cart' is a 'Thing' (an artifact).
+
+**Figure 2 – Knowledge from multimodal user input [b-Lee]**
+
+### 7.2 Uncertainty detection module
+
+The uncertainty detection module illustrated in Figure 3 identifies knowledge which has not been learned and is therefore considered uncertain. By detecting these gaps, the module supports the real-time knowledge learning module dynamically acquiring the missing or evolving information. It is also capable of informing the user when knowledge is uncertain, providing appropriate explanations through natural language.
+
+In this module, questions and documents/answers are tokenized using bidirectional encoder representations from transformers (BERT), and the resulting tokens are input into a cross-attention neural network via a BERT embedding layer, as shown in Figure 3. Subsequently, evidential uncertainty and classification of relatedness among documents are computed, and the output and uncertainty results are generated as shown in the table. Finally, the question-answer rankings are determined using an evidence-based neural network model to support the explanation.
+
+![Figure 3: Uncertainty detection module. A diagram showing the flow from 'Bert tokenized question' and 'Bert tokenized document or answer' through 'BERT embedding' and 'Cross-attention' to an 'Evidence-based neural network model'. The model consists of 'Classification' and 'Evidential uncertainty' functions. The 'Evidential uncertainty' function uses the formula E_y(y) = a_y(y) / sum(a_i(y_i)) and Vac(h o g(x|Theta)). The output is a 'Q-A rank' and a table of 'Input', 'Output', 'Uncertainty', and 'Use'.](7e670a2b556b53ea9002dfff3a420e08_img.jpg)
+
+Evidence-based neural network model  $h \circ g(\mathbf{x}|\Theta)$
+
+**$h(\cdot)$**  Classification
+
+**$g(\cdot)$**  Cross-attention
+
+**BERT embedding**
+
+Bert tokenized question
+
+Bert tokenized document or answer
+
+**Classification**  
+ $\mathcal{L}(h \circ g(\mathbf{x}|\Theta), y)$
+
+**Evidential uncertainty**  
+
+$$E_y(y) = \frac{\alpha_y(y)}{\sum \alpha_i(y_i)}$$
+
+$$Vac(h \circ g(\mathbf{x}|\Theta))$$
+
+**Q-A rank**
+
+| Input             | Output          | Uncertainty | Use      |
+|-------------------|-----------------|-------------|----------|
+| <b>Document 1</b> | <b>Good (0)</b> | <b>0.1</b>  | <b>Y</b> |
+| <b>Document 2</b> | <b>Good (0)</b> | <b>0.7</b>  | <b>N</b> |
+| <b>Document 3</b> | <b>Bad (1)</b>  | <b>0.2</b>  | <b>N</b> |
+| <b>Document 4</b> | <b>Bad (1)</b>  | <b>0.9</b>  | <b>Y</b> |
+
+--- Classification function --- Uncertainty function
+
+F.748.59(25)
+
+Figure 3: Uncertainty detection module. A diagram showing the flow from 'Bert tokenized question' and 'Bert tokenized document or answer' through 'BERT embedding' and 'Cross-attention' to an 'Evidence-based neural network model'. The model consists of 'Classification' and 'Evidential uncertainty' functions. The 'Evidential uncertainty' function uses the formula E\_y(y) = a\_y(y) / sum(a\_i(y\_i)) and Vac(h o g(x|Theta)). The output is a 'Q-A rank' and a table of 'Input', 'Output', 'Uncertainty', and 'Use'.
+
+**Figure 3 – Uncertainty detection module**
+
+### 7.3 Reasoning and decision prediction module
+
+The reasoning and decision prediction module presented in Figure 4 functions as the core engine of the decision support system. It conducts primary reasoning processes for problem-solving and produces decision predictions by integrating expert knowledge, situational knowledge and contextual information. In the reasoning function, answers for a problem which is a query or a question, are provided based on different evidence. Next, in the evidence selector function, the evidence are ranked with predefined reliability scores and the most reliable evidence is selected based on the different knowledge sources. Lastly, in the prediction function, the final decision predictions are produced according to the selected evidence in the previous step.
+
+![Figure 4: Reasoning and decision prediction module diagram](042733dc5e8e7f5f30b60adba3266cde_img.jpg)
+
+A diagram showing the 'Reasoning and decision prediction function' as a container for three sub-functions: 'Reasoning function', 'Evidence selector', and 'Prediction function'. Below the diagram is the code F.748.59(25).
+
+Figure 4: Reasoning and decision prediction module diagram
+
+Figure 4 – Reasoning and decision prediction module
+
+### 7.4 Explanation in natural language module
+
+Explanations are provided in natural language as the basis for reasoning and decision prediction. These explanations are collected and integrated with the contextual and situational knowledge within the summary and reporting module, which serves as the output of the decision support system. Through human-machine interaction and conversation, users receive these natural language explanations and can provide multimodal feedback to the expert system in the same interactive manner.
+
+Figure 5 illustrates the processing of multimodal user input and corresponding output feedback. Text, images and tables provided by the user are processed together as multimodal input through a large language model (LLM), which generates explanatory output text. Additionally, documents may serve as targets for separate text processing, which is also routed through the LLM to provide a basis for explanations or user feedback.
+
+![Figure 5: Multimodal user input and output feedback processing diagram](853f59c89931a666c07903b31d098277_img.jpg)
+
+A flow diagram showing multimodal input processing. On the left, a 'Document' is processed through 'Scan and analyse (Text extraction)' to produce 'Prompt: Text' and 'Source: Plain text'. Below it, 'Text + table + image' (represented by a CANFIR template) and an 'Image' (represented by two flowers) are processed through an 'Image' extraction step to produce 'Prompt: Text' and 'Source: Image'. These prompts are fed into an 'LLM' (Large Language Model) circle, which outputs 'Text'. A legend on the right indicates: blue arrows for 'Text data flow', green arrows for 'Multimodal data flow', and white arrows for 'Output data flow'. Below the diagram is the code F.748.59(25).
+
+Figure 5: Multimodal user input and output feedback processing diagram
+
+Figure 5 – Multimodal user input and output feedback processing
+
+### 7.5 Context understanding module
+
+The context understanding module analyses the context of the problem that the experts are trying to solve, providing essential evidence and a foundation for further processing. The results of this analysis are used to support reasoning and decision prediction, as well as to form the basis for natural language explanation and knowledge summarization and reporting.
+
+In Figure 6, a query undergoes a three-tiered process of representation generation to retrieve core information from the knowledge base that is relevant to the query. These tiers include passage-level ((dense passage representation (DPR)), sentence-level (dense core sentence representation (DCSR)) and phrase-level (DensePhrases). The resulting context representations are then used by a seq2seq generation model to produce answers, based on the relationship between the query and the context.
+
+![Diagram of the Context analysis module with three tiers (Figure 6).](ff0952ef692c9d960ce5f6708bcc9711_img.jpg)
+
+The diagram illustrates the context analysis module's three-tiered process. A grey box labeled 'Query' is on the left. An orange box labeled 'Knowledge base' is above it, with an orange arrow pointing from it to the 'Query' line. The 'Query' line branches into three parallel processing paths. The top path goes through an orange box labeled 'DPR' to a white box labeled 'Passage-level' containing a paragraph about Steven Paul Jobs. The middle path goes through a green box labeled 'DCSR' to a white box labeled 'Sentence-level' containing a sentence about his roles at Apple. The bottom path goes through a blue box labeled 'DensePhrases' to a white box labeled 'Phrase-level' containing the phrase 'Co-founder, chairman, and CEO'. All three white boxes point to a large yellow box on the right labeled 'seq2seq Generation model'. A legend at the bottom identifies the box colors: white for 'Data processing module', orange for 'Knowledge base', yellow for 'Neural network model', and grey for 'Query of the user'. Arrows indicate data flow: black for 'Data flow in the system' and orange for 'Data flow from KB'.
+
+Diagram of the Context analysis module with three tiers (Figure 6).
+
+F.748.59(25)
+
+Figure 6 – Context analysis module with three tiers
+
+### 7.6 Situation understanding module
+
+In the situation understanding module, the situation analysis is performed on the specific situations in which users and their problems are situated. The results of this analysis are transferred to the context understanding module, where they are used to support reasoning and decision prediction processes.
+
+### 7.7 Situation element and relation extraction module
+
+In this module, the situation elements and their relationships are extracted to provide a foundation for the situation understanding module. The situation elements and their interrelations are analysed based on the formal definitions and classifications.
+
+### 7.8 Knowledge summarization and reporting module
+
+In the knowledge summarization and reporting module, knowledge is summarized and presented in natural language as in Figure 7. The purpose of this summary and report is to provide users with clear explanations that support informed decision-making.
+
+Figure 7 illustrates the knowledge summarization and reporting process in the legal domain. First, the query is embedded into a multi-view neural network (multi-view contextualized late interaction over BERT (MV-ColBERT)). Then, law-related documents, including judicial precedents and statutes, are retrieved and processed by a small LLM (SLM), which generates an analysis report and summary, along with explanations based on the query results. In this figure, the user query is analysed by the understanding neural network model, and the retrieved results from the text of law documents such
+
+as statutes and judicial precedents are augmented. The augmented text is then processed through the SLM, which is the general knowledge language model to produce the output which is the analysis report.
+
+![Figure 7 – Knowledge summarization and reporting. A flow diagram showing the process from a user query (Q) through an MV-ColBERT model to retrieve judicial precedents and statutes, which are then processed by an SLM to generate an analysis report. The report includes sections for situation analysis, judicial precedent analysis, law analysis, similarity/differences analysis, and conclusion.](b9ecbc3baefab13719e000faa6e0c7eb_img.jpg)
+
+The diagram illustrates the knowledge summarization and reporting process. A user query (Q) is input into an MV-ColBERT model. This model retrieves judicial precedents (1~N) and statutes (1~N). These retrieved items are then processed by an SLM (Small Language Model). The SLM generates an analysis report based on a prompt that provides context and the question. The report is structured into five sections: 1. Situation analysis, 2. Analysis of judicial precedent, 3. Law analysis, 4. Similarity/Differences analysis, and 5. Conclusion. The situation analysis includes user situation, facts, and recommended actions. The law analysis includes a list of recommended actions (A, B, C and D).
+
+**Prompt:** Related judicial precedents and statutes are provided for the following questions.  
+ {{context}}  
+ {question}  
+ Answer::
+
+**Analysis report structure:**
+
+- 1. Situation analysis  
+User situation:  
+Facts
+- 2. Analysis of judicial precedent  
+...
+- 3. Law analysis  
+...
+- 4. Similarity/Differences analysis  
+...
+- 5. Conclusion:  
+Recommended actions:  
+Users are recommended to the following actions A, B, C and D.
+
+**Legend:**
+
+- Neural network model (pink box)
+- Q Query of the user (green box)
+- Text input and output (orange box)
+- Data flow in the system (blue arrow)
+- Output flow of the system (orange arrow)
+
+F.748.59(25)
+
+Figure 7 – Knowledge summarization and reporting. A flow diagram showing the process from a user query (Q) through an MV-ColBERT model to retrieve judicial precedents and statutes, which are then processed by an SLM to generate an analysis report. The report includes sections for situation analysis, judicial precedent analysis, law analysis, similarity/differences analysis, and conclusion.
+
+**Figure 7 – Knowledge summarization and reporting**
+
+## 8 Functional characteristics of human-machine interaction
+
+The functional characteristics of human-machine interaction in the explainable decision support system (EDSS) are analysed to define the initial functional requirements for the system. These functions are outlined as follows:
+
+- Decision support function: Generates reports based on multimodal, conversation-driven user feedback.
+- Learning function: Integrates continuously evolving real-world knowledge.
+- Knowledge tracking: Provides source-based explainability and justifications for uncertainty.
+- Uncertainty quantification: Identifies and presents unlearned or uncertain knowledge based on the current environment.
+- Answer recognition and explanation: Identifies and explains correct answers to user questions involving multiple conditions, such as issues, claims, and evidence.
+- Context-aware sentence classification: Classifies sentences based on multiple pieces of evidence related to the user's question across various contexts (e.g., issues, claims, evidence).
+- Inference explainability: Explains inference results derived from natural language texts through a natural language interface.
+- User intent and context understanding: Recognizes complex user intentions and situational contexts.
+- Expert knowledge summarization: Generates summary reports combining query-based expert knowledge and inference outcomes relevant to decision-making scenarios.
+
+## **9 Requirements for human-machine interaction in the explainable decision support system**
+
+### **9.1 Providing summary and report with explanation**
+
+[SR-01] The decision support system is required to provide explanation for the resulting answers to the user's question.
+
+[SR-02] The decision support system is recommended to explain inference results from natural language text through a natural language interface.
+
+[SR-03] The decision support system is recommended to provide summary results of query-based expert knowledge and inference results about decision-making situations.
+
+[SR-04] The decision support system is recommended to provide a report based on expert knowledge in the real world.
+
+### **9.2 Processing of user feedback**
+
+[UF-01] The decision support system is recommended to understand user feedback with multimodal conversation basis.
+
+[UF-02] The decision support system is recommended to reflect user feedback in the knowledge base to apply for the next problem-solving situation.
+
+[UF-03] The decision support system is recommended to understand user intention by providing recognition functions of complex context/situation.
+
+### **9.3 Continuous learning**
+
+[CL-01] The decision support system is recommended to provide a learning function to integrate continuously changing knowledge.
+
+[CL-02] The decision support system is recommended to track knowledge to provide source-based explainability and reasons for uncertainty.
+
+[CL-03] The decision support system is recommended to quantify and present unlearned and uncertain knowledge.
+
+### **9.4 Interaction through multimodal conversation**
+
+[MC-01] The decision support system is recommended to provide an interaction function between the user and the system based on multimodal conversation.
+
+[MC-02] The decision support system is recommended to recognize and explain the correct answer to the user's multi-condition questions, such as issues, claims and evidence.
+
+[MC-03] The decision support system is recommended to classify sentences based on multiple evidence for the subject of the user question in different situations.
+
+### **9.5 Multimodal input and output processing**
+
+[IO-01] The decision support system is recommended to provide the multimodal input processing function for the user input such as text, image, gestures, speech and video.
+
+[IO-02] The decision support system is recommended to provide the multimodal output producing function for the system output such as text, image, gestures, speech and video.
+
+[IO-03] The decision support system is recommended to provide explanation in multimodal output form such as text, image, gestures, speech and video.
+
+## Bibliography
+
+[b-Lee]
+
+Lee, J., Chung, C., Lee, H., Jo, S., Whang, J.J. (2023), *VISTA: Visual-Textual Knowledge Graph Representation Learning*, EMNLP Findings 2023.
+
+<<https://aclanthology.org/2023.findings-emnlp.488/>>
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.748.6-202503-I_PDF-E/raw.md b/marked/F/T-REC-F.748.6-202503-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a33532e99db5f19e203e9c1ec2e4bbf7dc3f3853
--- /dev/null
+++ b/marked/F/T-REC-F.748.6-202503-I_PDF-E/raw.md
@@ -0,0 +1,935 @@
+
+
+# Recommendation **ITU-T F.748.6 (03/2025)**
+
+SERIES F: Non-telephone telecommunication services  
+Multimedia services
+
+---
+
+## **Requirements and framework for interactive multimedia communication system of Internet of things (IoT) devices**
+
+![ITU logo](390120de4fe440c42fea8154fcaad334_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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.748.6
+
+# Requirements and framework for interactive multimedia communication system of Internet of things (IoT) devices
+
+## Summary
+
+Recommendation ITU-T F.748.6 specifies requirements and framework for interactive multimedia communication system of Internet of thing (IoT) devices.
+
+## History\*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.748.6  | 2025-03-16 | 21          | 11.1002/1000/16230 |
+
+## Keywords
+
+Interactive multimedia communication, IoT device, multimedia communication.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <https://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                      | 3    |
+| 5 Conventions .....                                                                     | 4    |
+| 6 Framework of interactive multimedia communication system for IoT device (IMCSI) ..... | 4    |
+| 6.1 Framework and network entities .....                                                | 4    |
+| 6.2 Entities functions .....                                                            | 5    |
+| 6.3 Reference points .....                                                              | 5    |
+| 7 IMCSI platform requirements.....                                                      | 5    |
+| 7.1 Communication requirement .....                                                     | 6    |
+| 7.2 Application requirement.....                                                        | 6    |
+| 7.3 Signalling requirement .....                                                        | 6    |
+| 7.4 Security requirement .....                                                          | 6    |
+| 8 IMCSI device requirements.....                                                        | 6    |
+| 8.1 Hardware requirement .....                                                          | 6    |
+| 8.2 Software requirement .....                                                          | 6    |
+| 8.3 Interaction requirements.....                                                       | 7    |
+| 9 IMCSI interaction procedure .....                                                     | 7    |
+| 9.1 Bootstrap data channel setup signalling procedure .....                             | 7    |
+| 9.2 Application data channel setup signalling procedure.....                            | 11   |
+| 9.3 Application interaction procedure .....                                             | 14   |
+| Appendix I – Typical use cases and scenarios .....                                      | 20   |
+| Bibliography.....                                                                       | 21   |
+
+
+
+# Recommendation ITU-T F.748.6
+
+## Requirements and framework for interactive multimedia communication system of Internet of things (IoT) devices
+
+# 1 Scope
+
+This Recommendation specifies requirements and framework for interactive multimedia communication system of Internet of things (IoT) devices, including the framework of interactive IoT multimedia communication system, the function requirements of platform, device and the procedure of signalling and interaction.
+
+The scope of this Recommendation includes:
+
+- Framework of interactive multimedia communication system for Internet of things (IoT) devices (IMCSI)
+- IMCSI platform requirements
+- IMCSI device requirements
+- IMCSI interaction procedure.
+
+# 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.13] Recommendation ITU-T F.746.13 (2022), *Requirements for smart speaker-based intelligent multimedia communication systems*.
+- [ETSI TS 123 228] ETSI TS 123 228 V18.6.0 (2024), *Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228 version 18.6.0 Release 18)*.
+- [IEEE 802.11] IEEE 802.11 (2024), *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*.
+- [IETF RFC 8864] IETF RFC 8864 (2021), *Negotiation Data Channels Using the Session Description Protocol (SDP)*.
+
+# 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 application data channel (ADC)** [ETSI TS 123 228]: A data channel within an IP multimedia subsystem (IMS) session used to transfer data of data channel applications between user equipment (UEs) or between the UE and the network.
+
+**3.1.2 bootstrap data channel** [ETSI TS 123 228]: A data channel established within an IMS session between the UE and the network, to transfer a graphical user interface that can include a list of data channel applications.
+
+**3.1.3 business support system** [b-GSMA NG.129]: A system used by an operator to define the provisioning of IMS data channel services.
+
+**3.1.4 data channel application repository (DCAR)** [b-GSMA NG.129]: Backend network functionality providing only the storage for the IMS data channel applications.
+
+NOTE – The network functionality of the data channel application repository complies with the specification given in section 6.2.10 of [b-ETSI TS 126 114].
+
+**3.1.5 data channel application server (DCAS)** [ETSI TS 123 228]: An application server (AS) that interacts with the data channel signalling function (DCSF) and the data channel (DC) media function for data channel traffic handling.
+
+**3.1.6 data channel server (DCS)** [b-GSMA NG.129]: A new IMS logical entity providing the data channel functions in 5G.
+
+NOTE – The network functionality of the data channel server complies with the specification given in section 6.2.10 of [b-ETSI TS 126 114].
+
+**3.1.7 device** [b-ITU-T Y.4000]: In the Internet of things, a piece of equipment with the mandatory capabilities of communication and the optional capabilities of sensing, actuation, data capture, data storage and data processing.
+
+**3.1.8 Internet of things** [b-ITU-T Y.4000]: A global infrastructure for the information society, enabling advanced services by interconnecting (physical and virtual) things based on, existing and evolving, interoperable information and communication technologies.
+
+NOTE 1 – Through the exploitation of identification, data capture, processing and communication capabilities, the IoT makes full use of (physical and virtual) things to offer services to all kinds of applications, whilst ensuring that security and privacy requirements are fulfilled.
+
+NOTE 2 – From a broader perspective, the IoT can be perceived as a vision with technological and societal implications.
+
+**3.1.9 multimedia resource function (MRF)** [ETSI TS 123 228]: The MRF is split into multimedia resource function controller (MRFC) and multimedia resource function processor (MRFP).
+
+NOTE – The tasks of MRFC and MRFP comply with the specification given in section 4.7 of [ETSI TS 123 228].
+
+**3.1.10 operation support systems** [b-GSMA NG.129]: A system used by the operator to define IMS data channel fault, configuration, accounting, performance, and security.
+
+### **3.2 Terms defined in this Recommendation**
+
+This Recommendation defines the following terms:
+
+**3.2.1 IMCSI data channel:** A data channel within an IP multimedia subsystem (IMS) session used to transfer data of interactive multimedia communication system for Internet of things devices (IMCSI) application among the IMCSI device, IMCSI platform and data channel media function (DCMF)/MRF.
+
+**3.2.2 IMCSI platform:** A series of functional units and subsystems deployed by an operator in the IP multimedia subsystem (IMS) network. It is used to implement audio or video calls to support interactive multimedia services between user equipment (UE) and IMCSI-enabled devices, which would support data channel services.
+
+**3.2.3 IMCSI device:** It refers to a kind of device that can be remotely controlled by UE or receive and display the multimedia stream processed by AI and other multimedia algorithms during a voice or video call session.
+
+**3.2.4 media capacity platform:** A system using different kinds of artificial intelligence (AI) algorithms and multimedia functions to process audio and video data, for instance voice recognition, voice-to-text/text-to-speech conversion, gesture recognition, etc.
+
+**3.2.5 master application data channel:** In the IMCSI, a kind of application data channel which is used to transmit management requests and manage work application data channels ADCs between user equipment (UE) and data channel media function (DCMF)/multimedia resource function (MRF).
+
+**3.2.6 work ADC:** In the interactive multimedia communication system for Internet of things devices (IMCSI), a kind of application data channel which is used to transmit application data between user equipment (UE) and data channel media function (DCMF)/multimedia resource function (MRF).
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|       |                                                                            |
+|-------|----------------------------------------------------------------------------|
+| ADC   | Application Data Channel                                                   |
+| AI    | Artificial Intelligence                                                    |
+| AR    | Augmented Reality                                                          |
+| AS    | Application Server                                                         |
+| BDC   | Bootstrap Data Channel                                                     |
+| D2U   | Device to UE                                                               |
+| DC    | Data Channel                                                               |
+| DCAR  | Data Channel Application Repository                                        |
+| DCAS  | Data Channel Application Server                                            |
+| DCMF  | Data Channel Media Function                                                |
+| DCS   | Data Channel Server                                                        |
+| DCSF  | Data Channel Signalling Function                                           |
+| DTMF  | Dual Tone Multi Frequency                                                  |
+| IMCSI | Interactive Multimedia Communication System for Internet of things devices |
+| IMS   | IP Multimedia Subsystem                                                    |
+| IoT   | Internet of Things                                                         |
+| MCP   | Multimedia Capacity Platform                                               |
+| MRF   | Multimedia Resource Function                                               |
+| NLP   | Natural Language Processing                                                |
+| NPU   | Neural Processing Unit                                                     |
+| PTZ   | Pan/Tilt/Zoom                                                              |
+| RAN   | Radio Access Network                                                       |
+| SDK   | Software Development Kit                                                   |
+| SDP   | Session Description Protocol                                               |
+
+|       |                                |
+|-------|--------------------------------|
+| SIP   | Session Initiation Protocol    |
+| TPU   | Tensor Processing Unit         |
+| U2D   | UE to Device                   |
+| UE    | User Equipment                 |
+| URL   | Uniform Resource Locator       |
+| VoLTE | Voice over Long-Term Evolution |
+| VoNR  | Voice over New Radio           |
+
+## 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.
+- IMCSI devices refers to IoT devices which can support interactive multimedia communication services in IMCSI system.
+
+## 6 Framework of interactive multimedia communication system for IoT device (IMCSI)
+
+### 6.1 Framework and network entities
+
+Figure 6-1 depicts the framework of IMCSI as well as the main entities used to implement interactive multimedia communication between user equipment (UEs) and IMCSI devices.
+
+The network environment of IMCSI is included in the IP multimedia subsystem (IMS) network. UEs are usually connected via radio access network (RAN) (e.g., IMT-2000, IMT-Advanced, IMT-2020) into the voice over new radio (VoNR) / voice over long-term evolution (VoLTE) network. IMCSI devices are connected via WLAN [IEEE 802.11] into the IMS network.
+
+The VoNR/VoLTE network consists of the following network entities:
+
+- IMS application server (IMS AS)
+- Data channel server (DCS)
+- Data channel signalling function (DCSF)
+- Multimedia resource function (MRF)
+- Data channel application repository (DCAR)
+- Multimedia capacity platform (MCP).
+
+The IMS network consists of the IMCSI platform.
+
+![Figure 6-1: Framework of interactive multimedia communication system for IoT device. The diagram shows an IMS network containing a VoNR/VoLTE network (with DCAR, MCP, DCS, DCSF, DCMF/MRF, IMS AS) and an IMCSI platform. The VoNR/VoLTE network is connected to a UE. The IMCSI platform is connected to an IMCSI device and an IMCSI database. Reference points are labeled: DC5, DC1, DC2/Mr'/Cr, Mc, Mt, Id, Mi, Rd.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+The diagram illustrates the framework of an interactive multimedia communication system for IoT devices. It is organized into three main layers:
+
+- UE (User Equipment):** Located at the bottom left, connected to the IMS AS.
+- IMS network:** A large box containing two sub-networks:
+  - VoNR/VoLTE network:** Enclosed in a dashed box, it contains the following components:
+    - DCAR** and **MCP** at the top.
+    - DCS** below them, containing **DCSF** and **DCMF/MRF**.
+    - IMS AS** at the bottom, connected to the UE.
+  - IMCSI platform:** Located to the right of the VoNR/VoLTE network, it connects to the **IMCSI device** (bottom right) and the **IMCSI database** (top right).
+
+Reference points are indicated by lines with labels:
+
+- DC5:** Between DCAR and DCS.
+- DC1:** Between DCSF and IMS AS.
+- DC2/Mr'/Cr:** Between DCMF/MRF and IMS AS.
+- Mc:** Between DCMF/MRF and MCP.
+- Mt:** Between MCP and the IMCSI platform.
+- Id:** Between DCMF/MRF and the IMCSI platform.
+- Mi:** Between the IMCSI platform and the IMCSI device.
+- Rd:** Between the IMCSI platform and the IMCSI database.
+
+A small label **F.748.6(25)** is in the bottom right corner of the diagram area.
+
+Figure 6-1: Framework of interactive multimedia communication system for IoT device. The diagram shows an IMS network containing a VoNR/VoLTE network (with DCAR, MCP, DCS, DCSF, DCMF/MRF, IMS AS) and an IMCSI platform. The VoNR/VoLTE network is connected to a UE. The IMCSI platform is connected to an IMCSI device and an IMCSI database. Reference points are labeled: DC5, DC1, DC2/Mr'/Cr, Mc, Mt, Id, Mi, Rd.
+
+**Figure 6-1 – Framework of interactive multimedia communication system for IoT device**
+
+### 6.2 Entities functions
+
+The functionalities of DCSF comply with AC.2.2.1 specified in [ETSI TS 123 228].
+
+The functionalities of DCAR comply with AC.2.2.2 specified in [ETSI TS 123 228].
+
+The functionalities of DCMF/MRF comply with AC.2.2.3 specified in [ETSI TS 123 228].
+
+The functionalities of IMS AS comply with AC.2.2.4 specified in [ETSI TS 123 228].
+
+The MCP provides artificial intelligence (AI) and multimedia algorithms to process multimedia data. The MCP provides the following functionalities.
+
+- The MCP receives the multimedia data sent by DCMF/MRF;
+- The MCP uses natural language processing (NLP) algorithms to execute audio process tasks, for instance, voice-to-text/text-to-speech conversion;
+- The MCP uses AI algorithms to execute audio process tasks, for instance, voice recognition, simultaneous translation;
+- The MCP uses AI algorithms to execute image process tasks, for instance, virtual portrait, gesture recognition, object detection, scene semantic segmentation;
+- The MCP uses multimedia functions to execute media process tasks, for instance, video transcoding, stream extraction, and media forwarding.
+
+### 6.3 Reference points
+
+The following reference points are defined to support IMCSI service:
+
+- DC1, DC2, Mr'/Cr, DC5 are defined in AC.2.3 of [ETSI TS 123 228];
+- Mc: Reference point between the DCMF and the MCP;
+- Mt: Reference point between the MCP and the IMCSI platform;
+- Id: Reference point between the DCMF/MRF and the IMCSI platform;
+- Mi: Reference point between the IMCSI platform and IMCSI device;
+- Rd: Reference point between the IMCSI platform and IMCSI database.
+
+## 7 IMCSI platform requirements
+
+This clause clarifies the requirements of the IMCSI platform.
+
+### **7.1 Communication requirement**
+
+IPCR-001: The IMCSI platform is required to support the communication requirements specified in clause 9.1 of [ITU-T F.746.13].
+
+NOTE – The smart speaker becomes an IMCSI device when it is upgraded to provide the IMCSI service.
+
+### **7.2 Application requirement**
+
+IPAR-001: The IMCSI platform is required to support the application requirements specified in clause 9.2 of [ITU-T F.746.13].
+
+IPAR-002: The IMCSI platform is required to query the IMCSI database whether a calling/called IMCSI device supports IMCSI service.
+
+IPAR-003: The IMCSI platform is required to negotiate the transmission protocol with DCSF.
+
+IPAR-004: The IMCSI platform is required to setup an IMCSI data channel to carry application data.
+
+### **7.3 Signalling requirement**
+
+IPSR-001: The IMCSI platform is required to transmit and receive the signalling with network entities, such as IMS AS, DCSF and data channel media function (DCMF)/MRF.
+
+IPSR-002: The IMCSI platform is required to execute a set of signalling to establish an IMCSI data channel that carries the application data interacted with the UE.
+
+### **7.4 Security requirement**
+
+IPSR-001: The IMCSI platform is required to validate whether a UE has the right to send application data to the called IMCSI device.
+
+IPSR-002: The IMCSI platform is required to encrypt data transmitted to the IMCSI device.
+
+## **8 IMCSI device requirements**
+
+This clause describes the requirements of IMCSI device requirements, including hardware and software requirements.
+
+### **8.1 Hardware requirement**
+
+IDHR-001: The IMCSI device is recommended to have some mechanical components to execute actions according to the corresponding instructions.
+
+IDHR-002: The IMCSI device is recommended to have a touch screen to display application data, such as emoji, marks, or texts, and receives touch commands.
+
+IDHR-003: The IMCSI device is recommended to be integrated with one or more cameras to support video related applications, such as video calls, meetings, training, etc.
+
+IDHR-004: The IMCSI device is recommended to be integrated with computing chips, such as neural processing unit (NPU) or tensor processing unit (TPU).
+
+IDHR-005: The IMCSI device is recommended to be integrated with audio/video codec chips to execute local multimedia processing tasks, such as mixing audio/video stream, rendering, etc.
+
+### **8.2 Software requirement**
+
+IDSR-001: The IMCSI device is required to run on the main operation system, such as Linux, Android, etc.
+
+IDSR-002: The IMCSI device is required to be embedded with a software development kit (SDK) which can be defined by operators, to support the management of the device capacity, access control, authentication, identification, etc.
+
+IDSR-003: The IMCSI device is required to report its capability set to the IMCSI platform. The capability set is recommended to include call types, AI functions, etc. Call type may include mainly three types, voice call only, one-way video call, and bi-directional video call. AI functions may support AI functions, such as automatic speech recognition, speech-to-text conversion, and object detection.
+
+IDSR-004: The IMCSI device is recommended to run multiple algorithms simultaneously.
+
+IDSR-005: The IMCSI device is required to support remote upgrade.
+
+IDSR-006: The IMCSI platform is required to transmit and receive the signalling with network entities, such as IMS AS, DCSF, and DCMF/MRF.
+
+IDSR-007: The IMCSI platform is required to execute a set of signalling to establish an IMCSI data channel that carries the application data interacted with the UE.
+
+### **8.3 Interaction requirements**
+
+IDIR-001: The IMCSI device is recommended to support voice interaction, such as voice wake-up, automatic speech recognition, etc.
+
+IDIR-002: The IMCSI device is recommended to support visual interaction, such as gesture recognition, face detection, etc.
+
+## **9 IMCSI interaction procedure**
+
+To support interactive multimedia communication services, a series of interaction procedures are defined in this clause.
+
+### **9.1 Bootstrap data channel setup signalling procedure**
+
+#### **9.1.1 UE to device (U2D) bootstrap data channel setup**
+
+Figure 9-1 depicts a signalling flow diagram for establishing a bootstrap data channel (BDC) in the IMCSI when the UE is the originating side and the IMCSI device is the terminating side, respectively. The DCMF anchors the bootstrap data channel, and the originating network is offering a bootstrap data channel to the UE as well for application download.
+
+In the call flow the UE and the IMCSI device have already established an IMS audio session, and the UE is updating the IMS audio/video session to an IMS data channel session.
+
+NOTE 1 – P/I/S-CSCFs and some irrelevant session initiation protocol (SIP) signalling are not shown in the call flow below.
+
+![Sequence diagram showing the U2D bootstrap data channel set up signalling procedure for IMCSI. Lifelines: UE, IMS AS, DCSF, DCMF/MRF, IMCSI platform, IMCSI device. The process involves INVITE, DC routing decision, Nimsas notifications, DC media information creation, DCMF/MRF discovery, media resource reservation, and final BDC establishment.](4801720824e4b5e2361a5564f91cfb70_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UE
+    participant IMS AS
+    participant DCSF
+    participant DCMF/MRF
+    participant IMCSI platform
+    participant IMCSI device
+
+    UE->>IMS AS: 1. INVITE (Audio/video offer, SDP offer for bootstrap DC)
+    Note right of IMS AS: 2. DC routing decision and DCSF discovery
+    IMS AS->>DCSF: 3. Nimsas_SessionEventControl_Notify
+    Note right of DCSF: 4. DCSF decides whether DC is provided and determines DC control policy
+    Note right of DCSF: 5. DCSF creates DC media information
+    DCSF->>IMS AS: 6. Nimsas_MediaControl_MediaInstruction
+    Note right of IMS AS: 7. DCMF/MRF discovery
+    IMS AS->>DCMF/MRF: 8. IMS AS request DCMF/MRF to reserve and allocate media resource
+    DCMF/MRF->>DCSF: 9. Nimsas_MediaControl_MediaInstruction response
+    DCSF->>IMS AS: 10. Nimsas_SessionEventControl_Notify response
+    IMS AS->>IMCSI platform: 11. INVITE (Audio/video offer, URL information)
+    Note right of IMCSI platform: 12. IMCSI service decision
+    IMCSI platform->>IMCSI device: 13. Call negotiation
+    IMCSI platform->>DCSF: 14. IMCSI service request (URL information)
+    DCSF->>IMCSI platform: 15. IMCSI service response
+    IMCSI platform->>IMS AS: 16. 18X/PRACK/200 OK (PRACK)/UPDATE
+    IMS AS->>UE: 17. 200 OK
+    IMS AS->>DCSF: 18. Nimsas_SessionEventControl_Notify
+    DCSF->>IMS AS: 19. Nimsas_SessionEventControl_Notify response
+    IMS AS->>UE: 20. 200 OK
+    Note over UE, DCMF/MRF: 21. BDC establishment (BDC with stream ID, DC application list download, dedicated DC application request and download)
+  
+```
+
+Sequence diagram showing the U2D bootstrap data channel set up signalling procedure for IMCSI. Lifelines: UE, IMS AS, DCSF, DCMF/MRF, IMCSI platform, IMCSI device. The process involves INVITE, DC routing decision, Nimsas notifications, DC media information creation, DCMF/MRF discovery, media resource reservation, and final BDC establishment.
+
+F.748.6(25)
+
+**Figure 9-1 – U2D bootstrap data channel set up signalling procedure for IMCSI**
+
+The steps in the call flow are as follows:
+
+- Step 1: UE sends the SIP INVITE request with an initial session description protocol (SDP) to IMS AS. The initial SDP contains offers for the bootstrap data channel establishment requirement. In this example procedure, SDP contains both bootstrap data channel offers for the originating side and terminating side.
+
+NOTE 2 – This SIP INVITE can also be a SIP re-INVITE performed after the initial IMS audio session is setup.
+
+- Step 2: IMS AS validates the user subscription data to determine whether the data channel call request should be conveyed to DCSF.
+
+- Step 3: IMS AS sends Nimsas\_SessionEventControl\_Notify request to DCSF.  
+NOTE 3 – Nimsas\_SessionEventControl\_Notify is defined in AA.2.4.2.2 of [ETSI TS 123 228].
+- Step 4: After receiving the DC control request, the DCSF determines the policy about how to process the bootstrap data channel establishment requirement based on the related parameters in the data channel control request and/or operator strategy.
+- Step 5: DCSF prepares originating side DC media information based on its policies.
+- Step 6: DCSF invokes the Nimsas\_MediaControl\_MediaInstruction operation based on its policies instructing the IMS AS on how to set up a bootstrap data channel with DCMF for the originating side.  
+NOTE 4 – Nimsas\_MediaControl\_MediaInstruction is defined in AA.2.4.3.2 of [ETSI TS 123 228].
+- Step 7: IMS AS selects a DCMF based on local configuration or discovers and selects a DCMF instance or MRF supporting DC media function.
+- Step 8: IMS AS invokes DCMF service to instruct DCMF to allocate media resources for the UE.
+- Step 9: IMS AS responds to the Nimsas\_MediaControl\_MediaInstruction request received in step 6.
+- Step 10: DCSF stores the media resource information and responds to the Nimsas\_SessionEventControl\_Notify request received in step 3.
+- Step 11: IMS AS sends the INVITE which includes the updated SDP offer adding the uniform resource locator (URL) information of DCSF to the IMCSI platform.
+- Step 12: The IMCSI platform queries the IMCSI database to check whether the called device supports IMCSI service.  
+If the called device does not support IMCSI service, the IMCSI platform proceeds with normal IMS procedures to setup the call session.  
+If the called device supports IMCSI service, the IMCSI platform proceeds with the following procedures.
+- Steps 13-15: After call negotiation between the IMCSI platform and the called device, the IMCSI platform sends an IMCSI service request which includes the URL information of the IMCSI platform to the DCSF and then receives the response.  
+NOTE 5 – Due to the IMCSI platform being deployed in the IMS network, the bootstrap data channel cannot be established between a DCMF and the IMCSI platform or device. Hence the IMCSI platform is required to obtain the URL of DCSF for the following signalling or business data transmission.
+- Steps 16-17: The IMCSI platform returns an 18X and then 200 OK response.
+- Step 18: IMS AS notifies the successful session establishment event to DCSF.
+- Step 19: DCSF responds to the notification.
+- Step 20: 200 OK is forwarded to UE.
+- Step 21: The bootstrap data channels have been established between the originating DCMF/MRF and the UE. The UE sends application request messages to DCMF/MRF via the bootstrap data channel with its data channel capabilities. The DCMF/MRF forwards the message to the received media point of DCSF. The DCSF provides the proper data channel applications to the UE based on their data channel capabilities through DCMF/MRF.  
+NOTE 6 – Since it is not allowed the IMCSI devices to initiate interactive multimedia communication services, there is no bootstrap data channel being established between DCMF/MRF and the IMCSI platform or device.  
+NOTE 7 – If multiple DC applications are available, UE may request a DC applications list after bootstrap data channels establishment.
+
+#### 9.1.2 Device to UE (D2U) bootstrap data channel setup
+
+Figure 9-2 depicts a signalling flow diagram for establishing a bootstrap data channel in the IMCSI when the IMCSI device is the originating side and the UE is the terminating side, respectively.
+
+The steps in the call flow are as follows:
+
+- Steps 1-2: The IMCSI device initiates a call request, and then the IMCSI platform sends a general SIP INVITE request to IMS AS.
+- Step 3: IMS AS validates the IMCSI device subscription data to determine whether the call request should be updated to a data channel call request.
+
+NOTE – The D2U bootstrap data channel establishment procedure does not affect the IMS audio session.
+
+- Step 4: IMS AS sends Nimsas\_SessionEventControl\_Notify request to DCSF.
+- Step 5: DCSF determines whether both the originating and terminating sides support DC capacity.
+- Step 6: After receiving the DC control request, the DCSF determines the policy about how to process the bootstrap data channel establishment requirement based on the related parameters in the data channel control request and/or operator strategy.
+- Step 7: Since the SessionEstablishmentRequestEvent indicates that the UE is offered remote bootstrap media, DCSF, based on its policies prepares terminating side DC media information.
+- Step 8: DCSF invokes the Nimsas\_MediaControl\_MediaInstruction operation based on its policies instructing the IMS AS how to set up a bootstrap data channel with DCMF for the terminating side.
+- Step 9: IMS AS selects a DCMF based on the local configuration or discovers and selects a DCMF instance or MRF supporting DC media function.
+- Step 10: IMS AS invokes DCMF service to instruct DCMF to allocate media resources for the UE.
+- Step 11: IMS AS responds to the Nimsas\_MediaControl\_MediaInstruction request received in step 8.
+- Step 12: The DCSF stores the media resource information and responds to the Nimsas\_SessionEventControl\_Notify request received in step 4.
+- Steps 13-14: IMS AS sends the INVITE request with an SDP offer for establishing a bootstrap data channel to the UE. UE returns an 18X response.
+- Step 15: IMS AS forwards the 18X response with the URL information of DCSF to the IMCSI platform.
+- Step 16: The IMCSI platform queries the IMCSI database to check whether the calling device supports IMCSI service.
+
+If the calling device does not support IMCSI service, the IMCSI platform proceeds with normal IMS procedures to setup the call session.
+
+If the calling device supports IMCSI service, the IMCSI platform proceeds with the following procedures.
+
+- Steps 17-18: IMCSI platform sends an IMCSI service request which includes the URL information of the IMCSI platform to DCSF and receives a response.
+- Step 19: UE returns a 200 OK to IMS AS.
+- Step 20: IMS AS notifies the successful session establishment event to DCSF.
+- Step 21: The DCSF responds to the notification.
+
+- Step 22: 200 OK is forwarded to the IMCSI platform.
+- Step 23: The bootstrap data channels have been established between the terminating DCMF/MRF and the UE. The UE sends application request messages to DCMF/MRF via the bootstrap data channel with its data channel capabilities. The DCMF/MRF forwards the message to the received media point of DCSF. The DCSF provides the proper data channel applications to the UE based on their data channel capabilities through DCMF/MRF.
+
+![Sequence diagram showing the D2U bootstrap data channel set up signalling procedure for IMCSI. Lifelines: UE, IMS AS, DCSF, DCMF/MRF, IMCSI platform, IMCSI device. The process involves a call request from the IMCSI device, INVITE and response messages between IMS AS and UE, DC routing decisions and discovery by IMS AS, media resource reservation by IMS AS, and final BDC establishment between DCMF/MRF and UE.](c85ded401105f62f2d6ff26b3b5eb4af_img.jpg)
+
+```
+
+sequenceDiagram
+    participant IMCSI device
+    participant IMCSI platform
+    participant DCMF/MRF
+    participant DCSF
+    participant IMS AS
+    participant UE
+
+    Note right of IMCSI device: 1. Call request
+    IMCSI device->>IMCSI platform: 1. Call request
+    Note right of IMCSI platform: 2. INVITE (Audio/video offer)
+    IMCSI platform->>IMS AS: 2. INVITE (Audio/video offer)
+    Note right of IMS AS: 3. DC routing decision and DCSF discovery
+    IMS AS->>DCSF: 4. Nimsas_SessionEventControl_Notify
+    Note right of DCSF: 6. DCSF decides whether DC is provided and determines DC control policy
+    Note right of DCSF: 7. DCSF creates DC media information
+    DCSF->>IMS AS: 8. Nimsas_MediaControl_MediaInstruction
+    Note right of IMS AS: 9. DCMF/MRF discovery
+    Note right of IMS AS: 10. IMS AS request DCMF/MRF to reserve and allocate media resource.
+    IMS AS->>DCSF: 11. Nimsas_MediaControl_MediaInstruction response
+    DCSF->>IMS AS: 12. Nimsas_SessionEventControl_Notify response
+    IMS AS->>UE: 13. INVITE (Audio/video offer, SDP offer for bootstrap DC)
+    UE->>IMS AS: 14. 18X (Audio/video offer, SDP offer for bootstrap DC)
+    IMS AS->>IMCSI platform: 15. 18X (Audio/video offer, URL information)
+    Note right of IMCSI platform: 16. IMCSI service decision
+    IMCSI platform->>DCSF: 17. IMCSI service request (URL information)
+    DCSF->>IMCSI platform: 18. IMCSI service response
+    UE->>IMS AS: 19. 200 OK
+    IMS AS->>DCSF: 20. Nimsas_SessionEventControl_Notify
+    DCSF->>IMS AS: 21. Nimsas_SessionEventControl_Notify response
+    IMS AS->>IMCSI platform: 22. 200 OK
+    Note right of DCMF/MRF: 23. BDC establishment (BDC with stream ID, DC application list download, dedicated DC application request and download)
+  
+```
+
+Sequence diagram showing the D2U bootstrap data channel set up signalling procedure for IMCSI. Lifelines: UE, IMS AS, DCSF, DCMF/MRF, IMCSI platform, IMCSI device. The process involves a call request from the IMCSI device, INVITE and response messages between IMS AS and UE, DC routing decisions and discovery by IMS AS, media resource reservation by IMS AS, and final BDC establishment between DCMF/MRF and UE.
+
+F.748.6(25)
+
+**Figure 9-2 – D2U bootstrap data channel set up signalling procedure for IMCSI**
+
+### 9.2 Application data channel setup signalling procedure
+
+Figure 9-3 depicts a signalling flow diagram for establishing an application data channel in the IMCSI.
+
+The steps in the call flow are as follows:
+
+- Step 0: IMS session has been established between UE and the IMCSI device. The bootstrap data channel has been established between UE and DCMF/MRF. Data channel applications have been downloaded to the UE.
+
+- Step 1: UE sends an establishment request, which is the SIP re-INVITE request with an updated SDP, to IMS AS. The updated SDP contains the bootstrap data channel information, as well as the application data channel establishment requirement.
+
+The establishment request is used to set up the application data channel between UE and DCMF/MRF. The establishment request contains the information of the master application data channel (ADC) and the work ADC, which can form an ADC group. The negotiation parameter format of the establishment request complies with [IETF RFC 8864].
+
+- Step 2: IMS AS validates the UE subscription data to determine whether the media change request should be triggered to DCSF.
+
+- Step 3: IMS AS notifies the DCSF, via Nimsas\_SessionEventControl\_Notify of the media update request event.
+
+- Step 4: DCSF determines whether the UE supports data channel capacity.
+
+- Step 5: DCSF determines the policy about how to process the application data channel establishment requirement with UE based on the related parameters in the notification and/or operator policy.
+
+- Step 6: DCSF responds to the Nimsas\_SessionEventControl\_Notify request received in step 3.
+
+- Step 7-1: IMS AS sends the IMCSI\_Event\_Notify request to DCSF to establish an IMCSI data channel.
+
+Step 7-2: DCSF forwards this request that includes its URL information to the IMCSI platform.
+
+Steps 7-3 and steps 7-4: The IMCSI platform returns a response to DCSF and IMS AS.
+
+NOTE – The IMCSI data channel is used to carry application data sent by the UE.
+
+- Step 8-1: The IMCSI platform sends the IMCSI\_Event\_Control request that includes its URL information to DCSF.
+
+Steps 8-2, 8-3 and 8-4: After receiving the control request, IMS AS returns a response to DCSF and the IMCSI platform.
+
+- Step 9: IMS AS sends the general re-INVITE to the IMCSI platform, and then receives a 200 OK response.
+
+- Steps 10-11: The network connected to UE executes the QoS procedure for application data channel media based on the SDP answer information from the 200 OK response. UE receives the application data channel establishment response sent by IMS AS. The establishment response can contain the information of the master ADC and the work ADC, which can form an ADC group.
+
+- Step 12: UE sends ACK to the IMCSI platform.
+
+- Steps 13-1, 13-2, 13-3 and 13-4: The IMCSI\_Event\_ControlResult\_Notify request and response are transmitted among IMS AS, DCSF, and the IMCSI platform to notify the successful IMCSI data channel establishment.
+
+- Steps 14-15: The application data channel between UE and DCMF/MRF is established. The IMCSI data channel between DCMF/MRF and the IMCSI platform is established.
+
+- Step 16: UE sends a management request to DCMF/MRF through a master ADC.
+
+The management request contains at least one operation for one or more work ADCs. The operation can be the setup of work ADC, the closure of work ADC, the cooperation between work ADCs, the bandwidth configuration of work ADC, or the QoS configuration of work ADC. For instance, the cooperation between work ADCs can transmit different parts of the data to be transmitted through two or more work ADCs.
+
+- Step 17: UE receives a management response related to work ADCs sent by DCMF/MRF through the master ADC.
+
+![Sequence diagram showing the application data channel set up signalling procedure for IMCSI. Lifelines: UE, IMS AS, DCSF, DCMF/MRF, IMCSI platform, IMCSI device. The process involves IMS session establishment, bootstrap data channel establishment, ReINVITE offer, DC routing decision, Nimsas notifications, IMCSI notifications and controls, DC QoS flow setup, 200 OK response, ACK, and final IMCSI data channel activation.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UE
+    participant IMS AS
+    participant DCSF
+    participant DCMF/MRF
+    participant IMCSI platform
+    participant IMCSI device
+
+    Note over all: 0-1. IMS session has been established
+    Note over all: 0-2. Bootstrap data channel has been established
+
+    UE->>IMS AS: 1. ReINVITE (Audio/video offer, SDP offer for application DC)
+    Note right of IMS AS: 2. DC routing decision and DCSF discovery
+    IMS AS->>DCSF: 3. Nimsas_SessionEventControl_Notify
+    Note right of DCSF: 4. DCSF determines whether two sides support DC capacity
+    Note right of DCSF: 5. DCSF decides whether DC is provided and determines DC control policy
+    DCSF->>IMS AS: 6. Nimsas_SessionEventControl_Notify response
+    IMS AS->>DCSF: 7-1. IMCSI_Event_Notify
+    DCSF->>IMCSI platform: 7-2. IMCSI_Event_Notify (URL information)
+    IMCSI platform->>DCSF: 7-3. IMCSI_Event_Notify response
+    DCSF->>IMS AS: 7-4. IMCSI_Event_Notify response
+    DCSF->>IMCSI platform: 8-1. IMCSI_Event_Control (URL information)
+    IMS AS->>DCSF: 8-2. IMCSI_Event_Control
+    DCSF->>IMS AS: 8-3. IMCSI_Event_Control response
+    DCSF->>IMCSI platform: 8-4. IMCSI_Event_Control response
+    DCSF->>IMCSI platform: 9-1. Re-INVITE (Audio/video)
+    IMCSI platform->>DCSF: 9-2. 200 OK
+    Note right of UE: 10. DC QoS flow
+    IMS AS->>UE: 11. 200 OK (Audio/video offer, modified SDP answer for application DC)
+    Note over all: 12. ACK
+    IMS AS->>DCSF: 13-1. IMCSI_Event_ControlResult_Notify
+    DCSF->>IMCSI platform: 13-2. IMCSI_Event_ControlResult_Notify
+    IMCSI platform->>DCSF: 13-3. IMCSI_Event_ControlResult_Notify response
+    DCSF->>IMS AS: 13-4. IMCSI_Event_ControlResult_Notify response
+    Note left of UE: 14. ADC for UE is activated
+    DCMF/MRF->>IMCSI device: 15. IMCSI data channel is activated
+    IMS AS->>DCMF/MRF: 16. request
+    DCMF/MRF->>IMS AS: 17. response
+  
+```
+
+Sequence diagram showing the application data channel set up signalling procedure for IMCSI. Lifelines: UE, IMS AS, DCSF, DCMF/MRF, IMCSI platform, IMCSI device. The process involves IMS session establishment, bootstrap data channel establishment, ReINVITE offer, DC routing decision, Nimsas notifications, IMCSI notifications and controls, DC QoS flow setup, 200 OK response, ACK, and final IMCSI data channel activation.
+
+F.748.6(25)
+
+**Figure 9-3 – Application data channel set up signalling procedure for IMCSI**
+
+### 9.3 Application interaction procedure
+
+The interaction procedure of the IMCSI application can be divided into three categories, which are remote control, AR multimedia calling, and AI multimedia calling.
+
+#### 9.3.1 Remote control interaction procedure
+
+Remote control applications can be used for cameras, home assistant robots, table lamps, or other home IoT devices. Figure 9-4 depicts an application interaction procedure of remote control.
+
+The steps in the call flow are as follows:
+
+- Step 0-1: IMS session has been established between the UE and the IMCSI device. During this procedure, if the IMCSI device is integrated with a camera, it would receive a call request sent by the IMCSI platform and then make a response for transmitting the video data.
+- Step 0-2: The bootstrap data channel (BDC) and the application data channel (ADC) have been established for the UE. Data channel (DC) applications have been downloaded to the UE.
+- Step 0-3: The IMCSI data channel has been established for the IMCSI device.
+- Step 1: A user triggers a remote control request and then the instruction is sent through the application data channel to DCMF/MRF.
+
+NOTE 1 – Functionally, a user can click the digital button on the dial of the UE to trigger the instruction represented by dual tone multi frequency (DTMF) to control the pan/tilt/zoom (PTZ).
+
+- Step 2: DCMF/MRF is required to convert the request into an IMCSI remote control request using some protocol and sends it to the IMCSI platform via Id.
+- Step 3: The IMCSI platform forwards the IMCSI remote control request to the corresponding IMCSI device via Mi.
+
+NOTE 2 – The protocol for transmitting the IMCSI remote control request is not specified in this release of the specification. This protocol can be determined by operators.
+
+- Step 4: The IMCSI device receives the IMCSI remote control request. After conducting the control instruction, the IMCSI device returns a response.
+- Step 5: The IMCSI platform sends the response to DCMF/MRF.
+- Step 6: DCMF/MRF converts the response and sends it to the UE through the application data channel.
+
+![Sequence diagram of the remote control interaction procedure. Lifelines: UE, IMS AS, DCSF, DCMF/MRF, IMCSI platform, IMCSI device. The diagram shows six steps: 0-1. IMS session establishment between UE and IMCSI device; 0-2. IMS session, BDC and ADC establishment for UE; 0-3. IMCSI data channel establishment for IMCSI device; 1. UE triggers remote control instruction in ADC to DCMF/MRF; 2. DCMF/MRF sends IMCSI remote control request to IMCSI platform; 3. IMCSI platform forwards request to IMCSI device; 4. IMCSI device conducts instruction and returns response; 5. IMCSI platform sends response to DCMF/MRF; 6. DCMF/MRF returns response in ADC to UE.](75e4b78ee25f885d73120e3066a5253e_img.jpg)
+
+```
+sequenceDiagram
+    participant UE
+    participant IMS AS
+    participant DCSF
+    participant DCMF/MRF
+    participant IMCSI platform
+    participant IMCSI device
+
+    Note over UE, IMCSI device: 0-1. IMS session has been established between UE and the IMCSI device
+    Note over UE, DCMF/MRF: 0-2. IMS session, BDC and ADC have been established for UE
+    Note over DCMF/MRF, IMCSI device: 0-3. IMCSI data channel has been established for IMCSI device
+
+    UE->>DCMF/MRF: 1. Trigger remote control and send the instruction in ADC
+    DCMF/MRF->>IMCSI platform: 2. IMCSI remote control request
+    IMCSI platform->>IMCSI device: 3. Forward IMCSI remote control request
+    IMCSI device->>IMCSI platform: 4. Conduct remote control request instruction and return a response
+    IMCSI platform->>DCMF/MRF: 5. IMCSI remote control response
+    DCMF/MRF->>UE: 6. Return remote control response in ADC
+```
+
+Sequence diagram of the remote control interaction procedure. Lifelines: UE, IMS AS, DCSF, DCMF/MRF, IMCSI platform, IMCSI device. The diagram shows six steps: 0-1. IMS session establishment between UE and IMCSI device; 0-2. IMS session, BDC and ADC establishment for UE; 0-3. IMCSI data channel establishment for IMCSI device; 1. UE triggers remote control instruction in ADC to DCMF/MRF; 2. DCMF/MRF sends IMCSI remote control request to IMCSI platform; 3. IMCSI platform forwards request to IMCSI device; 4. IMCSI device conducts instruction and returns response; 5. IMCSI platform sends response to DCMF/MRF; 6. DCMF/MRF returns response in ADC to UE.
+
+F.748.6(25)
+
+Figure 9-4 – Remote control interaction procedure
+
+#### 9.3.2 AR multimedia calling interaction procedure
+
+Augmented reality (AR) multimedia calling can enhance the experience in the scenarios of meeting, training, and teaching with various interactive applications.
+
+Figure 9-5 depicts an application interaction procedure of using AR mark during a voice or video call session.
+
+The steps in the call flow are as follows:
+
+- Step 0-1: IMS session has been established between the UE and the IMCSI device. During this procedure, if the IMCSI device is integrated with a camera, it would receive a call request sent by the IMCSI platform and then make a response for transmitting the video data.
+- Step 0-2: The bootstrap data channel (BDC) and the application data channel (ADC) have been established for the UE. DC applications have been downloaded to the UE.
+- Step 0-3: The IMCSI data channel has been established for the IMCSI device.
+- Step 1: A user triggers an AR mark request and then the coordinate of the mark is sent through the application data channel to DCMF/MRF.
+- Step 2: UE invokes the local rendering function to add the coordinate and displays the mark on the UE screen.
+- Step 3: DCMF/MRF is required to convert the request into an IMCSI AR mark request using some protocol and sends it to the IMCSI platform via Id.
+- Step 4: The IMCSI platform forwards the IMCSI AR mark request to the corresponding IMCSI device via Mi.
+
+NOTE – The protocol for transmitting IMCSI AR mark request is not specified in this release of the specification. This protocol can be determined by the operators.
+
+- Step 5: The IMCSI device invokes a local rendering function to add the coordinate and displays the mark on the device screen.
+- Steps 6-7: The IMCSI device returns a response to the IMSCI platform and DCMF/MRF.
+- Steps 8-9: A user triggers an AR mark on the IMCSI device. Then an IMCSI AR mark request including its coordinate is sent to the IMSCI platform and DCMF/MRF.
+- Step 10: The IMCSI device invokes local rendering function to add the coordinate and displays the mark on the device screen.
+- Step 11: DCMF/MRF is required to send the coordinate to the UE through the application data channel.
+- Step 12: UE invokes the local rendering function to add the coordinate and displays the mark on the UE screen.
+- Step 13: UE returns a response to DCMF/MRF.
+
+![Sequence diagram for AR multimedia calling interaction procedure. Lifelines: UE, IMS AS, DCSF, DCMF/MRF, IMCSI platform, IMCSI device. The diagram shows the interaction flow for establishing AR sessions and handling AR requests.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UE
+    participant IMS AS
+    participant DCSF
+    participant DCMF/MRF
+    participant IMCSI platform
+    participant IMCSI device
+
+    Note over UE, IMCSI device: 0-1. IMS session has been established between UE and the IMCSI device
+    Note over UE, DCMF/MRF: 0-2. IMS session, BDC and ADC have been established for UE
+    Note over DCMF/MRF, IMCSI device: 0-3. IMCSI data channel has been established for IMCSI device
+
+    UE->>DCMF/MRF: 1. Trigger AR mark and send the coordinate in ADC
+    Note left of UE: 2. Local rendering and display
+    DCMF/MRF->>IMCSI platform: 3. IMCSI AR request request
+    IMCSI platform->>IMCSI device: 4. Forward IMCSI AR request
+    Note right of IMCSI device: 5. Local rendering and display
+    IMCSI device->>IMCSI platform: 6. IMCSI AR response
+    IMCSI platform->>DCMF/MRF: 7. IMCSI AR response
+    DCMF/MRF->>IMCSI device: 8. Trigger AR mark on IMCSI device and send the coordinate
+    Note right of IMCSI device: 9. Local rendering and display
+    IMCSI device->>DCMF/MRF: 10. IMCSI AR response (coordinate)
+    DCMF/MRF->>UE: 11. Send the coordinate in ADC
+    Note left of UE: 12. Local rendering and display
+    UE->>DCMF/MRF: 13. Return trigger AR mark response
+  
+```
+
+F.748.6(25)
+
+Sequence diagram for AR multimedia calling interaction procedure. Lifelines: UE, IMS AS, DCSF, DCMF/MRF, IMCSI platform, IMCSI device. The diagram shows the interaction flow for establishing AR sessions and handling AR requests.
+
+**Figure 9-5 – AR multimedia calling interaction procedure**
+
+#### 9.3.3 AI multimedia calling interaction procedure
+
+Artificial intelligence (AI) multimedia calling would introduce some AI functions to enhance the experience in the multimedia communication, for instance, simultaneous translation.
+
+Figure 9-6 depicts an application interaction procedure of using simultaneous translation during a voice or video call session.
+
+![Sequence diagram of AI multimedia calling interaction procedure. Lifelines: UE, IMS AS, DCAS, DCSF, DCMF/MRF, MCP, IMCSI platform, IMCSI device. The diagram shows the flow of data and requests for translation between the UE and the IMCSI device via the DCMF/MRF and DCAS.](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UE
+    participant IMS AS
+    participant DCAS
+    participant DCSF
+    participant DCMF/MRF
+    participant MCP
+    participant IMCSI platform
+    participant IMCSI device
+
+    Note over UE, IMCSI device: 0-1. IMS session has been established between UE and the IMCSI device
+    Note over UE, DCMF/MRF: 0-2. IMS session, BDC and ADC have been established for UE
+    Note over DCMF/MRF, IMCSI device: 0-3. IMCSI data channel has been established for IMCSI device
+
+    UE->>DCMF/MRF: 1. Trigger simultaneous translation and send request in ADC
+    DCMF/MRF->>DCAS: 2. Send application request
+    DCAS->>DCMF/MRF: 3. Stream copy request
+    DCMF/MRF->>DCSF: 4. Copy the stream of UE
+    DCSF->>DCMF/MRF: 5. Translate the speech of UE and make Speech-to-Text
+    DCMF/MRF->>DCSF: 6. Return text
+    DCMF/MRF->>UE: 7. Return text in ADC
+    UE->>UE: 8. Add text to the stream and display
+
+    Note over DCSF, IMCSI device: 12. Copy the stream of IMCSI device
+    DCSF->>DCMF/MRF: 13. Translate the speech of IMCSI device and make Speech-to-Text
+    DCMF/MRF->>DCSF: 14. Return text
+    DCMF/MRF->>UE: 15. Return text in ADC
+    UE->>UE: 16. Add text to the stream and display
+
+    DCMF/MRF->>IMCSI platform: 9. Send text
+    IMCSI platform->>IMCSI device: 10. Forward text
+    IMCSI device->>IMCSI device: 11. Add text to the stream and display
+
+    DCMF/MRF->>IMCSI platform: 17. Send text
+    IMCSI platform->>IMCSI device: 18. Forward text
+    IMCSI device->>IMCSI device: 19. Add text to the stream and display
+  
+```
+
+Sequence diagram of AI multimedia calling interaction procedure. Lifelines: UE, IMS AS, DCAS, DCSF, DCMF/MRF, MCP, IMCSI platform, IMCSI device. The diagram shows the flow of data and requests for translation between the UE and the IMCSI device via the DCMF/MRF and DCAS.
+
+F.748.6(25)
+
+**Figure 9-6 – AI multimedia calling interaction procedure**
+
+The steps in the call flow are as follows:
+
+- Step 0-1: IMS session has been established between the UE and the IMCSI device. During this procedure, if the IMCSI device is integrated with a camera, it would receive a call request sent by the IMCSI platform and then make a response for transmitting the video data.
+- Step 0-2: The bootstrap data channel (BDC) and the application data channel (ADC) have been established for the UE. DC applications have been downloaded to the UE.
+- Step 0-3: The IMCSI data channel has been established for the IMCSI device.
+- Step 1: A user triggers the simultaneous translation and then the request is sent through the application data channel to DCMF/MRF.
+- Step 2: DCMF/MRF sends a request to data channel application server (DCAS) for duplicating a stream that needs to be translated.
+- Step 3: DCAS validates UE subscription data to determine whether the stream should be provided.
+
+- Step 4: After receiving permission from DCAS, DCMF/MRF duplicates the stream of UE and pushes it to MCP.
+- Step 5: MCP translates the speech in the stream of UE and makes speech-to-text conversion.
+- Step 6: MCP sends the text to DCMF/MRF via Mc.
+- Step 7: DCMF/MRF sends the text to the UE in the application data channel.
+- Step 8: UE adds the text into the stream and displays the text on the screen.
+- Step 9: DCMF/MRF sends the text to the IMCSI platform via Mt.
+- Step 10: The IMCSI platform forwards the text to the IMCSI device via Mi.
+- Step 11: The IMCSI device adds the text into the stream and displays the text on the screen.
+- Step 12: DCMF/MRF duplicates the stream of the IMCSI device and pushes it to MCP.
+- Step 13: MCP translates the speech in the stream of the IMCSI device and makes speech-to-text conversion.
+- Steps 14-19: The same with Steps 6-11.
+
+## Appendix I
+
+## Typical use cases and scenarios
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This clause describes the typical use cases and scenarios.
+
+Interactive multimedia communication system for Internet of things devices (IMCSI) system has been applied to support video communication and home surveillance services. It can simultaneously support data transmission and intelligent interactions among mobile phones and IoT devices. By sending control signalling along with the data channel (DC), it not only realizes IoT-based remote control but also launches many AI-based services, such as real time translation, virtual portrait, and gesture recognition.
+
+Typical scenarios are shown in Figure I.1 and four applications are introduced as follows.
+
+- Remote control scenario: By communicating with the AI-based table lamp, users are able to turn the lamp on/off, adjust the light intensity, etc.
+- Home surveillance scenario: By communicating with the intelligent home surveillance camera, users are able to realize the functions, such as remote live video watch, playback query and pan/tilt/zoom (PTZ) adjustment.
+- Video meeting scenario: During a video meeting, users are able to start several AI-based functions to facilitate communication, such as NLP or AI-based image processing, to make a real-time translation or virtual portrait show on the shared conversation screen.
+- AI-based assistance scenario: During video communication, users can talk with elderly people and provide the necessary instructions or assistance remotely.
+
+![Diagram illustrating the typical scenarios of IMCSI. It shows three main components: End user, IMCSI platform, and IMCSI devices. The End user includes Mobile and Smart speaker. The IMCSI platform is a central server icon. The IMCSI devices include Table lamp, Camera, Smart speaker, and Smart TV. Arrows labeled 'DC' indicate data flow between the End user and the IMCSI platform, and between the IMCSI platform and the IMCSI devices. Below the device icons are four application scenarios: Remote control, Surveillance, Video meeting, and AI-based assistance.](20136850feb70fd71c7d41cdae203ebb_img.jpg)
+
+The diagram illustrates the architecture of the IMCSI system. On the left, the 'End user' section contains icons for a 'Mobile' phone and a 'Smart speaker'. In the center, the 'IMCSI platform' is represented by a server icon. On the right, the 'IMCSI devices' section includes icons for a 'Table lamp', 'Camera', 'Smart speaker', and 'Smart TV'. Below these device icons are four application scenarios: 'Remote control', 'Surveillance', 'Video meeting', and 'AI-based assistance'. Blue arrows labeled 'DC' indicate the data flow from the End user to the IMCSI platform, and from the IMCSI platform to the IMCSI devices.
+
+Diagram illustrating the typical scenarios of IMCSI. It shows three main components: End user, IMCSI platform, and IMCSI devices. The End user includes Mobile and Smart speaker. The IMCSI platform is a central server icon. The IMCSI devices include Table lamp, Camera, Smart speaker, and Smart TV. Arrows labeled 'DC' indicate data flow between the End user and the IMCSI platform, and between the IMCSI platform and the IMCSI devices. Below the device icons are four application scenarios: Remote control, Surveillance, Video meeting, and AI-based assistance.
+
+F.748.6(25)
+
+Figure I.1 – Typical scenarios of IMCSI
+
+# Bibliography
+
+- [b-ITU-T Y.4000] Recommendation ITU-T Y.4000/Y.2060 (2012), *Overview of the Internet of things*.
+- [b-ETSI TS 126 114] ETSI TS 126 114 V18.6.0 (2024), *Universal Mobile Telecommunications System (UMTS); LTE; 5G; IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction (3GPP TS 26.114 version 18.6.0 Release 18)*.  
+<<https://cdn.standards.iteh.ai/samples/70669/edc4d3a0aac4ab4a462b389855e3238/ETSI-TS-126-114-V18-6-0-2024-05-.pdf>>
+- [b-GSMA NG.129] GSMA NG.129 (2021), *IMS Data Channel White Paper*.  
+<<https://www.gsma.com/newsroom/wp-content/uploads/NG.129-v1.0-1.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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.749.18-202406-I_PDF-E/raw.md b/marked/F/T-REC-F.749.18-202406-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..55eed2c898235941c3257feadbeb347e187d2fbe
--- /dev/null
+++ b/marked/F/T-REC-F.749.18-202406-I_PDF-E/raw.md
@@ -0,0 +1,519 @@
+
+
+# Recommendation**ITU-T F.749.18 (06/2024)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+---
+
+### **Framework and requirements for emergency services using civilian unmanned aerial vehicles**
+
+![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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.749.18
+
+# Framework and requirements for emergency services using civilian unmanned aerial vehicles
+
+## Summary
+
+When emergency occurs, there are always two critical things to consider: to find the survivors and to reduce the loss However, it is dangerous and difficult for human beings to observe or enter the scene in time. By using civilian unmanned aerial vehicles (CUAVs) that carry base stations or observation equipment (such as cameras and sensors), administrators can easily analyse the situation and make decisions.
+
+Recommendation ITU-T F.749.18 provides the framework and requirements for emergency services using civilian unmanned aerial vehicles, which meets the needs of emergency use cases.
+
+## History\*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.749.18 | 2024-06-13 | 16          | 11.1002/1000/15918 |
+
+## Keywords
+
+Civilian unmanned aerial vehicle, emergency services.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 within this document .....                                         | 2  |
+| 4          | Abbreviations and acronyms .....                                                 | 2  |
+| 5          | Convention.....                                                                  | 2  |
+| 6          | Introduction .....                                                               | 3  |
+| 7          | Framework of emergency services using civilian unmanned aerial vehicles.....     | 3  |
+| 7.1        | Device layer.....                                                                | 4  |
+| 7.2        | Network layer .....                                                              | 5  |
+| 7.3        | Service layer .....                                                              | 5  |
+| 7.4        | Application layer .....                                                          | 5  |
+| 8          | Requirements for emergency services using civilian unmanned aerial vehicle ..... | 5  |
+| 8.1        | Requirements for emergency communications .....                                  | 5  |
+| 8.2        | Requirements for emergency rescue and evaluation .....                           | 8  |
+| 8.3        | Requirements for service management .....                                        | 9  |
+| Appendix I | – Use cases of emergency services using civilian unmanned aerial vehicles.....   | 10 |
+| I.1        | Emergency communication support for natural disasters .....                      | 10 |
+| I.2        | Communication guarantee in hot spot areas .....                                  | 11 |
+| I.3        | Disaster scene with trapped people search and rescue.....                        | 11 |
+|            | Bibliography.....                                                                | 12 |
+
+
+
+# Recommendation ITU-T F.749.18
+
+## Framework and requirements for emergency services using civilian unmanned aerial vehicles
+
+## 1 Scope
+
+This Recommendation specifies the framework and requirements for emergency services using civilian unmanned aerial vehicles. The scope of this Recommendation includes framework, requirements and use cases for emergency services using civilian unmanned aerial vehicles.
+
+## 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 civilian unmanned aerial vehicle (CUAV)** [b-ITU-T F.749.10]: An unmanned flying device controlled by a ground control station or telecontroller via various wireless communication means. It usually consists of an aeroplane body, a power device, aviation electrical and electronic equipment and mission payload equipment, etc. and is used in non-military application areas such as industrial and consumer areas to complete the specific operation and transportation of data including audio, video and image.
+
+**3.1.2 flight control system** [b-ITU-T F.749.10]: This is the sum of all components and driving devices of instruction transferring, rudder motion. It is mainly composed of airborne and ground control terminals. The one that is airborne includes three parts: airborne sensors, steering engine and flight control units.
+
+**3.1.3 ground control station** [b-ITU-T F.749.10]: A ground control station is a device which is used to realize the functions of mission planning, flight control, payload control, flight path display, parameter display, image and video display and mission information displaying, recording and distributing.
+
+**3.1.4 mission payload equipment** [b-ITU-T F.749.10]: The mission payload equipment consists of an audio/video/image acquisition device, signal relay device, remote electronic detection/sense device and other auxiliary devices.
+
+**3.1.5 telecontroller** [b-ITU-T F.749.10]: A piece of equipment used by human beings to control an unmanned aerial vehicle. It is usually composed of an operating device, coding device, transmitting device, receiving device, decoding device and executing mechanism.
+
+**3.1.6 inspection and examination (IaE)** [b-ITU-T F.749.15]: A process to carefully check and look over specific objects/facilities and surroundings to determine whether these objects and surroundings are in a normal, damaged, dangerous or defective state.
+
+### **3.2 Terms defined within this document**
+
+This Recommendation defines the following term:
+
+**3.2.1 intelligentization:** The process of adding artificial intelligence to a system, service or application.
+
+## **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|              |                                                        |
+|--------------|--------------------------------------------------------|
+| AI           | Artificial Intelligence                                |
+| APN          | Access Point Name                                      |
+| AR           | Augmented Reality                                      |
+| CUAV         | Civilian Unmanned Aerial Vehicle                       |
+| DNN          | Data Network Name                                      |
+| eSIM         | Embedded-SIM                                           |
+| GIS          | Geographic Information System                          |
+| GPS          | Global Positioning Service                             |
+| IaE          | Inspection and Examination                             |
+| IMSI         | International Mobile Subscriber Identity               |
+| IMT-2020     | International Mobile Telecommunication System-2020     |
+| IMT-Advanced | International Mobile Telecommunication System-Advanced |
+| IoT          | Internet of Things                                     |
+| MR           | Mixed Reality                                          |
+| RRU          | Remote radio unit                                      |
+| SIM          | Subscriber Identification Module                       |
+| TAC          | Tracking Area Code                                     |
+| VR           | Virtual Reality                                        |
+
+## **5 Convention**
+
+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" 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**
+
+Civilian unmanned aerial vehicles (CUAVs) have gradually become important in the emergency industry. They have integrated telecommunication capabilities, Internet of things, big data, artificial intelligence and other technologies. This boosts the outstanding advantages of efficiency, safety, reliability and cost performance that manual operation does not possess. During emergencies, CUAVs play important roles in many fields such as terrain mapping, reconnaissance and communication. CUAVs are especially efficient in emergency handling for the construction of emergency communication channels and networks, facilitating good technical support with minimal human costs. By overcoming the difficulties of the objective environment, CUAVs provide important support for the work of the emergency communication teams and the handling of emergencies. When emergency occurs, there are always two critical things to consider: to find the survivors and to reduce the loss. However, it is dangerous and difficult for human beings to observe or enter the scene in time. With CUAVs carrying a base station or observation equipment (such as cameras or sensors), administrators can easily analyse the situation and make decisions.
+
+## **7 Framework of emergency services using civilian unmanned aerial vehicles**
+
+Figure 1 illustrates that the overall framework of emergency services using civilian unmanned aerial vehicles. Four layers are defined here: The device, network, service and application layers.
+
+![A four-layer diagram showing the framework of emergency services using civilian unmanned aerial vehicles (CUAVs). The layers are: Application layer (Operation and Management), Service layer (Capacities and Access), Network layer (Networking and transport), and Device layer (CUAV and End-user device).](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg)
+
+The diagram illustrates the framework of emergency services using civilian unmanned aerial vehicles (CUAVs), organized into four layers:
+
+- Application layer:**
+  - Operation:** Statistics, Analysis, Supervision, Mission.
+  - Management:** Flight, Stuff, Airspace, Fee, Device.
+- Service layer:**
+  - Capacities:** AI, Live, GIS, Etc.
+  - Capacities:** Videos, Etc.
+  - Access:** (Empty box).
+- Network layer:**
+  - Networking and transport:** (Top section).
+  - Non-cellular network access:** Satellite.
+  - Cellular network access:** 4G, 5G.
+- Device layer:**
+  - CUAV:**
+    - Airborne terminal:** (Left side).
+    - Back-end device:** (Right side, containing Payloads: Base station, Satellite communication equipment, Observation and sensor equipment).
+  - End-user device:**
+    - Computer, AR/VR/MR terminal.
+    - TV, Mobile phone.
+
+Emergency communication connections are indicated by a green line at the bottom.
+
+A four-layer diagram showing the framework of emergency services using civilian unmanned aerial vehicles (CUAVs). The layers are: Application layer (Operation and Management), Service layer (Capacities and Access), Network layer (Networking and transport), and Device layer (CUAV and End-user device).
+
+F.749.18(24)
+
+**Figure 1 – Framework of emergency services using civilian unmanned aerial vehicles**
+
+### 7.1 Device layer
+
+The device layer consists of back-end devices and end-user devices.
+
+Back-end devices are used for communications relay and the collection of environmental information collections during emergencies. By carrying airborne terminals, CUAVs can access non-cellular networks such as satellite networks and cellular networks. To carry out missions, CUAVs are required to carry mission payloads. For the task of communication relay, CUAVs are required to carry base stations and are recommended to carry satellite communications equipment. For observation and remote sensing tasks, CUAVs are required to carry cameras and certain kinds of rescue sensors. For communication networking tasks, CUAVs are required to carry communication and networking modules.
+
+End-user devices, which are user oriented, are used for communications, situation view, command and control. End-user devices include but are not limited to computers, TVs, augmented reality (AR)/virtual reality (VR)/mixed reality (MR) terminals and mobile phones. They can all be used for
+
+observation. Computers and mobile phones are recommended to be used for communications, command and control.
+
+### **7.2 Network layer**
+
+The network layer plays a crucial role in emergency data transmission, providing satellite access or terrestrial cellular access for CUAVs, and cellular access for rescuer workers as well as trapped personnel. In search and rescue, it is very important to have communications between rescuers, or between rescuer workers and trapped personnel, or between trapped personnel and their friends or relatives. To support the requirements when the telecommunication infrastructure has been destroyed, two ways for CUAVs to access the network are proposed: one is satellite access, as satellite systems can connect to almost everywhere on the earth, and the other is terrestrial cellular access.
+
+### **7.3 Service layer**
+
+The service layer provides service capacities and access. The service capacities include artificial intelligence (AI) processing, live broadcasting, geographic information system (GIS) processing, video shooting, etc. Only when service access is successful, management and command personnel are allowed to access the emergency service system.
+
+### **7.4 Application layer**
+
+The application layer is proposed to provide applications to management and command personnel. The application layer consists of two parts: operation and management. To support different emergency services and scenarios, various applications should be provided in the application layer, such as data statistics and analysis, emergency situation supervision, and mission deployment. To facilitate the operation of relevant personnel, these applications are used for emergency situation analysis and handling. Besides these, management functions include but are not limited to flight management, staff management, device management, airspace management and fee charging.
+
+## **8 Requirements for emergency services using civilian unmanned aerial vehicle**
+
+### **8.1 Requirements for emergency communications**
+
+#### **8.1.1 Requirements for CUAVs**
+
+For emergency service scenarios, CUAVs are mainly divided into two categories: CUAVs providing communication relay and CUAVs performing specific missions such as inspection, examination, etc. CUAVs providing communication relay include mooring CUAVs and long- endurance CUAVs. Both kinds of CUAVs carry high-altitude base stations.
+
+RC-01: It is recommended that long-endurance CUAVs are used for communication relay in emergency communication cases instead of mooring CUAVs, as they are more flexible and can give quicker responses.
+
+RC-02: It is recommended that multiple kinds of CUAVs are able to work together, including CUAVs providing communication relay and CUAVs performing specific missions.
+
+RC-03: CUAVs providing communication relay are required to carry base stations, and send and receive the data of the emergency communication services from mobile phones or Internet of things (IoT) equipment in the covered areas.
+
+RC-04: Mooring platforms for mooring CUAVs are required to provide electric power and communication signals.
+
+RC-05: Long-endurance CUAVs providing communication relay are recommended to carry base stations integrating radiofrequency (RF) and baseband to reduce the weight.
+
+RC-06: Long-endurance CUAVs providing communication relay are recommended to carry satellite communication equipment, and send and receive the data of the emergency communication services in the covered areas through satellite communications links.
+
+RC-07: For long-endurance CUAVs providing communication relay, it is recommended that base stations are able to communicate to satellite communication equipment.
+
+RC-08: For long-endurance CUAVs providing communication relay, it is recommended that they work in pairs, so that one can timely replace the other in case the first one runs out of power. Continuous communication is achieved this way.
+
+#### **8.1.2 Requirements for rescue terminals**
+
+Rescue terminals includes terminals of rescue workers and IoT equipment such as CUAVs for inspection and examination.
+
+RRT-01: Rescue terminals are recommended to use specific IoT subscriber identification module (SIM) or embedded SIM (eSIM) cards for emergency service, so as to identify rescue terminals and guarantee their communication service quality.
+
+#### **8.1.3 Requirements for the network**
+
+RRN-01: Networks of emergency services using CUAVs are required to provide communication relay in emergency scenarios where terrestrial communication networks are not available, such as following natural disasters or in remote or mountainous areas.
+
+##### **8.1.3.1 Requirements for the satellite communication network**
+
+RSC-01: In areas without coverage of terrestrial cellular communication networks, it is required that CUAVs for emergency communication are allowed to access satellite communication networks through high or low orbit satellites.
+
+RSC-02: In areas without coverage of terrestrial cellular communication networks, satellite communication networks are required to send communication data of CUAVs back to a gateway, and send communication data from the gateway to CUAVs.
+
+##### **8.1.3.2 Requirements for the terrestrial cellular communication network**
+
+RTC-01: For terrestrial cellular communication networks, both public networks and IoT networks are recommended to be used for emergency communication services using CUAVs.
+
+RTC-02: It is recommended that a unique emergency service tracking area code (TAC) is assigned to the base station of each CUAV.
+
+RTC-03: It is recommended that international mobile telecommunication system-2020 (IMT-2020) core networks have access policy configuration function for emergency communications.
+
+RTC-04: Terrestrial cellular communication networks are required to communicate with satellite communication networks via a gateway.
+
+##### **8.1.3.3 Requirements and features for gateways**
+
+###### **8.1.3.3.1 Requirements for the gateway**
+
+RG-01: It is recommended that the gateway be able to establish communications between satellites and international mobile telecommunication system-advanced (IMT-Advanced)/IMT-2020 core networks.
+
+###### **8.1.3.3.2 Features for gateways**
+
+Emergency communication service dataflows between satellite networks and terrestrial cellular networks are recommended to go through a gateway. Communication dataflows in emergency scenarios are transmitted from the base stations that are carried by CUAVs to the satellite, and then
+
+to terrestrial cellular networks through a gateway. In the reverse process, communication dataflows from terrestrial cellular networks are transmitted to the terminals in the coverage area of a CUAV.
+
+##### **8.1.3.4 Requirements for differentiated emergency communication services**
+
+Because of limited bandwidth and large delay of satellite communication links, which may become bottlenecks in network connection, it is recommended to differentiate the emergency communication services and give priority to key services.
+
+RDE-01: For a stable and reliable emergency system of rescue, it is recommended to ensure that priority is given to emergency communications.
+
+RDE-02: It is recommended that mobile communication core networks identify some TACs as emergency service TACs.
+
+RDE-03: It is recommended that a unique emergency service TAC is assigned to the base station of each CUAV.
+
+RDE-04: Communication data flows from the base stations with emergency service TACs are recommended to be identified as emergency communications service data flows.
+
+RDE-05: It is recommended that communication services in emergency scenarios contain the three categories defined in RDE-06, RDE-07 and RDE-08.
+
+RDE-06: Call service for rescue workers using specific IoT SIM or eSIM cards for emergency service is recommended to be identified as the first category.
+
+RDE-07: Data transmission service for IoT equipment is recommended to be identified as the second category.
+
+RDE-08: Other communication service using non-IoT SIM or eSIM cards is recommended to be identified as the third category.
+
+RDE-09: It is recommended that communication services in emergency scenarios are divided into different priority levels.
+
+RDE-10: It is recommended that the priority level of a certain communication service is determined by the emergency service TAC and the communication service category.
+
+RDE-11: It is recommended that the terrestrial cellular core network identifies a certain TAC as an emergency service TAC.
+
+RDE-12: It is recommended that dataflows from areas with this TAC are identified as emergency communication service dataflows.
+
+RDE-13: For emergency communication service dataflows, service of the first category is recommended to be identified as the first-priority service.
+
+RDE-14: Service of the second category is recommended to be identified as the second-priority service.
+
+RDE-15: Service of the third category is recommended to be identified as the third-priority service.
+
+RDE-16: It is recommended that mobile communication networks set up several emergency access point names (APNs)/ data network names (DNNs) and specify priority levels for the emergency APNs/DNNs.
+
+RDE-17: For emergency communication service data flows, it is recommended that emergency communication service data flows of a certain priority level be directed to the APN/DNN of the same priority level.
+
+RDE-18: It is recommended that a whitelist be specified for each emergency APN/DNN.
+
+RDE-19: It is recommended that a different data rate limit be set for each APN/DNN with a certain priority.
+
+### **8.2 Requirements for emergency rescue and evaluation**
+
+#### **8.2.1 Requirements for the emergency surveying and mapping service**
+
+In natural disaster scenarios, the natural environment and resources need to be rapidly monitored and evaluated.
+
+RES-01: With the mapping equipment of CUAVs, it is recommended that the geographic information is obtained through aerial images or radar scanning.
+
+RES-02: Combining with post-processing technology, accurate measurement and three-dimensional reconstruction of the ground features and terrain are recommended to be realized.
+
+RES-03: It is recommended that multi-modal data is acquired simultaneously, such as image, radar and navigation data.
+
+RES-04: It is recommended that the data acquired by CUAVs is used in collaboration with other data sources, such as satellite images and ground mapping data.
+
+RES-05: It is recommended that AI technology is used for CUAV emergency surveying and mapping service, so as to realize automatization and intelligentization, and improve work efficiency.
+
+RES-06: It is recommended that CUAVs have the ability to encode and decode video streams, support the acquisition and transmission of video streams, achieve docking with the drone control platform, and push videos to the platform side.
+
+RES-07: It is recommended that CUAVs support the setting of streaming media, streaming addresses and ports, video output resolution and video bit rate.
+
+RES-08: It is recommended that CUAVs support local video caching for recent time periods, and set the storage format for cached video files.
+
+RES-09: It is recommended that user experience of CUAVs may be ensured when processing high-resolution streaming media and running large-scale applications, to avoid video interruption, low resolution, and terminal over-heating.
+
+#### **8.2.2 Requirements for personnel search and rescue**
+
+RPS-01: It is recommended that rescue personnel get the location of trapped personnel, so that rescue can be carried out.
+
+RPS-02: It is recommended that CUAVs carry mobile communication base stations.
+
+RPS-03: The mobile communication base stations of CUAVs are recommended to adopt omnidirectional structure and omnidirectional antennas, and transmit IMT-Advanced/IMT-2020 signals of all carrier networks to terminals of trapped personnel within the coverage area of the CUAVs.
+
+RPS-04: It is recommended that terminals of trapped personnel initiate registration requests including international mobile subscriber identity (IMSI) after obtaining a wireless signal.
+
+RPS-05: It is recommended that the mobile communication base station of CUAV obtains the registration requests of terminals of trapped personnel, then gets its own location by Global Positioning Service (GPS).
+
+RPS-06: It is recommended that after getting the registration requests, the mobile communication base station disconnects from the terminals of trapped personnel and the IMT-Advanced/IMT-2020 core network and connects to the satellite communication equipment of one same CUAV.
+
+RPS-07: It is recommended that the mobile communication base station sends CUAV's location information and the IMSI information to the satellite communication equipment.
+
+RPS-08: It is recommended that CUAVs used for drone flight carry satellite communication equipment.
+
+RPS-09: It is recommended that the satellite communication equipment connects to the mobile communication base station of the same CUAV, so it gets CUAV's location information and the IMSI information from the mobile communication base station, and sends the above information to the ground control station at the same time.
+
+RPS-10: It is recommended that the ground control station obtains the CUAV's location information and the IMSI information at the same time, identifies the user identity information by IMSI information, and locates the user's target area as the CUAV's location information.
+
+RPS-11: If more precise location information is needed for the rescue, ground control stations are recommended to command CUAVs to reduce the hover range in the target area after locating the user's target area for the first time, and the target location where the user is located is obtained according to the frequency and intensity of registration requests in the hover range.
+
+RPS-12: It is recommended that CUAV obtains its own location information and IMSI information of registered terminals periodically when in movement.
+
+RPS-13: It is recommended that once the CUAV obtains its own location information and IMSI information of registered terminals, it immediately sends the information to the ground control station through satellite.
+
+#### **8.2.3 Requirements for perception of environment**
+
+In many disaster scenarios, further environmental parameters are needed so as to respond accordingly.
+
+RPE-01: It is recommended that CUAVs carry special sensors for further environmental parameters, including gas detectors used in toxic environment, geomagnetic sensors used in earthquake and flood, etc.
+
+RPE-02: It is recommended that CUAVs send the environmental parameters detected by special sensors to the ground control station.
+
+### **8.3 Requirements for service management**
+
+RSM-01: Ground control stations are recommended to support automatic or manual generation of task plan.
+
+RSM-02: Ground control stations are recommended to integrate and display flight parameters and mission parameters, which can be used by operators to analyse and judge the flight status of the CUAV and the status of the mission load equipment.
+
+RSM-03: Ground control stations are recommended to remotely operate and control the payload equipment carried by CUAV to complete the mission tasks.
+
+RSM-04: Ground control stations are recommended to display flight heading and track parameters in real time, including flight altitude, speed, flight track coordinates, flight attitude, flight time and navigation parameters of CUAVs.
+
+RSM-05: Ground control stations are recommended to support the function of automatic map roaming, scheduled flight track and real-time flight track display of CUAVs.
+
+RSM-06: Ground control stations are recommended to support the setting of travel routes of CUAVs.
+
+RSM-07: Ground control stations are recommended to support multiple flight control modes for different environments.
+
+## Appendix I
+
+## Use cases of emergency services using civilian unmanned aerial vehicles
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Typical application scenarios of the CUAV emergency communication system include emergency communication support in natural disaster scenarios, capacity expansion in hot spots, search and rescue of trapped people in disaster scenarios, and other scenarios in demand.
+
+### I.1 Emergency communication support for natural disasters
+
+When the terrestrial cellular network is paralyzed due to disasters or other reasons, it is difficult to recover it in a short time. CUAVs can guarantee temporary communications to for the affected areas by carrying a communication base station.
+
+Untied CUAVs have more flexibility than mooring CUAVs. They can provide quick communication support for vehicles or complex ground equipment, to ensure that trapped persons can contact rescue personnel during the search and rescue process. Such system composition is illustrated in Figure I.1.
+
+![Figure I.1: Network architecture of emergency services using civilian unmanned aerial vehicle. The diagram shows a Long-endurance CUAV connected to a Satellite and a Ground station. The Satellite is connected to a Ground station via a Network dedicated line. The Ground station is connected to a Gateway, which is connected to a Terrestrial cellular network. The Terrestrial cellular network is connected to a Metropolitan area network, a Bearer network, and an Access network. The Metropolitan area network, Bearer network, and Access network are connected to a Ground control station. The Long-endurance CUAV is connected to an Inspection CUAV and a User terminal. The Inspection CUAV is connected to a Ground control station. The User terminal is connected to a Ground control station.](cb4cfa42ce34febde7bdb882f3fc3094_img.jpg)
+
+The diagram illustrates a network architecture for emergency services. At the top, a 'Satellite' is shown. Below it, a 'Long-endurance CUAV' is connected to the satellite via a yellow lightning bolt. To the right, a 'Ground station' (represented by a satellite dish) is also connected to the satellite. A red line labeled 'Network dedicated line' connects the ground station to a 'Gateway' (represented by a small building icon). The gateway is connected to a 'Terrestrial cellular network' (represented by a cell tower icon). This network is further connected to three cloud-like shapes labeled 'Metropolitan area network', 'Bearer network', and 'Access network'. These three networks are all connected to a 'Ground control station' (represented by a truck icon). On the left side, the 'Long-endurance CUAV' is shown emitting signals (yellow lightning bolts) to an 'Inspection CUAV' (represented by a drone icon) and a 'User terminal' (represented by a smartphone icon). Both the inspection CUAV and the user terminal are connected to the 'Ground control station'.
+
+Figure I.1: Network architecture of emergency services using civilian unmanned aerial vehicle. The diagram shows a Long-endurance CUAV connected to a Satellite and a Ground station. The Satellite is connected to a Ground station via a Network dedicated line. The Ground station is connected to a Gateway, which is connected to a Terrestrial cellular network. The Terrestrial cellular network is connected to a Metropolitan area network, a Bearer network, and an Access network. The Metropolitan area network, Bearer network, and Access network are connected to a Ground control station. The Long-endurance CUAV is connected to an Inspection CUAV and a User terminal. The Inspection CUAV is connected to a Ground control station. The User terminal is connected to a Ground control station.
+
+**Figure I.1 – An example of network architecture of emergency services using civilian unmanned aerial vehicle**
+
+Long-endurance CUAVs carry base stations to provide communication connections to user terminals. Additionally, they carry satellite communication equipment to connect to satellites. Satellite communication network connects to terrestrial cellular network through gateway. That way, rescuers and trapped persons can make calls or send messages using their phones, and rescue work will be facilitated.
+
+Such scenarios generally have high voice demand, and there may be different degrees of data service requirements according to the different scenarios. When the coverage is wide, multi-mode high-power remote radio unit (RRU) with both voice and data service capability can be given priority. When the coverage requirement is not high or the data service capacity is small, a single-mode micropower RRU is used to provide sufficient voice support capability, or a multi-mode micropower RRU can be used to take into account some data service requirements. When the coverage demand is not high, but the data service capacity demand is high, multi-frequency multi-mode micropower RRU can be preferred. At the same time, considering that providing stable coverage is usually the primary goal in such scenarios, omnidirectional antennas, which are less affected by external factors, are generally preferred as the external antenna to cooperate with the base station equipment.
+
+### **I.2 Communication guarantee in hot spot areas**
+
+Large-scale events and gatherings will lead to a surge of communication volume, exceeding the carrying capacity of conventional network facilities. The reserved CUAV emergency communication system can be used to temporarily increase network capacity in hot spots to support the smooth progress of user business and ensure user experience.
+
+In such scenarios priority is given to data business requirements, and the preferred equipment is IMT-2020 single mode equipment. To cover all the possible scenarios an IMT-2020 single mode high power RRU can be chosen. To cover small demand scenarios, an IMT-2020 single mode micro power RRU can be used. Also, considering that the emergency communication system needs to avoid interference from the surrounding network in this scenario, external or integrated base stations can be used to effectively control the coverage of the CUAV emergency communication system. For some special scenarios, the CUAV emergency communication system needs to carry all the service capacity, or a multi-frequency and multi-mode micropower RRU with higher capacity can also be selected.
+
+### **I.3 Disaster scene with trapped people search and rescue**
+
+Untied CUAVs have more flexibility than mooring CUAVs, and they can provide quick communication support for vehicles or complex ground equipment, to ensure that trapped personnel can contact rescue personnel during the process of searching and rescuing trapped personnel.
+
+Inspection CUAVs can be used for emergency surveying and mapping. They send surveying and mapping information to CUAVs that carry base stations. This information is transferred to the satellite communication network, and then to the terrestrial cellular network. Finally, the ground control station gets the information. Rescue workers get the whole map view of the disaster place.
+
+Terminals of trapped people initiate registration requests including IMSI after obtaining a wireless signal. The mobile communication base station obtains their registration requests, then the CUAV gets its own location by GPS. After getting the registration requests, the CUAV sends CUAV's location information and the IMSI information to the satellite communication network and finally to the terrestrial cellular network. The ground control station obtains the CUAV's location information and the IMSI information at the same time, identifies user's identity information by IMSI information, and locates the user's target area from the CUAV's location information. Rescue work can be done more precisely.
+
+## Bibliography
+
+- [b-ITU-T F.749.10] Recommendation ITU-T F.749.10 (2019), *Requirements for communication services of civilian unmanned aerial vehicles.*
+- [b-ITU-T F.749.15] Recommendation ITU-T F.749.15 (2022), *Requirements for inspection and examination services using civilian unmanned aerial vehicles.*
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.751.0-202008-I_PDF-E/raw.md b/marked/F/T-REC-F.751.0-202008-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..b03a8e110d370297eead584a02422e7f7affdfc3
--- /dev/null
+++ b/marked/F/T-REC-F.751.0-202008-I_PDF-E/raw.md
@@ -0,0 +1,735 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.751.0**
+
+(08/2020)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Multimedia services
+
+# --- **Requirements for distributed ledger systems**
+
+Recommendation ITU-T F.751.0
+
+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 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 F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| <b>TELEGRAPH SERVICE</b>                                        |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| <b>MOBILE SERVICE</b>                                           |                    |
+| Mobile services and multdestination satellite services          | F.110–F.159        |
+| <b>TELEMATIC SERVICES</b>                                       |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| <b>MESSAGE HANDLING SERVICES</b>                                | F.400–F.499        |
+| <b>DIRECTORY SERVICES</b>                                       | F.500–F.549        |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | F.600–F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700–F.799</b> |
+| <b>ISDN SERVICES</b>                                            | F.800–F.849        |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | F.850–F.899        |
+| <b>ACCESSIBILITY AND HUMAN FACTORS</b>                          | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.751.0
+
+# Requirements for distributed ledger systems
+
+## Summary
+
+Recommendation ITU-T F.751.0 establishes basic and advanced requirements for distributed ledger systems.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.751.0  | 2020-08-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/14332">11.1002/1000/14332</a> |
+
+## Keywords
+
+Blockchain, consensus, decentralized ledger technology, non-repudiation, tamper-resistant.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....              | 1    |
+| 4 Abbreviations and acronyms .....                          | 2    |
+| 5 Conventions .....                                         | 3    |
+| 6 Overview.....                                             | 3    |
+| 7 Basic requirements for distributed ledger systems .....   | 3    |
+| 7.1 Decentralization.....                                   | 3    |
+| 7.2 Proof of ownership .....                                | 4    |
+| 7.3 Data validity .....                                     | 5    |
+| 7.4 Tamper-resistance.....                                  | 6    |
+| 7.5 Auditability.....                                       | 6    |
+| 7.6 Fairness.....                                           | 7    |
+| 7.7 Stability.....                                          | 7    |
+| 7.8 Governance.....                                         | 9    |
+| 8 Advanced requirements for distributed ledger systems..... | 9    |
+| 8.1 Access control .....                                    | 9    |
+| 8.2 Consensus .....                                         | 10   |
+| 8.3 Data storage .....                                      | 10   |
+| 8.4 Identity.....                                           | 11   |
+| 8.5 Interoperability .....                                  | 11   |
+| 8.6 Membership.....                                         | 12   |
+| 8.7 Openness.....                                           | 12   |
+| 8.8 Privacy protection.....                                 | 13   |
+| 8.9 Provenance .....                                        | 14   |
+| 8.10 Smart contract.....                                    | 14   |
+| 8.11 Token .....                                            | 15   |
+| 8.12 Cipher suites .....                                    | 16   |
+| 8.13 Utilities .....                                        | 16   |
+| Bibliography.....                                           | 18   |
+
+
+
+# Recommendation ITU-T F.751.0
+
+## Requirements for distributed ledger systems
+
+## 1 Scope
+
+This Recommendation establishes requirements for distributed ledger systems, covering:
+
+- a general overview;
+- basic requirements;
+- advanced 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.
+
+None.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 digital signature** [b-ITU-T X.800]: Data appended to, or a cryptographic transformation of a data unit that allows a recipient of the data unit to prove the source and integrity of the data unit and protect against forgery, e.g., by the recipient.
+
+**3.1.2 Internet of things (IoT)** [b-ITU-T Y.2060]: A global infrastructure for the information society, enabling advanced services by interconnecting (physical and virtual) things based on existing and evolving interoperable information and communication technologies.
+
+**3.1.3 private distributed ledger technology system** [b-ISO 22739]: DLT system that is accessible for use only to a limited group of DLT users.
+
+**3.1.4 public DLT; public distributed ledger system; public distributed ledger technology system** [b-ISO 22739]: DLT system which is accessible to the public for use.
+
+### 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 asset**: A representation of value. It can be a diamond, a unit of currency, items inside a shipping container, etc. An asset can be physical or virtual.
+
+**3.2.2 blockchain**: A type of distributed ledger that is composed of digitally recorded data arranged as a successively growing chain of blocks with each block cryptographically linked and hardened against tampering and revision.
+
+NOTE – Adapted from [b-ITU-T TS FG DLT D1.1].
+
+**3.2.3 consensus**: Agreement that a set of transactions is valid.
+
+NOTE – Originally published in [b-ITU-T TS FG DLT D1.1].
+
+- 3.2.4 consensus algorithm:** A set of rules that precisely establishes a sequence of operations to reach consensus.
+- 3.2.5 distributed ledger:** A type of ledger that is shared, replicated, and synchronized in a distributed and decentralized manner.  
+NOTE – Originally published in [b-ITU-T TS FG DLT D1.1].
+- 3.2.6 distributed ledger system:** A system that implements a distributed ledger.
+- 3.2.7 distributed ledger technology application; ledger application:** A client to a distributed ledger technology (DLT) system that is designed to help people perform an activity.
+- 3.2.8 entity:** Anything that has a separately identifiable existence (e.g., organization, person, group, smart contract or device). An entity uses distributed ledger technology to solve the problem of its business or information systems.  
+NOTE – Adapted from [b-ITU-T X.1215].
+- 3.2.9 entity address:** Identifier for one or more entities performing transactions or other actions in a blockchain or distributed ledger network.
+- 3.2.10 ledger:** Information store that keeps final and definitive (immutable) records of transactions.  
+NOTE – Originally published in [b-ITU-T TS FG DLT D1.1].
+- 3.2.11 mining:** A reward-seeking activity in some consensus mechanisms.
+- 3.2.12 node:** Device or process that participates in a distributed ledger network.  
+NOTE 1 – Nodes can store a complete or partial replica of the distributed ledger.  
+NOTE 2 – Originally published in [b-ITU-T TS FG DLT D1.1].
+- 3.2.13 P2P:** An instantiation of network architectures where all peers have equivalent authority and responsibility, differing completely from that of server and client system.  
+NOTE – Paraphrased from clause 1 of [b-ITU-T X.1161].
+- 3.2.14 permissioned distributed ledger system:** Distributed ledger system in which permissions are required to maintain and operate a node.  
+NOTE – Originally published in [b-ITU-T TS FG DLT D1.1].
+- 3.2.15 permissionless distributed ledger system:** Distributed ledger system where permissions are not required to maintain and operate a node.  
+NOTE – Originally published in [b-ITU-T TS FG DLT D1.1].
+- 3.2.16 smart contract:** Program written on the distributed ledger system that encodes the rules for specific types of distributed ledger system transactions in a way that can be validated, and triggered by specific conditions.  
+NOTE – Adapted from [b-ITU-T TS FG DLT D1.1].
+- 3.2.17 token:** A digital representation of value on a shared distributed ledger that is owned and secured using cryptography to ensure its authenticity and prevent modification or tampering without the owner's consent.  
+NOTE – Originally published in [b-ITU-T TS FG DLT D1.1].
+- 3.2.18 transaction:** An incident or an operation that leads to a change in the status of a ledger, such as adding a record or equivalent exchange based on currency.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+DDoS Distributed Denial of Service
+
+|     |                                 |
+|-----|---------------------------------|
+| DLT | Distributed Ledger Technology   |
+| DoS | Denial of Service               |
+| ID  | Identifier                      |
+| IoT | Internet of Things              |
+| P2P | Peer to Peer                    |
+| PoW | Proof of Work                   |
+| SPV | Simplified Payment Verification |
+| URL | Uniform Resource Locator        |
+
+## 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 or service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with this Recommendation.
+
+## 6 Overview
+
+Distributed ledger systems have no central administrator or centralized data storage. These systems form tamper-resistant, shared ledgers among distributed nodes [b-Zheng]. Besides the facilitation of the processing of transactions, distributed ledger systems enable the incorporation of data integrity and trust capabilities into applications.
+
+DLT can be integrated into multiple areas. The World Bank thinks that DLT could fundamentally change the financial sector, making it more efficient, resilient and reliable [b-Natarajan]. DLT also has the potential to transform various other sectors, e.g., manufacturing, clean energy, health care and the IoT. More and more public or commercial services are piloting DLT.
+
+DLT can be classified in two ways: public or private DLT; permissioned or permissionless DLT [b-Gramoli]. A public DLT has transaction records that are readable by anyone, while a private DLT limits the transaction records read access to some authorized groups. In a permissionless DLT, any computer can be a full functional node. In a permissioned DLT, only an authorized terminal can join the DLT network as a fully functional node.
+
+# 7 Basic requirements for distributed ledger systems
+
+This clause addresses basic requirements that apply to all distributed ledger systems, if not stated clearly otherwise.
+
+### 7.1 Decentralization
+
+Differing from many traditional systems, the operation of DLT relies on cooperation of multiple peer-to-peer (P2P) nodes. Each node maintains a partial or total local copy of the shared ledger, and validates the messages from others.
+
+DEC-001: A distributed ledger system is required to maintain a shared ledger.
+
+DEC-002: A distributed ledger system is required to identify each node on the network by a node identifier (ID).
+
+DEC-003: A distributed ledger system is required to implement an addressing system. Each entity gets its address from the addressing system. The address is then being utilized by transactions to identify the senders and receivers.
+
+DEC-004: A distributed ledger system node is required to be able to discover other nodes. Many technologies can be used for node discovery, such as bootstrapping, flooding or rumour mongering [b-Eugster].
+
+DEC-005: A distributed ledger system is required to adopt a P2P network as its underlying infrastructure. Each node in the network exchanges messages directly with all others instead of via a central gateway. A particular P2P protocol is required to maintain the P2P network structure. The P2P network is required to support:
+
+- data synchronization without connecting to a central server to get the ledger data;
+- maintenance of node information and tracking the status of the nodes.
+
+DEC-006: A distributed ledger system is required to send out broadcast messages. Broadcast messages are sent to all the other nodes in the DLT network.
+
+DEC-007: A distributed ledger system is required to provide mechanisms to distribute the shared ledger among its nodes. This requires the P2P architecture to allow large amounts of data to be transferred between nodes. To distribute the shared ledger, a common practice is to broadcast the transactions, then have the consensus algorithm determine the final state of the shared ledger.
+
+DEC-008: Any node of a distributed ledger system is required to be able to answer read-only transaction queries about the data they store. There is no need to forward a transaction to P2P network in this scenario.
+
+DEC-009: A distributed ledger system is recommended to support different node types, e.g., light, full and full archiving.
+
+DEC-010: A distributed ledger system can optionally support the execution of a transaction only if specific conditions are met. For example, a transaction must be executed within 24 h or a transaction dealing with more value than a defined threshold can be executed only after some days.
+
+### 7.2 Proof of ownership
+
+A distributed ledger is an information store that can be used to keep final and definitive (immutable) records of transactions. It keeps track of who owns an asset. In other words, a ledger records the transfer of assets from one owner to another. Assets may be physical or intangible. In DLT, any entity can be the owner of an asset. An entity can be a human, an organization, a smart contract, or a device. During their lifecycle, assets may be transferred multiple times and may be split or reorganized.
+
+RWO-001: A distributed ledger system is required to adopt public key cryptology in its addressing system. Assets on the distributed ledger system are associated with private keys, and public key cryptology ensures data integrity, authentication and non-repudiation when assets are transferred.
+
+RWO-002: A distributed ledger system is required to support transaction recording. Transactions are the fundamental activities that modify a shared ledger. Transactions may happen among multiple entities.
+
+RWO-003: A distributed ledger system is required to record the addresses involved in a transaction and the assets influenced. The basic transaction is from one sender to one receiver, i.e., one to one. For example, a transaction records that address A sends  $k$  tokens to address B.
+
+RWO-004: A distributed ledger system is required to have all transactions timestamped.
+
+RWO-005: Because transaction recording is distributed, to make the timestamp consistent and valid, a distributed ledger system is required to have all nodes with transaction recording rights time synchronized.
+
+RWO-006: A distributed ledger system is recommended to enable its transaction records to support supplementary information. For example, for a transaction in which A buys a house from B, the record contains not only the amount of tokens paid, but also the certificate of the house or the hash value of the certificate with the uniform resource locator (URL) of the certificate file.
+
+RWO-007: A distributed ledger system is required to have each transaction digitally signed by its authorized entity using its private key.
+
+RWO-008: A distributed ledger system is recommended to support multi-signature. If a transaction requires more than one entity to authorize, the usage of multi-signature is more compact than a collection of distinct signatures from all authorizers. Multi-signature also allows that  $m$  members of a group to authorize a transaction, although there are  $n$  members in total for the group, *i.e.*,  $m/n$  authorization.
+
+RWO-009: A distributed ledger system is required to support the storage of transactions. Multiple copies should be stored by at least all entities involved in a transaction.
+
+RWO-010: A distributed ledger system is required to support distributed ledger storage. Multiple copies are required to be stored.
+
+RWO-011: A distributed ledger system can optionally support functionalities that help users if they lose their private keys. In some use cases, such functionality should only be controlled by the user.
+
+RWO-012: A distributed ledger system can optionally support the specification of additional names for its addresses.
+
+RWO-013: A distributed ledger system can optionally support the possibility of segregating those who sign a transaction from those who publish it on the network.
+
+### 7.3 Data validity
+
+Each node operates to supervise all others in the DLT network because there are no trustable centralized nodes. Messages received from others require verification to confirm the validity of the information.
+
+DV-001: A distributed ledger system is required to provide mechanisms to validate transactions received from others.
+
+DV-002: A distributed ledger system is required to support:
+
+- examination of the transaction record to validate that it has not been tampered with;
+- examination of the address and signature of the sender to validate whether the sender is valid and authentic;
+- if a transaction involves token transfer, examination of the balance of the sender to validate that it has enough tokens to fulfil the transaction;
+- if the transaction involves the execution of a smart contract, execution of the specific function.
+
+DV-003: A distributed ledger system is required to provide mechanisms to validate the shared ledger, so that only valid transactions are recorded in it.
+
+DV-004: A distributed ledger system is required to support examination of the shared ledger:
+
+- to validate that it has not been tampered with;
+- to confirm that there are no suspicious transactions or accounts.
+
+DV-005: A distributed ledger system is recommended to adopt mechanisms to facilitate the validation of a shared ledger on storage-limited devices, such as the mobile phones, and to provide mechanisms to accelerate the validation. Simplified payment verification (SPV) is one such mechanism. SPV nodes do not have all transactions and do not download the full shared ledger. To verify that a transaction is included in a blockchain ledger, without having to download all the transactions in the block, SPV nodes use an authentication path, such as Merkle path.
+
+DV-006: A distributed ledger system is required to protect the system from fraud, such as:
+
+- transaction fraud, e.g., the entity sends a transaction that exceeds its payment capability;
+- erroneous response – a node returns an opposite value, e.g., the value of the execution result is 0, but the node returns 1.
+- fraud broadcast – a node without a ledger-recording privilege records and broadcasts it to other nodes.
+- fraudulent record – a node records and broadcasts a fraudulent transaction.
+
+### 7.4 Tamper-resistance
+
+Tamper-resistance is an important feature of the DLT that is favoured by the industry. Once data is loaded into a shared ledger, it requires extensive computational resources or massive collusion among nodes to modify it unnoticed by others, hence rendering it practically immutable. There is no difference whether the change is intentional or accidental, malicious or benign.
+
+TAM-001: A distributed ledger system is required to be tamper-resistant. Once the transaction record enters the shared ledger, it is hard to change it. If it does change, the process of implementing the change will inevitably be recorded and easily found, unless all nodes agree.
+
+TAM-002: A distributed ledger system is required to implement mechanisms to authenticate the addresses of a transaction.
+
+TAM-003: A distributed ledger system is required to have mechanisms to authenticate each node in the network.
+
+TAM-004: A distributed ledger system is required to implement algorithms to protect the integrity of the transactions and the ledger distribution messages.
+
+TAM-005: A distributed ledger system is required to implement mechanisms to ensure that data stored in the shared ledger cannot be repudiated.
+
+### 7.5 Auditability
+
+By sharing the data in the shared ledger, DLT facilitates audit processing. However, the supports of data privacy in public DLT and private DLT are different. A public DLT allows all data in a shared ledger to be audited by anyone, whereas a private DLT only allows those who are authorized to access a transaction. All transaction-related entities are authorized by default. To conform to regulations on data privacy makes audit processing more complicated, a public DLT has to either save information off-chain or save information in the shared ledger, but encrypted.
+
+AUD-001: A distributed ledger system is required to allow all transaction-related entities to access their transaction information stored in a shared ledger.
+
+AUD-002: A distributed ledger system is required to have all transaction records in the ledger signed by the entity or entities that initiate(s) the transaction.
+
+AUD-003: A distributed ledger system is required to store information that can help audit processing in the log managed by nodes and the enable the provision of such a log to the auditor when it is needed.
+
+### 7.6 Fairness
+
+Fairness between nodes is crucial for achieving effective multi-party supervision and ensuring that data cannot be falsified. The roles of nodes in the DLT network may vary due to differences in bandwidth, storage, computing power or shares possessed in the DLT network. For example, some nodes may only have verification capabilities, and others may record ledgers. A distributed ledger system is required to guarantee that the rules to assign rights are consistent and the possibility for a node to get a ledger-recording privilege is random. In other words, nodes of the same ability should have a statistically identical opportunity in the network. A distributed ledger system must avoid giving too many ledger-recording rights to a node or a group of nodes. Such unfair treatment can easily lead to security problems.
+
+FAI-001: A distributed ledger system is required to fairly assign rights to nodes, i.e., nodes with similar capabilities are given similar rights. Rights in the DLT network include governance participation, ledger recording and transaction verification.
+
+FAI-002: A distributed ledger system is recommended to choose the ledger recording node, e.g., randomly or in turns, from all nodes with a ledger-recording privilege.
+
+FAI-003: A distributed ledger system is required to support node management. Node management determines:
+
+- which server can join the DLT network as a node;
+- the rights of the node in the network.
+
+FAI-004: A distributed ledger system is required to support either permissioned or permissionless DLT deployment.
+
+FAI-005: A distributed ledger system is recommended to support nodes that cannot cooperate with the consensus, but can store the shared ledger and verify transactions.
+
+FAI-006: A distributed ledger system is recommended to support the configuration of permissioned nodes to participate in the consensus algorithm and permissionless nodes to receive and verify transactions without participating in the consensus algorithm.
+
+FAI-007: A distributed ledger system can optionally assign special rights only to nodes that have certain properties, e.g., a minimum number of tokens.
+
+### 7.7 Stability
+
+The distributed nature of the DLT makes it face stability challenges. Each node in a DLT may have the capability to record transactions, but which node is eventually selected is a result of the consensus algorithm. There are many factors that affect the stability of a DLT network, e.g., malicious nodes, network attacks, network failures, multipaths in networks, system upgrades or patches and governance disputes. The design of a distributed ledger system is required to take these factors into consideration and enables the distributed ledger to regain stable service through adaptive processing of the system.
+
+However, special interventional procedures are sometimes required, which often result in soft or hard forks. In some cases, it can be solved by a soft fork, i.e., a gradual upgrade of all nodes. At this point, an upgraded node can be compatible with a non-upgraded node on the same ledger.
+
+A hard fork is more serious situation, all nodes need to be upgraded synchronously to make the system resume stable operation. At this point, a node that has not been upgraded can no longer process the ledger information sent by an upgraded node. Note that due to the decentralization of nodes, it is almost impossible to upgrade them all simultaneously after the distributed ledger system has formed a certain scale. After the agreed upgrade time, there will be two parallel shared ledgers in the DLT network, one maintained by the upgraded nodes and another maintained by the un-upgraded nodes, which means that the shared ledger is forked.
+
+STA-001: A distributed ledger system is required to adopt a consensus algorithm. In this Recommendation, consensus is attained when all nodes in the network make unanimous agreement on a transaction, which records who sends assets to whom.
+
+STA-002: A distributed ledger system is required to run stably on heterogeneous networks.
+
+STA-003: A distributed ledger system is required to reach a correct consensus with high probability in limited time.
+
+STA-004: A distributed ledger system is required to reach a correct consensus even if there are malfunctioning or malicious nodes, providing that the number of malfunctioning nodes does not exceed the consensus threshold, which is the limitation on the number of malfunctioning or malicious nodes that the consensus algorithm can tolerate. The consensus threshold is determined mainly by the consensus algorithm. For example, the consensus threshold of proof of work (PoW) is 50% in many implementations. The consensus threshold is an important performance index of a distributed ledger system.
+
+STA-005: A distributed ledger system is required to be able to resolve a fork created due to the propagation of different transactions in the network. As more than one node may produce valid proofs almost simultaneously, and nodes producing the proofs may have different transaction records, multiple versions of ledgers will be generated in the distributed ledger system. Resolution of such an inconsistency is recommended by accepting one of the records and eliminating others according to predefined rules (e.g., the longest fork rule).
+
+STA-006: A distributed ledger system is required to defend against double spending, which is a failure mode of the DLT when it is possible to spend a single digital token twice. For example, an attacker who owns 10 tokens wants to pay the same 10 tokens to victims A and B. First, the attacker pays 10 tokens to A, which is recorded in the ledger and admitted by other nodes. Second, the attacker makes a transaction to B of the same 10 tokens that had been paid to A. Unlike physical token money, such as coins, electronic files can be duplicated, and hence the act of spending a digital coin does not remove its data from the ownership of the original holder. For this double spending, the network would have the ability to reject the second transaction and the second transaction is not recorded into the ledger.
+
+STA-007: A distributed ledger system is required to prevent Sybil attacks and dismiss masquerading hostile entities. A Sybil attack in DLT is one in which consensus processing is subverted by forging identities in P2P networks, such as an attacker disguised as:
+
+- a legitimate node to send a dishonest transaction;
+- multiple nodes to break consensus in the distributed ledger system.
+
+STA-008: For a permissionless distributed ledger system, the system is required to deploy an incentive mechanism, which allows a selected node to record that a shared ledger has been rewarded by an amount of tokens. The incentive encourages nodes to take active part in the algorithm and stabilizes the networks. Transaction fees are another type of incentive mechanism. For each transaction, a small amount of transaction fees is given to the network and shared by the rest of nodes.
+
+STA-009: A distributed ledger system is required to automatically recover from a malicious node attack, network attack, node failure or network failure to smooth operation.
+
+STA-010: A distributed ledger system is required to have the ability to initiate soft forks or hard forks. The system is required to have the ability to upgrade all nodes to the new system at the agreed time to initiate hard forks.
+
+NOTE – An upgrade of a distributed ledger node can only be done by its administrator. The centralized upgrade service of the traditional centralized system is not suitable for the distributed ledger system.
+
+### 7.8 Governance
+
+Given that a distributed ledger system is inherently distributed, with multiple nodes typically owned and operated by different owners, the requirements of usual governance are mainly about how to govern the system as a whole and keep the system executing the tasks.
+
+GOV-001: A distributed ledger system is recommended to adopt appropriate governance methods to ensure the continuity of its lifecycle.
+
+GOV-002: A distributed ledger system is required to adopt appropriate governance methods to ensure that the system is able to resolve disputes in an appropriate manner.
+
+GOV-003: A distributed ledger system is required to have its rules of network governance be open and clear. If it is necessary to amend the governance rules, their revision process should be ensured to be in accordance with the original agreement.
+
+GOV-004: A distributed ledger system is required to adopt appropriate governance practices to ensure that governance supports decentralization, tamper resistance, fairness and stability.
+
+GOV-005: A distributed ledger system is recommended to adopt appropriate governance methods to support changes in the platform.
+
+## 8 Advanced requirements for distributed ledger systems
+
+This clause defines advanced requirements for distributed ledger systems. These advanced functional requirements often make the design of the application more convenient and secure. However, because of the tighter coupling with the application, it is possible that these advanced requirements are not supported by all systems.
+
+### 8.1 Access control
+
+Access control is a requirement for DLT in most commercial enterprise services and in financial scenarios. Access control involves the rights to read the data in the shared ledger and to create new data.
+
+Implementing access control on a public DLT by encryption is not recommended. Storing private information off-chain and storing only hashes on-chain can be a way to appropriately handle private data on a public DLT. A private DLT is able to carry a more comprehensive access control by utilizing capabilities such as entity ID, blacklist or whitelist.
+
+ACC-001: A distributed ledger system can optionally protect the accessing of records in a shared ledger in some use cases.
+
+ACC-002: A distributed ledger system is required to use privacy enhancing technologies for the handling of private data. For example, if a social ID is stored in a shared ledger, storage of the ID as plaintext should be avoided.
+
+ACC-003: A distributed ledger system can optionally store only the integrity checksum (of the data) in the shared ledger and implement access control off the shared ledger.
+
+ACC-004: A distributed ledger system can optionally support the limitation of data access from the time perspective.
+
+ACC-005: If access control is implemented in the system, the system can optionally record all successful or failed data accesses.
+
+ACC-006: A distributed ledger system is recommended to be able to control who can create data in the shared ledger.
+
+### 8.2 Consensus
+
+A consensus algorithm is a set of rules that precisely defines a sequence of operations to reach consensus. Lots of functional or performance parameters are determined by consensus algorithms, including the fault tolerance threshold, the maximum number of transactions processed per second, the ledger recording period, and the transaction confirmation delay.
+
+CON-001: The distributed ledger system is required to determine a threshold of the number of nodes that need to agree in order to consider a transaction valid in the whole network. After a transaction is considered valid, all remaining nodes need to agree that the transaction is valid in order to continue with the same view of the shared ledger.
+
+CON-002: A distributed ledger system is required to support at least one type of crash fault tolerant consensus algorithm.
+
+CON-003: A distributed ledger system is recommended to support at least one type of Byzantine consensus algorithm.
+
+CON-004: A distributed ledger system is recommended to support the user selection of the consensus algorithm.
+
+CON-005: A distributed ledger system is recommended to have its consensus algorithm able to defend against denial of service (DoS) or distributed denial of service (DDoS) attacks.
+
+CON-006: A distributed ledger system is recommended to have its consensus algorithm able to defend against eclipse attacks, wherein an adversary controls a sufficient number of IP addresses to monopolize all connections between victim nodes and the DLT network, and exploits the victim nodes to launch other attacks, such as double spending.
+
+CON-007: If mining is supported, the distributed ledger system is recommended to have its consensus algorithm able to defend against selfish mining, wherein a group of colluding nodes hide newly generated records instead of broadcasting them instantly, and publish the records strategically. Selfish mining enables nodes to win more rewards than deserved, so rational nodes will prefer to join the colluding group. In this way, the colluding group will increase in size until it reaches the fault tolerance threshold.
+
+CON-008: A distributed ledger system is recommended to support changes in the consensus algorithm configuration. For example, how difficult it is to solve a puzzle in a PoW consensus algorithm.
+
+CON-009: A distributed ledger system is recommended to offer a quantum-resistant consensus algorithm.
+
+### 8.3 Data storage
+
+Because of the tamper resistant nature of DLT, many applications store its data on ledger. The data may be in various formats, such as images, audio, video or text. On-ledger data occupies  $N$  times the storage than the off-ledger case, where  $N$  is the number of copies of the data on the ledger.
+
+A data digest can be used to save ledger storage space while keep the data tamper resistant. When using a data digest, the hash digest of the data is stored on ledger, where the copy of the data is stored off ledger. One-way IDs can be used to point to data stored off ledger, to facilitate data access.
+
+DS-001: A distributed ledger system is recommended to support the storage of multiple data types, such as a video or audio clips, the name of the entity or the audit log for the transaction.
+
+DS-002: A distributed ledger system is recommended to store the hash digest of a file, and to store the file off ledger.
+
+DS-003: To avoid leakage of information, if one-way IDs are used to access off ledger files, the distributed ledger system is required to make the one-way ID independent of the data content.
+
+DS-004: A distributed ledger system can optionally store the transactions in blocks. Each block may contain a header with metadata and a body with a set of transactions.
+
+### 8.4 Identity
+
+A distributed ledger system promotes the protection and utilization of identity, and achieves the protection of identity information in terms of confidentiality, integrity and availability. Achieving these protections requires a combination of the following factors:
+
+- a combination of technical and non-technical means;
+- data processing across DLT and non-DLT systems;
+- security and encryption processing requirements;
+- access management through API and storage architecture.
+
+A distributed ledger system is the basis for decentralized identification. Trust is no longer rooted in any single entity, but is based on information sharing and mutual supervision in the network. This trust model allows non-trusted stakeholders to conclude transactions in the system, and the use of encryption and signatures helps to verify the provenance and hence facilitates audits. Decentralized identification can be applied to natural people, legal entities, things and processes.
+
+IDE-001: A distributed ledger system can optionally ensure that any certification information is recorded and stored in a shared ledger. The certification information includes, but is not limited to, copyright information, insurance information and enterprise qualification.
+
+IDE-002: A distributed ledger system can optionally provide a mechanism to validate the authenticity of certification information. Any certification information must be validated as authentic before being recorded and stored in a shared ledger.
+
+IDE-003: A distributed ledger system can optionally provide an access mechanism to ensure that any person or organization that wants to query the certification is authorized by the information owner.
+
+### 8.5 Interoperability
+
+Multiple DLT systems may run in parallel in the future, although the original DLT designer may wish to serve all the requirements by a single DLT system. If multiple DLTs are inevitable, how do these DLT systems interoperate?
+
+Interoperable DLT opens up a comprehensive service that moves assets from one platform to another, supporting atomic exchange across DLTs, making it easy to access information in other DLT networks (e.g., a link of "identity DLT" with a payment DLT network). Interoperability can also be achieved by a third party without any additional effort by the original DLT protocol.
+
+Interoperable DLT can be used in several use cases. Examples follow.
+
+- Transfer of assets across distributed ledger systems. For example, asset A is safely transferred from the parent ledger X system to the Y system, which can go through a series of transactions in the Y system, e.g., using the asset as collateral. The entire process should ensure that the relevant assets in the Y system are supported for back transfer to the mother ledger X system.
+- Atomic swap across distributed ledger system. Atomic swap consists of two asset exchanges and needs to ensure that they either succeed or fail. The atomic swap across the distributed ledger system allows user X to transfer digital asset A to user Y in exchange for Y to transfer digital asset B to user X. (A and B are maintained by different DLT systems. Both X and Y have accounts in A and B.) Cross-chain atomic exchange provides secure transaction processing for mutually untrusted parties.
+
+- Oracle across distributed ledger system. For example, a smart contract running on an X system will only perform certain operations if it receives valid evidence from the oracle address on another Y system.
+- Cross-DLT asset collateral: locks asset A on the X system, while the lock condition depends on the activity on the Y system. Many scenarios in a multi-DLT environment will require such cross-chain processing capabilities, such as liens, collateral for financial derivatives, bankruptcy recovery, court orders, and various use cases involving margin.
+- Smart contracts across distributed ledger system. For example, paying dividends to holders of assets registered on the Y system in the X system.
+
+INT-001: A distributed ledger system can optionally support interoperability with other distributed ledger systems.
+
+INT-002: A distributed ledger system can optionally support the transfer of assets to another distributed ledger system.
+
+INT-003: A distributed ledger system can optionally support atomic exchanges across distributed ledger systems.
+
+INT-004: A distributed ledger system can optionally support oracle across distributed ledger systems.
+
+INT-005: A distributed ledger system can optionally support cross-DLT asset collateral.
+
+INT-006: A distributed ledger system can optionally support smart contracts across DLT.
+
+### 8.6 Membership
+
+A distributed ledger system is a distributed network, and the public DLT treats the separation of the private key from the identity as a method to protect user privacy. Therefore, the public chain seldom provides user management, i.e., does not support the query of a user's address, and cannot verify the public key a user provided. However, an application exists that supports the disclosure the owner of some addresses. Such information is mainly collected from public information, e.g., the holder proactively claiming to hold certain addresses, or some financing activities or transactions reveal the ownership of some addresses.
+
+However, membership management is a requirement for most private or permissioned distributed ledger systems. The membership service can be implemented either distributed or centralized, i.e., on or off ledger, respectively. No matter how the membership service is implemented, the membership service means that important identification information is stored in the system; hence security and privacy protection is required.
+
+MEM-001: A public distributed ledger system can optionally have applications to serve the query of user/node information. The applications have to collect user or node information using public methods.
+
+MEM-002: A private or permissioned distributed ledger system is required to build a membership management service, to manage either the user information or the node information.
+
+MEM-003: If membership management is supported, the distributed ledger system is required to adopt appropriate methods to protect the security and privacy of the member's identification data.
+
+### 8.7 Openness
+
+Early distributed ledger systems were public DLTs, which benefit data disclosure and audit processing with open data access. In most enterprise services, government services, and financial services, the private DLTs are used. A viewing account needed to be authorized for audit by others.
+
+OPE-001: A public distributed ledger system is required to provide open access to the transaction records to anyone.
+
+OPE-002: A private distributed ledger system is required to limit the transaction records read access to the (predefined) particular group.
+
+OPE-003: To improve the stability and security, a permissioned distributed ledger system is recommended to deploy a node monitoring mechanism to monitor the bandwidth, CPU, storage, etc.
+
+OPE-004: A permissioned distributed ledger system can optionally implement censoring mechanisms, such as:
+
+- removal of a specific node from the distributed ledger system, i.e., so that the system neither processes messages received from nor sends messages to the node;
+- locking of a specific address so that it cannot make any new transactions;
+- monitoring of all transactions of a specific address by dedicated censors.
+
+OPE-005: A permissionless distributed ledger system can optionally implement some censoring mechanisms. One example is a decentralized decision about a forward transaction coming from specific nodes to other P2P nodes.
+
+### 8.8 Privacy protection
+
+For the public DLT and the private DLT, privacy protection has different meanings and implementations.
+
+For public DLT, anyone can access the transaction record in the ledger, although the transaction record itself is a very important private message. In order to protect privacy, most public distributed ledger systems anonymously process transaction records, i.e., the transaction record contains only signatures and addresses, and the address is not bound to a person's identity. Research has proved that this privacy protection method is not reliable, and a tracker can gradually confirm the holder of the transaction address through various means, such as address tracing and network tracing. To address this problem, many privacy transaction techniques have been introduced into public DLT, such as zero-knowledge proof, homomorphic encryption, ring signature and CoinJoin.
+
+For private DLT, privacy protection is mainly to prevent unauthorized access. Although the privacy protection methods in the public distributed ledger systems in the previous paragraph can still be used, having access control to protect privacy is a more direct and reliable solution. Besides the transaction records, there may have been user identification information in the ledger, the distributed ledger system is required to provide effective protection for this identification information.
+
+PRI-001: A distributed ledger system is recommended to protect the accessing of sensitive information on the shared ledger. Only those allowed by the owner of the data can access it.
+
+PRI-002: A distributed ledger system can optionally adopt change addresses schemes, to protect the privacy of an entity in transaction. With changed addresses, a new key pair (and thus a new address) can be used for each transaction.
+
+PRI-003: A distributed ledger system can optionally implement zero-knowledge proof mechanisms to protect privacy. Zero-knowledge proof is a method by which one party (the prover) can demonstrate to another party (the verifier) that a given statement is true, without conveying any information apart from the fact that the statement is indeed true.
+
+PRI-004: A distributed ledger system can optionally implement ring signature mechanisms to protect privacy. A ring signature is a type of digital signature that can be performed by any member of a group of users that have keys.
+
+PRI-005: A distributed ledger system can optionally implement CoinJoin mechanisms [b-Zheng] to protect privacy. CoinJoin makes a joint transaction instead of sending out several single transactions, i.e., when one wants to make a payment, find someone else who also wants to make a payment and make a joint transaction together.
+
+PRI-006: A distributed ledger system can optionally implement homomorphic encryption mechanisms to protect privacy. Homomorphic encryption is a form of encryption that allows computations to be carried out on cipher text, thus generating an encrypted result which, when decrypted, matches the result of operations performed on the plaintext.
+
+PRI-007: For a private distributed ledger system, the system is required to provide effective protection for any identification information stored on a ledger.
+
+### 8.9 Provenance
+
+Provenance is evidence of the origin and sequence of transactions about assets of interest. It is the ability to track the entire lifecycle of an asset from its creation. Different distributed ledger systems have different requirements for provenance. On the one hand, the privacy trading system keeps provenance confidential; on the other, the supply chain management system wants all transactions related to the asset to be maintained in the tamper resistant ledger, enabling it to be traced back to the source of any asset, and to prove the source of the asset.
+
+PRO-001: A distributed ledger system can optionally support provenance, i.e., support track the entire lifecycle of an asset from its creation.
+
+### 8.10 Smart contract
+
+A smart contract is a software program written on the distributed ledger system which encodes the rules for specific types of distributed ledger system transactions in a way that can be validated, and triggered by specific conditions. Based on smart contracts, different decentralized applications have been built. While support for smart contracts is an important feature of the distributed ledger system, there are different conceptions and implementations of them:
+
+- Global addressed. Each smart contract is identified by an address on the distributed ledger system. The application calls the function defined by the smart contract by sending a transaction to the smart contract address. The execution results are stored on the system. In this case, each smart contract address has a creator or owner. All nodes with ledger record or verification rights execute smart contracts. Since the ledger record itself requires a lot of computational processing, smart contracts need to avoid large storage requirements and avoid complex processing.
+- Node addressed. The installation of programs on dedicated nodes that can be executed by addressing function calls of these programs using the node address. Since the execution of smart contracts occurs primarily at dedicated nodes, it can use almost any resource on the local node.
+
+SC-001: A distributed ledger system can optionally support smart contracts and decentralized applications.
+
+SC-002: If smart contracts are supported, the distributed ledger system is required to provide mechanisms to automate the lifecycle of smart contracts.
+
+SC-003: If smart contracts are supported, the distributed ledger system is recommended to provide mechanisms to automate the definition of different roles to interact with the smart contracts.
+
+SC-004: If smart contracts are supported, the distributed ledger system is required to provide mechanisms to protect against attacks that take advantage of its smart contract capability.
+
+SC-005: If smart contracts are supported, the distributed ledger system can optionally support the running of a decentralized application over it.
+
+SC-006: If smart contracts are supported, the distributed ledger system can optionally support the running of multiple applications over it concurrently.
+
+SC-007: If smart contracts are supported, the distributed ledger system can optionally support the storage of data of an overlay application in the shared ledger.
+
+SC-008: To avoid incorrect automatic processing, a distributed ledger system can optionally have the validation of a transaction to check whether the address of the receiver is valid.
+
+SC-009: If global-addressed smart contracts are supported, the distributed ledger system is required to deploy mechanisms that protect the resources on ledger being abused. The resources may be the storage space on ledger or the computational power of the nodes, etc.
+
+SC-010: If global-addressed smart contracts are supported, the distributed ledger system can optionally store the global state data.
+
+SC-011: If global-addressed smart contracts are supported, the distributed ledger system is required to adopt mechanisms to limit the number and time of execution of smart contracts to guarantee the system stability.
+
+SC-012: If global-addressed smart contracts are supported, the distributed ledger system is required to adopt mechanisms to direct data-intense applications to store and retrieve their data off-ledger to prevent a DoS attack.
+
+SC-013: If smart contracts are supported, the distributed ledger system can optionally support the possibility of using multiple programming languages.
+
+SC-014: If smart contracts are supported, the distributed ledger system can optionally support a Turing-complete programming language.
+
+SC-015: If smart contracts are supported, the distributed ledger system can optionally support the possibility of emitting events to sign specific states.
+
+SC-016: If smart contracts are supported, the distributed ledger system can optionally support a link between the programming language code and a natural human language.
+
+SC-017: If smart contracts are supported, the distributed ledger system can optionally support a mechanism to help to upgrade the contracts used in an application.
+
+### 8.11 Token
+
+A token is a digital representation of value on a shared distributed ledger that is owned and secured using cryptography to ensure its authenticity and prevent modification or tampering without the owner's consent. Smart contracts provide an autonomous solution for supporting the issuance, trading, and destruction of tokens, although they can also be recorded directly in ledger transaction records. The technology to support tokens through smart contracts has experienced rapid improvements. Initially only able to issue fungible tokens, now extended to support tokens such as non-fungible and security. A non-fungible token corresponds to a unique item that is physically indivisible, such as a gem. The security token needs to meet related regulatory requirements for a securities register and trading in various countries. No matter how the tokens are implemented, on a distributed ledger system, tokens are associated with private keys. There are some terms with similar meanings to token in the DLT industry, such as crypto asset, cryptocurrency and virtual coin.
+
+TOK-001: A distributed ledger system is recommended to support the use of tokens that are associated with private keys or smart contracts.
+
+TOK-002: If the use of a token is supported, the distributed ledger system is required to support token issuance, token transfer, token withdrawal, token settlement and clearance, token balance enquiry.
+
+TOK-003: If the use of a token is supported, the distributed ledger system is required to protect the security of token processing, such as token issuance, token transfer, token withdrawal, token settlement and clearance.
+
+TOK-004: If the use of a token is supported, the distributed ledger system is recommended to ensure the appropriate level of privacy of token owners.
+
+TOK-005: If the use of a token is supported, the distributed ledger system is recommended to support the function of the token and its value generation method.
+
+### 8.12 Cipher suites
+
+Cipher suites are used in many functions in a DLT system, including addressing generation, consensus algorithm and data storage. Cipher suites include at least asymmetric cryptography and a hash function.
+
+CIP-001: A distributed ledger system is required to have the ability to provide cipher suites with appropriate security level, e.g., quantum-resistant, to ensure the functionalities and privacy of the platform.
+
+CIP-002: A distributed ledger system is recommended to support the user selection of cipher suites.
+
+CIP-003: If smart contracts are supported, a distributed ledger system is recommended to offer native support of asymmetric function and a hash function in the programming languages used to develop these smart contracts.
+
+### 8.13 Utilities
+
+To make a distributed ledger system easy to use for system developers, maintainers and users, there are various utilities requirements, such as complex transaction support, blockchain browsers, wallets, network monitoring tools, node self-test tools, smart contract debugging tools and test networks.
+
+EOU-001: A distributed ledger system is recommended to provide a shared ledger browser that allows users to query transaction details for a specified transaction or address, or to track the origin of a given asset.
+
+EOU-002: If used for asset management, a distributed ledger system is recommended to provide a wallet application to facilitate user access to account balances, perform transfers, and track the progress of operations.
+
+EOU-003: A distributed ledger system can optionally support one to multiple transactions. For example, a transaction records that entity A sends  $k$ ,  $l$ ,  $m$  tokens, respectively, to entities B, C, D.
+
+EOU-004: A distributed ledger system can optionally support multiple to multiple transactions. For example, a transaction records that entity A and B spends  $k$  and  $l$  tokens respectively, and entity C, D, E earns  $m$ ,  $n$ ,  $o$  tokens, respectively. Note that in this example,  $k + l$  must equal  $m + n + o$ .
+
+EOU-005: A distributed ledger system can optionally provide an application interface (API) to third party developers.
+
+EOU-006: If APIs are provided, the distributed ledger system is required to ensure the security and privacy of API processing.
+
+EOU-007: A distributed ledger system can optionally monitor the performance of nodes. Abnormal nodes will be handled in time to maintain the stability and security of the system.
+
+EOU-008: A distributed ledger system can optionally monitor network status, such as the number of pending transactions, the number of active nodes, node addresses, geographic distribution, bandwidth and processing capabilities. For DLT using the PoW consensus, the total hashing power of the network and the change in the hashing power can optionally be also monitored.
+
+EOU-009: A distributed ledger system can optionally monitor usage, such as the total number of transactions, total transaction amount, and total data records, in a given time period.
+
+EOU-010: A distributed ledger system can optionally monitor user volume such as the number of new users per day, the number of active users per day, the number of independent address visits per day, and changes in the foregoing information.
+
+EOU-011: A distributed ledger system can optionally provide accessibility to system upgrades. Since the DLT is based on a distributed network, the upgrade of the system on each node must be performed by the node administrator. The DLT system can construct a message channel for all node administrators, through which the system update notification is pushed.
+
+EOU-012: A distributed ledger system can optionally provide the test tools and test networks to facilitate application development based on the system. Although some of the systems are open source, the appropriate test tools and test networks can effectively reduce the developer's time and effort.
+
+## Bibliography
+
+- [b-ITU-T X.800] Recommendation ITU-T X.800 (1991), *Security architecture for Open Systems Interconnection for CCITT applications*.
+- [b-ITU-T X.1161] Recommendation ITU-T X.1161 (2008), *Framework for secure peer-to-peer communications*.
+- [b-ITU-T X.1215] Recommendation ITU-T X.1161 (2019), *Use cases for structured threat information expression*.
+- [b-ITU-T Y.2060] Recommendation ITU-T Y.4000/Y.2060 (2012), *Overview of the Internet of things*.
+- [b-ITU-T TS FG DLT D1.1] Technical Specification ITU-T FG DLT D1.1 (2019), *Distributed ledger technology terms and definitions*.
+- [b-ISO 22739] ISO 22739:2020, *Blockchain and distributed ledger technologies – Vocabulary*.
+- [b-Eugster] Eugster, P. T., Guerraoui, R., Handurukande, S. B., Kouznetsov, P., Kermarrec, A. M. (2003). Lightweight probabilistic broadcast. *ACM T. Comput. Syst.*, **21**(4), pp. 341-374. DOI: 10.1145/945506.945507
+- [b-Gramoli] Gramoli, V., Staples, M. (2018). Blockchain standard: Can we reach consensus? *IEEE Commun. Standards Mag.* **2**, pp. 16-21. DOI: 10.1109/MCOMSTD.2018.1800022.
+- [b-Natarajan] Natarajan, H., Krause, S., Gradstein, H. (2017). *Distributed ledger technology (DLT) and blockchain*, FinTech Note; No. 1. Washington, DC: World Bank. 60 pp. Available [viewed 2020-10-06] at: <https://openknowledge.worldbank.org/bitstream/handle/10986/29053/WP-PUBLIC-Distributed-Ledger-Technology-and-Blockchain-Fintech-Notes.pdf?sequence=1&isAllowed=y>
+- [b-Zheng] Zheng, Z., Xie, S., Dai, H., Chen, X., Wang, H. (2017). An overview of blockchain technology: Architecture, consensus, and future trends. In: *2017 IEEE International Congress on Big Data (BigData Congress)*, pp. 557-564. New York, NY: IEEE.
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.751.16-202406-I_PDF-E/raw.md b/marked/F/T-REC-F.751.16-202406-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..059cff08f3abd5cec53382b659ab44beca0c6289
--- /dev/null
+++ b/marked/F/T-REC-F.751.16-202406-I_PDF-E/raw.md
@@ -0,0 +1,438 @@
+
+
+# Recommendation **ITU-T F.751.16 (06/2024)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+---
+
+## **Reference framework for distributed ledger technology (DLT) management service platforms**
+
+![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg)
+
+The logo of the International Telecommunication Union (ITU), featuring the letters 'ITU' in blue inside a circular emblem with a globe and network lines.
+
+ITU logo
+
+## ITU-T F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.751.16
+
+# Reference framework for distributed ledger technology (DLT) management service platforms
+
+## Summary
+
+Recommendation ITU-T F.751.16 specifies the reference framework for distributed ledger technology management service platforms (DLT-MSP). The framework includes the resource layer, distributed ledger technology (DLT) layer, management layer, business layer, application layer, and security layer. Additionally in the framework, it provides functionalities for the DLT layer, management layer and business layer. This Recommendation can be used as a guideline for DLT-MSP development and assessment.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.751.16 | 2024-06-13 | 16          | 11.1002/1000/15921 |
+
+## Keywords
+
+DLT, DLT-MSP, management service platform, reference framework, technical requirement.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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..... | 2 |
+| 4   | Abbreviations and acronyms .....          | 2 |
+| 5   | Conventions .....                         | 2 |
+| 6   | Reference framework of DLT-MSP .....      | 2 |
+| 6.1 | Resource layer .....                      | 3 |
+| 6.2 | DLT layer .....                           | 3 |
+| 6.3 | Management layer .....                    | 3 |
+| 6.4 | Business layer.....                       | 4 |
+| 6.5 | Application layer .....                   | 4 |
+| 6.6 | Security layer.....                       | 4 |
+| 7   | DLT layer functionality .....             | 4 |
+| 7.1 | Cryptographic algorithm .....             | 4 |
+| 7.2 | Consensus mechanisms .....                | 4 |
+| 7.3 | P2P network.....                          | 4 |
+| 7.4 | Smart contracts .....                     | 5 |
+| 7.5 | Data storage .....                        | 5 |
+| 8   | Management layer functionality .....      | 5 |
+| 8.1 | User management .....                     | 5 |
+| 8.2 | Node management .....                     | 5 |
+| 8.3 | DLT management.....                       | 6 |
+| 8.4 | Smart contract management .....           | 6 |
+| 8.5 | Log management .....                      | 6 |
+| 9   | Business layer functionality.....         | 7 |
+| 9.1 | User key management .....                 | 7 |
+| 9.2 | Interface management .....                | 7 |
+| 9.3 | Browser.....                              | 8 |
+| 9.4 | Contract templates .....                  | 8 |
+|     | Bibliography.....                         | 9 |
+
+
+
+# Recommendation ITU-T F.751.16
+
+## Reference framework for distributed ledger technology (DLT) management service platforms
+
+# 1 Scope
+
+This Recommendation specifies the reference framework for distributed ledger technology management service platform (DLT-MSP). Additionally, in the framework it provides functionalities for the distributed ledger technology (DLT) layer, management layer and business layer.
+
+This Recommendation can be used for DLT-MSP development and assessment.
+
+# 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.751.0] Recommendation ITU-T F.751.0 (2020), *Requirements for distributed ledger system*.
+
+# 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 distributed ledger** [ITU-T F.751.0]: A type of ledger that is shared, replicated, and synchronized in a distributed and decentralized manner.
+
+**3.1.2 peer-to-peer network** [b-ITU-T F.751.7]: A computer network comprised of nodes with equal control and operation capabilities.
+
+**3.1.3 consensus** [ITU-T F.751.0]: Rules and procedures by which consensus among DLT nodes is reached.
+
+**3.1.4 smart contract** [ITU-T F.751.0]: A program written on a distributed ledger system which encodes the rules for specific types of distributed ledger system transactions in a way that can be validated, and triggered by specific conditions.
+
+**3.1.5 entity** [ITU-T F.751.0]: Anything that has a separately identifiable existence (e.g., organization, person, group, smart contract or device). An entity uses distributed ledger technology to solve the problem of its business or information systems.
+
+**3.1.6 transaction** [ITU-T F.751.0]: An incident or an operation that leads to a change in the status of the ledger changed, such as adding a record to the ledger or equivalent exchange based on currency.
+
+**3.1.7 Byzantine fault tolerance** [b-ITU-T X.1400]: Property that enables a system to continue to operate properly even if some of its components fail or the existence of intentional bad actors.
+
+**3.1.8 crash fault tolerance** [b-ITU-T X.1400]: Property that enables a system to continue operating properly even if some of its components crash.
+
+**3.1.9 node** [b-ITU-T F.751.1]: Device or process that participates in a distributed ledger network.
+
+### 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 distributed ledger technology management service platform (DLT-MSP):** A management and service platform that helps users to create, manage and maintain distributed ledger technology (DLT) systems and applications.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|         |                                                           |
+|---------|-----------------------------------------------------------|
+| API     | Application Programming Interface                         |
+| BFT     | Byzantine Fault Tolerance                                 |
+| CFT     | Crash Fault Tolerance                                     |
+| DAPP    | Decentralized Application                                 |
+| DLT     | Distributed Ledger Technology                             |
+| DLT-MSP | Distributed Ledger Technology Management Service Platform |
+| HTTP    | Hyper Text Transfer Protocol                              |
+| MD      | Message Digest                                            |
+| P2P     | Peer-to-Peer                                              |
+| SDK     | Software Development Kit                                  |
+| SHA     | Secure Hash Algorithm                                     |
+
+# 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 keyword "**functions**" is defined as a collection of functionalities.
+- The keywords "**is recommended to**" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement needs not be present to claim conformance.
+
+# 6 Reference framework of DLT-MSP
+
+Distributed ledger technology management service platform (DLT-MSP) is a service platform provided for users to create, manage, and maintain distributed ledger technology (DLT). DLT-MSP integrates software and hardware resources, DLT systems, and control management systems to provide generic technical components for application systems, reducing the complexity of DLT usage and management. DLT-MSP consists of resource layer, DLT layer, management layer, business layer, application layer, and security layer. The DLT layer, management layer, and business layer are the core modules of the management service platform (MSP). The reference framework is shown in Figure 1.
+
+![Reference framework of distributed ledger technology management service platform (DLT-MSP) diagram showing five layers: Application, Business, Management, DLT, and Resource, with a corresponding Security layer on the right.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg)
+
+The diagram illustrates the reference framework of a distributed ledger technology management service platform (DLT-MSP). It consists of five main horizontal layers, each enclosed in a dashed box, and a vertical Security layer on the right, also in a dashed box.
+
+- Application layer:** Contains four boxes: "Supply chain finance", "Copyright verification", "Deposit evidence", and "Other application".
+- Business layer:** Contains four boxes: "User key management", "Interface management", "Browser", and "Contract templates".
+- Management layer:** Contains five vertical modules, each with sub-functions:
+  - User management:** "User creation", "Information management", "Permission management", "User notification".
+  - Node management:** "Node deployment", "Resource configuration", "Information query", "Node monitor".
+  - DLT management:** "Cryptographic management", "Consensus management", "Network management", "Storage management".
+  - Smart contract management:** "Contract deployment", "Contract upgrade", "Contract freeze", "Contract unfreeze".
+  - Log management:** "Node log", "User log", "System log", "Other log".
+- DLT layer:** Contains five boxes: "Cryptographic algorithm", "Consensus mechanism", "P2P network", "Smart contract", and "Data storage".
+- Resource layer:** Contains three boxes: "Computing resource", "Network resource", and "Storage resource".
+- Security layer:** Contains six boxes corresponding to the layers above: "Application security", "Business security", "User security", "Node security", "Smart contract security", "Log security", "DLT security", and "Resource security".
+
+F.751.16(24)
+
+Reference framework of distributed ledger technology management service platform (DLT-MSP) diagram showing five layers: Application, Business, Management, DLT, and Resource, with a corresponding Security layer on the right.
+
+**Figure 1 – Reference framework of distributed ledger technology management service platform (DLT-MSP)**
+
+### 6.1 Resource layer
+
+The resource layer is required to provide the basic software and hardware resources required for the operation of the DLT-MSP, including computing resources, network resources, and storage resources.
+
+### 6.2 DLT layer
+
+The DLT layer provides the core functionalities required for a DLT system, including cryptographic algorithms, consensus mechanisms, peer-to-peer networks, smart contracts, and data storage, among others. The DLT layer is required to meet basic requirements proposed in clause 7 of [ITU-T F.751.0].
+
+- It is required to provide fundamental capabilities such as decentralization, multi-party consensus, and tamper resistance to the upper layers of the system.
+- The DLT layer implements the invocation of underlying resources and provides basic functional support to the management layer.
+
+### 6.3 Management layer
+
+The management layer is a collection of management functions of DLT-MSP. Specifically, the management layer contains five modules: user management, node management, DLT management, smart contract management and log management. The management layer provides users with operational management functions for the DLT layer and resource layer.
+
+### 6.4 Business layer
+
+The business layer provides foundational components to the application layer, enhancing the accessibility and application scope of DLT-MSP. The business layer primarily includes transaction invocation, user key management, software development kit (SDK) management, and browser.
+
+### 6.5 Application layer
+
+The application layer refers to the domains where DLT-MSP is required to be applied, including supply chain finance, copyright verification, electronic evidence storage, and product traceability.
+
+### 6.6 Security layer
+
+Each layer of DLT-MSP has corresponding security mechanisms to ensure the security of the whole platform.
+
+It is worth noting that the DLT layer, management layer and business layer are the key contents of this Recommendation.
+
+# 7 DLT layer functionality
+
+The DLT layer provides core functionalities of distributed ledger technology, including cryptographic algorithms, consensus mechanisms, peer-to-peer (P2P) networks, smart contracts, and data storage. DLT layer core functionalities are required to meet basic requirements proposed in clause 7 of [ITU-T F.751.0].
+
+### 7.1 Cryptographic algorithm
+
+The cryptographic algorithm is required to support certain cryptographic algorithms, such as hash algorithm, symmetric cryptographic, asymmetric cryptographic, etc.
+
+- It is required to support hash verification, signing, signature verification, and state space verification, etc.
+- It is recommended to support other cryptographic algorithms, such as zero-knowledge proofs, homomorphic encryption and others.
+- The cryptographic algorithm is required to meet correctness and security requirements.
+- It is recommended to support multiple cryptographic algorithms, for example, the hash algorithm supports multiple algorithms such as SHA series, MD5, blake2, sm3, etc.
+
+### 7.2 Consensus mechanisms
+
+The consensus mechanism is required to provide the ability for consensus nodes to achieve consistency for ledger data and state data. This includes consistency of the selection results of block-producing nodes, consistency of ledger data, consistency of transaction execution results, and consistency of the state data.
+
+- The consensus is required to support both crash fault tolerant (CFT) and byzantine fault tolerant (BFT). The consensus mechanism is required to prevent double spending attacks, replay attacks.
+- The consensus mechanism is required to support adjustable consensus scope, for example, allowing add or remove one consensus nodes under the condition that the system is running normally.
+
+### 7.3 P2P network
+
+The P2P network is required to support data transfer functions among different DLT nodes.
+
+- The P2P network is required to tolerate single-point broken connections and support node discovery and connection creation.
+- It is required to support message routing and transmission capabilities, data synchronization functionality, and secure protection features such as data encryption during transmission.
+- It is recommended to support network scalability.
+
+### **7.4 Smart contracts**
+
+Smart contracts are required to support the capability to compile and execute contract code.
+
+- Smart contracts are required to support contract compilation and execution environment, and to support contract deployment, contract invocation, and contract upgrade.
+
+### **7.5 Data storage**
+
+Data storage is required to support the capability of persistent data storage.
+
+- The data storage is required to support relational or non-relational databases and meet the requirements of data consistency, integrity, and tamper resistance.
+- It is required to support distributed storage, data archiving functionality, and data encryption storage capability.
+
+## **8 Management layer functionality**
+
+The management layer is a collection of management functions for DLT-MSP and it manages various resources within the DLT system. The management layer mainly consists of five modules: the user management module, node management module, DLT management module, smart contract management module, and the log management module.
+
+### **8.1 User management**
+
+User management is a collection of user-related functionalities, including user creation, user identity maintenance, user permission management, and user notifications. The following applies to user management:
+
+- DLT-MSP is required to provide the capability for user registration and login. For example, the user account is created by administrators or by the users themselves. Once successfully created, users are able to log in to the platform and use MSP services.
+- DLT-MSP is required to provide functionality for management user identity information. For instance, users update personal information such as name and address by themselves.
+- DLT-MSP is recommended to offer user permission management functionality, allowing different users to be assigned different permissions.
+- DLT-MSP is recommended to provide user notification functionality through email, messaging, or other means.
+
+### **8.2 Node management**
+
+Node management refers to the management functionality of nodes through DLT-MSP. This includes node deployment, node resource configuration, node information query, and node status monitoring. Node management is required to meet the following requirements:
+
+- DLT-MSP is required to provide operational and maintenance management capabilities for node deployment and upgrade.
+- DLT-MSP is required to offer configuration and adjustment functions for node computing resources, network resources, and storage resources.
+
+- DLT-MSP is required to provide query and retrieval functions for node identification, IP addresses, node count, online status, and other information.
+- DLT-MSP is required to offer monitoring functionality for node runtime status, like real-time monitoring of node operation and timely detection of node service anomalies and faults.
+
+### 8.3 DLT management
+
+DLT management refers to the management functions of a DLT system that be achieved through DLT-MSP. It includes password algorithm management, consensus mechanism management, network management, and storage management. DLT management is required to meet the following requirements:
+
+- DLT-MSP is required to provide the capability to manage multiple password algorithms if DLT is supporting multiple password algorithms. For example, when DLT supports multiple hash algorithms and asymmetric encryption algorithms, users choose any supported password algorithm type, create users, and send transactions.
+- DLT-MSP is required to provide the capability to manage multiple consensus mechanisms if DLT is supporting multiple consensus types. For example, users choose any supported consensus type by their requirements and deploy the system.
+- DLT-MSP is required to provide the functionality to query and display network topology, support the division of network subnets, and support nodes joining or exiting the network.
+- DLT-MSP is required to provide the capability to manage multiple storage methods if DLT supports multiple storage methods. For example, users choose any supported relational database or non-relational database based on their actual needs and deploy the system.
+
+### 8.4 Smart contract management
+
+Smart contract management refers to the management of smart contracts through DLT-MSP. This includes contract deployment, contract upgrading, and contract freezing and thawing. The following applies to smart contract management:
+
+- DLT-MSP is required to provide the deployment function for smart contracts, allowing users to submit and deploy smart contracts through DLT-MSP.
+- DLT-MSP is required to provide the upgrading function for smart contracts, allowing users to upgrade deployed smart contracts through DLT-MSP.
+- DLT-MSP is required to provide the freezing function for smart contracts, allowing users to freeze contracts through DLT-MSP. Frozen contracts cannot be invoked normally.
+- DLT-MSP is recommended to provide the thawing function for smart contracts, allowing users to thaw previously frozen contracts through DLT-MSP. Thawed contracts are able to be invoked normally.
+
+### 8.5 Log management
+
+Log management refers to the management function of logs that can be achieved through DLT-MSP. This includes node logs, user logs, system logs, and so on. The following applies to log management:
+
+- DLT-MSP is required to provide the logging function for node logs. The recorded node information includes node identification, transactions and block information initiated by the node, and the usage of computing resources, network resources, and storage resources of the node.
+- DLT-MSP is required to provide the logging function for user logs. The recorded user information includes key operations such as user registration and information changes, as well as key transaction information initiated by the user.
+
+- DLT-MSP is required to provide the logging function for system logs. The recorded system information includes events such as system startup and shutdown, DLT network connectivity, data synchronization and verification processes, smart contract execution, errors, and exceptional events.
+- DLT-MSP is recommended to provide general log management functions, including log recording level management, comprehensive log analysis functions, download or export functions, etc.
+
+## 9 Business layer functionality
+
+The business layer encapsulates the functionalities of the management layer into generic functional components, which are provided to the application layer to lower the usage threshold of management layer functionalities and enhance the development efficiency of decentralized application (DApp). This includes user key management, interface management, browser, and smart contract template functionalities.
+
+### 9.1 User key management
+
+DLT-MSP is required to provide key management functions to users, including key generation, key storage, key backup and recovery, key authorization access, and key updates. The following applies to user key management:
+
+- DLT-MSP is required to provide key generation capabilities, like allowing users to choose suitable cryptographic algorithms to generate key pairs, public and private keys, and address identifiers.
+- DLT-MSP is required to provide key storage functionality, allowing users to choose hardware wallets, software wallets, or other storage methods to store their private keys and other key information.
+- DLT-MSP is required to provide key backup and recovery functionality, providing mechanisms for users to recover and backup their keys in case of loss or damage.
+- DLT-MSP is required to provide key authorization access, ensuring that only authorized users use specific keys for transactions and operations, limiting the scope of key authorization.
+- DLT-MSP is recommended to provide key update functionality, allowing users to proactively update their key information in the event of key loss, leakage, or theft, enhancing security and defending against potential attacks.
+
+### 9.2 Interface management
+
+DLT-MSP provides support for interfaces like hyper-text transfer protocol (HTTP) and SDK, as well as interface management functionality, to expand the integration and interaction capabilities of DLT with other systems. This includes interface documentation, interface version management, interface testing environment, and interface access control. The following applies to interface management:
+
+- DLT-MSP is required to provide interface documentation that clearly specifies the supported interface list and interface definitions. This includes the functionality, parameters, return values, and invocation methods of the interfaces. Detailed interface documentation is provided to enable developers to understand and use these interfaces correctly.
+- DLT-MSP is required to provide interface version management functionality to ensure backward compatibility and evolution of the interfaces. When changes occur in the interfaces, appropriate upgrade and migration paths are provided to avoid impacting existing applications.
+
+- DLT-MSP is required to provide an interface testing environment, including interface examples, to facilitate users in conducting interface connectivity testing and verification.
+- DLT-MSP is recommended to provide interface access control functionality to ensure that only authorized users or applications invoke the interfaces. This is achieved through authentication and authorization mechanisms such as application programming interface (API) keys, access tokens, or digital signatures to control the access rights of the interfaces.
+
+### 9.3 Browser
+
+DLT-MSP is required to provide visual browsing and querying capabilities for DLT networks and related data, allowing users to explore and retrieve DLT data through a user interface or API interface. This includes information like blocks, transactions, addresses, and smart contracts. The following applies to browsing and querying capabilities:
+
+- DLT-MSP is required to provide block display and retrieval functionality, allowing users to browse and query block information on the DLT based on criteria such as block height and timestamp. This includes block headers, transaction count, and block hashes.
+- DLT-MSP is required to provide transaction display and retrieval functionality, enabling users to query specific transaction information using keywords like transaction hash, sender address, and receiver address. It provides detailed information about transactions, like transaction hash, sender address, receiver address, payload, and timestamp.
+- DLT-MSP is required to provide visualization capabilities, allowing DLT data to be presented through charts, graphs, and statistical data. This includes displaying statistics like transaction volume, block generation speed, and address distribution.
+- DLT-MSP is recommended to provide data export and sharing functionality, allowing users to export browser data as offline files for further analysis and sharing.
+
+## 9.4 Contract templates
+
+DLT-MSP provides a universal smart contract template to assist developers in creating and deploying smart contracts more quickly. These contract templates typically include common contract functionalities and structures that are customized and extended as needed. The following applies to typical contract templates:
+
+- DLT-MSP is required to provide a notarization contract template that allows storing the hash value of data or files on the DLT, including functions for data storage, retrieval, and verification.
+- DLT-MSP is required to provide a voting contract template that supports voting and decision-making in related DApp. This template offers a voting mechanism and vote counting functionality, allowing participants to express their opinions, cast votes, and execute corresponding actions based on the voting results.
+- DLT-MSP is recommended to provide a payment contract template that includes functions for token issuance, transfers, and balance queries. It allows customization of parameters such as token name, symbol, and total supply based on specific requirements.
+
+## Bibliography
+
+- [b-ITU-T F.751.1] Recommendation ITU-T F.751.1 (2020), *Assessment criteria for distributed ledger technology (DLT) platforms.*
+- [b-ITU-T F.751.2] Recommendation ITU-T F.751.2 (2020), *Reference framework for distributed ledger technologies.*
+- [b-ITU-T F.751.7] Recommendation ITU-T F.751.7 (2022), *Functional assessment methods for distributed ledger technology platforms.*
+- [b-ITU-T X.1400] Recommendation ITU-T X.1400 (2020), *Terms and definitions for distributed ledger technology.*
+
+
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.751.17-202406-I_PDF-E/raw.md b/marked/F/T-REC-F.751.17-202406-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..2fdb28acacf2389c1b71a464bed4aac511b9e386
--- /dev/null
+++ b/marked/F/T-REC-F.751.17-202406-I_PDF-E/raw.md
@@ -0,0 +1,463 @@
+
+
+# Recommendation **ITU-T F.751.17 (06/2024)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+---
+
+## **Smart contract lifecycle management requirements for distributed ledger technology 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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.751.17
+
+## Smart contract lifecycle management requirements for distributed ledger technology systems
+
+## Summary
+
+Recommendation ITU-T F.751.17 specifies the requirements for smart contract lifecycle management, including design, development, compliance, deployment, triggering, execution, maintenance and management. By addressing these areas, distributed ledger technology (DLT) systems can efficiently realize and support programmable and intelligent functions.
+
+## History\*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.751.17 | 2024-06-13 | 16          | 11.1002/1000/15922 |
+
+## Keywords
+
+Distributed ledger technology (DLT), lifecycle, smart contract.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                   | 2 |
+| 5    | Conventions .....                                                  | 2 |
+| 6    | Overview of smart contract lifecycle management .....              | 2 |
+| 7    | The requirements of smart contract design and development .....    | 3 |
+| 7.1  | Function design for smart contracts .....                          | 3 |
+| 7.2  | Programming guidelines.....                                        | 3 |
+| 7.3  | Languages.....                                                     | 4 |
+| 8    | The requirements of smart contract compliance and deployment.....  | 4 |
+| 8.1  | Smart contract and code testing.....                               | 4 |
+| 8.2  | Smart contract compilation.....                                    | 4 |
+| 8.3  | Smart contract code audit .....                                    | 4 |
+| 8.4  | Smart contract deployment.....                                     | 5 |
+| 9    | The requirements of smart contract triggering and execution.....   | 5 |
+| 9.1  | Smart contract call .....                                          | 5 |
+| 9.2  | External interactions .....                                        | 6 |
+| 9.3  | Execution environment.....                                         | 6 |
+| 9.4  | Events .....                                                       | 6 |
+| 9.5  | Execution monitoring .....                                         | 7 |
+| 9.6  | Consistency of smart contract execution.....                       | 7 |
+| 10   | The requirements of smart contract maintenance and management..... | 7 |
+| 10.1 | Smart contract versioning.....                                     | 7 |
+| 10.2 | Smart contract upgrading .....                                     | 8 |
+| 10.3 | Smart contract freezing and unfreezing.....                        | 8 |
+| 10.4 | Smart contract revocation.....                                     | 8 |
+|      | Bibliography.....                                                  | 9 |
+
+
+
+# Recommendation ITU-T F.751.17
+
+## Smart contract lifecycle management requirements for distributed ledger technology systems
+
+## 1 Scope
+
+This Recommendation specifies smart contract lifecycle management requirements for design, development, compliance, deployment, triggering, execution, maintenance and management modules.
+
+This Recommendation can be used by smart contract providers, developers and auditors to assess smart contract implementation.
+
+## 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 distributed ledger** [b-ITU-T F.751.0]: A type of ledger that is shared, replicated, and synchronized in a distributed and decentralized manner.
+
+**3.1.2 permissionless distributed ledger system** [b-ITU-T F.751.0]: Distributed ledger system where permissions are not required to maintain and operate a node.
+
+**3.1.3 consensus** [b-ITU-T F.751.0]: Agreement that a set of transactions is valid.
+
+**3.1.4 transaction** [b-ITU-T F.751.0]: An incident or an operation that leads to a change in the status of a ledger, such as adding a record or equivalent exchange based on currency.
+
+**3.1.5 smart contract** [b-ITU-T F.751.0]: Program written on the distributed ledger system that encodes the rules for specific types of distributed ledger system transactions in a way that can be validated, and triggered by specific conditions.
+
+**3.1.6 distributed ledger technology (DLT)** [b-ITU-T F.751.1]: Technology enabling large groups of nodes in distributed ledger networks to reach agreement and record information without the need for a central authority.
+
+### 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 smart contract deployment:** Process of initializing and making a smart contract available on the blockchain system.
+
+**3.2.2 smart contract execution:** Process of running a smart contract on the blockchain network.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                   |
+|------|-----------------------------------|
+| API  | Application Programming Interface |
+| BAAS | Blockchain as a Service           |
+| DLT  | Distributed Ledger Technology     |
+| SDK  | Software Development Kit          |
+
+## 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 that is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance.
+- The keyword "functions" is defined as a collection of functionalities.
+
+## 6 Overview of smart contract lifecycle management
+
+A smart contract is a program, which realizes the automatic processing of traditional contracts in the form of computer instructions. The smart contract program is not only a computer program that can be automatically executed, but is also a system participant. It responds to received information, can receive and store values, and can also send information and values to the outside. The smart contract program is like a trusted person who can temporarily keep assets and can always perform operations according to rules specified in advance. In short, a smart contract is a piece of code triggered by both parties when they trade on blockchain assets. The contents of the smart contract are specified in advance. When the conditions for triggering the smart contract are met, the program will automatically execute the smart contract contents. Figure 1 shows the lifecycle management of a smart contract.
+
+The full lifecycle of smart contracts comprises:
+
+- Smart contract design and development is the process to design the functionality and security of a smart contract based on its business requirements and then implement the smart contract in a specific smart contract programming language.
+- Smart contract compliance and deployment is the process to compile the smart contract source code into an executable format and then deploy the executable format to a block chain platform. If a smart contract testing error occurs, the design and development steps are performed again.
+- Smart contract triggering and execution involves multiple steps. Transaction requests are sent to a block chain system and queued. Chain nodes verify the requests and manage to reach a consensus. Transactions in consensus are executed. As a result, the transactions and the results are recorded in the ledger.
+- Smart contract maintenance and management is the process to upgrade, freeze, unfreeze, or revoke a deployed smart contract for a specific purpose such as a bug fix, or a performance upgrade.
+
+![Flowchart of smart contract lifecycle management showing four stages: design and development, testing and deployment, triggering and execution, and maintenance and management, with a feedback loop from testing back to design.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg)
+
+```
+
+graph TD
+    A[Smart contract design and development] --> B[Smart contract testing, compliance and deployment]
+    B --> C[Smart contract triggering and execution]
+    C --> D[Smart contract maintenance and management]
+    B --> A
+  
+```
+
+Flowchart of smart contract lifecycle management showing four stages: design and development, testing and deployment, triggering and execution, and maintenance and management, with a feedback loop from testing back to design.
+
+F.751.17(24)
+
+**Figure 1 – Lifecycle management of smart contract**
+
+## 7 The requirements of smart contract design and development
+
+### 7.1 Function design for smart contracts
+
+Before writing smart contract code, it is necessary to design the functions of the smart contract, and satisfy the following requirements:
+
+- it is required to collect, analyse, refine and verify the functional requirements of the smart contract, and draft the function requirement documents;
+- it is recommended to use the design tools, and retain the design drawings, e.g., class diagram, use case diagram, sequence diagram, data flow diagram, flow diagram, architecture diagram, deployment diagram, etc.;
+- it is required to design permission management for the smart contract and assign permissions according to the minimum requirements;
+- it is required to properly design the time-sequencing logic of the smart contract to avoid security issues, e.g., race conditions;
+- it is recommended to design class diagrams, use case diagrams, sequence diagrams, data flow diagrams, process diagrams, architecture diagrams, deployment diagrams, and preserve corresponding design diagrams;
+- it is required to design the security threat model and perform risk analysis, management, and contingency measures;
+- it is required to design the ability to handle or mitigate errors in the contract, including but not limited to terminate in advance or update online;
+- it is required to design the smart contract method interfaces with backward compatibility. If the method logic has undergone incompatible changes, the method version number should be modified or new interfaces should be added.
+
+### 7.2 Programming guidelines
+
+When writing smart contract code to realize the designed function, the programming manner satisfies the following requirements:
+
+- it is recommended to use a popular and stable coding language, such as solidity, C++, Java, Go, etc.;
+- the smart contract function is recommended to be coded in a modular manner.
+
+### 7.3 Languages
+
+The programming language satisfies the following requirements:
+
+- it is required to support both Turing-complete and non-Turing-complete languages;
+- the data types are required to support string, integer, Boolean and array;
+- the data types are required to support byte, char, short integer, long integer, float, map, and vector;
+- the calculation types are required to support arithmetic operation, relational operation, logical operation, conditional operation, and assignment operation.
+
+## 8 The requirements of smart contract compliance and deployment
+
+### 8.1 Smart contract and code testing
+
+After the smart contract codes are developed, necessary tests are carried out. The smart contract and code testing satisfy the following requirements:
+
+- a smart contract test process and scheme is required to be provided;
+- it is required to provide single-step debugging capability;
+- it is required to test and evaluate the business logic;
+- the test cases are required to cover all business logic branches and exception handling branches;
+- it is required to test and evaluate the security;
+- the test methods contain static analysis, dynamic test and formal verification. The testing method is recommended to have a high degree of automation.
+
+### 8.2 Smart contract compilation
+
+Smart contract compilation is the process of converting the smart contract code into executable format. The smart contract compilation satisfies the following requirements:
+
+- it is required to clarify the information and version of the compilation tool, as well as the relying environment information;
+- it is required to use the latest and stable safe compilation tools;
+- after compilation, the interface description file and suffix of the compilation result file are generated.
+
+### 8.3 Smart contract code audit
+
+After the smart contract is developed, functional and security audits are required The smart contract code audit satisfies the following requirements:
+
+- the audit document is required to contain a business description, and the steps and methods to compile, deploy and invoke the smart contract;
+- if the smart contract needs to call other external contracts or interact with other online or offline modules, the audit document is required to contain the corresponding description;
+- it is required to have sufficient comments about the interface, function, and complex logic of the smart contract, so as to help auditors understand the implementation of the code;
+- before the smart contract is deployed, it is required to undergo a complete and independent security audit;
+- before the smart contract is deployed, it is required to undergo a complete and independent business logic audit.
+
+### **8.4 Smart contract deployment**
+
+Smart contract deployment is the process of deploying a smart contract code to a blockchain node within the runtime environment of the smart contract, which meets the following requirements:
+
+- the smart contract deployment behaviour is required to achieve distributed ledger technology (DLT) consensus before conducting operations;
+- deployment permissions of the smart contract are required to be verified;
+- deployment status of the smart contract is required to be returned;
+- unique identification, such as address, smart contract name, etc. is required to be confirmed after the smart contract is deployed.
+
+## **9 The requirements of smart contract triggering and execution**
+
+### **9.1 Smart contract call**
+
+A smart contract call triggers the smart contract service. The smart contract call meets the following requirements:
+
+- interface calls are required to support the query of the basic smart contract information, execution results and smart contract status;
+- interface calls are required to support smart contract abolition, event setting, runtime environment variable setting;
+- interface calls are recommended to support smart contract upgrading, freezing, and unfreezing;
+- interface name is required to be identifiable and readable;
+- it is required to comply with safety rules;
+- it is required to verify the interface parameters to prevent the actual interface from being inconsistent with expectations;
+- the interface is required to comply with the principle of minimum requirements, and undergo strict authority management;
+- when a smart contract call fails, it is required to have an error message or have routine correction functions such as automatic parameter type conversion.
+
+#### **9.1.1 Oracle call**
+
+The smart contract triggers oracle through the relevant interface of oracle, and meets the following requirements:
+
+- interface name, input parameters and return data are required to meet the application programming interface (API) specification;
+- interface protocol is required to support the secure transmission protocol;
+- oracle is required to ensure the integrity and completeness of the source data and prevent any unauthorized alterations;
+- the impact of external data provided by the oracle is required to be limited within the scope of the smart contract and not affect the overall system.
+
+#### **9.1.2 Random number call**
+
+The smart contract triggers the random numbers for on-chain applications, such as voting or gaming applications, and meets the following recommendations:
+
+- random numbers at different nodes are recommended to ensure deterministic execution semantics;
+
+- random numbers obtained for different transactions are recommended to be truly random;
+- random numbers are recommended to be unpredictable, and random number algorithms require cryptographic proof.
+
+### 9.2 External interactions
+
+The smart contract interacts with the outside world during execution, and meets the following requirements:
+
+- it is required to support interactions with external users or applications, e.g., deployment, querying, invocation, etc.;
+- it is required to support accessing external data through the smart contract (such as oracle);
+- it is required to provide an accurate interface description and make a strict inspection of the external input;
+- when a smart contract interacts with the external data, the external data shall only affect the status of the current contract.
+
+### 9.3 Execution environment
+
+The execution (runtime) environment provides the environment for smart contract execution, and satisfies the following requirements:
+
+- it is required to support different types of virtual machines or containers;
+- it is required to be isolated from the external environment, and invocation will not cause the failure of the system;
+- it is required to be independent, and abnormal smart contract execution cannot affect the stability of the blockchain system;
+- different nodes are required to perform the same transaction with the same result under the same input and the same historical status;
+- a trusted execution environment is recommended to provide a privacy protection technology environment;
+- it is recommended to provide a pending function when a smart contract is incorrect.
+
+### 9.4 Events
+
+A smart contract event refers to a module in which the external account is packaged into the current block for permanent access during a smart contract call. The smart contract event meets the following requirements:
+
+- events are required to be monitored, and the business party can access the event name, event parameters, block height and other information;
+- events are required to include the event name and event parameters;
+- the event name is required to be the unique identity;
+- the event name is recommended to reflect the event type.
+
+#### 9.4.1 Normal business event
+
+A normal business event refers to a smart contract call that completes the normal business process, triggering an event and recording the normal flow of the business, which meets the following requirements:
+
+- it is required to record the relevant parties, business types and status;
+- the event parameters are required to record business data.
+
+#### **9.4.2 Abnormal business event**
+
+An abnormal business event refers to the process of calling the smart contract interface, entering the judgment logic of business exception handling, and triggering an exception event so that the business side can know the cause of the error. It satisfies the following requirements:
+
+- the initiator and the reason of the abnormal business events are required to be recorded;
+- the smart contract interface and parameters that cause abnormal business events are required to be recorded;
+- the event parameters are required to include the type of error exception and the reason for the error.
+
+### **9.5 Execution monitoring**
+
+The monitoring ability is necessary to display the execution process and any relevant information during the smart contract's execution. Smart contract execution monitoring satisfies the following:
+
+- a launched smart contract is required to have real-time transaction monitoring ability to detect abnormal transactions and attacks that may occur during the smart contract runtime;
+- transaction monitoring is required to cover the block information, transaction information, and the relevant indicators regarding to the asset flow and transaction logic;
+- the real-time identification of abnormal or malicious transactions is recommended to be completed within one block time.
+
+### **9.6 Consistency of smart contract execution**
+
+Smart contract execution runs the smart contract code to complete the scheduled function, which meets the following requirements:
+
+- enforceable termination principle and a deterministic execution result principle are required;
+- current smart contract execution is required to be atomic and support abnormal rollback;
+- smart contract status is required to be saved on a blockchain network, such as the attribute of a contract account;
+- certainty and consistency of the smart contract execution is required;
+- events pushed to subscribed clients in the process of smart contract execution is required;
+- deterministic treatment floating-point calculations are required.
+
+## **10 The requirements of smart contract maintenance and management**
+
+### **10.1 Smart contract versioning**
+
+Each modification of the smart contract is a separate version, which meets the following requirements:
+
+- the smart contract version is required to be maintained by using a version number. It can distinguish the order of versions before and after upgrading;
+- the smart contract version upgrade is required to support automatic number increment or customized version number;
+- each modification of the smart contract is required to update the version number.
+
+### **10.2 Smart contract upgrading**
+
+The upgrading operation for the smart contract is initiated by the client, submitted to the blockchain through an interface call, and becomes effective after achieving consensus. This upgrading process meets the following:
+
+- in the event of a failed upgrading, it is recommended to roll back to the pre-upgraded version of the smart contract;
+- it is recommended to include a version control function that ensures the new version is compatible with the old version.
+
+### **10.3 Smart contract freezing and unfreezing**
+
+The process of smart contract freezing and unfreezing involves pausing and resuming the smart contract calling function. Smart contract freezing and unfreezing meets the following:
+
+- the freezing function is recommended to halt the smart contract when breaches are detected;
+- the unfreezing function is recommended to restore the smart contract once the breaches have been rectified;
+- the operation authority is recommended to be verified when freezing and unfreezing the operation of the smart contract.
+
+### **10.4 Smart contract revocation**
+
+Smart contract revocation is an irreversible process that involves the annulment of a deployed smart contract. Smart contract revocation meets the following:
+
+- the data is required to be saved even after smart contract revocation;
+- the code of the terminated smart contract is recommended to be saved;
+- the operation authority is required when the smart contract revocation program is called, ensuring that only authorized operations can take effect;
+- cancellable smart contracts are recommended to be explicitly declared during deployment;
+- corresponding measures are required to protect the rights and assets of users in the smart contract when the smart contract is revoked.
+
+## Bibliography
+
+- [b-ITU-T F.751.0] Recommendation ITU-T F.751.0 (2020), *Requirements for distributed ledger systems.*
+- [b-ITU-T F.751.1] Recommendation ITU-T F.751.1 (2020), *Requirements for distributed ledger systems.*
+- [b-ITU-T F.751.2] Recommendation ITU-T F.751.2 (2020), *Reference framework for distributed ledger technologies.*
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.751.18-202406-I_PDF-E/raw.md b/marked/F/T-REC-F.751.18-202406-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..efa9455ff90a99ec70318c213d7088a9b9ed5233
--- /dev/null
+++ b/marked/F/T-REC-F.751.18-202406-I_PDF-E/raw.md
@@ -0,0 +1,414 @@
+
+
+# Recommendation **ITU-T F.751.18 (06/2024)**
+
+SERIES F: Non-telephone telecommunication services  
+Multimedia services
+
+---
+
+## **Framework for distributed ledger technology (DLT)-based energy metering data sharing**
+
+![ITU logo](390120de4fe440c42fea8154fcaad334_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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.751.18
+
+# Framework for distributed ledger technology (DLT)-based energy metering data sharing
+
+## Summary
+
+To provide better support for energy applications such as carbon emission and green certificates based on trustworthy energy metering data, Recommendation ITU-T F.751.18 specifies a framework for distributed ledger technology (DLT)-based energy metering data sharing and it provides functional modules of the DLT-based energy metering data sharing platform.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.751.18 | 2024-06-13 | 16          | 11.1002/1000/15923 |
+
+## Keywords
+
+DLT, energy metering data sharing.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                                | 2    |
+| 4 Abbreviations and acronyms .....                                           | 2    |
+| 5 Conventions .....                                                          | 3    |
+| 6 Background.....                                                            | 3    |
+| 7 Framework of DLT-based energy metering data sharing.....                   | 3    |
+| 7.1 Overview .....                                                           | 3    |
+| 7.2 DLT-based energy metering data sharing platform.....                     | 4    |
+| 7.3 Stakeholders .....                                                       | 5    |
+| 7.4 Energy applications .....                                                | 6    |
+| 7.5 Energy metering data sources.....                                        | 7    |
+| 8 Functional modules of DLT-based energy metering data sharing platform..... | 7    |
+| 8.1 DLT gateway layer .....                                                  | 7    |
+| 8.2 DLT core layer .....                                                     | 8    |
+| 8.3 DLT service layer .....                                                  | 8    |
+| Bibliography.....                                                            | 10   |
+
+
+
+# Recommendation ITU-T F.751.18
+
+## Framework for distributed ledger technology (DLT)-based energy metering data sharing
+
+## 1 Scope
+
+This Recommendation defines a framework for distributed ledger technology (DLT)-based energy metering data sharing and specifies functional modules of the DLT-based energy metering data sharing platform.
+
+This Recommendation provides guidance for the development and application of the DLT-based energy metering data sharing 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 F.751.0] Recommendation ITU-T F.751.0 (2020), *Requirements for distributed ledger systems*.
+- [ITU-T F.751.2] Recommendation ITU-T F.751.2 (2020), *Reference framework for distributed ledger technologies*.
+- [ITU-T F.751.9] Recommendation ITU-T F.751.9 (2023), *Trusted execution environment based confidential computing on distributed ledger technology systems*.
+- [ITU-T X.1400] Recommendation ITU-T X.1400 (2020), *Terms and definitions for distributed ledger technology*.
+- [ISO 22739] ISO 22739:2024, *Blockchain and distributed ledger technologies – Vocabulary*.
+- [ISO/IEC 11889-1] ISO/IEC 11889-1:2015, *Information technology – Trusted platform module library – Part 1: Architecture*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+- 3.1.1 account** [ITU-T X.1400]: Representation of an entity whose data is recorded on a distributed ledger.
+- 3.1.2 block** [ITU-T X.1400]: Individual data unit of a blockchain, composed of a collection of transactions and a block header.
+- 3.1.3 decentralized application** [ITU-T X.1400]: Application that runs in a distributed and decentralized computing environment.
+- 3.1.4 distributed ledger** [ITU-T X.1400]: A type of ledger that is shared, replicated, and synchronized in a distributed and decentralized manner.
+
+- 3.1.5 **distributed ledger network** [ISO 22739]: Network within a distributed ledger system.
+- 3.1.6 **DLT system** [ITU-T X.1400]: A system that implements a distributed ledger.
+- 3.1.7 **node** [ITU-T X.1400]: Device or process that participates in a distributed ledger network.
+- 3.1.8 **off-chain** [ITU-T X.1400]: Related to a blockchain system, but located, performed or run outside that blockchain system.
+- 3.1.9 **on-chain** [ITU-T X.1400]: Located, performed or run inside a blockchain system.
+- 3.1.10 **smart contract** [ITU-T X.1400]: A program written on the distributed ledger system which encodes the rules for specific types of distributed ledger system transactions in a way that can be validated and triggered by specific conditions.
+
+### 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+- 3.2.1 **DLT gateway**: A component that provides a secure and controlled interface between an external application or system and a DLT network. Its main purpose is to enable external applications to interact with the DLT network, without requiring direct access to the network. Refer to [b-Belchior].
+- 3.2.2 **DLT network**: The synonym of distributed ledger network [ISO 22739].
+- 3.2.3 **energy metering data**: The information collected by an energy metering device or energy metering system about the consumption and production of electricity or other forms of energy (e.g., water, gas) by a consumer or producer.
+- 3.2.4 **energy metering device**: The instrument used to measure, monitor, and record the consumption or production of energy, such as electricity, gas, or water. It typically consists of hardware and software components that work together to collect data and provide accurate readings of the amount of energy used or generated over a period of time.
+- 3.2.5 **energy metering system**: A collection of devices and software tools used to measure, monitor, analyse, and manage energy consumption or production in a facility or a broader area. It typically includes one or more energy metering devices, data communication infrastructure, data storage and management systems, and related applications for data analysis, reporting, and control.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                      |
+|------|--------------------------------------|
+| API  | Application Programming Interface    |
+| DApp | Decentralized Application            |
+| DLT  | Distributed Ledger Technology        |
+| DR   | Demand Response                      |
+| DRTM | Dynamic Root for Trusted Measurement |
+| P2P  | Peer to Peer                         |
+| PoS  | Proof of Stake                       |
+| PoW  | Proof of Work                        |
+| SRTM | Static Root for Trusted Measurement  |
+| TEE  | Trusted Execution Environment        |
+| TPM  | Trusted Platform Module              |
+
+## 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 needs 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 Background
+
+Accurate energy metering is crucial for the effective operation of energy business applications. The energy metering devices or systems are typically situated at the user's end, beyond direct regulatory oversight, which introduces the risk of potential tampering or inaccuracies. Compounded by the multitude of participants in energy applications and the diverse nature of business scenarios, a key challenge lies in seamlessly integrating foundational metering data with multiple upper-layer applications without redundancy. This underscores the critical need for reliable energy metering data as well as its sharing.
+
+In response to these challenges, applications using distributed ledger technology (DLT) and smart contract technology act as a sound solution. With their inherent features of transparency, traceability, and tamper resistance, distributed ledgers in conjunction with a peer to peer (P2P) infrastructure network, have established a platform where energy metering data are securely collected, verified, and shared. This platform facilitates the development of new energy applications that foster trust among a diverse array of stakeholders.
+
+# 7 Framework of DLT-based energy metering data sharing
+
+### 7.1 Overview
+
+The overall framework of DLT-based energy metering data sharing is shown in Figure 1.
+
+![Figure 1: Overall framework of DLT-based energy metering data sharing. The diagram illustrates a network of stakeholders and devices connected to a central 'DLT-based energy metering data sharing platform'. Stakeholders include Energy applications, Environmental agency, Regulatory body, Grid operator, Energy supplier, and Data consumer. The platform consists of multiple DLT nodes, each containing a Distributed ledger and a DLT node. Energy consumers are connected to the platform via DLT gateways, which in turn connect to Energy metering devices or systems. A legend on the right identifies the symbols for Distributed ledger, DLT node, Energy application, and Metering data resource. The reference F.751.18(24) is noted at the bottom right.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg)
+
+F.751.18(24)
+
+Figure 1: Overall framework of DLT-based energy metering data sharing. The diagram illustrates a network of stakeholders and devices connected to a central 'DLT-based energy metering data sharing platform'. Stakeholders include Energy applications, Environmental agency, Regulatory body, Grid operator, Energy supplier, and Data consumer. The platform consists of multiple DLT nodes, each containing a Distributed ledger and a DLT node. Energy consumers are connected to the platform via DLT gateways, which in turn connect to Energy metering devices or systems. A legend on the right identifies the symbols for Distributed ledger, DLT node, Energy application, and Metering data resource. The reference F.751.18(24) is noted at the bottom right.
+
+**Figure 1 – Overall framework of DLT-based energy metering data sharing**
+
+The framework of DLT-based energy metering data sharing is composed of the DLT-based energy metering data sharing platform, related stakeholders, energy applications and metering data sources.
+
+The DLT-based energy metering data sharing platform is composed of multiple DLT nodes, each hosting a DLT system and running decentralized applications (DApps). Various energy applications such as energy trading and carbon emissions interact with the platform through smart contracts or application programming interfaces (APIs). Energy metering devices or systems supply the platform with data on power, water, gas usage, etc., facilitated by DLT gateways provided by specific DLT nodes, enabling seamless integration of metering data with the DLT network.
+
+To ensure the integrity and immutability of energy metering data as it is uploaded to the DLT network through DLT gateways, a secure and transparent process is implemented. When energy metering data is collected from devices or systems, it undergoes encryption and hashing to create a unique digital fingerprint. This fingerprint is then timestamped and stored on the DLT network through the DLT gateway. The energy metering data is stored off-chain considering the privacy of energy metering data, the capacity of DLT nodes, and the overall efficiency of the platform.
+
+To prevent tampering, the DLT network employs consensus mechanisms such as proof of work (PoW) or proof of stake (PoS) to validate and confirm the transactions containing the metering data. Once the data is added to the DLT, it becomes part of a distributed ledger that is replicated across all nodes in the network. Any attempt to alter the data would require simultaneous changes to the majority of nodes, making it practically impossible to manipulate the information without detection.
+
+By utilizing cryptographic techniques, consensus mechanisms, and the decentralized nature of DLT, the platform ensures the authenticity and integrity of energy metering data, establishing a trusted and transparent environment for energy-related applications and transactions.
+
+### 7.2 DLT-based energy metering data sharing platform
+
+The functional modules of DLT-based energy metering data sharing platform are shown in Figure 2.
+
+![Diagram of functional modules of DLT-based energy metering data sharing platform](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+The diagram illustrates the functional modules of a DLT-based energy metering data sharing platform, organized into three layers:
+
+- DLT service layer** (top):
+  - Data entitlement
+  - Data query
+  - Data provenance
+  - Data validation
+  - Data processing
+  - Access control
+- DLT core layer** (middle):
+  - Smart contract
+  - TEE
+  - On-chain and off-chain collaboration
+  - P2P service
+  - Distributed ledger
+  - Consensus mechanism
+- DLT gateway layer** (bottom):
+  - Source verification
+  - Metrics monitoring
+  - Data collection and parsing
+  - Fingerprint generation
+  - On-chain functionality
+  - Off-chain storage
+
+F.751.18(24)
+
+Diagram of functional modules of DLT-based energy metering data sharing platform
+
+**Figure 2 – Functional modules of DLT-based energy metering data sharing platform**
+
+The DLT-based energy metering data sharing platform is mainly composed of three layers:
+
+- The DLT gateway layer: This layer facilitates the secure and reliable integration of metering data information onto the DLT nodes. Essential functionalities within this layer include source verification, metrics monitoring, data collection and parsing, fingerprint generation, on-chain functionality and off-chain storage.
+- The DLT core layer: This layer comprises a specific DLT system with a trusted execution environment (TEE) support. Essential functionalities within this layer include P2P service, consensus mechanism, distributed ledger, TEE, smart contract and on-chain and off-chain collaboration capabilities.
+- The DLT service layer: This layer serves as a decentralized application (DApps) on DLT nodes, providing services for energy applications through smart contracts or API. Essential functionalities within this layer include data query, data entitlement, data processing, data provenance, data validation and access control.
+
+The detailed functional modules of each layer are defined in clause 8.
+
+## 7.3 Stakeholders
+
+The stakeholders involved in DLT-based energy metering data sharing play a crucial role in the operation and governance of the DLT-based energy metering data sharing platform. These stakeholders may include:
+
+- Energy suppliers: These entities are involved in generating and supplying energy to consumers. They utilize metering data for billing, resource optimization, and forecasting energy demand. Some virtual energy operators which aggregate and manage distributed energy resources are also part of this category.
+
+- Energy consumers: These entities are end-users who consume energy for residential, commercial, or industrial purposes. They may use metering data for energy management, conservation, and cost optimization. Furthermore, they may participate in green certificate programmes to certify their purchases of electricity from renewable sources, which are also certified by reliable metering data.
+- Grid operators: These entities are responsible for managing the distribution and transmission of energy across the grid. They rely on metering data for grid balancing, maintenance, and ensuring grid stability.
+- Data consumers: These entities engage in energy data trading, exchanging data related to energy production, consumption, market prices, and emissions. They utilize this data to optimize energy strategies and improve environmental performance.
+- Environmental agencies: These entities utilize energy metering data to track carbon emissions associated with energy consumption. This data supports efforts towards carbon neutrality and greenhouse gas reduction.
+- Regulatory bodies: Regulatory bodies play a supervisory role by overseeing the compliance of energy transactions with established regulations and standards. By providing nodes on the DLT network, regulatory bodies monitor and audit energy metering data to ensure fairness, transparency, and adherence to legal requirements. Their involvement enhances the credibility and integrity of the energy metering data shared on the platform.
+
+### 7.4 Energy applications
+
+Energy applications rely on accurate metering data to optimize energy consumption, balance supply and demand, facilitate data exchange, incentivize energy efficiency and monitor carbon emissions for environmental sustainability. These applications may include:
+
+- Energy trading: Energy trading refers to the buying and selling of energy products in a competitive market. This includes electricity, natural gas and other renewable energy commodities such as biomass or wind power. Energy trading aims to balance supply and demand, manage price risks, and secure stable revenue streams for energy producers and suppliers. Refer to [b-ITU-T F.751.13] for more details on power trading based on DLT.
+- Energy data trading: Energy data trading refers to the buying and selling of data generated around energy production, use, distribution, and other aspects. This includes data such as energy market prices, energy production, energy consumption, and emissions data. Energy data trading helps companies and organizations better understand their energy usage patterns, optimize their energy procurement and consumption strategies, and improve their environmental performance.
+- Demand response (DR): DR is a smart grid management strategy that allows utilities and grid operators to balance electricity supply and demand by incentivizing users to adjust their energy consumption patterns during times of peak demand. DLT-based DR is for further study [b-ITU-T H.DLT-SGDRF].
+- Virtual power plant (VPP): VPP is a cloud-based platform that integrates multiple decentralized energy assets, such as rooftop solar panels, battery storage systems, and demand response programmes, to create an integrated network of distributed energy resources. VPPs enable utilities, grid operators, and aggregators to manage and optimize these distributed energy resources in real-time, much like a traditional power plant. Virtual power plants based on DLT are for further study [b-ITU-T F.DLT-VPPO].
+- Green certificate: Green certificates, also known as green power consumption certification, refer to a process of verifying and certifying green power purchases made by individual or corporate consumers, which typically involves the procurement of electricity generated from renewable sources such as solar and wind. The certification process typically confirms that
+
+the generation source is genuinely renewable and meets specific environmental criteria and standards. Refer to [b-ITU-T F.751.14] for more details on how reliable energy metering data are being traced based on DLT.
+
+- Carbon emission: Carbon emission refers to the release of carbon dioxide gas (CO<sub>2</sub>) and other greenhouse gases into the Earth's atmosphere, primarily from human activities such as burning fossil fuels, deforestation, and industrial processes. Reducing carbon emissions is considered vital for mitigating the effects of climate change, and energy metering data helps track the amount of carbon emissions associated with energy consumption, supporting efforts towards achieving carbon neutrality and reducing greenhouse gas emissions.
+
+### 7.5 Energy metering data sources
+
+The energy metering data originates from two main sources:
+
+- Energy metering device: These devices are situated on the user's side and are tasked with monitoring or regulating energy consumption. Energy suppliers typically authenticate and benchmark these devices before deployment. Examples include smart power meters and smart water meters.
+- Energy metering system: These systems are usually situated on either the energy supplier's side or the consumer's side and provide aggregated energy metering data on a larger scale. Examples include electric information collection systems used by power grid companies and energy consumption monitoring systems in industrial parks.
+
+To ensure the authenticity of collected metering data, it is required for both energy metering devices and systems to incorporate trusted platform module (TPM) functionality. TPM serves as a secure cryptographic component, establishing a root of trust in trusted computing before metering data is generated.
+
+Periodic integrity measurements using TPM are conducted in energy metering devices and systems. This process involves verifying software and firmware integrity by comparing stored measurements in the TPM with predefined expected values. This practice safeguards against tampering or compromise of energy metering data since the last measurement. In case of a discrepancy, an alert is triggered to notify the DLT network. Data collected post-alert is flagged as untrusted on the platform.
+
+The integrity measurement using TPM based on static root for trusted measurement (SRTM) and dynamic root for trusted measurement (DRTM) is required to comply with [ISO/IEC 11889-1].
+
+## 8 Functional modules of DLT-based energy metering data sharing platform
+
+### 8.1 DLT gateway layer
+
+The DLT gateway layer, embodied by the DLT gateway, plays a crucial role in ensuring the integrity and security of energy metering data and acts as a bridge between on-chain and off-chain. This layer comprises several essential modules as follows:
+
+- Source verification: It is required to validate the authenticity and origin of the incoming data, ensuring that it comes from trusted sources.
+- Metrics monitoring: It is required to monitor metrics from the TPM periodically. By keeping track of these metrics, the system ensures that the TPM is functioning correctly and that any deviations from the expected values are promptly identified and addressed.
+- Data collection and parsing: It is required to collect raw data from energy metering devices and systems, parse it into a standardized format, and prepare it for further processing.
+- Fingerprint generation: It is required to create unique identifiers for data sets, enabling efficient tracking and verification of data integrity.
+
+- On-chain functionality: It is required to store critical data and transactions directly on the chain, ensuring transparency, immutability, and decentralized access.
+- Off-chain storage: It is required to store the verified data in off-chain storage, providing flexibility and scalability while maintaining the privacy of the data as well as accessibility and security.
+
+The collection process of the energy metering data in the DLT gateway layer is shown in Figure 3. Before data acquisition, data source verification is always conducted. Once the sources are authenticated, the process bifurcates into two independent streams. One stream monitors periodic metrics from the trusted platform module (TPM). An alarm will be generated, organized into blocks, and uploaded on-chain when a discrepancy occurs. Simultaneously, the other stream manages the data collection process. The energy metering data from trusted sources are retrieved, performed with format parsing and forwarded to off-chain storage upon successful verification. Additionally, a unique fingerprint for the verified data is generated, encrypted, signed, packed into blocks, and subsequently transmitted to the DLT system.
+
+![Flowchart of the energy metering data collection process in the DLT gateway layer. The process starts with 'Data source validation', which branches into two paths. The first path goes to 'Monitor periodic metrics from TPM', which then leads to 'Alert upload on-chain'. The second path goes to 'Data collection', which leads to 'Data parsing'. From 'Data parsing', the process branches into two paths: one to 'Fingerprint generation', which leads to 'Fingerprint upload on-chain', and another to 'Data storage off-chain'. A label 'F.751.18(24)' is present in the bottom right corner of the diagram area.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg)
+
+```
+
+graph LR
+    A[Data source validation] --> B[Monitor periodic metrics from TPM]
+    B --> C[Alert upload on-chain]
+    A --> D[Data collection]
+    D --> E[Data parsing]
+    E --> F[Fingerprint generation]
+    F --> G[Fingerprint upload on-chain]
+    E --> H[Data storage off-chain]
+  
+```
+
+F.751.18(24)
+
+Flowchart of the energy metering data collection process in the DLT gateway layer. The process starts with 'Data source validation', which branches into two paths. The first path goes to 'Monitor periodic metrics from TPM', which then leads to 'Alert upload on-chain'. The second path goes to 'Data collection', which leads to 'Data parsing'. From 'Data parsing', the process branches into two paths: one to 'Fingerprint generation', which leads to 'Fingerprint upload on-chain', and another to 'Data storage off-chain'. A label 'F.751.18(24)' is present in the bottom right corner of the diagram area.
+
+**Figure 3 – The collection process of the energy metering data in DLT gateway layer**
+
+### 8.2 DLT core layer
+
+The basic functionalities of the DLT system, such as P2P service, consensus mechanism, smart contract and distributed ledger are required to comply with [ITU-T F.751.0] and [ITU-T F.751.2].
+
+Trusted execution environment (TEE) is required to enable secure and confidential computation in the DLT system. It creates a trusted environment where only authenticated parties access sensitive data and execute transactions securely. It allows the endorsement of transactions without revealing their details which enhances the privacy and confidentiality of the transactions. With TEE technology, it becomes possible to run smart contracts securely and verify them with minimal disclosure of the contract's contents to anyone other than the contract participants. The implementation of the TEE feature is required to comply with [ITU-T F.751.9].
+
+On-chain and off-chain collaboration is required to link or associate data stored in the distributed ledger on the chain (metering data fingerprints, transaction records, smart contracts, etc.) with off-chain data (energy metering data). In this way, on-chain and off-chain collaboration functions enhance the efficiency and reliability of DLT systems by combining the strengths of both on-chain and off-chain data sources. To reference the data stored off-chain, the DLT system is recommended to employ cryptographic hashes, pointers, or other unique identification methods that are verified on the chain to guarantee that the correct data has been retrieved.
+
+### 8.3 DLT service layer
+
+The capabilities that the DLT service layer is required to offer are not limited to:
+
+- Access control:
+
+- Login verification: Users are required to be verified by their accounts or keys to ensure that their identity is legal.
+  - Permission control: Different permissions are required to be assigned according to users' roles, the functionalities, and the data they would like to access.
+  - Log recording: Log is required to record sensitive operations and to audit.
+- Data verification: It is required to perform on-chain and off-chain joint verification for energy metering data and corresponding fingerprints to ensure the validity of off-chain data.
+  - Data processing:
+    - Data indexing: It is required to provide the ability to classify, mark, and organize the data so that users can quickly find the information they need.
+    - Data computing: It is required to provide statistical computing functions from different dimensions of metering data, e.g., monthly total usage and average value for a certain data source.
+  - Data query: It is required to provide query functions for different statistical dimensions of metering data based on the data processing results after data verification.
+  - Data entitlement: It is required to provide the ability of identification for ownership, permission, and value for energy metering data, which helps to clarify ownership and usage rights for each data and helps to determine the scope of access based on data sensitivity and confidentiality requirements.
+  - Data provenance: It is required to provide tracing functions for metering data's sources, storage, access, and transaction history to confirm the authenticity and trustworthiness of the data's entire lifecycle.
+
+## Bibliography
+
+- [b-ITU-T F.751.13] Recommendation ITU-T F.751.13 (2023), *Framework and requirements for distributed ledger technology-based distributed power trading systems.*
+- [b-ITU-T F.751.14] Recommendation ITU-T F.751.14 (2024), *Reference architecture for information tracing of renewable energy consumption based on distributed ledger technology.*
+- [b-ITU-T F.DLT-VPPO] Draft Recommendation ITU-T F.DLT-VPPO, *General architecture for DLT-based virtual power plant operation platform.*  
+<[http://www.itu.int/itu-t/workprog/wp\\_item.aspx?isn=18995](http://www.itu.int/itu-t/workprog/wp_item.aspx?isn=18995)>
+- [b-ITU-T H.DLT-SGDRF] Draft Recommendation ITU-T H.DLT-SGDRF, *Framework of distributed ledger technology-based smart grid demand response.*  
+<[http://www.itu.int/itu-t/workprog/wp\\_item.aspx?isn=18616](http://www.itu.int/itu-t/workprog/wp_item.aspx?isn=18616)>
+- [b-Belchior] Belchior, R., Riley, L., Hardjono, T., Vasconcelos, A., Correia, M. (2023), *Do You Need a Distributed Ledger Technology Interoperability Solution?* ACM Journals, Distributed Ledger Technologies: Research and Practice, Vol. 2, No. 1, pp. 1-37.  
+<<https://dl.acm.org/doi/10.1145/3564532>>
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.751.19-202406-I_PDF-E/raw.md b/marked/F/T-REC-F.751.19-202406-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c04713166753017674acdec42d71dbab95237ce4
--- /dev/null
+++ b/marked/F/T-REC-F.751.19-202406-I_PDF-E/raw.md
@@ -0,0 +1,412 @@
+
+
+# Recommendation **ITU-T F.751.19 (06/2024)**
+
+SERIES F: Non-telephone telecommunication services  
+Multimedia services
+
+---
+
+## **Framework and requirements for distributed ledger technology based on sharding technique**
+
+![ITU logo](390120de4fe440c42fea8154fcaad334_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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.751.19
+
+# Framework and requirements for distributed ledger technology based on sharding technique
+
+## Summary
+
+Recommendation ITU-T F.751.19 specifies the framework and technical requirements for distributed ledger technology based on the sharding technique, and it can be used as a guideline to perform DLT system scalability.
+
+Sharding technique helps to improve the scalability of distributed ledger technology (DLT) systems, including the transaction processing throughput and ledger storage capacity, without compromising the decentralization and security.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.751.19 | 2024-06-13 | 16          | 11.1002/1000/15924 |
+
+## Keywords
+
+Distributed ledger technology, framework and requirements, sharding technique.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                 | 2    |
+| 4 Abbreviations and acronyms .....                            | 2    |
+| 5 Conventions .....                                           | 2    |
+| 6 Overview .....                                              | 2    |
+| 7 Overall framework.....                                      | 3    |
+| 7.1 Framework of DLT system based on sharding technique ..... | 3    |
+| 7.2 Core functional components.....                           | 3    |
+| 8 Transaction flow .....                                      | 4    |
+| 9 Technical requirements.....                                 | 5    |
+| 9.1 Scalability requirements .....                            | 5    |
+| 9.2 Usability requirements.....                               | 6    |
+| 9.3 Security requirements.....                                | 6    |
+| Bibliography.....                                             | 8    |
+
+
+
+# Recommendation ITU-T F.751.19
+
+## Framework and requirements for distributed ledger technology based on sharding technique
+
+# 1 Scope
+
+This Recommendation specifies the framework and technical requirements for distributed ledger technology (DLT) based on sharding technique. It includes:
+
+- framework of DLT system based on sharding technique;
+- core functional components of DLT system based on sharding technique;
+- transaction flow of DLT system with sharding capabilities;
+- technical requirements described from the perspectives of scalability, usability and security.
+
+This Recommendation can be used as a guideline for DLT service providers to build DLT systems based on sharding technique, and for DLT system demanders to select and use a DLT system with sharding 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 F.751.2] Recommendation ITU-T F.751.2 (2020), *Reference framework for distributed ledger technologies*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 blockchain** [b-ITU-T F.751.0]: A type of distributed ledger that is composed of digitally recorded data arranged as a successively growing chain of blocks with each block cryptographically linked and hardened against tampering and revision.
+
+**3.1.2 consensus** [b-ITU-T F.751.0]: Agreement that a set of transactions is valid.
+
+**3.1.3 ledger** [b-ITU-T F.751.0]: Information store that keeps final and definitive (immutable) records of transactions.
+
+**3.1.4 node** [b-ITU-T F.751.0]: Device or process that participates in a distributed ledger network.
+
+**3.1.5 smart contract** [b-ITU-T F.751.0]: Program written on the distributed ledger system that encodes the rules for specific types of distributed ledger system transactions in a way that can be validated and triggered by specific conditions.
+
+**3.1.6 transaction** [b-ITU-T F.751.0]: An incident or an operation that leads to a change in the status of a ledger, such as adding a record or equivalent exchange based on currency.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 shard:** A logical division composed of a group of distributed ledger technology (DLT) system nodes. Each shard processes the transactions independently and has its own ledger storage. All shards within the DLT system communicate with each other to exchange and validate transaction data.
+
+**3.2.2 sharding:** A technique that divides the distributed ledger technology (DLT) system into multiple shards. It helps the DLT system to enhance scalability.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|     |                               |
+|-----|-------------------------------|
+| 2PC | Two-phase Commit              |
+| DLT | Distributed Ledger Technology |
+| EOV | Execute-Order-Validate        |
+| P2P | Peer to Peer                  |
+| TPS | Transactions Per Second       |
+| VM  | Virtual Machine               |
+| WFG | Wait For Graph                |
+
+# 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 or service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with this Recommendation.
+
+# 6 Overview
+
+This Recommendation specifies the framework and technical requirements for distributed ledger technology based on sharding technique, including the following three aspects:
+
+- Overall framework – High-level framework of distributed ledger technology (DLT) system based on the sharding technique, including the core functional components required to build the sharding capabilities and the hierarchical relationship between them.
+- Transaction flow – Diagram illustrating the flow of transaction processing in the DLT system based on the sharding technique.
+- Technical requirements – Requirements described from the scalability, usability and security perspectives.
+
+# 7 Overall framework
+
+## 7.1 Framework of DLT system based on sharding technique
+
+As mentioned in [ITU-T F.751.2], there is an internal system extension that aims to resolve the problem of scalability for one DLT system with the same governance model, and sharding is considered as one of the most valuable internal extension solutions, which allows the DLT system to be divided into multiple shards.
+
+The framework of the DLT system based on the sharding technique shown in Figure 1 is derived from a high-level framework of the DLT system included in [ITU-T F.751.2]. A new layer called "On-chain sharding" is appended, and it includes a group of functional components for building shards.
+
+![Figure 1: Framework of DLT system based on sharding technique. The diagram shows a layered architecture. The central part is a stack of layers: Application (top, containing Dapp(s) with Runtime, Lifecycle, Devtool), Governance and compliance, On-chain sharding (highlighted in blue, containing Sharding strategy management, Shard management, Intra-shard processing, Cross-shard distribution, Cross-shard coordination), Protocol (containing Account/DID, Right management, Consensus, Ledger management, Messaging, Crypto), and Resources (containing Node management, Storage management, Network management, Data integrity and privacy util). To the left is a vertical bar for 'Operation and maintenance'. To the right are 'External interaction management' and 'External resource management'. A dashed box on the far right lists 'Extensions' including Side chain, Off chain, Multi chain, Internal extensions, and '...'. The label F.751.19(24) is at the bottom right.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg)
+
+Figure 1: Framework of DLT system based on sharding technique. The diagram shows a layered architecture. The central part is a stack of layers: Application (top, containing Dapp(s) with Runtime, Lifecycle, Devtool), Governance and compliance, On-chain sharding (highlighted in blue, containing Sharding strategy management, Shard management, Intra-shard processing, Cross-shard distribution, Cross-shard coordination), Protocol (containing Account/DID, Right management, Consensus, Ledger management, Messaging, Crypto), and Resources (containing Node management, Storage management, Network management, Data integrity and privacy util). To the left is a vertical bar for 'Operation and maintenance'. To the right are 'External interaction management' and 'External resource management'. A dashed box on the far right lists 'Extensions' including Side chain, Off chain, Multi chain, Internal extensions, and '...'. The label F.751.19(24) is at the bottom right.
+
+**Figure 1 – Framework of DLT system based on sharding technique**
+
+## 7.2 Core functional components
+
+The on-chain sharding layer consists of five core functional components, including shard management, sharding strategy management, intra-shard processing, cross-shard distribution and cross-shard coordination.
+
+### 7.2.1 Shard management
+
+DLT system with sharding is required to provide the ability to manage the lifecycle of shards, including:
+
+- DLT system with sharding is required to provide the ability to create shards.
+- DLT system with sharding is required to provide the ability to setup shards, including configure DLT nodes within shards, initialize peer to peer (p2p) network, setup consensus mechanism, deploy smart contract, etc.
+- Delete shards – DLT system is required to provide the ability to delete shards, including recycle the resources of shards, backup data across shards, etc.
+
+### 7.2.2 Sharding strategy management
+
+DLT system with sharding is required to provide the sharding methods for users to predefine and manage the mapping relationship between transaction keys and shards, including:
+
+- DLT system with sharding is required to provide a default sharding strategy. For example, hash-based sharding can optionally be enabled by default to assign the state data to the corresponding shards and distribute the transaction to the corresponding shards determined by the hash of state key.
+- DLT system with sharding is recommended to provide an approach that the users optionally predefine the mapping relationship between state keys of transaction and shards according to the specific transaction logics.
+
+#### 7.2.3 Intra-shard processing
+
+Each shard within the DLT system is required to have the ability to process the incoming transactions independently and store the result in its own ledger. Each shard within the DLT system is required to provide intra-shard processing with the following functions: intra-shard transaction execution, intra-shard consensus, intra-shard transaction validation, intra-shard block synchronization, and intra-shard storage.
+
+#### 7.2.4 Cross-shard distribution
+
+Distributed ledger technology (DLT) system with sharding is required to provide the ability to process cross-shard transactions, which may access the state data across shards. DLT system with sharding is required to provide cross-shard distribution with the following functions:
+
+- DLT system with sharding is required to provide the ability to get the state data required by transaction across shards during the endorsement phase.
+- DLT system with sharding is required to provide the ability to distribute the transaction to the corresponding shards for processing during the consensus phase.
+- DLT system with sharding is required to provide the ability to get validation results of state data across shards during the validation phase.
+
+#### 7.2.5 Cross-shard coordination
+
+DLT system with sharding is required to provide a coordination mechanism across shards to complete atomic commit or rollback of cross-shard transactions to ensure data consistency, including:
+
+- DLT system with sharding is required to provide a decentralized coordinator for each shard to complete the coordination of cross-shard transactions.
+- DLT system with sharding is required to provide the atomic commitment protocol to ensure the atomicity and consistency of cross-shard transactions such as two-phase commit (2PC) protocol.
+
+# 8 Transaction flow
+
+DLT system is always dedicated to process transaction events/requests of users. Figure 2 is from [ITU-T F.751.2] illustrating a type of transaction flow and how DLT systems process events of incoming transactions and store the result in the ledger. This type of transaction flow follows the execute-order-validate (EOV) sequence, which greatly improves system throughput through parallelism in the pre-execution phase. However, this type of transaction flow cannot provide the scalability of the entire DLT system.
+
+![Figure 2: The transaction flow of DLT system without sharding. The flow consists of six sequential steps: Event, VM Pre-execute env., Execute Event → state, Consensus, Validate, and Store state/block. The label F.751.19(24) is at the bottom right.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+```
+
+graph LR
+    Event[Event] --> VM[VM Pre-execute env.]
+    VM --> Execute[Execute Event → state]
+    Execute --> Consensus[Consensus]
+    Consensus --> Validate[Validate]
+    Validate --> Store[Store state/block]
+  
+```
+
+F.751.19(24)
+
+Figure 2: The transaction flow of DLT system without sharding. The flow consists of six sequential steps: Event, VM Pre-execute env., Execute Event → state, Consensus, Validate, and Store state/block. The label F.751.19(24) is at the bottom right.
+
+**Figure 2 – The transaction flow of DLT system without sharding [ITU-T F.751.2]**
+
+DLT system with sharding can scale the transaction throughput and storage capacity without compromising and decentralization, and security. As shown in Figure 3, it is the transaction flow for DLT system based on sharding technique, which enhances the transaction flow in Figure 2 by adding three additional steps. This flow enables the shards within the DLT system to have the ability to process the transactions independently, and when it is necessary to process cross-shard transactions, shards communicate with each other to complete the data exchange, transaction distribution and coordination across them.
+
+![Figure 3: The transaction flow of DLT system with sharding. The flow consists of six sequential steps: Event, VM Pre-execute env., Execute Event → state, Consensus, Validate, and Store state/block. Between these steps, three additional cross-shard steps are added: A (Cross-shard data exchange) linked to Execute, B (Cross-shard transaction distribution) linked to Consensus, and C (Cross-shard transaction coordination) linked to Validate. The label F.751.19(24) is at the bottom right.](5a4e62bead259c258d069fd3663ea670_img.jpg)
+
+```
+
+graph LR
+    Event[Event] --> VM[VM Pre-execute env.]
+    VM --> Execute[Execute Event → state]
+    Execute --> Consensus[Consensus]
+    Consensus --> Validate[Validate]
+    Validate --> Store[Store state/block]
+    
+    Execute -.-│
+    │-.-│ A[Cross-shard data exchange]
+    
+    Consensus -.-│
+    │-.-│ B[Cross-shard transaction distribution]
+    
+    Validate -.-│
+    │-.-│ C[Cross-shard transaction coordination]
+  
+```
+
+F.751.19(24)
+
+Figure 3: The transaction flow of DLT system with sharding. The flow consists of six sequential steps: Event, VM Pre-execute env., Execute Event → state, Consensus, Validate, and Store state/block. Between these steps, three additional cross-shard steps are added: A (Cross-shard data exchange) linked to Execute, B (Cross-shard transaction distribution) linked to Consensus, and C (Cross-shard transaction coordination) linked to Validate. The label F.751.19(24) is at the bottom right.
+
+**Figure 3 – The transaction flow of DLT system with sharding**
+
+The additional steps of the transaction process in the DLT system with sharding includes:
+
+- A. **Cross-shard data exchange step** – When a transaction is executed, and if the transaction needs to read the states/records stored from different shards, a cross-shard data exchange step is required to collect states/records from all the involved shards and ensure that the transaction execution completed.
+- B. **Cross-shard transaction distribution step** – After transaction pre-execution is completed, the transaction needs to be packaged into the block in a certain order by consensus. If a transaction needs to be processed across shards, a cross-shard distribution step is required to distribute the transaction to all the involved shards and ensure that each shard completes the consensus and generates a block containing the transaction.
+- C. **Cross-shard transaction coordination step** – When a transaction is to be validated, the transaction is committed as valid only if all states pass the read-write set validation. If a transaction needs to be validated across shards, a cross-shard coordination step is required to collect the validation results from all the involved shards and decide whether the transaction is committed as valid in all shards.
+
+# 9 Technical requirements
+
+## 9.1 Scalability requirements
+
+### 9.1.1 Scalable transaction throughput
+
+Transaction throughput represents how many transaction events/requests that the system processes, validates and commits per unit time, which is always measured by transactions per second (TPS). Scalability of the DLT system is required to provide the ability to improve transaction throughput by adding resources to the DLT system, such as increasing the number of DLT nodes.
+
+- DLT system with sharding is required to provide nearly linear TPS scalability after adding shards and related resources required by shards.
+
+- DLT system with sharding is required to ensure that the overall TPS of the system will not drop sharply while processing a certain number of cross-shard transactions.
+
+### **9.1.2 Scalable storage capacity**
+
+Storage capacity represents the amount of data that the DLT system stores. Scalability of the DLT system is required to provide the growing storage capacity by adding resources to the system, such as increasing the number of DLT nodes.
+
+- DLT system with sharding is required to provide nearly linear storage capacity scalability after adding shards and related resources required for shards.
+- DLT system with sharding is required to ensure the immutability and traceability of the ledger after adding several DLT nodes for sharding.
+
+#### **9.1.3 Auto scaling**
+
+DLT system with sharding is required to provide the auto scaling capabilities. For example, increase the number of shards when the transaction traffic or storage usage exceeds a certain threshold.
+
+## **9.2 Usability requirements**
+
+### **9.2.1 Easy-to-use**
+
+DLT system with sharding is required to provide easy-to-use deployment and management capabilities for administrators/users, including:
+
+- DLT system with sharding is required to provide one-click deployment to achieve more convenient shard creation, initialization and deletion.
+- DLT system with sharding is required to provide rich interfaces and monitoring tools to make it easier to manage all shards in the system.
+
+### **9.2.2 Configurable sharding strategy**
+
+Whether the DLT system achieves near-linear scalability through sharding mechanism directly depends on whether an appropriate sharding strategy is configured to reduce the probability of cross-shard transactions as much as possible, so that all shards in the DLT system processes the transactions independently and in parallel. Usually, the DLT system users are well aware of their applications' logics and distribution of business data, so it is recommended to provide a configurable shard strategy which helps users to predefine the mapping relationship between state keys of transaction and shard ID according to the specific transaction logics.
+
+- DLT system with sharding is recommended to provide a flexible method for users to predefine various strategies based on different dimensions, including range-based, algorithmic-based, relationship-based, geography-based, etc. And it is recommended to provide wildcard support in strategy definitions so that different strategies can be combined and nested.
+- DLT system with sharding is recommended to provide the ability to update the sharding strategy in all shards of the system.
+
+### **9.2.3 Transparent application interfaces**
+
+DLT system with sharding is required to provide users with a suite of transparent application interfaces, regardless of whether the sharding is enabled or not.
+
+### **9.3 Security requirements**
+
+#### **9.3.1 Transaction atomicity**
+
+If a transaction needs to be processed and validated across shards, DLT system with sharding is required to ensure the atomicity of the transaction.
+
+- DLT system with sharding is required to provide a coordination mechanism to collect the validation results of all the involved shards during the transaction validation phase and decide whether the transaction is committed on each shard.
+- DLT system with sharding is required to provide a unified mechanism for each shard to detect the transaction deadlocks and solve the deadlocks with the same rules. The transaction deadlock occurs when a transaction in one shard waits for locks held by another transaction in another shard, which is also waiting for the locks held by the first transaction. Each involved shard in the DLT system is required to deploy a dedicated node responsible for identifying the presence of deadlocks and solving deadlocks by the same algorithm, such as wait for graph (WFG) algorithm.
+
+#### 9.3.2 Data integrity
+
+As mentioned in clause 9.1.3, DLT system with sharding is required to provide auto scaling capabilities. While doing the scale-in and scale-out, the state and ledger needs to be migrated across shards.
+
+- DLT systems with sharding is required to provide off-chain tools or on-chain mechanisms to help users complete data migration between shards, and after migration, verify the accuracy and completeness of the migrated state data and ledgers.
+- DLT systems with sharding is required to provide a transaction logging mechanism to maintain data changes caused by incremental transactions during the data migration across shards and ensure the newly incoming transaction events/requests is processed during the migration.
+- DLT systems with sharding are recommended to provide a monitoring mechanism to monitor the progress of migration and identify any anomalies or inconsistencies during migration.
+
+#### 9.3.3 Shard attack resistance
+
+Sharding technique helps DLT systems improve the scalability of transaction throughput and ledger storage capacity. However, it would also reduce the overall computing power required to validate transactions on each individual shard, so that attackers would have a higher chance of attacking the entire DLT system by attacking a single shard.
+
+- DLT system with sharding is required to provide a random shard allocation mechanism based on the cryptographic functions to randomly assign validators to different shards to prevent attackers from strategically attacking a certain shard.
+- DLT system with sharding is required to re-allocate the validators across shards periodically and dynamically.
+
+## Bibliography
+
+[b-ITU-T F.751.0] Recommendation ITU-T F.751.0 (2020), *Requirements for distributed ledger 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.751.26-202503-I_PDF-E/raw.md b/marked/F/T-REC-F.751.26-202503-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..709a95042145dc11ed07a9cf341366d99c3dc23b
--- /dev/null
+++ b/marked/F/T-REC-F.751.26-202503-I_PDF-E/raw.md
@@ -0,0 +1,473 @@
+
+
+# Recommendation**ITU-T F.751.26 (03/2025)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+---
+
+### **Framework and requirements for distributed ledger technology-based energy storage sharing**
+
+![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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.751.26
+
+# Framework and requirements for distributed ledger technology-based energy storage sharing
+
+## Summary
+
+Recommendation ITU-T F.751.26 specifies framework and requirements for distributed ledger technology (DLT)-based energy storage sharing (ESS) which aims at optimizing electricity demand management, improving renewable energy integration and increasing grid flexibility while ensuring trust and accountability. It includes the stakeholders, the framework and the functional requirements of DLT-based ESS. The business process of DLT-based ESS is also provided in the appendix.
+
+This Recommendation can be used as guidance for the development and application of the DLT-based ESS for smart grid.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.751.26 | 2025-03-16 | 21          | 11.1002/1000/16259 |
+
+## Keywords
+
+DLT, energy storage sharing.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <https://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                    | 2    |
+| 6 Stakeholders of DLT-based energy storage sharing.....                | 2    |
+| 7 Framework of DLT-based energy storage sharing .....                  | 4    |
+| 7.1 DLT core layer .....                                               | 4    |
+| 7.2 ESS service layer.....                                             | 5    |
+| 8 Functional requirements of DLT-based energy storage sharing.....     | 5    |
+| 8.1 DLT core layer .....                                               | 5    |
+| 8.2 ESS service layer.....                                             | 6    |
+| Appendix I – Business process of DLT-based energy storage sharing..... | 9    |
+| I.1 Overview .....                                                     | 9    |
+| I.2 User management phase .....                                        | 9    |
+| I.3 ESS publication and discovery phase.....                           | 10   |
+| I.4 ESS reservation and contracting phase.....                         | 10   |
+| I.5 ESS utilization and release phase .....                            | 11   |
+| I.6 Transaction management phase.....                                  | 11   |
+| I.7 ESS monitoring phase .....                                         | 12   |
+| Bibliography.....                                                      | 14   |
+
+
+
+# Recommendation ITU-T F.751.26
+
+## Framework and requirements for distributed ledger technology-based energy storage sharing
+
+# 1 Scope
+
+This Recommendation specifies the framework and requirements for distributed ledger technology (DLT) based energy storage sharing (ESS). It includes:
+
+- Stakeholders of DLT-based energy storage sharing;
+- Framework of DLT-based energy storage sharing;
+- Functional requirements of DLT-based energy storage sharing.
+
+This Recommendation provides guidance for the development and application of the DLT-based ESS for smart grid.
+
+# 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.751.0](#)] Recommendation ITU-T F.751.0 (2020), *Requirements for distributed ledger systems*.
+
+[[ITU-T F.751.2](#)] Recommendation ITU-T F.751.2 (2020), *Reference framework for distributed ledger technologies*.
+
+[[ITU-T F.751.9](#)] Recommendation ITU-T F.751.9 (2023), *Trusted execution environment based confidential computing on distributed ledger technology systems*.
+
+# 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 consensus** [b-ITU-T X.1400]: Agreement that a set of transactions is valid.
+
+**3.1.2 distributed energy resources (DER)** [b-ITU-T Y.2072]: An energy generation and energy storage facility located at the customer premises or power transmission and distribution systems.
+
+**3.1.3 distributed ledger** [b-ITU-T X.1400]: A type of ledger that is shared, replicated, and synchronized in a distributed and decentralized manner.
+
+**3.1.4 distributed ledger technology (DLT)** [b-ITU-T X.1400]: Technology that enables the operation and use of distributed ledgers.
+
+**3.1.5 DLT system** [b-ITU-T X.1400]: A system that implements a distributed ledger.
+
+**3.1.6 electrical energy storage (EES)** [b-IEC 62933-1]: Installation that is able to absorb electrical energy, to store it for a certain amount of time and release the electrical energy during which energy conversion processes may be included.
+
+**3.1.7 energy storage** [b-ITU-T Y.2072]: Energy storage provides storage functions of electricity using various types of batteries.
+
+**3.1.8 off-chain** [b-ITU-T X.1400]: Related to a blockchain system, but located, performed or run outside that blockchain system.
+
+**3.1.9 on-chain** [b-ITU-T X.1400]: Located, performed or run inside a blockchain system.
+
+**3.1.10 smart contract** [b-ITU-T X.1400]: A program written on the distributed ledger system which encodes the rules for specific types of distributed ledger system transactions in a way that can be validated, and triggered by specific conditions.
+
+### 3.2 Terms defined in this Recommendation
+
+None.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|     |                                   |
+|-----|-----------------------------------|
+| API | Application Programming Interface |
+| DLT | Distributed Ledger Technology     |
+| EES | Electrical Energy Storage         |
+| ESS | Energy Storage Sharing            |
+| IoT | Internet of Things                |
+| KPI | Key Performance Indicator         |
+| SLA | Service Level Agreement           |
+| TEE | Trusted Execution Environment     |
+
+# 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 needs not be present to claim conformance.
+
+# 6 Stakeholders of DLT-based energy storage sharing
+
+Energy storage sharing (ESS) refers to the practice of utilizing electrical energy storage (EES) collectively among multiple users or entities to optimize energy management, enhance grid stability, and support various grid services. The introduction of distributed ledger technology (DLT) enhances ESS by improving transparency and traceability of energy transactions, which fosters trust among users. Additionally, DLT-based ESS enables efficient coordination of EESs among multiple users and increases security through its immutable nature, thus reducing the risk of fraud. The stakeholders involved in DLT-based ESS is shown in Figure 1.
+
+![Diagram of stakeholders of DLT-based energy storage sharing. The diagram shows a central circle of eight 'DLT node' icons connected by dashed lines. Above the circle, 'Energy providers' (represented by a stack of boxes) and 'EES providers' (represented by a stack of boxes) are connected to the nodes. At the top center, a 'Grid operator' box is connected to a node. At the bottom center, a 'Regulatory body' box is connected to a node. A legend on the left identifies the icons: a stack of boxes for 'Distributed ledger', a cylinder for 'DLT node', and a rectangle for 'Stakeholder'. The text 'DLT-based energy storage sharing' is in the center of the circle. The code 'F.751.26(25)' is in the bottom right.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg)
+
+Diagram of stakeholders of DLT-based energy storage sharing. The diagram shows a central circle of eight 'DLT node' icons connected by dashed lines. Above the circle, 'Energy providers' (represented by a stack of boxes) and 'EES providers' (represented by a stack of boxes) are connected to the nodes. At the top center, a 'Grid operator' box is connected to a node. At the bottom center, a 'Regulatory body' box is connected to a node. A legend on the left identifies the icons: a stack of boxes for 'Distributed ledger', a cylinder for 'DLT node', and a rectangle for 'Stakeholder'. The text 'DLT-based energy storage sharing' is in the center of the circle. The code 'F.751.26(25)' is in the bottom right.
+
+**Figure 1 – Stakeholders of DLT-based energy storage sharing**
+
+The DLT-based ESS is composed of multiple DLT nodes, each hosting a DLT system and running decentralized applications. These nodes are contributed by various stakeholders, covering:
+
+- **EES providers:** These entities are organizations or individuals that own and operate EESs, including battery storage facilities. They facilitate the storage of excess energy during times of low demand and discharge it during peak periods or when required to stabilize the grid. EES providers may engage in energy arbitrage, buying electricity when prices are low and selling it when prices are high.
+- **Energy providers:** These entities are responsible for generating or procuring energy from various sources such as power plants or renewable energy installations. They play a crucial role in supplying energy to the grid and may also participate in energy trading markets to optimize their operations and revenue streams.
+- **Grid operator:** Grid operator manages the transmission and distribution infrastructure that delivers electricity from generation sources to end-users. It ensures the stability and reliability of the grid by balancing supply and demand in real-time. Grid operators also oversee the integration of distributed energy resources (DERs), including EESs, into the grid to enhance its flexibility and resilience.
+- **Regulatory body:** The regulatory body, often a government agency or regulatory commission, oversees the energy market and enforces rules and regulations to ensure fair competition, consumer protection, and grid reliability. It sets policies related to grid operation, energy pricing, and market participation criteria for energy suppliers, EES providers, and other stakeholders involved in the energy sector. Additionally, it may establish standards and guidelines for the deployment and operation of ESS.
+
+The DLT-based ESS enables stakeholders to collaborate and optimize their interactions through smart contracts:
+
+- EES providers efficiently manage energy storage assets, optimize their utilization, and participate in energy trading activities seamlessly. They can maximize revenue streams, improve asset efficiency, and contribute to grid stability.
+
+- Energy providers optimize energy procurement strategies and effectively manage energy portfolios. By using real-time data and insights, they ensure a reliable energy supply and meet consumer demand efficiently. Collaboration with other stakeholders also enables to integrate renewable energy sources seamlessly.
+- Grid operators issue instructions and coordinate with ESS providers to balance supply and demand dynamics in real-time. This also helps to optimize grid operations, mitigate congestion, and ensure reliable power delivery.
+- Regulatory body establishes rules, standards, and incentives for transparent and fair participation in the ESS. They ensure compliance with regulations and promote market integrity to drive sustainable development.
+
+Overall, the combination of DLT and smart contracts in the ESS enables greater efficiency, transparency, and reliability in energy transactions, contributing to the advancement of a more sustainable and resilient energy infrastructure.
+
+# 7 Framework of DLT-based energy storage sharing
+
+The framework of the DLT-based ESS is shown in Figure 2.
+
+![Figure 2 – Framework of the DLT-based energy storage sharing. The diagram shows two stacked layers: the ESS service layer on top and the DLT core layer on the bottom. The ESS service layer contains six boxes: User management, ESS publication and discovery, ESS reservation and contracting, ESS utilization and release, Transaction management, and ESS monitoring. The DLT core layer contains six boxes: P2P service, Distributed ledger, Consensus mechanism, Smart contract, Privacy computing, and On-chain and off-chain collaboration. A small label 'F.751.26(25)' is at the bottom right of the diagram.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg)
+
+Figure 2 – Framework of the DLT-based energy storage sharing. The diagram shows two stacked layers: the ESS service layer on top and the DLT core layer on the bottom. The ESS service layer contains six boxes: User management, ESS publication and discovery, ESS reservation and contracting, ESS utilization and release, Transaction management, and ESS monitoring. The DLT core layer contains six boxes: P2P service, Distributed ledger, Consensus mechanism, Smart contract, Privacy computing, and On-chain and off-chain collaboration. A small label 'F.751.26(25)' is at the bottom right of the diagram.
+
+**Figure 2 – Framework of the DLT-based energy storage sharing**
+
+The DLT-based ESS is mainly composed of two layers:
+
+- **The DLT core layer.** Essential functionalities within this layer include P2P service, consensus mechanism, distributed ledger, privacy computing, smart contract and on-chain and off-chain collaboration capabilities.
+- **The ESS service layer.** Essential functionalities within this layer include user management, ESS publication and discovery, ESS reservation and contracting, ESS utilization and release, transaction management, and ESS monitoring.
+
+### 7.1 DLT core layer
+
+This layer serves as the foundational backbone, providing the necessary infrastructure for secure and efficient operations. It includes:
+
+- **P2P service:** This functionality facilitates direct transactions between distributed nodes without intermediaries, enhancing efficiency and reducing costs.
+
+- **Consensus mechanism:** This functionality ensures agreement among distributed nodes on the state of the ledger, which is essential for maintaining trust and preventing fraud.
+- **Distributed ledger:** This functionality provides a transparent and immutable record of all transactions, enhancing accountability.
+- **Privacy computing:** This functionality protects user data and transaction details, ensuring that sensitive information remains confidential.
+- **Smart contracts:** This functionality automates and enforces agreements between parties, reducing the need for manual intervention and increasing trust.
+- **On-chain and off-chain collaboration:** This functionality allows for interaction between on-chain data and off-chain data, enabling a more flexible and comprehensive collaboration.
+
+### 7.2 ESS service layer
+
+This layer focuses on the operational aspects of energy storage sharing, providing the necessary support for users and transactions. Key functionalities include:
+
+- **User management:** This functionality handles user registration, authentication, and profile management to ensure a secure and personalized experience.
+- **ESS publication and discovery:** This functionality enables users to publish available EES resources and discover options that meet their needs.
+- **ESS reservation and contracting:** This functionality facilitates the reservation of energy storage resources and the creation of binding contracts between users.
+- **ESS utilization and release:** This functionality manages the actual use of EES resources and their return to the pool after use.
+- **Transaction management:** This functionality oversees all the financial transactions related to ESS, ensuring accuracy and security.
+- **ESS monitoring:** This functionality provides real-time monitoring of energy storage utilization and performance, ensuring transparency and efficiency.
+
+## 8 Functional requirements of DLT-based energy storage sharing
+
+### 8.1 DLT core layer
+
+The functional requirements for the DLT core layer are as follows:
+
+- P2P service, consensus mechanism, smart contract and distributed ledger are required to comply with clauses 7 and 8 of [ITU-T F.751.0] and clause 7 of [ITU-T F.751.2].
+- Privacy computing is required to adopt the trusted execution environment (TEE) solution for the DLT system and is required to comply with clause 8 of [ITU-T F.751.9].
+- For On-chain and off-chain collaboration:
+  - It is required to enable seamless data exchange between on-chain and off-chain systems, which ensures that relevant data can flow freely between the on-chain data and external data sources, facilitating comprehensive decision-making.
+  - It is required to implement secure application programming interfaces (APIs) for accessing off-chain data, which ensures that only authorized users and applications can access and interact with off-chain data, maintaining data integrity and security.
+  - It is required to support data validation mechanisms for off-chain inputs, which ensures that data coming from off-chain sources is verified for accuracy and reliability before being used in on-chain processes or smart contracts.
+
+- It is required to allow for real-time updates and synchronization between on-chain and off-chain data, which is essential for maintaining consistency and ensuring that participants have access to the most current information.
+- It is required to provide a mechanism for logging and auditing off-chain interactions, which ensures that interactions with off-chain data are recorded for transparency and accountability, allowing for audits and traceability.
+- It is required to ensure that off-chain computations can be securely referenced on-chain, which allows the results of complex calculations performed off-chain to be securely integrated into on-chain transactions or smart contracts.
+- It is recommended to support interoperability with various off-chain data sources and systems, which ensures that the collaboration functionality can integrate with different systems, databases, or services that provide relevant off-chain data.
+
+### 8.2 ESS service layer
+
+The functional requirements for the ESS service layer are as follows:
+
+– For user management:
+
+- It is required to provide secure user registration and authentication processes, which ensures that user accounts are protected against unauthorized access.
+- It is required to implement role-based access control, which ensures that different user roles have specific permissions to access various functionalities.
+- It is required to allow users to manage their profiles, which includes updating personal information, changing passwords, and configuring notification preferences.
+- It is required to provide a mechanism for account recovery, which ensures that users are able to recover their accounts through secure methods, such as password reset links or two-factor authentication.
+- It is required to maintain an audit trail of user activity, which includes logging significant actions taken by users, such as logins, profile changes, and transactions, to enhance accountability and security.
+
+– For ESS publication and discovery:
+
+- It is required to enable users to publish their available EES, which allows users to specify details such as capacity, location, availability, and pricing.
+- It is required to implement a search and filter mechanism for discovering EES, which allows users to be able to search for resources based on criteria such as location, capacity, price, and availability.
+- It is required to provide an interface for listing and managing published resources, which allows users to be able to easily view, edit, or remove their published listings.
+- It is required to support the categorization of sharing EES, which allows users to classify their resources based on type, technology, or other relevant attributes for easier discovery.
+- It is recommended to implement a rating and review function for published resources, which allows users to be able to provide feedback on their experiences, enhancing trust and transparency in the marketplace.
+
+– For ESS reservation and contracting:
+
+- It is required to facilitate the reservation process for energy storage resources, which allows users to be able to reserve resources for specific timeframes, subject to availability.
+
+- It is required to enable the creation of smart contracts for reservations which automate the terms of use, including duration, pricing, and conditions for cancellation or modification.
+- It is required to provide notifications for reservation confirmations and reminders, which allows users to receive alerts regarding their reservations, including confirmations and upcoming expirations.
+- It is required to implement an interface for managing reservations, which allows users to be able to view, modify, or cancel their reservations easily.
+- It is required to ensure compliance with legal and regulatory requirements in contracting, which includes incorporating necessary terms and conditions that protect both providers and consumers.
+
+– For ESS utilization and release:
+
+- It is required to track the utilization of EES resources in real-time, which includes monitoring storage levels, usage patterns, and performance metrics.
+- It is required to provide a mechanism for users to release storage resources after use, which ensures that resources are returned to the pool promptly and that their availability is updated.
+- It is required to implement alerts for low storage levels or abnormal usage patterns, which allows users to be notified of issues that may impact the performance or availability of their resources.
+- It is required to maintain an audit trail of utilization activities, which includes logging details of when resources were used, by whom, and for how long, enhancing transparency and accountability.
+- It is recommended to provide performance analytics for users, which allows users to have access to insights regarding their storage utilization, helping them make informed decisions about future engagements.
+
+– For transaction management:
+
+- It is required to facilitate secure payment processing for transactions, which includes support for various payment methods and ensuring that all financial interactions are encrypted and secure.
+- It is required to implement an invoicing function for transactions, which allows users to receive detailed invoices that outline the terms of the transaction, including costs and service periods.
+- It is required to provide a mechanism for transaction dispute resolution, which allows users to raise issues with transactions and facilitate communication between parties to resolve disputes.
+- It is required to maintain an audit trail of transactions which includes logging transaction details, such as timestamps, amounts, and involved parties, for transparency and accountability.
+
+– For ESS monitoring:
+
+- It is required to provide real-time monitoring of EES utilization, which allows users to be able to access live data regarding their storage usage, including current levels and performance metrics.
+- It is required to implement historical data analysis features, which allows users to be able to view trends and patterns in their storage utilization over time to inform future decisions.
+
+- It is required to send alerts for anomalies or performance issues, which allows users to receive notifications if there are significant deviations from expected performances or usage patterns.
+- It is required to ensure data privacy and security in monitoring, where the monitoring data is protected against unauthorized access while still being accessible to authorized users for analysis.
+- It is recommended to provide dashboards for monitoring, which allows users to have access to intuitive interfaces that visualize their storage performance and utilization metrics.
+
+## Appendix I
+
+### Business process of DLT-based energy storage sharing
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### I.1 Overview
+
+The distributed ledger technology (DLT)-based energy storage sharing (ESS) operates through a series of streamlined phases that facilitate user interactions and resource management, leveraging functionalities from both the DLT core layer and the ESS service layer. It consists of six key phases: user management, ESS publication and discovery, ESS reservation and contracting, ESS utilization and release, transaction management, and ESS monitoring.
+
+- The process begins with user management, where users securely register and authenticate their accounts through the ESS service layer. This phase establishes role-based access control, ensuring that users can log in according to their designated roles. The DLT core layer supports this process by maintaining a secure and immutable record of user identities and activities, enhancing trust and accountability.
+- Once registered, users can publish their electrical energy storage (EES) resources in the ESS publication and discovery phase. This phase allows users to list their resources, including details such as capacity and availability. The ESS service layer facilitates the search and filtering of these resources, while the DLT core layer ensures that all published data is securely stored and verifiable, promoting transparency in the marketplace.
+- In the reservation and contracting phase, users can reserve energy storage resources through smart contracts, which are executed on the DLT core layer. This automation streamlines the reservation process, ensuring that terms are clear and enforceable. Notifications regarding reservation confirmations and reminders are managed by the ESS service layer, keeping users informed throughout the process.
+- During the utilization and release phase, the real-time usage of reserved resources is tracked. The ESS service layer monitors utilization metrics, while the DLT core layer records all transactions and interactions, providing a transparent audit trail. Users are alerted to any performance issues, ensuring that resources are efficiently utilized and returned promptly.
+- Transaction management encompasses the secure processing of payments for reservations. The ESS service layer facilitates various payment methods, while the DLT core layer ensures that all financial transactions are securely logged and auditable. In case of disputes, transaction management provides mechanisms for resolution, promoting fairness and trust among users.
+- Finally, the ESS monitoring phase allows users to access real-time data and historical analytics regarding their energy storage utilization. The ESS service layer presents this information through user-friendly dashboards, while the DLT core layer ensures data integrity and security. Users receive alerts for any anomalies, enabling proactive management of their resources.
+
+### I.2 User management phase
+
+This phase is designed to ensure secure and efficient onboarding of participants and includes several key steps that facilitate user engagement, starting from initial registration where users provide essential personal and organizational information, to verification and authentication measures that safeguard their identities.
+
+This phase involves the following key steps:
+
+- **User registration:** Participants (EES providers, energy providers, etc.) complete the registration by providing personal and organizational details, selecting their role, and agreeing to the terms and conditions.
+- **Verification process:** Users undergo verifications to confirm their identity by email or phone number. Additional identity verification may be required for specific roles.
+- **Authentication setup:** Users create secure login credentials and have the option to enable multi-factor authentication for enhanced security.
+- **Role assignment:** Permissions are assigned based on the user's role, ensuring appropriate access to features and functionalities.
+- **Profile management:** Users can update their profile information and adjust security settings as needed.
+
+### I.3 ESS publication and discovery phase
+
+This phase is designed to facilitate the visibility and accessibility of ESS within a decentralized energy marketplace. It enables EES providers to publish their available resources, while consumers and other stakeholders can discover and evaluate these offerings based on their specific needs.
+
+This phase involves the following key steps:
+
+- **ESS publication:** EES providers submit details about their available information, including specifications, capacity, operational status, and pricing information for the listing. This information is securely recorded on the distributed ledger to ensure immutability and trust.
+- **Data validation:** It verifies the submitted information through consensus mechanisms inherent in the DLT system, ensuring accuracy and compliance with established standards, which enhances trust among users.
+- **Availability updates:** Providers can update the status and availability of their ESS in real-time, with these changes automatically reflected on-chain, allowing for dynamic responses to market demands and operational changes.
+- **ESS discovery:** Users can search and filter available ESS based on various criteria such as location, capacity, and pricing, facilitated by smart contracts that streamline the querying process.
+- **Matching and notifications:** Matching services may be offered to utilize smart contracts to notify users of relevant ESS based on their needs, enhancing the likelihood of successful transactions and collaborations.
+
+### I.4 ESS reservation and contracting phase
+
+This phase is designed to ensure that users can secure access to ESS in a reliable and transparent manner. It involves the formalization of agreements between EES providers and energy providers, facilitating the reservation of resources for specific time frames and conditions.
+
+This phase involves the following key steps:
+
+- **Reservation request:** Users initiate a reservation request for a specific ESS, indicating their desired time frame, capacity requirements, and any additional conditions. This request is recorded on-chain to ensure transparency and traceability.
+- **Smart contract creation:** Upon receiving a reservation request, a smart contract is automatically generated, outlining the terms of the agreement, including pricing, duration, and any service level agreements (SLAs). This contract is securely stored on-chain.
+
+- **Provider confirmation:** The EES provider reviews the reservation request and the associated smart contract. They can accept, reject, or propose modifications to the terms. This interaction is recorded on-chain, ensuring that all parties have access to the latest agreement details.
+- **Reservation confirmation:** The smart contract updates the reservation status and confirms the booking to the user. This confirmation is also recorded on-chain, providing an immutable record of the transaction.
+- **Monitoring and compliance:** During the reservation period, the smart contract can monitor compliance with the agreed terms, such as usage limits and maintenance requirements. Any deviations can trigger predefined actions, such as notifications or penalties, ensuring accountability.
+
+### I.5 ESS utilization and release phase
+
+This phase is designed to ensure that users can effectively utilize ESS during their reserved time and smoothly release the resources afterward. This phase involves monitoring actual usage, evaluating performance, and managing the release of resources, ensuring that all parties adhere to the agreed-upon terms while maintaining transparency.
+
+The phase includes the following key steps:
+
+- **Utilization monitoring:** During the user's utilization of the ESS, the usage of resources is continuously monitored. This includes tracking the amount of energy stored, the rates of discharge and charge, and whether the user adheres to the predefined usage conditions. Relevant data is recorded on-chain to ensure transparency and traceability.
+- **Performance evaluation:** Providers can assess the performance of the ESS based on the user's usage patterns and ensure that it meets the SLAs. If any issues or deviations are detected, providers can communicate with users promptly through a predefined notification.
+- **Completion notification:** Once the user has completed their usage of the ESS, a completion notification is automatically sent to both the user and the provider, which triggers the subsequent release process.
+- **Resource release:** After the user confirms the completion of usage, the ESS resources are automatically released with the availability status updated for other users to reserve. This process is also recorded on-chain to ensure transparency in all transactions.
+- **Settlement adjustment:** If there are any additional fees incurred during the usage (such as exceeding the reserved time or capacity limits), the smart contract automatically adjusts the payment amount based on the usage and handles the corresponding settlement, which would further be handled by the transaction management process. This process ensures fairness and transparency in billing.
+- **Data archiving:** Finally, all data related to the ESS usage will be archived for future analysis and auditing. This data can help optimize resource management and enhance user experience.
+
+### I.6 Transaction management phase
+
+This phase is designed to ensure that all transactions related to ESS reservations and utilization are processed accurately, securely, and transparently.
+
+The phase includes the following key steps:
+
+- **Transaction initiation:** It begins with the initiation of transactions by participants within the ESS. This initiation phase is critical for establishing clear terms and conditions that govern the transaction, including pricing, duration, and energy quantity.
+
+- **Smart contract deployment:** Once a transaction is initiated, a smart contract is deployed to automate the terms agreed upon by the parties involved. This smart contract encapsulates the rules and conditions of the transaction, ensuring that all stipulations are adhered to without the need for intermediaries. The deployment of the smart contract also enhances transparency, as all participants can view and verify the contract's terms on the distributed ledger.
+- **Transaction execution:** Following the deployment of the smart contract, the transaction is executed automatically based on the predefined conditions. This execution process involves the transfer of energy credits or assets between participants, facilitated by the smart contract. This step ensures that all transactions are executed in real-time, minimizing delays and enhancing operational efficiency.
+- **Verification and validation:** After execution, the step verifies and validates the transaction to ensure compliance with the agreed-upon terms. This step includes confirming that the energy transferred meets the SLAs specified in the smart contract. Any discrepancies or issues identified during this verification phase are flagged for review, ensuring that all transactions are accurate and trustworthy.
+- **Transaction recording:** All executed transactions are recorded on the distributed ledger, creating an immutable audit trail that can be referenced by all the stakeholders. This recording process enhances accountability and allows for easy tracking of transaction history. Participants can access this information to review past transactions, ensuring transparency and trust.
+- **Dispute resolution:** In cases where disputes arise regarding transaction execution or compliance with smart contract terms, the step provides a structured dispute resolution mechanism. This mechanism allows stakeholders to submit claims or issues for review, facilitating a fair and efficient resolution process. The transparent nature of the distributed ledger supports this process by providing verifiable evidence of all transactions.
+
+### I.7 ESS monitoring phase
+
+This phase is designed to ensure the efficient operation, safety, and performance of the ESS throughout their lifecycle. This phase involves continuous oversight of the ESS to optimize usage, detect anomalies, and ensure compliance with operational standards.
+
+The phase includes the following key steps:
+
+- **Data collection:** The ESS monitoring begins with the continuous collection of real-time data from sensors and Internet of things (IoT) devices, capturing various metrics such as energy levels, usage rates, charge and discharge cycles, and overall system health indicators. This data is integrated into a secure distributed ledger, ensuring that all information is immutable and tamper-proof, which allows for a comprehensive view that combines real-time data with historical transaction records.
+- **Performance analysis:** Next, this step performs performance analysis by calculating key performance indicators (KPIs) related to the ESS, such as efficiency, utilization rates, and availability. These metrics enable stakeholders to assess the performance of the energy storage resources effectively. At the same time, advanced algorithms such as machine learning techniques are recommended to be employed for anomaly detection and identifying unusual patterns or deviations in the data that may indicate operational issues.
+- **User dashboard:** This dashboard presents real-time information in an easily interpretable format, allowing users to monitor the status of the ESS at a glance. Additionally, automated reports are generated to summarize trends and performance evaluations over specified periods, facilitating informed decision-making.
+
+- **Real-time alerts:** Real-time alerts are generated automatically whenever deviations from expected performance or contractual obligations are detected. These alerts ensure that stakeholders are promptly informed of any critical issues, allowing for immediate intervention if necessary.
+- **Compliance monitoring:** Compliance with the terms of smart contracts is continuously monitored, creating an audit trail that can be referenced in case of disputes. This feature enhances trust among stakeholders, as it ensures that all actions and transactions are recorded transparently. In the event of a disagreement, this step provides the necessary documentation to support resolution efforts.
+
+## Bibliography
+
+- [b-ITU-T X.1400] Recommendation ITU-T X.1400 (2020), *Terms and definitions for distributed ledger technology*.
+- [b-ITU-T Y.2072] Recommendation ITU-T Y.2072 (2018), *Framework for an energy-sharing and trading platform*.
+- [b-IEC 62933-1] IEC 62933-1:2024, *Electrical energy storage (EES) systems – Part 1: Vocabulary*.  
+<<https://webstore.iec.ch/en/publication/64642>>
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.751.27-202503-I_PDF-E/raw.md b/marked/F/T-REC-F.751.27-202503-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..24eaf68fa8ff7cd65f004d6d5ed89234e37653fb
--- /dev/null
+++ b/marked/F/T-REC-F.751.27-202503-I_PDF-E/raw.md
@@ -0,0 +1,418 @@
+
+
+# Recommendation
+
+## **ITU-T F.751.27 (03/2025)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+## --- **Framework for distributed ledger technology-based multimedia data asset service**
+
+![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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.751.27
+
+## Framework for distributed ledger technology-based multimedia data asset service
+
+## Summary
+
+Recommendation ITU-T F.751.27 specifies a framework, and functional and security requirements for distributed ledger technology (DLT)-based multimedia data asset service to support multimedia data asset generation, purchase, trade and transfer in a trusted manner. This Recommendation can be used as guidance by the relevant parties to research, develop, test, deploy and manage the distributed ledger technology-based multimedia data asset services.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.751.27 | 2025-03-16 | 21          | 11.1002/1000/16260 |
+
+## Keywords
+
+DLT, framework, multimedia data asset service, requirement.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <https://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                           | 2    |
+| 6 Framework for DLT based multimedia data asset service ..... | 2    |
+| 6.1 Overview .....                                            | 2    |
+| 6.2 Infrastructure layer .....                                | 3    |
+| 6.3 Data asset DLT layer .....                                | 3    |
+| 7 Functional requirements .....                               | 4    |
+| 7.1 Functional requirements of the infrastructure layer ..... | 4    |
+| 7.2 Functional requirements of the data asset DLT layer.....  | 4    |
+| 8 Security requirements .....                                 | 6    |
+| 8.1 Identity authentication requirements .....                | 6    |
+| 8.2 Data security requirements .....                          | 6    |
+| 8.3 Privacy protection requirements.....                      | 7    |
+| Bibliography.....                                             | 8    |
+
+
+
+# Recommendation ITU-T F.751.27
+
+## Framework for distributed ledger technology-based multimedia data asset service
+
+# 1 Scope
+
+This Recommendation specifies a framework and functional and security requirements for distributed ledger technology (DLT)-based multimedia data asset service to support multimedia data asset generation, purchase, trade and transfer in a trusted manner. This Recommendation can be used as guidance by the relevant parties to develop, test, deploy and manage the distributed ledger technology-based multimedia data asset 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 asset** [b-ITU-T F.751.0]: A representation of value. It can be a diamond, a unit of currency, items inside a shipping container, etc. An asset can be physical or virtual.
+
+**3.1.2 blockchain** [b-ITU-T F.751.0]: A type of distributed ledger that is composed of digitally recorded data arranged as a successively growing chain of blocks with each block cryptographically linked and hardened against tampering and revision.
+
+**3.1.3 consensus** [b-ITU-T F.751.0]: Agreement that a set of transactions is valid.
+
+**3.1.4 data asset** [b-ITU-T X.1750]: An electronically recorded data resource, owned or controlled by an organization.
+
+**3.1.5 distributed ledger** [b-ITU-T F.751.0]: A type of ledger that is shared, replicated, and synchronized in a distributed and decentralized manner.
+
+NOTE – Originally published in [b-ITU-T TS FG DLT D1.1].
+
+**3.1.6 distributed ledger technology (DLT)** [b-ITU-T F.751.1]: Technology enabling large groups of nodes in distributed ledger networks to reach agreement and record information without the need for a central authority.
+
+**3.1.7 entity** [b-ITU-T F.751.0]: Anything that has a separately identifiable existence (e.g., organization, person, group, smart contract or device). An entity uses distributed ledger technology to solve the problem of its business or information systems.
+
+NOTE – Adapted from [b-ITU-T X.1215].
+
+**3.1.8 ledger** [b-ITU-T F.751.0]: Information store that keeps final and definitive (immutable) records of transactions.
+
+NOTE – Originally published in [b-ITU-T TS FG DLT D1.1].
+
+**3.1.9 node** [b-ITU-T F.751.0]: Device or process that participates in a distributed ledger network.
+
+NOTE 1 – Nodes can store a complete or partial replica of the distributed ledger.
+
+NOTE 2 – Originally published in [b-ITU-T TS FG DLT D1.1].
+
+**3.1.10 smart contract** [b-ITU-T F.751.0]: Program written on the distributed ledger system that encodes the rules for specific types of distributed ledger system transactions in a way that can be validated, and triggered by specific conditions.
+
+NOTE – Adapted from [b-ITU-T TS FG DLT D1.1].
+
+**3.1.11 transaction** [b-ITU-T F.751.0]: An incident or an operation that leads to a change in the status of a ledger, such as adding a record or equivalent exchange based on currency.
+
+## 3.2 Terms defined in this Recommendation
+
+None.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|     |                                       |
+|-----|---------------------------------------|
+| API | Application Programming Interface     |
+| DAO | Decentralized Autonomous Organization |
+| DAS | Data Asset Service                    |
+| DLT | Distributed Ledger Technology         |
+| IoT | Internet of Things                    |
+| NFT | Non-Fungible Token                    |
+| P2P | Peer to Peer                          |
+
+# 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.
+
+# 6 Framework for DLT based multimedia data asset service
+
+## 6.1 Overview
+
+Multimedia data asset is a vast collection of digital information, including images, audio, video, and textual data which includes the right to use it. Multimedia data asset service supports multimedia data asset generation, purchase, trade and transfer in a trusted manner and protects its right of access. The framework of a distributed ledger technology (DLT)-based multimedia data asset service is shown in Figure 1.
+
+![Figure 1 – Framework for DLT-based multimedia data asset service. The diagram shows two layers: the Infrastructure layer at the bottom and the Data asset DLT layer above it. The Data asset DLT layer contains six modules: Unified API module, Service module, Management module, Smart contract module, Core node module, and Cross-chain module. The Service module is divided into Data asset service and Repository service. The Core node module is divided into Consensus and Distributed ledger components. The Cross-chain module includes Relay, Identity, Storage, Proxy, and Authorization components. The Infrastructure layer includes Cloud platform, Public/Private network, IoT device, and Special chips.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg)
+
+|                      |                        |                     |                         |                                     |
+|----------------------|------------------------|---------------------|-------------------------|-------------------------------------|
+| Data asset DLT layer | Unified API module     |                     |                         |                                     |
+|                      | Service module         |                     |                         |                                     |
+|                      | Data asset service     |                     | Repository service      |                                     |
+|                      | Minting                | Browsing            | Asset storage           | Copyright confirmation registration |
+|                      | Issuance               | Transfer            | Chain operation         | Copyright tracking and monitoring   |
+|                      | Display                | Trade               | User account management | Copyright authorization record      |
+|                      | Management module      |                     |                         |                                     |
+|                      | Union management       | Node management     | Cross-chain management  | Identity management                 |
+|                      | Contract management    | DAO management      |                         |                                     |
+|                      | Smart contract module  |                     |                         |                                     |
+|                      | Identity contract      | Data asset contract | NFT contract            | Copyright contract                  |
+|                      | Core node module       |                     | Cross-chain module      |                                     |
+|                      | Consensus              | Distributed ledger  | Relay                   | Identity                            |
+|                      | P2P network            | Contract            | Storage                 | Proxy                               |
+|                      | Cryptography           |                     | Authorization           |                                     |
+| Infrastructure layer | Cloud platform         |                     |                         |                                     |
+|                      | Public/Private network | IoT device          | Special chips           |                                     |
+
+Figure 1 – Framework for DLT-based multimedia data asset service. The diagram shows two layers: the Infrastructure layer at the bottom and the Data asset DLT layer above it. The Data asset DLT layer contains six modules: Unified API module, Service module, Management module, Smart contract module, Core node module, and Cross-chain module. The Service module is divided into Data asset service and Repository service. The Core node module is divided into Consensus and Distributed ledger components. The Cross-chain module includes Relay, Identity, Storage, Proxy, and Authorization components. The Infrastructure layer includes Cloud platform, Public/Private network, IoT device, and Special chips.
+
+F.751.27(25)
+
+**Figure 1 – Framework for DLT-based multimedia data asset service**
+
+The framework of a DLT-based multimedia data asset service includes the infrastructure layer and data asset DLT layer. The data asset DLT layer contains the following six modules: core node module, cross-chain module, smart contract module, management module, service module and unified application programming interface (API) module.
+
+## 6.2 Infrastructure layer
+
+The infrastructure layer is the physical layer which can be a physical infrastructure with chips, the Internet of things (IoT) devices, the private/public network or a cloud platform.
+
+## 6.3 Data asset DLT layer
+
+The data asset DLT layer is a permissioned DLT system which provides support to perform different actions for data asset service including issuing, purchase, auction, trade, and transfer.
+
+The data asset DLT layer contains the following six modules: core node module, cross-chain module, smart contract module, management module, service module, and unified API module.
+
+### 6.3.1 Core node module
+
+The core node module provides DLT services, including consensus component, distributed ledger component, cryptographic component, peer to peer (P2P) network component, and contract management component. These components cooperate with each other to ensure that each node in the DLT network forms a consensus for the transactions, thereby ensuring the consistency of data across different nodes.
+
+### **6.3.2 Cross-chain module**
+
+The cross-chain module provides interoperability functions with different DLT networks by cooperating with the five components. The cross-chain module contains five components: relay component, identity component, router component, proxy component, authorization component. These components cooperate with each other to ensure the consistency of transactions from one DLT network to another DLT network.
+
+#### **6.3.3 Smart contract module**
+
+The smart contract module provides smart contract functions. It includes the following component: identify contract, data asset contract, non-fungible token (NFT) contract, copyright contracts and decentralized autonomous organization (DAO) management contracts.
+
+#### **6.3.4 Management module**
+
+The management module provides APIs used by the upper layer and manages different nodes to support contracts working as expected. It includes node management, union management, cross-chain management, identity management, contract management and DAO management.
+
+#### **6.3.5 Service module**
+
+The service module includes DLT-based data asset service and repository service. Both services provide APIs for users to manage their data asset and obtain digital rights for data asset. The platform administrator can build connections with other organizations or with other DLT systems.
+
+DLT-based data asset service is deployed in the server backend to provide functions including minting, issuance, display, browsing, transfer and trade of data asset. It also provides the functions of asset storage, chain operation, and user account management.
+
+Repository service is deployed in the server backend to provide functions including copyright confirmation registration, copyright tracking and monitoring, copyright authorization record and online rights.
+
+#### **6.3.6 Unified API module**
+
+The unified API module provides supply interface which provides management capability and application capability in the data asset node.
+
+# **7 Functional requirements**
+
+### **7.1 Functional requirements of the infrastructure layer**
+
+- a) It is required to support the deployment on cloud platform, IoT device in public and private networks;
+- b) It is recommended to support trusted execution environment capability.
+
+### **7.2 Functional requirements of the data asset DLT layer**
+
+#### **7.2.1 General functional requirements of the data asset DLT layer**
+
+- a) It is required to support quick creation and deletion of data asset DLT, joining and exiting of organizations and nodes, changing approvals of data asset DLT, data application, data approval, cross-system data application;
+- b) It is required to support one-click contract deployment, contract deletion, freezing and unfreezing, contract version management, contract integrated development environment, multi-language contract governance, contract security formal scanning and verification, contract runtime visualization, contract sharing, contract review and release and contract code to visual component generation;
+
+- c) It is required to support the management of data assets, wallet accounts, tokens and NFT;
+- d) It is required to support queries of block status, historical transaction queries, advanced transaction queries aggregated in multiple dimensions including time and organization, multi-functional data analysis, indexing and retrieval of chain data, report generation and display, on-chain and off-chain data orchestration, transaction rate and visual analysis;
+- e) It is required to support unified audit logs, sensitive word notification, anti-money laundering, and compliance checks;
+- f) It is required to support data asset casting, transferring, and data asset transactions, and support copyright storage services.
+
+#### **7.2.2 Functional requirements of core node module**
+
+- a) It is required to support different consensus algorithms, including practical byzantine fault tolerance (PBFT), replication and fault tolerant (Raft);
+- b) It is recommended to support the switch between different consensus algorithms;
+- c) It is required to use distributed ledger, smart contract, consensus P2P network and cryptography to build the infrastructure of the core node.
+
+#### **7.2.3 Functional requirements of cross-chain module**
+
+- a) It is required the data asset node to support cross-chain capability for transferring data across different chains;
+- b) It is recommended to support relay, identity, proxy, authorization and storage functions in cross-chain infrastructure;
+- c) It is recommended to integrate the core node certificate together with the cross-chain module.
+
+#### **7.2.4 Functional requirements of smart contract module**
+
+- a) It is required to provide verification based on digital identity contract with regard to the user identity of the data asset;
+- b) It is required to provide data asset management contracts during the full life cycle management of data assets;
+- c) It is required to support NFT contracts;
+- d) It is required to provide copyright protection contracts to meet the needs of data asset copyright confirmation;
+- e) It is required that smart contract management supports one-click deployment, contract deletion, freezing and unfreezing of contracts;
+- f) It is required to provide smart contract version management;
+- g) It is required that contract integrated development environment including development, online debugging and compilation;
+- h) It is required to support multilingual contract governance.
+
+#### **7.2.5 Functional requirements of management module**
+
+- a) It is required to support unified O&M monitoring, including the query of the running status, CPU usage, memory usage, and upstream and downstream rates of the confederation/node;
+- b) It is required to support on-chain service analysis, contract resource monitoring, application resource monitoring, alarm logs, alarm viewing, and run logs;
+- c) It is required to support union management capability for organizing different data asset node in one union and monitor the union node status;
+- d) It is required to support node management ability for managing data asset, and it is required not to support creating, modifying or deleting operations;
+
+- e) It is required to support node scale-out and scale-in, and support node starting and stopping;
+- f) It is required to support status monitoring of consensus and computing nodes, node running data, and node information obtaining (including the address, port, and domain name);
+- g) It is required to support alliance management, including fast alliance creation, chain core selection, and admission and exit of alliance chain members;
+- h) It is required to supports visualized display of the alliance, including the alliance status, alliance topology, bottom-layer chain distribution statistics, and cross-chain service analysis statistics;
+- i) It is required to provide metadata and multimedia data storage, and store media data on the chain using a hash;
+- j) It is required that data asset storage uses specific data asset service API and provides compliance verification for chain user identity and data asset content.
+
+#### **7.2.6 Functional requirements of service module**
+
+- a) It is required to support the transfer, minting, transaction, issuance, storage, and display of data assets for the data asset service component;
+- b) It is required that data asset service provides specific API for customers to call, through smart contract in the data asset DLT for the data asset service the data asset service component;
+- c) It is required to support copyright confirmation registration, copyright tracking and monitoring of data assets, as well as online rights confirmation and copyright authentication record for the repository service component.
+
+#### **7.2.7 Functional requirements of unified API module**
+
+- a) It is required to use authentication for each API and TLS for communication protection;
+- b) It is recommended to utilize both remote procedure call (RPC) and representational state transfer (REST) APIs for the interface.
+
+# **8 Security requirements**
+
+## **8.1 Identity authentication requirements**
+
+- a) It is required to protect personal identity information, support the independent authorization and secure storage of personal information, and support the independent and controllable processing of personal information in the minimum manner, minimum scope, and minimum time;
+- b) It is required that natural persons are notified of identity access, update, revocation, and freezing/unfreezing;
+- c) It is required that all user identities are authenticated in the DLT-based data asset service process;
+- d) It is required that the identity verification process supports the minimum disclosure of personal information;
+- e) It is required to provide service interfaces to support digital identity interoperability between multiple service systems;
+- f) It is required to provide support for identity authentication for digital identity holders in different scenarios.
+
+## **8.2 Data security requirements**
+
+- a) It is recommended to provide trusted hardware environment;
+
+- b) It is required to keep the data consistency in different data asset nodes for the DLT-based data asset service (DAS);
+- c) It is required to adopt verification technology or cryptographic technology to ensure the integrity and confidentiality during the transmission of important data asset.
+
+## **8.3 Privacy protection requirements**
+
+- a) It is required to use security isolation, password protection, access control, and disaster recovery backup for protecting personal information and ensuring the confidentiality, integrity, and availability of important data asset;
+- b) It is required to provide effective protection measures for ensuring the confidentiality, integrity, and availability of identity information throughout the life cycle of identity which includes identity issuance, holding, circulation and verification.
+
+#### **8.3.1 System security requirements**
+
+- a) It is required to meet the needs of peak access, provide necessary redundancy, and meet system availability;
+- b) It is required to support the capability of docking multiple nodes to store relevant digital data asset and the capability of cross-chain. The on-chain data is operated by the contract, and the right permission is restricted to specific users and nodes for operation and maintenance;
+- c) It is required to record all information about attacks, reports alarms in a timely manner, and retain evidences.
+
+#### **8.3.2 On-chain Content security requirements**
+
+- a) It is required that data assets are bound by smart contract for on-chain content, and fully explain the service interface defined by smart contracts to users;
+- b) It is required to generate certificates for metadata and media files, complying with NFT protocols;
+- c) It is required to review the content that violates the current national laws and regulations, and prohibit the illegal content from being on-chain;
+- d) It is required to clarify the data asset subject according to copyright and other laws and regulations, and to confirm the information including the issuer, authorization certificate, period, scope, and authorized party.
+
+## Bibliography
+
+- [b-ITU-T F.751.0] Recommendation ITU-T F.751.0 (2020), *Requirements for distributed ledger systems.*
+- [b-ITU-T F.751.1] Recommendation ITU-T F.751.1 (2020), *Assessment criteria for distributed ledger technology platforms.*
+- [b-ITU-T X.1215] Recommendation ITU-T X.1215 (2019), *Use cases for structured threat information expression.*
+- [b-ITU-T X.1750] Recommendation ITU-T X.1750 (2020), *Guidelines on security of big data as a service for big data service providers.*
+- [b-I-ITU-T TS FG DLT D1.1] Technical Specification ITU-T Focus Group on Application of Distributed Ledger Technology (FG DLT D1.1) (2019), *Distributed ledger technology 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.751.28-202512-I_PDF-E/raw.md b/marked/F/T-REC-F.751.28-202512-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..862b876ea3e8f29fe04a316d8451996f9fbbc9bb
--- /dev/null
+++ b/marked/F/T-REC-F.751.28-202512-I_PDF-E/raw.md
@@ -0,0 +1,931 @@
+
+
+Recommendation
+
+**ITU-T F.751.28 (12/2025)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+---
+
+**Framework for fast message delivery for  
+distributed ledger technology (DLT)-based  
+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 globe with white grid lines and a stylized 'ITU' text in blue, with a white lightning bolt symbol integrated into the letter 'U'.
+
+ITU logo
+
+# ITU-T F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.751.28
+
+# Framework for fast message delivery for distributed ledger technology (DLT)-based services
+
+## Summary
+
+To enable fast message exchange in peer-to-peer (P2P) networks for distributed ledger technology (DLT)-based services, Recommendation ITU-T F.751.28 specifies a framework and functional modules for fast DLT message delivery in the DLT network. The functional modules include a DLT interface client module, a committee management module, a network monitoring and management module, a block data/control message transmission module, and a consensus network module.
+
+## History\*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.751.28 | 2025-12-14 | 21          | 11.1002/1000/16599 |
+
+## Keywords
+
+Distributed ledger technology, fast DLT message delivery.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <https://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                             | 1    |
+| 4 Abbreviations and acronyms .....                                         | 2    |
+| 5 Conventions .....                                                        | 2    |
+| 6 Framework for fast DLT message delivery for DLT-based services .....     | 2    |
+| 7 Functional modules and requirements of the framework .....               | 4    |
+| 7.1 DLT interface client module .....                                      | 4    |
+| 7.2 Committee management module .....                                      | 5    |
+| 7.3 Network monitoring and management module .....                         | 6    |
+| 7.4 Block data and control message transmission module .....               | 8    |
+| 7.5 Consensus network module .....                                         | 9    |
+| Annex A – Multi-path management.....                                       | 11   |
+| Annex B – Block data structure .....                                       | 13   |
+| Annex C – Control message formats .....                                    | 14   |
+| Annex D – Leader node selection procedure .....                            | 15   |
+| Annex E – Consensus procedure .....                                        | 17   |
+| Appendix I – A delay-based 3D coordinate system estimation procedure ..... | 20   |
+| Bibliography.....                                                          | 24   |
+
+
+
+# Recommendation ITU-T F.751.28
+
+## Framework for fast message delivery for distributed ledger technology (DLT)-based services
+
+# 1 Scope
+
+This Recommendation specifies a framework for fast DLT message delivery for distributed ledger technology (DLT)-based services. It includes the following:
+
+- The framework for fast DLT message delivery for DLT-based services;
+- Functional modules including a DLT interface client module, a committee management module, a network monitoring and management module, a block data/control message transmission module, and a consensus network module for fast DLT message delivery.
+
+# 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.751.0](#)] Recommendation ITU-T F.751.0 (2020), *Requirements for distributed ledger systems*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 block** [b-ITU-T F.751.1]: Individual data unit of a blockchain, composed of a collection of transactions and a block header.
+
+**3.1.2 distributed ledger** [ITU-T F.751.0]: A type of ledger that is shared, replicated, and synchronized in a distributed and decentralized manner.
+
+**3.1.3 distributed ledger system** [ITU-T F.751.0]: A system that implements a distributed ledger.
+
+**3.1.4 P2P** [ITU-T F.751.0]: An instantiation of network architectures where all peers have equivalent authority and responsibility, differing completely from that of server and client system.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 fast distributed ledger technology message delivery**: The transmission of distributed ledger technology (DLT) messages with minimal latency and high throughput by utilizing real-time network monitoring for optimal path selection, multi-path routing and reduced control messages.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+BD Block Data
+
+|      |                                |
+|------|--------------------------------|
+| BFT  | Byzantine Fault Tolerance      |
+| CM   | Control Message                |
+| DLT  | Distributed Ledger Technology  |
+| DSP  | DLT Service Provider           |
+| FEC  | Forward Error Correction       |
+| IP   | Internet Protocol              |
+| MP2  | Multi-Path and Multi-Peer      |
+| P2P  | Peer-to-Peer                   |
+| QoS  | Quality of Services            |
+| QUIC | Quick UDP Internet Connections |
+| RPC  | Remote Procedure Call          |
+| RTT  | Round Trip Time                |
+| TPS  | Transactions Per Second        |
+| VRF  | Verifiable Random Function     |
+
+# 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.
+
+# 6 Framework for fast DLT message delivery for DLT-based services
+
+Distributed ledger technology (DLT)-based services can be provided using peer-to-peer (P2P) networks. The P2P network may be occupied by other services that hinder fast service provision. Moreover, the available bandwidth for a particular P2P link in the network is needed to support real-time application-oriented or on-demand content delivery services. Therefore, the real-time information for a P2P link including the available bandwidth should be monitored continuously. The optimized routing path between two remote peers can be obtained if the real-time monitored information is available for each P2P link among the used links, by avoiding the busy and unreliable P2P links.
+
+The existing P2P-oriented DLT services could be enhanced by defining a new framework for fast DLT message delivery. The P2P network can be composed of different types of networks, e.g., tree-based networks and mesh-based networks. DLT is used to ensure secure transactions among nodes, and the P2P network can be used for message transfer among trustworthy nodes by using overlay networks. In this situation, it is critical to find the optimal path between peers in the overlay network to quickly exchange DLT messages .
+
+Figure 1 shows the overall framework for fast DLT message delivery for DLT-based services. The framework comprises six functional modules, including a DLT interface client module, a committee management module, a network monitoring and a management module, a block data/control message transmission module, and a consensus network module.
+
+![Figure 1: Framework for fast DLT message delivery for DLT-based services. The diagram shows a stack of modules. On the left, from top to bottom: Committee management module, DLT interface client module, and DLT platform (dashed box). On the right, from top to bottom: Network monitoring and management module, Block data/Control message transmission module, and Consensus network module. Lines connect the Committee management module to the other three modules on the right. The DLT interface client module connects to the DLT platform and the Network monitoring and management module. The Network monitoring and management module connects to the Block data/Control message transmission module and the Consensus network module. A legend at the bottom left shows a dashed box labeled 'Out of the scope of this Recommendation'. The text 'F.751.28(25)' is in the bottom right.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg)
+
+Figure 1: Framework for fast DLT message delivery for DLT-based services. The diagram shows a stack of modules. On the left, from top to bottom: Committee management module, DLT interface client module, and DLT platform (dashed box). On the right, from top to bottom: Network monitoring and management module, Block data/Control message transmission module, and Consensus network module. Lines connect the Committee management module to the other three modules on the right. The DLT interface client module connects to the DLT platform and the Network monitoring and management module. The Network monitoring and management module connects to the Block data/Control message transmission module and the Consensus network module. A legend at the bottom left shows a dashed box labeled 'Out of the scope of this Recommendation'. The text 'F.751.28(25)' is in the bottom right.
+
+**Figure 1 – Framework for fast DLT message delivery for DLT-based services**
+
+- The **DLT interface client module** serves as an interface that ensures compatibility with various DLT platforms.
+- The **committee management module** selects and verifies committees that will participate in the audit chain and consensus process. The committee management module communicates with the DLT interface client module, the network monitoring and management module, and the consensus network module to provide a committee list comprising the committee Internet protocol (IP) addresses and public keys over the network.
+- The **network monitoring and management module** monitors the network in real-time and maintains a table to determine the optimal path between the source and destination nodes, considering factors such as available bandwidth and transmission delay. This module employs a delay-based 3D coordinate system to estimate end-to-end delay values among nodes and constructs a hybrid tree/mesh network topology to improve DLT quality of service (QoS) and scalability. Additionally, control messages within this module are managed by a dedicated control message generation/decoding subfunction.
+- The **block data (BD)/control message (CM) transmission module** is responsible for handling BD/CM generation and transmission among nodes in a DLT network. It includes functions such as the BD/CM transceiver function and the multi-peer and multi-path (MP2) DLT transmission function. The BD/CM transceiver function manages the transmission and reception of BD/CM while the message forwarding table assists in directing messages to their intended recipients within the network.
+- The **consensus network module** ensures decentralized agreement on the ledger state among participating nodes by performing a consensus mechanism for DLT-based services. It includes an audit chain function that comprises two subfunctions: DLT service provider (DSP) subfunction offering DLT services, and auditor subfunction featuring  $O(N)$  audit chain consensus for managing audit tasks.
+- The **DLT platform** is a type of DLT system, which is out of the scope of this Recommendation.
+
+The relationship between the functional modules of the framework is summarized below.
+
+- The DLT interface client module is responsible for ensuring seamless interaction with various DLT platforms and enabling the network monitoring and management module to function across different DLT environments.
+- The committee management module is responsible for selecting and verifying committees that participate in the consensus processes, and it provides the consensus network module with the necessary committee information.
+
+- The network monitoring and management module continuously observes network conditions to optimize communication paths and improve QoS and scalability. The block data (BD)/control message (CM) transmission module handles the generation, transmission, and reception of BD/CM using the information provided by the network monitoring and management module.
+- Finally, the consensus network module ensures fast agreement among participating nodes via the optimal path identified by the network monitoring and management module.
+
+# 7 Functional modules and requirements of the framework
+
+The following clauses describe the details of the functional modules and requirements of the framework for fast DLT message delivery for DLT-based services.
+
+## 7.1 DLT interface client module
+
+The DLT interface client module serves as an interface that ensures compatibility with various DLT platforms. As shown in Figure 2, this module is composed of remote procedure call (RPC) client function, Pub/Sub subscriber function, verifiable random function (VRF) executor function, metric exporter function, VRF key management function, aggregated signature generator function, block generator function, and requirement analysis function.
+
+![](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg)
+
+DLT interface client module
+
+|                             |                                         |
+|-----------------------------|-----------------------------------------|
+| RPC client function         | Pub/Sub subscriber function             |
+| VRF executor function       | Metric exporter function                |
+| VRF key management function | Aggregated signature generator function |
+| Block generator function    | Requirement analysis function           |
+
+F.751.28(25)
+
+**Figure 2 – DLT interface client module**
+
+### 7.1.1 RPC client function
+
+The RPC client function is required to support communication between the DLT interface client module and other modules using RPC.
+
+### 7.1.2 Pub/Sub subscriber function
+
+The Pub/Sub subscriber function is recommended for subscribing to a publish-subscribe messaging system, allowing the DLT interface client module to receive notifications and updates.
+
+### 7.1.3 VRF executor function
+
+The VRF executor function is required to support the cryptography used to generate random values in a verifiable manner. This function executes VRF operations required for certain cryptographic operations within the DLT system.
+
+### 7.1.4 Metric exporter function
+
+The metric exporter function is required to collect and export metrics or performance data related to the operations of the DLT interface client module.
+
+### 7.1.5 VRF key management function
+
+The VRF key management function is required to manage the keys required for VRF operations, including key generation, storage, and retrieval, ensuring the security of VRF-related cryptographic operations.
+
+### 7.1.6 Aggregated signature generator function
+
+The aggregated signature generator function is required to generate aggregated signatures, which are cryptographic constructs used for collectively signing data by multiple parties. This function facilitates secure and efficient signature generation within the DLT network.
+
+### 7.1.7 Block generator function
+
+The block generator function is required to create new blocks in the DLT network. This function assembles transactions and other relevant data into blocks and adds them to the DLT network, ensuring the integrity and immutability of the distributed ledger as proposed in [ITU-T F.751.0].
+
+### 7.1.8 Requirement analysis function
+
+The requirement analysis function is required to ensure that the DLT client node meets specified requirements in the DLT network. More specifically, these requirements may include transaction occurrence rates or minimum transactions per second (TPS) thresholds that every DLT network must support. To verify the suitability of a new node joining the network, the node provides its node ID and public key as input. The requirement analysis function then verifies the output result to assess the node's compatibility with the existing network and returns the verification result.
+
+## 7.2 Committee management module
+
+The committee management module is responsible for selecting and verifying committees that will participate in the consensus process. As shown in Figure 3, this module is comprised of peer information management function, committee selection message handler function, RPC server function, and Pub/Sub function.
+
+![Diagram of the Committee management module showing four sub-functions: Peer information management function, Committee selection message handler function, RPC server function, and Pub/Sub function.](18442e4e239480f0c3c95b547aa8fde2_img.jpg)
+
+The diagram illustrates the internal structure of the Committee management module. It is a rectangular box containing four smaller rectangular boxes arranged in a 2x2 grid. The top-left box is labeled 'Peer information management function'. The top-right box is labeled 'Committee selection message handler function'. The bottom-left box is labeled 'RPC server function'. The bottom-right box is labeled 'Pub/Sub function'.
+
+Diagram of the Committee management module showing four sub-functions: Peer information management function, Committee selection message handler function, RPC server function, and Pub/Sub function.
+
+F.751.28(25)
+
+Figure 3 – Committee management module
+
+### 7.2.1 Peer information management function
+
+The peer information management function is required to store and update peer information including IP addresses.
+
+### 7.2.2 Committee selection message handler function
+
+The committee selection message handler function is required to handle messages for committee selection within the DLT network.
+
+### 7.2.3 RPC server function
+
+The RPC server function is required to communicate between the committee management module and other modules.
+
+### 7.2.4 Pub/Sub function
+
+The Pub/Sub function is recommended and responsible for message publishing and subscription.
+
+## 7.3 Network monitoring and management module
+
+The network monitoring and management module plays a vital role in the dynamic and complex network. This module is used for fast block transmission in the DLT network. Fast block transmission in the DLT network depends on several characteristics of the network, e.g., the available bandwidth of the P2P link, transmission delay, and the processing capability of a peer node. Figure 4 shows the functional representation of the network monitoring and management module, and the detailed description of each function is as follows.
+
+![Functional representation of the network monitoring and management module diagram](1439cb942d9e363bbb3161b5540dd8c6_img.jpg)
+
+The diagram illustrates the functional representation of the network monitoring and management module. It is a hierarchical structure with a main box at the top labeled "Network monitoring and management module". Inside this box, there are two side-by-side boxes: "DLT interface client function" on the left and "Network monitoring function" on the right. Below these two boxes is a large box labeled "Hybrid tree/Mesh network topology management function". Inside this box, there are four stacked boxes: "Effective bandwidth/The number of supportable child nodes calculation subfunction", "Clustering and cluster leader selection subfunction", "Overlay multicast tree/Mesh construction subfunction", and "Control message generation/Decoding subfunction". Below the "Hybrid tree/Mesh network topology management function" box is another box labeled "Multi-path and multi-peer (MP2) DLT transmission function".
+
+F.751.28(25)
+
+Functional representation of the network monitoring and management module diagram
+
+**Figure 4 – Network monitoring and management module**
+
+### 7.3.1 DLT interface client function
+
+The DLT interface client function is required to verify the suitability of the peer node, ensuring that it possesses the necessary processing capabilities to be a part of the network. Once confirmed, the node can become a participant in the DLT network.
+
+### 7.3.2 Network monitoring function
+
+The network monitoring function is required to operate in a real-time manner. The overhead of the network monitoring is  $O(N)$  where  $N$  represents the total number of available nodes in the network. A delay-based 3D coordinate system estimates the end-to-end delay values among all participating nodes with  $O(N)$  message overhead. Each node is placed in the 3D coordinate system, whereby the Euclidean distance between two nodes in the 3D vector space denotes the delay value.
+
+### 7.3.3 Hybrid tree/mesh network topology management function
+
+The hybrid tree/mesh network topology management function is required to include subfunctions for effective bandwidth and the number of supportable child nodes calculation, clustering and cluster leader selection, overlay multicast tree/mesh construction, and control message generation/decoding.
+
+#### 7.3.3.1 Effective bandwidth and the number of supportable child nodes calculation subfunction
+
+The effective bandwidth and the number of supportable child nodes calculation subfunction is required to construct a hybrid tree/mesh network topology. To support the desired QoS and scalability in the DLT network, the effective bandwidth is calculated by considering the transaction rate, the
+
+number of transactions in a block, and block transmission success probability. The number of supportable child nodes is calculated by dividing the upload bandwidth by the estimated effective bandwidth.
+
+#### **7.3.3.2 Clustering and cluster leader selection subfunction**
+
+The clustering and cluster leader selection subfunction is required to perform clustering and cluster leader selection. For this purpose, the end-to-end delay information among all participating nodes is used. Cluster leader nodes are then selected according to network delay, node reliability, and available bandwidth.
+
+#### **7.3.3.3 Overlay multicast tree/mesh construction subfunction**
+
+The overlay multicast tree/mesh construction subfunction is required to group cluster leader nodes by employing a shortest path mechanism to establish efficient paths, considering the number of nodes in each cluster to minimize average block propagation delay. Within each cluster, paths are constructed based on the Dijkstra's algorithm to ensure optimal intra-cluster connectivity. After the multicast tree is formed, an inter-cluster mesh is established to enhance robustness and guarantee reliable block transmission across the entire DLT network.
+
+#### **7.3.3.4 Control message generation/decoding subfunction**
+
+The control message generation/decoding subfunction is required to support various activities, including control message generation, decoding, and other related tasks involved in sending/receiving messages to/from other functional modules. It ensures the proper handling of control messages throughout the network monitoring and management process.
+
+### **7.3.4 Multi-path and multi-peer (MP2) DLT transmission function**
+
+The multi-path and multi-peer (MP2) DLT transmission function is shown in Figure 5. It is required to ensure fast and reliable block transmission by applying multi-path with forward error correction (FEC) to mitigate the impact of node or network failures. It contains an FEC-based harmonization subfunction, a push/pull control subfunction, a multi-path control subfunction, and a transport subfunction.
+
+The MP2 DLT transmission function facilitates communication and data transmission between multiple peers using multiple connections through different networks and interfaces. Each connection is supported by the transport subfunction, and the management of all connections to a remote peer is handled by the multi-path control subfunction. The detailed operation of multi-path management is recommended and described in Annex A.
+
+- The peer establishes a primary connection with a neighbouring peer when initiating communication. After the primary connection is established, the sender-side multi-path control subfunction utilizes it to transmit block data over a single path. During this process, the multi-path control subfunction calculates the throughput of the transport subfunction connection using the current congestion window size, round-trip time (RTT), and packet loss rate.
+- If the expected transmission time of block data through the primary connection exceeds the target transmission time set by the DLT platform, the multi-path control subfunction establishes a new connection called the non-primary connection. This connection is established over a different physical path than the primary one. The multi-path control subfunction simultaneously utilizes both the primary connection and the non-primary connection to transmit block data.
+- When utilizing multiple connections (multi-paths) simultaneously, the multi-path control subfunction distributes packets to each transport function connection in proportion to the measured throughput ratios of the transport function connections.
+
+![Diagram of the Multi-path and multi-peer (MP2) DLT transmission function hierarchy.](4801720824e4b5e2361a5564f91cfb70_img.jpg)
+
+```
+
+graph TD
+    subgraph MP2 [Multi-path and multi-peer (MP2) DLT transmission function]
+        direction TB
+        sub1[FEC-based harmonization subfunction]
+        sub2[Push/Pull control subfunction]
+        sub3[Multi-path control subfunction]
+        sub4[Transport subfunction]
+        sub1 --- sub2 --- sub3 --- sub4
+    end
+  
+```
+
+The diagram shows a hierarchical structure for the Multi-path and multi-peer (MP2) DLT transmission function. It consists of a large outer rectangle containing four stacked, smaller rectangles. The top rectangle is labeled 'Multi-path and multi-peer (MP2) DLT transmission function'. Below it are four subfunctions stacked vertically: 'FEC-based harmonization subfunction', 'Push/Pull control subfunction', 'Multi-path control subfunction', and 'Transport subfunction'.
+
+Diagram of the Multi-path and multi-peer (MP2) DLT transmission function hierarchy.
+
+F.751.28(25)
+
+**Figure 5 – Multi-path and multi-peer (MP2) DLT transmission function**
+
+#### 7.3.4.1 FEC-based harmonization subfunction
+
+The FEC-based harmonization subfunction is required to provide the FEC functionality required for push/pull control function and transport function. In the pull mode of push/pull control function, peers that receive block requests from a receiving peer perform FEC encoding on the requested blocks and transmit the encoded data to the receiving peer. Additionally, in transport subfunction, FEC is applied to data transmitted over each path, enabling robust data transmission without the need for retransmission.
+
+#### 7.3.4.2 Push/pull control subfunction
+
+The push/pull control subfunction is utilized by the BD/CM transmission module to transmit and receive block data. This subfunction is recommended to enable the DLT nodes to either push block data to neighbouring nodes (i.e., push mode) or pull block data from multiple neighbouring nodes (i.e., pull mode).
+
+#### 7.3.4.3 Multi-path control subfunction
+
+The multi-path control subfunction is required to perform physical multi-path management using the transport subfunction. This subfunction can either connect a single transport connection as required or concurrently establish multiple transport connections through different physical paths at the application level.
+
+#### 7.3.4.4 Transport subfunction
+
+The transport subfunction is required to contain the FEC functionality that is provided by FEC-based harmonization subfunction.
+
+## 7.4 Block data and control message transmission module
+
+The block data (BD) and control message (CM) transmission module in the DLT network performs the transmission of block data and control messages among participating nodes. This module encompasses the BD/CM transceiver function, the message forwarding table, and the MP2 DLT transmission function as shown in Figure 6.
+
+![](33ed1f9b27c7c21c797aa928b0f06851_img.jpg)
+
+BD/CM transmission module
+
+|                                                           |                          |
+|-----------------------------------------------------------|--------------------------|
+| BD/CM transceiver function                                | Message forwarding table |
+| Multi-path and multi-peer (MP2) DLT transmission function |                          |
+
+F.751.28(25)
+
+**Figure 6 – BD/CM transmission module**
+
+### 7.4.1 BD/CM transceiver function
+
+The BD/CM transceiver function is required to manage the sending and receiving of block data and control messages between nodes.
+
+- It manages the distribution of newly created blocks or updated transactions to all nodes within the DLT network through the constructed hybrid P2P multicast tree. This function is specifically designed to handle the block transmission process, aiming to achieve high throughput and minimizing latency.
+- It is also responsible for the dissemination of CMs which include relevant information related to consensus, validation rules, and network updates. These control messages play a role in coordinating the behaviour and actions of participating nodes within the DLT network.
+- The structures of the block data and control messages are created by the BD/CM transmission function. The detailed operations of the block data structure and control message formats are recommended and described in Annex B and Annex C, respectively.
+
+### 7.4.2 Message forwarding table
+
+The message forwarding table is required to assist in directing messages to their appropriate destinations within the DLT network.
+
+- The message forwarding table is another important component within the BD and CM transmission module. It serves the purpose of efficiently directing messages to their appropriate destinations within the network.
+- When a node receives a block data or control message, it consults the message forwarding table to determine the next hop or recipient node to which the message should be forwarded.
+- The table contains relevant information about the network topology and the connections between nodes. Based on this information, the message forwarding table assists in determining the optimal path for message transmission. It helps ensure that the message reaches its intended destination in an efficient and timely manner.
+
+### 7.4.3 Multi-path and multi-peer (MP2) DLT transmission function
+
+The BD/CM transmission module includes the MP2 DLT transmission function. The detailed description on the MP2 DLT transmission function can be found in clause 7.3.4.
+
+## 7.5 Consensus network module
+
+The consensus network module in the DLT network is responsible for coordinating the consensus mechanism among participating nodes through the joint participation of DLT service providers (DSPs) and auditors to achieve agreement on the state of the ledger.
+
+DSPs focus on transmitting transaction batches efficiently across the network, while auditors are responsible for validating those transmissions and performing consensus to reach agreement on the ledger state.
+
+As shown in Figure 7, the consensus network module encompasses a network-aware leader selection function, an audit chain function, and the MP2 DLT transmission function.
+
+![Diagram of the Consensus network module showing its internal structure. The module is a large rectangle containing three main stacked boxes. The top box is 'Network-aware leader selection function'. The middle box is 'Audit chain function', which contains two nested stacked boxes: 'DLT service provider (DSP) subfunction' and 'Auditor subfunction'. The bottom box is 'Multi-path and multi-peer (MP2) DLT transmission function'.](fa859e4e468bfb2710a94527f2c504af_img.jpg)
+
+Consensus network module
+
+```
+
+graph TD
+    subgraph Consensus_network_module [Consensus network module]
+        direction TB
+        A[Network-aware leader selection function]
+        subgraph Audit_chain_function [Audit chain function]
+            direction TB
+            B[DLT service provider (DSP) subfunction]
+            C[Auditor subfunction]
+        end
+        D["Multi-path and multi-peer (MP2)  
+DLT transmission function"]
+        A --- Audit_chain_function --- D
+    end
+  
+```
+
+F.751.28(25)
+
+Diagram of the Consensus network module showing its internal structure. The module is a large rectangle containing three main stacked boxes. The top box is 'Network-aware leader selection function'. The middle box is 'Audit chain function', which contains two nested stacked boxes: 'DLT service provider (DSP) subfunction' and 'Auditor subfunction'. The bottom box is 'Multi-path and multi-peer (MP2) DLT transmission function'.
+
+**Figure 7 – Consensus network module**
+
+### 7.5.1 Network-aware leader selection function
+
+The network-aware leader selection function is required to select an appropriate leader node for the consensus process, by considering network conditions and performance metrics such as network delay, node reliability, and available bandwidth. The detailed operation of the leader node selection procedure is recommended and described in Annex D.
+
+### 7.5.2 Audit chain function
+
+The audit chain function includes the DSP subfunction and the auditor subfunction. The DSP subfunction is responsible for transmission, and the auditor subfunction is responsible for consensus. The DSP and auditor subfunctions work together in a complementary way to ensure that the audit chain operates reliably and efficiently.
+
+#### 7.5.2.1 DSP subfunction
+
+The DSP subfunction is required to enable all participants to reliably and efficiently exchange messages through transmission. This subfunction can utilize various existing mempool mechanisms to minimize message overhead while transmitting fewer messages.
+
+#### 7.5.2.2 Auditor subfunction
+
+The auditor subfunction is required to perform the consensus, and it ensures agreement among all auditors in maintaining the state of the ledger. The auditor subfunction validates the transaction batches transmitted by the DSP subfunction and performs the audit chain consensus algorithm to agree on the state of the ledger. The detailed operation of the consensus procedure is recommended and described in Annex E.
+
+### 7.5.3 Multi-path and multi-peer (MP2) DLT transmission function
+
+The consensus network module includes the MP2 DLT transmission function. The detailed description of the MP2 DLT transmission function can be found in clause 7.3.4.
+
+## Annex A
+
+## Multi-path management
+
+(This annex forms an integral part of this Recommendation.)
+
+This annex describes the detailed operation of multi-path management by the multi-path and multi-peer (MP2) DLT transmission function, which is a common function in the network monitoring and management module, the block data/control message transmission module, and the consensus network module of the framework.
+
+As shown in Figure A.1, the node information represents the network status pertaining to a corresponding node or the connections related to the node.
+
+![Figure A.1 – Multi-path management diagram showing the data flow from BD transceiver through MP2 and QUIC sessions to Peer #1 and Peer #2.](33a8f3f01dfa8bce75d23017855a13c5_img.jpg)
+
+The diagram illustrates the multi-path management architecture. At the top is the **BD transceiver**. Below it, the **MP2 blockchain session** contains **Send Block** and **Receive Block** components. The **MP2 session** includes **MP2Write()** and **MP2Read()** functions. The **Node information** block is connected to the **Block buffer** and **Send buffer**. The **Send session** and **Receive session** are shown on the left and right respectively. The **FEC (Encoder/Decoder)** is connected to the **Send buffer** and **Reorder buffer**. The **QUIC session** contains **Enhanced QUIC (QUIC with rateless codes)** and is connected to **Peer #1** and **Peer #2**. Each peer has its own **Send buffer** and **Receive buffer**. The data flow is indicated by arrows: from **Send Block** to **MP2Write()** to **Block buffer** to **Send buffer** to **FEC** to **Reorder buffer** to **Receive buffer** to **MP2Read()** to **Receive Block**. The **QUIC session** is connected to the **Send buffer** and **Receive buffer** of each peer.
+
+Figure A.1 – Multi-path management diagram showing the data flow from BD transceiver through MP2 and QUIC sessions to Peer #1 and Peer #2.
+
+**Figure A.1 – Multi-path management**
+
+Sessions are established between nodes, and if a session is disrupted for any reason, a new session can be established based on real-time network information. This ensures that the session can last for an extended duration and meet user requirements. However, even though a new session is established using real-time monitored network information, the connection may not meet user expectations due to unforeseen network conditions.
+
+To address these issues, the integration of FEC in block delivery can optimize network performance by minimizing block/packet loss in the network. Buffers are employed on both the sender and receiver sides, enabling automatic adjustments to block transmission based on network conditions.
+
+Additionally, the MP2 DLT transmission function utilizes send and receive buffers, allowing for the adjustment of block delivery speed at the physical level of communication. In this manner, the MP2 DLT transmission function can optimize block delivery under varying network conditions.
+
+The peer session manages one-to-one logical connections between peers and is capable of supporting multi-path streams in a peer session, where each stream corresponds to a quick UDP Internet connections (QUIC) session. Initially, the optimal path is chosen according to the real-time monitored information, and subsequently, additional paths are selected sequentially using the same procedure. The peer session also distributes blocks/packets adaptively, considering the network status of each path.
+
+The MP2 session manages multiple peer (1:N) connections for N peers and can encompass one or more peer sessions. It facilitates robust block data transmission by applying FEC.
+
+## Annex B
+
+## Block data structure
+
+(This annex forms an integral part of this Recommendation.)
+
+This annex describes the structure of the block data that is created by the block data (BD)/control message (CM) transmission module of the framework, particularly the BD/CM transceiver function in the module.
+
+Figure B.1 shows the detailed block data structure that consists of several components.
+
+- Each block includes the current consensus block hash, the previous consensus block hash, the Merkle root hash for transactions, the consensus leader ID, the time, the time constant, the aggregated signature, a list of nodes participating in consensus, and a list of transactions included in the block.
+- A transaction consists of a block number, as well as the previous and current block hashes.
+- The Merkle Root Hash is generated from the list of transactions.
+- The associated signatures at each round of the  $(k)_{th}$  block are linked together with the  $(k)_{th}$  consensus block hash. Any node can validate each block by using the aggregated signature and checking the list of nodes participating in the signing.
+- Each block must be validated within a certain time constant during each round. This process may help the consensus network identify adversarial nodes, especially if they become the leader node during a consensus round.
+
+![](a734898ce18e972938949637c32a34f4_img.jpg)
+
+Block data structure
+
+|                                   |                  |
+|-----------------------------------|------------------|
+| $(k)_{th}$ Consensus block hash   |                  |
+| $(k-1)_{th}$ Consensus block hash |                  |
+| Block number                      | Merkle root hash |
+| Time                              | Time constant    |
+| Leader ID                         | Consensus phase  |
+| List of nodes                     | Signature        |
+| List of transaction proposals     |                  |
+
+F.751.28(25)
+
+**Figure B.1 – Block data structure for the DLT network**
+
+## Annex C
+
+## Control message formats
+
+(This annex forms an integral part of this Recommendation.)
+
+This annex describes the format of the control message used for the updating of the message forwarding table in the block data (BD)/control message (CM) transmission module of the framework.
+
+The message forwarding table is periodically updated to reflect any changes in the network topology or node connections. This dynamic adjustment allows for effective message routing and facilitates the smooth flow of block data and control messages across the DLT network.
+
+For efficient retrieval of coordinate values, the control message formats in Figure C.1 are used.
+
+The control message illustrated in Figure C.1 (a) encompasses the reference node information and is transmitted from the validation node to participating nodes.
+
+- Ndim is the number of dimensions considered in a coordinate system.
+- NodeIDx is the unique identifier of a peer node.
+- EventType specifies the CM types, e.g., node join, leave, and update.
+- NumRef is the number of reference nodes included in the message.
+- Ref Node IP #N is the IP address of a reference node.
+
+The control message depicted in Figure C.1 (b) encompasses the coordinate values of the reference nodes and is exchanged between the corresponding participating nodes.
+
+- MsgType indicates the type of the message.
+- Ndim is the number of dimensions.
+- Coordinate value ( $X_{Ndim}$ ) is the actual coordinate value of the node in the given dimensional space.
+
+| 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 |   |         |   |  |  |
+| Ndim                                                            |   | NodeIDx |   |  |  |
+| EventType                                                       |   | NumRef  |   |  |  |
+| Ref Node IP #1                                                  |   |         |   |  |  |
+| Ref Node IP #2                                                  |   |         |   |  |  |
+| ...                                                             |   |         |   |  |  |
+
+a)
+
+| 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 |   |      |   |  |  |
+| MsgType                                                         |   | Ndim |   |  |  |
+| Coordinate value ( $x_1$ )                                      |   |      |   |  |  |
+| Coordinate value ( $x_2$ )                                      |   |      |   |  |  |
+| ...                                                             |   |      |   |  |  |
+| Coordinate value ( $X_{Ndim}$ )                                 |   |      |   |  |  |
+
+b)
+
+F.751.28(25)
+
+**Figure C.1 – Control message formats**
+
+## Annex D
+
+## Leader node selection procedure
+
+(This annex forms an integral part of this Recommendation.)
+
+This annex describes the leader node selection procedure that is performed by the network-aware leader selection function in the consensus network module of the framework. The detailed procedure in Figure D.1 is as follows.
+
+- **Candidate node identification:** Each participating node in the DLT network is considered by a verification node as a potential candidate for consensus leadership. A candidate list is then created, including all eligible nodes.
+- **Metric collection:** For each candidate node, relevant network performance metrics are collected. These include, but are not limited to, network delay, node reliability, and available bandwidth.
+- **Network-aware evaluation:** The collected metrics are evaluated to assess the suitability of each node. A network-aware selection function ranks the candidate nodes based on the performance data, ensuring fairness and efficiency in leader selection.
+- **Pool participation and rule adherence:** All candidate nodes participate in a consensus pool. All nodes follow predefined rules to maintain transparency and integrity in the selection process.
+- **Dissemination of results:** The outcome of the selection pool is communicated to all participating nodes in the DLT network. The node ranked highest based on the evaluation is selected as the consensus leader.
+- **Consensus leader designation:** The designated leader node assumes its role for the current consensus round, and all consensus-related operations are coordinated through this leader.
+
+![Flowchart of consensus leader node selection procedure involving Auditors and a Verification node. The process includes steps like 'Decide the candidate for the consensus network (By round)', 'Collect node information', 'Decide participating nodes pool', 'Change participating node pool?', 'Transfer pool information', 'Election of random participating node', 'Decide consensus node and consensus leader node', and 'Formation of overlay and optimal path'. It also shows data flows like 'Candidate node list + Additional metrics information', 'Participant nodes pool', and 'List of random participating node'.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg)
+
+```
+
+graph TD
+    subgraph Auditors
+        A1(( ))
+        A2(( ))
+        A3(( ))
+    end
+    subgraph Verification_node [Verification node]
+        V(( ))
+    end
+
+    subgraph Box1 [ ]
+        B1[Decide the candidate for the consensus network (By round)]
+    end
+
+    subgraph Box2 [ ]
+        B2[Collect node information]
+        B3[Decide participating nodes pool]
+        D{Change participating node pool?}
+        B4[Transfer pool information]
+    end
+
+    subgraph Box3 [ ]
+        B5[Election of random participating node]
+        B6[Decide consensus node and consensus leader node]
+        B7[Formation of overlay and optimal path]
+    end
+
+    B1 -.-> B2
+    B2 -.-> A1
+    B2 -.-> A2
+    B2 -.-> A3
+    B2 --> B3
+    B3 --> D
+    D -- No --> B2
+    D -- Yes --> B4
+    B4 -.-> A1
+    B4 -.-> A2
+    B4 -.-> A3
+    B4 --> B5
+    B5 -.-> B6
+    B6 -.-> A1
+    B6 -.-> A2
+    B6 -.-> A3
+    B6 --> B7
+    B7 --> End[ ]
+    style Box1 fill:none,stroke:none
+    style Box2 fill:none,stroke:none
+    style Box3 fill:none,stroke:none
+    style End fill:none,stroke:none
+  
+```
+
+F.751.28(25)
+
+Flowchart of consensus leader node selection procedure involving Auditors and a Verification node. The process includes steps like 'Decide the candidate for the consensus network (By round)', 'Collect node information', 'Decide participating nodes pool', 'Change participating node pool?', 'Transfer pool information', 'Election of random participating node', 'Decide consensus node and consensus leader node', and 'Formation of overlay and optimal path'. It also shows data flows like 'Candidate node list + Additional metrics information', 'Participant nodes pool', and 'List of random participating node'.
+
+**Figure D.1 – Consensus leader node selection procedure**
+
+## Annex E
+
+## Consensus procedure
+
+(This annex forms an integral part of this Recommendation.)
+
+This annex describes the consensus procedure that is performed by the DLT service provider (DSP) subfunction and the auditor subfunction in the audit chain function of the consensus network module of the framework.
+
+For the consensus procedure, the DSP subfunction propagates the transaction batch to the auditors. The DSP subfunction attaches stream height lists containing transactions when transmitting transaction batches. These lists reflect the most recent batch heights observed across all transaction streams, ensuring that auditors can reconstruct a consistent view of the DLT network state.
+
+The detailed example of the transaction batch transmission procedure for consensus in Figure E.1 is as follows.
+
+![Figure E.1: Transaction batch transmission procedure based on the relaxed mempool. The diagram shows the flow from a relaxed mempool containing multiple transaction streams (b1 to b4) to a block proposal and finally to audit chain consensus among nodes n1 to n4.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg)
+
+The diagram illustrates the transaction batch transmission procedure. On the left, a 'Relaxed mempool' contains four streams of transaction batches:  $b_1$  (C<sub>11</sub> to C<sub>15</sub>),  $b_2$  (C<sub>21</sub> to C<sub>26</sub>),  $b_3$  (C<sub>31</sub> to C<sub>35</sub>), and  $b_4$  (C<sub>41</sub> to C<sub>45</sub>). A 'Transaction batch' is shown being added to the mempool. An arrow labeled 'Extract stream height list' points to a 'Stream height list matrix' containing the latest heights for each stream. Below this, an 'Available block height list' shows the minimum height. An arrow labeled 'Build Block proposal' points to a 'Block proposal format' table. A large arrow points from the block proposal to an 'Audit chain consensus' diagram on the right. The consensus diagram shows four nodes (n<sub>1</sub> to n<sub>4</sub>) exchanging 'Prepare' and 'Commit' messages.
+
+| Stream height list matrix      |
+|--------------------------------|
+| C <sub>15</sub> : [5, 6, 5, 5] |
+| C <sub>25</sub> : [4, 6, 3, 4] |
+| C <sub>35</sub> : [5, 5, 5, 4] |
+| C <sub>45</sub> : [5, 5, 4, 5] |
+
+| Available block height list |
+|-----------------------------|
+| [5, 5, 4, 4]                |
+
+| Block proposal format |
+|-----------------------|
+| Previous hash         |
+| TX batch hash list    |
+| Signature             |
+
+F.751.28(25)
+
+Figure E.1: Transaction batch transmission procedure based on the relaxed mempool. The diagram shows the flow from a relaxed mempool containing multiple transaction streams (b1 to b4) to a block proposal and finally to audit chain consensus among nodes n1 to n4.
+
+**Figure E.1 – Transaction batch transmission procedure based on the relaxed mempool**
+
+- The DSP subfunction shares the most recent transaction view that they observe. Specifically, the transaction batches proposed by each auditor are assigned heights corresponding to the order in which they are proposed.
+- The sequence of transaction batches proposed by each auditor is defined as a stream, and when an auditor proposes a transaction batch, they attach a stream height list that includes the latest transaction batch heights they have seen for each stream. This is to maintain a consistent view of the stream among auditors. The audit chain function allows for reliable message exchange and the maintenance of a consistent view among nodes while utilizing the existing mempool as it is.
+- As shown in Figure E.1, if the stream heights observed by each auditor for the third stream are 5, 3, 5, and 4, the available block height would be 4, which is the smallest height among the fastest three auditors' stream heights of 5, 5, and 4.
+
+- Based on the selected available block height list, a block proposal is created, and the proposer generates a consensus instance to perform the audit chain consensus. The auditors who receive the proposal immediately create an audit chain consensus instance. The consensus algorithms operating on the consensus instance can use existing consensus algorithms like Hotstuff.
+
+After receiving the transaction batches from the auditors, the auditor subfunction starts the consensus procedure.
+
+The traditional consensus mechanisms like Hotstuff are designed to achieve consensus even in situations where participants may act maliciously or fail unintentionally. However, these consensus mechanisms inherently incur overhead at the block creation and propagation stages.
+
+Traditional byzantine fault tolerance (BFT) consensus mechanisms typically follow a sequential process, where one consensus instance must be fully completed before the next instance can begin. This sequential execution limits throughput, as blocks are finalized one at a time. In contrast, the audit chain enables pipelined execution of consensus processes, allowing multiple blocks to progress through consensus simultaneously.
+
+In contrast, the audit chain consensus mechanism is a consensus mechanism designed to improve throughput. The key features of the audit chain consensus model are as follows.
+
+- In the audit chain consensus mechanism, the following two types of pipelining are performed within the auditor subfunction.
+- First, consensus instances can be pipelined because the audit chain preserves the hash chain property across blocks. As long as each block proposal correctly extends the previous block by its hash pointer, the auditors can begin processing the next block before the prior one is fully finalized.
+- Second, the voting steps of the consensus process can also be pipelined. Since the Prepare and Commit steps follow the same message pattern, auditors can overlap these steps across multiple consensus instances, further reducing latency.
+- By combining these two pipelining dimensions, the auditor subfunction accelerates block finalization while maintaining Byzantine fault tolerance. The hash chain property guarantees that consensus decisions on higher blocks remain valid once earlier blocks are committed. At the same time, auditors can parallelize message exchanges to sustain high throughput.
+
+Figure E.2 illustrates the stages of the audit chain consensus algorithm: prepare and commit.
+
+![Sequence diagram illustrating the audit chain consensus mechanism. The diagram shows interactions between a Client, a DLT service provider (DSP), a Leader, and three other nodes. The process starts with 'Client TX' from the Client to the DSP. The DSP sends a 'Block proposal' to the Leader and the three nodes. The Leader sends a 'Prepare' message to the three nodes. The three nodes send a 'Response' back to the Leader. The Leader then sends a 'Commit' message to the three nodes. Finally, the Leader sends a 'Response' back to the DSP, which in turn sends a 'Response' back to the Client. The diagram is labeled 'F.751.28(25)' at the bottom right.](7133ccf78043568ca62ecbcd43628a4a_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Client
+    participant DSP as DLT service provider (DSP)
+    participant Leader
+    participant Node1
+    participant Node2
+    participant Node3
+
+    Client->>DSP: Client TX
+    DSP->>Leader: Block proposal
+    DSP->>Node1: Block proposal
+    DSP->>Node2: Block proposal
+    DSP->>Node3: Block proposal
+    Leader->>Node1: Prepare
+    Leader->>Node2: Prepare
+    Leader->>Node3: Prepare
+    Node1->>Leader: Response
+    Node2->>Leader: Response
+    Node3->>Leader: Response
+    Leader->>Node1: Commit
+    Leader->>Node2: Commit
+    Leader->>Node3: Commit
+    Leader->>DSP: Response
+    DSP->>Client: Response
+  
+```
+
+Sequence diagram illustrating the audit chain consensus mechanism. The diagram shows interactions between a Client, a DLT service provider (DSP), a Leader, and three other nodes. The process starts with 'Client TX' from the Client to the DSP. The DSP sends a 'Block proposal' to the Leader and the three nodes. The Leader sends a 'Prepare' message to the three nodes. The three nodes send a 'Response' back to the Leader. The Leader then sends a 'Commit' message to the three nodes. Finally, the Leader sends a 'Response' back to the DSP, which in turn sends a 'Response' back to the Client. The diagram is labeled 'F.751.28(25)' at the bottom right.
+
+**Figure E.2 – Illustration of the audit chain consensus mechanism**
+
+When a DLT node submits transactions, they are first received by the DSP subfunction. The DSP subfunction reliably propagates these transactions across the DLT network, after which the DSP subfunction constructs a block proposal as output. The block proposal is delivered to the auditor subfunction. Each auditor then engages in a two-phase consensus mechanism.
+
+- In the **prepare phase**, nodes send their acknowledgements and readiness to commit to the proposed transaction. The leader node collects the acknowledgements from all the nodes to establish a preliminary consensus.
+- Once the Prepare phase is complete, the network enters the **commit phase**. During this phase, each node sends a commitment message, indicating its final agreement to execute the proposed transaction. Nodes wait to receive commitments from the leader node before proceeding.
+
+Once consensus is reached, the auditor subfunction sends replies back to the client, confirming that the submitted transactions have been finalized and recorded in the ledger. This ensures that the client is promptly notified upon completion of consensus.
+
+## Appendix I
+
+## A delay-based 3D coordinate system estimation procedure
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This appendix describes a delay-based 3D coordinate system estimation procedure used by the network monitoring function in the network monitoring and management module of the framework.
+
+**Step 1:** The coordinates of the block generation node are fixed to  $(0,0,0)$ .
+
+**Step 2:** The line connecting the block generation node and the first anchor node is defined as the  $x$  axis. The coordinate of the first anchor node is set to  $(d_{0,1}, 0, 0)$ , as shown in the figure below.
+
+![Diagram for Step 2: A horizontal line representing the x-axis. Node #0 is at the origin (0, 0, 0). Node #1 is on the x-axis at (x1, 0, 0) where x1 = d0,1. A red dashed double-headed arrow between them is labeled d0,1. The label F.751.28(25) is at the bottom right.](392a79ccd95e682ccd08f35ab2e64144_img.jpg)
+
+Diagram for Step 2: A horizontal line representing the x-axis. Node #0 is at the origin (0, 0, 0). Node #1 is on the x-axis at (x1, 0, 0) where x1 = d0,1. A red dashed double-headed arrow between them is labeled d0,1. The label F.751.28(25) is at the bottom right.
+
+**Step 3:** Select the second anchor node that is not located on the line connecting the block generation node and the first anchor node. Next, the x-y plane is constructed using the block generation node, the first anchor node, and the second anchor node. The RTT values are measured as shown below.
+
+![Diagram for Step 3: A 2D coordinate system with x and y axes. Node #0 is at (0, 0, 0). Node #1 is at (x1, 0, 0) on the x-axis. Node #2 is at (x2, y2, 0) in the x-y plane. Red dashed double-headed arrows show distances d0,2 between Node #0 and Node #2, and d1,2 between Node #1 and Node #2. The label F.751.28(25) is at the bottom right.](9b686adccf125267a013fa25721231a3_img.jpg)
+
+Diagram for Step 3: A 2D coordinate system with x and y axes. Node #0 is at (0, 0, 0). Node #1 is at (x1, 0, 0) on the x-axis. Node #2 is at (x2, y2, 0) in the x-y plane. Red dashed double-headed arrows show distances d0,2 between Node #0 and Node #2, and d1,2 between Node #1 and Node #2. The label F.751.28(25) is at the bottom right.
+
+Based on the measured RTT values and the coordinate values received from the block generation node and the first anchor node, we can obtain Eq. (I.1) and (I.2).
+
+$$\sqrt{x_2^2 + y_2^2} = d_{0,2}, \quad (\text{I.1})$$
+
+$$\sqrt{(x_2 - d_{0,1})^2 + y_2^2} = d_{1,2}, \quad (\text{I.2})$$
+
+where  $(x_2, y_2, 0)$  are the coordinate values of the second anchor node. Now, the candidate coordinate values of the second anchor node can be determined by:
+
+$$x_2 = \frac{(d_{0,2}^2 + d_{0,1}^2 - d_{1,2}^2)}{2d_{0,1}}, \quad (\text{I.3})$$
+
+$$y_2 = \pm \sqrt{d_{0,2}^2 - \left( \frac{(d_{0,2}^2 + d_{0,1}^2 - d_{1,2}^2)}{2d_{0,1}} \right)^2}. \quad (\text{I.4})$$
+
+In fact, there are two coordinate values satisfying Eq. (I.1) and (I.2) as shown in Eq. (I.3) and (I.4). One of them is selected in the following step 4.
+
+**Step 4:** Choose the third anchor node that is not placed in the x-y plane of step 3. Thus, the x-y-z space is built with the block generation node, the first anchor, the second anchor, and the third anchor nodes. After measuring the RTT values with the block generation node, the first anchor, the second
+
+anchor, and the third anchor nodes as shown in the following Eq. (I.5), (I.6) and (I.7), the candidate coordinate values of the third anchor node can be calculated using the same method as in step 3.
+
+$$x_3 = \frac{(d_{0,1}^2 + d_{0,3}^2 - d_{1,3}^2)}{2d_{0,1}}, \quad (I.5)$$
+
+$$y_3 = \frac{(d_{0,3}^2 - 2x_2x_3 + y_2^2 - d_{2,3}^2 + x_2^2)}{2y_2}, \quad (I.6)$$
+
+$$z_3 = \pm \sqrt{d_{0,3}^2 - x_3^2 - y_3^2}, \quad (I.7)$$
+
+where  $(x_3, y_3, z_3)$  are the coordinate values of the third anchor node.
+
+![A 3D coordinate system diagram showing four nodes. Node #0 is at the origin (0, 0, 0). Node #1 is on the x-axis at (x1, 0, 0). Node #2 is in the xy-plane at (x2, y2, 0). Node #3 is at (x3, y3, z3). Red dashed lines connect Node #0 to Node #3, Node #1 to Node #3, and Node #2 to Node #3. The axes are labeled x, y, and z.](d6a5f8423065d7cef55e11a0007014d9_img.jpg)
+
+A 3D coordinate system diagram showing four nodes. Node #0 is at the origin (0, 0, 0). Node #1 is on the x-axis at (x1, 0, 0). Node #2 is in the xy-plane at (x2, y2, 0). Node #3 is at (x3, y3, z3). Red dashed lines connect Node #0 to Node #3, Node #1 to Node #3, and Node #2 to Node #3. The axes are labeled x, y, and z.
+
+F.751.28(25)
+
+There are two coordinate values for the third anchor node for the same reason as in step 3. The coordinate values are finally determined in step 5.
+
+**Step 5:** An arbitrary node is selected to measure RTT values with the block generation node and the previous anchor nodes. Now, we can finalize the coordinates of the first anchor node, the second, and the third anchor node to guarantee the existence of the coordinate values of the current node in Eq. (I.8), (I.9), (I.10) and (I.11).
+
+$$\sqrt{x_4^2 + y_4^2 + z_4^2} = d_{0,4}, \quad (I.8)$$
+
+$$\sqrt{(x_4 - d_{0,1})^2 + y_4^2 + z_4^2} = d_{1,4}, \quad (I.9)$$
+
+$$\sqrt{(x_4 - x_2)^2 + (y_4 \pm y_2)^2 + z_4^2} = d_{2,4}, \quad (I.10)$$
+
+$$\sqrt{(x_4 - x_3)^2 + (y_4 - y_3)^2 + (z_4 \pm z_3)^2} = d_{3,4}, \quad (I.11)$$
+
+where  $(x_4, y_4, z_4)$  are the coordinate values of a participating node.
+
+![A 3D coordinate system with x, y, and z axes. Node #0 is at the origin (0, 0, 0). Node #1 is on the x-axis at (x1, 0, 0). Node #2 is in the xy-plane at (x2, y2, 0). Node #3 is at (x3, y3, z3). Node #4 is at (x4, y4, z4). Red dashed lines connect Node #4 to Nodes #0, #1, #2, and #3. A label F.751.28(25) is at the bottom right.](2a23751710f7827065d2b99b6df588df_img.jpg)
+
+A 3D coordinate system with x, y, and z axes. Node #0 is at the origin (0, 0, 0). Node #1 is on the x-axis at (x1, 0, 0). Node #2 is in the xy-plane at (x2, y2, 0). Node #3 is at (x3, y3, z3). Node #4 is at (x4, y4, z4). Red dashed lines connect Node #4 to Nodes #0, #1, #2, and #3. A label F.751.28(25) is at the bottom right.
+
+F.751.28(25)
+
+**Step 6:** Since the coordinate system is generated, every participating node sends a request message to the block generation node, anchor nodes, and referencing nodes that have already identified their coordinate values. The participating node measures the RTT values until the reply message, including the coordinate values, arrives as mentioned earlier. Now the coordinates of the participating node are obtained by using the same method as in Step 5, as shown in the figure below.
+
+![A 3D coordinate system similar to the previous one, but with Node #k added at (xk, yk, zk). Red dashed lines connect Node #k to Nodes #0, #1, #2, #3, and #4. A label F.751.28(25) is at the bottom right.](85b10db535b22e64c7d37f362705ddbf_img.jpg)
+
+A 3D coordinate system similar to the previous one, but with Node #k added at (xk, yk, zk). Red dashed lines connect Node #k to Nodes #0, #1, #2, #3, and #4. A label F.751.28(25) is at the bottom right.
+
+F.751.28(25)
+
+In the distributed environment, it is difficult to get the information on nodes that identify their coordinate values. Thus, the underdetermined case may occur in the above process (e.g., the inverse matrix does not exist in the matrix form). To handle this problem, a new participating node contacts a sufficient number of randomly selected nodes including anchor nodes, which may cause the overdetermined case as shown in Eq. (I.12).
+
+$$A\vec{\omega} = \vec{b}, \quad (\text{I.12})$$
+
+$$\text{where } A = \begin{bmatrix} x_1 & y_1 & z_1 \\ x_2 & y_2 & z_2 \\ x_3 & y_3 & z_3 \\ \dots & \dots & \dots \\ x_N & y_N & z_N \end{bmatrix}, \vec{\omega} = \begin{bmatrix} x_k \\ y_k \\ z_k \end{bmatrix} \text{ and } \vec{b} = \begin{bmatrix} (d_{0,k}^2 + x_1^2 + y_1^2 + z_1^2 - d_{1,k}^2)/2 \\ (d_{0,k}^2 + x_2^2 + y_2^2 + z_2^2 - d_{2,k}^2)/2 \\ (d_{0,k}^2 + x_3^2 + y_3^2 + z_3^2 - d_{3,k}^2)/2 \\ \dots \\ (d_{0,k}^2 + x_N^2 + y_N^2 + z_N^2 - d_{N,k}^2)/2 \end{bmatrix}.$$
+
+Now we can obtain the approximate solution  $\vec{\omega}_{app}$  to minimize the error  $\|A\vec{\omega}_{app} - \vec{b}\|$  by
+
+$$\vec{\omega}_{app} = (A^T A)^{-1} A^T \vec{b}. \quad (\text{I.13})$$
+
+**Step 7:** The coordinate values of participating nodes change due to the time-varying network conditions. To efficiently update coordinate values, a self-cross check algorithm is proposed. As shown below, the block generation node sends request messages to a set of participating nodes that have already identified their coordinate values.
+
+$$\begin{bmatrix} x_1 & y_1 & z_1 \\ x_2 & y_2 & z_2 \\ x_3 & y_3 & z_3 \\ \dots & \dots & \dots \\ x_N & y_N & z_N \end{bmatrix} \begin{bmatrix} x_0 \\ y_0 \\ z_0 \end{bmatrix} = \begin{bmatrix} (d_{0,0}^2 + x_1^2 + y_1^2 + z_1^2 - d_{0,1}^2)/2 \\ (d_{0,0}^2 + x_2^2 + y_2^2 + z_2^2 - d_{0,2}^2)/2 \\ (d_{0,0}^2 + x_3^2 + y_3^2 + z_3^2 - d_{0,3}^2)/2 \\ \dots \\ (d_{0,0}^2 + x_N^2 + y_N^2 + z_N^2 - d_{0,N}^2)/2 \end{bmatrix}. \quad (\text{I.14})$$
+
+If the coordinates of the block generation node are non-zero, the coordinate system should be updated. To decrease the overhead, the coordinate system is updated only if the magnitude of the coordinates of the block generation node is larger than a threshold. As a result, the resulting control message complexity is  $O(n_{nd})$ .
+
+![A 3D coordinate system diagram showing Node #0 at the origin (x0, y0, z0). Other nodes are positioned at various coordinates: Node #1 at (x1, y1, z1) on the x-axis, Node #2 at (x2, y2, z2) on the y-axis, Node #3 at (x3, y3, z3), Node #4 at (x4, y4, z4), and Node #N at (xN, yN, zN). Dashed red lines connect Node #0 to each of the other nodes. The axes are labeled x, y, and z.](1033ab90cd19fd4c5901966aeec07a86_img.jpg)
+
+A 3D coordinate system diagram showing Node #0 at the origin (x0, y0, z0). Other nodes are positioned at various coordinates: Node #1 at (x1, y1, z1) on the x-axis, Node #2 at (x2, y2, z2) on the y-axis, Node #3 at (x3, y3, z3), Node #4 at (x4, y4, z4), and Node #N at (xN, yN, zN). Dashed red lines connect Node #0 to each of the other nodes. The axes are labeled x, y, and z.
+
+F.751.28(25)
+
+# Bibliography
+
+- [b-ITU-T F.751.1] Recommendation ITU-T F.751.1 (2020), *Assessment criteria for distributed ledger technology platforms.*
+- [b-ITU-T X.1161] Recommendation ITU-T X.1161 (2008), *Framework for secure peer-to-peer communications.*
+- [b-ITU-T X.1400] Recommendation ITU-T X.1400 (2020), *Terms and definitions for distributed ledger technology.*
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.760.2-202404-I_PDF-E/raw.md b/marked/F/T-REC-F.760.2-202404-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..6d33b2ca5d2891cb6aea77f9d72edbd5a0a0c36a
--- /dev/null
+++ b/marked/F/T-REC-F.760.2-202404-I_PDF-E/raw.md
@@ -0,0 +1,594 @@
+
+
+# Recommendation **ITU-T F.760.2 (04/2024)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+---
+
+## **Guidelines for user interface of first responders in emergency response support 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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.760.2
+
+## Guidelines for user interface of first responders in emergency response support systems
+
+## Summary
+
+Recommendation ITU-T F.760.2 provides guidelines for the user interface for first responders in emergency response support systems, which facilitates the use of information and devices supporting the activities of first responders at the scene of an emergency. This Recommendation identifies the human factors in emergency response services and the user interface guidelines in emergency response support systems based on the characteristics of first-response activities. These user interface guidelines are specified to support the functional modules and usability of emergency response support systems for first responders. By meeting these guidelines, developers can create user interfaces that are optimized to support the needs and tasks of first responders, resulting in more effective and efficient use of the system.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.760.2  | 2024-04-26 | 16          | 11.1002/1000/15611 |
+
+## Keywords
+
+First responder, emergency response service, human factors, user interface.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                              | 2  |
+| 5          | Conventions .....                                                                             | 2  |
+| 6          | Background.....                                                                               | 2  |
+| 7          | Concept of the human factors in emergency response services .....                             | 3  |
+| 7.1        | Perception .....                                                                              | 3  |
+| 7.2        | Contextualization.....                                                                        | 3  |
+| 7.3        | Comprehension.....                                                                            | 4  |
+| 7.4        | Projection.....                                                                               | 4  |
+| 7.5        | Decision-making.....                                                                          | 4  |
+| 7.6        | Collaboration .....                                                                           | 4  |
+| 8          | Concept of emergency response support systems .....                                           | 4  |
+| 8.1        | Multimodal resources .....                                                                    | 4  |
+| 8.2        | Functionality of emergency response support systems .....                                     | 5  |
+| 8.3        | Usability of user interface in emergency response support systems .....                       | 6  |
+| 9          | Guidelines of user interfaces in emergency response support systems .....                     | 7  |
+| 9.1        | Intuitive and easy to use .....                                                               | 7  |
+| 9.2        | Mobility features .....                                                                       | 8  |
+| 9.3        | Clear feedback.....                                                                           | 8  |
+| 9.4        | Consistency.....                                                                              | 8  |
+| 9.5        | Customizability.....                                                                          | 8  |
+| 9.6        | Prioritized information display .....                                                         | 8  |
+| 9.7        | Responsive and fast-loading design .....                                                      | 8  |
+| 9.8        | Quick search and filtering .....                                                              | 8  |
+| Appendix I | – Use cases of user interface for first responders in emergency response support systems..... | 9  |
+| I.1        | Introduction .....                                                                            | 9  |
+| I.2        | User interface of situational awareness for police officers in law enforcement .....          | 9  |
+| I.3        | User interface of patient identification for paramedics .....                                 | 10 |
+| I.4        | User interface of situational awareness for firefighters.....                                 | 11 |
+|            | Bibliography.....                                                                             | 13 |
+
+
+
+# Recommendation ITU-T F.760.2
+
+## Guidelines for user interface of first responders in emergency response support systems
+
+# 1 Scope
+
+This Recommendation specifies the concept, guidelines and application of the user interface of first responders in emergency response support systems.
+
+The scope of this Recommendation includes:
+
+- Characteristics of human factors in emergency response services;
+- Concept of the user interface of first responders in emergency response support systems;
+- Guidelines for the user interface that reflects human factors in emergency response services.
+
+Emergency procedures are country-specific activities subject to local laws, regulations and operating procedures. This Recommendation specifies the guidelines for user interfaces in emergencies that are independent of country-specific regulations.
+
+In addition, use cases of the proposed guidelines in the emergency scenarios are provided 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 F.760.1] Recommendation ITU-T F.760.1 (2022), *Requirements and reference framework for emergency rescue systems*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 interactive system** [b-ISO 9241-210]: A combination of hardware, software and/or services that receives input from, and communicates output to, users.
+
+**3.1.2 first responder** [b-ISO 17840-3]: [An] individual who is authorized, trained and qualified to provide primary response to victims of a traffic accident, fire or submersion.
+
+NOTE – Included, but not limited to, fire departments, rescue squads, emergency medical personnel, law enforcement personnel, and in some instances military personnel where the personnel are trained in assessing and treating injuries.
+
+### 3.2 Terms defined in this Recommendation
+
+None.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                   |
+|------|-----------------------------------|
+| ERS  | Emergency Response Service        |
+| ERSS | Emergency Response Support System |
+| NLP  | Natural Language Processing       |
+| SOP  | Standard Operating Procedure      |
+| UI   | User Interface                    |
+
+## 5 Conventions
+
+In this Recommendation:
+
+- The keywords "**is recommended**" indicate a guideline or recommendation that 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. 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 service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with the Recommendation.
+
+# 6 Background
+
+First responders in emergency response services (ERSs) are typically responsible for providing immediate assistance and support in emergency situations. This can include firefighting, emergency medical services and law enforcement responding to emergency calls, rescuing individuals in danger and providing medical attention [b-NIST-IR8340]. They must be able to think quickly and make decisions under pressure, as well as possessing strong communication and teamwork skills. They also often require specialized training and certifications for providing response services in dangerous environments. Additionally, first responders must be physically fit and able to handle physically demanding situations.
+
+Providing ERS is a representative time- and mission-critical task and requires rapid response activities. First responders at the scene of an emergency are supposed to be aware of the overall situation including the cause of the emergency, current status, the condition of subjects in need and the corresponding standard operating procedure (SOP) they are to follow. First responders, in the broad definition of the term, include professional responders such as firefighters, paramedics, emergency medical technicians and police, as well as voluntary citizen responders [b-EENA].
+
+The main goal of emergency response support systems (ERSSs) is to facilitate first-response activities using mobile services, connected information and the Internet of Things (IoT) in order to look up essential information required; to record field information; and to report emergency information to the management systems of the community, region and government.
+
+The general tasks of an ERS include response to emergency calls, assessment of the scene, transporting, reporting and role-based activities. An ERSS provides supportive functionality for first responders including situational awareness, team cooperation and role-based information management. Therefore, the user interface (UI) of an ERSS is recommended to provide human-centred interaction considering the goal of an ERSS in emergency environments.
+
+This Recommendation specifies the concept of ERSS and UI guidelines to support the tasks of first responders reflecting human factors in ERS. By providing the functionality and usability of an ERSS while meeting UI guidelines, emergency response support systems can help first responders
+
+effectively communicate and collaborate in emergency situations, leading to better outcomes for both responders and those in need of assistance.
+
+## 7 Concept of the human factors in emergency response services
+
+Human factors play a critical role in the design of support systems for first responders, as these systems must be designed to meet the unique needs of these users in high-stress, time-critical situations. By taking into account these human factors considerations, the design of an ERSS can be tailored to effectively meet the needs of first responders. This approach enables an ERSS to facilitate seamless collaboration and communication, leading to improved usability of the systems and enhanced effectiveness of first responders in the field. The key human factors for the UI are depicted in Figure 1.
+
+![Diagram illustrating the human factors and user interface in emergency response support systems. The diagram shows a central 'USER INTERFACE' box connected to 'FIRST RESPONDERS' above and 'EMERGENCY RESPONSE SUPPORT SYSTEMS' below. The 'Human factors in ERS' are listed above the first responders, and the 'Functional modules' are listed within the support systems, which are further categorized by service type.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+The diagram illustrates the relationship between human factors, the user interface, and emergency response support systems. At the top, a dashed box labeled 'Human factors in ERS' contains six sub-components: Perception, Contextualization, Comprehension, Projection, Decision-making, and Collaboration. Below this box, an upward-pointing arrow leads to a central grey box labeled 'USER INTERFACE'. Above this arrow is the label 'FIRST RESPONDERS'. Below the 'USER INTERFACE' box, a downward-pointing arrow leads to another dashed box labeled 'EMERGENCY RESPONSE SUPPORT SYSTEMS'. Inside this box, three stacked boxes represent 'Functional modules', 'Multimodal resources', and 'Devices, sensors, and facilities'. Below this box, three separate boxes represent different service types: 'Firefighting', 'Law enforcement', and 'Emergency medical services'. A small label 'F.760.2(24)' is located at the bottom right of the diagram.
+
+Diagram illustrating the human factors and user interface in emergency response support systems. The diagram shows a central 'USER INTERFACE' box connected to 'FIRST RESPONDERS' above and 'EMERGENCY RESPONSE SUPPORT SYSTEMS' below. The 'Human factors in ERS' are listed above the first responders, and the 'Functional modules' are listed within the support systems, which are further categorized by service type.
+
+**Figure 1 – Human factors and user interface in emergency response support systems**
+
+To ensure the optimal performance and effectiveness of an ERSS, it is essential to consider key human factors that influence how first responders perceive, understand and interact with it. By addressing factors such as perception, contextualization, comprehension, projection, decision-making and collaboration, an ERSS can be designed to enhance the situational awareness, decision-making capabilities and overall performance of first responders.
+
+### 7.1 Perception
+
+Perception in emergency response service means gathering and processing information about the emergency and the environment [b-NIST-IR8340]. It involves the senses of sight, hearing, touch, and other sensory modalities [b-ISO 9241-125]. Designing user interfaces that effectively present information to first responders is crucial for accurate perception. This includes obtaining information from various sources, such as sensors, cameras and communication systems.
+
+### 7.2 Contextualization
+
+First responders require supportive services for the right level of information and functionality for each role and task, such as front-line law enforcement, dispatchers, commanders, chief managers and field units. Contextualization involves providing relevant and meaningful information to first
+
+responders based on the specific emergency situation. It ensures that the information presented is tailored to the needs of the responders and the incident at hand. Contextualization helps reduce cognitive load and improves decision-making [b-ISO 9241-110].
+
+### **7.3 Comprehension**
+
+First responders understand the meaning of the information and how it relates to the emergency and the response effort. A UI facilitating easy understanding and minimizing ambiguity or confusion increases the comprehensibility and clarity of information.
+
+### **7.4 Projection**
+
+First responders anticipate the future evolution of the emergency. Projection involves the ability of first responders to anticipate and project the future state of the emergency situation based on the available information.
+
+### **7.5 Decision-making**
+
+Decision-making plays a crucial role in emergency response, as first responders rely on their knowledge and collected information, as well as understanding of the situation, to make informed decisions and take appropriate actions. The ability to quickly assess information, analyse the circumstances and anticipate potential outcomes is important for effective decision-making.
+
+### **7.6 Collaboration**
+
+Sharing the information and understanding of the emergency with other members of the emergency response team, as well as the public and other stakeholders. For example, multiple vehicles need to be dispatched to a single location based on the extent of the emergency and the vehicles need to be rerouted to a new location based on availability and on the emergency [b-Giri]. Such situations of multiple incidents and multiple responses are common complex problems that require collaboration between first responders.
+
+# **8 Concept of emergency response support systems**
+
+Emergency field operations are often conducted in resource-constrained environments, where first responders face challenges such as limited access to information and environmental hazards. In such environments, it is critical for the UI of ERSSs to be designed with consideration for the limited resources and harsh conditions that first responders may encounter.
+
+The following identifies the key considerations for ERSSs and UIs in resource-constrained environments.
+
+### **8.1 Multimodal resources**
+
+Multimodal access methods refer to the use of multiple resources of interaction to access and manipulate information and devices. In resource-constrained emergency environments, where first responders face challenges such as limited access to information, communication and network outages and environmental hazards, multimodal access methods provide a more flexible and efficient way to access the information they need. By leveraging multiple modes of human-centred interaction, organizations and agencies can ensure that the systems and technologies they provide support effective and efficient emergency response, regardless of the conditions and challenges first responders face.
+
+#### **8.1.1 Video**
+
+The system supports real-time streaming of video feeds from multiple sources, with the ability to switch between feeds as needed. Video quality is to be adjustable based on available bandwidth and
+
+network conditions [ITU-T F.760.1]. The system can also support the ability to record videos for later review.
+
+#### **8.1.2 Audio**
+
+The system can support real-time voice and data transmissions, with the ability to group users into channels or talk groups based on their role or location. The system also supports the ability to broadcast messages to multiple users simultaneously.
+
+#### **8.1.3 Images**
+
+The system displays high-resolution images and diagrams, with the ability to zoom in and out as needed. Users can annotate images with notes or other information.
+
+#### **8.1.4 Texts**
+
+The system enables first responders to document and report critical information, incident details and actions taken during the incident.
+
+#### **8.1.5 Geospatial information**
+
+The system supports the display of maps with real-time updates of the location of users and incidents. Maps are also able to display additional information such as building layouts, topography and road networks. Customizations to the target area incorporate geospatial data, such as local road networks and the positioning of hospitals or shelters near disaster sites. Moreover, the system also offers details such as the distribution of supplies and transport units within the area of concern, aiding in the identification of crucial elements for the response system [b-Bae].
+
+### **8.2 Functionality of emergency response support systems**
+
+The UI in an ERSS is for the description of the specific ways that first responders interact with a system to accomplish a particular goal or task within it. In the context of multimedia services for first responders, the functionality, which is identified by situational awareness, time management, information sharing and protection of first responders, represents the primary goals that the system is designed to support. By understanding these functional modules, developers can create user interfaces that are optimized to support the specific needs and tasks of first responders.
+
+#### **8.2.1 Situational awareness**
+
+Situational awareness in an emergency response system refers to the ability of first responders and other emergency personnel to understand the current situation of an emergency, including the location, type and severity of the incident, the presence of any hazards, the status of resources and personnel, and the actions that need to be taken to respond effectively.
+
+Situational awareness is critical in emergency response as it enables first responders to make informed decisions and take appropriate actions in real time. It also includes responsiveness to the dynamic environment which is one of the major challenges in an emergency, especially for those involving multiple incidents. Therefore, situational awareness requires access to timely and accurate information about the emergency and the surrounding environment, as well as the ability to process and interpret that information.
+
+#### **8.2.2 Safety management**
+
+The systems need to have a safety management plan to ensure that first responders are safe and healthy while performing their duties. The interface can provide first responders with information to help them stay safe and aware of their surroundings, such as weather and traffic reports and alerts for potential hazards.
+
+#### 8.2.3 Real-time data sharing
+
+ERSSs are based on the support of seamless communication, coordination and information sharing among team members, ensuring a shared understanding of the situation. Support systems allow first responders to communicate with each other and with dispatch centres, so they can coordinate their efforts and make sure that the right resources are deployed to the right location. This can include features such as real-time messaging, video conferencing and other forms of collaboration between users. The system also supports the ability to share files and other resources between users. In order to support this function, various parts such as integrated network management for different network types, high-definition video services and highly reliable data are considered [ITU-T F.760.1].
+
+#### 8.2.4 Connection to standard operating procedures
+
+ERS have established SOPs in place to ensure that first responders know how to respond to different types of emergencies. An ERSS provides first responders access to SOPs and guidelines, so they know how to respond to different types of emergencies.
+
+#### 8.2.5 Equipment management
+
+First responders must have access to the necessary equipment and supplies to provide ERS, such as oxygen tanks, fire hoses and pumps, or defibrillators. In addition, first responders must have access to appropriate personal protective equipment (PPE) to protect themselves and others from hazards, such as fire-resistant clothing, respirators and protective eyewear.
+
+![Diagram of functional modules in emergency response support systems](08441fa90c5fd11994626f662ac13f19_img.jpg)
+
+The diagram illustrates the functional modules of an emergency response support system. At the top, an arrow points to 'Application for first responders', which in turn points to a central box labeled 'Emergency response support systems'. This box contains five dashed rectangular modules: 'Situation awareness', 'Safety management', 'Real-time data sharing', 'Connection to standard operating procedure', and 'Equipment management'. Below this central box, two arrows point upwards. The left arrow is labeled 'Transportation' and is accompanied by icons of a fire truck and an ambulance. The right arrow is labeled 'Equipment' and is accompanied by icons of a camera, a laptop, a helmet, and a first aid kit. The text 'F.760.2(24)' is located at the bottom right of the diagram.
+
+Diagram of functional modules in emergency response support systems
+
+Figure 2 – Functional modules in the emergency response support systems
+
+### 8.3 Usability of user interface in emergency response support systems
+
+Studies have indicated that first responders are not averse to technology but rather seek technology that aligns with their specific contexts of use [b-NIST-SP1286pt4]. The goal is for ERSSs to make it easier for first responders to accomplish their primary tasks. Ultimately, first responders require user-centred technology that is easy to use, easy to learn and easy to integrate into their contexts of use. This includes intuitive and efficient UIs for clear and concise information presentation.
+
+#### 8.3.1 Immediate access
+
+An ERSS provides first responders with real-time and accurate information on the situation, including the location and status of other responders, the nature and severity of the incident and any hazards or risks present. This information can be presented in a clear and understandable format, such as maps or diagrams. An IoT-enabled UI can further enhance the usability of an ERSS, by leveraging real-time connectivity and seamless access to critical information.
+
+#### 8.3.2 Reducing cognitive workload
+
+Designing the ERSS with the goal of minimizing the cognitive workload on first responders is crucial. This can be achieved by reducing reliance on memorization or complex calculations and instead focusing on providing a clear and simplified information presentation. By streamlining the interface and presenting information in a straightforward manner, the ERSS can help alleviate cognitive burden, allowing first responders to more effectively and efficiently perform their duties during emergency situations.
+
+#### 8.3.3 Proper functionality
+
+The UI enables users to interact with the ERSS and perform tasks effectively. The UI accurately reflects the available features, controls and options, allowing users to access and utilize the system's capabilities without confusion or errors.
+
+First responders need the ERSS to provide feedback and monitoring on the performance of their tasks, including metrics such as response times, accuracy and effectiveness, to enable continuous improvement and optimization.
+
+#### 8.3.4 Alignment of user needs
+
+The UI aligns with the specific needs of first responders. For example, designing user interfaces that support predictive capabilities and visualization techniques can address the needs of first responders who require assistance in projecting future outcomes. By incorporating these features into the interface, first responders can gain valuable insights and anticipate potential scenarios, enabling them to make more informed decisions during emergency situations. [b-ISO 9241-110].
+
+## 9 Guidelines of user interfaces in emergency response support systems
+
+The design of the UI for first responders in resource-constrained environments is critical to the success of emergency response efforts. By considering the limitations and challenges faced by first responders in the field, organizations and agencies can ensure that the systems and technologies they provide support effective and efficient emergency response with UIs that provide a more flexible and efficient way for first responders to access information and control devices in resource-constrained emergency environments [b-NIST-IR8340]. This clause identifies the guidelines for the UIs in ERSSs.
+
+### 9.1 Intuitive and easy to use
+
+- R-ERSS-01: The UI is recommended to be designed to be intuitive and easy to use, with clear navigation and controls.
+
+Touch-based or haptic-based interaction, including touchscreens and touchpads, can provide a simple and intuitive way for first responders to access information and control devices. This mode of interaction is particularly useful when first responders need to receive notifications while wearing gloves or in noisy environments where audio feedback may not be easily audible or where traditional keyboard and mouse interaction is challenging.
+
+- R-ERSS-02: A UI with natural language processing (NLP), including voice commands and speech recognition, can optionally be adopted for a convenient and hands-free way for first responders to access information and control devices.
+
+This UI is particularly useful when first responders need to access information or control devices without looking at the screen or when their hands are occupied with other tasks such as carrying equipment or assisting a patient.
+
+### **9.2 Mobility features**
+
+- R-ERSS-03: The UI is recommended to be used on mobile devices, with large buttons and easy-to-read text.
+
+This is important because first responders need to be able to use the system on the go, without being distracted by a complex or cluttered interface.
+
+### **9.3 Clear feedback**
+
+- R-ERSS-04: The UI is recommended to provide clear feedback to users, such as confirmation messages or error alerts, to ensure that users understand the system's status.
+
+This is important because first responders need to be able to rely on the system to provide accurate and timely information.
+
+### **9.4 Consistency**
+
+- R-ERSS-05: The UI is recommended to be consistent across different devices and platforms, to ensure that users can easily switch between devices as needed.
+
+This is important because first responders may need to switch between different devices or platforms depending on the situation.
+
+### **9.5 Customizability**
+
+- R-ERSS-06: The UI can optionally be customizable, with the ability for first responders to set their own preferences for display and layout.
+
+This is important because first responders may have different roles, tasks and experience, and UIs corresponding to their preferences can enhance the efficiency of ERSs.
+
+### **9.6 Prioritized information display**
+
+- R-ERSS-07: The UI is recommended to prioritize the display of essential and time-critical information, presenting it prominently and ensuring it is easily visible at a glance.
+
+This reduces the need for first responders to search extensively for critical updates or incident details.
+
+### **9.7 Responsive and fast-loading design**
+
+- R-ERSS-08: The UI is recommended to be responsive, ensuring quick loading and smooth performance even in high-pressure situations.
+
+Delayed loading times or laggy responses can hinder immediate access and compromise the usability of the ERSS.
+
+### **9.8 Quick search and filtering**
+
+- R-ERSS-09: The interface is recommended to offer efficient search and filtering capabilities, enabling first responders to locate specific data or resources promptly.
+
+This can include search bars, filters or advanced search options tailored to the specific needs of emergency response.
+
+# Appendix I
+
+## Use cases of user interface for first responders in emergency response support systems
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This clause introduces the user interfaces (UIs) of first-response applications in various scenarios.
+
+### I.1 Introduction
+
+The appendix consists of three use cases. A situation-aware service and UI for police officers in law enforcement is described in clause I.2; a use case of a UI in the process of patient identification in emergency medical services is introduced in clause I.3; and a UI for firefighters in search and rescue activities is shown in clause I.4.
+
+### I.2 User interface of situational awareness for police officers in law enforcement
+
+#### I.2.1 Description
+
+Traffic stop procedures represent one of the most prevalent encounters between law enforcement personnel and members of the public. The design used the knowledge from the requirements analysis to develop a prototype with two features: a context-aware interface and an on-demand information display. The incorporation of situational awareness into the interface enables officers to discern crucial elements in their surroundings and evaluate the potential for a heightened risk scenario.
+
+#### I.2.2 Service flows
+
+The service flow of a law enforcement service for police officers is illustrated in Figure I.1 and can be described as follows.
+
+![Figure I.1: Service flow of a law enforcement service for police officers. The diagram shows a flow between a 'Server', 'Smart glasses or camera', and a 'Vehicle' (represented by 'Plate number', 'Driving licence', and 'Inside the vehicle'). The flow is numbered 1 to 4: 1) Input images from the vehicle to the smart glasses; 2) Request information from the smart glasses to the server; 3) Receive information from the server to the smart glasses; 4) Output images from the smart glasses to the vehicle. The output images include: 1) Hazardous colour highlighting (Low, Medium, High), 2) Vehicle registration certificate, and 3) Driver's background. A small code 'F.760.2(24)' is in the bottom right corner.](3f1987804d7d78bc3b3bc560e974280a_img.jpg)
+
+The diagram illustrates the service flow for police officers using smart glasses. On the left, three boxes represent input data: 'Plate number', 'Driving licence', and 'Inside the vehicle'. An arrow labeled '① Input images' points from these boxes to a central icon of 'Smart glasses or camera'. From the smart glasses, an arrow labeled '② Request information' points up to a 'Server' box. From the 'Server', an arrow labeled '③ Receive information' points down to the smart glasses. From the smart glasses, an arrow labeled '④ Output images' points to a large box on the right. This box contains three items: '1) Hazardous colour highlighting' with three colored circles (green, yellow, red) labeled 'Low', 'Medium', 'High'; '2) Vehicle registration certificate'; and '3) Driver's background'. The text 'F.760.2(24)' is in the bottom right corner of the diagram area.
+
+Figure I.1: Service flow of a law enforcement service for police officers. The diagram shows a flow between a 'Server', 'Smart glasses or camera', and a 'Vehicle' (represented by 'Plate number', 'Driving licence', and 'Inside the vehicle'). The flow is numbered 1 to 4: 1) Input images from the vehicle to the smart glasses; 2) Request information from the smart glasses to the server; 3) Receive information from the server to the smart glasses; 4) Output images from the smart glasses to the vehicle. The output images include: 1) Hazardous colour highlighting (Low, Medium, High), 2) Vehicle registration certificate, and 3) Driver's background. A small code 'F.760.2(24)' is in the bottom right corner.
+
+**Figure I.1 – Service flow of a law enforcement service for police officers**
+
+- 1) **Vehicle approach:** While approaching the vehicle, the officer performs a visual inspection looking for suspicious movements and illegal objects inside the vehicle.
+- 2) **Driver interaction:** The officer interacts with a driver, and the driver will hand over their driving licence upon request. Alternatively, a system control UI enables the interaction if voice commands are not possible or desirable.
+- 3) **Information verification:** With the driver's documents in the officer's possession, a search for information regarding the driver is initiated.
+
+#### I.2.3 Situation
+
+- 1) While on patrol, a law enforcement officer halts a suspicious vehicle and proceeds towards it for closer inspection.
+
+- 2) Utilizing a smart-glasses-activated menu interface, the officer scans the suspect's vehicle licence and numberplate to acquire real-time information.
+- 3) The officer proceeds to scan the driver's ID, cross-referencing the obtained information with the driver's identity. The smart display reveals that the driver's licence has expired and provides a summary of the driver's criminal record.
+- 4) Upon searching the vehicle, the officer discovers hazardous items, including knives and guns.
+- 5) The officer utilizes the task menu on the smart display to handle the situation and document the outcome. Subsequently, the driver is escorted to the police station for further processing.
+
+### **I.3 User interface of patient identification for paramedics**
+
+#### **I.3.1 Description**
+
+The UI of patient identification supports the integration of information from IoT devices, mobile services and disaster response systems to swiftly obtain information about an individual's identity and critical reference information during an emergency, taking into account environmental attributes and essential personal information that have been registered with the consent for usage in ERSs. This enables identity confirmation through IoT services that recognize NFC or QR codes and access information; see Figure I.2.
+
+#### **I.3.2 Service flows**
+
+- 1) The paramedics utilize contact or non-contact ID devices, along with biometric information, to identify an individual in need of assistance. This process automatically generates essential details such as the time of contact, personal information retrieval and an initial assessment of the individual's condition.
+- 2) The paramedics access the information-sharing system to retrieve personal data which have been stored with the consent for use in an emergency and present the necessary findings in an appropriate format.
+- 3) Using the mobile terminal, the paramedics retrieve personal health history, document the current activities and subsequently initiate transportation to the hospital for further care.
+
+#### **I.3.3 Situation**
+
+- 1) On receipt of an emergency call, an ambulance team is promptly dispatched to the reported location using the geospatial information detected from the emergency call.
+- 2) On arrival, paramedics utilize an IoT device to identify the unconscious individual.
+- 3) Once the patient's identity and critical information that have been stored with consent for use in an emergency are obtained, treatment congruous with their medical history is administered.
+- 4) From the patient's health history, the proximity of a frequently visited hospital is determined. If one is close by, the patient is taken there; otherwise, a nearby hospital is contacted, and the patient is transferred.
+
+![Sequence diagram showing interaction between User, System, and Server for NFC reader identification. The process involves reading an NFC tag, requesting a profile, searching for it, and either pairing or sending an unknown message based on whether the profile is found.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg)
+
+```
+
+sequenceDiagram
+    actor User
+    participant System
+    participant Server
+
+    Note left of User: Start
+    User->>System: Approach device of NFC reader
+    System->>System: Read device's NFC tag
+    System->>System: Read device profile
+    System->>Server: Request patient profile (device_profile)
+    Server->>Server: Receive request for patient profile
+    Server->>Server: Search device profile
+    Note right of Server: Profile found?
+    alt Profile found
+        Server->>Server: Pair device
+        Server->>Server: Search patient profile
+        Note right of Server: Profile found?
+        alt Profile found
+            Server->>System: Send patient profile (patient_profile)
+            System->>System: Receive patient profile
+            System->>User: Patient profile inquiry
+            User->>User: Terminate identification
+            Note left of User: End
+        else Profile not found
+            Note right of Server: Profile not found
+            Server->>Server: (End)
+        end
+    else Profile not found
+        Note right of Server: Profile not found
+        Server->>Server: No device information retrieved
+        Server->>Server: Send unknown device message
+        Note right of Server: (End)
+    end
+  
+```
+
+Sequence diagram showing interaction between User, System, and Server for NFC reader identification. The process involves reading an NFC tag, requesting a profile, searching for it, and either pairing or sending an unknown message based on whether the profile is found.
+
+F.760.2(24)
+
+**Figure I.2 – Interaction using an NFC reader for first responders**
+
+## I.4 User interface of situational awareness for firefighters
+
+#### I.4.1 Description
+
+Firefighters face a multitude of potential dangers during search and rescue operations [b-NIST-SP1286pt3]. In a burning building, for instance, risks can quickly escalate. On the scene, a firefighter encounters blocked passages, injurious gases, high temperatures, toxic smoke and various combinations of risk factors. Each incident is distinct, often requiring firefighters to blindly traverse buildings with diverse floor plans. The careful detection and monitoring of these hazards are crucial for the successful execution of their operations.
+
+#### I.4.2 Service flows
+
+The service flow of search and rescue activity using smart devices for firefighters is illustrated in Figure I.3, and can be described as follows:
+
+- 1) The UIs outline the structure of each explored region and display the room number on the walls. Combining this system with the map and navigation, firefighters can easily know their positions and communicate directions with other team members.
+- 2) The system tags the firefighters and shows their location in the environment. The tag contains the firefighter's name and distance. Each firefighter's tag has a different colour to easily distinguish them. The tag is visible through walls and barriers, and its size is consistent with the firefighter's distance.
+- 3) To improve awareness of environmental factors, the UI implements a situational awareness interface, which consists of a hazard marker system, an alert system and an environmental information display.
+
+![Diagram illustrating the service flows of search and rescue activity using smart devices for firefighters. The diagram shows a 'Fire scene' box pointing to a 'Smart glasses or camera' icon (step 1). The icon points to a 'Server' box (step 2, labeled 'Request route guidance'). The 'Server' box points to a list box (step 3, labeled 'Receive route guidance'). The list box contains: '1) Indoor guidance and mini-map', '2) Team identification', and '3) Alert information'. The list box points to the 'Smart glasses or camera' icon (step 4, labeled 'Output'). Below the 'Smart glasses or camera' icon is a 'Mobile device' box with an arrow pointing to it from the list box.](ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg)
+
+```
+
+graph TD
+    FS[Fire scene] -- 1 --> SG[Smart glasses or camera]
+    SG -- 2 Request route guidance --> S[Server]
+    S -- 3 Receive route guidance --> L["1) Indoor guidance and mini-map  
+2) Team identification  
+3) Alert information"]
+    L -- 4 Output --> SG
+    L --> MD[Mobile device]
+  
+```
+
+F.760.2(24)
+
+Diagram illustrating the service flows of search and rescue activity using smart devices for firefighters. The diagram shows a 'Fire scene' box pointing to a 'Smart glasses or camera' icon (step 1). The icon points to a 'Server' box (step 2, labeled 'Request route guidance'). The 'Server' box points to a list box (step 3, labeled 'Receive route guidance'). The list box contains: '1) Indoor guidance and mini-map', '2) Team identification', and '3) Alert information'. The list box points to the 'Smart glasses or camera' icon (step 4, labeled 'Output'). Below the 'Smart glasses or camera' icon is a 'Mobile device' box with an arrow pointing to it from the list box.
+
+**Figure I.3 – Service flows of search and rescue activity using smart devices for firefighters**
+
+#### I.4.3 Situation
+
+- 1) Firefighters receive a report that a building is on fire, arrive at the scene and enter the burning building.
+- 2) Use of the indoor guidance system activates dynamic route creation and map.
+- 3) When entering a new room or hallway, the room is automatically scanned and added to the map, depicting real-time data on the location of firefighters, victims and routes to specific areas.
+- 4) The system assigns tags to display information about current team members. The tag includes the firefighters' names with different colours.
+- 5) If planned evacuation routes are blocked due to unexpected fire spread, alerts are sent notifying changes to environmental factors.
+
+# Bibliography
+
+- [b-ISO 9241-110] ISO 9241-110:2020, *Ergonomics of human-system interaction – Part 110: Interaction principles*.
+- [b-ISO 9241-125] ISO 9241-125:2017, *Ergonomics of human-system interaction – Part 125: Guidance on visual presentation of information*.
+- [b-ISO 9241-210] ISO 9241-210:2010, *Ergonomics of human – system interaction – Part 210: Human-centred design for interactive systems*.
+- [b-ISO 17840-3] ISO 17840-3:2019, *Road vehicles – Information for first and second responders – Part 3: Emergency response guide template*.
+- [b-Bae] Bae, J.W., Shin, K., Lee, H.R., Lee, H.J., Lee, T., Kim, C.H., & Moon, I. C. (2017), Evaluation of Disaster Response System Using Agent-Based Model With Geospatial and Medical Details, *IEEE Transactions on Systems, Man, and Cybernetics: Systems*, Vol. 48, No. 9, pp. 1454–1469.
+- [b-EENA] European Emergency Number Association (2023), *Public Safety Answering Points –Global Edition 2022*. <https://eena.org/knowledge-hub/press-releases/public-safety-answering-points-global-edition-2022/>
+- [b-Giri] Giri, A.R., Chen, T., Rajendran, V.P., & Khamis, A. (2022), A Metaheuristic Approach to Emergency Vehicle Dispatch and Routing, In *2022 IEEE International Conference on Smart Mobility (SM)*, pp. 27–31.
+- [b-NIST-IR8340] Choong, Y. and Salvendy, G. (2021), *Voices of First Responders; Applying Human Factors and Ergonomics Knowledge to Improve the Usability of Public Safety Communications Technology: Findings from User-Centered Interviews*, Phase 1, Volume 5, NIST Interagency/Internal Report (NISTIR), National Institute of Standards and Technology, Gaithersburg, MD. <https://doi.org/10.6028/NIST.IR.8340>
+- [b-NIST-SP1286pt3] Dawkins, S., Choong, Y.-Y., Buchanan, K., Spickard-Prettyman, S. (2023) *Voices of First Responders – Fire Service, NIST Special Publication (NIST SP) No. 1286pt3*, National Institute of Standards and Technology, Gaithersburg, MD.
+- [b-NIST-SP1286pt4] Dawkins, S., Choong, Y.-Y., Buchanan, K. (2023), *Voices of First Responders – Law Enforcement*, NIST Special Publication (NIST SP), No. 1286pt3, National Institute of Standards and Technology, Gaithersburg, MD.
+
+
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.780.3-202212-I_PDF-E/raw.md b/marked/F/T-REC-F.780.3-202212-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..d0c9c1da7bb3079628030c833450d90b526bd30d
--- /dev/null
+++ b/marked/F/T-REC-F.780.3-202212-I_PDF-E/raw.md
@@ -0,0 +1,801 @@
+
+
+# Recommendation **ITU-T F.780.3 (12/2022)**
+
+SERIES F: Non-telephone telecommunication services  
+Multimedia services
+
+## --- **Use cases and requirements for ultra-high-definition teleconsulting system**
+
+![ITU logo](390120de4fe440c42fea8154fcaad334_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 F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+## **TELEGRAPH SERVICE**
+
+|                                                                 |             |
+|-----------------------------------------------------------------|-------------|
+| Operating methods for the international public telegram service | F.1–F.19    |
+| The gentex network                                              | F.20–F.29   |
+| Message switching                                               | F.30–F.39   |
+| The international telemessages service                          | F.40–F.58   |
+| The international telex service                                 | F.59–F.89   |
+| Statistics and publications on international telegraph services | F.90–F.99   |
+| Scheduled and leased communication services                     | F.100–F.104 |
+| Phototelegraph service                                          | F.105–F.109 |
+
+## **MOBILE SERVICE**
+
+|                                                        |             |
+|--------------------------------------------------------|-------------|
+| Mobile services and multdestination satellite services | F.110–F.159 |
+|--------------------------------------------------------|-------------|
+
+## **TELEMATIC SERVICES**
+
+|                                           |             |
+|-------------------------------------------|-------------|
+| Public facsimile service                  | F.160–F.199 |
+| Teletex service                           | F.200–F.299 |
+| Videotex service                          | F.300–F.349 |
+| General provisions for telematic services | F.350–F.399 |
+
+## **MESSAGE HANDLING SERVICES**
+
+F.400–F.499
+
+## **DIRECTORY SERVICES**
+
+F.500–F.549
+
+## **DOCUMENT COMMUNICATION**
+
+|                                      |             |
+|--------------------------------------|-------------|
+| Document communication               | F.550–F.579 |
+| Programming communication interfaces | F.580–F.599 |
+
+## **DATA TRANSMISSION SERVICES**
+
+F.600–F.699
+
+## **MULTIMEDIA SERVICES**
+
+**F.700–F.799**
+
+## **ISDN SERVICES**
+
+F.800–F.849
+
+## **UNIVERSAL PERSONAL TELECOMMUNICATION**
+
+F.850–F.899
+
+## **ACCESSIBILITY AND HUMAN FACTORS**
+
+F.900–F.999
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.780.3
+
+## Use cases and requirements for ultra-high-definition teleconsulting system
+
+## Summary
+
+Recommendation ITU-T F.780.3 describes the use cases and technical requirements of an ultra-high-definition (UHD) teleconsulting system. UHD teleconsulting system is an important application of UHD display technology and the information and communication technology (ICT) in the medical field, under the background of unbalanced medical resources, especially during the COVID-19 pandemic, which can realize the optimal allocation of medical resources and benefit people in areas with less developed medical resources.
+
+It recommends the framework, functional requirements, and performance requirements of a UHD teleconsulting system which are the necessary hardware and software foundations for teleconsultation.
+
+Finally, the Recommendation also provides two application cases of the UHD teleconsulting system in Appendix I, including the roles of different participants, as well as the teleconsultation process.
+
+This Recommendation is suitable for the development, construction, and evaluation of the UHD teleconsulting system in different countries and regions.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.780.3  | 2022-12-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/15203">11.1002/1000/15203</a> |
+
+## Keywords
+
+Framework, performance requirement, teleconsulting, UHD, use cases.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                | 3  |
+| 6          | Introduction .....                                               | 3  |
+| 7          | Framework for UHDTCS .....                                       | 4  |
+| 7.1        | Summary.....                                                     | 4  |
+| 7.2        | Overall system framework .....                                   | 4  |
+| 7.3        | Communication framework for streaming media service system ..... | 4  |
+| 8          | Function requirements for UHDTCS.....                            | 5  |
+| 8.1        | Summary.....                                                     | 5  |
+| 8.2        | BBS.....                                                         | 6  |
+| 8.3        | UHDSM service system .....                                       | 7  |
+| 8.4        | TCTS .....                                                       | 7  |
+| 8.5        | MCT .....                                                        | 8  |
+| 8.6        | Gateway .....                                                    | 8  |
+| 9          | Performance requirements for UHDTCS .....                        | 8  |
+| 9.1        | General .....                                                    | 8  |
+| 9.2        | BBS.....                                                         | 9  |
+| 9.3        | UHDSM service system .....                                       | 9  |
+| 9.4        | Teleconsulting terminal system.....                              | 9  |
+| 9.5        | MCT .....                                                        | 13 |
+| 9.6        | Gateway .....                                                    | 13 |
+| 9.7        | Security requirements .....                                      | 13 |
+| Appendix I | – Use cases for UHDTCS .....                                     | 15 |
+| I.1        | Use case 1: Scheduled teleconsultation .....                     | 15 |
+| I.2        | Use case 2: Emergency treatment teleconsultation .....           | 15 |
+|            | Bibliography.....                                                | 16 |
+
+
+
+# Recommendation ITU-T F.780.3
+
+# Use cases and requirements for ultra-high-definition teleconsulting system
+
+# 1 Scope
+
+This Recommendation specifies the use cases and requirements for the ultra-high definition (UHD) teleconsulting system, which includes:
+
+- framework for UHD teleconsulting system;
+- function requirements for UHD teleconsulting system; and
+- performance requirements for UHD teleconsulting system.
+
+For the implementation of this Recommendation, two application use-cases are given in Appendix I, scheduled teleconsultation and emergency treatment teleconsultation.
+
+# 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 K.116] Recommendation ITU-T K.116 (2019), *Electromagnetic compatibility requirements and test methods for radio telecommunication terminal equipment*.
+
+[ISO/IEC 27002] ISO/IEC 27002:2022, *Information security, cybersecurity and privacy protection – Information security controls*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 code rate** [b-ISO/IEC 23008-10]: Ratio between the number of source symbols and the number of encoding symbols.
+
+**3.1.2 colour gamut** [b-IEC 60050-845]: Volume, area, or solid in a colour space, consisting of all those colours that are either:
+
+- Present in a specific scene, artwork, photograph, photomechanical, or other reproduction; or
+- Capable of being created using a particular output device and/or medium.
+
+NOTE – In reproduction and media applications only the volume or solid in a colour space is regarded as a colour gamut. In applications such as signal lighting the colour gamut is an area.
+
+**3.1.3 echo cancellation** [b-IEC 60050-704]: A method of echo control effected by subtracting an estimated echo from the signal which includes an unwanted echo.
+
+**3.1.4 electromagnetic compatibility** [b-ITU-T K.127]: Ability of equipment to function satisfactorily in its electromagnetic environment without introducing intolerable electromagnetic disturbances to anything in that environment.
+
+**3.1.5 luminance** [b-IEC 60050-841]: Density of luminous intensity with respect to the projected area in a specified direction at a specified point on a real or imaginary surface.
+
+**3.1.6 luminance contrast** [b-IEC 60050-845]: Quotient of the luminance of two active parts of a display surface having the same or different colours.
+
+NOTE – The luminance contrast ratio has unit one.
+
+**3.1.7 luminance uniformity** [b-IEC 60050-845]: Quotient of minimum luminance and average luminance of a surface.
+
+NOTE – The luminance uniformity has unit one.
+
+**3.1.8 picture sticking** [b-IEC 60050-531]: An unwanted image reappearing after the apparent removal of the charge corresponding to a previously stationary image.
+
+**3.1.9 reverberation time** [b-ISO 354:2003]: Time, in seconds, that would be required for the sound pressure level to decrease by 60 dB after the sound source has stopped.
+
+**3.1.10 sampling rate** [b-ISO 21250-3]: <signal processing> Frequency with which a continuous signal is sampled and converted into a time-discrete signal.
+
+NOTE – The unit is hertz (Hz) or samples (readings) per second [samples per second (samples/s)].
+
+**3.1.11 signal-to-noise ratio (SNR)** [b-IEC/TR 80001-2-3]: Comparison of signal power to noise power.
+
+**3.1.12 ultra-high definition** [b-ITU-T F.780.1]: A video format of digital display and camera in which the horizontal screen resolution is on the order of over 4 000 pixels.
+
+## **3.2 Terms defined in this Recommendation**
+
+This Recommendation defines the following terms:
+
+**3.2.1 backend business system:** A system for controlling and processing the data related to the UHD teleconsulting service.
+
+**3.2.2 demander:** A doctor or nurse who wants to consult with other doctors through a UHD teleconsulting system.
+
+**3.2.3 mobile control terminal:** A portable control equipment for controlling the behaviour of the teleconsulting terminal system.
+
+**3.2.4 teleconsulting:** A consultation method between doctors or between doctors and nurses through telephone, fax, network video, and other modern communication tools, to complete the analysis of medical records, disease diagnosis, and to further determine the treatment plan.
+
+**3.2.5 teleconsulting terminal system:** A terminal system for displaying, capturing and real-time pushing messages of the UHD streaming media.
+
+**3.2.6 UHD streaming media:** A technology and process providing UHD definition video and high-fidelity audio audio-visual services, by compressing a series of UHD video data and high fidelity audio data, and transmitting the data packets in real time in streaming mode.
+
+**3.2.7 UHD streaming media service system:** A system for providing processing and transmission of UHD streaming media data generated by the UHD teleconsulting service.
+
+**3.2.8 ultra-high definition teleconsulting system:** A system for realizing complete teleconsulting service based on the UHD streaming media technology.
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+BBS            Backend Business System
+
+|        |                                             |
+|--------|---------------------------------------------|
+| EMR    | Electronic Medical Record                   |
+| HIS    | Hospital Information System                 |
+| ICT    | Information and Communication Technology    |
+| LAN    | Local Area Network                          |
+| MCT    | Mobile Control Terminal                     |
+| MMS    | Microsoft Media Server Protocol             |
+| MQTT   | Message Queuing Telemetry Transport         |
+| RTP    | Real-time Transport Protocol                |
+| RTCP   | Real-time Transport Control Protocol        |
+| RTMP   | Real-time Messaging Protocol                |
+| RTSP   | Real-time Streaming Protocol                |
+| SNR    | Signal-to-Noise Ratio                       |
+| TCTS   | Teleconsulting Terminal System              |
+| UHD    | Ultra-High Definition                       |
+| UHDSM  | Ultra-High-Definition Streaming Media       |
+| UHDTCS | Ultra-High-Definition Teleconsulting System |
+| WAN    | Wide Area Network                           |
+
+# 5 Conventions
+
+None.
+
+# 6 Introduction
+
+Teleconsulting is the convergence of modern medicine and the information and communication technology (ICT). It is a healthcare consultation carried out remotely using audio-visual telecommunications between doctors or between doctors and nurses. Teleconsulting system will realize face-to-face medical communication between doctors or between doctors and nurses in two or more places, furthermore, it will also realize the optimal allocation of medical resources.
+
+According to the World Health Organization (WHO), telemedicine is "the use of information and communication technology to deliver medical services and information from one location to another", while e-health is "a new term used to describe the combined use of electronic information and communication technology in the health sector". As a subcategory of e-health, teleconsulting which can reassign medical resources is going to be indispensable in the health care area and medical community, especially in developing countries. It is important to achieve interoperability amongst systems and to reduce the cost of devices through economies of scale. Consequently, the development of global international standards with the involvement of the major plays (i.e., governments, inter-governmental organizations, non-governmental organizations, medical institutions, doctors, manufacturers, etc.) is a key factor in achieving these objectives.
+
+Teleconsulting systems are supposed to be widely deployed in the coming future, especially in developing countries. Furthermore, the ultra-high-definition teleconsulting systems (UHDTCSs) meet the needs of local and remote consultation. The main object of this Recommendation is to standardize the use cases and requirements of the UHDTCS at the beginning of the worldwide technical promotion and initialize the basic requirements preliminarily as the guideline for the spread, especially in developing countries.
+
+# 7 Framework for UHDTCS
+
+## 7.1 Summary
+
+The technical requirement of UHDTCS specifies the overall system framework and communication framework for streaming the media service system, to maintain the conception model consistency of UHDTCS in the process of designing, development and application.
+
+## 7.2 Overall system framework
+
+UHDTCS should include the teleconsulting terminal system (TCTS), ultra-high-definition streaming media (UHDSM) service system, backend business system (BBS), mobile control terminal (MCT) and gateway as shown in Figure 1.
+
+![Figure 1 – Overall system framework for UHDTCS. The diagram shows five components: Gateway, TCTS, UHDSM service system, BBS, and MCT. The Gateway is on the left, connected to the other four components. The other four components are arranged in a 2x2 grid: TCTS (top-left), MCT (top-right), UHDSM service system (bottom-left), and BBS (bottom-right).](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg)
+
+```
+graph LR; Gateway[Gateway] --- TCTS[TCTS]; Gateway --- UHDSM[UHDSM service system]; Gateway --- BBS[BBS]; Gateway --- MCT[MCT]; TCTS --- UHDSM; TCTS --- BBS; UHDSM --- BBS; MCT --- TCTS; MCT --- UHDSM; MCT --- BBS;
+```
+
+F.780.3(22)
+
+Figure 1 – Overall system framework for UHDTCS. The diagram shows five components: Gateway, TCTS, UHDSM service system, BBS, and MCT. The Gateway is on the left, connected to the other four components. The other four components are arranged in a 2x2 grid: TCTS (top-left), MCT (top-right), UHDSM service system (bottom-left), and BBS (bottom-right).
+
+**Figure 1 – Overall system framework for UHDTCS**
+
+Each part of the system is briefly introduced as follows:
+
+- a) TCTS: It consists of at least a ultra-high definition (UHD) camera/display equipment, high quality audio record/display equipment, real time message display equipment, and a UHDSM distribution equipment which can support interoperation, relative business functions, and equipment management functions of TCTS;
+- b) UHDSM service system: It provides essential streaming media service support to UHDTCS, which includes the bidirectional transmission of the UHDSM data;
+- c) BBS: It should consist of a hospital business management, equipment management, consultation task management, and provide services such as doctor resource management, equipment information and status management, consultation statistics and clinic appointment to the UHDTCS;
+- d) MCT: It provides the controlling function support to the TCTS, BBS, and UHDSM service system. It should control the business and equipment of the UHD teleconsulting, ensuring that each part of the UHDTCS completes the consultation process co-ordinately, simply, efficiently and intelligently;
+- e) Gateway: It runs through the other parts of the UHDTCS, and should consist of a switch, router and a 4G / 5G wireless equipment, providing essential hardware support to the network connection of the UHD teleconsulting.
+
+## 7.3 Communication framework for streaming media service system
+
+The communication framework for streaming media service system consists of four subsystems, which are TCTS, BBS, MCT, and UHDSM service system. The functions of each subsystem are as follows:
+
+- a) TCTS: to provide collection, codec, and display/play of a UHD video and high definition audio, as well as the streaming media service of an uplink / downlink transmission with the UHDSM service system;
+
+- b) BBS: to provide registration, store consultation task information, and create streaming media virtual consultation room;
+- c) MCT: to show and enter consultation task, initiate and make the connection of the UHD teleconsulting;
+- d) UHDSM service system: to provide uplink / downlink and transmission of a UHDSM live broadcast and realise the seamless connection of the streaming media service.
+
+The four subsystems can realise the construction and operation of the UHDTCS through eight processes shown in Figure 2.
+
+![Figure 2 – Framework for system communication logic. The diagram shows four main components: MCT (Demand), BBS, MCT (Reception), and UHDSM service system, along with TCTS (Demand) and TCTS (Reception). Arrows indicate the flow of information between these components, numbered 1 through 8. Process 1: MCT (Demand) to BBS. Process 2: MCT (Reception) to BBS. Process 3: BBS to MCT (Demand) and MCT (Reception). Process 4: BBS to UHDSM service system. Process 5: BBS to TCTS (Demand) and TCTS (Reception). Process 6: TCTS (Demand) and TCTS (Reception) to UHDSM service system. Process 7: UHDSM service system to TCTS (Demand) and TCTS (Reception). Process 8: TCTS (Demand) to TCTS (Reception).](e9314c83043183351ed74908e9bf2f90_img.jpg)
+
+```
+
+graph TD
+    MCT_Demand[MCT (Demand)] -- 1 --> BBS
+    MCT_Reception[MCT (Reception)] -- 2 --> BBS
+    BBS -- 3 --> MCT_Demand
+    BBS -- 3 --> MCT_Reception
+    BBS -- 4 --> UHDSM[UHDSM service system]
+    BBS -- 5 --> TCTS_Demand[TCTS (Demand)]
+    BBS -- 5 --> TCTS_Reception[TCTS (Reception)]
+    TCTS_Demand -- 6 --> UHDSM
+    TCTS_Reception -- 6 --> UHDSM
+    UHDSM -- 7 --> TCTS_Demand
+    UHDSM -- 7 --> TCTS_Reception
+    TCTS_Demand -- 8 --> TCTS_Reception
+  
+```
+
+Figure 2 – Framework for system communication logic. The diagram shows four main components: MCT (Demand), BBS, MCT (Reception), and UHDSM service system, along with TCTS (Demand) and TCTS (Reception). Arrows indicate the flow of information between these components, numbered 1 through 8. Process 1: MCT (Demand) to BBS. Process 2: MCT (Reception) to BBS. Process 3: BBS to MCT (Demand) and MCT (Reception). Process 4: BBS to UHDSM service system. Process 5: BBS to TCTS (Demand) and TCTS (Reception). Process 6: TCTS (Demand) and TCTS (Reception) to UHDSM service system. Process 7: UHDSM service system to TCTS (Demand) and TCTS (Reception). Process 8: TCTS (Demand) to TCTS (Reception).
+
+**Figure 2 – Framework for system communication logic**
+
+As shown in Figure 2, the process number indicates the business sequence during the communication framework, and the same number indicates the simultaneous business. The detailed businesses of each process are as follows:
+
+- a) Process 1: The demand side initiates a UHD teleconsulting request to BBS by MCT;
+- b) Process 2: The reception side returns the treatment result to BBS by MCT;
+- c) Process 3: Communications have been established between TCTS and BBS for both the demand side and the reception side;
+- d) Process 4: Communication has been established between BBS and the UHDSM service system;
+- e) Process 5: BBS distributes information of the allocated UHDSM service system to TCTSs of both the demand and the reception side;
+- f) Process 6: Communications have been established between TCTS and the UHDSM service system for both the demand side and the reception side;
+- g) Process 7: TCTSs of the demand side and the reception side send the UHDSM data to the UHDSM service system;
+- h) Process 8: UHDSM service system provides UHDSM data to TCTSs of the demand side and reception side.
+
+# 8 Function requirements for UHDTCS
+
+## 8.1 Summary
+
+This Recommendation specifies the functions of the UHDTCS from the following five aspects: BBS, UHDSM service system, TCTS, MCT and gateway.
+
+## **8.2 BBS**
+
+### **8.2.1 Hospital business management**
+
+To ensure the efficient inquiry and effective management of the hospital information about the UHD teleconsulting business, the hospital business management of the backend business system (BBS) should include the following functions:
+
+- a) To create, edit, delete, distribute, record and inquire about the information of the hospital, department, consultation room, equipment and the doctors;
+- b) To create the management mechanism of the roles and the authorities;
+- c) To arrange and show the reception time, period (monthly or weekly), fees, patient residual number, and open the consultation appointment (such as emergency treatment, teleconsulting, etc.);
+- d) To register, edit, delete, and store the patient information (support both new creation and import from the hospital information system (HIS) system);
+- e) To accept / refuse the consultation task, initiate / end the operation, and record the diagnosis suggestion for the patients;
+- f) The consultation task information includes but is not limited to consultation time, doctor information, consultation content, contact methods of both sides, consultation status, patient information (name, age, sex, disease history, etc.), and doctor application;
+- g) To count, maintain and manage the gradual relevant number of hospitals, departments, consultation rooms and doctors;
+- h) To record, show, and print the electronic medical record (EMR) (handwritten or scanned), edit the consultation report, and store the EMR information on the cloud server.
+
+### **8.2.2 Equipment management**
+
+To monitor and manage the UHDTCS equipment in a unified way, the equipment management of BBS should include the following functions:
+
+- a) To register and authorise the equipment of UHDTCS;
+- b) To edit and delete the authorised equipment information;
+- c) To monitor the authorised equipment status.
+
+### **8.2.3 Teleconsulting task management**
+
+#### **8.2.3.1 Management of teleconsulting appointment**
+
+To ensure the efficiency, reasonability and operability of the consultation appointment management service. The management of the teleconsulting appointments of the BBS should include the following functions:
+
+- a) To support appointment initiation of point-to-point teleconsulting task;
+- b) To show the consultation task to be responded to by a relative director, who can add, delete, revise, respond, remark, transmit, hang up and trace the consultation task;
+- c) To trace the participated and initiated task information, including but not limited to consultation participant, time and results (besides the relevant information of the diagnosis);
+- d) Higher level doctors or managers can overrule the operation by management service according to the consultation reality, and require a lower doctor to supplement the relative material;
+- e) Higher level doctors or managers can require third party doctors by management service according to the patient's reality, and feedback the coordinated time and place to the service originator;
+
+- f) To support consultation fee settlement, online payment is more suitable.
+
+#### **8.2.3.2 Management of the teleconsulting process and files**
+
+To ensure the efficiency, reasonability and operability of the management of the consultation process and the relative files, the management of the consultation process and files of the BBS should include the following functions:
+
+- a) To inquire, edit and delete the consultation record;
+- b) To support ordinary teleconsulting mode and emergence teleconsulting mode. Only the former should be limited by a doctor appointment arrangement and a patient residual number;
+- c) To support the teleconsulting platform to manage the hospital authority in a unified way, including but not limited to hospital reception qualification, doctor arrangement situation, inquiry of patient medical record, consultation procedure initiation, and other account authority;
+- d) The upper / lower-level hospital can decide whether to use video function or not depending on the reality of the patient;
+- e) To connect to the UHDSM service, and support the monitoring and management of the local / cloud service room;
+- f) To support the data statistics overview of teleconsulting service usage, offer the statistics report service from the dimensions of the doctor's arrangement, consultation task, and equipment usage.
+
+## **8.3 UHDSM service system**
+
+To ensure to offer a stable, efficient, and high-quality streaming media service to the UHDTCS, the UHDSM service system should include the following functions:
+
+- a) To codec and transmit the UHD video and high-quality audio;
+- b) To ensure the bidirectional transmission of the UHD video and high-quality audio between the service system and the TCTS;
+- c) To monitor the logic and transmission of a live broadcast of both UHDSM and the virtual consultation room;
+- d) To monitor the user status of UHDTCS and the transmission reliability of the UHDSM.
+
+## **8.4 TCTS**
+
+To ensure the operability and support of the UHDSM multimedia display, the teleconsulting terminal system (TCTS) should include the following functions:
+
+- a) To have a highly efficient and high quality codec, uplink and downlink bidirectionally transmit, multichannel UHDSM display, UHDSM recorded by a multichannel UHD camera and a high quality audio recorder;
+- b) The equipment can be registered, recognised by MCT, and can accept the operation instructions sent by the MCT;
+- c) To display UHDSM and a high-quality audio, switch and split display UHD video;
+- d) To support ordinary maintenance operations such as software upload and debugging;
+- e) The equipment information can be registered into BBS;
+- f) To monitor the usage status of the equipment in the terminal system;
+- g) To prompt the network disconnection and monitor the network recovery.
+
+## 8.5 MCT
+
+To provide a convenient, efficient and stable control operation, the mobile control terminal (MCT) system should include the following functions:
+
+- a) To support log in with an account and password;
+- b) To support auto start control application, display consultation form interface after login, inquire and display the task card, calendar, and task status (such as not started, in process, ended and expired);
+- c) To configure relative parameters through the control application interface, the parameters include but are not limited to the IP address of the MCT, mobile control icon and server IP address of the UHD remote control system;
+- d) To operate the system on an information level, the operations include but are not limited to equipment registration, information editing, usage authority distribution, upgrading and maintenance, daily record traceability and parameter setting;
+- e) To initiate real time response instruction, monitor relative business information, and mark undone tasks every day;
+- f) To support control application auto renew and upgrading;
+- g) To inquire about the detail of the to-be-consulted list, which include but is not limited to consultation time, doctor, report the status of terminal and content;
+- h) To control the consultation process which include but is not limited to the initiation, ending, acceptance and push of the consultation video;
+- i) To control accessory equipment and their functions of TCTS, which include but is not limited to volume adjustment, the video window and video source shift;
+- j) To support the sequence arrangement of the doctor and consultation room;
+- k) To support the disease description of the patient and display of the case result;
+- l) When connections have been established among many TCTS in the same consultation task, each system can control the camera focal distance and veer off the others by the corresponding MCT;
+- m) To share the UHD video and high-quality audio recorded by any TCTS with the other TCTSs in the same consultation task by the corresponding MCT;
+- n) To push the case, patient test information and pictures of other TCTS to corresponding TCTS one key;
+- o) Gesture control is encouraged in the MCT to adjust the luminance, size, zooming, shift and erasure.
+
+## 8.6 Gateway
+
+The gateway should control the data transmission authority of the UHDSM and other businesses as well as the access authority of all the connections in the UHDTCS.
+
+# 9 Performance requirements for UHDTCS
+
+## 9.1 General
+
+The performance requirements for UHDTCS will be regulated on five aspects: BBS, UHDSM service system, TCTS, MCT and gateway.
+
+## 9.2 BBS
+
+The backend business system (BBS) shall ensure the following performance requirements:
+
+- Support 24-hour stable and reliable operation;
+- Stably support the concurrent amount of teleconsultation business of no less than 100 orders of magnitude.
+
+## 9.3 UHDSM service system
+
+The UHDSM service system shall ensure the following performance requirements:
+
+- Support 24-hour stable and reliable operation;
+- Stably support the concurrent amount of teleconsultation business of no less than 100 orders of magnitude;
+- Support different streaming media protocols, including but not limited to Microsoft media server protocol (MMS), real-time transport protocol (RTP) / real-time streaming protocol (RTSP), real-time messaging protocol (RTMP);
+- The delay of the UHDSM service provided in the network environment shall be guaranteed to be a millisecond. The UHDSM service can transmit UHDSM with high quality and efficiency according to the specifications of the ultra-high-definition video and high-definition audio specified in clauses 9.4.4 and 9.4.5;
+- Support multi-channel and multi-party simultaneous UHD teleconsultation business.
+
+## 9.4 Teleconsulting terminal system
+
+### 9.4.1 UHD video display equipment
+
+#### 9.4.1.1 Work and storage environment
+
+To ensure the normal work and good storage of the UHD video display equipment, the corresponding environmental requirements given in Table 1 shall be met.
+
+**Table 1 – The work and storage environment requirements**
+
+| No. | Parameters                | Specifications | Units            | Notes         |
+|-----|---------------------------|----------------|------------------|---------------|
+| 1   | Working temperature       | 5 ~ 35         | Celsius          | –             |
+| 2   | Working relative humidity | 10% ~ 90%      | –                | Noncondensing |
+| 3   | Maximum humidity gradient | 10             | Percent per hour | –             |
+| 4   | Storage temperature       | –20 ~ 60       | Celsius          | –             |
+| 5   | Storage relative humidity | 10% ~ 90%      | –                | Noncondensing |
+| 6   | Working altitude          | –16 ~ 3 048    | Metre            | –             |
+| 7   | Storage altitude          | –16 ~ 10 600   | Metre            | –             |
+| 8   | Loadability margin        | 7 × 24         | Hour per week    | –             |
+
+#### 9.4.1.2 Battery and efficiency
+
+To ensure normal operation and power consumption control, the requirements of the battery given in Table 2 shall be met.
+
+**Table 2 – The battery requirements of the UHD video display equipment**
+
+| No. | Parameters          | Specifications | Units |
+|-----|---------------------|----------------|-------|
+| 1   | Voltage             | AC 96 ~ 264    | Volt  |
+| 2   | Frequency           | 50/60          | Hertz |
+| 3   | Working power       | 220 ~ 380      | Watt  |
+| 4   | Standby power       | $\leq 0.8$     | Watt  |
+| 5   | Transfer efficiency | $\geq 83\%$    | –     |
+
+#### 9.4.1.3 Electromagnetic compatibility
+
+To ensure that the UHD video display equipment can operate safely in the complex electromagnetic environment, the electromagnetic compatibility test results of the UHD video display equipment should comply with the requirements of [ITU-T K.116].
+
+#### 9.4.1.4 UHD display
+
+To meet the display demand of a large amount of data for the consultation terminal system during the process of the teleconsulting business, the display device can frequently split screens and change screens stably and reliably for a long time.
+
+To ensure that the UHD video display equipment can display the consultation video / image content with high quality and ultra-high definition, the display performance requirements given in Table 3 should be met.
+
+**Table 3 – Performance requirements of a photoelectric display for UHD display equipment**
+
+| No. | Parameters                    | Specifications                   | Units             |
+|-----|-------------------------------|----------------------------------|-------------------|
+| 1   | Resolution                    | $\geq 3\,840 \times 2\,160$      | Pixel             |
+| 2   | Luminance                     | $\geq 340$                       | cd/m <sup>2</sup> |
+| 3   | Contrast ratio                | $\geq 800:1$                     | –                 |
+| 4   | Luminance uniformity          | $\geq 75\%$                      | –                 |
+| 5   | Colour gamut                  | $\geq 72\%$                      | –                 |
+| 6   | Response time                 | $\leq 12$                        | ms                |
+| 7   | Viewing angle range           | H : $\geq 178$<br>V : $\geq 178$ | Degree            |
+| 8   | White chromaticity uniformity | $\leq 0.01$                      | –                 |
+| 9   | Bright picture sticking       | $\leq 1$                         | –                 |
+| 10  | Dark picture sticking         | $\leq 1$                         | –                 |
+| 11  | Darkroom contrast ratio       | $\geq 3\,000:1$                  | –                 |
+| 12  | Light leakage                 | $\leq 0.5$                       | cd/m <sup>2</sup> |
+| 13  | Display format                | Conform                          | –                 |
+| 14  | Dark field uniformity         | $\geq 70\%$                      | –                 |
+
+#### 9.4.1.5 UHD video acquisition equipment
+
+To ensure the quality of the video acquired by the consultation terminal system, the UHD acquisition equipment of the system should meet the following requirements.
+
+**Table 4 – The core performance requirements**
+
+| No. | Parameters                   |            | Specifications              | Units  | Notes        |
+|-----|------------------------------|------------|-----------------------------|--------|--------------|
+| 1   | Resolution                   |            | $\geq 3\,840 \times 2\,160$ | Pixel  |              |
+| 2   | Horizontal translation range |            | $\pm 90$                    | Degree | Power-driven |
+| 3   | Vertical translation range   |            | $-30 \sim +30$              | Degree |              |
+| 4   | Zoom                         |            | $\geq 12$                   | Times  |              |
+| 5   | Zoom view                    | Diagonal   | $\geq 90$                   | Degree |              |
+| 6   |                              | Horizontal | $\geq 80$                   | Degree |              |
+| 7   |                              | Vertical   | $\geq 50$                   | Degree |              |
+
+In addition to the performance requirements in the table above, the camera shall be compatible with the mainstream video conference, recording and broadcast applications.
+
+In order to facilitate the real-time control of the UHD video acquisition equipment, the equipment shall support to be controlled remotely by the mobile control terminal.
+
+### 9.4.2 High fidelity audio acquisition equipment
+
+#### 9.4.2.1 Working environment
+
+To ensure the normal work and good storage of the high fidelity audio acquisition equipment, the corresponding environmental requirements in the following table shall be met.
+
+**Table 5 – The work and storage environment requirements**
+
+| No. | Parameters                | Specifications   | Units   | Notes         |
+|-----|---------------------------|------------------|---------|---------------|
+| 1   | Working temperature       | $5 \sim 40$      | Celsius |               |
+| 2   | Working relative humidity | $20\% \sim 85\%$ | –       | Noncondensing |
+| 3   | Noise level               | $< 48$           | dB      |               |
+| 4   | Storage temperature       | $-10 \sim 40$    | Celsius |               |
+| 5   | Reverberation time        | $< 0.5$          | Second  |               |
+
+#### 9.4.2.2 Acquisition performance
+
+To ensure the high fidelity and convenience of teleconsulting voice collection, the audio acquisition equipment shall guarantee that there are no obvious volume and quality drops in the audio collected in any direction within a radius of three metres and shall support intelligent dynamic noise cancelling technology. Gesture-controlled audio capture switches shall also be supported.
+
+High-fidelity audio acquisition equipment in UHDTCS should meet the performance requirements given in Table 6.
+
+**Table 6 – Performance requirements for high-fidelity audio acquisition equipment**
+
+| No. | Parameters                       | Specifications | Units  |
+|-----|----------------------------------|----------------|--------|
+| 1   | Up-sampling rate                 | $\geq 32$      | kHz/s  |
+| 2   | Down-sampling rate               | $\geq 48$      | kHz/s  |
+| 3   | Direction of audio acquisition   | All            | –      |
+| 4   | Audio bandwidth                  | 20 ~ 16 000    | Hz     |
+| 5   | Sensitivity of audio acquisition | $\leq -30$     | dB     |
+| 6   | Signal-to-noise ratio (SNR)      | $\geq 60$      | dB     |
+| 7   | Echo cancellation                | $< 390$        | ms     |
+| 8   | Quantization accuracy            | $\geq 16$      | bit    |
+| 9   | Sound channel number             | 2              | –      |
+| 10  | Code rate                        | $\geq 70$      | kbit/s |
+
+### 9.4.3 UHD streaming media distribution equipment
+
+To ensure the high-quality display of the collected UHDSM on multiple TCTS, the performance requirements given in Table 7 should be met.
+
+**Table 7 – The core performance requirements of UHDSM distribution equipment**
+
+| No. | Parameters              | Specifications                                                     | Units | Note                                              |
+|-----|-------------------------|--------------------------------------------------------------------|-------|---------------------------------------------------|
+| 1   | Input resolution        | $\geq 3\,840 \times 2\,160$                                        | Pixel |                                                   |
+| 2   | Recording resolution    | $\geq 3\,840 \times 2\,160$                                        | Pixel |                                                   |
+| 3   | Output resolution       | $\geq 3\,840 \times 2\,160$                                        | Pixel |                                                   |
+| 4   | Recording format        | Equal to or better than the existing mainstream recording formats. |       |                                                   |
+| 5   | Frame rate of recording | $\geq 30$                                                          |       | The resolution shall meet Article 2 of the table. |
+| 6   | Frame rate of output    | $\geq 60$                                                          |       | The resolution shall meet Article 3 of the table. |
+
+### 9.4.4 UHD video encoding/decoding
+
+The performance of the codec scheme adopted by the UHD video shall be equal to or better than the existing mainstream UHD video codec technology.
+
+### 9.4.5 High fidelity audio encoding/decoding
+
+The performance of the codec scheme adopted by the microphone and the audio player shall be equal to or better than the existing mainstream high fidelity audio codec technology.
+
+### 9.4.6 Acquisition and transmission of UHD video and high fidelity audio
+
+#### 9.4.6.1 UHD video and high-fidelity audio acquisition
+
+The performance requirements of the UHD video acquisition shall not be less than:
+
+- Resolution rate:  $3\,840 \times 2\,160$  pixels.
+- Frame rate: 25 frames/s, 30 frames/s is recommended.
+
+c) Code rate: 15 Mbit/s.
+
+If the acquisition setting of high-definition audio acquisition equipment is adjustable, the acquisition should be carried out under the optimal setting.
+
+#### 9.4.6.2 UHD video and high fidelity audio transmission
+
+It shall support the bidirectional real-time transmission of the UHDSM in the network environment and support the network jitter control.
+
+The audio of the TCTS shall be guaranteed to be high quality and high fidelity, and the audio code rate shall not be less than 15 Mbit/s.
+
+### 9.4.7 Streaming media transmission protocol
+
+It shall support the protocols including but not limited to MMS, RTP/RTSP, real-time transport control protocol (RTCP), and RTMP.
+
+It shall be consistent with the communication protocol of the streaming media server and real-time UHD multi-media cloud.
+
+## 9.5 MCT
+
+The screen size of the mobile control terminal (MCT) should not be less than 10 inches and the screen resolution should not be less than 1 920 × 1 080 pixels.
+
+The control application of the MCT shall aim to be the control software for the TCTS. The operation response speed shall be at a millisecond level and it shall guarantee that the users have no obvious feeling of stagnation.
+
+## 9.6 Gateway
+
+### 9.6.1 Working environment
+
+To ensure the normal operation of gateway equipment, the corresponding environmental requirements given in Table 8 shall be met.
+
+**Table 8 – The work and storage environment requirements**
+
+| No. | Parameters                | Specifications | Units   | Notes         |
+|-----|---------------------------|----------------|---------|---------------|
+| 1   | Working temperature       | 0 ~ 40         | Celsius |               |
+| 2   | Working relative humidity | 10% ~ 90%      |         | Noncondensing |
+| 3   | Storage temperature       | -40 ~ 70       | 11 111  |               |
+
+### 9.6.2 Performance requirements
+
+The gateway shall support all types of gigabit network equipment, gigabit network interfaces and data transmission protocols.
+
+The gateway shall ensure that the wireless speed is no less than one gigabit. It shall have a gigabit WAN interface, wide area network (WAN) / local area network (LAN) variable interfaces and LAN interfaces.
+
+## 9.7 Security requirements
+
+### 9.7.1 General
+
+To ensure the security of communication and data transmission in the UHDTCS, it will be regulated from four aspects: login management, transmission security, data security and key management.
+
+### **9.7.2 Login management**
+
+The requirements of login management shall comply with the requirements of [ISO/IEC 27002], including but not limited to user registration, user privilege management, user password management, password use, equipment login verification and network service access.
+
+### **9.7.3 Transmission security**
+
+The protocol and process of data transmission security shall comply with the requirements of [ISO/IEC 27002].
+
+### **9.7.4 Data security**
+
+In addition to patient data (including but not limited to user information, consultation purpose, consultation plan, etc.), the data generated during teleconsultation shall be encrypted and stored in the TCTS.
+
+Control measures and implementation of data encryption shall comply with the requirements of [ISO/IEC 27002].
+
+### **9.7.5 Key management**
+
+The requirements of key management shall comply with the requirements of [ISO/IEC 27002].
+
+# Appendix I
+
+## Use cases for UHDTCS
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This Recommendation can support two use cases of teleconsultation, which are scheduled teleconsultation and emergency treatment teleconsultation.
+
+## I.1 Use case 1: Scheduled teleconsultation
+
+![Flowchart of the process of scheduled teleconsultation](a24e89a6fe9bb70c83f8bf5202baba95_img.jpg)
+
+```
+graph LR; A["Demander launches teleconsultation requirement"] --> B["Enquiry of available reception experts and room"]; B --> C["Start of teleconsultation"]; C --> D["End of teleconsultation and release resources"];
+```
+
+The diagram is a horizontal flowchart with four rectangular boxes connected by arrows from left to right. The first box contains 'Demander launches teleconsultation requirement'. The second box contains 'Enquiry of available reception experts and room'. The third box contains 'Start of teleconsultation'. The fourth box contains 'End of teleconsultation and release resources'. Below the fourth box, the text 'F.780.3(22)' is written.
+
+Flowchart of the process of scheduled teleconsultation
+
+**Figure I.1 – Process of scheduled teleconsultation**
+
+As shown in Figure I.1, the process of a scheduled teleconsultation consists of four steps, in turn, each step and its requirements are as follows:
+
+- 1) The demander (e.g., medical doctor) launches a teleconsultation application. Before launching the teleconsultation, the demander shall confirm the available teleconsulting room of the hospital, the exact time of the teleconsultation, the conditions of the required equipment, department, and the number of the reception experts.
+- 2) UHDTCS searches the relevant experts (e.g., other doctors) according to the requirement. The hospital providing the teleconsultation shall update the available time of reception experts and the information on unoccupied consultation rooms in the UHDTCS in time.
+- 3) Teleconsultation starts.
+- 4) Release the teleconsulting resources at the end of the teleconsultation, such as room status and the available experts.
+
+## I.2 Use case 2: Emergency treatment teleconsultation
+
+The process and requirements of emergency treatment teleconsultation are similar to those of a scheduled teleconsultation, if the emergency treatment teleconsultation is in real time, the UHDTCS shall support the sending of temporary invitations to all the experts of the target departments.
+
+A temporary invitation is a message that is sent to the relevant experts by the system before the emergency treatment teleconsultation, e.g., a message informs the experts that the teleconsultation will start in a short time. Idle experts can directly participate in the consultation.
+
+# Bibliography
+
+- [b-ITU-T F.780.1] Recommendation ITU-T F.780.1 (2022), *Framework for telemedicine systems using ultra-high definition imaging*.
+- [b-ITU-T K.127] Recommendation ITU-T K.127 (2017), *Immunity requirements for telecommunication equipment in close proximity use of wireless devices*.
+- [b-ISO 354:2003] ISO 354:2003, *Acoustics – Measurement of sound absorption in a reverberation room*.  
+<<https://www.iso.org/standard/34545.html>>
+- [b-ISO 21250-3] ISO 21250-3:2020, *Rolling bearings – Noise testing of rolling bearing greases – Part 3: Test and evaluation method MQ*.  
+<<https://www.iso.org/standard/72363.html>>
+- [b-IEC 60050-531] IEC 60050-531:1974/AMD2:2020, *Amendment 2 – International Electrotechnical Vocabulary (IEV) – Part 531: Electronic tubes*.  
+<<https://webstore.iec.ch/publication/66855>>
+- [b-IEC 60050-704] IEC 60050-704:1993/AMD3:2018, *Amendment 3 – International Electrotechnical Vocabulary (IEV) – Part 704: Transmission*.  
+<<https://webstore.iec.ch/publication/63918>>
+- [b-IEC 60050-841] IEC 60050-841:2004/AMD1:2021, *Amendment 1 – International Electrotechnical Vocabulary (IEV) – Part 841: Industrial electroheat*.  
+<<https://webstore.iec.ch/publication/68734>>
+- [b-IEC 60050-845] IEC 60050-845:2020, *International Electrotechnical Vocabulary (IEV) – Part 845: Lightning*.  
+<<https://webstore.iec.ch/publication/26592>>
+- [b-ISO/IEC 23008-10] ISO/IEC 23008-10:2015, *Information technology – High efficiency coding and media delivery in heterogeneous environments – Part 10: MPEG media transport forward error correction (FEC) codes*.  
+<<https://www.iso.org/standard/63980.html>>
+- [b-IEC/TR 80001-2-3] IEC/TR 80001-2-3:2012, *Application of risk management for IT-networks incorporating medical devices – Part 2-2: Guidance for wireless networks*.  
+<<https://www.iso.org/standard/57941.html>>
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.780.4-202309-I_PDF-E/raw.md b/marked/F/T-REC-F.780.4-202309-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..31a288fb787e7ee59dd1cef72d28902599452d70
--- /dev/null
+++ b/marked/F/T-REC-F.780.4-202309-I_PDF-E/raw.md
@@ -0,0 +1,951 @@
+
+
+Recommendation
+
+**ITU-T F.780.4 (09/2023)**
+
+SERIES F: Non-telephone telecommunication services
+
+Multimedia services
+
+---
+
+**Reference framework, requirements and  
+scenarios for telemedicine systems**
+
+![ITU logo](84a1d09fb489061482111515543b60dc_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 the letters 'ITU' in a bold, blue, sans-serif font. The globe is stylized with a white arrow pointing upwards and to the right, symbolizing global connectivity and communication.
+
+ITU logo
+
+# ITU-T F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## Recommendation ITU-T F.780.4
+
+## Reference framework, requirements and scenarios for telemedicine systems
+
+## Summary
+
+Recommendation ITU-T F.780.4 describes the reference framework, requirements and scenarios of telemedicine systems. A telemedicine system is an important application of ICT in the medical field, especially against a background of unbalanced medical resources, and can realize the optimal allocation of medical resources and benefit people in areas with less developed medical resources.
+
+It recommends the framework, functional requirements and scenarios of telemedicine systems, i.e. the necessary hardware and software foundations for telemedicine.
+
+The Recommendation is suitable for the development, construction and evaluation of telemedicine systems in various countries and regions.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.780.4  | 2023-09-13 | 16          | 11.1002/1000/15628 |
+
+## Keywords
+
+Framework, requirements, scenarios, telemedicine.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 Introduction .....                                                | 3    |
+| 7 Reference framework of telemedicine systems .....                 | 4    |
+| 8 Functions and technical requirements of telemedicine systems..... | 5    |
+| 8.1 Application layer .....                                         | 5    |
+| 8.2 Service layer .....                                             | 10   |
+| 8.3 Resource layer .....                                            | 12   |
+| 8.4 Information exchange layer .....                                | 12   |
+| 8.5 Network layer .....                                             | 13   |
+| 8.6 Video audio system .....                                        | 14   |
+| 8.7 Security guarantee .....                                        | 18   |
+| Appendix I – Application scenarios for telemedicine.....            | 21   |
+| I.1 Scenario 1: Remote disease re-examination.....                  | 21   |
+| I.2 Scenario 2: Remote surgery teaching .....                       | 21   |
+| I.3 Scenario 3: Remote intensive care .....                         | 21   |
+| I.4 Scenario 4: Remote post-hospital management .....               | 21   |
+| Bibliography.....                                                   | 22   |
+
+
+
+## Reference framework, requirements and scenarios for telemedicine systems
+
+# 1 Scope
+
+This Recommendation describes the reference framework, requirements and scenarios for telemedicine systems. The scope of this Recommendation includes:
+
+- Reference framework for telemedicine systems;
+- Functions and technical requirements for telemedicine systems;
+- Scenarios for telemedicine systems.
+
+The reference framework and requirements given in this Recommendation is recommended not to be taken as restrictive.
+
+# 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.164] Recommendation ITU-T E.164 (2010), *The international public telecommunication numbering plan*.
+- [ITU-T G.711] Recommendation ITU-T G.711 (1988), *Pulse code modulation (PCM) of voice frequencies*.
+- [ITU-T G.719] Recommendation ITU-T G.719 (2008), *Low-complexity, full-band audio coding for high-quality, conversational applications*.
+- [ITU-T G.722] Recommendation ITU-T G.722 (2012), *7 kHz audio-coding within 64 kbit/s*.
+- [ITU-T G.722.1] Recommendation ITU-T G.722.1 (2005), *Low-complexity coding at 24 and 32 kbit/s for hands-free operation in systems with low frame loss*.
+- [ITU-T G.728] Recommendation ITU-T G.728 (2012), *Coding of speech at 16 kbit/s using low-delay code excited linear prediction*.
+- [ITU-T G.729] Recommendation ITU-T G.729 (2017), *Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited linear prediction (CS-ACELP)*.
+- [ITU-T H.235] Recommendation ITU-T H.235 (2005), *Security and encryption for H-Series (H.323 and other H.245-based) multimedia terminals*.
+- [ITU-T H.239] Recommendation ITU-T H.239 (2014), *Role management and additional media channels for ITU-T H.300-series terminals*.
+- [ITU-T H.261] Recommendation ITU-T H.261 (1993), *Video codec for audiovisual services at  $p \times 64$  kbit/s*.
+- [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 (2021), <i>Advanced video coding for generic audiovisual services</i> . |
+| [ITU-T H.323] | Recommendation ITU-T H.323 (2022), <i>Packet-based multimedia communications systems</i> .         |
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following term defined elsewhere:
+
+**3.1.1 telemedicine** [b-WHO]: The delivery of health-care services, where distance is a critical factor, by all health-care professionals using information and communication technologies for the exchange of valid information for diagnosis, treatment and prevention of disease and injuries, research and evaluation, and for continuing education of healthcare providers, all in the interests of advancing the health of individuals and their communities.
+
+NOTE – Tele-health, also known as e-health, is different from telemedicine because it refers to a broader scope of remote health care services than telemedicine. While telemedicine refers specifically to remote clinical services, tele-health can refer to remote non-clinical services, such as provider training, administrative meetings, and continuing medical education, in addition to clinical services [b-HealthIT.gov].
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 telemedicine system**: An information system which can realize remote collection, transmission, processing, storage and query of medical information, and provide remote patient consultation, guardianship, ward round, assist diagnosis, guide examination, treatment, operation, teaching, information service and other special medical activities of the information system.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|        |                                                |
+|--------|------------------------------------------------|
+| AAC-LD | Advanced Audio Coding, Low Delay               |
+| AES    | Advanced Encryption Standard                   |
+| BFCP   | Binary Floor Control Protocol                  |
+| B/S    | Browser/Server                                 |
+| CIF    | Common Intermediate Format                     |
+| DDoS   | Distributed Denial-of-Service                  |
+| DICOM  | Digital Imaging and Communications in Medicine |
+| DNS    | Domain Name System                             |
+| ECG    | Electrocardiogram                              |
+| EMR    | Electronic Medical Records                     |
+| ESB    | Enterprise Service Bus                         |
+| ETL    | Extract-Transform-Load                         |
+| FPS    | Frame Per Second                               |
+| GK     | Gate Keeper                                    |
+| GTP    | General data Transfer Platform                 |
+
+|         |                                              |
+|---------|----------------------------------------------|
+| HD      | High Definition                              |
+| HDMI    | High-Definition Multimedia Interface         |
+| HIS     | Hospital Information System                  |
+| HL7     | Health Level Seven                           |
+| HTTPS   | Hypertext Transfer Protocol Secure           |
+| IHE     | Integrating the Healthcare Enterprise        |
+| IPSec   | Internet Protocol Security                   |
+| IPv4    | Internet Protocol version 4                  |
+| IPv6    | Internet Protocol version 6                  |
+| LDAP    | Lightweight Directory Access Protocol        |
+| LED     | Light Emitting Diode                         |
+| MAC     | Media Access Control                         |
+| MCU     | Multicontrol Unit                            |
+| QoS     | Quality of Service                           |
+| SIP     | Session Initiation Protocol                  |
+| SMP     | Symmetrical Multiprocessing                  |
+| SNMP    | Simple Network Management Protocol           |
+| SRTP    | Secure Real-time Transport Protocol          |
+| SSH     | Secure Shell                                 |
+| SSL VPN | Secure Sockets Layer Virtual Private Network |
+| SVC     | Scalable Video Coding                        |
+| TLS     | Transport Layer Security                     |
+| VLAN    | Virtual Local Area Network                   |
+| VPN     | Virtual Private Network                      |
+
+## 5 Conventions
+
+None.
+
+# 6 Introduction
+
+Telemedicine is the use of telecommunications technology, holographic imaging technology, new electronic technology and computer multimedia technology to provide, enhance or expedite health care services by accessing off-site databases, linking clinics or physicians' offices to central hospitals or transmitting X-ray or other diagnostic images for examination at another site.
+
+Telemedicine will be the main trend of the future development of the medical and health industry. It not only reduces the cost of time and space, representing an economy for patients and doctors, but also provides powerful impetus and technical support for optimizing the allocation of medical resources worldwide and for building a more equal and better world.
+
+## 7 Reference framework of telemedicine systems
+
+The reference framework of telemedicine systems consists of layers, namely the network layer, information exchange layer, resource layer, service layer and application layer, and the video audio system and security guarantee. Figure 1 shows a typical framework.
+
+![Figure 1: Framework of typical telemedicine system. The diagram shows a layered architecture with five main layers: Application layer, Service layer, Resource layer, Information exchange layer, and Network layer. On the left, a Security guarantee column includes Authentication management, Network security, and Data security. On the right, a Video audio system column includes Business management, Multipoint exchanging, HD, and Recording. External systems (Emergency command system, Medical information system, Medical information acquisition equipment) are connected via the Information exchange layer.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg)
+
+|                           |                          |                                   |                                   |                                                                                                                                        |                                 |                           |
+|---------------------------|--------------------------|-----------------------------------|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|---------------------------|
+| <b>Security guarantee</b> | <b>Application layer</b> | Remote appointment                | Teleconsultation                  | Remote image diagnosis                                                                                                                 | Remote ECG diagnosis            | <b>Video audio system</b> |
+|                           |                          | Remote two-way referral           | Remote medical education          | Remote surgery teaching                                                                                                                | Remote pathology diagnosis      |                           |
+|                           |                          | Remote intense care               | Remote disease re-examination     | Remote prevention and health care                                                                                                      | Remote post-hospital management |                           |
+|                           |                          | <b>Service layer</b>              |                                   |                                                                                                                                        |                                 |                           |
+|                           |                          | Registration service              | Telemedicine data storage service | Index service                                                                                                                          |                                 |                           |
+| <b>Network security</b>   | <b>Resource layer</b>    | Basic information base            |                                   | Telemedicine data base                                                                                                                 |                                 |                           |
+|                           |                          | <b>Information exchange layer</b> |                                   |                                                                                                                                        |                                 |                           |
+|                           |                          | Information transmission          | Data port                         | External systems (dotted line):<br>Emergency command system<br>Medical information system<br>Medical information acquisition equipment |                                 |                           |
+| <b>Data security</b>      | <b>Network layer</b>     | Reliability                       | Open                              |                                                                                                                                        |                                 |                           |
+|                           |                          | Security                          | Manageable                        |                                                                                                                                        |                                 |                           |
+
+F.780.4(23)
+
+Figure 1: Framework of typical telemedicine system. The diagram shows a layered architecture with five main layers: Application layer, Service layer, Resource layer, Information exchange layer, and Network layer. On the left, a Security guarantee column includes Authentication management, Network security, and Data security. On the right, a Video audio system column includes Business management, Multipoint exchanging, HD, and Recording. External systems (Emergency command system, Medical information system, Medical information acquisition equipment) are connected via the Information exchange layer.
+
+**Figure 1 – Framework of typical telemedicine system**
+
+NOTE – In Figure 1, the boxes in the dotted lines refer to external systems.
+
+The functions of each part of the system are described below.
+
+### a) Network layer
+
+The network layer is the network foundation of telemedicine. The network of the telemedicine system is required to be reliable, open, safe and manageable, support the coordination of medical information inside and outside the hospital, ensure the normal work of the audio-video system and realize various applications of the telemedicine.
+
+### b) Information exchange layer
+
+According to the business process, the information exchange layer exchanges data with other information systems through the data interface or message transmission, providing message sharing, data reporting and other functions, meeting the requirements of information exchange and collaborative application of clinical information cross-hospital and cross-region.
+
+The telemedicine system can exchange data with the external emergency command system, medical and health information system and medical-information-collecting devices through the information exchange layer.
+
+### c) Resource layer
+
+The resource layer provides the basic information base and telemedicine database, in which the telemedicine database stores documents, images and videos. The data of the resource layer can be structured data, unstructured data (documents, audio and video materials), structured document data and application service resource, etc. It supports coordinated telemedicine work cross-region, assists
+
+data statistical analysis services and provides information services for the interconnection between telemedicine supervision and resource service centres in various regions.
+
+### **d) Service layer**
+
+The service layer provides services including registration service, storage service and EMR index service, supporting various telemedicine applications in the application layer.
+
+### **e) Application layer**
+
+The application layer provides telemedicine applications including remote appointment, teleconsultation, remote image diagnosis, remote electrocardiogram (ECG) diagnosis, remote two-way referral, remote medical education, remote intensive care, remote surgery teaching, remote pathological diagnosis, remote disease re-examination, remote prevention and health care and remote post-hospital management.
+
+### **f) Video audio system**
+
+The video audio system is the tool to realize various applications of telemedicine and it has the functions of video audio business management, video audio multipoint switching, video audio high-definition access, recording and playing, etc.
+
+### **g) Security guarantee**
+
+The telemedicine system is recommended to ensure the safety of the system through authentication management, network security, data security, etc.
+
+# **8 Functions and technical requirements of telemedicine systems**
+
+## **8.1 Application layer**
+
+The application layer includes, but not limited to, that described in clauses 8.1.1 to 8.1.12.
+
+### **8.1.1 Remote appointment**
+
+#### **8.1.1.1 General**
+
+Remote appointment allows the inviter to complete the appointment registration and appointment inspection and the invitee to complete the relevant application acceptance and information feedback.
+
+#### **8.1.1.2 Basic functions**
+
+The basic functions include:
+
+- a) Appointment arrangement. Fill in the appointment form, query the schedule and select the number source, submit and modify the appointment form, submit the patient's medical records, browse and print the appointment form, etc.
+- b) Appointment management. Manage appointment process, remind appointment process, query appointment record, manage medical record data, etc.
+
+### **8.1.2 Teleconsultation**
+
+#### **8.1.2.1 General**
+
+Teleconsultation is applicable to the process in which the inviter applies to the invitee for teleconsultation, the invitee accepts the invitation, conducts the teleconsultation and gives diagnosis opinions and reports.
+
+#### **8.1.2.2 Basic function**
+
+The basic functions include:
+
+- Consultation appointment. Fill in the application form, submit and modify the consultation application form, query the information of expert database, organize and transmit electronic data, query the consultation application, etc.;
+- Consultation management. Manage consultation process and medical record materials, browse the consultation report, follow-up and evaluate the consultation service, etc.;
+- Consultation service. Browse the medical record materials, discuss the illness with audiovisual interaction, write medical notes on whiteboard and compile and publish consultation reports.
+
+#### **8.1.3 Remote image diagnosis**
+
+#### **8.1.3.1 General**
+
+Remote image diagnosis is applicable to the process in which the inviter applies for remote image diagnosis, the invitee accepts the application, carries out remote image diagnosis and issues diagnosis opinions and reports, and the process that a number of medical institutions in the region are networked to form an image centre for the centralized storage, diagnosis and management of images.
+
+#### **8.1.3.2 Basic functions**
+
+The basic functions include:
+
+- Application. Fill in the application form, submit and modify the consultation application form, query the diagnosis institute and the application, etc.
+- Data sending and receiving. Send and receive different data.
+- Images browsing, enhancement and analysis. Browse, enhance contrast, enhance edge the original image, extract and quantitatively analyse the pathological features, computer-aided diagnosis, image retrieval based on image features.
+- Quality control and statistics. Image quality statistics, technician evaluation, collectively evaluation, report writing quality statistics, overall quality statistics of technician image, report diagnosis quality statistics, etc.
+- Publication, browsing and querying of diagnostic reports.
+- Medical case study. It provides a platform for doctors to study and improve, especially for refresher doctors and interns, who can query and browse the reports they care about, and make comparative study and borrowing.
+
+#### **8.1.4 Remote ECG diagnosis**
+
+#### **8.1.4.1 General**
+
+Remote ECG diagnosis is applicable to the process in which the inviter applies for remote ECG diagnosis, the invitee accepts the invitation, conducts remote ECG diagnosis and issues diagnosis opinions and reports, as well as to the ECG examination requirements of pre-hospital emergency centre.
+
+##### **8.1.4.2 Basic functions**
+
+The basic functions include:
+
+- Application and appointment. Accept the appointment registration and examination registration of patients as well as the registration of patients' examination information, scan and query application forms, and distribute patients' examination reports. Remote EDG diagnosis provides the functions of allocating appointment time for patients, querying appointments within an assigned time period, registering the patient list, scanning and photographing paper application forms and seamlessly connecting with the hospital information system (HIS);
+
+- Analysis and diagnosis. Professional ECG doctors make professional analysis and diagnosis according to the data collected by the ECG equipment. Remote EDG diagnosis provides the functions of instant reminder of the arrival of ECG examination data, analysis of ECG, report writing and printing, management of medical records, etc.;
+- Report browsing and analysis. Remote EDG diagnosis provides the tool for clinician to browse the ECG reports and ECG waveform, e.g., [b-ISO/TS 22077]. The doctor's browsing workstation can be embedded into the outpatient workstation, resident workstation and EMR system, which supports the doctor's browsing workstation and can perform online waveform analysis, processing and measurement.
+
+#### **8.1.5 Remote two-way referral**
+
+##### **8.1.5.1 General**
+
+Remote two-way referral is applicable to the management process of all medical and health service institutions for patients transferred in and out.
+
+##### **8.1.5.2 Basic functions**
+
+The basic functions include:
+
+- Referral application. Respond to the referral request of general practice, other service components or system modules, and submit a referral application to the designated referral institution. Remote two-way referral provides the functions of filling in the referral application form, submitting and modifying the referral application, querying the consultation institution and the referral application, etc.;
+- Referral management. Remote two-way referral includes transfer management and reception management, which supports the inviter to cancel transfer, print referral form and transfer out again, and also supports the invitee to accept or refuse the invitation. It provides the functions of referral process management, medical record management, referral process reminder, referral record query, etc.;
+- Patient information feedback. The discharge information of the patient can be automatically acquired from the invitee's HIS, sent back to the inviter according to the information of referral records or to the patients' reminder, referral record query, etc. and on to the designated referral institution;
+- Follow-up. Remote two-way referral provides follow-up records, a follow-up plan, query of follow-up records and reminder.
+
+#### **8.1.6 Remote medical education**
+
+##### **8.1.6.1 General**
+
+Remote medical education is applicable for hospitals and experts providing professional training, teaching, medical record discussion and technical support for grass-roots doctors through audio, video and courseware.
+
+##### **8.1.6.2 Basic functions**
+
+The basic functions include:
+
+- Teacher management. Teacher registration, information query and modification.
+- Student management. Student registration, information query and modification.
+- Course management. Video course query, video on demand, real-time training.
+- Courseware management. Video management, courseware management, video sharing and courseware synchronization.
+
+- Process management. Make the course study plan, record the course training and query progress.
+- Credit hour management. Application for credit hours, credit hour card printing, etc.
+
+#### **8.1.7 Remote intensive care**
+
+##### **8.1.7.1 General**
+
+Remote intensive care is a process in which the inviter applies to the invitee and provides the clinical data of patients who are critically ill, the invitee accepts the application, carries out remote intensive care and issues diagnosis opinions and treatment guidance opinions.
+
+#### **8.1.7.2 Basic functions**
+
+The basic functions include:
+
+- Application and appointment, data sending and receiving, browsing and analysis, quality control and statistics, report publishing and browsing, evaluation of service;
+- Real-time acquisition and transmission of vital signs parameters and continuous dynamic monitoring, diagnosis suggestions, treatment suggestions and other medical activities sent between the inviter, the invitee and the patient;
+- 24-hour continuous dynamic observation, providing the invitee with real-time continuous monitoring data of patients and giving early warning of abnormal situations;
+- Storage and management of vital signs parameters, including data recording, management, query and statistics;
+- Bedside videoconference, which facilitates remote interactive communication between inviters, invitees and patients;
+- Remote control of the video pan/tilt in real time, observing the patient from multiple angles and switching pictures quickly.
+
+#### **8.1.8 Remote surgery teaching**
+
+##### **8.1.8.1 General**
+
+Through the application of teleconsultation technology, images of clinical diagnosis or surgical site are required to be recorded in real time and remotely sent to remote surgical teaching.
+
+##### **8.1.8.2 Basic functions**
+
+The basic functions of a telemedicine system in the context of remote surgery teaching include the following:
+
+- A telemedicine system is required to support application and appointment, service evaluation and other process management functions;
+- An operating room is required to support multiple remote classrooms to watch the operation at the same time;
+- A telemedicine system is required to enable the medical experts to connect to the same operating room or multiple ones at any point in the telemedicine system for operation guidance or discussion;
+- A telemedicine system is recommended to support real-time recording of surgical images and scene videos;
+- A telemedicine system is recommended to support static photography and dynamic recording of the operation process;
+- A telemedicine system is recommended to support storage, playback and management of high-quality audio and video of operations;
+
+- A telemedicine system is recommended to support the function of real-time live broadcast and recording of audio and video information of operation;
+- A telemedicine system is recommended to support the function of real-time interactive audio-video call between operating room and medical experts;
+- A telemedicine system is recommended to support monitor high-definition TV or LED TV in surgical field;
+- A telemedicine system is recommended to support remote microcontrol function of surgical field camera;
+- A telemedicine system is recommended to support remote pan/tilt control function of the camera in operation field and other cameras in the operation room.
+
+#### **8.1.9 Remote pathology diagnosis**
+
+##### **8.1.9.1 General**
+
+Remote pathology diagnosis is the process in which the inviter applies for remote pathology diagnosis, the invitee accepts the application, conducts remote pathology diagnosis and issues diagnosis opinions and reports.
+
+##### **8.1.9.2 Basic functions**
+
+The basic functions include:
+
+- Application and appointment, service evaluation and other process management functions;
+- Digital scanning function of pathological sections, which converts pathological sections into digital sections;
+- Zoom in, zoom out, mark and other post-processing functions of virtual digital slices;
+- Uploading patient's information and downloading report;
+- Statistics function of relevant data.
+
+#### **8.1.10 Remote disease re-examination**
+
+##### **8.1.10.1 General**
+
+Remote disease re-examination is for patients with serious diseases who have received offline initial treatment in the hospital. It is the process in which the inviter applies to the invitee for re-examination, the invitee accepts the application, conducts disease diagnosis and issues diagnosis opinions and reports.
+
+##### **8.1.10.2 Basic functions**
+
+The basic functions include:
+
+- Re-examination appointment: Filling in the application form for re-examination visit, submitting and modification of the application, query of the information of expert database, organization and transmission of electronic data, query of the application, etc.;
+
+Re-examination management: Re-examination process management, medical record data management, first visit report browsing, follow-up management, re-examination service evaluation, etc.;
+
+Re-examination service: Medical record data browsing, audio-video interactive disease discussion, whiteboard writing and interaction of medical record data, preparation, release and modification of re-examination report, re-examination report template management, etc.
+
+#### **8.1.11 Remote prevention and health care**
+
+#### **8.1.11.1 General**
+
+Prevention and health care focuses on disease prevention and health promotion by assisting the inviter in self-monitoring and observation. When the body has not yet shown symptoms of disease, an abnormal situation is detected by other means, and targeted treatment is given.
+
+##### **8.1.11.2 Basic functions**
+
+The basic functions include:
+
+- The ability to receive health data from mobile health monitoring devices;
+- The ability to upload health data to the mobile terminal of the invitee in the form of questionnaire survey;
+- The ability to provide intelligent guidance according to the symptoms of the inviter and give advice on disease prediction and the relevant department;
+- The ability that the inviter can save or delete personal data;
+- The ability of providing disease prevention knowledge and popularizing health knowledge;
+- The ability of displaying the health data of the inviter to the invitee.
+
+### **8.1.12 Remote post-hospital management**
+
+#### **8.1.12.1 General**
+
+Remote post-hospital management includes outpatient service post-hospital management and leaving hospital post-hospital management. The main purpose of remote post-hospital management is to provide extended post-hospital medical care services. Further follow-up of the patient's disease condition and lifestyle has been achieved to receive better therapeutic effect.
+
+##### **8.1.12.2 Basic functions**
+
+The basic functions include:
+
+- The function of receiving health data of mobile portable sign monitoring equipment and the function of lifestyle management and recording;
+- The ability of regular follow-up recording;
+- The ability of comparison and analysis according to the results of follow-up and re-examination;
+- The ability of providing disease prevention knowledge and popularizing health knowledge;
+- The ability of in-hospital connection;
+- The ability that patients can make a consultation appointment directly when they need.
+
+## **8.2 Service layer**
+
+Service layer includes, but not limited to, that described in clauses 8.2.1 and 8.2.2.
+
+### **8.2.1 Registration service**
+
+##### **8.2.1.1 General**
+
+Registration service provides registration management services for patients, medical service personnel, medical and health institutions/departments and medical and health terminologies.
+
+The system is required to provide unique identification for these entities. All kinds of entities have their own registration databases, such as patient registration database, medical service personnel registration database, institution registration database and terminology registration database, which support one single entity having multiple identifiers.
+
+#### **8.2.1.2 Patient registration service**
+
+The basic functions include:
+
+- Registration of new patients;
+- Updating patients' information;
+- Validating patient identity;
+- Merging patient identities;
+- Querying patient information.
+
+#### **8.2.1.3 Medical service personnel registration**
+
+The basic functions include:
+
+- Registration of new medical service personnel;
+- Updating medical service personnel information;
+- Validating medical service personnel identities;
+- Merging medical service personnel identities;
+- Querying medical service personnel information.
+
+#### **8.2.1.4 Medical and health institutions/departments registration**
+
+The basic functions include:
+
+- Registration of new medical and health institutions/departments;
+- Updating medical and health institution/department information;
+- Suspension of medical and health institutions/departments;
+- Querying medical and health institution/department information.
+
+#### **8.2.1.5 Medical and health terminology registration**
+
+The basic functions include:
+
+- Providing batch import and export of terminologies;
+- Sorting and browsing terminologies;
+- Maintaining the relations of terminologies;
+- Managing version of terminologies;
+- Maintaining mapping relationship of terminologies;
+- Synchronizing terminologies with other systems.
+
+### **8.2.2 Telemedicine data storage service**
+
+Telemedicine data storage service provides patient basic information repository, electronic medical record repository, health file information repository, consultation information repository, image data repository and teaching resource repository.
+
+The basic functions include:
+
+- Reception of documents, images and video data materials;
+- Registration of documents, images and video data materials to index base;
+- Providing documents, images and video data materials to users.
+
+#### **8.2.2.1 Index service**
+
+The basic functions include:
+
+- Registration of static documents which include the patient's case information and the document catalogue and summary information related to the event information;
+
+- Supporting the function of querying and displaying related medical static document index according to medical events or patient information.
+
+## **8.3 Resource layer**
+
+The resource layer includes, but not limited to, that described in clauses 8.2.1 and 8.3.2.
+
+### **8.3.1 Basic information base**
+
+The basic information base includes the basic information of the patient, information of medical and health personnel, information of medical institution (department), medical and health terms.
+
+The basic information base is generated from the registration service of the telemedicine system, which provides uniform, complete and accurate basic information and unique identification for these entities.
+
+### **8.3.2 Telemedicine database**
+
+#### **8.3.2.1 Document repository**
+
+The document repository stores activity-based and standard-compliant clinical documents in a clear, safe and lasting way.
+
+The document repository is recommended to select the appropriate document to register according to the content type of clinical documentation and respond to the request of document retrieval.
+
+#### **8.3.2.2 Image repository**
+
+Medical image storage is required to follow the current international standards such as DICOM 3.0 and HL7, and to conform to the IHE framework. The whole system has high security, high reliability, high compatibility and sustainable scalability. It can realize the reception, transfer and printing of images, and support lossless or lossy compression storage mode of images.
+
+#### **8.3.2.3 Video repository**
+
+The video repository is required to be based on web structure for the convenience of daily maintenance and remote education.
+
+The video repository is required to be more flexible in data management. It can centrally manage all the materials in distance education projects, or divide the materials according to types or disciplines, manage them separately and divide the large material library into several small material libraries.
+
+## **8.4 Information exchange layer**
+
+### **8.4.1 General**
+
+The information exchange layer exchanges data with other information systems through data interface or message transmission according to the business process, including but not limited to enterprise service bus (ESB), symmetrical multiprocessing (SMP), general data transfer platform (GTP), extract-transform-load (ETL) and multicontrol unit (MCU). The telemedicine system is required to exchange data with the external emergency command system, medicine and health information system and medical information acquisition equipment.
+
+The information exchange layer includes, but not limited to, that described in clauses 8.4.1 to 8.4.4.
+
+### **8.4.2 Emergency command system**
+
+The telemedicine information system is connected with the emergency command system, and the video site is used to connect with the hospital network, providing dynamic audio and video information of the scene and the treatment process, so as to realize the linkage of information-sharing and treatment in emergency response. This can not only enable patients to obtain a diagnosis and
+
+treatment through remote video, but also help medical staff to report the latest situation of patients to the command centre at any time and analyse any potential new diseases.
+
+### **8.4.3 Medical information system**
+
+The medical information system mainly includes the electronic record system, hospital information system, laboratory information system, clinical information system, ECG diagnosis system, image diagnosis system, pathological diagnosis system and other medical information systems. Through the docking of the telemedicine information system and medical information system, information-sharing and business collaboration between hospitals can be realized.
+
+The telemedicine information system is connected with the regional health information platform, providing real-time information of telemedicine supervision and business services, and sharing the original health records and electronic medical records, so that the regional health information platform has the comprehensive management function of telemedicine business.
+
+If a medical institution has established a hospital information integration platform for data sharing, it will realize the docking with the telemedicine information system through the platform mechanism, reduce the number of data interfaces, and realize information-sharing and business collaboration between hospitals.
+
+### **8.4.4 Medical information acquisition equipment**
+
+Medical information acquisition equipment mainly includes the multiparameter vital signs monitor, digital imaging equipment, digital electrocardiogram, ventilator and other items of medical information acquisition equipment, which are mainly used to collect the vital signs, blood sugar, blood pressure and other data of patients.
+
+## **8.5 Network layer**
+
+### **8.5.1 Basic functions**
+
+The functions of the network layer are recommended to include, but are not limited to, the following:
+
+- Reliability: The stability and reliability of the network are the key guarantee for the normal operation of the application system. When designing the network, commercial network products are required to be selected, the network architecture is required to be designed reasonably and reliable network backup strategies are required to be formulated to ensure that the network has the ability of fault self-healing and of supporting the normal operation of the system to the maximum extent.
+- Openness: Open protocols (such as IPv6, etc.) that support international standard network protocols, international standard large-scale dynamic routeing protocols, etc., are conducive to ensuring smooth connection and interoperability with other networks and future network expansion.
+- Security: The network layer is required to improve the overall security of the network through an equipment mechanism and networking scheme.
+
+### **8.5.2 Network quality and requirements of QoS**
+
+The network quality and QoS requirements are as follows:
+
+- Network latency is required to be less than 50 ms;
+- Jitter is as low as possible, and is recommended not to exceed 20 ms;
+- Packet loss is recommended not to exceed 5%.
+
+## **8.6 Video audio system**
+
+### **8.6.1 General**
+
+The remote video audio system is required to comply with the basic video communication protocols of [ITU-T H.323] and SIP. The video audio system includes, but is not limited to, that described in clauses 8.6.1 to 8.6.5.
+
+### **8.6.2 Business management**
+
+The technical requirements of business management are recommended to include:
+
+- Unified communication management system supports B/S architecture, and realizes functions such as equipment management, registration and authentication, conference management, conference control and reporting statistics;
+- GK server requirements: Supports large-capacity node registration to realize equipment registration and authentication;
+- Network requirements: Business management is required to support IPv4 protocol stack, and IPv6 protocol stack is recommended to facilitate subsequent expansion.
+
+The requirements of user authentication management are as follows:
+
+- User authentication is required to be managed according to the organizational structure;
+- User authentication is recommended to be configurable only by the administrator of the telemedicine system;
+- User authentication management is recommended to support hierarchical and decentralized management.
+- System authentication and resources are required to be managed according to the structure of enterprise organization;
+- The same MCU or venue is recommended to be distributed to multiple organizations.
+
+The requirements of equipment management include:
+
+- a. Equipment capacity management:
+  1. The platform can be extended to manage multiple equipment and meeting places.
+  2. The equipment (MCU, meeting place) is required to be managed according to the organizational structure.
+- b. Supporting the management of mainstream video terminal equipment, and supporting the remote addition and management of MCU and terminal equipment, viewing the brand model, GK registration status, SIP registration status, MAC address, video capability of the terminal, software version number and other information of the terminal or MCU, and remotely modifying the device configuration in real time, such as remotely opening and closing GK registration, remotely modifying [ITU-T H.323] ID, [ITU-T E.164] number, DNS server address.
+- c. Supporting automatic device discovery. Devices (MCU and terminal) will be automatically identified by the management platform after joining the system. After discovering the devices, view and configure the information of the devices, and support configuration backup and remote recovery of the managed devices.
+- d. Supporting system alarm management to remotely view the alarm information of managed devices (terminals and MCU), classifying alarms based on alarm types, and quickly obtaining the operating status of managed devices.
+- e. Supporting remote view of logs of managed devices.
+- f. Supporting remote management and control of recording and playing server devices.
+
+### 8.6.3 Multipoint exchanging
+
+The requirements of multipoint exchanging include:
+
+- Supporting scalable architecture design and embedded operating system. Smooth upgrade of system capacity can be achieved by adding boards. Each board of the device has at least two 1000 Mbit/s RJ-45 interfaces and two optical fibre interfaces, which support IPv4 and IPv6 for future expansion.
+- Supporting SD (standard definition, a video format with a physical resolution below 1280P × 720P), HD (a video with a vertical resolution of 720 or greater), HD mixed conference and multipoint conference and rate adaptation. Each participating terminal can join the conference at the same time with different protocols ([ITU-T H.323]/SIP), different bandwidths (64 K–8 Mbps), different audio and video codes ([ITU-T H.263]/[ITU-T H.264], etc.), [ITU-T G.722]/[ITU-T G.711]/AAC-LD), different resolutions (CIF/4CIF/720P 30FPS, 60FPS/1080P 30FPS, 60FPS) and can support multiple groups of conferences at the same time. The number of conference groups is not limited by the number of mixed networks and mixed speeds.
+- System capacity. The port resources of the MCU can be randomly allocated according to the video definition through manual designation, so as to maximize the resource utilization, and MCU port resource allocation does not need to restart MCU equipment.
+- Multichannel cascade support. Multiple venues of lower MCU can be transmitted to higher MCU through multiple independent video channels.
+
+The requirements of audio and video technology include:
+
+- Video requirements. Support international standard video protocols including [ITU-T H.261], [ITU-T H.263], [ITU-T H.264] basic profile, [ITU-T H.264] high profile, [ITU-T H.264] SVC, etc. Support 1080P60 frames, 1080P30 frames, 720P60 frames and 720P30 frames and be downwardly compatible with 4CIF and CIF image formats;
+- Audio requirements. Audio and video technology is recommended to support international standard audio protocols, including [ITU-T G.711a], [ITU-T G.711u], [ITU-T G.722], [ITU-T G.728], [ITU-T G.722.1C], and support broadband voice coding [ITU-T G.719], AAC\_LD audio protocols with 20 kHz frequency response;
+- Multi-screen support. Support a variety of multiscreen types and multiscreen mode switching. Multiscreen per port is supported, and the terminal equipment participating in the conference can select the multiscreen combination mode required by its own venue through the remote-control keys, without affecting the clarity and multiscreen viewing mode of other venues. Adding the auxiliary stream into the multipicture, so that the terminal equipment which does not support [ITU-T H.239] can receive the auxiliary stream information.
+- Dual-stream support. Support [ITU-T H.239] dual-stream and binary floor control protocol (BFCP) dual-stream, static dual-stream and dynamic dual-stream. The bandwidth of the auxiliary stream can be set manually as required, and the maximum image format of the auxiliary stream is 1080P 60FPS. Supporting the auxiliary stream adaptation function, in a high-definition and standard-definition mixed conference, terminals with different video decoding capabilities can receive auxiliary stream information with different definitions, to ensure that the low auxiliary stream receiving capability of a certain conference venue will not affect other conference venues.
+
+The requirements of safety and stability include that:
+
+- Multipoint exchanging is required to support the hot backup of the main control board and media board, and the main control board will not affect the meeting being held during the switching process, and supporting the redundant backup of dual power supplies;
+
+- Multipoint exchanging is required to support encryption of media, signal and management such as [ITU-T H.235] Advanced Encryption Standard 256 (AES256), SRTP, TLS, HTTPS, SSH, SNMPv3, etc., providing a secure channel for authentication and encrypted communication, preventing users from being counterfeited, protecting conference information from being intercepted and translated during transmission, and fully guaranteeing the security of conference information;
+- MCU equipment has strong anti-packet loss capability. Under 10% packet loss, the voice is recommended to be smooth and clear, the video is recommended to be clear and smooth.
+
+### 8.6.4 High-definition audio and video system
+
+The requirements of HD audio and video system include that:
+
+- HD audio and video system is recommended to use embedded operating system, but not use pc or industrial pc architecture;
+- HD audio and video system is recommended to provide multichannel high-definition video input and multichannel high-definition video output interfaces, and support HDMI and video graphics array (VGA) interfaces;
+- HD audio and video system is recommended to support multichannel audio input and multichannel audio output interfaces, with standard microphone interface and digital audio interface.
+
+The technical requirements of video and audio include that:
+
+- The video is required to support [ITU-T H.263], [ITU-T H.264] and [ITU-T H.264] SVC image coding protocols. Image format is required to support 1080P50/60 frames, 1080P25/30 frames, 1080i50/60 frames, 720P50/60 frames, 720P25/30 frames, 4CIF, CIF.
+- The audio is required to support [ITU-T G.711], [ITU-T G.722], [ITU-T G.722.1], [ITU-T G.722.1C], [ITU-T G.728], [ITU-T G.719], [ITU-T G.729A], AAC-LD, etc., and to support at least three broadband audio protocols above 20 kHz and to support two-channel stereo function.
+- The high-definition audio and video system is required to support [ITU-T H.239] protocol under standard [ITU-T H.323], BFCP under standard SIP protocol, and 1080P effect of main and auxiliary streams, up to 1080P60 frames of main stream, and 1080P60 frames of auxiliary streams.
+- The high-definition audio and video system is required to support receiving and sending auxiliary streams at the same time when holding point-to-point meetings.
+
+The technical requirements of network access include that:
+
+- Network access is recommended to have good network adaptability. Under the maximum network packet loss of 20%, the image is recommended to be smooth and clear, so as to ensure the progress of the meeting;
+- The terminal is recommended to support a 1080P60-frame high-definition conference with 768 kbit/s conference bandwidth, with normal function and smooth audio and video; under the 512 kbit/s conference bandwidth, a 1080P30-frame high-definition conference is recommended to be held with normal functions and smooth audio and video; under the 384 kbit/s conference bandwidth, a 720P30-frame high-definition conference is recommended to be held, with normal functions and smooth audio and video.
+
+The system functions and safety requirements include:
+
+- Supporting [ITU-T H.235] signalling encryption under [ITU-T H.323] protocol, Under SIP, supporting TLS and SRTP encryption, and supporting the AES media stream encryption algorithm;
+
+- Supporting the LDAP address book, which can download and update address book entries directly from the address book server, supporting LDAP access authentication and encryption, supporting the network address book synchronization function and updating the contact directory through the address book server.
+
+The requirements of relative devices include that:
+
+- The digital microphone is recommended to support 360-degree omnidirectional pickup, with a maximum pickup distance of more than 5 metres;
+- The high-definition audio and video system is required to support adaptive echo cancellation, automatic gain control and automatic noise shooting;
+- The sampling rate is required to not be less than 48 kHz;
+- The high-definition audio and video system is required to support turning sound off and on through the microphone's touch panel.
+
+### **8.6.5 Network recording and playing**
+
+The technical requirements of network recording and playing system include that:
+
+- The network recording and broadcasting server is recommended to support B/S architecture, which can be accessed through a web page to realize the functions of on-demand and live broadcast;
+- The network recording and playing system is required to support IPv4 protocol stack and IPv4 single networking. It is recommended to support IPv6 single networking or IPv4/IPv6 hybrid networking to facilitate the subsequent expansion;
+- The network recording and playing system is recommended to record a maximum of 30 1080P30 meetings at a time;
+- The network recording and playing system is recommended to support simultaneous recording of one channel of high-definition and one channel of signposted images, and each branch node is recommended to select high-definition or standard-definition on-demand viewing according to the network status;
+- The network recording and playing system is recommended to support dual-stream recording of the conference, and the secondary stream recording is recommended to support HD recording;
+- Network recording and playing is required to support recording of single-point, peer-to-peer and multipoint meetings;
+- Network recording and playing is required to support controlling the process of conference recording, including recording, pausing, stopping and selecting the source of recording;
+- Network recording and playing is recommended to support live broadcast onto PC, smartphones, tablet platform and on-demand videos;
+- Network recording and playing is recommended to support browser plug-in free live broadcast and on-demand broadcast;
+- Network recording and playing is recommended to support previewing recorded pictures and text indexes on the browser;
+- Network recording and playing is recommended to support the synchronous playing of main and auxiliary streams and sounds in the process of live broadcast and on demand;
+- Network recording and playing is recommended to support switching the screen layout, when the browser broadcasts live or on demand;
+- Network recording and playing is recommended to support that the users can pause (play), locate, stop, play full screen (cancel full screen), and adjust the volume of the on-demand content, when the browser is playing on demand.
+
+## **8.7 Security guarantee**
+
+Security guarantee includes, but not limited to, the following:
+
+### **8.7.1 Authentication management**
+
+The system requires strict multilevel setting management of user rights of various medical institutions, departments, experts, patients, etc.
+
+The basic functions include:
+
+- Authorizing and distributing the rights of different users;
+- Distribution of rights for diagnosis and browsing of different reports;
+- Distribution of rights for writing, reviewing, revising and browsing different medical records;
+- Encrypted storage and transmission of all code.
+
+### **8.7.2 Network security**
+
+##### **8.7.2.1 Security of network architecture**
+
+The security requirements of network architecture include that:
+
+- The bandwidth of each part of the network is required to ensure that the access network and the core network can meet the needs of peak business;
+- Network architecture is required to define the priority of bandwidth allocation according to the important order of business system services, and give priority to important hosts in case of network congestion;
+- Network architecture is required to divide different network segments or VLAN, according to factors such as the work function, importance of each department and the importance of the information involved;
+- All kinds of network equipment such as router, switch and MCU is required to have telecom access cards;
+- The key network equipment, such as the core switch, firewall, application server, secure access equipment and database service, is recommended to adopt dual-machine hot standby technology, which makes the whole network business processing capacity have redundant space.
+
+#### **8.7.2.2 Network isolation**
+
+The requirements of network isolation include that:
+
+- The security relationship between different network areas is recommended to be defined through network partition, and security equipment is recommended to be set at the data sharing gateway between different centres;
+- Network isolation is required to adopt firewalls to isolate each security areas;
+- Network isolation is required to have the function of access control between different application systems.
+
+#### **8.7.2.3 Network access**
+
+The data centre exit of a telemedicine system is required to deploy anti-DDoS for safety protection. It is required to have second-level protection response capability. It is required to have attack type defence including IPv6 attack protection, and zero misjudgement for attacks.
+
+#### **8.7.2.4 Intrusion detection and defence**
+
+The requirements of intrusion detection and defence include that:
+
+- Intrusion detection and defence is required to have a continuously updated feature database to ensure a detection rate of more than 99%;
+- Intrusion detection and defence is recommended to support message detection for critical paths and identification of application protocols;
+- Intrusion detection and defence is recommended to support integration strategic configuration and unify the entrance of strategic configuration;
+- Intrusion detection and defence is recommended to support IPv6 technology to facilitate the future expansion of the system.
+
+#### **8.7.2.5 Network transmission**
+
+The requirements of network transmission include that:
+
+- The data is recommended to be transmitted by IPSec virtual private network / secure sockets layer (VPN/SSL) VPN encryption technology;
+- Network transmission is required to support a mainstream encryption algorithm to ensure trusted access of far-end medical institutions or mobile terminals;
+- Secure access gateway is recommended to support dual-machine hot standby.
+
+#### **8.7.2.6 Network security audit**
+
+The requirements of network security audit include that:
+
+- Audit records are required to be made on outgoing documents and contents, and suspicious leaks are required to be tracked through query and statistics of audit database;
+- Network security audit is recommended to detect the content of web, IM, and mail according to pre-set or user-defined sensitive data keywords to prevent the data containing key information from flowing out of the enterprise;
+- Network security audit is recommended to keep a log of daily behaviour;
+- Network security audit is recommended to locate illegal behaviours to find potential bad users and prevent reputation risks.
+
+#### **8.7.3 Data security**
+
+#### **8.7.3.1 Data-acquisition security**
+
+The requirements of data-acquisition security include that:
+
+- Data acquisition security is required to ensure the authenticity of data collected by the system, and have the ability to identify data forgery;
+- Data acquisition security is recommended to use a unified data-acquisition channel to guarantee the safety of data collection of medical information resources;
+- Data acquisition security is recommended to safely classify medical information resources, and designate different collection methods to collect medical information resources of different levels.
+
+#### **8.7.3.2 Data storage**
+
+The requirements of data storage include that:
+
+- Data storage is required to adopt fragmented distributed discrete storage technology to preserve medical information resources, and it is required to have at least two copies of data locally. The data is required to be stored in different racks after being forcibly fragmented.
+- The stored meta information is required to be deleted during the recycle of storage resources, and each physical bit of the logical volume is recommended to be overwritten with a clear "zero" to ensure that its original data cannot be recovered by software.
+
+- Data storage is required to use SSL to realize end-to-end transport layer encryption, use a symmetric encryption key to realize user signature verification and storage request encryption, and use the MD5 algorithm to realize message body encryption.
+- Data storage is recommended to create data storage area isolation; different levels of security data adopt different protection measures.
+- Data storage is required to provide authentication control of data storage access, establish corresponding access rules and assign a professional to manage the authentication of data storage.
+
+#### 8.7.3.3 Data transmission
+
+The requirements of data transmission include that:
+
+- Data transmission is required to adopt encryption and other effective measure to realize the confidentiality of transmission of virtual machine image files, system management data, identification information and important business data;
+- Data transmission is required to be able to detect that the integrity of virtual machine image files, system management data, authentication information and important business data is damaged during transmission, and take necessary recovery measures when integrity errors are detected;
+- Data transmission is required to have redundancy protection on the transmission channels of business data, control data and management data, the channels are required to be isolated from each other, and the fault detection, repair and isolation are recommended to be completed separately.
+
+##### 8.7.3.4 Data deletion
+
+The requirements of data deletion include that:
+
+- Data deletion is required to provide means to help clear the data left over by data migration between different centres, business termination, natural disasters, contract termination, etc.;
+- Data deletion is required to ensure that the disk storage space is completely eliminated before being released or distributed to other users;
+- Data deletion is required to ensure that data in the host computer's memory (e.g., RAM) is completely erased before being released;
+- Data deletion is required to provide means to eliminate all the copies of data;
+- Data deletion is required to provide technical means to prohibit the recovery of destroyed data.
+
+##### 8.7.3.5 Data backup and recovery security
+
+The requirements of date backup and recovery security include that:
+
+- Data backup and recovery security is required to provide a local data backup and data recovery function, perform a complete data backup at least once a day, and store the media off-site;
+- Data backup and recovery security is required to provide a non-local real-time backup function, and use the communication network to make a copy of real-time data to the disaster backup centre;
+- Data backup and recovery security is required to provide the fast recovery ability of the virtual machine;
+- Data backup and recovery security is required to support backup and recovery based on disks.
+
+# Appendix I
+
+## Application scenarios for telemedicine
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This Recommendation presents four application scenarios, which are applications of remote disease re-examination, remote surgery teaching, remote intensive care and remote post-hospital management.
+
+## I.1 Scenario 1: Remote disease re-examination
+
+Patients use the re-examination appointment service through the telemedicine system, select the corresponding department and the visiting doctors, according to their disease conditions, complete the offline re-examination appointment and initiate the remote disease re-examination service.
+
+The invited doctors obtain the information of the re-examination patients through the telemedicine system, manage the process of re-examination, obtain the patients' medical records, discuss the condition with the patients through video audio system and remote whiteboard writing, compile the report of re-examination, and conduct follow-up management for the patients.
+
+After completing the remote disease re-examination, inviters evaluate the service of the re-examination and the invited doctors through the telemedicine system.
+
+## I.2 Scenario 2: Remote surgery teaching
+
+Medical institutions apply for surgical teaching courses in the telemedicine system, including but not limited to surgical live broadcasting, recording and replaying, surgical guidance, case discussion, medical record sharing and other training, and fill in the teaching content and object-oriented course.
+
+The trainees apply and attend surgical teaching courses through the telemedicine system or its mobile terminal. After the remote surgery teaching course, the trainees can query the course application record, attendance record and review the course recording and playback in the system.
+
+## I.3 Scenario 3: Remote intensive care
+
+The inviter submits the application for remote intensive care through the telemedicine system, and the invitee obtains the patient's medical history data through the system to learn the patient's medical history and condition.
+
+The invitee obtains the vital signs data of the patient in real time through the telemedicine system, analyses the patient's condition, and provides diagnosis and treatment guidance. The two side doctors carry out bedside video discussion, and finally make an evaluation. The remote intensive care is completed.
+
+## I.4 Scenario 4: Remote post-hospital management
+
+After leaving the hospital, patients can obtain their own physical signs data at any time through the mobile health monitoring devices assigned or designated by the doctors, and upload the data to the telemedicine system through the mobile terminal.
+
+The invitee checks the patients' physical signs and data in time through the telemedicine system to provide reference and suggestions for follow-up treatment and rehabilitation. The time of post-hospital management adjusts dynamically according to the patient's condition and recovery condition. Generally, the time of leaving hospital post-hospital management is longer than that of outpatient service post-hospital management.
+
+# Bibliography
+
+- [b-IETF RFC 3261] IETF RFC 3261 (2002), *Session Initiation Protocol*.
+- [b-IETF RFC 3414] IETF RFC 3414 (2002), *User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)*.
+- [b-IETF RFC 3711] IETF RFC 3711 (2004), *The Secure Real-time Transport Protocol*.
+- [b-IETF RFC 4252] IETF RFC 4252 (2006), *The Secure Shell (SSH) Authentication Protocol*.
+- [b-IETF RFC 4511] IETF RFC 4511 (2006), *Lightweight Directory Access Protocol (LDAP): The Protocol*.
+- [b-IETF RFC 6190] IETF RFC 6190 (2011), *RTP Payload Format for Scalable Video Coding*.
+- [b-IETF RFC 8446] IETF RFC 8446 (2018), *The Transport Layer Security (TLS) Protocol Version 1.3*.
+- [b-IETF RFC 8855] IETF RFC 8855(2021), *The Binary Floor Control Protocol (BFCP)*.
+- [b-IETF RFC 9110] IETF RFC 9110 (2022), *HTTP Semantics*.
+- [b-ISO/TS 22077] ISO/TS 22077 (2015), *Health informatics — Medical waveform format*.
+- [b-HealthIT.gov] Office of the National Coordinator for Health Information Technology (2019), *What is Telehealth? How is it Different from Telemedicine?*  
+<<https://www.healthit.gov/faq/what-telehealth-how-telehealth-different-telemedicine>>
+- [b-WHO] World Health Organization (2022), *Consolidated telemedicine implementation guide*.  
+<https://www.who.int/publications/i/item/9789240059184>
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.780.6-202512-I_PDF-E/raw.md b/marked/F/T-REC-F.780.6-202512-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..8d54de1943da97db0770f77de4a297e31757df1a
--- /dev/null
+++ b/marked/F/T-REC-F.780.6-202512-I_PDF-E/raw.md
@@ -0,0 +1,1484 @@
+
+
+# Recommendation **ITU-T F.780.6 (12/2025)**
+
+SERIES F: Non-telephone telecommunication services  
+Multimedia services
+
+---
+
+## **Requirements for colourimetry for telemedicine systems using ultra-high definition imaging**
+
+![ITU logo](390120de4fe440c42fea8154fcaad334_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 F-SERIES RECOMMENDATIONS **Non-telephone telecommunication services**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| TELEMATIC SERVICES                                              | F.160-F.399        |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| <b>MULTIMEDIA SERVICES</b>                                      | <b>F.700-F.799</b> |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| ACCESSIBILITY AND HUMAN FACTORS                                 | F.900-F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.780.6
+
+# Requirements for colourimetry for telemedicine systems using ultra-high definition imaging
+
+## Summary
+
+Recommendation ITU-T F.780.6 describes the requirements for the use of colour and colourimetry for telemedicine systems using ultra-high definition imaging.
+
+It also outlines the requirements for the light source and test object colours, the camera and transmission, the viewing conditions and display, as well as the overall characteristics of the telemedicine system.
+
+It includes annexes on test colours for medical imaging equipment, measurement methods for colour capturing accuracy of cameras, and measurement method of colour reproducibility of electronic displays.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T F.780.6  | 2025-03-16 | 21          | 11.1002/1000/16246 |
+| 2.0     | ITU-T F.780.6  | 2025-12-14 | 21          | 11.1002/1000/16627 |
+
+## Keywords
+
+Colourimetry, digital imaging, telemedicine, ultra-high definition.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <https://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                                                                                         | 2    |
+| 4   | Abbreviations and acronyms .....                                                                                                  | 3    |
+| 5   | Conventions .....                                                                                                                 | 3    |
+| 6   | Background.....                                                                                                                   | 4    |
+| 7   | Conditions for high-fidelity colour reproduction .....                                                                            | 4    |
+| 7.1 | Illumination .....                                                                                                                | 5    |
+| 7.2 | Test colours .....                                                                                                                | 5    |
+| 7.3 | Colour reproduction of camera.....                                                                                                | 5    |
+| 7.4 | Transmission of image signals .....                                                                                               | 6    |
+| 7.5 | Viewing conditions.....                                                                                                           | 7    |
+| 7.6 | Colour reproduction of display.....                                                                                               | 8    |
+| 7.7 | Overall characteristics of system.....                                                                                            | 9    |
+| 7.8 | Application to equipment and systems other than those of [ITU-R BT.2020].....                                                     | 9    |
+| 8   | Conditions required for colour reproduction of specific surgical images .....                                                     | 9    |
+|     | Annex A – Test colours for medical imaging equipment .....                                                                        | 10   |
+|     | Annex B – Measurement methods for colour capturing accuracy of cameras for implementing fidelity colour reproduction (CCAC) ..... | 19   |
+| B.1 | Introduction .....                                                                                                                | 19   |
+| B.2 | Measurement conditions.....                                                                                                       | 19   |
+| B.3 | Measurement methods.....                                                                                                          | 23   |
+|     | Annex C – Measurement method of colour reproducibility of electronic displays.....                                                | 27   |
+| C.1 | Introduction .....                                                                                                                | 27   |
+| C.2 | Measurement conditions.....                                                                                                       | 27   |
+| C.3 | Measurement method .....                                                                                                          | 27   |
+|     | Annex D – On the use of [ITU-R BT.709] .....                                                                                      | 31   |
+| D.1 | The system colourimetry and OETF for [ITU-R BT.709] .....                                                                         | 31   |
+| D.2 | Use of test colours within the [ITU-R BT.709] colour gamut .....                                                                  | 31   |
+|     | Appendix I – Examples of Lab and signal values for test colours.....                                                              | 32   |
+| I.1 | Spectral distribution of D4500 .....                                                                                              | 32   |
+| I.2 | Lab values of the test colours with the illuminant D4500.....                                                                     | 33   |
+| I.3 | Reference display input signal with the illuminant D4500 .....                                                                    | 36   |
+|     | Bibliography.....                                                                                                                 | 38   |
+
+## Introduction
+
+Digital imaging is widely used in telemedicine, including surgery and even by pathologists for the creation of static images using microscope-dedicated optical cameras. Recently, this practice has gained even more urgency as many healthcare practices have to be done remotely, due to COVID-19. Such digital imaging for telemedicine is sometimes done using smartphones.
+
+It is clear that robust diagnosis relies upon satisfactory cross-media colour reproduction between physical targets and digital images displayed on different displays and observed under disparate viewing conditions. For this reason, standardization on the use of colour in medical imaging is necessary.
+
+The digital imaging and communications in medicine (DICOM) [b-ISO 12052] grayscale standard display function (GSDF) was developed to provide an objective, quantitative mechanism for mapping digital image values into a given range of luminance values in order to produce better visual consistency in the way images appear on diverse display devices [b-DICOM]. The DICOM GSDF is intended for use with grayscale images, such as x-ray images, MRI, CT, and ultrasound. As such, therefore, DICOM GSDF is not suitable as a standard to be used for ultra-high definition (UHD) medical imaging.
+
+However, there seems to be so far no agreed upon standard for describing the way colour is used for visualization of medical images or how calibration and quality assurance of displays for medical images need to be done.
+
+It is especially important for UHD imaging to have such a standard, as UHD imaging may be used for various areas, including endoscopic and open surgery, diagnosis and education.
+
+# Recommendation ITU-T F.780.6
+
+## Requirements for colourimetry for telemedicine systems using ultra-high definition imaging
+
+## 1 Scope
+
+This Recommendation describes the requirements for the use of colour and colourimetry for telemedicine systems using ultra-high definition imaging. It also outlines the requirements for the light source and test object colours, the camera and transmission, the viewing conditions and display as well as the overall characteristics of the telemedicine system.
+
+It includes annexes on test colours for medical imaging equipment, measurement methods for colour capturing accuracy of cameras, and measurement method of colour reproducibility of electronic displays.
+
+## 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.780.1] Recommendation ITU-T F.780.1 (V3) (2023), *Framework for telemedicine systems using ultra-high definition imaging*.
+- [ITU-R BT.709] Recommendation ITU-R BT.709-6 (2015), *Parameter values for the HDTV standards for production and international programme exchange*.
+- [ITU-R BT.2020] Recommendation ITU-R BT.2020 (2015), *Parameter values for ultra-high definition television systems for production and international programme exchange*.
+- [ISO 9241-305] ISO 9241-305:2008, *Ergonomics of human-system interaction – Part 305: Optical laboratory test methods for electronic visual displays*.
+- [ISO 12646] ISO 12646:2015, *Graphic technology – Displays for colour proofing – Characteristics*.
+- [ISO/CIE 11664-4] ISO 11664-4:2019, *Colorimetry – Part 4: CIE 1976 L\*a\*b\* Colour space*.
+- [ISO/TS 17321-4] ISO/TS 17321-4 (2022), *Graphic technology and photography – Colour characterization of digital still cameras (DSCs) – Part 4: Programmable light emission system*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 chromaticity** [b-ISO/CIE 11664-2]: Property of a colour stimulus defined by its chromaticity coordinates, or by its dominant or complementary wavelength and purity taken together.
+
+**3.1.2 colour rendering** [b-ISO/CIE 11664-2]: Effect of an illuminant on the perceived colour of objects by conscious or subconscious comparison with their perceived colour under a reference illuminant.
+
+**3.1.3 colour rendering index** [b-ISO/CIE 11664-2]: Measure of the degree to which the psychophysical colour of an object illuminated by the test illuminant conforms to that of the same object illuminated by the reference illuminant, suitable allowance having been made for the state of chromatic adaptation.
+
+**3.1.4 correlated colour temperature** [b-ISO/CIE 11664-2]: Temperature of a Planckian radiator having the chromaticity nearest the chromaticity associated with the given spectral distribution on a modified 1976 UCS diagram where  $u'$ ,  $(2/3)v'$  are the coordinates of the Planckian locus and the test stimulus.
+
+**3.1.5 illuminance** [b-ISO/CIE 11664-2]: Density of incident luminous flux with respect to area at a point on a real or imaginary surface.
+
+$$E_v = \frac{d\Phi_v}{dA}$$
+
+where  $\Phi_v$  is luminous flux and  $A$  is the area on which the luminous flux is incident.
+
+**3.1.6 illuminant** [b-ISO/CIE 11664-2]: Radiation with a relative spectral power distribution defined over the wavelength range that influences object-colour perception.
+
+**3.1.7 luminance** [b-ISO/CIE 11664-2]: Density of luminous intensity with respect to projected area in a specified direction at a specified point on a real or imaginary surface.
+
+$$L_v = \frac{dI_v}{dA \cos \alpha}$$
+
+where  $I_v$  is luminous intensity,  $A$  is area and  $\alpha$  is the angle between the normal to the surface at the specified point and the specified direction.
+
+**3.1.8 relative spectral power distribution** [b-ISO 3664]: Ratio of the spectral power distribution of a source or illuminant to a fixed reference value.
+
+NOTE – The fixed reference value can be an average value, a maximum value or an arbitrarily chosen value of this distribution
+
+**3.1.9 ultra-high definition** [ITU-T F.780.1]: A video format of digital display and camera in which the horizontal screen resolution is on the order of over 4 000 pixels.
+
+**3.1.10 ultra-high definition imaging** [ITU-T F.780.1]: Video imaging using system parameters of an ultra-high definition television (UHDTV) as defined by [ITU-R BT.2020].
+
+### 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 colour gamut**: A range of colours within the spectrum of colours, or a colour space, that can be reproduced on an output device.
+
+**3.2.2 correlated colour temperature**: A one-dimensional metric that aims to quantify the perceived visual quality of nominal white light sources.
+
+**3.2.3 delta E\* ( $\Delta E^*$ )**: In colourimetry, the difference between two colours designated as two points in the colour space as defined as the Euclidean distance between the given two points
+
+NOTE – This is defined by CIE.
+
+**3.2.4 out of gamut**: A range of colours that cannot be reproduced within the colour space of the output device.
+
+NOTE – Perceptual rendering intent is a good choice for keeping images realistic when there is a significant amount of out of gamut colours and it will help images avoid 'stair stepping' in the middle of a gradient. The
+
+other commonly used rendering intent is relative colourimetric. This rendering intent maps white of the input colour space to the white of the output colour space and then will reproduce in-gamut colours exactly. Out of gamut colours will be shifted to the next available colour in the output colour space. This option is the most accurate, however it can result in stair stepping in areas of gradient. Since we are looking for pathology and changes from the normal fundus photographs, having colour relationships preserved is probably more useful than having the exact colour represented.
+
+**3.2.5 self-emissive:** Technologies where individual pixels generate their own light without needing a backlight or external illumination source.
+
+**3.2.6 programmable light emission system:** A programmable self-emissive colour target.
+
+**3.2.7 colour target:** A device or material that reproduces colours used as reference for measurements of the accuracy of a camera or system.
+
+**3.2.8 metamerism:** The phenomenon in which two colours with different spectral distributions appear to be the same colour under certain lighting conditions.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|       |                                                              |
+|-------|--------------------------------------------------------------|
+| CCAC  | Measurement methods for Colour Capturing Accuracy of Cameras |
+| CCT   | Correlated Colour Temperature                                |
+| CIE   | International Commission on Illumination                     |
+| CRI   | Colour rendering index                                       |
+| DICOM | The Digital Imaging and Communications in Medicine           |
+| FOV   | Field Of View                                                |
+| GSDF  | Grayscale Standard Display Function                          |
+| OETF  | Opto-Electronic Transfer Function                            |
+| PLES  | Programmable Light Emission System                           |
+| RGB   | Red Green Blue                                               |
+| SPD   | Spectral Power Distribution                                  |
+| UHD   | Ultra-High Definition                                        |
+| UHDTV | Ultra-High Definition Television                             |
+
+## 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 does not imply that the vendor's implementation must provide the option, nor 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 this Recommendation.
+
+## 6 Background
+
+The following are the reasons for the need of this Recommendation:
+
+- Necessity of telemedicine due to the spread of COVID-19 (reduction of contact opportunities and consultation hours).
+- Improvement of digital technology such as the realization of high-speed communication of UHD images by 2K, 4K, 8K as well as over 5G.
+- Progress in digitization of medical information: e.g., the difference in device colour reproducibility, integration of colour information, database, introduction of AI.
+- Progress of aging societies that requires the improvement of educational efficiency for medical staff as well as the remote medical guidance using educational images.
+
+The diagram in Figure 6-1 describes the typical situation where colourimetry becomes crucial in telemedicine. There are at least two variables at the source to be considered at the source of imaging: the light source and the camera (system) or its equivalent.
+
+These variables, if uncontrolled, will result in different characteristics of images, which will complicate the decision process of diagnosing and other medical practices in the telemedicine scenario.
+
+![Figure 6-1: Description of the problem. A diagram showing two rows of image formation. The top row shows a D65 light source (spectrum graph) multiplied by a camera sensor (sensitivity graph) multiplied by a teddy bear image, resulting in a teddy bear image under D65 lighting. The bottom row shows an LED light source (spectrum graph) multiplied by the same camera sensor multiplied by the same teddy bear image, resulting in a teddy bear image under LED lighting. To the right, a cartoon doctor is shown with a light fixture, and the text F.780.6(25) is at the bottom right.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg)
+
+Characteristic of the environment at the source
+
+The diagram illustrates the process of image formation in telemedicine. It shows two rows of the equation: Light × Camera × Object = Image. The top row uses a D65 light source, and the bottom row uses an LED light source. The resulting images show the teddy bear under different lighting conditions. To the right, a cartoon doctor is shown with a light fixture, and the text F.780.6(25) is at the bottom right.
+
+Figure 6-1: Description of the problem. A diagram showing two rows of image formation. The top row shows a D65 light source (spectrum graph) multiplied by a camera sensor (sensitivity graph) multiplied by a teddy bear image, resulting in a teddy bear image under D65 lighting. The bottom row shows an LED light source (spectrum graph) multiplied by the same camera sensor multiplied by the same teddy bear image, resulting in a teddy bear image under LED lighting. To the right, a cartoon doctor is shown with a light fixture, and the text F.780.6(25) is at the bottom right.
+
+Figure 6-1 – Description of the problem
+
+## 7 Conditions for high-fidelity colour reproduction
+
+The overview of the framework is shown in Figure 7-1. A light source illuminates objects and the reflected light is input to the camera as scene light. Requirements for the light source and test object colours are described in clauses 7.1 and 7.2, respectively. The scene light is captured by the camera and converted to electronic signals for transmission and display. Requirements for the camera and transmission are described in clauses 7.3 and 7.4, respectively. The transmitted signals are input to the display, which reproduces the scene light as displayed light. The colour appearance of the displayed light is affected by viewing conditions. Requirements for the viewing conditions and display are described in clauses 7.5 and 7.6, respectively. Requirements for the overall characteristics of the system consisting of the camera, transmission and display are described in clause 7.7.
+
+![Figure 7-1 – Overview of the relevant system. The diagram illustrates the flow of light and image data from a light source (7.1) illuminating an object (7.2) to a camera (7.3), then through transmission (7.4) to a display (7.6), and finally to a human eye (CIE standard observer CIEXYZ). The viewing condition (7.5) is also shown.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+The diagram shows the following components and flow:
+
+- Light source (7.1)**: Illuminates the object with **Illumination (Incidence)**.
+- Object images (7.2)**: A red apple that reflects **Scene light (Reflection)** to the camera.
+- Camera (7.3)**: Captures the reflected light.
+- Transmission (7.4)**: The signal from the camera is transmitted.
+- Display (7.6)**: Receives the transmitted signal and emits **Display light (Incidence)** to the eye.
+- Viewing condition (7.5)**: The environment and lighting for viewing the display.
+- Human eye (CIE standard observer CIEXYZ)**: The final receiver of the light signal.
+
+Figure 7-1 – Overview of the relevant system. The diagram illustrates the flow of light and image data from a light source (7.1) illuminating an object (7.2) to a camera (7.3), then through transmission (7.4) to a display (7.6), and finally to a human eye (CIE standard observer CIEXYZ). The viewing condition (7.5) is also shown.
+
+F.780.6(25)
+
+Figure 7-1 – Overview of the relevant system
+
+### 7.1 Illumination
+
+Illumination for ultra-high definition (UHD) and high colour fidelity medical imaging is recommended to satisfy the following conditions:
+
+- Correlated colour temperature (CCT): 4 000 K to 5 300 K.
+- Colour rendering index (CRI): Ra is 90 or over, and R9 is 80 or over.
+
+### 7.2 Test colours
+
+Test colours for medical imaging equipment are shown in Annex A. The test colours should be used for measurement, calibration, etc. of colour reproducibility of medical imaging equipment.
+
+### 7.3 Colour reproduction of camera
+
+#### 7.3.1 Measurement method
+
+The measurement method for colour reproducibility of a camera is recommended to use the Measurement methods for colour capturing accuracy of cameras (CCAC) described in Annex B.
+
+Note that this method measures the colour reproducibility of camera output signals in the linear red green blue (RGB) signal domain or before applying any "gamma pre-correction" (opto-electronic transfer function (OETF)). The OETF will be described in clause 7.4.1.
+
+#### 7.3.2 Colour reproduction error
+
+Colour reproduction error of camera for ultra-high definition and high colour fidelity medical imaging should be assessed by colour difference  $\Delta E^*_{ab}$ .
+
+The  $\Delta E^*_{ab}$  should be measured using the method described in clause 7.3.1, for the test colours described in clause 7.2, under the illumination described in clause 7.1.
+
+The resultant  $\Delta E^*_{ab}$  is recommended to satisfy the following.
+
+$\Delta E^*_{ab}$  is 5 or less.
+
+The formula for calculating  $\Delta E$  recommended in this document is [ISO/CIE 11664-4] (denoted  $\Delta E^*_{ab}$ ), as calculated by:
+
+$$\Delta E^*_{ab} = \sqrt{(L^*_2 - L^*_1)^2 + (a^*_2 - a^*_1)^2 + (b^*_2 - b^*_1)^2}$$
+
+where:
+
+$L_1, a_1, b_1$  are Lab values of each test colour illuminated by the illumination used in the measurement;
+
+$L_2, a_2, b_2$  are Lab values of the linear camera output for the test colour illuminated by the illumination used in the measurement.
+
+### 7.4 Transmission of image signals
+
+#### 7.4.1 Signal format of camera output
+
+The signal format of the camera output for display and transmission should follow [ITU-R BT.2020]. Especially, the system colourimetry is shown in Table 1, and "gamma pre-correction", or the non-linear opto-electronic transfer function (OETF) is shown in Table 2. For  $Y'C'_B C'_R$  signals, etc., see [ITU-R BT.2020].
+
+**Table 1 – System colourimetry of [ITU-R BT.2020]**
+
+| Parameter                                                                 | Values                               |        |        |
+|---------------------------------------------------------------------------|--------------------------------------|--------|--------|
+| Opto-electronic transfer characteristics before non-linear pre-correction | Assumed linear <sup>(1)</sup>        |        |        |
+| Primary colours and reference white                                       | Chromaticity coordinates (CIE, 1931) | X      | y      |
+|                                                                           | Red primary (R)                      | 0.708  | 0.292  |
+|                                                                           | Green primary (G)                    | 0.170  | 0.797  |
+|                                                                           | Blue primary (B)                     | 0.131  | 0.046  |
+|                                                                           | Reference white (D65)                | 0.3127 | 0.3290 |
+
+<sup>(1)</sup> Picture information can be linearly indicated by the tristimulus values of RGB in the range of 0-1.
+
+**Table 2 – Non-linear opto-electronic transfer function (OETF) of [ITU-R BT.2020]**
+
+| Parameter                    | Values                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                           |
+|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|
+| Signal format                | <i>R'G'B'</i>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                           |
+|                              | Constant luminance<br><i>Y'C'BC'R'RC</i>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Non-constant luminance<br><i>Y'C'BC'R</i> |
+| Non-linear transfer function | $E' = \begin{cases} 4.5E, & 0 \leq E < \beta \\ \alpha E^{0.45} - (\alpha - 1), & \beta \leq E \leq 1 \end{cases}$ <p>where <i>E</i> is the voltage normalized by the reference white level and proportional to the implicit light intensity that would be detected with a reference camera colour channel <i>R, G, B</i>; <i>E'</i> is the resulting non-linear signal.</p> <p><math>\alpha</math> and <math>\beta</math> are the solutions to the following simultaneous equations:</p> $\begin{cases} 4.5\beta = \alpha\beta^{0.45} - \alpha + 1 & (1) \\ 4.5 = 0.45\alpha\beta^{-0.55} & (2) \end{cases}$ <p>The simultaneous equations provide the required condition to connect the two curve segments smoothly and yield <math>\alpha = 1.09929682680944\dots</math> and <math>\beta = 0.018053968510807\dots</math>. For practical purposes, the following values can be used:<br/> <math>\alpha = 1.099</math> and <math>\beta = 0.018</math> for 10-bit systems <math>\alpha = 1.0993</math> and <math>\beta = 0.0181</math> for 12-bit systems</p> |                                           |
+
+Note that the reference gamma characteristic of the reference monitor described in [b-ITU-R BT.1886] is not the inverse function of the OETF in Table 2, so it is not suitable for use in displays for high-fidelity colour reproduction.
+
+#### **7.4.2 Coding, transmission and decoding of image signals**
+
+As for coding, transmission and decoding of ultra-high definition and high colour fidelity image signals, it is recommended to follow the requirements described in [ITU-T F.780.1] clause 7.2.
+
+### **7.5 Viewing conditions**
+
+Viewing conditions for ultra-high definition and high colour fidelity medical images are recommended to satisfy Table 3.
+
+These conditions mainly assume medical examination room including telemedicine, or an area away from surgical lights in an operating room.
+
+**Table 3 – Viewing conditions**
+
+| Parameter                                                            | Values                                      |
+|----------------------------------------------------------------------|---------------------------------------------|
+| Room illumination                                                    |                                             |
+| Correlated colour temperature (CCT)                                  | 4 000 K to 5 300 K                          |
+| Colour rendering index (CRI): Ra                                     | 90 or over                                  |
+| R9                                                                   | 80 or over                                  |
+| Horizontal illuminance near the front of the screen of image display | 500 lux to 1 500 lux                        |
+| Display screen angle                                                 | Vertical or approximately 15 degrees tilted |
+
+**Table 3 – Viewing conditions**
+
+| Parameter                                                                                                                                                                                                                                        | Values                                                                                      |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|
+| Display installation location                                                                                                                                                                                                                    | Avoid direct reflections of light from any light source onto viewers, on the display screen |
+| Peak luminance <sup>(1)</sup> of displayed image                                                                                                                                                                                                 | 100 cd/m <sup>2</sup> to 500 cd/m <sup>2</sup>                                              |
+| Display contrast ratio                                                                                                                                                                                                                           | 0.02 or less                                                                                |
+| Ratio of luminance of surround <sup>(2)</sup> behind the display to the peak luminance                                                                                                                                                           | Approximately 10 to 20%                                                                     |
+| <sup>(1)</sup> Peak luminance should be adjusted according to the room illumination.<br><sup>(2)</sup> "Surround" is the area surrounding a display that can affect the adaptation of the eye, typically the wall or curtain behind the display. |                                                                                             |
+
+### 7.6 Colour reproduction of display
+
+#### 7.6.1 Measurement method
+
+Measurement method of colour reproducibility of a display is described in Annex C.
+
+The display input signal for this measurement should follow the signal format described in clause 7.4.1.
+
+#### 7.6.2 Colour reproduction error
+
+Colour reproduction error of display for ultra-high definition and high colour fidelity medical imaging should also be assessed by colour difference  $\Delta E^*_{ab}$ .
+
+The reference display input signal for the measurement should have R'G'B' values in the signal format described in clause 7.4.1, for the test colours described in clause 7.2, under the illumination described in clause 7.1. The reference signal means the output of an ideal camera of [ITU-R BT.2020].
+
+The  $\Delta E^*_{ab}$  should be measured using the method described in clause 7.6.1, for the reference display input signals, under the viewing conditions described in clause 7.5.
+
+The resultant  $\Delta E^*_{ab}$  is recommended to satisfy the following, over a certain viewing angle range.
+
+Note that the viewing angle range of a display does not directly relate to the field of view (FOV) of a video system.
+
+$\Delta E^*_{ab}$  is 5 or less, in viewing angle range within  $\pm 30$  arc degrees horizontally and  $\pm 15$  arc degrees vertically, where  $\Delta E^*_{ab}$  is calculated by:
+
+$$\Delta E^*_{ab} = \sqrt{(L^*_2 - L^*_1)^2 + (a^*_2 - a^*_1)^2 + (b^*_2 - b^*_1)^2}$$
+
+where:
+
+$L_1, a_1, b_1$  are Lab values of each test colour illuminated by the illumination used to derive the reference display input signal;
+
+$L_2, a_2, b_2$  are Lab values of the displayed light for the reference display input signals for the test colour, under the viewing conditions described in clause 7.5.
+
+The CCT of the display should be adequately adjusted to meet the above requirement for  $\Delta E^*_{ab}$ .
+
+### 7.7 Overall characteristics of system
+
+When a check of the overall characteristics of the system is required, follow the below steps.
+
+Shoot test colours described in clause 7.2 by the camera of the system, following the conditions and capturing procedure described in Annex B, under the illumination described in clause 7.1.
+
+Input the camera output with the signal format described in clause 7.4.1, to the display of the system.
+
+The coding, transmission and decoding process described in clause 7.4.2 are inserted between the camera and the display, if it is necessary.
+
+The  $\Delta E^*_{ab}$  should be measured using the method described in clause 7.6.1, for the display input signals of the system, under the viewing conditions described in clause 7.5.
+
+The resultant  $\Delta E^*_{ab}$  is recommended to satisfy the following, over a certain viewing angle range.
+
+Note that the viewing angle range of a display does not directly relate to the FOV of a video system.
+
+$\Delta E^*_{ab}$  is 7 or less, in the viewing angle range within  $\pm 30$  arc degrees horizontally and  $\pm 15$  arc degrees vertically, where  $\Delta E^*_{ab}$  is calculated by:
+
+$$\Delta E^*_{ab} = \sqrt{(L^*_2 - L^*_1)^2 + (a^*_2 - a^*_1)^2 + (b^*_2 - b^*_1)^2}$$
+
+where:
+
+$L_1, a_1, b_1$  are Lab values of each test colour illuminated by the illumination used in the measurement;
+
+$L_2, a_2, b_2$  are Lab values of the displayed light for the system display input signals for the test colour, under the viewing conditions described in clause 7.5.
+
+The CCT of the display should be adequately adjusted to meet the above requirement for  $\Delta E^*_{ab}$ .
+
+### 7.8 Application to equipment and systems other than those of [ITU-R BT.2020]
+
+The above conditions and methods can be applied to equipment and systems other than those of [ITU-R BT.2020] with some modifications. The modifications for application to equipment and systems of [ITU-R BT.709] is provided in Annex D.
+
+## 8 Conditions required for colour reproduction of specific surgical images
+
+For monitors of specific surgical images, it may be desirable to reproduce colours with good discrimination of human tissues rather than the faithful reproduction of colours.
+
+In such cases, the characteristics of the high colour fidelity system may not be suitable. In these cases, as an option, the system should be designed to reproduce the colours of human tissues with good discrimination. It is desirable for the system to be able to perform the colour-enhancement processing for better discrimination as an option, on the basis that the system satisfies the requirements for high-fidelity colour reproduction described in clause 7.
+
+Further potential requirements and specific colour enhancement method may be described in the future.
+
+## Annex A
+
+### Test colours for medical imaging equipment
+
+(This annex forms an integral part of this Recommendation.)
+
+Test colours for medical imaging equipment are shown in Table A.1.
+
+The table needs to be reviewed and updated in future.
+
+**Table A.1 – Spectral reflectance of test colours for medical imaging equipment**
+
+| Number                    | 1                | 2                | 3                | 4                | 5                | 6                | 7                | 8                |
+|---------------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|
+| Source                    | CIE13.3<br>TCS01 | CIE13.3<br>TCS02 | CIE13.3<br>TCS03 | CIE13.3<br>TCS04 | CIE13.3<br>TCS05 | CIE13.3<br>TCS06 | CIE13.3<br>TCS07 | CIE13.3<br>TCS08 |
+| HV/C                      | 7.5R6/4          | 5Y6/4            | 5GY6/8           | 2.5G6/6          | 10BG6/4          | 5PB6/8           | 2.5P6/8          | 10P6/8           |
+| Wavelength $\lambda$ (nm) |                  |                  |                  |                  |                  |                  |                  |                  |
+| 380                       | 0.219            | 0.070            | 0.065            | 0.074            | 0.295            | 0.151            | 0.378            | 0.104            |
+| 385                       | 0.239            | 0.079            | 0.068            | 0.083            | 0.306            | 0.203            | 0.459            | 0.129            |
+| 390                       | 0.252            | 0.089            | 0.070            | 0.093            | 0.310            | 0.265            | 0.524            | 0.170            |
+| 395                       | 0.256            | 0.101            | 0.072            | 0.105            | 0.312            | 0.339            | 0.546            | 0.240            |
+| 400                       | 0.256            | 0.111            | 0.073            | 0.116            | 0.313            | 0.410            | 0.551            | 0.319            |
+| 405                       | 0.254            | 0.116            | 0.073            | 0.121            | 0.315            | 0.464            | 0.555            | 0.416            |
+| 410                       | 0.252            | 0.118            | 0.074            | 0.124            | 0.319            | 0.492            | 0.559            | 0.462            |
+| 415                       | 0.248            | 0.120            | 0.074            | 0.126            | 0.322            | 0.508            | 0.560            | 0.482            |
+| 420                       | 0.244            | 0.121            | 0.074            | 0.128            | 0.326            | 0.517            | 0.561            | 0.490            |
+| 425                       | 0.240            | 0.122            | 0.073            | 0.131            | 0.330            | 0.524            | 0.558            | 0.488            |
+| 430                       | 0.237            | 0.122            | 0.073            | 0.135            | 0.334            | 0.531            | 0.556            | 0.482            |
+| 435                       | 0.232            | 0.122            | 0.073            | 0.139            | 0.339            | 0.538            | 0.551            | 0.473            |
+| 440                       | 0.230            | 0.123            | 0.073            | 0.144            | 0.346            | 0.544            | 0.544            | 0.462            |
+| 445                       | 0.226            | 0.124            | 0.073            | 0.151            | 0.352            | 0.551            | 0.535            | 0.450            |
+| 450                       | 0.225            | 0.127            | 0.074            | 0.161            | 0.360            | 0.556            | 0.522            | 0.439            |
+| 455                       | 0.222            | 0.128            | 0.075            | 0.172            | 0.369            | 0.556            | 0.506            | 0.426            |
+| 460                       | 0.220            | 0.131            | 0.077            | 0.186            | 0.381            | 0.554            | 0.488            | 0.413            |
+| 465                       | 0.218            | 0.134            | 0.080            | 0.205            | 0.394            | 0.549            | 0.469            | 0.397            |
+| 470                       | 0.216            | 0.138            | 0.085            | 0.229            | 0.403            | 0.541            | 0.448            | 0.382            |
+| 475                       | 0.214            | 0.143            | 0.094            | 0.254            | 0.410            | 0.531            | 0.429            | 0.366            |
+| 480                       | 0.214            | 0.150            | 0.109            | 0.281            | 0.415            | 0.519            | 0.408            | 0.352            |
+| 485                       | 0.214            | 0.159            | 0.126            | 0.308            | 0.418            | 0.504            | 0.385            | 0.337            |
+| 490                       | 0.216            | 0.174            | 0.148            | 0.332            | 0.419            | 0.488            | 0.363            | 0.325            |
+| 495                       | 0.218            | 0.190            | 0.172            | 0.352            | 0.417            | 0.469            | 0.341            | 0.310            |
+| 500                       | 0.223            | 0.207            | 0.198            | 0.370            | 0.413            | 0.450            | 0.324            | 0.299            |
+| 505                       | 0.225            | 0.225            | 0.221            | 0.383            | 0.409            | 0.431            | 0.311            | 0.289            |
+
+**Table A.1 – Spectral reflectance of test colours for medical imaging equipment**
+
+| Number                                      | 1                | 2                | 3                | 4                | 5                | 6                | 7                | 8                |
+|---------------------------------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|
+| Source                                      | CIE13.3<br>TCS01 | CIE13.3<br>TCS02 | CIE13.3<br>TCS03 | CIE13.3<br>TCS04 | CIE13.3<br>TCS05 | CIE13.3<br>TCS06 | CIE13.3<br>TCS07 | CIE13.3<br>TCS08 |
+| HV/C                                        | 7.5R6/4          | 5Y6/4            | 5GY6/8           | 2.5G6/6          | 10BG6/4          | 5PB6/8           | 2.5P6/8          | 10P6/8           |
+| <b>Wavelength <math>\lambda</math> (nm)</b> |                  |                  |                  |                  |                  |                  |                  |                  |
+| 510                                         | 0.226            | 0.242            | 0.241            | 0.390            | 0.403            | 0.414            | 0.301            | 0.283            |
+| 515                                         | 0.226            | 0.253            | 0.260            | 0.394            | 0.396            | 0.395            | 0.291            | 0.276            |
+| 520                                         | 0.225            | 0.260            | 0.278            | 0.395            | 0.389            | 0.377            | 0.283            | 0.270            |
+| 525                                         | 0.225            | 0.264            | 0.302            | 0.392            | 0.381            | 0.358            | 0.273            | 0.262            |
+| 530                                         | 0.227            | 0.267            | 0.339            | 0.385            | 0.372            | 0.341            | 0.265            | 0.256            |
+| 535                                         | 0.230            | 0.269            | 0.370            | 0.377            | 0.363            | 0.325            | 0.260            | 0.251            |
+| 540                                         | 0.236            | 0.272            | 0.392            | 0.367            | 0.353            | 0.309            | 0.257            | 0.250            |
+| 545                                         | 0.245            | 0.276            | 0.399            | 0.354            | 0.342            | 0.293            | 0.257            | 0.251            |
+| 550                                         | 0.253            | 0.282            | 0.400            | 0.341            | 0.331            | 0.279            | 0.259            | 0.254            |
+| 555                                         | 0.262            | 0.289            | 0.393            | 0.327            | 0.320            | 0.265            | 0.260            | 0.258            |
+| 560                                         | 0.272            | 0.299            | 0.380            | 0.312            | 0.308            | 0.253            | 0.260            | 0.264            |
+| 565                                         | 0.283            | 0.309            | 0.365            | 0.296            | 0.296            | 0.241            | 0.258            | 0.269            |
+| 570                                         | 0.298            | 0.322            | 0.349            | 0.280            | 0.284            | 0.234            | 0.256            | 0.272            |
+| 575                                         | 0.318            | 0.329            | 0.332            | 0.263            | 0.271            | 0.227            | 0.254            | 0.274            |
+| 580                                         | 0.341            | 0.335            | 0.315            | 0.247            | 0.260            | 0.225            | 0.254            | 0.278            |
+| 585                                         | 0.367            | 0.339            | 0.299            | 0.229            | 0.247            | 0.222            | 0.259            | 0.284            |
+| 590                                         | 0.390            | 0.341            | 0.285            | 0.214            | 0.232            | 0.221            | 0.270            | 0.295            |
+| 595                                         | 0.409            | 0.341            | 0.272            | 0.198            | 0.220            | 0.220            | 0.284            | 0.316            |
+| 600                                         | 0.424            | 0.342            | 0.264            | 0.185            | 0.210            | 0.220            | 0.302            | 0.348            |
+| 605                                         | 0.435            | 0.342            | 0.257            | 0.175            | 0.200            | 0.220            | 0.324            | 0.384            |
+| 610                                         | 0.442            | 0.342            | 0.252            | 0.169            | 0.194            | 0.220            | 0.344            | 0.434            |
+| 615                                         | 0.448            | 0.341            | 0.247            | 0.164            | 0.189            | 0.220            | 0.362            | 0.482            |
+| 620                                         | 0.450            | 0.341            | 0.241            | 0.160            | 0.185            | 0.223            | 0.377            | 0.528            |
+| 625                                         | 0.451            | 0.339            | 0.235            | 0.156            | 0.183            | 0.227            | 0.389            | 0.568            |
+| 630                                         | 0.451            | 0.339            | 0.229            | 0.154            | 0.180            | 0.233            | 0.400            | 0.604            |
+| 635                                         | 0.451            | 0.338            | 0.224            | 0.152            | 0.177            | 0.239            | 0.410            | 0.629            |
+| 640                                         | 0.451            | 0.338            | 0.220            | 0.151            | 0.176            | 0.244            | 0.420            | 0.648            |
+| 645                                         | 0.451            | 0.337            | 0.217            | 0.149            | 0.175            | 0.251            | 0.429            | 0.663            |
+| 650                                         | 0.450            | 0.336            | 0.216            | 0.148            | 0.175            | 0.258            | 0.438            | 0.676            |
+| 655                                         | 0.450            | 0.335            | 0.216            | 0.148            | 0.175            | 0.263            | 0.445            | 0.685            |
+| 660                                         | 0.451            | 0.334            | 0.219            | 0.148            | 0.175            | 0.268            | 0.452            | 0.693            |
+| 665                                         | 0.451            | 0.332            | 0.224            | 0.149            | 0.177            | 0.273            | 0.457            | 0.700            |
+
+**Table A.1 – Spectral reflectance of test colours for medical imaging equipment**
+
+| Number                                      | 1                | 2                | 3                | 4                | 5                | 6                | 7                | 8                |
+|---------------------------------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|
+| Source                                      | CIE13.3<br>TCS01 | CIE13.3<br>TCS02 | CIE13.3<br>TCS03 | CIE13.3<br>TCS04 | CIE13.3<br>TCS05 | CIE13.3<br>TCS06 | CIE13.3<br>TCS07 | CIE13.3<br>TCS08 |
+| HV/C                                        | 7.5R6/4          | 5Y6/4            | 5GY6/8           | 2.5G6/6          | 10BG6/4          | 5PB6/8           | 2.5P6/8          | 10P6/8           |
+| <b>Wavelength <math>\lambda</math> (nm)</b> |                  |                  |                  |                  |                  |                  |                  |                  |
+| 670                                         | 0.453            | 0.332            | 0.230            | 0.151            | 0.180            | 0.278            | 0.462            | 0.705            |
+| 675                                         | 0.454            | 0.331            | 0.238            | 0.154            | 0.183            | 0.281            | 0.466            | 0.709            |
+| 680                                         | 0.455            | 0.331            | 0.251            | 0.158            | 0.186            | 0.283            | 0.468            | 0.712            |
+| 685                                         | 0.457            | 0.330            | 0.269            | 0.162            | 0.189            | 0.286            | 0.470            | 0.715            |
+| 690                                         | 0.458            | 0.329            | 0.288            | 0.165            | 0.192            | 0.291            | 0.473            | 0.717            |
+| 695                                         | 0.460            | 0.328            | 0.312            | 0.168            | 0.195            | 0.296            | 0.477            | 0.719            |
+| 700                                         | 0.462            | 0.328            | 0.340            | 0.170            | 0.199            | 0.302            | 0.483            | 0.721            |
+| 705                                         | 0.463            | 0.327            | 0.366            | 0.171            | 0.200            | 0.313            | 0.489            | 0.720            |
+| 710                                         | 0.464            | 0.326            | 0.390            | 0.170            | 0.199            | 0.325            | 0.496            | 0.719            |
+| 715                                         | 0.465            | 0.325            | 0.412            | 0.168            | 0.198            | 0.338            | 0.503            | 0.722            |
+| 720                                         | 0.466            | 0.324            | 0.431            | 0.166            | 0.196            | 0.351            | 0.511            | 0.725            |
+| 725                                         | 0.466            | 0.324            | 0.447            | 0.164            | 0.195            | 0.364            | 0.518            | 0.727            |
+| 730                                         | 0.466            | 0.324            | 0.460            | 0.164            | 0.195            | 0.376            | 0.525            | 0.729            |
+| 735                                         | 0.466            | 0.323            | 0.472            | 0.165            | 0.196            | 0.389            | 0.532            | 0.730            |
+| 740                                         | 0.467            | 0.322            | 0.481            | 0.168            | 0.197            | 0.401            | 0.539            | 0.730            |
+| 745                                         | 0.467            | 0.321            | 0.488            | 0.172            | 0.200            | 0.413            | 0.546            | 0.730            |
+| 750                                         | 0.467            | 0.320            | 0.493            | 0.177            | 0.203            | 0.425            | 0.553            | 0.730            |
+| 755                                         | 0.467            | 0.318            | 0.497            | 0.181            | 0.205            | 0.436            | 0.559            | 0.730            |
+| 760                                         | 0.467            | 0.316            | 0.500            | 0.185            | 0.208            | 0.447            | 0.565            | 0.730            |
+| 765                                         | 0.467            | 0.315            | 0.502            | 0.189            | 0.212            | 0.458            | 0.570            | 0.730            |
+| 770                                         | 0.467            | 0.315            | 0.505            | 0.192            | 0.215            | 0.469            | 0.575            | 0.730            |
+| 775                                         | 0.467            | 0.314            | 0.510            | 0.194            | 0.217            | 0.477            | 0.578            | 0.730            |
+| 780                                         | 0.467            | 0.314            | 0.516            | 0.197            | 0.219            | 0.485            | 0.581            | 0.730            |
+
+**Table A.1 – Spectral reflectance of test colours for medical imaging equipment**
+
+| Number                                      | 9                | 10               | 11               | 12               | 13               | 14               | 15                |
+|---------------------------------------------|------------------|------------------|------------------|------------------|------------------|------------------|-------------------|
+| Source                                      | CIE13.3<br>TCS09 | CIE13.3<br>TCS10 | CIE13.3<br>TCS11 | CIE13.3<br>TCS12 | CIE13.3<br>TCS13 | CIE13.3<br>TCS14 | JISZ8726<br>No.15 |
+| HV/C                                        | 4.5R4/13         | 5Y8/10           | 4.5G5/8          | 3PB3/11          | 5YR8/4           | 5GY4/4           | 1YR6/4            |
+| <b>Wavelength <math>\lambda</math> (nm)</b> |                  |                  |                  |                  |                  |                  |                   |
+| 380                                         | 0.066            | 0.050            | 0.111            | 0.120            | 0.104            | 0.036            | 0.131             |
+
+**Table A.1 – Spectral reflectance of test colours for medical imaging equipment**
+
+| Number                                      | 9                | 10               | 11               | 12               | 13               | 14               | 15                |
+|---------------------------------------------|------------------|------------------|------------------|------------------|------------------|------------------|-------------------|
+| Source                                      | CIE13.3<br>TCS09 | CIE13.3<br>TCS10 | CIE13.3<br>TCS11 | CIE13.3<br>TCS12 | CIE13.3<br>TCS13 | CIE13.3<br>TCS14 | JISZ8726<br>No.15 |
+| HV/C                                        | 4.5R4/13         | 5Y8/10           | 4.5G5/8          | 3PB3/11          | 5YR8/4           | 5GY4/4           | 1YR6/4            |
+| <b>Wavelength <math>\lambda</math> (nm)</b> |                  |                  |                  |                  |                  |                  |                   |
+| 385                                         | 0.062            | 0.054            | 0.121            | 0.103            | 0.127            | 0.036            | 0.139             |
+| 390                                         | 0.058            | 0.059            | 0.127            | 0.090            | 0.161            | 0.037            | 0.147             |
+| 395                                         | 0.055            | 0.063            | 0.129            | 0.082            | 0.211            | 0.038            | 0.153             |
+| 400                                         | 0.052            | 0.066            | 0.127            | 0.076            | 0.264            | 0.039            | 0.158             |
+| 405                                         | 0.052            | 0.067            | 0.121            | 0.068            | 0.313            | 0.039            | 0.162             |
+| 410                                         | 0.051            | 0.068            | 0.116            | 0.064            | 0.341            | 0.040            | 0.164             |
+| 415                                         | 0.050            | 0.069            | 0.112            | 0.065            | 0.352            | 0.041            | 0.167             |
+| 420                                         | 0.050            | 0.069            | 0.108            | 0.075            | 0.359            | 0.042            | 0.170             |
+| 425                                         | 0.049            | 0.070            | 0.105            | 0.093            | 0.361            | 0.042            | 0.175             |
+| 430                                         | 0.048            | 0.072            | 0.104            | 0.123            | 0.364            | 0.043            | 0.182             |
+| 435                                         | 0.047            | 0.073            | 0.104            | 0.160            | 0.365            | 0.044            | 0.192             |
+| 440                                         | 0.046            | 0.076            | 0.105            | 0.207            | 0.367            | 0.044            | 0.203             |
+| 445                                         | 0.044            | 0.078            | 0.106            | 0.256            | 0.369            | 0.045            | 0.212             |
+| 450                                         | 0.042            | 0.083            | 0.110            | 0.300            | 0.372            | 0.045            | 0.221             |
+| 455                                         | 0.041            | 0.088            | 0.115            | 0.331            | 0.374            | 0.046            | 0.229             |
+| 460                                         | 0.038            | 0.095            | 0.123            | 0.346            | 0.376            | 0.047            | 0.236             |
+| 465                                         | 0.035            | 0.103            | 0.134            | 0.347            | 0.379            | 0.048            | 0.243             |
+| 470                                         | 0.033            | 0.113            | 0.148            | 0.341            | 0.384            | 0.050            | 0.249             |
+| 475                                         | 0.031            | 0.125            | 0.167            | 0.328            | 0.389            | 0.052            | 0.254             |
+| 480                                         | 0.030            | 0.142            | 0.192            | 0.307            | 0.397            | 0.055            | 0.259             |
+| 485                                         | 0.029            | 0.162            | 0.219            | 0.282            | 0.405            | 0.057            | 0.264             |
+| 490                                         | 0.028            | 0.189            | 0.252            | 0.257            | 0.416            | 0.062            | 0.269             |
+| 495                                         | 0.028            | 0.219            | 0.291            | 0.230            | 0.429            | 0.067            | 0.276             |
+| 500                                         | 0.028            | 0.262            | 0.325            | 0.204            | 0.443            | 0.075            | 0.284             |
+| 505                                         | 0.029            | 0.305            | 0.347            | 0.178            | 0.454            | 0.083            | 0.291             |
+| 510                                         | 0.030            | 0.365            | 0.356            | 0.154            | 0.461            | 0.092            | 0.296             |
+| 515                                         | 0.030            | 0.416            | 0.353            | 0.129            | 0.466            | 0.100            | 0.298             |
+| 520                                         | 0.031            | 0.465            | 0.346            | 0.109            | 0.469            | 0.108            | 0.296             |
+| 525                                         | 0.031            | 0.509            | 0.333            | 0.090            | 0.471            | 0.121            | 0.289             |
+| 530                                         | 0.032            | 0.546            | 0.314            | 0.075            | 0.474            | 0.133            | 0.282             |
+| 535                                         | 0.032            | 0.581            | 0.294            | 0.062            | 0.476            | 0.142            | 0.276             |
+| 540                                         | 0.033            | 0.610            | 0.271            | 0.051            | 0.483            | 0.150            | 0.274             |
+
+**Table A.1 – Spectral reflectance of test colours for medical imaging equipment**
+
+| Number                                      | 9                | 10               | 11               | 12               | 13               | 14               | 15                |
+|---------------------------------------------|------------------|------------------|------------------|------------------|------------------|------------------|-------------------|
+| Source                                      | CIE13.3<br>TCS09 | CIE13.3<br>TCS10 | CIE13.3<br>TCS11 | CIE13.3<br>TCS12 | CIE13.3<br>TCS13 | CIE13.3<br>TCS14 | JISZ8726<br>No.15 |
+| HV/C                                        | 4.5R4/13         | 5Y8/10           | 4.5G5/8          | 3PB3/11          | 5YR8/4           | 5GY4/4           | 1YR6/4            |
+| <b>Wavelength <math>\lambda</math> (nm)</b> |                  |                  |                  |                  |                  |                  |                   |
+| 545                                         | 0.034            | 0.634            | 0.248            | 0.041            | 0.490            | 0.154            | 0.276             |
+|                                             |                  |                  |                  |                  |                  |                  |                   |
+| 550                                         | 0.035            | 0.653            | 0.227            | 0.035            | 0.506            | 0.155            | 0.281             |
+| 555                                         | 0.037            | 0.666            | 0.206            | 0.029            | 0.526            | 0.152            | 0.286             |
+| 560                                         | 0.041            | 0.678            | 0.188            | 0.025            | 0.553            | 0.147            | 0.291             |
+| 565                                         | 0.044            | 0.687            | 0.170            | 0.022            | 0.582            | 0.140            | 0.289             |
+| 570                                         | 0.048            | 0.693            | 0.153            | 0.019            | 0.618            | 0.133            | 0.286             |
+|                                             |                  |                  |                  |                  |                  |                  |                   |
+| 575                                         | 0.052            | 0.698            | 0.138            | 0.017            | 0.651            | 0.125            | 0.280             |
+| 580                                         | 0.060            | 0.701            | 0.125            | 0.017            | 0.680            | 0.118            | 0.285             |
+| 585                                         | 0.076            | 0.704            | 0.114            | 0.017            | 0.701            | 0.112            | 0.314             |
+| 590                                         | 0.102            | 0.705            | 0.106            | 0.016            | 0.717            | 0.106            | 0.354             |
+| 595                                         | 0.136            | 0.705            | 0.100            | 0.016            | 0.729            | 0.101            | 0.398             |
+|                                             |                  |                  |                  |                  |                  |                  |                   |
+| 600                                         | 0.190            | 0.706            | 0.096            | 0.016            | 0.736            | 0.098            | 0.440             |
+| 605                                         | 0.256            | 0.707            | 0.092            | 0.016            | 0.742            | 0.095            | 0.470             |
+| 610                                         | 0.336            | 0.707            | 0.090            | 0.016            | 0.745            | 0.093            | 0.494             |
+| 615                                         | 0.418            | 0.707            | 0.087            | 0.016            | 0.747            | 0.090            | 0.511             |
+| 620                                         | 0.505            | 0.708            | 0.085            | 0.016            | 0.748            | 0.089            | 0.524             |
+|                                             |                  |                  |                  |                  |                  |                  |                   |
+| 625                                         | 0.581            | 0.708            | 0.082            | 0.016            | 0.748            | 0.087            | 0.535             |
+| 630                                         | 0.641            | 0.710            | 0.080            | 0.018            | 0.748            | 0.086            | 0.544             |
+| 635                                         | 0.682            | 0.711            | 0.079            | 0.018            | 0.748            | 0.085            | 0.552             |
+| 640                                         | 0.717            | 0.712            | 0.078            | 0.018            | 0.748            | 0.084            | 0.559             |
+| 645                                         | 0.740            | 0.714            | 0.078            | 0.018            | 0.748            | 0.084            | 0.565             |
+|                                             |                  |                  |                  |                  |                  |                  |                   |
+| 650                                         | 0.758            | 0.716            | 0.078            | 0.019            | 0.748            | 0.084            | 0.571             |
+| 655                                         | 0.770            | 0.718            | 0.078            | 0.020            | 0.748            | 0.084            | 0.576             |
+| 660                                         | 0.781            | 0.720            | 0.081            | 0.023            | 0.747            | 0.085            | 0.581             |
+| 665                                         | 0.790            | 0.722            | 0.083            | 0.024            | 0.747            | 0.087            | 0.586             |
+| 670                                         | 0.797            | 0.725            | 0.088            | 0.026            | 0.747            | 0.092            | 0.590             |
+|                                             |                  |                  |                  |                  |                  |                  |                   |
+| 675                                         | 0.803            | 0.729            | 0.093            | 0.030            | 0.747            | 0.096            | 0.594             |
+| 680                                         | 0.809            | 0.731            | 0.102            | 0.035            | 0.747            | 0.102            | 0.599             |
+| 685                                         | 0.814            | 0.735            | 0.112            | 0.043            | 0.747            | 0.110            | 0.603             |
+| 690                                         | 0.819            | 0.739            | 0.125            | 0.056            | 0.747            | 0.123            | 0.606             |
+| 695                                         | 0.824            | 0.742            | 0.141            | 0.074            | 0.746            | 0.137            | 0.610             |
+|                                             |                  |                  |                  |                  |                  |                  |                   |
+
+**Table A.1 – Spectral reflectance of test colours for medical imaging equipment**
+
+| Number                                      | 9                | 10               | 11               | 12               | 13               | 14               | 15                |
+|---------------------------------------------|------------------|------------------|------------------|------------------|------------------|------------------|-------------------|
+| Source                                      | CIE13.3<br>TCS09 | CIE13.3<br>TCS10 | CIE13.3<br>TCS11 | CIE13.3<br>TCS12 | CIE13.3<br>TCS13 | CIE13.3<br>TCS14 | JISZ8726<br>No.15 |
+| HV/C                                        | 4.5R4/13         | 5Y8/10           | 4.5G5/8          | 3PB3/11          | 5YR8/4           | 5GY4/4           | 1YR6/4            |
+| <b>Wavelength <math>\lambda</math> (nm)</b> |                  |                  |                  |                  |                  |                  |                   |
+| 700                                         | 0.828            | 0.746            | 0.161            | 0.097            | 0.746            | 0.152            | 0.612             |
+| 705                                         | 0.830            | 0.748            | 0.182            | 0.128            | 0.746            | 0.169            | 0.614             |
+| 710                                         | 0.831            | 0.749            | 0.203            | 0.166            | 0.745            | 0.188            | 0.616             |
+| 715                                         | 0.833            | 0.751            | 0.223            | 0.210            | 0.744            | 0.207            | 0.616             |
+| 720                                         | 0.835            | 0.753            | 0.242            | 0.257            | 0.743            | 0.226            | 0.616             |
+| 725                                         | 0.836            | 0.754            | 0.257            | 0.305            | 0.744            | 0.243            | 0.616             |
+| 730                                         | 0.836            | 0.755            | 0.270            | 0.354            | 0.745            | 0.260            | 0.615             |
+| 735                                         | 0.837            | 0.755            | 0.282            | 0.401            | 0.748            | 0.277            | 0.613             |
+| 740                                         | 0.838            | 0.755            | 0.292            | 0.446            | 0.750            | 0.294            | 0.612             |
+| 745                                         | 0.839            | 0.755            | 0.302            | 0.485            | 0.750            | 0.310            | 0.610             |
+| 750                                         | 0.839            | 0.756            | 0.310            | 0.520            | 0.749            | 0.325            | 0.609             |
+| 755                                         | 0.839            | 0.757            | 0.314            | 0.551            | 0.748            | 0.339            | 0.608             |
+| 760                                         | 0.839            | 0.758            | 0.317            | 0.577            | 0.748            | 0.353            | 0.607             |
+| 765                                         | 0.839            | 0.759            | 0.323            | 0.599            | 0.747            | 0.366            | 0.607             |
+| 770                                         | 0.839            | 0.759            | 0.330            | 0.618            | 0.747            | 0.379            | 0.609             |
+| 775                                         | 0.839            | 0.759            | 0.334            | 0.633            | 0.747            | 0.390            | 0.610             |
+| 780                                         | 0.839            | 0.759            | 0.338            | 0.645            | 0.747            | 0.399            | 0.611             |
+
+**Table A.1 – Spectral reflectance of test colours for medical imaging equipment**
+
+| Number                                      | 16                 | 17                 | 18                  | 19                   | 20                | 21                    |
+|---------------------------------------------|--------------------|--------------------|---------------------|----------------------|-------------------|-----------------------|
+| Source                                      | Original<br>(Blue) | Original<br>(Cyan) | Original<br>(Green) | Original<br>(Yellow) | Original<br>(Red) | Original<br>(Magenta) |
+| HV/C                                        | –                  | –                  | –                   | –                    | –                 | –                     |
+| <b>Wavelength <math>\lambda</math> (nm)</b> |                    |                    |                     |                      |                   |                       |
+| 380                                         | 0.000              | 0.000              | 0.000               | 0.000                | 0.000             | 0.024                 |
+| 385                                         | 0.000              | 0.000              | 0.000               | 0.001                | 0.000             | 0.071                 |
+| 390                                         | 0.000              | 0.000              | 0.000               | 0.001                | 0.000             | 0.088                 |
+| 395                                         | 0.000              | 0.002              | 0.000               | 0.002                | 0.000             | 0.099                 |
+| 400                                         | 0.000              | 0.001              | 0.000               | 0.002                | 0.000             | 0.116                 |
+| 405                                         | 0.000              | 0.000              | 0.000               | 0.002                | 0.000             | 0.134                 |
+| 410                                         | 0.000              | 0.001              | 0.000               | 0.002                | 0.000             | 0.149                 |
+
+**Table A.1 – Spectral reflectance of test colours for medical imaging equipment**
+
+| Number                                      | 16              | 17              | 18               | 19                | 20             | 21                 |
+|---------------------------------------------|-----------------|-----------------|------------------|-------------------|----------------|--------------------|
+| Source                                      | Original (Blue) | Original (Cyan) | Original (Green) | Original (Yellow) | Original (Red) | Original (Magenta) |
+| HV/C                                        | –               | –               | –                | –                 | –              | –                  |
+| <b>Wavelength <math>\lambda</math> (nm)</b> |                 |                 |                  |                   |                |                    |
+| 415                                         | 0.000           | 0.003           | 0.000            | 0.002             | 0.000          | 0.166              |
+| 420                                         | 0.000           | 0.011           | 0.000            | 0.002             | 0.000          | 0.186              |
+| 425                                         | 0.000           | 0.026           | 0.000            | 0.002             | 0.000          | 0.217              |
+| 430                                         | 0.001           | 0.045           | 0.000            | 0.002             | 0.000          | 0.253              |
+| 435                                         | 0.012           | 0.067           | 0.000            | 0.002             | 0.000          | 0.293              |
+| 440                                         | 0.061           | 0.095           | 0.000            | 0.003             | 0.000          | 0.323              |
+| 445                                         | 0.173           | 0.129           | 0.000            | 0.003             | 0.000          | 0.329              |
+| 450                                         | 0.314           | 0.173           | 0.000            | 0.003             | 0.000          | 0.312              |
+| 455                                         | 0.409           | 0.221           | 0.000            | 0.003             | 0.000          | 0.285              |
+| 460                                         | 0.434           | 0.271           | 0.000            | 0.003             | 0.000          | 0.251              |
+| 465                                         | 0.409           | 0.321           | 0.000            | 0.004             | 0.000          | 0.212              |
+| 470                                         | 0.348           | 0.362           | 0.000            | 0.004             | 0.000          | 0.174              |
+| 475                                         | 0.269           | 0.386           | 0.001            | 0.004             | 0.001          | 0.137              |
+| 480                                         | 0.192           | 0.416           | 0.001            | 0.005             | 0.001          | 0.100              |
+| 485                                         | 0.130           | 0.449           | 0.002            | 0.005             | 0.001          | 0.071              |
+| 490                                         | 0.080           | 0.461           | 0.006            | 0.006             | 0.001          | 0.049              |
+| 495                                         | 0.044           | 0.465           | 0.018            | 0.008             | 0.000          | 0.033              |
+| 500                                         | 0.022           | 0.458           | 0.057            | 0.010             | 0.000          | 0.022              |
+| 505                                         | 0.009           | 0.433           | 0.139            | 0.012             | 0.000          | 0.015              |
+| 510                                         | 0.003           | 0.404           | 0.256            | 0.015             | 0.000          | 0.010              |
+| 515                                         | 0.001           | 0.374           | 0.377            | 0.019             | 0.000          | 0.007              |
+| 520                                         | 0.000           | 0.342           | 0.455            | 0.027             | 0.000          | 0.004              |
+| 525                                         | 0.000           | 0.310           | 0.472            | 0.039             | 0.000          | 0.003              |
+| 530                                         | 0.000           | 0.280           | 0.452            | 0.065             | 0.000          | 0.002              |
+| 535                                         | 0.000           | 0.247           | 0.401            | 0.110             | 0.000          | 0.002              |
+| 540                                         | 0.000           | 0.207           | 0.334            | 0.181             | 0.000          | 0.002              |
+| 545                                         | 0.000           | 0.175           | 0.269            | 0.261             | 0.000          | 0.002              |
+| 550                                         | 0.000           | 0.142           | 0.206            | 0.347             | 0.000          | 0.002              |
+| 555                                         | 0.000           | 0.115           | 0.148            | 0.413             | 0.000          | 0.002              |
+| 560                                         | 0.000           | 0.094           | 0.096            | 0.449             | 0.000          | 0.002              |
+| 565                                         | 0.000           | 0.078           | 0.056            | 0.457             | 0.000          | 0.002              |
+| 570                                         | 0.000           | 0.064           | 0.028            | 0.442             | 0.000          | 0.002              |
+
+**Table A.1 – Spectral reflectance of test colours for medical imaging equipment**
+
+| Number                                      | 16              | 17              | 18               | 19                | 20             | 21                 |
+|---------------------------------------------|-----------------|-----------------|------------------|-------------------|----------------|--------------------|
+| Source                                      | Original (Blue) | Original (Cyan) | Original (Green) | Original (Yellow) | Original (Red) | Original (Magenta) |
+| HV/C                                        | –               | –               | –                | –                 | –              | –                  |
+| <b>Wavelength <math>\lambda</math> (nm)</b> |                 |                 |                  |                   |                |                    |
+|                                             |                 |                 |                  |                   |                |                    |
+| 575                                         | 0.000           | 0.053           | 0.013            | 0.413             | 0.000          | 0.002              |
+| 580                                         | 0.000           | 0.042           | 0.006            | 0.372             | 0.000          | 0.004              |
+| 585                                         | 0.000           | 0.032           | 0.004            | 0.329             | 0.000          | 0.007              |
+| 590                                         | 0.000           | 0.024           | 0.002            | 0.286             | 0.000          | 0.017              |
+| 595                                         | 0.000           | 0.018           | 0.002            | 0.243             | 0.000          | 0.043              |
+|                                             |                 |                 |                  |                   |                |                    |
+| 600                                         | 0.000           | 0.013           | 0.002            | 0.203             | 0.000          | 0.103              |
+| 605                                         | 0.000           | 0.011           | 0.001            | 0.166             | 0.007          | 0.205              |
+| 610                                         | 0.000           | 0.008           | 0.001            | 0.135             | 0.068          | 0.323              |
+| 615                                         | 0.000           | 0.006           | 0.001            | 0.109             | 0.237          | 0.425              |
+| 620                                         | 0.000           | 0.004           | 0.000            | 0.086             | 0.473          | 0.497              |
+|                                             |                 |                 |                  |                   |                |                    |
+| 625                                         | 0.000           | 0.003           | 0.000            | 0.068             | 0.673          | 0.539              |
+| 630                                         | 0.000           | 0.003           | 0.000            | 0.056             | 0.812          | 0.563              |
+| 635                                         | 0.000           | 0.001           | 0.000            | 0.045             | 0.893          | 0.566              |
+| 640                                         | 0.000           | 0.001           | 0.000            | 0.036             | 0.938          | 0.564              |
+| 645                                         | 0.000           | 0.000           | 0.000            | 0.030             | 0.964          | 0.553              |
+|                                             |                 |                 |                  |                   |                |                    |
+| 650                                         | 0.000           | 0.000           | 0.000            | 0.024             | 0.925          | 0.511              |
+| 655                                         | 0.000           | 0.000           | 0.000            | 0.016             | 0.753          | 0.403              |
+| 660                                         | 0.000           | 0.000           | 0.000            | 0.010             | 0.515          | 0.268              |
+| 665                                         | 0.000           | 0.000           | 0.000            | 0.006             | 0.333          | 0.170              |
+| 670                                         | 0.000           | 0.000           | 0.000            | 0.003             | 0.229          | 0.115              |
+|                                             |                 |                 |                  |                   |                |                    |
+| 675                                         | 0.000           | 0.000           | 0.000            | 0.002             | 0.158          | 0.078              |
+| 680                                         | 0.000           | 0.001           | 0.000            | 0.001             | 0.098          | 0.048              |
+| 685                                         | 0.000           | 0.000           | 0.001            | 0.001             | 0.055          | 0.027              |
+| 690                                         | 0.000           | 0.001           | 0.001            | 0.000             | 0.032          | 0.015              |
+| 695                                         | 0.000           | 0.001           | 0.000            | 0.000             | 0.022          | 0.010              |
+|                                             |                 |                 |                  |                   |                |                    |
+| 700                                         | 0.000           | 0.001           | 0.001            | 0.000             | 0.015          | 0.007              |
+| 705                                         | 0.000           | 0.001           | 0.001            | 0.000             | 0.012          | 0.006              |
+| 710                                         | 0.000           | 0.001           | 0.002            | 0.000             | 0.011          | 0.005              |
+| 715                                         | 0.000           | 0.003           | 0.002            | 0.000             | 0.010          | 0.005              |
+| 720                                         | 0.000           | 0.003           | 0.002            | 0.000             | 0.009          | 0.004              |
+|                                             |                 |                 |                  |                   |                |                    |
+| 725                                         | 0.001           | 0.003           | 0.002            | 0.000             | 0.006          | 0.003              |
+
+**Table A.1 – Spectral reflectance of test colours for medical imaging equipment**
+
+| <b>Number</b>                               | <b>16</b>              | <b>17</b>              | <b>18</b>               | <b>19</b>                | <b>20</b>             | <b>21</b>                 |
+|---------------------------------------------|------------------------|------------------------|-------------------------|--------------------------|-----------------------|---------------------------|
+| <b>Source</b>                               | <b>Original (Blue)</b> | <b>Original (Cyan)</b> | <b>Original (Green)</b> | <b>Original (Yellow)</b> | <b>Original (Red)</b> | <b>Original (Magenta)</b> |
+| <b>HV/C</b>                                 | –                      | –                      | –                       | –                        | –                     | –                         |
+| <b>Wavelength <math>\lambda</math> (nm)</b> |                        |                        |                         |                          |                       |                           |
+| 730                                         | 0.001                  | 0.003                  | 0.001                   | 0.000                    | 0.004                 | 0.002                     |
+| 735                                         | 0.000                  | 0.003                  | 0.000                   | 0.000                    | 0.002                 | 0.001                     |
+| 740                                         | 0.000                  | 0.003                  | 0.000                   | 0.000                    | 0.002                 | 0.001                     |
+| 745                                         | 0.000                  | 0.003                  | 0.000                   | 0.000                    | 0.002                 | 0.001                     |
+|                                             |                        |                        |                         |                          |                       |                           |
+| 750                                         | 0.000                  | 0.003                  | 0.000                   | 0.000                    | 0.002                 | 0.001                     |
+| 755                                         | 0.000                  | 0.003                  | 0.000                   | 0.000                    | 0.002                 | 0.001                     |
+| 760                                         | 0.001                  | 0.005                  | 0.001                   | 0.000                    | 0.002                 | 0.001                     |
+| 765                                         | 0.002                  | 0.005                  | 0.002                   | 0.000                    | 0.002                 | 0.001                     |
+| 770                                         | 0.001                  | 0.004                  | 0.001                   | 0.000                    | 0.002                 | 0.001                     |
+|                                             |                        |                        |                         |                          |                       |                           |
+| 775                                         | 0.000                  | 0.003                  | 0.000                   | 0.000                    | 0.001                 | 0.001                     |
+| 780                                         | 0.000                  | 0.003                  | 0.000                   | 0.000                    | 0.001                 | 0.001                     |
+
+## Annex B
+
+### Measurement methods for colour capturing accuracy of cameras for implementing fidelity colour reproduction (CCAC)
+
+(This annex forms an integral part of this Recommendation.)
+
+### B.1 Introduction
+
+This annex presents measurement methods and their requirements for obtaining colour measurement accuracy of cameras for implementing fidelity colour reproduction on endoscopic and open surgery and telemedicine systems using ultra-high definition imaging.
+
+### B.2 Measurement conditions
+
+#### B.2.1 Colour target for evaluation
+
+The annex introduces three types of colour targets, which are relatively easy to implement.
+
+##### B.2.1.1 PLES colour target
+
+Programmable light emission system (PLES) is a programmable self-emissive colour target. Figure B.1 shows the schematic diagram of the PLES. Various emission spectra can be realized by controlling the light intensity of 18-colour LEDs. The PLES has a wider colour reproduction range than the colour gamut of [ITU-R BT.2020].
+
+Required conditions and recommended conditions of the PLES hardware specifications to be used are described in Table B.1.
+
+![Schematic diagram of the Programmable Light Emission System (PLES). The diagram shows a circular integrating sphere with an output window on the left. Inside the sphere, a vertical array of 18 LEDs emits light of various colors (represented by colored arrows: red, orange, yellow, green, blue, violet). These light rays reflect off the interior surface of the sphere before exiting through the output window. A PC (laptop) is connected to the LED array via a control line to manage light intensity.](303fadfb9def251d1575d6221199b158_img.jpg)
+
+```
+
+    graph LR
+    PC[PC / Laptop] -- Control Line --> LEDs[18-colour LED Array]
+    subgraph Integrating_Sphere [Integrating Sphere]
+    LEDs -- Light Emission --> Interior[Reflective Interior Surface]
+    Interior -- Reflected Light --> Output[Output Window]
+    end
+  
+```
+
+Schematic diagram of the Programmable Light Emission System (PLES). The diagram shows a circular integrating sphere with an output window on the left. Inside the sphere, a vertical array of 18 LEDs emits light of various colors (represented by colored arrows: red, orange, yellow, green, blue, violet). These light rays reflect off the interior surface of the sphere before exiting through the output window. A PC (laptop) is connected to the LED array via a control line to manage light intensity.
+
+Figure B.1 – Schematic diagram of PLES
+
+**Table B.1 – Required conditions and recommended conditions of a PLES**
+
+| Specification                           | Required condition          | Recommended condition         |
+|-----------------------------------------|-----------------------------|-------------------------------|
+| Wavelength range                        | 380-730 nm                  | 360-830 nm                    |
+| Bit-depth resolution for A/D conversion | $\geq 10$ bits              | $\geq 12$ bits                |
+| Window size                             | $\geq 50$ mm $\phi$         | None (same as on the left)    |
+| (Maximum) Luminance                     | $\geq 40$ cd/m <sup>2</sup> | $\geq 80$ cd/m <sup>2</sup> * |
+| Uniformity                              | $\leq 2\%$                  | None (same as on the left)    |
+| Angular characteristics                 | $\leq 2\%$ (@ $\pm 5$ deg.) | None (same as on the left)    |
+
+**Table B.1 – Required conditions and recommended conditions of a PLES**
+
+| Specification                                                  | Required condition            | Recommended condition         |
+|----------------------------------------------------------------|-------------------------------|-------------------------------|
+| Short-term repeatability                                       |                               |                               |
+| Mean luminance level $Y_{S, mean}$ : xxx,xx cd/m <sup>2</sup>  |                               |                               |
+| ( $Y_S$ )                                                      | $\leq x.xx$ cd/m <sup>2</sup> | $\leq x.xx$ cd/m <sup>2</sup> |
+| ( $(Y_S)/Y_{S, mean}$ ( $Y_{cv}$ for short-term repeatability) | $\leq 0.015$                  | $\leq 0.0075$                 |
+| $u_S$                                                          | $\leq 0.0005$                 | $\leq 0.00025$                |
+| $v_S$                                                          | $\leq 0.0005$                 | $\leq 0.00025$                |
+| Long-term repeatability                                        |                               |                               |
+| Mean luminance level $Y_{L, mean}$ : xxx,xx cd/m <sup>2</sup>  |                               |                               |
+| ( $Y_L$ )                                                      | $\leq x.xx$ cd/m <sup>2</sup> | $\leq x.xx$ cd/m <sup>2</sup> |
+| ( $(Y_L)/Y_{L, mean}$ ( $Y_{cv}$ for long-term repeatability)  | $\leq 0.0375$                 | $\leq 0.01875$                |
+| $u_L$                                                          | $\leq 0.00125$                | $\leq 0.000625$               |
+| $v_L$                                                          | $\leq 0.00125$                | $\leq 0.000625$               |
+
+Here, uniformity means that of luminance measured at the output window. For circular-shaped output windows, luminance is measured at the centre and at 8 points as shown in Figure B.2, evenly spaced next to the circumference of the output window at 45-degree intervals. The luminance measurements are made normal to the plane of the output window at each measurement point.
+
+Uniformity is defined by the formula (B1):
+
+$$\Delta Y_u = \max_{i \in c, 0^\circ \sim 315^\circ} \left| \frac{Y_i - Y_{ave}}{Y_{ave}} \right| \times 100 \quad (B1)$$
+
+where,  $Y_{ave}$  is the average of the luminance measured on the output window.  $Y_i$  is the luminance measured either at the centre or at each location next to the circumference of the output window.
+
+![Diagram of a circular output window showing measurement points. The window is a circle with a central point and 8 points around the circumference. The points are labeled with angles: 0°, 45°, 90°, 135°, 180°, 225°, 270°, and 315°. The central point is also labeled 0°. The diagram is labeled 'Circular output window' and 'F.780.6(25)'. A legend indicates that a black dot represents 'Measurement points'.](62a4c9055642dbb00663e633332f04d3_img.jpg)
+
+Diagram of a circular output window showing measurement points. The window is a circle with a central point and 8 points around the circumference. The points are labeled with angles: 0°, 45°, 90°, 135°, 180°, 225°, 270°, and 315°. The central point is also labeled 0°. The diagram is labeled 'Circular output window' and 'F.780.6(25)'. A legend indicates that a black dot represents 'Measurement points'.
+
+**Figure B.2 – Luminance measurement points**
+
+Angular characteristics refer to how luminance of the output window changes when viewing it from different angles. The luminance is measured within a 10-degree cone angle to the normal line of the centre of the output window. Figure B.3 shows the angular characteristic measurement method.
+
+![Diagram illustrating the angular characteristics measurement method. A circular output window is shown at the base. Above it, a 10-degree cone is defined by two lines originating from the center. The normal axis is labeled Y_nor. Two other axes are shown, inclined at an angle theta to the normal axis, labeled Y_-theta and Y_+theta. The angle theta is indicated by a dashed arc and labeled -theta and +theta. The diagram is labeled F.780.6(25).](397d7c5f170e27a78f44fd8a5b0a234b_img.jpg)
+
+Diagram illustrating the angular characteristics measurement method. A circular output window is shown at the base. Above it, a 10-degree cone is defined by two lines originating from the center. The normal axis is labeled Y\_nor. Two other axes are shown, inclined at an angle theta to the normal axis, labeled Y\_-theta and Y\_+theta. The angle theta is indicated by a dashed arc and labeled -theta and +theta. The diagram is labeled F.780.6(25).
+
+**Figure B.3 – Angular characteristics measurement method**
+
+Angular characteristics is defined by the formula (B2),
+
+$$\Delta Y_\theta = \max_{i \in +\theta, -\theta} \left| \frac{Y_i - Y_{nor}}{Y_{nor}} \right| \quad (B2)$$
+
+where  $Y_{nor}$  is luminance measured along the axis normal to the output window,  $Y_{+\theta}$  or  $Y_{-\theta}$  is luminance measured along the axis which is inclined  $+\theta$  or  $-\theta$  to the normal axis, respectively. Maximum  $\theta$  is  $5^\circ$  of arc.
+
+Regarding short-term and long-term repeatability, refer to [ISO/TS 17321-4] for details.
+
+##### B.2.1.2 Wide gamut transmission type colour target
+
+In the following, a wide gamut transmission type colour target is introduced.
+
+This colour target is composed of a colour chart having colour patches designed to have specified chromaticity, and a light viewer that emits white light. Figure B.4 shows an example of the wide gamut colour chart. Figure B.5 shows one of the use cases of the colour target.
+
+The colour patches shall have chromaticity as close as possible to the three primary colours defined in [ITU-R BT.2020]. They also should have intermediate colours of the three primary colours. That is, red, green, and blue are required colours, and yellow, magenta, and cyan are recommended colours. The chromaticity of white can be changed to D50, D65, etc. by selecting the light source of the viewer. The test colours in Annex A other than the above six colours can also be included in the colour patches.
+
+![Image of a wide gamut transmission type colour chart. It features a 3x3 grid of color patches on a black background. The colors are: top row (red, cyan, white), middle row (yellow, blue, gray), and bottom row (green, magenta, dark gray). The diagram is labeled F.780.6(25).](c74ee8a60918baf4b06f002a72f86111_img.jpg)
+
+Image of a wide gamut transmission type colour chart. It features a 3x3 grid of color patches on a black background. The colors are: top row (red, cyan, white), middle row (yellow, blue, gray), and bottom row (green, magenta, dark gray). The diagram is labeled F.780.6(25).
+
+**Figure B.4 – Example of wide gamut transmission type colour chart**
+
+![Diagram illustrating the use case of a wide gamut transmission type colour target. A 'Light viewer' on the left contains a 'Colour chart' with a 3x3 grid of color patches (red, cyan, white; yellow, blue, grey; green, magenta, black). An arrow points to a 'Camera' on the right, which is shown capturing the color chart. The label F.780.6(25) is present below the camera.](cce1f4715971176232d2f8cf7b80acf7_img.jpg)
+
+Diagram illustrating the use case of a wide gamut transmission type colour target. A 'Light viewer' on the left contains a 'Colour chart' with a 3x3 grid of color patches (red, cyan, white; yellow, blue, grey; green, magenta, black). An arrow points to a 'Camera' on the right, which is shown capturing the color chart. The label F.780.6(25) is present below the camera.
+
+**Figure B.5 – Use case of the wide gamut transmission type colour target**
+
+##### B.2.1.3 Reflective type colour target
+
+In the following, a reflective type colour target is introduced.
+
+This colour target is composed of a colour chart having colour patches designed to have specified chromaticity, and an illumination that emits white light. Figure B.6 shows an example of the colour chart. Figure B.7 shows one of the use cases of the colour target.
+
+The colour patches should have chromaticity as close as possible to the three primary colours defined in [ITU-R BT.2020]. They also should have intermediate colours of three primary colours. That is, red, green, and blue are required colours, and yellow, magenta, and cyan are recommended colours. The chromaticity of white can be changed to D50, D65, etc. by selecting the light source of the illumination. The test colours in Annex A other than the above six colours can also be included in the colour patches.
+
+NOTE – Since it is difficult to reproduce [ITU-R BT.2020] colour gamut with a reflective type, a compromise has been made to have the widest possible colour gamut.
+
+![Diagram showing an example of a reflective type colour chart. It consists of a 3x3 grid of color patches: red, green, blue; black, grey, white; yellow, magenta, cyan. The label F.780.6(25) is present below the chart.](e3c1d325b828c44049a7ac37e5b34603_img.jpg)
+
+Diagram showing an example of a reflective type colour chart. It consists of a 3x3 grid of color patches: red, green, blue; black, grey, white; yellow, magenta, cyan. The label F.780.6(25) is present below the chart.
+
+**Figure B.6 – Example of the reflective type colour chart**
+
+![Diagram illustrating the use case of a reflective type colour target. A light source (represented by a sun-like icon) illuminates a colour chart (a 3x3 grid of colored patches: red, green, blue, black, grey, white, yellow, purple, cyan). The colour chart is then captured by a camera (represented by a box with a lens). The diagram is labeled F.780.6(25).](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg)
+
+Diagram illustrating the use case of a reflective type colour target. A light source (represented by a sun-like icon) illuminates a colour chart (a 3x3 grid of colored patches: red, green, blue, black, grey, white, yellow, purple, cyan). The colour chart is then captured by a camera (represented by a box with a lens). The diagram is labeled F.780.6(25).
+
+**Figure B.7 – Use case of the reflective type colour target**
+
+#### **B.2.2 Environment of capturing images**
+
+Capturing images is required to be taken in accordance with [ISO 12646] or in the darkroom with following conditions ("temperature" condition was referred from [ISO 12646]).
+
+- Temperature: 18 C° to 28 C°.
+- Temperature fluctuation:  $\pm 3$  C°.
+- Relative humidity: 15% to 80%.
+
+### **B.3 Measurement methods**
+
+#### **B.3.1 General**
+
+Measurement is required to be carried out in the following steps.
+
+Step 1: Select colour patch set(s) and illuminant suitable for the colour target used.
+
+Step 2: Capture RGB images of the selected colour patch set to obtain XYZ values.
+
+Step 3: Measure XYZ values of the selected colour patch set by using a spectral radiance meter. Or is recommended to obtain XYZ values from the PLES when PLES is used as the colour target.
+
+Step 4: Calculate the colour measurement accuracy from the above two sets of XYZ values.
+
+#### **B.3.2 Selection of colour targets and illuminant**
+
+##### **B.3.2.1 General**
+
+Selection of colour patch set and illuminant is required to take the use of a camera to be measured into account. For example, if such a camera is supposed to be used as a colour sensor for applications with highly saturated colours, a colour patch set including saturated colours is recommended to be selected.
+
+A gamut formed by target colours is required to be included in a gamut formed by colour patches under a specified illuminant.
+
+Chromaticity coordinates of all colour patches are required to be reported as a chromaticity diagram or table.
+
+They are required to be either  $a^*b^*$  values or  $xy$  values. The details of the light source will depend on clause 7.1. Selected type of illuminant for the colour patch set is required to be reported.
+
+When making a self-emissive colour target, it is recommended to noted that different spectral power distributions (SPDs) can generate an identical colour very occasionally due to metamerism. Also, it is recommended to noted that light emission with a peaky spectrum sometimes brings an unexpected large measurement error when a camera with steep spectral sensitivity is under test.
+
+##### **B.3.2.2 For surgery and endoscopic surgery applications**
+
+The colour targets are recommended to use PLES, which covers the colour gamut specified by [ITU-R BT.2020], as a colour chart for measurement in surgical and endoscopic surgery. A standard light source that conforms to the operating room lighting is required to be selected.
+
+##### **B.3.2.3 For telemedicine applications**
+
+Telemedicine requires faithful colour reproduction in a variety of environments, such as patients' home and remote clinics. In order to accurately measure the object colour, it is necessary to investigate the characteristics of the illumination light in the environment.
+
+##### **B.3.2.4 For application to other medical fields**
+
+The colour targets and illuminant in other medical applications, such as transfusion blood infection testing, are required to select specific colour charts and illuminant for each application.
+
+#### **B.3.3 RGB image capture of the colour target**
+
+##### **B.3.3.1 Attentions on the measurement/capturing conditions**
+
+- a) Any digital or analogue treatment that influences on linearity of the camera is required to be disabled.
+- b) Gamma settings are recommended to be unity.
+- c) All camera settings and treatment are required to be recorded.
+
+##### **B.3.3.2 Capturing of RGB images of the colour targets**
+
+The following method shows how to capture RGB images with a camera to be measured.
+
+Step 1: Camera to be measured is required to be placed so that it faces the output window of the light-emitting colour target, transmission type colour target, or reflective type colour target.
+
+Step 2: Allow both the camera and the light-emitting colour target, light viewer, or light source to have enough warm-up.
+
+Step 3: Set the exposure time and F-number of the lens so that the raw image output level falls between 50% and 90% of saturation level of the camera.
+
+NOTE – F-number of the lens is recommended to be large enough within the range of usage conditions so as not to worsen the colour measurement accuracy of the camera.
+
+Step 4: Adjust the image size of the colour patch to  $4 \pm 1\%$  of full image size. 20% of horizontal image size and 20% of vertical image size respectively.
+
+Step 5: Adjust the location of the colour patch image to the centre of the viewing area.
+
+Step 6: Display a colour at the output window of the light-emitting colour target, transmission type colour target, or reflective type colour target, and capture its RGB image with the camera.
+
+Step 7: Store the above image data to a memory.
+
+Step 8: Repeat the above procedure for all colour patches.
+
+Capturing of RGB images is recommended to be repeated to show repeatability of colour capturing accuracy. The number of capturing instances and its timing is recommended to be entrusted to a measurement body. When repeated capturing spans more than two days, power on/off of the camera under test is required to be executed on each capturing day.
+
+##### **B.3.3.3 Measurement of tristimulus XYZ values**
+
+If a light-emitting colour target outputs tristimulus XYZ values corresponding to the colour patch set used for the measurement, these values are required to be used as reference XYZ data.
+
+Otherwise, after placing a spectrophotometer at the position where the camera was located, measure tristimulus XYZ values for each colour of the colour target set. This spectrometer is required to be well calibrated.
+
+Measurement of tristimulus XYZ values is recommended to be repeated to show repeatability corresponding to the capturing of RGB images.
+
+#### B.3.4 Calculation of colour capturing accuracy and its repeatability
+
+The following steps show how to calculate the colour measurement accuracy of a camera from the image data obtained by the previously mentioned methods. Colourimetric capturing in surgical and endoscopic surgery with high saturation colour are required to perform conversion to XYZ for the [ITU-R BT.2020] (UHD) colour gamut using equation.
+
+In the following, image data are treated as they are provided by cameras in the UHD colour space and free from gamma correction. Other colour spaces might be considered. Figure B.8 shows the pre-processing to obtain L\*a\*b\* data from the image data.
+
+Step 1: Calculate average values of RGB image data,  $R_{UHD}$ ,  $G_{UHD}$  and  $B_{UHD}$  for each colour patch.
+
+Step 2: Convert  $R_{UHD}$ ,  $G_{UHD}$  and  $B_{UHD}$  values to CIE X, Y and Z values using following matrix B3.
+
+$$\begin{bmatrix} X \\ Y \\ Z \end{bmatrix} = \begin{bmatrix} 0.6370 & 0.1446 & 0.1689 \\ 0.2627 & 0.6780 & 0.0593 \\ 0.0000 & 0.0281 & 1.0610 \end{bmatrix} \begin{bmatrix} R_{UHD} \\ G_{UHD} \\ B_{UHD} \end{bmatrix} \quad (B3)$$
+
+Step 3: Convert both XYZ values generated by the camera and the colour target to L\*a\*b\* values using formulas (B4) defined by the CIE and shown in below:
+
+$$\begin{aligned} L^* &= 116f\left(\frac{Y}{Y_n}\right) - 16 \\ a^* &= 500 \left\{ f\left(\frac{X}{X_n}\right) - f\left(\frac{Y}{Y_n}\right) \right\} \\ b^* &= 200 \left\{ f\left(\frac{Y}{Y_n}\right) - f\left(\frac{Z}{Z_n}\right) \right\} \end{aligned} \quad (B4)$$
+
+where  $X_n$ ,  $Y_n$  and  $Z_n$  are tristimulus values for perfect reflecting diffuser.
+
+Function f has following expression and is also similar for  $f\left(\frac{Y}{Y_n}\right)$  and  $f\left(\frac{Z}{Z_n}\right)$ .
+
+$$f\left(\frac{X}{X_n}\right) = \left(\frac{X}{X_n}\right)^{\frac{1}{3}} \text{ If } \frac{X}{X_n} > 0.08856 \quad (B5)$$
+
+$$f\left(\frac{X}{X_n}\right) = 7.787 \left(\frac{X}{X_n}\right)^{\frac{1}{3}} + \frac{16}{116} \text{ If } \frac{X}{X_n} \leq 0.08856$$
+
+Step 4: Normalize all tristimulus values by setting  $Y_n$  is equal to 100. Then calculate the colour difference  $\Delta E_{ab}$  between L\*a\*b\* obtained by the camera and that of reference values for each colour patch according to the formula (B6).
+
+$$\Delta E_{ab} = \sqrt{(L_2^* - L_1^*)^2 + (a_2^* - a_1^*)^2 + (b_2^* - b_1^*)^2} \quad (B6)$$
+
+Step 5: Calculate mean value  $\Delta E_{ab,mean}^*$  and standard deviation  $\sigma(\Delta E_{ab,mean}^*)$  of  $\Delta E_{ab}^*$  for all colour patches.
+
+Step 6: Report  $\Delta E_{ab,mean}^*$  and  $\sigma(\Delta E_{ab,mean}^*)$ .
+
+Step 7: To obtain repeatability of colour capturing accuracy, calculate mean value  $\Delta E_{ab,mean}^{*rep}$  and standard deviation  $\sigma(\Delta E_{ab,mean}^{*rep})$  of  $\Delta E_{ab,mean}^{*i}$  for repeated measurements. Suffix  $i$  describes i-th measurement.
+
+Step 8: Report  $\Delta E_{ab,mean}^{*rep}$  and  $\sigma(\Delta E_{ab,mean}^{*rep})$ .
+
+![Flowchart showing the calculation of L*a*b* tables from camera RGB data and reference XYZ data. The top path uses a 3x3 matrix transformation on a PC, while the bottom path uses XYZ output from a spectrophotometer or PLES. Both lead to CIE formula calculations for L*, a*, b* values.](d9843ac5dfc4bbe9e4d21b8898723b5e_img.jpg)
+
+The flowchart illustrates the process of obtaining  $L^*a^*b^*$  tables. It starts with a color target (a circle with a color bar and a 24-color patch). Two arrows lead from this target to two different camera setups. The top setup shows a camera connected to a PC. The camera outputs  $\begin{bmatrix} R_{UHD} \\ G_{UHD} \\ B_{UHD} \end{bmatrix}$ , which undergoes an  $RGB_{UHD}$  to  $XYZ$  transformation using a 3x3 matrix on the PC to produce  $\begin{bmatrix} X \\ Y \\ Z \end{bmatrix}$ . This is then transformed to  $L^*a^*b^*$  using CIE formulas to produce the Camera's  $L^*a^*b^*$  table. The bottom setup shows a camera connected to a spectrophotometer or a PLES, which outputs  $\begin{bmatrix} X_{ref} \\ Y_{ref} \\ Z_{ref} \end{bmatrix}$ . This is transformed to  $L^*a^*b^*$  using CIE formulas to produce the Reference  $L^*a^*b^*$  table.
+
+**Camera's  $L^*a^*b^*$  table**
+
+|                  | $L^*$ | $a^*$ | $b^*$ |
+|------------------|-------|-------|-------|
+| White disc       | 98.3  | -1.3  | 1.1   |
+| Colour patch1    | 25.7  | 50.1  | 33.0  |
+| Colour patch2    | 15.8  | 33.8  | 17.4  |
+| ...              | ...   | ...   | ...   |
+| Colour patch $J$ | 12.4  | 5.4   | -16.2 |
+| ...              | ...   | ...   | ...   |
+| Colour patch24   | 3.6   | 5.0   | -6.6  |
+
+**Reference  $L^*a^*b^*$  table**
+
+|                  | $L^*$ | $a^*$ | $b^*$ |
+|------------------|-------|-------|-------|
+| White disc       | 100.0 | 0.0   | 0.0   |
+| Colour patch1    | 26.7  | 51.0  | 32.7  |
+| Colour patch2    | 16.2  | 33.0  | 16.5  |
+| ...              | ...   | ...   | ...   |
+| Colour patch $J$ | 11.8  | 5.9   | -15.4 |
+| ...              | ...   | ...   | ...   |
+| Colour patch24   | 3.9   | 4.8   | -6.8  |
+
+F.780.6(25)
+
+Flowchart showing the calculation of L\*a\*b\* tables from camera RGB data and reference XYZ data. The top path uses a 3x3 matrix transformation on a PC, while the bottom path uses XYZ output from a spectrophotometer or PLES. Both lead to CIE formula calculations for L\*, a\*, b\* values.
+
+Figure B.8 – Calculation flow to obtain  $L^*a^*b^*$  tables
+
+## Annex C
+
+### Measurement method of colour reproducibility of electronic displays
+
+(This annex forms an integral part of this Recommendation.)
+
+### C.1 Introduction
+
+This annex presents measurement methods of colour reproducibility of electronic displays. The role of electronic displays in a high-fidelity colour imaging system is to faithfully reproduce colour information (signals) similar to the real colour, and the evaluation method is to measure the actual characteristics in the viewing environment in which the display is used. This annex provides evaluation methods for stationary medical electronic displays that display images captured by cameras.
+
+### C.2 Measurement conditions
+
+Required measurement conditions of colour reproducibility of electronic displays is described in [ISO 9241-305] with Table C.1.
+
+**Table C.1 – Required measurement conditions**
+
+|                                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                |
+|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|
+| Environment of optical measurements | Temperature                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | 18 C° to 28 C° |
+|                                     | Temperature fluctuation                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | ±3 C°          |
+|                                     | Relative humidity                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | 15% to 80%     |
+| Display warm-up                     | ≥ 20 min.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                |
+| Measurement field                   | ≥ 500 pixels or area of a box that is 10% of the height and 10% of the width of the display                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                |
+| Meter angular aperture              | ≤ 2 deg.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                |
+| Measurement location                | <p>Nine points equally spread across the diagonal from the upper left corner of the display</p> <img alt="Diagram showing the measurement locations on a display. A rectangle represents the display area with width W_view and height H_view. A dashed horizontal line at H_view/2 and a dashed vertical line at W_view/2 divide the display into four quadrants. Nine measurement points are marked with numbers: 11, 15, 19 in the top row; 22, 33, 44, 55, 66, 77, 88 in the middle row; and 91, 95, 99 in the bottom row. The points are distributed along the main diagonal from the top-left to the bottom-right. The top-left corner is point 11, the center is point 55, and the bottom-right corner is point 99. The top-right corner is point 19. The bottom-left corner is point 91. The middle row points are 22, 33, 44, 55, 66, 77, 88. The top row points are 11, 15, 19. The bottom row points are 91, 95, 99. The diagram is labeled F.780.6(25)." data-bbox="798 1276 1420 1713" src="ee84ba98f797de76074797ce486078de_img.jpg"/> |                |
+
+### C.3 Measurement method
+
+#### C.3.1 General
+
+The colour-related optical characteristics of an electronic display depend on its colour gamut characteristics, brightness contrast characteristics, and brightness characteristics. Therefore, the signal indicating the intended chromaticity varies from device to device.
+
+Evaluation of colour reproducibility is measured using the signal that outputs the reference colour for each device. Since stationary monitors used in bright environments are affected by illumination light, measurements are performed by illuminating the display with diffused light source.
+
+#### C.3.2 Measurements
+
+##### C.3.2.1 Measurements of the luminance and chromaticity in the normal viewing direction
+
+The measurement of the luminance and chromaticity for the 81 measurement-locations shown in Table C.1 for each colour is required to measure in the arrangement shown in Figure C.1. As with measurements taken in the normal viewing direction shown in clause 7.5, place the diffused light source at 30 degrees from the normal direction of the display to create the lighting environment shown in clause 7. Place the light measuring device at 0 degrees or 15 degrees on the opposite side from the normal direction of the display. Measure the luminance and chromaticity of the equipment under test (display), as well as the standard diffuser plate.
+
+![Diagram of measurement configuration showing a display (1, 2), a diffused light source (3) at 30 degrees, and a light measuring device (4) at 15 degrees.](483c43eac5aa582dfcb6e0aa8cee163f_img.jpg)
+
+The diagram shows a side view of the measurement setup. A vertical line represents the display and standard diffuser plate (labeled 1, 2). Above it, a large grey circle represents the diffused light source (3). An angle of 30° is indicated between the normal of the display and the center of the light source. A smaller angle of 15° is shown for the tilt of the display surface. To the right, a rectangular box represents the light measuring device (4), positioned at a 15° angle relative to the normal of the display. The label 'F.780.6(25)' is in the bottom right.
+
+Diagram of measurement configuration showing a display (1, 2), a diffused light source (3) at 30 degrees, and a light measuring device (4) at 15 degrees.
+
+**Figure C.1 – Measurement configuration**
+
+###### Key
+
+- 1 Display
+- 2 Standard diffuser plate
+- 3 Diffused light source
+- 4 Light measuring device
+
+##### C.3.2.2 Measurement of the viewing angle characteristics
+
+Measurements for the viewing angle range within  $\pm 50$  arc degrees horizontally and  $\pm 33.7$  arc degrees vertically specified in clause 7.6.2 are taken at measurement point "55" of the measurement location in Table C.1 as centre of screen under the arrangement shown in Figure C.2. Place the diffused light source at 30 degrees from the normal direction of the display to create the lighting environment shown in clause 7. Measure the luminance and chromaticity of the display, as well as the standard diffuser plate.
+
+![Figure C.2 – Measurement configuration of the viewing angle characteristics. The diagram shows three views: Top view, Side view, and Front view (Plan view). In the Top view, a display (1, 2) is shown with a light measuring device (4) at an angle +θ_H and -θ_H. In the Side view, a display (1, 2) is shown with a light measuring device (4) at an angle +θ_V and -θ_V. In the Front view (Plan view), a display (1, 2) is shown. The text F.780.6(25) is at the bottom right.](f9c64800d9bace9b4315646d1057be3c_img.jpg)
+
+Figure C.2 – Measurement configuration of the viewing angle characteristics. The diagram shows three views: Top view, Side view, and Front view (Plan view). In the Top view, a display (1, 2) is shown with a light measuring device (4) at an angle +θ\_H and -θ\_H. In the Side view, a display (1, 2) is shown with a light measuring device (4) at an angle +θ\_V and -θ\_V. In the Front view (Plan view), a display (1, 2) is shown. The text F.780.6(25) is at the bottom right.
+
+**Figure C.2 – Measurement configuration of the viewing angle characteristics**
+
+###### **Key**
+
+- 1 Display
+- 2 Standard diffuser plate
+- 4 Light measuring device
+- $\theta_H$  The angle of the horizontal azimuth relative to the normal direction
+- $\theta_V$  The angle of the vertical azimuth relative to the normal direction
+
+#### **C.3.3 Repeatability**
+
+To verify the repeatability of the meter, it is recommended to be perform continuous measurements at least 7 times (short-term repeatability) and at least 7 measurements after turning the power off and on (long-term repeatability) to verify the measurement accuracy. The required and recommended standard deviation are described as following Table C.2.
+
+**Table C.2 – Required and recommended repeatability**
+
+| Short-term repeatability                                      | Required standard dev.        | Recommended standard dev.     |
+|---------------------------------------------------------------|-------------------------------|-------------------------------|
+| Mean luminance level $Y_{S, mean}$ : xxx,xx cd/m <sup>2</sup> |                               |                               |
+| ( $Y_S$ )                                                     | $\leq x.xx$ cd/m <sup>2</sup> | $\leq x.xx$ cd/m <sup>2</sup> |
+| $(Y_S)/Y_{S, mean}$ ( $Y_{cv}$ for short-term repeatability)  | $\leq 0.015$                  | $\leq 0.0075$                 |
+| $u_{s'}$                                                      | $\leq 0.0005$                 | $\leq 0.00025$                |
+| $v_{s'}$                                                      | $\leq 0.0005$                 | $\leq 0.00025$                |
+| Long-term repeatability                                       |                               |                               |
+| Mean luminance level $Y_{L, mean}$ : xxx,xx cd/m <sup>2</sup> |                               |                               |
+| ( $Y_L$ )                                                     | $\leq x.xx$ cd/m <sup>2</sup> | $\leq x.xx$ cd/m <sup>2</sup> |
+| $(Y_L)/Y_{L, mean}$ ( $Y_{cv}$ for long-term repeatability)   | $\leq 0.0375$                 | $\leq 0.01875$                |
+| $u_{L'}$                                                      | $\leq 0.00125$                | $\leq 0.000625$               |
+| $v_{L'}$                                                      | $\leq 0.00125$                | $\leq 0.000625$               |
+
+#### C.3.4 Analysis
+
+For each colour, calculate the colour difference  $\Delta E^*_{ab}$ .
+
+## Annex D
+
+### On the use of [ITU-R BT.709]
+
+(This annex forms an integral part of this Recommendation.)
+
+This annex specifies the modifications for the application of this Recommendation to equipment and systems of [ITU-R BT.709] or 2K systems.
+
+### D.1 The system colourimetry and OETF for [ITU-R BT.709]
+
+On the application of this Recommendation to equipment and systems of [ITU-R BT.709], the system colourimetry of [ITU-R BT.709] shown in Items 1.3 and 1.4 of Table D.1 should be used instead of the system colourimetry of [ITU-R BT.2020] shown in Table 1 in clause 7.4.1.
+
+Non-linear opto-electronic transfer function (OETF) of [ITU-R BT.709] shown in Item 1.2 of Table D.1 is the same as the function for 10-bit systems of [ITU-R BT.2020] shown in Table 2 in clause 7.4.1, and 12-bit coding is not recommended in [ITU-R BT.709]. Therefore, the 10-bit OETF is also applied to equipment and systems of [ITU-R BT.709].
+
+**Table D.1 – Opto-electronic conversion of [ITU-R BT.709]**
+
+| Item | Parameter                                                                 | System Values                                                                                                                                                                                       |        |
+|------|---------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|
+| 1.1  | Opto-electronic transfer characteristics before non-linear pre-correction | Assumed linear                                                                                                                                                                                      |        |
+| 1.2  | Overall opto-electronic transfer characteristics at source                | $V = 1.099 L^{0.45} - 0.099$ for $1 \geq L \geq 0.018$<br>$V = 4.500 L$ for $0.018 > L \geq 0$<br>where:<br>$L$ : luminance of the image $0 \leq L \leq 1$<br>$V$ : corresponding electrical signal |        |
+| 1.3  | Chromaticity coordinates (CIE, 1931)                                      | $x$                                                                                                                                                                                                 | $y$    |
+|      | Primary                                                                   |                                                                                                                                                                                                     |        |
+|      | – Red ( $R$ )                                                             | 0.640                                                                                                                                                                                               | 0.330  |
+|      | – Green ( $G$ )                                                           | 0.300                                                                                                                                                                                               | 0.600  |
+|      | – Blue ( $B$ )                                                            | 0.150                                                                                                                                                                                               | 0.060  |
+| 1.4  | Assumed chromaticity for equal primary signals (Reference white)          | $D_{65}$                                                                                                                                                                                            |        |
+|      |                                                                           | $x$                                                                                                                                                                                                 | $y$    |
+|      | $E_R = E_G = E_B$                                                         | 0.3127                                                                                                                                                                                              | 0.3290 |
+
+### D.2 Use of test colours within the [ITU-R BT.709] colour gamut
+
+When applying this Recommendation to equipment and systems of [ITU-R BT.709], test colours out of gamut of [ITU-R BT.709], specifically TC12 and TC16 to TC21 in Annex A, should not be used (see Figure I.2 for reference).
+
+## Appendix I
+
+### Examples of Lab and signal values for test colours
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This appendix gives examples of Lab values for the test colours listed in Annex A and the reference display input signal values described in clause 7.6.2.
+
+The illuminant used to calculate these values is the CIE illuminant D with a CCT of 4 500 K, or D4500. Since no real illuminator of illuminant D exists, it cannot be used in real medical shooting. However, it serves as a virtual illuminant for measuring colour reproducibility of medical video equipment. D4500 meets the requirements for medical illumination described in clause 7.1.
+
+### I.1 Spectral distribution of D4500
+
+The spectral distribution of D4500 is calculated according to CIE procedure. The results are shown in Table I.1, Table I.2 and Figure I.1.
+
+**Table I.1 – Chromaticity of D4500**
+
+| CCT   | $x_D$   | $y_D$   |
+|-------|---------|---------|
+| 4 500 | 0.36209 | 0.37087 |
+
+**Table I.2 – Relative spectral distribution of D4500**
+
+| Wavelength (nm) | D4500 | Wavelength (nm) | D4500  | Wavelength (nm) | D4500  |
+|-----------------|-------|-----------------|--------|-----------------|--------|
+| 380             | 17.79 | 515             | 93.00  | 650             | 105.16 |
+| 385             | 20.07 | 520             | 93.88  | 655             | 107.20 |
+| 390             | 22.35 | 525             | 96.77  | 660             | 109.23 |
+| 395             | 29.95 | 530             | 99.65  | 665             | 112.44 |
+| 400             | 37.55 | 535             | 99.45  | 670             | 115.66 |
+| 405             | 41.07 | 540             | 99.25  | 675             | 113.86 |
+| 410             | 44.60 | 545             | 100.41 | 680             | 112.07 |
+| 415             | 46.56 | 550             | 101.57 | 685             | 105.10 |
+| 420             | 48.53 | 555             | 100.78 | 690             | 98.14  |
+| 425             | 48.02 | 560             | 100.00 | 695             | 101.02 |
+| 430             | 47.52 | 565             | 99.16  | 700             | 103.90 |
+| 435             | 55.42 | 570             | 98.32  | 705             | 103.98 |
+| 440             | 63.31 | 575             | 99.29  | 710             | 104.05 |
+| 445             | 69.48 | 580             | 100.25 | 715             | 95.05  |
+| 450             | 75.65 | 585             | 98.29  | 720             | 86.04  |
+| 455             | 77.79 | 590             | 96.33  | 725             | 91.28  |
+
+**Table I.2 – Relative spectral distribution of D4500**
+
+| Wavelength (nm) | D4500 | Wavelength (nm) | D4500  | Wavelength (nm) | D4500  |
+|-----------------|-------|-----------------|--------|-----------------|--------|
+| 460             | 79.93 | 595             | 99.23  | 730             | 96.51  |
+| 465             | 80.98 | 600             | 102.12 | 735             | 99.81  |
+| 470             | 82.03 | 605             | 103.51 | 740             | 103.10 |
+| 475             | 84.35 | 610             | 104.90 | 745             | 95.07  |
+| 480             | 86.66 | 615             | 105.24 | 750             | 87.04  |
+| 485             | 85.98 | 620             | 105.58 | 755             | 75.77  |
+| 490             | 85.31 | 625             | 104.22 | 760             | 64.50  |
+| 495             | 87.81 | 630             | 102.86 | 765             | 78.57  |
+| 500             | 90.31 | 635             | 105.35 | 770             | 92.64  |
+| 505             | 91.22 | 640             | 107.84 | 775             | 89.93  |
+| 510             | 92.13 | 645             | 106.50 | 780             | 87.23  |
+
+![Line graph showing the relative spectral distribution of D65, D50, and D4500 illuminants. The x-axis is Wavelength (nm) from 350 to 780. The y-axis is Relative Spectral Distribution from 0 to 150. The D65 curve (blue) peaks at ~115 at 450 nm. The D50 curve (orange) peaks at ~100 at 550 nm. The D4500 curve (red) peaks at ~115 at 675 nm.](16c69c0dacd3c57ae91acd114e5f5bd2_img.jpg)
+
+The graph displays three spectral curves: D65 (blue), D50 (orange), and D4500 (red). The x-axis represents Wavelength in nanometers (nm), ranging from 350 to 780. The y-axis represents the Relative Spectral Distribution, ranging from 0 to 150. The D65 curve shows a sharp rise from 380 nm, peaking at approximately 115 at 450 nm, and then gradually declining to about 65 at 780 nm. The D50 curve starts at a lower value, rises to a peak of about 100 at 550 nm, and then declines to about 75 at 780 nm. The D4500 curve starts at the lowest value, rises to a peak of about 115 at 675 nm, and then declines to about 85 at 780 nm. The D4500 curve is notably higher than the others in the 600-700 nm range.
+
+Line graph showing the relative spectral distribution of D65, D50, and D4500 illuminants. The x-axis is Wavelength (nm) from 350 to 780. The y-axis is Relative Spectral Distribution from 0 to 150. The D65 curve (blue) peaks at ~115 at 450 nm. The D50 curve (orange) peaks at ~100 at 550 nm. The D4500 curve (red) peaks at ~115 at 675 nm.
+
+**Figure I.1 – Relative spectral distribution of D4500**
+
+### I.2 Lab values of the test colours with the illuminant D4500
+
+Examples of the spectral distribution of the scene light, as indicated in Figure 7-1, are obtained by multiplying the spectral distribution of D4500 in Table I.2 by the spectral reflectance of the test colours in Annex A. Chromaticity and Lab values of the resultant scene light are calculated as shown in Table I.3. The Lab values are normalized to a perfect reflecting diffuser. For reference, the chromaticity diagram and general appearance of the test colours are shown in Figure I.2 and Table I.4.
+
+The scene light with the resultant spectral distribution can be emitted by a self-emissive colour target such as the PLES in Annex B.
+
+By capturing the emitted light by a camera and comparing Lab values calculated from the linear output of the camera with the Lab in Table I.3, colour reproducibility of the camera is evaluated following the procedure described in clause 7.3.2.
+
+Overall, colour characteristics of a system are also measured using the emitted light. By capturing the emitted light by the camera of the system and comparing Lab values of displayed light on the display of the system with the Lab values in Table I.3, the colour reproducibility of the system is evaluated following the procedure described in clause 7.7.
+
+**Table I.3 – Chromaticity and Lab values of the test colours with the illuminant D4500**
+
+| Test colour | <i>x</i> | <i>y</i> | <i>L*</i> | <i>a*</i> | <i>b*</i> |
+|-------------|----------|----------|-----------|-----------|-----------|
+| TC01        | 0.4311   | 0.3729   | 62.30     | 19.52     | 13.49     |
+| TC02        | 0.4294   | 0.4253   | 61.21     | 3.72      | 29.31     |
+| TC03        | 0.4065   | 0.4849   | 62.16     | −16.72    | 43.48     |
+| TC04        | 0.3244   | 0.4472   | 60.54     | −31.13    | 14.29     |
+| TC05        | 0.2999   | 0.3684   | 61.60     | −19.71    | −10.32    |
+| TC06        | 0.2859   | 0.3076   | 60.63     | −5.42     | −29.62    |
+| TC07        | 0.3426   | 0.3024   | 61.16     | 16.85     | −23.50    |
+| TC08        | 0.3904   | 0.3175   | 63.44     | 27.33     | −11.62    |
+| TC09        | 0.6100   | 0.3207   | 42.78     | 63.04     | 33.52     |
+| TC10        | 0.4679   | 0.4671   | 82.26     | 3.60      | 71.45     |
+| TC11        | 0.2869   | 0.4621   | 51.27     | −40.63    | 10.43     |
+| TC12        | 0.1664   | 0.1940   | 28.56     | −8.13     | −50.72    |
+| TC13        | 0.4239   | 0.3917   | 81.03     | 14.55     | 22.14     |
+| TC14        | 0.3908   | 0.4643   | 40.79     | −11.82    | 23.84     |
+| TC15        | 0.4327   | 0.3804   | 64.66     | 18.12     | 16.65     |
+| TC16        | 0.1362   | 0.0523   | 8.86      | 41.41     | −76.36    |
+| TC17        | 0.1588   | 0.3865   | 45.02     | −65.92    | −18.69    |
+| TC18        | 0.1923   | 0.7486   | 44.35     | −93.45    | 54.28     |
+| TC19        | 0.4579   | 0.5319   | 53.47     | −12.33    | 83.27     |
+| TC20        | 0.7086   | 0.2909   | 32.59     | 74.61     | 55.90     |
+| TC21        | 0.4530   | 0.1910   | 34.66     | 75.16     | −32.57    |
+
+![Chromaticity diagram showing the color space (X, Y) with various test colors (TC01-TC21) and illuminants (D65, BT.709, BT.2020, D4500). The spectral locus is shown as a solid black line. The diagram includes a legend on the right side listing the spectral locus, D65, BT.709, BT.2020, D4500, and test colors TC01 through TC21 with their corresponding symbols and colors. The axes are labeled X and Y, with values ranging from 0 to 0.8 on the Y-axis and 0 to 0.7 on the X-axis. A small label 'F.780.6(25)' is present in the bottom right corner of the plot area.](32f80b2d70752613b6577797811f3a95_img.jpg)
+
+Chromaticity diagram showing the color space (X, Y) with various test colors (TC01-TC21) and illuminants (D65, BT.709, BT.2020, D4500). The spectral locus is shown as a solid black line. The diagram includes a legend on the right side listing the spectral locus, D65, BT.709, BT.2020, D4500, and test colors TC01 through TC21 with their corresponding symbols and colors. The axes are labeled X and Y, with values ranging from 0 to 0.8 on the Y-axis and 0 to 0.7 on the X-axis. A small label 'F.780.6(25)' is present in the bottom right corner of the plot area.
+
+Figure I.2 – Chromaticity of the test colours with the illuminant D4500
+
+Table I.4 – Appearance of the test colours
+
+| TC   | HV/C      | Appearance under daylight |
+|------|-----------|---------------------------|
+| TC01 | 7.5R 6/4  | Light greyish red         |
+| TC02 | 5Y 6/4    | Dark greyish yellow       |
+| TC03 | 5GY 6/8   | Strong yellow green       |
+| TC04 | 2.5G 6/6  | Moderate yellowish green  |
+| TC05 | 10BG 6/4  | Light bluish green        |
+| TC06 | 5PB 6/8   | Light blue                |
+| TC07 | 2.5P 6/8  | Light violet              |
+| TC08 | 10P 6/8   | Light reddish purple      |
+| TC09 | 4.5R 4/13 | Strong red                |
+| TC10 | 5Y 8/10   | Strong yellow             |
+| TC11 | 4.5G 5/8  | Strong green              |
+| TC12 | 3PB 3/11  | Strong blue               |
+
+**Table I.4 – Appearance of the test colours**
+
+| TC   | HV/C    | Appearance under daylight   |
+|------|---------|-----------------------------|
+| TC13 | 5YR 8/4 | Light yellowish pink        |
+| TC14 | 5GY 4/4 | Moderate olive green (leaf) |
+| TC15 | 1YR 6/4 | Light brownish pink         |
+| TC16 | –       | Very strong blue            |
+| TC17 | –       | Very strong cyan            |
+| TC18 | –       | Very strong green           |
+| TC19 | –       | Very strong yellow          |
+| TC20 | –       | Very strong red             |
+| TC21 | –       | Very strong magenta         |
+
+### I.3 Reference display input signal with the illuminant D4500
+
+Linear RGB values of ideal [ITU-R BT.2020] camera output are calculated by applying the [ITU-R BT.2020] colour-matching functions derived from the system colourimetry shown in Table 1 in clause 7.4.1, to the scene light described above, and normalizing them to the range 0 to 1 using perfect reflecting diffuser. Camera output signal values R'G'B' for display and transmission are calculated according to Table 2 in clause 7.4.1. The resultant values are shown in Table I.5, along with their digital representation DR'DG'DB'. The R'G'B' or DR'DG'DB' are examples of values of the reference display input signal described in clause 7.6.2.
+
+By inputting the reference signal to a display and comparing Lab values of displayed light of the display with the Lab in Table I.3, colour reproducibility of the display is evaluated following the procedure described in clause 7.6.2.
+
+**Table I.5 – Reference display input signal values of the test colours with the illuminant D4500**
+
+| Test colour | Linear RGB |        |        | R'G'B' |        |        | 10-bit digital R'G'B' <sup>(1)</sup> |     |     |
+|-------------|------------|--------|--------|--------|--------|--------|--------------------------------------|-----|-----|
+|             | R          | G      | B      | R'     | G'     | B'     | DR'                                  | DG' | DB' |
+| TC01        | 0.4041     | 0.2689 | 0.2225 | 0.6319 | 0.5094 | 0.4597 | 617                                  | 510 | 466 |
+| TC02        | 0.3345     | 0.2864 | 0.1341 | 0.5723 | 0.5270 | 0.3457 | 565                                  | 525 | 366 |
+| TC03        | 0.2759     | 0.3323 | 0.0857 | 0.5165 | 0.5703 | 0.2645 | 516                                  | 563 | 295 |
+| TC04        | 0.1918     | 0.3355 | 0.1985 | 0.4236 | 0.5732 | 0.4317 | 435                                  | 566 | 442 |
+| TC05        | 0.2140     | 0.3335 | 0.3758 | 0.4500 | 0.5714 | 0.6084 | 458                                  | 564 | 596 |
+| TC06        | 0.2292     | 0.3004 | 0.5380 | 0.4672 | 0.5406 | 0.7324 | 473                                  | 537 | 705 |
+| TC07        | 0.3339     | 0.2651 | 0.4879 | 0.5717 | 0.5055 | 0.6966 | 564                                  | 506 | 674 |
+| TC08        | 0.4294     | 0.2667 | 0.4157 | 0.6522 | 0.5072 | 0.6412 | 635                                  | 508 | 625 |
+| TC09        | 0.3263     | 0.0469 | 0.0387 | 0.5648 | 0.1780 | 0.1550 | 558                                  | 219 | 199 |
+| TC10        | 0.7094     | 0.5916 | 0.0987 | 0.8426 | 0.7687 | 0.2884 | 802                                  | 737 | 316 |
+| TC11        | 0.0981     | 0.2419 | 0.1433 | 0.2875 | 0.4811 | 0.3593 | 315                                  | 485 | 378 |
+| TC12        | 0.0140     | 0.0637 | 0.2672 | 0.0631 | 0.2190 | 0.5077 | 119                                  | 255 | 508 |
+
+**Table I.5 – Reference display input signal values of the test colours  
+with the illuminant D4500**
+
+| Test colour | Linear RGB |         |         | R'G'B' |         |         | 10-bit digital R'G'B' <sup>(1)</sup> |     |     |
+|-------------|------------|---------|---------|--------|---------|---------|--------------------------------------|-----|-----|
+|             | R          | G       | B       | R'     | G'      | B'      | DR'                                  | DG' | DB' |
+| TC13        | 0.7109     | 0.5407  | 0.3760  | 0.8435 | 0.7343  | 0.6085  | 802                                  | 707 | 597 |
+| TC14        | 0.1041     | 0.1273  | 0.0478  | 0.2979 | 0.3356  | 0.1804  | 324                                  | 357 | 222 |
+| TC15        | 0.4349     | 0.2980  | 0.2266  | 0.6564 | 0.5383  | 0.4643  | 639                                  | 535 | 470 |
+| TC16        | 0.0016     | 0.0013  | 0.2202  | 0.0071 | 0.0057  | 0.4571  | 70                                   | 69  | 464 |
+| TC17        | 0.0066     | 0.2028  | 0.2391  | 0.0297 | 0.4369  | 0.4781  | 90                                   | 446 | 482 |
+| TC18        | 0.0081     | 0.2085  | 0.0078  | 0.0364 | 0.4436  | 0.0349  | 95                                   | 452 | 94  |
+| TC19        | 0.2108     | 0.2293  | -0.0031 | 0.4463 | 0.4673  | -0.0141 | 454                                  | 473 | 51  |
+| TC20        | 0.2471     | -0.0006 | 0.0002  | 0.4867 | -0.0026 | 0.0009  | 490                                  | 61  | 64  |
+| TC21        | 0.2374     | 0.0055  | 0.2238  | 0.4762 | 0.0248  | 0.4612  | 481                                  | 85  | 468 |
+
+<sup>(1)</sup> DE'=INT[(219×E'+16) ×4] (E'=R', G', or B')
+
+# Bibliography
+
+- [b-ITU-R BT.1886] Recommendation ITU-R BT.1886 (2018), *Reference electro-optical transfer function for flat panel displays used in HDTV studio production.*
+- [b-DICOM] A. Salazar, *et al.* (2014), *DICOM gray-scale standard display function: clinical diagnostic accuracy of chest radiography in medical-grade gray-scale and consumer-grade colour displays*, June 2014, Vol. 202, No.6. *American Journal of Roentgenology*.
+- [b-ISO 3664] ISO 3664 (2009), *Graphic technology and photography – Viewing conditions.*
+- [b-ISO 12052] ISO 12052 (2017), *Health informatics – Digital imaging and communication in medicine (DICOM) including workflow and data management.*
+- [b-ISO/CIE 11664-2] ISO/CIE 11664-2 (2022), *Colorimetry – Part 2: CIE standard illuminants.*
+
+
+
+## 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                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| 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/F/T-REC-F.790-200701-I_PDF-E/raw.md b/marked/F/T-REC-F.790-200701-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..fbfbc961d0c28bca710bd0578164a1154d7ba7fb
--- /dev/null
+++ b/marked/F/T-REC-F.790-200701-I_PDF-E/raw.md
@@ -0,0 +1,701 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.790**
+
+(01/2007)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Audiovisual services
+
+---
+
+**Telecommunications accessibility guidelines for  
+older persons and persons with disabilities**
+
+ITU-T Recommendation F.790
+
+ITU-T
+
+![ITU logo: A globe with a red lightning bolt, next to the text 'International Telecommunication Union'.](1d7527f4316cfe2d342b08d1653d1592_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, and the text "International Telecommunication Union" to its right.
+
+ITU logo: A globe with a red lightning bolt, next to the text 'International Telecommunication Union'.
+
+# ITU-T F-SERIES RECOMMENDATIONS NON-TELEPHONE TELECOMMUNICATION SERVICES
+
+### **TELEGRAPH SERVICE**
+
+|                                                                 |             |
+|-----------------------------------------------------------------|-------------|
+| Operating methods for the international public telegram service | F.1-F.19    |
+| The gentex network                                              | F.20-F.29   |
+| Message switching                                               | F.30-F.39   |
+| The international telemessage service                           | F.40-F.58   |
+| The international telex service                                 | F.59-F.89   |
+| Statistics and publications on international telegraph services | F.90-F.99   |
+| Scheduled and leased communication services                     | F.100-F.104 |
+| Phototelegraph service                                          | F.105-F.109 |
+
+## **MOBILE SERVICE**
+
+|                                                        |             |
+|--------------------------------------------------------|-------------|
+| Mobile services and multdestination satellite services | F.110-F.159 |
+|--------------------------------------------------------|-------------|
+
+## **TELEMATIC SERVICES**
+
+|                                           |             |
+|-------------------------------------------|-------------|
+| Public facsimile service                  | F.160-F.199 |
+| Teletex service                           | F.200-F.299 |
+| Videotex service                          | F.300-F.349 |
+| General provisions for telematic services | F.350-F.399 |
+
+## **MESSAGE HANDLING SERVICES**
+
+F.400-F.499
+
+### **DIRECTORY SERVICES**
+
+F.500-F.549
+
+### **DOCUMENT COMMUNICATION**
+
+|                                      |             |
+|--------------------------------------|-------------|
+| Document communication               | F.550-F.579 |
+| Programming communication interfaces | F.580-F.599 |
+
+### **DATA TRANSMISSION SERVICES**
+
+F.600-F.699
+
+### **AUDIOVISUAL SERVICES**
+
+**F.700-F.799**
+
+## **ISDN SERVICES**
+
+F.800-F.849
+
+## **UNIVERSAL PERSONAL TELECOMMUNICATION**
+
+F.850-F.899
+
+### **HUMAN FACTORS**
+
+F.900-F.999
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# **ITU-T Recommendation F.790**
+
+# **Telecommunications accessibility guidelines for older persons and persons with disabilities**
+
+## **Summary**
+
+This Recommendation is intended to provide general guidelines for standardizing, planning, developing, designing and distributing all forms of telecommunications equipment and software and associated telecommunications services to ensure their accessibility for people with the widest possible range of abilities. It gives guidance on understanding the topic of accessibility and the ways that accessibility may be incorporated in products and services.
+
+###### **Source**
+
+ITU-T Recommendation F.790 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                                             | 2    |
+| 4    | Abbreviations.....                                                                            | 2    |
+| 5    | Conventions .....                                                                             | 2    |
+| 6    | General principles.....                                                                       | 3    |
+| 7    | Requirements for planning, development and design.....                                        | 3    |
+| 7.1  | Basic policies .....                                                                          | 3    |
+| 7.2  | Activities concerning development process .....                                               | 4    |
+| 8    | Common requirements for operation and usage of telecommunications equipment and services..... | 5    |
+| 8.1  | Operation .....                                                                               | 5    |
+| 8.2  | Installation, connection and configuration .....                                              | 6    |
+| 8.3  | Physical safety .....                                                                         | 6    |
+| 8.4  | Information security .....                                                                    | 7    |
+| 8.5  | Rights of content usage .....                                                                 | 7    |
+| 9    | Requirements for terminal equipment .....                                                     | 7    |
+| 9.1  | Input/Output interface .....                                                                  | 7    |
+| 9.2  | Body shapes and structures .....                                                              | 9    |
+| 9.3  | External connection ports .....                                                               | 9    |
+| 9.4  | Terminology, icons and graphic symbols.....                                                   | 10   |
+| 9.5  | Alternatives.....                                                                             | 10   |
+| 9.6  | Standardization and disclosure of interface specifications.....                               | 10   |
+| 10   | Requirements for telecommunications services .....                                            | 10   |
+| 10.1 | Interactive telecommunications services .....                                                 | 10   |
+| 10.2 | Telecommunications platform services .....                                                    | 11   |
+| 10.3 | Emergency calls.....                                                                          | 11   |
+| 10.4 | Telecommunications services specifications.....                                               | 11   |
+| 11   | Requirements for user support.....                                                            | 11   |
+| 11.1 | User manuals .....                                                                            | 11   |
+| 11.2 | Disclosure of information about telecommunications accessibility .....                        | 12   |
+| 11.3 | Instruction.....                                                                              | 12   |
+| 11.4 | Customer support centres .....                                                                | 12   |
+|      | Appendix I – Further details of informative references.....                                   | 13   |
+|      | Bibliography .....                                                                            | 15   |
+
+# **Introduction**
+
+Information and communications technology (ICT), in particular the rapid proliferation of the Internet, has provided substantial benefits to the community; but many older persons and persons with disabilities cannot enjoy these benefits due to barriers in using telecommunications products and services. This issue is becoming more serious with the increasing percentage of aging persons worldwide. In response, some nations have developed their own guidelines for telecommunications accessibility. In today's world, however, telecommunications equipment moves freely across national borders. Thus, in order to enhance telecommunications accessibility, telecommunications accessibility guidelines are indispensable not only domestically but also internationally.
+
+# **Telecommunications accessibility guidelines for older persons and persons with disabilities**
+
+# **1 Scope**
+
+This Recommendation is intended to provide general guidelines for standardizing, planning, developing, designing and distributing all forms of telecommunications equipment and software and associated telecommunications services (hereinafter referred to collectively as "telecommunications equipment and services") to ensure their accessibility for people with the widest possible range of abilities including older persons and persons with permanent or temporary disabilities (hereinafter referred to as "older persons and persons with disabilities").
+
+For many years, ITU-T has addressed the needs of persons with disabilities in the development of specific Recommendations. Making telecommunications equipment and services accessible makes sense not only in terms of humanitarian aspects but also in terms of economic aspects. The most obvious reason is the increase in potential customers. Features that make products and services usable for older persons and persons with disabilities can often make them convenient and easy to use for everyone else.
+
+This Recommendation is intended to be part of the overall framework that ITU-T can use in its efforts to support the need for older persons and persons with disabilities to provide more accessible equipment and services. This Recommendation provides information by identifying problem areas which need to be considered when drafting such Recommendations addressing the needs of older persons and persons with disabilities. In the process of developing those Recommendations, it is necessary to actively involve a broad range of users such as older persons and persons with disabilities and clearly understand user and task requirements. Especially, addressing needs earlier rather than later in the development process is preferable in order to reduce or eliminate extra cost for developing those Recommendations.
+
+Also it is to be noted that an accessible design approach may not resolve everything. Where accessible design cannot fully respond to the needs of older persons and persons with disabilities, in particular in the field of services, the need for personal assistance may still be required. However, the provision of personal assistance should never be relied upon to replace the accessible design approach.
+
+Of necessity, guidance provided in this Recommendation is general. It is recognized that additional specific guides need to be developed for specific equipment or service. Though the scope of this Recommendation is given for a development of Recommendations specific to meet the needs of older persons and persons with disabilities, the guidelines described in this Recommendation are expected to be a good reference for producing any other Recommendations in ITU-T to improve telecommunication accessibility.
+
+# **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 Guide 71] ISO/IEC Guide 71:2001, *Guidelines for standards developers to address the needs of older persons and persons with disabilities*.
+
+[ISO 13407] ISO 13407:1999, *Human-centred design processes for interactive systems*.
+
+# 3 Definitions
+
+This Recommendation defines the following terms:
+
+**3.1 user:** End-users of telecommunications products and services are people, groups of people and organizations that use or consume telecommunications products and services. They are a diverse group, including people, whatever the age or gender, level of income, geographic environment or work activities. End-users, whether they be organizations or people, have varied requirements.
+
+*See Resolution GSC 11-22 (UWG) on User needs, considerations and involvement.*
+
+**3.2 disability:** In this Recommendation, "disability" is defined as a state when use of telecommunications equipment and services is restricted.
+
+Mainly, "disability" is viewed as a result of temporary or permanent functional limitation due to disease, accident, ageing and so on. More generally, "disability" includes a state when full use of telecommunications equipment and services is not possible due to the physical and/or social environment (e.g., voice telephony under noisy environment).
+
+NOTE – For more detailed information about the definition of "disability", please refer to appropriate documents such as WHO ICF (World Health Organization – International Classification of Functioning, Disability and Health).
+
+**3.3 telecommunications equipment:** Any machine, device, line or other form of equipment used to perform telecommunications operations.
+
+**3.4 telecommunications services:** Services provided to users via the use of telecommunications equipment.
+
+**3.5 interactive telecommunications services:** Services designed to enable the two-way exchange of information between multiple users in multiple locations via telecommunications equipment such as exchanges and network servers. (Examples: voice telephony, facsimile, video phone, e-mail and instant messaging services.)
+
+**3.6 telecommunications platform services:** Services designed to support telecommunications equipment and user management, user authentication, content management, charging and payment procedures by operators engaged in the provision of information services via telecommunications equipment.
+
+**3.7 telecommunications accessibility:** For the telecommunications area, the usability of a product, service, environment or facility by the widest possible range of users and especially users with disabilities.
+
+**3.8 assistive technology:** Piece of equipment, product system, hardware, software or service that is used to enable, maintain or improve functional capabilities of individuals with disabilities.
+
+# 4 Abbreviations
+
+None.
+
+# 5 Conventions
+
+None.
+
+# **6 General principles**
+
+In order to ensure and improve telecommunications accessibility, developers of telecommunications equipment and services shall comply with the following general principles.
+
+- a) When planning, developing, designing, and distributing telecommunications equipment and services, developers should consider older persons and persons with disabilities to ensure that they can use such equipment and services as much as possible. This concept is known as "inclusive design". There will be cases where inclusive design is not practical and, in those cases, the aim should be to provide a service with absolute or near functional equivalence to the original service.
+- b) If the required degree of accessibility cannot be provided in the standard configuration of telecommunications equipment or services, such accessibility may be attained by using the product in combination with optional equipment or assistive technology from other manufacturers. Again, the aim should be to provide a service with absolute or near functional equivalence to the original service.
+- c) The functions related to telecommunications accessibility should ensure the safety of users.
+- d) The functions related to telecommunications accessibility should maintain the information security of users.
+- e) Telecommunications equipment and services should be as operable and usable as possible without imposing excessive load on cognitive and memory capabilities. Telecommunications equipment and services should also be as operable and usable as possible even if there are differences in culture or language or if users operate and use them for the first time.
+
+# **7 Requirements for planning, development and design**
+
+In order to ensure and improve telecommunications accessibility, developers of telecommunications equipment and services shall comply with the requirements provided in this Recommendation as well as plan, develop and design all telecommunications equipment and services.
+
+Also, management shall consider the importance of planning, development and design of accessible telecommunications equipment and services, and set specific policies on telecommunications accessibility.
+
+New designs of equipment should use existing international standards wherever possible and be designed to be compatible with existing equipment. Consideration should be given to making the equipment compatible with foreseeable future standards.
+
+## **7.1 Basic policies**
+
+In order to ensure and improve telecommunications accessibility, developers should understand the concept of human-centred design. The incorporation of a human-centred approach for telecommunications accessibility is characterized by the following:
+
+- a) the active involvement of a broad range of users such as older persons and persons with disabilities and a clear understanding of user and task requirements;
+- b) an appropriate allocation of functions between users and technology to make an interface friendly to older persons and persons with disabilities;
+- c) the iteration of design solutions and evaluations;
+- d) multi-disciplinary design.
+
+## 7.2 Activities concerning development process
+
+Until designs meet requirements, developers should iterate the development process, which includes the following four human-centred design activities (see Figure 1):
+
+- Understanding and specification of the context of use.
+- Specification of the user and organizational requirements.
+- Production of design solutions.
+- Evaluation of designs against requirements.
+
+![Flowchart of human-centred design activities for telecommunications accessibility based on ISO 13407.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+```
+graph TD; A([Identify need for human-centred design]) --> B[Understand and specify the context of use]; B --> C[Specify the user and organizational requirements]; C --> D[Produce design solutions]; D --> E[Evaluate designs against requirements]; E --> F([System satisfies specified user and organizational requirements]); E --> B; E --> C;
+```
+
+The diagram illustrates the iterative human-centred design process. It begins with an oval labeled 'Identify need for human-centred design', which points to a rectangular box 'Understand and specify the context of use'. This box points to another rectangular box 'Specify the user and organizational requirements', which in turn points to 'Produce design solutions'. This box points to 'Evaluate designs against requirements', which finally points to a central oval 'System satisfies specified user and organizational requirements'. From this central oval, two curved arrows point back to the 'Understand and specify the context of use' and 'Specify the user and organizational requirements' boxes, indicating an iterative cycle. A small label 'F.790(01-07)\_F01' is located at the bottom right of the diagram.
+
+Flowchart of human-centred design activities for telecommunications accessibility based on ISO 13407.
+
+**Figure 1 – Human-centred design activities for telecommunications accessibility (based on ISO 13407)**
+
+### 7.2.1 Understanding and specification of the context of use
+
+The following activities are performed to understand and specify the context of use:
+
+- Understanding of physical and cognitive functions of the intended users.
+- Understanding of knowledge, experience, and requirements of the intended users concerning use of telecommunications equipment.
+- Understanding of environments around the intended users when they use telecommunications equipment because the environments often have an impact on older persons and persons with disabilities.
+
+### 7.2.2 Specification of the user and organizational requirements
+
+The following activities are performed to specify the user and organizational requirements:
+
+- Identification of the range of users who are older persons and persons with disabilities.
+- Identification of requirements suitable for the intended users.
+- Determination of the priority of the intended user requirements.
+- Understanding of requirements of relevant laws, standards, etc.
+
+### **7.2.3 Production of design solutions**
+
+The following activities are performed to produce design solutions:
+
+- Use of existing knowledge of ergonomics, cognitive engineering, this Recommendation, etc.
+- Development of solution prototype by using simulations, models, mock-ups, etc.
+- Comprehensive study covering older persons and persons with disabilities besides other studies that mainly cover younger generations.
+
+### **7.2.4 Evaluation of designs against requirements**
+
+The following activities are performed to evaluate designs against requirements:
+
+- Involvement of the intended users in the prototype evaluation.
+- Return to appropriate activities based on the evaluation results and iteration of the development process until designs meet the intended user requirements.
+
+# **8 Common requirements for operation and usage of telecommunications equipment and services**
+
+This clause indicates what users such as older persons and persons with disabilities need to be able to do when they use telecommunications equipment and services that are designed with accessibility and usability in mind.
+
+## **8.1 Operation**
+
+### **8.1.1 Operation of functions**
+
+The aim is that functions shall be operable without any difficulties from beginning to end.
+
+### **8.1.2 Simplicity of operation procedures**
+
+Telecommunications equipment and services should avoid unnecessarily high cognitive demands on users by ensuring that the basic activities required to operate the equipment or use the service are as straightforward and simple as possible.
+
+### **8.1.3 Confirmation**
+
+The following shall be confirmable via multiple senses (visually, aurally and by touch):
+
+- Whether the device is in the ready mode.
+- Whether the line is in a usable condition.
+- The outcome of an operation.
+- Whether an input operation was intended or completed.
+- Whether the device is about to become unusable and, if possible, why.
+
+### **8.1.4 Time restrictions**
+
+If a task requires users to make responses within a limited time, the users should be able to adjust the time if possible. Users should in any event be able to receive a notice of time restrictions.
+
+### **8.1.5 Error prevention**
+
+Developers shall consider how to ensure that users do not make operation mistakes.
+
+### **8.1.6 Error cancellation**
+
+Users shall be able to cancel erroneous operations and revert to the previous setting or status as far as possible.
+
+### **8.1.7 Revert to initial status**
+
+Users shall be able to revert to the initial status during any given procedure.
+
+### **8.1.8 Error reset**
+
+Devices shall be designed so that they may be reset to a known state. This state should have a high probability of operation in, at least, a basic mode. The method of activating this reset should be simple to use but protected from accidental operation.
+
+### **8.1.9 Output adjustment**
+
+Older persons and persons with disabilities shall be able to adjust the level and nature of outputs such as sound, vibration and screen flashing. In addition, the device should display status of the level and nature of the outputs.
+
+### **8.1.10 Error messages**
+
+Error messages and the consequential action to be taken should be clear and unambiguous.
+
+## **8.2 Installation, connection and configuration**
+
+- a) Packages should be designed so that they are easy to open and easy to unpack without damaging the contents.
+- b) Setup procedures for products should be simple for users to perform unaided.
+- c) A product should be of simple structure and it should be made simple to plug power strips and any connectors and wire them so that users have an opportunity to do so unaided. Connectors should be easily distinguished to avoid incorrect insertion.
+- d) Plugged connectors shall remain secure once connected but easy to remove.
+- e) A product shall be designed to resist movement and remain in position during operation.
+- f) The installation of batteries and other auxiliary equipment such as a tray shall be easy and simple.
+- g) The procedures to store information such as time, names, and phone numbers to a product should be simple so that users have a possibility to do them unaided if required.
+- h) It should be easy to replace consumables such as batteries, inks, and roll paper, so that users have an opportunity to do so unaided.
+
+## **8.3 Physical safety**
+
+### **8.3.1 Safety**
+
+Products shall be designed so as not to cause bodily harm or adversely affect the health of users during operation.
+
+### **8.3.2 Electromagnetic noise**
+
+EMI (electromagnetic interference) levels generated by telecommunications equipment, such as radio waves and electromagnetic noise, shall be within internationally agreed limits. The International Commission on Non-Ionizing Radiation Protection (ICNIRP) publishes guidelines on electromagnetic field levels.
+
+Hearing aids have widely different levels of immunity to electromagnetic fields. Telecommunications equipment should be designed to minimize interference to hearing aids while maintaining intended functionality.
+
+### **8.3.3 Photosensitive epilepsy**
+
+Any flashing of lights or screen elements shall be carefully designed to avoid potential problems such as photosensitive epilepsy.
+
+### **8.3.4 Allergies**
+
+The use of materials that are likely to cause allergic reactions should be avoided if such materials are used for equipment that comes into contact with the skin of users. In any event, information on the materials used shall be disclosed. See section 9.5 of [ISO/IEC Guide 71].
+
+### **8.3.5 Acoustic shock**
+
+Acoustic signal levels should not be so loud as to cause danger or discomfort to users of the equipment. See [b-ITU-T P.360]. Note, however, that hard-of-hearing people may require very high audio levels.
+
+## **8.4 Information security**
+
+### **8.4.1 Privacy protection**
+
+Secure yet accessible operation procedures shall be provided for the protection of information of a private or confidential nature. Third parties who obtain confidential information during these procedures must keep that information confidential.
+
+### **8.4.2 Alternative method of user identification**
+
+When biometrics technology is used to identify the user or permit user operations, the device shall also offer the option of an alternative means of identification that is not dependent on the physical characteristics of the user.
+
+## **8.5 Rights of content usage**
+
+Data protected for copyright or other reasons should be converted to other media if laws allow older persons or persons with disabilities to use such data.
+
+# **9 Requirements for terminal equipment**
+
+This clause contains the requirements for terminal equipment, mainly concerning visual or aural characteristics of terminal equipment such as parts layout, shapes of buttons, and alert tones.
+
+## **9.1 Input/Output interface**
+
+### **9.1.1 Layout of operation panel**
+
+- a) Design the display and key layout on the basis of user thought processes and operational procedures.
+- b) Avoid excessive line length on the display and overly detailed information.
+- c) Avoid crowded display and key layout configurations.
+- d) Align the direction of operation of switches with the direction of movement of the device itself.
+- e) Arrange operation keys in functional groups by shape, position, colour or other attributes that can be readily identified by persons with visual or tactile sensory impairment.
+
+### **9.1.2 Operation keys, buttons and switches**
+
+- a) Operation keys, buttons and switches shall be designed for both visual and tactile recognition.
+- b) Operation keys, buttons and switches shall be designed in an appropriate size and shape for easy operation.
+- c) Operation keys, buttons and switches shall be easily recognizable both visually and tactilely when there are a lot of buttons and keys of similar shape or function.
+- d) When they are depressed, operation keys, buttons and switches shall provide not only a tactile response but also a visual and aural response.
+- e) Both visual and auditory confirmation of key input shall be provided.
+- f) The device should be equipped with a double input suppression feature.
+- g) The key repeat delay should be fully adjustable.
+- h) The placement, size and shape of keys and buttons should be designed to prevent accidental pressing of adjacent keys.
+- i) For users who need a lot of time to operate devices, another input method with fewer keystrokes should be provided.
+- j) Operation keys, buttons and switches shall be manipulated by using an aid such as an artificial limb or mouse stick as far as possible.
+- k) Touch panel software keys and buttons shall be user-friendly with involuntary movement of hands or hand-shaking and operated without direct visual confirmation as far as possible.
+
+### **9.1.3 Displays**
+
+- a) Text shall be as easy to read as possible.
+- b) Display content shall be colour-independent.
+- c) Surface reflection shall not create any difficulty in seeing the screen as far as possible.
+- d) Brightness and contrast shall be adjustable as far as possible.
+- e) The size, typeface, character-spacing, line-spacing and colour of text should be made adjustable for ease of use.
+- f) Visual information should be understandable in other sensory ways.
+- g) Standard position (or starting position) should be verifiable both visually and aurally.
+
+### **9.1.4 Ringing tones**
+
+- a) The volume and frequency of ringing tones shall be designed to make the tone easy to hear depending on the hearing characteristics of users as far as possible.
+- b) The sound level shall be adjustable and be able to be muted. In addition, the current status of the level shall be able to be confirmed visually.
+- c) It should be possible to choose tones, patterns and melodies for ringing tones.
+- d) Information provided by ringing tones shall be available not only in an aural way but also in other sensory ways.
+
+### **9.1.5 Alert tones and voice guidance system**
+
+- a) The volume and frequency of alert tones shall be designed to make the tone easy to hear depending on the hearing characteristics of users as far as possible.
+- b) The voice guidance system shall use plain and clearly-enunciated language, and employ logical procedures based on the thought processes of users.
+
+- c) The sound level shall be adjustable and be able to be muted. In addition, the current status of the level shall be able to be confirmed visually.
+- d) Basic frequency and sound acoustics should be adjustable.
+- e) The speaking rate of voice guidance should be adjustable.
+- f) Information provided by voice guidance system should be able to be repeated if necessary.
+- g) Information provided by alert tones shall be available not only in an aural way but also in other sensory ways.
+- h) Information provided by voice guidance shall also be available in visual form.
+
+### **9.1.6 Voice input/output system**
+
+- a) Receiver sound shall be as easy to hear as possible depending on the hearing characteristics of users.
+- b) The volume of receiver sound shall be adjustable, during a call if possible.
+- c) The volume of receiver sound shall return to normal levels at the end of a call if a device is expected to be used by several people.
+- d) If receiver sound can be amplified, sound leakage should be avoided.
+- e) Parameters concerning receiver sound should be adjustable depending on the hearing characteristics of users.
+- f) An appropriate side-tone (the sound of the speaker's own voice in the earpiece) shall be provided.
+- g) Devices shall be as compatible with hearing aids equipped with induction pick-up coils as possible.
+- h) Devices shall be as compatible with external input of hearing aids and cochlear implants as possible.
+- i) Devices shall not cause noise in assistive technology such as hearing aids and cochlear implant as far as possible.
+- j) Telephone calls shall be available without holding a receiver.
+
+## **9.2 Body shapes and structures**
+
+- a) A receiver or a whole device (if the device must be held during operation) shall have appropriate shape and structure, be made from appropriate materials and be evenly-weighted in order for them to be held easily.
+- b) Stationary devices should have appropriate shape and structure, be made from appropriate materials, be evenly-weighted in order to accommodate various sitting positions.
+- c) Devices shall be operable with either hand.
+- d) The position and aspects of the operation panel shall be easy to understand both visually and tactilely.
+- e) Procedure of opening/closing moving parts shall be easy and users should be able to confirm the status of moving parts (open or close) both visually and tactilely.
+- f) Moving parts shall be able to be moved without excess force but not moved too easily.
+
+## **9.3 External connection ports**
+
+- a) External connection ports shall be located at convenient location.
+- b) When several external connection ports exist, each of them shall be easy to distinguish from one another.
+
+- c) External connection ports shall be designed (with respect to their position and form) to enable correct insertion and prevent accidental removal.
+
+## 9.4 Terminology, icons and graphic symbols
+
+### 9.4.1 Commonly used terms and notations
+
+Professional terms, foreign words, and abbreviations shall not be used so often. Instead, commonly-used terms and easily-understandable notations shall be used.
+
+### 9.4.2 Printed information and engraved marks
+
+- a) Information including texts and symbols shall be easy to read at normal viewing distance under normal light conditions. Not only viewing distance and light conditions but also the choice of font, whether with or without serif, in upright form or *italics* and light, medium or **bold** appearance has a significant impact on legibility. It is to be noted that text written in CAPITAL letters is more difficult to read. This is significant for those with a visual impairment. Consideration should be given to specifying size and style of font and symbols for warnings.
+- b) Information content shall be colour-independent.
+- c) The display shall be close to the relevant keys and buttons.
+- d) Printed information and engraved marks shall be of appropriate length, easily understandable and durable.
+
+### 9.4.3 Icons and graphic symbols
+
+Icons and graphic symbols shall be easy to understand and consistent.
+
+## 9.5 Alternatives
+
+- a) The product shall be as compatible with assistive technology for older persons and persons with disabilities as possible.
+- b) Even when users use assistive technology, any functions of the main body (including operation buttons, keys and power switches) should be available.
+
+## 9.6 Standardization and disclosure of interface specifications
+
+- a) Specifications of the input-output interface for external connection to peripheral devices such as assistive technology should be open to the public as far as possible.
+- b) The input-output interface for external connection is based on interface specifications used extensively among manufacturers, except where the aim is to promote the use of interface specifications for the connection of external input-output devices.
+
+# 10 Requirements for telecommunications services
+
+This clause contains the requirements for telecommunications services such as mediated interactive telecommunications services and telecommunications platform services.
+
+## 10.1 Interactive telecommunications services
+
+### 10.1.1 Real-time transmission
+
+If technically feasible, real-time text, image and video functionality should satisfy the following requirements:
+
+- simultaneous two-way transfer of data (full duplex);
+- no delay or minimal delay with no effect on communication;
+
+- no information loss, or minimal information loss with no effect on communication.
+
+### **10.1.2 Multimedia**
+
+Two-way communication services involving combinations of different media (such as text, voice and video) should be supported.
+
+### **10.1.3 Compatibility**
+
+Real-time text, audio and video communication should be supported among different carriers and devices.
+
+### **10.1.4 Media conversion**
+
+Media conversion services (such as voice to text and text to voice) should be provided.
+
+## **10.2 Telecommunications platform services**
+
+### **10.2.1 Alternative media**
+
+Certain types of information cannot be subject to media conversion by terminal equipment. In this case, provision should be made to enable information providers to provide information services via alternative media.
+
+### **10.2.2 Media conversion**
+
+Media conversion services (such as voice to text and text to voice) should be provided, if technically feasible.
+
+### **10.2.3 Multimedia content information alternatives**
+
+Where multimedia content is supported, provision should be made to enable information providers to supply text or other alternatives to non-text information if technically feasible.
+
+### **10.2.4 Device identification**
+
+If the network is capable of recognizing the characteristics of a terminal device, provision should be made to enable information providers to supply content tailored to the characteristics of the device.
+
+## **10.3 Emergency calls**
+
+Accessible means of every variety should be provided for emergency calls and confirmation of personal safety.
+
+## **10.4 Telecommunications services specifications**
+
+If possible, international standard specifications should be used in planning, development, and design of telecommunications services in order to promote development and usage of assistive technology for older persons and persons with disabilities. If non-standard specifications are necessarily used, these should be open to the public if possible.
+
+# **11 Requirements for user support**
+
+This clause includes the requirements for user support to ensure and improve telecommunications accessibility.
+
+## **11.1 User manuals**
+
+Product user manuals should be provided on forms of media that are accessible to older persons and persons with disabilities.
+
+## **11.2 Disclosure of information about telecommunications accessibility**
+
+### **11.2.1 Scope of disclosed information**
+
+Information on telecommunications accessibility for as many products as possible should be disclosed to the public.
+
+### **11.2.2 Methodology**
+
+Information on telecommunications accessibility should be disclosed in formats that are accessible to as many people (including older persons and persons with disabilities) as possible.
+
+## **11.3 Instruction**
+
+### **11.3.1 Support for suppliers**
+
+Information on telecommunications accessibility of a product should be supplied to retailers, information service providers and support providers as far as possible.
+
+### **11.3.2 Support for users**
+
+When users receive instructions, such instructions should be provided in accessible formats.
+
+## **11.4 Customer support centres**
+
+- a) Customer support centres should be able to provide information in as varied a format as possible to mesh with user needs. Customer support centres should be also able to communicate with persons with disabilities.
+- b) To check whether products can be used, customers should be able to try to use them beforehand.
+
+# Appendix I
+
+## Further details of informative references
+
+(This appendix does not form an integral part of this Recommendation)
+
+### **ETSI EG 202 048 V1.1.1 (2002-08): Human Factors (HF); Guidelines on the multimodality of icons, symbols and pictograms**
+
+ETSI EG 202 048 presents guidelines for the design and use of multimodal symbols using a Design for All approach. It also provides a study of the needs and requirements for the use of multimodal symbols in user interfaces, with special emphasis on the requirements of people with disabilities and elderly people.
+
+### **ETSI EG 202 116 V1.2.1 (2002-09): Human Factors (HF); Guidelines for ICT products and services; "Design for All"**
+
+ETSI EG 202 116 is applicable to ICT products with a user interface that are connectable to all kinds of fixed and mobile telecommunications networks. This includes products such as telephones, multimedia terminals, personal digital assistants (PDAs) and services such as e-mail, short message services (SMS) and voice messaging. It is applicable to public and private access devices and services.
+
+### **ETSI TR 101 806 V1.1.1 (2000-06): Human Factors (HF); Guidelines for Telecommunication Relay Services for Text Telephones**
+
+ETSI TR 101 806 is applicable to all kinds of relay services especially those which enable a text telephone user to converse with a telephone user and to relay services which enable a text telephone user to converse with another text telephone user. It also applies to "Spoken to spoken" relays (which translate from a speech impaired user) and to videophone relays.
+
+### **Resolution GSC 11-22 (UWG): User Needs, Considerations and Involvement**
+
+Resolution GSC 11-22 is the resolution of GSC (Global Standards Collaboration) regarding user needs.
+
+#### **ITU-T Rec. P.360 – Efficiency of devices for preventing the occurrence of excessive acoustic pressure by telephone receivers and assessment of daily noise exposure of telephone users**
+
+ITU-T Rec. P.360 proposes limits to the acoustic pressure generated by the handset and headset earphones and some guidance on how to measure it. It includes also some guidance to avoid speech degradation due to the use of devices implemented in the terminal to prevent the occurrence of excessive acoustic pressure.
+
+#### **ITU-T Rec. E.135 – Human factors aspects of public telecommunication terminals for people with disabilities**
+
+ITU-T Rec. E.135 includes services for people with vision, hearing, and motion impairments. Preferably, this Recommendation applies to all public terminals. Practically, however, this Recommendation may cover a subset of public terminals, as determined by particular service provider's circumstances and/or national laws.
+
+### **ITU-T Rec. E.138 – Human factors aspects of public telephones to improve their usability for older people**
+
+ITU-T Rec. E.138 proposes guidelines for the design of public telephone terminals for voice communication to make them simpler to use for older people whose sight, hearing, information processing and motor functions have deteriorated. This Recommendation provides information on the requirements of older people and how telephones can be adapted for their use. This
+
+Recommendation addresses manufacturers, designers, procurers, network operators, regulatory authorities, and those who deploy telecommunication terminals intended for general (public) use.
+
+**"Guidelines for Limiting Exposure to Time-Varying Electric, Magnetic, and Electromagnetic Fields (up to 300 GHz)"; The International Commission on Non-Ionizing Radiation Protection (ICNIRP).** <http://www.icnirp.de/documents/emfgdl.pdf>
+
+ICNIRP publishes guidelines on electromagnetic field levels. The main objective of this publication is to establish guidelines for limiting EMF exposure that will provide protection against known adverse health effects. Studies on both direct and indirect effects of EMF are described. Results of laboratory and epidemiological studies, basic exposure criteria, and reference levels for practical hazard assessment are discussed, and the guidelines presented apply to occupational and public exposure.
+
+## Bibliography
+
+- [b-ITU-T E.135] ITU-T Recommendation E.135 (1995), *Human factors aspects of public telecommunication terminals for people with disabilities.*
+- [b-ITU-T E.138] ITU-T Recommendation E.138 (2002), *Human factors aspects of public telephones to improve their usability for older people.*
+- [b-ITU-T P.360] ITU-T Recommendation 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-GSC 11-22] Resolution GSC 11-22 (UWG), *User Needs, Considerations and Involvement.*
+- [b-ETSI EG 202 048] ETSI EG 202 048 V1.1.1 (2002-08), *Human Factors (HF); Guidelines on the multimodality of icons, symbols and pictograms.*
+- [b-ETSI EG 202 116] ETSI EG 202 116 V1.2.1 (2002-09), *Human Factors (HF); Guidelines for ICT products and services; "Design for All".*
+- [b-ETSI TR 101 806] ETSI TR 101 806 V1.1.1 (2000-06), *Human Factors (HF); Guidelines for Telecommunication Relay Services for Text Telephones.*
+- [b-ICNIRP] Guidelines for Limiting Exposure to Time-Varying Electric, Magnetic, and Electromagnetic Fields (up to 300 GHz); The International Commission on Non-Ionizing Radiation Protection (ICNIRP), April 1998. <http://www.icnirp.de/documents/emfgdl.pdf>
+
+
+
+
+
+## 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           |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                             |
+| 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/F/T-REC-F.80-199110-I_PDF-E/raw.md b/marked/F/T-REC-F.80-199110-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..59f17537ac93f266a7e8833ac6b2daaa04ca29f8
--- /dev/null
+++ b/marked/F/T-REC-F.80-199110-I_PDF-E/raw.md
@@ -0,0 +1,125 @@
+
+
+![ITU logo: A globe with the letters ITU and a lightning bolt.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+ITU logo: A globe with the letters ITU and a lightning bolt.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**CCITT**
+
+**F.80**
+
+THE INTERNATIONAL  
+TELEGRAPH AND TELEPHONE  
+CONSULTATIVE COMMITTEE
+
+**TELEGRAPH AND MOBILE SERVICES  
+OPERATIONS AND QUALITY OF SERVICE**
+
+---
+
+**BASIC REQUIREMENTS FOR INTERWORKING  
+RELATIONS BETWEEN THE INTERNATIONAL  
+TELEX SERVICE AND OTHER SERVICES**
+
+**Recommendation F.80**
+
+---
+
+![CCITT logo: A globe with the letters CCITT.](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg)
+
+CCITT logo: A globe with the letters CCITT.
+
+Geneva, 1991
+
+# FOREWORD
+
+The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT 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 Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988).
+
+Recommendation F.80 was prepared by Study Group I and was approved under the Resolution No. 2 procedure on the 11th of October 1991.
+
+## --- CCITT NOTES
+
+- 1) In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication Administration and a recognized private operating agency.
+- 2) A list of abbreviations used in this Recommendation can be found in Annex A.
+
+# **BASIC REQUIREMENTS FOR INTERWORKING RELATIONS BETWEEN THE INTERNATIONAL TELEX SERVICE AND OTHER SERVICES**
+
+## **1 Scope**
+
+This Recommendation defines the basic requirements which should be observed when defining interworking relations between the international telex service and other services. The aim of this Recommendation is to ensure that by implementing such interworking relations no negative influences arise for subscribers of the international telex service.
+
+Only the perspective of a telex subscriber communicating with terminals of another service [via an interworking function (IWF)] is considered in this Recommendation.
+
+## **2 Introduction**
+
+Providers of new and evolving non-voice services are aiming to offer communication relations with the international telex service by introducing interworking functions. The provision of such interworking functions must not reduce the perceived Quality of Service or modify the operational procedures of the international telex service. Therefore, when defining interworking functions, the general characteristics of the international telex service, as well as its operational provisions, listed in Recommendations F.59 and F.60, must be considered.
+
+Since the specific interworking procedures are defined in detail within numerous Recommendations, it seems beneficial to summarize the basic requirements for interworking relations between the international telex service and other services within one single Recommendation.
+
+## **3 Interworking principles**
+
+### **3.0 *General***
+
+The conformance of interworking relations to the international telex service is shown in Table 1/F.80.
+
+TABLE 1/F.80
+
+### **Compliance with the characteristics of the international telex service in the different interworking cases**
+
+|  |     |                                                                           | Communication from the international telex service to destination service/terminal via an IWF |               |                |               |                |                        |               |                |                         |               |               |
+|--|-----|---------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|---------------|----------------|---------------|----------------|------------------------|---------------|----------------|-------------------------|---------------|---------------|
+|  |     |                                                                           | Mode                                                                                          |               | Real-time mode |               |                | Store-and-forward mode |               |                | Store-and-retrieve mode |               |               |
+|  |     |                                                                           | Destination service/terminal                                                                  | TLX           | DTE<br>(PSPDN) | Intex         | INM.A/B        | (TTX)                  | FAX           | INM C          | DTE<br>(PSTN)           | IPMS          | VTX           |
+|  |     |                                                                           | Applicable Recommendations                                                                    | F.60<br>U.202 | F.83<br>U.203  | F.82<br>U.210 | F.125<br>F.126 | F.81<br>U.201          | F.87<br>U.207 | F.127<br>U.208 | F.83<br>U.205           | F.84<br>U.204 | F.86<br>U.206 |
+|  | 2   | 1. Direct communication between terminals                                 |                                                                                               | Y             | Y              | Y             | Y              | N                      | N             | N              | N                       | N             | N             |
+|  | 2.1 | 2. Transmitted and received messages identical                            |                                                                                               | Y             | N<br>(Note 1)  | Y             | Y              | Y<br>(Note 2)          | Y             | N<br>(Note 1)  | N<br>(Note 1)           | N<br>(Note 1) | N<br>(Note 2) |
+|  | 2.2 | 3. ITA2-69 spacing characters/line                                        |                                                                                               | Y             | N<br>(Note 1)  | Y             | Y              | Y<br>(Note 2)          | Y             | N<br>(Note 1)  | N<br>(Note 1)           | N<br>(Note 1) | N<br>(Note 2) |
+|  | 2.3 | 4. Half-duplex communication; distant terminal can interrupt transmission |                                                                                               | Y             | N<br>(Note 1)  | Y             | Y              | N                      | N             | N              | N                       | N             | N             |
+|  | 2.6 | 5. Terminals continuously ready to receive                                |                                                                                               | Y             | N              | N<br>(Note 1) | Y              | Y                      | N             | N              | N                       | N             | N             |
+|  | 2.6 | 6. Printout in unattended mode                                            |                                                                                               | Y             | N              | N<br>(Note 1) | Y              | N                      | N             | N              | N                       | N             | N             |
+|  | 2.7 | 7. Exchange of terminal identification at any stage of the call           |                                                                                               | Y             | N<br>(Note 3)  | Y             | Y              | N                      | N             | N              | N<br>(Note 3)           | N             | N             |
+|  | 2.8 | 8. Automatic printout on continuous paper at both ends                    |                                                                                               | Y             | N              | N<br>(Note 1) | Y              | N                      | N             | N              | N                       | N             | N             |
+|  | 2.9 | 9. Conversation character-by-character                                    |                                                                                               | Y             | N<br>(Note 4)  | Y             | Y              | N                      | N             | N              | N                       | N             | N             |
+|  | 3.4 | 10. Terminal identification protected from user access                    |                                                                                               | Y             | N<br>(Note 3)  | Y             | Y              | Y                      | N<br>(Note 3) | N<br>(Note 3)  | N                       | N             | N             |
+|  | 3.4 | 11. Chronological printout of answerback exchange with message            |                                                                                               | Y             | N              | N<br>(Note 1) | Y              | Y                      | N             | N              | N                       | N             | N             |
+
+Y Comply N does not comply INM Inmarsat TTX Teletex FAX Group 3 facsimile IPMS Interpersonal Messaging Service VTX Videotex DTE Data terminal equipment
+
+*Note 1* – No CCITT definition of this terminal characteristic currently exists.
+
+*Note 2* – CCITT definition of terminal characteristic does exist. The telex subscriber can structure his message according to this definition. Deviations from telex characteristics are defined, namely, pagination and representation of ITA2 combinations 4 and 10 in figure case.
+
+*Note 3* – Provided by the IWF.
+
+*Note 4* – Text transfer takes place in packets.
+
+#### 3.1 *One-stage selection*
+
+In the case of one-stage selection, where the destination terminal will have been assigned a telex number that is part of the national telex numbering plan of the destination country, the originating telex subscriber may assume, notwithstanding a received answerback conforming to Recommendation F.74, that a normal telex connection has been established and all telex characteristics (as listed in Recommendation F.59) will be available at the destination terminal.
+
+#### 3.2 *Two-stage selection*
+
+3.2.1 In the case of a two-stage selection it can generally be assumed that a telex subscriber establishes by intention an interworking relationship with the subscriber of another service. However, it should be recognized that a subscriber of the international telex service may not be aware of any or all of the service parameters of the destination service, in particular of its presentation facilities.
+
+3.2.2 In two-stage-interworking functions (IWF) the two-stage selection procedure itself is already a definite deviation from the normal operational procedures for the originating telex subscriber. Since there is a need to inform the telex subscribers about the details of the selection procedure, it is also feasible to draw the attention of the telex subscribers to the fact, that he or she cannot expect all the basic characteristics of the international telex service (as listed in Recommendation F.59) to be available at the destination terminal. This limitation must be recognized and telex customers should be recommended to inform themselves about the characteristics of the destination service.
+
+3.3 As it may not be possible to identify the service of origin by only evaluating the text part of a received message, the operator of the receiving telex terminal should be provided with information to identify the origin of a received message. Therefore it is recommended that an IWF provide the recipient with sufficient information on how to recall the originator, for example, a recall address.
+
+3.4 In the particular case of a two-stage IWF/CF (conversion facility) on the telex side, it is recommended that the IWF attach a herald to the text of the message to indicate the source of the message and the recall address. Such a herald should include two fields, as follows:
+
+- the recall address, preceded by the text “FOR RECALL (service address)”;
+- the IWF/CF answerback.
+
+3.5 If, in an interworking relationship, a sender wants the recipient to receive the transmitted message in identical format, he or she should if possible, structure his message according to the presentation facilities of the receiver.
+
+3.6 In order to offer a satisfactory usability of service interworking relations to the subscriber, the service provider should offer sufficient information on the characteristics of the services concerned.
+
+3.7 These operational instructions for the subscriber should include indications on any deviations from the general characteristics of the international telex service, as listed in Recommendation F.59, inherent to the interworking function.
+
+3.8 In order to keep interworking relations as transparent as possible, any concatenation of interworking relations should be indicated to the user.
+
+3.9 In order to provide the originating telex subscriber with the ability to determine the status of a message previously deposited, or to cancel such a message, the IWF should provide, where relevant, a status enquiry function. This should be implemented in accordance with Recommendations F.89 and U.220.
\ No newline at end of file
diff --git a/marked/H/T-REC-H.110-198811-I_PDF-E/raw.md b/marked/H/T-REC-H.110-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..66b3841f6aa571076bfad94cb65bed276472a4c2
--- /dev/null
+++ b/marked/H/T-REC-H.110-198811-I_PDF-E/raw.md
@@ -0,0 +1,224 @@
+
+
+![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.110**
+
+**LINE TRANSMISSION  
+OF NON-TELEPHONE SIGNALS**
+
+---
+
+**HYPOTHETICAL REFERENCE CONNECTIONS  
+FOR VIDEOCONFERENCING USING PRIMARY  
+DIGITAL GROUP TRANSMISSION**
+
+**ITU-T Recommendation H.110**
+
+(Extract from the *Blue Book*)
+
+---
+
+# NOTES
+
+1 ITU-T Recommendation H.110 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.
+
+## **HYPOTHETICAL REFERENCE CONNECTIONS FOR VIDEOCONFERENCING USING PRIMARY DIGITAL GROUP TRANSMISSION**
+
+*(Malaga-Torremolinos, 1984; amended at Melbourne, 1988)*
+
+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 switched digital transmission networks known as the Integrated Digital Network (IDN) and Integrated Services Digital Network (ISDN) are under study, but the methods of exploiting these networks for the transmission of primary digital groups will not become clear until the studies have progressed further;
+- (d) that the existence of different digital hierarchies and different television standards in different countries complicates the problems of defining hypothetical reference connections;
+- (e) that a hypothetical reference connection may be used as a guide to simplify the problems of connections between countries with different television standards and digital hierarchies,
+
+*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 hypothetical reference connections for videoconferencing at bit rates which are multiples or sub-multiples of 384 kbit/s during subsequent study periods, so that this may be considered as the first of an evolving series of Recommendations,
+
+*noting*
+
+- (a) that a hypothetical reference connection is a model in which studies relating to overall performance may be made, thereby allowing comparisons with standards and objectives; on this basis, limits for various impairments can be allocated to the elements of the connection;
+- (b) that such a model may be used:
+  - by an Administration to examine the effects on transmission quality of changes of impairment allocations in national networks,
+  - by the CCITT for studying the allocation of impairments to component parts of international networks,
+  - to test national rules for *prima facie* compliance with any impairment criteria which may be recommended by the CCITT for national systems;
+- (c) that hypothetical reference connections are not to be regarded as recommending particular values of impairments allocated to constituent parts of the connection, and they are not intended to be used for the design of transmission systems,
+
+*and recognizing*
+
+that the planning of the necessary transmission networks for a videoconference service will be facilitated if recommended hypothetical reference connections are available, even if only in a preliminary form without details of all transmission and switching arrangements,
+
+*recommends*
+
+(1) that the hypothetical reference connection and means for digital transmission illustrated in Figures 1/H.110 and 2/H.110 shall be used as the model for studies of the overall performance of international videoconference connections, both intra-regional<sup>1)</sup> and inter-regional<sup>1)</sup>, which are provided using minimum numbers of encoding and decoding equipments;
+
+(2) that hypothetical reference connections of a more complex type, as, for example, those illustrated in Figure 3/H.110, being representative of many connections that may be employed in practice, should be studied further.
+
+*Note 1* – The hypothetical reference connection shown in Figure 1/H.110 contains the basic transmission elements, but is incomplete because switching has been excluded and the local ends and parts of the national network at each end of the connection have been left unspecified.
+
+*Note 2* – Because the arrangements of transmission systems interconnecting regions using different digital hierarchies have not yet been standardized, and because videoconferencing is likely to be a minority service in such transmission systems, it seems prudent to consider videoconference connections both where the primary hierarchical level on the inter-regional link is 1.5 Mbit/s and where it is 2 Mbit/s. In Figure 2b/H.110, the change between 2048 kbit/s and 1544 kbit/s transmission is placed at the 2048 kbit/s end of the long international network. The long distance part of the connection is thus operated at the lower bit rate. Where the international network is provided on a system which uses the 2048 kbit/s hierarchy, Figure 2c/H.110 maintains the efficiencies offered by the arrangement shown in Figure 2b/H.110, by making available the six vacated time slots for other use. Figure 2d/H.110 offers the possibility of improved picture quality compared with Figures 2b/H.110 and 2c/H.110 by making full use of the available 2048 kbit/s for the videoconferencing signal. This arrangement would require a 2048 kbit/s codec compatible with 525-line Video Standards, or the use of an external standards converter. This is for further study.
+
+*Note 3* – The lengths which have been assigned to the parts of the connections have been arbitrarily chosen, but have some consistency with existing CCITT and CCIR Recommendations. They are intended to be representative of long international connections, but not the longest possible. The lengths will likely require revision when studies on the error rates of digital paths have progressed to the stage when the error rates of the paths used in the connections can be predicted.
+
+*Note 4* – The propagation delay is one of the main factors to be studied based upon the structures and lengths of the connections in Figures 1/H.110, 2/H.110 and 3/H.110. However, in the absence of subjective test results, the specification of requirements for videoconferencing connections must await further study. This study and particularly operational experience are required to determine the extent to which Recommendation G.114, which applies to telephone connections, relates to videoconferencing connections.
+
+*Note 5* – In Figures 1/H.110 and 3/H.110, the codecs may be located anywhere within the international or national networks including the international gateway or the customer's premises.
+
+*Note 6* – The extensions beyond the codec shown as A or D in Figures 1/H.110 and 3/H.110 may include wideband analogue or high-speed digital transmission systems on terrestrial bearers. It is not expected that these transmission systems will have any significant influence on the quality of the picture or sound, or, on the propagation delay, other than that due to their length.
+
+*Note 7* – For inter-regional operation, television standards conversion between 525-line and 625-line video signals may be required. This conversion may be performed by the codecs themselves, or provided by external equipment.
+
+*Note 8* – The arrangements shown in Figure 2/H.110 provide for the simplest means of transmission. More complex means are possible and are not precluded.
+
+*Note 9* – The hypothetical reference connection shown in Figure 3/H.110 is of a more complex type than the connection shown in Figure 1/H.110, in that it includes codecs in cascade, and, possibly an external Television Standards Converter. The picture quality attainable with these more complex connections may be degraded with respect to that attainable using the connection illustrated in Figure 1/H.110. This and other aspects of the more complex connection must be studied further.
+
+<sup>1)</sup> 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.
+
+![Diagram of a hypothetical reference connection showing a NATIONAL NETWORK connected to an INTERNATIONAL NETWORK via CODEC units (C/D). The connection is labeled 'A or D' and 'DIGITAL TRANSMISSION (See Figure 2/H.110)'. The entire setup is labeled 'INTERNATIONAL CONNECTION'.](f9a14fbfecbd7d059226cc93677d721b_img.jpg)
+
+Diagram of a hypothetical reference connection showing a NATIONAL NETWORK connected to an INTERNATIONAL NETWORK via CODEC units (C/D). The connection is labeled 'A or D' and 'DIGITAL TRANSMISSION (See Figure 2/H.110)'. The entire setup is labeled 'INTERNATIONAL CONNECTION'.
+
+A or D – Wideband analogue or digital transmission or both all providing equivalent quality.
+
+National option.
+
+Digital transmission – Circuits for intra-regional or interregional digital transmission at the primary rate. This includes the international network and any national digital extensions thereof (see Figure 2/H.110).
+
+![Icon for a CODEC unit, represented by a square with a diagonal line and the letters 'C' and 'D'.](8e065eabc40a3645a569db7e9cd0da32_img.jpg)
+
+Icon for a CODEC unit, represented by a square with a diagonal line and the letters 'C' and 'D'.
+
+– Types of codec which may be used in the hypothetical reference connections are indicated below. Each can work with others of the same type and can interwork with other types shown, using a remultiplexer, if required. Codecs which perform these functions are described in Recommendation H.120.
+
+### Analogue
+
+### Digital
+
+![CODEC icon CODEC icon CODEC icon CODEC icon CODEC icon CODEC icon](d980a3f9608055996a07f31788baf827_img.jpg)
+
+|             |  |                                                                       |
+|-------------|--|-----------------------------------------------------------------------|
+| 1) 625 Line |  | 2048 kbits/s capable of interworking with 3                           |
+| 2) 625 Line |  | 2048 kbits/s with 6 time slots vacated capable of interworking with 4 |
+| 3) 525 Line |  | 2048 kbits/s capable of interworking with 1                           |
+| 4) 525 Line |  | 1544 kbits/s capable of interworking with 2                           |
+| 5) 525 Line |  | 1544 kbits/s capable of interworking with 6                           |
+| 6) 625 Line |  | 1544 kbits/s capable of interworking with 5                           |
+
+CODEC icon CODEC icon CODEC icon CODEC icon CODEC icon CODEC icon
+
+CCITT-02620
+
+FIGURE 1/H.110  
+Hypothetical reference connection
+
+![Four diagrams (a, b, c, d) illustrating means for digital transmission. Diagram (a) shows an intra-regional path P with distances 1250 km, 7500 km, and 1250 km. Diagram (b) shows an inter-regional path P1,5. Diagram (c) shows an inter-regional path P2 with 384 kbit/s inputs. Diagram (d) shows an inter-regional path P2. All diagrams include various network elements like A, B, RM, and TSA.](a7d78d22e465dea388b31d0739f9d0cd_img.jpg)
+
+The figure consists of four sub-diagrams labeled a) through d), each showing a different network topology for digital transmission.
+
+- a) Intra-regional:** A central dashed rectangle labeled *P* is flanked by two segments, each labeled "1250 km". The central segment is labeled "7500 km". At each corner of the central rectangle is a small square with an 'X'. At the far left and far right ends of the 1250 km segments are boxes labeled "A or B". Above the central rectangle, a dashed line with downward-pointing arrows connects two small squares with 'X'.
+- b) Inter-regional:** A central dashed rectangle labeled *P<sub>1,5</sub>* has a small square with an 'X' at each of its top corners. To the left of the rectangle, a sequence of boxes labeled B, RM, and A is connected. To the right, a box labeled A is connected. Above the rectangle, a dashed line with downward-pointing arrows connects the two 'X' squares.
+- c) Inter-regional:** A central dashed rectangle labeled *P<sub>2</sub>* has a small square with an 'X' at each of its top corners. To the left, a sequence of boxes labeled B, TSA, and B is connected, with an arrow pointing to the TSA box labeled "384 kbit/s". To the right, a sequence of boxes labeled B, TSA, RM, and A is connected, with an arrow pointing to the TSA box labeled "384 kbit/s". Above the rectangle, a dashed line with downward-pointing arrows connects the two 'X' squares.
+- d) Inter-regional:** A central dashed rectangle labeled *P<sub>2</sub>* has a small square with an 'X' at each of its top corners. To the left, a box labeled B is connected. To the right, a box labeled B is connected. Above the rectangle, a dashed line with downward-pointing arrows connects the two 'X' squares.
+
+A label "Distance (terrestrial)" is placed between diagrams (a) and (c). A label "CCITT-82600" is at the bottom right of diagram (d).
+
+Four diagrams (a, b, c, d) illustrating means for digital transmission. Diagram (a) shows an intra-regional path P with distances 1250 km, 7500 km, and 1250 km. Diagram (b) shows an inter-regional path P1,5. Diagram (c) shows an inter-regional path P2 with 384 kbit/s inputs. Diagram (d) shows an inter-regional path P2. All diagrams include various network elements like A, B, RM, and TSA.
+
+*Note* – The distances shown in Figure 2a/H.110 are applicable to Figures 2b/H.110, 2c/H.110 and 2d/H.110. These distances refer to terrestrial transmission. Equivalent distances relating to satellite transmissions are for further study.
+
+FIGURE 2/H.110  
+Means for digital transmission
+
+### *Symbols for Figure 2/H.110*
+
+![Symbol A: A square box with the letter 'A' inside.](9ebd85380ef496499e5f23ec0d9cd744_img.jpg)
+
+Symbol A: A square box with the letter 'A' inside.
+
+Termination of a 1544 kbit/s circuit with G.733 interface.
+
+![Symbol B: A square box with the letter 'B' inside.](c1c7af7ea36be0323047962df57d75b0_img.jpg)
+
+Symbol B: A square box with the letter 'B' inside.
+
+Termination of a 2048 kbit/s circuit with G.732 interface.
+
+![Symbol RM: A square box with the letters 'RM' inside.](67b83c4adaaa4de02d367168308deb2a_img.jpg)
+
+Symbol RM: A square box with the letters 'RM' inside.
+
+Remultiplex Unit. This provides bit rate conversion between the 1544 kbit/s frame and 2048 kbit/s frame from which 6 timeslots have been vacated.
+
+![Symbol TSA: A square box with the letters 'TSA' inside.](f3e03accc76df483950e65a9fb19c20e_img.jpg)
+
+Symbol TSA: A square box with the letters 'TSA' inside.
+
+Optional Time Slot Access Unit. This provides means of inserting and extracting 384 kbit/s from the 2048 kbit/s frame which is not used for video conferencing.
+
+P Primary level of digital hierarchy ( $y + n \times 384$  kbit/s, where  $n = 5$  or  $4$  and  $y = 128$  or  $8$  kbit/s, respectively).
+
+$P_{1.5}$  1544 kbit/s.
+
+$P_2$  2048 kbit/s.
+
+![Diagram of a complex hypothetical reference connection. It shows a signal path starting from a NATIONAL NETWORK on the left (with camera and monitor icons), passing through an 'A or D' interface into a codec block labeled C'/D'. This connects via a dashed line labeled 'DIGITAL TRANSMISSION' (referencing Figure 2/H.110) to another C'/D' codec. The path then enters the 'INTER-NATIONAL NETWORK' section, passing through a dashed box labeled 'TSC' (Television Standards Converter) and then a codec block labeled C/D. Another dashed 'DIGITAL TRANSMISSION' line (referencing Figure 2/H.110) leads to a final C/D codec block. The path exits through an 'A or D' interface into a second NATIONAL NETWORK on the right (with camera and monitor icons). The diagram is labeled CCITT-82610.](78d5774278a3f4a614f8c0ae485ce8d9_img.jpg)
+
+Diagram of a complex hypothetical reference connection. It shows a signal path starting from a NATIONAL NETWORK on the left (with camera and monitor icons), passing through an 'A or D' interface into a codec block labeled C'/D'. This connects via a dashed line labeled 'DIGITAL TRANSMISSION' (referencing Figure 2/H.110) to another C'/D' codec. The path then enters the 'INTER-NATIONAL NETWORK' section, passing through a dashed box labeled 'TSC' (Television Standards Converter) and then a codec block labeled C/D. Another dashed 'DIGITAL TRANSMISSION' line (referencing Figure 2/H.110) leads to a final C/D codec block. The path exits through an 'A or D' interface into a second NATIONAL NETWORK on the right (with camera and monitor icons). The diagram is labeled CCITT-82610.
+
+Same symbols as Figure 1/H.110, and
+
+![Symbol for Codecs: A square box divided by a diagonal line with 'C'' in the top-left half and 'D'' in the bottom-right half.](e40ba44ba095240702ed2099e01d23ce_img.jpg)
+
+Symbol for Codecs: A square box divided by a diagonal line with 'C'' in the top-left half and 'D'' in the bottom-right half.
+
+Codecs in the HRC of Figure 3/H.110 which may be any compatible (with one another) combination of those defined as C/D in Figure 1/H.110 but not capable of interworking with the specific C/D codecs in Figure 3/H.110.
+
+![Symbol for TSC: A dashed vertical rectangle containing the letters T, S, and C stacked vertically.](a612b25163221507295cc3d2fb679c10_img.jpg)
+
+Symbol for TSC: A dashed vertical rectangle containing the letters T, S, and C stacked vertically.
+
+External Television Standards Converter.  
+May or may not be required in the connection.
+
+FIGURE 3/H.110  
+**Complex hypothetical reference connection**
+
+Symbols for Figure 3/H.110:
+
+### Analogue
+
+### Digital
+
+![Symbol for 625 Line analogue to 2048 kbits/s digital interworking with 3 Symbol for 625 Line analogue to 2048 kbits/s with 6 time slots vacated digital interworking with 4 Symbol for 525 Line analogue to 2048 kbits/s digital interworking with 1 Symbol for 525 Line analogue to 1544 kbits/s digital interworking with 2 Symbol for 525 Line analogue to 1544 kbits/s digital interworking with 6 Symbol for 625 Line analogue to 1544 kbits/s digital interworking with 5](d0abac95583b52a3b35f74a215567334_img.jpg)
+
+|             |  |                                                                       |
+|-------------|--|-----------------------------------------------------------------------|
+| 1) 625 Line |  | 2048 kbits/s capable of interworking with 3                           |
+| 2) 625 Line |  | 2048 kbits/s with 6 time slots vacated capable of interworking with 4 |
+| 3) 525 Line |  | 2048 kbits/s capable of interworking with 1                           |
+| 4) 525 Line |  | 1544 kbits/s capable of interworking with 2                           |
+| 5) 525 Line |  | 1544 kbits/s capable of interworking with 6                           |
+| 6) 625 Line |  | 1544 kbits/s capable of interworking with 5                           |
+
+Symbol for 625 Line analogue to 2048 kbits/s digital interworking with 3 Symbol for 625 Line analogue to 2048 kbits/s with 6 time slots vacated digital interworking with 4 Symbol for 525 Line analogue to 2048 kbits/s digital interworking with 1 Symbol for 525 Line analogue to 1544 kbits/s digital interworking with 2 Symbol for 525 Line analogue to 1544 kbits/s digital interworking with 6 Symbol for 625 Line analogue to 1544 kbits/s digital interworking with 5
\ No newline at end of file
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e5e8abbbdda60b3dfae5a543bdf1f94a26c5f41c
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dd9d070efda0b1dd412617aa4deb7446917ed63db2e3acbd7bac521693a20023
+size 47768
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f5f75f59f3535c48a51a7dde281259e0703e6d01
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e01299c6b76fe3d214c3e803ffd44b36526df862a907b8f912f95b9980c150e4
+size 15188
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/060e30970c1a5549f43dd504aa8aaed0_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/060e30970c1a5549f43dd504aa8aaed0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8d7d57587a79c86bd4fef13f5155440ff9578d5e
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/060e30970c1a5549f43dd504aa8aaed0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6b8efda917e87ae9a5e8ac2fa99ac3757ae00ed0565424e388b4f7aca99e4747
+size 87716
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..30eb60f4e903b3105782ee337188b805bb181097
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0d69b04e0e872a441f4ebae0aba098ba6e49a3e2144a56bc7938ca02084b356c
+size 107818
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b3cb3fe621c2b486a5d198f08c3a7dce21b54551
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b5741f2461c98a632183d43cb9e3deb6fafd8e688d44562e2c93b88087f8ae0f
+size 82323
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/1dbb1d90b2022a3a765c85929a515cc6_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/1dbb1d90b2022a3a765c85929a515cc6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1034724bffc4732546058c56e3c759dbb805f953
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/1dbb1d90b2022a3a765c85929a515cc6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7ed17887056e18370fd76eed8dba61bb64e142cfe1938a11245b3564f4027388
+size 19264
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1929a68fbdb6fbcc57e1ff6e512227c00990dc5c
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8608f3b7617b461470f82bfe596ec134fa6493fb3f6af9daa30b0c8c28e3ac2c
+size 21533
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a06b02b9ad97d4d7c23079516a7a6f383e526e04
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5947c888bb43e97a0ed905e9472beecd15180b924a2329621ef0ff436a530624
+size 15848
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..07882e53216010a60e9a65c2269a1383f90fa8f5
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8d55bc1404a00110e016e59b37c568857c51417048eaede96b71d932cccb62e1
+size 8202
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d25dea0726132aa19ccbcd6a682e5806420c0953
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd8799efe66e5ba21b55788c4c392d55a79ab9a6a6f3f4b5979fe438018e677e
+size 41400
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/382a9c9e4816bd229191ab4591424dd8_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/382a9c9e4816bd229191ab4591424dd8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..718c99cc3f2f59f494ed3f69a0eb1d405c2ac366
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/382a9c9e4816bd229191ab4591424dd8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bbc9e8a95f0382d17de9327be1ba096b162bddff0b3d0716c698b1d4211ed690
+size 34583
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/3b950edb26a62dde5f3c0f41d9983edc_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/3b950edb26a62dde5f3c0f41d9983edc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f8cb314e8299118fa4c75455c49190cb4ec04351
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/3b950edb26a62dde5f3c0f41d9983edc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:019dd90f17e8451504ab55fb92c720c4d5b8062c55157425b8f781557c3d28f8
+size 8572
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/5000e9028ee2990f6242b2c0a952010d_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/5000e9028ee2990f6242b2c0a952010d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bb277ea7a1c582d2a20f42b954e7c73755a06bac
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/5000e9028ee2990f6242b2c0a952010d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e9be2dce14946093d6e7dd7e9c0be36d51ec56f1481705a8e79602197601a914
+size 37189
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/55086c71bc8ee4c0abc7160d26a8092c_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/55086c71bc8ee4c0abc7160d26a8092c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..72e7e737286746ecee6bb62635bf9688f751f81a
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/55086c71bc8ee4c0abc7160d26a8092c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:caa3d395b9fbf55eb5d9206911ef2829a27b19d8433350af46260c872fc31f62
+size 16112
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1d3441675a6f1b4270b9ac1b54056a462813218a
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e61d66bcf675cb2c240e5c9e0487b8efbe6c6abbde434d0cb1a22312572dcc3
+size 36991
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/6b95a21425e452581ef1a50ee2a6d391_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/6b95a21425e452581ef1a50ee2a6d391_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..412bb3f73dfb5e56ccdd40c140c319354738ec14
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/6b95a21425e452581ef1a50ee2a6d391_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ca435cbb416786e4e51ca5bb5a818d656235eea0a26796d6361f23ad41045237
+size 23207
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/7b96fce298a23fd76a01ff6c176c1059_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/7b96fce298a23fd76a01ff6c176c1059_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2be5b0d45021a02dad86970ea0431102fa5e399e
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/7b96fce298a23fd76a01ff6c176c1059_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:33a7c9dda73f140488d274ada751c3303c19bb7f3cb3770950d7728846d3d9f7
+size 22437
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..650b75395e9b5d0ddeae18233eaa89bcfdf19ff5
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f7862ce8bf3eeb9dd643cb2390ed7138a9cb43a25176664b5f404b7e85cb4d7d
+size 94547
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/896e86ed12aff206d302c64f2e3091fa_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/896e86ed12aff206d302c64f2e3091fa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cb196606ac910a1fc4c1c7f81e6e56286c15055f
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/896e86ed12aff206d302c64f2e3091fa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:799b5efe70777af4ef323910db2df8b857603f81eeab25a7d996d19d494f3938
+size 50998
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e1a3cce1b9c72ec75bb8e11d42340e140b16d7f3
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8ca583d281eecc4df8ac23d51fbb93fbca2cd46843d1c2e57759b73cc3b44256
+size 55065
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/8e80de0cac529b2c3775d677c5203133_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5bf8c77cbe7490530075698cd805ccce9fa7e324
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/8e80de0cac529b2c3775d677c5203133_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:29d819b80f9d43f70d1e416d6287e6ac8a78d5d6d843a66f85d06b3515947801
+size 50718
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/977811d1c73b74f801be9f4c376694ca_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/977811d1c73b74f801be9f4c376694ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f7084f6b4ff9af492e9a1545d9f7765e5b934f8e
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/977811d1c73b74f801be9f4c376694ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4cdcf2c1985deff92885fd65222fcef46484b4432767e6ee56b0e163fb68ce9d
+size 80192
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/97f61e67792478fb6ce089868e503063_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/97f61e67792478fb6ce089868e503063_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6c5b0b0b0abebb6064f95dc986964e04443a4107
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/97f61e67792478fb6ce089868e503063_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3849ff4d0a9e52c12b19c1c5d53ff8ddd2f62397b889c42921d729e3e8f15139
+size 136898
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/9b1ec0090070bdf52ea28763b8d52477_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f3acc7d193e5b85e7ca180c2ba79a9dcd14758d5
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/9b1ec0090070bdf52ea28763b8d52477_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2906e790766d83bc6ea015ae8ddf6b3b1515f698628ec61a9d8e6075307d2961
+size 24853
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/9cd85f266cdb1fb3ad544eb3dd3bd5e4_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/9cd85f266cdb1fb3ad544eb3dd3bd5e4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a87270b4b38a916875df2f9ae69affe00ad82ae2
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/9cd85f266cdb1fb3ad544eb3dd3bd5e4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae3d882d867f71d6bb2ae6cb732ff831d5bcac4f1e77fde8bc2f752d16498be6
+size 36844
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/b4f6d3668f7e851eaff07ccf26001623_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/b4f6d3668f7e851eaff07ccf26001623_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dc07cf0fd8d3e194e3b2a2e02a9de50bd8a0354b
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/b4f6d3668f7e851eaff07ccf26001623_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b03d27b2fe087ca2f988837c4b99de01c58218e9ca30fcc9d0f9b5e2e37cbf02
+size 19887
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/b6ad8b32179842fca5ad086cf22b03eb_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/b6ad8b32179842fca5ad086cf22b03eb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..846148122f4626963211833ce626bbcd6b42a03e
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/b6ad8b32179842fca5ad086cf22b03eb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e3bd4dff9eeea833fb0f713ff9144cce217ccfec9625040afe93f718ca67d5b8
+size 19621
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..69830f43559e5952fcd0d10efbfcec69b38b4fea
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:228ea6cb9c6869bf1badcbbac5b45af47ce09a69e8aba871eb90c3b1ad2f8cfc
+size 29532
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/b904ac2472cab80892d1e783e6230d6e_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/b904ac2472cab80892d1e783e6230d6e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..729375ad093f4c6834e5af205f95ca98a99c17c6
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/b904ac2472cab80892d1e783e6230d6e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c69556f94b34b08cfd6f5e777f6838261f7103ffd588f3768cf8187855622cd2
+size 24288
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/c1278da91cbcabe32628e589ebc47418_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/c1278da91cbcabe32628e589ebc47418_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f28c0ae394cc6fd2dace93edc303784c96e478a3
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/c1278da91cbcabe32628e589ebc47418_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:40b4d06e14b46a29343cd174496d447c82303984c56b4a76cefc78cb06ae2d87
+size 22834
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..306d4763c2aa2b93b9b477866efcf3d9a91853ea
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7f33668f1433c03a7003e630fda2937d80e10e9646b126b48add05d563e4b51e
+size 82572
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/e0113695dbf148bf5ec34354e544414b_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/e0113695dbf148bf5ec34354e544414b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..14316364b8b2d53e0ea443e7446873d44e31008e
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/e0113695dbf148bf5ec34354e544414b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a1c5f44eb66199737651b79655116f495527f046aa866c521d0786780cf17ab
+size 26018
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2862b2fc663ef984cd2bad80d39b0b0aba3a4061
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4c9294de7361e37979ba55c7e5ed78d436434a01df8e0a19c6bcdc3c2bc0f163
+size 54702
diff --git a/marked/H/T-REC-H.120-199303-I_PDF-E/e94cbc0895c6914a2bb53f150ab7495e_img.jpg b/marked/H/T-REC-H.120-199303-I_PDF-E/e94cbc0895c6914a2bb53f150ab7495e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7da586b3042e9e4999a9701faf3c90df29d09037
--- /dev/null
+++ b/marked/H/T-REC-H.120-199303-I_PDF-E/e94cbc0895c6914a2bb53f150ab7495e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:661808f93b7548085d118114e1bd42ba2b4d8db168fe8631bc7475fb19511050
+size 20791
diff --git a/marked/H/T-REC-H.200-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.200-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..07882e53216010a60e9a65c2269a1383f90fa8f5
--- /dev/null
+++ b/marked/H/T-REC-H.200-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8d55bc1404a00110e016e59b37c568857c51417048eaede96b71d932cccb62e1
+size 8202
diff --git a/marked/H/T-REC-H.222.1-199603-I_PDF-E/raw.md b/marked/H/T-REC-H.222.1-199603-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..00ca3529be71aa72afb4199f8be5e1c3181a45b8
--- /dev/null
+++ b/marked/H/T-REC-H.222.1-199603-I_PDF-E/raw.md
@@ -0,0 +1,892 @@
+
+
+![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.222.1**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+(03/96)
+
+**TRANSMISSION OF NON-TELEPHONE SIGNALS**
+
+---
+
+**MULTIMEDIA MULTIPLEX AND  
+SYNCHRONIZATION FOR AUDIOVISUAL  
+COMMUNICATION IN ATM ENVIRONMENTS**
+
+**ITU-T Recommendation H.222.1**
+
+(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.222.1 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
+
+|      |                                                                             | <i>Page</i> |
+|------|-----------------------------------------------------------------------------|-------------|
+| 1    | Scope.....                                                                  | 1           |
+| 2    | References.....                                                             | 1           |
+| 3    | Terms and definitions.....                                                  | 2           |
+| 4    | Abbreviations.....                                                          | 2           |
+| 5    | General.....                                                                | 2           |
+| 6    | Services provided by Recommendation H.222.1 .....                           | 3           |
+| 7    | H.222.1 Program Stream.....                                                 | 5           |
+| 7.1  | H.222.1 Program Stream syntax and semantics.....                            | 5           |
+| 7.2  | H.222.1 Program Stream timing model.....                                    | 5           |
+| 8    | H.222.1 Transport Stream.....                                               | 5           |
+| 8.1  | H.222.1 Transport Stream syntax and semantics.....                          | 5           |
+| 8.2  | H.222.1 Transport Stream timing model.....                                  | 5           |
+| 9    | H.222.1 Network adaptation functions .....                                  | 5           |
+| 10   | Interaction with the AAL .....                                              | 5           |
+| 10.1 | AAL type 1 .....                                                            | 5           |
+| 10.2 | AAL type 5 .....                                                            | 6           |
+| 11   | Subchannel signalling .....                                                 | 7           |
+| 11.1 | In-band subchannel signalling .....                                         | 7           |
+| 11.2 | Out-of-band subchannel signalling.....                                      | 7           |
+| 11.3 | Default subchannels.....                                                    | 8           |
+| 12   | H.222.1 stream_id .....                                                     | 8           |
+| 13   | Use of multiple ATM Virtual Channel Connections.....                        | 9           |
+| 13.1 | General.....                                                                | 9           |
+| 13.2 | Hierarchical coded video and multiple ATM Virtual Channel Connections ..... | 10          |
+| 14   | Descriptors .....                                                           | 10          |
+| 14.1 | ITU-T Recommendation H.222.0 descriptor priority .....                      | 10          |
+| 14.2 | ITU-T H.222.1 descriptors .....                                             | 11          |
+| 15   | Synchronization of H.222.1 defined elementary stream types.....             | 16          |
+| 15.1 | H.261 video .....                                                           | 16          |
+| 15.2 | H.263 video .....                                                           | 17          |
+| 15.3 | G.711 audio .....                                                           | 17          |
+| 15.4 | G.722 audio .....                                                           | 17          |
+| 15.5 | G.723 audio .....                                                           | 17          |
+| 15.6 | G.728 audio .....                                                           | 17          |
+| 16   | System Target Decoder for H.222.1 defined elementary stream types.....      | 17          |
+| 16.1 | Program Streams.....                                                        | 17          |
+| 16.2 | Transport Streams .....                                                     | 18          |
+| 17   | Video frame synchronous signalling.....                                     | 18          |
+| 18   | Mode changing.....                                                          | 18          |
+| 19   | Encryption.....                                                             | 18          |
+| 20   | H.222.1 demultiplexer errors .....                                          | 18          |
+|      | Appendix I – Recommended usage of H.222.0 descriptors .....                 | 19          |
+|      | Appendix II – ITU-T Timing Descriptor usage.....                            | 20          |
+
+# **SUMMARY**
+
+This Recommendation describes the multiplexing and synchronization of multimedia information for audiovisual communications in ATM environments. It specifies the H.222.1 Program Stream and the H.222.1 Transport Stream by choosing necessary coding elements from the generic H.222.0 specifications and by adding items for use in ATM environments. It also covers methods for accommodating ITU-T defined elementary streams.
+
+# MULTIMEDIA MULTIPLEX AND SYNCHRONIZATION FOR AUDIOVISUAL COMMUNICATION IN ATM ENVIRONMENTS
+
+(Geneva, 1996)
+
+## 1 Scope
+
+This Recommendation describes the multiplexing and synchronization of multimedia information, for audiovisual communication in ATM environments. This Recommendation specifies the peer-to-peer syntax, semantics and procedures, and the interactions with the AAL.
+
+## 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.
+
+- [1] CCITT Recommendation G.711 (1988), *Pulse Code Modulation (PCM) of voice frequencies*.
+- [2] CCITT Recommendation G.722 (1988), *7 kHz audio-coding within 64 kbit/s*.
+- [3] ITU-T Recommendation G.723.1 (1996), *Dual rate speech coder for multimedia communication transmitting at 5.3 and 6.3 kbit/s*.
+- [4] CCITT Recommendation G.728 (1992), *Coding of speech at 16 kbit/s using low-delay code excited linear prediction*.
+- [5] ITU-T Recommendation H.222.0 (1995) | ISO/IEC 13818-1:(1996), *Information technology – Generic coding of moving pictures and associated audio information: Systems*.
+- [6] ITU-T Recommendation H.233 (1995), *Confidentiality system for audiovisual services*.
+- [7] ITU-T Recommendation H.245 (1996), *Control protocol for multimedia communication*.
+- [8] ITU-T Recommendation H.261 (1993), *Video codec for audiovisual services at  $p \times 64$  kbit/s*.
+- [9] ITU-T Recommendation H.262 (1995) | ISO/IEC 13818-2:(1995), *Information technology – Generic coding of moving pictures and associated audio information: Video*.
+- [10] ITU-T Recommendation H.263 (1996), *Video coding for low bit rate communication*.
+- [11] ITU-T Recommendation I.311 (1993), *B-ISDN general network aspects*.
+- [12] ITU-T Recommendation I.361 (1995), *B-ISDN ATM layer specification*.
+- [13] ITU-T Recommendation I.362 (1993), *B-ISDN ATM Adaptation Layer (AAL) functional description*.
+- [14] ITU-T Recommendation I.363 (1993), *B-ISDN ATM Adaptation Layer (AAL) specification*.
+- [15] ITU-T Recommendation T.120 (1996), *Data protocols for multimedia conferencing*.
+- [16] ITU-T Recommendation Q.2931 (1995), *Broadband Integrated Services Digital Network (B-ISDN) – Digital Subscriber Signalling System No. 2 (DSS 2) – User-Network Interface (UNI) layer 3 specification for basic call connection control*.
+
+## 3 Terms and definitions
+
+For the purposes of this Recommendation, the following definition applies:
+
+**3.1 subchannel:** A logical channel in Recommendation H.222.1 formed from packets having a unique multiplex identifier field value. A subchannel carries one H.222.1 elementary stream. A subchannel is unidirectional. There may be many subchannels within one ATM Virtual Channel.
+
+## 4 Abbreviations
+
+For the purposes of this Recommendation the following abbreviations are used:
+
+|         |                                              |
+|---------|----------------------------------------------|
+| AAL     | ATM Adaptation Layer                         |
+| ACELP   | Algebraic Codebook Excited Linear Prediction |
+| ATM     | Asynchronous Transfer Mode                   |
+| CA      | Conditional Access                           |
+| CDV     | Cell Delay Variation                         |
+| CPCS    | Common Part Convergence Sublayer             |
+| DP      | Data Partitioning                            |
+| DTS     | Decoding Time Stamp                          |
+| EOB     | End_of_Block                                 |
+| GOP     | Group of Picture                             |
+| LD-CELP | Low-Delay Codebook Excited Linear Prediction |
+| MBA     | Macro Block Address                          |
+| MP-MLQ  | Multi-Pulse Maximum Likelihood Quantization  |
+| PCR     | Program Clock Reference                      |
+| PDU     | Protocol Data Unit                           |
+| PES     | Packetized Elementary Stream                 |
+| PS      | Program Stream                               |
+| PSI     | Program Specific Information                 |
+| PSM     | Program Stream Map                           |
+| PTS     | Presentation Time Stamp                      |
+| QOS     | Quality of Service                           |
+| RTI     | Real Time Interface                          |
+| SCR     | System Clock Reference                       |
+| SDU     | Service Data Unit                            |
+| STC     | System Time Clock                            |
+| STD     | System Target Decoder                        |
+| TS      | Transport Stream                             |
+
+## 5 General
+
+This Recommendation deals with the multiplexing and synchronization of multiple multimedia signals, for use in audiovisual communications in ATM environments. The multimedia signals may be coded audio or video or other data signals.
+
+This Recommendation is suitable for various applications such as conversational services, distributive services, retrieval services and messaging services.
+
+This Recommendation is applicable to both unidirectional and bidirectional physical connections. A bi-directional connection may be symmetrical or asymmetrical.
+
+This Recommendation addresses constant bit rate coded video. No specific support is provided for variable bit rate coded video. Variable bit rate coded video is however not precluded.
+
+This Recommendation uses the services provided by the AAL. The AAL is specified in Recommendation I.363 [14]. The use of AAL type 1 and type 5 is specified here.
+
+This Recommendation may also be suitable for use in environments other than ATM.
+
+This Recommendation specifies two separate and independent protocols. They are:
+
+- H.222.1 Program Stream.
+- H.222.1 Transport Stream.
+
+These two protocols are based upon the Program Stream and Transport Stream respectively, defined in Recommendation H.222.0 [5]. This Recommendation specifies the necessary coding elements in H.222.0 plus additional functionalities to form the H.222.1 Program Stream protocol and the H.222.1 Transport Stream protocol. An overview of H.222.1 and its relation to Recommendation H.222.0 is shown in Figure 1.
+
+![Diagram illustrating the H.222.1 overview. A large box labeled 'H.222.1' contains two boxes: 'H.222.0 Program Stream' and 'H.222.0 Transport Stream'. Below these is a box labeled 'H.222.1 Network adaptation'. Above the 'H.222.1' box are three pairs of vertical arrows pointing up and down, with a dashed line between the first and second pairs. Below the 'H.222.1 Network adaptation' box is a single downward-pointing arrow. The text 'T1518830-95/d01' is located to the right of the bottom arrow.](1c953f32bd34345dfd68fddf8a3736d6_img.jpg)
+
+The diagram shows a large rectangular box labeled 'H.222.1' at the top left. Inside this box, there are two smaller rectangular boxes side-by-side: 'H.222.0 Program Stream' on the left and 'H.222.0 Transport Stream' on the right. Below these two boxes, centered within the 'H.222.1' box, is a third rectangular box labeled 'H.222.1 Network adaptation'. Above the 'H.222.1' box, there are three pairs of vertical arrows pointing both up and down. The first pair is on the left, the second pair is in the middle (aligned with the gap between the two inner boxes), and the third pair is on the right. A dashed line is positioned between the first and second pairs of arrows. Below the 'H.222.1 Network adaptation' box, a single vertical arrow points downwards. To the right of this bottom arrow, the text 'T1518830-95/d01' is written.
+
+Diagram illustrating the H.222.1 overview. A large box labeled 'H.222.1' contains two boxes: 'H.222.0 Program Stream' and 'H.222.0 Transport Stream'. Below these is a box labeled 'H.222.1 Network adaptation'. Above the 'H.222.1' box are three pairs of vertical arrows pointing up and down, with a dashed line between the first and second pairs. Below the 'H.222.1 Network adaptation' box is a single downward-pointing arrow. The text 'T1518830-95/d01' is located to the right of the bottom arrow.
+
+FIGURE 1/H.222.1  
+**H.222.1 overview**
+
+## 6 Services provided by Recommendation H.222.1
+
+The following services are provided by H.222.1 to the H.222.1 user:
+
+### a) *Multiplexing*
+
+Multiplexing is based on a sequence of PDUs, each of which carry consecutive data from one and only one media source type, i.e. audio, video or other data signals. In the H.222.1 Program Stream these PDUs may be of variable length and relatively large in size. In the H.222.1 Transport Stream these PDUs are of fixed length and of relatively small size. The H.222.1 Transport Stream has a large multiplex capacity.
+
+### b) *Timebase recovery*
+
+A program is a collection of associated media, all of which refer to a common timebase. The timebase is referred to as the System Time Clock (STC). The H.222.1 Program Stream supports one and only one program. The H.222.0 Transport Stream supports multiple programs. H.222.1, however, constrains the number of programs in the Transport Stream to be one.
+
+The send side and receive side each have their own timebases. Time stamps attached to specific PDUs identify the intended time of arrival of the PDU at the receive side. Synchronization of the receive side timebase with the send side timebase may be achieved using these time stamps. H.222.1 provides optional additional timebase recovery information, which may be useful in jittered environments.
+
+### c) *Media presentation synchronization*
+
+Additional time stamps identify times at which entities in each media are to be presented to the end user.
+
+### d) *Timing jitter removal*
+
+Recommendation H.222.1 may offer the capabilities to remove the effects of time delay variation on the encoded bit stream at the receiver.
+
+### e) *Buffer management*
+
+Rules are specified so as to avoid underflow and overflow of receive side buffers. This is achieved by a hypothetical receive side timing model, which specifies timing relationships between outgoing PDUs at the send side.
+
+### f) *Security and access control*
+
+Security and access control services are provided by media encryption. Support for entitlement control and management messages is also provided.
+
+### g) *In-band signalling*
+
+The multiplexing service provides multiple connection end points at the user/H.222.1 service boundary. Protocol is provided that signals to the receive side the association between a PDU and a connection end point. The nature of the information carried by the connection is also described.
+
+### h) *Error reporting*
+
+Protocol at the receive side reports error conditions to the H.222.1 user.
+
+### i) *Trick mode*
+
+Mechanisms to support video recorder like control functionality, e.g. fast forward, rewind etc. are included.
+
+### j) *Network maintenance*
+
+A network maintenance service, which monitors channel errors, is available.
+
+### k) *Remultiplex support*
+
+In the H.222.1 Transport Stream mechanisms to assist in the addition and removal of individual elementary streams are provided. This service only has meaning at a network element. This service is not explicitly supported in the H.222.1 Program Stream.
+
+### l) *Local program insertion*
+
+In the H.222.1 Transport Stream mechanisms are provided to assist in the replacement of one elementary stream with another elementary stream. This service only has meaning at a network element. This service is not explicitly supported in the H.222.1 Program Stream.
+
+### m) *Priority*
+
+In the H.222.1 Transport Stream, one of two priorities may be indicated for each PDU. This service only has meaning at a network element. This service is not explicitly supported in the H.222.1 Program Stream.
+
+It is not stated here as to which services are mandatory. An application decides what services are appropriate.
+
+## **7 H.222.1 Program Stream**
+
+### **7.1 H.222.1 Program Stream syntax and semantics**
+
+The H.222.0 Program Stream syntax and semantics apply, as defined in 2.5.3/H.222.0.
+
+The H.222.0 Program Stream Map is defined in 2.5.4/H.222.0. See clause 11 for details of H.222.1 usage of the H.222.0 PSM.
+
+The H.222.0 Program Stream Directory is defined in 2.5.5/H.222.0. Use of the H.222.0 Program Stream Directory is optional in the H.222.1 Program Stream.
+
+### **7.2 H.222.1 Program Stream timing model**
+
+The H.222.0 Program Stream System Target Decoder as defined in 2.5.2/H.222.0 applies.
+
+# **8 H.222.1 Transport Stream**
+
+The H.222.0 Transport Stream supports multiple programs, where a program is as defined in Recommendation H.222.0. Recommendation H.222.1 supports only single program Transport Streams. Multiple program Transport Streams are not supported.
+
+## **8.1 H.222.1 Transport Stream syntax and semantics**
+
+The H.222.0 Transport Stream syntax and semantics apply, as defined in 2.4.3/H.222.0.
+
+The H.222.0 Program Specific Information (PSI) is defined in 2.4.4/H.222.0. See clause 11 for details of H.222.1 usage of the H.222.0 PSI.
+
+### **8.2 H.222.1 Transport Stream timing model**
+
+The Transport Stream System Target Decoder as defined in 2.4.2/H.222.0 applies.
+
+## **9 H.222.1 Network adaptation functions**
+
+Recommendation H.222.1 may offer the capabilities to remove the effects of time-delay variation on the encoded bit stream at the receiver. No specific syntax is provided. The actual mechanism used is application dependent.
+
+NOTE – The Cell Delay Variation (CDV) at the input of the H.222.1 decoder depends on the network size, the volume and the characteristics of accommodated traffic, amongst other factors. It is assumed that the CDV value may be of the order of about 1-3 ms for CBR traffic at 156 Mbit/s data rate. If the H.222.0 decoder implementation can only accept CDV less than the above value at its input, then the H.222.1 network adaptation should provide the necessary CDV reduction. Allocation of the allowable CDV to the H.222.0 decoder and the H.222.1 network adaptation as well as the method to reduce the CDV in the H.222.1 network adaptation are left to the choice of implementation.
+
+## **10 Interaction with the AAL**
+
+The Program Stream and the Transport Stream may use the services of AAL type 1 and AAL type 5.
+
+### **10.1 AAL type 1**
+
+The Program Stream and the Transport Stream may use the service provided by AAL type 1 at the AAL-SAP. Two primitives are used between the AAL and the AAL user being AAL-UNITDATA-REQUEST and AAL-UNITDATA-INDICATION. The AAL-SDU length may be one bit or one byte according to the application.
+
+The AAL type 1 Convergence Sublayer offers a number of functions to deal with cell delay variation, lost and misinserted cells, timing relationship and correction of bit errors and lost cells.
+
+It is not specified here as to which AAL type 1 functions should be used. This is left to the application to specify.
+
+### 10.2 AAL type 5
+
+The Program Stream and the Transport Stream may use the services provided by the AAL type 5 Common Part Convergence Sublayer. Two signals are used between AAL type 5 CPCS and the AAL type 5 CPCS user, being CPCS-UNITDATA invoke and CPCS-UNITDATA signal.
+
+Recommendation H.222.1 uses the error detection function offered by the AAL type 5 CPCS layer. This, in combination with simple error concealment in the video decoder, should provide sufficient error resilience.
+
+It is an implementation option as to whether a corrupted AAL type 5 CPCS-PDU is discarded, or whether a corrupted AAL type 5 CPCS-PDU is passed to H.222.1.
+
+#### 10.2.1 AAL type 5 for one way audiovisual transmission
+
+#### The Transport Stream
+
+H.222.1 Transport Stream packets shall be mapped into AAL type 5 with a NULL Service Specific Convergence Sublayer. In the mapping, one to N Transport Streams packets are mapped into an AAL type 5 DDU.
+
+For Switched Virtual Circuits (SVCs), the value of N is established via ATM user-to-network call/connection control at call setup using the AAL type 5 maximum CPCS-SDU size negotiation procedure. The AAL type 5 maximum CPCS-SDU size that is signalled is  $N \times 188$  bytes, where N is the number of TS packets in the AAL type 5 SDU. This procedure is defined in Recommendation Q.2931 [16].
+
+For Permanent Virtual Circuits (PVCs), the default value of N is two (maximum CPCS-SDU size = 376 bytes). Other values of N may be selected by bilateral agreement via network provisioning.
+
+Furthermore, in order to ensure a base level of interoperability, all equipment shall support  $N = 2$  (CPCS-SDU size = 376 bytes).
+
+In summary, the mapping shall be:
+
+- Each AAL type 5 CPCS-SDU shall contain N Transport Stream packets, unless there are fewer than N packets left in the Transport Stream, in which case the final CPCS-SDU contains all of the remaining packets.
+- The value of N is established via ATM signalling and is equal to the AAL type 5 CPCS-SDU size divided by 188. The default AAL type 5 CPCS-SDU size is 376 octets, which is two Transport Stream packets ( $N = 2$ ).
+- In order to ensure a base level of interoperability, all equipment shall support the value  $N = 2$  (AAL type 5 CPCS-SDU size of 376 octets).
+
+Specifically when  $N = 2$ , the mapping shall be as follows:
+
+- An AAL type 5 PDU shall contain two Transport Stream packets unless it contains the last Transport Stream packet of the Transport Stream, in which case an AAL type 5 PDU shall contain one or two Transport Stream packets.
+
+When an AAL type 5 PDU contains two Transport Stream packets, which have a length of 188 octets, the AAL type 5 CPCS-SDU has a length of 376 octets. This AAL type 5 CPCS-SDU, together with the CPCS-PDU trailer of 8 octets, requires 384 octets and maps into eight ATM cells with zero CPCS padding octets. This is illustrated in Figure 2.
+
+#### The Program Stream
+
+The mapping method for Program Streams is for further study.
+
+#### 10.2.2 AAL type 5 for two way audiovisual communications
+
+The method described in 10.2.1 may be used. Other methods are for further study.
+
+![Diagram of AAL type 5 CPCS-PDU structure showing two Transport Stream (TS) packets and a trailer.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+The diagram illustrates the structure of an AAL type 5 CPCS-PDU. At the top, two Transport Stream (TS) packets are shown, labeled 'TS packet *i*' and 'TS packet *i* + 1'. Each TS packet is 188 octets long. Below the TS packets, a dashed line indicates the 'CPCS-PDU payload', which is 376 octets long (the sum of the two TS packets). To the right of the payload is an '8 octets' 'CPCS-PDU trailer'. The total length of the CPCS-PDU is indicated as 'CPCS-PDU = 8 × 48 octets'. A label '1st octet of TS packet' points to the beginning of the first TS packet. The reference 'T1520220-95/d02' is shown at the bottom right.
+
+Diagram of AAL type 5 CPCS-PDU structure showing two Transport Stream (TS) packets and a trailer.
+
+FIGURE 2/H.222.1  
+**Representation of AAL type 5 CPCS-PDU containing  
+ two Transport Stream packets**
+
+## 11 Subchannel signalling
+
+Subchannel signalling is the process by which a subchannel is established and released between peer send and receive H.222.1 entities. Subchannel signalling involves management of a unique multiplex identifier value at the send side and transmission of this value, together with information about the audiovisual data to be carried within the subchannel, to the receiver.
+
+Subchannel signalling may use acknowledged or unacknowledged procedures. In addition subchannel signalling may be performed in-band or out-of-band with respect to the H.222.1 multiplex.
+
+A unidirectional audiovisual call, with no return signalling channel, may only use unacknowledged procedures.
+
+A unidirectional or bidirectional audiovisual call, where a return signalling channel exists, may use unacknowledged or acknowledged procedures. Acknowledged signalling procedures offer improved call phase synchronization.
+
+### 11.1 In-band subchannel signalling
+
+Unacknowledged in-band subchannel signalling in the H.222.1 Program Stream is coded using the H.222.0 Program Stream Map, as defined in 2.5.4/H.222.0.
+
+Unacknowledged in-band subchannel signalling in the H.222.1 Transport Stream is coded using the Program Specific Information (PSI), as defined in 2.4.4/H.222.0.
+
+Subchannel signalling using unacknowledged procedures achieves reliable operation through the repeated transmission of signalling information. The frequency of repetition of signalling information is not specified here.
+
+No in-band acknowledged procedures are specified in Recommendation H.222.0 or H.222.1.
+
+### 11.2 Out-of-band subchannel signalling
+
+An out-of-band channel may have the advantage of being able to offer a reliable transport service for subchannel signalling.
+
+When out-of-band subchannel signalling is used, it is not mandatory to code in-band signalling information, i.e. Program Stream Map/Program Specific Information.
+
+However, all of the signalling information that would have otherwise been coded in-band in the PSM/PSI tables must be made available to the H.222.1 decoder through the out-of-band channel.
+
+### 11.3 Default subchannels
+
+Default subchannels are defined as shown in Table 1. These subchannels are assumed to be established as soon as call establishment has been completed. All applications must recognize these subchannel numbers.
+
+TABLE 1/H.222.1
+
+#### Default subchannels
+
+| Application       | Program Stream            |                     | Transport Stream PID |
+|-------------------|---------------------------|---------------------|----------------------|
+|                   | stream_id                 | stream_id_extension |                      |
+| Rec. H.245        | ITU-T Rec. H.222.1 type C | 0x10                | 0x00010              |
+| G.711 A-law audio | ITU-T Rec. H.222.1 type B | 0x10                | 0x00011              |
+| G.711 μ-law audio | ITU-T Rec. H.222.1 type B | 0x20                | 0x00012              |
+
+During the call the default subchannels may be released using subchannel signalling procedures. The subchannel numbers may then be reused for other purposes.
+
+## 12 H.222.1 stream\_id
+
+For type A-E stream\_ids defined in Table 2-18/H.222.0, in both Program Streams and Transport Streams, the first byte of the PES packet payload is the stream\_id\_extension field, as shown in Table 2. In Table 2, PES\_packet\_payload() are the bytes following the PES packet header, where PES packet header is as defined in Recommendation H.222.0. N is the number of bytes in the PES packet payload.
+
+These stream\_ids have an associated stream\_type value of 0x09 as indicated in Table 2-29/H.222.0.
+
+TABLE 2/H.222.1
+
+### stream\_id\_extension
+
+| Syntax                                                       | No. of bits | Identifier    |
+|--------------------------------------------------------------|-------------|---------------|
+| PES_packet_payload() {<br><b>stream_id_extension</b>         | <b>8</b>    | <b>uimsbf</b> |
+| for(i=0;i<N–1;i++){<br><b>PES_packet_data_byte</b><br>}<br>} | <b>8</b>    | <b>bslbf</b>  |
+
+#### Semantics of PES\_packet\_payload() fields
+
+**stream\_id\_extension:** The stream\_id\_extension field is coded according to the stream\_id value, as shown in Table 3.
+
+TABLE 3/H.222.1
+
+#### Coding of stream\_id\_extension field
+
+| stream_id                                                                                                                                                                                                                             | Class | stream_id_extension:<br>b <sub>7</sub> b <sub>6</sub> b <sub>5</sub> b <sub>4</sub> b <sub>3</sub> b <sub>2</sub> b <sub>1</sub> b <sub>0</sub>                                     |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ITU-T Rec. H.222.1 type A                                                                                                                                                                                                             | video | b <sub>7</sub> b <sub>6</sub> b <sub>5</sub> b <sub>4</sub> – coded as per Table 8 (Note 2)<br>b <sub>3</sub> b <sub>2</sub> b <sub>1</sub> b <sub>0</sub> – stream number (Note 1) |
+| ITU-T Rec. H.222.1 type B                                                                                                                                                                                                             | audio | b <sub>7</sub> b <sub>6</sub> b <sub>5</sub> b <sub>4</sub> – coded as per Table 11 (Note 2)<br>b <sub>3</sub> b <sub>2</sub> b <sub>1</sub> b <sub>0</sub> – stream number         |
+| ITU-T Rec. H.222.1 type C                                                                                                                                                                                                             | data  | b <sub>7</sub> b <sub>6</sub> b <sub>5</sub> b <sub>4</sub> – coded as per Table 13 (Note 2)<br>b <sub>3</sub> b <sub>2</sub> b <sub>1</sub> b <sub>0</sub> – stream number         |
+| ITU-T Rec. H.222.1 type D                                                                                                                                                                                                             | any   | b <sub>7</sub> b <sub>6</sub> b <sub>5</sub> b <sub>4</sub> b <sub>3</sub> b <sub>2</sub> b <sub>1</sub> b <sub>0</sub> – stream number                                             |
+| ITU-T Rec. H.222.1 type E                                                                                                                                                                                                             | –     | reserved                                                                                                                                                                            |
+| NOTES                                                                                                                                                                                                                                 |       |                                                                                                                                                                                     |
+| 1 The stream number is allocated using the stream id extension descriptor (see 14.2).                                                                                                                                                 |       |                                                                                                                                                                                     |
+| 2 It is the four lower order of the bits of the values defined in Tables 8, 11 and 13, which are mapped to b <sub>7</sub> b <sub>6</sub> b <sub>5</sub> b <sub>4</sub> , when the stream_id indicates types A, B and C, respectively. |       |                                                                                                                                                                                     |
+
+## 13 Use of multiple ATM Virtual Channel Connections
+
+## 13.1 General
+
+This clause addresses applications which use coded audiovisual data in multiple ATM Virtual Channel Connections (VCC) in one call<sup>1)</sup>. When this is the case the following conditions apply:
+
+- for coded audiovisual data, there is one instance of H.222.1 per VCC. This means that for coded audiovisual data there is one Program Stream or Transport Stream per VCC. There may be additional VCCs which are part of the call, but which do not require use of the Program Stream or Transport Stream;
+- a call shall consist of only one H.222.0 defined program in each communication direction, i.e. all Program Streams/Transport Streams used in that call refer to one STC, for each direction of communication;
+- it is mandatory to code SCR/PCR in at least one Program Stream/Transport Stream respectively used in the call. It is optional as to whether SCR/PCR is coded in more than one Program Stream/Transport Stream respectively;
+
+the notion here is that since there is only one STC in the decoder, there is redundancy in sending SCR/PCRs on multiple VCCs;
+
+- where in-band signalling using PSM/PSI tables is used, then PSM/PSI tables must be coded and must be valid, in all Program Streams/Transport Streams used in the call.
+
+Where out-of-band signalling is provided PSM/PSI tables are optional in each Program Stream/Transport Stream as stated in 11.2.
+
+<sup>1)</sup> Virtual Channel Connection is defined in Recommendation I.311.
+
+## 13.2 Hierarchical coded video and multiple ATM Virtual Channel Connections
+
+Some applications may require that the hierarchical layers of the scalability profiles in Recommendation H.262 be mapped to separate virtual channels. This allows:
+
+- the video layer to be routed only where it is required; and
+- to select a network Quality of Service (QOS) appropriate for each layer.
+
+In order to improve error resilience, especially during severe error bursts, the video information may be optionally encoded according to a modified and restricted usage of the Data Partitioning (DP) specification of Recommendation H.262.
+
+In this usage, the base layer is not a DP video stream, it does not contain the DP `sequence_scalable_extension()` and does not contain priority break points. The base layer contains a `profile_and_level_id` specified in Recommendation H.262. All End\_of\_Blocks (EOBs) are in the base layer, as usual.
+
+The (modified) DP enhancement layer consists only of Sequence, GOP, Picture and Slice headers that are an exact copy of the headers in the base layer.
+
+In this modified usage, the Hierarchy descriptor, defined in 2.6.6/H.222.0, must be transmitted. It defines both base and enhancement layers using the `profile_and_level_id` of the base layer. The enhancement layer is specified as `hierarchy_type` DP.
+
+As usual, decoders that cannot utilize enhancement layers should discard them. Decoders that utilize this modified DP can identify the enhancement layer by its designation as `hierarchy_type` DP, but with a non DP Profile.
+
+## 14 Descriptors
+
+### 14.1 ITU-T Recommendation H.222.0 descriptor priority
+
+This clause defines priority rules for an H.222.1 decoder in the case of semantic conflict of Recommendation H.222.0 descriptors.
+
+Appendix I recommends H.222.1 encoder rules for H.222.0 descriptors. When applied these rules result in bit streams that avoid semantic conflict.
+
+H.222.0 program level descriptors and elementary stream level descriptors may sometimes be in conflict. To deal with this conflict four priority rules are defined. These rules are as follows:
+
+- a) The descriptor at the elementary stream level overrides a descriptor with similar meaning at the program level. However, the descriptor at the program level applies to all of the elementary streams of the program (descriptors that are not relevant are ignored).
+- b) The descriptor used at the program level is applied only to that program and has no meaning for an individual elementary stream. Similarly, an elementary stream descriptor has meaning only for that elementary stream and has no meaning at the program level.
+- c) The descriptor is ignored when it is present at the program level. It is applied to the associated elementary stream only when it is present at the elementary stream level.
+- d) The descriptor is ignored when it is present at the elementary stream level. It is applied to the associated program only when it is present in program level.
+
+In general programs and elementary streams descriptors are ignored where the meaning of that descriptor conflicts with some other semantic, e.g. an audio descriptor when contained in an elementary stream with a `video stream_type` value.
+
+The priority rules for the H.222.0 defined descriptors are shown in Table 4.
+
+TABLE 4/H.222.1
+
+#### **H.222.1 decoder priority rules for H.222.0 defined descriptors**
+
+| Tag no. | Descriptor                              | Priority rule |
+|---------|-----------------------------------------|---------------|
+| 2       | video_stream_descriptor                 | A             |
+| 3       | audio_stream_descriptor                 | A             |
+| 4       | hierarchy_descriptor                    | C             |
+| 5       | registration_descriptor                 | NS            |
+| 6       | data_stream_alignment_descriptor        | A             |
+| 7       | target_background_grid_descriptor       | A             |
+| 8       | video_window_descriptor                 | A             |
+| 9       | CA_descriptor                           | NS            |
+| 10      | ISO_639_language_descriptor             | A             |
+| 11      | system_clock_descriptor                 | D             |
+| 12      | multiplex_buffer_utilization_descriptor | A             |
+| 13      | copyright_descriptor                    | B             |
+| 14      | maximum_bitrate_descriptor              | NS            |
+| 15      | private_data_indicator_descriptor       | NS            |
+| 16      | smoothing_buffer_descriptor             | B (Note)      |
+| 17      | STD_descriptor                          | A             |
+| 18      | IBP_descriptor                          | A             |
+
+NS Not specified in this Recommendation
+
+NOTE – When the descriptor at the program level conflicts with a descriptor of similar meaning at the elementary stream level, the descriptor at the program level takes precedence.
+
+## **14.2 ITU-T H.222.1 descriptors**
+
+Table 5 defines the descriptor\_tag values for descriptors defined in this Recommendation.
+
+TABLE 5/H.222.1
+
+#### **H.222.1 descriptor\_tag values**
+
+| descriptor_tag | Identification                 |
+|----------------|--------------------------------|
+| 0-63           | ITU-T Rec. H.222.0 defined     |
+| 64             | reserved                       |
+| 65             | ITU-T_video_stream_descriptor  |
+| 66             | ITU-T_audio_stream_descriptor  |
+| 67             | ITU-T_data_stream_descriptor   |
+| 68             | stream_id_extension_descriptor |
+| 69             | ITU-T_timing_descriptor        |
+| 70-255         | reserved                       |
+
+The allowed application of the H.222.1 descriptors is specified in Table 6.
+
+TABLE 6/H.222.1  
+Allowed use of H.222.1 descriptors
+
+| Identification                                                                                                                                            | Program level | Elementary stream level |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------------------|
+| ITU-T_video_stream_descriptor                                                                                                                             | .             | X                       |
+| ITU-T_audio_stream_descriptor                                                                                                                             | .             | X                       |
+| ITU-T_data_stream_descriptor                                                                                                                              | .             | X                       |
+| stream_id_extension_descriptor*                                                                                                                           | .             | X                       |
+| ITU-T_timing_descriptor**                                                                                                                                 | X             | X                       |
+| X    Presence of the descriptor is permitted<br>.    Presence of the descriptor is disallowed<br>*    Not used in Transport Streams<br>**   Not mandatory |               |                         |
+
+For H.222.1 descriptors, when a descriptor is used at the program level it is applied only to that program and has no meaning for an elementary stream within that program. Similarly, when a descriptor is used at the elementary stream level, it has meaning only for that elementary stream and has no meaning at the program level [same as item b) defined in 14.1].
+
+All data elements named **reserved** shall be coded as defined in Recommendation H.222.0, i.e. all reserved bits set to binary ones. Also, extra data contained in descriptors, but undefined by this Recommendation, shall be discarded by decoders conforming to this Recommendation.
+
+### 14.2.1 ITU-T video stream descriptor
+
+The ITU-T video stream descriptor indicates the H.222.1 defined video elementary stream type. It is coded as shown in Table 7.
+
+TABLE 7/H.222.1  
+Coding of ITU-T video stream descriptor
+
+| Syntax                                  | No. of bits | Identifier    |
+|-----------------------------------------|-------------|---------------|
+| ITU-T_video_stream_descriptor() {       |             |               |
+| <b>descriptor_tag</b>                   | <b>8</b>    | <b>uimsbf</b> |
+| <b>descriptor_length</b>                | <b>8</b>    | <b>uimsbf</b> |
+| <b>coding_algorithm</b>                 | <b>8</b>    | <b>uimsbf</b> |
+| if(coding_algorithm == H.261    H.263){ |             |               |
+| <b>picture_format</b>                   | <b>3</b>    | <b>uimsbf</b> |
+| <b>minimum_picture_interval</b>         | <b>5</b>    | <b>uimsbf</b> |
+| }                                       |             |               |
+| }                                       |             |               |
+
+#### Semantics of the ITU-T video stream descriptor fields
+
+**coding\_algorithm:** The coding\_algorithm field indicates the type of H.222.1 defined video elementary stream type. It is coded as shown in Table 8.
+
+TABLE 8/H.222.1
+
+##### **coding\_algorithm coding**
+
+| Value     | Description            |
+|-----------|------------------------|
+| 0x00      | forbidden              |
+| 0x01      | Rec. H.261             |
+| 0x02      | Rec. H.261 without FEC |
+| 0x03      | Rec. H.263             |
+| 0x04-0xff | reserved               |
+
+**picture\_format:** The picture\_format field indicates the picture format for H.261 and H.263 video. It is coded as shown in Table 9.
+
+TABLE 9/H.222.1
+
+##### **picture\_format coding**
+
+| Value   | Description |
+|---------|-------------|
+| 000     | CIF         |
+| 001     | QCIF        |
+| 010     | sub-QCIF    |
+| 011     | 4CIF        |
+| 100     | 16CIF       |
+| 101-111 | reserved    |
+
+**minimum\_picture\_interval:** The minimum\_picture\_interval field indicates the minimum interval between pictures for H.261 and H.263 video. The minimum picture interval is calculated from the value contained in the minimum\_picture\_interval field as  $(\text{minimum\_picture\_interval} + 1)/29.97$ .
+
+### **14.2.2 ITU-T audio stream descriptor**
+
+The ITU-T audio stream descriptor indicates the H.222.1 defined audio elementary stream type. It is coded as shown in Table 10.
+
+TABLE 10/H.222.1
+
+#### **Coding of ITU-T audio stream descriptor**
+
+| Syntax                            | No. of bits | Identifier    |
+|-----------------------------------|-------------|---------------|
+| ITU-T_audio_stream_descriptor() { |             |               |
+| <b>descriptor_tag</b>             | <b>8</b>    | <b>uimsbf</b> |
+| <b>descriptor_length</b>          | <b>8</b>    | <b>uimsbf</b> |
+| <b>coding_algorithm</b>           | <b>8</b>    | <b>uimsbf</b> |
+| <b>reserved</b>                   | <b>8</b>    | <b>uimsbf</b> |
+| }                                 |             |               |
+
+##### Semantics of the ITU-T audio stream descriptor fields
+
+**coding\_algorithm:** The coding\_algorithm field indicates the type of H.222.1 defined audio elementary stream type. It is coded as shown in Table 11.
+
+TABLE 11/H.222.1
+
+###### coding\_algorithm
+
+| Value     | Description         |
+|-----------|---------------------|
+| 0x00      | forbidden           |
+| 0x01      | G.711 A-law         |
+| 0x02      | G.711 $\mu$ -law    |
+| 0x03      | Rec. G.722 (mode 1) |
+| 0x04      | Rec. G.722 (mode 2) |
+| 0x05      | Rec. G.722 (mode 3) |
+| 0x06      | Rec. G.723          |
+| 0x07      | Rec. G.728          |
+| 0x08-0xff | reserved            |
+
+#### 14.2.3 ITU-T data stream descriptor
+
+The ITU-T data stream descriptor indicates the H.222.1 defined data elementary stream type. It is coded as shown in Table 12.
+
+TABLE 12/H.222.1
+
+#### Coding of ITU-T data stream descriptor
+
+| Syntax                           | No. of bits | Identifier    |
+|----------------------------------|-------------|---------------|
+| ITU-T_data_stream_descriptor() { |             |               |
+| <b>descriptor_tag</b>            | <b>8</b>    | <b>uimsbf</b> |
+| <b>descriptor_length</b>         | <b>8</b>    | <b>uimsbf</b> |
+| <b>protocol</b>                  | <b>8</b>    | <b>uimsbf</b> |
+| <b>reserved</b>                  | <b>8</b>    | <b>uimsbf</b> |
+| }                                |             |               |
+
+#### Semantics of the ITU-T data stream descriptor fields
+
+**protocol:** The protocol field indicates the type of H.222.1 defined data elementary stream type. It is coded as shown in Table 13.
+
+#### 14.2.4 stream id extension descriptor
+
+The stream\_id\_extension descriptor maps the associated H.222.1 defined elementary stream type descriptor to a stream\_id\_extension field value. The stream\_id\_extension descriptor is only coded in elementary streams with stream\_id value equal to Recommendation H.222.1 type A to type E. The stream id extension descriptor is only coded at the elementary stream level of the Program Stream PSM table. It is not coded in the Transport Stream. The stream id extension descriptor is shown in Table 14.
+
+TABLE 13/H.222.1
+
+#### **Protocol coding**
+
+| Value     | Description                        |
+|-----------|------------------------------------|
+| 0x00      | forbidden                          |
+| 0x01      | H.245 subchannel                   |
+| 0x02      | video frame synchronous subchannel |
+| 0x03      | T.120 subchannel                   |
+| 0x04-0xff | reserved                           |
+
+TABLE 14/H.222.1
+
+#### **Coding of the stream id extension descriptor**
+
+| Syntax                                | No. of bits | Identifier    |
+|---------------------------------------|-------------|---------------|
+| stream_id_extension_descriptor() {    |             |               |
+| <b>descriptor_tag</b>                 | <b>8</b>    | <b>uimsbf</b> |
+| <b>descriptor_length</b>              | <b>8</b>    | <b>uimsbf</b> |
+| <b>elementary_stream_id_extension</b> | <b>8</b>    | <b>uimsbf</b> |
+| }                                     |             |               |
+
+#### **Semantics of the stream\_id\_extension\_descriptor fields**
+
+**elementary\_stream\_id\_extension:** The elementary\_stream\_id\_extension field indicates the value in the PES packet stream\_id\_extension field which carries the H.222.1 defined elementary stream type.
+
+#### **14.2.5 ITU-T timing descriptor**
+
+The ITU-T timing descriptor is shown in Table 15.
+
+TABLE 15/H.222.1
+
+#### **Coding of ITU-T timing descriptor**
+
+| Syntax                     | No. of bits | Identifier    |
+|----------------------------|-------------|---------------|
+| ITU-T_timing_descriptor(){ |             |               |
+| <b>descriptor_tag</b>      | <b>8</b>    | <b>uimsbf</b> |
+| <b>descriptor_length</b>   | <b>8</b>    | <b>uimsbf</b> |
+| <b>SC_PESPtR</b>           | <b>24</b>   | <b>bslbf</b>  |
+| <b>SC_TESPtR</b>           | <b>24</b>   | <b>bslbf</b>  |
+| <b>SC_TSPtR</b>            | <b>24</b>   | <b>bslbf</b>  |
+| <b>SC_byte_rate</b>        | <b>30</b>   | <b>bslbf</b>  |
+| <b>vbv_delay_flag</b>      | <b>1</b>    | <b>bslbf</b>  |
+| <b>reserved</b>            | <b>1</b>    | <b>bslbf</b>  |
+| <b>reserved</b>            | <b>32</b>   | <b>bslbf</b>  |
+| }                          |             |               |
+
+#### Semantics of the ITU-T timing descriptor fields
+
+**SC\_PESPtR:** “if not equal to” 0xfffff, this parameter indicates that PES packets are passed from the encoder buffer to the multiplexer buffer at a constant rate. Integer value is the ratio of 27 MHz to the PES packet rate. It specifies the interpacket duration for the next PES packet and all following packets up to and including the PES packet following a new valid SC\_PESPtR. This parameter is valid only in an elementary stream descriptor. If SC\_PESPtR is equal to 0xfffff, the PES interpacket duration is unspecified.
+
+**SC\_TESPtR:** “if not equal to” 0xfffff, this parameter indicates that TS packets for the specified elementary stream (hereinafter called TES packets) are passed from the encoder buffer to the multiplexer buffer at a constant rate. Integer value is the ratio of 27 MHz to the TES packet rate. It specifies the interpacket duration for the next TES packet and all following packets up to and including the TES packet following a new valid SC\_TESPtR. This parameter is valid only in an elementary stream descriptor. If SC\_TESPtR is equal to 0xfffff, the TES interpacket duration is unspecified.
+
+**SC\_TSPktR:** “if not equal to” 0xfffff, this parameter indicates a constant Transport Stream packet rate. Integer value is the ratio of 27 MHz to the TS packet rate. It specifies the interpacket duration for the current TS packet and all following packets up to and including the TS packet containing a new valid SC\_TSPktR. This parameter is valid only in a program descriptor. The program\_number indicates to which STC the TS packet rate is locked. If SC\_TSPktR is equal to 0xfffff, the Transport Stream interpacket duration is unspecified.
+
+**SC\_byterate:** “if not equal to” 0x3fffffff, this parameter indicates that PES bytes are passed from the encoder buffer to the multiplexer buffer at a constant rate. Integer value is the ratio of 27 MHz to (byte\_rate/50) i.e.  $SC\_byterate = 1\ 350\ 000\ 000 / byte\_rate$ . It specifies the interbyte duration for the next PES packet and all following packets up to and including the PES packet following a new valid SC\_byterate. This parameter is valid only in an elementary stream descriptor. If SC\_byterate is equal to 0x3fffffff, the PES interbyte duration is unspecified.
+
+**vbv\_delay\_flag:** This is a 1-bit flag which when set to “1” indicates that the video parameter vbv\_delay may be used for timing recovery. The last byte of picture\_start\_code (see Recommendation H.262 [9]) arrives nominally at time DTS-vbv\_delay. This flag is valid only in a video elementary stream descriptor.
+
+All rates mentioned above are locked to the STC, whose frequency is nominally 27 MHz.
+
+In the above defined data, the byte aligned string 0x000001 should be avoided in order to minimize start code emulation.
+
+A detailed explanation of the usage of this descriptor is provided in Appendix II.
+
+# 15 Synchronization of H.222.1 defined elementary stream types
+
+When H.222.1 defined elementary stream types are carried in a Program Stream or a Transport Stream, they shall have an associated System Time Clock.
+
+In the following subclauses access units for each of the ITU-T stream types are defined. The semantic definition of the PTS field in 2.4.3.7/H.222.0 applies. The PTS field refers to the time of presentation of the presentation unit represented by the first access unit in the PES packet payload.
+
+The DTS field is not coded in PES packets carrying data of the following ITU-T stream types. For these stream types PTS and DTS are always equal.
+
+### 15.1 H.261 video
+
+For an H.261 video elementary stream type an access unit is defined as the coded representation of a presentation unit, where a presentation unit is a picture. An access unit includes all of the coded data for a picture. The access unit begins with the H.261 picture start code and includes all data, including MBA stuffing up to the next H.261 picture start code.
+
+PTS thus refers to the H.261 picture start code, contained in the PES packet payload.
+
+## 15.2 H.263 video
+
+For an H.263 video elementary stream type an access unit is defined as the coded representation of a presentation unit, where a presentation unit is a picture. An access unit includes all of the coded data for a picture. The access unit begins with the H.263 picture start code, and includes all data stuffing up to the next H.263 picture start code.
+
+PTS thus refers to the H.263 picture start code, contained in the PES packet payload.
+
+In the case of PB-frames the access unit is the coded representation of two presentation units. In this case PTS refers to the time of presentation of the P-picture and not the B-picture.
+
+## 15.3 G.711 audio
+
+For a G.711 audio elementary stream type an audio access unit is defined as the coded representation of an audio sample with 8 kHz sampling frequency.
+
+The PTS field in the PES packet header thus refers to the time of presentation of the first byte of the elementary stream in the PES packet payload.
+
+## 15.4 G.722 audio
+
+For a G.722 audio elementary stream type an access unit is defined as the coded representation of a byte representing the highband audio component (2 bits) and the lowband audio component (4 bits for mode 1, 3 bits for mode 2, 2 bits for mode 3) with 16 kHz sampling frequency. In case of mode 2 or mode 3, the byte also includes 1 or 2 stuffing bits, respectively.
+
+The PTS field in the PES packet header thus refers to the time of presentation of the first byte of the elementary stream in the PES packet payload.
+
+## 15.5 G.723 audio
+
+For a G.723 audio elementary stream type an access unit is defined as the coded representation of an MP-MLQ/ACELP 30 ms frame. The start of the G.723 frame shall be aligned with the start of the PES packet payload.
+
+The PTS field in the PES packet header thus refers to the time of presentation of the first MP-MLQ/ACELP 30 ms frame in the PES packet payload.
+
+## 15.6 G.728 audio
+
+For a G.728 audio elementary stream type an access unit is defined as the coded representation of an LD-CELP 2.5 ms frame. The start of the G.728 frame shall be aligned with the start of the PES packet payload.
+
+The PTS field in the PES packet header thus refers to the time of presentation of the first LD-CELP frame in the PES packet payload.
+
+# 16 System Target Decoder for H.222.1 defined elementary stream types
+
+## 16.1 Program Streams
+
+When H.222.1 defined elementary stream types are multiplexed into Program Streams, multiplexing shall be performed in such a way that the constraints imposed by the P-STD defined in 2.5.2/H.222.0 with the following parameters, shall be met.
+
+H.261 and H.263 elementary streams shall be considered to be low delay streams, that is, as though they had a low\_delay flag set to "1".
+
+All H.261 and H.263 pictures shall be considered to be P-pictures.
+
+## 16.2 Transport Streams
+
+When H.222.1 defined elementary stream types are multiplexed into Transport Streams, multiplexing shall be performed in such a way that the constraints imposed by the T-STD defined in 2.4.2/H.222.0 with the following parameters, shall be met.
+
+The rate at which data is removed from the TB buffer, Rxn, shall be 4 000 000 bit/s for H.261 and H.263 elementary streams and shall be 2 000 000 bit/s for G.711, G.722, G.723 and G.728 elementary streams.
+
+For H.261 and H.263 elementary streams, the size of the elementary stream buffer, EBS, shall be equal to the size of the HRD buffer specified in H.261 and H.263 or the size of the HRD buffer negotiated with out-of-band signalling when this is used.
+
+For H.261 and H.263 elementary streams, the size of the multiplexing buffer, MBS, shall be equal to  $(1/750 + 0.004) * 4\ 000\ 000$  bits.
+
+For G.711, G.722, G.723 and G.728 elementary streams, the size of the main buffer, BS, shall be equal to 3584 bytes.
+
+Data shall be transferred from the multiplexing buffer to the elementary stream buffer using the leak method, where the leak rate, Rbx, shall be equal to 4 000 000 bit/s.
+
+H.261 and H.263 elementary streams shall be considered to be low delay streams, that is, as though they had a low\_delay flag set to "1".
+
+All H.261 and H.263 pictures shall be considered to be P-pictures.
+
+## 17 Video frame synchronous signalling
+
+Synchronization between a video frame synchronous signal and the video frame is achieved using the PTS field in the PES packet header. The PTS refers to the time of a specific event coded in the PES packet payload. The coded video elementary stream and the video frame synchronous subchannel share the same STC. A video frame synchronous subchannel is identified by the ITU-T\_data\_stream\_descriptor coded in the PSM/PSI tables, with the protocol parameter equal to video frame synchronous subchannel.
+
+The events and the coding of the events, are not specified here.
+
+## 18 Mode changing
+
+A change of an audio, video or data communications mode is performed using in-band or out-of-band subchannel signalling procedures. Mode changing is achieved by terminating communications on one subchannel and beginning communications in the new mode on another subchannel.
+
+## 19 Encryption
+
+For further study.
+
+## 20 H.222.1 demultiplexer errors
+
+At the H.222.1 receive side demultiplexer, it shall be possible to identify the error conditions shown in Table 16. These error conditions may be reported to some management entity for possible transmission to the send side H.222.1 peer.
+
+For the demultiplexer, subchannel establishment is deemed to have occurred when:
+
+- in the case of acknowledged subchannel signalling, when the receiver sends a positive acknowledgment signal to the transmitter that originated the subchannel establishment;
+- in the case of unacknowledged subchannel signalling, when the complete signalling information for that subchannel has been received at the receiver.
+
+TABLE 16/H.222.1
+
+### **H.222.1 receive side demultiplexer error conditions**
+
+| Error type                           | Error code | Comment                                                                   |
+|--------------------------------------|------------|---------------------------------------------------------------------------|
+| undefined multiplex identifier value | 0          | A subchannel has not been established for this multiplex identifier value |
+| stream type error                    | 1          | The stream type differs from that agreed to at subchannel establishment   |
+
+# **Appendix I**
+
+## **Recommended usage of H.222.0 descriptors**
+
+(This appendix does not form an integral part of this Recommendation)
+
+TABLE I.1/H.222.1
+
+## **Recommended usage of ITU-T defined H.222.0 descriptors**
+
+| Tag value | Descriptor                              | Program level | Elementary stream level |
+|-----------|-----------------------------------------|---------------|-------------------------|
+| 2         | video_stream_descriptor                 | .             | X                       |
+| 3         | audio_stream_descriptor                 | .             | X                       |
+| 4         | hierarchy_descriptor                    | .             | X                       |
+| 5         | registration_descriptor                 | NS            | NS                      |
+| 6         | data_stream_alignment_descriptor        | .             | X                       |
+| 7         | target_background_grid_descriptor       | .             | X                       |
+| 8         | video_window_descriptor                 | .             | X                       |
+| 9         | CA_descriptor                           | NS            | NS                      |
+| 10        | ISO_639_language_descriptor             | .             | X                       |
+| 11        | system_clock_descriptor                 | X             | .                       |
+| 12        | multiplex_buffer_utilization_descriptor | .             | X                       |
+| 13        | copyright_descriptor                    | X             | X                       |
+| 14        | maximum_bitrate_descriptor              | X             | X                       |
+| 15        | private_data_indicator_descriptor       | NS            | NS                      |
+| 16        | smoothing_buffer_descriptor             | X             | X                       |
+| 17        | STD_descriptor                          | .             | X                       |
+| 18        | IBP_descriptor                          | .             | X                       |
+
+NS Not specified in this appendix  
+X Presence of the descriptor is permitted  
+. Presence of the descriptor is not recommended
+
+# Appendix II
+
+## ITU-T Timing Descriptor usage
+
+(This appendix does not form an integral part of this Recommendation)
+
+In severely jittered or highly lossy networks, timing recovery may be problematic in inexpensive implementations that cannot afford highly stable crystal clocks. Often the encoders can provide information as to which parts of the data stream may be useful for recovering the decoder System Time Clock (STC) frequency and phase. Such information is specified in the ITU-T Timing Descriptor.
+
+The descriptor specifies that one or more data rates are locked to the encoder STC and can be used, for example, in an Adaptive Clock Recovery (ACR) scheme at the decoder. The size of the assumed buffer in the ACR is implementation dependent and will depend on how much jitter is encountered during transmission. The jitter may or may not include multiplexing jitter. If it does, then the assumed ACR buffer will probably be larger.
+
+In an ITU-T H.222.0 multiplexed bit stream, the encoder periodically sends samples of its time clock, which are called Clock References. We denote these Encoder Clock References by PCR. Typically, the PCRs are sent at the rate of a few per second.
+
+With very low jitter, recovery of the time clock at the decoder relies on averaging the jitter effects over many received PCR values. However, in cases of extreme jitter, thousands of PCR values may be needed before high stability operation is achieved, which may require dozens of seconds. In many applications this is unacceptable.
+
+However, if the ITU-T Timing Descriptor specifies an SC\_TSPktR value, then additional synthetic PCRs can be calculated for each ensuing TS packet simply by adding SC\_TSPktR for each TS packet received. Timing recovery is speeded up considerably by using these synthetic PCRs.
\ No newline at end of file
diff --git a/marked/H/T-REC-H.235.1-200509-I_PDF-E/raw.md b/marked/H/T-REC-H.235.1-200509-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..405a0b68abca5c8700efec03bf3b0a9abb54830b
--- /dev/null
+++ b/marked/H/T-REC-H.235.1-200509-I_PDF-E/raw.md
@@ -0,0 +1,690 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.235.1**
+
+(09/2005)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS  
+Infrastructure of audiovisual services – Systems aspects
+
+---
+
+**H.323 security: Baseline security profile**
+
+ITU-T Recommendation H.235.1
+
+ITU-T
+
+![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg)
+
+The logo of the International Telecommunication Union (ITU) features a stylized 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 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        |
+| <b>Systems aspects</b>                                                        | <b>H.230–H.239</b> |
+| 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.1**
+
+## **H.323 security: Baseline security profile**
+
+### **Summary**
+
+This Recommendation provides authentication and integrity protection, or authentication-only for H.225.0 RAS and call signalling, H.225.0, and tunnelled H.245 using password-based HMAC-SHA1-96 hash protection of H.225.0 RAS and Call Signalling messages by using secure password-based cryptographic techniques. The security profile is applicable to H.323 terminal-to-gatekeeper, gatekeeper-to-gatekeeper, H.323 gateway-to-gatekeeper and to other H.323 entities in administered environments with symmetric assigned keys/passwords.
+
+In earlier versions of the H.235 subseries, this profile was contained in Annex D/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.1 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 .....                                                            | 2  |
+| 5    | Conventions .....                                                                          | 3  |
+| 6    | Overview .....                                                                             | 5  |
+| 6.1  | Summary of security features.....                                                          | 5  |
+| 6.2  | Applicability of the baseline security profile .....                                       | 6  |
+| 6.3  | H.323 requirements .....                                                                   | 7  |
+| 6.4  | Overview of procedures .....                                                               | 7  |
+| 7    | Symmetric-key-based signalling message authentication and integrity<br>(procedure I) ..... | 7  |
+| 7.1  | Computation of the password-based hash .....                                               | 9  |
+| 7.2  | HMAC-SHA1-96 .....                                                                         | 9  |
+| 7.3  | Computation and verification of authentication and integrity.....                          | 9  |
+| 8    | Authentication-only (procedure IA) .....                                                   | 10 |
+| 9    | Usage illustration for procedure I .....                                                   | 11 |
+| 9.1  | RAS message authentication and integrity.....                                              | 13 |
+| 9.2  | H.225.0 message authentication and integrity.....                                          | 13 |
+| 9.3  | H.245 message authentication and integrity.....                                            | 14 |
+| 9.4  | Direct-routed scenario .....                                                               | 15 |
+| 10   | Back-end-service support .....                                                             | 15 |
+| 11   | H.235 version 1 compatibility .....                                                        | 15 |
+| 12   | Multicast behaviour .....                                                                  | 15 |
+| 13   | List of secured signalling messages.....                                                   | 15 |
+| 13.1 | H.225.0 RAS .....                                                                          | 15 |
+| 13.2 | H.225.0 call signalling.....                                                               | 15 |
+| 13.3 | H.245 call control .....                                                                   | 16 |
+| 14   | Usage of sendersID and generalID .....                                                     | 16 |
+| 15   | List of object identifiers.....                                                            | 17 |
+
+
+
+## H.323 Security: Baseline security profile
+
+### 1 Scope
+
+This Recommendation provides authentication and integrity protection, or authentication-only for H.225.0 RAS and call signalling, H.225.0 and tunnelled H.245 messages using password-based HMAC-SHA1-96 hash protection of H.225.0 RAS and Call Signalling messages by using secure password-based cryptographic techniques. The security profile is applicable to H.323 terminal-to-gatekeeper, gatekeeper-to-gatekeeper, H.323 gateway-to-gatekeeper and to other H.323 entities.
+
+### 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.2 (2005), *H.323 security: Signature security profile*.
+- ITU-T Recommendation H.235.4 (2005), *H.323 security: Direct and selective routed call security*.
+- 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 version 10 (2003), *Control protocol for multimedia communication*.
+- ITU-T Recommendation H.323 (2003), *Packet-based multimedia communications systems*.
+- ITU-T Recommendation H.323 Annex F (1999), *Simple endpoint types*.
+- ITU-T Recommendation Q.931 (1998), *ISDN user-network interface layer 3 specification for basic call control*.
+- 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*.
+
+- 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 10118-3:2004, *Information Technology – Security techniques – Hash-functions – Part 3: Dedicated hash-functions*.
+
+### 2.2 Informative references
+
+- [FIPSPUB180-2] 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.
+- [OIW] Stable Implementation – Agreements for Open Systems Interconnection Protocols: Part 12 – OS Security; Output from the December 1994 Open Systems Environment Implementors' Workshop (OIW);  
+[http://nemo.ncsl.nist.gov/oiw/agreements/stable/OSI/12s\\_9412.txt](http://nemo.ncsl.nist.gov/oiw/agreements/stable/OSI/12s_9412.txt).
+- [RFC2104] IETF RFC 2104 (1997), *HMAC: Keyed-Hashing for Message Authentication*.
+- [WEB0IDs] <http://www.alvestrand.no/objectid/top.html>.
+
+### 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 as defined in ITU-T Recs X.800 | ISO/IEC 7498-2, X.803 | ISO/IEC 10745, X.810 | ISO/IEC 10181-1 and X.811 | ISO/IEC 10181-2.
+
+This Recommendation uses the following terms for provisioning the security services.
+
+**3.1 authentication and integrity:** This is a combined security service part of the baseline profile that supports message integrity in conjunction with user authentication. The user may ensure authentication by correctly applying a shared secret key procedure. Both security services are provided by the same security mechanism.
+
+**3.2 authentication-only:** This security service offered by the baseline security profile as an option supports authentication of selected fields only, but does not provide full message integrity. The authentication-only security profile is applicable for signalling messages traversing NAT/firewall devices. The user may ensure authentication by correctly applying a shared secret key procedure.
+
+When using symmetric key techniques, the security services authentication/integrity only apply on a hop-by-hop basis.
+
+### 4 Symbols and abbreviations
+
+This Recommendation uses the following abbreviations:
+
+|       |                              |
+|-------|------------------------------|
+| ASN.1 | Abstract Syntax Notation One |
+| EP    | Endpoint                     |
+| EPID  | Endpoint Identifier          |
+
+|      |                                       |
+|------|---------------------------------------|
+| GK   | Gatekeeper                            |
+| GKID | Gatekeeper Identifier                 |
+| GRQ  | Gatekeeper Request                    |
+| HMAC | Hashed Message Authentication Code    |
+| ICV  | Integrity Check Value                 |
+| ITU  | International Telecommunication Union |
+| LRQ  | Location Request                      |
+| MAC  | Message Authentication Code           |
+| NAT  | Network Address Translation           |
+| OID  | Object Identifier                     |
+| RAS  | Registration, Admission and Status    |
+| RTP  | Real-Time Protocol                    |
+| SHA  | Secure Hash Algorithm                 |
+| TCP  | Transmission Control Protocol         |
+| UTC  | Universal Time Clock                  |
+| 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.
+
+This Recommendation defines a **baseline security profile**. The baseline security profile provides basic security by simple means using secure password-based cryptographic techniques. The baseline security profile may be used in conjunction with the security profiles such as H.235.3, H.235.4, H.235.5, H.235.6 and H.235.7.
+
+This Recommendation uses H.235 fields for provisioning authentication/integrity security services upon H.323 signalling messages. Different object identifiers (see clause 15) determine which security service is actually selected and which protocol version of this Recommendation is being used. Procedure I specifies how to implement the security services by certain security mechanisms such as symmetric (keyed hashing) techniques. The object identifiers are referenced through a symbolic reference in the text (e.g., "A"), see also clause 5/H.235.0.
+
+While the message integrity service also always provides message authentication, the reverse is not always true. In practice, combined authentication and integrity service exploit the same key material without introducing a security weakness.
+
+Moreover, all hop-by-hop security information is put into the **CryptoHashedToken** element. This information is re-computed at every hop.
+
+This Recommendation applies certain symmetric cryptographic techniques for the purpose of authentication and integrity. This text uses the term password and shared secret when applying symmetric techniques.
+
+Generally, what password, session key and shared secret all have in common is that they are used in symmetric cryptography among two (or more) entities. The difference between a password and a session key/shared secret is how the keys are actually applied, e.g., passwords for authentication and authorization, session keys for encryption. The term "shared secret" is kind of neutral as it does not actually refer to any specific usage.
+
+The **password** (could be viewed also as a shared secret) is used for the authentication/integrity for RAS and H.225.0, as this item could be entered by the user. A password typically is an alphanumeric character string that users can memorize. The password usually has a longer-term lifetime; the password is known *a priori* and may be defined as part of the overall user subscription process. Some algorithm (e.g., piping the password through a hash algorithm) may transform the password for more convenient processing in the protocols in order to result in a fixed length.
+
+It is obvious that using passwords should be done with care. Passwords are able to provide sufficient security only when they are chosen randomly from a large space, when they convey sufficient entropy such that they are unpredictable and when they are changed periodically. Rules for setting up and maintaining passwords do not fall within the scope of this Recommendation.
+
+A good practice as to how to deploy the benefits from passwords and shared secrets is to transform the user password string into a fixed bit string as the shared secret using a cryptographically strong one-way hash function.
+
+As a recommended example, when using the security profile of this Recommendation, the SHA1 when applied to the password string, yields to a 20-byte shared secret. An advantage is that the hashed result does not only conceal the actual password, but also defines a fixed length bit string format without really sacrificing entropy.
+
+Thus,
+
+shared secret := SHA1 (password)
+
+The H.235 **ClearToken** offers a field called **random** holding a 32-bit integer. This field is used in the following sense: **random** is actually a monotonically increasing number starting at any value and increasing with every outgoing message. The **random** field is used as an additional "randomization" value for input to the keyed-hashed function in the case when several messages are issued shortly one after another, yet convey identical timestamps. This could happen when the UTC clock does not provide sufficient clock resolution. In essence, the produced hash value or integrity check value look different due to the changing **random** value. This is to counter replay attacks. For implementation simplicity, an increasing counter is preferred over a truly random sequence here. The recipient may keep received **timestamp/random** pairs during the period defined by a local time window. Replay attacks can be identified when the same **timestamp/random** pair occurs twice.
+
+NOTE – The time window compensates for variances of the synchronized time and for the network transit delay.
+
+This profile defines to "set the **generalID** in the **ClearToken** to the identifier of the recipient". This actually means that, for RAS messages destined for the gatekeeper, this is the GK identifier; for RAS messages destined for the endpoint, this is the endpoint identifier, for H.225.0 call signalling messages destined for the gatekeeper, this is the GK identifier and for H.225.0 call signalling messages destined for the endpoint, this is the called endpoint identifier, see also clause 14.
+
+The **sendersID** shall be set to the identification string of the sender. This actually means that for RAS messages destined for the gatekeeper, this is the endpoint identifier; for RAS messages destined for the endpoint this is the gatekeeper, identifier; for H.225.0 call signalling messages destined for the gatekeeper, this is the GK identifier and for H.225.0 call signalling messages destined for the endpoint, this is the called endpoint identifier, see also clause 14.
+
+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.
+
+This Recommendation uses well-known security terms such as key, key management and SET, which have different meanings in other contexts (e.g., touch key pad, Q.931/Q.932 feature key management, and Secure Electronic Transaction protocol).
+
+## 6 Overview
+
+This Recommendation provides authentication and integrity protection, or authentication-only for H.225.0 RAS and call signalling, H.225.0 and tunnelled H.245 messages using password-based HMAC-SHA1-96 hash protection of H.225.0 RAS and Call Signalling messages by using secure password-based cryptographic techniques. The security profile is applicable to H.323 terminal-to-gatekeeper, gatekeeper-to-gatekeeper, H.323 gateway-to-gatekeeper and to other H.323 entities in administered environments with symmetric keys/passwords assigned.
+
+### 6.1 Summary of security features
+
+The features provided by these profiles include:
+
+- for RAS, H.225.0 and tunnelled H.245 messages:
+  - User authentication to a desired entity irrespective of the number of application level hops that the message traverses.  
+NOTE – 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 the signalling message itself, including the critical portions (fields) of messages arriving at an entity irrespective of the number of application level hops that the message traverses.
+  - Application level hop-by-hop signalling message authentication and integrity provides these security services for the entire message.
+
+Several attacks are thwarted by providing the above security services in a suitable fashion. These include:
+
+- Denial-of-service attacks: Rapid checking of cryptographic hash values 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.
+- 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.
+
+Other highlights of the simple security profile include:
+
+- Use of robust, well-known and widely deployed algorithms based on IMTC/ETSI/IETF material.
+- Capability of deployment in stages based on the security requirement of the business model.
+- Applicability to various deployment scenarios such as in closed groups and for scaleable environments and in multipoint conferences.
+
+- The authentication-only security profile is applicable when providing some security for NAT/firewall traversal.
+
+Table 1 summarizes all the procedures defined in this Recommendation by the security profiles dealing with different security requirements. The optional authentication-only security profile is shown as diagonal shading – blue in the electronic copy.
+
+**Table 1/H.235.1 – Baseline security profile**
+
+| Security services                                                     | Call functions                         |                          |                          |     |
+|-----------------------------------------------------------------------|----------------------------------------|--------------------------|--------------------------|-----|
+|                                                                       | RAS                                    | H.225.0                  | H.245 (Note)             | RTP |
+| Authentication                                                        | Password<br>HMAC-SHA1-96               | Password<br>HMAC-SHA1-96 | Password<br>HMAC-SHA1-96 |     |
+| Authentication-only                                                   | Password<br>HMAC-SHA1-96               | Password<br>HMAC-SHA1-96 | Password<br>HMAC-SHA1-96 |     |
+| Non-repudiation                                                       |                                        |                          |                          |     |
+| Integrity                                                             | Password<br>HMAC-SHA1-96               | Password<br>HMAC-SHA1-96 | Password<br>HMAC-SHA1-96 |     |
+| Confidentiality                                                       |                                        |                          |                          |     |
+| Access control                                                        |                                        |                          |                          |     |
+| Key management                                                        | Subscription-based password assignment |                          |                          |     |
+| NOTE – Tunnelled H.245 or embedded H.245 inside H.225.0 fast connect. |                                        |                          |                          |     |
+
+For authentication, the user shall use a password-based scheme. The password-based scheme is highly recommended for authentication due to its simplicity and ease of implementation. Hashing all the fields in the H.225.0 RAS and call signalling messages is the recommended approach for integrity of the messages (also using the password scheme).
+
+Secure H.323 entities with this security profile realize authentication in conjunction with integrity using the same common security mechanism.
+
+Access control means are not explicitly described; they can be implemented locally upon the received information conveyed within H.235 signalling fields (ClearToken, CryptoToken).
+
+This Recommendation does not describe procedures for subscription-based password/secret key assignment with management and administration. Such procedures may take place by means that are beyond the scope of this Recommendation.
+
+The communication entities involved are able to implicitly determine usage of either the baseline security or the signature security profile by evaluating the signalled security object identifiers in the messages (**tokenOID**, and **algorithmOID**; see also clause 15).
+
+### 6.2 Applicability of the baseline security profile
+
+The baseline security profile is applicable in an environment where subscribed passwords/symmetric keys can be assigned to the secured H.323 entities (terminals) and network elements (GKs, proxies). It provides authentication and integrity, or authentication-only for H.225.0 RAS and call signalling, H.225.0 and tunnelled H.245 using password-based HMAC-SHA1-96 hash as specified by procedure I. H.225.0 call establishment using FastStart (GK-to-GK or terminal-to-terminal) includes integrated key management with Diffie-Hellman.
+
+The baseline security profile mandates the fast connect procedure and recommends to use H.245 tunnelling within H.225.0
+
+### 6.3 H.323 requirements
+
+H.323 entities that implement this baseline security profile are assumed to support the following H.323 features:
+
+- Fast connect;
+- GK-routed model.
+
+### 6.4 Overview of procedures
+
+The following procedure is described for use in this profile.
+
+Procedure I is a simple symmetric-key-based signalling message authentication mechanism based on a shared password between two entities (e.g., Gatekeeper and H.323 endpoint). This procedure provides authentication and integrity of the RAS, Q.931 and H.245 messages (see clause 7).
+
+Procedure IA is a simple symmetric-key-based authentication-only mechanism based on a shared password between two entities (e.g., Gatekeeper and H.323 endpoint). This procedure provides only authentication but does not provide full message integrity. The authentication-only option is applicable in scenarios where H.323 signalling messages traverse NATs/firewalls.
+
+Depending on the security policy, authentication may be unilateral or mutual by applying the authentication/integrity in the reverse direction as well and thereby providing higher security. The Gatekeeper decides whether to apply authentication/integrity in the reverse direction as well.
+
+Gatekeepers detecting failed authentication and/or failed integrity validation in a RAS or Call signalling message received from a secured endpoint or 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**) may respond with an unsecured **xRJ** and reject with reason set to **securityDenial**, or it 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**) may respond with an unsecured RELEASE COMPLETE and reject 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 I and the applied security mechanism, based upon the value of the object identifiers (see also clause 15) and the message fields filled in.
+
+This profile does not use the H.235 ICV fields; rather cryptographic integrity check values are treated as cryptographic hash values and are put into the hash fields of the **CryptoToken**.
+
+## 7 Symmetric-key-based signalling message authentication and integrity (procedure I)
+
+The procedures below shall be followed when procedure I is employed:
+
+- The HMAC-SHA1-96 algorithm generates a 12-byte (96-bit) hash value as the resulting authenticator. If the key is generated from a password, the mechanism described in 8.2.4/H.235.0 *shall* be used for computing the key from the password.
+
+NOTE 1 – When the secret key is derived from a user-entered password, care should be taken to ensure sufficient randomness. It is recommended, for example, to use truly random secrets for the secret key, or to ensure that random passwords are sufficiently long.
+
+- The **CryptoH323Token** field in each RAS/H.225.0 message shall contain the following fields:
+
+- **nestedCryptoToken** containing a **CryptoToken** which itself contains the **cryptoHashedToken** containing the following fields:
+    - **tokenOID** set to "A", indicating that the authentication/integrity computation includes all fields in the H.225.0 RAS and call signalling message.
+    - **hashedVals** containing the **ClearToken** field used with the following fields:
+      - **tokenOID** set to "T", indicating that the baseline **ClearToken** as shown below is being used for message authentication and replay protection and optionally also for Diffie-Hellman key management as described in 8.5/H.235.6. Alternatively, other ClearTokens with other OIDs may be used in place of the baseline ClearToken.
+      - **timeStamp** contains the timestamp.
+      - **random** contains a monotonically increasing sequence number. This number allows the construction of two messages with the same timestamp (within the clock resolution).
+      - **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 2 – When the baseline 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}.
+- **token** containing **HASHED** with the fields:
+    - **algorithmOID** set to "U" indicating the use of HMAC-SHA1-96.
+    - **params** set to NULL.
+    - **hash** containing the authenticator computed using HMAC-SHA1-96. The authenticator can be computed over:
+      - all the H.225.0 RAS and call signalling fields of the message if **tokenOID** in the **CryptoHashedToken** is set to "A" (indicating authentication and integrity).
+
+**tokenOID** "A" is used for protection of tunnelled H323-UU-PDUs including all H.245 message contents; the hash computation shall be done over the entire **H.225.0** call signalling message with all fields according to the procedure described in 7.3.
+
+- The authenticator is verified at the end of each channel terminating leg (EP1-GK1, GK1-GK2, GK2-EP2, EP1-GK2, GK1-EP2 or EP1-EP2 as the case may be), and recomputed prior to sending the message out on the subsequent leg.
+
+NOTE 3 – The authenticator is computed on a per-message basis.
+
+NOTE 4 – The padding method within the SHA1 standard (ISO/IEC 10118-3) shall be used.
+
+NOTE 5 – When the combined authentication and integrity is being used, the authenticator is computed over the entire message.
+
+NOTE 6 – In order to prevent the possibility of replay attacks, it is highly recommended that implementations ensure that the password (key) is changed prior to a turn-around (or cycle completion) of the monotonically increasing sequence number.
+
+NOTE 7 – The recipient is able to detect usage of procedure I by evaluating the **tokenOID** within the hashed **EncodedGeneralToken** (detecting presence of "A").
+
+### 7.1 Computation of the password-based hash
+
+Both sender and receiver of an authenticated/integrity protected message compute a keyed hash over all the ASN.1-coded message fields (using OID "A"). For the authentication-only profile, both sender and receiver compute a keyed hash over all the ASN.1 coded ClearToken (using OID "B").
+
+### 7.2 HMAC-SHA1-96
+
+HMAC-SHA1-96 is the truncated 96-bit cryptographic hash value of the 160-bit SHA1 computation. The 96 leftmost bits of the network byte order representation of the hash value shall be used as the result. RFC 2104 describes the procedure with the secret key *K* set to the shared secret (= SHA1-hashed password) and *text* set to the message buffer.
+
+### 7.3 Computation and verification of authentication and integrity
+
+For authentication and message integrity (in case OID "A" is applied), the procedure is as follows.
+
+The sender of a message shall compute the hash as follows:
+
+- 1) Set the hash value to a specific default pattern with a length of 96 bits. The exact bit pattern does not matter, but a good choice is a unique bit pattern that does not occur in the remaining message.
+- 2) ASN.1 – encode 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 96 zero bits.
+
+NOTE 1 – This location 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 cryptographic hash value upon the ASN.1 encoded message using HMAC-SHA1-96 (see 7.2).
+- 5) Substitute the default pattern in the encoded message with the computed hash value.
+
+The recipient receives the message and then proceeds as follows:
+
+- 1) ASN.1 – decode the message.
+- 2) Extract the received hash value and keep it in a local variable RV.
+- 3) Search and locate the hash value RV in the received encoded message.
+
+NOTE 2 – In rare circumstances where the hash 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 96 zeros.
+- 5) Compute the cryptographic hash value upon the encoded message using HMAC-SHA1-96 (see clause 7.2).
+- 6) Compare RV with the computed hash value. The message is considered uncorrupted only if both hash values are equal; in this case, the authentication is successful and the procedure stops.
+- 7) Otherwise, repeat steps 3-7 by restoring RV to the previous location and search for another match. If none of the matches yield a correct hash value comparison, then the authentication has failed and the message has been altered (accidentally or intentionally) during transit.
+
+### 8 Authentication-only (procedure IA)
+
+Terminals may choose to implement authentication-only (using OID "B", see clause 20/H.235.2). 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 traversing NAT/firewalls that change IP addresses/ports within the H.323 payloads.
+
+Since the authentication spans only a very limited portion of the message, authentication-only does not provide message integrity as procedure I features. Thus, authentication-only provides less security.
+
+For authentication-only, the following fields shall be used in the protected messages:
+
+- The **CryptoH323Token** field in each RAS/H.225.0 message shall contain the following fields:
+    - **nestedCryptoToken** containing a **CryptoToken** which itself contains the **cryptoHashedToken** containing the following fields:
+      - **tokenOID** set to:
+        - "B" (see clause 20/H.235.2) indicating that the authentication-only computation includes all fields in the **ClearToken**.
+      - **hashedVals** containing the **ClearToken** field used with the following fields:
+        - **tokenOID** set to:
+          - "T" (as the baseline ClearToken example for the remainder of ClearToken contents) or any suitable OID for any other purposes.
+        - **timeStamp** contains the timestamp;
+        - **random** contains a monotonically increasing sequence number. This number allows making two messages with the same timestamp (within the clock resolution) unique;
+        - **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 ITU-T Rec. H.235.0 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).
+- **token** containing **HASHED** with the fields:
+  - **algorithmOID** set to "U" indicating the use of HMAC-SHA1-96;
+  - **params** set to NULL;
+  - **hash** containing the authenticator computed using HMAC-SHA1-96. The authenticator shall be computed over:
+    - all the fields of the **ClearToken** if **tokenOID** in the **CryptoHashedToken** is set to "B" (indicating authentication-only).
+
+NOTE 1 – When the baseline 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'}.
+
+NOTE 2 – The authenticator is computed just on the **ClearToken**.
+
+NOTE 3 – The padding method within the SHA1 standard (ISO/IEC 10118-3) shall be used.
+
+NOTE 4 – In order to prevent the possibility of replay attacks, it is highly recommended that implementations ensure that the password (key) is changed prior to a turn-around (or cycle completion) of the monotonically increasing sequence number.
+
+NOTE 5 – The recipient is able to detect usage of procedure IA by evaluating the **OID** "B" within the **tokenOID**.
+
+The authenticator shall be computed just over the **ClearToken** inside the **CryptoH323Token** (i.e., **ClearToken**) of the **token** of the **cryptoHashedToken**. The cryptographic hash shall be computed over the ASN.1 encoded bitstring of **ClearToken**.
+
+H.235 version 1 and version 2 endpoints may use authentication-only, in which case the corresponding OIDs for "B" shall be used. H.235 version 1 endpoints shall adhere to the procedure described in clause 11.
+
+### 9 Usage illustration for procedure I
+
+Figures 1 through 3 depict the presence of shared keys at the end of communicating channels for the different combinations of gatekeeper and direct-routed H.225.0 channels. Irrespective of the call model, a secret key is always present between an EP and its GK in order to provide for RAS message authentication and integrity. When a RAS channel and an H.225.0 channel terminate between the same two nodes, the same key may be used to provide authentication and integrity for both RAS and H.225.0 messages.
+
+Figure 1 shows the most scaleable scenario where both endpoints are within zones that apply the GK-routed model. All the involved GKs share keys mutually. In order to be scaleable, the scenario depicted in Figure 1 is recommended.
+
+NOTE 1 – This scenario does not provide true end-to-end security between endpoints; all security depends on the trusted intermediate gatekeepers.
+
+![Diagram illustrating procedure I usage in a GK-GK scenario with both EPs in GK-routed zones. Two zones are shown, each containing an Endpoint (EP) and a Gatekeeper (GK). EP1 is connected to GK1, and EP2 is connected to GK2. GK1 and GK2 are connected to each other. Key1 is shared between EP1 and GK1. Key2 is shared between GK1 and GK2. Key3 is shared between GK2 and EP2. The legend indicates that dashed lines represent H.225.0 RAS and solid lines represent H.225.0 Call Signalling.](90ee16ccc0ad16aeca48087797d7b07f_img.jpg)
+
+The diagram shows two zones, each represented by a large oval. The left zone contains an endpoint labeled EP1 and a gatekeeper labeled GK1. A dashed double-headed arrow labeled 'Key1' connects EP1 and GK1. The right zone contains a gatekeeper labeled GK2 and an endpoint labeled EP2. A dashed double-headed arrow labeled 'Key3' connects GK2 and EP2. A solid horizontal line labeled 'Key2' connects GK1 and GK2. A legend at the bottom left shows a dashed line labeled 'H.225.0 RAS' and a solid line labeled 'H.225.0 Call Signalling'. The label 'H.235.1\_F01' is in the bottom right corner.
+
+Diagram illustrating procedure I usage in a GK-GK scenario with both EPs in GK-routed zones. Two zones are shown, each containing an Endpoint (EP) and a Gatekeeper (GK). EP1 is connected to GK1, and EP2 is connected to GK2. GK1 and GK2 are connected to each other. Key1 is shared between EP1 and GK1. Key2 is shared between GK1 and GK2. Key3 is shared between GK2 and EP2. The legend indicates that dashed lines represent H.225.0 RAS and solid lines represent H.225.0 Call Signalling.
+
+**Figure 1/H.235.1 – Illustrating procedure I usage in a GK-GK scenario with both EPs in GK-routed zones**
+
+Figure 2 shows a mixed scenario where one EP is within a zone applying the GK-routed model while the other EP is in a zone applying the direct-routed model. This scenario could occur in closed environments where the number of EP2s and GK1s is limited.
+
+![Figure 2/H.235.1: Illustrating procedure I usage in a mixed scenario with EP1 in a GK-routed zone and EP2 in a direct-routed zone. The diagram shows two zones represented by large ovals. The left zone contains EP1 and GK1. The right zone contains GK2 and EP2. A dashed line (H.225.0 RAS) labeled Key1 connects EP1 and GK1. A solid line (H.225.0 Call Signalling) labeled Key2 connects GK1 and GK2. A dashed line (H.225.0 RAS) labeled Key3 connects GK2 and EP2. Small rectangles represent keys near the Gatekeepers (GK1, GK2).](76b0cd79baaedd942af4dc42f2e764b8_img.jpg)
+
+H.225.0 RAS  
+ H.225.0 Call Signalling
+
+Figure 2/H.235.1: Illustrating procedure I usage in a mixed scenario with EP1 in a GK-routed zone and EP2 in a direct-routed zone. The diagram shows two zones represented by large ovals. The left zone contains EP1 and GK1. The right zone contains GK2 and EP2. A dashed line (H.225.0 RAS) labeled Key1 connects EP1 and GK1. A solid line (H.225.0 Call Signalling) labeled Key2 connects GK1 and GK2. A dashed line (H.225.0 RAS) labeled Key3 connects GK2 and EP2. Small rectangles represent keys near the Gatekeepers (GK1, GK2).
+
+**Figure 2/H.235.1 – Illustrating procedure I usage in a mixed scenario  
+with EP1 in a GK-routed zone and EP2 in a direct-routed zone**
+
+Figure 3 shows a scenario where both EPs are within zones applying the direct-routed GK model. This scenario is not very scaleable when many EPs are involved. In principle, usage of H.235.2 with procedures II/III is recommended instead. For this specific scenario and procedures I, II or III additional security measures (protecting against call fraud and misuse by means of call authorization with access tokens at H.323 gateways for example), which are not described in this Recommendation, are necessary as well; this is for further study.
+
+NOTE 2 – This scenario provides true end-to-end security among endpoints without relying on trusted intermediate nodes.
+
+![Figure 3/H.235.1: Illustrating procedure I usage in a scenario with both EPs in zones using a direct-routed GK. The diagram shows two zones represented by large ovals. The left zone contains EP1 and GK1. The right zone contains GK2 and EP2. A dashed line (H.225.0 RAS) labeled Key1 connects EP1 and GK1. A solid line (H.225.0 Call Signalling) labeled Key2 connects EP1 and EP2 directly across the zone boundaries. A dashed line (H.225.0 RAS) labeled Key3 connects GK2 and EP2. Small rectangles represent keys near the Gatekeepers (GK1, GK2).](9b9d2abd741ed4bafe7f78f89961c663_img.jpg)
+
+H.225.0 RAS  
+ H.225.0 Call Signalling
+
+Figure 3/H.235.1: Illustrating procedure I usage in a scenario with both EPs in zones using a direct-routed GK. The diagram shows two zones represented by large ovals. The left zone contains EP1 and GK1. The right zone contains GK2 and EP2. A dashed line (H.225.0 RAS) labeled Key1 connects EP1 and GK1. A solid line (H.225.0 Call Signalling) labeled Key2 connects EP1 and EP2 directly across the zone boundaries. A dashed line (H.225.0 RAS) labeled Key3 connects GK2 and EP2. Small rectangles represent keys near the Gatekeepers (GK1, GK2).
+
+**Figure 3/H.235.1 – Illustrating procedure I usage in a scenario  
+with both EPs in zones using a direct-routed GK**
+
+Consider the case in Figure 1 where three passwords are pair-wise shared between EP1-GK1, between GK1-GK2 and between GK2-EP2. Three 20-byte keys – *Key1*, *Key2* and *Key3* – are generated from these passwords based on the procedure described in 8.2.4/H.235.0. For maximum security, it is recommended to make each of the three random passwords/keys independent.
+
+Below, we illustrate the procedure details for RAS, H.225.0 and H.245 message authentication and integrity. The description example depicts specific parameters in a GK-routed model; other useful and valid combinations of object identifiers in different scenarios are possible as well.
+
+NOTE 3 – The scenarios shown in Figures 1 to 3 do not scale well in the case where the number of shared symmetric keys (passwords) between GKs (Figure 1), between GKs and remote EPs (Figure 2), or between the EPs (Figure 3) becomes too large.
+
+### 9.1 RAS message authentication and integrity
+
+Consider the case where EP1 wishes to send an 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 GK1's alias in the **generalID** and the EP's ID in the **sendersID** field. These fields are present in the **ClearToken** field of **hashedVals** present in the **cryptoHashedToken** of the **CryptoToken** field of the **cryptoH323Token** of the **ARQ** message.
+
+The **tokenOID** within the **cryptoHashedToken** is set to "A", indicating that all the fields in the **ARQ** message are hashed. The **HASHED** within **token** in **cryptoHashedToken** has **algorithmOID** set to "U" indicating the use of HMAC-SHA1-96 and **params** set to NULL. EP1 then computes the authenticator based on the HMAC-SHA1-96 using the 20-byte key *Key1*. The authenticator is computed over the entire RAS message.
+
+EP1 includes the computed authenticator within **hash** in the **token** field of the **cryptoHashedToken** field of the **CryptoToken** present in the **cryptoH323Token** of the **ARQ** message. The **ARQ** message is then sent to GK1.
+
+Upon receiving the **ARQ** message, GK1 verifies the authenticator based on several criteria that include:
+
+- liveness of the **timestamp**, uniqueness of the **random**;
+- identity of the **generalID** and own identifier;
+- matching of authenticator in **ARQ** message with that computed by GK1.
+
+### 9.2 H.225.0 message authentication and integrity
+
+Consider the case where EP1 wishes to send an H.225.0 message, say a **Setup** message, to EP2. EP1 generates a timestamp and a sequence number and includes it in the **timeStamp** and **random** fields respectively, along with GK1's alias in the **generalID** and the EP's ID in the **sendersID** field. EP1 computes also a Diffie-Hellman half-key and includes the Diffie-Hellman parameters **halfkey**, **modsize** and **generator** in the **dhkey** field of the **ClearToken**. These fields are present in the **ClearToken** field of **hashedVals** present in the **cryptoHashedToken** of the **CryptoToken** field of the **cryptoH323Token** of the **Setup** message.
+
+The **tokenOID** within the **cryptoHashedToken** is set to "A", indicating that all the fields in the H.225.0 call signalling message are hashed. The **HASHED** within **token** in **cryptoHashedToken** has **algorithmOID** set to "U" indicating the use of HMAC-SHA1-96 and **params** set to NULL. EP1 then computes the authenticator based on the HMAC-SHA1 algorithm using the 20-byte key *Key1*. The authenticator is computed according to the hash method chosen (A) taking into account the entire H.225.0 call signalling message.
+
+EP1 includes the computed authenticator within **hash** in the **token** field of the **cryptoHashedToken** field of the **CryptoToken** present in the **cryptoH323Token** of the **Setup** message. The **Setup** message is then sent to GK1.
+
+Upon receiving the **Setup** message, GK1 verifies the authenticator based on several criteria that include:
+
+- liveness of the **timestamp**, uniqueness of the **random**;
+- identity of the **generalID** and own identifier;
+- 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;
+- matching of authenticator in **Setup** message with that computed by GK1.
+
+If the authenticator is successfully verified, GK1 computes a new authenticator to insert (replace) in the **Setup** message before forwarding it to GK2 as follows. GK1 replaces the **timeStamp**, **random**, **sendersID** and **generalID** fields in the **ClearToken** field of **hashedVals** using values relevant to the GK1-GK2 leg. The **timestamp** field contains the current timestamp, the **random** field contains the next monotonically increasing sequence number for the GK1-GK2 leg, the **generalID** field contains the alias of GK2 and the **sendersID** contains the alias of GK1. GK1 includes also the received Diffie-Hellman parameters into the **dhkey** field of the **ClearToken**.
+
+GK1 then computes a new authenticator for this H.225.0 call signalling message using key **Key2** and algorithm HMAC-SHA1-96 (**algorithmOID="U"**), inserts it in **hash** within **token** and passes the **Setup** message on to GK2.
+
+Upon receiving the **Setup** message, GK2 verifies the authenticator, computes a new authenticator after modifying the **ClearToken** fields in **hashedVals** suitably, inserts it in the **hash** field and passes the **Setup** message on to EP2.
+
+### 9.3 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 GK1. 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 an H.225.0 message. Since the H.245 message is tunnelled, the **h323-uu-pdu** in the **h323-UserInformation** 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.
+
+EP1 generates a **CryptoToken** for the H.225.0 message, sets **tokenOID** to "A", indicating authentication and integrity, sets **timeStamp**, **random**, **sendersID**, **generalID** and **tokenOID** to "T" in the **ClearToken** of the **hashedVals**, set **algorithmOID** to "U", indicating the use of HMAC-SHA1-96 and **hash** to the computed hash authenticator over all the fields of the H.225.0 call signalling message.
+
+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-UserInformation** 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.
+
+As described above, EP1 generates a **CryptoToken** as part of the H.225.0 **facility** message. The **facility** message is then transmitted by EP1 to GK1.
+
+In either case (whether a H.225.0 message transmission is pending or an ad hoc H.225.0 **facility** message is used), GK1 verifies the authenticator upon receiving the message. Then, if an H.225.0 message transmission is pending for the GK1-GK2 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 message, a new authenticator is computed for the H.225.0 message prior to its transmission from GK1 to GK2. The process repeats for the GK2-EP2 leg.
+
+### 9.4 Direct-routed scenario
+
+Secured H.323 entities may communicate not only within the GK-routed environment as outlined in this Recommendation, but may also deploy the direct-routed model. This direct-routed model requires additional security measures (access tokens) that are not necessary in the simpler GK-routed environments. ITU-T Rec. H.235.4 describes how to secure the direct-routed model.
+
+## 10 Back-end-service support
+
+Secured H.323 entities may use back-end services according to the procedure described in I.1.6/H.235.0.
+
+## 11 H.235 version 1 compatibility
+
+While these security profiles are developed with ITU-T Rec. H.235 version 2 (ITU-T Rec. H.235 (2000)) in mind, it is also possible to apply the security profiles for ITU-T Rec. H.235 version 1 (ITU-T Rec. H.235 (1998)) with some minor modifications. A recipient is able to detect the presence of the sender's H.235 protocol version by evaluating the security profile object identifiers (see clause 15).
+
+ITU-T Rec. H.235 version 1 (ITU-T Rec. H.235 (1998)) implementations:
+
+- do not set or evaluate the **sendersID** in the **ClearToken**.
+- cannot use backend services as in clause 10.
+
+## 12 Multicast behaviour
+
+H.225.0 multicast messages such as GRQ or LRQ shall not include a CryptoToken according to procedure I. When such messages are sent unicast, then the message shall include a CryptoToken.
+
+## 13 List of secured signalling messages
+
+This clause provides a summary of how, and by which means, this Recommendation secures the various H.323 signalling messages.
+
+### 13.1 H.225.0 RAS
+
+| H.225.0 RAS message | H.235 signalling fields | Authentication and integrity |
+|---------------------|-------------------------|------------------------------|
+| Any                 | cryptoTokens            | Procedure I                  |
+
+### 13.2 H.225.0 call signalling
+
+| H.225.0 call signalling message                                                                                                                                                                         | H.235 signalling fields | Authentication and integrity |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------|
+| 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 I                  |
+
+### 13.3 H.245 call control
+
+H.245 messages to and from secured H.323 entities shall either be piggy-backed as part of the secured fast-connect, or shall be tunnelled using the secured H.225.0 **Facility-UUIE**.
+
+### 14 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.1 – Usage of sendersID and generalID**
+
+| Message                                                                                | sendersID                                       | generalID                                       |
+|----------------------------------------------------------------------------------------|-------------------------------------------------|-------------------------------------------------|
+| Unicast <b>GRQ</b>                                                                     | <b>EPID</b> if available, otherwise <b>NULL</b> | <b>GKID</b>                                     |
+| Multicast <b>GRQ</b>                                                                   | <b>EPID</b> if available, otherwise <b>NULL</b> |                                                 |
+| <b>GCF, GRJ</b>                                                                        | <b>GKID</b>                                     | <b>EPID</b> if available, otherwise <b>NULL</b> |
+| Initial <b>RRQ</b>                                                                     | <b>EPID</b> if available, otherwise <b>NULL</b> | <b>GKID</b>                                     |
+| <b>RCF</b>                                                                             | <b>GKID</b>                                     | <b>EPID</b>                                     |
+| <b>RRJ</b>                                                                             | <b>GKID</b>                                     |                                                 |
+| <b>URQ, UCF, URJ, BRQ, BCF, BRJ, DRQ, DCF, DRJ, NSM, RIP, SCI, SCR, XRS (EP-to-GK)</b> | <b>EPID</b>                                     | <b>GKID</b>                                     |
+| <b>URQ, UCF, URJ, BRQ, BCF, BRJ, DRQ, DCF, DRJ, NSM, RIP, SCI, SCR, XRS (GK-to-EP)</b> | <b>GKID</b>                                     | <b>EPID</b>                                     |
+| <b>ARQ, IRQ, RAI</b>                                                                   | <b>EPID</b>                                     | <b>GKID</b>                                     |
+| <b>ACF, ARJ, BCF, LCF, LRJ, IRR, IRQ, RAC, LCF, LRJ, IACK, INAK</b>                    | <b>GKID</b>                                     | <b>EPID</b>                                     |
+| Unicast <b>LRQ</b> (EP-to-GK)                                                          | <b>EPID</b>                                     | <b>GKID</b>                                     |
+| Unicast <b>LRQ</b> (GK-to-GK)                                                          | <b>GKID</b>                                     | <b>GKID</b>                                     |
+| Multicast <b>LRQ</b>                                                                   | <b>EPID</b>                                     |                                                 |
+
+NOTE – GKID stands for gatekeeper identifier, EPID stands for endpoint identifier. Blank indicates a missing or null identification string.
+
+### 15 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.1 – Object identifiers**
+
+| <b>Object identifier reference</b> | <b>Object identifier value(s)</b>                                                                                    | <b>Description</b>                                                                                                                                                                                    |
+|------------------------------------|----------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| "A"                                | {itu-t (0) recommendation (0) h (8) 235 version (0) 2 1}<br>{itu-t (0) recommendation (0) h (8) 235 version (0) 1 1} | Used in procedure I for the CryptoToken-tokenOID, indicating that the hash includes all fields in the H.225.0 RAS and call signalling message (authentication and integrity).                         |
+| "E"                                | {itu-t (0) recommendation (0) h (8) 235 version (0) 3 9}<br>{itu-t (0) recommendation (0) h (8) 235 version (0) 2 9} | End-to-end ClearToken carrying sendersID for verification at the recipient side.                                                                                                                      |
+| "T"                                | {itu-t (0) recommendation (0) h (8) 235 version (0) 2 5}<br>{itu-t (0) recommendation (0) h (8) 235 version (0) 1 5} | Used in procedures I and IA as the baseline ClearToken for the message authentication and replay protection and optionally also for Diffie-Hellman key management as described in 8.5/H.235.6 clause. |
+| "U"                                | {itu-t (0) recommendation (0) h (8) 235 version (0) 2 6}<br>{itu-t (0) recommendation (0) h (8) 235 version (0) 1 6} | Used in procedure I for the Algorithm OID, indicating use of HMAC-SHA1-96.                                                                                                                            |
+
+
+
+
+
+## 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.10-202203-I_PDF-E/raw.md b/marked/H/T-REC-H.235.10-202203-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..1e6a1a2385f79d99e32affad7b7d7d64766cd921
--- /dev/null
+++ b/marked/H/T-REC-H.235.10-202203-I_PDF-E/raw.md
@@ -0,0 +1,379 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.235.10**
+
+(03/2022)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS  
+Infrastructure of audiovisual services – Systems aspects
+
+---
+
+**H.323 security: Support of datagram transport  
+layer security (DTLS) for media streams**
+
+Recommendation ITU-T H.235.10
+
+# 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        |
+| <b>Systems aspects</b>                                                                      | <b>H.230–H.239</b> |
+| 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.235.10
+
+## H.323 security: Support of datagram transport layer security (DTLS) for media streams
+
+## Summary
+
+Recommendation ITU-T H.235.10 describes the security procedures for the establishment of media streams utilising datagram transport layer security (DTLS).
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T H.235.10 | 2022-03-16 | 16          | <a href="http://handle.itu.int/11.1002/1000/14968">11.1002/1000/14968</a> |
+
+## Keywords
+
+H.235, H.235.10, H.323, DTLS, security.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                 | 2    |
+| 4 Abbreviations and acronyms .....                            | 2    |
+| 5 Conventions .....                                           | 2    |
+| 6 Overview .....                                              | 3    |
+| 7 Usage of DTLS .....                                         | 3    |
+| 7.1 DTLS considerations .....                                 | 3    |
+| 7.2 DTLS parameter description .....                          | 4    |
+| 7.3 DTLS parameter transport.....                             | 4    |
+| 8 Procedures .....                                            | 5    |
+| 8.1 Security capability exchange .....                        | 5    |
+| 8.2 Logical channel initiation and fingerprint exchange ..... | 6    |
+| 8.3 DTLS connection initiation .....                          | 6    |
+| 8.4 DTLS connection modification .....                        | 7    |
+| 8.5 DTLS connection release .....                             | 7    |
+| Bibliography.....                                             | 8    |
+
+
+
+# Recommendation ITU-T H.235.10
+
+## H.323 security: Support of datagram transport layer security (DTLS) for media streams
+
+## 1 Scope
+
+The scope of this Recommendation is to provide procedures for the establishment of datagram transport layer security (DTLS) [IETF RFC 6347] connections for media streams. DTLS is an evolution of the widely implemented transport layer security (TLS) security protocol that allows the use of a security protocol over a datagram environment.
+
+An important aspect of the establishment of a DTLS connection is that a fingerprint and hash is communicated via an out-of-band means and that the certificate exchange occurs within the established DTLS connection. The fingerprint is used to ensure the integrity of the certificates. DTLS also follows the TLS client-server model for establishment of the DTLS connection where one of the endpoints is responsible for the establishment of the connection. The roles (client or server) need to be negotiated between the endpoints.
+
+In order for endpoints to communicate the fingerprint/hash and roles information, the information needs to be signalled to the peer endpoint. This Recommendation utilises [ITU-T H.245] to signal this information.
+
+This Recommendation also provides DTLS support for the transmission of secure real-time transport protocol (SRTP) keys in order to establish media protected via SRTP. The indication of support for DTLS based SRTP key negotiation is signalled via [ITU-T H.245]. Once the DTLS connection is established endpoints use the procedures defined in [IETF RFC 5764] for SRTP key negotiation during handshake. This Recommendation provides an alternate method to [ITU-T H.235.7] and [ITU-T H.235.8] for SRTP keying.
+
+## 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.235.7] Recommendation ITU-T H.235.7 (2005), *H.323 security: Usage of the MIKEY key management protocol for the Secure Real Time Transport Protocol (SRTP) within H.235*.
+- [ITU-T H.235.8] Recommendation ITU-T H.235.8 (2005), *H.323 security: Key exchange for SRTP using secure signalling channels*.
+- [ITU-T H.245] Recommendation ITU-T H.245 (2022), *Control protocol for multimedia communication*.
+- [ITU-T H.323] Recommendation ITU-T H.323 (2022), *Packet-based multimedia communications systems*.
+- [IETF RFC 4145] IETF RFC 4145 (2005), *TCP-Based Media Transport in the Session Description Protocol (SDP)*.
+- [IETF RFC 4301] IETF RFC 4301 (2005), *Security Architecture for the Internet Protocol*.
+
+- [IETF RFC 4572] IETF RFC 4572 (2006), *Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP)*.
+- [IETF RFC 5246] IETF RFC 5246 (2005), *The Transport Layer Security (TLS) Protocol Version 1.2*.
+- [IETF RFC 5764] IETF RFC 5764 (2010), *Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)*.
+- [IETF RFC 6083] IETF RFC 6083 (2011), *Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)*.
+- [IETF RFC 6347] IETF RFC 6347 (2012), *Datagram Transport Layer Security Version 1.2*.
+- [IETF RFC 8261] IETF RFC 8261 (2017), *Datagram Transport Layer Security (DTLS) Encapsulation of SCTP Packets*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+All DTLS-related terms used in this Recommendation are based on [b-IETF tls-terms].
+
+### 3.2 Terms defined in this Recommendation
+
+None.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|        |                                             |
+|--------|---------------------------------------------|
+| ABNF   | Augmented Backus-Naur Form                  |
+| DTLS   | Datagram Transport Layer Security           |
+| IPsec  | Internet Protocol Security                  |
+| OLC    | H.245 OpenLogicalChannel message            |
+| OLCAck | H.245 OpenLogicalChannelAck message         |
+| SCTP   | Stream Control Transmission Protocol        |
+| SDP    | Session Description Protocol                |
+| SIP    | Session Initiation Protocol                 |
+| SRTCP  | Secure Real-time Transport Control Protocol |
+| SRTP   | Secure Real-time Transport Protocol         |
+| TCS    | Terminal Capability Set                     |
+| TLS    | Transport Layer Security                    |
+| UDP    | User Datagram Protocol                      |
+
+## 5 Conventions
+
+None.
+
+# 6 Overview
+
+This Recommendation defines procedures based on those defined by [IETF RFC 4572], which as its title states, describes *Connection-oriented media transport over the transport layer security (TLS) protocol in the session description protocol (SDP)*.
+
+Endpoints involved in a datagram transport layer security (DTLS) connection establishment (Note 1) indicate their identity by presenting authentication certificates as part of the DTLS handshake procedure. In order to associate the media streams with the connection and to prevent attacks, the endpoints provide a certificate fingerprint. If the presented certificate matches the received fingerprint, then the endpoint who sent the fingerprint is who it claims to be. [IETF RFC 4572] specifies a fingerprint attribute for this purpose.
+
+NOTE 1 – Whether (or not) a *DTLS session* is established is dependent on if the establishment indicates the session as resumable. If used, there would then be a *resumable DTLS session* (or *semi-permanent DTLS session*) existing in parallel to the established DTLS connection.
+
+[IETF RFC 4572] also defines the use of the "setup" and "connection" attributes defined by [IETF RFC 4145] to determine which of the endpoints initiates the DTLS handshake.
+
+The support of DTLS in [ITU-T H.323] follows the same basic flow as described by [IETF RFC 4145]. That is a call signalling association is established between peer endpoints. The endpoints then exchange information regarding the media capabilities, transport and specific DTLS capabilities. They also indicate any DTLS extensions. For example, the use of DTLS for secure real-time transport protocol (SRTP) keying is indicated via a "use\_srtp" extension. If the endpoints agree to use DTLS then they perform a DTLS handshake (Note 2) to initiate and authenticate a data stream. The endpoints use the fingerprint information to verify the authentication certificates provided in the DTLS handshake. If the certificates are verified, then the data flows. This is illustrated in Figure 1.
+
+![Sequence diagram illustrating the Basic DTLS establishment flow between Endpoint A and Endpoint B. The process is divided into three phases: Phase A (ITU-T H.225 call setup and ITU-T H.245 capability exchange), Phase B (DTLS capabilities exchange including supported hash functions and setup role), and Phase C (ITU-T H.245 open logical channel/ack, DTLS certificate fingerprint and hash, DTLS handshake, and Media transfer).](dbe553cf16dd14073b89a8263a428664_img.jpg)
+
+```
+sequenceDiagram
+    participant Endpoint A
+    participant Endpoint B
+    Note left of Endpoint A: Phase A
+    Endpoint A->>Endpoint B: ITU-T H.225 call setup
+    Endpoint B-->>Endpoint A: ITU-T H.245 capability exchange
+    Note left of Endpoint A: Phase B
+    Endpoint A->>Endpoint B: DTLS capabilities: Supported hash functions
+    Endpoint B-->>Endpoint A: Setup role
+    Note left of Endpoint A: Phase C
+    Endpoint A->>Endpoint B: ITU-T H.245 open logical channel/ack
+    Endpoint B-->>Endpoint A: DTLS certificate fingerprint and hash
+    Endpoint A->>Endpoint B: DTLS handshake (Certificate exchange)
+    Endpoint B-->>Endpoint A: Media transfer
+```
+
+H.235.10(22)
+
+Sequence diagram illustrating the Basic DTLS establishment flow between Endpoint A and Endpoint B. The process is divided into three phases: Phase A (ITU-T H.225 call setup and ITU-T H.245 capability exchange), Phase B (DTLS capabilities exchange including supported hash functions and setup role), and Phase C (ITU-T H.245 open logical channel/ack, DTLS certificate fingerprint and hash, DTLS handshake, and Media transfer).
+
+**Figure 1 – Basic DTLS establishment flow**
+
+NOTE 2 – In more detail, this is a "DTLS full handshake" because a previous DTLS session does not exist, which might allow a DTLS abbreviated handshake.
+
+## 7 Usage of DTLS
+
+### 7.1 DTLS considerations
+
+Depending on the protocol stack that DTLS occurs in there are different considerations for its implementation. Different DTLS procedures are applied based on where it occurs in a stack. For example, if a DTLS connection occurs within a stream control transmission protocol (SCTP)
+
+association (SCTP/DTLS) [IETF RFC 6083] the implementation considerations are different to when an SCTP association occurs within a DTLS connection (DTLS/SCTP) [IETF RFC 8261].
+
+Therefore, the exact DTLS procedures that should be applied to the media stream are determined by the indicated protocol in the ITU-T H.245 **MediaTransportType** or **DataProtocolCapability** element. Any definition of DTLS protocol in these elements shall specify a profile document that describes the operation of DTLS within that protocol stack. For example, clause B.2.2.7 of [ITU-T H.245] indicates that **sctp-dtls** is specified by [IETF RFC 6083].
+
+These profile documents may also specify the use of the connection and set-up elements and the operation of other protocols in the stack.
+
+A DTLS connection is tied to a particular transport address/port. DTLS uses the record layer in order to send encrypted data between peers. However, [IETF RFC 5764] on the use of DTLS to establish SRTP keys mandates that the record layer is not used and the underlying user datagram protocol (UDP) transport connection is used instead. Thus, if both the DTLS record layer (e.g., for SCTP data) and the UDP connection (for audio/video streams) are used for data, they shall be multiplexed on the same transport address/port and share the same DTLS connection for key negotiation.
+
+### 7.2 DTLS parameter description
+
+Information regarding the DTLS session is exchanged via the following parameters:
+
+- **hashFunction** within the **DTLSSecurityCapability** contains the supported hash functions. The value is encoded as per "hash-func" in the ABNF syntax as defined by clause 5 of [IETF RFC 4572].
+- **setupInformation** within the **DTLSSecurityCapability** contains the set-up information used to determine which endpoint establishes the DTLS connection as defined by clause 4 of [IETF RFC 4572]. The value is encoded as per "role" in the ABNF syntax as defined by clause 4 of [IETF RFC 4145].
+- **connectionInformation** within the **DTLSSecurityCapability** contains the connection information used to determine whether an existing or new connection is used for the DTLS connection as defined by clause 4 of [IETF RFC 4572]. The value is encoded as per "conn-value" in the augmented Backus-Naur form (ABNF) syntax as defined by clause 5 of [IETF RFC 4145].
+- **fingerprint** within the **DTLSSecurityCapability** contains the fingerprint associated with the authentication certificates. The value is encoded as per "fingerprint" in the ABNF syntax as defined by clause 5 of [IETF RFC 4572].
+- **extensionsType** within the **DTLSSecurityCapability** indicates which DTLS/TLS extensions are supported by the endpoint. The values are as per the Transport Layer Security (TLS) extensions Internet Assigned Numbers Authority (IANA) registry (<http://www.iana.org/assignments/tls-extensiontype-values/>). The "use\_srtp" extension indicates that DTLS connection is used for SRTP keying. The resultant SRTP media flows use the same transport address/port as the DTLS connection.
+
+The use of the DTLS security capability parameters in this Recommendation is limited to two-party bidirectional media streams where each source has a unique cryptographic key; support for multicast media streams or multipoint unicast streams is for further study.
+
+### 7.3 DTLS parameter transport
+
+#### 7.3.1 DTLS Capabilities
+
+The supported hash functions, set-up, extensions and connection information are carried in the **dtlsSecurityCapability** field of **encryptionAuthenticationAndIntegrity** in
+
+**H235SecurityCapability** of the **TerminalCapabilitySet** **capabilityTable**. The **mediaCapability** field of the **H235SecurityCapability** is associated with the relevant receive or receiveAndTransmit capabilities. The fingerprint is not sent in the **TerminalCapabilitySet** exchange.
+
+Different audio, video or data capabilities exchange may require the use of a single DTLS connection for key negotiation (e.g., SRTP and WebRTC channel using the same DTLS connection). In this case each of those capabilities shall include identical **dtlsSecurityCapability** fields. This may mean the common use of extensions (e.g., "use\_srtp") that may only be applicable to one capability type but to the DTLS connection as a whole. This is also to avoid DTLS renegotiation.
+
+NOTE – See clause 11 of [b-IETF RFC 8843].
+
+#### 7.3.2 Fingerprint
+
+The fingerprint associated with the authentication certificate of the OLC initiating endpoint is carried in the **dtlsSecurityCapability** field of **encryptionAuthenticationAndIntegrity** in **h235Media** of the **OpenLogicalChannel** (OLC) **forwardLogicalChannelParameters** **dataType** field. A single hash function used for the fingerprint shall also be present in the **dtlsSecurityCapability** field which is supported by both endpoints and chosen from the hash functions.
+
+The fingerprint associated with the authentication certificate of the peer endpoint is carried in the **dtlsSecurityCapability** field of the **OpenLogicalChannelAck** (OLCAck). A single hash function used for the fingerprint shall also be present in the **dtlsSecurityCapability** field.
+
+# 8 Procedures
+
+The DTLS procedures described below shall only be used to negotiate security for two-party bidirectional media streams in situations where the ITU-T H.245 signalling channel is used. The ITU-T H.245 signalling channel may be protected by an encapsulating data-security protocol, e.g., IPsec [IETF RFC 4301] or TLS [IETF RFC 5246]. The exchange of DTLS crypto parameters using ITU-T H.245 messages shall provide the following functions:
+
+- 1) Exchange and negotiation of DTLS capabilities: supported hash types, set-up role, extensions and whether an existing connection is to be used.
+- 2) The exchange of fingerprints used to verify the authentication certificates used for the DTLS handshake for the channel.
+
+### 8.1 Security capability exchange
+
+The initiating endpoint indicates its DTLS capabilities as per clause 7.3.1. The initiating endpoint provides a list of hash functions (via the **hashFunction** field in **DTLSSecurityCapability**) that it supports to encode and decode authentication certificates. The peer endpoint replies with the sets of hash functions it supports. The initiating endpoint also sends the DTLS establishment role that it is willing to support (via the **setupInformation** field in **DTLSSecurityCapability**) as per clause 7.3.1 and clause 4.1 of [IETF RFC 4145]. The receiver then chooses based on the received roles, the role that the **TerminalCapabilitySet** initiator shall use for the DTLS connection.
+
+The initiating endpoint provides the supported DTLS extensions in order to indicate the DTLS capabilities to the peer endpoint before establishing the connection. The peer endpoint may use this information when responding to the ITU-T H.245 capabilities exchange. The DTLS handshake is used to negotiate and agree on the set of DTLS extensions used for the connection
+
+NOTE – There is a fundamental difference between H.323 and session initiation protocol (SIP) with regards to the establishment of the media stream. H.323 systems use the ITU-T H.245 master-slave determination procedures (clause C.2 of [ITU-T H.245]) to determine who is the master. Typically, the master is responsible for initiating connections, whereas in SIP/SDP for connections that require a handshake between
+
+a master/slave the SDP a=setup attribute is used to determine the initiating party. Thus, problems occur when interworking between H.323 and SIP systems. It should be possible to open an end-to-end DTLS connection between the H.323 and SIP endpoints without the need to terminate the data stream (i.e., a gateway operates in a pass through mode). The procedures of this Recommendation allow the initiator of the DTLS handshake to be independent of the ITU-T H.245 master.
+
+### 8.2 Logical channel initiation and fingerprint exchange
+
+DTLS connections are fundamentally bidirectional in nature. For a logical channel utilising the DTLS record layer to transfer media, the master endpoint initiates a bidirectional OLC request containing the DTLS fingerprint and hash function as per clause 7.3.2. As per clause 6.2.8.2 of [ITU-T H.323] the bidirectional logical channel procedures (clause C.5 of [ITU-T H.245]) are used to signal the initiation of a DTLS connection. For logical channels utilising DTLS only for key negotiation and another media transport type for transfer of media, a unidirectional OLC request is used.
+
+In response to the OLC, the peer endpoint returns an OLCack with its DTLS fingerprint and hash function.
+
+In the case that an endpoint has indicated the use of a single DTLS connection for multiple audio, video, and/or data logical channel as per clause 7.3.1, identical values shall be returned in the OLCacks related to those logical channels. The endpoint shall also use identical **portNumbers** to indicate that they share the same underlying transport.
+
+The authentication certificates and the associated fingerprint used for the DTLS connection are generated according to the procedures specified in clauses 5 and 6 of [IETF RFC 4572]. The endpoint will use one of the hash functions negotiated through the security capability exchange outlined in clause 8.1. If the ITU-T H.245 connection is secured as per clause 8 then, as per clause 6.1 of [IETF RFC 4572], any certificate asserting a syntactically valid identity may be used. If the ITU-T H.245 signalling is not secured, then an appropriate identity shall be provided. This is FFS.
+
+### 8.3 DTLS connection initiation
+
+On reception of an OLC or OLCack the endpoint that has been identified as the active endpoint for the DTLS connection initiation will initiate an outgoing DTLS connection to the peer to perform the DTLS handshake. During the handshake phase the certificates are exchanged as per [IETF RFC 6347] and clause 6.2 of [IETF RFC 4572]. The receipt of subsequent OLC/OLCacks with the same **dtlsSecurityCapability** shall not initiate additional DTLS signalling.
+
+As discussed in clause 7.1, different uses of DTLS may impose certain requirements for the DTLS handshake phase. The requirements are documented as part of profile document and are dependent on the transport, for example as per clause 4.7 of [IETF RFC 6083].
+
+The endpoints then verify that the fingerprints of the certificates received during the DTLS handshake match the fingerprints received in the OLC or OLCack messages. In this manner, the endpoints verify each other's credentials.
+
+If the fingerprints do not match, the endpoint shall close the DTLS connection via a DTLS closure alert and then immediately close the logical channel.
+
+Once the DTLS handshake is successfully completed and the credentials have been verified, data packets are transported in DTLS record layer "application\_data" packets.
+
+Some usages of DTLS (e.g., DTLS-SRTP) use alternate methods to transport data packets.
+
+If the "use\_srtp" extension has been negotiated via the DTLS handshake the endpoints shall follow the procedures of [IETF RFC 5764] to establish SRTP keying information and to send the SRTP/SRTCP data. In this case RTP and/or RTCP application data is protected via SRTP and not sent in the DTLS record layer "application\_data" packets.
+
+Whether the DTLS record layer or an alternate method is used is determined by the capabilities associated with the logical channel. For example, a **mediaTransportType** of UDP/DTLS/SCTP would indicate the use of the DTLS record layer, UDP would indicate the use of SRTP.
+
+### **8.4 DTLS connection modification**
+
+Additional media may be added to an existing connection by utilising TCS / OLC signalling with an identical **dtlsSecurityCapability** field and **portNumber** (as appropriate) to the existing DTLS connection to avoid the DTLS renegotiation.
+
+### **8.5 DTLS connection release**
+
+If the logical channel representing the DTLS connection is closed the security context is deleted and any application data shall stop flowing. That is, no packet shall be sent or received on the DTLS record layer. If SRTP keys have been negotiated via DTLS data flow shall cease on logical channels representing the SRTP/SRTCP streams.
+
+## Bibliography
+
+- [b-IETF RFC 8843] IETF RFC 8843 (2021), *Negotiating Media Multiplexing Using the Session Description Protocol (SDP)*.
+- [b-IETF tls-terms] IETF draft-guballa-tls-terminology-05 (2017), *Terminology related to TLS and DTLS*. <https://datatracker.ietf.org/doc/html/draft-guballa-tls-terminology-05>
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/H/T-REC-H.235.2-200509-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f09ba4bfeeb2b7e56c5ec255616f48a4f6420e28
--- /dev/null
+++ b/marked/H/T-REC-H.235.2-200509-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3a8c1e4f4d9f9db47e0cfe5de2bb9d119a0ddf6643b228364a981597fa68b2d9
+size 37414
diff --git a/marked/H/T-REC-H.235.2-200509-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.235.2-200509-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ed5d8e9d9a59a2e0fc66a58c5a4c791c43cfac6a
--- /dev/null
+++ b/marked/H/T-REC-H.235.2-200509-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:44c5f4aa83b4ce76984a1d30e8c189795b446ee51eacd71fc0721ed1e01ba4b8
+size 6976
diff --git a/marked/H/T-REC-H.235.2-200509-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.235.2-200509-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3b25bf5c00b9b2943ff401778d9cea15450558b4
--- /dev/null
+++ b/marked/H/T-REC-H.235.2-200509-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b2501f675de1ca20fb7128b9e1ab6473a12d828253ff5ab94e27fc3010ea97e3
+size 34697
diff --git a/marked/H/T-REC-H.235.5-200509-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/H/T-REC-H.235.5-200509-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4de1915cd9271cc20f87d0e68584b6f85a661745
--- /dev/null
+++ b/marked/H/T-REC-H.235.5-200509-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:caf0b6dda34cc63c8142c1a402a9789191e275a6be9d1a5dc330d9f784c24be2
+size 103919
diff --git a/marked/H/T-REC-H.235.5-200509-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.235.5-200509-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c
--- /dev/null
+++ b/marked/H/T-REC-H.235.5-200509-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_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.235.7-200509-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/H/T-REC-H.235.7-200509-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d6808a9aedf84e2781da322ca175763236e45fc2
--- /dev/null
+++ b/marked/H/T-REC-H.235.7-200509-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:853d63e82c00f9ed2c709777b3f4a1d2f0d5093c1f0ad4c618ae5954eec563fa
+size 90668
diff --git a/marked/H/T-REC-H.235.7-200509-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/H/T-REC-H.235.7-200509-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..937e63a4b921457b9d35445278a9a62e93fe4a09
--- /dev/null
+++ b/marked/H/T-REC-H.235.7-200509-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5df7360b0dbe0b4e5d22a1237f2b8919d4d74c9bbbd1edb415755af4b25efe8b
+size 102009
diff --git a/marked/H/T-REC-H.235.7-200509-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/H/T-REC-H.235.7-200509-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0bd8dcbdb8e5306d40bb4e04c0822cddd2280d04
--- /dev/null
+++ b/marked/H/T-REC-H.235.7-200509-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5595707711c5fc70b6458e478647b32524dae267a0cdeee52309d02481bf9f36
+size 23065
diff --git a/marked/H/T-REC-H.235.7-200509-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/H/T-REC-H.235.7-200509-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1faed970729a0b77d4b6168c23eb89fdfad94dab
--- /dev/null
+++ b/marked/H/T-REC-H.235.7-200509-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5c469411de2e9b485a9eede27dc80d7bf22d51c4ff5b452fc2902846f6df4129
+size 63676
diff --git a/marked/H/T-REC-H.235.7-200509-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/H/T-REC-H.235.7-200509-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..de1f26631133354bd7c6dd5853be01a941102175
--- /dev/null
+++ b/marked/H/T-REC-H.235.7-200509-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8c9f3d1ee0aaf740016668a9266ce3db14649778913316d6393f4b5c751bce8e
+size 151144
diff --git a/marked/H/T-REC-H.235.7-200509-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/H/T-REC-H.235.7-200509-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..49f68221697cea9557fe049ed45255053f104741
--- /dev/null
+++ b/marked/H/T-REC-H.235.7-200509-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9f6b78775ae786bb03be615ee9cb884b1b2304d552b27573e67e6b95165ba1a5
+size 188823
diff --git a/marked/H/T-REC-H.235.7-200509-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/marked/H/T-REC-H.235.7-200509-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..786761fd6936ae71581c6aebf8979c34ee62e076
--- /dev/null
+++ b/marked/H/T-REC-H.235.7-200509-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1356d99768bc5cd087f66978711b57cee86d9d013200cf41b694e8dc7acd7cae
+size 84434
diff --git a/marked/H/T-REC-H.235.7-200509-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg b/marked/H/T-REC-H.235.7-200509-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0db8d3d7457fec2cf01c3aa184d854b4f7ca00f3
--- /dev/null
+++ b/marked/H/T-REC-H.235.7-200509-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:66f53afa900c1d0d3ba5436a95861c3e8462f6eff77491fc4bdceb762f171574
+size 154164
diff --git a/marked/H/T-REC-H.235.7-200509-I_PDF-E/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/H/T-REC-H.235.7-200509-I_PDF-E/86b4670fc1a5a694821ee92b99c1209a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e86476729b86464327b9d3797d6eae1d23ef84ba
--- /dev/null
+++ b/marked/H/T-REC-H.235.7-200509-I_PDF-E/86b4670fc1a5a694821ee92b99c1209a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dfbd87392e9bf7809e372a122de798effb4c9ec2420a0e2d8ee1e585660dd445
+size 59468
diff --git a/marked/H/T-REC-H.235.7-200509-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.235.7-200509-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c
--- /dev/null
+++ b/marked/H/T-REC-H.235.7-200509-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_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.235.7-200509-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/H/T-REC-H.235.7-200509-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..53fdd51547babd4be578a4a9867cb031a33b704a
--- /dev/null
+++ b/marked/H/T-REC-H.235.7-200509-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b3333b551b9ae1897ff3c2b7b89c45c39e0dcd623ce8f0b421faa94cd98497a9
+size 136140
diff --git a/marked/H/T-REC-H.235.7-200509-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/H/T-REC-H.235.7-200509-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6c741374bd01f898092d5a504c9d6fbf0292fdcc
--- /dev/null
+++ b/marked/H/T-REC-H.235.7-200509-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:541eb7f681177aaa1a415a49d522b67b2b2757e1457fdbe93d6bde76ca8b9a4c
+size 19678
diff --git a/marked/H/T-REC-H.235.7-200509-I_PDF-E/dbbc0baac7341cda76cc4f8355dce23f_img.jpg b/marked/H/T-REC-H.235.7-200509-I_PDF-E/dbbc0baac7341cda76cc4f8355dce23f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..66c069df791e1c9fe19d7866d372a4513bc95acd
--- /dev/null
+++ b/marked/H/T-REC-H.235.7-200509-I_PDF-E/dbbc0baac7341cda76cc4f8355dce23f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aba2fcf48a78bb8fcbe041d054e9430ceca37dfb2b545bd8a01011b4d4a0a68b
+size 146918
diff --git a/marked/H/T-REC-H.235.7-200509-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/H/T-REC-H.235.7-200509-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c496ad1919e24e731aff37b049f6c43d8c79c12b
--- /dev/null
+++ b/marked/H/T-REC-H.235.7-200509-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:510628675674e0042b1baafa242e596ac62e86a9b5cb70840801fcca72657c73
+size 211223
diff --git a/marked/H/T-REC-H.235.7-200509-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/H/T-REC-H.235.7-200509-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..66fb82815e3a4b59d6c900ae9d1228bea4429c89
--- /dev/null
+++ b/marked/H/T-REC-H.235.7-200509-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fb380b9b0e62ef3538052c4208cf38f5e91925f872d309259196f2208a87b340
+size 109604
diff --git a/marked/H/T-REC-H.235.8-200509-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/H/T-REC-H.235.8-200509-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9cede155046ef6f46b62ca25c49580a3ca61463f
--- /dev/null
+++ b/marked/H/T-REC-H.235.8-200509-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:531c45960eafb645f8b1242b65bb76bd946a2bed690a22b1868ed4dc7981fa56
+size 25253
diff --git a/marked/H/T-REC-H.235.8-200509-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/H/T-REC-H.235.8-200509-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fa3aad4af0d54da2ed1ef1aaf2c98da281eb6ff9
--- /dev/null
+++ b/marked/H/T-REC-H.235.8-200509-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7c8c777905a39fe095712857fde99194a6bba372117d7594b53f6b96eb294e45
+size 64559
diff --git a/marked/H/T-REC-H.235.8-200509-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg b/marked/H/T-REC-H.235.8-200509-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b81f8e9ca1de694e1c571b9a716d42ce84fee88c
--- /dev/null
+++ b/marked/H/T-REC-H.235.8-200509-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f5343cde54bb269772430150ad6ecc596086ec12eebbf6aaf93f7dc2f329754d
+size 38071
diff --git a/marked/H/T-REC-H.235.8-200509-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.235.8-200509-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bc7c2735da4140ee3b8f6594a887d00eae6a5e9f
--- /dev/null
+++ b/marked/H/T-REC-H.235.8-200509-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fbbd392e3f07377ba2af380aadd33765303a8923d4bf18418d2ca5cfac57cdde
+size 6965
diff --git a/marked/H/T-REC-H.235.8-200509-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/H/T-REC-H.235.8-200509-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9325c4e2452830b7068ea1770c147e47204e51e7
--- /dev/null
+++ b/marked/H/T-REC-H.235.8-200509-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:92a73df9fb537507ddf51020475ce6cceb77e31da4d6a933bfb09354d2614a56
+size 40992
diff --git a/marked/H/T-REC-H.235.8-200509-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/H/T-REC-H.235.8-200509-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fb8006ba09035678a311f181a3bc6e32d1577742
--- /dev/null
+++ b/marked/H/T-REC-H.235.8-200509-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:45bb06ff54ca857cad36254f3f19f898b9fc6ebaa73c146344f36983d0a27ea1
+size 24352
diff --git a/marked/H/T-REC-H.235.8-200509-I_PDF-E/raw.md b/marked/H/T-REC-H.235.8-200509-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c008f61d5879279d7309bcc4fada1edc8a0c5a1d
--- /dev/null
+++ b/marked/H/T-REC-H.235.8-200509-I_PDF-E/raw.md
@@ -0,0 +1,799 @@
+
+
+I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.235.8**
+
+(09/2005)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS  
+Infrastructure of audiovisual services – Systems aspects
+
+---
+
+**H.323 security: Key exchange for SRTP using  
+secure signalling channels**
+
+ITU-T Recommendation H.235.8
+
+**ITU-T**
+
+![ITU logo: International Telecommunication Union](84a1d09fb489061482111515543b60dc_img.jpg)
+
+The logo of the International Telecommunication Union (ITU) features a blue globe with a red lightning bolt striking 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        |
+| <b>Systems aspects</b>                                                        | <b>H.230–H.239</b> |
+| 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.8**
+
+# **H.323 security: Key exchange for SRTP using secure signalling channels**
+
+## **Summary**
+
+The purpose of this Recommendation is to describe security procedures for key exchange for SRTP using secure signalling channels over H.323/H.235 networks.
+
+This Recommendation should be used in conjunction with ITU-T Recs H.323 and H.225.0 versions 4 or later.
+
+###### **Source**
+
+This Recommendation H.235.8 was approved on 13 September 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 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.....                                               | 2  |
+| 2.1 | Normative references.....                                     | 2  |
+| 2.2 | Informative references.....                                   | 2  |
+| 3   | Symbols and abbreviations .....                               | 2  |
+| 4   | Parameter description .....                                   | 3  |
+| 4.1 | SRTP parameter transport .....                                | 3  |
+| 4.2 | SrtpCryptoCapability parameter description.....               | 4  |
+| 4.3 | SrtpKeys parameter description .....                          | 6  |
+| 4.4 | SRTP crypto context initialization .....                      | 7  |
+| 5   | Procedures .....                                              | 9  |
+| 5.1 | Security capability exchange .....                            | 9  |
+| 5.2 | Initial negotiation.....                                      | 10 |
+| 5.3 | Session modification .....                                    | 13 |
+| 5.4 | No negotiation .....                                          | 14 |
+| 5.5 | Forward error correction.....                                 | 14 |
+| 6   | Public key cryptography to secure key exchange for SRTP ..... | 14 |
+| 6.1 | Endpoint identification .....                                 | 15 |
+| 6.2 | SRTP key exchange procedures .....                            | 15 |
+| 6.3 | CMS body usage.....                                           | 16 |
+| 7   | H.235 SRTP security descriptions syntax .....                 | 19 |
+
+
+
+# H.323 security: Key exchange for SRTP using secure signalling channels
+
+## 1 Scope
+
+The purpose of this Recommendation is to provide recommendations for security procedures to support the IETF Secure Real Time Protocol (SRTP) between H.323 Endpoints in cases where the cryptographic material for the media channel is transported over a secure signalling channel, e.g., IPsec (RFC 2401), TLS (RFC 2246) or other H.235 mechanisms. These security procedures are offered as an alternative to other H.235 security procedures that support SRTP.
+
+This Recommendation describes procedures used to support the IETF Secure Real Time Protocol (SRTP) in ITU-T Rec. H.323. SRTP provides security services for RTP media and relies on separate protocols to provide key management services and the negotiation of cryptographic parameters. These procedures should not be used when the secure signalling channel terminates at an intermediate system, in such cases the SRTP cryptographic material should be transported by a secure end-to-end mechanism.
+
+These procedures support the signalling, negotiation and transport of the SRTP cryptographic keys, authentication and encryption algorithm identifiers and other session parameters between H.323 Endpoints.
+
+A key aspect of these procedures is that the H.245 slave as well as the H.245 master shall be able to generate and distribute cryptographic keys.
+
+SRTP security capabilities may be exchanged using existing terminal capabilities exchange using h235SecurityCapability entries in the capabilityTable of the H.245 TerminalCapabilitySet message. The genericH235SecurityCapability field in the encryptionAuthenticationAndIntegrity field in the h235SecurityCapability entry contains the SrtpCryptoCapability field which will specify the SRTP crypto-suites.
+
+A SRTP crypto parameter is specified to signal and negotiate SRTP cryptographic parameters. The definition of the crypto parameter in this Recommendation is limited to two-party unicast media streams where each source has a unique cryptographic key; support for multicast media streams or multipoint unicast streams is for further study.
+
+The SRTP crypto parameter is intended to be able to establish the SRTP cryptographic parameters in a single message or a single round trip message exchange. In the case of a round trip message exchange, the cryptographic parameters may be negotiated. For example, in Fast Connect, the offering H.323 Endpoint sends a set of offered SRTP crypto parameters to the answering H.323 Endpoint, each offer encapsulated in a separate H.245 OpenLogicalChannel message. The answering H.323 Endpoint may then accept one of the offered parameters and respond with an answer that includes the selected parameter subset encapsulated in a H.245 OpenLogicalChannel message.
+
+In the case of a single message exchange there is no negotiation. The offering H.323 Endpoint sends the SRTP crypto parameters to the answering H.323 Endpoint which either accepts the offered parameters or rejects the call.
+
+Public key cryptography procedures may be added to provide end-to-end confidentiality and authentication of the SRTP session key material exchanged between H.323 Endpoints by encrypting and then signing the SRTP key material in the case where the encapsulating security protocol, e.g., IPsec, TLS, terminates on an intermediate device and, therefore, does not provide end-to-end security.
+
+# 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.323 (2003), *Packet-based multimedia communications systems*.
+- ITU-T Recommendation H.460.11 (2004), *Delayed call establishment within H.323 Systems*.
+- IETF RFC 2246 (1999), *The TLS Protocol Version 1.0*.
+- IETF RFC 2401 (1998), *Security Architecture for the Internet Protocol*.
+- IETF RFC 2733 (1999), *An RTP Payload Format for Generic Forward Error Correction*.
+- IETF RFC 3280 (2002), *Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile*.
+- 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 3852 (2004), *Cryptographic Message Syntax (CMS)*.
+
+## 2.2 Informative references
+
+- IETF Draft, F. Andreasen, M. Baugher, D. Wing: *Session Description Protocol Security Descriptions for Media Streams*, <draft-ietf-mmusic-sdescriptions-11.txt>.
+
+# 3 Symbols and abbreviations
+
+This Recommendation uses the following abbreviations:
+
+|       |                               |
+|-------|-------------------------------|
+| AES   | Advanced Encryption Algorithm |
+| ASN.1 | Abstract Syntax Notation One  |
+| CA    | Certificate Authority         |
+| CEK   | Content Encryption Key        |
+| CMS   | Cryptographic Message Syntax  |
+| EP    | Endpoint                      |
+| FEC   | Forward Error Correction      |
+| FFS   | For Further Study             |
+| F8    | UMTS Encryption Algorithm     |
+| GK    | Gatekeeper                    |
+
+|       |                                             |
+|-------|---------------------------------------------|
+| GW    | Gateway                                     |
+| HMAC  | Keyed-Hash Message Authentication Code      |
+| IETF  | Internet Engineering Task Force             |
+| KDR   | Key Derivation Rate                         |
+| MAC   | Message Authentication Code                 |
+| MKI   | Master Key Identifier                       |
+| OID   | Object Identifier                           |
+| OLC   | Open Logical Channel                        |
+| PKI   | Public Key Infrastructure                   |
+| RAS   | Registration, Admission, Status             |
+| ROC   | Roll-over Counter                           |
+| RTCP  | Real-time Transport Control Protocol        |
+| RTP   | Real-time Transport Protocol                |
+| SHA1  | Secure Hash Algorithm 1                     |
+| SRTCP | Secure Real-time Transport Control Protocol |
+| SRTP  | Secure Real-time Transport Protocol         |
+| SSRC  | Synchronization Source                      |
+| TLS   | Transport Level Security                    |
+| WSH   | Window Size Hint                            |
+
+# 4 Parameter description
+
+SRTP cryptographic capability and key material is exchanged using two parameters:
+
+- **SrtpCryptoInfo** within **SrtpCryptoCapability** shall contain the crypto-suite and session parameters. The **SrtpCryptoInfo** parameter shall be transported in the H.245 **genericH235SecurityCapability** parameter to signal and negotiate SRTP cryptographic parameters.
+- **SrtpKeyParameters** within **SrtpKeys** shall contain the SRTP key material. The **SrtpKeys** container in the H.245 **h235Key** parameter shall transport one or more **SrtpKeyParameters** with the SRTP keys.
+
+The use of the SRTP crypto parameters in this Recommendation is limited to two-party unicast media streams where each source has a unique cryptographic key; support for multicast media streams or multipoint unicast streams is for further study.
+
+## 4.1 SRTP parameter transport
+
+A full-duplex SRTP media connection consists of two unidirectional channels, one in each direction. Each crypto-offer is transported in a separate H.245 **OpenLogicalChannel** message.
+
+### 4.1.1 SrtpKeys transport
+
+The SRTP cryptographic key material **SrtpKeys** shall be transported in the **genericKeyMaterial** field of the **secureSharedSecret (V3KeySyncMaterial)** parameter contained within the **h235Key** container in the **encryptionSync** parameter of H.245 **OpenLogicalChannel** messages.
+
+The SRTP cryptographic key content in the **genericKeyMaterial** container shall be identified using the H.235.8 object identifier value (see Table 1) in the **standard** field of **capabilityIdentifier**
+
+within the **genericH235SecurityCapability** field of **encryptionAuthenticationAndIntegrity** in **h235Media** of the OLC **dataType**.
+
+Alternative **OpenLogicalChannel** proposals for the same channel that contain the same **sessionID** value in **H2250LogicalChannelParameters** may use the same crypto-offer. Since only one of these alternate sessions will be accepted key uniqueness will be guaranteed.
+
+### 4.1.2 SrtpCryptoCapability transport
+
+The **SrtpCryptoCapability** parameter shall be transported in the **genericH235SecurityCapability** field of **encryptionAuthenticationAndIntegrity** in **h235Media** of the **dataType** parameter of **OpenLogicalChannel** messages.
+
+The H.245 **TerminalCapabilitySet** message may include one or more **h235SecurityCapability** entries in the **capabilityTable**. In order to indicate support for these procedures the H.323 Endpoint shall set the **genericH235SecurityCapability** within **encryptionAuthenticationAndIntegrity** in an **h235SecurityCapability** entry as follows:
+
+- **capabilityIdentifier** shall contain the H.235.8 OID (see Table 1) in **standard** field;
+- **maxbitRate**, **collapsing**, **nonCollapsing**, and **transport** shall be unused;
+- **nonCollapsingRaw** shall contain the **SrtpCryptoCapability** parameter.
+
+Table 1/H.235.8 – H.235.8 object identifier
+
+| OID Value                                                   |
+|-------------------------------------------------------------|
+| { itu-t (0) recommendation (0) h (8) 235 version (0) 4 90 } |
+
+## 4.2 SrtpCryptoCapability parameter description
+
+The **SrtpCryptoCapability** may contain one or more **SrtpCryptoInfo** parameters that may be used to specify capabilities for the SRTP session. The **BOOLEAN OPTIONAL** elements shall be interpreted as:
+
+- 1) if FALSE, the capability is not supported;
+- 2) if TRUE, the capability is supported and required;
+- 3) if absent, the capability is supported but not required.
+
+When using **SrtpCryptoCapability** in a capability exchange, it is possible to indicate all acceptable options within a single generic capability. In this use, the omission of a **BOOLEAN OPTIONAL** element will be interpreted to mean that the capability is supported but not required.
+
+When used in an OLC **dataType** expression, only one option may be used. For this purpose, the following rules shall be observed:
+
+- **FecOrder** may contain only one of the optional values.
+- In **SrtpSessionParameters**, the **BOOLEAN OPTIONAL** values must be either TRUE or FALSE.
+- **SrtpCryptoCapability** shall contain only a single **SrtpCryptoInfo** element.
+
+The **SrtpCryptoInfo** parameter consists of mandatory **cryptoSuite** field and optional **sessionParams** and **allowMKI** fields which are described below.
+
+**Table 2/H.235.8 – H.235.8 crypto-suite object identifiers**
+
+| Crypto-suite            | OID value                                                   |
+|-------------------------|-------------------------------------------------------------|
+| AES_CM_128_HMAC_SHA1_80 | { itu-t (0) recommendation (0) h (8) 235 version (0) 4 91 } |
+| AES_CM_128_HMAC_SHA1_32 | { itu-t (0) recommendation (0) h (8) 235 version (0) 4 92 } |
+| F8_128_HMAC_SHA1_80     | { itu-t (0) recommendation (0) h (8) 235 version (0) 4 93 } |
+
+### 4.2.1 cryptoSuite
+
+The object identifier (see Table 2) in the field **cryptoSuite** identifies the desired encryption and authentication algorithms to be used in the SRTP session. The SRTP specification has many parameters that are bundled into three options, called "Crypto Suites". These are extensible in that new Crypto Suites can be added. The three Crypto Suites that are defined are AES\_CM\_128\_HMAC\_SHA1\_80, AES\_CM\_128\_HMAC\_SHA1\_32, and F8\_128\_HMAC\_SHA1\_80. The SRTP parameters that are bundled into each of these are shown as rows in Table 3.
+
+**Table 3/H.235.8 – Crypto-suites default values**
+
+| SRTP parameter            | AES_CM_128_HMAC_SHA1_80 | AES_CM_128_HMAC_SHA1_32 | F8_128_HMAC_SHA1_80     |
+|---------------------------|-------------------------|-------------------------|-------------------------|
+| Master key length         | 128 bits                | 128 bits                | 128 bits                |
+| Salt value                | 112 bits                | 112 bits                | 112 bits                |
+| Lifetime                  | 2 <sup>31</sup> packets | 2 <sup>31</sup> packets | 2 <sup>31</sup> packets |
+| Cipher                    | AES Counter             | AES Counter             | F8                      |
+| Encryption key            | 128 bits                | 128 bits                | 128 bits                |
+| MAC                       | HMAC-SHA1               | HMAC-SHA1               | HMAC-SHA1               |
+| Authentication tag length | 80 bits                 | 32 bits                 | 80 bits                 |
+| SRTP auth. Key length     | 160 bits                | 160 bits                | 160 bits                |
+| SRTCP auth. Key length    | 160 bits                | 160 bits                | 160 bits                |
+
+The field **cryptoSuite** is a negotiated parameter.
+
+### 4.2.2 sessionParams
+
+Session parameters may be either negotiated or declarative; the definition of a specific session parameter shall indicate whether it is negotiated or declarative. Negotiated parameters apply to data sent in both directions, whereas declarative parameters apply only to media sent by the entity that generated the session description. Thus, a declarative parameter in an offer applies to media sent by the offerer, whereas a declarative parameter in an answer applies to media sent by the answerer.
+
+The optional field **sessionParams** contains SRTP session parameters.
+
+#### 4.2.2.1 kdr
+
+KDR specifies the Key Derivation Rate, as described in section 4.3.1 of RFC 3711. The value shall be an integer in the set {1, 2, ..., 24}, which denotes a power of 2 from 2<sup>1</sup> to 2<sup>24</sup>, inclusive. The SRTP key derivation rate controls how frequently a new session key is derived from an SRTP master key (RFC 3711). When the key derivation rate is not specified (i.e., the KDR parameter is omitted), a single initial key derivation is performed (RFC 3711). KDR is a declarative parameter.
+
+#### 4.2.2.2 unencryptedSrtp
+
+This is an optional Boolean field: if present it signals that the SRTP packet payloads are not encrypted. This is a negotiated parameter.
+
+#### 4.2.2.3 unencryptedSrtcp
+
+This is an optional Boolean field: if present it signals that the SRTCP packet payloads are not encrypted. This is a negotiated parameter.
+
+#### 4.2.2.4 unauthenticatedSrtp
+
+SRTP and SRTCP packet payloads are authenticated by default. This is an optional Boolean field, if present it signals that the SRTP packet payloads are not authenticated. The SRTP specification requires use of message authentication for SRTCP, but not for SRTP (RFC 3711). This is a negotiated parameter.
+
+#### 4.2.2.5 fecOrder
+
+**fecOrder** signals the order of forward error correction processing for the RTP packets (RFC 3550, RFC 2733) relative to SRTP encryption at the sender. The value for **fecOrder** of **fecBeforeSrtp** signals that FEC is applied before SRTP processing by the sender of the SRTP media and after SRTP processing by the receiver of the SRTP media; **fecBeforeSrtp** is the default. **fecAfterSrtp** is the reverse order of processing. **fecOrder** is a declarative parameter.
+
+#### 4.2.2.6 windowSizeHint
+
+SRTP defines the SRTP-WINDOW-SIZE (RFC 3711, section 3.3.2) parameter to protect against replay attacks. The minimum value is 64 (RFC 3711), however this value may be considered too low for some applications, e.g., video.
+
+The Window Size Hint (WSH) session parameter provides a hint for how big this window should be to work satisfactorily (e.g., based on sender knowledge of number of packets per second). However, there might be enough information given in media packetization descriptors to allow a receiver to derive the parameter satisfactorily. Consequently, this value is only considered a hint to the receiver which may choose to ignore the value provided.
+
+**windowSizeHint** is a declarative parameter.
+
+#### 4.2.2.7 Defining new SRTP session parameters
+
+New SRTP session parameters are by default mandatory. The **newParameter** field is used as an extension mechanism for new session parameters. If an older H.323 Endpoint receives a **SrtpCryptoInfo** parameter with an unknown session parameter in the **newParameter** field, that new **SrtpCryptoInfo** parameter shall be considered invalid.
+
+## 4.3 SrtpKeys parameter description
+
+The field **SrtpKeys** contains one or more key parameters **SrtpKeyParameter** that are to be used for the SRTP session. Each **SrtpKeyParameter** contains the keying material (master key and salt) and all policy related to that master key, including how long it can be used (lifetime) and whether or not it uses a master key identifier (MKI) to associate an incoming SRTP packet with a particular master key. Compliant implementations obey the policies associated with a master key, and shall not accept incoming packets that violate the policy (e.g., after the master key lifetime has expired).
+
+### 4.3.1 masterKey
+
+This is the cryptographic master key to be used for the SRTP session. The length of the key is determined by the crypto suite for which the key applies. If the length does not match that specified for the crypto-suite, the crypto parameter in question shall be considered invalid. Each master key shall be a cryptographically random number and shall be unique to the proposed media flow.
+
+### 4.3.2 masterSalt
+
+This is the cryptographic master salt to be used for the SRTP session. The length of the salt is determined by the crypto suite for which the key applies. If the length does not match that specified for the crypto-suite, the crypto parameter in question shall be considered invalid. Each master salt shall be a cryptographically random number and shall be unique to the proposed media flow.
+
+### 4.3.3 lifetime
+
+This field is the optional lifetime of the master key as measured in the maximum number of SRTP or SRTCP packets using that master key (i.e., the number of SRTP packets and the number of SRTCP packets each have to be less than the lifetime). The lifetime value may be written as a non-zero, positive integer or as a power of 2. The "lifetime" value shall not exceed the maximum packet lifetime for the crypto-suite. If the lifetime is too large, or otherwise invalid, then the entire crypto parameter shall be considered invalid. If the lifetime field is not present, the default lifetime is to be used. This is convenient when the SRTP cryptographic key lifetime is the default value.
+
+### 4.3.4 masterKeyId
+
+This optional field specifies the policy of how keys are to be identified for the SRTP session. MKI is the master key identifier associated with the SRTP master key. If the MKI is given, then the length of the MKI shall also be provided. The MKI length is the size of the MKI field in the SRTP packet, specified in bytes. If the MKI length is not given or its value exceeds 128 (bytes), then the entire crypto parameter shall be considered invalid.
+
+As mentioned above, the key parameter can contain one or more master keys. When the key parameter contains more than one master key, all of the master keys in that key parameter shall include an MKI value. When using the MKI, the MKI length shall be the same for all keys in a given crypto parameter.
+
+## 4.4 SRTP crypto context initialization
+
+In addition to the various SRTP parameters defined above, there are three pieces of information that are critical to the operation of the default SRTP ciphers:
+
+- SSRC: Synchronization source
+- ROC: Roll-over counter for a given SSRC
+- SEQ: Sequence number for a given SSRC
+
+In a unicast session, as defined here, there are three constraints on these values. The first constraint is on the SSRC, which makes an SRTP keystream be unique from other participants. As explained in SRTP, the keystream shall not be reused on two or more different pieces of plaintext.
+
+Keystream reuse makes the ciphertext vulnerable to cryptanalysis. One vulnerability is that known-plaintext fields in one stream can expose portions of the reused keystream and this could further expose more plaintext in other streams. Since all current SRTP encryption transforms use keystreams, key sharing is a general problem (RFC 3711). SRTP mitigates this problem by including the SSRC of the sender in the keystream. But SRTP does not solve this problem in its entirety because Real-time Transport Protocol has SSRC collisions, which are very rare (RFC 3550) but quite possible. During a collision, two or more SSRCs that share a master key will have identical keystreams for overlapping portions of the RTP sequence-number space. The SRTP security description avoids keystream reuse by making unique master keys required for the sender and receiver of the security description. Thus, the first constraint is satisfied.
+
+It should also be noted that there is a second problem with SSRC collisions: The SSRC is used to identify the crypto context and thereby the cipher, key, ROC, etc. to process incoming packets. In case of SSRC collisions, crypto context identification becomes ambiguous and correct packet
+
+processing may not occur. Furthermore, if an RTCP BYE packet is to be sent for a colliding SSRC, that packet may also have to be secured.
+
+The second constraint is that the ROC shall be zero at the time that each SSRC commences sending packets. Thus, there is no concept of a "late joiner" in SRTP security descriptions, which are constrained to be unicast and pairwise. The ROC and SEQ form a "packet index" in the default SRTP transforms and the ROC is consistently set to zero at session commencement, according to this Recommendation.
+
+The third constraint is that the initial value of SEQ should be chosen to be within the range of  $0..2^{15} - 1$ ; this avoids an ambiguity when packets are lost at the start of the session. If, at the start of a session, an SSRC source might randomly select a high sequence-number value and put the receiver in an ambiguous situation: if initial packets are lost in transit up to the point that the sequence number wraps (i.e., exceeds  $2^{16} - 1$ ), then the receiver might not recognize that its ROC needs to be incremented. By restricting the initial SEQ to the range of  $0..2^{15} - 1$ , SRTP packet-index determination will find the correct ROC value, unless all of the first  $2^{15}$  packets are lost (which seems, if not impossible, then rather unlikely). See section 3.3.1 of the SRTP specification regarding packet-index determination (RFC 3771).
+
+### 4.4.1 Late binding of SSRCs to a crypto context
+
+The packet index, therefore, depends on the SSRC, the SEQ of an incoming packet and the ROC, which is an SRTP crypto context variable. Thus, SRTP has a big security dependency on SSRC uniqueness. Given the above constraints, unicast SRTP crypto contexts can be established without the need to negotiate SSRC values in the SRTP security description. Instead, an approach called "late binding" is recommended by this Recommendation. When a packet arrives, the SSRC that is contained in it can be bound to the crypto context at the time of session commencement (i.e., SRTP packet arrival) rather than at the time of session signalling (i.e., receipt of an H.245 message). With the arrival of the packet containing the SSRC, all the data items needed for the SRTP crypto context are held by the receiver (note that the ROC value by definition is zero; if non-zero values were to be supported, additional signalling would be required). In other words, the crypto context for a secure RTP session using late binding is initially identified by the H.245 message as:
+
+<\*, address, port>
+
+where '\*' is a wildcard SSRC, "address" is the local receive address from **mediaChannel**, and "port" is the local receive port from **portNumber**. When the first packet arrives with ssrcX in its SSRC field, the crypto context
+
+<ssrcX, address, port>
+
+is instantiated subject to the following constraints:
+
+- Media packets are authenticated: Authentication must succeed; otherwise, the crypto context is not instantiated.
+- Media packets are not authenticated: Crypto context is automatically instantiated.
+
+It should be noted that use of late binding, when there is no authentication of the SRTP media packets, is subject to numerous security attacks and, consequently, it is not recommended (of course, this can be said for unauthenticated SRTP in general).
+
+Note that use of late binding without authentication will result in local state being created as a result of receiving a packet from any unknown SSRC. Unauthenticated SRTP, therefore, is not recommended because it invites easy denial-of-service attack. In contrast, late binding with authentication does not suffer from this weakness.
+
+### 4.4.2 Sharing of crypto contexts among sessions or SSRCs
+
+With the constraints and procedures described above, it is not necessary to explicitly signal the SSRC, ROC and SEQ for a unicast RTP session. So there are no SRTP crypto-parameters for
+
+signalling SSRC, ROC or SEQ. Thus, multiple SSRCs from the same entity will share SRTP crypto parameters when late binding is used. Multiple SSRCs from the same entity arises due to either multiple sources (microphones, cameras, etc.), or RTP payloads requiring SSRC multiplexing within that same session.
+
+H.245 allows multiple RTP sessions to be defined in the same media description, these RTP sessions will also share the SRTP crypto parameters. An application that uses the SRTP crypto parameter in this way shares a master key among RTP sessions or SSRCs and shall replace the master key when the aggregate number of packets among all SSRCs approaches  $2^{31}$  packets. SSRCs that share a master key shall be unique from one another.
+
+The lifetime of all keys that are derived from a master key are determined by the lifetime of the master key. So if the lifetime of the master key is  $2^{31}$  packets and one derived key has sent  $2^{31} - y$  packets, then only  $y$  packets can be sent by any key derived from that master key. This is because the lifetime is based on the amount of entropy or randomness in the key and no randomness is introduced by deriving a key from a master key, which is all the randomness or entropy that the key has.
+
+### 4.4.3 Removal of crypto contexts
+
+The mechanism defined above addresses the issue of creating crypto contexts. However, in practice, session participants may want to remove crypto contexts prior to session termination. Since a crypto context contains information that cannot automatically be recovered (e.g., ROC), it is important that the sender and receiver agree on when a crypto context can be removed and, perhaps more importantly, when it cannot.
+
+Even when late binding is used for a unicast stream, the ROC is lost and cannot be recovered automatically (unless it is zero) once the crypto context is removed.
+
+Crypto-contexts shall be removed on receipt of a **CloseLogicalChannel**. In addition, crypto-context removal shall follow the same rules as SSRC removal from the member table (RFC 3711); note that this can happen as the result of an SRTCP BYE packet or a simple time-out due to inactivity. Inactive session participants that wish to ensure their crypto contexts are not timed out must thus send SRTCP packets at regular intervals.
+
+# 5 Procedures
+
+The SRTP procedures described below shall only be used to negotiate security for two-party unicast media streams in situations where the H.245 signalling channel is protected by an encapsulating data-security protocol, e.g., IPsec (RFC 2401), TLS (RFC 2246). The exchange of SRTP crypto parameters using H.245 messages shall provide the following functions:
+
+- 1) Exchange and negotiation of SRTP media encryption and integrity capabilities.
+- 2) Negotiation and establishment of the initial encryption and algorithms, keys and session parameters to be used for the SRTP streams in each direction.
+- 3) Modification of encryption and algorithms, keys and session parameters at any time during the SRTP session.
+
+## 5.1 Security capability exchange
+
+The SRTP crypto-suites, the encryption and integrity algorithms, that an H.323 Endpoint is capable of supporting shall be identified by **SrtpCryptoCapability**.
+
+Security capabilities exchange will be provided by existing terminal capabilities exchange using one or more **h235SecurityCapability** entries in the **capabilityTable** of the H.245 **TerminalCapabilitySet** message. The **mediaCapability** field in the **h235SecurityCapability** entry
+
+of the **capabilityTable** is used to associate the security capability with a particular media capability entry in the **capabilityTable**.
+
+The **encryptionAuthenticationAndIntegrity** field in the **h235SecurityCapability** entry contains the **genericH235SecurityCapability** field which will specify the SRTP crypto-suites identified by the H.235.8 OIDs. If the **standard** field of **capabilityIdentifier** of the **genericH235SecurityCapability** field contains the H.235.8 OID (see Table 1) then the **SrtpCryptoCapability** will contain one or more **SrtpCryptoInfo** parameters that represent the crypto-suites that the H.323 Endpoint supports. The **cryptoSuite** field in the **SrtpCryptoInfo** field contains an OID as defined in Table 2 that identifies a particular crypto-suite. Within **SrtpCryptoInfo** field the **sessionParams** field identifies the session parameters and the **allowMKI** field indicates whether the MKI is supported by the H.323 Endpoint.
+
+## 5.2 Initial negotiation
+
+### 5.2.1 Initial crypto offer
+
+Each crypto-offer is transported in a separate **OpenLogicalChannel** message. Each crypto-offer shall contain one **SrtpCryptoInfo** structure in **SrtpCryptoCapability** and one or more **SrtpKeyParameters** structures in **SrtpKeys**.
+
+For normal H.245 (not Fast Connect) procedures the H.323 Endpoint shall include the crypto-offer as described in **SrtpCryptoInfo** and **SrtpKeyParameters** structures in an H.245 **OpenLogicalChannel** message for the forward direction (from the offering H.323 Endpoint to the answering H.323 Endpoint). The H.323 Endpoint should offer the master's most preferred security capability as indicated during the terminal capabilities exchange and for which it itself has capability.
+
+For Fast Connect procedures, the offering H.323 Endpoint shall send each crypto-offer as described in **SrtpCryptoInfo** and **SrtpKeyParameters** structures in separate H.245 **OpenLogicalChannel** messages for the forward direction (from the offering H.323 Endpoint to the answering H.323 Endpoint).
+
+The offered **OpenLogicalChannel** messages shall be ordered by preference, the most preferred crypto-suite being listed first, the more preferred crypto-suites should be cryptographically stronger than less preferred crypto-suites. In general, a more preferred crypto-suite should be cryptographically stronger than a less preferred crypto-suite.
+
+When issuing a crypto-offer, the offerer shall be prepared to support media security in accordance with any of the offered crypto-parameters. There are two problems associated with this. Firstly, the offerer does not know which key the answerer will be using for media sent to the offerer. Since media may arrive prior to the crypto-answer, delay or clipping can occur. If this is unacceptable to the offerer, the offerer should use a mechanism such as H.460.11 delayed call establishment procedures to prevent the above problem.
+
+Another problem can occur when there are multiple offers: The offerer is not able to deduce which of the offers was accepted by the answerer until the crypto-answer is received, yet media may arrive before the crypto-answer. If this is unacceptable to the offerer, the offerer either should not send more than one offer, or a mechanism such as H.460.11 delayed call establishment procedures should be used to prevent the above problem.
+
+The **SrtpCryptoInfo** may include session parameters.
+
+![Sequence diagram showing the Fast connect offer-answer exchange between Endpoint A and Endpoint B. Endpoint A sends an OLC (LCNx, crypto-offer[SrtpSecurityCapability, SrtpKeys]) to Endpoint B. Endpoint B responds with an OLC (LCNy, crypto-answer[SrtpSecurityCapability, SrtpKeys]) to Endpoint A. The diagram is labeled H.235.8_F01.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Endpoint A
+    participant Endpoint B
+    Note right of Endpoint B: H.235.8_F01
+    Endpoint A->>Endpoint B: OLC (LCNx, crypto-offer[SrtpSecurityCapability, SrtpKeys])
+    Endpoint B-->>Endpoint A: OLC (LCNy, crypto-answer[SrtpSecurityCapability, SrtpKeys])
+  
+```
+
+Sequence diagram showing the Fast connect offer-answer exchange between Endpoint A and Endpoint B. Endpoint A sends an OLC (LCNx, crypto-offer[SrtpSecurityCapability, SrtpKeys]) to Endpoint B. Endpoint B responds with an OLC (LCNy, crypto-answer[SrtpSecurityCapability, SrtpKeys]) to Endpoint A. The diagram is labeled H.235.8\_F01.
+
+**Figure 1/H.235.8 – Fast connect offer-answer exchange**
+
+#### 5.2.1.1 Initial crypto-answer
+
+##### 5.2.1.1.1 General
+
+These procedures apply to both Fast Connect and normal H.245 procedures. A crypto-answer shall contain one **SrtpCryptoInfo** structure in **SrtpCryptoCapability** and one or more **SrtpKeyParameters** structures in **SrtpKeys**.
+
+The answering H.323 Endpoint shall apply the crypto-suite selected from the crypto-offer to the corresponding unidirectional SRTP channel in the reverse direction and shall generate the key(s) to be used for that SRTP channel in the reverse direction.
+
+In addition, the answering H.323 Endpoint shall include one or more keys in **SrtpKeys** that are to be used for the SRTP stream from the answering H.323 Endpoint to the offering H.323 Endpoint. The answering H.323 Endpoint may also include any session parameters from the crypto-offer that it wishes to negotiate.
+
+Only parameters that are valid can be accepted; valid parameters do not violate any of the general rules defined for security descriptions as well as any specific rules defined for the transport and key-method in question.
+
+For Fast Connect, when selecting one of the valid crypto-offers, the answerer should select the most preferred crypto-offer it can support, i.e., the first valid supported parameter in the list, considering the answerer's capabilities and security policies. If none of the offers are valid, or none of the valid ones are supported, the offered media stream shall be rejected.
+
+When a crypto-offer is accepted, the crypto-answer shall contain the key(s) the answerer will be using for media sent to the offerer. Note that a key shall be provided, irrespective of any direction parameters in the offer or answer.
+
+Furthermore, any session parameters that are negotiated shall be included in the crypto-answer. Declarative session parameters provided by the offerer are not included in the crypto-answer, however the answerer may provide its own set of declarative session parameters.
+
+Once the answerer has accepted one of the offered crypto parameters, the answerer may begin sending media to the offerer in accordance with the selected crypto-offer. Note however, that the offerer may not be able to process such media packets correctly until the crypto-answer has been received.
+
+##### 5.2.1.1.2 Fast connect procedures
+
+For Fast connect procedures, the answering H.323 Endpoint receiving the crypto-offers in one or more H.245 **OpenLogicalChannel** messages shall respond by accepting one of the crypto-offers by sending an H.245 **OpenLogicalChannel** containing the crypto-answer as shown in Figure 1, or by
+
+rejecting all the crypto-offers by sending a **ReleaseComplete** with **ReleaseCompleteReason** set to **securityDenied**, or by sending a **FastConnectRefused** element in an H.225.0 message. If the answering H.323 Endpoint does not support this Recommendation or any of the proposals in the crypto-offer it shall reject the crypto-offer by sending a **ReleaseComplete** with **ReleaseCompleteReason** set to **securityDenied**, or by sending a **FastConnectRefused** element in an H.225.0 message.
+
+##### 5.2.1.1.3 Normal H.245 procedures
+
+For normal H.245 (not Fast Connect) procedures, the following procedure applies. If the H.323 Endpoint has not already sent an **OpenLogicalChannel** containing a crypto-offer prior to the receipt of **OpenLogicalChannel** containing a crypto-offer it shall send an **OpenLogicalChannelAck** followed by an **OpenLogicalChannel** containing the crypto-answer as shown in Figure 2.
+
+![Sequence diagram illustrating the Offer-answer exchange between two H.323 endpoints. The diagram shows four messages: 1. OLC (LCNx, crypto-offer) from the left H.323 endpoint to the right H.323 endpoint. 2. OLCAck (LCNx) from the right H.323 endpoint to the left H.323 endpoint. 3. OLC (LCNy, crypto-answer) from the right H.323 endpoint to the left H.323 endpoint. 4. OLCAck (LCNy) from the left H.323 endpoint to the right H.323 endpoint, with a label H.235.8_F02 at the end of the message line.](4356776ca004ecba5d599667a155d7d4_img.jpg)
+
+```
+
+sequenceDiagram
+    participant H323_endpoint_1 as H.323 endpoint
+    participant H323_endpoint_2 as H.323 endpoint
+    Note right of H323_endpoint_2: H.235.8_F02
+    H323_endpoint_1->>H323_endpoint_2: OLC (LCNx, crypto-offer)
+    H323_endpoint_2-->>H323_endpoint_1: OLCAck (LCNx)
+    H323_endpoint_2->>H323_endpoint_1: OLC (LCNy, crypto-answer)
+    H323_endpoint_1-->>H323_endpoint_2: OLCAck (LCNy)
+  
+```
+
+Sequence diagram illustrating the Offer-answer exchange between two H.323 endpoints. The diagram shows four messages: 1. OLC (LCNx, crypto-offer) from the left H.323 endpoint to the right H.323 endpoint. 2. OLCAck (LCNx) from the right H.323 endpoint to the left H.323 endpoint. 3. OLC (LCNy, crypto-answer) from the right H.323 endpoint to the left H.323 endpoint. 4. OLCAck (LCNy) from the left H.323 endpoint to the right H.323 endpoint, with a label H.235.8\_F02 at the end of the message line.
+
+Figure 2/H.235.8 – Offer-answer exchange
+
+If the H.323 Endpoint has already sent an **OpenLogicalChannel** containing a crypto-offer prior to the receipt of **OpenLogicalChannel** containing a crypto-offer the action taken by the master and slave H.323 Endpoints is as follows:
+
+- 1) A master H.323 Endpoint shall process the received crypto-offer and if it is compatible with the crypto-offer that it has already sent, it shall accept the received crypto-offer as a crypto-answer by sending an **OpenLogicalChannelAck** as shown in Figure 3. If the received crypto-offer is not compatible with the crypto-offer that it has already sent, it shall reject the received crypto-offer by sending an **OpenLogicalChannelReject** with **cause** value of **securityDenied** as shown in Figure 4. The term compatible means that the following parameters in the crypto-offer shall match the corresponding parameters in the crypto-answer: **cryptoSuite** and the negotiated session parameters.
+- 2) A slave H.323 Endpoint shall process the received crypto-offer and, if it is compatible with the crypto-offer that it has already sent, it shall accept the received crypto-offer as a crypto-answer by sending an **OpenLogicalChannelAck** as shown in Figure 3. If the received crypto-offer is not compatible with the crypto-offer that it has already sent, and if it wishes to accept the crypto-offer, it shall do so by sending the following messages shown in Figure 4:
+  - a) **OpenLogicalChannelAck** to accept the initial crypto-offer from the master;
+  - b) **CloseLogicalChannel** to terminate its own initial crypto-offer if the **OpenLogicalChannelReject** has not already been received from the master;
+  - c) **OpenLogicalChannel** with a crypto-answer that matches the crypto-offer from the master.
+
+If the slave H.323 Endpoint does not support the proposal in the offer or does not wish to accept the crypto-offer it shall reject the crypto-offer by sending an **OpenLogicalChannelReject** with cause set to **securityDenied**.
+
+![Sequence diagram for simultaneous compatible offer-answer exchange between a Master endpoint and a Slave endpoint.](7f25db95ce3916c0e09803b861a2f7bc_img.jpg)
+
+This sequence diagram illustrates a simultaneous compatible offer-answer exchange. It features two vertical lifelines: 'Master endpoint' on the left and 'Slave endpoint' on the right. 
+ 1. The Master endpoint sends an 'OLC (LCNx, crypto-offer)' to the Slave endpoint.
+ 2. Simultaneously, the Slave endpoint sends an 'OLC (LCNy, crypto-offer)' to the Master endpoint.
+ 3. Below the lifelines, two boxes indicate that both endpoints find the offers compatible and treat them as answers.
+ 4. The Master endpoint then sends an 'OLCAck (LCNy)' to the Slave endpoint.
+ 5. Simultaneously, the Slave endpoint sends an 'OLCAck (LCNx)' to the Master endpoint.
+ 6. The diagram is labeled 'H.235.8\_F03' at the bottom right.
+
+Sequence diagram for simultaneous compatible offer-answer exchange between a Master endpoint and a Slave endpoint.
+
+**Figure 3/H.235.8 – Simultaneous compatible offer-answer exchange**
+
+![Sequence diagram for simultaneous incompatible offer-answer exchange between a Master endpoint and a Slave endpoint.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg)
+
+This sequence diagram illustrates a simultaneous incompatible offer-answer exchange. It features two vertical lifelines: 'Master endpoint' on the left and 'Slave endpoint' on the right.
+ 1. The Master endpoint sends an 'OLC (LCNx, crypto-offer)' to the Slave endpoint.
+ 2. Simultaneously, the Slave endpoint sends an 'OLC (LCNy, crypto-offer)' to the Master endpoint.
+ 3. Below the lifelines, two boxes indicate that both endpoints find the offers not compatible.
+ 4. The Master endpoint sends an 'OLCReject (LCNy)' to the Slave endpoint.
+ 5. Simultaneously, the Slave endpoint sends an 'OLCAck (LCNx)' to the Master endpoint.
+ 6. The Slave endpoint then sends an 'OLC (LCNy, crypto-answer)' to the Master endpoint.
+ 7. Finally, the Master endpoint sends an 'OLCAck (LCNy)' to the Slave endpoint.
+ 8. The diagram is labeled 'H.235.8\_F04' at the bottom right.
+
+Sequence diagram for simultaneous incompatible offer-answer exchange between a Master endpoint and a Slave endpoint.
+
+**Figure 4/H.235.8 – Simultaneous incompatible offer-answer exchange**
+
+#### 5.2.1.2 Offerer processing of initial answer
+
+When the offerer receives the crypto-answer, the offerer shall verify that one of the initial crypto-offers was accepted and echoed in the crypto-answer. Also, the crypto-answer shall include one or more keys, which will be used for media sent from the answerer to the offerer.
+
+The offerer shall verify that the keys in the crypto-answer do not match any of the keys in the crypto-offer. If the crypto-offer contained any mandatory negotiated session parameters, the offerer shall verify that said parameters are included in the crypto-answer and match the corresponding parameters in the crypto-offer. If the crypto-answer contains any mandatory declarative session parameters, the offerer shall be able to support those.
+
+If any of the above fails, the negotiation shall be deemed to have failed.
+
+## 5.3 Session modification
+
+Once the SRTP media stream has been established, it may be modified at any time using new offer-answer exchanges to perform re-keying or change the crypto-suite. The new crypto-offer and crypto-answer shall be transported in **SrtpCryptoCapability** and **SrtpKeys** parameters of an H.245 **OpenLogicalChannel** to open a new logical channel that will replace the existing logical channel using **replacementFor** procedures. The offering H.323 Endpoint shall include the crypto-offers in one or more H.245 **OpenLogicalChannel** messages within an H.225.0 message.
+
+The answering H.323 Endpoint receiving the crypto-offers shall respond by accepting one of the offers by sending an H.245 **OpenLogicalChannel** within an H.225.0 message or by rejecting the offers with an **OpenLogicalChannelReject** message with **cause** set to **securityDenied**. If the crypto-offer is rejected, the old crypto parameters remain in place.
+
+When establishing a new master key, there will be a window of time during which the H.323 Endpoint must receive media encrypted according to the old and the new offer-answer exchange. The MKI from the incoming SRTP packet shall be used to associate that packet with either the old master key or the new master key. For this reason, if it is anticipated that keys will be changed during a session that does not change the source/destination addresses and ports, the use of MKI is mandatory to allow the receiver to identify the associated key material during the key change.
+
+## 5.4 No negotiation
+
+In the case of no negotiation of the crypto suite, cryptographic key or session parameters the sender determines the security parameters for the stream. Since there is no negotiation mechanism, the sender shall include exactly one crypto-offer and the receiver shall either accept it or else should reject the offer by sending a **ReleaseComplete** with **ReleaseCompleteReason** set to **securityDenied** or an **OpenLogicalChannelReject** with **cause** set to **securityDenied**. The sender should select the security description that it deems most secure for its purposes.
+
+## 5.5 Forward error correction
+
+A different master key shall be specified to protect a FEC stream that is sent to a different IP address and/or port pair than the SRTP media stream to which it applies as described in RFC 2733, section 11.1. This FEC stream shall be established using a separate H.245 **OpenLogicalChannel** with **dataType** of **fec**. The master key for the FEC stream shall be transported in the **genericKeyMaterial** field of the **secureSharedSecret** (**V3KeySyncMaterial**) parameter contained within the **h235Key** container in the **encryptionSync** parameter of the H.245 **OpenLogicalChannel** message. The master key shall be different from all other master keys offered for the associated media stream.
+
+# 6 Public key cryptography to secure key exchange for SRTP
+
+Public key cryptography procedures may be added to provide end-to-end confidentiality and authentication of the SRTP session key material exchanged between H.323 Endpoints by encrypting and then signing the SRTP key material. Public key cryptography may be used in the case where the encapsulating security protocol, e.g., IPsec, TLS, terminates on an intermediate device and, therefore, does not provide end-to-end security.
+
+The SRTP session key that encrypts the SRTP media from the calling Endpoint to the called Endpoint is encrypted using the public key of the called Endpoint and signed with the private key of the calling Endpoint. Likewise, another SRTP session key that encrypts the SRTP media from the called Endpoint to the calling Endpoint shall be encrypted using the public key of the calling Endpoint and signed with the private key of the called Endpoint. The procedure described in this clause may terminate on a Gateway or Gatekeeper as well as an Endpoint.
+
+The SRTP session key shall be transported using Cryptographic Message Syntax (CMS) bodies within H.245 messages. The Cryptographic Message Syntax (RFC 3852) is used to digitally sign and encrypt arbitrary message content. The CMS syntax allows multiple encapsulations which lets one encapsulation envelope be nested within another. In particular, the SRTP session key material shall be transported within a CMS **EnvelopedData** body which is signed using a CMS **SignedData** body.
+
+## 6.1 Endpoint identification
+
+The following shall be used to identify an Endpoint, Gateway or Gatekeeper in a public key certificate:
+
+- H.323 URL;
+- Non-H.323 standard URL, e.g., *tel*;
+- Device identification/certificate (FFS).
+
+A public key certificate shall be used to assert the association of the identity of the Endpoint with its public key. The H.323 URL or non-H.323 standard URL shall be stored in the **subjectAltName** field of the certificate.
+
+Endpoints may maintain a local key-store that contains the public key certificates of other Endpoints with which it wishes to establish secure end-to-end communications. An Endpoint that sends signed content to provide end-to-end authentication shall include a public key certificate bearing the public key necessary to verify the signature. A receiving Endpoint shall either:
+
+- a) verify that sender's certificate is signed by a recognized certification authority (CA); or
+- b) trust a security assertion upon the certificate given by a third party. The assertion must be signed by globally verifiable key material.
+
+NOTE – This may be advantageous in scenarios where a global user PKI is not available and self-signed certificates or device certificates are being used.
+
+## 6.2 SRTP key exchange procedures
+
+If the calling and called Endpoints wish to ensure end-to-end confidentiality and authentication of their SRTP session key material in the case that the call establishment traverses one or more intermediate signalling devices, they should use public key cryptography and X.509 (RFC 3280) public key certificate exchange.
+
+The offer-answer procedures described in the previous clauses are unchanged except as stated below.
+
+### 6.2.1 Capability exchange
+
+To negotiate the use of public key certificates for SRTP key exchange, the H.323 Endpoint shall set the **genericH235SecurityCapability** within **encryptionAuthenticationAndIntegrity** in an **h235SecurityCapability** entry in the **capabilityTable** of a H.245 **TerminalCapabilitySet** message as follows:
+
+- **capabilityIdentifier** shall contain the H.235.8 CMS Object Identifier (see Table 4) in **standard** field;
+- **maxbitRate**, **collapsing**, **nonCollapsing**, and **transport** shall be unused;
+- **nonCollapsingRaw** shall contain the **SrtpCryptoCapability** parameter.
+
+### 6.2.2 Key exchange
+
+If the SRTP session key is to be encrypted using public keys, then the encrypted SRTP session key is transported within Cryptographic Message Syntax (CMS) bodies in H.245 messages. The CMS **EnvelopedData** body and the CMS **SignedData** body shall be transported instead of **SrtpKeys** in the **genericKeyMaterial** field of the **secureSharedSecret (V3KeySyncMaterial)** parameter contained within the **h235Key** container in the **encryptionSync** parameter of H.245 **OpenLogicalChannel** messages. The CMS **EnvelopedData** body shall be placed into **genericKeyMaterial** field immediately followed by the CMS **SignedData** body.
+
+The structure **SrtpKeys** shall be encrypted using the CMS Content Encryption Key (CEK) and transported in the **EncryptedContentInfo** structure of a CMS **EnvelopedData** body.
+
+The presence of a CMS body containing SRTP session key material in the **genericKeyMaterial** container shall be identified using the H.235.8 CMS Object Identifier value (see Table 4) in the **standard** field of **capabilityIdentifier** within the **genericH235SecurityCapability** field of **encryptionAuthenticationAndIntegrity** in **h235Media** of the OLC **dataType**.
+
+**Table 4/H.235.8 – H.235.8 CMS object identifier**
+
+| OID value                                                   |
+|-------------------------------------------------------------|
+| { itu-t (0) recommendation (0) h (8) 235 version (0) 4 94 } |
+
+## 6.3 CMS body usage
+
+The Endpoint that generates the SRTP session key material **SrtpKeys**, the sending Endpoint, shall encrypt it using the CMS Content Encryption Key (CEK) which is itself encrypted by the public key of the other Endpoint, the recipient Endpoint, and place the encrypted SRTP session key material into a CMS **EnvelopedData** body. The sending Endpoint shall then digitally sign the **EnvelopedData** body with its private key and create a "detached signature" CMS **SignedData** body. The sending Endpoint shall include the certificate with its public key in the CMS **SignedData** body. The sending Endpoint shall send the **EnvelopedData** body with the "detached signature" **SignedData** body to the recipient Endpoint. The creation of the **EnvelopedData** and the **SignedData** bodies by the sending Endpoint are described in more detail in the following clauses.
+
+The **EnvelopedData** body and the "detached signature" **SignedData** body are shown in Figure 5.
+
+![Diagram illustrating the creation of CMS EnvelopedData and SignedData bodies. The process starts with CEK and SRTP key material (SrtpKeys) being encrypted using the Recipient's public key. The resulting encrypted key and content are placed into the CMS EnvelopedData structure. Simultaneously, the SRTP key material is hashed and signed using the Sender's private key, with the Sender's certificate included. This results in the CMS SignedData (detached signature) structure.](5793a44ffdadd039928e2f9fe6daae06_img.jpg)
+
+The diagram illustrates the creation of CMS EnvelopedData and SignedData bodies. On the left, inputs include 'CEK' and 'SRTP key material (SrtpKeys)'. The 'CEK' is input to an 'Encrypt' block along with 'Recipient's public key'. The output of this 'Encrypt' block is 'EncryptedKey', which is part of the 'CMS EnvelopedData' structure. The 'SRTP key material (SrtpKeys)' is input to another 'Encrypt' block, which also uses 'Recipient's public key'. The output of this 'Encrypt' block is 'EncryptedContent', which is also part of the 'CMS EnvelopedData' structure. The 'CMS EnvelopedData' structure is shown as a box containing 'RecipientInfo', 'EncryptedKey', 'EncryptedContentInfo', and 'EncryptedContent'. Below this, the 'SRTP key material (SrtpKeys)' is input to a 'Hash' block. The output of the 'Hash' block is input to a 'Sign' block along with 'Sender's certificate' and 'Sender's private key'. The output of the 'Sign' block is 'Signature', which is part of the 'CMS SignedData (detached signature)' structure. The 'CMS SignedData (detached signature)' structure is shown as a box containing 'SignerInfo', 'Certificate', 'Signature', and 'Content (absent)'. A line connects the 'EncryptedContent' of the 'CMS EnvelopedData' to the 'Content (absent)' of the 'CMS SignedData (detached signature)'.
+
+H.235.8\_F05
+
+Diagram illustrating the creation of CMS EnvelopedData and SignedData bodies. The process starts with CEK and SRTP key material (SrtpKeys) being encrypted using the Recipient's public key. The resulting encrypted key and content are placed into the CMS EnvelopedData structure. Simultaneously, the SRTP key material is hashed and signed using the Sender's private key, with the Sender's certificate included. This results in the CMS SignedData (detached signature) structure.
+
+**Figure 5/H.235.8 – CMS EnvelopedData and SignedData bodies**
+
+### 6.3.1 Sending endpoint procedures
+
+The sending Endpoint shall perform the following procedures to generate, encrypt and sign the SRTP session key material.
+
+#### 6.3.1.1 EnvelopedData body
+
+The sending Endpoint shall construct the **EnvelopedData** body as follows:
+
+- 1) Generate the SRTP session key material **SrtpKeys** for the crypto-suite.
+- 2) Generate a random Content Encryption Key (CEK).
+- 3) Encrypt the CEK using the public key of the recipient Endpoint. It is assumed that sending Endpoint already has the public key and certificate of the recipient Endpoint. Place the identifier of the algorithm used in the encryption of the CEK in the **keyEncryptionAlgorithm** field of the **RecipientInfo.ktri** structure.
+- 4) Place the encrypted CEK in the **encryptedKey** field of a **RecipientInfo** structure of an **EnvelopedData** body. The **rid** field of the **RecipientInfo.ktri** structure is used to identify the certificate and public key of the recipient Endpoint that was used to encrypt the CEK.
+- 5) Encrypt the SRTP key material **SrtpKeys** using the CEK and place the identifier of the algorithm used in the encryption in the **contentEncryptionAlgorithm** field of the **EncryptedContentInfo** structure.
+- 6) Place the encrypted SRTP key material in the **encryptedContent** field of the **EncryptedContentInfo** structure.
+
+#### 6.3.1.2 SignedData body
+
+The sending Endpoint shall construct the "detached signature" **SignedData** body as follows:
+
+- 1) Compute a message digest, or hash value, over the **EnvelopedData** body. The message digest algorithm identifier is placed in the **digestAlgorithm** field of the **SignerInfo** structure.
+- 2) Sign the message digest using the sending Endpoint's private key and place the signature value in the **signature** field of the **SignerInfo** structure. The signature algorithm identifier is placed in the **signatureAlgorithm** field of the **SignerInfo** structure.
+- 3) Place the certificate containing the public key of the sending Endpoint in the **certificates** structure of the **SignerData** structure. The **sid** field of the **SignerInfo** structure shall be set to identify the certificate using either the issuer's distinguished name and certificate serial number, or the X.509 subjectKeyIdentifier extension value.
+- 4) The **eContentType** field of the **encapContentInfo** structure in the **SignedData** body shall contain the Object Identifier id-envelopedData. The **eContent** field of the **encapContentInfo** structure in the **SignedData** body shall be absent as this is a detached signature and the actual signed content is the **EnvelopedData** body.
+
+### 6.3.2 Recipient endpoint procedures
+
+The recipient Endpoint shall perform the following procedures to verify and decrypt the SRTP session key material.
+
+If the recipient Endpoint encounters any validation failure in the procedures described below, the call is rejected by sending a **ReleaseComplete** with **ReleaseCompleteReason** set to **securityDenied**, or by sending a **FastConnectRefused** element in an H.225.0 message.
+
+#### 6.3.2.1 SignedData body
+
+The recipient Endpoint shall verify the received "detached signature" **SignedData** body as follows:
+
+- 1) Obtain the sending Endpoint's certificate from the **certificates** structure of the **SignerData** structure.
+- 2) Validate the sending Endpoint's certificate. Details of certificate path validation are beyond the scope of this Recommendation. If the recipient is unable to authenticate the sending Endpoint, it may reject the call.
+- 3) The recipient Endpoint may then add the validated certificate to its key-store.
+- 4) Verify the signature value in the **signature** field of the **SignerInfo** structure using the sending Endpoint's public key from the validated certificate. Use the signature algorithm specified in the **signatureAlgorithm** field of the **SignerInfo** structure. The result of the decryption is the message digest over the **EnvelopedData** body computed by the sending Endpoint.
+- 5) Compute the message digest over the received **EnvelopedData** body using the message digest algorithm identifier specified in the **digestAlgorithm** field of the **SignerInfo** structure.
+- 6) Compare the decrypted message digest value with the computed message digest value. If the message digests match, the **EnvelopedData** body may then be processed. If the message digests do not match, the recipient endpoint shall reject the call.
+
+#### 6.3.2.2 EnvelopedData body
+
+The recipient Endpoint shall extract the SRTP session key material from the **EnvelopedData** body as follows:
+
+- 1) Use the **rid** field of the **RecipientInfo** structure to identify the certificate and corresponding private key of the recipient Endpoint in the recipient Endpoint's key-store. If the recipient Endpoint receives an **EnvelopedData** body that is encrypted with a public key that is unknown to the recipient, it shall reject the call.
+- 2) Extract the encrypted CEK from the **encryptedKey** field of a **RecipientInfo.ktri** structure of an **EnvelopedData** body.
+- 3) Decrypt the encrypted CEK using the private key of the recipient Endpoint and the algorithm specified in the **keyEncryptionAlgorithm** field of the **RecipientInfo.ktri** structure.
+- 4) Extract the encrypted SRTP session key material from the encrypted SRTP session key material in the **encryptedContent** field of the **EncryptedContentInfo** structure.
+- 5) Decrypt the encrypted SRTP session key material using the CEK and the algorithm specified in the **contentEncryptionAlgorithm** field of the **EncryptedContentInfo** structure.
+
+# 7 H.235 SRTP security descriptions syntax
+
+The ASN.1 syntax is defined below.
+
+```
+H235-SRTP DEFINITIONS AUTOMATIC TAGS ::=
+BEGIN
+
+IMPORTS
+    GenericData
+FROM H323-MESSAGES;
+
+SrtpCryptoCapability ::= SEQUENCE OF SrtpCryptoInfo -- used in H.245
+genericH235SecurityCapability
+
+SrtpCryptoInfo ::= SEQUENCE
+{
+    cryptoSuite           OBJECT IDENTIFIER OPTIONAL ,
+    sessionParams         SrtpSessionParameters OPTIONAL,
+    allowMKI            BOOLEAN OPTIONAL,
+    ...
+}
+
+SrtpKeys ::= SEQUENCE OF SrtpKeyParameters -- used in H.235 V3KeySyncMaterial
+
+SrtpKeyParameters ::= SEQUENCE
+{
+    masterKey             OCTET STRING,
+    masterSalt            OCTET STRING,
+    lifetime              CHOICE
+    {
+        powerOfTwo          INTEGER,
+        specific            INTEGER,
+        ...
+    } OPTIONAL,
+    mki                   SEQUENCE
+    {
+        length              INTEGER(1..128),
+        value               OCTET STRING,
+        ...
+    } OPTIONAL,
+    ...
+}
+
+SrtpSessionParameters ::= SEQUENCE
+{
+    kdr                   INTEGER(0..24) OPTIONAL, -- power of 2
+    unencryptedSrtp       BOOLEAN OPTIONAL,
+    unencryptedSrtcp      BOOLEAN OPTIONAL,
+    unauthenticatedSrtp   BOOLEAN OPTIONAL,
+    fecOrder              FecOrder OPTIONAL,
+    windowSizeHint        INTEGER(64..65535) OPTIONAL,
+    newParameter          SEQUENCE OF GenericData OPTIONAL,
+    ...
+}
+
+FecOrder ::= SEQUENCE
+{
+    fecBeforeSrtp         NULL OPTIONAL,
+    fecAfterSrtp          NULL OPTIONAL,
+    ...
+}
+
+END
+```
+
+
+
+
+
+## **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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.9-200509-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/H/T-REC-H.235.9-200509-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fe989180e91803be37cb088c96ce0410eeace6f4
--- /dev/null
+++ b/marked/H/T-REC-H.235.9-200509-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cceef00f960effe1751f248ecb9baa68cbc2ce5ea866e036cbee722445742ecd
+size 59720
diff --git a/marked/H/T-REC-H.235.9-200509-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg b/marked/H/T-REC-H.235.9-200509-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fbc5c6611b25e3090f10a5921be19f640aa4ba11
--- /dev/null
+++ b/marked/H/T-REC-H.235.9-200509-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b75656de1d4be5b76ecd6fe31e5443e223ecd244d8bdba8359f3a55e61f6c765
+size 74979
diff --git a/marked/H/T-REC-H.235.9-200509-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/H/T-REC-H.235.9-200509-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f734d52ab3069c72b3dbbb74a4f54b57a2cc7520
--- /dev/null
+++ b/marked/H/T-REC-H.235.9-200509-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6364205ea3b1c7de05662be0f1fb6364ebf9502a852bf7fe4fdacdcc2a5541f0
+size 29514
diff --git a/marked/H/T-REC-H.235.9-200509-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.235.9-200509-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..35d080739dd40d3a774e0eb22c42d16e417ea49a
--- /dev/null
+++ b/marked/H/T-REC-H.235.9-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.9-200509-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/H/T-REC-H.235.9-200509-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ea5e0982668d7978bc60a9a31a9f256211ad8e64
--- /dev/null
+++ b/marked/H/T-REC-H.235.9-200509-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cca85da37fb0b7e7e13830bc5f3d25e054fc683a667dc97f788392ec0e54f854
+size 101074
diff --git a/marked/H/T-REC-H.235.9-200509-I_PDF-E/raw.md b/marked/H/T-REC-H.235.9-200509-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..7b0eaf6a5de64d9d6af393aafe6702ae0e58ab8b
--- /dev/null
+++ b/marked/H/T-REC-H.235.9-200509-I_PDF-E/raw.md
@@ -0,0 +1,459 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.235.9**
+
+(09/2005)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS  
+Infrastructure of audiovisual services – Systems aspects
+
+---
+
+**H.323 security: Security gateway support for  
+H.323**
+
+ITU-T Recommendation H.235.9
+
+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 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        |
+| <b>Systems aspects</b>                                                        | <b>H.230–H.239</b> |
+| 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.9**
+
+## **H.323 security: Security gateway support for H.323**
+
+## **Summary**
+
+This Recommendation defines a method for the discovery of Security Gateways in the signalling path between communicating H.323 entities, and for sharing of security information between a gatekeeper and the SGs in order to preserve signalling integrity and privacy.
+
+## **Source**
+
+ITU-T Recommendation H.235.9 was approved on 13 September 2005 by ITU-T Study Group 16 (2005-2008) under the ITU-T Recommendation A.8 procedure.
+
+## **Keywords**
+
+Gateway, security, signalling.
+
+## 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 .....                               | 1    |
+| 4 Abbreviations.....                              | 2    |
+| 5 Conventions .....                               | 2    |
+| 6 Basic operation .....                           | 4    |
+| 6.1 Endpoint gatekeeper discovery.....            | 4    |
+| 6.2 Endpoint authentication key distribution..... | 5    |
+| 6.3 Address manipulation.....                     | 6    |
+| 7 Signalling details .....                        | 7    |
+| 8 SG configuration considerations.....            | 8    |
+| 8.1 SG registration.....                          | 8    |
+| 8.2 Authentication credentials .....              | 9    |
+| 9 Security considerations.....                    | 9    |
+| 10 Applicability .....                            | 10   |
+| 11 Object Identifier.....                         | 10   |
+
+## Introduction
+
+The use of Firewalls and/or Network Address Translation devices to provide traffic security between network regions under different administrative controls creates problems for telephony signalling protocols that must exchange network addresses for signalling and media exchange.
+
+ITU-T Rec. H.235.5 introduces a framework by which an endpoint and its gatekeeper, or two gatekeepers, can use the initial RAS messages to negotiate a set of strong-shared secrets between them, and use those secrets to encrypt selected parts of subsequent RAS and call signalling messages and to authenticate those messages. The method applies to gatekeeper-routed signalling only. Similar methods and security profiles are defined by ITU-T Recs H.235.1, H.235.2 and H.235.3. This security can come into conflict with Application Level Gateways (ALGs) which interconnect network realms and manipulate the signalling and media transport addresses carried in the H.225.0 RAS and/or call signalling messages. Such changes in the message will cause the message authentication check to fail at the destination.
+
+This Recommendation describes a simple means by which the gatekeeper may be informed of the ALGs in a signalling path, and may share the negotiated signalling authentication key with those ALGs. This will permit the ALGs to manipulate non-private data, particularly transport addresses, in the signalling messages, and then authenticate the result before passing the modified messages onward. Such devices are referred to as Security Gateways (SGs) in the subsequent text. This technique retains the end-to-end privacy of any encrypted elements in the signalling.
+
+## H.323 security: Security gateway support for H.323
+
+# 1 Scope
+
+This Recommendation is usable by any gatekeeper and endpoint using the H.225.0 RAS protocols, with one or more intervening Security Gateways with the prescribed behaviour.
+
+# 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.2 (2005), *H.323 security: Signature security profile*.
+- ITU-T Recommendation H.235.3 (2005), *H.323 security: Hybrid security profile*.
+- ITU-T Recommendation H.235.5 (2005), *H.323 security: Framework for secure authentication in RAS using weak shared secrets*.
+- ITU-T Recommendation H.245 (2005), *Control protocol for multimedia communication*.
+- ITU-T Recommendation H.323 (2003), *Packet-based multimedia communications systems*.
+
+## 2.2 Informative references
+
+- IETF RFC 2246 (1999), *The TLS Protocol Version 1.0*.
+- IETF RFC 3546 (2003), *Transport Layer Security (TLS) Extensions*.
+- IETF RFC 2401 (1998), *Security Architecture for the Internet Protocol*.
+
+# 3 Definitions
+
+This Recommendation defines the following terms:
+
+**3.1 application level gateway:** A protocol-aware device that interconnects two or more network regions which is able to interpret and modify the application level protocols to provide transport address translations and other functions. An ALG may provide transport level NAT and firewall functions internally, or may control them externally.
+
+**3.2 local address:** A transport address within a local address realm.
+
+- 3.3 media gateway:** A device which interconnects two or more network realms and which can be controlled by another device (e.g., an SG) to provide controlled media flows between realms. The MG is effectively a programmable NAT/firewall operating at the transport layer and below.
+- 3.4 network address translation:** The operation of mapping network transport addresses from one network realm to another.
+- 3.5 pinhole:** A flow path through an SG (or a media gateway under its control) by which packets or messages are permitted to move from one realm to another. A pinhole is typically characterized by four transport addresses (the realm A source address, the SG realm A address, the SG realm B address, and the realm B destination address), and other characteristics such as transport protocol and directionality. The source address may be unspecified, e.g., for a listen port.
+- 3.6 realm:** A network region which shares a common network address space; by presumption, different realms use incompatible, conflicting, or private address spaces.
+- 3.7 security gateway:** A device installed between two or more IP network regions in order to perform security functions such as the validation or restriction of packet flows and the mapping of transport addresses between network regions. For this Recommendation, it is assumed that the Security Gateway is an ALG knowledgeable of H.323 signalling protocols.
+
+# 4 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+|     |                                    |
+|-----|------------------------------------|
+| ALG | Application Level Gateway          |
+| GCF | GatekeeperConfirm                  |
+| GK  | Gatekeeper                         |
+| GRJ | GatekeeperReject                   |
+| LCF | LocationConfirm                    |
+| LRQ | LocationRequest                    |
+| MG  | Media Gateway                      |
+| NAT | Network Address Translation        |
+| OID | Object Identifier                  |
+| RAS | Registration, Admission and Status |
+| SG  | Security Gateway                   |
+| UDP | User Datagram Protocol             |
+
+# 5 Conventions
+
+This Recommendation defines various object identifiers (OIDs) for signalling security capabilities, procedures or security algorithms. These OIDs relate to a hierarchical tree of assigned values that may originate from external sources or are part of the ITU-T maintained OID tree. Those OIDs that are specifically related to ITU-T Rec. H.235 have the following appearance in the text:
+
+"OID" = {itu-t (0) recommendation (0) h (8) 235 version (0) V N} where V symbolically represents a single decimal digit denoting the corresponding version of ITU-T Rec. H.235; e.g., 1, 2, 3 or 4. N symbolically represents a decimal number uniquely identifying the instance of the OID and thus, the procedure, algorithm or security capability.
+
+Thus, the ASN.1 encoded OID consists of a sequence of numbers. For convenience, a textual mnemonic shorthand string notation for each OID is used in the text such as "OID". A mapping is
+
+given that relates each OID string with the ASN.1 sequence of numbers. Implementations conforming to ITU-T Rec. H.235 shall use only the ASN.1 encoded numbers
+
+## Basic Assumptions
+
+This Recommendation considers an IP network model in which multiple network regions, called realms, are interconnected by devices called Security Gateways (SGs) which are H.323 protocol aware, and which are designed to control information flows between the network realms they interconnect. The SGs are expected to examine signalling messages flowing between realms, insure their validity, and extract transport address information being exchanged, and use that transport information to construct appropriate flow paths between the realms, and to modify the transport addresses as appropriate for the realm to which the message is forwarded. The SGs must insure the signalling paths flow through themselves, of course, but they may control another device to support any media flows that are established. The control protocol between the SG and the "media gateway" is not specified by this Recommendation.
+
+In order to make the services of a gatekeeper in one realm available to endpoints or gatekeepers in another realm, an SG may provide a gatekeeper discovery address in each realm it serves in which there is no known gatekeeper. The SG would then forward any discovery message received on one of those addresses on toward the actual gatekeeper after performing any necessary processing of the H.323 message. An example configuration is illustrated in Figure 1, which shows a gatekeeper serving endpoints in multiple network realms.
+
+In effect, the Security Gateways must represent the gatekeeper in each of the realms they serve (except, of course, the realm in which the gatekeeper resides, e.g., realm A for gatekeeper A in the diagram). SG B provides discovery addresses for both gatekeepers in the figure, thus it provides a gatekeeper-to-gatekeeper path for LRQ/LCF signalling. Note also that an SG need not provide access to every gatekeeper in every realm. For example, in Figure 1, SG A might be configured to supply a discovery address in realm B only for gatekeeper A.
+
+It is assumed that each gatekeeper knows a unique name for each SG in the system, and that the gatekeeper and each SG also share a cryptographically strong secret that may be used to communicate securely between them. The manner in which these identities, and the corresponding keys, are negotiated or exchanged is discussed below, but is not the main subject of this Recommendation. The shared secrets should be unique per SG/gatekeeper pair. It is assumed that the SGs will modify the RAS and call signalling addresses exchanged to insure that the RAS and call signalling traffic passes through them.
+
+![Diagram of Security gateway configuration showing four realms (A, B, C, D) connected via Security Gateways (A and B) and Gatekeepers (A and C).](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg)
+
+The diagram illustrates a network configuration with four realms represented as orange clouds: Realm A, Realm B, Realm C, and Realm D. 
+ 
+
+- Realm A is connected to a 'Gatekeeper A' (server icon) and a telephone icon. It is also connected to 'Security GW A'.
+- Realm B is connected to 'Security GW A' and two telephone icons.
+- Realm C is connected to 'Security GW B' and a telephone icon. It is also connected to 'Gatekeeper C' (server icon).
+- Realm D is connected to 'Security GW B' and a telephone icon.
+
+ 'Security GW A' is positioned between Realm A and Realm B. 'Security GW B' is positioned between Realm A and Realm C. 
+ Callouts with letters 'A' and 'C' are shown near the gatekeepers and security gateways, representing local addresses. A legend at the bottom left shows a circle with an 'X' and the text 'Local Address within realm of Gatekeeper X'. The diagram is labeled 'H.235.9\_F01' in the bottom right corner.
+
+Diagram of Security gateway configuration showing four realms (A, B, C, D) connected via Security Gateways (A and B) and Gatekeepers (A and C).
+
+**Figure 1/H.235.9 – Security gateway configuration**
+
+In addition, the means by which routing and/or address translation for the initial discovery process is established is not the main subject of this Recommendation, but is discussed below. Subsequent address establishment, along with any required translations, are presumed to be carried out as part of the operation of the SGs.
+
+# 6 Basic operation
+
+The following description assumes that each SG present in the system has registered with each gatekeeper it is expected to serve. The details of how this may be done are described later. For the basic operation, it is assumed that the SG has identified itself to each gatekeeper, shares a unique, strong secret with each gatekeeper, and provides one or more "local" gatekeeper discovery addresses for each gatekeeper. The details of SG registration will be discussed in a later clause. The following describes how the SGs participate in endpoint registration in order to obtain access to the end-to-end authentication key negotiated between the GK and the endpoint.
+
+## 6.1 Endpoint gatekeeper discovery
+
+When an endpoint sends a GRQ to a gatekeeper discovery address, and the GRQ passes through an SG enroute to one or more gatekeepers, the SG may add a **ClearToken** to the GRQ.token element as it manipulates addresses within the GRQ. This **ClearToken** will be identified as an SG-id token (via its **tokenOID**), and will contain an identification string that uniquely identifies the SG. The SG
+
+should remove, from the GRQ's **authenticationCapability** profile, any particular **AuthenticationMechanism** (e.g., TLS in RFC 2246 and RFC 3546 or IPsec in RFC 2401) whose message authentication procedure it is unable to support. This will insure that the gatekeeper will select a profile that is compatible with the SG. The first SG to receive the GRQ shall include an element identifying the discovery address at which it received the GRQ from the endpoint.
+
+It is implicitly assumed that each SG will manipulate any signalling address fields within the GRQ and subsequent RAS messages to insure that all signalling messages flow through the SG for address processing.
+
+## 6.2 Endpoint authentication key distribution
+
+When the GRQ reaches the gatekeeper (GK), the gatekeeper will process the GRQ, including the SG-id token. Assuming the GK will act as the endpoint's gatekeeper, it will prepare to send a GCF back to the endpoint. The GK will then include, in the GCF message, the chosen **AuthenticationMechanism**, along with an SG-key **ClearToken** (identified by its **tokenOID**) for the SG identified by the SG-id token received. This key token will include the identification of the SG, the identification of the GK, an initialization vector, and the session authentication key encrypted using the IV, and the secret shared between the SG and the gatekeeper. The encryption algorithm shall be negotiated during SG registration, or pre-provisioned.
+
+As the GCF is passed back along the path to the endpoint, it passes through the SG that supplied the SG-id token. The SG shall parse the message to obtain the session ID and its own key token. It shall then decrypt the session authentication key and use it to authenticate the received message. If the message is authentic, the SG will manipulate any transport addresses as appropriate, then rebuild the message without its own SG-key token, insert an SG-NAT token if one is not already present, then authenticate the rebuilt message and send it on. The session ID and authentication key shall be preserved for use with subsequent RAS and call signalling messages for that session. The basic sequence through a single SG is illustrated in Figure 2. Note also that the SG must prepare any pinholes as inferred from the GCF (e.g., a RAS pinhole and alternate GK address pinholes.)
+
+![Sequence diagram showing the basic SG traversal exchange between an Endpoint in Realm X and a Gatekeeper in Realm Y via SG A.](7e670a2b556b53ea9002dfff3a420e08_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Endpoint
+    participant SG_A as SG A
+    participant Gatekeeper
+    Note right of SG_A: Realm Y
+    Note left of SG_A: Realm X
+    Endpoint->>SG_A: GRQ(SP2, AddrX)
+    SG_A->>Gatekeeper: GRQ(SP2, AddrY, SGID(A*))
+    Gatekeeper-->>SG_A: GCF(SP2, AddrY, SGKEY(A, K_a), SID, CY)
+    SG_A-->>Endpoint: GCF(SP2, AddrX, SID, SGNAT, CX)
+  
+```
+
+The diagram illustrates the message exchange for SG traversal. It is divided into two realms: Realm X (containing the Endpoint) and Realm Y (containing the Gatekeeper). The exchange proceeds as follows:
+ 
+
+- The Endpoint sends a GRQ(SP2, AddrX) to SG A.
+- SG A forwards the GRQ to the Gatekeeper as GRQ(SP2, AddrY, SGID(A\*)), where AddrY is the discovery address and SGID(A\*) identifies SG A.
+- The Gatekeeper responds with a GCF(SP2, AddrY, SGKEY(A, K<sub>a</sub>), SID, CY), where SGKEY(A, K<sub>a</sub>) is the ClearToken for SG A.
+- SG A receives the GCF and forwards it to the Endpoint as GCF(SP2, AddrX, SID, SGNAT, CX), where SGNAT is the SG-NAT token and CX is the message checksum.
+
+Sequence diagram showing the basic SG traversal exchange between an Endpoint in Realm X and a Gatekeeper in Realm Y via SG A.
+
+SP2 = H.235.5 security profile
+
+Addr<sub>x</sub> = addresses in the x realm
+
+SGID(A\*) = SG-id ClearToken identifying presence of SG A
+
+(\* indicates SGID includes discovery address used by GRQ.)
+
+SID = session ID (assigned by Gatekeeper)
+
+K<sub>a</sub> = message authentication key for SID
+
+SGKEY(A, K<sub>a</sub>) = SG-key ClearToken with K<sub>a</sub> encrypted under A's secret key.
+
+SGNAT = SG-NAT ClearToken
+
+CX = message checksum (computed using negotiated K<sub>a</sub>) in realm x
+
+**Figure 2/H.235.9 – Basic SG traversal exchange**
+
+This scheme easily extends to a series of SGs between the endpoint and the gatekeeper. Each SG adds its own ClearToken to the GRQ as it passes through, and strips off its own reply ClearToken from the GCF as it passes back from the Gatekeeper to the endpoint. The first SG in the path back
+
+to the endpoint shall insert the SG-NAT token in the GCF. Figure 3 shows this operation. The processing of subsequent RAS messages is illustrated by showing the transformation of transport addresses in an RRQ message, and the recomputed checksum.
+
+A similar sequence may be carried out in an LRQ/LCF exchange, using the same message elements, and the results may be used to process and authenticate subsequent signalling messages for that session.
+
+![Sequence diagram illustrating a two-level SG traversal exchange between an Endpoint in Realm X, SG A, SG B, and a Gatekeeper in Realm Z. The diagram shows the flow of GRQ, GCF, and RRQ messages across the realms, with address and token transformations at each SG.](042733dc5e8e7f5f30b60adba3266cde_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Endpoint
+    participant SG_A as SG A
+    participant SG_B as SG B
+    participant Gatekeeper
+
+    Note right of Gatekeeper: H.235.9_F03
+
+    Endpoint->>SG_A: GRQ(SP2, AddrX)
+    SG_A->>SG_B: GRQ(SP2, AddrY, SGID(A*))
+    SG_B->>Gatekeeper: GRQ(SP2, AddrZ, SGID(A*), SGID(B))
+    Gatekeeper-->>SG_B: GCF(SP2, AddrZ, SGKEY(A,Ka), SGKEY(B,Ka), SID, CZ)
+    SG_B-->>SG_A: GCF(SP2, AddrY, SGKEY(A,Ka), SID, SGNAT, CY)
+    SG_A-->>Endpoint: GCF(SP2, AddrX, SID, SGNAT, CX)
+    Endpoint->>SG_A: RRQ(SP2, AddrX, CX)
+    SG_A->>SG_B: RRQ(SP2, AddrY, CY)
+    SG_B->>Gatekeeper: RRQ(SP2, AddrZ, CZ)
+  
+```
+
+Sequence diagram illustrating a two-level SG traversal exchange between an Endpoint in Realm X, SG A, SG B, and a Gatekeeper in Realm Z. The diagram shows the flow of GRQ, GCF, and RRQ messages across the realms, with address and token transformations at each SG.
+
+SP2 = H.235.5 security profile
+
+Addrx = addresses in the x realm
+
+SGID(A\*) = SG-id ClearToken identifying presence of SG A
+
+(\* indicates presence of discovery address used by endpoint.)
+
+SID = session ID (assigned by Gatekeeper)
+
+K<sub>a</sub> = message authentication key for SID
+
+SGKEY(A, K<sub>a</sub>) = SG-key ClearToken with K<sub>a</sub> encrypted under A's secret key.
+
+SGNAT = SG-NAT ClearToken
+
+Cx = message checksum in the x realm
+
+**Figure 3/H.235.9 – Two-level SG traversal exchange**
+
+## 6.3 Address manipulation
+
+As each H.225.0 or H.245 signalling message passes through it, the SG must examine and replace any transport addresses carried therein so that they are valid within the next realm through which the message will travel. This may require the SG to establish new flow pinholes to support the associated signalling and/or media flows these addresses are meant to establish. Note that some addresses represent listen ports that must be opened "just in case"; a fully-specified pinhole will be created when/if a packet arrives at the listen port.
+
+Each SG may examine each received destination transport address to see if it actually represents a destination address on that SG. Consider the example realm configuration and media paths in Figure 4. A media stream from an endpoint in realm B to an endpoint in realm C must flow through SGs B and C as illustrated by the flow labelled "1". Without any special processing by SG B, a media stream between two endpoints in realm B would follow an equivalent path up to realm A and back to realm B, as illustrated by the flow labelled "2". Now, if SG B recognizes that the source and destination addresses supplied for the flow in realm A are actually addresses on SG B, then it can "short-circuit" the flow in either of two ways: it can route the flow internally, as illustrated by flow "3" (shown on SG C for clarity), or, if it recognizes that both endpoints reside in realm B, it can substitute realm B endpoint addresses to route the flow directly between the endpoints as shown by flow "4". Note that the "endpoint" addresses as seen by SG B might actually be addresses on an SG
+
+(call it D) connecting to another realm. After SG B modifies the addresses to perform "direct" routing between addresses on SG D, SG D may then short-cut the flows in the same manner.
+
+![Diagram illustrating media paths in a network architecture. A central 'Gatekeeper' is connected to 'Realm A'. 'Realm A' is connected to 'SG B' and 'SG C'. 'SG B' is connected to 'Realm B', which contains two endpoints. 'SG C' is connected to 'Realm C', which also contains two endpoints. Dashed lines represent media paths between endpoints. Numbered circles 1, 2, 3, and 4 indicate specific media paths: 1 is a path from an endpoint in Realm C to an endpoint in Realm B via SG C and SG B; 2 is a path between two endpoints in Realm B; 3 is a path from an endpoint in Realm B to an endpoint in Realm C via SG B and SG C; 4 is a path between two endpoints in Realm C. The diagram is labeled H.235.9_F04 and includes a legend for 'Media path'.](4e4be0bd8b235167902f2c03e41da651_img.jpg)
+
+Diagram illustrating media paths in a network architecture. A central 'Gatekeeper' is connected to 'Realm A'. 'Realm A' is connected to 'SG B' and 'SG C'. 'SG B' is connected to 'Realm B', which contains two endpoints. 'SG C' is connected to 'Realm C', which also contains two endpoints. Dashed lines represent media paths between endpoints. Numbered circles 1, 2, 3, and 4 indicate specific media paths: 1 is a path from an endpoint in Realm C to an endpoint in Realm B via SG C and SG B; 2 is a path between two endpoints in Realm B; 3 is a path from an endpoint in Realm B to an endpoint in Realm C via SG B and SG C; 4 is a path between two endpoints in Realm C. The diagram is labeled H.235.9\_F04 and includes a legend for 'Media path'.
+
+Figure 4/H.235.9 – Media paths
+
+One configuration that is not handled by this scheme is the case where one region gains access to another region via more than one SG. If an endpoint registers and signals through one SG, and another endpoint in the same region signals through a second SG, then it will be difficult for either SG to discover that both endpoints are in the same realm, or what addresses to use for the endpoint which signals through the other SG. To avoid this problem, it is convenient to employ a single SG that is capable of processing the expected level of signalling; the media flow processing load can be relegated to separate media gateways under control of the SG.
+
+# 7 Signalling details
+
+Support for this capability is most effectively identified via a standard object identifier (OID) in the applicable clear tokens. In the following, these tokens will be referred to as SG tokens. This permits the feature to be ignored by any receiving gatekeeper (or intervening gateway or other device that does not participate). The assigned OID will be used to identify **ClearTokens** which carry the following elements:
+
+- **tokenOID** – set to the OID assigned to this feature, call it "SG1", see clause 11.
+- **generalID** – if present, set to the name of the SG to which this **ClearToken** is directed (used in the SG-key token).
+- **sendersID** – set to the name of the SG which created this **ClearToken** (used in the SG-id token).
+- **profileInfo** – contains the specific information carried by this **ClearToken**, as specified in Table 1.
+
+**Table 1/H.235.9 – Profile elements for SG discovery**
+
+| Element name  | ElementID value | Element type (length) | Element description                                                                                                                                                                                                                 |
+|---------------|-----------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Token Type    | 1               | integer               | 0 = SG-id token<br>1 = SG-key token<br>2 = SG-NAT token<br>3 = SG-register token                                                                                                                                                    |
+| Encrypted Key | 2               | octets (16 for SP2)   | Session authentication key from the indicated security profile, encrypted under the secret shared between the specified SG and the GK. Sent in SG-key token. The necessary IV for decryption is specified in ProfileElement.paramS. |
+| ServedRealm   | 3               | name                  | Name of Realm in which SG can/should provide a gatekeeper discovery address                                                                                                                                                         |
+
+# 8 SG configuration considerations
+
+The procedures described in this Recommendation depend on some means for the SGs in the network to discover paths to the gatekeeper(s) whose services are to be made accessible to users in different realms of the network. Each SG must be able to contact its gatekeeper (or gatekeepers) in one realm, and provide access to those gatekeepers from endpoints (or other gatekeepers) in the other realm. For example, in Figure 3, SG B accesses the gatekeeper in realm Z. It can provide access to the gatekeeper for elements in realm Y. Thus, SG A can access the gatekeeper through SG B. Once SG B has access to the gatekeeper, it can provide access for parties in realm X. This suggests the use of a discovery protocol such as RAS by the SGs themselves. These procedures could also be used to identify each SG to each gatekeeper it can access, and to negotiate (a set of) keys to protect the user signalling exchanges.
+
+## 8.1 SG registration
+
+An SG may serve as a representative, within a realm, of a gatekeeper in another realm to which the SG has access. For example, in Figure 1, SG A can provide a representation (a discovery address) in realm B for the gatekeeper in realm A, once it knows the gatekeeper's discovery address in realm A. This technique can be extended to several levels of SGs; as each SG discovers a gatekeeper (or a representative) it can provide a discovery address for that gatekeeper in one or more new realms, at which point SGs connected to that realm can discover those new addresses.
+
+SGs shall use H.225.0 RAS procedures to discover and register with gatekeepers in any realm to which they want to provide service as a Security Gateway. An SG shall identify itself as a **gateway** endpoint type. The SG may specify protocol support for H.323 if it wishes to specify supported prefixes and/or bandwidth limitations, but this is not required. Standard security procedures such as those described in ITU-T Recs H.235.1, H.235.2, H.235.3 and H.235.5 shall be used to authenticate the SG to the gatekeeper and to negotiate secure shared secrets to be used in the procedures described below. H.235.1, H.235.2, H.235.3 and H.235.5 procedures can pass through other security gateways supporting this Recommendation. The SG must also include an SG-register ClearToken in the RRQ it sends toward the gatekeeper. This token serves to identify the gateway as an SG, and it shall contain a **ServedRealm** element for each new realm the SG will serve. Each element represents a potential new gatekeeper discovery address in its respective realm. Each SG may be configured to restrict the realms to which it will provide discovery addresses for a gatekeeper. For example, in Figure 1, SG B might be configured to not provide a discovery address for gatekeeper C in realm D, thus forcing endpoints in realm D to register to gatekeeper A. Insofar
+
+as the SG does not itself make or receive calls, it need not supply a call signalling address during its registration; it may provide an empty **SEQUENCE** for **callSignalAddress** in the RRQ. The gatekeeper shall respond in kind in **callSignalAddress** of the RCF.
+
+The gatekeeper shall indicate which realm(s) for which the SG may provide service by returning, in the RCF, an SG-register token containing one or more of the **ServedRealm** elements from the SG's RRQ. Once registration is complete, the SG shall open a listen socket for a gatekeeper discovery address in each indicated realm. Mechanisms outside this Recommendation may be used to announce this discovery address within the realm. The gatekeeper may choose to use the discovery addresses supplied by the SG in a list of alternate addresses.
+
+Any RAS security profile may be used, so long as the SGs are permitted to read and manipulate the signalling and media transport addresses exchanged and may re-authenticate the message.
+
+The gatekeeper can make use of SG realm information to map network regions and connectivity, and to authenticate the SG. The gatekeeper should provide information back to the SG:
+
+- The gatekeeper's credentials.
+- Registration address(es) the SG may use to relay RAS requests from endpoints in the region(s) it serves (i.e., the GK can decline to support endpoints in one or more regions served by the SG.).
+
+One important result of successful SG registration should be a strong secret key shared between the SG and the gatekeeper from which encryption and/or authentication keys may be derived. The authentication key may be used to authenticate the SG registration scheme, and the encryption key should be used during endpoint registrations to encrypt the endpoint session authentication key for distribution to the SG, as described above.
+
+## 8.2 Authentication credentials
+
+Unlike the number of endpoints, the number of SGs in a multi-region network is expected to be relatively small. In most cases, it is expected that service will be provided by subscription, or other contractual agreement, hence the gatekeeper will be provisioned with some identifying information about the SGs which might register with it. In the simplest case, SGs could be assigned passwords, and H.235.1, H.235.2, H.235.3, H.235.5 or challenge-response authentication procedures could be employed. The use of pre-shared secrets requires a secure out-of-band mechanism for their distribution, of course.
+
+An alternative mechanism might be based on public key certificates. Copies of the gatekeeper's certificate (or of the certificate belonging to the authority which signed the gatekeeper's certificate) could be installed to the SGs through some trusted process. The use of certificate methods remains for further study.
+
+# 9 Security considerations
+
+Protocols of this type, in which a message is permitted to be modified in transit, are subject to downgrade attacks. For example, if an endpoint offers both encrypted and unencrypted media transport capabilities, a malicious SG could remove the encryption offers and simply supply the unencrypted ones, thereby insuring that the media streams would be unencrypted. This type of attack must be countered by the endpoints (and the gatekeeper) by offering only those capabilities that are acceptable according to their own security policy. Ultimately, it is the responsibility of the endpoints and their users to insure that the appropriate security level is established and maintained. Similar considerations apply to the choice of security profiles during registration: if an endpoint requires strong authentication, it should specify so in its GRQ, and it should not accept a weaker offer from a gatekeeper.
+
+# 10 Applicability
+
+This scheme will be applicable to other H.235.1, H.235.2 and H.235.3 security profiles in addition to those described in ITU-T Rec. H.235.5. Any security profile which provides for the negotiation/derivation of suitable authentication keys may be supported. The SGs should examine elements of the GRQ/GCF (e.g., **authenticationCapability** and/or **authenticationMode**) to see if they can support the negotiated message authentication or security scheme.
+
+# 11 Object Identifier
+
+| OID   | Object identifier value                                     | Description                                            |
+|-------|-------------------------------------------------------------|--------------------------------------------------------|
+| "SG1" | { itu-t (0) recommendation (0) h (8) 235 version (0) 4 65 } | ClearToken carrying profile elements for SG discovery. |
+
+
+
+# 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.239-201410-I_PDF-E/2a23751710f7827065d2b99b6df588df_img.jpg b/marked/H/T-REC-H.239-201410-I_PDF-E/2a23751710f7827065d2b99b6df588df_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c8f5cc3e911099689a7a2865ed5ab8903ab99df9
--- /dev/null
+++ b/marked/H/T-REC-H.239-201410-I_PDF-E/2a23751710f7827065d2b99b6df588df_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4fcb0f6cd056d3e46dd5e78e3ae6511f5d998033d8d24e4bd3dae37566b6be99
+size 122976
diff --git a/marked/H/T-REC-H.239-201410-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.239-201410-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9e8c756205669eb173ca6812b96cc85ae0b38d7b
--- /dev/null
+++ b/marked/H/T-REC-H.239-201410-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c5c216bf4c9cbf2847d9375c712a074d19e06fdd8655cf36823232ef38473dc8
+size 7056
diff --git a/marked/H/T-REC-H.239-201410-I_PDF-E/raw.md b/marked/H/T-REC-H.239-201410-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..d1dd385d41bd804ee55108c32c024d6d77a8d584
--- /dev/null
+++ b/marked/H/T-REC-H.239-201410-I_PDF-E/raw.md
@@ -0,0 +1,1155 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.239**
+
+(10/2014)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS  
+Infrastructure of audiovisual services – Systems aspects
+
+---
+
+**Role management and additional media  
+channels for ITU-T H.300-series terminals**
+
+Recommendation ITU-T H.239
+
+ITU-T
+
+![ITU logo](84a1d09fb489061482111515543b60dc_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 on 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        |
+| <b>Systems aspects</b>                                                                 | <b>H.230–H.239</b> |
+| 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.239
+
+## Role management and additional media channels for ITU-T H.300-series terminals
+
+## Summary
+
+Recommendation ITU-T H.239 defines the procedures for use of more than one video channel in ITU-T H.320-based systems, and for labelling individual channels with a "role", which indicates requirements for processing the channel and the role of the channel content in the call. Role labels are applicable to both ITU-T H.320 and ITU-T H.245 signalling-based systems. The defined procedures include control, indication and capability exchange mechanisms
+
+This revised version introduces a number of typographical corrections and clarifications to the previous version, primarily the description of MCU procedures.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T H.239    | 2003-07-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/6455">11.1002/1000/6455</a>   |
+| 2.0     | ITU-T H.239    | 2005-09-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/8563">11.1002/1000/8563</a>   |
+| 3.0     | ITU-T H.239    | 2014-10-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12235">11.1002/1000/12235</a> |
+
+## Keywords
+
+AMC, capability exchange, commands, dual streams, ITU-T H.310, ITU-T H.320, ITU-T H.321, ITU-T H.322, ITU-T H.323, ITU-T H.324, multiple streams, roles, role labels, signalling, video channels, videoconferencing, videotelephony.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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    |
+| 4       | Abbreviations and acronyms .....                                                             | 3    |
+| 5       | Conventions .....                                                                            | 3    |
+| 5.1     | System terminology.....                                                                      | 3    |
+| 5.2     | Transport channel terminology.....                                                           | 3    |
+| 5.3     | Message names.....                                                                           | 4    |
+| 5.4     | Requirement terminology.....                                                                 | 4    |
+| 6       | Overview.....                                                                                | 4    |
+| 6.1     | Roles and role labels.....                                                                   | 5    |
+| 6.2     | Additional media channels .....                                                              | 5    |
+| 7       | ITU-T H.239 capabilities exchange.....                                                       | 5    |
+| 7.1     | ITU-T H.239 capabilities signals .....                                                       | 6    |
+| 8       | Control and indication (C&I) messages .....                                                  | 8    |
+| 8.1     | Signalling of messages in ITU-T H.239 .....                                                  | 8    |
+| 8.2     | ITU-T H.239 messages.....                                                                    | 9    |
+| 8.3     | GenericParameters used in ITU-T H.239 messages.....                                          | 9    |
+| 8.4     | Flow control release request and response messages .....                                     | 10   |
+| 8.5     | Presentation role token messages .....                                                       | 11   |
+| 9       | ITU-T H.245 OpenLogicalChannel procedure.....                                                | 12   |
+| 10      | Role policies and procedures .....                                                           | 12   |
+| 10.1    | "Live" role procedures.....                                                                  | 13   |
+| 10.2    | "Presentation" role procedures .....                                                         | 13   |
+| 10.3    | Multipoint considerations.....                                                               | 14   |
+| 11      | Token management.....                                                                        | 14   |
+| 11.1    | Procedure syntax .....                                                                       | 14   |
+| 11.2    | End-user system procedures.....                                                              | 14   |
+| 11.3    | Master MCU procedures .....                                                                  | 15   |
+| 11.4    | Slave MCU procedures.....                                                                    | 16   |
+| Annex A | – Procedures for translation of signalling between ITU-T H.320 and ITU-T H.245 systems ..... | 17   |
+| A.1     | Introduction .....                                                                           | 17   |
+| A.2     | Carriage of variable length integers in MBEs .....                                           | 17   |
+| A.3     | GenericParameter classes and associated translation procedures .....                         | 18   |
+| Annex B | – ITU-T H.320 additional media channel.....                                                  | 20   |
+| B.1     | ITU-T H.320 additional media channel.....                                                    | 20   |
+
+|                                                             | <b>Page</b> |
+|-------------------------------------------------------------|-------------|
+| B.2 AMC multiplex example 1 .....                           | 20          |
+| B.3 AMC multiplex example 2 .....                           | 21          |
+| B.4 AMC capabilities.....                                   | 22          |
+| B.5 AMC controls & indications .....                        | 23          |
+| B.6 Multipoint considerations.....                          | 24          |
+| Appendix I – ASN.1 OIDs defined in this Recommendation..... | 26          |
+
+# Recommendation ITU-T H.239
+
+## Role management and additional media channels for ITU-T H.300-series terminals
+
+# 1 Scope
+
+This Recommendation defines the procedures for use of more than one video channel in ITU-T H.320-based systems, and for labelling individual channels with a "role", which indicates requirements for processing the channel and the role of the channel content in the call. Role labels are applicable to both ITU-T H.320 and ITU-T H.245 signalling-based systems.
+
+The defined procedures include control, indication, and capability exchange 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.221] Recommendation ITU-T H.221 (2009), *Frame structure for a 64 to 1920 kbit/s channel in audiovisual teleservices.*
+- [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.*
+- [ITU-T H.230] Recommendation ITU-T H.230 (2009), *Frame-synchronous control and indication signals for audiovisual systems.*
+- [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 1920 kbit/s.*
+- [ITU-T H.245] Recommendation ITU-T H.245 (2009), *Control protocol for multimedia communication.*
+- [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.*
+- [ITU-T T.120] Recommendation ITU-T T.120 (2007), *Data protocols for multimedia conferencing.*
+
+# 3 Definitions
+
+This Recommendation defines the following terms:
+
+**3.1 bonding:** Term referring to [ISO/IEC 13871], which defines "Bandwidth ON Demand" (BOND) mechanisms.
+
+**3.2 cap:** Capability message.
+
+**3.3 channel:** A transport mechanism for a stream of data, such as a video stream. Examples include an ITU-T H.245 Logical Channel, or the ITU-T H.320 BAS and HSD channels.
+
+**3.4 control & indication:** Messages, including requests, responses, commands, and indication messages, but not including capability messages.
+
+**3.5 device:** An end-user system, gateway, or Multipoint Control Unit (MCU).
+
+**3.6 end-user system:** A terminal which is an ultimate source or sink of multimedia streams, such as a device which is meant for use by a human end user. Intermediary devices such as MCUs or gateways are not end-user systems.
+
+**3.7 intermediary device:** A multipoint control unit (MCU) or gateway.
+
+**3.8 kbits:** Units of 1000 bits.
+
+**3.9 main video channel:** For ITU-T H.320, the remainder of the traditional video channel, after subtracting the additional media channel (AMC) channel. When no AMC channel exists, this is the same as the traditional video channel. For ITU-T H.245-based systems, this is any logical channel which does not have a role label.
+
+**3.10 role:** A label which may be applied to a channel, identifying the nature of the content of the data carried in the channel. The phrase "the <role label> channel" should be read as meaning "the channel for which <role label> has been indicated".
+
+**3.11 second video channel:** For ITU-T H.320, the proposed new additional media channel (AMC). For ITU-T H.245-based systems this channel is any logical channel with an explicit role label.
+
+**3.12 stream:** The data content carried in a channel.
+
+**3.13 sub-timeslot:** An ITU-T H.221 sub-channel of 8 kbit/s. It consists of a single bit position of a timeslot, with the timeslot considered as octets (or in the case of restricted calls, septets) transmitted at 8 kHz. Sub-timeslots are numbered from 1 to 8 within each timeslot, corresponding to the bit-numbers shown in [ITU-T H.221]. For restricted calls, sub-timeslot 8 is considered to exist, but to be unavailable for use. This term is used in this Recommendation instead of "sub-channel" to avoid confusion with ITU-T H.245 Logical Channels or the ITU-T H.320 bit-rate allocation signal (BAS), frame alignment signal (FAS), low-speed data (LSD), high-speed data (HSD), multi-layer protocol (MLP), encryption control signal (ECS) or additional media channel (AMC) channels.
+
+**3.14 timeslot:** A single 64 kbit/s (or in the case of restricted calls, 56 kbit/s) ISDN B-channel, or in the case of an H<sub>0</sub>, H<sub>11</sub> or H<sub>12</sub> channel, a single 64 kbit/s (or in the case of restricted calls, 56 kbit/s) Time-Slot, as described in clause 1 of [ITU-T H.221] and Figure 2 of [ITU-T H.221]. Timeslots are numbered from 1 to N (where N is the total number of timeslots) as shown in [ITU-T H.221]. This term is used in this Recommendation instead of "channel" to avoid confusion with ITU-T H.245 Logical Channels or the ITU-T H.320 bit-rate allocation signal (BAS), frame alignment signal (FAS),
+
+low-speed data (LSD), high-speed data (HSD), multi-layer protocol (MLP), encryption control signal (ECS) or additional media channel (AMC) channels.
+
+**3.15 traditional video channel:** For [ITU-T H.320], the video channel as defined by [ITU-T H.320] when no additional media channel (AMC) is in use. For ITU-T H.245-based systems, this is the same as the main video channel.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|       |                                  |
+|-------|----------------------------------|
+| ASN.1 | Abstract Syntax Notation One     |
+| AMC   | Additional Media Channel         |
+| BAS   | Bit-rate Allocation Signal       |
+| BOND  | Bandwidth On Demand              |
+| C&I   | Control & Indication             |
+| ECS   | Encryption Control Signal        |
+| FAS   | Frame Alignment Signal           |
+| HSD   | High Speed Data                  |
+| LSD   | Low Speed Data                   |
+| MBE   | Multiple Byte Extension          |
+| MCU   | Multipoint Control Unit          |
+| MLP   | Multi-Layer Protocol             |
+| OID   | Object Identifier                |
+| PID   | Parameter Identifier             |
+| SBE   | Single Byte Extension            |
+| VIR   | Video Indicate Ready to activate |
+
+# 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 devices.
+
+"ITU-T H.320" refers to ITU-T H.320 systems.
+
+"ITU-T H.245" 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 Transport channel terminology
+
+In this Recommendation, the traditional ITU-T H.320 video channel, and in the case of ITU-T H.245-based systems, the **sessionID 2** video channel, is referred to as the "main" video channel. The terminology used to describe these is given in Table 1.
+
+**Table 1 – Transport channel terminology**
+
+| ITU-T H.239 term       | ITU-T H.320 channels                  | ITU-T H.245 based channels |
+|------------------------|---------------------------------------|----------------------------|
+| "control channel"      | BAS                                   | LC 0                       |
+| "main video channel"   | Traditional ITU-T H.320 video channel | LC with no role label      |
+| "second video channel" | AMC                                   | LC with an explicit role   |
+| "3rd video channel"    | AMC2 (for future study)               | LC nn                      |
+| etc.                   | AMC3, etc. (for future study)         | LC nn                      |
+
+## 5.3 Message names
+
+In this Recommendation signalling messages which are common to both ITU-T H.245 and ITU-T H.320 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 H.320 signalling environment is described. Message names are presented in **bold font** to distinguish them from the other text of this Recommendation.
+
+Table 2 provides a reference for corresponding ITU-T H.245 and ITU-T H.242/H.230 messages mentioned in this Recommendation.
+
+**Table 2 – Corresponding ITU-T H.245 and ITU-T H.320 video signals**
+
+| ITU-T H.245 name                   | ITU-T H.320/H.230 mnemonic |
+|------------------------------------|----------------------------|
+| <b>cancelMultipointConference</b>  | cancel-MCC                 |
+| <b>cancelMultipointModeCommand</b> | cancel-MMS                 |
+| <b>logicalChannelActive</b>        | VIA, VIA2, VIA3            |
+| <b>logicalChannelInactive</b>      | VIS                        |
+| <b>multipointConference</b>        | MCC                        |
+| <b>multipointModeCommand</b>       | MMS                        |
+| <b>terminalYouAreSeeing</b>        | VIN                        |
+| <b>videoFastUpdatePicture</b>      | VCU                        |
+| <b>videoFreezePicture</b>          | VCF                        |
+
+NOTE – ITU-T H.320 symbols VIA2 and VIA3 signal activity of alternate video sources (for example a document camera, VCR, or DVD player) on a single video channel, as described in clause 4.4 of [ITU-T H.320]. They do not indicate activity on alternate video channels. Activity of the primary video source on any video channel should be signalled with VIA.
+
+## 5.4 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 Overview
+
+ITU-T H.245-based systems provide for multiple channels of video, while ITU-T H.320 systems provide for only a single video channel. However, neither of these define a one-way transmission method, methods to label a video channel's content as a presentation video stream, or methods to
+
+control presentation video in a multipoint conference. This Recommendation provides these extensions, as well as a means to add an additional video channel to ITU-T H.320.
+
+The mechanisms are designed for both one-way and two-way video transmission. One-way transmission is particularly advantageous for presentation video; it reduces computational complexity in the devices, and it simplifies the distribution of the presentation stream in MCUs.
+
+## 6.1 Roles and role labels
+
+The architecture of this Recommendation separates the idea of transport channels (logical channels in ITU-T H.245, BAS, main video, main audio, LSD, HSD, MLP, etc. in ITU-T H.320) from "roles".
+
+Roles, which are indicated by "role labels" on a channel, indicate both the purpose of the stream carried on a channel, and indicate how the stream should be presented at the end-user system and processed by an MCU.
+
+The general architecture is that a role label may be assigned to any channel (audio, video, or data) where it is useful to establish policies for presentation, management, or distribution of the information on that channel.
+
+## 6.2 Additional media channels
+
+While [ITU-T H.320] has no provision for multiple video channels, it does provide a variety of data channels (LSD, HSD, MLP, H-MLP), which could be used to transport a second video stream. However, these channels are commonly used for both ITU-T H.224 and ITU-T T.120 services. Permitting a second video stream to run over these channels would interfere with these services, and complicates the allocation of these channels in a multipoint conference. In addition, use of the existing data channels is not extensible.
+
+Therefore, for ITU-T H.320, a second video channel called the Additional Media Channel (AMC) is described. In principle, this framework could be extended to include more than one AMC channel (e.g. AMC2, AMC3, etc.) but as applications for more than one AMC are not well defined, this functionality is for further study.
+
+The ITU-T H.320 AMC is described in Annex B.
+
+# 7 ITU-T H.239 capabilities exchange
+
+The capabilities given in this clause are distinct from those given in Annex B for the AMC.
+
+ITU-T H.239 capabilities use very similar structures for both ITU-T H.320 and ITU-T H.245-based signalling systems, to ease the implementation of gateways and MCUs.
+
+The **h239ControlCapability** indicates that the device supports ITU-T H.239 and the **flowControlReleaseRequest** and **flowControlReleaseResponse** messages defined in Table 7.
+
+A separate **h239ExtendedVideoCapability** message expresses video capabilities used with roles.
+
+The ITU-T H.239 capability signals permit a device to send capabilities that correspond to the following ITU-T H.245 capability structure:
+
+```
+{1 or more capabilities for traditional video channel},  
+{ {1 or more capabilities for second video channel}, {1 or more capabilities for main video  
+channel while second video channel is open} }
+```
+
+The {1 or more capabilities for traditional video channel} shall be sent via the normal capability exchange mechanism.
+
+The {1 or more capabilities for second video channel} shall be sent via the **h239ExtendedVideoCapability** message as described below.
+
+The {1 or more capabilities for main video channel while second video channel is open} may be sent via the **h239ExtendedVideoCapability** message as described below, if this capability differs from the capability for the traditional video channel.
+
+NOTE – For example, the capability for the main video channel, while the second video channel is open, may be less capable than the traditional video channel due to the computational requirements of operating two video streams simultaneously.
+
+The **h239ExtendedVideoCapability** message binds together a set of alternative video channel capabilities for a single channel with the channel's capability to operate in one or more roles.
+
+## 7.1 ITU-T H.239 capabilities signals
+
+ITU-T H.239 capabilities shall be carried by two separate signals, as shown in Table 3.
+
+**Table 3 – ITU-T H.239 capabilities signals**
+
+| ITU-T H.245-signalling based systems                                                                 |                                                                          | ITU-T H.320 systems                                                                                |                 |
+|------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------|
+| GenericCapability OID                                                                                | Appears in H.245 structure                                               | BAS name                                                                                           | BAS signal type |
+| {itu-t(0) recommendation(0) h(8) 239 generic-capabilities(1) h239ControlCapability(1) }              | Capability.genericControl Capability                                     | h239ControlCapability                                                                              | SBE             |
+| {itu-t(0) recommendation(0) h(8) 239 generic-capabilities(1) <b>h239ExtendedVideoCapability(2)</b> } | VideoCapability.<br>extendedVideoCapability.<br>videoCapabilityExtension | <b>h239ExtendedVideoCapability</b><br>(NOTE – This is an MBE <i>indication</i> , despite its name) | MBE indication  |
+
+The traditional and main video channels shall not signal a role capability.
+
+The second video channel shall signal a role capability.
+
+Systems which support ITU-T H.239 shall signal the following capabilities as listed below:
+
+- The traditional video channel, signalled normally as required by the system specification.
+- A second video channel – In ITU-T H.245 signalling-based systems, this shall be signalled in an **ExtendedVideoCapability** containing a **videoCapability** and a **videoCapabilityExtension** containing the **h239ExtendedVideoCapability** as in Table 5 and the roleLabel parameter as in Table 6. In ITU-T H.320 systems, this shall be signalled in an **h239ExtendedVideoCapability** MBE indication. These signals mean that the device supports any of the roles indicated in the roleLabel parameter, on a video channel conforming to any of the indicated video capabilities.
+- For ITU-T H.245 signalling-based systems, the main video channel shall be included in a set of **simultaneousCapabilities** together with the **ExtendedVideoCapability** for the second video channel. This indicates that the main video channel may be used simultaneously with the second video channel. In ITU-T H.320 systems, capabilities applicable to the main video channel while operating simultaneously with the second video channel may optionally be signalled using **h239ExtendedVideoCapability**.
+- The **h239ControlCapability** as in Table 4. This indicates that the device supports ITU-T H.239 and the **flowControlReleaseRequest** and **flowControlReleaseResponse** messages defined in Table 7.
+
+Except for ITU-T H.320-H.245 gateways, unrecognized **GenericParameter** structures shall be ignored by receivers.
+
+### 7.1.1 Capabilities for ITU-T H.245
+
+**Table 4 – h239ControlCapability capability identifier**
+
+| Capability name             | h239ControlCapability                                                                    |
+|-----------------------------|------------------------------------------------------------------------------------------|
+| Capability identifier type  | Standard                                                                                 |
+| Capability identifier value | { itu-t(0) recommendation(0) h(8) 239 generic-capabilities(1) h239ControlCapability(1) } |
+| maxBitRate                  | This parameter is not used.                                                              |
+| Collapsing                  | This field shall not be used and shall be ignored by receivers.                          |
+| nonCollapsing               | This field shall not be used and shall be ignored by receivers.                          |
+| nonCollapsingRaw            | This field shall not be used and shall be ignored by receivers.                          |
+| Transport                   | This field shall not be used and shall be ignored by receivers.                          |
+
+**Table 5 – h239ExtendedVideoCapability capability identifier**
+
+| Capability name             | h239ExtendedVideoCapability                                                                    |
+|-----------------------------|------------------------------------------------------------------------------------------------|
+| Capability identifier type  | Standard                                                                                       |
+| Capability identifier value | { itu-t(0) recommendation(0) h(8) 239 generic-capabilities(1) h239ExtendedVideoCapability(2) } |
+| maxBitRate                  | This parameter is not used.                                                                    |
+| Collapsing                  | This field contains the roleLabel parameter.                                                   |
+| nonCollapsing               | This field shall not be used and shall be ignored by receivers.                                |
+| nonCollapsingRaw            | This field shall not be used and shall be ignored by receivers.                                |
+| Transport                   | This field shall not be used and shall be ignored by receivers.                                |
+
+**Table 6 – roleLabel Boolean parameter**
+
+| Parameter name                  | roleLabel                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Parameter description           | This parameter is a Boolean array.<br>If bit 7 (value 2) is 1, this indicates support of the "Live" role.<br>If bit 8 (value 1) is 1, this indicates support of the "Presentation" role.<br>All other bits are reserved and shall be set to 0.<br>In a decoder capability, for each bit set to 1, this means that the device supports the indicated Role(s).<br>In an OpenLogicalChannel message, only 1 bit shall be set, corresponding to the channel Role. |
+| Parameter identifier (PID) type | Standard                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| PID value                       | 1                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| Parameter status                | Mandatory                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| Parameter type                  | booleanArray                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| Supersedes                      | This field is not used.                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+NOTE – If, in the future, more Roles are defined than the number of reserved bits can accommodate, additional Roles could be signalled by allocating another parameter for additional Roles. If this is done, in order for ITU-T H.320 receivers using ITU-T H.239 to avoid incorrectly interpreting the roleLabel parameter as indicating the main video channel, at least one bit in the roleLabel booleanArray should be set even if some
+
+other parameter is used to indicate the Role. One way to accomplish this would be to allocate one reserved bit in roleLabel to be set to 1 when another parameter indicates the Role.
+
+### 7.1.2 Capabilities for ITU-T H.320
+
+In ITU-T H.320 systems, the ITU-T H.239 capabilities shall be signalled in two different BAS messages, <h239ControlCapability> (see clause 3.10 of [ITU-T H.230]) and <h239ExtendedVideoCapability> (see Table 2 of [ITU-T H.230]).
+
+<h239ExtendedVideoCapability> is an H.320 MBE indication (see clause 2.2.3 of [ITU-T H.230]). Despite its name, it is not a formal H.320 capability, and it shall not be included in the formal ITU-T H.320 capability set.
+
+NOTE 1 – This separation of the <h239ControlCapability> BAS capability from the longer <h239ExtendedVideoCapability> MBE indication serves to reduce the length of the ITU-T H.320 system's capability set, which is already too long.
+
+This MBE has the format:
+
+$$\{ \text{Start-MBE} / N / \langle \text{h239ExtendedVideoCapability} \rangle / B_1 / \dots / B_{N-1} \}$$
+
+Bytes  $B_1$  through  $B_{N-1}$  within the MBE shall begin with the roleLabel parameter, as defined in Table 6 and coded as a **GenericParameter** as described in Annex A, followed by a single byte of 0, which marks the end of the sequence of one or more **GenericParameters**. (The use of more than one **GenericParameter** in this structure is for further study.)
+
+If all bits in the roleLabel parameter are set to 0, this indicates that the capability applies to the main video channel.
+
+Receivers shall parse the MBE as a sequence of one or more **GenericParameters** according to Annex A, followed by a single byte of 0 marking the end of the **GenericParameter** sequence.
+
+Immediately following the 0 byte marking the end of the **GenericParameter** sequence, the remaining bytes of the MBE shall contain a concatenated list of 1 or more video capabilities in the syntax given in Table A.1 of [ITU-T H.221], as specified with all escape codes, extensions, or MBE sequences. The list of capabilities shall not include H.221 Cap-mark.
+
+NOTE 2 – This <h239ExtendedVideoCapability> MBE indication may contain nested MBE messages.
+
+ITU-T H.320 devices shall not transmit video on a second video channel unless the far-end device has indicated support for at least one role and an associated video channel.
+
+# 8 Control and indication (C&I) messages
+
+C&I messages are used in this Recommendation to manage tokens for the "Presentation" role, and to permit devices to request release of video flow control to enable the operation of additional media channels.
+
+All C&I messages defined in this clause shall be carried as follows.
+
+## 8.1 Signalling of messages in ITU-T H.239
+
+For ITU-T H.245, each ITU-T H.239 message shall consist of a **GenericRequest**, **GenericResponse**, **GenericCommand** or **GenericIndication** according to Table 7 containing a **GenericMessage.messageIdentifier** with the OID { itu-t(0) recommendation(0) h(8) 239 generic-message(2) }, and a **subMessageIdentifier**. Each particular **subMessageIdentifier** listed in Table 7 has an associated **messageContent** syntax given in the following clauses.
+
+For ITU-T H.320, each ITU-T H.239 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.
+
+This MBE message uses the BAS code <H.239-message> (see Table 2 of [ITU-T H.230]). The MBE contents are in the format:
+
+{ Start-MBE / N / <H.239-message> / **subMessageIdentifier** / zero or more message content bytes }
+
+ITU-T H.320-H.245 gateways shall translate these ITU-T H.239 messages between the ITU-T H.320 and ITU-T H.245 signalling systems as specified in Annex A.
+
+Except for ITU-T H.320-H.245 gateways, devices that receive **messageContent** containing an unrecognized **parameterIdentifier** shall ignore such **parameterIdentifiers** and any associated **parameterValues**.
+
+C&I messages for the AMC are treated differently, and are described separately in Annex B.
+
+## 8.2 ITU-T H.239 messages
+
+Table 7 lists the messages defined in this Recommendation, except for those in Annex B.
+
+**Table 7 – subMessageIdentifier values**
+
+| <b>subMessageIdentifier</b> | <b>Message name</b>                   | <b>Message type<br/>(for ITU-T H.245)</b> |
+|-----------------------------|---------------------------------------|-------------------------------------------|
+| 1                           | <b>flowControlReleaseRequest</b>      | GenericRequest                            |
+| 2                           | <b>flowControlReleaseResponse</b>     | GenericResponse                           |
+| 3                           | <b>presentationTokenRequest</b>       | GenericRequest                            |
+| 4                           | <b>presentationTokenResponse</b>      | GenericResponse                           |
+| 5                           | <b>presentationTokenRelease</b>       | GenericCommand                            |
+| 6                           | <b>presentationTokenIndicateOwner</b> | 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 7 above. Parameters shall be sent as indicated in the "Required Presence" column of each table.
+
+## 8.3 GenericParameters used in ITU-T H.239 messages
+
+Table 8 lists the **GenericParameters** used in all **messageContent** sequences in this Recommendation.
+
+**Table 8 – GenericParameters used in ITU-T H.239 messageContent sequences**
+
+| <b>PID</b> | <b>Parameter name</b> | <b>Parameter value</b> | <b>Parameter value type</b> |
+|------------|-----------------------|------------------------|-----------------------------|
+| 0          | reserved              | 0                      | unsignedMin                 |
+| 41         | bitRate               | Integer (1..19200)     | unsignedMin                 |
+| 42         | channelId             | Integer (0..65535)     | unsignedMin                 |
+| 43         | symmetryBreaking      | Integer (0..127)       | unsignedMin                 |
+| 44         | terminalLabel         | Integer (0..65535)     | unsignedMin                 |
+| 126        | acknowledge           | None                   | logical                     |
+| 127        | reject                | None                   | logical                     |
+
+NOTE – PID 0 is reserved, and should not be defined in the future, as the value 0 is used to demarcate the end of the GenericParameter sequence in the <h239ExtendedVideoCapability> MBE indication.
+
+### 8.3.1 bitRate
+
+The bitRate parameter shall be a channel bit rate in units of 100 bit/s.
+
+### 8.3.2 channelID
+
+The channelID parameter shall be an AMC channel ID on ITU-T H.320 systems. On ITU-T H.245 systems, it shall be a **logicalChannelNumber**. Intermediary devices such as gateways and MCUs that forward this parameter shall convert the parameter value to the appropriate AMC channel ID or **logicalChannelNumber** for the device to which the message is forwarded.
+
+The AMC channel ID values for [ITU-T H.320] are shown in Table 9.
+
+**Table 9 – AMC channelID values**
+
+| ChannelID        | Description                |
+|------------------|----------------------------|
+| 1                | Main video channel         |
+| 2                | Second video channel (AMC) |
+| All other values | Reserved                   |
+
+### 8.3.3 symmetryBreaking
+
+The symmetryBreaking parameter shall be a random number with a uniformly distributed probability of having a value between 1 and 127 inclusive. In circumstances defined below, the MCU shall send a 0 value.
+
+### 8.3.4 terminalLabel
+
+The terminalLabel parameter value shall contain both the terminal number and MCU number as defined in clause 7 of [ITU-T H.243]. The MCU number M and the terminal number T shall be combined into a single integer as follows:  $\text{terminalLabel} = (M * 256) + T$ .
+
+NOTE – When in a point-to-point call (without an MCU), terminalLabel shall be set to 0.
+
+### 8.3.5 acknowledge and reject
+
+The acknowledge and reject parameters are used in response messages.
+
+## 8.4 Flow control release request and response messages
+
+The **flowControlReleaseRequest** and **flowControlReleaseResponse** messages may be used to request the far end to release flow control or **multipointConference** restrictions to permit a device to send the indicated channel at the indicated bit rate.
+
+Devices shall not send these messages unless the far end has expressed the ITU-T H.239 capability in its capability set.
+
+### 8.4.1 flowControlReleaseRequest
+
+This message may be used when a device wants to add a channel toward an MCU that has sent **multipointConference**, or if the device wants to increase a channel bit rate when the channel is flow-controlled.
+
+**Table 10 – flowControlReleaseRequest syntax**
+
+| GenericParameter order | Parameter name | Required presence |
+|------------------------|----------------|-------------------|
+| 1                      | channelID      | Mandatory         |
+| 2                      | bitRate        | Mandatory         |
+
+The originating channelID value shall be that of the device making the request.
+
+### 8.4.2 flowControlReleaseResponse
+
+Devices shall send this message in response to the **flowControlReleaseRequest** message.
+
+**Table 11 – flowControlReleaseResponse syntax**
+
+| GenericParameter order | Parameter name | Required presence                                 |
+|------------------------|----------------|---------------------------------------------------|
+| 1                      | acknowledge    | Exactly 1 of these 2 parameters shall be present. |
+|                        | reject         |                                                   |
+| 2                      | channelID      | Mandatory                                         |
+
+The "acknowledge" response indicates that the far-end device intends to make a best-effort attempt to comply with the request. The exact bit rate requested may not be allocated. Devices receiving the "acknowledge" response shall continue to comply with the signalled flow control or other restrictions until the far end modifies these restrictions in separate signals.
+
+The "reject" response indicates that the far-end device does not intend to comply with the request.
+
+The originating channelID value shall be that of the device making the request.
+
+## 8.5 Presentation role token messages
+
+The **presentationTokenRequest**, **presentationTokenResponse**, **presentationTokenRelease**, and **presentationTokenIndicateOwner** messages shall be used to manage the token associated with the "Presentation" role, according to the token management procedures given in clause 11.
+
+Devices shall not send these messages unless the far end has expressed the ITU-T H.239 capability in its capability set.
+
+### 8.5.1 presentationTokenRequest
+
+This message is a request by the sender to acquire the indicated token. The receiver shall respond with **presentationTokenResponse**.
+
+**Table 12 – presentationTokenRequest syntax**
+
+| GenericParameter order | Parameter name   | Required presence |
+|------------------------|------------------|-------------------|
+| 1                      | terminalLabel    | Mandatory         |
+| 2                      | channelID        | Mandatory         |
+| 3                      | symmetryBreaking | Mandatory         |
+
+The originating channelID and terminalLabel values shall be those of the device making the request.
+
+### 8.5.2 presentationTokenResponse
+
+Devices shall send this message in response to the **presentationTokenRequest** message.
+
+This response shall confirm or reject assignment of the indicated token to the sender of **presentationTokenRequest**. It shall include the parameter values from the original request.
+
+**Table 13 – presentationTokenResponse syntax**
+
+| GenericParameter order | Parameter name | Required presence                                 |
+|------------------------|----------------|---------------------------------------------------|
+| 1                      | acknowledge    | Exactly 1 of these 2 parameters shall be present. |
+|                        | reject         |                                                   |
+| 2                      | terminalLabel  | Mandatory                                         |
+| 3                      | channelID      | Mandatory                                         |
+
+The originating channelID and terminalLabel values shall be those of the device making the request.
+
+### 8.5.3 presentationTokenRelease
+
+The **presentationTokenRelease** message shall be sent by a device holding the token in order to relinquish the token.
+
+**Table 14 – presentationTokenRelease syntax**
+
+| GenericParameter order | Parameter name | Required presence |
+|------------------------|----------------|-------------------|
+| 1                      | terminalLabel  | Mandatory         |
+| 2                      | channelID      | Mandatory         |
+
+The originating channelID and terminalLabel values shall be those of the device releasing the token.
+
+#### 8.5.4 presentationTokenIndicateOwner
+
+This message indicates which device owns the token. This message should be sent periodically by the device holding the token, and forwarded by MCUs and gateways.
+
+NOTE – This message permits resynchronization in case of transmission errors.
+
+**Table 15 – presentationTokenIndicateOwner syntax**
+
+| GenericParameter order | Parameter name | Required presence |
+|------------------------|----------------|-------------------|
+| 1                      | terminalLabel  | Mandatory         |
+| 2                      | channelID      | Mandatory         |
+
+The originating channelID and terminalLabel values shall be those of the device indicating ownership.
+
+# 9 ITU-T H.245 OpenLogicalChannel procedure
+
+When a second video channel is opened in [ITU-T H.245], the **OpenLogicalChannel** message shall include an **extendedVideoCapability** with the **videoCapabilityExtension** including the **h239ExtendedVideoCapability** and roleLabel parameter. Changing the role may be accomplished by reopening the logical channel.
+
+ITU-T H.245 devices should not use the existing 3 primary sessionIDs for the second video channel.
+
+# 10 Role policies and procedures
+
+Role labels shall be assigned by the end-user system which sources the channel. Support for receiving role labels shall be signalled by devices in their capability set.
+
+The defined role labels are:
+
+- Live – video is processed normally; suitable for live video of people.
+- Presentation – a token-managed presentation to be distributed to all devices.
+
+For simplicity, role labels shall only be applied to the second video channel for ITU-T H.320.
+
+NOTE 1 – Application of role labels to other channels is for future study.
+
+No explicit role label shall be used on a channel unless support for that role is explicitly signalled by the receiving device.
+
+Regardless of roles, all C&I shall be used as specified elsewhere, except where this Recommendation makes specific mention otherwise.
+
+NOTE 2 – For example, the use of **videoIndicateReadyToActivate** and corresponding BAS signal **VIR** is not affected by this Recommendation.
+
+For any role, if a device is unable to open a channel due to flow control or **multipointConference** restrictions, the device may use the **flowControlReleaseRequest** message to request the far end to change its restrictions.
+
+## 10.1 "Live" role procedures
+
+The "Live" role indicates that the video channel shall be distributed, managed, and presented using the traditional means. The "Live" role is appropriate for live video of meeting participants. The "Live" video channel supplements the other video channel: it should carry a stream which is less important to display at end-user systems than the Presentation channel or channels without role labels.
+
+"Live" video is two-way transmission; multiple devices may transmit "Live" video simultaneously.
+
+### 10.1.1 MCU procedures
+
+MCUs that support roles and process "Live" video streams distribute all live video in accordance with manufacturer-defined conference policies and shall identify the source of the video channel(s) in use by sending **terminalYouAreSeeing** for the channel.
+
+MCUs should distribute a device's "Live" video stream to all participants who are also receiving the other video stream from the device.
+
+### 10.1.2 End-user system procedures
+
+To send a "Live" video stream, end-user systems that support roles shall open the channel (if closed), indicate **logicalChannelActive**, and start sending the stream.
+
+To stop sending a "Live" video stream, end-user systems that support roles shall indicate **logicalChannelInactive**, stop sending the stream, and optionally close the channel.
+
+## 10.2 "Presentation" role procedures
+
+The "Presentation" role is used to indicate that the video channel contains a presentation which is intended to be seen by all conference participants. Transmission on the Presentation channel shall be managed by the token mechanism in clause 11 in order to provide the one-way transmission described above. Generally, the Presentation channel, when it is in use, should carry the stream which is most important to display at end-user systems.
+
+Presentation token management procedures are described in clause 11.
+
+### 10.2.1 MCU procedures
+
+For the "Presentation" role, MCUs shall distribute the presentation video to all devices in the conference which support the "Presentation" role and its associated video mode, except when it is optional to send the presentation video to the sender.
+
+The MCU shall also manage the presentation token in a multipoint call (grants the token, and may also withdraw the token), and shall identify the presenter by sending **terminalYouAreSeeing** for the channel in use.
+
+### 10.2.2 End-user system procedures
+
+To send a presentation video stream, devices that support roles shall request the token. When the device obtains the token, it shall open the channel (if closed); indicate video active, and start sending the stream.
+
+To stop the presentation video stream, devices shall indicate **logicalChannelInactive**, stop sending the stream, and optionally close the channel. Then the end-user device shall release the token.
+
+## 10.3 Multipoint considerations
+
+The **multipointModeCommand** signal requires algorithm and image format symmetry for the Live role. However, since the "Presentation" role is one-way, devices shall ignore **multipointModeCommand** with respect to the Presentation channel.
+
+# 11 Token management
+
+The "Presentation" role is token-controlled. The token management procedure is described in this clause. There is one token in a conference.
+
+NOTE – A larger number of Presentation tokens in a conference might, in the future, be indicated by a signal; this is for further study.
+
+Token transfers should not drive video display rendering; instead existing explicit C&I messages should be used for this purpose.
+
+The token messages are defined in clause 8.5.
+
+The requirements in this clause apply to end-user systems only. MCU procedures for token management may follow specific manufacturer-defined conference policies. Such conference policies shall take into account the behaviour of devices according to this clause.
+
+## 11.1 Procedure syntax
+
+In this Recommendation, role token procedures are described using the following syntax:
+
+**subMessageIdentifier name (GenericParameter name)**
+
+For example, to indicate transmission of the ITU-T H.239 **presentationTokenResponse subMessageIdentifier** with the **messageContent** field containing the acknowledge **GenericParameter**, the following syntax is used:
+
+**presentationTokenResponse(acknowledge)**
+
+Unless otherwise mentioned in the following clauses, token messages not described in each case should be ignored.
+
+## 11.2 End-user system procedures
+
+### 11.2.1 End-user system does not own and does not want the token
+
+The end-user system shall respond to **presentationTokenRequest** by sending **presentationTokenResponse(acknowledge)**.
+
+The end-user system shall respond to **presentationTokenResponse(acknowledge)** by sending **presentationTokenRelease**.
+
+### 11.2.2 End-user system owns the token and wants to retain the token
+
+The end-user system shall respond to **presentationTokenRequest** by sending **presentationTokenResponse(acknowledge)**, giving up the token.
+
+While the token is held, the end-user system should send **presentationTokenIndicateOwner** periodically.
+
+### 11.2.3 End-user system owns the token and wants to release the token
+
+The end-user system shall send **presentationTokenRelease**.
+
+### 11.2.4 End-user system does not own but wants the token
+
+The end-user system shall send **presentationTokenRequest**.
+
+If, prior to receiving a response, **presentationTokenRequest** is received from another device, then the end-user system shall:
+
+- If (transmitted symmetryBreaking < received symmetryBreaking),  
+send **presentationTokenResponse(acknowledge)** – abandoning the request.
+- If (transmitted symmetryBreaking = received symmetryBreaking)  
+send new **presentationTokenRequest** with a new symmetryBreaking parameter.
+- If (transmitted symmetryBreaking > received symmetryBreaking)  
+send **presentationTokenResponse(reject)** – rejecting the far-end request.
+
+In all cases, the end-user system owns the token on receipt of **presentationTokenResponse(acknowledge)**.
+
+## 11.3 Master MCU procedures
+
+The designation of a master MCU in a cascaded MCU case is defined in clause 5.7 of [ITU-T H.243]. In a non-cascaded MCU case, the Master MCU procedures defined in this Recommendation should be used.
+
+At the start of a conference, the MCU should consider the token to be unowned.
+
+When the MCU receives **presentationTokenIndicateOwner** from a device that is not the token owner, it should send **presentationTokenRequest** with a 0 symmetryBreaking value to it, and should then consider the token to be unowned.
+
+### 11.3.1 Token unowned
+
+When the MCU receives **presentationTokenRequest**, it should assign the token to the sender and send **presentationTokenResponse(acknowledge)** to it.
+
+### 11.3.2 Token owned
+
+When the MCU receives **presentationTokenRequest** from a device that does not own the token, it should forward the **presentationTokenRequest** to the current token owner with a 0 symmetryBreaking parameter value.
+
+When the MCU receives **presentationTokenResponse(acknowledge)**, it should assign the token by forwarding the **presentationTokenResponse(acknowledge)** to the new owner. The MCU should then send a **presentationTokenIndicateOwner** indication to all connected devices, indicating the owner.
+
+When the MCU receives **presentationTokenRelease** from the token owner, it should consider the token to be unowned.
+
+The MCU should forward **presentationTokenIndicateOwner** messages from the token owner to all connected devices in the conference.
+
+When the end user system owning the token or slave MCU whose device owns the token disconnects, the MCU should consider the token to be unowned.
+
+## **11.4 Slave MCU procedures**
+
+The designation of a slave MCU in a cascaded MCU case is defined in clause 5.7 of [ITU-T H.243].
+
+Slave MCUs shall forward all token messages received from its end-user systems or slave MCUs to the master MCU.
+
+**presentationTokenRequest**, **presentationTokenResponse**, and **presentationTokenRelease** messages received from the master MCU shall be routed to the end-user system based on the **terminalLabel** parameter value.
+
+**presentationTokenIndicateOwner** messages from the Master MCU shall be forwarded to all other connected devices.
+
+# Annex A
+
+## Procedures for translation of signalling between ITU-T H.320 and ITU-T H.245 systems
+
+(This annex forms an integral part of this Recommendation.)
+
+### A.1 Introduction
+
+This annex defines a procedure to transport ITU-T H.245 generic messages in ITU-T H.320 MBEs which enables ITU-T H.320-H.245 gateways to automatically translate the signalling between the two systems. This method also ensures that the parameter syntax and semantics are the same between ITU-T H.320 and ITU-T H.245-based systems.
+
+### A.2 Carriage of variable length integers in MBEs
+
+This clause specifies a procedure for the carriage of integers of any length in MBEs.
+
+This procedure avoids emulation of the MBE BAS code.
+
+#### A.2.1 Non-negative integers
+
+Non-negative integers shall be carried in MBEs by the following method:
+
+- 1) If the integer is  $\leq 127$ , construct an MBE byte with a value equal to the integer. The procedure is complete. Otherwise, continue.
+- 2) Construct an MBE byte with the two high order bits (bits 1 and 2) equal to binary '10', and place the least significant 6 bits of the integer in the least significant 6 bits of the MBE byte.
+- 3) Discard the least significant 6 bits of the integer (shift the integer 6 bits to the right). Continue from step 1.
+
+The result of this procedure is that each MBE byte with a high order bit set to 1 contains 6 bits of the integer, starting with the least significant 6 bits and proceeding with each MBE to more significant bits. The final MBE byte has the high order bit set to 0, and contains the 7 most significant bits of the integer.
+
+Another result is that if the integer value is  $\leq 127$ , it is represented by a single MBE byte.
+
+#### A.2.2 Negative integers
+
+Negative integers shall be carried in MBEs by the following method:
+
+- 1) Set a non-negative integer I to have the absolute value of the negative integer.
+- 2) Construct an MBE byte with the three high order bits (bits 1, 2 and 3) equal to binary '110', and place the least significant 5 bits of I in the least significant 5 bits of the MBE byte.
+- 3) Discard the least significant 5 bits of I (shift I 5 bits to the right).
+- 4) If I is  $\leq 127$ , construct an MBE byte with a value equal to I. The procedure is complete. Otherwise, continue from step 2.
+
+The result of this procedure is that one or more MBE bytes with the 3 high order bits equal to binary '110' contain 5 bits of the absolute value of the negative integer each, starting with the least significant 5 bits and proceeding with each MBE to more significant bits. The final MBE byte has the high order bit set to 0, and contains the 7 most significant bits of the absolute value of the negative integer.
+
+Another result is that if the negative integer value is  $\geq -4095$ , it is represented by two MBE bytes.
+
+This procedure shall not be used to code the value negative zero. The use of negative zero is reserved for possible future signalling.
+
+#### A.2.3 Decoding variable length integers
+
+In the position within an MBE where a variable-length integer begins, high order bits equal to:
+
+binary 0 indicates the final (and only) byte of a non-negative integer;
+
+binary 10 indicates the first byte of a non-negative integer; and
+
+binary 11 indicates the first byte of a negative integer.
+
+### A.3 GenericParameter classes and associated translation procedures
+
+In order to facilitate efficient translation to ITU-T H.320 systems, three classes of **GenericParameter** within the **messageContent** sequence are defined here.
+
+Each **GenericParameter** class is identified by its own range of **standard ParameterIdentifier**. Table A.1 shows these classes, called **PID/VALUE** (representing a **parameterIdentifier/parameterValue** pair), **X/VALUE** (representing an omitted **parameterIdentifier** and a present **parameterValue**), and **PID/X** (representing a present **parameterIdentifier** and omitted **parameterValue**).
+
+ITU-T H.320-H.245 gateways shall translate all **messageContent** regardless of whether the content is understood by the gateway. This procedure allows gateways to properly parse and translate messages even if new **GenericParameters** are added to the **messageContent** in the future.
+
+**Table A.1 – ITU-T H.239 standard ParameterIdentifier classes**
+
+| <b>GenericParameter class</b> | <b>standard ParameterIdentifier range</b> |
+|-------------------------------|-------------------------------------------|
+| PID/VALUE                     | 1-39                                      |
+| X/VALUE                       | 40-79                                     |
+| PID/X                         | 80-127                                    |
+
+The **standard ParameterIdentifier** value 0 is reserved.
+
+NOTE – The value 0 in the place of a **ParameterIdentifier** is used in some circumstances, for example in the coding of the <h239ExtendedVideoCapability> MBE BAS sequence, as a special signal demarcating the end of a list of **GenericParameter** items. To avoid future ambiguity, a **standard ParameterIdentifier** with the value 0 should not be defined.
+
+#### A.3.1 Translation of PID/VALUE
+
+To translate a PID/VALUE parameter from ITU-T H.245 to ITU-T H.320, the **ParameterIdentifier** shall be inserted into the MBE string as a single byte, followed by the **ParameterValue** coded as a variable-length integer.
+
+To translate a PID/VALUE parameter from ITU-T H.320 to ITU-T H.245, the **ParameterIdentifier** shall be copied from a single byte in the MBE, and the **ParameterValue** shall be decoded from the MBE variable-length integer.
+
+#### A.3.2 Translation of X/VALUE
+
+To translate a X/VALUE parameter from ITU-T H.245 to ITU-T H.320, the **ParameterIdentifier** shall be discarded, and the **ParameterValue** shall be coded into the MBE as a variable-length integer.
+
+To translate a X/VALUE parameter from ITU-T H.320 to ITU-T H.245, the **ParameterIdentifier** shall be the one specified for the **GenericParameter** corresponding to the X/VALUE parameter in the ITU-T H.320 syntax, and the **ParameterValue** shall be decoded from the MBE variable-length integer.
+
+NOTE – Because **GenericParameters** in the X/VALUE class are coded in MBEs with no **ParameterIdentifier**, such parameters are not extensible in the same way as other classes. Such parameters
+
+should be defined in the future only when extensibility is not required. When this class is used, the syntax of the MBE must specify the location of such **ParameterValues**.
+
+#### **A.3.3 Translation of PID/X**
+
+To translate a PID/X parameter from ITU-T H.245 to ITU-T H.320, the **ParameterIdentifier** shall be inserted into the MBE string as a single byte, and the **ParameterValue** shall be discarded.
+
+To translate a PID/X parameter from ITU-T H.320 to ITU-T H.245, the **ParameterIdentifier** shall be copied from a single byte in the MBE, and the **ParameterValue** shall be set to "logical".
+
+# Annex B
+
+## ITU-T H.320 additional media channel
+
+(This annex forms an integral part of this Recommendation.)
+
+## B.1 ITU-T H.320 additional media channel
+
+This clause defines the ITU-T H.320 Additional Media Channel (AMC). It does not apply to ITU-T H.245 signalling-based systems, as ITU-T H.245 already supports multiple logical channels.
+
+The ITU-T H.320 AMC creates a partition of the traditional ITU-T H.320 video channel. When the AMC is in use, the total video bit rate is split into two separate subchannels: the main video channel and the AMC.
+
+Each video sub-channel shall use its own BCH (511,493) code for forward error correction.
+
+The partitioning shall be determined from the subTimeslotCount value signalled in the AMC-open command by the procedure described below.
+
+Starting from sub-timeslot 8 in the highest-numbered timeslot that is not occupied by the HSD channel, and progressing toward lower numbered sub-timeslots in each lower-numbered timeslot, the AMC shall occupy all bit positions in subTimeslotCount sub-timeslots that would otherwise have been allocated to the ITU-T H.320 traditional video channel. Bit positions which are occupied by channels other than the ITU-T H.320 traditional video channel (audio, FAS, BAS, LSD, ECS, etc.) shall not be included in the AMC. For restricted calls, in which sub-timeslot 8 is not available for use, sub-timeslot 8 is considered to exist, but as occupied by a channel other than the ITU-T H.320 traditional video channel.
+
+The video channel bit positions not included in the AMC shall be occupied by the main video channel.
+
+To simplify management of the AMC, a limited set of numbers of sub-timeslots for the AMC are permitted to be signalled in the **AMC-cap** capability and **AMC-open** command.
+
+Coexistence of HSD and AMC is an optional capability which shall be signalled as part of the AMC-cap (see clause B.4).
+
+### B.2 AMC multiplex example 1
+
+For example, assume that the AMC channel is signalled as using the "Presentation" role and occupying 5 sub-timeslot positions in a  $2 \times 64$  kbit/s call as shown in Figure B.1. This AMC channel would be opened using the command <AMC-open><0x22><0x05> (see clause B.5).
+
+All video bits from timeslot 2, sub-timeslot 4 to timeslot 7, sub-timeslot 8, inclusive, are used for the AMC. These 5 timeslots represent 40 kbit/s ( $5 \times 8000$ ), but since some of the bits in sub-timeslot 8 are used for FAS and BAS, the actual AMC bit rate is 38.4 kbit/s.
+
+The remaining video bits are occupied by the main video channel (marked "V" in Figure B.1), also providing 38.4 kbit/s in this example.
+
+| Initial timeslot (B-channel 1) |   |   |   |   |   |   |     | Additional timeslot (B-channel 2) |   |   |     |     |     |     |     |
+|--------------------------------|---|---|---|---|---|---|-----|-----------------------------------|---|---|-----|-----|-----|-----|-----|
+| sub-timeslot 1                 | 2 | 3 | 4 | 5 | 6 | 7 | 8   | 1                                 | 2 | 3 | 4   | 5   | 6   | 7   | 8   |
+| a                              | a | a | a | a | a | V | FAS | V                                 | V | V | AMC | AMC | AMC | AMC | FAS |
+| a                              | a | a | a | a | a | V |     | V                                 | V | V | AMC | AMC | AMC | AMC |     |
+| a                              | a | a | a | a | a | V |     | V                                 | V | V | AMC | AMC | AMC | AMC |     |
+|                                |   |   |   |   |   | V | BAS | V                                 | V | V | AMC | AMC | AMC | AMC | BAS |
+|                                |   |   |   |   |   | V |     | V                                 | V | V | AMC | AMC | AMC | AMC |     |
+|                                |   |   |   |   |   | V |     | V                                 | V | V | AMC | AMC | AMC | AMC |     |
+|                                |   |   |   |   |   | V | V   | V                                 | V | V | AMC | AMC | AMC | AMC | AMC |
+|                                |   |   |   |   |   | V | V   | V                                 | V | V | AMC | AMC | AMC | AMC | AMC |
+|                                |   |   |   |   |   | V | V   | V                                 | V | V | AMC | AMC | AMC | AMC | AMC |
+|                                |   |   |   |   |   | V | V   | V                                 | V | V | AMC | AMC | AMC | AMC | AMC |
+|                                |   |   |   |   |   | V | V   | V                                 | V | V | AMC | AMC | AMC | AMC | AMC |
+|                                |   |   |   |   |   | V | V   | V                                 | V | V | AMC | AMC | AMC | AMC | AMC |
+|                                |   |   |   |   |   | V | V   | V                                 | V | V | AMC | AMC | AMC | AMC | AMC |
+|                                |   |   |   |   |   | V | V   | V                                 | V | V | AMC | AMC | AMC | AMC | AMC |
+|                                |   |   |   |   |   | V | V   | V                                 | V | V | AMC | AMC | AMC | AMC | AMC |
+|                                |   |   |   |   |   |   |     |                                   |   |   |     |     |     |     |     |
+
+**Figure B.1 (modified from [ITU-T H.221]) – Example bit positions  
+for video in two B-channels**
+
+**B.3 AMC multiplex example 2**
+
+Figure B.2 below gives an example of a call using six 56 kbit/s timeslots according to [ISO/IEC 13871] (Bonding) Mode 1, with 64 kbit/s HSD and 12 AMC sub-timeslots used for the "Live" role. This AMC channel would be opened using the command <AMC-open><0x12><0x0C> (see clause B.5).
+
+Using the given rules, the distribution of the available bits is shown.
+
+This figure illustrates that ITU-T H.239 treats the timeslots as if each contained all 8 possible sub-timeslots, even in the case of restricted calls in which only sub-timeslots 1 through 7 are available.
+
+In the figure each letter represents a single sub-timeslot position as follows:
+
+- "a" represents audio bits;
+- "x" represents sub-timeslot 8 which is not available in this example;
+- "V" represents the main video channel;
+- "A" represents the AMC channel; and
+- "H" represents the HSD channel.
+
+Rec. ITU-T H.239 (10/2014) 21
+
+![Figure B.2 – Example bit positions in restricted call](2a23751710f7827065d2b99b6df588df_img.jpg)
+
+**Figure B.2 – Example bit positions in restricted call**
+
+Figure B.2 – Example bit positions in restricted call
+
+**B.4 AMC capabilities**
+
+The ITU-T H.320 AMC capability exchange is handled by an MBE message (see clause 2.2.3 of [ITU-T H.230]). This MBE message uses the type identification byte <AMC-cap> (see Table 2 of [ITU-T H.230]). A device shall signal the AMC capability by including within its capability set the message:
+
+{ Start-MBE / 3 / <AMC-cap> / optionByte1 / optionByte2 }
+
+The AMC capability MBE bytes shall indicate the capability to receive an AMC with the specified number of sub-timeslots. It shall also indicate whether the device is capable of receiving HSD and AMC simultaneously.
+
+optionByte1 and optionByte2 are shown in Tables B.1 and B.2 respectively. Each bit in the fields subTimeslotCapability1 and subTimeslotCapability2 indicate the ability to support AMC using the shown number of sub-timeslots. All devices that support AMC shall support operation with 8 sub-timeslots and with 0 sub-timeslots. The capability to operate with 0 sub-timeslots is not explicitly signalled.
+
+NOTE – Operation with 0 sub-timeslots permits transmitters to reduce the bit rate to 0 during a presentation when the content is not changing, without closing the AMC channel. Closing the AMC channel may cause some end-user system implementations to stop displaying the most recently transmitted video frame.
+
+The AMC+HSDCap field indicates the capability to simultaneously support the AMC and HSD channels.
+
+Reserved fields shall be set to 0 and ignored by receivers.
+
+**Table B.1 – optionByte1**
+
+| 1 (MSB)                | 2                      | 3 | 4  | 5  | 6  | 7  | 8 (LSB) |
+|------------------------|------------------------|---|----|----|----|----|---------|
+| Reserved<br>(set to 0) | subTimeslotCapability1 |   |    |    |    |    |         |
+|                        | 5                      | 8 | 12 | 16 | 24 | 32 | 48      |
+
+22 Rec. ITU-T H.239 (10/2014)
+
+**Table B.2 – optionByte2**
+
+| 1 (MSB)                | 2                               | 3 | 4                      | 5 | 6 | 7 | 8 (LSB)                                                     |
+|------------------------|---------------------------------|---|------------------------|---|---|---|-------------------------------------------------------------|
+| Reserved<br>(set to 0) | subTimeslotCapability2<br>64 96 |   | Reserved<br>(set to 0) |   |   |   | AMC+HSDCap<br>1 = Capable of<br>simultaneous<br>AMC and HSD |
+
+### **B.5 AMC controls & indications**
+
+AMC signalling applies only to H.320 devices that have expressed the capability to support AMC by signalling **AMC-cap**.
+
+Mode changes that are signalled by the messages AMC-open and AMC-close, and mode changes affecting the content of the AMC channel, shall conform to the mode switch procedures in clause 8.2 of [ITU-T H.242]. C&I messages for mode changes affecting the content of the AMC channel shall be sent using the AMC-C&I facility in clause B.5.3.
+
+#### **B.5.1 AMC-open**
+
+This command shall be sent to open an AMC in the ITU-T H.221 multiplex. It shall be immediately followed by two SBE numbers, AMCOpenByte1 and AMCOpenByte2:
+
+AMC-open<AMCOpenByte1><AMCOpenByte2>
+
+Tables B.3 and B.4 show the syntax for AMCOpenByte1 and AMCOpenByte2.
+
+**Table B.3 – AMCOpenByte1**
+
+| 1 (MSB)   | 2 | 3 | 4 | 5         | 6 | 7 | 8 (LSB) |
+|-----------|---|---|---|-----------|---|---|---------|
+| roleLabel |   |   |   | channelID |   |   |         |
+
+The roleLabel field shall be coded as in Table B.5.
+
+The channelID field shall be coded as in Table 9.
+
+**Table B.4 – AMCOpenByte2**
+
+| 1 (MSB)  | 2                | 3 | 4 | 5 | 6 | 7 | 8 (LSB) |
+|----------|------------------|---|---|---|---|---|---------|
+| reserved | subTimeslotCount |   |   |   |   |   |         |
+
+The reserved field shall be set to 0 and ignored by receivers.
+
+The subTimeslotCount field shall contain a count of subTimeslots that the AMC occupies, as described in clause B.1. This value shall be one of those values indicated in the far-end's AMC capability, or zero.
+
+**Table B.5 – roleLabel field values**
+
+| roleLabel value | Role           |
+|-----------------|----------------|
+| 1               | "Live"         |
+| 2               | "Presentation" |
+
+All other values are reserved.
+
+#### B.5.2 AMC-close
+
+This command shall be sent to close an AMC in the ITU-T H.221 multiplex. It shall be immediately followed by a single additional SBE numbers, AMCCloseByte1:
+
+AMC-close<AMCCloseByte1>
+
+Table B.6 shows the syntax for AMCCloseByte1.
+
+**Table B.6 – AMCCloseByte1**
+
+| 1 (MSB)             | 2 | 3 | 4 | 5         | 6 | 7 | 8 (LSB) |
+|---------------------|---|---|---|-----------|---|---|---------|
+| reserved (set to 0) |   |   |   | channelID |   |   |         |
+
+The reserved field shall be set to 0 and ignored by receivers.
+
+The channelID field shall be coded as in Table 9.
+
+#### B.5.3 AMC Control & Indication (AMC-C&I)
+
+The H.320 AMC-C&I MBE message is used to signal a Table 1 of [ITU-T H.230] C&I that applies to the indicated AMC channel.
+
+ITU-T H.320-H.245 gateways shall convert these signals between the two systems in the same manner as the equivalent signals for the traditional H.320 video channel, according to the procedures of Annex A.
+
+This MBE message uses the type identification byte <AMC-C&I> (see Table 2 of [ITU-T H.230]). The structure of this MBE is:
+
+{ Start-MBE / N / <AMC-C&I> / AMC-C&IByte1 / B<sub>2</sub> . . . B<sub>N-1</sub> }
+
+The AMC-C&IByte1 byte is structured as shown in Table B.7.
+
+**Table B.7 – AMC-C&IByte1**
+
+| 1 (MSB)             | 2 | 3 | 4 | 5         | 6 | 7 | 8 (LSB) |
+|---------------------|---|---|---|-----------|---|---|---------|
+| reserved (set to 0) |   |   |   | channelID |   |   |         |
+
+The reserved field shall be set to 0 and ignored by receivers.
+
+The channelID field shall be coded as in Table 9 and shall represent the channel to which the C&I message applies.
+
+Bytes B<sub>2</sub> through B<sub>N-1</sub> shall contain a single C&I BAS message from Table 1 of [ITU-T H.230]. The AMC-C&I message and capability messages are not considered C&I messages for the purposes of this clause.
+
+This message may be 1 or more bytes in length, as specified with all escape codes, extensions, or MBE sequences in Table A.1 of [ITU-T H.221].
+
+All C&I messages for the main video channel received within the AMC-C&I shall be treated as if they had been received on the BAS channel.
+
+### B.6 Multipoint considerations
+
+When the BAS command **MCS** (see clause 3.5 of [ITU-T H.230]) is received within the **AMC-C&I** message, the end-user system shall ensure, by mode change if necessary, that its outgoing AMC occupies the same ITU-T H.221 multiplex bit positions as its incoming AMC.
+
+If the AMC is not carrying a video stream, the end-user system shall send BCH fill in the AMC to comply with **MCS**.
+
+When the BAS command **MCN** (see clause 3.5 of [ITU-T H.230]) is received within the **AMC-C&I** message, the end-user system shall cancel the effect of **MCS**.
+
+# Appendix I
+
+## ASN.1 OIDs defined in this Recommendation
+
+(This appendix does not form an integral part of this Recommendation.)
+
+| <b>OID</b>                                                                                               | <b>Clause reference</b> |
+|----------------------------------------------------------------------------------------------------------|-------------------------|
+| { itu-t(0) recommendation(0) h(8) 239 generic-capabilities(1) h239ControlCapability(1) }                 | 7.1                     |
+| { itu-t(0) recommendation(0) h(8) 239 generic-capabilities(1)<br><b>h239ExtendedVideoCapability(2)</b> } | 7.1                     |
+| { itu-t(0) recommendation(0) h(8) 239 generic-message(2) }                                               | 8.1                     |
+
+
+
+# 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.1-201303-I_PDF-E/29aa6165ccf449dee0b4335676fa7b1a_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/29aa6165ccf449dee0b4335676fa7b1a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7c787cd733ba18df2e0a5e2c6eda184549870277
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/29aa6165ccf449dee0b4335676fa7b1a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ceacadc85f5264c1ba5053e34fab0ea44898ed5ff57f301ed47d3416bd73f68c
+size 97275
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/33a8f3f01dfa8bce75d23017855a13c5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..da51ffa0aeac3c765be79097b8b0901359850cad
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/33a8f3f01dfa8bce75d23017855a13c5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9b06a759c58fe9a0e9832d2c8af6fd341ccb8d2289fafae28cfad59e79abb8e9
+size 89738
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/3c6151f296d5800335472b7dc00ce423_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/3c6151f296d5800335472b7dc00ce423_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..92bab4a53795134fb95eafb692980b09a758712d
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/3c6151f296d5800335472b7dc00ce423_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4d1b303318422688879e27cf64518cb0551c5441e73cf31b60e85c2f0d6e6402
+size 28449
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..406b3375e6b683d611436c40ba300f11c334e7ee
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8992d673e7c7ea348e028e9e2c5c2e17bd4ba620d703e1f5d37061943cde04dc
+size 31754
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d22c79d2de17778de22a09fa8b2be51c8de37bfd
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6bbdf46ba4741549ab3edf6da22df3f084f215316afeee32f85199da16e1aa93
+size 58926
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..09fd06645bc5b96c3b94ccc0d2d536f49a87f2ac
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8572a867599cb5242f71d600e5b8815090aeae0a96bd948dc9bb4c08a6f6f248
+size 60470
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..60b975cc1db2f37da42b69713a865150bd3ce7e7
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:757898016c17ad4c2934a499687a8749c0735d8c933a0379eecf4fb45caf036d
+size 6636
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/7188dd653353235466aea783783e26c8_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/7188dd653353235466aea783783e26c8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1d9911e8cdfe17729d890793b85bce994353527e
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/7188dd653353235466aea783783e26c8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c75c47f3cea0e248292285519391d1448e96e37a7710a48ea504056b1abc44b7
+size 60808
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8fde3384ebec4e74645d98da2656f97a4183fc14
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd179262405b67f127f806dcc1a28a6f32d59b2cbf590989111a1a6e93bce333
+size 52745
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fe5f3a4f1bbf91b5db19c41d35f5d6214f5353da
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5757c152c1d7398e23c60f252fb87b99d794fa106a44f7fbd94df150aae8931e
+size 60466
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/9870bf462aa0d916a16d14b5a100c60a_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/9870bf462aa0d916a16d14b5a100c60a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0664dc096b977cb47c21b0e04c13504196b8af27
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/9870bf462aa0d916a16d14b5a100c60a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:74a427cdd8f53993eea1ac2e1a43549665b5e67ee4d20420fdb4d02b53afec9c
+size 119005
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/9de1e2f286f8fee526dc87eafad60401_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/9de1e2f286f8fee526dc87eafad60401_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..11056a6700fe5ab6a983d7aba919cbeae0a21f2b
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/9de1e2f286f8fee526dc87eafad60401_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:05b241e3517ef859c7eb62a08db54d051edddf678342c8329ad82d917a0faeba
+size 98307
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/aeb2a26a07219661191294dba528067a_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/aeb2a26a07219661191294dba528067a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ed8ee60be2700a39f632ba76c891efeeb86de05a
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/aeb2a26a07219661191294dba528067a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e06f69f3fd5491c3a2169afee3016cede9e856acea5b220ad904326ca9d03ef1
+size 28511
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..16a127c57df1334657b7e17d3e4ba5a37093b958
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a1ad3e15b0981e19684ce1bc7972b17f32d37735c33a94df15f22eee2a87d18c
+size 39375
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6549426fcb5cfc318ffefd78c9fa6126a70e9d4e
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ab043105f4a4fb2a9a7a781a2410f3fe92fbe40322aa46d4f47faea66a1cadb4
+size 41347
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..73d146356a554029b302f6cb7d5804be2e054aca
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2748c9f8415bfefce597a69a20555b35d3b36d99b60e56bdc970b019de138d55
+size 45007
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..207d1d0dff4af920918902db92ed9180aafb12ad
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6f9b11d5c85f9882b26a873198912793dffc1884f9b82e3a54cf3e7272d4a864
+size 46059
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..294f742daa720b1e336ed9152add7a2e377747f0
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:60736bb39c20f19ccd68f6dd7632dfb073287fb9842c3790efbe858b79765c84
+size 81305
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/dbe4ffa9778863279b48b56fe097cd23_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/dbe4ffa9778863279b48b56fe097cd23_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3fa0419464783d95689bcff3fcf83cd2494fdf48
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/dbe4ffa9778863279b48b56fe097cd23_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:852046f59d95cb5eeeb4339cd59b310d566cd646ef7073fbd4a614fff65cf272
+size 47000
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1d1dae4e6f0d44b9541e049e35ec53c7b230a6a4
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b3029a20efcf52d4395b04b68ec345ee511a74c2950322c446aabb26bd31a1ac
+size 50673
diff --git a/marked/H/T-REC-H.248.1-201303-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.248.1-201303-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..52e825f88439165777952bf4e7279e18b189ca79
--- /dev/null
+++ b/marked/H/T-REC-H.248.1-201303-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7963620ef30452847564636130d87216828961e13302bfed040a3b43deed43c1
+size 69632
diff --git a/marked/H/T-REC-H.248.10-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.248.10-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..104a57fbd03964ffd2520508b2be42e03343d20f
--- /dev/null
+++ b/marked/H/T-REC-H.248.10-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.248.10-200107-I_PDF-E/raw.md b/marked/H/T-REC-H.248.10-200107-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..34ca5d278a9793aa1705ce7bba3e1db3d7890166
--- /dev/null
+++ b/marked/H/T-REC-H.248.10-200107-I_PDF-E/raw.md
@@ -0,0 +1,233 @@
+
+
+![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.248.10**
+
+(07/2001)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+---
+
+**Gateway control protocol: Media gateway  
+resource congestion handling package**
+
+ITU-T Recommendation H.248.10
+
+---
+
+# 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        |
+| <b>Communication procedures</b>                                               | <b>H.240–H.259</b> |
+| 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.10**
+
+## **Gateway control protocol: Media gateway resource congestion handling package**
+
+### **Summary**
+
+This Recommendation describes a package for Media Gateway Resource Congestion Handling for use with the H.248.1 Gateway Control Protocol. As defined in ITU-T Rec. H.248.1, a "package" is an extension to H.248.1 that supports specific behaviour.
+
+NOTE – This Recommendation has been renumbered. It was formerly known as ITU-T Rec. H.248, Annex M2.
+
+###### **Source**
+
+ITU-T Recommendation H.248.10 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, by any means whatsoever, without the prior written permission of ITU.
+
+### CONTENTS
+
+###### Page
+
+|       |                                   |   |
+|-------|-----------------------------------|---|
+| 1     | Scope.....                        | 1 |
+| 2     | Definitions .....                 | 1 |
+| 3     | References.....                   | 1 |
+| 4     | Congestion Handling package ..... | 1 |
+| 4.1   | Properties .....                  | 1 |
+| 4.2   | Events .....                      | 1 |
+| 4.2.1 | MGCongestion .....                | 1 |
+| 5     | Signals.....                      | 2 |
+| 6     | Statistics.....                   | 2 |
+| 7     | Procedures.....                   | 2 |
+
+
+
+## **Gateway control protocol: Media gateway resource congestion handling package**
+
+## **1 Scope**
+
+This Recommendation defines a package that extends the applicability of the H.248.1 Gateway Control Protocol Recommendation. Specifically, this Recommendation describes a package for the H.248.1 gateway protocol related to Media Gateway Resource Congestion Handling. With the root termination implementing this package, a gateway is expected to report congestion events to a Media Gateway Controller (MGC).
+
+## **2 Definitions**
+
+See ITU-T Rec. H.248.1.
+
+## **3 References**
+
+See ITU-T Rec. H.248.1.
+
+## **4 Congestion Handling package**
+
+Package Name: CHP
+
+PackageID: chp, 0x0029
+
+Description:
+
+The package makes it possible for the MG to control its load.
+
+The events in this package may be provisioned in the MG.
+
+The event in this package may only be applied to the Root termination.
+
+Version: 1
+
+Extends: None
+
+### **4.1 Properties**
+
+NA
+
+### **4.2 Events**
+
+#### **4.2.1 MGCongestion**
+
+Event name: MGCon
+
+EventID: mgcon, (0x0001)
+
+Description:
+
+This event occurs when the MG requires that the MGC start or finish load reduction towards the MG or to adjust the Load Reduction Percentage. The event is ordered by the MGC or provisioned.
+
+EventsDescriptor Parameters: None
+
+ObservedEventsDescriptor Parameters
+
+Parameter Name: Reduction
+
+ParameterID: reduction, (0x0001)
+
+Type: Integer
+
+Possible Values: 0-100
+
+It represents a percentage of the load that the MGC is requested to block (reject or deflect).
+
+A value of 0 means that no reduction shall be applied.
+
+A value of 100 means that the MGC shall block all load towards the MG that is possible to block.
+
+## 5 Signals
+
+NA
+
+## 6 Statistics
+
+NA
+
+## 7 Procedures
+
+When the MGC receives a load reduction notification it tries to reduce the processing loads that it creates on the MG according to the parameter value. For example, if the Reduction Percentage is 20 then the MGC shall try to block 20% of the load that it would otherwise (without any reduction) have generated on the MG.
+
+It is left to the implementation to decide how the MGC shall translate a load reduction of 20% to a certain concrete action.
+
+One possible implementation is to reject (or redirect) a percentage of new calls based on 20% of the current calls in the MG. Another possibility is to block 20% of the commands that create new contexts.
+
+The MGC is free to support priorities by blocking low priority calls (originating normal calls) in the first place when load reduction is requested.
+
+If calls of different priority generate very different loads on the MG, and load reduction is implemented by rejecting a certain fraction of the calls, then it is recommended to give each call a weight proportional to the average load it is expected to create.
+
+
+
+## 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                                                                   |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                      |
+| 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.13-200203-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.248.13-200203-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..104a57fbd03964ffd2520508b2be42e03343d20f
--- /dev/null
+++ b/marked/H/T-REC-H.248.13-200203-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.248.13-200203-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/H/T-REC-H.248.13-200203-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aefc2fa88d9389e5d52d94e48cfa207eb39c7f41
--- /dev/null
+++ b/marked/H/T-REC-H.248.13-200203-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8e1a551024d59e8d121d8c4b7f388067036e182017e5cae83685a22a630aca73
+size 82251
diff --git a/marked/H/T-REC-H.248.20-201303-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.20-201303-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0ad98c6e45b6c52f074f0054407ca88a640d8f1d
--- /dev/null
+++ b/marked/H/T-REC-H.248.20-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.20-201303-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg b/marked/H/T-REC-H.248.20-201303-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4415f1d9d99cff2d70c1989dc7f8d455dc6fd9d1
--- /dev/null
+++ b/marked/H/T-REC-H.248.20-201303-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1f07f32342a9c075145beb8d8d741eaf5bed71d129067dd187d5b3ce1e60a7aa
+size 49921
diff --git a/marked/H/T-REC-H.248.20-201303-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/H/T-REC-H.248.20-201303-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..565cd8d002c046b8030b1ff53aa8f5bc7e60d6ae
--- /dev/null
+++ b/marked/H/T-REC-H.248.20-201303-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:53f6ef3dcddf54708d05fa8dab5596f08d80841c59abca3b6ce54ce3ddaf3672
+size 32885
diff --git a/marked/H/T-REC-H.248.22-201303-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg b/marked/H/T-REC-H.248.22-201303-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..99f2aa34a23b0275d42db4eb6105b23bfde270df
--- /dev/null
+++ b/marked/H/T-REC-H.248.22-201303-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7bf69033915075eae87c554a3ca70beb0bd1d7a48151c9f75f35633366d482d7
+size 165517
diff --git a/marked/H/T-REC-H.248.22-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.248.22-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7cb4d5d11511a2e361553824d508fde008fab400
--- /dev/null
+++ b/marked/H/T-REC-H.248.22-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:abbadb5a4216778c87e818254a2116b3161c9b23f839b90107c90e8f05b9e8c3
+size 3538
diff --git a/marked/H/T-REC-H.248.22-201303-I_PDF-E/raw.md b/marked/H/T-REC-H.248.22-201303-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..80c695e3d32d60c24049db4327fc3c0dc5d88d38
--- /dev/null
+++ b/marked/H/T-REC-H.248.22-201303-I_PDF-E/raw.md
@@ -0,0 +1,300 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.22**
+
+(03/2013)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+---
+
+**Gateway control protocol: Shared Risk Group  
+package**
+
+Recommendation ITU-T H.248.22
+
+# 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        |
+| <b>Communication procedures</b>                                               | <b>H.240–H.259</b> |
+| 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.22
+
+## Gateway control protocol: Shared Risk Group package
+
+## Summary
+
+Recommendation ITU-T H.248.22 describes a package to enable the media gateway controller (MGC) to indicate to the media gateway (MG) to use or not to use network resources associated with a shared risk group when setting up connections. When network connections are associated with ephemeral terminations in the MG, certain resources are used. A failure in the MG may result in the loss of certain groups of resources, whilst other groups of resources remain unaffected. The resources that share a risk of failure are called a shared risk group. A shared risk group is simply a grouping of the network resources (e.g., IP interfaces) sharing the same risk of failure. Each shared risk group could, for example, contain a number of IP interfaces located on the same piece of hardware. If a resource failure occurs, only terminations in the shared risk group corresponding to the failed resource are affected while other terminations are not.
+
+This revision incorporates corrections to several values in the procedure associated with the usage of the "Include shared risk group" property.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group |
+|---------|----------------|------------|-------------|
+| 1.0     | ITU-T H.248.22 | 2003-07-14 | 16          |
+| 2.0     | ITU-T H.248.22 | 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                  | 3    |
+| 3 Definitions .....                | 3    |
+| 4 Abbreviations and acronyms ..... | 3    |
+| 5 Shared risk group package.....   | 3    |
+| 5.1 Properties.....                | 3    |
+| 5.2 Events .....                   | 4    |
+| 5.3 Signals .....                  | 4    |
+| 5.4 Statistics.....                | 4    |
+| 5.5 Procedures .....               | 4    |
+
+
+
+## **Gateway control protocol: Shared Risk Group package**
+
+## **1 Scope**
+
+When network connections are associated with ephemeral terminations in the MG, certain resources are used. A failure in the MG may result in the loss of certain groups of resources, whilst other groups of resources remain unaffected. The resources that share a risk of failure are called a shared risk group. A shared risk group is simply a grouping of the network resources (e.g., IP interfaces) sharing the same risk of failure. Each shared risk group could, for example, contain a number of IP interfaces located on the same piece of hardware. If a resource failure occurs, only terminations in the shared risk group corresponding to the failed resource are affected while other terminations are not.
+
+The MGC may select different shared risk groups when the redundancy of network resources has to be controlled, or when the MGC wishes to specify which group of resources are to be used. With this functionality the MGC is given control of the resources used by ephemeral terminations in the MG. The MGC may order the MG to use resources from a selected Shared Risk Group, or not to use resources from a Shared Risk Group. This gives an advantage over using Termination ID schemes to link resource groups in that the MGC can specify certain resources to avoid in a CHOOSE (\$) Termination ID scenario.
+
+The capability to order the MG to use diverse resources for different connections is particularly useful when a pair of connections is used for a primary and secondary link e.g., for signalling transport.
+
+Figure 1 shows an example of a scenario where two shared risk groups have been defined and are used by ephemeral terminations. Context 3 represents a Primary Link and Context 5 is its secondary link.
+
+![Diagram of a Media Gateway showing six contexts (Context 1 to Context 6) with terminations, RTP streams, and SCN bearer channels. Contexts 1 and 2 are on Interface board 1; Contexts 3 and 4 are on Interface board 2 (grouped as SRGI 1); Contexts 5 and 6 are on Interface board 3 (grouped as SRGI 2). Each context has a central asterisk symbol.](3121ebddccf183ca63bb9781be440a7e_img.jpg)
+
+The diagram illustrates a Media Gateway architecture with six contexts, each containing a central asterisk (\*) symbol. The contexts are organized into three interface boards:
+
+- Interface board 1:**
+  - Context 1:** Termination 1 (RTP stream) — \* — Termination 7 (SCN bearer channel)
+  - Context 2:** Termination 2 (RTP stream) — \* — Termination 8 (SCN bearer channel)
+- Interface board 2:**
+  - Context 3:** Termination 3 (RTP stream) — \* — Termination 9 (SCN bearer channel)
+  - Context 4:** Termination 4 (RTP stream) — \* — Termination 10 (SCN bearer channel)
+- Interface board 3:**
+  - Context 5:** Termination 5 (RTP stream) — \* — Termination 11 (SCN bearer channel)
+  - Context 6:** Termination 6 (RTP stream) — \* — Termination 12 (SCN bearer channel)
+
+Terminations 3 and 4 are grouped under **SRGI 1**, and Terminations 5 and 6 are grouped under **SRGI 2**. Arrows indicate bidirectional flow for each termination.
+
+Diagram of a Media Gateway showing six contexts (Context 1 to Context 6) with terminations, RTP streams, and SCN bearer channels. Contexts 1 and 2 are on Interface board 1; Contexts 3 and 4 are on Interface board 2 (grouped as SRGI 1); Contexts 5 and 6 are on Interface board 3 (grouped as SRGI 2). Each context has a central asterisk symbol.
+
+H.248.22\_F01
+
+**Figure 1 – Example of shared risk group usage**
+
+The Shared Risk Group Package may be used whenever the behaviour described in the procedures section of the package is required.
+
+## 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 shared risk group:** A Shared Risk Group consists of resources or groups of resources that share the same risk of failure. It is the relationship between resources in a MG that defines a shared risk group.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                            |
+|------|----------------------------|
+| DSP  | Digital Signal Processor   |
+| MG   | Media Gateway              |
+| MGC  | Media Gateway Controller   |
+| RTP  | Real Time Protocol         |
+| SCN  | Switched Circuit Network   |
+| SRGI | Shared Risk Group Identity |
+
+## 5 Shared risk group package
+
+|                                      |                                                                                                                             |
+|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|
+| <b>Package name:</b>                 | Shared Risk Group Package                                                                                                   |
+| <b>Package ID:</b>                   | shrisk (0x006b)                                                                                                             |
+| <b>Description:</b>                  | This package defines properties and procedures that are used to distinguish between different shared risk groups in the MG. |
+| <b>Version:</b>                      | 1                                                                                                                           |
+| <b>Designed to be extended only:</b> | No                                                                                                                          |
+| <b>Extends:</b>                      | None                                                                                                                        |
+
+### 5.1 Properties
+
+#### 5.1.1 Include shared risk group
+
+|                       |                                                                                                                                                             |
+|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Property name:</b> | Include shared risk group                                                                                                                                   |
+| <b>Property ID:</b>   | incl (0x0001)                                                                                                                                               |
+| <b>Description:</b>   | The value of this property indicates if the shared risk group specified is requested to be used or to not be used (see clause 5.5.1.1 for further details). |
+
+|                         |                                                                                                                                 |
+|-------------------------|---------------------------------------------------------------------------------------------------------------------------------|
+| <b>Type:</b>            | Sublist of type Boolean                                                                                                         |
+| <b>Possible values:</b> | "on" (TRUE) Use resources from the specified SRGI only [Default]<br>"off" (FALSE) Use resources from any but the specified SRGI |
+| <b>Defined in:</b>      | Termination State Descriptor                                                                                                    |
+| <b>Characteristics:</b> | Write Only                                                                                                                      |
+
+#### 5.1.2 Shared risk group identity request
+
+|                         |                                                                                                                           |
+|-------------------------|---------------------------------------------------------------------------------------------------------------------------|
+| <b>Property name:</b>   | Shared risk group identity request                                                                                        |
+| <b>Property ID:</b>     | srgir (0x0002)                                                                                                            |
+| <b>Description:</b>     | The value of this property specifies the shared risk group identity                                                       |
+| <b>Type:</b>            | Sublist of type Integer                                                                                                   |
+| <b>Possible Values:</b> | The values specify the SRGI according to a scheme understood by both MGC and MG (see clause 5.5.1.3 for further details). |
+| <b>Defined in:</b>      | Termination State Descriptor                                                                                              |
+| <b>Characteristics:</b> | Write Only                                                                                                                |
+
+#### 5.1.3 Assigned shared risk group identity
+
+|                         |                                                                                                                                                           |
+|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Property name:</b>   | Assigned shared risk group identity                                                                                                                       |
+| <b>Property ID:</b>     | asrgi (0x0003)                                                                                                                                            |
+| <b>Description:</b>     | The value of this property specifies the Shared risk group identity that has been allocated by the MG. This value cannot be directly modified by the MGC. |
+| <b>Type:</b>            | Integer                                                                                                                                                   |
+| <b>Possible Values:</b> | The values specify the SRGI according to a scheme understood by both MGC and MG (see clause 5.5.1.2 for further details).                                 |
+| <b>Defined in:</b>      | Termination State Descriptor                                                                                                                              |
+| <b>Characteristics:</b> | ReadOnly                                                                                                                                                  |
+
+### 5.2 Events
+
+N/A
+
+### 5.3 Signals
+
+N/A
+
+### 5.4 Statistics
+
+N/A
+
+### 5.5 Procedures
+
+#### 5.5.1 Establishment/modification of terminations when using shared risk group
+
+When an MGC determines that an ephemeral termination must use resources belonging to (or different to) a specific shared risk group, an Add/Modify/Move command will be sent to the MG specifying the "*Include shared risk group*" property and the "*Shared risk group identity Request*" property.
+
+##### 5.5.1.1 Usage of the "Include shared risk group" property
+
+The "Include shared risk group" property shall be used to indicate to the MG if resources from the specified shared risk group identity (*shrisk/srgir*) must be used for the termination (*shrisk/incl = on*) or if resources from the specified risk group identity must not be used for the termination (*shrisk/incl = off*). If the MGC is not concerned with which shared risk groups are used then it should not include the *shrisk/incl* nor *shrisk/srgir* properties. The *shrisk/incl* and *shrisk/srgir* properties are valid only for the command that they are contained in. They cannot be read/audited after the execution of the command. Wildcarding values with CHOOSE (\$) or ALL (\*) shall not be used with *shrisk/incl* and/or *shrisk/srgir*. For example: in the case of a semi-permanent connection and a protective secondary link, by specifying (*shrisk/incl = on*, *shrisk/srgir = 1*) for the primary link and (*shrisk/incl = off*, *shrisk/srgir = 1*) for the secondary, the MGC is assured that the primary and secondary links are not sharing the same groups of resources.
+
+The MGC may provide a sublist of *shrisk/incl* and *shrisk/srgir* to the MG to enable the MGC to request that certain shared risk groups shall be used and other shared risk groups shall not be used. The first value of *shrisk/incl* in the sublist corresponds to the first value of *shrisk/srgir* sublist.
+
+##### 5.5.1.2 Usage of the "Assigned shared risk group identity" property
+
+The "Assigned Shared Risk Group Identity (*shrisk/asrgi*)" contains the accumulated shared risk identities of the resources used by the termination. This value cannot be directly written by the MGC. However, it can indirectly be influenced by adding, modifying or subtracting resources from the termination. The MGC can audit this property to determine the shared risk groups used by a termination.
+
+##### 5.5.1.3 Usage of the "Shared risk group identity" property
+
+How the "Shared risk group identity" is associated with MG resources is out of the scope of this Recommendation. The different resources used by a termination may have different "Shared Risk Group Identity" ranges. However, it is assumed that this will be operator configurable and provisioned on both the MGC and MG so that they have a mutual understanding of the Specified Risk Group identity schema. For example, a binary structure of the property can be used. That is, the *shrisk/srgi* decimal integer is treated as a four byte binary number within the MG and MGC. This way different bytes or groups of bits may be used to address different types of resources in the MG. For example: the first two bytes could be used to identify DSP resources while the last two bytes could identify interface boards on the MG. When sent over the GCP link, the binary number is, however, expressed as a decimal number integer.
+
+
+
+
+
+## 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.23-201303-I_PDF-E/raw.md b/marked/H/T-REC-H.248.23-201303-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..4c86f00ed2c1836547c036f683ff6c9a34af1c1c
--- /dev/null
+++ b/marked/H/T-REC-H.248.23-201303-I_PDF-E/raw.md
@@ -0,0 +1,572 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.23**
+
+(03/2013)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+# --- **Gateway control protocol: Enhanced Alerting packages**
+
+Recommendation ITU-T H.248.23
+
+## 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        |
+| <b>Communication procedures</b>                                               | <b>H.240–H.259</b> |
+| 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.23
+
+# Gateway control protocol: Enhanced Alerting packages
+
+## Summary
+
+Recommendation ITU-T H.248.23 defines two packages that provide enhanced alerting and data transfer capabilities for Recommendation ITU-T H.248.1.
+
+This revision includes updated procedures that discuss how to handle race conditions when the dwa signal is used. A clarification is added to the pattern parameter as to what signal should be used.
+
+## History
+
+| Edition | Recommendation               | Approval   | Study Group |
+|---------|------------------------------|------------|-------------|
+| 1.0     | ITU-T H.248.23               | 2003-07-14 | 16          |
+| 1.1     | ITU-T H.248.23 (2003) Cor. 1 | 2004-03-15 | 16          |
+| 2.0     | ITU-T H.248.23               | 2005-01-08 | 16          |
+| 2.1     | ITU-T H.248.23 (2005) Cor. 1 | 2006-05-29 | 16          |
+| 3.0     | ITU-T H.248.23               | 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 Enhanced Alerting Package.....           | 2    |
+| 5.1 Properties.....                        | 2    |
+| 5.2 Events .....                           | 2    |
+| 5.3 Signals .....                          | 2    |
+| 5.4 Statistics.....                        | 4    |
+| 5.5 Procedures .....                       | 4    |
+| 6 Analogue Display Signalling Package..... | 5    |
+| 6.1 Properties.....                        | 5    |
+| 6.2 Events .....                           | 5    |
+| 6.3 Signals .....                          | 5    |
+| 6.4 Statistics.....                        | 9    |
+| 6.5 Procedures .....                       | 9    |
+| Bibliography.....                          | 11   |
+
+# **Introduction**
+
+This Recommendation provides definitions for several supplemental packages for Recommendation ITU-T H.248.1. These packages define alternative signalling for ringing, add the capability for distinctive call waiting tones and address support of functionality for enhanced telephony services which utilize data transfer to the customer premises equipment.
+
+# Recommendation ITU-T H.248.23
+
+# Gateway control protocol: Enhanced Alerting packages
+
+# 1 Scope
+
+This Recommendation defines two packages that provide enhanced alerting and data transfer capabilities for [ITU-T H.248.1]. The support of these packages is optional.
+
+There is a direct mapping between the alert/ri pattern parameter, alert/cw pattern parameter, and to the andisp/dwa pattern parameter. Ringing patterns and call waiting patterns are paired to allow for distinctive alerting sets. In expanding this parameter in the future, it would be desirable to expand the alert/ri, alert/cw, and andisp/dwa signals together, maintaining the distinctive pattern pairings. This will continue to allow the andisp/dwa signal to have a definition independent of the alerting method, linking it only to the alerting style (pattern).
+
+# 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:
+
+|       |                                       |
+|-------|---------------------------------------|
+| ADSI  | Analogue Display Services Interface   |
+| AOC   | Advice of Charge                      |
+| BCLID | Bulk Calling Line Identification      |
+| CAS   | CPE Alerting Signal                   |
+| CLASS | Custom Local Area Subscriber Services |
+| CPE   | Customer Premises Equipment           |
+| DT-AS | Dual Tone Alerting Signal             |
+| MDMF  | Multiple Data Message Format          |
+| MG    | Media Gateway                         |
+| MGC   | Media Gateway Controller              |
+| MIB   | Management Information Base           |
+| MWI   | Message Waiting Indicator             |
+| RP-AS | Ring Pulse Alerting Signal            |
+
+|      |                            |
+|------|----------------------------|
+| SAS  | Subscriber Alerting Signal |
+| SDMF | Single Data Message Format |
+| SMS  | Short Message Service      |
+| TAS  | Terminal Alerting Signal   |
+
+# 5 Enhanced Alerting Package
+
+|                      |                                                                    |
+|----------------------|--------------------------------------------------------------------|
+| <b>Package name:</b> | Enhanced Alerting Package                                          |
+| <b>Package ID:</b>   | alert (0x003b)                                                     |
+| <b>Description:</b>  | This package defines enhanced alerting signals for analogue lines. |
+| <b>Version:</b>      | 2                                                                  |
+| <b>Extends:</b>      | None                                                               |
+
+## 5.1 Properties
+
+None.
+
+## 5.2 Events
+
+None.
+
+## 5.3 Signals
+
+### 5.3.1 Ring
+
+|                     |                             |
+|---------------------|-----------------------------|
+| <b>Signal name:</b> | Ring                        |
+| <b>Signal ID:</b>   | ri (0x0001)                 |
+| <b>Description:</b> | Applies ringing to the line |
+| <b>Signal type:</b> | TimeOut                     |
+| <b>Duration:</b>    | Provisioned                 |
+
+#### 5.3.1.1 Additional parameters
+
+##### 5.3.1.1.1 Pattern
+
+|                         |                                                                                                                                                                                                                                                         |
+|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Parameter name:</b>  | Pattern                                                                                                                                                                                                                                                 |
+| <b>Parameter ID:</b>    | pattern (0x0001)                                                                                                                                                                                                                                        |
+| <b>Description:</b>     | The pattern is an abstract indication of the distinctive alerting pattern that will be applied to the line. The actual cadence/frequency combination is known by the media gateway. Ring patterns repeat until the signal times out, or is interrupted. |
+| <b>Type:</b>            | Integer                                                                                                                                                                                                                                                 |
+| <b>Optional:</b>        | Yes                                                                                                                                                                                                                                                     |
+| <b>Possible values:</b> | 1-256 (0x0001-0x0100)                                                                                                                                                                                                                                   |
+| <b>Default:</b>         | 1                                                                                                                                                                                                                                                       |
+
+##### 5.3.1.1.2 Tone Direction
+
+|                        |                |
+|------------------------|----------------|
+| <b>Parameter name:</b> | Tone Direction |
+| <b>Parameter ID:</b>   | btd (0x0002)   |
+
+**Description:** The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Note that using the playtone signal to generate this signal will prevent the capability to use the directionality parameter.
+
+**Type:** Enumeration
+
+**Optional:** Yes
+
+**Possible values:** ext (0x0001)  
+int (0x0002)  
+both (0x0003)
+
+**Default:** ext
+
+### 5.3.2 Ringsplash
+
+**Signal name:** Ringsplash
+
+**Signal ID:** rs (0x0002)
+
+**Description:** Applies ringsplash to the line. Ringsplash is a short burst of ringing, typically in the range of 500 milliseconds in duration. The duration is provisioned in the MG.
+
+**Signal type:** Brief
+
+**Duration:** Provisioned
+
+#### 5.3.2.1 Additional parameters
+
+##### 5.3.2.1.1 Tone Direction
+
+**Parameter name:** Tone Direction
+
+**Parameter ID:** btd (0x0001)
+
+**Description:** The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Note that using the playtone signal to generate this signal will prevent the capability to use the directionality parameter.
+
+**Type:** Enumeration
+
+**Optional:** Yes
+
+**Possible values:** ext (0x0001)  
+int (0x0002)  
+both (0x0003)
+
+**Default:** ext
+
+### 5.3.3 Call Waiting
+
+**Signal name:** Call Waiting
+
+**Signal ID:** cw (0x0003)  
+**Description:** Generate call waiting indication. The cw signal definition takes a pattern parameter, to allow generation of distinctive waiting tones.  
+**Signal type:** Brief  
+**Duration:** Varies by pattern
+
+#### 5.3.3.1 Additional parameters
+
+##### 5.3.1.1.1 Pattern
+
+**Parameter name:** Pattern  
+**Parameter ID:** pattern (0x0001)  
+**Description:** The pattern is an abstract indication of the distinctive alerting pattern that will be applied to the line. The actual cadence/frequency combination is known by the media gateway. Call wait patterns do not repeat.  
+**Type:** Integer  
+**Optional:** Yes  
+**Possible values:** 1-256 (0x0001-0x0100)  
+**Default:** 1
+
+##### 5.3.1.1.2 Tone Direction
+
+**Parameter name:** Tone Direction  
+**Parameter ID:** btd (0x0002)  
+**Description:** The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Note that using the playtone signal to generate this signal will prevent the capability to use the directionality parameter.  
+**Type:** Enumeration  
+**Optional:** Yes  
+**Possible values:** ext (0x0001)  
+int (0x0002)  
+both (0x0003)  
+**Default:** ext
+
+## 5.4 Statistics
+
+None.
+
+## 5.5 Procedures
+
+The frequencies and cadences for the signals in this package shall be provisioned. This provisioning may occur through the use of a MIB.
+
+# 6 Analogue Display Signalling Package
+
+|                      |                                                                                                                                                                                |
+|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Package name:</b> | Analogue Display Signalling Package                                                                                                                                            |
+| <b>Package ID:</b>   | andisp (0x003c)                                                                                                                                                                |
+| <b>Description:</b>  | This package defines signalling for data features for analogue lines. These features may include Caller ID, Short Message Service, ADSI, Message Waiting Indicator and others. |
+| <b>Version:</b>      | 2                                                                                                                                                                              |
+| <b>Extends:</b>      | alert (0x003b) version 2                                                                                                                                                       |
+
+## 6.1 Properties
+
+None.
+
+## 6.2 Events
+
+None.
+
+## 6.3 Signals
+
+### 6.3.1 Display with Alerting
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Signal name:</b> | Display with Alerting                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Signal ID:</b>   | dwa (0x0004)                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Description:</b> | Sends the display information to the CPE. This signal indicates that the data must be applied in conjunction with alerting – either power ringing, or call waiting. Therefore, this signal implies alerting, which will be appropriately applied to the CPE by the gateway, based upon the on-hook/off-hook status of the line. The alerting portion of the signal occurs even if the termination is not equipped to receive the data portion. |
+| <b>Signal type:</b> | Brief<br>NOTE – Explicit changes to the signal duration affect the ringing/call waiting portion of the signal, if applicable. The data transmission should be considered Brief.                                                                                                                                                                                                                                                                |
+| <b>Duration:</b>    | Variable depending upon the data transferred                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+#### 6.3.1.1 Additional parameters
+
+##### 6.3.1.1.1 Display Data Block
+
+|                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Parameter name:</b> | Display Data Block                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Parameter ID:</b>   | ddb (0x0001)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Description:</b>    | <p>The Display Data Block contains the message data with any required checksum to be sent to the CPE. Binary encoding is the binary data itself, while text encoding shall carry the data as a big-endian encoded hex string. For example, in North America for basic Caller ID, this would be the SDMF or MDMF construct, including the checksum. The default value is an empty data block which will be silently discarded by the gateway.</p> <p>Once the signal is processed, failure to transmit the display data portion of the signal for any reason SHALL NOT generate an Error</p> |
+
+Descriptor. This includes attempts to transmit to a CPE that is not equipped to handle the data. Application of the alerting portion of the signal should proceed as if there had been no display data transmission request in the first place. This includes errors in the data itself, or a bad checksum.
+
+**Type:** Octet String  
+**Optional:** Yes  
+**Possible values:** See description  
+**Default:** Empty
+
+##### 6.3.1.1.2 Pattern
+
+**Parameter name:** Pattern  
+**Parameter ID:** pattern (0x0002)  
+**Description:** The pattern is an abstract indication of the distinctive alerting pattern that will be applied to the line. If data is to be applied without alerting, the data signal should be used.  
+Failure to apply the patterned signal SHOULD generate an Error Descriptor, as would any failed attempt to apply a signal. Typically, error 513, "Media Gateway unequipped to generate requested Signals" would apply.  
+**Type:** Integer  
+**Optional:** Yes  
+**Possible values:** 1-256 (0x0001-0x0100)  
+**Default:** 1
+
+##### 6.3.1.1.3 Tone Direction
+
+**Parameter name:** Tone Direction  
+**Parameter ID:** btd (0x0003)  
+**Description:** The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Unspecified tone direction shall default to "external". Note that using the playtone signal to generate this signal will prevent the capability to use the directionality parameter.  
+**Type:** Enumeration  
+**Optional:** Yes  
+**Possible values:** ext (0x0001)  
+int (0x0002)  
+both (0x0003)  
+**Default:** ext
+
+### 6.3.2 Generic Data Signalling
+
+**Signal name:** Generic Data Signalling
+
+**Signal ID:** data (0x0005)
+
+**Description:** Sends data not associated with alerting to the CPE. Examples of this would be Analogue Display Services Interface (ADSI), Message Waiting Indicator, Short Message Service, or Advice of Charge. ADSI is used for advanced features such as context-specific softkeys, and in-phone visual data editing.
+
+**Signal type:** Brief
+
+**Duration:** Variable depending on data transfer
+
+#### 6.3.2.1 Additional parameters
+
+##### 6.3.2.1.1 Data Block
+
+**Parameter name:** Data Block
+
+**Parameter ID:** db (0x0001)
+
+**Description:** The Data Block contains the message data with any required checksum to be sent to the CPE. Binary encoding is the binary data itself, while text encoding shall carry the data as a big-endian encoded hex string. The default value is an empty data block which will be acted upon as if there were data (such as playing a TAS tone to the set).
+
+Failure to transmit the data for any reason, excepting Megaco message formatting errors, SHALL NOT generate an Error Descriptor. Call processing should proceed as if there had been no data transmission request in the first place. This includes errors in the data itself, or a bad checksum.
+
+**Type:** Octet String
+
+**Optional:** Yes
+
+**Possible values:** See description
+
+**Default:** Empty
+
+##### 6.3.2.1.2 Terminal Alerting Signal
+
+**Parameter name:** Terminal Alerting Signal
+
+**Parameter ID:** tas (0x0002)
+
+**Description:** The TAS is the method to alert the set that data is forthcoming. In the offhook signalling case, the TAS parameter shall specify either the DT-AS (dt) or no TAS (nt). Use of the rp or lr values in the offhook case shall be treated as if dt were signalled.
+
+**Type:** Enumeration
+
+**Optional:** Yes
+
+**Possible values:**  
+dt (0x0001) Dual Tone Alerting Signal (DT-AS)  
+rp (0x0002) Ring Pulse Alerting Signal (RP-AS)  
+lr (0x0003) Line Reversal followed by DT-AS  
+nt (0x0004) No TAS
+
+**Default:** Provisioned
+
+##### 6.3.2.1.3 Tone Direction
+
+|                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Parameter name:</b>  | Tone Direction                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Parameter ID:</b>    | btd (0x0003)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Description:</b>     | The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Unspecified tone direction shall default to "external". Note that using the playtone signal to generate this signal will prevent the capability to use the directionality parameter. |
+| <b>Type:</b>            | Enumeration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Optional:</b>        | Yes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Possible values:</b> | ext (0x0001)<br>int (0x0002)<br>both (0x0003)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Default:</b>         | ext                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+### 6.3.3 Error Tone
+
+|                     |                                                                                                                                                                                             |
+|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Signal name:</b> | Error Tone                                                                                                                                                                                  |
+| <b>Signal ID:</b>   | err (0x0006)                                                                                                                                                                                |
+| <b>Description:</b> | Provides for a tone to be played to the subscriber indicating that an error has occurred (for example, bad input). The physical characteristic of error tone is provisioned in the gateway. |
+| <b>Signal type:</b> | Brief                                                                                                                                                                                       |
+| <b>Duration:</b>    | Provisioned                                                                                                                                                                                 |
+
+#### 6.3.3.1 Additional parameters
+
+##### 6.3.3.1.1 Tone Direction
+
+|                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Parameter name:</b>  | Tone Direction                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Parameter ID:</b>    | btd (0x0001)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Description:</b>     | The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Unspecified tone direction shall default to "external". Note that using the playtone signal to generate this signal will prevent the capability to use the directionality parameter. |
+| <b>Type:</b>            | Enumeration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Optional:</b>        | Yes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Possible values:</b> | ext (0x0001)<br>int (0x0002)<br>both (0x0003)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+**Default:** ext
+
+## 6.4 Statistics
+
+None.
+
+## 6.5 Procedures
+
+The data block parameter of the andisp/dwa and andisp/data signals always includes the checksum, if the data format specifies one. However, the signals do not include other data link parameters such as the Channel Seizure or Mark indications. These other parameters are generated by the MG.
+
+The following examples show how to build a Signals descriptor to deliver Caller ID to a CPE. The andisp/dwa signal is designed to stand alone, and be independent of on-hook/off-hook status.
+
+To apply ringing (via the alert package) for a normal call, the following signals descriptor is used:
+
+```
+Signals{alert/ri{pattern=1}}
+```
+
+To apply standard ringing and signal the Caller ID information, the following signals descriptor is used:
+
+```
+Signals{andisp/dwa{ddb=802001083035313831363135020A393139353535303030300708  
+4A6F686E20446F65D8,pattern=1}}
+```
+
+In this example, the data block is North American MDMF, or ETSI Call Setup Caller ID signalling, indicating a call at 4:15 PM, May 18 from John Doe at (919) 555-0000. The checksum is included (D5). For encoding information, see [b-Telcordia GR-30-CORE] or [b-ETSI EN 300 659-1], [b-ETSI EN 300 659-2] and [b-ETSI EN 300 659-3].
+
+This signalling implies standard ringing, and any other signalling necessary to deliver the Caller ID to the set between the first and second ring.
+
+For the UK, Caller ID info is delivered by ringsplashing the set, sending the DWA data, and then applying normal ringing. The signal this descriptor used is the following:
+
+```
+Signals{andisp/dwa{ddb=802001083035313831363135020A393139353535303030300708  
+4A6F686E20446F65D8,pattern=1}}
+```
+
+NOTE – This is the same as the previous example, since TAS should be provisioned for the gateway's location.
+
+Call Waiting ID follows the same principles. For normal call waiting, the tone is requested as follows:
+
+```
+Signals{alert/cw{pattern=1}}
+```
+
+To perform Call Waiting ID (off-hook signalling), the descriptor is identical to the on-hook case:
+
+```
+Signals{andisp/dwa{ddb=802001083035313831363135020A393139353535303030300708  
+4A6F686E20446F65D8,pattern=1}}
+```
+
+This signalling implies both application of call waiting tone, and any other signalling necessary to perform the Caller ID function. For North America and ETSI countries, it requests that the gateway apply call wait tone, then apply the CAS/DT-AS, and send down the Caller ID info after receipt of the ACK digit. If the MGC wants notification of the ACK digit, it should be requested in the Events descriptor. Any location-specific signalling requirements in the set-up of the DWA delivery are implied within the signal.
+
+Bulk Calling Line ID is handled in the same way as Caller ID, except the Generic Data signal is used. Transmission of the Caller ID data proceeds as normal for on-hook transmission without ringing. Similar procedures are used for delivery of Advice of Charge data, Short Message Service data, Message Waiting Indicator data, etc.
+
+For ADSI, there are constraints similar to the off-hook data with alerting around ACK digits and softkey/digit responses. Any responses that the MGC wishes to be made aware of should be requested in the Events descriptor. Digitmaps may be used for this application.
+
+There is a possible race condition where an MGC might apply the dwa signal intending power ringing and data to be applied, but before the signal reaches the MG, the termination undergoes a transition to offhook. The result is that the signal would apply a call waiting tone in the interim, while the MG reports the offhook and the MGC responds with updated Events and Signals Descriptors. It may be desirable to prevent any possibility of this race condition occurring. To achieve this, implementations may embed the andisp/dwa signal on the onhook event with its strict parameter set to "state". This will enforce that the dwa signal is only applied if the termination is still onhook when the command arrives at the MG.
+
+Binary encoding SHALL carry the binary data. Text encoding SHALL carry the data as a hex string encoded as big-endian hex data.
+
+# Bibliography
+
+- [b-Telcordia GR-30-CORE] Telcordia GR-30-CORE, Issue 2 (1998), *LSSGR: Voice Band Data Transmission*.
+- [b-ETSI EN 300 659-1] ETSI EN 300 659-1, V1.3.1 (2001), *Access and Terminals (AT); Analogue access to the Public Switched Telephone Network (PSTN); Subscriber line protocol over the local loop for display (and related) services; Part 1: On-hook data transmission*.
+- [b-ETSI EN 300 659-2] ETSI EN 300 659-2, V1.3.1 (2001), *Access and Terminals (AT); Analogue access to the Public Switched Telephone Network (PSTN); Subscriber line protocol over the local loop for display (and related) services; Part 2: Off-hook data transmission*.
+- [b-ETSI EN 300 659-3] ETSI EN 300 659-3, V1.3.1 (2001), *Access and Terminals (AT); Analogue access to the Public Switched Telephone Network (PSTN); Subscriber line protocol over the local loop for display (and related) services; Part 3: Data link message and parameter codings*.
+
+
+
+
+
+## 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.25-201303-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/H/T-REC-H.248.25-201303-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..46a86edc631d181b677b5e91db3a83049d59b77d
--- /dev/null
+++ b/marked/H/T-REC-H.248.25-201303-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e94933a67781af88e0b516dd66db47ff4ddb671b720aa1fa1c00e7b6a695d91b
+size 53109
diff --git a/marked/H/T-REC-H.248.25-201303-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg b/marked/H/T-REC-H.248.25-201303-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..40da3d6b88aa798cd9a320deb2e30c522d14d93c
--- /dev/null
+++ b/marked/H/T-REC-H.248.25-201303-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c523f4c08f9d57699ec2700f565d11e9e62651ca12d4cc606c21711de1d4de26
+size 111772
diff --git a/marked/H/T-REC-H.248.25-201303-I_PDF-E/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/marked/H/T-REC-H.248.25-201303-I_PDF-E/744acfe8d4e31bcf03f95714c2f6e567_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1908bc160d939d19431363e77b160167cabefe54
--- /dev/null
+++ b/marked/H/T-REC-H.248.25-201303-I_PDF-E/744acfe8d4e31bcf03f95714c2f6e567_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da177bb78ad702e5899c5a84069d4e45667b84bf83651524157ef566b3dd26e9
+size 65974
diff --git a/marked/H/T-REC-H.248.25-201303-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg b/marked/H/T-REC-H.248.25-201303-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7ebb3e33c394048535d4549837f66fc943c90a63
--- /dev/null
+++ b/marked/H/T-REC-H.248.25-201303-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e64530c9fcf04ffa3deffb998fb90ef1221295d86139ebb61347bbf72569017
+size 85279
diff --git a/marked/H/T-REC-H.248.25-201303-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg b/marked/H/T-REC-H.248.25-201303-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f5b62f5bd57f8b31f62f1d8ce351091bbab536a6
--- /dev/null
+++ b/marked/H/T-REC-H.248.25-201303-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:524e5e49cb7ef5add436687d8007f9c5fdc49ce65d31006faa5f8d5539cb3234
+size 143893
diff --git a/marked/H/T-REC-H.248.25-201303-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg b/marked/H/T-REC-H.248.25-201303-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..626864ee9a0b1a085699894c17d29eee45633838
--- /dev/null
+++ b/marked/H/T-REC-H.248.25-201303-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a7e722de46d4ed72a344f156fe4945477051cf14df3f5adf3bdc992d3b1ba1a
+size 112486
diff --git a/marked/H/T-REC-H.248.25-201303-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg b/marked/H/T-REC-H.248.25-201303-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f7e6e53a7435a6a5acad2e4ef4e0868f93693c53
--- /dev/null
+++ b/marked/H/T-REC-H.248.25-201303-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1a08d4d5f8fd2aca465c73fdff31bc96257d215ed2964a106d0d98c1c82e8a83
+size 102475
diff --git a/marked/H/T-REC-H.248.25-201303-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/H/T-REC-H.248.25-201303-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..843c023dc36cf8c7cfd2cf989cd6dd6a7f83d281
--- /dev/null
+++ b/marked/H/T-REC-H.248.25-201303-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:00144315decc522a7944c6058ebb91a8895aa5c38d047e20d67c9df94ed0200e
+size 44062
diff --git a/marked/H/T-REC-H.248.25-201303-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg b/marked/H/T-REC-H.248.25-201303-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7cb4d5d11511a2e361553824d508fde008fab400
--- /dev/null
+++ b/marked/H/T-REC-H.248.25-201303-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:abbadb5a4216778c87e818254a2116b3161c9b23f839b90107c90e8f05b9e8c3
+size 3538
diff --git a/marked/H/T-REC-H.248.27-200307-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.248.27-200307-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30
--- /dev/null
+++ b/marked/H/T-REC-H.248.27-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.27-200307-I_PDF-E/raw.md b/marked/H/T-REC-H.248.27-200307-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..083e606a8d71ca923ad00e35596ccea4cc7d05c0
--- /dev/null
+++ b/marked/H/T-REC-H.248.27-200307-I_PDF-E/raw.md
@@ -0,0 +1,724 @@
+
+
+![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.27**
+
+(07/2003)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS  
+Infrastructure of audiovisual services – Communication  
+procedures
+
+---
+
+**Gateway control protocol: Supplemental tones  
+packages**
+
+ITU-T Recommendation H.248.27
+
+---
+
+# 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        |
+| <b>Communication procedures</b>                                               | <b>H.240–H.259</b> |
+| 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.27**
+
+## **Gateway control protocol: Supplemental tones packages**
+
+## **Summary**
+
+This Recommendation defines three packages that provide conferencing, diagnostic and carrier services tones capabilities for H.248.
+
+###### **Source**
+
+ITU-T Recommendation H.248.27 was approved by ITU-T Study Group 16 (2001-2004) under the 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    |
+| 3 Definitions .....                           | 1    |
+| 4 Abbreviations.....                          | 1    |
+| 5 Conferencing tones generation package ..... | 1    |
+| 5.1 Properties.....                           | 1    |
+| 5.2 Events .....                              | 1    |
+| 5.3 Signals .....                             | 2    |
+| 5.4 Statistics.....                           | 5    |
+| 5.5 Procedures .....                          | 5    |
+| 6 Diagnostic tones generation package.....    | 5    |
+| 6.1 Properties.....                           | 5    |
+| 6.2 Events .....                              | 5    |
+| 6.3 Signals .....                             | 5    |
+| 6.4 Statistics.....                           | 9    |
+| 6.5 Procedures .....                          | 9    |
+| 7 Carrier tones generation package.....       | 9    |
+| 7.1 Properties.....                           | 9    |
+| 7.2 Events .....                              | 9    |
+| 7.3 Signals .....                             | 10   |
+| 7.4 Statistics.....                           | 12   |
+| 7.5 Procedures .....                          | 12   |
+
+
+
+## Gateway control protocol: Supplemental tones packages
+
+## 1 Scope
+
+This Recommendation defines three packages that provide conferencing, diagnostic and carrier services tones 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; 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*.
+
+## 3 Definitions
+
+None.
+
+## 4 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+MG Media Gateway
+
+MGC Media Gateway Controller
+
+## 5 Conferencing tones generation package
+
+PackageID: confn (0x0038)
+
+Version: 1
+
+Extends: tonegen version 1
+
+This package defines conferencing signals that indicate to the participants of a conference when:
+
+- a caller has entered or leaves a conference;
+- a conference is locked or unlocked;
+- a time limit is about to expire.
+
+This package uses the term "tone" which may be a tone for an audio stream or may be a still or moving image for a video stream, among other possible options.
+
+### 5.1 Properties
+
+None.
+
+### 5.2 Events
+
+None.
+
+### 5.3 Signals
+
+#### 5.3.1 Conference entrance tone
+
+SignalID: enter (0x0061)
+
+Description:
+
+Generate conference entrance tone, which indicates that a new caller has joined the conference. The physical characteristics of the conference entrance tone are available in the gateway.
+
+Signal Type: Brief
+
+Duration: Provisioned
+
+Additional parameters:
+
+*Tone Direction*
+
+ParameterID: btd (0x0001)
+
+Type: Enumeration
+
+Possible values: External ext (0x0001),
+
+Internal int (0x0002),
+
+Both both (0x0003)
+
+Description:
+
+The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Unspecified tone direction shall default to "external". Note that using the playtone signal in package tonegen to generate this signal will prevent the capability to use the directionality parameter.
+
+The other signals in this package are specified in exactly the same way. A table with all signal names and signal IDs is included. Note that each signal is defined as both a signal and a toneid, thus extending the basic tone generation package.
+
+| Signal name             | Signal ID/tone id |
+|-------------------------|-------------------|
+| Conf. Entrance Tone     | enter (0x0061)    |
+| Conf. Exit Tone         | exit (0x0062)     |
+| Conf. Lock Tone         | lock (0x0063)     |
+| Conf. Unlock Tone       | unlock (0x0064)   |
+| Time Limit Warning Tone | timelim (0x0065)  |
+
+#### 5.3.2 Conference exit tone
+
+SignalID: exit (0x0062)
+
+Description:
+
+Generate conference exit tone, which indicates that a conferee has left the conference. The physical characteristics of the conference exit tone are available in the gateway.
+
+Signal Type: Brief
+
+Duration: Provisioned
+
+Additional parameters:
+
+##### *Tone Direction*
+
+|                  |              |               |
+|------------------|--------------|---------------|
+| ParameterID:     | btd (0x0001) |               |
+| Type:            | Enumeration  |               |
+| Possible values: | External     | ext (0x0001), |
+|                  | Internal     | int (0x0002), |
+|                  | Both         | both (0x0003) |
+
+Description:
+
+The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Unspecified tone direction shall default to "external". Note that using the playtone signal in package tonegen to generate this signal will prevent the capability to use the directionality parameter.
+
+#### 5.3.3 Conference lock tone
+
+SignalID: lock (0x0063)
+
+Description:
+
+Generate conference lock tone, which indicates that the controller has blocked new callers from joining the conference. The physical characteristics of the conference lock tone are available in the gateway.
+
+Signal Type: Brief
+
+Duration: Provisioned
+
+Additional parameters:
+
+##### *Tone Direction*
+
+|                  |              |               |
+|------------------|--------------|---------------|
+| ParameterID:     | btd (0x0001) |               |
+| Type:            | Enumeration  |               |
+| Possible values: | External     | ext (0x0001), |
+|                  | Internal     | int (0x0002), |
+|                  | Both         | both (0x0003) |
+
+Description:
+
+The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Unspecified tone direction shall default to "external". Note that using the playtone signal in package tonegen to generate this signal will prevent the capability to use the directionality parameter.
+
+#### 5.3.4 Conference unlock tone
+
+SignalID: unlock (0x0064)
+
+Description:
+
+Generate conference unlock tone, which indicates that the controller has allowed new callers to join the conference. The physical characteristics of conference unlock tone is available in the gateway.
+
+Signal Type: Brief
+
+Duration: Provisioned
+
+Additional parameters:
+
+*Tone Direction*
+
+ParameterID: btd (0x0001)
+
+Type: Enumeration
+
+Possible values: External ext (0x0001),
+
+Internal int (0x0002),
+
+Both both (0x0003)
+
+Description:
+
+The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Unspecified tone direction shall default to "external". Note that using the playtone signal in package tonegen to generate this signal will prevent the capability to use the directionality parameter.
+
+#### 5.3.5 Time limit warning tone
+
+SignalID: timelim (0x0065)
+
+Description:
+
+Generates a time limit warning tone, which indicates that there are only a few minutes remaining on the provisioned conference bridge. The physical characteristics of the time limit warning tone are available in the gateway.
+
+Signal Type: Brief
+
+Duration: Provisioned
+
+Additional parameters:
+
+##### *Tone Direction*
+
+|                  |                                                                        |
+|------------------|------------------------------------------------------------------------|
+| ParameterID:     | btd (0x0001)                                                           |
+| Type:            | Enumeration                                                            |
+| Possible values: | External ext (0x0001),<br>Internal int (0x0002),<br>Both both (0x0003) |
+
+##### Description:
+
+The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Unspecified tone direction shall default to "external". Note that using the playtone signal in package tonegen to generate this signal will prevent the capability to use the directionality parameter.
+
+### 5.4 Statistics
+
+None.
+
+### 5.5 Procedures
+
+None.
+
+## 6 Diagnostic tones generation package
+
+|            |                   |
+|------------|-------------------|
+| PackageID: | test (0x0039)     |
+| Version:   | 1                 |
+| Extends:   | tonegen version 1 |
+
+This package defines diagnostic signals for use by telephony providers. The definitions and usage of these tones are dependent upon the test application in use. These signals are provided as an aid to performing diagnostic tests and the use and characteristics of the signals may vary from region to region and implementation to implementation.
+
+### 6.1 Properties
+
+None.
+
+### 6.2 Events
+
+None.
+
+### 6.3 Signals
+
+#### 6.3.1 Low tone
+
+|           |              |
+|-----------|--------------|
+| SignalID: | low (0x0066) |
+|-----------|--------------|
+
+##### Description:
+
+Generates a low tone. The physical characteristics of low tone are available in the gateway.
+
+Signal Type: Brief
+
+Duration: Provisioned
+
+Additional parameters:
+
+##### *Tone Direction*
+
+ParameterID: btd (0x0001)  
+Type: Enumeration  
+Possible values: External ext (0x0001),  
+Internal int (0x0002),  
+Both both (0x0003)
+
+Description:
+
+The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Unspecified tone direction shall default to "external". Note that using the playtone signal in package tonegen to generate this signal will prevent the capability to use the directionality parameter.
+
+The other signals in this package are specified in exactly the same way. A table with all signal names and signal IDs is included. Note that each signal is defined as both a signal and a toneid, thus extending the basic tone generation package.
+
+| Signal name           | Signal ID/tone id |
+|-----------------------|-------------------|
+| Low Tone              | low (0x0066)      |
+| High Tone             | high (0x0067)     |
+| Loud Tone             | loud (0x0068)     |
+| Faint Tone            | faint (0x0069)    |
+| Slow Interrupted Tone | slow (0x006a)     |
+| Fast Interrupted Tone | fast (0x006b)     |
+
+#### 6.3.2 High one
+
+SignalID: high (0x0067)
+
+Description:
+
+Generates a high tone. The physical characteristics of high tone are available in the gateway.
+
+Signal Type: Brief
+
+Duration: Provisioned
+
+Additional parameters:
+
+##### *Tone Direction*
+
+ParameterID: btd (0x0001)  
+Type: Enumeration
+
+|                  |          |               |
+|------------------|----------|---------------|
+| Possible values: | External | ext (0x0001), |
+|                  | Internal | int (0x0002), |
+|                  | Both     | both (0x0003) |
+
+Description:
+
+The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Unspecified tone direction shall default to "external". Note that using the playtone signal in package tonegen to generate this signal will prevent the capability to use the directionality parameter.
+
+#### 6.3.3 Loud tone
+
+SignalID: loud (0x0068)
+
+Description:
+
+Generates a loud tone. The physical characteristics of loud tone are available in the gateway.
+
+Signal Type: Brief
+
+Duration: Provisioned
+
+Additional parameters:
+
+*Tone Direction*
+
+|                  |              |               |
+|------------------|--------------|---------------|
+| ParameterID:     | btd (0x0001) |               |
+| Type:            | Enumeration  |               |
+| Possible values: | External     | ext (0x0001), |
+|                  | Internal     | int (0x0002), |
+|                  | Both         | both (0x0003) |
+
+Description:
+
+The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Unspecified tone direction shall default to "external". Note that using the playtone signal in package tonegen to generate this signal will prevent the capability to use the directionality parameter.
+
+#### 6.3.4 Faint tone
+
+SignalID: faint (0x0069)
+
+Description:
+
+Generates a faint tone. The physical characteristics of faint tone are available in the gateway.
+
+Signal Type: Brief
+
+Duration: Provisioned
+
+Additional parameters:
+
+##### *Tone Direction*
+
+|                  |                                                                        |
+|------------------|------------------------------------------------------------------------|
+| ParameterID:     | btd (0x0001)                                                           |
+| Type:            | Enumeration                                                            |
+| Possible values: | External ext (0x0001),<br>Internal int (0x0002),<br>Both both (0x0003) |
+
+Description:
+
+The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Unspecified tone direction shall default to "external". Note that using the playtone signal in package tonegen to generate this signal will prevent the capability to use the directionality parameter.
+
+#### 6.3.5 Slow interrupted tone
+
+SignalID: slow (0x006a)
+
+Description:
+
+Generates a slow interrupted tone. The physical characteristics of slow interrupted tone are available in the gateway.
+
+Signal Type: Brief
+
+Duration: Provisioned
+
+Additional parameters:
+
+##### *Tone Direction*
+
+|                  |                                                                        |
+|------------------|------------------------------------------------------------------------|
+| ParameterID:     | btd (0x0001)                                                           |
+| Type:            | Enumeration                                                            |
+| Possible values: | External ext (0x0001),<br>Internal int (0x0002),<br>Both both (0x0003) |
+
+Description:
+
+The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Unspecified tone direction shall default to "external". Note that using the playtone signal in package tonegen to generate this signal will prevent the capability to use the directionality parameter.
+
+#### 6.3.6 Fast interrupted tone
+
+SignalID: fast (0x006b)
+
+Description:
+
+Generates a fast interrupted tone. The physical characteristics of fast interrupted tone are available in the gateway.
+
+Signal Type: Brief
+
+Duration: Provisioned
+
+Additional parameters:
+
+*Tone Direction*
+
+ParameterID: btd (0x0001)
+
+Type: Enumeration
+
+Possible values: External ext (0x0001),
+
+Internal int (0x0002),
+
+Both both (0x0003)
+
+Description:
+
+The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Unspecified tone direction shall default to "external". Note that using the playtone signal in package tonegen to generate this signal will prevent the capability to use the directionality parameter.
+
+### 6.4 Statistics
+
+None.
+
+### 6.5 Procedures
+
+None.
+
+## 7 Carrier tones generation package
+
+PackageID: carr (0x003a)
+
+Version: 1
+
+Extends: tonegen version 1
+
+This package defines signals for use by carrier services.
+
+### 7.1 Properties
+
+None.
+
+### 7.2 Events
+
+None.
+
+### 7.3 Signals
+
+#### 7.3.1 Carrier dial tone
+
+SignalID: cdt (0x006c)
+
+Description:
+
+Generates a carrier dial tone, indicating that a carrier other than the default is providing service for the call. The physical characteristics of carrier dial tone are available in the gateway.
+
+Signal Type: Brief
+
+Duration: Provisioned
+
+Additional parameters:
+
+##### *Tone Direction*
+
+ParameterID: btd (0x0001)
+
+Type: Enumeration
+
+Possible values: External ext (0x0001),
+
+Internal int (0x0002),
+
+Both both (0x0003)
+
+Description:
+
+The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Unspecified tone direction shall default to "external". Note that using the playtone signal in package tonegen to generate this signal will prevent the capability to use the directionality parameter.
+
+The other signals in this package are specified in exactly the same way. A table with all signal names and signal IDs is included. Note that each signal is defined as both a signal and a toneid, thus extending the basic tone generation package.
+
+| Signal name                  | Signal ID/tone id |
+|------------------------------|-------------------|
+| Carrier Dial Tone            | cdt (0x006c)      |
+| Carrier Answer Tone          | ans (0x006d)      |
+| Carrier Charging Tone        | chg (0x006e)      |
+| Long Distance Indicator Tone | ldi (0x006f)      |
+
+#### 7.3.2 Carrier answer tone
+
+SignalID: ans (0x006d)
+
+Description:
+
+Generates a carrier answer tone, also known as tone burst on answer, indicating that a carrier other than the default is providing service for the call. The physical characteristics of carrier answer tone are available in the gateway.
+
+Signal Type: Brief
+
+Duration: Provisioned
+
+Additional parameters:
+
+##### *Tone Direction*
+
+|                  |                                                                        |
+|------------------|------------------------------------------------------------------------|
+| ParameterID:     | btd (0x0001)                                                           |
+| Type:            | Enumeration                                                            |
+| Possible values: | External ext (0x0001),<br>Internal int (0x0002),<br>Both both (0x0003) |
+
+Description:
+
+The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Unspecified tone direction shall default to "external". Note that using the playtone signal in package tonegen to generate this signal will prevent the capability to use the directionality parameter.
+
+#### 7.3.3 Carrier charging tone
+
+SignalID: chg (0x006e)
+
+Description:
+
+Generates a carrier charging tone, also known as subscriber trunk dialling tone, indicating that a subscriber has dialled a trunk call, and charging is about to commence. The physical characteristics of carrier charging tone are available in the gateway.
+
+Signal Type: Brief
+
+Duration: Provisioned
+
+Additional parameters:
+
+##### *Tone Direction*
+
+|                  |                                                                        |
+|------------------|------------------------------------------------------------------------|
+| ParameterID:     | btd (0x0001)                                                           |
+| Type:            | Enumeration                                                            |
+| Possible values: | External ext (0x0001),<br>Internal int (0x0002),<br>Both both (0x0003) |
+
+Description:
+
+The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Unspecified tone direction shall default to "external". Note that using the playtone signal in package tonegen to generate this signal will prevent the capability to use the directionality parameter.
+
+#### 7.3.4 Long distance indicator tone
+
+SignalID: ldi (0x006f)
+
+Description:
+
+Generates a long distance indicator tone, indicating that the call is a long-distance connection. The physical characteristics of long distance indicator tone are available in the gateway.
+
+Signal Type: Brief
+
+Duration: Provisioned
+
+Additional parameters:
+
+*Tone Direction*
+
+ParameterID: btd (0x0001)
+
+Type: Enumeration
+
+Possible values: External ext (0x0001),
+
+Internal int (0x0002),
+
+Both both (0x0003)
+
+Description:
+
+The tone direction indicates in which direction the signal shall proceed with respect to the centre of the context. "Internal" denotes that the signal shall proceed toward the centre of the context from the termination, while "external" denotes that the signal shall proceed toward the edge of the context. "Both" indicates that the signal shall proceed in both directions. Unspecified tone direction shall default to "external". Note that using the playtone signal in package tonegen to generate this signal will prevent the capability to use the directionality parameter.
+
+### 7.4 Statistics
+
+None.
+
+### 7.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                                                                   |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                      |
+| 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.28-200701-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.28-200701-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c
--- /dev/null
+++ b/marked/H/T-REC-H.248.28-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.248.28-200701-I_PDF-E/raw.md b/marked/H/T-REC-H.248.28-200701-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..ccd56b8380d974b2e41807eba6a0f0c5573872e9
--- /dev/null
+++ b/marked/H/T-REC-H.248.28-200701-I_PDF-E/raw.md
@@ -0,0 +1,619 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.28**
+
+(01/2007)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+---
+
+**Gateway control protocol: International  
+CAS packages**
+
+ITU-T Recommendation H.248.28
+
+# 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        |
+| <b>Communication procedures</b>                                               | <b>H.240–H.259</b> |
+| 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: International CAS packages**
+
+## **Summary**
+
+The international CAS package (icas) provides an extension to the basic CAS packages, defining additional line signals and events required for international signalling protocols.
+
+For some international protocols, such as some variants of the R2 signalling system, it would typically be necessary to implement the bcas, icas and casblk packages to fully support the interface. In addition, register signalling will require support of either the bcasaddr package for non-compelled signalling, or a package to perform compelled signalling.
+
+This version of this Recommendation adds new read-only properties containing the current CAS state of the termination, to allow the MGC to resynchronize itself in the event that it loses track of this state.
+
+## **Source**
+
+ITU-T Recommendation H.248.28 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....             | 2    |
+| 5 International CAS package..... | 2    |
+| 5.1 Properties.....              | 2    |
+| 5.2 Events .....                 | 3    |
+| 5.3 Signals .....                | 6    |
+| 5.4 Statistics.....              | 8    |
+| 5.5 Procedures .....             | 8    |
+| 6 CAS blocking package .....     | 8    |
+| 6.1 Properties.....              | 9    |
+| 6.2 Events .....                 | 9    |
+| 6.3 Signals .....                | 10   |
+| 6.4 Statistics.....              | 10   |
+| 6.5 Procedures .....             | 10   |
+
+
+
+# Gateway control protocol: International CAS packages
+
+# 1 Scope
+
+The icas package presented in this Recommendation is an extension of the bcas package (as per definition of package extensions in [ITU-T H.248.1]). Any termination supporting this package must also support the bcas package.
+
+Only signals and events related to generic international CAS signalling operation, both for automatic or semi-automatic working, have been considered for inclusion in the icas package. Some international signalling systems may require new supervisory (line) and call set-up control (register) signals to introduce features such as re-answering, trunk offering, re-ring, operator break-in, etc. As there is no single standard mechanism to implement such features (they vary from country to country), they have not been considered in this package. If these are required, it is expected they would be implemented by defining additional signals and events in new packages that either extend the bcas package or this icas package.
+
+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 shall be provisioned with the actual signalling frequencies for inter-register signalling (for example 2-out-of-n in-band multi-frequency 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 inter-register compelling actions shall be provisioned in the MG. For example in R2 the SF, E&M (for analogue) and "abcd" bits (for digital) line signalling parameters generated at the physical layer, along with their logical significance, are also assumed to be provisioned at the MG.
+
+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] 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*.
+
+# 3 Definitions
+
+None.
+
+# 4 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+|     |                               |
+|-----|-------------------------------|
+| CAS | Channel Associated Signalling |
+| E&M | Ear and Mouth                 |
+| MG  | Media Gateway                 |
+| MGC | Media Gateway Controller      |
+| PDN | Packet Data Network           |
+| R2  | Signalling System R2          |
+| SF  | Single Frequency              |
+
+# 5 International CAS package
+
+Package name: International CAS package
+
+PackageID: icas (0x007b)
+
+Description: This package provides event and signal handling for terminations that support international CAS signalling.
+
+Version: 2
+
+Extends: bcas version 2
+
+## 5.1 Properties
+
+### 5.1.1 Trunk direction
+
+Property name: Trunk direction
+
+PropertyID: trdir (0x0001)
+
+Description: Specifies whether the icas termination is an incoming, outgoing or both way trunk circuit.
+
+Type: Enumeration
+
+|                  |             |            |
+|------------------|-------------|------------|
+| Possible values: | IC (0x0001) | Incoming.  |
+|                  | OG (0x0002) | Outgoing.  |
+|                  | BW (0x0003) | Both ways. |
+
+Default: Provisioned
+
+Defined in: TerminationState descriptor
+
+Characteristics: Read only
+
+### 5.1.2 CAS near-end line state
+
+Property name: CAS near-end line state
+
+PropertyID: 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.            |
+| ClearFwd (0x05)  | The CAS termination near-end is in the clear forward state.     |
+| ClearBack (0x06) | The CAS termination near-end is in the clear back state.        |
+| RelGrd (0x07)    | The CAS termination near-end is in the release guard state.     |
+
+Default: The last applied line signal. If no line signal has been applied by the MGC, idle.
+
+Defined In: TerminationState descriptor
+
+Characteristics: Read only
+
+### 5.1.3 Far-end line state
+
+Property name: CAS far-end line state
+
+PropertyID: 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.            |
+| ClearFwd (0x05)  | The CAS termination far-end is in the clear forward state.     |
+| ClearBack (0x06) | The CAS termination far-end is in the clear back state.        |
+| RelGrd (0x07)    | The CAS termination far-end is in the release guard state.     |
+
+Default: The last detected line event. If no line event has been detected by the MGC, idle.
+
+Defined in: TerminationState descriptor
+
+Characteristics: Read only
+
+## 5.2 Events
+
+### 5.2.1 Subscriber line status
+
+Event name: Subscriber line status
+
+EventID: sls (0x0006)
+
+Description: Reports the line status of the called subscriber.
+
+EventsDescriptor parameters: None
+
+ObservedEventsDescriptor parameters:
+
+#### *Subscriber line condition*
+
+|                  |                                           |                               |
+|------------------|-------------------------------------------|-------------------------------|
+| Parameter name:  | Subscriber line condition                 |                               |
+| ParameterID:     | lst (0x0001)                              |                               |
+| Description:     | Line conditions of the called subscriber. |                               |
+| Type:            | Enumeration                               |                               |
+| Optional:        | No                                        |                               |
+| Possible values: | SLB (0x0001)                              | Subscriber line busy.         |
+|                  | SLFC (0x0002)                             | Subscriber line free, charge. |
+| Default:         | None                                      |                               |
+
+### 5.2.2 Clear forward
+
+Event name: Clear forward
+
+EventID: cf (0x0007)
+
+Description: This event applies to an incoming interface and is reported when a "clear" line 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 condition against which the signal is verified is provisioned in the MG. The parameter "clear guard timing" can optionally be included.
+
+EventsDescriptor parameters:
+
+#### *Clear guard timing*
+
+|                  |                                                                                                                                                                                                                                                                                                                                        |  |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|
+| Parameter name:  | Clear guard timing                                                                                                                                                                                                                                                                                                                     |  |
+| ParameterID:     | clgdt (0x0001)                                                                                                                                                                                                                                                                                                                         |  |
+| Description:     | Specifies whether the MG shall start a clear guard timer for the receipt of the clear forward signal. If the clear guard timer expires prior to the detection of clear forward signal and the CAS failure event is active, the MG shall report a CAS failure event with a "cfto" error code. The timer value is provisioned on the MG. |  |
+| Type:            | Boolean                                                                                                                                                                                                                                                                                                                                |  |
+| Optional:        | Yes                                                                                                                                                                                                                                                                                                                                    |  |
+| Possible values: | On when the clear guard timing is requested.                                                                                                                                                                                                                                                                                           |  |
+|                  | Off when the clear guard timing is turned off.                                                                                                                                                                                                                                                                                         |  |
+| Default:         | Off                                                                                                                                                                                                                                                                                                                                    |  |
+
+ObservedEventsDescriptor parameters: None
+
+### 5.2.3 Clear back
+
+Event name: Clear back
+
+EventID: cb (0x0008)
+
+Description: This event applies to an outgoing interface and is reported when a "clear back" line 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 condition against which the signal is verified is provisioned in the MG. The parameter "clear guard timing" can optionally be included.
+
+EventsDescriptor parameters:
+
+#### *Clear guard timing*
+
+Parameter name: Clear guard timing  
+ParameterID: clgdt (0x0001)  
+Description: Specifies whether the MG shall start a clear guard timer for the receipt of the "clear back" signal. If the clear guard timer expires prior to the detection of clear back signal and the CAS failure event is active, the MG shall report a CAS failure event with a "cbto" error code. The timer value is provisioned on the MG. If the clgdt parameter is not provided, the MG does not perform timing by default.  
+Type: Boolean  
+Optional: Yes  
+Possible values: On when the clear guard timing is requested.  
+Off when the clear guard timing is turned off.  
+Default: Off
+
+ObservedEventsDescriptor parameters: None
+
+### 5.2.4 CAS failure
+
+Event name: 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.
+
+EventsDescriptor parameters: None
+
+ObservedEventsDescriptor parameters:
+
+#### *Error code*
+
+Parameter name: Error code  
+ParameterID: ec (0x0001)  
+Description: Describes the CAS failure reason.  
+Type: Enumeration  
+Optional: No
+
+Possible values:
+
+|               |                                                                                                      |
+|---------------|------------------------------------------------------------------------------------------------------|
+| CFTO (0x0006) | Clear forward time out.                                                                              |
+| CBTO (0x0007) | Clear back time out.                                                                                 |
+| CNG (0x0008)  | Congestion: Encountered network congestion.                                                          |
+| DISC (0x0009) | Information signalled by the MGC is inappropriate at the compelling stage at MG and hence discarded. |
+
+Default: None
+
+### 5.2.5 Release guard
+
+Event name: Release guard
+
+EventID: rlg (0x0009)
+
+Description: This event applies to an incoming interface and is reported when a "release guard" line 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 condition against which the signal is verified is provisioned in the MG.
+
+EventsDescriptor parameters: None
+
+ObservedEventsDescriptor parameters: None
+
+### 5.2.6 Congestion
+
+Event name: Congestion
+
+EventID: cng (0x000a)
+
+Description: This event applies to an outgoing interface and is reported when a "network congestion" line 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 condition against which the signal is verified is provisioned in the MG.
+
+EventsDescriptor parameters: None
+
+ObservedEventsDescriptor parameters: None
+
+## 5.3 Signals
+
+### 5.3.1 Congestion
+
+Signal name: Congestion
+
+SignalID: cng (0x0005)
+
+Description: This signal applies to the network congestion signal on a termination. It arises when at the MGC the call setup attempt fails owing to unavailability of PDN resources or encounters network congestion while routing on PDN.
+
+Signal type: Brief
+
+Duration: Provisioned
+
+Additional parameters: None
+
+### 5.3.2 Clear forward
+
+Signal name: Clear forward
+
+SignalID: cf (0x0006)
+
+Description: This signal applies to an outgoing interface and is used to clear a call in the forward direction. The signal that is actually sent on the physical termination is provisioned in the MG.
+
+Signal type: Brief
+
+Duration: Provisioned
+
+Additional parameters: None
+
+### 5.3.3 Clear back
+
+Signal name: Clear back
+
+SignalID: cb (0x0007)
+
+Description: This signal applies to an incoming interface and is used to clear a call in the backward direction. The signal that is actually sent on the physical termination is provisioned in the MG.
+
+Signal type: Brief
+
+Duration: Provisioned
+
+Additional parameters: None
+
+### 5.3.4 Subscriber line status
+
+Signal name: Subscriber line status
+
+SignalID: sls (0x0008)
+
+Description: Applies to the called subscriber line status information signal.
+
+Signal Type: Brief
+
+Duration: Provisioned
+
+Additional parameters:
+
+#### *Subscriber line condition*
+
+Parameter name: Subscriber line condition
+
+ParameterID: lsts (0x0001)
+
+Description: Line conditions of the called subscriber.
+
+Type: Enumeration
+
+Optional: No
+
+Possible values: SLB (0x0001)      Subscriber line busy.
+
+SLFC (0x0002)      Subscriber line free, charge.
+
+Default: None
+
+### 5.3.5 Release guard
+
+Signal name: Release guard
+
+SignalID: rlg (0x0009)
+
+Description: This signal applies to an outgoing interface and is used to apply a release guard signal on the trunk. The signal that is actually sent on the physical termination is provisioned in the MG.
+
+Signal type: Brief
+
+Duration: Provisioned
+
+Additional parameters: None
+
+## 5.4 Statistics
+
+### 5.4.1 Call duration
+
+Statistic name: Call duration
+
+StatisticID: cd (0x0001)
+
+Description: Provides the cumulative duration of time the termination is in an active call context, i.e., from the point of applying or receiving the "answered" signal until the point of release ("clear-forward" or "clear-back") initiation.
+
+Type: Double
+
+Possible values: Any positive integer in seconds
+
+Level: Termination
+
+## 5.5 Procedures
+
+### 5.5.1 Glare mitigation
+
+Glare conditions shall be resolved as stated in 6.5.1/H.248.25.
+
+### 5.5.2 Signal procedures
+
+A line signal must always be present on a CAS interface. Therefore the icas signals defined here, as with the bcas 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 on the CAS interface until such a time as the MGC sends a new bcas or icas signal to the MG.
+
+### 5.5.3 Property procedures
+
+The nels property shall reflect the most recently successfully applied line signal from the MGC. As per the requirements in clause 5.5.2, 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.
+
+# 6 CAS blocking package
+
+Package name: CAS blocking package
+
+PackageID: casblk (0x007c)
+
+Description: This package provides the capability of exchanging maintenance state between the MGC and the MG for terminations realizing any CAS protocol.
+
+Version: 1  
+Extends: None
+
+## 6.1 Properties
+
+### 6.1.1 Near-end line state
+
+Property name: Near-end line state  
+PropertyID: 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.  
+    Block (0x08)          The CAS termination near-end is in the blocked state.  
+Default:           The last applied line signal. If no line signal has been applied by the MGC, idle.  
+Defined in:       TerminationState descriptor  
+Characteristics: Read only
+
+### 6.1.2 Far-end line state
+
+Property name: Far-end line state  
+PropertyID: 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.  
+    Block (0x08)          The CAS termination far-end is in the blocked state.  
+Default:           The last detected line event. If no line event has been detected by the MG, idle.  
+Defined in:       TerminationState descriptor  
+Characteristics: Read only
+
+## 6.2 Events
+
+### 6.2.1 Block
+
+Event name: Block  
+EventID: blk (0x0001)  
+Description: Indicates that the remote end has blocked the termination.  
+EventsDescriptor parameters: None  
+ObservedEventsDescriptor parameters: None
+
+### 6.2.2 Unblock
+
+Event name: Unblock  
+EventID: ublk (0x0002)
+
+Description: Indicates that the remote end has unblocked the termination, removing the busy condition.
+
+EventsDescriptor parameters: None
+
+ObservedEventsDescriptor parameters: None
+
+## **6.3 Signals**
+
+### **6.3.1 Block**
+
+Signal name: Block
+
+SignalID: blk (0x0001)
+
+Description: This signal indicates that the MG should render the termination blocked for the remote end. Removal of this signal results in the termination being idled.
+
+Signal type: Brief
+
+Duration: Provisioned
+
+Additional parameters: None
+
+## **6.4 Statistics**
+
+None.
+
+## **6.5 Procedures**
+
+### **6.5.1 Property procedures**
+
+The nels property shall reflect the most recent successfully applied line signal from the MGC. As per the requirements in clause 5.5.2, 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.
+
+
+
+## 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.3-201303-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.3-201303-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dad02182b30e94f721c7f50726f60641c96df521
--- /dev/null
+++ b/marked/H/T-REC-H.248.3-201303-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:45bf920a7798c0111eed0c87f3f277105f8935167814eaedd42f96a3f983bba0
+size 4024
diff --git a/marked/H/T-REC-H.248.30-200701-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.30-200701-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c
--- /dev/null
+++ b/marked/H/T-REC-H.248.30-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.248.31-200404-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/H/T-REC-H.248.31-200404-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..97978da26d5e13fdda73b2514c35bd84a3f951ef
--- /dev/null
+++ b/marked/H/T-REC-H.248.31-200404-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b5345c49e2e3d9515bf43fa642f753c936a5b4d13feb28db942445192319bd92
+size 50939
diff --git a/marked/H/T-REC-H.248.31-200404-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.248.31-200404-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5d265b0b1d801b68a1811f50255d4ce309cea099
--- /dev/null
+++ b/marked/H/T-REC-H.248.31-200404-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:83e288ae149cd15c33d4d0054115c536d5a200511f364537b2fb9fabaea4aeaa
+size 8235
diff --git a/marked/H/T-REC-H.248.31-200404-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/H/T-REC-H.248.31-200404-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..11aa78a3e2837d456582b01d7aa8d311837d8706
--- /dev/null
+++ b/marked/H/T-REC-H.248.31-200404-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6825c066258adc165d5825d109f5d84da1630be94b35c89480878fd585840d65
+size 35495
diff --git a/marked/H/T-REC-H.248.31-200404-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/H/T-REC-H.248.31-200404-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..82d9266a6ea5e0ae5b51e52ad0233872f421388d
--- /dev/null
+++ b/marked/H/T-REC-H.248.31-200404-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9afe4813315608a67d8fd45b7b8c7712e2c24ea0c05f8d7f74fb372015f059d8
+size 77248
diff --git a/marked/H/T-REC-H.248.31-200404-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/H/T-REC-H.248.31-200404-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3e1b86dbe268b1445bf4877bb64e488ea7487716
--- /dev/null
+++ b/marked/H/T-REC-H.248.31-200404-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c863221f8d49703ba3798eb815e66711ea1f75d44e9ae91c972083fb93b2f35e
+size 25830
diff --git a/marked/H/T-REC-H.248.32-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.248.32-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994
--- /dev/null
+++ b/marked/H/T-REC-H.248.32-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.34-201202-I_PDF-E/raw.md b/marked/H/T-REC-H.248.34-201202-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..9caaa1f367ebec33740d947a04ee65cde967bd52
--- /dev/null
+++ b/marked/H/T-REC-H.248.34-201202-I_PDF-E/raw.md
@@ -0,0 +1,821 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.34**
+
+(02/2012)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+---
+
+**Gateway control protocol: Stimulus analogue  
+line package**
+
+Recommendation ITU-T H.248.34
+
+![ITU logo](84a1d09fb489061482111515543b60dc_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        |
+| <b>Communication procedures</b>                                               | <b>H.240–H.259</b> |
+| 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.34
+
+# Gateway control protocol: Stimulus analogue line package
+
+## Summary
+
+Recommendation ITU-T H.248.34 describes a stimulus analogue line package that defines new ITU-T H.248 events, signals and parameters derived from the V5 PSTN protocol defined in Recommendation ITU-T G.964.
+
+To assist both vendors and operators in migrating V5 local exchange and access network nodes to a next generation network (NGN) media gateway (MG) and media gateway controller (MGC) architecture, the package provides guidelines for mapping the V5 PSTN protocol to the "stimulus analogue line" package, other ITU-T H.248 packages and the ITU-T H.248.1 protocol.
+
+This revision clarifies dialling method indications, implements a syntactical correction of steady state signal "reversed polarity" (see Table 6) and corrects the V5 digit-signal information element mapping (Table I.2).
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group |
+|---------|----------------|------------|-------------|
+| 1.0     | ITU-T H.248.34 | 2005-01-08 | 16          |
+| 2.0     | ITU-T H.248.34 | 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 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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    |
+| 4 Abbreviations and acronyms .....                    | 2    |
+| 5 Conventions .....                                   | 2    |
+| 6 Stimulus Analogue Line Package.....                 | 2    |
+| 6.1 Properties.....                                   | 3    |
+| 6.2 Events .....                                      | 3    |
+| 6.3 Signals .....                                     | 8    |
+| 6.4 Statistics.....                                   | 11   |
+| 6.5 Procedures .....                                  | 11   |
+| Appendix I – V5 to ITU-T H.248 mapping overview ..... | 21   |
+| Bibliography.....                                     | 24   |
+
+
+
+# Recommendation ITU-T H.248.34
+
+## Gateway control protocol: Stimulus analogue line package
+
+## 1 Scope
+
+The stimulus analogue line package defines ITU-T H.248 signals and events that are exchanged between a media gateway (MG) and a media gateway controller (MGC) for controlling analogue plain old telephone service (POTS) lines which can, for example, be used to host telephones, analogue private branch exchanges (PBXs) and turn-key systems. The signals and events defined in the package are stimulus in nature and enable the full set of POTS services that are delivered via a V5 local exchange (LE) and access network (AN) to be ubiquitously provided in a next generation network (NGN) MG and MGC architecture.
+
+NOTE – The use of the Call Finished signal is a national option. It is included as part of a joint text with ETSI. In normal circumstances, the national specific functionality shall be included as a separate package. The use of the Call Finished signal shall not compromise existing ITU-T H.248 procedures.
+
+## 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.964] Recommendation ITU-T G.964 (2001), *V-interfaces at the digital local exchange (LE) – V5.1 interface (based on 2048 kbit/s) for the support of access network (AN)*.
+- [ITU-T G.965] Recommendation ITU-T G.965 (2001), *V-interfaces at the digital local exchange (LE) – V5.2 interface (based on 2048 kbit/s) for the support of access network (AN)*.
+- [ITU-T H.248.1] Recommendation ITU-T H.248.1 (2002), *Gateway control protocol: Version 2, plus Corrigendum 1 (2004)*.
+- [ITU-T H.248.8] Recommendation ITU-T H.248.8 (2002), *Gateway control protocol: Error code and service change reason description, plus Amendment 1 (2004), New error code 458 (Unexpected Event/RequestID)*.
+- [ITU-T H.248.23] Recommendation ITU-T H.248.23 (2005), *Gateway control protocol: Enhanced alerting packages*.
+- [ITU-T H.248.26] Recommendation ITU-T H.248.26 (2003), *Gateway control protocol: Enhanced analogue lines packages, plus Amendment 1 (2005)*.
+- [ITU-T H.248.70] Recommendation ITU-T H.248.70 (2009), *Gateway control protocol: Dialling method information packages*.
+
+## 3 Definitions
+
+This Recommendation defines the following terms:
+
+**3.1 access network (AN):** A system implemented between the local exchange (LE) and user, replacing part or the whole of the local line distribution network.
+
+**3.2 local exchange (LE):** An exchange on which user lines are terminated via an access network (AN).
+
+**3.3 V5:** A general term for the family of V interfaces for connection of ANs to the LE, e.g., a V5.1 interface or a V5.2 interface.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                   |
+|------|-----------------------------------|
+| AN   | Access Network                    |
+| BCC  | Bearer Channel Connection         |
+| FSK  | Frequency-Shift Keying            |
+| LE   | Local Exchange                    |
+| MG   | Media Gateway                     |
+| MGC  | Media Gateway Controller          |
+| NGN  | Next Generation Network           |
+| PBX  | Private Branch Exchange           |
+| POTS | Plain Old Telephone Service       |
+| PSTN | Public Switched Telephone Network |
+| TDM  | Time Division Multiplex           |
+
+## 5 Conventions
+
+None.
+
+# 6 Stimulus Analogue Line Package
+
+Package name: Stimulus Analogue Line Package
+
+Package ID: stim1 (0x0093)
+
+Description: This package defines all the stimulus events and signals necessary for controlling an analogue line. This analogue line package is different from other ITU-T H.248 analogue line packages, because the analogue signals and events that are exchanged between the MGC and the MG are stimulus rather than functional in nature. The stimulus approach enables the MG to be transparent to the underlying service being delivered by the MGC and also does not unduly restrict the types of services that may be delivered to an analogue line.
+
+The ITU-T H.248 signals and events have been derived from the V5 PSTN protocol signals defined in [ITU-T G.965], [ITU-T G.964]. This approach enables the MGC to support the same type of services and capabilities as the existing PSTN network.
+
+NOTE – Unlike an AN as defined in [ITU-T G.964] and [ITU-T G.965], an ITU-T H.248 MG has the capability to detect in-band (e.g., DTMF) signals, generate local tones and announcements and generate frequency-shift keying (FSK) tones for caller display purposes. Control of these capabilities is provided by other packages in the ITU-T H.248 series of Recommendations.
+
+The stimulus analogue line package is a superset package that defines the full repertoire of signals and events. A particular PSTN national authority may support a subset of the signals, events and parameters listed in the package.
+
+Version: 1  
+Extends: none
+
+## 6.1 Properties
+
+None.
+
+## 6.2 Events
+
+### 6.2.1 Steady signal
+
+Event name: Steady Signal  
+Event ID: stedsig (0x0001)  
+Description: Activation of the "Steady Signal" event results in either all the steady signals that are supported by the MG being reported to the MGC, or a list of specified steady signals being reported by the MG to the MGC. The former functionality is achieved by excluding the events descriptor parameter "Signal to Detect" when the event descriptor is activated. The latter functionality is achieved by including the events descriptor parameter "Signal to Detect" when the events descriptor is activated. The actual steady signal that is reported to the MGC is identified by the ObservedEventsDescriptor parameter "Detected Signal".
+
+The default recognition time of a particular steady signal may be modified via the events descriptor parameter "Recognition Time".
+
+#### 6.2.1.1 EventsDescriptor parameters
+
+##### 6.2.1.1.1 Signal to Detect
+
+Parameter name: Signal to Detect  
+Parameter ID: detectsig (0x0001)  
+Description: This parameter indicates to the MG the type of steady signals that are to be recognized by the MG.
+
+If this parameter is excluded, then all steady signals that are recognized by the MG are detected and subsequently reported via the ObservedEvents descriptor.
+
+If this parameter is included, then only the specified list of steady signals are detected and subsequently reported via the ObservedEvents descriptor.
+
+Type: sub-list of Enumeration
+
+Optional: yes  
+ Possible values: See Table 1 below for a list of steady signal parameter names and values.  
+ Default: all steady signals
+
+**Table 1 – Steady signal parameter names and values**
+
+| Text encoding                 | Binary encoding |
+|-------------------------------|-----------------|
+| "normalPolarity"              | (0x0000)        |
+| "reversePolarity"             | (0x0001)        |
+| "batteryOnC-wire"             | (0x0002)        |
+| "noBatteryOnC-wire"           | (0x0003)        |
+| "offHook"                     | (0x0004)        |
+| "onHook"                      | (0x0005)        |
+| "batteryOnA-wire"             | (0x0006)        |
+| "aWireonEarth"                | (0x0007)        |
+| "noBatteryOnA-wire"           | (0x0008)        |
+| "noBatteryOnB-wire"           | (0x0009)        |
+| "reducedBattery"              | (0x000a)        |
+| "noBattery"                   | (0x000b)        |
+| "alternateReducedPower"       | (0x000c)        |
+| "normalBattery"               | (0x000d)        |
+| "stopRinging"                 | (0x000e)        |
+| "startPilotFrequency"         | (0x000f)        |
+| "stopPilotFrequency"          | (0x0010)        |
+| "lowImpedanceonB-wire"        | (0x0011)        |
+| "b-wireConnectedtoearth"      | (0x0012)        |
+| "b-wireDisconnectedfromearth" | (0x0013)        |
+| "batteryOnB-wire"             | (0x0014)        |
+| "lowLoopImpedance"            | (0x0015)        |
+| "highLoopImpedance"           | (0x0016)        |
+| "anomalousLoopImpedance"      | (0x0017)        |
+| "a-wireDisconnectedfromearth" | (0x0018)        |
+| "c-wireOneearth"              | (0x0019)        |
+| "c-wireDisconnectedfromearth" | (0x001a)        |
+| "rampToReversePolarity"       | (0x001d)        |
+| "rampToNormalPolarity"        | (0x001e)        |
+
+##### **6.2.1.1.2 Recognition Time**
+
+Parameter name: Recognition Time  
+Parameter ID: rectime (0x0002)  
+Description: This parameter is included if the default recognition time of a steady signal is to be modified.  
+Type: integer  
+Optional: yes  
+Possible values: Any positive value in milliseconds.  
+Default: provisioned default for each steady signal
+
+#### **6.2.1.2 ObservedEventsDescriptor parameters**
+
+##### **6.2.1.2.1 Detected Signal**
+
+Parameter name: Detected Signal  
+Parameter ID: sig (0x0001)  
+Description: This parameter returns the detected steady signal.  
+Type: enumeration  
+Optional: no  
+Possible values: See Table 1 for a list of steady signal parameter names and values.  
+Default: none
+
+### **6.2.2 Line Information**
+
+Event name: Line Information  
+Event ID: lineinfo (0x0002)  
+Description: The line information is used to transmit specific information on the subscriber line status to the MGC.
+
+#### **6.2.2.1 EventsDescriptor parameters**
+
+None.
+
+#### **6.2.2.2 ObservedEventsDescriptor parameters**
+
+##### **6.2.2.2.1 Line Information**
+
+Parameter name: Line Information  
+Parameter ID: info (0x0001)  
+Description: This parameter indicates that the status of the subscriber line has changed.  
+Type: enumeration  
+Optional: no  
+Possible values: See Table 2 for a list of line information parameter names and values.  
+Default: none
+
+**Table 2 – Line info parameter names and values**
+
+| <b>Text encoding</b>     | <b>Binary encoding</b> |
+|--------------------------|------------------------|
+| "impedanceMarkerReset"   | (0x0000)               |
+| "impedanceMarkerSet"     | (0x0001)               |
+| "lowLoopImpedance"       | (0x0002)               |
+| "anomalousLoopImpedance" | (0x0003)               |
+| "anomalousLineCondition" | (0x0004)               |
+
+### 6.2.3 Pulsed Signal
+
+Event name: Pulsed Signal
+
+Event ID: pulsedsig (0x0003)
+
+Description: Activation of the "Pulsed Signal" event results in either all the pulsed signals that are supported by the MG being reported to the MGC, or a list of specified pulsed signals being reported by the MG to the MGC. The former functionality is achieved by excluding the event descriptor parameter "Signal to Detect" when the events descriptor is activated. The latter functionality is achieved by including the events descriptor parameter "Signal to Detect", when the events descriptor is activated. The actual pulsed signal that is reported to the MGC is identified by the ObservedEventsDescriptor parameter "Detected Signal".
+
+The default recognition time of a particular pulsed signal may be modified via the Events Descriptor parameter "Recognition Time".
+
+#### 6.2.3.1 EventsDescriptor parameters
+
+##### 6.2.3.1.1 Signal to Detect
+
+Parameter name: Signal to Detect
+
+Parameter ID: detectsig (0x0001)
+
+Description: This parameter indicates to the MG the type of pulsed signals that are to be recognized by the MG.
+
+If this parameter is excluded, then all pulsed signals that are recognized by the MG are detected and subsequently reported via the ObservedEvents descriptor.
+
+If this parameter is included, then only the specified list of pulsed signals are detected and subsequently reported via the ObservedEvents descriptor.
+
+Type: sub-list of Enumeration
+
+Optional: yes
+
+Possible values: See Table 3 for a list of pulsed signal parameter names and values.
+
+Default: all pulsed signals
+
+**Table 3 – Pulsed signal parameter names and values**
+
+| Text encoding                    | Binary encoding |
+|----------------------------------|-----------------|
+| "pulsedNormalPolarity"           | (0x007f)        |
+| "pulsedReversedPolarity"         | (0x007e)        |
+| "pulsedBatteryonCwire"           | (0x007d)        |
+| "pulsedOnHook"                   | (0x007c)        |
+| "pulsedReducedBattery"           | (0x007b)        |
+| "pulsedNoBattery"                | (0x007a)        |
+| "initialRing"                    | (0x0079)        |
+| "meterPulse"                     | (0x0078)        |
+| "50HzPulse"                      | (0x0077)        |
+| "registerrecall"                 | (0x0076)        |
+| "pulsedOffHook"                  | (0x0075)        |
+| "pulsedB-wireConnectedToEarth"   | (0x0074)        |
+| "earthLoopPulse"                 | (0x0073)        |
+| "pulsedB-wireConnectedToBattery" | (0x0072)        |
+| "pulsedA-wireConnectedToEarth"   | (0x0071)        |
+| "pulsedA-wireConnectedToBattery" | (0x0070)        |
+| "pulsedC-wireConnectedToEarth"   | (0x006f)        |
+| "pulsedC-wireDisconnected"       | (0x006e)        |
+| "pulsedNormalBattery"            | (0x006d)        |
+| "pulsedA-wireDisconnected"       | (0x006c)        |
+| "pulsedB-wireDisconnected"       | (0x006b)        |
+
+##### **6.2.3.1.2 Recognition Time**
+
+Parameter name: Recognition Time  
+Parameter ID: rectime (0x0002)  
+Description: This parameter is included if the default recognition time of a pulsed signal is to be modified.  
+Type: integer  
+Optional: yes  
+Possible values: Any positive value in milliseconds.  
+Default: provisioned per pulsed signal
+
+#### **6.2.3.2 ObservedEventsDescriptor parameters**
+
+##### **6.2.3.2.1 Detected Signal**
+
+Parameter name: Detected Signal  
+Parameter ID: sig (0x0001)  
+Description: This parameter returns the detected pulsed signal.  
+Type: enumeration
+
+Optional: no  
+Possible values: See Table 3 for a list of pulsed signal parameter names and values.  
+Default: none
+
+### **6.2.4 Autonomous Signalling Sequence Response**
+
+Event Name: Autonomous Signalling Sequence Response  
+Event ID: autosigseqresp (0x0004)  
+Description: The purpose of the "autonomous signalling sequence response" is to inform the MGC about the results of the application of the signal "autonomous signalling sequence". The sequence response type identifies a particular (pre-defined) response.
+
+#### **6.2.4.1 EventsDescriptor parameters**
+
+None.
+
+#### **6.2.4.2 ObservedEventsDescriptor parameters**
+
+##### **6.2.4.2.1 Sequence Response Type**
+
+Parameter name: Sequence Response Type  
+Parameter ID: seqresptype (0x0001)  
+Description: The sequence response type specifies a particular response to the request to apply the autonomous signalling sequence.  
+Type: integer  
+Optional: no  
+Possible values: Any non-negative value  
+Default: none
+
+## **6.3 Signals**
+
+### **6.3.1 Pulsed Signal**
+
+Signal name: Pulsed Signal  
+Signal ID: pulsedsig (0x0001)  
+Description: Used by the MGC to instruct the MG to apply a pulsed signal.  
+Signal Type: brief  
+Duration: provisioned
+
+#### **6.3.1.1 Additional parameters**
+
+##### **6.3.1.1.1 Signal**
+
+Parameter name: Signal  
+Parameter ID: sig (0x0001)  
+Description: This parameter indicates the type of pulsed signal to be sent.  
+Type: enumeration  
+Optional: no
+
+Possible values: See Table 3 for a list of pulsed signal parameter names and values.  
+Default: none
+
+##### **6.3.1.1.2 Number of Pulses**
+
+Parameter name: Number of Pulses  
+Parameter ID: numofpulses (0x0002)  
+Description: This parameter indicates the number of pulses to be sent.  
+Type: integer  
+Optional: yes  
+Possible Values: A positive number of pulses  
+Default: 1
+
+### **6.3.2 Steady Signal**
+
+Signal name: Steady Signal  
+Signal ID: stedsig (0x0002)  
+Description: Used by the MGC to instruct the MG to apply a steady signal.  
+Signal Type: OnOff  
+Duration: not applicable
+
+#### **6.3.2.1 Additional parameters**
+
+##### **6.3.2.1.1 Signal**
+
+Parameter name: Signal  
+Parameter ID: sig (0x0001)  
+Description: This indicates the steady signal to be sent.  
+Type: enumeration  
+Optional: no  
+Possible values: See Table 1 for a list of steady signal parameter names and values.  
+Default: none
+
+### **6.3.3 Digits**
+
+Signal name: Digits  
+Signal ID: digits (0x0003)  
+Description: A signal to specify that loop digits are to be forwarded to the analogue line for onward routing of the call. The mapping of the digit values to the number of loop disconnect pulses sent is provisioned in the MG.  
+Signal Type: brief  
+Duration: provisioned
+
+#### **6.3.3.1 Additional parameters**
+
+##### **6.3.3.1.1 Digits**
+
+Parameter name: Digits  
+Parameter ID: digit (0x0001)  
+Description: The string of digits to be generated.  
+Type: string  
+Optional: no  
+Possible values: A sequence of the characters '0' through to '9', 'A' through 'F'.  
+Default: none
+
+### **6.3.4 Autonomous Signalling Sequence**
+
+Signal name: Autonomous Signalling Sequence  
+Signal ID: autosigseq (0x0004)  
+Description: An indication to the MG to start a predefined signalling sequence as defined by the sequence type.  
+Signal type: brief  
+Duration: duration varies depending on parameter values
+
+#### **6.3.4.1 Additional parameters**
+
+##### **6.3.4.1.1 Sequence Type**
+
+Parameter name: Sequence Type  
+Parameter ID: seqtype (0x0001)  
+Description: The sequence type to apply.  
+Type: integer  
+Optional: no  
+Possible values: Any non-negative value  
+Default: none
+
+### **6.3.5 Call Finished**
+
+Signal name: Call Finished  
+Signal ID: cfin (0x0005)  
+Description: This signal is sent by the MGC to indicate to the MG that it shall apply a voltage/current feed that corresponds to an Idle Feed condition. For example, as is defined in the "V5 – UK Mapping requirements" [b-SSPE/SPEC/001-1].  
+Signal type: brief  
+Duration: provisioned
+
+#### **6.3.5.1 Additional parameters**
+
+None.
+
+## **6.4 Statistics**
+
+None.
+
+## **6.5 Procedures**
+
+### **6.5.1 Event – Steady signal**
+
+The "steady signal" event is used by the MG to report to the MGC, the occurrence of a certain steady signal condition on the analogue line. The "signal" parameter identifies the type of steady signal detected. The default recognition time of a steady signal may be modified by including the Events Descriptor parameter "recognition time".
+
+### **6.5.2 Event – Line information**
+
+The "line information" event is used by the MG to report to the MGC the line status. This event is reported when the status of the line changes. The "info" parameter identifies the subscriber line status.
+
+### **6.5.3 Event – Pulsed signal**
+
+The "pulsed signal" event is used by the MG to report to the MGC, the occurrence of a certain pulsed signal condition on the analogue line. The "signal" parameter identifies the type of pulsed signal detected. The default recognition time of a pulsed signal may be modified by including the Events Descriptor parameter "recognition time".
+
+### **6.5.4 Event – Autonomous signalling response**
+
+The "autonomous signalling response" event is used to notify the MGC about the result of the application of the signal "autonomous signalling sequence" that was requested by the MGC. The parameter "Sequence Response Type" in the ObservedEvents Descriptor identifies the result.
+
+### **6.5.5 Signal – Pulsed signal**
+
+The "pulsed signal" signal is used by the MGC to request the MG to apply the specified pulsed signal to the analogue line.
+
+### **6.5.6 Signal – Steady signal**
+
+The "steady signal" signal is used by the MGC to request the MG to apply the specified steady signal to the analogue line.
+
+### **6.5.7 Signal – Digits**
+
+The "digits" signal is sent by the MGC to request the MG to send loop disconnect digits to an analogue line.
+
+### **6.5.8 Signal – Autonomous signalling sequence**
+
+The "autonomous signalling sequence" signal is used by the MGC to request the MG to apply a predefined signalling sequence.
+
+### **6.5.9 Signal – Call finished**
+
+The "Call Finished" signal is sent to the MG to indicate that it shall apply a voltage/current feed that corresponds to an Idle Feed condition.
+
+### **6.5.10 Guidelines for mapping of the V5 PSTN protocol**
+
+This clause provides guidelines on mapping the V5 PSTN protocol defined in [ITU-T G.964] to the ITU-T H.248 protocol. These guidelines may assist both network operators and vendors in the migration of their existing V5 PSTN protocol implementations to an architecture based on the ITU-T H.248 series of Recommendations.
+
+Table 4 describes the mapping of V5 PSTN Protocol messages to ITU-T H.248 commands. Table 5 describes the mapping of the V5 Bearer Channel Connection Protocol to ITU-T H.248 commands. Table 6 provides a mapping of V5 information elements to ITU-T H.248 concepts.
+
+**Table 4 – Mapping of V5 PSTN Protocol messages**
+
+| <b>Message type</b>                | <b>Reference ITU-T G.964 (clause)</b> | <b>Mapping</b>                                                              | <b>Mapping details</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|------------------------------------|---------------------------------------|-----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Path establishment messages</b> |                                       |                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| ESTABLISH                          | 13.3.1                                | ITU-T H.248 (Transaction Request e.g., Notify, Modify)                      | This V5 message maps to a command in ITU-T H.248 (e.g., Notify, Modify). V5 information elements can be mapped to appropriate ITU-T H.248 events and signals descriptors as defined in Table 6.                                                                                                                                                                                                                                                                                                                                                                 |
+| ESTABLISH ACK                      | 13.3.2                                | ITU-T H.248 (Transaction Reply), (Transaction Request e.g., Notify, Modify) | This V5 message maps to a ITU-T H.248 "Transaction Reply". V5 allows detected steady and pulsed signals to be embedded in the Establish Ack. In the MG to MGC case, detected ITU-T H.248 steady and pulsed signals must be carried in a separate transaction request and command (e.g., Notify) specifying an ObservedEvents descriptor as defined in Table 6. In the MGC to MG case, ITU-T H.248 steady and pulsed signals must be carried in a separate transaction request and command (e.g., Modify) specifying a signals descriptor as defined in Table 6. |
+| SIGNAL                             | 13.3.3                                | ITU-T H.248 (Transaction Request e.g., Notify, Modify)                      | This V5 message maps to a command in ITU-T H.248 (e.g., Notify, Modify) and V5 information elements can be carried within an events descriptor and signals descriptor as defined in Table 6.                                                                                                                                                                                                                                                                                                                                                                    |
+| SIGNAL ACK                         | 13.3.4                                | No mapping                                                                  | This V5 message is specific to the V5 PSTN protocol and support is not required within ITU-T H.248.                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+**Table 4 – Mapping of V5 PSTN Protocol messages**
+
+| <b>Message type</b>           | <b>Reference ITU-T G.964 (clause)</b> | <b>Mapping</b>                                                                               | <b>Mapping details</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|-------------------------------|---------------------------------------|----------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Path clearing messages</b> |                                       |                                                                                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| DISCONNECT                    | 13.3.7                                | ITU-T H.248 (Transaction Request e.g., Subtract, Modify)                                     | <p>This V5 message is used by the LE to indicate that there is no call activity to the AN.</p> <p>The V5 "Disconnect" is mapped as follows:<br/>           If the analogue termination is not in the Null context, then the V5 "Disconnect" is mapped to a ITU-T H.248 Subtract command. The ITU-T H.248 Subtract command will result in the descriptors (e.g., signals and events descriptors) being reset to their default or provisioned values and the termination is placed in an idle state.<br/>           If the analogue termination is in the Null context, then the V5 "Disconnect" is mapped to a ITU-T H.248 Modify command.<br/>           If the optional "call finished" signal is supported, then the V5 "Disconnect" is mapped to the "call finished" signal.</p> |
+| DISCONNECT COMPLETE           | 13.3.8                                | ITU-T H.248 (Transaction Reply)                                                              | This is an acknowledgement to the V5 Disconnect message. In ITU-T H.248 this maps to a "Transaction Reply".                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Other messages</b>         |                                       |                                                                                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| STATUS ENQUIRY                | 13.3.6                                | ITU-T H.248 (Transaction Request e.g., Audit Value, Modify or Move with an Audit Descriptor) | This V5 message is specific to the V5 PSTN protocol error handling and is used to request the V5 PSTN protocol state of the AN. The ITU-T H.248 protocol has an Audit Value command and Audit descriptor for auditing the MG.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| STATUS                        | 13.3.5                                | No mapping                                                                                   | This V5 message is specific to the V5 PSTN protocol error handling and carries state and cause information elements and therefore no direct mapping is required. The ITU-T H.248 protocol has its own mechanism for conveying protocol errors by using the Error descriptor.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| PROTOCOL PARAMETER            | 13.3.9                                | ITU-T H.248 (Transaction Request e.g., Modify)                                               | This V5 message is used to carry the recognition time, enable autonomous ack and disable autonomous ack V5 information elements. This message is mapped to a ITU-T H.248 command (e.g., Modify) and the V5 information elements can be mapped to ITU-T H.248 events and signals descriptors as defined in Table 6.                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+**Table 5 – Mapping of V5.2 Bearer Channel Connection (BCC) Protocol**
+
+| V5.2 BCC message | ITU-T H.248 mapping details                                                                                                                                                   |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Allocate         | An "Allocate" maps to ITU-T H.248 Add commands, which specify an association between physical and ephemeral terminations within the same context.                             |
+| Deallocate       | In the simplest case, the "Deallocate" maps to ITU-T H.248 "Subtract" commands that return physical terminations to the NULL context and destroys the ephemeral terminations. |
+
+**Table 6 – Detailed mapping of V5 PSTN Protocol Information Elements**
+
+| V5 PSTN Protocol Information Elements | ITU-T H.248 mapping details                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Pulse Notification                    | <p>In V5 a pulse notification can be requested by the LE at the end of all the pulses, start of the first pulse or at the end of each pulse.</p> <p>The corresponding mappings in ITU-T H.248 are provided below:</p> <ul style="list-style-type: none"> <li>• End of all the pulses – This is achieved in ITU-T H.248.1 by setting the Notify Complete flag to "Time Out" and activating the signal completion event in the Generic Package (see clause E.1 of [ITU-T H.248.1]).</li> <li>• Start of the first pulse – Determined by the MGC upon receipt of an ITU-T H.248 "Transaction Reply" containing a successful response to the command.</li> <li>• End of each pulse.</li> </ul> <p>NOTE – This may be achieved in ITU-T H.248.1 by setting the Notify Complete flag to "onIteration" (this value of NotifyComplete will be available in ITU-T H.248.1 version 3) and activating the signal completion event in the Generic Package (see clause E.1 of [ITU-T H.248.1]).</p> |
+| Line Information                      | Mapped to "line information" event in this package.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| Autonomous Signalling Sequence        | The V5 information element is mapped to the "autonomous signalling sequence" signal in this package. The V5 "sequence type" parameter is directly mapped to the signal parameter "sequence type". V5 supports "sequence type" values in the range 0 to 15, while the sequence type parameter in this package is an Integer and provides enhanced capability.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| Sequence Response                     | The V5 information element is mapped to the "autonomous signalling sequence response" event in this package. The V5 "sequence response type" parameter is directly mapped to the ObservedEvents Descriptor parameter "sequence response type". V5 supports "sequence response" values in the range 0 to 15, while the sequence response type parameter in this package is an Integer and provides enhanced capability.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| Cadenced Ringing                      | This is supported by ring signal in the Enhanced Alerting package version 2 [ITU-T H.248.23]. The V5 ring cadence type information element is mapped to the "pattern" parameter.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+**Table 6 – Detailed mapping of V5 PSTN  
+Protocol Information Elements**
+
+| <b>V5 PSTN<br/>Protocol<br/>Information<br/>Elements</b> | <b>ITU-T H.248 mapping details</b>                                                                                                                                                                                                                                                            |              |                                  |                        |
+|----------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|----------------------------------|------------------------|
+| Pulsed Signal                                            | In the MGC to MG direction, the V5 information element is mapped to the signal "pulsed signal" defined in this package with the V5 parameters mapped as follows: <ul style="list-style-type: none"> <li>Pulse type – Directly mapped to the parameter "Signal" as specified below.</li> </ul> |              |                                  |                        |
+|                                                          | <b>V5</b>                                                                                                                                                                                                                                                                                     |              | <b>H.248</b>                     |                        |
+|                                                          | <b>Pulsed signal</b>                                                                                                                                                                                                                                                                          | <b>Value</b> | <b>Text encoding</b>             | <b>Binary encoding</b> |
+|                                                          | Pulsed normal polarity                                                                                                                                                                                                                                                                        | 127          | "pulsedNormalPolarity"           | (0x007F)               |
+|                                                          | Pulsed reversed polarity                                                                                                                                                                                                                                                                      | 126          | "pulsedReversedPolarity"         | (0x007E)               |
+|                                                          | Pulsed battery on c-wire                                                                                                                                                                                                                                                                      | 125          | "pulsedBatteryonCwire"           | (0x007D)               |
+|                                                          | Pulsed on hook                                                                                                                                                                                                                                                                                | 124          | "pulsedOnHook"                   | (0x007C)               |
+|                                                          | Pulsed reduced battery                                                                                                                                                                                                                                                                        | 123          | "pulsedReducedBattery"           | (0x007B)               |
+|                                                          | Pulsed no battery                                                                                                                                                                                                                                                                             | 122          | "pulsedNoBattery"                | (0x007A)               |
+|                                                          | Initial Ring                                                                                                                                                                                                                                                                                  | 121          | "initialRing"                    | (0x0079)               |
+|                                                          | Meter pulse                                                                                                                                                                                                                                                                                   | 120          | "meterpulse"                     | (0x0078)               |
+|                                                          | 50 Hz pulse                                                                                                                                                                                                                                                                                   | 119          | "50HzPulse"                      | (0x0077)               |
+|                                                          | Register recall (timed loop open)                                                                                                                                                                                                                                                             | 118          | "registerrecall"                 | (0x0076)               |
+|                                                          | Pulsed off hook (pulsed loop closed)                                                                                                                                                                                                                                                          | 117          | "pulsedOffHook"                  | (0x0075)               |
+|                                                          | Pulsed b-wire connected to earth                                                                                                                                                                                                                                                              | 116          | "pulsedB-wireConnectedToEarth"   | (0x0074)               |
+|                                                          | Earth loop pulse                                                                                                                                                                                                                                                                              | 115          | "earthLoopPulse"                 | (0x0073)               |
+|                                                          | Pulsed b-wire connected to battery                                                                                                                                                                                                                                                            | 114          | "pulsedB-wireConnectedToBattery" | (0x0072)               |
+|                                                          | Pulsed a-wire connected to earth                                                                                                                                                                                                                                                              | 113          | "pulsedA-wireConnectedToEarth"   | (0x0071)               |
+|                                                          | Pulsed a-wire connected to battery                                                                                                                                                                                                                                                            | 112          | "pulsedA-wireConnectedToBattery" | (0x0070)               |
+|                                                          | Pulsed c-wire connected to earth                                                                                                                                                                                                                                                              | 111          | "pulsedC-wireConnectedToEarth"   | (0x006F)               |
+|                                                          | Pulsed c-wire disconnected                                                                                                                                                                                                                                                                    | 110          | "pulsedC-wireDisconnected"       | (0x006E)               |
+|                                                          | Pulsed normal battery                                                                                                                                                                                                                                                                         | 109          | "pulsedNormalBattery"            | (0x006D)               |
+|                                                          | Pulsed a-wire disconnected                                                                                                                                                                                                                                                                    | 108          | "pulsedA-wireDisconnected"       | (0x006C)               |
+|                                                          | Pulsed b-wire disconnected                                                                                                                                                                                                                                                                    | 107          | "pulsedB-wireDisconnected"       | (0x006B)               |
+
+**Table 6 – Detailed mapping of V5 PSTN  
+Protocol Information Elements**
+
+| V5 PSTN<br>Protocol<br>Information<br>Elements | ITU-T H.248 mapping details                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |       |                         |                 |
+|------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------------------------|-----------------|
+|                                                | <ul style="list-style-type: none"> <li>Number of pulses – Directly mapped to the "Number of Pulses" parameter.</li> <li>Pulse Duration Type – The default duration is provisioned in the MG, but this can be overridden by specifying a signal duration parameter specified in [ITU-T H.248.1].</li> <li>Suppression Indicator – Mapped to the ITU-T H.248.1 KeepActive flag, which is associated with the detected event that should not halt the pulsed signal.</li> <li>Ack Request Indicator – See text regarding V5 "pulse notification" information element.</li> </ul> <p>In the MG to MGC direction, the V5 information element is mapped to the ObservedEvent "pulsed signal" defined in this package with the V5 parameters mapped as follows:</p> <ul style="list-style-type: none"> <li>Pulse type – Directly mapped to the parameter "Detected Signal".</li> <li>Number of pulses – Not applicable in this direction.</li> <li>Pulse Duration Type – Not applicable in this direction.</li> <li>Suppression Indicator – Not applicable in this direction.</li> <li>Ack Request Indicator – Not applicable in this direction.</li> </ul> |       |                         |                 |
+| Steady Signal                                  | <p>In the MGC to MG direction, the V5 information element is mapped to the signal "steady signal" defined in this package with the V5 parameters mapped as follows:</p> <ul style="list-style-type: none"> <li>Steady Signal type – Directly mapped to the parameter "Signal" as specified below.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |       |                         |                 |
+|                                                | V5                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |       | ITU-T H.248             |                 |
+|                                                | Steady signal                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Value | Text encoding           | Binary encoding |
+|                                                | Normal polarity                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | 0     | "normalPolarity"        | (0x0000)        |
+|                                                | Reversed polarity                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | 1     | "reverse"               | (0x0001)        |
+|                                                | Battery on c-wire                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | 2     | "batteryOnC-wire"       | (0x0002)        |
+|                                                | No battery on c-wire                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | 3     | "noBatteryOnC-wire"     | (0x0003)        |
+|                                                | Off hook (loop closed)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | 4     | "offHook"               | (0x0004)        |
+|                                                | On hook (loop open)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | 5     | "onHook"                | (0x0005)        |
+|                                                | Battery on a-wire                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | 6     | "batteryOnA-wire"       | (0x0006)        |
+|                                                | A-wire on earth                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | 7     | "aWireonEarth"          | (0x0007)        |
+|                                                | No battery on a-wire                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | 8     | "noBatteryOnA-wire"     | (0x0008)        |
+|                                                | No battery on b-wire                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | 9     | "noBatteryOnB-wire"     | (0x0009)        |
+|                                                | Reduced Battery                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | 10    | "reducedBattery"        | (0x000a)        |
+|                                                | No battery                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | 11    | "noBattery"             | (0x000b)        |
+|                                                | Alternate reduced power/no power                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | 12    | "alternateReducedPower" | (0x000c)        |
+
+**Table 6 – Detailed mapping of V5 PSTN  
+Protocol Information Elements**
+
+| V5 PSTN<br>Protocol<br>Information<br>Elements | ITU-T H.248 mapping details                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |    |                               |          |
+|------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-------------------------------|----------|
+|                                                | Normal battery                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | 13 | "normalBattery"               | (0x000d) |
+|                                                | Stop ringing                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | 14 | "stopRinging"                 | (0x000e) |
+|                                                | Start pilot frequency                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | 15 | "startPilotFrequency"         | (0x000f) |
+|                                                | Stop pilot frequency                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | 16 | "stopPilotFrequency"          | (0x0010) |
+|                                                | Low impedance on b-wire                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | 17 | "lowImpedanceonB-wire"        | (0x0011) |
+|                                                | B-wire connected to earth                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | 18 | "b-wireConnectedtoearth"      | (0x0012) |
+|                                                | B-wire disconnected from earth                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | 19 | "b-wireDisconnectedfromearth" | (0x0013) |
+|                                                | Battery on b-wire                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | 20 | "batteryOnB-wire"             | (0x0014) |
+|                                                | Low loop impedance                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | 21 | "lowLoopImpedance"            | (0x0015) |
+|                                                | High loop impedance                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | 22 | "highLoopImpedance"           | (0x0016) |
+|                                                | Anomalous loop impedance                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | 23 | "anomalousLoopImpedance"      | (0x0017) |
+|                                                | A-wire disconnected from earth                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | 24 | "a-wireDisconnectedfromearth" | (0x0018) |
+|                                                | C-wire on earth                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | 25 | "c-wireOneearth"              | (0x0019) |
+|                                                | C-wire disconnected from earth                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | 26 | "c-wireDisconnectedfromearth" | (0x001a) |
+|                                                | Ramp to reverse polarity                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | 29 | "rampToReversePolarity"       | (0x001d) |
+|                                                | Ramp to normal polarity                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | 30 | "rampToNormalPolarity"        | (0x001e) |
+|                                                | In the MG to MGC direction, the V5 information element is mapped to the ObservedEvent "steady signal" defined in this package with the V5 parameters mapped as follows:<br><ul style="list-style-type: none"> <li>Steady Signal type – Directly mapped to the parameter "Detected Signal".</li> </ul>                                                                                                                                                                                                                                                                                                                       |    |                               |          |
+| Digits Signal                                  | In the MGC to MG direction, the V5 information element is mapped to the signal "digit" in this package, with the V5 parameters mapped as follows:<br><ul style="list-style-type: none"> <li>Digit Information – Directly mapped to the "Digits" Parameter.</li> <li>Digit Ack Request Indicator – See text regarding the V5 "pulse notification" information element.</li> </ul> In the direction of MG to MGC, the Loop Disconnect digits detected by the MG are reported as a "digit completion" event as part of ITU-T H.248 digit map handling or as events defined in extended packages according to [ITU-T H.248.70]. |    |                               |          |
+
+**Table 6 – Detailed mapping of V5 PSTN  
+Protocol Information Elements**
+
+| V5 PSTN<br>Protocol<br>Information<br>Elements | ITU-T H.248 mapping details                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Recognition<br>Time                            | <p>This is mapped to an events descriptor specifying the event "steady signal" or "pulsed signal" with events descriptor parameters specifying the "detected signal" and "recognition time".</p> <p>For example, to modify the steady signal "Off Hook" recognition time to "100" ms and to report all the other steady signals (i.e., NOT offHook), then the events descriptor would contain the following information:</p> <pre>Events = requestid {     stimal/stedsig {         detectsig = offHook,         rectime = 100     },     stimal/stedsig {         detectsig # offHook     } }</pre>                                                                                                                                                                                                                     |
+| Enable<br>Autonomous<br>Acknowledge            | <p>To enable autonomous acknowledgement, an embedded signals descriptor is added to the event specifying the signal to be detected. The signals descriptor shall contain the signal that is to be autonomously sent in response to the detected event.</p> <p>For example, if "Normal Polarity" is to be sent autonomously in response to an "Off Hook" and to continue reporting all other steady signals (i.e., NOT offHook), then the events descriptor would contain the following information:</p> <pre>Events = requestid {     stimal/stedsig {         detectsig = offHook,         Embed {             Signals {                 stimal/stedsig {                     signal = normalPolarity                 }             }         },     },     stimal/stedsig {         detectsig # offHook,     } }</pre> |
+
+**Table 6 – Detailed mapping of V5 PSTN  
+Protocol Information Elements**
+
+| <b>V5 PSTN<br/>Protocol<br/>Information<br/>Elements</b> | <b>ITU-T H.248 mapping details</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|----------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Disable<br>Autonomous<br>Acknowledgement                 | <p>An autonomous acknowledgement in the MG can be disabled by replacing the events descriptor containing an embedded signals descriptor with an events descriptor, which does not contain embedding.</p> <p>For example, to request the MG to detect all steady signal events without generating an "Autonomous Ack", then the events descriptor would contain the following information:</p> <pre>Events = requestid {     stim/alsig }</pre>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| Resource<br>Unavailable                                  | This is mapped to the ITU-T H.248.8 Error Code – 510, "Insufficient Resources".                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| Enable<br>Metering                                       | <p>The mapping of the relevant V5 parameters is described below:</p> <ul style="list-style-type: none"> <li>• Repetition Indicator – This is mapped to the enable metering signal defined in the Automatic Metering package [ITU-T H.248.26]. Value "00" indicates that fixed rate metering is required and this is mapped to a non-zero "pulse count" parameter value. Value "11" indicates automatic metering and this is mapped to a zero "pulse count" parameter value.</li> <li>• Pulse Type – The frequency of the metering pulse to be applied is configured in the MG.</li> <li>• Rate Type – The rate type is mapped to an appropriate "Pulse Repetition Interval" associated with the enable metering signal in the Automatic Metering package [ITU-T H.248.26].</li> <li>• Pulse duration type – This is a provisioned item in the MG.</li> <li>• Suppression Indicator – This is mapped to the KeepActive flag which is associated with the detected event that should not suppress the automatic metering.</li> <li>• Reporting pulse count – This is mapped to the Periodic Report event and its parameter "Report period" [ITU-T H.248.26].</li> </ul> |
+| Metering<br>Report                                       | <p>The mapping of the relevant V5 parameters is described below:</p> <ul style="list-style-type: none"> <li>• Pulse Count – Counts are returned via event "Periodic Report" and the statistics "Current Pulse Count" and "Pulse Count since Last Report" as defined in the Automatic Metering package [ITU-T H.248.26].</li> <li>• Report Type – "Metering Continuing" can be assumed by the MGC if no Signal Completion event is received. "Metering ended" is determined by the MGC when the Signal Completion event is received. "Positive acknowledgement of new automatic metering instructions" is determined by the MGC when a successful Transaction reply is received in response to the instruction to apply an Enable Metering signal. "Failure of metering in the AN" can be assumed by the MGC on reception of a transaction reply with an appropriate error code.</li> <li>• Failure Reason – This is handled by an appropriate H.248.8 error code and only included when the V5 "Report Type" specifies "Failure of metering in the AN".</li> </ul>                                                                                                    |
+| Attenuation                                              | This is mapped to the gain control property in the TDM Circuit Package [ITU-T H.248.1].                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+### **5.5.11 Dialling method indication**
+
+The MGC may need to know the dialling method (DTMF or decadic pulses) associated with the detected digit or digitmap. [ITU-T H.248.70] defines an extension for the indication of the dialling method associated with the reported dialled digits. [ITU-T H.248.70] shall be used for ITU-T H.248 "stim" gateways when dialling method differentiation is required.
+
+## Appendix I
+
+### V5 to ITU-T H.248 mapping overview
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Table I.1 contains an overview of the mapping of V5 messages to ITU-T H.248 commands based on Table 16 of [ITU-T G.964]. Table I.2 indicates which information elements are implemented as events and/or signals in the stimulus analogue line package and is based on Table 17 of [ITU-T G.964].
+
+**Table I.1 – PSTN protocol message types**
+
+| Message type                       | Reference ITU-T G.964 (clause) | ITU-T H.248 mapping direction LE → AN                            | ITU-T H.248 mapping direction AN → LE                            | Description                                                                              |
+|------------------------------------|--------------------------------|------------------------------------------------------------------|------------------------------------------------------------------|------------------------------------------------------------------------------------------|
+| <b>Path establishment messages</b> |                                |                                                                  |                                                                  |                                                                                          |
+| ESTABLISH                          | 13.3.1                         | MODIFY                                                           | NOTIFY                                                           | Initiation of PSTN path                                                                  |
+| ESTABLISH ACK                      | 13.3.2                         | TRANSACTION REPLY (if required additionally TRANSACTION REQUEST) | TRANSACTION REPLY (if required additionally TRANSACTION REQUEST) | Positive response to PSTN path initiation.                                               |
+| SIGNAL                             | 13.3.3                         | MODIFY                                                           | NOTIFY                                                           | An electrical line condition described in a message (e.g., pulsed signal "Meter pulse"). |
+| SIGNAL ACK                         | 13.3.4                         | TRANSACTION REPLY                                                | TRANSACTION REPLY                                                | Acknowledgement of sent/received message                                                 |
+| <b>Path clearing messages</b>      |                                |                                                                  |                                                                  |                                                                                          |
+| DISCONNECT                         | 13.3.7                         | SUBTRACT/MODIFY (stimal/call finished)                           | Not Applicable                                                   | Initiation of clearing the PSTN path                                                     |
+| DISCONNECT COMPLETE                | 13.3.8                         | Not applicable                                                   | TRANSACTION REPLY                                                | Positive response to a path clearing                                                     |
+
+**Table I.1 – PSTN protocol message types**
+
+| <b>Message type</b>                                                  | <b>Reference ITU-T G.964 (clause)</b> | <b>ITU-T H.248 mapping direction LE → AN</b> | <b>ITU-T H.248 mapping direction AN → LE</b> | <b>Description</b>                                                               |
+|----------------------------------------------------------------------|---------------------------------------|----------------------------------------------|----------------------------------------------|----------------------------------------------------------------------------------|
+| <b>Other messages</b>                                                |                                       |                                              |                                              |                                                                                  |
+| STATUS ENQUIRY                                                       | 13.3.6                                | ITU-T H.248 Audit Value, Audit Descriptor    | Not applicable                               | Request of status conditions in AN                                               |
+| STATUS                                                               | 13.3.5                                | Not applicable                               | TRANSACTION REPLY                            | Report of status conditions in AN                                                |
+| PROTOCOL PARAMETER                                                   | 13.3.9                                | MODIFY                                       | Not applicable                               | Request to change PSTN port parameters (e.g., timer values to detect hook flash) |
+| NOTE – All other values of PSTN protocol message types are reserved. |                                       |                                              |                                              |                                                                                  |
+
+**Table I.2 – Information element identifier coding**
+
+| <b>Name</b>                    | <b>Reference ITU-T G.964 (clause)</b> | <b>Implemented as an event in stimulus analogue line package</b> | <b>Implemented as a signal in stimulus analogue line package</b> | <b>Mapped</b> | <b>Not required</b> |
+|--------------------------------|---------------------------------------|------------------------------------------------------------------|------------------------------------------------------------------|---------------|---------------------|
+| <b>Single octet</b>            |                                       |                                                                  |                                                                  |               |                     |
+| Pulse-notification (Note 1)    | 13.4.6.1                              |                                                                  |                                                                  | X             |                     |
+| Line-information               | 13.4.6.2                              | X                                                                |                                                                  | X             |                     |
+| State                          | 13.4.6.3                              |                                                                  |                                                                  |               | X                   |
+| Autonomous-signalling-sequence | 13.4.6.4                              |                                                                  | X                                                                | X             |                     |
+| Sequence-response              | 13.4.6.5                              | X                                                                |                                                                  | X             |                     |
+| <b>Variable length</b>         |                                       |                                                                  |                                                                  |               |                     |
+| Sequence-number                | 13.4.7.1                              |                                                                  |                                                                  |               | X                   |
+| Cadenced-ringing (Note 2)      | 13.4.7.2                              |                                                                  |                                                                  | X             |                     |
+| Pulsed-signal                  | 13.4.7.3                              | X                                                                | X                                                                | X             |                     |
+| Steady-signal                  | 13.4.7.4                              | X                                                                | X                                                                | X             |                     |
+| Digit-signal                   | 13.4.7.5                              | X                                                                | X                                                                | X             |                     |
+| Recognition-time               | 13.4.7.6                              | X                                                                |                                                                  | X             |                     |
+| Enable-autonomous-acknowledge  | 13.4.7.7                              | X                                                                |                                                                  | X             |                     |
+| Disable-autonomous-acknowledge | 13.4.7.8                              | X                                                                |                                                                  | X             |                     |
+
+**Table I.2 – Information element identifier coding**
+
+| <b>Name</b>                                                                                                                                                                                                                                                                                                           | <b>Reference<br/>ITU-T G.964<br/>(clause)</b> | <b>Implemented<br/>as an event in<br/>stimulus<br/>analogue line<br/>package</b> | <b>Implemented<br/>as a signal in<br/>stimulus<br/>analogue line<br/>package</b> | <b>Mapped</b> | <b>Not<br/>required</b> |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------|---------------|-------------------------|
+| Cause                                                                                                                                                                                                                                                                                                                 | 13.4.7.9                                      |                                                                                  | Covered by<br>ITU-T H.248<br>Error Codes.                                        | X             |                         |
+| Resource-unavailable                                                                                                                                                                                                                                                                                                  | 13.4.7.10                                     |                                                                                  | Covered by<br>ITU-T H.248<br>Error Codes.                                        | X             |                         |
+| Enable-metering (Note 3)                                                                                                                                                                                                                                                                                              | 13.4.7.11                                     |                                                                                  |                                                                                  | X             |                         |
+| Metering-report (Note 3)                                                                                                                                                                                                                                                                                              | 13.4.7.12                                     |                                                                                  |                                                                                  | X             |                         |
+| Attenuation                                                                                                                                                                                                                                                                                                           | 13.4.7.13                                     |                                                                                  | Covered by<br>TDM Circuit<br>Package                                             | X             |                         |
+| NOTE 1 – Covered by the ITU-T H.248.1 Generic package and "signal completion" event.<br>NOTE 2 – Covered by the ITU-T H.248.23 Enhanced Alerting package and "ring" signal.<br>NOTE 3 – Covered by the ITU-T H.248.26 Automatic Metering package.<br>NOTE 4 – All other Information Element Name values are reserved. |                                               |                                                                                  |                                                                                  |               |                         |
+
+## Bibliography
+
+- [b-SSPE/SPEC/001-1] SSPE/SPEC/001-1 V5 (1998), *UK PSTN Mapping Requirements*, (Issue 2, July), Network Interoperability Consultative Committee, Office of Telecommunications (Ofcom), London.
+
+
+
+## **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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.36-201303-I_PDF-E/raw.md b/marked/H/T-REC-H.248.36-201303-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..6ea3991dd985b5c9a70bc0b4c3103a8dd051c74e
--- /dev/null
+++ b/marked/H/T-REC-H.248.36-201303-I_PDF-E/raw.md
@@ -0,0 +1,316 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.36**
+
+(03/2013)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+# --- **Gateway control protocol: Hanging Termination Detection package**
+
+Recommendation ITU-T H.248.36
+
+## 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        |
+| <b>Communication procedures</b>                                               | <b>H.240–H.259</b> |
+| 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.36
+
+# Gateway control protocol: Hanging Termination Detection package
+
+## Summary
+
+Recommendation ITU-T H.248.36 describes the Hanging Termination Detection package which is used to determine potential information mismatch in the record of Context and Termination identities between the media gateway controller and the media gateway. It also offers guidance on the action to take once a potential mismatch is detected.
+
+This revision incorporates a clarification as to how a media gateway notifies a media gateway controller of hanging terminations.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group |
+|---------|----------------|------------|-------------|
+| 1.0     | ITU-T H.248.36 | 2005-09-13 | 16          |
+| 2.0     | ITU-T H.248.36 | 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....            | 1    |
+| 5 Hanging Termination Detection package ..... | 1    |
+| 5.1 Properties.....                           | 2    |
+| 5.2 Events .....                              | 2    |
+| 5.3 Signals .....                             | 2    |
+| 5.4 Statistics.....                           | 2    |
+| 5.5 Error codes.....                          | 2    |
+| 5.6 Procedures .....                          | 3    |
+| Appendix I – Applicability statements.....    | 5    |
+| I.1 Applicability .....                       | 5    |
+| I.2 Non-applicability .....                   | 5    |
+
+
+
+# Gateway control protocol: Hanging Termination Detection package
+
+# 1 Scope
+
+This package is used to determine potential information mismatch in the record of Context and Termination identities between media gateway controllers and media gateways for individual terminations, not the MG as a whole (e.g., root termination). It can be applied in such situations as status synchronization of call and bearer, garbage collection for hanging resources, re-synchronization after short disconnection, etc., and cannot be applied in such situations as media inactivity detection, idle bearer detection, re-synchronization after long disconnection or system reboot, auditing for hanging resources, etc. It also offers guidance on the action to take once a potential mismatch is detected.
+
+# 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.8] Recommendation ITU-T H.248.8 (2013), *Gateway control protocol: Error code and service change reason description*.
+
+# 3 Definitions
+
+This Recommendation defines the following term:
+
+**3.1 hanging termination:** Every ITU-T H.248 termination has an associated record of Termination information. There are consequently two corresponding records at the MGC and MG level. The record of Termination information may be further embedded in a superior record of Context information. There are again corresponding records at the MGC and MG level. If there is a mismatch between corresponding records at the MGC and MG level, a Termination is considered hanging.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+MG Media Gateway
+
+MGC Media Gateway Controller
+
+# 5 Hanging Termination Detection package
+
+**Package name:** Hanging Termination Detection package
+
+**Package ID:** hangterm (0x0098)
+
+**Description:** This package contains an event that generates a periodic Notify message for the MG to determine if an MGC still has a record of the termination that the event is enabled on.
+
+**Version:** 1
+
+**Extends:** None
+
+## 5.1 Properties
+
+None.
+
+## 5.2 Events
+
+### 5.2.1 Termination Heartbeat
+
+**Event name:** Termination Heartbeat
+
+**Event ID:** thb (0x0001)
+
+**Description:** Indicates that (timer x) time has elapsed since the last message exchange between the MGC and MG for the indicated termination.
+
+#### 5.2.1.1 EventDescriptor parameters
+
+##### 5.2.1.1.1 Timer X
+
+**Parameter name:** Timer X
+
+**Parameter ID:** timerx (0x0001)
+
+**Description:** This parameter sets the time period (x) between the last message exchanged and the generation of this event. This timer is reset by any messaging between (including the Notify containing this event) the MGC and MG for the indicated termination. It is recommended to set timerx with a value of a multiple of the typical Context lifetime. The lifetime of the ITU-T H.248 Context is characteristically related to mean call or session holding times of the underlying (tele) service. Timerx is greater than call holding time (timerx >> CHT).
+
+**Type:** Integer
+
+**Optional:** Yes
+
+**Possible values:** 0 No Heartbeat message to be sent  
+1 up Time period in seconds
+
+**Default:** Provisioned
+
+#### 5.2.1.2 ObservedEventsDescriptor parameters
+
+None.
+
+## 5.3 Signals
+
+None.
+
+## 5.4 Statistics
+
+None.
+
+## 5.5 Error codes
+
+None.
+
+## 5.6 Procedures
+
+### 5.6.1 Detection of hanging terminations
+
+For the correct operation of gateways, synchronization of termination information between the MGC and MG is essential for traffic, maintenance and charging purposes. It is also essential to detect any information mismatches as soon as possible to minimize the time hanging terminations are consuming resources that could be used for a chargeable call. ITU-T H.248.1 enables an MGC to perform periodic audits on terminations to see if the terminations are still responding to ITU-T H.248.1 messages. The MGC may issue a wildcard "ALL" audit of termination state but, in large media gateways, this will result in very large messages that are undesirable from a messaging performance point of view. The MGC may issue periodic audits on particular terminations or ranges of terminations that decreases message size but increases the number of messages sent. There is also the danger that the MGC has lost a record of a termination and thus cannot audit it. As a result of the audit, the MGC may detect terminations it did not know existed, or detect that the MG has lost a record of the termination. The action taken is MGC dependent but the likely result is that the termination is subtracted. For terminations that the MGC has lost a record of, the MG is dependent on the MGC detecting its own loss. This may not prove to be 100% reliable.
+
+In the case where the MGC is unable to detect these terminations, the MG needs to be able to detect and clean up terminations that are hanging by sending Notify commands to the MGC identifying the hanging Terminations. The MG can detect hanging terminations by error responses to commands. Typically, during a stable speech call state, very few ITU-T H.248.1 messages are generated by the MG, thus a mechanism is needed to trigger a periodic message from the MG. The MG may issue a periodic Notify command on the concerned termination and check the response to determine if the MGC has a record of the termination or not. The time period for this Notify may be parameter driven.
+
+A Notify response command from an MGC may contain many different errors. However, it is only the error codes listed below that would indicate that there is a problem with information and that there is a potential hanging termination:
+
+- Error Code #: 411 Name: The transaction refers to an unknown ContextID;
+- Error Code #: 430 Name: Unknown TerminationID;
+- Error Code #: 435 Name: Termination ID is not in specified Context.
+
+After generating the Notify Response, action taken by the MGC is dependent on the error code.
+
+### 5.6.2 Use of termination heartbeat
+
+To enable the periodic Notify to be sent, the event "*hangterm/thb*" with the "*timerx*" parameter is set by the MGC or provisioned on the applicable termination. This parameter sets the time period (x) between the last message exchanged and the generation of the "*hangterm/thb*" event. This timer is reset by any messaging between the MGC and MG for the indicated termination (including the Notify containing the event).
+
+A response to this Notify without an error code indicates that the MGC and the MG agree that the context identity / termination identity combination exists.
+
+A response to this Notify containing error codes:
+
+- Error Code #: 411 Name: The transaction refers to an unknown ContextID;
+- Error Code #: 430 Name: Unknown TerminationID;
+- Error Code #: 435 Name: Termination ID is not in specified Context
+
+indicates that there is a potential information mismatch between the MGC and MG. A response to the Notify containing other error codes should be handled according to [ITU-T H.248.8].
+
+On reception of the "*hangterm/thb*" event, the MGC shall be responsible for correcting the mismatch. For example: The MGC may subtract the indicated termination and clear any associated context. The MGC may audit the termination Servicestate to check its records before taking further action.
+
+# Appendix I
+
+## Applicability statements
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## I.1 Applicability
+
+This package is applicable in the following situations (this list is not exhaustive):
+
+- 1) Synchronization of call (MGC) and corresponding bearer (MG) status.
+- 2) Garbage collection for hanging resources, hanging ITU-T H.248 Terminations, hanging ITU-T H.248 contexts.
+
+NOTE 1 – Garbage collection is an important mechanism for high-available, long time running network elements.
+
+- 3) Re-synchronization after (short) temporary losses of MGC-MG interconnection.
+
+NOTE 2 – "Short" here in the sense that all records on MGC and MG level are "almost consistent".
+
+- 4) ITU-T H.248.36 is termination-type independent, therefore applicable for physical and ephemeral terminations.
+- 5) Detection capability of hanging ITU-T H.248 terminations on MGC level.
+- 6) Non-root terminations only.
+
+## I.2 Non-applicability
+
+This package is not applicable (or not intended) in the following situations (this list is not exhaustive):
+
+- 1) Media inactivity detection.
+- 2) Idle bearer detection.
+- 3) Emergency standalone mode.
+- 4) Termination is in state "out-of-service" (according ServiceState property in TerminationState descriptor) (to be checked).
+- 5) Re-synchronization after (long) losses of MGC-MG interconnection, or cold reboots of ITU-T H.248 systems (this is tackled rather by service change and auditing procedures).
+
+NOTE – "Long" here in the sense of data inconsistency between MGC and MG level.
+
+- 6) Addressing potential issues related to bulk auditing.
+- 7) Different or dedicated types of auditing for "detection of hanging resources".
+- 8) Detection capability of hanging ITU-T H.248 terminations on MG level.
+
+
+
+
+
+## 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.37-200806-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.37-200806-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a
--- /dev/null
+++ b/marked/H/T-REC-H.248.37-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.37-200806-I_PDF-E/1c953f32bd34345dfd68fddf8a3736d6_img.jpg b/marked/H/T-REC-H.248.37-200806-I_PDF-E/1c953f32bd34345dfd68fddf8a3736d6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ba5d624316cf0d330de35154f23e4f76e565cb1d
--- /dev/null
+++ b/marked/H/T-REC-H.248.37-200806-I_PDF-E/1c953f32bd34345dfd68fddf8a3736d6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d66ffd462f98049615b59a532d71569bd409ef0f89a1350532f9ebe31717b8ea
+size 109210
diff --git a/marked/H/T-REC-H.248.37-200806-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/H/T-REC-H.248.37-200806-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fb89805a45a786149d6745532ed976a7f98392ca
--- /dev/null
+++ b/marked/H/T-REC-H.248.37-200806-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:154e8673fb6cd2ac6b0436da99434e927cc7294d649bcc8071892f9568e5091b
+size 55638
diff --git a/marked/H/T-REC-H.248.37-200806-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/H/T-REC-H.248.37-200806-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f8bc6d2e83a129c00ab081e37f39e597d13a0ee2
--- /dev/null
+++ b/marked/H/T-REC-H.248.37-200806-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:967f93df311b822b1f802e0c7612c0ab83f12f05e40c0c1a147fcd360daa788f
+size 51793
diff --git a/marked/H/T-REC-H.248.39-201410-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.248.39-201410-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..22dc7ff0fb30f976cc1e576c45d2b7e65fa5ddc7
--- /dev/null
+++ b/marked/H/T-REC-H.248.39-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.39-201410-I_PDF-E/raw.md b/marked/H/T-REC-H.248.39-201410-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..f41adf5492862cdc8f6e3cf86157b7f2cf296704
--- /dev/null
+++ b/marked/H/T-REC-H.248.39-201410-I_PDF-E/raw.md
@@ -0,0 +1,1135 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.39**
+
+(10/2014)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+---
+
+**Gateway control protocol: ITU-T H.248 SDP  
+parameter identification and wildcarding**
+
+Recommendation ITU-T H.248.39
+
+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.
+
+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        |
+| <b>Communication procedures</b>                                                        | <b>H.240–H.259</b> |
+| 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.39
+
+## Gateway control protocol: ITU-T H.248 SDP parameter identification and wildcarding
+
+# Summary
+
+Recommendation ITU-T H.248.39 describes the principles used to identify a single session description protocol (SDP) sub-field and how to apply wildcarding to that sub-field. The sub-field may be fully specified, wildcarded (CHOOSE "\$" or ALL "\*") or not significant "-". Being able to identify a single sub-field is of use when requesting the media gateway (MG) to choose a parameter, specifying a range or for the purposes of auditing. Further specification of how SDP can be wildcarded will assist in interoperation between a media gateway controller (MGC) and an MG.
+
+This revision incorporates guidelines for the wildcarding of source-specific media attributes. It also includes a package to indicate MG support for advanced wildcarding procedures that allow a MGC to request multiple SDP parameter values and/or multiple SDP lines to be returned in response to a CHOOSE request. Additionally, it allows the linking of multiple CHOOSE wildcards so that they return the same value. Furthermore, a new maintain value wildcard is introduced to allow the retention of a previously set value to avoid repetition of redundant information.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T H.248.39 | 2006-05-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/8819">11.1002/1000/8819</a>   |
+| 2.0     | ITU-T H.248.39 | 2014-10-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12236">11.1002/1000/12236</a> |
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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    |
+| 4          | Abbreviations and acronyms .....                                         | 1    |
+| 5          | ITU-T H.248 wildcarding guiding principles .....                         | 2    |
+| 5.1        | General ITU-T H.248 wildcarding principles .....                         | 2    |
+| 5.2        | Specific wildcarding principles for ITU-T H.248 embedded SDP .....       | 2    |
+| 6          | Identification of single parameters .....                                | 3    |
+| 6.1        | Protocol version.....                                                    | 3    |
+| 6.2        | Owner/Creator .....                                                      | 4    |
+| 6.3        | Session name .....                                                       | 4    |
+| 6.4        | URI of description .....                                                 | 5    |
+| 6.5        | Email address.....                                                       | 5    |
+| 6.6        | Phone number.....                                                        | 6    |
+| 6.7        | Encryption key.....                                                      | 6    |
+| 6.8        | Time description.....                                                    | 7    |
+| 6.9        | Repeat.....                                                              | 7    |
+| 6.10       | Time zone adjustments .....                                              | 8    |
+| 6.11       | Media description .....                                                  | 8    |
+| 6.12       | Media title and session information .....                                | 9    |
+| 6.13       | Connection information.....                                              | 10   |
+| 6.14       | Bandwidth information.....                                               | 10   |
+| 6.15       | Attributes .....                                                         | 11   |
+| 7          | Use for wildcarding (CHOOSE or ALL).....                                 | 20   |
+| 8          | Use in auditing .....                                                    | 21   |
+| 8.1        | Audit value .....                                                        | 21   |
+| 8.2        | Audit capability .....                                                   | 22   |
+| 9          | Advanced SDP Wildcarding Package .....                                   | 22   |
+| 9.1        | Properties.....                                                          | 22   |
+| 9.2        | Events .....                                                             | 23   |
+| 9.3        | Signals .....                                                            | 23   |
+| 9.4        | Statistics.....                                                          | 23   |
+| 9.5        | Error codes.....                                                         | 23   |
+| 9.6        | Procedures .....                                                         | 23   |
+| Appendix I | – Example signalling scenarios for the maintain value wildcard "~" ..... | 28   |
+| I.1        | Purpose .....                                                            | 28   |
+
+|                   | <b>Page</b>                                                 |
+|-------------------|-------------------------------------------------------------|
+| I.2               | Signalling without the maintain value wildcard "~" ..... 28 |
+| I.3               | Signalling using the maintain value wildcard "~" ..... 31   |
+| I.4               | Evaluation of the examples ..... 33                         |
+| Bibliography..... | 34                                                          |
+
+# Recommendation ITU-T H.248.39
+
+## Gateway control protocol: ITU-T H.248 SDP parameter identification and wildcarding
+
+# 1 Scope
+
+This Recommendation describes the principles to be used to identify a single session description protocol (SDP) sub-field and how to apply wildcarding to that sub-field. The sub-field may be fully specified, wildcarded (CHOOSE "\$" or ALL "\*") or not significant "-" (see clause 5.2.2.2). Being able to identify a single sub-field is of use when requesting the MG to choose a parameter, specifying a range or for the purposes of auditing.
+
+This Recommendation contains a package that allows a media gateway controller (MGC) to request multiple SDP parameter values and/or multiple SDP lines to be returned in response to a CHOOSE request. It also allows the linking of multiple CHOOSE wildcards so that they return the same value. A new "maintain value" wildcard, "~", is introduced, which is a short notation syntax (versus the fully specified SDP information) that allows performance optimization as well as the reduction of syntax errors (by avoiding the repetition of redundant 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.
+
+[ITU-T H.248.1] Recommendation ITU-T H.248.1 (2013), *Gateway control protocol: Version 3*.
+
+[ITU-T H.248.15] Recommendation ITU-T H.248.15 (2013), *Gateway control protocol: SDP H.248 package attribute*.
+
+# 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:
+
+|      |                                   |
+|------|-----------------------------------|
+| ABNF | Augmented Backus–Naur Form        |
+| ATM  | Asynchronous Transfer Mode        |
+| DTLS | Datagram Transport Layer Security |
+| FFS  | For further study                 |
+| IP   | Internet Protocol                 |
+
+|       |                                       |
+|-------|---------------------------------------|
+| LD    | Local Descriptor                      |
+| MG    | Media Gateway                         |
+| MGC   | Media Gateway Controller              |
+| MIME  | Multipurpose Internet Mail Extensions |
+| RD    | Remote Descriptor                     |
+| RTCP  | RTP Control Protocol                  |
+| RTP   | Real-time Transport Protocol          |
+| SDP   | Session Description Protocol          |
+| SSRC  | Synchronization Source                |
+| TLS   | Transport Layer Security              |
+| UDP   | User Datagram Protocol                |
+| VoATM | Voice over ATM                        |
+| VoIP  | Voice over IP                         |
+
+# 5 ITU-T H.248 wildcarding guiding principles
+
+## 5.1 General ITU-T H.248 wildcarding principles
+
+The overriding guidance provided by clause 7.1.8.1.1.1 of [ITU-T H.248.1] on the use of CHOOSE in the session description protocol (SDP) is: "the use of CHOOSE is allowed in place of a single parameter value".
+
+Subsequent principles are:
+
+- 1) In any SDP scheme each mandatory element SHALL therefore be represented by a single CHOOSE "S".
+- 2) Any part that contain text tokens (e.g., those in " ") that are mandatory SHALL also be included in the wildcard command.
+- 3) Optional parts of an SDP scheme should not be included unless the wildcard or value applies to them.
+- 4) When an item specifies a wildcard for a single sub-field, this applies to the nested augmented Backus–Naur form (ABNF) in that parameter.
+
+## 5.2 Specific wildcarding principles for ITU-T H.248 embedded SDP
+
+### 5.2.1 IETF SDP wildcards
+
+The core SDP [b-IETF RFC 2327], as well as its successor [b-IETF RFC 4566], does *not* specify any wildcards. SDP lines are therefore always *fully specified*.
+
+[b-ITU-T H.248.49] provides, *inter alia*, complementary information concerning relationship and usage of ITU-T H.248 and the various IETF RFCs on SDP.
+
+### 5.2.2 SDP wildcards introduced by specifications other than ITU-T H.248.1
+
+Wildcards are used (by the MGC) for *resource management* and/or the indication of particular *modes of operation* at the MG bearer level (aware versus agnostic). The scope of SDP wildcards in ITU-T H.248 messages is therefore limited to SDP media descriptions (see clause 7.1.8.1.1.2 of [ITU-T H.248.1]), within the Local Descriptor (LD) and the Remote Descriptor (RD).
+
+#### 5.2.2.1 Wildcard "-"
+
+Wildcard "-", meaning "not significant" (or "agnostic", "unaware"), was introduced (in 2005) by the so-called "H.248 Ia profile version 1" (see clause 5.15 of [b-ETSI ES 283 018]), motivated by control needs in dedicated "IP-to-IP interworking modes" in border gateways (see clause G.2.2 of [b-ETSI TR 183 068]).
+
+#### 5.2.2.2 Wildcards "r", "l" and "[0-F]"
+
+This Recommendation introduces the wildcarded value response "r", line response "l", interlinkage "[0-F]" and the maintain value "~" wildcards via the "Advanced SDP Wildcarding Package" (see clause 9).
+
+# 6 Identification of single parameters
+
+The clauses below define which parts of the SDP are classified as "single sub-fields (values)" for the purposes of ITU-T H.248.1 wildcarding. Each of these sub-fields may be fully specified, designated as CHOOSE "\$", designated as ALL "\*" or designated as not significant "-". The sub-fields should not be partially wildcarded.
+
+Each of the examples indicates what type of wildcarding is not valid. It also highlights some valid types of wildcarding and what should be returned.
+
+NOTE 1 – For the purposes of the examples below, "?" is used to denote the potential wildcards:
+
+- "\$" CHOOSE,
+- "\*" ALL,
+- "-" "not significant". (See Note 2 below)
+
+NOTE 2 – Not to be confused with clause B.2 of [ITU-T H.248.1] encoding for NULL Context (see also clause 5.2.2.2).
+
+ABNF grammar, in subsequent clauses, is copied from Appendix A (SDP Grammar) of [b-IETF RFC 2327] and other IETF RFCs concerning SDP extensions.
+
+NOTE 3 – Even though [b-IETF RFC 2327] is replaced by clause 9 of [b-IETF RFC 4566]), references to [b-IETF RFC 2327] have been used because [ITU-T H.248.1] specifies the use of this RFC for SDP.
+
+## 6.1 Protocol version
+
+Table 6-1 – Protocol version
+
+|                                                                   |                                                                                                |
+|-------------------------------------------------------------------|------------------------------------------------------------------------------------------------|
+| <b>SDP Specification:</b>                                         |                                                                                                |
+| <b>Definition:</b><br>(Clause 6 of [b-IETF RFC 2327])             | v= (protocol version)                                                                          |
+| <b>ABNF:</b><br>(Appendix A of [b-IETF RFC 2327])                 | proto-version = "v=" 1*DIGIT CRLF                                                              |
+| <b>ITU-T H.248/SDP encoding example with applied wildcarding:</b> | Result:                                                                                        |
+| v=?                                                               | Is valid. It would give<br>v= 1*DIGIT<br>The only parameter that may be wildcarded is 1*DIGIT. |
+
+## 6.2 Owner/Creator
+
+**Table 6-2 – Owner/Creator**
+
+| <b>SDP Specification:</b>                                                                                            |                                                                                                                                                                                           |
+|----------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 6 of [b-IETF RFC 2327])                                                                | <code>o= (owner/creator and session identifier)</code>                                                                                                                                    |
+| <b>ABNF:</b><br>(Appendix A of [b-IETF RFC 2327])                                                                    | <code>origin-field = "o=" username space<br/>                  sess-id space sess-version space<br/>                  nettype space addrtype space<br/>                  addr CRLF</code> |
+| <b>ITU-T H.248/SDP encoding examples with applied wildcarding:</b>                                                   | <b>Results:</b>                                                                                                                                                                           |
+| <code>o=?</code><br><code>o=? ?</code><br><code>o=? ? ?</code><br><code>o=? ? ? ?</code><br><code>o=? ? ? ? ?</code> | Are all invalid. There are six mandatory parameters: "username", "sess-id", "sess-version", "nettype", "addrtype" and "addr".                                                             |
+| <code>o=? ? ? ? ? ?</code>                                                                                           | Would return:<br><code>o=username sess-id sess-version<br/>nettype addrtype addr</code>                                                                                                   |
+
+## 6.3 Session name
+
+**Table 6-3 – Session name**
+
+| <b>SDP Specification:</b>                                         |                                                                                                        |
+|-------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 6 of [b-IETF RFC 2327])             | <code>s= (session name)</code>                                                                         |
+| <b>ABNF:</b><br>(Appendix A of [b-IETF RFC 2327])                 | <code>session-name-field = "s=" text CRLF</code>                                                       |
+| <b>ITU-T H.248/SDP encoding example with applied wildcarding:</b> | <b>Result:</b>                                                                                         |
+| <code>s=?</code>                                                  | Is valid. It would give<br><code>s=text</code><br>The only parameter that may be wildcarded is "text". |
+
+## 6.4 URI of description
+
+**Table 6-4 – URI of Description**
+
+| <b>SDP Specification:</b>                                         |                                                                                 |
+|-------------------------------------------------------------------|---------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 6 of [b-IETF RFC 2327])             | <code>u=* (URI of description)</code>                                           |
+| <b>ABNF:</b><br>(Appendix A of [b-IETF RFC 2327])                 | <code>uri-field = ["u=" uri CRLF]<br/>uri= ;defined in [b-IETF RFC 1630]</code> |
+| <b>ITU-T H.248/SDP encoding example with applied wildcarding:</b> | <b>Result:</b>                                                                  |
+| FFS.                                                              | –                                                                               |
+
+## 6.5 Email address
+
+**Table 6-5 – Email address**
+
+| <b>SDP Specification:</b>                                         |                                                                                                                                                                                                             |
+|-------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 6 of [b-IETF RFC 2327])             | <code>e=* (email address)</code>                                                                                                                                                                            |
+| <b>ABNF:</b><br>(Appendix A of [b-IETF RFC 2327])                 | <code>email-fields = *("e=" email-address CRLF)<br/>email-address = email   email "(" email-safe ")"  <br/>                  email-safe "&lt;" email "&gt;"<br/>email = ;defined in [b-IETF RFC 822]</code> |
+| <b>ITU-T H.248/SDP encoding example with applied wildcarding:</b> | <b>Result:</b>                                                                                                                                                                                              |
+| FFS.                                                              | –                                                                                                                                                                                                           |
+
+## 6.6 Phone number
+
+**Table 6-6 – Phone number**
+
+| <b>SDP Specification:</b>                                         |                                                                                                                                                                                                                                                            |
+|-------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 6 of [b-IETF RFC 2327])             | <code>p=* (phone number)</code>                                                                                                                                                                                                                            |
+| <b>ABNF:</b><br>(Appendix A of [b-IETF RFC 2327])                 | <code>phone-fields = *( "p=" phone-number CRLF )</code><br><code>phone-number = phone   phone "(" email-safe ")"  </code><br><code>                  email-safe "&lt;" phone "&gt;"</code><br><code>phone = "+" POS-DIGIT 1*( space   "-"   DIGIT )</code> |
+| <b>ITU-T H.248/SDP encoding example with applied wildcarding:</b> | <b>Result:</b>                                                                                                                                                                                                                                             |
+| FFS.                                                              | –                                                                                                                                                                                                                                                          |
+
+## 6.7 Encryption key
+
+**Table 6-7 – Encryption key**
+
+| <b>SDP Specification:</b>                                          |                                                                                                                                                                                                                                                                                                                                     |
+|--------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 6 of [b-IETF RFC 2327])              | <code>k=* (encryption key)</code>                                                                                                                                                                                                                                                                                                   |
+| <b>ABNF:</b><br>(Appendix A of [b-IETF RFC 2327])                  | <code>key-field = [ "k=" key-type CRLF ]</code><br><code>key-type = "prompt"  </code><br><code>              "clear:" key-data  </code><br><code>              "base64:" key-data  </code><br><code>              "uri:" uri</code><br><code>key-data = email-safe   "~"   "</code><br><br>There is one mandatory field "key-type". |
+| <b>ITU-T H.248/SDP encoding examples with applied wildcarding:</b> | <b>Results:</b>                                                                                                                                                                                                                                                                                                                     |
+| <code>k=?</code>                                                   | Would give<br><code>k=key-type</code>                                                                                                                                                                                                                                                                                               |
+| <code>k=? :</code>                                                 | Would give<br><code>k=key-type:key-data</code><br>where key-type is "clear" or "base64",<br><code>k=key-type:uri</code><br>where key-type is "uri".                                                                                                                                                                                 |
+
+## 6.8 Time description
+
+Table 6-8 – Time description
+
+| SDP Specification:                                                |                                                                                                             |
+|-------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 6 of [b-IETF RFC 2327])             | t= (time the session is active)                                                                             |
+| <b>ABNF:</b><br>(Appendix A of [b-IETF RFC 2327])                 | time-fields = 1*( "t=" start-time space stop-time<br>*(CRLF repeat-fields) CRLF)<br>[zone-adjustments CRLF] |
+| <b>ITU-T H.248/SDP encoding examples with applied wildcoding:</b> | <b>Results:</b>                                                                                             |
+| t=?                                                               | Is invalid. There are two mandatory parameters "start-time" and "stop-time".                                |
+| t=? ?                                                             | Would give<br>t=start-time stop-time                                                                        |
+| NOTE – For repeat-fields and zone-adjustments see below.          |                                                                                                             |
+
+## 6.9 Repeat
+
+Table 6-9 – Repeat
+
+| SDP Specification:                                                |                                                                                    |
+|-------------------------------------------------------------------|------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 6 of [b-IETF RFC 2327])             | r=* (zero or more repeat times)                                                    |
+| <b>ABNF:</b><br>(Appendix A of [b-IETF RFC 2327])                 | repeat-fields = "r=" repeat-interval space typed-time<br>1*(space typed-time)      |
+| <b>ITU-T H.248/SDP encoding examples with applied wildcoding:</b> | <b>Results:</b>                                                                    |
+| r=?                                                               | Is invalid. There are two mandatory parameters "repeat-interval" and "typed-time". |
+| r=? :                                                             | Would give<br>r=repeat-interval typed-time                                         |
+| r=? ? ?                                                           | Would give<br>r=repeat-interval typed-time<br>typed-time                           |
+
+## 6.10 Time zone adjustments
+
+Table 6-10 – Time zone adjustments
+
+| SDP Specification:                                                                  |                                                                                                                                                                             |
+|-------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 6 of [b-IETF RFC 2327])                               | <code>z=* (time zone adjustments)</code>                                                                                                                                    |
+| <b>ABNF:</b><br>(Appendix A of [b-IETF RFC 2327])                                   | <code>zone-adjustments = time space ["-"] typed-time<br/>                          *(space time space ["-"] typed-time)</code>                                              |
+| ITU-T H.248/SDP encoding examples<br>with applied wildcarding:                      | Results:                                                                                                                                                                    |
+| <code>z=?</code><br><code>z=? -</code><br><code>z=-?</code><br><code>z=? ? ?</code> | Are invalid.<br>There are two mandatory parameters "time" and "typed-time". These two parameters can be grouped multiple times thus an odd number of wildcards are invalid. |
+| <code>z=? ?</code>                                                                  | Would give<br><code>z=time typed-time</code>                                                                                                                                |
+| <code>z=? -?</code>                                                                 | Would give<br><code>z=time -typed-time</code>                                                                                                                               |
+| <code>z=? ? ? ?</code>                                                              | Would give<br><code>z=time typed-time time typed-time</code>                                                                                                                |
+
+## 6.11 Media description
+
+Table 6-11 – Media description
+
+| SDP Specification:                                                                                             |                                                                                                                                                     |
+|----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 6 of [b-IETF RFC 2327])                                                          | <code>m= (media name and transport address)</code>                                                                                                  |
+| <b>ABNF:</b><br>(Appendix A of [b-IETF RFC 2327])                                                              | <code>media-field = "m=" media space port ["/" integer]<br/>                  space proto 1*(space fmt) CRLF</code>                                 |
+| ITU-T H.248/SDP encoding examples<br>with applied wildcarding:                                                 | Results:                                                                                                                                            |
+| <code>m=?</code><br><code>m=? ?</code><br><code>m=? ?/?</code><br><code>m=? /?</code><br><code>m=? /? ?</code> | Are invalid.<br>There are four mandatory parameters "media", "port", "proto" and "fmt" and one optional parameter "integer" that may be wildcarded. |
+| <code>m=? ? ? ?</code>                                                                                         | Would give<br><code>m=media port proto fmt</code>                                                                                                   |
+| <code>m=? ?/? ? ?</code>                                                                                       | Would give<br><code>m=media port/integer proto fmt</code>                                                                                           |
+
+**Table 6-11 – Media description**
+
+| <b>SDP Specification:</b>    |                                                                                                                                                                       |
+|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>m=? ? ? ? ? ?</code>   | Would give<br><pre>m=media port proto fmt fmt</pre> This example is considering an "m=" line with multiple (here two) payload formats. See also clause 6.15.7         |
+| <code>m=? ?/? ? ? ? ?</code> | Would give<br><pre>m=media port/integer proto fmt fmt</pre> This example is considering an "m=" line with multiple (here two) payload formats. See also clause 6.15.7 |
+
+## **6.12 Media title and session information**
+
+**Table 6-12 – Media title and session information**
+
+| <b>SDP Specification:</b>                                          |                                                                   |
+|--------------------------------------------------------------------|-------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 6 of [b-IETF RFC 2327])              | <code>i=* (media title)</code>                                    |
+| <b>ABNF:</b><br>(Appendix A of [b-IETF RFC 2327])                  | <code>information-field = ["i=" text CRLF]</code>                 |
+| <b>ITU-T H.248/SDP encoding examples with applied wildcarding:</b> | <b>Results:</b>                                                   |
+| <code>i=?</code>                                                   | Is valid.<br>The only parameter that may be wildcarded is "text". |
+| <code>i=?</code>                                                   | Would give<br><pre>z i=text</pre>                                 |
+
+## 6.13 Connection information
+
+**Table 6-13 – Connection information**
+
+| <b>SDP Specification:</b>                                         |                                                                                                                             |
+|-------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 6 of [b-IETF RFC 2327])             | <code>c=* (connection information - optional if included at session-level)</code>                                           |
+| <b>ABNF:</b><br>(Appendix A of [b-IETF RFC 2327])                 | <code>connection-field = ["c="] nettype space addrtype space connection-address CRLF</code>                                 |
+| <b>ITU-T H.248/SDP encoding examples with applied wildcoding:</b> | <b>Results:</b>                                                                                                             |
+| <code>c=?</code><br><code>c=? ?</code>                            | Are invalid.<br>There are three mandatory parameters "nettype", "addrtype" and "connection-address" which may be wildcoded. |
+| <code>c=? ? ?</code>                                              | Would give<br><code>c=nettype addrtype connection-address</code>                                                            |
+
+## 6.14 Bandwidth information
+
+**Table 6-14 – Bandwidth information**
+
+| <b>SDP Specification:</b>                                         |                                                                                                                                     |
+|-------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 6 of [b-IETF RFC 2327])             | <code>b=* (bandwidth information)</code>                                                                                            |
+| <b>ABNF:</b><br>(Appendix A of [b-IETF RFC 2327])                 | <code>bandwidth-fields = *("b=" btype ":" bandwidth CRLF)</code>                                                                    |
+| <b>ITU-T H.248/SDP encoding examples with applied wildcoding:</b> | <b>Results:</b>                                                                                                                     |
+| <code>b=?</code>                                                  | Is invalid, as ? is only for one parameter value.<br>There are two mandatory values "btype" and "bandwidth" which may be wildcoded. |
+| <code>b=? : ?</code>                                              | Would give<br><code>b=btype:bandwidth</code>                                                                                        |
+
+## 6.15 Attributes
+
+**Table 6-15 – Attributes**
+
+| <b>SDP Specification:</b>                                          |                                                                                                                                                                                                                                                                                            |
+|--------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 6 of [b-IETF RFC 2327])              | <code>a=* (zero or more media attribute lines)</code>                                                                                                                                                                                                                                      |
+| <b>ABNF:</b><br>(Appendix A of [b-IETF RFC 2327])                  | <code>attribute-fields = *("a=" attribute CRLF)</code><br><code>attribute = (att-field ":" att-value)   att-field</code>                                                                                                                                                                   |
+| <b>ITU-T H.248/SDP encoding examples with applied wildcarding:</b> | <b>Results:</b>                                                                                                                                                                                                                                                                            |
+| <code>a=?:</code><br><code>a=? ?</code>                            | Is invalid.<br>There is one mandatory parameter "att-field" and one optional parameter "att-value".                                                                                                                                                                                        |
+| <code>a=?</code>                                                   | Would give<br><code>a=att-field</code><br>This will only wildcard a single "a=value", e.g., "a=recvonly" or "a=sendrecv" or "a=sendonly".                                                                                                                                                  |
+| <code>a=??:</code>                                                 | Would give<br><code>a=att-field:att-value</code><br>Depending on the value of the first parameter it may not be valid to wildcard the second value. The "att-value" field shall return all the mandatory parameters and may return the optional parameters associated with attribute type. |
+| <code>a=rtpmap:?</code>                                            | Should at least give:<br><code>a=rtpmap:payload</code><br><code>encodingname/clockrate</code><br>and may give:<br><code>a=rtpmap:payload</code><br><code>encodingname/clockrate</code><br><code>encodingparameters</code>                                                                  |
+
+Where multiple attributes of the same type are sent by the MGC, it should fully specify at least one of the parameters to uniquely identify the instance of the attribute, for example, the payload type in the rtpmap attribute.
+
+For a description of wildcarding various "att-value" parameters, see the clauses below.
+
+### 6.15.1 RTP map
+
+Table 6-15.1 – RTP map
+
+| SDP Specification:                                                                                                     |                                                                                                                                                     |
+|------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 6 of [b-IETF RFC 2327])                                                                  | –                                                                                                                                                   |
+| <b>ABNF:</b><br>(Appendix A of [b-IETF RFC 2327])                                                                      | <code>a=rtpmap:&lt;payload type&gt; &lt;encoding name&gt;/&lt;clock rate&gt;[/&lt;encodingparameters&gt;]</code>                                    |
+| <b>ITU-T H.248/SDP encoding examples with applied wildcarding:</b>                                                     | <b>Results:</b>                                                                                                                                     |
+| <code>a=rtpmap:? ?</code><br><code>a=rtpmap:? ?/</code><br><code>a=rtpmap:? ? ?</code><br><code>a=rtpmap:? ?//?</code> | Are invalid.<br>There are three mandatory parameters "payload type", "encoding name", "clock rate" and one optional parameter "encodingparameters". |
+| <code>a=rtpmap:? ?/?</code>                                                                                            | Would give<br><code>a=rtpmap:payloadtype<br/>encodingname/clockrate</code>                                                                          |
+| <code>a=rtpmap:? ?/?/?</code>                                                                                          | Would give<br><code>a=rtpmap:payloadtype<br/>encodingname/clockrate/encoding<br/>parameters</code>                                                  |
+
+### 6.15.2 Packetization time
+
+Table 6-15.2 – Packetization time
+
+| SDP Specification:                                                |                                                                                             |
+|-------------------------------------------------------------------|---------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 6 of [b-IETF RFC 2327])             | –                                                                                           |
+| <b>ABNF:</b><br>(Appendix A of [b-IETF RFC 2327])                 | <code>a=ptime:&lt;packet time&gt;</code><br>There is one mandatory parameter "packet time". |
+| <b>ITU-T H.248/SDP encoding example with applied wildcarding:</b> | <b>Result:</b>                                                                              |
+| <code>a=ptime:?</code>                                            | Would give<br><code>a=ptime:packettime</code>                                               |
+
+### 6.15.3 Parameter format
+
+Table 6-15.3 – Parameter format
+
+| SDP Specification:                                                 |                                                                                             |
+|--------------------------------------------------------------------|---------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 6 of [b-IETF RFC 2327])              | –                                                                                           |
+| <b>ABNF:</b><br>(Appendix A of [b-IETF RFC 2327])                  | <code>a=fmtp:&lt;format&gt; &lt;format specific parameters&gt;</code>                       |
+| <b>ITU-T H.248/SDP encoding examples with applied wildcarding:</b> | <b>Results:</b>                                                                             |
+| <code>a=fmtp:?</code>                                              | Is invalid as there are two mandatory parameters "format" and "format specific parameters". |
+| <code>a=fmtp: ? ?</code>                                           | Would give<br><code>a=fmtp:format<br/>formatspecificparameters</code>                       |
+
+### 6.15.4 Path
+
+Table 6-15.4 – Path
+
+| SDP Specification:                                                 |                                                                                                                              |
+|--------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 6 of [b-IETF RFC 2327])              | –                                                                                                                            |
+| <b>ABNF:</b><br>(Appendix A of [b-IETF RFC 2327])                  | <code>a=path:" MSRP-URL *(SP MSRP-URL)<br/>msrp-scheme"://"[userinfo "@"] hostport ["/" session-id] ";"<br/>transport</code> |
+| <b>ITU-T H.248/SDP encoding examples with applied wildcarding:</b> | <b>Results:</b>                                                                                                              |
+| <code>a=path:msrp://?</code>                                       | Is invalid as "?" is only for one parameter value. There are two mandatory values "hostport" and "transport".                |
+| <code>a=path:msrp://?;?</code>                                     | Would give<br><code>a=path:msrp://hostport;transport</code>                                                                  |
+| <code>a=path:msrp://?@?;?</code>                                   | Would give<br><code>a=path:msrp://userinfo@hostport;<br/>transport</code>                                                    |
+| <code>a=path:msrp://?/?;?</code>                                   | Would give<br><code>a=path:msrp://hostport/session-id;<br/>transport</code>                                                  |
+| <code>a=path:msrp://?@?/?;?</code>                                 | Would give<br><code>a=path:msrp://userinfo@hostport/<br/>session-id;transport</code>                                         |
+
+### 6.15.5 SDP ITU-T H.248 package attribute
+
+Table 6-15.5 – SDP ITU-T H.248 package attribute
+
+| SDP Specification:                                                                                                                                          |                                                                                                   |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>([ITU-T H.248.15])                                                                                                                    | –                                                                                                 |
+| <b>ABNF:</b><br>([ITU-T H.248.15])                                                                                                                          | <code>a=h248item:&lt;package name&gt;/&lt;property name&gt; = &lt;value&gt;</code>                |
+| <b>ITU-T H.248/SDP encoding examples with applied wildcarding:</b>                                                                                          | <b>Results:</b>                                                                                   |
+| <code>a=h248item:?</code><br><code>a=h248item:? ?</code><br><code>a=h248item:? ? ?</code><br><code>a=h248item:?/ =?</code><br><code>a=h248item:? ?=?</code> | Are invalid.<br>There are three mandatory parameters "package name", "property name" and "value". |
+| <code>a=h248item:?/?=?</code>                                                                                                                               | Would give<br><code>a=h248item:packagename/<br/>propertyname=value</code>                         |
+
+### 6.15.6 RTCP attribute
+
+Table 6-15.6 – RTCP attribute
+
+| SDP Specification:                                                 |                                                                                                                                                                             |
+|--------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>([b-IETF RFC 3605])                          | –                                                                                                                                                                           |
+| <b>ABNF:</b><br>(Clause 2.1 of [b-IETF RFC 3605])                  | <code>rtcp-attribute = "a=rtcp:" port [nettype space addrtype space connection-address] CRLF</code>                                                                         |
+| <b>ITU-T H.248/SDP encoding examples with applied wildcarding:</b> | <b>Results:</b>                                                                                                                                                             |
+| <code>a=rtcp:? ?</code><br><code>a=rtcp:? ? ?</code>               | Are invalid.<br>There is one mandatory parameter "port". There are three optional parameters "nettype", "addrtype" and "connection-address" but all three must be included. |
+| <code>a=rtcp:?</code>                                              | Would give<br><code>a=rtcp:port</code>                                                                                                                                      |
+| <code>a=rtcp:? ? ? ?</code>                                        | Would give<br><code>a=rtcp:port nettype addrtype<br/>connection-address</code>                                                                                              |
+
+#### 6.15.7 Silence suppression attribute
+
+The "silenceSupp" attribute is defined in clause 5.6.3.2 of [b-IETF RFC 3108]. This attribute may be used for enabling and disabling of silence suppression mode for voice codec types without embedded silence suppression support (e.g., [b-ITU-T G.711] or [b-ITU-T G.726]). This attribute may be also used for non-ATM bearer types like real-time transport protocol (RTP)/UDP/IP.
+
+The "silenceSupp" attribute provides five optional sub-fields for parameterization of the silence suppression function. Their usage may depend on the ephemeral ITU-T H.248 Termination type, e.g., voice over IP (VoIP) may only use the <silenceSuppEnable> sub-field, whereas voice over ATM (VoATM) may use additional sub-fields (see explicit statement in clause 5.6 of [b-IETF RFC 3108]).
+
+**Table 6-15.7 – Silence suppression attribute**
+
+| <b>SDP Specification:</b>                                                            |                                                                                                                                                                                                                                                                                         |
+|--------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 5.6.3.2 of [b-IETF RFC 3108])                          | –                                                                                                                                                                                                                                                                                       |
+| <b>ABNF:</b><br>(Clause 5.6.3.2 of [b-IETF RFC 3108])                                | a=silenceSupp: <silenceSuppEnable> <silenceTimer> <suppPref> <sidUse> <fxnslevel>                                                                                                                                                                                                       |
+| <b>ITU-T H.248/SDP encoding examples with applied wildcarding:</b>                   | <b>Results:</b>                                                                                                                                                                                                                                                                         |
+| a=silenceSupp:?<br>a=silenceSupp:? ?<br>a=silenceSupp:? ? ?<br>a=silenceSupp:? ? ? ? | Are invalid.<br>There are five mandatory parameters "silenceSuppEnable", "silenceTimer", "suppPref", "sidUse" and "fxnslevel".                                                                                                                                                          |
+| a=silenceSupp:? ? ? ? ?                                                              | Would give<br>a=silenceSupp:silenceSuppEnable<br>silenceTimer suppPref sidUse fxnslevel<br>That means that the ITU-T H.248 MG would reply with the default value for "silenceSuppEnable". That default value may, for instance, be defined within an ITU-T H.248 Profile specification. |
+
+#### 6.15.8 Media description with multiple payload types and multiple attribute lines
+
+Clause 6.11 shows a wildcarding example with multiple list entries in <fmt list> in the "m=" line.
+
+The fourth "m=" line parameter, <fmt list>, is a list of one or more payload formats. This clause is considering another wildcarding example with multiple list entries in <fmt list>.
+
+The unambiguous resource selection by the MG may require correspondent "a=" lines in case of wildcarding in the list of formats in the "m=" line. This is reflected in clause 7.1.8 of [ITU-T H.248.1].
+
+NOTE 1 – To avoid ambiguity when requesting the MG to reserve and commit resources, the MGC should supply as much information as needed when using under-specification (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).
+
+Such a wildcarding configuration must therefore consider the combination of a single "m=" and multiple "a=" lines.
+
+NOTE 2 – Clause 6.11 shows examples with scope on "m=" line only.
+
+**Table 6-15.8 – Examples**
+
+| ITU-T H.248/SDP encoding example with applied wildcarding:                                                                                               | Result:                                                                                                                                                           |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ITU-T H.248 request:<br>Local{<br>v=0<br>c=IN IP4 \$<br>m=audio\$ RTP/AVP \$ \$<br>a=rtpmap:\$ G729D/8000<br>a=rtpmap:\$ G726-16/8000<br>a=ptime:10<br>} | ITU-T H.248 reply:<br>Local{<br>v=0<br>c=IN IP4 11.9.19.65<br>m=audio 5000 RTP/AVP 98 99<br>a=rtpmap:98 G729D/8000<br>a=rtpmap:99 G726-16/8000<br>a=ptime:10<br>} |
+
+In this example the MGC specifies the encoding name for the two RTP payload types. Thus the MG cannot choose a different encoding name. If the MGC does not send the "a=" line, the MG could choose the encoding name as well. This latter option is not preferred.
+
+#### 6.15.9 Source-specific media attributes
+
+Source-specific media attributes are defined in [b-IETF RFC 5576]. These attributes may be used to describe *RTP media sources* in SDP, associate attributes with these sources, and express relationships among such traffic sources. [b-IETF RFC 5576] also defines several source-level attributes that can be used to describe properties of media sources.
+
+Structure of [b-IETF RFC 5576] SDP attributes:
+
+- media attributes:
+  - "ssrc" media attribute (see clause 6.15.9.1)
+  - "ssrc-group" media attribute (see clause 6.15.9.2).
+- source attributes:
+  - "cname" source attribute (see clause 6.15.9.1.2)
+  - "previous-ssrc" source attribute (see clause 6.15.9.1.3)
+  - "fmtp" source attribute (see clause 6.15.9.1.4).
+
+##### 6.15.9.1 The "ssrc" media attribute
+
+###### 6.15.9.1.1 ABNF structure
+
+See Table 6-15.9.1.1.
+
+**Table 6-15.9.1.1 – Media attribute "ssrc"**
+
+| SDP Specification:                                      |                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 4.1 of [b-IETF RFC 5576]) | –                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>ABNF:</b><br>(Clause 10 of [b-IETF RFC 5576])        | <pre> a=ssrc:&lt;ssrc-id&gt; &lt;attribute&gt; a=ssrc:&lt;ssrc-id&gt; &lt;attribute&gt;:&lt;value&gt; Formal: ssrc-attr = "ssrc:" ssrc-id SP attribute           ; The base definition of "attribute" is in           [b-IETF RFC 4566].           ; (It is the content of "a=" lines.)           ssrc-id = integer ; 0 .. 2**32 - 1           attribute =/ ssrc-attr         </pre> |
+
+The media attribute "a=ssrc:" must contain an additional source attribute (see next subclauses). The SDP wildcarding is also demonstrated in these clauses.
+
+###### 6.15.9.1.2 Wildcarding with source attribute "cname"
+
+See Table 6-15.9.1.2.
+
+**Table 6-15.9.1.2 – Source-specific attribute "cname"**
+
+|                                                                        |                                                                                                                                                                                                                                                                           |
+|------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>SDP Specification:</b>                                              |                                                                                                                                                                                                                                                                           |
+| <b>Definition:</b><br>(Clause 6.1 of [b-IETF RFC 5576])                | –                                                                                                                                                                                                                                                                         |
+| <b>ABNF:</b><br>(Clause 10 of [b-IETF RFC 5576])                       | a=ssrc:<ssrc-id> cname:<cname><br>Formal:<br>cname-attr = "cname:" cname<br>cname = byte-string ; Following the syntax conventions<br>for CNAME as defined in [b-IETF RFC 3550].<br>; The definition of "byte-string" is in [b-IETF RFC 4566].<br>attribute =/ cname-attr |
+| <b>ITU-T H.248/SDP encoding examples<br/>with applied wildcarding:</b> | <b>Results:</b>                                                                                                                                                                                                                                                           |
+| a=ssrc:<ssrc-id> cname:?                                               | Would give<br>a=ssrc:ssrc-id cname:cname<br>i.e.,<br>MG used CNAME value (typically at the level of<br>root), which is either provisioned or locally<br>generated, based on [b-IETF RFC 6222].                                                                            |
+
+##### 6.15.9.1.3 Wildcarding with source attribute "previous-ssrc"
+
+See Table 6-15.9.1.3.
+
+**Table 6-15.9.1.3 – Source-specific attribute "previous-ssrc"**
+
+|                                                                        |                                                                                                                                                                                        |
+|------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>SDP Specification:</b>                                              |                                                                                                                                                                                        |
+| <b>Definition:</b><br>(Clause 6.2 of [b-IETF RFC 5576])                | –                                                                                                                                                                                      |
+| <b>ABNF:</b><br>(Clause 10 of [b-IETF RFC 5576])                       | a=ssrc:<ssrc-id> previous-ssrc:<ssrc-id> ...<br>Formal:<br>previous-ssrc-attr = "previous-ssrc:" ssrc-id *(SP ssrc-id)<br>attribute =/ previous-ssrc-attr                              |
+| <b>ITU-T H.248/SDP encoding examples<br/>with applied wildcarding:</b> | <b>Results:</b>                                                                                                                                                                        |
+| a=ssrc:?                                                               | Is invalid.                                                                                                                                                                            |
+| a=ssrc:? previous-ssrc:?                                               | Would give<br>a= ssrc: ssrc-id1 previous-ssrc:<br>ssrc-id2, ssrc-id3 ... ssrc-idn<br>The use of a multiple value response wildcard is<br>required to return a list of previous- ssres. |
+
+NOTE – The example above illustrates wildcarding a previous-ssrc value. The use of the previous-ssrc attribute is dependent on SSRC identifier collision leading to an allocation of a new SSRC identifier. The conditions leading to such an occurrence are not in scope of this Recommendation, however, the information below details consideration when using such wildcarding:
+
+Such a use case would involve further procedures. For example:
+
+- 1) The MG notifies the MGC that SSRC collision was detected, e.g., using a new ITU-T H.248 event.
+- 2) The MGC requests the MG to allocate a new local SSRC and includes a wildcarded a=ssrc attribute:  
+
+```
+a=ssrc:$ previous-ssrc:$
+```
+- 3) The MG replies with a new SSRC and with an old SSRC:  
+
+```
+a=ssrc:<new-ssrc-id> previous-ssrc:<old-ssrc-id>
+```
+- 4) The MGC uses the MG's reply to generate a new **SDP offer** containing the MG replied attribute line:  
+
+```
+a=ssrc:<new-ssrc-id> previous-ssrc:<old-ssrc-id>
+```
+
+Variant of step (2):
+
+- 2) The MGC requests the MG to allocate a new local SSRC and includes a **partially** wildcarded a=ssrc attribute:  
+
+```
+a=ssrc:$ previous-ssrc:<old-ssrc-id> (If the MGC stored <old-ssrc-id>)
+```
+
+###### 6.15.9.1.4 Wildcarding with source attribute "fmtp"
+
+See Table 6-15.9.1.4.
+
+**Table 6-15.9.1.4 – Source-specific attribute "fmtp"**
+
+| <b>SDP Specification:</b>                                                  |                                                                                                                                |
+|----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 6.3 of [b-IETF RFC 5576])                    | –                                                                                                                              |
+| <b>ABNF:</b><br>(Clause 10 of [b-IETF RFC 5576])                           | <pre>a=ssrc:&lt;ssrc&gt; fmtp:&lt;format&gt; &lt;format specific parameters&gt;</pre> Formal:<br>Not part of [b-IETF RFC 5576] |
+| <b>ITU-T H.248/SDP encoding examples with applied wildcarding:</b>         | <b>Results:</b>                                                                                                                |
+| <pre>a=ssrc:? fmtp:? ?</pre>                                               | This syntax is valid; however the results would be uncertain. The usage in the following row is preferred.                     |
+| <pre>a=ssrc:? fmtp:&lt;format&gt; &lt;format specific parameters&gt;</pre> | Would give<br><pre>a=ssrc:ssrc-id fmtp:&lt;format&gt; &lt;format specific parameters&gt;</pre>                                 |
+
+#### 6.15.9.2 The "ssrc-group" media attribute
+
+See Table 6-15.9.2.
+
+**Table 6-15.9.2 – Media attribute "ssrc-group"**
+
+| <b>SDP Specification:</b>                               |                                                                                                                                                                                                                                                                          |
+|---------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Definition:</b><br>(Clause 4.2 of [b-IETF RFC 5576]) | –                                                                                                                                                                                                                                                                        |
+| <b>ABNF:</b><br>(Clause 10 of [b-IETF RFC 5576])        | <pre>a=ssrc-group:&lt;semantics&gt; &lt;ssrc-id&gt; ...</pre> Formal:<br><pre>ssrc-group-attr = "ssrc-group:" semantics *(SP ssrc-id)                 semantics = "FEC" / "FID" / token                                 ; Matches [b-IETF RFC 5888] definition and</pre> |
+
+**Table 6-15.9.2 – Media attribute "ssrc-group"**
+
+|                                                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                                                                                                                                 |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>SDP Specification:</b>                                                                                                                                                                                                                                                                               |                                                                                                                                                                                                                                                                                                                 |
+| token<br>attribute                                                                                                                                                                                                                                                                                      | ; IANA registration rules in this doc.<br>= <as defined in [b-IETF RFC 4566]<br>=/ ssrc-group-attr                                                                                                                                                                                                              |
+| <b>ITU-T H.248/SDP encoding examples<br/>with applied wildcarding:</b>                                                                                                                                                                                                                                  | <b>Results:</b>                                                                                                                                                                                                                                                                                                 |
+| a=ssrc-group:? ?<br>a=ssrc-group:? ?R                                                                                                                                                                                                                                                                   | Are invalid.<br>This is because there are semantic limitations concerning the <i>group semantics</i> according to clause 4.2 of [b-IETF RFC 5576]. For example meaningful tokens are "FEC" and "FID", but other tokens such as "LS", "SFR", "ANAT" or "CS" are normally not applicable in this service context. |
+| a=ssrc-group:token ?R (Note)                                                                                                                                                                                                                                                                            | Would give<br>a=ssrc-group:token <i>list of ssrc-ids</i>                                                                                                                                                                                                                                                        |
+| NOTE – This SDP attribute is interlinked with the SDP "ssrc" media attribute (see clause 6.15.9.1). Thus, unambiguous SDP wildcarding requires the usage of the advanced wildcarding capabilities according to clause 9. In particular: the application of wildcarding interlinkage (see clause 9.6.4). |                                                                                                                                                                                                                                                                                                                 |
+
+The wildcarding of "a=ssrc-group" must also consider the relationship to any wildcarding performed on "a=ssrc". An "ssrc" chosen as a result of a CHOOSE wildcard on one attribute may need to be used on another attribute. The wildcarding interlinkage wildcard is used to link the CHOOSE instances. See clause 9.6.4 for more information.
+
+##### **Example**
+
+Wildcarding a=ssrc-group using wildcarding interlinkage in conjunction with [b-IETF RFC 4588] specified multipurpose Internet mail extensions (MIME) subtype *rtx* is as follows:
+
+```
+a=ssrc-group:FID $1 $2
+a=ssrc:$1 cname:$
+a=ssrc:$2 cname:$
+```
+
+Where the MG then allocates one "original stream SSRC" and one "retransmission stream SSRC" and where it returns the "original stream SSRC" in the first a=ssrc attribute lines and the "retransmission stream SSRC" in the second a=ssrc attribute line, for example:
+
+Replied Local Descriptor:
+
+```
+...
+a=ssrc-group:FID <original-stream-SSRC> <retransmission-stream-SSRC>
+a=ssrc:<original-stream-SSRC> cname:<MG-CNAME>
+a=ssrc:<retransmission-stream-SSRC> cname:<MG-CNAME>
+```
+
+See also the example in clause 9.6.4.
+
+### **6.15.10 Fingerprint attribute**
+
+The fingerprint attribute is defined by [b-IETF RFC 4572] and is used for transport security protocols such as transport layer security (TLS) and datagram transport layer security (DTLS).
+
+**Table 6-15.10 – Attribute "fingerprint"**
+
+|                                                                        |                                                                                                                                                 |
+|------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>SDP Specification:</b>                                              |                                                                                                                                                 |
+| <b>Definition:</b><br>(Clause 5 of [b-IETF RFC 4572])                  | –                                                                                                                                               |
+| <b>ABNF:</b><br>(Clause 5 of [b-IETF RFC 4572])                        | <code>a=fingerprint:&lt;hash-func&gt; &lt;fingerprint&gt;</code>                                                                                |
+| <b>ITU-T H.248/SDP encoding examples<br/>with applied wildcarding:</b> | <b>Results:</b>                                                                                                                                 |
+| <code>a=fingerprint:?</code>                                           | Is invalid.<br>This is because both the mandatory 2-tuple of "name of hash function" and "hash value itself need to be individually wildcarded. |
+| <code>a=fingerprint:? ?</code>                                         | Would give<br><code>a=fingerprint:hash-func<br/>fingerprint</code>                                                                              |
+
+##### **6.15.10.1 Examples**
+
+See Table 6-15.10.1.
+
+**Table 6-15.10.1 – Examples for attribute "fingerprint""**
+
+|                                                                        |                                                                                                                                                     |
+|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>ITU-T H.248/SDP encoding examples<br/>with applied wildcarding:</b> | <b>Results:</b>                                                                                                                                     |
+| Example 1:<br>MGC:<br><code>a=fingerprint:\$ \$</code>                 | The MG chooses a hash function and hash value ('fingerprint'), and replies to the MGC, e.g.:<br><code>a=fingerprint: sha-384<br/>fingerprint</code> |
+| Example 2:<br>MGC:<br><code>a=fingerprint:md5 \$</code>                | The MG chooses a hash value for <i>md5</i> algorithm and replies to the MGC, e.g.:<br><code>a=fingerprint:md5 fingerprint</code>                    |
+
+# **7 Use for wildcarding (CHOOSE or ALL)**
+
+The MGC should fully specify as many of the SDP parameters as possible when specifying an SDP line in ITU-T H.248. As indicated above, the MGC shall provide: a fully specified value, wildcard (CHOOSE "\$" or ALL "\*") or not significant value, "-", for each parameter.
+
+For example (see Table 7-1): The MGC requests that the port be selected and issues the transaction below.
+
+NOTE – The full SDP is omitted for brevity.
+
+**Table 7-1 – Examples**
+
+| ITU-T H.248/SDP encoding example with applied wildcarding:                                                                                               | Result:                                                                                                                                                                   |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ITU-T H.248 request:<br>Transaction = 10 {<br>Context = 20 {<br>Modify = 30 {<br>Media {<br>Stream = 1 {<br>Local {<br>m=audio \$ RTP/AVP 4<br>} } } } } | ITU-T H.248 reply (the port is returned):<br>Reply = 10 {<br>Context = 20 {<br>Modify = 30 {<br>Media {<br>Stream = 1 {<br>Local {<br>m=audio 1111 RTP/AVP 4<br>} } } } } |
+
+# 8 Use in auditing
+
+## 8.1 Audit value
+
+Individual auditing of Local and Remote SDPs was introduced in [ITU-T H.248.1] Version 3.
+
+For use in auditing, the MGC should fully specify as many of the parameters in the SDP line as possible, to minimize the number of combinations that are returned. The actual parameters that the MGC requests to be returned should be designated with the ALL, "\*", wildcard. The parameters for which the MGC has no knowledge and whose values are not required to be returned shall be designated with "-" (i.e., not significant). In the reply from the MG, these parameters will be marked as "-". Examples follow in Table 8-1.
+
+**Table 8-1 – Examples**
+
+| ITU-T H.248/SDP encoding examples with applied wildcarding:                                                                                                                                                                                                                                                                                    | Results:                                                                   |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|
+| The MGC requests that all the attributes be returned with transaction:<br><pre>Transaction = 10 {   Context = 20 {     AuditValue = 30{       Audit{         Media{           Local{             a=*:*           }         }       }     }   } }</pre>                                                                                         | This could potentially return a long list of all the attributes on the MG. |
+| Whereas transaction:<br><pre>Transaction = 10 {   Context = 20 {     AuditValue = 30{       Audit{         Media{           Local{             a=ptime:*           }         }       }     }   } }</pre>                                                                                                                                       | This would only return the value of the ptime attribute.                   |
+| If the MGC audits a line with multiple parameters (for example "c=") and it only wants to know the type of network, it would issue the following transaction:<br><pre>Transaction = 10 {   Context = 20 {     AuditValue = 30{       Audit{         Media{           Local{             c= * -           }         }       }     }   } }</pre> | It would return the connection line:<br><br><pre>c= IP4 -</pre>            |
+
+## 8.2 Audit capability
+
+Wildcarding of SDP elements for audit capabilities is for further study.
+
+# 9 Advanced SDP Wildcarding Package
+
+**Package name:** Advanced SDP Wildcarding Package
+
+**Package ID:** aswp (0x011c)
+
+**Description:** This package allows the MG to indicate whether it supports advanced SDP wildcarding procedures: multiple value response, multiple line response, wildcarding interlinkage and maintain value. An MGC may use this information to determine which procedures and syntax to use.
+
+**Version:** 1
+
+**Extends:** None.
+
+## 9.1 Properties
+
+### 9.1.1 Advanced Wildcarding Support
+
+**Property name:** Advanced Wildcarding Support
+
+|                         |                                                                                                                                                                                                               |
+|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Property ID:</b>     | aws (0x0001)                                                                                                                                                                                                  |
+| <b>Description:</b>     | This property indicates whether advanced SDP wildcarding procedures: multiple value response, multiple line response, wildcarding interlinkage and maintain value (as described by clause 9.6) are supported. |
+| <b>Type:</b>            | Sub-list of enumeration                                                                                                                                                                                       |
+| <b>Possible values:</b> | MVR multiple value response<br>MLR multiple line response<br>WI wildcard interlinkage<br>MV maintain value                                                                                                    |
+| <b>Default:</b>         | None (unless provisioned otherwise)                                                                                                                                                                           |
+| <b>Defined in:</b>      | TerminationState (Root Termination only)                                                                                                                                                                      |
+| <b>Characteristics:</b> | Read/Write                                                                                                                                                                                                    |
+
+## 9.2 Events
+
+None.
+
+## 9.3 Signals
+
+None.
+
+## 9.4 Statistics
+
+None.
+
+## 9.5 Error codes
+
+None.
+
+## 9.6 Procedures
+
+### 9.6.1 General
+
+The support of the Advanced Wildcarding Support Package (*awsp*) indicates that an MG supports procedures that allow the following wildcards:
+
+- multiple value response: In response to a multiple value wildcard request the MG will return (if applicable) multiple values for the wildcarded parameter. The response uses a single SDP line for the response.
+- multiple line response: In response to a multiple line wildcard request the MG will return (if applicable) multiple values for the wildcarded parameter. The response uses multiple SDP lines for the response, one value per SDP line.
+- wildcarding interlinkage: This allows the MGC to indicate to the MG that a response to one wildcard is used for subsequent wildcards in a particular command.
+- maintain value: This allows the MGC to indicate to the MG that a particular value shall remain unchanged from a previously signalled, wildcarded or provisioned value.
+
+An MGC should perform a packages audit (see clause 7.2.5 of [ITU-T H.248.1]) on the Root Termination to determine if an MG supports the "Advanced Wildcarding Support" package. If the MGC requires the use of advanced wildcards it shall set the "Advanced Wildcarding Support" property (*awsp/aws*) to the wildcards types it requires unless it has already been set via provisioning.
+
+The Advanced Wildcarding Support Package is only for the ITU-T H.248.1 encoding of the SDP, either when the SDP is used natively in ITU-T H.248 text encoding mode or with the use of the SDP equivalent ITU-T H.248 properties (clause C.11 of [ITU-T H.248.1]) in binary encoding mode. It does not relate to the use of CHOOSE wildcards for TerminationIDs or StreamIDs.
+
+If the MGC attempts to use advanced wildcarding procedures toward an MG that does not support this package, the error code 403 "Syntax error in transaction request" is likely to be returned.
+
+### 9.6.2 Wildcarded value response
+
+An MGC may indicate that it requires a wildcarded multiple value response by appending the character "R" or "r" to a CHOOSE wildcard, i.e., "\$R" or "\$r". It may be used where the SDP ABNF definition allows a multiplicity of values, e.g., the ABNF "\* (SP value)". The MGC may use this when it does not know how many values will be returned.
+
+In response to a wildcard multiple value request, an MG will return multiple values (if applicable) of the SDP parameter where the wildcard was issued using a single SDP line.
+
+For example: Utilising the "ssrc-group" as defined in clause 6.15.9.2 an ITU-T H.248 command containing:
+
+```
+a=ssrc-group:FID $R
+```
+
+would return:
+
+```
+a=ssrc-group:FID <ssrc1> <ssrc2> <ssrc3> etc.
+```
+
+### 9.6.3 Wildcarded line response
+
+An MGC may indicate that it requires a wildcarded multiple line response by appending the character "L" or "l" to a CHOOSE wildcard, i.e., "\$L" or "\$l". This is used where the SDP response may require additional SDP lines, but the MGC does not know how many lines will be returned.
+
+In response to a wildcard multiple value request, an MG will return multiple lines (if applicable) of the SDP parameter where the wildcard was issued using a single SDP line.
+
+Only one wildcarded line response request is allowed in an SDP description. If there are other CHOOSE wildcards in the SDP line, then they shall be executed independently per line response.
+
+For example, an ITU-T H.248 command using "ssrc" as defined in clause 6.15.9.2:
+
+```
+a=ssrc:$L cname:$
+```
+
+would return:
+
+```
+a=ssrc:<ssrc2> cname:<cnameA>  
+a=ssrc:<ssrc1> cname:<cnameB>  
+a=ssrc:<ssrc3> cname:<cnameC>  
+etc.
+```
+
+### 9.6.4 Wildcarding interlinkage
+
+An MGC may indicate that multiple CHOOSE wildcard instances are related by appending a HEX digit (which represents a wildcard label) to a CHOOSE wildcard, i.e., "\$[0-F]" or "\$[0-f]". This allows an MGC to indicate that the resulting value of one CHOOSE should be used for the result of another CHOOSE. This is only used when an identical SDP parameter (semantically and syntactically) is used across SDP lines. Only one wildcard label may be used per wildcard; however, several wildcard labels may be used per SDP line and SDP description. CHOOSE wildcards with the same wildcard label may be used across SDP lines. The MG will use the value in response to the first CHOOSE wildcard for the results of the CHOOSE wildcards with the same label on subsequent lines.
+
+For example, using the "ssrc" and "ssrc-group" attributes as defined in clause 6.15.9.2 an ITU-T H.248 command containing:
+
+```
+a=ssrc:$1 cname:$  
+a=ssrc:$2 cname:$  
+a=ssrc-group:FID $1 $2
+```
+
+would return:
+
+```
+a=ssrc:<ssrca> cname:<cnameA>  
+a=ssrc:<ssrcb> cname:<cnameB>  
+a=ssrc-group:FID <ssrca> <ssrcb>
+```
+
+### 9.6.5 Maintain value
+
+The purpose of this wildcard is to allow the MGC to request the preservation of previously set SDP values. The maintain value wildcard, "~", maintains the following unchanged values:
+
+- a) signalled attribute values, or
+- b) previously wildcarded attribute values, or
+- c) provisioned attribute values.
+
+Not using this wildcard implies the complete replication of all SDP information (i.e., fully specified SDP lines) by the MGC, in order not to release previously requested resources at the MG. The MG must process entirely such SDP data and compare it with previously received SDPs. This process may be avoided through the use of this wildcard.
+
+Use cases for a) and b):
+
+- the wildcard is used in ITU-T H.248 command replies (when SDP information is replied).
+- the wildcard is typically used in subsequent ITU-T H.248 command requests, i.e., this wildcard is not used in the first ITU-T H.248 command request, when initially creating a stream endpoint or termination.
+
+Use case for c):
+
+- the wildcard could be used in the first ITU-T H.248 command request, under the condition that corresponding values are already prepared via management actions (at the MGC and the MG level).
+
+Wildcard "~" shall not be used in case of ambiguous SDP media descriptions (e.g., when multiple SDP lines would be linked via an identifier, which is wildcarded).
+
+### 9.6.6 Interactions
+
+#### 9.6.6.1 Interactions between wildcarding qualifiers "value response", "line response" and "interlinkage"
+
+The scope of the wildcarding interlinkage label is limited to the Command, Termination/Stream and Group where the wildcard is issued. For example:
+
+| ITU-T H.248 encoding                                                                                                                                                                                                                                                                                                                                                                                              | Comments                                                                                                                                                 |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <pre> MEGACO/3 [123.123.123.4]:55555 Transaction = 10004 {   Context = 1 {     Add = T1 {       Media {         Stream = 1 {           Local {             v=0             c=IN IP4 \$             m=audio \$1 RTP/AVP 32           }         }         Stream = 2 {           Local {             v=0             c=IN IP4 \$             m=audio \$1 RTP/AVP 8           }         }       }     }   } } </pre> | <p>Even though Stream 1 and Stream 2 both use an interlinked wildcard label \$1 it does not mean that the MG should use the same value for Stream 2.</p> |
+
+An MGC shall not use both the wildcard value response "R" and wildcard line response "L" in the same wildcard, e.g., "\$LR" is not valid.
+
+An MGC may use a wildcard label with a multiple value response (e.g., \$1R or \$R1) or with a multiple line response request (e.g., \$1L or \$L1) in combination with wildcarding interlinkage. An MGC may use the same wildcard label for either multiple values or multiple line response requests. This indicates that multiple values from one SDP line should be used to populate a value on multiple SDP lines and vice-versa.
+
+The use of a multiple values response request and a multiple line response request on one SDP line is valid.
+
+The following example illustrates the use of a multiple value and multiple line response request in an SDP description:
+
+```
+
+a=ssrc-group:FID $1R
+a=ssrc:$1L cname:$
+
+```
+
+The wildcard interlinkage element "1" indicates that the "R" and the "L" wildcards are related. Therefore the MG uses the results of the "R" CHOOSE wildcard to populate multiple instances of a= lines for the response, e.g.:
+
+```
+
+a=ssrc-group:FID <ssrc2> <ssrc1> <ssrc3>
+a=ssrc:<ssrc2> cname:<cnameA>
+a=ssrc:<ssrc1> cname:<cnameB>
+a=ssrc:<ssrc3> cname:<cnameC>
+
+```
+
+#### **9.6.6.2 Additional interactions with wildcarding qualifier "maintain value"**
+
+The combined usage of multiple wildcarding qualifiers in combination with the "maintain value" is principally feasible, but conditional, dependent on particular SDP elements and/or associated SDP lines.
+
+It is not recommended to use the wildcarding qualifier "maintain value" with the other wildcarding qualifiers per SDP line.
+
+# Appendix I
+
+## Example signalling scenarios for the maintain value wildcard "~"
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## I.1 Purpose
+
+The benefit of the maintain value wildcard, "~", is illustrated with two examples: one without wildcarding (clause I.2) and one with wildcarding (clause I.3). The value of this wildcard is primarily motivated by the "size of SDP information", e.g., in the context of large SDP objects (also known as "SDP blobs")<sup>1</sup> that are used in signalling SDP media descriptions for:
+
+- multi-media types/formats/parameters/etc. configurations,
+- key material as part of cryptographic information,
+- fingerprints as part of cryptographic information.
+
+## I.2 Signalling without the maintain value wildcard "~"
+
+The usage of the maintain value wildcard, "~", is illustrated with an example of the SDP attribute "a=fingerprint". This SDP element is an example representation of an SDP element that may have a large value size. An ADD.request command example without wildcard usage is used as a starting point as shown in Table I.1.
+
+A possible example MG reply is shown in Table I.2.
+
+The stream endpoint is modified in a subsequent command cycle, e.g., by the MODIFY.request command shown in Table I.3.
+
+A possible example MG reply is shown in Table I.4.
+
+**Table I.1 – Example command encoding – MGC Add request**
+
+| ITU-T H.248 encoding (shortened command)                                                                                                                                                                                                                                                                                                                                                                                                                                             | Comments                                                                                                                                              |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|
+| MGC to MG:<br>MEGACO/3 [11.9.19.65]:55555<br>Transaction = 1 {<br>Context = \$ {<br><b>Add</b> = ip/\$/\$/\$ {<br>Media {<br>Stream = 1 {<br>LocalControl {<br>...<br>},<br>Local {<br>v=0<br>c=IN IP4 \$<br>m=audio \$ UDP/TLS/RTP/SAVP -<br>b=AS:7<br>a=setup:passive<br><b>a=fingerprint: sha-256</b><br><b>0E:CB:C3:2A:EF:E8:3F:6A:FD:19:07:20:10:80:69:B4:17:E2:3E</b><br><b>:3B:2C:89:41:FB:06:85:E6:71:26:A2:19:51</b><br>},<br>Remote {<br>v=0<br>}<br>}<br>}<br>}<br>}<br>} | The SDP attribute "a=fingerprint" is contained in both the LD and RD. The value is fully specified in the request command in the MGC-to-MG direction. |
+
+<sup>1</sup> Blob: binary or basic large object, relates to a collection of data stored as a single entity.
+
+**Table I.1 – Example command encoding – MGC Add request**
+
+| ITU-T H.248 encoding (shortened command)                                                                                                                                                                 | Comments |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|
+| <pre> c=IN IP4 135.117.113.26 m=audio 56376 UDP/TLS/RTP/SAVP - a=fingerprint:sha-256 8F:AA:57:46:7C:C1:D3:50:74:8D:22:C9:10:12:BE:AD:F0:13:9C :4F:D1:4F:B7:F3:96:5B:C3:70:FC:C5:AA:AE     } ... } </pre> |          |
+
+**Table I.2 – Example command encoding– MG Add reply**
+
+| ITU-T H.248 encoding (shortened command)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Comments                                                                                                                                  |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|
+| <pre> MG to MGC: MEGACO/3 [125.125.125.111]:55555 Reply = 1 {   Context = &lt;C1&gt; {     Add = &lt;IP_A&gt; {       Media {         Stream = 1 {           Local {             v=0             c=IN IP4 172.40.7.1             b=AS:7             m=audio 23914 UDP/TLS/RTP/SAVP -             a=setup:passive             a=fingerprint:sha-256 0E:CB:C3:2A:EF:E8:3F:6A:FD:19:07:20:10:80:69:B4:17:E2:3E :3B:2C:89:41:FB:06:85:E6:71:26:A2:19:51           },           Remote {             v=0             c=IN IP4 135.117.113.26             m=audio 56376 UDP/TLS/RTP/SAVP -             a=fingerprint:sha-256 8F:AA:57:46:7C:C1:D3:50:74:8D:22:C9:10:12:BE:AD:F0:13:9C :4F:D1:4F:B7:F3:96:5B:C3:70:FC:C5:AA:AE           }         }       }     }   } } </pre> | <p>The entire SDP value is replied by the MG. Next, the MGC should validate that information by comparing the sent and received data.</p> |
+
+**Table I.3 – Example command encoding – MGC Modify request**
+
+| ITU-T H.248 encoding (shortened command)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Comments                                                                                                                                                                                                                                                                                                                                  |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <pre> MGC to MG: MEGACO/3 [11.9.19.65]:55555 Transaction = 2 {   Context = &lt;C1&gt; {     <b>Modify</b> = &lt;IP_A&gt; {       Media {         Stream = 1 {           LocalControl {             ...           },           Local {             v=0             c=IN IP4 172.40.7.1             b=AS:7             m=audio 23914 UDP/TLS/RTP/SAVP -             a=setup:passive             a=fingerprint: sha-256 0E:CB:C3:2A:EF:E8:3F:6A:FD:19:07:20:10:80:69:B4:17:E2:3E :3B:2C:89:41:FB:06:85:E6:71:26:A2:19:51             a=rtcp-mux           },           Remote {             v=0             c=IN IP4 135.117.113.26             m=audio 56376 UDP/TLS/RTP/SAVP -             a=fingerprint: sha-256 8F:AA:57:46:7C:C1:D3:50:74:8D:22:C9:10:12:BE:AD:F0:13:9C :4F:D1:4F:B7:F3:96:5B:C3:70:FC:C5:AA:AE             a=rtcp-mux           }         }       }     }   } } </pre> | <p>The MGC has to provide the full specification of the SDP attribute again.<br/> The MG has to validate this information by comparing (and possibly updating) the information received in the previous command request (Table I.1). This is a cumbersome and unnecessary task when the value itself was not changed (as shown here).</p> |
+
+**Table I.4 – Example command encoding– MG Modify reply**
+
+| ITU-T H.248 encoding (shortened command)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Comments                                                                                          |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|
+| <pre> MG to MGC: MEGACO/3 [125.125.125.111]:55555 Reply = 2 {   Context = &lt;C1&gt; {     <b>Modify</b> = &lt;IP_A&gt; {       Media {         Stream = 1 {           Local {             v=0             c=IN IP4 172.40.7.1             b=AS:7             m=audio 23914 UDP/TLS/RTP/SAVP -             a=setup:passive             a=fingerprint: sha-256 0E:CB:C3:2A:EF:E8:3F:6A:FD:19:07:20:10:80:69:B4:17:E2:3E :3B:2C:89:41:FB:06:85:E6:71:26:A2:19:51             a=rtcp-mux           },           Remote {             v=0             c=IN IP4 135.117.113.26             m=audio 56376 UDP/TLS/RTP/SAVP -             a=fingerprint: sha-256 8F:AA:57:46:7C:C1:D3:50:74:8D:22:C9:10:12:BE:AD:F0:13:9C :4F:D1:4F:B7:F3:96:5B:C3:70:FC:C5:AA:AE             a=rtcp-mux           }         }       }     }   } } </pre> | <p>Same comment as in Table I.2. Now, the MGC might be loaded with an unnecessary task again.</p> |
+
+## I.3 Signalling using the maintain value wildcard "~"
+
+The same signalling example, with two command request/reply cycles, is now used with wildcard "~". The wildcard, as such, is applicable due to unchanged parameter values. Table I.5 provides the starting point. A possible example MG reply is indicated in Table I.6.
+
+Table I.7 illustrates the MODIFY.request command and a possible example MG reply is indicated in Table I.8.
+
+**Table I.5 – Example command encoding – MGC Add request**
+
+| ITU-T H.248 encoding (shortened command)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Comments                                                                                                                                                        |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <pre> MGC to MG: MEGACO/3 [11.9.19.65]:55555 Transaction = 1 {   Context = \$ {     Add = ip/\$/\$/\$ {       Media {         Stream = 1 {           LocalControl {             ...           },           Local {             v=0             c=IN IP4 \$             m=audio \$ UDP/TLS/RTP/SAVP -             b=AS:7             a=setup:passive             a=fingerprint: sha-256 0E:CB:C3:2A:EF:E8:3F:6A:FD:19:07:20:10:80:69:B4:17:E2:3E :3B:2C:89:41:FB:06:85:E6:71:26:A2:19:51           },           Remote {             v=0             c=IN IP4 135.117.113.26             m=audio 56376 UDP/TLS/RTP/SAVP -             a=fingerprint:sha-256 8F:AA:57:46:7C:C1:D3:50:74:8D:22:C9:10:12:BE:AD:F0:13:9C :4F:D1:4F:B7:F3:96:5B:C3:70:FC:C5:AA:AE           }         }       }     }   } } </pre> | <p>This is identical to Table I.1, i.e., a fully specified SDP value (because such cryptographic information is normally out of scope of any provisioning).</p> |
+
+**Table I.6 – Example command encoding– MG Add reply**
+
+| ITU-T H.248 encoding (shortened command)                                                                                                                                                                                                                                                                                                                                                                                                       | Comments                                                                                                                                           |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|
+| <pre> MG to MGC: MEGACO/3 [125.125.125.111]:55555 Reply = 1 {   Context = &lt;C1&gt; {     Add = &lt;IP_A&gt; {       Media {         Stream = 1 {           Local {             v=0             c=IN IP4 172.40.7.1             b=AS:7             m=audio 23914 UDP/TLS/RTP/SAVP -             a=setup:passive             a=fingerprint::~           },           Remote {             v=0           }         }       }     }   } } </pre> | <p>The two SDP attribute parameter values could be both wildcarded "~". Thus, the MG acknowledges that it has accepted values sent by the MGC.</p> |
+
+**Table I.6 – Example command encoding– MG Add reply**
+
+| ITU-T H.248 encoding (shortened command)                                                        | Comments |
+|-------------------------------------------------------------------------------------------------|----------|
+| <pre> c=IN IP4 135.117.113.26 m=audio 56376 UDP/TLS/RTP/SAVP - a=fingerprint:~ ~ } ... } </pre> |          |
+
+**Table I.7 – Example command encoding – MGC Modify request**
+
+| ITU-T H.248 encoding (shortened command)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Comments                                                                                           |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|
+| <pre> MGC to MG: MEGACO/3 [11.9.19.65]:55555 Transaction = 2 {   Context = &lt;C1&gt; {     <b>Modify</b> = &lt;IP_A&gt; {       Media {         Stream = 1 {           LocalControl {             ...           },           Local {             v=0             c=IN IP4 172.40.7.1             b=AS:7             m=audio 23914 UDP/TLS/RTP/SAVP -             a=setup:passive             a=fingerprint: ~ ~             a=rtcp-mux           },           Remote {             v=0             c=IN IP4 135.117.113.26             m=audio 56376 UDP/TLS/RTP/SAVP -             a=fingerprint:~ ~             a=rtcp-mux           }         }       }     }   } } ... } </pre> | <p>The MGC could use "~" wildcarding again. This simplifies processing at the MGC and MG side.</p> |
+
+**Table I.8 – Example command encoding– MG Modify reply**
+
+| ITU-T H.248 encoding (shortened command)                                                                                                                                                                                                                                                                                                                                                                                                | Comments                                                                                               |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|
+| <pre> MG to MGC: MEGACO/3 [125.125.125.111]:55555 Reply = 2 {   Context = &lt;C1&gt; {     <b>Modify</b> = &lt;IP_A&gt; {       Media {         Stream = 1 {           Local {             v=0             c=IN IP4 172.40.7.1             b=AS:7             m=audio 23914 UDP/TLS/RTP/SAVP -             a=setup:passive             <b>a=fingerprint:~ ~</b>             a=rtcp-mux           }         }       }     }   } } </pre> | <p>The MG could also use "~" wildcarding again. This simplifies processing at the MG and MGC side.</p> |
+
+## **I.4 Evaluation of the examples**
+
+The maintain value wildcard, "~", could be applied in three out of four commands in the examples shown in clause I.3 versus I.2. It could also be demonstrated that wildcard "~" is used in command replies (see Tables I.6 and I.8) besides the usage in the MODify command request (see Table I.5).
+
+Furthermore, it should be emphasized that the processing savings are not only related to the sending ITU-T H.248 entity, but rather that both ITU-T H.248 entities (MGC and MG) benefit from wildcarding.
+
+# Bibliography
+
+- [b-ITU-T G.711] Recommendation ITU-T G.711 (1988), *Pulse code modulation (PCM) of voice frequencies*.
+- [b-ITU-T G.726] Recommendation ITU-T G.726 (1990), *40, 32, 24, 16 kbit/s Adaptive Differential Pulse Code Modulation (ADPCM)*.
+- [b-ITU-T H.248.49] Recommendation ITU-T H.248.49 (2007), *Gateway control protocol: Session description protocol RFC and capabilities packages*.
+- [b-ETSI ES 283 018] ETSI ES 283 018 (2007), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: H.248 Profile for controlling Border Gateway Functions (BGF) in the Resource and Admission Control Subsystem (RACS); Protocol specification*.  
+NOTE – This profile is also referred to as "H.248 Ia profile version 1".
+- [b-ETSI TR 183 068] ETSI TR 183 068 (2009), *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-IETF RFC 822] IETF RFC 822 (1982), *Standard for ARPA Internet Text Messages*.
+- [b-IETF RFC 1630] IETF RFC 1630 (1994), *Universal Resource Identifiers in WWW*.
+- [b-IETF RFC 2327] IETF RFC 2327 (1998), *SDP: Session Description Protocol*.
+- [b-IETF RFC 3108] IETF RFC 3108 (2001), *Conventions for the use of the Session Description Protocol (SDP) for ATM Bearer Connections*.
+- [b-IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications*.
+- [b-IETF RFC 3605] IETF RFC 3605 (2003), *Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)*.
+- [b-IETF RFC 4566] IETF RFC 4566 (2006), *SDP: Session Description Protocol*.
+- [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 4588] IETF RFC 4588 (2006), *RTP Retransmission Payload Format*.
+- [b-IETF RFC 5576] IETF RFC 5576 (2009), *Source-Specific Media Attributes in the Session Description Protocol (SDP)*.
+- [b-IETF RFC 5888] IETF RFC 5888 (2010), *The Session Description Protocol (SDP) Grouping Framework*.
+- [b-IETF RFC 6222] IETF RFC 6222 (2011), *Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)*.
+
+
+
+# **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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.40-201303-I_PDF-E/raw.md b/marked/H/T-REC-H.248.40-201303-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..aec8be7aba02b1f26358b020b62333f30fd038b3
--- /dev/null
+++ b/marked/H/T-REC-H.248.40-201303-I_PDF-E/raw.md
@@ -0,0 +1,536 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.40**
+
+(03/2013)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+---
+
+**Gateway control protocol: Application data  
+inactivity detection package**
+
+Recommendation ITU-T H.248.40
+
+# 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        |
+| <b>Communication procedures</b>                                               | <b>H.240–H.259</b> |
+| 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.40
+
+## Gateway control protocol: Application data inactivity detection package
+
+# Summary
+
+Recommendation ITU-T H.248.40 describes the principle used to detect application data inactivity for IP transport connections in general, like e.g., avoid a potential situation of deadlock if latching was set but no application data stream is incoming to latch on. The solution is based on an event to detect if application data had stopped (or not started).
+
+This revision provides additional information regarding the setting of the detection time for the IP flow stop event.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group |
+|---------|----------------|------------|-------------|
+| 1.0     | ITU-T H.248.40 | 2007-01-13 | 16          |
+| 2.0     | ITU-T H.248.40 | 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                      | 1    |
+| 5 Conventions .....                                                                     | 2    |
+| 6 Application data inactivity detection package.....                                    | 2    |
+| 6.1 Properties.....                                                                     | 2    |
+| 6.2 Events .....                                                                        | 2    |
+| 6.3 Signals .....                                                                       | 3    |
+| 6.4 Statistics.....                                                                     | 3    |
+| 6.5 Error codes.....                                                                    | 4    |
+| 6.6 Procedures .....                                                                    | 4    |
+| Appendix I – Example use case for voice-over-RTP.....                                   | 5    |
+| I.1 Introduction .....                                                                  | 5    |
+| I.2 Abbreviations .....                                                                 | 5    |
+| I.3 Assumptions .....                                                                   | 5    |
+| I.4 Example detection logic .....                                                       | 5    |
+| I.5 Recommendations for timer settings.....                                             | 6    |
+| Appendix II – Example use case for deadlock detection in IP latching scenarios.....     | 7    |
+| II.1 Introduction .....                                                                 | 7    |
+| II.2 Assumptions .....                                                                  | 8    |
+| II.3 Example detection logic .....                                                      | 8    |
+| II.4 Recommendations for timer settings.....                                            | 8    |
+| Appendix III – Example use case for detection of a hanging voice over RTP session ..... | 9    |
+| III.1 Introduction .....                                                                | 9    |
+| III.2 Abbreviations and acronyms .....                                                  | 9    |
+| III.3 Incorrect termination of a Voice over RTP session.....                            | 9    |
+| III.4 Relation of "hanging RTP session" with "hanging ITU-T H.248 termination" .....    | 10   |
+| Bibliography.....                                                                       | 11   |
+
+
+
+## Recommendation ITU-T H.248.40
+
+## Gateway control protocol: Application data inactivity detection package
+
+# 1 Scope
+
+This Recommendation allows a media gateway controller to request the media gateway to detect that after a certain period of time no Internet protocol application data has flowed on a particular termination/stream. The ability to detect if Internet protocol application data flow has stopped or has not started is useful to avoid deadlock in latching scenarios and also may be of use to detect hanging bearers.
+
+This Recommendation defines an event which is related to one or more IP 2-tuples. An individual 2-tuple is given by <IP address, IP port> of an IP flow of an ITU-T H.248 stream or termination. The set of conditions for inactivity detection is related to IP packet arrival and/or departure events for all 2-tuples of a stream/termination. The condition of packet arrivals or departures respectively is controlled via a dedicated parameter (called "*direction*").
+
+The flexibility of inactivity detection logic configurations allows the usage of ITU-T H.248.40 for various applications (see also 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 H.248.1] Recommendation ITU-T H.248.1 (2013), *Gateway control protocol: Version 3*.
+
+# 3 Terms and definitions
+
+None.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                       |
+|------|---------------------------------------|
+| ADID | Application Data Inactivity Detection |
+| IP   | Internet Protocol                     |
+| LD   | Local Descriptor                      |
+| MG   | Media Gateway                         |
+| MGC  | Media Gateway Controller              |
+| NAPT | Network Address and Port Translation  |
+| RD   | Remote Descriptor                     |
+| RTCP | RTP Control Protocol                  |
+| RTP  | Real-Time Transport Protocol          |
+| RTSP | Real-Time Streaming Protocol          |
+
+# 5 Conventions
+
+None.
+
+# 6 Application data inactivity detection package
+
+|                      |                                                                                                                                                  |
+|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Package name:</b> | Application data inactivity detection package                                                                                                    |
+| <b>Package ID:</b>   | adid (0x009c)                                                                                                                                    |
+| <b>Description:</b>  | This package enables the MGC to be notified when the MG has detected that no IP application data flow has been detected on a termination/stream. |
+| <b>Version:</b>      | 1                                                                                                                                                |
+| <b>Extends:</b>      | None                                                                                                                                             |
+
+## 6.1 Properties
+
+None.
+
+## 6.2 Events
+
+### 6.2.1 IP flow stop detection
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Event name:</b>  | IP flow stop detection                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Event ID:</b>    | ipstop (0x0001)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Description:</b> | <p>This event detects if there has been no direction-dependent application data for a set (detection time) interval of time. In cases where it has been indicated that multiple IP ports are associated with a flow (e.g., RTP and RTCP), the detection of no application data flow must be done on all ports before the event is triggered. When applied at a termination level the <i>adid/ipstop</i> event shall be notified when it has been determined that application data has stopped on all of the streams associated with the termination.</p> <p>If, after the initial reporting of the event, and if the event remains active, the detection time elapses without detection of application data, the event is reported again. This may occur multiple times.</p> <p>This event shall be detected irrespective of the StreamMode. For example, even if the stream is set to SendOnly and packets are received, this will be taken into account.</p> |
+
+#### 6.2.1.1 EventDescriptor parameters
+
+##### 6.2.1.1.1 Detection time
+
+|                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Parameter name:</b> | Detection time                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Parameter ID:</b>   | dt (0x0001)                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Description:</b>    | <p>This is the interval of time after which if no application data flow is detected, the IP Flow Stop Detection event is triggered. The MG checks over intervals of detection time <i>dt</i> if any application data traffic has occurred. If no application data has arrived, then the <i>adid/ipstop</i> event is triggered.</p> <p>NOTE – This may result that more than the detection time has passed between the IP data flow stop and the detection of the event.</p> |
+
+**Type:** Integer
+
+**Optional:** Yes (if default is provisioned).
+
+**Possible values:** Any positive number of seconds.
+
+**Default:** Provisioned
+
+NOTE:
+
+a) Application-independent versus application-specific values:
+
+Either a single, global default value or multiple, application specific default values may be provisioned. There is typically a single value configured in case of a provisioning approach, valid for all applications. Multiple, application-specific default values could be also provisioned. The value selection could be tied to application information like the LD/RD-embedded media description. The specific selection method is out of scope of this package definition and may be e.g., defined in an ITU-T H.248 profile specification.
+
+b) Stream- versus Termination-level event arming:
+
+When applied at a Termination level, where might be aggregated traffic based on multiple applications (in case of multiple streams). The value selection may be again application-specific or a single value. However in this case value selection must be based on the fact that the event will be notified when only all streams on the Termination have timed out.
+
+##### 6.2.1.1.2 Direction
+
+**Parameter name:** Direction
+
+**Parameter ID:** dir (0x0002)
+
+**Description:** With this parameter, the MGC indicates to the MG which direction of the data flow should be monitored to detect inactivity. Incoming direction means from the outside of the context. Outgoing direction means towards the outside of the context. If direction is set to "BOTH", the MG will generate the event if no data is sent nor received on the termination to/from the outside of the context for an interval of detection time *dt*.
+
+**Type:** Enumeration
+
+**Optional:** Yes
+
+**Possible values:** "IN" (0x0001) Incoming direction  
+"OUT" (0x0002) Outgoing direction  
+"BOTH" (0x0003) Both directions
+
+**Default:** Both
+
+#### 6.2.1.2 ObservedEventsDescriptor parameters
+
+None.
+
+## 6.3 Signals
+
+None.
+
+## 6.4 Statistics
+
+None.
+
+## 6.5 Error codes
+
+None.
+
+## 6.6 Procedures
+
+To detect application data inactivity, the MGC should set the *adid/ipstop* event with an appropriate "detection time" and the appropriate "direction" on the applicable ITU-T H.248 Stream/Termination. The *adid/ipstop* event is notified to the MGC:
+
+- If the MGC has set *dir* to "IN" and no IP data packets have been received by the MG from the network in that stream/termination by the expiry of the detection time (*dt*).
+- If the MGC has set *dir* to "OUT" and no IP data packets have been sent by the MG to the network in that stream/termination by the expiry of the detection time (*dt*).
+- If the MGC has set direction to "BOTH" and no IP data packets have been sent to nor received from the network in that stream/termination by the expiry of the detection time (*dt*).
+
+On reception of a NOTIFY.req with the *adid/ipstop* event, the MGC should take appropriate action.
+
+The triggered action on MGC level may have to take into account:
+
+- Service features (e.g., unidirectional applications, muted microphone in conference services, etc.).
+- Bearer service configuration settings (e.g., enabled silence suppression mode in case of speech telephony, RTP sessions without RTCP, etc.).
+- ITU-T H.248 Termination configurations (e.g., ITU-T H.248 StreamMode Property equals "Inactive").
+
+It is recommended to set timer detection time (*dt*) with a relevant value, e.g., a multiple of half the round-trip delay or a multiple of the typical packet interarrival time. The mean interarrival time may be IP application-specific (e.g., codec type), may depend on application level framing protocol usage (e.g., RTP packetization time, RTCP transmission interval, etc.) or service-specific (e.g., muted microphone in case of voice over RTP, or suspended streaming in case of RTSP-controlled multimedia streaming).
+
+# Appendix I
+
+## Example use case for voice-over-RTP
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## I.1 Introduction
+
+This Recommendation may be applied on ephemeral terminations, which are used for two-party voice-over-RTP (VoRTP) service realizations. The RTP packet transmission interval is here much smaller than the granularity of timer "ipstop/dt".
+
+This appendix illustrates the detection of "RTP media stop". The event of "RTP media stop" relates to the arrival/departure event of an RTP or RTCP packet.
+
+## I.2 Abbreviations
+
+This appendix uses the following abbreviations:
+
+|       |                                        |
+|-------|----------------------------------------|
+| FIB   | (IP) Forwarding Information Base       |
+| IPLR  | IP Packet Loss Ratio                   |
+| RIB   | (IP) Routing Information Base          |
+| SDL   | Specification and Description Language |
+| VoRTP | Voice over RTP                         |
+
+## I.3 Assumptions
+
+From the RTP bearer point of view:
+
+- RTCP is enabled.
+- Minimum RTCP transmission interval is 5 s (see clause A.7 of [b-IETF RFC 3550]).
+- RTP peer endpoints continue to send RTCP packets during "silence phases" (detected voice inactivity, or muted microphone).
+
+From the ITU-T H.248 point of view:
+
+- MGC considers StreamMode setting (in case of Event notification).
+
+## I.4 Example detection logic
+
+Figure I.1 illustrates example detection logic. The event is supposed to be continuously enabled (default EventBufferControl setting).
+
+It has to be noted that the event remains active until disabled by the MGC.
+
+![State transition diagram for VoRTP. It starts with a 'SET timer T1 := ipstop/dt' action, leading to 'State S1: WAIT'. From S1, a 'Timer expiration' event triggers a 'T1' transition to an 'H.248 NOTIFY.req' message sent to the 'MGC'. Another transition from S1 leads to a dashed box containing two 'RTP packet' and 'RTCP packet' blocks, each associated with an 'RTP peer endpoint'. A 'General' transition from the RTCP packet block leads to an 'IP Flow' RxPacket block. A 'NOTE' at the bottom states: 'Assumed are default settings of EventBufferControl (Off)'.](d4af765160d04ecef538e5066006dc77_img.jpg)
+
+MG: H.248 ephemeral termination, ServiceState = "In-Service"
+
+```
+
+stateDiagram-v2
+    [*] --> SET_timer_T1
+    state "SET timer T1 := ipstop/dt" as SET_timer_T1
+    SET_timer_T1 --> S1
+    state "State S1: WAIT" as S1
+    S1 --> T1
+    state "T1" as T1
+    T1 --> NOTIFY_req
+    state "H.248 NOTIFY.req" as NOTIFY_req
+    NOTIFY_req --> MGC
+    S1 --> RTP_packets
+    state "RTP packet" as RTP_packet
+    state "RTCP packet" as RTCP_packet
+    subgraph RTP_packets [ ]
+        RTP_packet --> RTCP_packet
+    end
+    RTCP_packet --> IP_Flow_RxPacket
+    state "\"IP Flow\" RxPacket" as IP_Flow_RxPacket
+    IP_Flow_RxPacket --> [*]
+    note right of RTP_packets: General
+    note right of RTCP_packets: RTP peer endpoint
+    note right of RTP_packet: RTP peer endpoint
+    note left of SET_timer_T1: (Note)
+    note right of NOTIFY_req: MGC
+    note bottom: NOTE – Assumed are default settings of EventBufferControl ("Off").
+  
+```
+
+H.248.40(01-07)\_FI.01
+
+State transition diagram for VoRTP. It starts with a 'SET timer T1 := ipstop/dt' action, leading to 'State S1: WAIT'. From S1, a 'Timer expiration' event triggers a 'T1' transition to an 'H.248 NOTIFY.req' message sent to the 'MGC'. Another transition from S1 leads to a dashed box containing two 'RTP packet' and 'RTCP packet' blocks, each associated with an 'RTP peer endpoint'. A 'General' transition from the RTCP packet block leads to an 'IP Flow' RxPacket block. A 'NOTE' at the bottom states: 'Assumed are default settings of EventBufferControl (Off)'.
+
+**Figure I.1 – Example SDL logic for VoRTP**
+
+## I.5 Recommendations for timer settings
+
+Some qualitative recommendations; specific settings may depend on the indicated variables.
+
+### I.5.1 Objective: "Detect Interrupted IP Route"
+
+Settings of timer "ipstop/dt" may be based on the RTP transmission interval ("estimated maximum interval size").
+
+In case of "fast detection" below, the minimum RTCP report interval is required.
+
+NOTE – Rerouting mechanisms on IP level might be of consideration (e.g., RIB/FIB update intervals due to applied IP routing protocol(s)).
+
+### I.5.2 Objective: "Detect Released RTP Endpoint"
+
+Settings of timer "ipstop/dt" may be based on a combination of:
+
+- RTCP transmission interval ("estimated maximum interval size"); and
+- IPLR conditions ("estimated loss of RTCP packets").
+
+In case "fast detection" is required, or in case of a more "conservative detection" on (RTP) session holding time (e.g., "estimated Context Holding Time (C<sub>o</sub>HT) for VoRTP service").
+
+# Appendix II
+
+## Example use case for deadlock detection in IP latching scenarios
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## II.1 Introduction
+
+This Recommendation may be applied in the context of [b-ITU-T H.248.37] applications. Figure II.1 shows a potential network configuration.
+
+![Figure II.1: Possible network configuration diagram. It shows a Media gateway (MG1) on the left connected via an 'IP connection' to an 'IP peer connection endpoint, e.g., media gateway (MG2)' on the right. The connection passes through a dashed box labeled 'NAT/FW' which contains three NAT/FW devices. The first two are labeled 'NAT/FW' and 'NAT/FW', and the third is labeled 'NAT/FW'. The connection is labeled 'A_MG1' at MG1, 'A'_MG2' at the first NAT/FW, 'A'_MG1' at the third NAT/FW, and 'A_MG2' at MG2. The NAT/FW devices are grouped into 'IP domain 1' and 'IP domain 2'. Below the NAT/FW box, it says '1 to N interim NAT/FW devices, modelled by a single entity'. The diagram is labeled 'H.248.40(01-07)_FII.01' at the bottom right.](410562339ce067fdc6fa41940c118658_img.jpg)
+
+Figure II.1: Possible network configuration diagram. It shows a Media gateway (MG1) on the left connected via an 'IP connection' to an 'IP peer connection endpoint, e.g., media gateway (MG2)' on the right. The connection passes through a dashed box labeled 'NAT/FW' which contains three NAT/FW devices. The first two are labeled 'NAT/FW' and 'NAT/FW', and the third is labeled 'NAT/FW'. The connection is labeled 'A\_MG1' at MG1, 'A'\_MG2' at the first NAT/FW, 'A'\_MG1' at the third NAT/FW, and 'A\_MG2' at MG2. The NAT/FW devices are grouped into 'IP domain 1' and 'IP domain 2'. Below the NAT/FW box, it says '1 to N interim NAT/FW devices, modelled by a single entity'. The diagram is labeled 'H.248.40(01-07)\_FII.01' at the bottom right.
+
+Figure II.1 – Possible network configuration
+
+[b-ITU-T H.248.37] is supporting dynamic IP address adaptations in the user plane (IP-based NGN transport stratum).
+
+This appendix illustrates the detection of a deadlock situation in relation to latching.
+
+### II.1.1 Deadlock situation
+
+Sent IP packets may not reach the peer endpoint due to incorrect address information (here: 4-tuple in case of NAPT devices). Figure II.2 illustrates a potential scenario.
+
+![Figure II.2: Potential deadlock situations diagram. It shows a Media gateway (MG1) on the left with 'Context C1' and 'IP packet flow' labeled 'A1'. It is connected to an 'IP peer connection endpoint' on the right with 'IP packet flow' labeled 'A2'. Between them is a 'NAT/FW' device. The diagram shows 'Deadlock' points at both MG1 and the peer endpoint. Red circles with numbers 1, 2, and 3 indicate specific deadlock scenarios: 1. Traffic might traverse wrong route (e.g., A not equal to A2'). 2. Traffic might be blocked at NAT/FW device (e.g., not equal to A2'). 3. Traffic might traverse wrong route (e.g., incorrect address translation). A text box at the bottom explains: 'Sent IP packets do not reach peer IP connection endpoint due to incorrect address (tuple) 'A'. E.g., MG1 perspective: 1. Traffic might traverse wrong route (e.g., A not equal to A2'). 2. Traffic might be blocked at NAT/FW device (e.g., not equal to A2'). 3. Traffic might traverse wrong route (e.g., incorrect address translation). The specific behaviour depends on the NAT mode of operation [b-IETF RFC 2663].'. The diagram is labeled 'H.248.40(13)_FII.02' at the bottom right.](5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg)
+
+Figure II.2: Potential deadlock situations diagram. It shows a Media gateway (MG1) on the left with 'Context C1' and 'IP packet flow' labeled 'A1'. It is connected to an 'IP peer connection endpoint' on the right with 'IP packet flow' labeled 'A2'. Between them is a 'NAT/FW' device. The diagram shows 'Deadlock' points at both MG1 and the peer endpoint. Red circles with numbers 1, 2, and 3 indicate specific deadlock scenarios: 1. Traffic might traverse wrong route (e.g., A not equal to A2'). 2. Traffic might be blocked at NAT/FW device (e.g., not equal to A2'). 3. Traffic might traverse wrong route (e.g., incorrect address translation). A text box at the bottom explains: 'Sent IP packets do not reach peer IP connection endpoint due to incorrect address (tuple) 'A'. E.g., MG1 perspective: 1. Traffic might traverse wrong route (e.g., A not equal to A2'). 2. Traffic might be blocked at NAT/FW device (e.g., not equal to A2'). 3. Traffic might traverse wrong route (e.g., incorrect address translation). The specific behaviour depends on the NAT mode of operation [b-IETF RFC 2663].'. The diagram is labeled 'H.248.40(13)\_FII.02' at the bottom right.
+
+Figure II.2 – Potential deadlock situations
+
+The initially incorrect address tuple requires an inbound IP packet flow in order to adapt to a correct address (also known as "latching" function; see [b-ITU-T H.248.37]).
+
+Deadlock situation:
+
+"No address update in case of missing inbound flow, accompanied by impossible packet delivery in outbound directions due to incorrect address information, ..."
+
+## **II.2 Assumptions**
+
+How such deadlock situations are finally resolved is beyond the scope of this Recommendation. Basic assumption is that such actions might be triggered by MGCs, based on ITU-T H.248.40 event notifications.
+
+From the IP bearer termination point of view:
+
+- None.
+
+From the ITU-T H.248 point of view:
+
+- MGC considers StreamMode setting (in case of Event notification).
+
+## **II.3 Example detection logic**
+
+Activity in outbound direction is irrelevant. The example detection logic according to Figure I.1 is therefore applicable as well. Valid IP packet arrival events are defined by available address tuple information according to the ITU-T H.248 local descriptor (LD).
+
+## **II.4 Recommendations for timer settings**
+
+Some qualitative recommendations; specific settings may depend on the indicated variables.
+
+### **II.4.1 Objective: "Detect deadlock in IP latching applications"**
+
+Settings of timer "ipstop/dt" may be based on "typical, end-to-end session establishment delay" values in case "fast detection" is required.
+
+NOTE – The assumption is stable "device configuration settings" after a completed signalling scenario for session establishment.
+
+# Appendix III
+
+## Example use case for detection of a hanging voice over RTP session
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## III.1 Introduction
+
+This Recommendation may be used to detect and avoid hanging RTP sessions. An RTP session is characterized by one or two (in case of RTCP) UDP-based IP transport connections between two RTP end systems (see [b-IETF RFC 3550]). For instance, in Figure III.1, the two peer RTP endpoints are located in VoRTP MGs, i.e., the MGs acting as RTP end system. The RTP session endpoint is therefore related to an ephemeral termination.
+
+![Diagram of network configuration in a voice over RTP session. It shows a sequence of components: End user equipment, Access network, Media gateway MG1, RTP/IP network, Media gateway MG2, Access network, and End user equipment. The components are connected in a linear fashion, with the RTP/IP network being a cloud-like shape in the center.](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg)
+
+```
+graph LR; EUE1[End user equipment] --- AN1((Access network)); AN1 --- MG1[Media gateway MG1]; MG1 --- RTP_IP_network((RTP/IP network)); RTP_IP_network --- MG2[Media gateway MG2]; MG2 --- AN2((Access network)); AN2 --- EUE2[End user equipment];
+```
+
+H.248.40(01-07)\_FIII.01
+
+Diagram of network configuration in a voice over RTP session. It shows a sequence of components: End user equipment, Access network, Media gateway MG1, RTP/IP network, Media gateway MG2, Access network, and End user equipment. The components are connected in a linear fashion, with the RTP/IP network being a cloud-like shape in the center.
+
+Figure III.1 – Network configuration in a voice over RTP session
+
+The "access network" in Figure III.1 is not necessarily "RTP-based".
+
+## III.2 Abbreviations and acronyms
+
+This appendix uses the following abbreviation:
+
+VoIP            Voice over IP
+
+## III.3 Incorrect termination of a Voice over RTP session
+
+Figure III.1 shows two user equipment engaged in a VoIP connection.
+
+If one or both of the sides of the session (RTP session and/or call/session control association) is not terminated properly, this may result in some cases in hanging bearer resources or sessions kept alive for unnecessary long time. The operator may protect itself against this situation by using ITU-T H.248.40.
+
+Normally in this case, a hanging situation cannot be assumed only due to lack of data activity in one direction. It is necessary to observe that no RTP stream is received in either direction to assume a hanging situation. Therefore the MGC should arm the ipstop event with direction equals to "both".
+
+## **III.4 Relation of "hanging RTP session" with "hanging ITU-T H.248 termination"**
+
+The hanging session scenario described in clause III.3 may imply hanging resources at call control level, i.e., not only have the bearer resources in the MG not been released, but the corresponding control resources in the MGC have not been released either. This kind of scenarios cannot be resolved with the ITU-T H.248.36 hanging termination detection package, as the scenario does not involve a hanging termination.
+
+Thus, the packages of ITU-T H.248.40 and ITU-T H.248.36 are generally decoupled and complementary because they are both addressing different inactivity conditions in user plane and control plane respectively.
+
+# Bibliography
+
+- [b-ITU-T H.248.37] Recommendation ITU-T H.248.37 (2008), *Gateway control protocol: IP NAPT traversal package.*
+- [b-IETF RFC 2663] IETF RFC 2663 (1999), *IP Network Address Translator (NAT) Terminology and Considerations.*
+- [b-IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications.*
+
+
+
+
+
+# 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.43-200806-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.43-200806-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a
--- /dev/null
+++ b/marked/H/T-REC-H.248.43-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.43-200806-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/H/T-REC-H.248.43-200806-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6687ec2831a42bf375f39d8aa4b655d0198467bd
--- /dev/null
+++ b/marked/H/T-REC-H.248.43-200806-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:752075faa914dc2d6afe399264cec4762dec8fbab9df663d64b380a664927a13
+size 48950
diff --git a/marked/H/T-REC-H.248.43-200806-I_PDF-E/9870bf462aa0d916a16d14b5a100c60a_img.jpg b/marked/H/T-REC-H.248.43-200806-I_PDF-E/9870bf462aa0d916a16d14b5a100c60a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a021f1dea7c7ff3a29bf3f6636d7be1ff6c6ab5d
--- /dev/null
+++ b/marked/H/T-REC-H.248.43-200806-I_PDF-E/9870bf462aa0d916a16d14b5a100c60a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:73a8c25b3c6392f587fdf91c06a5f5dd97d32ba3e20382923604192a5e662d00
+size 123637
diff --git a/marked/H/T-REC-H.248.43-200806-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg b/marked/H/T-REC-H.248.43-200806-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5d239adf099211a8cc22bc8ffdcf26b1b3ed5e22
--- /dev/null
+++ b/marked/H/T-REC-H.248.43-200806-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a9d8b1710543e9524663ff5a2cfb379a1ec2cca60495722c7e6ab12f06b6414f
+size 22291
diff --git a/marked/H/T-REC-H.248.43-200806-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/H/T-REC-H.248.43-200806-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..054196fa02dbcd7e7f022e70ad71e12640dcfcad
--- /dev/null
+++ b/marked/H/T-REC-H.248.43-200806-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1a5af635e9a4427a08aee1cac8c62f33a942403a3aac4e19a3be3af3f3434490
+size 45355
diff --git a/marked/H/T-REC-H.248.43-200806-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.248.43-200806-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8a48a7192ed173e4cd78983e6fd23138b1875388
--- /dev/null
+++ b/marked/H/T-REC-H.248.43-200806-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7acee061a555e66174380107915f3a73252baf155713682ebb54089fa13fe854
+size 104571
diff --git a/marked/H/T-REC-H.248.43-200806-I_PDF-E/e354b57563dae469c00b412b2abdf765_img.jpg b/marked/H/T-REC-H.248.43-200806-I_PDF-E/e354b57563dae469c00b412b2abdf765_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cbfb09e612c4db64ece27f9bc645992352f81525
--- /dev/null
+++ b/marked/H/T-REC-H.248.43-200806-I_PDF-E/e354b57563dae469c00b412b2abdf765_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02903cce2c06207f6542d9f95d11fbf803807c5856a9252505299bd05d75f057
+size 21608
diff --git a/marked/H/T-REC-H.248.43-200806-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/H/T-REC-H.248.43-200806-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..92e873ff55182f0ec1db1ddd152df24fe7abc216
--- /dev/null
+++ b/marked/H/T-REC-H.248.43-200806-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:970e235b368f43dda031001ac4ef0f94c9c79975784edb25a1a30387239d46ef
+size 79821
diff --git a/marked/H/T-REC-H.248.43-200806-I_PDF-E/raw.md b/marked/H/T-REC-H.248.43-200806-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a27774a93e3adb950cb25b148ce9afbdef917c79
--- /dev/null
+++ b/marked/H/T-REC-H.248.43-200806-I_PDF-E/raw.md
@@ -0,0 +1,1425 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.43**
+
+(06/2008)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+# --- **Gateway control protocol: Packages for gate management and gate control**
+
+Recommendation ITU-T H.248.43
+
+## 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        |
+| <b>Communication procedures</b>                                               | <b>H.240–H.259</b> |
+| 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.43**
+
+# **Gateway control protocol: Packages for gate management and gate control**
+
+## **Summary**
+
+Recommendation ITU-T H.248.43 contains several packages to support gate management/control at the boundary of IP domains. These packages allow a media gateway to be configured to filter packets based on rules for different criteria such as source address/port, destination address/port and protocol type. These rules are logically combined and admit/discard the packets matching any or all of them according to the behaviour specification. These filtering policies may be applied on an individual termination or the root termination by the media gateway controller or management action.
+
+## **Source**
+
+Recommendation ITU-T H.248.43 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 applications for gate control/management .....                     | 1  |
+| 2   | Reference .....                                                            | 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   | Model for IP-to-IP interworking.....                                       | 3  |
+| 6.1 | General model for IP-to-IP interworking .....                              | 4  |
+| 6.2 | Relation of general model to the H.248 model for "IP-to-IP" context.....   | 4  |
+| 6.3 | Interaction of different filtering properties.....                         | 5  |
+| 6.4 | Session-dependent versus session-independent gate management/control....   | 5  |
+| 6.5 | Filtering rule interaction between root and individual terminations .....  | 6  |
+| 6.6 | Interaction with IP address latching [ITU-T H.248.37] .....                | 7  |
+| 6.7 | Interaction with IP domains/realms [b-ITU-T H.248.41] .....                | 8  |
+| 7   | Gate management – Source address/port filtering package.....               | 8  |
+| 7.1 | Properties .....                                                           | 8  |
+| 7.2 | Events .....                                                               | 11 |
+| 7.3 | Signals .....                                                              | 11 |
+| 7.4 | Statistics.....                                                            | 11 |
+| 7.5 | Error codes.....                                                           | 12 |
+| 7.6 | Procedures .....                                                           | 12 |
+| 8   | Gate management – Outgoing destination address/port filtering package..... | 13 |
+| 8.1 | Properties .....                                                           | 13 |
+| 8.2 | Events .....                                                               | 15 |
+| 8.3 | Signals .....                                                              | 15 |
+| 8.4 | Statistics.....                                                            | 15 |
+| 8.5 | Error codes.....                                                           | 15 |
+| 8.6 | Procedures .....                                                           | 15 |
+| 9   | Gate management – Incoming protocol filtering package.....                 | 16 |
+| 9.1 | Properties .....                                                           | 16 |
+| 9.2 | Events .....                                                               | 17 |
+| 9.3 | Signals .....                                                              | 17 |
+| 9.4 | Statistics.....                                                            | 18 |
+| 9.5 | Error Codes.....                                                           | 18 |
+| 9.6 | Procedures .....                                                           | 18 |
+
+|                   | Page                                                          |    |
+|-------------------|---------------------------------------------------------------|----|
+| 10                | Gate management – Outgoing protocol filtering package.....    | 20 |
+| 10.1              | Properties.....                                               | 20 |
+| 10.2              | Events .....                                                  | 20 |
+| 10.3              | Signals .....                                                 | 20 |
+| 10.4              | Statistics.....                                               | 20 |
+| 10.5              | Error Codes.....                                              | 21 |
+| 10.6              | Procedures .....                                              | 21 |
+| 11                | Gate management – Incoming filtering behavior package.....    | 21 |
+| 11.1              | Properties.....                                               | 21 |
+| 11.2              | Events .....                                                  | 22 |
+| 11.3              | Signals .....                                                 | 22 |
+| 11.4              | Statistics.....                                               | 22 |
+| 11.5              | Error Codes.....                                              | 22 |
+| 11.6              | Procedures .....                                              | 22 |
+| 12                | Gate management – Outgoing filtering behavior package .....   | 23 |
+| 12.1              | Properties.....                                               | 23 |
+| 12.2              | Events .....                                                  | 24 |
+| 12.3              | Signals .....                                                 | 24 |
+| 12.4              | Statistics.....                                               | 24 |
+| 12.5              | Error Codes.....                                              | 24 |
+| 12.6              | Procedures .....                                              | 24 |
+| Appendix I –      | TISPAN gate management packages.....                          | 25 |
+| I.1               | Gate management package .....                                 | 25 |
+| Appendix II –     | Survey of packages for gate management and gate control ..... | 29 |
+| Appendix III –    | Example policy control commands .....                         | 30 |
+| III.1             | Examples .....                                                | 30 |
+| Bibliography..... |                                                               | 34 |
+
+# Gateway control protocol: Packages for gate management and gate control
+
+# 1 Scope
+
+The gate management and gate control packages define a number of properties to support gate management procedures at the boundary between two Internet protocol (IP) transport domains.
+
+The packages in this Recommendation allow a media gateway (MG) to be configured to filter packets based on rules for different criteria such as source address/port, destination address/port, incoming protocol and/or outgoing protocol. The protocol filtering may be at the IP layer, transport protocol layer, i.e., UDP/TCP or on a higher layer, i.e., HTTP. Once a packet is matched to any or all of the filter rules then the packet may be admitted (received and/or forwarded) or discarded according to the behaviour specification.
+
+These filtering rules have been placed in different packages to allow for different MG configurations to be deployed according to the gate management/control or firewall situation needed.
+
+The filtering rules may be placed on an individual termination or the root termination, thus allowing the filtering policy to be set on a per call/stream basis or on a media gateway as a whole. This policy may be set by the media gateway controller (MGC) or by management action.
+
+## 1.1 Typical applications for gate control/management
+
+Filtering capabilities for IP network infrastructure is a wide topic. This Recommendation supports the flexible definition of many different filter types and combinations of these filters. Such filters may be applied in order to satisfy similar (operational security) requirements for IP traffic as, e.g., outlined by [b-IETF RFC 3871], or to address similar protocol-specific attacks as, e.g., identified by [b-IETF RFC 4778], or to build similar filter structures, e.g., as are being considered by the OPSEC working group of the IETF [b-IETF opsec].
+
+# 2 Reference
+
+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.37] Recommendation ITU-T H.248.37 (2008), *Gateway control protocol: IP NAPT traversal package*.
+- [ITU-T H.248.57] Recommendation ITU-T H.248.57 (2008), *Gateway control protocol: RTP control protocol package*.
+- [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*.
+
+[IETF RFC 3198] IETF RFC 3198 (2001), *Terminology for Policy-Based Management*.  
+<<http://www.ietf.org/rfc/rfc3198.txt>>
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 policy:** [IETF RFC 3198].
+
+**3.1.2 private/local (internal) network** [b-IETF RFC 2663]: A private network is an address realm independent of external network addresses. A private network may also be referred to as a local network. Transparent routing between hosts in private realm and external realm is facilitated by a NAT router.
+
+**3.1.3 public/global/external network** [b-IETF RFC 2663]: A global or public network is an address realm with unique network addresses assigned by Internet Assigned Numbers Authority (IANA) or an equivalent address registry. This network is also referred to as an external network during NAT discussions.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 discarded:** In the context of packet handling, "discarded" refers to the packet not being processed further. No indication will be sent that this has occurred. However, the packet may be counted in certain statistics.
+
+**3.2.2 filter:** In general [IETF RFC 3198]: A set of terms and/or criteria used for the purpose of separating or categorizing. This is accomplished via single- or multi-field matching of traffic header and/or payload data. "Filters" are often manipulated and used in network operation and policy. A filter rule is a specific policy rule.
+
+In an H.248 framework: Packet filters specify the criteria for matching a pattern to distinguish separable classes of traffic. Filters are only related to ephemeral terminations. Filter rules are defined on the basis of H.248 properties.
+
+**3.2.3 filter/policy rules:** In general [IETF RFC 3198]: A basic building block of a policy-based system. It is the binding of a set of actions to a set of conditions, where the conditions are evaluated to determine whether the actions are performed.
+
+In an H.248 framework: The conditions are defined on the basis of H.248 properties, associated to a H.248 termination or/and stream; and the set of actions always contains just a single element per rule, either action "packet forward" or action "packet drop", with or without statistics recording.
+
+NOTE – Definition based on [IETF RFC 3198] and [b-IETF RFC 3060].
+
+**3.2.4 gate:** Gating is implemented through the use of a filter.
+
+NOTE 1 – The [ITU-T RFC 3198] term "policy enforcement point" (PEP) could be associated with the H.248 term "gate". In the user plane, policy enforcement is defined in terms of a "gate". A gate is a policy enforcement function (PEF) that interacts with a policy decision function (PDF). Gate operations are to control and manage media flows based on policy, and are under the control of the PDF. A gate operates on a unidirectional flow of packets, i.e., in either the upstream or downstream direction.
+
+NOTE 2 – A gate may also be referred to as a "pinhole".
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|        |                                                                                         |
+|--------|-----------------------------------------------------------------------------------------|
+| CPU    | Central Processing Unit                                                                 |
+| DP     | Destination Port number                                                                 |
+| IP     | Internet Protocol                                                                       |
+| HTTP   | Hyper Text Transfer Protocol                                                            |
+| L3     | Layer 3                                                                                 |
+| L4     | Layer 4                                                                                 |
+| MG     | Media Gateway                                                                           |
+| MGC    | Media Gateway Controller                                                                |
+| MIB    | Management Information Base                                                             |
+| NAT    | Network Address Translator                                                              |
+| PCI    | Protocol Control Information                                                            |
+| PDF    | Policy Decision Function                                                                |
+| PEF    | Policy Enforcement Function                                                             |
+| PEP    | Policy Enforcement Point                                                                |
+| SNMP   | Simple Network Management Protocol                                                      |
+| RTCP   | Real-time Transport Control Protocol                                                    |
+| RTP    | Real-time Transport Protocol                                                            |
+| SP     | Source Port number                                                                      |
+| TCP    | Transmission Control Protocol                                                           |
+| TISPAN | Telecommunication and Internet converged Services and Protocols for Advanced Networking |
+| TLS    | Transport Layer Security                                                                |
+| UDP    | User Datagram Protocol                                                                  |
+| UDPTL  | Facsimile user Datagram Protocol Transport Layer (protocol)                             |
+
+# 5 Conventions
+
+None.
+
+# 6 Model for IP-to-IP interworking
+
+This Recommendation defines several H.248 packages focused on IP-to-IP connection models (H.248 context type), though they may be used in support of non-IP-to-IP connection models as well (for example, ingress filtering). Definition of a connection model typically goes beyond the scope of a package definition (which considers primarily H.248 streams and terminations; connection models are specified in profile specifications). However, the purpose of this clause is to illustrate one possible IP-to-IP model.
+
+## 6.1 General model for IP-to-IP interworking
+
+The general model is based on a bidirectional IP connection (for the definition, see clause 3.7 of [b-ITU-T H-Sup.7]), comprised of two unidirectional IP flows. It has to be noted that there may be more than one IP flow per direction in real applications. The H.248 MG generally provides a pipeline that may be modelled with four or five (or more) stages per direction in the user plane. Each pipeline stage could be optional in real networks. The existence and specific capability set of each pipeline stage is determined by the specific, applied H.248 implementation (Note) of the IP-to-IP connection.
+
+NOTE – Figure 1 only indicates an example model without any relation to (vendor-specific) implementations.
+
+![Figure 1: General model for IP-to-IP interworking. The diagram shows a bidirectional pipeline within an H.248 Media Gateway. The pipeline is divided into three main sections: L3/L4 functions (left and right), L4+ functions (center), and H.248 Media Gateway (overall container). The L3/L4 functions on the left consist of Packet Filtering: Filter_in, Packet Header Processing, and Packet Filtering: Filter_out. The L4+ functions in the center consist of Media Processing, which is further divided into (1) media-aware path and (2) media-agnostic path. The L3/L4 functions on the right consist of Packet Header Processing and Packet Filtering: Filter_out. Arrows indicate the flow of packets from left to right and right to left through these stages.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+The diagram illustrates the general model for IP-to-IP interworking within an H.248 Media Gateway. It shows a bidirectional pipeline of packet processing stages. The pipeline is divided into three main functional groups: L3/L4 functions (left and right), L4+ functions (center), and the overall H.248 Media Gateway container. The L3/L4 functions on the left include Packet Filtering: Filter<sub>in</sub>, Packet Header Processing, and Packet Filtering: Filter<sub>out</sub>. The L4+ functions in the center include Media Processing, which is further divided into (1) media-aware path and (2) media-agnostic path. The L3/L4 functions on the right include Packet Header Processing and Packet Filtering: Filter<sub>out</sub>. Arrows indicate the flow of packets from left to right and right to left through these stages.
+
+Figure 1: General model for IP-to-IP interworking. The diagram shows a bidirectional pipeline within an H.248 Media Gateway. The pipeline is divided into three main sections: L3/L4 functions (left and right), L4+ functions (center), and H.248 Media Gateway (overall container). The L3/L4 functions on the left consist of Packet Filtering: Filter\_in, Packet Header Processing, and Packet Filtering: Filter\_out. The L4+ functions in the center consist of Media Processing, which is further divided into (1) media-aware path and (2) media-agnostic path. The L3/L4 functions on the right consist of Packet Header Processing and Packet Filtering: Filter\_out. Arrows indicate the flow of packets from left to right and right to left through these stages.
+
+Figure 1 – General model for IP-to-IP interworking
+
+The "L4+ functions" pipeline stage indicates the two principle modes of IP-to-IP interworking:
+
+- 1) **Media-agnostic IP-to-IP:** Functions applied on IP flow are limited on layer 3 (IP; network layer) and layer 4 (transport layer) protocol control information (PCI; i.e., the packet header fields).
+- 2) **Media-aware IP-to-IP:** Functions applied on IP flow may also include higher protocol layers, such as protocol control information of application level framing protocols (e.g., RTP, UDPTL) and/or media itself (relates to the service data unit on application layer, e.g., the RTP payload).
+
+This Recommendation may be applied in both modes of IP interworking (see, e.g., [ITU-T Q.3303.2], which also provides more precise definitions for the IP-to-IP interworking modes).
+
+The scope of this Recommendation relates primarily to the two pipeline stages regarding "packet filtering". Other pipeline stages may be addressed by other Recommendations.
+
+## 6.2 Relation of general model to the H.248 model for "IP-to-IP" context
+
+The H.248 connection model is a single H.248 context with two H.248 IP terminations. The relationship between the context model and the general model is illustrated in Figure 2.
+
+![Diagram illustrating the relation to H.248 'IP-to-IP' context. The diagram shows two terminations, 'T1' and 'T2', connected via a central 'H.248 context'. Each termination contains an 'IP H.248 termination' point (S1) and an 'IP H.248 stream' (T1 or T2). Bidirectional IP connections are shown on the left and right. Below the terminations, a detailed packet processing flow is shown for both incoming and outgoing traffic. Incoming traffic (left to right) passes through 'Packet filtering: Filter_In', 'Packet header processing', and 'Media processing'. Outgoing traffic (right to left) passes through 'Packet header processing', 'Packet filtering: Filter_Out', and 'Media processing'. The diagram is labeled 'H.248.43(08)_F02' at the bottom right.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+Diagram illustrating the relation to H.248 'IP-to-IP' context. The diagram shows two terminations, 'T1' and 'T2', connected via a central 'H.248 context'. Each termination contains an 'IP H.248 termination' point (S1) and an 'IP H.248 stream' (T1 or T2). Bidirectional IP connections are shown on the left and right. Below the terminations, a detailed packet processing flow is shown for both incoming and outgoing traffic. Incoming traffic (left to right) passes through 'Packet filtering: Filter\_In', 'Packet header processing', and 'Media processing'. Outgoing traffic (right to left) passes through 'Packet header processing', 'Packet filtering: Filter\_Out', and 'Media processing'. The diagram is labeled 'H.248.43(08)\_F02' at the bottom right.
+
+**Figure 2 – Relation to H.248 "IP-to-IP" context**
+
+Figure 2 illustrates the specific case of a single H.248 stream per IP termination, whereas the general case may be related to multiple H.248 streams.
+
+## 6.3 Interaction of different filtering properties
+
+Properties defined by packages of this Recommendation detail different filtering conditions, either on incoming packets or outgoing packets. Each property usually defines a condition on a different protocol element.
+
+The general interaction between filtering elements defined by the different properties of a single descriptor is based on a logical "AND" function. That is, for a packet to match the filter, it must match the conditions of all properties belonging to that descriptor. This default behaviour may be modified by the "rules relationship" property in the incoming or outgoing filtering behaviour packages. See clauses 11.6 and 12.6 for further details.
+
+The general filtering behaviour associated with the filtering rules is that packets matching the filter's criteria are admitted, while all other packets are discarded. This default behaviour may be modified by the "filtering mode" property in the incoming or outgoing filtering behaviour packages. See clauses 11.6 and 12.6 for further details.
+
+## 6.4 Session-dependent versus session-independent gate management/control
+
+There are two possible modes of operation:
+
+### Session-dependent gate management/control
+
+All protocol elements as defined by this Recommendation may be applied in the session-dependent mode. The MGC usually signals the H.248 elements on a session-individual basis, e.g., that gateway control activity could be triggered by a superior call/session control protocol, policy control protocol (e.g., protocols at reference points  $Gq'$  in ETSI TISPAN NGN or  $Rs$  in ITU-T NGN) or others.
+
+Session-dependent gate management/control is achieved by applying the protocol elements to the LocalControl descriptor or the Statistics descriptor (as appropriate) of the H.248 stream representing the session. In general, such streams will belong to an IP-based ephemeral termination.
+
+NOTE 1 – In theory, it is possible to apply a filter to all sessions/streams belonging to a single H.248 Termination by applying the protocol elements to the TerminationState descriptor of an ephemeral termination. Such use is for further study and is not covered by this version of the Recommendation.
+
+### **Session-independent gate management/control**
+
+All protocol elements as defined by this Recommendation may also be applied in a session-independent mode. There are three different methods in order to achieve session-independent configurations:
+
+- 1) **Root termination:** The protocol elements defined by this Recommendation may be applied to the TerminationState descriptor or the termination-level Statistics descriptor (as appropriate) of the root termination. See also clause 6.5 for further details.
+- 2) **Default values:** H.248 properties may have a default value assigned, either in an H.248 package itself, or later in an H.248 profile specification. When default values are not overwritten by H.248 signalling, then they have a "session-independent" characteristic.
+- 3) **Configuration management:** H.248 property values may be set via management action from the management system.
+
+NOTE 2 – The provisioning approach may only be relevant for the root termination. A session-independent behaviour via provisioning of ephemeral terminations is theoretically feasible (dependent on the information model used for managed objects), but questionable in practice.
+
+The session-independent mode is inherent in the H.248 protocol architecture, package and profile definition possibilities. The session-independent mode has its merits in various aspects, e.g., in allowing a reduction in the amount of signalling from MGC to MG or the enforcement of "black/white list" filter rules.
+
+## **6.5 Filtering rule interaction between root and individual terminations**
+
+As described previously, it is possible to define both session-independent and session-dependent filters. Session-independent filtering rules are applied at the root termination level, covering the entire gateway. Session-dependent filtering rules are applied at the individual H.248 stream level.
+
+Where filtering rules are applied both on an individual stream and on the root termination, incoming packets will be processed by that stream only if both the root level and the stream level filtering rules admit the packet. Similarly, outgoing packets will be sent by that stream only if both the root level and stream level filtering rules admit the packet. Packets not admitted by both filtering levels are discarded and counted in the relevant H.248 statistic.
+
+The above interaction can be considered as a refinement of the pipeline presented in clause 6.1. Each filtering stage in the pipe is now split in two – a session-independent stage and a session dependent stage. This refinement is presented in Figure 3.
+
+![Figure 3 – Interaction of root and stream level filtering. The diagram shows two flowcharts: 'Incoming Packet Filtering' and 'Outgoing Packet Filtering'. In 'Incoming Packet Filtering', packets flow from left to right through 'Root-Level Filtering (Session-Independent)' and then 'Stream-Level Filtering (Session-Dependent)'. In 'Outgoing Packet Filtering', packets flow from right to left through 'Stream-Level Filtering (Session-Dependent)' and then 'Root-Level Filtering (Session-Independent)'.](af7916c89a458fdab6c3f443217388ae_img.jpg)
+
+```
+
+graph TD
+    subgraph Incoming
+        direction LR
+        R1[Root-Level Filtering  
+(Session-Independent)] --> S1[Stream-Level Filtering  
+(Session-Dependent)]
+    end
+    subgraph Outgoing
+        direction RL
+        S2[Stream-Level Filtering  
+(Session-Dependent)] --> R2[Root-Level Filtering  
+(Session-Independent)]
+    end
+
+```
+
+Figure 3 – Interaction of root and stream level filtering. The diagram shows two flowcharts: 'Incoming Packet Filtering' and 'Outgoing Packet Filtering'. In 'Incoming Packet Filtering', packets flow from left to right through 'Root-Level Filtering (Session-Independent)' and then 'Stream-Level Filtering (Session-Dependent)'. In 'Outgoing Packet Filtering', packets flow from right to left through 'Stream-Level Filtering (Session-Dependent)' and then 'Root-Level Filtering (Session-Independent)'.
+
+**Figure 3 – Interaction of root and stream level filtering**
+
+The MG may return error code 473 "Conflicting property values" if it considers the filtering rules defined on the root level and on the stream level as contradicting each other. The exact definition of contradicting filtering rules is for further study.
+
+## 6.6 Interaction with IP address latching [ITU-T H.248.37]
+
+[ITU-T H.248.37] allows a media gateway controller to control IP *network address and port translation* (NAPT) traversal. Support of NAPT traversal is related to changes of remote IP transport addresses. Such changes could principally affect filter types with address-based policy rules, as defined by packages of this Recommendation. Thus there might be interactions between packet filters and address latching, as also indicated by clause 6.6.7 of [ITU-T H.248.37].
+
+In order to determine the behaviour of an MG with regard to the processing packets where H.248.37 and H.248.43 are both used, the following principle should be followed:
+
+*When a packet is received at a gateway, the filtering policy at layer 4 or below should be applied before the packet is processed by the latching function, and the filtering policy at above layer 4 should be applied after the packet is processed by the latching function. Such filtering policies are set by this Recommendation (or any other Recommendations). Such a latching function is described in [ITU-T H.248.37].*
+
+For example, the H.248.43 source address mask (*sam*) property may be set to allow a range of IP addresses into the MG, e.g., *sam* equals "128.64.32.\*". All packets received from source addresses in this range would be forwarded to the latching function. Latching will then occur on the source address of the first packet received in this range, e.g., "128.64.32.4". Once this latching has occurred, only packets matching both the *sam* and the source address 128.64.32.4 will be admitted for further processing, e.g., the packet header process is defined in Figure 1.
+
+The present IP NAPT traversal package version 1 does *not* support a method that would allow the MGC to enable the MG to make autonomous filter updates, in case of latching or re-latching events. However, given the principle described above, this is not seen as a problem as the address that is latched will always be valid according to the H.248.43 filters, thus only packets matching both H.248.37 and H.248.43 would be admitted.
+
+There is consequently no direct interaction between the technologies of IP NAPT traversal package version 1 and the packages of this Recommendation. If filter updates are required, then it is assumed that the correspondent filter will be indirectly (Note) updated, which means the involvement of the MGC.
+
+NOTE – Indirectly means a two-step procedure: 1) notification of the MGC by the MG in case of events due to latching/re-latching (e.g., based on H.248.37 event *adr/rtac*); 2) this event may trigger filter updates via the modification (by the MGC) of filter property values.
+
+### 6.6.1 Implicit address filtering by address latching
+
+It shall be noted that the latching and re-latching process is accompanied by an implicit address filter, see clause 6.6.3 in [ITU-T H.248.37], acting on the "*remote source transport address*" elements.
+
+## 6.7 Interaction with IP domains/realms [b-ITU-T H.248.41]
+
+For an MG that connects several IP networks, a specific filtering rule should usually be applied only to packets belonging to a specific IP realm. Therefore, some sort of association between filtering rules and realms is necessary.
+
+Session-dependent filtering rules can be easily associated with an IP realm, simply by using the realm of the relevant H.248 stream. Association of root level filtering rules with IP realms is for further study and not covered by this version of the Recommendation.
+
+# 7 Gate management – Source address/port filtering package
+
+Package name: Gate Management  
+Package ID: gm (0x008c)  
+Description: This package defines a number of properties to support gate management procedures at the boundary between two IP transport domains.  
+Version: 2  
+Extends: rtcph (0x00b5) version 1
+
+## 7.1 Properties
+
+### 7.1.1 Remote source address filtering
+
+Property name: Remote Source Address Filtering  
+Property ID: saf (0x0001)  
+Description: This property enables/disables incoming stream filtering based on the source address.  
+Type: Boolean  
+Possible values: ON to enable filtering  
+OFF to disable filtering  
+Default: OFF  
+Defined in: LocalControl on an individual stream or TerminationState on the root termination.  
+Characteristics: Read/write
+
+### 7.1.2 Remote source address mask
+
+Property name: Remote Source Address Mask  
+Property ID: sam (0x0002)  
+Description: This property specifies the incoming stream source address(es) (i.e., IP version 4 or version 6 address) that filtering is applied to.  
+Type: String  
+Possible values: Encoded as = DomainAddress ["/" UINT16]  
+DomainAddress as defined in Annex B of [ITU-T H.248.1]. Character "\*" is used as a wildcard for digits in the DomainAddress, for example "[72.12.207.\*]".  
+Alternatively, a fully specified domain address may be used and a bit mask using slash notation may be specified using the UINT16, for example "[72.14.207.99]/24".  
+Default: None  
+Defined in: LocalControl on an individual stream or TerminationState on the root termination.  
+Characteristics: Read/write
+
+### 7.1.3 Remote source port filtering
+
+Property name: Remote Source Port Filtering  
+Property ID: spf (0x0003)  
+Description: This property enables/disables incoming stream filtering based on the L4 source port.  
+Type: Boolean  
+Possible values: ON to enable filtering  
+OFF to disable filtering  
+Default: OFF  
+Defined in: LocalControl on an individual stream or TerminationState on the root termination.  
+Characteristics: Read/write
+
+### 7.1.4 Remote source port
+
+Property name: Remote Source Port  
+Property ID: spr (0x0004)  
+Description: This property specifies the incoming stream source port(s) that filtering is applied to.  
+Type: Sub-list of Integer  
+Possible values: 0..65535  
+A *single value*, *range* or a *sub-list*. Where a range is provided, a single value from this range will be chosen as per H.248.1 procedures. For where an entire range is to be supported, the *spr* property shall be used.  
+Default: None
+
+Defined in: LocalControl on an individual stream or TerminationState on the root termination.  
+Characteristics: Read/write
+
+### **7.1.5 Explicit source address setting**
+
+Property name: Explicit Source Address Setting  
+Property ID: esas (0x0005)  
+Description: This property indicates if special handling of the source address of packets sent by the termination is required.  
+Type: Boolean  
+Possible values: ON (address is set as specified in local source address property)  
+OFF (address is set to value specified in local descriptor)  
+Default: OFF  
+Defined in: LocalControl on an individual stream or TerminationState on the root termination.  
+Characteristics: Read/write
+
+### **7.1.6 Local source address**
+
+Property name: Local Source Address  
+Property ID: lsa (0x0006)  
+Description: This property indicates the source address to be used in packets sent by the termination.  
+Type: String  
+Possible values: Encoded as a domain address.  
+Default: None  
+Defined in: LocalControl on an individual stream or TerminationState on the root termination.  
+Characteristics: Read/write
+
+### **7.1.7 Explicit source port setting**
+
+Property name: Explicit Source Port Setting  
+Property ID: esps (0x0007)  
+Description: This property indicates if special handling of the source port of packets sent by the termination is required.  
+Type: Boolean  
+Possible values: ON (port is set as specified in local source address property)  
+OFF (port is set to value specified in local descriptor)  
+Default: OFF  
+Defined in: LocalControl on an individual stream or TerminationState on the root termination.  
+Characteristics: Read/write
+
+### **7.1.8 Local source port**
+
+Property name: Local Source Port  
+Property ID: lsp (0x0008)  
+Description: This property indicates the source port to be used in packets sent by the termination.  
+Type: Integer  
+Possible values: 0...65535  
+Default: None  
+Defined in: LocalControl on an individual stream or TerminationState on the root termination.
+
+Characteristics: Read/write
+
+### **7.1.9 Remote source port range**
+
+Property name: Remote Source Port Range  
+Property ID: sprr (0x000a)  
+Description: This property specifies the incoming stream source port(s) in terms of a range (start port, end port) that filtering is applied to. All of the ports within the range and including the start and end port shall be filtered.  
+Type: Sub-list of Integer  
+Possible values: 0...65535  
+The sub-list shall have two instances. The first instance shall be the start of the range. The second instance shall be the end of the range.  
+Default: None  
+Defined in: LocalControl on an individual stream or TerminationState on the root termination.  
+Characteristics: Read/write
+
+## **7.2 Events**
+
+None.
+
+## **7.3 Signals**
+
+None.
+
+## **7.4 Statistics**
+
+### **7.4.1 Discarded packets**
+
+Statistic name: Discarded Packets  
+Statistic ID: dp (0x0001)  
+Description: Contains the number of discarded packets due to source filtering.  
+Type: Integer  
+Possible Values: Integers from 0 upwards  
+Level: Stream (or termination)
+
+## 7.5 Error codes
+
+None.
+
+## 7.6 Procedures
+
+### 7.6.1 Package usage
+
+The use of the package extension mechanism in the gate management package is to enable backward compatibility with the original ETSI specifications in order to address the RTCP handling property through the gate management package identifier.
+
+As such implementers not requiring RTCP handling may implement the gate management (*gm*) without extending the RTCP handling (*rtcph*) package. Clause 6.2.3 of [ITU-T H.248.1] indicates that it is optional to publish the base packages, however, for this Recommendation the base packages shall be published and shall be addressable by their own package identities so that the MGC can determine by auditing whether or not the gate management package supports the RTCP handling.
+
+There are two properties indicating the remote source port (*spr*) and remote source port range (*sprr*) in order to maintain backwards compatibility with the original ETSI specifications. The gate management package version 1 only allowed a single port, a sub-list of port or a single value chosen from a range of ports. The property *sprr* is added to allow multiple ports over a range to be supported.
+
+### 7.6.2 Source address and port filtering
+
+When source filtering is required, the MGC sets the remote source address filtering and remote source port filtering properties to "ON". For each packet received by the termination (from the exterior of the MG), the MG checks whether the source address matches the address mask provided in the remote source address mask (*sam*) property and/or the source ports match the values provided in the remote source port (*spr*) property and/or remote source port range (*sprr*) property. If the MGC sets both the *spr* and *sprr* property, then all the ports described by the properties apply. Any packets that do not match these properties are admitted or discarded (depending on the *ifb/fm* property).
+
+#### 7.6.2.1 Encoding examples for filter configurations
+
+See Appendix III.
+
+### 7.6.3 Explicit source address and port setting
+
+By default, the source address/port of packets sent by the termination is equal to the address and port (specified in the local descriptor) at which packets are received by the termination. This behaviour can be changed by setting the explicit source address setting and explicit source port setting to "ON". The source address/port of packets sent by the termination will then be set to the values specified in the local source address and local source port properties.
+
+### 7.6.4 Filter rule enabling
+
+The application of a filter rule is dependent on both whether or not an address/port filter rule is enabled and whether a value for the address/port filter mask has been provided. There are three principle cases:
+
+- a) Where the *saf* and/or *spf* properties are set to "OFF" (either explicitly or by omitting the property from the LocalControl descriptor), the *gm* package shall not apply any session-dependant filtering based on the remote source address and/or port, respectively. The MG will therefore ignore the setting of the address mask (*sam*) and port (*spr/sprr*) properties.
+
+- b) Where the *saf* and/or *spf* properties are set to "ON" and no value has been provided by the *sam* and/or *spr/spr* properties, the MG will filter any received packets based on address information from the remote descriptor. If the stream is missing a remote descriptor, the MG shall respond with error code 472 "Required information missing".
+- c) Where the *saf* and/or *spf* properties are set to "ON" and values have been provided by the *sam* and/or *spr/spr* properties, the MG will filter any received packets based on the property values, and thus does not consider the address information from the remote descriptor (i.e., precedence of *gm* properties over RD).
+
+# 8 Gate management – Outgoing destination address/port filtering package
+
+Package name: Destination Address/Port Filtering  
+ Package ID: dapf (0x00b6)  
+ Description: This package defines a number of properties that allow the filtering of outgoing IP packets based on their IP destination address and L4 port.  
+ Version: 1  
+ Extends: None
+
+## 8.1 Properties
+
+### 8.1.1 Remote destination address filtering
+
+Property name: Remote Destination Address Filtering  
+ Property ID: daf (0x0001)  
+ Description: This property enables/disables outgoing stream filtering based on the IP destination address.  
+ Type: Boolean  
+ Possible values: ON to enable filtering  
+ OFF to disable filtering  
+ Default: OFF  
+ Defined in: LocalControl on an individual stream or TerminationState on the root termination.  
+ Characteristics: Read/write
+
+### 8.1.2 Remote destination address mask
+
+Property name: Remote Destination Address Mask  
+ Property ID: dam (0x0002)  
+ Description: This property specifies the outgoing stream destination address(es) that filtering is applied to.  
+ Type: String  
+ Possible values: Encoded as = DomainAddress ["/" UINT16]  
+ DomainAddress as defined in Annex B of [ITU-T H.248.1]. Character "\*" is used as a wildcard for digits in the DomainAddress, for example "[72.12.207.\*]".
+
+Alternatively, a fully specified domain address may be used and a bit mask using slash notation may specified using the UINT16, for example "[72.14.207.99]/24".
+
+Default: None  
+Defined in: LocalControl on an individual stream or TerminationState on the root termination.  
+Characteristics: Read/write
+
+### 8.1.3 Remote destination port filtering
+
+Property name: Remote Destination Port Filtering  
+Property ID: dpf (0x0003)  
+Description: This property enables/disables outgoing stream filtering based on the L4 destination port.  
+Type: Boolean  
+Possible values: ON to enable filtering  
+OFF to disable filtering  
+Default: OFF  
+Defined in: LocalControl on an individual stream or TerminationState on the root termination.  
+Characteristics: Read/write
+
+### 8.1.4 Remote destination port
+
+Property name: Remote Destination Port  
+Property ID: dpr (0x0004)  
+Description: This property specifies the outgoing stream destination port(s) that filtering is applied to.  
+Type: Sub-list of Integer  
+Possible values: 0...65535  
+*A single value, range or a sub-list. Where a range is provided, a single value from this range will be chosen as per H.248.1 procedures. For where an entire range is to be supported, the dpr property shall be used.*  
+Default: None  
+Defined in: LocalControl on an individual stream or TerminationState on the root termination.  
+Characteristics: Read/write
+
+### 8.1.5 Remote destination port range
+
+Property name: Remote Destination Port Range  
+Property ID: dpr (0x0009)  
+Description: This property specifies the outgoing stream destination port(s) in terms of a range (start port, end port) that filtering is applied to. All of the ports within the range and including the start and end port shall be filtered.  
+Type: Sub-list of Integer
+
+Possible values: 0...65535
+
+The sub-list shall have two instances. The first instance shall be the start of the range. The second instance shall be the end of the range.
+
+Default: None
+
+Defined in: LocalControl on an individual stream or TerminationState on the root termination.
+
+Characteristics: Read/write
+
+## 8.2 Events
+
+None.
+
+## 8.3 Signals
+
+None.
+
+## 8.4 Statistics
+
+### 8.4.1 Discarded packets
+
+Statistic name: Discarded Packets
+
+Statistic ID: dp (0x0001)
+
+Description: Contains the number of discarded packets due to destination filtering.
+
+Type: Integer
+
+Possible Values: Integers from 0 upwards
+
+Level: Stream (or termination)
+
+## 8.5 Error codes
+
+None.
+
+## 8.6 Procedures
+
+### 8.6.1 Destination address and port filtering
+
+When destination filtering is required, the MGC sets the remote destination address filtering (*daf*) and/or remote destination port filtering (*dpf*) properties to "ON". For each packet sent by the termination (to the exterior of the MG), the MG checks whether the destination address matches the address mask provided in the remote destination address mask (*dam*) property and/or the destination ports match the values provided in the remote destination port (*dpr*) property and/or remote destination port range (*dpr*) property. If the MGC sets both the *dpr* and *dpr* property, then all the ports described by the properties apply. Any packets that do not match these properties are admitted or discarded (depending on the *ofb/fm* property).
+
+### 8.6.2 Filter rule enabling
+
+The application of a filter rule is dependent on both whether or not an address/port filter rule is enabled and whether a value for the address/port filter mask has been provided. There are three principle cases:
+
+- a) Where the *daf* and/or *dpf* properties are set to "OFF" (either explicitly or by omitting the property from the LocalControl descriptor), the *dapf* package shall not apply any session-dependant filtering based on the remote destination address and/or port,
+
+respectively. The MG will therefore ignore the setting of the address mask (*dam*) and port (*dpr/dprr*) properties.
+
+- b) Where the *daf* and/or *dpf* properties are set to "ON" and no value has been provided by the *dam* and/or *dpr/dprr* properties, the MG will filter any received packets based on address information from the remote descriptor. If the stream is missing a remote descriptor, the MG shall respond with error code 472 "Required Information Missing".
+- c) Where the *daf* and/or *dpf* properties are set to "ON" and values have been provided by the *dam* and/or *dpr/dprr* properties, the MG will filter any received packets based on the property values, and thus does not consider the address information from the remote descriptor (i.e., precedence of *dapf* properties over RD).
+
+# 9 Gate management – Incoming protocol filtering package
+
+Package name: Incoming Protocol Filtering
+
+Package ID: ipf (0x00b7)
+
+Description: This package defines a number of properties that allow the filtering of incoming IP packets based on the protocol contained in those packets. The "protocol" is identified by either the layer 3 *protocol type* field, or the layer 4 *IANA registered codepoint*, or both.
+
+NOTE – SDP may be used to indicate the information provided by the *iptm* and *ulptm* properties. However, in certain use cases (i.e., session-independent filters) this may not be practical, thus these properties allow filtering on layer 3 *protocol type* and/or layer 4 *IANA registered codepoint* in these cases.
+
+Version: 1
+
+Extends: None
+
+## 9.1 Properties
+
+### 9.1.1 Protocol type filtering
+
+Property name: Protocol Type Filtering
+
+Property ID: ptf (0x0001)
+
+Description: This property enables/disables the stream filtering based on the protocol type.
+
+Type: Boolean
+
+Possible values: ON to enable filtering  
+OFF to disable filtering
+
+Default: OFF
+
+Defined in: LocalControl on an individual stream or TerminationState on the root termination.
+
+Characteristics: Read/write
+
+### 9.1.2 Internet protocol type mask
+
+Property name: Internet Protocol Type Mask
+
+Property ID: iptm (0x0002)
+
+**Description:** This property specifies the stream Internet protocol types that the filtering is applied to. The *protocol type* here relates to the 8-bit header field called "protocol" in the Internet protocol version 4 (IPv4) or called "next header" field in version 6 (IPv6), e.g., UDP, TCP.
+
+**Type:** Sub-list of Integer
+
+**Possible values:** A *single value*, *range* or a *sub-list*. The value of the protocol is given by the "decimal" associated with the "protocol" assigned by IANA [b-IANA Protocol].
+
+For example:
+
+```
+6   TCP      Transmission Control
+17  UDP      User Datagram
+```
+
+**Default:** None
+
+**Defined in:** LocalControl on an individual stream or TerminationState on the root termination.
+
+**Characteristics:** Read/write
+
+### 9.1.3 Upper layer protocol type mask
+
+**Property name:** Upper Layer Protocol Type Mask
+
+**Property ID:** ulptm (0x0003)
+
+**Description:** This property specifies the stream's upper layer protocols type that the filtering is applied to. The term "upper layer" denotes the protocol layer above the layer 4 transport protocol, i.e., an "upper layer" protocol is a "L4+" protocol, e.g., HTTP or RTP.
+
+**Type:** Sub-list of Integer
+
+**Possible values:** A *single value* or a *sub-list*. The value of the protocol is given by the "decimal" associated with the "description" assigned by IANA for *well known*, *registered*, *dynamic* and *private* ports. The *well known* ports are those from 0 through 1023. The *registered* ports are those from 1024 through 49151. The *dynamic* and/or *private* ports are those from 49152 through 65535 [b-IANA Port].
+
+For example:
+
+```
+80      World Wide Web HTTP
+554     Real Time Streaming Protocol (RTSP)
+5004    Real time Transport Protocol (RTP)
+5005    RTP Control Protocol (RTCP)
+```
+
+**Default:** None
+
+**Defined in:** LocalControl on an individual stream or TerminationState on the root termination.
+
+**Characteristics:** Read/write
+
+## 9.2 Events
+
+None.
+
+## 9.3 Signals
+
+None.
+
+## 9.4 Statistics
+
+None.
+
+## 9.5 Error Codes
+
+None.
+
+## 9.6 Procedures
+
+### 9.6.1 Incoming protocol filtering
+
+When incoming protocol filtering is required, the MGC sets the protocol type filtering (*ipf/ptf*) to "ON". For each packet received by the termination (from the exterior of the MG), the MG checks whether the protocol(s) contained in those packets match(es) the Internet protocol type mask (*ipf/iptm*) and/or the upper layer protocol type mask (*ipf/ulptm*) properties. The MGC may set either of these properties or both. In the case that both these properties are set, the packets must match both of the masks, otherwise the packets are discarded. Any packets that do not match these properties are admitted or discarded (depending on the *ifb/fm* property).
+
+### 9.6.2 Error case
+
+An MGC may try to enable a filter without firstly/synchronously providing a value for the associated filtering rule/mask. On reception of a command resulting in such behaviour, the MG shall respond with error code 472 "Required information missing".
+
+### 9.6.3 Illustrating the semantics for (incoming) protocol filtering
+
+Figure 4 shows *three* filter types with scope on "protocol" filtering (as opposed to the "address" filtering properties of clauses 7 and 8).
+
+The three filter types are different in the following manner:
+
+- A) "Internet protocol" filter:
+  - Protocol information for filter condition: L3 PCI.
+  - H.248 control element: *iptm* property.
+- B) "Transport port" filter:
+  - Protocol information for filter condition: L4 PCI.
+  - H.248 control element: *dapf/dpr* and *dapf/dprr* properties (see clause 9.6.4).
+- C) "Upper Layer Protocol" filter:
+  - Protocol information for filter condition: L4+ PDU.
+  - H.248 control element: *ulptm* property.
+
+The *ipf* package provides, therefore, a solution for A and C. B may be realized with *other* packages. The following clause may help understanding of the preference of C versus B in case of "upper layer protocol" filtering.
+
+#### **a) Filter type: "Internet Protocol" filter**
+
+![Diagram a) Filter type: 'Internet Protocol' filter. It shows a packet structure with L4+ PDU, L4 PCI, and L3 PCI. The L3 PCI contains a 'PCI field: Protocol'. An arrow points from this field to a 'Protocol value' box, which then points to a comparator function (hexagon with '= ?'). The comparator points to a box labeled 'IANA registered protocol number (value = iptm)'.](a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg)
+
+Diagram a) Filter type: 'Internet Protocol' filter. It shows a packet structure with L4+ PDU, L4 PCI, and L3 PCI. The L3 PCI contains a 'PCI field: Protocol'. An arrow points from this field to a 'Protocol value' box, which then points to a comparator function (hexagon with '= ?'). The comparator points to a box labeled 'IANA registered protocol number (value = iptm)'.
+
+An IANA registered port value indicates a specific "upper layer" protocol. "Upper layer" protocol filtering may be then achieved also via "transport port" filtering
+
+#### **b) Filter type: "Transport Port" filter**
+
+![Diagram b) Filter type: 'Transport Port' filter. It shows a packet structure with L4+ PDU, L4 PCI, and L3 PCI. The L4 PCI contains a 'PCI field: Port'. An arrow points from this field to a 'Port value' box, which then points to a comparator function (hexagon with '= ?'). The comparator points to a box labeled 'IANA registered port number (value = ulptm)'.](e354b57563dae469c00b412b2abdf765_img.jpg)
+
+Diagram b) Filter type: 'Transport Port' filter. It shows a packet structure with L4+ PDU, L4 PCI, and L3 PCI. The L4 PCI contains a 'PCI field: Port'. An arrow points from this field to a 'Port value' box, which then points to a comparator function (hexagon with '= ?'). The comparator points to a box labeled 'IANA registered port number (value = ulptm)'.
+
+#### **c) Filter type: "Upper Layer Protocol" filter**
+
+![Diagram c) Filter type: 'Upper Layer Protocol' filter. It shows a packet structure with L4+ PDU, PDU elements, L4 PCI, and L3 PCI. An arrow points from the PDU elements to a 'Message element values' box, which then points to a comparator function (hexagon with '= ?'). The comparator points to a stack of boxes labeled 'Grammar for L4+', 'Grammar for L4+', and 'Grammar for L4+ protocol j'. A note above the grammar boxes states 'Property value of ulptm = index to grammar of checked upper layer protocol'. A note below the comparator states 'Successive grammatical check till unambiguous identification of correct or incorrect L4+ protocol'. The diagram is labeled H.248.43(08)_F04 at the bottom right.](2734e7f9be3e1dc046f14be2e6c9a085_img.jpg)
+
+Diagram c) Filter type: 'Upper Layer Protocol' filter. It shows a packet structure with L4+ PDU, PDU elements, L4 PCI, and L3 PCI. An arrow points from the PDU elements to a 'Message element values' box, which then points to a comparator function (hexagon with '= ?'). The comparator points to a stack of boxes labeled 'Grammar for L4+', 'Grammar for L4+', and 'Grammar for L4+ protocol j'. A note above the grammar boxes states 'Property value of ulptm = index to grammar of checked upper layer protocol'. A note below the comparator states 'Successive grammatical check till unambiguous identification of correct or incorrect L4+ protocol'. The diagram is labeled H.248.43(08)\_F04 at the bottom right.
+
+L3 PCI Internet protocol header  
+ L4 PCI Transport protocol header  
+ L4+ Upper layer (ul)
+
+PCI Protocol Control Information  
+ PDU Protocol Data Unit  
+ (= ?) Comparator function
+
+**Figure 4 – Illustrates the semantics for (incoming) protocol filtering –  
+ Three filter types A, B and C**
+
+### **9.6.4 "Transport port" filter B: relation to other address filtering packages**
+
+The "Gate management – Source address/port filtering" package (see clause 7) and the "Gate management – Outgoing destination address/port filtering" package (see clause 8) have the same capability for filter rules on the layer 4 port codepoint basis as the "transport port" filter B: the L4 PCI element "port". However, any type B filter is out of scope of the *ipf* package, but a type B filter may be realized with the *dapf/dpr* and *dapf/dprr* properties.
+
+#### **9.6.4.1 Pre-condition for usage of the "transport port" filter as "protocol" filter**
+
+The "transport port" filter is basically an "address" filter type, but may be also *reused* as a "protocol" filter under the *condition* that the specified port value is assigned by IANA for *well-known*, *registered*, *dynamic* or *private* ports. The *well-known* ports are those from 0 through 1023. The *registered* ports are those from 1024 through 49151. The *dynamic* and/or *private* ports are those from 49152 through 65535.
+
+The pre-condition is related to the fact that the L4+ PDU content *may correlate* to the L4 PCI *port* value. The L4 PCI *port* value has then the additional semantic of a "*protocol type*" index.
+
+#### 9.6.4.2 Which transport port type: Source or destination?
+
+For "incoming protocol" filtering should then be applied: the 16-bit header field "destination port number" (abbreviated as 'DP') in the IP-based transport protocol.
+
+##### 9.6.4.2.1 Symmetry condition for well known ports?
+
+The values of the DP and source port number (SP) are often identical when using these 16-bit fields for *well known* port codepoints. Such symmetry could simplify port filtering. However, there are also asymmetrical cases concerning the usage of *well known* codepoint.
+
+##### 9.6.4.2.2 Symmetry condition for non-well known ports?
+
+There is not any symmetry condition.
+
+### 9.6.5 Drawback of "transport port" filter B, preference of "upper layer protocol" filter C
+
+Filter B looks very attractive in comparison to C because: a) the filter condition is not going above layer 4; and b) due to resource consumption concerning CPU power and memory. Filter C is a typical "deep message inspection" filter, accompanied by a rather high cost factor.
+
+However, B may be *not applied* when the port is not known in advance, and B has the disadvantage of assuming that the L4+ PDU content is correct. Filter C is directly checking that L4+ PDU content.
+
+# 10 Gate management – Outgoing protocol filtering package
+
+Package name: Outgoing Protocol Filtering
+
+Package ID: opf (0x00b8)
+
+Description: This package defines a number of properties that allow the filtering of outgoing IP packets based on the protocol contained in those packets. The "protocol" is identified by either the layer 3 *protocol type* field, or the layer 4 *IANA registered codepoint*, or both.
+
+NOTE – SDP may be used to indicate the information provided by the *iptm* and *ulptm* properties. However, in certain use cases (i.e., session-independent filters) this may not be practical, thus these properties allow filtering on layer 3 *protocol type* and/or layer 4 *IANA registered codepoint* in these cases.
+
+Version: 1
+
+Extends: None
+
+## 10.1 Properties
+
+As per the incoming protocol filtering package.
+
+## 10.2 Events
+
+None.
+
+## 10.3 Signals
+
+None.
+
+## 10.4 Statistics
+
+None.
+
+## 10.5 Error Codes
+
+None.
+
+## 10.6 Procedures
+
+### 10.6.1 Outgoing protocol filtering
+
+When outgoing protocol filtering is required, the MGC sets the protocol type filtering (*ofp/ptf*) to "ON". For each packet sent by the termination (to the exterior of the MG), the MG checks whether the protocol(s) contained in those packets match(es) the Internet protocol type mask (*ofp/iptm*) and/or the upper layer protocol type mask (*ofp/ulptm*) properties. The MGC may set either of these properties or both. In the case that both these properties are set, the packets must match both of the masks, otherwise the packets are discarded. Any packets that do not match these properties are admitted or discarded (depending on the *ofb/fm* property).
+
+### 10.6.2 Error case
+
+An MGC may try to enable a filter without firstly/synchronously providing a value for the associated filtering rule/mask. On reception of a command resulting in such behaviour, the MG shall response with error code 472 "Required information missing".
+
+# 11 Gate management – Incoming filtering behavior package
+
+Package name: Incoming Filtering Behavior
+
+Package ID: ifb (0x00b9)
+
+Description: This package contains several properties that describe the behaviour of the MG to apply a series of filtering rules on an incoming packet, as well as if the packet matches these filtering rules.
+
+Version: 1
+
+Extends: None
+
+## 11.1 Properties
+
+### 11.1.1 Rules relationship
+
+Property name: Rules Relationship
+
+Property ID: rr (0x0001)
+
+Description: This property indicates the relationship of the filtering rules applied for a particular stream.
+
+Type: Enumeration
+
+Possible values: AND (0x0001) – "Successful matching" means all of the related filtering rules are matched.  
+OR (0x0002) – "Successful matching" means any of the related filtering rules are matched.
+
+Default: AND (0x0001)
+
+Defined in: LocalControl on an individual stream or TerminationState on the root termination.
+
+Characteristics: Read/write
+
+### 11.1.2 Filtering mode
+
+Property name: Filtering Mode  
+Property ID: fm (0x0002)  
+Description: This property indicates the filtering mode applied to streams that match the related filtering rules.  
+Type: Enumeration  
+Possible values: PERMIT (0x0001) – The packet matching the rule(s) is admitted.  
+DENY (0x0002) – The packet matching the rule(s) is discarded.  
+Default: PERMIT (0x0001)  
+Defined in: LocalControl on an individual stream or TerminationState on the root termination.  
+Characteristics: Read/write
+
+## 11.2 Events
+
+None.
+
+## 11.3 Signals
+
+None.
+
+## 11.4 Statistics
+
+None.
+
+## 11.5 Error Codes
+
+None.
+
+## 11.6 Procedures
+
+### 11.6.1 Incoming rules relationship
+
+When a series of filtering rules, e.g., incoming address/port filtering and incoming protocol filtering are applied by the MG on an incoming packet, their relationship for the final result of the checking operation can be controlled via the rules relationship (*ifb/rr*) property. If it is set to "AND", the packet needs to satisfy all of the filtering rules in order to achieve a successful matching result. If it is set to "OR", the packet only needs to satisfy at least one of the filtering rules in order to achieve a successful matching result.
+
+The capabilities of this package only allow:
+
+- a logical AND of all filtering conditions, which are defined by individual properties of the *gm* and *ipf* packages; or
+- a logical OR of all filtering conditions, which are defined by individual properties of the *gm* and *ipf* packages.
+
+Such a logical combination of multiple filtering conditions may be denoted as compound policy (filtering) condition on stream descriptor level (as opposed to below property level condition).
+
+A combination of the filtering conditions by a mixture of logical AND and OR is not supported.
+
+The filtering condition at property level may be itself a compound condition based on a logical OR of a set of values, if the semantics of the property allows it. This logical operation at property level is not affected by the value of the *ifb/rr* property.
+
+NOTE 1 – Compound policy condition at property level can be achieved by applying a specific format of the H.248 data type "sub-list of", when defined for the corresponding property.
+
+For example, if a modify command is issued and:
+
+- the *ipf/iptm* property is set to a sub-list with the values of "6, 17", i.e., [6,17] in ABNF encoding;
+- the *ipf/ulptm* property is set to "80, 554", i.e., {80,554} in ABNF encoding;
+- the *ifb/rr* property is set to "AND".
+
+The MG would first choose either "80" or "554" from the *ipf/ulptm* property due to H.248 procedures that indicate an over-specified list results in a CHOOSE operation. In this example, the MG chooses "80". The MG would then allow incoming packets that utilize one of the Internet protocols specified in the *ipf/iptm* property (this is due to the sub-list) AND also having an upper layer protocol "80" as specified by *ipf/ulptm*.
+
+If, in the above example, the *ifb/rr* property was set to "OR":
+
+The MG would first choose either "80" or "554" from the *ipf/ulptm* property due to H.248 procedures that indicate an over-specified list results in a CHOOSE operation. In this example, the MG chooses "554". The MG would then allow incoming packets that utilize one of the Internet protocols specified in the *ipf/iptm* property (this is due to the sub-list). It would also allow packets that do not match the *ipf/iptm* property if they had an upper layer protocol "554" as specified by *ipf/ulptm*.
+
+NOTE 2 – The example has shown not only the OR-based compound policy condition at property level for the *ipf/iptm* property, but also the use of over-specification in the *ipf/ulptm* property. This is done for illustrative purposes, as the use of over-specification in this case is meaningless.
+
+### 11.6.2 Incoming filtering mode
+
+Depending on the filtering mode (*ifb/fm*) property, the incoming packet, which has successfully matched the related applicable filtering rules with the relationship according to *ifb/rr*, can be admitted or discarded by the MG. If it is set to "PERMIT", the MG shall only admit the packets that successfully match the related applicable filtering rules, and discard any other packets. If it is set to "DENY", the MG shall discard packets that successfully match the related applicable filtering rules, and admit any other packets.
+
+If an MG cannot support a filter condition, error code "449 – Unsupported or unknown parameter or property value" is returned.
+
+# 12 Gate management – Outgoing filtering behavior package
+
+Package name: Outgoing Filtering Behavior  
+Package ID: ofb (0x00ba)  
+Description: This package contains several properties that describe the behaviour of the MG to apply a series of filtering rules on an outgoing packet, as well as if the packet matches these filtering rules.  
+Version: 1  
+Extends: None
+
+## 12.1 Properties
+
+As per incoming filtering behavior package.
+
+## 12.2 Events
+
+None.
+
+## 12.3 Signals
+
+None.
+
+## 12.4 Statistics
+
+None.
+
+## 12.5 Error codes
+
+None.
+
+## 12.6 Procedures
+
+### 12.6.1 Outgoing rules relationship
+
+When a series of filtering rules, e.g., outgoing address/port filtering and outgoing protocol filtering, are applied by the MG on an outgoing packet, their relationship for the final result of the checking operation can be controlled via the rules relationship (*ofb/rr*) property. If it is set to "AND", the packet needs to satisfy all of the filtering rules in order to achieve a successful matching result. If it is set to "OR", the packet only needs to satisfy at least one of the filtering rules in order to achieve a successful matching result.
+
+The capabilities of this package only allow:
+
+- a logical AND of all filtering conditions, which are defined by individual properties of the *dapf* and *opf* packages; or
+- a logical OR of all filtering conditions, which are defined by individual properties of the *dapf* and *opf* packages.
+
+Such a logical combination of multiple filtering conditions may be denoted as compound policy (filtering) condition on stream descriptor level (as opposed to below property level condition).
+
+A combination of the filtering conditions by a mixture of logical AND and OR is not supported.
+
+The filtering condition at property level may be itself a compound condition based on a logical OR of a set of values, if the semantics of the property allows it. This logical operation at property level is not affected by the value of the *ofb/rr* property.
+
+NOTE – Compound policy condition at property level can be achieved by applying a specific format of the H.248 data type "sub-list of", when defined for the corresponding property.
+
+### 12.6.2 Outgoing filtering mode
+
+Depending on the filtering mode (*ofb/fm*) property, the outgoing packet, which has successfully matched the related applicable filtering rules with the relationship according to *ofb/rr*, can be admitted or discarded by the MG. If it is set to "PERMIT", the MG shall only admit the packets that successfully match the related applicable filtering rules, and discard any other packets. If it is set to "DENY", the MG shall discard packets that successfully match the related applicable filtering rules, and admit any other packets.
+
+If a MG cannot support a filter condition error code "449 – Unsupported or unknown parameter or property value" is returned.
+
+# Appendix I
+
+## TISPAN gate management packages
+
+(This appendix does not form an integral part of this Recommendation)
+
+This appendix contains a copy of the original version of the ETSI TISPAN gate management package for the information of implementers.
+
+## I.1 Gate management package
+
+Package name: Gate Management  
+Package ID: gm (0x008c) – value allocated by IANA  
+Description: This package defines a number of properties to support gate management procedures at the boundary between two IP transport domains.  
+NOTE – This package was originally defined in Annex B of [b-ETSI TS 102 333 V1.1.2], later corrected by [b-ETSI TS 102 333 V1.2.0].  
+Version: 1  
+Extends: rtcph (0x00b5) version 1
+
+### I.1.1 Properties
+
+#### I.1.1.1 Remote source address filtering
+
+Property name: Remote Source Address Filtering  
+Property ID: saf (0x0001)  
+Description: This property indicates whether source address filtering shall be enforced.  
+Type: Boolean  
+Possible values: ON (enforce source filtering)  
+OFF (no source filtering)  
+Default: OFF  
+Defined in: LocalControl  
+Characteristics: Read/write
+
+#### I.1.1.2 Remote source address mask
+
+Property name: Remote Source Address Mask  
+Property ID: sam (0x0002)  
+Description: This property indicates which source addresses are accepted for packets received by the termination.  
+Type: String  
+Possible values: Encoded as a DomainAddress.  
+DomainAddress is defined in Annex B of [ITU-T H.248.1]. "\*" is used as a wildcard for digits in the DomainAddress, for example "[72.12.207.\*]".  
+Default: None  
+Defined in: LocalControl  
+Characteristics: Read/write
+
+#### **I.1.1.3 Remote source port filtering**
+
+Property name: Remote Source Port Filtering  
+Property ID: spf (0x0003)  
+Description: This property indicates whether source port filtering shall be enforced.  
+Type: Boolean  
+Possible values: ON (enforce source filtering)  
+OFF (no source filtering)  
+Default: OFF  
+Defined in: LocalControl  
+Characteristics: Read/write
+
+#### **I.1.1.4 Remote source port**
+
+Property name: Remote Source Port  
+NOTE – Formerly "Remote Source Port Range". The name was changed as the former property name was misleading because the coding only represents a single port value.  
+Property ID: spr (0x0004)  
+Description: This property indicates the allowed source port value for packets received by the termination.  
+Type: Integer  
+Possible values: 0 through 65535  
+Default: None  
+Defined in: LocalControl  
+Characteristics: Read/write
+
+#### **I.1.1.5 Explicit source address setting**
+
+Property name: Explicit Source Address Setting  
+Property ID: esas (0x0005)  
+Description: This property indicates if special handling of the source address of packets sent by the termination is required.  
+Type: Boolean  
+Possible values: ON (address is set as specified in local source address property)  
+OFF (address is set to value specified in local descriptor)  
+Default: OFF  
+Defined in: LocalControl  
+Characteristics: Read/write
+
+#### **I.1.1.6 Local source address**
+
+Property name: Local Source Address  
+Property ID: lsa (0x0006)  
+Description: This property indicates the source address to be used in packets sent by the termination.
+
+Type: String  
+Possible values: Encoded as a domain address.  
+Default: None  
+Defined in: LocalControl  
+Characteristics: Read/write
+
+#### **I.1.1.7 Explicit source port setting**
+
+Property name: Explicit Source Port Setting  
+Property ID: esps (0x0007)  
+Description: This property indicates if special handling of the source port of packets sent by the termination is required.  
+Type: Boolean  
+Possible values: ON (port is set as specified in local source address property)  
+OFF (port is set to value specified in local descriptor)  
+Default: OFF  
+Defined in: LocalControl  
+Characteristics: Read/write
+
+#### **I.1.1.8 Local source port**
+
+Property name: Local Source Port  
+Property ID: lsp (0x0008)  
+Description: This property indicates the source port to be used in packets sent by the termination.  
+Type: Integer  
+Possible values: 0 through 65535  
+Default: None  
+Defined in: LocalControl  
+Characteristics: Read/write
+
+### **I.1.2 Events**
+
+None.
+
+### **I.1.3 Signals**
+
+None.
+
+### **I.1.4 Statistics**
+
+#### **I.1.4.1 Discarded packets**
+
+Statistic name: Discarded Packets  
+Statistic ID: dp (0x0001)  
+Description: Contains the number of discarded packets due to source filtering.  
+Type: Number of packets  
+Possible values:  
+Level:
+
+### **I.1.5 Error codes**
+
+None.
+
+### **I.1.6 Procedures**
+
+#### **I.1.6.1 Source filtering**
+
+When source filtering is required, the MGC sets the remote source address filtering and remote source port properties to TRUE. For each packet received by the termination (from the exterior of the equipment), the MG checks whether the source address and ports match the address mask and value range provided in the remote source address mask and remote source port range properties. Packets that do not match these properties are discarded.
+
+#### **I.1.6.2 Explicit address setting**
+
+By default, the source address/port of packets sent by the termination is equal to the address and port (specified in the local descriptor) at which packets are received by the termination. This behaviour can be changed by setting the explicit source address setting and explicit source port setting to ON. The source address/port of packets sent by the termination will then be set to the values specified in the local source address and local source port properties.
+
+#### **I.1.6.3 Specific RTCP banding**
+
+When the MG is requested to allocate/deallocate a port for an RTP stream, a consecutive port for the associated RTCP flow is automatically allocated/deallocated if the RTP-specific behaviour property is set to ON.
+
+# Appendix II
+
+## Survey of packages for gate management and gate control
+
+(This appendix does not form an integral part of this Recommendation)
+
+This appendix contains the landscape of existent packages for gate management and gate control. Packages gm version 1 and gm version 2 are extension packages of rtcph v1 [ITU-T H.248.57]. All other packages are stand-alone packages.
+
+![Diagram showing the relationship between various packages for gate management and gate control. It includes gm v1, rtcph v1, gm v2, dapf v1, ipf v1, opf v1, ifb v1, and ofb v1, with their respective properties and sections in H.248.43.](9870bf462aa0d916a16d14b5a100c60a_img.jpg)
+
+The diagram illustrates the hierarchy and relationships of various packages for gate management and gate control. It is organized into two main areas: **H.248.43, Appendix I** and **Main body of H.248.43**.
+
+- H.248.43, Appendix I**:
+  - gm v1**: 8 properties: saf, sam, spf, spr, esas, lsa, esps, lsp.
+  - rtcph v1**: 1 property: rsb. This package is referenced by gm v1 and gm v2.
+- Main body of H.248.43**:
+  - Source Address/Port Filtering**:
+    - gm v2**: 9 properties: saf, sam, spf, spr, esas, lsa, esps, lsp, sprr. This package is referenced by gm v1 and gm v2.
+  - Outgoing Destination Address/Port Filtering**:
+    - dapf v1**: 4 properties: daf, dam, dpf, dpr.
+  - Incoming Protocol Filtering**:
+    - ipf v1**: 3 properties: ptf, iptm, ulptm.
+  - Outgoing Protocol Filtering**:
+    - opf v1**: 3 properties (= ipf): ptf, iptm, ulptm.
+  - Incoming Filtering Behavior**:
+    - ifb v1**: 2 properties: rr, fm.
+  - Outgoing Filtering Behavior**:
+    - ofb v1**: 2 properties (= ifb): rr, fm.
+
+Diagram showing the relationship between various packages for gate management and gate control. It includes gm v1, rtcph v1, gm v2, dapf v1, ipf v1, opf v1, ifb v1, and ofb v1, with their respective properties and sections in H.248.43.
+
+NOTE: only package properties are indicated.
+
+Figure II.1 – Overview of packages for gate management and gate control
+
+# Appendix III
+
+## Example policy control commands
+
+(This appendix does not form an integral part of this Recommendation)
+
+The main body of this Recommendation supports the control or management of both *simple* and *compound* policy conditions:
+
+- A *simple* policy condition specifies the equality (in the sense of a particular *matching rule*) of a certain field in the IP packet to a predefined value as a filtering criterion, e.g., IPv4 source address = 222.222.222.222.
+
+NOTE 1 – This is an exact match condition.
+
+- A *compound* policy condition specifies a combination of simple policy conditions with a logical AND or a logical OR as the filtering criterion for all individual simple policy conditions, e.g., IPv4 source address = 222.222.222.222 AND L4 source port = 15.
+
+NOTE 2 – Again, two exact match conditions in this example.
+
+The policy conditions can be controlled and managed at H.248 property level and at H.248 stream descriptor level.
+
+The compound policy condition on stream descriptor level is supported in this Recommendation by the rules relationship property *ifb/rr* to the incoming filtering. With this property, the filtering criteria specified with individual properties can be combined into a compound policy condition.
+
+NOTE 3 – The same is applicable to the outgoing filtering conditions with the *ofb/rr* property.
+
+However, a filtering criterion specified by an individual property can itself represent a compound policy condition (on property level), if a list of values is provided. By that, the condition is specified as the equality of a field in the IP packet to one of the values specified in the list, thus a logical OR, e.g., source port = [7] OR source port = [15] is implied.
+
+NOTE 4 – "Implied" due to the applied "sub-list" syntax.
+
+## III.1 Examples
+
+### III.1.1 Example for "IP application" protocol and transport protocol-aware filter patterns
+
+There might be the requirement for policing of SIP traffic on the ingress side. In this scenario, the SIP traffic uses the IANA registered port values and is transported over UDP or TCP, and is either unsecured or secured via TLS.
+
+The aimed overall filter behaviour may be outlined by the following example of pseudo code-based description:
+
+```
+#### Logic for policy (filter) rule ####
+
+Hx = value of IP header field "protocol"      ; type INTEGER
+Hy = value of L4 header field "source port"    ; type INTEGER
+
+IF
+    ((Hx = 6) OR (Hx = 17))                ; compound policy condition on property level
+    AND                                     ; compound policy condition on Stream D. level
+    ((Hy = 5060) OR (Hy = 5061))          ; compound policy condition on property level
+    ; filtering mode policy condition leads to following order of actions
+THEN
+    accept packet      ; policy action A1
+ELSE
+    discard packet     ; policy action A2
+```
+
+#### III.1.1.1 Example with efficient H.248 signalling
+
+Table III.1 provides an example policy control command.
+
+**Table III.1 – Compound policy condition for SIP policing with different transports and security mechanisms**
+
+| <b>H.248 text encoding example</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <pre>H.248 request: Add = ip/3/realm1/\$ {   Media {     Stream = 1 {      ; filter on stream level       LocalControl {         ...         ; <b>policy condition #1</b> "ingress source port filter"         gm/spf = ON,         gm/spr = [5060, 5061],                      ; NOTE 1         ; <b>policy condition #2</b> "ingress L4 protocol type"         ipf/ptf = ON,         ipf/iptm = [6, 17],                         ; NOTE 2         ; <b>Rules relationship</b> on Stream D. level for <b>compound policy condition</b>         ; for <i>incoming</i> IP packets         ifb/rr   = AND,                             ; NOTE 3         ifb/fm   = PERMIT                            ; NOTE 4         ...       }     }   } }</pre> <p>NOTE 1 – Compound policy condition on property level: Two-field pattern – OR-based list of source port numbers.<br/>NOTE 2 – Compound policy condition on property level: Two-field pattern – OR-based list of protocol values for TCP and UDP.<br/>NOTE 3 – AND-based compound policy condition on stream descriptor level defined by rules relationship for ingress filter patterns.<br/>NOTE 4 – The packet is <i>accepted</i> only when matching the compound policy condition on stream descriptor level for ingress traffic.</p> |
+
+The *gm/spr* property defines a list of individual values where the value range is consecutive; alternatively, the *gm/sprr* property may be applied, see Table III.2.
+
+**Table III.2 – Compound policy condition for SIP policing – Alternative to Table III.1**
+
+| <b>H.248 text encoding example</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <pre>H.248 request: Add = ip/3/realm1/\$ {   Media {     Stream = 1 {      ; filter on stream level       LocalControl {         ...         ; <b>policy condition #1</b> "ingress source port filter"         gm/spf = ON,         gm/sprr = [5060, 5061],         ; <b>policy condition #2</b> "ingress L4 protocol type"         ipf/ptf = ON,         ipf/iptm = [6, 17],         ; <b>Rules relationship</b> on Stream D. level for <b>compound policy condition</b>         ; for <i>incoming</i> IP packets         ifb/rr = AND,         ifb/fm = DENY         ...       }     }   } }</pre> |
+
+### III.1.2 Alternative approach: Filtering of upper layer protocol
+
+As an alternative approach, SIP traffic may be filtered based on the SIP syntax contained in the packet's payload instead of the source port. The aimed overall filter behaviour may be outlined by the following example pseudo code-based description:
+
+```
+#### Logic for policy (filter) rule ####
+
+Hx = value of IP header field "protocol"           ; type INTEGER
+Hy = value of L4 header field "source port"         ; type INTEGER
+
+IF
+  ((Hx = 6) OR (Hx = 17))           ; compound policy condition on property level
+  AND                                     ; compound policy condition on Stream D. level
+  ((Hy = SIP) OR (Hy = SIP-TLS)) ; compound policy condition on property level
+  ; filtering mode policy condition leads to following order of actions
+THEN
+  accept packet           ; policy action A1
+ELSE
+  discard packet          ; policy action A2
+```
+
+Table III.3 provides an example policy control command. Note that this example still contains the registered port numbers; however, this time they are decimal values representing the SIP and SIP-TLS protocol themselves.
+
+**Table III.3 – Compound policy condition for SIP policing –  
+Alternative to Table III.1 with decimal values  
+representing SIP/SIP-TLS protocol**
+
+| <b>H.248 text encoding example</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <pre>H.248 request: Add = ip/3/realm1/\$ {   Media {     Stream = 1 {           ; filter on stream level       LocalControl {         ...         ; policy condition #1 "ingress L4 protocol and upper layer protocol"         ipf/ptf = ON,         ipf/iptm = [6, 17],           ; L4 protocol types, NOTE 1         ipf/ulptm = [5060, 5061],           ; upper layer protocol types, NOTE 2         ; Rules relationship on Stream D. level for compound policy condition         ; for incoming IP packets         ifb/rr = AND,         ifb/fm = PERMIT         ...       }     }   } }</pre> |
+| <p>NOTE 1 – Compound policy condition on property level: Two-field pattern – OR-based list of L4 protocol values for TCP and UDP.</p> <p>NOTE 2 – Compound policy condition on property level: Two-field pattern – OR-based list of registered port values. These port values represent the upper layer protocols of SIP and SIP-TLS.</p>                                                                                                                                                                                                                                                           |
+
+### III.1.3 Example for a more complex compound policy condition
+
+Table III.4 provides an example using all properties of this Recommendation for filter pattern definitions.
+
+**Table III.4 – Compound policy condition with six enabled multi-field filter patterns –  
+Each example with different Boolean combinations**
+
+| <b>H.248 text encoding example</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |  |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|
+| <pre> H.248 request: Add = ip/3/realm1/\$ {   Media {     Stream = 1 {      ; filter on stream level       LocalControl {         ...         ; <b>policy condition #1</b> "ingress source address filter"         gm/saf = ON,         gm/sam = "[101.0.*.0]" ,                      ; NOTE 1         ; <b>policy condition #2</b> "ingress source port filter"         gm/spf = ON,         gm/spr = [23, 14, 19999, 25000],              ; NOTE 2         gm/spr = [1442, 1490],                        ; NOTE 3         ; <b>policy condition #3</b> "egress destination address filter"         dapf/daf = ON,         dapf/dam = "[12.8.3.0]/12",                   ; NOTE 4         ; <b>policy condition #4</b> "egress destination port filter"         dapf/dpf = ON,         dapf/dpr = [153, 155, 157, 159, 161],          ; NOTE 5         dapf/dpr = [732, 789],                        ; NOTE 6         ; <b>policy condition #5</b> "ingress protocol type and well known port filter"         ipf/ptf = ON,         ipf/iptm = [21, 23, 25, 69, 79],              ; protocol types, NOTE 7         ipf/ulptm = [5060, 5061],                     ; port values, NOTE 8         ; <b>policy condition #6</b> "egress protocol type and well known port filter"         opf/ptf = ON,         opf/iptm = [1, 5, 7, 9, 49, 53],              ; protocol types, NOTE 9         opf/ulptm = [80, ,83, 15444],                 ; port values, NOTE 10         ; <b>Rules relationship</b> on Stream D. level for <b>compound policy condition</b>         ; Rules relationship #1 for <i>incoming</i> IP packets         ifb/rr = OR,                                    ; NOTE 11         ifb/fm = PERMIT,                                ; NOTE 12         ; Rules relationship #2 for <i>outcoming</i> IP packets         ofb/rr = AND,                                   ; NOTE 13         ofb/fm = DENY                                    ; NOTE 14         ...       }}}} </pre> |  |
+| NOTE 1 – One wildcarded IPv4 address.<br>NOTE 2 – Four-field pattern – List of four ORed individual port values.<br>NOTE 3 – Range of port values is indicated by two periods (start and end value).<br>NOTE 4 – One bit-masked IPv4 address.<br>NOTE 5 – Five-field pattern – List of five ORed individual port values.<br>NOTE 6 – Range of port values is indicated by two periods (start and end value).<br>NOTE 7 – Five-field pattern – ORed list of protocol values for FTP, TELNET, SMTP, TFTP and FINGER.<br>NOTE 8 – Two-field pattern – ORed list of port values for SIP and SIP-TLS.<br>NOTE 9 – Six-field pattern – ORed list of protocol type values.<br>NOTE 10 – Three-field pattern – ORed list of upper layer protocol types.<br>NOTE 11 – OR-based compound policy condition defined by rules relationship for ingress traffic.<br>NOTE 12 – The packet is <i>admitted</i> when matching the compound policy condition for ingress traffic.<br>NOTE 13 – AND-based compound policy condition defined by rules relationship for egress traffic.<br>NOTE 14 – The packet is <i>discarded</i> when matching the compound policy condition for egress traffic.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |  |
+
+# Bibliography
+
+- [b-ITU-T H.248.41] Recommendation ITU-T H.248.41 (2006), *Gateway control protocol: IP domain connection package*.
+- [b-ITU-T Y.1291] Recommendation ITU-T Y.1291 (2004), *An architectural framework for support of Quality of Service in packet networks*.
+- [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-IANA Port] IANA port numbers. <<http://www.iana.org/assignments/port-numbers>>
+- [b-IANA Protocol] IANA protocol numbers. <<http://www.iana.org/assignments/protocol-numbers>>
+- [b-ETSI TS 102 333 V1.2.0] ETSI TS 102 333 V1.2.0 (2007), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) ; Gate control protocol*.  
+<[http://pda.etsi.org/pda/home.asp?wiki\\_id=IBFKFHFozrtyustccH3B](http://pda.etsi.org/pda/home.asp?wiki_id=IBFKFHFozrtyustccH3B)>
+- [b-ETSI TS 102 333 V.1.1.2] ETSI TS 102 333 V1.1.2 (2004), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) ; Gate control protocol*.  
+<[http://pda.etsi.org/pda/home.asp?wiki\\_id=IBFKFHFozrtyustccH3B](http://pda.etsi.org/pda/home.asp?wiki_id=IBFKFHFozrtyustccH3B)>
+- [b-IETF RFC 2663] IETF RFC 2663 (1999), *IP Network Address Translator (NAT) Terminology and Considerations*.  
+<<http://www.ietf.org/rfc/rfc2663.txt>>
+- [b-IETF RFC 3060] IETF RFC 3060 (2001), *Policy Core Information Model – Version 1 Specification*.  
+<<http://www.ietf.org/rfc/rfc3060.txt>>
+- [b-IETF RFC 3871] IETF RFC 3871 (2004), *Operational Security Requirements for Large Internet Service Provider (ISP) IP Network Infrastructure*.  
+<<http://www.ietf.org/rfc/rfc3871.txt>>
+- [b-IETF RFC 4778] IETF RFC 4778 (2007), *Current Operational Security Practices in Internet Service Provider Environments*.  
+<<http://www.ietf.org/rfc/rfc4778.txt>>
+- [b-IETF opsec] IETF Opsec status page. <<http://tools.ietf.org/wg/opsec/>>
+
+
+
+# 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.44-200701-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.44-200701-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c
--- /dev/null
+++ b/marked/H/T-REC-H.248.44-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.248.44-200701-I_PDF-E/64174d87840762a4cadffcfdc8a5fb21_img.jpg b/marked/H/T-REC-H.248.44-200701-I_PDF-E/64174d87840762a4cadffcfdc8a5fb21_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5d3bffddd1453bab55cdae6586f545ab598dc467
--- /dev/null
+++ b/marked/H/T-REC-H.248.44-200701-I_PDF-E/64174d87840762a4cadffcfdc8a5fb21_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:68868ae8259819e27463ebab5546d62144a9b661d53ea3fa9154843a57008d0a
+size 2062
diff --git a/marked/H/T-REC-H.248.46-200701-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/H/T-REC-H.248.46-200701-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d8ba0c643f201daf50e4c180a4ed4d0c580ca773
--- /dev/null
+++ b/marked/H/T-REC-H.248.46-200701-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eee1d59880537505311be40f18663fed26ff1e837ce8b9a874b1e2a042142b8f
+size 26398
diff --git a/marked/H/T-REC-H.248.46-200701-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.248.46-200701-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..83797433997b8a6298ffeb2e97719acfd404d72c
--- /dev/null
+++ b/marked/H/T-REC-H.248.46-200701-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f60522ea65d93b6e46f1f896a23417f09599b2220a6d8286fca2aeee0d868897
+size 8282
diff --git a/marked/H/T-REC-H.248.46-200701-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg b/marked/H/T-REC-H.248.46-200701-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..065cec4437fc14829130e41a38fbd46c46c9373a
--- /dev/null
+++ b/marked/H/T-REC-H.248.46-200701-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8835f07639a3e947458c4cd62f527bc3454d525352bbbcbf3f8808a05c0c4548
+size 44692
diff --git a/marked/H/T-REC-H.248.47-200807-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.248.47-200807-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bf54140d721426c758ed93a03767e7ac220be214
--- /dev/null
+++ b/marked/H/T-REC-H.248.47-200807-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:50a5f072eda0f001f71a1a7e592c02d3b847e459e3d4437909954faed0b53e21
+size 6925
diff --git a/marked/H/T-REC-H.248.49-200708-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.49-200708-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a
--- /dev/null
+++ b/marked/H/T-REC-H.248.49-200708-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.49-200708-I_PDF-E/51db757d054ce1ce83c436a3578b56ca_img.jpg b/marked/H/T-REC-H.248.49-200708-I_PDF-E/51db757d054ce1ce83c436a3578b56ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e0217cb29cafc8010c540bcad4c97ace920cc4f5
--- /dev/null
+++ b/marked/H/T-REC-H.248.49-200708-I_PDF-E/51db757d054ce1ce83c436a3578b56ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:92f9d774f488cffa1a360476634d7d21752bceb85fe4303cdb3c996d413a10a0
+size 124702
diff --git a/marked/H/T-REC-H.248.50-201607-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.50-201607-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..827609df9ad8667ae079f875841506349f063390
--- /dev/null
+++ b/marked/H/T-REC-H.248.50-201607-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.50-201607-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg b/marked/H/T-REC-H.248.50-201607-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..719065290d1fdc3c7f7eb67885a94ca6eda23e87
--- /dev/null
+++ b/marked/H/T-REC-H.248.50-201607-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1057d8178a677767b0532d894cc13a393dd7ddd1fdb703884d72548a6bdcc51f
+size 110210
diff --git a/marked/H/T-REC-H.248.50-201607-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/H/T-REC-H.248.50-201607-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0e8134febc93eea0225337f15889b99b9f6abf7e
--- /dev/null
+++ b/marked/H/T-REC-H.248.50-201607-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c460989c217a2e524a4fef9363a31d235e8bf35fd080fd0968ecc46835c68568
+size 113667
diff --git a/marked/H/T-REC-H.248.50-201607-I_PDF-E/408c4798ea60469e0728a7cbbd598668_img.jpg b/marked/H/T-REC-H.248.50-201607-I_PDF-E/408c4798ea60469e0728a7cbbd598668_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7687d00b2dc55362fa0fccaff965a45244b2f6a8
--- /dev/null
+++ b/marked/H/T-REC-H.248.50-201607-I_PDF-E/408c4798ea60469e0728a7cbbd598668_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2fcaced9e9b0e70a5a6ec3ca41bc3986e1e11cbb554a33937689919225fccd71
+size 134704
diff --git a/marked/H/T-REC-H.248.50-201607-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/H/T-REC-H.248.50-201607-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9e84a326bd5107ea8a6a0339c463c828b174cc68
--- /dev/null
+++ b/marked/H/T-REC-H.248.50-201607-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:610d5beebc2c59b2c41ae43443753f6111f77fa5a024848f3284a7314e399b8d
+size 98489
diff --git a/marked/H/T-REC-H.248.50-201607-I_PDF-E/91b12db3c85bbf466ad27eb3665a1b06_img.jpg b/marked/H/T-REC-H.248.50-201607-I_PDF-E/91b12db3c85bbf466ad27eb3665a1b06_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f5e701f6c6b05abe623bfa7ede597656e602c7e6
--- /dev/null
+++ b/marked/H/T-REC-H.248.50-201607-I_PDF-E/91b12db3c85bbf466ad27eb3665a1b06_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cec0d4a89969a3cf8661f9ced284b1190c99b35dc33dd202040b968471de0a0c
+size 51311
diff --git a/marked/H/T-REC-H.248.50-201607-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/H/T-REC-H.248.50-201607-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..30516c63585413f27bf261f363dfcc39fd17ab14
--- /dev/null
+++ b/marked/H/T-REC-H.248.50-201607-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:231b8b6a17671317e4a1a3b01f7e571119c9ef3953c7498dff7023dd5b01c051
+size 97850
diff --git a/marked/H/T-REC-H.248.50-201607-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg b/marked/H/T-REC-H.248.50-201607-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b35e950bf1393d4447f354e008582cbd99df2c93
--- /dev/null
+++ b/marked/H/T-REC-H.248.50-201607-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c5dd1f93e789df270bd7742a8ce997726799c519c1d3973c108cf209faddb2c8
+size 108844
diff --git a/marked/H/T-REC-H.248.50-201607-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.248.50-201607-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..317afe469c976744d580e3130fe1cb270ba86e61
--- /dev/null
+++ b/marked/H/T-REC-H.248.50-201607-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a7cf9e164fbf6497977776f06dca7906e51c317aa9a293505c163df5dfd1d445
+size 92751
diff --git a/marked/H/T-REC-H.248.51-200708-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.51-200708-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a
--- /dev/null
+++ b/marked/H/T-REC-H.248.51-200708-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.51-200708-I_PDF-E/2e399449b7f62d40167a65ca88888917_img.jpg b/marked/H/T-REC-H.248.51-200708-I_PDF-E/2e399449b7f62d40167a65ca88888917_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b0d8060ea02c4132bbf3d282c91b5353fe196abe
--- /dev/null
+++ b/marked/H/T-REC-H.248.51-200708-I_PDF-E/2e399449b7f62d40167a65ca88888917_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:89b5ee6424c788ae86f49af193e6925ae57ce6310c04fdd458fa7a6fe61684c3
+size 14453
diff --git a/marked/H/T-REC-H.248.51-200708-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg b/marked/H/T-REC-H.248.51-200708-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fa8413431b29bb05bbb4c3b554c94f1ff975e4e4
--- /dev/null
+++ b/marked/H/T-REC-H.248.51-200708-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:773e8f26564a8f85165338f2f63b32a86fcb15b73da2aa821bbaf145747c4279
+size 15536
diff --git a/marked/H/T-REC-H.248.51-200708-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/H/T-REC-H.248.51-200708-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b9771842d0d6183cc66aae063773973671552003
--- /dev/null
+++ b/marked/H/T-REC-H.248.51-200708-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1c2c13f8a388f4c7c35c4229dbad6436783e34c8addbc5db477ad03342f2d3b2
+size 12824
diff --git a/marked/H/T-REC-H.248.51-200708-I_PDF-E/raw.md b/marked/H/T-REC-H.248.51-200708-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..536f9759f50f9aaf9a21cd80c39c716a8b302f47
--- /dev/null
+++ b/marked/H/T-REC-H.248.51-200708-I_PDF-E/raw.md
@@ -0,0 +1,429 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.51**
+
+(08/2007)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+# --- **Gateway control protocol: Termination connection model package**
+
+ITU-T Recommendation H.248.51
+
+## 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        |
+| <b>Communication procedures</b>                                               | <b>H.240–H.259</b> |
+| 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.51**
+
+# **Gateway control protocol: Termination connection model package**
+
+## **Summary**
+
+ITU-T Recommendation H.248.51 contains a H.248 package that enables a media gateway controller to audit a media gateway to determine what termination connection configurations are allowed in a context. The termination connection configuration may be the particular termination types allowed to be connected together, and/or the maximum number of a particular termination type allowed in a context for a multi-terminations scenario, e.g., conference or multicast.
+
+## **Source**
+
+ITU-T Recommendation H.248.51 was approved on 29 August 2007 by ITU-T Study Group 16 (2005-2008) under the ITU-T Recommendation A.8 procedure.
+
+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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 Relationship with H.248.38 property "number of terminations in a context" ..... | 1    |
+| 1.2 Relationship with multiplexed terminations.....                                 | 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 Termination Connection Model 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    |
+
+
+
+###### Gateway control protocol: Termination connection model package
+
+# 1 Scope
+
+This package allows a media gateway controller to audit a media gateway in order to determine what termination connection configurations are allowed in a context. It provides the media gateway controller an automatic means to determine the information contained in Appendix III of [ITU-T H.248.1], clause 6.4 "Connection Model". Based on this information, the media gateway controller should use the allowed termination connection configurations in its indication to the media gateway for connecting terminations in a context, thereby avoiding the potential failure.
+
+The termination connection configuration may be the termination types allowed to be connected together, and/or the maximum number of a particular termination type allowed in a context for a multi-terminations scenario, e.g., conference or multicast.
+
+It provides an enhanced capability of topology auditing to unambiguously describe the allowed termination connection configurations.
+
+In order to provide a mapping between the type of termination and the TerminationID, a meaningful TerminationID scheme should be used. This scheme shall be provisioned on both the MGC and MG. Using a meaningful scheme allows the TerminationID to be wildcarded in order to describe the terminations connection configurations.
+
+Even where this package is not implemented by a media gateway, the descriptions and syntax described in this Recommendation may be used by those defining Profiles when describing the connection model section of the H.248 Profile Template (Appendix III of [ITU-T H.248.1], clause 6.4).
+
+## 1.1 Relationship with H.248.38 property "number of terminations in a context"
+
+H.248.51 is about termination connection configurations, which are allowed in a possible context, whereas H.248.38 *bc/numterm* property is about the number of terminations present in a concrete, established context. Both functionalities are thus disjoint.
+
+## 1.2 Relationship with multiplexed terminations
+
+Multiplexed terminations are defined in clauses 6.2 (Terminations) and 7.1.3 (Multiplex Descriptor) of [ITU-T H.248.1]. This Recommendation does not allow the description of Termination Connection Models (see clause 3.2.1) with multiplexed termination types.
+
+# 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.1950] ITU-T Recommendation Q.1950 (2002), *Bearer independent call bearer control protocol*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+*None.*
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 termination connection model:** Such a model is characterized by:
+
+- a) (maximum) *number* of terminations per context;
+- b) possible termination *types* (Note 1) in such a context;
+- c) possible *topologies* between the terminations in such a context; and
+- d) supported topology *associations* for each possible topology in such a context.
+
+A MG may support one or multiple different termination connection model(s). The *termination type* is typically related to a specific *bearer technology* (Note 2) of the termination.
+
+NOTE 1 – The type of a termination may be visible via the Termination Identifier (Tid). For instance, H.248 Profile specifications often define "prefix" elements (e.g., 'ALN', 'TDM', 'IP', 'RTP', 'Ephemeral', 'AAL2', etc.) as part of the Tid names (for H.248 text encoding). Another example is dedicated codepoints, like the 3-bit 'termination type' codepoint in [ETSI TS 129 232], in ASN.1 coding schemes (for H.248 binary encoding). Such a prefix or codepoint may be used for unambiguous indications of a termination type.
+
+NOTE 2 – H.248 implementations may not support a means to determine the bearer type through the Termination Identifier. In this case, they may use a dedicated H.248 package for bearer technologies: the Bearer Characteristics package (see clause A.3 of [ITU-T Q.1950]) defines a maximum of 255 different bearer types. This property *BCP/BNCChar* is actually synonym to 'termination type'. In this case, the use of the TCM package does not provide information on the connection of bearer types.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                              |
+|------|------------------------------|
+| AAL2 | ATM Adaptation Layer 2       |
+| ALN  | Analog Line                  |
+| IP   | Internet Protocol            |
+| MG   | Media Gateway                |
+| MGC  | Media Gateway Controller     |
+| RTP  | Real-time Transport Protocol |
+| TDM  | Time Division Multiplex      |
+
+# 5 Conventions
+
+*None.*
+
+# 6 Termination Connection Model Package
+
+Package Name: Termination Connection Model  
+PackageID: tcm (0x00c6)  
+Description: This package allows an MGC to audit a MG to determine the supported termination connection models.  
+Version: 1  
+Extends: None
+
+## 6.1 Properties
+
+### 6.1.1 Supported Termination Connections
+
+Property Name: Supported Termination Connections  
+PropertyID: stc (0x0001)  
+Description: This root-only property describes the allowed termination configurations in a MG.  
+Type: Sub-List of type String  
+Possible values: The String is defined by the following H.248.1 Annex B ABNF:
+
+```
+connectionConfig = LBRKT configChoice *(COMMA configChoice) RBRKT
+; at-most-once
+configChoice = topologyDescriptor / conferenceDescriptor / multicastDescriptor
+topologyDescriptor = TopologyToken LBRKT topologyTriple *(COMMA topologyTriple)
+RBRKT
+topologyTriple = terminationA COMMA terminationB COMMA topologyDirection [COMMA
+eventStream]
+topologyDirection = BothwayToken / IsolateToken / OnewayToken /
+OnewayExternalToken / OnewayBothToken
+conferenceDescriptor = ConferenceToken LBRKT conferenceDuple *(COMMA
+conferenceDuple) RBRKT
+conferenceDuple = terminationA COMMA UINT16
+multicastDescriptor = MulticastToken LBRKT multicastTriple *(COMMA
+multicastTriple) RBRKT
+multicastTriple = terminationA COMMA terminationB COMMA UINT16
+terminationA = TerminationID [LSBRKT instanceID RSBRKT]
+terminationB = TerminationID [LSBRKT instanceID RSBRKT]
+instanceID = UINT16
+ConferenceToken = ("Conference" / "CNF")
+MulticastToken = ("Multicast" / "MLT")
+```
+
+NOTE – Any elements not described in this ABNF are defined in Annex B of [ITU-T H.248.1].
+
+Each instance of string in the "Sub-list of" describes a single overall connection configuration, e.g., one connectionConfig.
+
+Default: None  
+Defined in: TerminationState  
+Characteristics: ReadOnly
+
+### 6.1.2 Non-Supported Termination Connections
+
+Property Name: Non-Supported Termination Connections  
+PropertyID: nstc (0x0002)
+
+Description: This root-only property describes the termination configurations that are not allowed in a MG.  
+Type: Sub-List of type String  
+Possible values: As per clause 6.1.1  
+Default: None  
+Defined in: TerminationState  
+Characteristics: ReadOnly
+
+## 6.2 Events
+
+*None.*
+
+## 6.3 Signals
+
+*None.*
+
+## 6.4 Statistics
+
+*None.*
+
+## 6.5 Error Codes
+
+*None.*
+
+## 6.6 Procedures
+
+### 6.6.1 Supported and Non-Supported Connections
+
+Normally the MG should be configured with the information of its supported and/or non-supported termination connection configurations. To determine the supported configuration, a MGC may send an AuditValue command request to a MG that supports this package. The MGC should audit both the "Supported Termination Connections" and the "Non-supported Termination Connections" properties.
+
+If the "Supported Termination Connections" returns an empty result and the "Non-supported Termination Connections" returns values by the MG in the reply, then ONLY the configurations in "Non-supported Termination Connections" are non-supported by the MG, and the MGC may consider any configuration other than those returned against "Non-supported Termination Connections" is supported by the MG.
+
+If the "Supported Termination Connections" returns values and the "Non-supported Termination Connections" returns an empty result by the MG in the reply, then ONLY the configurations in "Supported Termination Connections" are supported by the MG, and the MGC may consider any configuration other than those returned against "Supported Termination Connections" is non-supported by the MG.
+
+If both the "Supported Termination Connections" and "Non-supported Termination Connections" are empty in the reply, then the MGC is free to use any configuration.
+
+NOTE – Practically speaking, this does not mean every conceivable configuration is possible. The MG may still return an error.
+
+If both the "Supported Termination Connections" and "Non-supported Termination Connections" return values in the reply, the same configuration shall not appear in both properties. The MGC should then only use the configurations listed in the "Supported Termination Connections", and avoid using the configurations listed in the "Non-Supported Termination Connections".
+
+The termination types to be used in either the "Supported Termination Connections", or in the "Non-supported Termination Connections", or in both, according to the above rules, should be provisioned between the MG and the MGC.
+
+### 6.6.2 Connection values
+
+Each string associated with the "Supported Termination Connections" and "Non-supported Termination Connections" properties describes a Connection Configuration. This Connection Configuration may take the form of a Topology Description Triple, a Conference Description Duple and/or a Multicast Description Triple.
+
+Each TerminationID in the Topology Description Triple, Conference Description Duple, and Multicast Description Triple may have an InstanceID associated with it. The InstanceID allows a particular instance of TerminationID to be linked when multiple triples/duples are specified within a single Connection Configuration.
+
+The descriptions should be applied to connections according to the order they are received.
+
+A single Connection Configuration describes a termination connection within a single context.
+
+#### 6.6.2.1 Topology Description
+
+The Topology Description string is of a (TerminationA, TerminationB, TopologyDirection) format, in which the TerminationA and TerminationB represent the termination types, and the TopologyDirection represents the direction between the TerminationA and TerminationB, and may be absent for bothway. This is similar to the definition of TopologyDescriptor. However, there is a difference that an optional InstanceID may be associated with a TerminationA or TerminationB. This is used instead of fully specifying an individual TerminationID and allows wildcarding of the TerminationID.
+
+The Topology Description is used to provide the same level of description as the TopologyDescriptor.
+
+For example, the case of 2 terminations in a context is represented by:
+
+$$tcm/sc = [\{tp\{*,*,bothway\}\}]$$
+
+For example, the case of 3 terminations in a context with one termination listening to the other's bothway connection is represented by:
+
+$$tcm/sc = [\{tp\{*[0],*[1],bothway,*[0],*[2],oneway,*[1],*[2],isolate\}\}]$$
+
+#### 6.6.2.2 Conference Description
+
+The Conference Description string is of the form of a (<termination>, <integer of the number of the termination>) duple. This allows the description of the maximum number of a particular termination type allowed in a context for the purposes of conferencing. The Duple allows the configuration of different termination types mixed in a conference to be described. When specifying the maximum number it implies support for all conferencing numbers up to and including the maximum number. The first Duple specifies the maximum number of all termination types of terminations within that conference. Subsequent Duples provide the maximum number of the individual types of terminations within that conference.
+
+An optional InstanceID may be associated with <termination>. This is used instead of fully specifying an individual TerminationID and allows wildcarding of the TerminationID. If the InstanceID is used on the <termination>s then the first termination of <termination>s will receive that InstanceID. The InstanceID of each subsequent termination in the range specified by <integer> shall be incremented by 1. E.g., given: (\*[1],3) the InstanceIDs of <termination> shall be 1, 2, 3 respectively.
+
+For example, the case of a 20 terminations conference in a context is represented by:
+
+$$\text{tcm/sc} = [\{\text{cnf}\{*,20\}\}]$$
+
+For example, the case of a 30 terminations conference with a maximum number of 10 TDM terminations in a context is represented by:
+
+$$\text{tcm/sc} = [\{\text{cnf}\{*,30,\text{TDM}/*,10\}\}]$$
+
+#### 6.6.2.3 Multicast Description
+
+The Multicast Description string is of the form of a (<termination from>, <terminations to>, <integer of number of terminations to>) triple. This allows the description of the maximum number of a particular termination type allowed to be multicast (broadcasted?) to. The Triples allows the configuration of different termination types mixed in a multicast to be described. When specifying the maximum number it implies support for all multicast numbers up to and including the maximum number. The first Triple specifies the maximum number of all termination types of terminations within that multicast. Subsequent Triples provide the maximum number of the individual types of terminations within that multicast.
+
+An optional InstanceID may be associated with <termination from> or <terminations to>. This is used instead of fully specifying an individual TerminationID and allows wildcarding of the TerminationID. If the InstanceID is used on the <terminations to> then the first termination of <terminations to> will receive that InstanceID. The InstanceID of each subsequent termination in the range specified by <integer of number of terminations to> shall be incremented by 1. E.g., given: (\*[1],\*[2],3) the InstanceIDs of <terminations to> shall be 2, 3, 4 respectively.
+
+When using subsequent Triples the <termination from> value shall be the same as the original Triple, including the InstanceID if included.
+
+For example, the case of a 20 terminations multicast in a context is represented by:
+
+$$\text{tcm/sc} = [\{\text{mlt}\{*,*,20\}\}]$$
+
+For example, the case of a 30 terminations multicast with a maximum number of 10 TDM terminations in a context is represented by:
+
+$$\text{tcm/sc} = [\{\text{mlt}\{*,*,30,*,\text{TDM}/*,10\}\}]$$
+
+#### 6.6.2.4 Description interactions
+
+As described above, the Topology, Conference and Multicast descriptions can be combined to define a Connection Configuration for a context. As such, there may be interactions between the different types of descriptions. Typically, the linkage between the types of descriptions is provided by the TerminationID in the descriptions. Where the TerminationID may prove ambiguous, it is recommended that the InstanceID be used to unambiguously define the relationship.
+
+The following examples illustrate Connection Configurations where multiple descriptions are used.
+
+##### *Example 1: Multicast and Topology Description*
+
+For example, the case of a 3 terminations multicast connection, where the sending termination may be bothway connected to another termination, may be represented by Figure 6-1 and the following syntax:
+
+$$\text{tcm/sc} = ["\{\text{mlt}\{*[1],*,3\}\}", "\{\text{tp}\{*[1],*,\text{bothway}\}\}"]$$
+
+![Figure 6-1: Multicast and Topology connection diagram. A central node T1 is connected to four other nodes: T2, T3, T4, and T5. Arrows point from T1 to each of these four nodes. A small label 'H.248.51(07)_F-6-1' is located to the right of the diagram.](af7916c89a458fdab6c3f443217388ae_img.jpg)
+
+Figure 6-1: Multicast and Topology connection diagram. A central node T1 is connected to four other nodes: T2, T3, T4, and T5. Arrows point from T1 to each of these four nodes. A small label 'H.248.51(07)\_F-6-1' is located to the right of the diagram.
+
+**Figure 6-1 – Multicast and Topology connection**
+
+##### *Example 2: Conference and Multicast Description*
+
+For example, the case of a 4 terminations conference connection where a termination may be multicasting to 3 terminations may be represented by Figure 6-2 and the following syntax:
+
+`tcn/sc = [{"cnf{*,4}}", {mlt{*,*,3}}]`
+
+![Figure 6-2: Conference and Multicast connection diagram. A central node T2 is connected to three nodes: T5, T6, and T7. Arrows point from T2 to each of these three nodes. Additionally, T2 is part of a conference connection with three other nodes: T1, T3, and T4. These three nodes are connected to a central square-shaped conference point. A small label 'H.248.51(07)_F-6-2' is located to the right of the diagram.](410562339ce067fdc6fa41940c118658_img.jpg)
+
+Figure 6-2: Conference and Multicast connection diagram. A central node T2 is connected to three nodes: T5, T6, and T7. Arrows point from T2 to each of these three nodes. Additionally, T2 is part of a conference connection with three other nodes: T1, T3, and T4. These three nodes are connected to a central square-shaped conference point. A small label 'H.248.51(07)\_F-6-2' is located to the right of the diagram.
+
+**Figure 6-2 – Conference and Multicast connection**
+
+##### *Example 3: Multicast and Conference Descriptor*
+
+For example, the case of a 3 terminations multicast where one of the terminations being multicast may be conference connected to 3 terminations may be represented by Figure 6-3 and the following syntax:
+
+`tcn/sc = [{mlt{*,*[2],3}}, {cnf{*[4],4}}]`
+
+![Figure 6-3: Multicast and Conference connection diagram. A central node T1 is connected to three nodes: T2, T3, and T4. Arrows point from T1 to each of these three nodes. Additionally, T4 is part of a conference connection with three other nodes: T5, T6, and T7. These three nodes are connected to a central square-shaped conference point. A small label 'H.248.51(07)_F-6-3' is located to the right of the diagram.](2e399449b7f62d40167a65ca88888917_img.jpg)
+
+Figure 6-3: Multicast and Conference connection diagram. A central node T1 is connected to three nodes: T2, T3, and T4. Arrows point from T1 to each of these three nodes. Additionally, T4 is part of a conference connection with three other nodes: T5, T6, and T7. These three nodes are connected to a central square-shaped conference point. A small label 'H.248.51(07)\_F-6-3' is located to the right of the diagram.
+
+**Figure 6-3 – Multicast and Conference connection**
+
+NOTE – When specifying Connection Configurations with both of multicast and conference connection, specifiers should be aware of the potential for InstanceID overlap due to the way InstanceIDs are automatically assigned with these description types.
+
+### 6.6.3 Message examples
+
+Given the connection model and the TerminationID scheme as follows:
+
+- Context[a](RTP, TDM);
+- Context[b](TDM, TDM).
+
+the MGC would audit the Supported Connections property. The response would be:
+
+```
+MEGACO/3 [125.125.125.111]:55555
+Reply = 50007 {
+  Context = - {
+    AuditValue = Root {
+      Media {
+        TerminationState {
+          tcm/sc = [{"tp{tdm/*,tdm/*,bothway}}",
+                    " {tp{rtp/*,tdm/*,bothway}}"]
+        }
+      }
+    }
+  }
+}
+```
+
+The response indicates that any TDM termination can be connected to any other TDM termination. It also indicates that any RTP termination can be connected to any TDM termination, and vice versa. As RTP to RTP is not described, RTP to RTP termination connection is not supported.
+
+
+
+## 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/H/T-REC-H.248.54-200708-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..05525a45aafd00c778e662ea020d2c792ef0359e
--- /dev/null
+++ b/marked/H/T-REC-H.248.54-200708-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:73cde25fba56a02e4ced43d6ae64fcf082cf52fee6ff509e4a10f3ce52fbb6d3
+size 14576
diff --git a/marked/H/T-REC-H.248.54-200708-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.54-200708-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c
--- /dev/null
+++ b/marked/H/T-REC-H.248.54-200708-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.54-200708-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/H/T-REC-H.248.54-200708-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..971835b2688ad3053ab69e904af07b693e4ab3de
--- /dev/null
+++ b/marked/H/T-REC-H.248.54-200708-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:982b3952100b93c0519a9d0a90f74d2748068e289c057956748c164a65ae9fea
+size 41512
diff --git a/marked/H/T-REC-H.248.55-200806-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/H/T-REC-H.248.55-200806-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d68c28ee068a2ce00ad855d0bae82a0636e30867
--- /dev/null
+++ b/marked/H/T-REC-H.248.55-200806-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e190b160500332e85d1d85d158b6036c121f8fc8ca2c50d5676e96a6ddf53c19
+size 104296
diff --git a/marked/H/T-REC-H.248.55-200806-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/H/T-REC-H.248.55-200806-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a52603b38c97f5b60122022e4fdbaff2edb4e1f9
--- /dev/null
+++ b/marked/H/T-REC-H.248.55-200806-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c37076c4cb5bf4935fb1e3f79ec5d55f28631fd3abc3b6a7a475c3d9669cb9c3
+size 35068
diff --git a/marked/H/T-REC-H.248.55-200806-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.248.55-200806-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d7536350b6709a613bfa3f1b8f23e25a4e38526f
--- /dev/null
+++ b/marked/H/T-REC-H.248.55-200806-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b3fa2dfd45cba5ba2a41858cc7e9e70aff13479736fca5063b4a1e79eb495227
+size 6982
diff --git a/marked/H/T-REC-H.248.55-200806-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/H/T-REC-H.248.55-200806-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..067d46e990553a887f43a26d1dbaf57789d36b3b
--- /dev/null
+++ b/marked/H/T-REC-H.248.55-200806-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:354f98e9902d96750feace292201b3c40a03bbc5106bece691990c758f67f61a
+size 61685
diff --git a/marked/H/T-REC-H.248.55-200806-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/H/T-REC-H.248.55-200806-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c92b7ada2649f2ebb79b10247c9e37f45ff895e4
--- /dev/null
+++ b/marked/H/T-REC-H.248.55-200806-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1d062c97c536001660fa127c0310e0e6ee5d75312d7c760a1195cfc4022956fe
+size 106297
diff --git a/marked/H/T-REC-H.248.55-200806-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/H/T-REC-H.248.55-200806-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2277cad8da8d1af5ff883e9cef7e9c50849500cc
--- /dev/null
+++ b/marked/H/T-REC-H.248.55-200806-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e164f9dca79eaf69d834b4f5bdb6d0485c5187d87b491a3f2206845ae3e0f902
+size 91441
diff --git a/marked/H/T-REC-H.248.55-200806-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/H/T-REC-H.248.55-200806-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..266f72ef30a6b6287432bdbef10936fc603c6fbb
--- /dev/null
+++ b/marked/H/T-REC-H.248.55-200806-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8c098d9ce09234a1cc531ef9d68c56149a214bd747abb93a72c5a062be8a1d87
+size 58370
diff --git a/marked/H/T-REC-H.248.55-200806-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/H/T-REC-H.248.55-200806-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e100c9827163e03eabee3be7e66302b7af2936ef
--- /dev/null
+++ b/marked/H/T-REC-H.248.55-200806-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:edc47bfc03e86516d595196f84914912466ef0f317d44b02b41ce16fc99da4bd
+size 136460
diff --git a/marked/H/T-REC-H.248.55-200806-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/H/T-REC-H.248.55-200806-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f1f99cf0c4a05cc29a37765d805671cb15d96c41
--- /dev/null
+++ b/marked/H/T-REC-H.248.55-200806-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7aee788227635e180dfd017e2cdb9598b86b15d634abcbb7b184b644f62fe724
+size 81894
diff --git a/marked/H/T-REC-H.248.55-200806-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/H/T-REC-H.248.55-200806-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8da45ecde7389e3f992352a58ca0cc2468ec45db
--- /dev/null
+++ b/marked/H/T-REC-H.248.55-200806-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:74f0c551fbdb4d42dee1e7c3f2a67f338a34f28c5df26b88942b930f1a1ee005
+size 84939
diff --git a/marked/H/T-REC-H.248.55-200806-I_PDF-E/e354b57563dae469c00b412b2abdf765_img.jpg b/marked/H/T-REC-H.248.55-200806-I_PDF-E/e354b57563dae469c00b412b2abdf765_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cc7783768eb55652c5acb486420b8734d6438614
--- /dev/null
+++ b/marked/H/T-REC-H.248.55-200806-I_PDF-E/e354b57563dae469c00b412b2abdf765_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:959de435a9175afe0fa465b04cc0218ce08c55fd79f73675581013dc8a9e8ef2
+size 47733
diff --git a/marked/H/T-REC-H.248.55-200806-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/H/T-REC-H.248.55-200806-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..506947fdaa267c877511b0b2ff45a8d9b650f8bb
--- /dev/null
+++ b/marked/H/T-REC-H.248.55-200806-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dfb5155389cf2931edbd15e15a9e1234c54d262f19ae2668d4333adb7a838491
+size 116028
diff --git a/marked/H/T-REC-H.248.55-200806-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/H/T-REC-H.248.55-200806-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d1c8c14932f4fc44e354b0165e9efad89becf0d1
--- /dev/null
+++ b/marked/H/T-REC-H.248.55-200806-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c4cffff35203a9300239c38ca218a4b7453d5db97de540c3881d3bfa43e5717e
+size 72589
diff --git a/marked/H/T-REC-H.248.55-200806-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/H/T-REC-H.248.55-200806-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1d310d2b567443c04070fbdd8767496fb7242c1c
--- /dev/null
+++ b/marked/H/T-REC-H.248.55-200806-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:318f0f53e6021c6dadea4c55f7c132564e4a59712e9f719810b020a6b804229f
+size 102760
diff --git a/marked/H/T-REC-H.248.56-200708-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.56-200708-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c
--- /dev/null
+++ b/marked/H/T-REC-H.248.56-200708-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.57-201410-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.248.57-201410-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..22dc7ff0fb30f976cc1e576c45d2b7e65fa5ddc7
--- /dev/null
+++ b/marked/H/T-REC-H.248.57-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.57-201410-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.248.57-201410-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ddca080eb2a3fa97db5e45e53c7567a674ba0c56
--- /dev/null
+++ b/marked/H/T-REC-H.248.57-201410-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f6c053c9f8a872a10ebd843de2432ac737061a31ec884c33cddc31ad4297af98
+size 128041
diff --git a/marked/H/T-REC-H.248.58-200806-I_PDF-E/raw.md b/marked/H/T-REC-H.248.58-200806-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..35413e706b3450cef8bf88b808a51883726e70f3
--- /dev/null
+++ b/marked/H/T-REC-H.248.58-200806-I_PDF-E/raw.md
@@ -0,0 +1,308 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.58**
+
+(06/2008)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+# --- **Gateway control protocol: Packages for application level H.248 statistics**
+
+Recommendation ITU-T H.248.58
+
+## 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        |
+| <b>Communication procedures</b>                                               | <b>H.240–H.259</b> |
+| 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.58**
+
+# **Gateway control protocol: Packages for application level H.248 statistics**
+
+## **Summary**
+
+Recommendation ITU-T H.248.58 defines an H.248 package for application data level statistics for applications, which use real-time transport protocol as an application-level framing protocol. Both statistics are related to traffic volume. Such metrics may be useful for usage metering.
+
+###### **Source**
+
+Recommendation ITU-T H.248.58 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 Introduction to areas with usage of H.248 statistics.....                       | 1    |
+| 1.2 Scope of H.248 statistics defined by this Recommendation .....                  | 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 Overview .....                                                                    | 2    |
+| 6.1 Relation of the <i>rtpad</i> package to <i>nt</i> and <i>rtp</i> packages ..... | 2    |
+| 7 RTP Application Data Package .....                                                | 3    |
+| 7.1 Properties.....                                                                 | 4    |
+| 7.2 Events .....                                                                    | 4    |
+| 7.3 Signals .....                                                                   | 4    |
+| 7.4 Statistics.....                                                                 | 4    |
+| 7.5 Error codes.....                                                                | 4    |
+| 7.6 Procedures .....                                                                | 5    |
+
+
+
+# Recommendation ITU-T H.248.58
+
+# Gateway control protocol: Packages for application level H.248 statistics
+
+# 1 Scope
+
+## 1.1 Introduction to areas with usage of H.248 statistics
+
+H.248 statistics are defined and used for different purposes. They may be categorized into the following main areas:
+
+- 1) **Usage metering:** Relates typically to the traffic volume on the application level; see, e.g., clauses E.11 and E.12 of [ITU-T H.248.1] for basic support.
+- 2) **Reporting of QoS related metrics:** See, e.g., [ITU-T H.248.30].
+- 3) **Recording of successful, unsuccessful or specific policing actions:** See, e.g., [ITU-T H.248.43].
+- 4) **Validation of network capacity allocations:** Relates typically to the traffic volume on the lowest layer of transport capacity reservation, e.g., could be layer 2, 3 or other; dependent on the specific local descriptor and/or remote descriptor information.)
+
+## 1.2 Scope of H.248 statistics defined by this Recommendation
+
+The scope of this Recommendation is related to H.248 statistics defined, in particular, for measurements on an application data level. Served user instances for such statistics may be in the area of usage metering.
+
+# 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.30] Recommendation ITU-T H.248.30 (2007), *Gateway control protocol: RTCP extended performance metrics packages*.
+- [ITU-T H.248.43] Recommendation ITU-T H.248.43 (2008), *Gateway control protocol: Packages for gate management and gate control*.
+- [ITU-T H.248.57] Recommendation ITU-T H.248.57 (2008), *Gateway control protocol: RTP control protocol package*.
+- [IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications*.  
+<<http://www.ietf.org/rfc/rfc3550.txt>>
+
+# **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:
+
+|      |                                      |
+|------|--------------------------------------|
+| IP   | Internet Protocol                    |
+| MG   | Media Gateway                        |
+| MGC  | Media Gateway Controller             |
+| RR   | Receiver Report                      |
+| RTCP | Real-time Transport Control Protocol |
+| RTP  | Real-time Transport Protocol         |
+| SR   | Sender Report                        |
+| SSRC | Synchronization Source               |
+
+# **5 Conventions**
+
+None.
+
+# **6 Overview**
+
+Clause 7 defines an H.248 package for application data level statistics for applications, which use RTP as the application level framing protocol.
+
+## **6.1 Relation of the *rtpad* package to *nt* and *rtp* packages**
+
+The calculation of statistics for the metrics "octets sent" and "octets received" is introduced by clause E.11.5.1.5 of [ITU-T H.248.1]. Figure 1 illustrates the concept of an IP stack (which is the case for RTP) and the various possibilities of layer-dependency for these two metrics.
+
+Figure 2 points out the difference between the semantics of the *rtpad* package (case 'e') versus *nt* and *rtp* package (case 'c').
+
+![Figure 1: Layer-dependent metrics for 'octets sent' and 'octets received' in case of an IP stack. The diagram shows five bars (a-e) representing different measurement points in a protocol stack. The stack layers are: L1 (Physical), L2 (Data Link), L3: IP (Network), L4: UDP, TCP, ... (Transport), RTP, UDPPTL, ... (Application level framing), and E.g. audio codec (Application data). Bars 'a' through 'e' show varying combinations of 'Transport overhead' (orange) and 'Reported traffic volume' (green). Bar 'a' is all green; 'b' has one orange layer at the bottom; 'c' has two orange layers; 'd' has three orange layers; 'e' has four orange layers. The label H.248.58(08)_F01 is at the bottom right.](352c5fab6f936356e9570761a02ab71e_img.jpg)
+
+Figure 1: Layer-dependent metrics for 'octets sent' and 'octets received' in case of an IP stack. The diagram shows five bars (a-e) representing different measurement points in a protocol stack. The stack layers are: L1 (Physical), L2 (Data Link), L3: IP (Network), L4: UDP, TCP, ... (Transport), RTP, UDPPTL, ... (Application level framing), and E.g. audio codec (Application data). Bars 'a' through 'e' show varying combinations of 'Transport overhead' (orange) and 'Reported traffic volume' (green). Bar 'a' is all green; 'b' has one orange layer at the bottom; 'c' has two orange layers; 'd' has three orange layers; 'e' has four orange layers. The label H.248.58(08)\_F01 is at the bottom right.
+
+**Figure 1 – Layer-dependent metrics for "octets sent" and "octets received" in case of an IP stack**
+
+![Figure 2: Semantics of the rtpad package versus nt and rtp package. The diagram shows five bars (a-e) representing different measurement points in a protocol stack for H.248 RTP terminations. The stack layers are: L1 (Physical), L2 (Data Link), L3: IPv4 or IPv6 (Network), L4: UDP or DCCP (Transport), RTP (Application level framing), and E.g. audio codec (Application data). Bars 'a' through 'e' show varying combinations of 'Transport overhead' (orange) and 'Reported traffic volume' (green). Bars 'c' and 'e' are highlighted with dashed boxes labeled 'nt and rtp' and 'rtpad' respectively. The label H.248.58(08)_F02 is at the bottom right.](91be14371a97fb5ce9eeb29ae18d07c3_img.jpg)
+
+Figure 2: Semantics of the rtpad package versus nt and rtp package. The diagram shows five bars (a-e) representing different measurement points in a protocol stack for H.248 RTP terminations. The stack layers are: L1 (Physical), L2 (Data Link), L3: IPv4 or IPv6 (Network), L4: UDP or DCCP (Transport), RTP (Application level framing), and E.g. audio codec (Application data). Bars 'a' through 'e' show varying combinations of 'Transport overhead' (orange) and 'Reported traffic volume' (green). Bars 'c' and 'e' are highlighted with dashed boxes labeled 'nt and rtp' and 'rtpad' respectively. The label H.248.58(08)\_F02 is at the bottom right.
+
+**Figure 2 – Semantics of the *rtpad* package versus *nt* and *rtp* package**
+
+The *rtpad* package provides complementary statistics with regard to the *nt* and *rtp* packages. For instance, the statistics of *rtpad* could be used for *usage metering*, and the statistics of *nt* or *rtp* could be used for the measurement of IP transport capacity usage and, thus, the validation of requested *transport protocol layer bandwidth*.
+
+# 7 RTP Application Data Package
+
+**Package name:** RTP Application Data Package
+
+**Package ID:** rtpad (0x00cb)
+
+**Description:** This package is used to support explicit octet count statistics according to the real-time transport protocol (RTP) [IETF RFC 3550].
+
+**Version:** 1  
+**Extends:** None.
+
+## 7.1 Properties
+
+None.
+
+## 7.2 Events
+
+None.
+
+## 7.3 Signals
+
+None.
+
+## 7.4 Statistics
+
+### 7.4.1 RTP Payload Octets Sent
+
+**Statistic name:** RTP Payload Octets Sent
+
+**Statistic ID:** payloados (0x0001)
+
+**Description:** Provides the number of octets sent from the termination or stream since the statistic has been set. The octets represent the egress RTP payload according to [IETF RFC 3550] (see clause 6.4.1, SR: Sender Report RTCP Packet):
+
+Sender's octet count:
+
+The total number of payload octets (i.e., not including header or padding) transmitted in RTP data packets.
+
+At the termination level, it is equal to the sum of the egress flows over all streams.
+
+**Type:** Double
+
+**Possible values:** any 64-bit integer 0 and up
+
+**Level:** Either
+
+### 7.4.2 RTP Payload Octets Received
+
+**Statistic name:** RTP Payload Octets Received
+
+**Statistic ID:** payloador (0x0002)
+
+**Type:** Double
+
+**Description:** Provides the number of octets received on the termination or stream since the statistic has been set. The octets represent the ingress RTP payload, i.e., the total number of payload octets (i.e., not including header or padding) received in RTP data packets by the receiver. This H.248 statistic is not related to Receiver Report RTCP Packet (RTCP RR).
+
+At the termination level, it is equal to the sum of the ingress flows over all streams.
+
+**Possible values:** any 64-bit integer 0 and up
+
+**Level:** Either
+
+## 7.5 Error codes
+
+None.
+
+## **7.6 Procedures**
+
+### **7.6.1 Relation of RTCP basic report metrics and H.248 statistics**
+
+The RTCP metrics for the octet count are dependent on the arrival events RTCP sender or receiver reports. The arrival of an SR or RR typically leads to the reset of the RTCP metrics. The correspondent H.248 statistics are independent of RTCP packet arrival and departure events.
+
+### **7.6.2 SSRC identifier changes**
+
+The SSRC may change for an active RTP session. Such a change may lead to the reset of the RTCP counters (see [IETF RFC 3550]).
+
+The correspondent H.248 statistics shall be independent of RTP SSRC changes.
+
+### **7.6.3 RTCP traffic**
+
+The traffic volume of a possible RTCP flow (note that the definition of RTCP flow is in clause 3 of [ITU-T H.248.57]) is not measured; only "RTP data packets" will be counted. In the case of a lack of sent and received RTP traffic the values of the statistics will consequently be equal to zero (e.g., also for H.248 streams with an assigned RTCP flow only), independent of the RTCP-related traffic volume.
+
+
+
+
+
+# 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.59-200708-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.59-200708-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c
--- /dev/null
+++ b/marked/H/T-REC-H.248.59-200708-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.59-200708-I_PDF-E/raw.md b/marked/H/T-REC-H.248.59-200708-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..38617161fb2616481f53e2520791e3c4b6c42f05
--- /dev/null
+++ b/marked/H/T-REC-H.248.59-200708-I_PDF-E/raw.md
@@ -0,0 +1,242 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.59**
+
+(08/2007)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+# --- **Gateway control protocol: Event timestamp notification package**
+
+ITU-T Recommendation H.248.59
+
+# 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        |
+| <b>Communication procedures</b>                                               | <b>H.240–H.259</b> |
+| 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.59**
+
+# **Gateway control protocol: Event timestamp notification package**
+
+## **Summary**
+
+ITU-T Recommendation H.248.59 contains a H.248 package that provides means for determining whether or not a media gateway supports the use of timestamps with the event detection time at event notification, and allows the media gateway controller to request that timestamps be or not be reported together with event notifications, if this feature is supported by the media gateway.
+
+###### **Source**
+
+ITU-T Recommendation H.248.59 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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   | Reference .....                            | 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   | Event timestamp notification package ..... | 1 |
+| 6.1 | Properties .....                           | 2 |
+| 6.2 | Events .....                               | 2 |
+| 6.3 | Signals .....                              | 2 |
+| 6.4 | Statistics .....                           | 2 |
+| 6.5 | Error Codes .....                          | 2 |
+| 6.6 | Procedures .....                           | 2 |
+
+
+
+# Gateway control protocol: Event timestamp notification package
+
+# 1 Scope
+
+This package is to provide a means of determining whether or not a media gateway supports the use of timestamps with the event detection time at event notification. If timestamps are supported, it allows the media gateway controller to request that timestamps be or not be reported with an event notification. This package is useful for control associations where profiles are not used to specify whether or not a media gateway supports the notification of event timestamp.
+
+# 2 Reference
+
+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
+
+## 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:
+
+MG Media Gateway
+
+MGC Media Gateway Controller
+
+# 5 Conventions
+
+*None.*
+
+# 6 Event timestamp notification package
+
+Package name: Event timestamp notification
+
+PackageID: etn (0x00cc)
+
+Description: This package contains a property which allows the MGC to determine or set whether or not a MG uses timestamps containing the detection time of an event in the notification of the detection of an event.
+
+Version: 1
+
+Extends: None
+
+## 6.1 Properties
+
+### 6.1.1 Request timestamp
+
+Property name: Request timestamp
+
+PropertyID: rt (0x0001)
+
+Description: This root-only property indicates whether or not the timestamp associated with event detection is included in a notify message.
+
+Type: Enumeration
+
+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*"
+
+Defined in:       TerminationState
+
+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 Event timestamp capability determination
+
+To determine whether a MG supports the sending of event detection timestamps in notify command requests, the MGC shall send an AuditCapabilities command request with an individual audit of the *etn/rt* property. If the MG does not support timestamps, it shall return "*suppressed*" as the only value. If the MG always sends timestamps, it shall return "*requested*" as the only value. If it is the MG that determines whether or not a timestamp is sent, then it shall return "*autonomous*" as the only value. If the MG supports either option (e.g., it is settable by the MGC), then it shall return all supported options as values. If the MG cannot support any option, then it shall return empty.
+
+### 6.6.2 Event timestamp notification setting
+
+If a MGC requires that event detection timestamps are included for all notify command requests, then it shall set the *etn/rt* property to "*requested*" via a modify command request.
+
+If a MGC requires that event detection timestamps are excluded for all NOTIFY.reqs, then it shall set the *etn/rt* property to "*suppressed*" via a modify command request.
+
+If a MGC does not care if event detection timestamps are included or excluded, then it shall set the *etn/rt* property to "*autonomous*" via a modify command request.
+
+If a MG cannot provide a timestamp for the event requested through an add, move or modify command request, it shall respond with error code 543 "MGC requested event detection timestamp not supported".
+
+
+
+
+
+# **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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.6-200011-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.248.6-200011-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2c51dc90cb14fcd4ad829473bcdc94837c38a376
--- /dev/null
+++ b/marked/H/T-REC-H.248.6-200011-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0694a5c0e74781c870cf178a1db34d73a40e7d59e98672b7dc54789998a7c6b4
+size 8299
diff --git a/marked/H/T-REC-H.248.6-200011-I_PDF-E/raw.md b/marked/H/T-REC-H.248.6-200011-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..8b5f1befad1609f50d14178256f3f407f33e8fe5
--- /dev/null
+++ b/marked/H/T-REC-H.248.6-200011-I_PDF-E/raw.md
@@ -0,0 +1,273 @@
+
+
+![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.6**
+
+(11/2000)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+---
+
+**Gateway control protocol: Dynamic Tone  
+Definition package**
+
+ITU-T Recommendation H.248.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        |
+| <b>Communication procedures</b>                                               | <b>H.240–H.259</b> |
+| 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.*
+
+## **Gateway control protocol: Dynamic Tone Definition package**
+
+## **Summary**
+
+This Recommendation defines a dynamic tone definition package for use with the H.248.1 Gateway Control Protocol. The dynamic tone definition package allows flexible tone specification in a media gateway for feedback to audio receivers. A tone can be defined by assigning properties (for example, frequency or duration) to an existing tone (i.e., a tone defined in some other package) or a new tone. As defined in ITU-T Rec. H.248.1, a "package" is an extension to H.248.1 that supports specific behavior.
+
+NOTE – This Recommendation has been renumbered. It was formerly known as ITU-T H.248 Annex J.
+
+###### **Source**
+
+Recommendation H.248.6 was prepared by ITU-T Study Group 16 (2001-2004) and approved under the WTSA Resolution 1 procedure on 17 November 2000.
+
+## 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 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     | Dynamic Tone Definition package..... | 1 |
+| 3.1   | Properties.....                      | 1 |
+| 3.2   | Events .....                         | 2 |
+| 3.3   | Signals .....                        | 2 |
+| 3.4   | Statistics.....                      | 2 |
+| 3.5   | Procedures .....                     | 2 |
+| 3.5.1 | Updating Tone Definition.....        | 2 |
+| 3.5.2 | Reading existing tones.....          | 2 |
+| 3.5.3 | Tone String (tst) description.....   | 2 |
+
+###### **Gateway control protocol: Dynamic Tone Definition package**
+
+# **1 Scope**
+
+This Recommendation defines a package that extends the applicability of the H.248.1 Gateway Control Protocol Recommendation. Specifically, ITU-T Rec. H.248.6 defines a dynamic tone definition package for use with the H.248.1 Gateway Control Protocol. The dynamic tone definition package allows flexible tone specification in a media gateway for feedback to audio receivers. A tone can be defined by assigning properties (for example, frequency or duration) to an existing tone (i.e. a tone defined in some other package) or a new tone.
+
+# **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 revisions; 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 (2000), *Gateway Control Protocol*.
+
+# **3 Dynamic Tone Definition package**
+
+PackageID: dtd, 0x001c
+
+Version: 1
+
+Extends: None
+
+This package defines a mechanism to redefine existing tones and create new tones for playback. The existing tones are the ones described in supported packages that extend the tonegen generic package.
+
+## **3.1 Properties**
+
+Tone ID
+
+PropertyID: tid (0x0001)
+
+Description:
+
+Indicates the new or existing tone to be modified or who's tone string is to be read.
+
+Type: expanding enumeration
+
+Possible Values:
+
+Existing package\_id, tone id described in supported packages that extend tonegen or new tones to be added.
+
+Defined in: TerminationState.
+
+If the termination is in a context, the changes to the tones apply only to the termination in the context. When the termination leaves the context, the changes are lost. If the termination is in the null context, the changes apply to the termination from then on. If the termination is root, the changes apply to the whole gateway.
+
+Characteristics: both read and write.
+
+### Tone String
+
+PropertyID: tst (0x0002)  
+Description: Tone description string. See procedures ,  
+Type: String  
+Possible Values: See procedures.  
+Defined in: TerminationState.  
+Characteristics: both read and write:
+
+## 3.2 Events
+
+None
+
+## 3.3 Signals
+
+None
+
+## 3.4 Statistics
+
+None
+
+## 3.5 Procedures
+
+### 3.5.1 Updating Tone Definition
+
+To modify or create a new tone:
+
+- 1) Set tid to an existing or new package\_id,tone id value.
+- 2) Set tst to the new tone description.
+
+If tst is null, the id is decommissioned and removed. Only newly defined tonids can be removed.
+
+### 3.5.2 Reading existing tones
+
+To read the list of tones defined:
+
+- 1) Read tid.
+
+To read an already defined tone string:
+
+- 1) Set tid.
+- 2) Read tst.
+
+Some package-defined tones may not have a tone string in the gateway. In that case the tst read will have the value "Not Available".
+
+### 3.5.3 Tone String (tst) description
+
+The syntax for the tone definition string is recursive and uses parenthesis as a delimiter of elements. DefToneString below is the tone string(tst):
+
+DefToneString = "(" DefToneElement [ "\*" RepeatCount ] ")" [ "," "+" / "X" DefToneString ]
+
+NOTE 1 – A separator of ',' indicates that the next definition follows sequentially in time; a separator of '+' indicates that the following tone is to be mixed with the previous tone and is simultaneous with it; a separator of 'X' indicates that the first tone is modulated by the second tone.
+
+NOTE 2 – All implementations must support sequential definitions (',' separator). Mixing ('+') and modulation ('X') support are optional; however, the implementation must make a best effort and return no error in these cases.
+
+NOTE 3 – Recursion is limited to a maximum of 32 levels. All implementations must support at least 2 levels of recursion.
+
+RepeatCount = %d1-32767 / %d0
+
+NOTE 4 – repeatcount of 0 indicates infinite repeating.
+
+DefToneElement = ToneName ["," ToneDuration ["," ToneAmplitude ]]
+
+ToneName = (Package id, Tone id) / "#"FreqValue / "&"AnnouncementParameterList
+
+Package id = 1\*VCHAR; Unique package identity string or value
+
+Tone id = 1\*VCHAR; Unique tone identity string or value
+
+FreqValue = %d0-4000; in Hertz
+
+AnnouncementParameterList = AnnouncementID ["," SubstitutionString]
+
+AnnouncementID = 1\*VCHAR; Unique identifier for an audio announcement
+
+SubstitutionString = """"1\*VCHAR""""; a string to be inserted into an announcement.
+
+ToneDuration = %d1-32767 / %d0; in milliseconds
+
+NOTE 5 – ToneDuration of 0 indicates infinite duration or duration defined by the Tone id.
+
+ToneAmplitude = "-""%d32-1 / %d0; in dBm0
+
+An example of tone definition follows.
+
+RingingTone = ((0x0005,0x0031),((#480)+(#620)),250,-24)\*0
+
+## 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                                                                   |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                      |
+| 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.60-200903-I_PDF-E/raw.md b/marked/H/T-REC-H.248.60-200903-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..38f5e3d6c89c0b63c9837a2d26e3ca91448d43e2
--- /dev/null
+++ b/marked/H/T-REC-H.248.60-200903-I_PDF-E/raw.md
@@ -0,0 +1,301 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.60**
+
+(03/2009)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+# --- **Gateway control protocol: Identification of content of communication**
+
+Recommendation ITU-T H.248.60
+
+## 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        |
+| <b>Communication procedures</b>                                               | <b>H.240–H.259</b> |
+| 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.60**
+
+# **Gateway control protocol: Identification of content of communication**
+
+## **Summary**
+
+Recommendation ITU-T H.248.60 defines an H.248 package to tag traffic of an individual H.248 stream/termination.
+
+###### **Source**
+
+Recommendation ITU-T H.248.60 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                                                  | 1    |
+| 6 Content of communication identity package for IP-based transport of content of communication ..... | 2    |
+| 6.1 Properties.....                                                                                  | 2    |
+| 6.2 Events .....                                                                                     | 2    |
+| 6.3 Signals .....                                                                                    | 2    |
+| 6.4 Statistics.....                                                                                  | 2    |
+| 6.5 Error codes.....                                                                                 | 2    |
+| 6.6 Procedures .....                                                                                 | 2    |
+| Appendix I – Example protocol stacks at content delivery interface .....                             | 4    |
+| I.1 Default transport: IP-over-IP .....                                                              | 4    |
+| I.2 Other encapsulation schemes .....                                                                | 4    |
+| Bibliography.....                                                                                    | 5    |
+
+
+
+## Recommendation ITU-T H.248.60
+
+# Gateway control protocol: Identification of content of communication
+
+# 1 Scope
+
+This Recommendation allows a media gateway controller (MGC) to request a media gateway (MG) to label/tag the content of communication using an H.248 interface. The tag for a particular media flow is termed as content of communication identifier (CCID) as H.248 signalling element. The inclusion of the CCID information in those packets is part of a dedicated encapsulation header.
+
+# 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 plus Amendment 1 (2008)*.
+
+# 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:
+
+|      |                                            |
+|------|--------------------------------------------|
+| CA   | (H.248) Control Association                |
+| CC   | Content of Communication                   |
+| CCCI | Content of Communication Control Interface |
+| CCID | Content of Communication Identifier        |
+| LCD  | LocalControl Descriptor                    |
+| MG   | Media Gateway                              |
+| MGC  | Media Gateway Controller                   |
+| SDU  | Service Data Unit                          |
+| UDP  | User Datagram Protocol                     |
+
+# 5 Conventions
+
+None.
+
+# 6 Content of communication identity package for IP-based transport of content of communication
+
+**Package Name:** Content of Communication Identity Package
+
+**Package ID:** cci (0x00d1)
+
+**Description:** This package enables the MGC to assign a correlation identifier for content of communication to a H.248 Termination/Stream.
+
+**Version:** 1
+
+**Extends:** None.
+
+## 6.1 Properties
+
+### 6.1.1 Content of communication identifier
+
+**Property Name:** Content of Communication Identifier
+
+**Property ID:** ccid (0x0001)
+
+**Description:** This property corresponds to the correlation identifier for content of communication.
+
+**Type:** Double
+
+**Possible values:** Any value
+
+NOTE – Profiles may further limit the value range and/or assign "special values".
+
+**Default:** None.
+
+**Defined in:** LocalControl
+
+**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 traffic tagging is required for a media stream (of a bearer connection), the MGC sets the content of communication ID in the LocalControl descriptor (LCD) which is then passed to the MG via a H.248 command. For each bearer packet received, the MG tags the packet with the correlation identifier for content of communication as the key. Appendix I provides some examples of possible forwarding methods.
+
+### 6.6.2 Example use case(s)
+
+This package may be applied to any kind of service that copies IP-based bearer traffic. Traffic copying may be, for instance, used for (but not limited to):
+
+- a) online tests, with the limitation on a unidirectional traffic flow delivered towards a test equipment acting as traffic sink;
+- b) online monitoring of traffic for QoS purposes (e.g., in case of particular performance metrics which may not be provided by the MG itself);
+- c) simple and limited tracing capabilities of bearer traffic;
+
+NOTE – Any advanced tracing service (e.g., as defined by [b-ETSI TS 132 421], [b-ETSI TS 132 422], [b-ETSI TS 132 423]) may benefit from the use of the 3GPP-defined H.248 *trace* package according to [b-ETSI TS 129 232].
+
+- d) access to intercepted bearer traffic.
+
+# Appendix I
+
+## Example protocol stacks at content delivery interface
+
+(This appendix does not form an integral part of this Recommendation)
+
+This appendix provides examples for possible encapsulation methods.
+
+## I.1 Default transport: IP-over-IP
+
+The original IP packet, either an IP version 4 or version 6 packet, shall be encapsulated in another IP packet. This is conceptually an IP-over-IP tunnelling method (like already known from correspondent technologies like: "IP in IP encapsulation" [b-IETF RFC 2003], GRE (generic routing encapsulation) see [b-IETF RFC 2784] or the GPRS terrestrial IP transport domain (with so-called GTP tunnels)).
+
+The IP tunnel itself may again use either IP version 4 or version 6. UDP should be the default transport protocol for the tunnel. The 4-byte word from the signalled *ccid* value shall be added in front of the original IP packet, which serves as a layer 4 service data unit (SDU) for the layer 4 tunnel protocol (e.g., the UDP payload in case of UDP). The mapping of *ccid* values to the 4-byte encapsulation header may be defined by a profile specification.
+
+The described IP-over-IP transport mechanism represents an "*IP layering with additional encapsulation header*" tunnelling method.
+
+There would be a unique protocol layering per network domain, i.e., a unique content delivery interface type per H.248 media gateway, and thus, per H.248 control association (CA). The applied protocol layering may be therefore defined by a profile specification using this package (or using provisioning).
+
+## I.2 Other encapsulation schemes
+
+There may be other different possible protocol encapsulation schemes, like for instance:
+
+- An application layer approach by using the *ccid* property value for the generation and insertion of digital signatures (on application layer) for the traffic at the content delivery interface; or even
+- A non-IP-based packet-switched bearer technology for content delivery.
+
+This Recommendation does not limit other encapsulation alternatives; however, a mutual agreement between MGC and MG would be then required (which would be an H.248 profile specification using the *cci* package).
+
+# Bibliography
+
+- [b-ETSI TS 129 232] ETSI TS 129 232 (2007), *Universal Mobile Telecommunications System (UMTS); Media Gateway Controller (MGC) – Media Gateway (MGW) interface; Stage 3 (3GPP TS 29.232 version 7.7.0 Release 7)*.
+- [b-ETSI TS 132 421] ETSI TS 132 421 (2007), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements (3GPP TS 32.421 version 7.2.0 Release 7)*.
+- [b-ETSI TS 132 422] ETSI TS 132 422 (2007), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Telecommunication management; Subscriber and equipment trace; Trace control and configuration management (3GPP TS 32.422 version 7.2.0 Release 7)*.
+- [b-ETSI TS 132 423] ETSI TS 132 423 (2007), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Telecommunication management; Subscriber and equipment trace; Trace data definition and management (3GPP TS 32.423 version 7.4.0 Release 7)*.
+- [b-IETF RFC 2003] IETF RFC 2003 (1996), *IP Encapsulation within IP*.
+- [b-IETF RFC 2784] IETF RFC 2784 (2000), *Generic Routing Encapsulation (GRE)*.
+
+
+
+
+
+## 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.63-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a
--- /dev/null
+++ b/marked/H/T-REC-H.248.63-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.67-200912-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.67-200912-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..04ed0575fb17e6faeb57d9d81b58c3b85f7e21df
--- /dev/null
+++ b/marked/H/T-REC-H.248.67-200912-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.67-200912-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg b/marked/H/T-REC-H.248.67-200912-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..db70bd46f924078d00012fce9e03ec5d63c9c24d
--- /dev/null
+++ b/marked/H/T-REC-H.248.67-200912-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6fb167422ed3fafa8e7f649a08ad1cfb18e5a82613c95ccc3b31b3180349a071
+size 80487
diff --git a/marked/H/T-REC-H.248.67-200912-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/H/T-REC-H.248.67-200912-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ea300f22feb2085a291375418343824b71fcb033
--- /dev/null
+++ b/marked/H/T-REC-H.248.67-200912-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae77710c11fe8eea48ab162e71b71f396a2f8411f25ff1033af0c80882cbedff
+size 74775
diff --git a/marked/H/T-REC-H.248.67-200912-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/marked/H/T-REC-H.248.67-200912-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6de26498b20e8d062fdfe8937f27c537e5885ce8
--- /dev/null
+++ b/marked/H/T-REC-H.248.67-200912-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8d090f45fa85714fa4c716a9d347d1687ce685952ab2c0fd149b4ff2158b0f69
+size 17926
diff --git a/marked/H/T-REC-H.248.67-200912-I_PDF-E/raw.md b/marked/H/T-REC-H.248.67-200912-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..cc47bfe1eb460f78aa997547dd121e56a25b122a
--- /dev/null
+++ b/marked/H/T-REC-H.248.67-200912-I_PDF-E/raw.md
@@ -0,0 +1,648 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.67**
+
+(12/2009)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+---
+
+**Gateway control protocol: Transport mode  
+indication package**
+
+Recommendation ITU-T H.248.67
+
+# 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        |
+| <b>Communication procedures</b>                                               | <b>H.240–H.259</b> |
+| 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.67**
+
+# **Gateway control protocol: Transport mode indication package**
+
+## **Summary**
+
+Gateway control signalling traffic is carried over a transport connection between the media gateway controller (MGC) and media gateway (MG). Recommendation ITU-T H.248 supports multiple, different transport technologies. Each possible protocol stack variant is called ITU-T H.248 transport mode.
+
+Recommendation ITU-T H.248.67 contains an ITU-T H.248 package to determine the supported transport modes by a MG and the indication of a preferred mode. The package enables an MGC to audit and change the transport mode. Transport mode changes may be driven by network evolution, i.e., transitioning from IP version 4 to IP version 6 environments. The added value of this package is given by the capability to support online transport mode changes.
+
+## **History**
+
+| Edition | Recommendation | Approval | Study Group |
+|---------|----------------|----------|-------------|
+|---------|----------------|----------|-------------|
+
+|     |                |            |    |
+|-----|----------------|------------|----|
+| 1.0 | ITU-T H.248.67 | 2009-12-14 | 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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    |
+| 1.1 Examples for typical transport mode changes .....              | 1    |
+| 1.2 Applicability .....                                            | 2    |
+| 2 References.....                                                  | 4    |
+| 3 Definitions .....                                                | 5    |
+| 3.1 Terms defined elsewhere .....                                  | 5    |
+| 3.2 Terms defined in this Recommendation.....                      | 5    |
+| 4 Abbreviations and acronyms .....                                 | 5    |
+| 5 Conventions .....                                                | 6    |
+| 6 Gateway control protocol transport mode indication package ..... | 6    |
+| 6.1 Properties .....                                               | 6    |
+| 6.2 Events .....                                                   | 7    |
+| 6.3 Signals .....                                                  | 8    |
+| 6.4 Statistics.....                                                | 8    |
+| 6.5 Error codes.....                                               | 8    |
+| 6.6 Procedures .....                                               | 8    |
+| Bibliography.....                                                  | 12   |
+
+
+
+# Gateway control protocol: Transport mode indication package
+
+# 1 Scope
+
+ITU-T H.248 is a "transport technology independent" or "bearer-independent" signalling protocol. This means it may be carried over multiple, different transport technologies. There is no tight coupling to a single, specific underlying protocol stack. Such a protocol design satisfies multiple protocol engineering requirements like: a) the signalling protocol is independent of network infrastructure, b) the signalling protocol may be used in present network infrastructures that are very heterogeneous concerning deployed bearer technologies, and c) the signalling protocol can be used in network infrastructures that evolve over time.
+
+The choice of a particular transport technology, either due to an initial negotiation process or due to a later change procedure, may benefit from correspondent signalling elements.
+
+This Recommendation provides functionality for the indication and negotiation of an ITU-T H.248 *transport mode* (see clause 3.1.1).
+
+## 1.1 Examples for typical transport mode changes
+
+The transport mode is tightly coupled to the concept of the ITU-T H.248 control association (CA). A static, never changing transport mode may be considered as *a priori* knowledge, i.e., a provisioning subject. There would be then configuration management actions, on the MG and MGC sides, before any registration attempt would be issued by the MG.
+
+This might be sufficient for some use cases, but the lack of flexibility has shortcomings in regard to evolving networks, multi-transport mode capable ITU-T H.248 entities and/or high service availability requirements.
+
+The transport mode may be characterized by two protocol stack segments (see also definition in clause 3.1.1): "network and lower layers" and "transport and higher layers", represented in the x- and y-axis in Figure 1.
+
+Figure 1 shows some typical transport mode changes:
+
+- 1) ATM network replacement by IP infrastructure: e.g., from "*MTP-3b/AAL5/ATM*" to "*SCTP/IPv4*".
+- 2) Introduction of IP version 6 in an IPv4 infrastructure: e.g., from "*UDP/IPv4*" to "*UDP/IPv6*".
+- 3) Replacement of an inappropriate transport technology by an optimized protocol for signalling transport: e.g., from "*TCP/IPv4*" to "*SCTP/IPv4*".
+- 4) Combination of 2) and 3) in one step: e.g., from "*UDP/IPv4*" to "*SCTP/IPv6*".
+
+![Diagram illustrating transport mode changes for ITU-T H.248 control associations. It shows a grid of transport and network layers with arrows indicating transitions between different modes. A legend on the right provides four examples of these transitions.](3121ebddccf183ca63bb9781be440a7e_img.jpg)
+
+The diagram illustrates the transport and network layers for ITU-T H.248 control associations. The vertical axis represents the "Transport layer", framing, which includes MTP3b/N-SAAL, SSCOP, ALF, TCP, UDP, Native SCTP, and M3UA/SCTP. The horizontal axis represents the "Network layer", which includes AAL5/ATM, IPv4, and IPv6. Red arrows with numbered circles (1-4) indicate transport mode changes. Grey boxes represent transport modes for ITU-T H.248 protocol data units ("signalling transport").
+
+**Examples:**
+
+| No. | From            | To        |
+|-----|-----------------|-----------|
+| 1)  | MTP-3b/AAL5/ATM | SCTP/IPv4 |
+| 2)  | UDP/IPv4        | UDP/IPv6  |
+| 3)  | TCP/IPv4        | SCTP/IPv4 |
+| 4)  | UDP/IPv4        | SCTP/IPv6 |
+
+H.248.67(09)\_F01
+
+Legend:  
+ Transport mode for ITU-T H.248 protocol data units ("signalling transport")  
+→ Transport mode changes examples
+
+Diagram illustrating transport mode changes for ITU-T H.248 control associations. It shows a grid of transport and network layers with arrows indicating transitions between different modes. A legend on the right provides four examples of these transitions.
+
+**Figure 1 – Example typical transport mode changes for ITU-T H.248 control associations**
+
+## 1.2 Applicability
+
+### 1.2.1 Online versus offline transport mode changes
+
+It may be noted that any transport mode change does not necessarily require the application of the (*ServiceChange* based) procedures defined by this Recommendation. Transport mode changes could be completely "controlled" by management plane activities, i.e., via configuration management. Such a procedure implies the transition of all involved ITU-T H.248 entities (MGC and associated MG(s)) in a particular management state in order to execute the configuration changes. Such a management state correlates with an "Out-of-Service" phase, the ITU-T H.248 entities are therefore entirely "offline". The ITU-T H.248 control association does not exist anymore during the "provisioned" transport mode change.
+
+In order to minimize such network "Out-of-Service" periods, it may be beneficial for *ServiceChange* based (termed "online" here) transport mode change support. The coordination and synchronization of transport mode changes via such ITU-T H.248 "call-independent" procedures might be a further advantage of the application of the *trm* package.
+
+### 1.2.2 Supported attributes of transport mode
+
+Figure 2 summarizes the IPv4 based transport modes. The usage of an encryption protocol for ITU-T H.248 traffic may be considered as third dimension of the transport mode. Figure 3 illustrates possible transport modes with encryption on network (L3) or transport (L4) protocol layer (see also [IETF RFC 3788]).
+
+| 1.1) IPv4 (unsecured) |       |       |           |
+|-----------------------|-------|-------|-----------|
+| H.248                 | H.248 | H.248 | H.248     |
+| UDP                   | TCP   | SCTP  | M3UA/SCTP |
+| IPv4                  | IPv4  | IPv4  | IPv4      |
+| L2                    | L2    | L2    | L2        |
+| L1                    | L1    | L1    | L1        |
+
+**Figure 2 – Overview of major transport modes with IP version 4 and without encryption protocol**
+
+| 1.2) IPv4 (L3 secured) |       |       |           |
+|------------------------|-------|-------|-----------|
+| H.248                  | H.248 | H.248 | H.248     |
+| UDP                    | TCP   | SCTP  | M3UA/SCTP |
+| IPv4                   | IPv4  | IPv4  | IPv4      |
+| IPsec                  | IPsec | IPsec | IPsec     |
+| L2                     | L2    | L2    | L2        |
+| L1                     | L1    | L1    | L1        |
+
+  
+
+| 1.3) IPv4 (L4 secured) |       |       |             |
+|------------------------|-------|-------|-------------|
+| H.248                  | H.248 | H.248 | H.248       |
+| DTLS                   | TLS   | TLS   | M3UA<br>TLS |
+| UDP                    | TCP   | SCTP  | SCTP        |
+| IPv4                   | IPv4  | IPv4  | IPv4        |
+| L2                     | L2    | L2    | L2          |
+| L1                     | L1    | L1    | L1          |
+
+**Figure 3 – Overview of major transport modes with IP version 4 and security support on network or transport layer**
+
+Figure 4 provides an overview of major transport modes with IP version 6 as network layer protocol. Figure 5 provides an overview of major transport modes for ATM networks.
+
+![](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg)
+
+**2.1) IPv6 (unsecured)**
+
+|       |       |       |           |
+|-------|-------|-------|-----------|
+| H.248 | H.248 | H.248 | H.248     |
+| UDP   | TCP   | SCTP  | M3UA/SCTP |
+| IPv6  | IPv6  | IPv6  | IPv6      |
+| L2    | L2    | L2    | L2        |
+| L1    | L1    | L1    | L1        |
+
+**2.2) IPv6 (L3 secured)**
+
+|       |       |       |           |
+|-------|-------|-------|-----------|
+| H.248 | H.248 | H.248 | H.248     |
+| UDP   | TCP   | SCTP  | M3UA/SCTP |
+| IPv6  | IPv6  | IPv6  | IPv6      |
+| IPsec | IPsec | IPsec | IPsec     |
+| L2    | L2    | L2    | L2        |
+| L1    | L1    | L1    | L1        |
+
+**2.3) IPv6 (L4 secured)**
+
+|       |       |       |             |
+|-------|-------|-------|-------------|
+| H.248 | H.248 | H.248 | H.248       |
+| DTLS  | TLS   | TLS   | M3UA<br>TLS |
+| UDP   | TCP   | SCTP  | SCTP        |
+| IPv6  | IPv6  | IPv6  | IPv6        |
+| L2    | L2    | L2    | L2          |
+| L1    | L1    | L1    | L1          |
+
+**Figure 4 – Overview of major transport modes with IP version 6 (unsecured and secured transport)**
+
+![](cfda9df1319e04207eb28bcefd1dab7b_img.jpg)
+
+**3.1) AAL5/ATM (unsecured)**
+
+|              |          |          |
+|--------------|----------|----------|
+| H.248        | H.248    | H.248    |
+| MTP3b/N-SAAL | SSCOP    | ALF      |
+| AAL5/ATM     | AAL5/ATM | AAL5/ATM |
+| L1           | L1       | L1       |
+
+**Figure 5 – Overview of major transport modes for ATM 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.248.1] Recommendation ITU-T H.248.1 (2005), *Gateway Control Protocol: Version 3, plus Amendment 2 (2009), New Appendix IV, plus corrections and clarifications.*
+- [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.*
+
+- [ETSI TS 129 202] ETSI TS 129 202 (2009), *Universal Mobile Telecommunications System (UMTS); Signalling System No. 7 (SS7) signalling transport in core network; Stage 3 (3GPP TS 29.202 version 8.1.1 Release 8)*.
+- [IETF RFC 3788] IETF RFC 3788 (2004), *Security Considerations for Signaling Transport (SIGTRAN) Protocols*.
+- [IETF RFC 4301] IETF RFC 4301 (2005), *Security Architecture for the Internet Protocol*.
+- [IETF RFC 4347] IETF RFC 4347 (2006), *Datagram Transport Layer Security*.
+- [IETF RFC 5246] IETF RFC 5246 (2008), *The Transport Layer Security (TLS) Protocol Version 1.2*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+None.
+
+## 3.2 Terms defined in this Recommendation
+
+**3.2.1 transport mode:** The actual *protocol stack* below the ITU-T H.248 protocol layer. This protocol stack may be divided into two main portions: a) transport protocol (L4) and higher layers, and b) network protocol (L3) and lower layers. Any transport mode may also provide encryption on network (L3) or transport (L4) protocol layer.
+
+NOTE – See also clauses 5.3.1, 10 and 11 of [b-ITU-T H.Sup7] concerning IP-based transport connections.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations:
+
+|        |                                                                                      |
+|--------|--------------------------------------------------------------------------------------|
+| AAL5   | ATM Adaptation Layer type 5                                                          |
+| ALF    | Application Level Framing                                                            |
+| ATM    | Asynchronous Transfer Mode                                                           |
+| CA     | (H.248) Control Association                                                          |
+| DTLS   | Datagram Transport Layer Security                                                    |
+| IP     | Internet Protocol                                                                    |
+| IPsec  | IP security                                                                          |
+| IPv4   | IP version 4                                                                         |
+| IPv6   | IP version 6                                                                         |
+| L1     | (Protocol) Layer 1                                                                   |
+| L2     | (Protocol) Layer 2                                                                   |
+| M3UA   | Signalling System No. 7 (SS7) Message Transfer Part 3 (MTP3) – User Adaptation Layer |
+| MG     | Media Gateway                                                                        |
+| MGC    | Media Gateway Controller                                                             |
+| mID    | (H.248) Message Identifier                                                           |
+| MTP-3b | Message Transfer Part level 3 using ITU-T Q.2140                                     |
+
+|        |                                               |
+|--------|-----------------------------------------------|
+| NNI    | Network-to-Network Interface                  |
+| N-SAAL | NNI Signalling ATM Adaptation Layer           |
+| SCTP   | Stream Control Transmission Protocol          |
+| SSCOP  | Service Specific Connection-Oriented Protocol |
+| UDP    | User Datagram Protocol                        |
+| TCP    | Transmission Control Protocol                 |
+| TLS    | Transport Layer Security                      |
+
+# 5 Conventions
+
+None.
+
+# 6 Gateway control protocol transport mode indication package
+
+|               |                                                                                                                                                                                                                                                                                                                                                               |
+|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Package name: | Gateway Control Protocol Transport Mode Indication Package                                                                                                                                                                                                                                                                                                    |
+| Package ID:   | trm (0x00d3)                                                                                                                                                                                                                                                                                                                                                  |
+| Description:  | This package allows the indication of supported transport modes for an ITU-T H.248 control association and the indication of a preferred mode. This package may be for example useful for multi-mode capable ITU-T H.248 entities, for a transport mode change of an existing control association, or for changeover procedures between ITU-T H.248 entities. |
+| Version:      | 1                                                                                                                                                                                                                                                                                                                                                             |
+| Extends:      | None.                                                                                                                                                                                                                                                                                                                                                         |
+
+## 6.1 Properties
+
+### 6.1.1 Supported ITU-T H.248 transport modes
+
+|                  |                                                                                                                                                                                                                                                                                                                                                                    |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Property name:   | Supported transport modes                                                                                                                                                                                                                                                                                                                                          |
+| Property ID:     | stm (0x0001)                                                                                                                                                                                                                                                                                                                                                       |
+| Description:     | <p>This property is used to determine which transport modes are supported by the MG. It is also used to determine the current mode in use.</p> <p>The MGC may perform an <i>AuditCapabilities</i> to determine which transport modes are supported by the MG. The MGC may perform an <i>AuditValue</i> to determine the transport mode that is in current use.</p> |
+| Type:            | Enumeration                                                                                                                                                                                                                                                                                                                                                        |
+| Possible values: | A value representing an ITU-T H.248 transport mode protocol stack combination (see Table 1).                                                                                                                                                                                                                                                                       |
+| Default:         | Provisioned or defined by a profile specification.                                                                                                                                                                                                                                                                                                                 |
+| Defined in:      | TerminationState (Root Termination only)                                                                                                                                                                                                                                                                                                                           |
+| Characteristics: | Read only                                                                                                                                                                                                                                                                                                                                                          |
+
+**Table 1 – Property values for ITU-T H.248 transport modes**
+
+|      | Text codepoint        | Binary Codepoint | Protocol Stack         | Reference                   |
+|------|-----------------------|------------------|------------------------|-----------------------------|
+| IPv4 | UDP   IP4             | 0x0000           | UDP/IPv4               | Annex D of [ITU-T H.248.1]  |
+|      | UDP   IP4 - IPS       | 0x0001           | UDP/IPsec/IPv4         | + [IETF RFC 4301]           |
+|      | UDP   IP4 - DTLS      | 0x0002           | UDP/DTLS/IPv4          | + [IETF RFC 4347]           |
+|      | TCP   IP4             | 0x0003           | TCP/IPv4               | Annex D of [ITU-T H.248.1]  |
+|      | TCP   IP4 - IPS       | 0x0004           | TCP/IPsec/IPv4         | + [IETF RFC 4301]           |
+|      | TCP   IP4 - TLS       | 0x0005           | TCP/TLS/IPv4           | + [IETF RFC 5246]           |
+|      | SCTP   IP4            | 0x0006           | SCTP/IPv4              | [ITU-T H.248.4]             |
+|      | SCTP   IP4 - IPS      | 0x0007           | SCTP/IPsec/IPv4        | + [IETF RFC 4301]           |
+|      | SCTP   IP4 - TLS      | 0x0008           | SCTP/TLS/IPv4          | + [IETF RFC 5246]           |
+|      | M3UA/SCTP   IP4       | 0x0009           | M3UA/SCTP/IPv4         | [ETSI TS 129 202]           |
+|      | M3UA/SCTP   IP4 - IPS | 0x000a           | M3UA/SCTP/IPsec/IPv4   | + [IETF RFC 4301]           |
+|      | M3UA/SCTP   IP4 - TLS | 0x000b           | M3UA/SCTP/TLS/IPv4     | + [IETF RFC 5246]           |
+| IPv6 | UDP   IP6             | 0x000c           | UDP/IPv6               | Annex D of [ITU-T H.248.1]  |
+|      | UDP   IP6 - IPS       | 0x000d           | UDP/IPsec/IPv6         | + [IETF RFC 4301]           |
+|      | UDP   IP6 - DTLS      | 0x000e           | UDP/DTLS/IPv6          | + [IETF RFC 5246]           |
+|      | TCP   IP6             | 0x000f           | TCP/IPv6               | Annex D of [ITU-T H.248.1]  |
+|      | TCP   IP6 - IPS       | 0x0010           | TCP/IPsec/IPv6         | + [IETF RFC 4301]           |
+|      | TCP   IP6 - TLS       | 0x0011           | TCP/TLS/IPv6           | + [IETF RFC 5246]           |
+|      | SCTP   IP6            | 0x0012           | SCTP/IPv6              | [ITU-T H.248.4]             |
+|      | SCTP   IP6 - IPS      | 0x0013           | SCTP/IPsec/IPv6        | + [IETF RFC 4301]           |
+|      | SCTP   IP6 - TLS      | 0x0014           | SCTP/TLS/IPv6          | + [IETF RFC 5246]           |
+|      | M3UA/SCTP   IP6       | 0x0015           | M3UA/SCTP/IPv6         | [ETSI TS 129 202]           |
+|      | M3UA/SCTP   IP6 - IPS | 0x0016           | M3UA/SCTP/IPsec/IPv6   | + [IETF RFC 4301]           |
+|      | M3UA/SCTP   IP6 - TLS | 0x0017           | M3UA/SCTP/TLS/IPv6     | + [IETF RFC 5246]           |
+| ATM  | MTP3b   ATM           | 0x0018           | MTP-3b/N-SAAL/AAL5/ATM | clause 6 of [ITU-T H.248.5] |
+|      | SSCOP   ATM           | 0x0019           | SSCOP/AAL5/ATM         | clause 7 of [ITU-T H.248.5] |
+|      | ALF/AAL5   ATM        | 0x001a           | ALF/AAL5/ATM           | clause 8 of [ITU-T H.248.5] |
+
+#### 6.1.1.1 Encoding examples
+
+##### 6.1.1.1.1 Text encoding
+
+Example 1 – An ITU-T H.248 MG supports UDP for both IP versions. IPv4 is the preferred mode and thus the default configuration:
+
+trm/stm=[UDP | IP4, UDP | IP6]
+
+Example 2 – Additional SCTP support. SCTP via IPv6 is here the preferred mode:
+
+trm/stm=[SCTP | IP6, UDP | IP4, SCTP | IP4, UDP | IP6]
+
+Example 3 – An ITU-T H.248 MG with ATM and IP support (e.g., prepared for an ATM-to-IP network evolution):
+
+trm/stm=[MTP3b | ATM, SCTP | IP4]
+
+## 6.2 Events
+
+None.
+
+## 6.3 Signals
+
+None.
+
+## 6.4 Statistics
+
+None.
+
+## 6.5 Error codes
+
+### 6.5.1 Alternate transport mode preferred
+
+Error code #: 507
+
+Name: Alternate Transport Mode Preferred
+
+Definition: As a result of the reception of a *ServiceChange* request command containing a transport mode extension parameter, the MGC has decided to use an alternate transport mode. This alternate mode is included in the error text. Optionally an address that the MG can subsequently use to contact the MGC with the new transport may be provided.
+
+Error text in the error descriptor: A string of type *transportInformation* defined by:  
+`transportInformation = transportMode [COMMA mId]  
+; mId is encoded as per Annex B/H.248.1  
+transportMode = VALUE  
+; Value is encoded with a single text codepoint from Table 1`
+
+Comment: None.
+
+## 6.6 Procedures
+
+### 6.6.1 ServiceChange – Transport mode determination
+
+A particular transport mode is tightly coupled with the ITU-T H.248 control association concept. Any changes of particular "attributes" of a control association (e.g., like ITU-T H.248 protocol version, profile, etc.) are related to *ServiceChange* procedures.
+
+This package defines a parameter that is used in the *ServiceChangeExtension* parameter. It may be used by MGs/MGCs to negotiate the transport to be used in the initial *ServiceChange* exchange. For more information regarding the definition of parameters in the *ServiceChangeExtension* parameter see clause 7.2.8.1.8 of [ITU-T H.248.1]. The package also defines a property which may be audited by the MGC to determine the available transport modes on the MG.
+
+#### 6.6.1.1 Transport mode extension parameter definition
+
+Name: transmode
+
+Type: Sub-list of enumeration
+
+Possible values: As per Table 1.
+
+### 6.6.2 Initial transport mode determination
+
+The establishment of the very first control association between a MGC-MG tandem shall be denoted as bootstrapping. The MG must select a transport mode for the very first ITU-T H.248 message issued by the MG (which carries a *ServiceChange.request* command). This selection implies prior knowledge and relates to a provisioning (configuration management) activity of the values for the property defined in this package.
+
+Transport mode negotiation is initiated by the MG. Where the MG supports multiple transport modes it may include the supported transports in the Service Change extension parameter containing a "Transport mode" parameter. The transports are provided in a preferential list. The first
+
+in the list is the highest preference. This preference is unrelated to the transport being used to send the transport mode extension; i.e., the MG may prefer to use a transport other than the one currently being used.
+
+NOTE 1 – According to clause 7.2.8.1.8 of [ITU-T H.248.1] an "X-SC" coded ExtensionParameter is only used with ITU-T H.248.1 version 1 coded messages. As such, the use of a ServiceChange extension parameter containing a "Transport mode" parameter is only applicable to a ServiceChange command from a MG that registers with an MGC. As per clause 11.3 of [ITU-T H.248.1], this ServiceChange request shall always be encoded with a version equal to 1.
+
+On reception of a ServiceChange extension parameter containing the "transport mode" parameter, the MGC may take one of two actions. If it does not understand the parameter, it will be ignored and the *ServiceChange.response* is issued as normal. On reception of the *ServiceChange.response*, the MG will continue to use the same transport as the initial *ServiceChange.request*.
+
+If the MGC does support the transport mode parameter, it shall then examine the transport modes and determine if a new transport mode is to be used. If so, the MGC shall respond with a *ServiceChange* response containing error code 507 "*Alternate Transport Mode Preferred*". The error descriptor shall contain both the error code and error text as described in clause 6.5.1. The error text shall contain the transport mode that the MGC requires the MG to use. It may also contain the address (*mId*) where the MG should send a subsequent *ServiceChange.request* to using the indicated transport. A subsequent *ServiceChange.request* is needed as the error response will terminate the initiation of a control association.
+
+NOTE 2 – The used ServiceChangeMethod and ServiceChangeReason are independent of the use of the "transport mode" parameter. These are dependent on the required MG action. If the MG action is purely to change the transport mode of an ongoing control association ServiceChangeReason 917 "Capability Change" should be used.
+
+On reception of a *ServiceChange* response with error code 507, the MG should resend the initial *ServiceChange* command to the MGC using the new transport mode. The MG should use the new address from the MGC if provided, otherwise the destination may be determined via provisioning or other means. The "transport mode" ServiceChange extension parameter is not needed in this request.
+
+### 6.6.3 Auditing and changing the transport mode
+
+The MGC may use an *AuditCapabilities* command to audit the Supported Transport modes (*trm/stm*) property to determine which transport the MG supports. In response to an *AuditCapabilities* command, the MG shall return the transport modes in a preferential list with the first element being the most preferred (or default). The MGC may use an *AuditValue* command to determine the transport currently in use.
+
+If the MGC requires that a transport from the list of those supported is to be used, it shall issue a "MGC initiated MG Re-Registration" or "MGC Initiated Service Restoration" procedure (as defined in clauses F.3.8 and F.3.9 of [ITU-T H.248.1]). As the MG supports the *trm* package, it shall provide the list of supported transports as per clause 6.6.2. The MGC may then indicate the transport to be used as per clause 6.6.2.
+
+### 6.6.4 Transport modes with encryption
+
+Any usage of, or any change to, a transport mode with encryption may require additional information (e.g., encryption keys) to be exchanged between the MGC and MG. This aspect is out of scope of this Recommendation.
+
+### 6.6.5 Examples
+
+#### 6.6.5.1 MGC supports the initial transport
+
+In this example, the MG sends a list of supported transports. The MG uses the preferred transport and the MGC also prefers this.
+
+- 1) An MG registers with an MGC using the *ServiceChange* command. The ITU-T H.248 MG supports UDP for both IP versions, however IPv4 is the preferred mode.
+
+MG1 to MGC:
+
+```
+MEGACO/1 [124.124.124.222]  
+Transaction = 9998 {  
+    Context = - {  
+        ServiceChange = ROOT {Services {  
+            Method=Restart,  
+            Reason="901",      ; example of 'Cold Boot'  
+            Version=3,  
+            ServiceChangeAddress=55555,  
+                                ; Indication of IP port redirection  
+            Profile=ResGW/1,  
+            X-SC="transmode=[UDP|IP4,UDP|IP6]" } ; Note  
+        }  
+    }  
+}
+```
+
+NOTE – The mID (message identifier) value is omitted here, indicating that the address of the (MG local) UDP transport interface will not change.
+
+- 2) The MGC sends a reply:
+
+```
+MGC to MG1:  
+MEGACO/1 [123.123.123.4]:55555  
+Reply = 9998 {  
+    Context = - {  
+        ServiceChange = ROOT {  
+            Services {  
+                ServiceChangeAddress=55555} ; Confirmation of IP port redirection  
+            }  
+        }  
+    }  
+}
+```
+
+#### 6.6.5.2 MGC prefers an alternate transport
+
+In this example, the MG sends a list of supported transports. The MG has used the preferred transport "UDP/IP4" for the initial message, however the MGC prefers the use of "UDP|IP6".
+
+- 1) An MG registers with an MGC using the *ServiceChange* command. The ITU-T H.248 MG supports UDP for both IP versions, however IPv4 is the preferred mode.
+
+MG1 to MGC:
+
+```
+MEGACO/1 [124.124.124.222]  
+Transaction = 9990 {  
+    Context = - {  
+        ServiceChange = ROOT {Services {  
+            Method=Restart,  
+            Reason="901",      ; example of 'Cold Boot'  
+            Version=3,  
+            ServiceChangeAddress=55555,
+```
+
+```
+
+        Profile=ResGW/1,
+        X-SC="transmode=[UDP|IP4,UDP|IP6] "
+    }
+}
+}
+
+```
+
+- 2) The MGC prefers the use of UDP|IP6. Therefore it sends an error reply indicating this and an address for subsequent communications.
+
+```
+
+MGC to MG1:
+MEGACO/1 [123.123.123.4]:55555
+Reply = 9990 {
+    Context = - {
+        ServiceChange = ROOT {
+            Error=507{"UDP|IP6,[2001:db8:85a3:0:0:8a2e:370:7334] "}
+        }
+    }
+}
+
+```
+
+- 3) As no control association is established, the MG resends the initial *ServiceChange* registration using the new transport and the address indicated in step 2).
+
+```
+
+MG1 to MGC:
+
+MEGACO/1 [2001:db8:85a3:0:0:8a2e:370:7335]; NOTE
+Transaction = 9991 {
+    Context = - {
+        ServiceChange = ROOT {Services {
+            Method=Restart,
+            Reason="901",
+            Version=3,
+            ServiceChangeAddress=55555,
+            Profile=ResGW/1}
+        }
+    }
+}
+
+```
+
+NOTE – The mID (message identifier) value of MG1 changes in this example (see steps 1 and 3) due to the chosen mID format ("IP transport address"). However, a transport mode may not necessarily lead to a mID change.
+
+- 4) The MGC sends a reply confirming the control association:
+
+```
+
+MGC to MG1:
+MEGACO/1 [2001:db8:85a3:0:0:8a2e:370:7334]:55555
+Reply = 9991 {
+    Context = - {
+        ServiceChange = ROOT {
+            Services {ServiceChangeAddress=55555}
+        }
+    }
+}
+
+```
+
+# Bibliography
+
+- [b-ITU-T H.Sup7] ITU-T Supplement H.Sup7 (2008), *Gateway control protocol: Establishment procedures for the H.248 MGC-MG control association.*
+
+
+
+## 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.68-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.68-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a
--- /dev/null
+++ b/marked/H/T-REC-H.248.68-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.68-200903-I_PDF-E/raw.md b/marked/H/T-REC-H.248.68-200903-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..ed0119573c52522b93dd0d4c8466ed0dbeb40651
--- /dev/null
+++ b/marked/H/T-REC-H.248.68-200903-I_PDF-E/raw.md
@@ -0,0 +1,320 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.68**
+
+(03/2009)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+---
+
+**Gateway control protocol: Package for removal  
+of digits and tones**
+
+Recommendation ITU-T H.248.68
+
+# 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        |
+| <b>Communication procedures</b>                                               | <b>H.240–H.259</b> |
+| 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.68**
+
+# **Gateway control protocol: Package for removal of digits and tones**
+
+## **Summary**
+
+Recommendation ITU-T H.248.68 defines a package that allows a media gateway controller to indicate to a media gateway whether to remove tones and/or digits from the media stream where the package properties are set.
+
+###### **Source**
+
+Recommendation ITU-T H.248.68 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 Removal of digits and tones Package .....   | 2    |
+| 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    |
+| Bibliography.....                             | 5    |
+
+
+
+# Gateway control protocol: Package for removal of digits and tones
+
+# 1 Scope
+
+This Recommendation defines a package that allows a media gateway controller (MGC) to indicate to a media gateway (MG) whether it should remove tones (such as those defined in [ITU-T H.248.27]) and/or DTMF digits (such as those defined in [ITU-T H.248.16]) from the media stream where the package properties are set. It is applicable to media streams transported over any type of transport protocol.
+
+This Recommendation primarily addresses signal (tone and digit) removal, rather than signal relay.
+
+Any signal removal capability requires a signal detection capability. In many systems there is first a "pre-detection" phase where there is a notification that a tone may be starting. Thus, signal detection requires a minimum detection time (e.g.,  $T_{min}$ ).
+
+If this notification is given after a minimal amount of time (typically 1 to 5 ms), the false alarm rate may be high. Therefore, the period of the minimum detection time leads to the following considerations:
+
+- a) 100% signal removal implies an artificial delay in the forwarding of media/bearer traffic.  
+The delay in forwarding of bearer traffic in certain cases may be acceptable; however, for real-time communications, this typically is not appropriate.
+- b) Signal removal without additional delay implies only X% of signal removal (with  $X < 100\%$ ), i.e., the signal is partially removed.
+
+The partial removal of X% leads to a 'leakage' in the forwarding direction, where "leakage" is the partial transmission of the signal. The acceptable leakage depends on the type of signal and/or tele/bearer service. Too much leakage may lead to problems in subsequent gateways/terminals, with stray audio confusing signal processing equipment and/or users, and with degradation of non-tone speech. Therefore, enabling the tone/digit removal function may cause problems that would otherwise not happen if the received signal was kept.
+
+- c) Samples may be discarded during the pre-detection phase
+
+In order to keep the delay down, samples received in the initial "pre-detection" phase are often used but not forwarded by the signal detection equipment. Signals are not released to the other end until the signal detection capability is more certain as to what signal(s) are present. This may result in loss of a few milliseconds of speech when the signal pre-detection is a false alarm.
+
+As can be observed, the signal removal capabilities in this Recommendation have important network performance/quality aspects. However, these aspects are not issues specific to an H.248 implementation. The same aspects occur in all signal removal equipment, whether it is for split or monolithic MGC/MGs.
+
+# 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*.
+
+[ITU-T H.248.27] Recommendation ITU-T H.248.27 (2003), *Gateway control protocol: Supplemental tones packages*.
+
+# 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] Add command request.
+
+**3.1.2 MOD.req:** [ITU-T H.248.1] Modify command request.
+
+**3.1.3 MOV.req:** [ITU-T H.248.1] Move command request.
+
+**3.1.4 NOTIFY.req:** [ITU-T H.248.1] Notify command request.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 signal:** For the purposes of descriptions in this Recommendation, "signal" comprises "tone" and (MF or DTMF) "digit".
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+DTMF Dual Tone Multi-Frequency
+
+MF Multi-Frequency
+
+MG Media Gateway
+
+MGC Media Gateway Controller
+
+# 5 Conventions
+
+None.
+
+# 6 Removal of digits and tones package
+
+Package Name: Removal of digits and tones
+
+Package ID: rdt (0x00e9)
+
+Description: This package defines a mechanism which allows the MGC to set whether or not the tones and/or digits should be removed from the received media stream by the MG before passing it through into the Context for further processing or transmission.
+
+Version: 1
+
+Extends: None
+
+## 6.1 Properties
+
+### 6.1.1 Tone Removal
+
+Property Name: Tone Removal  
+Property ID: tr (0x0001)  
+Description: This property indicates whether tones in the media stream should remain or be removed.  
+Type: Boolean  
+Possible values: *On* – Tones are removed from the media stream  
+*Off* – Tones remain in the media stream  
+Default: *Off*  
+NOTE – While [b-IETF RFC 5022] defines the default to be "*On*", in this Recommendation the default is set to "*Off*" in order to align with H.248 behaviour.  
+Defined in: LocalControl  
+Characteristics: Read/Write
+
+### 6.1.2 Tone Removal List
+
+Property Name: Tone Removal List  
+Property ID: trl (0x0002)  
+Description: This property indicates the list of tones that should be removed from the media stream.  
+Type: Sub-list of String (text), Sub-list of Octet String (binary)  
+Possible values: Each element of the sub-list is a valid H.248 PackageID/SignalID pair related to a particular toneID. They are formatted according to the pkgdName syntax. To indicate "all" tones, the text "all" is used in the case of text encoding, or the value "0xFFFF" is used in the case of binary encoding.  
+Default: "all" tones  
+Defined in: LocalControl  
+Characteristics: Read/Write
+
+### 6.1.3 Digit Removal
+
+Property Name: Digit Removal  
+Property ID: dr (0x0003)  
+Description: This property indicates whether digits in the media stream should be removed or remain.  
+Type: Boolean  
+Possible values: *On* – Digits are removed from the media stream  
+*Off* – Digits remain in the media stream  
+Default: *Off*  
+NOTE – While [b-IETF RFC 5022] defines the default to be "*On*", in this Recommendation the default is set to "*Off*" in order to align with H.248 behaviour.  
+Defined in: LocalControl
+
+Characteristics: Read/Write
+
+## 6.2 Events
+
+None.
+
+## 6.3 Signals
+
+None.
+
+## 6.4 Statistics
+
+None.
+
+## 6.5 Error codes
+
+None.
+
+## 6.6 Procedures
+
+The default behaviour of H.248 with respect to removal of tones (including DTMF) from media streams is that the MGC assumes that the MG does not alter the media stream, and the tones pass through into the Context. If the MGC requires that for a certain media stream the tones and/or digits be removed, it should use the removal of digits and tones (*rdt*) package to indicate this.
+
+Whilst [ITU-T H.248.1] treats digit detection as an extension of tone detection, DTMF digits are not treated as tones for the purposes of this package.
+
+If the MGC sets the Tone Removal (*rdt/tr*) property to "On", the MG shall remove all detected tones from the media stream and the property is set on before passing it through into the Context for further processing or transmission.
+
+While the *rdt/tr* property is set with "On", if the MGC wants to individually control which tones are to be removed, it shall set the Tone Removal List (*rdt/trl*) property to include these tones. The MG shall then remove only the detected tones indicated by the *rdt/trl* property from the media stream. The *rdt/trl* property is unavailable when the *rdt/tr* property is valued "Off".
+
+The tone removal should occur at the detection stage. Example behaviours are:
+
+- If an event was set on the media stream to detect the tone, it would still be detected and reported to the MGC. Then, the tone would be removed from the media stream before passing it through into the Context for further processing or transmission.
+- If the media stream was being recorded, the tone would not appear in the recording. This is because recording is considered as a further processing in the Context, which would occur later than the event detected.
+- If the media stream is transmitted to other terminations in the Context or other endpoint, they would not receive it.
+
+NOTE – A MG usually only has the capability to detect a certain set of tones. If a tone not belonging to that set is received on the MG, it cannot be detected and will be passed through into the Context.
+
+If the MGC sets the *rdt/tr* property to "Off", or this property uses the default value, tones will be passed with the media stream into the Context for further processing or transmission.
+
+The use of the Digit Removal (*rdt/dr*) property is as per the *rdt/tr* property, except that DTMF digits (instead of tones) are affected.
+
+# Bibliography
+
+- [b-IETF RFC 5022] IETF RFC 5022 (2007), *Media Server Control Markup Language (MSCML) and Protocol*.  
+<<http://www.ietf.org/rfc/rfc5022.txt?number=5022>>
+
+
+
+
+
+## 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.69-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.248.69-200903-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a
--- /dev/null
+++ b/marked/H/T-REC-H.248.69-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.69-200903-I_PDF-E/raw.md b/marked/H/T-REC-H.248.69-200903-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..accb61b8a1411254db463efa3cb7ce56fcc189cb
--- /dev/null
+++ b/marked/H/T-REC-H.248.69-200903-I_PDF-E/raw.md
@@ -0,0 +1,1640 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.69**
+
+(03/2009)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+# --- **Gateway control protocol: Packages for interworking between MSRP and H.248**
+
+Recommendation ITU-T H.248.69
+
+## 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        |
+| <b>Communication procedures</b>                                               | <b>H.240–H.259</b> |
+| 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.69**
+
+# **Gateway control protocol: Packages for interworking between MSRP and H.248**
+
+# **Summary**
+
+Recommendation ITU-T H.248.69 defines packages and procedures to enable the message session relay protocol (MSRP) to be sent and received on a H.248 controlled media gateway (MG). It further allows communication between an MGC and MG regarding the messaging policy, messaging statistics and message protocol connection state.
+
+###### **Source**
+
+Recommendation ITU-T H.248.69 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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    | Messaging streams.....                    | 2  |
+| 6.1  | Session establishment.....                | 2  |
+| 6.2  | Connection establishment.....             | 2  |
+| 6.3  | Recording messages .....                  | 4  |
+| 6.4  | Playing messages.....                     | 4  |
+| 6.5  | Deleting messages .....                   | 4  |
+| 6.6  | Connection removal.....                   | 4  |
+| 7    | Message conferencing .....                | 4  |
+| 8    | MSRP Statistics Package .....             | 4  |
+| 8.1  | Properties.....                           | 5  |
+| 8.2  | Events .....                              | 5  |
+| 8.3  | Signals .....                             | 11 |
+| 8.4  | Statistics.....                           | 11 |
+| 8.5  | Error codes.....                          | 12 |
+| 8.6  | Procedures .....                          | 12 |
+| 9    | MSRP Connection Status Package .....      | 13 |
+| 9.1  | Properties.....                           | 13 |
+| 9.2  | Events .....                              | 13 |
+| 9.3  | Signals .....                             | 13 |
+| 9.4  | Statistics.....                           | 14 |
+| 9.5  | Error codes.....                          | 14 |
+| 9.6  | Procedures .....                          | 14 |
+| 10   | Play Message Package.....                 | 14 |
+| 10.1 | Properties.....                           | 14 |
+| 10.2 | Events .....                              | 14 |
+| 10.3 | Signals .....                             | 15 |
+| 10.4 | Statistics.....                           | 17 |
+| 10.5 | Error codes.....                          | 17 |
+| 10.6 | Procedures .....                          | 17 |
+
+|      | Page                                        |    |
+|------|---------------------------------------------|----|
+| 11   | Delete Stored Message Package .....         | 18 |
+| 11.1 | Properties .....                            | 18 |
+| 11.2 | Events .....                                | 18 |
+| 11.3 | Signals .....                               | 18 |
+| 11.4 | Statistics .....                            | 19 |
+| 11.5 | Error Codes .....                           | 19 |
+| 11.6 | Procedures .....                            | 19 |
+| 12   | Messaging Session Information Package ..... | 19 |
+| 12.1 | Properties .....                            | 19 |
+| 12.2 | Events .....                                | 20 |
+| 12.3 | Signals .....                               | 20 |
+| 12.4 | Statistics .....                            | 20 |
+| 12.5 | Error codes .....                           | 20 |
+| 12.6 | Procedures .....                            | 21 |
+| 13   | Messaging Filtering Package .....           | 21 |
+| 13.1 | Properties .....                            | 21 |
+| 13.2 | Events .....                                | 22 |
+| 13.3 | Signals .....                               | 24 |
+| 13.4 | Statistics .....                            | 24 |
+| 13.5 | Error codes .....                           | 24 |
+| 13.6 | Procedures .....                            | 25 |
+| 14   | Stored Message Information Package .....    | 27 |
+| 14.1 | Properties .....                            | 27 |
+| 14.2 | Events .....                                | 27 |
+| 14.3 | Signals .....                               | 27 |
+| 14.4 | Statistics .....                            | 30 |
+| 14.5 | Error codes .....                           | 30 |
+| 14.6 | Procedures .....                            | 30 |
+| 15   | Record Message Package .....                | 30 |
+| 15.1 | Properties .....                            | 30 |
+| 15.2 | Events .....                                | 30 |
+| 15.3 | Signals .....                               | 31 |
+| 15.4 | Statistics .....                            | 32 |
+| 15.5 | Error codes .....                           | 32 |
+| 15.6 | Procedures .....                            | 32 |
+
+# Recommendation ITU-T H.248.69
+
+# Gateway control protocol: Packages for interworking between MSRP and H.248
+
+# 1 Scope
+
+This Recommendation defines packages and procedures to enable the message session relay protocol (MSRP) to be sent and received on a H.248 controlled media gateway (MG). It further allows communication between an MGC and MG regarding the messaging policy, messaging statistics and message protocol connection state.
+
+It is assumed that the MG contains the MSRP switch functionality.
+
+NOTE – The use of MSRP over TLS 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 H.248.1] Recommendation ITU-T H.248.1 (2005), *Gateway control protocol: Version 3*.
+- [ITU-T H.248.7] Recommendation ITU-T H.248.7 (2004), *Gateway control protocol: Generic announcement package*.
+- [ITU-T H.248.9] Recommendation ITU-T H.248.9 (2005), *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*.
+- [ITU-T H.248.43] Recommendation ITU-T H.248.43 (2008), *Gateway control protocol: Packages for gate management and gate control*.
+- [ITU-T H.248.47] Recommendation ITU-T H.248.47 (2008), *Gateway control protocol: Statistic conditional reporting package*.
+- [IETF RFC 2822] IETF RFC 2822 (2001), *Internet Message Format*.
+- [IETF RFC 3339] IETF RFC 3339 (2002), *Date and Time on the Internet: Timestamps*.
+- [IETF RFC 3860] IETF RFC 3860 (2004), *Common Profile for Instant Messaging (CPIM)*.
+- [IETF RFC 3862] IETF RFC 3862 (2004), *Common Presence and Instant Messaging (CPIM): Message format*.
+- [IETF RFC 3986] IETF RFC 3986 (2005), *Uniform Resource Identifier (URI): Generic Syntax*.
+- [IETF RFC 4021] IETF RFC 4021 (2005), *Registration of Mail and MIME Header Fields*.
+- [IETF RFC 4975] IETF RFC 4975 (2007), *The Message Session Relay Protocol (MSRP)*.
+- [IETF RFC 4976] IETF RFC 4976 (2007), *Relay Extensions for the Message Session Relay Protocol (MSRP)*.
+- [IETF RFC 5228] IETF RFC 5228 (2008), *Sieve: An Email Filtering Language*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following term defined elsewhere:
+
+**3.1.1 sieve** [IETF RFC 5228]: An Email Filtering Language.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 message identity:** Used between the MGC and MG in order to uniquely identify a particular message for H.248 procedural purposes. It may be the MSRP message identity but may be any valid identifier.
+
+**3.2.2 messaging stream:** A H.248 stream that contains SDP indicating that the connection media type format is related to messaging.
+
+**3.2.3 MSRP switch:** A media level entity that receives MSRP messages and delivers them to the other conference participants. An MSRP switch has a similar role to a conference mixer with the exception that an MSRP switch does not actually "mix" together different input media streams; it merely relays the messages between participants.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                |
+|------|--------------------------------|
+| MG   | Media Gateway                  |
+| MGC  | Media Gateway Controller       |
+| MSRP | Message Session Relay Protocol |
+| SDP  | Session Description Protocol   |
+
+# 5 Conventions
+
+None.
+
+# 6 Messaging streams
+
+## 6.1 Session establishment
+
+The MGC is responsible for determining the filtering criteria, based on subscriber information and any local policy. The filtering is enforced in two ways. Firstly, through the modification of the session requests received from users before the session description/configuration is provided to an MG. Secondly, filtering may occur within the messaging session with different actions being applied to messages received by a user's termination.
+
+## 6.2 Connection establishment
+
+In order for a MG to send and receive messages, a H.248 stream is created on a Termination in addition to any other streams, i.e., audio/video streams. The MGC shall assign a new StreamID for the stream. The characteristics of sent messaging may be set in the Local Descriptor and the characteristics of received messaging may be set in the Remote Descriptor.
+
+The addressing information for the messaging stream may be set via a session description protocol (SDP) connection "c=" line.
+
+The MGC shall indicate that the stream is for messaging through the use of a SDP media "m=" line. See clause 8.1 of [IETF RFC 4975] for details on how to set the components of this line.
+
+The MGC may indicate or request the allowed media types and formats through the use of the SDP "accept-types" attribute (see clause 8.6 of [IETF RFC 4975]). Messages received with message media types and formats not included in attribute are discarded by the MG.
+
+The MGC may indicate or request the maximum message size through the SDP "max-size" attribute (see clause 8.6 of [IETF RFC 4975]).
+
+The MGC may also set message level filters in order to request the MG to perform certain actions based on different message characteristics.
+
+Session level filtering (i.e., that is described in SDP) related to message media types, media formats and maximum message size is applied to messages entering the termination from an MG external direction.
+
+Message level filtering is typically applied to messages received on a termination from other terminations in the associated context.
+
+Additional characteristics of the messaging session may be set via the "Message Session Information" (*msi*) package (see clause 12).
+
+In addition to providing information regarding the allowed messages, the MGC may set quotas for the sending and reception of messages on a termination/stream. See clause 8.6.1 for more details.
+
+Once the message characteristics have been negotiated with the end user (see [IETF RFC 4975] for an example on how this is achieved) and the SDP related to the message stream has been set, then the MG shall wait for a MSRP connection request from the peer. If the MGC sends the "Establish MSRP Connection" (*msrpstat/conn*) signal, then the MG shall be responsible for initiating the MSRP connection. Once the connection is established, the MG shall then be responsible for MSRP signalling according to [IETF RFC 4975].
+
+NOTE – Clause 4 of [IETF RFC 4975] indicates that MSRP nodes may support multiple sessions over a single MSRP connection. In this case, multiple H.248 Streams are used for each session; however, the connection information will remain the same (see clause 8.1 of [IETF RFC 4975]).
+
+The MG shall then relay the MSRP messages between terminations containing the same StreamID. If a message is relayed to a termination that has message level filtering applied to it, the filter shall be applied before sending the message to the user represented by the termination. See clause 13 for more information.
+
+When sending MSRP "SEND Requests", the MG should follow the chunk size recommendations in clause 7.1.1 of [IETF RFC 4975]; however the chunk size may be altered via provisioning.
+
+Clause 8.9 of [IETF RFC 4975] describes the relationship between the SDP Direction Attribute and MSRP. [ITU-T H.248.1] contains the StreamMode property in the Local Control descriptor. The StreamMode property shall take precedence over the SDP Direction Attribute. The effect of the StreamMode property values shall be the same as described in clause 8.9 of [IETF RFC 4975].
+
+Clause 5.4 of [IETF RFC 4975] describes the MSRP Connection model. In order for the MGC to be aware of the status of the connection, it should set the "MSRP Connection Failure" event (see clause 9.2.1). If the MGC wishes to re-establish the MSRP connection (and associated Sessions), then the MGC should resend the *msrpstate/conn* signal.
+
+As per clause 8.4 of [IETF RFC 4975], the MGC may send SDP exchanges to refresh the network state. The MGC is responsible for determining when this occurs. However, if it needs the updated SDP "path" attribute information, it may perform a wildcard CHOOSE on this attribute to determine the current value.
+
+## 6.3 Recording messages
+
+It is assumed that the MGC is responsible for receiving application level requests related to the storage of messaging. The MGC is responsible for maintaining the list of URIs that are related to a particular user/subscriber and is also responsible for determining who may access this data.
+
+From a H.248 perspective, once a connection is established, the MGC may request via the "Store Message Package" that messages sent and/or received on a Termination/Stream be stored in a particular URI for later play out. See clause 15 for more details.
+
+Messages may also be recorded as a result of a filtering action. This is achieved through the use of the Message Filtering Package (see clause 13). The MGC shall set the filter rules indicating which messages are applicable and the action "fileinto" to indicate that the applicable messages are stored. The MGC may also request notification of the storage of a message with the storage location and message identity, so that the MGC may later manage the stored messages.
+
+Further information regarding stored messages can be retrieved via the Stored Message Information Package (see clause 14).
+
+## 6.4 Playing messages
+
+Once a connection is established, the MGC may request via the "Play Message Package" that a message stored on the MG (or provided by the MGC) be played to that particular user (termination/stream). See clause 10 for more details.
+
+## 6.5 Deleting messages
+
+A MGC may request the MG to delete previously stored messages. See clause 11 for more details.
+
+## 6.6 Connection removal
+
+When the MGC requires the removal of a MSRP connection, it should remove the associated StreamID from the applicable termination. As per clause 5.4 of [IETF RFC 4975], the MGC should ensure that call level sessions related to MSRP connection are terminated before removing the connection.
+
+# 7 Message conferencing
+
+[ITU-T H.248.1] allows conferencing as part of its core functionality. [ITU-T H.248.19] describes audio and video conferencing configurations. MSRP conferencing follows the same principles, except that the messages are not mixed but relayed between terminations where the messaging stream is set. The use of a separate messaging stream allows the MG to support different types of media per termination.
+
+Identity management and privacy information is typically negotiated via session-based signalling. Thus the MGC is responsible for relaying this MSRP received information between participants.
+
+The MGC/MG may itself act as a conference participant, and thus it has the capability to generate messages to the other participants in the conference connection.
+
+# 8 MSRP Statistics Package
+
+Package Name: MSRP Statistics Package
+
+Package ID: msrpstat (0x00ea)
+
+**Description:** This package allows the MGC to set certain messaging statistics on the MG per termination or messaging stream. It also allows the MGC to determine the cumulative messaging statistics for a particular messaging stream/termination and also message specific information.
+
+**Version:** 1
+
+**Extends:** None.
+
+## **8.1 Properties**
+
+None.
+
+## **8.2 Events**
+
+### **8.2.1 Messaging Quota**
+
+**Event Name:** Messaging Quota
+
+**Event ID:** mquota (0x0001)
+
+**Description:** This event allows the MGC to send quotas for message sending and reception on a MG. It allows the MG to report when the quota has been reached. The MGC may set multiple instances of this event if different sending and reception quotas are subject to different time constraints.
+
+#### **8.2.1.1 EventsDescriptor parameters**
+
+##### **8.2.1.1.1 Number of Messages Sent Quota**
+
+**Parameter Name:** Number of Messages Sent Quota
+
+**Parameter ID:** msq (0x0001)
+
+**Description:** This parameter defines the maximum number of messages that may be sent from the Termination for the messaging stream.
+
+**Type:** Integer
+
+**Optional:** Yes
+
+**Possible values:** 0 – 65535 (0 indicates no limit)
+
+**Default:** 0
+
+##### **8.2.1.1.2 Number of Messages Received Quota**
+
+**Parameter Name:** Number of Messages Received Quota
+
+**Parameter ID:** mrq (0x0002)
+
+**Description:** This parameter defines the maximum number of messages that may be received on the termination for the messaging stream.
+
+**Type:** Integer
+
+**Optional:** Yes
+
+**Possible values:** 0 – 65535 (0 indicates no limit)
+
+**Default:** 0
+
+##### **8.2.1.1.3 Messages Sent Volume Quota**
+
+**Parameter Name:** Messages Sent Volume Quota
+
+**Parameter ID:** msv (0x0003)
+
+Description: This parameter defines the maximum cumulative total size (in octets) of messages that may be sent by the termination for the messaging stream.  
+Type: Integer  
+Optional: Yes  
+Possible values: 0 and upwards. "0" indicates no quota.  
+Default: 0
+
+##### **8.2.1.1.4 Messages Received Volume Quota**
+
+Parameter Name: Messages Received Volume Quota  
+Parameter ID: mrv (0x0004)  
+Description: This parameter defines the maximum cumulative total size (in octets) of messages that may be received on the termination for the messaging stream.  
+Type: Integer  
+Optional: Yes  
+Possible values: 0 and upwards. "0" indicates no quota.  
+Default: 0
+
+##### **8.2.1.1.5 Time Quota**
+
+Parameter Name: Time Quota  
+Parameter ID: tm (0x0005)  
+Description: This parameter defines for how long the quotas associated with the event are active. On expiry of the time, the event is reported.  
+Type: Integer  
+Optional: Yes  
+Possible values: 0 and upwards (in seconds). "0" indicates no quota.  
+Default: 0
+
+##### **8.2.1.1.6 Statistics Reported**
+
+Parameter Name: Statistics Reported  
+Parameter ID: statrep (0x0006)  
+Description: This parameter defines which statistics are reported with the observed event.  
+Type: Sub-list of Enumeration  
+Optional: Yes  
+Possible values: none (0x0000) No Statistics Reported  
+nms (0x0001) Number of Messages Sent  
+nmr (0x0002) Number of Messages Received  
+vms (0x0003) Volume of Messages Sent  
+vmr (0x0004) Volume of Messages Received  
+Default: (nms, nmr, vms, vmr) "All Statistics"
+
+#### 8.2.1.2 ObservedEventsDescriptor parameters
+
+##### 8.2.1.2.1 Quota Reached
+
+Parameter Name: Quota Reached  
+Parameter ID: qreach (0x0001)  
+Description: This parameter indicates which quota has triggered the reporting of the event.  
+Type: Enumeration  
+Optional: No  
+Possible values: msq (0x0001) Number of Messages Sent Quota  
+mrq (0x0002) Number of Messages Received Quota  
+msv (0x0003) Messages Sent Volume Quota  
+mrv (0x0004) Messages Received Volume Quota  
+tm (0x0005) Time Quota  
+Default: None.
+
+##### 8.2.1.2.2 Number of Messages Sent
+
+Parameter Name: Number of Messages Sent  
+Parameter ID: nms (0x0002)  
+Description: This parameter indicates the number of messages successfully sent by a messaging stream.  
+Type: Integer  
+Optional: Yes  
+Possible values: 0 and up  
+Default: None.
+
+##### 8.2.1.2.3 Number of Messages Received
+
+Parameter Name: Number of Messages Received  
+Parameter ID: nmr (0x0003)  
+Description: This parameter indicates the number of messages successfully received by a messaging stream.  
+Type: Integer  
+Optional: Yes  
+Possible values: 0 and up  
+Default: None.
+
+##### 8.2.1.2.4 Volume of Messages Sent
+
+Parameter Name: Volume of Messages Sent  
+Parameter ID: vms (0x0004)  
+Description: This parameter indicates the current cumulative total size (in octets) of all messages successfully sent by the messaging stream.  
+Type: Integer
+
+Optional: Yes  
+Possible values: 0 and up  
+Default: None.
+
+##### **8.2.1.2.5 Volume of Messages Received**
+
+Parameter Name: Volume of Messages Received  
+Parameter ID: vmr (0x0005)  
+Description: This parameter indicates the current cumulative total size (in octets) of all messages successfully received by the messaging stream.  
+Type: Integer  
+Optional: Yes  
+Possible values: 0 and up  
+Default: None.
+
+### **8.2.2 Individual Message Information Event**
+
+Event Name: Individual Message Information  
+Event ID: imi (0x0002)  
+Description: This event allows the MGC to request detailed information regarding the messages that a particular user sends.  
+NOTE – This event may result in a large number of notifications where a large number of messages are sent; however, for some services/charging detailed information is required.
+
+#### **8.2.2.1 EventsDescriptor parameters**
+
+##### **8.2.2.1.1 Information Requested**
+
+Parameter Name: Information Requested  
+Parameter ID: infreq (0x0001)  
+Description: This parameter allows the MGC to request the information that is reported when a message is received.  
+Type: Sub-list of Enumeration  
+Optional: Yes  
+Possible values: "fr" (0x0001) From  
+"to" (0x0002) To  
+"cc" (0x0003) Carbon (or Courtesy) Copy  
+"dt" (0x0004) Date and Time  
+"sb" (0x0004) Subject  
+"sz" (0x0005) Size  
+Default: None. If no value is provided, all the information is reported.
+
+#### 8.2.2.2 ObservedEventsDescriptor parameters
+
+##### 8.2.2.2.1 Message Identity
+
+Parameter Name: Message Identity  
+Parameter ID: mi (0x0001)  
+Description: This parameter indicates the MSRP message identity of the received message.  
+Type: String  
+Optional: No  
+Possible values: The string is of type "ident" defined by the following ABNF:  
+`ident = ALPHANUM 3*31ident-char`  
+`ident-char = ALPHANUM / "." / "-" / "+" / "%" / "="`  
+See clause 9 of [IETF RFC 4975].  
+Default: None.
+
+##### 8.2.2.2.2 "From" Information
+
+Parameter Name: "From" Information  
+Parameter ID: fr (0x0002)  
+Description: This parameter indicates the sender or originator of a message.  
+Type: String  
+Optional: Yes  
+Possible values: String of type "From-header". Syntax according to the following ABNF:  
+`From = [ Formal-name ] "<" URI ">"`  
+See clause 4.1 of [IETF RFC 3862] for more information.  
+Default: None.
+
+##### 8.2.2.2.3 "To" Information
+
+Parameter Name: "To" Information  
+Parameter ID: to (0x0003)  
+Description: This parameter specifies an intended recipient of a message.  
+Type: Sub-list of String  
+Optional: Yes  
+Possible values: Each instance of String of type "To-header". Syntax according to the following ABNF:  
+`To-header = [ Formal-name ] "<" URI ">"`  
+See clause 4.2 of [IETF RFC 3862] for more information.  
+Default: None.
+
+##### 8.2.2.2.4 "CC" Information
+
+Parameter Name: "CC" Information  
+Parameter ID: cc (0x0004)  
+Description: This parameter specifies a non-primary recipient for a message.
+
+Type: Sub-list of String  
+Optional: Yes  
+Possible values: Each instance of String of type "Cc-header". Syntax according to the following ABNF:  
+`Cc-header = [ Formal-name ] "<" URI ">"`  
+See clause 4.3 of [IETF RFC 3862] for more information.  
+Default: None.
+
+##### 8.2.2.2.5 "DateTime" Information
+
+Parameter Name: "DateTime" Information  
+Parameter ID: dt (0x0005)  
+Description: This parameter specifies the date and time a message was sent.  
+Type: String  
+Optional: Yes  
+Possible values: String of type "DateTime-header". Syntax according to the following ABNF:  
+`DateTime-header = date-time`  
+The syntax of 'date-time' is defined in [IETF RFC 3339].  
+See clause 4.4 of [IETF RFC 3862] for more information.  
+Default: None.
+
+##### 8.2.2.2.6 "Subject" Information
+
+Parameter Name: "Subject" Information  
+Parameter ID: sb (0x0006)  
+Description: This parameter contains a description of the topic of the message.  
+Type: Sub-list of String  
+Optional: Yes  
+Possible values: Each instance of String of type "Subject-header". Syntax according to the following ABNF:  
+`Subject-header = [ ";" Lang-param ] SP *HEADERCHAR`  
+See clause 4.5 of [IETF RFC 3862] for more information.  
+Default: None.
+
+##### 8.2.2.2.7 "Size" Information
+
+Parameter Name: "Size" Information  
+Parameter ID: sz (0x0007)  
+Description: This parameter contains the total size of the message in bytes.  
+Type: String  
+Optional: Yes
+
+Possible values: Each instance of String of type "total". Syntax according to the following ABNF:  
+`total = 1*DIGIT`  
+For more information, see the "byte-range" header in [IETF RFC 4975].  
+Default: None.
+
+## 8.3 Signals
+
+None.
+
+## 8.4 Statistics
+
+### 8.4.1 Number of Messages Sent
+
+Statistic Name: Number of Messages Sent  
+Statistic ID: nms (0x0001)  
+Description: This Statistics counts the number of messages successfully sent by a messaging stream.  
+Type: Integer  
+Possible values: 0 and up.  
+Level: Stream or Termination.
+
+### 8.4.2 Number of Messages Received
+
+Statistic Name: Number of Messages Received  
+Statistic ID: nmr (0x0002)  
+Description: This Statistics counts the number of messages successfully received by a messaging stream.  
+Type: Integer  
+Possible values: 0 and up.  
+Level: Stream or Termination.
+
+### 8.4.3 Volume of Messages Sent
+
+Statistic Name: Volume of Messages Sent  
+Statistic ID: vms (0x0003)  
+Description: This Statistics contains the current cumulative total size (in octets) of all messages successfully sent by the messaging stream.  
+Type: Integer  
+Possible values: 0 and up.  
+Level: Stream or Termination.
+
+### 8.4.4 Volume of Messages Received
+
+Statistic Name: Volume of Messages Received  
+Statistic ID: vmr (0x0004)  
+Description: This Statistics contains the current cumulative total size (in octets) of all messages successfully received by the messaging stream.
+
+Type: Integer  
+Possible values: 0 and up.  
+Level: Stream or Termination.
+
+## 8.5 Error codes
+
+None.
+
+## 8.6 Procedures
+
+### 8.6.1 Quotas
+
+Where the MGC requires that quotas are set for messaging sending and reception, it shall set the "Messaging Quota" (*msrpstat/mquota*) event with the applicable quotas. The MGC must set at least one of the quotas. The MGC may set multiple events where different metrics apply to different quotas.
+
+If the event is set at a termination level, then the quota applies to all messaging streams and represents a cumulative value for all the messaging streams. Events may also be set at a stream level which allows different message streams to have different quotas.
+
+If the "Time Quota" (*tm*) parameter is set with another quota(s), then time-based reporting will apply to those quotas. The MG shall Notify the event when the time period has elapsed even if the other quotas have been reached. The time-triggered report shall only contain the quota reached reason "Time Quota".
+
+If the "Number of Messages Sent Quota" (*msq*), "Number of Messages Received Quota" (*mrq*), "Messages Sent Volume Quota" (*msv*) or "Messages Received Volume Quota" (*mrv*) quotas have been reached, then a Notify will be triggered containing the quota reached reason related to the quota that has been reached.
+
+NOTE – In this package, volume (size) relates to the MSRP application layer, not to the underlying protocol layers (i.e., TCP/IP). An MG sending or receiving a complete message may cause it to exceed a volume quota. It is a matter of MG policy whether this full message is accepted or only partially accepted.
+
+Once a quota has been reached, the MG shall not send any messages or relay any received messages related to the user (Termination/Stream). However, the MG may still perform message related signalling, i.e., generating MSRP error replies, etc.
+
+### 8.6.2 Cumulative statistics
+
+In order for the MG to record statistics related to Messaging Stream, it should set the "Number of Messages Sent" (*nms*), "Number of Messages Received" (*nmr*), "Volume of Messages Sent" (*vms*) or "Volume of Messages Received" (*vmr*) Statistics. If these are set at a termination level, then the statistics represent a cumulative total for all messaging streams on a termination. Where multiple messaging Streams are used on a termination, the Statistics may be set on each Stream in order to record individual statistics.
+
+NOTE – The ability to set Statistics on a stream level was introduced in [ITU-T H.248.1] version 3.
+
+Any further action by the MGC is service dependent. An indication may be sent to the user indicating that their quota has been reached (i.e., via [ITU-T H.248.9]) or the messaging stream may be removed.
+
+Where an MGC requires notification of the above Statistics without applying quotas, then it shall use the events and procedures defined in [ITU-T H.248.47]. These allow the MGC to set value or time-based metrics for reporting. When these metrics are reporting, the MG shall not stop the sending or reception of messages.
+
+### 8.6.3 Individual message statistics
+
+Where the MGC wishes to receive real-time information regarding messages sent by a certain user (received at the MG), it should set the "Individual Message Information" (*msrpstat/imi*) Event indicating in the "Information Requested" (*infreq*) parameter what information it requires. The *msrpstat/imi* shall be set on the Termination/Stream representing the message sender. If this parameter is omitted, all information defined in the Package will be returned.
+
+Once the event is set, the MG shall generate a notification with the requested information for each message received (from external to the MG) by the termination/stream. If the received message does not contain the requested information, it shall be omitted from the notification to the MGC.
+
+# 9 MSRP Connection Status Package
+
+Package Name: MSRP Connection Status Package  
+Package ID: msrpcs (0x00eb)  
+Description: This package allows the MGC to determine the status of the MSRP connection related to a particular messaging stream.  
+Version: 1  
+Extends: None.
+
+## 9.1 Properties
+
+None.
+
+## 9.2 Events
+
+### 9.2.1 MSRP Connection Failure
+
+Event Name: MSRP Connection Failure  
+Event ID: fail (0x0001)  
+Description: This event indicates that the MG considers that the MSRP connection has failed.
+
+#### 9.2.1.1 EventsDescriptor parameters
+
+None.
+
+#### 9.2.1.2 ObservedEventsDescriptor parameters
+
+None.
+
+## 9.3 Signals
+
+### 9.3.1 Establish MSRP Connection
+
+Signal Name: Connect  
+Signal ID: conn (0x0001)  
+Description: This signal indicates that the MG is responsible for initiating an MSRP connection to its peer (indicated by the SDP in the associated stream).  
+Signal Type: Brief  
+Duration: Not Applicable.
+
+#### 9.3.1.1 Additional parameters
+
+None.
+
+## 9.4 Statistics
+
+None.
+
+## 9.5 Error codes
+
+None.
+
+## 9.6 Procedures
+
+Clause 8.5 of [IETF RFC 4975] indicates that "the party that sent the original offer is responsible for connecting to its peer." As this relates to call/session level signalling, the MGC has the knowledge of this and, in order for the MG to establish the MSRP connection, the MG must be provided with this information. When the MGC requires the establishment of a MSRP connection, it shall propagate the necessary SDP information (see clause 6) in the Local and Remote Descriptors. It shall then issue the "Establish MSRP Connection" (*msrpcs/conn*) Signal.
+
+When the MGC wishes to determine when and if the MSRP connection has failed, it shall set the "MSRP Connection Failure" (*msrpcs/fail*) event on the stream, associated with the messaging stream. When the MG detects a failure of the messaging stream it shall Notify the MGC via the "MSRP Connection Failure" (*fail*) event. The MG shall include the StreamID in the response in order to uniquely identify the messaging stream.
+
+# 10 Play Message Package
+
+Package Name: Play Message
+
+Package ID: mess (0x00ec)
+
+Description: This package allows the MGC to request the MG to send a particular message on a termination/stream.
+
+Version: 1
+
+Extends: None.
+
+## 10.1 Properties
+
+None.
+
+## 10.2 Events
+
+### 10.2.1 Message Sending Response Status
+
+Event Name: Message Sending Response Status
+
+Event ID: msrs (0x0001)
+
+Description: This event allows the MG to report the response status when the MGC has requested that a message is sent via the "Send Message" Signal. It is only reported if the MGC had indicated that success and failures should be reported to it.
+
+#### 10.2.1.1 EventsDescriptor parameters
+
+None.
+
+#### 10.2.1.2 ObservedEventsDescriptor parameters
+
+##### 10.2.1.2.1 Message Identity
+
+Parameter Name: Message Identity  
+Parameter ID: mi (0x0001)  
+Description: This parameter allows the MGC to correlate the received message status with its original message sending request.  
+Type: String  
+Optional: No  
+Possible values: The string is of type "ident" defined by the following ABNF:  
+`ident = ALPHANUM 3*31ident-char`  
+`ident-char = ALPHANUM / "." / "-" / "+" / "%" / "="`  
+See clause 9 of [IETF RFC 4975].  
+NOTE – Whilst the MSRP message identity encoding is used, a message identity other than the MSRP message identity may be used.  
+Default: None.
+
+##### 10.2.1.2.2 Status Code
+
+Parameter Name: Status Code  
+Parameter ID: sc (0x0002)  
+Description: This parameter indicates the status code associated with the response to sending a message via the "Send Message" signal.  
+Type: String  
+Optional: No  
+Possible values: The string is of type "Status" defined by the following ABNF:  
+`Status = namespace SP status-code [SP comment]`  
+`namespace = 3(DIGIT);`  
+`status-code = 3DIGIT ;`  
+See clause 9 of [IETF RFC 4975] for further ABNF definitions.  
+See clause 10 of [IETF RFC 4975] for a list of possible codes.  
+Default: None.
+
+## 10.3 Signals
+
+### 10.3.1 Send Message
+
+Signal Name: Send Message  
+Signal ID: sm (0x0001)  
+Description: This signal allows the MGC to request the MG to send a message from a particular termination/stream.  
+Signal Type: Brief  
+Duration: Not Applicable
+
+#### 10.3.1.1 Additional parameters
+
+##### 10.3.1.1.1 Message Identity
+
+Parameter Name: Message Identity  
+Parameter ID: mi (0x0001)  
+Description: This parameter allows the MGC to correlate the sent message with any requested failure or success reports.  
+Type: String  
+Optional: No  
+Possible values: The string is of type "ident" defined by the following ABNF:  
+`ident = ALPHANUM 3*31ident-char`  
+`ident-char = ALPHANUM / "." / "-" / "+" / "%" / "="`  
+See clause 9 of [IETF RFC 4975].  
+NOTE – Whilst the MSRP message identity encoding is used, a message identity other than the MSRP message identity may be used.  
+This parameter may also be wildcarded CHOOSE in order for the MG to supply the Message Identity when the MGC is unaware of the Identity. The MGC may also wildcard ALL if it requests all messages associated with a URI are to be sent.  
+Default: None.
+
+##### 10.3.1.1.2 Message Contents by reference
+
+Parameter Name: Message Contents by reference  
+Parameter ID: mcr (0x0002)  
+Description: This parameter allows the MGC to provide the MG with an URI which points to the message data that shall be sent.  
+Type: String  
+Optional: No  
+Possible values: As per [IETF RFC 3986].  
+Default: None.
+
+##### 10.3.1.1.3 Failure Report
+
+Parameter Name: Failure Report  
+Parameter ID: fr (0x0003)  
+Description: This parameter allows the MGC to indicate the failure reporting mode that the MG shall use when sending the message. In order for the MGC to receive the error response from the MG, it shall set the "Message Sending Response Status" (*mess/msrs*) Event.  
+Type: Enumeration  
+Optional: Yes
+
+Possible values: "yes" (0x0001) Request Failure Report  
+"no" (0x0002) No Failure Report Request  
+"partial" (0x0003) Request partial failure reporting  
+Default: yes
+
+##### 10.3.1.1.4 Success Report
+
+Parameter Name: Success Report  
+Parameter ID: sr (0x0004)  
+Description: This parameter allows the MGC to indicate the success reporting mode that the MG shall use when sending the message. In order for the MGC to receive the status response from the MG, it shall set the "Message Sending Response Status" (*mess/msrs*) Event.  
+Type: Enumeration  
+Optional: Yes  
+Possible values: "yes" (0x0001) Request Success Status Report  
+"no" (0x0002) No Status Report Request  
+Default: no
+
+## 10.4 Statistics
+
+None.
+
+## 10.5 Error codes
+
+None.
+
+## 10.6 Procedures
+
+In a particular service scenario, the MGC may request the MG to send messages to particular end users. This is similar to the ability to send audio, video and multimedia announcements to users as defined in [ITU-T H.248.9] and [ITU-T H.248.7]. The packages in these Recommendations allow a MGC to use a Signal to point data to be sent to the user in the format described in the Local and Remote Descriptors.
+
+Likewise, this package defines the "Send Message" (*mess/sm*) signal that allows the MGC to request the MG to send a message to a user. Where there are multiple streams on a termination, the MGC should identify the StreamID of the messaging stream where the signal is to be sent. Furthermore, the MGC shall ensure that the messaging stream has been defined (clause 6.2) before requesting that the signal has been sent. If the MGC tries to send the *mess/sm* signal before the messaging stream is established, the MG shall respond with error code 514 "Media Gateway cannot send the specified Announcement".
+
+The MGC must set the "Message Contents by reference" (*mcr*) to identify the contents of the message to be sent.
+
+The MGC must either request or provide a value for the "Message Identity" in order to correlate the signal with a particular message.
+
+The MGC may request Status or Error Reporting through the use of the "Status Report" (*sr*) and "Failure Report" (*fr*) parameters, respectively. If received, the MG shall use these values in any messaging signalling it sends related to the *mess/sm* signal.
+
+On receipt of the *mess/sm* signal, the MG shall send the message using the protocol as described by the Local and Remote descriptors in the applicable messaging stream. The MG is responsible for providing and maintaining any protocol specific data, e.g., transaction-ids and message length information.
+
+If the MGC requires notification of a success or failure report associated with the sent message, then it shall set the "Message Sending Response Status" (*mess/msrs*) event on the applicable stream or termination. The MG shall trigger this event based on the success and failure reporting requested by a particular signal/message identity. If triggered, the MG shall send a Notify command to the MG containing the message identity and status.
+
+# **11 Delete Stored Message Package**
+
+Package Name: Delete Stored Message Package  
+Package ID: delmess (0x00ed)  
+Description: This package allows the MGC to request the MG to delete previously stored messages. The signal is applied to the root termination.  
+Version: 1  
+Extends: None.
+
+## **11.1 Properties**
+
+None.
+
+## **11.2 Events**
+
+None.
+
+## **11.3 Signals**
+
+### **11.3.1 Delete Message**
+
+Signal Name: Delete Message  
+Signal ID: dm (0x0001)  
+Description: This signal allows the MGC to request the MG to delete one or more messages associated with a particular URI.  
+Signal Type: Brief  
+Duration: Not Applicable
+
+#### **11.3.1.1 Additional parameters**
+
+##### **11.3.1.1.1 Storage Location**
+
+Parameter Name: Storage Location  
+Parameter ID: sl (0x0001)  
+Description: This parameter allows the MGC to provide to (or request from) the MG a URI where the messages are to be stored.  
+Type: String  
+Optional: No  
+Possible values: As per [IETF RFC 3986].  
+Default: None.
+
+##### 11.3.1.1.2 Message Identity
+
+Parameter Name: Message Identity  
+Parameter ID: mi (0x0002)  
+Description: This parameter allows the MGC to request that a MG deletes particular messages associated with the URI.  
+Type: Sub-list of String  
+Optional: Yes  
+Possible values: Each string instance of the sub-list is of type "ident" defined by the following ABNF:  
+`ident = ALPHANUM 3*31ident-char`  
+`ident-char = ALPHANUM / "." / "-" / "+" / "%" / "="`  
+See clause 9 of [IETF RFC 4975].  
+NOTE – Whilst the MSRP message identity encoding is used, a message identity other than the MSRP message identity may be used.  
+If no value is provided, all messages associated with the URI are deleted.  
+Default: None.
+
+## 11.4 Statistics
+
+None.
+
+## 11.5 Error codes
+
+None.
+
+## 11.6 Procedures
+
+The MGC may request the MG to delete a message associated with a particular URI or the entire URI through the use of the "Delete Message" (*delmess/dm*) signal on the root termination. The usage of the signal on the root termination allows the deletion of messages outside of a MSRP session. The MGC must provide the URI of the messages to be deleted.
+
+# 12 Messaging Session Information Package
+
+Package Name: Message Session Information Package  
+Package ID: msi (0x00ee)  
+Description: This package allows the MGC to indicate additional attributes to describe the messaging session to those defined in [IETF RFC 4975]. The MG shall ensure that messages sent/received also comply with these attributes.  
+Version: 1  
+Extends: None.
+
+## 12.1 Properties
+
+### 12.1.1 Subject
+
+Property Name: Message Subject  
+Property ID: sb (0x0001)  
+Description: This property contains a description of the topic of the message.
+
+Type: Sub-list of String  
+Possible values: Each instance of String of type "Subject-header". Syntax according to the following ABNF:  
+**Subject-header = [ ";" Lang-param ] SP \*HEADERCHAR**  
+See clause 4.5 of [IETF RFC 3862] for more information.  
+Default: None.  
+Defined in: LocalControl  
+Characteristics: Read/Write
+
+### 12.1.2 Message Class
+
+Property Name: Message Class  
+Property ID: class (0x0002)  
+Description: This property indicates the messages class, e.g., Advertisement/private  
+Type: Sub-list of String  
+Possible values: Any string. A profile may define possible values.  
+Default: None.  
+Defined in: LocalControl  
+Characteristics: Read/Write
+
+### 12.1.3 Message Priority
+
+Property Name: Message Priority  
+Property ID: pri (0x0003)  
+Description: This property indicates the messages priority.  
+Type: String  
+Possible values: "normal", "non-urgent", "urgent"  
+See clause 2.1.54 of [IETF RFC 4021].  
+Default: None.  
+Defined in: LocalControl  
+Characteristics: Read/Write
+
+## 12.2 Events
+
+None.
+
+## 12.3 Signals
+
+None.
+
+## 12.4 Statistics
+
+None.
+
+## 12.5 Error codes
+
+None.
+
+## 12.6 Procedures
+
+This package allows a MGC to provide further information to the MG on the characteristics of a particular messaging stream. If the MGC sets the properties in this package on a particular messaging stream, then the MG shall ensure that MSRP messages sent and received by the termination/stream comply with these characteristics. If MSRP messages/signalling does not comply with the properties, then the messaging server shall generate an appropriate error code.
+
+# 13 Messaging Filtering Package
+
+Package Name: Message Filtering Package
+
+Package ID: mf (0x00ef)
+
+Description: This package allows the MGC to indicate to the MG message filtering rules and the behaviour to apply to the messages based on matching the filtering rule. The filter rules and behaviour are based on "Sieve" as defined by [IETF RFC 5228], which allows complex filtering rules for e-mail to be specified. As e-mail and messaging have similar headers, this language is applied in ITU-T H.248.
+
+Version: 1
+
+Extends: None.
+
+## 13.1 Properties
+
+### 13.1.1 Incoming Message Filters
+
+Property Name: Incoming Message Filters
+
+Property ID: imf (0x0001)
+
+Description: This property contains a Sieve script that is applied to incoming messages from a user's perspective, i.e messages received by a termination from other terminations in the context.
+
+Type: String
+
+Possible values: As per the Sieve Grammar (clause 8.2 of [IETF RFC 5228]). See clause 13.6 for more information.
+
+Default: All messages are implicitly kept.
+
+Defined in: LocalControl
+
+Characteristics: Read/Write
+
+### 13.1.2 Incoming Message Filters by Reference
+
+Property Name: Incoming Message Filters by Reference
+
+Property ID: imfr (0x0002)
+
+Description: This property allows the MGC to indicate which Sieve script should be used for incoming message filtering by referring to a URI pointing to a Sieve script file (e.g., a file with .siv or .sieve file extension).
+
+Type: String
+
+Possible values: The string is of type "SIEVE-URI".
+
+See: <http://www.iana.org/assignments/uri-schemes.html>
+
+Default: All messages are implicitly kept.
+
+Defined in: LocalControl
+
+Characteristics: Read/Write
+
+### 13.1.3 Outgoing Message Filters
+
+Property Name: Outgoing Message Filters
+
+Property ID: omf (0x0003)
+
+Description: This property contains a Sieve script that is applied to outgoing messages from a user's perspective, i.e., messages received by a termination from the user.
+
+Type: String
+
+Possible values: As per the Sieve Grammar (clause 8.2 of [IETF RFC 5228]). See clause 13.6 for more information.
+
+Default: All messages are implicitly kept.
+
+Defined in: LocalControl
+
+Characteristics: Read/Write
+
+### 13.1.4 Outgoing Message Filters by Reference
+
+Property Name: Outgoing Message Filters by Reference
+
+Property ID: omfr (0x0004)
+
+Description: This property allows the MGC to indicate which Sieve script should be used for outgoing message filtering by referring to a URI pointing to a Sieve script file (e.g., a file with .siv or .sieve file extension).
+
+Type: String
+
+Possible values: The string is of type "SIEVE-URI". See:  
+<http://www.iana.org/assignments/uri-schemes.html>
+
+Default: All messages are implicitly kept.
+
+Defined in: LocalControl
+
+Characteristics: Read/Write
+
+## 13.2 Events
+
+### 13.2.1 Filed Message
+
+Event Name: Filed Message
+
+Event ID: fm (0x0001)
+
+Description: This event enables the MGC to be notified when the MG has filed a message as a result of filtering. This allows the MGC to determine if the user needs to be notified of this event.
+
+#### 13.2.1.1 EventsDescriptor parameters
+
+None.
+
+#### 13.2.1.2 ObservedEventsDescriptor parameters
+
+##### 13.2.1.2.1 Storage Location
+
+Parameter Name: Storage Location
+
+Parameter ID: sl (0x0001)
+
+Description: This parameter allows the MG to indicate to the MGC where the messages are stored.  
+Type: String  
+Optional: No  
+Possible values: As per [IETF RFC 3986].  
+Default: None.
+
+##### 13.2.1.2.2 Message Identity
+
+Parameter Name: Message Identity  
+Parameter ID: mi (0x0002)  
+Description: This parameter allows the MGC to request that a MG stores particular messages associated with the URI.  
+Type: Sub-list of String  
+Optional: No  
+Possible values: Each string instance of the sub-list is of type "ident" defined by the following ABNF:  
+`ident = ALPHANUM 3*31ident-char`  
+`ident-char = ALPHANUM / "." / "-" / "+" / "%" / "="`  
+See clause 9 of [IETF RFC 4975].  
+NOTE – Whilst the MSRP message identity encoding is used, a message identity other than the MSRP message identity may be used.  
+If no value is provided, all messages are stored.  
+Default: None.
+
+### 13.2.2 Filtering Runtime Error Event
+
+Event Name: Filtering Runtime Error  
+Event ID: fre (0x0002)  
+Description: This event allows the MG to send a notification to the MGC indicating that an error has occurred during the execution of a filtering script against a particular message.
+
+#### 13.2.2.1 EventsDescriptor parameters
+
+None.
+
+#### 13.2.2.2 ObservedEventsDescriptor parameters
+
+##### 13.2.2.2.1 Message Identity
+
+Parameter Name: Message Identity  
+Parameter ID: mi (0x0001)  
+Description: This parameter indicates the MSRP message identity of the message the filtering script that generated an error was applied to.  
+Type: String  
+Optional: Yes
+
+Possible values: The string is of type "ident" defined by the following ABNF:
+
+`ident = ALPHANUM 3*31ident-char`
+
+`ident-char = ALPHANUM / "." / "-" / "+" / "%" / "="`
+
+See clause 9 of [IETF RFC 4975].
+
+NOTE – Whilst the MSRP message identity encoding is used, a message identity other than the MSRP message identity may be used.
+
+Default: None.
+
+##### **13.2.2.2.2 Error Cause**
+
+Parameter Name: Error Cause
+
+Parameter ID: cause (0x0002)
+
+Description: This parameter provides information on the cause of the error.
+
+Type: Integer
+
+Optional: No
+
+Possible values:
+
+|   |                                          |
+|---|------------------------------------------|
+| 0 | Unknown Cause                            |
+| 1 | Invalid Combination of Actions           |
+| 2 | Unable to file message (disk full)       |
+| 3 | Unable to file message (invalid mailbox) |
+| 4 | Unable to redirect message               |
+| 5 | Loop detected in script                  |
+
+Default: 0
+
+## **13.3 Signals**
+
+None.
+
+## **13.4 Statistics**
+
+None.
+
+## **13.5 Error codes**
+
+### **13.5.1 Sieve Script Syntax Error**
+
+Error Code #: 700
+
+Name: Sieve Script Syntax Error
+
+Definition: The MG has detected a syntax error in the provided Sieve script. Therefore, the provided script is ignored.
+
+Error Text in the
+
+Error Descriptor: None.
+
+Comment: None.
+
+### **13.5.2 Unsupported Sieve Require Error**
+
+Error Code #: 701
+
+Name: Unsupported Sieve Require Error
+
+Definition: The MG does not support a particular "require" in the requested Sieve script. The provided script is ignored.
+
+Error Text in the
+
+Error Descriptor: A copy of the line containing the unsupported "require" may be included.
+
+Comment: None.
+
+### 13.5.3 Sieve Actions Exceeded Error
+
+Error Code #: 702
+
+Name: Sieve Actions Exceeded Error
+
+Definition: The MG does not support the number of Sieve actions required in the requested Sieve script. The provided script is ignored.
+
+Error Text in the
+
+Error Descriptor: An integer value of the maximum number of Sieve actions.
+
+Comment: None.
+
+## 13.6 Procedures
+
+### 13.6.1 Filtering script compatibility with Sieve
+
+The encoding, processing and actions of H.248 filtering scripts follows Sieve [IETF RFC 5228], with the following exceptions:
+
+- 1) The use of double quote (") character is not permitted within a H.248 Property String. However, double quotes are used in the Sieve language and may be contained in Sieve strings. Therefore, where quoted string is used within a Sieve script, it shall be represented using %x22.
+
+For example, the Sieve test 'header :contains ["To"]' would be encoded in a H.248 property as "header :contains [%x22To%x22]"
+
+NOTE – When a double quote is used within a Sieve String, a backslash "\" precedes the %x22 encoding.
+
+- 2) Sieve (clause 2.4.2.2 of [IETF RFC 5228]) allows the specification of header fields according to clause 3.6 of [IETF RFC 2822]. The use of this package allows the specification of header fields according to the MSRP [IETF RFC 4975] and CPIM [IETF RFC 3860].
+- 3) A subset of header fields may be specified in an applicable H.248 profile.
+- 4) A single Sieve script shall apply to either the incoming or outgoing messages. Separate scripts are used for the incoming or outgoing message direction. See clause 2.4.2.3 of [IETF RFC 5228] for related information.
+- 5) Sieve scripts allow different types of action commands (clause 2.9 of [IETF RFC 5228]). Implementation shall support the "Keep" action; however, the support of the "Discard", "Redirect" and "Fileinto" actions is optional.
+- 6) The "Fileinto" action is used to store a message. The <mailbox: string> format (see clause 4.1 of [IETF RFC 5228]) shall comply with the URI format.
+- 7) The "Keep" action results in the message being sent to the user, it does not imply local storage on the MG.
+
+### 13.6.2 Encoding of Sieve scripts
+
+Sieve scripts are encoded using the "Quoted String Form".
+
+### 13.6.3 H.248 usage of filtering scripts
+
+Based on a user profile or MGC policy, the MGC may set a message level filtering script at an individual termination/stream level. The result of such a script may cause the following actions:
+
+- A message is delivered to the user represented by the termination (i.e., action Keep).
+- A message is discarded (i.e., action Discard).
+- A message is redirected to another address (i.e., action Redirect).
+- A message is stored (i.e., action Fileinto).
+
+NOTE – Due to the complexity of the interaction between messaging scripts at an individual termination and root termination level, the use of message filters at the MG wide level (i.e., on the root termination) is for further study.
+
+For filtering incoming messages, the MGC shall use either the "Incoming Message Filters" (*mf/imf*) property or the "Incoming Message Filters by Reference" (*mf/imfr*) property containing a filtering script. If the MGC sets both these properties, the MG shall respond with error 473 "Conflicting Property Values". The filtering script shall comply with clause 13.6.1.
+
+For filtering outgoing messages, the MGC shall use either the "Outgoing Message Filters" (*mf/omf*) property or the "Outgoing Message Filters by Reference" (*mf/omfr*) property containing a filtering script. If the MGC sets both these properties, the MG shall respond with error 473 "Conflicting Property Values". The filtering script shall comply with clause 13.6.1.
+
+On reception of the script, the MG should parse the script to determine if there are any errors. If an error is detected, one of the errors in clause 13.5 shall be returned.
+
+Once the filtering script is accepted it shall be applied to each message received on the applicable termination/stream.
+
+If the MGC requires information regarding the storage (filing) of messages, it shall set the "Filed Message" (*mf/fm*) event. This allows the MGC to determine the message identity of the stored message along with the storage location. The MGC may then use this information to provide further services to a user.
+
+The MGC should also set the "Filter Runtime Error" (*mf/fre*) event on the applicable stream in order to determine if there are any errors when running the filter against an incoming message.
+
+### 13.6.4 H.248 filtering script example
+
+The script below shows an example filter that checks the sender of the message and provides different actions based on the sender. The example shows a filter that saves messages from *friend@friendlydomain.com* to a MSRP URI and forwards all work-related messages to the user.
+
+```
+mf/fre{"require [%x22fileinto%x22];  
+    if header is %x22Sender%x22 %x22friend@friendlydomain.com%x22  
+    {  
+        fileinto %x22msrp://mydomain.com:8493/sessid123;tcp%x22  
+    }  
+    elseif address :DOMAIN :is [%x22From%x22, %x22To%x22]  
+        %x22mycompany.com%x22  
+        {  
+            keep;  
+        }
+```
+
+# **14 Stored Message Information Package**
+
+Package Name: Stored Message Information Package  
+Package ID: sminf (0x00f0)  
+Description: This package allows the MGC to request information regarding stored messages.  
+Version: 1  
+Extends: None.
+
+## **14.1 Properties**
+
+None.
+
+## **14.2 Events**
+
+None.
+
+## **14.3 Signals**
+
+### **14.3.1 Message Information**
+
+Signal Name: Message Information  
+Signal ID: mi (0x0001)  
+Description: This signal allows the MGC to request information on a previously stored message on the MG.  
+Signal Type: Brief  
+Duration: Not Applicable
+
+#### **14.3.1.1 Additional parameters**
+
+##### **14.3.1.1.1 Storage Location**
+
+Parameter Name: Storage Location  
+Parameter ID: sl (0x0001)  
+Description: This parameter allows the MGC to provide to the MG the URI of the stored message.  
+Type: String  
+Optional: No  
+Possible values: As per [IETF RFC 3986].  
+Default: None.
+
+##### **14.3.1.1.2 Message Identity**
+
+Parameter Name: Message Identity  
+Parameter ID: mi (0x0002)  
+Description: This parameter allows the MGC to request information regarding a sub-set of messages when multiple messages are stored in a URI.  
+Type: Sub-list of String  
+Optional: No
+
+Possible values: Each string instance of the sub-list is of type "ident" defined by the following ABNF:
+
+`ident = ALPHANUM 3*31ident-char`
+
+`ident-char = ALPHANUM / "." / "-" / "+" / "%" / "="`
+
+NOTE – Whilst the MSRP message identity encoding is used, a message identity other than the MSRP message identity may be used.
+
+See clause 9 of [IETF RFC 4975].
+
+Default: None.
+
+##### 14.3.1.1.3 "From" Information
+
+Parameter Name: "From" Information
+
+Parameter ID: fr (0x0003)
+
+Description: This parameter indicates the sender or originator of a message.
+
+Type: String
+
+Optional: Yes
+
+Possible values: String of type "From-header". Syntax according to the following ABNF:
+
+`From = [ Formal-name ] "<" URI ">"`
+
+See clause 4.1 of [IETF RFC 3862] for more information.
+
+Default: None.
+
+##### 14.3.1.1.4 "To" Information
+
+Parameter Name: "To" Information
+
+Parameter ID: to (0x0004)
+
+Description: This parameter specifies an intended recipient of a message.
+
+Type: Sub-list of String
+
+Optional: Yes
+
+Possible values: Each instance of String of type "To-header". Syntax according to the following ABNF:
+
+`To-header = [ Formal-name ] "<" URI ">"`
+
+See clause 4.2 of [IETF RFC 3862] for more information.
+
+Default: None.
+
+##### 14.3.1.1.5 "CC" Information
+
+Parameter Name: "CC" Information
+
+Parameter ID: cc (0x0005)
+
+Description: This parameter specifies a non-primary recipient for a message.
+
+Type: Sub-list of String
+
+Optional: Yes
+
+Possible values: Each instance of String of type "Cc-header". Syntax according to the following ABNF:  
+`Cc-header = [ Formal-name ] "<" URI ">"`  
+See clause 4.3 of [IETF RFC 3862] for more information.  
+Default: None.
+
+##### 14.3.1.1.6 "DateTime" Information
+
+Parameter Name: "DateTime" Information  
+Parameter ID: dt (0x0006)  
+Description: This parameter specifies the date and time a message was sent.  
+Type: String  
+Optional: Yes  
+Possible values: String of type "DateTime-header". Syntax according to the following ABNF:  
+`DateTime-header = date-time`  
+The syntax of 'date-time' is defined in [IETF RFC 3339].  
+See clause 4.4 of [IETF RFC 3862] for more information.  
+Default: None.
+
+##### 14.3.1.1.7 "Subject" Information
+
+Parameter Name: "Subject" Information  
+Parameter ID: sb (0x0007)  
+Description: This parameter contains a description of the topic of the message.  
+Type: Sub-list of String  
+Optional: Yes  
+Possible values: Each instance of String of type "Subject-header". Syntax according to the following ABNF:  
+`Subject-header = [ ";" Lang-param ] SP *HEADERCHAR`  
+See clause 4.5 of [IETF RFC 3862] for more information.  
+Default: None.
+
+##### 14.3.1.1.8 "Size" Information
+
+Parameter Name: "Size" Information  
+Parameter ID: sz (0x0008)  
+Description: This parameter contains the total size of the message in bytes.  
+Type: String  
+Optional: Yes  
+Possible values: Each instance of String of type "total". Syntax according to the following ABNF:  
+`total = 1*DIGIT`  
+For more information, see the "byte-range" header in [IETF RFC 4975].  
+Default: None.
+
+## 14.4 Statistics
+
+None.
+
+## 14.5 Error codes
+
+None.
+
+## 14.6 Procedures
+
+A MGC may require further information regarding the messages stored by a MG. The MGC may learn of the location and the identity of the stored messages through the Filed Message (*mf/fm*) event.
+
+However, the MGC may determine further information regarding a storage location via the "Message Information" (*sminf/mi*) signal.
+
+Multiple messages may be stored in a particular URI. In order for the MGC to determine the identity of messages stored in a particular URI, it may wildcard "CHOOSE" the Message Identity (*mi*) parameter. The MGC shall not use the "from", "to", "cc", "datetime", "subject" and "size" parameters in a signal containing a wildcarded "CHOOSE" Message Identity. The MG shall then return a list of all the message identities in the URI.
+
+By providing the storage location and message identity in the *sminf/mi* signal and wildcarding CHOOSE the "from", "to", "cc", "datetime", "subject" and "size" parameters as appropriate, the MG will return detailed information regarding the referred-to message.
+
+# 15 Record Message Package
+
+Package Name: Record Message Package
+
+Package ID: recmess (0x00f1)
+
+Description: This package allows the MGC to request the MG to store messages sent and/or received at a particular termination/stream.
+
+Version: 1
+
+Extends: None.
+
+## 15.1 Properties
+
+None.
+
+## 15.2 Events
+
+### 15.2.1 Record Operation Failure
+
+Event Name: Record Operation Failure
+
+Event ID: messfail (0x0001)
+
+Description: This event allows the MG to send a notification to the MGC indicating that a failure has occurred when recording a message.
+
+#### 15.2.1.1 EventsDescriptor parameters
+
+None.
+
+#### 15.2.1.2 ObservedEventsDescriptor parameters
+
+##### 15.2.1.2.1 Return Code
+
+Parameter Name: Return Code
+
+Parameter ID: rc (0x0001)  
+Description: This parameter allows the MG to indicate to the MGC why the record operation failed.  
+Type: Integer  
+Optional: No  
+Possible values: 623 Out of Storage  
+Default: None.
+
+## 15.3 Signals
+
+### 15.3.1 Record Message
+
+Signal Name: Record Message  
+Signal ID: rm (0x0001)  
+Description: This signal allows the MGC to request the MG to store the message sent and/or received at a particular termination/stream.  
+Signal Type: On/Off  
+Duration: Not Applicable
+
+#### 15.3.1.1 Additional parameters
+
+##### 15.3.1.1.1 Storage Location
+
+Parameter Name: Storage Location  
+Parameter ID: sl (0x0001)  
+Description: This parameter allows the MGC to provide to (or request from) the MG a URI where the messages are to be stored.  
+Type: String  
+Optional: No  
+Possible values: As per [IETF RFC 3986].  
+Default: None.
+
+##### 15.3.1.1.2 Append
+
+Parameter Name: Append  
+Parameter ID: app (0x0002)  
+Description: This parameter allows the MGC to indicate to (or request from) the MG whether the messages will be appended to data already existing at a URI or whether the messages will overwrite the data at a URI.  
+Type: Enumeration  
+Optional: Yes  
+Possible values: "ovr" (0x0001) Overwrite  
+"app" (0x0002) Append  
+Default: ovr
+
+##### 15.3.1.1.3 Direction
+
+Parameter Name: Direction
+
+Parameter ID: dir (0x0003)
+
+Description: This parameter indicates which messages should be stored by the MG. "External" indicates those messages received on the termination/stream external to the MG. "Internal" indicates those messages received on the termination/stream from other terminations in the context. "Both" indicates messages from both directions.
+
+Type: Enumeration
+
+Optional: Yes
+
+Possible values: "EXT" (0x0001) External  
+"INT" (0x0002) Internal  
+"BOTH" (0x0003) Both
+
+Default: EXT
+
+##### 15.3.1.1.4 Maximum Record Size
+
+Parameter Name: Maximum Record Size
+
+Parameter ID: mrs (0x0004)
+
+Description: This parameter indicates the maximum storage size associated with the recording request.
+
+Type: Integer
+
+Optional: Yes
+
+Possible values: 0 – upwards (in octets). Zero (0) indicates no maximum size.
+
+Default: 0
+
+## 15.4 Statistics
+
+None.
+
+## 15.5 Error codes
+
+None.
+
+## 15.6 Procedures
+
+The MGC shall ensure that a messaging stream is established on the MG before requesting message storage. If the MGC requires that the MG store the messages on a particular messaging stream, it shall send the "Record Message" (*recmess/rm*) signal to the MG. It shall either provide to or request from the MG the URI of the stored messages. The MGC is responsible for maintaining the list of stored URI per user/subscriber and also the permissions of who may access the stored messages. The MGC may also request that the MG store the messages sent by a user or received by the user through the use of the "Direction" (*dir*) parameter. The MGC may also set the "Maximum Record Size" (*mrs*) parameter. This parameter indicates the size of the storage for recording messages. Messages are recorded until the maximum recording size is reached. If this size limit results in a partial message being stored, then this partial message is discarded and further recording is stopped.
+
+NOTE 1 – If the message recording is done in conjunction with message sending, the complete message is still sent.
+
+The MGC may set time-based recording by either applying the record message signal as an on/off or timeout signal. If the MGC requires notification of recording failure, it should set the "Record Operation Failure" event.
+
+NOTE 2 – There should be at most one outstanding record operation per messaging stream. In order to correlate the "Record Operation Failure" (*messfail*) event with the correct messaging stream, the MG shall return the StreamID with the ObservedEvent.
+
+The MG shall record the messages received by the termination/stream whilst the signal is set to "on". Messages are recorded prior to any message filtering taking place and once stored will be subject to any applicable message filtering (see the Message Filtering Package in clause 13). When the signal is removed, the MG shall stop recording. If the MGC wishes to subsequently record messages again and wishes to use the same URI, it may indicate whether the messages are appended to the data in the URI or whether the messages overwrite the data in the URI through the use of the "Append" (*app*) parameter. If maximum record size is specified in conjunction with the *app* parameter, then the storage size includes any messages already stored at the storage location. If the *messfail* event had been set, and the MG detects that a storage location size associated with a message recording has been exceeded, then it shall notify the MGC.
+
+
+
+
+
+# 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.72-200912-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.248.72-200912-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a8073c3055abc7731de1ae66c36e362f11443a0c
--- /dev/null
+++ b/marked/H/T-REC-H.248.72-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.72-200912-I_PDF-E/raw.md b/marked/H/T-REC-H.248.72-200912-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..de89fcaf32f944daa966bf391f3aed82a02b4f64
--- /dev/null
+++ b/marked/H/T-REC-H.248.72-200912-I_PDF-E/raw.md
@@ -0,0 +1,635 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.72**
+
+(12/2009)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+---
+
+**Gateway control protocol: ITU-T H.248 support  
+for media-oriented negotiation acceleration  
+(MONA)**
+
+Recommendation ITU-T H.248.72
+
+![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 the acronym "ITU" in a larger, bold blue font above it.
+
+ITU logo
+
+# **ITU-T H-SERIES RECOMMENDATIONS AUDIOVISUAL AND MULTIMEDIA SYSTEMS**
+
+|                                                                               |                    |
+|-------------------------------------------------------------------------------|--------------------|
+| <b>CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS</b>                            | <b>H.100–H.199</b> |
+| <b>INFRASTRUCTURE OF AUDIOVISUAL SERVICES</b>                                 |                    |
+| 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        |
+| <b>MOBILITY AND COLLABORATION PROCEDURES</b>                                  |                    |
+| 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        |
+| <b>BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES</b>                |                    |
+| Broadband multimedia services over VDSL                                       | H.610–H.619        |
+| Advanced multimedia services and applications                                 | H.620–H.629        |
+| <b>IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV</b>                     |                    |
+| 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.72
+
+## Gateway control protocol: ITU-T H.248 support for media-oriented negotiation acceleration (MONA)
+
+## Summary
+
+Recommendation ITU-T H.248.72 defines two ITU-T H.248 packages that are intended for media gateways and media gateway controllers designed to support the media-oriented negotiation acceleration (MONA) negotiation procedures from Recommendation ITU-T H.324. More specifically, this Recommendation contains:
+
+- The "MONA Preference" package that supports the sending and reception of MONA preference messages as well as the handling of the completion conditions; the detection of legacy conditions allowing for a swift fallback to Recommendation ITU-T H.245 interworking and the sending and reception of media in preconfigured channels, the so-called media preconfigured channel (MPC).
+- The "H.245 Transport for SPC Use" package, that supports the sending and reception of ITU-T H.245 messages using the signalling preconfigured channel (SPC) during a MONA negotiation procedure.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group |
+|---------|----------------|------------|-------------|
+| 1.0     | ITU-T H.248.72 | 2009-12-14 | 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                          | 2    |
+| 3 Definitions .....                        | 2    |
+| 4 Abbreviations and acronyms .....         | 2    |
+| 5 Conventions .....                        | 3    |
+| 6 H.245 Transport for SPC Use package..... | 3    |
+| 6.1 Properties.....                        | 3    |
+| 6.2 Events .....                           | 3    |
+| 6.3 Signals .....                          | 4    |
+| 6.4 Statistics.....                        | 4    |
+| 6.5 Error codes.....                       | 4    |
+| 6.6 Procedures .....                       | 5    |
+| 7 MONA preference package .....            | 5    |
+| 7.1 Properties.....                        | 6    |
+| 7.2 Events .....                           | 7    |
+| 7.3 Signals .....                          | 9    |
+| 7.4 Statistics.....                        | 10   |
+| 7.5 Error codes.....                       | 10   |
+| 7.6 Procedures .....                       | 10   |
+
+
+
+## Gateway control protocol: ITU-T H.248 support for media-oriented negotiation acceleration (MONA)
+
+# 1 Scope
+
+This Recommendation defines ITU-T H.248 packages that allow a decomposed gateway to realize the media-oriented negotiation acceleration (MONA) negotiation procedures specified in Annex K of [ITU-T H.324].
+
+During the MONA negotiation, terminals exchange their capabilities depending on which of the methods for establishing media channels are supported:
+
+- signalling preconfigured channel (SPC);
+- media preconfigured channel (MPC);
+- accelerated ITU-T H.245 procedure (ACP).
+
+The ACP method is supported in all terminals. The exchange of the MONA preference messages allows the determination of which of the three methods is used.
+
+The "MONA Preference" package supports the sending and reception of MONA preference messages. It provides the following capabilities:
+
+- Sending and reception of MONA preference messages including automatic retransmission.
+- Sending and reception of media in preconfigured channels during the MONA negotiation procedures.
+- Detection of legacy condition: this capability allows for a swift fallback to [ITU-T H.245] interworking.
+- Completion of the MONA negotiation procedures.
+
+The "MONA Preference" package is thus mandatory for any decomposed gateway that supports the ITU-T H.324, Annex K MONA procedures.
+
+The "MONA Preference" package also includes the needed ITU-T H.248 capabilities for the use of the MPC method to establish media channels. These MPC related capabilities within the package only need to be supported by decomposed gateways supporting MPCs.
+
+The "H.245 Transport for SPC Use" package allows the sending and reception of ITU-T H.245 messages using the SPC method during a MONA negotiation procedure. It also allows for the automatic retransmission of the messages to the remote end. This package is defined as an extension of the "H.245 Transport" package.
+
+Decomposed gateways that support the SPC method for establishing media channels need to support the "H.245 Transport for SPC Use" package in addition to the "MONA Preference" package.
+
+The ACP method is used when the terminals do not support another common method, SPC or MPC, or in order to establish missing channels when not all media channels have been already established with MPC. The ACP procedures are realized by exchanging ITU-T H.245 messages. The required ITU-T H.248 capabilities are provided by the [ITU-T H.248.12 Amd.2] H.245 transport 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.223] Recommendation ITU-T H.223 (2001), *Multiplexing protocol for low bit rate multimedia communication.*
+- [ITU-T H.245] Recommendation ITU-T H.245 (2008), *Control protocol for multimedia communication.*
+- [ITU-T H.248.12 Amd.2] Recommendation ITU-T H.248.12 (2007), *Gateway control protocol: H.248.1 packages for H.323 and H.324 interworking, Amendment 2 (2007), Transport mechanism.*
+- [ITU-T H.324] Recommendation ITU-T H.324 (2009), *Terminal for low bit-rate multimedia communication.*
+
+# 3 Definitions
+
+None.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|        |                                         |
+|--------|-----------------------------------------|
+| ACP    | Accelerated ITU-T H.245 procedures      |
+| AMR-WB | Adaptive Multi Rate Wide Band           |
+| ICM    | Inferred Common Mode                    |
+| MG     | Media Gateway                           |
+| MGC    | Media Gateway Controller                |
+| MONA   | Media-Oriented Negotiation Acceleration |
+| MOS    | Media-Oriented Set-up                   |
+| MPC    | Media Preconfigured Channel             |
+| MSD    | Master Slave Determination              |
+| MUX    | Multiplexer                             |
+| OID    | Object Identifier                       |
+| PDU    | Protocol Data Unit                      |
+| RTD    | Round Trip Delay                        |
+| RX     | Receive                                 |
+| SPC    | Signalling Preconfigured Channel        |
+| TCS    | Terminal Capability Set                 |
+| TX     | Transmit                                |
+
+# 5 Conventions
+
+None.
+
+# 6 H.245 Transport for SPC Use package
+
+Package name: H.245 Transport for SPC Use  
+Package ID: h245tpspc (0x00f7)  
+Description: This package extends the [ITU-T H.248.12 Amd.2] H.245 transport package "h245tp" and defines a mechanism for the transport of ITU-T H.245 messages when SPC is used.  
+Version: 1  
+Extends: h245tp (0x00b4) version 1
+
+## 6.1 Properties
+
+None.
+
+## 6.2 Events
+
+This package does not define any new event. It defines an event parameter and an observed event parameter that can be used in the *h245tpspc/h245msgin* event defined in the base package.
+
+### 6.2.1 EventsDescriptor parameters
+
+#### 6.2.1.1 Signalling preconfigured channel
+
+Parameter name: SPC  
+Parameter ID: spc (0x0001)  
+Description: This parameter indicates whether the incoming ITU-T H.245 message is expected to be received in the signalling preconfigured channel (SPC) or as a legacy ITU-T H.245 message. If the incoming ITU-T H.245 message is received differently to what this parameter specifies, the event does not occur, i.e., the ITU-T H.245 message is not reported.
+
+After the MG has detected a *monapref/legdet* event, the MG does not need to continue detecting incoming ITU-T H.245 messages in the SPC and shall not report them to the MGC, even if *h245tpspc/h245msgin* is not removed from the EventsDescriptor.
+
+Type: Enumeration  
+Optional: Yes  
+Possible values: "H245" (0x0001): Message should be received as a legacy ITU-T H.245.  
+"SPC" (0x0002): Message should be received in the SPC.  
+"Both" (0x0003): Message may be received either way.  
+Default: "H245"
+
+### 6.2.2 ObservedEventsDescriptor parameters
+
+#### 6.2.2.1 Signalling preconfigured channel
+
+Parameter name: SPC  
+Parameter ID: spc (0x0002)
+
+Description: This parameter indicates that the incoming ITU-T H.245 message has been received in the SPC.  
+Type: Boolean  
+Optional: Yes  
+Possible values: ON: ITU-T H.245 message was received in the SPC.  
+OFF: ITU-T H.245 message was received as a legacy message.  
+Default: OFF
+
+## 6.3 Signals
+
+This package does not define any new signal. It defines a signal parameter that can be used in the *h245tpspc/h245msgout* signal defined in the base package.
+
+### 6.3.1 Additional parameters
+
+#### 6.3.1.1 Signalling preconfigured channel
+
+Parameter name: SPC  
+Parameter ID: spc (0x0002)  
+Description: This parameter indicates whether the MG shall send the ITU-T H.245 message in the SPC or as a legacy.  
+Thus no message is sent if there is no MONA preference message sending ongoing, ordered with signals *monapref/monaprefmsgout*.  
+Type: Boolean  
+Optional: Yes  
+Possible values: ON: ITU-T H.245 message shall be sent in the SPC.  
+OFF: ITU-T H.245 message shall be sent as a legacy.  
+Default: OFF
+
+#### 6.3.1.2 Repetition
+
+Parameter name: Repetition  
+Parameter ID: rep (0x0003)  
+Description: Indicates that the MG shall indefinitely repeat the sending of the ITU-T H.245 message in the SPC. This parameter is only relevant when the *spc* signal parameter equals ON.  
+Type: Boolean  
+Optional: Yes  
+Possible values: ON: ITU-T H.245 message shall be repeated until the signal is removed  
+OFF: ITU-T H.245 message shall only be sent once  
+Default: ON
+
+## 6.4 Statistics
+
+None.
+
+## 6.5 Error codes
+
+None.
+
+## 6.6 Procedures
+
+If the MGC wants to be notified about ITU-T H.245 messages received in the signalling preconfigured channel (SPC), it shall include the *spc* parameter set to "SPC" in the *h245tpspc/h245msgin* event. In that case, the MG will only report the event if the ITU-T H.245 message is received in the SPC. If the MGC wants to be notified about ITU-T H.245 messages either received in the SPC or as a legacy, it shall include the *spc* parameter set to "BOTH" in the *h245tpspc/h245msgin* event.
+
+If the MGC does not include the *spc* parameter in the *h245tpspc/h245msgin* event or if the MGC sets it to "H245", the MG will only report reception of legacy ITU-T H.245 messages.
+
+If the MGC includes the *spc* parameter set to "BOTH" in the *h245tpspc/h245msgin* event and the ITU-T H.245 message is received in the SPC, the MG will include the *spc* parameter set to "SPC" in the observed event. In any other case, it is optional for the MG to include the parameter as there is no ambiguity.
+
+When the MG is requested to detect incoming ITU-T H.245 messages in the SPC, i.e., *spc* parameter set to "SPC" or to "BOTH", the MG shall do so as long as the event remains active or until a *monapref/legdet* event is detected.
+
+This package can be used by MGC and MGs implementing the SPC procedures specified in [ITU-T H.324].
+
+An MGC that wants to send an ITU-T H.245 message in the SPC channel shall send the *h245tpspc/h245msgout* signal to the MG with the '*spc*' parameter set to 'ON'. In this case, the ITU-T H.245 message can only be sent by the MG if there is an ongoing MONA preference message sending. Sending of MONA preference messages must be ordered prior to or in combination with the ordering of SPC with signal *monapref/monaprefmsgout*. The MGC may additionally request the MG to retransmit the message by including the parameter '*rep*' set to 'ON'. This retransmission is used for example for a MOS request message, as specified in [ITU-T H.324]. The '*rep*' parameter is only relevant when the '*spc*' parameter is set to 'SPC'. No automatic retransmission can be ordered for normal ITU-T H.245 communication.
+
+If the MGC orders the retransmission of the message in the SPC signalling channel, it is the responsibility of the MGC to stop the retransmission by sending a new signal descriptor.
+
+# 7 MONA preference package
+
+Package name: MONA Preference
+
+Package ID: monapref (0x00f8)
+
+Description: This package is used for transporting MONA preferences. The package defines a signal for sending MONA preference messages from a MGC to MG and an event for sending MONA preferences messages from the MG to MGC which are needed when the interworking function is handled by the MGC. Additionally the package defines events for indicating the completion of MONA preference negotiation, legacy interworking and media preconfigured channel.
+
+Version: 1
+
+Extends: None
+
+## 7.1 Properties
+
+### 7.1.1 MONA class
+
+|                  |                                                                                                                                                                  |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Property name:   | MONA Class                                                                                                                                                       |
+| Property ID:     | class (0x0001)                                                                                                                                                   |
+| Description:     | This property indicates which of the MONA negotiation methods are supported by the MG. It is applicable to the Root Termination only.                            |
+| Type:            | Enumeration                                                                                                                                                      |
+| Possible values: | "1" (0x0001): MG supports SPC, MPC and ACP procedures.<br>"2" (0x0002): MG supports MPC and ACP procedures.<br>"3" (0x0003): MG supports SPC and ACP procedures. |
+| Default:         | None                                                                                                                                                             |
+| Defined in:      | TerminationState                                                                                                                                                 |
+| Characteristics: | ReadOnly                                                                                                                                                         |
+
+### 7.1.2 Supported preconfigured channels receive
+
+|                  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Property name:   | Supported Media Preconfigured Channels Receive                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| Property ID:     | mpcrx (0x0002)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| Description:     | This property indicates which media preconfigured channels the MG is capable of receiving. It is applicable to the Root Termination only.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| Type:            | OCTET STRING                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| Possible values: | Octet string of size 2 where the bits 1 to 13 (least significant 13 bits) indicate the support or not by the MG of the corresponding Mux code value. It follows the same format as the "Media Preconfigured Channel Receive bits" (MPC-RX) field in the MONA preference message, as defined in Annex K of [ITU-T H.324], Table K.5. The three most significant bits are set to 0.<br><br>Example:<br><br>The octet string 00000000 00000111 indicates support of the Mux code values 1, 2 and 3. In text encoding, this octet string is represented as 00 E0.<br><br>NOTE – The MONA preference message is built by the MGC and the contents of the MPC-RX field may differ from the value of the mpcrx property if the MGC determines to use only a subset of the supported options. |
+| Default:         | None                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| Defined in:      | TerminationState                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| Characteristics: | ReadOnly                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+### 7.1.3 Supported preconfigured channels transmit
+
+|                |                                                                                                                                              |
+|----------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| Property name: | Supported Media Preconfigured Channels Transmit                                                                                              |
+| Property ID:   | mpctx (0x0003)                                                                                                                               |
+| Description:   | This property indicates which media preconfigured channels the MG is capable of transmitting. It is applicable to the Root Termination only. |
+| Type:          | OCTET STRING                                                                                                                                 |
+
+Possible values: Octet string of size 2 where the bits 1 to 13 (least significant 13 bits) indicate the support or not by the MG of the corresponding Mux code value. It follows the same format as the "Media Preconfigured Channel Transmit bits" (MPC-TX) field in the MONA preference message, as defined in Annex K of [ITU-T H.324], Table K.5. The three most significant bits are set to 0.
+
+Example:
+
+The octet string 00000000 00000111 indicates support of the Mux code values 1, 2 and 3. In text encoding, this octet string is represented as 00 E0.
+
+NOTE – The MONA preference message is built by the MGC and the contents of the MPC-TX field may differ from the value of the *mpctx* property if the MGC determines to use only a subset of the supported options.
+
+Default: None
+
+Defined in: TerminationState
+
+Characteristics: ReadOnly
+
+## 7.2 Events
+
+### 7.2.1 MONA preference reception
+
+Event name: MONA Preference reception
+
+Event ID: monaprefmsgin (0x0001)
+
+Description: This event occurs when the MG detects the first MONA preference message on the termination where it is set. After the MG detects a *legdet* event, the MG should cease detection of incoming MONA preference messages and shall not report the *monaprefmsgin* event to the MGC, even if it is not removed from the EventsDescriptor.
+
+#### 7.2.1.1 EventsDescriptor parameters
+
+None.
+
+#### 7.2.1.2 ObservedEventsDescriptor parameters
+
+##### 7.2.1.2.1 Contents of MONA preference message
+
+Parameter name: Contents of MONA Preference message
+
+Parameter ID: prefmsgc (0x0001)
+
+Description: This parameter specifies the actual contents of the MONA preference message.
+
+Type: OCTET STRING
+
+Optional: No
+
+Possible values: The octet string is the actual encoding of the MONA preference message as defined in Table K.4 of [ITU-T H.324].
+
+Default: None
+
+### 7.2.2 MONA preference negotiation completed
+
+Event name: MONA Preference negotiation completed
+
+Event ID: monaprefcompl (0x0002)
+
+Description: This event occurs when the MG detects the first MONA preference message containing an indication that the MONA preference negotiation is completed, i.e., acknowledgement bits are '10', or when the MG receives the first non empty ITU-T H.223 MUX-PDU, on the termination where this event is set. After the MG has detected a *legdet* event, it should cease detection of incoming MONA preference messages and shall not report a *monaprefcompl* event to the MGC, even if it is not removed from the EventsDescriptor.
+
+#### 7.2.2.1 EventsDescriptor parameters
+
+None.
+
+#### 7.2.2.2 ObservedEventsDescriptor parameters
+
+None.
+
+### 7.2.3 Legacy detected
+
+Event name: Legacy Detected
+
+Event ID: legdet (0x0003)
+
+Description: This event occurs when the MG detects a legacy interworking condition on the termination where the event is set.
+
+#### 7.2.3.1 EventsDescriptor parameters
+
+None.
+
+#### 7.2.3.2 ObservedEventsDescriptor parameters
+
+None.
+
+### 7.2.4 MPC reception
+
+Event name: MPC reception
+
+Event ID: mpcrec (0x0004)
+
+Description: This event occurs when the MG detects the first MONA preference message containing encapsulated media preconfigured channel (MPC) media of a predefined channel type or when the MG detects the first non-empty ITU-T H.223 MUX PDU of a predefined channel type on the termination where the event is set. The event occurs once for each different channel type. After the MG has detected a *legdet* event, it should cease detection of incoming MONA preference messages with attached MPC and shall not report the *mpcrec* event to the MGC, even if it is not removed from the EventsDescriptor.
+
+#### 7.2.4.1 EventsDescriptor parameters
+
+None.
+
+#### 7.2.4.2 ObservedEventsDescriptor parameters
+
+##### 7.2.4.2.1 Mux code
+
+Parameter name: Mux Code
+
+Parameter ID: muxcode (0x0001)
+
+Description: This parameter specifies the Mux code values in the media preconfigured channel configuration.
+
+|                  |                                                                                                                                                                                                                                                                                                                                                                                   |
+|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Type:            | OCTET STRING                                                                                                                                                                                                                                                                                                                                                                      |
+| Optional:        | No                                                                                                                                                                                                                                                                                                                                                                                |
+| Possible values: | The octet string is the actual encoding of the Mux code. The Mux code is carried in the four least significant bits of one octet, as defined in clause K.9.3 of [ITU-T H.324]. The four most significant bits are set to 0. The values of the Mux code are defined in Table K.15 of [ITU-T H.324].<br><br>Example:<br>Mux code 2 (AMR-WB) is represented by octet string 00000010 |
+| Default:         | None                                                                                                                                                                                                                                                                                                                                                                              |
+
+## 7.3 Signals
+
+### 7.3.1 Outgoing MONA preference message
+
+|              |                                                                                                                                                                                  |
+|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Signal name: | Outgoing MONA preference message                                                                                                                                                 |
+| Signal ID:   | monaprefmsgout (0x0001)                                                                                                                                                          |
+| Description: | This signal requests the MG to send a MONA preference message. The message is sent repeatedly as long as the signal is active or until a <i>monaprefcompl</i> event is detected. |
+| Signal type: | OnOff                                                                                                                                                                            |
+| Duration:    | Not applicable                                                                                                                                                                   |
+
+#### 7.3.1.1 Additional parameters
+
+##### 7.3.1.1.1 Contents of MONA preference message
+
+|                  |                                                                                                           |
+|------------------|-----------------------------------------------------------------------------------------------------------|
+| Parameter name:  | Contents of MONA preference message                                                                       |
+| Parameter ID:    | prefmsgc (0x0001)                                                                                         |
+| Description:     | This parameter specifies the contents of a MONA preference message.                                       |
+| Type:            | OCTET STRING                                                                                              |
+| Optional:        | No                                                                                                        |
+| Possible values: | The octet string is the encoding of the MONA preference message as defined in Table K.4 of [ITU-T H.324]. |
+| Default:         | None                                                                                                      |
+
+### 7.3.2 Forward media in preconfigured channel
+
+|              |                                                                                                                                                                                                                                                                                                                                                                                               |
+|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Signal name: | Forward Media in Preconfigured Channel                                                                                                                                                                                                                                                                                                                                                        |
+| Signal ID:   | Preconfchannelmedia (0x0002)                                                                                                                                                                                                                                                                                                                                                                  |
+| Description: | This signal requests the MG to forward available media outwards of the context in preconfigured channels. The media PDUs are encapsulated in MONA preference messages. As a result, this signal has no effect if the <i>monaprefmsgout</i> signal is not active, or if the sending of MONA preference messages has been stopped as a result of the detection of a <i>monaprefcompl</i> event. |
+| Signal type: | OnOff                                                                                                                                                                                                                                                                                                                                                                                         |
+| Duration:    | Not applicable                                                                                                                                                                                                                                                                                                                                                                                |
+
+#### 7.3.2.1 Additional parameters
+
+##### 7.3.2.1.1 Mux code
+
+Parameter name: Mux Code  
+Parameter ID: muxcode (0x0003)  
+Description: This parameter specifies the Mux code values in the media preconfigured channel configuration. The MG is requested to start forwarding available media using this configuration. Only one Mux code value per media type may be given at any time. The MGC determines which of the values supported by the MG is used for transmitting. The value must have been included in the MPC-TX field in the MONA preference message sent to the peer.  
+Type: Sub-list of OCTET STRING  
+Optional: No  
+Possible values: Each element in the list is an octet string of size one with the actual encoding of the Mux code in the four least significant bits. The four most significant bits are set to 0. The values of the Mux code are defined in Table K.15 of [ITU-T H.324].  
+Default: None
+
+## 7.4 Statistics
+
+None.
+
+## 7.5 Error codes
+
+None.
+
+## 7.6 Procedures
+
+An MGC implementing the MONA procedures may find out which of the negotiation methods are supported by the MG by auditing the "MONA Class" *monapref/class* property on the Root Termination. Alternatively, this information may be already available in the MGC by configuration.
+
+Additionally, if the MG supports the MPC procedures, i.e., class 1 or 2, the MGC may find out which of the media codec options are supported by the MG for the establishment of media preconfigured channels in the receive and transmit direction by auditing the *monapref/mpcrx* and *monapref/mpctx* properties. Alternatively, this information may be already available in the MGC by configuration. The MG may indicate its support for multiple codec options but the MGC shall only request MPC transmission for one codec option per media type at a time.
+
+Thereafter, the MGC shall build the MONA preference messages based on the procedures which are supported by the MG. The MGC may choose to indicate only a subset of the MG supported capabilities in the MONA preference messages. Indicating capabilities not supported by the MG in the MONA preference message may result in erroneous negotiation and failure to transmit or receive media. The MG does not verify if the contents of the MONA preference message being sent correspond to its supported capabilities.
+
+An MGC implementing the MONA procedures shall request the MG to notify the detection of MONA preference events: MONA Preference message reception, MONA preference negotiation completed, Legacy detected and MPC Reception. The latter event is only needed if the MPC is one of the methods supported for the establishing of media channels. Additionally, the MGC orders the MG to start the transmission of the MONA preference message with signal
+
+*monapref/monaprefmsgout* indicating the content of the message in the signal parameter *prefmsgc*. Thereafter, the MG autonomously retransmits the MONA preference message, eventually updating the acknowledgement bits. If MPC is supported, the MGC may request the MG to forward available early media encapsulated in the MONA preference messages by sending the *monapref/Preconfchannelmedia*. The MGC should preferably send the signal in the same signal descriptor as the *monapref/monaprefmsgout* signal for a faster set-up.
+
+When the MG receives a MONA preference message from the remote end, it shall examine the contents of the message and notify the corresponding events to the MGC.
+
+If the MGC determines that SPC is to be used when early media (via the MPC) is underway, it shall stop the MPC by removing the *monapref/Preconfchannelmedia* signal and the *monapref/mpcrec* event.
+
+If the MG notifies the MGC about the reception of an MPC PDU and the MGC determines that this channel can be established, it shall do so by configuring the multiplex termination with the 'Incoming Multiplex Table' property [ITU-T H.248.12 Amd.2].
+
+When the MGC has received notifications that MPC PDUs have been received in valid channels for all media types, it should remove the *mpcrec* event from the EventsDescriptor. It should also remove it if it determines that no more channels can be established based on the received MPC-TX bits.
+
+If the MGC determines that early media may continue for some media types but should be discontinued for others, it shall send the *monapref/Preconfchannelmedia* signal with a *muxcode* parameter modified appropriately. This may only occur as a result of the received MONA Preference message from the peer indicating that the media channel has not been established (i.e., MPC-RX received at the terminal did not match the media transmission from the terminal). Otherwise, a terminal is committed to continue using the channel indicated from the beginning.
+
+When deactivating or modifying the signal, the MGC should take care not to deactivate other possibly ongoing signals, most notably the *monapref/monaprefmsgout* signal, if that is not intended.
+
+### 7.6.1 MONA preference negotiation completion
+
+A terminal considers the MONA Preference Negotiation phase completed when it receives a MONA preference message with acknowledgement bits set to '10', or when it receives the first non-empty ITU-T H.223 MUX-PDU [ITU-T H.223]. After that point, the terminal will only send MONA preference messages for encapsulating SPC, if SPC is ongoing.
+
+A MG implementing the MONA procedures shall read the acknowledgement bits of the received MONA preference messages. When a MONA preference message is received with the acknowledgement bits set to '10', or when the first non-empty ITU-T H.223 MUX-PDU is received, the MG shall inform the MGC that MONA negotiation is completed with the observed event *monapref/monaprefcompl*.
+
+The MG shall also at this point stop any:
+
+- Sending of MONA preference messages with the exception of MONA preference message encapsulating SPC when SPC sending is ongoing, i.e., when signal *h245tpspc/h245msgout* with parameter *spc* = ON is active.
+- Sending of MPC media encapsulated in MONA preference message, as a consequence of the above action.
+- Detection of incoming MONA preference messages, if a MONA preference message was already received.
+
+NOTE – In an unlikely case, a non-empty ITU-T H.223 MUX PDU may be received at the MG before any MONA preference message has been received. In this case, the MG shall not discontinue the detection of incoming preference messages.
+
+- Detection of MONA Preference Negotiation completed.
+
+Stopping the above actions does not imply any change in the contents of the SignalsDescriptor nor EventsDescriptor, i.e., the signals and events remain in the respective descriptor until the MGC changes their contents. Stopping the above actions is a consequence of the signals and events definition.
+
+### 7.6.2 Fallback to ITU-T H.245 interworking
+
+An MGC and a MG involved in a MONA negotiation procedure with a remote terminal should fallback to ITU-T H.245 interworking on the occurrence of any of the conditions specified in [ITU-T H.324], i.e.:
+
+- More than 20 valid consecutive multiplexer level stuffing flags are detected, as described in clause C.6 in [ITU-T H.324].
+- A normal start-up procedure is detected with the receipt of a normal ITU-T H.245 **TerminalCapabilitySet** message as the first non-empty ITU-T H.223 MUX-PDU at an initial multiplexer level agreed by detecting the standard multiplexer level set-up.
+- A normal ITU-T H.245 **TerminalCapabilitySet** message with empty **genericControlCapability** containing MOS OID is received after completion of the MOS procedure.
+- No valid MOS request is detected, or the ICM is not accepted, within a multiple of the network round trip delay (RTD) period. Typically, three RTDs are adopted. An exception to this fallback condition is also specified in clause K.8.2 of [ITU-T H.324].
+
+The first fallback condition is detected by the MG. All other fallback conditions are detected by the MGC.
+
+In case a fallback to ITU-T H.245 interworking is determined, all channels must be established with legacy ITU-T H.245 methods, i.e., if any channel had already been established, it will be dropped.
+
+#### 7.6.2.1 Legacy condition detected by MGC
+
+If an MGC involved in a MONA negotiation procedure detects any of the conditions specified in clauses K.7.1.2 and K.8.2 of [ITU-T H.324], it should initiate a fallback to legacy interworking and order the MG to:
+
+- stop signal *monapref/monaprefmsgout*;
+- disable event *monapref/monaprefmsgin*;
+- disable event *monapref/monaprefcompl*;
+- stop signal *h245tpspc/h245msgout*, if it had been ordered with parameter *spc=ON*;
+- disable event *h245tpspc/h245msgin*, if it had been armed with parameter *spc=ON*;
+- stop signal *monapref/Preconfchannelmedia*;
+- disable event *monapref/mpcrec*.
+
+#### 7.6.2.2 Legacy condition detected by MG
+
+The MGC may also initiate standard ITU-T H.245 signalling in parallel in order to minimize the time for a legacy interworking fallback. This is done by arming a "Legacy detected" event including an embedded signal descriptor. The embedded signal is the initial ITU-T H.245 message out signal (including H.245 TCS+MSD) to send in case fallback to legacy interworking is detected. The MGC shall not include the *monaprefmsgout* signal nor the *h245tpspc/h245msgout* signal with parameter *spc = ON* in the embedded signal descriptor in order to stop the sending of MONA preference messages as well as encapsulated MPC and SPC when a legacy condition is detected by the MG. The MG will only send the embedded signal in case it detects a legacy interworking condition as specified in clause K.7.1.2 of [ITU-T H.324].
+
+Alternatively, the MGC may send the signal descriptor with the initial H.245 signal and without the MONA related signals subsequently to the reception of the *legdet* event.
+
+If the "Legacy interworking detected" event occurs, the MG shall stop any ongoing:
+
+- detection of incoming MONA preference messages;
+- detection of MONA preference negotiation completed;
+- detection of incoming MPC media in predefined channels;
+- detection of incoming SPC signals.
+
+Stopping the above actions does not imply any change in the contents of the EventsDescriptor, i.e., the events remain in the descriptor until the MGC changes its contents. The events related to the detection actions above by definition cannot occur once the *legdet* event has been detected.
+
+
+
+
+
+## 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.76-201009-I_PDF-E/raw.md b/marked/H/T-REC-H.248.76-201009-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..3bdbea76e71cfb6553bd701cd0ddf2c59c1dd65d
--- /dev/null
+++ b/marked/H/T-REC-H.248.76-201009-I_PDF-E/raw.md
@@ -0,0 +1,409 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.76**
+
+(09/2010)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+---
+
+**Gateway control protocol: Filter group package  
+and guidelines**
+
+Recommendation ITU-T H.248.76
+
+![ITU logo](84a1d09fb489061482111515543b60dc_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 prominently displayed in blue and red. To the right of the globe, the text "International Telecommunication Union" is written in a smaller, blue 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        |
+| <b>Communication procedures</b>                                               | <b>H.240–H.259</b> |
+| 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.76**
+
+# **Gateway control protocol: Filter group package and guidelines**
+
+## **Summary**
+
+Recommendation ITU-T H.248.76 defines the filter group package. Using this package, the media gateway controller (MGC) can create and manage groups of filters, then apply those filter-groups to the media gateway (MG) terminations and streams.
+
+While the filter group package provides the framework for managing filters, it does not provide protocol elements for defining the filters' concrete match conditions and actions. Instead, it relies on using elements from other packages, for example, the packages defined by Recommendation ITU-T H.248.43.
+
+## **History**
+
+| Edition | Recommendation | Approval   | Study Group |
+|---------|----------------|------------|-------------|
+| 1.0     | ITU-T H.248.76 | 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                           | 2    |
+| 6 Filter Group package .....                  | 2    |
+| 6.1 Properties.....                           | 3    |
+| 6.2 Events .....                              | 4    |
+| 6.3 Signals .....                             | 4    |
+| 6.4 Statistics.....                           | 4    |
+| 6.5 Error codes.....                          | 4    |
+| 6.6 Procedures .....                          | 5    |
+| Bibliography.....                             | 9    |
+
+
+
+## Gateway control protocol: Filter group package and guidelines
+
+# 1 Scope
+
+This Recommendation defines the filter group package. Using this package, the media gateway controller (MGC) can create and manage groups of filters, then apply those filter-groups to the MG's terminations and streams. The package is especially useful when large groups of related filters are called for, as it allows the MGC to manipulate the individual filters without having to repeat them all in each ITU-T H.248 command.
+
+The filter group package provides protocol elements and procedures for:
+
+- Creating groups of filters.
+- Adding and removing filters to and from an existing filter-group.
+- Modifying an existing filter.
+- Assigning multiple filter-groups to any of the MG's terminations or streams.
+- Collecting statistics regarding filters and filter-groups.
+
+The filter group package does not, however, provide any protocol elements covering a filter's concrete match conditions or actions. Instead, the package should be combined with other packages that provide such elements, e.g., the packages defined by [ITU-T H.248.43].
+
+# 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 (05/2008) and Amendment 2 (12/2009).
+- [ITU-T H.248.8] Recommendation ITU-T H.248.8 (2007), *Gateway control protocol: Error code and service change reason description*.
+- [ITU-T H.248.43] Recommendation ITU-T H.248.43 (2008), *Gateway control protocol: Packages for gate management and gate control*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following term defined elsewhere:
+
+**3.1.1 filter** [ITU-T H.248.43]: In general: A set of terms and/or criteria used for the purpose of separating or categorizing. This is accomplished via single- or multi-field matching of traffic header and/or payload data. "Filters" are often manipulated and used in network operation and policy.
+
+In an ITU-T H.248 framework: Filters specify the criteria for matching a pattern to distinguish separable classes of traffic. Filters are defined on the basis of H.248 properties, which determine the filter's condition and actions. Typically a filter includes a single action element indicating either an "accept" or "reject" action, with or without statistics recording.
+
+NOTE 1 – The definition is based on [b-IETF RFC 3198] and [b-IETF RFC 3060].
+
+NOTE 2 – This filter definition implies the concept of filter actions as well as filter conditions.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation uses the following terms:
+
+**3.2.1 filter-group context:** An ITU-T H.248 context that defines a group of filters. This filter-group can then be referenced by other terminations or streams.
+
+**3.2.2 filter-group termination:** A termination belonging to a filter-group context. Such a termination defines one filter out of the complete group.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+MG Media Gateway
+
+MGC Media Gateway Controller
+
+# 5 Conventions
+
+The names of ITU-T H.248 descriptors always have a capitalized first letter, for example, Streams and Local Descriptor.
+
+The names of ITU-T H.248 properties, events, signals, statistics and parameters appear in italics, for example *ReserveValue*.
+
+All error codes appearing in this Recommendation are described in [ITU-T H.248.8].
+
+# 6 Filter Group package
+
+Package Name: Filter Group
+
+Package ID: filtgrp (0x0103)
+
+Description: This package allows the MGC to indicate that a context is being used for defining a group of filters. That filter-group can then be applied to other terminations or streams, e.g., a termination representing a physical interface of the MG.
+
+This method for describing filter-groups is useful when a large number of filters are needed for a particular filter-group. It allows the creation, modification and deletion of individual filters without the need to repeat all filters in a single command
+
+Version: 1
+
+Extends: None
+
+## 6.1 Properties
+
+### 6.1.1 Filtering Context
+
+Property Name: Filtering Context  
+Property ID: fc (0x0001)  
+Description: This context level property indicates that the context is being used to define a group of filters (i.e., the context is a filter-group context). Such a context may only contain ephemeral terminations. The setting of the property is valid for the whole lifetime of the context.  
+Type: Enumeration  
+Possible values: "FILT" (0x0001): Filter-Group Context  
+Default: "FILT" (0x0001)  
+Defined in: ContextAttribute  
+Characteristics: Read/Write
+
+### 6.1.2 Filter Group Identifier
+
+Property Name: Filter Group Identifier  
+Property ID: fgid (0x0002)  
+Description: This property may only be used at the ContextAttribute level in a filter-group context. When used at that level, the property defines the identifier for the filter-group. Only one value shall be assigned, and that value must be unique across the complete MG (or virtual MG).  
+When used at the TerminationState level, this property indicates the list of filter-groups that shall be applied to the termination. As such, it shall not be used on terminations belonging to a filter-group context.  
+When used at the stream (i.e., LocalControl) level, this property indicates the list of filter-groups that shall be applied to the stream. As such, it shall not be used on terminations belonging to a filter-group context.  
+Type: Sub-list of String  
+Possible values: Any  
+If no filter-groups are applied to a termination or stream, the property shall include a single empty string. The empty string identifier shall not be assigned to any filter-group context.  
+Default: A single empty string  
+Defined in: Local Control, TerminationState or ContextAttribute  
+Characteristics: Read/Write
+
+### 6.1.3 Relative Filter Order
+
+Property Name: Relative Filter Order  
+Property ID: rfo (0x0003)  
+Description: The relative position of the filter defined by the filter-group termination holding this property, compared to the filters of the other terminations within the filter-group context. The filter defined by the termination with the lowest *filtgrp/rfo* number shall be executed first; the filter defined by the termination
+
+with the next-lowest *filtgrp/rfo* shall be executed second, etc. Terminations may not be assigned with identical *filtgrp/rfo* values within the same context.
+
+Type: Unsigned Integer  
+Possible values: 1 and up  
+Default: None  
+Defined in: TerminationState  
+Characteristics: Read/Write
+
+## 6.2 Events
+
+None.
+
+## 6.3 Signals
+
+None.
+
+## 6.4 Statistics
+
+None.
+
+## 6.5 Error codes
+
+### 6.5.1 Element not allowed in a filter-group context
+
+Error Code #: 481  
+Name: Element not allowed in a filter-group context  
+Definition: A filter-group termination may only contain elements (properties/signals/events and statistics) defined by [ITU-T H.248.43], and/or elements defined by other Recommendations that are related to packet filtering, and/or elements declared by other Recommendations as being valid for use in a filter-group context.  
+A command that would result in other elements being used in such a termination shall be rejected using this error code.  
+Error Text in the  
+Error Descriptor: –  
+Comment: –
+
+### 6.5.2 Unknown filter-group
+
+Error Code #: 482  
+Name: Unknown filter-group  
+Definition: The filter-group referenced is invalid or unknown. Therefore, the command is disregarded.  
+Error Text in the  
+ErrorDescriptor: –  
+Comment: –
+
+## 6.6 Procedures
+
+### 6.6.1 General
+
+The filter group package allows the MGC to gather a collection of filters into a single filter-group. The group is represented using a filter-group context, where each of the context's terminations describes a single filter. The conditions and actions comprising each filter are, in turn, encoded using the properties and statistics of the various packages dealing with gate management and filtering, such as those described in [ITU-T H.248.43]. The MGC can thus manage the filters of a filter-group by adding, modifying or subtracting individual terminations. Properties related to the individual filters shall not be added at the ContextAttribute level.
+
+NOTE – A filter's conditions and actions can be defined using elements outside of [ITU-T H.248.43]; however, such filters are for further study. It is expected that Recommendations defining such elements will have a statement of applicability with regard to the support of the filter group package.
+
+Each filter-group context has a unique identifier, given by a ContextAttribute level *Filter Group Identifier (filtgrp/fgid)* property. The MGC can then use that filter-group for processing the packets of another (non filter-group) termination by placing this identifier in the *filtgrp/fgid* property of a TerminationState or LocalControl Descriptor. More than one filter-group can be applied to a termination, by including more than one identifier in the *filtgrp/fgid* property.
+
+### 6.6.2 Filter-group management
+
+#### 6.6.2.1 Generation of filter-groups
+
+The MG builds one filter-group per filter-group context. Each of the context's terminations represents one filter within the group. For example, if there are five terminations in the context, there will be five filters in the filter-group. The conditions and actions associated with each filter are defined by placing applicable filtering-related elements (e.g., those defined in [ITU-T H.248.43]) on the filter-group termination. While the MGC may place those elements at either the stream or termination levels, only one stream may be defined on a filter-group termination. In effect, the complete filter-group is related to a single media stream; therefore, the same *StreamID* shall be used by all terminations within a single filter-group context.
+
+The ordering of filters within a filter-group is determined by the *Relative Filter Order (filtgrp/rfo)* property: The filter corresponding to the termination with the lowest *filtgrp/rfo* value (e.g., one) is executed first, followed by the termination with the next-lowest *filtgrp/rfo* value, etc. A *filtgrp/rfo* value shall be assigned at the termination creation time (i.e., the first Add request). The MGC shall not assign the same *filtgrp/rfo* number to more than one termination in a single filter-group context. If the MG detects such an occurrence, it shall respond with error code 473 "Conflicting Property Values".
+
+It is assumed that the MGC is responsible for validating any interactions between the filters in a filter-group. No such validation is expected at the MG.
+
+#### 6.6.2.2 Adding filters
+
+A new filter-group is instantiated when a termination is first Added to a context and the *Filtering Context* ContextAttribute property (*filtgrp/fc*) is set to "FILT". The MGC shall also assign an identifier to the filter-group via the *Filter Group Identity (filtgrp/fgid)* property. This identifier allows the filter-group to be referenced by other terminations and streams at a later point in time.
+
+A new filter is inserted to a filter-group by Adding to the corresponding filter-group context a new termination that carries the appropriate filtering-related elements. The value of the *Relative Filter Order (filtgrp/rfo)* property at termination creation may result in that filter being inserted at the start, middle or end of the filter-group, depending on how that value compares to the values of the property on the existing terminations.
+
+Filtering-related elements may be applied at both the termination (e.g., TerminationState Descriptor) and stream (e.g., LocalControl Descriptor) level. However, there may only be one stream per filter-group termination. The use of filtering-related properties in the Local and Remote Descriptors is not typical, as such properties usually indicate to which direction (ingress, egress or both) they apply. However, the use of such properties at the Local and Remote Descriptors is not prohibited.
+
+When utilizing properties defined in other Recommendations, attention should be paid to what descriptor shall be used in conjunction with this package. For example, clause 9.1.2 of [ITU-T H.248.43] indicates that the *Internet Protocol Type Mask* property may be used either in the LocalControl or TerminationState Descriptors. However, the use of TerminationState is only allowed on the Root termination. Therefore, it would not be valid to use this property at the TerminationState level in a filter-group termination.
+
+As the terminations in a filter-group context do not relate to actual media streams, the *StreamMode*, *ReserveValue* and *ReserveGroup* properties shall maintain their default values. If the MGC tries to change these properties, or to set properties/signals/events/statistics other than those supported by the MG for filtering, the MG shall reply with error code 481 "Element not allowed in a filter-group context".
+
+#### 6.6.2.3 Modification of filters
+
+A filter may be modified by changing the relevant properties on the filter-group termination representing it. Once modified, the changes to the filter shall be automatically propagated to all terminations and streams referencing the relevant filter-group.
+
+#### 6.6.2.4 Deleting filter-rules and filter-groups
+
+A filter is deleted by subtracting the corresponding termination from the filter-group context. A complete filter-group is destroyed when the filter-group context defining it is destroyed, i.e., when all terminations have been removed from that context.
+
+When an entire filter-group is removed, any terminations/streams that still reference it are left referencing an unknown filter-group identifier. Those terminations/streams shall filter their traffic as if the unknown identifier no longer appears in their *filtgrp/fgid* property. If the MGC subsequently changes the value of *filtgrp/fgid* on those terminations, it shall remove the offending identifier in order to avoid generating an error.
+
+#### 6.6.2.5 Auditing filters
+
+The MGC may audit the filters comprising a particular filter-group by performing a wildcarded AuditValue on all terminations belonging to the corresponding filter-group context. As filter-group terminations may only support filtering-related elements, only information related to the group's filters will be returned by the MG.
+
+#### 6.6.2.6 Locating filter-groups
+
+The MGC may locate the filter-group context corresponding to a specific identifier by issuing an AuditValue command, using wildcard (ALL) as the ContextID, and the known *filtgrp/fgid* value as a ContextAttribute level selection criteria (see clause 7.2.9 of [ITU-T H.248.1]). This procedure can be combined with that of clause 6.6.2.5, allowing the MGC to locate a filter-group and audit its filters using a single command.
+
+### 6.6.3 Assigning filter-groups
+
+The MGC can assign one or more filter-groups to a termination using the *Filter Group Identity* (*filtgrp/fgid*) property of that termination's TerminationState Descriptor. Similarly, filter-groups may be assigned to a stream via the *filtgrp/fgid* property appearing in the LocalControl Descriptor. The ability to set multiple filter-groups to a single termination or stream allows different terminations/streams to share subsets of related filters, thus minimizing the need for duplication.
+
+When multiple filter-groups are assigned to a single termination or stream, they are applied in the order in which they appear in the *filtgrp/fgid* property. Filtered traffic is first checked against the filters of the first group referenced by *filtgrp/fgid*. If the traffic does not match the conditions of any of those filters, it is checked against the second filter-group referenced by *filtgrp/fgid*, etc. Within each group, the traffic is checked against the individual filters according to the value of the *Relative Filter Order* (*filtgrp/rfo*) property. Once the traffic matches a filter, the actions of that filter are applied and the filtering process stops, i.e., further matching is attempted neither against the other filters of the current filter-group nor against those of the next groups.
+
+The MGC may set filtering-related properties directly on the termination or stream referencing the filter-groups. These "termination local" rules shall be treated as another filter, which has a higher priority than the filter-groups referenced by the *filtgrp/fgid* property. Similarly, if the MGC sets the *filtgrp/fgid* property at both the stream and the termination levels, the stream level filter-groups shall be treated as the higher priority ones. Note that this means that if the stream's traffic matches one of the stream level filters, it will not be checked against the filter-groups applied at the termination level.
+
+Any changes to a filter-group (addition, modification or removal of filters) are applied automatically to the terminations/streams referencing it, as soon as those changes are made.
+
+If the MGC requires the removal of one or more filter-groups from a termination or stream, it shall remove the identifier of those groups from the appropriate *filtgrp/fgid* property.
+
+In order to determine which filter-groups are applied to a termination or stream, the MGC can audit (using an AuditValue command) the value of the *filtgrp/fgid* property. The MG shall then respond with the list of filter-group identifiers.
+
+If the MGC refers to an unknown filter-group identifier in a *filtgrp/fgid* property, the MG shall respond with error code 482 "Unknown Filter Group".
+
+### 6.6.4 Statistics
+
+The MG may collect the statistics of filtering-related packages (e.g., those defined by [ITU-T H.248.43]) on filter-group terminations. Additional statistics that are relevant to packet filtering (e.g., the ones defined by [b-ITU-T H.248.61]) may also be supported on such terminations. Statistics on filter-group terminations are only collected at the termination level (i.e., not at the stream level).
+
+When a statistic is enabled on a filter-group termination, its value relates to the use of the corresponding filter across all references to the filter-group. For example, if the Discarded Packets statistic (see clause 7.4.1 of [ITU-T H.248.43]) is enabled on a filter-group termination, its value would record all incoming packets that were dropped by that filter, on all terminations and streams to which it was applied.
+
+Filtering-related statistics may also be collected on a termination or stream that references one or more filter-groups through the *Filter Group Identifier* property. Such a statistic corresponds to all filtering applied to that termination's or stream's traffic. Thus the statistic will relate both to the filter applied by properties installed directly on the termination/stream (if any), as well as to the filters in the filter-groups it references. This is irrespective of whether the statistic is enabled on the terminations of the referenced filter-group contexts.
+
+### 6.6.5 Examples
+
+**Table 1 – Creation of a filter-group**
+
+| ITU-T H.248 encoding (shortened command)                                                                                                                                                                                                                                                                                                                                                                      | Comments:                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <pre> MEGACO/3 [11.9.19.65]:54321 Transaction = 67891 {   Context = \$ {     ContextAttr = {       filtgrp/fc = FILT,       filtgrp/fgid = "MyFilter"     }     Add = tid1 {       Media {         Stream = 1 {           LocalControl {             gm/saf = ON,             gm/sam = "[102.0.*.*]",             ifb/fm = DENY,             filtgrp/rfo = 3           }         }       }     }   } } </pre> | <p>This command requests the creation of a filter-group context with two terminations. Each termination represents one filter within the group. The identifier associated with the new filter-group is "MyFilter". The filter of termination "tid2" will appear first in the filter-group followed by the filter defined by termination "tid1".</p> |
+
+**Table 2 – Assigning a filter to an interface**
+
+| ITU-T H.248 encoding (shortened command)                                                                                                                                                                                  | Comments:                                                                                      |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|
+| <pre> MEGACO/3 [11.9.19.65]:54321 Transaction = 67892 {   Context = 12345 {     Modify = interface1 {       Media {         TerminationState {           filtgrp/fgid = ["MyFilter"]         }       }     }   } } </pre> | <p>This command assigns the filter-group created in Table 1 to the interface1 termination.</p> |
+
+## Bibliography
+
+- [b-ITU-T H.248.61] Recommendation ITU-T H.248.61 (2009), *Gateway control protocol: Packages for network level H.248 statistics.*
+- [b-IETF RFC 3060] IETF RFC 3060 (2001), *Policy Core Information Model – Version 1 Specification.*
+- [b-IETF RFC 3198] IETF RFC 3198 (2001), *Terminology for Policy-Based Management.*
+
+
+
+
+
+## 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.77-201712-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.248.77-201712-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..22dc7ff0fb30f976cc1e576c45d2b7e65fa5ddc7
--- /dev/null
+++ b/marked/H/T-REC-H.248.77-201712-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.77-201712-I_PDF-E/24c9e038a791677ed33100667b64f7e6_img.jpg b/marked/H/T-REC-H.248.77-201712-I_PDF-E/24c9e038a791677ed33100667b64f7e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c6e0e0439537431580880517c6870494ec2aa56c
--- /dev/null
+++ b/marked/H/T-REC-H.248.77-201712-I_PDF-E/24c9e038a791677ed33100667b64f7e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0365b7f1d3be38a432fb09233255ec8c06c5b870b2e1d1552d1040f82580df8f
+size 87673
diff --git a/marked/H/T-REC-H.248.77-201712-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/H/T-REC-H.248.77-201712-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..96b4f5e506cea018e462219ee8d58e377674d574
--- /dev/null
+++ b/marked/H/T-REC-H.248.77-201712-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6c31dac4143902d5c0d69bc53f776514b327d9b9d06a08c1c9c1a2568927b7f2
+size 110200
diff --git a/marked/H/T-REC-H.248.77-201712-I_PDF-E/990567efebf979be51f56d1150012c9d_img.jpg b/marked/H/T-REC-H.248.77-201712-I_PDF-E/990567efebf979be51f56d1150012c9d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9fa0a843dfabeb6d4edb29e305223fbd2505a49e
--- /dev/null
+++ b/marked/H/T-REC-H.248.77-201712-I_PDF-E/990567efebf979be51f56d1150012c9d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:695ab9ea67d1d233a8ca5da2717c46b08f1949e1e4b219d2e8a1910c63ae321b
+size 37912
diff --git a/marked/H/T-REC-H.248.77-201712-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/H/T-REC-H.248.77-201712-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3cc633f0a3b78f55b2d3738a8f5577f202f2e176
--- /dev/null
+++ b/marked/H/T-REC-H.248.77-201712-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc782f49e601eceb350cc88b0c0bb24e2ccf7658d651ac5e26155cfff2dfd501
+size 95458
diff --git a/marked/H/T-REC-H.248.77-201712-I_PDF-E/raw.md b/marked/H/T-REC-H.248.77-201712-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..2f926ca093e2dd7d5a168fd38817391208794887
--- /dev/null
+++ b/marked/H/T-REC-H.248.77-201712-I_PDF-E/raw.md
@@ -0,0 +1,1211 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.77**
+
+(12/2017)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+---
+
+**Gateway control protocol: Secure real-time  
+transport protocol (SRTP) package and  
+procedures**
+
+Recommendation ITU-T H.248.77
+
+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. 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        |
+| <b>Communication procedures</b>                                                             | <b>H.240–H.259</b> |
+| 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.248.77
+
+## Gateway control protocol: Secure real-time transport protocol (SRTP) package and procedures
+
+## Summary
+
+Recommendation ITU-T H.248.77 defines a new ITU-T H.248 package, the secure real-time transport protocol (SRTP) package. In addition, this Recommendation covers a set of procedures related to SRTP key management. The combination of package and procedures allows a media gateway controller (MGC) to control the use of SRTP by a media gateway (MG).
+
+This revision contains an updated package that allows for the usage of datagram transport layer security (DTLS)-SRTP key management scheme that exchanges the peers' certificates via the signalling path and then establishes a DTLS connection on the bearer path.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T H.248.77 | 2010-09-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/10987">11.1002/1000/10987</a> |
+| 2.0     | ITU-T H.248.77 | 2017-12-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/13432">11.1002/1000/13432</a> |
+
+## Keywords
+
+Key management, SRTP.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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    |
+| 1.1 Connection model.....                                                           | 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 Secure RTP package .....                                                          | 4    |
+| 6.1 Properties .....                                                                | 4    |
+| 6.2 Events .....                                                                    | 6    |
+| 6.3 Signals .....                                                                   | 7    |
+| 6.4 Statistics.....                                                                 | 7    |
+| 6.5 Error codes.....                                                                | 9    |
+| 6.6 Procedures .....                                                                | 9    |
+| 7 Key management using SDP security descriptions .....                              | 11   |
+| 7.1 Overspecification of SRTP parameters and multiple keys.....                     | 12   |
+| 7.2 Wildcarding of SRTP parameters.....                                             | 12   |
+| 7.3 Interoperability with offer/answer-based implementations.....                   | 13   |
+| 7.4 SDES and SRTP cryptographic contexts .....                                      | 13   |
+| 7.5 Mapping of master keys for sent packets and received packets statistics .....   | 14   |
+| 8 Key management using DTLS-SRTP .....                                              | 14   |
+| 8.1 Key management indication .....                                                 | 15   |
+| 8.2 Bearer plane connection for "DTLS-SRTP" .....                                   | 15   |
+| 8.3 Multi key management operation .....                                            | 17   |
+| 9 Security considerations .....                                                     | 17   |
+| 9.1 Relation to key management scheme "SDES" .....                                  | 17   |
+| 9.2 Relation to key management scheme "DTLS-SRTP" .....                             | 17   |
+| Appendix I – Example call flows for key management scheme "SDES" .....              | 18   |
+| I.1 Initial session setup using SDP security descriptions.....                      | 18   |
+| I.2 MG1's key is about to expire .....                                              | 21   |
+| I.3 Auditing SRTP capabilities .....                                                | 21   |
+| I.4 Auditing of SRTP statistics .....                                               | 22   |
+| Appendix II – Sample use-cases of SRTP bearer encryption .....                      | 24   |
+| II.1 Use-case #1: ITU-T H.248 MG for peering IP and circuit-switched networks ..... | 24   |
+| II.2 Use-case #2: ITU-T H.248 MG for peering IP networks .....                      | 24   |
+| II.3 Use-case #3: Transparent SRTP forwarding .....                                 | 25   |
+| Bibliography.....                                                                   | 27   |
+
+
+
+# **Gateway control protocol: Secure real-time transport protocol (SRTP) package and procedures**
+
+# **1 Scope**
+
+The secure real-time transport protocol (SRTP) is a real-time transport protocol (RTP) profile that provides confidentiality, message authentication and replay protection to RTP and RTP control protocol (RTCP) sessions. The secure RTP package allows a media gateway controller (MGC) to control the use of SRTP by a media gateway (MG). This package is defined in detail in clause 6.
+
+By itself, the secure RTP package is incomplete, as it does not provide procedures for key management. Instead, it is designed to rely on existing key-management schemes (see also [b-IETF RFC 7202]). [b-IETF RFC 5479] provides an example selection of key-management protocol options for SRTP in "SIP networks".
+
+Clause 7 provides procedures for the use of one such key-management scheme: session description protocol (SDP) security descriptions.
+
+Clause 8 provides procedures for the use of one such key-management scheme: datagram transport layer security (DTLS)-SRTP.
+
+Several reasons exist why this Recommendation is required, in addition to the existing (usually SDP-based) SRTP key-management schemes. The most significant of which are listed below:
+
+- Most existing SDP key-management schemes rely on the SDP offer/answer model (see [b-IETF RFC 3264]). However, the offer/answer model is not used in ITU-T H.248 as it does not fit the nature of the connection between an ITU-T H.248 MGC and a MG.
+- Existing SDP key-management schemes do not contain procedures relating to parameter overspecification and wildcarding, which are unique to ITU-T H.248.
+- The limited lifetime of SRTP master keys calls for mechanisms for handling master key expiry. The existing mechanisms cannot be used in ITU-T H.248.
+- The SRTP package allows explicit control over the key-management scheme employed, allowing easy interoperability with, and migration to future schemes.
+- The SRTP package allows an MGC to audit the SRTP capabilities of an MG through the use of the packages descriptor and the properties of the new package.
+- The SRTP package allows an MGC to collect statistics regarding the number of security violations encountered by the MG, and the volume of SRTP traffic it processed.
+
+The scope of the (09/2010) edition of this Recommendation is limited to use-cases in which a MG applies SRTP procedures, as described in section 3.3 of [IETF RFC 3711], to the SRTP packets it sends and receives. Use-cases in which the MG handles SRTP packets without using those procedures (e.g., transparent forwarding, storage in encrypted form, etc.) are intentionally left out of this Recommendation.
+
+This revision (12/2017) of the Recommendation extends the scope for further SRTP key management schemes, such as DTLS-SRTP according to [b-IETF RFC 5763] and [IETF RFC 5764].
+
+## **1.1 Connection model**
+
+All protocol elements and procedures described in this Recommendation are limited to the extent of a single ITU-T H.248 termination. In addition, no assumptions are made regarding either the lower layer protocols beneath the SRTP level or the upper layer protocols/codecs being carried by the SRTP.
+
+This allows the use of the Recommendation's procedures in various connection models and use-cases (e.g., an SRTP-enabled announcement server, an SRTP to RTP translator, etc.).
+
+Figure 1 details the generic connection-model where an SRTP-enabled termination is connected to a single other termination (either SRTP-enabled or not). The generalization to any number of terminations is trivial.
+
+![Diagram of a two-termination context with an SRTP termination. The diagram shows an 'ITU-T H.248 context' box containing two terminations. The left termination is an 'SRTP-enabled termination' with internal layers: 'Upper-layer codecs', 'RTP/RTCP', 'SRTP/SRTCP', and 'Lower-layer protocols'. The right termination is labeled 'Other termination'. A dashed line labeled 'SRTP session' connects the 'RTP/RTCP' layer of the SRTP-enabled termination to the 'Other termination' via a star symbol. A solid line labeled 'Lower-layer bearer' connects the 'Lower-layer protocols' layer of the SRTP-enabled termination to the 'Other termination'. The 'Other termination' is connected to an external line labeled 'Any type of bearer/session'. The diagram is labeled 'H.248.77(10)_F01' in the bottom right corner.](990567efebf979be51f56d1150012c9d_img.jpg)
+
+Diagram of a two-termination context with an SRTP termination. The diagram shows an 'ITU-T H.248 context' box containing two terminations. The left termination is an 'SRTP-enabled termination' with internal layers: 'Upper-layer codecs', 'RTP/RTCP', 'SRTP/SRTCP', and 'Lower-layer protocols'. The right termination is labeled 'Other termination'. A dashed line labeled 'SRTP session' connects the 'RTP/RTCP' layer of the SRTP-enabled termination to the 'Other termination' via a star symbol. A solid line labeled 'Lower-layer bearer' connects the 'Lower-layer protocols' layer of the SRTP-enabled termination to the 'Other termination'. The 'Other termination' is connected to an external line labeled 'Any type of bearer/session'. The diagram is labeled 'H.248.77(10)\_F01' in the bottom right corner.
+
+**Figure 1 – Two-termination context with an SRTP 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 H.248.1] Recommendation ITU-T H.248.1 (2013), *Gateway control protocol: Version 3*.
+- [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.47] Recommendation ITU-T H.248.47 (2008), *Gateway control protocol: Statistic conditional reporting package*.
+- [ITU-T H.248.49] Recommendation ITU-T H.248.49 (2007), *Gateway control protocol: Session description protocol RFC and capabilities packages*.
+- [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.93] Recommendation ITU-T H.248.93 (2014), *Gateway control protocol: ITU-T H.248 support for control of transport security using the datagram transport layer security (DTLS) protocol*.
+- [IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications*.
+- [IETF RFC 3711] IETF RFC 3711 (2004), *The Secure Real-time Transport Protocol (SRTP)*.
+- [IETF RFC 4568] IETF RFC 4568 (2006), *Session Description Protocol (SDP) Security Descriptions for Media Streams*.
+
+- [IETF RFC 4572] IETF RFC 4572 (2017), *Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP)*.
+- [IETF RFC 5246] IETF RFC 5246 (2008), *The Transport Layer Security (TLS) Protocol Version 1.2*.
+- [IETF RFC 5764] IETF RFC 5764 (2010), *Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)*.
+- [IETF RFC 6347] IETF RFC 6347 (2012), *Datagram Transport Layer Security Version 1.2*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 RTP session** (section 2.2.2 of [b-IETF RFC 7656] | [b-ITU-T H.248.95]): An association among a group of participants communicating with RTP. It is a group communications channel which can potentially carry a number of RTP Streams. Within an RTP Session, every Participant can find meta-data and control information (over RTCP) about all the RTP Streams in the RTP Session. The bandwidth of the RTCP control channel is shared between all Participants within an RTP Session.
+
+**3.1.2 SRTP cryptographic context** [IETF RFC 3711]: The set of cryptographic state information that an SRTP sender or receiver must maintain per SRTP session participant.
+
+NOTE – This term is often abbreviated as "crypto context".
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 decrypting master key**: An SRTP master key used to decrypt and authenticate SRTP packets received by the MG.
+
+**3.2.2 encrypting master key**: An SRTP master key used to encrypt and authenticate SRTP packets sent by the MG.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|       |                                                                           |
+|-------|---------------------------------------------------------------------------|
+| AES   | Advanced Encryption Standard                                              |
+| DTLS  | Datagram Transport Layer Security                                         |
+| HMAC  | Keyed-Hash Message Authentication Code                                    |
+| IP    | Internet Protocol                                                         |
+| IPSec | IP Security                                                               |
+| ISDN  | Integrated Services Digital Network                                       |
+| L1    | Layer 1 (of the Open Systems Interconnection model – the physical layer)  |
+| L2    | Layer 2 (of the Open Systems Interconnection model – the data link layer) |
+| MG    | Media Gateway                                                             |
+| MGC   | Media Gateway Controller                                                  |
+| MKI   | Master Key Identifier                                                     |
+
+|        |                                                    |
+|--------|----------------------------------------------------|
+| NAPT   | Network Address and Port Translation               |
+| NAT    | Network Address Translation                        |
+| PSTN   | Public Switched Telephone Network                  |
+| ROC    | Rollover Counter                                   |
+| RTCP   | RTP Control Protocol                               |
+| RTP    | Real-time Transport Protocol                       |
+| SAVP   | Secure Audio-Video Profile                         |
+| SDES   | Session Description Protocol Security Descriptions |
+| SDP    | Session Description Protocol                       |
+| SHA1   | Secure Hash Algorithm 1                            |
+| SRTCP  | Secure RTCP                                        |
+| SRTP   | Secure RTP                                         |
+| SSRC   | Synchronization Source                             |
+| TDM    | Time Division Multiplexing                         |
+| TLS    | Transport Layer Security                           |
+| UDP    | User Datagram Protocol                             |
+| WebRTC | Web Real-Time Communications                       |
+
+# 5 Conventions
+
+The names of ITU-T H.248 descriptors are always capitalized, for example, Streams and Local Descriptor.
+
+The names of ITU-T H.248 properties, events, signals and parameters appear in the text in italics, for example *ReserveValue*.
+
+All error codes appearing in this Recommendation are described in [ITU-T H.248.8] and [ITU-T H.248.49].
+
+# 6 Secure RTP package
+
+|                      |                                                                                                                                                                           |
+|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Package name:</b> | Secure RTP                                                                                                                                                                |
+| <b>Package ID:</b>   | srtp (0x0107)                                                                                                                                                             |
+| <b>Description:</b>  | This package defines elements that allow the MGC to control an MG's use of the SRTP profile. Version 2 adds support for key management via DTLS for SRTP [IETF RFC 5764]. |
+| <b>Version:</b>      | 2                                                                                                                                                                         |
+| <b>Extends:</b>      | None                                                                                                                                                                      |
+
+## 6.1 Properties
+
+### 6.1.1 Supported Encryption Transforms
+
+|                       |                                 |
+|-----------------------|---------------------------------|
+| <b>Property name:</b> | Supported Encryption Transforms |
+| <b>Property ID:</b>   | set (0x0001)                    |
+
+**Description:** This property declares the set of encryption transforms that can be used by SRTP sessions.
+
+**Type:** Sub-list of Enumeration
+
+**Possible values:** Each item in the list can be one of:  
+ "NULL" (0x0000): The NULL Cipher  
+ "AES\_CM\_128" (0x0001): AES in counter mode with a 128-bit key  
+ "AES\_CM\_192" (0x0002): AES in counter mode with a 192-bit key  
+ "AES\_CM\_256" (0x0003): AES in counter mode with a 256-bit key  
+ "AES\_F8\_128" (0x0004): AES in f8 mode with a 128-bit key  
+ "AES\_F8\_192" (0x0005): AES in f8 mode with a 192-bit key  
+ "AES\_F8\_256" (0x0006): AES in f8 mode with a 256-bit key
+
+**Default:** Provisioned
+
+**Defined in:** TerminationState
+
+**Characteristics:** ReadOnly
+
+### 6.1.2 Supported Authentication Transforms
+
+**Property name:** Supported Authentication Transforms
+
+**Property ID:** sat (0x0002)
+
+**Description:** This property declares the set of authentication transforms that can be used by SRTP sessions.
+
+**Type:** Sub-list of Enumeration
+
+**Possible values:** Each item in the list can be one of:  
+ "NULL" (0x0000): The NULL authentication algorithm  
+ "HMAC\_SHA1\_80" (0x0001): HMAC-SHA1 with an 80-bit tag  
+ "HMAC\_SHA1\_32" (0x0002): HMAC-SHA1 with a 32-bit tag
+
+**Default:** Provisioned
+
+**Defined in:** TerminationState
+
+**Characteristics:** ReadOnly
+
+### 6.1.3 Key Management Scheme
+
+**Property name:** Key Management Scheme
+
+**Property ID:** km (0x0003)
+
+**Description:** This property controls the key management scheme that will be used for supplying the SRTP parameters and keys
+
+**Type:** Enumeration
+
+**Possible values:** "None" (0x0000): No key management will be used.  
+ "SDES" (0x0001): SDP security descriptions [IETF RFC 4568]  
+ "DTLS-SRTP" (0x0002): DTLS-SRTP [IETF RFC 5764]
+
+**Default:** "None", unless provisioned otherwise
+
+**Defined in:** TerminationState
+
+**Characteristics:** Read/Write
+
+### 6.1.4 Key Lifetime Expiry Behaviour
+
+|                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Property name:</b>   | Key Lifetime Expiry Behaviour                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Property ID:</b>     | kleb (0x0004)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Description:</b>     | <p>This property indicates which actions should be taken upon the expiry of the encrypting master key. The MG triggers key lifetime expiry when it determines that it has used the SRTP master key for the maximal number of packets allowed (by default <math>2^{48}</math> SRTP and/or <math>2^{31}</math> secure RTCP (SRTCP) packets; this value can be lowered through key-management).</p> <p>See sections 6.6.3 and 9.2 of [IETF RFC 3711] for further information regarding master key lifetime expiry.</p>                                                                                                                                                          |
+| <b>Type:</b>            | Enumeration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Possible values:</b> | <p>"DROP" (0x0000): Do not close SRTP session, drop all packets. If the property <i>srtp/km</i> is set to DTLS-SRTP then the DTLS connection is kept open.</p> <p>"BYE" (0x0001): Close SRTP session, send SRTCP BYE. If the <i>srtp/km</i> property is set to DTLS-SRTP then the DTLS connection shall be closed with a fatal alert.</p> <p>"RENEW-KEYS" (0x0002): This value is only applicable if the <i>srtp/km</i> property is set to DTLS-SRTP. The related DTLS procedure is triggered in the MG to renew the DTLS master secret and derive new SRTP/SRTCP master keys. For DTLS version 1.2 or lower a renegotiation (term see [b-IETF tls-terms]) will be used.</p> |
+| <b>Default:</b>         | "DROP", unless provisioned otherwise                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Defined in:</b>      | LocalControl                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Characteristics:</b> | Read/Write                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+## 6.2 Events
+
+#### 6.2.1 Master Key Expiry
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Event name:</b>  | Master Key Expiry                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Event ID:</b>    | mke (0x0001)                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Description:</b> | <p>This event allows the MGC to be notified when the encrypting SRTP master key is about to expire (watermark threshold crossed) or has already expired. As the lifetime is media-stream specific, when multiple streams are defined on a termination, this event shall be notified on a specific stream only.</p> <p>NOTE – If the watermarks are set to 0, notification will be sent only upon master key expiration.</p> |
+
+#### 6.2.1.1 EventsDescriptor Parameters
+
+##### 6.2.1.1.1 SRTP Watermark
+
+|                        |                |
+|------------------------|----------------|
+| <b>Parameter name:</b> | SRTP Watermark |
+| <b>Parameter ID:</b>   | rtpw (0x0001)  |
+
+**Description:** The number of SRTP packets that the master key can still support when the event is first notified.
+
+**Type:** Double (Note)
+
+**Optional:** Yes
+
+**Possible values:** Any non-negative value.
+
+**Default:** 0, unless provisioned otherwise
+
+NOTE – The maximal master key lifetime is  $2^{48}$  SRTP packets and  $2^{31}$  SRTCP packets. Therefore, the SRTP Watermark and SRTCP Watermark parameters are of type Double and Unsigned Integer, respectively.
+
+##### 6.2.1.1.2 SRTCP Watermark
+
+**Parameter name:** SRTCP Watermark
+
+**Parameter ID:** rtpcw (0x0002)
+
+**Description:** The number of SRTCP packets that the master key can still support when the event is first notified.
+
+**Type:** Unsigned Integer (Note)
+
+**Optional:** Yes
+
+**Possible values:** Any non-negative value.
+
+**Default:** 0, unless provisioned otherwise
+
+NOTE – The maximal master key lifetime is  $2^{48}$  SRTP packets and  $2^{31}$  SRTCP packets. Therefore, the SRTP Watermark and SRTCP Watermark parameters are of type Double and Unsigned Integer, respectively.
+
+#### 6.2.1.2 ObservedEventsDescriptor Parameters
+
+##### 6.2.1.2.1 Key Expired
+
+**Parameter name:** Key Expired
+
+**Parameter ID:** ke (0x0001)
+
+**Description:** The parameter indicates whether, at the time of notification, the master key is still valid or has already expired.
+
+**Type:** Boolean
+
+**Optional:** Yes
+
+**Possible values:** True: The number of SRTP and SRTCP packets has met the master key lifetime, i.e., the key has already expired. False: The number of SRTP and SRTCP packets is still within the master key's lifetime.
+
+**Default:** False
+
+## 6.3 Signals
+
+None.
+
+## 6.4 Statistics
+
+#### 6.4.1 Number of Replayed Packets
+
+**Statistic name:** Number of Replayed Packets
+
+**Statistic ID:** replay (0x0001)
+
+**Description:** This statistic logs the number of received packets that have been judged to be replayed and discarded, according to section 3.3 of [IETF RFC 3711], since the instantiation of the statistic.
+
+**Type:** Double
+
+**Possible values:** Any non-negative value
+
+**Level:** Either
+
+### 6.4.2 Number of Authentication Failures
+
+**Statistic Name:** Number of Authentication Failures
+
+**Statistic ID:** authfail (0x0002)
+
+**Description:** This statistic logs the number of packets that have failed authentication and been discarded, according to clause 3.3 of [IETF RFC 3711], since the instantiation of the statistic.
+
+**Type:** Double
+
+**Possible values:** Any non-negative value
+
+**Level:** Either
+
+### 6.4.3 Sent SRTP Packets Protected by Master Key
+
+**Statistic Name:** Sent SRTP Packets Protected by Master Key
+
+**Statistic ID:** srpk (0x0003)
+
+**Description:** This statistic logs the number of sent SRTP packets that were protected by each of the current master key(s).
+
+**Type:** Sub-list of Double. Each element in the list corresponds to one of the encrypting master keys. The mapping between keys and list positions depends on the key management scheme employed.
+
+**Possible values:** Any non-negative value
+
+**Level:** Stream
+
+### 6.4.4 Sent SRTCP Packets Protected by Master Key
+
+**Statistic name:** Sent SRTCP Packets Protected by Master Key
+
+**Statistic ID:** scpk (0x0004)
+
+**Description:** This statistic logs the number of sent SRTCP packets that were protected by each of the current master key(s).
+
+**Type:** Sub-list of Unsigned Integer. Each element in the list corresponds to one of the encrypting master keys. The mapping between keys and list positions depends on the key management scheme employed.
+
+**Possible values:** Any non-negative value
+
+**Level:** Stream
+
+### 6.4.5 Received SRTP Packets Protected by Master Key
+
+**Statistic name:** Received SRTP Packets Protected by Master Key
+
+**Statistic ID:** rrpk (0x0005)
+
+|                         |                                                                                                                                                                                           |
+|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Description:</b>     | This statistic logs the number of received SRTP packets that were protected by each of the current master key(s).                                                                         |
+| <b>Type:</b>            | Sub-list of Double. Each element in the list corresponds to one of the decrypting master keys. The mapping between keys and list positions depends on the key management scheme employed. |
+| <b>Possible values:</b> | Any non-negative value                                                                                                                                                                    |
+| <b>Level:</b>           | Stream                                                                                                                                                                                    |
+
+### 6.4.6 Received SRTCP Packets Protected by Master Key
+
+|                         |                                                                                                                                                                                                     |
+|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Statistic name:</b>  | Received SRTCP Packets Protected by Master Key                                                                                                                                                      |
+| <b>Statistic ID:</b>    | rcpk (0x0006)                                                                                                                                                                                       |
+| <b>Description:</b>     | This statistic logs the number of received SRTCP packets that were protected by each of the current master key(s).                                                                                  |
+| <b>Type:</b>            | Sub-list of Unsigned Integer. Each element in the list corresponds to one of the decrypting master keys. The mapping between keys and list positions depends on the key management scheme employed. |
+| <b>Possible values:</b> | Any non-negative value                                                                                                                                                                              |
+| <b>Level:</b>           | Stream                                                                                                                                                                                              |
+
+## 6.5 Error codes
+
+None.
+
+## 6.6 Procedures
+
+### 6.6.1 Determining cryptographic capabilities
+
+The MGC can determine the cryptographic transforms that an MG supports for the "SDES" key management scheme by auditing the value of the *Supported Encryption Transforms (set)* and *Supported Authentication Transforms (sat)* properties. Usually, these properties are only available on the Root termination, and convey the cryptographic capabilities of the MG as a whole. However, it is possible that some use-cases will call for the support of these properties on non-Root terminations. One example would be a case where different terminations have different cryptographic capabilities. The *srtp/set* and *srtp/sat* properties are only applicable for *srtp/km* = "SDES". For *srtp/km* = "DTLS-SRTP" the [ITU-T H.248.93] (DTLS) *dtlsen/dssp* property is used.
+
+The *Supported Encryption Transforms* and *Supported Authentication Transforms* properties declare a value for the NULL cipher and the NULL authentication algorithm respectively. By including these values, a MG explicitly indicates that its policy allows the use of unencrypted and/or unauthenticated SRTP and SRTCP packets. Note that, in accordance with [IETF RFC 3711], SRTCP packets must be authenticated using a non-NULL algorithm, regardless of the declared support of the NULL authentication algorithm.
+
+To determine the cryptographic capability for the "DTLS-SRTP" key management scheme, the MGC may audit the *DTLS-SRTP protection profiles (dtlsen/dspp)* property from the *dtlsen* package in [ITU-T H.248.90].
+
+### 6.6.2 Key management
+
+The SRTP package does not define protocol elements for performing SRTP key management. Instead, the *Key Management Scheme (km)* property allows the MGC to indicate the use of one of several, already established, key management schemes.
+
+The two key management schemes supported by version 2 of the package include the use of SDP security descriptions (see [IETF RFC 4568]) in the Local and Remote Descriptors and the use of DTLS-SRTP. Further details about the adaptation of these security descriptions for use in ITU-T H.248 are provided in clauses 7 and 8.
+
+NOTE – Future versions of this package may allow the use of additional key management schemes, for example, SDP key management extensions (see [b-IETF RFC 4567]).
+
+By default, the value of the *Key Management Scheme* property is "None"; indicating that no key management is used, and therefore SRTP is not employed. This prevents an MGC that is unaware of this package from inadvertently "turning on" SRTP through the careless inclusion of SDP parameters in the Local and Remote Descriptors.
+
+### 6.6.3 Master key lifetime
+
+SRTP master keys have a limited lifetime, measured in the number of SRTP and SRTCP packets that may be protected using the same key. The *Master Key Expiry (mke)* event allows the MGC to be notified when the master key is close to being, or has already been exhausted. The MG notifies this event based on the expiry status of the key used to encrypt and authenticate sent packets. No notification is generated regarding the expiry of the decrypting master key used for handling received packets.
+
+The *SRTP Watermark (rtpw)* and *SRTCP Watermark (rtcpw)* event parameters allow the MGC to control how long before key exhaustion the *mke* event is first notified. If the value of the relevant watermark is different from 0, the MG shall generate the event when the master key has been used for (lifetime – *rtpw*) SRTP packets or (lifetime – *rtcpw*) SRTCP packets (whichever happens first). For example, if the key lifetime is  $2^{20}$ , and *rtpw* and *rtcpw* are both equal to  $2^{16}$ , the event will be notified after  $(2^{20} - 2^{16} = 983040)$  SRTP or SRTCP packets have been protected by that key.
+
+Regardless of the value of the *rtpw* and *rtcpw* parameters, the *Master Key Expiry* event shall be notified by the MG when the master key has fully expired and can no longer be used. The MGC can differentiate whether the master key has already expired or only the SRTP/SRTCP watermark was crossed through the *Key Expired* parameter.
+
+When several master keys can be used by the MG (only applicable if the *Key Management Scheme* property is set to "SDES"), the gateway shall generate the *mke* event only when all master keys are about to be, and/or have already been exhausted. For example, if three keys are used in series, each with a lifetime of *X* packets, the MG shall first send a notification only after the third (and last) key has been used for *X-rtpw* SRTP packets or *X-rtcpw* SRTCP packets. An additional notification will be sent when the third key has been fully exhausted.
+
+The *mke* event may be configured on a specific stream or on the complete termination. Configuring the *mke* event on a termination is equivalent to configuring it, with the same parameter values, on each of these termination's streams (other than streams that already have the event explicitly enabled). As different streams may exhaust the key at different times, an *mke* notification shall always be associated with a specific stream.
+
+#### 6.6.3.1 MG behaviour at key exhaustion
+
+The operations taken by the MG when the last encrypting master key is exhausted are controlled through the *Key Lifetime Expiry Behaviour (kleb)* property. Setting this property to "BYE" will cause the MG to send an SRTCP BYE packet, hence leaving the RTP session or closing it (if it is the session's sole sender) as soon as the master-key expires. If DTLS-SRTP has been used for the *Key Management Scheme* property, the MG shall enforce the closure of the DTLS connection as well by sending a fatal alert.
+
+NOTE – The MG must ensure that it is able to send the SRTCP BYE packet using a valid master key. This means that when *kleb* is set to "BYE", the encrypting master key will expire when it can still protect one additional SRTCP packet.
+
+If the *Key Management Scheme* property is set to "SDES" and if the MGC installs a new master key after the MG has sent an SRTCP BYE packet, the MG will rejoin the RTP session or create a new one (if it was closed). This, in turn, will have whatever effects such rejoining or creating a session entails. For example, the SRTP rollover counter (ROC) will be reset, and the MG may start using a new synchronization source (SSRC) value.
+
+If the MGC requests *srtp/kleb* = "RENEW-KEYS" and *tlscn/srsc* = "false" then an error should be reported.
+
+Regardless of the value of the *kleb* property, the MG shall neither receive nor send SRTP packets using an expired key (i.e., all such packets shall be discarded).
+
+The MG's behaviour at key-exhaustion is completely independent of the expiry notification, and remains the same regardless of whether the *Master Key Expiry* event is configured at the stream level, termination level, or not at all.
+
+### 6.6.4 Logging of security violations
+
+Once an SRTP stream is established on a MG, sent and received packets are processed according to section 3.3 of [IETF RFC 3711]. Received packets are authenticated and decrypted. During this process, received packets may be judged to have been replayed or may fail authentication and be discarded. In order to log these events, the MGC shall set the *Number of Replayed Packets* (*srtp/replay*) and the *Number of Authentication Failures* (*srtp/authfail*) statistics. The MGC may audit these statistics when it wishes to know the number of replayed packets and/or authentication failures detected. If the MGC requires notification of such events, it shall use the Statistic Conditional Reporting package (see [ITU-T H.248.47]) with an appropriate reporting threshold.
+
+# 7 Key management using SDP security descriptions
+
+The MGC indicates that SDP security descriptions will be used for key management by setting the value of the *Key Management Scheme* property to "SDES". Under this scheme, the MGC and MG negotiate a stream's SRTP parameter by placing a "crypto" SDP attribute in the Local and Remote Descriptors. The "crypto" attribute and its use for negotiating SRTP parameters is described in [IETF RFC 4568]. This clause provides additional details regarding the adaptation of those procedures for use with ITU-T H.248.
+
+Naturally, this scheme is only applicable when SDP is used for the Local and Remote Descriptors. If the binary encoding of the protocol is used, the "crypto" SDP attribute can be carried using the SDP equivalents of clause C.11 of [ITU-T H.248.1]. The MG shall use error code 473 (Conflicting Property Values) when the Local and Remote Descriptors cannot carry a "crypto" SDP attribute and the *Key Management Scheme* is set to "SDES".
+
+The Local Descriptor controls the SRTP parameters of the flow(s) sent by the MG. Similarly, the Remote Descriptor controls the SRTP parameters of the flow(s) received by the MG. A Local or Remote Descriptor indicates that the MG shall use SRTP to protect sent or received packets if both:
+
+- 1) the media description ("m=" line) uses an SRTP-based profile as the transport protocol (e.g., "RTP/secure audio-video profile (SAVP)" or "RTP/secure audio-video profile with feedback (SAVPF)"), and;
+- 2) the SDP contains one or more "crypto" attributes.
+
+If either of these conditions is not met, the MG shall not apply SRTP procedures to the packets. This Recommendation does not imply any special meaning to descriptors that match only one or none of these conditions.
+
+The MG shall use error code 474 (Invalid SDP Syntax) if the above procedures indicate that the MG shall protect flows using SRTP but the "crypto" attribute does not match the SRTP-specific format, as described in section 6 of [IETF RFC 4568].
+
+In the following clauses, words appearing in `fixed-font` are references to specific augmented Backus-Naur form (ABNF) rules from section 9 of [IETF RFC 4568].
+
+## 7.1 Overspecification of SRTP parameters and multiple keys
+
+There are two possible ways for the MGC to specify more than one set of SRTP parameters within one SDP group:
+
+- 1) overspecify the "crypto" attribute by including more than one such attribute in the SDP group;
+- 2) include more than one `key-param` in one "crypto" attribute.
+
+These two methods can be combined (i.e., include several "crypto" attributes in the SDP group, each including more than one `key-param`).
+
+According to clause 7.1.5 of [ITU-T H.248.1], the behaviour of the MG when the "crypto" attribute is overspecified depends on the value of the *ReserveValue* property. If this value is false, the MG shall choose only one of the included "crypto" attributes and remove all others from the SDP group. Conversely, if *ReserveValue* is true, the MG shall reserve enough resources to support as many of the included "crypto" attributes as it can, and keep all those supported attributes in the descriptor.
+
+A Remote Descriptor with more than one "crypto" attribute and/or more than one `key-param` within a "crypto" attribute indicates that the MG shall be prepared to accept packets protected using any of the master keys contained in the Descriptor. To achieve this, each key shall include a master key identifier (MKI) value and that value shall be unique. Any command resulting in one MKI value being mapped to more than one master key shall be rejected using error 473 (Conflicting Property Values).
+
+A Local Descriptor with more than one "crypto" attribute indicates that the MG has reserved resources for all these attributes; however, only the first "crypto" attribute is used by the MG for protecting sent packets. As the MG does not use any of the other "crypto" attributes, different attributes may include identical MKI values (or not include MKI at all). Such configurations are often transient and exist while the session is being set up. An example for such a scenario is provided in item 1 of clause I.1.
+
+NOTE 1 – Mandating the use of the first "crypto" attribute in the Local Descriptor allows re-keying an existing session. The MGC would:
+
+- a) overspecify the Local Descriptor of the sender, adding a second, new "crypto" attribute;
+- b) overspecify the Remote Descriptor of the receiver, adding the new "crypto" attribute;
+- c) remove the first "crypto" attribute from the sender's Local Descriptor, leaving only the new attribute there.
+
+A "crypto" attribute with more than one `key-param` appearing first in the Local Descriptor indicates that the different `key-param` sub-fields shall be used sequentially. The MG shall use the first `key-param` whose master key has not yet expired for protecting sent packets. Once a master key expires (due to the number of either SRTP or SRTCP packets sent), the MG shall start using the next `key-param` in the attribute. As, over the course time, all `key-param` sub-fields might be used, each shall include a MKI value and that value shall be unique.
+
+NOTE 2 – The above procedures allow for the "automatic" re-keying of a stream upon key exhaustion, without the need for additional signalling messages.
+
+## 7.2 Wildcarding of SRTP parameters
+
+In addition to overspecification, many sub-fields of the "crypto" attribute may be wildcarded using the CHOOSE ("\$") wildcard. When a sub-field is wildcarded, the MG shall choose a value for it based on the MG capabilities and local configuration. The exact procedures for doing so are outside the scope of this Recommendation.
+
+Table 1 summarizes the guidelines for the sub-fields that may be wildcarded. Sub-fields that do not appear in the table cannot be wildcarded.
+
+**Table 1 – Wildcarding of SDP security descriptions**
+
+| Sub-Field    | Guidelines                                                                                                                                                               |
+|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| crypto-suite | Wildcarding this sub-field mandates that key-salt is also wildcarded, as the MGC cannot know in advance the required key length.                                         |
+| key-info     | Each part of key-info is wildcarded separately                                                                                                                           |
+| key-salt     | Can be wildcarded.<br>It is impossible to wildcard only the key or the salt.                                                                                             |
+| lifetime     | Can be wildcarded.                                                                                                                                                       |
+| mki          | Only mki-value can be wildcarded (i.e., mki-length cannot).<br>The MG shall choose the mki-value so that it is different from any other MKI appearing in the descriptor. |
+| kdr          | Can be wildcarded, using the form "KDR=\$"                                                                                                                               |
+| fec-order    | Can be wildcarded, using the form "FEC_ORDER=\$"                                                                                                                         |
+| fec-key      | The key-params part of the sub-field can be wildcarded, using the procedures for key-info above.                                                                         |
+| wsh          | Can be wildcarded, using the form "WSH=\$"                                                                                                                               |
+
+The MGC may combine overspecification and wildcarding, i.e., include in a descriptor multiple "crypto" attributes, where some of the attribute's subfields contain the CHOOSE wildcard.
+
+## 7.3 Interoperability with offer/answer-based implementations
+
+Under the SDP offer/answer procedures of [IETF RFC 4568], some of the SRTP parameters are considered "negotiated", meaning that the same parameter value must be used for both the sent and received RTP packets. The list of these parameters is:
+
+- 1) crypto-suite
+- 2) UNENCRYPTED\_SRTP
+- 3) UNENCRYPTED\_SRTP
+- 4) UNAUTHENTICATED\_SRTP
+
+To increase interoperability with such offer/answer based implementations, whenever the MG needs to choose a value for one of those parameters (i.e., when overspecification or wildcarding is employed), it shall ensure that the same value is used in both the Local and Remote Descriptors. Using different values in the Local and Remote Descriptors for a "negotiated" parameter is only allowed when the request sent by the MGC explicitly prevents the use of the same value.
+
+## 7.4 SDES and SRTP cryptographic contexts
+
+With regard to the initialization and maintenance of SRTP crypto contexts, the MGC and MG shall follow the procedures of sections 6.4 and 6.5 of [IETF RFC 4568]. In addition, the MGC and MG shall follow the procedures of section 7 of [IETF RFC 4568], adapted to ITU-T H.248's use of SDP (which is different from the offer/answer model covered by that document). The following list highlights the points of those clauses that have the most significant impact on the MGC's and MG's behaviour.
+
+- 1) The ROC of any newly created crypto context shall be initialized to zero.
+
+- 2) The MG should choose an initial sequence number in the range of  $0..2^{15}-1$  for any RTP stream associated with a newly created SRTP crypto context.
+- 3) The MG shall choose different SSRC values for different RTP streams sharing the same master key.
+- 4) The MG shall remove crypto-contexts using the same procedures as for SSRC removal from the member table, as described in [IETF RFC 3550].
+- 5) If the MGC has wildcarded a master key, the MG shall choose a master key different from all other master keys it is currently using. In particular, a master key chosen for the Local or Remote Descriptor shall be different from any other master key appearing in the Local or Remote Descriptor of the same stream.
+- 6) A command that changes the first "crypto" SDP attribute in the Local or Remote Descriptor shall create a new SRTP crypto context, which will be used by the MG for sending or receiving packets respectively. In particular, such a command shall reset the relevant ROC counter (Note 1).
+
+A change of a master key that does not involve a new "crypto" attribute (e.g., when multiple key-param sub-fields exist) shall not cause a new crypto context to be created, and the existing context shall be used (Note 2).
+
+NOTE 1 – A change of the first "crypto" attribute is considered as equivalent to sending a new master-key in a SDP offer/answer procedure. Therefore, the MG shall follow the requirements of section 7.1.4 of [IETF RFC 4568]:
+
+*"... the offerer MUST include a new master key with the offer (and in so doing, it will be creating a new crypto context where the ROC is set to zero)."*
+
+NOTE 2 – A change of the master-key that does not involve a new "crypto" attribute is equivalent to re-keying the SRTP session without using an offer/answer exchange. Therefore the MG shall follow the requirements of section 3.3.1 of [IETF RFC 3711]:
+
+*"After a re-keying occurs (changing to a new master key), the rollover counter always maintains its sequence of values, i.e., it MUST NOT be reset to zero."*
+
+- 7) The MGC should apply a new "crypto" SDP attribute to the Local Descriptor (and hence create a new local crypto context) whenever it changes the address or port used in that Descriptor.
+
+## 7.5 Mapping of master keys for sent packets and received packets statistics
+
+When SDP security descriptions are used for key management, each entry in the *Sent SRTP Packets Protected by Master Key (srpk)* and *Sent SRTCP Packets Protected by Master Key (scpk)* shall correspond to one of the master keys appearing in the first "crypto" SDP attribute of the Local Descriptor. The order of entries in the statistics shall match the order of keys in the "crypto" attribute.
+
+In a similar manner, each entry in the *Received SRTP Packets Protected by Master Key (rrpk)* and *Received SRTCP Packets Protected by Master Key (rcpk)* statistics shall correspond to one of the master keys appearing in the first "crypto" attribute of the Remote Descriptor.
+
+Changing the first "crypto" attribute of the Local or Remote Descriptors will cause the MG to discard the appropriate statistics values, and to start maintaining new ones.
+
+# 8 Key management using DTLS-SRTP
+
+NOTE – The interworking between SDES and DTLS-SRTP is for further study.
+
+The DTLS-SRTP [IETF RFC 5764] key management scheme exchanges the peers' certificates via the signalling path and then establishes a DTLS connection on the bearer path. The DTLS master secret is used to derive the SRTP master key. SRTP packets are then exchanged between the endpoints on the same transport protocol connection as used for the DTLS connection.
+
+The packages from [ITU-T H.248.90] (TLS) and [ITU-T H.248.93] (DTLS) are used for the establishment of the DTLS connection.
+
+## 8.1 Key management indication
+
+The MGC indicates the use of DTLS-SRTP key management by setting the *Key Management Scheme (srtp/km)* property to the value "DTLS-SRTP".
+
+Using this scheme a DTLS-SRTP connection is setup which is controlled by two sets of properties, one set is related to DTLS and the other is related to SRTP. Both sets of properties are orthogonal.
+
+The DTLS related properties and procedures are covered by [ITU-T H.248.90] (TLS) and by [ITU-T H.248.93] (DTLS).
+
+This clause provides additional details which are specific for the DTLS-SRTP key management scheme.
+
+## 8.2 Bearer plane connection for "DTLS-SRTP"
+
+The MG will establish the DTLS-SRTP connection based on the following properties:
+
+- *TLS Domain Profile Identifier (ITU-T H.248.90: tlscn/dpid)*  
+This property identifies the (D)TLS profile to be used to setup the DTLS connection.
+- *TLS Versions (ITU-T H.248.90: tlscn/tlsv)*  
+This property defines the set of DTLS protocol versions allowed establish the DTLS connection.
+- *Cipher Suites (ITU-T H.248.90: tlscn/cs)*  
+This property defines the set of ciphersuites used to negotiate a DTLS session.
+- *Compression Methods (ITU-T H.248.90: tlscn/cm)*  
+This property defines the set of compression methods to be used for the negotiation with the remote DTLS endpoint.  
+  
+NOTE – DTLS-SRTP [IETF RFC 5764] itself does not consider any application data to be protected and therefore potentially compressed by the DTLS stack. Nevertheless there might be use cases which will use DTLS-SRTP for the SRTP key management scheme and additionally for the protection of application data (e.g. WebRTC data channel).
+- *Client Authentication Required (ITU-T H.248.90: tlscn/car)*  
+This property indicates that – if the MG is acting as a DTLS-server – authentication of the client is requested.
+- *DTLS-SRTP protection profiles (ITU-T H.248.93: dtlcns/dspp)*  
+This property indicates the set of SRTP cypto suites that will be used for the negotiation with the peer endpoint.
+- *Master Key Identifier usage (ITU-T H.248.93: dtlcns/mkiu)*  
+This property indicates the use or not use of the DTLS-SRTP specific Master Key Identifier (MKI) (according to [IETF RFC 5764], clause 4.1.3 "srtp\_mki value").
+
+Prior to the establishment of the DTLS connection the SDP "a=fingerprint:" attribute (according to [IETF RFC 4572]) will be used to ensure the integrity of the self-signed certificates of both DTLS connection endpoints. The detailed procedures on how the fingerprints are exchanged between the MGC and the MG are covered in [ITU-T H.248.90] (TLS).
+
+Based on the events of the *TLS basic session control package (tlsbsc)* [ITU-T H.248.90] (TLS) the MG will start the setup of a DTLS connection.
+
+If the MG takes the DTLS client role, a DTLS handshake is initiated and the extension "use\_srtp" [IETF RFC 5764] is included into the "ClientHello" message. This extension will be used according
+
+to the value of the properties *DTLS-SRTP protection profiles (dtlcns/dspp)* and *Master Key Identifier usage (dtlcns/mkiu)*.
+
+If the MG takes the DTLS server role the SRTP crypto suite is negotiated according to the received "use\_srtp" extension from the "ClientHello" and the MG's property *DTLS-SRTP protection profiles (dtlcns/dspp)*. In case the received "ClientHello" does not include the "use\_srtp" extension the DTLS connection is terminated and error code 473 (Conflicting Property Values) is reported to the MGC.
+
+The handshake to negotiate a DTLS session follows the procedures of [IETF RFC 5246]. Once a DTLS session is negotiated and the DTLS master secret is determined the SRTP master keys are derived according to section 4.2 of [IETF RFC 5764]. From this point in time SRTP/SRTCP packets may be exchanged between the MG and its peer connection endpoint.
+
+### 8.2.1 Protocol stack and DTLS usage
+
+For further study.
+
+### 8.2.2 Reuse of DTLS connection by other applications
+
+DTLS-SRTP as specified by [IETF RFC 5764] does not consider the protection of DTLS application data. The DTLS connection is used as a key exchange mechanism for SRTP and once the SRTP master key is determined the video and/or audio flow is protected by SRTP.
+
+However there may be the requirement to send different audio, video or data streams secured over the same transport connection (e.g., SRTP and WebRTC Data Channel using the same DTLS connection). In such a case the data stream will correspond to the DTLS application and the data stream packets will be secured by the DTLS record layer.
+
+### 8.2.3 Lifetime of DTLS session and DTLS connection
+
+For a DTLS session used to derive the SRTP master key no special rule applies for its lifetime. Thus the session used might be a transient DTLS session or a semi-permanent DTLS session (i.e., resumable).
+
+The lifetime of the DTLS connection is coupled as follows to the lifetime of the (SRTP)-connection: If an event occurs which leads to the termination of the DTLS connection then the related (SRTP) and (SRTCP) connections must be terminated as well (Note 2).
+
+NOTE 1 – An SRTCP-BYE is not sent in this case. The rationale behind this is that any usage of the DTLS master secret and respectively the derived SRTP master key is not allowed anymore.
+
+NOTE 2 – See [IETF RFC 5246] (TLS version 1.2), section 7.2.2 on error alerts: "... *Servers and clients MUST forget any session-identifiers, keys, and secrets associated with a failed connection. ...*". The SRTP master key represents a "secret associated with a failed connection", hence the conclusion that the DTLS fatal alert will lead to a termination of the SRTP connection.
+
+### 8.2.4 Lifetime of DTLS master secret and SRTP master key
+
+In case the DTLS connection is reused by another application (e.g., WebRTC Data Channel) application data records as well as SRTP packets might be sent in parallel using the same transport address. This potentially may lead either to the expiration of the DTLS master secret (the connection state sequence number may not exceed  $2^{64}-1$ ) or to the expiration of the SRTP master key (at maximum  $2^{48}$  SRTP or  $2^{31}$  SRTCP packets may be sent using the same master key).
+
+NOTE 1 – [ITU-T H.248.90] does not define an MG-autonomous renegotiation in case a watermark (equal to a number of packets) is reached. Only a renegotiation period is defined, which might not be appropriate. This is for further study.
+
+In case the values as defined by the *SRTP Watermark (srtp/rtpw)* property or by the *SRTCP Watermark (srtp/rtcpw)* property are crossed the MG's behavior depends on the *Key Lifetime Expiry Behaviour (srtp/kleb)* property:
+
+- *srtp/kleb* = "DROP": All SRTP/SRTCP packets are dropped. DTLS application data sent or received over the DTLS record layer are not impacted.
+- *srtp/kleb* = "BYE": Close the (SRTP)-connection and send an SRTCP-BYE. DTLS application data sent or received over the DTLS record layer are not impacted. E.g., for WebRTC this allows to close the audio/video session but to continue the data transfer.
+- *srtp/kleb* = "RENEW-KEYS": This will trigger a renegotiation. A DTLS handshake will be initiated to determine a new DTLS master secret and derive a new SRTP master key from it. During the renegotiation SRTP/SRTCP packets may still be sent (if the watermarks are greater than zero) as well as DTLS application data using the old keying material. Once the handshake is completed (Finished message sent and received) the new keying material will be used for SRTP/SRTCP packets as well as for DTLS application data.
+
+NOTE 2 – Future (D)TLS versions might drop the support for renegotiation but may provide another procedure for renewing the (D)TLS master secret.
+
+## 8.3 Multi key management operation
+
+For further study.
+
+# 9 Security considerations
+
+## 9.1 Relation to key management scheme "SDES"
+
+SDP security descriptions do not provide any inherent authentication or encryption of the SRTP parameters carried in the Local and Remote Descriptors. Therefore, use of this key-management scheme is only appropriate when the ITU-T H.248 channel is secured through some other means (e.g., IP security (IPSec)).
+
+## 9.2 Relation to key management scheme "DTLS-SRTP"
+
+For the "DTLS-SRTP" key management scheme the security considerations as described by the related IETF RFCs [IETF RFC 5246], [IETF RFC 5764], [IETF RFC 6347] apply. An additional aspect for the establishment of a DTLS connection is the integrity protection of the self-signed certificates. Fingerprint hashes are calculated for the certificates and are communicated via out-of-band means (SDP "a=fingerprint" attribute). This attribute must be protected against tampering, thus the communication channel used to exchange the fingerprints must be integrity protected.
+
+# Appendix I
+
+## Example call flows for key management scheme "SDES"
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## I.1 Initial session setup using SDP security descriptions
+
+In the following examples, tokens such as <key1> and <key2> indicate sequences of 240 bits, encoded as 40 base64 characters.
+
+- 1) The MGC ADDs a new, SRTP-enabled, termination to MG1.
+
+The *Key Management Scheme* is set to SDES, the transport protocol is RTP/SAVP and a "crypto" attribute appear in the Local Descriptor, indicating that the packets sent by MG1 should be protected using SRTP.
+
+The Local Descriptor contains two "crypto" attributes and *ReserveValue* is true, meaning that MG1 should reserve resources for both, but only use the first. Note that the MKI value "1" is shared between the two attributes, which is allowed.
+
+```
+MGC to MG1:  
+MEGACO/3 [123.123.123.4]:55555  
+Transaction = 10003 {  
+    Context = $ {  
+        Add = $ {  
+            Media {  
+                TerminationState {  
+                    srtp/km = SDES  
+                },  
+                Stream = 1 {  
+                    LocalControl {  
+                        Mode = RecvOnly,  
+                        ReservedValue = ON  
+                    },  
+                    Local {  
+v=0  
+c=IN IP4 $  
+m=audio $ RTP/SAVP 4  
+a=ptime:30  
+a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:$|2^20|1:4;inline:$|2^20|2:4  
+a=crypto:2 F8_128_HMAC_SHA1_80 inline:$|2|1:4  
+                    }  
+                }  
+            }  
+        }  
+    }  
+}
+```
+
+- 2) MG1 returns the key-salt sub-fields it has chosen as well as the lifetime of the AES\_F8 key (these sub-fields were wildcarded in the request). The <key1>, <key2>, <key3> values must all be different from one another.
+
+```
+MG1 to MGC  
+MEGACO/3 [124.124.124.222]:55555  
+Reply = 10003 {  
+    Context = 2000 {  
+        Add = A4445 {  
+            Media {  
+                Stream = 1 {  
+                    Local {
+```
+
+
+
+```
+
+            Events = 1234 {
+                srtp/mke { rtpw=10000, rtpcw=50 }
+            }
+        }
+    }
+}
+
+```
+
+- 4) MG2 chooses the first "crypto" attribute in the Remote Descriptor. In accordance with clause 7.3, it chooses for the Local Descriptor the same `crypto-suite` as the one now used in the Remote Descriptor.
+
+```
+
+MG2 to MGC:
+MEGACO/3 [125.125.125.111]:55555
+Reply = 50003 {
+    Context = 5000 {
+        Add = A5556{
+            Media {
+                Stream = 1 {
+                    Local {
+v=0
+o=- 7736844526 7736842807 IN IP4 125.125.125.111
+s=-
+t=0 0
+c=IN IP4 125.125.125.111
+m=audio 1111 RTP/SAVP 4
+a=ptime:30
+a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:<key4>|2^20|1:4
+                    },
+                    Remote {
+v=0
+o=- 7736849782 7736858112 IN IP4 125.125.125.111
+s=-
+t=0 0
+c=IN IP4 124.124.124.222
+m=audio 2222 RTP/SAVP 4
+a=ptime:30
+a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:<key1>|2^20|1:4;inline:<key2>|2^20|2:4
+                    }
+                }
+            }
+        }
+    }
+}
+
+```
+
+- 5) The MGC updates MG1's Local and Remote Descriptors according to the choices made by MG2. The *Master Key Expiry* event is configured on the termination, using the same parameter values as the ones used at 3).
+
+```
+
+MGC to MG1:
+MEGACO/3 [123.123.123.4]:55555
+Transaction = 60006 {
+    Context = 2000 {
+        Modify = A4445 {
+            Media {
+                Stream = 1 {
+                    LocalControl {
+                        Mode = SendRecv
+                    },
+                    Local {
+v=0
+c=IN IP4 124.124.124.222
+m=audio 2222 RTP/SAVP 4
+
+```
+
+```
+
+a=ptime:30
+a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:<key1>|2^20|1:4;inline:<key2>|2^20|2:4
+        },
+        Remote {
+v=0
+c=IN IP4 125.125.125.111
+m=audio 1111 RTP/SAVP 4
+a=ptime:30
+a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:<key4>|2^20|1:4
+        },
+    }
+},
+Events = 5678 {
+    srtp/mke { rtpw=10000, rtpcw=50 }
+}
+}
+}
+}
+
+```
+
+###### **6) MG1 acknowledges the MODIFY request.**
+
+```
+
+MG1 to MGC
+MEGACO/3 [124.124.124.222]:55555
+Reply = 60006 {
+    Context = 2000 {
+        Modify = A4445
+    }
+}
+
+```
+
+## **I.2 MG1's key is about to expire**
+
+- 1) MG1 sends a *Master Key Expiry* NOTIFY request to the MGC. The *Key Expired* parameter is missing and its default value (false) is used, indicating that the key has not yet expired, but that either the SRTP or SRTCP watermarks has been crossed.
+
+```
+
+MG1 to MGC:
+MEGACO/3 [124.124.124.222]:55555
+Transaction = 76819 {
+    Context = 2000 {
+        Notify = A4445 {
+            ObservedEvents = 5678 {
+                20091201T07450122:srtp/mke ;ke is false by default
+            }
+        }
+    }
+}
+
+```
+
+- 2) The MGC acknowledges the NOTIFY request.
+
+```
+
+MGC to MG1:
+MEGACO/3 [123.123.123.4]:55555
+Transaction = 76819 {
+    Context = 2000 {
+        Notify = A4445
+    }
+}
+
+```
+
+## **I.3 Auditing SRTP capabilities**
+
+- 1) The MGC audits all SRTP properties on MG1's Root termination.
+
+```
+
+MGC to MG1
+MEGACO/3 [123.123.123.4]:55555
+
+```
+
+```
+
+Transaction = 87395 {
+  Context = - {
+    AuditValue = Root {
+      Audit { TerminationState { srtp/* } }
+    }
+  }
+}
+
+```
+
+- 2) MG1 answers with the lists of encryption and authentication transforms that it supports. These lists are missing the NULL value, meaning that MG1's security policy does not allow the use of unencrypted or unauthenticated SRTP packets.
+
+```
+
+MG1 to MGC
+MEGACO/3 [124.124.124.222]:55555
+Reply = 87395 {
+  Context = - {
+    AuditValue = Root {
+      TerminationState { srtp/set=[AES_CM_128, AES_CM_192, AES_CM_256],
+                        srtp/sat=[HMAC_SHA1_32, HMAC_SHA1_80]
+      }
+    }
+  }
+}
+
+```
+
+## I.4 Auditing of SRTP statistics
+
+- 1) The MGC audits the SRTP statistics of stream 1 on MG1:
+
+```
+
+MGC to MG1:
+MEGACO/3 [123.123.123.4]:2944
+Transaction = 91903 {
+  Context = 2000 {
+    AuditValue = A4445 {
+      Audit {
+        Media {
+          Stream = 1 {
+            Statistics { srtp/* }
+          }
+        }
+      }
+    }
+  }
+}
+
+```
+
+- 2) MG1 returns the current SRTP statistics. According to the values returned, MG1 has discarded seven (7) packets due to authentication failure and considered three (3) packets as replays. In addition (assuming that MG1 is using the keys negotiated in item 1 of clause I.1) the MG has protected 2<sup>20</sup> SRTP packets and 4'086 SRTCP packets using <key1>, and 37'112 SRTP packets and 941 SRTCP packets using <key2>. It received 519'733 SRTP packets and 2080 SRTCP packets protected by <key4>.
+
+```
+
+MG1 to MGC:
+MEGACO/3 [124.124.124.222]:55555
+Reply = 91903 {
+  Context = 2000 {
+    AuditValue = A4445 {
+      Media {
+        Stream = 1 {
+          Statistics {
+            srtp/replay = 3,
+            srtp/authfail = 7,
+          }
+        }
+      }
+    }
+  }
+}
+
+```
+
+```
+        srtp/srpk = [1048576, 37112],  
+        srtp/scpk = [4086, 941],  
+        srtp/rrpk = 519733,  
+        srtp/rcpk = 2080  
+    }  
+}  
+}  
+}  
+}  
+}
+```
+
+# Appendix II
+
+## Sample use-cases of SRTP bearer encryption
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This appendix illustrates some network level scenarios that employ SRTP bearer encryption.
+
+## II.1 Use-case #1: ITU-T H.248 MG for peering IP and circuit-switched networks
+
+Figure II.1 illustrates an ITU-T H.248 connection model of (IP, physical). This model is often employed for peering a circuit-switched and an IP network at a residential, access or trunking MG. The RTP session is terminated by the ITU-T H.248 MG. The MG is consequently behaving as a RTP end system (see section 3 of [IETF RFC 3550]).
+
+Any application of SRTP as a means for media security implies the termination of the SRTP session by the corresponding ITU-T H.248 stream.
+
+![Diagram of ITU-T H.248 MG for peering IP and circuit-switched networks](24c9e038a791677ed33100667b64f7e6_img.jpg)
+
+The diagram illustrates a network architecture for peering IP and circuit-switched networks. On the left, an 'SRTP end system' is shown with a protocol stack: RTP | RTCP, SRTP | SRTCP (highlighted in blue), UDP, IP, L2, and L1. This system is connected to an 'IP network' cloud via an 'IP bearer connection'. A dashed blue line labeled 'SRTP session' connects the SRTP end system to the 'ITU-T H.248 IP-physical media gateway'. Above the gateway, a 'Media gateway controller' is connected to the SRTP end system via a red arrow labeled 'Key exchange for secure RTP' and to the gateway via a red arrow labeled 'ITU-T H.248 control'. The 'ITU-T H.248 IP-physical media gateway' is highlighted with a yellow border and contains two internal components: an 'SRTP end system' (with the same protocol stack as the first one) and a '(e.g., TDM DS0 endpoint)'. The SRTP end system within the gateway is connected to a 'Circuit-switched network (e.g., PSTN/ISDN)' cloud via a 'Circuit-switched bearer connection'. Below the gateway, the text 'RTP topology: "RTP end system"' is present. In the bottom right corner, the text 'H.248.77(10)\_FII.1' is visible.
+
+Diagram of ITU-T H.248 MG for peering IP and circuit-switched networks
+
+Figure II.1 – Use-case #1: SRTP to circuit-switched ITU-T H.248 MG
+
+## II.2 Use-case #2: ITU-T H.248 MG for peering IP networks
+
+ITU-T H.248 IP-IP MGs are widely used as, e.g., border routers, border gateways, policy enforcement points, firewalls with session-dependent filter rules, network address translation (NAT) devices, media transcoders, etc.
+
+Figure II.2 outlines a scenario, where such a gateway is located between two IP domains: one domain without any media security and another domain using SRTP encrypted media. The ITU-T H.248 MG behaves as two, back-to-back RTP end systems due to the termination of SRTP in one ITU-T H.248 stream.
+
+![Diagram of Use-case #2: SRTP to RTP ITU-T H.248 MG. It shows an SRTP end system on the left connected via an IP network and IP bearer connection to an ITU-T H.248 IP-IP media gateway. The media gateway contains an SRTP end system and an RTP end system. The SRTP end system inside the gateway is connected to the RTP end system via an SRTP session. The RTP end system is connected via an IP network and IP bearer connection to another RTP end system on the right. Control signals from a Media gateway controller (Key exchange for secure RTP and ITU-T H.248 control) are shown. The RTP topology is labeled 'Back-to-back RTP end systems'.](c494cd874a082a97b50b3c4d3938f467_img.jpg)
+
+The diagram illustrates the network architecture for Use-case #2. On the left, an SRTP end system is shown with a protocol stack: RTP | RTCP, SRTP | SRTCP, UDP, IP, L2, and L1. It is connected to an IP network, which is further connected via an IP bearer connection to the ITU-T H.248 IP-IP media gateway. Inside the media gateway, there are two end systems: an SRTP end system (with the same stack as the first one) and an RTP end system (with a stack: RTP | RTCP, UDP, IP, L2, L1). An SRTP session is established between the SRTP end system and the RTP end system within the gateway. The RTP end system is then connected to another IP network, which is connected via an IP bearer connection to a final RTP end system on the right. This final RTP end system has the same stack as the one in the gateway. A Media gateway controller is shown at the top, with arrows indicating 'Key exchange for secure RTP' to the first SRTP end system and 'ITU-T H.248 control' to the media gateway. Below the gateway, the text 'RTP topology: "Back-to-back RTP end systems"' is present. The diagram is labeled 'H.248.77(10)\_FII.2' in the bottom right corner.
+
+Diagram of Use-case #2: SRTP to RTP ITU-T H.248 MG. It shows an SRTP end system on the left connected via an IP network and IP bearer connection to an ITU-T H.248 IP-IP media gateway. The media gateway contains an SRTP end system and an RTP end system. The SRTP end system inside the gateway is connected to the RTP end system via an SRTP session. The RTP end system is connected via an IP network and IP bearer connection to another RTP end system on the right. Control signals from a Media gateway controller (Key exchange for secure RTP and ITU-T H.248 control) are shown. The RTP topology is labeled 'Back-to-back RTP end systems'.
+
+**Figure II.2 – Use-case #2: SRTP to RTP ITU-T H.248 MG**
+
+## II.3 Use-case #3: Transparent SRTP forwarding
+
+It is possible for an MG to transparently forward SRTP packets, treating them as unprotected UDP or RTP packets. Such a scenario is illustrated in Figure II.3.
+
+As stated in clause 1, this use-case is outside the scope of this Recommendation. It is presented here for the sake of completeness.
+
+![Diagram of ITU-T H.248 MG with transparent SRTP forwarding. It shows two RTP end systems connected via an IP network to an ITU-T H.248 IP-IP media gateway. The media gateway contains two UDP endpoints. An SRTP session is established between the end systems, passing through the media gateway. A Media gateway controller is connected to the media gateway via ITU-T H.248 control and performs key exchange for secure RTP. The RTP topology is transparent forwarding. The diagram includes protocol stacks for RTP, SRTP, UDP, IP, L2, and L1 for the end systems, and UDP, IP, L2, and L1 for the media gateway endpoints.](692541e65db4dc852988ce77ebb60ce5_img.jpg)
+
+The diagram illustrates the architecture for Use-case #3: ITU-T H.248 MG with transparent SRTP forwarding. At the top, a **Media gateway controller** is connected to the central **ITU-T H.248 IP-IP media gateway** via an **ITU-T H.248 control** line. A red line labeled **Key exchange for secure RTP** also connects the controller to the media gateway. The media gateway is situated within an **IP network** and contains two **UDP endpoint** blocks. On either side of the media gateway, an **RTP end system** is connected via an **IP bearer connection**. Each RTP end system has a protocol stack consisting of **RTP | RTCP**, **SRTP | SRTCP** (highlighted in blue), **UDP**, **IP**, **L2**, and **L1**. The media gateway's UDP endpoints have a stack of **UDP**, **IP**, **L2**, and **L1**. A dashed blue line represents the **SRTP session** between the two end systems, passing through the media gateway. Below the media gateway, the text **RTP topology: transparent forwarding** is shown. At the bottom, a long dashed line with circles at each end represents the **End-to-end RTP session** between the two RTP end systems.
+
+Diagram of ITU-T H.248 MG with transparent SRTP forwarding. It shows two RTP end systems connected via an IP network to an ITU-T H.248 IP-IP media gateway. The media gateway contains two UDP endpoints. An SRTP session is established between the end systems, passing through the media gateway. A Media gateway controller is connected to the media gateway via ITU-T H.248 control and performs key exchange for secure RTP. The RTP topology is transparent forwarding. The diagram includes protocol stacks for RTP, SRTP, UDP, IP, L2, and L1 for the end systems, and UDP, IP, L2, and L1 for the media gateway endpoints.
+
+NOTE – The ITU-T H.248 MG may provide a local NAPT function, i.e., be media-agnostic, but transport-protocol aware (due to UDP checksum updates).
+
+H.248.77(10)\_FII.3
+
+**Figure II.3 – Use-case #3: ITU-T H.248 MG with transparent SRTP forwarding**
+
+# Bibliography
+
+- [b-ITU-T H.248.95] Recommendation ITU-T H.248.95 (2015), *Gateway control protocol: ITU-T H.248 support for RTP multiplexing*.
+- [b-IETF RFC 3264] IETF RFC 3264 (2002), *An Offer/Answer Model with Session Description Protocol (SDP)*.
+- [b-IETF RFC 4567] IETF RFC 4567 (2006), *Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)*.
+- [b-IETF RFC 5479] IETF RFC 5479 (2009), *Requirements and Analysis of Media Security Management Protocols*.
+- [b-IETF RFC 5763] IETF RFC 5763 (2010), *Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS)*.
+- [b-IETF RFC 7202] IETF RFC 7202 (2014), *Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution*.
+- [b-IETF RFC 7656] IETF RFC 7656 (2015), *A Taxonomy of Grouping Semantics and Mechanisms for Real-Time Transport Protocol (RTP) Sources*.
+- [b-IETF tls-terms] IETF draft-guballa-tls-terminology-05 (2017), *Terminology related to TLS and DTLS*.  
+<<https://datatracker.ietf.org/doc/draft-guballa-tls-terminology/>>
+
+
+
+
+
+## **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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.248.8-201303-I_PDF-E/raw.md b/marked/H/T-REC-H.248.8-201303-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..90d16dd5f0eea8296857d1c4c54247240a48a0fb
--- /dev/null
+++ b/marked/H/T-REC-H.248.8-201303-I_PDF-E/raw.md
@@ -0,0 +1,1198 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.8**
+
+(03/2013)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+# --- **Gateway control protocol: Error code and service change reason description**
+
+Recommendation ITU-T H.248.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        |
+| <b>Communication procedures</b>                                               | <b>H.240–H.259</b> |
+| 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.8
+
+# Gateway control protocol: Error code and service change reason description
+
+## Summary
+
+Recommendation ITU-T H.248.8 defines the service change reasons that are used in the core ITU-T H.248.1 protocol. It lists the service change reason code associated with the service change reason code name. It provides a definition of when the service change reason is to be used. It also provides an indication of what text may be included in the service change extension to allow further interpretation of the service change reason. Clause 5 provides these details.
+
+This revision addresses the following aspects:
+
+- Addition of new error codes: 507
+- Modification of error code: 511
+
+NOTE – This Recommendation has been renamed. It was formerly known as Annex L to Rec. ITU-T H.248.
+
+## History
+
+| Edition | Recommendation              | Approval   | Study Group |
+|---------|-----------------------------|------------|-------------|
+| 1.0     | ITU-T H.248 Annex L         | 2001-07-29 | 16          |
+| 2.0     | ITU-T H.248.8               | 2002-03-29 | 16          |
+| 2.1     | ITU-T H.248.8 (2002) Amd. 1 | 2004-03-15 | 16          |
+| 3.0     | ITU-T H.248.8               | 2005-09-13 | 16          |
+| 4.0     | ITU-T H.248.8               | 2007-08-29 | 16          |
+| 5.0     | ITU-T H.248.8               | 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 Error codes.....                         | 1    |
+| 4.1 Assigning error codes .....            | 1    |
+| 4.2 Error code descriptions.....           | 2    |
+| 5 Service change reasons .....             | 15   |
+| 5.1 Assigning service change reasons ..... | 15   |
+| 5.2 Service change reason description..... | 15   |
+
+
+
+# Recommendation ITU-T H.248.8
+
+# Gateway control protocol: Error code and service change reason description
+
+## 1 Scope
+
+This Recommendation defines the error codes that are used in the core ITU-T H.248.1 protocol. It lists the error code number associated with the error code name. It then provides a definition of when the error code is to be used and if the error code is defined in a package. It also provides an indication of what text may be included in the error text descriptor to allow further interpretation of the error code. Clause 4.2 provides these details. The normal actions for failed transactions and commands apply as specified in clause 8 of [ITU-T H.248.1]. Packages may define error codes not documented in this Recommendation. The IANA registry should be consulted for the complete list of error codes.
+
+Error codes marked as "not used" are historical in nature and are for informational purposes only. These error codes should not be used.
+
+This Recommendation also defines the service change reasons that are used in the core ITU-T H.248.1 protocol. It lists the service change reason code associated with the service change reason code name. It provides a definition of when the service change reason is to be used. It also provides an indication of what text may be included in the service change extension to allow further interpretation of the service change reason. Clause 5.2 provides these details.
+
+## 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
+
+See [ITU-T H.248.1].
+
+# 4 Error codes
+
+### 4.1 Assigning error codes
+
+The following considerations SHALL be met to register an error code with IANA:
+
+- 1) An error number and a one-line (80 characters 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) An error number shall not be redefined, nor modified except by the organization or individual that originally defined it, or their successors or assigns.
+
+Parameters included in the error text shall be coded according to the principles as specified in Annex A or Annex B of [ITU-T H.248.1]. If more than one parameter is included they shall be included in the order defined in this Recommendation and separated by a comma.
+
+Error text may be included in the error descriptor, even for those error codes for which no specific error text is defined in this Recommendation. If error text is included it should contain the information defined in the error specification.
+
+NOTE – The actions carried out after an error is discovered, which results in the sending of an error code described in clause 4.2, are specified in clause 8 of [ITU-T H.248.1].
+
+## 4.2 Error code descriptions
+
+#### 4.2.1 Error code #: 400
+
+**Name:** Syntax error in message
+
+**Definition:** The transaction request(s) has been disregarded due to a syntax error detected at the message level. The message does not conform to the productions of messages as per Annex A or Annex B of [ITU-T H.248.1] as applicable. Used when, e.g., no transaction can be parsed.
+
+**Error text in the error descriptor:** –
+
+**Comment:** If the error is detected prior to determining a valid transaction ID, no meaningful action can be taken on the receipt of the error message.
+
+### 4.2.2 Error code #: 401
+
+**Name:** Protocol error
+
+**Definition:** The transaction or command request(s) has been disregarded due to a violation of Megaco protocol procedures having been detected.
+
+**Error text in the error descriptor:** –
+
+**Comment:** Use more specific error codes (e.g., 505) if possible.
+
+### 4.2.3 Error code #: 402
+
+**Name:** Unauthorized
+
+**Definition:** The command is not executed due to the originator of a command not being authorized to execute that command for the termination(s) affected by it.
+
+**Error text in the error descriptor:** A string containing the command name is included in the error text in the error descriptor.
+
+**Comment:** –
+
+### 4.2.4 Error code #: 403
+
+**Name:** Syntax error in TransactionRequest
+
+**Definition:** The transaction request is disregarded since it failed to match production of a TransactionRequest as per Annexes A and B of [ITU-T H.248.1], as applicable. Used when, e.g., it is not possible to determine the end of a transaction, or when no action can be parsed.
+
+**Reference:** Clause 8.2.2 of [ITU-T H.248.1]
+
+**Error text in the error descriptor:** –
+
+**Comment:** If the error is detected prior to determining a valid transaction ID, no meaningful action can be taken on the receipt of the error message.
+
+#### **4.2.5 Error code #: 406**
+
+**Name:** Version not supported
+
+**Definition:** This indicates a lack of support for the protocol version indicated in the message header of the message, or in the ServiceChangeVersion parameter. In the case of the version number being indicated in the message header, the message contents are disregarded.
+
+**Reference:** Clauses 11.2 or 11.3 of [ITU-T H.248.1]
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.6 Error code #: 410**
+
+**Name:** Incorrect identifier
+
+**Definition:** The transaction request(s) has been disregarded due to a syntax error (illegal length or illegal character) having been found in a mId, transactionId, contextId, terminationId, propertyId, eventId, signalId, statisticsId, parameterId or requestID.
+
+**Error text in the error descriptor:** The concerned ID is included in the error text in the error descriptor.
+
+**Comment:** If the error is detected prior to determining a valid transaction ID, no meaningful action can be taken on the receipt of the error message.
+
+#### **4.2.7 Error code #: 411**
+
+**Name:** The transaction refers to an unknown ContextID
+
+**Definition:** The ContextID referred to by an action in the transaction request is unknown and the action is therefore disregarded.
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.8 Error code #: 412**
+
+**Name:** No ContextIDs available
+
+**Definition:** The MG is unable to create a context in response to an "Add" or "Move" command with CHOOSE given as the ContextId because of a shortage of resources within the MG, and the action is disregarded.
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.9 Error code #: 413**
+
+**Name:** Number of transactions in message exceeds maximum
+
+**Definition:** The message contains more than the maximum allowed number of transactions. If the error descriptor is returned at a message level, the message has not been executed. If the error descriptor is returned at a transaction level, the transaction has not been executed.
+
+**Error text in the error descriptor:** –
+
+**Comment:** The MGC/MG should resend the message with the number of transactions reduced less than or equal to the maximum number.
+
+#### **4.2.10 Error code #: 421**
+
+**Name:** Unknown action or illegal combination of actions
+
+**Definition:** Not used.
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.11 Error code #: 422**
+
+**Name:** Syntax error in action
+
+**Definition:** The action was disregarded due to the syntax of the action not conforming to the production of an actionRequest as per Annex A or B of [ITU-T H.248.1], as applicable. Used when it is not possible to determine the end of an action, when, e.g., no command can be parsed.
+
+**Reference:** Clause 8.2.2 of [ITU-T H.248.1]
+
+**Error text in the error descriptor:** –
+
+**Comment:** Examples of errors are spelling errors, missing brackets.
+
+#### **4.2.12 Error code #: 430**
+
+**Name:** Unknown TerminationID
+
+**Definition:** The TerminationID referred to by the command is unknown and the command is therefore disregarded. The termination ID is not found in the MG. This includes the NULL context. This is generated when the MG does not know which termination the MGC is trying to address.
+
+**Error text in the error descriptor:** The TerminationID is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.13 Error code #: 431**
+
+**Name:** No TerminationID matched a wildcard
+
+**Definition:** The command that included one or more wildcards (ALL or CHOOSE) TerminationID(s) is disregarded since the receiver of the command could not find an existing termination, or create a new termination matching the specified pattern.
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.14 Error code #: 432**
+
+**Name:** Out of TerminationIDs or no TerminationID available
+
+**Definition:** The add command, including the CHOOSE terminationID, is disregarded. The MG was unable to provide a TerminationID because it has exhausted the available range of TerminationIDs.
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.15 Error code #: 433**
+
+**Name:** TerminationID is already in a context
+
+**Definition:** A TerminationID specified in an add command already exists within an active context and therefore the command is disregarded.
+
+**Error text in the error descriptor:** The ContextID is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.16 Error code #: 434**
+
+**Name:** Max number of terminations in a context exceeded
+
+**Definition:** The MGC has requested that a termination be added or moved to a context that already contains a maximum number of terminations allowed. The command is therefore disregarded.
+
+**Reference:** Clauses 6.1 and E.2.1 of [ITU-T H.248.1]
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.17 Error code #: 435**
+
+**Name:** Termination ID is not in specified context
+
+**Definition:** A specific TerminationID specified in a modify, subtract, AuditValue, AuditCapabilities or ServiceChange command does not exist in a specified context and therefore the command is disregarded. This error occurs when the MGC sends a command with a valid TerminationID that is not in the specified contextID. This is used when the MG has a record of the termination but it is not where the MGC says it is.
+
+**Error text in the error descriptor:** The ContextID where the termination is located is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.18 Error code #: 440**
+
+**Name:** Unsupported or unknown package
+
+**Definition:** The package name in a property, parameter, event, signal or statistic identifier is not supported by the receiver. The command related to the unknown identifier is disregarded.
+
+**Error text in the error descriptor:** The package name is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.19 Error code #: 441**
+
+**Name:** Missing remote or local descriptor
+
+**Definition:** The requested command requires that the remote/local descriptor includes necessary or adequate information and therefore the action is not carried out.
+
+**Error text in the error descriptor:** –
+
+**Comment:** The error associated with this code may not be detectable until after the current command or subsequent commands result in failure to process the requested behaviour (e.g., the bearer setup fails).
+
+#### **4.2.20 Error code #: 442**
+
+**Name:** Syntax error in command
+
+**Definition:** A command request has failed to match the syntax of the commandRequest production and is therefore disregarded. Used when, e.g., end of a command cannot be determined.
+
+**Reference:** Clause 8.2.2 of [ITU-T H.248.1]
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.21 Error code #: 443**
+
+**Name:** Unsupported or unknown command
+
+**Definition:** The requested command is not recognized by the receiver and is therefore disregarded.
+
+**Error text in the error descriptor:** A string containing the command name is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.22 Error code #: 444**
+
+**Name:** Unsupported or unknown descriptor
+
+**Definition:** The descriptor in a command request or reply is not recognized by the receiver and is therefore disregarded.
+
+**Error text in the error descriptor:** A string containing the name of the descriptor is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.23 Error code #: 445**
+
+**Name:** Unsupported or unknown property
+
+**Definition:** Property name (Annex A of [ITU-T H.248.1]) or ItemID (Annex B of [ITU-T H.248.1]) of a property parameter within a descriptor is recognized but not supported and the command related to the property is not carried out.
+
+**Error text in the error descriptor:** The property name (Annex A of [ITU-T H.248.1]) or ItemID (Annex B of [ITU-T H.248.1]) is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.24 Error code #: 446**
+
+**Name:** Unsupported or unknown parameter
+
+**Definition:** The parameter in a command request is not recognized by the receiver and the command related to the descriptor is not carried out.
+
+**Error text in the error descriptor:** The ParameterID is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.25 Error code #: 447**
+
+**Name:** Descriptor not legal in this command
+
+**Definition:** The descriptor cannot be used in this command in accordance with the definition in Annexes A and B of [ITU-T H.248.1] and the command, including the descriptor, is not carried out.
+
+**Error text in the error descriptor:** A string containing the name of the descriptor is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.26 Error code #: 448**
+
+**Name:** Descriptor appears twice in a command
+
+**Definition:** The descriptor appears twice in the command and the command, including the descriptor, is not carried out.
+
+**Error text in the error descriptor:** A string containing the name of the descriptor is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.27 Error code #: 449**
+
+**Name:** Unsupported or unknown parameter or property value
+
+**Definition:** The value of a property or parameter within a descriptor is not recognized and the command, including the property/item, is not carried out.
+
+**Error text in the error descriptor:** The parameter or property name followed by the unsupported or unknown value is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.28 Error code #: 450**
+
+**Name:** No such property in this package
+
+**Definition:** Property name (Annex A of [ITU-T H.248.1]) or ItemID (Annex B of [ITU-T H.248.1]) of a property parameter within a descriptor is not recognized and the command, including the property/item, is not carried out.
+
+**Error text in the error descriptor:** The property name (Annex A of [ITU-T H.248.1]) or ItemID (Annex B of [ITU-T H.248.1]) is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.29 Error code #: 451**
+
+**Name:** No such event in this package
+
+**Definition:** The command, including the event name, is not executed because it is not considered to be a part of this version of the package.
+
+**Error text in the error descriptor:** The event name is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.30 Error code #: 452**
+
+**Name:** No such signal in this package
+
+**Definition:** The command, including the signal name, is not executed due to it not being considered by the MG to be a part of this version of the package.
+
+**Error text in the error descriptor:** The signal name is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.31 Error code #: 453**
+
+**Name:** No such statistic in this package
+
+**Definition:** The command, including the statistic name, is not executed due to it not being considered by the MG to be a part of this version of the package.
+
+**Error text in the error descriptor:** The statistic name is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.32 Error code #: 454**
+
+**Name:** No such parameter value in this package
+
+**Definition:** The command, including the parameter value, is not executed because it is not considered to be a part of this version of the package.
+
+**Error text in the error descriptor:** The parameter name is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.33 Error code #: 455**
+
+**Name:** Property illegal in this descriptor
+
+**Definition:** The command, including the property, is disregarded since the MG does not consider it to be a part of this descriptor.
+
+**Error text in the error descriptor:** The property name is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.34 Error code #: 456**
+
+**Name:** Property appears twice in this descriptor
+
+**Definition:** The command, including the property, is not executed due to the parameter or property appearing twice in this descriptor.
+
+**Error text in the error descriptor:** The property name is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.35 Error code #: 457**
+
+**Name:** Missing parameter in signal or event
+
+**Definition:** The command was disregarded due to a missing mandatory parameter.
+
+**Error text in the error descriptor:** If possible, the missing parameter name is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.36 Error code #: 458**
+
+**Name:** Unexpected event/request ID
+
+**Definition:** The command was disregarded because a notification for an event/request ID, that the MGC did not request, was received.
+
+**Error text in the error descriptor:** The request ID is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.37 Error code #: 460**
+
+**Name:** Unable to set statistic on stream
+
+**Definition:** The MG was unable to set the required statistic on a stream. The request has been disregarded.
+
+**Error text in the error descriptor:** The statistic(s) ID(s).
+
+**Comment:** –
+
+#### **4.2.38 Error code #: 471**
+
+**Name:** Implied add for multiplex failure
+
+**Definition:** A termination listed within a multiplex descriptor could not be added to the current context and the "ADD" command is not carried out.
+
+**Error text in the error descriptor:** The TerminationID is indicated in the error text in the error descriptor.
+
+**Comment:** If the termination is already in a different active context, use error code 433.
+
+#### **4.2.39 Error code #: 472**
+
+**Name:** Required information missing
+
+**Definition:** The required information to perform the function indicated by the property/signal/event/statistic sent from the MGC has not been provided to or provisioned on the MG. This dependent information may need to be set in one or more properties before the function/action can be performed. Therefore, the action is disregarded.
+
+**Error text in the error descriptor:** The property name/signal name/event name/statistics name of the element sent by the MGC that required dependent information not available at the MG is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.40 Error code #: 473**
+
+**Name:** Conflicting property values
+
+**Definition:** The values of two or more properties are incompatible with one another, and indicate an impossible or illogical operation. Therefore, the action is disregarded.
+
+**Error text in the error descriptor:** The property names of the conflicting properties are included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.41 Error code #: 500**
+
+**Name:** Internal software failure in the MG or MGC
+
+**Definition:** A command could not be executed due to a software failure within the MG or MGC.
+
+**Error text in the error descriptor:** –
+
+**Comment:** For hardware failures, see error code 529.
+
+#### **4.2.42 Error code #: 501**
+
+**Name:** Not implemented
+
+**Definition:** A property, parameter, signal, event or statistic mentioning the command has not been implemented.
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.43 Error code #: 502**
+
+**Name:** Not ready
+
+**Definition:** The command directed to a termination was not executed because of the service state of the termination.
+
+**Error text in the error descriptor:** The service state is indicated in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.44 Error code #: 503**
+
+**Name:** Service unavailable
+
+**Definition:** Not used.
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.45 Error code #: 504**
+
+**Name:** Command received from unauthorized entity
+
+**Definition:** Not used.
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.46 Error code #: 505**
+
+**Name:** Transaction request received before a ServiceChange reply has been received
+
+**Definition:** Sent by the MG/MGC that has sent a ServiceChange request to an MGC/MG and receives a transaction request from that MGC/MG before it has received the corresponding ServiceChange reply. The actions included in the transaction request are not carried out.
+
+**Reference:** Clause 11.2 of [ITU-T H.248.1]
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.47 Error code #: 506**
+
+**Name:** Number of TransactionPendings exceeded
+
+**Definition:** Indicates that the maximum number of TransactionPendings have been received and that the transaction can be assumed to be in error.
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.48 Error code #: 507**
+
+**Name:** Unknown Control Association
+
+**Definition:** Returned by a MGC in response to a ServiceChangeRequest with method "Disconnect" when the MGC has no knowledge of the indicated control association. MGC should only return responses to MGs that it has knowledge of in order to minimise security issues.
+
+**NOTE** – The MGC should respond using the same H.248 message version as the received message.
+
+**Error Text in the Error Descriptor:** –
+
+**Comment:** –
+
+#### **4.2.49 Error code #: 510**
+
+**Name:** Insufficient resources
+
+**Definition:** The command(s) was rejected due to lack of common resources in the MG.
+
+**Error text in the error descriptor:** The error text in the error descriptor includes the name or identity of the property, signal or event that represents a resource lacking in the MG.
+
+**Comment:** –
+
+#### **4.2.50 Error code #: 511**
+
+**Name:** Temporarily busy
+
+**Definition:** The command(s) was rejected due to a temporary busy condition in the MGC or MG.
+
+**Error text in the error descriptor:** –
+
+**Comment:** Upon receiving this error code, the command may be resent as the busy condition may have abated.
+
+#### **4.2.51 Error code #: 512**
+
+**Name:** Media gateway unequipped to detect requested event
+
+**Definition:** The MG is unable to detect the requested event due to lack of resources.
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.52 Error code #: 513**
+
+**Name:** Media gateway unequipped to generate requested signals
+
+**Definition:** The MG is unable to send the requested signal due to lack of resources.
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.53 Error code #: 514**
+
+**Name:** Media gateway cannot send the specified announcement
+
+**Definition:** The MG is unable to send the requested announcement due to lack of resources.
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.54 Error code #: 515**
+
+**Name:** Unsupported media type
+
+**Definition:** The stream included in the command is not supported by the MG, therefore the command is disregarded.
+
+**Error text in the error descriptor:** The streamID is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.55 Error code #: 517**
+
+**Name:** Unsupported or invalid mode
+
+**Definition:** The stream mode value is not supported for that stream. Therefore, the command related to that parameter is not executed.
+
+**Error text in the error descriptor:** The streamID and stream mode value is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.56 Error code #: 518**
+
+**Name:** Event buffer full
+
+**Definition:** Indicates that the event buffer in the MG is full.
+
+**Error text in the error descriptor:** –
+
+**Comment:** Sent in a notify command.
+
+#### **4.2.57 Error code #: 519**
+
+**Name:** Out of space to store digit map
+
+**Definition:** The MG is out of storage space for DigitMap descriptors, or is not capable of using DigitMaps.
+
+**Error text in the error descriptor:** –
+
+**Comment:** The MGC should fall back to single digit collection or unnamed digit maps.
+
+#### **4.2.58 Error code #: 520**
+
+**Name:** Digit map undefined in the MG
+
+**Definition:** The digit map named in a command is not defined in the MG, and the command is not executed.
+
+**Error text in the error descriptor:** The DigitMap name is included in the error text in the error descriptor.
+
+**Comment:** –
+
+#### **4.2.59 Error code #: 521**
+
+**Name:** Termination is "Service Changing"
+
+**Definition:** Not used.
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.60 Error code #: 522**
+
+**Name:** Functionality requested in topology triple not supported
+
+**Definition:** The MG was unable to apply the topology requested as it does not support the required interconnectivity.
+
+**Error text in the error descriptor:** The invalid topology triples.
+
+**Comment:** –
+
+#### **4.2.61 Error code #: 526**
+
+**Name:** Insufficient bandwidth
+
+**Definition:** The MG was unable to execute a command because of insufficient bandwidth at the network interface or externally to the MG.
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.62 Error code #: 529**
+
+**Name:** Internal hardware failure in MG
+
+**Definition:** The command could not be executed due to hardware failure in the MG.
+
+**Error text in the error descriptor:** –
+
+**Comment:** This error code is to be generated if the failure situation is not already covered by a more specific error, such as "514 – MG cannot send specified announcement", or whatever error is appropriate.
+
+#### **4.2.63 Error code #: 530**
+
+**Name:** Temporary network failure
+
+**Definition:** The command could not be executed due to a problem in the surrounding network. The problem is considered to be of a short-term duration.
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.64 Error code #: 531**
+
+**Name:** Permanent network failure
+
+**Definition:** The command could not be executed due to a problem in the surrounding network. The problem is considered to be of a long-term duration.
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.65 Error code #: 532**
+
+**Name:** Audited property, statistic, event or signal does not exist
+
+**Definition:** The MGC has tried to audit the value of a property or statistic which is currently not instantiated, or a signal that is not active, or an event that is not instantiated.
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+#### **4.2.66 Error code #: 533**
+
+**Name:** Response exceeds maximum transport PDU size
+
+**Definition:** The MG or MGC is unable to assemble a complete transaction response because the number of bytes for the message would exceed the maximum protocol data unit size of the underlying transport. The command instance in the response to that would have caused the overflow to be treated as if it were in error, and the remainder of the transaction is not executed, even if the command was marked "optional".
+
+This situation will typically arise in conjunction with the use of wildcarding, which causes the original command to be expanded into a series of similar command instances.
+
+If the request contained a wildcarded termination ID, the MGC or MG should send later requests with a smaller subset of termination IDs.
+
+**Error text in the error descriptor:** –
+
+**Comment:** Implementers' note: the detection of PDU overflow must occur at a point where there is still room in the PDU for the error descriptor.
+
+### **4.2.67 Error code #: 534**
+
+**Name:** Illegal write or read-only property
+
+**Definition:** The MGC has tried to write a property whose characteristics are defined as read-only. The command containing the property is disregarded.
+
+**Error text in the error descriptor:** A string containing the package ID and property ID of the property trying to be written.
+
+**Comment:** –
+
+#### **4.2.68 Error code #: 542**
+
+**Name:** Command is not allowed on this termination
+
+**Definition:** This error is generated when the MGC has tried to request the processing of a command, which is not allowed on the addressed H.248 termination.
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+### **4.2.69 Error code #: 543**
+
+**Name:** MGC requested event detection timestamp not supported
+
+**Definition:** This error code indicates that the MG is unable to provide event detection timestamps associated for requested event.
+
+**Error text in the error descriptor:** If applicable, the event identifier (i.e., pkgdNName).
+
+**Comment:** This error shall be generated on request of an event (e.g., through an add, modify or move request) not at detection time (e.g., notify request).
+
+### **4.2.70 Error code #: 581**
+
+**Name:** Does not exist
+
+**Definition:** Not used.
+
+**Error text in the error descriptor:** –
+
+**Comment:** –
+
+## 5 Service change reasons
+
+### 5.1 Assigning service change reasons
+
+The following considerations SHALL be met to register service change 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 it is used is detected, 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.
+
+Reason text included in the ServiceChangeReason shall be coded according to the principles as specified in Annex A or B of [ITU-T H.248.1] with a white space between the reason number and the reason text.
+
+### 5.2 Service change reason description
+
+### 5.2.1 Reason #: 900
+
+**Name:** Service restored
+
+**Definition:** It indicates that the entity indicated with the TerminationID is in ServiceState "In-Service".
+
+**Reference:** –
+
+**Text in the service change extension:** –
+
+**Comment:** –
+
+### 5.2.2 Reason #: 901
+
+**Name:** Cold boot
+
+**Definition:** This indicates that the entity indicated by the TerminationID is in ServiceState "In-Service", and that it has gone through a start or recovery action, and all associated contexts, except the null context, have been cleared.
+
+**Reference:** –
+
+**Text in the service change extension:** –
+
+**Comment:** This reason code only applies for TerminationID root.
+
+### 5.2.3 Reason #: 902
+
+**Name:** Warm boot
+
+**Definition:** This indicates that the entity indicated with the TerminationID is in ServiceState "In-Service", and that it has gone through a start or recovery action. All transactions in process may be lost, but otherwise all states are preserved on the termination.
+
+**Reference:** –
+
+**Text in the service change extension:** –
+
+**Comment:** This reason code only applies for TerminationID root.
+
+### 5.2.4 Reason #: 903
+
+**Name:** MGC directed change
+
+**Definition:** This indicates that the MG is directed by an MGC to use the receiver as MGC.
+
+**Reference:** –
+
+**Text in the service change extension:** –
+
+**Comment:** Clause 11.5 of [ITU-T H.248.1]
+
+#### **5.2.5 Reason #: 904**
+
+**Name:** Termination malfunctioning
+
+**Definition:** This indicates that the entity indicated with the TerminationID is in ServiceState "Out-Of-Service" due to some problem directly related to the termination.
+
+**Reference:** –
+
+**Text in the service change extension:** –
+
+**Comment:** –
+
+#### **5.2.6 Reason #: 905**
+
+**Name:** Termination taken out of service
+
+**Definition:** This indicates that the entity indicated with the TerminationID is in ServiceState "Out-Of-Service" due to maintenance action.
+
+**Reference:** –
+
+**Text in the service change extension:** –
+
+**Comment:** –
+
+#### **5.2.7 Reason #: 906**
+
+**Name:** Loss of lower layer connectivity (e.g., downstream sync)
+
+**Definition:** This indicates that the entity indicated with the TerminationID is in ServiceState "Out-Of-Service" due to the termination having experienced loss of lower layer connectivity on the incoming stream.
+
+**Reference:** –
+
+**Text in the service change extension:** –
+
+**Comment:** –
+
+#### **5.2.8 Reason #: 907**
+
+**Name:** Transmission failure
+
+**Definition:** This indicates that the entity indicated with the TerminationID is in ServiceState "Out-Of-Service" due to the termination having experienced a transmission failure, e.g., a degradation of transmission quality.
+
+**Reference:** –
+
+**Text in the service change extension:** –
+
+**Comment:** –
+
+#### **5.2.9 Reason #: 908**
+
+**Name:** MG impending failure
+
+**Definition:** Indicates that the entity indicated with the TerminationID will go to the ServiceState "Out-Of-Service" and is unable to handle new traffic.
+
+**Reference:** Clause 11.4 of [ITU-T H.248.1]
+
+**Text in the service change extension:** –
+
+**Comment:** This reason code only applies for TerminationID root.
+
+#### **5.2.10 Reason #: 909**
+
+**Name:** MGC impending failure
+
+**Definition:** Indicates that the sender will go to the ServiceState "Out-Of-Service" and is unable to handle new transactions.
+
+**Reference:** Clause 11.5 of [ITU-T H.248.1]
+
+**Text in the service change extension:** –
+
+**Comment:** –
+
+#### **5.2.11 Reason #: 910**
+
+**Name:** Media capability failure
+
+**Definition:** This indicates that the entity indicated with the TerminationID has experienced a change of its media capability.
+
+**Reference:** –
+
+**Text in the service change extension:** –
+
+**Comment:** –
+
+#### **5.2.12 Reason #: 911**
+
+**Name:** Modem capability failure
+
+**Definition:** This indicates that the entity indicated with the TerminationID has experienced a change in its modem capability.
+
+**Reference:** –
+
+**Text in the service change extension:** –
+
+**Comment:** –
+
+#### **5.2.13 Reason #: 912**
+
+**Name:** MUX capability failure
+
+**Definition:** This indicates that the entity indicated with the TerminationID has experienced a change in its MUX capability.
+
+**Reference:** –
+
+**Text in the service change extension:** –
+
+**Comment:** –
+
+#### **5.2.14 Reason #: 913**
+
+**Name:** Signal capability failure
+
+**Definition:** This indicates that the entity indicated with the TerminationID has experienced a capability change for its signal capability. This includes changes in packages and/or signalIDs.
+
+**Reference:** –
+
+**Text in the service change extension:** –
+
+**Comment:** –
+
+#### **5.2.15 Reason #: 914**
+
+**Name:** Event capability failure
+
+**Definition:** This indicates that the entity indicated with the TerminationID has experienced a capability change for its events capability. This includes changes in packages and/or eventIDs.
+
+**Reference:** –
+
+**Text in the service change extension:** –
+
+**Comment:** –
+
+Note for codes 911-914; an audit with respect to the:
+
+- Current packages;
+- Current packages and properties (with values);
+- Event descriptor;
+- Signal descriptor;
+- Digit map descriptor,
+
+may be performed to get more information about the changed condition.
+
+#### **5.2.16 Reason #: 915**
+
+**Name:** State loss
+
+**Definition:** This indicates that the entity indicated with the TerminationID has experienced loss of state and that the ServiceState is out of service.
+
+**Reference:** –
+
+**Text in the service change extension:** –
+
+**Comment:** –
+
+#### **5.2.17 Reason #: 916**
+
+**Name:** Packages change
+
+**Definition:** This indicates that the packages, or package versions, implemented on the media gateway have changed. The MGC should consider performing an AuditValue of the media gateway to determine which packages have changed.
+
+**Reference:** –
+
+**Text in the service change extension:** –
+
+**Comment:** –
+
+#### **5.2.18 Reason #: 917**
+
+**Name:** Capabilities change
+
+**Definition:** This indicates that the capabilities of the media gateway have changed. This is used in the case where the package has not changed but the capabilities of properties/parameters have. The MGC should consider performing an AuditCapabilities of the media gateway to determine which capabilities have changed.
+
+**Reference:** –
+
+**Text in the service change extension:** –
+
+**Comment:** –
+
+#### **5.2.19 Reason #: 918**
+
+**Name:** Cancel graceful
+
+**Definition:** This indicates that the previously sent ServiceChange with method graceful should be cancelled.
+
+**Reference:** Clause F.4.1 of [ITU-T H.248.1]
+
+**Text in the service change extension:** –
+
+**Comment:** –
+
+#### **5.2.20 Reason #: 919**
+
+**Name:** Warm failover
+
+**Definition:** This indicates that the media gateway has failed over to a secondary. All transactions in process may be lost, but otherwise all states are preserved on the MG.
+
+**Reference:** –
+
+**Text in the service change extension:** –
+
+**Comment:** This reason code only applies for TerminationID root.
+
+#### **5.2.21 Reason #: 920**
+
+**Name:** Cold failover
+
+**Definition:** This indicates that the media gateway has failed over to a secondary and all associated contexts, except the null context, have been cleared.
+
+**Reference:** –
+
+**Text in the service change extension:** –
+
+**Comment:** This reason code only applies for TerminationID root.
+
+
+
+
+
+## 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.84-201207-I_PDF-E/1316d63eca7b84e13c27f55f0027b7b5_img.jpg b/marked/H/T-REC-H.248.84-201207-I_PDF-E/1316d63eca7b84e13c27f55f0027b7b5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..128492d52804d942a0f86377ae811304ffb7b397
--- /dev/null
+++ b/marked/H/T-REC-H.248.84-201207-I_PDF-E/1316d63eca7b84e13c27f55f0027b7b5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:31940c5108983167b22ec1c557a07cdeff03621dcb1774ccdc7564cf528a9915
+size 116337
diff --git a/marked/H/T-REC-H.248.84-201207-I_PDF-E/339be989b91d5b1e73e5ecdc8401ca75_img.jpg b/marked/H/T-REC-H.248.84-201207-I_PDF-E/339be989b91d5b1e73e5ecdc8401ca75_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..65bfb6df570e71e66aa0ba0cb1b20f315e453291
--- /dev/null
+++ b/marked/H/T-REC-H.248.84-201207-I_PDF-E/339be989b91d5b1e73e5ecdc8401ca75_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a174b8869f35f6dfdcaf4ea51c3020a9ba233b4b8f4cc3227ee2cc3019afbd1f
+size 202285
diff --git a/marked/H/T-REC-H.248.84-201207-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/H/T-REC-H.248.84-201207-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1384c86d3fa149c97a6ac506ea92acee2eb1eb0e
--- /dev/null
+++ b/marked/H/T-REC-H.248.84-201207-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7ab9aa745e34ebffcf26d0ea4ee3a0546512bc28ce52c7fc700020af4ec1f859
+size 75655
diff --git a/marked/H/T-REC-H.248.84-201207-I_PDF-E/675af5bb2357ce5b510e613d04f66bdc_img.jpg b/marked/H/T-REC-H.248.84-201207-I_PDF-E/675af5bb2357ce5b510e613d04f66bdc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..339f5b28047b0d77995ff1d74f2ad88756f458c8
--- /dev/null
+++ b/marked/H/T-REC-H.248.84-201207-I_PDF-E/675af5bb2357ce5b510e613d04f66bdc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:77b994bd78e19b9f26f2d9af407223b25bcadce2d94a8c3c240fe2b6cdb40f79
+size 186051
diff --git a/marked/H/T-REC-H.248.84-201207-I_PDF-E/82b40cb8b2a5ac361973859400fa128a_img.jpg b/marked/H/T-REC-H.248.84-201207-I_PDF-E/82b40cb8b2a5ac361973859400fa128a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f9a2dd74993691fc7b4f1735fcf322c6d4637b0c
--- /dev/null
+++ b/marked/H/T-REC-H.248.84-201207-I_PDF-E/82b40cb8b2a5ac361973859400fa128a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:98da94420d34ef136dbbc38aeb782ada0ccadf3e21b0fdb5fac63eddefaf9525
+size 38437
diff --git a/marked/H/T-REC-H.248.84-201207-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg b/marked/H/T-REC-H.248.84-201207-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a05832b25ff8c4d65e246c34edfe91db91ed2560
--- /dev/null
+++ b/marked/H/T-REC-H.248.84-201207-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8885da2190408d1c8f5fbeef94b92e2bd8134fe9c05ce51950ac1e602162d69c
+size 206964
diff --git a/marked/H/T-REC-H.248.98-201602-I_PDF-E/raw.md b/marked/H/T-REC-H.248.98-201602-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..715a54cc6748b03457120bb0624d81dd30b27afa
--- /dev/null
+++ b/marked/H/T-REC-H.248.98-201602-I_PDF-E/raw.md
@@ -0,0 +1,1346 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.248.98**
+
+(02/2016)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Communication  
+procedures
+
+---
+
+**Gateway control protocol: Support of remote  
+media pause and resume**
+
+Recommendation ITU-T H.248.98
+
+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 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        |
+| <b>Communication procedures</b>                                                             | <b>H.240–H.259</b> |
+| 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.98
+
+# Gateway control protocol: Support of remote media pause and resume
+
+## Summary
+
+Recommendation ITU-T H.248.98 allows the real-time transport protocol (RTP) stream pause and resume functionality as defined by IETF RFC 7728 to be supported on ITU-T H.248 controlled gateways.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T H.248.98 | 2016-02-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/12640">11.1002/1000/12640</a> |
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                                                                 | 2  |
+| 3.1        | Terms defined elsewhere .....                                                                                     | 2  |
+| 3.2        | Terms defined in this Recommendation .....                                                                        | 2  |
+| 4          | Abbreviations and acronyms .....                                                                                  | 2  |
+| 5          | Conventions .....                                                                                                 | 2  |
+| 6          | Relationship to other Recommendations in the ITU-T H.248 sub-series.....                                          | 3  |
+| 7          | Design considerations .....                                                                                       | 3  |
+| 7.1        | Real-time nature .....                                                                                            | 4  |
+| 7.2        | Message direction .....                                                                                           | 4  |
+| 7.3        | Apply to individual sources .....                                                                                 | 4  |
+| 7.4        | Consensus .....                                                                                                   | 5  |
+| 7.5        | Message acknowledgements .....                                                                                    | 5  |
+| 7.6        | Retransmitting requests .....                                                                                     | 5  |
+| 7.7        | Sequence numbering .....                                                                                          | 5  |
+| 8          | RTP topology dependent RTCP handling .....                                                                        | 6  |
+| 8.1        | Introduction .....                                                                                                | 6  |
+| 8.2        | Interactions with ITU-T H.248.88 .....                                                                            | 6  |
+| 8.3        | Interactions with compound and reduced-size RTCP packets .....                                                    | 6  |
+| 8.4        | Gathering SSRC values, relevant for P/R-signalling, from the IP media path .....                                  | 7  |
+| 9          | Remote pause and resume package .....                                                                             | 7  |
+| 9.1        | Properties .....                                                                                                  | 8  |
+| 9.2        | Events .....                                                                                                      | 9  |
+| 9.3        | Signals .....                                                                                                     | 13 |
+| 9.4        | Statistics .....                                                                                                  | 17 |
+| 9.5        | Error codes .....                                                                                                 | 17 |
+| 9.6        | Procedures .....                                                                                                  | 17 |
+| 10         | Examples.....                                                                                                     | 22 |
+| 10.1       | Initiation – pause CCM config=1 .....                                                                             | 22 |
+| 10.2       | Initiation – pause CCM config=5 .....                                                                             | 23 |
+| Appendix I | – Network use cases with ITU-T H.248 media gateways in the end-to-end RTP path with pause/resume signalling ..... | 25 |
+| I.1        | Introduction .....                                                                                                | 25 |
+| I.2        | Single RTP Termination .....                                                                                      | 25 |
+| I.3        | Dual RTP Terminations .....                                                                                       | 25 |
+| I.4        | Multiple RTP Terminations .....                                                                                   | 28 |
+
+|                                                                             | <b>Page</b> |
+|-----------------------------------------------------------------------------|-------------|
+| Appendix II – State models for pause/resume signalling endpoints .....      | 31          |
+| II.1    Introduction .....                                                  | 31          |
+| II.2    RTP pause state model at the RTP sender side .....                  | 31          |
+| II.2    RTP pause state model at the RTP receiver side .....                | 31          |
+| Appendix III – SSRC identifiers for pause/resume signalling endpoints ..... | 34          |
+| III.1    SSRC information in RTCP FB "pause/resume" messages .....          | 34          |
+| III.2    Example use case.....                                              | 34          |
+| Bibliography.....                                                           | 36          |
+
+# Recommendation ITU-T H.248.98
+
+## Gateway control protocol: Support of remote media pause and resume
+
+# 1 Scope
+
+This Recommendation describes the support of real-time transport protocol (RTP) stream pause and resume functionality as defined by [IETF RFC 7728] on ITU-T H.248 controlled gateways. It describes the mapping of call control session description protocol (SDP) related to pause/resume to ITU-T H.248 SDP and vice versa. It also contains a package that allows several different implementation types to be supported. This allows the media gateway (MG) to operate in an autonomous manner by receiving, making pause/resume decisions and sending real-time control protocol (RTCP) level pause/resume messages with minimal media gateway controller (MGC) involvement. An MGC controlled configuration is also supported whereby the reception of pause/request requests/responses is indicated to the MGC for it to make decisions and determine a response. It also allows the MGC to initiate pause/resume requests.
+
+The use of pause codec control messages (CCMs) as defined by [IETF RFC 7728] and temporary maximum media stream bit rate requests (TMMBR) as defined by [IETF RFC 5104] to pause and resume RTP media streams are both supported.
+
+It also contains considerations related to the support of RTP stream pause and resume in ITU-T H.248 controlled gateways.
+
+This Recommendation also details the relationship to other existing ITU-T H.248.x sub-series Recommendations where pause/resume functions are supported.
+
+## 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.9] Recommendation ITU-T H.248.1 (2009), *Gateway control protocol: Advanced media server packages*.
+- [ITU-T H.248.71] Recommendation ITU-T H.248.71 (2010), *Gateway control protocol: RTCP support packages*.
+- [ITU-T H.248.88] Recommendation ITU-T H.248.88 (2014), *Gateway control protocol: RTP topology dependent RTCP handling by ITU-T H.248 media gateways with IP terminations*.
+- [IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications*.
+- [IETF RFC 5104] IETF RFC 5104 (2008), *Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF)*.
+- [IETF RFC 5576] IETF RFC 5576 (2009), *Source-Specific Media Attributes in the Session Description Protocol (SDP)*.
+
+[IETF RFC 7728] IETF RFC 7728 (2015), *RTP Stream Pause and Resume*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 RTP stream** [b-IETF RFC 7656]: A *stream* of RTP packets containing *media data, source or redundant*. The *RTP stream* is identified by an SSRC belonging to a particular *RTP session*.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 P/R-signalling**: The "RTP pause and resume" signalling as defined by [IETF RFC 7728].
+
+NOTE – The signalling protocol syntax is based on dedicated RTCP "feedback" packet types, the signalling protocol procedures use the associated bidirectional RTCP control flow and the signalling protocol semantics are that defined in sections 6 to 9 in [IETF RFC 7728].
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|         |                                                      |
+|---------|------------------------------------------------------|
+| AVPF    | Audio-Visual Profile with Feedback                   |
+| B2BRE   | Back-to-Back RTP End System                          |
+| CCM     | Codec Control Message                                |
+| CNAME   | Canonical NAME                                       |
+| DTMF    | Dual Tone Multi Frequency                            |
+| FB      | Feedback                                             |
+| IWF     | Interworking Function                                |
+| MG      | Media Gateway                                        |
+| MGC     | Media Gateway Controller                             |
+| P/R     | Pause and Resume                                     |
+| RTCP    | Real-Time Control Protocol                           |
+| RTCP FB | RTCP Feedback                                        |
+| RTP     | Real-time Transport Protocol                         |
+| SDES    | Source Description                                   |
+| SDP     | Session Description Protocol                         |
+| SSRC    | Synchronization Source Identifier                    |
+| TMMBN   | Temporary Maximum Media stream Bit rate Notification |
+| TMMBR   | Temporary Maximum Media stream Bit rate Request      |
+
+# 5 Conventions
+
+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.
+
+Capitalized names PAUSE, RESUME, REFUSED, PAUSED refer abstractly to Codec Control Messages (CCM) defined in [IETF RFC 7728] or to the CCMs temporary maximum media stream bit rate request (TMMBR) and temporary maximum media stream bit rate notification (TMMBN) [IETF RFC 5104] when these are used to emulate specific pause/resume behaviour.
+
+# 6 Relationship to other Recommendations in the ITU-T H.248 sub-series
+
+Gateways utilising ITU-T H.248 currently have several methods to pause the transmission of media.
+
+[ITU-T H.248.1]: Contains the Local Control Descriptor 'StreamMode' property that allows the MGC to effectively stop sending an RTP media flow (i.e., change from send/receive to receive only) while still maintaining an RTCP control flow. To resume the flow of media the MGC can change the StreamMode back to send/receive. However, this is a local MG action rather than a request to a remote endpoint. The action is also triggered from a call control level stimulus.
+
+[ITU-T H.248.1]: The ITU-T H.248 connection model (including the TopologyDescriptor) allows Terminations/Streams to be isolated from other Terminations/Streams in the Context. This allows an MGC to isolate an ITU-T H.248 media stream from other input streams effectively stopping the flow of RTP media. The MGC may then move the Termination/Stream back into a Context to resume RTP media flow.
+
+[ITU-T H.248.9]: Contains the "Play collect" package that enables a user to request (via a dual tone multi frequency (DTMF) digit) that the playout of media associated with a signal be paused. It also enables the user to resume the RTP media flow via a DTMF digit.
+
+[b-ITU-T H.248.66]: Contains the "Signal pause" package which is a generic package that allows the MGC to request a pause in the playout of media and to later resume the RTP media flow. It is suited to scenarios where media playout has been initiated through the use of ITU-T H.248 Signals rather than real-time media flows. It again is a local MG action rather than a request to a remote endpoint and the action is also triggered from a call control level stimulus.
+
+[ITU-T H.248.71]: Contains the "RTCP source description" package which allows the MGC to request the MG to monitor, extract and report synchronization source identifier (SSRC) values from RTP streams. Clause 8 describes how the package may be used together with RTP stream pause and resume services.
+
+[ITU-T H.248.88]: Describes RTCP handling by an ITU-T H.248 MG in association with a particular enforced local RTP topology. Clause 8 provides more detailed information on the subject. None of the above methods match the functionality supported by [IETF RFC 7728]. [ITU-T H.248.1] and [b-ITU-T H.248.66] do not support user-originated requests being terminated at the MG and [ITU-T H.248.9] and [b-ITU-T H.248.66] do not allow the pause of ITU-T H.248 media streams not related to the playout of signals.
+
+Pause/resume relates to real-time media flows (as subject of conversational communication services). Therefore, the resumption of an RTP media flow is based on the media at the time of the resume request rather than at the pause point. [b-ITU-T H.248.66] (typically applied in the context of streaming communication services) assumes that the playout occurs from the pause point unless another point is indicated in the resumption request.
+
+# 7 Design considerations
+
+Section 3 of [IETF RFC 7728] describes the main use cases for RTP stream pause and resume. It lists a number of RTP topologies. An ITU-T H.248 media gateway may act as a media sender, media receiver, mixer and/or other RTP topologies with involvement in pause and resume (P/R) signalling.
+
+Appendix I provides a list of example use cases from the perspective of ITU-T H.248 gateways. As such the design criteria listed in section 4 of [IETF RFC 7728] should be considered when implementing RTP stream pause and resume on gateways.
+
+Section 5 of [IETF RFC 7728] describes the remote pause and resume procedures through the use of pause and resume CCMs. In general, these procedures also apply to TMMBR/TMMBN messages. Section 5.6 of [IETF RFC 7728] contains considerations which also apply to this Recommendation. Procedures specific to TMMBR/TMMBN messaging will be specified.
+
+## 7.1 Real-time nature
+
+Given the real-time aspects described in section 4.1 of [IETF RFC 7728] a gateway should ensure prompt handling of resume requests, i.e., an MG and optionally MGC should process and act upon any requests to resume an RTP stream in an expedited manner.
+
+Pause requests are time-dependent; however, handling is not as stringent as resume requests.
+
+## 7.2 Message direction
+
+A gateway may: initiate a local pause or resume of an RTP stream, request a remote RTP sender to pause or resume an RTP stream, and respond to a request from a remote RTP receiver to pause or resume an RTP stream (see Figure 1).
+
+![Diagram showing sender-to-receiver indications for pause and resume. The first part shows a PAUSED.ind message from RTP sender to RTP receiver, with a dashed red arrow labeled 'no feedback' returning. The second part shows PAUSED.req and RESUME.req messages from RTP receiver to RTP sender, with corresponding 'OK' or 'REFUSED.notif' responses.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg)
+
+**Feedback-based control loop:**
+
+Sender-to-receiver indications:
+
+Receiver-to-sender requests:
+
+H.248.98(16)\_F01
+
+NOTE – The "P/R-signalling" path is highlighted in red.
+
+Diagram showing sender-to-receiver indications for pause and resume. The first part shows a PAUSED.ind message from RTP sender to RTP receiver, with a dashed red arrow labeled 'no feedback' returning. The second part shows PAUSED.req and RESUME.req messages from RTP receiver to RTP sender, with corresponding 'OK' or 'REFUSED.notif' responses.
+
+**Figure 1 – RTP stream pause and resume as feedback-based control loop**
+
+Clause 9 provides functionality for an MG to act autonomously or for it to coordinate with the MGC to implement RTP stream pause and resume. Furthermore, it allows the specification of which pause CCM messages are used.
+
+NOTE – There are configuration options in order to support partial implementations, see clause 9.6.1.1.
+
+## 7.3 Apply to individual sources
+
+Section 4.3 of [IETF RFC 7728] indicates that the pause CCM messages relate to a single RTP stream, i.e., relates to a single SSRC. This usually relates to a single ITU-T H.248 Stream. An RTP session may have multiple RTP streams. A single SDP m-line typically describes an RTP session. However, where media multiplexing is used (e.g., as described by [b-IETF BUNDLE]) multiple SDP m=lines can describe an RTP session. Thus an ITU-T H.248 Stream using a SDP "m=" line may describe one or more RTP streams. [IETF RFC 5576] provides attributes for source specific parameters.
+
+This has implications for signals and events related to pause and resume on ITU-T H.248 Streams. In order for any signals and events to be correctly scoped where a single SDP *m*=line describes multiple sources the signal or event must be able to reference the source. Clause 9 allows the SSRC to be associated with pause and resume related signals and events. The MGC shall include the *ssrc* parameter in *rempr* package signals when there are multiple SSRCs in an ITU-T H.248 Stream to uniquely identify the RTP stream instance.
+
+Alternatively, the MGC may consider alternate means (such as through ITU-T H.248 Stream grouping [b-ITU-T H.248.96]) to ensure that there is a single RTP stream per ITU-T H.248 Stream.
+
+## 7.4 Consensus
+
+Section 4.4 of [IETF RFC 7728] indicates that there must be consensus between RTP receivers before an RTP sender can pause an RTP stream. This requires that all RTP receivers be aware of the current RTP stream state (i.e., paused or playing, see section 6 of [IETF RFC 7728]) and that all receivers be aware of the pause request. Relevant example network use cases with ITU-T H.248 MGs are indicated in clause I.4. As described in section 5.3 of [IETF RFC 7728], the RTP sender should delay the pausing of a stream for a wait period. As the gateway acts as an RTP sender it should ensure that pausing meets these requirements. If MG autonomous response is indicated, the MG shall be responsible for maintaining the wait period. If MGC controlled mode is indicated, the MGC shall be responsible for maintaining the wait period.
+
+If a new RTP receiver that supports pause messages is added while an RTP stream is in the paused state, the gateway shall send it a PAUSED indication as per section 5.4 of [IETF RFC 7728]. The MG is responsible for sending the PAUSED indication. In the case of MGC controlled mode the MG shall only send a PAUSED indication if the MGC had previously sent a "Local Pause" (*rempr/lpause*) Signal for the particular RTP stream.
+
+## 7.5 Message acknowledgements
+
+As described in section 4.5 of [IETF RFC 7728] the RTP and RTCP do not guarantee reliable data transmission, meaning that the PAUSE, RESUME, PAUSED and REFUSED messages may be lost. ITU-T H.248 MGCs and MGs should ensure that they follow the procedures in [IETF RFC 7728] with respect to sending PAUSED and REFUSED messages and detecting paused and resumed states. Clause 9 provides events for detecting when an RTP media stream has been paused or resumed to allow coordination between the MGC and MG.
+
+## 7.6 Retransmitting requests
+
+As per section 4.6 of [IETF RFC 7728], PAUSE and RESUME requests sent from an ITU-T H.248 gateway (as RTP receiver) to an RTP stream sender may result in no response (either the receipt of a PAUSED or REFUSED, or media action (pause/resume)) being detected from the sender. The gateway may assume that the PAUSE or RESUME message was lost and thus may need to retransmit the message. Depending on the configuration, the MGC or MG is responsible for the retransmission once the timeout period is met. If MG autonomous response is indicated, the MG shall be responsible for retransmitting the messages. If MGC controlled mode is indicated, the MGC shall be responsible for retransmitting the message (i.e., by sending a new signal to the MG indicating pause or resume).
+
+## 7.7 Sequence numbering
+
+Section 4.7 of [IETF RFC 7728] indicates that PAUSE request messages have a sequence number associated with them. This sequence number is then referenced by the other pause CCM messages. As the pause identity is updated for each PAUSE request, the gateway needs to manage the pause identities (i.e., parameter *pauseID* in the Feedback Control Information field). If MG autonomous mode is indicated, then the MG shall be responsible for assigning the identities. If MGC controlled mode is indicated, then the MGC shall be responsible for assigning the identities.
+
+# 8 RTP topology dependent RTCP handling
+
+## 8.1 Introduction
+
+The ITU-T H.248 Stream endpoint(s) or/and Context involved in RTP stream pause and resume services may be requested to support additional RTP/RTCP related services, leading to potential interactions which should be considered by ITU-T H.248 profile designers. A brief summary of the problem statement may be found in clause 6 of [ITU-T H.248.88]. There are three basic aspects:
+
+1. correct handling of RTCP feedback (FB) "pause/resume" messages, dependent on the end-to-end use case of RTP stream pause and resume (see Appendix I) and dependent on the MG-internally enforced RTP topology (see clause 8.2);
+2. correct handling of compound RTCP packets (see clause 8.3); and
+3. correct handling of SSRC values due to their usage as P/R-signalling endpoint identifiers as well as their occurrence at "multiple places" in SDP and ITU-T H.248 signalling elements (see clause 8.4).
+
+[IETF RFC 7728] indicates that the use of TMMBR/TMMBN only applies to a point-to-point topology. Therefore, the use of other topologies requires the use of pause CCM messages for remote pause and resume.
+
+## 8.2 Interactions with ITU-T H.248.88
+
+[IETF RFC 7728] defines a service, with RTCP-based signalling along the IP media path, which belongs to the following [ITU-T H.248.88] category:
+
+- *RTP profile dependent RTCP service* (clause 8.3.2 of [ITU-T H.248.88]) because it is required to use RTP profiles *RTP/AVPF* or *RTP/SAVPF*;
+- handling of RTCP FB "pause/resume" messages is dependent on the network use case:
+  - o local P/R-signalling endpoint: requires the local *origination* and *termination* of such RTCP FB messages (i.e., support of function F-6 in clause 7.6 of [ITU-T H.248.88]);
+  - o transparent forwarding of P/R-signalling (e.g., use case #4 in Appendix I): requires the *unmodified forwarding* of such RTCP FB messages (i.e., support of function F-4 in clause 7.6 of [ITU-T H.248.88]); and
+- such required RTCP handling behaviour should be consistent when RTP topologies "point-to-point" (i.e., back-to-back RTP end system (B2BRE)), "transport translator" or "mixer" is enabled (i.e., a property setting of *rtpt/rtptopo* equal to 'PP', 'TR' or 'MX').
+
+How does the MG know how RTCP FB "pause/resume" messages need to be processed, i.e., *transparent forwarding* or *origination/termination* mode? Typically, the solution would be:
+
+- the ITU-T H.248 *rempr* package would be part of the operated ITU-T H.248 profile;
+- the usage of *rempr* package elements (in an ITU-T H.248 command request) implies the *origination/termination* mode; and
+- the omission of *rempr* package elements implies the *transparent forwarding* mode (i.e., the MG is not allowed to block such RTCP FB messages).
+
+## 8.3 Interactions with compound and reduced-size RTCP packets
+
+P/R-signalling could use *reduced-size* RTCP packets, which facilitates their processing by MGs because there are no interactions.
+
+However, *compound* RTCP packets may require enhanced processing because the compound RTCP packet might contain multiple RTCP packet types with different destination RTP endpoints. For
+
+instance, an RTCP extended report (XR) packet or RTCP FB explicit congestion notification (ECN) packet might be destined for a next RTP node in the forwarding path, whereas the RTCP FB "pause/resume" packet needs to be terminated locally. Hence, the MG might be required to *rewrite* a (compound) RTCP packet (i.e., support of function F-5 in clause 7.6 of [ITU-T H.248.88]).
+
+## 8.4 Gathering SSRC values, relevant for P/R-signalling, from the IP media path
+
+### 8.4.1 Active call interactions with ITU-T H.248.71
+
+The *RTCP source description* package according to clause 6 of [ITU-T H.248.71] allows the observation and extraction of SSRC values from remote and local RTP endpoints. The ITU-T H.248.71 *rtcpsdes* package is typically applied for network-wide performance monitoring services for RTP traffic, which use RTCP XR packets for transporting measurement data (see [b-ITU-T H.248.48] and [b-ITU-T H.248.87]). There are two basic ITU-T H.248 profile types:
+
+1. ITU-T H.248 profile with RTP stream pause and resume service support, but without any additional RTCP XR-based services; or
+2. ITU-T H.248 profile with support of both RTCP-based services.
+
+The ITU-T H.248.71 *rtcpsdes* package could be applied together with the *rempr* package in case 1, but it is not required for the P/R-signalling service. SSRC information would be extracted directly via ITU-T H.248 Events (of the *rempr* package) from RTCP FB pause/resume messages.
+
+With respect to case 2, where both packages are in use, the procedure to follow is that of case 1 during the active call phase.
+
+### 8.4.2 Pre-call usage of ITU-T H.248.71
+
+The MGC might already need to know the local SSRC value (e.g., for call control signalling purposes) of the RTP endpoint in the MG, participating in RTP stream pause and resume service, *before* any RTP and RTCP packets are transmitted. Hence, the ITU-T H.248 Events (of the *rempr* package) would not work. The solution to such a requirement could be addressed by the ITU-T H.248.71 *rtcpsdes* package (see clause 6.6.1 of [ITU-T H.248.71]).
+
+### 8.4.3 RTP topology "RTP source translator" (ITU-T H.248.88)
+
+An ITU-T H.248 Context enabled both for 1) transparent forwarding of P/R-signalling and 2) an RTP source translator topology (see clause 11.1 of [ITU-T H.248.88]) needs careful consideration because the RTP source translator may modify the SSRC field which is used for *RTP sender/RTP receiver* identification in P/R-signalling. Typically, such an interaction is conditionally dependent on the used RTCP packet structure (see clause 8.3).
+
+# 9 Remote pause and resume package
+
+**Package name:** Remote Pause and Resume
+
+**Package ID:** rempr (0x0123)
+
+**Description:** This package allows an MGC to request that the MG issue a request to a remote endpoint to pause (and subsequently resume) the transmission of an RTP media stream. These pause and resume requests typically apply to conversational media services.
+
+The ITU-T H.248 media stream and RTP media flow are supposed to be used in a bidirectional manner. Hence there are two RTP streams, one in an incoming and one in an outgoing direction. This package makes the assumption that the MG may provide P/R-signalling for both unidirectional RTP streams. P/R-signalling procedures in both directions are disjoint. The package description makes the assumption
+
+that the MG could provide the *RTP receiver* and/or the *RTP sender* function in parallel on a particular ITU-T H.248 stream endpoint (SEP) enabled for support of this package.
+
+This package supports both pause CCM and TMMBR/TMMBN CCM messages although only one method may be used on a particular stream. There are two slightly different *RTP stream pause state models* at *RTP sender* and *RTP receiver* side, see also Appendix II.
+
+**Version:** 1  
+**Extends:** None
+
+## 9.1 Properties
+
+### 9.1.1 Autonomous response
+
+**Property name:** Autonomous Response  
+**Property ID:** ar (0x0001)  
+**Description:** This property indicates whether the MG shall provide an autonomous response to PAUSE and RESUME requests or whether it should notify the MGC and await confirmation from the MGC on what action to take.  
+**Type:** Boolean  
+**Possible values:** On MG autonomous: The MG responds autonomously  
+Off MGC controlled: The MG notifies the MGC and awaits a response  
+**Default:** On (unless provisioned otherwise)  
+**Defined in:** LocalControl or TerminationState  
+**Characteristics:** Read/Write
+
+### 9.1.2 Autonomous request
+
+**Property name:** Autonomous Request  
+**Property ID:** aq (0x0002)  
+**Description:** This property indicates whether the MG is allowed to autonomously send remote pause and resume requests. The MGC is allowed to request the MG to send remote pause and resume requests at any time.  
+**Type:** Boolean  
+**Possible values:** On MG autonomous: The MG is allowed to autonomously send  
+Off MGC controlled: The MG is only allowed to messages requested by the MGC.  
+**Default:** On (unless provisioned otherwise)  
+**Defined in:** LocalControl or TerminationState  
+**Characteristics:** Read/Write
+
+## 9.2 Events
+
+### 9.2.1 RTP Pause State
+
+**Event name:** RTP Pause State  
+**Event ID:** rtpss (0x0001)  
+**Description:** This event allows the MG to indicate when the state associated with an RTP stream pause and resume changes. It is applicable to an ITU-T H.248 Stream endpoint that realizes the *RTP sender* function.
+
+#### 9.2.1.1 EventsDescriptor parameters
+
+##### 9.2.1.1.1 State
+
+**Parameter name:** State  
+**Parameter ID:** state (0x0001)  
+**Description:** This parameter indicates which pause state the MGC wishes to be notified about. Based on the *RTP pause state model* according to section 6 of [IETF RFC 7728] (see also clause II.2).  
+**Type:** Sub-list of Enumeration  
+**Optional:** Yes  
+**Possible values:**
+
+|             |                                                                                                              |
+|-------------|--------------------------------------------------------------------------------------------------------------|
+| paused      | The MG has paused RTP media flow as a result of the receipt of a PAUSE request from a remote RTP endpoint.   |
+| resumed     | The MG has resumed RTP media flow as a result of the receipt of a RESUME request from a remote RTP endpoint. |
+| localPause  | The MG has paused RTP media flow based on a local decision.                                                  |
+| localResume | The MG has resumed RTP media flow based on a local decision.                                                 |
+
+**Default:** All (paused, resumed, localPause, localResume)
+
+##### 9.2.1.1.2 RTP SSRC
+
+**Parameter name:** ssrc  
+**Parameter ID:** ssrc (0x0002)  
+**Description:** This parameter indicates on which SSRCs of the ITU-T H.248 Stream the event is detected.  
+**Type:** Sub-list of Integer (32 bit)  
+**Optional:** Yes  
+**Possible values:** As per section 3 of [IETF RFC 3550].  
+**Default:** The event is detected against all SSRCs that support pause/resume on the ITU-T H.248 Stream.
+
+#### 9.2.1.2 ObservedEventsDescriptor parameters
+
+##### 9.2.1.2.1 Observed state
+
+|                         |                                                                                                                      |
+|-------------------------|----------------------------------------------------------------------------------------------------------------------|
+| <b>Parameter name:</b>  | Observed State                                                                                                       |
+| <b>Parameter ID:</b>    | obstate (0x0001)                                                                                                     |
+| <b>Description:</b>     | This parameter indicates the detected pause state. It is reported whenever there is a transition between the states. |
+| <b>Type:</b>            | Enumeration                                                                                                          |
+| <b>Optional:</b>        | No                                                                                                                   |
+| <b>Possible values:</b> | As per "states" clause 9.2.1.1.1                                                                                     |
+| <b>Default:</b>         | None                                                                                                                 |
+
+##### 9.2.1.2.2 RTP SSRC
+
+|                         |                                                                                               |
+|-------------------------|-----------------------------------------------------------------------------------------------|
+| <b>Parameter name:</b>  | ssrc                                                                                          |
+| <b>Parameter ID:</b>    | ssrc (0x0002)                                                                                 |
+| <b>Description:</b>     | This parameter indicates on which SSRC of the ITU-T H.248 Stream the event has been detected. |
+| <b>Type:</b>            | Integer (32 bit)                                                                              |
+| <b>Optional:</b>        | No                                                                                            |
+| <b>Possible values:</b> | As per section 3 of [IETF RFC 3550].                                                          |
+| <b>Default:</b>         | None                                                                                          |
+
+### 9.2.2 Detect Pause/Resume Request
+
+|                     |                                                                                                                                                                       |
+|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Event name:</b>  | Detect Pause/Resume Request                                                                                                                                           |
+| <b>Event ID:</b>    | dprreq (0x0002)                                                                                                                                                       |
+| <b>Description:</b> | This event allows the MG to indicate when a PAUSE or RESUME request has been detected. Thus, the ITU-T H.248 Stream endpoint realizes the <i>RTP sender</i> function. |
+
+#### 9.2.2.1 EventsDescriptor parameters
+
+##### 9.2.2.1.1 RTP SSRC
+
+|                         |                                                                                              |
+|-------------------------|----------------------------------------------------------------------------------------------|
+| <b>Parameter name:</b>  | ssrc                                                                                         |
+| <b>Parameter ID:</b>    | ssrc (0x0001)                                                                                |
+| <b>Description:</b>     | This parameter indicates on which SSRCs of the ITU-T H.248 Stream the event is detected.     |
+| <b>Type:</b>            | Sub-list of Integer (32 bit)                                                                 |
+| <b>Optional:</b>        | Yes                                                                                          |
+| <b>Possible values:</b> | As per section 3 of [IETF RFC 3550].                                                         |
+| <b>Default:</b>         | The event is detected against all SSRCs that support pause/resume on the ITU-T H.248 Stream. |
+
+#### 9.2.2.2 ObservedEventsDescriptor parameters
+
+##### 9.2.2.2.1 Pause identity
+
+|                         |                                                                                                                                      |
+|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Parameter name:</b>  | Pause Identity                                                                                                                       |
+| <b>Parameter ID:</b>    | pauseID (0x0001)                                                                                                                     |
+| <b>Description:</b>     | This parameter indicates the pauseID contained in the detected request.                                                              |
+| <b>Type:</b>            | Integer                                                                                                                              |
+| <b>Optional:</b>        | Yes                                                                                                                                  |
+|                         | NOTE – The pauseID shall be present if pause/resume CCM messages are used. If TMMBR/TMMBN messages are used it shall not be present. |
+| <b>Possible values:</b> | 0 – 65535                                                                                                                            |
+| <b>Default:</b>         | None                                                                                                                                 |
+
+##### 9.2.2.2.2 Request Type
+
+|                         |                                                                                       |
+|-------------------------|---------------------------------------------------------------------------------------|
+| <b>Parameter name:</b>  | Request Type                                                                          |
+| <b>Parameter ID:</b>    | reqt (0x0002)                                                                         |
+| <b>Description:</b>     | This parameter indicates whether a PAUSE or a RESUME is requested for the RTP stream. |
+| <b>Type:</b>            | Enumeration                                                                           |
+| <b>Optional:</b>        | No                                                                                    |
+| <b>Possible values:</b> | "PAUSE" A PAUSE has been requested.<br>"RESUME" A RESUME has been requested.          |
+| <b>Default:</b>         | None                                                                                  |
+
+##### 9.2.2.2.3 RTP SSRC
+
+|                         |                                                                                               |
+|-------------------------|-----------------------------------------------------------------------------------------------|
+| <b>Parameter name:</b>  | ssrc                                                                                          |
+| <b>Parameter ID:</b>    | ssrc (0x0003)                                                                                 |
+| <b>Description:</b>     | This parameter indicates on which SSRC of the ITU-T H.248 Stream the event has been detected. |
+| <b>Type:</b>            | Integer (32 bit)                                                                              |
+| <b>Optional:</b>        | No                                                                                            |
+| <b>Possible values:</b> | As per section 3 of [IETF RFC 3550].                                                          |
+| <b>Default:</b>         | None                                                                                          |
+
+### 9.2.3 Detect pause and resume result
+
+|                     |                                                                                                                                                                                                        |
+|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Event name:</b>  | Detect Pause and Resume Result                                                                                                                                                                         |
+| <b>Event ID:</b>    | dprres (0x0003)                                                                                                                                                                                        |
+| <b>Description:</b> | This event allows the MG to detect and indicate whether the remote RTP sender has: sent a PAUSED indication, a REFUSE indication or resumed RTP transmission in response to a request initiated by the |
+
+MGC. It also detects a failure of the RTP sender to take action on a PAUSE or RESUME request.
+
+Thus, the ITU-T H.248 Stream endpoint realizes the *RTP receiver* function.
+
+#### 9.2.3.1 EventsDescriptor parameters
+
+##### 9.2.3.1.1 RTP SSRC
+
+|                         |                                                                                              |
+|-------------------------|----------------------------------------------------------------------------------------------|
+| <b>Parameter name:</b>  | ssrc                                                                                         |
+| <b>Parameter ID:</b>    | ssrc (0x0001)                                                                                |
+| <b>Description:</b>     | This parameter indicates on which SSRCs of the ITU-T H.248 Stream the event is detected.     |
+| <b>Type:</b>            | Sub-list of Integer (32 bit)                                                                 |
+| <b>Optional:</b>        | Yes                                                                                          |
+| <b>Possible values:</b> | As per section 3 of [IETF RFC 3550].                                                         |
+| <b>Default:</b>         | The event is detected against all SSRCs that support pause/resume on the ITU-T H.248 Stream. |
+
+#### 9.2.3.2 ObservedEventsDescriptor parameters
+
+##### 9.2.3.2.1 Pause identity
+
+|                         |                                                                                                                                                                           |
+|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Parameter name:</b>  | Pause Identity                                                                                                                                                            |
+| <b>Parameter ID:</b>    | pauseID (0x0001)                                                                                                                                                          |
+| <b>Description:</b>     | This parameter indicates the pauseID contained in the detected PAUSED or REFUSED indication. It may also contain the pauseID related to a failed PAUSE or RESUME request. |
+| <b>Type:</b>            | Integer                                                                                                                                                                   |
+| <b>Optional:</b>        | Yes<br>NOTE – The pauseID shall be present if pause/resume CCM messages are used. If TMMBR/TMMBN messages are used it shall not be present.                               |
+| <b>Possible values:</b> | 0 – 65535                                                                                                                                                                 |
+| <b>Default:</b>         | None                                                                                                                                                                      |
+
+##### 9.2.3.2.2 Response type
+
+|                         |                                                                                                                                                                                             |
+|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Parameter name:</b>  | Response Type                                                                                                                                                                               |
+| <b>Parameter ID:</b>    | rest (0x0002)                                                                                                                                                                               |
+| <b>Description:</b>     | This parameter indicates whether a PAUSED or a REFUSED indication has been received. It also indicates whether a RESUME request as resulted in the flow of RTP packets from the RTP sender. |
+| <b>Type:</b>            | Enumeration                                                                                                                                                                                 |
+| <b>Optional:</b>        | No                                                                                                                                                                                          |
+| <b>Possible values:</b> | "paused" A PAUSED indication has been received.<br>"refused" A REFUSED indication has been received.<br>"resumed" The MG has detected a resumed RTP flow.                                   |
+
+"failed" No response from the RTP sender has been detected
+
+**Default:** None
+
+##### 9.2.2.2.3 RTP SSRC
+
+**Parameter name:** ssrc
+
+**Parameter ID:** ssrc (0x0003)
+
+**Description:** This parameter indicates on which SSRC of the ITU-T H.248 Stream the event has been detected.
+
+**Type:** Integer (32 bit)
+
+**Optional:** No
+
+**Possible values:** As per section 3 of [IETF RFC 3550].
+
+**Default:** None
+
+## 9.3 Signals
+
+### 9.3.1 Local Pause
+
+**Signal name:** Local Pause
+
+**Signal ID:** lpause (0x0001)
+
+**Description:** This signal indicates that the MG shall pause the RTP stream and send a PAUSED indication to the remote RTP receiver(s). Thus, the ITU-T H.248 Stream endpoint realizes the *RTP sender* function.
+
+**Signal Type:** Brief
+
+**Duration:** None
+
+#### 9.3.1.1 Additional parameters
+
+##### 9.3.1.1.1 Pause identity
+
+**Parameter name:** Pause Identity
+
+**Parameter ID:** pauseID (0x0001)
+
+**Description:** This parameter indicates the pauseID of the PAUSE to which the PAUSED indication relates.
+
+**Type:** Integer
+
+**Optional:** Yes
+
+NOTE – The pauseID shall be present if pause/resume CCM messages are used. If TMMBR/TMMBN messages are used it shall not be present.
+
+**Possible values:** 0 – 65535
+
+**Default:** None
+
+##### 9.3.1.1.2 RTP SSRC
+
+**Parameter name:** ssrc
+
+**Parameter ID:** ssrc (0x0002)
+
+**Description:** This parameter indicates to which SSRC the PAUSE relates.
+
+**Type:** Integer (32 bit)
+
+|                         |                                      |
+|-------------------------|--------------------------------------|
+| <b>Optional:</b>        | Yes                                  |
+| <b>Possible values:</b> | As per section 3 of [IETF RFC 3550]. |
+| <b>Default:</b>         | None                                 |
+
+### 9.3.2 Local Resume
+
+|                     |                                                                                                                                                               |
+|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Signal name:</b> | Local Resume                                                                                                                                                  |
+| <b>Signal ID:</b>   | lresume (0x0002)                                                                                                                                              |
+| <b>Description:</b> | This signal indicates that the MG shall resume transmission of the RTP stream. Thus, the ITU-T H.248 Stream endpoint realizes the <i>RTP sender</i> function. |
+| <b>Signal Type:</b> | Brief                                                                                                                                                         |
+| <b>Duration:</b>    | None                                                                                                                                                          |
+
+#### 9.3.2.1 Additional parameters
+
+##### 9.3.2.1.1 Pause identity
+
+|                         |                                                                                                                                      |
+|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Parameter name:</b>  | Pause Identity                                                                                                                       |
+| <b>Parameter ID:</b>    | pauseID (0x0001)                                                                                                                     |
+| <b>Description:</b>     | This parameter indicates the pauseID indicating the PAUSE to which the RESUME relates.                                               |
+| <b>Type:</b>            | Integer                                                                                                                              |
+| <b>Optional:</b>        | Yes                                                                                                                                  |
+|                         | NOTE – The pauseID shall be present if pause/resume CCM messages are used. If TMMBR/TMMBN messages are used it shall not be present. |
+| <b>Possible values:</b> | 0 – 65535                                                                                                                            |
+| <b>Default:</b>         | None                                                                                                                                 |
+
+##### 9.3.2.1.2 RTP SSRC
+
+|                         |                                                            |
+|-------------------------|------------------------------------------------------------|
+| <b>Parameter name:</b>  | ssrc                                                       |
+| <b>Parameter ID:</b>    | ssrc (0x0002)                                              |
+| <b>Description:</b>     | This parameter indicates to which SSRC the RESUME relates. |
+| <b>Type:</b>            | Integer (32 bit)                                           |
+| <b>Optional:</b>        | Yes                                                        |
+| <b>Possible values:</b> | As per section 3 of [IETF RFC 3550].                       |
+| <b>Default:</b>         | None                                                       |
+
+### 9.3.3 Refuse
+
+|                     |                                                                                                                                                                                                                                                                                    |
+|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Signal name:</b> | Refuse                                                                                                                                                                                                                                                                             |
+| <b>Signal ID:</b>   | refuse (0x0003)                                                                                                                                                                                                                                                                    |
+| <b>Description:</b> | This signal indicates that the MG shall not change the state of the RTP stream. If the MG had received a remote request to change the state, it should send a REFUSED indication to the remote end. Thus, the ITU-T H.248 Stream endpoint realizes the <i>RTP sender</i> function. |
+
+**Signal Type:** Brief  
+**Duration:** None
+
+#### 9.3.3.1 Additional parameters
+
+##### 9.3.3.1.1 Pause Identity
+
+**Parameter name:** Pause Identity  
+**Parameter ID:** pauseID (0x0001)  
+**Description:** This parameter indicates the pauseID indicating the PAUSE to which the REFUSED relates.  
+**Type:** Integer  
+**Optional:** Yes  
+NOTE – The pauseID shall be present if pause/resume CCM messages are used. If TMMBR/TMMBN messages are used it shall not be present.  
+**Possible values:** 0 – 65535  
+**Default:** None
+
+##### 9.3.3.1.2 RTP SSRC
+
+**Parameter name:** ssrc  
+**Parameter ID:** ssrc (0x0002)  
+**Description:** This parameter indicates to which SSRC the REFUSED relates.  
+**Type:** Integer (32 bit)  
+**Optional:** Yes  
+**Possible values:** As per section 3 of [IETF RFC 3550].  
+**Default:** None
+
+### 9.3.4 Remote Pause
+
+**Signal name:** Remote Pause  
+**Signal ID:** rpause (0x0004)  
+**Description:** This signal indicates that the MG shall send a PAUSE request to the remote RTP sender. Thus, the ITU-T H.248 Stream endpoint realizes the *RTP receiver* function.  
+**Signal Type:** Brief  
+**Duration:** None
+
+#### 9.3.4.1 Additional parameters
+
+##### 9.3.4.1.1 Pause identity
+
+**Parameter name:** Pause Identity  
+**Parameter ID:** pauseID (0x0001)  
+**Description:** This parameter indicates the pauseID contained in the PAUSE request.  
+**Type:** Integer
+
+|                         |                                                                                                                                                   |
+|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Optional:</b>        | Yes                                                                                                                                               |
+| <b>Possible values:</b> | 0 – 65535<br>NOTE – The pauseID shall be present if pause/resume CCM messages are used. If TMMBR/TMMBN messages are used it shall not be present. |
+| <b>Default:</b>         | None                                                                                                                                              |
+
+##### 9.3.4.1.2 RTP SSRC
+
+|                         |                                                           |
+|-------------------------|-----------------------------------------------------------|
+| <b>Parameter name:</b>  | ssrc                                                      |
+| <b>Parameter ID:</b>    | ssrc (0x0002)                                             |
+| <b>Description:</b>     | This parameter indicates to which SSRC the PAUSE relates. |
+| <b>Type:</b>            | Integer (32 bit)                                          |
+| <b>Optional:</b>        | Yes                                                       |
+| <b>Possible values:</b> | As per section 3 of [IETF RFC 3550].                      |
+| <b>Default:</b>         | None                                                      |
+
+### 9.3.5 Remote Resume
+
+|                     |                                                                                                                                                                          |
+|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Signal name:</b> | Remote Resume                                                                                                                                                            |
+| <b>Signal ID:</b>   | rresume (0x0005)                                                                                                                                                         |
+| <b>Description:</b> | This signal indicates that the MG shall send a RESUME request to the remote RTP sender. Thus, the ITU-T H.248 Stream endpoint realizes the <i>RTP receiver</i> function. |
+| <b>Signal Type:</b> | Brief                                                                                                                                                                    |
+| <b>Duration:</b>    | None                                                                                                                                                                     |
+
+#### 9.3.5.1 Additional parameters
+
+##### 9.3.5.1.1 Pause identity
+
+|                         |                                                                                                                                             |
+|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Parameter name:</b>  | Pause Identity                                                                                                                              |
+| <b>Parameter ID:</b>    | pauseID (0x0001)                                                                                                                            |
+| <b>Description:</b>     | This parameter indicates the pauseID contained in the RESUME request.                                                                       |
+| <b>Type:</b>            | Integer                                                                                                                                     |
+| <b>Optional:</b>        | Yes<br>NOTE – The pauseID shall be present if pause/resume CCM messages are used. If TMMBR/TMMBN messages are used it shall not be present. |
+| <b>Possible values:</b> | 0 – 65535                                                                                                                                   |
+| <b>Default:</b>         | None                                                                                                                                        |
+
+##### 9.3.5.1.2 RTP SSRC
+
+|                        |                                                            |
+|------------------------|------------------------------------------------------------|
+| <b>Parameter name:</b> | ssrc                                                       |
+| <b>Parameter ID:</b>   | ssrc (0x0002)                                              |
+| <b>Description:</b>    | This parameter indicates to which SSRC the RESUME relates. |
+| <b>Type:</b>           | Integer (32 bit)                                           |
+
+**Optional:** Yes  
+**Possible values:** As per section 3 of [IETF RFC 3550].  
+**Default:** None
+
+## 9.4 Statistics
+
+### 9.4.1 Local pause duration
+
+**Statistic Name:** Local Pause duration  
+**Statistic ID:** lpdur (0x0001)  
+**Description:** This statistic indicates the total time that the stream has remained in local paused state (see Figure II.1.), i.e., not sending RTP media to a remote RTP receiver. This correlates to the period between sending a PAUSED indication to the sending of RTP media. The statistic is the sum of all such periods for the life of the stream.  
+**Type:** Unsigned Integer  
+**Possible Values:** Any in milliseconds.  
+**Level:** Stream
+
+### 9.4.2 Remote pause duration
+
+**Statistic Name:** Remote Local Pause duration  
+**Statistic ID:** rpdur (0x0002)  
+**Description:** This statistic indicates the total time that the stream has remained in remote paused state (see Figure II.2.), i.e., not receiving RTP media from a remote RTP sender. This correlates to the period between receiving a PAUSED indication to the detection of RTP media reception. The statistic is the sum of all such periods for the life of the stream.  
+**Type:** Unsigned Integer  
+**Possible Values:** Any in milliseconds.  
+**Level:** Stream
+
+## 9.5 Error codes
+
+None.
+
+## 9.6 Procedures
+
+This package allows the gateway to act in the following main modes:
+
+1. MG autonomous handling of pause and resume requests from a remote *RTP receiver* where the MGC is notified of RTP stream state change. The MG acts in the *RTP sender* role.
+2. MGC controlled handling of pause and resume requests from a remote *RTP receiver* where the MGC is notified of pause and resume messages from a remote RTP receiver and provides a response to the MG regarding the action to take. The MG acts in the *RTP sender* role.
+3. MGC initiated pause/resume requests towards a remote RTP sender where the MGC receives the pause and resume request results from MG. The MG acts in the *RTP receiver* role.
+
+4. MGC initiated local pause/resume where the MGC receives the local pause and local resume request results from MG. The MG acts in the *RTP sender* role.
+
+5. MG initiated autonomous sending of pause and resume requests towards a remote RTP sender where the MGC is notified of the result. The MG acts in the *RTP receiver* role.
+
+In addition, an MG acting as an RTP sender can autonomously pause and resume a stream. This package allows an MG to notify the MGC when such autonomous pause or resume actions take place.
+
+The procedures for these modes are described in clauses 9.6.3 to 9.6.8. Clauses 9.6.1 and 9.6.2 provide general procedures for these modes.
+
+### 9.6.1 General – SDP parameter setting
+
+On ITU-T H.248 Streams where RTP stream pause and resume is supported, for these modes of operation the MGC shall set SDP media descriptions in the Local and/or Remote Descriptors indicating the support of "pause" CCM [IETF RFC 5104] as per section 9 of [IETF RFC 7728] or the support of "TMMBR/TMMBN" CCMs. This allows the MGC to indicate to the MG the support of MG initiated local pause and resume (as *RTP sender* and *RTP receiver*) without the need for ITU-T H.248 Signals and Events.
+
+The inclusion of "**a=rtpfb:\* ccm tmmbbr**" and the absence of "**a=rtpfb:\* ccm pause**" would indicate that TMMBR/TMMBN CCM signalling is used. The inclusion of "**a=rtpfb:\* ccm pause**" irrespective of whether "**a=rtpfb:\* ccm tmmbbr**" is included would result in pause/resume CCMs being used.
+
+#### 9.6.1.1 Pause CCM
+
+The SDP for "pause" allows a "config" parameter to be set against an m-line which indicates which pause/resume CCM messages it supports. This description is based on the m-line describing a bidirectional bearer, however the Local and Remote Descriptor describes a unidirectional bearer. Rather than mapping the "config" value to a separate value for the Local and Remote Descriptor the same value shall be set on both these Descriptors.
+
+#### 9.6.1.2 TMMBR CCM
+
+See section 5.6 of [IETF RFC 7728] for TMMBR/TMMBN considerations and the mapping between TMMBR/TMMBN CCMs to Pause CCMs. The remainder of clause 9 discusses the procedures in terms of pause CCMs.
+
+The TMMBR SDP does not support the sending of configurations indicating which messages are supported. The inclusion of TMMBR in an SDP Offer and SDP Answer implies that the offerer and answerer can receive TMMBR/TMMBN messages and act upon them, however it does not mean that they can send messages. Therefore, for the purposes of this package it is assumed that when using TMMBR/TMMBN configuration "1" applies except that the sending of a REFUSED in response to a PAUSE is not supported (see section 5.3 of [IETF RFC 7728]). As per clause 9.6.1.1 identical TMMBR SDP shall be set on the both the Local and Remote Descriptors.
+
+### 9.6.2 General – event and signal scope
+
+Given that pause and resume relate to a single RTP stream, signals and vvents should be set in such a way that the affected RTP streams are unambiguously identified. Where an ITU-T H.248 Stream contains a single RTP stream (i.e., a single SSRC) the MGC may omit the *ssrc* parameter when setting any signals and events in this package. Where an ITU-T H.248 Stream contains multiple RTP streams the MGC shall include the *ssrc* parameter indicating the SSRC of the applicable RTP stream.
+
+There are several ways that an MGC may determine which SSRC to use:
+
+1. as detected and reported by the MG via ObservedEvent parameters *rtpps/ssrc* or *dpreq/ssrc*;
+2. via **SDP attributes** in SIP signalling [IETF RFC 5576]; or/and
+
+3. via [ITU-T H.248.71] "statistic" *rtcpdes/rssrc*.
+
+Typically method 1) is used by this package where the MG detects and reports the SSRC from incoming pause/resume signalling. If available, method 2) is used where the MGC needs to initiate P/R signalling to a remote endpoint without prior knowledge of the SSRCs from the MG. An audit of the statistic in method 3) may be initiated by the MGC to discover the remote SSRC.
+
+The ITU-T H.248 *ssrc* parameter shall be mapped by the MG to the correspondent SSRC field in a RTCP pause/resume CCM message, dependent on the applied in *RTP sender* or *RTP receiver* role (see also Appendix III).
+
+Where there are multiple ITU-T H.248 Streams on a Termination the MGC shall set the StreamID related to the RTP stream in the events and signals in this package.
+
+NOTE – The pauseID parameter shall be omitted when TMMBR/TMMBN signalling is used.
+
+### 9.6.3 MG autonomous handling of remote requests
+
+The MGC controller may confer handling of RTP pause/resume requests to the MG by setting the "Autonomous Response" (*rempr/ar*) property to "on" indicating that the MG shall autonomously process and respond to any RTP pause/resume messages as defined by [IETF RFC 7728]. If the MGC requires to be notified of any changes in RTP transmission state, then the MGC shall set the "RTP Pause State" (*rempr/rtppps*) Event with the states that it requires to be informed about. The MGC shall also set the 'pause' parameter in the Local and Remote Descriptor as appropriate according to clause 9.6.1.
+
+On receipt of a PAUSE request message the MG shall as RTP sender act according to sections 5.2 and 5.4 of [IETF RFC 7728]. This may result in the MG pausing the RTP stream and the sending of a PAUSED indication or sending a REFUSE message and continuing the transmission of the RTP stream. If requested when entering the PAUSED state the MG will generate a Notify.req with a "RTP Pause State" (*rempr/rtppps*) ObservedEvent indicating that the RTP stream has entered the "paused" state (*obstate="paused"*).
+
+On receipt of a RESUME request message the MG shall as RTP sender act according to section 5.5 of [IETF RFC 7728]. This may result in the MG resuming the RTP stream or the sending of a REFUSE message and the continuation of the paused state. If requested when resuming media flow the MG will generate a Notify.req with a "RTP Pause State" (*rempr/rtppps*) ObservedEvent indicating that the RTP stream has been resumed (*obstate="resumed"*).
+
+### 9.6.4 MGC of pause and resume requests
+
+The MGC may reception require that it be responsible for the decision of whether or not to pause or resume an RTP stream. In this case it shall set the "Autonomous Response" (*rempr/ar*) property to "off" indicating to the MG that it shall defer the decision to pause/resume an RTP stream to the MGC. The MGC shall also set the "Detect Pause/Resume Request" (*rempr/dprreq*) to request notification of pause or resume requests.
+
+On receipt of a PAUSE request the MG shall send a Notify.req with the "Detect Pause/Resume Request" (*rempr/dprreq*) ObservedEvent indicating a request type indicating a pause (*reqt="PAUSE"*). The MGC shall take into account any topology (end-to-end RTP session topology, see clause 8 and MG-local internal RTP topology, see Appendix I), service or other local considerations to determine whether to grant the pause request. In order to grant the request, the MGC shall send the "pause" (*rempr/lpause*) Signal to the MG. On receipt of the signal the MG shall pause the RTP stream and send a PAUSED indication as per section 5.4 of [IETF RFC 7728]. To deny the request, the MGC shall send the "refuse" (*rempr/refuse*) Signal to the MG. On receipt of the signal the MG shall send a REFUSED indication as per sections 5.3 and 5.4 of [IETF RFC 7728].
+
+On receipt of a RESUME request, the MG shall send a Notify.req with the "Detect Pause/Resume Request" (*rempr/dprreq*) ObservedEvent indicating a request type indicating a resume
+
+(*reqt="RESUME"*). The MGC shall take into account any topology (see clause 8), service or other local considerations to determine whether to grant the resume request. In order to grant the request, the MGC shall send the "resume" (*rempr/lresume*) Signal to the MG. On receipt of the signal the MG shall resume the RTP stream as per section 5.5 of [IETF RFC 7728]. Media is resumed at a time-shifted point rather than from the pause point. To deny the request, the MGC shall send the "refuse" (*rempr/refuse*) Signal to the MG. On receipt of the signal the MG shall send a REFUSED indication as per section 5.5 of [IETF RFC 7728].
+
+The MG shall not send a Notify.req with "Detect Pause/Resume Request" (*rempr/dprreq*) ObservedEvent with a request type for a pause state that the RTP stream is already in, i.e., the MG shall not send a request type equal to pause if the RTP stream is already paused.
+
+### 9.6.5 MGC initiation of remote pause and resume requests
+
+The MGC may require that for a particular RTP stream that the remote RTP sender pauses RTP transmission. In order to request the MG to send a PAUSE request to the remote RTP sender, the MGC shall send the "Remote Pause" (*rempr/rpause*) Signal to the MG. On reception of the signal the MG shall initiate a PAUSE request on the applicable RTP stream. The MGC may provide or wildcard CHOOSE a Pause Identity (*pauseid*). If the *pauseid* is wildcarded, the MG shall return the chosen value in a command reply. The MG will send the pause identity in the PAUSE request. The use of the pause identity allows the MGC and MG to correlate pause/resume requests and replies.
+
+The MGC may require that for a particular RTP stream that the remote RTP sender resumes RTP transmission. In order to request the MG to send a RESUME request to the remote RTP sender, the MGC shall send the "Remote Resume" (*rempr/rresume*) Signal to the MG. On reception of the Signal the MG shall initiate a RESUME request on the applicable RTP stream. The MGC shall provide a fully specified a Pause Identity (*pauseid*).
+
+In order that the MGC may be notified of the response from the remote RTP sender regarding MGC initiated PAUSE and RESUME requests it shall set the "Detect Pause and Resume Result" (*rempr/dprres*) Event. On reception of a *rempr/rpause* Signal with a pause identity, the MG arms the event and sends a Notify.req to the MGC when it detects a PAUSED or REFUSED indication for the applicable pause identity. On reception of a *rempr/rresume* Signal with a pause identity, the MG arms the events and sends a Notify.req to the MGC when it detects a REFUSED indication or when it detects a resumed RTP flow for the applicable RTP stream. The Notify.req contains the *dprres* ObservedEvent containing the Response Type (*rest*). If after a suitable timeout period (see section 4.6 of [IETF RFC 7728]) the MG does not detect any response from the RTP sender (either by signalling pause CCM messages or via a modification in the sending of the RTP stream) the MG shall send a Notify.req containing the *dprres* ObservedEvent containing the Response Type indicating a failure.
+
+### 9.6.6 Local pause and resume
+
+According to sections 5.4 and 5.5 of [IETF RFC 7728] an RTP sender can choose to pause and resume a stream at any time. In a decomposed RTP sender, the decision to perform a local pause or resume may be taken by the MGC or autonomously by the MG.
+
+#### 9.6.6.1 MGC initiation of local pause and resume
+
+The MGC may require that for a particular RTP stream that the MG as RTP sender pauses RTP transmission. In order to request the MG to pause RTP sending, the MGC shall send the "Local Pause" (*rempr/lpause*) Signal to the MG. On reception of the signal the MG shall initiate a PAUSE on the applicable RTP stream. The MG shall send a PAUSED indication to the RTP receivers. The MGC may provide or wildcard CHOOSE a Pause Identity (*pauseid*). If the *pauseid* is wildcarded, the MG shall return the chosen value in a command reply. The MG will send the pause identity in the PAUSED indication.
+
+The MGC may require that for a particular RTP stream that the MG as RTP sender resumes RTP transmission. In order to request the MG to resume RTP sending, the MGC shall send the "Local Resume" (*rempr/lresume*) Signal to the MG. On reception of the signal the MG shall initiate a RESUME request on the applicable RTP stream. The MGC shall provide a fully specified Pause Identity (*pauseid*).
+
+In order that the MGC may be notified of the result of the MG to MGC initiated local PAUSE and RESUME requests it shall set the "RTP Pause State" (*rempr/rtpps*) Event. On reception of a *rempr/lpause* Signal with a pause identity, the MG sends a Notify.req to the MGC when it enters the local paused state. On reception of a *rempr/lresume* Signal with a pause identity, the MG sends a Notify.req to the MGC when it resumes RTP flow for the applicable RTP stream. The Notify.req contains the *rtpps* ObservedEvent containing the Observed State (*obstate*) set to "localPause" or "localResume".
+
+#### 9.6.6.2 MG initiation of local pause and resume
+
+An MG acting as RTP sender may pause an RTP stream at any time. If the MG initiates a local pause and it has been requested to report this state, it shall generate a Notify.req with a "RTP Pause State" (*rempr/rtpps*) ObservedEvent indicating that the RTP stream has been paused (*obstate="localPause"*) due to a local decision.
+
+The MG shall send a PAUSED indication to the RTP receivers containing a PAUSE ID generated according to the rules specified in section 5.4 of [IETF RFC 7728].
+
+An MG may resume an RTP stream at any time. If the MG initiates a local resume and it has been requested to report this state, it shall generate a Notify.req with a "RTP Pause State" (*rempr/rtpps*) ObservedEvent indicating that the RTP stream has been resumed (*obstate="localResume"*) due to a local decision.
+
+### 9.6.7 MG initiation of remote pause and resume
+
+The MGC controller may allow the MG to autonomously send remote pause and resume requests by setting the "Autonomous Request" (*rempr/aq*) property to "on". An MG shall only initiate pause and resume requests as allowed by the SDP "config" CCM parameters set for the stream. The trigger for sending the requests may be the reception of pause and resumes requests on other Terminations with the same stream. See clause I.3 for further information regarding coupled pause and resume signalling. To avoid this behaviour the MGC shall set the *rempr/aq* property to "off".
+
+In order to determine the results of the MG initiated remote pause and resume requests the MGC should set the "Detect Pause and Resume Result" (*rempr/dprres*) Event. The ObservedEvent shall be notified to the MGC according to clause 9.6.5.
+
+### 9.6.8 Error handling
+
+The MGC shall not send signals or set events that are incompatible with the SDP "config" CCM parameters. For example, the MGC shall not request the "rpause" Signal on a stream if it has not set the "*config*" parameter equal to 1, 2 or 4. Table 1 indicates the allowed settings.
+
+**Table 1 – Allowed setting of "rempr" package signals and events**
+
+| Package "rempr" signals          | Valid "configs" | Comments |
+|----------------------------------|-----------------|----------|
+| Local Pause ( <i>lpause</i> )    | 1,2,3,5,6,8     |          |
+| Local Resume ( <i>lresume</i> )  | 1,2,4,5         |          |
+| Refuse ( <i>refuse</i> )         | 1,2,5           |          |
+| Remote Pause ( <i>rpause</i> )   | 1,2,4           |          |
+| Remote Resume ( <i>rresume</i> ) | 1,2,4           |          |
+
+**Table 1 – Allowed setting of "rempr" package signals and events**
+
+| Package "rempr" signals                          | Valid "configs" | Comments                                                                   |
+|--------------------------------------------------|-----------------|----------------------------------------------------------------------------|
+| RTP Pause State ( <i>rtpps</i> )                 | 1,2,3,4,5,6,7,8 | As the event may detect any state it may be set against any configuration. |
+| Detect Pause/Resume Request ( <i>dprreq</i> )    | 1,2,3,4,6,7     |                                                                            |
+| Detect Pause and Resume Result ( <i>dprres</i> ) | 1,3,5           |                                                                            |
+
+If the MGC sends a Signal or Event without having also set the 'pause' or 'paused' SDP parameter in a Local or Remote Descriptor then the MG shall respond with error 472 "Required Information Missing". If the MGC sends a Signal or Event on a Stream where the 'pause' or 'paused' SDP parameter is set contravening Table 1, then the MG shall respond with error 473 "Conflicting Property Values".
+
+### 9.6.9 Statistics
+
+The MGC may determine the amount of time a stream has been locally paused and/or remotely paused through an audit of the *rempr/lpdur* and *rempr/rpdur* statistics respectively.
+
+## 10 Examples
+
+The clauses below show examples for initiating pause and resume on a stream.
+
+Section 10 of [IETF RFC 7728] contains examples for pause and resume CCM flows.
+
+### 10.1 Initiation – pause CCM config=1
+
+This example shows a scenario where the MGC requests the MG to use pause and resume CCM signalling according to "config=1" and allows it to autonomously respond to requests. Autonomous requests are not supported. The SDP "nowait" parameter is included indicating that it will be the sole receiver. The MGC sends an SDP Offer with the following media description (see Table 2).
+
+**Table 2 – Example command encoding – (SIP) SDP offer**
+
+| (SIP) SDP encoding                                                                                                                                                                                                              | Comments                                                 |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|
+| <pre> v=0 o=alice 3203093520 3203093520 IN IP4 alice.example.com s=Pausing Media t=0 0 c=IN IP4 alice.example.com m=audio 49170 RTP/AVPF 98 99 a=rtpmap:98 G719/48000 a=rtpmap:99 PCMA/8000 a=rtcp-fb:* ccm pause nowait </pre> | The SDP Offer is as per section 10.1 of [IETF RFC 7728]. |
+
+The MGC maps this description into the Media Description in Table 3.
+
+**Table 3 – Example command encoding – MGC request**
+
+| ITU-T H.248 encoding (shortened command)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Comments                                                                                                                                                         |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Media {<br>Stream = 1 {<br>LocalControl {<br>repr/aq = Off,           ; No autonomous sending<br>; No repr/ar defaults to "on"<br>ReservedValue = On,   ; Reserve both audio formats<br>},<br>Remote {<br>c=IN IP4 alice.example.com<br>m=audio 49170 RTP/AVPF 98 99<br>a=rtpmap:98 G719/48000<br>a=rtpmap:99 PCMA/8000<br>a=rtcp-fb:* ccm pause nowait} ; Indicates pause ccm<br>; No config defaults to 1<br>},<br>Events=1234{               ; 3 Events are set as they are<br>repr/rtp,              ; all application to config=1<br>repr/dprreq,          ; no ssrc parameters are used.<br>repr/dprres},<br>}<br>}<br>} | A similar mapping would apply to the Local Descriptor. The Local Descriptor is not shown but it is also part of the Media Descriptor and will be sent to the MG. |
+
+## **10.2 Initiation – pause CCM config=5**
+
+This example shows a scenario where the MGC requests the MG to only respond to remote pause and resume requests using pause CCM signalling. This corresponds to "config=5". Autonomous response is allowed. Autonomous requests are not allowed due to the configuration. The MGC sends an SDP Offer with the following media description (see Table 4).
+
+**Table 4 – Example command encoding – (SIP) SDP offer**
+
+| (SIP) SDP encoding                                                                                                                                                                                                                                                      | Comments                                                                                              |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|
+| v=0<br>o=alice       3203093520       3203093520       IN       IP4<br>alice.example.com<br>s=Pausing Media<br>t=0 0<br>c=IN IP4 alice.example.com<br>m=audio 49170 RTP/AVPF 98 99<br>a=rtpmap:98 G719/48000<br>a=rtpmap:99 PCMA/8000<br>a=rtcp-fb:* ccm pause config=5 | The SDP Offer is as per section 10.1 of [IETF RFC 7728] except that the use of config=5 is signalled. |
+
+The MGC maps this description into the Media Description in Table 5.
+
+**Table 5 – Example command encoding – MGC request**
+
+| ITU-T H.248 encoding (shortened command)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Comments                                                                                                                                                                |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <pre> Media {   Stream = 1 {     LocalControl {       repr/aq = Off,      ; No autonomous sending                            ; No repr/ar defaults to "on"       ReservedValue = On, ; Reserve both audio formats     },     Remote { c=IN IP4 alice.example.com m=audio 49170 RTP/AVPF 98 99 a=rtpmap:98 G719/48000 a=rtpmap:99 PCMA/8000 a=rtcp-fb:* ccm pause config=3} ; Indicates pause ccms     },     Events=1234{      ; 2 Events are set as they are       repr/rtpops,    ; applicable to config=1       repr/dprreq    ; dprres is not required     },                ; no ssrc parameters are used.   } } </pre> | <p>A similar mapping would apply to the Local Descriptor. The Local Descriptor is not shown but it is also part of the Media Descriptor and will be sent to the MG.</p> |
+
+# Appendix I
+
+## Network use cases with ITU-T H.248 media gateways in the end-to-end RTP path with pause/resume signalling
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## I.1 Introduction
+
+Section 3 of [IETF RFC 7728] describes the main use cases for RTP sessions utilising RTP stream pause and resume. The example use cases consider the *unidirectional* RTP traffic flow between two or more RTP endpoints, with or without additional RTP nodes in between. Such interim RTP nodes realize a specific RTP topology function, which impact the variation of RTP pause/resume scenarios. This Appendix provides a mapping of the section 3 of [IETF RFC 7728] use cases on ITU-T H.248 gateways, i.e., when an ITU-T H.248 MG provides an RTP endpoint and an associated RTP topology function. The result of this analysis is a list of example reference network configurations with RTP stream pause and resume usage for a particular ITU-T H.248 gateway (profile).
+
+The ITU-T H.248 use cases might be classified in ITU-T H.248 Context models with a *single* (clause I.2), *two* (clause I.3) or *more than two* (clause I.4) ITU-T H.248 RTP-enabled Terminations.
+
+All use cases illustrate *only one traffic direction* (of a uni- or bidirectional RTP session) due to the asymmetric nature of RTP stream pause and resume between *RTP sender(s)* and *RTP receiver(s)*.
+
+## I.2 Single RTP Termination
+
+This use case relates to ITU-T H.248 connection models with a single RTP-enabled Termination per ITU-T H.248 Context. For instance, this use case includes all variants of ITU-T H.248 physical-to-RTP MG types within public switched telephone network (PSTN) emulation subsystems. The ITU-T H.248 RTP Termination represents an RTP endpoint, i.e., all RTCP packet types are terminated (inclusive of RTCP FB) and there are not any context-internal P/R-signalling aspects as opposed to subsequent use case discussions of the following clauses I.3 and I.4.
+
+## I.3 Dual RTP Terminations
+
+The notion of "dual RTP Terminations" relates to an ITU-T H.248 Context with two ITU-T H.248 RTP-enabled Terminations (which are labelled as T1 and T2) in the diagrams below. Section 3.1 of [IETF RFC 7728] provides use cases for a "*Point-to-Point*" RTP topology, from an end-to-end communication perspective. Such an end-to-end (RTP)-connection might be routed via an interim ITU-T H.248 IP-to-IP MG, which could have multiple different "RTP topology" modes, such as an *RTP media translator*, *RTP transport translator* or *Back-to-Back RTP end system* topology (see [ITU-T H.248.88]). This clause lists some use cases for such an ITU-T H.248 connection model, but without discussion of the applied RTP topology by the (T1, T2) Context configuration.
+
+Figure I.1 illustrates two use cases, termed "*point-to-point downstream*" and "*point-to-point upstream*".
+
+![Diagram showing Use case #1: PtP-Downstream. A flow goes from X' to X, then into an MG via T1, through IWF_RTP/IWF_RTCP, out via T2 to Y. A red dashed line for P/R-signalling goes from Y to T2. MGC controls MG via ITU-T H.248. Diagram showing Use case #2: PtP-Upstream. A flow goes from X' to X, then into an MG via T1, through IWF_RTP/IWF_RTCP, out via T2 to Y. A red dashed line for P/R-signalling goes from T1 to X. MGC controls MG via ITU-T H.248.](692541e65db4dc852988ce77ebb60ce5_img.jpg)
+
+Use case #1: PtP-Downstream
+
+Use case #2: PtP-Upstream
+
+Use case #2: PtP-Upstream
+
+- ➔ Unidirectional RTP stream (considered as "ITU-T H.248 RTP media flow")
+- ⅀ P/R-signalling (based on bidirectional RTCP FB message flows)
+- RTP source / RTP sink entity (identifiable via tuple of {SSRC, CNAME})
+- ◻ RTP node
+
+H.248.98(16)\_FI.1
+
+Diagram showing Use case #1: PtP-Downstream. A flow goes from X' to X, then into an MG via T1, through IWF\_RTP/IWF\_RTCP, out via T2 to Y. A red dashed line for P/R-signalling goes from Y to T2. MGC controls MG via ITU-T H.248. Diagram showing Use case #2: PtP-Upstream. A flow goes from X' to X, then into an MG via T1, through IWF\_RTP/IWF\_RTCP, out via T2 to Y. A red dashed line for P/R-signalling goes from T1 to X. MGC controls MG via ITU-T H.248.
+
+NOTE – The legend applies to all Figures in this appendix.
+
+**Figure I.1 – Use-cases #1 "Point-to-Point Downstream" & #2 "Point-to-Point Upstream"**
+
+Description of the remote RTP nodes (from an ITU-T H.248 MG perspective): Node Y is a pure *RTP sink*. Node X represents an optional, *virtual RTP source* (from MG perspective) because the real RTP source X' might not be visible from the MG perspective. There are RTCP-based services where the real RTP source X' might become visible, such as in the case of RTCP XR-based performance monitoring (see [b-ITU-T H.248.48] and [b-ITU-T H.248.87]).
+
+The ITU-T H.248 MG provides support of RTP stream pause and resume only in an outgoing (#1) or in an incoming (#2) RTP traffic direction. The P/R-signalling related RTCP packet types need to be terminated by the correspondent ITU-T H.248 Terminations (and not context-internally forwarded).
+
+Use cases #1 and #2 may be supported in parallel, leading to the configurations as outlined by Figure I.2.
+
+![Figure I.2: Use-cases #3 'Point-to-Point Downstream and Upstream'. The diagram is divided into two sections: #3a (Decoupled) and #3b (Coupled). Both show a flow from X' to X, then through a Media Gateway (MG) containing T1, IWF_RTCP, IWF_RTP, and T2, to Y. In #3a, red dashed lines show decoupled signalling loops from X to T1 and T2 to Y. In #3b, these loops are coupled via the MGC. A label H.248.98(16)_Fl.2 is at the bottom right.](08dce7ad4c512fdf0c0cde60415fade6_img.jpg)
+
+**Use case #3: PtP-Down- and Upstream**
+
+#3a: Decoupled (RTP)-connection-segments
+
+#3b: Coupled (RTP)-connection-segments
+
+H.248.98(16)\_Fl.2
+
+Figure I.2: Use-cases #3 'Point-to-Point Downstream and Upstream'. The diagram is divided into two sections: #3a (Decoupled) and #3b (Coupled). Both show a flow from X' to X, then through a Media Gateway (MG) containing T1, IWF\_RTCP, IWF\_RTP, and T2, to Y. In #3a, red dashed lines show decoupled signalling loops from X to T1 and T2 to Y. In #3b, these loops are coupled via the MGC. A label H.248.98(16)\_Fl.2 is at the bottom right.
+
+**Figure I.2 – Use-cases #3 "Point-to-Point Downstream and Upstream"**
+
+There are multiple options: first, the P/R-signalling loops might be fully decoupled (#3a) or coupled (#3b). It has to be emphasized that the P/R-signalling loops were intentionally established with a local scope (i.e., X-to-T1 and T2-to-Y) and not as a signal loop with a global scope (i.e., end-to-end loop between X and Y). Use case #3a looks similar as use case #1, with the difference that the MG is aware of P/R-signalling towards X. The decoupled mode (#3a) could lead to situations of a paused *RTP source* T2 but a still-playing *RTP source* X, which leads to the question of whether the MG should buffer or discard RTP packets received at T1? Due to the fact that P/R-signalling, defined by [IETF RFC 7728], is typically used for conversational services, the RTP packets are silently discarded.
+
+Use case #3b reflects the "coupled RTP stream pause and resume segments" case where the "RTP sink" requests to stop the RTP send process, meaning that the actual RTP source should be switched to pause mode (i.e., X or even X' and not T2). Hence, the two P/R-signalling loops need to be coupled. There are two coupling options: indirectly via the MGC or directly MG-internally.
+
+Finally, there might be a single, end-to-end P/R-signalling loop across the ITU-T H.248 MG, see Figure I.3.
+
+![Figure I.3: Use-cases #4 'Point-to-Point transparent'. The diagram shows a flow from X' to X, through a Media Gateway (MG) containing T1, IWF_RTCP, IWF_RTP, and T2, to Y. A single red dashed line represents an end-to-end signalling loop from X to Y. A label H.248.98(16)_Fl.3 is at the bottom right.](5478f70a6cef3e5672b2b22d28830cfb_img.jpg)
+
+**Use case #4: PtP-transparent**
+
+H.248.98(16)\_Fl.3
+
+Figure I.3: Use-cases #4 'Point-to-Point transparent'. The diagram shows a flow from X' to X, through a Media Gateway (MG) containing T1, IWF\_RTCP, IWF\_RTP, and T2, to Y. A single red dashed line represents an end-to-end signalling loop from X to Y. A label H.248.98(16)\_Fl.3 is at the bottom right.
+
+**Figure I.3 – Use-cases #4 "Point-to-Point transparent"**
+
+The "end-to-end" RTP stream pause and resume scope implies that neither termination T1 nor T2 provides an "RTP sender" or "RTP receiver" role. P/R-signalling information needs to be transparently forwarded by the MG. Such a forwarding requirement for dedicated RTCP packet types needs to be taking into account by a suitable RTP topology (see [b-ITU-T H.248.88]).
+
+## I.4 Multiple RTP Terminations
+
+This use case would be the result when an ITU-T H.248 MG realizes the "RTP mixer" function in all examples of sections 3.2 to 3.5 in [IETF RFC 7728].
+
+NOTE – Another multipoint configuration is the (RTP) *relay* topology in [IETF RFC 7728], which represents a "*RTP translator with only unicast paths*" according to [b-IETF RFC 7667].
+
+Figure I.4 illustrates a general multipoint configuration with enabled P/R-signalling between all RTP endpoints.
+
+![Diagram of Use case #5: Mixer / relay. It shows a central MG (Media Gateway) box containing three RTP terminations (T1.1, T1.2, T1.3) on the left and three (T2.1, T2.2, T2.3) on the right. A central dashed box labeled 'Mixer' IWF_RTP is connected to all six terminations. Above the MG, an MGC (Media Gateway Controller) is connected via an ITU-T H.248 interface. To the left of the MG are three RTP sources (X1, X2, X3) connected to T1.1, T1.2, and T1.3 respectively. To the right are three RTP sinks (Y1, Y2, Y3) connected to T2.1, T2.2, and T2.3 respectively. Red dashed lines with arrows indicate P/R-signalling paths from each source X and sink Y, through their respective terminations, into the central Mixer IWF_RTP box. A label 'IWF_RTCP' is shown above the Mixer box. The diagram is titled 'Use case #5: Mixer / relay' and signed 'H.248.98(16)_FI.4'.](a4b963a07cc368283154762c4b156fe7_img.jpg)
+
+Diagram of Use case #5: Mixer / relay. It shows a central MG (Media Gateway) box containing three RTP terminations (T1.1, T1.2, T1.3) on the left and three (T2.1, T2.2, T2.3) on the right. A central dashed box labeled 'Mixer' IWF\_RTP is connected to all six terminations. Above the MG, an MGC (Media Gateway Controller) is connected via an ITU-T H.248 interface. To the left of the MG are three RTP sources (X1, X2, X3) connected to T1.1, T1.2, and T1.3 respectively. To the right are three RTP sinks (Y1, Y2, Y3) connected to T2.1, T2.2, and T2.3 respectively. Red dashed lines with arrows indicate P/R-signalling paths from each source X and sink Y, through their respective terminations, into the central Mixer IWF\_RTP box. A label 'IWF\_RTCP' is shown above the Mixer box. The diagram is titled 'Use case #5: Mixer / relay' and signed 'H.248.98(16)\_FI.4'.
+
+**Figure I.4 – Use-case #5 "Multipoint-to-Multipoint" (with six RTP participants)**
+
+The MG behaviour (in use case #5) with respect to P/R-signalling handling is similar to that of use case #3, apart from the additional complexity that the MG-internal P/R-signalling interworking effort correlates with the applied mixer function for a multiparty, multimedia communication service. Three specific multipoint use case examples are discussed in more detail below.
+
+Figure I.5 illustrates a configuration for three RTP participants where the downstream RTP sink Y1 gets the RTP traffic forwarded from one-out-of-two upstream RTP sources X1 or X2.
+
+![Figure I.5: Use case #6: Mixer / relay. This diagram shows a network configuration where two senders, X1 and X2, are connected to a central MG (Media Gateway). X1 connects to T1.1 and X2 connects to T1.2. Both T1.1 and T1.2 are connected to a 'Switch' IWF_RTP block. The 'Switch' block is connected to T2.1, which in turn connects to receiver Y1. The MG is also connected to an MGC (Media Gateway Controller) via ITU-T H.248. Red dashed lines with arrows indicate P/R-signalling loops from X1 to T1.1, X2 to T1.2, and from the MG to Y1.](f9c64800d9bace9b4315646d1057be3c_img.jpg)
+
+H.248.98(16)\_FI.5
+
+Figure I.5: Use case #6: Mixer / relay. This diagram shows a network configuration where two senders, X1 and X2, are connected to a central MG (Media Gateway). X1 connects to T1.1 and X2 connects to T1.2. Both T1.1 and T1.2 are connected to a 'Switch' IWF\_RTP block. The 'Switch' block is connected to T2.1, which in turn connects to receiver Y1. The MG is also connected to an MGC (Media Gateway Controller) via ITU-T H.248. Red dashed lines with arrows indicate P/R-signalling loops from X1 to T1.1, X2 to T1.2, and from the MG to Y1.
+
+**Figure I.5 – Use-case #6 "Dual point-to-Point switching" (with three RTP participants)**
+
+Such a use case is, for example, discussed in section 10.3 of [IETF RFC 7728] ("voice activated mixer"). The two self-contained P/R-signalling loops X1-to-T1.1 and X2-to-T1.2 need to be coupled by the ITU-T H.248 gateway due to the applied service configuration.
+
+Figure I.6 illustrates a configuration between a sender X1 and two receivers Y1 and Y2 and an interim ITU-T H.248 MG in RTP transport relay topology (see also Figure 18 of [IETF RFC 7728]).
+
+![Figure I.6: Use case #7: Mixer / relay. This diagram shows a network configuration where a single sender, X1, is connected to T1.1 within an MG. T1.1 is connected to a 'Copy' IWF_RTP block. The 'Copy' block has two outputs, T2.1 and T2.2, which connect to receivers Y1 and Y2 respectively. The MG is also connected to an MGC via ITU-T H.248. Red dashed lines with arrows indicate P/R-signalling loops from X1 to T1.1, and from the MG to both Y1 and Y2.](9870bf462aa0d916a16d14b5a100c60a_img.jpg)
+
+H.248.98(16)\_FI.6
+
+Figure I.6: Use case #7: Mixer / relay. This diagram shows a network configuration where a single sender, X1, is connected to T1.1 within an MG. T1.1 is connected to a 'Copy' IWF\_RTP block. The 'Copy' block has two outputs, T2.1 and T2.2, which connect to receivers Y1 and Y2 respectively. The MG is also connected to an MGC via ITU-T H.248. Red dashed lines with arrows indicate P/R-signalling loops from X1 to T1.1, and from the MG to both Y1 and Y2.
+
+**Figure I.6 – Use-case #7 "Point-to-Dual point copying" (with three RTP participants) and a "P/R-signalling active MG"**
+
+Both receivers Y1 and Y2 may request the single sender X1 to pause the RTP playout process, hence there are inherent interactions between the concurrent P/R-signalling loops. Use case #7 represents a network configuration where the ITU-T H.248 gateway resolves such interactions. Use case #8 (Figure I.7) shows the same end-to-end scenario, but with a "dumb ITU-T H.248 gateway" because the MG transparently forwards all RTCP FB "P/R-signalling messages".
+
+![Diagram titled 'Use case #8: Mixer / relay' showing a network architecture. At the top, an MGC (Media Gateway Controller) is connected via an ITU-T H.248 protocol to a central MG (Media Gateway). The MG contains two dashed boxes: 'IWF_RTCP' and 'Copy IWF_RTP'. On the left, an RTP participant X1 is connected to a transcoder T1.1. The output of T1.1 enters the 'Copy IWF_RTP' box and is split to two other transcoders, T2.1 and T2.2. T2.1 is connected to participant Y1, and T2.2 is connected to participant Y2. Red dashed lines represent RTCP signaling paths: from X1 to the 'IWF_RTCP' box, from the 'IWF_RTCP' box to T2.1 and T2.2, and from T2.1 to Y1 and T2.2 to Y2. A small red arrow points to the RTCP path from X1. The diagram is labeled 'H.248.98(16)_FI.7' at the bottom right.](e451401f8fa77b466f401d5fce15b26c_img.jpg)
+
+Diagram titled 'Use case #8: Mixer / relay' showing a network architecture. At the top, an MGC (Media Gateway Controller) is connected via an ITU-T H.248 protocol to a central MG (Media Gateway). The MG contains two dashed boxes: 'IWF\_RTCP' and 'Copy IWF\_RTP'. On the left, an RTP participant X1 is connected to a transcoder T1.1. The output of T1.1 enters the 'Copy IWF\_RTP' box and is split to two other transcoders, T2.1 and T2.2. T2.1 is connected to participant Y1, and T2.2 is connected to participant Y2. Red dashed lines represent RTCP signaling paths: from X1 to the 'IWF\_RTCP' box, from the 'IWF\_RTCP' box to T2.1 and T2.2, and from T2.1 to Y1 and T2.2 to Y2. A small red arrow points to the RTCP path from X1. The diagram is labeled 'H.248.98(16)\_FI.7' at the bottom right.
+
+**Figure I.7 – Use-case #8 "Point-to-Dual point copying" (with three RTP participants) and a "P/R-signalling passive MG"**
+
+In summary, the ITU-T H.248 MG provides the same RTP topology in use cases #7 and #8, but each results in an ITU-T H.248 profile with and without ITU-T H.248 *rempr* package usage.
+
+# Appendix II
+
+## State models for pause/resume signalling endpoints
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## II.1 Introduction
+
+Section 6 of [IETF RFC 7728] defines the *RTP pause state model* at *RTP sender* side. This model is the normative framework for the ITU-T H.248 Events and Signals as defined by the *rempr* package in clause 9.
+
+The purpose of this Appendix is to illustrate and indicate the state transitions which are correlated with the ITU-T H.248 signalling elements. In case of any discrepancies between this Appendix and clause 8, the package specification in clause 9 takes precedence.
+
+## II.2 RTP pause state model at the RTP sender side
+
+Figure II.1 illustrates the *RTP sender* side state model.
+
+## II.3 RTP pause state model at the RTP receiver side
+
+Figure II.2 illustrates the *RTP receiver* side state model.
+
+![RTP sender (RTP source): RTP pause state model diagram showing states PLAYING, PAUSING, LOCAL PAUSED, and PAUSED with transitions and ITU-T H.248 signalling elements.](e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg)
+
+**RTP sender (RTP source): RTP pause state model**
+
+The diagram illustrates the RTP pause state model with four states: **PLAYING**, **PAUSING**, **LOCAL PAUSED**, and **PAUSED**. Transitions are triggered by local events, incoming P/R-signalling, or outgoing P/R-signalling.
+
+- PLAYING to PAUSING:** Triggered by *Received PAUSE* (incoming P/R-signalling) and *REFUSED reply* (outgoing P/R-signalling). The state returns to **PLAYING** upon *Received RESUME* (incoming P/R-signalling) with an *"OK"* response.
+- PLAYING to LOCAL PAUSED:** Triggered by *RESUME decision* (local event) and *Start RTP sent* (RTP stream).
+- PAUSING to LOCAL PAUSED:** Triggered by *Received RESUME* (incoming P/R-signalling) and *Start RTP sent* (RTP stream).
+- PAUSING to PAUSED:** Triggered by *Received PAUSE* (incoming P/R-signalling) and *Stop RTP sent* (RTP stream). A *Hold "off" timer* (local event) also triggers this transition, leading to a *PAUSED indication* (outgoing P/R-signalling).
+- LOCAL PAUSED to PAUSED:** Triggered by *PAUSE decision* (local event) and *PAUSED indication (tbc)* (outgoing P/R-signalling).
+- LOCAL PAUSED to PLAYING:** Triggered by *Received RESUME* (incoming P/R-signalling) and *REFUSED reply* (outgoing P/R-signalling).
+- PAUSED to PLAYING:** Triggered by *Received RESUME* (incoming P/R-signalling) and *REFUSED reply* (outgoing P/R-signalling).
+
+**ITU-T H.248 signalling:**
+
+- ITU-T H.248 event:** *rempr/rtpps {obstate="localResume", ssrc=...}*
+- ITU-T H.248 event:** *rempr/rtpps {obstate="resumed", ssrc=...}*
+- ITU-T H.248 event:** *rempr/rtpps {obstate="paused", ssrc=...}*
+- ITU-T H.248 event:** *rempr/dprreq {reqt="PAUSE", pauseid=..., ssrc=...}*
+- ITU-T H.248 event:** *rempr/dprreq {reqt="RESUME", pauseid=..., ssrc=...}*
+- ITU-T H.248 event:** *rempr/rtpps {obstate="localPause", ssrc=...}*
+- ITU-T H.248 signal:** *rempr/lpause {pauseid=..., ssrc=...}*
+- ITU-T H.248 signal:** *rempr/lresume {pauseid=..., ssrc=...}*
+- ITU-T H.248 signal:** *rempr/refuse {pauseid=..., ssrc=...}*
+
+**Legend - colour code**
+
+- Local event or decision (blue)
+- Incoming P/R-signalling (green)
+- Outgoing P/R-signalling (red)
+- RTP stream (purple)
+- ITU-T H.248 signalling element (dashed box)
+
+*Higher precedence than "Paused" state (because RTP receiver can't enforce state transition)*
+
+H.248.98(16)\_FII.1
+
+RTP sender (RTP source): RTP pause state model diagram showing states PLAYING, PAUSING, LOCAL PAUSED, and PAUSED with transitions and ITU-T H.248 signalling elements.
+
+NOTE – The state model indicates the main state transitions, but without any claim of complete- and correctness.
+
+**Figure II.1 – RTP sender (RTP source): RTP pause state model, extended with additional indication of ITU-T H.248 signalling elements**
+
+![State transition diagram for RTP pause state model. States: REMOTE PLAYING, REMOTE PAUSING, REMOTE PAUSED. Transitions are labeled with events like 'Sent PAUSE', 'REFUSED indication', 'Sent RESUME', 'OK', 'Expect incoming RTP', 'Expect no incoming RTP', and 'PAUSED indication'. The diagram is divided into three horizontal zones: Active, Pausing, and Paused.](77959075c823bb5169480d7b8ff82a63_img.jpg)
+
+| RTP sender (RTP sink): RTP pause state model                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | ITU-T H.248 signalling: |  |                         |                         |                         |            |                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--|-------------------------|-------------------------|-------------------------|------------|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <pre> stateDiagram-v2     state "REMOTE PLAYING" as RP     state "REMOTE PAUSING" as RPG     state "REMOTE PAUSED" as RPD      RP --&gt; RP : Sent PAUSE / REFUSED indication     RP --&gt; RPG : Sent PAUSE / Expect no incoming RTP     RPG --&gt; RP : Sent RESUME / "OK"     RPG --&gt; RPD : * / PAUSED indication     RPD --&gt; RP : Sent RESUME / Expect incoming RTP     RPD --&gt; RPD : Sent RESUME / REFUSED indication     RP --&gt; RPD : Sent RESUME / Expect incoming RTP </pre> <table border="1"> <tr><td colspan="2">Legend - colour code</td></tr> <tr><td>Local event or decision</td></tr> <tr><td>Incoming P/R-signalling</td></tr> <tr><td>Outgoing P/R-signalling</td></tr> <tr><td>RTP stream</td></tr> <tr><td>ITU-T H.248 signalling element</td></tr> </table> | Legend - colour code    |  | Local event or decision | Incoming P/R-signalling | Outgoing P/R-signalling | RTP stream | ITU-T H.248 signalling element | <div style="border: 1px dashed black; margin: 5px; padding: 2px;"> ITU-T H.248 signal:<br/> rempr/rpause {<br/> pauseid=..., ssrc=... } </div> <div style="border: 1px dashed black; margin: 5px; padding: 2px;"> ITU-T H.248 signal:<br/> rempr/rresume {<br/> pauseid=..., ssrc=... } </div> <div style="border: 1px dashed black; margin: 5px; padding: 2px;"> ITU-T H.248 event:<br/> rempr/dprres {<br/> rest="refused",<br/> pauseid=..., ssrc=... } </div> <div style="border: 1px dashed black; margin: 5px; padding: 2px;"> ITU-T H.248 event:<br/> rempr/dprres {<br/> rest="paused",<br/> pauseid=..., ssrc=... } </div> |
+| Legend - colour code                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                         |  |                         |                         |                         |            |                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| Local event or decision                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                         |  |                         |                         |                         |            |                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| Incoming P/R-signalling                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                         |  |                         |                         |                         |            |                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| Outgoing P/R-signalling                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                         |  |                         |                         |                         |            |                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| RTP stream                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                         |  |                         |                         |                         |            |                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| ITU-T H.248 signalling element                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                         |  |                         |                         |                         |            |                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+State transition diagram for RTP pause state model. States: REMOTE PLAYING, REMOTE PAUSING, REMOTE PAUSED. Transitions are labeled with events like 'Sent PAUSE', 'REFUSED indication', 'Sent RESUME', 'OK', 'Expect incoming RTP', 'Expect no incoming RTP', and 'PAUSED indication'. The diagram is divided into three horizontal zones: Active, Pausing, and Paused.
+
+H.248.98(16)\_FII.2
+
+NOTE – The state model indicates the main state transitions, but without any claim of complete- and corrections.
+
+**Figure II.2 – RTP receiver (RTP sink): RTP pause state model, extended with additional indication of ITU-T H.248 signalling elements**
+
+## Appendix III
+
+## SSRC identifiers for pause/resume signalling endpoints
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## III.1 SSRC information in RTCP FB "pause/resume" messages
+
+Figure III.1 outlines the structure of such a RTCP FB message type.
+
+![Diagram of RTCP FB packet structure for pause/resume. The packet is divided into a Header and a Chunk. The Header contains fields: ..., FMT (...), PT, and Length. The Chunk contains SSRC #1 (Packet sender), SSRC #2 (Media source), and FCI (Feedback control information). SSRC #1 is mapped to the SSRC of the 'PAU/RES' RTP sender/receiver. SSRC #2 is set to 0. SSRC #3 (Target) is mapped to the ITU-T H.248 ssrc parameter. The FCI contains Msg Type, ..., PauseID, and Type specific info. A table below defines the 'PAU/RES' feedback messages.](0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg)
+
+RTCP FB packet ("Feedback messages for pause/resume", **RFC STREAM PAUSE**)
+
+| "PAU/RES"- Feedback messages |              |                    |
+|------------------------------|--------------|--------------------|
+| Name                         | Type         | Directionality     |
+| PAUSE                        | Request      | Receiver-to-sender |
+| RESUME                       | Request      | Receiver-to-sender |
+| PAUSED                       | Indication   | Sender-to-receiver |
+| REFUSED                      | Notification | Sender-to-receiver |
+
+H.248.98(16)\_FIII.1
+
+Diagram of RTCP FB packet structure for pause/resume. The packet is divided into a Header and a Chunk. The Header contains fields: ..., FMT (...), PT, and Length. The Chunk contains SSRC #1 (Packet sender), SSRC #2 (Media source), and FCI (Feedback control information). SSRC #1 is mapped to the SSRC of the 'PAU/RES' RTP sender/receiver. SSRC #2 is set to 0. SSRC #3 (Target) is mapped to the ITU-T H.248 ssrc parameter. The FCI contains Msg Type, ..., PauseID, and Type specific info. A table below defines the 'PAU/RES' feedback messages.
+
+**Figure III.1 – RTCP FB packets for pause/resume-signalling – SSRC related fields**
+
+There are (at least) three SSRC identifiers in such a RTCP FB packet:
+
+1. **SSRC packet sender:** the SSRC of the RTP endpoint issuing a P/R-signalling message in an *RTP sender* or *RTP receiver* role;
+2. **SSRC media source:** original semantic see [IETF RFC 5104], not used in P/R-signalling messages, set to value '0'; and
+3. **SSRC target:** the SSRC of the remote RTP endpoint acting as the target of P/R-signalling (i.e., the associated *RTP sender* or *RTP receiver*).
+
+It could be concluded that the ITU-T H.248 signalled *ssrc* parameter (as part of event configuration, event notification and signal configuration) is either mapped on SSRC #1 (packet sender) or SSRC #3 (target), dependent whether the ITU-T H.248 unidirectional media stream endpoint is acting in *RTP sender* or *RTP receiver* role.
+
+## III.2 Example use case
+
+Figure III.2 provides an example, based on use case #3b from Appendix I, extended to bidirectional support of P/R-signalling. The ITU-T H.248 *rempr* package supports this case, which facilitates understanding the scope of the *ssrc* information in ITU-T H.248 Signals and Events of this package. Note that the MG provides an [ITU-T H.248.88] B2BRE RTP topology. Other RTP topologies might lead to different SSRC assignments. Figure III.2 outlines the SSRC values which appear in the SSRC fields #1 and #3 of the RTCP FB packets.
+
+![Diagram of Use case #3b showing RTP streams and P/R-signalling between entities X', X, MG (containing T1, IWF_RTCP, IWF_RTP, T2), and Y. It includes a legend for RTP streams, P/R-signalling, and various entity types.](9a5927586a691c4908aa2cf98bd47ebb_img.jpg)
+
+**Use case #3b: PtP-Down- and Upstream (coupled (RTP)-connection-segments)**
+
+The diagram illustrates a network architecture for ITU-T H.248. At the top, an **MGC** (Media Gateway Controller) is connected to the **MG** (Media Gateway) via an **ITU-T H.248** interface. The **MG** contains two **T** (Terminal) entities, **T1** and **T2**. Between **T1** and **T2** are two **IWF** (Interworking Function) blocks: **IWF\_RTCP** and **IWF\_RTP**. The **MG** is connected to an **RTP endpoint** **X** on the left and an **RTP endpoint** **Y** on the right. **RTP endpoint** **X** is further connected to an **RTP node** **X'**. **RTP endpoint** **Y** is connected to another **RTP node**. **RTP source / RTP sink entities** are identified by green labels: **SSRC<sub>X</sub>** (on **X'**), **SSRC<sub>T1</sub>** (on **T1**), **SSRC<sub>T2</sub>** (on **T2**), and **SSRC<sub>Y</sub>** (on **Y**). Solid black arrows represent **Unidirectional RTP stream (considered as "ITU-T H.248 RTP media flow")**. Red dashed arrows represent **P/R-signalling (based on bidirectional RTCP FB message flows)**. A legend at the bottom defines the symbols: solid arrow for RTP stream, red dashed arrow for P/R-signalling, circle for RTP source / sink entity, circle with a diagonal line for "P/R" RTP sender, circle with a cross for "P/R" RTP receiver, rectangle for RTP node, and dashed rectangle for RTP endpoint.
+
+→ Unidirectional RTP stream (considered as "ITU-T H.248 RTP media flow")
+
+← P/R-signalling (based on bidirectional RTCP FB message flows)
+
+○ RTP source / RTP sink entity (identifiable via tuple of {SSRC, CNAME})
+
+⌚ "P/R" RTP sender      ⊕ "P/R" RTP receiver
+
+□ RTP node              ▭ RTP endpoint
+
+H.248.98(16)\_FIII.2
+
+Diagram of Use case #3b showing RTP streams and P/R-signalling between entities X', X, MG (containing T1, IWF\_RTCP, IWF\_RTP, T2), and Y. It includes a legend for RTP streams, P/R-signalling, and various entity types.
+
+**Figure III.2 – Example use case #3b (from Appendix I) – Extended for bidirectional P/R-signalling and indication of SSRCs**
+
+# Bibliography
+
+- [b-ITU-T H.248.48] Recommendation ITU-T H.248.48 (2012), *Gateway control protocol: RTCP XR block reporting package*.
+- [b-ITU-T H.248.66] Recommendation ITU-T H.248.66 (2016), *Gateway control protocol: Packages for RTSP and H.248 interworking*.
+- [b-ITU-T H.248.82] Recommendation ITU-T H.248.82 (2013), *Gateway control protocol: Explicit congestion notification support*.
+- [b-ITU-T H.248.87] Recommendation ITU-T H.248.87 (2014), *Gateway control protocol: Guidelines on the use of ITU-T H.248 capabilities for performance monitoring in RTP networks in ITU-T H.248 profiles*.
+- [b-ITU-T H.248.96] Recommendation ITU-T H.248.96 (2015), *Gateway control protocol: ITU-T H.248 Stream grouping and aggregation*.
+- [b-IETF RFC 7656] IETF RFC 7656 (2015), *A Taxonomy of Semantics and Mechanisms for Real-Time Transport Protocol (RTP) Sources*.
+- [b-IETF RFC 7667] IETF RFC 7667 (2015), *RTP Topologies*.
+- [b-IETF BUNDLE] IETF draft-ietf-mmusic-sdp-bundle-negotiation-27 (2016), *Negotiating Media Multiplexing Using the Session Description Protocol (SDP)*.  
+<<https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-bundle-negotiation/>>
+
+
+
+# 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.261-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.261-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a2c75e11b04fd127605d60df9ed262f9f8382010
--- /dev/null
+++ b/marked/H/T-REC-H.261-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0cb103d466efaa003d84459d191ea40fc82a8118b924d7216e270b4deda6874f
+size 8276
diff --git a/marked/H/T-REC-H.261-199303-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg b/marked/H/T-REC-H.261-199303-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b207baa92c6a46c2015862ce5e79cbc2a75ecfb9
--- /dev/null
+++ b/marked/H/T-REC-H.261-199303-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bbba6b7be650aa7fb5bd43a7f2ba92de9f041158b47b8f4d56224d142c71e474
+size 29597
diff --git a/marked/H/T-REC-H.261-199303-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/H/T-REC-H.261-199303-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..654b5e2e79108425305ea55c4657cbe778464eaf
--- /dev/null
+++ b/marked/H/T-REC-H.261-199303-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3ed1e78dcf3f9af221677e247ab25637d4019435ce6507666ad6a8e4c77e3517
+size 11065
diff --git a/marked/H/T-REC-H.261-199303-I_PDF-E/4636adff5682a064f0ae5f13a1d464a6_img.jpg b/marked/H/T-REC-H.261-199303-I_PDF-E/4636adff5682a064f0ae5f13a1d464a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..21afe89c1eb7351425508cc9b06092a387675226
--- /dev/null
+++ b/marked/H/T-REC-H.261-199303-I_PDF-E/4636adff5682a064f0ae5f13a1d464a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e5120f330fc0a0efb90138713af206d03af76e502a38337b00cb74c5412fef72
+size 11238
diff --git a/marked/H/T-REC-H.261-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg b/marked/H/T-REC-H.261-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..eaaa1daef160913732712ad29485e6fd4177a712
--- /dev/null
+++ b/marked/H/T-REC-H.261-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ac9ba1664aa9f58ce17480de744080f631eadcd7ac1f088602b63442e8a2baab
+size 58930
diff --git a/marked/H/T-REC-H.261-199303-I_PDF-E/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg b/marked/H/T-REC-H.261-199303-I_PDF-E/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f912fbb0cd10f29b625b343c16815a89aa37c108
--- /dev/null
+++ b/marked/H/T-REC-H.261-199303-I_PDF-E/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c2e331a8dce52204b6a9913adc01043a5db8fc525965d93f2072acd929aeae75
+size 43570
diff --git a/marked/H/T-REC-H.261-199303-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/H/T-REC-H.261-199303-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2ec9e27a8a0086e12743dcd0a740139e0957dad8
--- /dev/null
+++ b/marked/H/T-REC-H.261-199303-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1a1b73a98ef529cc40b986aecb1854f1db063063e8169a5043ff3d3a3aceaf2d
+size 16542
diff --git a/marked/H/T-REC-H.261-199303-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/H/T-REC-H.261-199303-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..054e19ccd5c956c19bfb19b757773148e526230c
--- /dev/null
+++ b/marked/H/T-REC-H.261-199303-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7de626f9d1515d1473641d07b08c58df6cfa6564b5b309e0d7ceca732fd39804
+size 11244
diff --git a/marked/H/T-REC-H.261-199303-I_PDF-E/bfb6d182d624680db577069bbc0b2a93_img.jpg b/marked/H/T-REC-H.261-199303-I_PDF-E/bfb6d182d624680db577069bbc0b2a93_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..386613cf0fe0e56ecd41d43ef91161954a743850
--- /dev/null
+++ b/marked/H/T-REC-H.261-199303-I_PDF-E/bfb6d182d624680db577069bbc0b2a93_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88ea597ed77c3abde88db22559a23c184d53952b85254c9ed772f91a100f6dcc
+size 31820
diff --git a/marked/H/T-REC-H.261-199303-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/H/T-REC-H.261-199303-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..feeaef8bb66da1dbb5865f4ac3a82eadd05b62d7
--- /dev/null
+++ b/marked/H/T-REC-H.261-199303-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7e3dcfde12dcd1d8b428548658c1e514369cf72d89e87774a6dc4019e22291ed
+size 136774
diff --git a/marked/H/T-REC-H.261-199303-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/H/T-REC-H.261-199303-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ee3ea95d4a59ed3f7ccd84cad52ac7e543ba78b8
--- /dev/null
+++ b/marked/H/T-REC-H.261-199303-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4b12defa5669cab261ae6beb71834c840a8076c657ab682ff8cb7ecda329ac74
+size 12282
diff --git a/marked/H/T-REC-H.261-199303-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/H/T-REC-H.261-199303-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ed4b1b79ba0e738d2103b9b1dc3c243119c72a7a
--- /dev/null
+++ b/marked/H/T-REC-H.261-199303-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:044df3ccfe1d41a919ac29104a82d58ee8b5172f8db3edbbbc2af7d58bdbe5da
+size 58454
diff --git a/marked/H/T-REC-H.261-199303-I_PDF-E/raw.md b/marked/H/T-REC-H.261-199303-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..07b16962637c4a697b9398281fccbf90975f54ac
--- /dev/null
+++ b/marked/H/T-REC-H.261-199303-I_PDF-E/raw.md
@@ -0,0 +1,1184 @@
+
+
+![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.261**
+
+(03/93)
+
+**LINE TRANSMISSION OF NON-TELEPHONE  
+SIGNALS**
+
+---
+
+**VIDEO CODEC FOR AUDIOVISUAL  
+SERVICES AT  $p \times 64$  kbits**
+
+**ITU-T Recommendation H.261**
+
+(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.261 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
+
+|     |                                                          | <i>Page</i> |
+|-----|----------------------------------------------------------|-------------|
+| 1   | Scope.....                                               | 1           |
+| 2   | Brief specification .....                                | 1           |
+| 2.1 | Video input and output .....                             | 2           |
+| 2.2 | Digital output and input .....                           | 2           |
+| 2.3 | Sampling frequency .....                                 | 2           |
+| 2.4 | Source coding algorithm.....                             | 2           |
+| 2.5 | Bit rate .....                                           | 2           |
+| 2.6 | Symmetry of transmission.....                            | 3           |
+| 2.7 | Error handling.....                                      | 3           |
+| 2.8 | Multipoint operation .....                               | 3           |
+| 3   | Source coder.....                                        | 3           |
+| 3.1 | Source format .....                                      | 3           |
+| 3.2 | Video source coding algorithm.....                       | 3           |
+| 3.3 | Coding control .....                                     | 6           |
+| 3.4 | Forced updating .....                                    | 6           |
+| 4   | Video multiplex coder.....                               | 7           |
+| 4.1 | Data structure.....                                      | 7           |
+| 4.2 | Video multiplex arrangement .....                        | 7           |
+| 4.3 | Multipoint considerations .....                          | 18          |
+| 5   | Transmission coder .....                                 | 19          |
+| 5.1 | Bit rate .....                                           | 19          |
+| 5.2 | Video data buffering .....                               | 19          |
+| 5.3 | Video coding delay .....                                 | 20          |
+| 5.4 | Forward error correction for coded video signal .....    | 20          |
+|     | Annex A – Inverse transform accuracy specification ..... | 21          |
+|     | Annex B – Hypothetical reference decoder .....           | 22          |
+|     | Annex C – Codec delay measurement method .....           | 23          |
+|     | Annex D – Still image transmission .....                 | 24          |
+
+
+
+# **VIDEO CODEC FOR AUDIOVISUAL SERVICES AT $p \times 64$ kbit/s**
+
+*(Geneva, 1990; revised at Helsinki, 1993)*
+
+The CCITT,
+
+*considering*
+
+- (a) that there is significant customer demand for videophone, videoconference and other audiovisual services;
+- (b) that circuits to meet this demand can be provided by digital transmission using the B, H<sub>0</sub> rates or their multiples up to the primary rate or H<sub>11</sub>/H<sub>12</sub> rates;
+- (c) that ISDNs are likely to be available in some countries that provide a switched transmission service at the B, H<sub>0</sub> or H<sub>11</sub>/H<sub>12</sub> rate;
+- (d) 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;
+- (e) that a number of audiovisual services are likely to appear using basic and primary rate ISDN accesses and that some means of intercommunication among these terminals should be possible;
+- (f) that the video codec provides an essential element of the infrastructure for audiovisual services which allows such intercommunication in the framework of Recommendation H.200;
+- (g) that Recommendation H.120 for videoconferencing using primary digital group transmission was the first in an evolving series of Recommendations,
+
+*appreciating*
+
+that advances have been made in research and development of video coding and bit rate reduction techniques which lead to the use of lower bit rates down to 64 kbit/s so that this may be considered as the second in the evolving series of Recommendations,
+
+*and noting*
+
+that it is the basic objective of the CCITT to recommend unique solutions for international connections,
+
+*recommends*
+
+that in addition to those codecs complying to Recommendation H.120, codecs having signal processing and transmission coding characteristics described below should be used for international audiovisual services.
+
+# **NOTES**
+
+- 1 Codecs of this type are also suitable for some television services where full broadcast quality is not required.
+- 2 Equipment for transcoding from and to codecs according to Recommendation H.120 is under study.
+
+# **1 Scope**
+
+This Recommendation describes the video coding and decoding methods for the moving picture component of audiovisual services at the rates of  $p \times 64$  kbit/s, where  $p$  is in the range 1 to 30.
+
+# **2 Brief specification**
+
+An outline block diagram of the codec is given in Figure 1.
+
+![Outline block diagram of the video codec showing the video coder and video decoder paths.](547f726730e589392f239257a833ede3_img.jpg)
+
+The diagram illustrates the outline block diagram of the video codec, divided into two main sections: a) Video coder and b) Video decoder. Both sections are enclosed in a dashed rectangular box.
+
+**a) Video coder:** The process starts with a 'Video signal' input on the left. It passes through a 'Source coder', then a 'Video multiplex coder', then a 'Transmission buffer', and finally a 'Transmission coder', which outputs a 'Coded bit stream' on the right. A 'Coding control' block is positioned above the 'Source coder' and 'Video multiplex coder', receiving input from the 'Transmission buffer' and providing control signals to both. An 'External control' input is shown at the top, pointing into the 'Coding control' block.
+
+**b) Video decoder:** The process starts with the 'Coded bit stream' input on the right. It passes through a 'Receiving decoder', then a 'Receiving buffer', then a 'Video multiplex decoder', and finally a 'Source decoder', which outputs the reconstructed 'Video signal' on the left.
+
+T1502430-90/d01
+
+Outline block diagram of the video codec showing the video coder and video decoder paths.
+
+FIGURE 1/H.261  
+**Outline block diagram of the video codec**
+
+## 2.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 source coder operates on pictures based on a common intermediate format (CIF). 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.
+
+## 2.2 Digital output and input
+
+The video coder provides a self-contained digital bit stream which may be combined with other multi-facility signals (for example as defined in Recommendation H.221). The video decoder performs the reverse process.
+
+## 2.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.
+
+## 2.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.
+
+## 2.5 Bit rate
+
+This Recommendation is primarily intended for use at video bit rates between approximately 40 kbit/s and 2 Mbit/s.
+
+## 2.6 Symmetry of transmission
+
+The codec may be used for bidirectional or unidirectional visual communication.
+
+## 2.7 Error handling
+
+The transmitted bit-stream contains a BCH code (Bose, Chaudhuri and Hocquengham) (511,493) forward error correction code. Use of this by the decoder is optional.
+
+## 2.8 Multipoint operation
+
+Features necessary to support switched multipoint operation are included.
+
+# 3 Source coder
+
+## 3.1 Source format
+
+The source coder operates on non-interlaced pictures occurring 30 000/1001 (approximately 29.97) times per second. The tolerance on picture 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 CCIR Recommendation 601.
+
+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.
+
+Two picture scanning formats are specified.
+
+In the first format (CIF), the luminance sampling structure is 352 pels per line, 288 lines per picture in an orthogonal arrangement. Sampling of each of the two colour difference components is at 176 pels per line, 144 lines per picture, orthogonal. Colour difference samples are sited such that their block boundaries coincide with luminance block boundaries as shown in Figure 2. The picture area covered by these numbers of pels and lines has an aspect ratio of 4:3 and corresponds to the active portion of the local standard video input.
+
+NOTE – The number of pels per line is compatible 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 CCIR Recommendation 601.
+
+The second format, quarter-CIF (QCIF), has half the number of pels and half the number of lines stated above. All codecs must be able to operate using QCIF. Some codecs can also operate with CIF.
+
+Means shall be provided to restrict the maximum picture rate of encoders by having at least 0, 1, 2 or 3 non-transmitted pictures between transmitted ones. Selection of this minimum number and CIF or QCIF shall be by external means (for example via Recommendation H.221).
+
+## 3.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.
+
+The prediction error (INTER mode) or the input picture (INTRA mode) is subdivided into 8 pel by 8 line blocks which are segmented as transmitted or non-transmitted. Further, four luminance blocks and the two spatially corresponding colour difference blocks are combined to form a macroblock as shown in Figure 10.
+
+![Diagram showing the positioning of luminance and chrominance samples. It features a 6x6 grid of 'X' symbols representing luminance samples. Superimposed on this grid are four 'O' symbols representing chrominance samples, each centered within a 2x2 quadrant of 'X's. The grid is divided into four quadrants by a horizontal and a vertical dashed line representing block edges. A legend below the grid defines 'X' as a Luminance sample, 'O' as a Chrominance sample, and a dashed line as a Block edge. The identifier 'T1508180-92/d02' is in the bottom right.](3121ebddccf183ca63bb9781be440a7e_img.jpg)
+
+T1508180-92/d02
+
+X Luminance sample
+
+O Chrominance sample
+
+Block edge
+
+Diagram showing the positioning of luminance and chrominance samples. It features a 6x6 grid of 'X' symbols representing luminance samples. Superimposed on this grid are four 'O' symbols representing chrominance samples, each centered within a 2x2 quadrant of 'X's. The grid is divided into four quadrants by a horizontal and a vertical dashed line representing block edges. A legend below the grid defines 'X' as a Luminance sample, 'O' as a Chrominance sample, and a dashed line as a Block edge. The identifier 'T1508180-92/d02' is in the bottom right.
+
+FIGURE 2/H.261  
+**Positioning of luminance and chrominance samples**
+
+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 variable length coded.
+
+### **3.2.1 Prediction**
+
+The prediction is inter-picture and may be augmented by motion compensation (see 3.2.2) and a spatial filter (see 3.2.3).
+
+### **3.2.2 Motion compensation**
+
+Motion compensation (MC) is optional in the encoder. The decoder will accept one vector per macroblock. Both horizontal and vertical components of these motion vectors have integer values not exceeding  $\pm 15$ . The vector is used for all four luminance blocks in the macroblock. The motion vector for both colour difference blocks is derived by halving the component values of the macroblock vector and truncating the magnitude parts towards zero to yield integer components.
+
+A positive value of the horizontal or vertical component of the motion vector signifies that the prediction is formed from pels in the previous picture which are spatially to the right or below the pels being predicted.
+
+Motion vectors are restricted such that all pels referenced by them are within the coded picture area.
+
+![Block diagram of the H.261 source coder. The diagram shows the flow of video data from 'Video in' through various processing blocks. The main path consists of a subtraction node (circle with a minus sign), a dashed box containing a switch and a '0' input, a 'Transform' (T) block, a 'Quantizer' (Q) block, an inverse quantizer (Q⁻¹) block, an inverse transform (T⁻¹) block, and an addition node (circle with a plus sign). The output of the addition node goes to a 'Picture memory with motion compensated variable delay' (P) block, which outputs 'v' (Motion vector). The output of the P block goes to a 'Loop filter' (F) block, which outputs 'f' (Switching on/off of the loop filter). The output of the F block is fed back to the subtraction node. A 'Coding control' (CC) block at the top receives inputs from the subtraction node and the P block, and outputs 'p' (Flag for INTRA/INTER), 't' (Flag for transmitted or not), and 'qz' (Quantizer indication). The 'qz' output is also fed back to the subtraction node. The outputs 'p', 't', 'qz', 'q' (Quantizing index for transform coefficients), 'v', and 'f' are grouped by a bracket and labeled 'To video multiplex coder'. The diagram is labeled 'T1502441-90/d03' at the bottom right.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg)
+
+Block diagram of the H.261 source coder. The diagram shows the flow of video data from 'Video in' through various processing blocks. The main path consists of a subtraction node (circle with a minus sign), a dashed box containing a switch and a '0' input, a 'Transform' (T) block, a 'Quantizer' (Q) block, an inverse quantizer (Q⁻¹) block, an inverse transform (T⁻¹) block, and an addition node (circle with a plus sign). The output of the addition node goes to a 'Picture memory with motion compensated variable delay' (P) block, which outputs 'v' (Motion vector). The output of the P block goes to a 'Loop filter' (F) block, which outputs 'f' (Switching on/off of the loop filter). The output of the F block is fed back to the subtraction node. A 'Coding control' (CC) block at the top receives inputs from the subtraction node and the P block, and outputs 'p' (Flag for INTRA/INTER), 't' (Flag for transmitted or not), and 'qz' (Quantizer indication). The 'qz' output is also fed back to the subtraction node. The outputs 'p', 't', 'qz', 'q' (Quantizing index for transform coefficients), 'v', and 'f' are grouped by a bracket and labeled 'To video multiplex coder'. The diagram is labeled 'T1502441-90/d03' at the bottom right.
+
+- T Transform
+- Q Quantizer
+- P Picture memory with motion compensated variable delay
+- F Loop filter
+- 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
+- f Switching on/off of the loop filter
+
+FIGURE 3/H.261  
+Source coder
+
+### 3.2.3 Loop filter
+
+The prediction process may be modified by a two-dimensional spatial filter (FIL) which operates on pels within a predicted 8 by 8 block.
+
+The filter is separable into one-dimensional horizontal and vertical functions. Both are non-recursive with coefficients of 1/4, 1/2, 1/4 except at block edges where one of the taps would fall outside the block. In such cases the 1-D filter is changed to have coefficients of 0, 1, 0. Full arithmetic precision is retained with rounding to 8 bit integer values at the 2-D filter output. Values whose fractional part is one half are rounded up.
+
+The filter is switched on/off for all six blocks in a macroblock according to the macroblock type (see 4.2.3, MTYPE).
+
+### 3.2.4 Transformer
+
+Transmitted blocks are first processed by a separable two-dimensional 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[\pi(2x + 1)u/16] \cos[\pi(2y + 1)v/16]$$
+
+with  $u, v, x, y = 0, 1, 2, \dots, 7$
+
+where  $x, y =$  spatial coordinates in the pel domain,
+
+$u, v =$  coordinates in the transform domain,
+
+$$C(u) = 1/\sqrt{2} \text{ for } u = 0; \text{ otherwise } 1,$$
+
+$$C(v) = 1/\sqrt{2} \text{ for } v = 0; \text{ otherwise } 1.$$
+
+NOTE – Within the block being transformed,  $x = 0$  and  $y = 0$  refer to the pel nearest the left and top edges of the picture, respectively.
+
+The arithmetic procedures for computing the transforms are not defined, but the inverse one should meet the error tolerance specified in Annex A.
+
+### 3.2.5 Quantization
+
+The number of quantizers is 1 for the INTRA dc coefficient and 31 for all other coefficients. Within a macroblock the same quantizer is used for all coefficients except the INTRA dc one. The decision levels are not defined. The INTRA dc coefficient is nominally the transform value linearly quantized with a stepsize of 8 and no dead-zone. Each of the other 31 quantizers is also nominally linear but with a central dead-zone around zero and with a step size of an even value in the range 2 to 62.
+
+The reconstruction levels are as defined in 4.2.4.
+
+NOTE – For the smaller quantization step sizes, the full dynamic range of the transform coefficients cannot be represented.
+
+### 3.2.6 Clipping of reconstructed picture
+
+To prevent quantization distortion of transform coefficient amplitudes causing arithmetic overflow in the encoder and decoder loops, clipping functions are inserted. The clipping function is applied to the reconstructed picture which is formed by summing the prediction and the prediction error as modified by the coding process. This clipper operates on resulting pel values less than 0 or greater than 255, changing them to 0 and 255, respectively.
+
+## 3.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 sub-sampling. The proportions of such measures in the overall control strategy are not subject to recommendation.
+
+When invoked, temporal sub-sampling is performed by discarding complete pictures.
+
+## 3.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. For control of accumulation of inverse transform mismatch error a macroblock should be forcibly updated at least once per every 132 times it is transmitted.
+
+# 4 Video multiplex coder
+
+## 4.1 Data structure
+
+Unless specified otherwise the most significant bit is transmitted first. This is bit 1 and is the leftmost bit in the code tables in this Recommendation. Unless specified otherwise all unused or spare bits are set to “1”. Spare bits must not be used until their functions are specified by the CCITT.
+
+## 4.2 Video multiplex arrangement
+
+The video multiplex is arranged in a hierarchical structure with four layers. From top to bottom the layers are:
+
+- picture;
+- Group of blocks (GOB);
+- Macroblock (MB);
+- Block.
+
+A syntax diagram of the video multiplex coder is shown in Figure 4. Abbreviations are defined in later subclauses.
+
+### 4.2.1 Picture layer
+
+Data for each picture consists of a picture header followed by data for GOBs. The structure is shown in Figure 5. Picture headers for dropped pictures are not transmitted.
+
+#### 4.2.1.1 Picture start code (PSC) (20 bits)
+
+A word of 20 bits. Its value is 0000 0000 0000 0001 0000.
+
+#### 4.2.1.2 Temporal reference (TR) (5 bits)
+
+A 5-bit number which can have 32 possible values. It is formed by incrementing its value in the previously transmitted picture header by one plus the number of non-transmitted pictures (at 29.97 Hz) since that last transmitted one. The arithmetic is performed with only the five LSBs.
+
+#### 4.2.1.3 Type information (PTYPE) (6 bits)
+
+Information about the complete picture:
+
+- Bit 1 Split screen indicator, “0” off, “1” on;
+- Bit 2 Document camera indicator, “0” off, “1” on;
+- Bit 3 Freeze picture release, “0” off, “1” on;
+- Bit 4 Source format, “0” QCIF, “1” CIF;
+- Bit 5 Optional still image mode HI\_RES defined in Annex D; “0” on, “1” off;
+- Bit 6 Spare.
+
+#### 4.2.1.4 Extra insertion information (PEI) (1 bit)
+
+A bit which when set to “1” signals the presence of the following optional data field.
+
+#### 4.2.1.5 Spare information (PSPARE) (0/8/16 . . . bits)
+
+If PEI is set to “1”, then 9 bits follow consisting of 8 bits of data (PSPARE) and then another PEI bit to indicate if a further 9 bits follow and so on. Encoders must not insert PSPARE until specified by the CCITT. Decoders must be designed to discard PSPARE if PEI is set to 1. This will allow the CCITT to specify future backward compatible additions in PSPARE.
+
+![Syntax diagram for the Picture layer. It shows a sequence of elements: PSC (fixed length), TR (fixed length), PTYPE (fixed length), PEI (fixed length), PSPARE (fixed length), and GOB layer (variable length). Arrows indicate the flow and loops between these elements. Syntax diagram for the GOB layer. It shows a sequence of elements: GBSC (fixed length), GN (fixed length), GQUANT (fixed length), GEI (fixed length), GSPARE (fixed length), and MB layer (variable length). Arrows indicate the flow and loops between these elements. Syntax diagram for the MB layer. It shows a sequence of elements: MBA (variable length), MTYPE (variable length), MQUANT (fixed length), MVD (variable length), CBP (variable length), and Block layer (variable length). There are also MBA stuffing (fixed length) and additional MVD and CBP elements. Arrows indicate the flow and loops between these elements. Syntax diagram for the Block layer. It shows a sequence of elements: TCOEFF (variable length) and EOB (fixed length). Arrows indicate the flow and loops between these elements.](d4af765160d04ecef538e5066006dc77_img.jpg)
+
+Picture layer
+
+```
+
+graph LR
+    PSC[PSC] --> TR[TR]
+    TR --> PTYPE[PTYPE]
+    PTYPE --> PEI[PEI]
+    PEI --> PSPARE[PSPARE]
+    PSPARE --> GOB_layer([GOB layer])
+    GOB_layer --> PSC
+  
+```
+
+GOB layer
+
+```
+
+graph LR
+    GBSC[GBSC] --> GN[GN]
+    GN --> GQUANT[GQUANT]
+    GQUANT --> GEI[GEI]
+    GEI --> GSPARE[GSPARE]
+    GSPARE --> MB_layer([MB layer])
+    MB_layer --> GBSC
+  
+```
+
+MB layer
+
+```
+
+graph LR
+    MBA([MBA]) --> MTYPE([MTYPE])
+    MTYPE --> MQUANT[MQUANT]
+    MQUANT --> MVD1([MVD])
+    MVD1 --> CBP1([CBP])
+    CBP1 --> Block_layer([Block layer])
+    Block_layer --> MBA
+    MQUANT --> CBP2([CBP])
+    CBP2 --> Block_layer
+    MQUANT --> MBA_stuffing[MBA stuffing]
+    MBA_stuffing --> MBA
+  
+```
+
+Block layer
+
+```
+
+graph LR
+    TCOEFF([TCOEFF]) --> EOB[EOB]
+    EOB --> TCOEFF
+  
+```
+
+Fixed length
+   
+ Variable length
+
+Syntax diagram for the Picture layer. It shows a sequence of elements: PSC (fixed length), TR (fixed length), PTYPE (fixed length), PEI (fixed length), PSPARE (fixed length), and GOB layer (variable length). Arrows indicate the flow and loops between these elements. Syntax diagram for the GOB layer. It shows a sequence of elements: GBSC (fixed length), GN (fixed length), GQUANT (fixed length), GEI (fixed length), GSPARE (fixed length), and MB layer (variable length). Arrows indicate the flow and loops between these elements. Syntax diagram for the MB layer. It shows a sequence of elements: MBA (variable length), MTYPE (variable length), MQUANT (fixed length), MVD (variable length), CBP (variable length), and Block layer (variable length). There are also MBA stuffing (fixed length) and additional MVD and CBP elements. Arrows indicate the flow and loops between these elements. Syntax diagram for the Block layer. It shows a sequence of elements: TCOEFF (variable length) and EOB (fixed length). Arrows indicate the flow and loops between these elements.
+
+T1502451-90/d04
+
+FIGURE 4/H.261  
+Syntax diagram for the video multiplex coder
+
+![](af7916c89a458fdab6c3f443217388ae_img.jpg)
+
+|     |    |       |     |        |     |          |
+|-----|----|-------|-----|--------|-----|----------|
+| PSC | TR | PTYPE | PEI | PSPARE | PEI | GOB data |
+|-----|----|-------|-----|--------|-----|----------|
+
+T1514230-93/d05
+
+FIGURE 5/H.261  
+Structure of picture layer
+
+### 4.2.2 Group of blocks layer
+
+Each picture is divided into groups of blocks (GOBs). A group of blocks (GOB) comprises one twelfth of the CIF or one third of the QCIF picture areas (see Figure 6). A GOB relates to 176 pels by 48 lines of Y and the spatially corresponding 88 pels by 24 lines of each of C<sub>B</sub> and C<sub>R</sub>.
+
+Data for each group of blocks consists of a GOB header followed by data for macroblocks. The structure is shown in Figure 7. Each GOB header is transmitted once between picture start codes in the CIF or QCIF sequence numbered in Figure 6, even if no macroblock data is present in that GOB.
+
+![](ddc7460821484f1ae2835c67955c554c_img.jpg)
+
+|    |    |
+|----|----|
+| 1  | 2  |
+| 3  | 4  |
+| 5  | 6  |
+| 7  | 8  |
+| 9  | 10 |
+| 11 | 12 |
+
+CIF
+
+|   |
+|---|
+| 1 |
+| 3 |
+| 5 |
+
+QCIF
+
+FIGURE 6/H.261  
+Arrangement of GOBs in a picture
+
+![](4636adff5682a064f0ae5f13a1d464a6_img.jpg)
+
+|      |    |        |     |        |     |         |
+|------|----|--------|-----|--------|-----|---------|
+| GBSC | GN | GQUANT | GEI | GSPARE | GEI | MB data |
+|------|----|--------|-----|--------|-----|---------|
+
+T1514240-93/d06
+
+FIGURE 7/H.261  
+Structure of group of blocks layer
+
+#### 4.2.2.1 Group of blocks start code (GBSC) (16 bits)
+
+A word of 16 bits, 0000 0000 0000 0001.
+
+#### 4.2.2.2 Group number (GN) (4 bits)
+
+Four bits indicating the position of the group of blocks. The bits are the binary representation of the number in Figure 6. Group numbers 13, 14 and 15 are reserved for future use. Group number 0 is used in the PSC.
+
+#### 4.2.2.3 Quantizer information (GQUANT) (5 bits)
+
+A fixed length codeword of 5 bits which indicates the quantizer to be used in the group of blocks until overridden by any subsequent MQUANT. The codewords are the natural binary representations of the values of QUANT (see 4.2.4) which, being half the step sizes, range from 1 to 31.
+
+#### 4.2.2.4 Extra insertion information (GEI) (1 bit)
+
+A bit which when set to “1” signals the presence of the following optional data field.
+
+#### 4.2.2.5 Spare information (GSPARE) (0/8/16 . . . bits)
+
+If GEI is set to “1”, then 9 bits follow consisting of 8 bits of data (GSPARE) and then another GEI bit to indicate if a further 9 bits follow and so on. Encoders must not insert GSPARE until specified by the CCITT. Decoders must be designed to discard GSPARE if GEI is set to 1. This will allow the CCITT to specify future “backward” compatible additions in GSPARE.
+
+NOTE – Emulation of start codes may occur if the future specification of GSPARE has no restrictions on the final GSPARE data bits.
+
+### 4.2.3 Macroblock layer
+
+Each GOB is divided into 33 macroblocks as shown in Figure 8. A macroblock relates to 16 pels by 16 lines of Y and the spatially corresponding 8 pels by 8 lines of each of C<sub>B</sub> and C<sub>R</sub>.
+
+Data for a macroblock consists of an MB header followed by data for blocks (see Figure 9). MQUANT, MVD and CBP are present when indicated by MTYPE.
+
+|    |    |    |    |    |    |    |    |    |    |    |
+|----|----|----|----|----|----|----|----|----|----|----|
+| 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 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 |
+
+FIGURE 8/H.261  
+Arrangement of macroblocks in a GOB
+
+|     |       |        |     |     |            |
+|-----|-------|--------|-----|-----|------------|
+| MBA | MTYPE | MQUANT | MVD | CBP | Block data |
+|-----|-------|--------|-----|-----|------------|
+
+FIGURE 9/H.261  
+Structure of macroblock layer
+
+#### 4.2.3.1 Macroblock address (MBA) (Variable length)
+
+A variable length codeword indicating the position of a macroblock within a group of blocks. The transmission order is as shown in Figure 8. For the first transmitted macroblock in a GOB, MBA is the absolute address in Figure 8. For subsequent macroblocks, MBA is the difference between the absolute addresses of the macroblock and the last transmitted macroblock. The code table for MBA is given in Table 1.
+
+An extra codeword is available in the table for bit stuffing immediately after a GOB header or a coded macroblock (MBA stuffing). This codeword should be discarded by decoders.
+
+The VLC for start code is also shown in Table 1.
+
+MBA is always included in transmitted macroblocks.
+
+Macroblocks are not transmitted when they contain no information for that part of the picture.
+
+TABLE 1/H.261
+
+##### VLC table for macroblock addressing
+
+| MBA | Code         | MBA          | Code                |
+|-----|--------------|--------------|---------------------|
+| 1   | 1            | 17           | 0000 0101 10        |
+| 2   | 011          | 18           | 0000 0101 01        |
+| 3   | 010          | 19           | 0000 0101 00        |
+| 4   | 0011         | 20           | 0000 0100 11        |
+| 5   | 0010         | 21           | 0000 0100 10        |
+| 6   | 0001 1       | 22           | 0000 0100 011       |
+| 7   | 0001 0       | 23           | 0000 0100 010       |
+| 8   | 0000 111     | 24           | 0000 0100 001       |
+| 9   | 0000 110     | 25           | 0000 0100 000       |
+| 10  | 0000 1011    | 26           | 0000 0011 111       |
+| 11  | 0000 1010    | 27           | 0000 0011 110       |
+| 12  | 0000 1001    | 28           | 0000 0011 101       |
+| 13  | 0000 1000    | 29           | 0000 0011 100       |
+| 14  | 0000 0111    | 30           | 0000 0011 011       |
+| 15  | 0000 0110    | 31           | 0000 0011 010       |
+| 16  | 0000 0101 11 | 32           | 0000 0011 001       |
+|     |              | 33           | 0000 0011 000       |
+|     |              | MBA stuffing | 0000 0001 111       |
+|     |              | Start code   | 0000 0000 0000 0001 |
+
+#### 4.2.3.2 Type information (MTYPE) (Variable length)
+
+Variable length codewords giving information about the macroblock and which data elements are present. Macroblock types, included elements and VLC words are listed in Table 2.
+
+MTYPE is always included in transmitted macroblocks.
+
+#### 4.2.3.3 Quantizer (MQUANT) (5 bits)
+
+MQUANT is present only if so indicated by MTYPE.
+
+A codeword of 5 bits signifying the quantizer to be used for this and any following blocks in the group of blocks until overridden by any subsequent MQUANT.
+
+Codewords for MQUANT are the same as for GQUANT.
+
+TABLE 2/H.261
+
+##### **VLC table for MTTYPE**
+
+| Prediction                                                                                                                                                                                                         | MQUANT | MVD | CBP | TCOEFF | VLC          |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-----|-----|--------|--------------|
+| Intra                                                                                                                                                                                                              |        |     |     | x      | 0001         |
+| Intra                                                                                                                                                                                                              | x      |     |     | x      | 0000 001     |
+| Inter                                                                                                                                                                                                              |        |     | x   | x      | 1            |
+| Inter                                                                                                                                                                                                              | x      |     | x   | x      | 0000 1       |
+| Inter + MC                                                                                                                                                                                                         |        | x   |     |        | 0000 0000 1  |
+| Inter + MC                                                                                                                                                                                                         |        | x   | x   | x      | 0000 0001    |
+| Inter + MC                                                                                                                                                                                                         | x      | x   | x   | x      | 0000 0000 01 |
+| Inter + MC + FIL                                                                                                                                                                                                   |        | x   |     |        | 001          |
+| Inter + MC + FIL                                                                                                                                                                                                   |        | x   | x   | x      | 01           |
+| Inter + MC + FIL                                                                                                                                                                                                   | x      | x   | x   | x      | 0000 01      |
+| <b>NOTES</b><br>1     "x" means that the item is present in the macroblock.<br>2     It is possible to apply the filter in a non-motion compensated macroblock by declaring it as MC + FIL but with a zero vector. |        |     |     |        |              |
+
+#### **4.2.3.4 Motion vector data (MVD) (Variable length)**
+
+Motion vector data is included for all MC macroblocks. MVD is obtained from the macroblock vector by subtracting the vector of the preceding macroblock. For this calculation the vector of the preceding macroblock is regarded as zero in the following three situations:
+
+- 1) evaluating MVD for macroblocks 1, 12 and 23;
+- 2) evaluating MVD for macroblocks in which MBA does not represent a difference of 1;
+- 3) MTTYPE of the previous macroblock was not MC.
+
+MVD 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 3.
+
+Advantage is taken of the fact that the range of motion vector values is constrained. Each VLC word represents a pair of difference values. Only one of the pair will yield a macroblock vector falling within the permitted range.
+
+#### **4.2.3.5 Coded block pattern (CBP) (Variable length)**
+
+CBP is present if indicated by MTTYPE. The codeword gives a pattern number signifying those blocks in the macroblock for which at least one transform coefficient is transmitted. The pattern number is given by:
+
+$$32 \cdot P_1 + 16 \cdot P_2 + 8 \cdot P_3 + 4 \cdot P_4 + 2 \cdot P_5 + P_6$$
+
+where  $P_n = 1$  if any coefficient is present for block  $n$ , else 0. Block numbering is given in Figure 10.
+
+The codewords for CBP are given in Table 4.
+
+TABLE 3/H.261
+
+##### **VLC table for MVD**
+
+| MVD      | Code          |
+|----------|---------------|
+| -16 & 16 | 0000 0011 001 |
+| -15 & 17 | 0000 0011 011 |
+| -14 & 18 | 0000 0011 101 |
+| -13 & 19 | 0000 0011 111 |
+| -12 & 20 | 0000 0100 001 |
+| -11 & 21 | 0000 0100 011 |
+| -10 & 22 | 0000 0100 11  |
+| -9 & 23  | 0000 0101 01  |
+| -8 & 24  | 0000 0101 11  |
+| -7 & 25  | 0000 0111     |
+| -6 & 26  | 0000 1001     |
+| -5 & 27  | 0000 1011     |
+| -4 & 28  | 0000 111      |
+| -3 & 29  | 0001 1        |
+| -2 & 30  | 0011          |
+| -1       | 011           |
+| 0        | 1             |
+| 1        | 010           |
+| 2 & -30  | 0010          |
+| 3 & -29  | 0001 0        |
+| 4 & -28  | 0000 110      |
+| 5 & -27  | 0000 1010     |
+| 6 & -26  | 0000 1000     |
+| 7 & -25  | 0000 0110     |
+| 8 & -24  | 0000 0101 10  |
+| 9 & -23  | 0000 0101 00  |
+| 10 & -22 | 0000 0100 10  |
+| 11 & -21 | 0000 0100 010 |
+| 12 & -20 | 0000 0100 000 |
+| 13 & -19 | 0000 0011 110 |
+| 14 & -18 | 0000 0011 100 |
+| 15 & -17 | 0000 0011 010 |
+
+### **4.2.4 Block layer**
+
+A macroblock comprises four luminance blocks and one of each of the two colour difference blocks (see Figure 10).
+
+Data for a block consists of codewords for transform coefficients followed by an end of block marker (see Figure 11). The order of block transmission is as in Figure 10.
+
+#### **4.2.4.1 Transform coefficients (TCOEFF)**
+
+Transform coefficient data is always present for all six blocks in a macroblock when MTYPE indicates INTRA. In other cases MTYPE and CBP signal which blocks have coefficient data transmitted for them. The quantized transform coefficients are sequentially transmitted according to the sequence given in Figure 12.
+
+The most commonly occurring combinations of successive zeros (RUN) and the following value (LEVEL) are encoded with variable length codes. Other combinations of (RUN, LEVEL) are encoded with a 20-bit word consisting of 6 bits ESCAPE, 6 bits RUN and 8 bits LEVEL. For the variable length encoding there are two code tables, one being used for the first transmitted LEVEL in INTER, INTER+MC and INTER+MC+FIL blocks, the second for all other LEVELs except the first one in INTRA blocks which is fixed length coded with 8 bits.
+
+TABLE 4/H.261
+
+##### VLC table for CBP
+
+| CBP | Code      | CBP | Code        |
+|-----|-----------|-----|-------------|
+| 60  | 111       | 35  | 0001 1100   |
+| 4   | 1101      | 13  | 0001 1011   |
+| 8   | 1100      | 49  | 0001 1010   |
+| 16  | 1011      | 21  | 0001 1001   |
+| 32  | 1010      | 41  | 0001 1000   |
+| 12  | 1001 1    | 14  | 0001 0111   |
+| 48  | 1001 0    | 50  | 0001 0110   |
+| 20  | 1000 1    | 22  | 0001 0101   |
+| 40  | 1000 0    | 42  | 0001 0100   |
+| 28  | 0111 1    | 15  | 0001 0011   |
+| 44  | 0111 0    | 51  | 0001 0010   |
+| 52  | 0110 1    | 23  | 0001 0001   |
+| 56  | 0110 0    | 43  | 0001 0000   |
+| 1   | 0101 1    | 25  | 0000 1111   |
+| 61  | 0101 0    | 37  | 0000 1110   |
+| 2   | 0100 1    | 26  | 0000 1101   |
+| 62  | 0100 0    | 38  | 0000 1100   |
+| 24  | 0011 11   | 29  | 0000 1011   |
+| 36  | 0011 10   | 45  | 0000 1010   |
+| 3   | 0011 01   | 53  | 0000 1001   |
+| 63  | 0011 00   | 57  | 0000 1000   |
+| 5   | 0010 111  | 30  | 0000 0111   |
+| 9   | 0010 110  | 46  | 0000 0110   |
+| 17  | 0010 101  | 54  | 0000 0101   |
+| 33  | 0010 100  | 58  | 0000 0100   |
+| 6   | 0010 011  | 31  | 0000 0011 1 |
+| 10  | 0010 010  | 47  | 0000 0011 0 |
+| 18  | 0010 001  | 55  | 0000 0010 1 |
+| 34  | 0010 000  | 59  | 0000 0010 0 |
+| 7   | 0001 1111 | 27  | 0000 0001 1 |
+| 11  | 0001 1110 | 39  | 0000 0001 0 |
+| 19  | 0001 1101 |     |             |
+
+![Diagram showing the arrangement of blocks in a macroblock. It consists of three separate boxes. The first box is a 2x2 grid labeled 'Y' containing blocks 1, 2, 3, and 4. The second box is a single rectangle labeled '5' and 'C_B' below it. The third box is a single rectangle labeled '6' and 'C_R' below it.](4356776ca004ecba5d599667a155d7d4_img.jpg)
+
+Diagram showing the arrangement of blocks in a macroblock. It consists of three separate boxes. The first box is a 2x2 grid labeled 'Y' containing blocks 1, 2, 3, and 4. The second box is a single rectangle labeled '5' and 'C\_B' below it. The third box is a single rectangle labeled '6' and 'C\_R' below it.
+
+FIGURE 10/H.261
+
+#### Arrangement of blocks in a macroblock
+
+|        |     |
+|--------|-----|
+| TCOEFF | EOB |
+|--------|-----|
+
+FIGURE 11/H.261  
+**Structure of block layer**
+
+|    |    |    |    |    |    |    |    |
+|----|----|----|----|----|----|----|----|
+| 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 |
+
+→ Increasing cycles per picture width  
+↓ Increasing cycles per picture height  
+T1514100-93/d07
+
+FIGURE 12/H.261  
+**Transmission order for transform coefficients**
+
+Codes are given in Table 5.
+
+The most commonly occurring combinations of zero-run and the following value are encoded with variable length codes as listed in the table 5. End of block (EOB) is in this set. Because CBP indicates those blocks with no coefficient data, EOB cannot occur as the first coefficient. Hence EOB can be removed from the VLC table for the first coefficient.
+
+The last bit “s” denotes the sign of the level, “0” for positive and “1” for negative.
+
+The remaining combinations of (run, level) are encoded with a 20-bit word consisting of 6 bits escape, 6 bits run and 8 bits level. Use of this 20-bit word form encoding the combinations listed in the VLC table is not prohibited.
+
+TABLE 5/H.261  
+VLC table for TCOEFF
+
+| Run    | Level | Code                                            |
+|--------|-------|-------------------------------------------------|
+| EOB    |       | 10                                              |
+| 0      | 1     | 1s <sup>a</sup> ) If first coefficient in block |
+| 0      | 1     | 11s Not first coefficient in block              |
+| 0      | 2     | 0100 s                                          |
+| 0      | 3     | 0010 1s                                         |
+| 0      | 4     | 0000 110s                                       |
+| 0      | 5     | 0010 0110 s                                     |
+| 0      | 6     | 0010 0001 s                                     |
+| 0      | 7     | 0000 0010 10s                                   |
+| 0      | 8     | 0000 0001 1101 s                                |
+| 0      | 9     | 0000 0001 1000 s                                |
+| 0      | 10    | 0000 0001 0011 s                                |
+| 0      | 11    | 0000 0001 0000 s                                |
+| 0      | 12    | 0000 0000 1101 0s                               |
+| 0      | 13    | 0000 0000 1100 1s                               |
+| 0      | 14    | 0000 0000 1100 0s                               |
+| 0      | 15    | 0000 0000 1011 1s                               |
+| 1      | 1     | 011s                                            |
+| 1      | 2     | 0001 10s                                        |
+| 1      | 3     | 0010 0101 s                                     |
+| 1      | 4     | 0000 0011 00s                                   |
+| 1      | 5     | 0000 0001 1011 s                                |
+| 1      | 6     | 0000 0000 1011 0s                               |
+| 1      | 7     | 0000 0000 1010 1s                               |
+| 2      | 1     | 0101 s                                          |
+| 2      | 2     | 0000 100s                                       |
+| 2      | 3     | 0000 0010 11s                                   |
+| 2      | 4     | 0000 0001 0100 s                                |
+| 2      | 5     | 0000 0000 1010 0s                               |
+| 3      | 1     | 0011 1s                                         |
+| 3      | 2     | 0010 0100 s                                     |
+| 3      | 3     | 0000 0001 1100 s                                |
+| 3      | 4     | 0000 0000 1001 1s                               |
+| 4      | 1     | 0011 0s                                         |
+| 4      | 2     | 0000 0011 11s                                   |
+| 4      | 3     | 0000 0001 0010 s                                |
+| 5      | 1     | 0001 11s                                        |
+| 5      | 2     | 0000 0010 01s                                   |
+| 5      | 3     | 0000 0000 1001 0s                               |
+| 6      | 1     | 0001 01s                                        |
+| 6      | 2     | 0000 0001 1110 s                                |
+| 7      | 1     | 0001 00s                                        |
+| 7      | 2     | 0000 0001 0101 s                                |
+| 8      | 1     | 0000 111s                                       |
+| 8      | 2     | 0000 0001 0001 s                                |
+| 9      | 1     | 0000 101s                                       |
+| 9      | 2     | 0000 0000 1000 1s                               |
+| 10     | 1     | 0010 0111 s                                     |
+| 10     | 2     | 0000 0000 1000 0s                               |
+| 11     | 1     | 0010 0011 s                                     |
+| 12     | 1     | 0010 0010 s                                     |
+| 13     | 1     | 0010 0000 s                                     |
+| 14     | 1     | 0000 0011 10s                                   |
+| 15     | 1     | 0000 0011 01s                                   |
+| 16     | 1     | 0000 0010 00s                                   |
+| 17     | 1     | 0000 0001 1111 s                                |
+| 18     | 1     | 0000 0001 1010 s                                |
+| 19     | 1     | 0000 0001 1001 s                                |
+| 20     | 1     | 0000 0001 0111 s                                |
+| 21     | 1     | 0000 0001 0110 s                                |
+| 22     | 1     | 0000 0000 1111 1s                               |
+| 23     | 1     | 0000 0000 1111 0s                               |
+| 24     | 1     | 0000 0000 1110 1s                               |
+| 25     | 1     | 0000 0000 1110 0s                               |
+| 26     | 1     | 0000 0000 1101 1s                               |
+| Escape |       | 0000 01                                         |
+
+<sup>a</sup>) Never used in INTRA macroblocks.
+
+Run is a 6 bit fixed length code
+
+| Run | Code    |
+|-----|---------|
+| 0   | 0000 00 |
+| 1   | 0000 01 |
+| 2   | 0000 10 |
+| .   | .       |
+| .   | .       |
+| 63  | 1111 11 |
+
+Level is an 8 bit fixed length code
+
+| Level | Code      |
+|-------|-----------|
+| -128  | FORBIDDEN |
+| -127  | 1000 0001 |
+| .     | .         |
+| -2    | 1111 1110 |
+| -1    | 1111 1111 |
+| 0     | FORBIDDEN |
+| 1     | 0000 0001 |
+| 2     | 0000 0010 |
+| .     | .         |
+| 127   | 0111 1111 |
+
+For all coefficients other than the INTRA dc one, the reconstruction levels (REC) are in the range -2048 to 2047 and are given by clipping the results of the following formulas:
+
+$$\left. \begin{aligned} \text{REC} &= \text{QUANT} \cdot (2 \cdot \text{level} + 1); \text{ level} > 0 \\ \text{REC} &= \text{QUANT} \cdot (2 \cdot \text{level} - 1); \text{ level} < 0 \end{aligned} \right\} \text{QUANT} = \text{"odd"}$$
+
+$$\left. \begin{aligned} \text{REC} &= \text{QUANT} \cdot (2 \cdot \text{level} + 1) - 1; \text{ level} > 0 \\ \text{REC} &= \text{QUANT} \cdot (2 \cdot \text{level} - 1) + 1; \text{ level} < 0 \end{aligned} \right\} \text{QUANT} = \text{"even"}$$
+
+$$\text{REC} = 0; \text{ level} = 0$$
+
+NOTE – QUANT ranges from 1 to 31 and is transmitted by either GQUANT or MQUANT.
+
+Reconstruction levels (REC)
+
+| Level | QUANT |      |      |       |   |       |       |   |       |       |   |       |       |
+|-------|-------|------|------|-------|---|-------|-------|---|-------|-------|---|-------|-------|
+|       | 1     | 2    | 3    | 4     | . | 8     | 9     | . | 17    | 18    | . | 30    | 31    |
+| -127  | -255  | -509 | -765 | -1019 | . | -2039 | -2048 | . | -2048 | -2048 | . | -2048 | -2048 |
+| -126  | -253  | -505 | -759 | -1011 | . | -2023 | -2048 | . | -2048 | -2048 | . | -2048 | -2048 |
+| .     | .     | .    | .    | .     | . | .     | .     | . | .     | .     | . | .     | .     |
+| -2    | -5    | -9   | -15  | -19   | . | -39   | -45   | . | -85   | -89   | . | -149  | -155  |
+| -1    | -3    | -5   | -9   | -11   | . | -23   | -27   | . | -51   | -53   | . | -89   | -93   |
+| 0     | 0     | 0    | 0    | 0     | . | 0     | 0     | . | 0     | 0     | . | 0     | 0     |
+| 1     | 3     | 5    | 9    | 11    | . | 23    | 27    | . | 51    | 53    | . | 89    | 93    |
+| 2     | 5     | 9    | 15   | 19    | . | 39    | 45    | . | 85    | 89    | . | 149   | 155   |
+| 3     | 7     | 13   | 21   | 27    | . | 55    | 63    | . | 119   | 125   | . | 209   | 217   |
+| 4     | 9     | 17   | 27   | 35    | . | 71    | 81    | . | 153   | 161   | . | 269   | 279   |
+| 5     | 11    | 21   | 33   | 43    | . | 87    | 99    | . | 187   | 197   | . | 329   | 341   |
+| .     | .     | .    | .    | .     | . | .     | .     | . | .     | .     | . | .     | .     |
+| 56    | 113   | 225  | 339  | 451   | . | 903   | 1017  | . | 1921  | 2033  | . | 2047  | 2047  |
+| 57    | 115   | 229  | 345  | 459   | . | 919   | 1035  | . | 1955  | 2047  | . | 2047  | 2047  |
+| 58    | 117   | 233  | 351  | 467   | . | 935   | 1053  | . | 1989  | 2047  | . | 2047  | 2047  |
+| 59    | 119   | 237  | 357  | 475   | . | 951   | 1071  | . | 2023  | 2047  | . | 2047  | 2047  |
+| 60    | 121   | 241  | 363  | 483   | . | 967   | 1089  | . | 2047  | 2047  | . | 2047  | 2047  |
+| .     | .     | .    | .    | .     | . | .     | .     | . | .     | .     | . | .     | .     |
+| 125   | 251   | 501  | 753  | 1003  | . | 2007  | 2047  | . | 2047  | 2047  | . | 2047  | 2047  |
+| 126   | 253   | 505  | 759  | 1011  | . | 2023  | 2047  | . | 2047  | 2047  | . | 2047  | 2047  |
+| 127   | 255   | 509  | 765  | 1019  | . | 2039  | 2047  | . | 2047  | 2047  | . | 2047  | 2047  |
+
+NOTE – Reconstruction levels are symmetrical with respect to the sign of level except for 2047/-2048.
+
+For INTRA blocks the first coefficient is nominally the transform dc value linearly quantized with a step size of 8 and no dead-zone. The resulting values are represented with 8 bits. A nominally black block will give 0001 0000 and a nominally white one 1110 1011. 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 6).
+
+Coefficients after the last non-zero one are not transmitted. EOB (end of block code) is always the last item in blocks for which coefficients are transmitted.
+
+## 4.3 Multipoint considerations
+
+The following facilities are provided to support switched multipoint operation.
+
+### 4.3.1 Freeze picture request
+
+Causes the decoder to freeze its displayed picture until a freeze picture release signal is received or a timeout period of at least six seconds has expired. The transmission of this signal is via external means (for example by Recommendation H.221).
+
+### 4.3.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 via external means (for example by Recommendation H.221).
+
+TABLE 6/H.261
+
+#### Reconstruction levels for INTRA-mode dc coefficient
+
+| FLC             | Reconstruction level into inverse transform |
+|-----------------|---------------------------------------------|
+| 0000 0001 (1)   | 8                                           |
+| 0000 0010 (2)   | 16                                          |
+| 0000 0011 (3)   | 24                                          |
+| .               | .                                           |
+| .               | .                                           |
+| 0111 1111 (127) | 1016                                        |
+| 1111 1111 (255) | 1024                                        |
+| 1000 0001 (129) | 1032                                        |
+| .               | .                                           |
+| .               | .                                           |
+| 1111 1101 (253) | 2024                                        |
+| 1111 1110 (254) | 2032                                        |
+
+NOTE – The decoded value corresponding to FLC “*n*” is  $8n$  except FLC 255 gives 1024.
+
+### 4.3.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 bit 3 of PTYPE (see 4.2.1) in the picture header of the first picture coded in response to the fast update request.
+
+# 5 Transmission coder
+
+## 5.1 Bit rate
+
+The transmission clock is provided externally (for example from an I.420 interface).
+
+## 5.2 Video data buffering
+
+The encoder must control its output bitstream to comply with the requirements of the hypothetical reference decoder defined in Annex B.
+
+When operating with CIF the number of bits created by coding any single picture must not exceed 256 kbits.
+
+When operating with QCIF the number of bits created by coding any single picture must not exceed 64 kbits.
+
+In both the above cases the bit count includes the picture start code and all other data related to that picture including PSPARE, GSPARE and MBA stuffing. The bit count does not include error correction framing bits, fill indicator (Fi), fill bits or error correction parity information described in 5.4.
+
+Video data must be provided on every valid clock cycle. This can be ensured by the use of either the fill bit indicator (Fi) and subsequent fill all 1's bits in the error corrector block framing (see Figure 13) or MBA stuffing (see 4.2.3) or both.
+
+![Diagram of Figure 13 showing the error correcting frame structure. It illustrates a sequence of frames S1 through S8. A single frame is expanded to show it consists of a 1-bit S1 field, a 493-bit Data field, and an 18-bit Parity field. The Data field starts with a 1-bit Fill indicator (Fi). If Fi=1, the remaining bits are Coded data. If Fi=0, the remaining 492 bits are Fill (all '1').](86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg)
+
+Transmission order →       $(S_1 S_2 S_3 S_4 S_5 S_6 S_7 S_8) = (00011011)$
+
+|                |      |                |        |
+|----------------|------|----------------|--------|
+| S <sub>1</sub> | Data |                | Parity |
+| 1              | 493  |                | 18     |
+|                | Fi   |                |        |
+|                | 1    | Coded data     |        |
+|                | 0    | Fill (all "1") |        |
+|                | 1    | 492            |        |
+
+T1502460-90/d08
+
+Diagram of Figure 13 showing the error correcting frame structure. It illustrates a sequence of frames S1 through S8. A single frame is expanded to show it consists of a 1-bit S1 field, a 493-bit Data field, and an 18-bit Parity field. The Data field starts with a 1-bit Fill indicator (Fi). If Fi=1, the remaining bits are Coded data. If Fi=0, the remaining 492 bits are Fill (all '1').
+
+FIGURE 13/H.261  
+**Error correcting frame**
+
+## 5.3 Video coding delay
+
+This item is included in this Recommendation because the video encoder and video decoder delays need to be known to allow audio compensation delays to be fixed when H.261 is used to form part of a conversational service. This will allow lip synchronization to be maintained. Annex C recommends a method by which the delay figures are established. Other delay measurement methods may be used but they must be designed in a way to produce similar results to the method given in Annex C.
+
+## 5.4 Forward error correction for coded video signal
+
+### 5.4.1 Error correcting code
+
+The transmitted bitstream contains a BCH (511,493) forward error correction code. Use of this by the decoder is optional.
+
+### 5.4.2 Generator polynomial
+
+$$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).
+
+### 5.4.3 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 consists of a multiframe 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. The frame alignment pattern is:
+
+$$(S_1S_2S_3S_4S_5S_6S_7S_8) = (00011011).$$
+
+See Figure 13 for the frame arrangement. The parity is calculated against the 493-bits including fill indicator (Fi).
+
+The fill indicator (Fi) can be set to zero by an encoder. In this case only 492 consecutive fill bits (fill all 1s) plus parity are sent and no coded data is transmitted. This may be used to meet the requirement in 5.2 to provide video data on every valid clock cycle.
+
+### 5.4.4 Relock time for error corrector framing
+
+Three consecutive error correction framing sequences (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.
+
+# Annex AInverse transform accuracy specification
+
+(This annex forms an integral part of this Recommendation)
+
+**A.1** Generate random integer pel 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[\pi(2x + 1)u/16] \cos[\pi(2y + 1)v/16]$$
+
+with  $u, v, x, y = 0, 1, 2, \dots, 7$
+
+where  $x, y =$  spatial coordinates in the pel 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 transform (IDCT) using at least 64-bit floating point accuracy. Round the resulting pels to the nearest integer and clip to the range  $-256$  to  $+255$ . These blocks of  $8 \times 8$  pels are the reference IDCT input 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$  pels are the test IDCT output data.
+
+**A.6** For each of the 64 IDCT output pels, 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 pel, the peak error should not exceed 1 in magnitude.
+
+For any pel, the mean square error should not exceed 0.06.
+
+Overall, the mean square error should not exceed 0.02.
+
+For any pel, 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 must 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 pel.
+
+“C” program for random number generation
+
+```
+
+/* L and H must 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 & 0x7fffffff;        /* 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
+
+(This annex forms an integral part of this Recommendation)
+
+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 CIF rate, and are operated synchronously.
+
+**B.2** The HRD receiving buffer size is ( $B + 256$  kbits). The value of  $B$  is defined as follows:
+
+$B = 4R_{max}/29.97$  where  $R_{max}$  is the maximum video bit rate to be used in the connection.
+
+**B.3** The HRD buffer is initially empty.
+
+**B.4** The HRD buffer is examined at CIF intervals ( $\approx 33$  ms). If at least one complete coded picture is in the buffer then all the data for the earliest picture 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 MBA stuffing but not error correction framing bits, fill indicator (Fi), fill bits or error correction parity information described in 5.4.
+
+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 buffer occupancy just after the 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 the time  $t$ .
+
+![Figure B.1/H.261: HRD buffer occupancy graph. The y-axis is 'HRD buffer occupancy (bit)' and the x-axis is 'Time (CIF interval)'. The graph shows a sawtooth-like pattern. At time $t_n$, the buffer level is $b_n$. It increases linearly to a peak at time $t_{n+1}$, with the area under the curve between $t_n$ and $t_{n+1}$ labeled as $\int_{t_n}^{t_{n+1}} R(t)dt$. At $t_{n+1}$, there is a vertical drop to $b_{n+1}$. The peak level is labeled $d_{n+1}$. A horizontal dashed line at level $B$ represents the buffer capacity. There are break symbols (double squiggly lines) on the rising slopes. A small label 'T1502470-90/d09' is at the bottom right.](bfb6d182d624680db577069bbc0b2a93_img.jpg)
+
+Figure B.1/H.261: HRD buffer occupancy graph. The y-axis is 'HRD buffer occupancy (bit)' and the x-axis is 'Time (CIF interval)'. The graph shows a sawtooth-like pattern. At time \$t\_n\$, the buffer level is \$b\_n\$. It increases linearly to a peak at time \$t\_{n+1}\$, with the area under the curve between \$t\_n\$ and \$t\_{n+1}\$ labeled as \$\int\_{t\_n}^{t\_{n+1}} R(t)dt\$. At \$t\_{n+1}\$, there is a vertical drop to \$b\_{n+1}\$. The peak level is labeled \$d\_{n+1}\$. A horizontal dashed line at level \$B\$ represents the buffer capacity. There are break symbols (double squiggly lines) on the rising slopes. A small label 'T1502470-90/d09' 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, \dots)$ .
+
+FIGURE B.1/H.261  
+**HRD buffer occupancy**
+
+# Annex C
+
+## Codec delay measurement method
+
+(This annex forms an integral part of this Recommendation)
+
+The video encoder and video decoder delays will vary depending on implementation. The delay will also depend on the picture format (QCIF, CIF) and data rate in use. This annex specifies the method by which the delay figures are established for a particular design. To allow correct audio delay compensation the overall video delay needs to be established from a user perception point of view under typical viewing conditions.
+
+Point A is the video input to the video coder. Point B is the channel output from the video terminal (i.e. including any FEC, channel framing, etc.). Point C is the video output from the decoder.
+
+A video sequence lasting more than 100 seconds is connected to the video coder input (point A) in Figure C.1 above. The video sequence should have the following characteristics:
+
+- it should contain a typical moving scene consistent with the intended purpose of the video codec;
+- it should produce a minimum coded picture rate of 7.5 Hz at the bit rate in use;
+- it should contain a visible identification mark at intervals throughout the length of the sequence. The visible identification should change every 97 video input frames and be located within the picture area represented by the first GOB in the picture. For example, the first block in the picture could change from black to white at intervals of 97 video frame periods. The identification mark should be chosen so that it can be detected at point B and does not significantly contribute to the overall coding performance.
+
+The codec and video sequence should be arranged so that the bitstream contains less than 10% stuffing (MBA stuffing + error correction fill bits).
+
+The encoder delay is obtained by measuring the time from when the visible identification changes at point A to the time that the change is detected at point B. Similarly, the decoder delay is obtained by taking measurements at points B and C.
+
+Several measurements should be made during the sequence length and the average period obtained. Several tests should be made to ensure that a consistent average figure can be obtained for both encoder and decoder delay times.
+
+Average results should be obtained for each combination of picture format and bit rate within the capability of the particular codec design.
+
+NOTE – Due to pre- and post-temporal processing it may be necessary to take a mid-level for establishing the transition of the identification mark at points B and C.
+
+![Diagram showing measuring points A, B, and C in a video coding system.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg)
+
+The diagram illustrates a video processing pipeline. It consists of two main blocks: a 'Video coder' on the left and a 'Video decoder' on the right. An input arrow points from point 'A' into the 'Video coder'. An output arrow from the 'Video coder' points to point 'B', which is a vertical line extending upwards from the main horizontal path. From point 'B', the path continues to the 'Video decoder'. An output arrow from the 'Video decoder' points to point 'C'. Below the 'Video decoder' block, the text 'T1502480-90/d10' is present.
+
+Diagram showing measuring points A, B, and C in a video coding system.
+
+FIGURE C.1/H.261  
+**Measuring points**
+
+# Annex DStill image transmission
+
+(This annex forms an integral part of this Recommendation)
+
+## D.1 Introduction
+
+This annex describes the procedure for transmitting still images within the framework of this Recommendation. This procedure enables an H.261 video coder to transmit still images at four times the normal video resolution by temporarily stopping the motion video. Administrations may use this optional procedure as a simple and inexpensive method to transmit still images. However, Recommendation T.81 (JPEG) is preferred when the procedures for using T.81 within audiovisual systems are standardized.
+
+This procedure can provide high quality image transmission with effects similar to those of progressive and hierarchical schemes. Minimal changes to H.261 (low cost), backward compatibility with existing terminals, and flexibility in image quality versus transmission speed were the key considerations in its development.
+
+NOTE – The encoder would set a previously unused bit in PTYPE to “0” when it transmits a still image (unused bits should be set to “1”). A decoder that ignores this bit would receive the image as normal video. A decoder that goes into an error condition when this bit is “0” would most likely freeze the previous video frame, and resume when this bit is reset to “1”. A decoder having this new capability could display the image in a higher resolution, transfer the image to a separate graphics display and hold the image when video resumes, print and/or save the image, etc.
+
+## D.2 Still image format
+
+The still image format is four times the currently transmitted video format. If the video format is QCIF, then the still image is a CIF frame. If the video format is CIF, which contains  $352 \times 288$  luminance samples, then the still image contains  $704 \times 576$  luminance samples, and a corresponding increase in the number of chrominance samples (a CCIR-601 frame).
+
+For transmission using H.261, the still image is sub-sampled 2:1 horizontally and vertically into four sub-images in the currently transmitted video format. Figure D.1 shows the sub-sampling pattern on the still image. The samples labelled 0, 1, 2 and 3 form the four sub-images 0, 1, 2 and 3, respectively.
+
+|   |   |   |   |   |   |   |   |
+|---|---|---|---|---|---|---|---|
+| 0 | 3 | 0 | 3 | 0 | 3 | 0 | 3 |
+| 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 |
+| 0 | 3 | 0 | 3 | 0 | 3 | 0 | 3 |
+| 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 |
+| 0 | 3 | 0 | 3 | 0 | 3 | 0 | 3 |
+| 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 |
+
+FIGURE D.1/H.261
+
+### Sub-sampling pattern
+
+## D.3 Picture layer multiplex
+
+When HI\_RES is “0”, the two lower bits of the temporal reference (TR) identify one of the four sub-images 0, 1, 2 or 3. The three higher bits of the TR shall be set to “0”.
+
+The encoder transmits a still image by setting HI\_RES to “0” and transmitting the four sub-images 0, 1, 2 and 3 in sequential order. It is allowed to transmit more than one frame for each sub-image, but should not go back once it starts transmitting the next sub-image. The encoder is allowed to resume motion video at any time by setting HI\_RES back to “1”.
+
+NOTE – The reference memory for the current frame is always the previous frame, regardless of whether a frame is motion video or still image.
+
+## D.4 Multipoint considerations
+
+A still image transmitted within the video bit-stream can be broadcast on a multipoint connection by broadcasting the video. The MCV (multipoint command visualization-forcing) and Cancel-MCV commands defined in Recommendation H.230 provide for this capability. A terminal could force an MCU to broadcast its video by sending MCV, and then return to the previous mode of operation by sending Cancel-MCV. MCUs are required to implement these commands, but they are optional for terminals.
+
+## D.5 Other considerations
+
+- All the video coding modes are allowed (intra-frame, inter-frame, motion compensation, etc.);
+- the multiplex arrangement below the picture layer remains the same (group of blocks, macroblocks, etc.);
+- the maximum number of bits allowed per frame (sub-image) should not be exceeded (256 kbit/s for CIF and 64 kbit/s for QCIF);
+- forward error correction is not affected.
\ No newline at end of file
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/011605f44dd7f77a182efb20ed953a2e_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/011605f44dd7f77a182efb20ed953a2e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1d0d4a89bfbf44763161a8064fb10e4ede2c7c8c
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/011605f44dd7f77a182efb20ed953a2e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b16d70a2d0aa026df1efa239ebb3666f4d42823f7218982205de6b90995fdda8
+size 113703
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a2c6742f54e414b8ab2b2a227daca7140bee9304
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2294c52170e8f625eb8586a3b9d221805493d29eee5da24a1a8245f65f34271a
+size 22777
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a890093a7381c1c61be7f6db97b26b3c7d3bd1a4
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:79b9590624b4796c24a077a3a334dc84067b5dbdcde9b574f2d26cf98e847127
+size 49791
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/07e69273eef4109e165ab7129bf9f350_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/07e69273eef4109e165ab7129bf9f350_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9b05555b507e3990e24f4a66fa27b31ecfb973ea
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/07e69273eef4109e165ab7129bf9f350_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a19bda960b57d9c57c3c14405b8c2ccf752dbb3b6986fd48113e5ce600af99c3
+size 21893
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/0b2ee589f5c7802f3d332f421340cae1_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/0b2ee589f5c7802f3d332f421340cae1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5e46e43c31c1ea26e5fbb5572b6b1fae29a0ad2e
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/0b2ee589f5c7802f3d332f421340cae1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d6d4ceb3c76ef79a743ec21f961275c7ab1b5cc1d9f9428e533b5a7ee1f44821
+size 42616
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/0ea4dd371cc3e49d6c56433444d4ccc3_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/0ea4dd371cc3e49d6c56433444d4ccc3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f4100e20619c839fb0205dec414fd97d2a87b1ae
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/0ea4dd371cc3e49d6c56433444d4ccc3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5742e1908d5b5a59f7573e14934288fcf7cb7fb99249a4032c9dac3ec1a80676
+size 62865
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8b53228de45ae7ac8d7ea8beb3fb2cc76f689610
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6229efa70b6c19eeead03bbfa8b2017981075810be86271c0c4e71d8c2edfdab
+size 37442
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bece65d3e351fd0911d17d5909ea86d7e261b637
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:063e0124358016a50638ec07e4f1f87bf9c40271ce9e919a3a1a7b8b041abdae
+size 63064
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/143c8ee1010bf7669caabfbed815df1b_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/143c8ee1010bf7669caabfbed815df1b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..93a2ecb32f50e8cd23b1c7c3ffc42a3423ee99e0
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/143c8ee1010bf7669caabfbed815df1b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2169251677ca509c90fc70c8e3400d65786ac0f6e48979c82abf8b693fe6c9cb
+size 62129
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/18003425d0e8638dde4acc9c5c468c5c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f47ff7f6afbb3c13d1bd3201c0d9607dcc9b580f
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/18003425d0e8638dde4acc9c5c468c5c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a21760862caf4eb8832edae008c9d0a4eccd07920172f43d1c45a43c49271059
+size 17440
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/18bb06865e2dada3656ea3d57f290f7f_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/18bb06865e2dada3656ea3d57f290f7f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..539cf2bc630a59eeb955478d73968812ac2d63ad
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/18bb06865e2dada3656ea3d57f290f7f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e360bd3b0db7b78954b7aef31b7c74ef453395a2acbf8ae3426db983ffc048a
+size 36865
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/18e519d1f91133e080347562f681dfb5_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/18e519d1f91133e080347562f681dfb5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ff9c62b8a14d6445cd0c89aec4f4cbc641aab83f
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/18e519d1f91133e080347562f681dfb5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:22296bbb6efe5c05447cdbb93cc75234f17ddcad3954a5aa2aa459f868e546e3
+size 38599
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/1c3caf3c28fe1461a879e214f5df25ae_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/1c3caf3c28fe1461a879e214f5df25ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d872a29664363d892ae4a9a0565019c7c0e08177
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/1c3caf3c28fe1461a879e214f5df25ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:72c54b5a554fa01e9875773cd46fee62d91b41450220b74c6dbfd1cb57d56785
+size 47057
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..35d080739dd40d3a774e0eb22c42d16e417ea49a
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_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.263-200501-I_PDF-E/1daee79ab1ab652586116f083d50ed9d_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/1daee79ab1ab652586116f083d50ed9d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..088495fcd90654afcb998219904757d308d0c1c3
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/1daee79ab1ab652586116f083d50ed9d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d1b1e99886ae41b9e7985a894fba88182afd511e801418abf36ba7a9669e8ada
+size 54039
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/22bf3e72e46aed04ae8d8cc27f802995_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/22bf3e72e46aed04ae8d8cc27f802995_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..88ce0d6cf2f37b0ebafc2e4c9ab622afae7c5e5e
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/22bf3e72e46aed04ae8d8cc27f802995_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:71b788116618b5207a57b10a70e86595d30d477afab39d1a7a90e6df95629629
+size 40514
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/26a7a1b6f7ec54302b6fa07ad23380b0_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/26a7a1b6f7ec54302b6fa07ad23380b0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ac00b07f9e89073556c104e357bc8b8604498fdf
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/26a7a1b6f7ec54302b6fa07ad23380b0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ad05df0044163b17647aef92f2976b4748ee0ca3c3c1557eff6172acb30733e2
+size 51216
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/27d6042f4bce01ea5789efbd9e8d1f50_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/27d6042f4bce01ea5789efbd9e8d1f50_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7cf61d17b1b2f43417b32bb7ddb59525a9203638
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/27d6042f4bce01ea5789efbd9e8d1f50_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:19cc462065846c797ddec72f6ac7a8e81e62c9df2262f87a0b0ecfc9201f9b7c
+size 83774
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/2cca454bbea734b85b2a785da04388f9_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/2cca454bbea734b85b2a785da04388f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ae744bf3d5b3c4ed63ac86877144633ecc63f1ff
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/2cca454bbea734b85b2a785da04388f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e788410892c79b9fe21aaff21d99be85ff6f6c6fbc619593d0e9077216901ae7
+size 19017
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/2f108a589e99e93fd7aa8fac626398c7_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/2f108a589e99e93fd7aa8fac626398c7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2be62bf5c92f7c9129a4241204aa50d9b4e15146
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/2f108a589e99e93fd7aa8fac626398c7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bc780fbed5301b43d9de2345b9690114db9ebfc115096939cbd3ede60b07bac8
+size 25047
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/2fbbd361d3aff2374a19eb4fe03983bd_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/2fbbd361d3aff2374a19eb4fe03983bd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..16c598a014cfd0667bbc1b8506443de6797c136d
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/2fbbd361d3aff2374a19eb4fe03983bd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ec5e8fb88b858be9fd5c10d36cb8f87b32462d05fa579ef32f7e95243a812902
+size 27302
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/330e22134db7091a48c4c2366006c0d4_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/330e22134db7091a48c4c2366006c0d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4d50311f986104d5f76041c45710d106d8d6199a
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/330e22134db7091a48c4c2366006c0d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:53cb640b82c436eab47d49e9004ff699f6a9c1d8c03636d524ae9aa3eb6e9398
+size 42516
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/38d82ffe820e339811b396206f40a201_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/38d82ffe820e339811b396206f40a201_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5083c624b7e0b993fc1d371bef6b4ea63b249bee
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/38d82ffe820e339811b396206f40a201_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5cb7ad4b1711d5fa381dd86e11cafbf1de0ddf7da45586d173f200445c9a2168
+size 44421
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/39729be7ec83c3de8e480061966e4505_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/39729be7ec83c3de8e480061966e4505_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f9bb28abd9120018f2af6d8f884de38928b425da
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/39729be7ec83c3de8e480061966e4505_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:76b3d141197e4c1ad670dba67a0fecfd041daa01e88ba6a14f0ca1eb4264d531
+size 21633
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/3c04b14104f95eb8f7100f6d497d956e_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/3c04b14104f95eb8f7100f6d497d956e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..165ea7afba7a7f999e65feda98fd062c4bc8e256
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/3c04b14104f95eb8f7100f6d497d956e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f964bf1b268a6ed4b9d7cbc0c2856433445261f14f4951d4df2655a20af044ed
+size 5132
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/3d46409f8d0190e611a910ff27f8ec07_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/3d46409f8d0190e611a910ff27f8ec07_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a5c7c6f905ee00578da2abda3b7b8e1844211dd1
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/3d46409f8d0190e611a910ff27f8ec07_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:574be0ff99d395833570e1a37244616427f0c5b8911b30f3d422b2eedc973ce5
+size 27010
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/408c4798ea60469e0728a7cbbd598668_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/408c4798ea60469e0728a7cbbd598668_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f6954c3d4ead2868941b5cdf8dd11a4f9781e74a
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/408c4798ea60469e0728a7cbbd598668_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0d9afbd73eacc03a03157067e0291c85ad408f47ec8573f0f11c23b768c6dd78
+size 23098
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/43979979715bb3304389a0cb18f34444_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/43979979715bb3304389a0cb18f34444_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d70ce60b3cb3569ca6ca54a6afd7ad9ac427f478
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/43979979715bb3304389a0cb18f34444_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a98a53869a0f1779cc635491544d2f1ce7594c811aad07eb2bdab21cda9431bf
+size 10340
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/49d7bfbc65a92a7e1bd61777326a212d_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/49d7bfbc65a92a7e1bd61777326a212d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..503828760d78fe8eebab658c4482d1ab5035464f
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/49d7bfbc65a92a7e1bd61777326a212d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:19d8576c47139d660b7c60e93fae4f493c44e92f9736a5e7909dfdb6d171117a
+size 44853
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/4ecb55f0a56c2f3deb9eeddfde39d501_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/4ecb55f0a56c2f3deb9eeddfde39d501_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6427ac450f730bcd989b8912dd75271c98ec9406
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/4ecb55f0a56c2f3deb9eeddfde39d501_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a5e7e9b5b2632da13f360f3796fd56070109acf1933c7e876fdf5469fd4eda9d
+size 18640
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/4fed8a9f7064898f635d0f83b0a1ae61_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/4fed8a9f7064898f635d0f83b0a1ae61_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3facf69568ab9275ba86d200d184a9ebc131c068
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/4fed8a9f7064898f635d0f83b0a1ae61_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2999cede4c2475a56771b51f42da75e2bc187c3497bac7212f1772f7f60625c4
+size 46654
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/5525e7460947727851585808324e1f98_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/5525e7460947727851585808324e1f98_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4394e72d1fa45bad9fbdfbd9172aad462b0879c9
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/5525e7460947727851585808324e1f98_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:651a13c8c8716049557e1d3725e027222b06732252947d716c5c4ce0ffdccb93
+size 45337
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3f2599b546045e07154c9f18f2989df7674be7a6
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e104e1099c2bdaa98098338219f59099f9053ada4e73df2a5e8d6046a080579
+size 80133
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/6e9d059430baba0c363e33749f68b107_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/6e9d059430baba0c363e33749f68b107_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ca9c9ba19d3273b896d16e619cffb1c6b3559a27
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/6e9d059430baba0c363e33749f68b107_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2fe03c9744162d07d491e33a69ac481adcbac3a30b60cbcfef434dffacaaa94
+size 20925
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/708e4c9a044ef61f586126676eb2eeb8_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/708e4c9a044ef61f586126676eb2eeb8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..228a95965282bc9d8853eefb0156c784ec61f329
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/708e4c9a044ef61f586126676eb2eeb8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:40451ffbc86b88e47a14d12a9c62bd9f3c8e5c9ccecdf700d290d9a45924a73f
+size 24187
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/708e7ef81dbf726e558047afe57d6ff7_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/708e7ef81dbf726e558047afe57d6ff7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..786e6b49cbb888343bb5e52517d68ca76f6c450a
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/708e7ef81dbf726e558047afe57d6ff7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3dc38664d2a7e8c03c3e968187443552ffa0102f8f181b9d169c275ef5a0b32a
+size 35375
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b4bf5d9dd72571988a60e1663abefb2a586631c5
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e684c49e16652b8caaea441ebf0ae02cf9e94056eaf0140c95068da0b998826c
+size 118072
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/79403f771ea4876ca26ecee2f288b1d1_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/79403f771ea4876ca26ecee2f288b1d1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f23a4f213cd4099a8f2fbccd4add57026446d3db
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/79403f771ea4876ca26ecee2f288b1d1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0a6bb4e160d0a5126af2d38ec880cf41c2897c37aba652378c64961db33fa2dd
+size 45133
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/7fdddd449ff61579cf1f067a3bde63b0_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/7fdddd449ff61579cf1f067a3bde63b0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7d08d88fb13ddd2f0fce1b890b89f372721c26c5
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/7fdddd449ff61579cf1f067a3bde63b0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9b22baff090d1bdfca69f9f810a445d04def599552adf6ee0ff5846cc8ce93c7
+size 50366
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9d9265f3181309b26e82da1159a6da22947c7f9f
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d732f7e41def2a90ed7583b4d12bbfe2e4dfefbee0065077fdd56b9b73e2aca1
+size 15545
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/864e6cb4a0166a5b21a5d19f694e1606_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/864e6cb4a0166a5b21a5d19f694e1606_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..34a7dca5eaf53d2211ea9685dd59a1461e1a47b1
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/864e6cb4a0166a5b21a5d19f694e1606_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae252e1845fff3c25784868ca3e12da3b2e8455584cc9c0ac6fb73dc7cf0a86a
+size 15081
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e5b66f28a2900f120d825e1b26ba161c93ef6cd1
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5b031d139369c8e4cd666f5799a7b020336f5d3679db56bbf8104551e29f0d9a
+size 91551
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/9cf678d634932a43b7f6582878972a5d_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/9cf678d634932a43b7f6582878972a5d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a81d68fd4fec6d5b60f4753524f5b3fdfe99d84b
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/9cf678d634932a43b7f6582878972a5d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ca2ee8859a8d682fc56dfcfed97cafb8f2aad1407be6f00b36ef7e37a013a54f
+size 21861
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cbf082f7835c32a9d3a8e309be6dc9c2278ce6c8
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:06f348ffa1b49efa3e6b952b281f801a70607bad9b56dfab6c76d25e95fe2b41
+size 21495
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8210e9001bc8dacbb58da43d18a668653b92743f
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bb823ad0faa1a78301e4875aab6260f4c6b51e57a0e4b22ef04409ef6bdd4c9c
+size 30336
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/a76fa39f5daf6a026e032495262ed0f6_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/a76fa39f5daf6a026e032495262ed0f6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2b8dcccb8de2c632d3a8371c7f8f0e04d41370f0
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/a76fa39f5daf6a026e032495262ed0f6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ca33abfd9ccb0fb7b68c4abf285a96b46f2f14689c38680090f4733189b531cf
+size 29436
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/a83c022a6dac411615bcc38b7cd0d573_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/a83c022a6dac411615bcc38b7cd0d573_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..66420039345a6b02fae8a601403907dcafe0f743
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/a83c022a6dac411615bcc38b7cd0d573_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aff94bb324bc2a67a75cfc358af86c09fae747a95d88576e4e11fc42a1286e80
+size 103003
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/a98f3ef00da8508d2468334c6867f90f_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/a98f3ef00da8508d2468334c6867f90f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b55d88d33cfcbd3bf0c5199a302bb2e1a6efd793
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/a98f3ef00da8508d2468334c6867f90f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7384ecc488a4ba7a92fd9caf74c593973402b17a3a8673c5ab220070e91082be
+size 36547
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8f0c7d0482fd3464db84e434bf5d2296923938d4
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3825721046e4493dd35f6ff2e4c159458b722ff69c3718be79f62db3b2f32575
+size 84833
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b623ffa5ec6974e100d9de6c86212a2d37950ba7
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b8413119594067a4b3b2b7d3e90411f416ea10b0f896f63d32088041b99dff6d
+size 35000
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/b753a53960aa3a47023b9f767e02fecb_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/b753a53960aa3a47023b9f767e02fecb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..692f77dd6c841c5a7936199933aa483bc7e5f973
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/b753a53960aa3a47023b9f767e02fecb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:86cb8000d19ec093d5053c5aa3b480205b56eda6977c812415f6ec2fc196b206
+size 26262
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/b9745e4d501fcfe72053e7211ab39fed_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/b9745e4d501fcfe72053e7211ab39fed_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..24b6db59099abff37a2ecf934b4e5d2e7e2b425e
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/b9745e4d501fcfe72053e7211ab39fed_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b7d7a49adec92a554570944a513fddb2664784bbf7cca591c9e94d2ef3348822
+size 86010
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/b9f3b61f140ea64afb9205312d52eb0e_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/b9f3b61f140ea64afb9205312d52eb0e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d3076f8e26b069ae7820533bfccd9da58948001d
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/b9f3b61f140ea64afb9205312d52eb0e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2a468ec633eb80d28a1192b6b7543eff24d1722979eb6821404a84820650a271
+size 33261
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/bbce254e33d654e2077bd1e3e9beae8a_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/bbce254e33d654e2077bd1e3e9beae8a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..856003e221bbb7d0713aa3f9d61fe76de656e658
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/bbce254e33d654e2077bd1e3e9beae8a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:90f16d942c347be876810d0eeed9a4345141bb667202e786ee5500e9eda88a5f
+size 30389
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/bc6f20871b4f01c61470306c304fc9fe_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/bc6f20871b4f01c61470306c304fc9fe_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ef911155eb1db7dacb3f5bca7539051f627a626a
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/bc6f20871b4f01c61470306c304fc9fe_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4ca10b3b2310b6efcb03d2b8c9098a4a317526e87b7a88427f04d30999a8df40
+size 15957
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/c19f37cdfc7768db716bfc0cc5934cfb_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/c19f37cdfc7768db716bfc0cc5934cfb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d99d5ce2ea5fd99d0379274fe6f2e1b49e5c6acc
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/c19f37cdfc7768db716bfc0cc5934cfb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:37bb865e8f4aa5c33b6abc3c69d3575ea2f0211b471709910704e6dccc8c864a
+size 38105
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1086cc33498e3f8ede1649295833406bb53ac9bf
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5640005347faec47c438fcfdcc0852853bf9c1b22fc4e07fb6c56ac829fd1843
+size 162161
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..93ff0ea09b8f11daaa8e1cd221eec2cdd6b59c50
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6eb6bd111b8b4f1485de05febeaf2ebd3000379293867089336fefdc034e27a8
+size 112422
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/d7896dd2d38adf224c3b76cd22d29c10_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/d7896dd2d38adf224c3b76cd22d29c10_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d0f4c3ed9d8aa107ea2244b5f72379ddea92b402
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/d7896dd2d38adf224c3b76cd22d29c10_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:139c3e2281a0961c15033b7b1d1b0a7c9ef4c0d33f0c3a356b4de533485b55ff
+size 56394
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/dbbf61c7ed2ecc71307e31402743ca6b_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/dbbf61c7ed2ecc71307e31402743ca6b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a5492e53589db1c4226b6f2b22abeaf281e3b7b4
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/dbbf61c7ed2ecc71307e31402743ca6b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8046dcf1b51a9c92723967095361c6af2bf8caaf42077bec8936afde29bfb9e8
+size 115888
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/dbd4bab54b57e8d1abf80e3de6471130_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..722e814913faa2523b54cca0ef9c87389b69b94a
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/dbd4bab54b57e8d1abf80e3de6471130_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cd5aa5ffd288f0f3561b8f8084c85c0fc2ada685b0f89a59608817388f841d5d
+size 24645
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/dd00cc2325415c09afb8bf178f60f33b_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/dd00cc2325415c09afb8bf178f60f33b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4a1b87b56b55da51df52cd9bd6665492d804f609
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/dd00cc2325415c09afb8bf178f60f33b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5cddb359d1207f22b57a224dad33bf7b39a71d1e7257075f6090cf7864f4c91d
+size 35893
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/dd8d0fefeae62d64861afbb42b0df50e_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/dd8d0fefeae62d64861afbb42b0df50e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c27d5871e651b7544ca5f1705b83e7170363a76a
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/dd8d0fefeae62d64861afbb42b0df50e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9f9cb942a1fa05b8283efa5439205d8f724ae7e5754acc4bdfee3c37d1f181c2
+size 32997
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/e2245b4865907ad1259fd155f4beb6cf_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/e2245b4865907ad1259fd155f4beb6cf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4a39fd203ba2638d2d18baaee278a31b99800c71
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/e2245b4865907ad1259fd155f4beb6cf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cd08131e01c8e2fc7410781e8962f6fab7d1979abb4e37629da80c837a3cc01d
+size 47485
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/e5ded42f8e352da02ee86cb55550c45d_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/e5ded42f8e352da02ee86cb55550c45d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..793fdd71d7f49a62d59a843397d4a108afa81047
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/e5ded42f8e352da02ee86cb55550c45d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3ac3f48c8373bf5635d7b9101573cff9c5738e8d71687a8598ac5168d2facaca
+size 38790
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/f2a3faa7fc860dd26eda5b88460b0bcf_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/f2a3faa7fc860dd26eda5b88460b0bcf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c2048050576bcf8286d15633342f951abaee65d7
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/f2a3faa7fc860dd26eda5b88460b0bcf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2a00e0aeefdccc3aa3e928ff7410a0e185b73004c5c935ac8a274b007319d535
+size 60331
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/f54b2e4444e410765295be668123f27a_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/f54b2e4444e410765295be668123f27a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c55ac18dd1f472ab5fe62b1007ff26d569919712
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/f54b2e4444e410765295be668123f27a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9599cafe1812e2b736505f1763231c5b677485fd54f283b1621cef75cb639da9
+size 56217
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/fda85db2e355bb8e3edcd5a74bf3d673_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/fda85db2e355bb8e3edcd5a74bf3d673_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..624d082cfd89e3c97813b5f79e4d0236e664578b
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/fda85db2e355bb8e3edcd5a74bf3d673_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3cc5e95c8dca79981a350c2cbdce66a37c6844822daf9aac82655267c18abffe
+size 56238
diff --git a/marked/H/T-REC-H.263-200501-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg b/marked/H/T-REC-H.263-200501-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cdaf62ea0b39a5d985475c1321dd2de999d65880
--- /dev/null
+++ b/marked/H/T-REC-H.263-200501-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4b476bd701bfd72ffe9a873dbfee43417599cc9182f723667dbb5dbd42bc1a96
+size 28655
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/03703ee0fb20f67f19e3eb7c97a4b1e4_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/03703ee0fb20f67f19e3eb7c97a4b1e4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..04cfd2567bf37256e15e830323aaf91566d357c0
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/03703ee0fb20f67f19e3eb7c97a4b1e4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d28405a43cbc0e566de13a8d46696a7faf543570daf53362aafbb9c31583c7a8
+size 15227
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/09e581718ac5e06150e10552056892f3_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/09e581718ac5e06150e10552056892f3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6e5a9a32f696afe8fec0399a903838175a5e39d6
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/09e581718ac5e06150e10552056892f3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:13b586f661a0e1bf0cd92372f6920c09dabba7a24507aeab8190aa22e739f09c
+size 47546
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/15fe9d98813f20e61e8f2177ed1b84b4_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/15fe9d98813f20e61e8f2177ed1b84b4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ad6f62ed9d0428d6c3e593a6cea956a76234a189
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/15fe9d98813f20e61e8f2177ed1b84b4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:621b95d764bf9f1feb21a2791f4698bf13cf4ed2a04a72b187fca819b49a0790
+size 14086
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/166d8ee3cc0c825044a113560f81799c_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/166d8ee3cc0c825044a113560f81799c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6476a6e1cf2687ae9893bf533727c8119cade46f
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/166d8ee3cc0c825044a113560f81799c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e31fa0d017f0278304a455ab8b8223ad6bb609db893be4f225bf49491ed191a3
+size 93724
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/1b2e5b12ac4f5d7bb2fa18524982f2d8_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/1b2e5b12ac4f5d7bb2fa18524982f2d8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4916515666ead413f2b9245aafef3afbb9284a35
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/1b2e5b12ac4f5d7bb2fa18524982f2d8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:24d6346400c3fab9d8780ce21c94f7da9b6ebc72dea052247414f4d772544f40
+size 31539
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/212f85622719de88fe92d2a398eb778f_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/212f85622719de88fe92d2a398eb778f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..80f1b9dab104722e898848541bb2ee52710c656b
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/212f85622719de88fe92d2a398eb778f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ea32f6b4104d908e0e38c9d044846fa6caad12fcd96824a610ddc64afc8c35dc
+size 54545
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/22a8a787e18103c0859f95076ad941b5_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/22a8a787e18103c0859f95076ad941b5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..de04f54d7efc0f9d6900e1a96f39e24396dedac8
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/22a8a787e18103c0859f95076ad941b5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a2385e7d9a20c784603919cbf3afba9ea13133a8a33676c00d6e3cff0599f882
+size 92124
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/237b76118be454462fc9b4e96adaa6c7_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/237b76118be454462fc9b4e96adaa6c7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e4c81cc4acc5949996e5f12b4bd7f8350c374770
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/237b76118be454462fc9b4e96adaa6c7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a69a24cea1cf80ecb6ac2291bbd7de50f60e98201a13b3a26068902721a76daf
+size 10920
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/2399254baf1cd3a8e04cf5313b4d9b8f_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/2399254baf1cd3a8e04cf5313b4d9b8f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..376c04b550fdf11fa57d260c854a4a999f963dd1
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/2399254baf1cd3a8e04cf5313b4d9b8f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:80452867f97520b5465a1cff71e8d372d4b6312188fb15c51e0d1ea8864bfc1b
+size 93419
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/24ca424ca19ebeeafb6a9249dcd7bcfa_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/24ca424ca19ebeeafb6a9249dcd7bcfa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a380fc3dd2244c0f6603ff6f011d23baacc7022e
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/24ca424ca19ebeeafb6a9249dcd7bcfa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:48a042d747abde97ecf62337e3d77a6c39c89a145d34c5f3398a264d01f6fc11
+size 66280
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/29aa6165ccf449dee0b4335676fa7b1a_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/29aa6165ccf449dee0b4335676fa7b1a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5ed3543dd03bb72cda46f7ddf439829136769c2c
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/29aa6165ccf449dee0b4335676fa7b1a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6737334e3389fdd06db63e05d5b2f41130283764c92a0b6d445d10d4aab9064c
+size 29343
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/37e0794107700a747532b186849ffa68_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/37e0794107700a747532b186849ffa68_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3c565817885a8eb3e9a9369a82fcf9f71b26e597
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/37e0794107700a747532b186849ffa68_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a048fcb9cfed028335470eeb21992092abd8c48f883f06951d3015abfc7c03e1
+size 140490
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/3c721884a92b102becb43b52f6110e47_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/3c721884a92b102becb43b52f6110e47_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..011d71bf7f92c522569a7b467cb9597c09073035
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/3c721884a92b102becb43b52f6110e47_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:15c5b52a02c53d1caf9d365fc8c63876b984e0daf86216b02edde4fea391d2b2
+size 9293
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/460111aa57aedbb167f7464b02748cef_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/460111aa57aedbb167f7464b02748cef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3976b8ec849ffef2fc8d09198d4f40c8c0e3f42b
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/460111aa57aedbb167f7464b02748cef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d7847fd7522b27eeaf6d658645b1fff9857a1bc9172befe743211de8c2be518
+size 140023
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/4f2ed2a6c82bec5477b9e99a4b47e5e5_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/4f2ed2a6c82bec5477b9e99a4b47e5e5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c789872e81e6e9311284f2b2eb90f2e260806c1b
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/4f2ed2a6c82bec5477b9e99a4b47e5e5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:20f920b4ec57c4a7916a10a3df337942e348565af85c67d32ffd30a96a58e996
+size 24697
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/51b3f989269d40b52bbf69c7a448bf52_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/51b3f989269d40b52bbf69c7a448bf52_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d904c47608659a539a39169adb0dab1cbfcbc84e
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/51b3f989269d40b52bbf69c7a448bf52_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4272f4f8bfc903efb836a10a99dd15a6400f2cd84bd130453e16e11965ef84b5
+size 138761
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/527edc51c92c9d7126850c568985b4c8_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/527edc51c92c9d7126850c568985b4c8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9ed02e822708712013312ca588031f1df68b633d
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/527edc51c92c9d7126850c568985b4c8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:66f74f3167ebf275fd731b0d96fb1b33443c2ec6b4db9351dc700119c988d650
+size 51314
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/5a2819c2426bdc3b4d4593dc4b1fba4e_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/5a2819c2426bdc3b4d4593dc4b1fba4e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cfcbf86950a76d02b267f7118d5562927ee281bd
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/5a2819c2426bdc3b4d4593dc4b1fba4e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:93d9541ecc5dba704185d18f1e80137013eaf277afc72091fcd89a8fdc96286a
+size 139038
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/657acccf744d33f1fc3a1652741a256e_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/657acccf744d33f1fc3a1652741a256e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f37b5bc4dfa5d618224d2d2c71345da97b572fa1
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/657acccf744d33f1fc3a1652741a256e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2b5626f3f8944c229929d352233663f1d3f01e7bdbcd4e337e9c412d5140e3af
+size 31561
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/6afc9bc8eaf6acd589f4f81494c19c5a_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/6afc9bc8eaf6acd589f4f81494c19c5a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..059063f0277eb37295b048903aa05dc0bbea0cea
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/6afc9bc8eaf6acd589f4f81494c19c5a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8c45c3ca92fe6662f1720c94dd71d28c356ecd422ba93232a22343edc139f198
+size 96060
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/6ef03c6e28f2f1fd4f98529146ffeccc_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/6ef03c6e28f2f1fd4f98529146ffeccc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b841bebe323caf8934a1862579effedc1dff99b5
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/6ef03c6e28f2f1fd4f98529146ffeccc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:55563dbccbdd81a318d5f926e1b5700282b7a7cb3f2eb47b0ae3a85a44c16b42
+size 27623
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2ffab539dd457f713eef5846fe428cfc26712a5c
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2b15b17ac6c3d3bc7c8b9b9a7d3ec97735af160f9a51cd2c0f4ed7f057e1a534
+size 92698
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/71d7b20ced0151b68d524e8163f48ecb_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/71d7b20ced0151b68d524e8163f48ecb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b912a2914c1a4c84f663b381490b3ebafeb80c5e
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/71d7b20ced0151b68d524e8163f48ecb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:50e3f3e204159cdafe915eaabde5d74ab56144481dbdb52d70ead1c1df4ba597
+size 140235
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/75b9cb95f5815d6f3bbe57020a049504_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/75b9cb95f5815d6f3bbe57020a049504_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..93ed77c41f4f91c68377addd71d61a376673ab13
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/75b9cb95f5815d6f3bbe57020a049504_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2a7a42194aacde13c23614813408bf518a0b99b329becf8282b1178dc64b834e
+size 23719
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/7b325ed905fc90e53b5696554528d6e3_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/7b325ed905fc90e53b5696554528d6e3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d392207e01f43add2a14b66515c131d7667ec606
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/7b325ed905fc90e53b5696554528d6e3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b28d4e61e759a1fcdfb83fe18132fc96c9d7b626fc0816a6507cddecc2680adb
+size 140140
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/83a2e09b22f494ed17fc9c23d1cd2921_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/83a2e09b22f494ed17fc9c23d1cd2921_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2f0c57d0d796084c4e13935e4375b8a798ffd4fe
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/83a2e09b22f494ed17fc9c23d1cd2921_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1b2b0989565e14eba6ce63e289a4461677ab31f00655abd5a63e1f74f090e7d7
+size 142729
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..abda52cbb1047d6649f89e40c898a1c33bed7267
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6f3b7e07231c0f3e116c99c493bdda98ecd52313b6735faa6cea23815cf3162b
+size 7190
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/84d7d5863a5092cbe730c1baeb4fae2e_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/84d7d5863a5092cbe730c1baeb4fae2e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..341072881fd7dbbcf5f18f0aa9a607381b409e19
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/84d7d5863a5092cbe730c1baeb4fae2e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eb93a88424d5a561cec98f10bbce9a5f4c85afaaf70a7b029b56ce924ffd0aba
+size 39269
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/886a88caad59e8f8b1cf54c72e8adf4a_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/886a88caad59e8f8b1cf54c72e8adf4a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..53f3b3b2f70edfec834bf4f1034da050be343e51
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/886a88caad59e8f8b1cf54c72e8adf4a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:97d24e4a76d285f7cfc74a70bb2b86667495f93d2d5c134355c7b86c239fa459
+size 45140
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/8c126c290eea7c5d7807a293fd40f2d9_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/8c126c290eea7c5d7807a293fd40f2d9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d03ef3caa62c228d58b1abd6411432cc9e543b8a
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/8c126c290eea7c5d7807a293fd40f2d9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7a53e623223deb3a000577eec53cecd3fd98056aafd84398df6e30d6ddea7ec6
+size 77912
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/8e2056c5aa3b9d2021a48047657970f4_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/8e2056c5aa3b9d2021a48047657970f4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e4c091f0d0e024d4fbc228f781d8bc99951bdc89
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/8e2056c5aa3b9d2021a48047657970f4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bbb4f5e6c50beb92d5e592381ecd75de4da2afea3cb224386b3ae16218e1b021
+size 140020
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/8e77aa74bd5ab059077bf9bdb397e287_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/8e77aa74bd5ab059077bf9bdb397e287_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3a20f69227dc0d083c076294e8cd97b992681b12
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/8e77aa74bd5ab059077bf9bdb397e287_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7e39bcca7176fc516d2d2d57b0cc20b17e8ce84e00903636273e1018f1f4f493
+size 17534
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/8f8dd46963501da43c58707865c44cfb_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/8f8dd46963501da43c58707865c44cfb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0c7613a2bbd243b5d94baed9740180983e88bb83
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/8f8dd46963501da43c58707865c44cfb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5d8c8305b317eb471fdb41b3f8d4e6b024627c6df7c77c6d760af51e4f62ec4c
+size 27220
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/91ee3a5581ec88bfc52991720cd93795_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/91ee3a5581ec88bfc52991720cd93795_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..84c3e4e1568a2c33f74c92e7d8644e1e861ff172
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/91ee3a5581ec88bfc52991720cd93795_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:13bc5a21c9f956803a83f531b4eadd919cd2c7235fb33e53feab8d5e2be44c68
+size 140580
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/926c64a6177547a91f650c4c6f85ecb2_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/926c64a6177547a91f650c4c6f85ecb2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c27507a9fed3b4cc62123b66424373410b334266
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/926c64a6177547a91f650c4c6f85ecb2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:89f11bdf9aa1908b770cd4fcdac3774399fa6f09b5be629374b272c9efba99f7
+size 138888
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/9a627a1ad2e909ac4af71874ed1b0502_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/9a627a1ad2e909ac4af71874ed1b0502_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1f9b1390ff76debe51543d0cb5111b4742c8ffb5
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/9a627a1ad2e909ac4af71874ed1b0502_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3016951808fb15efa0f770e17aaefc23e055c381405ee7238df89fce140d2939
+size 20217
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/9ad891694657f787cf68e07db7060576_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/9ad891694657f787cf68e07db7060576_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..58c0d3b4dae46c2b2b21d2dad8656ec508383f0e
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/9ad891694657f787cf68e07db7060576_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:43457d43ca0ac6853683791e1a7361b855737fae68978fc0ca3f61593cbf4e78
+size 32602
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/9f92854fe6ecaf47760515c891a4fccc_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/9f92854fe6ecaf47760515c891a4fccc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..80690fab0b589c495732c2f487664170637e80dc
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/9f92854fe6ecaf47760515c891a4fccc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6b6b84759210b81e0389d28496549b642bb991df0bfe9841a82fc2d1a0ecc13f
+size 22814
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/ad9b0c8d0d3fc421b0dbc2ecc61376f4_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/ad9b0c8d0d3fc421b0dbc2ecc61376f4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0cee0c6fc5c289d78c7a8fa5884419387cb0384b
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/ad9b0c8d0d3fc421b0dbc2ecc61376f4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1ee1f1f10948b9079a0618727ca53eaf28837172fb1a70b25976e2f8e65031ef
+size 38565
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c60da6d2e082b2cb504c1d4ad164310a5bb07d19
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:167baa66775a9c88e7ce9a443cd3b14acf2681961d38d212f5a531b2df8d710f
+size 46391
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/bd0fe87fe6e236bc4778830b4f26d9e2_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/bd0fe87fe6e236bc4778830b4f26d9e2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4fc3522a59b5642fc66de296ef46f01edd43305d
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/bd0fe87fe6e236bc4778830b4f26d9e2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5e5e26c630c611f953bd692e0a5544999ae959dd9499a5a6c3063f187d490c6a
+size 38446
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/c3ba400c25c28fedce1c7d29414198de_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/c3ba400c25c28fedce1c7d29414198de_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fee89543f9cf910d9734b1f184d79c8311704732
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/c3ba400c25c28fedce1c7d29414198de_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:518cae4031031bb2246c2b1da8c3300afbc575c4a9ade904c9aa662959e3e81e
+size 13947
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/ce54f2a44c590dd67df743472e4de6d5_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/ce54f2a44c590dd67df743472e4de6d5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f29bef5db77768a3853c5c802d7f6678370e57df
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/ce54f2a44c590dd67df743472e4de6d5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7bc718ad4d78466305edc9617e1e778b771e13269bbe1f9d084ea12150eb6e88
+size 83655
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/cf9dafde28ab662345982f029d24ae77_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/cf9dafde28ab662345982f029d24ae77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a3fdb11b45d9d2c2647b5623f86b92cc991e3640
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/cf9dafde28ab662345982f029d24ae77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d7cda0d904fae59c94013edb69b429f144a480e70769228f1f7acd5472c1236c
+size 138499
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/d74ed29ed2b7aca01173043c14d46cab_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/d74ed29ed2b7aca01173043c14d46cab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9c5cc13e31deb27da60e2e12627bbf5161278073
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/d74ed29ed2b7aca01173043c14d46cab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a89f4d02f5c776128934147d02bbd27b39dd8faca41935491dc6b06d357ad2fd
+size 120648
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/d90f09fa97733a2cf12bb1ecaf8ddba8_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/d90f09fa97733a2cf12bb1ecaf8ddba8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ef229aeca18ec5265e2e7ee4405f6e760c1ec238
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/d90f09fa97733a2cf12bb1ecaf8ddba8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0407e411be33b4eaea92acb138a60c5fbd9732617e01b8f4bec7783626b01697
+size 49987
diff --git a/marked/H/T-REC-H.264-202408-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg b/marked/H/T-REC-H.264-202408-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..df79359aded2546d8838da40a8c0f4fc98827684
--- /dev/null
+++ b/marked/H/T-REC-H.264-202408-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7fbadaf633e72008ee8e00716166bec548c7a11b4d1b77e65374dc6fcac90b4f
+size 29036
diff --git a/marked/H/T-REC-H.264.1-201602-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.264.1-201602-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4f0dce751117f08d79053b75ca2cd249c7742317
--- /dev/null
+++ b/marked/H/T-REC-H.264.1-201602-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fcced544a68aa46dc98cd073d2093847511c2b8b862f3aa111fc60443c33cd48
+size 6849
diff --git a/marked/H/T-REC-H.264.2-201602-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.264.2-201602-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6b24036c6a7510d0ce14eb8a5f8a14f8739e8f9a
--- /dev/null
+++ b/marked/H/T-REC-H.264.2-201602-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f9e14b6a6883b343ddf4eee8a759e121085c44c63bcde76a275b5e372fb8cc05
+size 6920
diff --git a/marked/H/T-REC-H.264.2-201602-I_PDF-E/raw.md b/marked/H/T-REC-H.264.2-201602-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..92aa439a7c002394c68ad047f7dcade7e8b98717
--- /dev/null
+++ b/marked/H/T-REC-H.264.2-201602-I_PDF-E/raw.md
@@ -0,0 +1,306 @@
+
+
+I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n
+
+# **ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+# **H.264.2**
+
+(02/2016)
+
+### SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Coding of moving  
+video
+
+---
+
+## **Reference software for ITU-T H.264 advanced video coding**
+
+### Recommendation ITU-T H.264.2
+
+![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg)
+
+The logo of the International Telecommunication Union (ITU) features a blue globe with a red lightning bolt striking across it. The letters "ITU" are written in blue across the globe. To the right of the globe, the text "International Telecommunication Union" is written in blue, stacked in three 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        |
+| <b>Coding of moving video</b>                                                               | <b>H.260–H.279</b> |
+| 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.2
+
+# Reference software for ITU-T H.264 advanced video coding
+
+# Summary
+
+Recommendation ITU-T H.264.2 provides accompanying reference software for Rec. ITU-T H.264 | ISO/IEC 14496-10 as an electronic attachment. The software is an integral part of Rec. ITU-T H.264.2.
+
+The purpose of this Recommendation is to provide the following.
+
+- Reference decoder software capable of decoding bitstreams that conform to Rec. ITU-T H.264 | ISO/IEC 14496-10 in a manner that conforms to the decoding process specified in Rec. ITU-T H.264 | ISO/IEC 14496-10.
+- Reference encoder software capable of producing bitstreams that conform to Rec. ITU-T H.264 | ISO/IEC 14496-10.
+
+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.264 | ISO/IEC 14496-10. Requirements established in Rec. ITU-T H.264 | ISO/IEC 14496-10 take precedence over the behaviour of the reference software.
+
+The edition approved in 2009-05 incorporated changes made to the reference software for Rec. ITU-T H.264 | ISO/IEC 14496-10 advanced video coding. The changes contain improvements of encoder compression capability, bug fixes, speed and memory resource usage improvements, restructuring of the software for readability and ease of software maintenance, and the addition of support for new profiles of ITU-T H.264. The new profiles are from the set of profiles targeting professional applications that were added to Rec. ITU-T H.264 | ISO/IEC 14496-10 in 2007. No changes were made to the text of the Recommendation.
+
+The edition approved in 2010-06 contained improvements of encoder compression capability, bug fixes, speed and memory resource usage improvements, restructuring of the software for readability and ease of software maintenance. In addition, this edition includes support for the Scalable Baseline, Scalable High, Scalable High Intra, Multiview High, and Stereo High profiles. The support for the scalable profiles specified in Annex G of Rec. ITU-T H.264 | ISO/IEC 14496-10 (Scalable Baseline, Scalable High, and Scalable High Intra) and the support for the multiview profiles specified in Annex H of Rec. ITU-T H.264 | ISO/IEC 14496-10 (Multiview High and Stereo High) are provided in separate software solutions.
+
+The edition approved in 2012-01 only introduced changes to the reference software of Recommendation ITU-T H.264.2 (the text is the same as of the edition approved 2010-06). The changes in the reference software improve the encoder compression capability, fix bugs, and improve speed and memory resource usage. The software was also restructured for better readability and ease of maintenance.
+
+The edition approved in 2014-07 contains bug fixes for the profiles specified in Annex A of Rec. ITU-T H.264 | ISO/IEC 14496-10. In addition, the edition includes support for the MFC High profile specified in Annex H of Rec. ITU-T H.264 | ISO/IEC 14496-10, support for the Multiview Depth High profile specified in Annex I of Rec. ITU-T H.264 | ISO/IEC 14496-10, and support for the Enhanced Multiview Depth High profile specified in Annex J of Rec. ITU-T H.264 | ISO/IEC 14496-10, which are provided in separate software packages.
+
+This edition includes support for the MFC Depth High profile, which was included in the MFC plus Depth extension in ITU-T H.264 V10. It also includes miscellaneous minor improvements and bug fixes relative to the prior approved version. This Recommendation was developed jointly with ISO/IEC JTC 1/SC 29/WG 11 (MPEG) and corresponds to part of ISO/IEC 14496-5, up to and including ISO/IEC 14496-5:2001 Amendment 39.
+
+# History
+
+| Edition | Recommendation              | Approval   | Study Group | Unique ID*                                                                |
+|---------|-----------------------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T H.264.2               | 2005-03-01 | 16          | <a href="http://handle.itu.int/11.1002/1000/7826">11.1002/1000/7826</a>   |
+| 1.1     | ITU-T H.264.2 (2005) Cor. 1 | 2005-10-22 | 16          | <a href="http://handle.itu.int/11.1002/1000/8574">11.1002/1000/8574</a>   |
+| 2.0     | ITU-T H.264.2               | 2008-06-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/9487">11.1002/1000/9487</a>   |
+| 3.0     | ITU-T H.264.2               | 2010-06-22 | 16          | <a href="http://handle.itu.int/11.1002/1000/10637">11.1002/1000/10637</a> |
+| 4.0     | ITU-T H.264.2               | 2012-01-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/11468">11.1002/1000/11468</a> |
+| 5.0     | ITU-T H.264.2               | 2015-02-20 | 16          | <a href="http://handle.itu.int/11.1002/1000/12295">11.1002/1000/12295</a> |
+| 6.0     | ITU-T H.264.2               | 2016-02-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/12644">11.1002/1000/12644</a> |
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+# 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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
+
+|                                                                    | <i>Page</i> |
+|--------------------------------------------------------------------|-------------|
+| 0.1 Purpose.....                                                   | iv          |
+| 0.2 Examples of use .....                                          | iv          |
+| 0.3 Warranty disclaimer .....                                      | v           |
+| 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.264   ISO/IEC 14496-10 ..... | 2           |
+
+Electronic attachment: ITU-T H.264 reference software
+
+# Introduction\*
+
+This Recommendation provides accompanying reference software for Rec. ITU-T H.264 | ISO/IEC 14496-10 advanced 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.264 | ISO/IEC 14496-10 advanced video coding.
+
+The software has been jointly developed by ITU-T Video Coding Experts Group (VCEG) and the ISO/IEC Moving Picture Experts Group (MPEG).
+
+## 0.1 Purpose
+
+The purpose of this Recommendation is to provide the following:
+
+- Reference decoder software capable of decoding bitstreams that conform to Rec. ITU-T H.264 | ISO/IEC 14496-10 in a manner that conforms to the decoding process specified in Rec. ITU-T H.264 | ISO/IEC 14496-10.
+- Reference encoder software capable of producing bitstreams that conform to Rec. ITU-T H.264 | ISO/IEC 14496-10.
+
+## 0.2 Examples of use
+
+Some examples of uses 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.264 | ISO/IEC 14496-10.
+- As the starting basis for the implementation of a decoder that conforms to Rec. ITU-T H.264 | ISO/IEC 14496-10.
+- For testing the conformance of a decoder implementation with the decoding process specified in Rec. ITU-T H.264 | ISO/IEC 14496-10 (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.264 | ISO/IEC 14496-10).
+- For testing the conformance of a bitstream to the constraints specified for bitstream conformance in Rec. ITU-T H.264 | ISO/IEC 14496-10, 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.264 | ISO/IEC 14496-10.
+
+Some examples of uses 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.264 | ISO/IEC 14496-10.
+- As the starting basis for the implementation of an encoder that conforms to Rec. ITU-T H.264 | ISO/IEC 14496-10.
+- As a means of generating bitstreams for testing the conformance of a decoder implementation with the decoding process specified in Rec. ITU-T H.264 | ISO/IEC 14496-10.
+- 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.264 | ISO/IEC 14496-10.
+
+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.264 | ISO/IEC 14496-10, as the conformance of an encoder to Rec. ITU-T H.264 | ISO/IEC 14496-10 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.264 | ISO/IEC 14496-10, it provides neither an assurance of minimum guaranteed video encoding quality nor maximum achievable video encoding quality.
+
+---
+
+\* This introduction does not form an integral part of this Recommendation.
+
+## **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 disclaims 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) 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 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 <http://itu.int/ITU-T/dbase/patent/patent-policy.html>.
+
+
+
+## Reference software for ITU-T H.264 advanced video coding
+
+# 1 Scope
+
+This Recommendation provides accompanying reference software for Rec. ITU-T H.264 | ISO/IEC 14496-10 as an electronic attachment. The software is an integral part of this Recommendation.
+
+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.264 | ISO/IEC 14496-10. Requirements established in Rec. ITU-T H.264 | ISO/IEC 14496-10 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.264 (2007), *Advanced video coding for generic audiovisual services*.  
+ISO/IEC 14496-10:2008, *Information technology – Coding of audio-visual objects – Part 10: Advanced 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.264 | ISO/IEC 14496-10 (particularly in clause 3) apply. Definitions 3.1, 3.2, and 3.3 below replace the corresponding definitions in Rec. ITU-T H.264 | ISO/IEC 14496-10. Definitions 3.4 and 3.5 are additional definitions.
+
+**3.1 bitstream:** A sequence of bits that may conform to Rec. ITU-T H.264 | ISO/IEC 14496-10. A bitstream that conforms to Rec. ITU-T H.264 | ISO/IEC 14496-10 will contain one or more IDR slices, and may contain additional I, P, B, SI, SP, EI, EP or EB 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.264 | ISO/IEC 14496-10. The scope of decoder, as considered herein, does not include a display process, which is outside the scope of this Recommendation.
+
+**3.3 encoder:** An embodiment of a process, not specified in this Recommendation, that produces a bitstream.
+
+**3.4 reference software decoder:** The decoding software accompanying this Recommendation.
+
+**3.5 reference software encoder:** The encoding software accompanying this Recommendation.
+
+# 4 Abbreviations
+
+For the purposes of this Recommendation, relevant abbreviations are specified in clause 4 of Rec. ITU-T H.264 | ISO/IEC 14496-10.
+
+# 5 Conventions
+
+For the purposes of this Recommendation, relevant conventions are specified in clause 5 of Rec. ITU-T H.264 | ISO/IEC 14496-10.
+
+# 6 Reference software for Rec. ITU-T H.264 | ISO/IEC 14496-10
+
+The reference software for Rec. ITU-T H.264 | ISO/IEC 14496-10 is found in the electronic attachment to this Recommendation.
+
+The attached software package contains six separate parts:
+
+- JM software: Support for the Baseline, Constrained Baseline, Main, Extended, 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.
+- JSVM software: Support for the Scalable Baseline, Scalable High, and Scalable High Intra profiles.
+- JMVC software: Support for the Multiview High and Stereo High profiles.
+- MFC software: Support for the MFC High profile.
+- MVCD and 3D-AVC software: Support for the Multiview Depth High and Enhanced Multiview Depth High profiles.
+- MFCD software: Support for the MFC Depth High Profile
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.265.2-201612-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.265.2-201612-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4f0dce751117f08d79053b75ca2cd249c7742317
--- /dev/null
+++ b/marked/H/T-REC-H.265.2-201612-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fcced544a68aa46dc98cd073d2093847511c2b8b862f3aa111fc60443c33cd48
+size 6849
diff --git a/marked/H/T-REC-H.271-200605-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.271-200605-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c
--- /dev/null
+++ b/marked/H/T-REC-H.271-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.281-199411-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/H/T-REC-H.281-199411-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..91d19afadb119cec807b520093bf7aa82876ab8c
--- /dev/null
+++ b/marked/H/T-REC-H.281-199411-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fe79e12f6ae75395c3a42d8cad2a9c346ae9ed37e9261a1215ca72f5691f9f5d
+size 9598
diff --git a/marked/H/T-REC-H.281-199411-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/H/T-REC-H.281-199411-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cbc4f648431fc0a80e63ad18a6fae9cf82652ea3
--- /dev/null
+++ b/marked/H/T-REC-H.281-199411-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:10816e5a7f50714188098aee65792e46cae809384b7d4fb39f4892aae2421575
+size 19534
diff --git a/marked/H/T-REC-H.281-199411-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/H/T-REC-H.281-199411-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a91002c8d91ea61822be4f04ccf872e2f317563d
--- /dev/null
+++ b/marked/H/T-REC-H.281-199411-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:991f3c72ce6cee4140256077885d8a4a66edbf0d60cfee13d6be0354cb9c46a3
+size 27017
diff --git a/marked/H/T-REC-H.281-199411-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.281-199411-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1c7c8ff27b9fff7480ea06921d044959dd607324
--- /dev/null
+++ b/marked/H/T-REC-H.281-199411-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3dbbaecd59caaf6547472453981ab939ceac8c10bf379e1b1520c8bfe00a1635
+size 8210
diff --git a/marked/H/T-REC-H.281-199411-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg b/marked/H/T-REC-H.281-199411-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4cec21f9bdfc96a2d96cd37fc2b6f2bf0bb38da1
--- /dev/null
+++ b/marked/H/T-REC-H.281-199411-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8a3eb266e53c578352414ea4558b91ed9e0038afbed27ed57bf7671bfbe05844
+size 21598
diff --git a/marked/H/T-REC-H.281-199411-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg b/marked/H/T-REC-H.281-199411-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..638a67ca2f707813726e393d82c23eed0db8121b
--- /dev/null
+++ b/marked/H/T-REC-H.281-199411-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e0893a4114a26989ff8ea7349e851af8a68cb6928b391981844a8d1ecd71f77e
+size 17690
diff --git a/marked/H/T-REC-H.281-199411-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/H/T-REC-H.281-199411-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1c7e5775fec444fea5319a53f9be03d1cd1834ad
--- /dev/null
+++ b/marked/H/T-REC-H.281-199411-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d27dc8f2d174682f70b6e43b7b7ca283279f922b7ba1d9ef82122ce00079078f
+size 18228
diff --git a/marked/H/T-REC-H.281-199411-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/marked/H/T-REC-H.281-199411-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cc57b9672f0bf0baeb43f871c3f4cc15a5fadaab
--- /dev/null
+++ b/marked/H/T-REC-H.281-199411-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:72b823d4f2a5754932d8e0f2ce07526a20e38818ccaa723a18fe92b0432ae643
+size 37897
diff --git a/marked/H/T-REC-H.281-199411-I_PDF-E/b10763be31553f31cbb795653b731a43_img.jpg b/marked/H/T-REC-H.281-199411-I_PDF-E/b10763be31553f31cbb795653b731a43_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e18d6afecc7099ba0367215cc3b25d4e58b4713a
--- /dev/null
+++ b/marked/H/T-REC-H.281-199411-I_PDF-E/b10763be31553f31cbb795653b731a43_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02b3f22e5d0b14d863c45baf5c0fe9ba9dcce3e5f54fea060fde1bc5838f644a
+size 19707
diff --git a/marked/H/T-REC-H.281-199411-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg b/marked/H/T-REC-H.281-199411-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..97e8273d3c4a6ee340d75e5211d95d9173824231
--- /dev/null
+++ b/marked/H/T-REC-H.281-199411-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cf1ab308e17ae99da8e253ab288912ddcd776146dd07439e5255f826bfc7ee73
+size 17401
diff --git a/marked/H/T-REC-H.281-199411-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg b/marked/H/T-REC-H.281-199411-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..82199fe9c94b6310479718483e2dcdcb5fe0e8e6
--- /dev/null
+++ b/marked/H/T-REC-H.281-199411-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e97ac8a91171cd16ad55d2026dee8b062c6462d82c43d624f32ca9bfb7a84bca
+size 19149
diff --git a/marked/H/T-REC-H.310-199809-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg b/marked/H/T-REC-H.310-199809-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aa41c2c1122ee91793862c7885f38c705a8fbb24
--- /dev/null
+++ b/marked/H/T-REC-H.310-199809-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bd3908f7e347c737bfecfc957608898794bff9991d6c77583aa6ec39f2434694
+size 26044
diff --git a/marked/H/T-REC-H.310-199809-I_PDF-E/24c9e038a791677ed33100667b64f7e6_img.jpg b/marked/H/T-REC-H.310-199809-I_PDF-E/24c9e038a791677ed33100667b64f7e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8018ec15984337fe86c77510411f55cb31723209
--- /dev/null
+++ b/marked/H/T-REC-H.310-199809-I_PDF-E/24c9e038a791677ed33100667b64f7e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5de5062e51f1cc5747fc605d1cb74716217bafdf519c1193a9412cb2f3240532
+size 58591
diff --git a/marked/H/T-REC-H.310-199809-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.310-199809-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a7da83ecb82b51a4cef7694858eef2c35f1986ff
--- /dev/null
+++ b/marked/H/T-REC-H.310-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.310-199809-I_PDF-E/382a9c9e4816bd229191ab4591424dd8_img.jpg b/marked/H/T-REC-H.310-199809-I_PDF-E/382a9c9e4816bd229191ab4591424dd8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..69014e6971b364a4b22bad5094f5f3bdba93bcf9
--- /dev/null
+++ b/marked/H/T-REC-H.310-199809-I_PDF-E/382a9c9e4816bd229191ab4591424dd8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8e969ad7524f0b72094bd7533bbc43adc1103cd35b56c60d388518750eee592c
+size 18572
diff --git a/marked/H/T-REC-H.310-199809-I_PDF-E/3c04b14104f95eb8f7100f6d497d956e_img.jpg b/marked/H/T-REC-H.310-199809-I_PDF-E/3c04b14104f95eb8f7100f6d497d956e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3acce915f0f52ca54cd1203a025830a4f63e651e
--- /dev/null
+++ b/marked/H/T-REC-H.310-199809-I_PDF-E/3c04b14104f95eb8f7100f6d497d956e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9a6c143d7893f6356c226c27e8101bc80f6a0db78d91797f4be521d0eb35fc9a
+size 48808
diff --git a/marked/H/T-REC-H.310-199809-I_PDF-E/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg b/marked/H/T-REC-H.310-199809-I_PDF-E/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..790be526872f1e1012e57357367a5c102703bb65
--- /dev/null
+++ b/marked/H/T-REC-H.310-199809-I_PDF-E/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ac6a1af599013e8e39edffadb8f618a945efc93e9179e08f3552ac063d8c0203
+size 46467
diff --git a/marked/H/T-REC-H.310-199809-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg b/marked/H/T-REC-H.310-199809-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..117786a61c90be21652d4c248e522ddc574d0d8b
--- /dev/null
+++ b/marked/H/T-REC-H.310-199809-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d61ac7a56fce3f19370dc86407334afc2058ce1704d85e8d9ce29e996a4af187
+size 80692
diff --git a/marked/H/T-REC-H.310-199809-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/H/T-REC-H.310-199809-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..850d4f3d1737e897df2e79fa43e8172abee75f59
--- /dev/null
+++ b/marked/H/T-REC-H.310-199809-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d73f8d3f0b732c14c18307ffd838d12e63245e9f1cc06436685a8005e2d87a2f
+size 127238
diff --git a/marked/H/T-REC-H.310-199809-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/H/T-REC-H.310-199809-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bdac12bd5f6598ccd13c45ae330fcb146254667c
--- /dev/null
+++ b/marked/H/T-REC-H.310-199809-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7244f8328743d2e6ce6b5708251ae29dac94e88b7c53c1a6c94d3222c3eaae55
+size 121705
diff --git a/marked/H/T-REC-H.310-199809-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/H/T-REC-H.310-199809-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..710f6453d9cbf372c6604f9a934f6dd0d20f516b
--- /dev/null
+++ b/marked/H/T-REC-H.310-199809-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:29a265bb7fedb5683ed533e9a6144e8b866a4fb7999cb4c6eabdacfff11b05f4
+size 94854
diff --git a/marked/H/T-REC-H.310-199809-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg b/marked/H/T-REC-H.310-199809-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ef972007e7c46c231442a5a7f245a6c492a711ef
--- /dev/null
+++ b/marked/H/T-REC-H.310-199809-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1634b19ecbf2eead28429a36e2176a02b7ea2240d0717357b57fc34bfa26575b
+size 53524
diff --git a/marked/H/T-REC-H.310-199809-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/H/T-REC-H.310-199809-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..da25d0f4eec63565cc53db2d2993f6a778dd7a08
--- /dev/null
+++ b/marked/H/T-REC-H.310-199809-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7ad94948fdc3b31cc0466e382206749aefd35ed6ca3d558c3848cf8adacf942f
+size 82380
diff --git a/marked/H/T-REC-H.310-199809-I_PDF-E/dd6c544ab685b25dd17f59456efcfbfc_img.jpg b/marked/H/T-REC-H.310-199809-I_PDF-E/dd6c544ab685b25dd17f59456efcfbfc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..34d4759f05c271343ba321096cc0c09ee47b1692
--- /dev/null
+++ b/marked/H/T-REC-H.310-199809-I_PDF-E/dd6c544ab685b25dd17f59456efcfbfc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:42ba4dde17fc176dc1f14e15782241a668b8e85fa337e41b45786484ee4003f7
+size 48184
diff --git a/marked/H/T-REC-H.310-199809-I_PDF-E/dfafe39c233a62ec8ebd71e42992c14d_img.jpg b/marked/H/T-REC-H.310-199809-I_PDF-E/dfafe39c233a62ec8ebd71e42992c14d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b0441193062c4df5b4a9e4ac510bf727dd5052fe
--- /dev/null
+++ b/marked/H/T-REC-H.310-199809-I_PDF-E/dfafe39c233a62ec8ebd71e42992c14d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f748c70394b42a2b37468d5b3bc583c43bf368ca22b340765c07d0ca3d00ab2a
+size 23595
diff --git a/marked/H/T-REC-H.310-199809-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg b/marked/H/T-REC-H.310-199809-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..78d83186f0f1c7efef011d87bb7640cab0b42c75
--- /dev/null
+++ b/marked/H/T-REC-H.310-199809-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0cb108f7d983bfd86c6e71f4103bf59461818b31eed254134d38c2298dedf8ef
+size 75812
diff --git a/marked/H/T-REC-H.310-199809-I_PDF-E/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/H/T-REC-H.310-199809-I_PDF-E/fcc757566216206ceddbd6c775e8db02_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..22a654a8eb9932067d415c332176638bce3c85af
--- /dev/null
+++ b/marked/H/T-REC-H.310-199809-I_PDF-E/fcc757566216206ceddbd6c775e8db02_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:40a43097581de68016a9af2d10729564cabba25f391b803a528cc2a469af5ddc
+size 8633
diff --git a/marked/H/T-REC-H.310-199809-I_PDF-E/raw.md b/marked/H/T-REC-H.310-199809-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..8dcccbde97f34f78e75740427cebf8977e8ff88c
--- /dev/null
+++ b/marked/H/T-REC-H.310-199809-I_PDF-E/raw.md
@@ -0,0 +1,2029 @@
+
+
+![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.310**
+
+(09/98)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS  
+Infrastructure of audiovisual services – Systems and  
+terminal equipment for audiovisual services
+
+---
+
+**Broadband audiovisual communication systems  
+and terminals**
+
+ITU-T Recommendation H.310
+
+(Previously CCITT Recommendation)
+
+---
+
+# ITU-T H-SERIES RECOMMENDATIONS **AUDIOVISUAL AND MULTIMEDIA SYSTEMS**
+
+|                                                                                                            |                    |
+|------------------------------------------------------------------------------------------------------------|--------------------|
+| Characteristics of transmission channels used for other than telephone purposes                            | H.10–H.19          |
+| Use of telephone-type circuits for voice-frequency telegraphy                                              | H.20–H.29          |
+| Telephone circuits or cables used for various types of telegraph transmission or simultaneous transmission | H.30–H.39          |
+| Telephone-type circuits used for facsimile telegraphy                                                      | H.40–H.49          |
+| Characteristics of data signals                                                                            | H.50–H.99          |
+| 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        |
+| <b>Systems and terminal equipment for audiovisual services</b>                                             | <b>H.300–H.399</b> |
+| Supplementary services for multimedia                                                                      | H.450–H.499        |
+
+*For further details, please refer to ITU-T List of Recommendations.*
+
+# **ITU-T RECOMMENDATION H.310**
+
+# **BROADBAND AUDIOVISUAL COMMUNICATION SYSTEMS AND TERMINALS**
+
+## **Summary**
+
+This Recommendation covers the technical requirements for the systems and terminals of broadband audiovisual communication services defined in H.200/AV.100-series Recommendations. Both H.310 unidirectional and bidirectional broadband audiovisual terminals are defined. The classification of H.310 terminals into different terminal types is based on a set of audiovisual, network adaptation, and signalling capabilities. With these capabilities, H.310 terminals support a wide range of conversational and distributive applications and services. This revision enhances the interworking between different type of H.310 terminals.
+
+###### **Source**
+
+ITU-T Recommendation H.310 was revised by ITU-T Study Group 16 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 25th of September 1998.
+
+## FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the 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.
+
+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
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The 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, the 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 1998
+
+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 the ITU.
+
+## CONTENTS
+
+|                                                         | Page |
+|---------------------------------------------------------|------|
+| 1 Scope .....                                           | 1    |
+| 2 References .....                                      | 3    |
+| 3 Definitions .....                                     | 5    |
+| 4 Abbreviations .....                                   | 6    |
+| 5 Conventions .....                                     | 8    |
+| 6 System description .....                              | 8    |
+| 6.1 System configuration .....                          | 8    |
+| 6.2 Terminal types .....                                | 10   |
+| 6.2.1 Unidirectional terminal types (ROT and SOT) ..... | 10   |
+| 6.2.2 Bidirectional terminal types (RAST) .....         | 11   |
+| 6.3 Terminal capabilities .....                         | 12   |
+| 6.3.1 Video capabilities .....                          | 12   |
+| 6.3.2 Audio capabilities .....                          | 14   |
+| 6.3.3 Data capabilities .....                           | 15   |
+| 6.3.4 Network Adaptation Capabilities (NAC) .....       | 15   |
+| 6.3.5 Signalling capabilities .....                     | 18   |
+| 6.4 The use of the H.245 control channel .....          | 22   |
+| 6.4.1 Master slave determination .....                  | 23   |
+| 6.4.2 Capabilities exchange .....                       | 24   |
+| 6.4.3 Logical channel signalling .....                  | 25   |
+| 6.4.4 Mode request .....                                | 27   |
+| 6.4.5 Round trip delay .....                            | 27   |
+| 6.4.6 Maintenance loop .....                            | 28   |
+| 6.4.7 Specific commands and indications .....           | 29   |
+| 7 H.310 call phases .....                               | 29   |
+| 7.1 Native H.310 communication call procedures .....    | 29   |
+| 7.1.1 Phase A (call setup) .....                        | 32   |
+| 7.1.2 Phase B (audiovisual communication) .....         | 33   |
+| 7.1.3 Phase C (call release) .....                      | 33   |
+| 7.2 H.320/H.321 interoperation call procedures .....    | 34   |
+| 8 Multipoint communication .....                        | 34   |
+| 8.1 Native H.310 communication modes .....              | 34   |
+| 8.2 H.320/H.321 interoperation modes .....              | 34   |
+| 8.3 Other aspects .....                                 | 34   |
+
+|                                                                                      | <b>Page</b>                                                                    |    |
+|--------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|----|
+| 9                                                                                    | Equipment requirements.....                                                    | 34 |
+| 10                                                                                   | Error resilience .....                                                         | 35 |
+| 10.1                                                                                 | Video layer .....                                                              | 35 |
+| 10.2                                                                                 | Multimedia multiplex layer.....                                                | 35 |
+| 11                                                                                   | Maintenance loop .....                                                         | 35 |
+| 12                                                                                   | Intercommunications .....                                                      | 36 |
+| 12.1                                                                                 | Intercommunication between different terminal types.....                       | 37 |
+| 12.2                                                                                 | Intercommunication with N-ISDN terminals .....                                 | 38 |
+| 12.3                                                                                 | Intercommunication with telephony.....                                         | 38 |
+| 12.4                                                                                 | Intercommunication with audiovisual terminals connected to other networks..... | 38 |
+| Annex A – Protocol stack for control channel .....                                   |                                                                                | 38 |
+| A.1                                                                                  | General .....                                                                  | 38 |
+| A.2                                                                                  | X.214 .....                                                                    | 39 |
+| A.3                                                                                  | X.224 .....                                                                    | 39 |
+| A.4                                                                                  | LAPF (Q.922).....                                                              | 39 |
+| A.5                                                                                  | FR-SSCS (I.365.1) and H.222.1 .....                                            | 40 |
+| A.5.1                                                                                | FR-SSCS (I.365.1) .....                                                        | 40 |
+| A.5.2                                                                                | H.222.0 and H.222.1 .....                                                      | 40 |
+| Annex B – Use of DSS 2 signalling by H.310 terminals.....                            |                                                                                | 41 |
+| B.1                                                                                  | DSS 2 signalling information elements.....                                     | 41 |
+| B.2                                                                                  | ATM signalling required for the H.310 control VC.....                          | 44 |
+| B.3                                                                                  | ATM Signalling Required for RAST-1 A/V VC .....                                | 45 |
+| B.4                                                                                  | ATM Signalling Required for H.310 SOT/ROT-1 .....                              | 47 |
+| B.5                                                                                  | ATM Signalling Required for RAST-5 A/V VC .....                                | 48 |
+| B.6                                                                                  | ATM Signalling Required for H.310 SOT-5.....                                   | 50 |
+| B.7                                                                                  | ATM Signalling Required for H.310 ROT-5 .....                                  | 52 |
+| Annex C – Procedures for intercommunication between RAST-1 and RAST-5 terminals .... |                                                                                | 53 |
+| C.1                                                                                  | Introduction .....                                                             | 53 |
+| C.2                                                                                  | Two RAST-5 terminals on CPN .....                                              | 54 |
+| C.3                                                                                  | RAST-5 Terminal on CPN with RAST-1 Terminal on Public B-ISDN .....             | 55 |
+| C.3.1                                                                                | RAST-5 Terminal on CPN calls RAST-1 Terminal on B-ISDN.....                    | 55 |
+| C.3.2                                                                                | RAST-1 Terminal on B-ISDN calls RAST-5 Terminal on CPN.....                    | 56 |
+| C.4                                                                                  | RAST-5 Terminal on CPN with RAST-1 Terminal on CPN.....                        | 57 |
+
+|                                        | <b>Page</b> |
+|----------------------------------------|-------------|
+| Appendix I – Bit and byte order .....  | 58          |
+| Appendix II – H.310 CorrelationID..... | 58          |
+
+
+
+# **BROADBAND AUDIOVISUAL COMMUNICATION SYSTEMS AND TERMINALS**
+
+*(revised in 1998)*
+
+# **1 Scope**
+
+This Recommendation covers the technical requirements for the systems and terminals of broadband audiovisual communication services defined in H.200/AV.100-series Recommendations.
+
+This Recommendation defines both *unidirectional* and *bidirectional* broadband audiovisual terminals. The classification of H.310 terminals into different terminal types is based on audiovisual and ATM adaptation layer capabilities which are defined in 6.2. There are two classes of unidirectional terminals: Receive-Only Terminal (ROT) and Send-Only Terminal (SOT) classes.
+
+In this Recommendation, bidirectional terminal types are referred to as Receive-and-Send Terminal (RAST) types. The definition of H.310 RAST terminals is based on the following interoperability principles:
+
+- 1) Interworking between H.310 RAST terminal types and other N-ISDN/B-ISDN (H.320/H.321) audiovisual terminals is mandatory.
+- 2) Interworking among the *different* H.310 RAST terminal types is also mandatory.
+
+Three types of RAST terminals are defined: RAST-1, RAST-5, and RAST-1&5.
+
+RAST-1 and RAST-1&5 terminals may be connected to public networks and customer premise networks (private networks), while RAST-5 terminals may only be connected to customer premise networks (private networks).
+
+For interworking with H.320/H.321 terminals, all three RAST terminal types support common H.320 audiovisual modes. For interworking between RAST-5 terminals and RAST-1 and H.320/H.321 terminals, a gateway, that is not inside the public network but in the customer premises, between a B-ISDN and a customer-premises ATM network is needed to provide interoperability functions.
+
+The video and audio coding and other technical aspects that are applicable to more than one distinct service are covered in H.200/AV.200-series Recommendations.
+
+Figure 1 shows a generic broadband audiovisual communication system. It consists of terminal equipment, network, Multipoint Control Unit (MCU) and the constituent elements of the terminal equipment. The corresponding Recommendations are also identified.
+
+![Figure 1/H.310 – Broadband audiovisual communication system and terminal configuration. The diagram shows the internal architecture of an H.310 terminal and its connection to a network. On the left, inputs for Audio (G-Series, H.200/AV.255), Video (H.261/H.262), and Other data (End-to-end signalling via H.242/H.230 and H.245 Protocol Stack, and User-to-network signalling via Q.2931) are shown. These connect to internal processing blocks: 'Generic Packetized Multimedia Multiplex/Synchronization H.222.0', 'Packet-based Multimedia Multiplex/Synchronization in ATM Environments H.222.1', and 'Circuit-based Multimedia Multiplex/Synchronization H.221'. The terminal is connected to a 'Broadband ISDN network' (represented by an oval) via an 'MCU' (represented by a rectangle). The connection interface is labeled with 'A A L', 'A T M', and 'P H Y' on the terminal side, and 'I.363.1/5', 'I.361', and 'I.432' on the network side. A 'SAAL Q.2100' block is also shown at the interface. The entire terminal configuration is enclosed in a box labeled 'Scope of H.310'.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg)
+
+Figure 1/H.310 – Broadband audiovisual communication system and terminal configuration. The diagram shows the internal architecture of an H.310 terminal and its connection to a network. On the left, inputs for Audio (G-Series, H.200/AV.255), Video (H.261/H.262), and Other data (End-to-end signalling via H.242/H.230 and H.245 Protocol Stack, and User-to-network signalling via Q.2931) are shown. These connect to internal processing blocks: 'Generic Packetized Multimedia Multiplex/Synchronization H.222.0', 'Packet-based Multimedia Multiplex/Synchronization in ATM Environments H.222.1', and 'Circuit-based Multimedia Multiplex/Synchronization H.221'. The terminal is connected to a 'Broadband ISDN network' (represented by an oval) via an 'MCU' (represented by a rectangle). The connection interface is labeled with 'A A L', 'A T M', and 'P H Y' on the terminal side, and 'I.363.1/5', 'I.361', and 'I.432' on the network side. A 'SAAL Q.2100' block is also shown at the interface. The entire terminal configuration is enclosed in a box labeled 'Scope of H.310'.
+
+**Figure 1/H.310 – Broadband audiovisual communication system and terminal configuration**
+
+All H.310 terminals are required to support H.245 as their communication control protocol so that they can support their intended services and interoperate among each other. Accordingly, H.310 terminals shall use the H.222.1 acknowledged procedures for the subchannel signalling.
+
+It is important to note that the generic H.310 terminal shown in Figure 1 can represent any of the unidirectional or bidirectional terminal types defined in this Recommendation.
+
+The definition of H.310 terminal types is intended for the support of the following applications:
+
+- Conversational services (e.g. videoconferencing and videotelephony services).
+- Retrieval services.
+- Messaging services.
+- Distribution services with individual presentation by the recipient (e.g. video-on-demand services).
+- Distribution services without individual presentation by the recipient (e.g. broadcast TV services).
+- Video transmission.
+- 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; 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] CCITT Recommendation G.711 (1988), *Pulse Code Modulation (PCM) of voice frequencies.*
+- [2] CCITT Recommendation G.722 (1988), *7 kHz audio-coding within 64 kbit/s.*
+- [3] ITU-T Recommendation G.723.1 (1996), *Speech codecs: Dual rate speech coder for multimedia communications transmitting at 5.3 and 6.3 kbit/s.*
+- [4] CCITT Recommendation G.728 (1992), *Coding of speech at 16 kbit/s using low-delay code excited linear prediction.*
+- [5] ITU-T Recommendation G.729 (1996), *Coding of speech at 8 kbit/s using Conjugate Structure Algebraic-Code-Excited Linear-Prediction (CS-ACELP).*
+- [6] Annex A to G.729 (1996), *Reduced complexity 8 kbit/s CS-ACELP speech codec.*
+- [7] CCITT Recommendation H.100 (1988), *Visual telephone systems.*
+- [8] ITU-T Recommendation H.221 (1997), *Frame structure for a 64 to 1920 kbit/s channel in audiovisual teleservices.*
+- [9] ITU-T Recommendation H.222.0 (1995) | ISO/IEC 13818-1:1996, *Information technology – Generic coding of moving pictures and associated audio information: Systems.*
+- [10] ITU-T Recommendation H.222.1 (1996), *Multimedia multiplex and synchronization for audiovisual communication in ATM environments.*
+- [11] ITU-T Recommendation H.224 (1994), *A real time control protocol for simplex applications using the H.221 LSD/HSD/MLP channels.*
+- [12] ITU-T Recommendation H.230 (1997), *Frame-synchronous control and indication signals for audiovisual systems.*
+- [13] ITU-T Recommendation H.233 (1995), *Confidentiality system for audiovisual services.*
+- [14] ITU-T Recommendation H.234 (1994), *Encryption key management and authentication system for audiovisual services.*
+- [15] ITU-T Recommendation H.242 (1997), *System for establishing communication between audiovisual terminals using digital channels up to 2 Mbit/s.*
+- [16] ITU-T Recommendation H.245 (1998), *Control protocol for multimedia communication.*
+- [17] ITU-T Recommendation H.261 (1993), *Video codec for audiovisual services at  $p \times 64$  kbit/s.*
+- [18] ITU-T Recommendation H.262 (1995) | ISO/IEC 13818-2:1995, *Information technology – Generic coding of moving pictures and associated audio information: Video.*
+- [19] ITU-T Recommendation H.263 (1998), *Video coding for low bit rate communication.*
+- [20] ITU-T Recommendation H.281 (1994), *A far end camera control protocol for videoconferences using H.224.*
+
+- [21] ITU-T Recommendation H.320 (1997), *Narrow-band visual telephone systems and terminal equipment.*
+- [22] ITU-T Recommendation H.321 (1998), *Adaptation of H.320 visual telephone terminals to B-ISDN environments.*
+- [23] ITU-T Recommendation I.311 (1996), *B-ISDN general network aspects.*
+- [24] ITU-T Recommendation I.361 (1995), *B-ISDN ATM layer specification.*
+- [25] ITU-T Recommendation I.363.1 (1996), *B-ISDN ATM adaptation layer specification: Type 1 AAL.*
+- [26] ITU-T Recommendation I.363.5 (1996), *B-ISDN ATM adaptation layer specification: Type 5 AAL.*
+- [27] CCITT Recommendation Q.922 (1992), *ISDN data link layer specification for frame mode bearer services.*
+- [28] ITU-T Recommendation Q.2010 (1995), *Broadband integrated services digital network overview – Signalling capability set 1, release 1.*
+- [29] ITU-T Recommendation Q.2110 (1994), *B-ISDN ATM adaptation layer – Service Specific Connection Oriented Protocol (SSCOP).*
+- [30] ITU-T Recommendation Q.2130 (1994), *B-ISDN signalling ATM adaptation layer – Service specific coordination function for support of signalling at the user-network interface (SSCF at UNI).*
+- [31] ITU-T Recommendation Q.2931 (1995), *Digital subscriber Signalling System No. 2 – User-Network Interface (UNI) layer 3 specification for basic call/connection control.*
+- [32] ITU-T Recommendation Q.2941.1 (1997), *Digital subscriber Signalling System No. 2: Generic identifiers transport.*
+- [33] ITU-T Recommendation Q.2961.1 (1995), *Digital subscriber Signalling System No. 2 (DSS 2) – Additional traffic parameters: Additional signalling capabilities to support traffic parameters for the tagging option and the sustainable cell rate parameter set.*
+- [34] ITU-T Recommendation 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.*
+- [35] ITU-T Recommendation Q.2971 (1995), *Digital subscriber Signalling System No. 2 – User-network interface layer 3 specification for point-to-multipoint call/connection control.*
+- [36] ITU-T Recommendation T.84 (1996) | ISO/IEC 10918-3:1996, *Information technology – Digital compression and coding of continuous-tone still images: Extensions.*
+- [37] ITU-T Recommendation T.120 (1996), *Data protocols for multimedia conferencing.*
+- [38] ITU-T Recommendation T.123 (1996), *Network specific data protocol stacks for multimedia conferencing.*
+- [39] ITU-T Recommendation T.434 (1996), *Binary file transfer format for the telematic services.*
+- [40] ITU-T Recommendation X.214 (1995) | ISO/IEC 8072:1996, *Information technology – Open Systems Interconnection – Transport service definition.*
+- [41] ITU-T Recommendation X.224 (1995) | ISO/IEC 8073:1997, *Information technology – Open Systems Interconnection – Protocol for providing the connection-mode transport service.*
+
+- [42] ITU-T Recommendation X.680 (1997) | ISO/IEC 8824-1:1998, *Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation.*
+- [43] ITU-T Recommendation X.691 (1997) | ISO/IEC 8825-2:1998, *Information technology – ASN.1 encoding rules – Specification of Packed Encoding Rules (PER).*
+- [44] 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 3: Audio.*
+- [45] ISO/IEC 13818-3:1995, *Information technology – Generic coding of moving pictures and associated audio information – Part 3: Audio.*
+- [46] ISO/IEC 13818-6:1998, *Information technology – Generic coding of moving pictures and associated audio information – Part 6: Extensions for DSM-CC.*
+
+## 3 Definitions
+
+This Recommendation defines the following terms.
+
+- 3.1 **audiovisual information:** Information including audio and/or video information.
+- 3.2 **bidirectional logical channel:** A bidirectional logical channel consists of a pair of associated transmission paths between two terminals, one in each direction of transmission.
+- 3.3 **bidirectional terminal:** A terminal which can send and receive audiovisual information.
+- 3.4 **capability:** A terminal has a particular capability if it is able to encode and transmit or receive and decode that particular signal.
+- 3.5 **channel:** A channel is a unidirectional link between two end points.
+- 3.6 **command:** A command is a message that requires action but no explicit response.
+- 3.7 **control and indication:** End-to-end signalling between terminals, consisting of control, which requires action but no explicit response in the receiver, and indication which contains information but does not require action or response in the receiver.
+- 3.8 **customer premises network:** An ATM network administered by the user.
+- 3.9 **elementary stream:** Elementary stream is a generic term for a coded video, coded audio or other coded bit stream.
+- 3.10 **entry:** The word entry is used to refer to elements in sets or tables, such as capability sets.
+- 3.11 **gateway:** A function that converts transmission formats and/or protocols between different network environments.
+- 3.12 **in-band:** In-band messages are those that are transported within the channel or logical channel to which they refer.
+- 3.13 **indication:** An indication is a message that contains information but does not require action or response.
+- 3.14 **logical channel:** A logical channel is a unidirectional path or bidirectional path for the transmission of information.
+- 3.15 **logical channel number:** A logical channel number is a number that identifies a single logical channel.
+- 3.16 **logical channel signalling:** Logical channel signalling is a set of procedures that are used to open and close logical channels.
+
+- 3.17 master terminal:** A master terminal is the terminal that is determined as being the master terminal by the master-slave determination procedure used by this Recommendation.
+- 3.18 medium type:** A medium type is a single form of information that is presented to a user or the data representing that information: video, audio and text are example medium types.
+- 3.19 mode:** A mode is a set of elementary streams that a terminal is transmitting, intends to transmit, or would like to receive.
+- 3.20 multimedia communication:** Multimedia communication refers to the transmission and/or reception of signals of two or more medium types simultaneously.
+- 3.21 multipoint:** Multipoint refers to the simultaneous interconnection of three or more terminals to allow communication among several sites through the use of multipoint control units (bridges) that centrally direct the flow of information.
+- 3.22 non-standard:** Not conforming to a national or international standard referenced in this Recommendation.
+- 3.23 out-of-band:** Out-of-band messages are those that are not transported within the user-to-user information channel.
+- 3.24 public network:** An ATM network administered by the network provider for public access.
+- 3.25 request:** A request is a message that results in action by the remote terminal and requires an immediate response from it.
+- 3.26 response:** A response is a message that is the response to a request.
+- 3.27 session:** A session is a period of communication between two terminals which may be conversational or non-conversational (for example retrieval from a database).
+- 3.28 slave terminal:** A slave terminal is the terminal that is determined as being the slave terminal by the master-slave determination procedure used by this Recommendation.
+- 3.29 subchannel:** A channel in Recommendation H.222.1 formed from packets having a unique multiplex identifier field value. A subchannel carries one H.222.1 elementary stream. A subchannel is unidirectional. There may be many subchannels within one ATM virtual channel.
+- 3.30 support:** The ability to operate in a given mode; however, a requirement to support a mode does not mean that the mode shall actually be used at all times: unless prohibited, other modes may be used by mutual negotiation.
+- 3.31 terminal:** A terminal is any endpoint and may be a user's terminal or some other communication system such as an MCU or an information server.
+- 3.32 unidirectional logical channel:** A unidirectional logical channel is a path for the transmission of a single elementary stream from one terminal to another.
+- 3.33 unidirectional terminal:** A terminal which can only send or receive audiovisual information.
+
+## 4 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+|       |                              |
+|-------|------------------------------|
+| AAL   | ATM Adaptation Layer         |
+| ASN.1 | Abstract Syntax Notation One |
+| ATM   | Asynchronous Transfer Mode   |
+| B-BC  | Broadband Bearer Capability  |
+
+|          |                                                                                           |
+|----------|-------------------------------------------------------------------------------------------|
+| B-HLI    | Broadband High-Layer Information                                                          |
+| B-ISDN   | Broadband ISDN                                                                            |
+| B-LCSE   | Bidirectional Logical Channel Signalling Entity                                           |
+| C&I      | Control and Indication                                                                    |
+| CBR      | Constant Bit Rate                                                                         |
+| CESE     | Capability Exchange Signalling Entity                                                     |
+| CIF      | Common Intermediate Format (of a video picture: refer to Recommendations H.261 and H.263) |
+| CLCSE    | Close Logical Channel Signalling Entity                                                   |
+| CPCS     | Common Part Convergence Sublayer (of ATM Adaptation Layer 5)                              |
+| CPCS-UU  | CPCS User-to-User                                                                         |
+| CPI      | Common Part Indicator                                                                     |
+| CRC      | Cyclic Redundancy Check                                                                   |
+| CS       | Convergence Sublayer                                                                      |
+| DSM-CC   | Digital Storage Media – Command and Control                                               |
+| DSS 2    | Digital Subscriber Signalling System No. 2                                                |
+| FEC      | Forward Error Correction                                                                  |
+| FR-SSCS  | Frame Relay Service Specific Convergence Sublayer                                         |
+| GOB      | Group Of Blocks (of a video picture: refer to Recommendations H.261 and H.263)            |
+| IE       | Information Element                                                                       |
+| ISDN     | Integrated Services Digital Network                                                       |
+| LCSE     | Logical Channel Signalling Entity                                                         |
+| MCU      | Multipoint Control Unit                                                                   |
+| MLSE     | Maintenance Loop Signalling Entity                                                        |
+| MSDSE    | Master Slave Determination Signalling Entity                                              |
+| MRSE     | Mode Request Signalling Entity                                                            |
+| NAC      | Network Adaptation Capabilities                                                           |
+| N-BC     | Narrow-band Bearer Capability                                                             |
+| N-ISDN   | Narrow-band ISDN                                                                          |
+| PDU      | Protocol Data Unit                                                                        |
+| PES      | Packetized Elementary Stream                                                              |
+| PID      | Packet Identifier (refer to ITU-T Rec. H.222.0   ISO/IEC 13818-1)                         |
+| PS       | Program Stream                                                                            |
+| PTS      | Presentation Time Stamp                                                                   |
+| QCIF     | Quarter CIF                                                                               |
+| QoS      | Quality of Service                                                                        |
+| RAST     | Receive-and-Send Terminal                                                                 |
+| RAST-1   | Receive-and-Send Terminal with an AAL 1 interface                                         |
+| RAST-1&5 | Receive-and-Send Terminal with AAL 1 and AAL 5 interfaces                                 |
+| RAST-5   | Receive-and-Send Terminal with an AAL 5 interface                                         |
+| ROT      | Receive-Only Terminal                                                                     |
+| ROT-1    | Receive-Only Terminal with an AAL 1 interface                                             |
+
+|         |                                                       |
+|---------|-------------------------------------------------------|
+| ROT-1&5 | Receive-Only Terminal with AAL 1 and AAL 5 interfaces |
+| ROT-5   | Receive-Only Terminal with an AAL 5 interface         |
+| RTDSE   | Round Trip Delay Signalling Entity                    |
+| SAP     | Service Access Point                                  |
+| SAR     | Segmentation And Reassembly                           |
+| SDT     | Structured Data Transfer                              |
+| SDU     | Service Data Unit                                     |
+| SOT     | Send-Only Terminal                                    |
+| SOT-1   | Send-Only Terminal with an AAL 1 interface            |
+| SOT-1&5 | Send-Only Terminal with AAL 1 and AAL 5 interfaces    |
+| SOT-5   | Send-Only Terminal with an AAL 5 interface            |
+| SQCIF   | Sub QCIF                                              |
+| SRTS    | Synchronous Residual Time Stamp                       |
+| SSCOP   | Service Specific Connection-Oriented Protocol         |
+| SSCS    | Service Specific Convergence Sublayer                 |
+| TS      | Transport Stream                                      |
+| UNI     | User Network Interface                                |
+| VBR     | Variable Bit Rate                                     |
+| VC      | ATM Virtual Channel                                   |
+| VFS     | Video Frame Synchronous                               |
+| VOD     | Video On Demand                                       |
+
+## 5 Conventions
+
+The word "shall" is used in this Recommendation to specify a mandatory requirement.
+
+The word "should" is used in this Recommendation to specify a suggested, but not required, course of action.
+
+The word "may" is used in this Recommendation to specify an optional course of action, without expressing a preference.
+
+The term "11172 audio" is used in this Recommendation to represent ISO/IEC 11172-3.
+
+The term "13818 audio" is used in this Recommendation to represent ISO/IEC 13818-3.
+
+# 6 System description
+
+## 6.1 System configuration
+
+The interaction among the H.310 terminal capabilities is based on the protocol reference model shown in Figure 2, which illustrates the protocol stacks for the audiovisual, data, call management (DSS 2 and H.245), and other control and indication signals that can be supported by the different terminal types of this Recommendation.
+
+![Figure 2/H.310 – H.310 protocol reference model diagram showing various protocol stacks for Call Management, Audio, Video, Private Data, Synchronous Signalling, and T.120 over an ATM (I.361) base. The diagram includes multiple protocol layers such as H.245, X.224 Class 0, LAPF (Q.922), FR-SSCS (I.365.1), CPCS 5 (I.363.5), and SAR 5 (I.363.5). It also features seven numbered notes explaining specific protocol details and configurations.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg)
+
+The diagram illustrates the H.310 protocol reference model. At the top, several functional blocks are shown: Call Management, Audio (G.711, G.722, G.728, 11172, 13818), Video (H.261, H.262), Private Data, Synchronous Signalling (Note 2), and T.120 (Note 1). Below these, various protocol stacks are depicted. On the left, Call Management connects to H.245 and H.242/H.230. H.245 connects to X.224 Class 0, which connects to LAPF (Q.922). LAPF connects to FR-SSCS (I.365.1), which connects to CPCS 5 (I.363.5), which connects to SAR 5 (I.363.5). Call Control DSS 2 (Note 7) connects to SSCS.UNI (Q.2130), which connects to SSCOP (Q.2110), which connects to CPCS 5 (I.363.5), which connects to SAR 5 (I.363.5). In the center, Audio and Video connect to H.221 (Note 6). H.221 connects to a large box containing Note 4 (CS 1 (I.363.1) and SAR 1 (I.363.1)) and Note 5 (CPCS 5 (I.363.5) and SAR 5 (I.363.5)). Private Data connects to H.222.1, which contains H.222.0 and Network adaptation. Synchronous Signalling (Note 2) connects to H.222.1. T.120 (Note 1) connects to X.224 Classe 0, which connects to LAPF (Q.922), which connects to FR-SSCS (I.365.1), which connects to CPCS 5 (I.363.5), which connects to SAR 5 (I.363.5). All stacks converge to a common base: ATM (I.361).
+
+Figure 2/H.310 – H.310 protocol reference model diagram showing various protocol stacks for Call Management, Audio, Video, Private Data, Synchronous Signalling, and T.120 over an ATM (I.361) base. The diagram includes multiple protocol layers such as H.245, X.224 Class 0, LAPF (Q.922), FR-SSCS (I.365.1), CPCS 5 (I.363.5), and SAR 5 (I.363.5). It also features seven numbered notes explaining specific protocol details and configurations.
+
+T1604890-98
+
+NOTE 1 – T.120 may be carried within the H.222.1 multiplex or in a separate ATM virtual channel, as specified in Recommendation T.123.
+
+NOTE 2 – Video frame synchronous signals are described in 6.3.5.3.
+
+NOTE 3 – H.222.1/H.222.0 functions include multiplexing, timebase recovery, media synchronization, jitter removal, buffer management, security and access control, in-band signalling, and trick modes. Recommendation H.222.1 specifies elements and procedures from the generic H.222.0, for their use in ATM environments, and also specifies code points and procedures for ITU-T defined elementary streams.
+
+NOTE 4 – AAL type 1 CS functions include transmission clock recovery, jitter removal, bit error correction, cell loss correction, and data structure preservation.
+
+NOTE 5 – AAL type 5 (CPCS) functions include bit error detection, cell loss detection, and data structure preservation.
+
+NOTE 6 – H.221 is required in the H.310 RAST-1, RAST-5 and RAST-1&5 terminals for interworking with H.320/H.321 terminals.
+
+NOTE 7 – B-ISDN signalling is referred to as Digital Subscriber Signalling System No. 2 (DSS 2). DSS 2 is composed of the suite of protocols shown in Table 1. The protocol stack for the Q.2931 signalling messages is specified in Recommendation Q.2010.
+
+**Figure 2/H.310 – H.310 protocol reference model**
+
+**Table 1/H.310 – Summary of DSS 2 protocols**
+
+| Recommendation | Title                                                                                                |
+|----------------|------------------------------------------------------------------------------------------------------|
+| Q.2931         | User network interface layer 3 specification for basic call/connection control                       |
+| Q.2941.1       | DSS 2 user generated identifiers                                                                     |
+| Q.2961         | Support of additional traffic parameters                                                             |
+| Q.2961.2       | ATM transfer capability coding in the broadband bearer capability information element                |
+| Q.2962         | Negotiation of traffic and QoS parameters (during call/connection establishment)                     |
+| Q.2963         | Renegotiation/modification of traffic and QoS parameters (for already established calls/connections) |
+| Q.2964         | B-ISDN look-ahead                                                                                    |
+| Q.2971         | Point-multipoint call/connection control                                                             |
+| Q.298x         | Multiconnection calls                                                                                |
+
+## **6.2 Terminal types**
+
+This Recommendation defines both unidirectional and bidirectional broadband audiovisual terminals. The classification of H.310 terminals into different terminal types is based on audiovisual and AAL capabilities as summarized in Table 2.
+
+**Table 2/H.310 – Definition of H.310 terminal types**
+
+|                       |                |      | AAL    |        |          |
+|-----------------------|----------------|------|--------|--------|----------|
+|                       |                |      | AAL 1  | AAL 5  | AAL 1& 5 |
+| Audiovisual transport | Unidirectional | ROT  | ROT-1  | ROT-5  | ROT-1&5  |
+|                       |                | SOT  | SOT-1  | SOT-5  | SOT-1&5  |
+|                       | Bidirectional  | RAST | RAST-1 | RAST-5 | RAST-1&5 |
+
+### **6.2.1 Unidirectional terminal types (ROT and SOT)**
+
+Two classes of unidirectional terminals are defined: Send-Only Terminal (SOT) and Receive-Only Terminal (ROT).
+
+Three types of H.310 unidirectional terminals are defined, based on their supported AALs, for each of the two classes. The H.310 defined unidirectional terminal types are:
+
+- H.310 ROT-1 and SOT-1 which support AAL 1;
+- H.310 ROT-5 and SOT-5 which support AAL 5;
+- H.310 ROT-1&5 and SOT-1&5 is a composite terminal supporting both AAL 1 and AAL 5.
+
+Each of these terminal types shall support the H.310 native communication mode. The native communication mode consists of H.222.1, with ISO/IEC 11172-3 Layer 2, H.262 and H.245 as the audio, video and control protocols.
+
+Each of these terminals may be connected to public B-ISDN and customer premise networks (private networks).
+
+NOTE – Some pairs of unidirectional terminal will not interwork with each other. This may be due to incompatible class, such as ROT-1 connecting with ROT-1&5, or due to incompatible type, such as ROT-1 connecting to SOT-5.
+
+### 6.2.2 Bidirectional terminal types (RAST)
+
+Three types of H.310 bidirectional receive and send terminals (RAST) are defined based on their communication modes and supported AALs. The H.310 defined terminal types are:
+
+- H.310 RAST-1 which supports AAL 1;
+- H.310 RAST-5 which supports AAL 5;
+- H.310 RAST-1&5 is a composite terminal supporting both AAL 1 and AAL 5.
+
+Each of these terminal types shall support an H.310 native communication mode as well as an H.320/H.321 interoperation mode. Figure 3 depicts the protocol stacks for these two modes for each of the terminal types.
+
+![Figure 3/H.310 – Protocol stacks for native H.310 and H.320/H.321 interoperation communication modes. The diagram shows three protocol stacks for RAST-1, RAST-5, and RAST-1&5. Each stack is a 3x3 grid of protocol layers. The top row contains H.245, H.262/G.711, and H.242/H.261/G.711. The middle row contains X.224 LAPF FR-SSCS, H.222.0/H.222.1, and H.221. The bottom row contains AAL 5, AAL 1, and AAL 1. The left column represents Native H.310 Communication Mode, and the right column represents H.320/H.321 Interoperation Mode. For RAST-1, the layers are H.245, H.262/G.711, H.242/H.261/G.711 in the top row; X.224 LAPF FR-SSCS, H.222.0/H.222.1, H.221 in the middle row; and AAL 5, AAL 1, AAL 1 in the bottom row. For RAST-5, the layers are H.245, H.262/G.711, H.242/H.261/G.711 in the top row; X.224 LAPF FR-SSCS, H.222.0/H.222.1, H.221/NAL<sup>a)</sup> in the middle row; and AAL 5, AAL 5, AAL 5 in the bottom row. For RAST-1&5, the layers are H.245, H.262/G.711, H.262/G.711 in the top row; X.224 LAPF FR-SSCS, H.222.0/H.222.1, H.222.0/H.222.1 in the middle row; and AAL 5, AAL 1, AAL 5 in the bottom row. The H.320/H.321 Interoperation Mode for RAST-1&5 includes H.242/H.261/G.711, H.221, and AAL 1 in the top, middle, and bottom rows respectively.](898fb89a50d9ec1dfb4e425c816976a7_img.jpg)
+
+Figure 3/H.310 – Protocol stacks for native H.310 and H.320/H.321 interoperation communication modes. The diagram shows three protocol stacks for RAST-1, RAST-5, and RAST-1&5. Each stack is a 3x3 grid of protocol layers. The top row contains H.245, H.262/G.711, and H.242/H.261/G.711. The middle row contains X.224 LAPF FR-SSCS, H.222.0/H.222.1, and H.221. The bottom row contains AAL 5, AAL 1, and AAL 1. The left column represents Native H.310 Communication Mode, and the right column represents H.320/H.321 Interoperation Mode. For RAST-1, the layers are H.245, H.262/G.711, H.242/H.261/G.711 in the top row; X.224 LAPF FR-SSCS, H.222.0/H.222.1, H.221 in the middle row; and AAL 5, AAL 1, AAL 1 in the bottom row. For RAST-5, the layers are H.245, H.262/G.711, H.242/H.261/G.711 in the top row; X.224 LAPF FR-SSCS, H.222.0/H.222.1, H.221/NAL<sup>a)</sup> in the middle row; and AAL 5, AAL 5, AAL 5 in the bottom row. For RAST-1&5, the layers are H.245, H.262/G.711, H.262/G.711 in the top row; X.224 LAPF FR-SSCS, H.222.0/H.222.1, H.222.0/H.222.1 in the middle row; and AAL 5, AAL 1, AAL 5 in the bottom row. The H.320/H.321 Interoperation Mode for RAST-1&5 includes H.242/H.261/G.711, H.221, and AAL 1 in the top, middle, and bottom rows respectively.
+
+T1604900-98
+
+<sup>a)</sup> NAL Network Adaptation Layer (see Annex B/H.321).
+
+**Figure 3/H.310 – Protocol stacks for native H.310 and H.320/H.321 interoperation communication modes**
+
+NOTE – Figure 3 corresponds to the "separate VC" case in Annex A.
+
+The H.310 RAST-1 terminal supports AAL 1. Its native H.310 communication mode consists of H.222.1, with G.711, H.262, and H.245 as the audio, video, and control protocols. Its H.320/H.321 interoperation mode supports the full H.321/Annex A protocol stack.
+
+The H.310 RAST-5 terminal supports AAL 5. Its native H.310 communication mode consists of H.222.1 with G.711, H.262, and H.245 as the audio, video and control protocols. Its H.320/H.321 interoperation mode supports the full H.321/Annex B protocol stack.
+
+The H.310 RAST-1&5 is a composite of the RAST-1 and RAST-5 terminal types and supports all four modes described above.
+
+The RAST-1 and RAST-1&5 terminals connect to public B-ISDN and customer premise networks (private networks) and can interwork with H.320 via an I.580 interworking unit and directly with H.321/Annex A terminals. The RAST-5 terminal connects to customer premise networks (private networks), can directly interwork with H.321/Annex B terminals and requires a gateway to interwork with H.320, H.321/Annex A and H.310 RAST-1 terminals. See clause 12 for interworking scenarios.
+
+## 6.3 Terminal capabilities
+
+The definition and classification of H.310 terminal types and their communication modes are based on the following capabilities:
+
+- Audiovisual and Data;
+- Network Adaptation;
+- signalling (both user-to-user and user-to-network).
+
+A *communication mode* is defined as a combination of certain parameters of the above capabilities. Based on the different capabilities of H.310 terminals, two classes of communication modes are specified:
+
+- H.320/H.321 interoperation modes;
+- native H.310 communication modes.
+
+Unidirectional H.310 terminals need only support native H.310 communication modes of operation, that is, unidirectional terminals may optionally support the H.320/H.321 interoperation modes.
+
+At the start of the call, H.310 terminals shall identify the remote terminal type (H.320/H.321, H.310 bidirectional, etc.) via exchange of Q.2931 information elements, and shall use either H.245 or H.242 to perform capability exchange and other procedures.
+
+This Recommendation mandates the support of particular functionalities by the different terminal types. However, this does not imply that a particular communication mode shall be used by that terminal type during a given communication session. For example, RAST terminals shall support H.261 video capabilities for interworking with H.320/H.321 terminals, but the use of H.261 in the native mode, that is, when H.222.1 is used, is optional.
+
+The following subclauses describe mandatory and optional capabilities. Optional capabilities are included as guidelines for implementations and are in no way intended to be exhaustive lists of what may be implemented.
+
+### 6.3.1 Video capabilities
+
+All H.310 terminals shall support Recommendation H.262 at the Main Profile at Main Level (MP@ML) conformance point. Other H.262 profiles and levels may be optionally supported.
+
+H.310 terminals shall adhere to the hierarchical relationship, as defined in clause 8/H.262, among the different H.262 profiles and levels. Therefore, it should be noted that H.262 Simple Profile at Main Level (SP@ML) and Main Profile at Low Level (MP@LL) shall be supported by all H.310 terminals.
+
+When compliance with a H.262 conformance point, that is a given profile at a given level, is supported, H.310 terminals shall adhere to the video parameter constraints specified in clause 8/H.262 for that conformance point. However, terminals may indicate a capability for the functionality of a given profile with reduced level parameters using H.245, and such a communication mode may be established using the relevant procedures of H.245 when both terminals have the necessary capability.
+
+The mandatory and optional video and audio capabilities are summarized in Table 3.
+
+**Table 3/H.310 – Audiovisual capabilities of H.310 terminals**
+
+| Terminal type                                          |  | Audiovisual capabilities |                                                                                                                                                                                                                                             |                 |                                                                                                                                                                                        |
+|--------------------------------------------------------|--|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                                        |  | Video                    |                                                                                                                                                                                                                                             | Audio           |                                                                                                                                                                                        |
+|                                                        |  | Mandatory                | Optional                                                                                                                                                                                                                                    | Mandatory       | Optional                                                                                                                                                                               |
+| ROT-1<br>SOT-1<br>ROT-5<br>SOT-5<br>ROT-1&5<br>SOT-1&5 |  | H.262 MP@ML              | H.262 MP@H14L<br>H.262 MP@HL<br>H.262 SNR@LL<br>H.262 SNR@ML<br>H.262 Spatial@H14L<br>H.262 HP@ML<br>H.262 HP@H14L<br>H.262 HP@HL                                                                                                           | 11172-3 Layer 2 | 11172-3 Layer 3                                                                                                                                                                        |
+| RAST-1<br>RAST-5<br>RAST-1&5                           |  | H.262 MP@ML              | H.261 QCIF<br>H.261 CIF<br><br>H.262 MP@H14L<br>H.262 MP@HL<br>H.262 SNR@LL<br>H.262 SNR@ML<br>H.262 Spatial@H14L<br>H.262 HP@ML<br>H.262 HP@H14L<br>H.262 HP@HL<br><br>H.263 SQCIF<br>H.263 QCIF<br>H.263 CIF<br>H.263 4CIF<br>H.263 16CIF | G.711           | 11172-3 Layer 1<br>11172-3 Layer 2<br>11172-3 Layer 3<br><br>13818-3 Layer 1<br>13818-3 Layer 2<br>13818-3 Layer 3<br><br>G.711<br>G.722<br>G.728<br>G.723.1<br>G.729<br>Annex A/G.729 |
+| RAST-1<br>RAST-5<br>RAST-1&5                           |  | Native mode              |                                                                                                                                                                                                                                             |                 | 11172-3 Layer 1<br>11172-3 Layer 2<br>11172-3 Layer 3<br><br>13818-3 Layer 1<br>13818-3 Layer 2<br>13818-3 Layer 3<br><br>G.722<br>G.728<br>G.723.1<br>G.729<br>Annex A/G.729          |
+
+**Table 3/H.310 – Audiovisual capabilities of H.310 terminals (concluded)**
+
+| Terminal type                |                 | Audiovisual capabilities |                                                                                                                                                                                                                             |           |                                                                                                                                                                               |
+|------------------------------|-----------------|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                              |                 | Video                    |                                                                                                                                                                                                                             | Audio     |                                                                                                                                                                               |
+|                              |                 | Mandatory                | Optional                                                                                                                                                                                                                    | Mandatory | Optional                                                                                                                                                                      |
+| RAST-1<br>RAST-5<br>RAST-1&5 | H.320/1<br>mode | H.261 QCIF<br>H.261 CIF  | H.262 MP@ML<br>H.262 MP@H14L<br>H.262 MP@HL<br>H.262 SNR@LL<br>H.262 SNR@ML<br>H.262 Spatial@H14L<br>H.262 HP@ML<br>H.262 HP@H14L<br>H.262 HP@HL<br><br>H.263 SQCIF<br>H.263 QCIF<br>H.263 CIF<br>H.263 4CIF<br>H.263 16CIF | G.711     | 11172-3 Layer 1<br>11172-3 Layer 2<br>11172-3 Layer 3<br><br>13818-3 Layer 1<br>13818-3 Layer 2<br>13818-3 Layer 3<br><br>G.722<br>G.728<br>G.723.1<br>G.729<br>Annex A/G.729 |
+
+#### 6.3.1.1 Unidirectional video capabilities
+
+Unidirectional H.310 terminals are not required to support any of the H.261 or H.263 video coding modes.
+
+#### 6.3.1.2 Bidirectional video capabilities
+
+All H.310 bidirectional terminals shall support Recommendation H.261 with both the Common Intermediate Format (CIF) and Quarter CIF (QCIF) picture resolutions. This enables the interworking between H.310 and a wide range of existing and future H.320/H.321 terminals.
+
+Bidirectional terminals have the option of supporting Recommendation H.263 with any of the picture formats and any of the optional modes.
+
+### 6.3.2 Audio capabilities
+
+The mandatory and optional video and audio capabilities are summarized in Table 3.
+
+#### 6.3.2.1 Unidirectional audio capabilities
+
+Unidirectional H.310 terminals shall support ISO/IEC 11172-3 audio Layer 2.
+
+The support of ISO/IEC 11172-3 Layer 3, ISO/IEC 13818-3, and ITU-T G-series audio Recommendations is optional.
+
+#### 6.3.2.2 Bidirectional audio capabilities
+
+All bidirectional H.310 terminals shall support Recommendation G.711 (both A-law and  $\mu$ -law). This enables existing and future H.320/H.321 terminals to interwork with H.310 terminals.
+
+Bidirectional terminals may optionally support one or more of the following audio Recommendations: G.722 at 64 kbit/s, G.722 at 56 kbit/s, G.722 at 48 kbit/s, G.723.1 at either 5.3 or 6.3 kbit/s, G.728 (16 kbit/s), G.729 (8 kbit/s), and Annex A/G.729 (8 kbit/s).
+
+The support of ISO/IEC 11172-3 and ISO/IEC 13818-3 audio standards is optional.
+
+### 6.3.3 Data capabilities
+
+The support of data protocols is optional in H.310 terminals. Data protocols may be multiplexed with other audiovisual information by using either the H.222.1 or ATM layer multiplexing functions.
+
+T.120 is the default basis of data interoperability between an H.310 terminal and other H.310, H.320, H.321, H.322, H.323 or H.324 terminals. When any optional data application is implemented using one or more of the ITU-T Recommendations which can be negotiated via H.245, the equivalent T.120 applications shall be one of those provided (if such applications have been recommended by the ITU-T). A terminal that provides far-end camera control using H.281 and H.224 is not required to also support a T.120 far-end camera control protocol. Another exception is transparent user data.
+
+### 6.3.4 Network Adaptation Capabilities (NAC)
+
+The network adaptation capabilities of H.310 terminals include the multimedia multiplex and synchronization mechanism, ATM adaptation layer, transfer rate, and ATM VC capabilities.
+
+The mandatory and optional network adaptation capabilities are summarized in Table 4.
+
+**Table 4/H.310 – Network adaptation capabilities of H.310 terminals**
+
+| Terminal type      |                 | Network adaptation capabilities |            |                          |          |                    |          |                        |                                                       |
+|--------------------|-----------------|---------------------------------|------------|--------------------------|----------|--------------------|----------|------------------------|-------------------------------------------------------|
+|                    |                 | Multimedia multiplex            |            | AAL for audiovisual data |          | Number of ATM VC's |          | Transfer rate (kbit/s) |                                                       |
+|                    |                 | Mandatory                       | Optional   | Mandatory                | Optional | Mandatory          | Optional | Mandatory              | Optional                                              |
+| ROT-1<br>SOT-1     |                 | H.222.1<br>TS                   | H.222.1 PS | AAL 1                    | AAL 5    | 2                  | > 2      | 6144<br>9216           | n*64                                                  |
+| ROT-5<br>SOT-5     |                 | H.222.1<br>TS                   | H.222.1 PS | AAL 5                    | AAL 1    | 2                  | > 2      | 6144<br>9216           | n*64                                                  |
+| ROT-1&5<br>SOT-1&5 |                 | H.222.1<br>TS                   | H.222.1 PS | AAL 1<br>AAL 5           | –        | 2                  | > 2      | 6144<br>9216           | n*64                                                  |
+| RAST-1             | Native mode     | H.222.1<br>TS                   | H.222.1 PS | AAL 1                    | AAL 5    | 2                  | > 2      | 6144<br>9216           | n*64                                                  |
+|                    | H.320/1<br>mode | H.221                           | –          | AAL 1                    | –        | 2                  | > 2      | B<br>2B<br>H0          | n × B<br>n × H0<br>H <sub>11</sub><br>H <sub>12</sub> |
+| RAST-5             | Native mode     | H.222.1<br>TS                   | H.222.1 PS | AAL 5                    | AAL 1    | 2                  | > 2      | 6144<br>9216           | n*64                                                  |
+|                    | H.320/1<br>mode | H.221                           | –          | AAL 5                    | –        | 2                  | > 2      | B<br>2B<br>H0          | n × B<br>n × H0<br>H <sub>11</sub><br>H <sub>12</sub> |
+| RAST-1&5           | Native mode     | H.222.1<br>TS                   | H.222.1 PS | AAL 1<br>AAL 5           | –        | 2                  | > 2      | 6144<br>9216           | n*64                                                  |
+|                    | H.320/1<br>mode | H.221                           | –          | AAL 1<br>AAL 5           | –        | 2                  | > 2      | B<br>2B<br>H0          | n × B<br>n × H0<br>H <sub>11</sub><br>H <sub>12</sub> |
+
+#### **6.3.4.1 Multimedia multiplex and synchronization**
+
+Multiplexing of audio, video, data, and control signals in H.310 terminals is accomplished using the multimedia multiplex protocols and procedures defined in Recommendations H.221 and H.222.1. Recommendation H.222.1 specifies both H.222.0 and H.222.1 specific functions (e.g. error protection, jitter removal, ITU-T defined stream\_id and descriptors, etc.).
+
+H.310 terminals may support multiple instances of H.222.0/H.222.1. In this case ATM layer multiplexing is also used, since there is one instance of H.222.0/H.222.1 per ATM VC.
+
+All H.310 terminals shall support Recommendations H.222.0/H.222.1 for the multiplexing and synchronization of video, audio, data, and control signals. The support of H.222.1 Transport Stream multiplexing is mandatory for all H.310 terminals. The support of H.222.1 Program Stream multiplexing is optional for H.310 terminals.
+
+All bidirectional H.310 terminals shall support Recommendation H.221 for interworking with H.320 and H.321 terminals.
+
+NOTE – Unidirectional H.310 terminals are not required to support the H.221 multiplexing capability.
+
+#### **6.3.4.2 ATM adaptation layer**
+
+The different types of signals supported by H.310 terminals require different ATM adaptation layer functions. The H.310 AAL capabilities for the multimedia multiplexed, in-band signalling, and out-of-band signalling data signals are specified.
+
+AAL Segmentation And Reassembly (SAR) and Convergence Sublayer (CS) functions are supported by H.310 terminals. Both AAL types 1 and 5 are used for the transfer of the multiplexed constant bit rate signals over ATM networks.
+
+NOTE 1 – The definition of AAL functions and capabilities for the adaptation of variable bit rate audiovisual signals is under study.
+
+Data protocols may either be multiplexed with other audiovisual elementary streams using the H.222.1 multiplex layer or be multiplexed at the ATM layer.
+
+H.245 messages may either be multiplexed with other audiovisual elementary streams using the H.222.1 multiplex layer or be multiplexed at the ATM layer. The protocol stacks for these two means of multiplexing are specified in Annex A, and are referred to as "single VC" and "separate VC" respectively.
+
+H.310 terminals support the Q.2931 protocol stack for performing out-of-band call management and signalling functions. In addition to the Q.2130 (SSCS.UNI) and Q.2110 (SSCOP) layers, the AAL 5 CPCS and SAR sublayers represent an integrated part of the Q.2931 protocol stack.
+
+##### **The use of AAL type 1**
+
+RAST-1 and RAST-1&5 terminals shall support the adaptation of H.221 multiplexed audiovisual data using the AAL 1 SAR and CS functions which are defined in Recommendation I.363.1 and supported in H.321 Annex A terminals. This will enable the interworking between H.310 and H.321/Annex A terminals.
+
+RAST-1 and RAST-1&5 terminals shall support the adaptation of H.222.1 multiplexed bit streams into ATM using AAL type 1. The mode of AAL 1 with no FEC and no interleaving shall be supported, and the mode with (128, 124) Reed-Solomon Forward Error Correction (FEC) code without interleaving may optionally be supported<sup>1</sup>.
+
+ROT-1, ROT-1&5, SOT-1, and SOT-1&5 terminals shall support the adaptation of H.222.1 multiplexed bit streams into ATM using AAL type 1. The mode of AAL 1 with no FEC and no interleaving shall be supported, and the mode with (128, 124) Reed-Solomon Forward Error Correction (FEC) code with interleaving may optionally be supported<sup>1</sup>.
+
+Neither the Structure Data Transfer (SDT) mode nor the Synchronous Residual Time Stamp (SRTS) of AAL type 1 is supported by H.310 terminals for the transfer of H.222.1 multiplexed data.
+
+NOTE 2 – H.310 terminals that operate in the H.320/H.321 Annex A communication mode shall support the AAL type 1 SDT functions when doing so.
+
+All bidirectional H.310 terminals shall be capable of interworking. For RAST-5 terminals, and RAST-1&5 terminals when working with AAL 5, a gateway in the customer premises network shall be used to provide the AAL 1 adaptation function.
+
+##### **The use of AAL type 5**
+
+RAST-5 and RAST-1&5 terminals shall support the adaptation of H.221 multiplexed audiovisual data into ATM using the AAL 5 SAR and CPCS functions which are defined in Recommendation I.363.5. This will enable the interworking between H.310 and H.321 terminals.
+
+ROT-5, ROT-1&5, SOT-5, SOT-1&5, RAST-5, and RAST-1&5 terminals shall support the adaptation of H.222.1 multiplexed bit streams into ATM using AAL type 5.
+
+The rules and protocols used for the mapping of H.222.1 Program Stream and Transport Stream packets into the AAL 5 Protocol Data Unit (PDU) is specified in Recommendation H.222.1. Only SAR and common part CS (CPCS) functions are supported as defined in Recommendation I.363.5. Therefore, Service Specific Convergence Sublayer (SSCS) functions are neither defined nor supported by H.310 AAL 5 unidirectional terminals.
+
+When detecting an errored cell (using the CRC function of the AAL 5 CPCS sublayer), the AAL 5 PDU may be passed to the user (i.e. H.222.1) according to the corrupted-data delivery option specified in Recommendation I.363.5.
+
+The usage of the AAL 5 CPCS User-To-User (CPCS-UU) indication field is not specified in this Recommendation. Moreover, in H.310 SOT terminals, the Common Part Indicator (CPI) field shall always be set to zero (i.e. only the 64-bit alignment function is used).
+
+#### **6.3.4.3 ATM virtual connections**
+
+All H.310 terminals shall support at least two ATM VCs. In the native H.310 communication mode, there shall be one VC for the transfer of H.245 messages and at least one VC for H.222.1 multiplexed audiovisual and data signals. In the H.320/H.321 interoperation mode, two VCs shall be supported for the transfer of two B-channel signals.
+
+Additional VCs may optionally be used for transfer of audiovisual and/or data signals, such as T.120 data, or for other purposes.
+
+---
+
+<sup>1</sup> These specifications are in alignment with Recommendation J.82 "Transport of MPEG-2 constant bit rate television signals in B-ISDN". Note that Recommendation J.82 specifies the mandatory use of (128, 124) Reed-Solomon Forward Error Correction Code with interleaving.
+
+#### 6.3.4.4 Transfer rate
+
+H.310 terminals are capable of supporting a wide range of possible transfer rates. The transfer rate capabilities of H.310 terminals are defined at the AAL-SAP.
+
+Bidirectional H.310 terminals shall support the B, 2B, and H0 narrow-band ISDN transfer rates of H.320/H.321 terminals. Other H.320/H.321 rates (e.g. H<sub>11</sub> and H<sub>12</sub>) are optional. This will enable the interworking of H.310 terminals with a wide range of H.320/H.321 terminals.
+
+All H.310 terminals shall support constant bit rate transfer rates for native H.310 communication mode. The mandatory transfer rates are P = 6.144 Mbit/s (for MP@ML medium quality services) and Q = 9.216 Mbit/s (for MP@ML high quality services) where P/Q is 2/3. Other optional rates of  $n \times 64$  kbit/s (n is an integer from 1 to 65 535) can be negotiated through H.245 capability messages and related procedures.
+
+NOTE – Until an appropriate network environment is available everywhere, it would be desirable that all terminals support a rate of  $90 \times 64$  kbit/s, compatible with a VC-2 (Virtual Container 2).
+
+The specification of VBR transfer rates is under study.
+
+### 6.3.5 Signalling capabilities
+
+The mandatory and optional signalling capabilities are summarized in Table 5.
+
+**Table 5/H.310 – Signalling capabilities of H.310 terminals**
+
+| Terminal type                                          |              | Signalling capabilities |           |                            |           |
+|--------------------------------------------------------|--------------|-------------------------|-----------|----------------------------|-----------|
+|                                                        |              | User-to-user signalling |           | User-to-network signalling |           |
+|                                                        |              | Mandatory (Rec.)        | Optional  | Mandatory (Rec.)           | Optional  |
+| ROT-1<br>SOT-1<br>ROT-5<br>SOT-5<br>ROT-1&5<br>SOT-1&5 |              | H.245                   | DSM-CC UU | Q.2931                     | DSM-CC UN |
+| RAST-1                                                 | Native mode  | H.245                   | DSM-CC UU | Q.2931                     | DSM-CC UN |
+|                                                        | H.320/1 mode | H.242/H.230             | –         | Q.2931                     | –         |
+| RAST-5                                                 | Native mode  | H.245                   | DSM-CC UU | Q.2931                     | DSM-CC UN |
+|                                                        | H.320/1 mode | H.242/H.230             | –         | Q.2931                     | –         |
+| RAST-1&5                                               | Native mode  | H.245                   | DSM-CC UU | Q.2931                     | DSM-CC UN |
+|                                                        | H.320/1 mode | H.242/H.230             | –         | Q.2931                     | –         |
+
+#### 6.3.5.1 User-to-network signalling
+
+All H.310 terminals shall support Recommendation Q.2931 for user-to-network signalling.
+
+#### 6.3.5.2 User-to-user signalling
+
+All H.310 terminals shall support H.245 messages and procedures for user-to-user signalling. The exact set of H.245 messages and procedures that are mandated in H.310 terminals, and their usage, are specified in 6.4. H.245 signalling is only supported in the native H.310 communication mode.
+
+All bidirectional H.310 terminals shall support Recommendations H.242 and H.230 for interworking with H.320 and H.321 terminals.
+
+#### 6.3.5.3 Video Frame Synchronous (VFS) Control and Indication (C&I) signalling
+
+VFS C&I signalling is accomplished using the syntax given in Table 6. All H.310 terminals shall support this syntax and shall react to all the signals classified as controls in the appropriate way specified below. Terminals are not required to react to any of the signals classified as indications, but may optionally do so. The set of indications which invoke an action is implementation dependent. The reaction, if any, to each indication signal is also implementation dependent.
+
+**Table 6/H.310 – Syntax for H.310 video frame synchronous control and indication signals**
+
+|                                                                |                                                       |
+|----------------------------------------------------------------|-------------------------------------------------------|
+| <b>H310-TERMINAL-MANAGEMENT DEFINITIONS AUTOMATIC TAGS ::=</b> |                                                       |
+| BEGIN                                                          |                                                       |
+| <i>-- Export all symbols</i>                                   |                                                       |
+| <b>VideoFrameSynchronousCandIPDU</b>                           | <b>::= SEQUENCE</b>                                   |
+| {                                                              |                                                       |
+| <b>elementaryStream</b>                                        | <b>CHOICE</b>                                         |
+| {                                                              |                                                       |
+| <b>ts-PID</b>                                                  | <b>INTEGER (1..8191),</b>                             |
+| <b>ps-StreamID</b>                                             | <b>SEQUENCE</b>                                       |
+| {                                                              |                                                       |
+| <b>streamID</b>                                                | <b>INTEGER (0..255),</b>                              |
+| <b>streamIDExtension</b>                                       | <b>INTEGER (0..255) OPTIONAL</b>                      |
+| },                                                             |                                                       |
+| ...                                                            |                                                       |
+| },                                                             |                                                       |
+| <b>resourceID</b>                                              | <b>INTEGER (0..65535) OPTIONAL,</b>                   |
+| <b>videoFrameSynchronousCandI</b>                              | <b>CHOICE</b>                                         |
+| {                                                              |                                                       |
+| <b>videoFrameSynchronousControl</b>                            | <b>VideoFrameSynchronousControl,</b>                  |
+| <b>videoFrameSynchronousIndication</b>                         | <b>VideoFrameSynchronousIndication,</b>               |
+| ...                                                            |                                                       |
+| },                                                             |                                                       |
+| ...                                                            |                                                       |
+| }                                                              |                                                       |
+| <b>VideoFrameSynchronousControl</b>                            | <b>::= CHOICE</b>                                     |
+| {                                                              |                                                       |
+| <b>nonStandard</b>                                             | <b>NonStandardParameter,</b>                          |
+| <b>videoFreezePictureReleaseControl</b>                        | <b>NULL,     -- not used for Recommendation H.261</b> |
+|                                                                | <b>                    or H.263</b>                   |
+| ...                                                            |                                                       |
+| }                                                              |                                                       |
+
+|                                        |                                                                       |
+|----------------------------------------|-----------------------------------------------------------------------|
+| <b>VideoFrameSynchronousIndication</b> | <b>::= CHOICE</b>                                                     |
+| {                                      |                                                                       |
+| <b>nonStandard</b>                     | <b>NonStandardParameter,</b>                                          |
+| <b>closedCaption</b>                   | <b>OCTET STRING,</b>                                                  |
+| <b>splitScreenIndication</b>           | <b>NULL,</b> <i>-- not used for Recommendation H.261<br/>or H.263</i> |
+| <b>documentCameraIndication</b>        | <b>NULL,</b> <i>-- not used for Recommendation H.261<br/>or H.263</i> |
+| <b>...</b>                             |                                                                       |
+| }                                      |                                                                       |
+| <b>NonStandardParameter</b>            | <b>::= SEQUENCE</b>                                                   |
+| {                                      |                                                                       |
+| <b>nonStandardIdentifier</b>           | <b>NonStandardIdentifier,</b>                                         |
+| <b>data</b>                            | <b>OCTET STRING</b>                                                   |
+| }                                      |                                                                       |
+| <b>NonStandardIdentifier</b>           | <b>::= CHOICE</b>                                                     |
+| {                                      |                                                                       |
+| <b>object</b>                          | <b>OBJECT IDENTIFIER,</b>                                             |
+| <b>h221NonStandard</b>                 | <b>SEQUENCE</b>                                                       |
+| {                                      |                                                                       |
+| <b>t35CountryCode</b>                  | <b>INTEGER (0..255),</b>                                              |
+| <b>t35Extension</b>                    | <b>INTEGER (0..255),</b>                                              |
+| <b>manufacturerCode</b>                | <b>INTEGER (0..65535)</b>                                             |
+| }                                      |                                                                       |
+| }                                      |                                                                       |
+| <b>END</b>                             |                                                                       |
+
+The following video frame synchronous control and indication signals shall be supported by all H.310 terminals:
+
+- video freeze picture release control;
+- split-screen indication;
+- document camera indication;
+- closed caption.
+
+##### Syntax
+
+The syntax for Video Frame Synchronous (VFS) Control and Indication (C&I) is specified using the notation defined in ASN.1 [38] and is shown in Table 6. Messages shall be encoded for transmission by applying the packed encoding rules specified in [39] using the basic aligned variant. The first bit in each octet which is transmitted is the most significant bit of the octet as is specified in Recommendation X.691.
+
+This information is packed in PES packets, and Presentation Time Stamp (PTS) shall be used for timing the event. Multiple **VideoFrameSynchronousCandIPDUs** can exist in a single PES packet.
+
+The PES packets including VFS C&I information shall be transmitted in the video synchronous subchannel of the ITU-T H.222.1 type C elementary stream as specified in Recommendation H.222.1. If the VFS C&I information is delivered in a Transport Stream (TS), the **stuffing\_byte** field of the TS adaptation\_field() defined in Recommendation H.222.0 shall be used for alignment with the TS packets.
+
+##### Semantics
+
+The elementary stream to which the VFS control or indication is applied, the target elementary stream, shall be specified using **ts-PID** if it is included in a Transport Stream. This field shall have the identical value with the **PID** field of the target elementary stream, which is specified in Table 2-3/H.222.0.
+
+A target elementary stream included in a Program Stream shall be specified using **streamID**. If the target elementary stream is a Recommendation H.222.1 type A-E stream, **streamIDExtension** shall be used additionally. These fields shall have identical values with the **stream\_id** and **stream\_ID\_extension** fields of the target elementary stream, which are specified in Tables 2-34/H.222.0 and 2/H.222.1.
+
+**resourceID** shall be present only in the case when a VFS C&I is applied to an elementary stream included in a different Transport Stream or Program Stream.
+
+##### Procedures
+
+For the VFS C&I signals that can be signified at the video stream level, such as "video freeze picture release control", "split-screen indication", and "document camera indication" which are provided in Recommendations H.261 and H.263, the video synchronous subchannel shall not be used for transmission. The following are the procedures of H.310 VFS C&I signals:
+
+###### a) *Freeze picture release control*
+
+This control is signified by **videoFreezePictureReleaseControl** or the "video freeze picture release control" signal embedded in the video elementary stream (i.e. Recommendation H.261 or H.263). When a decoder receives **videoFreezePicture** specified in Recommendation H.245, it shall complete updating of the current video frame but subsequently display the frozen picture. The picture shall be frozen until **videoFreezePictureReleaseControl** is received or a timeout period of at least six seconds has expired (this specification is the same as in Recommendation H.230). If a terminal or a Multipoint Control Unit (MCU) wishes to continue the freezing of the picture at the remote end more than six seconds, it should send **videoFreezePicture/H.245** repeatedly with an appropriate period.
+
+NOTE – When H.262 streams are switched by an MCU, the switched stream shall start with an H.262 sequence\_header().
+
+###### b) *Closed caption*
+
+This information is transmitted using the **closedCaption** field in the **OCTET STRING** format. The detailed usage of this indication is defined in the specification of each individual application.
+
+###### c) *Split-screen indication*
+
+This indication is signified by **splitScreenIndication** or the "split-screen indication" signal embedded in the video elementary stream (i.e. Recommendation H.261 or H.263). The indication can be transmitted when the transmitted picture is in the split-screen state defined in Recommendation H.100. An example of the response to this indication at the receiving terminal is presenting each segment of the picture on a separate monitor.
+
+###### d) *Document camera indication*
+
+This indication is signified by **documentCameraIndication** or the "document camera indication" signal embedded in the video elementary stream (i.e. Recommendation H.261 or H.263). The indication can be transmitted when the transmitted frame includes still picture information, for example documents. An example of the response to this indication at the receiving terminal is holding and presenting the still picture on a separate monitor.
+
+## 6.4 The use of the H.245 control channel
+
+All H.310 terminals shall support H.245 messages and procedures in the native H.310 communication mode. The exact set of H.245 messages and procedures that are mandated in H.310 terminals, and their usage, are specified in this subclause.
+
+The H.245 control channel carries end-to-end control messages governing operation of the H.310 system, including capabilities exchange, opening and closing of logical channels, mode preference requests, round trip delay, maintenance loop and master slave determination.
+
+There shall be exactly one control channel in each direction within H.310 systems, which shall use the messages and procedures of Recommendation H.245. The H.245 control channel shall be set up at the beginning of communication, before the transmission of audiovisual information.
+
+Recommendation H.245 specifies a number of independent protocol entities which support terminal-to-terminal signalling. A protocol entity is specified by its syntax (messages), semantics, and a set of procedures which specify the exchange of messages and the interaction with the user. H.310 terminals shall support the syntax, semantics and procedures of the following protocol entities, as specified in the following subclauses:
+
+- Master slave determination.
+- Capabilities exchange.
+- Logical channel signalling.
+- Bidirectional logical channel signalling.
+- Close logical channel signalling.
+- Mode request.
+- Round trip delay determination.
+- Maintenance loop signalling.
+- Specific commands and indications.
+
+Figure 4 shows the interaction between the H.245 protocol entities and H.310.
+
+![Diagram showing the configuration of H.245 entities in an H.310 terminal. It illustrates the interaction between the Rec. H.310 layer and the Rec. H.245 layer, which contains nine specific protocol entities.](24c9e038a791677ed33100667b64f7e6_img.jpg)
+
+The diagram illustrates the configuration of H.245 entities within an H.310 terminal. It is structured as follows:
+
+- A large outer rectangle represents the **Rec. H.310** layer.
+- Inside this rectangle, at the top, is a box labeled **Rec. H.310**.
+- Below this box, a horizontal line separates it from the **Rec. H.245** layer.
+- The **Rec. H.245** layer contains a row of nine boxes, each representing a specific protocol entity. From left to right, they are: **Master slave determination**, **Capability exchange**, **Logical channel signalling**, **Bidirectional logical channel signalling**, **Close logical channel signalling**, **Mode request**, **Round trip delay determination**, **Maintenance loop procedure**, and **Specific commands and indications**.
+- Below these nine boxes, within the same outer rectangle, is a box labeled **Rec. H.245**.
+- Vertical double-headed arrows connect the top **Rec. H.310** box to each of the nine protocol entity boxes, and each of these boxes to the bottom **Rec. H.245** box, indicating bidirectional interaction.
+
+Diagram showing the configuration of H.245 entities in an H.310 terminal. It illustrates the interaction between the Rec. H.310 layer and the Rec. H.245 layer, which contains nine specific protocol entities.
+
+T1604910-98
+
+**Figure 4/H.310 – Configuration of H.245 entities in H.310 terminal**
+
+All H.245 messages are conveyed by the underlying protocol stack, as specified in Annex A, which provides a reliable end-to-end transmission of H.245 messages using acknowledgement of correct receipt within each layer protocol.
+
+H.310 terminals shall be capable of identifying all H.245 **MultimediaSystemControlPDU** messages, and shall respond to all messages needed to realize required H.310 functions. H.310 terminals shall send the **FunctionNotSupported** message in response to unrecognizable request, response, command or the H.245 message which is not supported by the H.310 terminal.
+
+Non-standard capabilities and control messages may be issued using the **NonStandardParameter** structure defined in Recommendation H.245. Note that while the meaning of non-standard messages is defined by individual organizations, equipment built by any manufacturer may signal any non-standard message, if the meaning is known.
+
+All timers defined in Recommendation H.245 should have periods of at least the maximum data delivery time allowed by the layer carrying H.245, including any retransmissions.
+
+The following subclauses outline the sequence of primitives exchanged between H.310 and the H.245 entities. Restrictions, which are applied to the direction from the H.310 entity to the H.245 entities, to the sequence of primitives defined in Recommendation H.245 are stated in the following subclauses.
+
+### 6.4.1 Master slave determination
+
+Master slave determination shall follow the procedures of Recommendation H.245, which provides the mechanism on an even basis to determine which is the master terminal and which is the slave terminal. The master terminal will be permitted to manage the resource limited to only one avoiding the simultaneous initiation of similar events by two or more terminals. The master terminal has precedence where conflict of requests occurs.
+
+There shall be exactly one MSDSE in one H.310 terminal. The H.310 terminal can start the master slave determination procedure by issuing **DETERMINE.request** primitive to its MSDSE without parameter.
+
+When the **DETERMINE.confirm** primitive is received from the MSDSE after **DETERMINE.request** was issued, the master slave determination has been successfully completed and confirmed by the peer terminal. The result of determination is indicated in the **TYPE** parameter of the **DETERMINE.confirm** primitive. If the **REJECT.indication** primitive is received instead, the determination procedure has failed. The H.310 terminal may reissue **DETERMINE.request** for retrying the master slave determination. When **DETERMINE.indication** is received, the peer terminal has also invoked the master slave determination procedure and H.310 shall follow the incoming side protocol described below. **DETERMINE.request** shall not be issued until **DETERMINE.confirm** or **REJECT.indication** primitive is received, after **DETERMINE.request** has been issued.
+
+When the peer terminal invoked the master slave determination procedure, H.310 will receive **DETERMINE.indication** from the MSDSE. The **TYPE** parameter in **DETERMINE.indication** indicates the preliminary result of master slave determination. However, it is necessary to confirm the result between the local and remote terminals. Therefore, H.310 shall wait for the **DETERMINE.confirm** primitive. When the **ERROR.indication** primitive is received, mismatch of state between local MSDSE and remote MSDSE may have occurred. It should be noted that **REJECT.indication** will follow **ERROR.indication** in some error situations. In these cases, the previously received result indicated by the **TYPE** parameter in the **DETERMINE.indication** primitive shall be discarded and ignored. **DETERMINE.request** shall not be issued until **DETERMINE.confirm** or **REJECT.indication** primitive is received, after **DETERMINE.indication** has been received.
+
+At the start of the communication, the H.310 terminal shall not have a preference that it is a master or a slave. H.245 procedures in which the master and slave distinction is necessary (see Table 7), shall not be initiated until the master/slave status has been determined.
+
+Only one random number shall be chosen by the terminal for one call, except in the case of identical random numbers, as described in Recommendation H.245. It should be noted that identical means identical modulo  $2^{23}$ .
+
+Terminals may reinvoke the master slave determination if necessary, according to the procedures described above. The value of counter N100 is 3 for H.310 terminal.
+
+**Table 7/H.310 – Necessity of the master slave determination procedure**
+
+| <b>H.245 procedure</b>                   | <b>Master/slave result is required?</b> |
+|------------------------------------------|-----------------------------------------|
+| Master slave determination               | Irrelevant                              |
+| Capabilities exchange                    | No                                      |
+| Logical channel signalling               | Yes                                     |
+| Bidirectional logical channel signalling | Yes                                     |
+| Close logical channel signalling         | No                                      |
+| Mode request                             | Yes                                     |
+| Round trip delay determination           | No                                      |
+| Maintenance loop signalling              | Yes                                     |
+| Specific commands and indications        | No                                      |
+
+### **6.4.2 Capabilities exchange**
+
+Capabilities exchange shall follow the procedures of Recommendation H.245, which provides for separate receive and transmit capabilities.
+
+Receive capabilities describe the terminals ability to receive and process incoming information streams. Transmitters shall limit the content of their transmitted information to that which the receiver has indicated it is capable of receiving. The absence of a receive capability indicates that the terminal cannot receive (is a transmitter only).
+
+Transmit capabilities describe the terminals ability to transmit information streams. Transmit capabilities serve to offer receivers a choice of possible modes of operation, so that the receiver may request the mode which it prefers to receive.
+
+There shall be exactly one outgoing CESE and one incoming CESE in one H.310 terminal. H.310 terminal can start the capability exchange procedure by issuing TRANSFER.request primitive to its outgoing CESE with proper parameters. The value of PROTOID parameter shall be "1" for terminals conforming to this Recommendation. MUXCAP and CAPDESCRIPTORS parameters with at least one capability set is mandatory for the H.310 terminal. Though the use of CAPTABLE parameter is optional, CAPTABLE parameter is required at the start of the communication, because the remote terminal does not have any knowledge about capability table entries which are referred to by the CAPDESCRIPTORS parameter. When H.310 terminal reinvokes the capability exchange procedure after the successful completion of a capability exchange, CAPTABLE can be omitted provided that CAPTABLEEntries are not changed from those that have already been transmitted.
+
+When the TRANSFER.response primitive is received from the outgoing CESE after TRANSFER.request has been issued, the capability message has been successfully transmitted to the peer terminal. If the REJECT.indication primitive is received instead, the previously sent capability message has not been accepted by the peer terminal (SOURCE=USER), or the timer has expired before receiving the response from the peer terminal (SOURCE=PROTOCOL). The H.310 terminal may reissue the TRANSFER.request primitive for retrying the capability message transmission in these cases. TRANSFER.request shall not be issued until TRANSFER.confirm or REJECT.indication primitive has been received, after TRANSFER.request has been issued.
+
+H.310 shall respond to the TRANSFER.indication primitive received from the incoming CESE, by issuing the TRANSFER.response primitive if the capabilities can be accepted successfully, or by issuing the REJECT.request primitive if the capabilities are not acceptable. The H.310 terminal may receive REJECT.indication, before responding to TRANSFER.indication. In this case, H.310 shall discard and ignore the contents of the previously received TRANSFER.indication and shall not respond to that indication until a new TRANSFER.indication is received.
+
+At the start of the communication, the H.310 terminal shall recognize that its own transmit capability declared to the remote terminal and the receive capability of remote terminal are null. Therefore, audiovisual communication cannot be started before the capability exchange procedure is carried out. The H.310 terminal can update its knowledge about its own declared and remote capabilities, only after the capability exchange procedure has been successfully completed.
+
+Terminals may reinvoke the capability exchange procedure at any time, according to the procedures described above.
+
+### 6.4.3 Logical channel signalling
+
+Each logical channel carries information from a transmitter to a receiver, and is identified by a logical channel number unique for each direction of transmission.
+
+Logical channels are opened and closed using the **OpenLogicalChannel** and **CloseLogicalChannel** messages and procedures of Recommendation H.245.
+
+When a logical channel is opened, the **OpenLogicalChannel** message fully describes the content of the logical channel, including media type, algorithm in use and any options, and all other information needed for the receiver to interpret the contents of the logical channel. Logical channels may be closed when no longer needed.
+
+Certain media types, including data protocols such as T.120, inherently require a bidirectional channel for their operation. In such cases a bidirectional logical channel, which is capable of information transmission in both directions, may be opened using the bidirectional channel opening procedures of Recommendation H.245.
+
+NOTE 1 – A pair of unidirectional logical channels, each of which is opened by the open logical channel procedure, can be applied to a bidirectional operation of those media providing the transmission in each direction. However, the use of bidirectional logical channel is strongly recommended for bidirectional media in this Recommendation.
+
+Bidirectional logical channels in H.310 may have asymmetrical characteristics, such that the medium type in each direction of transmission might be different.
+
+H.310 supports multiple logical channels. There shall be one outgoing LCSE and one incoming LCSE for each logical channel. There shall also be one outgoing CLCSE and one incoming CLCSE managing the same logical channel as an incoming LCSE and an outgoing LCSE, respectively. H.310 terminal can start the open logical channel procedure by issuing the ESTABLISH.request primitive to its outgoing LCSE of the required logical channel with proper parameters.
+
+FORWARD\_PARAM parameter describes the content of the logical channel, which will be transferred by the **OpenLogicalChannel** message to the peer terminal.
+
+When the ESTABLISH.response primitive is received from the outgoing LCSE after ESTABLISH.request was issued, the logical channel is successfully opened and H.310 terminal can start audiovisual information transmission through this logical channel. If the REJECT.indication primitive is received instead, either the open logical channel request has not been accepted by the peer terminal (SOURCE=USER), or the timer has expired before receiving a response from the peer terminal (SOURCE=LCSE). The H.310 terminal may reissue the ESTABLISH.request for retrying the open logical channel request in these cases.
+
+H.310 may close a logical channel which has been successfully opened by issuing the RELEASE.request primitive at the outgoing LCSE. The RELEASE.confirm primitive is passed to H.310 when the logical channel has been successfully closed. If the ERROR.indication primitive precedes the RELEASE.confirm primitive, then the local timer has expired before a response was received from the peer terminal.
+
+Before the ESTABLISH.confirm or the RELEASE.indication primitive is received in response to an earlier ESTABLISH.request, H.310 may close the logical channel using the RELEASE.indication primitive at the outgoing LCSE.
+
+Before the RELEASE.confirm primitive is received in response to a previously sent RELEASE.request primitive, H.310 may establish the logical channel using the ESTABLISH.request primitive at the outgoing LCSE.
+
+When the ERROR.indication primitive is received from the outgoing LCSE, a timer expiry or a mismatch of state has occurred and the logical channel has been closed. The ERROR.indication primitive is followed by either the RELEASE.indication or the RELEASE.confirm primitive.
+
+The H.310 terminal shall respond to the ESTABLISH.indication primitive received from the incoming LCSE, by issuing ESTABLISH.response if the opening of the logical channel can be accepted, or by RELEASE.request if the logical channel cannot be opened.
+
+H.310 may receive RELEASE.indication, before responding to ESTABLISH.indication. It is no longer necessary to respond to the previous ESTABLISH.request primitive and the logical channel shall be kept closed. Whenever RELEASE.indication is received, H.310 shall regard that the logical channel is now closed and unavailable. If RELEASE.indication is followed by ESTABLISH.indication, the logical channel immediately becomes unavailable and H.310 shall decide whether new logical channel with parameters conveyed by ESTABLISH.indication is acceptable.
+
+Incoming side of the H.310 terminal can request to close a logical channel using the close logical channel procedure by issuing the CLOSE.request primitive to outgoing LCSE. The logical channel is kept opened unless CLOSE.confirm is received. If REJECT.indication is received, H.310 may reinvoke the close logical channel procedure.
+
+NOTE 2 – Receipt of CLOSE.confirm indicates that the remote H.310 terminal will close the logical channel. The channel is not closed until it does so.
+
+If H.310 receives audiovisual information through a logical channel that is not open, the receiving H.310 terminal should request the closing of that logical channel by invoking close logical channel procedure to recover from the mismatch of state of local and remote LCSEs.
+
+When contention occurs between the open logical channel procedure and the close logical channel procedure for the same channel, the close logical channel always has a higher priority than the open logical channel. Therefore, if H.310 wants to re-open the logical channel, the open logical channel
+
+procedure can be invoked only after the close logical channel procedure has been successfully completed.
+
+The open bidirectional logical channel procedure is very similar to the procedure for unidirectional logical channel. The only difference is that the incoming side H.310 shall wait for ESTABLISH.confirm from the incoming B-LCSE, after H.310 responds to ESTABLISH.indication by ESTABLISH.response. Though a unidirectional channel can become active by issuing ESTABLISH.response, bidirectional channel cannot become active until ESTABLISH.confirm is received.
+
+### 6.4.4 Mode request
+
+The H.310 terminal is able to request a remote terminal to change its transmit mode of operation by using the mode request procedure of Recommendation H.245.
+
+The terminal shall select the requesting mode of operation from the valid transmission capabilities of the peer terminal previously received by successfully completed capability exchange procedure(s). If the peer terminal is receive only, and does not have any transmission capabilities, the mode request procedure shall not be invoked.
+
+There shall be exactly one outgoing MRSE and incoming MRSE in one H.310 terminal. The H.310 terminal can start the mode request procedure by issuing the TRANSFER.request primitive to its outgoing MRSE with proper parameters. MODE-ELEMENT parameter describes the requesting mode of operation for a remote terminal.
+
+When the TRANSFER.response primitive is received from the outgoing MRSE after TRANSFER.request was issued, the requested mode has been accepted by the peer terminal. The contents of logical channels in the receiving direction will soon be changed by the remote terminal according to the requested communication mode. If the REJECT.indication primitive is received instead, the requested mode has not been accepted by the peer terminal (SOURCE=USER), or the timer has expired before receiving a response from the peer terminal (SOURCE=PROTOCOL). The H.310 terminal may reissue TRANSFER.request for retrying the mode request procedure with the same parameters in the latter case, or with different parameters in the former case.
+
+NOTE – It is recommended for the H.310 terminal that TRANSFER.request should not be issued until TRANSFER.confirm or REJECT.indication primitive has been received, after TRANSFER.request has been issued.
+
+H.310 shall respond to TRANSFER.indication received from the incoming MRSE, by issuing the TRANSFER.response primitive if the requested mode can be accepted, or by REJECT.request if the requested mode is not acceptable. The H.310 terminal may receive REJECT.indication, before responding to TRANSFER.indication. In this case, H.310 shall discard and ignore the previously received TRANSFER.indication and shall not respond to that indication until a new TRANSFER.indication is received.
+
+Terminals may invoke the mode request procedure at any time, according to the procedures described above.
+
+### 6.4.5 Round trip delay
+
+The round trip delay procedure of H.245 enables the H.310 terminal to measure the round trip delay of H.245 message transmission between a local terminal and a remote terminal. This delay includes all the processing delay of underlying protocol layers for H.245 message transmission and H.245 message processing time of H.245 entities as well as delay in physical transmission line. This round trip delay procedure can be used to determine if the peer H.245 entity is still alive (i.e. as a keep alive function).
+
+There shall be exactly one RTDSE in one H.310 terminal. H.310 terminal can start the round trip delay procedure by issuing TRANSFER.request primitive to its RTDSE.
+
+When the TRANSFER.confirm primitive is received from the RTDSE after TRANSFER.request was issued, H.310 can estimate the value of the measured round trip delay using DELAY parameter in TRANSFER.confirm primitive.
+
+NOTE – The round trip delay procedure in Recommendation H.245 specifies that the DELAY parameter indicates the value of the timer T105 which cannot be directly interpreted as delay itself. Therefore, the actual delay value is: time out value of T105 – DELAY parameter.
+
+If EXPIRY.indication primitive is received instead, the peer H.245 entity has not responded before the local timer has expired. In this case, the remote H.245 entity may not be alive and H.245 procedures may not be usable. The local H.310 terminal may take appropriate actions, such as release the call or indicate to the human user, in this error situation.
+
+It is not necessary for H.310 to respond to any incoming messages concerning the round trip delay procedure, because the **RoundTripDelayResponse** message is automatically issued within RTDSE in response to the **RoundTripDelayRequest** message.
+
+Terminals may invoke the round trip delay procedure at any time, according to the procedures described above.
+
+### 6.4.6 Maintenance loop
+
+The maintenance loop procedure of Recommendation H.245 provides a maintenance loop function for the H.310 terminal.
+
+There shall be exactly one outgoing MLSE and incoming MLSE for each logical channel, and one of each for the system loop, in one H.310 terminal. The H.310 terminal can start the maintenance loop procedure by issuing LOOP.request primitive to an outgoing MLSE with proper parameters. LOOP\_TYPE parameter indicates the type of loop operation to the remote terminal.
+
+When the LOOP.confirm primitive is received from the outgoing MLSE after LOOP.request was issued, maintenance loop operation has been established by the peer terminal. Data received from logical channels will be that transmitted by the local terminal and then looped back. If the RELEASE.indication primitive is received instead, the maintenance loop is not accepted by the peer terminal. If ERROR.indication(B) primitive is received, the timer has expired before receiving a response from the peer terminal. LOOP.request shall not be issued until LOOP.confirm or RELEASE.indication primitive is received, after LOOP.request has been issued.
+
+When the ERROR.indication primitive is received, mismatch of state between local MLSE and remote MLSE may have occurred. In these error cases, RELEASE.indication will follow ERROR.indication, the maintenance loop procedure has failed and the state of local outgoing MLSE shall be kept not looped.
+
+The H.310 terminal shall respond to LOOP.indication received from the incoming MLSE, by LOOP.response if the requested maintenance loop operation can be accepted, or by RELEASE.request if the maintenance loop is not acceptable.
+
+Whenever the H.310 terminal receives RELEASE.indication, H.310 shall regard that the loop operation is released and the state of incoming MLSE immediately becomes not looped.
+
+The H.310 terminal which invoked the maintenance loop procedure shall be responsible for releasing the looped operation, when the maintenance loop becomes unnecessary. Terminals may invoke the maintenance loop procedure at any time, according to the procedures described above.
+
+### **6.4.7 Specific commands and indications**
+
+H.310 shall support the following H.245 commands and indications:
+
+SendTerminalCapabilitySet
+
+EncryptionCommand
+
+FlowControlCommand
+
+EndSessionCommand
+
+MiscellaneousCommand
+
+FunctionNotSupported
+
+MiscellaneousIndication
+
+JitterIndication
+
+NewATMVCIndication
+
+NewATMVCCCommand
+
+UserInputIndication
+
+# **7 H.310 call phases**
+
+The call and signalling procedures (between two H.310 terminals or between an H.310 terminal and an H.320/H.321 terminal) described in this clause are based on the following principles:
+
+- 1) An H.310 terminal (initiating or receiving a call) is able to identify the remote terminal type (H.320/H.321, H.310 RAST, etc.) via Q.2931 signalling at the beginning of the call (i.e. prior to audiovisual communications).
+- 2) When two H.310 terminals are communicating, a default H.245 (logical) channel is established over the initial ATM VC at the beginning of the call.
+- 3) When two H.310 terminals communicate, each terminal indicates its capabilities (specified in 6.3) to the remote terminal using the capabilities exchange messages and procedures described in Recommendation H.245.
+- 4) When an H.310 terminal communicates with an H.320/H.321 terminal, the two terminals use the H.242 and H.230 messages and procedures for capability exchanges and other in-band signalling needs as done in H.320/H.321 terminals.
+- 5) For the different types of native H.310 communication modes, in-band signalling during the call is based on H.245 messages and procedures.
+
+Depending on the type of the two communicating terminals, an H.310 terminal shall employ one of the following two call procedures: native H.310 communication call procedures or H.320/H.321 interoperation call procedures.
+
+## **7.1 Native H.310 communication call procedures**
+
+The native H.310 communication call procedures shall be supported by all unidirectional and bidirectional H.310 terminals.
+
+The H.310 correlationID is composed of a session identification field and the 2 octet H.245 "resourceID" as indicated in Table 8. The H.245 resourceID in the H222LogicalChannelParameters is used to indicate which ATM Virtual Channel the logical channel is associated with. The session identification field is currently undefined and is reserved for future use.
+
+**Table 8/H.310 – Definition of H.310 CorrelationID**
+
+| H.310 CorrelationID   |                  |
+|-----------------------|------------------|
+| Session ID (Reserved) | H.245 resourceID |
+
+In allocating H.245 resourceIDs, the side that sets up the initial H.245 VC chooses values starting from the lowest possible value and the other side (the called side), chooses values starting from the highest in the range.
+
+The Generic Identifier Transport (GIT) Information Element shall be used for the transmission of the H.310 correlationID in the Q.2931 SETUP message. The GIT information element is specified in Recommendation Q.2941.1.
+
+Since the resourceID is the only valid element in the correlation ID at this time, only the resourceID is sent in the Q.2931 SETUP. This is pictorially shown in Figure 5. When coding the GIT, the identifier related standard/application is coded as this Recommendation, the identifier type as Resource, and the identifier length as two octets.
+
+![Diagram of H.310 Correlation ID structure showing Session ID and H.245 Resource ID fields with their respective uses.](382a9c9e4816bd229191ab4591424dd8_img.jpg)
+
+The diagram illustrates the structure of the H.310 Correlation ID. At the top, a bracket labeled "H.310 Correlation ID" spans over a table with two columns: "Session ID" and "H.245 Resource ID". Below the "Session ID" column, a downward arrow points to the text "Reserved (Not used)". Below the "H.245 Resource ID" column, a downward arrow points to the text "Placed in Q.2931 GIT Identifier Type = Resource". To the right of the second arrow, the text "T1604920-98" is present.
+
+Diagram of H.310 Correlation ID structure showing Session ID and H.245 Resource ID fields with their respective uses.
+
+**Figure 5/H.310 – Use of H.310 CorrelationID**
+
+Optionally, the H.310 correlationID may also be sent in the user-to-user information IE.
+
+The native H.310 communication call procedures are divided into the following call phases as shown in Figure 6.
+
+![Flowchart of H.310 call phases: Phase A (Call Setup), Phase B (Audiovisual communication), and Phase C (Call Release).](77959075c823bb5169480d7b8ff82a63_img.jpg)
+
+```
+
+graph TD
+    subgraph PhaseA [Phase A (Call Setup)]
+        A1["A1:  
+Initial VC Setup  
+Q.2931"]
+        A2["A2:  
+Capability Exchange  
+Master Slave Determination  
+H.245"]
+        A3["A3:  
+Additional VC Setup  
+Q.2931"]
+        A4["A4:  
+Logical Channels Setup  
+H.245"]
+        A1 --> A2
+        A2 --> A3
+        A3 --> A4
+    end
+    subgraph PhaseB [Phase B (Audiovisual communication)]
+        BST["Audiovisual Signal Transfer"]
+        subgraph Loop [ ]
+            L["- Mode Request and Switching  
+- C&I Signalling  
+- Maintenance Loop  
+- Round Trip Delay  
+H.245  
+- Capability Exchange  
+H.245  
+- Additional VC Setup  
+Q.2931  
+- Logical Channels Setup/Release  
+H.245"]
+        end
+        BST --> Loop
+        Loop --> BST
+    end
+    subgraph PhaseC [Phase C (Call Release)]
+        C1["C1:  
+Logical Channels Release  
+H.245"]
+        C2["C2:  
+Virtual Channel Release  
+Q.2931"]
+        C1 --> C2
+    end
+    PhaseA --> PhaseB
+    PhaseB --> PhaseC
+    style Loop fill:none,stroke:none
+  
+```
+
+The diagram illustrates the call phases for native H.310 communication, organized into three main vertical sections:
+
+- Phase A (Call Setup):** This section contains four sequential steps:
+  - A1: Initial VC Setup (Q.2931)
+  - A2: Capability Exchange, Master Slave Determination (H.245)
+  - A3: Additional VC Setup (Q.2931)
+  - A4: Logical Channels Setup (H.245)
+- Phase B (Audiovisual communication):** This section begins with "Audiovisual Signal Transfer". Below this is a loop containing several operations:
+  - Mode Request and Switching
+  - C&I Signalling
+  - Maintenance Loop
+  - Round Trip Delay (H.245)
+  - Capability Exchange (H.245)
+  - Additional VC Setup (Q.2931)
+  - Logical Channels Setup/Release (H.245)
+- Phase C (Call Release):** This section contains two sequential steps:
+  - C1: Logical Channels Release (H.245)
+  - C2: Virtual Channel Release (Q.2931)
+
+Arrows indicate the flow from Phase A to Phase B, and from Phase B to Phase C. Within Phase B, an arrow points from the "Audiovisual Signal Transfer" box into the loop, and another arrow points from the loop back to the same box.
+
+Flowchart of H.310 call phases: Phase A (Call Setup), Phase B (Audiovisual communication), and Phase C (Call Release).
+
+T1604930-98
+
+**Figure 6/H.310 – H.310 call phases for native H.310 communication**
+
+### 7.1.1 Phase A (call setup)
+
+Phase A is a call-setup procedure phase which is divided into the following subphases.
+
+NOTE 1 – The call procedures defined here are based on establishing two or more VCs: one for H.245 messages, and the others for the transfer of audiovisual and other data. A single-VC call procedure is under study.
+
+#### Phase A1 (initial VC setup)
+
+In this phase, the initial ATM Virtual Channel (VC) using a Q.2931 SETUP message is established. The exact parameters and DSS 2 Information Elements (IEs) used for this phase are described in Annex B.
+
+One of the key features of this phase is that it enables an H.310 terminal (initiating or receiving a call) to either identify the type of remote H.310 terminal or infer that the remote terminal is not an H.310 terminal type. This is done by using the Broadband Bearer Capability (B-BC), Narrow-band Bearer Capability (N-BC) and other information elements of the Q.2931 SETUP message. An H.310 terminal shall set these information elements to the appropriate parameters which indicate the H.310 terminal type. If an H.310 terminal does not receive the N-BC information element from the remote terminal, then the H.310 terminal can assume that it is not communicating with an H.320/H.321 terminal.
+
+The initial VC shall have a bit rate of 64 kbit/s at the AAL-SAP, for the transfer of H.245 messages using the separate VC stack described in Annex A.
+
+NOTE 2 – Interaction between the arrival of the initial call and the human user is under study in the light of audio communication start up and charging aspects.
+
+#### Phase A2 (capability exchange and master slave determination)
+
+In this phase, it is assumed that each H.310 terminal has already identified that the remote terminal is an H.310 terminal type. Therefore, at this stage the two terminals shall exchange their capability information using the capability exchange signalling protocol defined in Recommendation H.245 as described in 6.4.2 over the initial VC that has been established in Phase A1. At the same time as this, the two terminals shall determine which is master and which is slave using the master slave determination signalling protocol defined in Recommendation H.245 as specified in 6.4.1. Based on the capabilities of the two terminals, an appropriate common mode of communication shall be determined.
+
+H.310 terminals shall be capable of operating in both master and slave modes, and shall set **terminalType** to 128 and set **statusDeterminationNumber** to a random number in the range 0 to  $2^{24}-1$ . Only one random number shall be chosen by the terminal for each call, except in the case of identical random numbers, as described in Recommendation H.245.
+
+#### Phase A3 (additional VC setup)
+
+This paragraph applies to the case where MCU is not used in the session. In this phase, and based on the communication mode determined above, the calling terminal, that is, the one that initiated the first VC SETUP message, shall firstly indicate the characteristics of the additional VC(s) to the remote end using the H.245 **NewATMVCIndication** message, and then shall set up the additional VC(s) with the appropriate parameters, such as bit rate and AAL type, for the transfer of the audiovisual and other data between the two H.310 terminals.
+
+NOTE 3 – This allows the remote end to receive the H.245 **NewATMVCIndication** message before responding to the VC-setup message.
+
+This paragraph applies to the case where MCU is used in the session. If the terminal is talking to an MCU, that is, it has received the H.245 **multipointModeCommand** message, the terminal shall wait
+
+for the H.245 **NewATMVCIndication** message or the H.245 **NewATMVCCCommand** message. In the former case, the additional VC(s) with the appropriate parameters, such as bit rate and AAL type, for the transfer of the audiovisual and other data shall be initiated by the MCU. In the latter case, the additional VC(s) with the appropriate parameters shall be initiated by the terminal.
+
+#### **Phase A4 (logical channels setup)**
+
+The choice of communication mode can be made by either the master or the slave. An H.310 terminal shall open the desired video, audio, data, and/or control logical channels using the logical channel signalling protocol and bidirectional logical channel signalling protocol defined in Recommendation H.245 as described in 6.4.3.
+
+### **7.1.2 Phase B (audiovisual communication)**
+
+In addition to the transfer of audiovisual and other data during Phase B of the call, one or more of the following procedures may also take place.
+
+#### **Mode request and switching**
+
+H.310 terminals can request a new mode of audiovisual communication over the different logical channels (established over a given VC) using the mode request signalling protocol defined in Recommendation H.245 as described in 6.4.4, and can switch to a new mode using the logical channel signalling protocol and bidirectional logical channel signalling protocol, and aided by the close logical channel signalling protocol, defined in Recommendation H.245 as described in 6.4.3.
+
+#### **Control & Indication (C&I) signalling**
+
+H.310 terminals can use H.230-like C&I signals provided by Recommendation H.245, in addition to the video frame synchronous C&I signals defined in 6.3.5.3. Specific H.230-like C&I signals which the H.310 terminal shall support is given in 6.4.7.
+
+#### **Maintenance loops and round trip delay signalling**
+
+H.310 terminals can perform loops for maintenance purposes using the maintenance loop signalling protocol defined in Recommendation H.245 as described in 6.4.6. Further information is provided on maintenance loops in clause 11.
+
+H.310 terminals can use the round trip delay signalling protocol defined in Recommendation H.245 as described in 6.4.5 to determine the round trip delay between the two terminals and also to determine if the far-end H.245 entity is "still alive".
+
+During Phase B, depending on the capabilities of the terminals involved and the requests of users, the following procedures may also be invoked:
+
+- capability exchange;
+- additional VC setup;
+- logical channels setup.
+
+These procedures are identical to those for Phases A2, A3 and A4, respectively.
+
+### **7.1.3 Phase C (call release)**
+
+Phase C is a call release procedure phase which is divided into the following subphases.
+
+#### **Phase C1 (logical channels release)**
+
+In this phase, all logical channels are closed and **EndSessionCommand** is transmitted, using the procedures described in Recommendation H.245.
+
+#### Phase C2 (virtual channels release)
+
+In this phase, all ATM VCs are released using the procedures described in Recommendation Q.2931.
+
+## 7.2 H.320/H.321 interoperation call procedures
+
+The H.320/H.321 interoperation call procedures shall be supported by all bidirectional H.310 RAST type terminals.
+
+Interoperation between an H.310 RAST terminal and an H.320/H.321 terminal shall be through the use of circuit transport service which requires inclusion of both broadband and narrow-band information elements (B-BC, ATM Traffic Descriptor, AAL parameters, etc.; N-BC, N-LLC, N-HLC).
+
+After determining that the remote terminal is an H.320/H.321 terminal type based on the Q.2931 SETUP message, an H.310 RAST terminal shall follow the call procedures described in Recommendations H.320 and H.321.
+
+NOTE – See clause 7/H.321 for interactions between an H.310 RAST-5 terminal or a RAST-1&5 terminal when working with AAL 5, the gateway and an H.320 or H.321/Annex A terminal.
+
+# 8 Multipoint communication
+
+H.310 terminals may be used in multipoint configuration through MCUs which may be accommodated in B-ISDN, N-ISDN or other networks.
+
+## 8.1 Native H.310 communication modes
+
+When an H.310 terminal is involved in the multipoint communication, MCUs may force terminals into a particular common mode of transmission by sending to the terminal a receive capability set listing only the desired mode of transmission or by sending the **RequestMode** message. The H.310 terminal shall obey the **multipointModeCommand** message of Recommendation H.245. It shall also obey **videoFreezePicture** and **videoFastUpdatePicture** messages of Recommendation H.245 and **videoFreezePictureRelease** message of this Recommendation for the video display control.
+
+Since each link in a multipoint configuration may be operating at different bit rates, MCUs may choose to send H.245 **FlowControlCommand** messages to limit the transmitted bit rates to those which can be sent to receivers.
+
+## 8.2 H.320/H.321 interoperation modes
+
+The requirements that apply to H.320 terminals also apply to H.310 terminals. See 4.5/H.320.
+
+NOTE – The clock synchronization of terminals connected to different types of networks and communicating through MCU(s) is for further study.
+
+## 8.3 Other aspects
+
+Cascaded MCU operation, encryption and other aspects of multipoint communication are under study.
+
+# 9 Equipment requirements
+
+Audio level setting for G.711, G.722, G.728 is as specified in Recommendation H.320. Audio level setting for other audio coding including ISO/IEC 11172 audio, ISO/IEC 13818 audio is under study. Other aspects of equipment requirements are also under study.
+
+# 10 Error resilience
+
+## 10.1 Video layer
+
+Several methods of error resilience at the video layer are provided as information in D.13/H.262.
+
+## 10.2 Multimedia multiplex layer
+
+An optional method of error resilience is defined in Recommendation H.222.1 which employs the use of two ATM virtual connections and the modified and restricted use of data partitioning specified in Recommendation H.262.
+
+# 11 Maintenance loop
+
+Some loopback functions are defined in Recommendation H.245 to allow verification of some functional aspects of the terminal, correct operation of the system and satisfactory quality of the service to the remote party. H.310 RAST terminals shall support the following loop back, as shown in Figure 6:
+
+- a) Normal mode: no loop. Indicated in a) of Figure 7.
+- b) System loop at the multiplex-AAL interface (toward the AAL interface). Upon receiving the **systemLoop** request as defined in Recommendation H.245, loopback toward the AAL side shall be made, as indicated in b) of Figure 7. The bit rate should not be changed in response to this request. Support for this loopback is mandatory for all terminals, but users may optionally disable response to it.
+- c) Logical channel loopback in H.222.1 multiplex (toward the multiplex interface). Upon receiving the **logicalChannelLoop** request, each information stream for the specified logical channel should be looped back on the corresponding reverse logical channel, as indicated in c) of Figure 7. This loopback is optional, and should be used only on logical channels opened using the bidirectional channel procedures of Recommendation H.245.
+- d) Media loop at analogue I/O interface (optional): Upon receiving the **mediaLoop** request as defined in Recommendation H.245, loopback of the content of the selected logical channel should be activated as close as possible to the analogue interface of the video/audio codec towards the video/audio codec, so that decoded and re-coded media content is looped, as indicated in d) of Figure 7. This loopback is optional, and should be used only on logical channels opened using the bidirectional channel procedures of Recommendation H.245.
+
+The system loopback (**systemLoop**) request may also be used during actual conversations, for example to measure the network delay.
+
+The message loopback off (**MaintenanceLoopOffCommand**) requires that all loopbacks currently in effect be turned off.
+
+![Four diagrams (a, b, c, d) illustrating maintenance loops in an H.310 terminal architecture. Each diagram shows a flow from a camera/monitor through a Codec, a Multiplex, and an AAL. (a) Normal: Standard forward and backward flow. (b) System loopback: Loopback at the AAL interface. (c) Logical Channel loopback: Loopback at the Multiplex for one logical channel. (d) Media loopback: Loopback at the Codec interface. A label 'T1604940-98' is present at the bottom right of diagram (d).](cbb2d311b20781a595488445ded48d0a_img.jpg)
+
+The figure illustrates four maintenance loop scenarios in an H.310 terminal architecture. Each scenario shows a flow from a camera/monitor through a Codec, a Multiplex, and an AAL.
+
+- a) Normal:** The standard flow where data from the camera is encoded by the Codec, multiplexed, and sent to the AAL. Return data from the AAL is decoded by the Codec and displayed on the monitor.
+- b) System loopback:** The flow is looped back at the AAL interface. Data from the Multiplex is sent to the AAL and immediately looped back to the Multiplex.
+- c) Logical Channel loopback:** The flow is looped back at the Multiplex. Data from the Codec is multiplexed and immediately looped back to the Codec. A note indicates that this applies to "One logical channel only" and "Other logical channels" continue to function normally.
+- d) Media loopback:** The flow is looped back at the Codec interface. Data from the camera is encoded and immediately looped back to the camera/monitor.
+
+T1604940-98
+
+Four diagrams (a, b, c, d) illustrating maintenance loops in an H.310 terminal architecture. Each diagram shows a flow from a camera/monitor through a Codec, a Multiplex, and an AAL. (a) Normal: Standard forward and backward flow. (b) System loopback: Loopback at the AAL interface. (c) Logical Channel loopback: Loopback at the Multiplex for one logical channel. (d) Media loopback: Loopback at the Codec interface. A label 'T1604940-98' is present at the bottom right of diagram (d).
+
+**Figure 7/H.310 – Maintenance loops**
+
+# 12 Intercommunications
+
+Interworking between bidirectional (RAST) H.310 terminals and H.320/H.321 is mandatory. In addition, interworking among the different types of bidirectional H.310 terminals is also mandatory. Figure 8 illustrates the interworking scenarios for H.310 terminals.
+
+![Diagram illustrating the interworking of H.310 terminals. A central 'Customer Premises ATM network (ATM LAN)' is connected to two gateways, G1 and G2. G1 is connected to a 'B-ISDN' node, which in turn connects to H.310 RAST-1, H.310 RAST-1&5, H.321/Annex A, and H.321/Annexes A and B terminals. G2 is connected to an 'N-ISDN' node, which connects to an 'I.580 Gateway (AAL 1)' and an 'H.320' terminal. The ATM LAN also connects directly to H.310 RAST-5, H.310 RAST-1, H.310 RAST-1&5, H.321/Annex B, H.321/Annex A, and H.321/Annexes A and B terminals. A label 'T1604950-98' is present in the bottom right of the diagram area.](e8e818455bb0d1a6153299a388b94868_img.jpg)
+
+Diagram illustrating the interworking of H.310 terminals. A central 'Customer Premises ATM network (ATM LAN)' is connected to two gateways, G1 and G2. G1 is connected to a 'B-ISDN' node, which in turn connects to H.310 RAST-1, H.310 RAST-1&5, H.321/Annex A, and H.321/Annexes A and B terminals. G2 is connected to an 'N-ISDN' node, which connects to an 'I.580 Gateway (AAL 1)' and an 'H.320' terminal. The ATM LAN also connects directly to H.310 RAST-5, H.310 RAST-1, H.310 RAST-1&5, H.321/Annex B, H.321/Annex A, and H.321/Annexes A and B terminals. A label 'T1604950-98' is present in the bottom right of the diagram area.
+
+G1 = AAL 1/AAL 5 Gateway
+
+G2 = H.321 Annex B/H.320 Gateway
+
+**Figure 8/H.310 – Interworking of H.310 terminals**
+
+## 12.1 Intercommunication between different terminal types
+
+Since the support of AAL type 1 (for the transfer of H.222.1 and H.221 audiovisual signals over B-ISDN) is mandatory for H.310 RAST-1 and RAST-1&5 terminals, these terminals can interwork with each other and with H.321 without a gateway function.
+
+Similarly, since the support of AAL type 5 (for the transfer of H.222.1 and H.221 audiovisual signals over B-ISDN) is mandatory for H.310 RAST-5 and RAST-1&5 terminals, these terminals can interwork with each other and with H.321/Annex B without a gateway function.
+
+RAST-5 terminals and RAST-1&5 terminals working in the AAL 5 mode shall interwork with RAST-1 terminals and RAST-1&5 terminals working in the AAL 1 mode and with H.321 with a gateway that is located in the customer premises ATM network. This gateway is needed to provide interworking functions between:
+
+- a) RAST-5 and RAST-1;
+- b) RAST-5 and RAST-1&5 working in AAL 1 mode; and
+- c) RAST-5 or RAST-1&5 working in AAL 5 mode and H.321 terminals.
+
+Communication procedures for the above cases a) and b) are given in Annex C, while those for case c) are given in clause 7/H.321.
+
+Similarly, a gateway between an N-ISDN and a customer premises ATM network is needed to provide interworking functions between RAST-5 terminals and RAST-1&5 terminals working in the AAL 5 mode and H.320 terminals.
+
+It is important to note that H.310 RAST-1 terminals and H.310 RAST-1&5 terminals can be deployed on (or interface with) both B-ISDN and customer premises ATM networks. However, H.310 RAST-5 terminals can only interface with customer premises networks.
+
+## 12.2 Intercommunication with N-ISDN terminals
+
+For interworking with H.320/H.321 terminals, all RAST terminal types shall support the following modes:
+
+- a) H.261 CIF/QCIF.
+- b) G.711.
+
+Additionally, for interworking with H.320/H.321 terminals, all RAST terminal types shall support the following modes.
+
+- c) H.221/H.242-H.230.
+- d) 1B, 2B and H0 transfer modes.
+- e) Two ATM VCs (for supporting the 2B communication mode with H.320).
+
+NOTE – For the clock synchronization of terminals connected to different types of networks, refer to Annex C/H.321.
+
+## 12.3 Intercommunication with telephony
+
+For further study.
+
+## 12.4 Intercommunication with audiovisual terminals connected to other networks
+
+For further study.
+
+# ANNEX A
+
+## Protocol stack for control channel
+
+This annex defines two protocol stacks for the control channel.
+
+## A.1 General
+
+Figure A.1 shows two protocol stacks for the control channel. Two modes of operation are envisaged. Figure A.1 a) shows the protocol stack when the messages are transported in a separate ATM VC to that used for multimedia data. Figure A.1 b) shows the protocol stack when the messages are transported in the same ATM VC as that used for multimedia data.
+
+The X.224 SDU shall contain a whole number of octets, not to exceed 2048 octets, representing one or more H.245 **MultimediaSystemControlPDU** messages.
+
+![Protocol stack diagram for control channel showing two configurations: a) Separate VC and b) Single VC. Both stacks start with Rec. H.245 at the top. Stack (a) includes X.224 class 0, LAPF (Rec. Q.922), FR-SSCS (Rec. I.365.1), AAL 5, and ATM. Stack (b) includes X.224 class 0, LAPF (Rec. Q.922), Rec. H.222.0/Rec. H.222.1, CS 1/5, AAL 1/5, and ATM. The label 'Rec. X.214' is placed between the two stacks.](c1df61cc3717e878a48e530218403403_img.jpg)
+
+T1604960-98
+
+Protocol stack diagram for control channel showing two configurations: a) Separate VC and b) Single VC. Both stacks start with Rec. H.245 at the top. Stack (a) includes X.224 class 0, LAPF (Rec. Q.922), FR-SSCS (Rec. I.365.1), AAL 5, and ATM. Stack (b) includes X.224 class 0, LAPF (Rec. Q.922), Rec. H.222.0/Rec. H.222.1, CS 1/5, AAL 1/5, and ATM. The label 'Rec. X.214' is placed between the two stacks.
+
+**Figure A.1/H.310 – Protocol stack for control channel**
+
+## A.2 X.214
+
+A connection-mode service shall be used for the transport of MultimediaSystemControl messages as defined in Recommendation X.214.
+
+A single Transport Connection (TC) shall be used for the transport of MultimediaSystemControl messages.
+
+The encoded representation of individual MultimediaSystemControl messages shall be transported in single Transport Service Data Units (TSDUs). The bits produced by the ASN.1 encoding process shall be put into TSDU octets, with the first bit generated going into the Most Significant Bit (MSB) of the octet, and progressing down to the Least Significant Bit (LSB).
+
+## A.3 X.224
+
+X.214 service shall be provided by X.224 class 0.
+
+## A.4 LAPF (Q.922)
+
+Q.922 shall be used to provide a network connection of type A defined in 5.4.3/X.224, that is, a connection with acceptable residual error rate and acceptable rate of signalled errors. This shall be done by use of information (I) frames.
+
+Frame types UI and XID shall not be transmitted. The address field format shall be two octets (10-bit DLCIs). The default values of Q.922 system parameters, k, N200, N201, T.200, T.203, are used for H.310. Values of k, N201 and T.200 can be negotiated in Q.922 data link connection setup. The values of N200 and T.203 need not be negotiated between terminals and may be set locally on each side.
+
+## **A.5 FR-SSCS (I.365.1) and H.222.1**
+
+Both FR-SSCS (see Recommendation I.365.1) and H.222.1 provide octet transmission with structure. The transparency procedure specified in 2.6/Q.922 shall not be used, that is, no zero bits shall be inserted after any sequence of five consecutive 1 bits. No flags shall be present.
+
+### **A.5.1 FR-SSCS (I.365.1)**
+
+FR-SSCS (see Recommendation I.365.1) emulates the Frame Relaying Bearer Service (FRBS) on top of the Common Part Convergence Sublayer (CPCS) of AAL type 5, providing the core service at the DL-CORE-SAP as defined in clause 2/I.365.1. FR-SSCS is used as the DL-CORE sublayer combined with DL-CONTROL sublayer described in clause 4/Q.922. The structure of FR-SSCS-PDUs is exactly the same as the Q.922 frame without flags, zero bit insertion, and FCS.
+
+### **A.5.2 H.222.0 and H.222.1**
+
+Q.922 octets shall be transported in PES packets defined in Recommendation H.222.0 so that the first octet of a PES packet is the first octet of the address field and the last octet of the PES packet is the last octet of the FCS field, as defined in 2.2/Q.922.
+
+# ANNEX B
+
+## Use of DSS 2 signalling by H.310 terminals
+
+## B.1 DSS 2 signalling information elements
+
+The following information elements are required in the SETUP message to establish the following types of connections for H.310 terminals.
+
+**Table B.1/H.310 – DSS 2 signalling information elements**
+
+| Information element              | H.310 Control VC                                        | H.310 RAST A/V VC | H.310 ROT/SOT A/V VC |
+|----------------------------------|---------------------------------------------------------|-------------------|----------------------|
+| Protocol discriminator           | M                                                       | M                 | M                    |
+| Call Reference                   | M                                                       | M                 | M                    |
+| Message type                     | M                                                       | M                 | M                    |
+| Message length                   | M                                                       | M                 | M                    |
+| AAL Parameters                   | M                                                       | M                 | M                    |
+| ATM Traffic descriptor           | M                                                       | M                 | M                    |
+| Broadband bearer capability      | M                                                       | M                 | M                    |
+| Broadband repeat indicator       | CM                                                      | O                 | O                    |
+| Broadband low layer information  | M                                                       | M                 | M                    |
+| Generic Identifier Transport     | M                                                       | M                 | M                    |
+| Broadband High layer information | O                                                       | O                 | O                    |
+| Notification Indicator           | O                                                       | O                 | O                    |
+| Called party number              | M                                                       | M                 | M                    |
+| Called party subaddress          | C                                                       | C                 | C                    |
+| Calling party number             | M                                                       | M                 | M                    |
+| Calling party subaddress         | C                                                       | C                 | C                    |
+| Connection identifier            | O                                                       | O                 | O                    |
+| Extended QoS parameters          | O                                                       | O                 | O                    |
+| End-to-end transit delay         | O                                                       | O                 | O                    |
+| QoS parameter                    | M                                                       | M                 | M                    |
+| Broadband sending complete       | C                                                       | C                 | C                    |
+| Transit network selection        | O                                                       | O                 | O                    |
+| Endpoint reference               | NA                                                      | NA                | NA                   |
+| NA                               | Not Applicable                                          |                   |                      |
+| O                                | Optional                                                |                   |                      |
+| CM                               | Conditionally Mandatory                                 |                   |                      |
+| M                                | Required                                                |                   |                      |
+| C                                | Conditional (if appropriate for the network being used) |                   |                      |
+
+The next subclauses summarize the use of the information elements that are unique to H.310 RAST/ROT/SOT. The elements that are not specifically described here are coded in accordance with the requirements of DSS 2 specification.
+
+**Table B.2/H.310 – DSS 2 signalling information elements specific to H.310 RAST-1 and ROT/SOT-1**
+
+| Information element             | H.310 Control VC                                                                                                                                                    | H.310 RAST-1 A/V VC                                                                                                                                                                                                                                                 | H.310 ROT/SOT-1 A/V VC                                                                                                                                  |
+|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| AAL Parameters                  | AAL Type = AAL 5<br>Forward CPCS SDU size<br>Backward CPCS SDU size<br>SSCS Type = Frame Relay                                                                      | AAL Type = AAL 1<br>Subtype = Video signal transport<br>CBR rate = $n \times 64$<br>Multiplier = As negotiated by H.245<br>Source Clock Frequency Recovery = As negotiated by H.245<br>Error Correction = As negotiated by H.245<br>SDT Block Size = Impl. specific |                                                                                                                                                         |
+| ATM Traffic descriptor          | Forward PCR and Backward PCR = 167 cells per second which corresponds to 64 kbit/s<br>Sustainable Cell Rate = Impl. specific<br>Maximum burst size = Impl. specific | Forward PCR = Implementation specific<br>Backward PCR = Implementation specific<br>(Note 1)                                                                                                                                                                         |                                                                                                                                                         |
+| Broadband bearer capability     | Bearer Class = BCOB-X<br>Broadband Transfer Capability = BTC10<br>User Plane Connection = PtP                                                                       | Bearer Class = BCOB-A<br>Broadband Transfer Capability = CBR<br>Timing Requirements = end-to-end timing required<br>User Plane Connection = PtP                                                                                                                     |                                                                                                                                                         |
+| Broadband repeat indicator      | Set when more than one B-LLI element is present                                                                                                                     |                                                                                                                                                                                                                                                                     |                                                                                                                                                         |
+| Broadband low layer information | User Layer 3 = H.310<br>Terminal type = ROT/SOT/RAST<br>Terminal capability = AAL 1<br>Forward Multiplexing = NO<br>Backward Multiplexing = NO                      | User Layer 3 = H.310<br>Terminal type = RAST<br>Terminal capability = AAL 1<br>Forward Multiplexing = TS<br>Backward Multiplexing = TS                                                                                                                              | User Layer 3 = H.310<br>Terminal type = ROT/SOT<br>Terminal capability = AAL 1<br>Forward Multiplexing = TS<br>Backward Multiplexing = Null<br>(Note 1) |
+| Generic Identifier Transport    |                                                                                                                                                                     | H.310 Correlation ID                                                                                                                                                                                                                                                |                                                                                                                                                         |
+
+NOTE 1 – Forward and Backward are set according to which terminal sends the original SETUP message.  
+NOTE 2 – **Terminal type** and **Terminal capability** in the B-LLI for the additional channels are encoded, but not used at the receiving end. This is applied to the following tables in this annex.
+
+**Table B.3/H.310 – DSS 2 signalling information elements specific to H.310 RAST-5 and ROT/SOT-5**
+
+| Information element             | H.310 Control VC                                                                                                                                                    | H.310 RAST-5 A/V VC                                                                                                                    | H.310 ROT/SOT-5 A/V VC                                                                                                                                  |
+|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| AAL Parameters                  | AAL Type = AAL 5<br>Forward CPCS SDU size<br>Backward CPCS SDU size<br>SSCS Type = Frame Relay                                                                      | AAL Type = AAL 5<br>Forward CPCS SDU size<br>Backward CPCS SDU size<br>SSCS Type = Null                                                |                                                                                                                                                         |
+| ATM Traffic descriptor          | Forward PCR and Backward PCR = 167 cells per second which corresponds to 64 kbit/s<br>Sustainable Cell Rate = Impl. specific<br>Maximum burst size = Impl. specific | Forward PCR = Implementation specific<br>Backward PCR = Implementation specific<br>(Note 1)                                            |                                                                                                                                                         |
+| Broadband bearer capability     | Bearer Class = BCOB-X<br>Broadband Transfer Capability = BTC10<br>User Plane Connection = PtP                                                                       | Bearer Class = BCOB-X<br>Broadband Transfer Capability = CBR<br>User Plane Connection = PtP                                            |                                                                                                                                                         |
+| Broadband repeat indicator      | Set when more than one B-LLI element is present                                                                                                                     |                                                                                                                                        |                                                                                                                                                         |
+| Broadband low layer information | User Layer 3 = H.310<br>Terminal type = ROT/SOT/RAST<br>Terminal capability = AAL 5<br>Forward Multiplexing = NO<br>Backward Multiplexing = NO                      | User Layer 3 = H.310<br>Terminal type = RAST<br>Terminal capability = AAL 5<br>Forward Multiplexing = TS<br>Backward Multiplexing = TS | User Layer 3 = H.310<br>Terminal type = ROT/SOT<br>Terminal capability = AAL 5<br>Forward Multiplexing = TS<br>Backward Multiplexing = Null<br>(Note 1) |
+| Generic Identifier Transport    |                                                                                                                                                                     | H.310 Correlation ID                                                                                                                   |                                                                                                                                                         |
+
+NOTE 1 – Forward and Backward are set according to which terminal sends the original SETUP message.  
+NOTE 2 – **Terminal capability** for RAST-5 terminal shall be set taking both terminal and gateway into account, if the terminal is supported by a gateway.
+
+## B.2 ATM signalling required for the H.310 control VC
+
+The following tables define the ATM signalling information elements for the H.310 control channel. The AAL, Traffic Descriptor and Broadband Bearer Capabilities IEs are defined similarly for other applications.
+
+The control VC Protocol stack can be assumed based on Terminal identification exchanged in B-LLI. The Quality of Service (QoS) parameters shall be coded in accordance with the requirements of the network and are not specifically defined here.
+
+**Table B.4/H.310 – AAL parameters IE**
+
+| IE parameter                         | Value      | Notes                                                              |
+|--------------------------------------|------------|--------------------------------------------------------------------|
+| AAL type                             | AAL 5      |                                                                    |
+| Forward Maximum AAL 5 CPCS SDU size  |            | Value sufficient for transporting H.245 messages up to 2048 octets |
+| Backward Maximum AAL 5 CPCS-SDU size |            | Value sufficient for transporting H.245 messages up to 2048 octets |
+| SSCS Type                            | '00000100' | Frame Relay SSCS                                                   |
+
+**Table B.5/H.310 – ATM Traffic Descriptor IE**
+
+| IE parameter            | Value                                         | Notes                                                               |
+|-------------------------|-----------------------------------------------|---------------------------------------------------------------------|
+| Forward Peak Cell Rate  | Implementation and program selection specific | Set to the Peak Cell Rate value required for the control connection |
+| Backward Peak Cell Rate | Implementation and program selection specific | Set to the Peak Cell Rate value required for the control connection |
+
+**Table B.6/H.310 – Broadband Bearer Capabilities IE**
+
+| IE parameter                        | Value           | Notes                                                         |
+|-------------------------------------|-----------------|---------------------------------------------------------------|
+| Bearer Class                        | BCOB-X          |                                                               |
+| Broadband Transfer Capability       | BTC10 = '01010' | VBR with End-to-End Timing not required<br>(Non-realtime VBR) |
+| User Plane Connection configuration | Point-to-Point  |                                                               |
+
+**Table B.7/H.310 – Broadband Low Layer IE**
+
+| IE parameter                            | Value                                                           | Notes                                                                        |
+|-----------------------------------------|-----------------------------------------------------------------|------------------------------------------------------------------------------|
+| User Information Layer 3 Protocol Field | '01100'                                                         | Rec. H.310                                                                   |
+| Terminal Type                           | '0001' = H.310 ROT<br>'0010' = H.310 SOT<br>'0011' = H.310 RAST | Specify the appropriate terminal type for the expected mode of operation     |
+| Terminal capability                     | '001' = AAL 1 only<br>'010' = AAL 5 only<br>'010' = AAL 1 & 5   | Specify the appropriate terminal capability regarding the supported AAL type |
+| Forward Multiplexing Capability         | '000'                                                           | No multiplex                                                                 |
+| Backward Multiplexing Capability        | '000'                                                           | No multiplex                                                                 |
+
+## **B.3 ATM Signalling Required for RAST-1 A/V VC**
+
+The following tables define the signalling elements required to establish a bidirectional (RAST) audiovisual virtual circuit from a terminal. The QoS parameters shall be coded in accordance with the requirements of the network.
+
+**Table B.8/H.310 – AAL parameters IE**
+
+| IE parameter                    | Value                  | Notes                  |
+|---------------------------------|------------------------|------------------------|
+| AAL type                        | AAL 1                  |                        |
+| Subtype                         | Video signal transport |                        |
+| CBR rate                        | $N \times 64$ kbit/s   |                        |
+| Multiplier                      | m                      | As negotiated by H.245 |
+| Source Clock Frequency Recovery |                        | As negotiated by H.245 |
+| Error Correction Method         |                        | As negotiated by H.245 |
+
+The Peak Cell Rate for the video service component is calculated using the MPEG-2 encoded rate plus AAL 1 overhead and specified as shown in Table B.9. The ATM Traffic Descriptor includes only the user plane information rate for the service components in that one VC.
+
+The video service component PCR may be specified using Cell Loss Priority,  $CLP = 0 + 1$  and  $CLP = 0$  or  $CLP = 0 + 1$ .
+
+**Table B.9/H.310 – ATM Traffic Descriptor IE**
+
+| <b>IE parameter</b>     | <b>Value</b>                                  | <b>Notes</b>                                                             |
+|-------------------------|-----------------------------------------------|--------------------------------------------------------------------------|
+| Forward Peak Cell Rate  | Implementation and program selection specific | Set to the Peak Cell Rate value required for the video service component |
+| Backward Peak Cell Rate | Implementation and program selection specific | Set to the Peak Cell Rate value required for the video service component |
+
+**Table B.10/H.310 – Broadband Bearer Capabilities IE**
+
+| <b>IE parameter</b>                 | <b>Value</b>               | <b>Notes</b> |
+|-------------------------------------|----------------------------|--------------|
+| Bearer Class                        | BCOB-A                     |              |
+| Broadband Transfer Capability       | Constant Bit Rate          |              |
+| Timing Requirements                 | End-to-end timing required |              |
+| Susceptibility to clipping          | Susceptible to clipping    |              |
+| User Plane Connection configuration | Point-to-Point             |              |
+
+**Table B.11/H.310 – Broadband Low Layer IE**
+
+| <b>IE parameter</b>                                                                      | <b>Value</b>        | <b>Notes</b>              |
+|------------------------------------------------------------------------------------------|---------------------|---------------------------|
+| User Information Layer 3 Protocol Field                                                  | '01100'             | Rec. H.310                |
+| Terminal Type                                                                            | '0011' = H.310 RAST | Receive and Send Terminal |
+| Terminal capability                                                                      | '001' = AAL 1 only  |                           |
+| Forward Multiplexing Capability (Note)                                                   | '001'               | Transport Stream          |
+| Backward Multiplexing Capability (Note)                                                  | '001'               | Transport Stream          |
+| NOTE – Program Stream is also an option for Forward and Reverse Multiplexing Capability. |                     |                           |
+
+The Generic Identifier Transport Information Element is a generic parameter that indicates the correspondence of the VC to a certain previously established request carried outside ATM signalling. Table B.12 identifies the parameters of the Generic Identifier Transport IE for use in an H.310 environment.
+
+**Table B.12/H.310 – Generic Identifier Transport IE**
+
+| <b>IE parameter</b>         | <b>Value</b>                       | <b>Notes</b>         |
+|-----------------------------|------------------------------------|----------------------|
+| Identifier Related Standard | '00000010'                         | Rec. H.310           |
+| Resource                    | Identifier for the virtual circuit | H.310 Correlation ID |
+
+## B.4 ATM Signalling Required for H.310 SOT/ROT-1
+
+The following tables define the signalling elements required to establish an audiovisual virtual circuit for a ROT or SOT terminal.
+
+The QoS parameters shall be coded in accordance with the requirements of the network.
+
+**Table B.13/H.310 – AAL parameters IE**
+
+| IE parameter                    | Value                  | Notes                  |
+|---------------------------------|------------------------|------------------------|
+| AAL type                        | AAL 1                  |                        |
+| Subtype                         | Video signal transport |                        |
+| CBR rate                        | $N \times 64$ kbit/s   |                        |
+| Multiplier                      | m                      | As negotiated by H.245 |
+| Source Clock Frequency Recovery |                        | As negotiated by H.245 |
+| Error Correction Method         |                        | As negotiated by H.245 |
+
+The Peak Cell Rate for the video service component is calculated using the MPEG-2 encoded rate plus AAL 1 overhead and specified as shown in Table B.14. The ATM Traffic Descriptor includes only the user plane information rate for the service components in that one VC.
+
+The video service component PCR may be specified using Cell Loss Priority,  $CLP = 0 + 1$  and  $CLP = 0$  or  $CLP = 0 + 1$ .
+
+The Forward and Backward Peak Cell Rates are set according to which terminal sends the original SETUP message.
+
+**Table B.14/H.310 – ATM Traffic Descriptor IE**
+
+| IE parameter            | Value                                         | Notes                                                                    |
+|-------------------------|-----------------------------------------------|--------------------------------------------------------------------------|
+| Forward Peak Cell Rate  | Implementation and program selection specific | Set to the Peak Cell Rate value required for the video service component |
+| Backward Peak Cell Rate | Implementation and program selection specific | Set to the Peak Cell Rate value required for the video service component |
+
+**Table B.15/H.310 – Broadband Bearer Capabilities IE**
+
+| IE parameter                        | Value                      | Notes |
+|-------------------------------------|----------------------------|-------|
+| Bearer Class                        | BCOB-A                     |       |
+| Broadband Transfer Capability       | Constant Bit Rate          |       |
+| Timing Requirements                 | End-to-end timing required |       |
+| Susceptibility to clipping          | Susceptible to clipping    |       |
+| User Plane Connection configuration | Point-to-Point             |       |
+
+The Forward and Backward Multiplexing Capability parameters are set according to which terminal sends the original SETUP message.
+
+**Table B.16/H.310 – Broadband Low Layer IE**
+
+| IE parameter                                                                             | Value                                                                    | Notes      |
+|------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|------------|
+| User Information Layer 3 Protocol Field                                                  | '01100'                                                                  | Rec. H.310 |
+| Terminal Type                                                                            | '0010' = H.310 ROT<br>'0001' = H.310 SOT                                 |            |
+| Terminal capability                                                                      | '001' = AAL 1 only                                                       |            |
+| Forward Multiplexing Capability (Note)                                                   | If ROT then '000' = No multiplex<br>If SOT then '001' = Transport Stream |            |
+| Backward Multiplexing Capability (Note)                                                  | If ROT then '001' = Transport Stream<br>If SOT then '000' = No multiplex |            |
+| NOTE – Program Stream is also an option for Forward and Reverse Multiplexing Capability. |                                                                          |            |
+
+The Generic Identifier Transport Information Element is a generic parameter that indicates the correspondence of the VC to a certain previously established request carried outside ATM signalling. Table B.17 identifies the parameters of the Generic Identifier Transport IE for use in an H.310 environment.
+
+**Table B.17/H.310 – Generic Identifier Transport IE**
+
+| IE parameter                | Value                              | Notes                |
+|-----------------------------|------------------------------------|----------------------|
+| Identifier Related Standard | '00000010'                         | Rec. H.310           |
+| Resource                    | Identifier for the virtual circuit | H.310 Correlation ID |
+
+## B.5 ATM Signalling Required for RAST-5 A/V VC
+
+The following tables define the signalling elements required to establish a bidirectional (RAST) audiovisual virtual circuit from a terminal. The QoS parameters shall be coded in accordance with the requirements of the network.
+
+**Table B.18/H.310 – AAL parameters IE**
+
+| IE parameter                         | Value       | Notes                                                                                              |
+|--------------------------------------|-------------|----------------------------------------------------------------------------------------------------|
+| AAL type                             | AAL 5       |                                                                                                    |
+| Forward Maximum AAL 5 CPCS SDU size  | N*188 bytes | Default value for the video service component in this specification is 376 bytes. N is an integer. |
+| Backward Maximum AAL 5 CPCS-SDU size | N*188 bytes | Default value for the video service component in this specification is 376 bytes. N is an integer. |
+| SSCS Type                            | Null        |                                                                                                    |
+
+The Peak Cell Rate for the video service component is calculated using the MPEG-2 encoded rate plus AAL 5 overhead and specified as shown in Table B.19. The ATM Traffic Descriptor includes only the user plane information rate for the service components in that one VC.
+
+The video service component PCR may be specified using Cell Loss Priority, CLP = 0 + 1 and CLP = 0 or CLP = 0 + 1.
+
+**Table B.19/H.310 – ATM Traffic Descriptor IE**
+
+| IE parameter            | Value                                         | Notes                                                                     |
+|-------------------------|-----------------------------------------------|---------------------------------------------------------------------------|
+| Forward Peak Cell Rate  | Implementation and program selection specific | Set to the Peak Cell Rate value required for the video service component. |
+| Backward Peak Cell Rate | Implementation and program selection specific | Set to the Peak Cell Rate value required for the video service component. |
+
+**Table B.20/H.310 – Broadband Bearer Capabilities IE**
+
+| IE parameter                        | Value             | Notes |
+|-------------------------------------|-------------------|-------|
+| Bearer Class                        | BCOB-X            |       |
+| Broadband Transfer Capability       | Constant Bit Rate |       |
+| User Plane Connection configuration | Point-to-Point    |       |
+
+**Table B.21/H.310 – Broadband Low Layer IE**
+
+| IE parameter                                                                             | Value               | Notes                     |
+|------------------------------------------------------------------------------------------|---------------------|---------------------------|
+| User Information Layer 3 Protocol Field                                                  | '01100'             | Rec. H.310                |
+| Terminal Type                                                                            | '0011' = H.310 RAST | Receive and Send Terminal |
+| Terminal capability                                                                      | '010' = AAL 5 only  |                           |
+| Forward Multiplexing Capability (Note)                                                   | '001'               | Transport Stream          |
+| Backward Multiplexing Capability (Note)                                                  | '001'               | Transport Stream          |
+| NOTE – Program Stream is also an option for Forward and Reverse Multiplexing Capability. |                     |                           |
+
+The Generic Identifier Transport Information Element is a generic parameter that indicates the correspondence of the VC to a certain previously established request carried outside ATM signalling. Table B.22 identifies the parameters of the Generic Identifier Transport IE for use in an H.310 environment.
+
+**Table B.22/H.310 – Generic Identifier Transport IE**
+
+| IE parameter                | Value                              | Notes                |
+|-----------------------------|------------------------------------|----------------------|
+| Identifier Related Standard | '00000010'                         | Rec. H.310           |
+| Resource                    | Identifier for the virtual circuit | H.310 Correlation ID |
+
+## B.6 ATM Signalling Required for H.310 SOT-5
+
+For an H.310 SOT terminal, the Forward and Backwards Maximum AAL 5 CPCS SDU sizes are set according to which terminal sends the original SETUP message. Table B.23 shows the settings if the SOT terminal sends the SETUP message.
+
+**Table B.23/H.310 – AAL type IE**
+
+| IE parameter                         | Value                                                                                       | Notes                                                                                              |
+|--------------------------------------|---------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|
+| AAL type                             | AAL 5                                                                                       |                                                                                                    |
+| Forward Maximum AAL 5 CPCS SDU size  | N*188 bytes                                                                                 | Default value for the video service component in this specification is 376 bytes. N is an integer. |
+| Backward Maximum AAL 5 CPCS-SDU size | 0 bytes if the video service component is unidirectional, otherwise implementation specific |                                                                                                    |
+| SSCS Type                            | '00000000'                                                                                  | Null                                                                                               |
+
+The Peak Cell Rate for the video service component is calculated using the MPEG-2 encoded rate plus the AAL 5 overhead. The ATM Traffic Descriptor includes only the user plane information rate for the service components in that one VC.
+
+The video service component PCR may be specified using Cell Lost Priority CLP = 0 + 1 and CLP = 0 or CLP = 0 + 1.
+
+The Forward and Backward Peak Cell Rates are set according to which terminal sends the original SETUP message. The following tables show the settings if the SOT terminal sends the SETUP message.
+
+**Table B.24/H.310 – ATM Traffic Descriptor**
+
+| IE parameter            | Value                                                                                     | Notes                                                                    |
+|-------------------------|-------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|
+| Forward Peak Cell Rate  | Implementation and program selection specific                                             | Set to the Peak Cell Rate value required for the video service component |
+| Backward Peak Cell Rate | 0 cells/s if video service component is unidirectional, otherwise implementation specific |                                                                          |
+
+**Table B.25/H.310 – Broadband Bearer Capabilities IE**
+
+| IE parameter                        | Value             | Notes |
+|-------------------------------------|-------------------|-------|
+| Bearer Class                        | BCOB-X            |       |
+| Broadband Transfer Capability       | Constant Bit Rate |       |
+| User Plane Connection configuration | Point-to-Point    |       |
+
+**Table B.26/H.310 – Broadband Low Layer IE**
+
+| IE parameter                                                                 | Value              | Notes              |
+|------------------------------------------------------------------------------|--------------------|--------------------|
+| User Information Layer 3 Protocol Field                                      | '01100'            | Rec. H.310         |
+| Terminal Type                                                                | '0010' = H.310 SOT | Send Only Terminal |
+| Terminal capability                                                          | '010' = AAL 5 only |                    |
+| Forward Multiplexing Capability (Note)                                       | '001'              | Transport Stream   |
+| Backward Multiplexing Capability (Note)                                      | '000'              | No multiplex       |
+| NOTE – Program Stream is also an option for Forward Multiplexing Capability. |                    |                    |
+
+The QoS parameters shall be coded in accordance with the requirements of the network.
+
+The Generic Identifier Transport Information Element is a generic parameter that indicates the correspondence of the VC to a certain previously established request carried outside ATM signalling. Table B.27 identifies the parameters of the Generic Identifier Transport IE for use in an H.310 environment.
+
+**Table B.27/H.310 – Generic Identifier Transport IE**
+
+| IE parameter                | Value                              | Notes                |
+|-----------------------------|------------------------------------|----------------------|
+| Identifier Related Standard | '00000010'                         | Rec. H.310           |
+| Resource                    | Identifier for the virtual circuit | H.310 Correlation ID |
+
+## **B.7 ATM Signalling Required for H.310 ROT-5**
+
+The Forward and Backward Maximum AAL 5 CPCS SDU sizes are set according to which terminal sends the original SETUP message. The following table shows the settings if the ROT terminal sends the SETUP message.
+
+**Table B.28/H.310 – AAL parameters IE**
+
+| IE parameter                         | Value                                                                                  | Notes                                                                                              |
+|--------------------------------------|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|
+| AAL type                             | AAL 5                                                                                  |                                                                                                    |
+| Forward Maximum AAL 5 CPCS SDU size  | 0 bytes if video service component is unidirectional otherwise implementation specific |                                                                                                    |
+| Backward Maximum AAL 5 CPCS-SDU size | N*188 bytes                                                                            | Default value for the video service component in this specification is 376 bytes. N is an integer. |
+| SSCS Type                            | Null                                                                                   |                                                                                                    |
+
+The Peak Cell Rate for the video service component is calculated using the MPEG-2 encoded rate plus the AAL 5 overhead. The ATM Traffic Descriptor includes only the user plane information rate for the service components in that one VC.
+
+The video service component Peak Cell Rate may be specified using CLP = 0 + 1 and CLP = 0 or CLP = 0 + 1.
+
+The Forward and Backward Peak Cell Rates are set according to which terminal sends the original SETUP message. The following tables show the settings if the ROT terminal sends the SETUP message.
+
+**Table B.29/H.310 – ATM Traffic Descriptor IE**
+
+| IE parameter            | Value                                                                                     | Notes                                                                    |
+|-------------------------|-------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|
+| Forward Peak Cell Rate  | 0 cells/s if video service component is unidirectional, otherwise implementation specific |                                                                          |
+| Backward Peak Cell Rate | Implementation and program selection specific                                             | Set to the Peak Cell Rate value required for the video service component |
+
+**Table B.30/H.310 – Broadband Bearer Capabilities IE**
+
+| IE parameter                        | Value             | Notes |
+|-------------------------------------|-------------------|-------|
+| Bearer Class                        | BCOB-X            |       |
+| Broadband Transfer Capability       | Constant Bit Rate |       |
+| User Plane Connection configuration | Point-to-Point    |       |
+
+**Table B.31/H.310 – Broadband Low Layer IE**
+
+| IE parameter                                                                 | Value              | Notes                 |
+|------------------------------------------------------------------------------|--------------------|-----------------------|
+| User Information Layer 3 Protocol Field                                      | '01100'            | Rec. H.310            |
+| Terminal Type                                                                | '0001' = H.310 ROT | Receive Only Terminal |
+| Terminal capability                                                          | '010' = AAL 5 only |                       |
+| Forward Multiplexing Capability (Note)                                       | '000'              | No multiplex          |
+| Backward Multiplexing Capability (Note)                                      | '001'              | Transport Stream      |
+| NOTE – Program Stream is also an option for Reverse Multiplexing Capability. |                    |                       |
+
+These QoS parameters shall be coded in accordance with the requirements of the network.
+
+The Generic Identifier Transport Information Element is a generic parameter that indicates the correspondence of the VC to a certain previously established request carried outside ATM signalling. Table B.32 identifies the parameters of the Generic Identifier Transport IE for use in an H.310 environment.
+
+**Table B.32/H.310 – Generic Transport Identifier IE**
+
+| IE parameter                | Value                              | Notes                |
+|-----------------------------|------------------------------------|----------------------|
+| Identifier Related Standard | '00000010'                         | Rec. H.310           |
+| Resource                    | Identifier for the virtual circuit | H.310 Correlation ID |
+
+# ANNEX C
+
+## Procedures for intercommunication between RAST-1 and RAST-5 terminals
+
+## C.1 Introduction
+
+The procedures are defined to meet the following requirements:
+
+- Two terminals are connected directly as far as possible without use of the conversion gateway. If necessary, a minimum number of gateways are used for protocol conversion.
+- To achieve this, H.245 message exchange is used to take advantage of the fact that H.245 is common to all H.310 terminals including its transport method.
+
+- The extended communication procedures should be a superset of the one stipulated for simple direct communications.
+
+For the description of this annex, CPN stands for customer premises ATM network while B-ISDN is the public network. Audiovisual connection is meant to cover audio, video and data.
+
+It is important to note that the terminal connected to a CPN has the knowledge of its associated gateway capability, thus it shall indicate its terminal type in B-LLI according to the combined capability of its own and that of the associated gateway. A RAST-5 terminal, for example, shall indicate "AAL 1 and AAL 5" in B-LLI if it is supported by the AAL 1/AAL 5 conversion gateway. The mechanism for a terminal to obtain the associated gateway capability is not part of this specification; it may be manual, it may be automatic.
+
+## C.2 Two RAST-5 terminals on CPN
+
+This is the case where two terminals both on CPN are connected through B-ISDN as shown in Figure C.1.
+
+![Diagram illustrating communication between two RAST-5 terminals (Terminal A and Terminal B) connected via a B-ISDN network. Both terminals are connected to their respective CPN (Customer Premises Network) via a Gateway (GW). The B-ISDN network is shown as a central oval. Two communication paths are indicated: 'Initial VC for H.245' and 'Additional VC for Audio, Video and Data'. Terminal C (H.310 RAST-1) is also shown connected to the B-ISDN network.](3c04b14104f95eb8f7100f6d497d956e_img.jpg)
+
+The diagram shows three main network components represented by ovals: a CPN on the left, a B-ISDN network in the center, and another CPN on the right. 
+ - On the left CPN, there is a box labeled 'H.310 RAST-5 Terminal A' and a box labeled 'GW' (Gateway). An arrow points from Terminal A to the GW, and another arrow points from the GW into the B-ISDN network.
+ - On the right CPN, there is a box labeled 'H.310 RAST-5 Terminal B' and a box labeled 'GW'. An arrow points from Terminal B to the GW, and another arrow points from the GW into the B-ISDN network.
+ - In the center B-ISDN oval, two horizontal double-headed arrows span across it. The top arrow is labeled 'Initial VC for H.245' and the bottom arrow is labeled 'Additional VC for Audio, Video and Data'. These arrows connect the GW on the left to the GW on the right.
+ - Below the B-ISDN oval, there is a box labeled 'H.310 RAST-1 Terminal C' with an arrow pointing up into the B-ISDN network.
+
+Diagram illustrating communication between two RAST-5 terminals (Terminal A and Terminal B) connected via a B-ISDN network. Both terminals are connected to their respective CPN (Customer Premises Network) via a Gateway (GW). The B-ISDN network is shown as a central oval. Two communication paths are indicated: 'Initial VC for H.245' and 'Additional VC for Audio, Video and Data'. Terminal C (H.310 RAST-1) is also shown connected to the B-ISDN network.
+
+T1604970-98
+
+**Figure C.1/H.310 – Communication between two RAST-5 terminals**
+
+Communication is established as follows:
+
+- 1) Terminal A calls Terminal B and sets up the H.245 control session by indicating its type as AAL 1 and AAL 5 in B-LLI because it is supported by the AAL 1/AAL 5 conversion gateway.
+- 2) H.245 is used to exchange terminal capabilities, including terminal type and the gateway address(es) and facilities. Both terminals indicate that they have their local gateways.
+- 3) According to the H.245 capability exchange, Terminal A infers that both terminals are of the same type (RAST-5), thus no gateway is required.
+- 4) According to the communication mode determination, the calling Terminal A indicates parameters of the additional VC to the called Terminal B by sending NewATMVCIndication message.
+
+- 5) Terminal A sets up the audiovisual connection directly to Terminal B with parameters set in the **NewATMVCIndication** message.
+
+**Table C.1/H.310 – GIT – Terminal A to Terminal B**
+
+| IE parameter                | Code                   | Semantics                                    |
+|-----------------------------|------------------------|----------------------------------------------|
+| Identifier related standard | 00000010               | Rec. H.310                                   |
+| Identifier type             | 00000010               | Resource                                     |
+| Value (2 octets)            | e.g. 00000000 00000000 | H.245 resourceID (the lowest possible value) |
+
+## C.3 RAST-5 Terminal on CPN with RAST-1 Terminal on Public B-ISDN
+
+This is the case where a RAST-5 terminal on CPN communicates with a RAST-1 terminal on public B-ISDN as shown in Figure C.2. There are two subcases depending on which side calls.
+
+![Diagram showing communication between RAST-5 Terminal A on CPN and RAST-1 Terminal C on B-ISDN via a Gateway (GW). Terminal A sends an 'Initial VC for H.245' to Terminal C. Terminal A also sends an 'Additional VC for Audio, Video and Data' to Terminal C via the GW. Terminal B is shown on the right side of the diagram, connected to a CPN and a GW, but not involved in the communication with Terminal C.](4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg)
+
+The diagram illustrates the network architecture for communication between a RAST-5 terminal on a CPN and a RAST-1 terminal on a B-ISDN. On the left, 'H.310 RAST-5 Terminal A' is connected to a 'CPN' circle, which is further connected to a 'GW' (Gateway) box. On the right, 'H.310 RAST-5 Terminal B' is connected to another 'CPN' circle, which is connected to its own 'GW' box. In the center is a large circle labeled 'B-ISDN'. 'H.310 RAST-1 Terminal C' is connected to the 'B-ISDN' circle. An arrow labeled 'Initial VC for H.245' originates from Terminal A and points to Terminal C. Another arrow labeled 'Additional VC for Audio, Video and Data' originates from Terminal A, passes through the first 'GW', enters the 'B-ISDN' circle, and points to Terminal C. A small text label 'T1604980-98' is located in the bottom right corner of the diagram area.
+
+Diagram showing communication between RAST-5 Terminal A on CPN and RAST-1 Terminal C on B-ISDN via a Gateway (GW). Terminal A sends an 'Initial VC for H.245' to Terminal C. Terminal A also sends an 'Additional VC for Audio, Video and Data' to Terminal C via the GW. Terminal B is shown on the right side of the diagram, connected to a CPN and a GW, but not involved in the communication with Terminal C.
+
+**Figure C.2/H.310 – Communication between RAST-5 on CPN and RAST-1 on B-ISDN**
+
+### C.3.1 RAST-5 Terminal on CPN calls RAST-1 Terminal on B-ISDN
+
+- 1) Terminal A calls Terminal C and sets up the H.245 control session.
+- 2) The call is accepted by Terminal C because the remote terminal type indicates AAL 1 and AAL 5 in B-LLI.
+- 3) H.245 is used to exchange terminal capabilities, including terminal type and the gateway address(es) and facilities. Terminal A will indicate that it has a local gateway. Terminal C will not indicate that it has a gateway. Audiovisual communication modes are determined by Terminal A based on its own capabilities and those of the gateway and Terminal C.
+- 4) The calling Terminal A indicates parameters of the additional VC to the called Terminal C by sending **NewATMVCIndication** message.
+
+- 5) Terminal A sets up a concatenated audiovisual connection through the gateway with parameters set in the **NewATMVCIndication** message.
+- 6) The gateway sets up a connection to Terminal C using the next connection ATM address and H.310 Correlation\_ID passed to it in the SETUP message from Terminal A.
+
+Generic Identifier Transport IE shall be coded as in Tables C.2 and C.3.
+
+**Table C.2/H.310 – GIT – Terminal A to GW**
+
+| IE parameter                | Code                   | Semantics                                    |
+|-----------------------------|------------------------|----------------------------------------------|
+| Identifier related standard | 00000010               | Rec. H.310                                   |
+| Identifier type             | 00000010               | Resource                                     |
+| Value (2 octets)            | e.g. 00000000 00000000 | H.245 resourceID (the lowest possible value) |
+| Identifier type             | 00000011               | End Station (to be defined by SG 11)         |
+| Value (up to 20 octets)     | (to be specified)      | ATM address of Terminal C                    |
+
+**Table C.3/H.310 – GIT – GW to Terminal C**
+
+| IE parameter                | Code                   | Semantics                                    |
+|-----------------------------|------------------------|----------------------------------------------|
+| Identifier related standard | 00000010               | Rec. H.310                                   |
+| Identifier type             | 00000010               | Resource                                     |
+| Value (2 octets)            | e.g. 00000000 00000000 | H.245 resourceID (the lowest possible value) |
+
+### **C.3.2 RAST-1 Terminal on B-ISDN calls RAST-5 Terminal on CPN**
+
+- 1) Terminal C calls Terminal A and sets up the H.245 control session.
+- 2) The call is accepted by Terminal A based on the knowledge of its associated gateway even though the remote terminal type indicates AAL 1 in B-LLI.
+- 3) H.245 is used to exchange terminal capabilities, including terminal type and the gateway address(es) and facilities. Terminal A will indicate that it has a local gateway. Terminal C will not indicate that it has a gateway.
+- 4) Audiovisual communication modes are determined by Terminal C based on its own capabilities and those of the gateway and Terminal A.
+- 5) The calling Terminal C indicates parameters of the additional VC to the called Terminal A by sending **NewATMVCIndication** message.
+- 6) Terminal C sets up a concatenated audiovisual connection through the gateway identified by Terminal A with parameters set in the **NewATMVCIndication** message.
+- 7) The gateway sets up a connection to Terminal A using the next connection ATM Address and H.310 Correlation\_ID passed to it in the SETUP message from Terminal C.
+
+Generic Identifier Transport IE shall be coded as in Tables C.4 and C.5.
+
+**Table C.4/H.310 – GIT – Terminal C to GW**
+
+| IE parameter                | Code                   | Semantics                                    |
+|-----------------------------|------------------------|----------------------------------------------|
+| Identifier related standard | 00000010               | Rec. H.310                                   |
+| Identifier type             | 00000010               | Resource                                     |
+| Value (2 octets)            | e.g. 00000000 00000000 | H.245 resourceID (the lowest possible value) |
+| Identifier type             | 00000011               | End Station (to be defined by SG 11)         |
+| Value (up to 20 octets)     | (to be specified)      | ATM address of Terminal A                    |
+
+**Table C.5/H.310 – GIT – GW to Terminal A**
+
+| IE parameter                | Code                   | Semantics                                    |
+|-----------------------------|------------------------|----------------------------------------------|
+| Identifier related standard | 00000010               | Rec. H.310                                   |
+| Identifier type             | 00000010               | Resource                                     |
+| Value (2 octets)            | e.g. 00000000 00000000 | H.245 resourceID (the lowest possible value) |
+
+## C.4 RAST-5 Terminal on CPN with RAST-1 Terminal on CPN
+
+This is the case where a RAST-5 terminal on CPN communicates with a RAST-1 terminal on CPN through public B-ISDN as shown in Figure C.3. The procedures are identical to those defined in C.3 because RAST-1 terminals have no associated gateways.
+
+![Diagram showing communication between RAST-5 Terminal A and RAST-1 Terminal D via CPN and B-ISDN. Terminal A connects to a CPN, which connects to a Gateway (GW). The GW connects to a B-ISDN. The B-ISDN connects to another CPN, which connects to another Gateway (GW). The second GW connects to Terminal D. A direct line labeled 'Initial VC for H.245' connects Terminal A to Terminal D. A line labeled 'Additional VC for Audio, Video and Data' connects Terminal A to the first GW, then through the B-ISDN to the second GW, and finally to Terminal D. Terminal C is shown below the B-ISDN.](dd6c544ab685b25dd17f59456efcfbfc_img.jpg)
+
+The diagram illustrates a network topology for H.310 communication. On the left, an 'H.310 RAST-5 Terminal A' is connected to a 'CPN' (Packet Switched Network). This CPN is connected to a 'GW' (Gateway). The 'GW' is connected to a central 'B-ISDN' (Integrated Services Digital Network). The 'B-ISDN' is connected to another 'CPN', which is in turn connected to another 'GW'. This second 'GW' is connected to an 'H.310 RAST-1 Terminal D'. A direct horizontal line labeled 'Initial VC for H.245' connects Terminal A and Terminal D. A line labeled 'Additional VC for Audio, Video and Data' originates from Terminal A, goes to the first 'GW', then through the 'B-ISDN' to the second 'GW', and finally to Terminal D. Below the 'B-ISDN', there is a box labeled 'H.310 RAST-1 Terminal C' which is not connected to any network elements in this diagram.
+
+Diagram showing communication between RAST-5 Terminal A and RAST-1 Terminal D via CPN and B-ISDN. Terminal A connects to a CPN, which connects to a Gateway (GW). The GW connects to a B-ISDN. The B-ISDN connects to another CPN, which connects to another Gateway (GW). The second GW connects to Terminal D. A direct line labeled 'Initial VC for H.245' connects Terminal A to Terminal D. A line labeled 'Additional VC for Audio, Video and Data' connects Terminal A to the first GW, then through the B-ISDN to the second GW, and finally to Terminal D. Terminal C is shown below the B-ISDN.
+
+T1604990-98
+
+**Figure C.3/H.310 – Communication between RAST-5 on CPN and RAST-1 on CPN**
+
+# APPENDIX I
+
+## Bit and byte order
+
+This appendix is supplied as a summary of bit and octet order in this Recommendation, including the elements specified in Recommendations H.261, H.262, H.263, G.711, G.722, G.723.1, G.728, G.729, ISO/IEC 11172 audio, ISO/IEC 13818 audio, Recommendations H.245, H.222.0 and H.222.1. In case of any discrepancy, the normative text of the various Recommendations shall take precedence over this appendix. H.261, H.262, H.263, G.711, G.722, G.723.1, G.728, G.729, ISO/IEC 11172 audio, ISO/IEC 13818 audio, H.245, H.222.0 and H.222.1 each produce a sequence of bits. Within this sequence of bits there are fields of various lengths, in some cases aligned with octet boundaries. In the case of H.261, H.262, H.263, G.711, G.722, G.723.1, G.728, G.729, ISO/IEC 11172 audio, ISO/IEC 13818 audio, H.245, H.222.0 and H.222.1 these fields are ordered Most Significant Bit (MSB) first. Figure I.1 illustrates this, with "M" indicating the MSB of each field and "L" indicating the Least Significant Bit (LSB) of each field.
+
+![Diagram illustrating bit and byte order. It shows a sequence of bits starting with 'First' and ending with 'Last'. The sequence is divided into four octets. Each octet contains two bits: the first bit is labeled 'M' (Most Significant Bit) and the second bit is labeled 'L' (Least Significant Bit). The sequence of bits is: M L M L M L M L.](fcc757566216206ceddbd6c775e8db02_img.jpg)
+
+|       |   |   |   |   |   |   |   |   |      |
+|-------|---|---|---|---|---|---|---|---|------|
+| First | M | L | M | L | M | L | M | L | Last |
+|-------|---|---|---|---|---|---|---|---|------|
+
+Diagram illustrating bit and byte order. It shows a sequence of bits starting with 'First' and ending with 'Last'. The sequence is divided into four octets. Each octet contains two bits: the first bit is labeled 'M' (Most Significant Bit) and the second bit is labeled 'L' (Least Significant Bit). The sequence of bits is: M L M L M L M L.
+
+T1521660-96
+
+**Figure I.1/H.310 – Output from H.261, H.262, G.711, G.722, G.723.1, G.728, G.729, ISO/IEC 11172 audio, ISO/IEC 13818 audio, H.245, H.222.0, H.222.1**
+
+# APPENDIX II
+
+## H.310 CorrelationID
+
+This appendix is for clarifying the use of the H.310 CorrelationID and its relationship to the H.245 resourceID.
+
+When multiple VCs are involved in an H.310 communication, H.245 needs to be able to indicate a particular logical channel in a particular VC. Conventions are necessary for the:
+
+- association of the multiple VCs originated at a particular terminal;
+- identification of each VC.
+
+Since H.310 currently assumes that a single session exists between any two instances of H.310, the association of the multiple VCs can be uniquely identified by the Calling party number/Called party number and Calling party subaddress/Called party subaddress in the Q.2931 SETUP message. The identification of each VC is accomplished by using the H.245 resourceID (2 bytes). This is depicted in Figure II.1.
+
+![Diagram of a single session case showing two terminals, A and C, connected to a central terminal B. Terminal A has three horizontal lines (channels) labeled A, B, and C. Terminal C also has three horizontal lines labeled A, B, and C. These lines connect to terminal B. Above the lines from A and C, the text 'Correlation ID' is present, with sub-labels A, B, and C. A double-headed arrow between the lines from A and C is labeled 'Differentiated by calling/called party number pairs'. The diagram is labeled T1605000-98 at the bottom right.](1b23b78336d8bd286c653cbdb38428dd_img.jpg)
+
+Diagram of a single session case showing two terminals, A and C, connected to a central terminal B. Terminal A has three horizontal lines (channels) labeled A, B, and C. Terminal C also has three horizontal lines labeled A, B, and C. These lines connect to terminal B. Above the lines from A and C, the text 'Correlation ID' is present, with sub-labels A, B, and C. A double-headed arrow between the lines from A and C is labeled 'Differentiated by calling/called party number pairs'. The diagram is labeled T1605000-98 at the bottom right.
+
+**Figure II.1/H.310 – Identification of VCs in single session case**
+
+To prepare for the eventual possibility that multiple H.310 sessions will exist between two terminals, as shown in Figure II.2, the correlationID has been defined as follows:
+
+correlationID =        session ID                                ; Identification of a session  
+                              +        resource ID (2 bytes) ; Identification of a logical channel
+
+![Diagram of a multi-session case showing two terminals, A and B. Terminal A has two groups of three horizontal lines. The top group is labeled 'Session 1' and the bottom group is labeled 'Session 2'. Each group has lines labeled A, B, and C. Above each group, the text 'Correlation ID' is present, with sub-labels A, B, and C. The lines connect to terminal B. The diagram is labeled T1605010-98 at the bottom right.](dfafe39c233a62ec8ebd71e42992c14d_img.jpg)
+
+Diagram of a multi-session case showing two terminals, A and B. Terminal A has two groups of three horizontal lines. The top group is labeled 'Session 1' and the bottom group is labeled 'Session 2'. Each group has lines labeled A, B, and C. Above each group, the text 'Correlation ID' is present, with sub-labels A, B, and C. The lines connect to terminal B. The diagram is labeled T1605010-98 at the bottom right.
+
+**Figure II.2/H.310 – Identification of VCs in multi-session case**
+
+However, the current H.310 specification does not assume the multi-session case so the resourceID is the only valid element in the correlation ID for the moment.
+
+
+
+# ITU-T RECOMMENDATIONS SERIES
+
+|                 |                                                                                                                                |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of the 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                                                                   |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                      |
+| Series I        | Integrated services digital network                                                                                            |
+| Series J        | 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                                                                                              |
+| Series Z        | Programming languages                                                                                                          |
\ No newline at end of file
diff --git a/marked/H/T-REC-H.322-199603-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.322-199603-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fa1d67ece5eaed98bf56a079d462c117a609e409
--- /dev/null
+++ b/marked/H/T-REC-H.322-199603-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bced574df39af174a9bb3635f44ee4f00da8580db6e7f06454c84fb654bc8e8d
+size 8235
diff --git a/marked/H/T-REC-H.322-199603-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg b/marked/H/T-REC-H.322-199603-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9284a0c726b042e1ba028c57d70626b2bf959362
--- /dev/null
+++ b/marked/H/T-REC-H.322-199603-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:38937196e0c22de6bac4092230d984f47c56de3ec5a346e6963c4c3328a6d295
+size 100959
diff --git a/marked/H/T-REC-H.322-199603-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/H/T-REC-H.322-199603-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..81c89e9da47bb1d8234af72ab111af298bc56442
--- /dev/null
+++ b/marked/H/T-REC-H.322-199603-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fb0fc04f3b48cad382525664af63a810eed09a9f306f80db3d1bf1d05cb6a278
+size 38742
diff --git a/marked/H/T-REC-H.322-199603-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg b/marked/H/T-REC-H.322-199603-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..661be19551c0e4d527f4e63e450199ab260a8821
--- /dev/null
+++ b/marked/H/T-REC-H.322-199603-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:35db8d04752539e87da84e48d2a0a4a9d5b4d343acf6ecc1ad7342c02ef9f3f8
+size 16414
diff --git a/marked/H/T-REC-H.322-199603-I_PDF-E/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/H/T-REC-H.322-199603-I_PDF-E/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f8422525a589d83191ab1b4cb84da02dbf7465c1
--- /dev/null
+++ b/marked/H/T-REC-H.322-199603-I_PDF-E/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b287426be19c25ece0c85b8ebeb17b18dfae781a8b21320f5151344b5bf3823b
+size 83753
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/070352b751dd0711b8ac6ddfa6df1d98_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/070352b751dd0711b8ac6ddfa6df1d98_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1e533137a1d101c870bf1b03e74df971ab5a1df5
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/070352b751dd0711b8ac6ddfa6df1d98_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6a2df3fce42c0b1071575153bc5dc39df54976bdec12a10fa0f9ec3a5a0b8a5f
+size 51440
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bf911210e02751ed55990a8f4b329a97623d5681
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4095dfab7abaa81393b70c9b244333575aab4cf7e5ff3d95af3791410fab3c56
+size 8233
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/107da2e3495b2f24352c9e3b26ec4841_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/107da2e3495b2f24352c9e3b26ec4841_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8b91950e4a68860dbc369cec4997546130cc2c4f
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/107da2e3495b2f24352c9e3b26ec4841_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cfeaed86033d9ea8bdaca847d53ca1c17ff7dcd252bd45fe31d861bebfa35e2f
+size 23271
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..76273765faed4b983f610e16556018e87749191e
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f9253ac37ae05f460cda0af079ec95f8c46811e96d7614ddfe815af8979d6545
+size 3640
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..61b70017eca7d13379ae66663ed6dbdce15ec4b0
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b5003c92f9c0df652523e08148cd880628c9aba0e31a617f7011490203af793d
+size 30829
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/487c58c79e44e6cf98b6368b6667b9c6_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/487c58c79e44e6cf98b6368b6667b9c6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5a2e3a1420807643980d857edce623f7bc77947b
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/487c58c79e44e6cf98b6368b6667b9c6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f126f54288cb5db75c7ce49287e53d251c932f502ebb4d30e0e196b4ec5f03de
+size 49437
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a62e814fbd4abb6cd1f95084158b542e6e0d4c99
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a513533160116535bbb5460a7fca04bf5e5df1d7b72449fd320e8a3ab35935a1
+size 11332
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/50214d232017279410e9c9db8eb75119_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/50214d232017279410e9c9db8eb75119_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2b5538ac2f0bc0c85e677d3574279973dbf08ee0
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/50214d232017279410e9c9db8eb75119_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:36525c36333e3b5b46ef6cb31c9ad26cacea1ef286cf4fab71f548f2ddc97766
+size 13444
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/572cf014db14c8234f91c07d5a5a28c6_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/572cf014db14c8234f91c07d5a5a28c6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e653be74d950bc490f608faf478d1ae340fe58ee
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/572cf014db14c8234f91c07d5a5a28c6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1dc918d474a02d87fa309b24f333e38d27f88b5bc0b5382489fb1cc1f8228654
+size 16098
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/59121d561a4158609b4c354b9ffd0605_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/59121d561a4158609b4c354b9ffd0605_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0dd978b03f403ad28b8f2a51fa4718a6bc3040a4
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/59121d561a4158609b4c354b9ffd0605_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1d5a4e0f820edc51a160445c961b9c2224834a9e5a5f1beaaacac66fd270d8f
+size 98222
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0fa3eb8060ed4474f4d7088af4bea20d39bf85a8
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4b7e1e121eff18253e4291a0d1776fb530461db857c0599dffb5e6972ce6375f
+size 14702
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ee8e36b9f2601be3f5824122305fb47c38c6e50e
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9002d8d794ae8e988fd6671a88e8d5d1666203864ff66a782723f36fd56a7533
+size 16493
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/6be06b7dc72bb42afcb3465394667c3b_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/6be06b7dc72bb42afcb3465394667c3b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0cfa60b958954bd57cd0455f54c627687f0a68f0
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/6be06b7dc72bb42afcb3465394667c3b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d114a1ddb33a2a78b62cc352e02c59466c3e09c3dec7191f59781a2f0a2d6630
+size 32522
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dd33289512838bd2afbc8c6cccf3da2388e40e60
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:75efc7726d413bece828892a87b5afbb338e910252d198b7d0e0db8795a0423a
+size 37381
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e28d70a65f94d15d6788115ef7e047d76f8fec2b
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b17ad68fe21b178235cc38f96488ffa20143d58e6852c75516d4028781fd715b
+size 11058
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/789ee0a267b24f34bd1f45313e86c9a4_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/789ee0a267b24f34bd1f45313e86c9a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6a5a5a9ff4da4e80ccdc888d00575f96b0dc8182
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/789ee0a267b24f34bd1f45313e86c9a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:840545f209818a0d54c6ada2a3464fb318b20ecd983905e21377b555e1f543ca
+size 39148
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/7be79849b00ccd5e7220d808251b1258_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/7be79849b00ccd5e7220d808251b1258_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6b8ebf28dea534debe2120fc58490d1dca0f4df1
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/7be79849b00ccd5e7220d808251b1258_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9a176422a2218b92a7fa294a01f56978c10d7a3a79ff66bd7aaf7671e31bcf4c
+size 21436
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/8ab30dbff406204a68c59ae7c1b77413_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/8ab30dbff406204a68c59ae7c1b77413_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..174d7dde63bc85042f61b7906880b082dcea8b25
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/8ab30dbff406204a68c59ae7c1b77413_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f4cc68e94a5f112f3ddcf3bf70df21607dcd18ad4ffb3c07f7ab398fe2bbab1a
+size 13104
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/8c880d6b715587bd710a9ba8414469b1_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/8c880d6b715587bd710a9ba8414469b1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2962086429863440841203bde868f260844b247c
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/8c880d6b715587bd710a9ba8414469b1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:68612a14915581032879092dc44cbc1c3c0db432cc0f1a35d7303df492c239a2
+size 30178
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/9527d5a8f0830aff6b77bf256be0bc9c_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/9527d5a8f0830aff6b77bf256be0bc9c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1974158ecb8ab613e2dd1884c0177ea734460ea3
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/9527d5a8f0830aff6b77bf256be0bc9c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a2853b2ea3ce73cdb2c15ad0bb376fcb0c0e4dbb291e23f7354eb265c6051671
+size 40259
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d1089ebae30889c2dab3064130a3a5d20f30bcb4
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:adaa199f59ffad69d9ba9e5a82969b816c7ff4033574046f696d52dc7d0f30ab
+size 126560
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/9c80cf99954eb0142f694456d39fae4b_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/9c80cf99954eb0142f694456d39fae4b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3834f7a9e24de9caf6ab00a8d0ea6fa64e775708
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/9c80cf99954eb0142f694456d39fae4b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f048891abe89881a9d08f59fa667167ca7e4f58a05cc09763f8b7abd34e1c962
+size 142085
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/a634891d16b60b21df90a35c2af72c67_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/a634891d16b60b21df90a35c2af72c67_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2310531dbc3f10510d378539e51d6a90ce2cd092
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/a634891d16b60b21df90a35c2af72c67_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e037a300a89def360aa3bf6ce271bcdf394a90808e21f11d725124094b64b1e1
+size 16580
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/aa39f51ba214496042ee3e2ce4ecee80_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/aa39f51ba214496042ee3e2ce4ecee80_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f5ef878d77391219b80ff1e3fb228feac8bda24e
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/aa39f51ba214496042ee3e2ce4ecee80_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2a4ced8fac75c2e242b9fac208ed8b9c5ff462f73f948bcaf77644104bc92714
+size 10955
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/abeba89144744fac6a1571aa9f94889e_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/abeba89144744fac6a1571aa9f94889e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cbe044d83478258ce2609c7c508c5664746d1a7f
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/abeba89144744fac6a1571aa9f94889e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dd4b83d5bd99ca89bab36aa7dc49a454b5a81f66a7170c773df75c0fecb2e7d8
+size 98564
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/aed5b156b9b0fff9167baba88e5fdcfc_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/aed5b156b9b0fff9167baba88e5fdcfc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0d8f99aac950d05a97bd2f07768f8705327d9947
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/aed5b156b9b0fff9167baba88e5fdcfc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:82ddef91474bdac1bbd477f498dec569fe7e596a97e6ddb7fbf561feb4e4bf50
+size 74520
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a345c2bf17d4df8dff5c9eff1f331a8fa9818815
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5e6cef41d1f45df03a32aaab5c7e88011c45de1e39cb540088b4869cd0282d7f
+size 84112
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/b3d488012fdceacab867cf24c5efef05_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/b3d488012fdceacab867cf24c5efef05_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0a04cf0fa44f929d2e00237f4c03c13c09530c98
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/b3d488012fdceacab867cf24c5efef05_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:72c835ecc4fbff4fcf3dd0a5a665da1a99104ba7e009f7e98702230827848ba2
+size 61731
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/b8d855a06aad434aeafa2739bf62e7de_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/b8d855a06aad434aeafa2739bf62e7de_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..17d519aefeb8418d3809ccb1b572c241107a8263
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/b8d855a06aad434aeafa2739bf62e7de_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:58bff8507f3d19f9a6d4c699e57e05e03bf0781aeafe95b43e78b52d72cb5d1e
+size 57659
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4c872fa2e311456e56dbe1cb15fe17d9e0c87053
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aefa17f79139a2b87e9e4b0cdbfe9f8f22f7426c574f1355446046993b176b69
+size 21004
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6e6bec5798114f5bfb092d7eced3195edf724562
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:27f9f0fb8a93ad145a1bdb1b985e3b6cfe3185ece90a4dad38d3c836f095a663
+size 8253
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/d8698aacaeead6dfed9a1e448670a2e4_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/d8698aacaeead6dfed9a1e448670a2e4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b9ee73ad2593ef09bd2c4bb0eb975a4bde2b4e79
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/d8698aacaeead6dfed9a1e448670a2e4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b78c5560347e46aff87f29eb586ea573523c27e0bf14a75fa79ce8fb15908de2
+size 25779
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/e151d3468319b81f042ca232c4d82e4b_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/e151d3468319b81f042ca232c4d82e4b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1e6d82eac3d9c5960b4dfd8c5857e439ff6ad62f
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/e151d3468319b81f042ca232c4d82e4b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:871769a97ebe3970485e173deac565d4827bcbdd871041a4490d40918eea50ea
+size 15234
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8bcd7dac67a5e7c65cbb97a1a6f6faabc303807e
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:78b7457380471d3b2a5f52e2d92dab2a76b7634a8e96f4029b936d5bc5ed505b
+size 31085
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/f23879f003c58b57f690e2dc6c95816a_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/f23879f003c58b57f690e2dc6c95816a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..11d8620eb12b07fd1e6a0419032a7aec6b755171
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/f23879f003c58b57f690e2dc6c95816a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:10c1ab1e2dcde97ad50aec1a062569356409d0f03a397f2bf75f65253ff6a363
+size 31232
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/f5deee2f3301ee351c4008283ffafbb3_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/f5deee2f3301ee351c4008283ffafbb3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..14dc7be0dedc9bd03b55263a9d5651c4ddae05a9
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/f5deee2f3301ee351c4008283ffafbb3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0dc89d61384a1c670e9f881edbb127368b176f18da8dea3b50c00c02f684324b
+size 14792
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/fe7304192caf64cda93b580c5e7e5c06_img.jpg b/marked/H/T-REC-H.324-200904-I_PDF-E/fe7304192caf64cda93b580c5e7e5c06_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ae5f6d6dcf554128834e6d0ce06f11193cbba01a
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/fe7304192caf64cda93b580c5e7e5c06_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1ed6871438097960c595a9dace2e0b5fd6105325fa71f8bceb9d81a6c427f9cf
+size 18280
diff --git a/marked/H/T-REC-H.324-200904-I_PDF-E/raw.md b/marked/H/T-REC-H.324-200904-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..0580d7984fb324b331a6622e3bc302143d3dbaae
--- /dev/null
+++ b/marked/H/T-REC-H.324-200904-I_PDF-E/raw.md
@@ -0,0 +1,4017 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.324**
+
+(04/2009)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Systems and  
+terminal equipment for audiovisual services
+
+---
+
+**Terminal for low bit-rate multimedia  
+communication**
+
+Recommendation ITU-T H.324
+
+# 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        |
+| <b>Systems and terminal equipment for audiovisual services</b>                | <b>H.300–H.349</b> |
+| 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.324
+
+## Terminal for low bit-rate multimedia communication
+
+## Summary
+
+Recommendation ITU-T H.324 describes terminals for low bit-rate multimedia communication, utilizing ITU-T V.34 modems operating over the general switched telephone network (GSTN), I.400-series user-network interface for integrated services digital network (ISDN) or an appropriate wireless interface for mobile networks. ITU-T H.324 terminals may carry real-time voice, data and video, or any combination, including videotelephony.
+
+ITU-T H.324 terminals may be integrated into personal computers or implemented in stand-alone devices such as videotelephones. Support for each media type (voice, data, video) is optional, but if supported, the ability to use a specified common mode of operation is required, so that all terminals supporting that media type can interwork. This Recommendation allows more than one channel of each type to be in use. Other Recommendations in this series include Recommendation ITU-T H.223 (multiplex), Recommendation ITU-T H.245 (control), Recommendation ITU-T H.263 (video codec) and Recommendation ITU-T G.723.1 (audio codec).
+
+This Recommendation makes use of the logical channel signalling procedures of Recommendation ITU-T H.245, in which the content of each logical channel is described when the channel is opened. Procedures are provided for expression of receiver and transmitter capabilities, so transmissions are limited to what receivers can decode, and so that receivers may request a particular desired mode from transmitters. Since the procedures of this Recommendation are also planned for use by Recommendation ITU-T H.310 for ATM networks, and Recommendation ITU-T H.323 for non-guaranteed bandwidth LANs, interworking with these systems should be straightforward.
+
+ITU-T H.324 terminals may be used in multipoint configurations through multipoint control units (MCUs), and may interwork with ITU-T H.320 terminals on the ISDN, as well as with terminals on wireless networks.
+
+Annex A defines the data protocol stack for use with the ITU-T H.324 control channel.
+
+Annex B defines high-level data link control (HDLC) frame structure transparency for asynchronous transmission.
+
+Annex C defines the use of ITU-T H.324 terminals in error-prone transmission environments ("also referred to elsewhere as ITU-T H.324/M").
+
+Annex D defines the use of ITU-T H.324 terminals on ISDN circuits ("also referred to elsewhere as ITU-T H.324/I").
+
+Annex E defines timer T401 initialization for operation over geostationary-satellite channels.
+
+Annex F supports multilink operation on the GSTN and ISDN.
+
+Annex G defines the use of ISO/IEC 14496-1 ("MPEG-4 systems") generic capabilities in ITU-T H.324 terminals.
+
+Annex H supports multilink operation on error-prone mobile networks.
+
+Annex I defines the use of HTTP in ITU-T H.324 terminals, enabling non-conversational services with a user interface through web-like menus.
+
+Annex J summarizes the OIDs defined in this Recommendation and defines ITU-T H.324 generic capabilities which are used in ITU-T H.245 signalling-based systems.
+
+Annex K defines the media-oriented negotiation acceleration (MONA) procedure, which allows media channels to be established in a fast and flexible manner.
+
+Annex L defines procedures to establish and carry text conversation sessions in the ITU-T H.324 multimedia environment.
+
+Annex M defines the nature of ITU-T H.245 messages used by ITU-T H.324 endpoints.
+
+This revised version of this Recommendation introduces a number of enhancements and clarifications to the previous version, primarily the introductions of Annex K (MONA), Annex L (text conversation) and Annex M (ITU-T H.245 messages).
+
+## Source
+
+Recommendation ITU-T H.324 was approved on 29 April 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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  |
+| 1.1 | Block diagram and functional elements .....                           | 1  |
+| 1.2 | System elements outside the scope of this Recommendation .....        | 2  |
+| 1.3 | Functional elements covered by this Recommendation .....              | 2  |
+| 2   | References.....                                                       | 3  |
+| 2.1 | Normative references.....                                             | 3  |
+| 2.2 | Informative references.....                                           | 5  |
+| 3   | Definitions .....                                                     | 6  |
+| 4   | Abbreviations and acronyms .....                                      | 7  |
+| 5   | Conventions .....                                                     | 8  |
+| 6   | Functional requirements .....                                         | 8  |
+| 6.1 | Required elements .....                                               | 8  |
+| 6.2 | Information streams.....                                              | 9  |
+| 6.3 | Modem.....                                                            | 9  |
+| 6.4 | Multiplex .....                                                       | 9  |
+| 6.5 | Control channel .....                                                 | 11 |
+| 6.6 | Video channels .....                                                  | 14 |
+| 6.7 | Audio channels .....                                                  | 17 |
+| 6.8 | Data channels.....                                                    | 18 |
+| 7   | Terminal procedures .....                                             | 23 |
+| 7.1 | Phase A – Call set-up of voiceband channel .....                      | 23 |
+| 7.2 | Phase B – Initial analogue telephony communication .....              | 24 |
+| 7.3 | Phase C – Establishment of digital communication, modem training..... | 24 |
+| 7.4 | Phase D – Initialization .....                                        | 25 |
+| 7.5 | Phase E – Communication.....                                          | 25 |
+| 7.6 | Phase F – End of session .....                                        | 26 |
+| 7.7 | Phase G – Supplementary services and call clearing .....              | 26 |
+| 8   | Interoperation with other terminals .....                             | 27 |
+| 8.1 | Speech only terminals.....                                            | 27 |
+| 8.2 | ITU-T H.320 multimedia telephone terminals over the ISDN.....         | 27 |
+| 8.3 | Multimedia telephone terminals over mobile radio.....                 | 27 |
+| 9   | Optional enhancements.....                                            | 27 |
+| 9.1 | Data facilities.....                                                  | 27 |
+| 9.2 | Encryption .....                                                      | 28 |
+| 9.3 | Multilink.....                                                        | 30 |
+
+|         | Page                                                                                  |    |
+|---------|---------------------------------------------------------------------------------------|----|
+| 10      | Multipoint considerations .....                                                       | 30 |
+| 10.1    | Establishment of common mode .....                                                    | 30 |
+| 10.2    | Multipoint rate matching .....                                                        | 30 |
+| 10.3    | Multipoint lip synchronization .....                                                  | 30 |
+| 10.4    | Multipoint encryption .....                                                           | 31 |
+| 10.5    | Cascaded MCU operation.....                                                           | 31 |
+| 11      | Maintenance.....                                                                      | 31 |
+| 11.1    | Loopbacks for maintenance purposes .....                                              | 31 |
+| Annex A | – Protocol stack for control channel.....                                             | 33 |
+| A.1     | General .....                                                                         | 33 |
+| A.2     | SRP mode .....                                                                        | 34 |
+| A.3     | LAPM/ITU-T V.42 mode.....                                                             | 36 |
+| A.4     | WNSRP control frame signalling on the control channel .....                           | 36 |
+| Annex B | – HDLC frame structure transparency for asynchronous transmission.....                | 40 |
+| Annex C | – Multimedia telephone terminals over error-prone channels.....                       | 41 |
+| C.1     | Abstract.....                                                                         | 41 |
+| C.2     | General .....                                                                         | 41 |
+| C.3     | Changes to procedures.....                                                            | 42 |
+| C.4     | Interworking .....                                                                    | 42 |
+| C.5     | Terminal procedures.....                                                              | 42 |
+| C.6     | Initialization of multiplex level at the start of a session.....                      | 42 |
+| C.7     | Dynamic change of level or option during session .....                                | 44 |
+| C.8     | Control channel definition for mobile terminals .....                                 | 45 |
+| Annex D | – Operation on ISDN circuits (H.324/I) .....                                          | 49 |
+| D.1     | Scope .....                                                                           | 49 |
+| D.2     | References .....                                                                      | 49 |
+| D.3     | Definitions .....                                                                     | 49 |
+| D.4     | Functional requirements .....                                                         | 49 |
+| D.5     | Terminal procedures.....                                                              | 51 |
+| Annex E | – Timer T401 initialization for operation over geostationary-satellite channels ..... | 54 |
+| E.1     | Introduction .....                                                                    | 54 |
+| E.2     | Determination of timer value.....                                                     | 54 |
+| E.3     | Timer tuning procedure .....                                                          | 55 |
+| Annex F | – Multilink operation.....                                                            | 56 |
+| F.1     | Scope .....                                                                           | 56 |
+| F.2     | References .....                                                                      | 56 |
+| F.3     | Functional requirements .....                                                         | 56 |
+| F.4     | Overview .....                                                                        | 56 |
+| F.5     | Procedures .....                                                                      | 56 |
+
+|                                                                                        | Page |
+|----------------------------------------------------------------------------------------|------|
+| F.6 Maximum transmit skew .....                                                        | 62   |
+| F.7 Sequence diagram for establishment of multilink operation.....                     | 62   |
+| Annex G – Usage of ISO/IEC 14496-1 generic capabilities in ITU-T H.324 terminals ..... | 64   |
+| G.1 Scope .....                                                                        | 64   |
+| G.2 References .....                                                                   | 64   |
+| G.3 General .....                                                                      | 64   |
+| G.4 Choice of error protection for ISO/IEC 14496 data streams.....                     | 64   |
+| G.5 Framing of ISO/IEC 14496-1 data streams .....                                      | 64   |
+| Annex H – Mobile multilink operation.....                                              | 65   |
+| H.1 Scope .....                                                                        | 65   |
+| H.2 Definitions and format conventions .....                                           | 65   |
+| H.3 Functional requirements .....                                                      | 65   |
+| H.4 Overview .....                                                                     | 65   |
+| H.5 Mobile multilink layer specification .....                                         | 66   |
+| H.6 Procedures .....                                                                   | 69   |
+| H.7 Header modes .....                                                                 | 72   |
+| Annex I – Usage of HTTP generic capability in ITU-T H.324 terminals .....              | 73   |
+| I.1 General .....                                                                      | 73   |
+| I.2 Logical channel for HTTP .....                                                     | 74   |
+| I.3 HTTP generic capability.....                                                       | 74   |
+| I.4 References .....                                                                   | 74   |
+| Annex J – ASN.1 OIDs defined in this Recommendation.....                               | 75   |
+| J.1 Summary of OIDs defined in this Recommendation .....                               | 75   |
+| J.2 Session reset capability identifier.....                                           | 75   |
+| Annex K – Media oriented negotiation acceleration procedure .....                      | 76   |
+| K.1 Abstract.....                                                                      | 76   |
+| K.2 General .....                                                                      | 76   |
+| K.3 References .....                                                                   | 76   |
+| K.4 Definitions and format conventions .....                                           | 76   |
+| K.5 Terminal procedures.....                                                           | 77   |
+| K.6 MONA signalling .....                                                              | 77   |
+| K.7 Channel establishment method negotiation.....                                      | 80   |
+| K.8 Channel establishment via the signalling preconfigured channel (SPC).....          | 88   |
+| K.9 Preconfigured channel establishment .....                                          | 92   |
+| K.10 Accelerated ITU-T H.245 procedures .....                                          | 97   |
+| Annex L – Text conversation in ITU-T H.324 .....                                       | 101  |
+| L.1 Introduction .....                                                                 | 101  |
+| L.2 Scope .....                                                                        | 101  |
+| L.3 Definitions .....                                                                  | 101  |
+
+|                                                                   | <b>Page</b> |
+|-------------------------------------------------------------------|-------------|
+| L.4    Procedures for ITU-T T.140 text conversation .....         | 101         |
+| L.5    Framing and buffering of ITU-T T.140 data .....            | 103         |
+| L.6    Presentation considerations .....                          | 103         |
+| Annex M – ITU-T H.245 messages used by ITU-T H.324 endpoints..... | 106         |
+| Appendix I – Bit and octet order.....                             | 110         |
+| Appendix II – ITU-T V.8 <i>bis</i> codepoints.....                | 111         |
+
+# Recommendation ITU-T H.324
+
+## Terminal for low bit-rate multimedia communication
+
+# 1 Scope
+
+This Recommendation covers the technical requirements for very low bit-rate multimedia telephone terminals operating over the general switched telephone network (GSTN).
+
+ITU-T H.324 terminals provide real-time video audio or data, or any combination, between two multimedia telephone terminals over a GSTN voice band network connection. Communication may be either 1-way or 2-way. Multipoint communication using a separate multipoint control unit (MCU) among more than two ITU-T H.324 terminals is possible. MCUs and other non-terminal devices are not bound by the requirements in this Recommendation, but they should comply where practical.
+
+The multimedia telephone terminals defined in this Recommendation can be integrated into personal computers (PCs) or workstations, or be stand-alone units.
+
+Interworking with visual telephone systems on the integrated services digital network (ISDN) (known as the ITU-T H.320-series of Recommendations) and on mobile radio networks are also covered.
+
+## 1.1 Block diagram and functional elements
+
+A generic ITU-T H.324 multimedia videophone system is shown in Figure 1. It consists of terminal equipment, GSTN modem, GSTN network, multipoint control unit (MCU) and other system operation entities. ITU-T H.324 implementations are not required to have each functional element.
+
+![Block diagram for ITU-T H.324 multimedia system](b28af4985cdef1e519e3aaf26561dcb3_img.jpg)
+
+The diagram illustrates the functional elements of an ITU-T H.324 multimedia system. On the left, four external components are shown: 'Video I/O equipment', 'Audio I/O equipment', 'User data applications ITU-T T.120, etc.', and 'System control'. These are connected to a central dashed box labeled 'Scope of ITU-T H.324'. Inside this box, the components connect to internal functional blocks: 'Video codec ITU-T H.263/ITU-T H.261' (receiving input from Video I/O), 'Audio codec ITU-T G.723.1' (receiving input from Audio I/O and connected to a 'Receive path delay' block), 'Data protocols ITU-T V.14, LAPM, etc.' (receiving input from User data applications), and 'Control protocol ITU-T H.245' (receiving input from System control and connected to 'SRP/LAPM procedures'). All four internal blocks feed into a 'Multiplex/demultiplex ITU-T H.223' block. This block connects to a 'Modem ITU-T V.34/ITU-T V.8' block, which in turn connects to an external 'GSTN network' (represented by a circle). Below the Modem block is a 'Modem control ITU-T V.250' block, which also connects to the GSTN network. The GSTN network is further connected to an external 'MCU' (Multipoint Control Unit) block. A small label 'H.324(09)\_F01' is located in the bottom right corner of the diagram area.
+
+Block diagram for ITU-T H.324 multimedia system
+
+Figure 1 – Block diagram for ITU-T H.324 multimedia system
+
+## 1.2 System elements outside the scope of this Recommendation
+
+The following system elements are covered by other Recommendations or are not subject to standardization, and are therefore not defined in this Recommendation:
+
+- Video I/O equipment including cameras and monitors, their control and selection, video processing to improve compression or provide split-screen functions.
+- Audio I/O equipment including microphone and loudspeaker, telephone instrument or equivalent, attached audio devices providing voice activation sensing, multiple microphone mixers, acoustic echo cancellation.
+- Data application equipment such as computers, non-standardized data application protocols, telematic visual aids such as electronic whiteboards, etc.
+- GSTN network interface supporting appropriate signalling, ringing functions and voltage levels, in accordance with national standards.
+- Human user system control, user interface and operation.
+
+## 1.3 Functional elements covered by this Recommendation
+
+The scope of this Recommendation is indicated by the elements within the dashed line of Figure 1, which include:
+
+- The video codec (ITU-T H.263 or ITU-T H.261) carries out redundancy reduction coding and decoding for video streams.
+- The audio codec (ITU-T G.723.1) encodes the audio signal from the microphone for transmission, and decodes the audio code which is output to the speaker. Optional delay in the receiving audio path compensates for the video delay, so as to maintain audio and video synchronization.
+- The data protocols support data applications such as electronic whiteboards, still image transfer, file exchange, database access, audiographics conferencing, remote device control, network protocols, etc. Standardized data applications include ITU-T T.120 for real-time audiographics conferencing, ITU-T T.84 simple point-point still image file transfer, ITU-T T.434 simple point-point file transfer, ITU-T H.224/ITU-T H.281 far-end camera control, ISO/IEC TR 9577 network protocols including point-to-point protocol (PPP) and Internet Protocol (IP), and transport of user data using buffered ITU-T V.14 or LAPM/ITU-T V.42. Other applications and protocols may also be used via ITU-T H.245 negotiation.
+- The control protocol (ITU-T H.245) provides end-to-end signalling for proper operation of the ITU-T H.324 terminal, and signals all other end-to-end system functions including reversion to analogue speech-only telephony mode. It provides for capability exchange, signalling of commands and indications, and messages to open and fully describe the content of logical channels.
+- The multiplex protocol (ITU-T H.223) multiplexes transmitted video, audio, data and control streams into a single bitstream, and demultiplexes a received bitstream into various multimedia streams. In addition, it performs logical framing, sequence numbering, error detection and error correction by means of retransmission, as appropriate to each media type.
+- The modem (ITU-T V.34) converts the ITU-T H.223 synchronous multiplexed bitstream into an analogue signal that can be transmitted over the GSTN, and converts the received analogue signal into a synchronous bitstream that is sent to the multiplex/demultiplex protocol unit. [ITU-T V.250] (Former Recommendation ITU-T 25 *ter*) is used to provide control/sensing of the modem/network interface, when the modem with network signalling and ITU-T V.8/ITU-T V.8 *bis* functional elements is a separate physical item.
+
+# 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 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 (1996), *Dual rate speech coder for multimedia communications transmitting at 5.3 and 6.3 kbit/s*.
+- [ITU-T G.725] Recommendation ITU-T G.725 (1988), *System aspects for the use of the 7 kHz audio codec within 64 kbit/s*.
+- [ITU-T H.221] Recommendation ITU-T H.221 (2004), *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.224] Recommendation ITU-T H.224 (2005), *A real time control protocol for simplex applications using the H.221 LSD/HSD/MLP channels*.
+- [ITU-T H.226] Recommendation ITU-T H.226 (1998), *Channel aggregation protocol for multilink operation on circuit-switched networks*.
+- [ITU-T H.233] Recommendation ITU-T H.233 (2002), *Confidentiality system for audiovisual services*.
+- [ITU-T H.234] Recommendation ITU-T H.234 (2002), *Encryption key management and authentication system for audiovisual services*.
+- [ITU-T H.239] Recommendation ITU-T H.239 (2005), *Role management and additional media channels for H.300-series terminals*.
+- [ITU-T H.241] Recommendation ITU-T H.241 (2005), *Extended video procedures and control signals for H.300-series terminals*.
+- [ITU-T H.245] Recommendation ITU-T H.245 (2005), *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.263] Recommendation ITU-T H.263 (2005), *Video coding for low bit rate communication*.
+- [ITU-T H.264] Recommendation ITU-T H.264 (2005), *Advanced video coding for generic audiovisual services*.
+- [ITU-T H.281] Recommendation ITU-T H.281 (1994), *A far end camera control protocol for videoconferences using H.224*.
+- [ITU-T H.320] Recommendation ITU-T H.320 (2004), *Narrow-band visual telephone systems and terminal equipment*.
+
+- [ITU-T T.30] Recommendation ITU-T T.30 (2005), *Procedures for document facsimile transmission in the general switched telephone network.*
+- [ITU-T T.84] Recommendation ITU-T T.84 (1996) | ISO/IEC 10918-3:1997, *Information technology – Digital compression and coding of continuous-tone still images: Extensions.*
+- [ITU-T T.120] Recommendation ITU-T T.120 (1996), *Data protocols for multimedia conferencing.*
+- [ITU-T T.134] Recommendation ITU-T T.134 (1998), *Text chat application entity.*
+- [ITU-T T.140] Recommendation ITU-T T.140 (1998), *Protocol for multimedia application text conversation.*
+- [ITU-T T.434] Recommendation ITU-T T.434 (1999), *Binary file transfer format for the telematic services.*
+- [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.14] Recommendation ITU-T V.14 (1993), *Transmission of start-stop characters over synchronous bearer channels.*
+- [ITU-T V.34] Recommendation ITU-T V.34 (1998), *A modem operating at data 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.42] Recommendation ITU-T V.42 (2002), *Error-correcting procedures for DCEs using asynchronous-to-synchronous conversion.*
+- [ITU-T V.42 bis] Recommendation ITU-T V.42 bis (1990), *Data compression procedures for data circuit-terminating equipment (DCE) using error correction procedures.*
+- [ITU-T V.140] Recommendation ITU-T V.140 (2005), *Procedures for establishing communication between two multiprotocol audiovisual terminals using digital channels at a multiple of 64 or 56 kbit/s.*
+- [ITU-T V.250] Recommendation ITU-T V.250 (2003)<sup>1</sup>, *Serial asynchronous automatic dialling and control.*
+- [ITU-T X.691] Recommendation ITU-T X.691 (2002) | ISO/IEC 8825-2:2002, *Information technology – ASN.1 encoding rules – Specification of Packed Encoding Rules (PER).*
+- [ISO/IEC 13239] ISO/IEC 13239:2002, *Information technology – Telecommunications and information exchange between systems – High-level data link control (HDLC) procedures.*
+- [ISO/IEC 14496-1] ISO/IEC 14496-1:2001, *Information technology – Coding of audio-visual objects – Part 1: Systems.*
+
+<sup>1</sup> Former Recommendation ITU-T V.25 ter (1997), renumbered as Recommendation ITU-T V.250 in 1998.
+
+- [ISO/IEC 14496-2] ISO/IEC 14496-2:2004, *Information technology – Coding of audio-visual objects – Part 2: Visual*.
+- [ISO/IEC 14496-3] ISO/IEC 14496-3:2001, *Information technology – Coding of audio-visual objects – Part 3: Audio*.
+- [ISO/IEC TR 9577] ISO/IEC TR 9577:1999, *Information technology – Protocol identification in the network layer*.
+- [ETSI TS 126 071] ETSI TS 126 071 V6.0.0 (2004-12), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); AMR speech Codec; General description (3GPP TS 26.071 version 6.0.0 Release 6)*.
+- [ETSI TS 126 171] ETSI TS 126 171 V6.0.0 (2004-12), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); AMR speech Codec, wideband; General description (3GPP TS 26.171 version 6.0.0 Release 6)*.
+- [IETF RFC 2616] IETF RFC 2616 (1999), *Hypertext Transfer Protocol – HTTP/1.1*.
+
+## 2.2 Informative references
+
+- [ITU-T E.164] Recommendation ITU-T E.164 (2005), *The international public telecommunication numbering plan*.
+- [ITU-T F.703] Recommendation ITU-T F.703 (2000), *Multimedia conversational services*.
+- [ITU-T G.114] Recommendation ITU-T G.114 (2003), *One-way transmission time*.
+- [ITU-T G.703] Recommendation ITU-T G.703 (2001), *Physical/electrical characteristics of hierarchical digital interfaces*.
+- [ITU-T G.704] Recommendation ITU-T G.704 (1998), *Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44 736 kbit/s hierarchical levels*.
+- [ITU-T G.722] Recommendation ITU-T G.722 (1988), *7 kHz audio-coding within 64 kbit/s*.
+- [ITU-T G.722.1] Recommendation ITU-T G.722.1 (2005), *Low-complexity coding at 24 and 32 kbit/s for hands-free operation in systems with low frame loss*.
+- [ITU-T G.728] Recommendation ITU-T G.728 (1992), *Coding of speech at 16 kbit/s using low-delay code excited linear prediction*.
+- [ITU-T H.230] Recommendation ITU-T H.230 (2004), *Frame-synchronous control and indication signals for audiovisual systems*.
+- [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*.
+- [ITU-T H.310] Recommendation ITU-T H.310 (1998), *Broadband audiovisual communication systems and terminals*.
+- [ITU-T H.323] Recommendation ITU-T H.323 (2006), *Packet-based multimedia communications systems*.
+- [ITU-T Q.931] Recommendation ITU-T Q.931 (1998), *ISDN user-network interface layer 3 specification for basic call control*.
+- [ITU-T T.35] Recommendation ITU-T T.35 (2000), *Procedure for the allocation of ITU-T defined codes for non-standard facilities*.
+
+- [ITU-T T.39] Recommendation ITU-T T.39 (1997), *Application profiles for simultaneous voice and facsimile terminals.*
+- [ITU-T T.51] Recommendation ITU-T T.51 (1992), *Latin based coded character sets for telematic services.*
+- [ITU-T T.123] Recommendation ITU-T T.123 (2007), *Network-specific data protocol stacks for multimedia conferencing.*
+- [ITU-T T.126] Recommendation ITU-T T.126 (2007), *Multipoint still image and annotation protocol.*
+- [ITU-T T.127] Recommendation ITU-T T.127 (2007), *Multipoint binary file transfer protocol.*
+- [ITU-T V.24] Recommendation ITU-T V.24 (2000), *List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE).*
+- [ITU-T X.21] Recommendation ITU-T X.21 (1992), *Interface between Data Terminal Equipment and Data Circuit-terminating Equipment for synchronous operation on public data networks.*
+- [ITU-T X.680] Recommendation ITU-T X.680 (2002) | ISO/IEC 8824-1:2002, *Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation.*
+- [IETF RFC 1490] IETF RFC 1490 (1993), *Multiprotocol Interconnect over Frame Relay.*
+- [IETF RFC 1661] IETF RFC 1661 (1994), *The Point-to-Point Protocol (PPP).*
+
+# 3 Definitions
+
+For the purposes of this Recommendation, the definitions given in clause 3 of both [ITU-T H.223] and [ITU-T H.245] apply, along with the following:
+
+- 3.1 adaptation layer service data unit (AL-SDU):** The logical unit of information exchanged between the ITU-T H.223 multiplex and the audio codec, video codec or data protocol above.
+- 3.2 channel:** A unidirectional link between two endpoints.
+- 3.3 codec:** Coder/decoder, used to convert audio or video signals to/from digital format.
+- 3.4 connection:** A bidirectional link between two endpoints.
+- 3.5 control channel:** Dedicated logical channel number 0 carrying system control protocol per [ITU-T H.245].
+- 3.6 data:** Information streams other than control, audio and video, carried in a logical data channel (see [ITU-T H.223]).
+- 3.7 in-band signalling:** Control signals sent within a specific logical channel other than the control channel, carrying information applicable only to that logical channel.
+- 3.8 interworking adapter:** A device connected to terminals or MCUs working according to two or more Recommendations, which translates the content of one or more logical channels to allow interoperation between otherwise incompatible equipment.
+- 3.9 lip synchronization:** Operation to provide the feeling that speaking motion of the displayed person is synchronized with the voice sounds.
+- 3.10 logical channel:** One of several logically distinct channels carried over a single bitstream.
+- 3.11 media:** One or more of audio, video or data.
+
+- 3.12 multilink:** The use of more than one physical connection to obtain a larger aggregate bit rate.
+- 3.13 multipoint:** The simultaneous interconnection of three or more terminals to allow communication among several sites through the use of multipoint control units (bridges) which centrally direct the flow of information.
+- 3.14 MUX-PDU:** The logical unit of information exchanged between the ITU-T H.223 multiplex layer and the underlying physical layer. It is a packet framed by HDLC flags and using HDLC zero-bit insertion for transparency.
+- 3.15 non-segmentable:** The ITU-T H.223 mode of operation in which AL-SDUs must be sent as consecutive octets in a single MUX-PDU. See [ITU-T H.223].
+- 3.16 segmentable:** The ITU-T H.223 mode of operation in which AL-SDUs may be sent in separate multiplex slots carried on one or more MUX-PDUs (see [ITU-T H.223]).
+- 3.17 support:** The ability to operate in a given mode; however, a requirement to "support" a mode does not mean that the mode must actually be used at all times. Unless prohibited, other modes may be used by mutual negotiation.
+- 3.18 videophone:** A terminal capable of sending and receiving audio and video information simultaneously.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|        |                                                        |
+|--------|--------------------------------------------------------|
+| AL-SDU | Adaptation Layer Service Data Unit (see [ITU-T H.223]) |
+| ASN.1  | Abstract Syntax Notation One                           |
+| BC     | Bearer Capability                                      |
+| BCH    | Bose-Chaudhuri-Hocquenghem                             |
+| CIF    | Common Intermediate Format                             |
+| CCSRL  | Control Channel Segmentation and Reassembly Layer      |
+| CPF    | Compatible Protocol Field                              |
+| CRC    | Cyclic Redundancy Check                                |
+| DCE    | Data Circuit-Terminating Equipment                     |
+| DTE    | Data Terminal Equipment                                |
+| DTMF   | Dual Tone Multi-Frequency                              |
+| EIV    | Encryption Initialization Vector                       |
+| GSTN   | General Switched Telephone Network                     |
+| HLC    | High Level Capability                                  |
+| HDLC   | High-Level Data Link Control (per [ISO/IEC 13239])     |
+| IP     | Internet Protocol                                      |
+| ISDN   | Integrated Services Digital Network                    |
+| LAPM   | Link Access Procedures for Modems (per [ITU-T V.42])   |
+| LC     | Logical Channel                                        |
+| LCN    | Logical Channel Number (per [ITU-T H.223])             |
+
+|       |                                                           |
+|-------|-----------------------------------------------------------|
+| LS    | Last Segment                                              |
+| MCU   | Multipoint Control Unit                                   |
+| MONA  | Media Oriented Negotiation Acceleration                   |
+| MUX   | Multiplexer                                               |
+| NLPID | Network Layer Protocol Identifier (per [ISO/IEC TR 9577]) |
+| NSRP  | Numbered Simple retransmission protocol Response Frames   |
+| OID   | Object Identifier                                         |
+| PDU   | Protocol Data Unit                                        |
+| PER   | Packed Encoding Rules                                     |
+| PPP   | Point-to-Point Protocol                                   |
+| QCIF  | Quarter Common Intermediate Format                        |
+| SDU   | Service Data Unit                                         |
+| SE    | Session Exchange (per [ITU-T H.233])                      |
+| SQCIF | Sub Quarter Common Intermediate Format                    |
+| SRP   | Simple Retransmission Protocol (see Annex A)              |
+| WNSRP | Windowed NSRP                                             |
+
+# 5 Conventions
+
+The word "shall" is used in this Recommendation to specify a mandatory requirement.
+
+The word "should" is used in this Recommendation to specify a suggested, but not required, course of action.
+
+The word "may" is used in this Recommendation to specify an optional course of action, without expressing a preference.
+
+References in this Recommendation to specific ITU-T H.245 ASN.1 message structures are presented in **this typeface**.
+
+ITU-T H.324/I            Systems or endpoints conforming to Annex D.
+
+ITU-T H.324/M           Systems or endpoints conforming to Annex C.
+
+# 6 Functional requirements
+
+## 6.1 Required elements
+
+ITU-T H.324 implementations are not required to have each functional element, except for the ITU-T V.34 modem, ITU-T H.223 multiplex and ITU-T H.245 system control protocol, all of which shall be supported by all ITU-T H.324 terminals.
+
+ITU-T H.324 terminals offering audio communication shall support the ITU-T G.723.1 audio codec. ITU-T H.324 terminals offering video communication shall support the ITU-T H.263 and ITU-T H.261 video codecs. ITU-T H.324 terminals offering real-time audiographic conferencing should support the ITU-T T.120 protocol suite. In addition, other video and audio codecs, and other data protocols, may optionally be used via negotiation over the ITU-T H.245 control channel.
+
+If a modem external to the ITU-T H.324 terminal is used, terminal/modem control shall conform to [ITU-T V.250].
+
+The presence of optional facilities is signalled via the ITU-T H.245 control channel. If both ends support an optional facility, and choose to make use of it, the opening of a path to carry such information streams is negotiated according to the procedures of [ITU-T H.245].
+
+NOTE – This Recommendation does not specify a particular implementation. Any implementation that provides the required functionality, and that conforms to the bitstream format ultimately described by this Recommendation, is considered compliant.
+
+## 6.2 Information streams
+
+Multimedia information streams are classified into video, audio, data and control as follows:
+
+- Video streams are continuous traffic carrying moving colour pictures. When used, the bit rate available for video streams may vary according to the needs of the audio and data channels.
+- Audio streams are real-time, but may optionally be delayed in the receiver processing path to maintain synchronization with the video streams. In order to reduce the average bit rate of audio streams, voice activation may be provided.
+- Data streams may represent still pictures, facsimile, documents, computer files, computer application data, undefined user data and other data streams.
+- Control streams pass control commands and indications between remote counterparts. Terminal-to-modem control conforms to [ITU-T V.250] for terminals using external modems connected by a separate physical interface. Terminal-to-terminal control is according to [ITU-T H.245].
+
+## 6.3 Modem
+
+Modems used for ITU-T H.324 terminals shall operate in full duplex, synchronous mode and conform to [ITU-T V.34] and [ITU-T V.8]. Support of [ITU-T V.8 *bis*] is optional. The output of the ITU-T H.223 multiplex shall be applied directly to the [ITU-T V.34] synchronous data pump. When an external, non-integrated ITU-T V.34 modem is used, control between the modem and the terminal shall be via [ITU-T V.250]. In such cases, the physical interface is implementation-specific. The use of the optional ITU-T V.34 auxiliary channel is reserved for further study.
+
+## 6.4 Multiplex
+
+Logical channels of video, audio, data or control information may be transmitted, after the channels have been established according to the procedures of [ITU-T H.245]. Logical channels are unidirectional, and are independent in each direction of transmission. Any number of logical channels of each media type may be transmitted, except for the ITU-T H.245 control channel of which there shall be one. The multiplex method used to transmit these logical channels shall conform to [ITU-T H.223]. The optional exclusive-OR procedure of clause 6.4.2 of [ITU-T H.223] shall not be used by [ITU-T H.324] terminals.
+
+The ITU-T H.223 multiplex consists of a multiplex layer, which mixes the various logical channels into a single bitstream, and an adaptation layer, which handles error control and sequence numbering, as appropriate to each information stream. The multiplex layer transfers logical channel information in packets called MUX-PDUs, delimited by HDLC flags and using HDLC zero-bit insertion for transparency. Each MUX-PDU contains a one-octet header followed by a variable number of information field octets. The header octet includes a multiplex code, which specifies, by reference to a multiplex table, the mapping of the information field octets to various logical channels. Each MUX-PDU may contain a different multiplex code, and therefore a different mix of logical channels.
+
+ITU-T H.324 terminals shall signal their ITU-T H.223 capabilities via the ITU-T H.245 **H223Capability** message.
+
+### 6.4.1 Logical channel numbers
+
+Each logical channel is identified by a logical channel number (LCN), in the range 0 to 65535, which serves only to associate logical channels with the corresponding entries in the ITU-T H.223 multiplex table. Logical channel numbers are selected arbitrarily by the transmitter, except that logical channel 0 shall be permanently assigned to the ITU-T H.245 control channel.
+
+### 6.4.2 Multiplex table entries
+
+Multiplex table entries are independent in each direction of transmission, and are sent from transmitters to receivers using the ITU-T H.245 **MultiplexEntrySend** request message. Multiplex table entry 0 shall not be sent, but shall be permanently assigned to logical channel 0, used for the control channel. Multiplex table entry 0 shall therefore be used for initial capability exchanges and transmission of initial multiplex table entries.
+
+### 6.4.3 Flow control
+
+ITU-T H.324 terminals shall respond to the ITU-T H.245 **FlowControlCommand** message, which commands a limit to the overall bit rate of one or more logical channels, or the entire multiplex.
+
+When one or more logical channels are limited by the **FlowControlCommand**, other less restricted logical channels may increase their transmission rate. The limit applies to the content of the logical channel at the input to the multiplex layer, before flags or zero-bit insertion is applied.
+
+When the entire ITU-T H.223 multiplex is limited by the **FlowControlCommand**, or when the terminal has no information to send, the terminal shall send HDLC flags in place of logical channel information. The limit applies to the entire multiplex output, including opening flags, header octets and inserted zero bits, but not including idle flags.
+
+### 6.4.4 Error control
+
+The multiplex layer of [ITU-T H.223] does not perform error control, except for a CRC on the header octet. Error control for each logical channel is handled separately by the adaptation layers of [ITU-T H.223], which may use a variety of error control techniques, including but not limited to, error detection and retransmission.
+
+### 6.4.5 Adaptation layers
+
+[ITU-T H.223] defines three adaptation layers, AL1, AL2 and AL3. AL1 is intended primarily for variable-rate framed information, including unframed octets treated as a single frame of indefinite length. AL2 is intended primarily for digital audio, and includes an 8-bit CRC and optional sequence numbers. AL3 is intended primarily for digital video and includes provision for retransmission.
+
+The logical unit of information exchanged between the ITU-T H.223 multiplex and the audio codec, video codec, data protocol or control protocol above is called an AL-SDU.
+
+Logical channels carried by the ITU-T H.223 multiplex may be of either "segmentable" or "non-segmentable" type, as defined in [ITU-T H.223], and signalled by [ITU-T H.245] when each channel is opened. AL-SDUs of segmentable logical channels may be segmented by the ITU-T H.223 multiplex. AL-SDUs of non-segmentable logical channels are not segmented by the ITU-T H.223 multiplex. Generally, segmentable channels should be used for variable bit-rate information streams such as control, video and data, while non-segmentable channels should be used for constant bit-rate streams such as audio.
+
+Receivers shall signal their capability to process various adaptation layers and channel types according to [ITU-T H.245]. Transmitters shall signal which adaptation layers, options and channel type are used for each logical channel when opening the channel, according to [ITU-T H.245].
+
+## 6.5 Control channel
+
+The control channel carries end-to-end control messages governing operation of the ITU-T H.324 system, including capabilities exchange, opening and closing of logical channels, mode preference requests, multiplex table entry transmission, flow control messages and general commands and indications.
+
+There shall be exactly one control channel in each direction within ITU-T H.324, which shall use the messages and procedures of [ITU-T H.245]. The control channel shall be carried on logical channel 0. The control channel shall be considered to be permanently open from the establishment of digital communication until the termination of digital communication; the normal procedures for opening and closing logical channels shall not apply to the control channel.
+
+General commands and indications shall be chosen from the message set contained in [ITU-T H.245]. In addition, other command and indication signals may be sent which have been specifically defined to be transferred in-band within video, audio or data streams (see the appropriate Recommendation to determine if such signals have been defined).
+
+ITU-T H.245 messages fall into four categories: request, response, command and indication. Request messages require a specific action by the receiver, including an immediate response. Response messages respond to a corresponding request. Command messages require a specific action, but do not require a response. Indication messages are informative only, and do not require any action or response. ITU-T H.324 terminals shall respond to all supported ITU-T H.245 commands and requests as specified in [ITU-T H.245], and shall transmit accurate indications reflecting the state of the terminal.
+
+NOTE 1 – All control channel messages are sent over a link layer protocol which acknowledges correct receipt. This acknowledgement is distinct from the response messages, which convey content beyond that of correct receipt of the message.
+
+ITU-T H.324 terminals shall be capable of parsing all ITU-T H.245 **MultimediaSystemControlMessage** messages, and shall send and receive all messages needed to implement required ITU-T H.324 functions and those optional functions which are supported by the terminal. All messages and procedures of [ITU-T H.245] related to required ITU-T H.324 functions are required, except for those explicitly described as optional, or which are related to defined optional capabilities the terminal does not support. ITU-T H.324 terminals shall send the **FunctionNotSupported** message in response to unrecognized request, response or command messages.
+
+A control channel indication, **UserInputIndication**, is available for transport of user input alphanumeric characters from a keypad or keyboard, equivalent to the DTMF signals used in analogue telephony. This may be used to manually operate remote equipment such as voice mail or video mail systems, menu-driven information services, etc. ITU-T H.324 terminals shall support the transmission of user input characters 0-9, '\*' and '#'. Transmission of other characters is optional.
+
+NOTE 2 – If the encryption procedures of this Recommendation are in use, the control channel will not be encrypted. Users are therefore cautioned regarding the carriage of user data in the control channel, the use of non-standard messages and the confidentiality risk from traffic analysis of the control channel.
+
+### 6.5.1 Capabilities exchange
+
+Capabilities exchange shall follow the procedures of [ITU-T H.245], which provides for separate receive and transmit capabilities, as well as a system by which the terminal may describe its ability to operate in various combinations of modes simultaneously.
+
+Receive capabilities describe the terminal's ability to receive and process incoming information streams. Transmitters shall limit the content of their transmitted information to that which the receiver has indicated it is capable of receiving. The absence of a receive capability indicates that the terminal cannot receive (is a transmitter only).
+
+Transmit capabilities describe the terminal's ability to transmit information streams. Transmit capabilities serve to offer receivers a choice of possible modes of operation, so that the receiver may request the mode which it prefers to receive. The absence of a transmit capability indicates that the terminal is not offering a choice of preferred modes to the receiver (but it may still transmit anything within the capability of the receiver).
+
+The transmitting terminal assigns each individual mode the terminal is capable of operating in a number in a **capabilityTable**. For example, ITU-T G.723.1 audio, ITU-T G.728 audio and ITU-T H.263 CIF video would each be assigned separate numbers.
+
+These capability numbers are grouped into **AlternativeCapabilitySet** structures. Each **AlternativeCapabilitySet** indicates that the terminal is capable of operating in exactly one mode listed in the set. For example, an **AlternativeCapabilitySet** listing {G.711, G.723.1, G.728} means that the terminal can operate in any one of those audio modes, but not more than one.
+
+These **AlternativeCapabilitySet** structures are grouped into **simultaneousCapabilities** structures. Each **simultaneousCapabilities** structure indicates a set of modes the terminal is capable of using simultaneously. For example, a **simultaneousCapabilities** structure containing the two **AlternativeCapabilitySet** structures {H.261, H.263} and {G.711, G.723.1, G.728} means that the terminal can operate either of the video codecs simultaneously with any one of the audio codecs. The **simultaneousCapabilities** set { {H.261}, {H.261, H.263}, {G.711, G.723.1, G.728} } means the terminal can operate two video channels and one audio channel simultaneously: one video channel per [ITU-T H.261], another video channel per either [ITU-T H.261] or [ITU-T H.263], and one audio channel per either [ITU-T G.711], [ITU-T G.723.1] or [ITU-T G.728].
+
+NOTE – The actual capabilities stored in the **capabilityTable** are often more complex than presented here. For example, each ITU-T H.263 capability indicates details including the ability to support various picture formats at given minimum picture intervals, and ability to use optional coding modes. For a complete description, see [ITU-T H.245].
+
+The terminal's total capabilities are described by a set of **CapabilityDescriptor** structures, each of which is a single **simultaneousCapabilities** structure and a **capabilityDescriptorNumber**. By sending more than one **CapabilityDescriptor**, the terminal may signal dependencies between operating modes by describing different sets of modes which it can simultaneously use. For example, a terminal issuing two **CapabilityDescriptor** structures, one { {H.261, H.263}, {G.711, G.723.1, G.728} } as in the previous example, and the other { {H.262}, {G.711} }, means the terminal can also operate the ITU-T H.262 video codec, but only with the low-complexity ITU-T G.711 audio codec.
+
+Terminals may dynamically add capabilities during a communication session by issuing additional **CapabilityDescriptor** structures, or remove capabilities by sending revised **CapabilityDescriptor** structures. All ITU-T H.324 terminals shall transmit at least one **CapabilityDescriptor** structure.
+
+Non-standard capabilities and control messages may be issued using the **NonStandardParameter** structure defined in [ITU-T H.245]. Note that while the meaning of non-standard messages is defined by individual organizations, equipment built by any manufacturer may signal any non-standard message, if the meaning is known.
+
+Terminals may reissue capability sets at any time, according to the procedures of [ITU-T H.245].
+
+### 6.5.2 Logical channel signalling
+
+Each logical channel carries information from a transmitter to a receiver, and is identified by a logical channel number unique for each direction of transmission.
+
+Logical channels are opened and closed using the **OpenLogicalChannel** and **CloseLogicalChannel** messages and procedures of [ITU-T H.245]. When a logical channel is opened, the **OpenLogicalChannel** message fully describes the content of the logical channel, including media type, algorithm in use, ITU-T H.223 adaptation layer and any options, and all other information needed for the receiver to interpret the content of the logical channel. Logical channels may be closed when no longer needed. Open logical channels may be inactive, if the information source has nothing to send.
+
+Logical channels in this Recommendation are unidirectional, so asymmetrical operation, in which the number and type of information streams is different in each direction of transmission, is allowed. However, if a receiver is capable only of certain symmetrical modes of operation, it may send a receive capability set that reflects its limitations. Terminals may also be capable of using a particular mode in only one direction of transmission.
+
+Certain media types, including data protocols such as ITU-T T.120 and LAPM, and video carried over AL3, inherently require a bidirectional channel for their operation. In such cases, a pair of unidirectional logical channels, one in each direction, may be opened and associated together to form a bidirectional channel using the bidirectional channel opening procedures of [ITU-T H.245]. Such pairs of associated channels need not share the same logical channel number, since logical channel numbers are independent in each direction of transmission.
+
+#### 6.5.2.1 Channel muting
+
+Logical channels may be temporarily inactive. Such temporary inactivation (muting) should be indicated to the far-end terminal using the ITU-T H.245 miscellaneous indication **logicalChannelInactive**.
+
+The ITU-T H.245 miscellaneous indication **logicalChannelActive** should be used to indicate when a normal signal has resumed on the logical channel. These indications are intended to be used to inform the human user that the far end has muted or unmuted the channel.
+
+Before sending the **logicalChannelInactive** message, the transmitter should ensure that no data is sent on the logical channel.
+
+However, regardless of whether or not **logicalChannelInactive** or **logicalChannelActive** messages are received, receivers shall decode the contents of the logical channel normally.
+
+### 6.5.3 Mode preferences
+
+Receivers may request transmitters to send a particular mode using the ITU-T H.245 **RequestMode** message, which describes the desired mode. Except when in receipt of **multipointModeCommand**, transmitters may deny such requests, but should comply if possible.
+
+### 6.5.4 Interface to multiplex
+
+The control channel shall be segmentable and use logical channel 0. All ITU-T H.324 terminals shall support transmission of ITU-T H.245 control messages over the framed AL1 layer of ITU-T H.223 according to the procedures in Annex A, which ensure reliable delivery by retransmission of errored frames.
+
+Annex A defines a simple retransmission protocol (SRP) as a data link layer for ITU-T H.245. All ITU-T H.324 terminals shall support the SRP defined in Annex A. Terminals may optionally use LAPM/ITU-T V.42 as a data link layer instead of the SRP, if this mode is negotiated per the procedure in Annex A. In the LAPM/ITU-T V.42 mode, several control messages may be streamed using the procedures of LAPM, avoiding a wait for acknowledgement of each frame before the next message may be sent.
+
+More than one ITU-T H.245 control message may be sent in each SRP or LAPM frame.
+
+### 6.5.5 Timer and counter values and protocol errors
+
+All timers defined in [ITU-T H.245] shall have periods of at least the maximum data delivery time allowed by the data link layer carrying ITU-T H.245, including any retransmissions. For SRP, a period of at least  $T401 \times (N400 + 1)$  [that is, acknowledgement timer  $\times$  (retransmit counter + 1)].
+
+The ITU-T H.245 retry counter N100 should be at least 3.
+
+If an ITU-T H.245 protocol error occurs, the terminal may optionally retry the ITU-T H.245 procedure or may take other appropriate action, such as disconnection or reversion to analogue telephony, depending on predetermined configuration.
+
+### 6.5.6 Resolution of logical channel conflicts
+
+In the event of a conflict when requests to open logical channels are initiated at the same time, ITU-T H.324 terminals should follow the optional recommended procedure in clause C.4.1.3 of [ITU-T H.245] or clause C.5.1.3 of [ITU-T H.245], as appropriate.
+
+The master which experiences such a conflict shall reject the channel with a **masterSlaveConflict** reason. The slave which receives the **OpenLogicalChannelReject** message with the **masterSlaveConflict** reason should retry to open a logical channel with the media type most preferred by the master terminal, unless the master terminal has already opened a logical channel which suits the purpose intended by the slave terminal.
+
+## 6.6 Video channels
+
+All ITU-T H.324 terminals offering video communication shall support both the ITU-T H.263 and ITU-T H.261 video codecs, except that ITU-T H.320 interworking adapters (which are not terminals) do not have to support ITU-T H.263 (see clause 8.2). The ITU-T H.261 and ITU-T H.263 codecs shall be used without BCH error correction and without error correction framing. There are five standardized image formats: 16CIF, 4CIF, CIF, QCIF and SQCIF. Video may be supported in either one direction (transmit or receive) or both directions.
+
+CIF and QCIF are defined in [ITU-T H.261]. For the ITU-T H.263 algorithm, SQCIF, 4CIF and 16CIF are defined in [ITU-T H.263]. For the ITU-T H.261 algorithm, SQCIF is any active picture size less than QCIF, filled out by a black border, and coded in the QCIF format. For all these formats, the pixel aspect ratio is the same as that of the CIF format.
+
+NOTE 1 – The resulting *picture* aspect ratio for ITU-T H.263 SQCIF is different from the other formats.
+
+Table 1 shows which picture formats are required, and which are optional for ITU-T H.324 terminals which support video.
+
+**Table 1 – Picture formats for video terminals**
+
+| Picture format | Luminance pixels                  | Encoder           |                          | Decoder           |                   |
+|----------------|-----------------------------------|-------------------|--------------------------|-------------------|-------------------|
+|                |                                   | ITU-T H.261       | ITU-T H.263              | ITU-T H.261       | ITU-T H.263       |
+| SQCIF          | 128 × 96 for ITU-T H.263 (Note 1) | Optional (Note 1) | Required (Notes 2 and 3) | Optional (Note 1) | Required (Note 2) |
+| QCIF           | 176 × 144                         | Required          | Required (Notes 2 and 3) | Required          | Required (Note 2) |
+| CIF            | 352 × 288                         | Optional          | Optional                 | Optional          | Optional          |
+| 4CIF           | 704 × 576                         | Not defined       | Optional                 | Not defined       | Optional          |
+| 16CIF          | 1408 × 1152                       | Not defined       | Optional                 | Not defined       | Optional          |
+
+NOTE 1 – ITU-T H.261 SQCIF is any active size less than QCIF, filled out by a black border, coded in QCIF format.  
+NOTE 2 – Optional for ITU-T H.320 interworking adapters.  
+NOTE 3 – Mandatory to encode one of the picture formats QCIF and SQCIF; optional to encode both formats.
+
+All video decoders shall signal the maximum bit rate which can be decoded in the ITU-T H.245 **maxBitRate** parameter.
+
+Which picture formats, minimum number of skipped pictures and algorithm options can be accepted by the receiver is determined during the capability exchange using [ITU-T H.245]. After that, the transmitter is free to open any video LC which is in line with the receiver's capability. Receivers which indicate capability for a particular algorithm option shall also be capable of accepting video bitstreams which do not make use of that option as specified in [ITU-T H.245].
+
+When each video logical channel is opened, all supported operating modes for that channel are signalled to the receiver via [ITU-T H.245]. The picture header within the video bitstream indicates which mode is actually used for each picture, within the capabilities stated in the **OpenLogicalChannel** message. Receivers may signal, via [ITU-T H.245], a preference for a certain mode.
+
+NOTE 2 – In previous versions of this Recommendation, this paragraph was incorrect and inconsistent with [ITU-T H.245]. The semantics of [ITU-T H.245] shall be followed.
+
+Other video codecs, and other picture formats, may also be used via ITU-T H.245 negotiation. [ITU-T H.264] may optionally be used as a video codec, the signalling and procedures for the use of [ITU-T H.264] in ITU-T H.320 systems are defined in [ITU-T H.241]. [ITU-T H.264] 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. More than one video channel may be transmitted, as negotiated via the ITU-T H.245 control channel.
+
+NOTE 3 – The method of continuous presence multipoint operation, in which a single picture is divided into multiple sub-pictures, should not be used by ITU-T H.324 terminals. Instead, multiple logical channels of video should be used.
+
+### 6.6.1 Interface to multiplex
+
+All ITU-T H.324 terminals offering video communication shall support the required video codecs in segmentable logical channels using ITU-T H.223 adaptation layer AL3, and using a control field of at least one octet. Support of retransmission is required in encoders, with a minimum AL3 **sendBufferSize** of 1024 octets.
+
+The size of each AL-SDU, and their alignment with the video bitstream, is determined by video encoders, within the limit of the maximum AL3 SDU size the receiver indicates it is capable of. Video pictures may span more than one AL-SDU. ITU-T H.261 AL-SDUs are not required to align with logical structures in the video bitstream. ITU-T H.263 encoders shall align picture start codes with the start of an AL-SDU.
+
+NOTE – ITU-T H.263 pictures are a whole number of octets in length, since encoders add fill zero bits at the end of each picture as needed to fill out the final octet.
+
+If video communication is supported only in one direction (transmit or receive), the ITU-T H.223 adaptation layer AL3 protocol for the reverse direction shall also be supported, even if no video information will be sent on the reverse channel. Since the AL3 protocol requires a reverse channel for operation, logical channels using AL3 shall be opened using the ITU-T H.245 procedures for opening associated logical channels in each direction of transmission (bidirectional channels).
+
+While ITU-T H.223 AL3 allows for the retransmission of video information with detected errors, the receiving terminal may decide not to request a retransmission, based on factors including, but not limited to, the measured network delay, the error rate, whether the terminal is part of a multipoint conference, whether there is interworking with an ITU-T H.320 terminal, and the effectiveness of its error concealment techniques.
+
+When a video codec receives an AL-DRTX indication from ITU-T H.223 AL3, indicating that the local AL3 layer was unable to satisfy a retransmission request, it should encode the next video picture in the INTRA coding mode.
+
+Other video codecs, adaptation layers and options may be used via ITU-T H.245 negotiation.
+
+#### **6.6.1.1 ITU-T H.263 reference picture selection mode support**
+
+Annex N of [ITU-T H.263], reference picture selection mode, may optionally be supported. In this mode, video backchannel messages may be mixed with the video data in the opposite direction according to [ITU-T H.263], or video backchannel messages may be carried on an additional separate logical channel.
+
+In the case where Annex N of ITU-T H.263 video backchannel messages are carried on a separate LC, the procedure to set up the LC for the video backward channel is different depending on whether the video communication is unidirectional or bidirectional.
+
+In the case of bidirectional video communication, the LCs for original video data shall first be opened as bidirectional LCs which shall support ITU-T H.223 AL3. The LCs for the video backchannel messages shall next be opened by the terminal which originated the video LCs. The backchannel LCs shall be opened as bidirectional LCs with the LC dependency parameters indicating dependency on the corresponding video LC flowing in the same direction. The backchannel LCs shall support ITU-T H.223 AL2. Until the backchannel LCs are established, the terminal shall not send any video data which requests backchannel messages.
+
+In the case of unidirectional video communication, a single bidirectional LC shall be opened, which shall support ITU-T H.223 AL3. Variable length stuffing (BSTUF), defined in [ITU-T H.263], shall be used to make all the backward channel messages whole numbers of octets in length.
+
+### **6.6.2 Multiple channels of video**
+
+More than one channel of video may be transmitted, as negotiated, via [ITU-T H.245].
+
+The procedures of [ITU-T H.239] may be used with ITU-T H.324 systems. These procedures should be used when more than one channel of video is in use, in order to indicate the role of each channel in a conference, for example, "live" video of conference participants or video of "presentation" materials.
+
+## 6.7 Audio channels
+
+All ITU-T H.324 terminals offering audio communication shall support both the high and low rates of the ITU-T G.723.1 audio codec. ITU-T G.723.1 receivers shall be capable of accepting silence frames. The choice of high rate low rate or silence is made by the transmitter, and is signalled to the receiver in-band in the audio channel, as part of the syntax of each audio frame. Transmitters may switch ITU-T G.723.1 rates on a frame-by-frame basis, based on bit rate, audio quality or other preferences. Receivers may signal, via [ITU-T H.245], a preference for a particular audio rate or mode. Audio may be supported in either one direction (transmit or receive) or both directions.
+
+Alternative audio codecs may also be used, via ITU-T H.245 negotiation. 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.
+
+More than one audio channel may be transmitted, as negotiated via the ITU-T H.245 control channel.
+
+NOTE – Each audio channel is independent. Grouping of audio channels into stereo pairs or other synchronized groups is for further study.
+
+### 6.7.1 Delay compensation
+
+The ITU-T H.263 and ITU-T H.261 video codecs require some processing delay, while the ITU-T G.723.1 audio codec involves much less delay. Lip synchronization is not mandatory, but if it is to be maintained, additional delay must be added in the audio path to compensate.
+
+An ITU-T H.324 terminal shall not add delay for this purpose in its transmitting audio path. Instead, since video and audio coder delays may vary according to implementation, ITU-T H.324 terminals shall signal, via **H223SkewIndication** messages in the ITU-T H.245 control channel, the average skew by which their transmitted video signal trails the audio signal.
+
+Intermediate processing points such as MCUs or interworking adapters may alter the video/audio skew (see clause 10.3), and shall transmit appropriately modified video/audio skew indications, reflecting their transmitted streams. Video signals shall not precede audio signals; if necessary, video path delay shall be added to prevent this.
+
+Receiving terminals may optionally use this information to add appropriate delay in the audio path to achieve lip synchronization.
+
+### 6.7.2 Maximum delay jitter
+
+Audio AL-SDUs shall be transmitted periodically at an interval determined by the audio codec Recommendation in use (audio frame interval). The transmission of each audio AL-SDU at the ITU-T H.223 multiplex shall commence no later than 10 milliseconds after a whole multiple of the audio frame interval, measured from transmission of the first audio frame (audio delay jitter). Transmitters capable of further limiting their audio delay jitter may so signal using the ITU-T H.245 **maximumDelayJitter** parameter of the **H223Capability** message, so that receivers may optionally reduce their jitter delay buffers.
+
+### 6.7.3 Interface to multiplex
+
+All ITU-T H.324 terminals offering audio communication shall support the ITU-T G.723.1 codec using ITU-T H.223 adaptation layer AL2. The use of the sequence number option of AL2 is optional, but is not recommended for ITU-T G.723.1, since sequence numbers are generally not useful when the maximum delay jitter is less than the audio frame interval.
+
+For all frame-oriented audio codecs, AL-SDUs shall be transmitted in non-segmentable logical channels. Receivers shall signal the maximum number of audio frames they are capable of accepting in a single audio AL-SDU. Transmitters may send any whole number of audio frames in
+
+each AL-SDU, up to the maximum stated by the receiver. Transmitters shall not split audio frames across AL-SDUs, and shall send whole numbers of octets in each audio AL-SDU.
+
+NOTE 1 – Sample-based codecs, such as ITU-T G.711, shall be considered to be frame-oriented, with a frame size of one sample.
+
+For audio algorithms such as ITU-T G.723.1 which use more than one size of audio frame, audio frame boundaries within each AL-SDU shall be signalled in-band to the audio channel. For audio algorithms which use a fixed frame size, audio frame boundaries shall be implied by the ratio of AL-SDU size to audio frame size.
+
+Other adaptation layers and options may be used via ITU-T H.245 negotiation.
+
+NOTE 2 – Transmitters using alternative audio codecs should also support AL2, unless another adaptation layer has been specified for use with a particular codec.
+
+### 6.7.4 Use of [ITU-T G.722.1] for wideband audio
+
+[ITU-T G.722.1] may be used for wideband audio applications. ITU-T G.722.1 frames shall be sent using AL2. Audio frame boundaries within each AL-SDU shall be implied by the ratio of AL-SDU size to ITU-T G.722.1 frame size at the currently selected ITU-T G.722.1 bit rate.
+
+## 6.8 Data channels
+
+All data channels are optional. Standardized options for data applications include:
+
+- ITU-T T.120-series for point-to-point and multipoint audiographic teleconferencing including database access, still image transfer and annotation, application sharing, real-time file transfer, etc.;
+- ITU-T T.84 (SPIFF) point-to-point still image transfer cutting across application borders;
+- ITU-T T.434 point-to-point telematic file transfer cutting across application borders;
+- ITU-T H.224 for real-time control of simplex applications, including ITU-T H.281 far-end camera control;
+- network link layer, per [ISO/IEC TR 9577] (supports IP and PPP network layers, among others);
+- unspecified user data from external data ports;
+- ITU-T T.30 facsimile transfer;
+- ITU-T T.140 text conversation protocol.
+
+These data applications may reside in an external computer or other dedicated device attached to the ITU-T H.324 terminal through an ITU-T V.24 or equivalent interface (implementation-dependent), or may be integrated into the ITU-T H.324 terminal itself. Each data application makes use of an underlying data protocol for link layer transport. For each data application supported by the ITU-T H.324 terminal, this Recommendation requires support for a particular underlying data protocol to ensure interworking of data applications.
+
+NOTE – The ITU-T H.245 control channel is not considered a data channel.
+
+Standardized link layer data protocols used by data applications include:
+
+- buffered ITU-T V.14 mode for transfer of asynchronous characters, without error control;
+- LAPM/ITU-T V.42 for error-corrected transfer of asynchronous characters. Additionally, depending on application, ITU-T V.42 *bis* data compression may be used;
+- HDLC frame tunnelling for transfer of HDLC frames;
+- transparent data mode for direct access by unframed or self-framed protocols.
+
+All ITU-T H.324 terminals offering real-time audiographic conferencing should support the ITU-T T.120 protocol suite.
+
+All data protocols shall operate within ITU-T H.223 logical channels. All protocol procedures referring to link establishment or link termination (including set-up and disconnection of physical channels) shall be interpreted as referring to opening and closing of logical channels, and shall not affect the ITU-T H.324 physical link. For all protocol procedures which distinguish between an originator and an answerer, the ITU-T H.324 master terminal, determined according to the **MasterSlaveDetermination** procedure of [ITU-T H.245], shall be the originator, and the slave terminal shall be the answerer.
+
+More than one data channel, or more than one protocol, may be used at the same time (each in a separate logical channel), as negotiated via the ITU-T H.245 control channel. Other data protocols and applications may be used via ITU-T H.245 negotiation.
+
+### 6.8.1 Data protocols
+
+This clause describes these data protocols as if they are resident in the ITU-T H.324 terminal, connected through an ITU-T V.24 interface to an external computer or other dedicated device running the data application, as shown in Figure 2. The ITU-T V.24 interface may be replaced by a logical equivalent. ITU-T H.324 terminals with integrated data applications need not implement procedures related to the ITU-T V.24 interface which have no net effect on the transmitted bitstream.
+
+![Figure 2: Data application – Data protocol interface. The diagram shows a flow from left to right: an 'External computer or other dedicated device' connected to a 'Data application' box. This box is connected via an 'ITU-T V.24' interface to an 'ITU-T H.324 terminal' box. Inside the terminal, the flow goes through a 'Data protocol' block and then a 'ITU-T H.223 multiplex' block. From the multiplex, the flow goes via another 'ITU-T V.24' interface to a 'Modem' box. Finally, the Modem is connected to a 'GSTN network' represented by a circle. A label 'H.324(09)_F02' is present near the Modem to GSTN connection.](e90987faabad6a6665cd8ed1151dc474_img.jpg)
+
+Figure 2: Data application – Data protocol interface. The diagram shows a flow from left to right: an 'External computer or other dedicated device' connected to a 'Data application' box. This box is connected via an 'ITU-T V.24' interface to an 'ITU-T H.324 terminal' box. Inside the terminal, the flow goes through a 'Data protocol' block and then a 'ITU-T H.223 multiplex' block. From the multiplex, the flow goes via another 'ITU-T V.24' interface to a 'Modem' box. Finally, the Modem is connected to a 'GSTN network' represented by a circle. A label 'H.324(09)\_F02' is present near the Modem to GSTN connection.
+
+**Figure 2 – Data application – Data protocol interface**
+
+ITU-T H.324 terminals offering any data protocol described here shall support that protocol using segmentable logical channels and ITU-T H.223 adaptation layer AL1, in the framed or unframed mode as specified below. Other ALs may be used if receivers indicate the capability to do so via ITU-T H.245 negotiation.
+
+#### 6.8.1.1 Buffered ITU-T V.14
+
+In the buffered ITU-T V.14 mode, asynchronous characters and BREAK signals arriving at the ITU-T V.24 interface shall be converted to a synchronous bitstream using the procedures of [ITU-T V.14]. Operation at the ITU-T V.24 interface shall use buffering and flow-control across the DTE-DCE interface as described in clause 7.9 of [ITU-T V.42] and clause 1.3 of [ITU-T V.14].
+
+The resulting bitstream shall be placed into the octets of an unframed AL1 AL-SDU, preserving the original bit ordering (least significant bit first). The unframed AL-SDU should be transferred to the underlying AL in a streaming mode without waiting for the end of the AL-SDU (which will never occur).
+
+If receipt of characters at the ITU-T V.24 interface pauses, the terminal may omit transmission of octets containing only stop bits (because the line is idle), after transmitting the octet containing the final character, plus at least two stop bits.
+
+The receiver shall perform the reverse operation.
+
+#### 6.8.1.2 LAPM/ITU-T V.42
+
+In the LAPM/ITU-T V.42 mode, asynchronous characters and BREAK signals arriving at the ITU-T V.24 interface shall be transferred to the far end using the procedures of [ITU-T V.42] in the LAPM mode. The alternative procedure of Annex A of [ITU-T V.42] is not required.
+
+The procedures of [ITU-T V.42] shall be followed, except that:
+
+- The flag sequence and transparency procedures of clause 8.1.1.2 of [ITU-T V.42] shall not be performed, as the ITU-T H.223 multiplex provides equivalent functions. Instead, the entire content of each frame between the opening and closing flags shall be placed in a single framed AL1 AL-SDU, without application of the zero-bit insertion transparency procedure.
+- The detection phase of [ITU-T V.42] shall be bypassed, proceeding directly to the protocol establishment phase.
+- Aborts shall be sent using the procedure of [ITU-T H.223], instead of the procedure in [ITU-T V.42].
+- Only frames shall be sent; interframe time filling flags shall not be sent.
+
+The receiver shall perform the reverse operations.
+
+If ITU-T V.42 *bis* data compression is to be used, it shall be negotiated in-band to the LAPM/ITU-T V.42 channel according to the procedures of [ITU-T V.42 *bis*].
+
+Since the LAPM/ITU-T V.42 protocol requires a reverse channel for operation, LAPM/ITU-T V.42 logical channels shall be opened using the ITU-T H.245 procedures for opening associated logical channels in each direction of transmission (bidirectional channels).
+
+ITU-T H.324 terminals declaring capability for LAPM/ITU-T V.42 in only one direction of transmission shall support the ITU-T V.42/LAPM protocol for the reverse direction, even if no payload data will be sent on the reverse channel.
+
+#### 6.8.1.3 HDLC frame tunnelling
+
+In the HDLC frame tunnelling mode, HDLC frames arrive at the ITU-T V.24 interface from the data application.
+
+If the ITU-T V.24 interface is operating synchronously, inserted zero bits shall be removed and the entire content of each frame between the opening and closing flags shall be placed in a single framed AL1 AL-SDU, for transmission through the ITU-T H.223 multiplex. Aborts shall be sent using the procedure of [ITU-T H.223]. Only frames shall be sent; flags (including interframe time filling flags) shall not be sent.
+
+If the ITU-T V.24 interface is operating asynchronously, HDLC frames arrive at the ITU-T V.24 interface encoded as a sequence of asynchronous characters using octet-stuffing according to clause 4.5.2 of [ISO/IEC 13239] instead of the usual zero-bit insertion transparency procedure of HDLC. This recognized alternative to the zero-bit insertion procedure makes the implementation of HDLC protocols over asynchronous serial links possible. Typical personal computer serial ports do not support synchronous operation, making this operation mode important. In particular, the PSTN basic mode profile of [ITU-T T.123] specifies this mode of operation.
+
+If operating asynchronously, the terminal shall receive HDLC frames at the ITU-T V.24 interface according to the procedure given in Annex B. After execution of the receiver procedure given there, the entire content of each frame between the opening and closing flags shall be placed in a single framed AL1 AL-SDU, without application of the zero-bit insertion or octet-stuffing transparency procedures, for transmission through the ITU-T H.223 multiplex. Aborts shall be sent using the procedure of [ITU-T H.223]. Only frames shall be sent; flags (including interframe time filling flags) shall not be sent.
+
+The receiver shall perform the reverse operation. The choice of asynchronous or synchronous ITU-T V.24 interface is a local matter and does not need to be signalled to the far end.
+
+NOTE – Since the HDLC octet-stuffing transparency procedure serves only to transport HDLC frames across an asynchronous interface, integrated terminals containing the HDLC protocol (ITU-T T.120, ITU-T H.224 or other) may omit the octet stuffing/unstuffing procedure, directly placing each HDLC frame in an AL-SDU, since the stuffing and unstuffing procedures cancel each other out inside the terminal. However, such integrated terminals shall still signal the HDLC frame tunnelling data protocol, for proper interworking with far-end terminals.
+
+#### **6.8.1.4 Transparent data**
+
+In the transparent data mode, octets arriving at the ITU-T V.24 interface shall be placed directly into the octets of an unframed AL-SDU, preserving the original bit ordering (least significant bit first). No framing or transparency procedure shall be applied. The unframed AL-SDU should be transferred to the underlying AL in a streaming mode without waiting for the end of the AL-SDU (which will never occur).
+
+The receiver shall perform the reverse operation.
+
+NOTE – The transparent data protocol may be considered equivalent to a variable-rate synchronous data channel, as it simply transports octets without any additional framing or protocol.
+
+### **6.8.2 Data applications**
+
+Data applications make use of an underlying data protocol, as described in the previous clause. This clause describes these data applications as if they are resident in an external computer running the application, connected through an ITU-T V.24 interface to the ITU-T H.324 terminal. The ITU-T V.24 interface may be replaced by a logical equivalent. Data applications integrated with the ITU-T H.324 terminal may choose to omit procedures related to the ITU-T V.24 interface which have no net effect on the transmitted bitstream.
+
+#### **6.8.2.1 ITU-T T.120 multimedia teleconferencing applications**
+
+The ITU-T T.120-series of Recommendations is for point-to-point and multipoint audiographic teleconferencing including database access, still image transfer and annotation, application sharing, real-time file transfer, etc.
+
+All ITU-T H.324 terminals offering real-time audiographic conferencing should support the ITU-T T.120 protocol suite.
+
+ITU-T H.324 terminals supporting ITU-T T.120 shall use the PSTN basic mode profile protocol stack specified in [ITU-T T.123], except that when arriving at the ITU-T V.24 interface from the ITU-T T.120 protocol implementation, the HDLC frame tunnelling data protocol described above shall be used. ITU-T H.324 terminals shall declare the ITU-T T.120 capability and mode if, and only if, they are compliant with this paragraph.
+
+Since ITU-T T.120 requires a reverse channel for operation, ITU-T T.120 logical channels shall be opened using the ITU-T H.245 procedures for opening associated logical channels in each direction of transmission (bidirectional channels).
+
+NOTE – ITU-T T.120 data can also be transported as unspecified user data, but this mode is discouraged, since ITU-T H.324 terminals will not be able to automatically negotiate use of ITU-T T.120 in this mode.
+
+#### **6.8.2.2 ITU-T T.84 (SPIFF) point-to-point still image transfer cutting across application borders**
+
+This application supports the point-to-point transfer of ITU-T T.84 (SPIFF – still picture interchange file format) still images (JPEG, JBIG or facsimile group 3/4 coded) through application borders (e.g., a digital photocamera connected through an ITU-T V.24 interface to the sending
+
+ITU-T H.324 terminal, and a digital photoprinter connected through another ITU-T V.24 interface to the receiving ITU-T H.324 terminal).
+
+The file exchange format to be used for ITU and ISO/IEC applications crosscutting application borders is defined in [ITU-T T.84].
+
+[ITU-T H.245] should be used for the determination of still image profiles supported by the end-applications and the selection of an appropriate profile.
+
+The data protocol used shall be LAPM/ITU-T V.42 as described in clause 6.8.1.2.
+
+NOTE – The ITU-T T.120 protocol series [ITU-T T.126] also performs still image transfer, among many other functions, within the framework of audiographic teleconferencing, and is preferred for such applications. [ITU-T T.84] is concerned with passing still images over one or more application borders using the ITU-T | ISO/IEC standardized common file-interchange format. The ITU-T T.84 (SPIFF) file exchange format is backwards compatible with JFIF, the predecessor "*de facto* standard" JPEG file format, widely used in PC applications and on the Internet. [ITU-T T.126] is also compatible with this file format.
+
+#### **6.8.2.3 ITU-T T.434 point-to-point telematic file transfer cutting across application borders**
+
+This application supports the point-to-point transfer of ITU-T T.434 defined telematic files through application borders (e.g., an intelligent memory card connected to the sending ITU-T H.324 terminal, and a computerized database connected through an ITU-T V.24 interface to the receiving ITU-T H.324 terminal).
+
+The data protocol used shall be LAPM/ITU-T V.42 as described in clause 6.8.1.2.
+
+NOTE – The ITU-T T.120 protocol series ([ITU-T T.127], which also uses [ITU-T T.434]) also performs file transfer, among many other functions, within the framework of audiographic teleconferencing, and is preferred for such applications. The ITU-T T.434 application is concerned with point-to-point passing of telematic files over one or more application borders without implementing the entire protocol set of the ITU-T T.120 series, which is indeed needed for file sharing among many users in a collaborative working environment.
+
+#### **6.8.2.4 ITU-T H.224 real-time control protocol for ITU-T H.281 far-end camera control**
+
+[ITU-T H.224] is for real-time simplex device control. The only currently standardized application is [ITU-T H.281] for far-end camera control.
+
+ITU-T H.324 terminals supporting ITU-T H.224 shall use the HDLC frame tunnelling protocol to transport HDLC frames. There shall be no more than one ITU-T H.224 channel in use, and references in [ITU-T H.224] to the LSD channel of [ITU-T H.221] shall be interpreted as referring to the ITU-T H.224 logical channel. The maximum transmission time requirements of [ITU-T H.224] shall be met, with the ITU-T H.224 logical channel considered as operating at 4800 bit/s, regardless of the actual bit rate of the channel.
+
+#### **6.8.2.5 Network link layer**
+
+The network link layer data application supports ISO network layer protocols defined by [ISO/IEC TR 9577], which include Internet Protocol (IP) and IETF point-to-point protocol (PPP), among others. The particular network layer protocol to be used shall be identified in ITU-T H.245 data application capability and data mode messages using the network layer protocol identifier (NLPID) as defined in [ISO/IEC TR 9577].
+
+For the NLPID application, the link layer which is defined for use with asynchronous GSTN modems shall be used. If this link layer uses HDLC framing, the HDLC frame tunnelling protocol shall be supported by the ITU-T H.324 terminal. Otherwise, the transparent data protocol shall be supported by the ITU-T H.324 terminal.
+
+NOTE – Use of the NLPID is extensively described in [IETF RFC 1490].
+
+#### 6.8.2.6 External data ports and unspecified user data
+
+All ITU-T H.324 terminals offering external data ports for transport of unspecified user data shall support both the buffered ITU-T V.14 data protocol mode and the HDLC frame tunnelling mode. Means shall be provided to configure the ITU-T H.324 terminal for ITU-T T.120 protocol on external data ports. If so configured, the HDLC frame tunnelling protocol and ITU-T T.120 capability and mode shall be used by the terminal.
+
+Other data protocols may optionally be used by ITU-T H.245 negotiation.
+
+#### 6.8.2.7 ITU-T T.30 facsimile
+
+This application supports document facsimile transmission according to Annex C of [ITU-T T.30], and is signalled by the **t30fax** data application codepoint in [ITU-T H.245]. The facsimile data channel shall be carried within an ITU-T H.223 logical channel using the AL1 adaptation layer in the segmentable mode. The data channel carrying the ITU-T T.30 protocol shall be opened using the bidirectional logical channel procedures of [ITU-T H.245].
+
+Error correction is inherent in the use of Annex C of [ITU-T T.30] for facsimile communication. Therefore, the HDLC frame tunnelling data protocol shall be used for ITU-T T.30 operation.
+
+NOTE – This ITU-T T.30 operation mode is the same as that used by [ITU-T T.39], and will interwork with ITU-T T.39 terminals in the MSVF mode. However, full conformance with [ITU-T T.39] involves additional requirements beyond those of this Recommendation.
+
+#### 6.8.2.8 ITU-T T.140 text conversation protocol
+
+This application supports text conversation according to [ITU-T T.140], and is signalled and implemented as described in Annex L.
+
+NOTE – In previous versions of this Recommendation, the **t140** data application codepoint in ITU-T H.245 was specified to signal the support of ITU-T T.140 using the AL1 transparent data protocol. This codepoint is no longer to be used for new implementations; instead, the method described in Annex L is to be used. It is believed that no implementations of this mode using the **t140** data application codepoint for signalling have been deployed.
+
+# 7 Terminal procedures
+
+The provision of the communication is made in the following steps:
+
+- Phase A: Call set-up of voiceband channel.
+- Phase B: Initial analogue telephony communication.
+- Phase C: Establishment of digital communication, modem training.
+- Phase D: Initialization.
+- Phase E: Communication.
+- Phase F: End of session.
+- Phase G: Supplementary services and call clearing.
+
+## 7.1 Phase A – Call set-up of voiceband channel
+
+The calling terminal shall request the connection according to procedures for analogue telephony, according to national standards.
+
+When a call is initiated by a terminal which is external to the modem (a separate physical item connected by an interface), the procedures of [ITU-T V.250] shall be used. Upon successful completion of call set-up, the ITU-T H.324 terminal shall proceed to phase B.
+
+## 7.2 Phase B – Initial analogue telephony communication
+
+### 7.2.1 ITU-T V.8 procedure
+
+When the procedures of [ITU-T V.8] are in use, phase B shall be bypassed, proceeding directly to phase C.
+
+### 7.2.2 ITU-T V.8 *bis* procedure
+
+When the procedures of [ITU-T V.8 *bis*] are in use, an optional phase B begins when the called party has answered. Phase B is normal analogue telephony voice mode. In this mode users have the opportunity to speak before proceeding to multimedia telephony.
+
+If the terminal is conditioned to go directly into digital communication mode, phase B shall be bypassed, proceeding directly to phase C. If the terminal is conditioned for initial analogue telephony voice mode, the terminal shall proceed to phase C when:
+
+- the user manually causes the terminal to initiate an ITU-T V.8 *bis* transaction; or
+- the terminal detects an initiation signal from the distant terminal.
+
+## 7.3 Phase C – Establishment of digital communication, modem training
+
+### 7.3.1 ITU-T V.8 procedure
+
+The terminal shall follow the call start-up procedure described in [ITU-T V.8]. The calling terminal should not transmit ITU-T V.8 calling tones CT or CNG, and should transmit calling tone CI. The answer terminal shall support ITU-T V.8 CM/JM exchanges, and shall transmit answer tone without waiting for call signals. ITU-T H.324 terminals should signal the "H.324" ITU-T V.8 call function (value 0x21), and shall not signal an ITU-T V.8 protocol category.
+
+If the ITU-T V.8 start-up procedure detects an ITU-T V.34 modem, the start-up procedure for that modem shall be followed. Upon completion of the modem start-up procedure and establishment of digital communication, the terminal shall proceed to phase D – Initialization.
+
+If the ITU-T V.8 procedure fails to detect an ITU-T V.34 modem, or the handshake and the establishment of the digital connection is not successful after a suitable period the calling terminal may, depending on predetermined configuration, go to telephony mode, disconnect the line, or go to another operating mode more suitable for the detected modem. Such other modes are outside the scope of this Recommendation.
+
+NOTE – The terminal shall wait for a suitable call set-up period, in addition to processing, signal detection and maximum round-trip delays, before deciding on further action.
+
+### 7.3.2 ITU-T V.8 *bis* procedure
+
+The terminal shall follow the call start-up procedure described in [ITU-T V.8 *bis*]. If the ITU-T V.8 *bis* procedure detects that the distant terminal is not capable of ITU-T V.8 *bis*, but is capable of ITU-T V.8, the phase C procedure for ITU-T V.8 (above) shall be followed. If the ITU-T V.8 *bis* procedure detects a distant ITU-T H.324 terminal supporting the capabilities desired for this call, the ITU-T V.34 start-up procedure shall be followed.
+
+Upon completion of the ITU-T V.8 *bis* procedures and establishment of digital communication, the terminal shall proceed to phase D – Initialization.
+
+NOTE – Some successful ITU-T V.8 *bis* transactions result in a return to telephony mode (phase B).
+
+If the ITU-T V.8 *bis* procedure fails, results in a return to analogue telephony, or the handshake and the establishment of the digital connection is not successful after the period specified in [ITU-T V.8 *bis*], the calling terminal may, depending on predetermined configuration, go to telephony mode, disconnect the line, or go to another operating mode more suitable for the detected modem. Such other modes are outside the scope of this Recommendation.
+
+## 7.4 Phase D – Initialization
+
+After digital communication has been established, a minimum of 16 HDLC flags shall be transmitted in order to ensure synchronization. Following this, system-to-system communication shall be initiated using the ITU-T H.245 control channel. Since no multiplex table entries have yet been sent to the receiver, initial control messages shall be sent using multiplex table entry 0.
+
+Terminal system capabilities are exchanged by transmission of the ITU-T H.245 **TerminalCapabilitySet** message. This capability PDU shall be the first message sent. The ITU-T H.245 **MasterSlaveDetermination** message shall also be sent at this time, in which the terminals exchange random numbers, according to the procedure in [ITU-T H.245], to determine the master and slave terminals. ITU-T H.324 terminals shall be capable of operating in both master and slave modes, and shall set **terminalType** to 128 and set **statusDeterminationNumber** to a random number in the range 0 to  $2^{24} - 1$ . Only one random number shall be chosen by the terminal for each call, except in the case of identical random numbers, as described in [ITU-T H.245].
+
+If the initial capability exchange or master/slave determination procedures fail, these should be retried at least two additional times before the terminal abandons the connection attempt and proceeds to phase G.
+
+NOTE – For **terminalType**, the range from 0 to 127 is reserved for possible use by MCUs or other non-terminal devices which may need to be slave at all times, and the range 129 to 255 is reserved for possible use by MCUs or other non-terminal devices which may need to be master at all times.
+
+After these procedures are complete, and the far end's capabilities have been received, the procedures of [ITU-T H.245] may then be used to open logical channels for various information streams. Multiplex table entries may be sent before or after logical channels are opened, but information shall not be transmitted over a logical channel until the channel is open, and an appropriate ITU-T H.223 multiplex table entry has been defined.
+
+### 7.4.1 Exchange of video by mutual agreement
+
+The indication **videoIndicateReadyToActivate**, "video indicate ready-to-activate", is defined in [ITU-T H.245]. Its use is optional, but when used, the procedure shall be as follows:
+
+Terminal X has been set so that video is not transmitted unless, and until, the remote terminal has also indicated readiness to transmit video. Terminal X shall send the indication **videoIndicateReadyToActivate** when the initial capability exchange has been completed, but shall not transmit a video signal until it has received either **videoIndicateReadyToActivate** or incoming video.
+
+A terminal which has not been set in this optional way is not obliged to wait until receipt of **videoIndicateReadyToActivate** or video before initiating its video transmission.
+
+## 7.5 Phase E – Communication
+
+During a session, the procedures for changing logical channel attributes, capability, receive mode, etc., shall be carried out as defined in [ITU-T H.245].
+
+### 7.5.1 Rate changes and retrains
+
+During phase E communication, the modem may retrain or alter its rate of data transmission, with or without momentary disruption of data transmission and loss of data. Upon any such momentary disruption of data transfer, the terminal shall not restart phase D, but shall remain in phase E and execute the normal ITU-T H.324 error recovery procedures according to [ITU-T H.223].
+
+### 7.5.2 Involuntary disconnection
+
+Should the terminal detect involuntary, unrecoverable loss of modem communication, or of the underlying GSTN connection, the terminal shall immediately proceed to phase G, analogue telephony mode or line disconnection, bypassing phase F.
+
+## 7.6 Phase F – End of session
+
+Either terminal may initiate the end of the session. The initiating terminal shall use the following procedure:
+
+- 1) For each logical channel carrying video, it shall stop sending video at the end of a complete picture and then close the logical channel.
+- 2) It shall close all outgoing logical channels carrying data and audio.
+- 3) It shall transmit the ITU-T H.245 message **EndSessionCommand**, and then discontinue all ITU-T H.245 message transmissions. This message shall contain an indication to the far end regarding the mode the terminal will enter after the end of the session (disconnect line, analogue telephony, or other mode).
+- 4) On subsequent receipt of **EndSessionCommand** from the remote end, it shall proceed to phase G, except that if the initiating terminal indicated an intention to disconnect the line after the end of session, the terminal shall not wait for receipt of **EndSessionCommand** from the remote end, but shall proceed directly to phase G.
+
+A terminal receiving **EndSessionCommand** without first having transmitted it, shall:
+
+- a) if the initiating terminal's **EndSessionCommand** message indicated "disconnect line", optionally follow 3) above, then proceed to phase G;
+- b) otherwise, follow 3) above, then proceed to phase G. If possible, the responding terminal should proceed to the new mode indicated in the initiating terminal's **EndSessionCommand** message.
+
+## 7.7 Phase G – Supplementary services and call clearing
+
+If the terminal arrived at phase G by involuntary disconnection, it shall disconnect or revert to analogue telephony, depending on predetermined configuration.
+
+A terminal wishing to terminate a call shall first initiate the end of session procedure described in phase F.
+
+In phase G, the terminal should proceed as it indicated in the **EndSessionCommand** message. If it indicated a change to another digital communication mode, it shall begin the new mode at the equivalent of phase D. Otherwise, it shall initiate the clearance procedures defined in [ITU-T V.34], except that it shall not physically disconnect the GSTN connection if it indicated an intention to revert to analogue telephony mode.
+
+These procedures ensure that:
+
+- the distant terminal does not erroneously invoke a fault procedure;
+- the human user gets the right indications via tones and announcements from the network exchange;
+- relevant messages can be displayed for the human user by the terminal.
+
+### 7.7.1 Reset of ITU-T H.324 session
+
+In phase G, if both the terminal and the far end have the **sessionResetCapability**, defined in Annex J, in **Capability.genericControlCapability**, and the mode indicated in the **EndSessionCommand** message is **gstnOptions.v34H324**, the terminal shall reset the ITU-T H.324 session by moving immediately to phase D without changing communication mode and without disconnecting the
+
+physical connection. Before sending synchronization flags as indicated in phase D, the receiver of the **EndSessionCommand** message with **gstnOptions.v34H324** shall answer with the same message and then transmit one's complemented synchronization flags to distinguish the new session from the old one. The amount of one's complemented synchronization flags transmitted shall be at least 10 consecutive flags. The maximum number of one's complemented synchronization flags transmitted shall be equivalent to the number of synchronization flags possible to be sent in a period of 500 ms. If the initiator of the session reset procedure received one's complemented synchronization flags without receiving the **EndSessionCommand** message first, it shall start transmitting one's complemented synchronization flags of its own and proceed with the procedure.
+
+# 8 Interoperation with other terminals
+
+## 8.1 Speech only terminals
+
+ITU-T H.324 videophones shall support interoperation with analogue speech-only telephones.
+
+## 8.2 ITU-T H.320 multimedia telephone terminals over the ISDN
+
+Interoperation with multimedia telephone terminals over the ISDN [ITU-T H.320] can be provided by:
+
+- using on the ISDN an interworking adapter; or
+- using dual-mode (ISDN and GSTN) terminals on the ISDN.
+
+An ITU-T H.324/ITU-T H.320 interworking adapter is located at the interface between ISDN and GSTN signals. It transcodes the ITU-T H.223 and ITU-T H.221 multiplexes, and the content of control, audio and data logical channels between the ITU-T H.324 and ITU-T H.320 protocols.
+
+In order to ease communication between ITU-T H.324 and ITU-T H.320 terminals via interworking adapters, ITU-T H.324 terminals which support video shall support the ITU-T H.261 video codec in the QCIF picture format so that the additional delay of video transcoding can be avoided. When this mode is in use, interworking adapters shall insert and remove ITU-T H.261 and ITU-T H.263 BCH error correction and error correction framing as appropriate for each terminal type. ITU-T H.324 terminals shall respond to the ITU-T H.245 **FlowControlCommand**, so that transmitted ITU-T H.324 video streams can be matched to the ITU-T H.320 video bit rate in use by the ITU-T H.221 multiplex.
+
+Dual-mode (ITU-T H.320 and ITU-T H.324) terminals on the ISDN shall send ITU-T H.324 GSTN signals by the use of a "virtual modem", which generates and receives an ITU-T V.34 analogue signal encoded as an ITU-T G.711 audio bitstream over the ISDN.
+
+## 8.3 Multimedia telephone terminals over mobile radio
+
+It is expected that multimedia telephone terminals will also be used on mobile radio networks. Rate matching between wireless terminals and GSTN terminals can be achieved by the use of the ITU-T H.245 **FlowControlCommand**. Wireless operation is for further study.
+
+# 9 Optional enhancements
+
+## 9.1 Data facilities
+
+A terminal may have physical I/O ports for external telematic and other equipment, or there may be data applications within the terminal itself. Data transmission may be activated and deactivated by local action.
+
+When a logical channel is opened to carry data originating at a port, the **portNumber** parameter of the ITU-T H.245 **OpenLogicalChannel** message should contain the number of the relevant port, so
+
+that data on the logical channel may be routed to a corresponding port at the far end, if so desired by the far-end user. For example, in the case where a terminal has general purpose physical I/O ports intended for connection to telematic or other equipment, such ports might be labelled "1", "2", "3", etc., up to the number of actual ports.
+
+## 9.2 Encryption
+
+Encryption may optionally be used by ITU-T H.324 terminals. Encryption, including selection of algorithm and key exchange, shall conform to the procedures of [ITU-T H.233] and this Recommendation with the following modifications to the procedures defined in [ITU-T H.233]. The ability to support encryption shall be signalled by the presence of the **h233EncryptionTransmitCapability** and **h233EncryptionReceiveCapability** parameters of the **Capability** message of ITU-T H.245.
+
+In [ITU-T H.233], specific reference is made to [ITU-T H.221] in describing how encryption takes place. In applying ITU-T H.233 to ITU-T H.324 terminals, references to [ITU-T H.221], FAS and BAS channels therein shall be ignored and appropriate substitute Recommendations be taken from this subclause. Messages referred to as carried in the ITU-T H.221 ECS channel shall be re-interpreted as being carried within the **encryptionSE** parameter of the ITU-T H.245 **EncryptionCommand** or encryption initialization vector (EIV) logical channel, as specified below.
+
+### 9.2.1 EncryptionSE messages
+
+ITU-T H.233 session exchange (SE) messages shall be carried in the **encryptionSE** parameter of the ITU-T H.245 **EncryptionCommand** message. Since the ITU-T H.245 control channel is carried on a reliable data link layer using retransmission of errored frames, the error protection bits described in [ITU-T H.233] shall not be applied to SE messages.
+
+The ITU-T H.233 header for SE messages shall have the value binary 00000000, indicating an SE message in a single block, not followed by related blocks.
+
+The ITU-T H.233 media identifier value shall be binary 00000000, which shall indicate encryption of all logical channels except for the EIV and ITU-T H.245 control channels. The use of other values is for further study.
+
+NOTE – Non-standard encryption algorithms may be referenced in SE messages after associating a non-standard algorithm with an ITU-T H.233 algorithm identifier value using the **encryptionAlgorithmID** parameter of the **EncryptionCommand** message.
+
+### 9.2.2 Encryption initialization vector (EIV) channel
+
+The encryption initialization vector (EIV) logical channel is used for the transmission of ITU-T H.233 initialization vector (IV) messages.
+
+To ensure accurate synchronization of the IV messages with the ITU-T H.223 multiplex bitstream, the EIV channel is an independent logical channel which shall be non-segmentable, and shall use adaptation layer AL2 of the ITU-T H.223 multiplex. The entire IV message, exactly as defined in [ITU-T H.233], including error protection bits, shall be placed in a single AL-SDU. The sequence number option of AL2 shall not be used.
+
+Messages carried within the EIV channel shall retain the error protection mechanism of [ITU-T H.233].
+
+### 9.2.3 Encryption procedure
+
+The encrypter shall produce a pseudo-random bitstream (cipher stream) corresponding to all bits output by the ITU-T H.223 multiplex prior to insertion of flags and application of the HDLC zero-bit insertion procedure.
+
+When encryption is activated according to [ITU-T H.233], the ITU-T H.223 bitstream shall, prior to flag insertion and application of the HDLC zero-bit insertion procedure, be exclusive-ORed with the pseudo-random bitstream generated by the encrypter. However, the exclusive-OR procedure shall not be applied to the ITU-T H.223 header octet nor to the octets belonging to the ITU-T H.245 control channel or EIV channel, which shall all be passed transparently to the HDLC zero-bit insertion and flag insertion stage.
+
+For each transmitted ITU-T H.223 header octet or octet belonging to the EIV or control channels, eight bits shall be discarded from the pseudo-random bitstream generated by the encrypter. Nothing is discarded from the pseudo-random bitstream for transmitted flags or for bits added by the HDLC zero-bit insertion process.
+
+The receiver shall apply the reverse procedure.
+
+### 9.2.4 Encryption initialization vectors
+
+Once an encrypted session is in progress, the transmitter should periodically send new IV messages in order to limit the duration of repeated pseudo-random bitstream in the event of a collision with a previously used state of the pseudo-random bitstream generator. The frequency of these messages is left to the discretion of the implementer.
+
+As shown in Figure 3, new initialization vectors (IVs) take effect at the start of the next ITU-T H.223 MUX-PDU following the MUX-PDU containing an IV message. The old IV continues in effect through the entirety of the MUX-PDU containing the IV message, at the end of which any remaining pseudo-random bits generated using the old IV are discarded. In order for the receiver to have time to process the new IV before needing to use it, the transmitter shall wait a minimum time after sending the last octet of the IV message, as specified by the receiver's **h233IVResponseTime** capability, before starting transmission of the next MUX-PDU. If necessary, the transmitter shall send idle flags to meet the receiver's **h233IVResponseTime** requirement.
+
+NOTE – Definition, by the implementer, of an appropriate ITU-T H.223 multiplex table entry allows octets from other logical channels to follow an IV message within the same MUX-PDU so that no transmission bandwidth is squandered in meeting the receiver's IV processing delay requirement.
+
+![Figure 3: Encryption IV synchronization diagram. The diagram shows a sequence of data units: Flag (F), Header octet (H), Logical channel octets (represented by a dashed line), and an Initialization Vector (IV). This is followed by another Flag (F), then a sequence of Flags (F, F, F), a Header octet (H), more Logical channel octets (dashed line), and a final Flag (F). Two arrows labeled 'MUX-PDU' point to the first and second header octets. A horizontal double-headed arrow labeled 'h233IVResponseTime' spans from the end of the IV message to the start of the second MUX-PDU. A vertical arrow labeled 'New IV takes effect here' points to the start of the second MUX-PDU. A legend at the bottom left defines 'F' as Flag, 'H' as Header octet, and '...' as Logical channel octets. The diagram is labeled 'H.324(09)_F03' in the bottom right.](6be06b7dc72bb42afcb3465394667c3b_img.jpg)
+
+Figure 3: Encryption IV synchronization diagram. The diagram shows a sequence of data units: Flag (F), Header octet (H), Logical channel octets (represented by a dashed line), and an Initialization Vector (IV). This is followed by another Flag (F), then a sequence of Flags (F, F, F), a Header octet (H), more Logical channel octets (dashed line), and a final Flag (F). Two arrows labeled 'MUX-PDU' point to the first and second header octets. A horizontal double-headed arrow labeled 'h233IVResponseTime' spans from the end of the IV message to the start of the second MUX-PDU. A vertical arrow labeled 'New IV takes effect here' points to the start of the second MUX-PDU. A legend at the bottom left defines 'F' as Flag, 'H' as Header octet, and '...' as Logical channel octets. The diagram is labeled 'H.324(09)\_F03' in the bottom right.
+
+**Figure 3 – Encryption IV synchronization**
+
+### 9.2.5 Error recovery
+
+In the event of line errors that cause flag emulation, flag erasure or erroneous HDLC zero-bit removal, it is possible that a newly received flag, signifying the end of the previous MUX-PDU, will not align with the octet boundaries of the preceding data. In order to maximize the resilience of the encryption system against synchronization loss under these circumstances, the decryptor should, for each new flag received, re-align its pseudo-random bitstream generator to the nearest octet boundary. This allows recovery from up to at least three zero-bit removal errors between valid flags, although it does not provide any protection against flag emulation or erasure.
+
+In the event that the receiver suspects that it has lost encryption synchronization, it shall send an **encryptionIVrequest** command, except that it should not re-send such commands at intervals less than the maximum expected round-trip response time.
+
+Upon receipt of an **encryptionIVrequest** command, the transmitter shall, at its earliest opportunity, send a new IV message, except that it should ignore **encryptionIVrequest** commands received within the minimum expected round-trip response time since sending the last IV message.
+
+## 9.3 Multilink
+
+[ITU-T H.226] describes a protocol for aggregation of data over multiple independent channels.
+
+Annex F defines the operation of ITU-T H.324 over multiple independent physical connections, aggregated together according to [ITU-T H.226] to provide a higher total bit rate. These connections may be GSTN circuits, or ISDN circuits as defined in Annex D. The use of both GSTN and ISDN connections in the same call is supported.
+
+Annex H defines the operation of H.324/M over up to eight independent physical connections, aggregated together according to the mobile multilink layer defined in that annex to provide a higher total bit rate. These connections are error-prone mobile channels, as defined in Annex C, all having the same transmission rate.
+
+# 10 Multipoint considerations
+
+ITU-T H.324 terminals may be used in multipoint configurations via interconnection through MCUs, as indicated in Figure 4 (note that cascaded MCU operation is for further study).
+
+![Figure 4 – Multipoint configuration diagram showing three MCUs and five Terminals.](d8698aacaeead6dfed9a1e448670a2e4_img.jpg)
+
+The diagram illustrates a multipoint configuration. At the top center is a circle labeled 'MCU'. Below it, two more circles labeled 'MCU' are positioned. The left 'MCU' is connected to the top 'MCU' and to two ovals labeled 'Terminal'. The right 'MCU' is connected to the top 'MCU' and to two ovals labeled 'Terminal'. A small label 'H.324(09)\_F04' is located near the bottom right 'Terminal'.
+
+Figure 4 – Multipoint configuration diagram showing three MCUs and five Terminals.
+
+Figure 4 – Multipoint configuration
+
+## 10.1 Establishment of common mode
+
+MCUs may force terminals into a particular common mode of transmission by sending to the terminal a receive capability set listing only the desired mode of transmission. ITU-T H.324 terminals shall obey the **MultipointModeCommand** message of [ITU-T H.245].
+
+## 10.2 Multipoint rate matching
+
+Since the modems on each link in a multipoint configuration may be operating at different bit rates, MCUs may choose to send ITU-T H.245 **FlowControlCommand** messages to limit the transmitted bit rates to those which can be sent to receivers.
+
+## 10.3 Multipoint lip synchronization
+
+In a multipoint configuration, each terminal may be transmitting a different **H223SkewIndication** message for associated video and audio channels. To enable lip synchronization at receiving
+
+terminals, MCUs shall transmit accurate **H223SkewIndication** messages. MCUs may accomplish this by adding delay to equalize the audio/video skew for all transmitting terminals, or, when switching between broadcasting terminals, may transmit a new **H223SkewIndication** message reflecting the audio/video skew of the current broadcaster.
+
+## 10.4 Multipoint encryption
+
+In a multipoint configuration, the MCU is considered to be a trusted entity. Each port of the MCU encrypts/decrypts the ITU-T H.223 bitstream from the ITU-T H.324 terminal or MCU attached to that port as though it were an ITU-T H.324 terminal in accordance with clause 9.2.
+
+## 10.5 Cascaded MCU operation
+
+Multipoint operation in a cascaded MCU configuration is for further study.
+
+# 11 Maintenance
+
+## 11.1 Loopbacks for maintenance purposes
+
+Some loopback functions are defined in [ITU-T H.245] to allow verification of some functional aspects of the terminal, to ensure correct operation of the system and satisfactory quality of the service to the remote party. The message loopback off (**MaintenanceLoopOffCommand**) requires that all loopbacks currently in effect be turned off.
+
+### 11.1.1 Normal mode
+
+Normal (no loopback) operation mode is illustrated in Figure 5a.
+
+### 11.1.2 System loopback
+
+Operation in system loopback mode is for further study.
+
+### 11.1.3 Media loopback
+
+Media loopback operates at the analogue I/O interface (toward modem). Upon receiving the **mediaLoop** request as defined in [ITU-T H.245], loopback of the content of the selected logical channel shall be activated as close as possible to the analogue interface of the video/audio codec towards the video/audio codec, so that decoded and re-coded media content is looped, as indicated in Figure 5c. While in this mode, the terminal shall respond normally to received data, including ITU-T H.245 messages. Media loopback provides a subjective test of ITU-T H.324 operation through the far-end codec for human user evaluation. It should be used only on video and audio channels.
+
+This loopback is optional, and should be used only on logical channels opened using the bidirectional channel procedures of [ITU-T H.245].
+
+### 11.1.4 Logical channel loopback
+
+Logical channel loopback operates in the ITU-T H.223 multiplex (toward modem). Upon receiving the **logicalChannelLoop** request, each received ITU-T H.223 MUX-SDU for the specified logical channel shall be looped back to the transmitter on the corresponding reverse logical channel, as indicated in Figure 5d. While in this mode, the terminal shall respond normally to received data, including ITU-T H.245 messages.
+
+This loopback is optional, and should be used only on logical channels opened using the bidirectional channel procedures of [ITU-T H.245].
+
+![Diagram a) Normal: Shows a standard system architecture. On the left, a camera and a monitor are connected to a 'Codec' block. The 'Codec' is connected to a 'Multiplex' block, which is in turn connected to a 'Modem' block. Arrows indicate the flow of data from left to right through the components.](5eb69662cc4fa7d0d49b4eb22951c204_img.jpg)
+
+Diagram a) Normal: Shows a standard system architecture. On the left, a camera and a monitor are connected to a 'Codec' block. The 'Codec' is connected to a 'Multiplex' block, which is in turn connected to a 'Modem' block. Arrows indicate the flow of data from left to right through the components.
+
+a) Normal
+
+![Diagram b) System loopback: Shows the same architecture as (a), but with a loopback connection. An arrow branches off from the output of the 'Multiplex' block and loops back into its input, bypassing the 'Modem' block.](e151d3468319b81f042ca232c4d82e4b_img.jpg)
+
+Diagram b) System loopback: Shows the same architecture as (a), but with a loopback connection. An arrow branches off from the output of the 'Multiplex' block and loops back into its input, bypassing the 'Modem' block.
+
+b) System loopback
+
+![Diagram c) Media loopback: Shows the same architecture as (a), but with a loopback connection. An arrow branches off from the output of the 'Codec' block and loops back into its input, bypassing both the 'Multiplex' and 'Modem' blocks.](f5deee2f3301ee351c4008283ffafbb3_img.jpg)
+
+Diagram c) Media loopback: Shows the same architecture as (a), but with a loopback connection. An arrow branches off from the output of the 'Codec' block and loops back into its input, bypassing both the 'Multiplex' and 'Modem' blocks.
+
+c) Media loopback
+
+![Diagram d) Logical channel loopback: Shows the same architecture as (a). Inside the 'Multiplex' block, there are two dashed arrows pointing from the output back to the input. A legend indicates that one dashed arrow represents 'One logical channel only' and the other represents 'Other logical channels'.](107da2e3495b2f24352c9e3b26ec4841_img.jpg)
+
+Diagram d) Logical channel loopback: Shows the same architecture as (a). Inside the 'Multiplex' block, there are two dashed arrows pointing from the output back to the input. A legend indicates that one dashed arrow represents 'One logical channel only' and the other represents 'Other logical channels'.
+
+d) Logical channel loopback
+
+H.324(09)\_F05
+
+**Figure 5 – Loopback**
+
+# Annex A
+
+## Protocol stack for control channel
+
+(This annex forms an integral part of this Recommendation)
+
+This annex defines the data protocol stack for use with the ITU-T H.324 control channel.
+
+## A.1 General
+
+Figure A.1 shows the control channel protocol stack for use with this Recommendation.
+
+![Figure A.1: Protocol stack for ITU-T H.324 control channel. The diagram shows four stacked layers: ITU-T H.245 at the top, followed by SRP or LAPM/ITU-T V.42, then ITU-T H.223 – Framed AL1 and ITU-T H.223 – MUX, and finally the Physical layer (ITU-T V.34 modem) at the bottom. Horizontal lines separate the layers. Below the stack is the label H.324(09)_FA.1.](8c880d6b715587bd710a9ba8414469b1_img.jpg)
+
+ITU-T H.245
+
+---
+
+SRP or LAPM/ITU-T V.42
+
+---
+
+ITU-T H.223 – Framed AL1  
+ITU-T H.223 – MUX
+
+---
+
+Physical layer (ITU-T V.34 modem)
+
+---
+
+H.324(09)\_FA.1
+
+Figure A.1: Protocol stack for ITU-T H.324 control channel. The diagram shows four stacked layers: ITU-T H.245 at the top, followed by SRP or LAPM/ITU-T V.42, then ITU-T H.223 – Framed AL1 and ITU-T H.223 – MUX, and finally the Physical layer (ITU-T V.34 modem) at the bottom. Horizontal lines separate the layers. Below the stack is the label H.324(09)\_FA.1.
+
+**Figure A.1 – Protocol stack for ITU-T H.324 control channel**
+
+The control protocol of [ITU-T H.245] requires a reliable link layer for proper operation.
+
+Two means of transporting **MultimediaSystemControlMessage** messages are defined: simple retransmission protocol (SRP) frames and LAPM/ITU-T V.42 I frames. In the SRP mode, each SRP command frame must be acknowledged with an SRP response frame before the next command can be transmitted. In the LAPM/ITU-T V.42 mode, multiple frames may be sent in a streaming mode, before an acknowledgement is received for the first frame. All ITU-T H.324 terminals shall support the SRP mode, and shall use SRP as the ITU-T H.245 link layer upon initial communication. The LAPM/ITU-T V.42 mode is optional, and is preferred for use by complex terminals.
+
+In both cases, bits produced by the ITU-T X.691 encoding process shall be put into the octets of an information field, with the first bit generated going into the most significant bit (MSB) of the first octet, and progressing down to the least significant bit (LSB) of the last octet. One or more complete ITU-T H.245 **MultimediaSystemControlMessage** messages may be sent in each information field, to be transported in a single SRP or LAPM frame.
+
+When possible, multiple ITU-T H.245 messages should be sent in each single frame in order to reduce the number of round-trip message exchanges and frame header overhead.
+
+NOTE 1 – The specified ITU-T X.691 encoding process produces **MultimediaSystemControlMessage** messages which are each a multiple of 8 bits in length (see clause 10.1.3 of [ITU-T X.691]), so all messages begin on an octet boundary.
+
+ITU-T H.324 terminals capable of using LAPM/ITU-T V.42 as the control channel link layer shall so indicate by setting the **transportWithI-frames** parameter of the **H223Capability** structure true. Such terminals, upon receiving the corresponding indication from the far-end terminal, shall henceforth, and without further notification of intent, proceed to establish an error-corrected
+
+connection according to the procedures given in clause 6.8.1.2 and subsequently transmit control channel messages only using LAPM/ITU-T V.42 for the duration of the connection. The terminal shall, however, transmit a SRP response message in reply to any SRP command message received.
+
+The transition to LAPM/ITU-T V.42 mode shall take place regardless of the state of any ITU-T H.245 transactions in progress; any pending transactions shall proceed using LAPM/ITU-T V.42 for transfer of additional messages.
+
+NOTE 2 – Since the ITU-T H.245 control channel is not considered a data channel, ability to operate the control channel over LAPM/ITU-T V.42 is signalled only in the **transportWithI-frames** parameter of **H223Capability**, and is not signalled as a data protocol.
+
+## A.2 SRP mode
+
+All terminals shall support the transfer of **MultimediaSystemControlMessage** messages using SRP mode. Each SRP frame shall be placed in a single framed AL1 AL-SDU.
+
+NOTE – The procedures of the SRP mode are based on those of XID frame transfer in [ITU-T V.42].
+
+### A.2.1 SRP command frames
+
+SRP command frames, as shown in Figure A.2, shall be used to send ITU-T H.245 control messages. All fields shall be formatted as specified in [ITU-T H.223] (note that these formats are consistent with [ITU-T V.42]).
+
+![](50214d232017279410e9c9db8eb75119_img.jpg)
+
+|                     |                                 |                                                   |                   |
+|---------------------|---------------------------------|---------------------------------------------------|-------------------|
+| Header<br>(1 octet) | Sequence<br>number<br>(1 octet) | Information field<br>(one or more ASN.1 messages) | FCS<br>(2 octets) |
+|---------------------|---------------------------------|---------------------------------------------------|-------------------|
+
+H.324(09)\_FA.2
+
+**Figure A.2 – Format of SRP command frames for MultimediaSystemControlMessage messages**
+
+The SRP command frame header octet shall have the value binary 11111001 (decimal 249). This may be considered equivalent to an HDLC address octet with the DLCI value 62, C/R bit set to 0, and EA bit set to 1.
+
+The sequence number shall be set arbitrarily by a terminal for the first SRP command frame sent and shall be incremented modulo 256 for each new SRP command frame sent. Retransmissions of the same SRP frame, sent according to the procedures below, shall not increment the sequence number, but shall use the same sequence number as the original transmission, so that receivers can distinguish between separate valid messages and retransmissions of a single message (possibly sent in error if the original SRP response frame was lost).
+
+The information field shall contain a whole number of octets, not to exceed 2048 octets, representing one or more ITU-T H.245 **MultimediaSystemControlMessage** messages. The procedure specified by [ITU-T X.691] shall be used to fill any spare bits in the last octet.
+
+The FCS field shall contain a 16-bit CRC, applied to the entire frame content, as described in clause 8.1.1.6.1 of [ITU-T V.42].
+
+### A.2.2 SRP response frames
+
+SRP response frames shall be used to acknowledge correct receipt of SRP command frames from the far end. Each SRP response frame shall consist of a header octet and FCS field only, and shall not contain any other fields.
+
+The SRP response frame header octet shall have the value binary 11111011 (decimal 251). This may be considered equivalent to an HDLC address octet with the DLCI value 62, C/R bit set to 1, and EA bit set to 1.
+
+The FCS field shall contain a 16-bit CRC, applied to the entire frame content, as described in clause 8.1.1.6.1 of [ITU-T V.42].
+
+### **A.2.3 SRP procedure at transmitter**
+
+The SRP procedure makes use of an acknowledgement timer T401 and retransmission counter N400.
+
+The period of T401 is a local matter; the two terminals may operate with different periods of T401. Appendix IV of [ITU-T V.42] shows the various factors that influence T401.
+
+The maximum value of N400 is a local matter; the two terminals may operate with different maximum values of N400. While no default maximum is specified for N400, it should be at least 5.
+
+When the terminal transmits a new SRP command frame, timer T401 shall then be started and the retransmission counter, N400, reset. No additional SRP command frames shall be sent until a response SRP frame with correct header and FCS is received, or timer T401 expires.
+
+If a valid SRP response frame is received, a new SRP command frame, with an incremented sequence number, may be transmitted.
+
+If timer T401 expires before receipt of a valid SRP response frame, the terminal shall:
+
+- retransmit the SRP command (with the same sequence number) as above;
+- restart timer T401; and
+- increment the retransmission counter (N400).
+
+After retransmission of the SRP command N400 times and failure to receive a valid SRP response, the terminal shall consider modem communication to be lost, and take appropriate action.
+
+### **A.2.4 SRP procedure at receiver**
+
+On receipt of an SRP command frame with correct header and FCS, the receiving terminal shall acknowledge by transmitting an SRP response frame within 500 milliseconds.
+
+If the received SRP command frame has the same sequence number as the previously received command frame, it shall not be passed to the ITU-T H.245 layer, since it is a retransmission of an already-processed command.
+
+Receipt of all other frames shall be ignored, except that if the terminal has signalled ability to operate in LAPM/ITU-T V.42 mode, the receiver shall check the DLCI value of the received frame header. If the DLCI value matches that specified for use in the LAPM/ITU-T V.42 mode, the terminal shall respond according to the procedures of LAPM/ITU-T V.42, as described below.
+
+### **A.2.5 Numbered SRP response frames (NSRP)**
+
+The standard SRP response frame does not include a sequence number, which can result in transmitter uncertainty as to which SRP command frame is being acknowledged. Therefore, this optional numbered SRP response frame (NSRP) procedure is strongly preferred. Use of the NSRP allows smaller values of T401 and more reliable control channel operation.
+
+Each NSRP response frame, as shown in Figure A.3, shall consist of a header octet, sequence number and FCS field.
+
+![](cbb2d311b20781a595488445ded48d0a_img.jpg)
+
+|                     |                                 |                   |
+|---------------------|---------------------------------|-------------------|
+| Header<br>(1 octet) | Sequence<br>number<br>(1 octet) | FCS<br>(2 octets) |
+|---------------------|---------------------------------|-------------------|
+
+H.324(09)\_FA.3
+
+**Figure A.3 – Format of NSRP response frame**
+
+The NSRP response frame header octet shall have the value binary 11110111 (decimal 247). This may be considered equivalent to an HDLC address octet with the DLCI value 61, C/R bit set to 1, and EA bit set to 1. The FCS field shall contain a 16-bit CRC, applied to the entire frame content, as described in clause 8.1.1.6.1 of [ITU-T V.42].
+
+Terminals supporting NSRP shall signal this capability via [ITU-T H.245].
+
+Terminals which support the NSRP mode shall transmit SRP response frames until receipt of the NSRP capability in [ITU-T H.245]. After that time, only NSRP response frames shall be sent to acknowledge received SRP command frames.
+
+Terminals shall accept received SRP response frames until receipt of the first NSRP response frame. After that time, only NSRP response frames shall be accepted.
+
+All other SRP procedures are as described in previous clauses.
+
+## A.3 LAPM/ITU-T V.42 mode
+
+Terminals may optionally support the transfer of **MultimediaSystemControlMessage** messages using LAPM/ITU-T V.42.
+
+SRP frames shall be used to transfer **MultimediaSystemControlMessage** messages before LAPM/ITU-T V.42 transmission is initiated but shall not be used for this purpose after LAPM/ITU-T V.42 transmission has been used.
+
+In the LAPM/ITU-T V.42 mode, the information field, as defined for the SRP mode above, shall be placed into a single LAPM/ITU-T V.42 I-frame and transferred using procedures of LAPM/ITU-T V.42, as described in clause 6.8.1.2, except that the procedures for opening logical channels shall not be used, as the control channel is considered already open at the start of digital communication.
+
+The address field shall be one octet with the 6-bit DLCI field set to binary 111111 (decimal 63).
+
+ITU-T V.42 *bis* data compression should not be used.
+
+Default values for all ITU-T V.42 parameters shall be as specified in [ITU-T V.42], except for N401, maximum number of octets in an information field, which shall have a default value of 2048 octets, in order to accommodate large capability sets.
+
+## A.4 WNSRP control frame signalling on the control channel
+
+Windowed NSRP (WNSRP) control frames shall be assigned to the control channel with LCN 0 using multiplex table entry 15.
+
+For backward compatibility reasons, SRP/NSRP command and response frames, depending on the involved multiplexer level, are the only control frames sent using multiplex table entry 0 before receiving any indication from the remote terminal regarding its capabilities.
+
+A receiver terminal that does not support multiplex table entry 15 from the beginning of the call shall ignore it as stated in clause 6.4.1.1 of [ITU-T H.223]. Furthermore, a receiver terminal receiving a control frame using multiplex table entry 15 with a header it does not recognize shall ignore that frame.
+
+### A.4.1 WNSRP command frames
+
+The WNSRP command frame format is the same as that of an SRP command frame except that the WNSRP command frame header octet shall be 11110001 (decimal 241).
+
+![](60ffbad6c0fb7371a57fe8f267d2d141_img.jpg)
+
+|                     |                                 |                                                   |                   |
+|---------------------|---------------------------------|---------------------------------------------------|-------------------|
+| Header<br>(1 octet) | Sequence<br>number<br>(1 octet) | Information field<br>(one or more ASN.1 messages) | FCS<br>(2 octets) |
+|---------------------|---------------------------------|---------------------------------------------------|-------------------|
+
+H.324(09)\_FA.4
+
+**Figure A.4 – Format of WNSRP command frames for  
+MultimediaSystemControlMessage messages**
+
+The standard SRP command frame does not allow the use of the sequence number for a window of SRP commands, which causes each SRP command frame to be acknowledged using a full round-trip. During call set-up, the number of control messages passed between the terminals can reach more than 5, which accounts for too many round-trips for call set-up. Use of the WNSRP allows reduction of the sequential round-trips needed by parallelizing them.
+
+Terminals supporting WNSRP shall support the following additional capabilities:
+
+- Terminals do not signal this capability via [ITU-T H.245].
+- For WNSRP mode detection, terminals shall transmit WNSRP command frames using multiplex table entry 15 until the receipt of the first incoming WNSRP response or command frame. After switching to WNSRP mode, all WNSRP control frames shall be sent using multiplex table entry 0.
+- Terminals shall transmit both SRP command frames and WNSRP command frames until the receipt of the first incoming WNSRP response or command frame, in which case they shall stop sending SRP command frames and switch to the WNSRP mode only.
+- Received SRP command frames shall always be acknowledged using SRP/NSRP response frames.
+- Terminals shall have an additional mode counter N402. The maximum value of this mode counter is a local matter; the two terminals may operate with different mode counters. The minimal value of this mode counter N402 shall be 1. On receipt of an SRP or NSRP response, frame N402 shall be incremented.
+- Terminals that do not receive WNSRP response or command frames, but receive N402 number of SRP or NSRP response frames, shall stop sending WNSRP command frames and use SRP or NSRP only.
+- The sequence number used for the first SRP and WNSRP command frames shall be zero and shall be incremented by modulo 256 for each new SRP and WNSRP command frame sent. This allows sending of multiple WNSRP command frames from the beginning of the call.
+- Terminals that switched to WNSRP mode cannot revert back to using SRP or NSRP.
+
+### A.4.2 WNSRP response frames
+
+The WNSRP response frame format is the same as that of an NSRP response frame except that the WNSRP response frame header octet shall be 11110011 (decimal 243).
+
+WNSRP response frames shall be used to acknowledge correct receipt of WNSRP command frames from the far end.
+
+![](0a42e05c07941450f34e4f7117725834_img.jpg)
+
+|                     |                                 |                   |
+|---------------------|---------------------------------|-------------------|
+| Header<br>(1 octet) | Sequence<br>number<br>(1 octet) | FCS<br>(2 octets) |
+|---------------------|---------------------------------|-------------------|
+
+H.324(09)\_FA.5
+
+**Figure A.5 – Format of WNSRP response frame**
+
+After switching to WNSRP mode, the terminal shall stop transmitting SRP command frames and start transmitting one or more WNSRP command frames without waiting for the response of the previous transmitted frame. Each transmitted WNSRP command frame shall make use of an acknowledgement timer T401 and a retransmission counter N400.
+
+### A.4.3 WNSRP procedure at the transmitter
+
+The WNSRP procedure makes use of the same acknowledgement timer T401 and the retransmission counter N400 that are used for the SRP procedure in clause A.2.3.
+
+The period of T401 is a local matter; the two terminals may operate with different periods of T401. Appendix IV of [ITU-T V.42] shows the various factors that influence T401.
+
+The maximum value of N400 is a local matter; the two terminals may operate with different maximum values of N400. While no default maximum is specified for N400, it should be at least 5.
+
+Each WNSRP command frame shall be associated with its own acknowledgement timer T401 and a retransmission counter N400.
+
+When the terminal transmits a new WNSRP command frame, timer T401 shall then be started for that specific command frame and the retransmission counter, N400, reset.
+
+A new WNSRP command frame can be sent by incrementing the sequence number, without the need to wait for a WNSRP response frame on pending WNSRP command frames.
+
+The transmitter shall store each WNSRP command frame until it receives the WNSRP response frame that acknowledges its receipt.
+
+If a valid WNSRP response frame is received for a WNSRP command frame, the associated timer T401 shall be stopped.
+
+If timer T401 expires before receipt of a valid WNSRP response frame for a given WNSRP command frame, the terminal shall:
+
+- retransmit the WNSRP command (with the same sequence number) as above;
+- restart timer T401; and
+- increment the retransmission counter (N400).
+
+On receipt of a WNSRP response frame, the terminal shall:
+
+- retransmit any WNSRP command that was created before the acknowledged WNSRP command frame;
+- restart timer T401 for the retransmitted WNSRP commands; and
+- increment the retransmission counter (N400) for the retransmitted WNSRP commands.
+
+NOTE – This retransmission reduces the timeout on WNSRP command frames that the transmitter knows it will not get acknowledgements for.
+
+After retransmission of the WNSRP command N400 times and failure to receive a valid WNSRP response, the terminal shall consider modem communication to be lost, and take appropriate action.
+
+### **A.4.4 WNSRP procedure at the receiver**
+
+On receipt of a WNSRP command frame with correct header and FCS, the receiving terminal shall acknowledge by transmitting a WNSRP response frame.
+
+If the received WNSRP command frame has the same sequence number as the previously received command frame, it shall not be passed to the ITU-T H.245 layer, since it is a retransmission of an already-processed command.
+
+If the received WNSRP command frame has a sequence number that is higher than the expected sequence number, the receiver shall store the WNSRP command frame until the receipt of the expected sequence number frame(s) and only then forward the stored WNSRP command frame to the ITU-T H.245 layer. If the receiver cannot store the WNSRP command frame (because its window is too small or because of low memory) it shall ignore the WNSRP command frame and shall not send an acknowledgement for the ignored WNSRP command frame.
+
+On receipt of the first SRP command frame with a sequence number other than zero, the terminal shall consider the call as a call without WNSRP and revert to using SRP or NSRP.
+
+# Annex B
+
+## HDLC frame structure transparency for asynchronous transmission
+
+(This annex forms an integral part of this Recommendation)
+
+When operating in the HDLC frame tunnelling mode, the ITU-T H.324 terminal shall implement at the asynchronous ITU-T V.24 interface the following procedures taken from clause 4.5.2 of [ISO/IEC 13239].
+
+The control escape octet is a transparency identifier that identifies an octet occurring within a frame to which the following transparency procedure is applied. The encoding of the escape octet is given in Figure B.1.
+
+![Diagram of the control escape octet for HDLC frame tunnelling procedure. It shows an 8-bit octet: 01111101. Bit 8 is 0, bits 7-4 are 1, bit 3 is 1, bit 2 is 0, and bit 1 is 1. An arrow labeled 'Complemented bit' points to bit 6 (the second '1'). An arrow labeled 'First bit transmitted' points to bit 1 (the last '1'). The text 'H.324(09)_FB.1' is below the diagram.](73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg)
+
+|   |   |   |   |   |   |   |   |
+|---|---|---|---|---|---|---|---|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 |
+| 0 | 1 | 1 | 1 | 1 | 1 | 0 | 1 |
+
+Complemented bit —————↑  
+H.324(09)\_FB.1                      ↑ First bit transmitted
+
+Diagram of the control escape octet for HDLC frame tunnelling procedure. It shows an 8-bit octet: 01111101. Bit 8 is 0, bits 7-4 are 1, bit 3 is 1, bit 2 is 0, and bit 1 is 1. An arrow labeled 'Complemented bit' points to bit 6 (the second '1'). An arrow labeled 'First bit transmitted' points to bit 1 (the last '1'). The text 'H.324(09)\_FB.1' is below the diagram.
+
+**Figure B.1 – Control escape octet for HDLC frame tunnelling procedure**
+
+The transmitter shall examine the frame content between the opening and closing flag sequences (01111110) including the address control and FCS fields and, following completion of the FCS calculation, shall:
+
+- upon the occurrence of the flag or a control escape octet, complement the 6th bit of the octet; and
+- insert a control escape octet immediately preceding the octet resulting from the above prior to transmission.
+
+The receiver shall examine the frame content between the two flag octets and shall, upon receipt of a control escape octet and prior to FCS calculation:
+
+- discard the control escape octet; and
+- restore the immediately following octet by complementing its 6th bit.
+
+Other octet values may optionally be included in the transparency procedure by the transmitter.
+
+# Annex C
+
+# Multimedia telephone terminals over error-prone channels
+
+(This annex does not form an integral part of this Recommendation)
+
+## C.1 Abstract
+
+This annex describes specific issues to allow the use of ITU-T H.324 terminals in error-prone transmission environments. These issues include specific options for ITU-T H.324 terminals, e.g.:
+
+- the mandatory use of NSRP;
+- the use of robust versions of the terminal multiplexer (several different levels of robustness are provided);
+- procedure for level set-up;
+- procedure for dynamic change between levels during a session.
+
+## C.2 General
+
+This annex describes multimedia terminals that use a robust multiplexing procedure to improve operation over error-prone channels. In this annex, terminals supporting robust multiplexing will be referred to as "mobile terminals". Except as noted below, all features of ITU-T H.324 terminals apply to these terminals. Four different multiplexer levels are described, offering progressively increased robustness at the cost of progressively increased overhead and complexity.
+
+- ITU-T H.223 level 0: This term is used to describe [ITU-T H.223].
+- ITU-T H.223 level 1: Described in Annex A of [ITU-T H.223]. The HDLC flag in ITU-T H.223 used to delimit MUX-PDUs in Level 0 is replaced with a longer flag that leads to improved MUX-PDU synchronization. HDLC bit stuffing is not used. The control channel segmentation and reassembly layer (CCSRL) is introduced for the transmission of the control channel. The transmitter side shall take necessary precautions to prevent possible flag emulation for the control channel. Flag emulation can be prevented, e.g., by detecting N 16-bit flags in each MUX-SDU for the channel and by breaking the SDU into N+1 segments. This may also apply to data channels.
+- ITU-T H.223 level 2: Described in Annex B of [ITU-T H.223]. Includes the features of Annex A of [ITU-T H.223]. In addition, the header describing the MUX-PDU contents includes error protection.
+- ITU-T H.223 level 3: Described in Annex C of [ITU-T H.223]. Includes the features of Annex B of [ITU-T H.223]. In addition, error protection and other features are provided to increase the protection of the AL-PDUs. Described in Annex D of [ITU-T H.223] as an optional definition of Annex C of [ITU-T H.223].
+
+In addition to the hierarchy offered by the level structure, some of the multiplex levels contain options.
+
+If the terminal is connected to an octet-oriented network interface, the transmitter shall align the first transmitted bit to the network octet timing. Note that the MUX-PDU of ITU-T H.223 level 1 and higher levels have an octet-aligned structure. Therefore, the receiver may use the octet timing information from the network interface to detect the start of a MUX-PDU to reduce the mis-synchronisation.
+
+Mobile terminals shall support the NSRP and the SRP mode of Annex A. If both terminals start the session in level 0 initially, the SRP mode shall be used. Otherwise, both terminals shall start with NSRP mode.
+
+If both terminals in a session support level 3 of [ITU-T H.223], then adaptation layers AL1M, AL2M, and AL3M as defined in level 3 of [ITU-T H.223] may also be used in Annexes A and B of [ITU-T H.223] (levels 1 and 2). However, bidirectional channels shall use either the ITU-T H.223 adaptation layers or the Annex C of [ITU-T H.223] adaptation layers for level 3 of [ITU-T H.223], but not a mixture of the two.
+
+It is possible that the level may differ in the two directions of a session.
+
+## **C.3 Changes to procedures**
+
+The procedures to be used when making and using a mobile terminal based on a robust multiplexing protocol are exactly the same as those for this Recommendation with the following exceptions:
+
+- Mobile terminals may be implemented with any appropriate wireless interface in place of the ITU-T V.34 modem. The specification of this interface is not within the scope of this annex. All references to the "ITU-T V.34 modem" in this Recommendation shall for wireless terminals be replaced with "wireless interface".
+- If ITU-T V.34 is not used, ITU-T V.8 shall not be used.
+- All ITU-T H.324 terminals should support Annex C of [ITU-T G.723.1].
+
+## **C.4 Interworking**
+
+Since all mobile terminals support ITU-T H.223 level 0, no interworking function is needed when communicating with an ITU-T H.324 terminal that does not support any of the robust multiplexing annexes (Annexes A, B, C and D of [ITU-T H.223]).
+
+## **C.5 Terminal procedures**
+
+The steps for provision of communication are as listed in clause 7, with the following modifications:
+
+- Depending on the access procedures to be used for wireless telephony, phase A and phase B may be bypassed.
+- Phase C: The terminal shall establish digital communications using local standards.
+- Phase D: The value of timer T401 shall be defined using the procedures in Annex E. The transmission of 16 consecutive HDLC flags is replaced with the level set-up procedure defined in clause C.6.
+- Phase G: If the terminal arrived at phase G by involuntary disconnection, it shall disconnect or revert to the set-up procedures in phases A and C, depending on predetermined configuration.
+
+## **C.6 Initialization of multiplex level at the start of a session**
+
+All mobile terminals based on this Recommendation support level 0. However, if two terminals want to establish connection in an error-prone environment, it is more likely that this will succeed in the higher levels.
+
+This set-up procedure describes a method for achieving the highest level supported by both terminals. It is used after the physical line has been established and before any capability exchange (phase D) for both terminals take place. This procedure is not used in ITU-T H.223 level 0; however, it shall be used in all terminals which support level 1 or higher, unless outband signalling for this purpose is available. The use of out-of-band signalling is for further study.
+
+### C.6.1 Definition of stuffing sequences
+
+The level set-up procedure shall use the stuffing methods described in the appropriate Recommendations as listed in Table C.1. The stuffing sequences are also used when the entire ITU-T H.223 multiplex is limited by the **FlowControlCommand**.
+
+**Table C.1 – Definition of stuffing sequences according to Recommendations**
+
+| Level | Stuffing sequence                                                            | Comments                            |
+|-------|------------------------------------------------------------------------------|-------------------------------------|
+| 0     | Consecutive HDLC flags                                                       | See clause 6.3.1 of [ITU-T H.223]   |
+| 1     | Consecutive PN flags                                                         | See clause A.2.1.1 of [ITU-T H.223] |
+| 2     | Consecutive combination of PN flag + header field (MC = 0000, MPL = 0000000) | See clause B.3.2.3 of [ITU-T H.223] |
+| 3     | Consecutive combination of PN flag + header field (MC = 1111, MPL = 0000000) | See clause C.3.1 of [ITU-T H.223]   |
+
+### C.6.2 Definition of level set-up procedure
+
+Each terminal shall start transmitting the stuffing sequence of its highest supported level. The terminal shall also search for the stuffing sequences at its receiving entity until it recognizes that the other terminal also supports either:
+
+- a) the same level; or
+- b) a lower level.
+
+If the other terminal supports the same level, the procedure described in phase D of the call set-up procedure in this Recommendation shall be used.
+
+If the terminal detects a stuffing sequence of a level that is lower than its own highest supported level, it shall immediately change the stuffing sequence of its transmitting entity according to the detected lower level. This ensures that all sessions will be initialized with both terminals operating at the same level. Then the terminals shall continue with the procedure described in phase D of the call set-up procedure in this Recommendation.
+
+Each terminal shall start searching for the stuffing sequence of level 0 first. It should be noted that ITU-T H.223-compliant terminals will send a sequence of at least 16 consecutive HDLC flags.
+
+For improving reliability, the receiving entity may only detect a stuffing sequence if it was sent  $n$  times, e.g.,  $n = 5$ . However, this is only valid for the level set-up procedure.
+
+The stuffing mode shall be determined entirely by the multiplex level, and has no dependence on the adaptation layer used.
+
+If both terminals start with level 3, the stuffing mode of Annex C of [ITU-T H.223] shall be used, even if one channel is opened in AL1, AL2 or AL3.
+
+### C.6.3 Definition of the parameters for the control channel
+
+After both terminals are running in the same level, the highest supported level is known for both terminals. For achieving a very error-robust control channel (logical channel 0), the control channel shall be defined according to the highest level (see Table C.2).
+
+The CCSRL defined in this annex shall be used by all mobile levels to transport the control channel.
+
+**Table C.2 – Definition of the parameters of the control channel according to the level**
+
+| Level | Definition of the parameters                                                                                                                        | Comments |
+|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------|
+| 0     | The same as in clause 6.5.4                                                                                                                         |          |
+| 1     | The same as in clause 6.5.4, except that NSRP or LAPM/ITU-T V.42 as defined in Annex A shall be used, and CCSRL defined in this annex shall be used |          |
+| 2     | The same as level 1                                                                                                                                 |          |
+| 3     | The same as level 1                                                                                                                                 |          |
+
+This configuration shall not be changed during the entire session even if the levels for the other channels are changed to lower levels.
+
+### C.6.4 Definition of other parameters
+
+The minimum size of the send buffer,  $B_s$ , for AL1M and AL3M shall be set to 4096 octets.
+
+## C.7 Dynamic change of level or option during session
+
+The procedure described below for changing multiplex options during a session assumes that a capabilities exchange has taken place between a receiver (terminal A) and a transmitter (terminal B), and that an ITU-T H.245 command for a level change will be sent by the receiver terminal to the transmitter terminal. A terminal, which has the capability to change ITU-T H.223 multiplex levels or options during a session, shall set **modeChangeCapability** in **mobileOperationTransmitCapability** to true. Levels and options supported by the terminal are indicated using the codepoint in **mobileOperationTransmitCapability**.
+
+A terminal, which has the above capability and has received the ITU-T H.245 message with **modeChangeCapability** of true, may start the ITU-T H.223 mode change procedure, illustrated in Figure C.1. Only levels supported by both terminals may be commanded. Note that the "replacementFor" procedure described in [ITU-T H.245] may be used when changing from a mobile adaptation layer (ALXM) to a regular ITU-T H.223 adaptation layer (ALX) or vice versa.
+
+The recommended procedure for changing levels and level option between mobile terminals is the following:
+
+- 1) The receiver side of terminal A sends the ITU-T H.245 command **H223MultiplexReconfiguration.h223ModeChange** to the corresponding transmitter side in terminal B indicating that a level change has to be made.
+- 2) Soon after detecting this command, the transmitter side of terminal B shall:
+  - stop transmitting MUX-PDUs with payload;
+  - begin transmitting successive ones complemented synchronization flags of the current level. The number of ones complemented synchronization flags transmitted shall be at least 10. The maximum number of ones complemented synchronization flags transmitted should be equivalent to the number of synchronization flags possible to be sent in a period of 500 ms;
+  - begin transmitting valid MUX-PDUs of the new level.
+- 3) The receiver side of terminal A uses the transition between the last ones complemented synchronization flag of the series in step 2 and the first regular (non-complemented) synchronization flag of the new level to synchronize to the multiplex of the new level.
+
+If terminal A does not receive the successive complemented synchronization flags within the value specified by T401 plus a margin, terminal A should restart this procedure.
+
+If terminal B receives a command to change to a level option in which it already is, terminal B shall take no action.
+
+While servicing an option change command, terminal B shall not initiate an option change procedure for the other direction.
+
+![Sequence diagram illustrating the level or option change procedure between Terminal A (receiver side) and Terminal B (transmitter side).](789ee0a267b24f34bd1f45313e86c9a4_img.jpg)
+
+The diagram shows the interaction between Terminal A (receiver side) and Terminal B (transmitter side) during a level or option change procedure. Both terminals start at Level j. Terminal A initiates the change by sending an 'ITU-T H.245 change' and 'ITU-T H.223 multiplex option command' to Terminal B. Terminal B responds with 'Current level' and 'Is Complement sync flags B → A'. Terminal A then sends a series of messages labeled (1), (2), ..., (m). Finally, Terminal B sends 'Normal sync flags of the new level B → A' to Terminal A, and Terminal A changes to level k. A timer T401 is shown on the receiver side. The diagram is labeled H.324(09)\_FC.1.
+
+Sequence diagram illustrating the level or option change procedure between Terminal A (receiver side) and Terminal B (transmitter side).
+
+**Figure C.1 – Level or option change procedure**
+
+Note that after changing from level 0 to some higher levels, MUX-PDU octet alignment shall be preserved. Therefore, the transmitter shall add as many "0" bits after the level change sequence as necessary to octet align the first synchronization flag of the new level. In the transmitter, the reference for the octet alignment is the first bit of the first transmitted synchronization flag. In the receiver, the reference for the octet alignment is the first bit of the first detected synchronization flag in the initial level set-up procedure.
+
+## C.8 Control channel definition for mobile terminals
+
+Annex A defines the protocol stack for control channels for use with generic ITU-T H.324 terminals. For mobile applications, however, a reliable link layer may not be available under certain high bit error rate channels. These high bit error rates make the successful transmission of large ITU-T H.245 messages unlikely, in particular the capability exchange message. This problem is circumvented by defining a segmentation layer between the ITU-T H.245 and NSRP or LAPM/ITU-T V.42 layers (see Annex A), as illustrated in Figure C.2. This modified protocol stack shall be used for the control channel in terminals defined by this annex.
+
+![Protocol stack diagram for ITU-T H.324 control channel. The stack consists of five layers: ITU-T H.245 at the top, followed by Control channel segmentation and reassembly layer (CCSRL), NSRP or LAPM/ITU-T V.42, ITU-T H.223 – Framed AL1 and ITU-T H.223 – MUX, and Physical layer at the bottom. Horizontal lines separate the layers. A label H.324(09)_FC.2 is at the bottom right.](701bc79e78b382bcfd3ba85597dbb9c3_img.jpg)
+
+H.324(09)\_FC.2
+
+Protocol stack diagram for ITU-T H.324 control channel. The stack consists of five layers: ITU-T H.245 at the top, followed by Control channel segmentation and reassembly layer (CCSRL), NSRP or LAPM/ITU-T V.42, ITU-T H.223 – Framed AL1 and ITU-T H.223 – MUX, and Physical layer at the bottom. Horizontal lines separate the layers. A label H.324(09)\_FC.2 is at the bottom right.
+
+**Figure C.2 – Protocol stack for ITU-T H.324 control channel**
+
+### C.8.1 Control channel segmentation and reassembly layer (CCSRL)
+
+#### C.8.1.1 Framework of CCSRL
+
+CCSRL is designed for segmenting **MultimediaSystemControlMessage** messages (CCSRL-SDUs) into one or more segments (CCSRL-PDUs). The CCSRL user shall always be [ITU-T H.245].
+
+#### C.8.1.2 Primitives exchanged between CCSRL and the CCSRL user
+
+The information exchanged between CCSRL and the CCSRL user includes the following primitives:
+
+- CCSRL-DATA.request (CCSRL-SDU).
+- CCSRL-DATA.indication (CCSRL-SDU).
+
+##### C.8.1.2.1 Description of primitives
+
+- CCSRL-DATA.request: This primitive is issued by the CCSRL user to CCSRL to request the transfer of an CCSRL-SDU to a corresponding CCSRL user.
+- CCSRL-DATA.indication: This primitive is issued to an CCSRL user by CCSRL to indicate the arrival of an CCSRL-SDU.
+
+##### C.8.1.2.2 Description of parameters
+
+- CCSRL-SDU: This parameter specifies the information exchanged between CCSRL and the CCSRL user. The length of the CCSRL-SDU may be variable. Each transmitted CCSRL-SDU shall contain an integral number of octets. The maximum size of CCSRL-SDUs that a CCSRL receiver can accept shall be 256 octets.
+
+NOTE – The maximum size of CCSRL-SDUs is 256 octets, even though the maximum ITU-T H.245 **MultimediaSystemControlMessage** message length is 2048 octets according to clause A.2.1. This effectively limits the maximum **MultimediaSystemControlMessage** message length to 256 octets for "H.324/M" systems. This limitation is required for interworking with deployed "H.324/M" endpoints. Sending more than 256 octets in a single CCSRL-SDU is for further study.
+
+- CCSRL-PDU: This parameter specifies the information exchanged between the CCSRL and the lower layer. The length of the CCSRL-PDU is variable.
+
+#### C.8.1.3 Functions of CCSRL
+
+CCSRL provides the function of segmenting an CCSRL-SDU containing one or more ASN.1 messages (encoded as defined in [ITU-T X.691]) into one or more CCSRL-SDU segments.
+
+#### C.8.1.4 Format and coding of CCSRL
+
+The format of the CCSRL-PDU is illustrated in Figure C.3.
+
+![Diagram of CCSRL-PDU format showing a header field and a payload field.](fe7304192caf64cda93b580c5e7e5c06_img.jpg)
+
+The diagram illustrates the structure of a CCSRL-PDU. It consists of two main parts: a header and a payload. The header is a single octet, divided into 8 bits (numbered 8 to 1 from left to right), labeled as the 'Last segment (LS) field (1 octet)'. The payload is one or more octets, labeled as 'CCSRL-PDU payload (1 or more octets)'. A vertical double-headed arrow on the left indicates the entire structure is the 'CCSRL-PDU'. On the right, the word 'Octet' is followed by a vertical list of numbers: 1, 2, ..., indicating the sequence of octets. Below the diagram, the text 'H.324(09)\_FC.3' is present.
+
+Diagram of CCSRL-PDU format showing a header field and a payload field.
+
+Figure C.3 – CCSRL-PDU format
+
+##### C.8.1.4.1 Last segment (LS) field
+
+The 8-bit LS field indicates the last segment of an CCSRL-SDU. It shall be set to "1111 1111" on the CCSRL-PDU containing the last segment of an CCSRL-SDU. It shall be set to "0000 0000" otherwise. All other combinations for an LS field are invalid.
+
+##### C.8.1.4.2 CCSRL-PDU payload field
+
+The payload field of an CCSRL-PDU shall contain an CCSRL-SDU segment of at least one octet. The first octet of the CCSRL-PDU payload field shall be the first octet of the CCSRL-SDU segment.
+
+#### C.8.1.5 Procedures for encoding
+
+Information received from the CCSRL user in an CCSRL-SDU by means of an CCSRL-DATA.request primitive shall be passed to the layer below using the following procedure:
+
+- i) break the CCSRL-SDU into an appropriate number of segments;
+- ii) for each CCSRL-SDU segment:
+  - a) set LS to "1111 1111" if this is the last segment of an CCSRL-SDU. Otherwise, set LS to "0000 0000";
+  - b) pass the generated CCSRL-PDU to the underlying layer.
+
+#### C.8.1.6 Procedures for error control
+
+An invalid CCSRL-PDU is one which:
+
+- does not contain an integral number of octets; or
+- is longer than the maximum CCSRL-PDU size; or
+- is equal to 0 octet; or
+- contains an invalid LS field.
+
+CCSRL-PDUs which are invalid shall be discarded.
+
+#### C.8.1.7 Interface to [ITU-T H.245]
+
+Interface to [ITU-T H.245] is defined by primitives defined in clause C.8.1.2.
+
+#### C.8.1.8 Interface to NSRP or LAPM/ITU-T V.42
+
+Interface to NSRP or LAPM/ITU-T V.42 are defined in clauses C.8.2 and C.8.3, respectively, as delivery of CCSRL-PDUs.
+
+### C.8.2 NSRP mode
+
+The general description of the NSRP protocol given in clause A.2 shall be followed with the following exceptions: the terminal shall transmit frames generated by the segmentation layer defined above whereby complete ITU-T H.245 **MultimediaSystemControlMessage** messages of clause A.2 are replaced by CCSRL frames. This is a generalization of the NSRP protocol concept, where an ITU-T H.245 message no longer needs to be transmitted within a single NSRP frame, but can be transmitted in segments.
+
+### C.8.3 LAPM/ITU-T V.42 mode
+
+The description of the LAPM/ITU-T V.42 for ITU-T H.324 terminals provided in clause A.3 is also applicable, with the exception that counter N401, maximum number of octets in an information field, may be set to a value smaller than 2048, but not shorter than the size of the frames generated by the CCSRL. Moreover, ITU-T H.245 **MultimediaSystemControlMessage** messages are not necessarily transmitted within one single LAPM/ITU-T V.42 frame but may be segmented and transmitted within CCSRL frames.
+
+# Annex D
+
+# Operation on ISDN circuits (H.324/I)
+
+(This annex forms an integral part of this Recommendation)
+
+## D.1 Scope
+
+This annex defines an operation mode for this Recommendation on ISDN circuits at bit rates ranging from 56 kbit/s to 1920 kbit/s. This channel capacity may be provided as a single B/H<sub>0</sub>/H<sub>11</sub>/H<sub>12</sub>-channel or multiple B/H<sub>0</sub>-channels, according to the multilink procedures. Operation on restricted networks (at 56 kbit/s for each channel) is also covered.
+
+The mode of operation defined by this annex is referred to as " H.324/I".
+
+ITU-T H.324/I terminals provide backwards compatibility with the installed base of ITU-T H.320 terminals, and forward compatibility with ITU-T H.324 Annex C terminals (mobile), while providing direct interoperation with:
+
+- ITU-T H.324 terminals on the GSTN (using GSTN modems);
+- ITU-T H.324 terminals operating on ISDN through user substitution of ITU-T I.400-series ISDN interfaces for ITU-T V.34 modems; and
+- voice telephones (both GSTN and ISDN).
+
+H.324/I offers users and implementers many technical improvements incorporated in the second-generation standards [ITU-T H.310], [ITU-T H.323] and this Recommendation, and corrects limitations and problems discovered with [ITU-T H.320].
+
+## D.2 References
+
+See clause 2.
+
+## D.3 Definitions
+
+This annex defines the following term:
+
+**D.3.1 restricted channel:** A channel carried on a network whose B-channels are effectively restricted to 56 kbit/s, or whose channels at H<sub>0</sub> or higher are restricted by ones-density considerations. This can be because the network inherently operates at 56 kbit/s, or because it provides a 64 kbit/s local interface, of 7 out of each 8 bits are delivered to the far end.
+
+## D.4 Functional requirements
+
+Except as noted below, all features and requirements of this Recommendation apply to H.324/I terminals.
+
+Additionally, H.324/I terminals shall comply with the following clauses.
+
+Procedures and requirements in this annex relating to ITU-T G.711 audio (voice telephony, ITU-T V.8, ITU-T V.8 *bis* modems) do not apply to H.324/I terminals connected to networks which do not provide octet or septet timing alignment, since transmission and reception of ITU-T G.711 audio telephony is impossible without such alignment.
+
+NOTE – Octet/septet timing is needed to use ITU-T G.711 audio with ordinary telephones which do not support ITU-T V.140 (for modem or speech). ITU-T V.24 type interfaces and some restricted (56 kbit/s) digital networks do not provide octet timing, so only H.324/I and ITU-T H.320 modes can be supported.
+
+### D.4.1 Modem interface
+
+H.324/I terminals shall use an ITU-T I.400-series ISDN user-network interface in place of the ITU-T V.34 modem. All references to the "ITU-T V.34 modem" in this Recommendation shall, for
+
+H.324/I, be replaced with "ITU-T I.400-series ISDN user-network interface" (see Note). The output of the ITU-T H.223 multiplex shall be applied directly to each bit of the digital channel, in the order defined by [ITU-T H.223].
+
+Within each octet or septet of the channel, any bit position determined by the ITU-T V.140 phase 2 procedure to be unusable shall be skipped and filled with 1s. Each octet or septet of digital channels using octet/septet timing shall be filled in the order starting with bit 1 (most significant bit of ITU-T G.711 audio) and progressing toward bit 8 (least significant bit of ITU-T G.711 audio).
+
+[ITU-T V.8] or [ITU-T V.8 *bis*] shall be used only when operating with far-end terminals determined to be on the GSTN by the procedures below.
+
+NOTE – For leased line networks, the network interface is defined in [ITU-T G.703] for bit rates in the range of 64 kbit/s to 2048 kbit/s. An alternative interface is defined in [ITU-T X.21]. For  $n \times H_0$  channels, timeslot allocation is given in clause 5 of [ITU-T G.704] for the ITU-T G.703 interface. It is stressed that interworking towards ISDN requires synchronous operation of the leased line network.
+
+### **D.4.2 ITU-T H.320 ISDN interoperation**
+
+In order to provide continued compatibility for existing users of ITU-T H.320 systems on ISDN, H.324/I terminals shall support operation in conformance with [ITU-T H.320]. If video transmission or reception is supported in the ITU-T H.324 mode of the H.324/I terminal, video transmission or reception shall also be supported in the ITU-T H.320 mode.
+
+### **D.4.3 ITU-T H.324 GSTN interoperation**
+
+H.324/I terminals shall support interoperation with ITU-T H.324 terminals on GSTN (using ITU-T V.34 modems) according to this Recommendation.
+
+H.324/I terminals shall send ITU-T H.324 GSTN signals by the use of a "virtual modem", which generates and receives an ITU-T V.34 analogue signal encoded as an ITU-T G.711 audio bitstream over the ISDN (note that the functional equivalent to a "virtual modem" can also be provided by attaching an ordinary ITU-T V.34 modem to the analogue output of an ITU-T I.400-series ISDN terminal adapter).
+
+### **D.4.4 Voice telephone interoperation**
+
+H.324/I terminals shall support interoperation with voice telephones using ITU-T G.711 speech coding as a speech or 3.1 kHz audio bearer service call. Other modes such as ITU-T G.722 audio may optionally be supported as well.
+
+Interconnection between the ISDN and GSTN networks for speech or 3.1 kHz audio bearer service is provided in the network, and does not affect terminals.
+
+### **D.4.5 NSRP support for ITU-T H.245 control channel**
+
+H.324/I terminals shall support the NSRP mode for the ITU-T H.245 control channel, as defined in Annex A. This is in addition to support for the standard SRP mode which is required by Annex A. The LAPM/ITU-T V.42 protocol stack may optionally be supported as well.
+
+### **D.4.6 ITU-T V.140 support**
+
+ITU-T H.324/I terminals shall support [ITU-T V.140].
+
+Upon initial connection of each digital channel (on the lowest numbered time-slot of a multi-channel connection such as an  $H_0$  channel), H.324/I terminals shall use the procedures of [ITU-T V.140] to determine network end-to-end connectivity and to automatically negotiate a selected mode for the call among the H.324/I, ITU-T H.320, ITU-T H.324 and voice telephone modes (or any other modes which the terminal supports).
+
+In this case, the H.324/I terminal should signal the "*Recommendations H.221 and H.242*" BC and LLC information elements as described in [ITU-T Q.931], and shall not signal the "*Recommendations H.223 and H.245*" BC and LLC information elements.
+
+#### **D.4.6.1 Exceptional bypass of [ITU-T V.140]**
+
+The ITU-T V.140 procedures may be bypassed for a particular connection when all of the following conditions apply:
+
+- 1) it is known from ISDN D-channel signalling that the far-end terminal is capable of supporting H.324/I; and
+- 2) it is known that all channels of both terminals are connected to 64 kbit/s octet-aligned network interfaces; and
+- 3) it is known (perhaps from analysis of the national telephone number of the far-end terminal) that the interconnecting network transfers all bits end-to-end between the two terminals, without possibility of bit misalignment or loss.
+
+In this case, the H.324/I terminal shall signal the "*Recommendations H.223 and H.245*" BC and LLC information elements in [ITU-T Q.931]. If phase D of the ITU-T H.324 call set-up procedure is not complete within 5 seconds of the establishment of the digital channel, the H.324/I terminal shall automatically disconnect the digital channel and automatically re-establish it using the normal ITU-T V.140 procedures.
+
+This ITU-T V.140 bypass procedure can be used only for single-channel H.324/I calls.
+
+### **D.4.7 terminalOnHold**
+
+The terminal shall revert to voice telephony mode when it receives an ITU-T H.245 **EndSessionCommand** message which signals **terminalOnHold** in **isdnOptions**. ITU-T G.711 speech coding shall be used. The encoder can choose the ITU-T G.711 law for the outgoing audio. The decoder shall determine the proper ITU-T G.711 law of the incoming audio, for example by using the procedures of Appendix I of [ITU-T G.725]. ITU-T G.711 law is allowed to be different in each direction. The terminal shall periodically send an ITU-T V.140 signature as long as it is on hold.
+
+## **D.5 Terminal procedures**
+
+The steps for provision of communication are as listed in clause 7 but with the following modifications.
+
+### **D.5.1 Phase A – Call set-up of digital channel**
+
+In phase A, the calling terminal shall request the connection according to procedures for the digital network in use (ITU-T I.400-series ISDN D-channel signalling, etc.).
+
+If the call is rejected by the network due to mismatch of ISDN bearer capability (BC) or high level capability (HLC) values, the terminal shall follow the procedures of [ITU-T V.140] to retry the call with different values.
+
+Upon successful completion of call set-up, the terminal shall initiate ITU-T V.140 procedures, as described below.
+
+#### **D.5.1.1 Transmitted signals**
+
+While executing the ITU-T V.140 phase 1 procedure, the H.324/I terminal shall transmit in bits 1-6 of each octet and in the ITU-T V.140 compatible protocol field (CPF), signals conforming to:
+
+- ITU-T H.320 (send H.221 FAS and BAS signalling in CPF); and
+- if ITU-T V.8 *bis* is supported, ITU-T V.8 *bis* (send initial ITU-T V.8 *bis* messages in bits 1-6 of ITU-T G.711 audio); or
+
+- if ITU-T V.8 *bis* is not supported, ITU-T V.8 (send initial ITU-T V.8 messages in bits 1-6 of ITU-T G.711 audio).
+
+These signals are sent in order that far-end terminals of these types (which do not support H.324/I or ITU-T V.140) will initiate their negotiation.
+
+Additionally, if the far-end terminal is known from ISDN D-channel signalling to be compatible with H.324/I, bits 1-6 of each octet should be set to 1 while executing this procedure. Otherwise, H.324/I terminals should send ITU-T G.711 coded speech on bits 1-6 of each octet while executing this procedure, so that voice telephony is established immediately upon connection of the circuit, if the far-end terminal supports voice telephony.
+
+#### D.5.1.2 Received signals
+
+While executing the ITU-T V.140 phase 1 procedure, the H.324/I terminal shall search the received data for signals conforming to:
+
+- ITU-T V.140 signature;
+- HDLC flags followed by an ITU-T H.223 MUX\_PDU on the digital channel or, if Annex C is supported, all possible stuffing sequences defined in Table C.1;
+- ITU-T H.320 (search for ITU-T H.221 FAS and BAS signalling);
+- If ITU-T V.8 *bis* is supported, ITU-T V.8 *bis* (search for initial ITU-T V.8 *bis* messages in ITU-T G.711 audio);
+- ITU-T V.8 (search for initial ITU-T V.8 messages in ITU-T G.711 audio).
+
+Additionally, bits 1-6 of each octet may be decoded as audio according to [ITU-T G.711] and delivered to the user while executing this procedure, so that voice telephony is established immediately upon connection of the circuit, if the far-end terminal supports voice telephony.
+
+#### D.5.1.3 Procedure
+
+Based on the received signal, the H.324/I terminal shall follow the algorithm below:
+
+- if ITU-T V.140 signature is detected, the H.324/I terminal shall proceed with ITU-T V.140 and upon completion of those procedures, proceed to the mode negotiated. Otherwise;
+- if ITU-T H.324 signalling is detected on the digital channel, the terminal shall proceed to phase D. Otherwise;
+- if ITU-T V.8 *bis* or ITU-T V.8 signalling is detected, the H.324/I terminal shall proceed with ITU-T V.8 *bis* or ITU-T V.8 and upon completion of those procedures, proceed to the mode negotiated. Otherwise;
+- if signals corresponding to any other operation mode supported by the terminal (such as ITU-T H.320 or other ISDN or PSTN protocols) are detected, the terminal may enter an operation mode appropriate to the detected signal. Otherwise;
+- if none of the above signals are detected after a time sufficient to detect these signals if they were present, the terminal shall enter voice telephone mode.
+
+The mode entered as a result of this negotiation should begin at the equivalent of phase B. For ITU-T H.324 GSTN mode, the terminal shall begin at phase B of this Recommendation according to clause 7.2. For ITU-T H.320 mode, the terminal shall begin at phase B1 of [ITU-T H.320]. For H.324/I mode, the terminal shall proceed to phase B, below.
+
+### D.5.2 Phase B – Initial telephony communication
+
+An optional phase B is voice telephony mode. In this mode, users have the opportunity to speak before proceeding to multimedia telephony.
+
+If the terminal is conditioned to go directly into multimedia communication mode, phase B shall be bypassed, proceeding directly to phase D. If the terminal is conditioned for initial telephony voice mode, the terminal shall proceed to phase D when:
+
+- the user manually causes the terminal to initiate an ITU-T V.140 phase 3 transaction; or
+- the terminal detects an ITU-T V.140 phase 3 initiation signal from the distant terminal.
+
+### **D.5.3 Phase C – Establishment of digital communication**
+
+There is no phase C, as the digital connection is already established. Terminals shall proceed directly to phase D.
+
+### **D.5.4 Phases D through G**
+
+All remaining phases (D through G) shall proceed as specified in the main body of this Recommendation, or as defined in clause C.5 if Annex C is supported.
+
+# Annex E
+
+# Timer T401 initialization for operation over geostationary-satellite channels
+
+(This annex forms an integral part of this Recommendation)
+
+## E.1 Introduction
+
+Two key aspects in transmission of multimedia communications through geostationary-satellite channels are the bit error rate and the transmission delay. The raw bit error rate can be as high as  $10^{-2}$ , or even worse in fading conditions. However, channel encoding is used to give a typical channel BER of  $10^{-5}$  or better. One-way transmission delay depends heavily on the connection used, as illustrated in Table E.1 for a typical mobile satellite system. These delay values are much larger than for typical cable GSTN lines (examples are given in Table A.1 of [ITU-T G.114]).
+
+**Table E.1 – Example of end-to-end delay values for communications via mobile geostationary-satellite channels**
+
+|                                               | Double-hop worst case [ms] | Single-hop typical case [ms] |
+|-----------------------------------------------|----------------------------|------------------------------|
+| <b>Mobile geostationary-satellite channel</b> |                            |                              |
+| Free space transmission delay                 | 260 (Note)                 | 260                          |
+| Coding/processing delay                       | 170                        | 170                          |
+| <b>GSTN</b>                                   |                            |                              |
+| Second GSTN satellite hop                     | 260                        | –                            |
+| Rest of GSTN                                  | 100                        | 100                          |
+| <b>Total</b>                                  | <b>790</b>                 | <b>530</b>                   |
+| NOTE – As per Table A.1 of [ITU-T G.114].     |                            |                              |
+
+## E.2 Determination of timer value
+
+Hence, careful determination of a suitable value for timer T401 is necessary for proper operation of an ITU-T H.324 terminal over geostationary-satellite channels. The use of one of the two following procedures is required:
+
+### a) *Generic T401 value definition*
+
+The use of an initial large value for timer T401, to ensure an appropriate throughput when geostationary communication satellite channels are used. For ITU-T H.324 mobile terminals, the minimum initial value for timer T401 shall be in the range of 1600-2100 ms. This value should also be used for fixed ITU-T H.324 terminals to support communication over geostationary-satellite channels. Tuning of the value of the timer T401 should be performed after the connection is established (see tuning procedure below), and the optimized value of the T401 timer may be larger or smaller than the initial value.
+
+### b) *T401 value definition with ITU-T V.42 and NSRP protocols*
+
+Timer T401 shall be initialized with an arbitrarily small value. The timer tuning procedure shall be used during phase D of the communication to define an optimized value for timer T401 (see tuning procedure below). This approach will work with the numbered SRP (NSRP) protocol and the ITU-T V.42 protocol, but it will not work when the SRP protocol is used while the actual round-trip delay is larger than the initial small value of T401.
+
+Procedure a) is more generic and more robust because it is applicable to existing as well as future ITU-T H.324 terminals. However, procedure a) may require larger buffers and, in some cases, may result in a longer start-up time. In ITU-T H.324 connections where ITU-T V.42 or NSRP are supported, the use of procedure b) could be advantageous.
+
+## **E.3 Timer tuning procedure**
+
+In either of the two procedures defined above, it is recommended that the value initially defined for timer T401 be tuned to a value close to but greater than the actual round-trip delay for a given connection. This should be performed to minimize the size of the buffers in the ITU-T H.324 terminal, speed up error recovery and increase overall throughput.
+
+The ITU-T H.245 round-trip delay estimation procedure may be used to tune the value of the timer T401. However, an implementer may explore other alternatives, such as:
+
+- observing the system response time to receive the acknowledgement for the first SRP message sent;
+- exploring modem training results available in some implementations of V-series modems.
+
+It should be noted that the total buffer size allocated for data retransmission in the error control protocol must be compatible with the T401 value obtained from the tuning procedure. This is important, especially for procedure b) in clause E.2, to avoid buffer overrun.
+
+# Annex F
+
+# Multilink operation
+
+(This annex forms an integral part of this Recommendation)
+
+## F.1 Scope
+
+This annex defines the operation of ITU-T H.324 over multiple independent physical connections, aggregated together according to [ITU-T H.226] to provide a higher total bit rate. These connections may be GSTN circuits, or ISDN circuits as defined in Annex D. The use of both GSTN and ISDN connections in the same call is supported.
+
+## F.2 References
+
+See clause 2.
+
+## F.3 Functional requirements
+
+For use on GSTN connections, terminals compliant with this annex shall comply with ITU-T H.324 and support ITU-T V.8 *bis* operation.
+
+For use on ISDN connections, terminals compliant with this annex shall comply with Annex D.
+
+## F.4 Overview
+
+In summary, the establishment of an ITU-T H.324 multilink call involves the following steps:
+
+- 1) Initial channel physical connection is established.
+- 2) ITU-T V.8 *bis* or ITU-T V.140 is executed, selecting *ITU-T H.324-Multilink* as the mode for the call.
+- 3) ITU-T H.324 operation begins on the initial channel, using ITU-T H.226.
+- 4) ITU-T H.245 is used to exchange information about available additional channels, including a 32-bit **callAssociationNumber** which will be used to identify the call.
+- 5) An additional channel physical connection is established.
+- 6) ITU-T V.8 *bis* or ITU-T V.140 is executed on the new channel, selecting *Multilink-Additional-Connection* as the mode; the initiator supplies the previously received **callAssociationNumber** to identify that the new channel is associated with the existing call.
+- 7) The new channel is added to the ITU-T H.226 channel set as part of the ITU-T H.324 multilink call.
+
+Figure F.2 illustrates these steps. Steps 5, 6 and 7 may proceed in parallel for any number of additional channels.
+
+## F.5 Procedures
+
+### F.5.1 Establishing multilink ITU-T H.324 operation
+
+#### F.5.1.1 Establishment of initial physical connection
+
+The initial physical connection shall be established according to the procedures of ITU-T H.324 (for GSTN circuits) or Annex D (for ISDN circuits), call set-up phases A and B.
+
+#### F.5.1.2 Execution of ITU-T V.8 *bis* or ITU-T V.140 procedure on initial connection
+
+Multilink operation shall be initiated via the capabilities exchange and mode selection procedures of [ITU-T V.8 *bis*] (according to phase C of the ITU-T H.324 call set-up procedure) in the case of a
+
+GSTN initial physical connection, or [ITU-T V.140] (according to Annex D) in the case of an ISDN initial physical connection.
+
+Using the procedures of ITU-T V.8 *bis* or ITU-T V.140, as appropriate, if the *H.324-Multilink* capability is present at both terminals of a connection, the terminal performing the mode selection may choose *H.324-Multilink* as the selected mode of communication.
+
+If *H.324-Multilink* is chosen as the selected mode, the procedures defined in this annex for ITU-T H.324 multilink operation shall be used for all subsequent communications until the end of the communication session or until the procedures of ITU-T V.8 *bis* or ITU-T V.140, as appropriate, are re-established to negotiate into a different mode.
+
+NOTE – Since ITU-T V.8 *bis* is an integral part of establishing multilink operation for ITU-T H.324, ITU-T V.8 *bis* is required for this mode over GSTN, unlike basic ITU-T H.324 which allows the use of ITU-T V.8 instead.
+
+#### F.5.1.3 Initiation of H.226 and ITU-T H.324 operation
+
+If *ITU-T H.324-Multilink* is the selected mode of communication, once the procedures of ITU-T V.8 *bis* or ITU-T V.140 have been completed, all subsequent communication shall apply the procedures of ITU-T H.226 to all data transmitted over the connection. Specifically, the ITU-T H.324 bitstream that would otherwise be transmitted in ordinary ITU-T H.324 (or Annex D) operation is instead used as the input to the ITU-T H.226 input queue as defined by the transmitter model in [ITU-T H.226]. Similarly, received information shall pass through the ITU-T H.226 receiver and the data stream produced by the output queue defined in the ITU-T H.226 receiver model shall be used as input to the ordinary ITU-T H.324 (or Annex D) receiver. The model of ITU-T H.324 multilink operation is shown in Figure F.1. Prior to associating any additional physical connections, ITU-T H.226 shall initially operate using a channel set size of one.
+
+ITU-T H.324 call set-up shall complete according to phases D and E of the ITU-T H.324 call set-up procedure, using the procedures of [ITU-T H.226] to transport the ITU-T H.223 bitstream.
+
+It is possible that, upon establishment of the initial connection, the terminals may not yet know if any additional connections will later be established. If no additional connections are established, ITU-T H.324 multilink operation shall continue to be used, as defined for a channel set size of one, throughout the ITU-T H.324 communication session.
+
+![Diagram of ITU-T H.324 multilink operation model showing data flow between ITU-T H.324 and ITU-T H.226 components over physical connections.](f23879f003c58b57f690e2dc6c95816a_img.jpg)
+
+The diagram illustrates the data flow in ITU-T H.324 multilink operation. At the top, a box labeled 'ITU-T H.324' contains a smaller box labeled 'ITU-T H.223'. Below this, a large box labeled 'ITU-T H.226' contains two sub-boxes: 'Input queue' on the left and 'Output queue' on the right. A downward arrow points from the 'ITU-T H.223' box to the 'Input queue'. An upward arrow points from the 'Output queue' to the 'ITU-T H.223' box. At the bottom, three vertical double-headed arrows represent 'Physical connections', with ellipses between them. The label 'H.324(09)\_FF.1' is in the bottom right corner.
+
+Diagram of ITU-T H.324 multilink operation model showing data flow between ITU-T H.324 and ITU-T H.226 components over physical connections.
+
+Figure F.1 – Model of ITU-T H.324 multilink operation
+
+### F.5.2 Adding physical connections
+
+The procedures for adding associated physical connections require one of the two terminals to be designated as the initiator and the other as the responder. If the initial physical connection is over GSTN, the terminal considered the *calling station* as defined in [ITU-T V.8 bis] shall be considered the initiator, and the *answering station* as defined in [ITU-T V.8 bis] shall be considered the responder. If the initial physical connection is over ISDN, the initiator and responder shall correspond to the *initiator* and *responder* as determined in phase 3 of [ITU-T V.140].
+
+The procedures for establishing and associating additional connections may be used on multiple connections at the same time.
+
+#### F.5.2.1 Exchanging call information
+
+At any time after ITU-T H.324 multilink operation is established, the initiator may begin the procedures to establish additional connections.
+
+To request the information needed to establish and associate additional connections, the initiator shall send the ITU-T H.245 **MultilinkRequest.callInformation** message to the responder. In this message, the initiator shall indicate the maximum number of additional connections that it is capable of establishing in the **maxNumberOfAdditionalConnections** parameter.
+
+On receipt of a **MultilinkRequest.callInformation** message, the responder shall send the ITU-T H.245 **MultilinkResponse.callInformation** message to the initiator. In this message, the responder shall include the **DialingInformation** parameter, with contents as described below, as well as a **callAssociationNumber**. The **callAssociationNumber** shall contain a 32-bit random number (uniformly distributed). Any subsequent **callInformation** exchanges within the same ITU-T H.324 session shall re-use the identical **callAssociationNumber**.
+
+The **DialingInformation** parameter should be used to provide explicit dialling information to allow the initiator to establish the additional connections. If this information is not available, it shall indicate the maximum number of additional connections available with no indication of how to dial those connections.
+
+##### F.5.2.1.1 Differential automatic dialling information
+
+If the responder chooses to provide dialling information for the additional connections, it may do so using the **differential** choice of the **DialingInformation** parameter. In this case, the responder shall provide a list of **DialingInformationNumber** parameters, one for each potential additional connection. The length of this list indicates implicitly the maximum number of additional connections available. For each potential additional connection, **DialingInformationNumber** includes up to three subparameters that indicate the dialling information for this connection differentially relative to the corresponding information for the already established initial connection.
+
+The **networkAddress** parameter shall include the least significant (right-most) portion of the telephone number for this connection, up to and including the most significant digit that is different from the number for the initially established connection, and shall include no digits that are more significant than this. If the number for the additional connection is identical to that of the initial connection, the **networkAddress** parameter shall consist of a zero-length string (since there are no differing digits in the telephone number).
+
+NOTE – The differential digit method is used instead of the full ITU-T E.164 digit string because the first few digits of the number to be dialled can vary based on the geographic location of the two terminals; for example, whether or not they are located in the same city.
+
+If there is a subaddress used for dialling, and the subaddress of a given connection is different from that of the initial connection, the responder shall include the subaddress, in full, in the optional **subAddress** parameter.
+
+The responder shall indicate the network types supported for the connection (GSTN, ISDN or both) using the **networkType** parameter.
+
+##### F.5.2.1.2 Automatic dialling information not available
+
+If the responder chooses not to provide any dialling information (or if the dialling information is provided using an out-of-band mechanism), it shall indicate this using the **infoNotAvailable** setting of the **DialingInformation** parameter. In this case, the responder shall indicate the maximum number of additional connections that are available.
+
+NOTE – It is suggested that, whenever possible, the responder should indicate the explicit dialling information to allow the initiator to automatically establish additional connections. This avoids the need for the user at the calling terminal to provide these numbers explicitly.
+
+#### F.5.2.2 Establishing additional physical connections
+
+The initiator of the initial physical connection may, at any time, establish additional physical connections to be used for multilink operation. It shall not establish additional connections that exceed the maximum number of additional connections indicated by the responder during the exchange of call information.
+
+If the initiator chooses to establish additional connections, it shall do so using the following procedure.
+
+In the case that the responder provided dialling information in a **DialingInformation.differential** parameter, the initiator shall form the network address (telephone number) to be dialled by taking the network address used to dial the initially established connection, and replacing the least significant N digits with the contents of the **networkAddress** parameter. If this parameter has zero length, the network address used to dial the initial connection shall be used in full without modification.
+
+For example, if the initial connection was established by dialling "0019786234349", and the **networkAddress** parameter contains "51", the number to be dialled for the additional connection is "0019786234351".
+
+If the **subAddress** parameter is present, the contents of this parameter shall fully replace any subaddress used to establish the initial connection. Use of the **networkType** parameter by the initiator is a local matter, beyond the scope of this Recommendation.
+
+In the case that the responder did not provide any dialling information (indicated by **infoNotAvailable**), the initiator may either choose not to add additional connections, or may attempt to determine the network address of the additional connections through other means (e.g., requesting from the local user or through an out-of-band communication mechanism). Any such means is beyond the scope of this Recommendation.
+
+##### F.5.2.2.1 Responder request to add additional connections
+
+At any time after exchange of call information according to clause F.5.2.1, the responder may request that the initiator add physical connections. This shall be done using the **MultilinkRequest.addConnection** message in [ITU-T H.245]. The responder shall indicate the connections desired to be added using the **DialingInformation** structure as described above. On receiving this message, the initiator shall respond with an **MultilinkResponse.addConnection** message indicating that it either intends to add the connections as requested, or that it does not intend to do so, along with the appropriate reason code.
+
+NOTE – It is possible that the responder could be the terminal that establishes additional physical connections instead of the initiator. The procedures and exchange of information needed to facilitate this are for further study.
+
+#### F.5.2.3 Associating additional physical connections
+
+Upon establishment of a GSTN circuit, the procedures of [ITU-T V.8 *bis*] shall be executed, leading to establishment of a ITU-T V-series modem data connection.
+
+Upon establishment of an ISDN circuit, the procedures of [ITU-T V.140] shall be executed.
+
+##### F.5.2.3.1 ITU-T V.8 *bis* or ITU-T V.140 capability exchange
+
+When an additional physical connection is established, the capability list in ITU-T V.8 *bis* or ITU-T V.140 shall include the *Multilink-Additional-Connection* capability.
+
+If a terminal is only capable of establishing this connection such that it is associated with an already established session, it shall only indicate the *Multilink-Additional-Connection* capability and no others (it shall not indicate H.324 or H.324-*Multilink* capability).
+
+If a terminal is capable of allowing this connection to either be associated with an already established connection, or to be an independent connection, then other capabilities in addition to *Multilink-Additional-Connection* may be listed as well. The additional capabilities indicate *only* the capabilities for independent connections, therefore, the H.324 or H.324-*Multilink* capability may or may not be included depending on whether the terminal can support a separate ITU-T H.324 or ITU-T H.324-*multilink* session in addition to the existing ITU-T H.324-*multilink* session.
+
+NOTE – The *Multilink-Additional-Connection* capability indicates the ability for the connection to be associated with an existing ITU-T H.226 session. The H.324 or H.324-*Multilink* capabilities indicate the ability for the connection to become a new ITU-T H.324 or ITU-T H.324-*multilink* session.
+
+##### F.5.2.3.2 ITU-T V.8 *bis* or ITU-T V.140 mode selection
+
+To associate a connection with an existing ITU-T H.324-*multilink* session, the terminal that issues the ITU-T V.8 *bis* or ITU-T V.140 mode selection command shall indicate *Multilink-Additional-Connection* as the selected mode, and shall set the call association parameter to the value of the **callAssociationNumber** previously specified in the **MultilinkResponse.callInformation** message.
+
+On reception of a *Multilink-Additional-Connection* mode selection command, the receiving terminal shall determine which existing ITU-T H.324-*multilink* session to associate the new connection with by comparing the call association number in the mode selection command with the **callAssociationNumber** corresponding to any existing sessions. If the terminal has no existing sessions with the corresponding **callAssociationNumber**, it shall reject the connection.
+
+NOTE – Since V.8 *bis* is an integral part of establishing multilink operation for ITU-T H.324, ITU-T V.8 *bis* is required for this mode over GSTN, unlike basic ITU-T H.324 which allows the use of ITU-T V.8 instead.
+
+### F.5.3 Removing physical connections
+
+#### F.5.3.1 Removing last remaining connection
+
+Phases F and G of the ITU-T H.324 call set-up procedures shall be followed to remove the last remaining physical connection at the end of an ITU-T H.324 session. Note that the last remaining connection need not be the same as the initially established connection.
+
+#### F.5.3.2 Removing additional connections
+
+At any time, a terminal may remove additional physical connections. Note that the initially established connection may be removed just like any other connection. Removal of the last remaining connection (which may or may not be the same as the initially established connection) is described above.
+
+If a connection is removed intentionally, the terminal initiating the removal shall remove this channel from the ITU-T H.226 channel set prior to removal of the physical connection (allowing sufficient time for local data buffers for that channel to empty). Also prior to removal of the physical connection, it shall send the **MultilinkRequest.removeConnection** message in ITU-T H.245
+
+to the remote site. In this message it shall indicate which channel is to be removed. It shall wait until it either receives the **MultilinkResponse.removeConnection** message from the remote site indicating that the corresponding channel has stopped being used, or a locally specified time-out, and then it should remove the physical connection.
+
+On receipt of a **MultilinkRequest.removeConnection** message, a terminal shall remove the indicated channel from its transmitted ITU-T H.226 channel set (assuming that the indicated channel is bidirectional, and is in use by this terminal). In any case, it shall send the **MultilinkResponse.removeConnection** message in response to the remote site, indicating that this channel is no longer (or was never) in use.
+
+Identification of the channel to be removed is done with respect to the channel numbering received via ITU-T H.226 from the terminal to which the **MultilinkRequest.removeConnection** is being sent. The **connectionIdentifier** parameter in each message shall identify a channel by indicating a combination of **channelTag** and **sequenceNumber** corresponding to a recently received ITU-T H.226 header on the channel to be removed. If a channel tag was not specified at all in the header, a value of zero shall be used for the **channelTag** parameter. In the **MultilinkResponse.removeConnection**, the **connectionIdentifier** shall be identical to the value in the corresponding **MultilinkRequest.removeConnection** message.
+
+NOTE – Since the value of the channel tag is meaningful only with respect to a particular header set, the sequence number must be used in combination with the channel tag to uniquely specify the channel to be removed. The receiver of a **MultilinkRequest.removeConnection** must have the ability to determine, from these two values, which channel the requester intends to be removed. To do this, it must have the ability to remember the correspondence between physical connections and channel tags for header sets that have already been sent. Maintaining the same value of channel tag for a given physical channel is a straightforward means of determining this correspondence without explicitly saving these values for all header sets.
+
+If a connection is removed accidentally, each terminal should, as soon as possible, begin transmission of a new ITU-T H.226 data set which no longer includes this connection in the channel set.
+
+### F.5.4 Negotiating the maximum header interval
+
+For use with this annex, the value of the ITU-T H.226 maximum header interval shall not be greater than 2 seconds, unless negotiated to another value as described below.
+
+A terminal may send the **MultilinkRequest.maximumHeaderInterval** message in [ITU-T H.245]. In this message, it may either indicate that it wishes to know the actual interval being used by the remote transmitter without altering it, or it may request a particular value to be used instead.
+
+A terminal receiving a **MultilinkRequest.maximumHeaderInterval** message shall respond by sending a **MultilinkResponse.maximumHeaderInterval** message. If the corresponding request indicated a request for information about the current minimum rate, the terminal shall provide the value that its transmitter is currently using as the maximum header interval in the response. If the corresponding request specified a particular minimum rate to use, the terminal should attempt to comply with this request by modifying the maximum header interval used by its transmitter. Whether or not it makes a change to the maximum header interval, the response shall indicate the new value that is in use (which may be different from the requested value).
+
+NOTE – A receiver may use its knowledge of the maximum header interval used by the remote transmitter to help ensure that data over a physical channel are continuing to be received successfully. By knowing the maximum interval between headers, long periods of time with no headers may indicate a malfunctioning channel. The ability to request a maximum header interval also allows a terminal to bound the error propagation of data that it is receiving.
+
+### F.5.5 Using the optional data CRC
+
+In [ITU-T H.226], a transmitter may include an optional CRC on the data. This CRC may be used by a receiver to determine the quality of a given channel. A terminal may indicate its desire that the remote terminal send this CRC in all subsequent data sets by sending the ITU-T H.245 **MultilinkIndication.crcDesired** message. The receiving terminal may optionally comply, there is no explicit acknowledgment or response required.
+
+### F.5.6 Using the excessive error indication
+
+A terminal may indicate to the remote terminal that excessive errors are being received on a particular connection. The means for the terminal to determine the error rate or the criterion for determining what is excessive is defined locally at that terminal. It could, for example, result from receiving an excessive number of ITU-T H.226 headers that contain errors, from the failure to receive ITU-T H.226 headers at the minimum specified rate, or from an excessive rate of errors detected using the optional data CRC. In any case, the indication should be given with the expectation that the remote terminal will take some corrective action. This indication is made by sending the **MultilinkIndication.excessiveError** message in ITU-T H.245 indicating which connection is causing problems. The connection is indicated using the **connectionIdentifier** parameter in the same manner as defined above for the **MultilinkRequest.removeConnection** message.
+
+On receipt of this message, a terminal may choose to take corrective action. The particular corrective action that it should take is not specified. Examples include removing the connection from use or lowering the rate of the connection in the hope of reducing the error rate.
+
+## F.6 Maximum transmit skew
+
+In using ITU-T H.226 for ITU-T H.324 multilink operation, as defined in this annex, the value of the maximum transmit skew shall equal 50 milliseconds.
+
+## F.7 Sequence diagram for establishment of multilink operation
+
+Figure F.2 shows the sequence of events in establishing multilink operation. In the figure, solid lines represent exchanges over the initial connection, dotted lines represent exchanges over additional connection(s), and heavy solid lines represent exchanges over all connections.
+
+![Sequence diagram for establishing multilink operation between an Initiator and a Responder.](99698c448635861b7dc8d352f87a1b2b_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Initiator
+    participant Responder
+    Note right of Initiator: Establish initial connection
+    Initiator->>Responder: Initial ITU-T V.140 or ITU-T V.8 bis exchange (ITU-T H.324-Multilink as mode choice)
+    Note left of Responder: ...
+    Responder->>Initiator: Begin ITU-T H.226 operation on initial connection
+    Responder->>Initiator: Begin ITU-T H.324 operation on initial connection
+    Note left of Responder: ...
+    Initiator->>Responder: MultilinkRequest.callInformation
+    Responder->>Initiator: MultilinkResponse.callInformation (with dialingInformation and callAssociationNumber)
+    Note right of Initiator: Establish additional connection(s)
+    Initiator-->>Responder: Additional connection ITU-T V.140 or ITU-T V.8 bis exchange (Multilink-Additional-Connection as mode choice)
+    Note left of Responder: ...
+    Responder->>Initiator: callAssociationNumber
+    Responder->>Initiator: Expand ITU-T H.226 operation to any established connections
+    Note right of Responder: H.324(09)_FF.2
+  
+```
+
+The sequence diagram illustrates the interaction between an Initiator and a Responder to establish a multilink operation. The process begins with the Initiator sending a message to 'Establish initial connection'. This is followed by an 'Initial ITU-T V.140 or ITU-T V.8 bis exchange (ITU-T H.324-Multilink as mode choice)' from the Initiator to the Responder. A vertical ellipsis indicates further messages. The Responder then sends 'Begin ITU-T H.226 operation on initial connection' and 'Begin ITU-T H.324 operation on initial connection' to the Initiator. Another vertical ellipsis follows. The Initiator sends a 'MultilinkRequest.callInformation' message, and the Responder responds with 'MultilinkResponse.callInformation (with dialingInformation and callAssociationNumber)'. Next, the Initiator sends 'Establish additional connection(s)', followed by an 'Additional connection ITU-T V.140 or ITU-T V.8 bis exchange (Multilink-Additional-Connection as mode choice)' message. A third vertical ellipsis is shown. The Responder sends 'callAssociationNumber' and 'Expand ITU-T H.226 operation to any established connections' to the Initiator. The diagram concludes with the text 'H.324(09)\_FF.2' in the bottom right corner.
+
+Sequence diagram for establishing multilink operation between an Initiator and a Responder.
+
+**Figure F.2 – Sequence diagram for establishing multilink operation**
+
+# Annex G
+
+# Usage of ISO/IEC 14496-1 generic capabilities in ITU-T H.324 terminals
+
+## G.1 Scope
+
+This annex defines the usage of [ISO/IEC 14496-1] ("MPEG-4 systems") generic capabilities in ITU-T H.324 terminals and the framing and error protection of the corresponding data streams.
+
+## G.2 References
+
+See clause 2.
+
+## G.3 General
+
+The codepoint for [ISO/IEC 14496-1] presented herein shall only be used for applications that want to make use of the object descriptor and scene description capability of [ISO/IEC 14496-1]. In this case, any type of ISO/IEC 14496 data stream to be used shall be indicated by means of the ISO/IEC 14496-1 generic capability during capability exchange as defined in [ITU-T H.245].
+
+Applications that only want to use ISO/IEC 14496-2 ("MPEG-4 visual") and/or ISO/IEC 14496-3 ("MPEG-4 audio") data streams, shall use the ISO/IEC 14496-2 generic capability and/or the ISO/IEC 14496-3 generic capability, respectively, as defined in [ITU-T H.245] for a fast set-up.
+
+NOTE – ITU-T H.324 terminals using these ISO/IEC 14496 codepoints shall support the mandatory audio and video codecs as applicable.
+
+## G.4 Choice of error protection for ISO/IEC 14496 data streams
+
+The error protection of the ISO/IEC 14496 data streams can be arbitrarily negotiated, requested and chosen by use of the "transport" field in the generic capability for [ISO/IEC 14496-1]. By usage of this field, an appropriate **DataProtocolCapability** shall be indicated.
+
+## G.5 Framing of ISO/IEC 14496-1 data streams
+
+Each individual SL packet (as defined in [ISO/IEC 14496-1]) to be transmitted shall be mapped on exactly one ITU-T H.223 AL-SDU as defined in [ITU-T H.223].
+
+# Annex H
+
+# Mobile multilink operation
+
+(This annex forms an integral part of this Recommendation)
+
+## H.1 Scope
+
+This annex defines the operation of ITU-T H.324 over up to eight independent physical connections, aggregated together according to the mobile multilink layer defined in this annex to provide a higher total bit rate. These connections are error-prone mobile channels as defined in Annex C, all having the same transmission rate.
+
+The difference between Annexes H and F is that Annex H is primarily intended to be used on error-prone connections by not using HDLC framing and with less flexibility in terms of the number, the bit rate and the delay differences of the channels involved in the aggregation than Annex F, in order to work on mobile connections. Annex H is not intended to be a replacement of Annex F on connections with very low bit error rates.
+
+## H.2 Definitions and format conventions
+
+### H.2.1 Definition of terms
+
+This annex defines the following terms:
+
+**H.2.1.1 header:** A collection of parameters whose beginning is marked by one flag.
+
+**H.2.1.2 sample:** The smallest unit of data which is always kept contiguous when distributing data among multiple channels. The size of the sample is an integer number of octets.
+
+### H.2.2 Format conventions
+
+See clause 3.2 of [ITU-T H.223].
+
+## H.3 Functional requirements
+
+For use on mobile connections, terminals compliant with this annex shall comply with Annex C. The multilink operation is limited to channels having the same characteristics. In particular, the channels to be aggregated shall have the same bit rate. Since the channels as defined in Annex C do not utilise ITU-T V.8 *bis* or ITU-T V.140, in-band signalling is defined in this annex for the purpose of setting up the mobile multilink, as well as the addition and the removal of additional connections.
+
+## H.4 Overview
+
+In summary, the establishment of a mobile multilink call involves the following steps:
+
+- 1) Initial channel physical connection is established.
+- 2) The mobile multilink is set up using the in-band joint multilink and multiplex set-up procedure.
+- 3) ITU-T H.324 operation begins on the initial connection.
+- 4) ITU-T H.245 is used to exchange information about available additional channels, including a 32-bit **callAssociationNumber**, which will be used to identify the call.
+- 5) An additional physical connection is established.
+- 6) In-band control frames are exchanged between the initiator and the responder to set up an additional connection to be associated with the mobile multilink. The initiator supplies the
+
+previously received **callAssociationNumber** to identify that the new connection is associated with the existing call.
+
+- 7) The new connection is added to the mobile multilink layer as part of the ITU-T H.324 mobile multilink call.
+
+## H.5 Mobile multilink layer specification
+
+### H.5.1 Overview
+
+The mobile multilink is a layer between an ITU-T H.223 multiplex and up to eight physical channels (Figure H.1). Its function is to aggregate the physical channels in order to provide a higher total bit rate for an Annex C. The transmission rate of each of the physical channels involved shall have the same value.
+
+![Diagram of the mobile multilink layer structure showing the ITU-T H.223 multiplex, the mobile multilink layer, and physical channels.](a634891d16b60b21df90a35c2af72c67_img.jpg)
+
+The diagram illustrates the mobile multilink layer structure. At the top is a box labeled "ITU-T H.223 level 0, 1, 2 or 3 multiplex". Below it is a box labeled "Mobile multilink layer". Between these two boxes are two vertical arrows: a downward arrow on the left and an upward arrow on the right. Below the "Mobile multilink layer" box are three pairs of vertical double-headed arrows, representing connections to "Physical channels". The text "H.324(09)\_FH.1" is located to the right of the bottom right double-headed arrow.
+
+Diagram of the mobile multilink layer structure showing the ITU-T H.223 multiplex, the mobile multilink layer, and physical channels.
+
+**Figure H.1 – Overview of the mobile multilink layer**
+
+The input to the mobile multilink layer shall be a bitstream from an ITU-T H.223 level 0, 1, 2 or 3 multiplex as defined in [ITU-T H.223] and in Annexes A, B, C and D of [ITU-T H.223]. The output from the multilink layer shall be distributed onto the physical channels.
+
+In order to recover the multiplexed stream at the receiving side from one or more physical channels, a synchronization mechanism is needed. This is achieved by a framing format where header information is inserted at regular intervals into the physical channels.
+
+### H.5.2 Mobile multilink framing
+
+Data to be sent over the physical channels shall be segmented into frames. A frame shall start with a 16-bit flag, followed by a 2- or 5-octet header after which the payload follows as shown in Figure H.2. The number of octets in the payload is signalled in the header.
+
+![Diagram of the mobile multilink layer framing format showing the flag, header, and payload.](4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg)
+
+The diagram shows the framing format as a vertical stack of three boxes. The top box is labeled "Flag (2 octets)". The middle box is labeled "Header (2 or 5 octets)". The bottom box is labeled "Payload (0 to SS\*SPF octets)".
+
+Diagram of the mobile multilink layer framing format showing the flag, header, and payload.
+
+NOTE – The SS and SPF parameters are defined in clause H.5.2.2.
+
+**Figure H.2 – Mobile multilink layer framing format**
+
+#### H.5.2.1 Flag
+
+A mobile multilink frame shall begin with the 16-bit flag shown in Figure H.3 or its one's complement flag if the full header is used or the compressed header is used, respectively. If synchronization is lost on the receiving side, a search for this flag should be performed to reacquire synchronization. Since this sequence of bits is not unique in the bitstream but can be emulated by data in the payload part of the framing format, a multilink receiver should also check that a valid header can be decoded before synchronization is accepted.
+
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet |
+|---|---|---|---|---|---|---|---|-------|
+| 1 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1     |
+| 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 2     |
+
+**Figure H.3 – 16-bit flag pattern for the mobile multilink**
+
+NOTE – The flags defined in Annex A of [ITU-T H.223] are at a Hamming distance of 8 from this flag.
+
+#### H.5.2.2 Header
+
+Two types of headers are defined: the full header and the compressed header. The full header contains all information for initial operation, whereas the compressed header contains minimum information, which can be used after information frame synchronization has been acquired. The distinction between these headers is made by the polarity of the flag field. The full header is preceded by a flag field as shown in Figure H.3 and the compressed header is preceded by the one's complemented flag.
+
+##### H.5.2.2.1 Full header configuration
+
+The full header is shown in Figure H.4.
+
+| 8                | 7 | 6  | 5 | 4 | 3  | 2 | 1 | Octet |
+|------------------|---|----|---|---|----|---|---|-------|
+| FT               | L | SN |   |   | CT |   |   | 1     |
+| SS               |   |    |   |   |    |   |   | 2     |
+| SPF              |   |    |   |   |    |   |   | 3     |
+| 16-bit CRC field |   |    |   |   |    |   |   | 4     |
+|                  |   |    |   |   |    |   |   | 5     |
+
+**Figure H.4 – Full header format**
+
+Two types of frames are defined, control frames and information frames, as indicated by the FT (frame type) bit. FT shall be set to "1" for control frames used for in-band signalling to add connections. FT shall be set to "0" for information frames carrying ITU-T H.223 multiplexed data in the payload part.
+
+The 3-bit sequence number (SN) field shall be incremented by one modulo 8 for each new information frame and shall have the same value for all channels in use.
+
+The 3-bit channel tag (CT) field is a unique identifier for a channel in multilink session.
+
+The L bit shall be set to "1" for the channel that is the highest numbered channel. For all other channels, the L bit shall be set to "0".
+
+The 8-bit sample size (SS) field indicates the size of a sample in octets (see clause H.5.4). The value 0 of SS is reserved for future use.
+
+The 8-bit samples per frame (SPF) field indicates the length in samples of the payload (see clause H.5.4).
+
+The product of SS and SPF gives the size of the payload in octets.
+
+The last two octets of the header hold a 16-bit CRC field (see clause 7.4.3.2.3 of [ITU-T H.223]) as protection for the 3 octets following the flag.
+
+##### H.5.2.2.2 Compressed header configuration
+
+The compressed header is shown in Figure H.5.
+
+![](8ab30dbff406204a68c59ae7c1b77413_img.jpg)
+
+|                 |   |    |   |   |    |   |   |       |
+|-----------------|---|----|---|---|----|---|---|-------|
+| 8               | 7 | 6  | 5 | 4 | 3  | 2 | 1 | Octet |
+| X               | L | SN |   |   | CT |   |   | 1     |
+| 8-bit CRC field |   |    |   |   |    |   |   | 2     |
+
+**Figure H.5 – Compressed header format**
+
+The CT, SN and L fields are identical to those described in clause H.5.2.2.1.
+
+The X bit is set to "0". The value "1" is reserved for future use.
+
+The 8-bit CRC field (see clause 7.3.3.2.3 of [ITU-T H.223]) is used as protection for the octet following the one's complemented flag.
+
+#### H.5.2.3 Control frames
+
+To support in-band signalling for the handling of initial and additional connections to the multilink layer, control frames are used.
+
+Control frames use the full header format with the FT bit set to "1". There are three types of control frames defined as shown in Figure H.6.
+
+| Control frame      | MUX Level | Control Field |    |    |    |    |     | Payload                                          |
+|--------------------|-----------|---------------|----|----|----|----|-----|--------------------------------------------------|
+|                    |           | L             | FT | CT | SN | SS | SPF |                                                  |
+| Initial            | 0         | 0             | 1  | 0  | 0  | 1  | 0   | –                                                |
+|                    | 1         | 0             | 1  | 0  | 1  | 1  | 0   | –                                                |
+|                    | 2         | 0             | 1  | 0  | 2  | 1  | 0   | –                                                |
+|                    | 3         | 0             | 1  | 0  | 3  | 1  | 0   | –                                                |
+| Request additional | –         | 1             | 1  | 0  | 0  | 1  | 6   | 6-octet payload as described in clause H.6.2.3.1 |
+| Accept additional  | –         | 1             | 1  | 0  | 0  | 1  | 0   | –                                                |
+
+**Figure H.6 – Header and payload for control frames**
+
+*initial* control frames are used for setting up a multilink session between two terminals, including multiplex level set-up. The SN field is set to the level of the multiplex, i.e., 0, 1, 2 or 3.
+
+*request additional* control frames are used for requesting to add a physical connection to an already existing multilink session.
+
+*accept additional* control frames are used for accepting the request to add a physical connection to an already existing multilink session.
+
+The use of these control frames is described in clause H.6.
+
+### H.5.3 Stuffing frames
+
+In the event that the mobile multilink layer has no information to send on a channel, such as when a channel is no longer part of the multilink session but has not been disconnected yet, a flag shown in Figure H.3, followed by 5 zero octets shall be sent as the stuffing sequence.
+
+For connections that are part of a multilink session, it is the responsibility of the ITU-T H.223 multiplex to supply the multilink with the correct amount of data, taking into account the overhead for the multilink framing.
+
+### H.5.4 Information frames
+
+Information frames use either the full header format with the FT bit set to "0" or the compressed header. For all channels in use the same type of header (full header or compressed header) shall be used.
+
+Information frames are generated for each block of ITU-T H.223 bitstream. The size of a block is (number of channels \* SS \* SPF) octets. A block is divided into samples of SS octets. Then samples are put onto the payload part of information frames. The first sample shall be placed on the frame with the lowest CT value, the next sample on the next lowest numbered frame, and so on. After a sample has been placed on the highest numbered frame, the process shall be repeated using the lowest numbered frame until all samples in the block have been sent.
+
+NOTE 1 – On channels having a burst characteristic, it may be advantageous to choose a value for a sample larger than one octet. For instance, a value that is related to the mean burst length may be a good choice.
+
+NOTE 2 – All the information frames for this block have the same values of SS and SPF.
+
+The L bit shall be set to "1" for the highest numbered channel and to "0" for the remaining channels.
+
+The SN field shall be incremented by one modulo 8 for each block of ITU-T H.223 bitstream.
+
+The CT value indicates the channel onto which the information frame is transmitted.
+
+NOTE 3 – In the case that a header cannot be interpreted due to a CRC error, a receiver may assume that the header contained a CT value identical to a previously correct received header.
+
+## H.6 Procedures
+
+### H.6.1 Establishing mobile multilink operation
+
+#### H.6.1.1 Establishment of initial connection
+
+The procedure described in clauses C.5 and C.6 shall be applied except for clause C.6.2, which is replaced by clause H.6.1.2.
+
+#### H.6.1.2 Joint multilink and multiplex set-up over the initial connection
+
+After the establishment of the initial physical connection, a terminal that intends to use the mobile multilink shall start transmitting control frames for *initial connection* (Figure H.6). This sequence of control frames jointly sets up both the mobile multilink layer and the ITU-T H.223 multiplex level. The terminal shall set the SN field of the header to its highest supported multiplex level, which shall be 0, 1, 2 or 3.
+
+If the terminal detects an Annex C stuffing sequence in place of mobile multilink control frames, it shall immediately start the Annex C set-up procedure according to clause C.6.2.
+
+If the terminal detects control frames for *initial connection* with a multiplex level lower than its own transmitted level, it shall immediately change its value in the SN field according to the detected lower level.
+
+When the terminal detects control frames with a multiplex level that is identical to its own transmitted level, multilink and multiplex set-up has been completed. The ITU-T H.223 multiplex shall then start its operation using the multiplex level indicated in the SN field.
+
+#### H.6.1.3 Initiation of mobile multilink operation
+
+If the mobile multilink is set up, all subsequent communication shall apply the mobile multilink mode to all data transmitted over the connection. Specifically, the ITU-T H.324 bitstream that would otherwise be transmitted in Annex C operation is instead used as the input to the mobile multilink. Similarly, received information shall pass through the mobile multilink receiver and the data output stream produced shall be used as input to the ordinary Annex C receiver.
+
+It is possible that, upon establishment of the initial connection, the terminals may not yet know if any additional connections will later be established. If no additional connections are established, ITU-T H.324 mobile multilink operation shall continue to be used, on the initial connection, throughout the ITU-T H.324 communication session.
+
+The initial connection shall be assigned a CT value of "0" initially until another connection is added to the session.
+
+The ITU-T H.245 **TerminalCapabilitySet** message shall include the **mobileMultilinkFrameCapability** in **H223Capability**.
+
+### **H.6.2 Adding physical connections**
+
+The procedures for adding associated physical connections require one of the two terminals to be designated as the initiator and the other as the responder. The terminal that originates the first physical connection shall be the initiator, and the terminal that answers the first physical connection shall be the responder.
+
+The procedures for establishing and associating additional connections may be performed on multiple connections at the same time.
+
+When one or more channels are added to a multilink session, the transmitting entity of the multilink shall assign a channel tag from 0 to (N-1) to each of the channels before the next information frames are transmitted, where N is the number of connections in use.
+
+#### **H.6.2.1 Exchanging call information**
+
+See clause F.5.2.1 with multilink replaced with mobile multilink.
+
+##### **H.6.2.1.1 Differential automatic dialling information**
+
+See clause F.5.2.1.1.
+
+The responder may use the **networkType** of **mobile**.
+
+##### **H.6.2.1.2 Automatic dialling information not available**
+
+See clause F.5.2.1.2.
+
+#### **H.6.2.2 Establishing additional physical connections**
+
+See clause F.5.2.2 with multilink replaced with mobile multilink.
+
+##### **H.6.2.2.1 Responder request to add additional connections**
+
+See clause F.5.2.2.1.
+
+#### **H.6.2.3 Associating additional physical connections**
+
+Upon establishment of an additional physical connection, the exchange of control frames between the initiator and the responder will determine if the connection can be associated with an existing mobile multilink session or if the connection is an independent connection by using the following procedure.
+
+##### **H.6.2.3.1 Procedure for initiator**
+
+The initiator shall immediately start to send control frames for *request additional*. The payload for *request additional* control frames shall contain the **callAssociationNumber** that was determined in clause H.6.2.1 and a 16-bit CRC field, see Figure H.7.
+
+![](c6212a3b14736d6a8c81ace75ae94ccf_img.jpg)
+
+|                                                   |       |
+|---------------------------------------------------|-------|
+| <b>callAssociationNumber</b> field                | Octet |
+|                                                   | 1     |
+|                                                   | 2     |
+|                                                   | 3     |
+| CRC field (see clause 7.4.3.2.3 of [ITU-T H.223]) | 4     |
+|                                                   | 5     |
+|                                                   | 6     |
+
+**Figure H.7 – Payload for *request additional* control frames**
+
+If it detects control frames for *accept additional*, it shall add this connection to the existing session that has the same **callAssociationNumber**. If it cannot detect a control frame for *accept additional* until the appropriate timer expires, it shall disconnect this additional connection.
+
+##### H.6.2.3.2 Procedure for responder
+
+##### H.6.2.3.2.1 Responder capable of an independent session
+
+If the responder allows another independent session of either mobile multilink or Annex C, it shall immediately start to send control frames for *initial connection* with its highest supported multiplex level.
+
+If it detects a control frame for *request additional* that has the same **callAssociationNumber** as that of an existing session, it shall immediately start to send multiple control frames for *accept additional*, and shall add this connection to the session. The number of control frames sent should be sufficient for the receiver to detect taking into account the mobile channel condition.
+
+If it detects a control frame for *initial connection*, it shall start a new session according to the procedure in clause H.6.1. If it detects a stuffing sequence for Annex C, it shall start the Annex C set-up procedure according to clause C.6.
+
+##### H.6.2.3.2.2 Responder not capable of an independent session
+
+If the responder is not capable of another independent session, it shall immediately start to send control frames for *accept additional*.
+
+If it detects control frames for *request additional* that has the same **callAssociationNumber** as that of an existing session, it shall add this connection to the session. If it detects control frames for *initial connection* or stuffing sequence for Annex C, it shall disconnect this additional connection.
+
+### H.6.3 Removing physical connections
+
+#### H.6.3.1 Removing last remaining connection
+
+Phases F and G in clause C.5 shall be followed to remove the last remaining physical connection at the end of an ITU-T H.324 session.
+
+#### H.6.3.2 Removing additional connections
+
+See clause F.5.3.2 with references to ITU-T H.226, ITU-T H.226 channel set, ITU-T H.226 header and ITU-T H.226 data set replaced by the mobile multilink, mobile multilink connections, mobile multilink header and mobile multilink frames, respectively, except for the procedure when a connection is removed accidentally. If a connection is removed accidentally, each terminal shall assign a channel tag to each of the remaining channels before the next information frames are transmitted.
+
+When one or more channels are removed from a multilink session, the transmitting entity of the multilink shall assign a channel tag from 0 to (N-1) to each of the channels, where N is the number of connections in use.
+
+## H.7 Header modes
+
+Mobile multilink operation has two modes for information frame transmission: full header mode and compressed header mode. This clause defines these modes and the mode transition procedures.
+
+### H.7.1 Full header mode
+
+In full header mode, the full header defined in Figure H.4 is used for information frames on all channels. In this mode, the transmitter may change the value of SS and SPF in the information frame header, but the transmitter shall send the **MobileMultilinkReconfigurationIndication** message to the receiver before changing the values.
+
+Mobile multilink starts with this mode, and the initial value of SS shall be set to "1", and that of SPF shall be set to "255".
+
+### H.7.2 Compressed header mode
+
+In compressed header mode, the compressed header defined in Figure H.5 is used for information frames on all channels. In this mode, the transmitter shall use the same SS and SPF values with those used for the last information frames in full header mode.
+
+### H.7.3 Mode transition (from full header to compressed header)
+
+When the receiver has synchronized the frame timing of the information frames in full header mode, the receiver shall send the **MobileMultilinkReconfigurationCommand** with the detected SS and SPF values and the status of **synchronized**. On the receipt of this command, the transmitter shall assess the SS and SPF values in the command message. If these values are the same as the values in use, then the transmitter shall change the mode from full header mode to compressed header mode. Otherwise, the transmitter shall continue the operation in full header mode.
+
+### H.7.4 Transition from compressed header mode to full header mode
+
+If the receiver finds that better SS and SPF values for the current channel conditions (e.g., bit error rate or burst error characteristics), the receiver may request to change these values by sending **MobileMultilinkReconfigurationCommand** with the detected SS and SPF values and the status of **reconfiguration**. On the receipt of this command, the transmitter shall move to the full header mode. The receiver should use the values for SS and SPF in the command message, but the actual value used for the information frames is up to the transmitter.
+
+# Annex I
+
+## Usage of HTTP generic capability in ITU-T H.324 terminals
+
+(This annex forms an integral part of this Recommendation)
+
+## I.1 General
+
+This annex defines the usage of hypertext transfer protocol (HTTP) [IETF RFC 2616] capability in ITU-T H.324 terminals. HTTP is an application-level protocol for distributed, collaborative, hypermedia information systems, and its technical specifications are provided in [IETF RFC 2616]. The capability presented in this annex is used for applications that want to make use of HTTP capabilities in ITU-T H.324 terminals.
+
+The purpose of using an HTTP channel associated with an ITU-T H.324 call is to permit the HTTP client (e.g., web browser) to remotely operate a far-end ITU-T H.324 endpoint (in which the HTTP server is implemented). This is especially useful in cases where the far-end ITU-T H.324 endpoint is an automatic device.
+
+For example, by selecting items on a web page, the human user could cause the far-end system to switch input video or audio sources, or control far-end audio pickup. In another example, the human user could choose via a web page to view one of a set of stored audiovisual streams, which might contain entertainment or educational material.
+
+Figure AnI.1 illustrates such an example. In this example, an ITU-T H.324 Annex I terminal (on the left) receives audiovisual content from a content server where ITU-T H.324 Annex I is implemented. The logical channel for HTTP transactions, which is used to select the audiovisual content to be sent, is opened using ITU-T H.245 logical channel signalling. Separate logical channels for delivery of audio and video data may be opened using ITU-T H.245 logical channel signalling, if necessary.
+
+![Diagram of an application using ITU-T H.324 Annex I. It shows an Annex I/ITU-T H.324 terminal on the left and a Content server with Annex I/ITU-T H.324 on the right, connected by a circuit-switched connection. The terminal contains an HTTP client, audio and video decoders, and an ITU-T H.223 MUX. The server contains an HTTP server, audio and video content sources, and an ITU-T H.223 MUX. Logical channels (LCN 0, i, j, k) are shown for signalling, HTTP, audio, and video respectively.](59121d561a4158609b4c354b9ffd0605_img.jpg)
+
+The diagram illustrates the internal architecture and data flow of an ITU-T H.324 Annex I terminal and a content server connected via a circuit-switched connection.
+
+- Annex I/ITU-T H.324 terminal (Left):**
+  - Contains an **HTTP client** connected to an **Underlying protocol** block (LCN i).
+  - Contains an **Audio decoder** connected to an **Audio** block (LCN j).
+  - Contains a **Video decoder** connected to a **Video** block (LCN k).
+  - Both the **Underlying protocol** and the **Audio/Video** blocks are connected to an **ITU-T H.223 MUX**.
+  - The **ITU-T H.223 MUX** is connected to the **Circuit-switched connection**.
+- Content server with Annex I/ITU-T H.324 (Right):**
+  - Contains a **Server HTTP** connected to an **Underlying protocol** block (LCN i).
+  - Contains an **Audio content** source connected to an **Audio** block (LCN j).
+  - Contains a **Video content** source connected to a **Video** block (LCN k).
+  - Both the **Underlying protocol** and the **Audio/Video** blocks are connected to an **ITU-T H.223 MUX**.
+  - The **ITU-T H.223 MUX** is connected to the **Circuit-switched connection**.
+- Signalling and Data Flow:**
+  - An orange arrow labeled **Logical channel signalling For HTTP/audio/video** points from the terminal's **ITU-T H.245** block (LCN 0) to the server's **ITU-T H.245** block (LCN 0).
+  - A blue double-headed arrow labeled **Exchange information about audio/video content** connects the terminal's **Underlying protocol** (LCN i) and the server's **Server HTTP** (LCN i).
+  - A black arrow labeled **Audio content** points from the server's **Audio** block (LCN j) to the terminal's **Audio decoder**.
+  - A black arrow labeled **Video content** points from the server's **Video** block (LCN k) to the terminal's **Video decoder**.
+
+Diagram of an application using ITU-T H.324 Annex I. It shows an Annex I/ITU-T H.324 terminal on the left and a Content server with Annex I/ITU-T H.324 on the right, connected by a circuit-switched connection. The terminal contains an HTTP client, audio and video decoders, and an ITU-T H.223 MUX. The server contains an HTTP server, audio and video content sources, and an ITU-T H.223 MUX. Logical channels (LCN 0, i, j, k) are shown for signalling, HTTP, audio, and video respectively.
+
+Figure AnI.1 – An application using ITU-T H.324 Annex I
+
+## I.2 Logical channel for HTTP
+
+The terminals which intend to use the HTTP capability shall open bidirectional logical channels for HTTP messages encapsulated by the underlying protocol specified in Table I.3.
+
+The error protection for these logical channels may be arbitrarily negotiated, requested and chosen by use of the "transport" field in the generic capability.
+
+## I.3 HTTP generic capability
+
+Table I.1 defines the capability identifier for HTTP generic capability. Tables I.2 and I.3 define the associated capability parameters.
+
+**Table I.1 – Capability identifier for HTTP capability**
+
+| Capability name             | HTTP                                                            |
+|-----------------------------|-----------------------------------------------------------------|
+| Capability class            | Data application                                                |
+| Capability identifier type  | Standard                                                        |
+| Capability identifier value | itu-t (0) recommendation (0) h(8) 324 generic-capabilities(1) 0 |
+| maxBitRate                  | This field shall be included.                                   |
+| nonCollapsingRaw            | This field shall not be included.                               |
+| Transport                   | This field shall be included.                                   |
+
+**Table I.2 – Mode for HTTP capability**
+
+| Parameter name             | mode                                                                                                                                                                                                                                                 |
+|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Parameter description      | This is a nonCollapsing GenericParameter.<br>mode indicates the operating mode of the terminal:<br>1) Server<br>2) Client<br>3) Server and Client (this mode may be used in capability exchange, but shall not be set in logical channel signalling) |
+| Parameter identifier value | 0                                                                                                                                                                                                                                                    |
+| Parameter status           | Mandatory                                                                                                                                                                                                                                            |
+| Parameter type             | unsignedMin                                                                                                                                                                                                                                          |
+| Supersedes                 | –                                                                                                                                                                                                                                                    |
+
+**Table I.3 – Underlying protocol for HTTP capability**
+
+| Parameter name             | underlyingProtocol                                                                                                             |
+|----------------------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Parameter description      | This is a nonCollapsing GenericParameter.<br>underlyingProtocol indicates the protocol under HTTP:<br>0) None<br>1) TCP/IP/PPP |
+| Parameter identifier value | 1                                                                                                                              |
+| Parameter status           | Mandatory                                                                                                                      |
+| Parameter type             | unsignedMin                                                                                                                    |
+| Supersedes                 | –                                                                                                                              |
+
+## I.4 References
+
+See clause 2.
+
+# Annex J
+
+## ASN.1 OIDs defined in this Recommendation
+
+(This annex forms an integral part of this Recommendation)
+
+This annex summarizes the OIDs defined in this Recommendation and defines ITU-T H.324 generic capabilities which are used in ITU-T H.245 signalling-based systems.
+
+## J.1 Summary of OIDs defined in this Recommendation
+
+**Table J.1 – Summary of OIDs defined in this Recommendation**
+
+| OID                                                                                           | Clause reference |
+|-----------------------------------------------------------------------------------------------|------------------|
+| { itu-t(0) recommendation(0) h(8) 324 generic-capabilities(1) sessionResetCapability(1) }     | 7.7.1            |
+| { itu-t(0) recommendation(0) h(8) 324 generic-capabilities(1) mona(2) }                       | K.10.1           |
+| { itu-t(0) recommendation(0) h(8) 324 generic-capabilities(1) mona(2) mos(1) }                | K.8.3            |
+| { itu-t(0) recommendation(0) h(8) 324 generic-capabilities(1) mona(2) mosack(2) }             | K.8.3            |
+| { itu-t(0) recommendation(0) h(8) 324 generic-capabilities(1) textConversationCapability(3) } | L.4.1            |
+
+## J.2 Session reset capability identifier
+
+**Table J.2 – Capability identifier for session reset**
+
+| Capability name             | sessionResetCapability                                                                    |
+|-----------------------------|-------------------------------------------------------------------------------------------|
+| Capability identifier type  | Standard                                                                                  |
+| Capability identifier value | { itu-t(0) recommendation(0) h(8) 324 generic-capabilities(1) sessionResetCapability(1) } |
+| maxBitRate                  | This parameter is not used.                                                               |
+| Collapsing                  | This field shall not be used and shall be ignored by receivers.                           |
+| nonCollapsing               | This field shall not be used and shall be ignored by receivers.                           |
+| nonCollapsingRaw            | This field shall not be used and shall be ignored by receivers.                           |
+| Transport                   | This field shall not be used and shall be ignored by receivers.                           |
+
+# Annex K
+
+# Media oriented negotiation acceleration procedure
+
+(This annex forms an integral part of this Recommendation)
+
+## K.1 Abstract
+
+This annex specifies an optional enhancement to the ITU-T H.324 call set-up procedure, to be used only in conjunction with Annex C, which allows media channels to be established in a fast and flexible manner.
+
+## K.2 General
+
+When the optional media oriented negotiation acceleration procedure is in use, there is an initial transmission of messages called MONA preference messages that are used to transmit preferences relevant to initial set-up of the media channels. The details of media channel set-up fall to one of several established signalling methods, depending on the channel set-up capabilities and preferences of the terminals as exchanged in the preference messages. Terminals may utilize a fast channel set-up which does not wait for capability exchange, but which requires fallback in the case where the initial channel transmission attempts do not succeed. Terminals may also utilize a flexible accelerated channel set-up method that depends on an initial exchange of preferences and the execution of a common inference algorithm on both sides. All terminals are capable of a reasonably fast fallback mechanism implemented as a minor change to the existing ITU-T H.245 procedures.
+
+## K.3 References
+
+See clause 2.
+
+## K.4 Definitions and format conventions
+
+### K.4.1 Definitions
+
+This annex defines the following terms:
+
+**K.4.1.1 inferred common mode (ICM):** The unique non-conflicting media mode determined by both terminals based on media preferences of local and peer MOS profile requests (always the same for both terminals). ICM is applicable to MOS only.
+
+**K.4.1.2 normal multiplexer level operation (NMLO):** The normal operation of the ITU-T H.223 multiplexer on the bearer channel. This is phase E of ITU-T H.324.
+
+### K.4.2 Abbreviations
+
+This annex uses the following abbreviations:
+
+|     |                                       |
+|-----|---------------------------------------|
+| ACP | Accelerated ITU-T H.245 Procedures    |
+| FEA | Frame Emulation Avoidance (procedure) |
+| FI  | Frame Information                     |
+| MOS | Media Oriented Set-up                 |
+| MPC | Media Preconfigured Channel           |
+| MTE | Multiplexer Table Entry               |
+| OLC | Open Logical Channel                  |
+| PL  | Payload Length                        |
+| PSR | Payload Segmentation and Reassembly   |
+
+|     |                                             |
+|-----|---------------------------------------------|
+| RTD | Round Trip Delay                            |
+| SPC | Signalling Preconfigured Channel            |
+| SPP | Signalling Preconfigured channel Preference |
+| SSN | Segment Sequence Number                     |
+
+### K.4.3 Format conventions
+
+The numbering, field mapping and bit transmission conventions used are consistent with those used in clause 3.2 of [ITU-T H.223].
+
+## K.5 Terminal procedures
+
+The steps for provision of communication are as listed in clause C.5 with the following modifications:
+
+Phase D: MONA phase, as specified in this annex, is inserted during the level set-up procedure.
+
+## K.6 MONA signalling
+
+The initial exchange of preferences between MONA-capable terminals is performed using preference messages, short messages that include signalling to accelerate the establishment of multimedia sessions. These messages shall include the information of the supported methods for initial media channel creation.
+
+### K.6.1 Framing
+
+The MONA preference message frames are octet aligned and have the structure shown in Table K.1.
+
+**Table K.1 – Structure of a MONA preference message frame**
+
+|                                                |
+|------------------------------------------------|
+| Frame Information (FI) (1 octet)               |
+| Reserved (Always 0x00) (1 octet)               |
+| Payload Length (PL) (1 octet)                  |
+| Payload<br>(0 or more octets up to 150 octets) |
+| CRC (2 octets)                                 |
+
+The **Frame Information (FI)** bit allocation is shown in Table K.2. Bit 8 is reserved and shall be set to 1. Bit 7 represents the **Last Segment (LS)** flag, and the three following bits represent the **Segment Sequence Number (SSN)**. The three least significant bits are reserved and shall be set to 0.
+
+**Table K.2 – Bit structure of the MONA Frame Information (FI) field**
+
+|   |    |      |      |      |   |   |   |
+|---|----|------|------|------|---|---|---|
+| 8 | 7  | 6    | 5    | 4    | 3 | 2 | 1 |
+| 1 | LS | SSN3 | SSN2 | SSN1 | 0 | 0 | 0 |
+
+The **Payload Length (PL)** field indicates the payload size in octets before the application of the frame emulation avoidance (FEA) procedure.
+
+The **Payload** consists of the preference message capability description, as defined below.
+
+The **cyclic redundancy check (CRC)** field is 16 bits and is determined by applying the CRC described in clause 8.1.1.6.1 of [ITU-T V.42] to the entire frame, excluding the MONA synchronization flags and the CRC field, and before FEA.
+
+On detecting a CRC error or undefined frame information or undefined reserved bits, the corresponding MONA preference message frame shall be discarded, except in cases where MONA framing is used to encapsulate MPC media data. In such cases, the terminal may have a media decoder capable of error correction and/or concealment, and so the corrupted media may be salvaged as appropriate.
+
+The MONA synchronization flag is defined in Table K.3.
+
+**Table K.3 – Structure of the MONA synchronization flag**
+
+|      |                 |
+|------|-----------------|
+| 0xA3 | 1 0 1 0 0 0 1 1 |
+| 0x35 | 0 0 1 1 0 1 0 1 |
+
+One MONA synchronization flag shall be inserted immediately before and after each preference message frame. Only one MONA synchronization flag shall exist between two consecutive preference message frames.
+
+Segmentation and reassembly of preference message frames is done using a modified version of the control channel segmentation and reassembly layer (CCSRL) procedure defined in clause C.8.1. The following modifications are made:
+
+- The LS flag shall be used in place of CCSRL LS. LS shall be set to 1 on the PDU containing the last segment of an SDU. It shall be set to 0 otherwise.
+- The SSN shall be set to 0 for the first segment and monotonically incremented for each segment, the maximum value of SSN shall be 6. The value 7 is reserved.
+
+A flag emulation avoidance (FEA) procedure shall be performed against synchronization flags for all multiplexer levels of ITU-T H.324 before transmitting a MONA preference message frame onto the bearer. Frame information, payload length, payload and CRC are included in the FEA procedure. All octets with values 0xA3, 0x35, 0xE1, 0x4D, 0x1E, 0xB2, 0x19, 0xB1, 0x7E and 0xC5 shall have an octet with value 0xC5 inserted immediately preceding them.
+
+### K.6.2 Payload
+
+The preference message payload contains the information of the initial accelerated call set-up method capabilities. These capabilities indicate which methods may be used for establishment of media channels. The payload is defined in Tables K.4 and K.5. For transmission, this payload is considered to consist of 16-bit words which are sent in little-endian order.
+
+**Table K.4 – Bit fields defining preference message capabilities**
+
+| 16      | 15  | 14     | 13 | 12       | 11 | 10 | 9      | 8      | 7       | 6 | 5 | 4 | 3 | 2 | 1 |
+|---------|-----|--------|----|----------|----|----|--------|--------|---------|---|---|---|---|---|---|
+| VER     | SPC | MPC-RX |    |          |    |    |        |        |         |   |   |   |   |   |   |
+| ACK     | SPP | MPC-TX |    |          |    |    |        |        |         |   |   |   |   |   |   |
+| MONA-ML |     |        |    | Reserved |    |    | SPC-DA | SPC-DC | EXT-LEN |   |   |   |   |   |   |
+
+**Table K.5 – Preference message capability definition**
+
+| Capability name                                         | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Version (VER)                                           | MONA version number (2 bits). It shall be set to 0 for the current version. The value 3 is reserved.                                                                                                                                                                                                                                                                                                                                                                      |
+| Signalling preconfigured channel (SPC) support          | Set to 1 if the MONA terminal supports negotiation of logical channels using the signalling preconfigured channel, set to 0 otherwise.                                                                                                                                                                                                                                                                                                                                    |
+| Media preconfigured channel receive bits (MPC-RX)       | (13 bits) Describes which media preconfigured channel configurations the MONA terminal is capable of receiving.<br>The bit numbers, (from 1 to 13) as shown in Table K.4, correspond exactly to the MUX code values in the media preconfigured channel configuration (See Table K.15).                                                                                                                                                                                    |
+| Acknowledgement state (ACK)                             | The MONA terminal shall set ACK in its outgoing preference messages as follows:<br>00 – MONA terminal has not successfully received any incoming preference messages<br>01 – MONA terminal acknowledges receiving at least one incoming preference message containing an ACK value of 00<br>10 – MONA terminal acknowledges receiving at least one incoming preference message containing an ACK value of 01<br>11 – Reserved                                             |
+| Signalling preconfigured channel preference (SPP)       | Set to 1 if the MONA terminal prefers negotiation of logical channels using the signalling preconfigured channel, set to 0 otherwise.                                                                                                                                                                                                                                                                                                                                     |
+| Media preconfigured channel transmit bits (MPC-TX)      | (13 bits) Describes which media preconfigured channel configurations the MONA terminal is capable of sending.<br>The bit numbers (from 1 to 13) as shown in Table K.4 correspond exactly to the MUX code values in the media preconfigured channel configuration (See Table K.15).                                                                                                                                                                                        |
+| MONA multiplex level (MONA-ML)                          | (5 bits) Represents the multiplexer level preference of the terminal.<br>First 3 MSBs indicate initial multiplexer level. Fourth bit indicates using ITU-T H.223 Annex A double flag mode. Fifth bit indicates using ITU-T H.223 Annex B optional header mode.<br>Operating multiplexer level shall be determined as defined in clause C.6.2 but without transmission, recognizing the MONA-ML in the transmitted and received preference message as the starting points. |
+| Reserved                                                | Reserved bits shall be set to zero. Non-zero values received shall be ignored.                                                                                                                                                                                                                                                                                                                                                                                            |
+| Signalling preconfigured channel delay attempt (SPC-DA) | (1 bit) SPC delay attempt. When set (to 1), it is an indication that a device wants the peer device to not time out for SPC upon not receiving SPC MOS Ack.<br>SPC-DA shall not be set if SPC-DC is set.                                                                                                                                                                                                                                                                  |
+| Signalling preconfigured channel delay capable (SPC-DC) | (1 bit) SPC delay capable. When set (to 1), it is an indication that a device is capable of delaying time out for SPC upon not receiving SPC MOS Ack.<br>SPC-DC shall not be set if SPC-DA is set.                                                                                                                                                                                                                                                                        |
+| Extension length (EXT-EN)                               | (7 bits) Length of additional capability information, in octets.                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+Terminals shall support at least one preconfigured channel receive capability.
+
+NOTE – This requirement may be met by setting SPC to 1, or by setting at least one non-zero bit within MPC-RX.
+
+The SPC field indicates whether the terminal supports channel negotiation using the procedures defined in clause K.8. The SPP field indicates whether the terminal prefers channel negotiation using the procedures defined in clause K.8. Interpretation of these fields is given in clause K.7.
+
+Media oriented negotiation acceleration multiplex level (MONA-ML) is used to signal the multiplex level used in the case where the media channels are negotiated using the accelerated procedures of this annex (see clauses K.8, K.9 and K.10).
+
+The ACK bits are used by the terminal to signal the acknowledgement state of the peer's preference message.
+
+The SPC-DC and SPC-DA fields are used to signal SPC MOS request delay capability or request. Interpretation of these fields is given in clause K.8.1.1.
+
+Future protocol versions may add extra fields to the end of the capability information defined in Table K.4. The length of such extra information in octets is provided in the EXT-LEN field. For compatibility with such future versions, a terminal that receives a preference message with VER set to an unknown version should discard the extra information.
+
+Preference message frames may be used to encapsulate media per the definition in clause K.9.3 and encapsulate signalling per the definition of clause K.9.4.
+
+## **K.7 Channel establishment method negotiation**
+
+### **K.7.1 MONA algorithm**
+
+A MONA-capable terminal begins the session establishment procedure by transmitting at least ten repetitions of the preference message which contains information about its channel establishment capabilities and preferences. All outgoing preference messages sent from a terminal during a particular session shall contain identical information in the preference message capability payload, with the exception of the acknowledgement state (ACK).
+
+The ACK bits are used by the terminal to signal an acknowledgement of the peer's preference message. These bits are set to 00 in the initial transmission. After receiving at least one incoming preference message, the ACK bits in subsequent outgoing preference messages shall be set to 01 to acknowledge the reception of the incoming preference message. After receiving at least one incoming preference message with the ACK set to 01, the ACK bits in subsequent outgoing preference messages shall be set to 10. Upon receiving an incoming preference message with ACK containing value 10, or receiving the first non-empty ITU-T H.223 MUX-PDU, the terminal shall stop sending outgoing preference messages. In the case of an active SPC/MOS negotiation, a terminal shall continue sending preference messages encapsulating the SPC/MOS messages until completion of the procedures of clause K.8.
+
+After sending the initial preference message repetitions, but before receiving incoming preference messages from the remote end, the MONA-capable terminal may make outgoing transmissions with any combination of the following:
+
+- It may send media data on one or more media preconfigured channels (per definition in clause K.9.3).
+- It may send session signalling data on the signalling preconfigured channel (per the definition in clause K.9.4).
+- It may send multiplexer level set-up flags (per the definition in clause K.7.1.1).
+
+The MONA-capable terminal shall not transmit media on any preconfigured channels not indicated in the MPC-TX bits of the outgoing preference messages sent by the terminal. The terminal shall continue to send at least one preference message between each pair of outgoing preconfigured channel PDUs until the stopping criterion (defined previously) is reached.
+
+Upon the successful receipt of an incoming preference message, the MONA-capable terminal shall examine the received MPC-RX bits to determine which outgoing media preconfigured channels were not successfully established. The transmission of any such unsuccessful channels shall be immediately dropped.
+
+At this point, the channel negotiation behaviour of the terminal is determined as follows:
+
+- If both terminals have indicated support for the procedures of clause K.8 (SPC) and at least one of the two terminals indicates preference for those procedures (SPP), then all outgoing media preconfigured channels shall be dropped, and channel negotiation shall proceed using the procedures of clause K.8.
+
+NOTE 1 – In this case, the media preconfigured channels are never considered to be successfully established.
+
+- If both terminals have indicated support for the procedures of clause K.8 (SPC) and a comparison of the MPC sending and receiving capabilities (expressed as the MPC-RX and MPC-TX bits exchanged between both sides) indicates that no successful preconfigured channels can be established in the current session, then channel negotiation shall proceed using the procedures of clause K.8.
+
+NOTE 2 – Such determination may be made by logical AND-ing of the local MPC-RX bits with the remote MPC-TX bits, and likewise AND-ing of the remote MPC-RX bits with the local MPC-TX bits.
+
+- In all other cases, the terminal shall establish the missing outgoing media channels for each media type using one of the following procedures:
+
+- If examination of the received MPC-RX bits indicates that a media preconfigured channel can be successfully established for the given media type, the terminal may begin transmitting media on the appropriate preconfigured channel.
+
+NOTE 3 – Successful channel establishment is guaranteed in this case. If this is used for fallback following a failed transmission attempt, then it is equivalent to the MPC-Fallback procedure defined in clause K.9.3.
+
+- The terminal may establish the outgoing channel using the procedures of clause K.10 (ACP).
+
+- If the procedures of clause K.8 (SPC) are used to establish media channels, the following apply:
+
+- SPC negotiation procedures exchange media oriented set-up (MOS) request messages in order to establish media channels.
+- The SPC channel negotiation will make use of any MOS request messages previously exchanged using the signalling preconfigured channel. The initial exchange of MOS request messages is independent of the exchange of preference messages.
+- If one or both sides have not sent initial signalling preconfigured channel transmissions, they shall begin to do so as soon as the decision to use SPC has been made through the exchange of preference messages. A terminal may delay transmission of SPC/MOS requests in accordance with the use of SPC-DC and SPC-DA as described in Table K.5 and clause K.8.1.1.
+
+NOTE 4 – Terminals supporting SPC will achieve better session set-up if they transmit SPC/MOS at an earlier time than the SPP determination.
+
+- Upon receiving the first incoming ITU-T H.245 message from a remote MONA terminal, a MONA terminal shall immediately initiate outgoing ITU-T H.245 TerminalCapabilitySet (TCS) and MasterSlaveDetermination (MSD) procedures, if such procedures have not yet been started.
+
+NOTE 5 – Prior to sending any ITU-T H.245 messages during a session, ITU-T H.245 TerminalCapabilitySet (TCS) and MasterSlaveDetermination (MSD) requests are required to be sent according to clause 7.4. The use of ITU-T H.245 signalling, including ACP, requires initiating both the TerminalCapabilitySet (TCS) and MasterSlaveDetermination (MSD) procedures.
+
+#### K.7.1.1 Multiplexer flag interleaving
+
+A terminal should insert stuffing flags of its multiplexer level, as described in clause C.6.1, between adjacent preference messages and/or preconfigured channel PDUs. No more than 20 stuffing flags shall be inserted. Interleaving should be halted upon reception of a preference message.
+
+The initial level used for such interleaved flags shall match the multiplexer level preference signalled in the MONA-ML field.
+
+Figure K.1 illustrates some acceptable patterns of MONA sync flags, MONA preference message frames and multiplexer level stuffing flags.
+
+![Figure K.1: Illustration showing several acceptable patterns of MONA sync flags, MONA preference message frames and multiplexer level stuffing flags. The diagram consists of three horizontal rows of colored boxes. The first row shows a sequence of MONA sync flag (green), Preference message frame (yellow), and MONA sync flag (green). The second row shows a sequence of MONA sync flag (green), Preference message frame (yellow), MONA sync flag (green), Preference message frame (yellow), and MONA sync flag (green). The third row shows a sequence of MONA sync flag (green), Preference message frame (yellow), MONA sync flag (green), MUX level flags (no more than 20) (blue), MONA sync flag (green), Preference message frame (yellow), and MONA sync flag (green).](070352b751dd0711b8ac6ddfa6df1d98_img.jpg)
+
+|                |                          |                |                                      |                |                          |                |
+|----------------|--------------------------|----------------|--------------------------------------|----------------|--------------------------|----------------|
+| MONA sync flag | Preference message frame | MONA sync flag |                                      |                |                          |                |
+| MONA sync flag | Preference message frame | MONA sync flag | Preference message frame             | MONA sync flag |                          |                |
+| MONA sync flag | Preference message frame | MONA sync flag | MUX level flags<br>(no more than 20) | MONA sync flag | Preference message frame | MONA sync flag |
+
+Figure K.1: Illustration showing several acceptable patterns of MONA sync flags, MONA preference message frames and multiplexer level stuffing flags. The diagram consists of three horizontal rows of colored boxes. The first row shows a sequence of MONA sync flag (green), Preference message frame (yellow), and MONA sync flag (green). The second row shows a sequence of MONA sync flag (green), Preference message frame (yellow), MONA sync flag (green), Preference message frame (yellow), and MONA sync flag (green). The third row shows a sequence of MONA sync flag (green), Preference message frame (yellow), MONA sync flag (green), MUX level flags (no more than 20) (blue), MONA sync flag (green), Preference message frame (yellow), and MONA sync flag (green).
+
+H.324(09)\_FK.1
+
+**Figure K.1 – Illustration showing several acceptable patterns of MONA sync flags, MONA preference message frames and multiplexer level stuffing flags**
+
+#### K.7.1.2 Legacy interworking
+
+When communicating with a legacy terminal, a MONA terminal will encounter standard multiplexer level flags. In order to have negligible impact on set-up time with the legacy terminal, a MONA terminal should try to detect the standard multiplexer level set-up as soon as possible and revert to legacy behaviour, cease all MONA transmissions and follow normal start-up procedures as defined in Annex C. Either of the following conditions shall initiate fallback to legacy behaviour:
+
+- More than 20 valid consecutive multiplexer level stuffing flags are detected, as described in clause C.6.
+- A normal start-up procedure is detected with a normal ITU-T H.245 TerminalCapabilitySet message as the first non-empty ITU-T H.223 MUX-PDU at an initial multiplexer level agreed by detecting standard multiplexer level set-up.
+
+### K.7.2 Terminal requirements and illustrative behaviour
+
+#### K.7.2.1 Minimum terminal requirements
+
+It is possible for a MONA terminal to implement all aspects of the channel negotiation methods defined in clauses K.8, K.9 and K.10. However, a complete implementation is not required. The minimum set of channel negotiation method elements which shall be supported by all compliant MONA terminals are as follows:
+
+- 1) MONA terminals shall support the MONA signalling defined in clause K.6 and the MONA algorithm defined in clause K.7.1.
+- 2) MONA terminals shall be capable of opening incoming and outgoing channels using the accelerated ITU-T H.245 procedures (ACP) defined in clause K.10.
+- 3) MONA terminals shall support at least one preconfigured channel receive capability. This may be met in one of two ways:
+  - a) the terminal may set SPC to 1, to indicate the capability of negotiating channels via the SPC procedures (clause K.8); or
+  - b) the terminal may set one or more MPC-RX bits to 1, to indicate the capability to receive media using the MPC procedures (clause K.9).
+
+Hence, MONA terminal implementations could be classified into three classes:
+
+- **Class I: SPC+MPC+ACP** – The terminal supports all three procedures.
+- **Class II: MPC+ACP** – The terminal supports the MPC and ACP procedures.
+- **Class III: SPC+ACP** – The terminal supports the SPC and ACP procedures.
+
+#### K.7.2.2 Typical decision logic (informative)
+
+The following figures show how typical MONA terminal classes would establish a single outgoing audio and a single outgoing video channel. A key to the symbols used in these diagrams is provided in Figure K.2.
+
+![Flowchart illustrating typical decision logic for MONA terminal classes. The flow starts with a 'Start condition' (parallelogram), followed by an 'Action' (circle), then an 'Event' (horizontal line), a 'Decision?' (diamond) with 'Y' (Yes) and 'N' (No) paths, and finally an 'End' (square with X). The diagram is labeled H.324(09)_FK.2.](572cf014db14c8234f91c07d5a5a28c6_img.jpg)
+
+```
+graph TD; A[/Start condition/] --> B((Action)); B --> C[Event]; C --> D{Decision?}; D -- Y --> E[ ]; D -- N --> F[⊠ End]; style E fill:none,stroke:none;
+```
+
+Flowchart illustrating typical decision logic for MONA terminal classes. The flow starts with a 'Start condition' (parallelogram), followed by an 'Action' (circle), then an 'Event' (horizontal line), a 'Decision?' (diamond) with 'Y' (Yes) and 'N' (No) paths, and finally an 'End' (square with X). The diagram is labeled H.324(09)\_FK.2.
+
+Figure K.2 – Key to the symbols used in Figures K.3 through K.6
+
+##### **K.7.2.2.1 Capability class I: SPC + MPC + ACP**
+
+Figure K.3 shows the logic which a class I MONA terminal would follow in order to establish the outgoing audio and video channels to a remote MONA terminal. Depending on the specific capabilities and preferences expressed by the terminals, it is possible that all channels would be established using a single method (SPC, ACP or MPC), or that a combination of MPC and ACP techniques could be applied on a per-channel basis.
+
+![Flowchart illustrating the logic typically used by a class I MONA terminal to establish outgoing audio and video channels to a remote MONA terminal. The process starts with a terminal supporting SPC + MPC + ACP, followed by transmitting preference messages and MOS requests. It then checks for remote SPC support and preferences, leading to either dropping transmissions or establishing channels via SPC or ACP/MPC procedures.](9c80cf99954eb0142f694456d39fae4b_img.jpg)
+
+```
+
+graph TD
+    Start[/MONA-to-MONA:  
+Terminal supports  
+SPC + MPC + ACP/] --> Step1((Transmit MONA preference messages  
+(initial repetitions)))
+    Step1 --> Step2((Transmit MOS requests on SPC  
+and/or outgoing media on MPC(s)  
+and/or standard level set-up flags))
+    Step2 --> Step3((MONA preference message(s)  
+received from remote end))
+    Step3 --> Step4((Drop unsuccessful  
+outgoing MPCs, if any))
+    Step4 --> Decision1{Does  
+remote terminal  
+support SPC  
+(test SPC bit)?}
+    Decision1 -- N --> Decision4{Are all desired  
+outgoing channels  
+established?}
+    Decision1 -- Y --> Decision2{Does  
+either terminal  
+prefer SPC  
+(test SPP bits)?}
+    Decision2 -- Y --> Step5((Drop all outgoing MPC  
+transmissions))
+    Decision2 -- N --> Decision3{Are any  
+MPCs possible  
+(test MPC-RX,  
+MPC-TX)?}
+    Decision3 -- Y --> Step6((Drop any outgoing SPC  
+transmission))
+    Decision3 -- N --> Step7((Establish all channels  
+using SPC procedures))
+    Step5 --> Step7
+    Step6 --> Decision4
+    Step7 --> Decision4
+    Decision4 -- Y --> End[All outgoing channels  
+established successfully]
+    Decision4 -- N --> Decision5{Prefer  
+ACP or MPC  
+to open missing  
+channel?}
+    Decision5 -- ACP --> Step8((Establish missing  
+channel using ACP))
+    Decision5 -- MPC --> Decision6{Does a  
+compatible MPC  
+exist for the  
+channel?}
+    Decision6 -- N --> Step8
+    Decision6 -- Y --> Step9((Transmit media  
+for missing  
+channel using  
+compatible MPC))
+    Step8 --> Step10[Execute procedures within  
+dotted line independently per  
+missing outgoing channel]
+    Step9 --> Step10
+    Step10 --> Decision4
+  
+```
+
+H.324(09)\_FK.3
+
+Flowchart illustrating the logic typically used by a class I MONA terminal to establish outgoing audio and video channels to a remote MONA terminal. The process starts with a terminal supporting SPC + MPC + ACP, followed by transmitting preference messages and MOS requests. It then checks for remote SPC support and preferences, leading to either dropping transmissions or establishing channels via SPC or ACP/MPC procedures.
+
+**Figure K.3 – Logic typically used by a class I MONA terminal to establish outgoing audio and video channels to a remote MONA terminal**
+
+##### K.7.2.2.2 Capability class II: MPC + ACP
+
+Figure K.4 shows the logic which a class II MONA terminal would follow in order to establish the outgoing audio and video channels to a remote MONA terminal. In this case, it is possible that all channels are established using either MPC or ACP, or that the two methods may be applied on a per-channel basis.
+
+![Flowchart showing the logic for establishing outgoing channels for a class II MONA terminal. The process starts with terminal support for MPC + ACP, followed by preference message transmission, media transmission, and handling of received preference messages. A loop for missing channels uses either MPC or ACP based on preference and compatibility.](abeba89144744fac6a1571aa9f94889e_img.jpg)
+
+```
+
+graph TD
+    Start[/MONA-to-MONA:  
+Terminal supports  
+MPC + ACP/] --> T1(( ))
+    T1 --> T1_desc[Transmit MONA preference messages  
+(initial repetitions)]
+    T1_desc --> T2(( ))
+    T2 --> T2_desc[Transmit outgoing media  
+on 1 or more MPCs and/or  
+standard level set-up flags]
+    T2_desc --> T3(( ))
+    T3 --> T3_desc[MONA preference message(s)  
+received from remote end]
+    T3_desc --> T4(( ))
+    T4 --> T4_desc[Drop unsuccessful  
+outgoing MPCs, if any]
+    T4_desc --> D1{Are all desired  
+outgoing channels  
+established?}
+    D1 -- Y --> End[All outgoing channels  
+established successfully  
+H.324(09)_FK.4]
+    D1 -- N --> D2{Prefer  
+ACP or MPC  
+to open missing  
+channel?}
+    subgraph Loop [Execute procedures within  
+dotted line independently per  
+missing outgoing channel]
+        D2 -- ACP --> T5(( ))
+        D2 -- MPC --> D3{Does a  
+compatible MPC  
+exist for the  
+channel?}
+        D3 -- N --> T5
+        D3 -- Y --> T6(( ))
+        T6 --> T6_desc[Transmit media for  
+missing channel using  
+compatible MPC]
+        T5 --> T5_desc[Establish missing  
+channel using ACP]
+    end
+    T6_desc --> End
+    T5_desc --> End
+    
+```
+
+Flowchart showing the logic for establishing outgoing channels for a class II MONA terminal. The process starts with terminal support for MPC + ACP, followed by preference message transmission, media transmission, and handling of received preference messages. A loop for missing channels uses either MPC or ACP based on preference and compatibility.
+
+**Figure K.4 – Logic typically used by a class II MONA terminal to establish outgoing audio and video channels to a remote MONA terminal**
+
+##### K.7.2.2.3 Capability class III: SPC + ACP
+
+Figure K.5 shows the logic which a class III MONA terminal would follow in order to establish the outgoing audio and video channels to a remote MONA terminal. For this case, either SPC or ACP will be selected depending on the contents of the sent and received MONA preference frames. The selected method will then be used to establish all audio and video channels in the current session.
+
+![Flowchart showing the logic for establishing outgoing audio and video channels for a class III MONA terminal.](b3d488012fdceacab867cf24c5efef05_img.jpg)
+
+```
+graph TD; A[/MONA-to-MONA:  
+Terminal supports  
+SPC + ACP/] --> B((Transmit  
+MONA preference messages  
+(initial repetitions))); B --> C((Transmit MOS requests  
+on SPC and/or standard  
+level set-up flags)); C --> D[MONA preference message(s)  
+received from remote end]; D --> E{Does  
+remote terminal  
+support SPC  
+(test SPC bit)?}; E -- Y --> F{Does  
+either terminal  
+prefer SPC  
+(test SPP bits)?}; E -- N --> G((Establish all channels  
+using ACP)); F -- Y --> H((Establish all channels  
+using SPC procedures)); F -- N --> G; G --> I[All outgoing channels  
+established successfully]; H --> I; H -- H.324(09)_FK.5 --> I;
+```
+
+The flowchart illustrates the logic for establishing outgoing audio and video channels for a class III MONA terminal. It begins with a terminal that supports both SPC and ACP. The process involves transmitting MONA preference messages and MOS requests. Upon receiving a MONA preference message from the remote end, the terminal checks if the remote terminal supports SPC (by testing the SPC bit). If not, it establishes all channels using ACP. If the remote terminal does support SPC, the terminal then checks if either terminal prefers SPC (by testing SPP bits). If SPC is preferred, it establishes all channels using SPC procedures. Otherwise, it falls back to using ACP. Both methods lead to all outgoing channels being established successfully. The diagram is labeled H.324(09)\_FK.5.
+
+Flowchart showing the logic for establishing outgoing audio and video channels for a class III MONA terminal.
+
+Figure K.5 – Logic typically used by a class III MONA terminal to establish outgoing audio and video channels to a remote MONA terminal
+
+##### K.7.2.2.4 MONA-to-legacy case
+
+Figure K.6 shows the logic by which a MONA terminal would detect that the remote terminal is not MONA-capable, and so revert to legacy ITU-T H.245 session negotiation (signalling) in order to establish the audio and video channels. This logic is applicable to any of the MONA capability classes.
+
+![Flowchart for the MONA-to-legacy case logic flow.](487c58c79e44e6cf98b6368b6667b9c6_img.jpg)
+
+```
+graph TD; A[/MONA-to-legacy/] --> B(( )); B --> C[Transmit MONA preference messages  
+(initial repetitions)]; C --> D(( )); D --> E[Transmit MOS requests on SPC  
+and/or outgoing media on MPC(s) and/or  
+standard level set-up flags]; E --> F[Detect incoming  
+>20 legacy stuffing flags or  
+normal ITU-T H.245 TerminalCapabilitySet]; F --> G(( )); G --> H[Drop outgoing MONA transmissions  
+and revert to legacy behavior]; H --> I[Session established via  
+regular ITU-T H.245 negotiation]; I --- J[H.324(09)_FK.6];
+```
+
+The flowchart illustrates the logic for the MONA-to-legacy case. It begins with a parallelogram labeled 'MONA-to-legacy'. The process then enters a loop: first, a circle followed by the text 'Transmit MONA preference messages (initial repetitions)'; second, another circle followed by 'Transmit MOS requests on SPC and/or outgoing media on MPC(s) and/or standard level set-up flags'; third, a circle followed by 'Detect incoming >20 legacy stuffing flags or normal ITU-T H.245 TerminalCapabilitySet'. If the detection condition is met, the flow proceeds to a circle followed by 'Drop outgoing MONA transmissions and revert to legacy behavior', which then leads to a crossed square symbol followed by 'Session established via regular ITU-T H.245 negotiation'. A small label 'H.324(09)\_FK.6' is at the bottom right.
+
+Flowchart for the MONA-to-legacy case logic flow.
+
+Figure K.6 – Logic flow for the MONA-to-legacy case
+
+## K.8 Channel establishment via the signalling preconfigured channel (SPC)
+
+### K.8.1 MOS profile exchange
+
+#### K.8.1.1 Procedure
+
+If a terminal supports the SPC, it shall send its MOS request (**mos**) using the SPC (see Table K.6) as defined in clause K.7.1. The MOS request transmissions should be repeated until a MOS **requestAck** (see Table K.14) is detected, or one of the conditions in clause K.8.2 is fulfilled. For the latter case, the procedure in clause K.8.2 shall be followed.
+
+When a MOS request is detected and decoded successfully from the MOS SPC, the terminal accepts it by beginning the transmission and processing of media data as determined by the ICM at NMLO using the agreed mobile level. MOS **requestAck** shall be sent on receiving every MOS request.
+
+Delayed transmission of MOS requests is only allowed when both the SPC-DA is set in the local PM and the SPC-DC is set in the remote PM received.
+
+If MOS is completed successfully, ITU-T H.245 message exchange is skipped and opened logical channels operate immediately. The procedure is shown in Figure K.7.
+
+NOTE 1 – The channels established through the MOS procedure operate immediately on their determined multiplexer entries and require no special framing.
+
+![Sequence diagram of MOS call flow between Terminal A and Terminal B. Terminal A sends a 'mos request' to Terminal B. Terminal B responds with a 'MOS requestAck'. Terminal A then sends another 'mos request' to Terminal B, which responds with another 'MOS requestAck'. The messages are shown crossing over a 'Media' block at the bottom. The diagram is labeled H.324(09)_FK.7.](2dd10dd89365981b6b6154de6390a602_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Terminal A with MOS support
+    participant Terminal B with MOS support
+    Note right of Terminal B: H.324(09)_FK.7
+    Terminal A->>Terminal B: mos request
+    Terminal B-->>Terminal A: MOS requestAck
+    Terminal B->>Terminal A: mos request
+    Terminal A-->>Terminal B: MOS requestAck
+    Note over Media: Media
+  
+```
+
+Sequence diagram of MOS call flow between Terminal A and Terminal B. Terminal A sends a 'mos request' to Terminal B. Terminal B responds with a 'MOS requestAck'. Terminal A then sends another 'mos request' to Terminal B, which responds with another 'MOS requestAck'. The messages are shown crossing over a 'Media' block at the bottom. The diagram is labeled H.324(09)\_FK.7.
+
+**Figure K.7 – MOS call flow**
+
+NOTE 2 – A device that has delayed transmission of its MOS request could send extra media decoder refresh points in the early part of its media session to help ensure early session quality in case its first MOS request is delayed in processing or corrupted.
+
+For the master slave determination, when the **terminalType** (Table K.7) fields differ, the terminal which has higher **terminalType** value shall be the master. When the **terminalType** fields in the MOS request of the two terminals are identical, and the two terminals have different values of **caller** (Table K.11) field, the caller shall be the master; if the **caller** fields are identical, the **terminalType** and **statusDeterminationNumber** (Table K.12) fields in the MOS request of the two terminals are used according to the master slave determination procedure in clause C.2 of [ITU-T H.245] and in an inferred manner without additional ITU-T H.245 signalling.
+
+NOTE 3 – The master slave relationship determined through MOS/SPC is used for at least the MOS/SPC procedures but would be overridden by a later ITU-T H.245 MasterSlaveDetermination (MSD) procedure.
+
+Unexpected MOS-SDUs shall be discarded.
+
+#### K.8.1.2 Logical channels
+
+A terminal indicates its requested logical channels by listing ITU-T H.245 **OpenLogicalChannel** (OLC) requests according to an order of preference in **mediaProfile** (Table K.8). The requests shall be processed in the same order.
+
+Logical channel numbers (LCNs) are assigned by the message originator. OLC requests with the same LCN indicate alternative media capabilities for the logical channel. For bidirectional logical channels, the reverse LCN shall be the same as the forward LCN. If a reverse LCN is already assigned, the next available LCN shall be assigned. The highest LCN shall be 13, and any OLC requests that lead to LCN exceeding 13 shall be ignored.
+
+If ICM contains an ITU-T H.223 adaptation layer type not supported by a terminal, the terminal shall fallback as described in clause K.8.2.
+
+#### K.8.1.3 Multiplex table entries
+
+The logical channel number shall be mapped to ITU-T H.223 multiplex entry index. For example, if logical channel 1 is opened, multiplex entry index 1 will be associated to this logical channel as "{LCN1, RC UCF}". For a reverse logical channel, the logical channel number shall be mapped to multiplex entry index at the ITU-T H.223 demultiplexer.
+
+Explicit multiplex table entries may be set using **additionalInfo** (Table K.10) parameter.
+
+Alternate multiplex entries may be signalled similarly as assigning LCNs for alternative media capabilities in clause K.8.1.2.
+
+NOTE 1 – Outgoing LCNs specified in explicit multiplex table entries for transmission are not expected to be changed.
+
+NOTE 2 – For example or alternative logical channels of {AMR, G.723.1} with LCN 3 and {H.263, H.261} with LCN 2, additional multiplex entries may be set as follows:
+
+- Index 5: (empty); Index 5: {LC 3, RC 22}, {LC 2, RC UCF}
+- Index 7: {LC 3, RC 32}, {LC 2, RC UCF}; Index 7: {LC 3, RC 25}, {LC 2, RC UCF}
+- Index 8: {LC 3, RC 7}, {LC 2, RC UCF}
+
+This represents, when AMR is selected, multiplex entries are: Index 7: {LC 3, RC 32}, {LC 2, RC UCF}; Index 8: {LC 3, RC 7}, {LC 2, RC UCF}; when ITU-T G.723.1 is selected, multiplex entries are: Index 5: {LC 3, RC 22}, {LC 2, RC UCF}; Index 7: {LC 3, RC 25}, {LC 2, RC UCF}.
+
+### K.8.2 Fallback procedure
+
+A fallback procedure shall be used by a MOS terminal to switch to the next phase of normal operation mode as described in clause K.7.
+
+MONA fallback is specified in clause K.7.2, the following additional conditions shall also initiate a fallback from MOS:
+
+- A normal ITU-T H.245 **TerminalCapabilitySet** message with empty **genericControlCapability** containing MOS OID after completion of the MOS procedure.
+- A terminal does not detect a valid MOS request, or does not accept the ICM, within a multiple of the network round trip delay (RTD) period. Typically, three RTDs are adopted.
+
+An exception to the timeout-initiated fallback as above is that timeout fallback shall not occur if the SPC-DC capability was set in transmitted PMs and the SPC-DA indication was set in received PMs (as in this situation, the remote terminal may delay its SPC MOS request). In this case, the device shall not fallback from MOS before a MOS request is received.
+
+### K.8.3 MOS messages
+
+Table K.6 defines the capability identifier for the **mos** capability and Tables K.7 to K.12 define the associated parameters. Tables K.13 and K.14 define the MOS Ack capability identifier and parameter, respectively.
+
+**Table K.6 – MOS capability identifier**
+
+|                             |                                                                                |
+|-----------------------------|--------------------------------------------------------------------------------|
+| Capability name             | mos                                                                            |
+| Capability class            | Control capability                                                             |
+| Capability identifier type  | Standard                                                                       |
+| Capability identifier value | { itu-t(0) recommendation(0) h(8) 324 generic-capabilities(1) mona(2) mos(1) } |
+
+**Table K.7 – MOS parameter – terminalType**
+
+|                            |                                        |
+|----------------------------|----------------------------------------|
+| Parameter name             | terminalType                           |
+| Parameter description      | Terminal type as defined in clause 7.4 |
+| Parameter identifier value | 2                                      |
+| Parameter status           | Mandatory                              |
+| Parameter type             | unsignedMax                            |
+| Supersedes                 | –                                      |
+
+**Table K.8 – MOS parameter – mediaProfile**
+
+|                            |                                                                                                                |
+|----------------------------|----------------------------------------------------------------------------------------------------------------|
+| Parameter name             | mediaProfile                                                                                                   |
+| Parameter description      | One or more ITU-T H.245 <b>OpenLogicalChannel</b> structures specifying media channels in order of preference. |
+| Parameter identifier value | 4                                                                                                              |
+| Parameter status           | Optional                                                                                                       |
+| Parameter type             | octetString                                                                                                    |
+| Supersedes                 | –                                                                                                              |
+
+**Table K.9 – MOS parameter – mediaSymmetric**
+
+|                            |                                                                                                                                                                    |
+|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Parameter name             | mediaSymmetric                                                                                                                                                     |
+| Parameter description      | When set, all media capabilities are symmetric as per [ITU-T H.245]. When this parameter is absent, all media capabilities are non-symmetric as per [ITU-T H.245]. |
+| Parameter identifier value | 5                                                                                                                                                                  |
+| Parameter status           | Optional                                                                                                                                                           |
+| Parameter type             | logical                                                                                                                                                            |
+| Supersedes                 | –                                                                                                                                                                  |
+
+**Table K.10 – MOS parameter – additionalInfo**
+
+|                            |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Parameter name             | additionalInfo                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| Parameter description      | <p>One or more ITU-T H.245 <b>MultimediaSystemControlMessage</b> such as <b>UserInputIndication</b>, <b>MultiplexEntrySend</b> and <b>TerminalCapabilitySet</b>. <b>OpenLogicalChannel</b> should not be included. No ITU-T H.245 response shall be generated for request messages interpreted as commands. Only messages with settings within the mandatory limit of the Recommendation shall be sent as receivers, receivers shall ignore messages outside these limits. Response messages are meaningless. Values specified in this parameter take precedence to inferred values. An exception is to <b>MultiplexEntrySend</b> such that inferred multiplex entry index takes precedence.</p> <p>If a <b>TerminalCapabilitySet</b> is supplied, <b>OPTIONAL</b> fields such as <b>multiplexCapability</b>, <b>capabilityTable</b> and <b>capabilityDescriptors</b> are optional. Capabilities already inferred from <b>mediaProfile</b> parameter should not be included. Additional capabilities such as <b>receiveUserInputCapability</b> may be appended to <b>capabilityTable</b>.</p> |
+| Parameter identifier value | 6                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| Parameter status           | Optional                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| Parameter type             | octetString                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| Supersedes                 | –                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+**Table K.11 – MOS parameter – caller**
+
+|                            |                                                                                         |
+|----------------------------|-----------------------------------------------------------------------------------------|
+| Parameter name             | caller                                                                                  |
+| Parameter description      | Indication that the terminal is a caller. When not specified, the terminal is a callee. |
+| Parameter identifier value | 7                                                                                       |
+| Parameter status           | Mandatory                                                                               |
+| Parameter type             | logical                                                                                 |
+| Supersedes                 | –                                                                                       |
+
+**Table K.12 – MOS parameter – statusDeterminationNumber**
+
+|                            |                                                              |
+|----------------------------|--------------------------------------------------------------|
+| Parameter name             | statusDeterminationNumber                                    |
+| Parameter description      | A random number as defined in clause B.1.1 of [ITU-T H.245]. |
+| Parameter identifier value | 8                                                            |
+| Parameter status           | Mandatory                                                    |
+| Parameter type             | unsigned32Max                                                |
+| Supersedes                 | –                                                            |
+
+**Table K.13 – MOS Ack capability identifier**
+
+|                             |                                                                                   |
+|-----------------------------|-----------------------------------------------------------------------------------|
+| Capability name             | mos Ack                                                                           |
+| Capability class            | Control capability                                                                |
+| Capability identifier type  | Standard                                                                          |
+| Capability identifier value | { itu-t(0) recommendation(0) h(8) 324 generic-capabilities(1) mona(2) mosack(2) } |
+
+**Table K.14 – MOS Ack parameter – requestAck**
+
+|                            |                                                                                                   |
+|----------------------------|---------------------------------------------------------------------------------------------------|
+| Parameter name             | requestAck                                                                                        |
+| Parameter description      | Acknowledge receipt of MOS message. One Ack message shall be sent for every MOS message received. |
+| Parameter identifier value | 10                                                                                                |
+| Parameter status           | Mandatory                                                                                         |
+| Parameter type             | logical                                                                                           |
+| Supersedes                 | –                                                                                                 |
+
+## K.9 Preconfigured channel establishment
+
+This clause specifies a procedure by which media channels may be established before capabilities and intents are exchanged. Specifically, a MONA terminal is allowed to send media before receiving any capability or other information from the opposite terminal. This allows for fastest possible set-up of channels, but limits the set-up options to a small set of fixed channel configurations.
+
+### K.9.1 General
+
+When the procedures of the current clause are in use, several of the ITU-T H.223 multiplex table entries are defined to reference default configurations for the multiplex table, codec configuration and other related parameters. Such default operation points may be used to quickly establish
+
+channels for data flow, called preconfigured channels. Preconfigured channels may be used to carry media data, or they may be used to exchange signalling data in order to negotiate regular logical channels. Once a preconfigured channel is established, it may be used for the duration of the session. media preconfigured channels may be replaced through ITU-T H.245-based negotiation of a regular logical channel of the same media type. If the procedures of clause K.7.1 determine that SPC-based negotiation will not be used to establish channels in the current session, then any current transmission of SPC data shall be dropped.
+
+NOTE – MPC does not include a mechanism to signal symmetric codec requirements. If a terminal has such requirements, it could use MPC limited to a single codec of a given media type for both transmit and receive. Alternately, it could use the SPC or ACP negotiation methods which do support symmetric codec negotiation.
+
+### K.9.2 Channel configurations
+
+The following combinations shown in Table K.15 of codec, LCN and multiplex table configuration shall be used within the MPC establishment procedure in order to establish preconfigured channels.
+
+**Table K.15 – Channel configurations**
+
+| Codec                                  | MUX code | LCN | Multiplex table entry |
+|----------------------------------------|----------|-----|-----------------------|
+| Reserved (ITU-T H.245)                 | 0        | –   | –                     |
+| ETSI TS 126 071 (AMR)                  | 1        | 1   | {1 ucf}               |
+| ETSI TS 126 171 (AMR-WB)               | 2        | 2   | {2 ucf}               |
+| ITU-T H.264                            | 3        | 3   | {3 ucf}               |
+| ISO/IEC 14496-2 (MPEG-4 part 2)        | 4        | 4   | {4 ucf}               |
+| ITU-T H.263                            | 5        | 5   | {5 ucf}               |
+| Reserved                               | 6..11    |     |                       |
+| Unspecified, left for operator use     | 12..13   |     |                       |
+| Signalling preconfigured channel (SPC) | 14       | 14  | {14 ucf}              |
+| Reserved (WNSRP)                       | 15       | –   | –                     |
+
+Each of the media codec options is associated with fixed configuration information. The configuration information consists of the whole state pertaining to a logical channel, as if that channel would have been opened using the normal open logical channel procedure of [ITU-T H.245].
+
+#### K.9.2.1 AMR speech (mux code 1)
+
+##### **Codec configuration:**
+
+maxBitRate = 12.2 kbit/s
+
+maxAl-sdu-Frames = 1
+
+##### **ITU-T H.223 configuration:**
+
+AL2 with sequence numbers
+
+maxAl-sdu-Frames = 1
+
+#### K.9.2.2 AMR-WB speech (mux code 2)
+
+##### **Codec configuration:**
+
+maxbitRate = 23.85 kbit/s
+
+maxAl-sduFrames = 1
+
+octetAlign = TRUE  
+modeSet = all modes available  
+modeChangePeriod = anytime  
+modeChangeNeighbour = FALSE  
+crc = FALSE
+
+##### **ITU-T H.223 configuration:**
+
+AL2 with sequence numbers  
+(non-segmentable)
+
+#### **K.9.2.3 ITU-T H.264 visual (mux code 3)**
+
+##### **Codec configuration:**
+
+Sequence and picture parameter sets shall be inferred to be set as if the following, base64 encoded bitstream were received at the decoder:
+
+Base64: AAAAASdCoAqVoLE6AeEQjUAAAABKM4Gag==
+
+Hex: 00 00 00 01 27 42 a0 0a 95 a0 b1 3a 01 e1 10 8d 40 00 00 00 01 28 ce 06 6a
+
+##### **ITU-T H.223 configuration:**
+
+AL2 with sequence numbers  
+(segmentable)
+
+NOTE – The above base64 coded bitstream corresponds to a single sequence parameter set with ID 0, and a single picture parameter set with ID 0. The properties are set to a widely accepted operation point of ITU-T H.264, which can be summarized as baseline profile, level 1.0, QCIF picture format, 8-bit frame\_num, one reference picture and constrained intra prediction on.
+
+#### **K.9.2.4 MPEG-4 visual (mux code 4)**
+
+##### **Codec configuration:**
+
+QCIF only
+
+maxBitRate = 64 kbit/s
+
+profileAndLevel = 8
+
+object = 1
+
+decoderConfigurationInformation:
+
+Base64: AAABsAgAAAG1CQAAAQAAAAEgAIRdTCgsIJCijw==
+
+Hex: 00 00 01 b0 08 00 00 01 b5 09 00 00 01 00 00 00 01 20 00 84 5d 4c 28 2c 20 90 a2 8f
+
+##### **ITU-T H.223 configuration:**
+
+AL2 with sequence numbers  
+(segmentable)
+
+#### **K.9.2.5 ITU-T H.263 (mux code 5)**
+
+##### **Codec configuration:**
+
+QCIF only, with qcifMPI = 2
+
+maxBitRate = 64 kbit/s
+
+unrestrictedVector = FALSE  
+arithmeticCoding = FALSE  
+advancedPrediction = FALSE  
+pbFrames = FALSE
+
+##### **ITU-T H.223 configuration:**
+
+AL2 with sequence numbers  
+(segmentable)
+
+NOTE 1 – The ITU-T H.263 codec configuration is consistent with profile 0, level 10 defined in Annex X of [ITU-T H.263].
+
+NOTE 2 – A MONA terminal which opens an ITU-T H.263 channel using MPC procedures may or may not be capable of adjusting the videoTemporalSpatialTradeOff value used by its encoder. If a MONA terminal has this capability and wishes to allow adjustment of the value, it is required by clause B.14.2 of [ITU-T H.245] to send ITU-T H.245 MiscellaneousIndication messages including videoTemporalSpatialTradeOff values to the remote terminal. The remote terminal could use the presence or absence of such indications to infer whether the capability is supported.
+
+NOTE 3 – Other H263VideoCapability parameters not listed here are considered to be 'off' or not present.
+
+### **K.9.3 Sending procedure – Media preconfigured channels**
+
+MONA terminals may use preconfigured channels to establish the initial outgoing audio and visual connections to the remote terminal. The timing for the initiation of outgoing media preconfigured channel transmissions is restricted by the following rules (see also clause K.7.1):
+
+- Media preconfigured channel transmission may not start until the initial outgoing preference message repetition requirement has been met.
+- Media preconfigured channel transmission may not begin after the decision has been made to negotiate media channels using the procedures of clause K.8 (SPC).
+- Preconfigured channel transmission for a particular media type shall not begin after an outgoing channel of the same media type has been already established (whether via a different media preconfigured channel or by any other means). Equivalently, a preconfigured channel may only be used for the initial establishment of a channel for a given media type.
+- Transmission shall be limited to a single preconfigured channel per media type at any given time.
+
+Media preconfigured channels shall be formatted according to the following rules:
+
+- Until the receipt of at least one incoming preference message, outgoing preconfigured channel media PDUs shall be encapsulated within MONA preference messages.
+  - The framing for preference messages is defined in clause K.6.1.
+  - The payload for preference messages consists of the preference message capability payload defined in clause K.6.2, immediately followed by:
+    - One octet where the MUX code is carried in the least significant four bits. The MUX code is taken from the appropriate media preconfigured channel configuration defined in clause K.9.2.
+    - Media data in the form of a complete AL-PDU, including additional fields added at the adaptation layer.
+  - If the payload formed as above is larger than 150 octets, the payload will be subject to the usual segmentation and reassembly procedure for MONA framing (see clause K.6.1).
+
+NOTE 1 – As a consequence of the segmentation, the AL-PDU boundaries will be naturally marked by the last segment (LS) bit of the MONA frame information (FI) field.
+
+NOTE 2 – The PSR and FEA procedures normally used for preference messages are applied as well to preference messages which encapsulate media payloads.
+
+NOTE 3 – In order to meet audio jitter requirements, a MONA terminal may find it necessary to insert MONA-encapsulated audio frames between fragmented segments of MONA-encapsulated video or SPC signalling data. In this case, the receiver may use the fact that MPC audio configurations are nonsegmentable in order to correctly parse and recover the audio data. MONA-encapsulated data types which are segmentable (e.g., video and SPC signalling data) cannot be interleaved with one another, as the receiver may not be able to determine the payload types for the interleaved fragments.
+
+- After the receipt of at least one incoming preference message, outgoing preconfigured channel media PDUs are sent as standard ITU-T H.223 MUX PDUs, using the appropriate MUX code and configuration described in clause K.9.2. The MUX Level is agreed via the MONA-ML negotiation defined in Table K.5.
+
+NOTE 4 – Upon receiving a remote terminal's preference message and recognizing that one or more codecs (for a given media type) may be transmitted to establish a channel, the selection of which codec to employ is a local matter and no preference rules exist for making the determination.
+
+The initial MPC transmission results in the successful establishment of preconfigured channels only if the remote terminal supports receipt of the specific configurations transmitted. The remote terminal signals this in its outgoing MPC-RX field. The sending terminal discovers whether the initial outgoing preconfigured channels were established upon receipt of the first incoming preference message from the remote terminal. Upon learning the remote terminal's capabilities, the sending terminal shall drop all current unsuccessful transmissions. Each unsuccessful transmission may be replaced via a new preconfigured channel transmission that the remote terminal is known to support. This procedure is known as "MPC-Fallback". Alternately, the accelerated ITU-T H.245 procedures described in clause K.10 may be used to establish a successful channel. More details on the selection of negotiation procedures are given in clause K.7.
+
+Once established, a media preconfigured channel shall be treated as though it were negotiated using ITU-T H.245 logical channel procedures. ITU-T H.245 messages which reference the channel shall do so using the appropriate LCN defined in clause K.9.2.
+
+Any terminal which begins MPC transmission before the receipt of the first incoming preference message may need to switch its outgoing codec, since such a switch may be necessary in the event that the initial transmission does not lead to successful channel establishment.
+
+For media codecs that employ cross-AL SDU prediction (e.g., video codecs employing inter-picture prediction), it is recommended to send decoder refresh points (e.g., intra frames) frequently during the session set-up.
+
+Terminals implementing the procedures of this clause should be capable of responding to the ITU-T H.245 videoFastUpdatePicture command.
+
+### **K.9.4 Sending procedure – Signalling preconfigured channel**
+
+MOS messages as defined in clause K.8.3 are transmitted over the signalling preconfigured channel. MOS messages shall be ITU-T H.245 genericRequest messages (using GenericMessage) and shall be encoded as ITU-T H.245 MultimediaSystemControlMessage according to packed encoding rules (PER) as defined in [ITU-T X.691]. PDUs carrying MOS messaging within the signalling preconfigured channel shall be encapsulated using the MONA preference message frame structure as defined in clause K.6.1, and following PSR procedure and FEA according to clause K.8.2.
+
+Signalling preconfigured channels shall be formatted according to the following rules:
+
+- The framing for preference messages is defined in clause K.6.1.
+- The payload for preference messages consists of the preference message capability payload defined in clause K.6.2, immediately followed by:
+  - One octet where the MUX code is carried in the least significant four bits. The MUX code is the signalling preconfigured channel configuration defined in clause K.9.2.
+  - Encoded MOS message for the PDU.
+
+NOTE 1 – The PSR and FEA procedures normally used for preference messages are applied as well to preference messages which encapsulate signalling payloads.
+
+NOTE 2 – The signalling encapsulation does not change on the receipt of any incoming preference message.
+
+NOTE 3 – MOS messages are not used after completion of MOS signalling and are always formatted as specified in this clause. No further specification of adaptation layer is made.
+
+### K.9.5 Receiving procedure
+
+Terminals which support media preconfigured channel establishment shall search for incoming preconfigured channel PDUs for which receive capability was indicated in the MPC-RX field of the outgoing preference messages. When acceptable incoming preconfigured channels are detected, the terminal shall begin to decode the received audio and/or video data. Incoming preconfigured channel data for unknown or unsupported codec configurations shall be ignored by the receiver.
+
+A terminal which is capable of media preconfigured channel data shall be prepared to accept new incoming audio and/or video preconfigured channels at any time until one of the following conditions are met:
+
+- The terminal determines (per the decision algorithm in clause K.7.1) that the remote terminal will not use the procedures of this clause to establish a preconfigured channel of the given media type.
+- An incoming channel of the given media type is successfully established, whether via a media preconfigured channel or by any other means.
+
+## K.10 Accelerated ITU-T H.245 procedures
+
+### K.10.1 Accelerated ITU-T H.245 signalling
+
+Terminals shall signal MONA parameters by specifying the **mona** capability identifier, OID { itu-t(0) recommendation(0) h(8) 324 generic-capabilities(1) mona(2) }, in the **genericInformation.messageIdentifier** field of the **TerminalCapabilitySet** message. This message may be sent after at least one incoming MONA preference message has been received. The MUX level is agreed via the MONA-ML negotiation defined in Table K.5.
+
+Master/slave status shall be determined once the terminal has received the **MasterSlaveDetermination** message or the **MasterSlaveDeterminationAck** message from the remote terminal. When such status is determined, the terminal shall select the most preferred channels and shall send the corresponding **OpenLogicalChannel** messages. The terminal should start sending media without waiting to receive acknowledgement messages for its outgoing **TerminalCapabilitySet**, **MasterSlaveDetermination** or **OpenLogicalChannel** messages. Accelerated ITU-T H.245 procedures are shown in Figure K.8.
+
+### K.10.2 The MONA capability definition
+
+Table K.16 defines the capability identifier for the **mona** capability. Tables K.17, K.18 and K.19 define the associated parameters.
+
+**Table K.16 – MONA capability identifier**
+
+|                             |                                                                         |
+|-----------------------------|-------------------------------------------------------------------------|
+| Capability name             | mona                                                                    |
+| Capability class            | Control capability                                                      |
+| Capability identifier type  | Standard                                                                |
+| Capability identifier value | { itu-t(0) recommendation(0) h(8) 324 generic-capabilities(1) mona(2) } |
+
+**Table K.17 – MONA parameter – mediaBuffering**
+
+|                            |                                                                                                                                                                                                                                                                                                                                                                                           |
+|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Parameter name             | mediaBuffering                                                                                                                                                                                                                                                                                                                                                                            |
+| Parameter description      | A terminal indicating this parameter's value as 1 is able to buffer incoming media which arrives before the relevant OLC message is received from the remote terminal, allowing faster call set-up. In this case, the receiving terminal is responsible for managing the buffer and limiting the delay introduced by the buffering. The size of the buffer is left to the implementation. |
+| Parameter identifier value | 3                                                                                                                                                                                                                                                                                                                                                                                         |
+| Parameter status           | Shall be present once for capability exchange                                                                                                                                                                                                                                                                                                                                             |
+| Parameter type             | unsignedMin, with the value 0 or 1                                                                                                                                                                                                                                                                                                                                                        |
+| Supersedes                 | –                                                                                                                                                                                                                                                                                                                                                                                         |
+
+**Table K.18 – MONA parameter – audioEntry**
+
+|                            |                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Parameter name             | audioEntry                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| Parameter description      | This parameter indicates which multiplex entry shall be reserved in the call for an audio channel established using the accelerated ITU-T H.245 procedures. <ul style="list-style-type: none"> <li>• The value shall differ from that of videoEntry.</li> <li>• The value shall differ from the multiplex codes corresponding to outgoing media preconfigured channels (MPCs) which are currently established or which are candidates for later establishment.</li> </ul> |
+| Parameter identifier value | 4                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| Parameter status           | May be present only once for capability exchange                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| Parameter type             | unsignedMin, with the value 1 to 15                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| Supersedes                 | –                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+**Table K.19 – MONA parameter – videoEntry**
+
+|                            |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Parameter name             | videoEntry                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| Parameter description      | <p>This parameter indicates which multiplex entry shall be reserved in the call for a video channel established using the accelerated ITU-T H.245 procedures.</p> <ul style="list-style-type: none"> <li>• The value shall differ from that of audioEntry.</li> <li>• The value shall differ from the multiplex codes corresponding to outgoing media preconfigured channels (MPCs) which are currently established or which are candidates for later establishment.</li> </ul> |
+| Parameter identifier value | 5                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| Parameter status           | May be present only once for capability exchange                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| Parameter type             | unsignedMin, with the value 1 to 15                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| Supersedes                 | –                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+### K.10.3 Opening accelerated channels
+
+The procedures of this clause may be used to establish outgoing channels once the remote terminal's **TerminalCapabilitySet** is known. The procedures below are only required for opening channels when no existing channels of the same media types have previously been established successfully, as described in clause K.7.
+
+Channels opened using these procedures shall always be unidirectional channels.
+
+The terminal may start sending media on an accelerated video channel and on an accelerated audio channel simultaneously with sending the **OpenLogicalChannel** messages. The entry used for the transmission of the media shall be the one specified by the **videoEntry** or **audioEntry** parameter in the **mona** capability found in the outgoing **TerminalCapabilitySet**. The receiver terminal shall infer the media type of the incoming media from the received **OpenLogicalChannel** messages. The receiver terminal shall ignore or buffer incoming media MUX-SDUs on the accelerated video and on the accelerated audio channel until the corresponding **OpenLogicalChannel** message is received.
+
+If no outgoing video or audio channels are currently opened, and the relevant entry in the multiplexing table is not defined or is defined for a closed logical channel, then a terminal may send an **OpenLogicalChannel** message and simultaneously start sending the corresponding media.
+
+The multiplex table may be later reconfigured by sending a **MultiplexEntrySend** message for channels opened using these procedures.
+
+For media codecs that employ cross-AL-SDU prediction (e.g., video codecs employing interpicture prediction), it is recommended to send decoder refresh points (e.g., intraframes) frequently during the session set-up.
+
+![Sequence diagram for accelerated ITU-T H.245 procedures for both audio and video channels. The diagram shows a Master and a Slave exchanging messages. The Master sends TCS+MSD to the Slave. The Slave responds with TCS Ack+MSD Ack+. The Master then sends OLC (audio)+OLC (video) to the Slave. The Slave responds with OLC Ack (audio)+OLC Ack (video). The Master then sends MES to the Slave. The Slave responds with MES Ack. The Master then sends OLC Ack (audio)+OLC Ack (video) to the Slave. The Slave responds with Playback buffered media. The Master then sends Playback buffered media to the Slave. The Slave responds with Prepare to ignore or buffer media. The Master then sends Start sending media on audio and video channels to the Slave. The Slave responds with Start sending media on audio and video channels. The Master then sends Playback buffered media to the Slave. The Slave responds with Playback buffered media. The diagram is labeled H.324(09)_FK.8.](b8d855a06aad434aeafa2739bf62e7de_img.jpg)
+
+Sequence diagram for accelerated ITU-T H.245 procedures for both audio and video channels. The diagram shows a Master and a Slave exchanging messages. The Master sends TCS+MSD to the Slave. The Slave responds with TCS Ack+MSD Ack+. The Master then sends OLC (audio)+OLC (video) to the Slave. The Slave responds with OLC Ack (audio)+OLC Ack (video). The Master then sends MES to the Slave. The Slave responds with MES Ack. The Master then sends OLC Ack (audio)+OLC Ack (video) to the Slave. The Slave responds with Playback buffered media. The Master then sends Playback buffered media to the Slave. The Slave responds with Prepare to ignore or buffer media. The Master then sends Start sending media on audio and video channels to the Slave. The Slave responds with Start sending media on audio and video channels. The Master then sends Playback buffered media to the Slave. The Slave responds with Playback buffered media. The diagram is labeled H.324(09)\_FK.8.
+
+Figure K.8 – Accelerated ITU-T H.245 procedures for both audio and video channels
+
+### K.10.4 Handling OpenLogicalChannelReject
+
+The terminal receiving an **OpenLogicalChannel** using the accelerated ITU-T H.245 procedures may reject the proposed channel and ignore any media received for this channel. In this case, the terminal shall not buffer any incoming media for this media type until a new **OpenLogicalChannel** is received for it. Channel rejection procedures are shown in Figure K.9.
+
+The terminal which has received the **OpenLogicalChannelReject** message should reopen a channel with a different media type using the regular **OpenLogicalChannel** procedure.
+
+![Sequence diagram for channel rejection during accelerated ITU-T H.245 procedures. The diagram shows a Master and a Slave exchanging messages. The Master sends TCS+MSD to the Slave. The Slave responds with TCS Ack+MSD Ack+. The Master then sends OLC (audio)+OLC (video) to the Slave. The Slave responds with OLC Ack (audio)+OLC Reject (video). The Master then sends OLC (video) to the Slave. The Slave responds with MES. The Master then sends MES Ack to the Slave. The Slave then sends OLC Ack (video) to the Master. The Master then sends MES to the Slave. The Slave responds with MES Ack. The Master then sends Playback buffered media to the Slave. The Slave responds with Prepare to ignore or buffer media. The Master then sends Start sending media on audio and video channels to the Slave. The Slave responds with Start sending media on audio and video channels. The Master then sends Playback buffered media to the Slave. The Slave responds with Playback buffered media on the audio channel and clean up buffered media on the video channel. The Master then sends Playback buffered media to the Slave. The Slave responds with Playback buffered media on the video channel. The diagram is labeled H.324(09)_FK.9.](aed5b156b9b0fff9167baba88e5fdcfc_img.jpg)
+
+Sequence diagram for channel rejection during accelerated ITU-T H.245 procedures. The diagram shows a Master and a Slave exchanging messages. The Master sends TCS+MSD to the Slave. The Slave responds with TCS Ack+MSD Ack+. The Master then sends OLC (audio)+OLC (video) to the Slave. The Slave responds with OLC Ack (audio)+OLC Reject (video). The Master then sends OLC (video) to the Slave. The Slave responds with MES. The Master then sends MES Ack to the Slave. The Slave then sends OLC Ack (video) to the Master. The Master then sends MES to the Slave. The Slave responds with MES Ack. The Master then sends Playback buffered media to the Slave. The Slave responds with Prepare to ignore or buffer media. The Master then sends Start sending media on audio and video channels to the Slave. The Slave responds with Start sending media on audio and video channels. The Master then sends Playback buffered media to the Slave. The Slave responds with Playback buffered media on the audio channel and clean up buffered media on the video channel. The Master then sends Playback buffered media to the Slave. The Slave responds with Playback buffered media on the video channel. The diagram is labeled H.324(09)\_FK.9.
+
+Figure K.9 – Channel rejection during accelerated ITU-T H.245 procedures
+
+# Annex L
+
+## Text conversation in ITU-T H.324
+
+(This annex forms an integral part of this Recommendation)
+
+## L.1 Introduction
+
+Standardized, character-oriented text conversation facilities are needed in all networks. When building text conversation facilities on multimedia protocols, an opportunity is created to use any combination of text, video and voice in a conversation. The initiative to standardize this combination comes from the needs of persons with communication-related disabilities. The availability of the three media in a conversation offers communication opportunities over any one of the media alone. Anyone may find valuable a commonly available, standardized text conversation addition to multimedia conversation services, enhancing videotelephony to "total conversation" as defined in [ITU-T F.703].
+
+Since ITU-T H.324 is a framework where components can be included when required, single function text terminals as well as text and voice terminals can be useful subsets of the full total conversation terminal. These subsets correspond to text telephones available for the PSTN.
+
+[ITU-T T.140] specifies a text conversation protocol. It is a common presentation level suitable for straightforward real-time text conversation in multimedia services and in text telephony. It is based on the ISO/IEC 10646-1 character code so as to be suitable for any language. It is introduced throughout the ITU-T H-series multimedia protocols.
+
+This annex describes how text conversation facilities are added to the ITU-T H.324 multimedia environment.
+
+## L.2 Scope
+
+The scope of this annex is to specify ITU-T H.324 procedures to establish and carry text conversation sessions in the ITU-T H.324 multimedia environment.
+
+## L.3 Definitions
+
+This annex defines the following terms:
+
+**L.3.1 total conversation:** Conversational services offering real-time communication in video, text and voice [ITU-T F.703].
+
+**L.3.2 T140PDU:** protocol data unit from [ITU-T T.140], i.e., a collection of data submitted in ITU-T T.140 format for transmission.
+
+## L.4 Procedures for ITU-T T.140 text conversation
+
+### L.4.1 Capability signalling
+
+A terminal which is capable of text conversation according to [ITU-T T.140] shall signal this in its capability set by including `UserInputCapability.genericUserInputCapability`, using the capability identifier given in Table L.1 below.
+
+**Table L.1 – Capability identifier for ITU-T H.324 text conversation**
+
+|                             |                                                                                              |
+|-----------------------------|----------------------------------------------------------------------------------------------|
+| Capability name             | ITU-T H.324 text conversation capability identifier                                          |
+| Capability identifier type  | standard                                                                                     |
+| Capability identifier value | {itu-t(0) recommendation(0) h(8) 324 generic-capabilities(1) textConversationCapability(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.                                                            |
+
+### **L.4.2 ITU-T T.140 operation**
+
+The ITU-T T.140 output octets shall be included in one or more ITU-T H.245 UserInputIndication messages in the genericInformation structure. The GenericInformation message shall contain in the CapabilityIdentifier.standard structure the OID given for the ITU-T H.324 text conversation capability identifier in Table L.1, and an ITU-T T.140 message parameter according to Table L.2.
+
+**Table L.2 – ITU-T T.140 message parameter**
+
+|                            |                                                                                                                                                                          |
+|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Parameter name             | ITU-T T.140 message                                                                                                                                                      |
+| Parameter description      | The value of this parameter shall contain a sequence of two GenericParameter structures, terminal label (see Table L.3), followed by ITU-T T.140 octets (see Table L.4). |
+| Parameter identifier value | 1                                                                                                                                                                        |
+| Parameter status           | Optional                                                                                                                                                                 |
+| Parameter type             | genericParameter                                                                                                                                                         |
+| Supersedes                 | None                                                                                                                                                                     |
+
+The ITU-T T.140 message parameter given in Table L.2 shall be itself composed of a sequence of two GenericParameter structures, the terminal label parameter shown in Table L.3, followed by the ITU-T T.140 octets parameter shown in Table L.4.
+
+**Table L.3 – Terminal label parameter**
+
+|                            |                                                                                                                                                                                                                                                                                                                                            |
+|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Parameter name             | Terminal label                                                                                                                                                                                                                                                                                                                             |
+| Parameter description      | The value of this parameter shall contain an unsignedMin parameter representing the values of the ITU-T H.245 McuNumber and TerminalNumber structures which identify the terminal from which the ITU-T T.140 octets originated.<br>The value of the parameter shall be constructed as follows:<br>Value = McuNumber * 256 + TerminalNumber |
+| Parameter identifier value | 2                                                                                                                                                                                                                                                                                                                                          |
+| Parameter status           | Optional                                                                                                                                                                                                                                                                                                                                   |
+| Parameter type             | unsignedMin                                                                                                                                                                                                                                                                                                                                |
+| Supersedes                 | None                                                                                                                                                                                                                                                                                                                                       |
+
+The terminal label parameter serves to identify which terminal sent the ITU-T T.140 octets. This information may be useful, for example, to label the source of the ITU-T T.140 text.
+
+**Table L.4 – ITU-T T.140 octets parameter**
+
+|                            |                                                                                                                                       |
+|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------|
+| Parameter name             | ITU-T T.140 octets                                                                                                                    |
+| Parameter description      | The value of this parameter shall contain octets according to [ITU-T T.140].<br>This parameter shall not exceed 128 octets in length. |
+| Parameter identifier value | 3                                                                                                                                     |
+| Parameter status           | Optional                                                                                                                              |
+| Parameter type             | octetString                                                                                                                           |
+| Supersedes                 | None                                                                                                                                  |
+
+The destination node and originating node concepts of ITU-T T.140 are mapped to the two ITU-T H.324 endpoints.
+
+The ITU-T T.140 user identity is an alias for an ITU-T H.324 endpoint. When the source is an MCU, the terminal label should be used as the transmitting ITU-T T.140 user identity. Data from one source only shall be provided in one ITU-T T.140 message.
+
+ITU-T T.140 operations should use the WNSRP procedures (see clause A.4).
+
+## L.5 Framing and buffering of ITU-T T.140 data
+
+Transmission of ITU-T T.140 data shall be done according to the following specifications.
+
+### L.5.1 Common considerations
+
+ITU-T T.140 data at the source terminal should be collected in a buffer before transmission in the channel. On low bit-rate channels, such buffering is recommended in order to reduce overhead. Buffering of data in intervals of not more than 0.3 seconds is recommended.
+
+On reception, the data content of the data channel is retrieved and used as ITU-T T.140 data.
+
+## L.6 Presentation considerations
+
+### L.6.1 One-to-one sessions
+
+The one-to-one case represents a direct conversation in text between two parties, where the text entered at one endpoint is displayed shortly after at the other endpoint. Character by character display is desirable. Typical examples are situations like the traditional text telephony in PSTN and multimedia conversation applications with video, text and audio used for person-to-person calls as shown in Figure L.1.
+
+| Anne                                                                           | Eve                                                                                             |
+|--------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|
+| Hi, this is Anne.<br><br>Have you heard that I will come to Paris in November? | Oh, hello Anne, I am glad you are calling!<br><br>No, that was new to me. What brings you here? |
+
+**Figure L.1 – Possible display of a one-to-one text call**
+
+### L.6.2 Multipoint considerations
+
+Without further specification, two alternative options exist for ITU-T H.324 endpoints with ITU-T T.140 text conversation to participate in multipoint text conversations:
+
+- 1) An MCU coordinates the ITU-T T.140 data stream to the ITU-T H.324 endpoint to contain data from a number of remote endpoints.
+- 2) Instead of the procedures described in this annex, the T.134 application member of ITU-T T.120 data conferencing is used as the channel for ITU-T T.140 data. Multipoint sessions are coordinated through the ITU-T T.120 concepts.
+
+#### L.6.2.1 Informative examples for multipoint text conversation
+
+In order to clarify the use of text conversation, and especially the different multipoint cases, the following examples of possible set-ups and applications are given without being normative.
+
+In these cases, the value of the terminal label parameter (see Table L.3) is associated with information provided in the ITU-T H.245 TerminalID structure to label the source of messages and to coordinate the positioning of the text in the area belonging to the source. This coordination is maintained during build-up of entries and possible erasures, as shown in the examples below.
+
+##### L.6.2.1.1 Many-to-many
+
+All users have write permission, forming an unmanaged conference.
+
+The display can be arranged as specified in ITU-T T.140 with one window for each participant as shown in Figure L.2.
+
+| Anne                                                                    | Eve                                                      |
+|-------------------------------------------------------------------------|----------------------------------------------------------|
+| Hi, this is Anne. Have you heard that I will come to Paris in November? | Oh, hello guys! How are you Steve?                       |
+| Steve                                                                   | Bill                                                     |
+| Hi there! This is Steve, I'm fine.                                      | Hello Anne! I am happy that you are on the big Internet! |
+
+**Figure L.2 – Possible display of an unmanaged four-to-four text session**
+
+The display of a many-to-many conference can also be ordered in one window with labels for each participant's entries (Internet relay chat style). Entries that are not yet completed may be displayed in a separate real-time entry area and moved when completed to the history area by a new line or any other decided entry delimiter as shown in Figure L.3.
+
+|                                                                                                                                                                                              |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Steve> Hi there!<br>Anne> Have you heard that I will come to Paris in November?<br>Bill> Hello Anne! I am happy that you are on the big Internet!<br>Eve> Oh, hello guys! How are you Steve? |
+| Steve> I'm fi                                                                                                                                                                                |
+
+**Figure L.3 – Possible display of an unmanaged four-to-four text session IRC style with one entry in creation (Steve is typing an unfinished sentence)**
+
+##### **L.6.2.1.2 One-to-many with managed right to type**
+
+One writer at a time is given the right to transmit text to many readers. The right to type can be passed to other writers, in a managed meeting.
+
+A typical application is in distance education when the teacher normally has the right to type, but can hand it over to a participant.
+
+##### **L.6.2.1.3 One-to-many with fixed right to type**
+
+One writer types text in the session from one fixed endpoint, the other endpoints display the text in a receiving window. The right to type cannot be transferred.
+
+A typical application is found in subtitled speeches as shown in Figure L.4.
+
+|                                                                                |
+|--------------------------------------------------------------------------------|
+| We are proud to announce today a new superior system for intergalactic travel. |
+|--------------------------------------------------------------------------------|
+
+**Figure L.4 – Example of one-to-many text session**
+
+# Annex M
+
+## ITU-T H.245 messages used by ITU-T H.324 endpoints
+
+(This annex forms an integral part of this Recommendation)
+
+The following rules apply to the use of ITU-T H.245 messages by ITU-T H.324 endpoints:
+
+- An endpoint shall not malfunction or otherwise be adversely affected by receiving ITU-T H.245 messages that it does not recognize. An endpoint receiving an unrecognizable request, response or command shall return "function not supported" (this is not required for indications).
+- FunctionNotSupported and FunctionNotUnderstood are intended as responses to messages that are not understood (because they are non-standard or from a later version of the standard), see clause B.14.1 of [ITU-T H.245], rather than as responses to messages and/or procedures that have not been implemented.
+- The following abbreviations are used in Tables M.1 to M.10:  
+M Mandatory  
+O Optional  
+F Forbidden to transmit
+- A message marked as mandatory for the receiving endpoint indicates that the endpoint shall accept the message and take the appropriate action. A message marked as mandatory for the transmitting endpoint indicates that the endpoint shall generate the message under the appropriate circumstances.
+
+An implemented optional request message at a terminal's transmitting endpoint causes the corresponding response message at the terminal's receiving endpoint to be mandatory.
+
+**Table M.1 – Master slave determination messages**
+
+| Message                   | Receiving endpoint status | Transmitting endpoint status |
+|---------------------------|---------------------------|------------------------------|
+| Determination             | M                         | M                            |
+| Determination acknowledge | M                         | M                            |
+| Determination reject      | M                         | M                            |
+| Determination release     | M                         | M                            |
+
+**Table M.2 – Terminal capability messages**
+
+| Message                    | Receiving endpoint status | Transmitting endpoint status |
+|----------------------------|---------------------------|------------------------------|
+| Capability set             | M                         | M                            |
+| Capability set acknowledge | M                         | M                            |
+| Capability set reject      | M                         | M                            |
+| Capability set release     | M                         | M                            |
+
+**Table M.3 – Logical channel signalling messages**
+
+| <b>Message</b>                    | <b>Receiving endpoint status</b> | <b>Transmitting endpoint status</b> |
+|-----------------------------------|----------------------------------|-------------------------------------|
+| Open logical channel              | M                                | M                                   |
+| Open logical channel acknowledge  | M                                | M                                   |
+| Open logical channel reject       | M                                | M                                   |
+| Open logical channel confirm      | M                                | M                                   |
+| Close logical channel             | M                                | M                                   |
+| Close logical channel acknowledge | M                                | M                                   |
+| Request channel close             | M                                | O                                   |
+| Request channel close acknowledge | O                                | O                                   |
+| Request channel close reject      | O                                | M                                   |
+| Request channel close release     | O                                | M                                   |
+
+**Table M.4 – Multiplex table signalling messages**
+
+| <b>Message</b>                   | <b>Receiving endpoint status</b> | <b>Transmitting endpoint status</b> |
+|----------------------------------|----------------------------------|-------------------------------------|
+| Multiplex entry send             | M                                | M                                   |
+| Multiplex entry send acknowledge | M                                | M                                   |
+| Multiplex entry send reject      | M                                | M                                   |
+| Multiplex entry send release     | M                                | M                                   |
+
+**Table M.5 – Request multiplex table signalling messages**
+
+| <b>Message</b>                      | <b>Receiving endpoint status</b> | <b>Transmitting endpoint status</b> |
+|-------------------------------------|----------------------------------|-------------------------------------|
+| Request multiplex entry             | M                                | O                                   |
+| Request multiplex entry acknowledge | O                                | O                                   |
+| Request multiplex entry reject      | O                                | M                                   |
+| Request multiplex entry release     | O                                | M                                   |
+
+**Table M.6 – Request mode messages**
+
+| <b>Message</b>           | <b>Receiving endpoint status</b> | <b>Transmitting endpoint status</b> |
+|--------------------------|----------------------------------|-------------------------------------|
+| Request mode             | M                                | O                                   |
+| Request mode acknowledge | O                                | O                                   |
+| Request mode reject      | O                                | M                                   |
+| Request mode release     | O                                | M                                   |
+
+**Table M.7 – Round trip delay messages**
+
+| <b>Message</b>            | <b>Receiving endpoint status</b> | <b>Transmitting endpoint status</b> |
+|---------------------------|----------------------------------|-------------------------------------|
+| Round trip delay request  | M                                | O                                   |
+| Round trip delay response | O                                | M                                   |
+
+**Table M.8 – Maintenance loop messages**
+
+| <b>Message</b>               | <b>Receiving endpoint status</b> | <b>Transmitting endpoint status</b> |
+|------------------------------|----------------------------------|-------------------------------------|
+| Maintenance loop request     | M                                | O                                   |
+| Maintenance loop acknowledge | O                                | O                                   |
+| Maintenance loop reject      | O                                | M                                   |
+| Maintenance loop command off | O                                | O                                   |
+
+**Table M.9 – Commands**
+
+| <b>Message</b>                        | <b>Receiving endpoint status</b> | <b>Transmitting endpoint status</b> |
+|---------------------------------------|----------------------------------|-------------------------------------|
+| Send terminal capability set          | M                                | O                                   |
+| Encryption                            | O                                | O                                   |
+| Flow control                          | M                                | O                                   |
+| End session                           | M                                | M                                   |
+| <b>Miscellaneous commands</b>         |                                  |                                     |
+| Equalize delay                        | O                                | O                                   |
+| Zero delay                            | O                                | O                                   |
+| Multipoint mode command               | O                                | O                                   |
+| Cancel multipoint mode command        | O                                | O                                   |
+| Video freeze picture                  | O                                | O                                   |
+| Video fast update picture             | M                                | O                                   |
+| Video fast update GOB                 | M                                | O                                   |
+| Video fast update MB                  | M                                | O                                   |
+| Video temporal spatial trade off      | O                                | O                                   |
+| Video send sync every GOB             | O                                | O                                   |
+| Video send sync every GOB cancel      | O                                | O                                   |
+| Max ITU-T H.223 MUXPDU size           | O                                | O                                   |
+| ITU-T H.223 multiplex reconfiguration | O                                | O                                   |
+| Mobile multilink reconfiguration      | O                                | O                                   |
+
+**Table M.10 – Indications**
+
+| <b>Message</b>                              | <b>Receiving endpoint status</b> | <b>Transmitting endpoint status</b> |
+|---------------------------------------------|----------------------------------|-------------------------------------|
+| Function not understood                     | M                                | M                                   |
+| Function not supported                      | M                                | M                                   |
+| <b>Miscellaneous indication</b>             |                                  |                                     |
+| Logical channel active                      | O                                | O                                   |
+| Logical channel inactive                    | O                                | O                                   |
+| Video indicate ready to activate            | O                                | O                                   |
+| Video temporal spatial trade off            | O                                | O                                   |
+| Video not decoded MBs                       | O                                | O                                   |
+| Vendor indications                          | O                                | O                                   |
+| Jitter indication                           | O                                | O                                   |
+| ITU-T H.223 skew indication                 | M                                | O                                   |
+| H2250maximumskewindication                  | F                                | F                                   |
+| New ATM virtual channel indication          | F                                | F                                   |
+| User input                                  | M (for 0-9, * and #)             | M (for 0-9, * and #)                |
+| Flow control indication                     | O                                | O                                   |
+| Mobile multilink reconfiguration indication | O                                | O                                   |
+
+Non-standard commands, requests, etc., are allowed.
+
+# Appendix I
+
+## Bit and octet order
+
+(This appendix does not form an integral part of this Recommendation)
+
+This appendix is supplied as a summary of bit and octet order in this Recommendation, including [ITU-T H.223], [ITU-T H.261], [ITU-T H.263], [ITU-T H.245] and [ITU-T G.723.1]. In case of any discrepancy, the normative text of the various Recommendations shall take precedence over this appendix.
+
+[ITU-T H.261], [ITU-T H.263], [ITU-T G.723.1] and [ITU-T H.245] each produce a sequence of bits which are delivered as octets to the ITU-T H.223 multiplex. Within this sequence of bits there are fields of various lengths, in some cases aligned with octet boundaries. In the case of [ITU-T H.261], [ITU-T H.263], [ITU-T G.723.1] and [ITU-T H.245], these fields are ordered most significant bit (MSB) first. Figure ApI.1 illustrates this, with "M" indicating the MSB of each field and "L" indicating the least significant bit (LSB) of each field.
+
+![](aa39f51ba214496042ee3e2ce4ecee80_img.jpg)
+
+|                  |   |   |   |   |   |   |   |   |   |   |      |
+|------------------|---|---|---|---|---|---|---|---|---|---|------|
+| First            | M | L | M | L | M | L | M | L | M | L | Last |
+| H.324(09)_FApI.1 |   |   |   |   |   |   |   |   |   |   |      |
+
+**Figure ApI.1 – Output from [ITU-T H.261]/[ITU-T H.263]/[ITU-T G.723.1]/[ITU-T H.245]**
+
+Upon delivery to the ITU-T H.223 multiplex, this bit sequence is split into octets, each with a defined MSB/LSB position, as shown in Figure ApI.2.
+
+![](7be79849b00ccd5e7220d808251b1258_img.jpg)
+
+|                  |         |   |             |   |             |   |             |   |             |   |             |
+|------------------|---------|---|-------------|---|-------------|---|-------------|---|-------------|---|-------------|
+|                  | M       | L | M           | L | M           | L | M           | L | M           | L |             |
+| First            | M       | L | M           | L | M           | L | M           | L | M           | L | Last        |
+|                  | Octet n |   | Octet n + 1 |   | Octet n + 2 |   | Octet n + 3 |   | Octet n + 4 |   | Octet n + 5 |
+| H.324(09)_FApI.2 |         |   |             |   |             |   |             |   |             |   |             |
+
+**Figure ApI.2 – Output split into octets**
+
+The ITU-T H.223 multiplex then transmits each of these octets in the order LSB first (the reverse of the original order), applying the transparency procedure (inserting a '0' after each sequence of five '1's) as it does so.
+
+For example, a sequence of six octets, with hexadecimal values 0x92, 0xF1, 0x39, 0x35, 0x31, 0x30 would be transmitted as shown in Figure ApI.3.
+
+![](9527d5a8f0830aff6b77bf256be0bc9c_img.jpg)
+
+|                    |                                                                                   |   |             |   |             |   |             |   |             |   |             |
+|--------------------|-----------------------------------------------------------------------------------|---|-------------|---|-------------|---|-------------|---|-------------|---|-------------|
+|                    | M                                                                                 | L | M           | L | M           | L | M           | L | M           | L |             |
+|                    | Octet n                                                                           |   | Octet n + 1 |   | Octet n + 2 |   | Octet n + 3 |   | Octet n + 4 |   | Octet n + 5 |
+| First              | 1                                                                                 | 0 | 0           | 1 | 0           | 0 | 1           | 0 | 1           | 1 | Last        |
+|                    | 0x92                                                                              |   | 0xF1        |   | 0x39        |   | 0x35        |   | 0x31        |   | 0x30        |
+| is transmitted as: |                                                                                   |   |             |   |             |   |             |   |             |   |             |
+| First              | 0                                                                                 | 1 | 0           | 0 | 1           | 0 | 0           | 1 | 1           | 1 | Last        |
+|                    | 1 0 0 0 1 1 1 1 1 0 0 1 1 1 0 0 1 0 1 0 1 1 0 0 1 0 0 0 1 1 1 0 0 0 0 0 1 1 1 0 0 |   |             |   |             |   |             |   |             |   |             |
+|                    | ↑ 0 bit will be inserted here                                                     |   |             |   |             |   |             |   |             |   |             |
+| H.324(09)_FApI.3   |                                                                                   |   |             |   |             |   |             |   |             |   |             |
+
+**Figure ApI.3 – Example sequence**
+
+# Appendix II
+
+## ITU-T V.8 *bis* codepoints
+
+(This appendix does not form an integral part of this Recommendation)
+
+ITU-T V.8 *bis* capability exchange may be used during call set-up to help terminals quickly decide, in the most common cases, if operation in ITU-T H.324 mode is desired. ITU-T V.8 *bis* capabilities indicate only the most basic and commonly used modes, and are not a substitute for ITU-T H.245 procedures. If an ITU-T H.324 operation mode not signalled by ITU-T V.8 *bis* is desired, the terminal must complete call establishment and perform an ITU-T H.245 capabilities exchange to determine if the far-end terminal supports the desired mode.
+
+Within the ITU-T V.8 *bis* communications capabilities (CC) field for this Recommendation, the CC field is formatted into one or more subfields. Each subfield ends with the octet in which bit [n] is set to 1. Following the first subfield, the remaining subfields, if present, shall appear in the same order in which the bits indicating their presence are transmitted.
+
+NOTE 1 – Implementers should refer directly to [ITU-T V.8 *bis*] for the actual bit assignments.
+
+In the first subfield, the following bits are allocated:
+
+| <i>Name</i> | <i>Meaning</i>                                                                                                 |
+|-------------|----------------------------------------------------------------------------------------------------------------|
+| Video       | Shall be set only if bidirectional video is supported per clause 6.6.                                          |
+| Audio       | Shall be set only if bidirectional audio is supported per clause 6.7.                                          |
+| Encryption  | Shall be set only if encryption is supported per clause 9.2.                                                   |
+| Data        | Indicates that a data subfield is present. Shall be set only if one or more bits in the data subfield are set. |
+
+NOTE 2 – Possible future allocations include profiles (new subfield).
+
+In the Data subfield, the following bits are allocated:
+
+| <i>Name</i> | <i>Meaning</i>                                                                                                                       |
+|-------------|--------------------------------------------------------------------------------------------------------------------------------------|
+| T.120       | Shall be set only if ITU-T T.120 conferencing is supported per clause 6.8.2.1.                                                       |
+| T.84        | Shall be set only if ITU-T T.84 still image transfer is supported per clause 6.8.2.2.                                                |
+| T.434       | Shall be set only if ITU-T T.434 file transfer is supported per clause 6.8.2.3.                                                      |
+| V.42        | Shall be set only if ITU-T V.42 user data is supported per clauses 6.8.1.2 and 6.8.2.6.                                              |
+| V.14        | Shall be set only if ITU-T V.14 user data is supported per clauses 6.8.1.1 and 6.8.2.6.                                              |
+| PPP         | Shall be set only if IETF point-to-point protocol is supported via the network layer protocol identifier (NLPID) per clause 6.8.2.5. |
+| T.140       | Shall be set only if ITU-T T.140 text conversation protocol for multimedia application is supported per clause 6.8.2.8.              |
+
+NOTE 3 – Other modes beside those indicated in [ITU-T V.8 *bis*], such as unidirectional modes, may be supported by terminals as signalled via ITU-T H.245 capabilities exchange.
+
+
+
+
+
+# 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.351-200806-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.351-200806-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a
--- /dev/null
+++ b/marked/H/T-REC-H.351-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.351-200806-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg b/marked/H/T-REC-H.351-200806-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..625bbe6448315e9491ddbb2ff52471bc6fb3539f
--- /dev/null
+++ b/marked/H/T-REC-H.351-200806-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5df4a335b219857ca8f8acf91c1f534790ab8972c8eb604a2ef7c61ddec5932f
+size 60211
diff --git a/marked/H/T-REC-H.362-201009-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/H/T-REC-H.362-201009-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..211c7eacca7307af486c6a037acf4c5fdebdcf58
--- /dev/null
+++ b/marked/H/T-REC-H.362-201009-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:82ca146e4003452f508a0f400eefc1a5d987d318728030881a636bf453070f60
+size 74527
diff --git a/marked/H/T-REC-H.362-201009-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/H/T-REC-H.362-201009-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..188ddc126495f4b5d9e4ef0bb6c28dfcb895da28
--- /dev/null
+++ b/marked/H/T-REC-H.362-201009-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3d3e9d5201e17b783df41f21017f2e5a7c267259396d486a457142a50ad45629
+size 52043
diff --git a/marked/H/T-REC-H.362-201009-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/H/T-REC-H.362-201009-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a3f6027b0656096d0a88532755dcccf1a732d23a
--- /dev/null
+++ b/marked/H/T-REC-H.362-201009-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4db98c1f12abac12e7294e907fe5d621a4a397cf4e72ef177fcb289613bce5ca
+size 43302
diff --git a/marked/H/T-REC-H.362-201009-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/H/T-REC-H.362-201009-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..808e4821ddab756505d8d1fdff7625dcdc29f942
--- /dev/null
+++ b/marked/H/T-REC-H.362-201009-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:13b7017e594807ba3b3a886fb2cb8ade480b62696912caba84090885b016ac13
+size 32069
diff --git a/marked/H/T-REC-H.362-201009-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/H/T-REC-H.362-201009-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2de8251bd77ed71c30d1b6b222820cd2d9dae6cc
--- /dev/null
+++ b/marked/H/T-REC-H.362-201009-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:717844dbbf8233c4b2e820c460081d9ae81940fbbb0962ffdecd7f6a1ef70af6
+size 113354
diff --git a/marked/H/T-REC-H.362-201009-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg b/marked/H/T-REC-H.362-201009-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4ad82b9a7451cdac18b771076d0c13dd82405c34
--- /dev/null
+++ b/marked/H/T-REC-H.362-201009-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:52c73fc307dd399243d97f1a12a6ecd800f6fcc3b81d02c85373259a521138b2
+size 121966
diff --git a/marked/H/T-REC-H.362-201009-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/H/T-REC-H.362-201009-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6c1b1ad6016708ae83b81fac41b2711aed54e45a
--- /dev/null
+++ b/marked/H/T-REC-H.362-201009-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4fe4f14d955caddfc4360c74d3835c9fd8ed1c91957cd613fd15c970a6dbfbda
+size 38194
diff --git a/marked/H/T-REC-H.362-201009-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/H/T-REC-H.362-201009-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1fc133bca483f25707f37b7183e5126762e56366
--- /dev/null
+++ b/marked/H/T-REC-H.362-201009-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:61d348a8bc2890acab30182daa7f815c6fd131d5ffde9e082cd1dd20026e3086
+size 30695
diff --git a/marked/H/T-REC-H.362-201009-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.362-201009-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994
--- /dev/null
+++ b/marked/H/T-REC-H.362-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.362-201009-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/H/T-REC-H.362-201009-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0880dcbeebcc446d9e618c7a7c2973a8e89f3eed
--- /dev/null
+++ b/marked/H/T-REC-H.362-201009-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7fb8a84211e039448e84f84127d0240dda84c7562487938ea8cd43aca52ca27b
+size 54791
diff --git a/marked/H/T-REC-H.362-201009-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg b/marked/H/T-REC-H.362-201009-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4975351e3bb3a405c9d2f93ca5345d68978beb15
--- /dev/null
+++ b/marked/H/T-REC-H.362-201009-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d68acc975f6841b06ca5ecfeab38f6c80baddd7c01baa3512a9d4cfda2354dfb
+size 43028
diff --git a/marked/H/T-REC-H.362-201009-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg b/marked/H/T-REC-H.362-201009-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d1e88eea8860d0b15fc843bec634c410def443fd
--- /dev/null
+++ b/marked/H/T-REC-H.362-201009-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f10623b377ee60b790ecf630d2a7e2bbafd7291bfd68d90197e73a097e462cbe
+size 52541
diff --git a/marked/H/T-REC-H.362-201009-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/H/T-REC-H.362-201009-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a9b4d62a212f5791112eff1e20ae698111171693
--- /dev/null
+++ b/marked/H/T-REC-H.362-201009-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5949aa6c83eeccf9bc1bdc75087644c281b97a835d48820b825dfc6ce5764380
+size 84564
diff --git a/marked/H/T-REC-H.362-201009-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/H/T-REC-H.362-201009-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ece2880bb389e7f13d78c239f6d51c88d92887f1
--- /dev/null
+++ b/marked/H/T-REC-H.362-201009-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6bd3ce321d59b775615d3c6f3bcdc473c5c0270ae8172d7d7288abf6232f82f7
+size 102595
diff --git a/marked/H/T-REC-H.362-201009-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/H/T-REC-H.362-201009-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ebcc95744b47a47a459438abf510d5e7fa1d20e2
--- /dev/null
+++ b/marked/H/T-REC-H.362-201009-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fff0296ac0b39bea91713c45c2d5f0a274ae31c8f323ce240f33fabb49b527be
+size 170052
diff --git a/marked/H/T-REC-H.362-201009-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.362-201009-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c6ddf52ecd5333b3a1a147c723d2e9ecf9e4de4b
--- /dev/null
+++ b/marked/H/T-REC-H.362-201009-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b5a0bdab1cea7d52857db651119c5d07afe39229332e09dbdbc5a0d66e93d568
+size 133094
diff --git a/marked/H/T-REC-H.430.3-202309-I_PDF-E/raw.md b/marked/H/T-REC-H.430.3-202309-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..25d4d657ce641d4f731c819deb2f2f2a2d911018
--- /dev/null
+++ b/marked/H/T-REC-H.430.3-202309-I_PDF-E/raw.md
@@ -0,0 +1,843 @@
+
+
+# Recommendation**ITU-T H.430.3 (V2) (09/2023)**
+
+SERIES H: Audiovisual and multimedia systems
+
+Infrastructure of audiovisual services – Telepresence,  
+immersive environments, virtual and extended reality
+
+---
+
+## **Service scenario for immersive live experience (ILE)**
+
+![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 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        |
+| <b>Telepresence, immersive environments, virtual and extended reality</b> | <b>H.420-H.439</b> |
+| 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.3 (V2)
+
+## Service scenario for immersive live experience (ILE)
+
+## Summary
+
+Recommendation ITU-T H.430.3 identifies service scenarios by analysing several use cases of immersive live experience (ILE) services, in order to classify them and to establish a reference model for ILE. The 2023 edition of Recommendation ITU-T H.430.3 appends service scenarios and use cases of interactive immersive services as part of ILE. This Recommendation also summarizes several use cases and identifies candidate technologies for implementing ILE, including related standards gap analysis.
+
+## History \*
+
+| Edition | Recommendation     | Approval   | Study Group | Unique ID          |
+|---------|--------------------|------------|-------------|--------------------|
+| 1.0     | ITU-T H.430.3      | 2018-08-29 | 16          | 11.1002/1000/13668 |
+| 2.0     | ITU-T H.430.3 (V2) | 2023-09-13 | 16          | 11.1002/1000/15652 |
+
+## Keywords
+
+Immersive live experience (ILE), service scenario, standards gap analysis, use cases.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 High-level service category .....                                 | 2    |
+| 7 Categorized service scenarios.....                                | 3    |
+| 7.1 Live sports scenario .....                                      | 3    |
+| 7.2 Entertainment scenarios.....                                    | 5    |
+| 7.3 Telepresence scenarios .....                                    | 7    |
+| 7.4 Remote operation scenarios.....                                 | 9    |
+| 7.5 Emergency scenarios .....                                       | 10   |
+| 7.6 Remote assistance scenarios.....                                | 11   |
+| Appendix I – Use cases for immersive live experience services ..... | 12   |
+| I.1 Introduction .....                                              | 12   |
+| I.2 Use cases of ILE services .....                                 | 12   |
+| I.3 Configuration of ILE .....                                      | 21   |
+| I.4 Candidate technologies used for ILE .....                       | 22   |
+| I.5 Standards gap analysis of ILE related technologies .....        | 23   |
+| Bibliography.....                                                   | 26   |
+
+## Introduction
+
+In recent times, many major sporting and music events have not only been broadcast, but also delivered to remote sites for public or live viewing with the aim of sharing the emotional experience with spectators there as if they themselves were also in the event venue. At the same time, ultra-high definition (UHD) broadcasting known as 4K (resolution of approximately 4 000 pixels) and 8K (resolution of approximately 8 000 pixels) broadcasting is becoming increasingly popular. It is therefore expected that many people all over the world wish to share in the excitement of viewing sporting or musical events on UHD TV or public viewing sites in the near future. However, realistic experience with flat displays has limitations.
+
+In order to provide highly realistic sensations to audiences at remote sites, immersive live experience (ILE) needs to be implemented to reconstruct event sites virtually with presentation of real-sized objects and sound direction by transmitting environmental information together with audio and video streams. For example, using ILE musicians could harmonize with player images that are transmitted from several locations. By using ILE, real objects, in this case musicians at the remote sites, can collaborate with three dimensional images of remote musicians that are projected on to the screen. ILE enables virtual concerts with highly realistic sensations.
+
+In order to share the enthusiasm of event venues with large audiences even if they are remote from the event venue, implementing ILE services based on standardized designs is desirable. ILE can allow audiences anywhere in the world cheer their favourite sporting teams or musical artists at remote sites even if they are not themselves present in the event venue and they may feel a sense of togetherness and even become passionate just as though they were actually present in the event venue.
+
+This Recommendation specifies several service scenarios for ILE to identify key requirements and architectural frameworks to implement its services and provides several use cases around the world. The 2023 edition of this Recommendation appends service scenarios and use cases of interactive immersive services as part of ILE. This Recommendation also provides candidate technologies for implementing ILE and standardization gap analysis of ILE-related technologies.
+
+# Recommendation ITU-T H.430.3 (V2)
+
+## Service scenario for immersive live experience (ILE)
+
+# 1 Scope
+
+This Recommendation analyses several use cases for immersive live experience (ILE), specifies service scenarios, and identifies key requirements and architectural considerations.
+
+This Recommendation includes:
+
+- service scenarios;
+- use cases of ILE services;
+- candidate technologies for implementing ILE;
+- standards gap analysis of ILE related technologies.
+
+# 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 immersive live experience (ILE)** [b-ITU-T H.430.1]: A shared viewing experience that stimulates emotions within audiences at both the event site and the remote sites, as if the audience at the remote sites had wandered into 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.2 haptics** [b-ISO 9241-910]: Sensory and/or motor activity based in the skin, muscles, joints, and tendons.
+
+NOTE – Haptics consists of two parts: touch and kinaesthesia.
+
+**3.1.3 touch** [b-ISO 9241-910]: Sense based on receptors in the skin.
+
+**3.1.4 cutaneous** [b-ISO 9241-910]: Belonging to the skin.
+
+**3.1.5 tactile** [b-ISO 9241-910]: Appertaining to touch.
+
+**3.1.6 kinaesthesia** [b-ISO 9241-910]: Sense and motor activity based in the muscles, joints and tendons.
+
+**3.1.7 kinaesthetic** [b-ISO 9241-910]: Appertaining to kinaesthesia.
+
+**3.1.8 vibrotactile** [b-ISO 9241-910]: 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             |
+| 4D    | four Dimensional              |
+| 6DoF  | six Degrees of Freedom        |
+| AR    | Augmented Reality             |
+| CI    | Composition Information       |
+| codec | coder-decoder                 |
+| DJ    | Disc Jockey                   |
+| EMG   | Electromyograph               |
+| HMD   | Head-Mounted Device           |
+| IIS   | Interactive Immersive Service |
+| ILE   | Immersive Live Experience     |
+| IPTV  | Internet Protocol Television  |
+| MMT   | MPEG media transport          |
+| mux   | multiplexer                   |
+| OMAF  | Omnidirectional Media Format  |
+| QoS   | Quality of Service            |
+| UHD   | Ultra-High Definition         |
+| VR    | Virtual Reality               |
+
+# 5 Conventions
+
+Service scenarios in this Recommendation are described using the following template, in relation to other Recommendations, use cases, requirements, etc.
+
+| <b>Title-X: high-level service scenario title</b> | <b>Sub-title: Specific title of service scenario related to the high-level service scenario</b> |
+|---------------------------------------------------|-------------------------------------------------------------------------------------------------|
+| Description                                       | General description for service scenario of ILE                                                 |
+| Service scenario                                  | General explanation of how a service works                                                      |
+| Stakeholder (actor)/domains                       | Roles of related stakeholders and domains                                                       |
+| Main requirements                                 | Service and technical requirements                                                              |
+| Source (references)                               | Use cases in Appendix I or reference document, websites                                         |
+
+# 6 High-level service category
+
+This clause briefly describes the high-level service categories shown in Figure 1. ILE services or use cases can be classified into several categories of scenario, such as live sports, entertainment and telepresence.
+
+![A diagram showing 'Immersive live experience use cases' branching into four categories: Live sports scenario, Entertainment scenario, Telepresence scenario, and Remote operation scenario. A note below states that categorization is not limited to these and more classification should be studied. The code H.430.3(23)_F01 is in the bottom right.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg)
+
+**Immersive live experience use cases**
+
+**Live sports scenario**  
+Sports continue to sustain popularity among other contents and present a great opportunity to harness technologies available to further enhance the experience for spectators
+
+**Entertainment scenario**  
+Music concerts or theatrical plays require live experience on stage where actors perform to appeal to their audiences and there are ways to reproduce the similar or better experience without actors on stage
+
+**Telepresence scenario**  
+Figure, either a person or an object, could be transported in real time to remote places as a whole for informative purposes
+
+**Remote operation scenario**  
+Remote surgery and collaborative operation could be realized by interactive immersive video, audio and haptic information with remote persons
+
+⋮
+
+Categorization for use cases of Immersive Live Experience is not limited to above scenarios and more classification should be further studied
+
+H.430.3(23)\_F01
+
+A diagram showing 'Immersive live experience use cases' branching into four categories: Live sports scenario, Entertainment scenario, Telepresence scenario, and Remote operation scenario. A note below states that categorization is not limited to these and more classification should be studied. The code H.430.3(23)\_F01 is in the bottom right.
+
+**Figure 1 – High-level service categories of ILE services**
+
+Major categories for use cases of ILE include, but are not limited to, the following.
+
+- Live sports scenario: Sport continues to maintain popularity among other content and presents a great opportunity to harness technologies available to further enhance the experience for spectators.
+- Entertainment scenario: Concerts or stage plays require live experience where actors perform to their audiences; there are ways to reproduce a similar or better experience without live actors.
+- Telepresence scenario: An image of a figure, either a person or an object, can be transported in real time to remote places as a whole for informative purposes.
+- Remote operation scenario: Remote surgery and collaborative operation can be effectively realized by interactive immersive video, audio and haptic information with remote persons.
+
+# **7 Categorized service scenarios**
+
+## **7.1 Live sports scenario**
+
+The following tables describe live sports scenarios.
+
+| Live sports | Live broadcast service of first-person synchronous view                                                                                                             |
+|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Description | The service is provided by transmission by high-definition media of a first person viewpoint of an athlete in real time via a camera installed in sports equipment. |
+
+| <b>Live sports</b>    | <b>Live broadcast service of first-person synchronous view</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Service scenario      | <p>A synchronous camera is installed on the front of a fast-moving vehicle, such as a racing car or bobsleigh, whose perspective is fixed to face straight ahead along the racecourse. In other words, the camera provides a first person synchronous view as if audience members were riding in the athlete's vehicle.</p> <p>The camera is equipped with network capability of sufficiently high bandwidth to seamlessly upload its live feed in ultra-high definition (UHD) to a backend system that is then broadcast to user devices.</p> <p>The view is provided via either a big screen or mobile device screen. The additional information related to the race, such as speed, acceleration, current ranking and remaining distance to the finish line, can enhance the excitement of ongoing competition.</p> <p>The purpose of the service is to simulate the game-like experience of becoming an athlete on the track in real time.</p> |
+| Stakeholders (actors) | Institutes managing facilities at sports venues, participating athletes, producers with broadcasting rights, network providers.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| Main requirements     | Extremely stringent delay, ultra-high-definition coder-decoder (codec), reliable and broadband uplink.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| Source (references)   | KT use case, see clause I.2.7.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+| <b>Live sports</b>    | <b>Live 360° virtual reality service of single point view</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Description           | The service provides an immersive experience of attending a live event at a sports venue by constructing a 360° panoramic view in real time via multiple camera feeds from the site.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| Service scenario      | <p>A camera capable of filming live panoramic views or several high-definition cameras is or are installed at the venue such as a gymnasium, an ice rink (for figure skating events) and stadia (for ball games, athletic sports and opening or closing ceremonies).</p> <p>The live feeds from cameras at multiple angles are transmitted via a high-bandwidth uplink to a backend system for distribution with minimum latency.</p> <p>In order to view several media, including broadcasting, in an appropriate form, a user might need to wear a special device like virtual reality (VR) goggles or a head-mounted device (HMD) that constantly process and piece together multiple images to project the real world. For this purpose, it can be used in pseudo-three dimensional (pseudo-3D) displays without special wearable devices such as VR goggles or an HMD.</p> <p>The purpose of the service is to enable viewers to observe every event live around the venue so that they feel as if they are present at the remote location.</p> |
+| Stakeholders (actors) | Institutes managing facilities at sports venues, participating athletes, producers with broadcasting rights, network providers, VR manufacturers.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| Main requirements     | Extremely stringent delay, UHD codec, reliable and broadband connection, massive connectivity, VR media processing (e.g., image stitching).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| Source (references)   | <p>NTT use case (Kirari!), see clauses I.2.1, I.2.8, I.2.9 and I.3.</p> <p>KT use case, see clause I.2.7.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+| <b>Live sports</b>    | <b>Live broadcast service of selected multi objective view</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Description           | The broadcasting service provides a user-selected view of live game action in high definition from among other preinstalled cameras at the venue with the aid of position information of athletes on a 3D map.                                                                                                                                                                                                                                                                                                                          |
+| Service scenario      | A number of cameras is installed at strategic locations along the racecourse where live action of athletes can be best captured simultaneously.<br>With the aid of a 3D map interface, viewers can select any point of interest on the map at any given time for better angles of an action. Every competing athlete is tracked in real time and their corresponding locations continuously indicated on the map.<br>The service provides a perspective of the racecourse from all angles to better track favourite athletes in action. |
+| Stakeholders (actors) | Institutes managing facilities at sports venues, participating athletes, producers with broadcasting rights, network providers, outdoor positioning information providers.                                                                                                                                                                                                                                                                                                                                                              |
+| Main requirements     | Extremely stringent delay, UHD codec, reliable and broadband uplink, massive connectivity, location-based services (e.g., 3D map, precise positioning).                                                                                                                                                                                                                                                                                                                                                                                 |
+| Source (references)   | KT use case [b-Sohn], see also clause I.2.7.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+| <b>Live sports</b>    | <b>Becoming-player sports viewing</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Description           | The service provides a becoming-player experience by using haptic sense in addition to video and audio during a sports match. A combination of visual-auditory-haptic senses aims to reproduce becoming-player sensations for real players at the event site.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| Service scenario      | At the viewing site, people are in front of a monitor and move as if they are players in the stadium at the event site. Sound from the event site is transmitted to vibration platforms on which people stand, equipped with vibration devices. While watching the game on the monitor, each person moves their devices as if they are one of the players at the event site.<br>As a result, people feel as if they are standing in the stadium at the event site due to the vibrations of their feet, and at the same time, they feel as if vibrations are occurring in their bodies in response to their movements. They are able to feel the physical movements of players and reproduce them through their own bodies.<br>The purpose of the service is to provide audiences with becoming-player sports viewing by interactive ILE with haptic information, which can be further enhanced by addition of special effects, such as lighting, temperature and humidity. |
+| Stakeholders (actors) | Interested people: producers with broadcasting rights, promoters of a sports event, video, audio and haptic equipment providers, data analytics providers, network providers.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| Main requirements     | High-definition codec, high definition audio, haptic sensing, haptic transmission, haptic reproduction, video/audio/haptic multiplexer (mux), converter, reliable and broadband connectivity.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| Source (references)   | NTT West use case, see clause I.2.16.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+## 7.2 Entertainment scenarios
+
+The following tables describe entertainment scenarios.
+
+| <b>Entertainment</b> | <b>On-stage holographic performance show service</b>                                                                                                                                |
+|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Description          | The service provides holographic media of concerts that are live-streamed or pre-recorded for audiences at special theatres with capability of reconstructing the live environment. |
+
+| <b>Entertainment</b>  | <b>On-stage holographic performance show service</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Service scenario      | <p>A live concert performance is captured or pre-recorded by several UHD cameras at multiple angles and using high-quality microphone systems. Then, high-quality UHD video and audio is processed separately at the initial stage. Processed media streams, including video, audio and other sensory data, should be transmitted synchronously from the event to remote sites.</p> <p>A theatre similar to one set up for the original concert hall is reconstructed at a remote site for highly realistic effects where the processed media stream is regenerated to simulate the live event. Audiences at such a remote site can experience almost the same visual and sound quality as the original on holographic or pseudo-3D projection.</p> <p>The purpose of the service is to evoke the sense of a concert-like environment that is on a par with a real concert but without actual performers on stage.</p> |
+| Stakeholders (actors) | Concert performers, concert producers, network providers, hologram equipment providers.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| Main requirements     | UHD codec, hologram conversion, on stage hologram or pseudo-3D projection, video/audio mux.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| Source (references)   | NTT use case (Kirari!), see clauses I.2.1, I.2.8, I.2.9 and I.3.<br>KT use case, see clause I.2.7.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+| <b>Entertainment</b>  | <b>Live interactive service</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Description           | <p>The service provides virtual scenes in collaboration with real people and transmitted images in real time. The images are extracted from real people in different places and transmitted by real-time high-definition media. The transmitted images and sounds are reconstructed and interact with real people at a remote site. The service, which might be considered as a variation of live interactive service, also provides virtual scenes in collaboration with real people and transmitted images in real time. Haptic information is interactively communicated within remote places and event sites.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| Service scenario      | <p>Live video images of artists at event venues are extracted in real time and transmitted in various media formats synchronously over high-speed networks with low latency. In viewing sites, transmitted images and sounds are dynamically projected and mapped on to multiple transparent screens that are spatially set up. As an optional feature, the vibration of artists or audiences can be captured at each site and transmitted to other sites including studios without audience, in order to share amount of excitement and to play music synchronously even in noisy situations.</p> <p>A real person, such as a disc jockey (DJ) or master of ceremonies, at the remote site can collaborate and interact with artists in event venues by transmitted images.</p> <p>The purpose of this service is to provide the audience at a remote site with a new immersive experience as if they are watching the live stage of a DJ interacting with artists in the event venue who are teleported to remote sites beyond time and space. By adding haptic communication, this service may provide new entertainment feature which realize location free concerts, and the audience in event venues and remote sites with a new immersive experience as if they are watching one complete live stage in the event venue.</p> |
+| Stakeholders (actors) | Institutes managing facilities at event venue, participating artists, producers with broadcasting rights, network providers.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| Main requirements     | Extremely stringent delay, UHD codec, reliable and broadband uplink and downlink, haptic communication.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| Source (references)   | NTT use case, see clauses I.2.8, I.2.9, I.2.10 and I.2.11.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+| <b>Entertainment</b>  | <b>Multi-angle viewing service</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Description           | The service projects virtual pseudo-3D images on to a special arena, which can be viewed from any angle, and reconstructs sound direction. The images are captured by several cameras at the event site and transmitted with audio and spatial information synchronously to remote sites, at which the images and sound are reconstructed in a special arena. The users can simultaneously watch the images from their standpoints.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| Service scenario      | <p>The images of artists or sport players at an event site are extracted by using several cameras and their sounds captured by using several microphones. In addition, 3D-sensing and object-tracking information is captured to fix spatial locations. These video and audio streams are synchronously transmitted to the viewing site with spatial information via high-speed networks.</p> <p>At the viewing site, these images and sounds are reconstructed in a special arena, which has multiple screens and an array of loudspeakers.</p> <p>The audiences at viewing sites can see images from any angle outside the special arena and synchronously hear sounds. In order to realize image or auditory localization, pseudo-3D image displaying and wave field synthesis might be used in a special arena.</p> <p>The purpose of this service is to provide experience of real events that are reconstructed images and sounds in a special arena in real time. By using this service, several audiences can watch the event at viewing sites such as sport bars.</p> |
+| Stakeholders (actors) | Institutes managing facilities at event venue, participating artists, producers with broadcasting rights, network providers.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| Main requirements     | Extremely stringent delay, UHD codec, reliable and broadband uplink and downlink, pseudo-3D display, wave field synthesis.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| Source (references)   | NTT use case, see clauses I.2.8, I.2.9, I.2.10 and I.2.11.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+## 7.3 Telepresence scenarios
+
+The following tables describe telepresence scenarios.
+
+| <b>Telepresence</b>   | <b>Live ultra-high-definition presence video view service</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Description           | The service provides a real-time holographic presentation of a person of interest in UHD with augmented information or special effects around the figure for audiences at viewing sites.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| Service scenario      | <p>A single person of interest such as someone being interviewed or highlighted is captured in real time by a special holographic camera.</p> <p>Once high-definition video and digital audio are encoded, they are synchronously transmitted via an ultra-high-speed network to a viewing site where the holographic video and audio are decoded and reproduced in real time.</p> <p>Various special effects like animation or information in many formats can be projected on to an original object or person for amusement or marketing. For a better feeling of reality, projection of the person or object at their actual size is preferred.</p> <p>The purpose of the service is to provide ILE of telepresence of a person or object at their actual size that can be further enhanced by addition of special effects.</p> |
+| Stakeholders (actors) | Interested people: producers with broadcasting rights, hologram equipment providers, data analytics providers, network providers.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| Main requirements     | High-definition codec, hologram conversion, hologram projection, high-definition audio, video/audio mux, converter, reliable and broadband connectivity.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+| <b>Telepresence</b> | <b>Live ultra-high-definition presence video view service</b>                                                                |
+|---------------------|------------------------------------------------------------------------------------------------------------------------------|
+| Source (references) | KT use case [b-KT PC], see also clause I.2.7.<br>NTT use case [b-NTT JKF], see also clauses I.2.8, I.2.9, I.2.10 and I.2.11. |
+
+| <b>Telepresence</b>   | <b>Immersive live meeting</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Description           | This service provides teleconferencing where participants from remote sites are represented as highly realistic images to each other in order to induce an immersive experience of being present in the same meeting room.                                                                                                                                                                                                                                                                                                                                        |
+| Service scenario      | Each participant image is captured by cameras, then high-resolution video and audio are transmitted over extremely low latency and high bandwidth networks. A highly realistic image of each participant is distributed to all others in real time.<br>Users can view the scene at the reconstruction end and feel themselves to be in a fully immersive meeting environment, where they can interact with actual figures of people.<br>The purpose of this service is to provide a portrait capture and display service for video conferences, board games, etc. |
+| Stakeholders (actors) | Business discussants, image capture equipment providers, network providers, game producers.                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| Main requirements     | Image capture equipment, UHD codec, reliable and broadband uplink and downlink, virtual or holographic display device.                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| Source (references)   | OKI use case, see clause I.2.4.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+| <b>Telepresence</b>   | <b>Interactive presence service with haptic sense</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Description           | The service provides haptic sense in addition to video and audio of a person during face-to-face conversation. A combination of visual-auditory-haptic senses aims to reproduce the atmosphere of a real conversation, by using a communication system with other people who share a similar desk at a remote site.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| Service scenario      | A user is seated in front of a communication system, whose display shows the upper body of another user at a remote site. The area between the display and user is a shared space for haptic interaction. The area shows the hands of another user and vibrators are attached behind the screen to reproduce vibrotactile information at the remote site.<br>Vibrotactile information from the remote user is captured by sensing devices and transmitted from the remote to the other site. Haptic information is reproduced by the vibration devices synchronously with visual and auditory information from the remote user.<br>The purpose of the service is to provide interactive ILE of telepresence of a person or object at actual size with haptic information, which can be further enhanced by addition of special effects, such as lighting, temperature and humidity. |
+| Stakeholders (actors) | Interested people: producers with broadcasting rights, hologram equipment providers, data analytics providers, network providers.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| Main requirements     | High-definition codec, hologram conversion, hologram projection, high-definition audio, haptic sensing, haptic transmission, haptic reproduction, video/audio/haptic mux, converter, reliable and broadband connectivity.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| Source (references)   | NTT use case [b-NTT ICC].                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+## 7.4 Remote operation scenarios
+
+The following tables describe remote operation scenarios.
+
+| Remote operation      | Interactive live object control                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Description           | This service provides interactive control of actual objects from remote sites in real time so that users can experience additional senses of touch and control, providing an increased degree of reality as a result.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| Service scenario      | <p>Certain spatial dimensions are set up at a real-world location, which users can physically pilot from remote sites. The boundaries of the space are marked by sensors installed on the corners. Selected physical object(s) is (are) placed inside the setting delimited by the boundaries. Such objects are scanned and digitally encoded in advance or in real time to create an exact replica for display and control of the virtual object. With this or these physical object(s), a user can navigate and manipulate the virtual objects with a high degree of ease and comfort.</p> <p>This virtual object is coordinated in a central location, distributed over a network of high bandwidth and low latency and fed into an HMD or 3D display in real time for multiple users at different places where they interact with each other in similar settings to the first as if they are all in the same venue. Especially with such items under control, users interact with virtual objects in a far more immersive and live manner.</p> <p>The purpose of the service is to provide users with a great degree of manoeuvrability via a virtual world combined with physical object(s), further enhancing immersive and live aspects of user interaction experience.</p> |
+| Stakeholders (actors) | VR producers, government and travel agencies for scenery rights, sports associations, HMD and sensor equipment providers, network providers.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| Main requirements     | VR production, object encoding and coordination, UHD codec, reliable and broadband downlink, extremely stringent delay, HMD and VR sensors.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| Source (references)   | Tektonspace use case [b-Tektonspace].                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+| Remote operation      | Remote object operation                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Description           | The service provides interactive remote control capabilities. Users can perform operations on remote objects via their virtual images.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| Service scenario      | <p>A high-resolution image of remote object(s), with the help of capture equipment, is generated by a combination of XR, holographic 3D image, surrounding audio, haptic information and other multimedia technologies. The image is transmitted to remote users over extremely low latency and high bandwidth networks in real time. Users can perform a series of operations on remote object(s) by interacting with this image. Information about operations on the image is captured and converted into control signals, transmitted to remote auxiliary facilities through extremely low latency and reliable networks. The facilities perform operations on remote object(s) in accordance with the control signals received. Feedback information about remote object(s) is reflected in the image in real time.</p> <p>The purpose of this service is to provide interactive remote capabilities for industrial control, remote maintenance, remote surgery, prototype design and test, etc.</p> |
+| Stakeholders (actors) | Manufacturers, medical institutions, image equipment providers, sensor equipment providers, auxiliary equipment providers, network providers.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| Main requirements     | Image capture equipment, sensor equipment, UHD codec, reliable and broadband uplink and downlink, ultra-low latency, extremely stringent delay, multiple stream synchronization, hologram conversion and projection, holographic display device.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+| <b>Remote operation</b> | <b>Remote object operation</b>              |
+|-------------------------|---------------------------------------------|
+| Source (references)     | Remote surgery use case, see clause I.2.12. |
+
+| <b>Remote operation</b> | <b>Real-time multi-user collaboration</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Description             | This service provides multi-user manipulation on 3D or holographic images of real objects or digital models, which can be simultaneously viewed from any angle or position and changed by users.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| Service scenario        | <p>The images of real object(s) captured by high-definition cameras or laser scanners and virtual object(s) generated by computer as an option are transmitted to multiple users after media processing (e.g., media selection, rendering). Multiple users can synchronously view the virtual object(s) on display devices from different angles, and manipulate the virtual object(s) via peripheral equipment(s) (e.g., camera, data glove). During the collaboration, remote users can see a virtual scene of the event site and all real-time changes in the virtual object(s), and communicate and collaborate with each user at the event and other remote sites as if they work in the same place.</p> <p>The purpose of this service is to provide users with synchronous interaction on real and virtual object(s) by immersive communication with each other user for remote teaching, remote training, remote collaborative design, etc.</p> |
+| Stakeholders (actors)   | Capture equipment providers, network providers, display equipment providers, peripheral equipment providers, owners of the physical object, simulated data providers, collaborative participants.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| Main requirements       | Capture device, UHD codec, reliable and broadband uplink and downlink, hologram or 3D display, real-time media processing.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| Source (references)     | Multi-user collaborative design use case, see clause I.2.13.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+## 7.5 Emergency scenarios
+
+The following tables describe emergency scenarios.
+
+| <b>Emergency</b>      | <b>Live streaming service in inaccessible areas</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Description           | The service provides real time reconstruction of scenes in inaccessible areas that cannot be reached by humans immediately, such as post-disaster environments, polar regions or inaccessible mountains.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| Service scenario      | <p>This scenario provides an immersive experience for inaccessible areas. By using robots and unmanned aerial vehicles carrying microphones, holographic cameras, environmental sensors in position or by using pre-installed sensors, UHD video and audio are captured and processed.</p> <p>In close proximity to these areas, in a location that people can reach, high-bandwidth and low-latency wireless network coverage is needed to transmit high-quality holographic data.</p> <p>These scenes are reconstructed in real time at the viewing site (possibly the disaster relief command centre or the polar experience museum). In addition to holographic video and high-quality audio projection abilities, viewing sites also require testing by manufacturers under extreme conditions, such as a challenging temperature and humidity simulator for human tolerance.</p> |
+| Stakeholders (actors) | Government, travel producers, hologram equipment providers, network providers.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| Main requirements     | Capture device, environment analysis and position assign system, UHD codec, reliable and broadband uplink, hologram projection.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| Source (references)   | NA.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+## 7.6 Remote assistance scenarios
+
+The following tables describe remote assistance scenarios.
+
+| <b>Remote assistance</b> | <b>Remote assistance</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Description              | This service provides remote assistance to users by professionals. Users can experience highly realistic guidance by using this service.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| Service scenario         | This service contains one guiding site as a remote site and guided sites as event sites. An original image is captured from one guided site and transmitted to another to project the virtual image. Professionals can demonstrate on the image for guidance. The demonstration (voice, action, signs, etc.) is captured and transmitted to guided sites. Then representatives at guided sites demonstrate on the real object. Users at guided sites can do the same operation on a real object according to the guidance presented. Changes in real object and demonstration are synchronously reflected in the images at both sites. |
+| Stakeholders (actors)    | Government, rescue centres, education or technical support centres, hologram equipment providers, augmented reality (AR) equipment providers, network providers.                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| Main requirements        | Capture device, reliable and broadband uplink, AR or holographic display device.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| Source (references)      | Emergency treatment guidance use case, see clause I.2.14.<br>Remote maintenance guidance use case, see clause I.2.15.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+# Appendix I
+
+## Use cases for immersive live experience services
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This appendix provides several use cases for ILE services and identifies candidate technologies for implementing ILE. In addition, this appendix summarizes standards gap analysis related to ILE technologies.
+
+### I.1 Introduction
+
+ILE is a completely new service, so it is important to create common understanding through identifying use cases for it. In addition, this appendix identifies standardization gaps within and outside ITU-T, since several key technologies may already be standardized in ITU-T or in other standards development organizations.
+
+This appendix includes:
+
+- use cases of ILE services;
+- configuration of ILE;
+- candidate technologies for implementing ILE;
+- standards gap analysis of ILE-related technologies.
+
+### I.2 Use cases of ILE services
+
+#### I.2.1 Use case – Kirari! (NTT)
+
+Nowadays, big events such as worldwide sports events like the soccer World Cup are not only broadcast on live television but can also be watched on public or live viewing sites for sharing emotions with audiences. Watching styles are becoming more diversified. It is expected that sharing emotions with audiences will be increased by highly realistic television and public viewing sites using 4K and 8K technologies.
+
+In order to provide UHD content and highly realistic sensations for audiences in remote sites, NTT has been working on research and development of immersive telepresence technology called "Kirari!", which consists of real time and synchronous media transmission, UHD media codecs, spatial and environmental information transmission, etc. As shown in Figure I.1, Kirari! enables audiences who can be anywhere in the world to feel highly realistic sensations as if they were present in a major event venue. At the event site, multiple cameras and sensors capture information about objects and the environment, and the information is sent to remote sites with some media transformation in real time. At the remote sites, virtual images reconstruct the atmosphere of the event site using time-synchronized media such as 3D projection, surrounding audio and lighting. Audiences at remote sites can share emotions with spectators at the event site and watch their favourite stars with their own eyes.
+
+![Figure I.1 – Concept of Kirari! A composite image showing a world map with three circular insets of people, connected by blue curved arrows. Below the map, a group of people is shown clapping. Overlaid text reads: 'Audiences can have the emotions and get stars in their eyes by Immersive Live Experience'. A small code 'H.430.3(18)_FI.1' is in the bottom right corner.](3267a096e9ca525744d8cd820f12eb59_img.jpg)
+
+Figure I.1 – Concept of Kirari! A composite image showing a world map with three circular insets of people, connected by blue curved arrows. Below the map, a group of people is shown clapping. Overlaid text reads: 'Audiences can have the emotions and get stars in their eyes by Immersive Live Experience'. A small code 'H.430.3(18)\_FI.1' is in the bottom right corner.
+
+**Figure I.1 – Concept of Kirari!**
+
+#### **I.2.2 Use case – High-quality video for VR streaming (Fraunhofer HHI)**
+
+One of the critical elements to produce ILE effectively is to capture the 360° surrounding environment of a source venue. Several camera systems can be used to deliver such VR video content such as direct stitching by using mirrors, depth-aware stitching and depth-enabled light-field rendering.
+
+Multi-view reconstruction enables a 3D image of a real person or object to be projected on to a computer-generated background and provides an immersive experience of being present in the virtual surroundings.
+
+Another sophisticated video streaming technology can be employed, in which many tile-based images are encoded using high efficiency video coding and then stitched together to render a cubic virtual environment.
+
+#### **I.2.3 Use case – 3D interactive experience (B<>Com)**
+
+With advanced technologies using six degrees of freedom (6DoF) VR reconstruction of the surrounding environment, sparse camera arrays, and a light field of representation and compression and point cloud, a 3D interactive service delivers a virtual environment in which a single or multiple users can interact with each other or computer-generated 3D objects in an ultra-realistic way. This service provides users with the ultimate natural feeling of virtual presence.
+
+#### **I.2.4 Use case – Ultra-realistic telework and 4K/8K broadcast (OKI)**
+
+High-resolution displays along with high definition sound systems transform separate working places into one integrated immersive office in which people can collaborate as if they were right next to each other.
+
+The general public is able to watch big sporting events such as the Olympic or Paralympic Games, which are broadcast in extremely high definition of 4K or 8K. This service provides viewers with much crisper and more accurate images of sports events and produces an ILE even in a 2D setting.
+
+#### **I.2.5 Use case – High-quality cloud-based 360° rendering and streaming (Fraunhofer FOCUS)**
+
+Cloud-based 360° video playout enables high-quality 360° experience on low capability devices such as hybrid TVs and mobile devices. By moving a simple remote control, video adjusts the angle of a scene accordingly in real time, providing some degree of immersive experience. The video is produced and rendered on a backend system from signals received by remote control of movement.
+
+#### **I.2.6 Use case – Multi-channel 4K and 8K broadcast service (NHK)**
+
+Live video of 8K quality is broadcast over satellite with multiple videos of high quality up to 4K supplemented over broadband in order to provide a high degree of excitement about live action.
+
+#### I.2.7 Use case – Immersive live experience over 5G technologies (KT)
+
+5G technologies of high bandwidth and low latency provide robust infrastructure on which ILE is featured for a batch of 5G services.
+
+A high-speed bobsleigh equipped with a high resolution camera provides a first person synchronous view in real time over 5G radio technologies augmented with various physical status information points about the athlete such as heart rate to give an immersive feel of what the athlete sees and feels.
+
+The 360° VR/TimeSlice service lets audiences with HMDs absorb a sense of immersive presence with access to all angle views around the venues and through mobile devices, also a 360° peripheral view of any athlete selected by the viewer allowing a close up monitoring of events such as ice hockey tournaments or figure skating.
+
+Hologram Live teleports a real size image of a person or object from remote sites and creates a virtual environment in which an interview can be conducted live. This multi-site service utilizes hologram technologies to carefully integrate two live images from different venues into one place to coordinate or choreograph multi-party activities as if everyone were present at the same spot.
+
+#### I.2.8 Use case – Interaction with images (NTT)
+
+On 2017-03-13, a music live showcase was presented as a remote interactive performance between Tokyo and Austin, Texas.
+
+Featuring a Japanese electronic music producer and DJ in Austin, and Japanese artists in Tokyo, NTT showed a live performance experience, *Cyber teleportation Tokyo at SXSW* [b-NTT Krause], in which the audience experienced an immersive synchronized performance of a DJ in Austin and the artists "teleported" from Tokyo.
+
+The live video images of the artists in Tokyo were extracted in real time and transported in various media formats synchronously over the network, then dynamically projected on to multiple double-sided transparent screens that were spatially set up in the Austin live space (see Figure I.2) by utilizing NTT's Kirari! technology. The latency is about 400 ms, so the interaction was sufficient.
+
+The network infrastructure used for this showcase was established using NTT's network testbed GEMnet2, in cooperation with Internet2 (a consortium of US universities providing an advanced networking environment), the Lonestar Education and Research Network and the University of Texas System, and Greater Austin Area Telecommunication Network.
+
+These technologies provided the audience in Austin with a new immersive experience as if they were seeing the interplay live on stage of the DJ with the artists in Tokyo who were teleported to Austin.
+
+![Figure I.2: Four panels showing the stage setup for the Cyber teleportation Tokyo at SXSW. The top-left panel shows a wide view of the stage with multiple transparent screens displaying colorful graphics. The top-right panel shows a crowd of people with their hands raised, looking at the screens. The bottom-left panel shows a close-up of the transparent screens displaying data-like visualizations. The bottom-right panel shows a person on stage, possibly a DJ, interacting with the screens. A small text label 'H.430.3(18)_FI.2' is visible in the bottom right corner of the image area.](a251a846ffb8c1750262be87b489eeec_img.jpg)
+
+Figure I.2: Four panels showing the stage setup for the Cyber teleportation Tokyo at SXSW. The top-left panel shows a wide view of the stage with multiple transparent screens displaying colorful graphics. The top-right panel shows a crowd of people with their hands raised, looking at the screens. The bottom-left panel shows a close-up of the transparent screens displaying data-like visualizations. The bottom-right panel shows a person on stage, possibly a DJ, interacting with the screens. A small text label 'H.430.3(18)\_FI.2' is visible in the bottom right corner of the image area.
+
+**Figure I.2 – Computer-generated images of the stage at *Cyber teleportation Tokyo at SXSW***
+
+#### I.2.9 Use case – Multi-angle viewing styles (NTT)
+
+Several cameras at an event site and transmitting images all over the world, enables the atmosphere of the event site to be captured and reconstructed at viewing sites. NTT has developed a new viewing
+
+style for audiences who watch a reconstructed event together at a remote site, namely *Kirari! for Arena*, which reconstructs the atmosphere of the event site allowing viewing from several angles by audiences at viewing sites, by capturing object images with their location information. Figure I.3 shows an image constructed by "*Kirari! for Arena*" of a judo event.
+
+![A 3D reconstructed image of a judo match. Two judokas, one in a white gi and the other in a blue gi, are engaged in a match on a red mat. The background is dark, with some blurred figures of spectators visible in the shadows.](3376f33dd811eb3e39ff47117c958ed9_img.jpg)
+
+A 3D reconstructed image of a judo match. Two judokas, one in a white gi and the other in a blue gi, are engaged in a match on a red mat. The background is dark, with some blurred figures of spectators visible in the shadows.
+
+H.430.3(18)\_FI.3
+
+**Figure I.3 – Image constructed by *Kirari! for Arena* of judo**
+
+3D-sensing and object-tracking technologies are key functionalities for realizing *Kirari! for Arena*. In order to reconstruct the atmosphere of an event site at viewing sites, capture of 3D position information of objects and object tracking are required. The combination of object recognition using deep learning, object tracking using particulate filters and depth sensors using lasers enables rough tracking of object location. The location information enables reproduction of natural motion in depth in addition to horizontal direction at viewing sites.
+
+Another key functionality is pseudo-3D image localization, which reconstructs the atmosphere of an event site at viewing sites and displays natural motion of objects even in the depth direction. This also enables many audiences to observe a displayed object from any angle. Pseudo-3D image localization can reconstruct event venues with moving objects at viewing sites, so that dynamic display achieves spatial position relations as if players were moving around fields in front of audiences.
+
+By using a simple display device, as shown in Figure I.4, audiences can watch objects displayed as pseudo-3D images without recognition of the display devices. Displayed at viewing sites on the horizontal floor plane is a projected pseudo-3D image reflected by an angled half mirror, which transmits some incident light and reflects the rest. In this case, it is difficult to move images in the depth direction since the pseudo-3D images are fixed at the same location. In order to display moving objects in the depth direction, utilization of visual effects is required for audience perception.
+
+![A photograph of a physical display setup. A large, dark, angular structure made of four half-mirrors is positioned on a stage. In the center, a small, brightly lit area on the floor displays a projected image of a judo match, appearing as a pseudo-3D effect to the audience.](40aa08ca83c29a9281c0096fb9335f55_img.jpg)
+
+A photograph of a physical display setup. A large, dark, angular structure made of four half-mirrors is positioned on a stage. In the center, a small, brightly lit area on the floor displays a projected image of a judo match, appearing as a pseudo-3D effect to the audience.
+
+H.430.3(18)\_FI.4
+
+**Figure I.4 – Simple display device using four half mirrors**
+
+#### I.2.10 Use case – Remote ensemble concert using haptic communication (NTT)
+
+Remote or virtual concerts, which are realized by using telecommunication network, are challenges addressed recently. At some remote concerts, musicians are located in several different places, like Tokyo and Paris, and they play instruments or sing songs synchronously. This type of remote concerts is called "remote ensemble concert".
+
+Remote ensemble concerts need communication networks with very low latency, because players who are in different places have to play synchronously. Most music players recognize the baton of conductor, sound of drumstick and some vibrations when they start playing, so haptic communication may be needed for remote ensemble concerts.
+
+As an example, Figure I.5 shows an image of a remote ensemble concert.
+
+![Diagram of a remote ensemble concert setup showing four locations connected via a central network cloud.](09955ff8214ffb6947951fc0f60eb6ab_img.jpg)
+
+The diagram illustrates a remote ensemble concert setup. At the center is a light blue cloud labeled "Network". Four pink ovals, each representing a location, are connected to this central network. The locations are: "Concert hall A with audiences" (top left), "Concert hall B with audiences" (top right), "Studio without audiences" (bottom left), and "Live viewing site with audiences" (bottom right). Each location contains an "ILE display" and "Real musicians". In Concert hall A and B, the ILE display shows a virtual stage with multiple video feeds of musicians. In the Studio, the ILE display shows a single video feed of a musician playing a saxophone. In the Live viewing site, the ILE display shows a virtual stage with multiple video feeds of musicians. The audiences are represented by silhouettes of people in the concert halls and live viewing site.
+
+H.430.3(23)\_FI.5
+
+Diagram of a remote ensemble concert setup showing four locations connected via a central network cloud.
+
+**Figure I.5 – Images of a remote ensemble concert**
+
+This example is a live concert event involving four locations. Real musicians play instruments in three places, and audiences are located at three places. In concert hall A, an ILE display is installed to show real musicians at remote places, allowing audiences to see them as well as local real musicians. At a live viewing site, there are ILE systems that reconstruct a virtual event venue with combination of other places, and audiences can enjoy virtual concert. All musicians have to play synchronously, so timing recognition is critical when they start playing music. In concert halls A and B, musicians may need vibration signals as cues because of the noisy situation. Vibration signals might be sent from hall A to hall B and studio allowing synchronous playing of music. In addition, real musicians in the studio, where there is no audience, may feel the atmosphere in halls A and B and live viewing site by video, sound and some vibration information.
+
+The benefits of haptic communication such as vibration transmission in a remote ensemble concert are considered at the start of a music performance, especially to adjust timing, as follows:
+
+- vibration might not be affected by a noisy environment;
+- for instrumental playing, vibration might not hinder music performance;
+- vibration can be used even in dark concert hall such as rock concert with lighting effects or stage effects, and stage monitor display might hinder stage effects;
+
+— players can pick up cue from the conductor cue by vibration, thus players can see audiences in the concert halls and in the remote sites through display.
+
+When a rhythm is constant, haptic signals might be generated by a beat manager such as a conductor, sequencer or metronome. For a remote ensemble concert, a haptic signal might be generated by information from a remote site. An electromyograph (EMG) signal is obtained on starting to play musical instruments because humans move muscle to make sound. For example, an EMG signal is generated when a drummer raises a drumstick, since this involves arm movement. Thus, an EMG signal can be detected before the stick hits the drum. If information from the EMG is transmitted earlier than that of sound, other players like guitarists at another site can feel the vibration triggered by the EMG information before the drum is heard from the remote site.
+
+In this example, it might be needed to implement interactive haptic communication, in addition to 3D videos, audios, lighting, and stage effects, within these four sites for a successful remote ensemble concert.
+
+#### I.2.11 Use case – Public booth for vibrotactile communication (NTT)
+
+A public booth for vibrotactile communication has been introduced as an interactive immersive service (IIS) using vibrotactile communication. This service utilizes an interactive audio-visual-haptic media that allows users to feel vibrations of other people at remote site who share feelings at the same desk. The system configuration is shown in Figure I.6.
+
+![Figure I.6: Configuration of the public booth for vibrotactile communication. The diagram shows two identical booths connected by a central 'Communication system' consisting of two 'Terminal' units and a 'Network'. Each booth contains a 'Camera', 'Screens', 'Projectors', a 'Sensor', and a 'Vibrator'. A hand is shown interacting with the 'Vibrator' and 'Sensor' in each booth. Orange arrows labeled 'Vibration' show the flow of data from the sensor in one booth, through the network, to the vibrator in the other booth. The diagram is labeled H.430.3(23)_FI.6.](d9c0a780cd22626253dab4aa41699e2f_img.jpg)
+
+Figure I.6: Configuration of the public booth for vibrotactile communication. The diagram shows two identical booths connected by a central 'Communication system' consisting of two 'Terminal' units and a 'Network'. Each booth contains a 'Camera', 'Screens', 'Projectors', a 'Sensor', and a 'Vibrator'. A hand is shown interacting with the 'Vibrator' and 'Sensor' in each booth. Orange arrows labeled 'Vibration' show the flow of data from the sensor in one booth, through the network, to the vibrator in the other booth. The diagram is labeled H.430.3(23)\_FI.6.
+
+**Figure I.6 – Configuration of the public booth for vibrotactile communication**
+
+Figure I.6 shows a pair of booths that connects via a communication system (terminals and network). Each booth has a camera, one round screen, a projector, a vibration sensor and a vibrator. Behind the round screen, a vibrator is attached to provide vibrotactile sense to the user and a vibration sensor to capture vibration generated by the user. In order to avoid vibration howling, a sound equalizer and a howling compressor might be needed. The sound equalizer removes high-frequency vibration signals, where humans cannot feel vibration, and signals of specific frequency bands that cause strong howling by resonant frequency of booth and screen. A compressor controls howling in real time.
+
+NTT Labs demonstrated the public booth for vibrotactile communication in exhibition spaces in Tokyo in 2019. Figure I.7 is an image of the demonstration.
+
+![A person interacting with a large, curved screen displaying a virtual environment, demonstrating vibrotactile communication.](e9a1dfde7b55d69a0a56f5bbe35328d4_img.jpg)
+
+A photograph showing a person from behind, seated at a desk and interacting with a large, curved projection surface. The surface displays a virtual environment where a hand is visible, and there are various objects like cups and a basket on the desk. The person's hands are on the surface, and they appear to be interacting with the virtual content.
+
+A person interacting with a large, curved screen displaying a virtual environment, demonstrating vibrotactile communication.
+
+H.430.3(23)\_FI.7
+
+**Figure I.7 – Demonstration of the public booth for vibrotactile communication**
+
+This demonstration used high-definition video and audio communication system and the Internet. Vibrotactile information was carried by one of two audio channels, which were used for stereo sound transmission, and was fully synchronized with video images. The video signals were carried by a video codec such as one compliant with [b-ITU-T H.264], and the audio and vibrotactile signals were carried by audio codec such as MPEG-4 AAC-LD. The audio and vibrotactile signals can also be carried by MPEG-4 ALS.
+
+This demonstration provided several experiences using vibrotactile information between two users. When seated in front of a booth, user A can see the upper half of the body including the hands of user B, who is seated in front of another booth at a remote site, at actual size on the round screen. In the appropriate areas, both users can see each other's hands and feel vibrations. For example, if user A hits the desk with the hand, user B can hear the sound and feel the vibration simultaneously. This kind of interactive experience makes users feel as if they are seated at the same desk.
+
+In this demonstration, users can also feel vibrations of rolling balls, drawing pictures, and touching and scuffing the screen from the other side.
+
+#### **I.2.12 Use case – Remote surgery**
+
+Based on extremely stringent delay and reliable connectivity, remote surgery is one critical application of telemedicine. As shown in Figure I.8, it involves the patient and auxiliary facility in the local site, and the doctor and holographic stereogram of the patient in a remote site.
+
+![Two side-by-side images illustrating remote surgery. Image (a) shows a robotic arm performing surgery on a patient. Image (b) shows two surgeons in an operating room, with a holographic stereogram of a patient visible on a screen.](082ba09313df59d76a7bfbdde8ec877d_img.jpg)
+
+Two side-by-side photographs. The left photograph (a) shows a robotic arm with multiple joints performing a surgical procedure on a patient lying on a table. The right photograph (b) shows two surgeons in blue surgical gowns and masks standing in an operating room. They are looking at a large screen that displays a holographic stereogram of a patient's torso, showing internal structures.
+
+Two side-by-side images illustrating remote surgery. Image (a) shows a robotic arm performing surgery on a patient. Image (b) shows two surgeons in an operating room, with a holographic stereogram of a patient visible on a screen.
+
+H.430.3(23)\_FI.8
+
+**a) b)**  
+**Figure I.8 – Remote surgery: a) local site; b) remote site**
+
+First, the holographic stereogram of the patient in the local site is generated by holographic technology and captured with the help of cameras and sensors; the result is displayed at the remote site. The remote doctor can view the real-time status (such as pulse count, blood pressure measurements and blood vessel status on the surface of the skin) of the local patient.
+
+Second, the remote doctor performs a series of operations on the holographic stereogram. Haptic information about operations (such as touch and kinaesthesia) is captured by cameras and sensors, converted into control signals and transmitted to local auxiliary facilities (such as mechanical arms) through networks.
+
+Finally, local auxiliary facilities perform represented operations on the local patient and the feedback interactive information is reflected on the remote holographic stereogram in real time. The remote doctor can judge the result and continue to the next.
+
+#### 1.2.13 Use case – Multi-user collaborative design
+
+With advanced 3D display technologies, a design prototype or physical model is represented by a high-resolution 3D image at actual size at different sites, and can be watched or modified by users. Highly realistic image(s) of the user(s) at the event site is or are transferred to the remote site and presented at life size and in real time, and *vice versa*. Figure I.9 is an image of an example of multi-user collaboration for vehicle design. Colleagues who work in the office (event site) can communicate and collaborate with a colleague who works from home (remote site) to interact with the virtual vehicle model.
+
+![Diagram illustrating multi-user collaboration for vehicle design across remote and event sites connected via a network.](a0739aaf13fa5a632d4faa830f6b2708_img.jpg)
+
+The diagram illustrates a multi-user collaborative design environment for a vehicle. At the top, a central 'Network' hub connects two main locations: 'Remote site' (Home A) and 'Event site' (Office B).  
+- **Remote site:** Contains 'Colleague A' and icons for a head-mounted display and a haptic glove. An arrow points from this site to a 'Virtual office B' containing 'Colleague A', 'Virtual B' (a person icon), a 3D car model, and 'Virtual C' (a person icon).  
+- **Event site:** Contains 'Colleague B' and 'Colleague C', along with icons for a head-mounted display, a haptic glove, and a gear. An arrow points from this site to a 'Design model and virtual colleague at office B', which shows 'Virtual A' (a person icon), 'Colleague B', a 3D car model, and 'Colleague C'.  
+- **Vehicle parts:** A speech bubble from 'Colleague B' contains icons for various vehicle components like a steering wheel, engine, and gears.  
+- **Labels:** 'Home A', 'Colleague A', 'Remote site', 'Office B', 'Colleague B', 'Colleague C', 'Event site', 'Virtual office B with colleagues and virtual design model', 'Design model and virtual colleague at office B', 'Network', and 'Vehicle parts'.  
+- **Reference:** H.430.3(23)\_F1.9
+
+Diagram illustrating multi-user collaboration for vehicle design across remote and event sites connected via a network.
+
+**Figure I.9 –Multi-user collaboration**
+
+In the collaborative design process, each user's ideas and operations on the virtual object are tracked and captured via cameras, wearable devices or other accessories, and delivered to other users working at different sites in real-time. Users at the event site can design the virtual object with natural experience, e.g., by moving it, modifying components or attributes, labelling instructions and testing new configurations. The users at the event and remote sites can watch the same virtual object from an arbitrary viewing angle, discuss the design plan and design the virtual object simultaneously. This service provides 3D visualization of the design process, immersive interaction with virtual objects and immersive communication for users in real-time.
+
+#### **I.2.14 Use case – Emergency treatment guidance**
+
+Many injured people die in emergency situations (drowning, heart disease, stroke, etc.) due to lack of appropriate treatment in the first minutes after the event. Guidance is in high demand due to the deficiency of emergency treatment knowledge.
+
+Remote rescue centre professionals can guide on-site people to treat emergencies appropriately in a timely fashion. The operation on the replica of the patient performed by surgeons is captured and presented to people on site, who can then perform the same treatment on a real patient. In addition, if a natural disaster such as an earthquake occurs, trapped people can be guided to treat themselves.
+
+#### **I.2.15 Use case – Remote maintenance guidance**
+
+If faults occur, a customer calls a technical support centre for assistance and is guided by a specialist for maintenance.
+
+An image of the real device is captured at the customer site and transmitted to the support centre. The specialist demonstrates maintenance on the virtual image using voice, action, signs, etc. The demonstration is captured and transmitted to the customer site and represented as if demonstrating on the real device. The customer conducts the same operation on the real device, and any changes of device are synchronously reflected in virtual image. The device is then fixed with the guidance of the specialist.
+
+#### **I.2.16 Use case – Becoming-player sports viewing (NTT West use case)**
+
+In sports viewing, audiences cheer with enthusiasm because they have empathy with players, and player performance can improve through the enthusiastic cheering. "Becoming-player sports viewing" is a new experience, in which audience emotions at viewing sites can be evoked using haptic information from the event site.
+
+One use case is the fencing project that was demonstrated in Numazu-city in Shizuoka, Japan in 2021. In the stadium (event site) for a fencing match at the Roppongi Hills Arena in Tokyo, Japan, six microphones were installed at the side of the piste (on which the match must occur), mainly to capture the sound of a fencer's foot stepping on the piste and the sound of swords colliding with each other. The captured sounds were mixed into two channel audio, and transmitted to Numazu by telecommunication network. This use case involves a sabre match (one of three disciplines in fencing), in which the weapon is used to slash rather than stab, unlike the other two. Thus, the sabres make big sounds and intense vibrations.
+
+Figure I.10 is an image of this use case. At the viewing site in Numazu, two children with experience of sabre stood facing each other in front of the monitor, as if they were in the stadium in Tokyo. The video image captured by the camera in Tokyo was displayed on the monitor at Numazu. The sound from Tokyo was transmitted to the speakers, including output from the vibration platform that the two children stood on and the sword-type vibration device held in their hands. The sound signal from the left channel mix of output from the platform and the device on the left side of the viewing site was sent to one speaker, and the sound signal from the right channel mix was sent to another for the right side. The children were instructed to move their hands while synchronizing to each of the players they were becoming. The video images and sounds from Numazu were sent to the monitor and speakers in Tokyo.
+
+![Figure I.10 – Becoming-player sports viewing. The diagram is split into two panels. The left panel, 'Roppongi hills arena', shows a fencing match on a screen. Below the screen are three pairs of microphones (L-1, R-1; L-2, R-2; L-3, R-3) connected to a 'MIXER'. The mixer outputs 'L-Mix' and 'R-Mix' to a 'TRANSMISSION SYSTEM'. The transmission system connects to a 'CAM' and 'MONITOR' setup, which in turn connects to 'L-SP' (left speaker) and 'R-SP' (right speaker). The right panel, 'F3 BASE (Numazu)', shows two children standing on platforms, holding handles. They are connected to a 'TRANSMISSION SYSTEM' via 'L-MIC' and 'R-MIC'. The transmission system connects to a 'CAM' and 'MONITOR' setup, which shows the fencing match. The children are also connected to 'L-SP' and 'R-SP' speakers. The diagram illustrates a system for immersive sports viewing where users can feel the movements of the players.](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg)
+
+Figure I.10 – Becoming-player sports viewing. The diagram is split into two panels. The left panel, 'Roppongi hills arena', shows a fencing match on a screen. Below the screen are three pairs of microphones (L-1, R-1; L-2, R-2; L-3, R-3) connected to a 'MIXER'. The mixer outputs 'L-Mix' and 'R-Mix' to a 'TRANSMISSION SYSTEM'. The transmission system connects to a 'CAM' and 'MONITOR' setup, which in turn connects to 'L-SP' (left speaker) and 'R-SP' (right speaker). The right panel, 'F3 BASE (Numazu)', shows two children standing on platforms, holding handles. They are connected to a 'TRANSMISSION SYSTEM' via 'L-MIC' and 'R-MIC'. The transmission system connects to a 'CAM' and 'MONITOR' setup, which shows the fencing match. The children are also connected to 'L-SP' and 'R-SP' speakers. The diagram illustrates a system for immersive sports viewing where users can feel the movements of the players.
+
+Figure I.10 – Becoming-player sports viewing
+
+As a result, children felt as if they were standing in the stadium in Tokyo due to the vibrations of their feet, and at the same time, they felt as if vibrations were occurring in their hands in response to their movements. They were able to feel the physical movements of the players, such as footwork and swordplay, and reproduce them through their own bodies.
+
+After the demonstration, the children's impressions were, "I was happy to win", and, "I was disappointed to lose", so the children talked about winning and losing as if they had become players themselves.
+
+### I.3 Configuration of ILE
+
+If transmitting a soccer game to gymnasiums for example, there is a big difference in the sizes of venues as well as the sound and lighting equipment. Figure I.11 shows a configuration of Kirari! as an example of an ILE service, in order to reconstruct the atmosphere of a soccer stadium in a remote site. The following approaches can achieve highly realistic sensations as if audiences in a gymnasium had entered a soccer stadium.
+
+- 1) Objects such as soccer players are measured in  $(x, y, z)$  coordinates and are extracted images in real time at the stadium. In order to reconstruct the extracted objects in the gymnasium, information about the object is transmitted in real time.
+- 2) Video, audio and lighting information, except for objects previously described, is also transmitted to gymnasiums after transforming information based on the data of the hall environment such as the width and height of screens, the number of projectors, the types of audio equipment and characteristics of the lighting equipment. This transforming function calculates parameters from the gymnasium environmental data to reconstruct the atmosphere of the stadium at remote sites. For example, the following are the actual parameters: i)  $(x, y, z)$  coordinates of objects; ii) range of captured environmental and spatial information except for objects; iii) region of sound space.
+- 3) At remote sites, environmental information is reconstructed by projection mapping technology. Then another projector shows objects in 3D and numerous speakers reconstruct the audio space and auditory lateralization.
+
+![Figure I.11: Configuration of Kirari! showing the flow from Event venue to Media synchronization for high-realistic sense to Viewing sites.](8c348bf9c2c81b018017ae1d19506a9a_img.jpg)
+
+The diagram illustrates the configuration of Kirari! for a soccer match. On the left, an 'Event venue' shows a soccer match. Arrows point to a central box labeled 'Media synchronization for high-realistic sense'. This box contains three sections: (i) 'Extraction objects' with a soccer player and the function  $f(x, y, z)$ ; (ii) 'Environmental and spatial info' with a soccer goal; and (iii) 'Sound space info' with multiple speaker icons. Arrows from this box point to 'Viewing sites', represented by a grid of screens. Above the viewing sites is a callout box with technical specifications: 'Size: 10 m × 5 m × 5 m', 'Projector: 4K × 4', 'Speaker: 5.1 ch', 'light: 5', and '....'. The text 'H.430.3(23)\_FI.11' is at the bottom right.
+
+Figure I.11: Configuration of Kirari! showing the flow from Event venue to Media synchronization for high-realistic sense to Viewing sites.
+
+**Figure I.11 – Configuration of Kirari!**
+
+As shown in Figure I.12, audiences in remote sites can feel ultra-highly realistic sensations by pseudo-3D projection and auditory lateralization of Kirari! Audiences experience emotions as though they are watching actual events, exceeding those provided by 2D displays. Kirari! provides new experiences for audiences.
+
+![Figure I.12: Reconstruction atmosphere of event venue at viewing site showing a 3D projection of a soccer match with an audience.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg)
+
+The diagram shows a 'Viewing site' (represented by a grid of screens) projecting a 3D image of a soccer match. An audience is shown watching the projection. Below the audience, a callout box contains the text 'Reconstruct images fitting sizes or environments of viewing sites'. The text 'H.430.3(23)\_FI.12' is at the bottom right.
+
+Figure I.12: Reconstruction atmosphere of event venue at viewing site showing a 3D projection of a soccer match with an audience.
+
+**Figure I.12 – Reconstruction atmosphere of event venue at viewing site**
+
+### I.4 Candidate technologies used for ILE
+
+Candidate technologies used in ILE that aim to realize pseudo 3D presentations in real time are described in this clause and include highly realistic media synchronization, real-time object image extraction, highly realistic auditory lateralization and extra-wide video stitching technologies.
+
+#### (1) Highly realistic media synchronization
+
+The MPEG media transport (MMT) technology has features that synchronize video and audio streams by using absolute time management. However, it is necessary to synchronize several elements such as lighting and spatial information to reconstruct a virtual field of the event venue at remote sites. A signalling descriptor of MMT is required to model spatial information such as size of objects, positional relations and direction of sounds.
+
+By using this technology, it is possible to handle asset information related to physical spatial position information such as the size of screen, resolution of displays and spatial position. Using the transmitted spatial size of images and auditory lateralization information together with multiple audio and video streams constituting the event venue, a virtual field of the event
+
+venue can be reconstructed highly realistically at the viewing site, depending on its specifications.
+
+For IISs, interactive media require multiple concurrent streams to be delivered. Coordination and synchronization of multiple concurrent streams is a key technology to control their establishment, synchronization and reconstruction according to specific scenarios and service policies.
+
+#### (2) Real-time object image extraction
+
+Real-time object image extraction is a key technology to realize live experience, and extracted objects are displayed as pseudo-3D images at the viewing site. This may be achieved by a combination of contour detection technology using sensor information such as distance and temperature, and image-processing technology, which identifies boundaries of target objects at high speed and in high resolution. Real-time image extraction can clip purely the target object to be presented as a pseudo-3D image at the viewing site.
+
+#### (3) Highly realistic auditory lateralization
+
+Highly realistic auditory lateralization aims to reconstruct a virtual acoustic field over a wide viewing area. This enables sound direction from actual-sized objects projected on to wide screens to be reproduced, thus audiences can feel voice and sound as if they come from the projected objects.
+
+#### (4) Extra-wide video stitching
+
+Video-stitching technology pieces together processed video images of multiple high-definition cameras, adjusts the images and enables highly realistic field images to be reconstructed in real time for major sports venues, and track and field events such as athletics.
+
+#### (5) Intelligent distribution technology of massive multimedia data
+
+Intelligent distribution technology of massive multimedia data aims to select appropriate media processing servers in accordance with the requirements of codec, compression and rendering.
+
+#### (6) Network status awareness and quality of service scheduling
+
+Network status awareness and quality of service (QoS) scheduling aim to guarantee the quality of experience of IISs. Network status awareness is the capability to collect QoS and network resource information. QoS scheduling is the capability to update policies based on the collected information.
+
+### **I.5 Standards gap analysis of ILE related technologies**
+
+#### **I.5.1 ITU-T work**
+
+There exist several Recommendations related to Internet protocol television (IPTV) services. For example, IPTV architecture [b-ITU-T Y.1910], establishes the reference model and function blocks. However, there are no specifications about immersive services in those IPTV-related Recommendations.
+
+#### **I.5.2 ISO/IEC JTC1 SC29 (MPEG) work**
+
+ISO/IEC JTC1 SC29, MPEG, has been working with ITU-T SG16 on video codecs for many years. MPEG has developed media transport technologies called MMT. Media coding technology called visual volumetric video-based coding (V3C) has been developed by MPEG as well.
+
+##### **ISO/IEC 23008-1**
+
+[b-ISO/IEC 23008-1], which was developed in MPEG, gives an MMT overview, and extends existing media transport technologies such as MPEG2-TS [b-ITU-T H.222.0] and specifies multi-source content delivery. This enables synchronous media transmission between video and sound, but
+
+transporting special environment information is not considered in [b-ISO/IEC 23008-1]. In other words, MMT cannot resolve synchronous media transportation.
+
+##### **ISO/IEC 23008-11**
+
+MPEG has also developed [b-ISO/IEC 23008-11], which is a composition information (CI) specification of terminal devices. Display of a real-sized object needs to be considered as CI; however, [b-ISO/IEC 23008-11] does not cover spatial environments such as bezel size of display devices and spatial position information. Therefore, CI is inefficient for displaying actual-sized objects.
+
+##### **MPEG-I Project**
+
+From the systems perspective, the MPEG-I project has laid out a basic foundation of coding, signalling, encapsulation and delivery formats for both mono and stereoscopic 360° video and audio in omnidirectional media format (OMAF) in its initial phase. However, a rich set of features in immersive media including 6DoF, point clouds, light fields that could enhance new use cases is set to be further explored in the next phase.
+
+##### **ISO/IEC 23090-2**
+
+[b-ISO/IEC 23090-2], which was developed in MPEG, specifies the OMAF for coding, storage, delivery and rendering of omnidirectional media, including video, images, audio and timed text. An omnidirectional image or video can contain graphics elements generated by computer graphics but encoded as image or video. Multiple viewpoints, each corresponding to an omnidirectional camera, are supported. [b-ISO/IEC 23090-2] also specifies storage and delivery of overlay images or video intended for rendering over an omnidirectional background image or video.
+
+##### **ISO/IEC 23090-5**
+
+[b-ISO/IEC 23090-5], which was developed in MPEG, specifies the syntax, semantics and decoding for visual volumetric media using video-based coding methods. [b-ISO/IEC 23090-5] also specifies processes that can be needed for reconstruction of visual volumetric media, which can also include additional processes such as post-decoding, pre-reconstruction, post-reconstruction and adaptation. This enables the coding and processing for holographic images.
+
+#### **I.5.3 ISO work**
+
+##### **ISO 9241-910**
+
+[b-ISO 9241-910] provides a framework for understanding and communicating various aspects of tactile or haptic interaction. [b-ISO 9241-910] defines terms, describes structures and models, and gives explanations related to the other parts of the ISO 9241-9XX subseries. [b-ISO 9241-910] also provides guidance on how various forms of interaction can be applied to a variety of user tasks. [b-ISO 9241-910] applies to all types of interactive systems making use of tactile/haptic devices and interactions. [b-ISO 9241-910] does not address purely kinaesthetic interactions such as gestures.
+
+#### **I.5.4 Institute of Electrical and Electronics Engineers work**
+
+In March 2016, the Institute of Electrical and Electronics Engineers (IEEE) Standards Association approved the creation of the IEEE P1918.1 standards working group. The core activities of the working group can be classified into three distinct areas: 1) definitions and use-cases; 2) haptic codecs; and 3) reference architectural framework.
+
+Ongoing IEEE activity on haptic codecs for the tactile internet [b-IEEE P1918.1.1] is attempting to standardize the first kinaesthetic codec. [b-IEEE P1918.1.1] focuses on standardization of a corresponding tactile codec. [b-IEEE P1918.1] and [b-IEEE P1918.1.1] draft standards were planned for completion in 2019. However, there is no codec standard published at the time of publication.
+
+#### **I.5.5 Work in broadcasting area**
+
+In the broadcasting standardization area, standardization of media transport technologies has been started.
+
+##### **Association of Radio Industries and Business**
+
+[b-ARIB STD-B60] is a media transport standard based on MMT and [b-ISO/IEC 23008-1]. [b-ARIB STD-B60] aims to enhance terrestrial broadcasting services. However, as shown in clause I.6.2, [b-ARIB STD-B60] does not specify synchronous media transportation.
+
+##### **ITU-R**
+
+ITU-R has started considering new media transport technologies based on ARIB B-60. This work is not yet finalized.
+
+#### **I.5.6 Work in cinema area**
+
+Today, four dimensional (4D) cinemas that provide highly realistic sensation for users have been developed and deployed all over the world. 4D means that the user can sense several feelings such as vibration of seats, lighting and smell in addition to 3D video and surround sound. 4D cinemas can only be provided at specific theatres that are equipped with special devices, with special programmes that are designed for 4D. Moreover, a 4D cinema does not have live content transmission capability.
+
+On the other hand, there exist several 4D cinema technologies such as 4DX and MX4D, but there are no standards so far.
+
+Therefore, ILE services cannot be covered by this area.
+
+#### **I.5.7 Standardization gaps**
+
+Standardization of terminal devices decreases the cost of highly realistic IPTV services and standardization of the transmission issue provides interoperability between providers of services and content.
+
+As previously mentioned, standardization of all key features of ILE services has not progressed, so it is necessary to start standardization work in ITU-T.
+
+## Bibliography
+
+- [b-ITU-T H.222.0] Recommendation ITU-T H.222.0 (2023), *Information technology – Generic coding of moving pictures and associated audio information: Systems: Various corrections and updates.*
+- [b-ITU-T H.264] Recommendation ITU-T H.264 (2021), *Advanced video coding for generic audiovisual service.*
+- [b-ITU-T H.430.1] Recommendation ITU-T H.430.1 (2018), *Requirements for immersive live experience (ILE) services.*
+- [b-ITU-T Y.1910] Recommendation ITU-T Y.1910 (2008), *IPTV functional architecture.*
+- [b-ISO 9241-910] ISO 9241-910:2011, *Ergonomics of human-system interaction – Part 910: Framework for tactile and haptic interaction.*
+- [b-ISO/IEC 23008-1] International Standard ISO/IEC 23008-1:2023, *Information technology – High efficiency coding and media delivery in heterogeneous environments – Part 1: MPEG media transport (MMT).*
+- [b-ISO/IEC 23008-11] International Standard ISO/IEC 23008-11:2015, *Information technology – High efficiency coding and media delivery in heterogeneous environments – Part 11: MPEG media transport composition information.*
+- [b-ISO/IEC 23090-2] International Standard ISO/IEC 23090-2:2023, *Information technology – Coded representation of immersive media – Part 2: Omnidirectional media format.*
+- [b-ISO/IEC 23090-5] International Standard ISO/IEC 23090-5:2023, *Information technology – Coded representation of immersive media – Part 5: Visual volumetric video-based coding (V3C) and video-based point cloud compression (V-PCC).*
+- [b-IEEE P1918.1] IEEE P1918.1, *IEEE Draft Standard for tactile Internet: Application scenarios, definitions and terminology, architecture, functions, and technical assumptions.*
+- [b-IEEE P1918.1.1] IEEE P1918.1.1, *IEEE Draft Standard for haptic codecs for the tactile Internet.*
+- [b-ARIB STD-B60] Association of Radio Industries and Businesses Standard ARIB STD-B60 version 1.14 (2019), *MMT-based media transport scheme in digital broadcasting systems.* Available [viewed 2023-11-20] at: [https://www.arib.or.jp/english/html/overview/doc/6-STD-B60\\_v1\\_14-E1.pdf](https://www.arib.or.jp/english/html/overview/doc/6-STD-B60_v1_14-E1.pdf)
+- [b-KT PC] Chosunbiz (2016). *Kt기자간담회.. 5G 홀로그램라이브* [KT press conference. 5G hologram live]. San Bruno, CA: Youtube. Available [viewed 2023-11-20] at: <https://www.youtube.com/watch?v=cJgo-b4aEjE>
+- [b-NTT JKF] SHOCHIKUch (2016). *『KABUKI LION 獅子王』遠隔舞台挨拶in Las Vegas.* [Japan Kabuki Festival in Las Vegas 2016]. San Bruno, CA: Youtube. Available [viewed 2023-11-20] at: <https://www.youtube.com/watch?v=E0D67sBsCY0>.
+- [b-NTT Krause] Krause, J. (2017). *Cyber teleportation Tokyo at SXSW.* Austin, TX: SXSW. Available [viewed 2023-11-21] at: <https://www.sxsw.com/news/2017/cyber-teleportation-tokyo-at-sxsw/>
+
+- [b-NTT ICC] Intercommunication Center (2023). *Public booth for vibrotactile communication*. Tokyo: Intercommunication Center. Available [viewed 2023-11-20] at: <https://www.ntticc.or.jp/en/archive/works/public-booth-for-vibrotactile-communication/>
+- [b-Sohn] Sohn Ji-young (2018). Hard to follow cross-country skiing? 5G is here to help. *The Korea Herald*. Seoul: Herald Corporation. Available [viewed 2023-11-20] at: <http://www.koreaherald.com/view.php?ud=20180213001003>
+- [b-Tektonspace] Tektonspace (2017). *VR walk through*. San Bruno, CA: Youtube. Available [viewed 2023-11-20] at: <https://www.youtube.com/watch?v=EUDTTLNLfDo>
+
+
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/H/T-REC-H.430.7-202309-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477
--- /dev/null
+++ b/marked/H/T-REC-H.430.7-202309-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.7-202309-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/H/T-REC-H.430.7-202309-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e43dfe1dd929ef37c23f69cfaa953b65c1ea9a39
--- /dev/null
+++ b/marked/H/T-REC-H.430.7-202309-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4d73912861c3ce69c7671fe7b8ab63919892ea06b77dd5ff166cae5be2745876
+size 81781
diff --git a/marked/H/T-REC-H.460.10-200403-I_PDF-E/raw.md b/marked/H/T-REC-H.460.10-200403-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..9090689bbaa0524277621a5a8de73764e098f1a5
--- /dev/null
+++ b/marked/H/T-REC-H.460.10-200403-I_PDF-E/raw.md
@@ -0,0 +1,241 @@
+
+
+![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.10**
+
+(03/2004)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS  
+Infrastructure of audiovisual services – Supplementary  
+services for multimedia
+
+---
+
+**Call party category within H.323 systems**
+
+ITU-T Recommendation H.460.10
+
+---
+
+# 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        |
+| <b>Supplementary services for multimedia</b>                                  | <b>H.450–H.499</b> |
+| 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.10**
+
+## **Call party category within H.323 systems**
+
+## **Summary**
+
+This Recommendation specifies a mechanism that allows calling H.323 endpoints to signal calling party category information in the forward direction, and allows called H.323 endpoints to signal called party category information in the backward direction.
+
+###### **Source**
+
+ITU-T Recommendation H.460.10 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 Call party category.....                          | 2    |
+| 4 Call party category info parameter .....          | 2    |
+| 4.1 Call party category info ASN.1 definition ..... | 3    |
+| 4.2 Description of ASN.1 types and fields .....     | 3    |
+
+
+
+## Call party category within H.323 systems
+
+# 1 Scope
+
+A calling party's category (CPC) parameter is defined by ISUP that describes the nature of the calling party, e.g., operator language, test call, payphone, etc. In addition, a called party category indicator is included in the ISUP backward call indicators parameter. ISUP variants used in some regional networks (in North America) define an originating line information (OLI) parameter to carry this information instead of the CPC parameter. R2 signalling uses the Group II forward signals to carry similar information. ITU-T Rec. H.450.12 defines a partyCategory field that identifies the category of either the calling party or the called party involved in the call.
+
+This information would be very useful for making routing and accounting decisions within the H.323 network. A mechanism is, therefore, required to support the signalling of the calling party category in H.323 networks.
+
+A calling endpoint should be able to signal calling party category information in the forward direction. The calling party category parameter may be included in Setup, ARQ and LRQ messages. H.323 devices, gateways, gatekeepers and border elements may apply routing and accounting policies based on the value of the calling party category.
+
+A called endpoint should be able to signal called party category information in the backward direction. The called party category parameter may be included in progress, alerting or connect messages. H.323 devices, gateways, gatekeepers and border elements may apply routing and accounting policies based on the value of the called party category.
+
+This Recommendation specifies a mechanism that allows calling H.323 endpoints to signal calling party category information in the forward direction and allows called H.323 endpoints to signal called party category information in the backward direction.
+
+## 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 Q.763 (1999), *Signalling System No. 7 – ISDN user part formats and codes plus Amendment 2 (2002), Support for the International Emergency Preference Scheme*.
+- ITU-T Recommendation H.460.4 (2002), *Call priority designation for H.323 calls*.
+- ANSI T1.113-2000<sup>1</sup>, *Signalling System No. 7 (SS7) – Integrated Services Digital Network (ISDN) User Part*.
+
+---
+
+<sup>1</sup> T1 standards are maintained since November 2003 by ATIS.
+
+# 3 Call party category
+
+The call party category parameter is used to transport calling party category information in messages sent by the calling H.323 endpoint in the forward direction, and to transport called party category information in messages sent by the called H.323 endpoint in the backward direction. If the calling party category has the value of the International Emergency Preference Scheme (IEPS), then the use of H.460.4 procedures is not precluded.
+
+A H.323 endpoint or gatekeeper may include the call party category parameter in H.225.0 RAS and call signalling (Q.931) messages using the generic extensibility framework.
+
+When sending the call party category parameter in the call signalling messages, it shall be coded in the genericData parameter in the H.225.0 H323-UU-PDU in the user-user information element.
+
+When sending the call party category parameter in the RAS messages, it shall be coded in the genericData parameter in the request parameter of the H.225.0 RAS Message.
+
+The GenericData parameter indicates the callPartyCategory feature and contains a callPartyCategory parameter.
+
+Table 1 defines the call party category feature.
+
+**Table 1/H.460.10 – Call party category feature**
+
+|                           |                                                                                                                                      |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------|
+| Feature name:             | Call party category                                                                                                                  |
+| Feature Description:      | This feature allows a H.323 endpoint to include calling party category or called party category information in a signalling message. |
+| Feature identifier type:  | Standard                                                                                                                             |
+| Feature identifier value: | 10                                                                                                                                   |
+
+## 4 Call party category info parameter
+
+Table 2 defines the call party category info parameter.
+
+**Table 2/H.460.10 – Call party category info parameter**
+
+|                             |                                                                                                                                                                                                                                    |
+|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Parameter name:             | Call party category info                                                                                                                                                                                                           |
+| Parameter description:      | The call party category information parameter is the data sent in H.225.0 RAS and call signalling messages. The content is a raw field consisting of the ASN.1 PER encoded CallPartyCategoryInfo as specified in the ASN.1 in 4.1. |
+| Parameter identifier type:  | Standard                                                                                                                                                                                                                           |
+| Parameter identifier value: | 1                                                                                                                                                                                                                                  |
+| Parameter type:             | Raw                                                                                                                                                                                                                                |
+| Parameter cardinality:      | Once and only once                                                                                                                                                                                                                 |
+
+### 4.1 Call party category info ASN.1 definition
+
+The call party category info definition used within the GenericData is shown below.
+
+```
+CALL-PARTY-CATEGORY DEFINITIONS AUTOMATIC TAGS ::=
+BEGIN
+
+CallPartyCategoryInfo ::= SEQUENCE
+{
+    callPartyCategory           CallPartyCategory OPTIONAL,
+    originatingLineInfo         OriginatingLineInfo OPTIONAL,
+    ...
+}
+
+CallPartyCategory ::= INTEGER (0..255)
+
+OriginatingLineInfo ::= INTEGER (0..255)
+
+END
+```
+
+### 4.2 Description of ASN.1 types and fields
+
+**CallPartyCategoryInfo** – The H.323 endpoint may include this field to signal the calling or called party category or originating line information parameters in call signalling or RAS messages.
+
+**CallPartyCategory** – The H.323 endpoint may include this field to signal the calling or called party category information in call signalling or RAS messages. The contents are values that are defined in ITU-T Rec. Q.763 (1999) and its Amendment 2 (2002).
+
+**OriginatingLineInfo** – The calling H.323 endpoint may include this field to signal the originating line information parameter in call signalling or RAS messages. The contents are values that are defined in ANSI T1.113.3-2000, Annex C.
+
+
+
+
+
+# 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                                                                   |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                      |
+| 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.11-200403-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.460.11-200403-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5d265b0b1d801b68a1811f50255d4ce309cea099
--- /dev/null
+++ b/marked/H/T-REC-H.460.11-200403-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:83e288ae149cd15c33d4d0054115c536d5a200511f364537b2fb9fabaea4aeaa
+size 8235
diff --git a/marked/H/T-REC-H.460.11-200403-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/H/T-REC-H.460.11-200403-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..27721883368d8ca4bb6566bd268635f87f10c758
--- /dev/null
+++ b/marked/H/T-REC-H.460.11-200403-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:54828c4afa00b38678a0f82662a5ff56205a627b52cc890244974c1c0b33f052
+size 126457
diff --git a/marked/H/T-REC-H.460.11-200403-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/H/T-REC-H.460.11-200403-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7c3920ae0670c2efdd6bcba3d013475f356506e0
--- /dev/null
+++ b/marked/H/T-REC-H.460.11-200403-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:30a17197fe796b0fe98093c8d2a7d883f996832f83cd34e5ad505936af9209e8
+size 95280
diff --git a/marked/H/T-REC-H.460.13-200403-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/H/T-REC-H.460.13-200403-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c03eb88b810c3f4de18cef0319ae881a650ca448
--- /dev/null
+++ b/marked/H/T-REC-H.460.13-200403-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5162dcf5e639b026f1734d65454d78cd87307a11867fb2cdbcc5a372dc0b51b8
+size 34354
diff --git a/marked/H/T-REC-H.460.13-200403-I_PDF-E/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg b/marked/H/T-REC-H.460.13-200403-I_PDF-E/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7a7d59465dfe9ff04f51092dbda64a3a7ee4d83c
--- /dev/null
+++ b/marked/H/T-REC-H.460.13-200403-I_PDF-E/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8aadb5bd766f791cdb5706ddc1b7f0e0b13155460e00ab0ba29e1f5a307eee1f
+size 28250
diff --git a/marked/H/T-REC-H.460.13-200403-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.460.13-200403-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5d265b0b1d801b68a1811f50255d4ce309cea099
--- /dev/null
+++ b/marked/H/T-REC-H.460.13-200403-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:83e288ae149cd15c33d4d0054115c536d5a200511f364537b2fb9fabaea4aeaa
+size 8235
diff --git a/marked/H/T-REC-H.460.13-200403-I_PDF-E/e1a0d046fbe7f28f5e93a47091851747_img.jpg b/marked/H/T-REC-H.460.13-200403-I_PDF-E/e1a0d046fbe7f28f5e93a47091851747_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..49c8750402ceddbb5a298f951854a3f0c6c2e0a0
--- /dev/null
+++ b/marked/H/T-REC-H.460.13-200403-I_PDF-E/e1a0d046fbe7f28f5e93a47091851747_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:852f651dde49ec94f85ee1aa14cc2d99555005a364572854ef8940b60aed861c
+size 36284
diff --git a/marked/H/T-REC-H.460.14-200403-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.460.14-200403-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5d265b0b1d801b68a1811f50255d4ce309cea099
--- /dev/null
+++ b/marked/H/T-REC-H.460.14-200403-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:83e288ae149cd15c33d4d0054115c536d5a200511f364537b2fb9fabaea4aeaa
+size 8235
diff --git a/marked/H/T-REC-H.460.14-200403-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg b/marked/H/T-REC-H.460.14-200403-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aa0aa38f037188eb74755fccd7f4bbf5105dd79d
--- /dev/null
+++ b/marked/H/T-REC-H.460.14-200403-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e0a08e136e5e33daa54fa8835df51a6aa1975414e167fd8717f850853c9d308e
+size 55889
diff --git a/marked/H/T-REC-H.460.14-200403-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/H/T-REC-H.460.14-200403-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ab4de58b13dd834604949115bea8130d063eacc0
--- /dev/null
+++ b/marked/H/T-REC-H.460.14-200403-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4969e7a2c3f6ffeabaae870119de13d76cf5f3f1a1825e6e2d64739e6bc9decf
+size 39338
diff --git a/marked/H/T-REC-H.460.14-200403-I_PDF-E/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/marked/H/T-REC-H.460.14-200403-I_PDF-E/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..38e6baaa6f629a874d4f27a50b746d7cbcfbf58d
--- /dev/null
+++ b/marked/H/T-REC-H.460.14-200403-I_PDF-E/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:57d3a57831ed3a7e0f9a2fa10901f6de5097f71f1e39f65293e185a83f7e9d65
+size 51299
diff --git a/marked/H/T-REC-H.460.14-200403-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/H/T-REC-H.460.14-200403-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5c13e6c44836a7555569aa3450877e1ad9c40a82
--- /dev/null
+++ b/marked/H/T-REC-H.460.14-200403-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ddac8d7ec3061764e8e7c51478829cefdafcac6a37f52e23f9cd46856ab8a7d1
+size 110994
diff --git a/marked/H/T-REC-H.460.14-200403-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/H/T-REC-H.460.14-200403-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2bf45160fd513636b51823da4fccff9f8636e0f1
--- /dev/null
+++ b/marked/H/T-REC-H.460.14-200403-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c5509bff6d875ae12341e1d2fac542ac5ccabc6c0541f93dd549110708abf419
+size 76589
diff --git a/marked/H/T-REC-H.460.14-200403-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/H/T-REC-H.460.14-200403-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f3176422af53a11fe1952b1b7f70fc9542de26f1
--- /dev/null
+++ b/marked/H/T-REC-H.460.14-200403-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:edac22b7870327aeb28aaf10e74c0f58682b909942eed8ea91855acfb6135d8c
+size 42931
diff --git a/marked/H/T-REC-H.460.14-200403-I_PDF-E/990567efebf979be51f56d1150012c9d_img.jpg b/marked/H/T-REC-H.460.14-200403-I_PDF-E/990567efebf979be51f56d1150012c9d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64c502288f11b7a71039f255d21ce96c253b2d9c
--- /dev/null
+++ b/marked/H/T-REC-H.460.14-200403-I_PDF-E/990567efebf979be51f56d1150012c9d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7793bc5f99025ba5239679541844da4b483ac22fb668f0430fa13cdb15ba7152
+size 84292
diff --git a/marked/H/T-REC-H.460.14-200403-I_PDF-E/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg b/marked/H/T-REC-H.460.14-200403-I_PDF-E/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..09399cb96563c3d6718e1b37ec0fc6bd0159bde9
--- /dev/null
+++ b/marked/H/T-REC-H.460.14-200403-I_PDF-E/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c9740910feadcb15219b593bcf8ff2efc9066996a3ddb718e86fbb556e15db0b
+size 42636
diff --git a/marked/H/T-REC-H.460.14-200403-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/H/T-REC-H.460.14-200403-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8af74ef74f0cb078894c303106aa7dd3daeeca6f
--- /dev/null
+++ b/marked/H/T-REC-H.460.14-200403-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a2dda27c52c99ac0d1b53dd4fcd0f3bc98119d319ef6ef2ae9ddd504308a8b1f
+size 23197
diff --git a/marked/H/T-REC-H.460.14-200403-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/H/T-REC-H.460.14-200403-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3f5d8f3a6262a0e94dda6590ce73e5fbe2389f52
--- /dev/null
+++ b/marked/H/T-REC-H.460.14-200403-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8f97712ae9e7a2999c829274569b926e01deebfe871a461080cf68748c2ff707
+size 182199
diff --git a/marked/H/T-REC-H.460.14-200403-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/H/T-REC-H.460.14-200403-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6777ae4d9ca9f15413a79004391d0c1380a59a1e
--- /dev/null
+++ b/marked/H/T-REC-H.460.14-200403-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a9bb3cb22c2a6ecb73bcf8aa058026513eb563d640517ec53628eb644e1a45e9
+size 111941
diff --git a/marked/H/T-REC-H.460.14-200403-I_PDF-E/c9d8a18a6137ad054b841d7a614afb48_img.jpg b/marked/H/T-REC-H.460.14-200403-I_PDF-E/c9d8a18a6137ad054b841d7a614afb48_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aa6e296a035985a7e6bee434803fff09232728db
--- /dev/null
+++ b/marked/H/T-REC-H.460.14-200403-I_PDF-E/c9d8a18a6137ad054b841d7a614afb48_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0dcfa2f0b6b084d7cf6c4b7531739cc274310da0709d7e7c510e928be289620f
+size 19899
diff --git a/marked/H/T-REC-H.460.14-200403-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/H/T-REC-H.460.14-200403-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..542ecc2d90e47452a0ace8e3204f1637f8940d6b
--- /dev/null
+++ b/marked/H/T-REC-H.460.14-200403-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:978dda45d20a419e7ed8c09bd5fdd121d176060b1a1a9063a425fff09ba004b3
+size 102654
diff --git a/marked/H/T-REC-H.460.14-200403-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/H/T-REC-H.460.14-200403-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fb50b118e8286c777e34df6959291fe15b191203
--- /dev/null
+++ b/marked/H/T-REC-H.460.14-200403-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:139d2d6f408765028e956a9ecebdcc0270170d2d890ed08176037cd511989d5c
+size 121515
diff --git a/marked/H/T-REC-H.460.14-200403-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/H/T-REC-H.460.14-200403-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6df4aaf49b2363b71f42f191be60cb4c4c31b51c
--- /dev/null
+++ b/marked/H/T-REC-H.460.14-200403-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:35f6de02bafafaca96663a01bb6b76ffe80cfa6465a572defe87e4761943ce77
+size 28607
diff --git a/marked/H/T-REC-H.460.14-200403-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/H/T-REC-H.460.14-200403-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..32da80e05179ca043b95823e7201c247bc61cb74
--- /dev/null
+++ b/marked/H/T-REC-H.460.14-200403-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:125ba806b32dfd46673ddfac810069371c52502857076633a98af6c61b191e72
+size 43297
diff --git a/marked/H/T-REC-H.460.14-200403-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg b/marked/H/T-REC-H.460.14-200403-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3122e260cceed9d081b44da1ba04fbe46d18fe8e
--- /dev/null
+++ b/marked/H/T-REC-H.460.14-200403-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1dff19a052f62e41750c76dcdacba8f8524438db2cfa726e7e7af2ba9ffcbeec
+size 88398
diff --git a/marked/H/T-REC-H.460.16-200501-I_PDF-E/raw.md b/marked/H/T-REC-H.460.16-200501-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a19bf189d2466a151ee0c3be9da9b3f58cd65b91
--- /dev/null
+++ b/marked/H/T-REC-H.460.16-200501-I_PDF-E/raw.md
@@ -0,0 +1,466 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.460.16**
+
+(01/2005)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Supplementary  
+services for multimedia
+
+---
+
+**Multiple-message release sequence capability  
+within H.323 systems**
+
+ITU-T Recommendation H.460.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        |
+| <b>Supplementary services for multimedia</b>                                  | <b>H.450–H.499</b> |
+| 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.16**
+
+# **Multiple-message release sequence capability within H.323 systems**
+
+## **Summary**
+
+This Recommendation specifies a mechanism that allows H.323 endpoints to negotiate and use a multiple-message release sequence.
+
+###### **Source**
+
+ITU-T Recommendation H.460.16 was approved on 8 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 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 2005
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## CONTENTS
+
+|     |                                                                         |   |
+|-----|-------------------------------------------------------------------------|---|
+| 1   | Scope .....                                                             | 1 |
+| 2   | References.....                                                         | 1 |
+| 3   | Introduction .....                                                      | 1 |
+| 4   | Feature description.....                                                | 2 |
+| 4.1 | H.501 signalling .....                                                  | 2 |
+| 4.2 | RAS signalling.....                                                     | 2 |
+| 4.3 | Call signalling – negotiation.....                                      | 2 |
+| 4.4 | Call signalling – release.....                                          | 4 |
+| 4.5 | Call signalling timers.....                                             | 4 |
+| 5   | Generic data usage.....                                                 | 5 |
+| 5.1 | Multiple-message release sequence feature.....                          | 5 |
+| 5.2 | Multiple-message release sequence parameters .....                      | 5 |
+| 6   | Message flows .....                                                     | 6 |
+| 6.1 | Three-message sequence .....                                            | 6 |
+| 6.2 | Time-outs.....                                                          | 7 |
+| 6.3 | Two-message sequence .....                                              | 7 |
+| 6.4 | Simultaneous initiation of two-message MMRS procedure.....              | 8 |
+| 6.5 | Simultaneous initiation of two- and three-message MMRS procedures ..... | 8 |
+| 6.6 | Simultaneous initiation of MMRS and H.225.0 procedures .....            | 9 |
+
+
+
+# Multiple-message release sequence capability within H.323 systems
+
+# 1 Scope
+
+This Recommendation specifies a mechanism, using the generic extensibility framework defined in ITU-T Rec. H.460.1, which allows endpoints to use a multiple-message release sequence rather than the single release complete message procedure defined in ITU-T Rec. H.225.0. It includes the capability for one endpoint to inform the other that it supports and will use the alternate multiple-message release sequence.
+
+# 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 Q.931 (1998), *ISDN user-network interface layer 3 specification for basic call control*.
+
+# 3 Introduction
+
+The call control signalling defined in ITU-T Rec. H.225.0 is based on Q.931 signalling. ITU-T Rec. Q.931 defined a multiple-message sequence to be used between the user and the network to control release of a connection. This used the disconnect message from the user as a request to release a connection, and then the release and release complete messages to actually release the connection. This allowed additional information to be passed in both directions during the disconnect process and allowed the initiator of the disconnect to supervise the operation and to retransmit the request in case of failure.
+
+ITU-T Rec. H.225.0 does not use the disconnect and release messages and, therefore, depends on a single message without acknowledgement by the application. While this suffices for many cases, some applications require the functionality of a multiple-message sequence for release of a connection. Further, an occasional loss of the release complete message could cause significant problems.
+
+This Recommendation, using the generic extensibility framework, provides the capability with H.225.0 of performing the multiple-message release sequence of a connection in a way that is analogous to Q.931. The H.225.0 facility message is used for the additional messages of the sequence, with the addition of the GEF parameter defined herein to distinguish its place and function in the sequence.
+
+The multiple-message release sequence may be used to provide additional capabilities such as:
+
+- 1) supervision of acknowledgement of release and repetition in case of failure;
+- 2) inclusion of supplemental information in both directions during the release procedure;
+
+- 3) provision of in-band tones and announcements;
+- 4) full coordination of release of resources;
+- 5) called user release control.
+
+# 4 Feature description
+
+## 4.1 H.501 signalling
+
+When a Gatekeeper uses the H.501 access request procedures to request that another gatekeeper perform address resolution, it may indicate the requirement for support of the MMRS feature by inclusion of the MMRS parameters. The responding gatekeeper shall use this information in the selection of a location, which matches the address and complies with any MMRS support requirement.
+
+## 4.2 RAS signalling
+
+### 4.2.1 Registration
+
+Support for the MMRS feature shall be indicated by the endpoint in an RRQ when the endpoint initially attempts to register. This shall indicate that MMRS will be supported by the endpoint if requested and it may indicate if support for MMRS is required for all calls to and from this endpoint. A gatekeeper may reject a registration due to the lack of support for MMRS by inclusion of **neededFeatureNotSupported** in the **rejectReason** in the RRJ, for example, if the gatekeeper knows that all calls in the network must use the MMRS procedures. The **desiredFeatures** field shall not be used to carry the MMRS parameter in an RRQ.
+
+### 4.2.2 Location request
+
+When an endpoint sends an LRQ to the gatekeeper for address resolution, it may indicate the requirement or desire for MMRS support by inclusion of the MMRS indication in either the **neededFeatures** or the **desiredFeatures** field. The gatekeeper shall use this information for the selection of a location, which matches the address and complies with any MMRS support requirement.
+
+### 4.2.3 Admission request
+
+Support for the MMRS feature for an individual call is negotiated between an 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 5.1 in **supportedFeatures** and may include the **neededFeatures** in the ARQ message in order to indicate whether the endpoint requires support for MMRS for the calls for which admission is being requested. If support for the feature is not indicated, a gatekeeper may reject an ARQ due to the lack of support for MMRS by the endpoint by inclusion of **neededFeatureNotSupported** in the **rejectReason** in the ARJ, for example, if the network or destination endpoint requires the use of MMRS.
+
+The MMRS parameter shall not be including in the **desiredFeatures** field in RAS admission request signalling, since support either is or is not required. Further, the "MMRS Sse Required" parameter shall not be used, since support always implies that it can be used if required by call signalling.
+
+## 4.3 Call signalling – negotiation
+
+The required or optional use of the MMRS procedure shall be negotiated by the two ends exchanging call-signalling messages using the Setup message and the first positive response to that
+
+setup. Positive responses are the setup acknowledge, alerting, call proceeding, progress, and connect messages.
+
+### 4.3.1 Setup
+
+If the calling endpoint supports the MMRS feature, but does not require the called endpoint to support it, it shall include the MMRS feature identifier in the **supportedFeatures** field in the setup to indicate its support for the feature. If the calling endpoint requires that the called party supports the MMRS feature as a condition for setting up the call, it shall include the MMRS feature identifier in the **neededFeatures** field. The MMRS feature identifier shall not be included in the **desiredFeatures** field since support either is or is not required.
+
+In addition, the setup may also include the "MMRS Use Required" parameter to indicate that the feature must be used by the responder if the responder initiates release of this call.
+
+In summary, the following combinations of supported, needed, and use required are possible in the setup message:
+
+| Case | Supported<br>(by sender) | (Support)<br>needed<br>(by responder) | Use<br>required |
+|------|--------------------------|---------------------------------------|-----------------|
+| 1    | Yes                      | No                                    | No              |
+| 2    | Yes                      | Yes                                   | No              |
+| 3    | Yes                      | Yes                                   | Yes             |
+
+### 4.3.2 Response
+
+Depending on the contents of the setup messages, the response shall be as follows:
+
+- If the setup indicated that support for MMRS by the responder is not required, the first positive response to setup may contain the **supportFeatures** field indicating that the responder supports the feature. In addition, the response message may include the "MMRS Use Required" parameter to indicate that the feature must be used by the other endpoint if the other endpoint initiates release of this call.
+
+Otherwise, the absence of the MMRS feature indication in the **supportedFeatures** field indicates that the responder does not support MMRS. The originator and responder shall continue to set up the call as normal.
+
+- If the setup indicated that support for MMRS is needed (required) but that use of the feature is not required for this call, the first positive response to setup may contain the **supportFeatures** field indicating that the responder supports the feature. In addition, the response message may include the "MMRS Use Required" parameter to indicate that the responder requires that the feature be used by the other endpoint if the other endpoint initiates release of this call.
+
+Otherwise, the absence of the MMRS feature indication in the **supportedFeatures** field indicates that the responder does not support MMRS. The responder shall continue to set up the call as normal, however the originator may decide to release the call setup.
+
+- If the setup indicated that MMRS must be used for this call, the first positive response to setup may contain the MMRS feature indication in the **supportedFeatures** to indicate that the responder supports the feature and will use it to release calls. Otherwise, the absence of the MMRS feature indication in the **supportedFeatures** field indicates that the responder does not support MMRS or cannot use it for this call, in which case the originator may release the call setup.
+
+## 4.4 Call signalling – release
+
+### 4.4.1 Facility message encoding
+
+The function of the Q.931 disconnect and release messages are provided by the H.225.0 facility message. The corresponding fields of the facility message shall be used to carry the information normally in the disconnect and release messages. Those additional fields, which are not defined in H.225.0 as being included in the facility message but are required in the release sequence shall be encoded in the "MMRS Additional IEs" parameter.
+
+### 4.4.2 Facility message procedures
+
+The "MMRS Procedure" parameter shall be used in facility messages between endpoints and gatekeepers and between endpoints to indicate the procedure to be used to release the connection.
+
+Either end may initiate the release procedure, independent of which one originally established the call. The "originator" in the following description refers to the end, which initiates the release.
+
+When sending the first facility message of the MMRS, the originator shall include the "MMRS procedure" parameter to indicate one of the following:
+
+- 1) "treat as Q.931 Disconnect message", that is, it is a request for the other end to begin a release procedure which may include delays or time-outs before the actual release occurs. The originator shall set T305 or T306.
+- 2) "treat as Q.931 Release message", that is, it must be responded to immediately with the release complete message, and if not, the originator will repeat the message. The originator shall set T308.
+
+It should be noted that, as in ITU-T Rec. Q.931, the use of the first "treat as Q.931 Disconnect message" is optional and the procedure functions properly if the first message sent is the "treat as Q.931 Release message". When the MMRS parameters exchanged indicates that MMRS must be used for this call, the "treat as Q.931 Disconnect message" is optional and its use depends on other factors such as the need to provide in-band tones and announcements.
+
+The action taken by the responder shall be as follows:
+
+Upon receipt of a facility message indicated as "treat as Q.931 Disconnect message", the responder may apply timeouts, or other feature specific procedures, before sending the response. Upon completion of such specific procedures, the responder shall send a facility message indicated as "treat like Q.931 Release message" and shall set T308.
+
+Upon receipt of a facility message indicated as "treat as Q.931 Release message", the responder shall immediately return a release complete message.
+
+Upon receipt of a release complete message, the responder shall clear all resources and not return any message, that is, it shall operate as defined in ITU-T Rec. H.225.0.
+
+Further procedures for timeouts, message repetition, and treatment of glare shall be as defined in ITU-T Rec. Q.931. In addition, upon time-out of T308 the second time, the endpoint shall send a release complete message.
+
+## 4.5 Call signalling timers
+
+In addition to the timers defined in ITU-T Rec. H.225.0, the following additional timers are used with the MMRS feature (see Tables 9-1/Q.931 and 9-2/Q.931):
+
+- 1) T305 defines how long the sender of a facility message marked as "treat as Q.931 Disconnect message" should wait for a response facility message before taking other action. It is set when facility marked as "treat as Q.931 Disconnect message" without progress indicator No. 8 is sent. Its default value is 30 seconds.
+
+- 2) T306 defines how long the sender of a facility message marked as "treat as Q.931 Disconnect message" should wait for a response facility message before taking other action. It is set when facility marked as "treat as Q.931 Disconnect message" with progress indicator No. 8 is sent. Its default value is 30 seconds (see 7.2.2.23/H.225.0 and 4.5.23/Q.931).
+- 3) T308 defines how long the sender of a facility message marked as "treat as Q.931 Release message" should wait for a response release complete message before taking other action, either resending the facility message or entering failure procedures. Its default value is 4 seconds.
+
+# 5 Generic data usage
+
+When sending the MMRS parameter in H.501 access request and service request messages, it shall be coded in the **common.genericData** field of the message.
+
+When sending the MMRS parameter in H.225.0 RAS messages, the parameter shall be coded in the **genericData** field in the request parameter of the H.225.0 **RasMessage**.
+
+When sending the MMRS parameter in the H.225.0 call signalling messages, it shall be coded in the **genericData** field in the H.225.0 H323-UU-PDU in the user-user information element.
+
+The **genericData** parameter indicates the MMRS feature and contains the MMRS parameters.
+
+## 5.1 Multiple-message release sequence feature
+
+Table 1 defines the multiple-message release sequence feature.
+
+**Table 1/H.460.16 – Multiple-message release sequence feature**
+
+| Feature name             | Multiple-message release sequence                                                                                                              |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|
+| Feature Description      | This feature allows one end to inform the other that it intends to use the multiple-message release sequence procedure or that it is using it. |
+| Feature identifier type  | Standard                                                                                                                                       |
+| Feature identifier value | 16                                                                                                                                             |
+
+## 5.2 Multiple-message release sequence parameters
+
+Tables 2 to 4 define the multiple-message release sequence parameters.
+
+**Table 2/H.460.16 – Multiple-message release sequence use parameter**
+
+| Parameter name             | MMRS use required                                                                                                                          |
+|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|
+| Parameter description      | This parameter is sent in H.225.0 call signalling setup/response messages to indicate that the MMRS procedures must be used for this call. |
+| Parameter identifier type  | Standard                                                                                                                                   |
+| Parameter identifier value | 1                                                                                                                                          |
+| Parameter type             | No content                                                                                                                                 |
+| Parameter cardinality      | Zero or one                                                                                                                                |
+
+**Table 3/H.460.16 – Multiple-message release sequence procedure parameter**
+
+| Parameter name             | MMRS procedure                                                                                                                               |
+|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| Parameter description      | This parameter is sent in the H.225.0 facility message to indicate how this message should be interpreted in supporting the MMRS procedures. |
+| Parameter identifier type  | Standard                                                                                                                                     |
+| Parameter identifier value | 2                                                                                                                                            |
+| Parameter type             | number8                                                                                                                                      |
+| Parameter valid values     | 1 = treat as Q.931 disconnect message<br>2 = treat as Q.931 release message                                                                  |
+| Parameter cardinality      | Zero or one.                                                                                                                                 |
+
+**Table 4/H.460.16 – Multiple-message release sequence additional IEs parameter**
+
+| Parameter name             | MMRS additional IEs                                                                                                                                                                                      |
+|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Parameter description      | This parameter is sent in the H.225.0 call signalling facility message to pass additional information elements not defined in facility which are contained in the Q.931 disconnect and release messages. |
+| Parameter identifier type  | Standard                                                                                                                                                                                                 |
+| Parameter identifier value | 3                                                                                                                                                                                                        |
+| Parameter type             | raw                                                                                                                                                                                                      |
+| Parameter cardinality      | Zero or one                                                                                                                                                                                              |
+
+NOTE – The MMRS additional IEs parameter is used to pass the cause, progress, and signal information elements defined in the Q.931 disconnect and release messages. The binary representation of the required IEs shall be contained in the raw parameter (similar to the procedure defined in ITU-T Rec. H.460.5).
+
+# 6 Message flows
+
+This clause provides message flows for the use of the MMRS procedure. In each case, the originating endpoint in the figure is the one, which initiates the release, not the one, which sets up the call.
+
+## 6.1 Three-message sequence
+
+When the signalling during call setup has determined that both endpoints support the MMRS procedure, the message flow for call release using three messages is as shown in Figure 1.
+
+![Sequence diagram showing the three-message release sequence between an Originating endpoint and a Responding endpoint. The sequence starts with the Originating endpoint sending a 'Facility – treat as Q.931 disconnect' message to the Responding endpoint. The Responding endpoint then sends a 'Facility – treat as Q.931 release' message back to the Originating endpoint. Finally, the Originating endpoint sends a 'Release complete' message to the Responding endpoint. The diagram includes labels for the endpoints, the messages, and the protocol standards T305 and T308. The figure is labeled H.460.16_F01.](78ffccd66df9bafd96e3e081110d09dd_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Originating endpoint
+    participant Responding endpoint
+    Note left of Originating endpoint: T305
+    Originating endpoint->>Responding endpoint: Facility – treat as Q.931 disconnect
+    Note right of Responding endpoint: T308
+    Responding endpoint->>Originating endpoint: Facility – treat as Q.931 release
+    Originating endpoint->>Responding endpoint: Release complete
+    Note right of Responding endpoint: H.460.16_F01
+  
+```
+
+Sequence diagram showing the three-message release sequence between an Originating endpoint and a Responding endpoint. The sequence starts with the Originating endpoint sending a 'Facility – treat as Q.931 disconnect' message to the Responding endpoint. The Responding endpoint then sends a 'Facility – treat as Q.931 release' message back to the Originating endpoint. Finally, the Originating endpoint sends a 'Release complete' message to the Responding endpoint. The diagram includes labels for the endpoints, the messages, and the protocol standards T305 and T308. The figure is labeled H.460.16\_F01.
+
+**Figure 1/H.460.16 – Message flow for three-message sequence**
+
+## 6.2 Time-outs
+
+If a time-out occurs while waiting for the response facility or release complete message, the appropriate message is repeated or a new message is sent. Figure 2 shows the case of the three-message procedure when all messages from the responding endpoint are lost, causing multiple time-outs at the originating endpoint. (Since T308 is generally much less than T305, several timeouts may also occur at the responding endpoint in this example.)
+
+![Sequence diagram illustrating time-outs in a three-message procedure between an originating and a responding endpoint.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg)
+
+This sequence diagram illustrates a three-message procedure for call release between an originating endpoint and a responding endpoint. The originating endpoint sends a 'Facility – treat as Q.931 disconnect' message. The responding endpoint receives it and sends a 'Facility – treat as Q.931 release' message, which is lost. The originating endpoint times out (T305) and retransmits the 'Facility – treat as Q.931 disconnect' message. The responding endpoint receives this and sends another 'Facility – treat as Q.931 release' message, which is also lost. The originating endpoint times out (T308) and retransmits the 'Facility – treat as Q.931 disconnect' message. The responding endpoint receives this and sends a 'Release complete' message, which is lost. The originating endpoint times out (T308) and sends a 'Release complete' message. The responding endpoint receives this and completes the release. The diagram is labeled H.460.16\_F02.
+
+Sequence diagram illustrating time-outs in a three-message procedure between an originating and a responding endpoint.
+
+Figure 2/H.460.16 – Time-outs
+
+## 6.3 Two-message sequence
+
+When the signalling during call setup has determined that both endpoints support the MMRS procedure, the message flow for call release using two messages is as shown in Figure 3. In this case, the originating endpoint does not use the optional "treat as Q.931 Disconnect" message.
+
+![Sequence diagram illustrating the message flow for a two-message sequence between an originating and a responding endpoint.](ddc7460821484f1ae2835c67955c554c_img.jpg)
+
+This sequence diagram illustrates a two-message sequence for call release between an originating endpoint and a responding endpoint. The originating endpoint sends a 'Facility – treat as Q.931 release' message. The responding endpoint receives it and sends a 'Release complete' message. The originating endpoint receives this and completes the release. The diagram is labeled H.460.16\_F03.
+
+Sequence diagram illustrating the message flow for a two-message sequence between an originating and a responding endpoint.
+
+Figure 3/H.460.16 – Message flow for two-message sequence
+
+## 6.4 Simultaneous initiation of two-message MMRS procedure
+
+When the signalling during call setup has determined that both endpoints support the MMRS procedure, if both endpoints initiate call release at the same instant, the messages will cross. The resulting message flow is shown in Figure 4.
+
+![Sequence diagram for simultaneous initiation of two-message MMRS procedure.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg)
+
+```
+
+sequenceDiagram
+    participant L as Originating endpoint
+    participant R as Originating endpoint
+    Note over L: T308
+    Note over R: T308
+    L->>R: Facility – treat as Q.931 release
+    R->>L: Facility – treat as Q.931 release
+    L->>R: Release complete
+    R->>L: Release complete
+  
+```
+
+Sequence diagram illustrating the message flow for simultaneous initiation of two-message MMRS procedure. Two vertical lines represent the 'Originating endpoint' on both sides. The sequence of messages is as follows:
+
+- Both endpoints simultaneously send a 'Facility – treat as Q.931 release' message to each other. These messages cross.
+- Both endpoints simultaneously receive a 'Release complete' message from the other endpoint. These messages also cross.
+
+Timing diagrams T308 are shown on both sides, indicating the sequence of events. The diagram is labeled H.460.16\_F04.
+
+Sequence diagram for simultaneous initiation of two-message MMRS procedure.
+
+**Figure 4/H.460.16 – Message flow for simultaneous initiation of two-message MMRS procedure**
+
+## 6.5 Simultaneous initiation of two- and three-message MMRS procedures
+
+When the signalling during call setup has determined that both endpoints support the MMRS procedure, if both endpoints initiate call release at the same instant, the messages will cross. If one initiates the two-message sequence and the other the three-message sequence, the resulting message flow is shown in Figure 5.
+
+![Sequence diagram for simultaneous initiation of two- and three-message MMRS procedures.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg)
+
+```
+
+sequenceDiagram
+    participant L as Originating endpoint
+    participant R as Originating endpoint
+    Note over L: T305
+    Note over R: T308
+    L->>R: Facility – treat as Q.931 disconnect
+    R->>L: Facility – treat as Q.931 release
+    R->>L: Release complete
+    L->>R: (Message ignored)
+  
+```
+
+Sequence diagram illustrating the message flow for simultaneous initiation of two- and three-message MMRS procedures. Two vertical lines represent the 'Originating endpoint' on both sides. The sequence of messages is as follows:
+
+- The left endpoint sends a 'Facility – treat as Q.931 disconnect' message. The right endpoint sends a 'Facility – treat as Q.931 release' message. These messages cross.
+- The left endpoint receives a 'Release complete' message from the right endpoint.
+- The right endpoint receives a message from the left endpoint, but it is ignored, as indicated by a 'Message ignored' box. This message is likely a 'Facility' message that the right endpoint does not expect at this stage of its three-message sequence.
+
+Timing diagrams T305 and T308 are shown on the left and right sides respectively, indicating the sequence of events. The diagram is labeled H.460.16\_F05.
+
+Sequence diagram for simultaneous initiation of two- and three-message MMRS procedures.
+
+**Figure 5/H.460.16 – Message flow for simultaneous initiation of two- and three-message MMRS procedure**
+
+## 6.6 Simultaneous initiation of MMRS and H.225.0 procedures
+
+When the signalling during call setup has determined that both endpoints support but do not require that the MMRS procedure be used, if both endpoints initiate call release using different procedures at the same instant, the different messages will cross. The resulting message flow is shown in Figure 6. In this case, the endpoint, which initiated the three-message sequence, will receive the normal H.225.0 release complete message in response and treat it as the proper response. The endpoint, which initiated the H.225.0 single message sequence, will receive the facility, which it will ignore.
+
+![Sequence diagram showing message flow between Originating endpoint A and Originating endpoint B for simultaneous initiation of MMRS and H.225.0 procedures.](724c7777b608e53be38b12b6fb3c43bc_img.jpg)
+
+The diagram illustrates the message exchange between two endpoints, Originating endpoint A and Originating endpoint B, during simultaneous call release initiation. The sequence of messages is as follows:
+
+- Originating endpoint A sends a **Facility – treat as Q.931 disconnect** message to Originating endpoint B.
+- Originating endpoint B sends a **Release complete** message to Originating endpoint A.
+- Originating endpoint A receives the **Release complete** message and treats it as a proper response, indicated by a callout box labeled **Treated as proper response**.
+- Originating endpoint B receives the **Facility – treat as Q.931 disconnect** message and ignores it, indicated by a callout box labeled **Message ignored**.
+
+The diagram also includes a **T305** label near the start of the message exchange on the left side. The diagram is labeled **H.460.16\_F06** in the bottom right corner.
+
+Sequence diagram showing message flow between Originating endpoint A and Originating endpoint B for simultaneous initiation of MMRS and H.225.0 procedures.
+
+Figure 6/H.460.16 – Message flow for simultaneous initiation of both procedures
+
+
+
+
+
+## **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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.460.17-200509-I_PDF-E/raw.md b/marked/H/T-REC-H.460.17-200509-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..66d6a1150ed3164bb827f1a9ebdcb0e29e751484
--- /dev/null
+++ b/marked/H/T-REC-H.460.17-200509-I_PDF-E/raw.md
@@ -0,0 +1,267 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.460.17**
+
+(09/2005)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Infrastructure of audiovisual services – Supplementary  
+services for multimedia
+
+---
+
+**Using H.225.0 call signalling connection as  
+transport for H.323 RAS messages**
+
+ITU-T Recommendation H.460.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        |
+| <b>Supplementary services for multimedia</b>                                  | <b>H.450–H.499</b> |
+| 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.17**
+
+# **Using H.225.0 call signalling connection as transport for H.323 RAS messages**
+
+## **Summary**
+
+The current version of ITU-T Rec. H.323 requires two completely independent transports: one for RAS and another for H.225.0 call signalling. For several reasons, one of them is FW/NAT traversal; it would be advantageous to be able to use the same transport for both protocols.
+
+This Recommendation defines the mechanism of encapsulating RAS messages inside H.225.0 messages and the method for discovering the ability of a peer H.323 entity to support features defined in this Recommendation.
+
+###### **Source**
+
+ITU-T Recommendation H.460.17 was approved on 13 September 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 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 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    |
+| 3 Terms and Definitions .....                                   | 1    |
+| 4 Abbreviations.....                                            | 2    |
+| 5 Feature Description.....                                      | 2    |
+| 6 Discovering remote entity's support of RAS over H.225.0 ..... | 2    |
+| 7 Transport of RAS over H.225.0.....                            | 2    |
+| 7.1 Usage of H.225.0.....                                       | 2    |
+| 7.2 Generic data usage.....                                     | 3    |
+| 7.3 RAS over H.225.0 feature definition.....                    | 3    |
+| 7.4 RAS over H.225.0 parameters.....                            | 4    |
+| 8 Security considerations.....                                  | 4    |
+
+
+
+# Using H.225.0 call signalling connection as transport for H.323 RAS messages
+
+## 1 Scope
+
+This Recommendation defines the mechanism of encapsulating RAS messages inside H.225.0 messages and the method for discovering the ability of a peer H.323 entity to support features defined in 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.
+
+- [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.235.0 (2005), *H.323 security: Framework for security in H-series (H.323 and other H.245-based) multimedia systems*.
+- [5] ITU-T Recommendation H.235.1 (2005), *H.323 security: Baseline security profile*.
+- [6] ITU-T Recommendation H.235.2 (2005), *H.323 security: Signature security profile*.
+- [7] ITU-T Recommendation H.235.3 (2005), *H.323 security: Hybrid security profile*.
+- [8] ITU-T Recommendation H.235.4 (2005), *H.323 security: Direct and selective routed call security*.
+- [9] ITU-T Recommendation H.235.5 (2005), *H.323 security: Framework for secure authentication in RAS using weak shared secrets*.
+- [10] ITU-T Recommendation H.235.6 (2005), *H.323 security: Voice encryption profile with native H.235/H.245 key management*.
+- [11] ITU-T Recommendation H.235.7 (2005), *H.323 security: Usage of the MIKEY key management protocol for the Secure Real Time Transport Protocol (SRTP) within H.235*.
+- [12] IETF RFC 2246 (1999), *The TLS Protocol Version 1.0*.
+
+## 3 Terms and Definitions
+
+This Recommendation defines the following term:
+
+**3.1 RAS over H.225.0:** The mechanism allowing transport of RAS messages inside the H.225.0 call signalling connection.
+
+## 4 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+|      |                                      |
+|------|--------------------------------------|
+| EP   | Endpoint                             |
+| GK   | Gatekeeper                           |
+| RAS  | Registration, Admission and Status   |
+| RCF  | Registration Confirm                 |
+| RRQ  | Registration Request                 |
+| SCTP | Stream Control Transmission Protocol |
+| TCP  | Transport Control Protocol           |
+| TLS  | Transport Level Security             |
+| TSAP | Transport Service Access Point       |
+
+## 5 Feature Description
+
+This Recommendation defines two mechanisms:
+
+- Discovery of the remote entity's support of RAS over H.225.0
+- Transport of RAS messages over the H.225.0 call signalling connection.
+
+## 6 Discovering remote entity's support of RAS over H.225.0
+
+RAS messages are sent between EP and GK or between two GKs. In both cases the first RAS message between two particular H.323 entities is sent in the GK direction. The support of RAS over H.225.0 by a particular GK may be either known *a priori* (provisioned) or may require discovery. H.460 feature negotiation mechanisms cannot be used in this case because the discovery should be performed before the first message between the H.323 entities is sent.
+
+Annex O/H.323 GK discovery mechanism should be used for discovery of support of RAS over H.225.0. The service for the discovery shall be either h323rs or h323ls. The H.225.0 transport will be discovered based on the following rules:
+
+In the case of H.225.0 signalling over TCP, the transport shall be tcp.
+
+In the case of H.225.0 signalling over Annex E/H.323, the transport shall be h323mux.
+
+In the case of H.225.0 signalling over SCTP, the transport shall be sctp.
+
+If the IP address of the GK is known *a priori* and the port is unknown, the well-known H.225.0 call signalling port 1720 shall be used for RAS over H.225.0 procedure.
+
+## 7 Transport of RAS over H.225.0
+
+## 7.1 Usage of H.225.0
+
+The entity which supports RAS over H.225.0 shall also support persistent H.225.0 transport connections as described in 7.3/H.323. An endpoint shall indicate such support by setting maintainConnection in RRQ to TRUE.
+
+If both the entity sending the RAS message, and the entity receiving it support RAS over H.225.0, then they should use it for RAS messages transport.
+
+In order to keep the transport connection open, the two entities should use lightweight RRQ, as described in 7.2.2.1/H.323. In the case of NAT traversal, the timeToLive value should be shorter
+
+than the NAT binding timeout. The entities may use the IRR mechanism to support the same functionality. Alternatively, for the cases when transport is TCP, an entity which established the TCP connection may periodically send empty TPKT packets (packets containing bytes 03 00 00 04 only). A keep-alive interval in the range of 5 to 30 seconds should be used except in cases where it is known (for example, from the specifics of the network) that a longer interval will not result in the closure of pinholes.
+
+To send a RAS message between two H.323 entities supporting RAS over the H.225.0 feature, a persistent H.225.0 transport connection shall be used between the entities. If such a connection is already established it may be re-used, or a new connection may be established. If no persistent connection is currently established, then it shall be established. Generally, the entity sending the first RAS message establishes the connection to the entity receiving the RAS message. The H.225.0 signalling TSAP of the entity receiving the RAS message is used as the transport connection destination. The same transport connection should be used for RAS over H.225.0 signalling and regular H.225.0 signalling.
+
+If desired, more than one H.225.0 transport connection between the same two entities may be used for RAS messages transfer. No association is mandated between RAS messages and transport connections in such a case.
+
+To signal that the same GK's H.225.0 transport signalling TSAP shall be used for all RAS and H.225.0 communication, the callSignalAddress and rasAddress fields of the RRQ and RCF shall contain a SEQUENCE OF containing zero elements.
+
+The H.225.0 FACILITY message shall be used to transfer RAS messages. The CRV field of the message shall have a value of 0 (including the flag bit). Such a message shall contain User-user Information Element with the h323-message-body field of H323-UU-PDU set to empty. The genericData field of the H323-UU-PDU shall contain RAS messages as described in 7.2 and 7.4.
+
+An H.323 entity, which supports RAS over H.225.0, shall also support tunnelling of H.245 channel over H.225.0.
+
+## 7.2 Generic data usage
+
+RAS messages to be sent over H.225.0 call signalling shall be encapsulated in the genericData field of the H323-UU-PDU in the User-user Information Element of the H.225.0 FACILITY message. Each such genericData field has the id field specifying RAS over H.225.0 (as defined in Table 1) and one or more RAS message parameters (as defined in Table 2) containing binary encoding of one RAS message each.
+
+## 7.3 RAS over H.225.0 feature definition
+
+Table 1 defines the RAS over the H.225.0 feature.
+
+**Table 1/H.460.17 – RAS over H.225.0 feature**
+
+|                           |                                                                                        |
+|---------------------------|----------------------------------------------------------------------------------------|
+| Feature name:             | RAS over H.225.0                                                                       |
+| Feature Description:      | This feature allows transport of RAS messages over H.225.0 call signalling connection. |
+| Feature identifier type:  | Standard                                                                               |
+| Feature identifier value: | 17                                                                                     |
+
+## 7.4 RAS over H.225.0 parameters
+
+Table 2 defines the RAS over H.225.0 parameters.
+
+**Table 2/H.460.17 – RAS message parameter**
+
+|                             |                                                                |
+|-----------------------------|----------------------------------------------------------------|
+| Parameter name:             | RAS message                                                    |
+| Parameter description:      | This parameter contains basic-aligned PER-encoded RAS message. |
+| Parameter identifier type:  | Standard                                                       |
+| Parameter identifier value: | 1                                                              |
+| Parameter type:             | raw                                                            |
+| Parameter cardinality:      | One or more                                                    |
+
+## 8 Security considerations
+
+The transport of RAS messages provided by RAS over H.225.0 mechanism does not provide a means of security. It relies on the security mechanisms provided by underlying transport and security mechanisms defined for RAS messages.
+
+TLS may be used for the RAS over a TCP or SCTP channel. The procedure for supporting TLS is out of the scope of this Recommendation and needs to be addressed by H.235.
+
+
+
+## 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.460.27-201511-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg b/marked/H/T-REC-H.460.27-201511-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ce43dea629b572c3ac4df9327581d2332e329dd1
--- /dev/null
+++ b/marked/H/T-REC-H.460.27-201511-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a80e243c43648a06f93857ceeded529c56edc3066c78aab19047ea6acb4ab2ce
+size 21334
diff --git a/marked/H/T-REC-H.460.27-201511-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg b/marked/H/T-REC-H.460.27-201511-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..de025d3b586678c8351b8e7d092111bdcdf0fdbc
--- /dev/null
+++ b/marked/H/T-REC-H.460.27-201511-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1cb0df7fd46327531a0a69bbf1d4d16788bcdf6e9e67c4fb68003b9eb4ee4f73
+size 9033
diff --git a/marked/H/T-REC-H.460.27-201511-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.460.27-201511-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9002ee68e2b9ebf63d27d39ba8c73bdafb0e6be6
--- /dev/null
+++ b/marked/H/T-REC-H.460.27-201511-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.460.27-201511-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/H/T-REC-H.460.27-201511-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3b6d995cf512b50d685470de29c08befc27cf4dd
--- /dev/null
+++ b/marked/H/T-REC-H.460.27-201511-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a8d0f534aa774dddbac0b2a0f2f3696867c9ed98f5d5beb642c84d57137eba8a
+size 9441
diff --git a/marked/H/T-REC-H.460.27-201511-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/H/T-REC-H.460.27-201511-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4aae7e2dcd0d85e15f038228c3fd029b529f0a05
--- /dev/null
+++ b/marked/H/T-REC-H.460.27-201511-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6a3d1be9c35eeb7822de56a5b0101d7db7632f57395971102e2fafb5f7acd10b
+size 9284
diff --git a/marked/H/T-REC-H.460.27-201511-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/H/T-REC-H.460.27-201511-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3e8e7db82b079a73f03a7335ec845e12d29a0ebf
--- /dev/null
+++ b/marked/H/T-REC-H.460.27-201511-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e50bc46cd9faed2941f80eff3f81361d44c9e88ed192951614c6bbfa26c7238b
+size 12221
diff --git a/marked/H/T-REC-H.460.3-200211-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.460.3-200211-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30
--- /dev/null
+++ b/marked/H/T-REC-H.460.3-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.5-200211-I_PDF-E/raw.md b/marked/H/T-REC-H.460.5-200211-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a369bbe5c3ed000be609ff4de724f41f62d04a58
--- /dev/null
+++ b/marked/H/T-REC-H.460.5-200211-I_PDF-E/raw.md
@@ -0,0 +1,186 @@
+
+
+![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.5**
+
+(11/2002)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS  
+Supplementary services for multimedia
+
+---
+
+**H.225.0 transport of multiple Q.931 information  
+elements of the same type**
+
+ITU-T Recommendation H.460.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.399        |
+| <b>SUPPLEMENTARY SERVICES FOR MULTIMEDIA</b>                                  | <b>H.450–H.499</b> |
+| 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.5**
+
+### **H.225.0 transport of multiple Q.931 information elements of the same type**
+
+## **Summary**
+
+This Recommendation specifies the method of transferring duplicate Q.931 information elements in the H.225.0 messages. Such a method is required to overcome limitations imposed by ITU-T Rec. H.225.0. ITU-T Rec. H.225.0 allows for the inclusion of only a single Q.931 information element of a particular type in the single H.225.0 message.
+
+###### **Source**
+
+ITU-T Recommendation H.460.5 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 | Terms and definitions .....                | 1 |
+| 4 | The conversion procedure.....              | 1 |
+| 5 | Generic Data Parameter specification ..... | 1 |
+
+
+
+## ITU-T Recommendation H.460.5
+
+### H.225.0 transport of multiple Q.931 information elements of the same type
+
+## 1 Scope
+
+ITU-T Rec. H.225.0 forbids including multiple Q.931 information elements (IEs) of the same type in the same message.
+
+This Recommendation specifies the method of transferring duplicate Q.931 IEs in H.225.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 Recommendation H.225.0 (2000), *Call signalling protocols and media stream packetization for packet-based multimedia communications systems*.
+- ITU-T Recommendation H.323 (2000), *Packet-based multimedia communications systems*.
+- ITU-T Recommendation Q.931 (1998), *ISDN user-network interface layer 3 specification for basic call control*.
+
+## 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 and H.245 apply.
+
+## 4 The conversion procedure
+
+To transfer a Q.931 message containing multiple IEs of the same type over the H.225.0 protocol, the conversion specified in this clause shall be performed.
+
+The conversion applies to all IEs except for the IEs that have the first appearance of the particular IE identifier. The binary representations (that includes IE identifier, length and content) of all such IEs shall be assembled into a single octet string. The resulting octet string shall be used as the value of the GEF parameter, as defined in clause 5, "Generic Data Parameter specification". In accordance with ITU-T Rec. H.225.0, IEs shall not be duplicated in the Q.931 part of the H.225.0 message.
+
+## 5 Generic Data Parameter specification
+
+This clause defines the DuplicateIEs feature and parameter
+
+|                           |                                 |
+|---------------------------|---------------------------------|
+| Feature name:             | DuplicateIEs                    |
+| Feature Description:      | The duplicate Q.931 IE support. |
+| Feature identifier type:  | Standard                        |
+| Feature identifier value: | 5                               |
+
+|                             |                                                                    |
+|-----------------------------|--------------------------------------------------------------------|
+| Parameter name:             | IEsString                                                          |
+| Parameter description:      | The binary representation of the 2 to last IEs of particular type. |
+| Parameter identifier type:  | Standard                                                           |
+| Parameter identifier value: | 1                                                                  |
+| Parameter type:             | raw                                                                |
+| Parameter cardinality:      | 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                                                                   |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                      |
+| 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/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/H/T-REC-H.460.9-200211-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30
--- /dev/null
+++ b/marked/H/T-REC-H.460.9-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.530-200203-I_PDF-E/raw.md b/marked/H/T-REC-H.530-200203-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..2e7729a8684b8f33e0e20ac421fb694bf4d3deab
--- /dev/null
+++ b/marked/H/T-REC-H.530-200203-I_PDF-E/raw.md
@@ -0,0 +1,840 @@
+
+
+![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.530**
+
+(03/2002)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Mobility and Collaboration procedures – Security for  
+mobile multimedia systems and services
+
+---
+
+**Symmetric security procedures for H.323  
+mobility in H.510**
+
+ITU-T Recommendation H.530
+
+---
+
+# 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        |
+| <b>Security for mobile multimedia systems and services</b>                    | <b>H.530–H.539</b> |
+| 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.530**
+
+# **Symmetric security procedures for H.323 mobility in H.510**
+
+## **Summary**
+
+The purpose of this Recommendation is to describe security procedures for an H.323 multimedia mobility environment. This Recommendation provides the details about the security procedures for H.510.
+
+## **Source**
+
+ITU-T Recommendation H.530 was prepared by ITU-T Study Group 16 (2001-2004) and approved under the WTSA Resolution 1 procedure on 29 March 2002.
+
+## **Keywords**
+
+Annex D/H.235, authentication, encryption, integrity, key management, mobility, 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.
+
+## 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 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     | Introduction .....                                                      | 1  |
+| 3     | Specification conventions .....                                         | 1  |
+| 4     | Terms and definitions .....                                             | 3  |
+| 5     | Abbreviations and symbols.....                                          | 4  |
+| 6     | References.....                                                         | 5  |
+| 6.1   | Normative references.....                                               | 5  |
+| 6.2   | Non-normative references .....                                          | 5  |
+| 7     | Security requirements and constraints for mobility .....                | 6  |
+| 8     | Hop-by-hop security with symmetric cryptographic techniques.....        | 7  |
+| 8.1   | Assumptions .....                                                       | 8  |
+| 8.2   | Secure location updating procedures.....                                | 8  |
+| 8.2.1 | MT to V-GK .....                                                        | 11 |
+| 8.2.2 | V-GK to MRP .....                                                       | 14 |
+| 8.2.3 | MRP to V-BE .....                                                       | 15 |
+| 8.2.4 | V-BE to H-BE .....                                                      | 16 |
+| 8.2.5 | H-BE to MRP .....                                                       | 17 |
+| 8.2.6 | MRP to AuF .....                                                        | 17 |
+| 8.3   | Terminal authentication.....                                            | 19 |
+| 8.4   | Unregistration .....                                                    | 21 |
+| 8.5   | Application of the symmetric security protocol in the home domain ..... | 21 |
+| 8.6   | List of Object Identifiers .....                                        | 22 |
+| 9     | End-to-end security.....                                                | 22 |
+
+
+
+# Symmetric security procedures for H.323 mobility in H.510
+
+# 1 Scope
+
+The purpose of this Recommendation is to provide recommendations for security procedures in H.323 mobility environments such as under the scope of ITU-T Rec. H.510. This Recommendation provides the details about the security procedures for ITU-T Rec. H.510.
+
+# 2 Introduction
+
+So far, the signalling capabilities of ITU-T Rec. H.235 in its versions 1 and 2 [4] are designed to handle security in mostly static H.323 [5] environments. Those environments and multimedia systems can achieve some limited mobility within gatekeeper zones; ITU-T Rec. H.323 [5] in general and ITU-T Rec. H.235 [4] specifically provide only very little support for secure roaming of mobile users and terminals across different domains with many involved entities in a mobility, distributed environment for example.
+
+The H.323 mobility scenarios depicted in ITU-T Rec. H.510 [6] regarding terminal mobility pose a new situation with their flexible and dynamic character also from a security point of view. Roaming H.323 users and mobile terminals have to be authenticated by a foreign, visited domain. Likewise, the mobile user would like to obtain evidence about the true identity of the visited domain. In addition to that, it may be also useful to obtain evidence about the identity of the terminals complementing user authentication. Thus, these requirements demand for mutual authentication of the user and the visited domain and optionally also of the identity of the terminal.
+
+As the mobile user is usually known only to the home domain where the user is subscribed and assigned a password, the visited domain initially does not know the mobile user. As such, the visited domain does not share any established security relationship with the mobile user and the mobile terminal. In order to let the visited domain achieve the authentication and authorization assurance for the mobile user and for the mobile terminal, the visited domain would relay certain security tasks such as authorization checks or key management to the home domain through intermediate network and service entities. This requires securing the communication and key management between the visited domain and the home domain too.
+
+While, in principle, mobility H.323 environments are more open than closed H.323 networks, there is of course also need to appropriately secure the key management tasks. It is also true that communication within and across the mobility domains deserves protection against malicious tampering.
+
+In summary, this Recommendation describes a generic security concept for mobility among domains for multimedia applications and multimedia services. The technical details describe the deployment for H.323 and for H.510 in particular, but are considered potentially open to other environments.
+
+## 3 Specification 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 Recommendation is explicitly listed. For example, "1.4" refers to clause 1.4 of this Recommendation; "6.4/H.245" refers to clause 6.4 in Recommendation H.245.
+
+This Recommendation shows several mobility functional entities such as border elements. For a general description of those functional elements and their interaction, please refer to ITU-T Rec. H.510 [6]. As this Recommendation only describes user/terminal mobility security, interaction with other mobility related functional entities such as mobility routing proxies like VLF, HLF is just briefly mentioned; such functional entities are considered not an integral part of this Recommendation. Specifically, the security architecture does not depend on the presence or absence of such functional elements nor does the security architecture require separating any such function. For simplicity, this Recommendation rather assumes these functions co-located in compound network elements, but for completeness those network entities are shown as decomposed functional entities. Of course, the security concepts could be extended in a straightforward manner to cover those elements when present as well by functionally decomposing and separating them.
+
+All those optional network entities appear as dashed boxes in the diagrams. Regarding the home domain, an authentication entity (AuF) functioning as a back-end security service may be separate or may be co-located with the home border element or other appropriate H.323 entities [5], e.g. the home gatekeeper (H-GK). Which of those instantiations actually apply is left as a local implementation matter.
+
+In this Recommendation, the **authentication function (AuF)** is understood as the security functional entity in the home domain that maintains security relationship with the subscribed mobile users and the subscribed mobile terminals if necessary. Among further tasks not described in this Recommendation, the AuF shall accomplish at least the following tasks:
+
+- Evaluate incoming **AuthenticationRequest** messages from a visited domain, check the authenticity and integrity of such messages, and particularly, the AuF shall authenticate the mobile user and optionally also the mobile terminal (MT) if provided and desired.
+- Upon successful authentication of the mobile user/terminal, the AuF shall decide upon granting authorization. Exactly how the AuF would achieve this decision is outside the scope of this Recommendation, but some policy database or certain access rules might be appropriate.
+- Further on, the AuF shall support and assist the visited domain in the key management task; specifically, the AuF shall authenticate a received Diffie-Hellman half-key and  $GK_{ID}$  from the visited domain using the corresponding user shared secret.
+- Finally, the AuF shall respond back to the visited domain about the security authorization decision taken, with the authenticated value Diffie-Hellman half-key and  $GK_{ID}$  included.
+
+The AuF could be thought of as a security module – potentially physically separate from other functional entities – with specific security functionality such as protected key storage, cryptographic algorithm and mechanism support, secured administration and maintenance access, reliability, etc. However, this Recommendation does not assume presence of any such feature in the AuF. Rather, the AuF may also well be co-located with other H.323 functional entities [5] in the home domain such as in the border element, in the gatekeeper, in a mobility routing proxy (MRP) or in any other appropriate entity. The concept of the AuF leaves it open on whether it would be best implemented in hardware, in software, or in a combination of both.
+
+This Recommendation introduces a **mobility routing proxy (MRP)** as an optional functional entity. The MRP acts as an intermediate functional entity, terminating the security association of a hop-by-hop link. The MRP shall forward the security tokens by re-computing anew the hop-by-hop message authentication codes in the **CryptoToken**. The MRP may encompass the functionality of a mobility management functional entity (e.g. of a HLF or of a VLF or of any other mobility
+
+back-end service entity). The MRP may appear in the visited domain or in the home domain, or in any other domain traversed.
+
+In case a shown MRP does not occur in the actual communication, the hop-by-hop links entering and leaving the MRP shall be considered to belong to the same security association and re-computation of the **CryptoToken** shall be omitted.
+
+This Recommendation uses the term **password** when a user-entered password string is meant. The password in this Recommendation is understood to be the assigned security key, which the mobile user shares with his or her home domain. This user password and derived user shared secret shall be applied for the purpose of user authentication.
+
+Different to that, a **shared secret** is the security key that is part of the security parameters for the cryptographic algorithms; it can be derived from a password (see H.235 procedure 10.3.5 [4]) or it can be assigned per configuration or by other means.
+
+Likewise, the mobile terminal may have been assigned a separate security shared secret by the home domain for the purpose of terminal authentication.
+
+The assignment and distribution of passwords and shared secrets among the functional entities is outside the scope of this Recommendation.
+
+This Recommendation uses the term **service relationship** to reference an established security association between two functional entities, such as between a visited border element (V-BE) and a home border element (H-BE). Among other parameters of such a service relationship, it is essential that at least a shared key  $ZZ_n$  be present, by which traffic between both functional entities is secured (e.g. IPSEC or Annex D/H.235 [4]).
+
+The **AuthenticationRejection** message used in this Recommendation indicates a failed security check by the AuF. The **AuthenticationRejection** message shall hold the same **Clear-** and **CryptoTokens** as the related **AuthenticationConfirmation** message.
+
+The object identifiers are referenced through a symbolic reference in the text (e.g. "G1"). Clause 8.6 lists the actual numeric values for the symbolic object identifiers.
+
+# 4 Terms and definitions
+
+For the purposes of this Recommendation the definitions given in clause 3 of ITU-T Recs H.323 [5], H.225.0 [1], H.225.0 Annex G [2], H.235 [4], H.501 [3], H.510 [6] and X.800 [7] apply along with those in this clause.
+
+**4.1 authentication function (AuF):** The AuF is the security functional entity in the home domain that maintains security relationship with the subscribed mobile users and the subscribed mobile terminals.
+
+**4.2 credential:** In this Recommendation, a credential [such as  $\text{HMAC}_{ZZ}(\text{GK}_{\text{ID}})$  or  $\text{HMAC}_{ZZ}(\text{W})$ ] is understood as some piece of data to which the AuF cryptographically has applied its shared secret  $ZZ$  that it shares with the mobile user. The credential is transferred to prove authorization and timeliness in the authorization check.
+
+**4.3 home border element (H-BE):** This is a border element (BE) placed within the home domain.
+
+**4.4 mobility routing proxy (MRP):** The MRP is an optional functional entity that acts as an intermediate functional entity, terminating the security association of a hop-by-hop link.
+
+**4.5 password:** Referring to a user-entered password string.
+
+**4.6 service relationship:** References an established security association between two functional entities, assuming that at least a shared key is present.
+
+**4.7 shared secret:** Refers to the security key for the cryptographic algorithms; it may be derived from a password.
+
+**4.8 visited border element (V-BE):** This is a border element (BE) placed within the visited domain.
+
+## 5 Abbreviations and symbols
+
+This Recommendation uses the following abbreviations and symbols:
+
+|                   |                                                                                                                                  |
+|-------------------|----------------------------------------------------------------------------------------------------------------------------------|
+| AuF               | Authentication Function, see ITU-T Rec. H.510 [6]                                                                                |
+| BE                | Border Element, see ITU-T Rec. H.225.0 Annex G [2]                                                                               |
+| CH <sub>n</sub>   | Challenge number $n$                                                                                                             |
+| DH                | Diffie-Hellman                                                                                                                   |
+| EP <sub>ID</sub>  | MT endpoint identifier, see ITU-T Rec. H.225.0 [1]                                                                               |
+| GK                | Gatekeeper, see ITU-T Rec. H.510 [6]                                                                                             |
+| GK <sub>ID</sub>  | Visited Gatekeeper identifier, see ITU-T Rec. H.225.0 [1]                                                                        |
+| GRJ               | Gatekeeper Reject                                                                                                                |
+| GRQ               | Gatekeeper Request                                                                                                               |
+| H-BE              | Home BE                                                                                                                          |
+| H-GK              | Home GK                                                                                                                          |
+| HLF               | Home Location Function                                                                                                           |
+| HMAC-SHA1-96      | Hashed Message Authentication Code with Secure Hash Algorithm 1                                                                  |
+| HMAC <sub>Z</sub> | Key Hashed message authentication code/response with shared secret $Z$ , if $Z$ is not shown then the next-hop secret is applied |
+| IPSEC             | Internet Protocol Security                                                                                                       |
+| K                 | Dynamic session/link key                                                                                                         |
+| MRP               | Mobility Routing Proxy                                                                                                           |
+| MT                | Mobile Terminal, see ITU-T Rec. H.510 [6]                                                                                        |
+| NTP               | Network Time Protocol                                                                                                            |
+| OID               | Object Identifier                                                                                                                |
+| PKI               | Public-key infrastructure                                                                                                        |
+| PW                | Mobile User Password                                                                                                             |
+| R <sub>1</sub>    | Random number                                                                                                                    |
+| RIP               | Request in Progress                                                                                                              |
+| RRJ               | Registration Reject                                                                                                              |
+| RRQ               | Registration Request                                                                                                             |
+| SNTP              | Simple Network Time Protocol                                                                                                     |
+| T <sub>n</sub>    | Timestamp number $n$                                                                                                             |
+| V-BE              | Visited BE                                                                                                                       |
+
+|                 |                                                                                       |
+|-----------------|---------------------------------------------------------------------------------------|
+| V-GK            | Visited GK                                                                            |
+| VLF             | Visitor Location Function                                                             |
+| W               | Compound value with arithmetic combination of Diffie-Hellman half-keys                |
+| WT              | Mobility ClearToken                                                                   |
+| XT              | CryptoToken for MT authentication                                                     |
+| ZZ              | Shared secret/password of the mobile user, which is shared with the corresponding AuF |
+| ZZMT            | Shared secret of the mobile terminal MT, which is shared with the corresponding AuF   |
+| ZZ <sub>n</sub> | Shared-secret number $n$                                                              |
+| ⊕               | Bitwise XOR                                                                           |
+
+# 6 References
+
+## 6.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.
+
+- [1] ITU-T Recommendation H.225.0 Version 4 (2000), *Call signalling protocols and media stream packetization for packet-based multimedia communications systems*.
+- [2] ITU-T Recommendation H.225.0 Annex G (Draft), *Communication between administrative domains*.
+- [3] ITU-T Recommendation H.501 (2002), *Protocol for mobility management and intra/inter-domain communication in multimedia systems*.
+- [4] ITU-T Recommendation H.235 Version 2 (2000), *Security and encryption for H-series (H.323 and other H.245-based) multimedia terminals*.
+- [5] ITU-T Recommendation H.323 Version 4 (2000), *Packet-based multimedia communication systems*.
+- [6] ITU-T Recommendation H.510 (2002), *Mobility for H.323 multimedia systems*.
+- [7] ITU-T Recommendation X.800 (1991), *Security architecture for Open Systems Interconnection for CCITT applications*.
+
+## 6.2 Non-normative references
+
+- [8] IETF RFC 1305 (1992), *Network Time Protocol (Version 3) Specification, Implementation and Analysis, Internet Engineering Task Force*.
+- [9] IETF RFC 2030 (1996), *Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI; Internet Engineering Task Force*.
+
+# 7 Security requirements and constraints for mobility
+
+Multimedia mobility management and application to H.323 mobility environments face the following security requirements and constraints:
+
+- This Recommendation shall support and facilitate better security interworking of H.323-secured systems when deployed in a mobility environment with distributed components and separately managed domains.
+- The mobile user shall be authenticated when roaming across domains. The mobile user authentication shall serve as a base for granting user access and service permission. The authentication shall be accomplished through the home AuF when initially attaching to a foreign visited domain. For any further interaction with the visited domain, the mobile user authentication shall be accomplished through the visited domain without necessarily querying the home AuF each time.
+- The mobile terminal should be authenticated when roaming across domains. The mobile terminal authentication may be used to detect and trace black-list/white-list MTs. The MT authentication should be accomplished in conjunction with the mobile user authentication, instead of a separate and additional procedure.
+- A scenario should be supported where the MTs are maintained in a different AuF (possibly in a different domain) than the mobile users. In such a scenario, the visited domain shall query the user's home domain with a single authentication request rather than separate authentication requests. The user's home AuF may then further delegate queries for the MT authentication, but such communication is not part of this Recommendation.
+- Based upon the trust relationship between visited domain and home domain, the visited domain shall authenticate towards the mobile user, e.g. in that the MT is able to authenticate the visited gatekeeper. Likewise, the visited domain should authenticate towards the home AuF.
+
+NOTE – As visited domain and home domain usually do not share an established security relationship, one cannot expect to achieve strong authentication between those two domains in a strict sense. However, some trust assurance could be achieved by relying on the hop-by-hop secured links between the visited domain and the home domain.
+
+- The mobility management protocols within and across domains shall be secured against masquerade, loss of integrity and if possible against loss of confidentiality.
+- Denial-of-service attacks should be minimized as far as possible.
+- User profile and user service profile information, as well as any security keys shall be transmitted securely across and within domains. The latter demands secure key management in a mobility environment. This includes the requirement that such sensitive information shall not be made available to any intermediate entities and domains unless required. This means that the MT user password shall not be made available to any functional entity except MT and AuF. This also means that the MT shared secret shall not be made available to any functional entity except MT and AuF. Further, this means that the negotiated dynamic session key for securing communication between the MT and the visited domain shall not be made available to other intermediate network entities.
+- The dynamic session key shall be authentic and cryptographically bound to the accomplished authentication. This includes the requirement for the session key to be fresh.
+- The overall security architecture shall take the trust relationships among domains into account. On one hand, this requires taking the security relationship among entities and domains into account. On the other hand, cheating entities (such as potentially a masqueraded visited gatekeeper (V-GK) but also any other entity) shall be detected and the likelihood of cheating be minimized.
+
+- The security techniques to be applied shall take existing H.235 [4] and other security techniques into account with enhancement only if necessary.
+- The security architecture deployed shall be simple and shall not require assuming additional security infrastructure measures such as smart cards and complex management protocols.
+
+# 8 Hop-by-hop security with symmetric cryptographic techniques
+
+As symmetric security techniques are deployed according to Annex D/H.235 [4] in non-mobility, quasi-static H.323 environments, this Recommendation shows the security architecture with security procedures in a mobility H.323 environment, which deploys the same security techniques as well. Basically, this Recommendation describes a security architecture that is based upon a security infrastructure only using symmetrically shared secrets. The shared secrets are defined on a hop-by-hop or pair-wise base between the communicating entities.
+
+This is a simple security model and does not require using a specific public-key security infrastructure for example. The hop-by-hop security architecture is designed to deploy well-engineered Annex D/H.235 [4] security symmetric techniques to a large extend. It is believed that symmetric crypto techniques provide rather high performance and thus, such techniques are generally applicable in the mobility environment as well.
+
+Figure 1 depicts the security architecture for an H.323 mobility environment according to H.510 [6], which is based upon H.501 [3]. The figure shows the principal architectural relationship of the functional entities. Furthermore, the figure shows the security relationship of keys among the entities. The figures also shows the case when the MT is attached to home gatekeeper in the home domain.
+
+![Diagram of security architecture for mobility H.323 environment showing functional entities and shared secrets in Visited and Home domains.](410562339ce067fdc6fa41940c118658_img.jpg)
+
+The diagram illustrates the security architecture for a mobility H.323 environment, showing functional entities and shared secrets across two domains: Visited domain and Home domain.
+
+**Visited domain:** Contains functional entities MT (Mobile Terminal), V-GK (Visited Gatekeeper), MRP (Mobility Registration Protocol), and V-BE (Visited Border Element). The MT is connected to the V-GK. The V-GK, MRP, and V-BE are grouped within a dashed box.
+
+**Home domain:** Contains functional entities H-BE (Home Border Element), MRP (Mobility Registration Protocol), AuF (Authentication Function), MRP (Mobility Registration Protocol), H-GK (Home Gatekeeper), and MT (Mobile Terminal). The H-BE, MRP, AuF, MRP, and H-GK are grouped within a dashed box. The MT is connected to the H-GK.
+
+**Shared secrets and keys:**
+
+- Dynamic link key K (between MT and V-GK, and between H-GK and MT)
+- Shared secret ZZ4 (between V-GK and MRP)
+- Shared secret ZZ5 (between MRP and V-BE)
+- Shared secret ZZ2 (between V-BE and H-BE)
+- Shared secret ZZ6 (between H-BE and MRP)
+- Shared secret ZZ3 (between MRP and AuF)
+- Shared secret ZZ7 (between AuF and MRP)
+- Shared secret ZZ8 (between MRP and H-GK)
+
+**Groupings:**
+
+- User password/Shared secret ZZ (grouping ZZ4, ZZ5, ZZ2, ZZ6, ZZ3)
+- MT shared secret ZZMT (grouping ZZ7, ZZ8)
+
+T1610770-02
+
+Diagram of security architecture for mobility H.323 environment showing functional entities and shared secrets in Visited and Home domains.
+
+**Figure 1/H.530 – Security architecture for mobility H.323 environment**
+
+It is assumed that the MT and the AuF in the home domain share an administered password ZZ that is assigned during the user's subscription process. Further on, the V-GK and the next functional element one hop away (e.g. a MRP) share a shared secret ZZ4, and the MRP shares a shared secret ZZ5 with V-BE. As an example, if a MRP does not occur in a particular environment, then a shared secret shall be assumed between the V-GK and the V-BE accordingly and the security protection of relayed messages shall be applied accordingly.
+
+It is assumed that the H-BE and a MRP share a shared secret ZZ6 and the MRP shares a shared secret ZZ3 with the AuF. Among the domains, there is a shared secret ZZ2 assumed between V-BE and H-BE or there should be IPSEC or other appropriate network security protection as a generic security means. The shared secrets ZZ2-ZZ6 may be applied for security protection of the H.501 [3] mobility management protocol or may serve as shared secret for underlying IPSEC. While the user
+
+password and the shared secrets *ZZ2-ZZ6* and *ZZMT* are statically administered, the link key *K* is dynamically assigned as part of the signalling and authentication procedure. The dynamic link key *K* is shared between the MT and the V-GK.
+
+As described in 8.5, the AuF and the MRP share a shared secret *ZZ7* and the MRP and the H-GK share a shared secret *ZZ8*.
+
+NOTE 1 – This security architecture depends on trusted intermediate nodes. This means that any intermediate nodes such as V-BE and H-BE and potentially also MRP, AuF and GK may read and intercept signalling information in transit that is not actually targeted for them. This should not be a real issue as long as there is full trust assumed within a domain and, further, a tight, mutual trust relationship between visited domain and home domain with no other intermediate domains involved in the H.323 communication [5] in-between these two domains.
+
+NOTE 2 – Generally, using shared secrets limits scalability; thus, only a small number of domains and BE nodes may use this principle in controlled environments. For example, it is anticipated that the security architecture described in this Recommendation scales up to a number of approximately 500 network domains such as proved feasible in the GSM networks. It is assumed that the security architecture herein would not scale well beyond significantly more network domains than those say 500. Thus, support for a large-scale secure mobility environment is left for further study.
+
+## 8.1 Assumptions
+
+The H.530 security protocol deployed in this Recommendation, when used in conjunction with H.501 [3], assumes synchronized time on each leg in case of Annex D/H.235 [4] techniques applied at the application layer (i.e. V-GK-to-MRP, MRP-to-V-BE, V-BE-to-H-BE, H-BE-to-MRP and MRP-to-AuF). In case of network or transport security techniques applied on those links, synchronized time among the listed entities is not required. The security architecture further assumes synchronized time clocks between the MT and the AuF in the home domain. This could be achieved through NTP (IETF RFC 1305, [8]) or SNTP (IETF RFC 2030, [9]) time and clock synchronization protocols for example.
+
+NOTE – No time synchronization is assumed between the MT and any visited GK. For mutual authentication of the MT and the visited GK, challenge-response security techniques are deployed. No time synchronization is required for IPSEC security protection of H.501 [3].
+
+The H.225.0 RAS [1] protocol shall be applied for signalling communication between MT and V-GK, while the H.501 [3] mobility management protocol shall be applied between any other functional entities shown. H.501 [3] shall use H.235 [4] signalling facilities for message security protection and secured mobility management and may in addition use IPSEC for enhanced security.
+
+## 8.2 Secure location updating procedures
+
+While the MT and the visited GK usually never had any contact before and thus cannot deploy common subscription information, the visited GK when receiving an initial message from the MT is not able at first to immediately authenticate the MT, and vice versa. For this reason, the V-GK relays the task of MT user authentication and authorization to the AuF in the domain where the MT user is subscribed. The AuF shall perform the user/MT authentication and decide upon the authorization. The AuF responds with the result of the security verification and delivers security information such as credentials towards the visited GK and towards the MT for the session.
+
+Since the authentication and authorization query to the AuF usually only occurs when the MT and the user initially attach to the visited domain, there is no immediate need to execute this procedure at any later point in time during the same call/session, unless explicitly deemed adequate by the V-GK security policy. Thus, the V-GK is able to operate autonomously from the AuF once having received the authorization credentials. This makes the V-GK behave as a local operating security server in the visited domain.
+
+This Recommendation supports two procedures for secure location updating.
+
+Both procedures occur during initial authentication: It is common to both procedures that authentication is identical using **AuthenticationRequest** and **AuthenticationConfirmation** beyond the visited GK. The only difference between the two is that either the **GRQ** or the **RRQ** message is applied.
+
+- Authentication during the V-GK discovery phase: This procedure is applicable when the MT has already an endpoint ID and knows a priori the visited gatekeeper identifier. In this case, it is possible to secure the **GRQ** message according to Annex D; see Figure 2.
+- Authentication during the MT and user registration: This procedure applies when the MT does not know the visited gatekeeper identifier and does not yet have an endpoint ID assigned. Thus, MT and GK first complete the discovery procedure (insecure) and thereby exchange their IDs. After that, the MT and user authenticate when sending initial **RRQ**; see Figure 3.
+
+![Sequence diagram of H.530 authentication and key management during GK discovery phase. The diagram shows interactions between H.323 MT, V-GK, MRP, V-BE, H-BE, and AuF. The MT sends a GRQ message to the V-GK. The V-GK computes DH and sends an AuthenticationRequest to the MRP. The MRP forwards it through V-BE and H-BE to the AuF. The AuF sends an AuthenticationConfirmation back through the chain. The V-GK then sends a GCF message to the MT. The MT computes K and W, and sends an RRQ message to the V-GK. The V-GK sends an RCF message back to the MT.](724c7777b608e53be38b12b6fb3c43bc_img.jpg)
+
+The diagram illustrates the following sequence of events:
+
+- The H.323 MT computes DH:  $g^x \bmod p$  and sends message 1) GRQ( $EP_{ID}$ ,  $GK_{ID}$ , 0,  $CH_1$ ,  $T_1$ ,  $g^x$ , HMAC $_{ZZ}$ (GRQ)) to the V-GK.
+- The V-GK computes DH:  $g^y \bmod p$  and  $W := g^x \oplus g^y$ . It sends message 3) to the MRP.
+- The MRP sends message 4) to the V-BE.
+- The V-BE sends message 5) to the H-BE.
+- The H-BE sends message 6) to the MRP.
+- The MRP sends message 7) to the AuF.
+- The AuF sends message 8) back to the MRP.
+- The MRP sends message 9) back to the H-BE.
+- The H-BE sends message 10) back to the V-BE.
+- The V-BE sends message 11) back to the MRP.
+- The MRP sends message 12) back to the V-GK.
+- The V-GK sends message 13) GCF( $GK_{ID}$ ,  $EP_{ID}$ ,  $CH_1$ ,  $CH_2$ ,  $(T_{13})$ ,  $g^y$ , HMAC $_{ZZ}$ (W), HMAC $_{ZZ}$ ( $GK_{ID}$ ), HMAC $_K$ (GCF)) to the MT. The MT computes  $K := g^{xy} \bmod p$  and  $W := g^x \oplus g^y$ .
+- The MT sends message 14) RRQ( $EP_{ID}$ ,  $GK_{ID}$ ,  $CH_2$ ,  $CH_3$ ,  $(T_{14})$ , HMAC $_K$ (RRQ)) to the V-GK.
+- The V-GK sends message 15) RCF( $GK_{ID}$ ,  $EP_{ID}$ ,  $CH_3$ ,  $CH_4$ ,  $(T_{15})$ , HMAC $_K$ (RCF)) back to the MT.
+
+A shaded region labeled "AuthenticationRequest" and "AuthenticationConfirmation" encompasses steps 3 through 12. A label T1610780-02 is present in the bottom right of the diagram area.
+
+Sequence diagram of H.530 authentication and key management during GK discovery phase. The diagram shows interactions between H.323 MT, V-GK, MRP, V-BE, H-BE, and AuF. The MT sends a GRQ message to the V-GK. The V-GK computes DH and sends an AuthenticationRequest to the MRP. The MRP forwards it through V-BE and H-BE to the AuF. The AuF sends an AuthenticationConfirmation back through the chain. The V-GK then sends a GCF message to the MT. The MT computes K and W, and sends an RRQ message to the V-GK. The V-GK sends an RCF message back to the MT.
+
+Figure 2/H.530 – Authentication and key management during GK discovery phase
+
+![Sequence diagram for H.530 authentication and key management during registration phase. Lifelines: H.323 MT, V-GK, MRP, V-BE, H-BE, MRP, AuF. The process involves GRQ, GCF, RRQ, RIP, RCF, ARQ, and ACF messages with associated cryptographic computations like DH, HMAC, and XOR.](fa859e4e468bfb2710a94527f2c504af_img.jpg)
+
+The diagram illustrates the authentication and key management process during the registration phase of H.530. It involves the following sequence of interactions:
+
+- H.323 MT** sends **GRQ( $EP_{ID}$ )** to **V-GK**.
+- V-GK** responds with **GCF( $GK_{ID}$ )**.
+- H.323 MT** computes  $DH: g^x \bmod p$  and sends **1) RRQ( $EP_{ID}$ ,  $GK_{ID}$ , 0,  $CH_1$ ,  $T_1$ ,  $g^x$ ,  $HMAC_{ZZ}(RRQ)$ )** to **V-GK**.
+- V-GK** computes  $DH: g^y \bmod p$  and  $W := g^x \oplus g^y$ .
+- V-GK** sends **2) RIP(...)** to **H.323 MT**.
+- V-GK** sends **AuthenticationRequest( $RRQ(\dots)$ ,  $GK_{ID}$ ,  $W$ ,  $HMAC$ )** to **MRP**.
+- MRP** relays it to **V-BE** (3), **H-BE** (4), **MRP** (5), and **AuF** (6).
+- AuF** sends responses back through the chain: **MRP** (7), **H-BE** (8), **V-BE** (9), **MRP** (10), and **V-GK** (11).
+- V-GK** computes  $K := g^{xy} \bmod p$  and sends **AuthenticationConfirmation( $HMAC_{ZZ}(W)$ ,  $HMAC_{ZZ}(GK_{ID})$ ,  $HMAC$ )** to **H.323 MT** (12).
+- H.323 MT** receives **13) RCF( $GK_{ID}$ ,  $EP_{ID}$ ,  $CH_1$ ,  $CH_2$ ,  $(T_{13})$ ,  $g^y$ ,  $HMAC_{ZZ}(W)$ ,  $HMAC_{ZZ}(GK_{ID})$ ,  $HMAC_K(RCF)$ )** from **V-GK**.
+- H.323 MT** computes  $K := g^{xy} \bmod p$  and  $W := g^x \oplus g^y$ .
+- H.323 MT** sends **14) ARQ( $EP_{ID}$ ,  $GK_{ID}$ ,  $CH_2$ ,  $CH_3$ ,  $(T_{14})$ ,  $HMAC_K(ARQ)$ )** to **V-GK**.
+- V-GK** sends **15) ACF( $GK_{ID}$ ,  $EP_{ID}$ ,  $CH_3$ ,  $CH_4$ ,  $(T_{15})$ ,  $HMAC_K(ACF)$ )** to **H.323 MT**.
+
+T1610790-02
+
+Sequence diagram for H.530 authentication and key management during registration phase. Lifelines: H.323 MT, V-GK, MRP, V-BE, H-BE, MRP, AuF. The process involves GRQ, GCF, RRQ, RIP, RCF, ARQ, and ACF messages with associated cryptographic computations like DH, HMAC, and XOR.
+
+**Figure 3/H.530 – Authentication and key management during registration phase**
+
+Secure location updating occurs either:
+
+- when a user and an MT contact a visited domain for the first time without any prior information available in the visited domain; or
+- when there already is some temporary information available about the MT and the user in the visited domain.
+
+The former case requires full execution of the authentication procedures whereby the visited domain gathers sufficient information from the home domain in order to serve the MT. This procedure includes reporting results of the authentication, authorization check, and credentials by the home domain. This procedure may further carry service profile information towards the visited gatekeeper. It is to be noted that such procedure usually involves network communication and interaction with potentially several entities, and therefore might take some time to complete.
+
+The latter case would not make it necessary for the V-GK to contact the home domain, although this is not precluded. The visited gatekeeper would reuse locally stored information without contacting the home domain. This could happen in case of a lost and re-established connection, or of a local change of the network point of attachment. Whenever the MT possesses a valid link key, the MT shall attempt to use it first before falling back to deploying an initial location update.
+
+Primarily, the user authenticates explicitly by applying the password, which the user obtained at subscription time. However, for mobile terminal authentication, it may optionally also be possible that the MT authenticates additionally towards the AuF (see the procedure described in 8.3).
+
+Basically, the secure location updating procedure proceeds as follows: The initial RAS message that the visited GK receives is encapsulated in an **AuthenticationRequest** and relayed through one or several functional entities to the AuF in the home domain. This is done because the visited GK is not able to authenticate the MT and the user. The AuF verifies the relayed information, authenticates the MT/user and then decides upon the MT/user's authorization using some criterion. Alternatively, the AuF may remember the MT/user and shall deliver result of the authentication and authorization check by credentials towards the V-GK and MT using **AuthenticationConfirmation/AuthenticationRejection**.
+
+The visited domain authenticates towards the MT/user when delivering the dynamic link key, in response to the challenge of the MT. The MT/user authenticates with any subsequent RAS message towards the V-GK using challenge and response techniques. Likewise, the MT is able to authenticate the V-GK.
+
+Due to the principle of hop-by-hop security, it is necessary for any intermediate nodes or proxies to verify the applied H.235 [4] security on each leg and re-compute the **CryptoToken** with the message digest anew, as long as network or transport security means are not available. If network or transport security means are available, then re-computation of the message digest in the **CryptoToken** may be omitted.
+
+As the execution of the authentication procedures and network communication between V-GK and AuF may take some time, it may be necessary for the V-GK to send a **RIP** message to the MT indicating that the request is in progress.
+
+The diagrams in Figures 4 through 10 depict the message flow and emphasize H.235 [4] security. The depicted message flow is given for the scenario where the authentication occurs during the registration phase. A similar description applies to the procedures when secure location updating occurs during V-GK discovery; in this case, the encapsulated **RRQ** is to be substituted with **GRQ**. The signalling elements for the optional MT authentication are defined in 8.3 and for simplicity they are not shown in most of the figures. For reasons of space and clarity, the message flow is separated into several phases – each in a separate figure – that all belong together. A logical end-to-end message flow results when reading the numbered messages in sequence.
+
+### 8.2.1 MT to V-GK
+
+Figure 4 shows the initial registration phase between the MT and the visited GK. Each RAS message conveys a new challenge and the previous challenge value. Except for the first message, the HMAC message integrity check value serves as the computed response to the previous challenge; that HMAC shall be computed according to Annex D/H.235 [4] using the dynamic link key *K* as shared secret. The computation of the HMAC shall follow Procedure I of D.6.3.2/H.235 [4]; without using the **timeStamp** field. If the MT or the visited GK include timestamps anyway (such as  $T_{13}$ ,  $T_{14}$  and  $T_{15}$ ), then these timestamps should not be checked because synchronized time cannot be assumed between MT and V-GK.
+
+![Sequence diagram showing the initial registration phase and further RAS messages between MT and V-GK. The diagram includes message exchanges 1) through 15) and cryptographic computations for Diffie-Hellman key exchange.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MT
+    participant V-GK
+    Note left of MT: compute DH:  $g^x \bmod p$ 
+    MT->>V-GK: 1) RRQ(..., EPID, GKID, 0, CH1, T1,  $g^x$ , HMAC-SHA1(ZZ, RRQ()))
+    Note right of V-GK: Compute DH:  $g^y \bmod p$   
+ $W := g^x \oplus g^y$ 
+    V-GK-->>MT: 2) RIP(...)
+    Note right of V-GK: 3) ...
+    Note right of V-GK: Compute link key  $= g^{xy} \bmod p$ 
+    V-GK-->>MT: 12) ...
+    Note right of V-GK: 13) RCF(..., GKID, EPID, CH1, CH2, (T13),  $g^y$ ,  
+WT(HMACZZ(W), HMACZZ(GKID)), HMAC-SHA1(K, RCF()))
+    Note left of MT: Compute link key  $K = g^{xy} \bmod p$   
+ $W := g^x \oplus g^y$ 
+    MT->>V-GK: 14) ARQ(..., EPID, GKID, CH2, CH3, (T14), HMAC-SHA1(K, ARQ()))
+    V-GK->>MT: 15) ACF(..., GKID, EPID, CH4, CH5, (T15), HMAC-SHA1(K, ACF()))
+    Note right of V-GK: T1610800-02
+
+```
+
+Sequence diagram showing the initial registration phase and further RAS messages between MT and V-GK. The diagram includes message exchanges 1) through 15) and cryptographic computations for Diffie-Hellman key exchange.
+
+**Figure 4/H.530 – Initial registration phase and further RAS messages  
+between MT and V-GK**
+
+For the initial registration, the MT shall generate a fresh challenge CH<sub>1</sub> and include it in the **challenge** field in the **ClearToken** of the **RRQ**, see message 1). The **password** field in the **ClearToken** shall convey the previous challenge value. For the initial **RRQ/GRQ**, the previous challenge shall be set to all zeros.
+
+Further, the MT shall generate a fresh Diffie-Hellman half-key  $g^x \bmod p$  with random  $x$  kept secret and include the half-key in the **halfkey** field of the **dhkey** field within the **ClearToken** of the message. The applied prime number shall be included in **modsize** while the Diffie-Hellman generator shall be included in **generator** of that **ClearToken**. For the Diffie-Hellman (DH) system parameters, the available parameters as given in Table D.4/H.235 [4] shall be taken, where Generator is 2 and the 1024-bit mod-P prime referred to by "Z" are recommended.
+
+The V-GK receives the challenged **RRQ** and encapsulates it in **applicationMessage** within an **AuthenticationRequest**, see message 3) and sends it to the next hop (e.g. MRP).
+
+The V-GK shall generate a fresh Diffie-Hellman half-key  $g^y \bmod p$  with random  $y$  kept secret. For the Diffie-Hellman system parameters, the available parameters as given in Table D.4/H.235 [4] shall be taken; where Generator is 2 and the 1024-bit mod-P prime referred to by "Z" are recommended.
+
+Taking the received Diffie-Hellman half-key  $g^x \bmod p$  and its own Diffie-Hellman half-key  $g^y \bmod p$ , the V-GK shall compute a compound value  $W$  by bitwise XORing both values.
+
+This compound value  $W$  shall be included in the **halfkey** field of the **dhkey** field within a separate mobility **ClearToken** of the **AuthenticationRequest** message. The **generalID** of that **ClearToken** shall convey the  $GK_{ID}$ . The **tokenOID** of that mobility **ClearToken** shall be set to "G2". Any other parameters in that mobility **ClearToken** shall be unused. The AuF will authenticate this **ClearToken** information and compute the corresponding credentials. The mobility **ClearToken** is shown as **WT()**.
+
+The **AuthenticationRequest** message shall convey integrity protection according to Annex D/H.235 [4], unless the link between the V-GK and the next hop (e.g. MRP) is secured by IPSEC.
+
+NOTE 1 – As the mobility **ClearToken** is integral part of the **AuthenticationRequest** message, full message integrity protection already covers the integrity of any conveyed **Clear** and/or **CryptoTokens**. Thus, no separate protection of the mobility **ClearToken** is necessary.
+
+The V-GK may submit an unsecured **RIP** message to the MT to indicate message processing in progress, see message 2). Due to the fact that the MT and visited GK do not share a common secret yet, the V-GK is not able to authenticate and integrity protect this immediate **RIP** message.
+
+NOTE 2 – The MT should not trust unprotected **RIP** messages as they might not be authentic, they might be replayed or stem from denial-of-service attacks. The MT should be prepared to treat replayed **RIP** messages and cope with potential message flooding. It is up to the security policy of the MT how to treat such unprotected **RIP** messages.
+
+Until the **RCF** is submitted as message 13), the V-GK has time to compute the dynamic link  $K$  using the Diffie-Hellman half-key of the MT and its own secret  $y$ . For HMAC-SHA1-96 message integrity protection of the H.225.0 RAS [1] messages, the 96 leftmost bits shall be taken from the resulting Diffie-Hellman shared secret as represented in network byte order.
+
+The V-GK receives an **AuthenticationConfirmation/AuthenticationRejection** with the result of the authentication and authorization check by the AuF and conveyed credentials; see message 12).
+
+The V-GK may supervise reception of **AuthenticationConfirmation/AuthenticationRejection** messages using a timer. The timer duration should be chosen long enough by taking the network transit and the AuF processing into account. If the timer expires and the corresponding reply from the AuF has not arrived, the V-GK shall send an unprotected **RCF**.
+
+The V-GK shall generate a new challenge  $CH_2$  and build **RCF**. The **RCF** shall convey the previous challenge  $CH_1$  within **password**, a new challenge  $CH_2$  within **challenge** within the **ClearToken** inside the **CryptoToken** of **RCF**. That **ClearToken** shall also convey the computed Diffie-Hellman half-key of the V-GK in the **halfkey** field of the **dhkey** field within the **ClearToken** of that message. The applied prime number shall be included in **modsize** while the DH-generator shall be included in **generator** of that **ClearToken**.
+
+Further, the V-GK shall forward the credentials from the AuF to the MT. The credentials encompass the mobility **ClearToken** shown as **WT()**. This mobility **ClearToken** conveys on one hand the authenticated compound value  $W$  in the **halfkey** field of the **dhkey** field and on the other hand the authenticated V-GK ID. The **tokenOID** shall be set to "G2" and any other parameters in that mobility **ClearToken** shall be unused.
+
+The V-GK computes the HMAC upon the entire **RCF** message using the link key  $K$ . Thus, the HMAC serves as a response to the previous challenge according to Annex D/H.235 procedure I [4], see message 13).
+
+In addition to the authorization check performed by the AuF, the visited GK may decide by its own criteria on whether to allow or disallow the MT. Thus, the visited GK may reject a **GRQ/RRQ** even if the AuF confirmed authentication and authorization. In such a case, the visited GK shall respond with a **GRJ/RRJ** indicating the **reason** according to B.2.2/H.235 [4].
+
+The MT receives the protected **RCF** with challenges, Diffie-Hellman half-key and credentials such as the authenticated compound value  $W$  and authenticated  $GK_{ID}$ ; see message 13). The MT extracts these parameters from the mobility **ClearToken**. The MT shall compute the dynamic link key  $K$  in an analogue fashion as the V-GK did and as described above. The MT shall verify the HMAC as response of the entire **RCF** message using the link key  $K$ . The MT shall compute the compound value  $W$  by bitwise XORing the received  $g^y \bmod p$  and its own  $g^x \bmod p$ . The MT shall verify the correctness of the authenticated compound value  $W$  in the **halfkey** field in the mobility **ClearToken** by applying the shared secret  $ZZ$ . The MT shall verify the correctness of the authenticated  $GK_{ID}$  in the **generator** field in the mobility **ClearToken** by applying the shared secret  $ZZ$ . If the authenticity of either value cannot be proved, the link key  $K$  or the V-GK cannot be assumed to be authentic either. This may indicate fraudulent network entities or failed authentication in general. In this case, the MT shall ignore the **RCF** and restart again with a fresh **RRQ**.
+
+In case the V-GK receives an **AuthenticationRejection** and indicated **reason**, then the V-GK shall send an **RRJ** to the MT, see message 13). The security **reason** indicates a security error, as the AuF probably was not able to identify the MT/user. The V-GK shall then forward this error in **RRJ reason**.
+
+As MT and V-GK do not share synchronized clocks, any optional timestamps conveyed within a RAS message shall be ignored.
+
+NOTE 3 – Since the V-GK cannot authenticate an initial unprotected **GRQ/RRQ** message, they might be replayed or stem from denial-of-service attacks. Visited gatekeepers receiving an unexpectedly high number of protected or unprotected RAS messages may assume a denial-of-service attack and immediately refuse further message processing.
+
+### 8.2.2 V-GK to MRP
+
+The communication between the V-GK and the next hop functional element (e.g. MRP) serves the following purposes:
+
+- relaying authentication and authorization of the MT and user towards the AuF;
+- relaying authorization confirmation from the AuF towards the MT.
+
+Figure 5 shows the protocol message flow. The **AuthenticationRequest** message 2) entirely carries the **RRQ/GRQ** RAS message as received from the MT. Further, the **AuthenticationRequest** message carries a mobility **ClearToken** conveying compound value  $W$  and the  $GK_{ID}$ . The mobility **ClearToken** is shown as **WT()**. If authentication of the MT is performed, the V-GK includes a separate **CryptoToken** for that purpose; see 8.3.
+
+![Sequence diagram showing the transmission of authentication information between V-GK and MRP. The diagram includes steps 1) through 14). Step 1) is an incoming request to V-GK. V-GK computes DH: g^y mod p and W := g^x ⊕ g^y. Step 3) is an AuthenticationRequest message from V-GK to MRP. Step 4) is a response from MRP. Step 11) is another response from MRP. Step 12) is an AuthenticationConfirmation message from MRP to V-GK. V-GK then computes the link key K = g^xy mod p. Steps 13) and 14) are outgoing messages from V-GK. The diagram is labeled T1610810-02.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg)
+
+1) ...
+
+Compute DH:  $g^y \bmod p$
+
+$W := g^x \oplus g^y$
+
+3) AuthenticationRequest (RRQ(..., EP<sub>ID</sub>, GK<sub>ID</sub>, 0, CH<sub>1</sub>, T<sub>1</sub>, HMAC<sub>1</sub>), T<sub>3</sub>,  
+WT(GK<sub>ID</sub>, W),  
+HMAC-SHA1(ZZ4, T<sub>3</sub>, Authentication Request (...)))
+
+4) ...
+
+11) ...
+
+12) AuthenticationConfirmation (... , T<sub>12</sub>,  
+WT(GK<sub>ID</sub>, EP<sub>ID</sub>, HMAC<sub>ZZ</sub>(GK<sub>ID</sub>), HMAC<sub>ZZ</sub>(W)),  
+HMAC-SHA1(ZZ4, T<sub>12</sub>, AuthenticationConfirmation (...)))
+
+Compute link key  $K = g^{xy} \bmod p$
+
+13) ...
+
+14) ...
+
+T1610810-02
+
+Sequence diagram showing the transmission of authentication information between V-GK and MRP. The diagram includes steps 1) through 14). Step 1) is an incoming request to V-GK. V-GK computes DH: g^y mod p and W := g^x ⊕ g^y. Step 3) is an AuthenticationRequest message from V-GK to MRP. Step 4) is a response from MRP. Step 11) is another response from MRP. Step 12) is an AuthenticationConfirmation message from MRP to V-GK. V-GK then computes the link key K = g^xy mod p. Steps 13) and 14) are outgoing messages from V-GK. The diagram is labeled T1610810-02.
+
+**Figure 5/H.530 – Transmission of authentication information between V-GK and MRP**
+
+In case the link between V-GK and MRP is not protected by network security (e.g. IPSEC), **AuthenticationRequest** shall be secured according to Annex D/H.235 [4] with a new timestamp T<sub>3</sub> and HMAC computed with key ZZ4. Otherwise, **AuthenticationRequest** message may not need security protection by Annex D/H.235 [4].
+
+**AuthenticationConfirmation** or **AuthenticationRejection** in message 12) carry the authenticated values from the AuF as credentials in a separate mobility **ClearToken** shown as **WT()**. If the link between V-GK and MRP is not protected by network security (e.g. IPSEC), **AuthenticationConfirmation** shall be secured according to Annex D/H.235 [4] with a new timestamp T<sub>12</sub> and HMAC with key ZZ4. Otherwise, **AuthenticationConfirmation/AuthenticationRejection** may not need security protection by Annex D/H.235 [4].
+
+The conveyed GK<sub>ID</sub> and EP<sub>ID</sub> within that mobility **ClearToken** allow the V-GK to associate the received **AuthenticationConfirmation/AuthenticationRejection** message with the corresponding **AuthenticationRequest** message.
+
+In case the V-GK does not have a service relationship with the MRP (e.g. missing key ZZ4), then the V-GK shall not send an **AuthenticationRequest** but rather respond with **AuthenticationRejection** and reason set to **noServiceRelationship**.
+
+### 8.2.3 MRP to V-BE
+
+A MRP (if present and the conveyed hop count is not exceeded and if a service relationship is present with the V-BE) shall forward the received **AuthenticationRequest** message to the V-BE; see message 4) in Figure 6. The forwarded message shall be secured according to Annex D/H.235 [4] with a new timestamp T<sub>4</sub> and HMAC computed with key ZZ5. Otherwise, **AuthenticationRequest** message may not need security protection by Annex D/H.235 [4].
+
+![Sequence diagram showing authentication information transmission between MRP and V-BE. The diagram includes messages 4, 11, and 12. Message 4 is an AuthenticationRequest from MRP to V-BE. Message 11 is an AuthenticationConfirmation from V-BE to MRP. Message 12 is a response from MRP. External messages 3, 5, 10, and 12 are also shown.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MRP
+    participant V-BE
+    Note left of MRP: 3) 
+    MRP->>V-BE: 4) AuthenticationRequest (RRQ(...), T4, WT(GKID, W), HMAC-SHA1(ZZ5, T4, Authentication Request (...)))
+    Note right of V-BE: 5) 
+    Note right of V-BE: 10) 
+    V-BE->>MRP: 11) AuthenticationConfirmation (..., T11, WT(GKID, EPID, HMACZZ(GKID), HMACZZ(W)), HMAC-SHA1(ZZ5, T11, AuthenticationConfirmation (...)))
+    Note left of MRP: 12) 
+
+```
+
+T1610820-02
+
+Sequence diagram showing authentication information transmission between MRP and V-BE. The diagram includes messages 4, 11, and 12. Message 4 is an AuthenticationRequest from MRP to V-BE. Message 11 is an AuthenticationConfirmation from V-BE to MRP. Message 12 is a response from MRP. External messages 3, 5, 10, and 12 are also shown.
+
+**Figure 6/H.530 – Transmission of authentication information between MRP and V-BE**
+
+A V-BE shall forward an **AuthenticationConfirmation** or an **AuthenticationRejection** to the MRP.
+
+**AuthenticationConfirmation** or **AuthenticationRejection** in message 11) carry the authenticated values as credentials from the AuF. If the link between V-BE and MRP is not protected by network security (e.g. IPSEC), **AuthenticationConfirmation/AuthenticationRejection** shall be secured according to Annex D/H.235 [4] with a new timestamp  $T_{11}$  and HMAC with key ZZ5. Otherwise, **AuthenticationConfirmation/AuthenticationRejection** may not need security protection by Annex D/H.235 [4].
+
+If the hop count is exceeded, then the MRP shall not send an **AuthenticationRequest** message, but it shall rather reply with the **AuthenticationRejection** with reason set to **hopCountExceeded**; (see message 12).
+
+In case the MRP does not have a service relationship with the V-BE (e.g. missing key ZZ5), then the V-GK shall not send an **AuthenticationRequest**, but it shall rather respond with **AuthenticationRejection** and reason set to **noServiceRelationship**; see message 12).
+
+### 8.2.4 V-BE to H-BE
+
+Figure 7 depicts the message flow between two BEs of two adjacent domains at the time of initial registration. Security may be realized either using IPSEC according to ITU-T Rec. H.501 [3] or by using the shared secret ZZ2 that is shared between V-BE and H-BE. In the latter case, the H.501 [3] message shall be secured according to Annex D/H.235 [4].
+
+![Sequence diagram showing authentication information transmission between V-BE and H-BE. The diagram includes messages 5, 10, and 11. Message 5 is an AuthenticationRequest from V-BE to H-BE. Message 10 is an AuthenticationConfirmation from H-BE to V-BE. Message 11 is a response from V-BE. External messages 4, 6, 9, and 11 are also shown.](b2ea162a0f53d5e0504b7d28346e0754_img.jpg)
+
+```
+
+sequenceDiagram
+    participant V-BE
+    participant H-BE
+    Note left of V-BE: 4) 
+    V-BE->>H-BE: 5) AuthenticationRequest (RRQ(...), T5, WT(GKID, W), HMAC-SHA1(ZZ2, T5, AuthenticationRequest (...)))
+    Note right of H-BE: 6) 
+    Note right of H-BE: 9) 
+    H-BE->>V-BE: 10) AuthenticationConfirmation (..., T10, WT(GKID, EPID, HMACZZ(GKID), HMACZZ(W)), HMAC-SHA1(ZZ2, T10, AuthenticationConfirmation (...)))
+    Note left of V-BE: 11) 
+
+```
+
+T1610830-02
+
+Sequence diagram showing authentication information transmission between V-BE and H-BE. The diagram includes messages 5, 10, and 11. Message 5 is an AuthenticationRequest from V-BE to H-BE. Message 10 is an AuthenticationConfirmation from H-BE to V-BE. Message 11 is a response from V-BE. External messages 4, 6, 9, and 11 are also shown.
+
+**Figure 7/H.530 – Transmission of authentication information between BEs**
+
+If the conveyed hop count is not exceeded and a service relationship is present with the H-BE, the H.501 [3] **AuthenticationRequest** message carries the entire **RRQ** including the related Clear- and CryptoTokens; see message 5). This is done to let the AuF validate the **RRQ** message and authenticate the user/MT. An H.501 [3] message is secured such that the entire message is integrity-protected similarly as described by Annex D/H.235, where the computed hash is stored in the **CryptoToken** of the **MessageCommonInfo**. BEs shall insert new timestamps ( $T_5$ ,  $T_{10}$ ) for each H.501 [3] message.
+
+The **AuthenticationConfirmation/AuthenticationRejection** carry the authenticated values as credentials from the AuF in a mobility **ClearToken** shown as **WT()**.
+
+In case the MT user is not authorized to use the mobile H.323 service, the AuF should send **AuthenticationRejection** with **reason** set to security. For any other security failure, the AuF shall set **reason** to an error as appropriate to B.2.2/H.235 [4].
+
+If the hop count is exceeded, then the V-BE shall not send an **AuthenticationRequest** message, but rather reply with the **AuthenticationRejection** with reason set to **hopCountExceeded**; see message 11).
+
+In case the V-BE does not have a service relationship with the H-BE (e.g. missing key ZZ2), then the V-BE shall not send an **AuthenticationRequest**, but rather respond with **AuthenticationRejection** and **reason** set to **noServiceRelationship**; see message 11).
+
+### 8.2.5 H-BE to MRP
+
+In case a MRP is present, the message flow proceeds according to Figure 8.
+
+![Sequence diagram showing the transmission of authentication information between H-BE and MRP. Message 6 is an AuthenticationRequest from H-BE to MRP containing RRQ, timestamp T6, and WT credentials. Message 9 is an AuthenticationConfirmation from MRP to H-BE containing timestamp T9 and various HMAC-protected credentials.](86b4670fc1a5a694821ee92b99c1209a_img.jpg)
+
+```
+
+sequenceDiagram
+    participant H-BE
+    participant MRP
+    Note left of H-BE: 5) ...
+    H-BE->>MRP: 6) AuthenticationRequest (RRQ(...), T6,  
+WT(GKID, W),  
+HMAC-SHA1(ZZ6, T6, AuthenticationRequest (...)))
+    Note right of MRP: 7) ...
+    MRP-->>H-BE: 8) ...
+    MRP->>H-BE: 9) AuthenticationConfirmation (..., T9,  
+WT(GKID, EPID, HMACZZ(GKID), HMACZZ(W)),  
+HMAC-SHA1(ZZ6, T9, AuthenticationConfirmation (...)))
+    Note left of H-BE: 10) ...
+
+```
+
+T1610840-02
+
+Sequence diagram showing the transmission of authentication information between H-BE and MRP. Message 6 is an AuthenticationRequest from H-BE to MRP containing RRQ, timestamp T6, and WT credentials. Message 9 is an AuthenticationConfirmation from MRP to H-BE containing timestamp T9 and various HMAC-protected credentials.
+
+**Figure 8/H.530 – Transmission of authentication information between H-BE and MRP**
+
+### 8.2.6 MRP to AuF
+
+Figure 9 shows the message flow between the MRP (if present, if the hop count is not exceeded and if a service relationship is present) and the AuF. If no MRP is present, then the previous network entity shall be substituted instead. Similar to the figures before, the shared secret ZZ3 secures the transmitted messages.
+
+![Sequence diagram showing the transmission of authentication information between MRP and AuF. The diagram includes three messages: 6) ... (incoming to MRP), 7) AuthenticationRequest (RRQ(0, CH1, T1, HMAC1), T7, WT(GKID, W), HMAC-SHA1(ZZ3, T7, AuthenticationRequest (...))) (MRP to AuF), and 8) AuthenticationConfirmation (... T8, WT(GKID, EPID, HMACZZ(GKID), HMACZZ(W)), HMAC-SHA1(ZZ3, T8, AuthenticationConfirmation (...))) (AuF to MRP). Message 9) ... is an outgoing response from MRP. A reference T1610850-02 is shown at the bottom right.](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MRP
+    participant AuF
+    Note left of MRP: 6) ...
+    MRP->>AuF: 7) AuthenticationRequest (RRQ(0, CH1, T1, HMAC1), T7, WT(GK_{ID}, W), HMAC-SHA1(ZZ3, T7, AuthenticationRequest (...)))
+    AuF-->>MRP: 8) AuthenticationConfirmation (..., T_8, WT(GK_{ID}, EP_{ID}, HMAC_{ZZ}(GK_{ID}), HMAC_{ZZ}(W)), HMAC-SHA1(ZZ3, T_8, AuthenticationConfirmation (...)))
+    Note left of MRP: 9) ...
+    Note right of AuF: T1610850-02
+  
+```
+
+Sequence diagram showing the transmission of authentication information between MRP and AuF. The diagram includes three messages: 6) ... (incoming to MRP), 7) AuthenticationRequest (RRQ(0, CH1, T1, HMAC1), T7, WT(GKID, W), HMAC-SHA1(ZZ3, T7, AuthenticationRequest (...))) (MRP to AuF), and 8) AuthenticationConfirmation (... T8, WT(GKID, EPID, HMACZZ(GKID), HMACZZ(W)), HMAC-SHA1(ZZ3, T8, AuthenticationConfirmation (...))) (AuF to MRP). Message 9) ... is an outgoing response from MRP. A reference T1610850-02 is shown at the bottom right.
+
+**Figure 9/H.530 – Transmission of authentication information between MRP and AuF**
+
+Upon reception of the **AuthenticationRequest**, the AuF may successively trust the other functional entities in the chain to have preserved the integrity of the conveyed **RRQ**; see message 7). The AuF shall verify the **AuthenticationRequest** and then verify the encapsulated **RRQ** as described by Annex D/H.235 procedure I [4]. The conveyed timestamp  $T_1$  indicates freshness of the **RRQ** and shall be checked.
+
+If the MT/user is known to the AuF and authorized, the AuF shall respond with **AuthenticationConfirmation**; see message 8). Further, if MT authentication is desired, the AuF shall verify the corresponding conveyed **CryptoToken**. Otherwise, when the MT/user cannot be authenticated or is unknown to the AuF, a protected **AuthenticationRejection** shall be submitted with a **reason** set to an appropriate error as defined in B.2.2/H.235 [4].
+
+When the AuF is not able to apply the shared secret **ZZ**, the computation of the authenticated values for the credentials as described below shall be omitted, and no such result shall be included in the **AuthenticationRejection** message. In that case, a mobility **ClearToken** is not present in the **AuthenticationRejection** message.
+
+Otherwise, the AuF shall also compute the credentials of the authenticated compound value  $W$  using HMAC-SHA1-96 key hash function and **ZZ** as the shared key. The authenticated compound value  $W$  shall be included in a separate mobility **ClearToken**, where the result is stored in the **halfkey** field of the **dhkey** field within that mobility **ClearToken**. Further, the AuF shall compute an authenticated  $GK_{ID}$  as another credential using HMAC-SHA1-96 key hash function and **ZZ** as the shared key. The result shall be included within **generator** in that **ClearToken**. The **generalID** shall convey the  $GK_{ID}$ , while the **sendersID** shall convey the  $EP_{ID}$  in that **ClearToken**. This shall allow the V-GK to associate an **AuthenticationConfirmation/AuthenticationRejection** with the corresponding **AuthenticationRequest** message. The **tokenOID** of that **ClearToken** shall be set to "G2" and any other parameters in that mobility **ClearToken** shall be unused. The mobility **ClearToken** is shown as **WT()**.
+
+A new timestamp  $T_8$  shall be used and the response message shall be secured by according to Annex D/H.235 procedure I [4] using the shared secret **ZZ3**; see message 8).
+
+If the hop count is exceeded, then the MRP shall not send an **AuthenticationRequest** message, but rather reply with the **AuthenticationRejection** with reason set to **hopCountExceeded**; see message 9).
+
+If the MRP does not have a service relationship with the AuF (e.g. missing key **ZZ3**), then the MRP shall not send an **AuthenticationRequest**, but rather respond with **AuthenticationRejection** and **reason** set to **noServiceRelationship**; see message 9).
+
+NOTE – The AuF is not able to fully authenticate the V-GK in a strict sense. This is because the V-GK is not able to cryptographically prove its identity. However, the AuF certifies by the credential whatever V-GK identity is submitted. Thus, the MT/user is assured that the V-GK with which the MT/user is talking is always the same one as has been certified during the authentication procedure.
+
+## 8.3 Terminal authentication
+
+Authentication of the mobile terminal (MT) is an additional, optional feature, which is supported in addition to authentication of the mobile user. MT authentication shall be used, when mobile user authentication alone is not considered sufficient and when the MT has a corresponding shared secret *ZZMT*. It is assumed that the mobile terminal owns an assigned shared secret *ZZMT*, which it shares with the AuF. Assignment and distribution of this shared secret is outside the scope of this Recommendation.
+
+Actually, two scenarios for MT authentication are supported:
+
+- The AuF to which the mobile user is subscribed is identical to the AuF that maintains the subscribed MTs. In this case, the AuF is able to authenticate and decide upon authorization both for the user and the MT.
+- The AuF to which the mobile user is subscribed is different from the AuF where the MT is subscribed. In this case, the **AuthenticationRequest** shall first be sent to the user's AuF. It is the responsibility of that user AuF to locate and contact the appropriate MT AuF that is responsible for the MT. Such an MT AuF may be located in a different domain. Any such communication and necessary security protection beyond the AuF or among AuFs are outside the scope of this Recommendation.
+
+Authentication of the mobile terminal is accomplished in conjunction with user authentication. For terminal authentication, a separate **CryptoToken** XT() is used. This **CryptoToken** is carried within the security fields of the user authentication messages of either **GRQ** or **RRQ**, depending on whether user and terminal authentication occurs during the discovery phase of the visited GK or during the registration phase; see 8.2.
+
+The mobile terminal authenticates itself towards the AuF by proving knowledge or possession of the shared secret *ZZMT*. This allows the AuF to verify correctness the provided **CryptoToken** and to acknowledge this property as part of the authorization response (**AuthenticationConfirmation/AuthenticationRejection**) back to the visited domain. Then, the visited domain can decide upon the authorization of the MT.
+
+The keyed HMAC-SHA1-96 algorithm is used as the cryptographic authentication function. The procedure deployed basically follows the procedure I of Annex D/H.235 [4] with the exception that the integrity check is computed just over the specific mobile terminal **CryptoToken**, instead of over the entire message as actually described by Annex D/H.235 procedure I [4].
+
+The specific **CryptoH323Token** for mobile terminal authentication shall contain the following fields:
+
+- **NestedCryptoToken** containing a **CryptoToken**, which itself contains the **cryptoHashedToken** containing the following fields:
+  - **TokenOID** set to:
+    - "G1" indicating the authentication/integrity computation includes only the contents of this **CryptoToken**.
+- **HashedVals** containing the **ClearToken** field used with the following fields:
+  - **TokenOID** set to:
+    - "T" indicating that **ClearToken** is being used for authentication/integrity (see D.11/H.235 [4]).
+
+- **timestamp** containing the time stamp.
+- **random** containing a monotonically increasing sequence number. This number allows to make unique two messages with the same timestamp (within the clock resolution).
+- **generalID** containing the identifier of the recipient (only in case of unicast messages). In this scenario, this is the identifier of the home domain.
+- **sendersID** contains the identifier of the sender. In this scenario, this is the endpoint identifier of the MT.
+- **Token** containing **HASHED** with the fields:
+  - **algorithmOID** set to "U" indicating HMAC-SHA1-96; (see D.11/H.235 [4]).
+  - **params** set to NULL.
+  - **hash** containing the authenticator computed using HMAC-SHA1-96. The authenticator shall be computed over the entire **CryptoH323Token**.
+
+The receiving AuF shall verify the found **CryptoToken**, which is conveying MT authentication. In case the verification check fails, the AuF shall consider the MT not as authorized. In this case, the AuF shall respond with **AuthenticationRejection** and reason set to **security**. For any other security failure, the AuF shall set **reason** to an error according to B.2.2/H.235 [4].
+
+Figure 10 shows the message flow for mobile terminal authentication during the registration phase of the mobile terminal. The specific **CryptoToken** for MT authentication is shown as XT().
+
+![Sequence diagram showing MT authentication between MT and V-GK. The diagram includes five main message exchanges: 1) RRQ from MT to V-GK with CryptoToken XT(); 2) RIP from V-GK to MT; 3) ... from V-GK to an external entity; 12) ... from the external entity to V-GK; 13) RCF from V-GK to MT; 14) ARQ from MT to V-GK; 15) ACF from V-GK to MT. Each message contains specific parameters and cryptographic tokens.](90ddb84c323b956e2d50a54d3f870566_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MT
+    participant V-GK
+    Note left of MT: 1) RRQ(..., EP_ID, GK_ID, 0, CH_1, T_1, g^x, XT(T_1, R_1, EP_ID, AuF-ID, ..., HMAC-SHA1(ZZMT, XT()), HMAC-SHA1(ZZ, RRQ()))
+    MT->>V-GK: 1) RRQ(...)
+    Note right of V-GK: 2) RIP(...)
+    V-GK-->>MT: 2) RIP(...)
+    Note right of V-GK: 3) ...
+    V-GK->>External: 3) ...
+    Note left of External: 12) ...
+    External-->>V-GK: 12) ...
+    Note right of V-GK: 13) RCF(..., GK_ID, EP_ID, CH_1, CH_2, (T_13), g^y, WT(HMAC_ZZ(W), HMAC_ZZ(GK_ID)), HMAC-SHA1(K, RCF()))
+    V-GK-->>MT: 13) RCF(...)
+    Note left of MT: 14) ARQ(..., EP_ID, GK_ID, CH_2, CH_3, (T_14), HMAC-SHA1(K, ARQ()))
+    MT->>V-GK: 14) ARQ(...)
+    Note right of V-GK: 15) ACF(..., GK_ID, EP_ID, CH_4, CH_5, (T_15), HMAC-SHA1(K, ACF()))
+    V-GK-->>MT: 15) ACF(...)
+  
+```
+
+T1610860-02
+
+Sequence diagram showing MT authentication between MT and V-GK. The diagram includes five main message exchanges: 1) RRQ from MT to V-GK with CryptoToken XT(); 2) RIP from V-GK to MT; 3) ... from V-GK to an external entity; 12) ... from the external entity to V-GK; 13) RCF from V-GK to MT; 14) ARQ from MT to V-GK; 15) ACF from V-GK to MT. Each message contains specific parameters and cryptographic tokens.
+
+**Figure 10/H.530 – MT authentication**
+
+The authentication procedure of the MT shall be done explicitly only during **GRQ** or **RRQ**. In any later RAS messages exchanged between the MT and the V-GK, MT authentication is done implicitly through the ongoing user authentication and message integrity. No particular means for further MT authentication are necessary.
+
+## 8.4 Unregistration
+
+A MT or V-GK upon reception of UCF shall release the link key  $K$ .
+
+## 8.5 Application of the symmetric security protocol in the home domain
+
+While the security mobility protocol described in this Recommendation would usually be deployed for MTs attached to foreign visited domains, this clause describes the case how this security mobility protocol may also be deployed for MTs attached to the home domain. This allows deployment of the mobility security protocol to be independent of where the MT actually attaches. It includes the case also for non-mobility environments, which nevertheless supports H.530.
+
+Figure 11 shows the scenario where an MT is attached to the home GK in the home domain and the authentication and authorization occurs during the registration phase. A similar scenario not shown is also possible, where the authentication and authorization occur during the gatekeeper discovery phase.
+
+![Sequence diagram of MT authentication in the home domain during registration phase. Entities: AuF, MRP (dashed), H-GK, H.323 MT. The diagram shows the flow of messages for registration, including GRQ, GCF, RRQ, RIP, RCF, ARQ, and ACF messages with associated cryptographic computations like DH key exchange and HMAC verification.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg)
+
+The sequence diagram illustrates the authentication and authorization process in the home domain. The entities involved are AuF (Authentication Function), MRP (Mobility Registration Proxy, optional), H-GK (Home Gatekeeper), and H.323 MT (Mobile Terminal). The process begins with the MT sending a GRQ (EP<sub>ID</sub>) to the H-GK, which responds with GCF (GK<sub>ID</sub>). The MT then computes a Diffie-Hellman (DH) value  $g^x \bmod p$  and sends an RRQ (EP<sub>ID</sub>, GK<sub>ID</sub>, 0, CH<sub>1</sub>,  $T_1$ ,  $g^x$ , HMAC<sub>ZZ</sub>(RRQ)) to the H-GK. The H-GK computes its own DH value  $g^y \bmod p$  and calculates  $W := g^x \oplus g^y$ . It then sends a RIP(...) message to the MT. The H-GK also sends an AuthenticationRequest (RRQ(...), GK<sub>ID</sub>,  $W$ , HMAC) to the AuF. The AuF responds with an AuthenticationConfirmation (HMAC<sub>ZZ</sub>( $W$ ), HMAC<sub>ZZ</sub>(GK<sub>ID</sub>), HMAC) to the H-GK. The H-GK then sends an RCF (GK<sub>ID</sub>, EP<sub>ID</sub>, CH<sub>1</sub>, CH<sub>2</sub>, ( $T_{13}$ ),  $g^y$ , HMAC<sub>ZZ</sub>( $W$ ), HMAC<sub>ZZ</sub>(GK<sub>ID</sub>), HMAC <sub>$\bar{K}$</sub> (RCF)) to the MT. The MT computes  $K := g^{xy} \bmod p$  and  $W := g^x \oplus g^y$ , then sends an ARQ (EP<sub>ID</sub>, GK<sub>ID</sub>, CH<sub>2</sub>, CH<sub>3</sub>, ( $T_{14}$ ), HMAC <sub>$K$</sub> (ARQ)) to the H-GK. Finally, the H-GK sends an ACF (GK<sub>ID</sub>, EP<sub>ID</sub>, CH<sub>3</sub>, CH<sub>4</sub>, ( $T_{15}$ ), HMAC <sub>$K$</sub> (ACF)) to the MT. The diagram also shows internal message flows between the AuF and H-GK (labeled 7, 8, 3, 12) and a reference code T1610870-02.
+
+Sequence diagram of MT authentication in the home domain during registration phase. Entities: AuF, MRP (dashed), H-GK, H.323 MT. The diagram shows the flow of messages for registration, including GRQ, GCF, RRQ, RIP, RCF, ARQ, and ACF messages with associated cryptographic computations like DH key exchange and HMAC verification.
+
+Figure 11/H.530 – MT authentication in the home domain during registration phase
+
+In any case, the H-GK shall behave exactly as a V-GK in the visited domain as shown in Figure 11 and following the security procedures respectively as described above. The shared secret ZZ4 shall be substituted by ZZ8, and ZZ3 by ZZ7, respectively.
+
+The MRP shown is an optional entity. When the MRP is not present, AuF and H-GK have a direct security relationship established. As a special case, AuF and H-GK may even be co-located, thus making communication between both entities a local issue.
+
+## 8.6 List of Object Identifiers
+
+Table 1 lists all the OIDs referenced in this Recommendation.
+
+**Table 1/H.530 – Object Identifiers used by H.530**
+
+| Object Identifier reference | Object Identifier value(s)                                | Description                                                                                                                                                                                                                                                      |
+|-----------------------------|-----------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| "G1"                        | {itu-t (0) Recommendation (0) h (8) 235 version (0) 2 10} | Used to indicate a mobility <b>CryptoToken</b> for authentication of the MT                                                                                                                                                                                      |
+| "G2"                        | {itu-t (0) Recommendation (0) h (8) 235 version (0) 2 11} | Used to indicate a mobility <b>ClearToken</b> that holds $GK_{ID}$ and compound value $W$ within <b>AuthenticationRequest</b> or the corresponding AuF-authenticated values within <b>AuthenticationConfirmation/AuthenticationRejection</b> or GCF/GRJ, RCF/RCF |
+
+## 9 End-to-end security
+
+An end-to-end security architecture in an H.323 mobility environment that is relying on a public-key infrastructure (PKI) concepts is subject of further study.
+
+
+
+## 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                                                                   |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                      |
+| 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/043e64d41a3368d138ace3816fd26469_img.jpg b/marked/H/T-REC-H.550-201712-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..67ae4a1ad401a9749d628d4e55ed8a129fd4fb31
--- /dev/null
+++ b/marked/H/T-REC-H.550-201712-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:19f63a8b3489ae041639cbb763cb18a545b5619560f6863733de983ce72dc068
+size 46312
diff --git a/marked/H/T-REC-H.550-201712-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg b/marked/H/T-REC-H.550-201712-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..514bf42d831b395edb8319ea26520ac02bab6899
--- /dev/null
+++ b/marked/H/T-REC-H.550-201712-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:33c9cd3b718daf99c25004cfbf9d63bc87a0193d2dd9b04b2f389ce7494f82a7
+size 47705
diff --git a/marked/H/T-REC-H.550-201712-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/H/T-REC-H.550-201712-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..128b733ce145a0b1f56676fa796670a9b3d39f53
--- /dev/null
+++ b/marked/H/T-REC-H.550-201712-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:efae7e9d29c3333d96ab823c015f9b1e1d276cb298ed9db675745e52d0a9a2e9
+size 157325
diff --git a/marked/H/T-REC-H.550-201712-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg b/marked/H/T-REC-H.550-201712-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9548e12445a206b7a6c442ae282a39f393d21758
--- /dev/null
+++ b/marked/H/T-REC-H.550-201712-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b3e1aab992a277c3efbb20aa293cac4ffb5817c6e818cf85d570a4f2c45cb113
+size 53349
diff --git a/marked/H/T-REC-H.550-201712-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg b/marked/H/T-REC-H.550-201712-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ef251266bde0dfd1c5640017b86ab505592a4c8b
--- /dev/null
+++ b/marked/H/T-REC-H.550-201712-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02275b011f7beb8f53648843c5bf0f81a62dbefabcdb38938b5e5a120f9d9aec
+size 39401
diff --git a/marked/H/T-REC-H.550-201712-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg b/marked/H/T-REC-H.550-201712-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4f87adae63eee65805045bdb2af44f28f7564339
--- /dev/null
+++ b/marked/H/T-REC-H.550-201712-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:38d8ba747a5fd4053683217c1c47b8b0886131fd533496ac97a65a9c3de98a81
+size 43359
diff --git a/marked/H/T-REC-H.550-201712-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.550-201712-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..61b15be46780132c54267e35b172ef1ecd6c5ece
--- /dev/null
+++ b/marked/H/T-REC-H.550-201712-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:057b6c42402cf4cabc37f224a8b1ee4415e0eb70b3a8f932892fa75306a4501e
+size 7201
diff --git a/marked/H/T-REC-H.550-201712-I_PDF-E/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/H/T-REC-H.550-201712-I_PDF-E/a0739aaf13fa5a632d4faa830f6b2708_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5b05bf70a71f9a156d842ca6e6789f21bc31ab08
--- /dev/null
+++ b/marked/H/T-REC-H.550-201712-I_PDF-E/a0739aaf13fa5a632d4faa830f6b2708_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e65a76bf9bebbb836dd8f94c74bde4618a8e6b7d5700cfd00706894c23339e40
+size 42267
diff --git a/marked/H/T-REC-H.550-201712-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.550-201712-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..890381e54c6aec6c74d72827e6bf5b4b2a072cbb
--- /dev/null
+++ b/marked/H/T-REC-H.550-201712-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d79e26692c03f0b928bc994dd69a6bd2d3e857cc339be1771beb6bf3e91df52
+size 193279
diff --git a/marked/H/T-REC-H.550-201712-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg b/marked/H/T-REC-H.550-201712-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b0d5872f35d43d3e35a60bd5f99bb0826b1503b3
--- /dev/null
+++ b/marked/H/T-REC-H.550-201712-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:238b046f49185952b1b533acc063d00351c218d4a17d3750ca57fca81c74af4f
+size 50449
diff --git a/marked/H/T-REC-H.550-201712-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg b/marked/H/T-REC-H.550-201712-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..069059b134d15af4fa7c6ebd72057b4aab944834
--- /dev/null
+++ b/marked/H/T-REC-H.550-201712-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:949923ac6294f4098a3ddbb4583265c8897fce1be34a6ef190cb30cfd9b92fc2
+size 79338
diff --git a/marked/H/T-REC-H.551-202201-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/marked/H/T-REC-H.551-202201-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dcba3e8f8bc5ee7fc12658431e85097f0a10a96d
--- /dev/null
+++ b/marked/H/T-REC-H.551-202201-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7f651886a7ed4c41c1a4693604ed37d3c24b3376e68e19352fbc2294af602a3b
+size 93319
diff --git a/marked/H/T-REC-H.551-202201-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.551-202201-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1e32f9b8f1141bed243c16e02a6cd1411cbb87f1
--- /dev/null
+++ b/marked/H/T-REC-H.551-202201-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.551-202201-I_PDF-E/220869911a1ecfa1dd4aa6d750319aad_img.jpg b/marked/H/T-REC-H.551-202201-I_PDF-E/220869911a1ecfa1dd4aa6d750319aad_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..896f77e3e352b472a57a1522be481d7ce1a62e41
--- /dev/null
+++ b/marked/H/T-REC-H.551-202201-I_PDF-E/220869911a1ecfa1dd4aa6d750319aad_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3b3e646b3d3ced1256a61a0e3d3db301c6484c1867745a37ec63bac1e02aecf3
+size 70610
diff --git a/marked/H/T-REC-H.551-202201-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg b/marked/H/T-REC-H.551-202201-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..69522c5d721f91c709584167ff3968f995f7b0a8
--- /dev/null
+++ b/marked/H/T-REC-H.551-202201-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3967f56749fa73378f9cb3338608e409da867327f94038416922d968b49e1ee4
+size 97796
diff --git a/marked/H/T-REC-H.551-202201-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/H/T-REC-H.551-202201-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b51fdf1a824a42af089a03c13c354c072f70534c
--- /dev/null
+++ b/marked/H/T-REC-H.551-202201-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:df9ce997fc504f67e96f05ee026f93cdaaa608c3ffcdb159b217e69ab1e0cd14
+size 153871
diff --git a/marked/H/T-REC-H.551-202201-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/H/T-REC-H.551-202201-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b30fd6d5c81f53133be1da7711ccc5794f0ec9a4
--- /dev/null
+++ b/marked/H/T-REC-H.551-202201-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cd26eb5e05392cda013b4f5780f7695ce7d0de2b8f4d1a4e03ef04dee23428a7
+size 70504
diff --git a/marked/H/T-REC-H.551-202201-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg b/marked/H/T-REC-H.551-202201-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cc1b9be5d2bbfa27ff95d683dc0e2c30538bff2f
--- /dev/null
+++ b/marked/H/T-REC-H.551-202201-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b7706d66afd1c5eeb6531f9c076287918ca68f762ab45ee9f57fae983dd8510e
+size 54702
diff --git a/marked/H/T-REC-H.553-202512-I_PDF-E/raw.md b/marked/H/T-REC-H.553-202512-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..375b8cb29e7a87b4e5a3665c73cfc63075f5b0fe
--- /dev/null
+++ b/marked/H/T-REC-H.553-202512-I_PDF-E/raw.md
@@ -0,0 +1,395 @@
+
+
+# Recommendation **ITU-T H.553 (12/2025)**
+
+SERIES H: Audiovisual and multimedia systems
+
+Vehicular gateways and intelligent transportation systems (ITS) – Architecture for vehicular gateways
+
+---
+
+## **Functional requirements and architecture of a vehicular multimedia system for heterogeneous access network selection**
+
+![ITU logo](0538daaa5583c23e17db3a12f2281a55_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        |
+| <b>Architecture for vehicular gateways</b>                      | <b>H.550-H.559</b> |
+| Vehicular gateway interfaces                                    | H.560-H.569        |
+| 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.553
+
+# Functional requirements and architecture of a vehicular multimedia system for heterogeneous access network selection
+
+## Summary
+
+Recommendation ITU-T H.553 specifies the functional requirements and architecture of a vehicular multimedia system for heterogeneous access network selection when connected vehicles support external communication networks, such as wireless wide area networks (WWAN) and wireless short-range communication networks.
+
+## History\*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T H.553    | 2025-12-14 | 21          | 11.1002/1000/16601 |
+
+## Keywords
+
+Connected vehicles, heterogeneous access network selection, VGP.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <https://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                                    | 2    |
+| 4 Abbreviations and acronyms .....                                               | 2    |
+| 5 Conventions .....                                                              | 2    |
+| 6 Introduction.....                                                              | 2    |
+| 7 Functional architecture .....                                                  | 3    |
+| 8 Functional requirements of heterogeneous access network management (HANM) .... | 4    |
+| 8.1 Requirements of network analysis.....                                        | 4    |
+| 8.2 Requirements of decision-making.....                                         | 5    |
+| 8.3 Requirements of data fusion and deduplication .....                          | 5    |
+| 9 Functional requirements of access network management (ANM) .....               | 5    |
+| 9.1 Requirements of access network monitor.....                                  | 5    |
+| 9.2 Requirements of access network selection .....                               | 6    |
+| 10 Functional requirements of network handover management (NHM).....             | 6    |
+| 10.1 Requirements of MIB .....                                                   | 6    |
+| 10.2 Requirements of network switch .....                                        | 6    |
+| 11 Interfaces of heterogeneous access network selection.....                     | 7    |
+| Bibliography.....                                                                | 8    |
+
+
+
+# Recommendation ITU-T H.553
+
+## Functional requirements and architecture of a vehicular multimedia system for heterogeneous access network selection
+
+## 1 Scope
+
+This Recommendation specifies the functional requirements and architecture of a vehicular multimedia system for heterogeneous access network selection. This Recommendation defines the following:
+
+- Functional architecture including heterogeneous access network selection;
+- Functional requirements of heterogeneous access network management;
+- Functional requirements of access network management;
+- Functional requirements of network handover management;
+- Interfaces of heterogeneous access network selection.
+
+## 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.550](#)] Recommendation ITU-T H.550 (2017), *Architecture and functional entities of vehicle gateway platforms*.
+
+# 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 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.2 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.3 vehicle gateway (VG)** [b-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 Quality of Service (QoS), arbitration and integration of network communications, security and switching network connections to maintain service continuity.
+
+**3.1.4 vehicle gateway platform (VGP)** [b-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:
+
+|       |                                               |
+|-------|-----------------------------------------------|
+| ANM   | Access Network Management                     |
+| CIEN  | Communication Interface for External Networks |
+| C-V2X | Cellular Vehicle-to-everything                |
+| HANM  | Heterogeneous Access Network Management       |
+| MIB   | Management Information Base                   |
+| NHM   | Network Handover Management                   |
+| QoS   | Quality of Service                            |
+| RSU   | Roadside Unit                                 |
+| VG    | Vehicle Gateway                               |
+| VGP   | Vehicle Gateway Platform                      |
+| WWAN  | Wireless Wide Area Network                    |
+
+## 5 Conventions
+
+In this Recommendation:
+
+- The keywords "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.
+
+# 6 Introduction
+
+With the rapid development of industry, connected vehicles can support ubiquitous connectivity to external communication networks. Meanwhile, the connected vehicles utilize peripheral equipment such as radars and cameras to collect data. Based on the vehicles' local processing and the cooperation with other vehicles, road infrastructure and cloud server, multiple application scenarios of vehicle systems have been implemented.
+
+To provide consistency and continuous service in a wider range of communication to users, the vehicle system supports both wireless wide area networks (WWANs) and wireless short-range communication networks for one same application. These two network types differ in their physical layer protocols, transmission rates, and quality of service (QoS) capabilities. Therefore, the vehicle system incorporates a unified functionality of network selection to manage the collaboration of different communication networks and process data from multiple communication networks to ensure reliable support for a specific application. For example, in the heterogeneous access network environment, the vehicle system can use both WWAN and a wireless short-range communication network to support a traffic lights application, so the vehicle system can receive traffic light
+
+information both from the cloud server through WWAN and from a roadside unit (RSU) through a wireless short-range communication network, as illustrated in Figure 1.
+
+![Figure 1: Overview of a multi-communication technology connection. The diagram shows a vehicle containing a VGP (Vehicle Gateway Platform) connected to cloud-based servers via a WWAN (Wide Area Network) and to an infrastructure unit (containing a traffic light and RSU) via wireless short-range communication.](acfc53eca625d62b38aa2563efa95c3e_img.jpg)
+
+The diagram illustrates a multi-communication setup. At the top, three blue cylinders represent 'Cloud-based servers'. Below them, a cellular tower icon represents 'WWAN'. At the bottom right, a dashed box labeled 'Vehicle' contains a blue rectangle labeled 'VGP' and a black car icon. At the bottom left, a dashed box labeled 'Infrastructure' contains a traffic light icon and a small building icon representing an RSU. A blue arrow points from the VGP up through the WWAN tower to the cloud servers. Another blue arrow points from the VGP to the RSU in the infrastructure box, labeled 'Wireless short-range communication'. A small label 'H.553(25)' is in the bottom right corner.
+
+Figure 1: Overview of a multi-communication technology connection. The diagram shows a vehicle containing a VGP (Vehicle Gateway Platform) connected to cloud-based servers via a WWAN (Wide Area Network) and to an infrastructure unit (containing a traffic light and RSU) via wireless short-range communication.
+
+**Figure 1 – Overview of a multi-communication technology connection**
+
+A heterogeneous access network is a network system composed of multiple wireless access technologies with distinct types and characteristics. These technologies exhibit significant differences in physical layer protocols, coverage range, transmission rates, QoS, and management mechanisms. Through collaborative integration, they achieve complementary advantages to provide users with seamless and high-efficiency communication services.
+
+Heterogeneous access network selection is the technical process of dynamically selecting the optimal access network for a vehicle's vehicle gateway platform (VGP), which supports multiple types of access network (e.g., IMT-2020 [b-ITU-R M.2150-2], cellular vehicle-to-everything (C-V2X), Wireless LAN, etc.) to meet user service requirements (such as bandwidth, latency, cost, etc.).
+
+Thus, it is important to define the functional requirements of network selection for heterogeneous access networks. The vehicle system has a unified requirement of network selection to manage the service, which can avoid inconsistent service issues from different communication networks due to delay or other problems. The vehicle system supports the functionality of different network quality analysis, and can process the receiving information, including data fusion and deduplication.
+
+## 7 Functional architecture
+
+Figure 2 presents the functional architecture and interfaces of a vehicular multimedia system for heterogeneous access network selection based on [ITU-T H.550]. The related new functionalities in the various subsystems of a VGP for heterogeneous access network selection include:
+
+- Heterogeneous access network management (HANM): It supports network selection and data processing in the session management functional entity, including network analysis, decision-making, data fusion and deduplication.
+- Access network management (ANM): It supports monitoring communication network status and selection of access network connections in the networking and transport functional entity. It includes access network monitor and access network selection.
+
+- Network handover management (NHM): It supports the storage of configuration and current status information, and the handover of access network connections. It includes the management information base (MIB) and network switch in the wired and wireless access management functional entity.
+
+![Functional architecture and interfaces of heterogeneous access network selection diagram](f4fdd410cdb84df81274da55721e56fb_img.jpg)
+
+The diagram illustrates the functional architecture and interfaces of heterogeneous access network selection. It is organized into three main layers: External application, Vehicle gateway platform (VGP), and Vehicle gateway (VG).
+
+- External application** and **SAM** are at the top, connected to the VGP via double-headed arrows.
+- Vehicle gateway platform (VGP)** contains three main functional blocks:
+  - Services**: Includes 'Software and application data management service', 'Driver-vehicle access (DVA) service', and 'Other services'.
+  - Service functionalities**: Includes 'Session management' (with 'Heterogeneous access network management' containing 'Network analysis', 'Decision-making', and 'Data fusion and deduplication') and 'In-vehicle resource access management'.
+  - Management**: Includes 'Device management', 'Security management', and 'Wired and wireless access management' (containing 'Network handover management', 'MIB', and 'Network switch').
+- Vehicle gateway (VG)** is at the bottom, containing:
+  - Networking and transport**: Includes 'Access network management' (with 'Access network monitor' and 'Access network selection').
+  - Communication interfaces**: Categorized into 'nomadic devices' (USB, Wireless LAN, Short range wireless), 'external networks' (Cellular, Wireless LAN, Short-to-medium range wireless), and 'in-vehicle networks' (Short-to-medium range wireless).
+
+**Interfaces:**
+
+- Chn** (dashed red double-headed arrow) connects 'Data fusion and deduplication' in Session management to 'Access network selection' in Access network management.
+- Cha** (dashed red double-headed arrow) connects 'Access network monitor' in Access network management to 'Network analysis' in Heterogeneous access network management.
+- Can** (dashed red double-headed arrow) connects 'Access network selection' in Access network management to 'Network handover management' in Wired and wireless access management.
+- Cac** (dashed red double-headed arrow) connects 'Access network monitor' in Access network management to 'Network switch' in Wired and wireless access management.
+
+**Legend:**
+
+- New function
+- ← - - - → New interface
+
+H.553(25)
+
+Functional architecture and interfaces of heterogeneous access network selection diagram
+
+**Figure 2 – Functional architecture and interfaces of heterogeneous access network selection**
+
+# 8 Functional requirements of heterogeneous access network management (HANM)
+
+HANM in the session management functional entity supports network selection and data processing, including network analysis, decision making, data fusion and deduplication.
+
+### 8.1 Requirements of network analysis
+
+The requirements for network analysis of the HANM function are as follows:
+
+NA-001 – Network analysis is required to analyse the availability of access networks and evaluate the available network capability (including maximum bandwidth, minimum latency and highest reliability).
+
+NA-002 – Network analysis is required to track the dynamic changes in external network state and evaluate the resource usage of the network.
+
+NA-003 – Network analysis is required to identify network misbehaviour, potential security threats and prevent unauthorized access.
+
+NA-004 – Network analysis is required to receive the information of network configuration (e.g., software and hardware parameters), network status (e.g., connection, disconnection) and QoS (including real-time bandwidth, throughput and packet loss rate) reported by the networking and transport layer.
+
+NA-005 – Network analysis is required to provide access to the MIB containing configuration and status information.
+
+### **8.2 Requirements of decision-making**
+
+The requirements for decision-making of the HANM are as follows:
+
+DM-001 – Decision-making is required to support access network selection based on service types, traffic characteristics and access network characteristics, and to deliver user data over the selected access network.
+
+DM-002 – Decision-making is required to support the mechanism or strategy to establish, manage and disconnect networks based on the results of network analysis.
+
+DM-003 – Decision-making is required to support the network handover triggering mechanism and resource conflict control mechanism to ensure service continuity.
+
+DM-004 – Decision-making is recommended to support the seamless handover mechanism between different access networks, minimize the interruption time and maintain ongoing communications during handover.
+
+DM-005 – Decision-making is recommended to support simultaneous data transmission via different access networks (e.g., dual connectivity).
+
+### **8.3 Requirements of data fusion and deduplication**
+
+The requirements for data fusion and deduplication of the HANM function are as follows:
+
+DFD-001 – Data fusion and deduplication are required to have the capability to receive multi-source data and identify the source of data delivery.
+
+DFD-002 – Data fusion and deduplication are required to have the capability of duplicate data detection and deduplication.
+
+DFD-003 – Data fusion and deduplication are required to support multi-source data processing, including pre-processing (e.g., filtering aged or inaccurate data), and fusion of data from different access networks according to the quality and source.
+
+DFD-004 – Data fusion and deduplication are required to have the capability to transmit the processed data to the corresponding services.
+
+# **9 Functional requirements of access network management (ANM)**
+
+ANM in the function entity of networking and transport supports to monitor communications network status and select access network connections, including access network monitor and access network selection.
+
+### **9.1 Requirements of access network monitor**
+
+The requirements for access network monitor of the ANM function are as follows:
+
+ANM-001 – The access network monitor is required to receive information regarding network configuration, network status and QoS reported by external communication networks.
+
+ANM-002 – The access network monitor is required to provide access to the MIB containing the configuration and status information.
+
+ANM-003 – The access network monitor is required to track the dynamic changes in external network state and evaluate the resource usage of the network.
+
+ANM-004 – The access network monitor is required to identify network misbehaviour, potential security threats and prevent unauthorized access.
+
+### **9.2 Requirements of access network selection**
+
+The requirements for access network selection of the ANM function are as follows:
+
+ANS-001 – The access network selection is required to analyse the availability of different access networks, and evaluate the available network capability (including bandwidth, latency and reliability).
+
+ANS-002 – The access network selection is required to select the access network to deliver application data as indicated by the function of heterogeneous access network management.
+
+ANS-003 – The access network selection is recommended to select the access network based on service types, traffic characteristics and access network characteristics, and deliver application data over the selected access network.
+
+ANS-004 – The access network selection is recommended to select the seamless handover mechanism among different access networks to minimize the interruption time and maintain ongoing communications during handover.
+
+ANS-005 – The access network selection is recommended to select two or more different access networks to simultaneously deliver application data (e.g., dual connectivity).
+
+## **10 Functional requirements of network handover management (NHM)**
+
+NHM in the wired and wireless management functional entity supports the storage of configuration and status information and the handover of access network connections, including management of the MIB and the network switch.
+
+### **10.1 Requirements of MIB**
+
+The requirements for MIB of NHM are as follows:
+
+MIB-001 – MIB is required to support real-time fault detection of different access networks and to report any detected faults.
+
+MIB-002 – MIB is required to store and modify the configuration information of the handover strategy, including thresholds of network performance metrics, preferred access network.
+
+MIB-003 – MIB is required to store the configuration and status information of different access network, including signal strength and data rate.
+
+MIB-004 – MIB is required to report the configuration and status information of different access networks.
+
+## **10.2 Requirements of network switch**
+
+The requirements for the network switch of NHM are as follows:
+
+NS-001 – The network switch is recommended to analyse the availability of different access networks, and evaluate the available network capability (including bandwidth, latency and reliability).
+
+NS-002 – The network switch is recommended to select the access network based on the handover strategy stored in MIB.
+
+NS-003 – The network switch is recommended to support the network handover triggering mechanism and resource conflict control mechanism to ensure service continuity.
+
+# **11 Interfaces of heterogeneous access network selection**
+
+The interfaces of heterogeneous access network selection are defined in Figure 2 based on [ITU-T H.550]. All independent functional blocks for heterogeneous access network selection are interconnected through the control reference points which include the following:
+
+- Cha reference point: control reference point between HANM and ANM.
+- Cac reference point: control reference point between ANM and communication interface for external networks (CIEN).
+- Chn reference point: control reference point between HANM and NHM.
+- Can reference point: control reference point between ANM and NHM.
+
+The requirements for the control reference points are as follows:
+
+CRP-001 – Cha reference point is required to send control messages, including the information of network configuration (ANM to HANM), network status (ANM to HANM) and QoS (ANM to HANM).
+
+CRP-002 – Cac reference point is required to send control messages, including the information of the network configuration (CIEN to ANM), network status (CIEN to ANM) and QoS (CIEN to ANM) of different access networks.
+
+CRP-003 – Chn reference point is required to send control messages, including the configuration and status of the networks (NHM to HANM), the mechanisms or strategies to establish, manage and disconnect networks (NHM to HANM).
+
+CRP-004 – Can reference point is required to send control messages, including the configuration and status of the networks (NHM to ANM), the mechanisms or strategies to establish, manage and disconnect networks (NHM to ANM).
+
+## Bibliography
+
+- [b-ITU-T F.749.1] Recommendation ITU-T F.749.1 (2015), *Functional requirements for vehicle gateways*.
+- [b-ITU-T Y.2012] Recommendation ITU-T Y.2012 (2010), *Functional requirements and architecture of next generation networks*.
+- [b-ITU-R M.2150-2] Recommendation ITU-R M.2150-2 (2023), *Detailed specifications of the terrestrial radio interfaces of International Mobile Telecommunications-2020 (IMT-2020)*.
+- [b-ITU-R handbook] ITU-R Handbook (2006), *Land Mobile (including wireless access), Volume 4: Intelligent Transport Systems*, 109 p.  
+<https://www.itu.int/pub/R-HDB-49-2006/en>
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.622-200806-I_PDF-E/2119293733c74fc64de88aefd597f4bb_img.jpg b/marked/H/T-REC-H.622-200806-I_PDF-E/2119293733c74fc64de88aefd597f4bb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aa018dcb17644100276baa4bc529a7c2f021ac0f
--- /dev/null
+++ b/marked/H/T-REC-H.622-200806-I_PDF-E/2119293733c74fc64de88aefd597f4bb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3d9a5ff4533992e95b22da221f5586c36d6f8c00345c0205bdcc31c9f5fa6c76
+size 30102
diff --git a/marked/H/T-REC-H.622-200806-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/H/T-REC-H.622-200806-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..acff713556f2be75eacbd53c5e7bc73a149f1cc4
--- /dev/null
+++ b/marked/H/T-REC-H.622-200806-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7d6b3a5a4d8b773863ec8f465ae3b99cb19b48700ce42d19d8adf0a9dcc9e1b8
+size 48590
diff --git a/marked/H/T-REC-H.622-200806-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/H/T-REC-H.622-200806-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..acd11260442edb6c33bc02ff0d0e411cc8351e30
--- /dev/null
+++ b/marked/H/T-REC-H.622-200806-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc70ee5b58af86ef5a199986d79caec55a6adc180459c7811208058331f838a1
+size 52517
diff --git a/marked/H/T-REC-H.622-200806-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg b/marked/H/T-REC-H.622-200806-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..41be9df9ad306e7a65b5e2d2b075557eb67a0134
--- /dev/null
+++ b/marked/H/T-REC-H.622-200806-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:69876b6d5b0c884b66c2b13359ccb154d9d8721981dd3efc522435e47ec31057
+size 33463
diff --git a/marked/H/T-REC-H.622-200806-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/H/T-REC-H.622-200806-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6280393a706e90d53ac93e9205a29a6f29518a71
--- /dev/null
+++ b/marked/H/T-REC-H.622-200806-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0481f453f896b3c9ac2bc03fb01202d4452a4c5f6fab33bedb838752c0974f07
+size 114045
diff --git a/marked/H/T-REC-H.622-200806-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/H/T-REC-H.622-200806-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4cf55bf3047b18f9f3b247953230296db8e4e41f
--- /dev/null
+++ b/marked/H/T-REC-H.622-200806-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:959f4e33ddba65a99951ab43bb3b2c9f539e9146cf106981e6bfd8b2d53a6d13
+size 11627
diff --git a/marked/H/T-REC-H.622-200806-I_PDF-E/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg b/marked/H/T-REC-H.622-200806-I_PDF-E/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7e6ffec936f8bb81f3a1774ee33b28869622d5e1
--- /dev/null
+++ b/marked/H/T-REC-H.622-200806-I_PDF-E/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:780bffad56267b08be87968d749d5d6ab3ad0482633ab2b11b1b97ecbb41029d
+size 17132
diff --git a/marked/H/T-REC-H.622-200806-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg b/marked/H/T-REC-H.622-200806-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..deec6ee04d28340cdbbbb47b8875a72616a5d39d
--- /dev/null
+++ b/marked/H/T-REC-H.622-200806-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d6d48b5977f3adbb74f45dd0d3e0c2808728de0b6e8c1c2dc5c944b405a0527a
+size 39231
diff --git a/marked/H/T-REC-H.622-200806-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/H/T-REC-H.622-200806-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e6e00ab7ab25ac31185f6d520f9db0b106149b79
--- /dev/null
+++ b/marked/H/T-REC-H.622-200806-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f528f8c6abdb0263a9bea485573b9350321e0c8ae3c8f59c472949cdddad1a99
+size 29017
diff --git a/marked/H/T-REC-H.622-200806-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg b/marked/H/T-REC-H.622-200806-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7318cbd3595a11844446cf8c17bfb39955b94572
--- /dev/null
+++ b/marked/H/T-REC-H.622-200806-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9a8b93590c58950e11281ae516a3297d0dd8979b5233727d8949a7b4101a6b1f
+size 63821
diff --git a/marked/H/T-REC-H.622-200806-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.622-200806-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a
--- /dev/null
+++ b/marked/H/T-REC-H.622-200806-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_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-200806-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/H/T-REC-H.622-200806-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4eae90eea9ec92ea31e24c3c4a772d32fd7c4196
--- /dev/null
+++ b/marked/H/T-REC-H.622-200806-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e2370b9197df114273d7ae056ed4a375249329fa433a7a2decb327a96ec75f9f
+size 112650
diff --git a/marked/H/T-REC-H.622-200806-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/H/T-REC-H.622-200806-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6ccb095a9711e1a5dfdd656dab2c4f60d38a4560
--- /dev/null
+++ b/marked/H/T-REC-H.622-200806-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:07bbfd8d2fb4b01e16db0ad1c99f9e808a7ff61859ae0fd99991ee58cd08166a
+size 68670
diff --git a/marked/H/T-REC-H.622-200806-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/H/T-REC-H.622-200806-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9c8a74584025c348f2b6921eda16bce5f66c045d
--- /dev/null
+++ b/marked/H/T-REC-H.622-200806-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:48a5591c7318f26ff64ce46087ecad2a2a13fcccad39b723e7f836bbb7d61dbd
+size 92704
diff --git a/marked/H/T-REC-H.622-200806-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/H/T-REC-H.622-200806-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c0f8d9375ad0e84c9a26bf520b049fbbd4d62f8c
--- /dev/null
+++ b/marked/H/T-REC-H.622-200806-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:46aedd2686cdd35944b842e25c411c83d14d333113edade9303c357e7dc77772
+size 80555
diff --git a/marked/H/T-REC-H.622-200806-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.622-200806-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ac46f204f6340390a553e30bcc58ff4422023877
--- /dev/null
+++ b/marked/H/T-REC-H.622-200806-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b747c5eb0cb69c7d0e5cf415d13d92aa897cdf73623479c05145e3181e3a353e
+size 28106
diff --git a/marked/H/T-REC-H.626.2-201712-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/H/T-REC-H.626.2-201712-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..687658c5cf82dfe7157798a530de18b7b5fc264e
--- /dev/null
+++ b/marked/H/T-REC-H.626.2-201712-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:edd330f0a9c71f2d63a4eb395fd20aab4af9f2d084b4cba4bfc38cbd06939c08
+size 105565
diff --git a/marked/H/T-REC-H.626.2-201712-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/H/T-REC-H.626.2-201712-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b1689402a460ddab7ddda4b2544ab47be9f7e90b
--- /dev/null
+++ b/marked/H/T-REC-H.626.2-201712-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9615f17bf58f3af6ff2dbf24d22c85c35d90e6c145d2a1e1a2d1e09f092c0d9c
+size 46442
diff --git a/marked/H/T-REC-H.626.2-201712-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/H/T-REC-H.626.2-201712-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f8f20f5f9cef00e827ca4072feb97c772d4cb403
--- /dev/null
+++ b/marked/H/T-REC-H.626.2-201712-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3f92555d078c7d26fb7d9992bc196fa7268ae53471ca093c162b320befbdddf7
+size 62877
diff --git a/marked/H/T-REC-H.626.2-201712-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/H/T-REC-H.626.2-201712-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e9f513b035b3541204f22012dc0e73121e4c3819
--- /dev/null
+++ b/marked/H/T-REC-H.626.2-201712-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b4f155c90edf7ad7a53977fffa548872b8cb8c185dbb7002e92f7a4e8bfb0688
+size 107387
diff --git a/marked/H/T-REC-H.626.2-201712-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/H/T-REC-H.626.2-201712-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e57d9677dc2d5b6ec322ff5c588c8ac58def719f
--- /dev/null
+++ b/marked/H/T-REC-H.626.2-201712-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:69e56667c85e126f1e7baef4e67c7e8e321421867b2b63b6f9330afe5972768d
+size 99812
diff --git a/marked/H/T-REC-H.626.2-201712-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.626.2-201712-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b7d507f727b7c272392dd19081f2020ac8ff7ab1
--- /dev/null
+++ b/marked/H/T-REC-H.626.2-201712-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:70162d23ec00454bad4fa7944806bda226b158aae196478f38b5e99799cdf30c
+size 3839
diff --git a/marked/H/T-REC-H.626.2-201712-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/H/T-REC-H.626.2-201712-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d803110a28b2db5f5f4d4a4fbb3d9ef759442628
--- /dev/null
+++ b/marked/H/T-REC-H.626.2-201712-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:898644ccd4f4e2918167ca91cd8bbb010fe4e72d8effd19099d6b2738d80380e
+size 91765
diff --git a/marked/H/T-REC-H.626.2-201712-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/H/T-REC-H.626.2-201712-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4e631e965e72806faf8685d5439c3e64d8799143
--- /dev/null
+++ b/marked/H/T-REC-H.626.2-201712-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:789f5b163471b3813ac6f5ee6b7cc36e60ed0cfcffc0808b32d8f32696ba5bcc
+size 101981
diff --git a/marked/H/T-REC-H.626.6-202402-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/H/T-REC-H.626.6-202402-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..38bdd7bc1d3581fbdc3cf6b035f618693dbe3846
--- /dev/null
+++ b/marked/H/T-REC-H.626.6-202402-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.626.6-202402-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/H/T-REC-H.626.6-202402-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8b8e9c81c421fde94bfc126d620b0569c937d407
--- /dev/null
+++ b/marked/H/T-REC-H.626.6-202402-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2579fe0e580e74fe9952a7973d7541de79d4ebc51c18ce11a160912e1bf3975d
+size 3975
diff --git a/marked/H/T-REC-H.626.6-202402-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg b/marked/H/T-REC-H.626.6-202402-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cbe84d5fcec1f222f5b5e6f15436cae3211b1776
--- /dev/null
+++ b/marked/H/T-REC-H.626.6-202402-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2cab60218dea2d5071eb5e10b8dc6c1c3afdb0bbe713184a40295e100ee68917
+size 15628
diff --git a/marked/H/T-REC-H.626.6-202402-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/H/T-REC-H.626.6-202402-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a2c7d3573823deade60b98b44493bbc2b613820e
--- /dev/null
+++ b/marked/H/T-REC-H.626.6-202402-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:01449305f7990e3d5bed3e7de9a5b6ae89573f9cd8b0d0091c50c2f90776db92
+size 4647
diff --git a/marked/H/T-REC-H.626.6-202402-I_PDF-E/e58a867750e4ae01604318506b79df7a_img.jpg b/marked/H/T-REC-H.626.6-202402-I_PDF-E/e58a867750e4ae01604318506b79df7a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5f9133704d016ca732e9897fa8f039f494274fc6
--- /dev/null
+++ b/marked/H/T-REC-H.626.6-202402-I_PDF-E/e58a867750e4ae01604318506b79df7a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f15656ccb51d6f007ceace29c173faacecee2070b5620b3a587a72b6d58e791d
+size 25001
diff --git a/marked/H/T-REC-H.626.6-202402-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/H/T-REC-H.626.6-202402-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2af9d10e1b6a04192eb683c20663e6c86b20fdb5
--- /dev/null
+++ b/marked/H/T-REC-H.626.6-202402-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5856f65fbf5409edd7a5ba0dc99d74fa3164adb16b0d61d783bb72bf24dfa526
+size 67747
diff --git a/marked/H/T-REC-H.626.6-202402-I_PDF-E/raw.md b/marked/H/T-REC-H.626.6-202402-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..bd37dc5234ef57bcd8ae6f1cd5fcab4900a8c8e6
--- /dev/null
+++ b/marked/H/T-REC-H.626.6-202402-I_PDF-E/raw.md
@@ -0,0 +1,407 @@
+
+
+# Recommendation**ITU-T H.626.6 (02/2024)**
+
+SERIES H: Audiovisual and multimedia systems
+
+Broadband, triple-play and advanced multimedia services –  
+Advanced multimedia services and applications
+
+---
+
+## **Architecture for big data application in video surveillance 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        |
+| 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        |
+| <b>Advanced multimedia services and applications</b>            | <b>H.620-H.629</b> |
+| 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.6
+
+## Architecture for big data application in video surveillance systems
+
+## Summary
+
+Recommendation ITU-T H.626.6 defines an architecture for big data application in video surveillance systems, including the functional architecture and reference points. As the amount of video data is growing in video surveillance systems, a suitable architecture is needed to support the requirements for big data application in video surveillance systems to deal with the structured and unstructured data, and to enhance the efficiency of huge data retrieval and data mining across time and space range. This Recommendation is based on Recommendation ITU-T F.743.7, *Requirements for big data-enhanced visual surveillance services*.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T H.626.6  | 2024-02-13 | 16          | 11.1002/1000/15848 |
+
+## Keywords
+
+Architecture, big data, video surveillance system.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                      | 2    |
+| 4 Abbreviations and acronyms .....                                 | 2    |
+| 5 Conventions .....                                                | 3    |
+| 6 Functional architecture for big data application in VSS(s) ..... | 3    |
+| 6.1 Functional architecture in VSBD .....                          | 4    |
+| 6.2 Functional entities .....                                      | 4    |
+| 7 Reference points .....                                           | 6    |
+| 7.1 Reference point Va/Va'.....                                    | 6    |
+| 7.2 Reference point Vd/Vd' .....                                   | 6    |
+| 7.3 Reference point Da/Da'.....                                    | 7    |
+| 7.4 Reference point Cb .....                                       | 7    |
+| 7.5 Reference point Ca .....                                       | 7    |
+| Bibliography.....                                                  | 8    |
+
+
+
+# Recommendation ITU-T H.626.6
+
+## Architecture for big data application in video surveillance systems
+
+# 1 Scope
+
+This Recommendation specifies the functional architecture and reference points for big data application in video surveillance systems (VSS).
+
+The scope of this Recommendation includes:
+
+- Functional architecture for big data application in video surveillance systems;
+- Reference points for big data application in video surveillance systems.
+
+# 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 (V2) (2019), *Requirements and service description for video surveillance*.
+- [ITU-T F.743.1] Recommendation ITU-T F.743.1 (2015), *Requirements for intelligent visual surveillance*.
+- [ITU-T F.743.7] Recommendation ITU-T F.743.7 (2019), *Requirements for big data-enhanced visual surveillance services*.
+- [ITU-T H.626] Recommendation ITU-T H.626 (V2) (2019), *Architectural requirements for video surveillance system*.
+- [ITU-T H.626.5] Recommendation ITU-T H.626.5 (V2) (2022), *Architecture for intelligent video surveillance systems*.
+- [ITU-T L.1390] Recommendation ITU-T L.1390 (2022), *Energy saving technologies and best practices for 5G radio access network (RAN) equipment*.
+
+# 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 big data** [ITU-T L.1390]: A term that describes the large volume of data – both structured and unstructured – that inundates a business on a day-to-day basis. Big data can be analysed for insights that lead to better decisions and strategic business moves.
+
+**3.1.3 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 (CCS) consists of a centre management unit and a service-control unit.
+
+**3.1.4 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.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.
+
+**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, and 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 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 (MS) receives the media stream from the premises unit or other media server and forwards the media stream to another customer unit or media server. It consists of a media distribution unit and a media storage unit.
+
+**3.1.10 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.11 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.12 service** [b-ITU-T Y.101]: A structured set of capabilities intended to support applications.
+
+**3.1.13 video surveillance system (VSS)** [ITU-T F.743]: A telecommunication system focusing on video (but including audio) application technology, which is used to remotely capture multimedia (such as audio, video, image, alarm signals, etc.) and present them to the end user in a friendly manner, based on a managed broadband network with quality, security and reliability ensured.
+
+## 3.2 Terms defined in this Recommendation
+
+None.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|       |                                          |
+|-------|------------------------------------------|
+| AEF   | Analysis Evaluation Function             |
+| AMF   | Analysis Management Function             |
+| APP   | Application                              |
+| ASCF  | Analysis Service Control Function        |
+| BDAU  | Big Data Application Unit                |
+| CCS   | Centre Control Server                    |
+| CFBDA | Console Function of Big Data Application |
+
+|      |                                                    |
+|------|----------------------------------------------------|
+| CSF  | Computing Service Function                         |
+| CU   | Customer Unit                                      |
+| CMU  | Centre Management Unit                             |
+| DMAF | Data Mining and Analysis Function                  |
+| DSS  | Data Storage and Service                           |
+| DSU  | Data Storage Unit                                  |
+| ISU  | Information Storage Unit                           |
+| IVS  | Intelligent Visual Surveillance                    |
+| MDU  | Media Distribution Unit                            |
+| MS   | Media Server                                       |
+| MSU  | Media Storage Unit                                 |
+| PU   | Premises Unit                                      |
+| VAEU | Visual Analysis Engine Unit                        |
+| VSAF | Video Streaming Access Function                    |
+| VSBD | Big Data application in Video Surveillance systems |
+| VSS  | Video Surveillance System                          |
+
+## 5 Conventions
+
+Functional entities: In the context of VSBD architecture, "functional entities" are defined as a collection of functionalities. It is represented by the following symbol:
+
+![A rectangular box with a black border containing the text 'Functional entities'.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+A rectangular box with a black border containing the text 'Functional entities'.
+
+Function modules: In the context of VSBD architecture, "function modules" are defined as groups 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 with a blue border containing the text 'Function modules'.](367926125450c2bc3f4bdca9d59a62ba_img.jpg)
+
+A rectangular box with a blue border containing the text 'Function modules'.
+
+NOTE – In the future, other groups or other Recommendations may possibly further subdivide these function modules.
+
+# 6 Functional architecture for big data application in VSS(s)
+
+This clause describes the functional architecture for big data application in video surveillance systems (VSBD) and functional entities.
+
+Big data is defined in [ITU-T L.1390], and big data application are also analysed for insights that lead to better decisions and strategic business moves from the amount of data. The scenarios of VSBD are defined in [ITU-T F.743.7], they are:
+
+- Intelligent video retrieval. For example, VSBD can use characteristic information such as licence plate, vehicle type, colour, brand type or body feature of the target vehicle as input, to retrieve similar objects in multiple videos with the trajectories displayed to users.
+
+- Intelligent event detection. For example, VSBD can detect a fire disaster by analysing the related real-time videos as well as sensing data from smoke detectors and temperature sensors in areas of concern to the users.
+- Status prediction. For example, according to the data collected by cameras, VSBD can analyse the rules and forecast future traffic flow in order to achieve efficient traffic control.
+
+### 6.1 Functional architecture in VSBD
+
+The system's functional architecture is illustrated in Figure 6-1.
+
+![Figure 6-1 – Functional architecture diagram showing the internal components of a VS system and its interaction with external units. The VS system contains CCS (CMU, SCU), VSBD (BDAU, DSU with MSU and ISU, VAEU), and MS (MDU). External units include PU and CU. Arrows indicate Media (black), Control (red), and Video and image information (green) flows between these components.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+The diagram illustrates the functional architecture of a Video Surveillance and Broadcasting (VSBD) system within a 'VS system' boundary. Inside the boundary, the 'CCS' (Centre Control System) contains 'CMU' (Centre Management Unit) and 'SCU' (Service Control Unit). The 'VSBD' (Video Surveillance and Broadcasting Device) contains 'BDAU' (Big Data Application Unit), 'DSU' (Data Storage Unit), and 'VAEU' (Visual Analysis Engine Unit). The 'DSU' contains 'MSU' (Media Storage Unit) and 'ISU' (Image Storage Unit). The 'MS' (Media System) contains 'MDU' (Media Distribution Unit). Outside the boundary are 'PU' (Premises Unit) and 'CU' (Customer Unit). Arrows represent different types of data flow: Media (black), Control (red), and Video and image information (green). Control signals include 'Ps', 'Cm', 'Cs', 'Cb', 'Mp', 'Mp'', 'Pc', 'Mc', 'Mc'', 'Ca', 'Da', 'Da'', 'Vd', 'Vd'', 'Va', 'Va''.
+
+Figure 6-1 – Functional architecture diagram showing the internal components of a VS system and its interaction with external units. The VS system contains CCS (CMU, SCU), VSBD (BDAU, DSU with MSU and ISU, VAEU), and MS (MDU). External units include PU and CU. Arrows indicate Media (black), Control (red), and Video and image information (green) flows between these components.
+
+Figure 6-1 – Functional architecture
+
+The VSBD is an end-to-end system without a customer unit focusing on a large amount of video (but including audio) data, which is to collect, store, process, analyse, apply, and display the video data. It consists of a big data application unit (BDAU), data storage unit (DSU) and visual analysis engine unit (VAEU).
+
+The VSBD is different from the intelligent visual surveillance (IVS) system and the application (APP) defined in [ITU-T F.743.1] and the data storage and service (DSS) defined in [ITU-T H.626.5].
+
+The centre management unit (CMU), service-control unit (SCU), media distribution unit (MDU), media storage unit (MSU), premises unit (PU) and customer unit (CU) are defined in [ITU-T H.626]. And the rest in Figure 6-1 is described in clause 6.2 and the reference points in clause 7.
+
+## 6.2 Functional entities
+
+This clause defines the functional entities for VSBD.
+
+#### 6.2.1 Big data application unit
+
+The BDAU is the functional entity of application aspects. It consists of a video streaming access function (VSAF), console function of big data application (CFBDA) and a data mining and analysis function (DMAF).
+
+The main tasks of BDAU are application selection, application operation, application presentation, application access such as video streaming access function, portal service presentation, data mining and analysis service selection.
+
+Figure 6-2 shows the function modules of the BDAU.
+
+![Figure 6-2 – Function modules of BDAU](5b4e774d63e0e0ed73801a9247755e5f_img.jpg)
+
+A block diagram showing three functional modules. On the left is a box labeled "Console function of big data application". A red arrow points from this box to a central box labeled "Video streaming access function". Above the central box is another box labeled "Data mining and analysis function", connected by a green upward-pointing arrow. Below the central box is the text "H.626.6(24)".
+
+Figure 6-2 – Function modules of BDAU
+
+Figure 6-2 – Function modules of BDAU
+
+##### 6.2.1.1 Video streaming access function
+
+VSAF is a functional module for access and re-transmission.
+
+The main tasks of VSAF are to access data storage and re-transmit analysis data. For example, VSAF can be used to get the original video data according to monitoring time. VSAF can also be used to decode the original video data to get the required video data and send the video frames to the video analysis engine for analysis.
+
+#### 6.2.1.2 Console function of big data application
+
+CFBDA is the portal of VSBD.
+
+The main task of the CFBDA is to interact with the CU. The CFBDA provides the interface to operate and control the VSBD. Through the CFBDA, the authorized end user can, e.g., manage alarm task, video enrichment task, data retrieval and analysis task, subject research-prediction task, etc.
+
+#### 6.2.1.3 Data mining and analysis function
+
+DMAF is the display carrier for the results of big data analysis.
+
+The main tasks of DMAF are to play and display the result and information of data mining and analysis such as video enrichment, real-time deploy-control and alarming, data retrieval and analysis and status prediction.
+
+#### 6.2.2 Visual analysis engine unit
+
+VAEU is the functional entity for visual analysis aspects. It consists of an analysis service control function (ASCF), analysis management function (AMF), computing service function (CSF) and analysis evaluation function (AEF).
+
+The main tasks of VAEU are to analyse the video data and output the analysis results.
+
+Figure 6-3 shows the function modules of the VAEU.
+
+![Figure 6-3 – Function modules of VAEU](e58a867750e4ae01604318506b79df7a_img.jpg)
+
+A block diagram showing four functional modules. On the left is a box labeled "Analysis service control function". Two red arrows point from this box to two boxes in the center: "Analysis management function" (top) and "Analysis evaluation function" (bottom). These two central boxes are connected by a green double-headed vertical arrow. To the right is a box labeled "Computer service function". Green arrows point from the "Analysis management function" and the "Analysis evaluation function" to the "Computer service function". A long red arrow originates from the bottom of the "Analysis service control function" box and points to the bottom of the "Computer service function" box. Below the "Computer service function" box is the text "H.626.6(24)".
+
+Figure 6-3 – Function modules of VAEU
+
+Figure 6-3 – Function modules of VAEU
+
+##### **6.2.2.1 Analysis service control function**
+
+ASCF is the functional module for service-control aspects.
+
+The main tasks of the ASCF are service description, service registration, service access, service selection, service scheduling, service monitoring, service tracking and service management.
+
+##### **6.2.2.2 Analysis management function**
+
+AMF is the functional module for video or image process aspects.
+
+The main tasks of the AMF are to identify specific objects automatically and output the analysis results to the BDAU, recognize information including triggered events and acquired data, load or unload one or more intelligent analysis algorithms on the CSF according to the different requirements and evaluation from the AEF, send capability lists, statuses and analysis results to the AEF.
+
+##### **6.2.2.3 Computing service function**
+
+CSF is the functional module for computing aspects.
+
+The main task of the CSF is to provide calculation ability to the AMF and AEF according to the different requirements.
+
+#### **6.2.2.4 Analysis evaluation function**
+
+AEF is the functional module for evaluating aspects to improve the accuracy of the visual analysis.
+
+The main tasks of the AEF are to evaluate the quality and performance of capabilities and send the report to the AMF. According to the different requirements, the AEF evaluates analysis results by checking the statuses of capability lists and choosing the one which has the best performance capability.
+
+#### **6.2.3 Data storage function**
+
+DSF is the functional entity for data storage aspects. It consists of MSU and an information storage unit (ISU). MSU is defined in [ITU-T H.626]. ISU is the function module to store, index, download and provide serving of video and image information from the VAEU.
+
+The main tasks of the DSF are to store data, index data, download data and provide data serving.
+
+## **7 Reference points**
+
+This clause defines reference points. The reference points Cm, Cs, Ps, Ds, Ds', Mp, Mp', Mc, Mc' and Pc are defined in [ITU-T H.626].
+
+## **7.1 Reference point Va/Va'**
+
+Reference points Va and Va' are between the BDAU and the VAEU.
+
+Va is used to report the results of the intelligent analysis task from the VAEU to the BDAU.
+
+Va' is used to send the user request of a big data analysis task (such as search target by image, search target by attribute, etc.) from the BDAU to the VAEU, report the status of the big data analysis task from the VAEU to the BDAU, and control the big data analysis task from the VAEU to the BDAU.
+
+## **7.2 Reference point Vd/Vd'**
+
+Reference points Vd and Vd' are between the VAEU and the DSU.
+
+Vd is used to transmit the authorized video and image data from the DSU to the VAEU when the data stored in the DSU is required to be accessed by the BDAU's users and transmit video and image information from the VAEU to the DSU when the analysed information is required to be collected to the DSU.
+
+Vd' is used to send data access request from the VEAU to the DSU, and support data operations like information query, etc., based on the request from the VEAU to the DSU.
+
+## **7.3 Reference point Da/Da'**
+
+Reference points Da and Da' are between the DSU and the BDAU.
+
+Da is used to transmit the authorized video and image information from the DSU to the BDAU when the data stored in the DSS is required to be accessed by the BDAU's users and transmit video and image information from the BDAU to the DSU when the information captured by the BDAU is required to be collected to the DSU.
+
+Da' is used to send video and image information access request from the BDAU to the DSU such as information query or subscription and so on.
+
+## **7.4 Reference point Cb**
+
+Reference point Cb lies between the centre control server (CCS) and the BDAU. It is used to send the user authentication request from the BDAU to the CMU and return the authentication result.
+
+## **7.5 Reference point Ca**
+
+Reference point Ca lies between the CU and the BDAU. It is used by the CU to select, search, play, download and install applications.
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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-202008-I_PDF-E/raw.md b/marked/H/T-REC-H.627-202008-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..85fd4b1e517187fcd273931659ca885c6b8dc114
--- /dev/null
+++ b/marked/H/T-REC-H.627-202008-I_PDF-E/raw.md
@@ -0,0 +1,9753 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.627**
+
+(08/2020)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Broadband, triple-play and advanced multimedia services –  
+Advanced multimedia services and applications
+
+# --- **Signalling and protocols for a video surveillance system**
+
+Recommendation ITU-T H.627
+
+**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 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        |
+| <b>Advanced multimedia services and applications</b>                                        | <b>H.620–H.629</b> |
+| 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.627
+
+# Signalling and protocols for a video surveillance system
+
+## Summary
+
+Recommendation ITU-T H.627V2 specifies detailed signalling flows and relevant protocols of a video surveillance system, based on the requirements specified in Recommendation ITU-T F.743V2 and the functional architecture specified in Recommendation ITU-T H.626V2.
+
+This edition updates the title, adds overall requirements, as well as revising the signalling flows and relevant protocols.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T H.627    | 2012-06-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/11676">11.1002/1000/11676</a> |
+| 2.0     | ITU-T H.627    | 2020-08-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/14342">11.1002/1000/14342</a> |
+
+## Keywords
+
+Protocols, signalling, video surveillance system.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....               | 3    |
+| 4 Abbreviations and acronyms .....                          | 3    |
+| 5 Conventions .....                                         | 4    |
+| 6 Introduction to functional architecture of VSS.....       | 4    |
+| 7 Overall requirements of signalling and media stream ..... | 5    |
+| 7.1 Introduction of related protocols .....                 | 5    |
+| 7.2 SIP header requirements.....                            | 5    |
+| 7.3 Extended media command set .....                        | 6    |
+| 7.4 Media stream keepalive mechanism.....                   | 9    |
+| 7.5 Transmission of multiple response messages.....         | 9    |
+| 7.6 RTP-based video or audio data packaging .....           | 10   |
+| 7.7 SDP definitions.....                                    | 12   |
+| 7.8 TCP-based media transmission .....                      | 16   |
+| 8 Signalling flows and relevant protocols .....             | 17   |
+| 8.1 Registration and de-registration .....                  | 17   |
+| 8.2 Real-time media stream.....                             | 20   |
+| 8.3 Device configuration and control .....                  | 35   |
+| 8.4 Alarm event notification and distribution.....          | 44   |
+| 8.5 Device information query.....                           | 47   |
+| 8.6 Status information reporting.....                       | 74   |
+| 8.7 Historical media file retrieval.....                    | 76   |
+| 8.8 Historical media file playback.....                     | 78   |
+| 8.9 Historical media file download .....                    | 98   |
+| 8.10 Time calibration.....                                  | 116  |
+| 8.11 Subscription and notification.....                     | 118  |
+| 8.12 Audio broadcast and audio intercom.....                | 125  |
+| 8.13 Instant image snapshot .....                           | 130  |
+| Annex A – Extended control command set .....                | 134  |
+| A.1 Overall requirements .....                              | 134  |
+| A.2 Command definitions .....                               | 134  |
+| A.3 PU control commands .....                               | 162  |
+
+
+
+# Recommendation ITU-T H.627
+
+# Signalling and protocols for a video surveillance system
+
+# 1 Scope
+
+This Recommendation specifies in detail signalling and relevant protocols of a video surveillance system (VSS) based on the functional architecture specified in [ITU-T H.626V2].
+
+# 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] 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.222.0] ISO/IEC 13818-1:2019|ITU-T H.222.0 (2018), *Information technology – Generic coding of moving pictures and associated audio information – Systems.*
+- [ITU-T H.264V13] 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.626V2] Recommendation ITU-T H.626 (2019), *Architectural requirements 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 3725] IETF RFC 3725 (2004), *Best current practices for third party call control (3pcc) in the session initiation protocol (SIP).*
+- [IETF RFC 4566] IETF RFC 4566 (2006), *SDP: Session description protocol.*
+- [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 6086] IETF RFC 6086 (2011), *Session initiation protocol (SIP) INFO method and package framework*.
+- [IETF RFC 6184] IETF RFC 6184 (2011), *RTP payload format for H.264 video*.
+- [IETF RFC 6665] IETF RFC 6665 (2012), *SIP – Specific event notification*.
+- [IETF RFC 7798] IETF RFC 7798 (2016), *RTP payload format for high efficiency video coding (HEVC)*.
+- [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 central control server (CCS)** [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.2 centre management unit** [ITU-T H.626V2]: 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.1.3 customer unit** [ITU-T H.626V2]: 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 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.5 media distribution unit** [ITU-T H.626V2]: 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, media replication, etc.
+
+**3.1.6 media server** [ITU-T H.626V2]: 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 media storage unit** [ITU-T H.626V2]: 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 media downloading, etc.
+
+**3.1.8 premises unit** [ITU-T H.626V2]: 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.9 service control unit** [ITU-T H.626V2]: 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.1.10 video surveillance system** [ITU-T H.626V2]: 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.
+
+## **3.2 Terms defined in this Recommendation**
+
+None.
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|       |                                    |
+|-------|------------------------------------|
+| AAC   | Advanced Audio Coding              |
+| ACK   | Acknowledgement                    |
+| B2BUA | Back to Back User Agent            |
+| CBR   | Constant Bitrate                   |
+| CCS   | Central Control Server             |
+| CIF   | Common Intermediate Format         |
+| CMU   | Centre Management Unit             |
+| CPG   | Control Protocol Gateway           |
+| CRLF  | Carriage Return and Line Feed      |
+| CU    | Customer Unit                      |
+| ECCS  | Extended Control Command Set       |
+| EMCS  | Extended Media Command Set         |
+| FI    | Focus Iris                         |
+| ID    | Identifier                         |
+| IP    | Internet Protocol                  |
+| IPC   | IP Camera                          |
+| MDU   | Media Distribution Unit            |
+| MS    | Media Server                       |
+| MSU   | Media Storage Unit                 |
+| NPT   | Normal Play Time                   |
+| NTP   | Network Time Protocol              |
+| OSD   | On-Screen Display                  |
+| PCM   | Pulse Code Modulation              |
+| PES   | Packetized Elementary Stream       |
+| PESA  | Packetized Elementary Stream Audio |
+| PESV  | Packetized Elementary Stream Video |
+
+|       |                                                    |
+|-------|----------------------------------------------------|
+| PS    | Program Stream                                     |
+| PSM   | Program Stream Map                                 |
+| PTZ   | Pan/Tilt/Zoom                                      |
+| PU    | Premises Unit                                      |
+| QCIF  | Quarter Common Intermediate Format                 |
+| RTCP  | Real-time Transport Control Protocol               |
+| RTP   | Real-time Transport Protocol                       |
+| RTSP  | Real-time Streaming Protocol                       |
+| SCU   | Service Control Unit                               |
+| SDP   | Session Description Protocol                       |
+| SIP   | Session Initiation Protocol                        |
+| SMPTE | Society of Motion Picture and Television Engineers |
+| SN    | Serial Number                                      |
+| SRG   | Signal Routing Gateway                             |
+| SSRC  | Synchronization Source                             |
+| TCP   | Transmission Control Protocol                      |
+| UA    | User Agent                                         |
+| UDP   | User Datagram Protocol                             |
+| URI   | Uniform Resource Identifier                        |
+| UTC   | Coordinated Universal Time                         |
+| VBR   | Variable Bitrate                                   |
+| VSS   | Video Surveillance System                          |
+| XML   | extensible Markup Language                         |
+
+# 5 Conventions
+
+None.
+
+# 6 Introduction to functional architecture of VSS
+
+The functional architecture of a VSS is illustrated in Figure 6-1. Regarding the detailed entities and function, see clause 6.2 of [ITU-T H.626V2].
+
+![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. Media flows are shown with black arrows, and control flows with red arrows. Labels include Ps, Cs, Cm, Ds, Ds', Mp, Mp', Mc, Mc', and Pc. A legend at the bottom indicates black arrows for Media and red arrows for Control. The diagram is labeled H.627(20)_F6-1.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+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. Media flows are shown with black arrows, and control flows with red arrows. Labels include Ps, Cs, Cm, Ds, Ds', Mp, Mp', Mc, Mc', and Pc. A legend at the bottom indicates black arrows for Media and red arrows for Control. The diagram is labeled H.627(20)\_F6-1.
+
+CMU: centre management unit, MDU: media distribution unit; MSU: media storage unit; SCU: service control unit
+
+**Figure 6-1 – Functional architecture of VSS**
+
+# 7 Overall requirements of signalling and media stream
+
+## 7.1 Introduction of related protocols
+
+The structure of communication protocols is illustrated in Figure 7-1. Regarding the detailed protocols and data formats, see clause 7.1 of [ITU-T H.626V2].
+
+![](5e92d9e8e9ce204e405bff2367f88176_img.jpg)
+
+| Session channel |      |      | Media stream channel        |                                                   |
+|-----------------|------|------|-----------------------------|---------------------------------------------------|
+| SDP             | ECCS | EMCS | ITU-T H.264/<br>ITU-T H.265 | ITU-T G.711/<br>ITU-T G.723.1/<br>ITU-T G.729/AAC |
+| SIP             |      |      | RTP/RTCP                    |                                                   |
+| TCP/UDP         |      |      | TCP/UDP                     |                                                   |
+| IP              |      |      |                             |                                                   |
+
+H.627(20)\_F7-1
+
+**Figure 7-1 – Structure of communication protocols**
+
+## 7.2 SIP header requirements
+
+With reference to [IETF RFC 3261], the session initiation protocol (SIP) uniform resource identifier (URI) formats in From and To headers of SIP messages within the VSS are specified as follows:
+
+```
+sip[s]:username@domain;uri-parameters
+```
+
+in which it shall be ensured that the username is unique in the same VSS, and the identifier (ID) uniform codes specified in [ITU-T H.626V2] should be adopted; the domain should adopt the first 14 digits in the ID uniform codes, or adopt the IP: port format, while the port should adopt 5060; URI parameters can be used to carry the extended parameters.
+
+The SIP URI values of other headers in SIP messages should comply with the signal communication provisions of [IETF RFC 3261].
+
+The Subject header field of the INVITE message sent by the CCS is used to identify the different media links. The VSS has the capability of media distribution: for the video with the same sender ID, only one request shall be initiated to the target VSS or device and the video resources are sent to different receivers.
+
+The format of the subject field is as follows:
+
+Subject: Media stream sender ID: Sender's media stream serial number, media stream receiver ID: Receiver's media stream serial number.
+
+The various fields are described as follows:
+
+Media stream sender ID: The media stream sender ID code complies with the specification in [ITU-T H.626V2].
+
+Sender's media stream serial number (SN): The sender's media stream SN is a character string that consists of no more than 20 digits. When the requested media is the real-time media stream, the value of the first digit is 0, and the value is unique for each media link; when the requested media is the historical media stream, the value of the first digit is 1, and the value is unique for each media link.
+
+Media stream receiver ID: The media stream receiver ID code complies with the specification in [ITU-T H.626V2].
+
+Receiver's media stream SN: The identification SN of the media stream receiver is a non-repeating character string at the same moment. When the receiver is a client, it can be taken as the ID of the display window.
+
+## 7.3 Extended media command set
+
+### 7.3.1 Command names and descriptions
+
+The historical media file playback control commands are implemented through the request message from the client to the server and the response message from the server to the client. The request and response adopt part of the request and response message formats in the real-time streaming protocol (RTSP) [IETF RFC 7826].
+
+A message includes a start line, one or more message headers, a blank line (namely the line without content before carriage return and line feed (CRLF)) representing the end of the header and a message body (optional). An example is as follows:
+
+```
+message =start-line  
+message header  
+CRLF  
+[message body]
+```
+
+The messages include requests and responses. Each pair of request-response messages shall include the same CSeq header field, with the specific description shown as follows.
+
+#### a) Request
+
+The start line format of the request message is Method SP RTSP-Version CRLF, where Method: request command; SP: blank character; RTSP-Version: protocol version number; CR: carriage return; LF: line feed. Request commands include: PLAY, PAUSE, TEARDOWN;
+
+#### b) Response
+
+The start line format of the response message is:
+
+```
+Status-Line = RTSP-Version SP Status-Code SP Reason-Phrase CRLF.
+```
+
+where RTSP-Version: protocol version number; Status-Code: 3-bit status code, used for representing the host status when responding to the request; Reason-Phrase: textual interpretation corresponding to the status code.
+
+### 7.3.2 Command definitions
+
+#### CD-1: Media playing command
+
+The client sends the PLAY request message, and requests the server to send the media stream. Range headers shall be supported, which provides the time range for playing in the Range header so as to play the media in the specified time period; see clause 12.40 of [IETF RFC 7826]. The time range shall support normal play time (NPT) and Society of Motion Picture and Television Engineers (SMPTE) relative timestamp ranges. The RTP-Info header information is given in the response message from the server; see clause 18.45 of [IETF RFC 7826]. The RTP-Info should be returned in the 200 OK of the SIP INFO, and the seq and rtptime parameters should be carried in the RTP-Info field.
+
+The value of the Range header is "npt=now-", without carrying the Scale header, representing that it resumes playing at the original speed from the paused position.
+
+Example:
+
+```
+PLAY RTSP/2.0
+CSeq:2
+Range:npt=now-
+```
+
+Example of the video playback PLAY command returns RTP-Info (take random drag and drop as an example):
+
+Request info:
+
+```
+INFO SIP:media stream sender code@ media stream sender domain name or IP
+address port SIP/2.0
+From: <sip:SIP: media stream receiver code@media stream receiver domain
+name>;tag=e3719a0b
+To: <sip: media stream sender code@ media stream sender domain
+name>;tag=949c43d7
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bfd0@172.20.16.4
+Via: SIP/2.0/UDP media stream receiver domain name or IP address
+Content-Length: the byte length of message
+CSeq: 2 INFO
+Content-Type: Application/EMCS
+Max-Forwards: 70
+
+PLAY RTSP/2.0
+CSeq: 4
+Range: npt=100-
+```
+
+Response example:
+
+```
+SIP/2.0 200 OK
+Via: SIP/2.0/UDP media stream receiver domain name or IP address
+From: <sip:media stream receiver code@media stream receiver domain
+name>;tag=e3719a0b
+To: <sip:media stream sender code@media stream sender domain
+name>;tag=949c43d7
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bfd0@172.20.16.4
+CSeq: 2 INFO
+Content-Type: Application/EMCS
+Content-Length: the byte length of message
+
+RTSP/2.0 200 OK
+CSeq: 6
+Range: npt=100-
+RTP-Info: seq=18139;rtptime=3119600838
+```
+
+#### **CD-2: Pause playing command**
+
+The client sends the PAUSE request message, and requests the server to pause the sending of media, but not release the resources. See clause 13.6 of [IETF RFC 7826].
+
+The value of the PauseTime is fixed as "now", representing that the video pauses at the current position.
+
+Example:
+
+```
+PAUSE RTSP/2.0  
+CSeq:1  
+PauseTime: now
+```
+
+#### **CD-3: Fast forward/slow forward command**
+
+In the PLAY request message sent by the client, the Scale header shall be used to control the playing speed; see clause 18.46 of [IETF RFC 7826]. When the value of Scale is 1, it represents normal speed playing; when it is not 1, it represents the multiple of normal playing speed; when it is negative, it represents backward playing.
+
+The fast forward/slow forward command shall only carry the Scale header, representing that it starts playing from the current position at the specified speed, without carrying the Range header.
+
+Example:
+
+```
+PLAY RTSP/2.0  
+CSeq:3  
+Scale:2.0
+```
+
+#### **CD-4: Random playback command**
+
+The PLAY request message sent by the client shall support the Range header field, use the SMPTE relative timestamp range, and realize random playback, representing that it skips to the time point specified by the Range header at the current play speed, without carrying the Range header.
+
+Example:
+
+```
+PLAY RTSP/2.0  
+CSeq:4  
+Range:npt=100-
+```
+
+#### **CD-5: Stop command**
+
+The client sends the TEARDOWN request message to stop the sending of the specified stream, terminate the session, and release the resources.
+
+#### **CD-6: Response command**
+
+The client and the server shall support the state codes of 200, 4XX and 5XX for the response command. See [IETF RFC 7826].
+
+#### **CD-7: Value ranges for Scale and Range header fields**
+
+The Scale header shall support the basic values of 0.25, 0.5, 1, 2 and 4.
+
+The value of the Range header is the relative value with respect to the starting point of the recorded video to be played, with the value ranging from 0 to the end time of the video played. The parameters, taking *s* as the unit, cannot be negative. If the value of the Range header is 0, it represents that it starts playing from the starting point; if the value of the Range header is 100, it represents that it starts playing from the point of 100s after the starting point of the recorded video; if the value of the Range header is now, it represents that it starts playing from the current position.
+
+## 7.4 Media stream keepalive mechanism
+
+The keepalive mechanism for the media stream of VSS and PU is specified as follows.
+
+- 1) After the media link is established, the VSS shall have the capability of monitoring media stream losses. If any media stream loss is monitored, the media link shall be released, and it shall notify the other interconnected VSS through Bye messages in the session;
+- 2) Status monitoring shall be performed through registration, status information reporting, etc. between the interconnected VSSs, between the VSS and the PU, and between the VSS and the CU. If the media stream receiver or media stream sender is monitored to be faulty or off-line, it shall actively release the media link and stop sending the media stream;
+- 3) The sent stream shall be cleared and judged by the Subject identification. When a CCS sends a call request to another CCS or a CCS sends a call request to a PU, it shall carry the Subject header field, and the "media stream sender ID: sender's media stream SN" in the Subject header field is used as the identification of the media source, and the identification corresponds to the requested code stream. Upon receiving the call request, the requested VSS or the PU shall judge whether the code stream identified by the media source is being sent. If it has been sent, the existing media stream sending link shall be released, and a new media stream sending link shall be established according to the request.
+
+## 7.5 Transmission of multiple response messages
+
+The response to a catalogue query, the response to a file query and the notification message after subscription may require the sending of multiple records for the response or notification message, whereby the notification message could transmit the records in batches through multiple responses or notification messages, and the SN value of each response message shall be the same as the request message. In order to ensure the stability and reliability of transmission of multiple responses or notification messages, the serial transmission method should be used for transmitting multiple responses or notification messages, and the record sender shall perform the subsequent transmission processing after receiving the SIP response to the previous SIP Message. When the records to be transmitted reach the level of one hundred records, in order to shorten the transmission time, multiple records should be carried in each response message, and the maximum records carried shall be 10000 records for each response message. When the response and notification messages exceed 10000, they should use the transmission control protocol (TCP) for transmission.
+
+The SIP protocol stack shall support the SIP message receiving and sending processing by the TCP method, and the processing mechanism shall comply with the provisions of Chapter 18 "Transport" in [IETF RFC 3261].
+
+Under the condition that the catalogue query or file query has no query results, the value of SumNum in the returned response shall be 0, and it shall not carry the record list. The file query response is taken as an example as follows:
+
+```
+<?xml version="1.0"?>
+<Response>
+<CmdType> RecordInfo </CmdType>
+<SN>17430</SN>
+<DeviceID>0086110100000013100000001</DeviceID>
+<Name>Camera1</Name>
+<SumNum>0</SumNum>
+</Response>
+```
+
+## 7.6 RTP-based video or audio data packaging
+
+### 7.6.1 RTP-based PS packaging of video or audio data
+
+The RTP-based program stream (PS) packaging firstly packages the video or audio 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 video keyframe is as shown in Figure 7-2, showing packetized elementary stream video (PESV) and packetized elementary stream audio (PESA) packages, while the PS package structure of a video non-keyframe 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 7-2: Typical PS package structure for a video keyframe. The diagram shows a horizontal sequence of five boxes: PS package header, System header, PSM, PESV, and PESA. Below the boxes is the text H.627(20)_F7-2.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg)
+
+|                   |               |     |      |      |
+|-------------------|---------------|-----|------|------|
+| PS package header | System header | PSM | PESV | PESA |
+|-------------------|---------------|-----|------|------|
+
+H.627(20)\_F7-2
+
+Figure 7-2: Typical PS package structure for a video keyframe. The diagram shows a horizontal sequence of five boxes: PS package header, System header, PSM, PESV, and PESA. Below the boxes is the text H.627(20)\_F7-2.
+
+**Figure 7-2 – 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 video and audio stream IDs (stream\_id) are as follows:
+
+- a) video stream ID: 0xE0;
+- b) audio stream ID: 0xC0.
+
+For the various video or audio formats specified in this Recommendation, the values for media stream types (stream\_type) in PSM are as follows:
+
+- a) ITU-T H.264 video stream: 0x1B;
+- b) ITU-T H.265 video stream: 0x24;
+- c) ITU-T G.711A audio stream: 0x90;
+- d) ITU-T G.711U audio stream: 0x91;
+- e) ITU-T G.723.1 audio stream: 0x93;
+- f) ITU-T G.729 audio stream: 0x99;
+- g) advanced audio coding (AAC) audio stream: 0x0f.
+
+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:
+
+- a) payload type: 96;
+- b) encoding name: PS;
+- c) clock rate: 90 kHz;
+- d) the "Media" item of the "m" field in the SDP description (see clause 7.7): video.
+
+### 7.6.2 RTP-based elementary stream packaging of video or audio data
+
+The video or audio data is directly packaged into the RTP packages as payloads.
+
+#### **1: RTP packaging for ITU-T H.264 video stream**
+
+The RTP payload format for ITU-T H.264 shall comply with the relevant provisions of [IETF RFC 6184].
+
+Selection of payload type identification number of RTP packages for ITU-T H.264 video stream: It shall be selected from the dynamic range (96-127) in Table 5 of [IETF RFC 3551], which is recommended to be set as 98.
+
+#### **2: RTP packaging for ITU-T H.265 video stream**
+
+The RTP payload format for ITU-T H.265 shall comply with the relevant provisions of [IETF RFC 7798].
+
+Selection of payload type identification number of RTP packages for ITU-T H.265 video stream: It shall be selected from the dynamic range (96–127) in Table 5 of [IETF RFC 3551], which is recommended to be set as 100.
+
+#### **3: RTP packaging for audio stream**
+
+Audio streams should be packaged to comply with the relevant provisions of [IETF RFC 3551].
+
+The audio payload data of an RTP packet consists of an integer number of audio frames with a length between 20 ms and 180 ms.
+
+##### **a) Main parameters of ITU-T G.711**
+
+The payload type parameters of RTP packages for ITU-T G.711 A-law audio encoding are specified as follows (see Table 4 of [IETF RFC 3551]):
+
+- 1 PT: 8;
+- 2 encoding name: PCMA;
+- 3 clock rate: 8 kHz;
+- 4 number of channels: 1;
+- 5 the "Media" item of the "m" field in the SDP description (see clause 7.7): audio.
+
+##### **b) Main parameters of ITU-T G.723.1**
+
+For the specifications of payload type parameters of RTP packages for ITU-T G.723.1 audio encoding, see G723 in Table 4 of [IETF RFC 3551], with details as follows:
+
+- 1 PT: 4;
+- 2 encoding name: G723;
+- 3 clock rate: 8 kHz;
+- 4 number of channels: 1;
+- 5 the "Media" item of the "m" field in the SDP description (see clause 7.7): audio.
+
+##### **b) Main parameters of ITU-T G.729**
+
+The payload type parameters of RTP packages for ITU-T G.729 audio encoding are specified as follows (see G729 in Table 4 of [IETF RFC 3551]):
+
+- 1 PT: 18;
+- 2 encoding name: G729;
+- 3 clock rate: 8 kHz;
+- 4 number of channels: 1;
+- 5 the "Media" item of the "m" field in the SDP description (see clause 7.7): audio.
+
+## 7.7 SDP definitions
+
+The session description protocol (SDP) carried in the SIP message body in the VSS shall comply with the relevant provisions of [IETF RFC 4566]. It shall have the following fields:
+
+#### a) Session description:
+
+```
+v= (protocol version)
+o= (owner/creator and session identifier)
+s= (session name)
+u=* (URI of description)
+c=* (connection information - not required if included in all media)
+```
+
+#### b) Time description:
+
+```
+t= (time the session is active)
+```
+
+#### c) Media description
+
+```
+m= (media name and transport address)
+c=* (connection information - optional if included at session-level)
+b=* (bandwidth information)
+a=* (zero or more media attribute lines)
+y=* (SSRC)
+f=* (media description)
+```
+
+#### Details:
+
+a **field**: Enable the definition of a field in [IETF RFC 4566] as <encoding name> in a=rtpmap:<payload type><encoding name>/<clock rate> [/<encoding parameters>], and carry the name of the encoder manufacturer using the attribute (i.e., Manufacturer1 or Manufacturer2 for the encoding name of manufacturer). The attribute indicates that the stream is the encoder code of a manufacturer and does not comply with the media stream specified by the standard, and the media stream complied with the specification of the standard does not require for the attribute.
+
+For example:
+
+```
+a=rtpmap:96 Manufacturer1/90000;
+a=rtpmap:96 Manufacturer2/90000.
+```
+
+The a field has the following formats:
+
+- a field can carry the speed parameter, used to control the download speed while downloading files. The format is as follows:
+
+```
+a=downloadspeed: download speed (the value is integral)
+```
+
+- a field can carry the parameter of file size, used for calculating the progress while downloading. The format is as follows:
+
+```
+a=filesize: file size (unit: Byte)
+```
+
+- a field can carry setup and connection as the parameter for TCP connection negotiation, used for the negotiation between the server and the client for the transmission of media streams in the form of TCP, and the negotiation mechanism refers to the specification of [IETF RFC 4571]. The format is as follows:
+
+```
+a=setup:TCP connection method
+```
+
+(representing whether the TCP connection is initiated actively or passively by the SDP sender when RTP over TCP connection is established, "active" for active, and "passive" for passive)
+
+a=connection:new
+
+(representing that when the RTP over TCP transmission is adopted, a new TCP connection can be established or the original TCP connection can be reused, and the method of establishing a new TCP connection can be used in a fixed manner.)
+
+**s field:** In the SIP message between the CCS and media stream receiver/media stream sender, use the s field ID to request the operation type of media streams. "Play" represents real-time media stream; "Playback" represents historical media file playback; "Download" represents historical media file download; "Talk" represents audio intercom.
+
+**u field:** The URI of the video or audio file shall be filed in the u line. The URI value has two modes: concise mode and common mode. The concise mode directly adopts the device ID (compliant with the definition in [ITU-T H.626V2]) and relevant parameters (such as playback type, download type. 0: all; 1: manual; 2: Alarm; 3: time) of the media source (e.g.: a camera) generating the historical media, and the parameters are separated by ":"; the common mode adopts http://storage device ID [/folder]\* /file name, and the [/folder]\* is an L0-N folder.
+
+**m field:** The m field describes the media type, port, transmission layer protocol, load type and other contents of the media. The media type adopts "video" to identify the transmission of video or video and audio mixed contents, and adopts "audio" to identify the transmission of audio contents; the transmission mode adopts "RTP/AVP" to identify the transmission layer protocol of RTP over the user datagram protocol (UDP), and adopts "TCP/RTP/AVP" to identify the transmission layer protocol of RTP over TCP.
+
+For example:
+
+"m=video 6000 RTP/AVP 96" identifies the media type of video or video and audio, the transmission port is 6000, the transmission mode of RTP over UDP is adopted, and the load type is 96.
+
+"m=video 6000 TCP/RTP/AVP 96" identifies the media type of video or video and audio, the transmission port is 6000, the transmission mode of RTP over TCP is adopted, and the load type is 96.
+
+"m=audio 8000 RTP/AVP 8" identifies the media type of audio, the transmission port is 8000, the transmission mode of RTP over UDP is adopted, and the load type is 8.
+
+**t field:** In playback or download, the values in the t line are the start time and end time, separated by " ", see clause 5.9 of [IETF RFC 4566] for the time format, and UNIX timestamp is adopted, namely, the relative time started from 1970-01-01. Both the start time and end time are the moments in the recording period of the audio or video file to be played back or downloaded.
+
+**y field:** It is a decimal integer character string, representing the synchronization source (SSRC) value. The format is as follows: dddddddddd, where the first digit is the flag of the historical or real-time media stream, 0 for real-time, and 1 for historical; the second to the sixth digits take the eighth to 12th of the 24-digit VSS ID as the VSS ID; e.g., taking "10000" from "008613010000002000000001"; the seventh to the 10th digits as the ID of media stream in the VSS, which is a four-digit decimal integer that does not duplicate the last four digits of the SSRC of the media stream generated in the current VSS.
+
+**f field:** f = v/encoding format/resolution/frame rate/type of bitrate/value of bitrate a/encoding format /value of bitrate/sampling rate.
+
+Specific meaning of each item:
+
+v: The subsequent parameters are video parameters; the parameters are separated by "/";
+
+Encoding format (expressed by a decimal integer character string):
+
+1– ITU-T H.264            2– ITU-T H.265
+
+Resolution (expressed by a string):
+
+1 – QCIF    2 – CIF    3 – 4CIF    4 – D1    5 – 720P    6 – 1080P
+
+where QCIF is quarter common intermediate format and CIF is common intermediate format.
+
+The rest of the resolution is expressed by W\*H (W is width and H is height).
+
+Frame rate (expressed by a decimal integer character string): 0~99.
+
+Type of bitrate (expressed by a decimal integer character string):
+
+1 – Constant bitrate (CBR) 2 – Variable bitrate (VBR)
+
+Size of bitrate (expressed by a decimal integer character string): 0~100000 (e.g.: 1 represents 1 kbit/s).
+
+a: The subsequent parameters are audio parameters; the parameters are separated by "/"
+
+Encoding format (expressed by a decimal integer character string):
+
+1 – ITU-T G.711    2 – ITU-T G.723.1    3 – ITU-T G.729    4–AAC
+
+Value of bitrate (Expressed by a decimal integer character string):
+
+Bitrate of audio:
+
+1–5.3 kbit/s (NOTE – used in [ITU-T G.723.1])
+
+2–6.3 kbit/s (NOTE – used in [ITU-T G.723.1])
+
+3–8 kbit/s (NOTE – used in [ITU-T G.729])
+
+4–64 kbit/s (NOTE – used in [ITU-T G.711])
+
+Sampling rate:
+
+1 – 8 kHz (NOTE – used in [ITU-T G.711]/[ITU-T G.723.1]/[ITU-T G.729])
+
+The characteristics of some concepts used under the Details heading follow.
+
+#### **Descriptions of character string**
+
+The meaning of the decimal integer character string used in this clause is the decimal numerical character string between "0" and "4294967296".
+
+#### **Parameter separator**
+
+The parameters are separated by "/", and the separator "/" between parameters cannot be omitted.
+
+If a parameter between two separators "/" is null, (namely, two separators "/" are next to each other), it represents the non-existence of such a parameter value.
+
+#### **Descriptions of f field**
+
+When the f field is used, it shall ensure the structural integrity of video and audio parameters, i.e., the structure of the f field shall be an integral structure at any time:
+
+f = v/encoding format/resolution/frame rate/type of bitrate/value of bitrate a/encoding format /value of bitrate/sampling rate
+
+If there is video only, the parameter items in audio can be omitted, but the "a///" structure shall be maintained:
+
+f = v/encoding format /resolution /frame rate/type of bitrate/value of bitrate a///
+
+If there is audio only, it shall also be processed similarly, the parameter items in videos can be omitted, but the "v///" structure shall be maintained:
+
+f = v////a/encoding format/size of bitrate/sampling rate
+
+In the f field, space separation is unnecessary between the video and audio parameter fields.
+
+The resolution parameter in the f field can be used for identifying the streams of different resolutions for the same device.
+
+#### SSRC usage
+
+The SSRC is generated by the VSS where the PU is located, and it is used as the ID of the media stream. The processing methods of the SSRC within a VSS and between two VSSs are explained in a) and b).
+
+##### a) Processing method of the SSRC within a VSS
+
+For the media stream within a VSS, the SSRC is generated by the CCS in the VSS and sent to the PU by the SIP message of the Invite request, the device carries the SDP with the SSRC in the 200 OK response message, and the PU uses the value as the SSRC of RTP media stream. The specific processing method is shown in Figure 7-3.
+
+![Sequence diagram showing the processing method of the SSRC within a VSS between CCS/MS and PU.](75e4b78ee25f885d73120e3066a5253e_img.jpg)
+
+```
+sequenceDiagram
+    participant CCS/MS
+    participant PU
+    Note left of CCS/MS: Generating the SSRC
+    CCS/MS->>PU: Invite (SDP with SSRC)
+    PU-->>CCS/MS: 200 OK (SDP with SSRC)
+    CCS/MS->>PU: ACK
+    Note right of PU: RTP stream using the SSRC generated by the VSS
+    PU-->>CCS/MS: RTP stream
+```
+
+The diagram illustrates the interaction between a CCS/MS (Client Control System/Media Server) and a PU (Processing Unit). The sequence of events is as follows: 1. The CCS/MS generates an SSRC (indicated by a self-loop arrow). 2. The CCS/MS sends an 'Invite (SDP with SSRC)' message to the PU. 3. The PU responds with a '200 OK (SDP with SSRC)' message. 4. The CCS/MS sends an 'ACK' message to the PU. 5. The PU sends an 'RTP stream using the SSRC generated by the VSS' to the CCS/MS. The final message is highlighted with a green arrow. The diagram is labeled 'H.627(20)\_F7-3' at the bottom right.
+
+Sequence diagram showing the processing method of the SSRC within a VSS between CCS/MS and PU.
+
+Figure 7-3 – Processing method of the SSRC within a VSS
+
+#### b) Processing method of the SSRC between two VSSs
+
+For the media stream between two VSSs, the SSRC is generated by the VSS B and carried in the 200 OK SDP message body sent by the VSS B, and the RTP stream sent by the VSS B uses the SSRC. The specific processing method is shown in Figure 7-4.
+
+![Sequence diagram showing the processing method of the SSRC between two VSSs (VSS A and VSS B).](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg)
+
+```
+sequenceDiagram
+    participant VSS A
+    participant VSS B
+    Note right of VSS B: Generating the SSRC
+    VSS A->>VSS B: Invite (with SDP)
+    VSS B-->>VSS A: 200 OK (SDP with SSRC)
+    VSS A->>VSS B: ACK
+    VSS B->>VSS A: RTP stream using the SSRC generated by the VSS B
+```
+
+The diagram illustrates the interaction between VSS A and VSS B for SSRC generation and RTP stream transmission. VSS A sends an 'Invite (with SDP)' to VSS B. VSS B performs an internal action labeled 'Generating the SSRC'. VSS B then responds with a '200 OK (SDP with SSRC)' message. VSS A replies with an 'ACK' message. Finally, VSS B sends an 'RTP stream using the SSRC generated by the VSS B' to VSS A. The diagram is labeled 'H.627(20)\_F7-4' at the bottom right.
+
+Sequence diagram showing the processing method of the SSRC between two VSSs (VSS A and VSS B).
+
+**Figure 7-4 – Processing method of the SSRC between two VSSs**
+
+#### Additional descriptions for error response
+
+When the PU receives an SDP that is un usable, it shall send a status-code of 488 response message to the VSS; when the PU cannot accept a more invite request, it shall send a status-code of 486 response message to the VSS.
+
+## 7.8 TCP-based media transmission
+
+The TCP media transmission for real-time media stream, historical media stream playback and download shall support the video and audio PS streams based on the RTP 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 PU sends a media stream to the MS, the PU shall serve as the client for TCP media stream transmission, and the MS shall serve as the server for TCP media stream transmission. In the case of TCP-based video stream transmission between two MSs, the media stream receiver should serve as the server for the TCP media stream transmission.
+
+The media stream sender and receiver can extend the SDP parameters for the negotiation of server and client for the TCP media stream transmission. For the negotiation mechanism, see clause 7.7 and the specification in [IETF RFC 4571].
+
+The TCP media transmission for real-time media stream, historical media stream playback, and download should support the reconnection mechanisms when establishing TCP connections. The first TCP connection fails. The TCP media-streaming client should be reconnected at intervals. The reconnection interval should be no less than 1 s, and the number of reconnections should be no less than three.
+
+# 8 Signalling flows and relevant protocols
+
+## 8.1 Registration and de-registration
+
+### 8.1.1 Basic requirements
+
+An SIP user agent (UA), including PU, CU, control protocol gateway (CPG), MS and the other CCS with a signal routing gateway (SRG), 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 digest authentication method.
+
+The SIP UA shall update the registration in the CCS 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 shall 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 s generally.
+
+The registration expiry time of the SIP UA shall be configurable, and the default value is 86 400 s (1 day). The registration-updating message shall be sent before the expiry of the registration, thereby leaving a proper registration updating time for the CCS, and the registration expiry time shall not be less than 3 600 s.
+
+If the SIP UA registration is successful, the CCS is deemed as online. If the registration fails, the CCS is considered to be offline. The SIP UA is deemed as online by the CCS after the SIP UA registration is successful. If the registration expires, the SIP UA is considered to be offline.
+
+For SIP UA and CCS to identify each other's protocol versions, the extension field, in the header of the SIP registration and its response message (whether success 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 digest specified in [IETF RFC 3261]. For the specific registration signalling flow, see Figure 8-1.
+
+![Sequence diagram showing the signalling flow of registration between CCS and SIP UA.](2119293733c74fc64de88aefd597f4bb_img.jpg)
+
+```
+sequenceDiagram
+    participant CCS
+    participant SIP_UA as SIP UA
+    Note right of SIP_UA: H.627(20)_F8-1
+    SIP_UA->>CCS: 1: Register
+    CCS-->>SIP_UA: 2: 401 unauthorized
+    SIP_UA->>CCS: 3: Register
+    CCS-->>SIP_UA: 4: 200 OK
+```
+
+The diagram illustrates the four-step registration process between a CCS and a SIP UA. The sequence is as follows: 1. The SIP UA sends a 'Register' message to the CCS. 2. The CCS responds with a '401 unauthorized' message. 3. The SIP UA sends another 'Register' message, presumably with authentication. 4. The CCS responds with a '200 OK' message, indicating successful registration. The diagram is labeled 'H.627(20)\_F8-1' at the bottom right.
+
+Sequence diagram showing the signalling flow of registration between CCS and SIP UA.
+
+Figure 8-1 – Signalling flow of registration
+
+The signalling flow description is as follows.
+
+- The SIP UA sends the REGISTER request to the CCS.
+- The CCS 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 CCS, and provides a trust letter in the authorization field of the request, including authentication information.
+- The CCS 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.
+
+See the examples of registration messages in clause 8.1.4.1.
+
+#### 8.1.2.2 De-registration
+
+For the de-registration signalling flow, see Figure 8-2.
+
+![Sequence diagram showing the signalling flow of de-registration between a CCS and a SIP UA. The flow consists of four steps: 1. SIP UA sends a Register (Expires = 0) to CCS; 2. CCS responds with 401 unauthorized; 3. SIP UA resends Register (Expires = 0); 4. CCS responds with 200 OK.](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg)
+
+```
+sequenceDiagram
+    participant CCS
+    participant SIP_UA
+    Note right of SIP_UA: H.627(20)_F8-2
+    SIP_UA->>CCS: 1: Register (Expires = 0)
+    CCS-->>SIP_UA: 2: 401 unauthorized
+    SIP_UA->>CCS: 3: Register (Expires = 0)
+    CCS-->>SIP_UA: 4: 200 OK
+```
+
+Sequence diagram showing the signalling flow of de-registration between a CCS and a SIP UA. The flow consists of four steps: 1. SIP UA sends a Register (Expires = 0) to CCS; 2. CCS responds with 401 unauthorized; 3. SIP UA resends Register (Expires = 0); 4. CCS responds with 200 OK.
+
+**Figure 8-2 – Signalling flow of de-registration**
+
+The de-registration signalling flow description is as follows:
+
+- The SIP UA sends the REGISTER request to the CCS, and the value of the Expires field is 0, showing that the SIP UA requests to be de-registered;
+- The CCS 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 CCS 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 CCS 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.
+
+See the examples of de-registration messages in clause 8.1.4.2.
+
+### 8.1.3 Protocol interface
+
+For the protocol interface, see [IETF RFC 3261], which specifies the SIP registration protocol.
+
+### 8.1.4 Examples of messages
+
+#### 8.1.4.1 Examples of registration messages
+
+- a) REGISTER sip: CCS code @ CCS domain name or IP address port SIP/2.0  
+Via: SIP/2.0/UDP SIP UA domain name or IP address port  
+From: <sip: SIP UA code@SIP UA domain name>;tag=185326220  
+To: <sip: SIP UA code@SIP UA domain name>  
+Call-ID: ms1214-322164710-681262131542511620107-0@172.18.16.3  
+CSeq: 1 REGISTER  
+Contact: <sip: SIP UA code@ SIP UA IP address port>  
+Max-Forwards: 70  
+Expires: 3600  
+Content-Length: 0  
+X-Ver: 1.0
+- b) SIP/2.0 401 Unauthorized  
+To: sip: SIP UA code @ SIP UA domain name  
+Content-Length: 0  
+CSeq: 1 REGISTER  
+Call-ID: ms1214-322164710-681262131542511620107-0@172.18.16.3  
+From: <sip: SIP UA code@SIP UA domain name>; tag=185326220  
+Via: SIP/2.0/UDP SIP UA domain name or IP address port  
+WWW-Authenticate: Digest realm="008611010000",nonce="6fe9ba44a76be22a"  
+X-Ver: 1.0
+- c) REGISTER sip: CCS code@CCS domain name or IP address port SIP/2.0  
+Via: SIP/2.0/UDP SIP UA domain name or IP address port  
+From: <sip: SIP UA code@SIP UA domain name>; tag=185326220  
+To: <sip: SIP UA code@SIP UA domain name>  
+Call-ID: ms1214-322164710-681262131542511620107-0@172.18.16.3  
+CSeq: 2 REGISTER  
+Contact: <sip: SIP UA code@SIP UA IP address port>  
+Authorization: Digest username="008611010000002020000001",  
+realm="008611010000", nonce="6fe9ba44a76be22a",  
+uri="sip:008611010000002000000001@172.18.16.5:5060",  
+response="9625d92d1bddea7a911926e0db054968", algorithm=MD5  
+Max-Forwards: 70  
+Expires: 3600  
+Content-Length: 0  
+X-Ver: 1.0
+- d) SIP/2.0 200 OK  
+To: <sip: SIP UA code@ SIP UA domain name>; tag=69113a2a  
+Contact: sip: SIP UA code@ SIP UA IP address port  
+Content-Length: 0  
+CSeq: 2 REGISTER  
+Call-ID: ms1214-322164710-681262131542511620107-0@172.18.16.3  
+From: <sip: SIP UA code@ SIP UA domain name>; tag=185326220  
+Via: SIP/2.0/UDP SIP UA domain name or IP address port  
+Date: 2010-11-02T15:01:26.115  
+Expires: 3600  
+X-Ver: 1.0
+
+#### 8.1.4.2 Examples of de-registration messages
+
+- a) REGISTER sip: CCS code @ CCS domain name or IP address port SIP/2.0  
+Via: SIP/2.0/UDP SIP UA domain name or IP address port  
+From: <sip: SIP UA code@ SIP UA domain name>; tag=185326220  
+To: <sip: SIP UA code@ SIP UA domain name>  
+Call-ID: ms1214-322164710-681262131542511620107-0@172.18.16.3
+
+```
+
+CSeq: 1 REGISTER
+Contact: <sip: SIP UA code@ SIP UA IP address port>
+Max-Forwards: 70
+Expires: 0
+Content-Length: 0
+X-Ver: 1.0
+
+```
+
+##### b) **SIP/2.0 401 Unauthorized**
+
+```
+
+To: sip: SIP UA code @ SIP UA domain name
+Content-Length: 0
+CSeq: 1 REGISTER
+Call-ID: ms1214-322164710-681262131542511620107-0@172.18.16.3
+From: <sip: SIP UA code@ SIP UA domain name>; tag=185326220
+Via: SIP/2.0/UDP SIP UA domain name or IP address port
+WWW-Authenticate: Digest realm="008611010000", nonce="6fe9ba44a76be22a"
+X-Ver: 1.0
+
+```
+
+##### c) **REGISTER sip: CCS code@CCS domain name or IP address port SIP/2.0**
+
+```
+
+Via: SIP/2.0/UDP SIP UA domain name or IP address port
+From: <sip: SIP UA code@ SIP UA domain name>; tag=185326220
+To: <sip: SIP UA code@ SIP UA domain name>
+Call-ID: ms1214-322164710-681262131542511620107-0@172.18.16.3
+CSeq: 2 REGISTER
+Contact: <sip: SIP UA code@ SIP UA IP address port>
+Authorization: Digest username="008611010000002020000001",
+realm="008611010000", nonce="6fe9ba44a76be22a",
+uri="sip:008611010000002000000001@172.18.16.5:5060",
+response="9625d92d1bddea7a911926e0db054968", algorithm=MD5
+Max-Forwards: 70
+Expires: 0
+Content-Length: 0
+X-Ver: 1.0
+
+```
+
+##### d) **SIP/2.0 200 OK**
+
+```
+
+To: <sip: SIP UA code@ SIP UA domain name>; tag=69113a2a
+Contact: sip: SIP UA code@ SIP UA IP address port
+Content-Length: 0
+CSeq: 2 REGISTER
+Call-ID: ms1214-322164710-681262131542511620107-0@172.18.16.3
+From: <sip: SIP UA code@ SIP UA domain name>; tag=185326220
+Via: SIP/2.0/UDP SIP UA domain name or IP address port
+Date: 2010-11-02T15:01:26.115
+Expires: 0
+X-Ver: 1.0
+
+```
+
+## 8.2 Real-time media stream
+
+### 8.2.1 Basic requirements
+
+The SIP message of real-time media stream shall be routed and forwarded through the CCS in the VSS or other VSSs, and the real-time media stream of the target device should be forwarded through the MS in the VSS.
+
+The session connection of real-time media stream is achieved with the INVITE method in the SIP [IETF RFC 3261], and the media transmission is achieved through the RTP or RTCP [IETF RFC 3550][IETF RFC 4571].
+
+The signalling process of real-time media stream can be initiated by the media stream receiver and by a third party unit, and the VSS can select one method or the combination of the two methods for the implementation. The third-party controller should be achieved by using the back-to-back user agent (B2BUA); for third-party call control, see [IETF RFC 3725].
+
+The real-time media stream should support the media stream keepalive mechanism specified in clause 7.4.
+
+### 8.2.2 Signalling process
+
+#### 8.2.2.1 Initiation by media stream receiver
+
+The signalling flow of real-time media stream initiated by media stream receiver refers to Figure 8-3.
+
+![Sequence diagram showing the signalling flow of a real-time media stream initiated by a media stream receiver. The diagram involves four lifelines: Media stream receiver, CCS, MS, and Media stream sender. The process involves multiple messages (Invite, 200 OK, ACK, BYE) and two real-time media streams.](e90987faabad6a6665cd8ed1151dc474_img.jpg)
+
+```
+sequenceDiagram
+    participant MS as Media stream sender
+    participant MSR as Media stream receiver
+    participant CCS as CCS
+    participant MS2 as MS
+
+    Note right of MS: H.627(20)_F8-3
+
+    MSR->>CCS: 1: Invite (with SDP)
+    CCS->>MS2: 2: Invite
+    MS2-->>CCS: 3: 200 OK (with SDP)
+    CCS->>MS: 4: Invite (with SDP)
+    MS-->>CCS: 5: 200 OK (with SDP)
+    CCS->>MS2: 6: ACK (with SDP)
+    MS2-->>MS: 7: ACK
+    Note right of MS: Real-time media stream
+    MS->>MS2: 8: Invite (with SDP)
+    MS2-->>MS: 9: 200 OK (with SDP)
+    MS2-->>CCS: 10: 200 OK (with SDP)
+    CCS->>MSR: 11: ACK
+    CCS->>MS2: 12: ACK
+    Note left of MS: Real-time media stream
+    MSR->>CCS: 13: BYE
+    MSR-->>CCS: 14: 200 OK
+    CCS->>MS2: 15: BYE
+    MS2-->>CCS: 16: 200 OK
+    CCS->>MS2: 17: BYE
+    MS2-->>CCS: 18: 200 OK
+    CCS->>MS: 19: BYE
+    MS-->>CCS: 20: 200 OK
+```
+
+Sequence diagram showing the signalling flow of a real-time media stream initiated by a media stream receiver. The diagram involves four lifelines: Media stream receiver, CCS, MS, and Media stream sender. The process involves multiple messages (Invite, 200 OK, ACK, BYE) and two real-time media streams.
+
+Figure 8-3 – Signalling flow of real-time media stream initiated by media stream receiver
+
+The media stream receiver includes the CU or the other VSS. The media stream sender includes the PU or the other VSS.
+
+In Figure 8-3:
+
+signals 1, 8, 9, 10, 11 and 12 constitute the process of establishing the media link between the media stream receiver and the MS with the B2BUA method by the CCS after receiving the client call request;
+
+signals 2–7 constitute the process of establishing the media link between the MS and the media stream sender through the third-party call control by the CCS;
+
+signals 13–16 constitute the process of the media stream receiver disconnecting the media link with the MS;
+
+signals 17–20 constitute the process of disconnecting the media link between the MS and the media stream sender by the CCS.
+
+The signalling flow description is as follows.
+
+- The media stream receiver sends the Invite message to the CCS, and the message header field carries the subject field, showing such parameters as source ID of real-time media stream, sender media stream SN, media stream receiver ID and receiver media stream SN, the s field in the SDP message is "Play", representing real-time media stream.
+- After the CCS receives the Invite request, the media connection between the MS and the media stream sender is established through third-party call control. The Invite message is sent to the MS, and this message does not carry the SDP message body.
+- After the MS receives the Invite request of the CCS, it replies with the 200 OK response, carrying the SDP message body in which the Internet protocol (IP), port, media format, etc. of the media stream received by the MS are described.
+- After the CCS receives the 200 OK response sent from the MS, it sends the Invite request to the media stream sender; the request carries the 200 OK response message body sent by the MS in message 3, and the s field is "Play", representing the real-time media stream; the y field is added to describe the SSRC value and f field for the media parameters.
+- After the media stream sender receives the Invite request from the CCS, it replies with the 200 OK response, carrying the SDP message body in which the IP, port, media format, SSRC field, etc. of the media stream sent by the media stream sender are described.
+- After the CCS receives the 200 OK response sent back from the media stream sender, it sends the acknowledgement (ACK) request to the MS, which carries the 200 OK response message body sent by the media stream sender in message 5, and the establishment process of the Invite session with the MS is finished.
+- After the CCS receives the 200 OK response sent back from the media stream sender, it sends an ACK request to the media stream sender, which does not carry a message body, and the establishment process of the Invite session with the media stream sender is finished.
+- Upon the completion of third party call control, the CCS establishes the media connection between the media stream receiver and the MS with the B2BUA method, adds the SSRC value to message 1 and forwards it to the MS.
+- After the MS receives the Invite request, it replies with the 200 OK response, carrying the SDP message body in which the IP, port, media format, SSRC value, etc. of the media stream sent by the MS are described.
+- The CCS forwards message 9 to the media stream receiver.
+- After the media stream receiver receives the 200 OK response, it replies with the ACK message, and the establishment process of the Invite session with CCS is finished.
+- The CCS forwards message 11 to the MS, and the establishment process of the Invite session with the MS is finished.
+- The media stream receiver sends the BYE message to the CCS, and the Invite session with the media stream receiver established by messages 1, 10 and 11 is disconnected.
+- After the CCS receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- After the CCS receives the BYE message, it sends the BYE message to the MS, and the Invite session with the MS established by messages 8, 9 and 12 is disconnected.
+- After the MS receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+
+- The CCS sends the BYE message to the MS, and the Invite session with the MS established by messages 2, 3 and 6 is disconnected.
+- After the MS receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- The CCS sends the BYE message to the media stream sender, and the Invite session with the media stream sender established by messages 4, 5 and 7 is disconnected.
+- After the media stream sender receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+
+See the examples of real-time media stream messages initiated by the media stream receiver in clause 8.2.4. 1.
+
+#### 8.2.2.2 Third-party call control
+
+The signalling flow of real-time media stream initiated by a third party unit is shown in Figure 8-4.
+
+![Sequence diagram showing the signalling flow of real-time media stream initiated by a third party unit. The diagram involves four lifelines: Media stream receiver, CCS, MS, and Media stream sender. The sequence starts with CCS sending an Invite to MS, followed by a 200 OK response. CCS then sends an Invite to Media stream sender, which responds with 200 OK. CCS sends an ACK to MS, and MS sends an ACK to Media stream sender. A real-time media stream is established from Media stream sender to MS. The Media stream receiver sends an Invite to CCS, which responds with 200 OK. CCS sends an Invite to MS, which responds with 200 OK. Media stream receiver sends an ACK to CCS, and CCS sends an ACK to MS. A real-time media stream is established from MS to Media stream receiver. The Media stream receiver sends a BYE to CCS, which responds with 200 OK. CCS sends a BYE to MS, which responds with 200 OK. CCS sends a BYE to Media stream sender, which responds with 200 OK.](474a819357587e34949a3e110ff19b30_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MSReceiver as Media stream receiver
+    participant CCS
+    participant MS
+    participant MSSender as Media stream sender
+
+    Note right of MS: Real-time media stream
+    CCS->>MS: 1: Invite
+    MS-->>CCS: 2: 200 OK (with SDP)
+    CCS->>MSSender: 3: Invite (with SDP)
+    MSSender-->>CCS: 4: 200 OK (with SDP)
+    CCS->>MS: 5: ACK (with SDP)
+    MS->>MSSender: 6: ACK
+    Note right of MS: Real-time media stream
+    MSReceiver->>CCS: 7: Invite
+    MSReceiver-->>CCS: 8: 200 OK (with SDP)
+    CCS->>MS: 9: Invite (with SDP)
+    MS-->>CCS: 10: 200 OK (with SDP)
+    MSReceiver->>CCS: 11: ACK (with SDP)
+    CCS->>MS: 12: ACK
+    Note left of MS: Real-time media stream
+    MSReceiver->>CCS: 13: BYE
+    MSReceiver-->>CCS: 14: 200 OK
+    CCS->>MS: 15: BYE
+    MS-->>CCS: 16: 200 OK
+    CCS->>MS: 17: BYE
+    MS-->>CCS: 18: 200 OK
+    CCS->>MSSender: 19: BYE
+    MSSender-->>CCS: 20: 200 OK
+  
+```
+
+Sequence diagram showing the signalling flow of real-time media stream initiated by a third party unit. The diagram involves four lifelines: Media stream receiver, CCS, MS, and Media stream sender. The sequence starts with CCS sending an Invite to MS, followed by a 200 OK response. CCS then sends an Invite to Media stream sender, which responds with 200 OK. CCS sends an ACK to MS, and MS sends an ACK to Media stream sender. A real-time media stream is established from Media stream sender to MS. The Media stream receiver sends an Invite to CCS, which responds with 200 OK. CCS sends an Invite to MS, which responds with 200 OK. Media stream receiver sends an ACK to CCS, and CCS sends an ACK to MS. A real-time media stream is established from MS to Media stream receiver. The Media stream receiver sends a BYE to CCS, which responds with 200 OK. CCS sends a BYE to MS, which responds with 200 OK. CCS sends a BYE to Media stream sender, which responds with 200 OK.
+
+H.627(20)\_F8-3
+
+**Figure 8-4 – Signalling flow of real-time media stream initiated by a third party unit**
+
+The media stream receiver includes the CU or the other VSS. The media stream sender includes the PU or the other VSS.
+
+In Figure 8-4:
+
+signals 1-6 constitute the process of establishing the media link between the MS and the media stream sender through the third-party call control by the CCS;
+
+signals 7-12 constitute the process of establishing the media link between the media stream receiver and the MS through the third-party call control by the CCS;
+
+signals 13-16 constitute the process of disconnecting the media link between the media stream receiver and MS;
+
+signals 17-20 constitute the process of disconnecting the media link between the MS and the media stream sender.
+
+The signalling flow description is as follows.
+
+- The CCS sends the Invite message to the MS, and this message does not carry the SDP message body.
+- After the MS receives the Invite request of the CCS, it replies with the 200 OK response, carrying the SDP message body in which the IP, port, media format, etc. of the media stream received by the MS are described.
+- After the CCS receives the 200 OK response sent back from the MS, it sends the Invite request to the media stream sender, which carries the 200 OK response message body sent by the MS in message 2, and the s field is "Play", representing real-time media stream; the y field is added to describe the SSRC value and f field for media parameter.
+- After the media stream sender receives the Invite request of the CCS, it replies with the 200 OK response, carrying the SDP message body in which the IP, port, media format, SSRC field, etc. of the media stream sent by the media stream sender are described.
+- After the CCS receives the 200 OK response sent back from the media stream sender, it sends an ACK request to the MS, which carries the 200 OK response message body sent by the media stream sender in message 4, and the establishment process of the Invite session with the MS is finished.
+- After the CCS receives the 200 OK response sent back from the media stream sender, it sends an ACK request to the media stream sender, which does not carry a message body, and the establishment process of the Invite session with the media stream sender is finished.
+- The CCS sends the Invite message to the media stream receiver, and this message does not carry the SDP message body.
+- After the media stream receiver receives the Invite request of the CCS, it replies with the 200 OK response, carrying the SDP message body in which the IP, port, media format, etc. of the media stream received by the media stream receiver are described.
+- After the CCS receives the 200 OK response sent back from the media stream receiver, it sends the Invite request to the MS, which carries the 200 OK response message body sent by the media stream receiver in message 8, and the s field is "Play", representing real-time media stream; the y field is added to describe the SSRC value.
+- After the MS receives the Invite request of the CCS, it replies with the 200 OK response, carrying the SDP message body in which the IP, port, media format, SSRC field, etc. of the media stream sent by the MS are described.
+- After the CCS receives the 200 OK response sent back from the MS, it sends an ACK request to the MS, which carries the 200 OK response message body sent by the MS in message 10, and the establishment process of the Invite session with the media stream receiver is finished.
+- After the CCS receives the 200 OK response sent back from the MS, it sends an ACK request to the MS, which does not carry a message body, and the establishment process of the Invite session with the MS is finished.
+
+- The CCS sends the BYE message to the media stream receiver, and the Invite session with the media stream receiver established by messages 7, 8 and 11 is disconnected.
+- After the media stream receiver receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- The CCS sends the BYE message to the MS, and the Invite session with the MS established by messages 9, 10 and 12 is disconnected.
+- After the MS receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- The CCS sends the BYE message to the MS, and the Invite session with the MS established by messages 1, 2 and 5 is disconnected.
+- After the MS receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- The CCS sends the BYE message to the media stream sender, and the Invite session with the media stream sender established by messages 3, 4 and 6 is disconnected.
+- After the media stream sender receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+
+See the examples of real-time media streams initiated by the third party unit in clause 8.2.4.2.
+
+### 8.2.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.
+
+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 4566]) 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 header of the message sent to the MS shall include the subject field, and the VSS shall support this field, for the detailed specification, see clause 7.2. 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 4566].
+
+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 4566]), and the username in the o line shall be the device code of this device; the device code shall comply with the provisions of the VSS ID in clause 7.1.4 of [ITU-T H.626V2]; the c line shall include the device or system IP address; the m line shall include the media receiving port number.
+
+### 8.2.4 Examples of messages
+
+#### 8.2.4.1 Examples of real-time media stream messages initiated by the media stream receiver
+
+##### a) INVITE sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0
+
+To: sip: media stream sender code@ media stream sender domain name  
+Content-Length: Byte length of message body  
+Contact: <sip: media stream receiver code@ media stream receiver IP address port>  
+CSeq: 1 INVITE  
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bfd0@172.20.16.4  
+Via: SIP/2.0/UDP media stream receiver domain name or IP address  
+From: <sip: media stream receiver code @ media stream receiver domain name>;tag=e3719a0b  
+Subject: Media stream sender ID: Sender's media stream serial number, media stream receiver ID: Receiver's media stream serial number  
+Content-Type: Application/SDP  
+Max-Forwards: 70  
+v=0  
+o=008611010600002020000001 0 0 IN IP4 172.20.16.3  
+s=Play  
+c=IN IP4 172.20.16.3  
+t=0 0  
+m=video 6000 RTP/AVP 96 98 100  
+a=recvonly  
+a=rtpmap:96 PS/90000  
+a=rtpmap:98 H264/90000  
+a=rtpmap:100 H265/90000
+
+##### b) INVITE sip: MS code@MS domain name or IP address port SIP/2.0
+
+To: sip: MS code@MS domain name  
+Content-Length: Byte length of message body  
+Contact: <sip: CCS code@CCS IP address port>  
+CSeq: 1 INVITE  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address port  
+From: <sip: CCS code@CCS domain name>;tag=1ad9931d  
+Subject: Media stream sender ID: Sender's media stream serial number, media stream receiver ID: Receiver's media stream serial number  
+Max-Forwards: 70
+
+##### c) SIP/2.0 200 OK
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=1ad9931d  
+To: <sip: MS code@MS domain name>;tag=3094947605  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+CSeq: 1 INVITE  
+Contact: <sip: MS code@MS domain name or IP address port>  
+Content-Type: Application/SDP  
+Content-Length: Byte length of message body  
+v=0  
+o=008611010000002020000001 0 0 IN IP4 172.18.16.3  
+s=Play  
+c=IN IP4 172.18.16.3  
+t=0 0  
+m=video 6000 RTP/AVP 96 98 100  
+a=recvonly  
+a=rtpmap:96 PS/90000  
+a=rtpmap:98 H264/90000  
+a=rtpmap:100 H265/90000
+
+##### d) INVITE sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0
+
+To: sip: media stream sender code@ media stream sender domain name  
+Content-Length: Byte length of message body  
+Contact: <sip: CCS code@CCS IP address port>  
+CSeq: 1 INVITE  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=f569d024  
+Content-Type: Application/SDP  
+Subject: Media stream sender ID: Sender's media stream serial number,  
+media stream receiver ID: Receiver's media stream serial number  
+Max-Forwards: 70  
+v=0  
+o=008611010000002020000001 0 0 IN IP4 172.18.16.3  
+s=Play  
+c=IN IP4 172.18.16.3  
+t=0 0  
+m=video 6000 RTP/AVP 96 98 100  
+a=reconly  
+a=rtpmap:96 PS/90000  
+a=rtpmap:98 H264/90000  
+a=rtpmap:100 H265/90000  
+y=0100000001
+
+##### e) SIP/2.0 200 OK
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=f569d024  
+To: <sip: media stream sender code@media stream sender domain  
+name>;tag=32128  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+CSeq: 1 INVITE  
+Contact: <sip: media stream sender code@ media stream sender IP address  
+port>  
+Content-Type: Application/SDP  
+Content-Length: Byte length of message body  
+v=0  
+o=0086110100000411100000044 0 0 IN IP4 172.24.18.44  
+s=Play  
+c=IN IP4 172.24.18.44  
+t=0 0  
+m=video 8412 RTP/AVP 96  
+a=sendonly  
+a=rtpmap:96 PS/90000  
+y=1000000001
+
+##### f) ACK sip: MS code@MS domain name or IP address port SIP/2.0
+
+To: <sip: MS code@MS domain name>;tag=3094947605  
+Content-Length: Byte length of message body  
+CSeq: 1 ACK  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=1ad9931d  
+Content-Type: Application/SDP  
+Max-Forwards: 70  
+v=0  
+o=0086110100000411100000044 0 0 IN IP4 172.24.18.44  
+s=Play  
+c=IN IP4 172.24.18.44  
+t=0 0
+
+m=video 8412 RTP/AVP 96  
+a=sendonly  
+a=rtpmap:96 PS/90000  
+y=100000001
+
+##### g) ACK sip: media stream sender code@media stream sender domain name or IP address port SIP/2.0
+
+To: <sip: media stream sender code@media stream sender domain name>;tag=32128  
+Content-Length: Byte length of message body  
+CSeq: 1 ACK  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=f569d024  
+Max-Forwards: 70
+
+##### h) INVITE sip: MS code@MS domain name or IP address port SIP/2.0
+
+To: sip: MS code@MS domain name  
+Content-Length: Byte length of message body  
+Contact: <sip: CCS code@CCS IP address port>  
+CSeq: 1 INVITE  
+Call-ID: wlss-294c2c6e-eea27828118c3b50449185980f4bdfd0@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=02f283d7  
+Subject: Media stream sender ID: Sender's media stream serial number, media stream receiver ID: Receiver's media stream serial number  
+Content-Type: Application/SDP  
+Max-Forwards: 70  
+v=0  
+o=008611010600002020000001 0 0 IN IP4 172.18.16.3  
+s=Play  
+c=IN IP4 172.18.16.3  
+t=0 0  
+m=video 6000 RTP/AVP 96 98 100  
+a=recvonly  
+a=rtpmap:96 PS/90000  
+a=rtpmap:98 H264/90000  
+a=rtpmap:100 H265/90000  
+y=0100000001
+
+##### i) SIP/2.0 200 OK
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=02f283d7  
+To: <sip: MS code@MS domain name>;tag=994072228  
+Call-ID: wlss-294c2c6e-eea27828118c3b50449185980f4bdfd0@172.18.16.5  
+CSeq: 1 INVITE  
+Contact: <sip: MS code@MS IP address port>  
+Content-Type: Application/SDP  
+Content-Length: Byte length of message body  
+v=0  
+o=008611010000002020000001 0 0 IN IP4 172.18.16.1  
+s=Play  
+c=IN IP4 172.18.16.1  
+t=0 0  
+m=video 6000 RTP/AVP 96  
+a=sendonly  
+a=rtpmap:96 PS/90000  
+y=0100000001
+
+##### j) SIP/2.0 200 OK
+
+```
+
+To: <sip: media stream sender code@ media stream sender domain
+name>;tag=949c43d7
+Contact: <sip: media stream sender code@ media stream sender IP address
+port>
+Content-Length: Byte length of message body
+CSeq: 1 INVITE
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bdfd0@172.20.16.4
+Via: SIP/2.0/UDP media stream receiver domain name or IP address
+From: <sip: media stream receiver code@media stream receiver domain
+name>;tag=e3719a0b
+Content-Type: Application/SDP
+v=0
+o=008611010000002020000001 0 0 IN IP4 172.18.16.1
+s=Play
+c=IN IP4 172.18.16.1
+t=0 0
+m=video 6000 RTP/AVP 96
+a=sendonly
+a=rtpmap:96 PS/90000
+y=0100000001
+
+```
+
+##### k) ACK sip: media stream sender code@media stream sender domain name or IP address port SIP/2.0
+
+```
+
+To: <sip: media stream sender code@media stream sender domain
+name>;tag=949c43d7
+Content-Length: Byte length of message body
+CSeq: 1 ACK
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bdfd0@172.20.16.4
+Via: SIP/2.0/UDP media stream receiver domain name or IP address
+From: <sip: media stream receiver code @ media stream receiver domain
+name>;tag=e3719a0b
+Max-Forwards: 70
+
+```
+
+##### l) ACK sip: MS code@MS domain name or IP address port SIP/2.0
+
+```
+
+To: <sip: MS code@MS domain name>;tag=994072228
+Content-Length: Byte length of message body
+CSeq: 1 ACK
+Call-ID: wlss-294c2c6e-eea27828118c3b50449185980f4bdfd0@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>;tag=02f283d7
+Max-Forwards: 70
+
+```
+
+##### m) BYE sip: media stream sender code@media stream sender domain name or IP address port SIP/2.0
+
+```
+
+To: <sip: media stream sender code@media stream sender domain
+name>;tag=949c43d7
+Content-Length: Byte length of message body
+CSeq: 2 BYE
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bdfd0@172.20.16.4
+Via: SIP/2.0/UDP media stream receiver domain name or IP address
+From: <sip: media stream receiver code@media stream receiver domain
+name>;tag=e3719a0b
+Max-Forwards: 70
+
+```
+
+##### n) SIP/2.0 200 OK
+
+```
+
+Via: SIP/2.0/UDP media stream receiver domain name or IP address
+From: <sip: media stream receiver code@media stream receiver domain
+name>;tag=e3719a0b
+To: <sip: media stream sender code@ media stream sender domain
+name>;tag=949c43d7
+
+```
+
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bdfd0@172.20.16.4  
+CSeq: 2 BYE  
+Content-Length: Byte length of message body
+
+##### **o) BYE sip: MS code@MS domain name or IP address port SIP/2.0**
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=02f283d7  
+To: <sip: MS code@MS domain name>;tag=994072228  
+Call-ID: wlss-294c2c6e-eea27828118c3b50449185980f4bdfd0@172.18.16.5  
+Content-Length: Byte length of message body  
+CSeq: 2 BYE  
+Max-Forwards: 70
+
+##### **p) SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=02f283d7  
+To: <sip: MS code@MS domain name>;tag=994072228  
+Call-ID: wlss-294c2c6e-eea27828118c3b50449185980f4bdfd0@172.18.16.5  
+CSeq: 2 BYE  
+Content-Length: Byte length of message body
+
+##### **q) BYE sip: MS code@MS domain name or IP address port SIP/2.0**
+
+To: <sip: MS code@MS domain name>;tag=3094947605  
+Content-Length: Byte length of message body  
+CSeq: 2 BYE  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=1ad9931d  
+Max-Forwards: 70
+
+##### **r) SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=1ad9931d  
+To: <sip: MS code@MS domain name>;tag=3094947605  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+CSeq: 2 BYE  
+Content-Length: Byte length of message body
+
+##### **s) BYE sip: media stream sender code@media stream sender domain name or IP address port SIP/2.0**
+
+To: <sip: media stream sender code@media stream sender domain name>;tag=32128  
+Content-Length: Byte length of message body  
+CSeq: 2 BYE  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=f569d024  
+Max-Forwards: 70
+
+##### **t) SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP source domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=f569d024  
+To: <sip: media stream sender code@media stream sender domain name>;tag=32128  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+CSeq: 2 BYE  
+Content-Length: Byte length of message body
+
+#### 8.2.4.2 Examples of real-time media stream messages called by a third party unit
+
+- a) **INVITE sip: MS code@MS domain name or IP address port SIP/2.0**
+- To: sip: MS code@MS domain name  
+Content-Length: Byte length of message body  
+Contact: <sip: CCS code@CCS IP address port>  
+CSeq: 1 INVITE  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=1ad9931d  
+Subject: Media stream sender ID: Sender's media stream serial number, media stream receiver ID: Receiver's media stream serial number  
+Max-Forwards: 70
+- b) **SIP/2.0 200 OK**
+- Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=1ad9931d  
+To: <sip: MS code@MS domain name>;tag=3094947605  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+CSeq: 1 INVITE  
+Contact: <sip: MS code@MS domain name or IP address port>  
+Content-Type: Application/SDP  
+Content-Length: Byte length of message body  
+v=0  
+o=008611010000002020000001 0 0 IN IP4 172.18.16.3  
+s=Play  
+c=IN IP4 172.18.16.3  
+t=0 0  
+m=video 6000 RTP/AVP 96 98 100  
+a=recvonly  
+a=rtpmap:96 PS/90000  
+a=rtpmap:98 H264/90000  
+a=rtpmap:100 H265/90000
+- c) **INVITE sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0**
+- To: sip: media stream sender code@ media stream sender domain name  
+Content-Length: Byte length of message body  
+Contact: <sip: CCS code@CCS IP address port>  
+CSeq: 1 INVITE  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=f569d024  
+Content-Type: Application/SDP  
+Subject: Media stream sender ID: Sender's media stream serial number, media stream receiver ID: Receiver's media stream serial number  
+Max-Forwards: 70  
+v=0  
+o=008611010000002020000001 0 0 IN IP4 172.18.16.3  
+s=Play  
+c=IN IP4 172.18.16.3  
+t=0 0  
+m=video 6000 RTP/AVP 96 98 100  
+a=recvonly  
+a=rtpmap:96 PS/90000  
+a=rtpmap:98 H264/90000  
+a=rtpmap:100 H265/90000  
+y=0100000001
+- d) **SIP/2.0 200 OK**
+- Via: SIP/2.0/UDP CCS domain name or IP address
+
+```
+
+From: <sip: CCS code@CCS domain name>;tag=f569d024
+To: <sip: media stream sender code@CCS domain name>;tag=32128
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5
+CSeq: 1 INVITE
+Contact: <sip: media stream sender code@media stream sender IP address
+port>
+Content-Type: Application/SDP
+Content-Length: Byte length of message body
+v=0
+o=008611010000041110000044 0 0 IN IP4 172.24.18.44
+s=Play
+c=IN IP4 172.24.18.44
+t=0 0
+m=video 8412 RTP/AVP 96
+a=sendonly
+a=rtpmap:96 PS/90000
+y=100000001
+
+```
+
+##### e) ACK sip: MS code@MS domain name or IP address port SIP/2.0
+
+```
+
+To: <sip: MS code@MS domain name>;tag=3094947605
+Content-Length: Byte length of message body
+CSeq: 1 ACK
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>;tag=1ad9931d
+Content-Type: Application/SDP
+Max-Forwards: 70
+v=0
+o=008611010000041110000044 0 0 IN IP4 172.24.18.44
+s=Play
+c=IN IP4 172.24.18.44
+t=0 0
+m=video 8412 RTP/AVP 96
+a=sendonly
+a=rtpmap:96 PS/90000
+y=100000001
+
+```
+
+##### f) ACK sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0
+
+```
+
+To: <sip: media stream sender code@ media stream sender domain
+name>;tag=32128
+Content-Length: Byte length of message body
+CSeq: 1 ACK
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>;tag=f569d024
+Max-Forwards: 70
+
+```
+
+##### g) INVITE sip: media stream receiver code@ media stream receiver domain name or IP address port SIP/2.0
+
+```
+
+To: sip: media stream receiver code @ media stream receiver domain name
+Content-Length: Byte length of message body
+Contact: <sip: CCS code@CCS IP address port>
+CSeq: 1 INVITE
+Call-ID: wlss-e862d62c-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>;tag=8338d6ac
+Subject: Media stream sender ID: Sender's media stream serial number, media
+stream receiver ID: Receiver's media stream serial number
+Max-Forwards: 70
+
+```
+
+##### **h) SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=8338d6ac  
+To: <sip: media stream receiver code @ media stream receiver domain name>;tag=41  
+Call-ID: wlss-e862d62c-72ff1e2e1d0f2ceaf8d07cf1e3a87f090@172.18.16.5  
+CSeq: 1 INVITE  
+Contact: <sip: media stream receiver code@ media stream receiver IP address port>  
+Content-Type: Application/SDP  
+Content-Length: Byte length of message body  
+v=0  
+o=008611010000003001000001 0 0 IN IP4 172.18.16.126  
+s=Play  
+c=IN IP4 172.18.16.126  
+t=0 0  
+m=video 9010 RTP/AVP 96  
+a=recvonly  
+a=rtpmap:96 PS/90000
+
+##### **i) INVITE sip: MS code@MS domain name or IP address port SIP/2.0**
+
+To: sip: MS code@MS domain name  
+Content-Length: Byte length of message body  
+Contact: <sip: CCS code@CCS IP address port>  
+CSeq: 1 INVITE  
+Call-ID: wlss-19677597-72ff1e2e1d0f2ceaf8d07cf1e3a87f090@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=39a741c5  
+Content-Type: Application/SDP  
+Subject: Media stream sender ID: Sender's media stream serial number, media stream receiver ID: Receiver's media stream serial number  
+Max-Forwards: 70  
+v=0  
+o=008611010000003001000001 0 0 IN IP4 172.18.16.126  
+s=Play  
+c=IN IP4 172.18.16.126  
+t=0 0  
+m=video 9010 RTP/AVP 96  
+a=recvonly  
+a=rtpmap:96 PS/90000  
+y=0100000001
+
+##### **j) SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=39a741c5  
+To: <sip: MS code@MS domain name>;tag=3243635917  
+Call-ID: wlss-19677597-72ff1e2e1d0f2ceaf8d07cf1e3a87f090@172.18.16.5  
+CSeq: 1 INVITE  
+Contact: <sip: MS code@MS domain name or IP address port>  
+Content-Type: Application/SDP  
+Content-Length: Byte length of message body  
+v=0  
+o=008611010000002020000001 0 0 IN IP4 172.18.16.3  
+s=Play  
+c=IN IP4 172.18.16.3  
+t=0 0  
+m=video 6000 RTP/AVP 96  
+a=sendonly  
+a=rtpmap:96 PS/90000  
+y=0100000001
+
+- k) **ACK sip: media stream receiver code@ media stream receiver domain name or IP address port SIP/2.0**
+- ```
+To: <sip: media stream receiver code @ media stream receiver domain name>;tag=41
+Content-Length: Byte length of message body
+CSeq: 1 ACK
+Call-ID: wlss-e862d62c-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>;tag=8338d6ac
+Content-Type: Application/SDP
+Max-Forwards: 70
+v=0
+o=00861101000000020200000001 0 0 IN IP4 172.18.16.3
+s=Play
+c=IN IP4 172.18.16.3
+t=0 0
+m=video 6000 RTP/AVP 96
+a=sendonly
+a=rtpmap:96 PS/90000
+y=0100000001
+```
+- l) **ACK sip: MS code@MS domain name or IP address port SIP/2.0**
+- ```
+To: <sip: MS code@MS domain name>;tag=3243635917
+Content-Length: Byte length of message body
+CSeq: 1 ACK
+Call-ID: wlss-19677597-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>;tag=39a741c5
+Max-Forwards: 70
+```
+- m) **BYE sip: media stream receiver code@ media stream receiver domain name or IP address port SIP/2.0**
+- ```
+To: <sip: media stream receiver code @ media stream receiver domain name>;tag=41
+Content-Length: Byte length of message body
+CSeq: 2 BYE
+Call-ID: wlss-e862d62c-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>;tag=8338d6ac
+Max-Forwards: 70
+```
+- n) **SIP/2.0 200 OK**
+- ```
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>;tag=8338d6ac
+To: <sip: media stream receiver code @ media stream receiver domain name>;tag=41
+Call-ID: wlss-e862d62c-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5
+CSeq: 2 BYE
+Content-Length: Byte length of message body
+```
+- o) **BYE sip: MS code@MS domain name or IP address port SIP/2.0**
+- ```
+To: <sip: MS code@MS domain name>;tag=3243635917
+Content-Length: Byte length of message body
+CSeq: 2 BYE
+Call-ID: wlss-19677597-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>;tag=39a741c5
+Max-Forwards: 70
+```
+
+- p) **SIP/2.0 200 OK**  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=39a741c5  
+To: <sip: MS code@MS domain name>;tag=3243635917  
+Call-ID: wlss-19677597-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5  
+CSeq: 2 BYE  
+Content-Length: Byte length of message body
+- q) **BYE sip: MS code@MS domain name or IP address port SIP/2.0**  
+To: <sip: MS code@MS domain name>;tag=3094947605  
+Content-Length: Byte length of message body  
+CSeq: 2 BYE  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=1ad9931d  
+Max-Forwards: 70
+- r) **SIP/2.0 200 OK**  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=1ad9931d  
+To: <sip: MS code@MS domain name>;tag=3094947605  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+CSeq: 2 BYE  
+Content-Length: Byte length of message body
+- s) **BYE sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0**  
+To: <sip: media stream sender code@ media stream sender domain name>;tag=32128  
+Content-Length: Byte length of message body  
+CSeq: 2 BYE  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=f569d024  
+Max-Forwards: 70
+- t) **SIP/2.0 200 OK**  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>;tag=f569d024  
+To: <sip: media stream sender code@ media stream sender domain name>;tag=32128  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+CSeq: 2 BYE  
+Content-Length: Byte length of message body
+
+## 8.3 Device configuration and control
+
+### 8.3.1 Device configuration
+
+#### 8.3.1.1 Basic requirements
+
+The source sends the device configuration command to the target, and the configuration command types include device parameter configuration, guard/unguard, alarm reset and guard control, and the device configuration is achieved by the MESSAGE method of [IETF RFC 3428]. For details of the configuration parameters, see the device configuration of control command in clause A.2.3.
+
+The sources include a CU, CPG or the other CCS with SRG, and the targets include a PU, CPG or the other CCS with SRG.
+
+After the source sends the device parameter configuration, guard/unguard, alarm reset and guard control commands, the target shall send a response command to represent the executive result. For the signalling process, see clause 8.3.1.2.
+
+#### 8.3.1.2 Signalling process
+
+For the device configuration signalling flow, see Figure 8-5.
+
+![Sequence diagram showing the signalling flow of device configuration between Source, CCS, and Target.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg)
+
+```
+sequenceDiagram
+    participant Source
+    participant CCS
+    participant Target
+    Note right of Target: H.627(20)_F8-5
+    Source->>CCS: 1: Message (Device configuration request command)
+    CCS-->>Source: 2: 200 OK
+    CCS->>Target: 3: Message (Device configuration request command)
+    Target-->>CCS: 4: 200 OK
+    Target->>CCS: 5: Message (Device configuration response command)
+    CCS-->>Target: 6: 200 OK
+    CCS->>Source: 7: Message (Device configuration response command)
+    Source-->>CCS: 8: 200 OK
+```
+
+The diagram illustrates a sequence of eight messages between three entities: Source, CCS, and Target. The interaction begins with the Source sending a 'Message (Device configuration request command)' to the CCS. The CCS responds with '200 OK'. Next, the CCS sends a 'Message (Device configuration request command)' to the Target. The Target replies with '200 OK'. Then, the Target sends a 'Message (Device configuration response command)' to the CCS. The CCS responds with '200 OK'. Finally, the CCS sends a 'Message (Device configuration response command)' to the Source, which replies with '200 OK'. The diagram is labeled 'H.627(20)\_F8-5' in the bottom right corner.
+
+Sequence diagram showing the signalling flow of device configuration between Source, CCS, and Target.
+
+**Figure 8-5 – Signalling flow of device configuration**
+
+The signalling flow description is as follows.
+
+- The source sends device configuration commands to the CCS, and the device configuration commands are carried in the message body by the MESSAGE method.
+- The CCS replies with a 200 OK response after receiving the commands.
+- The CCS 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 CCS, and the device configuration response commands are carried in the message body by the MESSAGE method.
+- The CCS replies with a 200 OK response after receiving the commands.
+- The CCS forwards 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.
+
+See the examples of guard messages in clause 8.3.1.4. The other control commands of device configuration, such as device parameter configuration, unguard, alarm reset and guard control, see clause A.2.3.
+
+#### 8.3.1.3 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). For a detailed description, see the configuration commands in clause A.2.3. 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.
+
+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.3.1.4 Examples of guard messages
+
+- a) MESSAGE sip: target code@target domain name or IP address port SIP/2.0  
+To: <sip: target code@target domain name>  
+Content-Length: Byte length of message body  
+CSeq: 2 MESSAGE  
+Call-ID: a84b4c76e66710  
+Via: SIP/2.0/UDP source domain name or IP address  
+From: <sip: source code@source domain name>; tag=e40807c0  
+Content-Type: Application/ECCS+xml  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Control>  
+<CmdType>DeviceControl</CmdType>  
+<SN>17</SN>  
+<DeviceID>008611010000002020000001</DeviceID>  
+<GuardCmd>SetGuard</GuardCmd>  
+</Control>
+- b) SIP/2.0 200 OK  
+Via: SIP/2.0/UDP source domain name or IP address  
+From: <sip: source code@source domain name>; tag=e40807c0  
+To: <sip: Target code@target domain name>; tag=852843529  
+Call-ID: a84b4c76e66710  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+- c) MESSAGE sip: target code@target domain name or IP address port SIP/2.0  
+To: <sip: target code@target domain name>  
+Content-Length: Byte length of message body  
+CSeq: 2 MESSAGE  
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address
+
+From: <sip: source code@source domain name>; tag=e40807c0  
+Content-Type: Application/ECCS+xml  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Control>  
+<CmdType>DeviceControl</CmdType>  
+<SN>17</SN>  
+<DeviceID>0086110100000020200000001</DeviceID>  
+<GuardCmd>SetGuard</GuardCmd>  
+</Control>
+
+##### **d) SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: source code@source domain name>; tag=e40807c0  
+To: <sip: Target code@target domain name>; tag=852843529  
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+
+##### **e) MESSAGE sip: source code@source domain name or IP address port SIP/2.0**
+
+Via: SIP/2.0/UDP target domain name or IP address  
+From: <sip: Target code@target domain name>; tag=852843529  
+To: <sip: source code@source domain name>  
+Call-ID: de432gtf51u870  
+CSeq: 2 MESSAGE  
+Max-Forwards: 70  
+Content-Type: Application/ECCS+xml  
+Content-Length: Byte length of message body  
+<?xml version="1.0"?>  
+<Response>  
+<CmdType>DeviceControl</CmdType>  
+<SN>17</SN>  
+<DeviceID>0086110100000020200000001</DeviceID>  
+<Result>OK</Result>  
+</Response>
+
+##### **f) SIP/2.0 200 OK**
+
+To: <sip: source code@source domain name>; tag=e40807c0  
+Content-Length: 0  
+CSeq: 2 MESSAGE  
+Call-ID: de432gtf51u870  
+Via: SIP/2.0/UDP target domain name or IP address  
+From: <sip: Target code@target domain name>; tag=852843529
+
+##### **g) MESSAGE sip: source code@source domain name or IP address port SIP/2.0**
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: Target code@target domain name>; tag=852843529  
+To: <sip: source code@source domain name>  
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+CSeq: 2 MESSAGE  
+Max-Forwards: 70  
+Content-Type: Application/ECCS+xml  
+Content-Length: Byte length of message body  
+<?xml version="1.0"?>  
+<Response>  
+<CmdType>DeviceControl</CmdType>  
+<SN>17</SN>  
+<DeviceID>0086110100000020200000001</DeviceID>  
+<Result>OK</Result>  
+</Response>
+
+h) SIP/2.0 200 OK  
+ To: <sip: source code@source domain name>; tag=e40807c0  
+ Content-Length: 0  
+ CSeq: 2 MESSAGE  
+ Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+ Via: SIP/2.0/UDP CCS domain name or IP address  
+ From: <sip: Target code@target domain name>; tag=852843529
+
+### 8.3.2 Recording control
+
+#### 8.3.2.1 Basic requirements
+
+The source sends the recording control command to the target, and the recording control is achieved by the MESSAGE method of [IETF RFC 3428].
+
+The sources include a CU, CPG or the other CCS with SRG, and the targets include a PU, CPG, MS or the other CCS with SRG.
+
+After the source sends the recording control commands, the target shall send a response command to represent the executive result. For the signalling process, see clause 8.3.2.2.
+
+#### 8.3.2.2 Signalling process
+
+For the recording control signalling flow, see Figure 8-6.
+
+![Sequence diagram showing the signalling flow of recording control between Source, CCS, and Target. The flow consists of 8 steps: 1. Source to CCS: Message (Recording control request command); 2. CCS to Source: 200 OK; 3. CCS to Target: Message (Recording control request command); 4. Target to CCS: 200 OK; 5. CCS to Target: Message (Recording control response command); 6. Target to CCS: 200 OK; 7. CCS to Source: Message (Recording control response command); 8. Source to CCS: 200 OK. The diagram is labeled H.627(20)_F8-6 at the bottom right.](a97518a839da75f8379c578562b01bc2_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Source
+    participant CCS
+    participant Target
+    Note right of Target: H.627(20)_F8-6
+    Source->>CCS: 1: Message (Recording control request command)
+    CCS-->>Source: 2: 200 OK
+    CCS->>Target: 3: Message (Recording control request command)
+    Target-->>CCS: 4: 200 OK
+    CCS->>Target: 5: Message (Recording control response command)
+    Target-->>CCS: 6: 200 OK
+    CCS->>Source: 7: Message (Recording control response command)
+    Source-->>CCS: 8: 200 OK
+  
+```
+
+Sequence diagram showing the signalling flow of recording control between Source, CCS, and Target. The flow consists of 8 steps: 1. Source to CCS: Message (Recording control request command); 2. CCS to Source: 200 OK; 3. CCS to Target: Message (Recording control request command); 4. Target to CCS: 200 OK; 5. CCS to Target: Message (Recording control response command); 6. Target to CCS: 200 OK; 7. CCS to Source: Message (Recording control response command); 8. Source to CCS: 200 OK. The diagram is labeled H.627(20)\_F8-6 at the bottom right.
+
+Figure 8-6 – Signalling flow of recording control
+
+The signalling flow description is as follows:
+
+- The source sends recording control commands to the CCS, and the recording control commands are carried in the message body by the MESSAGE method;
+- The CCS replies with a 200 OK response after receiving the commands;
+- The CCS sends recording control commands to the target, and the recording control 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 recording control response commands to the CCS, and the recording control response commands are carried in the message body by the MESSAGE method;
+- The CCS replies with a 200 OK response after receiving the commands;
+
+- The CCS forwards recording control response commands to the source, and the recording control response commands are carried in the message body by the MESSAGE method;
+- The source replies with a 200 OK response after receiving the commands.
+
+See the example of recording control messages in clause 8.3.2.4.
+
+#### 8.3.2.3 Protocol interface
+
+##### a Request command message body
+
+The Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+Recording control commands are specified in the ECCS. For a detailed description, see the control commands in clause A.2.3. The recording control 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 recording control 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.
+
+Recording control response commands are specified in the ECCS. For a detailed description, see the recording control response commands in clause A.2.6 a).
+
+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.3.2.4 Examples of recording control messages
+
+- MESSAGE sip: target code@target domain name or IP address port SIP/2.0  
+ To: <sip: target code@target domain name>  
+ Content-Length: Byte length of message body  
+ CSeq: 2 MESSAGE  
+ Call-ID: a84b4c76e66710  
+ Via: SIP/2.0/UDP source domain name or IP address  
+ From: <sip: source code@source domain name>; tag=e40807c0  
+ Content-Type: Application/ECCS+xml  
+ Max-Forwards: 70  
+ <?xml version="1.0"?>  
+ <Control>  
+ <CmdType>DeviceControl</CmdType>  
+ <SN>17</SN>  
+ <DeviceID>008611010000002020000001</DeviceID>  
+ <RecordCmd>Record</RecordCmd>  
+ </Control>
+- SIP/2.0 200 OK  
+ Via: SIP/2.0/UDP source domain name or IP address  
+ From: <sip: source code@source domain name>; tag=e40807c0  
+ To: <sip: Target code@target domain name>; tag=852843529  
+ Call-ID: a84b4c76e66710  
+ CSeq: 2 MESSAGE  
+ Content-Length: 0
+- MESSAGE sip: target code@target domain name or IP address port SIP/2.0
+
+```
+
+To: <sip: target code@target domain name>
+Content-Length: Byte length of message body
+CSeq: 2 MESSAGE
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: source code@source domain name>; tag=e40807c0
+Content-Type: Application/ECCS+xml
+Max-Forwards: 70
+<?xml version="1.0"?>
+<Control>
+<CmdType>DeviceControl</CmdType>
+<SN>17</SN>
+<DeviceID>008611010000002020000001</DeviceID>
+<RecordCmd>Record</RecordCmd>
+</Control>
+
+```
+
+##### **d) SIP/2.0 200 OK**
+
+```
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: source code@source domain name>; tag=e40807c0
+To: <sip: Target code@target domain name>; tag=852843529
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+CSeq: 2 MESSAGE
+Content-Length: 0
+
+```
+
+##### **e) MESSAGE sip: source code@source domain name or IP address port SIP/2.0**
+
+```
+
+Via: SIP/2.0/UDP target domain name or IP address
+From: <sip: Target code@target domain name>; tag=852843529
+To: <sip: source code@source domain name>
+Call-ID: de432gtf51u870
+CSeq: 2 MESSAGE
+Max-Forwards: 70
+Content-Type: Application/ECCS+xml
+Content-Length: Byte length of message body
+<?xml version="1.0"?>
+<Response>
+<CmdType>DeviceControl</CmdType>
+<SN>17</SN>
+<DeviceID>008611010000002020000001</DeviceID>
+<Result>OK</Result>
+</Response>
+
+```
+
+##### **f) SIP/2.0 200 OK**
+
+```
+
+To: <sip: source code@source domain name>; tag=e40807c0
+Content-Length: 0
+CSeq: 2 MESSAGE
+Call-ID: de432gtf51u870
+Via: SIP/2.0/UDP target domain name or IP address
+From: <sip: Target code@target domain name>; tag=852843529
+
+```
+
+##### **g) MESSAGE sip: source code@source domain name or IP address port SIP/2.0**
+
+```
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: Target code@target domain name>; tag=852843529
+To: <sip: source code@source domain name>
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+CSeq: 2 MESSAGE
+Max-Forwards: 70
+Content-Type: Application/ECCS+xml
+Content-Length: Byte length of message body
+<?xml version="1.0"?>
+<Response>
+<CmdType>DeviceControl</CmdType>
+
+```
+
+```
+
+<SN>17</SN>
+<DeviceID>0086110100000020200000001</DeviceID>
+<Result>OK</Result>
+</Response>
+
+```
+
+##### h) **SIP/2.0 200 OK**
+
+```
+
+To: <sip: source code@source domain name>; tag=e40807c0
+Content-Length: 0
+CSeq: 2 MESSAGE
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: Target code@target domain name>; tag=852843529
+
+```
+
+### 8.3.3 Device control
+
+#### 8.3.3.1 Basic requirements
+
+The source sends the device control command to the target, and the control command types include pan/tilt/zoom (PTZ) control, remote booting, mandatory key frame, zoom-in, zoom-out, PTZ precise angle control and on-screen display (OSD) configuration, and the device control is achieved by the MESSAGE method specified in [IETF RFC 3428].
+
+The sources include a CU, CPG or the other CCS with SRG, and the target devices include a PU, CPG or the other CCS with SRG.
+
+After the source sends the PTZ control, remote booting, mandatory key frame, zoom-in and zoom-out commands to the target, the target does not send a response command. For the signalling process, see clause 8.3.3.2.
+
+#### 8.3.3.2 Signalling process
+
+For the device control signalling flow, see Figure 8-7.
+
+![Sequence diagram showing the signalling flow of device control between Source, CCS, and Target. The flow consists of four steps: 1. Source sends a Message (Device control command) to CCS; 2. CCS responds with 200 OK to Source; 3. CCS sends a Message (Device control command) to Target; 4. Target responds with 200 OK to CCS. The diagram is labeled H.627(20)_F8-7.](f943b07ab747bfd85e302e5a31c20ba8_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Source
+    participant CCS
+    participant Target
+    Note right of Target: H.627(20)_F8-7
+    Source->>CCS: 1: Message (Device control command)
+    CCS-->>Source: 2: 200 OK
+    CCS->>Target: 3: Message (Device control command)
+    Target-->>CCS: 4: 200 OK
+
+```
+
+Sequence diagram showing the signalling flow of device control between Source, CCS, and Target. The flow consists of four steps: 1. Source sends a Message (Device control command) to CCS; 2. CCS responds with 200 OK to Source; 3. CCS sends a Message (Device control command) to Target; 4. Target responds with 200 OK to CCS. The diagram is labeled H.627(20)\_F8-7.
+
+**Figure 8-7 – Signalling flow of device control**
+
+The signalling flow description is as follows.
+
+- The source sends device control commands to the CCS, and the device control commands are carried in the message body by the MESSAGE method.
+- The CCS replies with a 200 OK response after receiving the commands.
+- The CCS sends device control commands to the target, and the device control commands are carried in the message body by the MESSAGE method.
+- The target replies with a 200 OK response after receiving the commands.
+
+See the examples of device control messages in clause 8.3.3.4.
+
+#### 8.3.3.3 Protocol interface
+
+The Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+Device control commands are specified in the ECCS; for a detailed description, see the control commands in clause A.2.3. The device control 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.
+
+#### 8.3.3.4 Examples of device control messages
+
+- a) MESSAGE sip: Target code@target domain name or IP address port SIP/2.0
+- ```
+To: sip: Target code@target domain name
+Content-Length: Byte length of message body
+CSeq: 1 MESSAGE
+Call-ID: a84b4c76e66710
+Via: SIP/2.0/UDP source domain name or IP address
+From: <sip: source code@source domain name>; tag=237f57dc
+Content-Type: Application/ECCS+xml
+Max-Forwards: 69
+<?xml version="1.0"?>
+<Control>
+<CmdType>DeviceControl</CmdType>
+<SN>11</SN>
+<DeviceID>008611010000041310000345</DeviceID>
+<PTZCmd>A50F4D1000001021</PTZCmd>
+</Control>
+```
+- b) SIP/2.0 200 OK
+- ```
+Via: SIP/2.0/UDP source domain name or IP address
+From: <sip: source code@source domain name>; tag=237f57dc
+To: <sip: Target code@target domain name>; tag=13057
+Call-ID: a84b4c76e66710
+CSeq: 1 MESSAGE
+Content-Length: 0
+```
+- c) MESSAGE sip: target code@target domain name or IP address port SIP/2.0
+- ```
+To: sip: target code@target domain name
+Content-Length: Byte length of message body
+CSeq: 1 MESSAGE
+Call-ID: wlss-f304376c-264c72115264900e8257ecale15b0ae3@172.18.16.5
+Via: SIP/2.0/UDP source domain name or IP address
+From: <sip: source code@source domain name>; tag=237f57dc
+Content-Type: Application/ECCS+xml
+Max-Forwards: 69
+<?xml version="1.0"?>
+<Control>
+<CmdType>DeviceControl</CmdType>
+<SN>11</SN>
+<DeviceID>008611010000041310000345</DeviceID>
+<PTZCmd>A50F4D1000001021</PTZCmd>
+</Control>
+```
+- d) SIP/2.0 200 OK
+- ```
+Via: SIP/2.0/UDP source domain name or IP address
+From: <sip: source code@source domain name>; tag=237f57dc
+To: <sip: Target code@target domain name>; tag=13057
+Call-ID: wlss-f304376c-264c72115264900e8257ecale15b0ae3@172.18.16.5
+CSeq: 1 MESSAGE
+```
+
+## 8.4 Alarm event notification and distribution
+
+### 8.4.1 Basic requirements
+
+If an alarm event occurs, the source shall send the alarm message to the CCS, after the CCS receives the alarm message, it distributes the message to the target. In the alarm event notification and distribution, the alarm message is achieved by the MESSAGE method specified in [IETF RFC 3428].
+
+The sources include a PU, CU, CPG or the other CCS with SRG, and the targets include a CU or the other CCS with SRG.
+
+### 8.4.2 Signalling process
+
+For alarm event notification and distribution signalling flow, see Figure 8-8.
+
+![Sequence diagram showing the signalling flow of alarm event notification and distribution between Source, CCS, and Target.](fd76efce549d3713543bb5ed9b023c2e_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Source
+    participant CCS
+    participant Target
+    Note right of Target: H.627(20)_F8-8
+    Source->>CCS: 1: Message (Alarm notification command)
+    CCS-->>Source: 2: 200 OK
+    CCS->>Source: 3: Message (Alarm notification response command)
+    Source-->>CCS: 4: 200 OK
+    CCS->>Target: 5: Message (Alarm notification command)
+    Target-->>CCS: 6: 200 OK
+    CCS->>Target: 7: Message (Alarm notification response command)
+    Target-->>CCS: 8: 200 OK
+  
+```
+
+The diagram illustrates the signalling flow for alarm event notification and distribution. It involves three entities: Source, CCS, and Target. The sequence of messages is as follows:
+ 
+
+- The Source sends a 'Message (Alarm notification command)' to the CCS.
+- The CCS responds with a '200 OK' message.
+- The CCS then sends a 'Message (Alarm notification response command)' to the Source.
+- The Source replies with a '200 OK' message.
+- The CCS sends a 'Message (Alarm notification command)' to the Target.
+- The Target responds with a '200 OK' message.
+- The CCS sends a 'Message (Alarm notification response command)' to the Target.
+- The Target replies with a '200 OK' message.
+
+ The diagram is labeled H.627(20)\_F8-8.
+
+Sequence diagram showing the signalling flow of alarm event notification and distribution between Source, CCS, and Target.
+
+**Figure 8-8 – Signalling flow of alarm event notification and distribution**
+
+The Signalling flow description is as follows.
+
+- The source sends the alarm notification commands to the CCS after the occurrence of the alarm event, and the alarm notification commands are carried in the message body by the MESSAGE method.
+- The CCS replies with a 200 OK response after receiving the commands.
+- The CCS sends the alarm notification response commands to the source after receiving the alarm event, and the alarm notification response commands are carried in the message body by the MESSAGE method.
+- The source replies with a 200 OK response after receiving the commands.
+- The CCS determines the target to be forwarded after receiving the alarm event, and sends the alarm event notification commands to the target, and the alarm notification response 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 alarm notification response commands to the CCS after receiving the alarm event, and the alarm notification response commands are carried in the message body by the MESSAGE method.
+- The CCS replies with a 200 OK response after receiving the commands.
+
+See the examples of alarm event notification and distribution messages in clause 8.4.4.
+
+### 8.4.3 Protocol interface
+
+#### 8.4.3.1 Request command message body
+
+The Content-type field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+Request commands in the alarm event notification and distribution process are specified in the ECCS; for a detailed description, see clause A.2.5 b).
+
+The alarm notification commands sent from the source to the CCS and those sent from the CCS to the target are all carried in the message body by the MESSAGE method. The alarm event notification commands shall include command type (CmdType), command serial number (SN), device code (DeviceID), alarm priority (AlarmPriority), alarm time (AlarmTime), alarm method (AlarmMethod), longitude (Longitude), latitude (Latitude), extension alarm type (AlarmType) and alarm type parameter (AlarmTypeParam).
+
+The relevant devices shall reply with a 200 OK response immediately after receiving a MESSAGE, and the 200 OK response has no message body.
+
+#### 8.4.3.2 Response command message body
+
+The Content-type field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+Response commands in the alarm event notification and distribution process are specified in the ECCS; for a detailed description, see clause A.2.6 b).
+
+The alarm notification response commands sent from the CCS to the source and those sent from the target to the CCS are all carried in the message body by the MESSAGE method. The alarm event notification response commands shall include command type (CmdType), command serial number (SN), device code (DeviceID) and executive result (Result).
+
+The relevant device shall reply with a 200 OK response immediately after receiving a MESSAGE, and the 200 OK response has no message body.
+
+### 8.4.4 Examples of alarm event notification and distribution messages
+
+- a) MESSAGE sip: CCS code @ CCS domain name or IP address port SIP/2.0
+
+```
+To: <sip: CCS code@CCS domain name>
+Content-Length: Byte length of message body
+CSeq: 2 MESSAGE
+Call-ID: a84b4c76e66710
+Via: SIP/2.0/UDP source domain name or IP address
+From: <sip: source code@source domain name>; tag=e40807c0
+Content-Type: Application/ECCS+xml
+Max-Forwards: 70
+<?xml version="1.0"?>
+<Notify>
+<CmdType>Alarm</CmdType>
+<SN>1</SN>
+<DeviceID>008611010000001340000101</DeviceID>
+<AlarmPriority>4</AlarmPriority>
+<AlarmTime>2009-12-04T16:23:32</AlarmTime>
+<AlarmMethod>2</AlarmMethod>
+</Notify>
+```
+
+- b) **SIP/2.0 200 OK**  
+Via: SIP/2.0/UDP source domain name or IP address  
+From: <sip: source code@source domain name>; tag=e40807c0  
+To: <sip: CCS code@CCS domain name>; tag=852843529  
+Call-ID: a84b4c76e66710  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+- c) **MESSAGE sip: source code@source domain name or IP address port SIP/2.0**  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=852843529  
+To: <sip: source code@source domain name>  
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+CSeq: 2 MESSAGE  
+Max-Forwards: 70  
+Content-Type: Application/ECCS+xml  
+Content-Length: Byte length of message body  
+<?xml version="1.0"?>  
+<Response>  
+<CmdType>Alarm</CmdType>  
+<SN>1</SN>  
+<DeviceID>008611010000001340000101</DeviceID>  
+<Result>OK</Result>  
+</Response>
+- d) **SIP/2.0 200 OK**  
+To: <sip: source code@source domain name>; tag=e40807c0  
+Content-Length: 0  
+CSeq: 2 MESSAGE  
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=852843529
+- e) **MESSAGE sip: target code@target domain name or IP address port SIP/2.0**  
+To: <sip: target code@target domain name>  
+Content-Length: Byte length of message body  
+CSeq: 2 MESSAGE  
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=e40807c0  
+Content-Type: Application/ECCS+xml  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Notify>  
+<CmdType>Alarm</CmdType>  
+<SN>1</SN>  
+<DeviceID>008611010000001340000101</DeviceID>  
+<AlarmPriority>4</AlarmPriority>  
+<AlarmTime>2009-12-04T16:23:32</AlarmTime>  
+<AlarmMethod>2</AlarmMethod>  
+</Notify>
+- f) **SIP/2.0 200 OK**  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=e40807c0  
+To: <sip: Target code@target domain name>; tag=852843529  
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+
+- g) MESSAGE sip: CCS code @ CCS domain name or IP address port SIP/2.0  
+ Via: SIP/2.0/UDP target domain name or IP address  
+ From: <sip: Target code@target domain name>; tag=852843529  
+ To: <sip: CCS code@CCS domain name>  
+ Call-ID: de432gtf51u870  
+ CSeq: 2 MESSAGE  
+ Max-Forwards: 70  
+ Content-Type: Application/ECCS+xml  
+ Content-Length: Byte length of message body  
+ <?xml version="1.0"?>  
+ <Response>  
+ <CmdType>Alarm</CmdType>  
+ <SN>1</SN>  
+ <DeviceID>008611010000001340000101</DeviceID>  
+ <Result>OK</Result>  
+ </Response>
+- h) SIP/2.0 200 OK  
+ To: <sip: CCS code@CCS domain name>; tag=e40807c0  
+ Content-Length: 0  
+ CSeq: 2 MESSAGE  
+ Call-ID: de432gtf51u870  
+ Via: SIP/2.0/UDP target domain name or IP address  
+ From: <sip: Target code@target domain name>; tag=852843529
+
+## 8.5 Device information query
+
+### 8.5.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 device directory query command, PU information query command, PU status information query command, device configuration query command, preset position query command, PTZ precise status query command, OSD information query command, guard position information query command, cruise track list query command and cruise track query command. The information query scope includes the local VSS or the other VSS. The device information query and response are both achieved by the MESSAGE method specified in [IETF RFC 3428]. The directory query response commands shall comply with the provisions of multiple response message transmission in clause 7.5.
+
+The sources include a CU, CPG or the other CCS with SRG, and the targets include a PU, CPG, MS or the other CCS with SRG.
+
+### 8.5.2 Signalling process
+
+For the device information query signalling flow, see Figure 8-9.
+
+![Sequence diagram showing the signalling flow of device information query between Source, CCS, and Target. The flow consists of 8 steps: 1. Source to CCS: Message (Device information query command); 2. CCS to Source: 200 OK; 3. CCS to Target: Message (Device information query command); 4. Target to CCS: 200 OK; 5. Target to CCS: Message (Device information query response command); 6. CCS to Target: 200 OK; 7. CCS to Source: Message (Device information query response command); 8. Source to CCS: 200 OK. The diagram is labeled H.627(20)_F8-9.](701bc79e78b382bcfd3ba85597dbb9c3_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Source
+    participant CCS
+    participant Target
+    Note right of Target: H.627(20)_F8-9
+    Source->>CCS: 1: Message (Device information query command)
+    CCS-->>Source: 2: 200 OK
+    CCS->>Target: 3: Message (Device information query command)
+    Target-->>CCS: 4: 200 OK
+    Target->>CCS: 5: Message (Device information query response command)
+    CCS-->>Target: 6: 200 OK
+    CCS->>Source: 7: Message (Device information query response command)
+    Source-->>CCS: 8: 200 OK
+  
+```
+
+Sequence diagram showing the signalling flow of device information query between Source, CCS, and Target. The flow consists of 8 steps: 1. Source to CCS: Message (Device information query command); 2. CCS to Source: 200 OK; 3. CCS to Target: Message (Device information query command); 4. Target to CCS: 200 OK; 5. Target to CCS: Message (Device information query response command); 6. CCS to Target: 200 OK; 7. CCS to Source: Message (Device information query response command); 8. Source to CCS: 200 OK. The diagram is labeled H.627(20)\_F8-9.
+
+**Figure 8-9 – Signalling flow of device information query**
+
+The signalling flow description is as follows.
+
+- The source sends the device information query commands to the CCS, and the device information query commands are carried in the message body by the MESSAGE method.
+- The CCS replies with a 200 OK response after receiving the commands.
+- The CCS 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 CCS, and the device information query response commands are carried in the message body by the MESSAGE method.
+- The CCS replies with a 200 OK response after receiving the commands.
+- The CCS 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.3 Protocol interface
+
+#### 8.5.3.1 Device directory query message body
+
+##### a Request command message body
+
+The Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+Device directory query commands are specified in the ECCS. For a detailed description, see the device directory information query requests of query command in clause A.2.4 b).
+
+The device directory query request commands shall include command type (CmdType), command serial number (SN) and device/administrative zone/VSS ID (DeviceID), and are carried in the message body by the MESSAGE method.
+
+When enquiring according to the VSS ID, the enquired VSS replies with the VSS ID, administrative zone and device directory items of the VSS and the subordinate VSS. When enquiring according to the administrative zone, responses include the directory items of the administrative zone, as well as
+
+the administrative zone and device directory items under the jurisdiction of the administrative zone. When enquiring according to the device ID, responses include the directory items of the device and the device directory items subordinated to the device.
+
+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 Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+Device directory query response commands are specified in the ECCS. For a detailed description, see the device directory information query responses of response command in clause A.2.6 c).
+
+The device directory query response commands shall include command type (CmdType), command serial number (SN), device/administrative zone/VSS ID (DeviceID), device/administrative zone/VSS name (Name), device status (Status), longitude (Longitude) and latitude (Latitude), 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.
+
+See the examples of device catalogue query messages in clause 8.5.4.1.
+
+#### **8.5.3.2 Device information query message body**
+
+##### **a Request command message body**
+
+The Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+Device information query commands are specified in the ECCS. For a detailed description, see the device information query requests of query command in clause A.2.4 c).
+
+The device information query request commands shall include command type (CmdType), command serial number (SN) and device code (DeviceID), 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 Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+Device information query response commands are specified in the ECCS. For a detailed description, see the device information query responses of response command in clause A.2.6 d).
+
+The device information query response commands shall include command type (CmdType), device code (DeviceID), device name (DeviceName), query result markup (Result), manufacturer information (Manufacturer), device model (Model) and firmware version (Firmware), and 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.
+
+See the examples of device information query messages in clause 8.5.4.2.
+
+#### **8.5.3.3 Device status query message body**
+
+##### **a Request command message body**
+
+The Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+Device status query commands are specified in the ECCS. For a detailed description, see the device status query requests of query command in clause A.2.4 a).
+
+The device status query request commands shall include command type (CmdType), command serial number (SN) and device/administrative zone/VSS ID (DeviceID), 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 Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+Device information query response commands are specified in the ECCS. For a detailed description, see the device status information query responses of response command in clause A.2.6 g).
+
+The device status query response commands shall include target device/administrative zone/VSS ID (DeviceID), command type (CmdType), query result markup (Result), online or not (Online), normal operation or not (Status), abnormality reason (Reason), encode or not (Encode), record or not (Record), device time and date (DeviceTime), alarm device status list (Alarmstatus), etc., and the alarm device status list shall include alarm device/administrative zone/VSS ID (DeviceID) and alarm device status (DutyStatus), 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.
+
+See the examples of device status query messages in clause 8.5.4.3.
+
+#### **8.5.3.4 Device configuration query message body**
+
+##### **a Request command message body**
+
+The Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+Device configuration query request commands are specified in the ECCS. The device configuration query request commands shall include command type (CmdType), command serial number (SN), device code (DeviceID) and query configuration parameter type (ConfigType), and are carried in the message body by the MESSAGE method. For a detailed description, see the device configuration query requests of query command in clause A.2.4 f).
+
+##### **b Response command message body**
+
+The Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+The device configuration query response commands shall include command type (CmdType), command serial number (SN), device code (DeviceID), query result (Result) and configuration parameters, and are carried in the message body by the MESSAGE method. For a detailed description, see the device configuration query responses of response command in clause A.2.6 j).
+
+See the examples of device configuration query messages in clause 8.5.4.4.
+
+#### **8.5.3.5 Device preset position query message body**
+
+##### **a Request command message body**
+
+The Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+Device preset position query commands are specified in the ECCS. For a detailed description, see the preset position query requests of query command in clause A.2.4 g).
+
+The device preset position query request commands shall include command type (CmdType), command serial number (SN) and device code (DeviceID), and are carried in the message body by the MESSAGE method [IETF RFC 3428].
+
+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 Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+Device preset position query response commands are specified in the ECCS. For a detailed description, see the preset position query responses of response command in clause A.2.6 k).
+
+The device preset position query response commands shall include device ID (DeviceID), command type (CmdType), command serial number (SN), device preset position result total number (SumNum) and device preset position list (PresetList), and the device preset position list shall include preset position identification (PresetID) and preset position name (PresetName), which 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.
+
+See the examples of device preset position query messages in clause 8.5.4.5.
+
+#### **8.5.3.6 Guard position information query message body**
+
+##### **a Request command message body**
+
+The Content-type header field of the MESSAGE header is Content-type: Application/ ECCS + xml.
+
+Guard position information query commands are specified in the ECCS, for a detailed description, see the guard position information query requests in clause A.2.4 i).
+
+The guard position query request commands shall include command type (CmdType), command serial number (SN) and device ID (DeviceID), 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 Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+Guard position information query response commands are specified in the ECCS; for a detailed description, see the guard position information query responses in clause A.2.6 m).
+
+The guard position information query response commands shall include command type (CmdType), command serial number (SN), device ID (DeviceID), guard position configuration information (HomePosition), the guard position configuration information shall include the guard position enable (Enabled), the automatic homing time interval (ResetTime), the preset position number (PresetIndex), and are carried in the message body with 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.
+
+See the examples of guard position information query messages in clause 8.5.4.6.
+
+#### **8.5.3.7 Cruise track list query message body**
+
+##### **a Request command message body**
+
+The Content-type header field of the MESSAGE header is Content-type: Application/ECCS+ xml.
+
+Cruise track list query commands are specified in the ECCS, for a detailed description, see the cruise track list query requests in clause A.2.4 j).
+
+The cruise track list query request commands shall include command type (CmdType), command serial number (SN) and device ID (DeviceID), 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 Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+Cruise track list query response commands are specified in the ECCS, for a detailed description, see the cruise track list information query responses in clause A.2.6 n).
+
+The cruise track list query response commands shall include command type (CmdType), command serial number (SN), device ID (DeviceID), cruise track list (CruiseTrackList), the cruise track (CruiseTrack) shall include the track number (Number), the track name (Name), 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.
+
+See the examples of cruise track list query messages in clause 8.5.4.7.
+
+#### **8.5.3.8 Cruise track query message body**
+
+##### **a Request command message body**
+
+The Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+Cruise track query commands are specified in the ECCS; for a detailed description, see the cruise track query requests in clause A.2.4 k).
+
+The cruise track query request commands shall include command type (CmdType), command serial number (SN), device ID (DeviceID) and track number (Number), 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 Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+Cruise track query response commands are specified in the ECCS, for a detailed description, see the cruise track information query responses in clause A.2.6 o).
+
+The cruise track query response commands shall include command type (CmdType), command serial number (SN), device ID (DeviceID), track number (Number), track name (Name), track point list (CruisePointList), the track point information (CruisePoint) shall include preset index (PresetIndex), preset point stay time (StayTime), PTZ speed (Speed), 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.
+
+See the examples of cruise track query messages in clause 8.5.4.8.
+
+#### **8.5.3.9 PTZ precise status query message body**
+
+##### **a Request command message body**
+
+The Content-type header field of the MESSAGE header is Content-type: Application/ECCS+ xml.
+
+PTZ precise status query commands are specified in the ECCS, for a detailed description, see the PTZ precise status query requests in clause A.2.4, l).
+
+The PTZ precise status query request commands shall include command type (CmdType), command serial number (SN) and device ID (DeviceID), 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 Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+PTZ precise status query response commands are specified in the ECCS, for a detailed description, see the PTZ precise status query responses in clause A.2.6, p).
+
+The PTZ precise status query response commands shall include command type (CmdType), command serial number (SN), device ID (DeviceID), horizontal angle (Pan), vertical angle (Tilt), zoom factor (Zoom), 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.
+
+See the examples of PTZ precise status query messages in clause 8.5.4.9.
+
+#### **8.5.3.10 OSD information query message body**
+
+##### **a Request command message body**
+
+The Content-type header field of the MESSAGE header is Content-type: Application/ECCS+ xml.
+
+OSD information query commands are specified in the ECCS, for a detailed description, see the OSD information query requests in clause A.2.4 m).
+
+The OSD information query request commands shall include command type (CmdType), command serial number (SN) and device ID (DeviceID), 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 Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+OSD information query response commands are specified in the ECCS; for a detailed description, see the OSD information query responses in clause A.2.6 q).
+
+The OSD information query response commands shall include command type (CmdType), command serial number (SN), device ID (DeviceID), it should include window length pixel value (Length), window width pixel value (Width), timestamp-X coordinate (TimeX), timestamp-Y coordinate (TimeY), time-display switch (TimeEnable), time-display type (TimeType), text list (Item), 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.
+
+See the examples of OSD information query messages in clause 8.5.4.10.
+
+### 8.5.4 Examples of messages
+
+#### 8.5.4.1 Examples of device catalogue query messages
+
+- a) MESSAGE sip: target code@target domain name or IP address port SIP/2.0  
+To: <sip: target code@target domain name>  
+Content-Length: Byte length of message body  
+CSeq: 2 MESSAGE  
+Call-ID: a84b4c76e66710  
+Via: SIP/2.0/UDP source domain name or IP address  
+From: <sip: source code@source domain name>; tag=e40807c0  
+Content-Type: Application/ECCS+xml  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Query>  
+<CmdType>Catalog</CmdType>  
+<SN>17430</SN>  
+<DeviceID>008611010000001110000001</DeviceID>  
+</Query>
+- b) SIP/2.0 200 OK  
+Via: SIP/2.0/UDP source domain name or IP address  
+From: <sip: source code@source domain name>; tag=e40807c0  
+To: <sip: Target code@target domain name>; tag=852843529  
+Call-ID: a84b4c76e66710  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+- c) MESSAGE sip: target code@target domain name or IP address port SIP/2.0  
+To: <sip: target code@target domain name>  
+Content-Length: Byte length of message body  
+CSeq: 2 MESSAGE  
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: source code@source domain name>; tag=e40807c0  
+Content-Type: Application/ECCS+xml  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Query>  
+<CmdType> Catalog </CmdType>  
+<SN>17430</SN>  
+<DeviceID>008611010000001110000001</DeviceID>  
+</Query>
+- d) SIP/2.0 200 OK  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: source code@source domain name>; tag=e40807c0  
+To: <sip: Target code@target domain name>; tag=852843529  
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+- e) MESSAGE sip: source code@source domain name or IP address port SIP/2.0  
+Via: SIP/2.0/UDP target domain name or IP address  
+From: <sip: Target code@target domain name>; tag=852843529  
+To: <sip: source code@source domain name>  
+Call-ID: de432gtf5lu870  
+CSeq: 2 MESSAGE  
+Max-Forwards: 70  
+Content-Type: Application/ECCS+xml  
+Content-Length: Byte length of message body
+
+```
+
+<?xml version="1.0"?>
+  <Response>
+    <CmdType> Catalog </CmdType>
+    <SN>17430</SN>
+    <DeviceID>008611010000001110000001</DeviceID>
+    <SumNum>100</SumNum>
+    <DeviceList Num="2">
+      <Item>
+        <DeviceID>008611010000001330000001</DeviceID>
+        <Name>Camera1</Name>
+        <Manufacturer>Manufacturer </Manufacturer>
+        <Model> Model 1 </Model>
+        <Owner> Owner 1 </Owner>
+        <ZoneCode>ZoneCode 1</ZoneCode>
+        <Block>Block 1</Block>
+        <Address> Address 1 </Address>
+        <Parental> 1 </Parental>
+        <ParentID>008611010000001110000001</ParentID>
+        <IPAddress>192.168.3.81</IPAddress>
+        <Port>5060</Port>
+        <Password> Password 1</Password>
+        <Status>Status 1</Status>
+        <Longitude> 171.3</Longitude>
+        <Latitude> 34.2 </Latitude>
+      </Item>
+      <Item>
+        <DeviceID>008611010000001330000002</DeviceID>
+        <Name> Camera2 </Name>
+        <Manufacturer> Manufacturer 2 </Manufacturer>
+        <Model> Model 2 </Model>
+        <Owner> Owner 2 </Owner>
+        <ZoneCode> ZoneCode 2 </ZoneCode>
+        <Block> Block2 </Block>
+        <Address> Address2 </Address>
+        <Parental> 1 </Parental>
+        <ParentID>008611010000001110000001 </ParentID>
+        <IPAddress> 192.168.3.81 </IPAddress>
+        <Port> 5060 </Port>
+        <Password> Password 1 </Password>
+        <Status> Status 1 </Status>
+        <Longitude> 171.4</Longitude>
+        <Latitude> 34.2 </Latitude>
+      </Item>
+    </DeviceList>
+  </Response>
+
+```
+
+##### **f) SIP/2.0 200 OK**
+
+```
+
+To: <sip: source code@source domain name>; tag=e40807c0
+Content-Length: 0
+CSeq: 2 MESSAGE
+Call-ID: de432gtf51u870
+Via: SIP/2.0/UDP target domain name or IP address
+From: <sip: Target code@target domain name>; tag=852843529
+
+```
+
+##### **g) MESSAGE sip: source code@source domain name or IP address port SIP/2.0**
+
+```
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: Target code@target domain name>; tag=852843529
+To: <sip: source code@source domain name>
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+CSeq: 2 MESSAGE
+Max-Forwards: 70
+Content-Type: Application/ECCS+xml
+
+```
+
+```
+
+Content-Length: Byte length of message body
+<?xml version="1.0"?>
+<Response>
+  <CmdType> Catalog </CmdType>
+  <SN>17430</SN>
+  <DeviceID>008611010000001110000001</DeviceID>
+  <SumNum>100</SumNum>
+  <DeviceList Num="2">
+    <Item>
+      <DeviceID>008611010000001330000001</DeviceID>
+      <Name> Camera1 </Name>
+      <Manufacturer> Manufacturer 1 </Manufacturer>
+      <Model> Model 1 </Model>
+      <Owner> Owner 1 </Owner>
+      <ZoneCode> ZoneCode 1 </ZoneCode>
+      <Block> Block 1 </Block>
+      <Address> Address 1 </Address>
+      <Parental> 1 </Parental>
+      <ParentID>008611010000001110000001 </ParentID>
+      <IPAddress> 192.168.3.81 </IPAddress>
+      <Port> 5060 </Port>
+      <Password> Password 1 </Password>
+      <Status> Status 1 </Status>
+      <Longitude> 171.3</Longitude>
+      <Latitude> 34.2 </Latitude>
+    </Item>
+    <Item>
+      <DeviceID>008611010000001330000002</DeviceID>
+      <Name> Camera2 </Name>
+      <Manufacturer> Manufacturer 2 </Manufacturer>
+      <Model> Model 2 </Model>
+      <Owner> Owner 2 </Owner>
+      <ZoneCode> ZoneCode 2 </ZoneCode>
+      <Block> Block2 </Block>
+      <Address> Address2 </Address>
+      <Parental> 1 </Parental>
+      <ParentID>008611010000001110000001 </ParentID>
+      <IPAddress> 192.168.3.81 </IPAddress>
+      <Port> 5060 </Port>
+      <Password> Password 1 </Password>
+      <Status> Status 1 </Status>
+      <Longitude> 171.4</Longitude>
+      <Latitude> 34.2 </Latitude>
+    </Item>
+  </DeviceList>
+</Response>
+
+```
+
+##### **h) SIP/2.0 200 OK**
+
+```
+
+To: <sip: source code@source domain name>; tag=e40807c0
+Content-Length: 0
+CSeq: 2 MESSAGE
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: Target code@target domain name>; tag=852843529
+
+```
+
+#### **8.5.4.2 Examples of device information query messages**
+
+##### **a) MESSAGE sip: target code@target domain name or IP address port SIP/2.0**
+
+```
+
+To: <sip: target code@target domain name>
+Content-Length: Byte length of message body
+CSeq: 2 MESSAGE
+Call-ID: a84b4c76e66710
+
+```
+
+Via: SIP/2.0/UDP source domain name or IP address  
+From: <sip: source code@source domain name>; tag=e40807c0  
+Content-Type: Application/ECCS+xml  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Query>  
+<CmdType>DeviceInfo</CmdType>  
+<SN>17430</SN>  
+<DeviceID>00861101000000011100000001</DeviceID>  
+</Query>
+
+##### b) **SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP source domain name or IP address  
+From: <sip: source code@source domain name>; tag=e40807c0  
+To: <sip: Target code@target domain name>; tag=852843529  
+Call-ID: a84b4c76e66710  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+
+##### c) **MESSAGE sip: target code@target domain name or IP address port SIP/2.0**
+
+To: <sip: target code@target domain name>  
+Content-Length: Byte length of message body  
+CSeq: 2 MESSAGE  
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: source code@source domain name>; tag=e40807c0  
+Content-Type: Application/ECCS+xml  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Query>  
+<CmdType>DeviceInfo</CmdType>  
+<SN>17430</SN>  
+<DeviceID>00861101000000011100000001</DeviceID>  
+</Query>
+
+##### d) **SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: source code@source domain name>; tag=e40807c0  
+To: <sip: Target code@target domain name>; tag=852843529  
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+
+##### e) **MESSAGE sip: source code @source domain name or IP address port SIP/2.0**
+
+Via: SIP/2.0/UDP target domain name or IP address  
+From: <sip: Target code@target domain name>; tag=852843529  
+To: <sip: source code@source domain name>  
+Call-ID: de432gtf51u870  
+CSeq: 2 MESSAGE  
+Max-Forwards: 70  
+Content-Type: Application/ECCS+xml  
+Content-Length: Byte length of message body  
+<?xml version="1.0"?>  
+<Response>  
+<CmdType>DeviceInfo</CmdType>  
+<SN>17430</SN>  
+<DeviceID>00861101000000011100000001</DeviceID>  
+<Result>OK</Result>  
+<Manufacturer>Tiandy</Manufacturer>  
+<Model>TC-2808AN-HD</Model>  
+<Firmware>V2.1, build 091111</Firmware>
+
+</Response>
+
+##### **f) SIP/2.0 200 OK**
+
+To: <sip: source code@source domain name>; tag=e40807c0  
+Content-Length: 0  
+CSeq: 2 MESSAGE  
+Call-ID: de432gtf51u870  
+Via: SIP/2.0/UDP target domain name or IP address  
+From: <sip: Target code@target domain name>; tag=852843529
+
+##### **g) MESSAGE sip: source code @source domain name or IP address port SIP/2.0**
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: Target code@target domain name>; tag=852843529  
+To: <sip: source code@source domain name>  
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+CSeq: 2 MESSAGE  
+Max-Forwards: 70  
+Content-Type: Application/ECCS+xml  
+Content-Length: Byte length of message body  
+<?xml version="1.0"?>  
+<Response>  
+<CmdType>DeviceInfo</CmdType>  
+<SN>17430</SN>  
+<DeviceID>0086110100000011100000001</DeviceID>  
+<Result>OK</Result>  
+<Manufacturer>Tiandy</Manufacturer>  
+<Model>TC-2808AN-HD</Model>  
+<Firmware>V2.1, build 091111</Firmware>  
+</Response>
+
+##### **h) SIP/2.0 200 OK**
+
+To: <sip: source code@source domain name>;tag=e40807c0  
+Content-Length: 0  
+CSeq: 2 MESSAGE  
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: Target code@target domain name>; tag=852843529
+
+#### **8.5.4.3 Examples of device status query messages**
+
+##### **a) MESSAGE sip: target code@target domain name or IP address port SIP/2.0**
+
+To: <sip: target code@target domain name>  
+Content-Length: Byte length of message body  
+CSeq: 2 MESSAGE  
+Call-ID: a84b4c76e66710  
+Via: SIP/2.0/UDP source domain name or IP address  
+From: <sip: source code@source domain name>;tag=e40807c0  
+Content-Type: Application/ECCS+xml  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Query>  
+<CmdType>DeviceStatus</CmdType>  
+<SN>248</SN>  
+<DeviceID>0086340200000011100000001</DeviceID>  
+</Query>
+
+##### **b) SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP source domain name or IP address  
+From: <sip: source code@source domain name>; tag=e40807c0  
+To: <sip: Target code@target domain name>; tag=852843529
+
+Call-ID: a84b4c76e66710  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+
+##### c) MESSAGE sip: target code@target domain name or IP address port SIP/2.0
+
+To: <sip: target code@target domain name>  
+Content-Length: Byte length of message body  
+CSeq: 2 MESSAGE  
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: source code@source domain name>; tag=e40807c0  
+Content-Type: Application/ECCS+xml  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Query>  
+<CmdType>DeviceStatus</CmdType>  
+<SN>248</SN>  
+<DeviceID>008634020000001110000001</DeviceID>  
+</Query>
+
+##### d) SIP/2.0 200 OK
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: source code@source domain name>; tag=e40807c0  
+To: <sip: Target code@target domain name>; tag=852843529  
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+
+##### e) MESSAGE sip: source code @source domain name or IP address port SIP/2.0
+
+Via: SIP/2.0/UDP target domain name or IP address  
+From: <sip: Target code@target domain name>; tag=852843529  
+To: <sip: source code@source domain name>  
+Call-ID: de432gtf51u870  
+CSeq: 2 MESSAGE  
+Max-Forwards: 70  
+Content-Type: Application/ECCS+xml  
+Content-Length: Byte length of message body  
+<?xml version="1.0"?>  
+<Response>  
+<CmdType>DeviceStatus</CmdType>  
+<SN>248</SN>  
+<DeviceID>008634020000001130000001</DeviceID>  
+<Result>OK</Result>  
+<Online>ONLINE</Online>  
+<Status>OK</Status>  
+<Encode>ON</Encode>  
+<Record>OFF</Record>  
+<DeviceTime>2010-11-11T19:46:17</DeviceTime>  
+<Alarmstatus Num="2">  
+<Item>  
+<DeviceID>008634020000001340000001</DeviceID>  
+<DutyStatus>OFFDUTY</DutyStatus>  
+</Item>  
+<Item>  
+<DeviceID>008634020000001340000002</DeviceID>  
+<DutyStatus>OFFDUTY</DutyStatus>  
+</Item>  
+</Alarmstatus>  
+</Response>
+
+##### f) SIP/2.0 200 OK
+
+```
+
+To: <sip: source code@source domain name>; tag=e40807c0
+Content-Length: 0
+CSeq: 2 MESSAGE
+Call-ID: de432gtf51u870
+Via: SIP/2.0/UDP target domain name or IP address
+From: <sip: Target code@target domain name>; tag=852843529
+
+```
+
+##### **g) MESSAGE sip: source code @source domain name or IP address port SIP/2.0**
+
+```
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: Target code@target domain name>; tag=852843529
+To: <sip: source code@source domain name>
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+CSeq: 2 MESSAGE
+Max-Forwards: 70
+Content-Type: Application/ECCS+xml
+Content-Length: Byte length of message body
+<?xml version="1.0"?>
+<Response>
+  <CmdType>DeviceStatus</CmdType>
+  <SN>248</SN>
+  <DeviceID>008634020000001130000001</DeviceID>
+  <Result>OK</Result>
+  <Online>ONLINE</Online>
+  <Status>OK</Status>
+  <Encode>ON</Encode>
+  <Record>OFF</Record>
+  <DeviceTime>2010-11-11T19:46:17</DeviceTime>
+  <Alarmstatus Num="2">
+    <Item>
+      <DeviceID>008634020000001340000001</DeviceID>
+      <DutyStatus>OFFDUTY</DutyStatus>
+    </Item>
+    <Item>
+      <DeviceID>008634020000001340000002</DeviceID>
+      <DutyStatus>OFFDUTY</DutyStatus>
+    </Item>
+  </Alarmstatus>
+</Response>
+
+```
+
+##### **h) SIP/2.0 200 OK**
+
+```
+
+To: <sip: source code@source domain name>; tag=e40807c0
+Content-Length: 0
+CSeq: 2 MESSAGE
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: Target code@target domain name>; tag=852843529
+
+```
+
+#### **8.5.4.4 Examples of device configuration query messages**
+
+##### **a) MESSAGE sip: target code@target domain name or IP address port SIP/2.0**
+
+```
+
+To: <sip: target code@target domain name>
+Content-Length: Byte length of message body
+CSeq: 2 MESSAGE
+Call-ID: a84b4c76e66710
+Via: SIP/2.0/UDP source domain name or IP address
+From: <sip: source code@source domain name>; tag=e40807c0
+Content-Type: Application/ECCS+xml
+Max-Forwards: 70
+<?xml version="1.0"?>
+<Query>
+  <CmdType>ConfigDownload</CmdType>
+  <SN>17430</SN>
+  <DeviceID>00861101000000011100000001</DeviceID>
+
+```
+
+```
+<ConfigType>BasicParam</ConfigType>
+</Query>
+```
+
+##### **b) SIP/2.0 200 OK**
+
+```
+Via: SIP/2.0/UDP source domain name or IP address
+From: <sip: source code@source domain name>; tag=e40807c0
+To: <sip: Target code@target domain name>; tag=852843529
+Call-ID: a84b4c76e66710
+CSeq: 2 MESSAGE
+Content-Length: 0
+```
+
+##### **c) MESSAGE sip: target code@target domain name or IP address port SIP/2.0**
+
+```
+To: <sip: target code@target domain name>
+Content-Length: Byte length of message body
+CSeq: 2 MESSAGE
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: source code@source domain name>; tag=e40807c0
+Content-Type: Application/ECCS+xml
+Max-Forwards: 70
+<?xml version="1.0"?>
+<Query>
+<CmdType>ConfigDownload</CmdType>
+<SN>17430</SN>
+<DeviceID>008611010000001110000001</DeviceID>
+<ConfigType>BasicParam</ConfigType>
+</Query>
+```
+
+##### **d) SIP/2.0 200 OK**
+
+```
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: source code@source domain name>; tag=e40807c0
+To: <sip: Target code@target domain name>; tag=852843529
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+CSeq: 2 MESSAGE
+Content-Length: 0
+```
+
+##### **e) MESSAGE sip: source code @source domain name or IP address port SIP/2.0**
+
+```
+Via: SIP/2.0/UDP target domain name or IP address
+From: <sip: Target code@target domain name>; tag=852843529
+To: <sip: source code@source domain name>
+Call-ID: de432gtf5lu870
+CSeq: 2 MESSAGE
+Max-Forwards: 70
+Content-Type: Application/ECCS+xml
+Content-Length: Byte length of message body
+<?xml version="1.0"?>
+<Response>
+<CmdType>ConfigDownload</CmdType>
+<SN>17430</SN>
+<DeviceID>008611010000001110000001</DeviceID>
+<Result>OK</Result>
+<BasicParam>
+<Name>Device1</Name>
+<Expiration>86400</Expiration>
+<HeartBeatInterval>60</HeartBeatInterval>
+<HeartBeatCount>3</HeartBeatCount>
+<PositionCapability>2</PositionCapability>
+<Longitude>110.20</Longitude>
+<Latitude>90.00</Latitude>
+</BasicParam>
+</Response>
+```
+
+- f) **SIP/2.0 200 OK**  
+ To: <sip: source code@source domain name>; tag=e40807c0  
+ Content-Length: 0  
+ CSeq: 2 MESSAGE  
+ Call-ID: de432gtf51u870  
+ Via: SIP/2.0/UDP target domain name or IP address  
+ From: <sip: Target code@target domain name>; tag=852843529
+- g) **MESSAGE sip: source code @source domain name or IP address port SIP/2.0**  
+ Via: SIP/2.0/UDP CCS domain name or IP address  
+ From: <sip: Target code@target domain name>; tag=852843529  
+ To: <sip: source code@source domain name>  
+ Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+ CSeq: 2 MESSAGE  
+ Max-Forwards: 70  
+ Content-Type: Application/ECCS+xml  
+ Content-Length: Byte length of message body  
+ <?xml version="1.0"?>  
+ <Response>  
+ <CmdType>ConfigDownload</CmdType>  
+ <SN>17430</SN>  
+ <DeviceID>008611010000001110000001</DeviceID>  
+ <Result>OK</Result>  
+ <BasicParam>  
+ <Name>Device1</Name>  
+ <Expiration>86400</Expiration>  
+ <HeartBeatInterval>60</HeartBeatInterval>  
+ <HeartBeatCount>3</HeartBeatCount>  
+ <PositionCapability>2</PositionCapability>  
+ <Longitude>110.20</Longitude>  
+ <Latitude>90.00</Latitude>  
+ </BasicParam>  
+ </Response>
+- h) **SIP/2.0 200 OK**  
+ To: <sip: source code@source domain name>;tag=e40807c0  
+ Content-Length: 0  
+ CSeq: 2 MESSAGE  
+ Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+ Via: SIP/2.0/UDP CCS domain name or IP address  
+ From: <sip: Target code@target domain name>; tag=852843529
+
+#### 8.5.4.5 Examples of device preset position query messages
+
+- a) **MESSAGE sip: target code@target domain name or IP address port SIP/2.0**  
+ To: <sip: target code@target domain name>  
+ Content-Length: Byte length of message body  
+ CSeq: 2 MESSAGE  
+ Call-ID: a84b4c76e66710  
+ Via: SIP/2.0/UDP source domain name or IP address  
+ From: <sip: source code@source domain name>; tag=e40807c0  
+ Content-Type: Application/ECCS+xml  
+ Max-Forwards: 70  
+ <?xml version="1.0"?>  
+ <Query>  
+ <CmdType>PresetQuery</CmdType>  
+ <SN>123</SN>  
+ <DeviceID>008634020000001310000001</DeviceID>  
+ </Query>
+
+- b) **SIP/2.0 200 OK**  
+Via: SIP/2.0/UDP source domain name or IP address  
+From: <sip: source code@source domain name>;tag=e40807c0  
+To: <sip: Target code@target domain name>;tag=852843529  
+Call-ID: a84b4c76e66710  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+- c) **MESSAGE sip: target code@target domain name or IP address port SIP/2.0**  
+To: <sip: target code@target domain name>  
+Content-Length: Byte length of message body  
+CSeq: 2 MESSAGE  
+Call-ID: a84b4c76e66543  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: source code@source domain name>; tag=e40807c0  
+Content-Type: Application/ECCS+xml  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Query>  
+<CmdType>PresetQuery</CmdType>  
+<SN>123</SN>  
+<DeviceID>0086340200000013100000001</DeviceID>  
+</Query>
+- d) **SIP/2.0 200 OK**  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: source code@source domain name>;tag=e4080457  
+To: <sip: Target code@target domain name>;tag=852843630  
+Call-ID: a84b4c76e66543  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+- e) **MESSAGE sip: source code@source domain name or IP address port SIP/2.0**  
+To: <source code@source domain name>  
+Content-Length: Byte length of message body  
+CSeq: 2 MESSAGE  
+Call-ID: a84b4c76e66543  
+Via: SIP/2.0/UDP target domain name or IP address  
+From: <sip:Target code@target domain name>;tag=e4080457  
+Content-Type: Application/ECCS+xml  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Response>  
+<CmdType>PresetQuery</CmdType>  
+<SN>123</SN>  
+<SumNum>1</SumNum>  
+<DeviceID>0086340200000013100000001</DeviceID>  
+<PresetList Num="1">  
+<Item>  
+<PresetID>1</DeviceID>  
+<PresetName> PresetName1 </PresetName>  
+</Item>  
+</PresetList>  
+</Response>
+- f) **SIP/2.0 200 OK**  
+Via: SIP/2.0/UDP target domain name or IP address  
+From: <sip:Target code@target domain name>;tag=e4080457  
+To: <sip:source code@source domain name>;tag=852843630  
+Call-ID: a84b4c76e66543  
+CSeq: 2 MESSAGE
+
+Content-Length: 0
+
+- g) MESSAGE sip:source code@source domain name or IP address port SIP/2.0  
+To: <sip:source code@source domain name>  
+Content-Length: Byte length of message body  
+CSeq: 2 MESSAGE  
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip:Target code@target domain name>;tag=e4080458  
+Content-Type: Application/ECCS+xml  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Response>  
+<CmdType>PresetQuery</CmdType>  
+<SN>123</SN>  
+<SumNum>1</SumNum>  
+<DeviceID>0086340200000013100000001</DeviceID>  
+<PresetList Num="1">  
+<Item>  
+<PresetID>1</DeviceID>  
+<PresetName> PresetName1 </PresetName>  
+</Item>  
+</PresetList>  
+</Response>
+- h) SIP/2.0 200 OK  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip:Target code@target domain name>;tag=e4080458  
+To: <sip:source code@source domain name>;tag=8528436309  
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+
+#### 8.5.4.6 Examples of guard position information query messages
+
+- a) MESSAGE sip: target code@target domain name or IP address port SIP/2.0  
+To: <sip: target code@target domain name>  
+Content-Length: Byte length of message body  
+CSeq: 2 MESSAGE  
+Call-ID: a84b4c76e66710  
+Via: SIP/2.0/UDP source domain name or IP address  
+From: <sip: source code@source domain name>; tag=e40807c0  
+Content-Type: Application/ECCS+xml  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Query>  
+<CmdType>HomePositionQuery</CmdType>  
+<SN>123</SN>  
+<DeviceID>0086340200000013100000001</DeviceID>  
+</Query>
+- b) SIP/2.0 200 OK  
+Via: SIP/2.0/UDP source domain name or IP address  
+From: <sip: source code@source domain name>;tag=e40807c0  
+To: <sip: Target code@target domain name>;tag=852843529  
+Call-ID: a84b4c76e66710  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+- c) MESSAGE sip: target code@target domain name or IP address port SIP/2.0
+
+```
+
+To: <sip: target code@target domain name>
+Content-Length: Byte length of message body
+CSeq: 2 MESSAGE
+Call-ID: a84b4c76e66543
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: source code@source domain name>; tag=e40807c0
+Content-Type: Application/ECCS+xml
+Max-Forwards: 70
+<?xml version="1.0"?>
+<Query>
+<CmdType>HomePositionQuery</CmdType>
+<SN>123</SN>
+<DeviceID>008634020000001310000001</DeviceID>
+</Query>
+
+```
+
+##### **d) SIP/2.0 200 OK**
+
+```
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: source code@source domain name>;tag=e4080457
+To: <sip: Target code@target domain name>;tag=852843630
+Call-ID: a84b4c76e66543
+CSeq: 2 MESSAGE
+Content-Length: 0
+
+```
+
+##### **e) MESSAGE sip: source code@source domain name or IP address port SIP/2.0**
+
+```
+
+To: <source code@source domain name>
+Content-Length: Byte length of message body
+CSeq: 2 MESSAGE
+Call-ID: a84b4c76e66543
+Via: SIP/2.0/UDP target domain name or IP address
+From: <sip:Target code@target domain name>;tag=e4080457
+Content-Type: Application/ECCS+xml
+Max-Forwards: 70
+<?xml version="1.0"?>
+<Response>
+<CmdType>HomePositionQuery</CmdType>
+<SN>123</SN>
+<DeviceID>008634020000001310000001</DeviceID>
+<HomePosition>
+<Enabled>1</Enabled>
+<ResetTime>120</ResetTime>
+<PresetIndex>10</PresetIndex>
+</HomePosition>
+</Response>
+
+```
+
+##### **f) SIP/2.0 200 OK**
+
+```
+
+Via: SIP/2.0/UDP target domain name or IP address
+From: <sip:Target code@target domain name>;tag=e4080457
+To: <sip:source code@source domain name>;tag=852843630
+Call-ID: a84b4c76e66543
+CSeq: 2 MESSAGE
+Content-Length: 0
+
+```
+
+##### **g) MESSAGE sip:source code@source domain name or IP address port SIP/2.0**
+
+```
+
+To: <sip:source code@source domain name>
+Content-Length: Byte length of message body
+CSeq: 2 MESSAGE
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip:Target code@target domain name>;tag=e4080457
+Content-Type: Application/ECCS+xml
+Max-Forwards: 70
+
+```
+
+```
+
+<?xml version="1.0"?>
+<Response>
+<CmdType>HomePositionQuery</CmdType>
+<SN>123</SN>
+<DeviceID>0086340200000013100000001</DeviceID>
+<HomePosition>
+<Enabled>1</Enabled>
+<ResetTime>120</ResetTime>
+<PresetIndex>10</PresetIndex>
+</HomePosition>
+</Response>
+
+```
+
+##### **h) SIP/2.0 200 OK**
+
+```
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip:Target code@target domain name>;tag=e4080458
+To: <sip:source code@source domain name>;tag=8528436309
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+CSeq: 2 MESSAGE
+Content-Length: 0
+
+```
+
+#### **8.5.4.7 Examples of cruise track list query messages**
+
+##### **a) MESSAGE sip:Target code@target domain name or IP address port SIP/2.0**
+
+```
+
+To: <sip:Target code@target domain name>
+Content-Length: Byte length of message body
+CSeq: 2 MESSAGE
+Call-ID: a84b4c76e66710
+Via: SIP/2.0/UDP source domain name or IP address
+From: <sip:source code@source domain name>;tag=e40807c0
+Content-Type: Application/ECCS+xml
+Max-Forwards: 70
+<?xml version="1.0"?>
+<Query>
+<CmdType>CruiseTrackListQuery</CmdType>
+<SN>123</SN>
+<DeviceID>0086340200000013100000001</DeviceID>
+</Query>
+
+```
+
+##### **b) SIP/2.0 200 OK**
+
+```
+
+Via: SIP/2.0/UDP source domain name or IP address
+From: <sip:source code@source domain name>;tag=e40807c0
+To: <sip:Target code@target domain name>;tag=852843529
+Call-ID: a84b4c76e66710
+CSeq: 2 MESSAGE
+Content-Length: 0
+
+```
+
+##### **c) MESSAGE sip:Target code@target domain name or IP address port SIP/2.0**
+
+```
+
+To: <sip:Target code@target domain name>
+Content-Length: Byte length of message body
+CSeq: 2 MESSAGE
+Call-ID: a84b4c76e66543
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip:source code@source domain name>;tag=e4080457
+Content-Type: Application/ECCS+xml
+Max-Forwards: 70
+<?xml version="1.0"?>
+<Query>
+<CmdType>CruiseTrackListQuery</CmdType>
+<SN>123</SN>
+<DeviceID>0086340200000013100000001</DeviceID>
+</Query>
+
+```
+
+##### **d) SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip:source code@source domain name>;tag=e4080457  
+To: <sip:Target code@target domain name>;tag=852843630  
+Call-ID: a84b4c76e66543  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+
+##### **e) MESSAGE sip:source code@source domain name or IP address port SIP/2.0**
+
+To: <sip:source code@source domain name>  
+Content-Length: Byte length of message body  
+CSeq: 2 MESSAGE  
+Call-ID: a84b4c76e66543  
+Via: SIP/2.0/UDP target domain name or IP address  
+From: <sip:Target code@target domain name>;tag=e4080457  
+Content-Type: Application/ECCS+xml  
+Max-Forwards: Byte length of message body  
+<?xml version="1.0"?>  
+<Response>  
+<CmdType>CruiseTrackListQuery</CmdType>  
+<SN>123</SN>  
+<DeviceID>0086340200000013100000001</DeviceID>  
+<SumNum>2</SumNum>  
+<CruiseTrackList Num="2">  
+<CruiseTrack>  
+<Number>1</Number>  
+<Name>CRUISE TRACKE1</Name>  
+</CruiseTrack>  
+<CruiseTrack>  
+<Number>2</Number>  
+<Name>CRUISE TRACKE2</Name>  
+</CruiseTrack>  
+</CruiseTrackList>  
+</Response>
+
+##### **f) SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP target domain name or IP address  
+From: <sip:Target code@target domain name>;tag=e4080457  
+To: <sip:source code@source domain name>;tag=852843630  
+Call-ID: a84b4c76e66543  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+
+##### **g) MESSAGE sip:source code@source domain name or IP address port SIP/2.0**
+
+To: <sip:source code@source domain name>  
+Content-Length: Byte length of message body  
+CSeq: 2 MESSAGE  
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip:Target code@target domain name>;tag=e4080457  
+Content-Type: Application/ECCS+xml  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Response>  
+<CmdType>CruiseTrackListQuery</CmdType>  
+<SN>123</SN>  
+<DeviceID>0086340200000013100000001</DeviceID>  
+<Sum">2</SumNum>  
+<CruiseTrackList Num="2">  
+<CruiseTrack>  
+<Number>1</Number>
+
+```
+
+<Name>CRUISE TRACKER1</Name>
+</CruiseTrack>
+<CruiseTrack>
+<Number>2</Number>
+<Name>CRUISE TRACKER2</Name>
+</CruiseTrack>
+</CruiseTrackList>
+</Response>
+
+```
+
+##### **h) SIP/2.0 200 OK**
+
+```
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip:Target code@target domain name>;tag=e4080458
+To: <sip:source code@source domain name>;tag=852843630
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+CSeq: 2 MESSAGE
+Content-Length: 0
+
+```
+
+#### 8.5.4.8 Examples of cruise track query messages
+
+##### **a) MESSAGE sip:Target code@target domain name or IP address port SIP/2.0**
+
+```
+
+To: <sip:Target code@target domain name>
+Content-Length: Byte length of message body
+CSeq: 2 MESSAGE
+Call-ID: a84b4c76e66710
+Via: SIP/2.0/UDP source domain name or IP address
+From: <sip:source code@source domain name>;tag=e40807c0
+Content-Type: Application/ECCS+xml
+Max-Forwards: 70
+<?xml version="1.0"?>
+<Query>
+<CmdType>CruiseTrackQuery</CmdType>
+<SN>123</SN>
+<DeviceID>0086340200000013100000001</DeviceID>
+<Number>1</Number>
+</Query>
+
+```
+
+##### **b) SIP/2.0 200 OK**
+
+```
+
+Via: SIP/2.0/UDP source domain name or IP address
+From: <sip:source code@source domain name>;tag=e40807c0
+To: <sip:Target code@target domain name>;tag=852843529
+Call-ID: a84b4c76e66710
+CSeq: 2 MESSAGE
+Content-Length: 0
+
+```
+
+##### **c) MESSAGE sip:Target code@target domain name or IP address port SIP/2.0**
+
+```
+
+To: <sip:Target code@target domain name>
+Content-Length: Byte length of message body
+CSeq: 2 MESSAGE
+Call-ID: a84b4c76e66543
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip:source code@source domain name>;tag=e4080457
+Content-Type: Application/ECCS+xml
+Max-Forwards: 70
+<?xml version="1.0"?>
+<Query>
+<CmdType>CruiseTrackQuery</CmdType>
+<SN>123</SN>
+<DeviceID>0086340200000013100000001</DeviceID>
+<Number>1</Number>
+</Query>
+
+```
+
+##### **d) SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip:source code@source domain name>;tag=e4080457  
+To: <sip:Target code@target domain name>;tag=852843630  
+Call-ID: a84b4c76e66543  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+
+##### **e) MESSAGE sip:source code@source domain name or IP address port SIP/2.0**
+
+To: <sip:source code@source domain name>  
+Content-Length: Byte length of message body  
+CSeq: 2 MESSAGE  
+Call-ID: a84b4c76e66543  
+Via: SIP/2.0/UDP target domain name or IP address  
+From: <sip:target code@target domain name>;tag=e4080457  
+Content-Type: Application/ECCS+xml  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Response>  
+<CmdType>CruiseTrackQuery</CmdType>  
+<SN>123</SN>  
+<DeviceID>0086340200000013100000001</DeviceID>  
+<Number>1</Number>  
+<Name>CRUISE TRACK1</Name>  
+<SumNum>2</SumNum>  
+<CruisePointList Num="2">  
+<CruisePoint>  
+<PresetIndex>1</PresetIndex>  
+<StayTime>5</StayTime>  
+<Speed>2</Speed>  
+</CruisePoint>  
+<CruisePoint>  
+<PresetIndex>2</PresetIndex>  
+<StayTime>10</StayTime>  
+<Speed>5</Speed>  
+</CruisePoint>  
+</CruisePointList>  
+</Response>
+
+##### **f) SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP target domain name or IP address  
+From: <sip:Target code@target domain name>;tag=e4080457  
+To: <sip:source code@source domain name>;tag=852843630  
+Call-ID: a84b4c76e66543  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+
+##### **g) MESSAGE sip:source code@source domain name or IP address port SIP/2.0**
+
+To: <sip:source code@source domain name>  
+Content-Length: Byte length of message body  
+CSeq: 2 MESSAGE  
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip:Target code@target domain name>;tag=e4080458  
+Content-Type: Application/ECCS+xml  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Response>  
+<CmdType>CruiseTrackQuery</CmdType>  
+<SN>123</SN>  
+<DeviceID>0086340200000013100000001</DeviceID>
+
+```
+
+<Number>1</Number>
+<Name>CRUISE TRACK1</Name>
+<SumNum>2</SumNum>
+<CruisePointList Num="2">
+  <CruisePoint>
+    <PresetIndex>1</PresetIndex>
+    <StayTime>5</StayTime>
+    <Speed>2</Speed>
+  </CruisePoint>
+  <CruisePoint>
+    <PresetIndex>2</PresetIndex>
+    <StayTime>10</StayTime>
+    <Speed>5</Speed>
+  </CruisePoint>
+</CruisePointList>
+</Response>
+
+```
+
+##### **h) SIP/2.0 200 OK**
+
+```
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip:Target code@target domain name>;tag=e4080458
+To: <sip:source code@source domain name>;tag=852843630
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+CSeq: 2 MESSAGE
+Content-Length: 0
+
+```
+
+#### **8.5.4.9 Examples of PTZ precise status query messages**
+
+##### **a) MESSAGE sip:Target code@target domain name or IP address port SIP/2.0**
+
+```
+
+To: <sip:Target code@target domain name>
+Content-Length: Byte length of message body
+CSeq: 2 MESSAGE
+Call-ID: a84b4c76e66710
+Via: SIP/2.0/UDP source domain name or IP address
+From: <sip:source code@source domain name>;tag=e40807c0
+Content-Type: Application/ECCS+xml
+Max-Forwards: 70
+<?xml version="1.0"?>
+<Query>
+<CmdType>PTZPosition</CmdType>
+<SN>17430</SN>
+<DeviceID>0086110100000011100000001</DeviceID>
+</Query>
+
+```
+
+##### **b) SIP/2.0 200 OK**
+
+```
+
+Via: SIP/2.0/UDP source domain name or IP address
+From: <sip:source code@source domain name>;tag=e40807c0
+To: <sip:Target code@target domain name>;tag=852843529
+Call-ID: a84b4c76e66710
+CSeq: 2 MESSAGE
+Content-Length: 0
+
+```
+
+##### **c) MESSAGE sip:Target code@target domain name or IP address port SIP/2.0**
+
+```
+
+To: <sip:Target code@target domain name>
+Content-Length: Byte length of message body
+CSeq: 2 MESSAGE
+Call-ID: a84b4c76e66543
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip:source code@source domain name>;tag=e4080457
+Content-Type: Application/ECCS+xml
+Max-Forwards: 70
+<?xml version="1.0"?>
+<Query>
+
+```
+
+```
+
+<CmdType>PTZPosition</CmdType>
+<SN>17430</SN>
+<DeviceID>0086110100000011100000001</DeviceID>
+</Query>
+
+```
+
+##### **d) SIP/2.0 200 OK**
+
+```
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip:source code@source domain name>;tag=e4080457
+To: <sip:Target code@target domain name>;tag=852843630
+Call-ID: a84b4c76e66543
+CSeq: 2 MESSAGE
+Content-Length: 0
+
+```
+
+##### **e) MESSAGE sip:source code@source domain name or IP address port SIP/2.0**
+
+```
+
+Via: SIP/2.0/UDP target domain name or IP address
+From: <sip:Target code@target domain name>;tag=852843529
+To: <sip:source code@source domain name>
+Call-ID: de432gtf51u870
+CSeq: 2 MESSAGE
+Max-Forwards: 70
+Content-Type: Application/ECCS+xml
+Content-Length: Byte length of message body
+<?xml version="1.0"?>
+  <Response>
+    <CmdType>PTZPosition</CmdType>
+    <SN>17430</SN>
+    <DeviceID>0086110100000011100000001</DeviceID>
+    <Pan>90.00</Pan>
+    <Tilt>70.00</Tilt>
+    <Zoom>3.00</Zoom>
+    <HorizontalFieldAngle>100.00</HorizontalFieldAngle>
+    <VerticalFieldAngle>90.00</VerticalFieldAngle>
+    <MaxViewDistance>34.00</MaxViewDistance>
+  </Response>
+
+```
+
+##### **f) SIP/2.0 200 OK**
+
+```
+
+To: <sip:source code@source domain name>;tag=e40807c0
+Content-Length: 0
+CSeq: 2 MESSAGE
+Call-ID: de432gtf51u870
+Via: SIP/2.0/UDP target domain name or IP address
+From: <sip:Target code@target domain name>;tag=852843529
+
+```
+
+##### **g) MESSAGE sip:source code@source domain name or IP address port SIP/2.0**
+
+```
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip:Target code@target domain name>;tag=852843529
+To: <sip:source code@source domain name>
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+CSeq: 2 MESSAGE
+Max-Forwards: 70
+Content-Type: Application/ECCS+xml
+Content-Length: Byte length of message body
+<?xml version="1.0"?>
+  <Response>
+    <CmdType>PTZPosition</CmdType>
+    <SN>17430</SN>
+    <DeviceID>0086110100000011100000001</DeviceID>
+    <Pan>90.00</Pan>
+    <Tilt>70.00</Tilt>
+    <Zoom>3.00</Zoom>
+    <HorizontalFieldAngle>100.00</HorizontalFieldAngle>
+    <VerticalFieldAngle>90.00</VerticalFieldAngle>
+
+```
+
+```
+<MaxViewDistance>34.00</MaxViewDistance>  
+</Response>
+```
+
+##### **h) SIP/2.0 200 OK**
+
+```
+To: <sip:source code@source domain name>;tag=e40807c0  
+Content-Length: 0  
+CSeq: 2 MESSAGE  
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip:Target code@target domain name>;tag=852843529
+```
+
+#### **8.5.4.10 Examples of OSD information query messages**
+
+##### **a) MESSAGE sip:Target code@target domain name or IP address port SIP/2.0**
+
+```
+To: <sip:Target code@target domain name>  
+Content-Length: Byte length of message body  
+CSeq: 2 MESSAGE  
+Call-ID: a84b4c76e66710  
+Via: SIP/2.0/UDP source domain name or IP address  
+From: <sip:source code@source domain name>;tag=e40807c0  
+Content-Type: Application/ECCS+xml  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Query>  
+<CmdType>OSDQuery</CmdType>  
+<SN>17430</SN>  
+<DeviceID>008611010000001110000001</DeviceID>  
+</Query>
+```
+
+##### **b) SIP/2.0 200 OK**
+
+```
+Via: SIP/2.0/UDP source domain name or IP address  
+From: <sip:source code@source domain name>;tag=e40807c0  
+To: <sip:Target code@target domain name>;tag=852843529  
+Call-ID: a84b4c76e66710  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+```
+
+##### **c) MESSAGE sip:Target code@target domain name or IP address port SIP/2.0**
+
+```
+To: <sip:Target code@target domain name>  
+Content-Length: Byte length of message body  
+CSeq: 2 MESSAGE  
+Call-ID: a84b4c76e66543  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip:source code@source domain name>;tag=e4080457  
+<?xml version="1.0"?>  
+<Query>  
+<CmdType>OSDQuery</CmdType>  
+<SN>17430</SN>  
+<DeviceID>008611010000001110000001</DeviceID>  
+</Query>
+```
+
+##### **d) SIP/2.0 200 OK**
+
+```
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip:source code@source domain name>;tag=e4080457  
+To: <sip:Target code@target domain name>;tag=852843630  
+Call-ID: a84b4c76e66543  
+CSeq: 2 MESSAGE  
+Content-Length: 0
+```
+
+##### **e) MESSAGE sip:source code@source domain name or IP address port SIP/2.0**
+
+```
+
+Via: SIP/2.0/UDP target domain name or IP address
+From: <sip:Target code@target domain name>;tag=852843529
+To: <sip:source code@source domain name>
+Call-ID: de432gtf51u870
+CSeq: 2 MESSAGE
+Max-Forwards: 70
+Content-Type: Application/ECCS+xml
+Content-Length: Byte length of message body
+<?xml version="1.0"?>
+<Response>
+<CmdType>OSDQuery</CmdType>
+<SN>17430</SN>
+<DeviceID>0086110100000011100000001</DeviceID>
+<Length>1920</Length>
+<Width>1080</Width>
+<TimeX>0</TimeX>
+<TimeY>0</TimeY>
+<TimeEnable>1</TimeEnable>
+<TimeType>0</TimeType>
+<TextEnable>1</TextEnable>
+<Item>
+<Text>CameraIPC</Text>
+<X>1</X>
+<Y>1</Y>
+</Item>
+<Item>
+<Text>street</Text>
+<X>1</X>
+<Y>3</Y>
+</Item>
+</Response>
+
+```
+
+##### **f) SIP/2.0 200 OK**
+
+```
+
+To: <sip:source code@source domain name>;tag=e40807c0
+Content-Length: 0
+CSeq: 2 MESSAGE
+Call-ID: de432gtf51u870
+Via: SIP/2.0/UDPtarget domain name or IP address
+From: <sip:Target code@target domain name>;tag=852843529
+
+```
+
+##### **g) MESSAGE sip:source code@source domain name or IP address port SIP/2.0**
+
+```
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip:Target code@target domain name>;tag=852843529
+To: <sip:source code@source domain name>
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+CSeq: 2 MESSAGE
+Max-Forwards: 70
+Content-Type: Application/ECCS+xml
+Content-Length: Byte length of message body
+<?xml version="1.0"?>
+<Response>
+<CmdType>OSDQuery</CmdType>
+<SN>17430</SN>
+<DeviceID>0086110100000011100000001</DeviceID>
+<Length>1920</Length>
+<Width>1080</Width>
+<TimeX>0</TimeX>
+<TimeY>0</TimeY>
+<TimeEnable>1</TimeEnable>
+<TimeType>0</TimeType>
+<TextEnable>1</TextEnable>
+<Item>
+
+```
+
+```
+
+<Text>CameraIPC</Text>
+<X>1</X>
+<Y>1</Y>
+</Item>
+<Item>
+<Text>street</Text>
+<X>1</X>
+<Y>3</Y>
+</Item>
+</Response>
+
+```
+
+##### h) **SIP/2.0 200 OK**
+
+```
+
+To: <sip:source code@source domain name>;tag=e40807c0
+Content-Length: 0
+CSeq: 2 MESSAGE
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip:Target code@target domain name>;tag=852843529
+
+```
+
+## 8.6 Status information reporting
+
+### 8.6.1 Basic requirements
+
+If the source, including PU, CU, CPG, MS or the other CCS with SRG, is found to be working abnormally, a status information shall be sent to the CCS of the VSS immediately. If there is no abnormality, status information shall be sent to the CCS of the VSS regularly. The source should carry the descriptive information of the faulty subdevice in the status information; see the status information reporting of notification command in clause A.2.5 a) for details. 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 CCS shall configure a unified heartbeat interval parameter, and send heartbeat messages according to the heartbeat interval regularly, with the default heartbeat interval being 60 s. The source and CCS shall configure a unified number of heartbeat timeouts parameter. 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.6.2 Signalling process
+
+For the status information reporting signalling flow, see Figure 8-10.
+
+![Sequence diagram showing the signalling flow of status information reporting between a Source and a CCS. The Source sends a '1: Message (Status information reporting)' to the CCS, and the CCS responds with '2: 200 OK'. The diagram is labeled H.627(20)_F8-10.](e404de9a69c05473fbd6af28ee32311b_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Source
+    participant CCS
+    Note right of CCS: H.627(20)_F8-10
+    Source->>CCS: 1: Message (Status information reporting)
+    CCS-->>Source: 2: 200 OK
+  
+```
+
+Sequence diagram showing the signalling flow of status information reporting between a Source and a CCS. The Source sends a '1: Message (Status information reporting)' to the CCS, and the CCS responds with '2: 200 OK'. The diagram is labeled H.627(20)\_F8-10.
+
+**Figure 8-10 – Signalling flow of status information reporting**
+
+The signalling flow description is as follows.
+
+- The source sends the device status information reporting commands to the CCS, and the device status information reporting commands are carried in the message body by the MESSAGE method.
+- The CCS replies with a 200 OK response after receiving the commands.
+
+See the examples of device status-reporting messages in clause 8.6.4.
+
+### 8.6.3 Protocol interface
+
+The Content-type header field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+Status information reporting commands are specified in the ECCS. For a detailed description, see the status information reporting of notification command in clause A.2.5 a).
+
+The status information reporting commands shall include command type (CmdType), device/VSS 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.4 Examples of device status-reporting messages
+
+- MESSAGE sip: target code@target domain name or IP address port SIP/2.0
+
+```
+
+To: <sip: target code@target domain name>
+Content-Length: Byte length of message body
+CSeq: 2 MESSAGE
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+Via: SIP/2.0/UDP source domain name or IP address
+From: <sip: source code@source domain name>; tag=e40807c0
+Content-Type: Application/ECCS+xml
+Max-Forwards: 70
+<?xml version="1.0"?>
+<Notify>
+<CmdType>Keepalive</CmdType>
+<SN>43</SN>
+<DeviceID>0086110100000011100000001</DeviceID>
+<Status>OK</Status>
+</Notify>
+          
+```
+- SIP/2.0 200 OK
+
+```
+
+Via: SIP/2.0/UDP source domain name or IP address
+From: <sip: source code@source domain name>; tag=e40807c0
+To: <sip: Target code@target domain name>; tag=852843529
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+CSeq: 2 MESSAGE
+Content-Length: 0
+          
+```
+
+## 8.7 Historical media file retrieval
+
+### 8.7.1 Basic requirements
+
+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, and the results can be sent by multiple MESSAGES compliant with clause 7.5. File retrieval request and response commands are specified in the ECCS, for a detailed description, see the file directory retrieval requests in clause A.2.4 d) and file directory retrieval responses in clause A.2.6 h).
+
+### 8.7.2 Signalling process
+
+For the historical media file retrieval signalling flow, see Figure 8-11.
+
+![Sequence diagram showing the signalling flow of historical media file retrieval between a Source and a Target. The flow consists of four steps: 1. Source sends a 'Message (File directory query)' to Target; 2. Target responds with '200 OK'; 3. Target sends the 'Message (File directory)' results to Source; 4. Source responds with '200 OK'. The diagram is labeled H.627(20)_F8-11.](20cb2d2cc18d663dc1b82453c67250bb_img.jpg)
+
+```
+sequenceDiagram
+    participant Source
+    participant Target
+    Note right of Target: H.627(20)_F8-11
+    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 media file retrieval between a Source and a Target. The flow consists of four steps: 1. Source sends a 'Message (File directory query)' to Target; 2. Target responds with '200 OK'; 3. Target sends the 'Message (File directory)' results to Source; 4. Source responds with '200 OK'. The diagram is labeled H.627(20)\_F8-11.
+
+**Figure 8-11 – Signalling flow of historical media file retrieval**
+
+The sources include CU or CCS and the targets include PU, MS or CCS of the other VSS.
+
+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 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.
+
+See the examples of historical media file retrieval messages in clause 8.7.4.
+
+### 8.7.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.4 Examples of historical media file retrieval messages
+
+- a) MESSAGE sip: target code@target domain name or IP address port SIP/2.0  
+To: <sip: target code@target domain name>  
+Content-Length: Byte length of message body  
+CSeq: 2 MESSAGE  
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+Via: SIP/2.0/UDP source domain name or IP address  
+From: <sip: source code@source domain name>; tag=e40807c0
+
+```
+
+Content-Type: Application/ECCS+xml
+Max-Forwards: 70
+<?xml version="1.0"?>
+<Query>
+<CmdType> RecordInfo </CmdType>
+<SN>17430</SN>
+<DeviceID>0086110100000013100000001</DeviceID>
+<StartTime>2010-11-11T19:46:17</StartTime>
+<EndTime>2010-11-12T19:46:17</EndTime>
+<FilePath>0086110100000021000000001</FilePath>
+<Address> Address 1</Address>
+<Type>time</Type>
+<RecorderID>0086110100000030000000001</RecorderID>
+</Query>
+
+```
+
+#### **b) SIP/2.0 200 OK**
+
+```
+
+Via: SIP/2.0/UDP source domain name or IP address
+From: <sip: source code@source domain name>; tag=e40807c0
+To: <sip: Target code@target domain name>; tag=852843529
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+CSeq: 2 MESSAGE
+Content-Length: 0
+
+```
+
+##### **c) MESSAGE sip: source code@source domain name or IP address port SIP/2.0**
+
+```
+
+Via: SIP/2.0/UDP target domain name or IP address
+From: <sip: Target code@target domain name>; tag=852843529
+To: <sip: source code@source domain name>
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+CSeq: 2 MESSAGE
+Max-Forwards: 70
+Content-Type: Application/ECCS+xml
+Content-Length: Byte length of message body
+<?xml version="1.0"?>
+<Response>
+<CmdType> RecordInfo </CmdType>
+<SN>17430</SN>
+<DeviceID>0086110100000013100000001</DeviceID>
+<Name>Camera1</Name>
+<SumNum>100</SumNum>
+<RecordList Num="2">
+<Item>
+<DeviceID>0086110100000013100000001</DeviceID>
+<Name> Camera1 </Name>
+<FilePath> 0086110100000021000000001 </FilePath>
+<Address> Address 1 </Address>
+<StartTime> 2010-11-12T10:10:00 </StartTime>
+<EndTime> 2010-11-12T10:20:00 </EndTime>
+<Type> time </Type>
+<RecorderID> 0086110100000030000000001 </RecorderID>
+</Item>
+<Item>
+<DeviceID>0086110100000013100000001</DeviceID>
+<Name> Camera1 </Name>
+<FilePath> 0086110100000021000000001 </FilePath>
+<Address> Address 1 </Address>
+<StartTime> 2010-11-12T10:8:00 PM </StartTime>
+<EndTime> 2010-11-12T10:30:00 </EndTime>
+<Type> time </Type>
+<RecorderID> 0086110100000030000000001 </RecorderID>
+</Item>
+</RecordList>
+</Response>
+
+```
+
+d) SIP/2.0 200 OK  
+To: <sip: source code@source domain name>; tag=e40807c0  
+Content-Length: 0  
+CSeq: 2 MESSAGE  
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5  
+Via: SIP/2.0/UDP target domain name or IP address  
+From: <sip: Target code@target domain name>; tag=852843529
+
+## 8.8 Historical media file playback
+
+### 8.8.1 Basic requirements
+
+Session connection shall be achieved with the INVITE method in the SIP [IETF RFC 3261], historical media file playback control commands shall be carried in the message body with the INFO method in the SIP Extension [IETF RFC 6086], and media transmission shall be achieved through the RTP or RTCP [IETF RFC 3550][IETF RFC 4571]. Historical media file playback control commands adopt the request and response messages of PLAY, PAUSE and TEARDOWN in the extended media command set (EMCS), see clause 7.3 for details.
+
+The signalling process of historical media file playback comprises two methods, namely initiated by the media stream receiver and a third party unit, and the VSS can select one method or the combination of the two methods for implementation. The third-party controller of the third-party call control should be achieved by using the B2BUA; for matters related to third party call control, see [IETF RFC 3725].
+
+The historical media file playback should support the media stream keepalive mechanism specified in clause 7.4.
+
+### 8.8.2 Signalling process
+
+#### 8.8.2.1 Initiation by media stream receiver
+
+For the historical media file playback signalling flow initiated by media stream receiver, see Figure 8-12.
+
+![Sequence diagram showing the signalling flow of historical media file playback initiated by a media stream receiver. The diagram involves four lifelines: Media stream receiver, CCS, MS, and Media stream sender. The process involves multiple SIP messages (Invite, 200 OK, ACK, INFO, BYE) and two 'Historical media stream' transfers indicated by green arrows.](caeb1637753f79f4cd005eda3768d1d5_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS as Media stream sender
+    participant CCS as CCS
+    participant MR as Media stream receiver
+    participant M as MS
+
+    Note right of M: Historical media stream
+    MR->>CCS: 1: Invite (with SDP)
+    CCS->>M: 2: Invite
+    M-->>CCS: 3: 200 OK (with SDP)
+    CCS->>MS: 4: Invite (with SDP)
+    MS-->>CCS: 5: 200 OK (with SDP)
+    CCS->>M: 6: ACK (with SDP)
+    CCS->>MS: 7: ACK
+    Note right of M: Historical media stream
+    CCS->>M: 8: Invite (with SDP)
+    M-->>CCS: 9: 200 OK (with SDP)
+    CCS-->>MR: 10: 200 OK (with SDP)
+    MR->>CCS: 11: ACK
+    CCS->>M: 12: ACK
+    Note left of M: Historical media stream
+    MR->>CCS: 13: INFO
+    CCS->>MS: 14: INFO
+    MS-->>CCS: 15: 200 OK
+    CCS-->>MR: 16: 200 OK
+    CCS->>MS: 17: Message (File sending complete)
+    MR-->>CCS: 18: Message (File sending complete)
+    MR->>CCS: 19: 200 OK
+    CCS->>MS: 20: 200 OK
+    MR->>CCS: 21: BYE
+    MR-->>CCS: 22: 200 OK
+    CCS->>M: 23: BYE
+    M-->>CCS: 24: 200 OK
+    CCS->>M: 25: BYE
+    M-->>CCS: 26: 200 OK
+    CCS->>MS: 27: BYE
+    MS-->>CCS: 28: 200 OK
+  
+```
+
+Sequence diagram showing the signalling flow of historical media file playback initiated by a media stream receiver. The diagram involves four lifelines: Media stream receiver, CCS, MS, and Media stream sender. The process involves multiple SIP messages (Invite, 200 OK, ACK, INFO, BYE) and two 'Historical media stream' transfers indicated by green arrows.
+
+H.627(20)\_F8-12
+
+**Figure 8-12 – Signalling flow of historical media file playback initiated by a media stream receiver**
+
+In Figure 8-12, the media stream receiver includes the CU or the other VSS. The media stream sender includes the PU or the other VSS.
+
+In Figure 8-12:
+
+signals 1, 8, 9, 10, 11 and 12 constitute the process of establishing the media link between the media stream receiver and the MS with the B2BUA method by the CCS, after receiving the media stream receiver call request;
+
+signals 2-7 constitute the process of establishing the media link between the MS and the media stream sender through the third-party call control by the CCS;
+
+signals 13-16 constitute the process of conducting the playback control by the media stream receiver;
+
+signals 17-20 constitute the process of sending the notification message to the media stream receiver by the media stream sender while playback ends;
+
+signals 21-24 constitute the process of disconnecting the media link between the media stream receiver and the MS; and
+
+signals 25-28 constitute the process of disconnecting the media link between the MS and the media stream sender by the CCS.
+
+The signalling flow description is as follows.
+
+- The media stream receiver sends the Invite message to the CCS, and the message header field carries the subject field, showing such parameters as video source ID of real-time media stream, sender media stream SN, media stream receiver ID and receiver media stream SN; the s field in the SDP message is "Playback", representing historical playback; the u field represents the playback channel ID and playback type; the t field represents the playback time period.
+- After the CCS receives the Invite request, the media connection between the MS and the media stream sender is established through third-party call control. The Invite message is sent to the MS, and this message does not carry the SDP message body.
+- After the MS receives the Invite request of the CCS, it replies with a 200 OK response, carrying the SDP message body in which the IP, port, media format, etc. of the media stream received by the MS are described.
+- After the CCS receives the 200 OK response sent from the MS, it sends the Invite request to the media stream sender; the request carries the 200 OK response message body sent by the MS in message 3, and the s field is "Playback", representing historical playback; the u field represents the playback channel ID and playback type; the t field represents the playback time period; the y field is added to describe the SSRC value and f field for the media parameters.
+- After the media stream sender receives the Invite request from the CCS, it replies with the 200 OK response, carrying the SDP message body in which the IP, port, media format, SSRC field, etc. of the media stream sent by the media stream sender are described.
+- After the CCS receives the 200 OK response sent back from the media stream sender, it sends an ACK request to the MS, which carries the 200 OK response message body sent by the media stream sender in message 5, and the establishment process of the Invite session with the MS is finished.
+- After the CCS receives the 200 OK response sent back from the media stream sender, it sends an ACK request to the media stream sender, which does not carry a message body, and the establishment process of the Invite session with the media stream sender is finished.
+- Upon the completion of third-party call control, the CCS establishes the media connection between the media stream receiver and the MS with the B2BUA method, adds the SSRC value to message 1 and forwards it to the MS.
+- After the MS receives the Invite request, it replies with the 200 OK response, carrying the SDP message body in which the IP, port, media format, SSRC value, etc. of the media stream sent by the MS are described.
+- The CCS forwards message 9 to the media stream receiver.
+- After the media stream receiver receives the 200 OK response, it replies with the ACK message, and the establishment process of the Invite session with CCS is finished.
+
+- The CCS forwards message 11 to the MS, and the establishment process of the Invite session with the CCS is finished.
+- The media stream receiver sends the session Info message to the CCS in the playback process for playback control, including such operations as pause, play, fast forward, slow forward, random playback and play; for the Info message body, see clause 7.3.
+- The CCS forwards message 13 to the media stream sender after receiving the message.
+- After the media stream sender receives message 14, it replies with the 200 OK response.
+- The CCS forwards message 15 to the media stream receiver.
+- The media stream sender sends the session MESSAGE at the end of file playback, notifying the CCS that the playback has ended; for the message body format, see the media notifications in clause A.2.5 c).
+- The CCS forwards message 17 to the media stream receiver after receiving the message.
+- After the media stream receiver receives message 18, it replies with the 200 OK response, and the link disconnection process is initiated.
+- The CCS forwards message 19 to the media stream sender.
+- The media stream receiver sends the BYE message to the CCS, and the Invite session with the media stream receiver established by messages 1, 10 and 11 is disconnected.
+- After the CCS receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- After the CCS receives the BYE message, it sends the BYE message to the MS, and the Invite session with the MS established by messages 8, 9 and 12 is disconnected.
+- After the MS receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- The CCS sends the BYE message to the MS, and the Invite session with the MS established by messages 2, 3 and 6 is disconnected.
+- After the MS receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- The CCS sends the BYE message to the media stream sender, and the Invite session with the media stream sender established by messages 4, 5 and 7 is disconnected.
+- After the media stream sender receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+
+See the examples of historical media file playback messages initiated by the media stream receiver in clause 8.8.4.1.
+
+#### **8.8.2.2 Third-party call control**
+
+For the historical media file playback signalling flow initiated by a third party unit, see Figure 8-13.
+
+![Sequence diagram showing the signalling flow for historical media file playback initiated by a third party unit. The diagram involves four lifelines: Media stream receiver, CCS, MS, and Media stream sender. The process involves two main media link establishment phases (signals 1-6 and 7-12), followed by playback control (signals 13-14), end-of-playback notification (signals 15-16), and session termination (signals 17-24). Green arrows indicate the 'Historical media stream' flow from the Media stream sender to the Media stream receiver via the MS.](e8f5117fb031f413a836525061addd61_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS as MS
+    participant CSS as CCS
+    participant MSReceiver as Media stream receiver
+    participant MSSender as Media stream sender
+
+    Note right of MS: Historical media stream
+    CSS->>MS: 1: Invite
+    MS-->>CSS: 2: 200 OK (with SDP)
+    CSS->>MSSender: 3: Invite (with SDP)
+    MSSender-->>CSS: 4: 200 OK (with SDP)
+    CSS->>MS: 5: ACK (with SDP)
+    MSSender-->>CSS: 6: ACK
+    Note right of MS: Historical media stream
+    CSS->>MSReceiver: 7: Invite
+    MSReceiver-->>CSS: 8: 200 OK (with SDP)
+    CSS->>MS: 9: Invite (with SDP)
+    MS-->>CSS: 10: 200 OK (with SDP)
+    MSReceiver-->>CSS: 11: ACK (with SDP)
+    CSS->>MS: 12: ACK
+    Note left of MS: Historical media stream
+    CSS->>MSSender: 13: INFO
+    MSSender-->>CSS: 14: 200 OK
+    CSS-->>MSSender: 15: Message (File to end)
+    MSSender-->>CSS: 16: 200 OK
+    MSReceiver-->>CSS: 17: BYE
+    CSS-->>MSReceiver: 18: 200 OK
+    CSS->>MS: 19: BYE
+    MS-->>CSS: 20: 200 OK
+    CSS->>MS: 21: BYE
+    MS-->>CSS: 22: 200 OK
+    CSS->>MSSender: 23: BYE
+    MSSender-->>CSS: 24: 200 OK
+  
+```
+
+Sequence diagram showing the signalling flow for historical media file playback initiated by a third party unit. The diagram involves four lifelines: Media stream receiver, CCS, MS, and Media stream sender. The process involves two main media link establishment phases (signals 1-6 and 7-12), followed by playback control (signals 13-14), end-of-playback notification (signals 15-16), and session termination (signals 17-24). Green arrows indicate the 'Historical media stream' flow from the Media stream sender to the Media stream receiver via the MS.
+
+H.627(20)\_F8-13
+
+**Figure 8-13 – Signalling flow of historical media file playback initiated by a third party unit**
+
+In Figure 8-13, the media stream receiver includes the CU or the other VSS. Media stream sender includes PU or the other VSS.
+
+In Figure 8-13:
+
+signals 1-6 constitute the process of establishing the media link between the MS and the media stream sender through the third-party call control by the CCS;
+
+signals 7-12 constitute the process of establishing the media link between the media stream receiver and the MS through the third-party call control by the CCS;
+
+signals 13-14 constitute the process of conducting the playback control signals;
+
+signals 15-16 constitute the process of sending the end-of-playback notification message to the media stream receiver by the media stream sender while playback ends;
+
+signals 17–20 constitute the process of disconnecting the media link between the media stream receiver and the MS;
+
+signals 21-24 constitute the process of disconnecting the media link between the MS and the media stream sender.
+
+The signalling flow description is as follows.
+
+- The CCS sends the Invite message to the MS, and this message does not carry the SDP message body.
+- After the MS receives the Invite request of the CCS, it replies with a 200 OK response, carrying the SDP message body in which the IP, port, media format, etc. of the media stream received by the MS are described.
+- After the CCS receives the 200 OK response sent back from the MS, it sends the Invite request to the media stream sender, which carries the 200 OK response message body sent by the MS in message 2, and the s field is "Playback", representing historical playback; the u field represents the playback channel ID and playback type; the t field represents the playback time period; the y field is added to describe the SSRC value and f field for media parameter.
+- After the media stream sender receives the Invite request of the CCS, it replies with the 200 OK response, carrying the SDP message body in which the IP, port, media format, SSRC field, etc. of the media stream sent by the media stream sender are described.
+- After the CCS receives the 200 OK response sent back from the media stream sender, it sends an ACK request to the MS, which carries the 200 OK response message body sent by the media stream sender in message 4, and the establishment process of the Invite session with the MS is finished.
+- After the CCS receives the 200 OK response sent back from the media stream sender, it sends an ACK request to the media stream sender, which does not carry a message body, and the establishment process of the Invite session with the media stream sender is finished.
+- The CCS sends the Invite message to the media stream receiver, and this message does not carry the SDP message body.
+- After the media stream receiver receives the Invite request of the CCS, it replies with the 200 OK response, carrying the SDP message body in which the IP, port, media format, etc. of the media stream received by the media stream receiver are described.
+- After the CCS receives the 200 OK response sent back from the media stream receiver, it sends the Invite request to the MS, which carries the 200 OK response message body sent by the media stream receiver in message 8, and the s field is "Playback", representing historical playback; the y field is added to describe the SSRC value.
+- After the MS receives the Invite request of the CCS, it replies with the 200 OK response, carrying the SDP message body in which the IP, port, media format, SSRC field, etc. of the media stream sent by the MS are described.
+- After the CCS receives the 200 OK response sent back from the MS, it sends an ACK request to the MS, which carries the 200 OK response message body sent by the MS in message 10, and the establishment process of the Invite session with the media stream receiver is finished.
+- After the CCS receives the 200 OK response sent back from the MS, it sends an ACK request to the MS, which does not carry a message body, and the establishment process of the Invite session with the MS is finished.
+- The media stream receiver sends the Info message to the CCS in the playback process for playback control, including such operations as pause, play, positioning, fast forward and slow forward; for the Info message body, see clause 7.3.
+
+- After the media stream sender receives the Info message, it replies with the 200 OK response.
+- The media stream sender sends the session MESSAGE at the end of file playback, notifying the CCS that the playback has ended; for the message body format, see the media notifications in clause A.2.5 c).
+- After the CCS receives the MESSAGE, it replies with the 200 OK response, and the link disconnection process is initiated.
+- The CCS sends the BYE message to the media stream receiver, and the Invite session with the media stream receiver established by messages 7, 8 and 11 is disconnected.
+- After the media stream receiver receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- The CCS sends the BYE message to the MS, and the Invite session with the MS established by messages 9, 10 and 12 is disconnected.
+- After the MS receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- The CCS sends the BYE message to the MS, and the Invite session with the MS established by messages 1, 2 and 5 is disconnected.
+- After the MS receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- The CCS sends the BYE message to the media stream sender, and the Invite session with the media stream sender established by messages 3, 4 and 6 is disconnected.
+- After the media stream sender receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+
+See the examples of historical media file playback messages initiated by a third party unit in clause 8.8.4.2.
+
+### 8.8.3 Protocol interface
+
+#### 8.8.3.1 Session control protocol
+
+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 is Content-type: Application/SDP.
+
+The request and response message bodies carried in the historical media file playback process are defined in the SDP format. For a detailed description related to SDP, see [IETF RFC 4566].
+
+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 INVITE request acquires the historical media in the form of time periods.
+
+The information of positioning the historical media data is carried with the message body in the SDP format, and shall include the device name and time period information, specified as follows.
+
+- The media stream receiver shall include the u line (see clause 5.5 of [IETF RFC 4566]) in the message body in the SDP format, and the device URI of the media source (such as a certain camera) generating the historical media shall be filled in the u line, which shall comply with the provisions of clause 7.2. The device URI shall include the media source
+
+device ID, and the media source device ID shall become the device name information for retrieving the historical media data.
+
+- The media stream receiver shall include the t line (see clause 5.9 of [IETF RFC 4566]) in the message body in the SDP format, and the start time and the end time of the t line shall constitute the time period information for retrieving the historical media data.
+
+#### 8.8.3.2 Historical media file playback control protocol
+
+The historical media file playback control process is the process of achieving such historical media file playback control commands as play, pause, forward/backward and stop with the SIP INFO message. The historical media file playback control request message is carried in the message body with the INFO method, and the playback control request message shall comply with certain specifications for request messages in the EMCS, including PLAY, PAUSE and TEARDOWN; the historical media file playback control response message can be carried in the 200 OK response message body with the INFO method, and the playback control response message shall comply with the specifications for response messages in the EMCS. For a detailed description related to historical media file playback control commands, see clause 7.3.
+
+The Content-type field of the INFO header carrying EMCS request and response commands is Content-type: Application/EMCS
+
+### 8.8.4 Examples of messages
+
+#### 8.8.4.1 Examples of historical media file playback messages initiated by a media stream receiver
+
+- INVITE sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0  
+To: sip: media stream sender code@ media stream sender domain name  
+Content-Length: Byte length of message body  
+Contact: <sip: media stream receiver code@ media stream receiver IP address port>  
+CSeq: 1 INVITE  
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bdfd0@172.20.16.4  
+Via: SIP/2.0/UDP media stream receiver domain name or IP address  
+From: <sip: media stream receiver code@media stream receiver domain name>; tag=e3719a0b  
+Subject: Media stream sender ID: Sender's media stream serial number, media stream receiver ID: Receiver's media stream serial number  
+Content-Type: Application/SDP  
+Max-Forwards: 70  
+v=0  
+o=008611010600002020000001 0 0 IN IP4 172.20.16.3  
+s=Playback  
+u=008611010000041310000345:3  
+c=IN IP4 172.20.16.3  
+t=1288625085 1288625871  
+m=video 6000 RTP/AVP 96 98 100  
+a=recvonly  
+a=rtpmap: 96 PS/90000  
+a=rtpmap: 98 H264/90000  
+a=rtpmap: 100 H265/90000
+- INVITE sip: MS code@MS domain name or IP address port SIP/2.0  
+To: sip: MS code@MS domain name  
+Content-Length: Byte length of message body  
+Contact: <sip: CCS code@CCS IP address port>  
+CSeq: 1 INVITE  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address
+
+From: <sip: CCS code@CCS domain name>; tag=1ad9931d  
+Subject: Media stream sender ID: Sender's media stream serial number,  
+media stream receiver ID: Receiver's media stream serial number  
+Max-Forwards: 70
+
+##### c) SIP/2.0 200 OK
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=1ad9931d  
+To: <sip: MS code@MS domain name>; tag=3094947605  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+CSeq: 1 INVITE  
+Contact: <sip: MS code@MS domain name or IP address port>  
+Content-Type: Application/SDP  
+Content-Length: Byte length of message body  
+v=0  
+o=008611010000002020000001 0 0 IN IP4 172.18.16.3  
+s=Playback  
+c=IN IP4 172.18.16.3  
+t=1288625085 1288625871  
+m=video 6000 RTP/AVP 96 98 100  
+a=recvonly  
+a=rtpmap: 96 PS/90000  
+a=rtpmap: 98 H264/90000  
+a=rtpmap: 100 H265/90000
+
+##### d) INVITE sip: media stream sender code@media stream sender domain name or IP address port SIP/2.0
+
+To: sip: media stream sender code@ media stream sender domain name  
+Content-Length: Byte length of message body  
+Contact: <sip: CCS code@CCS IP address port>  
+CSeq: 1 INVITE  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=f569d024  
+Content-Type: Application/SDP  
+Subject: Media stream sender ID: Sender's media stream serial number,  
+media stream receiver ID: Receiver's media stream serial number  
+Max-Forwards: 70  
+v=0  
+o=008611010000002020000001 0 0 IN IP4 172.18.16.3  
+s=Playback  
+u=008611010000041310000345:3  
+c=IN IP4 172.18.16.3  
+t=1288625085 1288625871  
+m=video 6000 RTP/AVP 96 98 100  
+a=recvonly  
+a=rtpmap: 96 PS/90000  
+a=rtpmap: 98 H264/90000  
+a=rtpmap: 100 H265/90000  
+y=100000001
+
+##### e) SIP/2.0 200 OK
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=f569d024  
+To: <sip: media stream sender code@ media stream sender domain name>;  
+tag=32128  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+CSeq: 1 INVITE  
+Contact: <sip: media stream sender code@ media stream sender IP address  
+port>  
+Content-Type: Application/SDP
+
+```
+
+Content-Length: Byte length of message body
+v=0
+o=008611010000041110000044 0 0 IN IP4 172.24.18.44
+s=Playback
+c=IN IP4 172.24.18.44
+t=1288625085 1288625871
+m=video 8412 RTP/AVP 96
+a=sendonly
+a=rtpmap: 96 PS/90000
+y=100000001
+
+```
+
+##### f) ACK sip: MS code@MS domain name or IP address port SIP/2.0
+
+```
+
+To: <sip: MS code@MS domain name>;tag=3094947605
+Content-Length: Byte length of message body
+CSeq: 1 ACK
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>; tag=lad9931d
+Content-Type: Application/SDP
+Max-Forwards: 70
+v=0
+o=008611010000041110000044 0 0 IN IP4 172.24.18.44
+s=Playback
+c=IN IP4 172.24.18.44
+t=1288625085 1288625871
+m=video 8412 RTP/AVP 96
+a=sendonly
+a=rtpmap: 96 PS/90000
+y=100000001
+
+```
+
+##### g) ACK sip: media stream sender code@media stream sender domain name or IP address port SIP/2.0
+
+```
+
+To: <sip: media stream sender code@media stream sender domain name>;
+tag=32128
+Content-Length: Byte length of message body
+CSeq: 1 ACK
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>; tag=f569d024
+Max-Forwards: 70
+
+```
+
+##### h) INVITE sip: MS code@MS domain name or IP address port SIP/2.0
+
+```
+
+To: sip: MS code@MS domain name
+Content-Length: Byte length of message body
+Contact: <sip: CCS code@CCS IP address port>
+CSeq: 1 INVITE
+Call-ID: wlss-294c2c6e-eea27828118c3b50449185980f4bfd0@172.18.16.5
+Via: SIP/2.0/UDP source domain name or IP address
+From: <sip: CCS code@CCS domain name>; tag=02f283d7
+Subject: Media stream sender ID: Sender's media stream serial number, media
+stream receiver ID: Receiver's media stream serial number
+Content-Type: Application/SDP
+Max-Forwards: 70
+v=0
+o=008611010600002020000001 0 0 IN IP4 172.18.16.3
+s=Playback
+c=IN IP4 172.18.16.3
+t=1288625085 1288625871
+m=video 6000 RTP/AVP 96 98 100
+a=recvonly
+a=rtpmap: 96 PS/90000
+
+```
+
+a=rtpmap: 98 H264/90000  
+a=rtpmap: 100 H265/90000  
+y=100000001
+
+##### i) SIP/2.0 200 OK
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=02f283d7  
+To: <sip: MS code@MS domain name>; tag=994072228  
+Call-ID: wlss-294c2c6e-eea27828118c3b50449185980f4bdfd0@172.18.16.5  
+CSeq: 1 INVITE  
+Contact: <sip: MS code@MS IP address port>  
+Content-Type: Application/SDP  
+Content-Length: Byte length of message body  
+v=0  
+o=008611010000002020000001 0 0 IN IP4 172.18.16.1  
+s=Playback  
+c=IN IP4 172.18.16.1  
+t=1288625085 1288625871  
+m=video 6000 RTP/AVP 96  
+a=sendonly  
+a=rtpmap: 96 PS/90000  
+y=100000001
+
+##### j) SIP/2.0 200 OK
+
+To: <sip: media stream sender code@media stream sender domain name>;  
+tag=949c43d7  
+Contact: <sip: media stream sender code@media stream sender IP address  
+port>  
+Content-Length: Byte length of message body  
+CSeq: 1 INVITE  
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bdfd0@172.20.16.4  
+Via: SIP/2.0/UDP media stream receiver domain name or IP address  
+From: <sip: media stream receiver code@media stream receiver domain name>;  
+tag=e3719a0b  
+Content-Type: Application/SDP  
+v=0  
+o=008611010000002020000001 0 0 IN IP4 172.18.16.1  
+s=Playback  
+c=IN IP4 172.18.16.1  
+t=1288625085 1288625871  
+m=video 6000 RTP/AVP 96  
+a=sendonly  
+a=rtpmap: 96 PS/90000  
+y=100000001
+
+##### k) ACK sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0
+
+To: <sip: media stream sender code@ media stream sender domain name>;  
+tag=949c43d7  
+Content-Length: Byte length of message body  
+CSeq: 1 ACK  
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bdfd0@172.20.16.4  
+Via: SIP/2.0/UDP media stream receiver domain name or IP address  
+From: <sip: media stream receiver code@media stream receiver domain name>;  
+tag=e3719a0b  
+Max-Forwards: 70
+
+##### l) ACK sip: MS code@MS domain name or IP address port SIP/2.0
+
+To: <sip: MS code@MS domain name>;tag=994072228  
+Content-Length: Byte length of message body  
+CSeq: 1 ACK
+
+Call-ID: wlss-294c2c6e-eea27828118c3b50449185980f4bdfd0@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=02f283d7  
+Max-Forwards: 70
+
+##### m) INFO sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0
+
+To: <sip: media stream sender code@ media stream sender domain name>; tag=949c43d7  
+Contact: <sip: media stream receiver code@ media stream receiver IP address port>  
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bdfd0@172.20.16.4  
+Via: SIP/2.0/UDP media stream receiver domain name or IP address  
+From: <sip: media stream receiver code@media stream receiver domain name>; tag=e3719a0b  
+Content-Length: Byte length of message body  
+CSeq: 6 INFO  
+Content-Type: Application/EMCS  
+Max-Forwards: 70
+
+PLAY RTSP/2.0  
+CSeq: 5  
+Scale: 1.0  
+Range: npt=196-
+
+##### n) INFO sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0
+
+To: <sip: media stream sender code@ media stream sender domain name>; tag=32128  
+Content-Length: Byte length of message body  
+CSeq: 6 INFO  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=f569d024  
+Content-Type: Application/EMCS  
+Max-Forwards: 70
+
+PLAY RTSP/2.0  
+CSeq: 5  
+Scale: 1.0  
+Range: npt=196-
+
+##### o) SIP/2.0 200 OK
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=f569d024  
+To: <sip: media stream sender code@ media stream sender domain name>; tag=32128  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+CSeq: 6 INFO  
+Content-Length: Byte length of message body
+
+##### p) SIP/2.0 200 OK
+
+Via: SIP/2.0/UDP media stream receiver domain name or IP address  
+From: <sip: media stream receiver code@media stream receiver domain name>; tag=e3719a0b  
+To: <sip: media stream sender code@ media stream sender domain name>; tag=949c43d7  
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bdfd0@172.20.16.4  
+CSeq: 6 INFO
+
+Contact: <sip: media stream receiver code@ media stream receiver IP address port>  
+Content-Length: Byte length of message body
+
+##### q) MESSAGE sip: CCS code@CCS domain name or IP address port SIP/2.0
+
+To: <sip: CCS code@CCS domain name>; tag=32128  
+Content-Length: Byte length of message body  
+CSeq: 7 Message  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP media stream sender domain name or IP address  
+From: <sip: media stream sender code @ media stream sender domain name>;  
+tag=f569d024  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Notify>  
+<CmdType>MediaStatus</CmdType>  
+<SN>8</SN>  
+<DeviceID>008611010000041310000345</DeviceID>  
+<NotifyType>121</NotifyType>  
+</Notify>
+
+##### r) MESSAGE sip: media stream receiver code@ media stream receiver IP address port SIP/2.0
+
+From: <sip: CCS code@CCS domain name>; tag=e3719a0b  
+Contact: <sip: CCS code@CCS IP address port>  
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bfd0@172.20.16.4  
+Via: SIP/2.0/UDP media stream receiver domain name or IP address  
+To: <sip: media stream receiver code @ media stream receiver domain name>;  
+tag=949c43d7  
+Content-Length: Byte length of message body  
+CSeq: 7 Message  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Notify>  
+<CmdType>MediaStatus</CmdType>  
+<SN>8</SN>  
+<DeviceID>008611010000041310000345</DeviceID>  
+<NotifyType>121</NotifyType>  
+</Notify>
+
+##### s) SIP/2.0 200 OK
+
+From: <sip: CCS code@CCS domain name>; tag=e3719a0b  
+Contact: <sip: media stream receiver code@ media stream receiver IP address port>  
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bfd0@172.20.16.4  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+To: <sip: media stream receiver code @ media stream receiver domain name>;  
+tag=949c43d7  
+CSeq: 7 Message  
+Content-Length: Byte length of message body
+
+##### t) SIP/2.0 200 OK
+
+Via: SIP/2.0/UDP media stream sender domain name or IP address  
+From: <sip: media stream sender code @ media stream sender domain name>;  
+tag=f569d024  
+To: <sip: CCS code@CCS domain name>; tag=32128  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+CSeq: 7 Message  
+Content-Length: Byte length of message body
+
+- u) **BYE sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0**  
+ To: <sip: media stream sender code@ media stream sender domain name>;  
+ tag=949c43d7  
+ Content-Length: Byte length of message body  
+ CSeq: 2 BYE  
+ Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bdfd0@172.20.16.4  
+ Via: SIP/2.0/UDP media stream receiver domain name or IP address  
+ From: <sip: media stream receiver code@media stream receiver domain name>;  
+ tag=e3719a0b  
+ Max-Forwards: 70
+- v) **SIP/2.0 200 OK**  
+ Via: SIP/2.0/UDP media stream receiver domain name or IP address  
+ From: <sip: media stream receiver code@media stream receiver domain name>;  
+ tag=e3719a0b  
+ To: <sip: media stream sender code@ media stream sender domain name>;  
+ tag=949c43d7  
+ Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bdfd0@172.20.16.4  
+ CSeq: 2 BYE  
+ Content-Length: Byte length of message body
+- w) **BYE sip: MS code@MS domain name or IP address port SIP/2.0**  
+ Via: SIP/2.0/UDP CCS domain name or IP address  
+ From: <sip: CCS code@CCS domain name>; tag=02f283d7  
+ To: <sip: MS code@MS domain name>;tag=994072228  
+ Call-ID: wlss-294c2c6e-eea27828118c3b50449185980f4bdfd0@172.18.16.5  
+ Content-Length: Byte length of message body  
+ CSeq: 2 BYE  
+ Max-Forwards: 70
+- x) **SIP/2.0 200 OK**  
+ Via: SIP/2.0/UDP CCS domain name or IP address  
+ From: <sip: CCS code@CCS domain name>; tag=02f283d7  
+ To: <sip: MS code@MS domain name>;tag=994072228  
+ Call-ID: wlss-294c2c6e-eea27828118c3b50449185980f4bdfd0@172.18.16.5  
+ CSeq: 2 BYE  
+ Content-Length: Byte length of message body
+- y) **BYE sip: MS code@MS domain name or IP address port SIP/2.0**  
+ To: <sip: MS code@MS domain name>;tag=3094947605  
+ Content-Length: Byte length of message body  
+ CSeq: 2 BYE  
+ Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+ Via: SIP/2.0/UDP CCS domain name or IP address  
+ From: <sip: CCS code@CCS domain name>; tag=1ad9931d  
+ Max-Forwards: 70
+- z) **SIP/2.0 200 OK**  
+ Via: SIP/2.0/UDP CCS domain name or IP address  
+ From: <sip: CCS code@CCS domain name>; tag=1ad9931d  
+ To: <sip: MS code@MS domain name>;tag=3094947605  
+ Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+ CSeq: 2 BYE  
+ Content-Length: Byte length of message body
+- aa) **BYE sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0**
+
+```
+
+To: <sip: media stream sender code@ media stream sender domain name>;
+tag=32128
+Content-Length: Byte length of message body
+CSeq: 2 BYE
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>; tag=f569d024
+Max-Forwards: 70
+
+```
+
+##### ab) **SIP/2.0 200 OK**
+
+```
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>; tag=f569d024
+To: <sip: media stream sender code@ media stream sender domain name>;
+tag=32128
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5
+CSeq: 2 BYE
+Content-Length: Byte length of message body
+
+```
+
+#### 8.8.4.2 Examples of historical media file playback messages initiated by a third party unit
+
+##### a) **INVITE sip: MS code@MS domain name or IP address port SIP/2.0**
+
+```
+
+To: sip: MS code@MS domain name
+Content-Length: Byte length of message body
+Contact: <sip: CCS code@CCS IP address port>
+CSeq: 1 INVITE
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>; tag=1ad9931d
+Subject: Media stream sender ID: Sender's media stream serial number,
+media stream receiver ID: Receiver's media stream serial number
+Max-Forwards: 70
+
+```
+
+##### b) **SIP/2.0 200 OK**
+
+```
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>; tag=1ad9931d
+To: <sip: MS code@MS domain name>; tag=3094947605
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5
+CSeq: 1 INVITE
+Contact: <sip: MS code@MS domain name or IP address port>
+Content-Type: Application/SDP
+Content-Length: Byte length of message body
+v=0
+o=0086110100000002020000001 0 0 IN IP4 172.18.16.3
+s=##ms20091214
+c=IN IP4 172.18.16.3
+t=0 0
+m=video 6000 RTP/AVP 96 98 100
+a=recvonly
+a=rtpmap: 96 PS/90000
+a=rtpmap: 98 H264/90000
+a=rtpmap: 100 H265/90000
+
+```
+
+##### c) **INVITE sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0**
+
+```
+
+To: sip: media stream sender code@ media stream sender domain name
+Content-Length: Byte length of message body
+Contact: <sip: CCS code@CCS IP address port>
+CSeq: 1 INVITE
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>; tag=f569d024
+
+```
+
+```
+
+Content-Type: Application/SDP
+Subject: Media stream sender ID: Sender's media stream serial number,
+media stream receiver ID: Receiver's media stream serial number
+Max-Forwards: 70
+v=0
+o=008611010000002020000001 0 0 IN IP4 172.18.16.3
+s=Playback
+u=008611010000041310000345:3
+c=IN IP4 172.18.16.3
+t=1288625085 1288625871
+m=video 6000 RTP/AVP 96 98 100
+a=recvonly
+a=rtpmap: 96 PS/90000
+a=rtpmap: 98 H264/90000
+a=rtpmap: 100 H265/90000
+y=1100000000
+
+```
+
+##### **d) SIP/2.0 200 OK**
+
+```
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>; tag=f569d024
+To: <sip: media stream sender code@ media stream sender domain name>;
+tag=32128
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5
+CSeq: 1 INVITE
+Contact: <sip: media stream sender code@ media stream sender IP address
+port>
+Content-Type: Application/SDP
+Content-Length: Byte length of message body
+v=0
+o=008611010000041110000044 0 0 IN IP4 172.24.18.44
+s=Playback
+c=IN IP4 172.24.18.44
+t=1288625085 1288625871
+m=video 9412 RTP/AVP 96
+a=sendonly
+a=rtpmap: 96 PS/90000
+y=1100000000
+
+```
+
+##### **e) ACK sip: MS code@MS domain name or IP address port SIP/2.0**
+
+```
+
+To: <sip: MS code@MS domain name>;tag=3094947605
+Content-Length: Byte length of message body
+CSeq: 1 ACK
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>; tag=1ad9931d
+Content-Type: Application/SDP
+Max-Forwards: 70
+v=0
+o=008611010000041110000044 0 0 IN IP4 172.24.18.44
+s=Playback
+c=IN IP4 172.24.18.44
+t=1288625085 128862587
+m=video 9412 RTP/AVP 96
+a=sendonly
+a=rtpmap: 96 PS/90000
+y=1100000000
+
+```
+
+##### **f) ACK sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0**
+
+```
+
+To: <sip: media stream sender code@ media stream sender domain name>;
+tag=32128
+
+```
+
+Content-Length: Byte length of message body  
+ CSeq: 1 ACK  
+ Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+ Via: SIP/2.0/UDP CCS domain name or IP address  
+ From: <sip: CCS code@CCS domain name>; tag=f569d024  
+ Max-Forwards: 70
+
+##### **g) INVITE sip: media stream receiver code@ media stream receiver domain name or IP address port SIP/2.0**
+
+To: sip: media stream receiver code @ media stream receiver domain name  
+ Content-Length: Byte length of message body  
+ Contact: <sip: CCS code@CCS IP address port>  
+ CSeq: 1 INVITE  
+ Call-ID: wlss-e862d62c-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5  
+ Via: SIP/2.0/UDP CCS domain name or IP address  
+ From: <sip: CCS code@CCS domain name>; tag=8338d6ac  
+ Subject: Media stream sender ID: Sender's media stream serial number,  
+ media stream receiver ID: Receiver's media stream serial number  
+ Max-Forwards: 70
+
+##### **h) SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+ From: <sip: CCS code@CCS domain name>; tag=8338d6ac  
+ To: <sip: media stream receiver code @ media stream receiver domain name>;  
+ tag=41  
+ Call-ID: wlss-e862d62c-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5  
+ CSeq: 1 INVITE  
+ Contact: <sip: media stream receiver code@ media stream receiver IP  
+ address port>  
+ Content-Type: Application/SDP  
+ Content-Length: Byte length of message body  
+ v=0  
+ o=008611010000003001000001 0 0 IN IP4 172.18.16.126  
+ s=Playback  
+ c=IN IP4 172.18.16.126  
+ t=1288625085 128862587  
+ m=video 9010 RTP/AVP 96  
+ a=recvonly  
+ a=rtpmap:96 PS/90000
+
+##### **i) INVITE sip: MS code@MS domain name or IP address port SIP/2.0**
+
+To: sip: MS code@MS domain name  
+ Content-Length: Byte length of message body  
+ Contact: <sip: CCS code@CCS IP address port>  
+ CSeq: 1 INVITE  
+ Call-ID: wlss-19677597-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5  
+ Via: SIP/2.0/UDP CCS domain name or IP address  
+ From: <sip: CCS code@CCS domain name>; tag=39a741c5  
+ Content-Type: Application/SDP  
+ Subject: Media stream sender ID: Sender's media stream serial number,  
+ media stream receiver ID: Receiver's media stream serial number  
+ Max-Forwards: 70  
+ v=0  
+ o=008611010000003001000001 0 0 IN IP4 172.18.16.126  
+ s=Playback  
+ c=IN IP4 172.18.16.126  
+ t=1288625085 128862587  
+ m=video 9010 RTP/AVP 96  
+ a=recvonly  
+ a=rtpmap:96 PS/90000  
+ y=1100000000
+
+- j) **SIP/2.0 200 OK**  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=39a741c5  
+To: <sip: MS code@MS domain name>; tag=3243635917  
+Call-ID: wlss-19677597-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5  
+CSeq: 1 INVITE  
+Contact: <sip: MS code@MS domain name or IP address port>  
+Content-Type: Application/SDP  
+Content-Length: Byte length of message body  
+v=0  
+o=00861101000000020200000001 0 0 IN IP4 172.18.16.3  
+s=Playback  
+c=IN IP4 172.18.16.3  
+t= 1288625085 128862587  
+m=video 6000 RTP/AVP 96  
+a=sendonly  
+a=rtpmap: 96 PS/90000  
+y=1100000000
+- k) **ACK sip: media stream receiver code@ media stream receiver domain name or IP address port SIP/2.0**  
+To: <sip: media stream receiver code @ media stream receiver domain name>;  
+tag=41  
+Content-Length: Byte length of message body  
+CSeq: 1 ACK  
+Call-ID: wlss-e862d62c-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=8338d6ac  
+Content-Type: Application/SDP  
+Max-Forwards: 70  
+v=0  
+o=00861101000000020200000001 0 0 IN IP4 172.18.16.3  
+s=Playback  
+c=IN IP4 172.18.16.3  
+t=1288625085 128862587  
+m=video 6000 RTP/AVP 96  
+a=sendonly  
+a=rtpmap: 96 PS/90000  
+y=1100000000
+- l) **ACK sip: MS code@MS domain name or IP address port SIP/2.0**  
+To: <sip: MS code@MS domain name>; tag=3243635917  
+Content-Length: Byte length of message body  
+CSeq: 1 ACK  
+Call-ID: wlss-19677597-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=39a741c5  
+Max-Forwards: 70
+- m) **INFO sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0**  
+To: <sip: media stream sender code@ media stream sender domain name>;  
+tag=32128  
+Content-Length: Byte length of message body  
+CSeq: 6 INFO  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=f569d024  
+Content-Type: Application/EMCS
+
+Max-Forwards: 70
+
+PLAY RTSP/2.0
+
+CSeq: 5
+
+Scale: 1.0
+
+Range: npt=196-
+
+##### **n) SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+
+From: <sip: CCS code@CCS domain name>; tag=f569d024
+
+To: <sip: media stream sender code@ media stream sender domain name>;
+
+tag=32128
+
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5
+
+CSeq: 6 INFO
+
+Content-Length: Byte length of message body
+
+##### **o) MESSAGE sip: CCS code @ CCS domain name or IP address port SIP/2.0**
+
+To: <sip: CCS code@CCS domain name>; tag=32128
+
+Content-Length: Byte length of message body
+
+CSeq: 7 Message
+
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+
+From: <sip: media stream sender code@ media stream sender domain name>;
+
+tag=f569d024
+
+Max-Forwards: 70
+
+<?xml version="1.0"?>
+
+<Notify>
+
+<CmdType>MediaStatus</CmdType>
+
+<SN>8</SN>
+
+<DeviceID>008611010000041310000345</DeviceID>
+
+<NotifyType>121</NotifyType>
+
+</Notify>
+
+##### **p) SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+
+From: <sip: media stream sender code@ media stream sender domain name>;
+
+tag=f569d024
+
+To: <sip: CCS code@CCS domain name>; tag=32128
+
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5
+
+CSeq: 7 Message
+
+Content-Length: Byte length of message body
+
+##### **q) BYE sip: media stream receiver code@ media stream receiver domain name or IP address port SIP/2.0**
+
+To: <sip: media stream receiver code @ media stream receiver domain name>;  
+tag=41
+
+Content-Length: Byte length of message body
+
+CSeq: 2 BYE
+
+Call-ID: wlss-e862d62c-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+
+From: <sip: CCS code@CCS domain name>; tag=8338d6ac
+
+Max-Forwards: 70
+
+##### **r) SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+
+From: <sip: CCS code@CCS domain name>; tag=8338d6ac
+
+To: <sip: media stream receiver code @ media stream receiver domain name>;
+
+tag=41
+
+Call-ID: wlss-e862d62c-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5
+
+CSeq: 2 BYE
+
+Content-Length: Byte length of message body
+
+##### s) BYE sip: MS code@MS domain name or IP address port SIP/2.0
+
+To: <sip: MS code@MS domain name>;tag=3243635917  
+Content-Length: Byte length of message body  
+CSeq: 2 BYE  
+Call-ID: wlss-19677597-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=39a741c5  
+Max-Forwards: 70
+
+##### t) SIP/2.0 200 OK
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=39a741c5  
+To: <sip: MS code@MS domain name>; tag=3243635917  
+Call-ID: wlss-19677597-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5  
+CSeq: 2 BYE  
+Content-Length: Byte length of message body
+
+##### u) BYE sip: MS code@MS domain name or IP address port SIP/2.0
+
+To: <sip: MS code@MS domain name>;tag=3094947605  
+Content-Length: Byte length of message body  
+CSeq: 2 BYE  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=1ad9931d  
+Max-Forwards: 70
+
+##### v) SIP/2.0 200 OK
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=1ad9931d  
+To: <sip: MS code@MS domain name>;tag=3094947605  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+CSeq: 2 BYE  
+Content-Length: Byte length of message body
+
+##### w) BYE sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0
+
+To: <sip: media stream sender code@ media stream sender domain name>;tag=32128  
+Content-Length: Byte length of message body  
+CSeq: 2 BYE  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=f569d024  
+Max-Forwards: 70
+
+##### x) SIP/2.0 200 OK
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=f569d024  
+To: <sip: media stream sender code@ media stream sender domain name>;tag=32128  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+CSeq: 2 BYE  
+Content-Length: Byte length of message body
+
+## **8.9 Historical media file download**
+
+### **8.9.1 Basic requirements**
+
+After the CCS receives the historical media file download request sent by the media stream receiver, it sends the media file download commands to the media stream sender, then the media stream sender transmits the video stream to the media stream receiver through RTP, and the media stream receiver saves the media stream as media files directly.
+
+The media stream receiver or the CCS can acquire the download sending speed supported by the media stream sender through such means of configuration query, and carry the specified download speed in the SDP message body of the request (see clause 7.7). The media stream sender can extend to carry the size parameter of the file to be downloaded in the SDP message body of a 200 OK response corresponding to the Invite request (see clause 7.7), so as to facilitate the calculation of download progress by the media stream receiver; when the media stream sender is unable to provide the file size parameter, the media stream receiver shall support the calculation of download progress according to the time acquired in the code stream.
+
+The historical media file download should support the media stream keepalive mechanism specified in clause 7.4.
+
+### 8.9.2 Signalling process
+
+#### 8.9.2.1 Initiation by media stream receiver
+
+For the media file download signalling flow initiated by media stream receiver, see Figure 8-14.
+
+![Sequence diagram showing the signalling flow for a historical media file download initiated by the media stream receiver. The diagram involves four lifelines: Media stream receiver, CCS, MS, and Media stream sender. The process involves multiple SIP messages (Invite, 200 OK, ACK, BYE) and two 'Historical media stream' transfers.](d04c50badc78d5ba47bf4e352af4a754_img.jpg)
+
+```
+sequenceDiagram
+    participant MS as Media stream sender
+    participant MR as Media stream receiver
+    participant CCS as CCS
+    participant MS2 as MS
+
+    Note right of MS: Historical media stream
+    MR->>CCS: 1: Invite (with SDP)
+    CCS->>MS2: 2: Invite
+    MS2->>CCS: 3: 200 OK (with SDP)
+    CCS->>MS: 4: Invite (with SDP)
+    MS->>CCS: 5: 200 OK (with SDP)
+    CCS->>MS2: 6: ACK (with SDP)
+    MS2->>MS: 7: ACK
+    Note left of MS2: Historical media stream
+    CCS->>MS2: 8: Invite (with SDP)
+    MS2->>CCS: 9: 200 OK (with SDP)
+    CCS->>MR: 10: 200 OK (with SDP)
+    MR->>CCS: 11: ACK
+    CCS->>MS2: 12: ACK
+    Note left of MS2: Historical media stream
+    MS->>CCS: 13: Message (File sending complete)
+    CCS->>MR: 14: Message (File sending complete)
+    MR->>CCS: 15: 200 OK
+    MS->>MS2: 16: 200 OK
+    MR->>CCS: 17: BYE
+    CCS->>MR: 18: 200 OK
+    CCS->>MS2: 19: BYE
+    MS2->>CCS: 20: 200 OK
+    CCS->>MS2: 21: BYE
+    MS2->>CCS: 22: 200 OK
+    CCS->>MS: 23: BYE
+    MS->>CCS: 24: 200 OK
+```
+
+Sequence diagram showing the signalling flow for a historical media file download initiated by the media stream receiver. The diagram involves four lifelines: Media stream receiver, CCS, MS, and Media stream sender. The process involves multiple SIP messages (Invite, 200 OK, ACK, BYE) and two 'Historical media stream' transfers.
+
+H.627(20)\_F8-14
+
+**Figure 8-14 – Signalling flow of historical media file download initiated by media stream receiver**
+
+In Figure 8-14, the media stream receiver includes the CU or the other VSS. The media stream sender includes the PU or the other VSS.
+
+In Figure 8-14:
+
+signals 1, 8, 9, 10, 11 and 12 constitute the process of establishing the media link between the media stream receiver and the MS with the B2BUA method by the CCS, after receiving the media stream receiver call request;
+
+signals 2–7 constitute the process of establishing the media link between the MS and the media stream sender through the third-party call control by the CCS;
+
+signals 13–16 constitute the process of sending the download completion notification message to the media stream receiver by media stream sender after download ends;
+
+signals 17–20 constitute the process of disconnecting the media link between the media stream receiver and the MS; and
+
+signals 21–24 constitute the process of disconnecting the media link between the MS and the media stream sender by the CCS.
+
+The signalling flow description is as follows.
+
+- The media stream receiver sends the Invite message to the CCS, and the message header field carries the subject field, showing such parameters as video source ID of real-time media stream, sender media stream SN, media stream receiver ID and receiver media stream SN; the s field in the SDP message is "Download", representing file download; the u field represents the download channel ID and the download type; the t field represents the download time period; the extendable a field carries the download speed parameter specifying the sending media speed of the download device in this download; if the speed parameter is not carried, the default speed is 1.
+- After the CCS receives the Invite request, the media connection between the MS and the media stream sender is established through third-party call control. The Invite message is sent to the MS, and this message does not carry the SDP message body.
+- After the MS receives the Invite request of the CCS, it replies with a 200 OK response, carrying the SDP message body in which the IP, port, media format, etc. of the media stream received by the MS are described.
+- After the CCS receives the 200 OK response sent back from the MS, it sends the Invite request to the media stream sender; the request carries the 200 OK response message body sent by the MS in the message 3, and the s field is "Download", representing file download; the u field represents the download channel ID and download type; the t field represents the download time period; the y field is added to describe the SSRC value and f field for the media parameters; the extendable a field carries the download speed parameter, which transmits the speed parameter to the device.
+- After the media stream sender receives the Invite request from the CCS, it replies with the 200 OK response, carrying the SDP message body in which the IP, port, media format, SSRC field, etc. of the media stream sent by the media stream sender are described; the extendable a field carries the file size parameter.
+- After the CCS receives the 200 OK response sent back from the media stream sender, it sends an ACK request to the MS, which carries the 200 OK response message body sent by the media stream sender in message 5, and the establishment process of the Invite session with the MS is finished.
+- After the CCS receives the 200 OK response sent back from the media stream sender, it sends an ACK request to the media stream sender, which does not carry a message body, and the establishment process of the Invite session with the media stream sender is finished.
+- Upon the completion of third-party call control, the CCS establishes the media connection between the media stream receiver and the MS with the B2BUA method, adds the SSRC value to message 1 and forwards it to the MS.
+- After the MS receives the Invite request, it replies with the 200 OK response, carrying the SDP message body in which the IP, port, media format, SSRC value, etc. of the media stream sent by the MS are described.
+
+- The CCS forwards message 9 to the media stream receiver, and the extendable a field carries the file size parameter.
+- After the media stream receiver receives the 200 OK response, it replies with the ACK message, and the establishment process of the Invite session with CCS is finished.
+- The CCS forwards message 11 to the MS, and the establishment process of the Invite session with the MS is finished.
+- The media stream sender sends the session MESSAGE at the end of file playback, notifying the CCS that the playback has ended; for the message body format, see the media notifications in clause A.2.5 c).
+- The CCS forwards message 17 to the media stream receiver after receiving the message.
+- After the media stream receiver receives message 18, it replies with the 200 OK response, and the link disconnecting process is initiated.
+- The CCS forwards message 19 to the media stream sender.
+- The media stream receiver sends the BYE message to the CCS, and the Invite session with the media stream receiver established by messages 1, 10 and 11 is disconnected.
+- After the CCS receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- After the CCS receives the BYE message, it sends the BYE message to the MS, and the Invite session with the MS established by messages 8, 9 and 12 is disconnected.
+- After the MS receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- The CCS sends the BYE message to the MS, and the Invite session with the MS established by messages 2, 3 and 6 is disconnected.
+- After the MS receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- The CCS sends the BYE message to the media stream sender, and the Invite session with the media stream sender established by messages 4, 5 and 7 is disconnected.
+- After the media stream sender receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+
+See the examples of historical media file download message initiated by the media stream receiver in clause 8.9.4.1.
+
+#### 8.9.2.2 Third-party call control
+
+For the historical media file download signalling flow initiated by a third-party unit, see Figure 8-15.
+
+![Sequence diagram showing the signalling flow of historical media file download initiated by a third-party unit. The diagram involves four lifelines: Media stream receiver, CCS, MS, and Media stream sender. The process involves establishing media links between the MS and both the receiver and sender via the CCS, followed by the download of a historical media stream and subsequent teardown.](3d1817e8551f9c226a5f561108d3b3f9_img.jpg)
+
+```
+sequenceDiagram
+    participant MS as MS
+    participant CCS as CCS
+    participant MSender as Media stream sender
+    participant MReceiver as Media stream receiver
+
+    Note right of MS: Historical media stream
+    Note left of MReceiver: Historical media stream
+
+    CCS->>MS: 1: Invite
+    MS-->>CCS: 2: 200 OK (with SDP)
+    CCS->>MSender: 3: Invite (with SDP)
+    MSender-->>CCS: 4: 200 OK (with SDP)
+    CCS->>MS: 5: ACK (with SDP)
+    CCS->>MSender: 6: ACK
+    MSender->>MS: Historical media stream
+    CCS->>MReceiver: 7: Invite
+    MReceiver-->>CCS: 8: 200 OK (with SDP)
+    CCS->>MS: 9: Invite (with SDP)
+    MS-->>CCS: 10: 200 OK (with SDP)
+    MReceiver-->>CCS: 11: ACK (with SDP)
+    CCS->>MS: 12: ACK
+    MS->>MReceiver: Historical media stream
+    MSender->>CCS: 13: Message (File to end)
+    MSender-->>CCS: 14: 200 OK
+    MReceiver->>CCS: 15: BYE
+    CCS-->>MReceiver: 16: 200 OK
+    CCS->>MS: 17: BYE
+    MS-->>CCS: 18: 200 OK
+    CCS->>MS: 19: BYE
+    MS-->>CCS: 20: 200 OK
+    CCS->>MSender: 21: BYE
+    MSender-->>CCS: 22: 200 OK
+```
+
+H.627(20)\_F8-15
+
+Sequence diagram showing the signalling flow of historical media file download initiated by a third-party unit. The diagram involves four lifelines: Media stream receiver, CCS, MS, and Media stream sender. The process involves establishing media links between the MS and both the receiver and sender via the CCS, followed by the download of a historical media stream and subsequent teardown.
+
+**Figure 8-15 – Signalling flow of historical media file download initiated by a third-party unit**
+
+In Figure 8-15, the media stream receiver includes CU or the other VSS. Media stream sender includes the PU or the other VSS.
+
+In Figure 8-15:
+
+signals 1–6 constitute the process of establishing the media link between the MS and the media stream sender through the third-party call control by the CCS;
+
+signals 7–12 constitute the process of establishing the media link between the media stream receiver and the MS through the third-party call control by the CCS;
+
+signals 13-14 constitute the process of sending the download completion notification message to the media stream receiver by media stream sender after download ends;
+
+signals 15–18 constitute the process of disconnecting the media link between the media stream receiver and MS;
+
+signals 19–22 constitute the process of disconnecting the media link between the MS and the media stream sender.
+
+The signalling flow description is as follows:
+
+- The CCS sends the Invite message to the MS, and this message does not carry the SDP message body.
+- After the MS receives the Invite request of the CCS, it replies with a 200 OK response, carrying the SDP message body in which the IP, port, media format, etc. of the media stream received by the MS are described.
+- After the CCS receives the 200 OK response sent back from the MS, it sends the Invite request to the media stream sender, which carries the 200 OK response message body sent by the MS in message 2, and the s field is "Download", representing download; the u field represents the download channel ID and the download video type; the t field represents the download time period; the y field is added to describe the SSRC value and f field for media parameter; the extendable a field carries the download speed parameter specifying the sending media speed of the download device in this download; if the speed parameter is not carried, the default speed is 1.
+- After the media stream sender receives the Invite request of the CCS, it replies with the 200 OK response, carrying the SDP message body in which the IP, port, media format, SSRC field, etc. of the media stream sent by the media stream sender are described; the extendable a field carries the file size parameter.
+- After the CCS receives the 200 OK response sent back from the media stream sender, it sends an ACK request to the MS, which carries the 200 OK response message body sent by the media stream sender in message 4, and the establishment process of the Invite session with the MS is finished.
+- After the CCS receives the 200 OK response sent back from the media stream sender, it sends an ACK request to the media stream sender, which does not carry a message body, and the establishment process of the Invite session with the media stream sender is finished.
+- The CCS sends the Invite message to the media stream receiver, and this message does not carry the SDP message body.
+- After the media stream receiver receives the Invite request of the CCS, it replies with the 200 OK response, carrying the SDP message body in which the IP, port, media format, etc. of the media stream received by the media stream receiver are described.
+- After the CCS receives the 200 OK response sent back from the media stream receiver, it sends the Invite request to the MS, which carries the 200 OK response message body sent by the media stream receiver in message 8, and the s field is "Playback", representing historical playback; the y field is added to describe the SSRC value.
+- After the MS receives the Invite request of the CCS, it replies with the 200 OK response, carrying the SDP message body in which the IP, port, media format, SSRC field, etc. of the media stream sent by the MS are described.
+- After the CCS receives the 200 OK response sent back from the MS, it sends an ACK request to the MS, which carries the 200 OK response message body sent by the MS in message 10, and the establishment process of the Invite session with the media stream receiver is finished, and the extendable a field carries the file size parameter.
+- After the CCS receives the 200 OK response sent back from the MS, it sends an ACK request to the MS, which does not carry a message body, and the establishment process of the Invite session with the MS is finished.
+
+- The media stream sender sends the session MESSAGE at the end of file playback, notifying the CCS that the playback has ended; for the message body format, see the media notifications in clause A.2.5 c).
+- After the CCS receives the MESSAGE, it replies with the 200 OK response, and the link disconnection process is initiated.
+- The CCS sends the BYE message to the media stream receiver, and the Invite session with the media stream receiver established by messages 7, 8 and 11 is disconnected.
+- After the media stream receiver receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- The CCS sends the BYE message to the MS, and the Invite session with the MS established by messages 9, 10 and 12 is disconnected.
+- After the MS receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- The CCS sends the BYE message to the MS, and the Invite session with the MS established by messages 1, 2 and 5 is disconnected.
+- After the MS receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- The CCS sends the BYE message to the media stream sender, and the Invite session with the media stream sender established by messages 3, 4 and 6 is disconnected.
+- After the media stream sender receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+
+See the examples of historical media file download messages initiated by a third-party unit in clause 8.9.4.2.
+
+### 8.9.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.
+
+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 is Content-type: Application/SDP.
+
+The request and response message bodies carried in the historical media download process shall be defined in the SDP format. For a detailed description related to SDP, see [IETF RFC 4566].
+
+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 INVITE request acquires the historical media in the form of time periods.
+
+The information positioning the historical media data is carried in the message body in the SDP format, and shall include the device name and time period information, specified as follows.
+
+- The media stream receiver shall include the u line (see clause 5.5 of [IETF RFC 4566]) in the message body in the SDP format, indicating the URI of the historical media files; for specific definitions, see clause 7.7.
+- The media stream receiver shall include the t line (see clause 5.9 of [IETF RFC 4566]) in the message body in the SDP format, and the start time and the end time of the t line shall constitute the time period information for retrieving the historical media data.
+
+### 8.9.4 Examples of messages
+
+#### 8.9.4.1 Examples of historical media file download messages initiated by media stream receiver
+
+##### a) INVITE sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0
+
+To: sip: media stream sender code@ media stream sender domain name  
+Content-Length: Byte length of message body  
+Contact: <sip: media stream receiver code@ media stream receiver IP address port>  
+CSeq: 1 INVITE  
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bdfd0@172.20.16.4  
+Via: SIP/2.0/UDP media stream receiver domain name or IP address  
+From: <sip: media stream receiver code @ media stream receiver domain name>; tag=e3719a0b  
+Subject: Media stream sender ID: Sender's media stream serial number, media stream receiver ID: Receiver's media stream serial number  
+Content-Type: Application/SDP  
+Max-Forwards: 70  
+v=0  
+o=008611010600002020000001 0 0 IN IP4 172.20.16.3  
+s=Download  
+u=008611010000041310000345:3  
+c=IN IP4 172.20.16.3  
+t=1288625085 1288625871  
+m=video 6000 RTP/AVP 96 98 100  
+a=recvonly  
+a=rtpmap: 96 PS/90000  
+a=rtpmap: 98 H264/90000  
+a=rtpmap: 100 H265/90000  
+a=downloadspeed: 4
+
+##### b) INVITE sip: MS code@MS domain name or IP address port SIP/2.0
+
+To: sip: MS code@MS domain name  
+Content-Length: Byte length of message body  
+Contact: <sip: CCS code@CCS IP address port>  
+CSeq: 1 INVITE  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=lad9931d  
+Subject: Media stream sender ID: Sender's media stream serial number, media stream receiver ID: Receiver's media stream serial number  
+Max-Forwards: 70
+
+##### c) SIP/2.0 200 OK
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=lad9931d  
+To: <sip: MS code@MS domain name>; tag=3094947605  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+CSeq: 1 INVITE  
+Contact: <sip: MS code@MS domain name or IP address port>  
+Content-Type: Application/SDP  
+Content-Length: Byte length of message body  
+v=0  
+o=008611010000002020000001 0 0 IN IP4 172.18.16.3  
+s=Download  
+c=IN IP4 172.18.16.3  
+t=1288625085 1288625871  
+m=video 6000 RTP/AVP 96 98 100  
+a=recvonly  
+a=rtpmap: 96 PS/90000
+
+a=rtpmap: 98 H264/90000  
+a=rtpmap: 100 H265/90000
+
+##### d) INVITE sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0
+
+To: sip: media stream sender code@ media stream sender domain name  
+Content-Length: Byte length of message body  
+Contact: <sip: CCS code@CCS IP address port>  
+CSeq: 1 INVITE  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=f569d024  
+Content-Type: Application/SDP  
+Subject: Media stream sender ID: Sender's media stream serial number,  
+media stream receiver ID: Receiver's media stream serial number  
+Max-Forwards: 70  
+v=0  
+o=008611010000002020000001 0 0 IN IP4 172.18.16.3  
+s=Download  
+u=008611010000041310000345:3  
+c=IN IP4 172.18.16.3  
+t=1288625085 1288625871  
+m=video 6000 RTP/AVP 96 98 100  
+a=recvonly  
+a=rtpmap: 96 PS/90000  
+a=rtpmap: 98 H264/90000  
+a=rtpmap: 100 H265/90000  
+a=downloadspeed: 4  
+y=1000000001
+
+##### e) SIP/2.0 200 OK
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=f569d024  
+To: <sip: media stream sender code@ media stream sender domain name>;  
+tag=32128  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+CSeq: 1 INVITE  
+Contact: <sip: media stream sender code@ media stream sender IP address  
+port>  
+Content-Type: Application/SDP  
+Content-Length: Byte length of message body  
+v=0  
+o=008611010000041110000044 0 0 IN IP4 172.24.18.44  
+s=Download  
+c=IN IP4 172.24.18.44  
+t=1288625085 1288625871  
+m=video 8412 RTP/AVP 96  
+a=sendonly  
+a=rtpmap: 96 PS/90000  
+a=filesize: 10485760  
+y=1000000001
+
+##### f) ACK sip: MS code@MS domain name or IP address port SIP/2.0
+
+To: <sip: MS code@MS domain name>; tag=3094947605  
+Content-Length: Byte length of message body  
+CSeq: 1 ACK  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=1ad9931d  
+Content-Type: Application/SDP  
+Max-Forwards: 70
+
+```
+
+v=0
+o=0086110100000411100000044 0 0 IN IP4 172.24.18.44
+s=Download
+c=IN IP4 172.24.18.44
+t=1288625085 1288625871
+m=video 8412 RTP/AVP 96
+a=sendonly
+a=rtpmap: 96 PS/90000
+y=1000000001
+
+```
+
+##### g) **ACK sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0**
+
+```
+
+To: <sip: media stream sender code@ media stream sender domain name>;
+tag=32128
+Content-Length: Byte length of message body
+CSeq: 1 ACK
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>; tag=f569d024
+Max-Forwards: 70
+
+```
+
+##### h) **INVITE sip: MS code@MS domain name or IP address port SIP/2.0**
+
+```
+
+To: sip: MS code@MS domain name
+Content-Length: Byte length of message body
+Contact: <sip: CCS code@CCS IP address port>
+CSeq: 1 INVITE
+Call-ID: wlss-294c2c6e-eea27828118c3b50449185980f4bdfd0@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>; tag=02f283d7
+Subject: Media stream sender ID: Sender's media stream serial number,
+media stream receiver ID: Receiver's media stream serial number
+Content-Type: Application/SDP
+Max-Forwards: 70
+v=0
+o=0086110106000020200000001 0 0 IN IP4 172.18.16.3
+s=Download
+c=IN IP4 172.18.16.3
+t=1288625085 1288625871
+m=video 6000 RTP/AVP 96 98 100
+a=recvonly
+a=rtpmap: 96 PS/90000
+a=rtpmap: 98 H264/90000
+a=rtpmap: 100 H265/90000
+y=1000000001
+
+```
+
+##### i) **SIP/2.0 200 OK**
+
+```
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>; tag=02f283d7
+To: <sip: MS code@MS domain name>;tag=994072228
+Call-ID: wlss-294c2c6e-eea27828118c3b50449185980f4bdfd0@172.18.16.5
+CSeq: 1 INVITE
+Contact: <sip: MS code@MS IP address port>
+Content-Type: Application/SDP
+Content-Length: Byte length of message body
+v=0
+o=0086110100000020200000001 0 0 IN IP4 172.18.16.1
+s=Download
+c=IN IP4 172.18.16.1
+t=1288625085 1288625871
+m=video 6000 RTP/AVP 96
+a=sendonly
+
+```
+
+a=rtpmap: 96 PS/90000  
+y=1000000001
+
+##### j) SIP/2.0 200 OK
+
+To: <sip: media stream sender code@ media stream sender domain name>;  
+tag=949c43d7  
+Contact: <sip: media stream sender code@ media stream sender IP address  
+port>  
+Content-Length: Byte length of message body  
+CSeq: 1 INVITE  
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bdfd0@172.20.16.4  
+Via: SIP/2.0/UDP media stream receiver domain name or IP address  
+From: <sip: media stream receiver code @ media stream receiver domain  
+name>; tag=e3719a0b  
+Content-Type: Application/SDP  
+v=0  
+o=008611010000002020000001 0 0 IN IP4 172.18.16.1  
+s=Download  
+c=IN IP4 172.18.16.1  
+t=1288625085 1288625871  
+m=video 6000 RTP/AVP 96  
+a=sendonly  
+a=rtpmap: 96 PS/90000  
+a=filesize: 10485760  
+y=1000000001
+
+##### k) ACK sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0
+
+To: <sip: media stream sender code@ media stream sender domain name>;  
+tag=949c43d7  
+Content-Length: Byte length of message body  
+CSeq: 1 ACK  
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bdfd0@172.20.16.4  
+Via: SIP/2.0/UDP media stream receiver domain name or IP address  
+From: <sip: media stream receiver code @ media stream receiver domain  
+name>; tag=e3719a0b  
+Max-Forwards: 70
+
+##### l) ACK sip: MS code@MS domain name or IP address port SIP/2.0
+
+To: <sip: MS code@MS domain name>;tag=994072228  
+Content-Length: Byte length of message body  
+CSeq: 1 ACK  
+Call-ID: wlss-294c2c6e-eea27828118c3b50449185980f4bdfd0@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=02f283d7  
+Max-Forwards: 70
+
+##### m) MESSAGE sip: CCS code@CCS domain name or IP address port SIP/2.0
+
+To: <sip: CCS code@CCS domain name>; tag=32128  
+Content-Length: Byte length of message body  
+CSeq: 7 Message  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP media stream sender domain name or IP address  
+From: <sip: media stream sender code @ media stream sender domain name>;  
+tag=f569d024  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Notify>  
+<CmdType>MediaStatus</CmdType>  
+<SN>8</SN>  
+<DeviceID>008611010000041310000345</DeviceID>
+
+```
+<NotifyType>121</NotifyType>
+</Notify>
+```
+
+##### n) MESSAGE sip: media stream receiver code@target IP address port SIP/2.0
+
+```
+From: <sip: CCS code@CCS domain name>; tag=e3719a0b
+Contact: <sip: CCS code@CCS IP address port>
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bdfd0@172.20.16.4
+Via: SIP/2.0/UDP media stream receiver domain name or IP address
+To: <sip: media stream receiver code @ media stream receiver domain name>;
+tag=949c43d7
+Content-Length: Byte length of message body
+CSeq: 7 Message
+Max-Forwards: 70
+<?xml version="1.0"?>
+<Notify>
+<CmdType>MediaStatus</CmdType>
+<SN>8</SN>
+<DeviceID>008611010000041310000345</DeviceID>
+<NotifyType>121</NotifyType>
+</Notify>
+```
+
+##### o) SIP/2.0 200 OK
+
+```
+From: <sip: CCS code@CCS domain name>; tag=e3719a0b
+Contact: <sip: media stream receiver code@ media stream receiver IP
+address port>
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bdfd0@172.20.16.4
+Via: SIP/2.0/UDP CCS domain name or IP address
+To: <sip: media stream receiver code @ media stream receiver domain name>;
+tag=949c43d7
+CSeq: 7 Message
+Content-Length: Byte length of message body
+```
+
+##### p) SIP/2.0 200 OK
+
+```
+Via: SIP/2.0/UDP media stream receiver domain name or IP address
+From: <sip: media stream sender code @receiver domain name>; tag=f569d024
+To: <sip: CCS code@CCS domain name>; tag=32128
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5
+CSeq: 7 Message
+Content-Length: Byte length of message body
+```
+
+##### q) BYE sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0
+
+```
+To: <sip: media stream sender code@ media stream sender domain name>;
+tag=949c43d7
+Content-Length: Byte length of message body
+CSeq: 2 BYE
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bdfd0@172.20.16.4
+Via: SIP/2.0/UDP media stream receiver domain name or IP address
+From: <sip: media stream receiver code @receiver domain name>;
+tag=e3719a0b
+Max-Forwards: 70
+```
+
+##### r) SIP/2.0 200 OK
+
+```
+Via: SIP/2.0/UDP media stream receiver domain name or IP address
+From: <sip: media stream receiver code @ media stream receiver domain
+name>; tag=e3719a0b
+To: <sip: media stream sender code@ media stream sender domain name>;
+tag=949c43d7
+Call-ID: wlss-f7c53b46-eea27828118c3b50449185980f4bdfd0@172.20.16.4
+CSeq: 2 BYE
+```
+
+Content-Length: Byte length of message body
+
+##### s) BYE sip: MS code@MS domain name or IP address port SIP/2.0
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=02f283d7  
+To: <sip: MS code@MS domain name> ;tag=994072228  
+Call-ID: wlss-294c2c6e-eea27828118c3b50449185980f4bdfd0@172.18.16.5  
+Content-Length: Byte length of message body  
+CSeq: 2 BYE  
+Max-Forwards: 70
+
+##### t) SIP/2.0 200 OK
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=02f283d7  
+To: <sip: MS code@MS domain name>; tag=994072228  
+Call-ID: wlss-294c2c6e-eea27828118c3b50449185980f4bdfd0@172.18.16.5  
+CSeq: 2 BYE  
+Content-Length: Byte length of message body
+
+##### u) BYE sip: MS code@MS domain name or IP address port SIP/2.0
+
+To: <sip: MS code@MS domain name>; tag=3094947605  
+Content-Length: Byte length of message body  
+CSeq: 2 BYE  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=1ad9931d  
+Max-Forwards: 70
+
+##### v) SIP/2.0 200 OK
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=1ad9931d  
+To: <sip: MS code@MS domain name>; tag=3094947605  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+CSeq: 2 BYE  
+Content-Length: Byte length of message body
+
+##### w) BYE sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0
+
+To: <sip: media stream sender code@ media stream sender domain name>; tag=32128  
+Content-Length: Byte length of message body  
+CSeq: 2 BYE  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=f569d024  
+Max-Forwards: 70
+
+##### x) SIP/2.0 200 OK
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=f569d024  
+To: <sip: media stream sender code@ media stream sender domain name>; tag=32128  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+CSeq: 2 BYE  
+Content-Length: Byte length of message body
+
+#### 8.9.4.2 Examples of historical media file download messages initiated by third party unit
+
+- a) INVITE sip: MS code@MS domain name or IP address port SIP/2.0
+- To: sip: MS code@MS domain name  
+Content-Length: Byte length of message body  
+Contact: <sip: CCS code@CCS IP address port>  
+CSeq: 1 INVITE  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=1ad9931d  
+Subject: Media stream sender ID: Sender's media stream serial number, media stream receiver ID: Receiver's media stream serial number  
+Max-Forwards: 70
+- b) SIP/2.0 200 OK
+- Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=1ad9931d  
+To: <sip: MS code@MS domain name>; tag=3094947605  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+CSeq: 1 INVITE  
+Contact: <sip: MS code@MS domain name or IP address port>  
+Content-Type: Application/SDP  
+Content-Length: Byte length of message body  
+v=0  
+o=008611010000002020000001 0 0 IN IP4 172.18.16.3  
+s=##ms20091214  
+c=IN IP4 172.18.16.3  
+t=0 0  
+m=video 6000 RTP/AVP 96 98 100  
+a=recvonly  
+a=rtpmap: 96 PS/90000  
+a=rtpmap: 98 H264/90000  
+a=rtpmap: 100 H265/90000
+- c) INVITE sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0
+- To: sip: media stream sender code@ media stream sender domain name  
+Content-Length: Byte length of message body  
+Contact: <sip: CCS code@CCS IP address port>  
+CSeq: 1 INVITE  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=f569d024  
+Content-Type: Application/SDP  
+Subject: Media stream sender ID: Sender's media stream serial number, media stream receiver ID: Receiver's media stream serial number  
+Max-Forwards: 70  
+v=0  
+o=008611010000002020000001 0 0 IN IP4 172.18.16.3  
+s=Download  
+u=008611010000041310000345:3  
+c=IN IP4 172.18.16.3  
+t=1288625085 1288625871  
+m=video 6000 RTP/AVP 96 98 100  
+a=recvonly  
+a=rtpmap: 96 PS/90000  
+a=rtpmap: 98 H264/90000  
+a=rtpmap: 100 H265/90000  
+a=downloadspeed: 4  
+y=1100000000
+
+##### **d) SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=f569d024  
+To: <sip: media stream sender code@ media stream sender domain name>; tag=32128  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+CSeq: 1 INVITE  
+Contact: <sip: media stream sender code@ media stream sender IP address port>  
+Content-Type: Application/SDP  
+Content-Length: Byte length of message body  
+v=0  
+o=008611010000041110000044 0 0 IN IP4 172.24.18.44  
+s=Download  
+c=IN IP4 172.24.18.44  
+t=1288625085 1288625871  
+m=video 9412 RTP/AVP 96  
+a=sendonly  
+a=rtpmap: 96 PS/90000  
+a=filesize: 10485760  
+y=1100000000
+
+##### **e) ACK sip: MS code@MS domain name or IP address port SIP/2.0**
+
+To: <sip: MS code@MS domain name>; tag=3094947605  
+Content-Length: Byte length of message body  
+CSeq: 1 ACK  
+Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=1ad9931d  
+Content-Type: Application/SDP  
+Max-Forwards: 70  
+v=0  
+o=008611010000041110000044 0 0 IN IP4 172.24.18.44  
+s=Download  
+c=IN IP4 172.24.18.44  
+t=1288625085 1288625871  
+m=video 9412 RTP/AVP 96  
+a=sendonly  
+a=rtpmap:96 PS/90000  
+y=1100000000
+
+##### **f) ACK sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0**
+
+To: <sip: media stream sender code@ media stream sender domain name>; tag=32128  
+Content-Length: Byte length of message body  
+CSeq: 1 ACK  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=f569d024  
+Max-Forwards: 70
+
+##### **g) INVITE sip: media stream receiver code@ media stream receiver domain name or IP address port SIP/2.0**
+
+To: sip: media stream receiver code @receiver domain name  
+Content-Length: Byte length of message body  
+Contact: <sip: CCS code@CCS IP address port>  
+CSeq: 1 INVITE  
+Call-ID: wlss-e862d62c-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=8338d6ac
+
+Subject: Media stream sender ID: Sender's media stream serial number,  
+media stream receiver ID: Receiver's media stream serial number  
+Max-Forwards: 70
+
+##### **h) SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=8338d6ac  
+To: <sip: media stream receiver code@media stream receiver domain name>;  
+tag=41  
+Call-ID: wlss-e862d62c-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5  
+CSeq: 1 INVITE  
+Contact: <sip: media stream receiver code@ media stream receiver IP  
+address port>  
+Content-Type: Application/SDP  
+Content-Length: Byte length of message body  
+v=0  
+o=008611010000003001000001 0 0 IN IP4 172.18.16.126  
+s=Download  
+c=IN IP4 172.18.16.126  
+t=1288625085 1288625871  
+m=video 9010 RTP/AVP 96  
+a=recvonly  
+a=rtpmap: 96 PS/90000
+
+##### **i) INVITE sip: MS code@MS domain name or IP address port SIP/2.0**
+
+To: sip: MS code@MS domain name  
+Content-Length: Byte length of message body  
+Contact: <sip: CCS code@CCS IP address port>  
+CSeq: 1 INVITE  
+Call-ID: wlss-19677597-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=39a741c5  
+Content-Type: Application/SDP  
+Subject: Media stream sender ID: Sender's media stream serial number,  
+media stream receiver ID: Receiver's media stream serial number  
+Max-Forwards: 70  
+v=0  
+o=008611010000003001000001 0 0 IN IP4 172.18.16.126  
+s=Download  
+c=IN IP4 172.18.16.126  
+t=1288625085 1288625871  
+m=video 9010 RTP/AVP 96  
+a=recvonly  
+a=rtpmap: 96 PS/90000  
+y=1100000000
+
+##### **j) SIP/2.0 200 OK**
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=39a741c5  
+To: <sip: MS code@MS domain name>; tag=3243635917  
+Call-ID: wlss-19677597-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5  
+CSeq: 1 INVITE  
+Contact: <sip: MS code@MS domain name or IP address port>  
+Content-Type: Application/SDP  
+Content-Length: Byte length of message body  
+v=0  
+o=008611010000002020000001 0 0 IN IP4 172.18.16.3  
+s=Download  
+c=IN IP4 172.18.16.3  
+t= 1288625085 1288625871  
+m=video 6000 RTP/AVP 96  
+a=sendonly
+
+a=rtpmap:96 PS/90000  
+y=1100000000
+
+##### k) ACK sip: media stream receiver code@ media stream receiver domain name or IP address port SIP/2.0
+
+To: <sip: media stream receiver code@media stream receiver domain name>; tag=41  
+Content-Length: Byte length of message body  
+CSeq: 1 ACK  
+Call-ID: wlss-e862d62c-72ff1e2e1d0f2ceaf8d07cf1e3a87f090@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=8338d6ac  
+Content-Type: Application/SDP  
+Max-Forwards: 70  
+v=0  
+o=008611010000002020000001 0 0 IN IP4 172.18.16.3  
+s=Download  
+c=IN IP4 172.18.16.3  
+t=1288625085 1288625871  
+m=video 6000 RTP/AVP 96  
+a=sendonly  
+a=rtpmap: 96 PS/90000  
+a=filesize: 10485760  
+y=1100000000
+
+##### l) ACK sip: MS code@MS domain name or IP address port SIP/2.0
+
+To: <sip: MS code@MS domain name>;tag=3243635917  
+Content-Length: Byte length of message body  
+CSeq: 1 ACK  
+Call-ID: wlss-19677597-72ff1e2e1d0f2ceaf8d07cf1e3a87f090@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: CCS code@CCS domain name>; tag=39a741c5  
+Max-Forwards: 70
+
+##### m) MESSAGE sip: CCS code @ CCS domain name or IP address port SIP/2.0
+
+To: <sip: CCS code@CCS domain name>; tag=32128  
+Content-Length: Byte length of message body  
+CSeq: 7 Message  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b0@172.18.16.5  
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: media stream sender code@media stream sender domain name>; tag=f569d024  
+Max-Forwards: 70  
+<?xml version="1.0"?>  
+<Notify>  
+<CmdType>MediaStatus</CmdType>  
+<SN>8</SN>  
+<DeviceID>008611010000041310000345</DeviceID>  
+<NotifyType>121</NotifyType>  
+</Notify>
+
+##### n) SIP/2.0 200 OK
+
+Via: SIP/2.0/UDP CCS domain name or IP address  
+From: <sip: media stream sender code@media stream sender domain name>; tag=f569d024  
+To: <sip: CCS code@CCS domain name>; tag=32128  
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b0@172.18.16.5  
+CSeq: 7 Message  
+Content-Length: Byte length of message body
+
+- o) **BYE sip: media stream receiver code@media stream receiver domain name or IP address port SIP/2.0**  
+ To: <sip: media stream receiver code@media stream receiver domain name>;  
+ tag=41  
+ Content-Length: Byte length of message body  
+ CSeq: 2 BYE  
+ Call-ID: wlss-e862d62c-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5  
+ Via: SIP/2.0/UDP CCS domain name or IP address  
+ From: <sip: CCS code@CCS domain name>; tag=8338d6ac  
+ Max-Forwards: 70
+- p) **SIP/2.0 200 OK**  
+ Via: SIP/2.0/UDP CCS domain name or IP address  
+ From: <sip: CCS code@CCS domain name>; tag=8338d6ac  
+ To: <sip: media stream receiver code@media stream receiver domain name>;  
+ tag=41  
+ Call-ID: wlss-e862d62c-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5  
+ CSeq: 2 BYE  
+ Content-Length: Byte length of message body
+- q) **BYE sip: MS code@MS domain name or IP address port SIP/2.0**  
+ To: <sip: MS code@MS domain name>; tag=3243635917  
+ Content-Length: Byte length of message body  
+ CSeq: 2 BYE  
+ Call-ID: wlss-19677597-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5  
+ Via: SIP/2.0/UDP CCS domain name or IP address  
+ From: <sip: CCS code@CCS domain name>; tag=39a741c5  
+ Max-Forwards: 70
+- r) **SIP/2.0 200 OK**  
+ Via: SIP/2.0/UDP CCS domain name or IP address  
+ From: <sip: CCS code@CCS domain name>; tag=39a741c5  
+ To: <sip: MS code@MS domain name>;tag=3243635917  
+ Call-ID: wlss-19677597-72ff1e2e1d0f2ceaf8d07cf1e3a87f09@172.18.16.5  
+ CSeq: 2 BYE  
+ Content-Length: Byte length of message body
+- s) **BYE sip: MS code@MS domain name or IP address port SIP/2.0**  
+ To: <sip: MS code@MS domain name>; tag=3094947605  
+ Content-Length: Byte length of message body  
+ CSeq: 2 BYE  
+ Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+ Via: SIP/2.0/UDP CCS domain name or IP address  
+ From: <sip: CCS code@CCS domain name>; tag=1ad9931d  
+ Max-Forwards: 70
+- t) **SIP/2.0 200 OK**  
+ Via: SIP/2.0/UDP CCS domain name or IP address  
+ From: <sip: CCS code@CCS domain name>; tag=1ad9931d  
+ To: <sip: MS code@MS domain name>;tag=3094947605  
+ Call-ID: wlss-11df50d7-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5  
+ CSeq: 2 BYE  
+ Content-Length: Byte length of message body
+- u) **BYE sip: media stream sender code@ media stream sender domain name or IP address port SIP/2.0**  
+ To: <sip: media stream sender code@ media stream sender domain name>;  
+ tag=32128  
+ Content-Length: Byte length of message body
+
+```
+
+CSeq: 2 BYE
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>; tag=f569d024
+Max-Forwards: 70
+
+```
+
+##### v) **SIP/2.0 200 OK**
+
+```
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: CCS code@CCS domain name>; tag=f569d024
+To: <sip: media stream sender code@ media stream sender domain name>;
+tag=32128
+Call-ID: wlss-e680b2c1-730beb6350a5506aa8316d9dc100cf6b@172.18.16.5
+CSeq: 2 BYE
+Content-Length: Byte length of message body
+
+```
+
+## 8.10 Time calibration
+
+### 8.10.1 Basic requirements
+
+The devices in the VSS 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, UDP and NTP, and the input or self-produced time signals are output in the standard NTP IP format.
+
+Specific time calibration methods can be applied according to the configuration during the operation of the VSS.
+
+### 8.10.2 Signalling process
+
+SIP time calibration is finished in the registration process, see Figure 8-16.
+
+![Sequence diagram showing the signalling flow of registration between a CCS and a SIP UA. The steps are: 1: Register (SIP UA to CCS), 2: 401 unauthorized (CCS to SIP UA), 3: Register (SIP UA to CCS), 4: 200 OK (CCS to SIP UA).](46357bd4781f8f8f776667fb096f54a9_img.jpg)
+
+```
+
+sequenceDiagram
+    participant CCS
+    participant SIP_UA as SIP UA
+    Note right of SIP_UA: 1: Register
+    SIP_UA->>CCS: 
+    Note left of CCS: 2: 401 unauthorized
+    CCS->>SIP_UA: 
+    Note right of SIP_UA: 3: Register
+    SIP_UA->>CCS: 
+    Note left of CCS: 4: 200 OK
+    CCS->>SIP_UA: 
+  
+```
+
+H.627(20)\_F8-16
+
+Sequence diagram showing the signalling flow of registration between a CCS and a SIP UA. The steps are: 1: Register (SIP UA to CCS), 2: 401 unauthorized (CCS to SIP UA), 3: Register (SIP UA to CCS), 4: 200 OK (CCS to SIP UA).
+
+**Figure 8-16 – Signalling flow of registration**
+
+In Figure 8-16, The SIP UA includes the PU, CU, CPG, MS and the other CCS with SRG.
+
+The signalling flow description is as follows.
+
+- The SIP UA sends a REGISTER request to the CCS.
+- The CCS sends response 401 to the SIP UA, and the authentication VSS and parameters applicable for the SIP UA are provided in the WWWAuthenticate field of the response message header.
+
+- The SIP UA resends the REGISTER request to the CCS, and provides a trust letter in the Authorization field of the request, including authentication information.
+- The CCS 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.
+
+See the examples of registration messages in clause 8.10.4.
+
+### 8.10.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 UA performs time calibration with the registration method, the expiration time of the registration should be less than the running time taken by the SIP UA and CCS for an error of 1 s to occur. For example, after time calibration by the SIP UA and CCS, if the difference between the device time after the CCS time is more than 1 s after the SIP UA runs for 10 h, the expiration time of the registration should be set to 10 h (36 000 s), so as to ensure that the time error between the SIP UA and the CCS is less than 1 s.
+
+### 8.10.4 Examples of registration messages
+
+- a) REGISTER sip: CCS code @ CCS domain name or IP address port SIP/2.0  
+Via: SIP/2.0/UDP SIP UA domain name or IP address port  
+From: <sip: SIP UA code@ SIP UA domain name>;tag=185326220  
+To: <sip: SIP UA code@ SIP UA domain name>  
+Call-ID: ms1214-322164710-681262131542511620107-0@172.18.16.3  
+CSeq: 1 REGISTER  
+Contact: <sip: SIP UA code@ SIP UA IP address port>  
+Max-Forwards: 70  
+Expires: 3600  
+Content-Length: 0
+- b) SIP/2.0 401 Unauthorized  
+To: sip: SIP UA code @ SIP UA domain name  
+Content-Length: 0  
+CSeq: 1 REGISTER  
+Call-ID: ms1214-322164710-681262131542511620107-0@172.18.16.3  
+From: <sip: SIP UA code@ SIP UA domain name>; tag=185326220  
+Via: SIP/2.0/UDP SIP UA domain name or IP address port  
+WWW-Authenticate: Digest realm="0086110100000",nonce="6fe9ba44a76be22a"
+- c) REGISTER sip: CCS code@CCS domain name or IP address port SIP/2.0  
+Via: SIP/2.0/UDP SIP UA domain name or IP address port  
+From: <sip: SIP UA code@ SIP UA domain name>; tag=185326220  
+To: <sip: SIP UA code@ SIP UA domain name>  
+Call-ID: ms1214-322164710-681262131542511620107-0@172.18.16.3  
+CSeq: 2 REGISTER  
+Contact: <sip: SIP UA code@ SIP UA IP address port>  
+Authorization: Digest username="008611010000002020000001",  
+realm="0086110100000", nonce="6fe9ba44a76be22a",  
+uri="sip:008611010000002000000001@172.18.16.5:5060",  
+response="9625d92d1bdea7a911926e0db054968", algorithm=MD5  
+Max-Forwards: 70  
+Expires: 3600  
+Content-Length: 0
+- d) SIP/2.0 200 OK  
+To: <sip: SIP UA code@ SIP UA domain name>; tag=69113a2a
+
+```
+
+Contact: sip: SIP UA code@ SIP UA IP address port
+Content-Length: 0
+CSeq: 2 REGISTER
+Call-ID: ms1214-322164710-681262131542511620107-0@172.18.16.3
+From: <sip: SIP UA code@ SIP UA domain name>; tag=185326220
+Via: SIP/2.0/UDP SIP UA domain name or IP address port
+Date: 2010-11-02T15:01:26.115
+Expires: 3600
+
+```
+
+## 8.11 Subscription and notification
+
+### 8.11.1 Event subscription
+
+#### 8.11.1.1 Basic requirements
+
+When an event notifier receives an event subscription message, it sends a confirmation message to the event subscriber. Event subscription is achieved with the SUBSCRIBE method specified in [IETF RFC 6665].
+
+The event notifier includes the CCS with SRG and PU, and the event subscriber includes the other CCS with SRG and CU. Events include alarm events and mobile device position notification events.
+
+#### 8.11.1.2 Signalling process
+
+For the event subscription signalling flow, see Figure 8-17.
+
+![Sequence diagram showing the signalling flow of event subscription between a Subscriber and a Notifier. The Subscriber sends a 1: SUBSCRIBE (Event subscription) message to the Notifier, and the Notifier responds with a 2: 200 OK (or 400 to end this session) message. The diagram is labeled H.627(20)_F8-17.](f59dafee4c3bbc563111e5b1b6048c3d_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Subscriber
+    participant Notifier
+    Note right of Notifier: H.627(20)_F8-17
+    Subscriber->>Notifier: 1: SUBSCRIBE (Event subscription)
+    Notifier-->>Subscriber: 2: 200 OK (or 400 to end this session)
+
+```
+
+Sequence diagram showing the signalling flow of event subscription between a Subscriber and a Notifier. The Subscriber sends a 1: SUBSCRIBE (Event subscription) message to the Notifier, and the Notifier responds with a 2: 200 OK (or 400 to end this session) message. The diagram is labeled H.627(20)\_F8-17.
+
+**Figure 8-17 – Signalling flow of event subscription**
+
+The event subscription signalling flow description is as follows.
+
+- The event subscriber sends a SUBSCRIBE request to the event notifier, and the request message body carries the subscription parameters.
+- The event notifier shall return the response message indicating whether the subscription is successful to the event subscriber.
+
+See the examples of event subscription messages in clause 8.11.1.4.
+
+#### 8.11.1.3 Protocol interface
+
+The Content-type field of the MESSAGE header is Content-type: Application/ ECCS+xml.
+
+The request command and response command message bodies in the alarm event subscription process are specified in the ECCS, for a detailed description, see the alarm queries in clause A.2.4 and the alarm notification responses in clause A.2.6.
+
+The request command message body in the process of the mobile device position reporting event subscription is specified in the ECCS, for a detailed description, see the mobile device position data queries in clause A.2.4.
+
+#### 8.11.1.4 Examples of event subscription messages
+
+- a) SUBSCRIBE sip: event notifier code@event notifier domain name or IP address SIP/2.0
+- ```
+Via: SIP/2.0/UDP event subscriber domain name or IP address
+Max-Forwards: 70
+From: <sip: event subscriber code@event subscriber domain name or IP
+address> ; tag=BK32B1U8DKDrB
+To: <sip: event notifier code@event notifier domain name or IP address>
+Call-ID: 17250
+CSeq: 1 SUBSCRIBE
+Expires: 90
+Event: Alarm
+Content-type: Application/ECCS+XML
+Content-Length: Byte length of message body
+<?xml version="1.0"?>
+<Query>
+<CmdType> Alarm </CmdType>
+<SN>17430</SN>
+<DeviceID>0086110100000013400000001</DeviceID>
+<StartAlarmPriority>1</StartAlarmPriority>
+<EndAlarmPriority>4</EndAlarmPriority>
+<AlarmMethod>0</AlarmMethod>
+<StartTime>2010-11-11T00:00:00</StartTime>
+<EndTime>2010-12-11T00:00:00</EndTime>
+</Query>
+```
+- b) 200 OK
+- ```
+Via: SIP/2.0/UDP event subscriber domain name or IP address
+From: <sip: event subscriber code@event subscriber domain name or IP
+address> ; tag=BK32B1U8DKDrB
+To: <sip: event notifier code@event notifier domain name or IP
+address> ; tag=AK22C1Z8DKDrB
+Call-ID: 17250
+CSeq: 1 SUBSCRIBE
+Expires: 90
+Content-type: Application/ECCS+XML
+Content-Length: Byte length of message body
+```
+
+### 8.11.2 Event notification
+
+#### 8.11.2.1 Basic requirements
+
+After the event notifier accepts the event subscription, it shall notify the event subscriber of the occurrence of the event immediately after the event is triggered, and the event subscriber shall send the confirmation message that the event has been received to the event notifier. The event notification is achieved with the NOTIFY method specified in [IETF RFC 6665]. Event notification exception handling shall comply with the provisions of [IETF RFC 6665].
+
+The event notifier includes the CCS with SRG and PU, and the event subscriber includes the other CCS with SRG and CU. The events include alarm events and mobile device position notification events.
+
+#### 8.11.2.2 Signalling process
+
+For the event notification signalling flow, see Figure 8-18.
+
+![Sequence diagram showing the signalling flow of event notification between a Notifier and a Subscriber. The Notifier sends a NOTIFY message (Notification of preset event) to the Subscriber, and the Subscriber responds with a 200 OK message. The diagram is labeled H.627(20)_F8-18.](92e26d86c5a582766cb9afdbd2c1aee7_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Notifier
+    participant Subscriber
+    Note right of Subscriber: H.627(20)_F8-18
+    Notifier->>Subscriber: 1: NOTIFY (Notification of preset event)
+    Subscriber-->>Notifier: 2: 200 OK
+  
+```
+
+Sequence diagram showing the signalling flow of event notification between a Notifier and a Subscriber. The Notifier sends a NOTIFY message (Notification of preset event) to the Subscriber, and the Subscriber responds with a 200 OK message. The diagram is labeled H.627(20)\_F8-18.
+
+**Figure 8-18 – Signalling flow of event notification**
+
+The event notification process description is as follows.
+
+- After the notification event occurs, the event notifier sends a NOTIFY message to the event subscriber, and the message body of NOTIFY shall carry the notification parameters.
+- The event subscriber shall return the response message of the notification to the event notifier, event notification exception handling shall comply with the provisions of [IETF RFC 6665].
+
+See the examples of event notification messages in clause 8.11.2.4.
+
+#### 8.11.2.3 Protocol interface
+
+The Content-type field of the MESSAGE header is Content-type: Application/ ECCS+xml.
+
+The request command and response command message bodies in the alarm event notification process are specified in the ECCS, for a detailed description, see the alarm notifications in clause A.2.5 and the alarm notification responses in clause A.2.6.
+
+The request command message body in the mobile device position notification process is specified in the ECCS; for a detailed description, see the mobile device position data notifications in clause A.2.5.
+
+#### 8.11.2.4 Examples of event notification messages
+
+- a) NOTIFY sip: event subscriber address@event subscriber domain name or IP address SIP/2.0
+- ```
+
+Via: SIP/2.0/UDP event notifier domain name or IP address
+Max-Forwards: 70
+From: <sip: event notifier code@event notifier domain name or IP
+address>;tag=AK22C1Z8DKDrB
+To: <sip: event subscriber code@event subscriber domain name or IP
+address>;tag=BK32B1U8DKDrB
+Call-ID: 17250
+CSeq:1 NOTIFY
+Subscription-State: active;expires=90;retry-after=0
+Event: alarm
+Content-type: Application/ECCS+XML
+Content-Length: Byte length of message body
+<?xml version="1.0"?>
+<Notify>
+<CmdType>Alarm</CmdType>
+<SN>1</SN>
+<DeviceID>0086110100000013400000001</DeviceID>
+<AlarmPriority>4</AlarmPriority>
+<AlarmMethod>2</AlarmMethod>
+<AlarmTime>2009-12-04T16:23:32</AlarmTime>
+<AlarmDescription>AlarmDescription </AlarmDescription>
+<Longitude> 171.3</Longitude>
+<Latitude> 34.2 </Latitude>
+  
+```
+
+</Notify>
+
+##### b) 200 OK
+
+Via: SIP/2.0/UDP event notifier domain name or IP address  
+From: <sip: event notifier code@event notifier domain name or IP address>;tag=AK22C1Z8DKDrB  
+To: <sip: event subscriber code@event subscriber domain name or IP address>;tag=BK32B1U8DKDrB  
+Call-ID: 17250  
+CSeq: 1 NOTIFY  
+Content-type: Application/ECCS+XML  
+Content-Length: Byte length of message body
+
+### 8.11.3 Directory subscription
+
+#### 8.11.3.1 Basic requirements
+
+The subscription mechanism is used to transmit the device information of status changes among the VSSs, and it is a maintenance mechanism used for providing device status conformity among the VSSs. The VSS can subscribe to the alternation information including offline, online, addition, deletion and update of all or part of the catalogues of the other VSSs by means of subscription.
+
+A VSS may subscribe to the catalogue information of multiple other VSSs. The list of subscribing catalogues and subscribed catalogues are saved in the local VSS.
+
+After the directory notifier accepts the directory subscription, it shall send a request confirmation message to the directory subscriber. The directory subscription is achieved with the SUBSCRIBE method specified in [IETF RFC 6665].
+
+The VSS A subscribes to the VSS B, after successful initial subscription, The VSS A shall send a refresh subscription message to the VSS B before expiration, so as to maintain the subscription status. The refresh subscription messages and the initial subscription message belong to the same session, and the value in the Expire header field is greater than 0.
+
+If the VSS A no longer wishes to subscribe to the catalogue alterations in the VSS B, it shall send a request of unsubscription to the VSS B. The unsubscription request and the initial subscription request shall belong to the same session, and the value in the Expire header field is greater than 0. On receiving the unsubscription request, the VSS B shall remove the subscription status of the VSS A.
+
+The directory notifier includes the CCS with SRG, MS and PU with subdevice, and the directory subscriber includes the other CCS with SRG and PU with subdevice.
+
+#### 8.11.3.2 Signalling process
+
+For the directory subscription signalling flow, see Figure 8-19.
+
+![Sequence diagram showing the signalling flow of directory subscription between a Subscriber and a Notifier.](2eb73eee0ca246cd09f43c2044f3fb49_img.jpg)
+
+```
+sequenceDiagram
+    participant Subscriber
+    participant Notifier
+    Note right of Notifier: H.627(20)_F8-19
+    Subscriber->>Notifier: 1: SUBSCRIBE (Event subscription)
+    Notifier-->>Subscriber: 2: 200 OK (or 400 to end this session)
+```
+
+The diagram illustrates the signalling flow for directory subscription. It features two vertical dashed lines representing the lifelines of a 'Subscriber' and a 'Notifier'. A solid horizontal arrow labeled '1: SUBSCRIBE (Event subscription)' points from the Subscriber to the Notifier. A return arrow labeled '2: 200 OK (or 400 to end this session)' points from the Notifier back to the Subscriber. The diagram is identified by the text 'H.627(20)\_F8-19' at the bottom right.
+
+Sequence diagram showing the signalling flow of directory subscription between a Subscriber and a Notifier.
+
+Figure 8-19 – Signalling flow of directory subscription
+
+The directory subscription signalling flow description is as follows.
+
+- The directory subscriber sends a SUBSCRIBE request to the directory notifier, and the message body of the SUBSCRIBE request shall include the directory type of the subscription, and the start time of adding devices. For a detailed description, see the device directory queries in clause A.2.4.
+- The directory notifier shall return the response message indicating whether the subscription is successful to the directory subscriber; the message body of the confirmation response message that the subscription is successful shall include the device information. See the directory query receiving responses in clause A.2.6.
+
+See the examples of directory subscription messages in clause 8.11.3.4.
+
+#### 8.11.3.3 Protocol interface
+
+The Content-type field of the MESSAGE header is Content-type: Application/ ECCS+xml.
+
+The request commands in the directory subscription process are specified in the ECCS; for a detailed description, see the device directory queries in clause A.2.4 and the directory information query received responses in clause A.2.6.
+
+#### 8.11.3.4 Examples of catalogue subscription messages
+
+- a) SUBSCRIBE sip: catalog notifier code@catalog notifier domain name or IP address SIP/2.0
+- ```
+Via: SIP/2.0/UDP catalog subscriber domain name or IP address
+Max-Forwards: 70
+From: <sip: catalog subscriber code@catalog subscriber domain name or IP
+address> ;tag=BK32B1U8DKDrB
+To: <sip: catalog notifier code @catalog notifier domain name or IP
+address>
+Call-ID: 17250
+CSeq:1 SUBSCRIBE
+Expires: 90
+Event:Catalog;id=1894
+Content-type: Application/ECCS+XML
+Content-Length: Byte length of message body
+<?xml version="1.0"?>
+<Query>
+<CmdType> Catalog </CmdType>
+<SN>17430</SN>
+<DeviceID>0086110100000011100000001</DeviceID>
+<StartTime>2010-11-11T00:00:00</StartTime>
+<EndTime>2010-12-11T00:00:00</EndTime>
+</Query>
+```
+- b) 200 OK
+- ```
+Via: SIP/2.0/UDP catalog subscriber domain name or IP address
+From: <sip: catalog subscriber code@catalog subscriber domain name or IP
+address> ;tag=BK32B1U8DKDrB
+To: <sip: catalog notifier code@catalog notifier domain name or IP
+address>;tag=AK22C1Z8DKDrB
+Call-ID: 17250
+CSeq:1 SUBSCRIBE
+Expires:90
+Content-type: Application/ECCS+XML
+Content-Length: Byte length of message body
+```
+
+### 8.11.4 Directory notification
+
+#### 8.11.4.1 Basic requirements
+
+The notification mechanism is used to transmit of the device information of status changes among the VSSs, and it is a maintenance mechanism used for providing device status conformity among the VSSs.
+
+After the directory notifier accepts the directory subscription, it shall notify the directory subscriber immediately if the directory changes, and the directory subscriber shall send a confirmation message that the directory has been received to the directory owner, directory notification exception handling shall comply with the provisions of [IETF RFC 6665]. The directory notification is achieved with the NOTIFY method specified in [IETF RFC 6665].
+
+The VSS B subscribes to the VSS A. On receiving the unsubscription request, the VSS A shall remove the subscription status of the VSS B and it will no longer notify the VSS B after catalogue alteration.
+
+The VSS A may actively end the subscription by sending the NOTIFY message with Terminated in the subscription-state header field; the NOTIFY message body can be null, and the subscriber shall reply 200 OK for response on receiving the message.
+
+When sending the notification message, the transmission processing of multiple notification messages shall be performed, the method provided in clause 7.5 should be used to control the transmission of notification messages, and transmission data-filtering processing should be performed, so as to avoid the transmission of mass invalid data between systems that affects system performance due to the device frequently going online and offline and other abnormal conditions.
+
+The directory notifier refers to the CCS, PU with subdevice, etc. and the directory subscriber refers to the CCS, PU with subdevice, etc.
+
+#### 8.11.4.2 Signalling process
+
+For the directory notification signalling flow, refers to Figure 8-20.
+
+![Sequence diagram showing the signalling flow of directory notification between a Notifier and a Subscriber.](ccb9a8830d90ffdcecfc4ef45ce72dbe_img.jpg)
+
+```
+sequenceDiagram
+    participant Notifier
+    participant Subscriber
+    Note right of Subscriber: H.627(20)_F8-20
+    Notifier->>Subscriber: 1: NOTIFY (Notification of preset event)
+    Subscriber-->>Notifier: 2: 200 OK
+```
+
+The diagram illustrates the signalling flow for directory notification. It features two vertical dashed lines representing the lifelines of a 'Notifier' and a 'Subscriber'. A solid horizontal arrow labeled '1: NOTIFY (Notification of preset event)' points from the Notifier to the Subscriber. A return arrow labeled '2: 200 OK' points from the Subscriber back to the Notifier. The diagram is identified by the text 'H.627(20)\_F8-20' at the bottom right.
+
+Sequence diagram showing the signalling flow of directory notification between a Notifier and a Subscriber.
+
+**Figure 8-20 – Signalling flow of directory notification**
+
+The directory notification signalling flow description is as follows.
+
+- After the change of directory, the directory notifier sends a NOTIFY request to the directory subscriber; for a detailed description, see the directory query responses in clause A.2.6;
+- The directory subscriber shall return a response message indicating whether the directory transmission is successful to the directory notifier, directory notification exception handling shall comply with the provisions of [IETF RFC 6665]; the message body carries the directory receiving result markup, etc. For a detailed description, see the directory receiving responses in clause A.2.6.
+
+See the examples of directory notification messages in clause 8.11.4.4.
+
+#### 8.11.4.3 Protocol interface
+
+The Content-type field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+The request commands in the directory notification process are specified in the ECCS, for a detailed description, see the directory query responses in clause A.2.6 and the directory received responses clause A.2.6.
+
+#### 8.11.4.4 Examples of catalogue notification messages
+
+- a) NOTIFY sip: catalog subscriber code@catalog subscriber domain name or IP address SIP/2.0
+- ```
+Via: SIP/2.0/UDP catalog notifier domain name or IP address
+Call-ID: 17520
+From: <sip: catalog notifier code@catalog notifier domain name or IP
+address>;tag=AK22C1Z8DKDrB
+To: <sip: catalog subscriber code@catalog subscriber domain name or IP
+address>; tag=BK32B1U8DKDrB
+CSeq: 1 NOTIFY
+Max-Forwards: 70
+Subscription-State: active;expires=90;retry-after=0
+Event: Catalog;id=1894
+Content-Length: Byte length of message body
+<?xml version="1.0"?>
+<Response>
+  <CmdType> Catalog </CmdType>
+  <SN>17430</SN>
+  <DeviceID>008611010000001110000001</DeviceID>
+  <SumNum>100</SumNum>
+  <DeviceList Num="2">
+    <Item>
+      <DeviceID>008611010000001310000001</DeviceID>
+      <!--Optional field "Event", indicate device status alteration events
+      of ON: online; OFF: offline;VLOST: video lost;DEFECT: defect;ADD: add;
+      DEL: delete;UPDATE: update (mandatory) -->
+      <Event>OFF</Event>
+    </Item>
+    <Item>
+      <DeviceID>008611010000001310000002</DeviceID>
+      <!--Optional field "Event", indicate device status alteration events
+      of ON: online; OFF: offline;VLOST: video lost;DEFECT: defect;ADD: add;
+      DEL: delete;UPDATE: update (mandatory) -->
+      <Event>ADD</Event>
+      <Name> Camera1</Name>
+      <Manufacturer> Manufacturer1</Manufacturer>
+      <Model> Model1</Model>
+      <Owner> Owner1</Owner>
+      <ZoneCode>ZoneCode1</ZoneCode>
+      <Block> Block1</Block>
+      <Address> Address1</Address>
+      <Parental> 1 </Parental>
+      <ParentID>008611010000001110000001 </ParentID>
+      <IPAddress> 192.168.3.81 </IPAddress>
+      <Port> 5060 </Port>
+      <Password> Password 1 </Password>
+      <Status> Status 1 </Status>
+      <Longitude> 171.4</Longitude>
+      <Latitude> 34.2 </Latitude>
+    </Item>
+  </DeviceList>
+</Response>
+```
+- b) 200 OK
+- ```
+Via: SIP/2.0/UDP catalog notifier domain name or IP address
+Call-ID: 17520
+```
+
+```
+From: <sip: catalog notifier code@catalog notifier domain name or IP address>;tag=AK22C1Z8DKDrB
+To: <sip: catalog subscriber code@catalog subscriber domain name or IP address>; tag=BK32B1U8DKDrB
+CSeq: 1 NOTIFY
+Content-Length: 0
+```
+
+## **8.12 Audio broadcast and audio intercom**
+
+### **8.12.1 Audio broadcast**
+
+#### **8.12.1.1 Basic requirements**
+
+The audio broadcast from the user to the audio receiver through the audio stream sender is achieved through the audio broadcast function. The CCS sends notification messages to the audio stream receiver, which makes a judgement after receiving the notification message. If it is able to receive audio stream, it sends a call request to the audio stream sender to obtain the broadcast media stream.
+
+The audio stream receiver includes the PU or the other VSS, the audio stream sender includes the CU or the other VSS. For the audio stream receiver ID and audio stream sender ID, see clause 7.1.4 of [ITU-T H.626V2].
+
+If the PU has audio output capability, the audio output device ID shall be reported during the directory query and subscription of the PU. If the audio output device ID and capability are not reported, it shows that the PU has no audio output capability. When the audio output channel is reported, ParentID is the parent device ID.
+
+For the packaging format of the audio stream, see the specification of the audio stream RTP packaging in clause 7.6.2.
+
+The audio broadcast should support the media stream keepalive mechanism specified in clause 7.4.
+
+#### 8.12.1.2 Signalling process
+
+For the signalling flow of broadcast initiated by CCS, see Figure 8-21.
+
+![Sequence diagram showing the signalling flow of broadcast initiated by CCS. Lifelines: Audio stream receiver, CCS, MS, Audio stream sender. The diagram shows 24 numbered messages and two audio stream flows.](b54b769d67164910c7c5b2a0ea74257b_img.jpg)
+
+```
+sequenceDiagram
+    participant ASR as Audio stream receiver
+    participant CCS
+    participant MS
+    participant ASS as Audio stream sender
+
+    Note left of ASR: 1: Message (Audio broadcast notification)
+    ASR->>CCS: 1: Message (Audio broadcast notification)
+    CCS-->>ASR: 2: 200 OK
+    Note left of ASR: 3: Message (Audio broadcast response)
+    ASR->>CCS: 3: Message (Audio broadcast response)
+    CCS-->>ASR: 4: 200 OK
+    Note left of ASR: 5: Invite (with SDP)
+    ASR->>CCS: 5: Invite (with SDP)
+    CCS->>MS: 6: Invite
+    MS-->>CCS: 7: 200 OK (with SDP)
+    CCS->>ASS: 8: Invite (with SDP)
+    ASS-->>CCS: 9: 200 OK (with SDP)
+    CCS->>MS: 10: ACK (with SDP)
+    MS-->>ASS: 11: ACK
+    Note right of ASS: Audio stream
+    ASS-->>MS: Audio stream
+    CCS->>MS: 12: Invite (with SDP)
+    MS-->>CCS: 13: 200 OK (with SDP)
+    CCS-->>ASR: 14: 200 OK (with SDP)
+    ASR->>CCS: 15: ACK
+    CCS->>MS: 16: ACK
+    Note left of ASR: Audio stream
+    MS-->>ASR: Audio stream
+    Note left of ASR: 17: BYE
+    ASR->>CCS: 17: BYE
+    CCS-->>ASR: 18: 200 OK
+    CCS->>MS: 19: BYE
+    MS-->>CCS: 20: 200 OK
+    CCS->>MS: 21: BYE
+    MS-->>CCS: 22: 200 OK
+    CCS->>ASS: 23: BYE
+    ASS-->>CCS: 24: 200 OK
+```
+
+Sequence diagram showing the signalling flow of broadcast initiated by CCS. Lifelines: Audio stream receiver, CCS, MS, Audio stream sender. The diagram shows 24 numbered messages and two audio stream flows.
+
+H.627(20)\_F8-21
+
+**Figure 8-21 – Signalling flow of broadcast initiated by CCS**
+
+In Figure 8-21:
+
+signals 1, 2, 3 and 4 constitute the audio broadcast notification and audio broadcast response message process;
+
+signals 5, 12, 13, 14, 15 and 16 constitute the process of establishing the media stream signals between the audio stream receiver and the MS through the B2BUA method by the CCS after receiving the audio stream receiver call request;
+
+signals 6–11 constitute the process of establishing the media stream signals between the MS and the audio stream sender through the third-party call control by the CCS;
+
+signals 17–20 constitute the process of disconnecting the media link signals between the audio stream receiver and the MS by the CCS;
+
+signals 21–24 constitute the process of disconnecting the media stream signals between the MS and the audio stream sender by the CCS.
+
+The signalling flow description is as follows.
+
+- The CCS sends the audio broadcast notification message to the audio stream receiver; the audio stream receiver ID as the destination address is indicated through the To header field in the message, and the message is carried by the MESSAGE method.
+- After the audio stream receiver receives the audio broadcast notification message, it sends a 200 OK response to the CCS.
+- The audio stream receiver sends the audio broadcast response message to the CCS; the CCS ID as the destination address is indicated through the To header field in the message, and the message is carried by the MESSAGE method.
+- After the CCS receives the audio broadcast response message, it sends the 200 OK response to the audio stream receiver.
+- The audio stream receiver sends the Invite message to the CCS; the message indicates the audio stream sender ID as the destination address through the To header field; the message header field carries the subject field, showing such parameters as the request audio stream sender ID, sender media stream SN, audio stream receiver ID and receiver media stream SN; the s field in the SDP message body is "Play", representing real-time media stream; the media parameter in the m field is marked with "audio", showing the request of audio media stream.
+- After the CCS receives the Invite request, the media connection between the MS and the audio stream sender is established through third-party call control. The Invite message is to the MS, and this message does not carry an SDP message body.
+- After the MS receives the Invite request of the CCS, it replies with the 200 OK response, carrying the SDP message body in which the IP, port, media format, etc. of the media stream received by the MS are described.
+- After the CCS receives the 200 OK response sent back from the MS, it sends the Invite message to the audio stream sender, which indicates the audio stream sender ID as the destination address through the To header field; the message header field carries the subject field, showing such parameters as the request audio stream sender ID, sender media stream SN, audio stream receiver ID and receiver media stream SN; the request carries the 200 OK response message body sent by the MS in message 7; the s field in the SDP message body is "Play", representing real-time media stream; the media parameter in the m field is marked with "audio", showing the request of audio media stream; the y field is added to describe the SSRC value and f field for media parameter;
+- After the audio stream sender receives the Invite request of the CCS, it replies with the 200 OK response, carrying the SDP message body in which the IP, port, media format, SSRC field, etc. of the media stream received by the media stream sender are described; the s field in the SDP message body is "Play", representing real-time media stream; the media parameter in the m field is marked with "audio", showing the request of audio media stream.
+- After the CCS receives the 200 OK response sent back from the audio stream sender, it sends an ACK request to the MS, which carries the 200 OK response message body sent by the audio stream sender in message 9, and the establishment process of the Invite session with the MS is finished.
+
+- After the CCS receives the 200 OK response sent back from the audio stream sender, it sends an ACK request to the media stream sender, which does not carry a message body, and the establishment process of the Invite session with the media stream sender is finished.
+- Upon completion of third party call control, the CCS establishes the media link between the audio stream receiver and the MS. The SSRC value is added to message 5, which is forwarded to the MS.
+- After the MS receives the Invite request, it replies with the 200 OK response, carrying the SDP message body in which the IP, port, media format, SSRC value, etc. of the media stream sent from the MS are described; the s field in the SDP message body is "Play", representing real-time media stream; the media parameter in the m field is marked with "audio", showing the request of audio media stream.
+- The CCS forwards message 13 to the audio stream receiver.
+- After the audio stream receiver receives the 200 OK response, it replies with the ACK message, and the establishment process of the Invite session with CCS is finished.
+- The CCS forwards message 15 to the MS, and the establishment process of the Invite session with the CCS is finished.
+- The CCS sends the BYE message to the audio stream receiver, and the Invite session established by messages 5, 14 and 15 is disconnected.
+- After the audio stream receiver receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- The CCS sends the BYE message to the MS, and the Invite session with the MS established by messages 12, 13 and 16 is disconnected
+- After the MS receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- The CCS sends the BYE message to the MS, and the Invite session with the MS established by messages 6, 7 and 10 is disconnected.
+- After the MS receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+- The CCS sends the BYE message to the audio stream server, and the Invite session with the audio stream sender established by messages 8, 9 and 11 is disconnected.
+- After the audio stream sender receives the BYE message, it replies with the 200 OK response, and the session is disconnected.
+
+NOTE – The audio broadcast notification messages can be sent through the CCS by the process specified in this clause, or otherwise through the audio stream sender. The audio stream receiver ID as the destination address is indicated by the To header field in the message, and sent to the audio stream receiver after transfer through the CCS. The audio stream receiver sends the response message after processing, and the audio stream sender ID as the destination address is indicated through the To header field in the message, and replied to the audio stream sender after transfer through the CCS. The subsequent call processes are the same as those specified in this clause.
+
+For the examples of audio broadcast notification and response messages, see clause 8.12.1.4. For the examples of audio media stream session interaction messages, see clause 8.2.4.1.
+
+#### 8.12.1.3 Protocol interface
+
+##### 1) Audio broadcast notification and audio broadcast response commands
+
+The Content-type field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+The audio broadcast notification and audio broadcast response commands are specified in the ECCS, for a detailed description, see the audio broadcast notifications in clause A.2.5 and the audio broadcast responses in clause A.2.6.
+
+##### 2) SDP parameters
+
+For a detailed description of the SDP transporting the audio stream, see the SDP specifications in clause 7.7.
+
+### 8.12.2 Examples of audio broadcast notification and response messages
+
+#### a) Audio broadcast notification
+
+```
+MESSAGE sip:008631010403001370002272@192.168.0.199:5511 SIP/2.0
+From: <sip:0086310104000020000000001@31010400000>;tag=b05e7e60-ca00a8c0-1587-3a3-7fb52a44-3a3
+To: <sip:008631010403001370002272@192.168.0.199:5511>
+Call-ID: b05e7e60-ca00a8c0-1587-3a3-2b297f29-3a3@008631010400000
+CSeq: 1761796551 MESSAGE
+Via: SIP/2.0/UDP 192.168.0.202:5511;rport;branch=z9hG4bK-3a3-e3849-287ef646
+Max-Forwards: 70
+Content-Type: Application/ECCS+xml
+Content-Length: 159
+<?xml version="1.0" ?>
+<Notify>
+<CmdType>Broadcast</CmdType>
+<SN>992</SN>
+<SourceID>0086110104000013600000001</SourceID>
+<TargetID>008611010403001370002272</TargetID>
+</Notify>
+```
+
+#### b) Audio broadcast response:
+
+```
+MESSAGE sip:0086110104000020000000001@008611010400000 SIP/2.0
+From: <sip:008611010403001370002272@008611010403000>;tag=b55b4cf8-c700a8c0-1587-a3-1ba9ac5-a3
+To: <sip:0086110104000020000000000@31010400000>
+Call-ID: b55b4cf8-c700a8c0-1587-a3-5eacf182-a3@008631010403000
+CSeq: 1856483244 MESSAGE
+Via: SIP/2.0/UDP 192.168.0.199:5511;rport;branch=z9hG4bK-a3-27e0b-71dd2b33
+Max-Forwards: 70
+Content-Type: Application/ECCS+xml
+Content-Length: 143
+<?xml version="1.0" ?>
+<Response>
+<CmdType>Broadcast</CmdType>
+<SN>992</SN>
+<DeviceID>008611010403001370002272</DeviceID>
+<Result>OK</Result>
+</Response>
+```
+
+#### c) The examples of SDP parameters are shown as follows:
+
+```
+v=0
+o=0086110106000020200000001 0 0 IN IP4 172.20.16.3
+s=Play
+c=IN IP4 172.20.16.3
+t=0 0
+m=audio 8000 RTP/AVP 8
+a=sendonly
+a=rtpmap:8 PCMA/8000
+y=01000000001
+f=v////a/1/8/1
+```
+
+### 8.12.3 Audio intercom
+
+The audio intercom function achieves the one-to-one audio intercom function between the centre user and the front-end user.
+
+The audio intercom function is achieved by combining the following two independent processes.
+
+- The centre user acquires the real-time media stream of the PU through the real-time media stream function in clause 8.2.
+- The centre user sends the real-time audio stream to the PU through the audio broadcast function in clause 8.12.1; for the packaging format of the audio stream, see the specification of the audio stream RTP packaging in clause 7.6.2.
+
+## 8.13 Instant image snapshot
+
+### 8.13.1 Basic requirements
+
+The source sends the snapshot command to the target, and the snapshot is achieved by the MESSAGE method of [IETF RFC 3428].
+
+The sources include a CU, CPG or the other CCS with SRG, and the targets include a PU, CPG or the other CCS with SRG.
+
+After the source sends the snapshot command to the target, the target sends a response command to represent the executive result. For the signalling process, see clause 8.13.2.
+
+### 8.13.2 Signalling process
+
+For an instant image snapshot signalling flow, see Figure 8-22.
+
+![Sequence diagram showing the signalling flow of an instant image snapshot between Source, CCS, and Target.](e4aab374983ba0fc24496fe7cd11c06c_img.jpg)
+
+```
+sequenceDiagram
+    participant Source
+    participant CCS
+    participant Target
+    Note left of Source: Source sends snapshot request to CCS
+    Source->>CCS: 1: Message (Snapshot request command)
+    CCS-->>Source: 2: 200 OK
+    Note right of CCS: CCS forwards snapshot request to Target
+    CCS->>Target: 3: Message (Snapshot request command)
+    Target-->>CCS: 4: 200 OK
+    Note right of CCS: CCS sends snapshot response to Target
+    CCS->>Target: 5: Message (snapshot response command)
+    Target-->>CCS: 6: 200 OK
+    Note right of CCS: CCS forwards snapshot response to Source
+    CCS->>Source: 7: Message (Snapshot response command)
+    Source-->>CCS: 8: 200 OK
+    Note right of CCS: CCS initiates image download to Target
+    CCS-->>Target: Download image
+    Target-->>CCS: Image data
+    CCS-->>Source: Image data
+```
+
+The diagram illustrates the signalling flow for an instant image snapshot. It involves three participants: Source, CCS, and Target. The process begins with the Source sending a 'Message (Snapshot request command)' to the CCS. The CCS responds with '200 OK'. Next, the CCS sends a 'Message (Snapshot request command)' to the Target. The Target responds with '200 OK'. Then, the CCS sends a 'Message (snapshot response command)' to the Target. The Target responds with '200 OK'. Finally, the CCS sends a 'Message (Snapshot response command)' to the Source, which responds with '200 OK'. The CCS then initiates the 'Download image' process with the Target, which returns 'Image data' to the CCS, which in turn returns it to the Source.
+
+Sequence diagram showing the signalling flow of an instant image snapshot between Source, CCS, and Target.
+
+H.627(20)\_F8-22
+
+**Figure 8-22 – Signalling flow of an instant image snapshot**
+
+The instant image snapshot signalling flow description is as follows.
+
+- The source sends snapshot commands to the CCS, and the snapshot commands are carried in the message body with the MESSAGE method.
+
+- The CCS replies with a 200 OK response after receiving the commands.
+- The CCS sends snapshot commands to the target, and the snapshot 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 snapshot response commands to the CCS, and the snapshot response commands are carried in the message body by the MESSAGE method.
+- The CCS replies with a 200 OK response after receiving the commands.
+- The CCS forwards snapshot response commands to the source, and the snapshot response commands are carried in the message body by the MESSAGE method.
+- The source replies with a 200 OK response after receiving the commands.
+
+See the examples of instant image snapshot messages in clause 8.13.4.
+
+NOTE – "Download image" in Figure 8-22 does not lie within the scope of this Recommendation. The URL returned by the target is effective within 1 h.
+
+### 8.13.3 Protocol interface
+
+The Content-type field of the MESSAGE header is Content-type: Application/ECCS+xml.
+
+The instant image snapshot command and instant image snapshot response command are specified in the ECCS, for a detailed description, see the instant image snapshot command in clause A.2.3 a) and instant image snapshot response in clause A.2.6.
+
+### 8.13.4 Examples of instant image snapshot messages
+
+- a) MESSAGE sip: target code@target domain name or IP address port SIP/2.0
+
+```
+To: <sip: target code@target domain name>
+Content-Length: Byte length of message body
+CSeq: 2 MESSAGE
+Call-ID: a84b4c76e66710
+Via: SIP/2.0/UDP source domain name or IP address
+From: <sip: source code@source domain name>; tag=e40807c0
+Content-Type: Application/ECCS+xml
+Max-Forwards: 70
+<?xml version="1.0"?>
+<Control>
+<CmdType>DeviceControl</CmdType>
+<SN>17</SN>
+<DeviceID>008611010000002020000001</DeviceID>
+<CaptureCmd>Snapshot</CaptureCmd>
+</Control>
+```
+
+- b) SIP/2.0 200 OK
+
+```
+Via: SIP/2.0/UDP source domain name or IP address
+From: <sip: source code@source domain name>; tag=e40807c0
+To: <sip: Target code@target domain name>; tag=852843529
+Call-ID: a84b4c76e66710
+CSeq: 2 MESSAGE
+Content-Length: 0
+```
+
+- c) MESSAGE sip: target code@target domain name or IP address port SIP/2.0
+
+```
+To: <sip: target code@target domain name>
+Content-Length: Byte length of message body
+CSeq: 2 MESSAGE
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+```
+
+```
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: source code@source domain name>; tag=e40807c0
+Content-Type: Application/ECCS+xml
+Max-Forwards: 70
+<?xml version="1.0"?>
+<Control>
+<CmdType>DeviceControl</CmdType>
+<SN>17</SN>
+<DeviceID>008611010000002020000001</DeviceID>
+<CaptureCmd> Snapshot </CaptureCmd>
+</Control>
+
+```
+
+##### **d) SIP/2.0 200 OK**
+
+```
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: source code@source domain name>; tag=e40807c0
+To: <sip: Target code@target domain name>; tag=852843529
+Call-ID: wlss-3a65dfb6-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+CSeq: 2 MESSAGE
+Content-Length: 0
+
+```
+
+#### **e) MESSAGE sip: source code@source domain name or IP address port SIP/2.0**
+
+```
+
+Via: SIP/2.0/UDP target domain name or IP address
+From: <sip: Target code@target domain name>; tag=852843529
+To: <sip: source code@source domain name>
+Call-ID: de432gtf51u870
+CSeq: 2 MESSAGE
+Max-Forwards: 70
+Content-Type: Application/ECCS+xml
+Content-Length: Byte length of message body
+<?xml version="1.0"?>
+<Response>
+<CmdType>DeviceControl</CmdType>
+<SN>17</SN>
+<DeviceID>008611010000002020000001</DeviceID>
+<CaptureCmd> Snapshot </CaptureCmd>
+<URL>http://ip:port/FileService/DownloadFile?filesessionid=F5IQ3O64V88UF000
+B1G5U39R3C</URL>
+<Result>OK</Result>
+</Response>
+
+```
+
+#### **f) SIP/2.0 200 OK**
+
+```
+
+To: <sip: source code@source domain name>; tag=e40807c0
+Content-Length: 0
+CSeq: 2 MESSAGE
+Call-ID: de432gtf51u870
+Via: SIP/2.0/UDP target domain name or IP address
+From: <sip: Target code@target domain name>; tag=852843529
+
+```
+
+#### **g) MESSAGE sip: source code@source domain name or IP address port SIP/2.0**
+
+```
+
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: Target code@target domain name>; tag=852843529
+To: <sip: source code@source domain name>
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+CSeq: 2 MESSAGE
+Max-Forwards: 70
+Content-Type: Application/ECCS+xml
+Content-Length: Byte length of message body
+<?xml version="1.0"?>
+
+```
+
+```
+<Response>
+<CmdType>DeviceControl</CmdType>
+<SN>17</SN>
+<DeviceID>0086110100000020200000001</DeviceID>
+<CaptureCmd> Snapshot </CaptureCmd>
+<URL>http://ip:port/FileService/DownloadFile?filesessionid=F5IQ3O64V88UF000
+B1G5U39R3C</URL>
+<Result>OK</Result>
+</Response>
+```
+
+#### h) SIP/2.0 200 OK
+
+```
+To: <sip: source code@source domain name>; tag=e40807c0
+Content-Length: 0
+CSeq: 2 MESSAGE
+Call-ID: wlss-dc907ta2-7ee86970ea84c5b2284ad158b3d4fdee@172.18.16.5
+Via: SIP/2.0/UDP CCS domain name or IP address
+From: <sip: Target code@target domain name>; tag=852843529
+```
+
+# Annex A
+
+## Extended control command set
+
+(This annex forms an integral part of this Recommendation.)
+
+## A.1 Overall requirements
+
+The ID values in the From and To header field URI in the ECCS message are used as the message source and target identification. The ID value in the To header field URI in the ECCS response command shall be the ID value in the From header field URI of the request command. The SN value in the ECCS message is used for matching with the request command, and the SN value in the response command shall be the SN value in the request command. The administrative zone parameters in the ECCS message adopt the digital coding specified in [ITU-T H.626V2], and the value is of four digits for country or area level, of eight for zone level.
+
+## A.2 Command definitions
+
+### A.2.1 Names and descriptions of commands
+
+The names and descriptions of the commands in the application process are as shown in Table A.1.
+
+**Table A.1 – Function descriptions of extended control commands**
+
+| Classification   | Name     | Description                     |
+|------------------|----------|---------------------------------|
+| Request command  | Control  | Control operation               |
+|                  | Query    | Query operation                 |
+|                  | Notify   | Notification operation          |
+| Response command | Response | Response to a request operation |
+
+The header file of the request command structure is as follows.
+
+```
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element ref="Control"/>
+    <element ref="Query"/>
+    <element ref="Notify"/>
+  </choice>
+</schema>
+```
+
+Header file of response command structure
+
+```
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <element ref="Response"/>
+</schema>
+```
+
+### A.2.2 Specifications of global data types
+
+The global data types specified in this Recommendation are shown in Table A.2. The global data types indicate the XML Schema type or direct subitem of Schema element, and can be cited at different positions.
+
+**Table A.2 – Global data type names and descriptions**
+
+| Name                    | Description                    |
+|-------------------------|--------------------------------|
+| deviceIDType            | Device code type               |
+| statusType              | Status type                    |
+| resultType              | Result type                    |
+| PTZType                 | Control code type              |
+| recordType              | Recording control type         |
+| guardType               | Guard/Unguard control type     |
+| itemType                | Device item type               |
+| itemFileType            | File item type                 |
+| PTZPreciseCtrlType      | PTZ precise control type       |
+| OSDConfigType           | OSD configuration type         |
+| videoParamAttributeType | Video parameter attribute type |
+| itemMobilePositionType  | Mobile device location type    |
+
+The global data types are specified as follows.
+
+```
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <simpleType name="deviceIDType">
+    <restriction base="ID">
+      <!--when representing the administrative zone ID, the value is 4-bit
+country or area code + zone code (the 8-bit zone code can be divided according
+to the specific situation, for example, the 8-bit zone code is divided by
+every two digits, the administrative zone value is 6, 8, 10, 12 bits); when
+representing device ID/ VSS ID, the value is 24 bits.-->
+      <pattern value="(\d{6}|\d{8}|\d{10}|\d{12}|\d{24})"/>
+    </restriction>
+  </simpleType>
+  <simpleType name="statusType">
+    <restriction base="string">
+      <enumeration value="ON"/>
+      <enumeration value="OFF"/>
+    </restriction>
+  </simpleType>
+  <simpleType name="resultType">
+    <restriction base="string">
+      <enumeration value="OK"/>
+      <enumeration value="ERROR"/>
+    </restriction>
+  </simpleType>
+  <simpleType name="PTZType">
+    <restriction base="string">
+      <length value="8"/>
+    </restriction>
+  </simpleType>
+  <simpleType name="recordType">
+    <restriction base="string">
+      <enumeration value="Record"/>
+      <enumeration value="StopRecord"/>
+    </restriction>
+  </simpleType>
+  <simpleType name="guardType">
+    <restriction base="string">
+      <enumeration value="SetGuard"/>
+      <enumeration value="ResetGuard"/>
+    </restriction>
+  </simpleType>
+</schema>
+```
+
+```
+
+    </restriction>
+  </simpleType>
+  <complexType name="itemType">
+    <sequence>
+      <!-- Device/administrative zone/VSS code (required) -->
+      <element name="DeviceID" type="deviceIDType"/>
+      <!-- Device/administrative zone/VSS name (required) -->
+      <element name="Name" type="string"/>
+      <!-- if it is a device, device manufacturer (required) -->
+      <element name="Manufacturer" type="string"/>
+      <!-- if it is a device, device model (required) -->
+      <element name="Model" type="string"/>
+      <!-- if it is a device, device owner (required) -->
+      <element name="Owner" type="string"/>
+      <!-- if it is a device, ZoneCode (required) -->
+      <element name="ZoneCode" type="string"/>
+      <!-- Block (optional) -->
+      <element name="Block" type="string"/>
+      <!-- if it is a device, installation address (required) -->
+      <element name="Address" type="string"/>
+      <!-- if it is a device, whether there is a sub device (required), 1-
+yes, 0-no -->
+      <element name="Parental" type="integer" minInclusive="0"/>
+      <!-- if it is a device, the parent node ID (required): if there is no
+parent device, it is the system ID of the device; if there is a parent device,
+it is the parent device ID; if it is a VSS, the parent node ID (it is required
+if there is a parent node VSS): it is the parent node VSS ID;
+if it is an administrative zone, no parent node ID; can be multi-value,
+separated by "/" -->
+      <element name="ParentID" type="string"/>
+      <!-- Device /VSS IPV4 address (optional) -->
+      <element name="IPAddress" type="string"/>
+      <!-- Device /VSS port (optional) -->
+      <element name="Port" type="integer"/>
+      <!-- Device password (optional) -->
+      <element name="Password" type="string"/>
+      <!-- Device status (optional) -->
+      <element name="Status" type=" statusType"/>
+      <!-- if it is a device, longitude (optional) WGS-84 coordinate system-
+-->
+      <element name="Longitude" type="double" minOccurs="0"/>
+      <!-- if it is a device, latitude (optional) WGS-84 coordinate system--
+-->
+      <element name="Latitude" type="double" minOccurs="0"/>
+      <Info>
+        <!-- Camera type extension, markup camera type: 1-ballhead camera; 2-
+hemisphere; 3-fixed bolt; 4-remote control bolt; 5-remote control hemisphere;
+6-multicamera; 7-integrated gun ball linkage camera, can be multi-value,
+separated by "/". It is optional when the directory entry is camera. -->
+        <element name="PTZType" type="string" minOccurs="0"/>
+        <!-- Camera photoelectric imaging type. 1-visible light imaging; 2-
+thermal imaging; 9-other. It is optional when the directory entry is camera. -
+-->
+        <element name="PhotoelectricImagingType" type="string" minOccurs="0"/>
+        <!-- Camera position type extension. 1-Inter-provincial checkpoint, 2-
+party and government organizations, 3-station and dock, 4-central plaza, 5-
+stadium, 6-business center, 7-religious venue, 8-campus surrounding, 9-
+security complex area, 10-arterial traffic. It is optional when the directory
+entry is camera. -->
+        <element name="PositionType" type="string" minOccurs="0"/>
+        <!-- Outdoor and indoor camera mounting position type. 1-outdoor, 2-
+indoor. It is optional when the directory entry is camera, and defaults as 1.
+-->
+        <element name="RoomType" type="integer" default="1"/>
+
+```
+
+```
+
+    <!-- Camera fill light type. 1-no fill light, 2-infrared fill light,
+3-white fill light, 4-laser fill light, 9-othe. It is optional when the
+directory entry is camera, and defaults as 1. -->
+    <element name="SupplyLightType" type="integer" default="1"/>
+    <!-- Camera surveillance direction (optical axis direction) type. 1-
+East (west to east), 2-west (east to west), 3-south (north to south), 4-north
+(south to north), 5-southeast (northwest to southeast), 6-northeast (southwest
+to northeast), 7-southwest (northeast to southwest), 8-northwest (southeast to
+northwest), 9-other. It is optional when the directory entry is the fixed
+camera or set to be the guard camera. -->
+    <element name="DirectionType" type="integer" minOccurs="0"/>
+    <!-- Resolution supported by the camera, there are multiple resolution
+values separated with "/". For the resolution values, see the SDP f field
+provisions of clause 7.7. It is optional when the directory entry is camera. -
+->
+    <element name="Resolution" type="string" minOccurs="0"/>
+    <!-- List of stream numbers supported by the camera, it is used to
+specify the stream numbers during live video on demand, with multiple values
+separated by "/". For example, "0/1/2" indicates support for the primary
+stream, the secondary stream and the second auxiliary stream.-->
+    <element name=" StreamNameList " type="string" minOccurs="0"/>
+    <!-- Download speed range (optional), the optional parameters are
+separated with "/"; if the device supports 1, 2 and 4 times the speed, it
+shall be written as "1/2/4"-->
+    <element name="DownloadSpeed" type="string" minOccurs="0"/>
+    <!-- Mobile acquisition device type (it is required if the device type
+code is 138); 1-camera on mobile robot; 2-law enforcement recorder; 3-mobile
+soldier equipment; 4-vehicle video recording equipment; 5-unmanned aerial
+vehicle camera; 9-other -->
+    <element name="MobileDevieType" type="integer" minOccurs="0"/>
+    <!-- Camera horizontal field of view angle (optional), the value
+range is greater than 0 degrees and less than or equal to 360 degrees -->
+    <element name="HorizontalFieldAngle" type="double" minOccurs="0"/>
+    <!-- Camera vertical field of view angle (optional), the value range
+is greater than 0 degrees and less than or equal to 360 degrees -->
+    <element name="VerticalFieldAngle" type="double" minOccurs="0"/>
+    <!-- Camera visible distance (optional), unit: meter -->
+    <element name=" MaxViewDistance " type="double" minOccurs="0"/>
+    <!-- The common name of the point (optional), if there are landmark
+buildings, places or monitoring points near the monitoring point, it can be
+filled in the landmark construction name and location.-->
+    <element name="PointCommonName" type="string" minOccurs="0"/>
+    <!-- Device MAC address (optional), in the format of "XX-XX-XX-XX-XX-
+XX", where "XX" represents two hexadecimal numbers, separated by "-"-->
+    <element name="MAC" type="string" minOccurs="0"/>
+    <!-- Camera function type, 01-facebayonet; 02-person bayonet; 03-motor
+vehicle bayonet; 04-non-motor vehicle bayonet; 05-item bayonet; 99-other,
+multiple selection, parameters are separated by "/". Optional when it is a
+camera -->
+    <element name="FunctionType" type="string" minOccurs="0"/>
+    <!-- Camera video encoding format (optional), the value is specified
+in the SDP f field in clause 7.7 -->
+    <element name="EncodeType" type="string" minOccurs="0"/>
+    <!-- Camera installation time (optional) -->
+    <element name="InstallTime" type="dateTime" minOccurs="0"/>
+    <!-- Name of camera management unit (optional) -->
+    <element name="ManagementUnit" type="string" minOccurs="0"/>
+    <!-- Contact information (phone number) of the contact person of the
+management unit to which the camera belongs (optional)-->
+    <element name="ContactInfo" type="string" minOccurs="0"/>
+    <!-- Video save days (optional) -->
+    <element name="RecordSaveDays" type="integer" minOccurs="0"/>
+  </Info>
+</sequence>
+
+```
+
+```
+
+</complexType>
+<complexType name="itemFileType">
+  <sequence>
+    <!-- Device ID (required) -->
+    <element name="DeviceID" type="deviceIDType"/>
+    <!-- Device name (required) -->
+    <element name="Name" type="string"/>
+    <!-- File path name (optional)-->
+    <element name="FilePath" type="string" minOccurs="0"/>
+    <!-- Recording address (optional)-->
+    <element name="Address" type="string" minOccurs="0"/>
+    <!-- Recording start time (optional)-->
+    <element name="StartTime" type="dateTime" minOccurs="0"/>
+    <!-- Recording end time (optional)-->
+    <element name="EndTime" type="dateTime" minOccurs="0"/>
+    <!-- Video type (optional) time or alarm or manual-->
+    <element name="Type" type="string" minOccurs="0"/>
+    <!-- Recorder ID (optional) -->
+    <element name="RecorderID" type="string" minOccurs="0"/>
+    <!-- Video file size, unit: Byte (optional) -->
+    <element name="FileSize" type="string" minOccurs="0"/>
+    <!-- PU/VSS ID for storing video files (required for fuzzy query) -->
+    <element name="RecordLocation" type="deviceIDType"/>
+  </sequence>
+</complexType>
+<complexType name="PTZPreciseCtrlType">
+  <!-- Set the horizontalangle of the cradle head (optional), 0~360.00
+degrees.
+0 degree: absolute 0 degree is based on the horizontal optocoupler of the
+ballhead camera, relative 0 degree is subject to the actual setting.
+The user first sets the relative origin coordinates, determines the relative 0
+degree position, and sets the cradle head angle with respect to the relative 0
+degree as the starting point.
+Direction: the ballhead camera is installed upright, viewed from the top down,
+clockwise direction increases, counter clockwise direction decreases;
+If the received command parameter exceeds the actual rotation angle limit of
+the device, it will move to the actual maximum angle.-->
+  <element name="Pan" type="double" minOccurs="0"/>
+  <!-- Set the vertical angle of the cradle head (optional), The general
+value is -30.00~90.00 degrees;
+0 degree: when the ballhead camera is installed vertically, the horizontal
+position of the lens is 0 degree.
+Direction: when the ballhead camera is installed vertically, if the lens turn
+up, the degree will decrease; if the lens turn down, the degree will increase.
+If the received command parameter exceeds the actual reach of the device,
+then move to the actual maximum limit angle position.
+For example, if the value of receiving command value is -28.00 and the maximum
+limit angle is -20.00, it is enough to move to -20.00.-->
+  <element name="Tilt" type="double" minOccurs="0"/>
+  <!-- Set the zoom factor (optional), the value is generally greater than
+1.00.
+If the receiving command parameter is within the optical zoom maximum value,
+it will move to the corresponding optical zoom factor.
+When the optical zoom maximum value is exceeded, the corresponding digital
+zoom will be activated. The device shall check the validity of the parameter
+value.
+For example, if the device optical zoom maximum value is 36.00 and the
+receiving command parameter is 72.00, the action will be 36.00x optical zoom
+and 36.00x digital zoom (if the device digital zoom maximum value is less than
+36.00, the actual maximum value shall be executed) .-->
+  <element name="Zoom" type="double" minOccurs="0"/>
+</complexType>
+<element name="OSDConfigType" minOccurs="0">
+  <complexType>
+
+```
+
+```
+
+<sequence>
+  <!-- Configure window length pixel values (required) -->
+  <element name="Length" type="integer"/>
+  <!-- Configure window width pixel values (required) -->
+  <element name="Width" type="integer"/>
+  <!-- Time X pixel coordinates (required), the pixel in the upper left
+corner of the playback window is the origin, and the horizontal right is
+positive.-->
+  <element name="TimeX" type="integer"/>
+  <!-- Time Y pixel coordinates (required), the pixel in the upper left
+corner of the playback window is the origin, and the vertical down is
+positive-->
+  <element name="TimeY" type="integer"/>
+  <!-- Display time switch (optional), 0-off; 1-open (default value) -->
+  <element name="TimeEnable" type="integer" default="1"/>
+  <!-- Time display type (optional):
+0- Year-Month-Day Hour:Minute:Second
+1- Year Month Day Hour:Minute:Second
+2- Day/Month/Year Hour:Minute:Second
+3- Month /Day/Year Hour:Minute:Second -->
+  <element name="TimeType" type="integer" minOccurs="0"/>
+  <!-- Display text switch (optional), 0-off; 1-open (default value) -->
+  <element name="TextEnable" type="integer" default="1"/>
+  <!-- Text list (optional) -->
+  <element name="Item" minOccurs="0" maxOccurs="8"/>
+  <complexType>
+    <sequence>
+      <!-- Text content, length range 0 ~ 32 (required) -->
+      <element name="Text" type="string"/>
+      <!-- Text X coordinate (required) -->
+      <element name="X" type="integer"/>
+      <!-- Text Y coordinate (required) -->
+      <element name="Y" type="integer"/>
+    </sequence>
+  </complexType>
+</sequence>
+</complexType>
+</element>
+<complexType name="videoParamAttributeType">
+  <sequence>
+    <!-- Video stream name (required), such as the first video stream
+Stream1, the second video stream Stream2 -->
+    <element name="StreamName" type="string"/>
+    <!-- Video stream number (required), used to specify the stream number
+in real-time video and audio on demand. 0-main stream; 1-substream; 2-second
+auxiliary stream, and soon-->
+    <element name="StreamNumber" type="integer"/>
+    <!-- The current configuration value of the video encoding format
+(required). The value is specified in the SDP f field in clause 7.7.-->
+    <element name="VideoFormat" type="string"/>
+    <!-- Resolution current configuration value (required). The value is
+specified in the SDP f field in clause 7.7.-->
+    <element name="Resolution" type="string"/>
+    <!-- Frame rate current configuration value (required). The value is
+specified in the SDP f field in clause 7.7.-->
+    <element name="FrameRate" type="string"/>
+    <!-- Rate type configuration value (required).The value is specified in
+the SDP f field in clause 7.7.-->
+    <element name="BitRateType" type="string"/>
+    <!-- Video bitrate configuration value (required for fixed bitrate), The
+value is specified in the SDP f field in clause 7.7.-->
+    <element name="VideoBitRate" type="string" minOccurs="0"/>
+  </sequence>
+</complexType>
+
+```
+
+```
+
+<complexType name="itemMobilePositionType">
+  <sequence>
+    <!-- Target device code (required) -->
+    <element name="DeviceID" type="deviceIDType"/>
+    <!-- Location collection time (required) -->
+    <element name="CaptureTime" type="dateTime"/>
+    <!-- Longitude (required), WGS-84 coordinate system -->
+    <element name="Longitude" type="double"/>
+    <!-- Latitude (required), WGS-84 coordinate system -->
+    <element name="Latitude" type="double"/>
+    <!-- Speed, unit: km/h (optional) -->
+    <element name="Speed" type="double" minOccurs="0"/>
+    <!-- Direction angle (optional), the value is the clockwise angle
+between the current camera direction and the north, the value range is greater
+than or equal to 0 less than 360, unit: degree -->
+    <element name="Direction" type="double" minOccurs="0"/>
+    <!-- Altitude, unit: meter (optional) -->
+    <element name="Altitude" type="double" minOccurs="0"/>
+    <!-- Ground height, unit: meter (optional) -->
+    <element name="Height" type="double" minOccurs="0"/>
+  </sequence>
+</complexType>
+</schema>
+
+```
+
+### A.2.3 Control commands
+
+The control command definitions are shown in a) and b)
+
+#### a) Control command
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Control">
+      <complexType>
+        <sequence>
+          <!-- Control request command series is shown as follows-->
+          <!-- Command type: device control (required)-->
+          <element name="CmdType" fixed="DeviceControl"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device ID (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- PTZ control command (optional, the control code shall comply
+with the provisions in clause A.3-->
+          <element name=" PTZCmd " type="PTZType"/>
+          <!-- Ballhead camera/cradle control command additional parameters
+(optional)-->
+          <element name="PTZCmdParams" minOccurs="0">
+            <sequence>
+              <!-- Preset name (optional when PTZCmd is a preset position
+setting command)-->
+              <element name="PresetName" type="string" minOccurs="0"/>
+              <!-- Cruise track name (optional when PTZCmd is a cruise track
+setting command)-->
+              <element name="CruiseTrackName" type="string" minOccurs="0"/>
+            </sequence>
+          </element>
+          <!-- Teleboot control command (optional) -->
+          <element name="TeleBoot" minOccurs="0">
+            <restriction base="string">
+              <enumeration value="Boot"/>
+            </restriction>
+          </element>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+
+```
+
+```
+
+</element>
+<!-- Record control command (optional) -->
+<element name="RecordCmd" type="recordType" minOccurs="0"/>
+<!-- Guard/ Unguard command (optional) -->
+<element name="GuardCmd" type="guardType" minOccurs="0"/>
+<!-- Alarm reset command (optional) -->
+<element name="AlarmCmd" minOccurs="0">
+  <restriction base="string">
+    <enumeration value="ResetAlarm"/>
+  </restriction>
+</element>
+<!-- instant image snapshot command (optional) -->
+<element name="CaptureCmd" minOccurs="0">
+  <restriction base="string">
+    <enumeration value="Snapshot"/>
+  </restriction>
+</element>
+<!--Mandatory key frame command (optional), the device shall send an
+IDR frame after receiving this command (optional) -->
+<element name="IFameCmd" minOccurs="0">
+  <restriction base="string">
+    <enumeration value="Send"/>
+  </restriction>
+</element>
+<!-- Drag zoom-in control command (optional) -->
+<element name="DragZoomIn" type="string" minOccurs="0"/>
+<complexType>
+  <sequence>
+    <!--Length pixel value of play window (required) -->
+    <element name="Length" type="integer"/>
+    <!--Width pixel value of play window (required) -->
+    <element name="Width" type="integer"/>
+    <!-- X-axis coordinate pixel value of drop-down box center-->
+    <element name="MidPointX" type="integer"/>
+    <!-- Y-axis coordinate pixel value of drop-down box center-->
+    <element name="MidPointY" type="integer"/>
+    <!--Length pixel value of drop-down box (required) -->
+    <element name="LengthX" type="integer"/>
+    <!--Width pixel value of drop-down box (required) -->
+    <element name="LengthY" type="integer"/>
+  </sequence>
+</complexType>
+<!-- Guard control command (optional) -->
+<element name="HomePosition" type="string" minOccurs="0"/>
+<complexType>
+  <sequence>
+    <!-- Guard enable 1-enabled, 0-disabled (required)-->
+    <element name="Enabled" type="integer"/>
+    <!-- Automatic rest time interval, used in guard enabling, unit:
+second (s) (optional) -->
+    <element name="ResetTime" type="integer" minOccurs="0"/>
+    <!-- Call preset position number, used in guard enabling, the
+value range: 0-255 (optional) -->
+    <element name="PresetIndex" minOccurs="0"/>
+    <simpleType>
+      <restriction base="integer">
+        <minInclusive value="0"/>
+        <maxInclusive value="255"/>
+      </restriction>
+    </simpleType>
+  </sequence>
+</complexType>
+<!--This item is expanded during alarm reset control, and carries
+alarm method and alarm type. -->
+
+```
+
+```
+
+<element name="Info" minOccurs="0">
+  <complexType>
+    <sequence>
+      <!--Alarm method type of reset alarm -->
+      <element name="AlarmMethod" type="string" minOccurs="0"/>
+      <!--Alarm type of reset alarm -->
+      <element name="AlarmType" type="string" minOccurs="0"/>
+    </sequence>
+  </complexType>
+</element>
+<!--PTZ precise control command (optional) -->
+<element name="PTZControl" type="PTZPreciseCtrlType" minOccurs="0"/>
+<!--PU OSD configuration commands (optional) -->
+<element name="OSDConfig" type="OSDConfigType" minOccurs="0"/>
+<!--Extended information, multiple -->
+<element name="Info" minOccurs="0" maxOccurs="unbounded">
+  <restriction base="string">
+    <maxLength value="1024"/>
+  </restriction>
+</element>
+</sequence>
+</complexType>
+</element>
+</choice>
+</schema>
+
+```
+
+NOTE – The drag zoom-in command is used for zooming in the image in the play window selected box to the whole play window; the drag zoom-out command is used for zooming out the image of the whole play window into the play window selected box; the coordinate system in the command takes the top left corner of the play window as the origin, and the coordinate values are expressed in pixels.
+
+#### b) Device configuration
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Control"/>
+    <complexType>
+      <sequence>
+        <!-- Command type: device configuration (required) -->
+        <element name="CmdType" fixed="DeviceConfig"/>
+        <!-- Command SN (required) -->
+        <element name="SN" type="integer" minInclusive="1"/>
+        <!-- Target device ID (required) -->
+        <element name="DeviceID" type="deviceIDType"/>
+        <!-- Basic parameters (optional) -->
+        <element name="BasicParam" minOccurs="0">
+          <complexType>
+            <sequence>
+              <!-- Device name (optional) -->
+              <element name="Name" type="string" minOccurs="0"/>
+              <!-- Registration expiration time (optional) -->
+              <element name="Expiration" type="integer" minOccurs="0"/>
+              <!-- heartbeat interval (optional) -->
+              <element name="HeartBeatInterval" type="integer" minOccurs="0"/>
+              <!-- Heartbeat timeout count (optional) -->
+              <element name="HeartBeatCount" type="integer" minOccurs="0"/>
+            </sequence>
+          </complexType>
+        </element>
+      </sequence>
+    </complexType>
+  </choice>
+</schema>
+
+```
+
+```
+</schema>
+```
+
+### A.2.4 Query commands
+
+The query command definitions are shown in a) to m)
+
+#### a) Device status query request
+
+```
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Query">
+      <complexType>
+        <sequence>
+          <!-- Query request command series is shown as follows.-->
+          <!-- Command type: device status query (required)-->
+          <element name="CmdType" fixed="DeviceStatus"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device ID (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+```
+
+#### b) Device directory information query request
+
+```
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Query">
+      <complexType>
+        <sequence>
+          <!-- Query request command series is shown as follows.-->
+          <!-- Command type: device directory query (required)-->
+          <element name="CmdType" fixed="Catalog"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device/administrative zone/VSS ID (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Start time of adding the device (optional), null shows no
+limit. -->
+          <element name="StartTime" type="dateTime"/>
+          <!-- End time of adding the device (optional), null shows the
+current time.-->
+          <element name="EndTime" type="dateTime"/>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+```
+
+#### c) Device information query request
+
+```
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Query">
+      <complexType>
+        <sequence>
+```
+
+```
+
+    <!-- Query request command series is shown as follows.-->
+    <!-- Command type: device information query (required)-->
+    <element name="CmdType" fixed="DeviceInfo"/>
+    <!-- Command SN (required) -->
+    <element name="SN" type="integer" minInclusive="1"/>
+    <!-- Target device ID (required) -->
+    <element name="DeviceID" type="deviceIDType"/>
+  </sequence>
+</complexType>
+</element>
+</choice>
+</schema>
+
+```
+
+#### d) File directory retrieval request
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Query">
+      <complexType>
+        <sequence>
+          <!-- Query request command series is shown as follows.-->
+          <!--Command type: file directory retrieval (required) -->
+          <element name="CmdType" fixed="RecordInfo"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- device ID (required)-->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!--Recording start time (required)-->
+          <element name="StartTime" type="dateTime"/>
+          <!--Recording end time (required)-->
+          <element name="EndTime" type="dateTime"/>
+          <!-- File path name (optional)-->
+          <element name="FilePath" type="string"/>
+          <!-- Recording address (optional, support incomplete query)-->
+          <element name="Address" type="string"/>
+          <!-- Video type (optional) time or alarm or manual or all-->
+          <element name="Type" type="string"/>
+          <!-- Recorder ID (optional) -->
+          <element name="RecorderID" type="string"/>
+          <!--Video fuzzy query type (optional) defaults as 0; 0: fuzzy query
+is not conducted; at the moment, the query recording position is determined
+according to the ID value in To header field URI of the SIP message; if the ID
+value is the VSS ID in this domain, perform historical record retrieval of the
+center; if the ID value is the PU's ID, perform the historical record
+retrieval of the PU; 1: conduct fuzzy query; at the moment the domain of the
+device shall perform center retrieval and PU retrieval simultaneously, and
+return the results in the unified form. -->
+          <element name="IndistinctQuery" type="string"/>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+
+```
+
+#### e) Alarm query
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Query">
+      <complexType>
+
+```
+
+```
+
+<sequence>
+  <!-- Query request command series is shown as follows.-->
+  <!-- Command type: alarm query (required)-->
+  <element name="CmdType" fixed="Alarm"/>
+  <!-- Command SN (required) -->
+  <element name="SN" type="integer" minInclusive="1"/>
+  <!-- Alarm device ID or alarm center ID (10-digit) (required)-->
+  <element name="DeviceID" type="deviceIDType"/>
+  <!--Start alarm priority (optional), 0-all, 1-first level alarm, 2-
+second level alarm, 3-third level alarm, 4-fourth level alarm-->
+  <element name="StartAlarmPriority" type="string"/>
+  <!--End alarm priority (optional), 0-all, 1-first level alarm, 2-
+second level alarm, 3-third level alarm, 4-fourth level alarm-->
+  <element name="EndAlarmPriority" type="string"/>
+  <!--Alarm method conditions (optional), 0-all, 1- telephone alarm,
+2-device alarm, 3-SMS alarm, 4-GPS alarm, 5-video alarm, 6-device fault alarm,
+7-other alarm; it can be combined directly, such as 12-telephone alarm or
+device alarm -->
+  <element name="AlarmMethod" type="string"/>
+  <!-- Alarm type-->
+  <element name="AlarmType" type="string"/>
+  <!--Start alarm time (optional)-->
+  <element name="StartAlarmTime" type="dateTime"/>
+  <element name="EndAlarmTime" type="dateTime"/>
+</sequence>
+</complexType>
+</element>
+</choice>
+</schema>
+
+```
+
+#### f) Device configuration query
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Query">
+      <complexType>
+        <sequence>
+          <!-- Query request command series is shown as follows.-->
+          <!-- Command type: device configuration query (required)-->
+          <element name="CmdType" fixed="ConfigDownload"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device ID (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Query configuration parameter type (required), the queryable
+configuration types include basic parameter configuration:
+BasicParam, video parameter range: VideoParamOpt, Video
+parameter current configuration: VideoParamConfig.Multiple
+configuration types can be enquired at the same time, and
+separated with "/", and multiple responses same as the SN
+value can be returned; each response corresponds to one
+configuration type. -->
+          <element name="ConfigType" type="string"/>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+
+```
+
+#### g) Device preset query
+
+```
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Query">
+      <complexType>
+        <sequence>
+          <!-- Query request command series is shown as follows.-->
+          <!-- Command type: preset position query (required)-->
+          <element name="CmdType" fixed="PresetQuery"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Query of target device ID (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+```
+
+#### h) Mobile device position data query
+
+```
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Query">
+      <complexType>
+        <sequence>
+          <!-- Query request command series is shown as follows.-->
+          <!-- Command type: mobile device position data query (required)-->
+          <element name="CmdType" fixed="MobilePosition"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Query of mobile device/VSS ID (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!--Mobile device position information reporting interval, unit: s,
+default value: 5 (optional)-->
+          <element name="Interval" type="integer" default="5"/>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+```
+
+#### i) Guard position information query
+
+```
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Query">
+      <complexType>
+        <sequence>
+          <!-- Query request command series is shown as follows.-->
+          <!-- Command type: guard position information query (required) -->
+          <element name="CmdType" fixed="HomePositionQuery"/>
+          <!-- Command serial number (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device code (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+```
+
+```
+
+    </element>
+  </choice>
+</schema>
+
+```
+
+#### j) Cruise track list query
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Query">
+      <complexType>
+        <sequence>
+          <!-- Query request command series is shown as follows.-->
+          <!-- Command type: cruise track list query (required) -->
+          <element name="CmdType" fixed="CruiseTrackListQuery"/>
+          <!-- Command serial number (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device code (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+
+```
+
+#### k) Cruise track query
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Query">
+      <complexType>
+        <sequence>
+          <!-- Query request command series is shown as follows.-->
+          <!-- Command type: cruise track query (required) -->
+          <element name="CmdType" fixed="CruiseTrackQuery"/>
+          <!-- Command serial number (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device code (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Track number (required): 0-first track; 1-second track-->
+          <element name="Number" type="integer"/>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+
+```
+
+#### l) PTZ precise status query
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Query">
+      <complexType>
+        <sequence>
+          <!-- Query request command series is shown as follows.-->
+          <!-- Command type: PTZ precise status query (required) -->
+          <element name="CmdType" fixed="PTZPosition"/>
+          <!-- Command serial number (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device code (required) -->
+
+```
+
+```
+
+        <element name="DeviceID" type="deviceIDType"/>
+      </sequence>
+    </complexType>
+  </element>
+</choice>
+</schema>
+
+```
+
+#### m) OSD information query
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Query">
+      <complexType>
+        <sequence>
+          <!-- Query request command series is shown as follows.-->
+          <!-- Command type: OSD information query (required) -->
+          <element name="CmdType" fixed="OSDQuery"/>
+          <!-- Command serial number (required)-->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device code (required)-->
+          <element name="DeviceID" type="deviceIDType"/>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+
+```
+
+### A.2.5 Notification commands
+
+The notification command definitions are shown in a) to e).
+
+#### a) Status information reporting
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Notify">
+      <complexType>
+        <sequence>
+          <!-- Notification request command series is shown as follows-->
+          <!-- Command type: device status information reporting (required) -->
+          <element name="CmdType" fixed="Keepalive"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Device/VSS ID of source device (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Work normally or not (required) -->
+          <element name="Status" type="resultType"/>
+          <!-- Fault device list -->
+          <element name="Info">
+            <complexType>
+              <sequence>
+                <element name="DeviceID" type="deviceIDType" minOccurs="0"
+maxOccurs="unbounded "/>
+              </sequence>
+            </complexType>
+          </element>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+
+```
+
+</schema>
+
+#### b) Alarm notification
+
+```
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Notify">
+      <complexType>
+        <sequence>
+          <!-- Notification request command series is shown as follows.-->
+          <!-- Command type: alarm notification (required)-->
+          <element name="CmdType" fixed="Alarm"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Alarm device ID or alarm center ID (10-digit) (required)-->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!--Alarm priority (required), 1-first level alarm, 2-second level
+alarm, 3-third level alarm, 4-fourth level alarm-->
+          <element name="AlarmPriority" type="string"/>
+          <!--Alarm method (optional), 1-telephone alarm, 2-device alarm, 3-
+SMS alarm, 4-GPS alarm, 5-video alarm, 6-device fault alarm, 7-other alarm -->
+          <element name="AlarmMethod" type="string"/>
+          <!--Alarm time (required)-->
+          <element name="AlarmTime" type="dateTime"/>
+          <!--Alarm description (optional)-->
+          <element name="AlarmDescription" type=" string "/>
+          <!-- Latitude and longitude information (optional)-->
+          <element name="Longitude" type="double" minOccurs="0"/>
+          <element name="Latitude" type="double" minOccurs="0"/>
+          <!-- Extended Info item carries the alarm type and alarm type
+parameter field-->
+          <element name="Info" minOccurs="0">
+            <complexType>
+              <sequence>
+                <!-- Alarm type. If the alarm method is 2, the message which
+does not carry AlarmType is the default alarm device for
+alarm; the value carrying AlarmType and corresponding
+alarm type are shown as follows: 1-video loss alarm; 2-
+device tamper alarm; 3-storage device disk full alarm; 4-
+device high-temperature alarm; 5-device low-temperature
+alarm. If the alarm method is 5, the values represent as
+follows:
+1-manual video alarm;
+2-moving object detection alarm;
+3-hangover detection alarm;
+5-trip wire detection alarm;
+6-intrusion detection alarm;
+7-reverse detection alarm; 8-loitering detection alarm;
+9-flow statistics alarm;
+10-density detection alarm;
+11-video anomaly detection alarm;
+12-quick motion alarm.
+If the alarm method is 6, the values represent as
+follows: 1-storage device disk fault alarm; 2-storage
+device fan fault alarm. -->
+                <element name="AlarmType" type="positiveInteger"/>
+                <!-- Alarm type extended parameter. <EventType>event
+type</EventType> can be carried in intrusion detection alarm, event type
+value: 1-enter area; 2-leave area. -->
+                <element name="AlarmTypeParam" type="string" minOccurs="0"/>
+              </sequence>
+            </complexType>
+          </element>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+```
+
+```
+
+        <element name="EventType" type="positiveInteger"
+minOccurs="0"/>
+      </sequence>
+    </complexType>
+  </sequence>
+</complexType>
+</element>
+<!--Extended information, multiple -->
+<element name="Info" minOccurs="0" maxOccurs="unbounded">
+  <restriction base="string">
+    <maxLength value="1024"/>
+  </restriction>
+</element>
+</sequence>
+</complexType>
+</element>
+</choice>
+</schema>
+
+```
+
+NOTE – After the device sends a notification that the alarm method is 2 "device alarm", the platform shall perform the "alarm reset" control operation in clause A.2.3 a), and then the device can send new notification of the device alarm.
+
+#### c) Media notification
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Notify">
+      <complexType>
+        <sequence>
+          <!-- Notification request command series is shown as follows.-->
+          <!-- Command type: media notification (required)-->
+          <element name="CmdType" fixed="MediaStatus"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Media stream sender ID (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Notification event type (required), the value "121" shows end
+of historical media file sending. -->
+          <element name="NotifyType" type="string"/>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+
+```
+
+#### d) Audio broadcast notification
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Notify">
+      <complexType>
+        <sequence>
+          <!-- Notification request command series is shown as follows.-->
+          <!-- Command type: audio broadcast notification (required)-->
+          <element name="CmdType" fixed="Broadcast"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Audio input device ID (required) -->
+          <element name="SourceID" type="deviceIDType"/>
+          <!-- Audio output device ID (required) -->
+
+```
+
+```
+
+        <element name="TargetID" type="deviceIDType"/>
+      </sequence>
+    </complexType>
+  </element>
+</choice>
+</schema>
+
+```
+
+#### e) Mobile device position data notification
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Notify">
+      <complexType>
+        <sequence>
+          <!-- Notification request command series is shown as follows.-->
+          <!-- Target device /VSS ID (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Command type: mobile device position data notification
+(required)-->
+          <element name="CmdType" fixed="MobilePosition"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Notification time (required) -->
+          <element name="Time" type="dateTime"/>
+          <!-- Total number of mobile device locations (required)-->
+          <element name="SumNum" type="integer"/>
+          <!-- Mobile device location list, Num indicates the number of list
+entries -->
+          <element name="DeviceList" minOccurs="0">
+            <complexType>
+              <choice minOccurs="0" maxOccurs="unbounded">
+                <element name="Item" type="itemMobilePositionType"/>
+              </choice>
+              <attribute name="Num" type="integer"/>
+            </complexType>
+          </element>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+
+```
+
+### A.2.6 Response commands
+
+The response command definitions are shown in a) to q).
+
+#### a) Device control response
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Response">
+      <complexType>
+        <sequence>
+          <!-- The query request response message is shown as follows.-->
+          <!-- Command type: device control (required)-->
+          <element name="CmdType" fixed="DeviceControl"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device ID (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Execution result markup (required) -->
+
+```
+
+```
+
+        <element name="Result" type="resultType"/>
+      </sequence>
+    </complexType>
+  </element>
+</choice>
+</schema>
+
+```
+
+#### b) Alarm notification response
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Response">
+      <complexType>
+        <sequence>
+          <!-- The query request response message is shown as follows.-->
+          <!-- Command type: alarm notification (required)-->
+          <element name="CmdType" fixed="Alarm"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device/administrative zone/VSS ID (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Execution result markup (required) -->
+          <element name="Result" type="resultType"/>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+
+```
+
+#### c) Device directory information query response
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Response">
+      <complexType>
+        <sequence>
+          <!-- The query request response message is shown as follows.-->
+          <!-- Command type: device directory query (required)-->
+          <element name="CmdType" fixed="Catalog"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device/administrative zone/VSS ID, the values are the
+same as those of the directory query request (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Total of query results (required) -->
+          <element name="SumNum " type="integer"/>
+          <!-- Device directory item list, Num shows the number of the
+directory items.-->
+          <element name="DeviceList" minOccurs="0">
+            <complexType>
+              <choice minOccurs="0" maxOccurs="unbounded ">
+                <element name="Item" type="itemType"/>
+              </choice>
+              <attribute name="Num" type="integer"/>
+            </complexType>
+          </element>
+          <!-- Extended information, multiple -->
+          <element name="Info" minOccurs="0" maxOccurs="unbounded">
+            <restriction base="string">
+
+```
+
+```
+
+        <maxLength value="1024"/>
+      </restriction>
+    </element>
+  </sequence>
+</complexType>
+</element>
+</choice>
+</schema>
+
+```
+
+#### d) Directory information query response
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Response">
+      <complexType>
+        <sequence>
+          <!-- The query request response message is shown as follows.-->
+          <!-- Command type: device directory query (required)-->
+          <element name="CmdType" fixed="Catalog"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device ID (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Execution result markup (required) -->
+          <element name="Result" type="resultType"/>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+
+```
+
+#### e) Directory response
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Response">
+      <complexType>
+        <sequence>
+          <!-- The query request response message is shown as follows.-->
+          <!-- Command type: device directory query (required)-->
+          <element name="CmdType" fixed="Catalog"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device/administrative zone/VSS ID (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Execution result markup (required) -->
+          <element name="Result" type="resultType"/>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+
+```
+
+#### f) Device information query response
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+
+```
+
+```
+
+<element name="Response">
+  <complexType>
+    <sequence>
+      <!-- The query request response message is shown as follows.-->
+      <!-- Command type: device information query (required)-->
+      <element name="CmdType" fixed="DeviceInfo"/>
+      <!-- Command SN (required) -->
+      <element name="SN" type="integer" minInclusive="1"/>
+      <!-- Target device ID (required) -->
+      <element name="DeviceID" type="deviceIDType"/>
+      <!-- Target device/administrative zone/VSS ID (optional) -->
+      <element name="DeviceName" type="string" minOccurs="0"/>
+      <!-- Query results (required) -->
+      <element name="Result" type="resultType"/>
+      <!-- Device manufacturer (optional)-->
+      <element name="Manufacturer" type="normalizedString" minOccurs="0"/>
+      <!-- Device model (optional) -->
+      <element name="Model" type="string" minOccurs="0"/>
+      <!-- Device firmware version (optional) -->
+      <element name="Firmware" type="string" minOccurs="0"/>
+      <!-- Number of video input channels (optional) -->
+      <element name="Channel" type="integer" minInclusive="0"
+minOccurs="0"/>
+      <!-- Extended information, multiple -->
+      <element name="Info" minOccurs="0" maxOccurs="unbounded">
+        <restriction base="string">
+          <maxLength value="1024"/>
+        </restriction>
+      </element>
+    </sequence>
+  </complexType>
+</element>
+</choice>
+</schema>
+
+```
+
+#### g) Device status information query response
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Response">
+      <complexType>
+        <sequence>
+          <!-- The query request response message is shown as follows.-->
+          <!-- Command type: device status query (required)-->
+          <element name="CmdType" fixed="DeviceStatus"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device ID (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Query result markup (required) -->
+          <element name="Result" type="resultType"/>
+          <!-- Online or not (required) -->
+          <element name="Online">
+            <restriction base="string">
+              <enumeration value="ONLINE"/>
+              <enumeration value="OFFLINE"/>
+            </restriction>
+          </element>
+          <!-- Work normally or not (required) -->
+          <element name="Status" type="resultType"/>
+          <!-- Reason for abnormal operation (optional) -->
+          <element name="Reason" type="string" minOccurs="0"/>
+
+```
+
+```
+
+    <!-- Encode or not (optional) -->
+    <element name="Encode" type="statusType" minOccurs="0"/>
+    <!-- Record or not (optional) -->
+    <element name="Record" type=" statusType" minOccurs="0"/>
+    <!-- Device time and date (optional) -->
+    <element name="DeviceTime" type="dateTime" minOccurs="0"/>
+    <!-- Alarm device status list, num shows the number of list items
+(optional) -->
+    <element name="Alarmstatus" minOccurs="0">
+      <attribute name="Num" type="integer"/>
+      <element name="Item" minOccurs="0" maxOccurs=" unbounded ">
+        <complexType>
+          <sequence>
+            <!-- Alarm device ID (required) -->
+            <element name="DeviceID" type=" deviceIDType "
+minOccurs="0"/>
+            <!-- Alarm device status (optional) -->
+            <element name="DutyStatus" minOccurs="0">
+              <restriction base="string">
+                <enumeration value="ONDUTY"/>
+                <enumeration value="OFFDUTY"/>
+                <enumeration value="ALARM"/>
+              </restriction>
+            </element>
+          </sequence>
+        </complexType>
+      </element>
+    </element>
+    <!-- Extended information, multiple -->
+    <element name="Info" minOccurs="0" maxOccurs="unbounded">
+      <restriction base="string">
+        <maxLength value="1024"/>
+      </restriction>
+    </element>
+  </sequence>
+</complexType>
+</element>
+</choice>
+</schema>
+
+```
+
+#### h) File directory retrieval response
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Response">
+      <complexType>
+        <sequence>
+          <!-- The query request response message is shown as follows.-->
+          <!-- Command type: file directory query (required) -->
+          <element name="CmdType" fixed=" RecordInfo "/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Device/VSS ID (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Device/VSS name (required) -->
+          <element name="Name" type="string"/>
+          <!-- Total of query results (required) -->
+          <element name="SumNum " type="integer"/>
+          <!-- File directory item list, Num shows the number of the directory
+items.-->
+          <element name="RecordList">
+            <complexType>
+
+```
+
+```
+
+        <choice minOccurs="0" maxOccurs="unbounded">
+          <element name="Item" type="itemFileType"/>
+        </choice>
+        <attribute name="Num" type="integer"/>
+      </complexType>
+    </element>
+    <!--Extended information, multiple -->
+    <element name="Info" minOccurs="0" maxOccurs="unbounded">
+      <restriction base="string">
+        <maxLength value="1024"/>
+      </restriction>
+    </element>
+  </sequence>
+</complexType>
+</element>
+</choice>
+</schema>
+
+```
+
+#### i) Device configuration response
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Response">
+      <complexType>
+        <sequence>
+          <!-- The query request response message is shown as follows.-->
+          <!-- Command type: device parameter configuration (required)-->
+          <element name="CmdType" fixed="DeviceConfig"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device ID (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Execution result markup (required) -->
+          <element name="Result" type="resultType"/>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+
+```
+
+#### j) Device configuration query response
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Response">
+      <complexType>
+        <sequence>
+          <!-- The query request response message is shown as follows.-->
+          <!-- Command type: device configuration acquirement (required)-->
+          <element name="CmdType" fixed="ConfigDownload"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Device ID (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Query result markup (required) -->
+          <element name="Result" type="resultType"/>
+          <!-- Basic parameters (optional) -->
+          <element name="BasicParam " minOccurs="0">
+            <complexType>
+
+```
+
+```
+
+      <sequence>
+        <!-- Device name (required) -->
+        <element name="Name" type="string"/>
+        <!-- Registration expiration time (required)-->
+        <element name="Expiration" type="integer"/>
+        <!-- heartbeat interval (required)-->
+        <element name="HeartBeatInterval" type="integer"/>
+        <!-- Heartbeat timeout count (required) -->
+        <element name="HeartBeatCount" type="integer"/>
+        <!-- Positioning function support conditions. Value: 0-
+unsupported; 1-support GPS; 2-support Beidou positioning (optional, the
+default value is 0) -->
+        <element name="PositionCapability" type="integer"
+default="0"/>
+        <!-- Longitude (optional) -->
+        <element name="Longitude" type="double" minOccurs="0"/>
+        <!-- Latitude (optional) -->
+        <element name="Latitude" type="double" minOccurs="0"/>
+      </sequence>
+    </complexType>
+  </element>
+  <!-- Video parameter range (optional), the optional parameters are
+separated with "/". -->
+  <element name="VideoParamOpt" minOccurs="0">
+    <complexType>
+      <sequence>
+        <!-- Download speed range (optional), the optional parameters
+are separated with "/"; if the device supports 1, 2 and 4 times the speed, it
+shall be written as "1/2/4" -->
+        <element name="DownloadSpeed" type="string" minOccurs="0"/>
+        <!-- Resolution supported by the camera (optional), there are
+multiple resolution values separated with "/". For the resolution values,
+refer to the SDP f field provisions of clause 7.7. -->
+        <element name="Resolution" type="string" minOccurs="0"/>
+      </sequence>
+    </complexType>
+  </element>
+  <!-- Video parameter current configuration (optional) -->
+  <element name="VideoParamConfig">
+    <complexType>
+      <attribute name="Num" type="integer"/>
+      <choice minOccurs="0" maxOccurs="unbounded">
+        <element name="Item" type="videoParamAttributeType"/>
+      </choice>
+    </complexType>
+  </element>
+  </sequence>
+  </complexType>
+  </element>
+  </choice>
+</schema>
+
+```
+
+#### k) Device pre-set position query response
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Response">
+      <complexType>
+        <sequence>
+          <!-- The query request response message is shown as follows. -->
+          <!-- Command type: preset position query (required) -->
+          <element name="CmdType" fixed="PresetQuery"/>
+
+```
+
+```
+
+        <!-- Command SN (required) -->
+        <element name="SN" type="integer" minInclusive="1"/>
+        <!-- Query of target device ID (required) -->
+        <element name="DeviceID" type="deviceIDType"/>
+        <!-- Total of query results (required) -->
+        <element name="SumNum" type="integer"/>
+        <!-- Device preset position list, used for preset position query
+between platforms or between platform and device (required) -->
+        <element name="PresetList">
+          <complexType>
+            <sequence>
+              <!-- Preset position record of current configuration, not
+filled in if the preset position is not configured -->
+              <element name="Item" minOccurs="0" maxOccurs=" unbounded ">
+                <complexType>
+                  <sequence>
+                    <!-- Preset position ID (required) -->
+                    <element name="PresetID" type="string"/>
+                    <!-- Preset position name (required) -->
+                    <element name="PresetName" type="string"/>
+                  </sequence>
+                </complexType>
+              </element>
+              <!-- Number of list items, the value is 0 if the preset
+position is not configured (required) -->
+              <attribute name="Num" type="integer"/>
+            </sequence>
+          </complexType>
+        </element>
+      </sequence>
+    </complexType>
+  </element>
+</choice>
+</schema>
+```
+
+#### l) Audio broadcast response
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Response">
+      <complexType>
+        <sequence>
+          <!-- The query request response message is shown as follows.-->
+          <!-- Command type: audio broadcast notification (required)-->
+          <element name="CmdType" fixed="Broadcast"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Audio output device ID (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Execution result markup (required) -->
+          <element name="Result" type="resultType"/>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+```
+
+#### m) Guard position information query response
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+```
+
+```
+
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Response">
+      <complexType>
+        <sequence>
+          <!-- The query request response message is shown as follows.-->
+          <!-- Command type: Guard position information query (required) -->
+          <element name="CmdType" fixed="HomePositionQuery"/>
+          <!-- Command SN (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device code (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Guard position configuration information (optional) -->
+          <element name="HomePosition" minOccurs="0">
+            <complexType>
+              <sequence>
+                <!-- Guard position switch (required), 0-off; 1-open -->
+                <element name="Enabled" type="integer"/>
+                <!-- Automatic home time interval, used when opening guard
+position, unit: seconds (optional)-->
+                <element name="ResetTime" type="integer" minOccurs="0"/>
+                <!-- Call the preset number and use when opening the guard
+position (optional). The value range is greater than or equal to 0 and less
+than or equal to 255.-->
+                <element name="PresetIndex" minOccurs="0">
+                  <simpleType>
+                    <restriction base="integer">
+                      <minInclusive value="0"/>
+                      <maxInclusive value="255"/>
+                    </restriction>
+                  </simpleType>
+                </element>
+              </sequence>
+            </complexType>
+          </element>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+
+```
+
+#### n) Cruise track list query response
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Response">
+      <complexType>
+        <sequence>
+          <!-- The query request response message is shown as follows.-->
+          <!-- Command type: cruise track list query (required) -->
+          <element name="CmdType" fixed="CruiseTrackListQuery"/>
+          <!-- Command serial number (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device code (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!--Total number of results (required) -->
+          <element name="SumNum" type="integer"/>
+          <!-- Cruise track information (optional) -->
+          <element name="CruiseTrackList" minOccurs="0">
+            <complexType>
+              <!-- The number of track items, when the cruise track is not
+configured, the value is 0 (required) -->
+
+```
+
+```
+
+        <attribute name="Num" type="integer"/>
+        <choice minOccurs="0" maxOccurs="unbounded">
+          <!-- Track information -->
+          <element name="CruiseTrack">
+            <complexType>
+              <sequence>
+                <!-- Track number (required), 0 - first track, 1 -
+second track-->
+                <element name="Number" type="integer"/>
+                <!-- Track name (optional), up to 32 bytes -->
+                <element name="Name" type="integer" minOccurs="0"/>
+              </sequence>
+            </complexType>
+          </element>
+        </choice>
+      </complexType>
+    </element>
+  </sequence>
+</complexType>
+</element>
+</choice>
+</schema>
+
+```
+
+#### **o) Cruise track query response**
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Response">
+      <complexType>
+        <sequence>
+          <!-- The query request response message is shown as follows.-->
+          <!-- Command type: cruise track query (required) -->
+          <element name="CmdType" fixed="CruiseTrackQuery"/>
+          <!-- Command serial number (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device code (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Track number (required)-->
+          <element name="Number" type="integer"/>
+          <!-- Track name, up to 32 bytes (optional)-->
+          <element name="Name" type="integer" minOccurs="0"/>
+          <!--Total number of results (required) -->
+          <element name="SumNum" type="integer"/>
+          <!-- Track point list (optional) -->
+          <element name="CruisePointList" minOccurs="0">
+            <complexType>
+              <!-- The number of track points, when the cruise track is not
+configured, the value is 0 (required) -->
+              <attribute name="Num" type="integer"/>
+              <choice minOccurs="0" maxOccurs="unbounded">
+                <!-- Track point information -->
+                <element name="CruisePoint">
+                  <complexType>
+                    <sequence>
+                      <!-- Preset number (required)-->
+                      <element name="PresetIndex" type="integer"/>
+                      <!-- Preset point stay time, unit: second (required)-->
+                      <element name="StayTime" type="integer"/>
+                      <!-- PTZ speed: 1 to 15 (required)-->
+                      <element name="Speed" type="integer"/>
+                    </sequence>
+                  </complexType>
+
+```
+
+```
+
+    </element>
+  </choice>
+</complexType>
+</element>
+</sequence>
+</complexType>
+</element>
+</choice>
+</schema>
+
+```
+
+#### p) PTZ precise status query response
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Response">
+      <complexType>
+        <sequence>
+          <!-- The query request response message is shown as follows.-->
+          <!-- Command type: PTZ precise status query response (required) -->
+          <element name="CmdType" fixed=" PTZPosition"/>
+          <!-- Command serial number (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device code (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Horizontal angle of PTZ setting (optional) -->
+          <element name="Pan" type="double" minOccurs="0"/>
+          <!-- Vertical angle of PTZ setting (optional) -->
+          <element name="Tilt" type="double"/>
+          <!-- Zoom factor for PTZ setting (optional) -->
+          <element name="Zoom" type="double" minOccurs="0"/>
+          <!-- Camera horizontal field of view angle (optional) -->
+          <element name="HorizontalFieldAngle" type="double" minOccurs="0"/>
+          <!-- Camera vertical field of view angle (optional) -->
+          <element name="VerticalFieldAngle" type="double" minOccurs="0"/>
+          <!-- Camera visible radius, unit: meter, (optional) -->
+          <element name="MaxViewDistance" type="double" minOccurs="0"/>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</schema>
+
+```
+
+#### q) OSD information query response
+
+```
+
+<?xml version="1.0" encoding="utf-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema">
+  <choice maxOccurs="unbounded">
+    <element name="Response">
+      <complexType>
+        <sequence>
+          <!-- The query request response message is shown as follows.-->
+          <!-- Command Type: OSD Information Query Response (Required) -->
+          <element name="CmdType" fixed="OSDQuery"/>
+          <!-- Command serial number (required) -->
+          <element name="SN" type="integer" minInclusive="1"/>
+          <!-- Target device code (required) -->
+          <element name="DeviceID" type="deviceIDType"/>
+          <!-- Configure window length pixel values (required) -->
+          <element name="Length" type="integer"/>
+          <!-- Configure window width pixel values (required) -->
+
+```
+
+```
+
+    <element name="Width" type="integer"/>
+    <!-- Time X pixel coordinates (required), the pixel in the upper left
+corner of the playback window is the origin, and the horizontal right is
+positive.-->
+    <element name="TimeX" type="integer"/>
+    <!-- Time Y pixel coordinates (required), the pixel in the upper left
+corner of the playback window is the origin, and the vertical down is positive-
+-->
+    <element name="TimeY" type="integer"/>
+    <!-- Display time switch (optional), 0-off; 1-open (default value)-->
+    <element name="TimeEnable" type="integer" default="1"/>
+    <!--Time display type (optional):
+0- Year-Month-Day Hour:Minute:Second
+1- Year Month Day Hour:Minute:Second
+2- Day/Month/Year Hour:Minute:Second
+3- Month / Day/Year Hour:Minute:Second
+-->
+    <element name="TimeType" type="integer" minOccurs="0"/>
+    <!--Display text switch (optional), 0-off; 1-open (default value)-->
+    <element name="TextEnable" type="integer" default="1"/>
+    <!--Text list (optional)-->
+    <element name="Item" minOccurs="0" maxOccurs="8">
+      <complexType>
+        <sequence>
+          <!--Text content, length range 0 ~ 32 (required)-->
+          <element name="Text" type="string" minOccurs="0"/>
+          <!--Text X coordinate (required)-->
+          <element name="X" type="integer" minOccurs="0"/>
+          <!--Text Y coordinate (required)-->
+          <element name="Y" type="integer" minOccurs="0"/>
+        </sequence>
+      </complexType>
+    </element>
+  </sequence>
+</complexType>
+</element>
+</choice>
+</schema>
+
+```
+
+## A.3 PU control commands
+
+### A.3.1 Command format
+
+For the format of PU control command, see Table A.3.
+
+**Table A.3 – Command format of PU control**
+
+| Bytes   | Byte 1 | Byte 2          | Byte 3  | Byte 4  | Byte 5 | Byte 6 | Byte 7          | Byte 8            |
+|---------|--------|-----------------|---------|---------|--------|--------|-----------------|-------------------|
+| Meaning | A5H    | Combined code 1 | Address | Command | Data 1 | Data 2 | Combined code 2 | Verification code |
+
+The byte definitions of the command are as follows:
+
+- byte 1: the first byte of the command is A5H;
+- byte 2: combined code 1; the high-order 4 bits are 0H, and the low-order 4 bits are the check bits;
+- check bits = (the high-order 4 bits of the byte 1 + the low-order 4 bits of the byte 2) % 16;<sup>a</sup>
+- byte 3: the low-order 8 bits of the address;
+
+<sup>a</sup> In this clause, "%" denotes the modulus operation, e.g., 17 % 16 = 1.
+
+- byte 4: command code;
+- bytes 5 and 6: data 1 and data 2;
+- byte 7: combined code 2; the high-order 4 bits are the data 3, and the low-order 4 bits are the high-order 4 bits of the address; in the following description, if there is no specific high-order 4 bits, it shows these 4 bits are unrelated to the specified function;
+- byte 8: verification code; the low-order 8 bits of the arithmetic sum of the above bytes 1-7, namely the result of the arithmetic sum % 256;
+- $\text{byte } 8 = (\text{byte } 1 + \text{byte } 2 + \text{byte } 3 + \text{byte } 4 + \text{byte } 5 + \text{byte } 6 + \text{byte } 7) \% 256$ .
+
+The address range is 000H-FFFH (namely 0-4095), where the 000H address is regarded as the broadcast address.
+
+NOTE – Byte 3 and the low-order 4 bit address codes of byte 7 are not used in the control of the PU, and the controlled PUs are marked with unified <DeviceID> in the PU control message body.
+
+### A.3.2 PTZ commands
+
+For the PTZ commands, see Table A.4, where bit5 and bit4 should not be 1 at the same time, nor should bit3 and bit2, as well as bit1 and bit0. The lens zoom commands, pan and tilt up and down commands as well as pan and tilt left and right commands can be combined.
+
+For examples of PTZ commands, see Table A.5.
+
+**Table A.4 – PTZ commands**
+
+| Byte   | Bit                                        |      |                  |              |                                  |      |                          |       |  |
+|--------|--------------------------------------------|------|------------------|--------------|----------------------------------|------|--------------------------|-------|--|
+|        | Bit7                                       | Bit6 | Bit5             | Bit4         | Bit3                             | Bit2 | Bit1                     | Bit0  |  |
+| Byte 4 | 0                                          | 0    | Lens zoom (Zoom) |              | Vertical control (Tilt)          |      | Horizontal control (Pan) |       |  |
+|        |                                            |      | Zoom-out (OUT)   | Zoom-in (IN) | Up                               | Down | Left                     | Right |  |
+| Byte 5 | Relative value of horizontal control speed |      |                  |              |                                  |      |                          |       |  |
+| Byte 6 | Relative value of vertical control speed   |      |                  |              |                                  |      |                          |       |  |
+| Byte 7 | Relative value of zoom control speed       |      |                  |              | High-order 4 bits of the address |      |                          |       |  |
+
+NOTE 1 – Bit5 and bit4 in byte 4 are used to control the lens zoom-in and zoom-out, respectively, and the bit3, bit2, bit1 and bit0 in the byte 4 are used to control the up, down, left and right rotation of the pan-tilt; when the corresponding bit is 1, the pan-tilt is switched on to rotate in the corresponding direction; when the bit is reset to 0, the rotation of the pan-tilt in the corresponding direction is stopped. For the rotation direction of the pan-tilt, the moving direction of the monitor display image shall prevail.
+
+NOTE 2 – Byte 5 is used to control the horizontal speed, and the speed range is 00H-FFH from slow to fast; byte 6 is used to control the vertical speed, and the speed range is 00H-FFH from slow to fast.
+
+NOTE 3 – The high-order 4 bits of byte 7 is used to control the zoom speed, and the speed range is 0H-FH from slow to fast; the low-order 4 bits are the high-order 4 bits of the address.
+
+**Table A.5 – Examples of PTZ commands**
+
+| No. | Byte 4 | Byte 5  | Byte 6  | High-order 4 bits of byte 7 | Functional description                                                                                                                                                                                                                                                                                                                            |
+|-----|--------|---------|---------|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | 20H    | XX      | XX      | 0H-FH                       | The lens is zoomed out at the value of high-order 4 bits of byte 7.                                                                                                                                                                                                                                                                               |
+| 2   | 10H    | XX      | XX      | 0H-FH                       | The lens is zoomed in at the value of high-order 4 bits of byte 7.                                                                                                                                                                                                                                                                                |
+| 3   | 08H    | XX      | 00H-FFH | X                           | The pan-tilt moves upward at the speed provided by byte 6.                                                                                                                                                                                                                                                                                        |
+| 4   | 04H    | XX      | 00H-FFH | X                           | The pan-tilt moves downward at the speed provided by byte 6.                                                                                                                                                                                                                                                                                      |
+| 5   | 02H    | 00H-FFH | XX      | X                           | The pan-tilt moves leftward at the speed provided by byte 5.                                                                                                                                                                                                                                                                                      |
+| 6   | 01H    | 00H-FFH | XX      | X                           | The pan-tilt moves rightward at the speed provided by byte 5.                                                                                                                                                                                                                                                                                     |
+| 7   | 00H    | XX      | XX      | X                           | All operations of the PTZ stop.                                                                                                                                                                                                                                                                                                                   |
+| 8   | 29H    | 00H-FFH | 00H-FFH | 0H-FH                       | This is an example of combined PTZ commands: The pan-tilt moves rightward at the speed provided by byte 5, and at the same time moves upward at the speed provided by byte 6; actually the pan-tilt moves aslant towards the upper right direction; meanwhile, the lens is zoomed out at the rate represented by the high-order 4 bits of byte 7. |
+
+### **A.3.3 Focus iris commands**
+
+For the focus iris (FI) commands, see Table A.6, where bit3 and bit2 should not be 1 at the same time, nor should bit1 and bit0; the iris control and focus control commands can be combined.
+
+For examples of FI commands, see Table A.7.
+
+**Table A.6 – FI commands**
+
+| Byte   | Bit         |      |      |      |                                  |         |       |      |  |  |  |
+|--------|-------------|------|------|------|----------------------------------|---------|-------|------|--|--|--|
+|        | Bit7        | Bit6 | Bit5 | Bit4 | Bit3                             | Bit2    | Bit1  | Bit0 |  |  |  |
+| Byte 4 | 0           | 1    | 0    | 0    | Iris                             |         | Focus |      |  |  |  |
+|        |             |      |      |      | Zoom out                         | Zoom in | Close | Far  |  |  |  |
+| Byte 5 | Focus speed |      |      |      |                                  |         |       |      |  |  |  |
+| Byte 6 | Iris speed  |      |      |      |                                  |         |       |      |  |  |  |
+| Byte 7 | 0           | 0    | 0    | 0    | High-order 4 bits of the address |         |       |      |  |  |  |
+
+NOTE 1 – When bit3 in byte 4 is 1, the iris is zoomed out; when bit2 is 1, the iris is zoomed in. When bit1 is 1, focus on close objects; when bit0 is 1, focus on far objects. If bit3-bit0 are reset to 0 correspondingly, the corresponding control operation is stopped.
+
+NOTE 2 – Byte 5 represents the focus speed, and the speed range is 0H-FH from slow to fast.
+
+NOTE 3 – Byte 6 represents the iris speed, and the speed range is 0H-FH from slow to fast.
+
+**Table A.7 – Examples of FI commands**
+
+| No. | Byte 4 | Byte 5  | Byte 6  | High-order 4 bits of byte 7 | Functional description                                                                                                                                              |
+|-----|--------|---------|---------|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | 48H    | XX      | 00H-FFH | 0H                          | The lens iris is zoomed out at the value of byte 6.                                                                                                                 |
+| 2   | 44H    | XX      | 00H-FFH | 0H                          | The lens iris is zoomed in at the value of byte 6.                                                                                                                  |
+| 3   | 42H    | 00H-FFH | XX      | 0H                          | The lens iris focuses on close objects at the value of byte 5.                                                                                                      |
+| 4   | 41H    | 00H-FFH | XX      | 0H                          | The lens iris focuses on far objects at the value of byte 5.                                                                                                        |
+| 5   | 40H    | XX      | XX      | 0H                          | The lens stops all operations of FI.                                                                                                                                |
+| 6   | 49H    | 00H-FFH | 00H-FFH | 0H                          | This is an example of combined FI commands; the lens iris is zoomed out at the value of byte 6, and at the same time focuses on far objects at the value of byte 5. |
+
+### A.3.4 Presetting bit commands
+
+For presetting bit commands, see Table A.8, where the maximum number of presetting bits is 255 and 0 is reserved.
+
+**Table A.8 – Presetting bit commands**
+
+| No. | Byte 4 | Byte 5 | Byte 6  | Functional description      |
+|-----|--------|--------|---------|-----------------------------|
+| 1   | 81H    | 00H    | 01H-FFH | Setting the presetting bit  |
+| 2   | 82H    | 00H    | 01H-FFH | Invoking the presetting bit |
+| 3   | 83H    | 00H    | 01H-FFH | Deleting the presetting bit |
+
+### A.3.5 Cruise commands
+
+For the cruise commands, see Table A.9.
+
+**Table A.9 – Cruise commands**
+
+| No. | Byte 4 | Byte 5  | Byte 6  | High-order 4 bits of byte 7 | Functional description        |
+|-----|--------|---------|---------|-----------------------------|-------------------------------|
+| 1   | 84H    | 00H-FFH | 01H-FFH | X                           | Adding a cruise point         |
+| 2   | 85H    | 00H-FFH | 00H-FFH | X                           | Deleting a cruise point       |
+| 3   | 86H    | 00H-FFH | 01H-FFH | 0H-FH                       | Setting the cruise speed      |
+| 4   | 87H    | 00H-FFH | 01H-FFH | 0H-FH                       | Setting the cruise dwell time |
+| 5   | 88H    | 00H-FFH | 00H     | X                           | Starting the cruise           |
+
+NOTE 1 – Byte 5 represents the cruise group number, and byte 6 represents the presetting bit number.
+
+NOTE 2 – If byte 6 is 00H in No. 2, delete the corresponding cruise as a whole; byte 6 in No. 3 and No. 4 represents the low-order 8 bits of the data, and the high-order 4 bits of byte 7 represent the high-order 4 bits of the data.
+
+NOTE 3 – The unit of cruise dwell time is the second (s).
+
+NOTE 4 – To stop the cruise, use the stop command in which all bits in byte 4 in the PTZ command are 0.
+
+### A.3.6 Scanning commands
+
+For scanning commands, see Table A.10.
+
+**Table A.10 – Scanning commands**
+
+| No. | Byte 4 | Byte 5  | Byte 6  | High-order 4 bits of byte 7 | Functional description                               |
+|-----|--------|---------|---------|-----------------------------|------------------------------------------------------|
+| 1   | 89H    | 00H-FFH | 00H     | X                           | Starting the automatic scanning                      |
+| 2   | 89H    | 00H-FFH | 01H     | X                           | Setting the left boundary of the automatic scanning  |
+| 3   | 89H    | 00H-FFH | 02H     | X                           | Setting the right boundary of the automatic scanning |
+| 4   | 8AH    | 00H-FFH | 01H-FFH | 0H-FH                       | Setting the automatic scanning speed                 |
+
+NOTE 1 – Byte 5 represents the scanning group number.
+
+NOTE 2 – Byte 6 in No. 4 represents the low-order 8 bits of the data, and the high-order 4 bits of byte 7 represent the high-order 4 bits of the data.
+
+NOTE 3 – To stop the automatic scanning, use the stop command in which all bits in byte 4 in the PTZ command are 0.
+
+NOTE 4 – The overall picture moves from right to left when the automatic scanning starts.
+
+### A.3.7 Auxiliary switch control commands
+
+For the auxiliary switch control commands, see Table A.11.
+
+**Table A.11 – Auxiliary switch control commands**
+
+| No. | Byte 4 | Byte 5  | Functional description  |                                        |                                                                  |
+|-----|--------|---------|-------------------------|----------------------------------------|------------------------------------------------------------------|
+|     |        |         | Auxiliary switch action | Controlled object is a switch quantity | Controlled object is an analogue quantity                        |
+| 1   | 8CH    | 00H-FFH | ON                      | Switch ON                              | The stopping value of the analogue quality increases by one unit |
+| 2   | 8DH    | 00H-FFH | OFF                     | Switch OFF                             | The stopping value of the analogue quality decreases by one unit |
+
+NOTE – Byte 5 is the auxiliary switch number, and the value "1" represents the wiper control.
+
+# Bibliography
+
+- [b-ITU-T F.743V2] Recommendation ITU-T F.743 (2019), *Requirements and service description for video surveillance.*
+- [ITU-T H.264.1] Recommendation ITU-T H.264.1 (V6) (2016), *Conformance specification for ITU-T H.264 advanced video coding.*
+- [ITU-T H.265.1] Recommendation ITU-T H.265.1 (2018), *Conformance specification for ITU-T H.265 high-efficiency video coding.*
+- [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.*
+- [ITU-T Y.2012] Recommendation ITU-T Y.2012 (2010), *Functional requirements and architecture of next generation networks.*
+- [IETF RFC 768] IETF RFC 768 (1980), *User datagram protocol.*
+- [IETF RFC 793] IETF RFC 793 (1981), *Transmission control protocol.*
+
+
+
+
+
+# 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.2-202203-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.627.2-202203-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1e32f9b8f1141bed243c16e02a6cd1411cbb87f1
--- /dev/null
+++ b/marked/H/T-REC-H.627.2-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.627.2-202203-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/H/T-REC-H.627.2-202203-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..269d06bdd719719de9aa83bd6596be31f74762a9
--- /dev/null
+++ b/marked/H/T-REC-H.627.2-202203-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f6016af2f3a12d7c2715b8f10f87024bb11f75ccb4bd21ee02aa0044885bd794
+size 23357
diff --git a/marked/H/T-REC-H.627.2-202203-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/H/T-REC-H.627.2-202203-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ce6bc48f44d60e8a18207f6904935a78c4c3221f
--- /dev/null
+++ b/marked/H/T-REC-H.627.2-202203-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7fec60907d9708d869a2e1900f3a270cc5d3e812d3714f86356618774326143f
+size 19659
diff --git a/marked/H/T-REC-H.627.2-202203-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/H/T-REC-H.627.2-202203-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e84c0e6c3d3954b9024e3a0513f116cdcc0be4b9
--- /dev/null
+++ b/marked/H/T-REC-H.627.2-202203-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:34647ef3143d992c454c35a7d485c8f7ed200969494059c694ee37d5ce4de5cd
+size 44708
diff --git a/marked/H/T-REC-H.627.2-202203-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg b/marked/H/T-REC-H.627.2-202203-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e7c46de0d9bac904c05a4a66d8c4afd11081b154
--- /dev/null
+++ b/marked/H/T-REC-H.627.2-202203-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:984975613671a38735a94870f2e0b238c9b3f05fbcf7183121be150e1ed780d8
+size 43582
diff --git a/marked/H/T-REC-H.627.2-202203-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/H/T-REC-H.627.2-202203-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..49481288230b8e8462f5e49558b3d47f3455c4fe
--- /dev/null
+++ b/marked/H/T-REC-H.627.2-202203-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd96ef2ad129c72f4c667b08eff036fbf1660b5a6051f18795f00e4dbd7c4ea7
+size 54494
diff --git a/marked/H/T-REC-H.627.2-202203-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/H/T-REC-H.627.2-202203-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..df9dfcd0ee989ab2292a69c50b411493c67c849f
--- /dev/null
+++ b/marked/H/T-REC-H.627.2-202203-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c5fffd3c05c9b7ce759de142c949d2a4182daa4a14d5ebcb9d508dfbad7b96e6
+size 13796
diff --git a/marked/H/T-REC-H.627.2-202203-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/marked/H/T-REC-H.627.2-202203-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f73895b16a501678598d497550f41e55a83272b3
--- /dev/null
+++ b/marked/H/T-REC-H.627.2-202203-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f9556584884ff8dfb05a77c4bd6f3532ba1136870db952d785916006f0656685
+size 18866
diff --git a/marked/H/T-REC-H.627.2-202203-I_PDF-E/raw.md b/marked/H/T-REC-H.627.2-202203-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..08929db6e2f7e0090a55ac80b9452467aed973b0
--- /dev/null
+++ b/marked/H/T-REC-H.627.2-202203-I_PDF-E/raw.md
@@ -0,0 +1,1356 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.627.2**
+
+(03/2022)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Broadband, triple-play and advanced multimedia  
+services – Advanced multimedia services and applications
+
+# --- **Requirements and protocols for home surveillance systems**
+
+Recommendation ITU-T H.627.2
+
+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 latitude and longitude lines, and the letters 'ITU' in white, 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        |
+| <b>Advanced multimedia services and applications</b>                                        | <b>H.620–H.629</b> |
+| 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.627.2
+
+# Requirements and protocols for home surveillance systems
+
+## Summary
+
+Recommendation ITU-T H.627.2 defines the requirements and protocols for Internet protocol (IP) based network access of varied types of equipment under home security surveillance scenarios including the architecture, protocol for transmission, access and service functions as well as other relevant requirements under the home surveillance considerations.
+
+This Recommendation specifies a way to eliminate the difference in network communication and access management of heterogeneous devices, simplify the construction complexity of home security platforms, improve the security and reliability of data transmission between home security equipment and the home surveillance platform, and finally guarantee high-qualified development of home surveillance service.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T H.627.2  | 2022-03-16 | 16          | <a href="http://handle.itu.int/11.1002/1000/14971">11.1002/1000/14971</a> |
+
+## Keywords
+
+Home surveillance, interface, protocols, requirements.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....               | 1    |
+| 4 Abbreviations and acronyms .....                          | 2    |
+| 5 Conventions .....                                         | 3    |
+| 6 Message syntax and semantics .....                        | 3    |
+| 7 Requirements for home surveillance systems (HSS).....     | 3    |
+| 8 Reference architecture for HSS .....                      | 3    |
+| 8.1 Architectural framework .....                           | 4    |
+| 8.2 Functional entities .....                               | 4    |
+| 8.3 Protocols and interfaces.....                           | 5    |
+| 9 Protocols for home surveillance system (HSS) .....        | 7    |
+| 9.1 Requirements of the network transmission function ..... | 7    |
+| 9.2 Requirements of access function .....                   | 7    |
+| 9.3 Requirements of service function.....                   | 7    |
+| Appendix I – Interface message examples.....                | 16   |
+| I.1 Messages of the scheduling service interface.....       | 16   |
+| I.2 Messages of device management interface .....           | 16   |
+| I.3 Messages of video service interface .....               | 31   |
+
+
+
+# Recommendation ITU-T H.627.2
+
+# Requirements and protocols for home surveillance systems
+
+# 1 Scope
+
+This Recommendation specifies the requirements and protocols for home surveillance systems (HSS) and covers the following aspects:
+
+- Requirements for home surveillance systems;
+- Reference architecture for home surveillance systems;
+- Protocol interface framework for home surveillance systems;
+- Relevant protocols of home surveillance systems.
+
+# 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 (V2) (2019), *Architectural requirements for video surveillance system*.
+- [ITU-T H.626.4] Recommendation ITU-T H.626.4 (2018), *Architecture for a point-to-point visual surveillance system*.
+- [IETF RFC 2818] IETF RFC 2818 (2000), *HTTP Over TLS*.
+- [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:
+
+None.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 central management unit:** A functional unit located in the main part of a home 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 cloud storage:** A functional unit located at the central part of a home surveillance system. It is used to retrieve and store media and as well as provide a streaming media service. The main functions include media storage, media serving, media indexing, and media downloading, etc.
+
+**3.2.3 customer unit:** A functional unit located at the customer part of a home surveillance system. It is used to present multimedia information (such as audio, video, image, alarm signal, etc.) to the end user.
+
+**3.2.4 home surveillance system:** A telecommunication service focusing on video (including audio and image) application technology, which is used to remotely capture multimedia information (such as audio, video, image, alarm signal, etc.) and present them to the end users in a user-friendly manner. Above service is expected to be realized via a managed broadband network with ensured quality, security and reliability for home surveillance applications.
+
+**3.2.5 media distribution unit:** A functional unit located in the main part of a home surveillance system. It is used to transport media from the premises unit (PU) to the customer unit (CU). The main functions include media reception, media processing, media routing, media transmission, media forwarding, media replication, etc.
+
+**3.2.6 premises unit:** A functional unit located at the remote part of a home surveillance system and is used to capture multimedia information (such as audio, video, image, alarm signal, etc.) from a surveilled object.
+
+**3.2.7 service platform:** A series of functional units and subsystems located at the central part of a home surveillance system. It is used to integrate all capabilities and provides home surveillance services to customers. The main functions include service-control function, media switching, distribution, storage, and control and management.
+
+**3.2.8 service control unit:** A functional unit located in the main part of a home surveillance system. It is used for access service control and signal call control between the premises unit (PU) and the customer unit (CU). The main functions include access registration, access identification, authentication, authorization, call control, location, presence, and target media serving function selection.
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                               |
+|------|-------------------------------|
+| CCS  | Central Control Server        |
+| CMU  | Centre Management Unit        |
+| CS   | Cloud Storage                 |
+| CU   | Customer Unit                 |
+| HSS  | Home Surveillance System      |
+| MDU  | Media Distribution Unit       |
+| MS   | Media Server                  |
+| PTZ  | Pan/Tilt/Zoom                 |
+| PU   | Premises Unit                 |
+| REST | Representation State Transfer |
+| RPC  | Remote Procedure Call         |
+| SCU  | Service Control Unit          |
+| SRT  | Secure Reliable Transport     |
+| SSL  | Secure Sockets Layer          |
+| TCP  | Transmission Control Protocol |
+| TLS  | Transport Layer Security      |
+| 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 Message syntax and semantics
+
+This Recommendation outlines the urgent requirements for home surveillance systems. When regarding the overall architectural framework of home surveillance systems, it references the architecture based on [ITU-T H.626] and [ITU-T H.626.4] with a few extensions. This Recommendation gives a more detailed description of protocol interfaces based on the reference architecture as well as the relevant protocols for such systems, including device management, media stream transmission, recording cloud storage (CS) and their related functions.
+
+# 7 Requirements for home surveillance systems (HSS)
+
+This Recommendation is targeted at providing a series of comprehensive requirements and protocols for a home surveillance system that is implemented in public IP based networks. The home surveillance system (HSS) is required to provide some advanced services such as remote real-time surveillance, video remote storage, and video playback. In addition, it is recommended to provide other value-added services when new AI technologies are used to realize object detection or identification. All devices accessing the HSS are recommended to follow the protocols and interface specifications defined in the following sections.
+
+# 8 Reference architecture for HSS
+
+In this clause, a reference architecture for HSS will be presented in detail.
+
+![Figure 8-1: Reference architecture of home surveillance system. The diagram shows a Service platform (dashed box) containing CS (Core Storage), CCS (Core Control Service), and MS (Media Service) sub-components. CS is connected to PU (Premises Unit) via Vr (Media) and Vs (Control). CCS contains CMU (Centre Management Unit) and SCU (Service Control Unit). CMU is connected to PU via Vd (Control) and to SCU via Ms (Control). SCU is connected to PU via Vm (Media) and to MDU (Media Distribution Unit) via Sm (Control). MDU is connected to PU via Vm (Media) and to CU (Customer Unit) via Cm (Media). CU is connected to CS via Sc (Control) and to PU via Cm (Media). A legend at the bottom indicates that black arrows represent Media and red arrows represent Control. The reference number H.627.2(22) is shown in the bottom right.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg)
+
+Figure 8-1: Reference architecture of home surveillance system. The diagram shows a Service platform (dashed box) containing CS (Core Storage), CCS (Core Control Service), and MS (Media Service) sub-components. CS is connected to PU (Premises Unit) via Vr (Media) and Vs (Control). CCS contains CMU (Centre Management Unit) and SCU (Service Control Unit). CMU is connected to PU via Vd (Control) and to SCU via Ms (Control). SCU is connected to PU via Vm (Media) and to MDU (Media Distribution Unit) via Sm (Control). MDU is connected to PU via Vm (Media) and to CU (Customer Unit) via Cm (Media). CU is connected to CS via Sc (Control) and to PU via Cm (Media). A legend at the bottom indicates that black arrows represent Media and red arrows represent Control. The reference number H.627.2(22) is shown in the bottom right.
+
+**Figure 8-1 – Reference architecture of home surveillance system**
+
+## 8.1 Architectural framework
+
+The architectural framework of home surveillance systems contains three major parts, including a premises unit (PU), customer unit (CU) and a service platform.
+
+PU is a functional unit to capture multimedia information from a surveilled object. CU is a functional unit to present multimedia information towards the end user. There are four additional functional units in the service platform, namely, core storage (CS), service control unit (SCU), media distribution unit (MDU), and centre management unit (CMU). CS is used to retrieve and store media and as well as provides a streaming media service. SCU is used for access service control and signal call control between the PU and the CU. MDU is used to transport media from the PU to the CU. CMU is used for service and operational management functionality.
+
+In order to provide the following functions via the service platform, all PUs are required to access the service platform with authentication and authorization according to the requirements and protocols for home surveillance systems in clause 9.
+
+## 8.2 Functional entities
+
+There are three main functional entities in the service platform, they are signalling control service, media broadcasting service and video service.
+
+- a) Signalling control service is responsible for control signalling between PUs and the service platform. PUs are required to access the service platform through interface Vs and interface Vd shown in Figure 8-1.
+- b) Media broadcasting service is responsible for push flow, transcoding, distribution and other functions of PUs. PUs are required to access the service platform through the interface Vm.
+- c) Video service is responsible for record slice uploading, storage, playback and other functions of PUs. PUs are required to access service platform through the interface Vr.
+- d) Scheduling service is responsible for sending instructions to PUs to connect to the designated signalling server and the peer-to-peer server.
+
+## 8.3 Protocols and interfaces
+
+### 8.3.1 Interface stack
+
+This specification mainly defines the protocols of interfaces (Vs/Vd/Vm/Vr) between PUs and the service platform, including signalling and data transmission protocols. The entire protocol stack is presented in Figure 8-2 which consists of three functions, they are the transmission function, access function and service function.
+
+![Figure 8-2 – Interface stack diagram showing three layers: Service function, Access function, and Transmission function.](5a4e62bead259c258d069fd3663ea670_img.jpg)
+
+The diagram illustrates the interface stack, organized into three horizontal layers, each enclosed in a dashed box. The top layer, 'Service function', contains four boxes labeled Vs, Vd, Vr, and Vm. Below Vs, Vd, and Vr is a single box labeled 'TSL/SSL'. To the right of 'TSL/SSL' is a box labeled 'SRT'. The middle layer, 'Access function', contains a single box labeled 'Authentication and authorization'. The bottom layer, 'Transmission function', contains two stacked boxes labeled 'TCP/UDP' and 'IP'.
+
+|                       |                                  |           |      |    |
+|-----------------------|----------------------------------|-----------|------|----|
+| Service function      | Vs                               | Vd        | Vr   | Vm |
+|                       | HTTP                             | WebSocket | HTTP |    |
+| Access function       | Authentication and authorization |           |      |    |
+| Transmission function | TCP/UDP                          |           |      |    |
+|                       | IP                               |           |      |    |
+
+H.627.2(22)
+
+Figure 8-2 – Interface stack diagram showing three layers: Service function, Access function, and Transmission function.
+
+Figure 8-2 – Interface stack
+
+The transmission function uses transmission control protocol (TCP) / user datagram protocol (UDP) protocol for data transmission. Signalling control service is achieved by interfaces Vs and Vd, respectively. Media broadcasting service is achieved by interface Vm, video service is achieved by interface Vr, and device management is achieved by interface Vd.
+
+In the access function, it is required to provide the PU with an authentication service during the access process. The service platform is required to set several security mechanisms, including the identity verification of PUs, the prevention of brute force attacks and replay attacks, etc. It is required that only the PU with successful authentication can access the service platform. It is required that the CU can only obtain the access right of its binding PU.
+
+In the service function, the detailed protocols of interfaces (Vs/Vd/Vm/Vr) between PUs and the service platform are specified as below.
+
+### 8.3.2 Interface definition
+
+#### a) Interface Ms: CMU-SCU
+
+It is used by the SCU to report the status, capability of the PU and the alarm information to the CMU. It is also used by the CMU to manage service resources, session status and transferring the session ID for authentication.
+
+#### b) Interface Sm: SCU-MDU
+
+It is used by the SCU to control the MDU for media distribution, media selection and media location.
+
+#### c) Interface Cs: SCU-CU
+
+It is used by the CU to send certain video requests to the SCU and to receive the responses.
+
+#### d) Interface Cm: MDU-CU
+
+It is used by the CU to send a request to the MDU and get the media to stream from the MDU.
+
+#### **e) Interface Cc: CMU-CU**
+
+It is used to send a request and return the authentication result, which includes configuration and status query, alarm information, video list and information of cloud storage and front-end storage from the CMU to the CU.
+
+#### **f) Interface Sc: CS-CU**
+
+It is used by the CU to send a query, certain video requests, on command and download command to the CS and get live media stream and to record files from the CS when using the on command and download function.
+
+#### **g) Scheduling service interface Vs**
+
+Interface Vs complies with HTTPS and JSON. Service platform uses Vs to realize PUs dispatching and signalling access among server rooms.
+
+#### **h) Device management interface Vd**
+
+Interface Vd complies with WebSockets and JSON. It defines the control signalling of security devices, including device management, status query, device control, status subscription, live broadcast, network configuration, cloud platform control, alarm reporting, talkback and other functions.
+
+#### **i) Media transmission interface Vm**
+
+Interface Vm complies with a secure reliable transport (SRT) protocol based on the user datagram protocol (UDP). It is used for pushing real-time audio and video media stream.
+
+#### **j) Video recording interface Vr**
+
+Interface Vr complies with HTTPS and JSON. It defines video recording services, including video segment storage allocation, video content upload, video meta-data upload, playback and other functions.
+
+### **8.3.3 Interface message definition**
+
+The standard interface message using HTTPS and JSON is defined in Table 8-1. Here, the property of direction sets the direction for the message which is sent from the service platform to the PU or from the PU to the service platform. There are several properties contained in the "Request message body" which are request method, request URL, request message header and request content. For response message body, there are mainly three categories, namely, return status code, response message header and response message payload.
+
+**Table 8-1 – Interface message for HTTPS+JSON**
+
+|                       |                         |              |
+|-----------------------|-------------------------|--------------|
+| Protocol type         |                         | HTTPS + JSON |
+| Direction             |                         |              |
+| Request message body  | Request method          |              |
+|                       | Request URL             |              |
+|                       | Request message header  |              |
+|                       | Request content         |              |
+| Response message body | Return status code      |              |
+|                       | Response message header |              |
+|                       | Response content        |              |
+
+The standard message for WebSocket protocol and JSON format is defined in Table 8-2. Here, Request name refers to the main purpose of this message. The message type can be either remote procedure call (RPC) or Event type (seen in clause 9.3.2). The property of Direction defines the direction for the message which is sent from the service platform to the PU or from the PU to the service platform. There are several parameters that can be defined in the Request message body according to requirements. For response message body, there are mainly two types, namely, return status code and response content.
+
+**Table 8-2 – Interface message for WebSocket and JSON**
+
+|                                           |                    |
+|-------------------------------------------|--------------------|
+| Request name                              |                    |
+| Message type                              |                    |
+| Direction                                 |                    |
+| Request message body<br>(Request content) |                    |
+| Response<br>message body                  | Return status code |
+|                                           | Response content   |
+
+# 9 Protocols for home surveillance system (HSS)
+
+## 9.1 Requirements of the network transmission function
+
+The protocols defined in this Recommendation are required to support the secure reliable transport (SRT) / user datagram protocol (UDP), WebSocket / TCP and HTTP over TLS [IETF RFC 2818] transmission protocols requirements. The connection between interfaces is required to support HTTP short connection and long connection mechanisms which are in accord with the regulations specified as hypertext transfer protocol – HTTP/1.1 [IETF RFC 7230]. The data transmitted through networks is required to be encrypted using the secure sockets layer (SSL) / transport layer security (TLS) to ensure data security.
+
+## 9.2 Requirements of access function
+
+The interface information delivered via access function protocols is recommended to use the resource in representation state transfer (REST) architecture, using URI as a unique identification. The major purpose of the access function protocol is to provide authentication and access control for accessing devices. In general, HTTP protocols are recommended for access control. Specifically, a new parameter <Mac-Identity> is recommended to be used to extend the common HTTP header field for representing the requester. Here, the Mac address or similar unique information is required to identify the device when considering the public access networks environment.
+
+## 9.3 Requirements of service function
+
+This clause will provide a detailed description about the requirements of a service function.
+
+### 9.3.1 Interface of scheduling service – Vs
+
+A scheduling server sends instructions to PUs through Vs and instructs PUs to connect to the designated signalling server and the peer-to-peer server. The response information is required to contain a timestamp to synchronize the system time of the dispatching server to PUs. Vs uses HTTPS and JSON.
+
+![Sequence diagram showing the flow of scheduling service between PU, CMU, and SCU. The sequence is: 1. PU sends 'Request: Device access (Mac-ID)' to CMU. 2. CMU sends 'Response: Server address, timestamp' back to PU. 3. PU sends 'Request: Request for connection' to SCU. The diagram is labeled H.627.2(22) at the bottom right.](4801720824e4b5e2361a5564f91cfb70_img.jpg)
+
+```
+
+sequenceDiagram
+    participant PU
+    participant CMU
+    participant SCU
+    Note right of SCU: H.627.2(22)
+    PU->>CMU: Request: Device access (Mac-ID)
+    CMU-->>PU: Response: Server address, timestamp
+    PU->>SCU: Request: Request for connection
+  
+```
+
+Sequence diagram showing the flow of scheduling service between PU, CMU, and SCU. The sequence is: 1. PU sends 'Request: Device access (Mac-ID)' to CMU. 2. CMU sends 'Response: Server address, timestamp' back to PU. 3. PU sends 'Request: Request for connection' to SCU. The diagram is labeled H.627.2(22) at the bottom right.
+
+**Figure 9-1 – Flow of scheduling service**
+
+#### 9.3.1.1 Scheduling service procedure
+
+The procedure of scheduling service shown in Figure 9-1 is as follows:
+
+- 1 When a PU is successfully connected to the Internet, it is required to send a scheduling Request to a preset address which is configured in SDK in advance.
+- 2 The scheduling service module in CMU is required to check the Mac-ID and relevant information to determine the current signalling server address, P2P server, and current timestamp in the Response message.
+- 3 When receiving the Response, the PU compares the timestamp with the current system time. If the difference is larger than a threshold (i.e., 10 s), the system time is reset with the received timestamp to ensure synchronization.
+- 4 The device sends a connection Request according to the address information contained in the Response to the SCU.
+
+#### 9.3.1.2 Re-scheduling service procedure
+
+The device needs to send a new scheduling request if it is required to restart services. The situations that may cause re-scheduling service is as follows:
+
+- 1 If the PU is running normally but some network signalling or transmission request fails, it may cause several re-connection requests between the device and the signalling server. When there are multiple re-connection failures (i.e., more than 15 times), the PU is required to send a re-scheduling request.
+- 2 If the PU works normally, the signalling server sends a rescheduling request to the device when assuming asynchronized procedure is agreed upon. The device will initiate a rescheduling procedure if all other sessions are proceeded in normal.
+
+#### 9.3.1.3 Service re-connection procedure
+
+There are some unusual reasons such as abnormal network conditions that can cause connection failures between the devices and the scheduling service module. However, it is still required to avoid re-connection requests congestion in some single moment when many devices send requests for service re-connection. It is recommended to follow the rules as given below:
+
+- 1 Assuming N represents re-connection tries, the device needs to hibernate some time period  $[0, 5*N]$  seconds if  $N \leq 12$ ;
+- 2 The device is required to hibernate for 60 seconds and then sends a re-connection request if  $N > 12$ .
+
+### 9.3.2 Interface of device management – Vd
+
+Vd defines the control signalling of PUs, including device management, status query, device control, status subscription, live broadcast, network configuration, cloud platform control, alarm reporting, talkback and other functions. Vd uses WebSocket and JSON protocols.
+
+#### 9.3.2.1 Interface protocols
+
+There are two types of interface messages for device management. One is remote procedure call (RPC) which is called a request-response mode, and the other is Event for event notification without responses.
+
+##### 9.3.2.1.1 RPC message
+
+RPC is used for a request-response mode. Both PU and the service platform are required to initiate RPC requests. Regarding a single direction, the responder is required to process and reply to the request according to the timing order of arrivals. The RPC message template is shown in Table 9-1.
+
+**Table 9-1 – RPC message template**
+
+|                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Request content    | {<br>"req": < request name, string, required>;<br>"params": < request content, JSON object, optional, values of RPC method>, if there is no value for the method this field does not exist;<br>"seq": < sequence number of RPC request message, int, required >, the calculation value adds one for each request;<br>}                                                                                                                                                                                                                      |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| Response content   | { //successful calling examples<br>"seq": < sequence number of RPC request message, int, required; to be consistent with the sequence number of the corresponding RPC requests>;<br>"resp": < response content, JSON object, required>;<br>}<br><br>{ //failed call example<br>"seq": < sequence number of RPC request message, int, required> to be consistent with the sequence number of the corresponding RPC request<br>>,<br>"err": {<br>"code": < error code, int, required>,<br>"msg": < error message, string, required><br>}<br>} |
+
+The communication procedure of the RPC message is shown in Figure 9-2.
+
+![Sequence diagram showing the communication procedure between PU and SCU. The sequence starts with a 'Setup: WebSocket' message from SCU to PU. Then, PU sends 'Request #1' to SCU, which responds with 'Response #1'. Next, PU sends 'Request #2' to SCU, which responds with 'Response #2'. The diagram is labeled H.627.2(22) at the bottom right.](bffdddb47fced140f8d17fdc2a29f592_img.jpg)
+
+```
+
+sequenceDiagram
+    participant PU
+    participant SCU
+    Note right of SCU: H.627.2(22)
+    SCU->>PU: Setup: WebSocket
+    PU->>SCU: Request #1
+    SCU-->>PU: Response #1
+    PU->>SCU: Request #2
+    SCU-->>PU: Response #2
+  
+```
+
+Sequence diagram showing the communication procedure between PU and SCU. The sequence starts with a 'Setup: WebSocket' message from SCU to PU. Then, PU sends 'Request #1' to SCU, which responds with 'Response #1'. Next, PU sends 'Request #2' to SCU, which responds with 'Response #2'. The diagram is labeled H.627.2(22) at the bottom right.
+
+**Figure 9-2 – Communication procedure of RPC message**
+
+##### 9.3.2.1.2 Event message
+
+Event message works in a no response mode. Both PU and service platform are required to send an Event message to each other. The Event message template is shown in Table 9-2.
+
+**Table 9-2 – Event message template**
+
+|                 |                                                                                                                                                                                            |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Request content | {<br>"event": < request name, string, required>,<br>"params": < request content, JSON object, optional, parameter >; this field does not exist if there is no value for the parameter<br>} |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+The communication procedure of the Event message is shown in Figure 9-3.
+
+![Sequence diagram showing communication between PU and SCU. The sequence starts with 'Set up: WebSocket' from SCU to PU. Then 'Request #1' is sent from PU to SCU. Finally, 'Request #2' is sent from SCU to PU. The diagram is labeled H.627.2(22).](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg)
+
+```
+
+sequenceDiagram
+    participant SCU
+    participant PU
+    Note right of SCU: H.627.2(22)
+    SCU->>PU: Set up: WebSocket
+    PU->>SCU: Request #1
+    SCU->>PU: Request #2
+  
+```
+
+Sequence diagram showing communication between PU and SCU. The sequence starts with 'Set up: WebSocket' from SCU to PU. Then 'Request #1' is sent from PU to SCU. Finally, 'Request #2' is sent from SCU to PU. The diagram is labeled H.627.2(22).
+
+**Figure 9-3 – Communication procedure of Event message**
+
+#### 9.3.2.2 Messages for Vd
+
+When the connection is establishing, the format of WebSocket URL is shown as below:
+
+wss://<domain:port>/Vd?login\_code=<device ID>&login\_passwd=<login password>&hardware\_model=<hardware model>&firmware\_model=<firmware version>&sdk=<SDK version>&reconnect=<reconnect or not>(optional)
+
+Field information is shown in Table 9-3.
+
+**Table 9-3 – Detailed information for the above fields**
+
+| Name           | Type   | Information                                                                                                                                                                                                                      |
+|----------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| login_code     | string | Required: device ID                                                                                                                                                                                                              |
+| login_passwd   | string | Required: Device login password. If the device ID and login password in the URL do not match the pre-configured information stored in the service platform, the login fails.                                                     |
+| hardware_model | string | Required: Hardware model which is customized by the manufacturer is used for problem tracking and remote firmware upgrades.                                                                                                      |
+| firmware_model | string | Required: Firmware version which is customized by the manufacturer is used for problem tracking and remote firmware upgrades.                                                                                                    |
+| sdk            | string | Optional: The current version of the SDK is filled within SDK. If the SDK is not used, this parameter can be omitted. The default value is null.                                                                                 |
+| reconnect      | int    | Optional: To confirm whether this connection is a reconnect or not. "0" means this connection is the first connection after start up. "1" means this connection is a reconnect after a disconnection. The default value is zero. |
+
+Table 9-4 describes detailed messages used for Vd, which contains three parts including message name, message type and detailed description about this message.
+
+**Table 9-4 – Detailed information for Vd messages**
+
+| <b>Message name</b>    | <b>Message type</b> | <b>Description</b>                                                                                                               |
+|------------------------|---------------------|----------------------------------------------------------------------------------------------------------------------------------|
+| Heartbeat report       | RPC                 | A PU is required to use this message to periodically report its working status to the service platform.                          |
+| Get server information | RPC                 | A PU is required to use this message to obtain the IP address from the service platform.                                         |
+| Binding report         | EVENT               | A PU is required to use this message to send the binding information to the service platform.                                    |
+| Reboot channel         | EVENT               | The service platform is required to use this message to ask a PU to reboot a specified channel.                                  |
+| Reboot device          | EVENT               | The service platform is required to use this message to reboot a PU.                                                             |
+| Reschedule device      | EVENT               | The service platform is required to use this message to ask a PU to conduct a re-schedule service procedure.                     |
+| Upgrade firmware       | EVENT               | The service platform is required to use this message to launch a firmware upgrade procedure for a PU.                            |
+| Upgrade status query   | RPC                 | The service platform is required to use this message to inquire and present the upgrade status of a PU, such as the process bar. |
+| Set device time        | RPC                 | The service platform is required to use this message to set the date and time of a PU.                                           |
+| Query device time      | RPC                 | The service platform is required to use this message to inquire about the date and time of a PU.                                 |
+| Query device status    | RPC                 | The service platform is required to use this message to inquire about the running status of a PU.                                |
+| Push live video        | RPC                 | The service platform is required to use this message to ask a PU to push a live video stream to an assigned URL.                 |
+| Stop live video        | RPC                 | The service platform is required to use this message to ask a PU to stop pushing live video.                                     |
+| Start recording        | RPC                 | The service platform is required to use this message to ask a PU to make records and upload them to the cloud storage.           |
+| Stop recording         | RPC                 | The service platform is required to use this message to ask a PU to stop recording.                                              |
+| Alarm notification     | RPC                 | A PU is required to use this message to report alarm events.                                                                     |
+| PTZ control            | EVENT               | The service platform is required to use this message to control Pan/Tilt/Zoom (PTZ).                                             |
+| Get list               | RPC                 | The service platform is required to use this message to obtain the PTZ preset list of a PU.                                      |
+| Get configuration      | RPC                 | The service platform is required to use this message to obtain the configuration of a PU.                                        |
+| Set configuration      | RPC                 | The service platform is required to use this message to set the configuration of a PU.                                           |
+
+**Table 9-4 – Detailed information for Vd messages**
+
+| Message name         | Message type | Description                                                                                                                                                                        |
+|----------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Reset configuration  | RPC          | The service platform is required to use this message to reset the configuration of a PU.                                                                                           |
+| Snapshot             | RPC          | The service platform is required to use this message to take a snapshot of the camera screen and upload it to the service platform.                                                |
+| Start playing        | EVENT        | The service platform is required to use this message to ask a PU to play a video.                                                                                                  |
+| Control playing      | EVENT        | The service platform is required to use this message to control video playing.                                                                                                     |
+| Query playing status | RPC          | The service platform is required to use this message to inquire about the playing state of a PU.                                                                                   |
+| Keep awake           | RPC          | The service platform is required to use this message to prevent a PU and its specified channel from hibernating within a specified time or wake up a PU and its specified channel. |
+| Battery reporting    | EVENT        | A PU is required to use this message to report the current power to the service platform.                                                                                          |
+| Get capability list  | RPC          | The service platform is required to use this message to obtain the capability list of a PU.                                                                                        |
+| Upload log           | RPC          | The service platform is required to use this message to control a PU to upload its logs for debugging and analysis.                                                                |
+| Upload log done      | EVENT        | A PU is required to use this message to inform the service platform that the log file is uploaded.                                                                                 |
+| Get disk information | RPC          | The service platform is required to use this message to get the SD card status of a PU.                                                                                            |
+| Format disk          | RPC          | The service platform is required to use this message to format the SD card of a PU.                                                                                                |
+
+### 9.3.3 Interface of media broadcasting service – Vm
+
+When the SCU receives a command for publishing the video, a PU uploads the video to the service platform. If SCU receives a command for stopping, the PU stops uploading. The media broadcasting service interface Vm uses the SRT protocol for providing media broadcasting services.
+
+#### 9.3.3.1 Specification of interface Vm
+
+Vm is responsible for media data transmission while data transmission control is realized by the device management interface (Vd).
+
+##### 9.3.3.1.1 Media broadcasting service procedure
+
+![Sequence diagram of the media broadcasting service procedure involving PU, SCU, MDU, and CU.](7f25db95ce3916c0e09803b861a2f7bc_img.jpg)
+
+```
+sequenceDiagram
+    participant CU
+    participant MDU
+    participant SCU
+    participant PU
+    Note right of CU: H.627.2(22)
+    CU->>SCU: Request: Start live media
+    SCU->>PU: Pushing live media streaming
+    PU->>MDU: Setting up a connection
+    PU->>MDU: Pushing live media streaming
+    MDU->>CU: Push live media
+    Note right of MDU: ...
+    CU->>SCU: Request: Stop live media
+    SCU->>PU: Stopping live media streaming
+    PU->>MDU: Disconnection
+```
+
+The diagram illustrates the sequence of messages for the media broadcasting service procedure. It involves four entities: PU (Primary User), SCU (Service Control Unit), MDU (Media Distribution Unit), and CU (Customer Unit). The sequence starts with the CU sending a 'Request: Start live media' to the SCU. The SCU responds with 'Pushing live media streaming' to the PU. The PU then performs 'Setting up a connection' with the MDU. Once connected, the PU sends 'Pushing live media streaming' to the MDU, which in turn 'Push live media' to the CU. A vertical ellipsis indicates a continuation of the streaming. When the user wants to stop, the CU sends a 'Request: Stop live media' to the SCU. The SCU commands the PU to perform 'Stopping live media streaming'. Finally, the PU sends a 'Disconnection' message to the MDU. The diagram is labeled 'H.627.2(22)' in the bottom right corner.
+
+Sequence diagram of the media broadcasting service procedure involving PU, SCU, MDU, and CU.
+
+**Figure 9-4 – Media broadcasting service procedure**
+
+The media broadcasting service procedure is shown in Figure 9-4. The steps are as follows:
+
+- 1 Users send the "start live media" request on the CU if they want to watch the live media streaming;
+- 2 After receiving the "start live media streaming" request from the CU, the service platform (SCU) sends a "push live media" command to the PU;
+- 3 The PU sets up a connection with the MDU, after receiving the address;
+- 4 After the connection is established, the PU pushes a live media streaming to the MDU by using the SRT protocol. Then the media server (MS) pushes the live media streaming to the CU;
+- 5 Users send "stop live media" requests on the CU to the SCU;
+- 6 After receiving the "stop live media" request from the CU, the service platform (SCU) sends a "stop live media" command to the PU;
+- 7 The PU stops pushing the live media streaming and disconnects with the media server after it receives the command.
+
+#### 9.3.3.2 Messages of Vm
+
+##### 9.3.3.2.1 Starting media broadcasting service
+
+The service platform sends the "pushing live media streaming" command to the PU via Vd. After receiving the command, the PU pushes a live media streaming to the dedicated URL address, which is embedded in the command. The messages used here are required to support the SRT protocol. Please refer to clause 9.3.3.1.1 for more information.
+
+##### 9.3.3.2.2 Stopping media service
+
+The service platform sends the "stopping live media streaming" command to the PU via Vd. After the PU receives the command, it stops pushing the live media streaming. The messages used here are required to support the SRT protocol. Please refer to clause 9.3.3.1.1 for more information.
+
+### 9.3.4 Interface of video service – Vr
+
+The video service uses the interface Vr to realize the functions of video storage and distribution, video content upload, video metadata upload, and look back. When Vr receives a command of starting a record, a PU uploads the video to the storage device. After receiving a command of stopping the service, the PU stops uploading. Vr uses HTTPS and JSON protocols.
+
+#### 9.3.4.1 Specification of interface Vr
+
+##### 9.3.4.1.1 Video storage procedure
+
+![Sequence diagram of the video storage procedure between PU and CS.](523ab7b925beb555f88b2e1e1336974f_img.jpg)
+
+```
+sequenceDiagram
+    participant PU
+    participant CS
+    Note left of PU: Video segment
+    PU->>CS: 1. Request: Upload url  
+2. Metadata of the previous video
+    CS-->>PU: Return upload url
+    PU->>CS: Upload video segment
+    Note right of CS: H.627.2(22)
+```
+
+The diagram illustrates the video storage procedure between a User Equipment (PU) and a Cloud Server (CS). The sequence of messages is as follows: 1. The PU sends a request containing the upload URL and metadata of the previous video to the CS. 2. The CS responds with the upload URL. 3. The PU then uploads the video segment to the CS. The diagram is labeled with 'H.627.2(22)' at the bottom right.
+
+Sequence diagram of the video storage procedure between PU and CS.
+
+Figure 9-5 – Video storage procedure
+
+The entire procedure of video storage is shown in Figure 9-5. The steps are as follows:
+
+- 1) For a video segment, the PU requests an upload URL from the service platform and reports the metadata of the latest video segment if there was already a previous video segment.
+- 2) The service platform returns an upload URL and records the metadata of the latest video segment.
+- 3) The PU uploads the video segment to the CS.
+- 4) Repeat steps from 1 to 3.
+
+##### 9.3.4.1.2 Exceptional handling
+
+Note that some network abnormal issues may lead to video segment uploading failures. The PU is required to re-upload several times as possible. If the final uploading fails, the PU is required to send a message to the CS to notify that the task of video segment uploading finally fails. Then, the service platform will clean up all the residual information about this video segment.
+
+###### 9.3.4.1.3 Uploading confirmation
+
+In general, there is a two-stage strategy defined for video segment uploading. For each segment uploading task, the interface Vr has to be called twice. One is for the previous segment confirmation and another is for the next segment creation. To improve efficiency, it is recommended to confirm the two-stage requests at the same time since the video segments are consecutively uploaded.
+
+#### 9.3.4.2 Message of Vr
+
+The PU relies on the interface Vr to call the storage service using HTTPS and JSON. Each PU is required to establish a corresponding channel. To identify each video storage task, a specific HTTPS URI for each video channel must be assigned.
+
+For example,
+
+<https://<domain:port>/live/cseg/<channel ID>>.
+
+Here, the channel ID is the channel identification assigned by the service platform for each PU. This ID is used to distinguish the video requests of different PUs. The PU uses the POST method to initiate a request and the response is returned in the JSON format.
+
+**Table 9-5 – Detailed information for Vr messages**
+
+| <b>Message name</b>     | <b>Message type</b> | <b>Description</b>                                                                                                      |
+|-------------------------|---------------------|-------------------------------------------------------------------------------------------------------------------------|
+| Create video segment    | HTTPS+JSON          | A PU is required to use this message to request the service platform to allocate resources for storing a video segment. |
+| Confirm video segment   | HTTPS+JSON          | A PU is required to use this message to confirm with the service platform the information of a video segment.           |
+| Cancel video segment    | HTTPS+JSON          | A PU is required to use this message to notify the service platform of which video segment is to be cancelled.          |
+| Get server information  | HTTPS+JSON          | A PU is required to use this message to obtain the date and time of the service platform.                               |
+| Report statistical data | HTTPS+JSON          | A PU is required to use this message to report the statistical data of the video segment within a time interval.        |
+
+# Appendix I
+
+## Interface message examples
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## I.1 Messages of the scheduling service interface
+
+**Table I.1 – Specification of scheduling service interface**
+
+|                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Protocol               | HTTPS + JSON                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| Direction              | From PU to platform                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| Request method         | GET                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| Request URL            | <a href="https://&lt;domain:port&gt;/Vs/getServerAddr?macid=XXXXX">https://&lt;domain:port&gt;/Vs/getServerAddr?macid=XXXXX</a>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| Request message header | None                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| Request content        | {<br>"mac_id": <required, string><br>}                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| Return status code     | 200: normal<br>400~499: user input error<br>500~599: service error                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| Response content       | <pre> {//successful response   "PassDomain":"www.test01.com ",      //signalling server address   "P2p_passDomain":"www.test02.com ", // P2P server address   "TurnDomain": "www.test03.com ",      //turn server address   "HibernationDomain": "www.test04.com", //hibernation server address   "PassPort": xxxx,                   //signalling server ws interface(non-encryption   interface)   "Secure_PassPort": xxxx,            //signalling server wss interface(send non-zero   value if the PU supports wss protocol)   "P2p_passPort": xxxx,               //P2P interface   "TurnPort": xxxx,                   //turn server port   "SyncTime": xxxxx                  //current time of the service platform }  {//failed response   "info": &lt;string, required: error description&gt; } </pre> |
+
+## I.2 Messages of device management interface
+
+### I.2.1 An example of keeping alive report
+
+**Table I.2-1 – Keep alive report message**
+
+|              |                     |
+|--------------|---------------------|
+| Request name | Keepalive           |
+| Message type | RPC                 |
+| Direction    | From PU to platform |
+
+**Table I.2-1 – Keep alive report message**
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |            |                 |                |                |                  |               |                     |                |               |               |                  |               |                 |                 |             |                |               |               |               |               |                 |                  |
+|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------|----------------|----------------|------------------|---------------|---------------------|----------------|---------------|---------------|------------------|---------------|-----------------|-----------------|-------------|----------------|---------------|---------------|---------------|---------------|-----------------|------------------|
+| Request content     | <pre>{   "mac_id": &lt;required, string&gt;   "state": &lt;required, int; device status, 1:online, 2: upgrading, 3: error&gt;   "channels": [{     "channel": &lt;required, int&gt;,     "state": &lt;required, int; channel status, 0: offline, 1: online, 3: error, 4: disable&gt;,     "stream_id": &lt;optional, string; channel stream_id represents the channel which is     currently used for streaming. Note if stream_id is null or does not exist, the     corresponding channel cannot be used for streaming&gt;     "record_session": &lt;optional, string; record_session represents the index of session     being currently used for recording in the service platform. Note if the record_session is     null or does not exist, the PU is not recording&gt;     "alarm": &lt;optional, int; flags, each bit position of current alarm status shown in     flags represents one alarm type,     Flag = 1, the corresponding type of alarm is triggered     More information about specific values is defined in the table of alarm status flags&gt;   }] }</pre> |            |                 |                |                |                  |               |                     |                |               |               |                  |               |                 |                 |             |                |               |               |               |               |                 |                  |
+| Return status code  | <p>200: normal<br/>         400~499: user input error<br/>         500~599: server error</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |            |                 |                |                |                  |               |                     |                |               |               |                  |               |                 |                 |             |                |               |               |               |               |                 |                  |
+| Response content    | <p>flags</p> <table border="1"> <tr> <td>alarm type</td> <td>position of bit</td> </tr> <tr> <td>external alarm</td> <td>the second bit</td> </tr> <tr> <td>motion detection</td> <td>the third bit</td> </tr> <tr> <td>intrusion detection</td> <td>the fourth bit</td> </tr> <tr> <td>cry detection</td> <td>the fifth bit</td> </tr> <tr> <td>face recognition</td> <td>the sixth bit</td> </tr> <tr> <td>sound detection</td> <td>the seventh bit</td> </tr> <tr> <td>low battery</td> <td>the eighth bit</td> </tr> <tr> <td>lock breaking</td> <td>the ninth bit</td> </tr> <tr> <td>ring the bell</td> <td>the tenth bit</td> </tr> <tr> <td>human detection</td> <td>the eleventh bit</td> </tr> </table>                                                                                                                                                                                                                                                                                                                                                                 | alarm type | position of bit | external alarm | the second bit | motion detection | the third bit | intrusion detection | the fourth bit | cry detection | the fifth bit | face recognition | the sixth bit | sound detection | the seventh bit | low battery | the eighth bit | lock breaking | the ninth bit | ring the bell | the tenth bit | human detection | the eleventh bit |
+| alarm type          | position of bit                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |            |                 |                |                |                  |               |                     |                |               |               |                  |               |                 |                 |             |                |               |               |               |               |                 |                  |
+| external alarm      | the second bit                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |            |                 |                |                |                  |               |                     |                |               |               |                  |               |                 |                 |             |                |               |               |               |               |                 |                  |
+| motion detection    | the third bit                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |            |                 |                |                |                  |               |                     |                |               |               |                  |               |                 |                 |             |                |               |               |               |               |                 |                  |
+| intrusion detection | the fourth bit                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |            |                 |                |                |                  |               |                     |                |               |               |                  |               |                 |                 |             |                |               |               |               |               |                 |                  |
+| cry detection       | the fifth bit                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |            |                 |                |                |                  |               |                     |                |               |               |                  |               |                 |                 |             |                |               |               |               |               |                 |                  |
+| face recognition    | the sixth bit                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |            |                 |                |                |                  |               |                     |                |               |               |                  |               |                 |                 |             |                |               |               |               |               |                 |                  |
+| sound detection     | the seventh bit                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |            |                 |                |                |                  |               |                     |                |               |               |                  |               |                 |                 |             |                |               |               |               |               |                 |                  |
+| low battery         | the eighth bit                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |            |                 |                |                |                  |               |                     |                |               |               |                  |               |                 |                 |             |                |               |               |               |               |                 |                  |
+| lock breaking       | the ninth bit                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |            |                 |                |                |                  |               |                     |                |               |               |                  |               |                 |                 |             |                |               |               |               |               |                 |                  |
+| ring the bell       | the tenth bit                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |            |                 |                |                |                  |               |                     |                |               |               |                  |               |                 |                 |             |                |               |               |               |               |                 |                  |
+| human detection     | the eleventh bit                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |            |                 |                |                |                  |               |                     |                |               |               |                  |               |                 |                 |             |                |               |               |               |               |                 |                  |
+
+### **I.2.2 An example of getting server information**
+
+**Table I.2-2 – Get server information**
+
+|                 |                                                                                                                                        |
+|-----------------|----------------------------------------------------------------------------------------------------------------------------------------|
+| Request name    | GetServerInfo                                                                                                                          |
+| Message type    | RPC                                                                                                                                    |
+| Direction       | From PU to platform                                                                                                                    |
+| Request content | <pre>{   "mac_id": &lt;required, string&gt;   "state": &lt;required, int; device status, 1: online, 2: upgrading, 3: error&gt; }</pre> |
+
+**Table I.2-2 – Get server information**
+
+|                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error                                                                                                                                                                                                                                                                                                                                                                                                       |
+| Response content   | {<br>"hibernation": <optional, string; format of hibernation server address, IP: port, Hibernation is not available if this field is null or non-exist>,<br>"hb_interval": <optional, int: device heartbeat interval(sec), the default is 10 seconds if this field does not exist>,<br>"hb_token": <optional, string: hibernation service token, length is no more than 16 characters. Token is not required for hibernation service if this field does not exist><br>} |
+
+### **I.2.3 An example of getting binding report**
+
+**Table I.2-3 – Binding report**
+
+|                    |                                                                         |
+|--------------------|-------------------------------------------------------------------------|
+| Request name       | Bind                                                                    |
+| Message type       | Event                                                                   |
+| Direction          | From PU to platform                                                     |
+| Request content    | {<br>"mac_id": <required, string><br>"bind_id": <required, string><br>} |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error       |
+| Response content   | None                                                                    |
+
+### **I.2.4 An example of rebooting channel**
+
+**Table I.2-4 – Reboot channel**
+
+|                    |                                                                   |
+|--------------------|-------------------------------------------------------------------|
+| Request name       | RebootChannel                                                     |
+| Message type       | Event                                                             |
+| Direction          | From platform to PU                                               |
+| Request content    | {<br>"channel": <required, int><br>}                              |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error |
+| Response content   | None                                                              |
+
+### I.2.5 An example of rebooting device
+
+**Table I.2-5 – Reboot device**
+
+|                    |                                                                   |
+|--------------------|-------------------------------------------------------------------|
+| Request name       | RebootDevice                                                      |
+| Message type       | Event                                                             |
+| Direction          | From platform to PU                                               |
+| Request content    | None                                                              |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error |
+| Response content   | None                                                              |
+
+### I.2.6 An example of rescheduling device
+
+**Table I.2-6 – Reschedule device**
+
+|                    |                                                                   |
+|--------------------|-------------------------------------------------------------------|
+| Request name       | Reschedule                                                        |
+| Message type       | Event                                                             |
+| Direction          | From platform to PU                                               |
+| Request content    | None                                                              |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error |
+| Response content   | None                                                              |
+
+### I.2.7 An example of upgrading firmware
+
+**Table I.2-7 – Upgrade firmware**
+
+|                    |                                                                             |
+|--------------------|-----------------------------------------------------------------------------|
+| Request name       | UpgradeFirmware                                                             |
+| Message type       | Event                                                                       |
+| Direction          | From platform to PU                                                         |
+| Request content    | {<br>"firmware_model": <required, string><br>"url": <required, string><br>} |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error           |
+| Response content   | None                                                                        |
+
+### I.2.8 An example of querying upgrading status
+
+**Table I.2-8 – Query upgrade status**
+
+|                    |                                                                                                                                                                                                              |
+|--------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Request name       | QueryUpgrade                                                                                                                                                                                                 |
+| Message type       | RPC                                                                                                                                                                                                          |
+| Direction          | From platform to PU                                                                                                                                                                                          |
+| Request content    | None                                                                                                                                                                                                         |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error                                                                                                                                            |
+| Response content   | {<br>"upgrade_status": <required, string; upgrading status: notstart/downloading/installing/done/error><br>"progress": <required, int; current progress, 0-100><br>"firmware_model": <required, string><br>} |
+
+### I.2.9 An example of setting device time
+
+**Table I.2-9 – Set device time**
+
+|                    |                                                                                                                                             |
+|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------|
+| Request name       | Settime                                                                                                                                     |
+| Message type       | RPC                                                                                                                                         |
+| Direction          | From platform to PU                                                                                                                         |
+| Request content    | {<br>"datetime": <required, string; format: yyyy-MM-ddTHH:mm:ss><br>"tz": <optional, int; time zone code><br>"offset": <required, int><br>} |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error                                                                           |
+| Response content   | None                                                                                                                                        |
+
+### I.2.10 An example of querying device time
+
+**Table I.2-10 – Query device time**
+
+|                    |                                                                   |
+|--------------------|-------------------------------------------------------------------|
+| Request name       | QueryTime                                                         |
+| Message type       | RPC                                                               |
+| Direction          | From platform to PU                                               |
+| Request content    | None                                                              |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error |
+
+**Table I.2-10 – Query device time**
+
+|                  |                                                                                                                |
+|------------------|----------------------------------------------------------------------------------------------------------------|
+| Response content | {<br>"datetime": <required, string; format: yyyy-MM-ddTHH:mm:ss><br>"tz": <optional, int; time zone code><br>} |
+|------------------|----------------------------------------------------------------------------------------------------------------|
+
+#### **I.2.11 An example of querying device status**
+
+**Table I.2-11 – Query device status**
+
+|                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|--------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Request name       | DevStatus                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| Message type       | RPC                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| Direction          | From platform to PU                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| Request content    | None                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| Response content   | {<br>"dev_id": <required, string: device ID><br>"hardware_model": <required, string: device model><br>"firmware_model": <required, string: device firmware version number><br>"last_upgrade_datetime": <required, string; last successfully upgrading time, format: YY-MM-DDTHH:MM:SS, e.g., 2016-12-05T02:15:32><br>"wifi_ssid": <optional, string: the ssid of the wifi currently connected, the absence of this field or an empty string means that the device is not connected to wifi><br>"wifi_signal": <optional, int: the current wifi signal strength of the device ><br>"up_bandwidth": <optional, int: maximum uplink bandwidth detected by the device, unit bps, if it does not exist, it means the uplink bandwidth is unknown><br>"down_bandwidth": <optional, int: minimum downlink bandwidth detected by the device, unit bps, if it does not exist, it means the downlink bandwidth is unknown><br>"ip_addr": <optional, string: the current internal network IP address of the device, if it does not exist, it means the IP address is unknown><br>"mac_addr": <optional, string: the mac address of the device network card, if it does not exist, it means the mac address is unknown><br>"battery": <optional, int: current device battery level, 0-100 ><br>} |
+
+### **I.2.12 An example of pushing live video**
+
+**Table I.2-12 – Push live video**
+
+|              |                     |
+|--------------|---------------------|
+| Request name | PushLive            |
+| Message type | RPC                 |
+| Direction    | From platform to PU |
+
+**Table I.2-12 – Push live video**
+
+|                    |                                                                                                                                                                                                                                        |
+|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Request content    | {<br>"channel": <required, int><br>"url": <required, string; preferred destination URL1 for streaming><br>"stream_id": <required, string; the ID used by the platform to identify this stream><br>"max_bitrate": <required, int ><br>} |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error<br>11: the code stream is too large<br>12: parameter error<br>101: unsupported RPC method                                                                            |
+| Response content   | Pushing stream is successful, or the stream already exists.                                                                                                                                                                            |
+
+#### **I.2.13 An example of stopping live video**
+
+**Table I.2-13 – Stop live video**
+
+|                    |                                                                                                             |
+|--------------------|-------------------------------------------------------------------------------------------------------------|
+| Request name       | StopLive                                                                                                    |
+| Message type       | RPC                                                                                                         |
+| Direction          | From platform to PU                                                                                         |
+| Request content    | {<br>"stream_id": <required, string; the stream_id when push live video><br>"channel": <required, int><br>} |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error                                           |
+| Response content   | Stop pushing is completed, or the stream does not exist.                                                    |
+
+### **I.2.14 An example of starting recording**
+
+**Table I.2-14 – Start recording**
+
+|                 |                                                                                                                                                                                                                                                                                                                                                                                           |
+|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Request name    | StartRecord                                                                                                                                                                                                                                                                                                                                                                               |
+| Message type    | RPC                                                                                                                                                                                                                                                                                                                                                                                       |
+| Direction       | From platform to PU                                                                                                                                                                                                                                                                                                                                                                       |
+| Request content | {<br>"session_id": <required, string; the corresponding record session ID of the platform><br>"channel": <required, int><br>"max_bitrate": <required, int ><br>"seg_duration": <required, int; video segment duration><br>"seg_max_size": <required, int; maximum size of each video segment><br>"seg_max_count": <required, int; maximum number of video segments cached in memory><br>} |
+
+**Table I.2-14 – Start recording**
+
+|                    |                                                                                                                                                                                                                                                                        |
+|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                    | "prerecord_seconds": <optional, int; pre-recorded seconds><br>"start_ts": <required, float; timestamp of the first video segment><br>"cbk_url": <required, callback URL, maximum is 256 bytes; the video module obtains the upload address by requesting the url><br>} |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error<br>11: the code stream is too large<br>12: parameter error<br>101: unsupported RPC method                                                                                                            |
+| Response content   | None                                                                                                                                                                                                                                                                   |
+
+#### **I.2.15 An example of stopping record**
+
+**Table I.2-15 – Stop recording**
+
+|                    |                                                                                                                                  |
+|--------------------|----------------------------------------------------------------------------------------------------------------------------------|
+| Request name       | StopRecord                                                                                                                       |
+| Message type       | RPC                                                                                                                              |
+| Direction          | From platform to PU                                                                                                              |
+| Request content    | {<br>"session_id": <required, string; the corresponding recording session ID of the platform><br>"channel": <required, int><br>} |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error                                                                |
+| Response content   | Stop recording is completed, or the record session does not exist.                                                               |
+
+#### **I.2.16 An example of alarming notification**
+
+**Table I.2-16 – Alarm notification**
+
+|              |                     |
+|--------------|---------------------|
+| Request name | AlarmNotify         |
+| Message type | RPC                 |
+| Direction    | From PU to platform |
+
+**Table I.2-16 – Alarm notification**
+
+| Request content      | <pre> {   "channel": &lt;required, int&gt;   "timestamp": &lt;required, int&gt;   "type": &lt;required, int; alarm type: see the table below&gt;   "state": &lt;required, string enumeration, start/end/pulse&gt;   "desc": &lt;required, string; description&gt; } </pre> Alarm type value: <table border="1" style="width: 100%; border-collapse: collapse;"> <thead> <tr> <th>Type</th> <th>Type value</th> <th>State/Single Trigger</th> </tr> </thead> <tbody> <tr><td>External alarm</td><td>2</td><td>state</td></tr> <tr><td>Motion detection</td><td>3</td><td>state</td></tr> <tr><td>Mixed net</td><td>4</td><td>single</td></tr> <tr><td>Cry detection</td><td>5</td><td>state</td></tr> <tr><td>Face recognition</td><td>6</td><td>state</td></tr> <tr><td>Sound detection</td><td>7</td><td>state</td></tr> <tr><td>Low power</td><td>8</td><td>single</td></tr> <tr><td>Lock picking</td><td>9</td><td>single</td></tr> <tr><td>Bell ring</td><td>10</td><td>single</td></tr> <tr><td>Human detection</td><td>11</td><td>state</td></tr> <tr><td>PIR motion detection</td><td>12</td><td>state</td></tr> </tbody> </table> | Type                 | Type value | State/Single Trigger | External alarm | 2 | state | Motion detection | 3 | state | Mixed net | 4 | single | Cry detection | 5 | state | Face recognition | 6 | state | Sound detection | 7 | state | Low power | 8 | single | Lock picking | 9 | single | Bell ring | 10 | single | Human detection | 11 | state | PIR motion detection | 12 | state |
+|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|------------|----------------------|----------------|---|-------|------------------|---|-------|-----------|---|--------|---------------|---|-------|------------------|---|-------|-----------------|---|-------|-----------|---|--------|--------------|---|--------|-----------|----|--------|-----------------|----|-------|----------------------|----|-------|
+| Type                 | Type value                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | State/Single Trigger |            |                      |                |   |       |                  |   |       |           |   |        |               |   |       |                  |   |       |                 |   |       |           |   |        |              |   |        |           |    |        |                 |    |       |                      |    |       |
+| External alarm       | 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | state                |            |                      |                |   |       |                  |   |       |           |   |        |               |   |       |                  |   |       |                 |   |       |           |   |        |              |   |        |           |    |        |                 |    |       |                      |    |       |
+| Motion detection     | 3                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | state                |            |                      |                |   |       |                  |   |       |           |   |        |               |   |       |                  |   |       |                 |   |       |           |   |        |              |   |        |           |    |        |                 |    |       |                      |    |       |
+| Mixed net            | 4                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | single               |            |                      |                |   |       |                  |   |       |           |   |        |               |   |       |                  |   |       |                 |   |       |           |   |        |              |   |        |           |    |        |                 |    |       |                      |    |       |
+| Cry detection        | 5                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | state                |            |                      |                |   |       |                  |   |       |           |   |        |               |   |       |                  |   |       |                 |   |       |           |   |        |              |   |        |           |    |        |                 |    |       |                      |    |       |
+| Face recognition     | 6                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | state                |            |                      |                |   |       |                  |   |       |           |   |        |               |   |       |                  |   |       |                 |   |       |           |   |        |              |   |        |           |    |        |                 |    |       |                      |    |       |
+| Sound detection      | 7                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | state                |            |                      |                |   |       |                  |   |       |           |   |        |               |   |       |                  |   |       |                 |   |       |           |   |        |              |   |        |           |    |        |                 |    |       |                      |    |       |
+| Low power            | 8                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | single               |            |                      |                |   |       |                  |   |       |           |   |        |               |   |       |                  |   |       |                 |   |       |           |   |        |              |   |        |           |    |        |                 |    |       |                      |    |       |
+| Lock picking         | 9                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | single               |            |                      |                |   |       |                  |   |       |           |   |        |               |   |       |                  |   |       |                 |   |       |           |   |        |              |   |        |           |    |        |                 |    |       |                      |    |       |
+| Bell ring            | 10                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | single               |            |                      |                |   |       |                  |   |       |           |   |        |               |   |       |                  |   |       |                 |   |       |           |   |        |              |   |        |           |    |        |                 |    |       |                      |    |       |
+| Human detection      | 11                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | state                |            |                      |                |   |       |                  |   |       |           |   |        |               |   |       |                  |   |       |                 |   |       |           |   |        |              |   |        |           |    |        |                 |    |       |                      |    |       |
+| PIR motion detection | 12                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | state                |            |                      |                |   |       |                  |   |       |           |   |        |               |   |       |                  |   |       |                 |   |       |           |   |        |              |   |        |           |    |        |                 |    |       |                      |    |       |
+| Return status code   | 200: normal<br>400~499: user input error<br>500~599: server error                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                      |            |                      |                |   |       |                  |   |       |           |   |        |               |   |       |                  |   |       |                 |   |       |           |   |        |              |   |        |           |    |        |                 |    |       |                      |    |       |
+| Response content     | <pre> {   "pic_upload_url": &lt;optional, string&gt; } </pre>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                      |            |                      |                |   |       |                  |   |       |           |   |        |               |   |       |                  |   |       |                 |   |       |           |   |        |              |   |        |           |    |        |                 |    |       |                      |    |       |
+
+#### **I.2.17 An example of PTZ control**
+
+**Table I.2-17 – PTZ control**
+
+| Request name    | CtrlPTZ                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |           |       |    |                                                            |      |               |
+|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-------|----|------------------------------------------------------------|------|---------------|
+| Message type    | EVENT                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |           |       |    |                                                            |      |               |
+| Direction       | From platform to PU                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |           |       |    |                                                            |      |               |
+| Request content | <pre> {   "channel": &lt;required, int&gt;   "op": &lt;required, string; PTZ operation code, see the table below for details&gt;   "value": &lt;optional, int; the table is shown in the table below&gt; } </pre> <table border="1" style="width: 100%; border-collapse: collapse;"> <thead> <tr> <th>operation</th> <th>value</th> </tr> </thead> <tbody> <tr><td>up</td><td>Optional int speed, 0-100, 0 slowest, 100 fast, default 50</td></tr> <tr><td>down</td><td>Same as above</td></tr> </tbody> </table> | operation | value | up | Optional int speed, 0-100, 0 slowest, 100 fast, default 50 | down | Same as above |
+| operation       | value                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |           |       |    |                                                            |      |               |
+| up              | Optional int speed, 0-100, 0 slowest, 100 fast, default 50                                                                                                                                                                                                                                                                                                                                                                                                                                                        |           |       |    |                                                            |      |               |
+| down            | Same as above                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |           |       |    |                                                            |      |               |
+
+**Table I.2-17 – PTZ control**
+
+|                    |                                                                   |                                                              |
+|--------------------|-------------------------------------------------------------------|--------------------------------------------------------------|
+|                    | left                                                              | Same as above                                                |
+|                    | right                                                             | Same as above                                                |
+|                    | upleft                                                            | Same as above                                                |
+|                    | upright                                                           | Same as above                                                |
+|                    | downleft                                                          | Same as above                                                |
+|                    | downright                                                         | Same as above                                                |
+|                    | zoomin                                                            | Same as above                                                |
+|                    | zoomout                                                           | Same as above                                                |
+|                    | stop                                                              | optional, int, but the value is meaningless                  |
+|                    | goto_preset                                                       | Preset ID, 0-255                                             |
+|                    | set_preset                                                        | Same as above                                                |
+|                    | clear_preset                                                      | Same as above                                                |
+|                    | up_step                                                           | optional, int, single step, 0-100, min 0, max 100, default 0 |
+|                    | down_step                                                         | Same as above                                                |
+|                    | left_step                                                         | Same as above                                                |
+|                    | right_step                                                        | Same as above                                                |
+|                    | upleft_step                                                       | Same as above                                                |
+|                    | upright_step                                                      | Same as above                                                |
+|                    | downleft_step                                                     | Same as above                                                |
+|                    | downright_step                                                    | Same as above                                                |
+|                    | zoomin_step                                                       | Same as above                                                |
+|                    | zoomout_step                                                      | Same as above                                                |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error |                                                              |
+| Response content   | None                                                              |                                                              |
+
+#### **I.2.18 An example of getting PTZ preset list**
+
+**Table I.2-18 – Get PTZ preset list**
+
+|                    |                                                                   |
+|--------------------|-------------------------------------------------------------------|
+| Request name       | GetPTZPresetList                                                  |
+| Message type       | RPC                                                               |
+| Direction          | From platform to PU                                               |
+| Request content    | {<br>"channel": <required, int><br>}                              |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error |
+
+**Table I.2-18 – Get PTZ preset list**
+
+|                  |                                                                                                   |
+|------------------|---------------------------------------------------------------------------------------------------|
+| Response content | <pre> "presetList": [   {     "ptzId": &lt;required, int; preset ID, 0-255&gt;   }   ... ] </pre> |
+|------------------|---------------------------------------------------------------------------------------------------|
+
+#### **I.2.19 An example of getting device configuration**
+
+**Table I.2-19 – Get configuration**
+
+|                    |                                                                   |
+|--------------------|-------------------------------------------------------------------|
+| Request name       | GetConfig                                                         |
+| Message type       | RPC                                                               |
+| Direction          | From platform to PU                                               |
+| Request content    | None                                                              |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error |
+| Response content   | Configuration set                                                 |
+
+#### **I.2.20 An example of setting device configuration**
+
+**Table I.2-20 – Set configuration**
+
+|                    |                                                                                                                                                          |
+|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Request name       | SetConfig                                                                                                                                                |
+| Message type       | RPC                                                                                                                                                      |
+| Direction          | From platform to PU                                                                                                                                      |
+| Request content    | User defined                                                                                                                                             |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error<br>12: parameter error<br>13: unsupported configuration<br>102: channel does not exist |
+| Response content   | Configuration set                                                                                                                                        |
+
+#### I.2.21 An example of resetting device configuration
+
+**Table I.2-21 – Reset configuration**
+
+|                    |                                                                   |
+|--------------------|-------------------------------------------------------------------|
+| Request name       | ResetConfig                                                       |
+| Message type       | RPC                                                               |
+| Direction          | From platform to PU                                               |
+| Request content    | None                                                              |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error |
+| Response content   | None                                                              |
+
+#### I.2.22 An example of snapshot
+
+**Table I.2-22 – Snapshot**
+
+|                    |                                                                                                |
+|--------------------|------------------------------------------------------------------------------------------------|
+| Request name       | Snapshot                                                                                       |
+| Message type       | RPC                                                                                            |
+| Direction          | From platform to PU                                                                            |
+| Request content    | {<br>"channel": <required, int><br>"url": <required, string; the url of uploaded picture><br>} |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error                              |
+| Response content   | None                                                                                           |
+
+#### I.2.23 An example of starting playing a video
+
+**Table I.2-23 – Start playing**
+
+|                    |                                                                                          |
+|--------------------|------------------------------------------------------------------------------------------|
+| Request name       | PlayVideo                                                                                |
+| Message type       | EVENT                                                                                    |
+| Direction          | From platform to PU                                                                      |
+| Request content    | {<br>"channel": <required, int><br>"url": <required, string; the url of video file><br>} |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error                        |
+| Response content   | None                                                                                     |
+
+#### I.2.24 An example of controlling playing
+
+**Table I.2-24 – Control playing**
+
+|                    |                                                                                                                                    |
+|--------------------|------------------------------------------------------------------------------------------------------------------------------------|
+| Request name       | CtrlVideo                                                                                                                          |
+| Message type       | EVENT                                                                                                                              |
+| Direction          | From platform to PU                                                                                                                |
+| Request content    | {<br>"channel": <required, int><br>"op": <required, string; play control instructions, stop/pause/resume supported currently><br>} |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error                                                                  |
+| Response content   | None                                                                                                                               |
+
+#### I.2.25 An example of querying playing status
+
+**Table I.2-25 – Query playing status**
+
+|                    |                                                                                                                                                                                                                                         |
+|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Request name       | QueryVideoStatus                                                                                                                                                                                                                        |
+| Message type       | RPC                                                                                                                                                                                                                                     |
+| Direction          | From platform to PU                                                                                                                                                                                                                     |
+| Request content    | {<br>"channel": <required, int><br>}                                                                                                                                                                                                    |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error                                                                                                                                                                       |
+| Response content   | {<br>"status": <required, string; play status, stopped, pausing, playing><br>"url": <optional, string; URL of the video file current playing, if this field is empty or does not exist, it means that it is not currently playing><br>} |
+
+#### I.2.26 An example of keeping awaken
+
+**Table I.2-26 – Keep awake**
+
+|                 |                                                                                                                   |
+|-----------------|-------------------------------------------------------------------------------------------------------------------|
+| Request name    | KeepAwaken                                                                                                        |
+| Message type    | RPC                                                                                                               |
+| Direction       | From platform to PU                                                                                               |
+| Request content | {<br>"channel": <required, int><br>"expired": <required, int; minimum time to keep power on, unit is second><br>} |
+
+**Table I.2-26 – Keep awake**
+
+|                    |                                                                   |
+|--------------------|-------------------------------------------------------------------|
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error |
+| Response content   | None                                                              |
+
+#### **I.2.27 An example of battery change**
+
+**Table I.2-27 – Battery reporting**
+
+|                    |                                                                                      |
+|--------------------|--------------------------------------------------------------------------------------|
+| Request name       | BatteryChange                                                                        |
+| Message type       | EVENT                                                                                |
+| Direction          | From platform to PU                                                                  |
+| Request content    | {<br>"battery": <required, int: current device battery power percentage, 0-100><br>} |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error                    |
+| Response content   | None                                                                                 |
+
+#### **I.2.28 An example of getting device capability list**
+
+**Table I.2-28 – Get capability list**
+
+|                    |                                                                   |
+|--------------------|-------------------------------------------------------------------|
+| Request name       | GetCap                                                            |
+| Message type       | RPC                                                               |
+| Direction          | From platform to PU                                               |
+| Request content    | None                                                              |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error |
+| Response content   | None                                                              |
+
+### **I.2.29 An example of uploading device log**
+
+**Table I.2-29 – Upload log**
+
+|              |                     |
+|--------------|---------------------|
+| Request name | LogUploadAsync      |
+| Message type | RPC                 |
+| Direction    | From platform to PU |
+
+**Table I.2-29 – Upload log**
+
+|                    |                                                                                                                                                                                                                                                                                                                                                          |
+|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Request content    | {<br>"trans_id": <required, int: mark the task ID of this log upload><br>"start": <required, string; logging start time, format yyyy-MM-ddTHH:mm:ss><br>"end": <required, string; logging end time, format yyyy-MM-ddTHH:mm:ss><br>"url": <required, string, URL of log upload,the device upload the corresponding log file through the PUT method><br>} |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error                                                                                                                                                                                                                                                                                        |
+| Response content   | None                                                                                                                                                                                                                                                                                                                                                     |
+
+### **I.2.30 An example of uploading device log done**
+
+**Table I.2-30 – Upload log done**
+
+|                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Request name       | LogDone                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| Message type       | EVENT                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| Direction          | From PU to platform                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| Request content    | {<br>"mac_id": <required, string, the mac address of this device, test uniqueness><br>"trans_id": <required, string; mark the task ID of this log upload, consistent with LogUploadAsync><br>"status": <required, string enumeration; success/fail><br>"start": <required, string; logging end time, format yyyy-MM-ddTHH:mm:ss><br>"end": <required, string; logging end time, format yyyy-MM-ddTHH:mm:ss><br>"url": <required, string, url of log uploaded><br>"size": < required, int; the number of bytes of the uploaded log file><br>} |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| Response content   | None                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+#### **I.2.31 An example of getting disk information**
+
+**Table I.2-31 – Get disk information**
+
+|                    |                                                                   |
+|--------------------|-------------------------------------------------------------------|
+| Request name       | GetDiskInfo                                                       |
+| Message type       | RPC                                                               |
+| Direction          | From platform to PU                                               |
+| Request content    | None                                                              |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error |
+
+**Table I.2-31 – Get disk information**
+
+|                  |                                                                                                                                                                                                                                                                           |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Response content | {<br>"state": <required, int; the state of SD card, 0: normal, 1: no card inserted, 2:card exception, 3: formatting><br>"total": <required, int; total capability of the SD card, unit is MB><br>"free": <required, int; left capability of the SD card, unit is MB><br>} |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+### **I.2.32 An example of formatting disk**
+
+**Table I.2-32 – Format disk**
+
+|                    |                                                                   |
+|--------------------|-------------------------------------------------------------------|
+| Request name       | FormatDisk                                                        |
+| Message type       | RPC                                                               |
+| Direction          | From platform to PU                                               |
+| Request content    | None                                                              |
+| Return status code | 200: normal<br>400~499: user input error<br>500~599: server error |
+| Response content   | None                                                              |
+
+## **I.3 Messages of video service interface**
+
+### **I.3.1 An example of creating video segment**
+
+**Table I.3-1 – Create video segment**
+
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Protocol type        | HTTPS + JSON                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| Direction            | From PU to platform                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| Request method       | POST                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| Request URL          | "upload address" returned by the platform, e.g.,<br>https://<domain:port>/live/cseg/<channelID>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| Request message head | Content-Type: application/x-www-form-urlencoded                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| Request content      | {<br>"op": <string enumeration, required: create video segment are fixed as create><br>"content_type": <string, required><br>"size": <int,required: the size of the video segment, unit is byte><br>"start": <float,required: the start time of the segment recording, recording time from epoch to the start of the slice, unit is second><br>"duration": <float,required: the duration time of this segmentation, unit is second><br>"discontinue": <int, required: (0, 1)><br>"https": <int, required><br>}<br>The example string of the body:<br>op=create&content_type=video%2Fmp2t&size=32768&start=1574322174&duration=600&discontinue=0&https=0 |
+
+**Table I.3-1 – Create video segment**
+
+|                          |                                                                                                                                                                        |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Return status code       | 200: normal<br>400~499: user input error<br>500~599: server error                                                                                                      |
+| Response header          | Content-Type: application/json; charset=utf-8<br>Access-Control-Allow-Origin: *<br>Access-Control-Allow-Methods: POST                                                  |
+| Response message content | Normal response:<br>{<br>"name": <string, required><br>"url": <string, required><br>}<br>Abnormal response:<br>{<br>"info": <string, required: wrong description><br>} |
+
+### **I.3.2 An example of confirm video segment**
+
+**Table I.3-2 – Confirm video segment**
+
+|                          |                                                                                                                                      |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------|
+| Protocol type            | HTTPS + JSON                                                                                                                         |
+| Direction                | From PU to platform                                                                                                                  |
+| Request method           | POST                                                                                                                                 |
+| Request URL              | "upload address" returned by the platform, e.g.,<br>https://<domain:port>/live/cseg/<channelID>                                      |
+| Request message head     | Content-Type: application/x-www-form-urlencoded                                                                                      |
+| Request content          | {<br>"op": <string enumeration, required><br>"name": <string, required><br>}<br>The example of the body string: op=save&name=0003.ts |
+| Return status code       | 200: normal<br>400~499: user input error<br>500~599: server error                                                                    |
+| Response header          | Content-Type: application/json; charset=utf-8<br>Access-Control-Allow-Origin: *<br>Access-Control-Allow-Methods: POST                |
+| Response message content | Normal response:<br>None<br>Abnormal response:<br>{<br>"info": <string, required: wrong description><br>}                            |
+
+### I.3.3 An example of cancelling a video segment
+
+**Table I.3-3 – Cancel video segment**
+
+|                          |                                                                                                                                                                              |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Protocol type            | HTTPS + JSON                                                                                                                                                                 |
+| Direction                | From PU to platform                                                                                                                                                          |
+| Request method           | POST                                                                                                                                                                         |
+| Request URL              | "upload address" returned by the platform, e.g.,<br>https://<domain:port>/live/cseg/<channelID>                                                                              |
+| Request message head     | Content-Type: application/x-www-form-urlencoded                                                                                                                              |
+| Request content          | {<br>"op": <string enumeration, required: cancel video segment are fixed as fail><br>"name": <string, required><br>}<br>The example of the body string: op=fail&name=0003.ts |
+| Return status code       | 200: normal<br>400~499: user input error<br>500~599: server error                                                                                                            |
+| Response header          | Content-Type: application/json; charset=utf-8<br>Access-Control-Allow-Origin: *<br>Access-Control-Allow-Methods: POST                                                        |
+| Response message content | Normal response:<br>None<br>Abnormal response:<br>{<br>"info": <string, required: wrong description><br>}                                                                    |
+
+### I.3.4 An example of getting server information
+
+**Table I.3-4 – Get server information**
+
+|                      |                                                                                                                                                                                     |
+|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Protocol type        | HTTPS + JSON                                                                                                                                                                        |
+| Direction            | From PU to platform                                                                                                                                                                 |
+| Request method       | POST                                                                                                                                                                                |
+| Request URL          | "upload address" returned by the platform, e.g.,<br>https://<domain:port>/live/cseg/<channelID>                                                                                     |
+| Request message head | Content-Type: application/x-www-form-urlencoded                                                                                                                                     |
+| Request content      | {<br>"op": <string enumeration, required; operation type, getting the current calendar time is fixed as get current time><br>}<br>The example of the body string: op=getcurrenttime |
+| Return status code   | 200: normal<br>400~499: user input error<br>500~599: server error                                                                                                                   |
+
+**Table I.3-4 – Get server information**
+
+|                          |                                                                                                                                                                                                             |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Response header          | Content-Type: application/json; charset=utf-8<br>Access-Control-Allow-Origin: *<br>Access-Control-Allow-Methods: POST                                                                                       |
+| Response message content | Normal response:<br>{<br>"currenttime":<float, required: the number of seconds from epoch to current, unit is second><br>}<br>Abnormal response:<br>{<br>"info": <string, required: wrong description><br>} |
+
+### **I.3.5 An example of report statistical data**
+
+**Table I.3-5 – Report statistical data**
+
+|                          |                                                                                                                                                                                                              |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Protocol type            | HTTPS + JSON                                                                                                                                                                                                 |
+| Direction                | From PU to platform                                                                                                                                                                                          |
+| Request method           | POST                                                                                                                                                                                                         |
+| Request URL              | "upload address" returned by the platform, e.g.,<br>https://<domain:port>/live/cseg/<channelID>                                                                                                              |
+| Request message head     | Content-Type: application/x-www-form-urlencoded                                                                                                                                                              |
+| Request content          | {<br>"op": <string enumeration, required; operation type><br>"Dropped_nb": <int, optional><br>"Dropped_time": <float, optional><br>}<br>The example of the body string: op=stat&dropped_nb=3&dropped_time=30 |
+| Return status code       | 200: normal<br>400~499: user input error<br>500~599: server error                                                                                                                                            |
+| Response header          | Content-Type: application/json; charset=utf-8<br>Access-Control-Allow-Origin: *<br>Access-Control-Allow-Methods: POST                                                                                        |
+| Response message content | Normal response:<br>None<br>Abnormal response:<br>{<br>"info": <string, required: wrong description><br>}                                                                                                    |
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.3-202212-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/H/T-REC-H.627.3-202212-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477
--- /dev/null
+++ b/marked/H/T-REC-H.627.3-202212-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_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.627.3-202212-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg b/marked/H/T-REC-H.627.3-202212-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bc64a5220bd9b8bccdd75b38522c2f27db86142d
--- /dev/null
+++ b/marked/H/T-REC-H.627.3-202212-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c6469ec14f6658c81c82749cdbde5e30f5c12229b7d1e30ff31ea78a9a619b10
+size 18288
diff --git a/marked/H/T-REC-H.627.3-202212-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/H/T-REC-H.627.3-202212-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a48728e4a2502a11c35ce4f18e307b1b205c15cb
--- /dev/null
+++ b/marked/H/T-REC-H.627.3-202212-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e7a2edff84d88ff0e2799b71bc46053430f143b0f31d836c81eb024305e8d96b
+size 19100
diff --git a/marked/H/T-REC-H.627.3-202212-I_PDF-E/6f31cdb576d2f15c35c3f266e5f59211_img.jpg b/marked/H/T-REC-H.627.3-202212-I_PDF-E/6f31cdb576d2f15c35c3f266e5f59211_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9abb0ac71f8e0fd561e168eefc715a7f5009a444
--- /dev/null
+++ b/marked/H/T-REC-H.627.3-202212-I_PDF-E/6f31cdb576d2f15c35c3f266e5f59211_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c271dea8dada544695148c4f2448a0505f1b66881aef259a5dfd4a8b64f1d62b
+size 17402
diff --git a/marked/H/T-REC-H.627.3-202212-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/H/T-REC-H.627.3-202212-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..00aa2383b285926643046197555e2004aca4d31b
--- /dev/null
+++ b/marked/H/T-REC-H.627.3-202212-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f71ba8e09f0ee4b0f05bce5edf1f851e9f3df11fa17727658f16c34e29b467be
+size 30260
diff --git a/marked/H/T-REC-H.627.3-202212-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/marked/H/T-REC-H.627.3-202212-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..15bb4251235da117c78698df670e66c1031b9cb8
--- /dev/null
+++ b/marked/H/T-REC-H.627.3-202212-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c8b9bdaebadde6bfbb1aaa838c05283138e3a33cd91cb454aaf2e7fae4e8a331
+size 68414
diff --git a/marked/H/T-REC-H.627.3-202212-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg b/marked/H/T-REC-H.627.3-202212-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..46627be8b765c90bef872c945f7a73f104f67466
--- /dev/null
+++ b/marked/H/T-REC-H.627.3-202212-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:635906b4d7490d6826ec3bc2a471b0beea886dcd91539adf3e3695c7048351e6
+size 17845
diff --git a/marked/H/T-REC-H.627.3-202212-I_PDF-E/raw.md b/marked/H/T-REC-H.627.3-202212-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..8aae5cadb6a9bd4b756d2919f191567f70b2aa22
--- /dev/null
+++ b/marked/H/T-REC-H.627.3-202212-I_PDF-E/raw.md
@@ -0,0 +1,3843 @@
+
+
+# Recommendation **ITU-T H.627.3 (12/2022)**
+
+SERIES H: Audiovisual and multimedia systems
+
+Broadband, triple-play and advanced multimedia services –  
+Advanced multimedia services and applications
+
+## --- **Protocols for intelligent video surveillance 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                                                      |                    |
+| 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        |
+| <b>Advanced multimedia services and applications</b>                                        | <b>H.620–H.629</b> |
+| 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.627.3
+
+# Protocols for intelligent video surveillance systems
+
+## Summary
+
+Recommendation ITU-T H.627.3 defines protocols for intelligent video surveillance systems, including the functional architecture, functional interface, overall requirements of the protocol, message flows and relevant protocols. This Recommendation is based on Recommendation ITU-T H.626.5, *Architecture for intelligent video surveillance systems*.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T H.627.3  | 2022-12-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/15204">11.1002/1000/15204</a> |
+
+## Keywords
+
+Intelligent video surveillance, protocol.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                              | 3    |
+| 5 Conventions .....                                             | 3    |
+| 6 Introduction to functional architecture of an IVS system..... | 4    |
+| 7 Overall requirements.....                                     | 4    |
+| 7.1 Introduction of relevant protocol.....                      | 4    |
+| 7.2 Interface description.....                                  | 7    |
+| 8 Message flows and relevant protocols .....                    | 16   |
+| 8.1 Message flow .....                                          | 16   |
+| 8.2 Interface definition .....                                  | 19   |
+| Annex A – Data type and object JSON-Schema description .....    | 36   |
+| A.1 Data type .....                                             | 36   |
+| A.2 JSON-Schema description .....                               | 38   |
+| Bibliography .....                                              | 74   |
+
+
+
+# Recommendation ITU-T H.627.3
+
+## Protocols for intelligent video surveillance systems
+
+# 1 Scope
+
+This Recommendation defines protocols for intelligent video surveillance (IVS) systems, including the functional architecture, functional interface, overall requirements of the protocol, message flows and relevant protocols. The protocols of the video surveillance (VS) system refer to [ITU-T H.627].
+
+# 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.5] Recommendation ITU-T H.626.5 (V2) (2022), *Architecture for intelligent video surveillance system*.
+- [ITU-T H.627] Recommendation ITU-T H.627 (V2) (2020), *Signalling and protocols for a video surveillance system*.
+- [IETF RFC 2045] IETF RFC 2045 (1996), *Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies*.
+- [IETF RFC 2046] IETF RFC 2046 (1996), *Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types*.
+- [IETF RFC 3339] IETF RFC 3339 (2002), *Date and Time on the Internet: Timestamps*.
+- [IETF RFC 3986] IETF RFC 3986 (2005), *Uniform Resource Identifier (URI): Generic Syntax*.
+- [IETF RFC 7616] IETF RFC 7616 (2015), *HTTP Digest Access Authentication*.
+- [IETF RFC 9110] IETF RFC 9110 (2022), *HTTP Semantics*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+- 3.1.1 centre management unit (CMU)** [ITU-T H.626.5]: 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.1.2 client intelligent video (CIV)** [ITU-T H.626.5]: 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.1.3 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.4 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.5 intelligent customer unit (ICU)** [ITU-T H.626.5]: 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.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 management (IVM)** [ITU-T H.626.5]: 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.1.8 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.9 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.10 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.11 premises intelligent video (PIV)** [ITU-T H.626.5]: An intelligent identification module in the premises unit (PU). It identifies required information from input video and outputs the result.
+
+**3.1.12 service-control unit (SCU)** [ITU-T H.626.5]: 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.1.13 video and image information** [ITU-T H.626.5]: Video clips, images, related files and content description information.
+
+## **3.2 Terms defined in this Recommendation**
+
+None.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|       |                                                       |
+|-------|-------------------------------------------------------|
+| APE   | Acquisition and Processing Equipment                  |
+| API   | Application Programming Interface                     |
+| CCS   | Central Control Server                                |
+| CIV   | Client Intelligent Video                              |
+| CMU   | Centre Management Unit                                |
+| CU    | Customer Unit                                         |
+| DSS   | Data Storage and Service                              |
+| HTTP  | Hyper Text Transfer Protocol                          |
+| HTTPS | Hyper Text Transfer Protocol over Secure Socket Layer |
+| IAS   | Intelligent Application Service                       |
+| ICU   | Intelligent Customer Unit                             |
+| 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                                    |
+| PIV   | Premises Intelligent Video                            |
+| PU    | Premises Unit                                         |
+| REST  | Representation State Transfer                         |
+| SBI   | Searched By Image                                     |
+| SCU   | Service-Control Unit                                  |
+| URI   | Universal Resource Identifier                         |
+| URL   | Uniform Resource Locator                              |
+
+# 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.
+
+# 6 Introduction to functional architecture of an IVS system
+
+The functional architecture of an IVS system is illustrated in Figure 6-1. For the detailed entities and functions, see clause 6.2 of [ITU-T H.626.5].
+
+![Functional architecture of IVS system diagram](cfda9df1319e04207eb28bcefd1dab7b_img.jpg)
+
+The diagram illustrates the functional architecture of an IVS system, divided into two main parts by a vertical dashed line. On the left, outside the 'VS system' boundary, are three entities: DSS, IAS, and IVM. DSS is connected to IAS via 'Ad' (green arrow) and 'Ad'' (red arrow). DSS is also connected to IVM via 'Id' (green arrow) and 'Id'' (red arrow). IAS is connected to IVM via 'Ma' (green arrow) and 'Ma'' (red arrow). IVM is connected to IVU via 'Mu' (green arrow) and 'Mu'' (red arrow). IVU is connected to IPU via 'Pd' (green arrow) and 'Pd'' (red arrow). On the right, inside the 'VS system' boundary, are several components. IAS is connected to the 'CCS' block via 'Ac' (red arrow). The 'CCS' block contains 'CMU' and 'SCU'. 'CMU' is connected to 'SCU' via 'Cm' (red arrow). 'SCU' is connected to 'MSU' via 'Cs' (red arrow). The 'MS' block contains 'MDU' and 'MSU'. 'MDU' is connected to 'MSU' via 'Ds' (green arrow) and 'Ds'' (red arrow). 'MDU' is also connected to 'IPU' via 'Mp' (red arrow) and 'Mp'' (red arrow). 'IPU' (containing 'PIV') is connected to 'ICU' (containing 'CIV') via 'Pc' (black arrow). 'ICU' is connected to 'MDU' via 'Mc' (red arrow) and 'Mc'' (red arrow). 'IPU' is also connected to 'DSS' via 'Du' (red arrow). A legend at the bottom indicates: black arrow for 'Media', red arrow for 'Control', and green arrow for 'Video and image information'. The reference 'H.627.3(22)' is shown in the bottom right corner.
+
+Functional architecture of IVS system diagram
+
+Figure 6-1 – Functional architecture of IVS system
+
+# 7 Overall requirements
+
+## 7.1 Introduction of relevant protocol
+
+This Recommendation uses the representation state transfer (REST) style [b-REST] to design the application programming interface (API). The implementation of the protocol based on Hyper Text Transfer Protocol (HTTP) or Hyper Text Transfer Protocol over Secure Socket Layer (HTTPS).
+
+### 7.1.1 Protocol requirements
+
+##### 7.1.1.1 URI
+
+Universal resource identifier (URI) uses nouns to describe the provided resources. The definition is required to meet the requirements of section 4.2 of [IETF RFC 9110] and support Path Templating. Path Templating refers to the usage of curly brace({}) to mark a section of a uniform resource locator (URL) path as replaceable using path parameters.
+
+##### 7.1.1.2 Request header
+
+The request header field is required to be extended to add <User-Identify>. The field name User-Identify is used to carry the system ID of the requester to identify the requester's identity.
+
+##### 7.1.1.3 Request method
+
+Request method (section 9 of [IETF RFC 9110]) is used to describe operations performed on resources, the specific correspondence is as follows:
+
+- GET: Read resources, call cannot change the resource state, only return data to the requester without any side effects.
+- POST: Create a resource, it can only be used to add a resource that does not exist before.
+- PUT: Update resources, generally used to update existing resources, if the specified resource does not exist, it can also be created.
+
+d) DELETE: Delete resources.
+
+##### 7.1.1.4 Message body
+
+The encoding method of the message body adopts UTF-8. Under normal circumstances, the interface message body is required to be encapsulated in JavaScript object notation (JSON) format, and the Content-Type header field is required to be set to application/json. When carrying video clips or images, Base64 encodes the data into a string and stores it in JSON. The encoding method is required to meet the requirements of [IETF RFC 2045]; when transmitting large video clip data or image data is recommended to be encapsulated by multipart, and the encapsulation method is required to meet the requirements of section 5.1 of [IETF RFC 2046].
+
+##### 7.1.1.5 Status code
+
+Status code is used to describe the result of operations performed on resources, and its definition is required to meet the requirements of section 15 of [IETF RFC 9110].
+
+#### 7.1.2 Query requirements
+
+The query part of the URI is required to meet the requirements of section 3.4 of [IETF RFC 3986], and is required to support regular expressions.
+
+#### 7.1.2.1 Expansion requirements
+
+This Recommendation extends the query content:
+
+$$\text{query} = (\text{o.p1 OP v1})^* \& ( (\text{o.p2 OP v2}) \text{ OP2 } (\text{o.p3 OP v3}) )^*$$
+
+In the expression, o indicates the object to be queried, p indicates the property of the object, and \* indicates that the preceding () and the content inside appear 0 or more times. Operator OP is required to comply with Table 1, Table 2 and Table 3, OP2 takes the value of AND or OR. The parameters of the object attribute limit, sort field, number of records and other parameters of the result returned by the query is required to comply with the regulations in Table 4.
+
+**Table 1 – Arithmetic operators**
+
+| Operator | Meaning                                               |
+|----------|-------------------------------------------------------|
+| +        | addition                                              |
+| -        | subtraction                                           |
+| *        | multiplication                                        |
+| /        | division                                              |
+| %        | Returns the integer remainder of a division operation |
+
+**Table 2 – Logical operators**
+
+| Operator | Meaning                                                  |
+|----------|----------------------------------------------------------|
+| AND      | If both Boolean expressions are TRUE, then TRUE          |
+| OR       | If one of the two Boolean expressions is TRUE, then TRUE |
+
+**Table 3 – Comparison operators**
+
+| <b>Operator</b> | <b>Meaning</b>        |
+|-----------------|-----------------------|
+| =               | equal                 |
+| >               | more than             |
+| <               | Less than             |
+| >=              | greater or equal to   |
+| <=              | Less than or equal to |
+| <>              | not equal to          |
+| !=              | not equal to          |
+| !<              | not less than         |
+| !>              | not greater than      |
+
+**Table 4 – Conventions of variable names and meanings**
+
+| <b>Variable name</b> | <b>Meaning</b>                                         | <b>Description</b>                                                                  |
+|----------------------|--------------------------------------------------------|-------------------------------------------------------------------------------------|
+| Fields               | Used to specify the returned query property collection | Multiple properties are separated by ";"                                            |
+| Sort                 | Specify sort field                                     | "-" means descending order, otherwise ascending order, placed before the sort field |
+| PageRecordNum        | Specify the number of records per page                 |                                                                                     |
+| RecordStartNo        | Specify the start record number of the first page      |                                                                                     |
+| MaxNumRecordReturn   | Maximum number of records returned                     |                                                                                     |
+
+#### **7.1.2.2 Query example**
+
+- a) Search for person records with red or pink packages, and the returned results are sorted by the upper age limit, and only two attributes of PersonID and SourceID are returned.
+
+```
+GET /Persons?((Person.BagColor = Red) OR (Person.BagColor = Pink)) & (Sort = Person.AgeUpLimit) & (Fields = (Person.PersonID, Person.SourceID))
+```
+
+- b) Find person information, only query the first 200 records, 25 records per page, starting from the first record, sort by age upper limit, and return all attributes.
+
+```
+GET /Persons? (MaxNumRecordReturn = 200) & (PageRecordNum = 25) & (RecordStartNo = 1) & (Sort = Person.AgeUpLimit)
+```
+
+- c) Query ApeID contains 110109 ape information
+
+```
+GET /APes? (APE.ApeID like 110109)
+```
+
+### **7.1.3 Safety requirements**
+
+The two parties involved in the information exchange is required to conduct identity authentication. The authentication process is required to follow the digital digest authentication specified in [IETF RFC 7616] and is required to follow [IETF RFC 9110]. During digest authentication, the server random number nonce is required to be reset after it exceeds a limited period of time, and the limited period of time is recommended as 3600 s.
+
+## 7.2 Interface description
+
+### 7.2.1 Public interface
+
+- It is required to support registration, de-registration, keep-alive, and time calibration.
+- It is required to re-register after a random time within 300 s, when the registration fails.
+- It is required to support both registration parties configure the "heartbeat interval" parameter (the default heartbeat interval is 90 s).
+- It is required to support the registrant periodically send heartbeat messages to the registered party to keep the heartbeat alive according to the "heartbeat interval", after the successful registration.
+- It is required to support both registration parties configure the "Keep-alive timeout times" parameter uniformly (the default number of heartbeat timeouts is 3 times).
+
+Comparative table of registration, de-registration, keep-alive, and time calibration with interface message is shown in Table 5.
+
+**Table 5 – Comparative table of registration, de-registration, keep alive, time calibration with interface message**
+
+| No. | Interface name   | Description      | Interface message clause | Method |
+|-----|------------------|------------------|--------------------------|--------|
+| 1   | registration     | Registration     | 8.2.1                    | POST   |
+| 2   | de-registration  | De-registration  | 8.2.2                    | POST   |
+| 3   | keep_alive       | Keep alive       | 8.2.3                    | POST   |
+| 4   | time_calibration | Time calibration | 8.2.4                    | POST   |
+
+### 7.2.2 Interfaces of reference point Pd/Pd'
+
+- It is required to support registration, de-registration, keep\_alive, and time\_calibration functions from IPU to DSS. Interfaces as shown in Table 5.
+- It is required to support upload automatically acquisition video and image information from IPU to DSS. Interfaces as shown in Table 6.
+- It is required to support retransmission, when upload failed, after uploading the information.  
+NOTE 1 – Upload failed means that the response is not received within a certain time (e.g., 5 s).
+
+- It is required to support cache information, de-registration, and re-registration, when link problem happened. It is required to support transmission cache information after re-registration successful.
+
+NOTE 2 – Link problem means that unsuccessful retransmission multiple times (e.g., 3 times).
+
+**Table 6 – Comparative table of automatic video and image information uploading with interface message**
+
+| No. | Interface name                                      | Description                                      | Interface provider | Interface caller | Interface message clause | Method |
+|-----|-----------------------------------------------------|--------------------------------------------------|--------------------|------------------|--------------------------|--------|
+| 1   | batch_video_clips_create_and_query                  | Upload video clips automatically in batch.       | DSS                | IPU              | 8.2.6.1                  | POST   |
+| 2   | batch_image_create_and_query                        | Upload image in batch automatically.             | DSS                | IPU              | 8.2.7.1                  | POST   |
+| 3   | batch_motor_vehicles_Create_query_update_delete     | Upload motor vehicle in batch automatically.     | DSS                | IPU              | 8.2.8.1                  | POST   |
+| 4   | batch_non-motor_vehicles_create_query_update_delete | Upload non-motor vehicle in batch automatically. | DSS                | IPU              | 8.2.9.1                  | POST   |
+
+### 7.2.3 Interfaces of reference point Ma/Ma'
+
+- It is required to support registration, de-registration, keep\_alive, and time\_calibration functions from IVM to IAS. Interfaces as shown in Table 5.
+- It is required to support retrieving target by image and attribution between IAS and IVM. Interfaces as shown in Table 7.
+
+**Table 7 – Comparative table of target retrieving by image and attribution with interface message**
+
+| No. | Interface name                                          | Description                                                       | Interface provider | Interface caller | Interface message clause | Method       |
+|-----|---------------------------------------------------------|-------------------------------------------------------------------|--------------------|------------------|--------------------------|--------------|
+| 1   | synchronously_target_query_by_image                     | Create a task to target query by image (synchronization).         | IVM                | IAS              | 8.2.10.1                 | POST         |
+| 2   | asynchronously_create_and_delete_target_query_by_image  | Create and delete a task to target query by image (asynchronous). | IVM                | IAS              | 8.2.10.2                 | POST, DELETE |
+| 3   | create_and_delete_target_retrieval_by_image             | Upload a result of object to target query by image.               | IAS                | IVM              | 8.2.10.3                 | POST         |
+| 4   | batch_motor_vehicles_create_query_update_and_delete     | Query motor vehicle by attribution.                               | IVM                | IAS              | 8.2.8.1                  | GET          |
+| 5   | batch_non-motor_vehicles_create_query_update_and_delete | Query non-motor vehicle by attribution.                           | IVM                | IAS              | 8.2.9.1                  | GET          |
+
+- It is recommended to support analysis task controlling and analysis task status query between IAS and IVM. Interfaces as shown in Table 8.
+
+**Table 8 – Comparative table of analysis task control and status query with interface message**
+
+| No. | Interface name             | Description                            | Interface provider | Interface caller | Interface message clause | Method |
+|-----|----------------------------|----------------------------------------|--------------------|------------------|--------------------------|--------|
+| 1   | analysis_task_control      | Pause, resume, and stop analysis task. | IVM                | IAS              | 8.2.12                   | POST   |
+| 2   | analysis_task_status_query | Query analysis task status.            | IVM                | IAS              | 8.2.11                   | GET    |
+
+### **7.2.4 Interfaces of reference point Ad/Ad'**
+
+- It is required to support registration, de-registration, keep\_alive, and time\_calibration functions from IAS to DSS. Interfaces as shown in Table 5.
+- It is required to support queries based on feature attributes such as video and image information objects and their combinations, business operations and structural objects from IAS to DSS. Interfaces as shown in Table 9.
+
+**Table 9 – Comparative table of feature attributes and their combination query with interface message**
+
+| No. | Interface name                                                 | Description                              | Interface provider | Interface caller | Interface message clause | Method |
+|-----|----------------------------------------------------------------|------------------------------------------|--------------------|------------------|--------------------------|--------|
+| 1   | batch_video_clips_create_and_query                             | Query video clips in batch.              | DSS                | IAS              | 8.2.6.1                  | GET    |
+| 2   | a_single_video_clip_query_update_and_delete                    | Query a single video clip.               | DSS                | IAS              | 8.2.6.2                  | GET    |
+| 3   | a_single_video_clip_query_update_and_delete_object_information | Query object information of video clips. | DSS                | IAS              | 8.2.6.3                  | GET    |
+| 4   | batch_image_create_and_query                                   | Query images in batch.                   | DSS                | IAS              | 8.2.7.1                  | GET    |
+| 5   | a_single_image_query_update_and_delete                         | Query a single image.                    | DSS                | IAS              | 8.2.7.2                  | GET    |
+| 6   | a_single_image_query_update_and_delete_object_information      | Query image object information.          | DSS                | IAS              | 8.2.7.3                  | GET    |
+| 7   | batch_motor_vehicles_create_query_update_and_delete            | Query motor vehicles in batch.           | DSS                | IAS              | 8.2.8.1                  | GET    |
+| 8   | batch_motor_vehicle_create_query_update_delete                 | Query a single motor vehicle.            | DSS                | IAS              | 8.2.8.2                  | GET    |
+| 9   | batch_non-motor_vehicles_create_query_update_and_delete        | Query non-motor vehicles in batch.       | DSS                | IAS              | 8.2.9.1                  | GET    |
+| 10  | a_single_non-motor_vehicle_query_update_and_delete             | Query a single non-motor vehicle.        | DSS                | IAS              | 8.2.9.2                  | GET    |
+
+**Table 9 – Comparative table of feature attributes and their combination query with interface message**
+
+| No. | Interface name                                                        | Description                                        | Interface provider | Interface caller | Interface message clause | Method |
+|-----|-----------------------------------------------------------------------|----------------------------------------------------|--------------------|------------------|--------------------------|--------|
+| 11  | batch_video_image_event_create_and_query                              | Query video and image events in batch.             | DSS                | IAS              | 8.2.14.1                 | GET    |
+| 12  | a_single_video_image_event_query_update_and_delete                    | Query a single video and image event.              | DSS                | IAS              | 8.2.14.2                 | GET    |
+| 13  | a_single_video_image_event_query_update_and_delete_object_information | Query object information of video and image event. | DSS                | IAS              | 8.2.14.3                 | GET    |
+| 14  | batch_disposition_create_query_update_and_delete                      | Query disposition task.                            | DSS                | IAS              | 8.2.15.1                 | GET    |
+| 15  | disposition_notification                                              | Query disposition notification record.             | DSS                | IAS              | 8.2.16                   | GET    |
+| 16  | batch_subscription_create_query_update_and_delete                     | Query subscription task.                           | DSS                | IAS              | 8.2.17.1                 | GET    |
+| 17  | subscription_notification                                             | Query notification record.                         | DSS                | IAS              | 8.2.18                   | GET    |
+| 18  | create_and_delete_target_retrival_by_image                            | Query to retrieve the target result by image.      | DSS                | IAS              | 8.2.10.3                 | GET    |
+
+– It is required to support the manual acquisition of video and image events and the creation, update and deletion of video and image information objects from IAS to DSS. Interfaces as shown in Table 10.
+
+**Table 10 – Comparative table of manual acquisition of video and image information object with interface message**
+
+| No. | Interface name                                                        | Description                                                 | Interface provider | Interface caller | Interface message clause | Method      |
+|-----|-----------------------------------------------------------------------|-------------------------------------------------------------|--------------------|------------------|--------------------------|-------------|
+| 1   | batch_video_image_event_create_and_query                              | Create video and image events in batch.                     | DSS                | IAS              | 8.2.14.1                 | POST        |
+| 2   | a_single_video_image_event_query_update_and_delete                    | Update and delete a single video and image event.           | DSS                | IAS              | 8.2.14.2                 | PUT, DELETE |
+| 3   | a_single_video_image_event_query_update_and_delete_object_information | Update and delete video and image event object information. | DSS                | IAS              | 8.2.14.3                 | PUT, DELETE |
+| 4   | batch_video_clips_create_and_query                                    | Create manually acquisition video clips in batch.           | DSS                | IAS              | 8.2.6.1                  | POST        |
+
+**Table 10 – Comparative table of manual acquisition of video and image information object with interface message**
+
+| No. | Interface name                                                 | Description                                                                   | Interface provider | Interface caller | Interface message clause | Method            |
+|-----|----------------------------------------------------------------|-------------------------------------------------------------------------------|--------------------|------------------|--------------------------|-------------------|
+| 5   | a_single_video_clip_query_update_and_delete                    | Update and delete a single video clip acquisition manually.                   | DSS                | IAS              | 8.2.6.2                  | PUT, DELETE       |
+| 6   | A_single_video_clip_query_update_and_delete_object_information | Update and delete the object information of manually acquisition video clips. | DSS                | IAS              | 8.2.6.3                  | PUT, DELETE       |
+| 7   | batch_image_create_and_query                                   | Create manually acquisition images in batch.                                  | DSS                | IAS              | 8.2.7.1                  | POST              |
+| 8   | a_single_image_query_update_and_delete                         | Update and delete a single acquisition image manually.                        | DSS                | IAS              | 8.2.7.2                  | PUT, DELETE       |
+| 9   | a_single_image_query_update_and_delete_object_information      | Update and delete manually acquisition image object information.              | DSS                | IAS              | 8.2.7.3                  | PUT, DELETE       |
+| 10  | batch_motor_vehicles_create_query_update_and_delete            | Create, update and delete motor vehicles in batch.                            | DSS                | IAS              | 8.2.8.1                  | POST, PUT, DELETE |
+| 11  | batch_motor_vehicle_create_query_update_delete                 | Update and delete a single motor vehicle.                                     | DSS                | IAS              | 8.2.8.2                  | PUT, DELETE       |
+| 12  | batch_non-motor_vehicles_create_query_update_and_delete        | Create, update and delete non-motor vehicles in batch.                        | DSS                | IAS              | 8.2.9.1                  | POST, PUT, DELETE |
+| 13  | a_single_non-motor_vehicle_query_update_and_delete             | Update and delete a single non-motor vehicle                                  | DSS                | IAS              | 8.2.9.2                  | PUT, DELETE       |
+
+– It is required to support query and update IPU from IAS to DSS, and to query video tollgates, lanes and other information. Interfaces as shown in Table 11.
+
+**Table 11 – Comparative table of query and update the acquisition device/system with interface message**
+
+| No. | Interface name                      | Description                                    | Interface provider | Interface caller | Interface message clause | Method |
+|-----|-------------------------------------|------------------------------------------------|--------------------|------------------|--------------------------|--------|
+| 1   | acquisition_device_query_and_update | Query the acquisition device.                  | DSS                | IAS              | 8.2.5                    | GET    |
+| 2   | acquisition_device_query_and_update | Change the password of the acquisition device. | DSS                | IAS              | 8.2.5                    | PUT    |
+| 3   | video_tollgate_query                | Query the video tollgate.                      | DSS                | IAS              | 8.2.13.1                 | GET    |
+| 4   | lane_query                          | Query the lanes.                               | DSS                | IAS              | 8.2.13.2                 | GET    |
+
+– It is required to support the disposition and notification of video and image information objects and the retrieval of targets by image between IAS and DSS. Interfaces as shown in Table 12.
+
+**Table 12 – Comparative table of disposition and notification with interface message**
+
+| No. | Interface name                                         | Description                                                       | Interface provider | Interface caller | Interface message clause | Method       |
+|-----|--------------------------------------------------------|-------------------------------------------------------------------|--------------------|------------------|--------------------------|--------------|
+| 1   | batch_disposition_create_query_update_and_delete       | Disposition in batch.                                             | DSS                | IAS              | 8.2.15.1                 | POST         |
+| 2   | batch_disposition_create_query_update_and_delete       | Update and delete disposition tasks in batch.                     | DSS                | IAS              | 8.2.15.1                 | PUT, DELETE  |
+| 3   | withdraw_disposition                                   | Withdraw disposition.                                             | DSS                | IAS              | 8.2.15.2                 | PUT          |
+| 4   | disposition_notification                               | Notification.                                                     | IAS                | DSS              | 8.2.16                   | POST         |
+| 5   | disposition_notification                               | Delete notification record.                                       | IAS                | DSS              | 8.2.16                   | DELETE       |
+| 6   | synchronously_target_query_by_image                    | Create a task to target query by image (synchronization).         | DSS                | IAS              | 8.2.10.1                 | POST         |
+| 7   | asynchronously_create_and_delete_target_query_by_image | Create and delete a task to target query by image (asynchronous). | DSS                | IAS              | 8.2.10.2                 | POST, DELETE |
+| 8   | create_and_delete_target_retrieval_by_image            | Upload a result of object to target query by image.               | IAS                | DSS              | 8.2.10.3                 | POST         |
+
+– It is required to support subscriptions and notifications of video and image information objects, IPU directories, etc. between IAS and DSS. Interfaces as shown in Table 13.
+
+**Table 13 – Comparative table of subscription and notification with interface message**
+
+| No. | Interface name                                    | Description                                    | Interface provider | Interface caller | Interface message clause | Method      |
+|-----|---------------------------------------------------|------------------------------------------------|--------------------|------------------|--------------------------|-------------|
+| 1   | batch_subscription_create_query_update_and_delete | Subscription in batch.                         | DSS                | IAS              | 8.2.17.1                 | POST        |
+| 2   | batch_subscription_create_query_update_and_delete | Update and delete subscription tasks in batch. | DSS                | IAS              | 8.2.17.1                 | PUT, DELETE |
+| 3   | unsubscription                                    | Unsubscription.                                | DSS                | IAS              | 8.2.17.2                 | POST        |
+| 4   | subscription_notification                         | Notification.                                  | IAS                | DSS              | 8.2.18                   | POST        |
+| 5   | subscription_notification                         | Delete notification record.                    | IAS                | DSS              | 8.2.18                   | DELETE      |
+
+### **7.2.5 Interfaces of reference point Id/Id'**
+
+- It is required to support registration, de-registration, keep alive, and time calibration functions from IVM to DSS. Interfaces as shown in Table 5.
+- It is required to support upload automatically acquisition video and image information from IVM to DSS. Functions as shown in Table 14.
+- It is required to support retransmission, when upload failed, after uploading the information.  
+NOTE 1 – Upload failed means that the response is not received within a certain time (e.g., 5 s).
+- It is required to support cache information, de-registration, and re-registration, when link problem happened. It is required to support transmission cache information after re-registration successful.  
+NOTE 2 – Link problem means that unsuccessful retransmission multiple times (e.g., 3 times).
+
+**Table 14 – Comparative table of uploading the automatically acquisition video and image information with interface message**
+
+| No. | Interface name                                      | Description                                              | Interface provider | Interface caller | Interface message clause | Method |
+|-----|-----------------------------------------------------|----------------------------------------------------------|--------------------|------------------|--------------------------|--------|
+| 1   | batch_video_clips_create_and_query                  | Upload automatically acquisition video clips.            | DSS                | IVM              | 8.2.6.1                  | POST   |
+| 2   | batch_image_create_and_query                        | Upload automatically acquisition images.                 | DSS                | IVM              | 8.2.7.1                  | POST   |
+| 3   | batch_motor_vehicles_create_query_update_delete     | Upload automatically acquisition motor vehicles.         | DSS                | IVM              | 8.2.8.1                  | POST   |
+| 4   | batch_non-motor_vehicles_create_query_update_delete | Upload automatically acquisition non-motorized vehicles. | DSS                | IVM              | 8.2.9.1                  | POST   |
+
+- It is required to support queries based on feature attributes such as video and image information objects and their combinations from IVM to DSS. Interfaces as shown in Table 15.
+
+**Table 15 – Comparative table of feature attributes and their combination query with interface message**
+
+| No. | Interface name                                                        | Description                                        | Interface provider | Interface caller | Interface message clause | Method |
+|-----|-----------------------------------------------------------------------|----------------------------------------------------|--------------------|------------------|--------------------------|--------|
+| 1   | batch_video_clips_create_and_query                                    | Query video clips in batch.                        | DSS                | IVM              | 8.2.6.1                  | GET    |
+| 2   | a_single_video_clip_query_update_and_delete                           | Query a single video clip.                         | DSS                | IVM              | 8.2.6.2                  | GET    |
+| 3   | a_single_video_clip_query_update_and_delete_object_information        | Query object information of video clips.           | DSS                | IVM              | 8.2.6.3                  | GET    |
+| 4   | batch_image_create_and_query                                          | Query images in batch.                             | DSS                | IVM              | 8.2.7.1                  | GET    |
+| 5   | a_single_image_query_update_and_delete                                | Query a single image.                              | DSS                | IVM              | 8.2.7.2                  | GET    |
+| 6   | a_single_image_query_update_and_delete_object_information             | Query image object information.                    | DSS                | IVM              | 8.2.7.3                  | GET    |
+| 7   | batch_motor_vehicles_create_query_update_and_delete                   | Query motor vehicles in batch.                     | DSS                | IVM              | 8.2.8.1                  | GET    |
+| 8   | batch_motor_vehicle_create_query_update_delete                        | Query a single motor vehicle.                      | DSS                | IVM              | 8.2.8.2                  | GET    |
+| 9   | batch_non-motor_vehicles_create_query_update_and_delete               | Query non-motor vehicles in batch.                 | DSS                | IVM              | 8.2.9.1                  | GET    |
+| 10  | a_single_non-motor_vehicle_query_update_and_delete                    | Query a single non-motor vehicle.                  | DSS                | IVM              | 8.2.9.2                  | GET    |
+| 11  | batch_video_image_event_create_and_query                              | Query video and image events in batch.             | DSS                | IVM              | 8.2.14.1                 | GET    |
+| 12  | a_single_video_image_event_query_update_and_delete                    | Query a single video and image event.              | DSS                | IVM              | 8.2.14.2                 | GET    |
+| 13  | a_single_video_image_event_query_update_and_delete_object_information | Query object information of video and image event. | DSS                | IVM              | 8.2.14.3                 | GET    |
+| 14  | batch_disposition_create_query_update_and_delete                      | Query disposition task.                            | DSS                | IVM              | 8.2.15.1                 | GET    |
+| 15  | disposition_notification                                              | Query notification record.                         | DSS                | IVM              | 8.2.16                   | GET    |
+
+**Table 15 – Comparative table of feature attributes and their combination query with interface message**
+
+| No. | Interface name                                    | Description                                   | Interface provider | Interface caller | Interface message clause | Method |
+|-----|---------------------------------------------------|-----------------------------------------------|--------------------|------------------|--------------------------|--------|
+| 16  | batch_subscription_create_query_update_and_delete | Query subscription task.                      | DSS                | IVM              | 8.2.17.1                 | GET    |
+| 17  | subscription_notification                         | Query notification record.                    | DSS                | IVM              | 8.2.18                   | GET    |
+| 18  | create_and_delete_target_retrieval_by_image       | Query to retrieve the target result by image. | DSS                | IVM              | 8.2.10.3                 | GET    |
+
+– It is required to support the disposition and notification of video and image information objects and the retrieval of targets by image between IVM and DSS. Interfaces as shown in Table 16.
+
+**Table 16 – Comparative table of disposition and notification with interface message**
+
+| No. | Interface name                                        | Description                                                      | Interface provider | Interface caller | Interface message clause | Method       |
+|-----|-------------------------------------------------------|------------------------------------------------------------------|--------------------|------------------|--------------------------|--------------|
+| 1   | batch_disposition_create_query_update_and_delete      | Disposition in batch.                                            | IVM                | DSS              | 8.2.15.1                 | POST         |
+| 2   | batch_disposition_create_query_update_and_delete      | Update and delete disposition tasks in batch.                    | IVM                | DSS              | 8.2.15.1                 | PUT, DELETE  |
+| 3   | withdraw_disposition                                  | Withdraw disposition.                                            | IVM                | DSS              | 8.2.15.2                 | PUT          |
+| 4   | disposition_notification                              | Notification.                                                    | DSS                | IVM              | 8.2.16                   | POST         |
+| 5   | disposition_notification                              | Delete notification record.                                      | DSS                | IVM              | 8.2.16                   | DELETE       |
+| 6   | synchronously_target_query_by_image                   | Create synchronization for image retrieval target task.          | IVM                | DSS              | 8.2.10.1                 | POST         |
+| 7   | synchronously_create_and_delete_target_query_by_image | Create and delete asynchronous target tasks for image retrieval. | IVM                | DSS              | 8.2.10.2                 | POST, DELETE |
+| 8   | create_and_delete_target_retrieval_by_image           | Upload the target results for image retrieval.                   | DSS                | IVM              | 8.2.10.3                 | POST         |
+
+– It is required to support subscriptions and notifications of video and image information objects, acquisition device / system directories, etc. between IVM and DSS. Interfaces as shown in Table 17.
+
+**Table 17 – Comparative table of subscription and notification with interface message**
+
+| No. | Interface name                                    | Description                                    | Interface provider | Interface caller | Interface message clause | Method      |
+|-----|---------------------------------------------------|------------------------------------------------|--------------------|------------------|--------------------------|-------------|
+| 1   | batch_subscription_create_query_update_and_delete | Subscription in batch.                         | DSS                | IVM              | 8.2.17.1                 | POST        |
+| 2   | batch_subscription_create_query_update_and_delete | Update and delete subscription tasks in batch. | DSS                | IVM              | 8.2.17.1                 | PUT, DELETE |
+| 3   | unsubscription                                    | Unsubscription.                                | DSS                | IVM              | 8.2.17.2                 | POST        |
+| 4   | subscription_notification                         | Notification.                                  | IVM                | DSS              | 8.2.18                   | POST        |
+| 5   | subscription_notification                         | Delete notification record.                    | IVM                | DSS              | 8.2.18                   | DELETE      |
+
+# 8 Message flows and relevant protocols
+
+## 8.1 Message flow
+
+### 8.1.1 Create resource message interaction process
+
+The interface caller creates the video and image information object for the interface provider. The interface caller sends an HTTP POST request to the interface provider according to the interface access form, and the interface provider returns a response of whether the creation is successful or not to the interface caller. The interactive process is shown in Figure 2.
+
+![Sequence diagram showing the creation flow between an Interface caller and an Interface provider. The caller sends a POST request to the provider, and the provider returns a response.](5793a44ffdadd039928e2f9fe6daae06_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Interface caller
+    participant Interface provider
+    Note right of Interface caller: H.627.3(22)
+    Interface caller->>Interface provider: 1: POST/uri
+    activate Interface provider
+    Interface provider-->>Interface caller: 2: 201/4XX/5XX
+    deactivate Interface provider
+  
+```
+
+Sequence diagram showing the creation flow between an Interface caller and an Interface provider. The caller sends a POST request to the provider, and the provider returns a response.
+
+**Figure 2 – Creation flow**
+
+The message process is described as follows:
+
+- 1) The interface caller sends an HTTP POST request to the interface provider for /uri corresponding resource creation.
+- 2) The interface provider returns a response to the interface caller regarding whether the creation is successful or not. Response code 201 is returned for success; Response code 4XX is returned for failure caused by the interface caller, and the message body carries the corresponding failure reason; Response code 5XX is returned for failure caused by the interface provider, and the message body carries the corresponding failure reason.
+
+### 8.1.2 Query resource message interaction process
+
+The interface caller can query the video and image information object, acquisition device and other information from the interface provider. The interface caller sends an HTTP GET request to the interface provider according to the interface access form, and the interface provider returns the reading result to the interface caller. The interactive process is shown in Figure 3.
+
+![Sequence diagram for Figure 3: Query flow. It shows an 'Interface caller' sending a '1: GET/uri' request to an 'Interface provider', which responds with '2: 200/204/4XX/5XX'.](d734a6ea1b381280f043fcf70391b6db_img.jpg)
+
+```
+sequenceDiagram
+    participant Interface caller
+    participant Interface provider
+    Note right of Interface provider: H.627.3(22)
+    Interface caller->>Interface provider: 1: GET/uri
+    activate Interface provider
+    Interface provider-->>Interface caller: 2: 200/204/4XX/5XX
+    deactivate Interface provider
+```
+
+Sequence diagram for Figure 3: Query flow. It shows an 'Interface caller' sending a '1: GET/uri' request to an 'Interface provider', which responds with '2: 200/204/4XX/5XX'.
+
+Figure 3 – Query flow
+
+The message process is described as follows:
+
+- 1) The interface caller sends an HTTP GET request to the interface provider for /uri corresponding resources. If pagination is required, specify it in the query condition.
+- 2) The interface provider processes the combined query condition and returns the results that meet the conditions. Successfully processed and found a qualified result, response code 200 is returned, and the message body carries the result; the successful processing and no qualified result is found, response code 204 is returned, and the message body is empty; the failure caused by the interface caller returns response code 4XX, and the message body carries the corresponding failure reason; the failure caused by the interface provider returns response code 5XX, and the message body carries the corresponding failure reason.
+
+### 8.1.3 Update resource message interaction process
+
+The interface caller updates the video and image information object, disposition and announcement object, subscription and notification object, etc. to the interface provider; the interface caller sends an HTTP PUT request to the interface provider according to the interface access form, and the interface provider returns the update result to the interface caller. The interactive process is shown in Figure 4.
+
+![Sequence diagram for Figure 4: Update flow. It shows an 'Interface caller' sending a '1: PUT/uri' request to an 'Interface provider', which responds with '2: 200/4XX/5XX'.](6f31cdb576d2f15c35c3f266e5f59211_img.jpg)
+
+```
+sequenceDiagram
+    participant Interface caller
+    participant Interface provider
+    Note right of Interface provider: H.627.3(22)
+    Interface caller->>Interface provider: 1: PUT/uri
+    activate Interface provider
+    Interface provider-->>Interface caller: 2: 200/4XX/5XX
+    deactivate Interface provider
+```
+
+Sequence diagram for Figure 4: Update flow. It shows an 'Interface caller' sending a '1: PUT/uri' request to an 'Interface provider', which responds with '2: 200/4XX/5XX'.
+
+Figure 4 – Update flow
+
+The message process is described as follows:
+
+- 1) The interface caller sends an HTTP PUT update request to the interface provider for /uri corresponding resources.
+- 2) The interface provider returns a response of whether the update is successful or not to the interface caller. Response code 200 is returned for success; Response code 4XX is returned for failures caused by the interface caller, and the message body carries the corresponding failure reason; Response code 5XX is returned for failures caused by the interface provider, and the message body carries the corresponding failure reason.
+
+### 8.1.4 Delete resource message interaction process
+
+The interface caller deletes the video and image information object, disposition and announcement object, the subscription and notification object, etc. to the interface provider. The interface caller sends an HTTP DELETE request to the interface provider according to the interface access form, and the interface provider returns the delete result to the interface caller. The interactive process is shown in Figure 5.
+
+![Sequence diagram showing the delete flow between an interface caller and an interface provider.](4b87467ad9642943235f48f7d4b59449_img.jpg)
+
+```
+sequenceDiagram
+    participant Interface caller
+    participant Interface provider
+    Note right of Interface provider: H.627.3(22)
+    Interface caller->>Interface provider: 1: DELETE/uri
+    activate Interface provider
+    Interface provider-->>Interface caller: 2: 200/4XX/5XX
+    deactivate Interface provider
+```
+
+The diagram illustrates the interaction between an 'Interface caller' and an 'Interface provider'. The 'Interface caller' sends a 'DELETE/uri' request (labeled '1: DELETE/uri') to the 'Interface provider'. The 'Interface provider' responds with a status code (labeled '2: 200/4XX/5XX'). The reference 'H.627.3(22)' is noted at the bottom right.
+
+Sequence diagram showing the delete flow between an interface caller and an interface provider.
+
+**Figure 5 – Delete flow**
+
+The message process is described as follows:
+
+- 1) The interface caller sends an HTTP DELETE to delete request to the interface provider for /uri corresponding resources, and the resource identifier to be deleted is specified in the query string.
+- 2) The interface provider returns a response of whether the deletion is successful or not to the interface caller. Response code 200 is returned for success; response code 4XX is returned for failures caused by the interface caller, and the message body carries the corresponding failure reason; response code 5XX is returned for failures caused by the interface provider, and the message body carries the corresponding failure reason.
+
+### 8.1.5 Asynchronous operation message interaction process
+
+The interface caller performs asynchronous operations such as disposition and announcement, subscription and notification, and image retrieval of the target to the interface provider. The interface caller sends an HTTP POST request to the interface provider according to the interface access form, and the interface provider asynchronously returns the result to the interface caller after a period of processing. The interactive process is shown in Figure 6.
+
+![Sequence diagram illustrating the asynchronous operation flow between an Interface caller and an Interface provider. The flow consists of four steps: 1) POST/uri from caller to provider, 2) 201/4XX/5XX response from provider to caller, 3) POST/uri2 from provider to caller, and 4) 201/4XX/5XX response from caller to provider. The diagram is labeled H.627.3(22) at the bottom right.](7133ccf78043568ca62ecbcd43628a4a_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Caller as Interface caller
+    participant Provider as Interface provider
+    Note left of Caller: 
+    Caller->>Provider: 1: POST/uri
+    activate Provider
+    Provider-->>Caller: 2: 201/4XX/5XX
+    deactivate Provider
+    Note right of Provider: 
+    Provider->>Caller: 3: POST/uri2
+    activate Caller
+    Caller-->>Provider: 4: 201/4XX/5XX
+    deactivate Caller
+  
+```
+
+H.627.3(22)
+
+Sequence diagram illustrating the asynchronous operation flow between an Interface caller and an Interface provider. The flow consists of four steps: 1) POST/uri from caller to provider, 2) 201/4XX/5XX response from provider to caller, 3) POST/uri2 from provider to caller, and 4) 201/4XX/5XX response from caller to provider. The diagram is labeled H.627.3(22) at the bottom right.
+
+**Figure 6 – Asynchronous operation flow**
+
+The message process is described as follows:
+
+- 1) The interface caller sends an HTTP POST request to the interface provider to perform asynchronous operations for /uri corresponding resources.
+- 2) The interface provider returns a response to the interface caller regarding whether the reception is successful or not. Response code 201 is returned for success; response code 4XX is returned for failure caused by the interface caller, and the message body carries the corresponding failure reason; Response code 5XX is returned for failure caused by the interface provider, and the message body carries the corresponding failure reason.
+- 3) The interface provider processes the asynchronous request and sends the processing result to /uri2 specified by the interface caller via HTTP POST.
+- 4) The interface caller returns a response to the interface provider regarding whether the reception is successful or not. Response code 201 is returned for success; response code 4XX is returned for failure caused by the interface caller, and the message body carries the corresponding failure reason; response code 5XX is returned for failure caused by the interface provider, and the message body carries the corresponding failure reason.
+
+## 8.2 Interface definition
+
+The interface definition description is shown in Table 18. Among them, the URI item describes the interface resource request URI; the function item comprehensively describes the functional behaviour; the method item lists the HTTP methods involved in the resource, including POST, GET, PUT, and DELETE; the query string item describes the key-value pair of the resource; the message body item describes the message body of the HTTP request; the returned result item describes the response message body of the HTTP request; use "<object tag>" to point the object that constitutes the message body and the returned result; the comment item gives a special description of the interface message. The interface message body and response results are described by the JSON Schema shown in Annex A.
+
+**Table 18 – Interface definition description**
+
+|                   |                     |                     |                      |
+|-------------------|---------------------|---------------------|----------------------|
+| <b>URI</b>        |                     |                     |                      |
+| <b>Function</b>   |                     |                     |                      |
+| <b>Method</b>     | <b>Query string</b> | <b>Message body</b> | <b>Return result</b> |
+| <b>POST</b>       |                     |                     |                      |
+| <b>GET</b>        |                     |                     |                      |
+| <b>PUT</b>        |                     |                     |                      |
+| <b>DELETE</b>     |                     |                     |                      |
+| <b>Annotation</b> |                     |                     |                      |
+
+### **8.2.1 Interface of registration**
+
+**Table 19 – Interface of registration**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                     |                      |
+|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------|
+| <b>URI</b>        | /Register                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                     |                      |
+| <b>Function</b>   | registration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                     |                      |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | <b>Message body</b> | <b>Return result</b> |
+| <b>POST</b>       | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | <Register>          | <ResponseStatus>     |
+| <b>Annotation</b> | 1) Json Schema description of Register is shown in clause A.2.1<br>/schema/components#/\$defs/register<br>2) Json Schema description of ResponseStatus is shown in clause A.2.1<br>/schema/components#/\$defs/responseStatus, and the Id of ResponseStatus is the DeviceID requested to register<br>3) The registration process is required to comply with the process specified in [IETF RFC 9110], in which Authentication Schema uses Digest (shown in [IETF RFC 7616] for details)<br>4) POST process is shown in clause 8.1.1 |                     |                      |
+
+### **8.2.2 Interface of de-registration**
+
+**Table 20 – Interface of de-registration**
+
+|                   |                                                                                                                                                                                                                                                                              |                     |                      |
+|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------|
+| <b>URI</b>        | /UnRegister                                                                                                                                                                                                                                                                  |                     |                      |
+| <b>Function</b>   | de-registration                                                                                                                                                                                                                                                              |                     |                      |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                          | <b>Message body</b> | <b>Return result</b> |
+| <b>POST</b>       | none                                                                                                                                                                                                                                                                         | <UnRegister>        | <ResponseStatus>     |
+| <b>Annotation</b> | 1) Json Schema description of UnRegister is shown in clause A.2.1<br>/schema/components#/\$defs/unRegister<br>2) Json Schema description of ResponseStatus is shown in clause A.2.1<br>/schema/components#/\$defs/responseStatus<br>3) POST process is shown in clause 8.1.1 |                     |                      |
+
+### 8.2.3 Interface of keep\_alive
+
+**Table 21 – Interface of keep\_alive**
+
+|                   |                                                                                                                                                                                                                                                                             |                     |                      |
+|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------|
+| <b>URI</b>        | /Keepalive                                                                                                                                                                                                                                                                  |                     |                      |
+| <b>Function</b>   | keep alive                                                                                                                                                                                                                                                                  |                     |                      |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                         | <b>Message body</b> | <b>Return result</b> |
+| <b>POST</b>       | none                                                                                                                                                                                                                                                                        | <Keepalive>         | <ResponseStatus>     |
+| <b>Annotation</b> | 1) Json Schema description of Keep alive is shown in clause A.2.1<br>/schema/components#/\$defs/keepalive<br>2) Json Schema description of ResponseStatus is shown in clause A.2.1<br>/schema/components#/\$defs/responseStatus<br>3) Message flow is shown in clause 8.1.1 |                     |                      |
+
+### 8.2.4 Interface of time\_calibration
+
+**Table 22 – Interface of time\_calibration**
+
+|                   |                                                                                                                                                        |                     |                      |
+|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------|
+| <b>URI</b>        | /Time                                                                                                                                                  |                     |                      |
+| <b>Function</b>   | time calibration                                                                                                                                       |                     |                      |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                    | <b>Message body</b> | <b>Return result</b> |
+| <b>GET</b>        | none                                                                                                                                                   | none                | <SystemTime>         |
+| <b>Annotation</b> | 1) Json Schema description of SystemTime is shown in clause A.2.1<br>/schema/components#/\$defs/systemTime<br>2) Message flow is shown in clause 8.1.2 |                     |                      |
+
+### 8.2.5 Interface of acquisition\_device\_query\_and\_update
+
+**Table 23 – Interface of acquisition\_device\_query\_and\_update**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                     |                               |
+|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|-------------------------------|
+| <b>URI</b>        | /APEs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                     |                               |
+| <b>Function</b>   | IPU query and update                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                     |                               |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | <b>Message body</b> | <b>Return result</b>          |
+| <b>GET</b>        | APE attribute key-value pairs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | none                | <APEList> or <ResponseStatus> |
+| <b>PUT</b>        | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | <APEList>           | <ResponseStatusList>          |
+| <b>Annotation</b> | 1) Definition of APE attributes is shown in clause A.2.2/schema/ape-list#/\$defs/ape/properties<br>2) Json Schema description of APEList is shown in clause A.2.2/schema/ape-list<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1<br>/schema/components#/\$defs/responseStatus<br>4) Json Schema description of ResponseStatusList is shown in clause A.2.1<br>/schema/components#/\$defs/responseStatusList<br>5) Query string requirements of the GET method is shown in clause 7.1.2. When the query string is empty, it means that there is no restriction<br>6) The PUT method is used to modify the password of the IPU to realize dynamic password management<br>7) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>8) GET process is shown in clause 8.1.2 and PUT process is shown in clause 8.1.3 |                     |                               |
+
+### 8.2.6 Interface of video clip
+
+##### 8.2.6.1 Interface of batch\_video\_clips\_create\_and\_query
+
+**Table 24 – Interface of batch\_video\_clips\_create\_and\_query**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                     |                                    |
+|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|------------------------------------|
+| <b>URI</b>        | /VideoSlices                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                     |                                    |
+| <b>Function</b>   | create and query the combined information of video clip objects and related semantic attribute objects.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                     |                                    |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | <b>Message body</b> | <b>Return result</b>               |
+| <b>POST</b>       | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | <VideoSliceList>    | <ResponseStatusList>               |
+| <b>GET</b>        | VideoSliceInfo attribute key-value pairs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | none                | <VideoSliceList>or<ResponseStatus> |
+| <b>Annotation</b> | 1) Definition of VideoSliceInfo attributes is shown in clause A.2.5/schema/video-slice-info-list#/\$defs/videoSliceInfo/properties<br>2) Json Schema description of VideoSliceList is shown in clause A.2.19/schema/video-slice-list<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1/schema/components#/\$defs/responseStatus<br>4) Json Schema description of ResponseStatusList is shown in clause A.2.1/schema/components#/\$defs/responseStatusList<br>5) Query string requirements of the GET method are shown in clause 7.1.2. When the query string is empty, it means that there is no restriction<br>6) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>7) POST process is shown in clause 8.1.1 and GET process is shown in clause 8.1.2 |                     |                                    |
+
+##### 8.2.6.2 Interface of a\_single\_video\_clip\_query\_update\_and\_delete
+
+**Table 25 – Interface of a\_single\_video\_clip\_query\_update\_and\_delete**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                     |                                |
+|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|--------------------------------|
+| <b>URI</b>        | /VideoSlices/{VideoID}                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                     |                                |
+| <b>Function</b>   | query, update and delete the combination information of a single video clip object and related semantic attribute objects.                                                                                                                                                                                                                                                                                                                                                    |                     |                                |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                           | <b>Message body</b> | <b>Return result</b>           |
+| <b>GET</b>        | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | none                | <VideoSlice>or<ResponseStatus> |
+| <b>PUT</b>        | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | <VideoSlice>        | <ResponseStatus>               |
+| <b>DELETE</b>     | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | none                | <ResponseStatus>               |
+| <b>Annotation</b> | 1) The {} uses in URI is shown in clause 7.1.1.1<br>2) Json Schema description of VideoSlice is shown in clause A.2.19/schema/video-slice-list#/\$defs/videoSlice<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1/schema/components#/\$defs/responseStatus<br>4) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>5) GET process is shown in clause 8.1.2 and DELETE process is shown in clause 8.1.4 |                     |                                |
+
+##### 8.2.6.3 Interface of a\_single\_video\_clip\_query\_update\_and\_delete\_object\_information
+
+**Table 26 – Interface of a\_single\_video\_clip\_query\_update\_and\_delete\_object\_information**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                     |                                    |
+|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|------------------------------------|
+| <b>URI</b>        | /VideoSlices/{VideoID}/Info                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                     |                                    |
+| <b>Function</b>   | query, update and delete object information of a single video clip.                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                     |                                    |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | <b>Message body</b> | <b>Return result</b>               |
+| <b>GET</b>        | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | none                | <VideoSliceInfo>or<ResponseStatus> |
+| <b>PUT</b>        | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | <VideoSliceInfo>    | <ResponseStatus>                   |
+| <b>DELETE</b>     | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | none                | <ResponseStatus>                   |
+| <b>Annotation</b> | 1) The {} uses in URI is shown in clause 7.1.1.1<br>2) Json Schema description of VideoSliceInfo is shown in clause A.2.5/schema/video-slice-info-list#\$defs/videoSliceInfo/properties<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1/schema/components#\$defs/responseStatus<br>4) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>5) GET process is shown in clause 8.1.2, PUT process is shown in 8.1.3, DELETE process is shown in clause 8.1.4 |                     |                                    |
+
+#### 8.2.7 Interface of image
+
+#### 8.2.7.1 Interface of batch\_image\_create\_and\_query
+
+**Table 27 – Interface of batch\_image\_create\_and\_query**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                     |                               |
+|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|-------------------------------|
+| <b>URI</b>        | /Images                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                     |                               |
+| <b>Function</b>   | create and query the combined information of image objects and related semantic attribute objects.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                     |                               |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | <b>Message body</b> | <b>Return result</b>          |
+| <b>POST</b>       | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | <ImageList>         | <ResponseStatusList>          |
+| <b>GET</b>        | ImageInfo attribute key-value pairs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | none                | <ImageList>or<ResponseStatus> |
+| <b>Annotation</b> | 1) Definition of ImageInfo attributes is shown in clause A.2.6/schema/image-info-list#\$defs/imageInfo/properties<br>2) Json Schema description of ImageList is shown in clause A.2.18/schema/image-list<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1/schema/components#\$defs/responseStatus<br>4) Json Schema description of ResponseStatusList is shown in clause A.2.1/schema/components#\$defs/responseStatusList<br>5) Query string requirements of the GET method are shown in clause 7.1.2. When the query string is empty, it means that there is no restriction<br>6) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>7) POST process is shown in clause 8.1.1 and GET process is shown in clause 8.1.2 |                     |                               |
+
+##### 8.2.7.2 Interface of a\_single\_image\_query\_update\_and\_delete
+
+**Table 28 – Interface of a\_single\_image\_query\_update\_and\_delete**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                     |                           |
+|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------------------------|
+| <b>URI</b>        | /Images/{ImageID}                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                     |                           |
+| <b>Function</b>   | query, update and delete the combination information of a single image object and related semantic attribute objects.                                                                                                                                                                                                                                                                                                                                                                             |                     |                           |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | <b>Message body</b> | <b>Return result</b>      |
+| <b>GET</b>        | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | none                | <Image>or<ResponseStatus> |
+| <b>PUT</b>        | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | <Image>             | <ResponseStatus>          |
+| <b>DELETE</b>     | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | none                | <ResponseStatus>          |
+| <b>Annotation</b> | 1) The {} uses in URI is shown in clause 7.1.1.1<br>2) Json Schema description of Image is shown in clause A.2.18/schema/image-list#/\$defs/image<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1 /schema/components#/\$defs/responseStatus<br>4) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>5) GET process is shown in clause 8.1.2, PUT process is shown in clause 8.1.3, DELETE process is shown in clause 8.1.4 |                     |                           |
+
+#### 8.2.7.3 Interface of a\_single\_image\_query\_update\_and\_delete\_object\_information
+
+**Table 29 – Interface of a\_single\_image\_query\_update\_and\_delete\_object\_information**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                     |                               |
+|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|-------------------------------|
+| <b>URI</b>        | /Images/{ImageID}/Info                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                     |                               |
+| <b>Function</b>   | query, update and delete object information of a single image.                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                     |                               |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | <b>Message body</b> | <b>Return result</b>          |
+| <b>GET</b>        | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | none                | <ImageInfo>or<ResponseStatus> |
+| <b>PUT</b>        | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | <ImageInfo>         | <ResponseStatus>              |
+| <b>DELETE</b>     | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | none                | <ResponseStatus>              |
+| <b>Annotation</b> | 1) The {} uses in URI is shown in clause 7.1.1.1<br>2) Json Schema description of ImageInfo is shown in clause A.2.6/schema/image-info-list#/\$defs/imageInfo/properties<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1 /schema/components#/\$defs/responseStatus<br>4) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>5) GET process is shown in clause 8.1.2, PUT process is shown in clause 8.1.3, DELETE process is shown in clause 8.1.4 |                     |                               |
+
+### 8.2.8 Interface of motor vehicle
+
+##### 8.2.8.1 Interface of batch\_motor\_vehicles\_create\_query\_update\_delete
+
+**Table 30 – Interface of batch\_motor\_vehicles\_create\_query\_update\_and\_delete**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                     |                                        |
+|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------------------------|
+| <b>URI</b>        | /MotorVehicles                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                     |                                        |
+| <b>Function</b>   | create, query, update, and delete motor vehicle object information, and support batch operations.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                     |                                        |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | <b>Message body</b> | <b>Return result</b>                   |
+| <b>POST</b>       | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | <MotorVehicleList>  | <ResponseStatusList>                   |
+| <b>GET</b>        | MotorVehicle attribute key-value pairs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | none                | <MotorVehicleList> or <ResponseStatus> |
+| <b>PUT</b>        | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | <MotorVehicleList>  | <ResponseStatusList>                   |
+| <b>DELETE</b>     | The key is IDList, and the value is the motor vehicle object identifier separated by ";"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | none                | <ResponseStatusList>                   |
+| <b>Annotation</b> | 1) Definition of MotorVehicle attributes is shown in clause A.2.7/schema/motor-vehicle-list#/\$defs/motorVehicle/properties<br>2) Json Schema description of MotorVehicleList is shown in clause A.2.7/schema/motor-vehicle-list<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1/schema/components#/\$defs/responseStatus<br>4) Json Schema description of ResponseStatusList is shown in clause A.2.1/schema/components#/\$defs/responseStatusList<br>5) Query string requirements of the GET method are shown in clause 7.1.2. When the query string is empty, it means that there is no restriction<br>6) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>7) POST process is shown in clause 8.1.1, GET process is shown in clause 8.1.2, PUT process is shown in clause 8.1.3, and DELETE process in clause 8.1.4 |                     |                                        |
+
+##### 8.2.8.2 Interface of a\_single\_motor\_vehicle\_query\_update\_and\_delete
+
+**Table 31 – Interface of a\_single\_motor\_vehicle\_query\_update\_and\_delete**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                     |                                    |
+|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|------------------------------------|
+| <b>URI</b>        | /MotorVehicles/{MotorVehicleID}                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                     |                                    |
+| <b>Function</b>   | query, update and delete object information of a single motor vehicle.                                                                                                                                                                                                                                                                                                                                                                                                                                                |                     |                                    |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | <b>Message body</b> | <b>Return result</b>               |
+| <b>GET</b>        | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | none                | <MotorVehicle> or <ResponseStatus> |
+| <b>PUT</b>        | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | <MotorVehicle>      | <ResponseStatus>                   |
+| <b>DELETE</b>     | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | none                | <ResponseStatus>                   |
+| <b>Annotation</b> | 1) The {} uses in URI is shown in clause 7.1.1.1<br>2) Json Schema description of MotorVehicle is shown in clause A.2.7/schema/motor-vehicle-list#/\$defs/motorVehicle<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1/schema/components#/\$defs/responseStatus<br>4) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>5) GET process is shown in clause 8.1.2, PUT process is shown in clause 8.1.3, DELETE process is shown in clause 8.1.4 |                     |                                    |
+
+### 8.2.9 Interface of non-motor vehicle
+
+##### 8.2.9.1 Interface of batch\_non-motor\_vehicles\_create\_query\_update\_delete
+
+**Table 32 – Interface of batch\_non-motor\_vehicles\_create\_query\_update\_and\_delete**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                       |                                           |
+|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------------------------------|
+| <b>URI</b>        | /NonMotorVehicles                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |                                           |
+| <b>Function</b>   | create, query, update, and delete non-motor vehicle object information, and support batch operations.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |                                           |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | <b>Message body</b>   | <b>Return result</b>                      |
+| <b>POST</b>       | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | <NonMotorVehicleList> | <ResponseStatusList>                      |
+| <b>GET</b>        | NonMotorVehicle attribute key-value pairs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | none                  | <NonMotorVehicleList> or <ResponseStatus> |
+| <b>PUT</b>        | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | <NonMotorVehicleList> | <ResponseStatusList>                      |
+| <b>DELETE</b>     | the key is IDList, and the value is the non-motor vehicle object identifier separated by ";"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | none                  | <ResponseStatusList>                      |
+| <b>Annotation</b> | 1) Definition of NonMotorVehicle attributes is shown in clause A.2.8 /schema/nonmotor-vehicle-list#/\$defs/nonMotorVehicle/properties<br>2) Json Schema description of NonMotorVehicleList is shown in clause A.2.8 /schema/nonmotor-vehicle-list<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1 /schema/components#/\$defs/responseStatus<br>4) Json Schema description of ResponseStatusList is shown in clause A.2.1 /schema/components#/\$defs/responseStatusList<br>5) Query string requirements of the GET method are shown in clause 7.1.2. When the query string is empty, it means that there is no restriction<br>6) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>7) POST process is shown in clause 8.1.1, GET process is shown in clause 8.1.2, PUT process is shown in clause 8.1.3, and DELETE process in clause 8.1.4 |                       |                                           |
+
+#### 8.2.9.2 Interface of a\_single\_non-motor\_vehicle\_query\_update\_and\_delete
+
+**Table 33 – Interface of a\_single\_non-motor\_vehicle\_query\_update\_and\_delete**
+
+|                   |                                                                                                                                                                                                                                                                               |                     |                                       |
+|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------------------------------------|
+| <b>URI</b>        | /NonMotorVehicles/{NonMotorVehicleID}                                                                                                                                                                                                                                         |                     |                                       |
+| <b>Function</b>   | query, update and delete object information of a single non-motor vehicle.                                                                                                                                                                                                    |                     |                                       |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                           | <b>Message body</b> | <b>Return result</b>                  |
+| <b>GET</b>        | none                                                                                                                                                                                                                                                                          | none                | <NonMotorVehicle> or <ResponseStatus> |
+| <b>PUT</b>        | none                                                                                                                                                                                                                                                                          | <NonMotorVehicle>   | <ResponseStatus>                      |
+| <b>DELETE</b>     | none                                                                                                                                                                                                                                                                          | none                | <ResponseStatus>                      |
+| <b>Annotation</b> | 1) The {} uses in URI is shown in clause 7.1.1.1<br>2) Json Schema description of Non-Motor Vehicle is shown in clause A.2.8 /schema/nonmotor-vehicle-list<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1 /schema/components#/\$defs/responseStatus |                     |                                       |
+
+**Table 33 – Interface of a\_single\_non-motor\_vehicle\_query\_update\_and\_delete**
+
+|  |                                                                                                                                                                                                                           |
+|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | 4) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>5) GET process is shown in clause 8.1.2, PUT process is shown in clause 8.1.3, DELETE process is shown in clause 8.1.4 |
+|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+### **8.2.10 Interface of target query by image**
+
+##### **8.2.10.1 Interface of synchronously\_target\_query\_by\_image**
+
+**Table 34 – Interface of synchronously\_target\_query\_by\_image**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                                    |
+|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------------------|
+| <b>URI</b>        | /ImageSearchedByImagesSync                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                                    |
+| <b>Function</b>   | query the target object by image synchronously. Realize the image query target for the video and image information objects such as a motor vehicle, etc., and synchronously return the image query target result.                                                                                                                                                                                                                                                                             |                        |                                    |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | <b>Message body</b>    | <b>Return result</b>               |
+| <b>POST</b>       | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | <ImageSearchedByImage> | <ImageResultSBI>or<ResponseStatus> |
+| <b>Annotation</b> | 1) Definition of ImageSearchedByImage attributes is shown in clause A.2.15<br>/schema/image-searched-by-image<br>2) Json Schema description of ResponseStatus is shown in clause A.2.1<br>/schema/components#/\$defs/responseStatus<br>3) Json Schema description of ImageResultSBI is shown in clause A.2.16<br>/schema/image-result-SBI-list<br>4) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>5) POST process is shown in clause 8.1.1 |                        |                                    |
+
+##### **8.2.10.2 Interface of asynchronously\_create\_and\_delete\_target\_query\_by\_image**
+
+**Table 35 – Interface of asynchronously\_create\_and\_delete\_target\_query\_by\_image**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                   |                        |                      |
+|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------------|
+| <b>URI</b>        | /ImageSearchedByImagesAsync                                                                                                                                                                                                                                                                                                                                       |                        |                      |
+| <b>Function</b>   | create and delete asynchronously query the target object by image. Realize the image retrieval target for the video and image information objects such as motor vehicle, etc., and asynchronously return the image retrieval target result.                                                                                                                       |                        |                      |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                               | <b>Message body</b>    | <b>Return result</b> |
+| <b>POST</b>       | none                                                                                                                                                                                                                                                                                                                                                              | <ImageSearchedByImage> | <ResponseStatus>     |
+| <b>DELETE</b>     | The key is IDList, and the value is the search ID separated by ";"                                                                                                                                                                                                                                                                                                | none                   | <ResponseStatusList> |
+| <b>Annotation</b> | 1) Definition of ImageSearchedByImage attributes is shown in clause A.2.15<br>/schema/image-searched-by-image<br>2) Json Schema description of ResponseStatus is shown in clause A.2.1<br>/schema/components#/\$defs/responseStatus<br>3) Json Schema description of ResponseStatusList is shown in clause A.2.1<br>/schema/components#/\$defs/responseStatusList |                        |                      |
+
+**Table 35 – Interface of asynchronously\_create\_and\_delete\_target\_query\_by\_image**
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <p>4) When the operation fails, a ResponseStatus is returned, explaining the reason for the failure.</p> <p>5) DELETE process is shown in clause 8.1.4</p> <p>6) The addition of the image retrieval target and the addition of the image retrieval target result are a pair of asynchronous operation interfaces. After the image retrieval target is issued through the POST method, when the target that meets the conditions appears, the retrieval result is synchronously uploaded through the POST method. The process is shown in clause 8.1.5.</p> |
+|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+#### 8.2.10.3 Interface of create\_and\_delete\_target\_retrieval\_by\_image
+
+**Table 36 – Interface of create\_and\_delete\_target\_retrieval\_by\_image**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                          |                                        |
+|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|----------------------------------------|
+| <b>URI</b>        | /ImageResultSBIs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                          |                                        |
+| <b>Function</b>   | create and query to retrieve the target results object by image, and support batch operation.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                          |                                        |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | <b>Message body</b>      | <b>Return result</b>                   |
+| <b>POST</b>       | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | <ImageResultSBILi<br>st> | <ResponseStatusList>                   |
+| <b>GET</b>        | ImageResultSBI attribute key-value pairs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | none                     | <ImageResultSBIList>or<ResponseStatus> |
+| <b>Annotation</b> | <p>1) Definition of ImageResultSBI attributes is shown in clause A.2.16/schema/image-result-SBI-list#/\$defs/imageResultSBIList/properties</p> <p>2) Json Schema description of ImageResultSBIList is shown in clause A.2.16/schema/image-result-SBI-list</p> <p>3) Json Schema description of ResponseStatus is shown in clause A.2.1/schema/components#/\$defs/responseStatus</p> <p>4) Json Schema description of ResponseStatusList is shown in clause A.2.1/schema/components#/\$defs/responseStatusList</p> <p>5) When the operation fails, a ResponseStatus is returned, explaining the reason for the failure.</p> <p>6) GET process is shown in clause 8.1.2</p> <p>7) The addition of the image retrieval target and the addition of the image retrieval target result are a pair of asynchronous operation interfaces. After the image retrieval target is issued through the POST method, when the target that meets the conditions appears, the retrieval result is synchronously uploaded through the POST method. The process is shown in clause 8.1.5.</p> |                          |                                        |
+
+### 8.2.11 Interface of analysis\_task\_status\_query
+
+**Table 37 – Interface of analysis\_task\_status\_query**
+
+|                   |                                                                                                                               |                     |                                    |
+|-------------------|-------------------------------------------------------------------------------------------------------------------------------|---------------------|------------------------------------|
+| <b>URI</b>        | /TaskStatus                                                                                                                   |                     |                                    |
+| <b>Function</b>   | query the status of the video image analysis task.                                                                            |                     |                                    |
+| <b>Method</b>     | <b>Query string</b>                                                                                                           | <b>Message body</b> | <b>Return result</b>               |
+| <b>GET</b>        | TaskStatus attribute key-value pairs                                                                                          | none                | <TaskStatusList>or<ResponseStatus> |
+| <b>Annotation</b> | <p>1) Definition of TaskStatus attributes is shown in clause A.2.20/schema/task-status-list#/\$defs/taskStatus/properties</p> |                     |                                    |
+
+**Table 37 – Interface of analysis\_task\_status\_query**
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | 2) Json Schema description of TaskStatusList is shown in clause A.2.20 /schema/task-status-list<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1 /schema/components#/\$defs/responseStatus<br>4) Query string requirements of the GET method are shown in clause 7.1.2. When the query string is empty, it means that there is no restriction<br>5) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>6) GET process is shown in clause 8.1.2 |
+|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+### **8.2.12 Interface of analysis\_task\_control**
+
+**Table 38 – Interface of analysis\_task\_control**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                   |                      |                      |
+|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------|
+| <b>URI</b>        | /AnalyzeTaskControl                                                                                                                                                                                                                                                                                                                                               |                      |                      |
+| <b>Function</b>   | create analysis task control objects to realize the start and stop control of each analysis task of the video image.                                                                                                                                                                                                                                              |                      |                      |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                               | <b>Message body</b>  | <b>Return result</b> |
+| <b>POST</b>       | none                                                                                                                                                                                                                                                                                                                                                              | <AnalyzeTaskControl> | <ResponseStatus>     |
+| <b>Annotation</b> | 1) Json Schema description of AnalyzeTaskControl is shown in clause A.2.21 /schema/task-control<br>2) Json Schema description of ResponseStatus is shown in clause A.2.1 /schema/components#/\$defs/responseStatus<br>3) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>4) POST process is shown in clause 8.1.1 |                      |                      |
+
+### **8.2.13 Interface of video tollgate and lane**
+
+##### **8.2.13.1 Interface of video\_tollgate\_query**
+
+**Table 39 – Interface of video\_tollgate\_query**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                     |                                  |
+|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------------------|
+| <b>URI</b>        | /Tollgates                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                     |                                  |
+| <b>Function</b>   | query video tollgate                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                     |                                  |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | <b>Message body</b> | <b>Return result</b>             |
+| <b>GET</b>        | Tollgate attribute key-value pairs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | none                | <TollgateList>or<ResponseStatus> |
+| <b>Annotation</b> | 1) Definition of Tollgate attributes is shown in clause A.2.3/schema/tollgate-list#/\$defs/tollgate/properties<br>2) Json Schema description of TollgateList is shown in clause A.2.3/schema/tollgate-list<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1 /schema/components#/\$defs/responseStatus<br>4) Query string requirements of the GET method are shown in clause 7.1.2. When the query string is empty, it means that there is no restriction<br>5) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>6) GET process is shown in clause 8.1.2 |                     |                                  |
+
+##### 8.2.13.2 Interface of lane\_query
+
+**Table 40 – Interface of lane\_query**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                     |                              |
+|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|------------------------------|
+| <b>URI</b>        | /Tollgates                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                     |                              |
+| <b>Function</b>   | query lane                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                     |                              |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | <b>Message body</b> | <b>Return result</b>         |
+| <b>GET</b>        | Lane attribute key-value pairs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | none                | <LaneList>or<ResponseStatus> |
+| <b>Annotation</b> | 1) Definition of Lane attributes is shown in clause A.2.4/schema/lane-list#/\$defs/lane/properties<br>2) Json Schema description of LaneList is shown in clause A.2.4/schema/lane-list<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1/schema/components#/\$defs/responseStatus<br>4) Query string requirements of the GET method are shown in clause 7.1.2. When the query string is empty, it means that there is no restriction<br>5) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>6) GET process is shown in clause 8.1.2 |                     |                              |
+
+### 8.2.14 Interface of video image event
+
+##### 8.2.14.1 Interface of batch\_video\_image\_event\_create\_and\_query
+
+**Table 41 – Interface of batch\_video\_image\_event\_create\_and\_query**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                     |                              |
+|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|------------------------------|
+| <b>URI</b>        | /Cases                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                     |                              |
+| <b>Function</b>   | create and query the combined information of video image event, support batch operation.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                     |                              |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | <b>Message body</b> | <b>Return result</b>         |
+| <b>POST</b>       | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | <CaseList>          | <ResponseStatusList>         |
+| <b>GET</b>        | CaseInfo attribute key-value pairs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | none                | <CaseList>or<ResponseStatus> |
+| <b>Annotation</b> | 1) Definition of CaseInfo attributes is shown in clause A.2.9/schema/case-info-list#/\$defs/caseInfo/properties<br>2) Json Schema description of CaseList is shown in clause A.2.17/schema/case-list<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1/schema/components#/\$defs/responseStatus<br>4) Json Schema description of ResponseStatusList is shown in clause A.2.1/schema/components#/\$defs/responseStatusList<br>5) Query string requirements of the GET method are shown in clause 7.1.2. When the query string is empty, it means that there is no restriction<br>6) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>7) POST process is shown in clause 8.1.1 and GET process is shown in clause 8.1.2 |                     |                              |
+
+##### 8.2.14.2 Interface of a\_single\_video\_image\_event\_query\_update\_and\_delete
+
+**Table 42 – Interface of a\_single\_video\_image\_event\_query\_update\_and\_delete**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                     |                          |
+|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|--------------------------|
+| <b>URI</b>        | /Cases/{CaseID}                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                     |                          |
+| <b>Function</b>   | query, update and delete combined information of a single video image event.                                                                                                                                                                                                                                                                                                                                                                                                                  |                     |                          |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | <b>Message body</b> | <b>Return result</b>     |
+| <b>GET</b>        | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | none                | <Case>or<ResponseStatus> |
+| <b>PUT</b>        | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | <Case>              | <ResponseStatus>         |
+| <b>DELETE</b>     | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | none                | <ResponseStatus>         |
+| <b>Annotation</b> | 1) The {} uses in URI is shown in clause 7.1.1.1<br>2) Json Schema description of Case is shown in clause A.2.17/schema/case-list#/\$defs/case<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1/schema/components#/\$defs/responseStatus<br>4) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>5) GET process is shown in clause 8.1.2, PUT process is shown in clause 8.1.3, DELETE process is shown in clause 8.1.4 |                     |                          |
+
+##### 8.2.14.3 Interface of a\_single\_video\_image\_event\_query\_update\_and\_delete\_object\_information
+
+**Table 43 – Interface of a\_single\_video\_image\_event\_query\_update\_and\_delete\_object\_information**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                     |                              |
+|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|------------------------------|
+| <b>URI</b>        | /Cases/{CaseID}/Info                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                     |                              |
+| <b>Function</b>   | query, update and delete description information of a single video image event.                                                                                                                                                                                                                                                                                                                                                                                                                                      |                     |                              |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | <b>Message body</b> | <b>Return result</b>         |
+| <b>GET</b>        | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | none                | <CaseInfo>or<ResponseStatus> |
+| <b>PUT</b>        | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | <CaseInfo>          | <ResponseStatus>             |
+| <b>DELETE</b>     | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | none                | <ResponseStatus>             |
+| <b>Annotation</b> | 1) The {} uses in URI is shown in clause 7.1.1.1<br>2) Json Schema description of CaseInfo is shown in clause A.2.9/schema/case-info-list#/\$defs/caseInfo/properties<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1/schema/components#/\$defs/responseStatus<br>4) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>5) GET process is shown in clause 8.1.2, PUT process is shown in clause 8.1.3, DELETE process is shown in clause 8.1.4 |                     |                              |
+
+### 8.2.15 Interface of disposition
+
+#### 8.2.15.1 Interface of batch\_disposition\_create\_query\_update\_and\_delete
+
+**Table 44 – Interface of batch\_disposition\_create\_query\_update\_and\_delete**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                     |                                     |
+|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|-------------------------------------|
+| <b>URI</b>        | /Dispositions                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                     |                                     |
+| <b>Function</b>   | create, query, update and delete disposition object information, support batch operations.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                     |                                     |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | <b>Message body</b> | <b>Return result</b>                |
+| <b>POST</b>       | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | <DispositionList>   | <ResponseStatusList>                |
+| <b>GET</b>        | Disposition attribute key-value pairs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | none                | <DispositionList>or<ResponseStatus> |
+| <b>PUT</b>        | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | <DispositionList>   | <ResponseStatusList>                |
+| <b>DELETE</b>     | the key is IDList, and the value is the non-motor vehicle object identifier separated by ","                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | none                | <ResponseStatusList>                |
+| <b>Annotation</b> | 1) Definition of Disposition attributes is shown in clause A.2.10/schema/disposition-list#/\$defs/disposition/properties<br>2) Json Schema description of DispositionList is shown in clause A.2.10/schema/disposition-list<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1/schema/components#/\$defs/responseStatus<br>4) Json Schema description of ResponseStatusList is shown in clause A.2.1/schema/components#/\$defs/responseStatusList<br>5) Query string requirements of the GET method are shown in clause 7.1.2. When the query string is empty, it means that there is no restriction<br>6) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>7) GET process is shown in clause 8.1.2, PUT process is shown in clause 8.1.3, and DELETE process in clause 8.1.4<br>8) Disposition and notification is a pair of asynchronous operation interface, after the disposition is released through the POST method, when the qualified target appears, the notification is uploaded asynchronously through the POST method, and its process is shown in clause 8.1.5 |                     |                                     |
+
+##### 8.2.15.2 Interface of withdraw\_disposition
+
+**Table 45 – Interface of withdraw\_disposition**
+
+|                   |                                                                                                                                                                                                                                                                                       |                     |                      |
+|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------|
+| <b>URI</b>        | /Dispositions/{DispositionID}                                                                                                                                                                                                                                                         |                     |                      |
+| <b>Function</b>   | update the disposition task to achieve withdraw                                                                                                                                                                                                                                       |                     |                      |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                   | <b>Message body</b> | <b>Return result</b> |
+| <b>PUT</b>        | none                                                                                                                                                                                                                                                                                  | <Disposition>       | <ResponseStatus>     |
+| <b>Annotation</b> | 1) The {} uses in URI is shown in clause 7.1.1.1<br>2) Json Schema description of Disposition is shown in clause A.2.10/schema/disposition-list#/\$defs/disposition<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1/schema/components#/\$defs/responseStatus |                     |                      |
+
+**Table 45 – Interface of withdraw\_disposition**
+
+|  |                                                                                                                                                                                                                                                    |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | 4) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>5) Update the Disposition status to "withdraw" through PUT method to achieve the withdrawal function, and its process is shown in clause 8.1.3. |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+### 8.2.16 Interface of disposition\_notification
+
+**Table 46 – Interface of disposition\_notification**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                               |                                                   |
+|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|---------------------------------------------------|
+| <b>URI</b>        | /DispositionNotifications                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                               |                                                   |
+| <b>Function</b>   | create, query and delete disposition notification object, support batch operations.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                               |                                                   |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | <b>Message body</b>           | <b>Return result</b>                              |
+| <b>POST</b>       | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | <DispositionNotificationList> | <ResponseStatusList>                              |
+| <b>GET</b>        | DispositionNotificationList attribute key-value pairs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | none                          | <DispositionNotificationList> or <ResponseStatus> |
+| <b>DELETE</b>     | the key is IDList, and the value is the non-motor vehicle object identifier separated by ","                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | none                          | <ResponseStatusList>                              |
+| <b>Annotation</b> | 1) Definition of DispositionNotificationList attributes is shown in clause A.2.11<br>/schema/disposition-notification-list#/\$defs/dispositionNotification/properties<br>2) Json Schema description of DispositionNotificationList is shown in clause A.2.11<br>/schema/disposition-notification-list<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1<br>/schema/components#/\$defs/responseStatus<br>4) Json Schema description of ResponseStatusList is shown in clause A.2.1<br>/schema/components#/\$defs/responseStatusList<br>5) Query string requirements of the GET method are shown in clause 7.1.2. When the query string is empty, it means that there is no restriction<br>6) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>7) GET process is shown in clause 8.1.2, and DELETE process in clause 8.1.4<br>8) Disposition and notification is a pair of asynchronous operation interface, after the disposition is released through the POST method, when the qualified target appears, the notification is uploaded asynchronously through the POST method, and its process is shown in clause 8.1.5 |                               |                                                   |
+
+### 8.2.17 Interface of subscription
+
+#### 8.2.17.1 Interface of batch\_subscription\_create\_query\_update\_and\_delete
+
+**Table 47 – Interface of batch\_subscription\_create\_query\_update\_and\_delete**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                     |                                   |
+|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|-----------------------------------|
+| <b>URI</b>        | /Subscribes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                     |                                   |
+| <b>Function</b>   | implement subscriptions to video image information objects, etc, support batch operations.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                     |                                   |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | <b>Message body</b> | <b>Return result</b>              |
+| <b>POST</b>       | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | <SubscribeList>     | <ResponseStatusList>              |
+| <b>GET</b>        | Subscribe attribute key-value pairs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | none                | <SubscribeList>or<ResponseStatus> |
+| <b>PUT</b>        | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | <SubscribeList>     | <ResponseStatusList>              |
+| <b>DELETE</b>     | the key is IDList, and the value is the non-motor vehicle object identifier separated by ","                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | none                | <ResponseStatusList>              |
+| <b>Annotation</b> | 1) Definition of Subscribe attributes is shown in clause A.2.12/schema/subscribe-list#/\$defs/subscribe/properties<br>2) Json Schema description of SubscribeList is shown in clause A.2.12/schema/subscribe-list<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1/schema/components#/\$defs/responseStatus<br>4) Json Schema description of ResponseStatusList is shown in clause A.2.1/schema/components#/\$defs/responseStatusList<br>5) Query string requirements of the GET method are shown in clause 7.1.2. When the query string is empty, it means that there is no restriction<br>6) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>7) GET process is shown in clause 8.1.2, PUT process is shown in clause 8.1.3, and DELETE process in clause 8.1.4<br>8) Subscription and notification is a pair of asynchronous operation interface, after the subscription is released through the POST method, when the qualified target appears, the notification is uploaded asynchronously through the POST method, and its process is shown in clause 8.1.5 |                     |                                   |
+
+##### 8.2.17.2 Interface of unsubscription
+
+**Table 48 – Interface of unsubscription**
+
+|                   |                                                                                                                                                                                                                                                                                 |                     |                      |
+|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------|
+| <b>URI</b>        | /Subscribes/{SubscribeID}                                                                                                                                                                                                                                                       |                     |                      |
+| <b>Function</b>   | update the subscription task to achieve withdrawl                                                                                                                                                                                                                               |                     |                      |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                             | <b>Message body</b> | <b>Return result</b> |
+| <b>PUT</b>        | none                                                                                                                                                                                                                                                                            | <Subscribe>         | <ResponseStatus>     |
+| <b>Annotation</b> | 1) The {} uses in URI is shown in clause 7.1.1.1<br>2) Json Schema description of Subscribe is shown in clause A.2.12/schema/subscribe-list#/\$defs/subscribe<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1/schema/components#/\$defs/responseStatus |                     |                      |
+
+**Table 48 – Interface of unsubscription**
+
+|  |                                                                                                                                                                                                                                                            |
+|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | 4) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>5) Update the Subscribe status to "unsubscription" through PUT method to achieve the unsubscription function, and its process is shown in clause 8.1.3. |
+|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+#### **8.2.18 Interface of subscription notification**
+
+**Table 49 – Interface of subscription notification**
+
+|                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                             |                                                 |
+|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|-------------------------------------------------|
+| <b>URI</b>        | /SubscribeNotifications                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                             |                                                 |
+| <b>Function</b>   | create, query and delete subscription notification object, support batch operations.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                             |                                                 |
+| <b>Method</b>     | <b>Query string</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | <b>Message body</b>         | <b>Return result</b>                            |
+| <b>POST</b>       | none                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | <SubscribeNotificationList> | <ResponseStatusList>                            |
+| <b>GET</b>        | SubscribeNotificationList attribute key-value pairs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | none                        | <SubscribeNotificationList> or <ResponseStatus> |
+| <b>DELETE</b>     | the key is IDList, and the value is the non-motor vehicle object identifier separated by ","                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | none                        | <ResponseStatusList>                            |
+| <b>Annotation</b> | 1) Definition of SubscribeNotification attributes is shown in clause A.2.13<br>/schema/subscribe-notification-list#/\$defs/subscribeNotification/properties<br>2) Json Schema description of SubscribeNotificationList is shown in clause A.2.13<br>/schema/subscribe-notification-list<br>3) Json Schema description of ResponseStatus is shown in clause A.2.1<br>/schema/components#/\$defs/responseStatus<br>4) Json Schema description of ResponseStatusList is shown in clause A.2.1<br>/schema/components#/\$defs/responseStatusList<br>5) Query string requirements of the GET method are shown in clause 7.1.2. When the query string is empty, it means that there is no restriction<br>6) When the operation fails, a ResponseStatus is returned to explain the reason for the failure<br>7) GET process is shown in clause 8.1.2, and DELETE process in clause 8.1.4<br>8) Subscription and notification is a pair of asynchronous operation interface, after the subscription is released through the POST method, when the qualified target appears, the notification is uploaded asynchronously through the POST method, and its process is shown in clause 8.1.5 |                             |                                                 |
+
+# Annex A
+
+## Data type and object JSON-Schema description
+
+(This annex forms an integral part of this Recommendation.)
+
+This annex defines the data type and JSON-Schema description<sup>1</sup> of the interface object in clause 8. Clause A.1 defines the data type of object attribute. Clause A.2 defines JSON-Schema description comparative with tables in clause 8.2.
+
+## A.1 Data type
+
+This Recommendation uses JSON-Schema to describe the data objects passed between each unit. For more information about JSON-Schema, please refer to JSON Schema Core [b-JSON-1] and JSON Schema Validation [b-JSON-2] and Understanding JSON [b-JSON-3].
+
+Data types are based on the types supported by the draft-bhutton-schema-00 (<https://datatracker.ietf.org/doc/html/draft-bhutton-json-schema-00#section-4.2.1>). null is not supported as a type.
+
+In order to describe the data object more conveniently, this Recommendation expands the attribute of the format keyword. The expanded attribute is defined in Table A.1.
+
+**Table A.1 – Format attribute extension**
+
+| Format attribute | Type   | Comments                                                                                                                                                                                                  |
+|------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| integer          | number | signed 32 bit                                                                                                                                                                                             |
+| long             | number | signed 64 bit                                                                                                                                                                                             |
+| double           | number |                                                                                                                                                                                                           |
+| dateTime         | string | as defined in section 5.6 of [IETF RFC 3339]<br>dateTime = date-fullyear date-month date-mday time-hour<br>time-minute time-second                                                                        |
+| dateTimeMS       | string | as defined in section 5.6 of [IETF RFC 3339]<br>time-millisecond = 3 digits, range from 000 to 999<br>dateTime = date-fullyear date-month date-mday time-hour<br>time-minute time-second time-millisecond |
+| deviceIDType     | string | deviceIDType in accordance with [ITU-T H.626]<br>clause 7.1.4                                                                                                                                             |
+
+---
+
+<sup>1</sup> The Software Copyright Holder represents and warrants that to the best of its knowledge, it has the necessary copyright rights to waive all of the copyright rights as permissible under national law in the Software such that the Software can be used by implementers without further licensing concerns.
+
+No patent licence is granted, nor is a patent licensing commitment made, by implication, estoppel or otherwise.
+
+**Disclaimer:** Other than as expressly provided herein, (1) the Software is provided “AS IS” WITH NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS and (2) neither the Software Copyright Holder (or its affiliates) nor the ITU shall be held liable in any event for any damages whatsoever (including, without limitation, damages for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use of or inability to use the Software.”
+
+**Table A.1 – Format attribute extension**
+
+| Format attribute         | Type   | Comments                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|--------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| basicObjectTypeIdType    | string | <p>The basic information object type of the video image is composed of 45 digits, and the formula is as follows:<br/> basicObjectTypeIdType = deviceIDType subType dateTime serialNumber</p> <p>The deviceIDType and dateTime in the formula are defined in front of the table.</p> <p>subType= 01-videoslice<br/> 02-image<br/> 03-file<br/> 04-reserved<br/> 05-dataClassTab:motorVehicle<br/> 06-dataClassTab:nonMotorVehicle<br/> 99-other</p> <p>serialNumber= 5-digit serial number: It generally follows numerical order.<br/> Display sequentially from 00001</p> |
+| imageCntObjectTypeIdType | string | <p>The semantic attribute object type of video image information is composed of 52 digits, and the formula is as follows:<br/> imageCntObjectTypeIdType = basicObjectTypeIdType subType serialNumber</p> <p>The basicObjectTypeIdType in the formula is defined in front of the table.</p> <p>subType= 01-motorVehicle<br/> 02-nonMotorVehicle<br/> 99-other</p> <p>serialNumber= 5-digit serial number: It generally follows numerical order.<br/> Sequential representation starting from 00001.</p>                                                                    |
+| caseObjectTypeIdType     | string | <p>The time object identification coding type of video image information is composed of 34 digits<br/> caseObjectTypeIdType=countryCode zoneCode reservedCode dateTime serialNumber</p> <p>The dateTime in the formula is defined in front of the table.</p> <p>countryCode=4-digit country code<br/> zoneCode=8-digit zone code, it is recommended to use postal code or customized zone code.<br/> reservedCode=4-digit code, it is reserved for industry classification or other usage.<br/> serialNumber=4 digit serial number</p>                                    |
+| businessObjectTypeIdType | string | <p>The service operation identification type of video image information is composed of 37 digits<br/> businessObjectTypeIdType= countryCode zoneCode reservedCode subType dateTime serialNumber</p> <p>The dateTime in the formula is defined in front of the table.</p>                                                                                                                                                                                                                                                                                                  |
+
+**Table A.1 – Format attribute extension**
+
+| Format attribute | Type | Comments                                                                                                                                                                                                                                                                                                                                                                                           |
+|------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                  |      | countryCode=4-digit country code<br>zoneCode=8-digit zone code, it is recommended to use postal code or customized zone code.<br>reservedCode=4-digit code, it is reserved for industry classification or other usage.<br>subType=01-disposition<br>02-disposition notification<br>03-subscribe<br>04-subscribe notification<br>05-analysis task<br>99-other<br>serialNumber=4 digit serial number |
+
+## A.2 JSON-Schema description
+
+#### A.2.1 /schema/components
+
+```
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "http://www.itu.int/schema/components",
+  "description": " Common item definition ",
+  "$defs": {
+    "deviceID": {
+      "description": "Device ID, identifying the uniqueness of the
+device",
+      "type": "string",
+      "format": "deviceIDType"
+    },
+    "basicObjectID": {
+      "description": "Video image basic information object ID and data
+organization library, used to identify the uniqueness of videoSliceInfo,
+imageInfo, motorVehicle library, nonMotorVehicle library, etc.",
+      "type": "string",
+      "format": "basicObjectIDType"
+    },
+    "imageCntObjectID": {
+      "description": "Video image information semantic attribute object
+ID, used to identify the uniqueness of motorVehicle, nonMotorVehicle, etc.",
+      "type": "string",
+      "format": "imageCntObjectIDType"
+    },
+    "caseObjectID": {
+      "description": "Case object ID",
+      "type": "string",
+      "format": "caseObjectIDType"
+    },
+    "businessObjectID": {
+      "description": "Unified identification of business operation tasks,
+disposition/cancel disposition, announcements, subscriptions, notifications,
+analysis tasks, etc.",
+      "type": "string",
+      "format": "businessObjectIDType"
+    },
+    "hDirection": {
+      "description": "Horizontal direction. 1: west to east; 2: east to
+west; 3: north to south; 4: south to north; 5: southwest to northeast; 6:
+
+```
+
+```
+
+northeast to southwest; 7: northwest to southeast; 8: southeast to northwest; 9:
+Other directions",
+    "enum": [1, 2, 3, 4, 5, 6, 7, 8, 9]
+},
+"vDirection": {
+    "description": "Vertical direction. 1: From top to bottom; 2: From
+bottom to top; 3: Horizontal; 9: Other",
+    "enum": [1, 2, 3, 9]
+},
+"statusType": {
+    "description": "Device status, 1: online; 2: offline; 9: other",
+    "enum": ["1", "2", "9"]
+},
+"storagePath": {
+    "description": "Storage path",
+    "type": "string",
+    "format": "url",
+    "maxLength": 256
+},
+"urlPath": {
+    "description": "url address",
+    "type": "string",
+    "format": "uri",
+    "maxLength": 256
+},
+"flag": {
+    "description": "Judgmental flag. 0: false; 1: true",
+    "enum": [0, 1]
+},
+"wearedFlag": {
+    "description": "Weared flag. 0: false; 1: true; 2: not sure",
+    "enum": [0, 1, 2]
+},
+"securityLevel": {
+    "description": "Sensitivity level. 1: Sensitive; 2: Normal; 9:
+Other",
+    "enum": [1, 2, 9]
+},
+"binary": {
+    "description": "File Binary Content ",
+    "type": "string",
+    "contentMediaType": "application/octet-stream",
+    "contentEncoding": "binary"
+},
+"base64": {
+    "description": "File base64 encoding, the base64 encoding method
+adopts the method specified by rfc2046",
+    "type": "string",
+    "contentEncoding": "base64"
+},
+"infoKind": {
+    "description": "Information acquisition classification, 0: other;
+1: automatic acquired by acquisition device or analysis system; 2: manual
+acquisition and input through the application platform",
+    "enum": [0, 1, 2]
+},
+"imageCoordinates": {
+    "description": "The position of the smaller image in the larger
+image, starting from the upper left pixel of the larger image, moving
+horizontally to the right is the X-axis forward direction, and moving
+horizontally downward is the Y-axis forward direction, in pixels.",
+    "type": "integer"
+},
+"color": {
+
+```
+
+```
+
+        "description":"The video focuses on the target color. A: white; B:
+gray; C: yellow; D: pink; E: red; F: purple; G: green; H: blue; I: brown; J:
+black; K: orange; L: green; Y: colorless; Z: other",
+        "enum":["A", "B", "C", "D", "E", "F", "G", "H", "I", "J", "K", "L", "Y", "Z"]
+    },
+    "dataClassTab":{
+        "description":"Structure definition of data organization library",
+        "type":"object",
+        "properties" : {
+            "TabID":{
+                "description":"Library ID",
+                "$ref":"#/$defs/basicObjectId"
+            },
+            "TabName":{
+                "description":"Library name",
+                "type":"string"
+            },
+            "Description":{
+                "description":"Library Description",
+                "type":"string"
+            },
+            "IsAffirmed":{
+                "description":"Known identity. 0: Known identity; 1:
+Unknown identity",
+                "enum":[0,1]
+            },
+        },
+        "required":["TabID", "TabName"]
+    },
+    "dataClassTabList":{
+        "description":"Structure definition of data organization library
+list",
+        "type":"array",
+        "items":{
+            "$ref":"#/$defs/dataClassTab"
+        }
+    },
+    "responseStatus":{
+        "description":"Structure definition of response object",
+        "type":"object",
+        "properties" : {
+            "RequestURL":{
+                "description":"URL for corresponding operation",
+                "$ref":"#/$defs/urlPath"
+            },
+            "StatusCode":{
+                "description":"status code. 0:OK, normal. 1. Other
+errors. 4: invalid operation; 7: The JSON format is invalid. 8: Invalid JSON
+content",
+                "enum":[0,1,4,7,8]
+            },
+            "StatusString":{
+                "description":"Response description information",
+                "type":"string"
+            },
+            "Id":{
+                "description":"The POST method will return a new ID if
+it succeeds in creating a resource, but it will not return if it fails.",
+                "type":"string"
+            },
+            "LocalTime":{
+                "description":"Current time, used for occasions when
+time adjustment is needed",
+                "type":"string",
+            }
+        }
+    }
+}
+
+```
+
+```
+
+        "format":"dateTime"
+      }
+    },
+    "required":["RequestURL", "StatusCode", "StatusString"]
+  },
+  "responseStatusList":{
+    "description":"Structure definition of response object list",
+    "type":"array",
+    "items":{
+      "$ref":"#/$defs/responseStatus"
+    }
+  },
+  "register":{
+    "description":"Structure definition of registered object",
+    "type":"object",
+    "properties" : {
+      "DeviceID":{
+        "description":"Registration ID refers to apeID,
+        application platform ID, analysis system ID, etc.",
+        "$ref":"#/$defs/deviceID"
+      }
+    },
+    "required":["DeviceID"]
+  },
+  "unRegister":{
+    "description":"Structure definition of de-registration object",
+    "type":"object",
+    "properties" : {
+      "DeviceID":{
+        "description":"Logout ID refers to apeID, application
+        platform ID, analysis system ID, etc.",
+        "$ref":"#/$defs/deviceID"
+      }
+    },
+    "required":["DeviceID"]
+  },
+  "keepalive":{
+    "description":"Structure Definition of keep alive objects",
+    "type":"object",
+    "properties" : {
+      "DeviceID":{
+        "description":"Logout ID refers to apeID, application
+        platform ID, analysis system ID, etc.",
+        "$ref":"#/$defs/deviceID"
+      }
+    },
+    "required":["DeviceID"]
+  },
+  "systemTime":{
+    "description":"System time object",
+    "type":"object",
+    "properties" : {
+      "VIIDServerID":{
+        "description":"Server ID",
+        "$ref":"#/$defs/deviceID"
+      },
+      "TimeMode":{
+        "description":"Time calibration mode. 1: network; 2:
+        manual",
+        "enum":["1", "2"]
+      },
+      "LocalTime":{
+        "description":"Date time",
+        "type":"string",
+      }
+    }
+  }
+}
+
+```
+
+```
+
+        "format":"dateTime"
+      },
+      "TimeZone":{
+        "description":"Time zone",
+        "type":"string"
+      }
+    },
+    "required":["VIIDServerID","TimeMode","LocalTime","TimeZone"]
+  },
+  "featureExtTask":{
+    "description":"Feature vector extraction task object",
+    "type":"object",
+    "properties" : {
+      "ExtractID":{
+        "description":"Extract task ID",
+        "$ref":"#/$defs/businessObjectId"
+      },
+      "IsSaved":{
+        "description":"Save settings. 0: do not save; 1: save",
+        "enum":[0,1]
+      },
+      "MotorVehicleListObject":{
+        "description":"List of motor vehicle objects",
+        "$ref":"/schema/motor-vehicle-list"
+      },
+      "NonMotorVehicleListObject":{
+        "description":"List of Non-motor vehicle objects",
+        "$ref":"/schema/nonmotor-vehicle-list"
+      }
+    },
+    "required":["ExtractID","IsSaved"]
+  },
+  "featureExtTaskList":{
+    "description":"Feature vector extraction task list",
+    "type":"array",
+    "items":{
+      "$ref":"#/$defs/featureExtTask"
+    }
+  }
+}
+}
+}
+
+```
+
+#### A.2.2 /schema/ape-list
+
+```
+
+{
+  "$schema":"https://json-schema.org/draft/2020-12/schema",
+  "$id":"http://www.itu.int/schema/ape-list",
+  "description":"Structure definition of acquisition device list",
+
+  "type":"array",
+  "items":{
+    "$ref":"#/$defs/ape"
+  },
+  "$defs":{
+    "ape":{
+      "type":"object",
+      "description":"Acquisition device",
+      "properties" : {
+        "ApeID":{
+          "description":"Camera ID",
+          "$ref":"/schema/components#/$defs/deviceID"
+        },
+        "Name":{
+          "description":"Camera name",
+          "maxLength":100,
+
+```
+
+```
+
+        "type":"string"
+    },
+    "Model":{
+        "description":"Camera model",
+        "type":"string",
+        "maxLength":100
+    },
+    "IPAddr":{
+        "type":"string",
+        "format":"ipv4"
+    },
+    "IPV6Addr":{
+        "type":"string",
+        "format":"ipv6"
+    },
+    "Port":{
+        "type":"integer"
+    },
+    "Longitude":{
+        "description":"Earth latitude and longitude coordinates,
+accurate to 6 decimal places",
+        "type":"number",
+        "maximum":180,
+        "minimum":-180
+    },
+    "Latitude":{
+        "description":"Earth latitude and longitude coordinates,
+accurate to 6 decimal places",
+        "type":"number",
+        "maximum":90,
+        "minimum":-90
+    },
+    "PlaceCode":{
+        "description":"Region Code",
+        "type":"string"
+    },
+    "Place":{
+        "description":"Description of the specific installation
+location of the camera",
+        "type":"string"
+    },
+    "DepartCode":{
+        "description":"Department or industry code of the
+camera",
+        "type":"string"
+    },
+    "FuncType":{
+        "description":"Camera function type",
+        "type":"string"
+    },
+    "PositionType":{
+        "description":"Camera acquisition position type",
+        "type":"int"
+    },
+    "CapDirection":{
+        "description":"Vehicle capture direction, 0: rear of the
+car; 1: back rear of the car, compatible with non-video tollgate information
+equipment",
+        "enum":[0,1]
+    },
+    "MonitorDirection":{
+        "description":"Monitoring direction",
+        "$ref":"/schema/components#/$defs/hDirection"
+    },
+
+```
+
+```
+
+        "MonitorAreaDesc":{
+          "description":"Monitoring area description",
+          "type":"string"
+        },
+        "IsOnline":{
+          "$ref":"/schema/components#/$defs/statusType"
+        },
+        "OwnerApsID":{
+          "description":"ID of the owning acquisition system",
+          "deprecated":true,
+          "$ref":"/schema/components#/$defs/deviceID"
+        },
+        "UserId":{
+          "description":"User account, used to modify the login
+account of the acquisition device",
+          "type":"string"
+        },
+        "Password":{
+          "description":"Password, used to modify the login
+password of the acquisition device",
+          "type":"string",
+          "maxLength":32
+        }
+      },
+
+      "required":["ApeID", "Name", "Model", "IPAddr", "Port", "Longitude", "Latitude",
+"PlaceCode", "IsOnline"]
+    },
+    "apeStatus":{
+      "type":"object",
+      "description":"Acquisition device status object",
+      "properties" : {
+        "ApeID":{
+          "description":"Camera ID",
+          "$ref":"/schema/components#/$defs/deviceID"
+        },
+        "IsOnline":{
+          "$ref":"/schema/components#/$defs/statusType"
+        },
+        "CurrentTime":{
+          "description":"Current time",
+          "type":"string",
+          "format":"dateTime"
+        }
+      },
+      "required":["ApeID", "IsOnline", "CurrentTime"]
+    },
+    "apeStatusList":{
+      "description":"Acquisition device status list",
+      "type":"array",
+      "items":{
+        "$ref":"/$defs/apeStatus"
+      }
+    }
+  }
+}
+
+```
+
+#### A.2.3 /schema/tollgate-list
+
+```
+
+{
+  "$schema":"https://json-schema.org/draft/2020-12/schema",
+  "$id":"http://www.itu.int/schema/tollgate-list",
+  "description":"The structure definition of the tollgate list",
+
+  "type":"array",
+
+```
+
+```
+
+    "items":{
+      "$ref":"#/$defs/tollgate"
+    },
+    "$defs":{
+      "tollgate":{
+        "type":"object",
+        "description":"tollgate, equipped with points for video image
+information acquisition and identification device for moving vehicles,
+pedestrians, etc.",
+        "properties" : {
+          "TollgateID":{
+            "description":"Tollgate ID",
+            "$ref":"/schema/components#/$defs/deviceID"
+          },
+          "Name":{
+            "description":"Tollgate name",
+            "maxLength":100,
+            "type":"string"
+          },
+          "Longitude":{
+            "$ref":"/schema/ape-
+list#/$defs/ape/properties/Longitude"
+          },
+          "Latitude":{
+            "$ref":"/schema/ape-list#/$defs/ape/properties/Latitude"
+          },
+          "PlaceCode":{
+            "description":"Installation location area code",
+            "type":"string"
+          },
+          "Place":{
+            "description":"Description of the specific installation
+location of the tollgate",
+            "type":"string"
+          },
+          "Status":{
+            "description":"Tollgate status",
+            "$ref":"/schema/components#/$defs/statusType"
+          },
+          "TollgateUsage":{
+            "description":"Use of tollgate, 80: security tollgate;
+81: traffic tollgate; 82: other",
+            "enum":["80","81","82"]
+          },
+          "LaneNum":{
+            "description":"Number of tollgate lanes",
+            "type":"integer"
+          },
+          "ActiveTime":{
+            "description":"Tollgate activation time",
+            "type":"string",
+            "format":"dateTime"
+          }
+        }
+      }
+    }
+  }
+}
+
+```
+
+#### A.2.4 /schema/lane-list
+
+```
+
+{
+  "$schema":"https://json-schema.org/draft/2020-12/schema",
+
+```
+
+```
+
+    "$id": "http://www.itu.int/schema/lane-list",
+    "description": "Structure definition of lane list",
+
+    "type": "array",
+    "items": {
+      "$ref": "#/$defs/lane"
+    },
+    "$defs": {
+      "lane": {
+        "type": "object",
+        "description": "Tollgate, equipped with points for video image
+information acquisition and identification device for moving vehicles,
+pedestrians, etc.",
+        "properties" : {
+          "TollgateID": {
+            "$ref": "/schema/tollgate-
+list#/$defs/tollgate/properties/TollgateID"
+          },
+          "LaneNo": {
+            "description": "Lane number",
+            "type": "integer"
+          },
+          "Name": {
+            "description": "Lane name",
+            "maxLength": 100,
+            "type": "string"
+          },
+          "Direction": {
+            "description": "Lane direction",
+            "$ref": "/schema/components#/$defs/hDirection"
+          },
+          "Desc": {
+            "description": "Lane description",
+            "type": "string"
+          },
+          "MaxSpeed": {
+            "description": "Speed limit",
+            "type": "integer"
+          },
+          "CityPass": {
+            "description": "Code for the direction of entering and
+leaving the city, 1: enter the city; 2: out of the city; 3: mixed in and out of
+the city",
+            "enum": [1, 2, 3]
+          },
+          "ApeID": {
+            "$ref": "/schema/ape-list#/$defs/ape/properties/ApeID"
+          }
+        },
+        "required": ["TollgateID", "LaneNo", "Name", "Direction"]
+      }
+    }
+  }
+}
+
+```
+
+#### A.2.5 /schema/video-slice-info-list
+
+```
+
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "http://www.itu.int/schema/video-slice-info-list",
+  "description": "Structure definition of video slice list",
+
+  "type": "array",
+  "items": {
+    "$ref": "#/$defs/videoSliceInfo"
+  },
+
+```
+
+```
+
+"$defs":{
+  "videoSliceInfo":{
+    "type":"object",
+    "description":"Video slice object content definition",
+    "properties" : {
+      "VideoID":{
+        "description":"Tollgate ID",
+        "$ref":"/schema/components#/$defs/basicObjectId"
+      },
+      "InfoKind":{
+        "$ref":"/schema/components#/$defs/infoKind"
+      },
+      "VideoSourcePos":{
+        "description":"Video capture part, key public area part,
+A\\d{6}",
+        "type":"string",
+        "deprecated":true
+      },
+      "IsAbstractVideo":{
+        "description":"Abstract video flag, true: abstract
+video; false: original video",
+        "type":"boolean"
+      },
+      "EventSort":{
+        "description":"Video image content analysis event type.
+01: car passing; 02: cars tripping wires; 03: cars intruding; 04: cars
+wandering; 05: cars and objects disappear; 06: vehicles in violation of traffic
+regulations; 07: objects left behind; 08: cars are stranded; 99: Others",
+        "enum":["01","02","03","04","05","06","07","08","99"]
+      },
+      "DeviceID":{
+        "description":" Acquisition device code",
+        "$ref":"/schema/components#/$defs/deviceID"
+      },
+      "StoragePath":{
+        "description":"Storage path",
+        "$ref":"/schema/components#/$defs/storagePath"
+      },
+      "ThumbnailStoragePath":{
+        "description":"Thumbnail storage path",
+        "$ref":"/schema/components#/$defs/storagePath"
+      },
+      "FileHash":{
+        "description":"Video slice hash",
+        "type":"string",
+        "oneOf": [
+          { "maxLength":128, "minLength":128 },
+          { "maxLength":256, "minLength":256 }
+        ]
+      },
+      "FileFormat":{
+        "description":"Video format. Mpg:MPEG-1 MPG;M2ts:MPEG-2
+TS;Ps:MPEG-2 PS",
+        "enum":["Mpg","Mov","Avi","Rm","Rmvb","Flv","Vob","M2ts","Mp4","Es","Ps","Ts","W
+mv","Other"]
+      },
+      "VideoEncodeFormat":{
+        "description":"coding format. 01:AVC/H.264;02:MPEG-
+4;03:MPEG-2;04:MJPEG;05:H.263;06:HEVC/H.265; 99:Other",
+        "enum":["01","02","03","04","05","06","99"]
+      },
+      "AudioFlag":{
+        "description":"Audio flag",
+        "$ref":"/schema/components#/$defs/flag"
+      }
+    }
+  }
+}
+
+```
+
+```
+
+    },
+    "AudioEncodeFormat":{
+        "description":"Audio coding format.
+01:G.711a;02:G.711u;03:G.723;04:G.729;05:G.726;06:AAC ;99:other",
+        "enum":["01","02","03","04","05","06","99"]
+    },
+    "Title":{
+        "description":"Video title description",
+        "type":"string"
+    },
+    "TitleNote":{
+        "description":"Title supplements and remarks",
+        "type":"string"
+    },
+    "SpecialName":{
+        "description":"Name of the subject to which the video
+belongs",
+        "type":"string"
+    },
+    "Keyword":{
+        "description":"Words or phrases with retrieval
+significance that express the main content of video material",
+        "type":"string"
+    },
+    "ContentDescription":{
+        "description":"Brief description of video content.",
+        "type":"string"
+    },
+    "ShotPlaceCode":{
+        "description":"Shooting location area code",
+        "$ref":"/schema/ape-
+list#/$defs/ape/properties/PlaceCode"
+    },
+    "ShotPlaceFullAdress":{
+        "$ref":"/schema/ape-list#/$defs/ape/properties/Place"
+    },
+    "ShotPlaceLongitude":{
+        "$ref":"/schema/ape-
+list#/$defs/ape/properties/Longitude"
+    },
+    "ShoPlaceLatitude":{
+        "$ref":"/schema/ape-list#/$defs/ape/properties/Latitude"
+    },
+    "HorizontalShotDirection":{
+        "description":"Horizontal shooting direction",
+        "$ref":"/schema/components#/$defs/hDirection"
+    },
+    "VerticalShotDirection":{
+        "description":"Vertical shooting direction",
+        "$ref":"/schema/components#/$defs/vDirection"
+    },
+    "SecurityLevel":{
+        "$ref":"/schema/components#/$defs/securityLevel"
+    },
+    "VideoLen":{
+        "description":"Duration of video slice, in seconds.",
+        "type":"number",
+        "format":"long",
+        "minimum":1,
+        "maximum":99999999
+    },
+    "BeginTime":{
+        "description":"Video start time",
+        "type":"string",
+    }
+}
+
+```
+
+```
+
+        "format":"dateTime"
+    },
+    "EndTime":{
+        "description":"Video end time",
+        "type":"string",
+        "format":"dateTime"
+    },
+    "TimeErr":{
+        "description":"Time error, in seconds",
+        "type":"integer"
+    },
+    "Width":{
+        "description":"Width in pixels",
+        "type":"integer"
+    },
+    "Height":{
+        "description":"Height in pixels",
+        "type":"integer"
+    },
+    "QualityGrade":{
+        "description":"Video quality level. 1: worst; 2: bad; 3:
+normal; 4: fine; 5: best",
+        "enum":[1,2,3,4,5]
+    },
+    "CollectorName":{
+        "description":"The name of the person who collected the
+video data or the name of the acquisition system/platform",
+        "type":"string"
+    },
+    "CollectorOrg":{
+        "description":"The name of the video acquisition unit",
+        "type":"string"
+    },
+    "CollectorPhone":{
+        "description":"Contact number of the person who
+collected the video.",
+        "type":"string"
+    },
+    "EntryClrk":{
+        "description":"The name of the entry person of the video
+or the name of the entry system",
+        "type":"string"
+    },
+    "EntryClrkOrg":{
+        "description":"The name of storage unit of video
+materials",
+        "type":"string"
+    },
+    "EntryTime":{
+        "description":"Entry time, this attribute is not needed
+in the POST method, it is automatically generated when creating",
+        "type":"string",
+        "format":"dateTime"
+    },
+    "VideoProcFlag":{
+        "description":"Video processing flag",
+        "$ref":"/schema/components#/$defs/flag"
+    },
+    "FileSize":{
+        "description":"Video slice size, in bytes",
+        "type":"number",
+        "format":"long"
+    },
+    "FileData":{
+
+```
+
+```
+
+                "$ref":"/schema/components#/$defs/binary"
+            }
+        },
+
+        "required":["InfoKind","VideoSourcePos","FileFormat","VideoEncodeFormat","AudioFlag","Title","ContentDescription","ShotPlaceCode","ShotPlaceFullAdress","VideoLen","BeginTime","EndTime","TimeErr","Width","Height"],
+
+        "allOf":[
+            {
+                "if":{
+                    "properties":{"IsAbstractVideo":true }
+                },
+                "then":{
+                    "properties":{
+                        "anyOf":[{
+                            "OriginVideoID":{
+                                "description":"Original video ID",
+                                "$ref":"/schema/components#/$defs/basicObjectId"
+                            }
+                        },{
+                            "OriginVideoURL":{
+                                "description":"Original video URL",
+                                "$ref":"/schema/components#/$defs/storagePath"
+                            }
+                        }]
+                    }
+                }
+            },
+            {
+                "if":{
+                    "properties":{"InfoKind":1 }
+                },
+                "then":{
+                    "required":["EventSort"]
+                }
+            },
+            {
+                "if":{
+                    "properties":{"InfoKind":2 }
+                },
+                "then":{
+                    "required":["VideoID","CollectorName","CollectorOrg","EntryClrk","EntryClrkOrg"]
+                }
+            }
+        ]
+    }
+}
+
+```
+
+### A.2.6 /schema/image-info-list
+
+```
+
+{
+    "$schema":"https://json-schema.org/draft/2020-12/schema",
+    "$id":"http://www.itu.int/schema/image-info-list",
+    "description":"Structure definition of image list",
+
+    "type":"array",
+    "items":{
+
+```
+
+50 Rec. ITU-T H.627.3 (12/2022)
+
+```
+
+        "$ref":"#/$defs/imageInfo"
+    },
+    "$defs":{
+        "imageInfo":{
+            "type":"object",
+            "description":"Image content definition",
+            "properties" : {
+                "ImageID":{
+                    "description":"Image ID",
+                    "$ref":"/schema/components#/$defs/basicObjectId"
+                },
+                "InfoKind":{
+                    "$ref":"/schema/components#/$defs/infoKind"
+                },
+                "ImageSourcePos":{
+                    "description":"Image acquisition part, key public area
+part, A\d{6}",
+                    "type":"string",
+                    "deprecated":true
+                },
+                "SourceVideoID":{
+                    "description":"Source video ID",
+                    "$ref":"/schema/components#/$defs/basicObjectId"
+                },
+                "OriginImageID":{
+                    "description":"Original image ID",
+                    "$ref":"/schema/components#/$defs/basicObjectId"
+                },
+                "EventSort":{
+                    "$ref":"/schema/video-slice-info-
+list#/$defs/videoSliceInfo/properties/EventSort"
+                },
+                "DeviceID":{
+                    "description":" Acquisition device code",
+                    "$ref":"/schema/components#/$defs/deviceID"
+                },
+                "StoragePath":{
+                    "description":"Storage path",
+                    "$ref":"/schema/components#/$defs/storagePath"
+                },
+                "FileHash":{
+                    "$ref":"/schema/video-slice-info-
+list#/$defs/videoSliceInfo/properties/FileHash"
+                },
+                "FileFormat":{
+                    "description":"Image format",
+                    "enum":["Bmp", "Gif", "Jpeg", "Jfif", "Kdc", "Pcd", "Pcx", "Pic", "Pix", "Png", "Psd"
+, "Tapga", "Tiff", "Wmf", "Jp2", "Other"]
+                },
+                "ShotTime":{
+                    "description":"Shooting Time",
+                    "type":"string",
+                    "format":"dateTime"
+                },
+                "Title":{
+                    "description":"Description of image name",
+                    "type":"string"
+                },
+                "TitleNote":{
+                    "description":"Title supplements and remarks",
+                    "type":"string"
+                },
+                "SpecialName":{
+
+```
+
+```
+
+        "description":"The name of the subject to which the
+video belongs",
+        "type":"string"
+    },
+    "Keyword":{
+        "description":"Words or phrases with retrieval
+significance that express the main content of the video",
+        "type":"string"
+    },
+    "ContentDescription":{
+        "description":"Brief description of video content",
+        "type":"string"
+    },
+    "ShotPlaceCode":{
+        "description":"Shooting location area code",
+        "$ref":"/schema/ape-
+list#/$defs/ape/properties/PlaceCode"
+    },
+    "ShotPlaceFullAdress":{
+        "$ref":"/schema/ape-list#/$defs/ape/properties/Place"
+    },
+    "ShotPlaceLongitude":{
+        "$ref":"/schema/ape-
+list#/$defs/ape/properties/Longitude"
+    },
+    "ShoPlacetLatitude":{
+        "$ref":"/schema/ape-list#/$defs/ape/properties/Latitude"
+    },
+    "HorizontalShotDirection":{
+        "description":"Horizontal shooting direction",
+        "$ref":"/schema/components#/$defs/hDirection"
+    },
+    "VerticalShotDirection":{
+        "description":"Vertical shooting direction",
+        "$ref":"/schema/components#/$defs/vDirection"
+    },
+    "SecurityLevel":{
+        "$ref":"/schema/components#/$defs/securityLevel"
+    },
+    "Width":{
+        "description":"Width in pixels",
+        "type":"integer"
+    },
+    "Height":{
+        "description":"Height in pixels",
+        "type":"integer"
+    },
+    "CameraManufacturer":{
+        "description":"manufacturer name, if the photo is from a
+camera, fill in the camera manufacturer",
+        "type":"string"
+    },
+    "CameraVersion":{
+        "description":"Camera brand and model. If the photo is
+from a camera, fill in the model of the camera.",
+        "type":"string"
+    },
+    "ApertureValue":{
+        "description":"Aperture value",
+        "type":"integer"
+    },
+    "ISOSensitivity":{
+        "description":"ISO sensitivity value",
+        "type":"integer"
+    }
+}
+
+```
+
+```
+
+    },
+    "FocalLength":{
+        "description":"Focal length",
+        "type":"integer"
+    },
+    "QualityGrade":{
+        "description":"Video quality level. 1: worst; 2: bad; 3:
+normal; 4: fine; 5: best",
+        "enum":[1,2,3,4,5]
+    },
+    "CollectorName":{
+        "description":"The name of the person who collected the
+video data or the name of the acquisition system/platform",
+        "type":"string"
+    },
+    "CollectorOrg":{
+        "description":"The name of the video data acquisition
+unit",
+        "type":"string"
+    },
+    "CollectorPhone":{
+        "description":"Contact number of the person who
+collected the video.",
+        "type":"string"
+    },
+    "EntryClrk":{
+        "description":"The name of the entry person of the video
+or the name of the entry system",
+        "type":"string"
+    },
+    "EntryClrkOrg":{
+        "description":"The name of storage unit of video",
+        "type":"string"
+    },
+    "EntryTime":{
+        "description":"Entry time, this attribute is not needed
+in the POST method, it is automatically generated when creating",
+        "type":"string",
+        "format":"dateTime"
+    },
+    "ImgProcFlag":{
+        "description":"Image processing flag",
+        "$ref":"/schema/components#/$defs/flag"
+    },
+    "FileSize":{
+        "description":"Video slice size, in bytes",
+        "type":"number",
+        "format":"long"
+    },
+    "FileData":{
+        "$ref":"/schema/components#/$defs/binary"
+    }
+},
+
+"required":["InfoKind","ImageSourcePos","FileFormat","ShotTime","Title","Co
+ntentDescription","ShotPlaceFullAdress","SecurityLevel","Width","Height"],
+
+"allOf":[
+{
+    "if":{
+        "properties":{"InfoKind":1  }
+    },
+    "then":{
+
+```
+
+```
+
+        "required": ["EventSort"]
+      }
+    },
+    {
+      "if": {
+        "properties": { "InfoKind": 2 }
+      },
+      "then": {
+        "required": ["ImageID", "ShotPlaceCode", "CollectorName", "CollectorOrg", "Entry
+Clrk", "EntryClrkOrg"]
+      }
+    }
+  ]
+}
+}
+}
+}
+
+```
+
+#### A.2.7 /schema/motor-vehicle-list
+
+```
+
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "http://www.itu.int/schema/motor-vehicle-list",
+  "description": "Structure definition of motor vehicle list",
+
+  "type": "array",
+  "items": {
+    "$ref": "#/$defs/motorVehicle"
+  },
+  "$defs": {
+    "motorVehicle": {
+      "type": "object",
+      "description": "Motor vehicle description information definition",
+      "properties" : {
+        "MotorVehicleID": {
+          "description": "Motor vehicle ID",
+          "$ref": "/schema/components#/$defs/imageCntObjectId"
+        },
+        "InfoKind": {
+          "$ref": "/schema/components#/$defs/infoKind"
+        },
+        "SourceID": {
+          "description": "The VideoID or imageID of the source of
+the collector object",
+          "$ref": "/schema/components#/$defs/basicObjectId"
+        },
+        "TollgateID": {
+          "description": "Associated tollgate number",
+          "$ref": "/schema/components#/$defs/deviceID"
+        },
+        "DeviceID": {
+          "description": "Device ID",
+          "$ref": "/schema/components#/$defs/deviceID"
+        },
+        "StorageUrl1": {
+          "description": "Close-up photo",
+          "$ref": "/schema/components#/$defs/storagePath"
+        },
+        "StorageUrl2": {
+          "description": "License plate photo.",
+          "$ref": "/schema/components#/$defs/storagePath"
+        },
+        "LeftTopX": {
+
+```
+
+```
+
+        "description":"X-axis coordinate of the upper left
+corner of the small picture of the motor vehicle",
+        "$ref":"/schema/components#/$defs/imageCoordinates"
+    },
+    "LeftTopY":{
+        "description":"Y-axis coordinate of the upper left
+corner of the small picture of the motor vehicle",
+        "$ref":"/schema/components#/$defs/imageCoordinates"
+    },
+    "RightBtnX":{
+        "description":"X-axis coordinate of the lower right
+corner of the small picture of the motor vehicle",
+        "$ref":"/schema/components#/$defs/imageCoordinates"
+    },
+    "RightBtnY":{
+        "description":"Y-axis coordinate of the lower right
+corner of the small picture of the motor vehicle",
+        "$ref":"/schema/components#/$defs/imageCoordinates"
+    },
+    "LaneNo":{
+        "$ref":"/schema/lane-list#/$defs/lane/properties/LaneNo"
+    },
+    "HasPlate":{
+        "description":"There is a license plate or not",
+        "$ref":"/schema/components#/$defs/flag"
+    },
+    "PlateClass":{
+        "description":"Types of license plates. 01: large car
+license plates; 02: small car license plates; 99: other license plates",
+        "enum":["01", "02", "99"]
+    },
+    "PlateColor":{
+        "description":"License plate color",
+        "$ref":"/schema/components#/$defs/color"
+    },
+    "PlateNo":{
+        "description":"License plate number",
+        "type":"string"
+    },
+    "PlateNoAttach":{
+        "description":"Trailer license plate number",
+        "type":"string"
+    },
+    "PlateDescribe":{
+        "description":"License plate description, license plate
+frame advertising information, including dealership, contact number, etc.",
+        "type":"string"
+    },
+    "IsAltered":{
+        "description":"License plate altered or not",
+        "$ref":"/schema/components#/$defs/flag"
+    },
+    "IsCovered":{
+        "description":"License plate covered or not",
+        "$ref":"/schema/components#/$defs/flag"
+    },
+    "Speed":{
+        "description":"Speed, in kilometers per hour.",
+        "type":"double"
+    },
+    "Direction":{
+        "description":"Driving Direction",
+        "$ref":"/schema/components#/$defs/hDirection"
+    },
+
+```
+
+```
+
+    "VehicleModel":{
+      "description":"Vehicle model",
+      "type":"string",
+      "examples":["Passat,Volvo,BMW"]
+    },
+    "VehicleStyles":{
+      "description":"Vehicle year",
+      "examples":["2022,2021"],
+      "type":"string"
+    },
+    "VehicleColor":{
+      "description":"Vehicle color",
+      "$ref":"/schema/components#/$defs/color"
+    },
+    "VehicleColorDepth":{
+      "description":"Vehicle color depth. 0: dark; 1: light",
+      "enum":[0,1]
+    },
+    "VehicleFrontItem":{
+      "description":"Items on the front of the vehicle. 1:
+logo, detection mark; 2: perfume; 3: ornaments; 4: main sun visor; 99: Other",
+      "enum":[1,2,3,4,99]
+    },
+    "DescOfFrontItem":{
+      "description":"Description of items on the front of the
+vehicle",
+      "type":"string"
+    },
+    "VehicleRearItem":{
+      "description":"Items on the rear of the vehicle. 1:
+Pillow; 2: Umbrella; 3: Paper towel (box); 4: Car sticker; 5: Logo; 99: other",
+      "enum":[1,2,3,4,5,99]
+    },
+    "DescOfRearItem":{
+      "description":"Description of items on the rear of the
+vehicle",
+      "type":"string"
+    },
+    "PassTime":{
+      "description":"Passing time",
+      "type":"string",
+      "format":"dateTimeMS"
+    },
+    "Sunvisor":{
+      "description":"The sun visor is put down or not",
+      "$ref":"/schema/components#/$defs/flag"
+    },
+    "SafetyBelt":{
+      "description":"The driver is wearing a seat belt or
+not",
+      "$ref":"/schema/components#/$defs/flag"
+    },
+    "Calling":{
+      "description":"The driver is calling or not",
+      "$ref":"/schema/components#/$defs/flag"
+    },
+    "PlateReliability":{
+      "description":"The recognition reliability of the entire
+license plate number is expressed as a percentage from 0 to 100. The larger the
+value, the higher the reliability.",
+      "type":"string"
+    },
+    "PlateCharReliability":{
+
+```
+
+```
+
+        "description":"The recognition credibility of the number
+plate number is expressed as a percentage from 0 to 100. The larger the value,
+the higher the credibility. Arranged in the manner of <character 1-credibility
+1, character 2-credibility 2>, the middle is English half-width connecting line,
+comma",
+        "type":"string",
+        "examples":["B-90", "1-90"]
+    },
+    "SubImageInfoListObject":{
+        "$ref":"/schema/subimage-info-list"
+    },
+    "FeatureInfoListObject":{
+        "$ref":"/schema/feature-ext-result-
+list#/$defs/featureInfoList"
+    },
+    "TabID":{
+        "description":"Attribution category label",
+        "$ref":"/schema/components#/$defs/basicObjectId"
+    }
+},
+
+"required":["MotorVehicleID", "InfoKind", "SourceID", "StorageUrl1"],
+
+"if":{
+    "properties":{"InfoKind":1  }
+},
+"then":{
+
+"required":["DeviceID", "LeftTopX", "LeftTopY", "RightBtnX", "RightBtnY"]
+}
+
+    }
+}
+}
+
+```
+
+#### A.2.8 /schema/nonmotor-vehicle-list
+
+```
+
+{
+    "$schema":"https://json-schema.org/draft/2020-12/schema",
+    "$id":"http://www.itu.int/schema/nonmotor-vehicle-list",
+    "description":"Structure definition of non-motor vehicle list",
+
+    "type":"array",
+    "items":{
+        "$ref":"#/$defs/nonMotorVehicle"
+    },
+    "$defs":{
+        "nonMotorVehicle":{
+            "type":"object",
+            "description":"Non-motor vehicle description information content
+definition",
+            "properties" : {
+                "MotorVehicleID":{
+                    "description":"Non-motor vehicle ID",
+                    "$ref":"/schema/components#/$defs/imageCntObjectId"
+                },
+                "InfoKind":{
+                    "$ref":"/schema/components#/$defs/infoKind"
+                },
+                "SourceID":{
+                    "description":"VideoID or imageID of the source of the
+non-motor vehicle object",
+                    "$ref":"/schema/components#/$defs/basicObjectId"
+                },
+            },
+        },
+    },
+}
+
+```
+
+```
+
+    "DeviceID":{
+      "description":"Device ID",
+
+      "$ref":"/schema/components#/$defs/deviceID"
+    },
+    "LeftTopX":{
+      "description":"X-axis coordinate of the upper left
+corner of the small picture of non-motor vehicle",
+      "$ref":"/schema/components#/$defs/imageCoordinates"
+    },
+    "LeftTopY":{
+      "description":"Y-axis coordinate of the upper left
+corner of the small picture of the non-motor vehicle",
+      "$ref":"/schema/components#/$defs/imageCoordinates"
+    },
+    "RightBtmX":{
+      "description":"X-axis coordinate of the lower right
+corner of the small picture of non-motor vehicle",
+      "$ref":"/schema/components#/$defs/imageCoordinates"
+    },
+    "RightBtmY":{
+      "description":"Y-axis coordinate of the lower right
+corner of the small picture of non-motor vehicle",
+      "$ref":"/schema/components#/$defs/imageCoordinates"
+    },
+    "HasPlate":{
+      "description":"There is a license plate or not",
+      "$ref":"/schema/components#/$defs/flag"
+    },
+    "PlateClass":{
+      "$ref":"/schema/motor-vehicle-
+list#/$defs/motorVehicle/properties/PlateClass"
+    },
+    "PlateColor":{
+      "description":"License plate color",
+      "$ref":"/schema/components#/$defs/color"
+    },
+    "PlateNo":{
+      "description":"License plate number",
+      "type":"string"
+    },
+    "PlateDescribe":{
+      "description":"License plate description, license plate
+frame advertising information, including dealership, contact number, etc.",
+
+      "type":"string"
+    },
+    "NonMotorVehicleStructClass":{
+      "description":"Non-motor vehicle structure category",
+      "type":"string",
+      "pattern":"^\\d{3}$"
+    },
+    "SubImageInfoListObject":{
+      "$ref":"/schema/subimage-info-list"
+    },
+    "FeatureInfoListObject":{
+      "$ref":"/schema/feature-ext-result-
+list#/$defs/featureInfoList"
+    },
+    "TabID":{
+      "description":"Attribution category label",
+      "$ref":"/schema/components#/$defs/basicObjectId"
+    }
+  },
+}
+
+```
+
+```
+
+    "required": ["NonMotorVehicleID", "InfoKind", "SourceID"],
+
+    "if": {
+      "properties": { "InfoKind": 1 }
+    },
+    "then": {
+      "required": ["DeviceID", "LeftTopX", "LeftTopY", "RightBtmX", "RightBtmY"]
+    }
+  }
+}
+}
+
+```
+
+#### A.2.9 /schema/case-info-list
+
+```
+
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "http://www.itu.int/schema/case-info-list",
+  "description": "Structure definition of case list",
+
+  "type": "array",
+  "items": {
+    "$ref": "#/$defs/caseInfo"
+  },
+  "$defs": {
+    "caseInfo": {
+      "type": "object",
+      "description": "Case description information content definition",
+      "properties": {
+        "CaseID": {
+          "description": "Case ID",
+          "$ref": "/schema/components#/$defs/caseObjectId"
+        },
+        "CaseLinkMark": {
+          "description": "The video slice or image of the associated case, can be multiple, if multiple, they are separated by an English semicolon \";\"",
+          "$ref": "/schema/components#/$defs/basicObjectId"
+        },
+        "CaseName": {
+          "description": "Case name",
+          "type": "string"
+        },
+        "CaseAbstract": {
+          "description": "Abstract description of case",
+          "type": "string"
+        },
+        "CreateTime": {
+          "description": "Creation time",
+          "type": "string",
+          "format": "dateTime"
+        },
+        "PlaceCode": {
+          "description": "Case occurrence area code",
+          "type": "string"
+        },
+        "PlaceFullAddress": {
+          "description": "Detailed location description of the case.",
+          "type": "string"
+        },
+        "Longtitude": {
+
+```
+
+```
+
+        "description":"Longitude of the case",
+        "$ref":"/schema/ape-
+list#/$defs/ape/properties/Longitude"
+      },
+      "Latitude":{
+        "description":"Latitude of the case",
+        "$ref":"/schema/ape-list#/$defs/ape/properties/Latitude"
+      },
+      "MotorVehicleIDs":{
+        "description":"Case-related motor vehicle
+identification, can be multiple, if multiple, they are separated by an English
+semicolon \";\\"",
+        "$ref":"/schema/components#/$defs/imageCntObjectId"
+      },
+      "NonMotorVehicleIDs":{
+        "description":"Case-related non-motor vehicle
+identification, can be multiple, if multiple, they are separated by an English
+semicolon \";\\"",
+        "$ref":"/schema/components#/$defs/imageCntObjectId"
+      },
+      "RelateCaseIdList":{
+        "description":"Case associated case identification, can
+be multiple, if multiple, they are separated by an English semicolon \";\\"",
+        "$ref":"/schema/components#/$defs/caseObjectId"
+      }
+    },
+    "required":["CaseID", "CaseName", "CaseAbstract", "CreateTime", "PlaceCode", "Pl
+aceFullAddress"]
+  }
+}
+}
+
+```
+
+#### A.2.10 /schema/disposition-list
+
+```
+
+{
+  "$schema":"https://json-schema.org/draft/2020-12/schema",
+  "$id":"http://www.itu.int/schema/disposition-list",
+  "description":"Structure definition of the disposition list",
+
+  "type":"array",
+  "items":{
+    "$ref":"#/$defs/disposition"
+  },
+  "$defs":{
+    "disposition":{
+      "type":"object",
+      "description":"Structure description of disposition object",
+      "properties" : {
+        "DispositionID":{
+          "description":"The disposition ID is generated by DSS
+when disposing, and cannot be empty when cascading calls",
+          "$ref":"/schema/components#/$defs/businessObjectId"
+        },
+        "Title":{
+          "description":"The title of disposition, describing the
+theme and purpose of disposition",
+          "type":"string"
+        },
+        "DispositionCategory":{
+          "description":"Disposition category. 1: Motor vehicle;
+2: Non-motor vehicle; 3: Keyword",
+          "enum":[1,2,3,4,5]
+        },
+      },
+    },
+  },
+}
+
+```
+
+```
+
+        "TargetFeature":{
+            "description":"Features of the disposed object. Value is
+a combination of multiple kvs:'(k1=v1) and (k2=v2)' or (k3=v3)' Supports
+regular expressions for fuzzy matching. The value and meaning of kn are, 1:
+license plate; 2: license plate color; 3: vehicle brand; 4: vehicle model; 5:
+vehicle model year; 6: keyword.",
+            "type":"string",
+            "examples":"2=blue"
+        },
+        "TargetImageURI":{
+            "description":"Disposed object image path",
+            "$ref":"/schema/components#/$defs/storagePath"
+        },
+        "PriorityLevel":{
+            "description":"Disposition priority, 1 means the highest
+level",
+            "enum":[1,2,3]
+        },
+        "ApplicantName":{
+            "description":"Applicant",
+            "type":"string"
+        },
+        "ApplicantInfo":{
+            "description":"Applicant's contact information, mobile
+phone number, email address, etc.",
+            "type":"string"
+        },
+        "ApplicantOrg":{
+            "description":"Applicant unit",
+            "type":"string"
+        },
+        "BeginTime":{
+            "description":"Disposition start time",
+            "type":"string",
+            "format":"dateTime"
+        },
+        "EndTime":{
+            "description":"Disposition end time",
+            "type":"string",
+            "format":"dateTime"
+        },
+        "CreatTime":{
+            "description":"The creation time of disposing is
+automatically generated by the system",
+            "type":"string",
+            "format":"dateTime"
+        },
+        "OperateType":{
+            "description":"Disposition type.0: Disposition; 1:
+Remove disposition",
+            "enum":[0,1]
+        },
+        "DispositionStatus":{
+            "description":"Disposition status. 0: Disposed; 1:
+Removed disposition; 2: Disposition expired; 9: Not disposed",
+            "enum":[0,1,2,9]
+        },
+        "DispositionRange":{
+            "description":"Disposition range. 1: tollgate; 2: area
+range",
+            "enum":[1,2]
+        },
+        "TollgateList":{
+
+```
+
+```
+
+        "description":"The ID of the disposed tollgate, can be
+multiple, if multiple, they are separated by an English semicolon \";\"",
+        "$ref":"/schema/tollgate-
+list#/$defs/tollgate/properties/TollgateID"
+    },
+    "DispositionArea":{
+        "description":"Disposition area code, can be multiple,
+if multiple, they are separated by an English semicolon \";\"",
+        "type":"string"
+    },
+    "DeviceList":{
+        "description":"Disposed device ID, can be multiple, if
+multiple, they are separated by an English semicolon \";\"",
+        "$ref":"/schema/ape-list#/$defs/ape/properties/ApeID"
+    },
+    "ReceiveAddr":{
+        "description":"The receiving address of the notification
+information, according to the address to decide whether to receive or forward",
+        "$ref":"/schema/components#/$defs/urlPath"
+    },
+    "ReceiveMobile":{
+        "description":"Notification receiving mobile phone
+number, can be multiple, if multiple, they are separated by an English semicolon
+\";\"",
+        "type":"string"
+    },
+    "Reason":{
+        "description":"Reason for disposition",
+        "type":"string"
+    },
+    "DispositionRemoveOrg":{
+        "description":"Name of removing disposition unit",
+        "type":"string"
+    },
+    "DispositionRemovePerson":{
+        "description":"Removing disposition people",
+        "type":"string"
+    },
+    "DispositionRemoveTime":{
+        "description":"Removing disposition time",
+        "type":"string",
+        "format":"dateTime"
+    },
+    "DispositionRemoveReason":{
+        "description":"Reason for removing disposition",
+        "type":"string"
+    },
+    "SubImageInfoListObject":{
+        "description":"Image list",
+        "$ref":"/schema/subimage-info-list"
+    },
+    "FeatureObject":{
+        "description":"Feature list",
+        "$ref":"/schema/feature-ext-result-
+list#/$defs/featureInfo"
+    },
+    "ResultImageDeclare":{
+        "description":"Return picture convention. -1: No
+picture; 01: Large image of the vehicle; 02: Small color image of the license
+plate; 03: Binary image of the license plate; 04: Vehicle logo; 05: Violation
+composite image; 06: Passing vehicle composite image; 07: Vehicle close-up
+image; 08: Non-motorized vehicle image; 100: General picture",
+        "enum":["-
+1","01","02","03","04","05","06","07","08",100]
+    }
+}
+
+```
+
+```
+
+    },
+    "ResultFeatureDeclare":{
+      "description":"Return feature vector flag. -1: No need
+to return feature vector; 1: Need to return feature vector",
+      "enum":[-1,1]
+    },
+    "TabID":{
+      "description":"Disposition label flag",
+      "$ref":"/schema/components#/$defs/basicObjectIdType"
+    },
+    "AlarmSensitivity":{
+      "description":"Warning sensitivity, the higher the
+sensitivity, the lower the warning threshold, the higher the false alarm rate.
+1: Level 1; 2: Level 2; 3: Level 3",
+      "enum":[1,2,3]
+    }
+  },
+  "required":["OperateType"],
+  "allOf":[
+  {
+    "if":{
+      "properties":{"OperateType":0    }
+    },
+    "then":{
+      "required":["Title","DispositionCategory","TargetFeature","ApplicantName",
+"ApplicantOrg","DispositionRange"]
+    }
+  },
+  {
+    "if":{
+      "properties":{"OperateType":1    }
+    },
+    "then":{
+      "required":["DispositionID"]
+    }
+  }
+  ]
+}
+
+```
+
+#### A.2.11 /schema/disposition-notification-list
+
+```
+
+{
+  "$schema":"https://json-schema.org/draft/2020-12/schema",
+  "$id":"http://www.itu.int/schema/disposition-notification-list",
+  "description":"Structure definition of notification list",
+
+  "type":"array",
+  "items":{
+    "$ref":"#/$defs/dispositionNotification"
+  },
+  "$defs":{
+    "dispositionNotification":{
+      "type":"object",
+      "description":"Structure description of notification list",
+      "properties" : {
+        "NotificationID":{
+          "description":"Notification ID corresponding to
+disposition",
+          "$ref":"/schema/components#/$defs/businessObjectId"
+        },
+        "DispositionID":{
+
+```
+
+```
+
+        "description":"Disposition ID",
+        "$ref":"/schema/components#/$defs/businessObjectId"
+    },
+    "Title":{
+        "description":"The title of disposition, describing the
+theme and purpose of disposition",
+        "type":"string"
+    },
+    "TriggerTime":{
+        "description":"Trigger time",
+        "type":"string",
+        "format":"dateTime"
+    },
+    "MotorVehicleObject":{
+        "description":"Automatically collected motor vehicle
+data",
+        "$ref":"/schema/motor-vehicle-list#/$defs/motorVehicle"
+    },
+    "NonMotorVehicleObject":{
+        "description":"Automatically collected non-motor vehicle
+data",
+        "$ref":"/schema/nonmotor-vehicle-
+list#/$defs/nonMotorVehicle"
+    },
+    "CaseInfoObject":{
+        "description":"Automatically collected case data",
+        "$ref":"/schema/case-info-list#/$defs/caseInfo"
+    },
+    "DispositionTargetID":{
+        "description":"The disposition target ID can be the
+identification of the disposed vehicle, etc., or the image identification of
+disposed multiple image lists.",
+        "type":"string"
+    }
+}
+
+},
+"required":["NotificationID", "DispositionID", "Title", "TriggerTime"]
+}
+}
+}
+
+```
+
+#### A.2.12 /schema/subscribe-list
+
+```
+
+{
+    "$schema":"https://json-schema.org/draft/2020-12/schema",
+    "$id":"http://www.itu.int/schema/subscribe-list",
+    "description":"Structure definition of subscription list",
+    "type":"array",
+    "items":{
+        "$ref":"#/$defs/subscribe"
+    },
+    "$defs":{
+        "subscribe":{
+            "type":"object",
+            "description":"Subscription object structure description",
+            "properties" : {
+                "SubscribeID":{
+                    "description":"Subscription ID, generated by DSS when
+desposing, cannot be empty when cascading call",
+                    "$ref":"/schema/components#/$defs/businessObjectId"
+                },
+                "Title":{
+                    "description":"The title of disposition, describing the
+theme and purpose of disposition",
+
+```
+
+```
+
+        "type":"string"
+    },
+    "SubscribeDetail":{
+        "description":"Subscription category, can be multiple,
+if multiple, usually they are separated by an English half-width','. 1:
+Acquisition device catalog; 2: Acquisition device status; 3: Acquisition system
+catalog ; 4: Acquisition system status; 5: Video tollgate catalog; 6: Single
+bayonet record; 7: Lane catalog; 8: Single lane record; 9: Motor vehicle
+information; 10: Self-non-motor vehicle information; 11: File information; 12:
+Video slice; 13: Image; 14: Data classification label list",
+        "enum":["1","2","3","4","5","6","7","8","9","10","11","12","13","14"],
+        "examples":"1,2"
+    },
+    "ResourceClass":{
+        "description":"Subscription resource category. 0:
+tollgate; 1: device; 2: acquisition content; 3: case; 4: image library; 5:
+administrative division",
+        "enum":[0,1,2,3,4,5]
+    },
+    "ResourceURI":{
+        "description":"Subscription resource path, tollgate ID,
+device ID, acquisition content ID, case ID, target image library ID, area code
+2/4/6 bits, etc., can be multiple, only one resource category at a time.",
+        "type":"string"
+    },
+    "ApplicantName":{
+        "description":"Applicant",
+        "type":"string"
+    },
+    "ApplicantOrg":{
+        "description":"Applicant unit",
+        "type":"string"
+    },
+    "BeginTime":{
+        "description":"Subscription start time",
+        "type":"string",
+        "format":"dateTime"
+    },
+    "EndTime":{
+        "description":"Subscription end time",
+        "type":"string",
+        "format":"dateTime"
+    },
+    "ReceiveAddr":{
+        "description":"Notification information receiving
+address, according to the address to decide whether to receive or forward",
+        "$ref":"/schema/components#/$defs/urlPath"
+    },
+    "ReportInterval":{
+        "description":"Report interval, in seconds, <=0 means no
+limit",
+        "type":"integer"
+    },
+    "Reason":{
+        "description":"Reason for subscription",
+        "type":"string"
+    },
+    "OperateType":{
+        "description":"Subscription type. 1: Subscription; 2:
+Cancel subscription",
+        "enum":[1,2]
+    },
+    "SubscribeStatus":{
+
+```
+
+```
+
+        "description":"Subscription status. 1: subscribing; 2:
+canceled subscription; 3: subscription expired; 4: not subscribed; 9: other",
+        "enum":[1,2,3,4,9]
+    },
+    "SubscribeCancelOrg":{
+        "description":"Unsubscribe unit name",
+        "type":"string"
+    },
+    "SubscribeCancelPerson":{
+        "description":"Subscription canceller",
+        "type":"string"
+    },
+    "CancelTime":{
+        "description":"Cancel subscription time",
+        "type":"string",
+        "format":"dateTime"
+    },
+    "CancelReason":{
+        "description":"Reason for canceling subscription",
+        "type":"string"
+    },
+    "ResultImageDeclare":{
+        "description":"Return picture convention. 00: No
+picture; 01: Large image of the vehicle; 02: Small color image of the license
+plate; 03: Binary image of the license plate; 04: Car logo; 05: Violation
+composite image; 06: Passing vehicle composite image; 07: Vehicle close-up
+image;08: Non-motorized vehicle image; 100 :General picture",
+        "enum":["00","01","02","03","04","05","06","07","08","09","10","100"]
+    },
+    "ResultFeatureDeclare":{
+        "description":"feature vector declare. 0: No need to
+return feature vector; 1: Need to return feature vector ",
+        "enum":[0,1]
+    },
+    "TabID":{
+        "description":"Subscription category label
+identification",
+
+        "$ref":"/schema/components#/$defs/basicObjectIdType"
+    }
+},
+
+"required":["OperateType","ResultImageDeclare","ResultFeatureDeclare"],
+
+"allOf":[
+{
+    "if":{
+        "properties":{"OperateType":0 }
+    },
+    "then":{
+"required":["Title","SubscribeDetail","ResourceClass","ResourceURI","ApplicantName","ApplicantOrg","BeginTime","EndTime"]
+    }
+},
+{
+    "if":{
+        "properties":{"OperateType":1 }
+    },
+    "then":{
+        "required":["SubscribeID"]
+    }
+}
+]
+}
+
+```
+
+```
+
+    }
+  }
+
+```
+
+#### A.2.13 /schema/subscribe-notification-list
+
+```
+
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "http://www.itu.int/schema/subscribe-notification-list",
+  "description": "Structure definition of notification list",
+
+  "type": "array",
+  "items": {
+    "$ref": "#/$defs/subscribeNotification"
+  },
+  "$defs": {
+    "subscribeNotification": {
+      "type": "object",
+      "description": "Notification object structure description",
+      "properties" : {
+        "NotificationID": {
+          "description": "Subscribe to the corresponding
+notification ID",
+          "$ref": "/schema/components#/$defs/businessObjectId"
+        },
+        "SubscribeID": {
+          "description": "Subscription ID",
+          "$ref": "/schema/components#/$defs/businessObjectId"
+        },
+        "Title": {
+          "description": "The title of disposition, describing the
+theme and purpose of arming",
+          "type": "string"
+        },
+        "TriggerTime": {
+          "description": "Trigger time",
+          "type": "string",
+          "format": "dateTime"
+        },
+        "InfoIDs": {
+          "description": "Identification acquisition of detailed
+information (motor vehicle, non-motor vehicle) of subscription notification",
+          "type": "string"
+        },
+        "CaseListobject": {
+          "description": "Case data acquisition",
+          "$ref": "/schema/case-info-list"
+        },
+        "Tollgate": {
+          "description": "Tollgate data acquisition",
+          "$ref": "/schema/tollgate-list"
+        },
+        "Lane": {
+          "description": "Lane data acquisition",
+          "$ref": "/schema/lane-list"
+        },
+        "DeviceList": {
+          "description": " Acquisition device data acquisition",
+          "$ref": "/schema/ape-list"
+        },
+        "DeviceStatusList": {
+          "description": " Acquisition device status data
+acquisition",
+          "$ref": "/schema/ape-list#/$defs/apeStatusList"
+        },
+        "MotorVehicleListobject": {
+
+```
+
+```
+
+        "description":"Motor vehicle data acquisition",
+        "$ref":"/schema/motor-vehicle-list"
+    },
+    "NonMotorVehicleListobject":{
+        "description":"Non-motor vehicle data acquisition",
+        "$ref":"/schema/nonmotor-vehicle-list"
+    },
+    "DataClassTabListobject":{
+        "description":"Automatically collected case data",
+        "$ref":"/schema/components#/$defs/dataClassTabList"
+    },
+    "ExecuteOperation":{
+        "description":"Update operation. 1: add; 2: modify; 3:
+delete",
+        "enum":[1,2,3]
+    }
+},
+
+    "required":["NotificationID", "DispositionID", "Title", "TriggerTime"]
+}
+}
+}
+
+```
+
+#### A.2.14 /schema/subimage-info-list
+
+```
+
+{
+    "$schema":"https://json-schema.org/draft/2020-12/schema",
+    "$id":"http://www.itu.int/schema/subimage-info-list",
+    "description":"Structure definition of sub-image list",
+
+    "type":"array",
+    "items":{
+        "$ref":"#/$defs/subImageInfo"
+    },
+    "$defs":{
+        "subImageInfo":{
+            "type":"object",
+            "description":"Image content definition",
+            "properties" : {
+                "ImageID":{
+                    "description":"Image ID",
+                    "$ref":"/schema/components#/$defs/basicObjectId"
+                },
+                "EventSort":{
+                    "$ref":"/schema/video-slice-info-
+list#/$defs/videoSliceInfo/properties/EventSort"
+                },
+                "DeviceID":{
+                    "description":"Acquisition device code",
+                    "$ref":"/schema/components#/$defs/deviceID"
+                },
+                "StoragePath":{
+                    "description":"Storage path",
+                    "$ref":"/schema/components#/$defs/storagePath"
+                },
+                "Type":{
+                    "description":"Image file hash value. 01: Motor vehicle
+image; 02: License plate color small image; 03: License plate binarization
+image; 04: Vehicle logo image; 05: Violation composite image; 06: Passing
+vehicle composite image; 07: Vehicle close-up image;08: Non-motorized vehicle
+image; 09: Object image; 10: Vehicle Feature map, binary feature map; 11: non-
+motor vehicle feature map; 12: general feature map; 100: general picture",
+                    "enum":["01", "02", "03", "04", "05", "06", "07", "08", "09", "10", "11", "12", "13", "
+100"]
+                }
+            }
+        }
+    }
+}
+
+```
+
+```
+
+    },
+    "FileFormat":{
+      "$ref":"/schema/image-info-
+list#/$defs/imageInfo/properties/FileFormat"
+    },
+    "ShotTime":{
+      "description":"Shooting time",
+      "type":"string",
+      "format":"dateTime"
+    },
+    "Width":{
+      "description":"Width in pixels, in pixels",
+      "type":"integer"
+    },
+    "Height":{
+      "description":"Height in pixels, in pixels",
+      "type":"integer"
+    },
+    "Data":{
+      "$ref":"/schema/components#/$defs/base64"
+    },
+    "FeatureInfoObject":{
+      "$ref":"/schema/feature-ext-result-
+list#/$defs/featureInfo"
+    }
+  }
+}
+}
+}
+
+```
+
+#### A.2.15 /schema/image-searched-by-image
+
+```
+
+{
+  "$schema":"https://json-schema.org/draft/2020-12/schema",
+  "$id":"http://www.itu.int/schema/image-searched-by-image",
+  "description":"Structure definition of object searched by image",
+
+  "type":"object",
+
+  "properties" : {
+    "SearchID":{
+      "description":"Search ID, the 13th to 14th digits take 11 to
+indicate that the target is searched by image",
+      "$ref":"/schema/components#/$defs/basicObjectId"
+    },
+    "SearchType":{
+      "description":"Search type, specify the search target type",
+      "enum":["MotorVehicle", "NonMotorVehicle"]
+    },
+    "SubImageObject":{
+      "description":"Picture information searched by pictures in the
+image searching",
+      "$ref":"/schema/subimage-info-list#/$defs/subImageInfo"
+    },
+    "FeatureObject":{
+      "description":"Feature vector information searched by Feature
+vector in the image searching",
+      "$ref":"/schema/feature-ext-result-list#/$defs/featureInfo"
+    },
+    "Threshold":{
+      "description":"Similarity threshold",
+      "type":"number",
+      "format":"double",
+      "minimum":0,
+    }
+  }
+}
+
+```
+
+```
+
+        "maximum":1
+      }
+    },
+    "required":["SearchID"]
+  }
+}
+
+```
+
+#### A.2.16 /schema/image-result-SBI-list
+
+```
+
+{
+  "$schema":"https://json-schema.org/draft/2020-12/schema",
+  "$id":"http://www.itu.int/schema/image-result-SBI-list",
+  "description":"Structure definition of target result list object searched
+by image",
+  "type":"array",
+  "items":{
+    "$ref":"#/$defs/imageResultSBIList"
+  },
+  "$defs":{
+    "imageResultSBIList":{
+      "type":"object",
+      "description":"Query target result object by image",
+      "properties" : {
+        "SearchID":{
+          "description":"Search ID corresponding to the result",
+          "$ref":"/schema/components#/$defs/basicObjectId"
+        },
+        "MotorVehicleListObject":{
+          "description":"Returned motor vehicle search results",
+          "$ref":"/schema/motor-vehicle-list"
+        },
+        "NonMotorVehicleListObject":{
+          "description":"Returned non-motor vehicle search
+results",
+          "$ref":"/schema/nonmotor-vehicle-list"
+        }
+      },
+      "required":["SearchID"]
+    }
+  }
+}
+
+```
+
+#### A.2.17 /schema/case-list
+
+```
+
+{
+  "$schema":"https://json-schema.org/draft/2020-12/schema",
+  "$id":"http://www.itu.int/schema/case-list",
+  "description":"The definition of the structure of the video image case
+acquisition list. The video image case acquisition refers to objects that
+combine video image cases and associated video slices, images, motor vehicles,
+non-motor vehicles, etc.",
+  "type":"array",
+  "items":{
+    "$ref":"#/$defs/case"
+  },
+  "$defs":{
+    "case":{
+      "type":"object",
+      "description":"Video image case content definition",
+      "properties" : {
+        "CaseInfo":{
+          "$ref":"/schema/case-info-list#/$defs/caseInfo"
+        },
+        "VideoSliceListObject":{
+          "$ref":"/schema/video-slice-list"
+        }
+      }
+    }
+  }
+}
+
+```
+
+```
+
+    },
+    "ImageListObject":{
+      "$ref":"/schema/image-list"
+    },
+    "MotorVehicleListObject":{
+      "$ref":"/schema/motor-vehicle-list"
+    },
+    "NonMotorVehicleListObject":{
+      "$ref":"/schema/nonmotor-vehicle-list"
+    }
+  },
+  "required":["CaseInfo"]
+}
+}
+}
+
+```
+
+#### A.2.18 /schema/image-list
+
+```
+
+{
+  "$schema":"https://json-schema.org/draft/2020-12/schema",
+  "$id":"http://www.itu.int/schema/image-list",
+  "description":"Structure definition of the image acquisition list, which
+are objects that combine images with associated, motor vehicles, non-motor
+vehicles, etc.",
+  "type":"array",
+  "items":{
+    "$ref":"#/$defs/image"
+  },
+  "$defs":{
+    "image":{
+      "type":"object",
+      "description":"Image content definition",
+      "properties" : {
+        "ImageInfo":{
+          "$ref":"/schema/image-info-list#/$defs/imageInfo"
+        },
+        "MotorVehicleListObject":{
+          "$ref":"/schema/motor-vehicle-list"
+        },
+        "NonMotorVehicleListObject":{
+          "$ref":"/schema/nonmotor-vehicle-list"
+        }
+      },
+      "required":["ImageInfo"]
+    }
+  }
+}
+
+```
+
+#### A.2.19 /schema/video-slice-list
+
+```
+
+{
+  "$schema":"https://json-schema.org/draft/2020-12/schema",
+  "$id":"http://www.itu.int/schema/video-slice-list",
+  "description":"Structure definition of video slice acquisition list, video
+slice acquisition refers to the object that combines video slices and associated
+motor vehicles, non-motor vehicles, etc.",
+  "type":"array",
+  "items":{
+    "$ref":"#/$defs/videoSlice"
+  },
+  "$defs":{
+    "videoSlice":{
+      "type":"object",
+      "description":"Video slice content definition",
+      "properties" : {
+
+```
+
+```
+
+        "VideoSliceInfo":{
+          "$ref":"/schema/video-slice-info-list#
+/$defs/videoSliceInfo"
+        },
+        "MotorVehicleListObject":{
+          "$ref":"/schema/motor-vehicle-list"
+        },
+        "NonMotorVehicleListObject":{
+          "$ref":"/schema/nonmotor-vehicle-list"
+        }
+      },
+      "required":["VideoSliceInfo"]
+    }
+  }
+}
+
+```
+
+#### A.2.20 /schema/task-status-list
+
+```
+
+{
+  "$schema":"https://json-schema.org/draft/2020-12/schema",
+  "$id":"http://www.itu.int/schema/task-status-list",
+  "description":"Structure definition of analysis task status",
+
+  "type":"array",
+
+  "items":{
+    "$ref":"#/$defs/taskStatus"
+  },
+  "$defs":{
+    "taskStatus":{
+      "description":"Structure definition of analysis task status",
+      "type":"object",
+      "properties" : {
+        "TaskID":{
+          "description":"Task ID",
+          "$ref":"/schema/components#/$defs/basicObjectId"
+        },
+        "CommitTime":{
+          "description":"Task submission time",
+          "type":"string",
+          "format":"dateTime"
+        },
+        "BeginTime":{
+          "description":"Task start time",
+          "type":"string",
+          "format":"dateTime"
+        },
+        "ExpectEndTime":{
+          "description":"Estimated task completion time",
+          "type":"string",
+          "format":"dateTime"
+        },
+        "Status":{
+          "description":"status. 1: queuing; 2: executing; 3: suspended; 4: completed; 9: other",
+          "enum":["1","2","3","4","9"]
+        },
+        "ConsumeTime":{
+          "description":"The effective time the task has been executed, in seconds",
+          "type":"number",
+          "format":"integer"
+        },
+        "Progress":{
+          "description":"Task progress percentage",
+
+```
+
+```
+
+        "type": "number",
+        "format": "integer",
+        "minimum": 0,
+        "maximum": 100
+      }
+    },
+    "required": ["TaskID", "CommitTime", "BeginTime", "Status"]
+  }
+}
+}
+
+```
+
+#### A.2.21 /schema/task-control
+
+```
+
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "http://www.itu.int/schema/task-control",
+  "description": "Structure definition of analysis task control",
+  "type": "object",
+  "properties" : {
+    "TaskID": {
+      "description": "Task ID",
+      "$ref": "/schema/components#/$defs/basicObjectId"
+    },
+    "Control": {
+      "description": "Task control code. 1: create task; 2: Start task;
+3: pause task; 4: continue task; 5: modify task parameters; 6: abort task; 9:
+other",
+      "enum": ["1", "2", "3", "4", "5", "6", "9"]
+    }
+  },
+  "required": ["TaskID", "Control"]
+}
+
+```
+
+# Bibliography
+
+- [b-REST] *Architectural Styles and the Design of Network-based Software Architecture  
+CHAPTER 5: Representation State Transfer.*
+- [b-JSON-1] *JSON Schema: A Media Type for Describing JSON Documents.* <http://json-schema.org/draft/2020-12/json-schema-core.html>
+- [b-JSON-2] *JSON Schema Validation: A Vocabulary for Structural Validation of JSON.* <http://json-schema.org/draft/2020-12/json-schema-validation.html>
+- [b-JSON-3] *Understanding JSON Schema.* <http://json-schema.org/understanding-json-schema>
+
+
+
+# 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/H/T-REC-H.627.4-202512-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..985ce4f109b67d2faa0bfb4095195a8c8daeb31f
--- /dev/null
+++ b/marked/H/T-REC-H.627.4-202512-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:df1fd24c75458ea11a4825ba5d66828f9be3dd9f00ac276be6c1bcb17fce8e9f
+size 7269
diff --git a/marked/H/T-REC-H.627.4-202512-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg b/marked/H/T-REC-H.627.4-202512-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ede24890c749c87b28be21afda5c3c68268018ac
--- /dev/null
+++ b/marked/H/T-REC-H.627.4-202512-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:21f5cc76ffc3162029e529a2d1dd8879582cc7b3917c6415f5f51c1301ca391c
+size 16326
diff --git a/marked/H/T-REC-H.627.4-202512-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/H/T-REC-H.627.4-202512-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5b556b7b77a580a31bd1094d7b1f2cf75b41f548
--- /dev/null
+++ b/marked/H/T-REC-H.627.4-202512-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ef38ecc0d63a87cf42874926c310b1aab4c07d60a8f39df5f7687ab7f8e4aa02
+size 86045
diff --git a/marked/H/T-REC-H.643.1-201905-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/H/T-REC-H.643.1-201905-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..591bf92736868db907403c6f60d66b510e9a408b
--- /dev/null
+++ b/marked/H/T-REC-H.643.1-201905-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:60568c8a191ccc5d2e6f23167daa17ea5fedba093b3a6fc875e61f5973b23b73
+size 44972
diff --git a/marked/H/T-REC-H.643.1-201905-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.643.1-201905-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ec5b983e3fb25669841b667867a819fc81d26071
--- /dev/null
+++ b/marked/H/T-REC-H.643.1-201905-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e5fac2728bb91c97ce467edd0f7d87cc887f3ea1d8f1b1145e57827e9e049943
+size 7004
diff --git a/marked/H/T-REC-H.643.1-201905-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg b/marked/H/T-REC-H.643.1-201905-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..868e65ce566a943b452a99c22c23a0b4416dd2da
--- /dev/null
+++ b/marked/H/T-REC-H.643.1-201905-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5ee13d27ae1fdc8dba43548ce3d7890236ae97440cac7fe042e338987d2cd82e
+size 49623
diff --git a/marked/H/T-REC-H.643.1-201905-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/H/T-REC-H.643.1-201905-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..50c8fd5db9c76cf552824935c8d52c75e9a107de
--- /dev/null
+++ b/marked/H/T-REC-H.643.1-201905-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1e057f06901c23099fef0ae07fc6a57fc5dd9e39b3b20c6b6b5e53acb33a2935
+size 45123
diff --git a/marked/H/T-REC-H.643.1-201905-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/H/T-REC-H.643.1-201905-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ef185f25bf9d2576366123c9f92f595ebd1be22e
--- /dev/null
+++ b/marked/H/T-REC-H.643.1-201905-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:012c4854826335ea74a495ae42f7cd972eaa747fb1ddfec9b72457a444ba1d54
+size 81031
diff --git a/marked/H/T-REC-H.643.1-201905-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg b/marked/H/T-REC-H.643.1-201905-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..951ff266184e455e5ce606eaefef45b7b92a80a8
--- /dev/null
+++ b/marked/H/T-REC-H.643.1-201905-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:59746ce528a763a35fbd8e97b13ab03f11232b0e848547ed5195ebfcaaba599a
+size 43958
diff --git a/marked/H/T-REC-H.643.1-201905-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/H/T-REC-H.643.1-201905-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d4c12a8f452ee9685f75f9e58d51d098420c7414
--- /dev/null
+++ b/marked/H/T-REC-H.643.1-201905-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:27d8d721ff0dfcf78c2da88665b61ddc4bad8002908907dba8191bacd7dd3362
+size 38884
diff --git a/marked/H/T-REC-H.643.1-201905-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg b/marked/H/T-REC-H.643.1-201905-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b00f759794d411cc68e100d9b74eb46471bf9a14
--- /dev/null
+++ b/marked/H/T-REC-H.643.1-201905-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9abff97a30dd38dd9c6cc7eebc432adab7306fd83e68c452bab36ef4e658fe42
+size 153449
diff --git a/marked/H/T-REC-H.643.1-201905-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg b/marked/H/T-REC-H.643.1-201905-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..19fd5dd814f624dad4f15b1f60947b771b443424
--- /dev/null
+++ b/marked/H/T-REC-H.643.1-201905-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:72e771114558b1ae28ef3d539c6e851fa4297a15a6ca961a65ab2d0b9f109a55
+size 90250
diff --git a/marked/H/T-REC-H.643.2-202512-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/H/T-REC-H.643.2-202512-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb
--- /dev/null
+++ b/marked/H/T-REC-H.643.2-202512-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3763acd7a0ed56aa30f3f90468c1fb0cb54573eb9045bca3eddf8976b4f0f41d
+size 7219
diff --git a/marked/H/T-REC-H.643.2-202512-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg b/marked/H/T-REC-H.643.2-202512-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3fc0de6c37e0d28e204f6d37fdb6508eb57816ca
--- /dev/null
+++ b/marked/H/T-REC-H.643.2-202512-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8e75c36190ec2ef181186e6af8e1f120ffb814bfcb3e3a5590f3d6cf67a69ee1
+size 41809
diff --git a/marked/H/T-REC-H.643.2-202512-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg b/marked/H/T-REC-H.643.2-202512-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e0015a8e821ba6c3d22e229d4144dbadadda7dde
--- /dev/null
+++ b/marked/H/T-REC-H.643.2-202512-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c3a1708167f3f23699388713746965515cf72682cec1f8d5a2fa326427cb5b1f
+size 105889
diff --git a/marked/H/T-REC-H.643.2-202512-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg b/marked/H/T-REC-H.643.2-202512-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..60de6eda72dade83aab2f7c2d69f5602a278a1e6
--- /dev/null
+++ b/marked/H/T-REC-H.643.2-202512-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:146ddfea3312ed4cd2725557c508d4cb9375e55eb25e5bd778956bc87e0e9291
+size 74330
diff --git a/marked/H/T-REC-H.643.2-202512-I_PDF-E/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/marked/H/T-REC-H.643.2-202512-I_PDF-E/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c147a8e1a3f8b546afa4e03574f3affbde01c725
--- /dev/null
+++ b/marked/H/T-REC-H.643.2-202512-I_PDF-E/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c53bcf79c939c33c558c89acea82aae735a0b707f96a4197a4cecfad67baa63c
+size 17710
diff --git a/marked/H/T-REC-H.643.2-202512-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/H/T-REC-H.643.2-202512-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fbaa9fa18db1959cb7529cecd293a8fec7f6d8a4
--- /dev/null
+++ b/marked/H/T-REC-H.643.2-202512-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:507d2391953476f3d6f22ef390292ebb3c84ff1cf7323e2a1ca2aac4534bae0b
+size 20050
diff --git a/marked/H/T-REC-H.643.2-202512-I_PDF-E/c036e2540a94b31357ceb0002f0cacab_img.jpg b/marked/H/T-REC-H.643.2-202512-I_PDF-E/c036e2540a94b31357ceb0002f0cacab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a4d107ee4865264f8c08ed8269725f5235580e6f
--- /dev/null
+++ b/marked/H/T-REC-H.643.2-202512-I_PDF-E/c036e2540a94b31357ceb0002f0cacab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:307cca04ff728961e7c18a084474f30c7920284b20f9e2f817cee95c303a318a
+size 20823
diff --git a/marked/H/T-REC-H.643.2-202512-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg b/marked/H/T-REC-H.643.2-202512-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9c3793e4dcb3c69277a6dfbdd4f475c5f8dda701
--- /dev/null
+++ b/marked/H/T-REC-H.643.2-202512-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e53248265c38279a8c022275e17f5ff8bbc8cae3f31691a469deffd663f9d734
+size 55277
diff --git a/marked/H/T-REC-H.643.2-202512-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.643.2-202512-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3d5504847d275ae6061e6d09a082775685e57b57
--- /dev/null
+++ b/marked/H/T-REC-H.643.2-202512-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fa12af3f49db56317ae4eb7748921b0c1a2b7af7b568406be9b5d797010a29db
+size 36470
diff --git a/marked/H/T-REC-H.643.2-202512-I_PDF-E/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/marked/H/T-REC-H.643.2-202512-I_PDF-E/e9d825d87c5f85c8dba0664eace96ef4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d82a73d7a909597450da5fcff89fddd2350f3006
--- /dev/null
+++ b/marked/H/T-REC-H.643.2-202512-I_PDF-E/e9d825d87c5f85c8dba0664eace96ef4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8fed8ebbc281e642132974eeaf6e6456c35c28681d4ac1271bff5f7cac339086
+size 44633
diff --git a/marked/H/T-REC-H.643.2-202512-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg b/marked/H/T-REC-H.643.2-202512-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4e3c9085a7804e3fd26bc4c9905dc0ed0e2c046f
--- /dev/null
+++ b/marked/H/T-REC-H.643.2-202512-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:172907da34528820cf08266e5f26f7573359665ed843814870e9f626d1f91488
+size 98256
diff --git a/marked/H/T-REC-H.643.2-202512-I_PDF-E/raw.md b/marked/H/T-REC-H.643.2-202512-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..40923ccfe11bc66fbb80fab5b455c2296623e22d
--- /dev/null
+++ b/marked/H/T-REC-H.643.2-202512-I_PDF-E/raw.md
@@ -0,0 +1,657 @@
+
+
+# Recommendation**ITU-T H.643.2 (12/2025)**
+
+SERIES H: Audiovisual and multimedia systems
+
+Broadband, triple-play and advanced multimedia services –  
+Content delivery and ubiquitous sensor network applications
+
+---
+
+### **Requirements and architecture for information-centric networking (ICN)-based mobile multimedia services**
+
+![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        |
+| 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        |
+| <b>Content delivery and ubiquitous sensor network applications</b> | <b>H.640-H.649</b> |
+| 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.643.2
+
+# Requirements and architecture for information-centric networking (ICN)-based mobile multimedia services
+
+## Summary
+
+Multimedia content is becoming dominant in the Internet, and the significant amount of the traffic in mobile networks is multimedia. Information-centric networking (ICN) offers increased flexibility, higher efficiency and improved user satisfaction in various multimedia services by using the information-centric paradigm, which is focused on the named content, rather than having to reference a specific and physical location of the content. Recommendation ITU-T H.643.2 describes requirements and functional architecture for ICN-based mobile multimedia services to deliver multimedia content in an efficient, scalable, secure and collaborative manner.
+
+## History\*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T H.643.2  | 2025-12-14 | 21          | 11.1002/1000/16603 |
+
+## Keywords
+
+ICN, information-centric networking, mobile multimedia services.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <https://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                                       | 2    |
+| 4 Abbreviations and acronyms .....                                                  | 2    |
+| 5 Conventions .....                                                                 | 2    |
+| 6 Generic requirements for ICN-based mobile multimedia services.....                | 2    |
+| 7 Functional architecture for ICN-based mobile multimedia services .....            | 4    |
+| 7.1 Overview .....                                                                  | 4    |
+| 7.2 Common functions of ICN-enabled nodes .....                                     | 5    |
+| 7.3 Functional entities .....                                                       | 6    |
+| 7.4 ICN forwarding module in the ICN-enabled node .....                             | 7    |
+| 7.5 Content routing.....                                                            | 9    |
+| 7.6 Content request and retrieval operation.....                                    | 10   |
+| 7.7 Mobility support for seamless multimedia services .....                         | 13   |
+| 7.8 Support of quality of service and quality of experience.....                    | 14   |
+| 8 Procedures for ICN-based mobile multimedia services using an overlay network..... | 14   |
+| 8.1 Content registration procedure for the IBS .....                                | 14   |
+| 8.2 Content registration procedure for the IMD .....                                | 15   |
+| 8.3 Content retrieval procedure .....                                               | 15   |
+| 9 Security considerations .....                                                     | 16   |
+| Appendix I – Content naming structure.....                                          | 17   |
+| Bibliography.....                                                                   | 18   |
+
+
+
+# Recommendation ITU-T H.643.2
+
+## Requirements and architecture for information-centric networking (ICN)-based mobile multimedia services
+
+# 1 Scope
+
+This Recommendation specifies the requirements and functional architecture for information-centric networking (ICN)-based mobile multimedia services. The scope of this Recommendation is as follows:
+
+- Generic requirements for ICN-based mobile multimedia services;
+- Functional architecture for ICN-based mobile multimedia services including overall architecture, common functions of ICN-enabled nodes, functional entities, ICN forwarding module, content routing, content request and retrieval procedure, and mobility and quality of service (QoS)/quality of experience (QoE) support;
+- Procedures for ICN-based mobile multimedia services;
+- Security considerations.
+
+# 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.3071](#)] Recommendation ITU-T Y.3071 (2017), *Data aware networking (information centric networking) – Requirements and capabilities*.
+
+[[ITU-T Y.3072](#)] Recommendation ITU-T Y.3072 (2019), *Requirements and capabilities of name mapping and resolution for information-centric networking in IMT-2020*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following term defined elsewhere:
+
+**3.1.1 information-centric networking (ICN)** [b-ITU-T Y.3077]: A new approach to networking where named objects (not only devices) are the principal components for the network. Named data objects can be stored in network nodes (with caching capability) distributed throughout the network. Data objects are transmitted by using names to requesting consumers from any network node that can provide requested data. Locations of the nodes that store data objects in their caches are irrelevant to consumers because they send their requests for data objects by using names (not the data object locations).
+
+NOTE – ICN is an alias for data aware networking (DAN) [b-ITU-T Y.3033]. Example implementations of ICN are content-centric networking (CCN) [b-IETF RFC 8569] and named data networking (NDN) [b-Zhang].
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 ICN-enabled node:** A network node that is capable of supporting information-centric networking (ICN) functionalities.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                                       |
+|------|-------------------------------------------------------|
+| CDN  | Content Delivery Network                              |
+| CLMD | Content Lookup and Metadata Distribution              |
+| CS   | Content Storage                                       |
+| CSI  | Content Storage Index                                 |
+| CSR  | Content Storage Repository                            |
+| D2D  | Device-to-Device Communication                        |
+| FIB  | Forwarding Information Base                           |
+| IBS  | Information-centric-networking-enabled Base Station   |
+| ICN  | Information-Centric Networking                        |
+| ICS  | Information-centric-networking-enabled Content Server |
+| IMD  | Information-centric-networking-enabled Mobile Device  |
+| IR   | Information-centric-networking-enabled Router         |
+| NAT  | Number of Accessed Times                              |
+| PRT  | Pending Request Table                                 |
+| QoE  | Quality of Experience                                 |
+| QoS  | Quality of Service                                    |
+| TL   | Time-to-Live                                          |
+
+# 5 Conventions
+
+In this Recommendation:
+
+- The keywords "is required" 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.
+
+# 6 Generic requirements for ICN-based mobile multimedia services
+
+ICN is a new networking paradigm to provide more efficient, scalable, secure and collaborative multimedia communications than the traditional host-centric networking paradigm. ICN can be used to reduce the time to access multimedia content and provide seamless and ubiquitous user experiences by allowing users to easily send and receive multimedia content in the network including mobile wireless networks.
+
+ICN can also be used to avoid congestion in the network and reduce content delivery latency by content caching in ICN-enabled nodes. The content is requested by content request packets, and the requested content is delivered using response packets. ICN will be useful in ensuring the security
+
+[ITU-T Y.3071] of content by including a security field in the content response packet format and allowing users to express their preference in the types of content.
+
+ICN is based on the use of the content name for delivering the requested content rather than the location. Typically, in IP-based networks, users request the desired content by using the actual address (i.e., IP address) of the content provider that contains the requested content. In ICN, users request the content by using the name of the content, and the content provider delivers the requested content using the given content name [ITU-T Y.3072].
+
+ICN applications may run over multiple wireless interfaces, and one of the multiple interfaces can be selected for content delivery services considering network conditions, or available multiple interfaces can be used at the same time to increase the transmission efficiency and reduce the content delivery time.
+
+Generic requirements for ICN-based mobile multimedia services are described as follows:
+
+- For information-centric multimedia services in mobile networks, it is required that the architecture provide mechanisms to store, register and find multimedia content, and deliver the requested multimedia content using the caching capability of ICN-enabled nodes such as mobile devices and network equipment.
+- It is required that the content request packet be forwarded by using a unique content name included in a well-defined content request packet format.
+- It is required that an optimal network interface be selected for fast and efficient multimedia content request and delivery.
+- It is required that seamless multimedia content delivery services be provided even while in motion.
+- It is required that the architecture be designed to provide fault-tolerant solutions in cases where some nodes fail to deliver the requested multimedia content.
+- It is required that a unified user-friendly content naming scheme be provided. The detailed example structure of a content naming mechanism is described in Appendix I.
+- It is recommended that a content owner register its multimedia content to a content registrar entity for fast content lookup and distribution.
+- It is recommended that the architecture be able to interoperate with the architecture and mechanisms of existing content delivery systems, e.g., content delivery network (CDN).
+- It is recommended that the architecture be lightweight, scalable and flexible to accommodate emerging multimedia applications and services.
+- It is recommended that the architecture provide a multimedia content advertisement capability for future multimedia content discovery and retrieval.
+- It is recommended that the architecture allow the user to obtain the multimedia content from the optimal location considering the user's environment for fast and timely services.
+- It is recommended that the architecture ensure the privacy of the communicating entities, the secure delivery of the multimedia content and the delivery of trusted content.
+- It is recommended that available multiple interfaces be used at the same time to increase transmission efficiency and reduce the multimedia content delivery time.
+
+# 7 Functional architecture for ICN-based mobile multimedia services
+
+## 7.1 Overview
+
+Figure 1 shows the reference network for ICN-based mobile multimedia services. The network is comprised of various ICN-enabled nodes including ICN-enabled base stations (IBS), ICN-enabled routers (IRs), ICN-enabled content servers (ICSSs), ICN-enabled mobile devices (IMDs), and ICN
+
+controllers. These components are equipped with ICN capabilities. The IMDs are connected to the IBSs. The IBSs are connected to the IRs, and the ICSs are also connected to the IRs. The IMDs may communicate with each other when the device-to-device (D2D) communication capabilities are available.
+
+![Figure 1: Reference network for ICN-based mobile multimedia services. The diagram shows a central ICN backbone network cloud containing IRs (routers) and caches. Three ICSs (content servers) are connected to the backbone. Two ICN controllers are also connected to the backbone. Below the backbone are three mobile access networks (1, 2, and N). Each access network contains IBSs (base stations) and caches. IMDs (mobile devices) are connected to the IBSs and can also communicate directly with each other (D2D). A legend on the right defines the icons: IMD (ICN-enabled mobile device), IR (ICN-enabled router), IBS (ICN-enabled base station), ICS (ICN-enabled content server), and a cylinder icon for ICN-enabled cache. The label H.643.2(25) is in the bottom right corner.](f4fdd410cdb84df81274da55721e56fb_img.jpg)
+
+Figure 1: Reference network for ICN-based mobile multimedia services. The diagram shows a central ICN backbone network cloud containing IRs (routers) and caches. Three ICSs (content servers) are connected to the backbone. Two ICN controllers are also connected to the backbone. Below the backbone are three mobile access networks (1, 2, and N). Each access network contains IBSs (base stations) and caches. IMDs (mobile devices) are connected to the IBSs and can also communicate directly with each other (D2D). A legend on the right defines the icons: IMD (ICN-enabled mobile device), IR (ICN-enabled router), IBS (ICN-enabled base station), ICS (ICN-enabled content server), and a cylinder icon for ICN-enabled cache. The label H.643.2(25) is in the bottom right corner.
+
+**Figure 1 – Reference network for ICN-based mobile multimedia services**
+
+In the original ICN architecture, the ICN-enabled nodes independently perform content caching and packet forwarding regardless of the caching and forwarding strategies of the neighbouring ICN-enabled nodes. The inefficient use of content storage may be due to duplicate content stored in the ICN-enabled nodes. Besides this, traditional forwarding strategies may result in the waste of network bandwidth by flooding the content request packets to find the ICN-enabled nodes that contain the requested multimedia content. To avoid the inefficient use of content storage and the waste of network bandwidth, a coordinator called an ICN controller can be used.
+
+The IMDs can exchange the multimedia content with other IMDs as well as nearby IBSs. The IRs can also communicate with the IBSs to provide fast and efficient multimedia content delivery. If there is still no requested multimedia content available in the IRs, then the content request packet is forwarded to the ICS.
+
+The more detailed functions of the individual component in Figure 1 are described in the following clauses.
+
+## 7.2 Common functions of ICN-enabled nodes
+
+The ICN-enabled nodes have several common functions as illustrated in Figure 2. These functions include the ICN forwarding module, network interfaces, and the content lookup and metadata distribution (CLMD) module. The CLMD module incorporates a content management function and finger table.
+
+![Diagram of common functions of ICN-enabled nodes. The diagram shows three main components: ICN Forwarding module, Network interfaces, and CLMD module. The ICN Forwarding module contains Forwarding information base, Pending request table, Content storage, and Forwarding function. The CLMD module contains Content management function and Finger table.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+```
+
+graph TD
+    subgraph ICN_Forwarding_module [ICN Forwarding module]
+        FIB[Forwarding information base]
+        PRT[Pending request table]
+        CS[Content storage]
+        FF[Forwarding function]
+    end
+    NI[Network interfaces]
+    subgraph CLMD_module [CLMD module]
+        CMF[Content management function]
+        FT[Finger table]
+    end
+  
+```
+
+H.643.2(25)
+
+Diagram of common functions of ICN-enabled nodes. The diagram shows three main components: ICN Forwarding module, Network interfaces, and CLMD module. The ICN Forwarding module contains Forwarding information base, Pending request table, Content storage, and Forwarding function. The CLMD module contains Content management function and Finger table.
+
+**Figure 2 – Common functions of ICN-enabled nodes**
+
+The ICN forwarding module consists of a forwarding information base (FIB), pending request table (PRT), content storage and forwarding function. It supports core ICN operations, including multimedia content segmentation into uniquely identifiable chunks, receiver-driven content delivery, in-network caching and name-based routing. The detailed description of the ICN forwarding module is provided in clause 7.4.
+
+Network interfaces are used for forwarding the content request packets and delivering the content response packets. Appropriate network interfaces are selected depending on the situation.
+
+The CLMD module manages the metadata of the multimedia content stored in the IMDs, IBSs and IRs and performs the discovery of the ICN-enabled nodes that contain the requested multimedia content. The ICN-enabled nodes may enable efficient content delivery by assigning the content request packets to multiple interfaces, thereby providing enhanced multimedia experience for users. An ICN-enabled node can communicate with other ICN-enabled nodes. It also performs content dissemination, segmentation, integration, interaction and recognition, enabling each ICN-enabled node to act as an independent source of cached content. This capability allows for reduced content delivery latency, even in highly mobile environments.
+
+The content management function disseminates information about the locally stored multimedia content in an ICN-enabled node to neighbouring ICN-enabled nodes. This facilitates multimedia content retrieval by enabling these nodes to send content request packets directly to the appropriate ICN-enabled nodes. Furthermore, the ICN-enabled nodes in proximity can exchange content information and cooperate in delivery.
+
+The finger table is a data structure designed to optimize multimedia content routing and retrieval. Each ICN-enabled node maintains a finger table containing references to peer nodes likely to cache multimedia content items. Upon receiving a content request packet, an ICN-enabled node consults its finger table to identify candidate nodes that may store the requested multimedia content. The request is forwarded accordingly and may be further propagated based on each node's finger table until the multimedia content is located. Once retrieved, the multimedia content is delivered to the original requester, with caching optionally performed along the delivery path. The use of finger tables enhances the scalability and efficiency of content retrieval by leveraging both network topology and content popularity.
+
+## 7.3 Functional entities
+
+### 7.3.1 ICN-enabled base station
+
+The IBS serves as a key access point in the ICN-based mobile multimedia service architecture, bridging IMDs with the broader ICN infrastructure.
+
+Each IBS is equipped with the CLMD module, which manages local content metadata and facilitates the discovery of cached content across neighbouring IBSs and IMDs.
+
+The IBS supports name-based content forwarding and in-network caching functionalities defined by the ICN paradigm, enabling efficient content dissemination and retrieval. It can perform intelligent forwarding decisions by referencing a local FIB and coordinating with adjacent nodes to avoid redundant content storage.
+
+Additionally, the IBS is capable of interacting with IRs and ICS for upstream content delivery when local retrieval fails. In scenarios where no centralized ICN controller is deployed, the IBS assumes responsibility for metadata distribution and localized caching coordination.
+
+Furthermore, with support for D2D communication, IBSs enhance media delivery performance by facilitating direct content exchange among nearby IMDs.
+
+Through these capabilities, the IBS significantly improves content availability, reduces delivery latency and optimizes network bandwidth usage in mobile ICN environments.
+
+### 7.3.2 ICN-enabled router
+
+An IR is a core forwarding device equipped with ICN capabilities, including content caching, name-based routing and chunk-level content delivery.
+
+The IR architecture integrates the FIB, PRT and CS, enabling it to perform key ICN functions such as content segmentation, in-network storage and receiver-driven data retrieval.
+
+Acting as an intermediate node, the IR facilitates scalable and efficient content dissemination by dynamically assigning content request packets to multiple routing interfaces. It is capable of interacting with neighbouring IRs and IBSs to locate and retrieve the requested content.
+
+The IR supports content assembly, dissemination and interaction with adjacent nodes, and can operate autonomously as a content source through local caching. This allows IRs to enhance media delivery performance and reduce retrieval latency across heterogeneous ICN-based network environments.
+
+### 7.3.3 ICN-enabled mobile device
+
+An IMD is a user-operated terminal that incorporates core ICN functionalities, consistent with the general architecture of an ICN-enabled device.
+
+The IMD includes an ICN forwarding module responsible for name-based routing, packet forwarding and content caching. It also incorporates the CLMD module, which manages metadata associated with locally cached content. Through its content management function, the IMD can notify physically connected IBSs of the availability of stored content, enabling IBSs to request and retrieve content directly from the IMD.
+
+Furthermore, when D2D communication capabilities are available, IMDs can exchange content directly with neighbouring devices, bypassing the need for infrastructure-based relays. This design enhances content delivery efficiency, supports seamless content dissemination in mobile environments and contributes to the scalability and responsiveness of ICN-based networks.
+
+### 7.3.4 ICN controller
+
+The ICN controller is divided into monitoring and control modules. The architecture is shown in Figure 3.
+
+The monitoring modules periodically receive the location of IMDs, content popularity, network condition and the content list from IBSs and IMDs. This information is sent out to the control modules.
+
+The mobility handler predicts the position of IMDs in the near future based on the location of the IMD, and the preferable contents predictor selects the popular content based on the content popularity.
+
+Next, the CS manager determines the content to be stored in IBSs, and the FIB manager determines the interface of IBSs to forward the content request packets.
+
+![Figure 3: Structure of the ICN controller. The diagram shows a 'Control module' containing 'Mobility handler' and 'Preferable content predictor'. These are connected via dashed arrows to a 'CS manager' and 'FIB manager' box. Below this is a 'Monitoring module' containing four boxes: 'IMD Location', 'Content popularity', 'Network condition', and 'Content list in the CS'. These are also connected via dashed arrows to the 'CS manager' and 'FIB manager' box. On the right, a vertical bar labeled 'ICN-enabled nodes' receives arrows from the 'CS manager' and 'FIB manager'. The label 'H.643.2(25)' is at the bottom right.](4e4be0bd8b235167902f2c03e41da651_img.jpg)
+
+Figure 3: Structure of the ICN controller. The diagram shows a 'Control module' containing 'Mobility handler' and 'Preferable content predictor'. These are connected via dashed arrows to a 'CS manager' and 'FIB manager' box. Below this is a 'Monitoring module' containing four boxes: 'IMD Location', 'Content popularity', 'Network condition', and 'Content list in the CS'. These are also connected via dashed arrows to the 'CS manager' and 'FIB manager' box. On the right, a vertical bar labeled 'ICN-enabled nodes' receives arrows from the 'CS manager' and 'FIB manager'. The label 'H.643.2(25)' is at the bottom right.
+
+**Figure 3 – Structure of the ICN controller**
+
+## 7.4 ICN forwarding module in the ICN-enabled node
+
+Each ICN-enabled node in the network has an ICN forwarding module which is composed of three basic functional elements for ICN: CS, FIB and PRT.
+
+### 7.4.1 Content storage
+
+The CS maintains the relationship between the content name and stored content at the local cache of an ICN-enabled node.
+
+In the architecture, the CS is divided into two elements: CS index (CSI) and CS repository (CSR). The CSI holds the content name, content memory pointer to the CSR, the time-to-live (TL), and the number of accessed times (NAT). The CSR holds the corresponding content only. The traditional CS is extended to increase the flexibility of content management and content replacement.
+
+The basic structure of CS is shown in Figure 4. The CS also uses a content replacement policy and a content decision policy to determine the content to be stored and retrieved considering the network resources or storage utilization.
+
+![Figure 4: Content store (CS). The diagram shows a 'CS' box containing 'CSI' and 'CSR'. The 'CSI' is a table with columns 'Name', 'Pointer', 'TL', and 'NAT'. The 'CSR' is a cylinder containing three entries: '../v1/s1', '../v1/s2', and '../v1/s3'. Arrows from the 'Pointer' column in the 'CSI' point to the entries in the 'CSR'. The label 'H.643.2(25)' is at the bottom right.](e9d825d87c5f85c8dba0664eace96ef4_img.jpg)
+
+| CSI                                   |         |    |     | CSR      |
+|---------------------------------------|---------|----|-----|----------|
+| Name                                  | Pointer | TL | NAT |          |
+| /prefix.xyz1.xyz/videos/xy.mpeg/V1/S1 | ●       |    |     | ../v1/s1 |
+| /prefix.xyz1.xyz/videos/xy.mpeg/V1/S2 | ●       |    |     | ../v1/s2 |
+| /prefix.xyz1.xyz/videos/xy.mpeg/V1/S3 | ●       |    |     | ../v1/s3 |
+
+Figure 4: Content store (CS). The diagram shows a 'CS' box containing 'CSI' and 'CSR'. The 'CSI' is a table with columns 'Name', 'Pointer', 'TL', and 'NAT'. The 'CSR' is a cylinder containing three entries: '../v1/s1', '../v1/s2', and '../v1/s3'. Arrows from the 'Pointer' column in the 'CSI' point to the entries in the 'CSR'. The label 'H.643.2(25)' is at the bottom right.
+
+**Figure 4 – Content store (CS)**
+
+NOTE – Various content naming conventions can be used to identify content names in the name field in Figure 4. An example of hierarchical content naming is /prefix.xyz1.xyz/videos/xy.mpeg/V1/S1. The detailed example structure of the content naming is described in Appendix I. This note is also applicable to the name field of FIB and PRT described in clauses 7.4.2 and 7.4.3, respectively.
+
+### 7.4.2 Forwarding information base
+
+The FIB contains the necessary information to forward a content request packet to the appropriate next hop, which is similar to the routing table of the host-based network architecture.
+
+Each ICN-enabled node in the network may have multiple network interfaces and each of these interfaces is considered a face.
+
+The basic structure of FIB is shown in Figure 5. The FIB contains the next hop interface IDs for each item of reachable content. FIB has a forwarding strategy, e.g., the best-face strategy to determine how to forward the content request packet to increase the network performance and efficiency.
+
+![Diagram of the Forwarding Information Base (FIB) table structure.](bd671b21db63e6fdb2196e9b18502aac_img.jpg)
+
+The diagram shows a table titled "FIB" with two columns: "Name" and "Interface". The table contains two entries: one for "/prefix.xyz1.xyz/videos" pointing to interface "1", and another for "/prefix.xyz1.xyz/audio" pointing to interface "2". The text "H.643.2(25)" is located below the table.
+
+| Name                    | Interface |
+|-------------------------|-----------|
+| /prefix.xyz1.xyz/videos | 1         |
+| /prefix.xyz1.xyz/audio  | 2         |
+
+H.643.2(25)
+
+Diagram of the Forwarding Information Base (FIB) table structure.
+
+Figure 5 – Forwarding information base (FIB)
+
+### 7.4.3 Pending request table
+
+The PRT is a fundamental structure to preserve the state of the received request packet. It records all incoming interface IDs for unsatisfied content requests so that it can satisfy the request later as soon as the content is available.
+
+Each PRT entry also holds the TL to maintain its freshness. The basic structure of PRT is shown in Figure 6. Entries are added or modified in the PRT when request packets are received and removed after corresponding content responses are received. A PRT entry may also be removed due to the expiration of TL.
+
+![Diagram of the Pending Request Table (PRT) table structure.](c036e2540a94b31357ceb0002f0cacab_img.jpg)
+
+The diagram shows a table titled "PRT" with three columns: "Name", "Interface", and "LV". The table contains one entry for "/prefix.xyz1.xyz/videos/xy.mpeg/V1/S1" pointing to interface "0". The text "H.643.2(25)" is located below the table.
+
+| Name                                  | Interface | LV |
+|---------------------------------------|-----------|----|
+| /prefix.xyz1.xyz/videos/xy.mpeg/V1/S1 | 0         |    |
+
+H.643.2(25)
+
+Diagram of the Pending Request Table (PRT) table structure.
+
+Figure 6 – Pending request table (PRT)
+
+## 7.5 Content routing
+
+ICN enables content name-based routing without knowing the host address. This means that the contents are disseminated across the network; mobile devices retrieve the desired content by using the appropriate content name; and the content will be provided from the most appropriate content source in terms of distance and storage capacity.
+
+ICN uses a dynamic forwarding strategy so that each ICN-enabled node can make a routing decision in per-packet and hop-by-hop manners for forwarding the content request packet. The ICN routing strategy considers various factors such as congestion and transfer time for deciding a routing path.
+
+### 7.5.1 Message types
+
+ICN uses two types of messages for communication, namely, content request packet and content response packet.
+
+The content request packets are used to request a particular content, and the content provider provides the requested content using the given content name. The content request packets contain the content name and other identifiers, e.g., type, version, author.
+
+The content response packets are used to transmit the requested content to the requester as a response to the content request packet. The content response packets also contain digitally signed information for protecting the content and respecting the content publisher.
+
+The content request packets may contain a content name with a req flag, which implies the content provider needs to reply with the exact content name, content meta data (e.g., content ID, size, content provider, encoding scheme) and path attributes (e.g., bandwidth, hop count) using a content response packet that contains the content name with a special flag dataReq.
+
+### 7.5.2 Content service subscription and publication
+
+Content providers may allow only valid requesters to access and store data by publishing the data items with a valid name.
+
+Each content is assigned a unique attribute according to the category of data items. An ICN-enabled node that intends to publish content injects its name to its local CS and forwards the name to the network based on the scope. In the initial phase, content is published inside the end devices and distributed to other ICN-enabled nodes. The publisher periodically publishes and updates the list of contents it contains.
+
+### 7.5.3 FIB entry manipulation
+
+The FIB prefix is learned in two ways. First, the content provider may broadcast, multicast or unicast the content name or a prefix of a content name to the nearby neighbours. The prefix will eventually reach the core network routers. Second, each ICN-enabled node may learn the FIB prefix by referring to the response of the pending content request packet.
+
+Each router has a limited amount of storage capacity to handle FIB entries. In order to handle the scalability problem of FIB manipulation for a huge amount of real-world content, it is needed to set a storage threshold to a certain value. The storage threshold means that an ICN-enabled node can hold the threshold value of its total storage for FIB manipulation.
+
+The remaining storage is used for FIB updates. When a new FIB entry appears, the storage capacity of the ICN-enabled node will be checked against the threshold, and if it is below the threshold, the entry is injected into the FIB; otherwise, a FIB aggregation is performed, e.g., /prefix.xyz1.xyz/videos and /prefix.xyz1.xyz/audio to /prefix.xyz1.xyz, the storage capacity will be checked again and the new FIB entry is inserted. The network operators or Internet service providers should be aware of prefix aggregation to provide faster, more efficient and scalable content access.
+
+## 7.6 Content request and retrieval operation
+
+The operation of ICN is triggered by making a request specifying the name of the desired content. Any ICN-enabled node that holds the requested content may reply with the data corresponding to the request.
+
+### 7.6.1 Content request and retrieval using broadcast
+
+When the content names are not known in the network or the FIB does not have any prior information regarding the requested content, the content request packet is sent to the nearby ICN-enabled nodes.
+
+#### 7.6.1.1 Content request
+
+Content requesters broadcast a content request packet to nearby IBSs or IMDs using the content name. When IBSs or IMDs receive the content request packet, they look up their CS for the requested content.
+
+If a matching item of content is found, then it will be sent out via the arrival interface as a response to the content request packet. If the matching content is not found in the CS, a lookup is performed in the PRT. If there is an already existing PRT entry for the corresponding content request packet for the same arrival interface, the content request packet is discarded and the lifetime of the PRT entry is updated. If there is an already existing PRT entry for the corresponding content request packet but the arrival interface is different, then the arrival interface is added to the existing PRT interface and the content request packet is discarded. If there is no matching PRT entry, then a lookup is performed in the FIB. If there is a matching entry found in the FIB for the requested content, a new PRT entry is added to the PRT by assigning the lifetime that adjusts the TL of the PRT entry, and the content request packet is forwarded to the interfaces available in the FIB.
+
+A content request packet is forwarded to a single interface in round-robin fashion or using the random probability to reduce the response time for the same content from different providers. It also makes the retrieval of a large volume of multimedia content faster by requesting small chunks of the content from different content providers.
+
+If there is no match found in the FIB, the content request packet is broadcast. The content request packet can be discarded only based on a nonce value that is defined in the content request packet.
+
+#### 7.6.1.2 Content retrieval
+
+Content is delivered back to the content requester using the forwarding route of the content request packet towards the content source.
+
+When a content response packet is received by the IBS or IR, it looks up its CS. If a matching entry for the received content is found on its CS, then it discards the content because the same content was received previously.
+
+If there is no corresponding matching entry in the CS, it looks up its PRT to find any content request unsatisfied for the corresponding content. If there is a match in the PRT, the content is stored in the CS and forwarded to the arrival interfaces in the PRT.
+
+After successful forwarding, the PRT entry is removed. If there is no match found in the PRT, the content is discarded and not processed further.
+
+### 7.6.2 Content request and retrieval using unicast
+
+When the requested content is available throughout the network or the FIB contains the routing information for the content, the content request packet is forwarded to a single face according to the FIB.
+
+#### 7.6.2.1 Content request
+
+In a simple approach, the content request packet may be disseminated to the different content providers, and the same content may be replied back to the content requester using multiple different routes. This will result in the waste of the network resources and increase the network overhead due to the unnecessary content transfer using different routes. To avoid this and to increase the bandwidth efficiency, the following reliable approach is used for the proper route selection.
+
+As shown in Figure 7, content requesters, e.g., IMD, unicast a content request packet to a nearby IBS or IMD with the name of the desired content by adding an additional flag (req) inside the content name. When the IBS or IMD receives the content request packet, it looks up its CS for the requested content. If an exactly matched or a larger prefix matched content is found, then it will be sent out in a content response packet that contains the exact content name with an additional flag dataReq, other
+
+attributes (e.g., size, encoding types) and the route-related information (e.g., bandwidth, current load) via the arrival interface as a response to the content request packet. If the matching content is not found in the CS, a lookup is performed in the PRT. The other operation is similar to the content request functions described in the simple approach.
+
+![Figure 7: Content request and retrieval steps. The diagram illustrates a network architecture with three main components: ICS (Information Center Server), IR (Intermediate Router), and IBS (Internet Base Station). Each component contains a FIB (Forwarding Information Base), PRT (Pending Request Table), and CS (Content Store). The IR and IBS also have 'Faces' interfaces. Two Requesters (IMD) are shown on the right. The process is numbered 1 through 10: 1. Requester 1 sends a request to IBS. 2. IBS checks its CS. 3. IBS checks its PRT. 4. IBS checks its FIB. 5. IBS sends a request to IR. 6. IR checks its CS. 7. IR checks its PRT. 8. IR checks its FIB. 9. IR sends a request to ICS. 10. ICS returns the content to IR, which then forwards it to IBS and then to Requester 1. Requester 2 is shown sending a request to IBS, but the process is not numbered for it.](c85ded401105f62f2d6ff26b3b5eb4af_img.jpg)
+
+Figure 7: Content request and retrieval steps. The diagram illustrates a network architecture with three main components: ICS (Information Center Server), IR (Intermediate Router), and IBS (Internet Base Station). Each component contains a FIB (Forwarding Information Base), PRT (Pending Request Table), and CS (Content Store). The IR and IBS also have 'Faces' interfaces. Two Requesters (IMD) are shown on the right. The process is numbered 1 through 10: 1. Requester 1 sends a request to IBS. 2. IBS checks its CS. 3. IBS checks its PRT. 4. IBS checks its FIB. 5. IBS sends a request to IR. 6. IR checks its CS. 7. IR checks its PRT. 8. IR checks its FIB. 9. IR sends a request to ICS. 10. ICS returns the content to IR, which then forwards it to IBS and then to Requester 1. Requester 2 is shown sending a request to IBS, but the process is not numbered for it.
+
+**Figure 7 – Content request and retrieval steps**
+
+When the core router, e.g., IR receives the content response packet *dataReq* as in Figure 7, it looks up its FIB. If an exactly matching entry for the named content is found in its FIB, then it calculates its current weight value. If the weight value is greater than the previous weight value, then the FIB interface is updated, otherwise the content response packet *dataReq* is discarded. If there is no corresponding matching entry in the FIB, the incoming interface is stored in the FIB with a TL value equal to the half of the normal TL value and a weight value equal to the calculated value, and it is forwarded to the relevant interfaces in the PRT. After successful forwarding, the PRT entry is removed.
+
+#### 7.6.2.2 Content retrieval
+
+Content response packets with the metadata of the content are delivered back to the content requester using the forwarding route of the content request packet to the content source. The other operations are similar to the content retrieval functions described above.
+
+#### 7.6.2.3 Content request and retrieval using a cluster-based approach
+
+In ICN, it is very important to provide efficient and fast content delivery to the users. In this clause, an enhanced cluster-based content access mechanism is described, which accelerates the rapid transmission of the content. The architecture is based on the principles of ICN and incorporates a cluster-based approach for better performance in terms of content retrieval delay and traffic overhead compared with the basic ICN and other content delivery architectures.
+
+The scheme reduces the transmission of content request packets, which are query packets for searching the target content, without sending them repeatedly. This cluster-based forwarding mechanism reduces the time complexity and improves the efficiency of the ICN-based architecture.
+
+The overall procedure makes sure that the capacity of the ICN-based network will be ensured. This scheme does not use any additional equipment to maintain the movement of the content request packets and catch the neighbouring router information, which ensures cost effectiveness. When storing the information about the neighbouring routers and clusters, the intra-cluster caching capability is better than the other existing schemes in terms of the low content retrieval time.
+
+The scheme mainly works based on the improvement of the existing cluster-based approach in ICN. The scheme is divided into the following steps:
+
+- Formation of a cluster;
+- Selection of a cluster head among the scattered IRs;
+- Caching at each IR and the cluster head;
+- Transmission of content request and content response packets.
+
+##### **A Formation of a content cluster**
+
+Clustering is the task of grouping a set of objects in such a way that objects in the same group (called a cluster) are more similar (in some sense or another) to each other than to those in other groups (clusters).
+
+In ICN, a cluster is a group of some routers that can share different types of information, e.g., the neighbouring routers' addresses, their available storage and so on. With the concept of the cluster, the computational and transmission overhead can be reduced.
+
+##### **B Selection of a content cluster head**
+
+The cluster head is the main object of a cluster. The important tasks are done by the cluster head. Every cluster constructs its cluster head using the same mechanism.
+
+##### **C Operation of ICN-enabled routers**
+
+All end user terminals are directly or indirectly connected to an IR. Every IR stores information about the end user terminals.
+
+When a user sends a content request packet towards its connected IR, it will be stored in the IR's internal memory. If another user terminal sends the same content via a content request packet towards its connected IR, the IR first compares it with the information in its internal memory. If a match is found, then the content request packet is discarded. Otherwise, it will forward the content request packet. Ultimately, the previously requested content contained in content response packets will arrive at the IR, and the IR will forward the content response packets towards the second end user whose content request packet was discarded.
+
+In this way, the repeated transmissions of content request packets will be minimized. Since every IR is a member of a cluster and every cluster has a cluster head, every IR must store the information about the head.
+
+###### **D Operation of the cluster heads**
+
+A cluster head contains all the information of the corresponding cluster. Every connected IR is directly connected to the cluster head. It stores all incoming and outgoing information, e.g., content request packets (content requests) and content response packets (responses). It also stores the neighbouring cluster heads' addresses.
+
+## **7.7 Mobility support for seamless multimedia services**
+
+When a mobile device changes its point of attachment due to handover, it should be possible to support mobility for seamless content delivery services.
+
+IBS uses a mobility management mechanism to address content diversity and device diversity. It introduces a context-aware handover prediction mechanism to deal with the heterogeneity of wireless content providers and consumers. Context awareness provides a significant effect to ensure data continuity in the mobile environment. It also uses a content similarity matching mechanism to provide data continuity when high mobility increases the chance of data unavailability.
+
+### 7.7.1 Content consumer mobility support
+
+It has been shown that ICN works well in a network with mobile nodes, but several problems arise with real-time applications when the ICN-enabled nodes become highly mobile and the content size increases.
+
+To support mobility for real-time communication and to guarantee session continuity and reachability, a soft-handover approach can be used where the routing information on the new access network is updated before the original handover occurs. This is almost similar to the follow-me service that is the modern trend of mobile communications. In this approach, the IBS has the capability that measures the traffic rate and the signal strength and can also apply some utility functions to decide whether the user equipment will move to a new IBS access network or not.
+
+If the old IBS detects a possible handover of the UE, it forwards the content name and the related information to the new IBS, and the new IBS forwards the content request to the core network to retrieve the content. If successful, the UE terminates the connection to the old IBS, is attached to the new IBS, and continues to receive the content seamlessly using the new IBS.
+
+### 7.7.2 Content provider mobility support
+
+Content provider mobility allows content sources to be relocated without disrupting content availability.
+
+In order to reduce handover latency and the cost of the content provider mobility in ICN, it uses a soft-handover approach where a new connection is established to a new IBS before breaking the old connection.
+
+Once a handover occurs, the producer will update its prefix to match the new location (e.g., when a producer named: /prefix moves from IBS1 to IBS2, the producer's name will change from /IBS1/prefix to /IBS2/prefix). If the producer changes its attachment point, i.e., IBS, its location name becomes invalid and content requests from the UE and IBS will no longer reach the content source.
+
+As soon as it is assigned a new location name at the new IBS, the IBS updates the binding information. Consumers exploit ICN's multipath forwarding to handle handovers. Due to mobility, if the content name is changed and the producer receives the old named content request message, it can use a similarity matching mechanism to satisfy the content request.
+
+## 7.8 Support of quality of service and quality of experience
+
+In any circumstances, QoS and QoE for content delivery services should be always maintained at a desirable level.
+
+In the ICN communication paradigm, all communications are local and bidirectional, send content request packets and reply with content response packets.
+
+An example of the decision attributes in the content request packet is "The content is more important to me than anything else I have already requested for". Then the important content response packet is sent first rather than sending other content response packets. Any ICN-enabled nodes have the capability to use some QoS/QoE oriented utility functions or decision metrics to select a better route or better experience in terms of bandwidth, delay and cost.
+
+# 8 Procedures for ICN-based mobile multimedia services using an overlay network
+
+This clause provides procedures for ICN-based mobile multimedia services using an overlay network. A logical overlay network is constructed among the IBSs and the IMDs to handle a large number of distributed contents in the IBSs and the IMDs to retrieve the request content in a fast manner.
+
+In the overlay network, all IBSs and content are assigned a unique  $m$ -bit identifier using a consistent hashing function. These identifiers are ordered on an identifier circle modulo  $2^m$ . Figure 8 shows the structure of the overlay network.
+
+![Figure 8: An overlay network with an m-bit identifier (m = 4).](83852ec55d4802521a727926336bedab_img.jpg)
+
+The diagram illustrates the mapping of a physical network to a logical overlay network. On the left, a cloud-like shape represents the physical network containing six IBS (Internet Border Server) nodes (IBS 1 to IBS 6) arranged in a mesh. Five IMD (Internet Device) nodes are connected to specific IBSs: IMD 1 and IMD 2 to IBS 2; IMD 3 to IBS 5; IMD 4 to IBS 4; and IMD 5 to IBS 1. An arrow points to the right, showing the logical mapping onto a circle representing an identifier space modulo 16 (since  $m=4$ ). The circle is marked with identifiers 0 through 15. IBS nodes are placed at specific points: IBS 3 at 0, IBS 6 at 2, IBS 2 at 5, IBS 1 at 8, IBS 4 at 10, and IBS 5 at 13. IMD nodes are also mapped: IMD 3 at 13 (with IBS 5), IMD 1 at 5 (with IBS 2), IMD 2 at 6, IMD 5 at 9, and IMD 4 at 11. The center of the circle is labeled 'ICN network'.
+
+Figure 8: An overlay network with an m-bit identifier (m = 4).
+
+Figure 8 – An overlay network with an  $m$ -bit identifier ( $m = 4$ )
+
+## 8.1 Content registration procedure for the IBS
+
+Figure 9(a) shows the content registration procedure for the IBS. This procedure is activated at the IBS whenever new content is cached at the IBS's CS. The IBS sends a *Content\_Metadata\_Registration* message to the closest successor IBS or the predecessor IBS of the content. This message includes the content's name and metadata such as content ID and IP address of the IBS that has the content. If the IBS receiving the message is the successor of the content ID, it keeps the metadata of the content and completes the content registration. Otherwise, the IBS passes the message to another IBS depending on the content ID.
+
+## 8.2 Content registration procedure for the IMD
+
+Figure 9(b) shows the content registration procedure for the IBS. This procedure is activated at the IMD whenever new content is cached at the IMD's CS. The IMD sends a *D2D\_Content\_Registration* message to the connected IBS. The IBS receiving the message transmits a *D2D\_Content\_Metadata\_Registration* message to the closest successor IBS or predecessor IBS of the content. The remaining procedure is the same as that of the content registration message flow for the IBS.
+
+The *D2D\_Content\_Registration* message includes content name and meta data such as content ID and IP address of the IMD that has the content.
+
+## 8.3 Content retrieval procedure
+
+Figure 9(c) shows the content retrieval procedure. This procedure is activated whenever an IMD requests content from its IBS. The IMD sends a content request packet called *D2D\_Content\_Search* to its IBS. If the IBS receiving the message does not have the metadata of the requested content, it sends a *Content\_Metadata\_Search* message to the appropriate IBS depending upon the content name. If the IBS receiving the message has the content metadata, it transmits a *Content\_Metadata\_Reply* message to the IBS that is connected to the IMD. Otherwise, the IBS passes the message to another IBS depending on the content name.
+
+The *D2D\_Content\_Search* message includes content name and meta data such as the content ID and IP address of the IMD that requests the content. The *Content\_Metadata\_Search* message adds the IP of the IBS to the *D2D\_Content\_Search* message.
+
+![Figure 9: Procedures for ICN-based mobile multimedia services using an overlay network. The figure consists of three sub-diagrams: (a) Content registration procedure for the IBS, (b) Content registration procedure for the IMD, and (c) Content retrieval procedure. Each diagram shows a network of nodes (IBS and others) and an IMD. (a) shows two nodes within an oval network exchanging 'Content_Metadata_Registration' messages. (b) shows an IMD sending a 'D2D_Content_Registration' message to a node, which then sends 'D2D_Content_Metadata_Registration' messages to other nodes. (c) shows an IMD sending a 'D2D_Content_Search' message to a node, which then sends 'Content_Metadata_Search' and 'Content_Metadata_Reply' messages to other nodes. Labels like 'Content caching' and 'Content metadata registration' are present in the diagrams.](812e188283162af0b54fb3e30ffee51b_img.jpg)
+
+(a) Content registration procedure for the IBS
+
+(b) Content registration procedure for the IMD
+
+(c) Content retrieval procedure
+
+H.643.2(25)
+
+Figure 9: Procedures for ICN-based mobile multimedia services using an overlay network. The figure consists of three sub-diagrams: (a) Content registration procedure for the IBS, (b) Content registration procedure for the IMD, and (c) Content retrieval procedure. Each diagram shows a network of nodes (IBS and others) and an IMD. (a) shows two nodes within an oval network exchanging 'Content\_Metadata\_Registration' messages. (b) shows an IMD sending a 'D2D\_Content\_Registration' message to a node, which then sends 'D2D\_Content\_Metadata\_Registration' messages to other nodes. (c) shows an IMD sending a 'D2D\_Content\_Search' message to a node, which then sends 'Content\_Metadata\_Search' and 'Content\_Metadata\_Reply' messages to other nodes. Labels like 'Content caching' and 'Content metadata registration' are present in the diagrams.
+
+**Figure 9 – Procedures for ICN-based mobile multimedia services using an overlay network**
+
+# 9 Security considerations
+
+Content security is provided by incorporating the security features in the content itself, unlike in current networks where trust is with the location of the content or medium. The following characteristics are considered:
+
+- Integrity: Ability to identify the illegal content or have the ability to self-certify the content.
+- Accountability and transparency: Ability for the content to be authenticated and maintain the transparent relation associated with an entity such as an organization.
+
+- Confidentiality and controlled access: Unauthorized access to content should be prohibited using content protection mechanisms.
+- Availability: Ability to make the content available for authorized parties.
+
+# Appendix I
+
+## Content naming structure
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This appendix describes a content naming structure for retrieving the content requested by an information-centric networking (ICN)-enabled node. The main principle of ICN is that the content is accessed using the content name.
+
+With the exponential growth of multimedia content on the Internet, it is difficult to find and organize relevant content in an efficient way. Therefore, it is necessary to provide a well-organized naming scheme that is flexible and provides a low delay in retrieving or identifying the content.
+
+A hierarchical content naming structure can be used for content retrieval as shown in Figure I.1, i.e., "/prefix.xyz1.xyz/videos/xy.mpeg /V<1, 2>/S<1, 2>". The V and S represent version and segment, respectively, and the number of naming components is not limited. It is fully flexible for the content provider and takes the shape in Figure I.1. The ICN content names can also implicitly contain a hash algorithm, e.g., the SHA-256 digest of the content, to provide uniqueness and data integrity.
+
+![A hierarchical content naming structure diagram. The root node is 'prefix.xyz1.xyz'. It branches into 'Video' and 'Audio'. 'Video' branches into 'xy.mpg'. 'xy.mpg' branches into 'V1' and 'V2'. 'V1' branches into 'S1' and 'S2'. 'V2' branches into 'S1' and 'S2'. The label 'H.643.2(25)' is present near the bottom right of the diagram.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg)
+
+```
+graph TD; A[prefix.xyz1.xyz] --> B[Video]; A --> C[Audio]; B --> D[xy.mpg]; D --> E[V1]; D --> F[V2]; E --> G[S1]; E --> H[S2]; F --> G; F --> H;
+```
+
+H.643.2(25)
+
+A hierarchical content naming structure diagram. The root node is 'prefix.xyz1.xyz'. It branches into 'Video' and 'Audio'. 'Video' branches into 'xy.mpg'. 'xy.mpg' branches into 'V1' and 'V2'. 'V1' branches into 'S1' and 'S2'. 'V2' branches into 'S1' and 'S2'. The label 'H.643.2(25)' is present near the bottom right of the diagram.
+
+**Figure I.1 – A content naming structure**
+
+# Bibliography
+
+- [b-ITU-T Y.3033] Recommendation ITU-T Y.3033 (2014), *Framework of data aware networking for future networks*.
+- [b-ITU-T Y.3077] Recommendation ITU-T Y.3077 (2021), *Framework for interworking of heterogeneous application domain connected objects through information-centric networking in IMT-2020*.
+- [b-IETF RFC 8569] IETF RFC 8569 (2019), *Content-Centric Networking (CCNx) Semantics*.
+- [b-Zhang] Lixia Zhang et al. (2014), *Named data networking*, SIGCOMM Computer Communication Review, Vol. 44, No. 3, pp. 66-73.
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.2-201911-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.644.2-201911-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8c94bf101028e47e1092a9f88016d53bfc75d59b
--- /dev/null
+++ b/marked/H/T-REC-H.644.2-201911-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:86fe8f93f8ec914a5fc9f87517c767efcd7ee0659948fc230669bd291872e016
+size 7017
diff --git a/marked/H/T-REC-H.644.2-201911-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/H/T-REC-H.644.2-201911-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3b42053f32800da1cd356bc66d2d3f8b52df284e
--- /dev/null
+++ b/marked/H/T-REC-H.644.2-201911-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cd219934eaf7f76d5136a02ec0b0b71eee5b745301136b1a7cb4cc42d3884373
+size 66194
diff --git a/marked/H/T-REC-H.644.2-201911-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/H/T-REC-H.644.2-201911-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..eee72327215b309bc527bce2b170fe66a81214ed
--- /dev/null
+++ b/marked/H/T-REC-H.644.2-201911-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:efbd474692aa932044175363d9a11683c63d42c658db410fdaf932b3c96b82b5
+size 101657
diff --git a/marked/H/T-REC-H.644.2-201911-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/H/T-REC-H.644.2-201911-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5baa97d5d659545f2b701d54f87861f44c5a004d
--- /dev/null
+++ b/marked/H/T-REC-H.644.2-201911-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d45bd2df436d78bb2042a418469720cfd4ae0b55d64af3d8a5224ae9e13c6699
+size 113411
diff --git a/marked/H/T-REC-H.644.2-201911-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg b/marked/H/T-REC-H.644.2-201911-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..77ef2a06eb3a0dd96dc9ec72d9d9a14c02e6e2dd
--- /dev/null
+++ b/marked/H/T-REC-H.644.2-201911-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a8ee473c912086293dd2aed2e5fe785756c027b9d216adbe64a7f61c7d0d22ab
+size 124049
diff --git a/marked/H/T-REC-H.644.2-201911-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg b/marked/H/T-REC-H.644.2-201911-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ac9748fed92e6be91f36470ca134f371cfb4f118
--- /dev/null
+++ b/marked/H/T-REC-H.644.2-201911-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b4e00995b81ce4d5e8f0261e15e1ba0e5f49341f4fc946790dd08940a7d466a8
+size 46809
diff --git a/marked/H/T-REC-H.644.2-201911-I_PDF-E/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/marked/H/T-REC-H.644.2-201911-I_PDF-E/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ac3ff75644e28662dced7c5a6e363b6e847a1a52
--- /dev/null
+++ b/marked/H/T-REC-H.644.2-201911-I_PDF-E/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:efb1600a8be5b914bec9b56b7abf53a912f4fa55c117c6ae0799d2bf26c84f3b
+size 65354
diff --git a/marked/H/T-REC-H.644.2-201911-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/marked/H/T-REC-H.644.2-201911-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6783e554c18e3d529c6a2128452411dc4ff6275a
--- /dev/null
+++ b/marked/H/T-REC-H.644.2-201911-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:00be1b60765538118299c6815fd167c0e4fd4359d4dcf805f8234a8f2ff1a2bc
+size 82616
diff --git a/marked/H/T-REC-H.644.2-201911-I_PDF-E/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/H/T-REC-H.644.2-201911-I_PDF-E/86b4670fc1a5a694821ee92b99c1209a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5db8806635e10e9a7aac9f44937442041a7ddcc8
--- /dev/null
+++ b/marked/H/T-REC-H.644.2-201911-I_PDF-E/86b4670fc1a5a694821ee92b99c1209a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:34198af92b1c36e39dc85c5545d7f0c776fc8e9f096e8b3dbe7d9c22f01c472b
+size 95250
diff --git a/marked/H/T-REC-H.644.2-201911-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/H/T-REC-H.644.2-201911-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0a3022bb16a8719ae9c7845cbd76de798b16eead
--- /dev/null
+++ b/marked/H/T-REC-H.644.2-201911-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7e25deeb48c2c8100619680f272a1ce3588575b375dc86cb9f000c4f864645cc
+size 30464
diff --git a/marked/H/T-REC-H.644.2-201911-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/H/T-REC-H.644.2-201911-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ea2248421420d81ddb85624933466d0809be9586
--- /dev/null
+++ b/marked/H/T-REC-H.644.2-201911-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7037727af1f2e8cf11d8402c39865ce4024e562b744183ad585a6e01dc7a492b
+size 105234
diff --git a/marked/H/T-REC-H.644.2-201911-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.644.2-201911-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7488725a93142a3230d5bbd77f2b6b11b5048b7c
--- /dev/null
+++ b/marked/H/T-REC-H.644.2-201911-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:41891cb1481a6872bad168d6e926a50ed8ca2e3fbdd978492a8ef6ea073c1c9a
+size 89521
diff --git a/marked/H/T-REC-H.644.2-201911-I_PDF-E/raw.md b/marked/H/T-REC-H.644.2-201911-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..01cda490cb38998d7adcb8facab5279390ce3eaf
--- /dev/null
+++ b/marked/H/T-REC-H.644.2-201911-I_PDF-E/raw.md
@@ -0,0 +1,733 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.644.2**
+
+(11/2019)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Broadband, triple-play and advanced multimedia  
+services – Ubiquitous sensor network applications and  
+Internet of Things
+
+---
+
+**Virtual content delivery network: Network  
+virtualization**
+
+Recommendation ITU-T H.644.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 across 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, 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        |
+| <b>Ubiquitous sensor network applications and Internet of Things</b>                        | <b>H.640–H.649</b> |
+| 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.2
+
+# Virtual content delivery network: Network virtualization
+
+## Summary
+
+Recommendation ITU-T H.644.2 specifies the functional architecture, related functions and functional blocks, and high-level reference points which implement content delivery network (CDN) virtualization by utilizing networking virtualization technologies. Based on the functional architecture and functions, this Recommendation also introduces the various technical solutions of the CDN nodes virtualization utilizing current network virtualization technologies, such as network function virtualization and software-defined networks.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T H.644.2  | 2019-11-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/14111">11.1002/1000/14111</a> |
+
+## Keywords
+
+Content delivery network, network virtualization, software-defined network, virtualization.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                                                       | 2    |
+| 6            | Introduction.....                                                                                       | 3    |
+| 7            | Functions and functional blocks related to network virtualization under VCDN architecture .....         | 4    |
+| 7.1          | Functions and functional blocks in resource control functions .....                                     | 4    |
+| 7.2          | Functions and functional blocks in resource functions .....                                             | 5    |
+| 8            | Network virtualization for VCDN .....                                                                   | 6    |
+| 8.1          | CDN function virtualization coupled with SDN-based solution.....                                        | 6    |
+| 8.2          | CDN node virtualized with the support of network virtualization system .....                            | 9    |
+| 8.3          | CDN node virtualized with the support of network virtualization system and SDN controller.....          | 11   |
+| 8.4          | CDN node virtualized with the support of network virtualization system and virtual SDN controller ..... | 13   |
+| 9            | Reference points .....                                                                                  | 15   |
+| 9.1          | Reference point M' .....                                                                                | 16   |
+| 9.2          | Reference point C' .....                                                                                | 16   |
+| 9.3          | Reference point V' .....                                                                                | 16   |
+| 9.4          | Reference point N1' .....                                                                               | 16   |
+| 9.5          | Reference point N2' .....                                                                               | 16   |
+| 9.6          | Reference point A' .....                                                                                | 16   |
+| 9.7          | Reference point D' .....                                                                                | 16   |
+| Appendix I   | – Use cases of network virtualization supporting VCDN services.....                                     | 17   |
+| I.1          | Virtualized CDN node deploy dynamically and flexibly .....                                              | 17   |
+| I.2          | Smart traffic control .....                                                                             | 18   |
+| I.3          | Rapid service deployment .....                                                                          | 18   |
+| I.4          | Unified configuration and management .....                                                              | 19   |
+| Bibliography | .....                                                                                                   | 20   |
+
+
+
+# Recommendation ITU-T H.644.2
+
+# Virtual content delivery network: Network virtualization
+
+## 1 Scope
+
+This Recommendation specifies the functional architecture, related functions and functional blocks, and high-levelled reference points which support content delivery network (CDN) virtualization by utilizing networking virtualization technologies. This Recommendation also describes the various technical solutions of the CDN nodes virtualization utilizing current network virtualization technologies.
+
+## 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.1] Recommendation ITU-T H.644.1 (2019), *Functional architecture for virtual content delivery networks*.
+
+[ITU-T Y.3300] Recommendation ITU-T Y.3300 (2014), *Framework of software-defined networking*.
+
+[ITU-T Y.3302] Recommendation ITU-T Y.3302 (2017), *Functional architecture of software-defined networking*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 content delivery network** [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 audio) 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.2 logically isolated network partition (LINP)** [b-ITU-T Y.3011]: A network that is composed of multiple virtual resources which is isolated from other LINPs.
+
+**3.1.3 network virtualization** [b-ITU-T Y.3011]: A technology that enables the creation of logically isolated network partitions over shared physical networks so that heterogeneous collection of multiple virtual networks can simultaneously coexist over the shared networks. This includes the aggregation of multiple resources in a provider and appearing as a single resource.
+
+**3.1.4 software-defined networking** [ITU-T Y.3300]: A set of techniques that enables to directly program, orchestrate, control and manage network resources, which facilitates the design, delivery and operation of network services in a dynamic and scalable manner.
+
+**3.1.5 virtual content delivery network** [b-ITU-T F.743.4]: A content delivery network using virtualisation technology that enables the allocation of virtual storage, virtual machines, and network resources according to vendors' requirements in a dynamic and scalable manners.
+
+**3.1.6 virtual resource** [b-ITU-T Y.3011]: An abstraction of physical or logical resource, which may have different characteristics from the physical or logical resource and whose capability may be not bound to the capability of the physical or logical resource.
+
+## **3.2 Terms defined in this Recommendation**
+
+This Recommendation defines the following term:
+
+**3.2.1 network virtualization system:** A software platform or the logical functions collection which can provide the capability of network resource virtualization. Its physical system components can be deployed in a centralized way or geographically distributed way.
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                               |
+|------|-----------------------------------------------|
+| BSS  | Business Support System                       |
+| CDN  | Content Delivery Network                      |
+| CP   | Content Provider                              |
+| GSLB | Global Server Load Balance                    |
+| LINP | Logically Isolated Network Partition          |
+| MANO | Management and Orchestrator                   |
+| OSS  | Operation Support System                      |
+| RCF  | Resource Control Functions                    |
+| RF   | Resource Functions                            |
+| RP   | Reference Point                               |
+| SDN  | Software Defined Network                      |
+| SP   | Service Provider                              |
+| VCDN | Virtual Content Delivery Network              |
+| VN   | Virtual Network                               |
+| VNAM | Virtual Network Application Management (VNAM) |
+| VNRC | Virtual Network Resource Control              |
+
+# **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.
+
+# 6 Introduction
+
+The target of a conventional CDN is to improve the service QoE by pushing the content to the server node which is nearest to the end user. However, the efficiency of a CDN will be affected by various factors, such as loading balance status, bandwidth changing, network traffic and the underlay network topology. The current network is fixed, non-service aware and hard to be replaced. For some CDN solutions, CDN nodes may have the capability to detect and retrieve the network status periodically for service optimizing. But the problem is, the retrieved network information is unreliable, which may reduce the CDN service efficiency. On the other hand, it is difficult for the service provider to quickly create and distribute a new service based on the fixed network hardware and configuration.
+
+Therefore, as the fundamental element of CDNs, network innovation brings a great benefit to the service provider or CDN operator to optimize their CDN service. A flexible, programmable and service-aware network would give an opportunity to solve the problem mentioned above and reduce the cost of CDN service investment and maintenance.
+
+Figure 6-1 shows the functional component that relates to network virtualization in the virtual content delivery network (VCDN). The functional architecture can be found in [ITU-T H.644.1].
+
+![Figure 6-1: Functions related to network virtualization in VCDN architecture. The diagram shows a layered functional architecture. At the top, a dashed box labeled 'VCDN' contains three stacked components: 'VCDN service functions' (light blue), 'Resource control functions' (yellow, containing 'Virtual network resource control'), and 'Resource functions' (green, containing 'Virtual network resource'). Below this box is a grey 'Network functions' block. To the left is a 'Content delivery functions' block, and to the right is a 'Content delivery management functional block'. Arrows indicate interactions between these components. A horizontal line at the bottom divides the 'Scope of ITU-T H.644.2' (left) from 'Out of scope' (right). The label 'H.644.2(19)_F6-1' is in the bottom right corner.](367926125450c2bc3f4bdca9d59a62ba_img.jpg)
+
+Figure 6-1: Functions related to network virtualization in VCDN architecture. The diagram shows a layered functional architecture. At the top, a dashed box labeled 'VCDN' contains three stacked components: 'VCDN service functions' (light blue), 'Resource control functions' (yellow, containing 'Virtual network resource control'), and 'Resource functions' (green, containing 'Virtual network resource'). Below this box is a grey 'Network functions' block. To the left is a 'Content delivery functions' block, and to the right is a 'Content delivery management functional block'. Arrows indicate interactions between these components. A horizontal line at the bottom divides the 'Scope of ITU-T H.644.2' (left) from 'Out of scope' (right). The label 'H.644.2(19)\_F6-1' is in the bottom right corner.
+
+**Figure 6-1 – Functions related to network virtualization in VCDN architecture**
+
+Figure 6-1 presents the basic idea of network virtualization related functions within the scope of VCDNs.
+
+The physical network resource in network functions, such as routers and switches, can be abstracted in the resource function and be orchestrated and managed by the resource control functions (RCF). The orchestrator and management can be implemented in the VN MANO (virtual network management and orchestrator) functions which could be integrated with the RCF. Alternatively, the VN MANO functions can be separated from the RCF and act as third party functions. In this case,
+
+the communication between the RCF and third party MANO can be realized through a standard interface.
+
+The network resource control may be based on the request from the content delivery management functional block or be dynamically modified according to the network information from the under layer network.
+
+Resource functions (RF) will provide an abstract resource infrastructure based on the physical resource from the content delivery functions (CDF) and create the required virtual resource by the instructions of the RCF.
+
+## 7 Functions and functional blocks related to network virtualization under VCDN architecture
+
+Resource control functions and resource functions handle the core functionalities of CDN virtualization. The following clauses specify the functions and functional blocks within those two functions which relate to the scope of network virtualization.
+
+## 7.1 Functions and functional blocks in resource control functions
+
+Resource control functions handle the orchestration and management of the virtual network resource abstracted from the resource functions. It also creates and manages the networking related application instances to meet the VCDN operator's requirements. With the combination of these components, the RCF is able to control the virtual network resource creation, allocation and release.
+
+Figure 7-1 shows the functions and functional blocks in the RCF.
+
+![Diagram of functional blocks in resource control functions related to virtual network instance. The diagram shows a hierarchy of nested boxes. The outermost box is 'Resource control functions' (yellow). Inside it is 'Virtual network resource control functions' (orange). Inside that is 'Virtual network MANO functions' (white), which contains two side-by-side boxes: 'VN orchestrator functional block' and 'VN App management functional block'. Below these two is a single box labeled 'Virtual network resource control functional block'. To the right of the 'Virtual network MANO functions' box is a dashed box labeled 'Third virtual network MANO functions', connected by a dashed line. The label 'H.644.2(19)_F7-1' is at the bottom right.](54fabc351eda5228d2fa28cd9ba07971_img.jpg)
+
+H.644.2(19)\_F7-1
+
+Diagram of functional blocks in resource control functions related to virtual network instance. The diagram shows a hierarchy of nested boxes. The outermost box is 'Resource control functions' (yellow). Inside it is 'Virtual network resource control functions' (orange). Inside that is 'Virtual network MANO functions' (white), which contains two side-by-side boxes: 'VN orchestrator functional block' and 'VN App management functional block'. Below these two is a single box labeled 'Virtual network resource control functional block'. To the right of the 'Virtual network MANO functions' box is a dashed box labeled 'Third virtual network MANO functions', connected by a dashed line. The label 'H.644.2(19)\_F7-1' is at the bottom right.
+
+**Figure 7-1 – Functional blocks in resource control functions related to virtual network instance**
+
+NOTE – The architecture of the virtual network resource control functions (VN-RCF) in this Recommendation covers the instantiation of the virtual network. But it could cover the instantiation of virtual storage and virtual computing as well.
+
+### 7.1.1 Virtual network MANO functions
+
+Virtual network MANO (VN-MANO) functions handle the lifecycle of the VCDN service, VNAF and the virtualized network resource control corresponding to the VCDN service request. It is composed of an orchestrator, VN application management and VN resource control functional blocks. It is noted that VN-MANO functions are alternatively exited out of the RCF as third party functions. The examples of communication between VN-RCF and the third party VN-MANO can be referenced to [b-ETSI GS NFV 002].
+
+#### 7.1.1.1 Virtual network orchestrator functional block
+
+The orchestrator functional block is responsible for the lifecycle management of the VN service, the coordination of VN applications management in the VCDN and the orchestration of the VN resource.
+
+#### 7.1.1.2 Virtual network application management functional block
+
+The virtual network application management (VNAM) functional block is responsible for the instantiation and lifecycle management of the VN application related to a VCDN service. It is noted that the VNAM functional block is possibly composed of many independent instances.
+
+#### 7.1.1.3 Virtual network resource control functional block
+
+The virtual network resource control (VNRC) functional block is responsible for the control and management of the virtual network resource from the resource functions.
+
+## 7.2 Functions and functional blocks in resource functions
+
+Resource functions handle the physical resource maintenance, especially the network resources in this Recommendation, and the resource virtualization. The virtualized network resource can be utilized by the resource control function. With the combination of these components, the RF is able to create the logical network resource partition for different uses under the control of the RCF.
+
+Figure 7-2 shows the functions and functional blocks that are contained in the RF.
+
+![Diagram of functional blocks in resource functions related to virtual network instance](8e14350b4b669119a3bdfca7869110ca_img.jpg)
+
+The diagram illustrates the functional blocks within the Resource functions. It is a vertical stack of four components inside a green rounded rectangle. From top to bottom, they are: 'Virtual network application functions' (white box), 'Virtualized network resource' (orange box), 'Resource abstract layer' (white box), and 'Physical network resource' (white box). The boxes are connected by vertical lines. A label 'Resource functions' is at the top of the green box. A small label 'H.644.2(19)\_F7-2' is at the bottom right of the diagram.
+
+Diagram of functional blocks in resource functions related to virtual network instance
+
+**Figure 7-2 – Functional blocks in resource functions related to virtual network instance**
+
+NOTE – The physical resource here is in the scope of the resource function. In fact, the physical resource entity comes from different geographical locations.
+
+### 7.2.1 Virtual network application functions
+
+Virtual network application (VNA) functions enable the resource control function (RCF) to implement the CDN service logical functional components as instances based on virtualized network resources, e.g., an APP implements CDN service functionalities as virtualized CDN nodes.
+
+### 7.2.2 Virtualized network resource
+
+Virtual network resource (VNR) functions are a logical representation of the physical network resource. These virtualized network resources are created and assigned by the request from the RCF according to the specific capability of an application or a service.
+
+### 7.2.3 Resource abstract layer
+
+The resource abstract layer (RAL) interacts with the physical network resource to provide the abstraction of the physical network functions. With this abstraction, the physical network resource can be reassigned as many logical network resource partitions, and be presented as the available virtual network resource.
+
+### 7.2.4 Physical network resource
+
+Physical network resource is composed of the physical network elements, such as routers and switches. In a general point of view, the CPU and hard-disk can also be regarded as the physical
+
+network elements. They have different capabilities and characteristics. Those network elements can be located in one data centre or can be distributed in the broad geographic locations.
+
+# 8 Network virtualization for VCDN
+
+With the network virtualization technologies, VCDNs can be built in a flexible, programmable and service-sensitive network environment. The different network virtualization technologies enable the VCDN to work for different purposes with the corresponding solutions. The following clauses introduce some potential solutions by taking advantage of network virtualization technologies.
+
+## 8.1 CDN function virtualization coupled with SDN-based solution
+
+The following subclauses introduce the possible solutions of adopting SDN into CDN function virtualization. According to the purpose of CDN capability design, the two different SDN-based solutions could be selected: tight coupled SDN-based solution and loose coupled SDN-based solution.
+
+### 8.1.1 Tight coupled SDN-based network virtualization
+
+The tight coupled network virtualization means most data routing functions in the CDN, especially the network transport and traffic control related functions, can be coordinated with the SDN service and the rest of the CDN service logic remains in the CDN functions. VCDN functions need to receive the request from CDN functions to create its own service logic and control the resource usage directly. The benefit of adopting the tight coupled network virtualization is the improvement of the CDN distribution and delivery efficiency. Data transport and processes can be directly executed under the control of the virtualized network elements in the VCDN.
+
+The SDN-based VCDN solution provides an opportunity to integrate the CDN functions with the SDN functional architecture. Figure 8-1 shows how the SDN functional architecture can be integrated with CDN functions within the VCDN scope.
+
+![Figure 8-1: Tightly-coupled SDN-based network virtualization solutions. The diagram illustrates the integration of SDN layers with CDN functions. It is divided into three horizontal layers: SDN application layer, SDN control layer, and SDN resource layer. The SDN application layer contains an 'SDN application' which is integrated with a 'CDN application'. The SDN control layer contains an 'Orchestrator' which is integrated with 'Content distribution, delivery control' and 'Content distribution, delivery' from the CDN. The SDN resource layer contains 'Data transport and processing' which is integrated with the 'CDN transport network (Physical resource)'. Arrows indicate the flow of 'Function integration' (thick grey), 'Media stream' (thin black), and 'Controlling message' (thin grey).](78ffccd66df9bafd96e3e081110d09dd_img.jpg)
+
+The diagram shows the integration of SDN layers with CDN functions. It is structured as follows:
+
+- SDN application layer:** Contains 'SDN application'. It is integrated with 'CDN application' via a thick grey arrow (Function integration).
+- SDN control layer:** Contains 'Orchestrator'. It is integrated with 'Content distribution, delivery control' and 'Content distribution, delivery' from the CDN via thick grey arrows (Function integration).
+- SDN resource layer:** Contains 'Data transport and processing'. It is integrated with 'CDN transport network (Physical resource)' via thick grey arrows (Function integration).
+
+Vertical arrows within the SDN layers indicate internal flow: from SDN application to SDN control layer, and from SDN control layer to SDN resource layer. Horizontal arrows from the CDN side indicate the flow of 'Media stream' (thin black) and 'Controlling message' (thin grey).
+
+Legend:
+
+- Function integration (thick grey arrow)
+- Media stream (thin black arrow)
+- Controlling message (thin grey arrow)
+
+Reference: H.644.2(19)\_F8-1
+
+Figure 8-1: Tightly-coupled SDN-based network virtualization solutions. The diagram illustrates the integration of SDN layers with CDN functions. It is divided into three horizontal layers: SDN application layer, SDN control layer, and SDN resource layer. The SDN application layer contains an 'SDN application' which is integrated with a 'CDN application'. The SDN control layer contains an 'Orchestrator' which is integrated with 'Content distribution, delivery control' and 'Content distribution, delivery' from the CDN. The SDN resource layer contains 'Data transport and processing' which is integrated with the 'CDN transport network (Physical resource)'. Arrows indicate the flow of 'Function integration' (thick grey), 'Media stream' (thin black), and 'Controlling message' (thin grey).
+
+**Figure 8-1 – Tightly-coupled SDN-based network virtualization solutions**
+
+Basically, there are three parts in the CDN are recommended to be coordinated with SDN layers:
+
+- The CDN application function is integrated with SDN application.
+- The CDN control functions, i.e., content distribution control function and content delivery control function are integrated with the SDN controller.
+
+- Content distribution, content delivery and the physical network resource, such as switcher, router, gateway or any device which supports SDN transport protocols, are integrated with the SDN resource layer (more precisely, the data transport and processing function).
+
+With the integration, when the SDN application layer receives the service request from the CDN application, it creates the resource acquiring information and service orchestrating information based on the request. Then that information will be used to create the resource reservation request. The request is then sent from the application layer to the SDN control layer.
+
+The SDN control layer allocates the CDN resource required according to the above-mentioned resource reservation requirement. It also generates a content route table for data transporting, according to the network load balance and routing policy. Then the SDN control layer generates the L2/L3 (data link layer/network layer) forwarding table based on the content routing table and sends this table to the SDN resource layer.
+
+The data transport and processing function in the SDN resource layer is responsible for the data transporting for content distribution and content delivery. When the request of content distribution and content delivery are received, the SDN resource layer invokes the related resource from the CDN physical network to execute the functions of distribution and delivery for implementing the service application, according to the L2/L3 forwarding table.
+
+From the above conceptual progress, the CDN is able to request, allocate, occupy and release the network resource dynamically by taking advantage of tight coupled SDN-based network virtualization.
+
+### **8.1.2 Loose coupled SDN-based network virtualization**
+
+Loose coupled network virtualization means the most of CDN functions, i.e., the application, distribution and delivery, can be migrated into an SDN-based VCDN and only a few functions still remain in the CDN functions, e.g., user request redirect. When the VCDN receives the request redirected from the CDN or other request sources, it implements its own service logic and controls the resource usage directly under the VCDN software environment. In this case, the VCDN node is almost separated from the physical dedicated CDN node. The benefit of adopting the loose coupled network virtualization is flexible CDN functions deployment. CDN nodes can be created as a software module based on a universal hardware and operation system, where other application programs are managed in parallel. It is easily managed by operators and can reduce the hardware and software investment.
+
+Figure 8-2 shows how CDN functions are migrated in the SDN functional architecture within the VCDN scope.
+
+![Diagram of loose coupled SDN-based network virtualization solutions. The diagram shows three main components: a VCDN (Virtual CDN) box on the left, a 'CDN functions/other source' box on the right, and a 'User terminal device' at the bottom right. The VCDN box contains three layers: SDN application layer (with 'CDN function (SDN application)' containing 'Request function' and 'Operation function'), SDN control layer (with 'Orchestrator' containing 'Orchestrate' and 'Control'), and SDN resource layer (with 'Data transport and processing'). Arrows show interactions: 'Service request' from User terminal device to SDN application layer; 'Resource request' from Request function to Orchestrator; 'Orchestrate feedback' from Orchestrator to Operation function; 'Resource reservation' from Orchestrator to Data transport and processing; 'Media stream' from Data transport and processing to User terminal device; and 'Function integration' from CDN functions/other source to Operation function. A legend at the bottom defines the arrow types: thick grey for Function integration, solid black for Media stream, and dashed grey for Request message.](4801720824e4b5e2361a5564f91cfb70_img.jpg)
+
+Diagram of loose coupled SDN-based network virtualization solutions. The diagram shows three main components: a VCDN (Virtual CDN) box on the left, a 'CDN functions/other source' box on the right, and a 'User terminal device' at the bottom right. The VCDN box contains three layers: SDN application layer (with 'CDN function (SDN application)' containing 'Request function' and 'Operation function'), SDN control layer (with 'Orchestrator' containing 'Orchestrate' and 'Control'), and SDN resource layer (with 'Data transport and processing'). Arrows show interactions: 'Service request' from User terminal device to SDN application layer; 'Resource request' from Request function to Orchestrator; 'Orchestrate feedback' from Orchestrator to Operation function; 'Resource reservation' from Orchestrator to Data transport and processing; 'Media stream' from Data transport and processing to User terminal device; and 'Function integration' from CDN functions/other source to Operation function. A legend at the bottom defines the arrow types: thick grey for Function integration, solid black for Media stream, and dashed grey for Request message.
+
+**Figure 8-2 – Loose coupled SDN-based network virtualization solutions**
+
+- SDN application layer – CDN function (SDN application)  
+ CDN logical functions could be migrated into the SDN application layer as an SDN application. To implement CDN service logical operations, the CDN function needs to implement at least 2 functional modules:
+  - Request function  
+ This functional block is used to add the integrated CDN service logical functions into the SDN application layer. Moreover, it receives the CDN service request and then sends the request of resource requiring and service orchestrating to the orchestrate function in the orchestrator in the SDN control layer.
+  - Operation function  
+ The major CDN functions, e.g., CDN application, content distribution and delivery, content storage and load balance, can be migrated into the operation function which handles the logical procedure of the CDN service. When the feedback information of resource reservation is received, the operation function implements the logical operation based on the content distribution or media accessing request.
+- SDN control layer – Orchestrator functions  
+ The orchestrator provides control and management of the network resource, as well as the coordination of requests from the SDN application layer (referenced from [ITU-T Y.3300]). To process the request from the SDN application layer, the orchestrator is recommended to implement 2 functional modules:
+  - Orchestrate function  
+ The orchestrate function can be further composed of two functional blocks:
+    - 1 Resource coordination: This is used to receive the request of resource requiring and service orchestrating and to process the service orchestrating according to the SDN
+
+network information. Then it sends the request of required resource reservation to the control function.
+
+- 2 Orchestrate feedback: When the resource reservation has been completed, it returns the feedback to the CDN function with the resource reservation information.
+
+#### - Control function
+
+The control function is used to allocate the resource required by the CDN service, according to the resource reservation request. After the resource allocation, the control function will determine the routing path for content distribution and delivery, combining with the condition of load balance and routing status in the network. It also creates the data link layer/network layer (L2/L3) forwarding tables based on the control policy of the SDN controller layer and then sends these tables to the data transport and process function. Moreover, it also needs to return the information of resource reservation to the orchestrate function.
+
+#### - SDN resource layer – data transport and processing functions
+
+The data transport and processing function entity involves many network devices which support SDN transport protocols. They are used for storing data based on the allocated resource related to the CDN function. Furthermore, it executes data transporting correspond with the logical operation in the CDN function, according to the L2/L3 forwarding tables determined by the control function.
+
+## **8.2 CDN node virtualized with the support of network virtualization system**
+
+The following subclauses introduce the solution of creating a virtualized CDN node with the support of a network virtualization system.
+
+### **8.2.1 High-level functional architecture of CDN node virtualization**
+
+The typical service components of the CDN include the CDN operation and maintenance system, content distribution system, delivery system, content location and routing system. These systems are composed of many logical functions and are implemented in the various types of CDN node. According to the VCDN solution, these logical functions are required to be virtualized and be reorganized as the one or various virtual applications running in one or multiple virtual machines. These virtual applications are recommended to be created by the network virtualization system.
+
+The diagram in Figure 8-3 shows the high-level functional architecture of a virtualized CDN node.
+
+![Figure 8-3: CDN node virtualized with network virtualization system. The diagram shows a layered architecture. At the top is the 'vCDN service' containing 'OSS/BSS'. Below it is the 'Resource control functions' layer containing 'Configuration' and 'Virtual resource orchestration'. The 'OSS/BSS' sends 'Resource orchestrate' to 'Virtual resource orchestration' and receives 'Configuration'. The 'Virtual resource orchestration' sends 'APP create' and 'Resource reservation' to the 'Resource functions' layer. The 'Resource functions' layer contains 'vCDN node (APPs)' which includes 'APP management and configuration' for 'Virtual APP' instances (each with 'CDN functions'). These instances send 'Resource invoke' to the 'Virtual resource management platform' at the bottom. The platform contains 'Virtual computing', 'Virtual storage', and 'Virtual networking'. A return arrow goes from the platform back to the 'OSS/BSS'. A label 'H.644.2(19)_F8-3' is at the bottom right.](fa859e4e468bfb2710a94527f2c504af_img.jpg)
+
+Figure 8-3: CDN node virtualized with network virtualization system. The diagram shows a layered architecture. At the top is the 'vCDN service' containing 'OSS/BSS'. Below it is the 'Resource control functions' layer containing 'Configuration' and 'Virtual resource orchestration'. The 'OSS/BSS' sends 'Resource orchestrate' to 'Virtual resource orchestration' and receives 'Configuration'. The 'Virtual resource orchestration' sends 'APP create' and 'Resource reservation' to the 'Resource functions' layer. The 'Resource functions' layer contains 'vCDN node (APPs)' which includes 'APP management and configuration' for 'Virtual APP' instances (each with 'CDN functions'). These instances send 'Resource invoke' to the 'Virtual resource management platform' at the bottom. The platform contains 'Virtual computing', 'Virtual storage', and 'Virtual networking'. A return arrow goes from the platform back to the 'OSS/BSS'. A label 'H.644.2(19)\_F8-3' is at the bottom right.
+
+**Figure 8-3 – CDN node virtualized with network virtualization system**
+
+In the VCDN ecosystem, the creation of a virtual CDN node will mainly rely on the network virtualization system. Typically, a network virtualization system can be composed of a virtual resource orchestration system and virtual resource management system (resource pool).
+
+The virtual CDN node should be created by the intention of the VCDN customer. The intention will be decomposed and be reprogrammed as the computing request in the VCDN service system, typically, in the OSS/BSS. The virtual resource orchestration system receives the request and then orchestrates the related resource for a target VCDN node(s). The resource reservation request is sent to the virtual resource management system for resource allocation and reservation. With the response of the resource reservation, the virtual resource orchestration system created the instance of the VCDN node as one or couples of software apps. Furthermore, once the VCDN nodes have been created, the VCDN nodes information should be updated in the OSS/BSS or GSLB and can be used in the entire CDN ecosystem.
+
+### 8.2.2 The functional components within network virtualization system
+
+The network virtualization system in Figure 8-3 is composed of several functional components: the virtual resource orchestrator, virtual resource management platform, virtual applications and the related management system.
+
+#### 8.2.2.1 Virtual resource orchestrator
+
+The virtual resource orchestrator receives the VCDN service creation request from the OSS/BSS in the VCDN service functions. The service creation request contains the VCDN node description information. Based on the description information, the logical VCDN node functions and the resources for VCDN node creation are orchestrated and the related virtual applications which represent the CDN functions are created and performed on the physical hardware, i.e., virtual machine(s).
+
+It is noted that the resource orchestration request could also come from the GSLB if the GSLB determines to modify the node capacity by inspecting the CDN node topology.
+
+The resource orchestrator can be further composed of the following subfunctions:
+
+- ***Orchestrating function:*** Receives the VCDN nodes creation request and orchestrates the related resource based on the VCDN node logical functions. In an optional way, a preconfigured resource orchestration template can be stored in advance for quick CDN node virtualization.
+- ***Virtual resource reservation function:*** Sends the resource request to the virtual resource management platform and reserves the related virtual resources.
+- ***Virtual application management function:*** With the reserved virtual resource, the virtual application management system creates the instances of VCDN logical functions, i.e., virtual apps. The lifecycle of virtual apps is also managed by the virtual application management functions.
+
+#### 8.2.2.2 Virtual resource management platform
+
+The virtual resource management platform is regarded as a resource pool which provides the abstract resource to the resource orchestrator. The virtual CDN apps are able to be deployed in the hardware and software environments provided by the virtual resource management platform. In addition, the virtual resource can be adjusted in the future if the VCDN node functions need to be modified.
+
+The logical virtual resource can be integrated in one virtual machine or be provided by multiple separate virtual machines.
+
+#### 8.2.2.3 Virtual application
+
+The virtual application is the instance of the virtual CDN functions. By invoking the reserved virtual resource portion, these applications are created and managed by the virtual resource orchestrator. The logical functions of a virtualized CDN node can be made up of one or many virtual applications. According to the functional requirements, the virtual CDN node can be performed as different types, such as the centre node and edge node:
+
+The virtual application for the centre node may contain a content pro-process function, content ingestion function, content distribution function, storage/cache function, GSLB function, SLB function and OSS/BSS functions.
+
+The virtual application for the edge node may contain a content delivery function, delivery control function, SLB function, storage/cache function, content process function and OSS/BSS functions.
+
+In addition, some network devices, such as a virtual switch, may also be created as one or more apps.
+
+The application is recommended to be configurable after it has been created. The parameters of CDN node functions are usually determined by the CDN OSS/BSS according to the VCDN customer's intention. An app management and configuration system can be used to execute the CDN node app configuration.
+
+## 8.3 CDN node virtualized with the support of network virtualization system and SDN controller
+
+The following subclauses introduce the solution of creating a virtualized CDN node with the support of a network virtualization system and an SDN controller.
+
+In this case, the networking sources virtualization and allocation are under the control of SDN controller functions, which can be performed as a dedicated physical device.
+
+### 8.3.1 High-level functional architecture of CDN node virtualization with SDN controller
+
+The primary intention of this solution is to leave the network resource to be orchestrated by the SDN, precisely, the SDN controller layer. In this solution, most procedures of the creation of a virtual CDN node are the same as the description given in clause 8.2.1. The only difference is that the network
+
+resource orchestration request will be forward to the SDN controller. The SDN controller controls reservation and management of the virtual network resource.
+
+The other functional components and the related functions are very similar to the components mentioned in clause 8.2.1. But in the resource control functions, the physical network devices are recommended to be able to support the interaction between the virtual resource orchestration functions and the SDN controller functions.
+
+The diagram in Figure 8-4 shows the high-level functional architecture of CDN node virtualization with an SDN controller.
+
+![Figure 8-4: CDN node virtualized with network virtualization system (cooperated with SDN controller). The diagram shows a hierarchical functional architecture. At the top is a 'vCDN service' box containing 'OSS/BSS'. Below it is a 'Resource control functions' box containing 'Virtual resource orchestration' and 'SDN controller functions'. Below that is a 'Resource functions' box containing 'vCDN node (APPs)' with 'APP management and configuration', 'Virtual APP' (with 'CDN functions 1', 'CDN functions 2', 'CDN functions 3'), and 'Virtual resource management platform' (with 'Virtual computing', 'Virtual storage', and 'SDN resource'). Arrows show interactions: 'Resource orchestrate' from vCDN service to Virtual resource orchestration; 'Configuration' from vCDN service to Resource functions; 'APP create' from Virtual resource orchestration to APP management and configuration; 'Network resource orchestration' from Virtual resource orchestration to SDN controller functions; 'Resource reservation' from SDN controller functions to Virtual resource orchestration; 'Resource invoke' from Virtual APP to Virtual resource management platform; and 'Network resource reservation' from SDN controller functions to SDN resource.](4356776ca004ecba5d599667a155d7d4_img.jpg)
+
+Figure 8-4: CDN node virtualized with network virtualization system (cooperated with SDN controller). The diagram shows a hierarchical functional architecture. At the top is a 'vCDN service' box containing 'OSS/BSS'. Below it is a 'Resource control functions' box containing 'Virtual resource orchestration' and 'SDN controller functions'. Below that is a 'Resource functions' box containing 'vCDN node (APPs)' with 'APP management and configuration', 'Virtual APP' (with 'CDN functions 1', 'CDN functions 2', 'CDN functions 3'), and 'Virtual resource management platform' (with 'Virtual computing', 'Virtual storage', and 'SDN resource'). Arrows show interactions: 'Resource orchestrate' from vCDN service to Virtual resource orchestration; 'Configuration' from vCDN service to Resource functions; 'APP create' from Virtual resource orchestration to APP management and configuration; 'Network resource orchestration' from Virtual resource orchestration to SDN controller functions; 'Resource reservation' from SDN controller functions to Virtual resource orchestration; 'Resource invoke' from Virtual APP to Virtual resource management platform; and 'Network resource reservation' from SDN controller functions to SDN resource.
+
+**Figure 8-4 – CDN node virtualized with network virtualization system (cooperated with SDN controller)**
+
+Logically, the SDN controller functions are recommended to be separated from the virtual resource orchestrator and to deal with the network resource orchestration specifically. It receives the network resource orchestrate request from the virtual resource orchestrator through a standard interface, e.g., the northbound interface. The reservation of management of network resources is controlled by the SDN controller by through another standard interface, e.g., the southbound interface. The implementation of these interfaces may have many solutions. For example, [ITU-T Y.3300] defines the interfaces and their functions in clause 11.5.
+
+### 8.3.2 The functional components within network virtualization system and SDN controller
+
+Most of the functional components and the functional requirements in this case are the same as those of the previous case. Considering the requirement of supporting the SDN controller, the functional components in the network virtualization system may have some new features.
+
+#### 8.3.2.1 Virtual resource orchestrator cooperated with SDN controller
+
+The primarily functions of the virtual resource orchestrator can be referenced from clause 8.2.2.1.
+
+In this solution, after the virtual resource orchestrator receives the VCDN service request, the network resource orchestration request will be separately forwarded to the SDN controller. The virtual
+
+network resource will be orchestrated by the SDN controller based on the real-time transport network information.
+
+Therefore, the virtual resource orchestrator should be performed as a logical SDN application. The interface between the virtual resource orchestrator and the SDN controller is recommended to be compliant with the SDN northbound interface requirements. The SDN northbound interface definition can be referenced from [ITU-T Y.3300], clause 11.2.
+
+In an optional way, a proxy server can be performed as the protocol interpreter between the virtual resource orchestrator and the SDN controller, if the virtual resource orchestrator does not support the SDN northbound interface definition. That proxy server can be physical equipment or a software app.
+
+#### **8.3.2.2 Virtual resource management platform**
+
+The primary functions of the virtual resource orchestrator can be referenced from clause 8.2.2.2.
+
+What is different from the description in clause 8.2.2.2 is that the virtual resource management platform is recommended to be able to respond to the network resource control request from the SDN controller. The request can be delivered through an interface between the virtual resource management platform and the SDN controller, which is recommended to be compliant with the SDN southbound interface requirements. The SDN southbound interface definition can be referenced from [ITU-T Y.3300], clause 11.2.
+
+The physical network resources managed by this platform, such as routers, are required to support SDN protocols.
+
+#### **8.3.2.3 Virtual application**
+
+The primary functions of the virtual resource orchestrator can be referenced from clause 8.2.2.3.
+
+#### **8.3.2.4 SDN controller functions**
+
+In this case, SDN controller functions are separated from the virtual resource orchestrator. They orchestrate and reserve the network resource based on the available network resource under their control. The detailed functions of the SDN controller can be referenced from [ITU-T Y.3300] and [ITU-T Y.3302].
+
+It is noted that the physical SDN controller device can be deployed separately from the resource control function (physical platform) in the real implementation, while the SDN controller functions act as a software application.
+
+## **8.4 CDN node virtualized with the support of network virtualization system and virtual SDN controller**
+
+The following subclauses introduce the solution of creating a virtualized CDN node with the support of a network virtualization system and an SDN controller.
+
+In this case, the SDN controller is not a dedicated piece of hardware but a virtual app created dynamically by a specific request.
+
+### **8.4.1 High-level functional architecture of CDN node virtualization with virtual SDN controller**
+
+The primary intention of this solution is very similar to the intention of clause 8.3.1. The only difference in this solution is the network resource will be orchestrated by a virtual SDN controller, which is created by the network virtualization system as a virtual app. Therefore, the network virtualization system manages the lifecycle of the virtual SDN controller, as well as the virtual CDN functions simultaneously.
+
+The diagram in Figure 8-5 shows the high-level functional architecture of CDN node virtualization with the virtual SDN controller.
+
+![Figure 8-5: CDN node virtualized with network virtualization system (cooperated with virtual SDN controller). The diagram shows a hierarchical structure of network functions. At the top is a 'vCDN service' box containing 'OSS/BSS'. Below it is a 'Resource control functions' box containing 'Virtual resource orchestration'. Below that is a 'Resource functions' box containing a 'vCDN node (SDN APPs)' box (with 'APP management and configuration', 'Virtual APP', 'CDN functions 1', and 'CDN functions 2'), a 'Virtual APP' box (with 'SDN controller'), and a 'Virtual resource management platform' box (with 'Virtual computing', 'Virtual storage', and 'SDN resource'). Arrows indicate various interactions: 'Configuration' from vCDN service to Resource functions; 'Resource orchestrate' from vCDN service to Virtual resource orchestration; 'APP create' from Virtual resource orchestration to vCDN node and Virtual APP; 'Resource reservation' and 'Network resource orchestration' from Virtual resource orchestration to SDN controller; 'Network resource orchestration' from Virtual APP to vCDN node; 'Resource invoke' from vCDN node to Virtual resource management platform; 'Network resource reservation' from SDN controller to Virtual resource management platform; and 'H.644.2(19)_F8-5' at the bottom right.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg)
+
+Figure 8-5: CDN node virtualized with network virtualization system (cooperated with virtual SDN controller). The diagram shows a hierarchical structure of network functions. At the top is a 'vCDN service' box containing 'OSS/BSS'. Below it is a 'Resource control functions' box containing 'Virtual resource orchestration'. Below that is a 'Resource functions' box containing a 'vCDN node (SDN APPs)' box (with 'APP management and configuration', 'Virtual APP', 'CDN functions 1', and 'CDN functions 2'), a 'Virtual APP' box (with 'SDN controller'), and a 'Virtual resource management platform' box (with 'Virtual computing', 'Virtual storage', and 'SDN resource'). Arrows indicate various interactions: 'Configuration' from vCDN service to Resource functions; 'Resource orchestrate' from vCDN service to Virtual resource orchestration; 'APP create' from Virtual resource orchestration to vCDN node and Virtual APP; 'Resource reservation' and 'Network resource orchestration' from Virtual resource orchestration to SDN controller; 'Network resource orchestration' from Virtual APP to vCDN node; 'Resource invoke' from vCDN node to Virtual resource management platform; 'Network resource reservation' from SDN controller to Virtual resource management platform; and 'H.644.2(19)\_F8-5' at the bottom right.
+
+**Figure 8-5 – CDN node virtualized with network virtualization system (cooperated with virtual SDN controller)**
+
+As an alternative solution, the procedure of the creation of a virtual CDN node is the same as the procedure description in clause 8.3.1. The only difference is the SDN controller here is a virtualized app to which the network resource orchestration request will be forwarded. The functions of a virtual SDN controller is almost the same as that of a physical SDN controller.
+
+This case is expected to be suited to a CDN which is composed of virtual nodes completely.
+
+### 8.4.2 The functional components within network virtualization system and virtual SDN controller
+
+Most functional components and functional requirements in this case are the same as those in clause 8.3.2.
+
+#### 8.4.2.1 Virtual resource orchestrator cooperated with a virtual SDN controller
+
+The primary functions of the virtual resource orchestrator can be referenced from clause 8.2.2.1.
+
+In this case, after the virtual resource orchestrator has received the VCDN service request, the network resource orchestration request is separately forwarded to the virtual SDN controller. The virtual SDN controller will orchestrate the virtual network resource based on the transport network information.
+
+As noted in clause 8.3.2.1, the virtual resource orchestrator should be performed as the logical SDN application. The interface between the virtual resource orchestrator and the virtual SDN controller is recommended to be compliant with the SDN northbound interface requirements.
+
+In an optional way, a proxy server can be performed as the protocol interpreter between the virtual resource orchestrator and the virtual SDN controller, if the virtual resource orchestrator does not support the SDN northbound interface definition. That proxy server can be a physical piece of equipment or a software app.
+
+#### 8.4.2.2 Virtual resource management platform
+
+The primary functions of the virtual resource management platform can be referenced from clause 8.3.2.2.
+
+#### 8.4.2.3 Virtual application
+
+The primary functions of the virtual application can be referenced from clause 8.3.2.3. In this case, the virtual SDN controller or the virtual network device running the SDN protocol is created as a virtual application, as well as the creation of the other functions mentioned previously.
+
+#### 8.4.2.4 Virtual SDN controller
+
+The virtual SDN controller in this case is separated from the virtual resource orchestrator and be virtualized by the network virtualization system, as a virtual app. It orchestrates and reserves the network resource based on the network resource under its control. The detailed functions of the SDN controller can be referenced from [ITU-T Y.3300] and [ITU-T Y.3302].
+
+As a virtual app, the virtual SDN controller can be created and released by request dynamically and be managed by a network virtualization system, after the CDN service request has been received. Like other virtual applications, the resources for creating the virtual SDN controller are orchestrated and managed by the virtual resource orchestrator as well. Different from the physical SDN controller or the third party SDN controller, the virtual SDN control may only control the limited network resource which is provided by a specific CDN service provider, instead of the entire resource from all networks. Moreover, the virtual SDN controller can work as an individual server or together with the other SDN controllers to share the information between them as a logical SDN controller function.
+
+# 9 Reference points
+
+The diagram in Figure 9-1 presents the high-level reference points between the functions within the VCDN service scope defined in [ITU-T H.644.1].
+
+![Figure 9-1: Reference points of VCDN architecture. The diagram shows four main functional blocks: End-user functions (left), Application functions (top center), Content delivery functions (middle center), and Management functions (right). The Content delivery functions block contains General content delivery functions, Virtual resource control functions, and Resource functions. Reference points are indicated by dashed lines with labels: A' (between Application and Content delivery), C' (between Application and Content delivery), C1 and C2 (between Application and Management), D' (between General content delivery and Virtual resource control), V' (between Virtual resource control and Resource), N2' (between Virtual resource control and Resource), N1' (between Resource and Network functions), Ud (between Resource and Network functions), and E4 and E6 (between End-user and Content delivery). The Network functions block is at the bottom. A label H.644.2(19)_F9-1 is at the bottom right.](608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg)
+
+H.644.2(19)\_F9-1
+
+Figure 9-1: Reference points of VCDN architecture. The diagram shows four main functional blocks: End-user functions (left), Application functions (top center), Content delivery functions (middle center), and Management functions (right). The Content delivery functions block contains General content delivery functions, Virtual resource control functions, and Resource functions. Reference points are indicated by dashed lines with labels: A' (between Application and Content delivery), C' (between Application and Content delivery), C1 and C2 (between Application and Management), D' (between General content delivery and Virtual resource control), V' (between Virtual resource control and Resource), N2' (between Virtual resource control and Resource), N1' (between Resource and Network functions), Ud (between Resource and Network functions), and E4 and E6 (between End-user and Content delivery). The Network functions block is at the bottom. A label H.644.2(19)\_F9-1 is at the bottom right.
+
+Figure 9-1 – Reference points of VCDN architecture
+
+The reference point defined in this document is recommended to be compliant with the general reference point definition in clause 9 of [ITU-T H.644.1]. By considering the usage of network virtualization technology in a VCDN, the reference point and the information carried on it can be extended as follows, based on the general definitions mentioned in [ITU-T H.644.1].
+
+## **9.1 Reference point M'**
+
+In this document, VCDN application functions receive the service request from the customer management functions on behalf of a certain SP or CP, by RP-M'.
+
+The service request includes the service creation and delete request, service requirements request and other types of requests.
+
+## **9.2 Reference point C'**
+
+The virtual resource control functions receive the required service related resource orchestration request from the VCDN application functions, by RP-C'. In the scenarios mentioned in this document, the requests refer to the orchestration of resources which enable the creation of logical function entities or apps of virtualized CDN nodes.
+
+While the virtual service is created, the feedback information can be returned by this RP.
+
+## **9.3 Reference point V'**
+
+Resource functions receive the resource reservation, allocation and other resource management requests from the virtual resource control functions, by RP-V'.
+
+While the virtual app is created, the app management request is also delivered from this RP.
+
+## **9.4 Reference point N1'**
+
+The general RP-N1' definition can be found in [ITU-T H.644.1]. The VCDN data, especially L2/L3 data, can be transferred or forwarded by this RP.
+
+## **9.5 Reference point N2'**
+
+The general RP-N2' definition can be found in [ITU-T H.644.1]. This RP can be particularly used by the SDN controller if the SDN technology is used together with the other network virtualization technologies in the VCDN service.
+
+The following reference points can be used in the situation of coexistence of the VCDN and physical CDN nodes.
+
+## **9.6 Reference point A'**
+
+The application-level request is transmitted from the VCDN application functions to the general content delivery functions, by RP-A'. The general content delivery functions, as the software collection, can be implemented in the dedicated CDN hardware or virtualized in the common virtual machines.
+
+The general RP-A' definition can be found in [ITU-T H.644.1].
+
+## **9.7 Reference point D'**
+
+Generally, this RP-D' is used to exchange the information of physical CDN hardware/software resources between the content delivery functions and the virtual resource control functions, which can be found in [ITU-T H.644.1].
+
+In this Recommendation, this RP-D' would also be used to transfer the virtual network resource orchestration request from the content delivery functions to the virtual resource control functions where the SDN controller is placed, especially under the situation of coexistence of the VCDN and physical CDN nodes.
+
+# Appendix I
+
+## Use cases of network virtualization supporting VCDN services
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Legacy telecommunication services, such as IPTV, is usually deployed on the telecommunication operator's dedicated network. The CDN is also a distribute network overlay with the legacy transport network. But in current markets, the CDN is expected to be designed for an integrated service in an open network environment. Integrated services may be run on different platforms or networks with their own service logic. According to the features of the integrated service, network virtualization is a prospective approach to improve the CDN capability to use the network resource with higher efficiency and flexibility by ignoring the difference of hardware/software.
+
+So the network virtualization for VCDN is considered to have the following use cases.
+
+## I.1 Virtualized CDN node deploy dynamically and flexibly
+
+In general, CDN nodes deployment depends on many factors such as geographical location, target user density, etc. Usually the deployment purpose and node device should be determined by CDN operators. Once the CDN nodes are deployed, the configuration and maintenance for CDN nodes are usually kept stable. But in this situation, if one CDN node capability has exceeded its limitation by the rapid increase of user requests at a peak time, it is difficult to add a new CDN node in time. Also a deployed CDN node resource may not be used efficiently in normal time. The VCDN approach is able to create a new logical CDN node when there is a network device supporting network virtualization through a resource control request and to release the resource when the peak time has passed.
+
+![Diagram illustrating the dynamic deployment of VCDN nodes. The diagram shows a network architecture with a Content centre (Central cache), Control centre (Data centre), Legacy CDN nodes, and NFV/SDN nodes. The Control centre is connected to a GSLB, MANO, and SDN controller, which in turn connects to a VM. The NFV/SDN nodes are connected to the Control centre and the Legacy CDN nodes. The NFV/SDN nodes are also connected to a VM. The NFV orchestrate is shown as a dashed red arrow pointing to the NFV/SDN node. The bottom of the diagram shows various user types: Fixed network, Group user, wlan, and 2G/3G/4G.](86b4670fc1a5a694821ee92b99c1209a_img.jpg)
+
+The diagram illustrates a network architecture for VCDN. At the top, a 'Content centre' with a 'Central cache' is connected to a 'Control centre' with a 'Data centre'. The 'Control centre' is connected to a 'GSLB', 'MANO', and 'SDN controller' block, which contains a 'VM'. Below the 'Control centre', there are two 'Legacy CDN node' units and two 'NFV/SDN node' units. Each 'NFV/SDN node' contains a 'VM' and is labeled 'vCDN node'. A dashed red arrow labeled 'NFV orchestrate' points to one of the 'NFV/SDN node' units. At the bottom, a green bar represents different user types: 'Fixed network' (house icon), 'Group user' (building icon), 'wlan' (laptop icon), and '2G/3G/4G' (mobile phone icon). The text 'H.644.2(19)\_FA.1' is in the bottom right corner.
+
+Diagram illustrating the dynamic deployment of VCDN nodes. The diagram shows a network architecture with a Content centre (Central cache), Control centre (Data centre), Legacy CDN nodes, and NFV/SDN nodes. The Control centre is connected to a GSLB, MANO, and SDN controller, which in turn connects to a VM. The NFV/SDN nodes are connected to the Control centre and the Legacy CDN nodes. The NFV/SDN nodes are also connected to a VM. The NFV orchestrate is shown as a dashed red arrow pointing to the NFV/SDN node. The bottom of the diagram shows various user types: Fixed network, Group user, wlan, and 2G/3G/4G.
+
+Figure I.1 – VCDN nodes deploy dynamically
+
+As Figure I.1 shows, a VCDN node can be created and deployed by the service request. The functionality of a CDN node can be virtualized and programmed on the virtual machine in a server located in a data centre or any device which supports NFV/SDN functions.
+
+## I.2 Smart traffic control
+
+In general, the quality of media content distribution and delivery in the CDN is usually restricted to bandwidth, traffic congestion and network jitter. The routing path and transport control cannot be easily predicted in the legacy CDN because of a lack of sensing for the low layer network status. In the VCDN approach, the traffic control can be centralized in a transport controller, e.g., an SDN controller, and the profile of the network can be obtained by the VCDN management node. Before the content transmission, the VCDN will plan a shortest (may not the shortest in geography) and efficient distribution/delivery path, according the profile of the network status. Moreover, the traffic control may adjust the bandwidth for media transmission during the peak time and release the bandwidth afterwards.
+
+As Figure I.2 shows, the media content data can be distributed to the different edge nodes with an optimized path while the traffic congestion is detected. In addition, a virtualized switch/router can be created for adjusting the bandwidth temporarily.
+
+![Diagram illustrating smart traffic control in VCDN. The diagram shows a network architecture with a Content centre (Central cache), a Control centre (Data centre) containing GSLB, MANO, and SDN controller (VM), and various edge nodes (vCDN node, NFV/SDN node, Legacy CDN node) connected via routers and switches. The Control centre is connected to the Central cache and the edge nodes. The edge nodes are connected to the Central cache and the Control centre. The vCDN node and NFV/SDN node are connected to the Central cache and the Control centre. The Legacy CDN node is connected to the Central cache and the Control centre. The diagram also shows traffic congestion and traffic control paths. At the bottom, a legend indicates 'Traffic control' (blue dashed line) and 'NFV/SDN orchestrate' (red dashed line). Below the network diagram, icons represent different user types: Fixed network, Group user, wlan, and 2G/3G/4G. A reference code 'H.644.2(19)_FA.2' is in the bottom right corner.](4b87467ad9642943235f48f7d4b59449_img.jpg)
+
+Diagram illustrating smart traffic control in VCDN. The diagram shows a network architecture with a Content centre (Central cache), a Control centre (Data centre) containing GSLB, MANO, and SDN controller (VM), and various edge nodes (vCDN node, NFV/SDN node, Legacy CDN node) connected via routers and switches. The Control centre is connected to the Central cache and the edge nodes. The edge nodes are connected to the Central cache and the Control centre. The vCDN node and NFV/SDN node are connected to the Central cache and the Control centre. The Legacy CDN node is connected to the Central cache and the Control centre. The diagram also shows traffic congestion and traffic control paths. At the bottom, a legend indicates 'Traffic control' (blue dashed line) and 'NFV/SDN orchestrate' (red dashed line). Below the network diagram, icons represent different user types: Fixed network, Group user, wlan, and 2G/3G/4G. A reference code 'H.644.2(19)\_FA.2' is in the bottom right corner.
+
+Figure I.2 – Smart traffic control in VCDN
+
+## I.3 Rapid service deployment
+
+In the current market, with the development of transport networks, service platforms and terminal devices, more and more services are being designed rapidly with multiple service types. But with traditional platforms, services usually run in a closed ecosystem. Service design and deployment may
+
+take a couple of months. They may require to be run on special hardware and software. Service configuration and maintenance are difficult because the network resources that the service requires cannot be easily reserved and allocated while the service needs to be distributed over a large-scaled network.
+
+In the VCDN, a virtualized CDN node provides a network resource abstraction with the common hardware/software resource. A new service can be programmed and installed into the operator's service platform quicker than in the legacy way. Also, the visualization of network resources, information collection and network policy would help the operator to deploy the new service into each node in a very short period of time (usually a couple of months before, but only a few days now). The configuration will also be automatically completed in a short time by taking advantage of network resource virtualization.
+
+## **I.4      Unified configuration and management**
+
+In the traditional CDN ecosystem, many CDN equipment from different manufacturers may be deployed in a telecommunication operator's premises side-by-side. These CDN nodes are usually designed for different purposes and rely on the dedicated hardware or software. Any changes such as system/equipment updates and new service creation, may affect the operation for each node in the whole CDN topology correspondingly. Therefore, the differentiation of dedicated hardware/software increases the complexity of configuration, management and operation investments.
+
+The VCDN approach provides an opportunity to separate the logical control layer from the dedicated physical equipment and be redesigned as a unified control centre. The unified control centre can interact with network elements in L2/L3 layer, such as a switch or router, through a standard interface. Moreover, with the virtualization of CDN functions, the unified control centre is able to configure and manage the logical CDN nodes for different purposes based on the resource allocated in a general infrastructure, even where the resource may physically come from different data centres. The resource can be added, adjusted, shared and migrated according to the CDN operator's purpose and time allocation.
+
+## Bibliography
+
+- [b-ITU-T F.743.4] Recommendation ITU-T F.743.4 (2017), *Functional requirements for virtual content delivery networks.*
+- [b-ITU-T Y.2019] Recommendation ITU-T Y.2019 (2010), Content delivery functional architecture in NGN.
+- [b-ITU-T Y.2084] Recommendation ITU-T Y.2084 (2015), Distributed service networking content distribution functions.
+- [b-ITU-T Y.3011] Recommendation ITU-T Y.3011 (2012), *Framework of network virtualization for future networks.*
+- [b-ITU-T Y.3012] Recommendation ITU-T Y.3012 (2014), *Requirements of network virtualization for future networks.*
+- [b-ETSI GS NFV 002] ETSI GS NFV 002 V1.2.1 (2014), *Network Functions Virtualisation (NFV): Architectural Framework.*
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.644.3-202008-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..61904c12b802df120c05ae72cd89a3ef2690dd5b
--- /dev/null
+++ b/marked/H/T-REC-H.644.3-202008-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_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.644.3-202008-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/H/T-REC-H.644.3-202008-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9b8a2a2d73809d8cbfddb3d52516feb806522ad0
--- /dev/null
+++ b/marked/H/T-REC-H.644.3-202008-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4f021f325e0d5b4161d22c21b2c5672c9b7b4addc152e041a07d08e1838e1fe2
+size 172319
diff --git a/marked/H/T-REC-H.644.3-202008-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg b/marked/H/T-REC-H.644.3-202008-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..761d116a8f7a0f91feb947ad01c39710bb4c3479
--- /dev/null
+++ b/marked/H/T-REC-H.644.3-202008-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3cc0a714feee99ffff13d7389d67d142bf90a8c869b6586d16d2350d7f7f55bc
+size 56803
diff --git a/marked/H/T-REC-H.644.3-202008-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/H/T-REC-H.644.3-202008-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..182400e1597c621a09ea1ae825cdae69c3027b12
--- /dev/null
+++ b/marked/H/T-REC-H.644.3-202008-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e68a30a42e305214897d2202caa92d8cc7b771a71912cb36ea974c9142480e98
+size 50451
diff --git a/marked/H/T-REC-H.644.3-202008-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/marked/H/T-REC-H.644.3-202008-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cb358b68f0c70a9fc5f45306ef9b8a4a8b7873b8
--- /dev/null
+++ b/marked/H/T-REC-H.644.3-202008-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:94e5a4e97cf804575400049318a036a778083ffc6479245c3f0a81e3061ec2aa
+size 39755
diff --git a/marked/H/T-REC-H.644.3-202008-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg b/marked/H/T-REC-H.644.3-202008-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8a21ba9a15ba5dbadc5a2a632042ceb3b696c188
--- /dev/null
+++ b/marked/H/T-REC-H.644.3-202008-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:96a8c984829f30f277f6229b5ef1a74ddcb995bcd393734ddf1b71e098d1fa6b
+size 48532
diff --git a/marked/H/T-REC-H.644.3-202008-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/H/T-REC-H.644.3-202008-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8ae0f4bc7f4b5c2dd96f4225b5cc249e66fe26c9
--- /dev/null
+++ b/marked/H/T-REC-H.644.3-202008-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8364eb95a90cdf247dd461273dc1e6acc6243cf3c2d37d34a517011ef9da72b7
+size 159153
diff --git a/marked/H/T-REC-H.644.3-202008-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg b/marked/H/T-REC-H.644.3-202008-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8f8c57623b3ffb146ff3a5092556c4cec6818dda
--- /dev/null
+++ b/marked/H/T-REC-H.644.3-202008-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b810560babe0af20f37670e34690f32e3563ca8bb1738663d6543a896d6cb1a0
+size 55914
diff --git a/marked/H/T-REC-H.644.3-202008-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.644.3-202008-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e7c1cec74d05b0e59b80c840f74157c2d3bfdc8f
--- /dev/null
+++ b/marked/H/T-REC-H.644.3-202008-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a18354d292e366f0c8f0928eec513f039c6859a75c1f1cff36fc6fe59a106730
+size 59356
diff --git a/marked/H/T-REC-H.644.3-202008-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg b/marked/H/T-REC-H.644.3-202008-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..86d5b37017a698b4fa3ab321c3ece5739967af50
--- /dev/null
+++ b/marked/H/T-REC-H.644.3-202008-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9009bdde85443028b7d7ef399cfc3e53d594c8902737152988bda073bbe10ad9
+size 50728
diff --git a/marked/H/T-REC-H.644.3-202008-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg b/marked/H/T-REC-H.644.3-202008-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e9c8371578f2139fc71844f04e43c5e51364b445
--- /dev/null
+++ b/marked/H/T-REC-H.644.3-202008-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3b179e2e3b6216e98b53e3436e1e66be903ed45390f34a879b49e3526e949c68
+size 55478
diff --git a/marked/H/T-REC-H.644.3-202008-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/H/T-REC-H.644.3-202008-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2a91229b2ed1d19366afb966841f9a2d384ab359
--- /dev/null
+++ b/marked/H/T-REC-H.644.3-202008-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4acdf386ccfa578642a510fc9fc282174a4e5e627de8b3b8147340d4c8429539
+size 4390
diff --git a/marked/H/T-REC-H.644.3-202008-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg b/marked/H/T-REC-H.644.3-202008-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..acc3d909cbed32afa408ffba38a509e8ed8c6609
--- /dev/null
+++ b/marked/H/T-REC-H.644.3-202008-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dcdad173fe7aa7b370fe6dcd6aa78bbc1511734840aad4fd10d69022f275b619
+size 3691
diff --git a/marked/H/T-REC-H.644.8-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/H/T-REC-H.644.8-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb
--- /dev/null
+++ b/marked/H/T-REC-H.644.8-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3763acd7a0ed56aa30f3f90468c1fb0cb54573eb9045bca3eddf8976b4f0f41d
+size 7219
diff --git a/marked/H/T-REC-H.644.8-202406-I_PDF-E/a3472689858b068ef469213682965325_img.jpg b/marked/H/T-REC-H.644.8-202406-I_PDF-E/a3472689858b068ef469213682965325_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..013fd7cb1bc7b4a1a4c59f0af66a52b901e8703c
--- /dev/null
+++ b/marked/H/T-REC-H.644.8-202406-I_PDF-E/a3472689858b068ef469213682965325_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1086cbdbcea21312914b1498ab176844f039af6636d367040ab6a96954a51a5
+size 62513
diff --git a/marked/H/T-REC-H.644.8-202406-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/H/T-REC-H.644.8-202406-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..452336ef8d8d0ed08c2567af587768b4bead8b35
--- /dev/null
+++ b/marked/H/T-REC-H.644.8-202406-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b8c07c94d55cf138577abffe2bfb4c1315015ba6f78f246ded23494907a543d8
+size 62612
diff --git a/marked/H/T-REC-H.644.8-202406-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/H/T-REC-H.644.8-202406-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..744cc2bc97af2cecdf2afdeffe76609887b1ed88
--- /dev/null
+++ b/marked/H/T-REC-H.644.8-202406-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b902e696d119991f65615d381eb350bac11f5e42dc559893c09b24e14b4f8697
+size 88492
diff --git a/marked/H/T-REC-H.644.8-202406-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/H/T-REC-H.644.8-202406-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5d6897ebe56366acbb192b58fbae2c8e29927d94
--- /dev/null
+++ b/marked/H/T-REC-H.644.8-202406-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:21c88fb3586a450f3b55abea8e5e48257645ff0dd4deec05c909578cb993a499
+size 199902
diff --git a/marked/H/T-REC-H.644.8-202406-I_PDF-E/raw.md b/marked/H/T-REC-H.644.8-202406-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..4103c3a4ec55c357b40d2a0ee85555876f21ccb0
--- /dev/null
+++ b/marked/H/T-REC-H.644.8-202406-I_PDF-E/raw.md
@@ -0,0 +1,891 @@
+
+
+# Recommendation**ITU-T H.644.8 (06/2024)**
+
+SERIES H: Audiovisual and multimedia systems
+
+Broadband, triple-play and advanced multimedia services –  
+Content delivery and ubiquitous sensor network applications
+
+# --- **Requirements and architecture for audio and video processing for media processing services**
+
+![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 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        |
+| <b>Content delivery and ubiquitous sensor network applications</b> | <b>H.640-H.649</b> |
+| 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.644.8
+
+# Requirements and architecture for audio and video processing for media processing services
+
+## Summary
+
+Given the requirements of recently developed video services, media contents are required to be processed before transmission through a content delivery network (CDN). For example, media contents are required to be transcoded adaptively according to the quality of the network. Some user generated contents (UGCs) are required to not include specific contents, while other image and text contents are required to be detected, located and identified in order to provide personalized services for consumers.
+
+The media processing service (MPS) is based on the concept of cloud computing technology and provides a cost-effective, easy-to-use, elastic, on-demand and highly scalable method to process audio and video in various video-related services. Recommendation ITU-T H.644.8 identifies requirements and architecture for audio and video processing via a management platform for the media processing service.
+
+## History\*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T H.644.8  | 2024-06-13 | 16          | 11.1002/1000/15932 |
+
+## Keywords
+
+Audio processing, management platform, media processing service, video processing.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                              | 2    |
+| 4 Abbreviations and acronyms .....                                         | 2    |
+| 5 Conventions .....                                                        | 3    |
+| 6 Introduction .....                                                       | 3    |
+| 7 Management platform.....                                                 | 4    |
+| 7.1 Architecture .....                                                     | 4    |
+| 7.2 Core functions of platform .....                                       | 6    |
+| 7.3 Platform operations and maintenance (O&M) functions .....              | 11   |
+| 7.4 Platform generic capabilities .....                                    | 12   |
+| 8 Audio processing subfunctional block .....                               | 15   |
+| 8.1 Basic requirements for service .....                                   | 15   |
+| 8.2 Requirements for infrastructure-oriented adaptation capabilities ..... | 15   |
+| 8.3 Key capabilities for audio processing.....                             | 16   |
+| 8.4 Key performance metrics .....                                          | 17   |
+| 8.5 Requirements for supporting service operation capability .....         | 17   |
+| 8.6 Requirements for supporting O&M capabilities .....                     | 18   |
+| 8.7 Requirements for supporting security assurance capability .....        | 18   |
+| 8.8 Requirements for supporting completeness capability.....               | 19   |
+| 9 Video processing subfunctional block.....                                | 20   |
+| 9.1 Basic requirements for service .....                                   | 20   |
+| 9.2 Requirements for infrastructure-oriented adaptation capabilities ..... | 21   |
+| 9.3 Key capabilities for video processing.....                             | 22   |
+| 9.4 Key performance metrics .....                                          | 24   |
+| 9.5 Requirements for supporting service operation capability .....         | 24   |
+| 9.6 Requirements for supporting O&M capabilities .....                     | 25   |
+| 9.7 Requirements for supporting security assurance capability .....        | 25   |
+| 9.8 Requirements for supporting completeness capability.....               | 27   |
+| Bibliography.....                                                          | 28   |
+
+
+
+# Recommendation ITU-T H.644.8
+
+## Requirements and architecture for audio and video processing for media processing services
+
+# 1 Scope
+
+This Recommendation specifies the requirements and architecture for audio and video processing via a management platform for the media processing service (MPS) and includes:
+
+- Requirements and architecture for audio processing.
+- Requirements and architecture for video processing.
+- Requirements and architecture for the management platform.
+- Other requirements and architecture for media processing 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 F.746.17] Recommendation ITU-T F.746.17 (2022), *Requirements for media processing services*.
+
+[ITU-T H.644.7] Recommendation ITU-T H.644.7 (2023), *Functional architecture for media processing services*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 media processing service (MPS)** [ITU-T F.746.17]: A cloud service for transcoding multimedia data, which can provide a cost-effective, easy-to-use, elastic, and highly scalable method to convert audio and video into formats suitable for playing on PCs, TVs and mobile interfaces, and can also conduct deep learning based technology on massive data to analyse the content including text, voice and other scenarios of the media in multiple modes, and to achieve intelligent review, content understanding, intelligent editing, etc.
+
+**3.1.2 artificial intelligence (AI)** [b-ITU-T F.749.13]: An interdisciplinary field, usually regarded as a branch of computer science, dealing with models and systems for the performance of functions generally associated with human intelligence, such as reasoning and learning.
+
+**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.
+
+**3.1.4 content delivery network (CDN)** [b-ITU-T F.750]: A network optimized for delivering digital content.
+
+**3.1.5 platform as a service (PaaS)** [b-ITU-T Y.3500]: Cloud service category (see clause 3.2.10 in [b-ITU-T Y.3500]) in which the cloud capabilities type (see clause 3.2.4 in [b-ITU-T Y.3500]) provided to the cloud service customer (see clause 3.2.11 in [b-ITU-T Y.3500]) is a platform capabilities type (see clause 3.2.31 in [b-ITU-T Y.3500]).
+
+**3.1.6 infrastructure as a service (IaaS)** [b-ITU-T Y.3500]: Cloud service category (see clause 3.2.10 in [b-ITU-T Y.3500]) in which the cloud capabilities type (see clause 3.2.4 in [b-ITU-T Y.3500]) provided to the cloud service customer (see 3.2.11 in [b-ITU-T Y.3500]) is an infrastructure capabilities type (see clause 3.2.25 in [b-ITU-T Y.3500]).
+
+## **3.2 Terms defined in this Recommendation**
+
+None.
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|       |                                         |
+|-------|-----------------------------------------|
+| 2B    | To Business                             |
+| 2C    | To Consumer                             |
+| ABR   | Available Bitrate                       |
+| AI    | Artificial Intelligence                 |
+| ASIC  | Application Specific Integrated Circuit |
+| CBR   | Constant Bitrate                        |
+| CDN   | Content Delivery Network                |
+| CPU   | Central Processing Unit                 |
+| CU    | Compute Unit                            |
+| CU1   | Unit of Reference CU                    |
+| CUDA  | Compute Unified Device Architecture     |
+| DDoS  | Distributed Denial of Service           |
+| DRM   | Digital Rights Management               |
+| DTS   | Decoding Time Stamp                     |
+| FPGA  | Field Programmable Gate Array           |
+| FRC   | Frame Rate Conversion                   |
+| GPU   | Graphics Processing Unit                |
+| HDR   | High Dynamic Range                      |
+| HTTP  | Hyper Text Transfer Protocol            |
+| HTTPS | Hypertext Transfer Protocol Secure      |
+| IaaS  | Infrastructure as a Service             |
+| ID    | Identifier                              |
+| IT    | Information Technology                  |
+| I/O   | Input/Output                            |
+| MPS   | Media Processing Service                |
+| Mutex | Mutual exclusion                        |
+
+|       |                                     |
+|-------|-------------------------------------|
+| NAS   | Network Attached Storage            |
+| O&M   | Operation and Maintenance           |
+| OSS   | Object Storage Service              |
+| PaaS  | Platform as a Service               |
+| PC    | Personal Computer                   |
+| PIP   | Picture in Picture                  |
+| POSIX | Portable Operating System Interface |
+| PTS   | Presentation Time Stamp             |
+| QoS   | Quality of Service                  |
+| RAM   | Random Access Memory                |
+| RTMP  | Real Time Messaging Protocol        |
+| SaaS  | Software as a Service               |
+| SDR   | Standard Dynamic Range              |
+| SLA   | Service-Level Agreement             |
+| SMS   | Short Message Service               |
+| TV    | Television                          |
+| UGC   | User Generated Content              |
+| VBR   | Variable Bitrate                    |
+| VM    | Virtual Machine                     |
+
+# 5 Conventions
+
+In this Recommendation:
+
+- The keywords "functional block" indicate the top granularity used in function division in schematic of functional architecture for specific platform/system. It generally includes a further division.
+- The keywords "subfunctional block" indicate the medium granularity used in function division in schematic of functional architecture for specific platform/system. It is included in a functional block. It can include more-subdivided subfunctional block(s) or functional entities.
+- The keywords "functional entity" indicate the least granularity used in function division in schematic of functional architecture for specific platform/system. It is included in a functional block and maybe included in subfunctional block(s).
+
+# 6 Introduction
+
+Media processing service (MPS) supports regular media processing functions as well as the ability to convert video into structured data using the latest artificial intelligence (AI) technologies. It can meet the media processing needs of media files as well as video streams as input. The media processing capabilities are scalable and can be expanded and upgraded to follow technological developments.
+
+# 7 Management platform
+
+### 7.1 Architecture
+
+Figure 7-1 (based on Figure 8-1 in [ITU-T H.644.7]) shows the functional architecture for the MPS. The blocks with grey background (i.e., blocks named as content provider, CDN, end-user, storage, and IaaS) are out of the research scope of this Recommendation.
+
+NOTE – Based on Figure 8-1 in [ITU-T H.644.7], the following Figure 7-1 comprises a correction to the original figure with the positions of "Execute job" and "Job scheduling" switched as per a corrigendum.
+
+![Schematic of functional architecture for the MPS. The diagram shows the flow from Content domain (Content provider) through Processing domain (Application, Media processing, Resource management) to Delivery domain (CDN) and Presentation domain (End-user).](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg)
+
+The diagram illustrates the functional architecture for the Media Processing System (MPS), organized into three main domains: Content domain, Processing domain, and Delivery/Presentation domains.
+
+- Content domain:** Contains the **Content provider** (grey block). It initiates the process via **Submit job** and **Upload** to **Storage** (grey block).
+- Processing domain:** The central part of the MPS, containing three main functional blocks:
+  - Application (Job managing and scheduling):** Includes **Job management**, **Queue management**, and **Job scheduling**. It receives **Entering queues** from Job management and sends **Exiting queues** to Job scheduling. It also receives **Execute job** from Job scheduling.
+  - Media processing:** A large block containing several sub-functions:
+    - Video processing:** Transcoding (Encoding format, Resolution, File format, Live recording, Embedded subtitles, Information insertion, Rotating, ...), Snapshot (Frame snapshot, Batch snapshot), Watermark (Text watermark, Picture watermark), Encryption (Video encryption, DRM), Clipping and stitching (Video stitching, PIP, ...).
+    - AI processing:** Multimodal analysis (Face filters, Speech recognition, Character recognition, Video tagging, Specific content detection, ...).
+    - Audio processing:** Automatic gain control, Automatic noise suppression, Acoustic echo canceller, Audio mixing, ...
+  - Resource management:** Includes **Execution management**, **Node management**, **Workload management**, **Service nodes**, and **Elastic scaling management**. It receives **Execute job** from Job scheduling and interacts with **Service nodes**. It also receives **Stream** from the Content provider and sends **Stream** to the CDN. It interacts with **Storage** (Upload/Download) and **IaaS** (grey block).
+- Delivery domain:** Contains the **CDN** (grey block), which receives **Stream** from the Processing domain and sends it to the **End-user** (grey block) in the **Presentation domain**.
+
+Additional interactions include **Download** from **Storage** to **Content provider** and **Download** from **CDN** to **Storage**.
+
+Schematic of functional architecture for the MPS. The diagram shows the flow from Content domain (Content provider) through Processing domain (Application, Media processing, Resource management) to Delivery domain (CDN) and Presentation domain (End-user).
+
+H.644.8(24)
+
+**Figure 7-1 – Schematic of functional architecture for the MPS**
+
+The media processing domain is the core link of the MPS and belongs to the cloud-centric deployment. It consists of three main functional blocks: the application (job managing and scheduling) functional block, the resource management functional block, and the media processing functional block. Storage is used to store media files. Infrastructure as a service (IaaS) provides infrastructure such as containers, machines, etc.
+
+The application (job managing and scheduling) functional block consists of three functional entities: job management, queue management, and job scheduling. Job management is responsible for the life cycle of the jobs. Queue management is responsible for the life cycle of queues and the functions of entering queues and exiting queues. Job scheduling is responsible for making decisions on when a job will be executed according to the information provided by the execution management function in the resource management functional block.
+
+The media processing functional block consists of three main subfunctional blocks: video processing, audio processing and AI processing. Video processing mainly includes transcoding, snapshot, watermark, encryption, clipping and stitching functional entities. Audio processing mainly includes automatic gain control, automatic noise suppression, acoustic echo canceller, and audio mixing functional entities. AI processing mainly includes multimodal analysis and specific content detection functional entities. The function of the media processing functional block is capable of expanding and upgrading with the development of technology.
+
+The resource management functional block consists of five functional entities: execution management, nodes management, workload management, service nodes and elastic scaling management. Execution management evaluates the overall load of the resource pool through the information provided by nodes management and workload management. After receiving the scheduled job, execution management selects the appropriate node for execution according to comprehensive information such as job type. Elastic scaling management is responsible for interacting with the infrastructure as a service (IaaS) layer and adjusting the water level of the resource pool according to the peak and valley of the service, to meet the peak demand of the service and improve the overall utilization rate. Service nodes is a set of service nodes and is a logical node deployed in a physical machine to execute MPS.
+
+The management platform is related to large-scale computing for MPS (belonging to the platform as a service (PaaS) layer), which should be able to provide large-scale computing capabilities by utilizing the IaaS layer as well as shielding the IaaS layer from the variability of different implementations. For the upper software as a service (SaaS) layer it is important to provide higher levels of domain abstraction, scalable processing and integrated capabilities, and the ability to support multi-tenant, elasticity, etc.
+
+The management platform refers to the orchestration and configuration management of the functional processes of user' jobs, as well as the control of the status, progress, and resources consumed during the processing of services within functional modules. It is mainly oriented to business (2B) users. It is used to help business users effectively configure, monitor, control, and manage the service processes, job tasks, system resources, and related IT infrastructure for each functional module of the MPS.
+
+The management platform, supported by the infrastructure, mainly includes core function modules such as job management, scheduling management (belonging to the application functional block), resource management, and cluster management.
+
+Cluster management sits between the IaaS and resource management functional block in the overall architecture of Figure 7-1 (i.e., Figure 8-1 in [ITU-T H.644.7]), which is used to manage multiple IaaS instances (multi-vendor or multi-region). The system architecture is schematically shown in Figure 7-2.
+
+![Schematic diagram of the management platform architecture showing layers for User, Job management, Scheduling management, Resource management, and Cluster management (IaaS).](d4af765160d04ecef538e5066006dc77_img.jpg)
+
+The diagram illustrates the management platform architecture, organized into five horizontal layers separated by dashed lines:
+
+- User:** Represented by three smiley face icons at the top, with an arrow pointing down to the Job management layer.
+- Job management:** Contains a central 'Job' box. Below it, 'Input' and 'Processing type and parameter' are shown, with another 'Input' box to the right. Arrows point from the 'Job' box to these elements.
+- Scheduling management:** Contains a 'Scheduling' box. Below it, 'User queue' is shown with three vertical columns of boxes, each containing three small squares. An arrow points from the 'Scheduling' box to the 'User queue'.
+- Resource management:** Contains an 'Execution node' box. Inside, there are three boxes: 'Video processing', 'Audio processing', and 'AI processing'. Below these are four boxes: 'CPU', 'GPU', 'FPGA', and 'ASIC', each with an ellipsis (...) below it. An arrow points from the 'User queue' to the 'Execution node'.
+- Cluster management:** Contains an 'IaaS' box at the bottom. An arrow points from the 'Execution node' to the 'IaaS' box.
+
+External components and interactions:
+
+- Storage:** A cylinder icon labeled 'Storage' is connected to the 'Execution node' via a double-headed arrow labeled 'File'.
+- Real-time streaming:** A double-headed arrow labeled 'Real-time streaming' connects the 'Execution node' to a 'Push/Pull streaming' icon (a fish) and a 'Displaying' icon (a play button).
+
+The label 'H.644.8(24)' is located at the bottom right of the diagram.
+
+Schematic diagram of the management platform architecture showing layers for User, Job management, Scheduling management, Resource management, and Cluster management (IaaS).
+
+**Figure 7-2 – Schematic diagram of the management platform architecture**
+
+Users use media files or streams as inputs and submit processing requirements (processing types, processing parameters including related configurations) to job management. Scheduling management provides multi-tenant scheduling capabilities and is responsible for submitting jobs to specific computing nodes (i.e., resources) for execution when the pool of resources meets the job requirements. Lastly, cluster management accomplishes node scaling up and scaling down by coordinating with the IaaS layer to provide large-scale and elasticity capability.
+
+### 7.2 Core functions of platform
+
+#### 7.2.1 Job management
+
+Job management is responsible for the lifecycle of a job and persists the job state, driving the job to complete the entire lifecycle according to the job state.
+
+Job is the smallest unit of management and execution, including input, output and processing parameters. Input and output support both file and stream. File is often used for non-real-time offline processing (such as on-demand). Stream is often used for real-time online processing (such as live, video conferencing). The states include "Submitted", "Queued", "Executing", "Completed" (contains both "Success" and "Failure" results) and "Stopped". After the job is submitted, it is in the "Submitted" state. After the job is scheduled, it is in the "Queued" state. When it starts to execute, it is in the "Executing" state. After it finishes, it is in the "Completed" state. If a job is submitted but not completed, it can be stopped, and its state after stopping is the "Stopped" state.
+
+The job has the required resource requirement and the required computing resource quota, for example, a resource requirement such as some model/performance of graphics card, and computing resource quota such as 1G bytes graphics memory, 30% compute unified device architecture (CUDA) graphics card cores.
+
+Related requirements for the job management function are described in Table 7-1.
+
+**Table 7-1 – Requirements for job management function**
+
+| Function name                                                                   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Submit job                                                                      | <p>Input (support multiple)/output file/stream.</p> <p>Processing requirements (specific processing types and related parameters), such as audio/video transcoding, encapsulation formats, etc.</p> <p>The system distinguishes between administrators and users by the different rights of users. For users, the system does not make user type classification. 2B and 2C can use the same interface. At present, it is mainly used for 2B users. Users input and select various service parameters on the console interface to determine the service requirements.</p> <p>Scheduling requirements (specify priority and queue for job).</p> <p>Successful creation will return the job ID which is a unique identifier for the job.</p> <p>Failure to create will return an error code and error description information (returned via different fields in JSON format).</p> |
+| Query job                                                                       | <p>Query the job based on the job ID:</p> <p>Progress: percentage</p> <p>State: "Submitted", "Queued", "Executing", "Completed" (contains both "Success" and "Failure" results)</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| Stop job                                                                        | <p>A job can be stopped in the "Executing" or "Queued" states according to the job ID, and the job state can be changed to "Stopped".</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| Delete job                                                                      | <p>Delete job with a "Completed" state based on the job ID.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| NOTE – Job ID and queue ID are managed and assigned by the management platform. |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+#### 7.2.2 Scheduling management
+
+##### Scheduling
+
+Scheduling makes decisions about the timing of job execution based on information provided by resource management and is responsible for coordinating resource allocation strategy among multi-tenants or among different types of jobs. It can judge the overall load of the system based on the overall situation of job execution and queuing. Based on the elasticity strategy and cost considerations, it can choose to call the resource management functional block for dynamic expansion and contraction of resources at a suitable time.
+
+#### Queue management
+
+Queue management is responsible for the lifecycle of jobs in the queue and persists the state of the queue and job queuing. It provides the management of the queue itself and the two core interfaces i.e., entering queues and exiting queues. Jobs in the queue support prioritization. Jobs with high-priority can be prioritized.
+
+Queue is a virtual concept. Its management method has 2 dimensions: user and type.
+
+Each user can have one or more queues, and the time exiting of each queue can be individually controlled, so that job isolation and resource allocation function can be realized for a single user as well as multi-tenant.
+
+Queues can also be subdivided into several types based on specific processing requirements: video/audio processing queues, AI processing queues, etc.
+
+In the job design, it is also necessary to consider abnormal job execution and abnormal nodes. In the event of abnormal job execution, it is necessary to choose to restart the job or to set the job state to
+
+"Failure" according to the situation. Table 7-2 describes the requirements for the queue management function.
+
+**Table 7-2 – Requirements for queue management function**
+
+| Function name                                                                   | Description                                                                                                                                                                                                                                                                               |
+|---------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create queue                                                                    | Create a queue for the user. When creating a successful queue will return the queue ID which is a unique identifier of the queue, and when creating a failure will return an error code and error information.                                                                            |
+| Query queue                                                                     | Query based on queue ID: <ul style="list-style-type: none"> <li>– Basic attributes of the queue (e.g., name, attributed user)</li> <li>– Queuing situation of jobs (i.e., number)</li> </ul>                                                                                              |
+| Pause queue                                                                     | Pausing the execution of jobs in the queue according to the queue ID, all jobs that have not started execution are paused, and jobs under executing are not affected.                                                                                                                     |
+| Delete queue                                                                    | Deleting a queue based on the queue ID, the jobs in the queue are deleted and executed jobs are not affected.                                                                                                                                                                             |
+| Entering queues of job                                                          | Submitted jobs are accepted by the scheduling system only after they have successfully entered queues, and then choose when to start executing based on the job's demand on resources, the scheduling's strategy, and the specific situation of load on the resources.                    |
+| Exiting queues of job                                                           | Once the job is exited from the queue, it enters the real execution phase. The required resources from the computing resources provided by the resource management will be allocated to this job, and then the computing resources will be returned after the job execution is completed. |
+| NOTE – Job ID and queue ID are managed and assigned by the management platform. |                                                                                                                                                                                                                                                                                           |
+
+#### 7.2.3 Resource management
+
+Resource management is mainly to provide virtual computing nodes for scheduling management so that scheduling can avoid strong coupling with specific IaaS in architecture design, and so can realize decoupling, interoperability and sharing.
+
+The node is a virtual concept corresponding to an actual physical machine or to a virtual machine (VM) instance. All virtual nodes form a resource pool, and each node supports multiple types of resource definitions such as central processing unit (CPU), graphics processing unit (GPU), field programmable gate array (FPGA), application specific integrated circuit (ASIC), etc. Resource management cannot only manage the state of the nodes in the resource pool, but can also provide a more fine-grained allocation of computing resources provided by the nodes (e.g., number of CPU cores, memory/graphics memory, network/disk I/O, etc.) in order to provide the scheduling management with the allocation, and the return of the computing resources required for job execution.
+
+The allocation of resources is based on a virtual unit i.e., a compute unit (CU) and it is generally recommended that  $1\text{CU} = 1\text{ core CPU} + 4\text{G memory}$  (which can be defined differently according to different scenarios, e.g.,  $1\text{CU for GPU} = 1\text{ core GPU} + 4\text{G graphics memory}$ ). It is recommended to give the value of CU corresponding to the common processing functions, so as to estimate the number of CU consumed according to the actual usage.
+
+Various abnormalities (such as reboots, network disconnects, machine crashes, etc.) need to be considered in the node design as they will affect the jobs under execution when they occur. The scheduling management function also should be notified when an abnormality occurs so that the execution of the job can be resumed. At the same time, resource management will also take the initiative to scan the heartbeat health status of each node regularly. According to the heartbeat signalling timeout and other mechanisms it can be determined whether some nodes may have
+
+experienced machine abnormalities or service abnormalities. Once an abnormality occurs, the node concerned will automatically go offline, and the resource management function will monitor and alert, and also re-schedule the job to facilitate the resumption of the execution of the job. Table 7-3 describes requirements for the resource management function.
+
+**Table 7-3 – Requirements for the resource management function**
+
+| Function name      | Description                                                                                                                                                                                                                                                                                                                                                |
+|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Register node      | Add a new node to the resource pool and return the node ID which is a unique identifier for the node.                                                                                                                                                                                                                                                      |
+| Delete node        | Delete a node based on its node ID. Nodes will not be allowed to be deleted if they already have allocated resources. Deletion must be allowed by clearing the resource interface and waiting for all jobs in execution to be completed.                                                                                                                   |
+| Query node         | Query based on node ID:<br>State (online, offline, deleted)<br>Resource allocation state (total resources, allocated resources and list details).                                                                                                                                                                                                          |
+| Node heartbeat     | Nodes update their online state regularly via heartbeat. The resource management service will decide whether the node is abnormal or not based on the latest updated state of the node. That is, the node can actively report its abnormality (e.g., go offline voluntarily), or the resource management service will scan the node state to determine it. |
+| Allocate resource  | Provide:<br>Number of resource requests (e.g., number of CPU cores)<br>Returns the node ID and the allocation ID which is a unique identifier for this resource allocation). Resource management will choose the allocation algorithm based on its own strategy (e.g., average allocation or centralized allocation, etc.).                                |
+| Return of resource | Resources are returned based on node ID and allocation ID. Scheduling management will return the resources after the job execution is completed.                                                                                                                                                                                                           |
+| Empty resource     | All allocated resources in a node can be returned at once. But before actually completing the clearing process, for the job being executed in this node must be waited to be completed. When emptying resources, user can choose to wait or force the execution of the job to stop.                                                                        |
+
+#### 7.2.4 Cluster management
+
+The clustering of resources should be able to leverage the IaaS layer to provide large-scale computing resources as well as shielding the IaaS layer from the variability of different implementations. Cluster management is specifically responsible for interacting with the infrastructure layer to perform elastic scaling of the overall resource pool. The architecture needs to be designed to avoid coupling with specific IaaS implementations and to work with different IaaS providers in order to support a wider range of infrastructures.
+
+Cluster management mainly defines interfaces related to computing resources. Table 7-4 describes requirements for the cluster management function.
+
+**Table 7-4 – Requirements for the cluster management function**
+
+| Function name | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Expansion     | <p>When calling the newly added node interface of the infrastructure layer (IaaS) service, IaaS performs initialization work on the node for basic environments (such as operating system and others) and then adds the node to the resource pool for resource management.</p> <p>Needs to specify:<br/> Type of node (e.g., CPU, GPU, FPGA, ASIC, etc.)<br/> Specifications of the node (e.g., 16-core CPU, 32G RAM, 100G disk, etc.)<br/> The number of nodes.</p> |
+| Contraction   | <p>The node deletion operation is first logically performed from the resource pool of resource management, and then the release of physical resources is performed at the infrastructure layer (IaaS).</p>                                                                                                                                                                                                                                                           |
+
+The only metric of a cluster's elasticity performance is the timeliness for elastic expansion and contraction. In the case of elastic expansion, this can be metered from the time when the expansion interface is called until the expanded resource is able to provide the service. This period of time can be used to meter the elasticity of scaling. The elasticity of scaling is not only related to the design and implementation of the system, but also to the existence of the required resources at the infrastructure layer (IaaS). The timeliness of elasticity can affect the cost of the system and even the efficiency of the media processing multiplier. For example, the number of nodes required for sliced offline media processing is likely to be the number of nodes required for great elastic capability.
+
+#### 7.2.5 Requirements of infrastructure to support a management platform
+
+Infrastructure is the basic environment for the operation of the management platform. The IaaS contains three major parts namely computing, storage, and network. IaaS connects to the resource management functional block.
+
+In addition to computing and network, the management platform needs to make certain requirements for storage services. The input and output content of media processing will involve storage services. Storage generally has two types namely file storage and object storage. Table 7-5 describes requirements for the object storage function while Table 7-6 describes requirements for the file storage function.
+
+**Table 7-5 – Requirements for the object storage function**
+
+| Function name         | Description                                                                                                                                                                                                                                                                                                                                      |
+|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Object storage-Bucket | <p>A container for storing objects, all of which must belong to a storage space. Storage space has various configuration attributes, including locale, access rights, storage type, etc. Users can create different types of storage space to store different data according to actual needs.</p>                                                |
+| Object storage-Object | <p>The basic unit for storing data, also known as a file. An object consists of object meta, data, and key. Objects are identified by a unique key within the storage space. Object meta information is a set of key-value pairs that represent some attributes of the object, such as final modification time, size, and other information.</p> |
+
+Object storage is suitable for storing any type of file, and provides a storage architecture with high performance, high reliability, cross-platform, and secure data sharing.
+
+**Table 7-6 – Requirements for the file storage function**
+
+| <b>Function name</b>                       | <b>Description</b>                                                                                                                                             |
+|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Network Attached Storage (NAS)-File system | Manage (create, query, delete) the file system.                                                                                                                |
+| NAS-Mount                                  | Manage mount points and mount to the file system of specific computing nodes. Add, activate, disable, and delete mount points as well as modify rights groups. |
+| NAS-File                                   | POSIX-compliant file interface.                                                                                                                                |
+
+Network attached storage (NAS) is based on the portable operating system interface (POSIX) file interface. It adapts to native operating systems, and provides shared access and so can guarantee data consistency and mutual exclusion (Mutex).
+
+Network is mainly concerned with the network I/O capability for different types of job and scenarios requiring different network bandwidths. In resource management, network I/O may also be a metric of the node's resource capability. For example, when a video with large bitrate needs to be processed offline, in order to meet the timeliness processing requirements, a larger network traffic bandwidth should be provided in order to avoid that the time consumed for downloading the source video is not too long.
+
+## **7.3 Platform operations and maintenance (O&M) functions**
+
+### **7.3.1 Overview**
+
+The management platform basically consists of four parts: job management, scheduling management, resource management and cluster management. The upper-level service caller mainly submits jobs through the job management module, and then the following processing modules are mainly based on the resources (i.e., processing units) scheduled by the management platform to carry out video-audio, AI and other types of processing. In other words, the other modules of the platform run in a background mode to the external callers (service) and users (video-audio, AI processing units) without reflecting the number of scheduling resources and the progress of processing jobs. The suddenness of the service and some other factors may cause the platform resources to be insufficient, so the platform should have operation and maintenance (O&M) functions e.g., alarms and monitors, etc.
+
+#### **7.3.2 Log collection**
+
+Different service modules need to print their respective logs and collect them, and then manage and cascade these centrally collected logs to build a link-wide log system.
+
+The log collection of each service module needs to include at least the following points.
+
+- Module name: Indicates which module belongs to the management platform.
+- Time: The point in time when the log is generated, accurate to milliseconds.
+- Job ID: The ID of the job submitted by the service side.
+- Subtask name: The name of each subtask module after each module may be split into different subtasks.
+- Subtask state: e.g., "Success", "Failure", "Executing", etc.
+- Detailed information: Detailed information of each job.
+
+The centre has a log service collecting from each service module, and storage for query (usually a common log collection and management system is used and this system is not described in this Recommendation). Simultaneously, the log data can be linked to establish an end-to-end full-link log
+
+system that includes process data from the 'service job be submitted' to the 'service job to be completed'. This would facilitate the job traceability and state queries, etc.
+
+#### 7.3.3 Monitoring alarms
+
+All monitoring alarms are basically set for logs, so there is a certain delay during log collecting, gathering and monitoring, and the alarms are required to be set within 30 seconds.
+
+Monitoring alarms need to provide configurable threshold settings for alarms. The value below the threshold is safe, while above the threshold an alarm occurs.
+
+Alarm types include instant messaging group alarms, SMS alarms, e-mail alarms, and phone alarms. When 3 consecutive written alarms (such as: instant messaging groups/SMS/e-mail alarms) do not incur a response or when the alarms are not deactivated/released, then the phone will trigger an alarm and alarms will be upgraded and expanded.
+
+For the management platform, monitoring alarms include at least the following problem items which can trigger alarms:
+
+- Job list blockage/timeout.
+- Job failure rate.
+- Resource water level exceeds the safety limit line (i.e., water level alarm).
+- Resource variety (increase/decrease) hour-on-hour/day-on-day/week-on-week ratio.
+- Node unintentional offline rate.
+
+#### 7.3.4 Water level management
+
+The water level of resources is the physical basis on which jobs can be executed, and a burst of service scenarios can reveal resources to be insufficient. Excessive resources will affect costs. Insufficient resources will result in insufficient response to volatility and a burst of jobs.
+
+The water level value is a pre-condition for elastic expansion or contraction on resource capacity, while the elasticity timeliness determines the safety limit line (i.e., threshold) of the resource water level.
+
+Water level alarms need to categorize water levels for different resource types and set different thresholds for alarms based on service characteristics. Details of alarms can be found in clause 7.3.3.
+
+## 7.4 Platform generic capabilities
+
+### 7.4.1 SLA service levels
+
+#### 7.4.1.1 SLA definition
+
+Service-level agreements (SLAs) are required for all types of cloud services. Different services rely on different components and are guaranteed at different levels, and the definition of SLAs represents the quality, level, and performance of the service.
+
+SLA definitions are related to system stability and third-party SLAs (e.g., for databases, IaaS services, etc.), can affect the final revenue and profitability of the platform.
+
+Offline media processing and real-time streaming processing scenarios are different: offline media processing can be retried, while real-time streaming cannot, consequently the related SLA definitions are different.
+
+SLAs define the process of fault reporting, the level of fault definition, and the service standard corresponding to the fault level.
+
+SLA definitions need to be continuously updated, and at least the following points will be listed:
+
+- Service interface success rate, e.g., 99.999%.
+- Cumulative length of service interface failures/year.
+
+- Job success rate.
+- Job completion timeliness.
+
+#### 7.4.1.2 SLA assurance
+
+Pressure testing, upgrading and maintenance of the platform need to be carried out during the low peak hours of the water level to minimize the impact on the use of online users, and users need to be notified 3~5 days in advance of the time point of the pressure testing of the platform and the aspects that may be affected.
+
+The third-party SLAs that the platform relies on should be sorted. For the third-party service components that provide lower SLAs, it is necessary to increase the SLAs of the shortest board of third-party capability by various means such as adding master and backup, decoupling, etc.
+
+Reading and writing on the database can be realized through dual databases to improve stability and reliability.
+
+Resource nodes are disaster-tolerant through multi-computer room and multi-region methods to improve reliability.
+
+Platform services need to support automatic restart, automatic job migration, and automatic state recovery capabilities to control the scope of service damage with timeliness.
+
+The platform service supports manual job migration capability, which is convenient for upgrading and changing.
+
+The platform service needs to support distributed and segment multiplier processing capability for the processing timeliness of offline video.
+
+Platform service scheduling supports resource heterogeneous serial capability to expand processing capability.
+
+Perfect monitoring and timely response to alarms can improve SLAs and reduce the risk of users reporting faults and damage to quality of service (QoS).
+
+### 7.4.2 Metering
+
+Metering and billing are related, and metering is the basis for product pricing and billing.
+
+Metering needs to be accurate and traceable. Metering can be traced through pre-sets.
+
+The metering information is related to the billing method (e.g., processing time, video play time, etc.) and the billing model (prepaid/post-paid, monthly/yearly, peak/average calculation), and different metering information may need to be captured for different billing methods.
+
+Metering is a measure of the compute units (CUs) consumed by a job, which is a comprehensive multi-dimensional unit of metering, not an actual cost.
+
+Metering length is the actual media play time (which can be simply converted to frames) processed by the job according to the dimensions of the job ID. For example, the system time consumed for transcoding one hour long video may be 10 minutes, but the metering is based on one hour, not 10 minutes. Since the system can support multiplier processing, the computing resources consumed by different multiplier processing resources are different.
+
+The final result of the metering needs to be converted into CUs, the formula for converting CUs is generally described as follows:
+
+$$\text{Total consumption of CU} = \text{unit of reference CU (CU1)} / \text{weighting ratio} \times \text{metering length}$$
+
+Where the "unit of reference CU" (i.e., CU1) refers to the unit of time (seconds or converted to frames) in accordance with different dimensions (such as disk, I/O, memory, etc., according to the shortest board of the various capabilities to be calculated) or functional modules (such as transcoding,
+
+snapshots and other specific service-related functional modules) of the consumed CU for a comprehensive consideration of CU. This value is related with the performance of the service module, efficiency and machine hardware performance, etc. This value is generally obtained from a large number of sample video tests. The results from different service providers are deviated.
+
+The weighting ratio is the proportion of resource costs consumed by the module of the CU1 (i.e., the reference metering module) in the whole processing process.
+
+The CU1 divided by the weighting ratio is the CUs.
+
+Metering is also required to obtain media information according to different types of jobs. The basic factors and approaches when measuring different types of jobs are briefly described below:
+
+- Video-audio: obtain the resolution, frame rate, encoding format, processing time, etc. of the video as a multi-dimensional information input for various metering methods.
+
+In video-audio metering, the number of CUs consumed by the processing of audio is very small compared to the number of CUs consumed by the processing of video, so audio is generally ignored. In order to simplify the metering model in video processing, the dimension with the largest CU consumption (i.e., the largest weighting) for different functions is generally selected to calculate the basic CU1, and then get a CU1 based on the proportion of this dimension in the whole process.
+
+- Pure audio: coding format, audio processing function module (e.g., noise reduction, echo cancellation), etc., as a multi-dimensional information input of various metering methods.
+
+Audio generally consumes less CUs, which is related to many information dimensions. In addition to the above listed coding format and functional modules, but also the bitrate, sound channel, etc., the largest weighting ratio is generally the coding format or relatively more complex functional modules.
+
+- AI: multi-dimensional information inputs for various metering methods are based on functional modules, coding, etc.
+
+AI processing involves general transcoding processing of audio and video, and is more involved in heavy computing complexity of the AI processing module. Consequently in AI metering, the general reference metering module based on the AI functional module, and the length of the job is generally converted according to the frame, rather than time. The length of the video and the number of frames is converted according to the video frame rate  $\times$  duration (seconds), assuming that the length of a video is 3 minutes and 5 seconds, and the frame rate is 25 frames per second, then the total number of frames converted to the number of frames of the video is  $(3 \times 60 + 5) \times 25 = 4\,625$  frames.
+
+Metering can be used to support billing functions. Because the basis of billing for different types of jobs may need to refer to different dimensions, some video processing for example may be more associated with the resolution, so the actual cost consumed by different resolutions is not the same. When billing, it is necessary to determine the billing coefficient based on the size of the resolution. Therefore, in order to expand the system's subsequent billing methods and modes, metering in addition to giving the metering formula and the converted CU, may also need to record the various dimensions information for expanding in the future.
+
+Metering also needs to record the types of job and requirements on attributes, because requirements on attributes for different types of job may require different resources, such as multiplier processing. Too large a multiplier will pose a significant challenge to the elasticity of the platform, while causing the peak amplitude of the resource to be too large, and so it will increase the cost of the platform. For different multipliers, the billing may not be the same. During metering, this item needs to be recorded.
+
+A job has at least one metering log, and a user has multiple jobs, resulting in a metering flow sheet.
+
+Metering logs need to be collected and stored for at least 6 months to facilitate the traceability of the user's measurement journal sheet (i.e., a running log of metering, generally used to reconcile billing statements).
+
+# 8 Audio processing subfunctional block
+
+## 8.1 Basic requirements for service
+
+The MPS supports regular audio processing functions, as well as the use of the latest AI technology to convert audio into structured data. It can meet the media processing requirements of video-audio files and video-audio streams as input, and can separate audio data from them to do relevant audio processing, and then synthesize them with video data to generate complete video-audio files/streams.
+
+![Schematic diagram of audio processing boundary showing four domains: Content, Processing, Delivery, and Presentation.](a3472689858b068ef469213682965325_img.jpg)
+
+The diagram illustrates the flow of media data through four distinct domains, separated by vertical dashed lines. The domains are: Content domain, Processing domain, Delivery domain, and Presentation domain. In the Content domain, a 'Content provider' box is above a server icon labeled 'Media data flow'. A blue arrow points from the server to the Processing domain. In the Processing domain, an 'MPS provider' box contains 'Video processing', 'Audio processing' (highlighted with a red border), and 'AI processing'. Below this box is a server icon with a green light. A blue arrow points from this server to the Delivery domain. In the Delivery domain, a 'CDN provider' box is above a cloud icon. A blue arrow points from the cloud to the Presentation domain. In the Presentation domain, an 'End-user' box is above a monitor icon displaying four video feeds. A blue arrow points from the monitor to the right. The text 'H.644.8(24)' is in the bottom right corner.
+
+Schematic diagram of audio processing boundary showing four domains: Content, Processing, Delivery, and Presentation.
+
+Figure 8-1 – Schematic diagram of audio processing boundary
+
+As shown in the Figure 8-1, from the view of service, audio processing is designed as a subfunctional block service of the MPS functional block. Audio processing belongs to the processing domain, is mainly deployed in the cloud and provides related functional services.
+
+## 8.2 Requirements for infrastructure-oriented adaptation capabilities
+
+The audio processing functional block should comprise the capabilities supporting the resource management, migration, etc. of the cloud platform foundation. The specific capability requirements are shown in Table 8-1.
+
+**Table 8-1 – Basic capability requirements for audio processing subfunctional block**
+
+| Serial number | Item                                   | Sub-item                       | Request                                                                                                                                                                                                                                                             |
+|---------------|----------------------------------------|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1             | Adaptive capability of basic resources | Computing resource             | It is required to support adaptive capability for different specifications of the same type of computing resources. For example, an audio processing service requires a 4-core, 8 GB RAM model, but an 8-core, 16 GB model can be adaptively deployed and serviced. |
+|               |                                        | Storage resource               | It is required to support any type of object storage service (OSS) read and write capabilities.                                                                                                                                                                     |
+|               |                                        | Transport protocol             | <ul style="list-style-type: none"> <li>– It is required to support HTTP and HTTPS and HTTP 2.0 transport protocols.</li> <li>– It is required to support real time messaging protocol (RTMP) transport protocol.</li> </ul>                                         |
+|               |                                        | Container                      | It is required to provide containerized deployment.                                                                                                                                                                                                                 |
+|               |                                        | Resource scheduling capability | It is required to support service state heartbeat reporting capabilities required for resource scheduling.                                                                                                                                                          |
+| 2             | Mobility                               | Cloud host migration           | It is required to support the migration of cloud host for resource scheduling management as well as the capability to migrate processing tasks.                                                                                                                     |
+| 3             | Dependability                          | High availability              | It is required to support the audio processing subfunctional block and can continually provide services normally in the event of failure of computing nodes, storage nodes, network nodes, controlling nodes, etc.                                                  |
+| 4             | Audio synthesis                        | /                              | It is required to support the capability to synthesize audio data into video-audio files.                                                                                                                                                                           |
+| 5             | Audio separation                       | /                              | It is required to support the capability to separate audio data from video-audio files.                                                                                                                                                                             |
+
+## 8.3 Key capabilities for audio processing
+
+Key capabilities for audio processing include audio transcoding, mixing, and audio quality. The specific requirements are shown in Table 8-2.
+
+**Table 8-2 – Requirements for key capabilities of audio processing**
+
+| Serial number | Item              | Sub-item                  | Request                                                                                                                                                                                                                                                                                               |
+|---------------|-------------------|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1             | Audio transcoding | Coding format conversion  | <ul style="list-style-type: none"> <li>– It is required to support the conversion from MP3, AAC, FLAC to MP3, AAC, FLAG coding formats.</li> <li>– For the same type of encoding format, it is required to support changing bitrate (i.e., compression ratio), channel, sample value, etc.</li> </ul> |
+|               |                   | Package format conversion | It is required to support the conversion from 3GP, MP4, M3U8, MPG, WMA to MP4, M3U8, MP3, OGG, FLAC.                                                                                                                                                                                                  |
+|               |                   | Bitrate conversion        | <ul style="list-style-type: none"> <li>– It is required to support the conversion among various specified bitrate settings.</li> </ul>                                                                                                                                                                |
+
+**Table 8-2 – Requirements for key capabilities of audio processing**
+
+| Serial number | Item           | Sub-item               | Request                                                                                                                                                          |
+|---------------|----------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|               |                |                        | – It is recommended to support adaptive bitrate conversion, bitrate following source function, etc.                                                              |
+|               |                | Sample rate conversion | It is required to support conversion such as 4 kHz, 8 kHz, 16 kHz, 44.1 kHz, 48 kHz, etc.                                                                        |
+|               |                | Channel switching      | – It is required to support mono and dual-channel (i.e., stereo) conversion.<br>– It is recommended to support multi-channel (>2-channel) conversion             |
+| 2             | Audio splicing | /                      | It is required to support 2-channel audio data splicing capability and splicing effects (e.g., fade in-out, etc.).                                               |
+| 3             | Mix            | Multi-track mixing     | It is required to support two-track mixing processing.                                                                                                           |
+| 4             | Audio quality  | Loudness               | It is required to support volume adjustment.                                                                                                                     |
+|               |                | Phase                  | It is required to support automatic detection of audio left and right channel phase, intelligent inversion, and phase alignment between left and right channels. |
+|               |                | Echo cancellation      | It is recommended to support the echo cancellation function.                                                                                                     |
+|               |                | Noise reduction        | It is recommended to support intelligent noise reduction.                                                                                                        |
+
+## 8.4 Key performance metrics
+
+Timeliness is one of the key metrics for audio processing services and the following is recommended:
+
+- Audio transcoding: For offline documents, should support at least normal speed (1X) to ensure real-time processing, and the general requirement is 10 times the normal speed (10X). Real-time is required for live streaming.
+- Audio processing: should support at least 5 times the normal speed (5X).
+
+NOTE – Timeliness formula:
+
+Timeliness multiplier = audio source play time (second)/audio processing time (second).
+
+The maximum size of audio sources supported is one of the key metrics for measuring the extreme capabilities and high availability of the audio processing service, and the following is recommended:
+
+- The audio processing service should support processing of 100 hours of audio sources.
+- If this audio processing and video processing are in parallel, then the audio processing must ensure that it is synchronized with the video processing, keeping the decoding time stamp (DTS) consistent with the presentation time stamp (PTS) of the video, with an error of no more than 100 milliseconds.
+
+### 8.5 Requirements for supporting service operation capability
+
+Service operation capability includes billing management and self-service. The specific requirements are shown in Table 8-3.
+
+**Table 8-3 – Requirements for service operation capability**
+
+| Serial number | Item         | Sub-item          | Request                                                                                                                                                                                                                                                                                                                            |
+|---------------|--------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1             | Metering     | Metering accuracy | <ul style="list-style-type: none"> <li>– It is required to support metering capabilities in a variety of ways, such as: number of tasks, length of time, resource consumed by audio processing, length of service, etc.</li> <li>– It is required to support packaging, categorizing, and aggregating of metering data.</li> </ul> |
+| 2             | Self-service | /                 | It is required to support users to query metering data for audio processing, etc.                                                                                                                                                                                                                                                  |
+
+### 8.6 Requirements for supporting O&M capabilities
+
+Operation and maintenance (O&M) capabilities include O&M management mechanisms, hardware resource monitoring, data monitoring, alarm management, role and rights management, tenant management, report management, automated O&M, and one-click cancelling. The specific requirements are shown in Table 8-4.
+
+**Table 8-4 – Requirements for O&M capabilities**
+
+| Serial number | Item                                         | Sub-item | Request                                                                                                                                                                                                                                                                                           |
+|---------------|----------------------------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1             | Monitoring of resources consumed by services | /        | It is required to support viewing the resource consumption of all and individual audio processing tasks, such as CPU, memory, disk, network I/O, etc.                                                                                                                                             |
+| 2             | Data monitoring                              | /        | It is required to support data monitoring and log query services for audio processing, including but not limited to time consumed during task processing, task start/stop time, number of success and failure tasks.                                                                              |
+| 3             | One-click cancelling                         | /        | It is recommended to support one-click cancelling of specified tasks or cancelling all processing tasks under a certain user.                                                                                                                                                                     |
+| 4             | Alarm management                             | /        | It is required to support the following: <ul style="list-style-type: none"> <li>– Alarm levels should be recognizable.</li> <li>– Alarm thresholds should be configurable.</li> <li>– e-mail or SMS notification alarm function.</li> </ul>                                                       |
+| 5             | Disaster recovery management                 | /        | <ul style="list-style-type: none"> <li>– It is required to support the provision of hierarchical disaster recovery program according to the user's service requirements needs.</li> <li>– It is required to provide regular disaster recovery switchover drill mechanism and measures.</li> </ul> |
+| 6             | Automated O&M                                | /        | It is required to support O&M automation including automatic software deployment, updates, etc.                                                                                                                                                                                                   |
+
+### 8.7 Requirements for supporting security assurance capability
+
+The security assurance capability requirements include a security management centre, data security, network security and application security. The specific requirements are shown in Table 8-5.
+
+**Table 8-5 – Requirement for supporting security assurance capability**
+
+| Serial number | Item                       | Sub-item                        | Request                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------|----------------------------|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1             | Security management centre | Resource isolation              | It is required to support resource isolation among different users of the audio processing service, including cloud host, network, and security strategies.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|               |                            | Emergency response and handling | <ul style="list-style-type: none"> <li>– It is required to have security emergency response and handling mechanism and recovery process.</li> <li>– It is required to conduct regular emergency response drills.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| 2             | Data security              | Data access security            | <ul style="list-style-type: none"> <li>– It is required to have measures to deal with multiple authentication failures.</li> <li>– It is required to support role and resource-based grouping access control rights on video-audio or audio file.</li> <li>– It is required to support customized access control strategies.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                            |
+|               |                            | Data privacy                    | It is required to support network isolation of different tenants.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|               |                            | Security situational awareness  | <ul style="list-style-type: none"> <li>– It is required to provide a variety of ways to uncover abnormal behaviour, advanced threats, zero-day attacks, data leakage and other security risks.</li> <li>– It is required to provide data security trend analysis, to display via a visual interface.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                    |
+|               |                            | Data destructibility            | <p>The following are required to be supported:</p> <ul style="list-style-type: none"> <li>– When the user ends the service, the service provider is required to immediately delete the user's data completely, unless there is a special agreement.</li> <li>– During the service process, if the user makes a request for data deletion, the service provider is required to delete the data immediately.</li> <li>– If the user makes a request for clearing the data, the service provider is required to provide the corresponding service.</li> <li>– When the storage device is scrapped, the service provider is required to use demagnetization, destruction and other methods to deal with it.</li> </ul> |
+| 3             | Network security           | /                               | It is required to provide distributed denial of service (DDoS) attack protection services.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| 4             | Application security       | /                               | <ul style="list-style-type: none"> <li>– It is required to provide vulnerability scanning service and to output reports to users.</li> <li>– It is required to provide Web application firewall service.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+## 8.8 Requirements for supporting completeness capability
+
+Service completeness includes consulting service, migration service, delivery service, and rights protection. The specific requirements are shown in Table 8-6.
+
+**Table 8-6 – Requirements for supporting completeness capability**
+
+| Serial number | Item                   | Sub-item                        | Request                                                                                                                                                                                                                                                                                                                   |
+|---------------|------------------------|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1             | Consulting service     | Feasibility analysis consulting | It is required to provide a consulting service for project feasibility analysis, including technical feasibility, economic feasibility, risk factors, etc. to the users.                                                                                                                                                  |
+|               |                        | Project solutions consulting    | It is required to provide consulting to the users on the overall solution of the project (including analysis of the current state of the project background, introduction of product solutions, implementation and quotation).                                                                                            |
+| 2             | Migration program      | /                               | It is required to provide migration programs (including migration methods, migration processes, migration tools, etc.) to users.                                                                                                                                                                                          |
+| 3             | User commitment        | Service availability commitment | It is required to provide values for service availability commitments to users.                                                                                                                                                                                                                                           |
+|               |                        | Data persistence commitments    | It is required to provide values for data persistence commitment.                                                                                                                                                                                                                                                         |
+| 4             | User rights protection | Terms of user                   | <ul style="list-style-type: none"> <li>– Terms and conditions for users.</li> <li>– Service change and termination terms.</li> <li>– Service provider disclaimer.</li> <li>– Service indemnity clause.</li> </ul>                                                                                                         |
+|               |                        | After-sales service             | <ul style="list-style-type: none"> <li>– It is required to provide clarified duration of O&amp;M and upgrading services.</li> <li>– It is required to provide clarified after-sales service methods (e.g., remote, on-site, etc.)</li> <li>– It is required to provide disclosed after-sales service duration.</li> </ul> |
+
+# 9 Video processing subfunctional block
+
+### 9.1 Basic requirements for service
+
+The MPS supports regular video processing capabilities, as well as the ability to convert video into structured data using the latest AI technology. It can meet the media processing requirements of video files and video streams (streaming can include live and on-demand) as input.
+
+![Figure 9-1: Schematic diagram of video processing boundary. The diagram shows four domains: Content domain (Content provider), Processing domain (MPS provider with Video processing, Audio processing, and AI processing), Delivery domain (CDN provider), and Presentation domain (End-user). A media data flow arrow points from the Content provider through the MPS provider, then through the CDN provider, and finally to the End-user. The MPS provider box has 'Video processing' highlighted with a red border. The diagram is labeled H.644.8(24) in the bottom right corner.](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg)
+
+Figure 9-1: Schematic diagram of video processing boundary. The diagram shows four domains: Content domain (Content provider), Processing domain (MPS provider with Video processing, Audio processing, and AI processing), Delivery domain (CDN provider), and Presentation domain (End-user). A media data flow arrow points from the Content provider through the MPS provider, then through the CDN provider, and finally to the End-user. The MPS provider box has 'Video processing' highlighted with a red border. The diagram is labeled H.644.8(24) in the bottom right corner.
+
+**Figure 9-1 – Schematic diagram of video processing boundary**
+
+As shown in the Figure 9-1, from the view of service, video processing is designed as a subfunctional block of the MPS functional block. Video processing belongs to the processing domain, is mainly deployed in the cloud and provides related functional services. Figure 9-1 illustrates the boundaries of the 4 domains along with a brief description of the workflow.
+
+## 9.2 Requirements for infrastructure-oriented adaptation capabilities
+
+The video processing functional block should have the capabilities supporting the resource management, migration of the cloud platform foundation. The specific requirements are shown in Table 9-1.
+
+**Table 9-1 – Basic capability requirements for the video processing subfunctional block**
+
+| Serial number | Item                                   | Sub-item                       | Request                                                                                                                                                                                                                                                           |
+|---------------|----------------------------------------|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1             | Adaptive capability of basic resources | Computing resource             | It is required to support adaptive capability for different specifications of the same type of computing resources. For example, video processing service requires an 8-core 16 GB RAM models, but a 16-core 32 GB model can be adaptively deployed and serviced. |
+|               |                                        | Storage resource               | – It is required to support any type of object storage service (OSS) read and write capabilities.                                                                                                                                                                 |
+|               |                                        | Transport protocol             | – It is required to support the HTTP, HTTPS and HTTP 2.0 transport protocols.<br>– It is required to support the RTMP transport protocol.                                                                                                                         |
+|               |                                        | Containers                     | It is required to provide containerized deployment.                                                                                                                                                                                                               |
+|               |                                        | Resource scheduling capability | It is required to support the service state heartbeat reporting capabilities required for resource scheduling.                                                                                                                                                    |
+
+**Table 9-1 – Basic capability requirements for the video processing subfunctional block**
+
+| Serial number | Item             | Sub-item             | Request                                                                                                                                                                                                             |
+|---------------|------------------|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 2             | Mobility         | Cloud host migration | It is required to support the migration of cloud host for resource scheduling management as well as the ability to migrate processing tasks.                                                                        |
+| 3             | Dependability    | High availability    | It is required to support that the video processing subfunctional block can continually provide services normally in the event of failure of computing nodes, storage nodes, network nodes, controlling nodes, etc. |
+| 4             | Video synthesis  | /                    | It is required to support the capability to synthesize video into audio to produce video-audio files.                                                                                                               |
+| 5             | Video separation | /                    | It is required to support the capability to separate video data from video-audio files.                                                                                                                             |
+
+### 9.3 Key capabilities for video processing
+
+Key capabilities for video processing include video transcoding, video snapshot, video watermarking, video clipping and stitching, video encryption, etc. The specific requirements are shown in Table 9-2.
+
+**Table 9-2 – Requirements for key capabilities of video processing**
+
+| Serial number | Item              | Sub-item                    | Request                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------|-------------------|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1             | Video transcoding | Coding format conversion    | <ul style="list-style-type: none"> <li>– It is required to support converting H.264/AVC, H.265/HEVC, MPEG-4, MJPEG, VP8, VP9, Quicktime, WMV, ProRes to H.264/AVC, H.265/HEVC encoding formats.</li> <li>– It is recommended to support converting H.264/AVC, H.265/HEVC, MPEG-4, MJPEG, VP8, VP9, Quicktime, WMV, ProRes to AVS, AVS2, AVS3, AV1, H.266, VP8, VP9 encoding formats.</li> </ul>           |
+|               |                   | Package format conversion   | It is required to support converting from 3GP, AVI, FLV, MP4, M3U8, m4s, ASF, WMV, MKV, MOV, TS, WebM, MXF to FLV, MP4, M3U8, TS, GIF, WebP, etc.                                                                                                                                                                                                                                                         |
+|               |                   | Bitrate conversion          | <ul style="list-style-type: none"> <li>– It is required to support conversion of various specified bitrate settings.</li> <li>– It is required to support various bitrate control designations such as constant bitrate (CBR), available bitrate (ABR), variable bitrate (VBR), etc.</li> <li>– It is recommended to support adaptive bitrate conversion, bitrate-follow-source function, etc.</li> </ul> |
+|               |                   | Resolution conversion       | <ul style="list-style-type: none"> <li>– It is required to support resolution conversion among 8K, 4K, 1080P, 720P, 480P.</li> <li>– It is recommended to support 2 times super resolution: 720P to 2K and 2K to 4K.</li> </ul>                                                                                                                                                                           |
+|               |                   | Frame rate conversion (FRC) | <ul style="list-style-type: none"> <li>– It is required to support down-sampling frame rate conversion, e.g., 60 fps to 30 fps, 30 fps to 24 fps.</li> <li>– It is recommended to support FRC, up-sampling frame rate conversion, e.g., 30 fps to 60 fps.</li> </ul>                                                                                                                                      |
+
+**Table 9-2 – Requirements for key capabilities of video processing**
+
+| Serial number | Item       | Sub-item                | Request                                                                                                                                                                                                                                                                                  |
+|---------------|------------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|               |            | Picture quality control | – It is recommended to support the interconversion of HDR and SDR, of which HDR supports HDR10, HLG formats.                                                                                                                                                                             |
+|               |            | Video rotation          | – It is required to support manual setting of 90/180/270 degree rotation.<br>– It is recommended to support adaptive conversion of horizontal and vertical screens.                                                                                                                      |
+|               |            | Cropping                | It is required to support specifying origin coordinates (top and left) and width and height to select different areas.                                                                                                                                                                   |
+|               |            | Blackened edge          | – It is required to support specifying coordinates (top and left) and width and height to set the fill range.<br>– It is recommended to support the specification of different colours for filling other than black.                                                                     |
+|               |            | De-interleaving         | It is recommended to support de-interleaving.                                                                                                                                                                                                                                            |
+|               |            | Embedded hard subtitles | – It is recommended to support the function of automatically reading the text content of the subtitle stream in the video and embedding the text into the video figure as a sub figure.<br>– It is recommended to support subtitle streams in the following formats: srt, aas, ssa, etc. |
+| 2             | Snapshot   | Snapshot method         | – It is required to support taking snapshots according to video key frames.<br>– It is recommended to support snapshots at a specified point in time.<br>– It is recommended to support the generation of cover snapshots in conjunction with video content.                             |
+|               |            | Output format           | – It is required to support jpg, png, bmp.<br>– It is recommended to support animated GIFs generated from snapshots of a wide range of video content.                                                                                                                                    |
+|               |            | Black frame detection   | It is recommended to support specifying the recognition threshold of the video content to recognize black frames, to avoid snapshots to generate black screen images.                                                                                                                    |
+|               |            | CSS Sprites             | It is recommended to support stitching of a specified batch of snapshots into a Sprite image.                                                                                                                                                                                            |
+| 3             | Watermarks | Text watermark          | It is required to support setting the font, font size, and colour of the text, specifying the position (X/Y coordinates of the upper left corner, width and height of the watermark) and transparency of the watermark.                                                                  |
+|               |            | Image watermark         | It is required to support specifying the position X/Y coordinates of the upper left corner, width and height of the watermark) and transparency of the image watermark.                                                                                                                  |
+
+**Table 9-2 – Requirements for key capabilities of video processing**
+
+| Serial number | Item                         | Sub-item                     | Request                                                                                                                                                                                                                              |
+|---------------|------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|               |                              | Animated watermark           | It is required to support APNG/MOV videos, specifying the position (X/Y coordinates of the upper left corner, width and height of the watermark) and transparency of the watermark.                                                  |
+| 4             | Video clipping and stitching | Multi-video splicing         | It is required to support specifying the start time and video duration of multiple spliced source videos and also the duration of transcoded output videos.                                                                          |
+|               |                              | Picture in picture (PIP)     | It is required to support setting the position of the PIP video: coordinates (top and left) and width and height.                                                                                                                    |
+|               |                              | Opening and closing of video | Support the addition of opening and closing of video. After processing, it will ensure that the encoding, container, and resolution of the newly added opening, closing of video and original video are unified to the output video. |
+| 5             | Video encryption             | HLS standard encryption      | It is required to support HLS standard encryption (SAMPLE-AES and AES-128 binary file encryption etc.)                                                                                                                               |
+|               |                              | DRM                          | It is recommended to support the ChinaDRM, Widevine solution, and FairPlay solution.                                                                                                                                                 |
+
+### 9.4 Key performance metrics
+
+Timeliness is one of the key performance metrics for video processing services, and clauses 9.4.1 to 9.4.3 present recommended timeliness key performance metrics.
+
+#### 9.4.1 Video transcoding
+
+- Should support at least normal speed (1X) to ensure real-time processing, and the general requirement is 10 times the speed.
+
+#### 9.4.2 Video snapshot/watermark/encryption
+
+- Should support at least 10 times the speed.
+
+#### 9.4.3 Video clipping and stitching
+
+- Should support at least normal speed (1X) to ensure real-time processing, the general requirement is 5 times the speed.
+
+NOTE – Timeliness formula:
+
+Timeliness multiplier = video source play time (second)/video processing time (second).
+
+The maximum size of the supported video source is one of the key metrics for metering the extreme capabilities and its high availability of the video processing service. The following is recommended:
+
+- The video processing service should support the processing of 100 hours of video sources or 400GB video files.
+
+## 9.5 Requirements for supporting service operation capability
+
+The service operation capability includes billing management and self-service. The specific requirements are shown in Table 9-3.
+
+**Table 9-3 – Requirements for service operation capability**
+
+| Serial number | Item         | Sub-item          | Request                                                                                                                                                                                                                                                                                                                            |
+|---------------|--------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1             | Metering     | Metering accuracy | <ul style="list-style-type: none"> <li>– It is required to support metering capabilities in a variety of ways, such as: number of tasks, length of time, resource consumed by video processing, length of service, etc.</li> <li>– It is required to support packaging, categorizing, and aggregating of metering data.</li> </ul> |
+| 2             | Self-service | /                 | It is required to support users to query metering data for video processing, etc.                                                                                                                                                                                                                                                  |
+
+### 9.6 Requirements for supporting O&M capabilities
+
+O&M capabilities include O&M management mechanism, hardware resource monitoring, data monitoring, alarm management, role and rights management, tenant management, report management, automated O&M, and one-click cancelling. The specific requirements are shown in Table 9-4.
+
+**Table 9-4 – Requirements for O&M capabilities**
+
+| Serial number | Item                                         | Sub-item | Request                                                                                                                                                                                                                                                                                           |
+|---------------|----------------------------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1             | Monitoring of resources consumed by services | /        | It is required to support viewing the resource consumption of all and individual video processing tasks, such as CPU, memory, disk, network I/O, etc.                                                                                                                                             |
+| 2             | Data monitoring                              | /        | It is required to support data monitoring and log query services for video processing, including but not limited to time consumed during task processing, task start/stop time, number of success and failure tasks.                                                                              |
+| 3             | One-click cancelling                         | /        | It is recommended to support one-click cancelling of specified tasks or cancelling all processing tasks under a certain user.                                                                                                                                                                     |
+| 4             | Alarm management                             | /        | It is required to support: <ul style="list-style-type: none"> <li>– Alarm levels should be recognizable.</li> <li>– Alarm thresholds should be configurable.</li> <li>– E-mail or SMS notification alarm function.</li> </ul>                                                                     |
+| 5             | Disaster recovery management                 | /        | <ul style="list-style-type: none"> <li>– It is required to support the provision of hierarchical disaster recovery program according to the user's service requirements needs.</li> <li>– It is required to provide regular disaster recovery switchover drill mechanism and measures.</li> </ul> |
+| 6             | Automated O&M                                | /        | It is required to support O&M automation including automatic software deployment, updates, etc.                                                                                                                                                                                                   |
+
+## 9.7 Requirements for supporting security assurance capability
+
+The security assurance capability requirements include security management centre, data security, network security and application security. The specific requirements are shown in Table 9-5.
+
+**Table 9-5 – Requirements for supporting security assurance capability**
+
+| Serial number | Item                       | Sub-item                        | Request                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------|----------------------------|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1             | Security management centre | Resource isolation              | It is required to support resource isolation among different users of the video processing service, including cloud host, network, and security strategies.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|               |                            | Emergency response and handling | <ul style="list-style-type: none"> <li>– It is required to have security emergency response and handling mechanism and recovery process.</li> <li>– It is required to conduct regular emergency response drills.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| 2             | Data security              | Data access security            | <ul style="list-style-type: none"> <li>– It is required to have measures to deal with multiple authentication failures.</li> <li>– It is required to support role and resource-based grouping access control rights permissions on video file.</li> <li>– It is required to support customized access control strategies.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                               |
+|               |                            | Data privacy                    | It is required to support network isolation of different tenants.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|               |                            | Security situational awareness  | <ul style="list-style-type: none"> <li>– It is required to provide a variety of ways to uncover abnormal behaviour, advanced threats, zero-day attacks, data leakage and other security risks.</li> <li>– It is required to provide data security trend analysis, to display via a visual interface.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                    |
+|               |                            | Data destructibility            | <p>The following are required to be supported:</p> <ul style="list-style-type: none"> <li>– When the user ends the service, the service provider is required to immediately delete the user's data completely, unless there is a special agreement.</li> <li>– During the service process, if the user makes a request for data deletion, the service provider is required to delete the data immediately.</li> <li>– If the user makes a request for clearing the data, the service provider is required to provide the corresponding service.</li> <li>– When the storage device is scrapped, the service provider is required to use demagnetization, destruction and other methods to deal with it.</li> </ul> |
+| 3             | Network security           | /                               | It is required to provide DDoS attack protection services.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| 4             | Application security       | /                               | <ul style="list-style-type: none"> <li>– It is required to provide vulnerability scanning service and to output reports to users.</li> <li>– It is required to provide Web application firewall service.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+### 9.8 Requirements for supporting completeness capability
+
+Service completeness includes consulting service, migration service, delivery service, and rights protection. The specific requirements are shown in Table 9-6.
+
+**Table 9-6 – Requirements for supporting completeness capability**
+
+| Serial number | Item                   | Sub-item                        | Request                                                                                                                                                                                                                                                                                                                    |
+|---------------|------------------------|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1             | Consulting service     | Feasibility analysis consulting | It is required to provide consulting service for project feasibility analysis, including technical feasibility, economic feasibility, risk factors, etc. to the users.                                                                                                                                                     |
+|               |                        | Project solutions consulting    | It is required to provide consulting to the users on the overall solution of the project (including analysis of the current state of the project background, introduction of product solutions, implementation and quotation).                                                                                             |
+| 2             | Migration program      | /                               | It is required to provide migration programs (including migration methods, migration processes, migration tools, etc.) to users.                                                                                                                                                                                           |
+| 3             | User commitment        | Service availability commitment | It is required to provide values for service availability commitments to users.                                                                                                                                                                                                                                            |
+|               |                        | Data persistence commitments    | It is required to provide values for data persistence commitment.                                                                                                                                                                                                                                                          |
+| 4             | User rights protection | Terms of user                   | <ul style="list-style-type: none"> <li>– Terms and conditions for users.</li> <li>– Service change and termination terms.</li> <li>– Service provider disclaimer.</li> <li>– Service indemnity clause.</li> </ul>                                                                                                          |
+|               |                        | After-sales service             | <ul style="list-style-type: none"> <li>– It is required to provide clarified duration of O&amp;M and upgrading services.</li> <li>– It is required to provide clarified after-sales service methods (e.g., remote, on-site, etc.).</li> <li>– It is required to provide disclosed after-sales service duration.</li> </ul> |
+
+## Bibliography
+
+- [b-ITU-T F.749.13] Recommendation ITU-T F.749.13 (2021), *Framework and requirements for civilian unmanned aerial vehicle flight control using artificial intelligence.*
+- [b-ITU-T F.750] Recommendation ITU-T F.750 (2005), *Metadata framework.*
+- [b-ITU-T Y.3500] Recommendation ITU-T Y.3500 (2014), *Information technology – Cloud computing – Overview and vocabulary.*
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.701-200903-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/H/T-REC-H.701-200903-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..995ea9a7b56bcf8bc3a53081570e6e4036aed58d
--- /dev/null
+++ b/marked/H/T-REC-H.701-200903-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4db0538824c3b7ced21eb053ae87d17d40931f16fdbe60ebc5ce531594bff8e1
+size 76662
diff --git a/marked/H/T-REC-H.701-200903-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/H/T-REC-H.701-200903-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6823948f4fe7955c62537c58cd69509ba359e83b
--- /dev/null
+++ b/marked/H/T-REC-H.701-200903-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ef5effbb6214d39082db45f0bf276cae421d8aa463a3d14c35d241ebfd111155
+size 133698
diff --git a/marked/H/T-REC-H.701-200903-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/H/T-REC-H.701-200903-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..49bfec389090d8eb3fd90db2e2a6beab5c237280
--- /dev/null
+++ b/marked/H/T-REC-H.701-200903-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:01dc7425ae19e51199ba2e54187c084e372add23aa69fcd98388614d0182575e
+size 122982
diff --git a/marked/H/T-REC-H.701-200903-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/H/T-REC-H.701-200903-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5fce83d9f1549dbfc5cff702e8b1a8890f2fe0fe
--- /dev/null
+++ b/marked/H/T-REC-H.701-200903-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:195964037e648a0e7e45bcea0c38d7baac358990669f3d909331dd3d2fb1e896
+size 87836
diff --git a/marked/H/T-REC-H.701-200903-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/H/T-REC-H.701-200903-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e270a297fe17a0d79d95c670794475347a46a0cb
--- /dev/null
+++ b/marked/H/T-REC-H.701-200903-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:881fab33022b1253a66243fda553057f001cc3e534ffb3a5436529697b35f751
+size 120996
diff --git a/marked/H/T-REC-H.701-200903-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg b/marked/H/T-REC-H.701-200903-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3d7d2c1388317c6fbc04f819b894fa98f420e360
--- /dev/null
+++ b/marked/H/T-REC-H.701-200903-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9903398caaf7376885f774b1d9917ef864432dea324d8302f85e128636f82f71
+size 84682
diff --git a/marked/H/T-REC-H.701-200903-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/H/T-REC-H.701-200903-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7a021616b4a713fecead9a9f0246a03e92a07af5
--- /dev/null
+++ b/marked/H/T-REC-H.701-200903-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4dd0a0924465f2ee8b256a972115fef08658015b39b202a87dea94688505504e
+size 93819
diff --git a/marked/H/T-REC-H.701-200903-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg b/marked/H/T-REC-H.701-200903-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..76273765faed4b983f610e16556018e87749191e
--- /dev/null
+++ b/marked/H/T-REC-H.701-200903-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f9253ac37ae05f460cda0af079ec95f8c46811e96d7614ddfe815af8979d6545
+size 3640
diff --git a/marked/H/T-REC-H.701-200903-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/H/T-REC-H.701-200903-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7700b5b7ff58778be76c352e9e5351c4b607d36d
--- /dev/null
+++ b/marked/H/T-REC-H.701-200903-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a03cb7df89499acddb803c46e119ba566ecb4f38c0a6ad5e9180a622e80d9a30
+size 272309
diff --git a/marked/H/T-REC-H.701-200903-I_PDF-E/raw.md b/marked/H/T-REC-H.701-200903-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..d71707e764219528f9c64c48deb76563a2adad26
--- /dev/null
+++ b/marked/H/T-REC-H.701-200903-I_PDF-E/raw.md
@@ -0,0 +1,879 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.701**
+
+(03/2009)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS  
+IPTV multimedia services and applications for IPTV –  
+General aspects
+
+# --- **Content delivery error recovery for IPTV services**
+
+Recommendation ITU-T H.701
+
+## 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                            |                    |
+| <b>General aspects</b>                                                        | <b>H.700–H.719</b> |
+| 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.701**
+
+# **Content delivery error recovery for IPTV services**
+
+## **Summary**
+
+Recommendation ITU-T H.701 provides content delivery error recovery (CDER) mechanisms for IPTV services. It details the error recovery functions in the IPTV architecture and specifies detailed CDER mechanisms. It also provides guidelines on the applicability of the CDER mechanisms to different IPTV services and network conditions.
+
+## **Source**
+
+Recommendation ITU-T H.701 was approved on 16 March 2009 by ITU-T Study Group 16 (2009-2012) under Recommendation ITU-T A.8 procedures.
+
+## **Keywords**
+
+Content delivery error recovery, forward error correction, retransmission.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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    |
+| 4   | Abbreviations and acronyms .....                                                      | 2    |
+| 5   | Conventions .....                                                                     | 3    |
+| 6   | Introduction .....                                                                    | 3    |
+| 7   | Content delivery error recovery architecture.....                                     | 5    |
+| 7.1 | Content delivery error recovery in IPTV architecture.....                             | 5    |
+| 7.2 | Content delivery error recovery functions.....                                        | 5    |
+| 7.3 | CDER interfaces and protocols .....                                                   | 7    |
+| 7.4 | CDER control functional block.....                                                    | 7    |
+| 8   | Content delivery error recovery mechanisms for streaming.....                         | 7    |
+| 8.1 | General .....                                                                         | 7    |
+| 8.2 | Retransmission .....                                                                  | 8    |
+| 8.3 | Forward error correction.....                                                         | 8    |
+| 8.4 | Hybrid combinations of FEC with retransmissions and feedback .....                    | 9    |
+| 8.5 | Usage guidelines for retransmission and FEC.....                                      | 10   |
+| 9   | Content delivery error recovery for content download services.....                    | 11   |
+| 9.1 | General .....                                                                         | 11   |
+| 9.2 | Retransmission-based mechanism: reliable unicast download with TCP .....              | 11   |
+| 9.3 | FEC-based mechanism: reliable multicast file distribution with FLUTE<br>and FEC ..... | 12   |
+| 9.4 | Retransmission-based file repair procedures.....                                      | 12   |
+|     | Annex A – FEC-based error recovery mechanisms for streaming distribution.....         | 13   |
+| A.1 | Assumptions .....                                                                     | 13   |
+| A.2 | Forward error correction according to [ETSI TS 102 034].....                          | 13   |
+| A.3 | Recommended FEC for linear TV services.....                                           | 15   |
+| A.4 | Recommended FEC for content-on-demand services .....                                  | 16   |
+|     | Annex B – Retransmission-based error recovery mechanisms for streaming delivery ..... | 17   |
+|     | Annex C – Content delivery error recovery for content download services.....          | 18   |
+|     | Appendix I – Evaluation of CDER mechanisms for IPTV services .....                    | 19   |
+| I.1 | Introduction .....                                                                    | 19   |
+| I.2 | Evaluation criteria for multicast linear TV .....                                     | 20   |
+| I.3 | Evaluation criteria for content-on-demand services.....                               | 20   |
+| I.4 | Evaluation criteria for content download services .....                               | 20   |
+
+|                                                                                                          | <b>Page</b> |
+|----------------------------------------------------------------------------------------------------------|-------------|
+| Appendix II – Use cases for content delivery error recovery .....                                        | 21          |
+| II.1    Linear TV service .....                                                                          | 21          |
+| II.2    Tightly coupled content-on-demand service .....                                                  | 23          |
+| II.3    Place-shifting service.....                                                                      | 25          |
+| Appendix III – Evaluation results and recommended parameter settings for error recovery mechanisms ..... | 27          |
+| III.1    FEC according to [ETSI TS 102 034] .....                                                        | 27          |
+| Bibliography.....                                                                                        | 30          |
+
+# Recommendation ITU-T H.701
+
+# Content delivery error recovery for IPTV services
+
+# 1 Scope
+
+The ability to deliver high level of service quality to users is an essential aspect of IPTV services, and thus captured in many IPTV-related requirements. As IPTV services can easily be degraded if the media decoders are exposed to impairments such as packet losses, mechanisms are needed to reliably deliver good IPTV service quality in the presence of such defects.
+
+This Recommendation integrates error recovery in the IPTV architecture, describes specific mechanisms and discusses the applicability of the mechanism to IPTV services and network conditions, and provides recommendations and guidance on their use.
+
+## 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.1541] Recommendation ITU-T Y.1541 (2006), *Network performance objectives for IP-based services*.
+- [ITU-T Y.1910] Recommendation ITU-T Y.1910 (2008), *IPTV functional architecture*.
+- [ITU-T Y.Sup5] ITU-T Y-series Recommendations – Supplement 5 (2008), *ITU-T Y.1900-series – Supplement on IPTV service use cases*.
+- [ARIB STD-B24] ARIB Standard, ARIB STD-B24, *Data Coding and Transmission Specification for Digital Broadcasting*.
+- [ATIS-0800005] ATIS-0800005 (2006), *IPTV Packet Loss Issue Report*.
+- [ETSI TS 102 034] ETSI TS 102 034 v1.3.1 (2007), *Digital Video Broadcasting (DVB); Transport of MPEG-2 TS Based DVB Services over IP Based Networks*.
+- [SMPTE 2022-1] SMPTE specification 2022-1 (2007), *Forward Error Correction for Real-time Video/Audio Transport Over IP Networks*.
+- [IETF RFC 793] IETF RFC 793 (1981), *Transmission Control Protocol*.
+- [IETF RFC 3550] IETF RFC 3550 (2003), *RTP: A Transport Protocol for Real-Time Applications*.
+- [IETF RFC 5052] IETF RFC 5052 (2007), *Forward Error Correction (FEC) Building Block*.
+- [IETF RFC 5053] IETF RFC 5053 (2007), *Raptor Forward Error Correction Scheme for Object Delivery*.
+
+## 3 Definitions
+
+This Recommendation defines the following terms:
+
+**3.1 FEC base layer:** Most important FEC layer. In the context of this Recommendation, this refers to the base layer in the FEC as specified in [ETSI TS 102 034].
+
+**3.2 FEC enhancement layers:** Subsequent FEC layers. In the context of this Recommendation, this refers to the enhancement layers in the FEC as specified in [ETSI TS 102 034].
+
+**3.3 FEC layer:** One FEC stream of multiple ordered FEC streams where support of this layer means that all FEC streams with more important order are also supported.
+
+**3.4 FEC stream:** IP packet stream associated with a media stream that contains redundant data to reconstruct a media stream locally at the IPTV terminal.
+
+**3.5 forward error correction (FEC):** FEC-based CDER mechanisms generate redundant data to allow the IPTV terminal to correct packet losses. With this redundant information, the receivers can recover from packet losses locally at the IPTV terminal.
+
+**3.6 retransmission:** Retransmission-based CDER mechanisms use feedback messages to recover from packet losses.
+
+## **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|          |                                                                                 |
+|----------|---------------------------------------------------------------------------------|
+| ALC      | Asynchronous Layered Coding                                                     |
+| AFEC     | Adaptive FEC                                                                    |
+| ARQ      | Automatic Repeat Request                                                        |
+| ATIS-IIF | Alliance for Telecommunication Industry Solutions – IPTV Interoperability Forum |
+| AVP      | Audio-Visual Profile                                                            |
+| CBR      | Constant Bit Rate                                                               |
+| CDER     | Content Delivery Error Recovery                                                 |
+| DSL      | Digital Subscriber Line                                                         |
+| DVB      | Digital Video Broadcasting                                                      |
+| ECG      | Electronic Content Guide                                                        |
+| EPG      | Electronic Program Guide                                                        |
+| FEC      | Forward Error Correction                                                        |
+| FLUTE    | File delivery over unidirectional transport                                     |
+| FTP      | File Transfer Protocol                                                          |
+| ID       | Identifier                                                                      |
+| IDR      | Instantaneous Decoder Refresh                                                   |
+| IP       | Internet Protocol                                                               |
+| IPDV     | IP Packet Delay Variation                                                       |
+| IPER     | IP Packet Error Ratio                                                           |
+| IPLR     | IP Packet Loss Ratio                                                            |
+| IPTD     | IP Packet Transfer Delay                                                        |
+| IPTV     | IP Television                                                                   |
+| MTBA     | Mean Time Between Artefacts                                                     |
+| NACK     | Negative ACKnowledgement                                                        |
+| QoE      | Quality of Experience                                                           |
+
+|      |                                 |
+|------|---------------------------------|
+| QoS  | Quality of Service              |
+| RMT  | Reliable Multicast Transmission |
+| RTCP | Real-Time Control Protocol      |
+| RTP  | Real-Time Transport Protocol    |
+| RTT  | Round-Trip Time                 |
+| SCP  | Service and Content Protection  |
+| TCP  | Transmission Control Protocol   |
+| TF   | Terminal Function               |
+| TS   | Transport Stream                |
+| TTS  | Timestamped Transport Stream    |
+| UDP  | User Datagram Protocol          |
+| VoD  | Video on Demand                 |
+| XML  | eXtensible Markup Language      |
+
+## 5 Conventions
+
+None.
+
+# 6 Introduction
+
+Content delivery error recovery (CDER) is an important aspect for IPTV services. Data being delivered over IP networks may suffer from packet losses. In case of the delivery of video and audio, data errors, such as packet losses or bit errors being delivered to the media decoder, generally degrade the IPTV service quality. Moreover, losses in metadata such as electronic program guides (EPG), electronic content guides (ECG), and interactive user data may cause more severe problems in IPTV services. Therefore, data reliability support is essential to IPTV services.
+
+This Recommendation addresses the requirement that the IPTV architecture provide a mechanism for resiliency of the service provider infrastructure in order to maintain a high QoE for video services [ITU-T Y.Sup5]. It addresses specific realizations of the content delivery error recovery function and the content delivery error recovery client function in the IPTV architecture [ITU-T Y.1910]. Reference point E4 is used to exchange messages for delivering and requesting error recovery information [ITU-T Y.1910].
+
+The support of content delivery error recovery mechanisms is not required for all networks, in particular for networks that can fulfil the desired IPTV service requirements.
+
+In case that a network cannot fulfil the packet loss requirements necessary to achieve the IPTV service requirements, the use of a content delivery error recovery solution is recommended.
+
+Retransmission, forward error correction (FEC), and hybrid combinations of both are known mechanisms for error recovery. When an error recovery scheme and the associated protocol is selected, at least the following aspects should be taken into account:
+
+- 1) type of IPTV service, e.g., linear TV, content-on-demand, content download, EPG distribution, application data;
+- 2) type of data delivery mechanisms, e.g., broadcast, multicast, unicast, overlay multicast, or peer-to-peer;
+- 3) protocol or processing overhead at senders and receivers;
+- 4) network bandwidth overhead aspects.
+
+This Recommendation is structured as follows:
+
+Clause 7 introduces the content delivery error recovery architecture and provides some high-level descriptions of the involved functional blocks and interfaces.
+
+Clause 8 provides an overview on different CDER mechanisms for streaming, i.e., for solutions in which the media stream is distributed in real-time and consumed at the same time.
+
+Clause 9 provides an overview on different CDER mechanisms for content download services, i.e., for solutions in which a media file is distributed to terminals for later consumption.
+
+This Recommendation also contains several annexes that contain specific recommendations for CDER mechanisms. The first release of this Recommendation is restricted to one annex specifying recommended FEC-based error recovery mechanisms for streaming distribution.
+
+It is expected that in future releases, additional annexes will be added to specify recommendations at least on:
+
+- Retransmission-based error recovery mechanisms for streaming delivery.
+- Content delivery error recovery mechanisms for content download services.
+
+This Recommendation also includes appendices for background information on the evaluation of CDER mechanisms as well as on configuration of specific CDER mechanisms in IPTV networks.
+
+# 7 Content delivery error recovery architecture
+
+## 7.1 Content delivery error recovery in IPTV architecture
+
+![Figure 7-1: Error recovery functions in IPTV architecture [ITU-T Y.1910]. This is a complex block diagram showing the IPTV architecture layers. From top to bottom, the layers are: Application Functions (blue), Service Control Functions (yellow), Content Delivery Functions (orange), and Network Functions (green). On the left, IPTV Terminal Functions (pink) and Home Network Functions (pink) are shown. On the right, Management Functions (grey) and Content Provider Functions (grey) are shown. The diagram details various functional blocks such as 'Application Provisioning', 'Content Processing Control', 'IPTV Service Control', 'Content Distribution & Location Control', 'Authentication & IP Allocation', and 'Multicast Transport Functions'. It also shows data flows for 'Content, Metadata & Control', 'Control', 'Unicast Path', and 'Multicast Path'. Specific error recovery components like 'Error Recovery Client Functional Block' and 'Error Recovery Functional Block' are highlighted in pink.](e9314c83043183351ed74908e9bf2f90_img.jpg)
+
+Figure 7-1: Error recovery functions in IPTV architecture [ITU-T Y.1910]. This is a complex block diagram showing the IPTV architecture layers. From top to bottom, the layers are: Application Functions (blue), Service Control Functions (yellow), Content Delivery Functions (orange), and Network Functions (green). On the left, IPTV Terminal Functions (pink) and Home Network Functions (pink) are shown. On the right, Management Functions (grey) and Content Provider Functions (grey) are shown. The diagram details various functional blocks such as 'Application Provisioning', 'Content Processing Control', 'IPTV Service Control', 'Content Distribution & Location Control', 'Authentication & IP Allocation', and 'Multicast Transport Functions'. It also shows data flows for 'Content, Metadata & Control', 'Control', 'Unicast Path', and 'Multicast Path'. Specific error recovery components like 'Error Recovery Client Functional Block' and 'Error Recovery Functional Block' are highlighted in pink.
+
+Figure 7-1 – Error recovery functions in IPTV architecture [ITU-T Y.1910]
+
+[ITU-T Y.1910] adopts error recovery as an optional function in the content delivery functions in the IPTV architecture in case that the network functions cannot provide sufficient QoS for IPTV services, as shown in Figure 7-1. The error recovery function consists of the content delivery error recovery functional block and the error recovery client functional block. The configure/control interactions between these two functional blocks is established by an error recovery control protocol.
+
+## 7.2 Content delivery error recovery functions
+
+Figure 7-2 shows the content delivery error recovery function and error recovery client function decomposed into constituent functional blocks.
+
+![Diagram of CDER Functions showing IPTV terminal functions and Content delivery and storage functions connected by an Error recovery control protocol.](d4af765160d04ecef538e5066006dc77_img.jpg)
+
+The diagram illustrates the functional architecture of CDER (Content Delivery Error Recovery) functions, divided into two main categories:
+
+- IPTV terminal functions (Left side, purple background):**
+  - Contains an **Error recovery client functional block** (outlined in red).
+    - Inside this block are three sub-functional blocks: **Error recovery client control functional block** (top), **FEC client function block** (bottom left), and **Retransmission client function block** (bottom right).
+- Content delivery and storage functions (Right side, orange background):**
+  - At the top is the **Content delivery control functional block**, which contains **Cache/storage functional block** and **Distribution functional block**.
+  - In the middle is the **Content delivery error recovery functions** block (outlined in red), which contains:
+    - Error recovery control functional block** (top)
+    - FEC function block** (bottom left)
+    - Retransmission function block** (bottom right)
+  - At the bottom are **Unicast delivery functional block** and **Multicast delivery functional block**.
+
+A dashed red line labeled **Error recovery control protocol** connects the **Error recovery client control functional block** on the left to the **Error recovery control functional block** on the right.
+
+H.701(09)\_F7-2
+
+Diagram of CDER Functions showing IPTV terminal functions and Content delivery and storage functions connected by an Error recovery control protocol.
+
+**Figure 7-2 – CDER Functions**
+
+The constituent functional blocks are described in the following:
+
+- **FEC functional block:** The FEC functional block generates FEC packets from the media data that are sent along with the media data to allow the receiver to correct packet losses in the media data. With this FEC information, the receivers can recover from packet losses locally at the receiver. The FEC may generate packets in layers that can be distinguished by the FEC Client function and can be individually selected using the error recovery control protocol. FEC may be used in unicast and multicast delivery.
+- **Retransmission functional block:** The retransmission functional block retransmits lost packets to recover from packet losses on request of the retransmission client functional block through the error recovery control protocol. Retransmission may be unicast or multicast, depending on the distribution of clients reporting the errors.
+- **Error recovery control functional block:** The error recovery control functional block controls the behaviour of the FEC functional block and the retransmission functional block. For example, it generates information such that the FEC client or the retransmission client functional block is informed on where to access redundant information, on the syntax and semantics of this information, etc. It also permits to send feedback information, if required.
+- **FEC client functional block:** The FEC client functional block receives redundant information generated by the FEC functional block to correct packet losses in the original media data locally.
+- **Retransmission client functional block:** The retransmission client functional block receives information generated by the retransmission functional block to correct packet losses in the original media data.
+- **Error recovery client control functional block:** The error recovery client control functional block manages the behaviour of the FEC client functional block and retransmission client functional block. It receives configuration/control information generated by the error recovery control functional block, negotiates with the content delivery error recovery function on which CDER mechanism (FEC, retransmission or combination of the two) is available, and among those available, which is suitable for this terminal/service combination. It may also select the appropriate FEC layers.
+
+The support of the CDER functions is not required for all networks, in particular for networks that can fulfil the desired IPTV service requirements. In case that a network cannot fulfil the packet loss requirements necessary to achieve the IPTV service requirements, the use of a content delivery error recovery solution is recommended.
+
+If a content delivery and storage function implements CDER functions, it is required to implement at least the error recovery control function as well as one of the two functions: the FEC functional block or the retransmission functional block. The content delivery and storage function is permitted to implement both, the FEC and the retransmission functional blocks.
+
+If an IPTV terminal error recovery client function implements an error recovery client functional block, it is required to implement at least the error recovery control client function as well as one of the two functions: the FEC client functional block or the retransmission client functional block. The IPTV terminal is permitted to implement both, the FEC and the retransmission client functional blocks.
+
+### **7.3 CDER interfaces and protocols**
+
+Information generated in CDER functions relates to one or multiple media streams encapsulated in a certain protocol and packetized into IP packets.
+
+CDER functions are permitted to be used with different services and different types of media protocols. For the transport of the repair packets, it is recommended to use the same protocol as for the media stream. Even though the error recovery packet streams are recommended to have a similar format as the original media stream, it must be ensured that the FEC packets can be differentiated from original media packets. This may be accomplished by sending the error recovery packets using different payload IDs, ports or IP addresses.
+
+For example, in linear TV services, a service encapsulated in a MPEG-2 transport stream is distributed over RTP/UDP/IP. The media stream and the error recovery packet streams typically use similar protocols, i.e., also RTP/UDP. The error recovery packets generated in CDER functions are sent to the receiver. These packets permit to recover lost RTP media packets and the contained MPEG-2 TS packets. The receiver may differentiate original packets and FEC packets by using different payload IDs, different port numbers, or different IP addresses.
+
+Specific realizations of CDER protocols for media streams encapsulated in a certain protocol are specified along with specific CDER functions in the annexes of this Recommendation.
+
+## **7.4 CDER control functional block**
+
+The CDER control functional block is recommended to ensure that all non-preconfigured necessary information on the CDER functions and interfaces is sent to the CDER client control functional blocks and vice versa. This information includes the connection between the media stream and the error recovery packet streams. It also contains the access information of the CDER streams and provides additional information on the details of the CDER streams. The description of this set up information as well as the transport of this set up information is out of the scope of this Recommendation, but is part of [b-ITU-T H.770], clauses 10 and 11, respectively. The CDER control functions may also exchange real-time control information such as feedback information from the error recovery control client function to the error recovery control function.
+
+# **8 Content delivery error recovery mechanisms for streaming**
+
+## **8.1 General**
+
+This clause introduces retransmission-based error recovery functions, FEC-based error recovery functions, and combinations of the two for streaming distribution of media. Streaming distribution is applied in linear TV and content-on-demand services. In most cases, the media streams are transported over the real time protocol (RTP) [IETF RFC 3550].
+
+Retransmission and FEC are two different techniques to recover from RTP packet losses during the delivery of streaming IPTV services. The retransmission approach recovers from packet losses by
+
+requesting retransmission from the sender or intermediate retransmission server. The FEC approach operates by adding redundant information to the data at the sender.
+
+## 8.2 Retransmission
+
+Retransmission-based CDER mechanisms use feedback messages to recover from packet losses. They require a return feedback path and one or more retransmission servers that host the retransmission functional block. On detecting a packet loss, e.g., by noting a gap in the packet sequence, a receiver requests a sender or designated repair servers to retransmit the lost packets. Retransmission may be either unicast or multicast, depending on the distribution of clients reporting the errors.
+
+For retransmission-based CDER, it is required that feedback from receivers to senders or designated repair servers be available. A retransmission server is required to store the original data, such that retransmission requests can be served. The physical location of the retransmission servers is out of the scope of this Recommendation. For fast retransmissions, it is recommended that the retransmission server be in the proximity of the IPTV terminals. The retransmission server functionality may for example be hosted in an edge server, or it may even be hosted in IPTV terminals.
+
+For streaming services, RTP retransmission is one recommended packet loss recovery technique for real-time applications. Retransmitted RTP packets are recommended to be sent in a separate stream from the original RTP stream. To support retransmission with RTP, the RTP protocol [IETF RFC 3550] is not sufficient. This is so because the companion protocol to the real time protocol (RTP), the real time control protocol (RTCP) as specified in [IETF RFC 3550] does not acknowledge single RTP packets but only reports statistics on packet loss and jitter. Extensions to RTCP for the audio-visual profile (AVP) that enable receivers to provide, statistically, more immediate feedback to senders, allowing for efficient feedback-based repair mechanisms (e.g., retransmission) are recommended to be used. Such extensions are recommended to provide a retransmission request of specific, lost packets, for example by sending negative acknowledgements (RTCP NACK) to a retransmission server. Furthermore, it is recommended that a single feedback packet could be used to request transmission of one or multiple lost packets. The retransmission server is recommended to provide a retransmission of the missing packets over IP unicast or alternatively via IP multicast (for multicast sessions).
+
+Specific realizations of retransmission-based CDER protocols for media streams encapsulated in a certain protocol will be specified along with specific CDER functions in the annexes of this Recommendation.
+
+## 8.3 Forward error correction
+
+An FEC-based error recovery function generates redundant data to allow the receiver to correct packet losses. The redundant data is sent in one or multiple FEC streams. With this redundant information, the receiver can recover from packet losses locally. FEC may be used in unicast and multicast delivery.
+
+FEC to be applied in CDER functions refers to packet erasure correction techniques. In these techniques, an amount of data is sent which is in total greater than the original media stream to be communicated, with the property that the original media stream can be reconstructed from any sufficiently large subset of the transmitted data. The original stream is thus resilient to a certain amount of loss (at most the difference between the transmitted and the original data size).
+
+For streaming services with delay constraints, it is recommended to use systematic FEC codes. Systematic FEC codes have the property that the original data to be protected is not modified by the FEC encoding operation. If used in streaming services, it is recommended that the original media packets of the stream be sent unmodified. In addition to the unmodified original data packets, a
+
+certain amount of additional FEC packets is sent. The FEC packets can be used to recover original media packets that have been lost between sender and receiver, without requiring any feedback from the IPTV terminal to the FEC functional block in the network.
+
+To apply FEC to media streams, a certain configuration information is required to be available to the FEC functional block and the FEC client functional block. This information includes the information of the original media data streams to be protected, the definition of the FEC stream and the relationship between the original media stream and the FEC stream. Furthermore, each packet of the FEC stream is required to contain implicit or explicit information on which original media stream packets it protects and how it has been protected. For example, if RTP is used as the media stream protocol, then the RTP sequence number range that the FEC packet protects may be specified.
+
+An FEC client function is recommended to use all received original media packets and FEC packets to recover lost media packets, but minimizing the buffer delay in the FEC client function.
+
+An FEC stream is required to protect at least one media stream. However, a FEC stream may protect multiple media streams at the same time.
+
+Furthermore, one media stream or multiple media streams may be protected by multiple FEC streams at the same time. Multiple FEC streams may be provided such that the CDER client function can distinguish and individually select FEC streams. The selection may be based on the IPTV terminal capabilities, or on some observed error conditions, or any other criteria.
+
+If multiple FEC streams are provided, it is required that the FEC client functional block can select each of the multiple streams individually. Furthermore, if multiple FEC streams are provided, it is recommended that the FEC functional block provide an order of the FEC streams and that the FEC client functions select the streams in the order they are provided. In case of multiple ordered FEC streams, a FEC stream is referred to as a *layer*, and support of this layer means that all FEC streams with more important order are also supported.
+
+An FEC client function is recommended to select FEC streams in an ordered way up to the layer it wants to have access to.
+
+In multicast distribution, the FEC function block may offer multiple layers on different IP multicast addresses. The FEC client functional block may subscribe up to the layer it wants to have access to.
+
+In unicast distribution, the FEC client functional is recommended to indicate to the FEC functional block which FEC layers are requested. The FEC functional block is recommended to only send up to the requested layer.
+
+Specific realizations of FEC-based CDER protocols are specified along with the respective CDER functions in the annexes of this Recommendation.
+
+## **8.4 Hybrid combinations of FEC with retransmissions and feedback**
+
+FEC and retransmission technologies for error recovery are not necessarily mutually exclusive technologies, but they may be used combined and complementarily. By applying such combinations, some interesting benefits may be obtained. The significance of the benefits depends, among others, on the considered service, the considered distribution mean, i.e., multicast or unicast, and/or the number of available retransmission servers. This clause provides a high-level overview of possible combinations.
+
+For retransmission-based mechanisms when combined with an FEC repair mechanism, negative acknowledgements (NACKs) of packets may result in the transmission of FEC packets instead of original data packets. This may be beneficial especially for the case of multicast transmission as the FEC packets may serve the retransmission request of several receivers, which may have observed the loss of different data packets. Such a scheme may allow to reduce the average transmit bandwidth.
+
+For FEC-based mechanisms, the introduction of feedback messages may be used to influence the sender strategy. For example, if receivers are aware that the sender will transmit some small amount of initial FEC data for the current source block, retransmission requests need only to be sent in case this initial FEC information is not sufficient. If the loss exceeds what can be repaired by the initial FEC data, retransmission requests can be made and in response the sender can send additional FEC data for the source block that is independent of the initial FEC data. Such a scheme may reduce the amount of necessary feedback messages and therefore may allow reducing the amount of necessary retransmission servers, when compared to conventional retransmission mechanisms. In an alternative setup, a default level of FEC protection is provided which is capable of correcting all anticipated errors (i.e., the same level of FEC protection as for an FEC-only mechanism). For each FEC source block, the receiver may send an acknowledgement packet requesting that sending of FEC data for that source block should be terminated early, because the receiver has received enough data to recover the block. Such scheme may allow reducing the average bandwidth, if compared to an FEC-only mechanism.
+
+## **8.5 Usage guidelines for retransmission and FEC**
+
+The main advantage of FEC is that there is no need for a back channel to request retransmission from the sender. It is therefore very suitable for unidirectional communications, but can obviously also be used on any (bidirectional) network. FEC introduces a fixed delay due to the generation and processing of the redundant information and to the fact that data must be buffered before error recovery can take place. The delay depends, among others, on service bit rates, FEC block size, and sending arrangements.
+
+In case of retransmission-based error recovery, since the error recovery is handled by requesting and receiving a retransmitted packet from a server with a copy of the original stream, the time needed to receive a repair packet is composed of the round trip time (RTT) between the receiver and the recovery retransmission server plus any jitter imposed in the packet repair process.
+
+Jitter could be caused by variations in time for detecting the lost packet and for generating the repair packet due to server loads. Buffering at the receiver is needed to provide time to receive repair packets before the data stream is sent to the decoder. There are trade-offs among buffer size, latency through the buffers, server load based on the number of users on the server, and quality of the video delivery.
+
+In terms of bandwidth consumption in case of FEC, since the redundant information should always be sent along with the original packets, it generally consumes more average bandwidth than retransmission. Since a retransmission is done on demand, the additionally required average bandwidth for error recovery can be lowered. However, note that to serve the retransmission request fast enough, a certain peak bandwidth higher than the average bandwidth needs to be reserved for retransmission. Therefore, for the case of retransmission, the bandwidth being saved compared relative to FEC may generally only be used for lower priority traffic on the shared access.
+
+The complexity in encoding and decoding FEC data may provide some computational overhead at both the sender and receiver. Retransmission approaches do not require extra decoder computing resources because the entire lost packet is retransmitted to the receiver.
+
+In the retransmission-based approach, an intermediate retransmission server may receive many feedback messages from multiple receivers who experience packet losses. This may lead to the phenomenon of feedback implosion: the concept of receiving many feedback messages for common errors.
+
+To reduce the problem of feedback implosion for retransmission-based mechanisms, a careful architectural design is necessary. When retransmission is used in multicast delivery, proper attention must be paid to the ratio of clients to retransmission servers to avoid any scalability issues. A distributed retransmission approach can be introduced to resolve the issues of timeliness,
+
+scalability, and feedback implosion. A local retransmission server placed in the vicinity of the receiver can be used to recover the losses across the access and consumer environment and a core retransmission server located near the head end can be used to recover losses in the core and common losses requested via the local retransmission server. However, such architecture may require additional network equipment to serve retransmission requests, or the function may reside in servers already present for other purposes. Due to the different architectural design, feedback implosion is not existent for FEC-based approaches.
+
+Any content delivery error recovery scheme has a non-zero probability that a complete recovery from packet loss cannot be done. Lowering the probability for missing packets is a balance between complexity of design and quality of the received video. In case of FEC, if the packet loss exceeds the repair capabilities of the FEC scheme, recovery will not be possible. In case of retransmission, recovery may be deficient due to non-persistent automatic repeat request (ARQ) protocols or late arrival of packets.
+
+In these unlikely cases of failure, media post-decoder remediation schemes may need to be used.
+
+# **9 Content delivery error recovery for content download services**
+
+## **9.1 General**
+
+In content download services, large media files are distributed. File distribution can only be considered successful if the entire file is received correctly. In the case of lossy networks, this is obviously a challenging task. However, in contrast to streaming services, for download services the delay and latency requirements are significantly lower. Therefore, for media delivery generally mechanisms other than RTP-based real-time distribution are used. These alternative distribution means also enable and require alternative CDER mechanisms.
+
+For unicast download modes, it is recommended to use TCP [IETF RFC 793] for reliable data delivery. In case of multicast delivery, the following is recommended. For multicast download using file delivery over unidirectional transport (FLUTE) [b-IETF RFC 3926], FEC [b-IETF RFC 3695], [IETF RFC 5052] and [IETF RFC 5053] is recommended as CDER mechanisms. Furthermore, multicast delivery may be supported by associated file repair procedures that are invoked if the multicast delivery of a media file is not successful.
+
+## **9.2 Retransmission-based mechanism: reliable unicast download with TCP**
+
+TCP provides a reliable communication service for file delivery applications over the Internet Protocol (IP). Due to network congestion, traffic load balancing, or other unpredictable network behaviour, IP packets can be lost or delivered out of order. TCP detects these problems, requests retransmission of lost packets, rearranges out-of-order packets, and even helps minimize network congestion to reduce the occurrence of the other problems. Once the TCP receiver has finally reassembled a perfect copy of the data originally transmitted, it passes that datagram to the application.
+
+TCP is used extensively by the most popular file delivery protocols such as HTTP or FTP. As TCP is optimized for accurate delivery rather than timely delivery, TCP sometimes incurs in relatively long delays (in the order of seconds) while waiting for out-of-order messages or retransmissions of lost messages. However, for download services these delays are irrelevant.
+
+To guarantee reliability over unreliable networks, positive acknowledgment with retransmission is used to guarantee reliability of packet transfers. This fundamental technique requires the receiver to respond with an acknowledgment message as it receives the data. The sender keeps a record of each packet it sends, and waits for acknowledgment before sending the next packet. The sender also keeps a timer from when the packet was sent, and retransmits a packet if the timer expires.
+
+## **9.3 FEC-based mechanism: reliable multicast file distribution with FLUTE and FEC**
+
+To deliver large multimedia files to many hosts, the file delivery over unidirectional transport (FLUTE) protocol is commonly used. Despite the fact that IP multicast is inherently massively scalable, this best effort service does not provide a session management functionality, congestion control or reliability. FLUTE provides these functionalities and therefore permits to distribute large objects over the asynchronous layered coding (ALC) [b-IETF RFC 3450] protocol and IP multicast without sacrificing the inherent scalability of IP multicast.
+
+In particular, for the delivery over unreliable networks, it is recommended to use the FEC building block inherited from ALC. ALC uses the FEC building block to provide reliability. In this case, the sender generates encoding symbols based on the file to be delivered using FEC codes and sends them in packets to channels associated with the session. Receivers simply wait for enough packets to arrive in order to reliably reconstruct the object. Thus, there is no request for retransmission of individual packets from receivers that miss packets in order to assure reliable reception of a file, and the packets and their rate of transmission out of the sender can be independent of the number and the individual reception experiences of the receivers.
+
+## **9.4 Retransmission-based file repair procedures**
+
+The distribution of large multimedia files using TCP or FLUTE sessions may still result in situations where the download is interrupted due to network congestion, powering off the IPTV terminal device or other reasons that lead to the interruption of the service reception. In this case, it is recommended that the IPTV terminal be able to invoke file repair procedures to restart and complete the delivery of the file. Because of the feedback request, file repair procedures can also be viewed as a retransmission-based mechanism. File repair procedures are recommended to minimize the additional load by using as much data as possible from what has already been received. This can for example be accomplished by requesting only the missing byte ranges of the file, or by requesting only the necessary FLUTE symbols to recover a file using FEC.
+
+## Annex A
+
+## FEC-based error recovery mechanisms for streaming distribution
+
+(This annex forms an integral part of this Recommendation)
+
+This annex provides recommendations for CDER mechanisms based on FEC for streaming distribution of FEC.
+
+### A.1 Assumptions
+
+For the remainder of this annex, it is assumed that the original media streams to be FEC-protected are transported over a single RTP flow. Examples for media streams that fall into this category are:
+
+- RTP-encapsulated MPEG-2 transport stream transported according to [ETSI TS 102 034], clause 7.1.1,
+- RTP-encapsulated timestamped transport Streams (TTS) transported according to [ARIB STD-B24], or
+- any other RTP encapsulated stream that contains media data.
+
+### A.2 Forward error correction according to [ETSI TS 102 034]
+
+#### A.2.1 Overview
+
+Annex E of [ETSI TS 102 034] specifies a FEC-based CDER mechanism, in which the IPTV data stream is MPEG-2 TS encapsulated in RTP. The specification provides the option to add FEC streams on top of any legacy RTP stream.
+
+This FEC mechanism provides the option to generate multiple FEC streams for a single media stream. In particular, it also consists of two forward error correction codes, a simple packet-based interleaved parity code equivalent to a subset of the code defined in [SMPTE 2022-1] and Raptor codes defined in [IETF RFC 5053].
+
+Based on this construction, FEC packets may be sent in one (or more) layers: the first layer contains packets generated by the interleaved parity code and the optional second and subsequent layers contain packets generated by the Raptor code. In particular, clause E.3 of [ETSI TS 102 034] defines the first layer based on [SMPTE 2022-1], referred to as base layer in this Recommendation. Clause E.4 of [ETSI TS 102 034] defines the subsequent layers, based on [IETF RFC 5053] referred to as enhancement layers in this Recommendation.
+
+Receivers process only packets from the layer or layers they support. Clause E.5 of [ETSI TS 102 034] describes the decoding procedures. A receiver only supporting [SMPTE 2022-1] decodes lost media packets using packets from the base layer only. One key property of the code defined in Annex E of [ETSI TS 102 034] is that simultaneous support of multiple layers is possible and FEC packets from these multiple layers can be combined at the receiver in the decoding process. The so-called hybrid decoding procedures can make use of packets from all layers of the code. The sender is recommended to align the source blocks of the base layer and the enhancement layers.
+
+Finally, clause E.6 of [ETSI TS 102 034] defines complete FEC protocols for multicast and unicast video.
+
+#### A.2.2 Configuration information
+
+The details of the configuration of the FEC in the IPTV architecture are outside the scope of this Recommendation. All or some of the parameters may be pre-configured, or configuration methods
+
+as specified in [b-ITU-T H.770] may be used. It is required that the FEC client functional block has access to the following service discovery information.
+
+Table A.1 is related to the setup of each FEC stream.
+
+**Table A.1 – Setup parameters for FEC streams**
+
+| Attribute                  | Explanation                                                    | Comments                                                                                                                                                   |
+|----------------------------|----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FECStreamMulticastAddress  | IP multicast address for this FEC stream.                      | <i>Optional.</i> If the IP multicast address is omitted, then the FEC stream is assumed to be on the same multicast address as the original data.          |
+| FECStreamMulticastPort     | IP multicast port to access the FEC stream.                    | <i>Mandatory</i> , if FECStreamMulticastAddress is given. Otherwise, then the FEC stream is assumed to be on the same multicast port as the original data. |
+| FECStreamMulticastSource   | IP multicast source address for FEC stream.                    | <i>Optional.</i> If the IP multicast source address is omitted, then the FEC stream is assumed to be on the same multicast address as the original data.   |
+| FECStreamMaximumBitrate    | Specifies the maximum bit rate (in kbit/s) of this FEC stream. | <i>Optional.</i> If not provided, then the receiver cannot make any assumptions on the maximum bit rate.                                                   |
+| FECStreamPayloadTypeNumber | RTP payload type number for this FEC stream.                   | <i>Optional.</i> It shall be 96 (the 1st dynamic payload number) for the base layer FEC stream if SMPTE-2022 compatibility is required.                    |
+
+The order of the FEC stream elements determines the order of the layers. However, to be more specific, the attribute may for example explicitly contain the layer it refers to, e.g., BaseLayer or EnhancementLayer (see for example [b-ITU-T H.770]).
+
+Furthermore, if FEC streams are defined, the information in Table A.2 may be available.
+
+**Table A.2 – Additional information for FEC streams**
+
+| Attribute                  | Explanation                                                                                                                                                                          | Comments         |
+|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|
+| MaximumPacketNumberInBlock | 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). | <i>Optional.</i> |
+| MaximumFECBlockDuration    | Maximum transmission duration of any FEC block (source and FEC packets).                                                                                                             | <i>Optional.</i> |
+
+**Table A.2 – Additional information for FEC streams**
+
+| Attribute                         | Explanation                                                                                                                                                                                            | Comments                                                                      |
+|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|
+| FECObjectTransmission Information | FEC object transmission information for the FEC enhancement layer. This information contains the maximum source block length and the encoding symbol size (see [ETSI TS 102 034], clause E.4.3.1.1.1). | <i>Mandatory</i> , if at least one FEC enhancement layer element is included. |
+
+The FEC functional block is required to generate the FEC streams such that they conform to the configuration, i.e., the FEC streams are sent on adequate IP addresses, ports and use the adequate signalling.
+
+An IPTV terminal and in particular the FEC client functional block that supports receiving FEC streams is required to acquire the adequate configuration information.
+
+#### A.2.3 Syntax and configuration protocols
+
+To configure FEC streams with some of the parameters as specified in clause A.2.2, a minimum set of attributes are required to be available at the FEC client functional block, either by pre-configuration or by the use of methods defined in [b-ITU-T H.770].
+
+### A.3 Recommended FEC for linear TV services
+
+For a CDER mechanism based on FEC for linear TV services, the provisions in Annex E of [ETSI TS 102 034] are recommended.
+
+The FEC protocol comprises two layers of FEC protection:
+
+- 1-D interleaved parity FEC (referred to as base layer); and
+- Raptor FEC (referred to as enhancement layer).
+
+For some background information, refer to clause A.2.
+
+If the error recovery functional block supports FEC for linear TV services, then the generation of FEC protection of the MPEG-2 transport stream shall be required to be provided according to clause E.3 of [ETSI TS 102 034]. This corresponds to the support of the base layer.
+
+If the error recovery functional block supports enhanced FEC for linear TV services, then the base layer FEC and the generation of FEC streams according to clause E.4 of [ETSI TS 102 034] shall be supported. This corresponds to the support of the enhancement layer. If the enhancement layer is applied, the FEC scheme defined in clause E.4.3.2 of [ETSI TS 102 034] shall be used.
+
+An IPTV terminal and in particular the FEC client functional block that supports receiving the FEC base layer packets only is required to perform any FEC decoding to meet the minimum decoder requirements according to clause E.5.1.1 of [ETSI TS 102 034].
+
+An IPTV terminal, and in particular the FEC client functional block that supports receiving and decoding both the base and enhancement-layer FEC, is required to perform decoding to meet the enhanced decoder requirements according to clause E.5.1.2 of [ETSI TS 102 034].
+
+- The relation of this FEC mechanism to the QoS classes in [ITU-T Y.1541], especially recommended parameters settings for different QoS classes and different services is discussed in clause III.1.2, specifically in Table III.1. Consumer television quality can be achieved using the standard Y.1541 QoS Classes 0 and 1 together with this FEC mechanism, low to modest overhead, and the enhanced decoder according to clause E.5.1.2 of [ETSI TS 102 034].
+
+For configuration information and protocols to setup FEC streams for linear TV services in different IPTV architectures, refer to clause A.2.
+
+For more detailed performance results and recommended parameter settings, please refer to clause III.1.
+
+### **A.4 Recommended FEC for content-on-demand services**
+
+For a CDER mechanism based on FEC, Annex E of [ETSI TS 102 034] is recommended. The same principles as for linear TV services apply also for content-on-demand services. For details, refer to clause A.3.
+
+For configuration information and protocols to setup of FEC streams for content-on-demand services in different IPTV architectures, refer to clause A.2.
+
+# **Annex B**
+
+## **Retransmission-based error recovery mechanisms for streaming delivery**
+
+(This annex forms an integral part of this Recommendation)
+
+*For further study.*
+
+# Annex C
+
+## **Content delivery error recovery for content download services**
+
+(This annex forms an integral part of this Recommendation)
+
+*For further study.*
+
+# Appendix I
+
+## Evaluation of CDER mechanisms for IPTV services
+
+(This appendix does not form an integral part of this Recommendation)
+
+### I.1 Introduction
+
+When proposing a technical mechanism, the relevant performance evaluation results produced under different impairment conditions should be provided. The evaluation results should be able to evaluate the following characteristics of a CDER mechanism:
+
+- A CDER mechanism's actual recovery ability, given certain impairment conditions. The definition of ability could be how well a CDER mechanism can actually improve an IPTV service quality, compared to that before recovery, under a certain impairment condition.
+- The cost of CDER mechanisms, provided the actual recovery ability of the mechanism is reached under certain impairment conditions. The cost may include the bandwidth overhead caused by a CDER mechanism, the memory required by implementing a CDER mechanism in IPTV equipment(s), the processing requirement by implementing a CDER mechanism in IPTV equipment(s), etc.
+- Comparison to existing CDER mechanisms already specified in this Recommendation.
+- Other characteristics.
+
+These characteristics should be taken into account when approving additional mechanisms in CDER work. And for those mechanisms that have been recommended as optional CDER functions for IPTV services, these characteristics may help estimate which one is appropriate to work under a certain set of circumstances.
+
+To be comparable and fair for evaluation of CDER mechanisms characteristics, the agreement may be generally reached as guidelines at least in terms of:
+
+- 1) The objective impairment conditions. For "Content Delivery Error" notion, the objective impairments usually refer to those errors occurring during content transport, which can be reflected by various QoS parameters including packet loss pattern, packet loss rate, end-to-end packet transfer delay, delay variation, etc.
+- 2) The content to be handled by the CDER mechanism. For multimedia services, the content may refer to a specific video/audio sequence to be tested. The content of other services, if necessary, need to be discussed as well.
+- 3) The quality estimation method/model for IPTV services. The CDER's ultimate objective is to improve the quality of IPTV services. Therefore, the estimation of service quality may be a measure for performance of CDER mechanisms. For example, by comparing the actual service quality after using a CDER mechanism to that before recovering, the mechanism's actual gain on service quality under a certain impairment condition can be rated and thus, is comparable to other CDER mechanisms. A trusted quality estimation method/model is the basis of such measurement. For multimedia services, QoE estimation and corresponding method/model may be a reasonable choice. ITU-T SG 12 is also working on this subject and its results may be considered for CDER mechanism evaluation. For other services, if necessary, the quality estimation method/model needs to be discussed as well.
+- 4) The target quality requirements for IPTV services. With these requirement sets, we can assess how well the actual service quality, after being recovered by a CDER mechanism, meets the target requirements. For multimedia services, QoE is a subjective notion perceived by end users. It is usually collectively determined by subjective factors (human component) and objective factors (QoS). However, conducting the unanimous comprehensive target QoE requirements, with the contributions due to subjective factors
+
+being taken into account, is very difficult for the moment. [b-ITU-T G.1080] recommends some objective transport layer parameters for satisfactory QoE for various encoded standard definition video materials, which for the time being avoid the issue of subjective factors. The CDER mechanisms for video and audio content delivery may take these objective parameters as the provisional target quality requirement. And for CDER mechanisms for services other than multimedia, the objective target requirements also may be a reasonable choice.
+
+- 5) The cost metrics and corresponding estimation method/tools.
+
+### **I.2 Evaluation criteria for multicast linear TV**
+
+[ITU-T Y.1541] describes a number of QoS classes for IP networks. Specifically, Table 1 of [ITU-T Y.1541] defines six IP network QoS classes and the respective network performance objectives. In addition, Table 3 of [ITU-T Y.1541] proposes two additional provisional QoS classes mainly for the purpose of supporting sufficient QoS for digital television transmission. The difference to those in Table 1 of [ITU-T Y.1541] is that these values need not to be met by networks until they are revised (up or down) based on operational experience.
+
+Appendix VIII of [ITU-T Y.1541] considers digital television transmission on IP networks and concludes that, by the use of specific application layer error recovery mechanisms, digital television quality requirements can be met using the new provisional QoS classes.
+
+However, as stated in this Recommendation, additional experience on content delivery error recovery may allow revising the considerations on QoS classes 6 and 7. Error recovery mechanisms being considered in the ITU-T IPTV architecture are related to the QoS classes in [ITU-T Y.1541] and appropriate parameter settings should be applied.
+
+For this relation, suitable performance metrics shall be applied. Table VIII.1 of [ITU-T Y.1541] proposes some loss/error considerations. DVB and the ATIS IIF [ATIS-0800005] propose to measure the performance of mechanisms in terms of the *mean time between artefacts* (MTBA) in the video playout. Both have used a quality target of four hours MTBA, which also fits into the loss ratio recommendations of Table VIII.1 of [ITU-T Y.1541].
+
+Y.1541 QoS classes specify an upper bound on the packet loss ratio (Class 0-4:  $10^{-3}$ , provisional classes 6 and 7:  $10^{-5}$ ), but do not specify packet loss patterns. However, suitable parameter settings to meet the requirements may be affected not only by the loss rate, but also by loss patterns. In order to present application layer reliability performance with different loss patterns, different packet loss models may be considered, e.g., independent random loss model or burst loss models.
+
+[ITU-T Y.1541] also specifies limits on the IP packet transfer delay (IPTD), IP packet delay variation (IPDV), and IP packet error rate (IPER). The effect of these parameters in relation to the error recovery mechanism is also of interest.
+
+The performance and parameter settings for a certain mechanism may also depend on the service bit rate. This effect should also be considered when relating mechanisms to QoS classes.
+
+## **I.3 Evaluation criteria for content-on-demand services**
+
+*For further study.*
+
+### **I.4 Evaluation criteria for content download services**
+
+*For further study.*
+
+## Appendix II
+
+## Use cases for content delivery error recovery
+
+(This appendix does not form an integral part of this Recommendation)
+
+## II.1 Linear TV service
+
+Figure II.1 illustrates general high-level error recovery flow applied in linear TV loose model [ITU-T Y.1910].
+
+![Sequence diagram illustrating the error recovery flow for linear TV service. The diagram shows interactions between IPTV TF, Application Functions, Content Delivery Functions, and Network Functions across four phases: Select, Consume: Set-up, Play, and Consume: Close. The Play phase is highlighted with a blue background and includes Error Recovery Configure/Control Information, IGMP Join, Error Recovery Flow/Content flow, and Error Recovery Feedback messages.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg)
+
+The diagram illustrates the error recovery flow for linear TV service across four phases: Select, Consume: Set-up, Play, and Consume: Close. The participants involved are IPTV TF, Application Functions, Content Delivery Functions, and Network Functions.
+
+- Select Phase:**
+  - IPTV TF sends a **Connect** message to Application Functions, which responds with **OK**.
+  - IPTV TF sends a **Browser & select** message to Application Functions.
+  - Application Functions sends an **Establish authority** message to Content Delivery Functions, which responds with **OK**.
+  - Content Delivery Functions sends an **OK (Service URL)** message back to Application Functions.
+- Consume: Set-up Phase:**
+  - Application Functions sends a **Consume (Service URL)** message to Content Delivery Functions.
+  - Content Delivery Functions sends a **Get current ITF location (\*)** message to Network Functions, which responds with **Location (\*)**.
+  - Content Delivery Functions sends a **Request network resources** message to Network Functions, which responds with **Allocate network resources**.
+  - Content Delivery Functions sends an **OK** message back to Application Functions.
+- Play Phase (Highlighted in Blue):**
+  - IPTV TF and Content Delivery Functions exchange **Error Recovery Configure/Control Information**.
+  - Content Delivery Functions sends an **IGMP Join** message to Network Functions.
+  - IPTV TF and Content Delivery Functions exchange **Error Recovery Flow/Content flow**.
+  - IPTV TF and Content Delivery Functions exchange **Error Recovery Feedback**.
+- Consume: Close Phase:**
+  - Application Functions sends a **Close** message to Content Delivery Functions.
+  - Content Delivery Functions performs an **Error Recovery Process. Can be FEC, retransmission or combination of the two**.
+  - Content Delivery Functions sends a **Release network resources** message to Network Functions, which responds with **Release network resources**.
+  - Content Delivery Functions sends an **OK** message back to Application Functions.
+  - Application Functions sends a **Disconnect** message to IPTV TF, which responds with **OK**.
+
+A note indicates that the **Error Recovery Process** can be triggered by abnormal termination or timeout of streaming session.
+
+Sequence diagram illustrating the error recovery flow for linear TV service. The diagram shows interactions between IPTV TF, Application Functions, Content Delivery Functions, and Network Functions across four phases: Select, Consume: Set-up, Play, and Consume: Close. The Play phase is highlighted with a blue background and includes Error Recovery Configure/Control Information, IGMP Join, Error Recovery Flow/Content flow, and Error Recovery Feedback messages.
+
+Figure II.1 – Error recovery flow for linear TV service
+
+The description of the flow is as follows:
+
+- 1) During setup, the error recovery configure/control information is exchanged between IPTV terminal functions (IPTV TF) and content delivery error recovery functions to prepare for the subsequent error recovery actions.
+
+- 2) Content delivery functions send error recovery flow along with content flow to IPTV TF right after joining the channel (as step "IGMP Join" indicates) to carry out error recovery in case that content flow is damaged.
+- 3) IPTV TF may send error recovery feedback to error recovery functions depending on the CDER mechanisms it prefers to use.
+
+In the above steps, the error recovery configure/control information, the error recovery feedback and the information exchange and error recovery flow need to be standardized.
+
+![Sequence diagram illustrating the FEC recovery flow for linear TV service. The diagram shows two main functional blocks: 'End-User Functions' (pink) and 'Content Delivery Functions' (orange). The 'End-User Functions' block contains 'Error Recovery Client Functional Block' (blue), 'Multicast Delivery Functional Block' (red), and 'Control Client Functional Block' (green). The 'Content Delivery Functions' block contains 'Content Delivery Control Functional Block' (green), 'Error Recovery Functional Block' (blue), and 'Multicast Delivery Functional Block' (red). The process is divided into 'Set-up' and 'Play' phases. In the 'Set-up' phase, a dashed green arrow labeled 'Error Recovery Configure/Control Information' points from the 'Control Client Functional Block' to the 'Content Delivery Control Functional Block'. In the 'Play' phase, a solid blue arrow labeled 'FEC flow' points from the 'Multicast Delivery Functional Block' in the 'Content Delivery Functions' to the 'Error Recovery Client Functional Block' in the 'End-User Functions'. A solid pink arrow labeled 'FEC flow & Content Flow' points from the 'Multicast Delivery Functional Block' in the 'Content Delivery Functions' to the 'Error Recovery Client Functional Block' in the 'End-User Functions'. A large yellow double-headed arrow labeled 'FEC Recovery' is positioned between the 'Error Recovery Client Functional Block' and the 'Error Recovery Functional Block'.](b235edb1dbe659e2782c9a0e47775ca4_img.jpg)
+
+Sequence diagram illustrating the FEC recovery flow for linear TV service. The diagram shows two main functional blocks: 'End-User Functions' (pink) and 'Content Delivery Functions' (orange). The 'End-User Functions' block contains 'Error Recovery Client Functional Block' (blue), 'Multicast Delivery Functional Block' (red), and 'Control Client Functional Block' (green). The 'Content Delivery Functions' block contains 'Content Delivery Control Functional Block' (green), 'Error Recovery Functional Block' (blue), and 'Multicast Delivery Functional Block' (red). The process is divided into 'Set-up' and 'Play' phases. In the 'Set-up' phase, a dashed green arrow labeled 'Error Recovery Configure/Control Information' points from the 'Control Client Functional Block' to the 'Content Delivery Control Functional Block'. In the 'Play' phase, a solid blue arrow labeled 'FEC flow' points from the 'Multicast Delivery Functional Block' in the 'Content Delivery Functions' to the 'Error Recovery Client Functional Block' in the 'End-User Functions'. A solid pink arrow labeled 'FEC flow & Content Flow' points from the 'Multicast Delivery Functional Block' in the 'Content Delivery Functions' to the 'Error Recovery Client Functional Block' in the 'End-User Functions'. A large yellow double-headed arrow labeled 'FEC Recovery' is positioned between the 'Error Recovery Client Functional Block' and the 'Error Recovery Functional Block'.
+
+**Figure II.2 – FEC recovery flow for linear TV service**
+
+FEC is suitable for linear TV service, where a feedback channel may not exist or may exist but has the risk of feedback implosion if feedbacks are frequently used. An example of FEC error recovery flow is depicted in Figure II.2. The feedback channel may be used during the Setup phase only, to exchange FEC codec information (which should be standardized) and after that, the feedback channel is no longer needed.
+
+A retransmission error recovery function may also be used for linear TV service for the purpose of reducing channel change delay, as shown in Figure II.3:
+
+- 1) When a user changes from the current channel to a new channel, it may trigger the procedure of leaving the current channel and simultaneously send a retransmission request with the necessary information.
+- 2) Upon receiving a retransmission request, the error recovery functional block responds immediately with the proper flow of the new channel cached for recovery purposes.
+- 3) The error recovery client functional block receives the recovery flow; delivers the flow to, for example, the application client function and immediately plays it out without waiting for the end user to join the new channel and for the arrival of the new content flow.
+
+![Sequence diagram for fast channel switch flow for linear TV service. It shows interactions between End-User Functions, Content Delivery Functions, and another Content Delivery Functions block. The process involves leaving the current channel, sending a retransmission request, receiving cached data, switching channels, and joining the new channel with a recovery flow.](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg)
+
+The diagram illustrates the interaction for a fast channel switch flow for linear TV service. It consists of three main functional blocks: **End-User Functions** (pink), **Content Delivery Functions** (orange), and another **Content Delivery Functions** block (green).
+
+**End-User Functions** include:
+
+- Error Recovery Client Functional Block
+- Multicast Delivery Functional Block
+- Unicast Delivery Functional Block
+
+**Content Delivery Functions** (orange) include:
+
+- Error Recovery Functional Block
+- Multicast Delivery Functional Block
+
+**Content Delivery Functions** (green) include:
+
+- Multicast Delivery Functional Block
+
+**Sequence of Events:**
+
+- Consume: Chang Channel**: The user initiates a channel change. The Error Recovery Client Functional Block sends a **Retransmission Request** (green arrow) to the Error Recovery Functional Block.
+- Leave the current Channel**: Represented by a grey box on the left timeline.
+- Transmit cached data of new channel immediately to IPTV terminal to reduce channel change delay**: Text describing the purpose of the retransmission.
+- Recovery Flow**: The Error Recovery Functional Block responds with a **Recovery Flow** (blue arrow) to the Error Recovery Client Functional Block.
+- Channel Switch**: A dashed green horizontal line indicates the channel switch to the second Content Delivery Functions block.
+- Joint new channel & Play**: The phase where the new channel is joined.
+- Recovery Flow**: A second blue arrow labeled **Recovery Flow** is sent from the second Content Delivery Functions block to the Unicast Delivery Functional Block.
+- Join a new Channel**: Represented by a grey box on the left timeline.
+- Accelerate Channel Change**: Indicated by a yellow double-headed arrow diamond.
+- Content Flow of New Channel**: A red arrow labeled **Content Flow of New Channel** is received from the second Content Delivery Functions block by the Multicast Delivery Functional Block.
+
+Sequence diagram for fast channel switch flow for linear TV service. It shows interactions between End-User Functions, Content Delivery Functions, and another Content Delivery Functions block. The process involves leaving the current channel, sending a retransmission request, receiving cached data, switching channels, and joining the new channel with a recovery flow.
+
+**Figure II.3 – Retransmission for fast channel switch flow for linear TV service**
+
+### II.2 Tightly coupled content-on-demand service
+
+Figure II.4 illustrates general high-level error recovery flow applied in tightly coupled content-on-demand service [ITU-T Y.1910]. The flow is similar to steps shown in Figure II.1.
+
+![Sequence diagram illustrating the error recovery flow for tightly coupled content-on-demand service. The diagram shows interactions between IPTV TF, Application Functions, Content Delivery & Service Control Functions, and Network Functions across four phases: Select, Consume: Set-up, Play, and Consume: Close. The Play phase includes an Error Recovery/Content flow and Error Recovery Feedback loop.](11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg)
+
+The diagram illustrates the interaction between four functional blocks: IPTV TF, Application Functions, Content Delivery & Service Control Functions, and Network Functions. The process is divided into four phases: Select, Consume: Set-up, Play, and Consume: Close.
+
+- Select:** IPTV TF sends a 'Connect' message to Application Functions, which responds with 'OK'. IPTV TF then sends 'Browser & select' to Application Functions.
+- Consume: Set-up:** Application Functions send 'Establish authority & Resource' to Content Delivery & Service Control Functions. These functions send 'Get current ITF location (\*)' and 'Location (\*)' to Network Functions. Content Delivery & Service Control Functions then send 'Allocate CD&SF Capabilities' and 'Request network resources' to Network Functions. Network Functions respond with 'Allocate network resources' and 'OK'. Content Delivery & Service Control Functions send 'OK' to Application Functions, which then send 'Consume (Service URL)' to IPTV TF. IPTV TF responds with 'OK (Service URL)'.
+- Play:** IPTV TF sends 'Error Recovery Configure/Control Information' to Content Delivery & Service Control Functions, which respond with 'OK'. IPTV TF sends 'Play' to Content Delivery & Service Control Functions, which respond with 'OK'. A solid green line represents the 'Error Recovery/Content flow' from Content Delivery & Service Control Functions to IPTV TF. A dashed green line represents the 'Error Recovery Feedback' from IPTV TF to Content Delivery & Service Control Functions. IPTV TF sends 'Close' to Content Delivery & Service Control Functions, which respond with 'OK'.
+- Consume: Close:** IPTV TF sends 'Disconnect' to Application Functions, which send 'Release authority & Resource' to Content Delivery & Service Control Functions. Content Delivery & Service Control Functions send 'Release CD&SF Capabilities' and 'Release network resources' to Network Functions. Network Functions respond with 'Release network resources' and 'OK'. Content Delivery & Service Control Functions send 'OK' to Application Functions, which then send 'OK' to IPTV TF. A note indicates that this phase 'Can be triggered by abnormal termination or timeout of transaction session.'
+
+Vertical labels on the left indicate the phases: Select, Consume: Set-up, Play, and Consume: Close. Double-headed arrows labeled 'Transaction Protocol' are shown between IPTV TF and Application Functions in the Select and Consume: Close phases. A double-headed arrow labeled 'Stream Control Protocol' is shown between Content Delivery & Service Control Functions and IPTV TF in the Play phase. A double-headed arrow labeled 'Feedback & Recovery' is shown between IPTV TF and Content Delivery & Service Control Functions in the Play phase.
+
+Sequence diagram illustrating the error recovery flow for tightly coupled content-on-demand service. The diagram shows interactions between IPTV TF, Application Functions, Content Delivery & Service Control Functions, and Network Functions across four phases: Select, Consume: Set-up, Play, and Consume: Close. The Play phase includes an Error Recovery/Content flow and Error Recovery Feedback loop.
+
+Figure II.4 – Error recovery flow for tightly coupled content-on-demand service
+
+Applying retransmission for tightly coupled content-on-demand service may result in a lower risk of feedback implosion than for IPTV linear TV because tightly coupled content-on-demand service flow is based on unicast delivery and a packet loss would only affect one on-demand flow, probably resulting in one retransmission feedback. Retransmission may, however, not be the exclusive CDER mechanism. FEC may also be a viable choice. Sometimes, the combination of the two in a complementary manner may be better than having only one. Figure II.5 shows an example of such a combination:
+
+- 1) The error recovery functional block sends FEC control information to the error recovery client functional block.
+- 2) The error recovery functional block generates FEC flows to the error recovery client functional block for recovering the content flow.
+- 3) If the damaged content flow (for example, a long burst loss) cannot be recovered by the received FEC flow, the error recovery client functional block may send a retransmission feedback, requesting additional FEC recovery information rather than all the lost content.
+
+This may reduce the amount of feedback messages, the traffic overhead due to retransmission along the content forwarding path and the amount of retransmission servers, as compared with conventional retransmission mechanisms [ITU-T Y.1910].
+
+- 4) The error recovery functional block sends additional FEC flows to recover from the pending errors.
+
+In this case, the retransmission feedback information plays a key role and may be standardized.
+
+![Sequence diagram illustrating the error recovery flow for tightly coupled content-on-demand. The diagram shows two main entities: IPTV TF (left) and Content Delivery & Service Control Functions (right). IPTV TF contains 'Error Recovery Client Functional Block' and 'Unicast Content Delivery Client Functional Block'. Content Delivery & Service Control Functions contains 'Unicast Delivery Functional Block' and 'Error Recovery Functional Block'. The sequence of messages is: 1. FEC control information (green arrow) from Content Delivery to IPTV TF. 2. Content flow (red arrow) from Content Delivery to IPTV TF. 3. FEC flow (blue arrow) from Content Delivery to IPTV TF. 4. Retransmission Feedback Information (green arrow) from IPTV TF to Content Delivery. 5. Retrans flow (blue arrow) from Content Delivery to IPTV TF. There are also internal arrows within IPTV TF and Content Delivery blocks, and a '.....' separator between the first and second content/FEC flows.](00504fc688ebcf131ccbeff94dfc9939_img.jpg)
+
+Sequence diagram illustrating the error recovery flow for tightly coupled content-on-demand. The diagram shows two main entities: IPTV TF (left) and Content Delivery & Service Control Functions (right). IPTV TF contains 'Error Recovery Client Functional Block' and 'Unicast Content Delivery Client Functional Block'. Content Delivery & Service Control Functions contains 'Unicast Delivery Functional Block' and 'Error Recovery Functional Block'. The sequence of messages is: 1. FEC control information (green arrow) from Content Delivery to IPTV TF. 2. Content flow (red arrow) from Content Delivery to IPTV TF. 3. FEC flow (blue arrow) from Content Delivery to IPTV TF. 4. Retransmission Feedback Information (green arrow) from IPTV TF to Content Delivery. 5. Retrans flow (blue arrow) from Content Delivery to IPTV TF. There are also internal arrows within IPTV TF and Content Delivery blocks, and a '.....' separator between the first and second content/FEC flows.
+
+**Figure II.5 – Error recovery flow for tightly coupled content-on-demand**
+
+### II.3 Place-shifting service
+
+An IPTV service in which subscribers can access (pause, rewind, fast forward, etc.) IPTV contents without placing limitations. That is, the end-user sees his or her subscribed IPTV contents anywhere. The place-shifting basically addresses requirements of end-users who move from one place to another. This service assumes that the end-user's terminal device can be a mobile phone [ITU-T Y.Sup5].
+
+In the place-shifting scenario, the channel condition may experience significant changes. The new condition after a change may last for a "long period" during which an adaptive FEC (AFEC) is possible to be applied to achieve more efficient bandwidth utilization as well as better service quality. That is, the end user may send feedback with the necessary information for the AFEC encoder to adjust, for example, its FEC redundancy based on the channel condition.
+
+Depending on who is taking care of redistributing the IPTV traffic, two types of place-shifting services can be defined: subscriber-based place-shifting and network-based place-shifting service [ITU-T Y.Sup5]. An example of applying AFEC in network-based place-shifting is illustrated in Figure II.6.
+
+![Sequence diagram illustrating the AFEC recovery flow for place-shifting service. The diagram is divided into two main functional areas: 'End-User Functions' (pink background) and 'Content Delivery Functions' (orange background). The 'End-User Functions' box contains three sub-blocks: 'Error Recovery Client Functional Block' (blue), 'Unicast Delivery Functional Block' (red), and 'Control Client Functional Block' (green). The 'Content Delivery Functions' box contains three sub-blocks: 'Content Delivery Control Functional Block' (green), 'Unicast Delivery Functional Block' (red), and 'Error Recovery Functional Block' (blue). The sequence of interactions is as follows: 1. Setup phase: A dashed green arrow labeled 'Error Recovery Config/Control message' goes from the Content Delivery Control block to the Error Recovery Client block. A solid purple arrow labeled 'Content Flow & FEC flow' goes from the Unicast Delivery block in Content Delivery Functions to the Unicast Delivery block in End-User Functions. A solid blue arrow labeled 'FEC flow' goes from the Error Recovery block in Content Delivery Functions to the Error Recovery Client block. 2. A grey box labeled 'network-based Place-shifting' is positioned between the two main boxes. 3. Play phase: A dashed green arrow labeled 'Information FeedBack' goes from the Control Client block to the Content Delivery Control block. A dashed green arrow labeled 'Error Recovery Config/Control message' goes from the Content Delivery Control block to the Error Recovery Client block. A solid purple arrow labeled 'Content Flow & FEC flow' goes from the Unicast Delivery block in Content Delivery Functions to the Unicast Delivery block in End-User Functions. A solid blue arrow labeled 'FEC flow' goes from the Error Recovery block in Content Delivery Functions to the Error Recovery Client block. Vertical blue arrows on the far left are labeled 'Setup' and 'Play'.](692541e65db4dc852988ce77ebb60ce5_img.jpg)
+
+Sequence diagram illustrating the AFEC recovery flow for place-shifting service. The diagram is divided into two main functional areas: 'End-User Functions' (pink background) and 'Content Delivery Functions' (orange background). The 'End-User Functions' box contains three sub-blocks: 'Error Recovery Client Functional Block' (blue), 'Unicast Delivery Functional Block' (red), and 'Control Client Functional Block' (green). The 'Content Delivery Functions' box contains three sub-blocks: 'Content Delivery Control Functional Block' (green), 'Unicast Delivery Functional Block' (red), and 'Error Recovery Functional Block' (blue). The sequence of interactions is as follows: 1. Setup phase: A dashed green arrow labeled 'Error Recovery Config/Control message' goes from the Content Delivery Control block to the Error Recovery Client block. A solid purple arrow labeled 'Content Flow & FEC flow' goes from the Unicast Delivery block in Content Delivery Functions to the Unicast Delivery block in End-User Functions. A solid blue arrow labeled 'FEC flow' goes from the Error Recovery block in Content Delivery Functions to the Error Recovery Client block. 2. A grey box labeled 'network-based Place-shifting' is positioned between the two main boxes. 3. Play phase: A dashed green arrow labeled 'Information FeedBack' goes from the Control Client block to the Content Delivery Control block. A dashed green arrow labeled 'Error Recovery Config/Control message' goes from the Content Delivery Control block to the Error Recovery Client block. A solid purple arrow labeled 'Content Flow & FEC flow' goes from the Unicast Delivery block in Content Delivery Functions to the Unicast Delivery block in End-User Functions. A solid blue arrow labeled 'FEC flow' goes from the Error Recovery block in Content Delivery Functions to the Error Recovery Client block. Vertical blue arrows on the far left are labeled 'Setup' and 'Play'.
+
+**Figure II.6 – AFEC recovery flow for place-shifting service**
+
+In network-based place-shifting, the IPTV service provider sends the IPTV traffic to the moved-to place [ITU-T Y.Sup5].
+
+The description of the flow is as follows:
+
+- 1) During setup, the content delivery control functional block delivers FEC configure/control information to the error recovery functional block and the end user.
+- 2) After setup, the error recovery functional block generates a FEC flow and sends the flow to the error recovery client functional block for error recovery.
+- 3) During the play period, the control client functional block may periodically send feedback with the necessary information (including packet loss, delay, power, etc.) to reflect the current channel condition.
+- 4) In case that a channel condition change is detected by using the information feedback, the content delivery control functional block may change the configure/control information in the error recovery functional block, resulting in a new FEC flow that adapts to the new channel condition.
+
+In this example, the error recovery configure/control information and information feedback may be standardized.
+
+# Appendix III
+
+## Evaluation results and recommended parameter settings for error recovery mechanisms
+
+(This appendix does not form an integral part of this Recommendation)
+
+### III.1 FEC according to [ETSI TS 102 034]
+
+#### III.1.1 Parameters
+
+The DVB-IPTV FEC code according to Annex E of [ETSI TS 102 034], and as recommended in Annex A of this Recommendation, is a block erasure code, meaning that it applies erasure protection to blocks of packets of the original stream. The code is basically fully determined by two parameters:
+
+- 1) The size of each of these blocks is usually expressed in terms of the *protection period*, which is the interval of time taken to send the packets of a block.
+- 2) For each block, the FEC code provides a number of additional "repair" packets that can then be sent immediately after the original packets of the block (the "source" packets). The number of FEC packets sent for each block is another parameter of the code, usually expressed as the *FEC overhead* – the ratio of FEC packets to source packets.
+
+There is a trade-off between these two parameters of the code, protection period and FEC overhead: in general, if the protection period is increased, then the FEC overhead required will decrease and vice versa, all other factors remaining equal. The 'other factors' are the packet loss rate and pattern and the quality target. This feature allows service operators to trade efficiency vs. channel switching times.
+
+Note that the channel switching times correlate to the latency added by the FEC. However, there are also many other things which contribute to channel change time, for example IGMP latency, the need to wait for an IDR frame, RTP buffering, video decoding buffer, etc. These factors have already led to the development of a number of channel change acceleration techniques. A good survey is available in [b-ISMA TD 00096] and some of the techniques described there are already deployed. These techniques can be used to mitigate the additional delay caused by the use of FEC, making it practical to consider relatively long protection periods without significantly impacting channel change time.
+
+#### III.1.2 Relation to network performance parameters
+
+By some representative investigations, the FEC mechanism is related to the different network parameters.
+
+For the IP packet loss ratio (IPLR), two models are considered:
+
+- An independent random loss model assumes that each packet is lost with independent probability. Although in practice IP packet losses are not independent, this channel provides some kind of baseline from which other cases can be assessed.
+- A short burst loss model considers burst outages of fixed duration, occurring at independent random intervals (Poisson distribution). This is intended to simulate a DSL access line subject to electrical impulse noise. In this case, each impulse causes an outage equal in length to the DSL interleaving depth, which we take to be 8 ms.
+
+For a streaming service such as IPTV, the absolute IPTD is only important insofar as it affects channel change time and so need not be considered further here for the simulations. The IPTD is additive to the latency introduced by the FEC mechanism.
+
+The IP packet delay variation (IPDV) may affect the performance if it results in packets arriving too late to be rendered to the user. The use of FEC mitigates this problem, since as long as each packet arrives before the appointed time to decode its FEC block, there will be no problem. Packets at the beginning of a block could arrive extremely late and still arrive in time. On the other hand if packets at the end of the block arrive too late then they cannot be used, but these packets may be considered lost and recovered by the FEC.
+
+In general, as long as the IPDV is in the range of the protection period, or the protection period is greater than the IPDV as defined in [ITU-T Y.1541], then for QoS classes 0-4, the IPDV does not have any influence on the performance. Therefore, for QoS classes 0 and 1 and protection periods of at least 50 ms, the IPDV does not influence the performance. Furthermore, it should be noted that with the addition of modest IPDV requirements, then Y.1541 classes 2-4 would also be suitable for IPTV applications, especially if the protection period is relaxed.
+
+It is expected that erroneous packets are detected by the UDP checksum and therefore are converted to packet losses. As the IPER for QoS classes 0-4 is a magnitude less than the IPLR, this effect is negligible.
+
+#### III.1.3 Recommended parameter settings
+
+The recommended parameter settings for the DVB-IPTV FEC mechanism for QoS classes 0-4 are provided in the following. The influence of IPTD, IPDV, and IPER has been discussed previously. Therefore, the benchmarking and recommended parameter settings are provided for IPLR of  $10^{-3}$  for two channel models, namely, independent random packet losses (random) and the short burst model (burst) with 8 ms independent burst losses.
+
+Results are obtained for standard definition (2.1 Mbit/s) and high definition (9.4 Mbit/s) video streams. The streams are assumed to be CBR MPEG-2 transport streams (TS) encapsulated within RTP packets with 7 MPEG-2 TS packets per RTP packet, to achieve a MTBA of at least 4 hours. Table III.1 shows the required overhead for different bit rates, different channel models at IPLR  $10^{-3}$ , and different protection periods.
+
+**Table III.1 – Required overhead for DVB-IPTV FEC for different bit rates, different channel models at IPLR of 10e-3, and different protection periods**
+
+| Protection period | Random, 2.1 Mbit/s | Random, 9.4 Mbit/s | Burst, 2.1 Mbit/s | Burst, 9.4 Mbit/s |
+|-------------------|--------------------|--------------------|-------------------|-------------------|
+| 100 ms            | 16%                | 5%                 | 20%               | 12%               |
+| 200 ms            | 8%                 | 3.5%               | 10%               | 6%                |
+| 400 ms            | 5%                 | 3%                 | 7%                | 4%                |
+| 600 ms            | 4%                 | 2%                 | 4%                | 2.5%              |
+| 800 ms            | 3.5%               | 2%                 | 4%                | 2.5%              |
+| 1000 ms           | 3%                 | 2%                 | 4%                | 2%                |
+
+The results show that with a modest additional delay and a low-to-modest FEC overhead, a consumer television quality target of a MTBA of 4 hours can be achieved using the standard Y.1541 QoS classes 0 and 1. The provisional QoS classes 6 and 7 are not required by the use of the DVB-IPTV FEC mechanism. Note that, in all cases, the enhanced decoder, according to clause E.5.1.2 of [ETSI TS 102 034], which was applied as the minimum decoder, could not fulfil the service requirements.
+
+In addition, note that if the FEC source block structure is chosen with proper alignment, for example with the random access points of the video stream, then the FEC latency can be absorbed into the video decoding buffer latency. This would mean that the protection period is in general not additive to the end-to-end latency, but generally lower. With encoding parameters and alignment strategies, even no difference in the latency may be observed when FEC is used and when it is not.
+
+# Bibliography
+
+- [b-ITU-T G.1080] Recommendation ITU-T G.1080 (2008), *Quality of experience requirements for IPTV services.*
+- [b-ITU-T H.770] Recommendation ITU-T H.770 (2009), *Mechanisms for service discovery and selection for IPTV services.*
+- [b-IETF RFC 3450] IETF RFC 3450 (2002), *Asynchronous Layered Coding Protocol Instantiation.*
+- [b-IETF RFC 3695] IETF RFC 3695 (2004), *Compact Forward Error Correction (FEC) Schemes.*
+- [b-IETF RFC 3926] IETF RFC 3926 (2004), *FLUTE – File Delivery over Unidirectional Transport.*
+- [b-ISMA TD 00096] Internet Streaming Media Alliance (ISMA) TD00096 (2007), *Fast channel changing in RTP.*
+
+
+
+## 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.705.1-202309-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..985ce4f109b67d2faa0bfb4095195a8c8daeb31f
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:df1fd24c75458ea11a4825ba5d66828f9be3dd9f00ac276be6c1bcb17fce8e9f
+size 7269
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f854bb1b2b17cccbf26c46e1c6e77f3da290c64f
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c5b097f24764bbca391e582b13f2dde50e5f710a02a5c532542fac1d0184de7
+size 30783
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f452033973505561a8564b588e44e822eeb91db3
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:589f766b6801f7d1653c867251ed13a2b80aced2d65990bc51276e51dcd7ee4e
+size 64860
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/19a5f0db57a21a0e82a7f326083e96fd_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/19a5f0db57a21a0e82a7f326083e96fd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..76389e3accc27bf6bb2bdbc85edc962b41b51d7b
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/19a5f0db57a21a0e82a7f326083e96fd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aaa6db7a114febc23f73306b83a6ccac909c6e00a112caba048b5febd27c3b70
+size 57169
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f9305c0a12d18a8a5f4e527def7244445b7235bb
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2a682e134a31f4287202b065601bde609f627b65c85eecb6dae6e36a8d3a0425
+size 85079
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/28d75f39a24203712ee907b32cf0bbe5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..86ba6d49e7cbd801c89f15ff3cc53912ddf27b51
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/28d75f39a24203712ee907b32cf0bbe5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1d4fedc45b1e7bb6d993964f0b8ee30088fb872f7107ea83a09bcb5403d7330d
+size 39128
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7fbe3d04db9d1e601fdf94922f29520ecb24c366
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a3f42b711d4e14569aaab258b95920744e2c9505109379e04550383577dac41c
+size 39346
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/4f148853ae68fdcf5e43f7604cab457d_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/4f148853ae68fdcf5e43f7604cab457d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d909536bf55a4f040e88c9b79c494d66be57f868
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/4f148853ae68fdcf5e43f7604cab457d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5a80911d51483ea2b6d76ca88a75bfaebc33e0d27421ef444762705e7877e287
+size 9280
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/55136bc716146672fc680fa05989f1d2_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/55136bc716146672fc680fa05989f1d2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..98f604f00f6bd3f7b9eee593a4992420f7fc11bb
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/55136bc716146672fc680fa05989f1d2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f28a49ccd3ac63ec9dfd0cbf14ff11497a70019677d941916a28931ad76821b5
+size 63720
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c854b8540a78cd310937d94cf32d2abcc54c48f9
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e8add055eca71299c492718ccda4bc7a412e303a6b9de988b83fe9de2a4311bf
+size 106721
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/6ca05954842b17f14dfd52f26b9d43d2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..da4f8a1ba1570c197b91754133f0550fca76106a
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/6ca05954842b17f14dfd52f26b9d43d2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:edc647c3bd8e6f9f5dd42443bbb05af2c7f37828dd56d1cafaa58026f4ac57a2
+size 59252
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/744acfe8d4e31bcf03f95714c2f6e567_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4f9d8ef59f9eebecb339e856e21123e1e49e64bf
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/744acfe8d4e31bcf03f95714c2f6e567_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2acc43c00ddcddc4593280c43e6dda02d1b1361d7fab5803f5cb1a6b92c03a62
+size 44011
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4206ac5c23309a9842149c36cf79fc6a96749934
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1ca7203047a5e7fa86897461d2e8821cbf0dfcdfac9847d3d7b2bd81f257304e
+size 69912
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/a3472689858b068ef469213682965325_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/a3472689858b068ef469213682965325_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3ae3bccb4f320680a1beb9999f2d0372d37f534d
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/a3472689858b068ef469213682965325_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:19a8e34054b0268611c1f37d2e4dd3005d5c3850752df0f571c091bc533551dc
+size 58121
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3264fbb5c14e37d330d50d9ccaefaaa12e16a21c
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d7622d49b3c30cecd6d6dcc3a518ccfa1c98e4d1ddf1ec86bcf6e14363017f46
+size 37300
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/d116934392360da963e91d840d1e45a8_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/d116934392360da963e91d840d1e45a8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b67789c8e9f14c95eecfc1b097f27fa194be90ea
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/d116934392360da963e91d840d1e45a8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2000b00324e9ff7e3a59776f298cc149306be35e62bba47dbb188ad919650889
+size 33502
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/d3f6de4fe9f9138fc6afc584b5104433_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/d3f6de4fe9f9138fc6afc584b5104433_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..723b2671a5a8ecf64e530c02e34101ac2ef29e67
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/d3f6de4fe9f9138fc6afc584b5104433_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1bc56865f55087069350038e7970e2301188e6910162d5c9817ba89b583f00c4
+size 2609
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/dc22d132f81aafd8d8e2ebae77bdbedd_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/dc22d132f81aafd8d8e2ebae77bdbedd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5fbbdedc46c7a4f9bd83259617f0de02ef09180e
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/dc22d132f81aafd8d8e2ebae77bdbedd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:90a6d6f07578caa13e85cef19be31f3e546cfcd6866499b719e63d241b03c617
+size 3922
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b7a2185d34673a56b295e9d38d4d2aa55771a881
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e94949ec2528cba9ed95fefa432caaacbe486a4e19642222d631a8615c74e6a8
+size 40170
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3d855178fe4c628b1a485099b65ca3e18414230c
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:388030a71baad78c5ef6fc665b9fc24f080d44f9e04a470c3d219baf0b4039ba
+size 125596
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/e9b30aeb317ed964fa6de36804acf24c_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/e9b30aeb317ed964fa6de36804acf24c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ba056616eaabc3ee49f5fd6d3434fd12b7b13fb6
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/e9b30aeb317ed964fa6de36804acf24c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c1d51a04d0a45a4b94569cefd618f9ce4aa1b2d518f8563947557b5d6083f4f
+size 2694
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/ec3647789b5c38fb686f2a0833324e79_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/ec3647789b5c38fb686f2a0833324e79_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7c51935b8e109de2f55f8756876aac647eb18540
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/ec3647789b5c38fb686f2a0833324e79_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4f1b93d311e036a1cef299b0dde58a3fe04c0190e616b0f799bdbfc184794b23
+size 45609
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f5f5cc501c87e2f31391dd1449bb77471f222305
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0350e7a6bdaeb01e060e5f2bc813e6c87ab5d1c7954473dcf06ce44e3c0518b8
+size 40898
diff --git a/marked/H/T-REC-H.705.1-202309-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.705.1-202309-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ddbe7f1e86e0e06c6ad5abea6a1e9c02d8e0abd9
--- /dev/null
+++ b/marked/H/T-REC-H.705.1-202309-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3acb37e5adeb20595d27e4ea8cacdd98e5c6c5fc0a4ac065b17391eec339b0be
+size 51621
diff --git a/marked/H/T-REC-H.705.2-202309-I_PDF-E/raw.md b/marked/H/T-REC-H.705.2-202309-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..49ae571bccf6fc41e17e97e91f6aa492f3e6a364
--- /dev/null
+++ b/marked/H/T-REC-H.705.2-202309-I_PDF-E/raw.md
@@ -0,0 +1,666 @@
+
+
+# Recommendation **ITU-T H.705.2 (09/2023)**
+
+SERIES H: Audiovisual and multimedia systems
+
+IPTV multimedia services and applications for IPTV –  
+General aspects
+
+---
+
+# **Requirements for live streaming systems based on the QUIC transport protocol**
+
+![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 grid lines and the letters 'ITU' in a bold, 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                          | 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        |
+| <b>General aspects</b>                                          | <b>H.700-H.719</b> |
+| 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.2
+
+# Requirements for live streaming systems based on the QUIC transport protocol
+
+## Summary
+
+Recommendation ITU-T H.705.2 specifies the requirements of a live streaming system to utilize quick user datagram protocol (UDP) Internet connections (QUIC) transport protocol to improve its delivery performance and security. It also describes the procedures and framework for QUIC-based live streaming system to provide unicast or multicast service encapsulating in QUIC protocol.
+
+With this Recommendation, a live streaming service provider can gain an understanding of how to utilize QUIC protocol to provide unicast or multicast live streaming media service. With QUIC transport protocol, the services will have lower connection establishment and delivery delay, enhanced delivery performance, and security insurance.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T H.705.2  | 2023-09-13 | 16          | 11.1002/1000/15634 |
+
+## Keywords
+
+CDN, HTTP, live streaming, multicast, QUIC, RTP, RTSP.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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           | Introduction .....                                                | 3  |
+| 6.1         | Introduction to the QUIC protocol .....                           | 3  |
+| 6.2         | QUIC-based live streaming system architecture .....               | 4  |
+| 7           | Requirements on QUIC-based live streaming system.....             | 4  |
+| 7.1         | General requirements for QUIC-based live streaming service.....   | 4  |
+| 7.2         | Requirements for application functions.....                       | 5  |
+| 7.3         | Requirements for service control functions.....                   | 5  |
+| 7.4         | Requirements for content delivery functions .....                 | 5  |
+| 7.5         | Requirement for network functions.....                            | 6  |
+| 7.6         | Requirements for management functions.....                        | 6  |
+| 8           | Adaptations for QUIC based IPTV functions.....                    | 6  |
+| 8.1         | Adaptations for application functions .....                       | 6  |
+| 8.2         | Adaptations for service control functions.....                    | 6  |
+| 8.3         | Adaptations for content delivery functions .....                  | 6  |
+| 8.4         | Adaptations for network functions .....                           | 7  |
+| 8.5         | Adaptations for management functions.....                         | 7  |
+| 9           | QUIC-based live streaming framework.....                          | 7  |
+| 9.1         | Hybrid QUIC-based live streaming system.....                      | 7  |
+| 9.2         | QUIC-based multicast service framework .....                      | 9  |
+| Appendix I  | – Live streaming use cases and scenarios.....                     | 11 |
+| I.1         | High latency live streaming (End-to-end delay > 5 seconds).....   | 11 |
+| I.2         | Low latency live streaming (End-to-end delay 1 ~ 5 seconds) ..... | 11 |
+| I.3         | Ultra-low latency live streaming (End-to-end delay < 1s) .....    | 12 |
+| Appendix II | – Conventional live streaming architecture .....                  | 14 |
+| II.1        | IPTV-based live streaming architecture .....                      | 14 |
+| II.2        | OTT live streaming architecture.....                              | 15 |
+|             | Bibliography.....                                                 | 17 |
+
+
+
+# Requirements for live streaming systems based on the QUIC transport protocol
+
+# 1 Scope
+
+This Recommendation focuses on solving the problems that emerge when deploying quick user datagram protocol (UDP) Internet connections (QUIC) on a live streaming system, as well as systematically analysing the QUIC streaming system requirements and use case scenarios.
+
+The Recommendation covers the study of:
+
+- Use case studies and QUIC-based live streaming scenarios analysis;
+- Requirements on QUIC-based live streaming platforms;
+- Requirements on QUIC-based live streaming network, including multicast requirements and device requirements;
+- Requirements on QUIC-based live streaming system architecture evolution including real-time transport protocol (RTP) mapping and hybrid request routing;
+- Security mechanisms 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 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 9000] IETF RFC 9000 (2021), *QUIC: A UDP-Based Multiplexed and Secure Transport*.
+- [IETF RFC 9001] IETF RFC 9001 (2021), *Using TLS to Secure QUIC*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 application level gateway (ALG)** [b-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.
+
+**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 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.4 terminal device (TD)** [ITU-T Y.1901]: An end-user device that 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.2 Terms defined in this Recommendation**
+
+This Recommendation defines the following terms:
+
+**3.2.1 hybrid QUIC-based live streaming system:** A QUIC-based live streaming system that only uses the QUIC protocol on some but not all of the uploading, delivery, and streaming service phases to transport live streaming content.
+
+**3.2.2 over-the-top live streaming:** A live streaming service whose delivery process relies on the Internet rather than the traditional Internet protocol television (IPTV) dedicated network.
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                      |
+|------|--------------------------------------|
+| CDN  | Content Delivery Network             |
+| DASH | Dynamic Adaptive Streaming over HTTP |
+| GSLB | Global Server Load Balancer          |
+| HLS  | HTTP Live Streaming                  |
+| HTTP | Hypertext Transfer Protocol          |
+| IPTV | Internet Protocol Television         |
+| QUIC | Quick UDP Internet Connections       |
+| RTP  | Real-time Transport Protocol         |
+| RTMP | Real-time Messaging Protocol         |
+| RTSP | Real-time Streaming Protocol         |
+| STB  | Set-Top Box                          |
+| TCP  | Transmission Control Protocol        |
+| TLS  | Transport Layer Security             |
+| 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 need not be present to claim conformance.
+
+# 6 Introduction
+
+The existing live streaming systems usually use real-time streaming protocol (RTSP) on Internet protocol television (IPTV) live streaming media service or hypertext transfer protocol (HTTP) on over-the-top live streaming (OTT live streaming) media service. IPTV live streaming system can use real-time transport protocol (RTP) over UDP on multicast services, and RTP over user datagram protocol (UDP) / transmission control protocol (TCP) on unicast service. However, OTT live streaming systems are running on the Internet, which is not a multicast dedicated network, and therefore cannot use the multicast protocol for its live content delivery. It usually uses content delivery network (CDN) to relay its unicast streaming requests for providing live streaming service, by using HTTP over TCP as its transport protocol. Those two types of existing streaming systems that adopt the TCP/UDP transport protocol do not meet the low latency and high quality requirements of live streaming service very well, albeit with multiple supplemental techniques provided. Because TCP is implemented in operating system kernels and client box firmware, making significant changes to TCP is next to impossible.
+
+Quick UDP Internet connections (QUIC) [IETF RFC 9000] is a new transport layer protocol that reduces latency compared to that of TCP. It is very similar to TCP+TLS+HTTP/2 implemented on UDP. Since QUIC is built on top of UDP, it is very easy to be implemented on an IPTV set-top box (STB) or a PC. In the current ITU-T Recommendations, there is a lack of study of the use cases and scenarios for using QUIC to improve the quality of delivering live content on an unreliable network with low latency requirements.
+
+## 6.1 Introduction to the QUIC protocol
+
+IETF QUIC covers different aspects of the 'core' QUIC protocol, defines mapping of HTTP semantics to it, and covers selected other topics such as transport, recovery, transport layer security (TLS), HTTP, QPACK, and load balancers.
+
+The key features of QUIC include:
+
+- Dramatically reduced connection establishment time.
+- Improved congestion control.
+- Multiplexing without head of line blocking.
+- Connection migration based on the situation.
+- Better encryption performance.
+
+Due to the above advantages of QUIC protocol, a growing number of applications have started to use it. However, there are multiple problems that need to be addressed before massive deploying QUIC on live streaming, including:
+
+- 1) Switches, gateways, and firewalls may block UDP ports used by QUIC.
+- 2) Due to the QoS restriction, Internet service providers may consider exceeding UDP packets as DDoS attacks therefore dropping them.
+- 3) The standards for deploying QUIC on multicast are not well defined.
+- 4) Deploying QUIC may require several modifications to the current IPTV platform architecture, including service discovery, security mechanisms, CDN transmission and distribution, STB software, and so on.
+
+## 6.2 QUIC-based live streaming system architecture
+
+![Diagram of QUIC-based live streaming system architecture showing the flow from Upstream to Platform to Edge server to Client.](f4fdd410cdb84df81274da55721e56fb_img.jpg)
+
+The diagram illustrates the QUIC-based live streaming system architecture, divided into four main stages by vertical dashed lines:
+
+- Upstream:** Contains 'Upstream live source' and 'Encoder'. It connects to the Platform via a 'QUIC' link.
+- Platform:** Contains 'Encapsulation translation' and 'Control'. It connects to the Edge server via a 'Live delivery' link.
+- Edge server:** Contains 'Cache', 'Unicast delivery function', 'Multicast delivery function', and 'Retransmission function'. It connects to the Client via a 'Live streaming service' link.
+- Client:** The final destination. It receives data via 'RTP over QUIC', 'HTTP over QUIC', and 'QUIC over multicast'.
+
+Labels at the bottom of the diagram: 'Upstream', 'Live uploading', 'Platform', 'Live delivery', 'Edge server', 'Live streaming service', 'Client'.
+
+Diagram of QUIC-based live streaming system architecture showing the flow from Upstream to Platform to Edge server to Client.
+
+H.705.2(23)
+
+**Figure 6-1 – QUIC-based live streaming architecture**
+
+QUIC-based live streaming can reuse the current application layer protocol, such as RTP/RTSP for IPTV or HTTP for OTT live streaming, while replacing the transportation layer protocol with QUIC.
+
+- QUIC-based upstream source usually uploads media contents with HTTP 3.0 using OTT live streaming unicast.
+- QUIC-based live streaming delivers content through HTTP 3.0. Since QUIC-based multicast technology is immature, most live streaming requests can be served through unicast.
+- QUIC-based live streaming can utilize RTP/RTSP/HTTP 3.0 as its application protocol which uses QUIC as an underlying transport protocol.
+
+# 7 Requirements on QUIC-based live streaming system
+
+Aside from the requirements described in [ITU-T Y.1901], the QUIC-based IPTV service platform should also satisfy the following requirements when utilizing QUIC.
+
+## 7.1 General requirements for QUIC-based live streaming service
+
+GR-01: The QUIC-based live streaming service is required to support QUIC-based streaming service discovery.
+
+GR-02: The QUIC-based live streaming service is required to support QUIC session control.
+
+GR-03: The QUIC-based live streaming service is required to support QUIC security mechanism.
+
+GR-04: The QUIC-based live streaming service is required to support QUIC packet forwarding.
+
+GR-05: The QUIC-based live streaming service is required to support either QUIC unicast or QUIC based multicast.
+
+![Figure 7-1 – Functions of QUIC-based IPTV live streaming system. The diagram shows a layered architecture of functions. On the left, 'End-user functions' are shown. The central part consists of four main functional blocks: 'Application functions' (top), 'Service control functions', 'Content delivery functions', and 'Network functions' (bottom). 'Application functions' include IPTV application function, Application profile functional block, SCP function, and Content preparation functions. 'Service control functions' include Service user profile functional block and Service control functional block. 'Content delivery functions' include Content distribution and location control function and Content delivery and storage function. 'Network functions' include Authentication and IP allocation function block and Resource control functional block. Below 'Network functions' are 'Transport functions' which include Access network functions, Edge functions, and Core transport functions. On the right, 'Management functions' are shown as a vertical block. At the top right, 'QUIC or Non-QUIC live upload' is indicated. On the far right, 'Content provider functions' are shown, containing 'Content and metadata sources'. The diagram is labeled H.705.2(23) at the bottom right.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+Figure 7-1 – Functions of QUIC-based IPTV live streaming system. The diagram shows a layered architecture of functions. On the left, 'End-user functions' are shown. The central part consists of four main functional blocks: 'Application functions' (top), 'Service control functions', 'Content delivery functions', and 'Network functions' (bottom). 'Application functions' include IPTV application function, Application profile functional block, SCP function, and Content preparation functions. 'Service control functions' include Service user profile functional block and Service control functional block. 'Content delivery functions' include Content distribution and location control function and Content delivery and storage function. 'Network functions' include Authentication and IP allocation function block and Resource control functional block. Below 'Network functions' are 'Transport functions' which include Access network functions, Edge functions, and Core transport functions. On the right, 'Management functions' are shown as a vertical block. At the top right, 'QUIC or Non-QUIC live upload' is indicated. On the far right, 'Content provider functions' are shown, containing 'Content and metadata sources'. The diagram is labeled H.705.2(23) at the bottom right.
+
+**Figure 7-1 – Functions of QUIC-based IPTV live streaming system**
+
+## 7.2 Requirements for application functions
+
+RAF-1: The application functions are required to support QUIC-extended service control function API.
+
+## 7.3 Requirements for service control functions
+
+RSCF 1: The service control functions are required to support QUIC-extended content delivery functions API.
+
+## 7.4 Requirements for content delivery functions
+
+RCDF 1: The content delivery functions are required to support QUIC transport protocol based on TLS/1.3. This Recommendation is based on TLS/1.3 without the guarantee of compatibility with future TLS versions. Future TLS version support is recommended but not required.
+
+RCDF 2: The content delivery functions are required to support QUIC-based client requests.
+
+RCDF 3: The content delivery functions are recommended to distribute content using QUIC multicast.
+
+RCDF 4: The content delivery functions are recommended to support QUIC encryption with external keys provided by service control functions.
+
+RCDF 5: The content delivery functions are recommended to support QUIC unicast and QUIC multicast services.
+
+RCDF 6: The content delivery functions are recommended to retransmit multicast content using QUIC unicast connection.
+
+RCDF 7: The content delivery functions are recommended to support QUIC multicast session control.
+
+RCDF 8: The content delivery functions are recommended to support QUIC multicast session secret key generation and distribution to the client.
+
+RCDF 9: The content delivery functions are recommended to support the encapsulation of existing protocols using QUIC, for example, RTP over QUIC.
+
+RCDF 10: The content delivery functions are recommended to support QUIC-based request routing services.
+
+RCDF 11: The content delivery functions are recommended to support user IP migration based on QUIC connections.
+
+## **7.5 Requirements for network transport functions**
+
+RNF 1: The transport functions are required to recognize QUIC-encapsulated UDP packets.
+
+RNF 2: The transport functions are required to forward QUIC-encapsulated UDP traffic based on configurations.
+
+RNF 3: The transport functions are required to allow QUIC-encapsulated UDP packets to pass the application level gateway (ALG) if the ALG is presented.
+
+## **7.6 Requirements for management functions**
+
+RMF 1: The management functions are required to configure QUIC requirements and recommendations in clause 8.
+
+# **8 Adaptations for QUIC based IPTV functions**
+
+To satisfy the general functional requirements described in clause 7.1, some IPTV functions should be extended to have augmented functionalities concerning QUIC.
+
+The client can detect HTTP-based QUIC streaming services such as HTTP live streaming (HLS), dynamic adaptive streaming over HTTP (DASH) with HTTP alternative services. If QUIC service is available, the client can send the QUIC-based service request to the IPTV system.
+
+## **8.1 Adaptations for application functions**
+
+According to [ITU-T Y.1910], the application functions enable the end-user functions to select and purchase or rent a content item.
+
+Application functions do not need to change to accommodate QUIC delivery. The data uploading from the content provider functions and content delivery to the end-user functions via QUIC are handled by the network functions, and the application functions will not be concerned about QUIC related issues. It only needs to be extended with an API for QUIC protocol selection.
+
+## **8.2 Adaptations for service control functions**
+
+According to [ITU-T Y.1910], the IPTV service control functional block provides the functions to handle service initiation, modification and termination requests, perform service access control, and establish and maintain the network and system resources required to support the IPTV services requested by the IPTV terminal functions.
+
+The service control functions authenticate and redirect the user request to content delivery functions, and therefore they should support the QUIC-based service API.
+
+## **8.3 Adaptations for content delivery functions**
+
+According to [ITU-T Y.1910], the content delivery functions (CDF) perform cache and storage functionalities and deliver the content according to the request from the end-user functions.
+
+The content delivery functions are the cardinal functions to implement and apply the QUIC protocol as the underlying transportation protocol. They handle QUIC session initialization, manage QUIC connections, and distribute QUIC keys in multicast service. Also, the user IP migration can be implemented in content delivery functions to fully facilitate QUIC features.
+
+It is possible for the content delivery functions to repair multicast content with unicast transmission with either or both of the methods being QUIC-based.
+
+## 8.4 Adaptations for network functions
+
+The network functions are the basic infrastructure of the QUIC protocol. They should allow the QUIC-encapsulated UDP traffic to be delivered.
+
+## 8.5 Adaptations for management functions
+
+The management functions are required to be able to configure the IPTV service platform to support QUIC functionalities as illustrated above.
+
+# 9 QUIC-based live streaming framework
+
+## 9.1 Hybrid QUIC-based live streaming system
+
+Although QUIC-based live streaming system is more efficient, secure, and reliable, and may be a better solution for future live streaming systems, the majority of extant Internet equipment does not support QUIC and thus requires software or hardware updates regarding service platform, CDN, network system, and terminal devices [b-ITU-T H.720]. The evolution towards the QUIC protocol is a time-consuming progress, in which most live streaming systems will be hybrid live streaming systems for an extended period.
+
+In a hybrid QUIC-based live streaming system, the uploading, delivery, and streaming service phases can independently use the QUIC protocol to transport their content. It is required to deploy the QUIC protocol translation function on the boundary between QUIC-enabled transportation components and QUIC-disabled transportation components. The clauses below describe exemplary hybrid QUIC-based live streaming systems.
+
+### 9.1.1 Hybrid QUIC/IPTV-based live streaming architecture
+
+Since QUIC multicast technology is immature, the IPTV live streaming system should use the traditional multicast method during the delivery phase and use QUIC-based transmission during live streaming service phase.
+
+![Figure 9-1: Hybrid IPTV multicast system using QUIC. The diagram illustrates the flow of data from an upstream live source through various components. The upstream live source (containing an encoder) sends data via QUIC to the Platform (containing Encapsulation Translation and Control). The Platform then uses Multicast over UDP to send data to the Edge server (containing Cache and RTSP QUIC server). The Edge server then uses RTSP over QUIC to send data to the Client (containing RTSP/RTP QUIC GW). The Client then uses RTSP over QUIC to send data back to the Edge server. The diagram is divided into three phases: Live uploading (Upstream live source to Platform), Live delivery (Platform to Edge server), and Live streaming service (Edge server to Client).](5dfc130b129ace4df375839020a5700d_img.jpg)
+
+The diagram shows the following components and flow:
+
+- Upstream live source:** Contains 'Upstream live source' and 'Encoder'. It connects to the Platform via a 'QUIC' link.
+- Platform:** Contains 'Encapsulation Translation' and 'Control'. It receives data from the Upstream live source and sends it to the Edge server via 'Multicast over UDP'.
+- Edge server:** Contains 'Cache' and 'RTSP QUIC server'. It receives data from the Platform and sends it to the Client via 'RTSP over QUIC'.
+- Client:** Contains 'RTSP/RTP QUIC GW'. It receives data from the Edge server and sends it back to the Edge server via 'RTSP over QUIC'.
+
+The diagram is divided into three phases by vertical dashed lines:
+
+- Live uploading:** From the Upstream live source to the Platform.
+- Live delivery:** From the Platform to the Edge server.
+- Live streaming service:** Between the Edge server and the Client.
+
+H.705.2(23)
+
+Figure 9-1: Hybrid IPTV multicast system using QUIC. The diagram illustrates the flow of data from an upstream live source through various components. The upstream live source (containing an encoder) sends data via QUIC to the Platform (containing Encapsulation Translation and Control). The Platform then uses Multicast over UDP to send data to the Edge server (containing Cache and RTSP QUIC server). The Edge server then uses RTSP over QUIC to send data to the Client (containing RTSP/RTP QUIC GW). The Client then uses RTSP over QUIC to send data back to the Edge server. The diagram is divided into three phases: Live uploading (Upstream live source to Platform), Live delivery (Platform to Edge server), and Live streaming service (Edge server to Client).
+
+**Figure 9-1 – Hybrid IPTV multicast system using QUIC**
+
+In the hybrid IPTV live streaming transmission architecture exhibited in Figure 9-1, the edge server and the client are extended with the QUIC protocol translation module. The client initiates an RTSP
+
+request through the QUIC protocol translation module to the edge RTSP live streaming server, which receives and translates the QUIC encapsulated message, generates the corresponding RTSP response encapsulated within the QUIC protocol, and sends the response via QUIC connection to the client to be processed. Then the edge server starts transmitting the requested media by translating RTP-based multicast media contents that are already received from the central node into the QUIC-based unicast content and sends them to the client. The client uses the QUIC protocol translation module to translate the QUIC-based packets into RTP-based media streams which can be recognized and processed by most media players.
+
+Clients that do not support the QUIC protocol can utilize the extant multicast protocol with the retransmission mechanism based on QUIC in order to improve the QoS of the live streaming service.
+
+![Figure 9-2 – Hybrid IPTV live streaming interfaces. The diagram shows four main components: Upstream, Platform, Edge server, and Client, separated by vertical dashed lines representing interfaces. Upstream contains 'Upstream live source' and 'Media encoder'. Platform contains 'Encapsulation Translation' and 'Control'. Edge server contains 'Multicast delivery function' and 'QUIC-based retransmission function'. Client contains 'RTSP/RTP' and 'QUIC GW'. The interfaces are: 'Live uploading' (QUIC) between Upstream and Platform; 'Live delivery' (Multicast over UDP) between Platform and Edge server; and 'Live streaming service' (Multicast, RTP over QUIC) between Edge server and Client. A small label 'H.705.2(23)' is in the bottom right corner of the diagram area.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg)
+
+Figure 9-2 – Hybrid IPTV live streaming interfaces. The diagram shows four main components: Upstream, Platform, Edge server, and Client, separated by vertical dashed lines representing interfaces. Upstream contains 'Upstream live source' and 'Media encoder'. Platform contains 'Encapsulation Translation' and 'Control'. Edge server contains 'Multicast delivery function' and 'QUIC-based retransmission function'. Client contains 'RTSP/RTP' and 'QUIC GW'. The interfaces are: 'Live uploading' (QUIC) between Upstream and Platform; 'Live delivery' (Multicast over UDP) between Platform and Edge server; and 'Live streaming service' (Multicast, RTP over QUIC) between Edge server and Client. A small label 'H.705.2(23)' is in the bottom right corner of the diagram area.
+
+**Figure 9-2 – Hybrid IPTV live streaming interfaces**
+
+To re-transmit data in multicast, the live streaming system should have a retransmission function module that can cache the multicast content and its metadata in the memory from the upstream multicast source server. When the client detects a transmission error, it establishes a QUIC-based connection with the live stream system retransmission function, which may not reside in the same physical nodes as the multicast delivery function does, and then sends a retransmission request. The retransmission function receives the retransmission request, locates the referred content using metadata, and then sends the requested content to the client through the established QUIC-based connection in a unicast manner. To detect packet missing or errors, the client QUIC protocol translation module should maintain a cache to arrange and sort the real-time transport protocol (RTP) contents.
+
+### 9.1.2 Hybrid QUIC/OTT live streaming architecture
+
+Without standardized QUIC multicast technology, QUIC-based OTT live streaming service still uses unicast. By introducing extant multicast networks and technology from IPTV into QUIC-based OTT live streaming systems in order to construct a hybrid live streaming system, the network bandwidth consumption in a streaming can be greatly reduced.
+
+![Figure 9-3 – OTT live streaming interfaces. The diagram shows four main components: Upstream, Platform, Edge server, and Client. The Upstream component contains 'Upstream live source' and 'Encoder'. The Platform component contains 'Encapsulation translation' and 'Control'. The Edge server component contains 'Cache' and 'Unicast delivery function'. The Client component is labeled 'Client'. Interfaces are shown between Upstream and Platform (HTTP/RTMP, labeled 'Live uploading'), between Platform and Edge server (Multicast over UDP, labeled 'Live delivery'), and between Edge server and Client (HTTP, labeled 'Live streaming service'). A small note 'H.705.2(23)' is present at the bottom right of the diagram.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg)
+
+Figure 9-3 – OTT live streaming interfaces. The diagram shows four main components: Upstream, Platform, Edge server, and Client. The Upstream component contains 'Upstream live source' and 'Encoder'. The Platform component contains 'Encapsulation translation' and 'Control'. The Edge server component contains 'Cache' and 'Unicast delivery function'. The Client component is labeled 'Client'. Interfaces are shown between Upstream and Platform (HTTP/RTMP, labeled 'Live uploading'), between Platform and Edge server (Multicast over UDP, labeled 'Live delivery'), and between Edge server and Client (HTTP, labeled 'Live streaming service'). A small note 'H.705.2(23)' is present at the bottom right of the diagram.
+
+**Figure 9-3 – OTT live streaming interfaces**
+
+In a QUIC-based OTT live streaming system, the platform can use encapsulation translation and transcoding functions to transform upstream media contents into multicast media contents that have a normalized encapsulation and coding scheme, and deliver them to the edge nodes through multicast. The edge nodes cache the content and provide live streaming service through QUIC-based unicast.
+
+## 9.2 QUIC-based multicast service framework
+
+Although there is no QUIC multicast profile being standardized or universally applied, there are proposals on the road towards standardization reflecting conjectures about future development. Their technical details may vary in future modifications, but the general design principles shall persist.
+
+### 9.2.1 QUIC-based multicast streaming service
+
+QUIC-based multicast streams can be delivered like standard multicast streams since they are all based on the user datagram protocol (UDP). However, the client cannot directly obtain media content encapsulated in the QUIC multicast stream by receiving the multicast stream, because it does not have the required key material to decrypt the received QUIC stream. The key material includes TLS state (encryption state, AEAD function information, etc.) and QUIC state (connection information, packet number, header protection key, etc.), which can be referenced in [IETF RFC 9001] and its referenced standards. To allow such decryption, there are two possible methods for QUIC-based multicast stream recipients to access the key material. A practice to define the QUIC multicast profile can be referenced in the draft "Multicast Extension for QUIC" [b-draft-jholland-quic-multicast].
+
+1. The QUIC multicast service provider can agree with its clients on the key material of the multicast QUIC stream. The key material can either be explicitly defined or be derived through a set of rules.
+2. The QUIC multicast service provider can send the key material to the client directly or indirectly. In a simplified scenario, the client can establish a QUIC connection with the QUIC multicast server and request the key material of the multicast channel. Upon receiving the key material, the client can therefore receive and decrypt the multicast QUIC stream.
+
+The first method is simple but invalidates the meaning of using encryption and QUIC. The second option is more sophisticated but preferable if using QUIC multicast.
+
+Using the second method, a potential service process can be described as follows. The client sends its content request with a content ID to the global server load balancer (GSLB), and the GSLB responds with multicast channel information for that content along with the key material. The client will join the multicast group using the multicast channel information and decrypt the QUIC stream using key material from GSLB. If the key material is changed periodically to ensure service management and safety, when it is updated, the GSLB will send a notification and new key material to the client if it is still active.
+
+### 9.2.2 QUIC-based multicast service for unicast client
+
+In some IPTV systems, clients do not have access to a multicast network due to ISP restrictions, but their closest gateway can access multicast content and relay that content to the client via unicast. In a QUIC-based IPTV system, the encryption process of QUIC must be taken into account.
+
+![Diagram illustrating the procedure of QUIC-based multicast streaming for unicast clients. The diagram shows the flow of key material and QUIC multicast media content from a Multicast server through a Multicast network and Multicast network gateway to clients (Client A and Client B) via the GSLB.](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg)
+
+The diagram illustrates the flow of data and key material in a QUIC-based multicast streaming system. At the top, a 'Multicast server' sends 'QUIC multicast media content' to a cloud representing the 'Multicast network'. The 'Multicast network' then sends this content to a 'Multicast network gateway'. The 'Multicast network gateway' sends 'QUIC multicast media content' to 'Client A' and 'Client B'. A 'GSLB' (Global Server Load Balancer) is connected to the 'Multicast network gateway' and sends 'Key material' to it. The 'GSLB' also receives 'Key material' from the 'Multicast server' and sends it to the 'Multicast network gateway'. The 'Multicast network gateway' sends 'Key material' to 'Client A' and 'Client B'. A legend on the right indicates that a double-headed arrow represents 'Bidirectional / QUIC unicast' and a single-headed arrow represents 'Unidirectional / QUIC multicast'.
+
+H.705.2(23)
+
+Diagram illustrating the procedure of QUIC-based multicast streaming for unicast clients. The diagram shows the flow of key material and QUIC multicast media content from a Multicast server through a Multicast network and Multicast network gateway to clients (Client A and Client B) via the GSLB.
+
+**Figure 9-4 – Procedure of QUIC-based multicast streaming for unicast client**
+
+In this scenario, a client will first send the media content request with the content ID to the GSLB. The GSLB parses the request and responds with a multicast service label. The client will parse the multicast service label to obtain the QUIC-based multicast service information, including the QUIC multicast service name and use the QUIC multicast service information to request the multicast content from the gateway of the multicast network. The multicast service name will be used to locate the gateway through multicast DNS service discovery. Upon receiving the client's request, if the gateway has not received such a multicast label before, it will start the QUIC multicast service registration process. First, it retrieves QUIC multicast channel information, including key material, from the GSLB using the multicast label, and sends the key material to each requester. Then the gateway will join the multicast group of QUIC. When the gateway receives a QUIC multicast stream, and relays one copy of the stream to each requester through unicast. Each requester will use the key material to decrypt the QUIC stream and obtain the media content. When the key material is updated, the GSLB will send a notification and the new key material to the gateway, which in turn relays it to any of its active requesters for further usage.
+
+# Appendix I
+
+## Live streaming use cases and scenarios
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Live streaming services can be classified from various perspectives. They can be divided into IPTV live streaming, OTT live streaming, and mobile device live streaming in terms of the types of terminal devices; live media streaming and whole file streaming in terms of the media formats; and unicast streaming, multicast streaming, and broadcast streaming in terms of the service network types. This Recommendation focuses on the live streaming system requirements based on QUIC, whose prominent feature is the low delay in transportation. Therefore, the following clauses will categorize the live streaming service into high-delay/latency live streaming, low-delay/latency live streaming, and ultra-low-delay/latency live streaming.
+
+### I.1 High latency live streaming (End-to-end delay > 5 seconds)
+
+High latency live streaming usually applies to non-interactive live streaming scenarios such as non-interactive OTT live streaming and digital audio broadcast channels.
+
+- 1) Typical end-to-end content delivery scenario
+
+![Diagram of a typical end-to-end content delivery system for high latency live streaming. The flow is: Source media content -> Encoder -> Live streaming platform -> CDN -> Unicast -> Client. The label H.705.2(23) is at the bottom right.](36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg)
+
+```
+graph LR; A[Source media content] --> B[Encoder]; B --> C[Live streaming platform]; C --> D[CDN]; D -- Unicast --> E[Client];
+```
+
+H.705.2(23)
+
+Diagram of a typical end-to-end content delivery system for high latency live streaming. The flow is: Source media content -> Encoder -> Live streaming platform -> CDN -> Unicast -> Client. The label H.705.2(23) is at the bottom right.
+
+**Figure I.1 – Typical end-to-end content delivery system for high latency live streaming**
+
+In a typical non-interactive high-latency live streaming scenario, such as UGC live streaming, the media host records and encodes the media contents and uploads them to the live stream platform, which in turn performs transcoding and multiplexing on the content and injects them into the content delivery network (CDN). The client can request the media contents from the CDN.
+
+Due to the high latency during the content delivery, the high-latency live streaming service is only used in non-interactive live streaming scenarios and is unable to support the real-time interaction between the host and audiences, which is necessary for a live show.
+
+- 2) Media format
+
+Usually in high latency live streaming services, the payloads of media content are encapsulated in variable bit-rate container/file formats. The delivery of high latency live streaming content can be based on HTTP for session control and media data transmission, such as HLS and DASH.
+
+- 3) Transportation protocol
+
+The conventional high latency live streaming service usually delivers their contents through CDN via TCP protocol. In recent years, multicast OTT live streaming solutions have been gradually applied, which deliver HLS/DASH based media content through a multicast-dedicated network based on the UDP.
+
+### I.2 Low latency live streaming (End-to-end delay 1 ~ 5 seconds)
+
+As the "live streaming + X" business models continue to be developed in various businesses, plenty of interactive live streaming applications emerge, such as e-commercial live advertisement, online
+
+education, live sports, and live entertainment, which put serious demands on reducing the streaming transmission delay.
+
+Typical scenarios may include:
+
+- E-commercial: in the "instant buy" activities, the high delay will reduce the initiatives to interact, thus lowering the sales.
+- Online education: the interactive experience in remote teaching is highly dependent on the delay.
+- Live sports: delay affects the psychological resonance of the audiences.
+- Live show: delay affects the efficacy of interactions and feedback between the compère and the audiences.
+
+Due to the demand for interactive capability, live streaming services require a better network performance with respect to low latency.
+
+#### 1) Typical end-to-end content delivery scenario
+
+![Diagram of a typical end-to-end content delivery system for low latency live streaming. The flow is: Source media content -> Encoder -> Live streaming platform -> CDN -> Client. A bidirectional 'Interaction' line connects the Live streaming platform and the Client. The 'Media content' flows from the CDN to the Client. The diagram is labeled H.705.2(23).](9cd90f495b95ad2116ff780248c26d95_img.jpg)
+
+```
+graph LR; A[Source media content] --> B[Encoder]; B --> C[Live streaming platform]; C --> D[CDN]; D -- Media content --> E[Client]; C -- Interaction --> E;
+```
+
+Diagram of a typical end-to-end content delivery system for low latency live streaming. The flow is: Source media content -> Encoder -> Live streaming platform -> CDN -> Client. A bidirectional 'Interaction' line connects the Live streaming platform and the Client. The 'Media content' flows from the CDN to the Client. The diagram is labeled H.705.2(23).
+
+**Figure I.2 – Typical end-to-end content delivery system for low latency live streaming**
+
+In a typical low latency live streaming scenario, the media source content, being locally encoded by the media content producer is usually uploaded via a streaming protocol such as a real-time messaging protocol (RTMP) [b-IETF RFC 7425] and WebRTC [b-IETF RFC 8835] to the live streaming platform, which will subsequently transcode and encapsulate the media content, and inject them onto the CDN. The client can request the media content using live media streaming protocol (RTMP and WebRTC) from the CDN.
+
+In this scenario, the clients can interact with the live streaming platform and thus the host within a negligible delay in the sense of human communication, but they do not need to interact with the CDN.
+
+#### 2) Media format
+
+In low latency live streaming, media content is usually encoded into a variable bit-rate version and encapsulated using stream media formats supported by live streaming transport protocols such as RTMP/TCP and RTP/UDP.
+
+#### 3) Network and protocol
+
+Low latency live streaming usually distributes media content through the CDN, using TCP or UDP unicast network protocol.
+
+### **I.3 Ultra-low latency live streaming (End-to-end delay < 1s)**
+
+The ultra-low latency live streaming is usually required for strong interactive live streaming scenarios, including field-of-view (FOV) enhanced virtual reality streaming, and cloud game streaming.
+
+#### 1) Typical end-to-end content delivery scenario
+
+![Figure I.3: Typical end-to-end content delivery system for ultra-low latency live streaming. The diagram shows a flow from Source media content to Encoder to Live streaming platform to CDN to Client. The CDN and Client are connected by three lines: Media content, Control signal, and Interaction. The label H.705.2(23) is at the bottom right.](9c6461e1e94afae4dec455e69a2ce152_img.jpg)
+
+```
+
+graph LR
+    S[Source media content] --> E[Encoder]
+    E --> L[Live streaming platform]
+    L --> C[CDN]
+    C -- Media content --> Cl[Client]
+    C -- Control signal --> Cl
+    Cl -- Interaction --> C
+  
+```
+
+H.705.2(23)
+
+Figure I.3: Typical end-to-end content delivery system for ultra-low latency live streaming. The diagram shows a flow from Source media content to Encoder to Live streaming platform to CDN to Client. The CDN and Client are connected by three lines: Media content, Control signal, and Interaction. The label H.705.2(23) is at the bottom right.
+
+**Figure I.3 – Typical end-to-end content delivery system for ultra-low latency live streaming**
+
+Taking viewport-dependent virtual reality (VR) live streaming as an example of the ultra-low latency live streaming scenario. In the viewport-dependent VR live streaming service, the VR content source will be stored in the CDN in the form of tiles, and the client will request the corresponding tiles via a control signal based on the viewport orientation to avoid downloading a full amount of VR media content. The quality of experience of viewport-dependent VR service highly relies on network latency.
+
+In this scenario, the clients can interact with the live streaming platform using the control signal and the CDN within a negligible delay in the sense of human perception.
+
+#### 2) Media format
+
+Ultra-low latency live streaming usually uses stream media formats that can have media content's random-access interval be less than a second, such as DASH and other stream media formats supported by RTP.
+
+#### 3) Network and protocol
+
+Ultra-low latency live streaming usually distributes media content through the CDN, using UDP unicast streaming protocol which allows a stateful connection between the client and the CDN.
+
+# Appendix II
+
+## Conventional live streaming architecture
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### II.1 IPTV-based live streaming architecture
+
+Figure II.1 shows the content delivery functions in the IPTV architecture and the corresponding reference points (refer to [ITU-T Y.1910] for further details).
+
+![Diagram of IPTV-based live streaming architecture showing functional blocks and reference points.](3da1a07cb87051bf616c9876db958cf0_img.jpg)
+
+The diagram illustrates the IPTV-based live streaming architecture, organized into two main functional groups. The top group, 'Content distribution and location control functions', contains two sub-blocks: 'Location control functional block' and 'Distribution control functional block'. Reference points A2, C2, and C1 are at the top, and S1 is on the left. The bottom group, 'Content delivery and storage functions', contains a 'Content delivery control functional block' at the top, followed by a grid of four blocks: 'Cache/storage functional block', 'Distribution functional block', 'Error recovery functional block', 'Content processing functional block', 'Unicast delivery functional block', and 'Multicast delivery functional block'. Reference points S5, E6, and E4 are on the left, and D1 is between the two main groups. At the bottom, reference points Uc, Mc, and Md are shown. The diagram is labeled H.705.2(23).
+
+Diagram of IPTV-based live streaming architecture showing functional blocks and reference points.
+
+Figure II.1 – Content delivery functions in [ITU-T Y.1910]
+
+In [ITU-T Y.1910], the content delivery functions consist of two groups of functions:
+
+- Content distribution and location control functions (CD & LCF);
+- Content delivery and storage functions (CD & SF).
+
+Figure 7-1 applies to IPTV live streaming and video-on-demand scenarios. IPTV video on-demand service only use unicast transmission while live streaming services can use both unicast and multicast transmission.
+
+According to the architecture exhibited in Appendix I, IPTV live streaming architecture can be depicted as the following:
+
+![Figure II.2 – IPTV-based live streaming architecture diagram. The diagram is divided into three vertical sections by dashed blue lines: 'Live uploading', 'Live delivery', and 'Live streaming service'. In the 'Live uploading' section, an 'Upstream live source' and 'Encoder' are connected to a 'TS over unicast' transport. In the 'Live delivery' section, the transport connects to a 'Platform' containing 'Encapsulation translation' and 'Control'. The 'Platform' then connects to an 'Edge server' in the 'Live streaming service' section. The 'Edge server' has two parallel paths: one for 'Unicast delivery function' (with 'Cache' and 'Retransmission') using 'RTP over unicast' and 'RTSP over unicast' to a 'Client'; and another for 'Multicast delivery function' (with 'Retransmission') using 'RTP over multicast' to a 'Client'. Labels 'Upstream', 'Platform', 'Edge server', and 'Client' are at the bottom.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg)
+
+Figure II.2 – IPTV-based live streaming architecture diagram. The diagram is divided into three vertical sections by dashed blue lines: 'Live uploading', 'Live delivery', and 'Live streaming service'. In the 'Live uploading' section, an 'Upstream live source' and 'Encoder' are connected to a 'TS over unicast' transport. In the 'Live delivery' section, the transport connects to a 'Platform' containing 'Encapsulation translation' and 'Control'. The 'Platform' then connects to an 'Edge server' in the 'Live streaming service' section. The 'Edge server' has two parallel paths: one for 'Unicast delivery function' (with 'Cache' and 'Retransmission') using 'RTP over unicast' and 'RTSP over unicast' to a 'Client'; and another for 'Multicast delivery function' (with 'Retransmission') using 'RTP over multicast' to a 'Client'. Labels 'Upstream', 'Platform', 'Edge server', and 'Client' are at the bottom.
+
+H.705.2(23)
+
+**Figure II.2 – IPTV-based live streaming architecture**
+
+As Figure II.2 shows, IPTV live streaming consists of three phases classified as live streaming upload, live streaming distribution, and live streaming service.
+
+- IPTV live streaming upload usually encapsulates the payloads through MPEG2-TS ([b-ISO/IEC 13818-1]) and transports them using unicast protocol through QoS guaranteed private network.
+- IPTV live streaming distribution can deliver content through the CDN or Internet multicast via unicast or multicast separately.
+- IPTV live streaming service usually adopts stream media method, using real-time streaming protocol (RTSP) as the control protocol and RTP as the data transmission protocol. Because RTP is built on top of UDP, the IPTV system usually has a retransmission function to improve QoS. IPTV live streaming can adopt both unicast and multicast methods.
+
+### **II.2 OTT live streaming architecture**
+
+![Figure II.3 – OTT live streaming architecture diagram. The diagram is divided into three vertical sections by dashed blue lines: 'Live uploading', 'Live delivery', and 'Live streaming service'. In the 'Live uploading' section, an 'Upstream live source' and 'Encoder' are connected to an 'HTTP/RTMP' transport. In the 'Live delivery' section, the transport connects to a 'Platform' containing 'Encapsulation Translation' and 'Control', which then connects via 'QUIC' to an 'Edge server'. In the 'Live streaming service' section, the 'Edge server' (with 'Cache' and 'Unicast delivery function') connects via 'HTTP' to a 'Client'. Labels 'Upstream', 'Platform', 'Edge server', and 'Client' are at the bottom.](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg)
+
+Figure II.3 – OTT live streaming architecture diagram. The diagram is divided into three vertical sections by dashed blue lines: 'Live uploading', 'Live delivery', and 'Live streaming service'. In the 'Live uploading' section, an 'Upstream live source' and 'Encoder' are connected to an 'HTTP/RTMP' transport. In the 'Live delivery' section, the transport connects to a 'Platform' containing 'Encapsulation Translation' and 'Control', which then connects via 'QUIC' to an 'Edge server'. In the 'Live streaming service' section, the 'Edge server' (with 'Cache' and 'Unicast delivery function') connects via 'HTTP' to a 'Client'. Labels 'Upstream', 'Platform', 'Edge server', and 'Client' are at the bottom.
+
+H.705.2(23)
+
+**Figure II.3 – OTT live streaming architecture**
+
+Classical OTT live streaming consists of three reference points: live streaming upload, live streaming distribution, and live streaming service.
+
+- OTT live streaming usually uploads via HTTP or RTMP using the Internet by unicast protocol.
+
+- OTT live streaming delivery usually delivers content via HTTP. Because the prevalent HTTP version 1.1 does not support multicast, OTT live streaming service only supports unicast through the CDN.
+- OTT live streaming service usually uses adaptive HTTP streaming to deliver media content, which relies on HTTP on top of TCP, and therefore only supports unicast streaming. Meanwhile, because TCP is reliable, the OTT live streaming system does not need to consist of an error recovery function unlike the IPTV live streaming system.
+
+# Bibliography
+
+- [b-ITU-T H.720] Recommendation ITU-T H.720 (2008), *Overview of IPTV terminal devices and end systems*.
+- [b-ITU-T Y.2084] Recommendation ITU-T Y.2084 (2015), *Distributed service networking content distribution functions*.
+- [b-draft-jholland-quic-multicast] IETF RFC Internet Draft (2023), *Multicast Extension for QUIC*.  
+<<https://datatracker.ietf.org/doc/draft-jholland-quic-multicast/>>
+- [b-IETF RFC 7425] IETF RFC 7425 (2014), *Adobe's RTMFP Profile for Flash Communication*.
+- [b-IETF RFC 8835] IETF RFC 8835 (2021), *Transports for WebRTC*.
+- [b-ETSI TS 123 228] ETSI TS 123 228 V10.7.0 (2012), *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)*.  
+<[https://www.etsi.org/deliver/etsi\\_ts/123200\\_123299/123228/10.07.00\\_60/ts\\_123228v100700p.pdf](https://www.etsi.org/deliver/etsi_ts/123200_123299/123228/10.07.00_60/ts_123228v100700p.pdf)>
+- [b-ISO/IEC 13818-1] ISO/IEC 13818-1:2022, *Information technology – Generic coding of moving pictures and associated audio information – Part 1: Systems*.  
+<<https://www.iso.org/standard/83239.html>>
+
+
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.725-202406-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/marked/H/T-REC-H.725-202406-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fa802c227ec964a4c86dce7c2853e9cf0a0fd5f7
--- /dev/null
+++ b/marked/H/T-REC-H.725-202406-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2e2e9f4edb7a23936fcf8bf2779e334b0708171fde14cc71169ea1084dd25e96
+size 28538
diff --git a/marked/H/T-REC-H.725-202406-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/H/T-REC-H.725-202406-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3b0c9950a28d77ce55678819b970a9fd0c701677
--- /dev/null
+++ b/marked/H/T-REC-H.725-202406-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7872f564bafdbd673e2823c71ea725ffdac271a8ecaeb7a3a826bf60c800b96a
+size 250981
diff --git a/marked/H/T-REC-H.725-202406-I_PDF-E/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg b/marked/H/T-REC-H.725-202406-I_PDF-E/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2c8cf508e40f9d260675c7c0d2a0dccae1b6cfe1
--- /dev/null
+++ b/marked/H/T-REC-H.725-202406-I_PDF-E/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dc02f1a84c7e1aa6a392253aad01afbcc7cc393e7d15eed6721223ea00d683dd
+size 14099
diff --git a/marked/H/T-REC-H.725-202406-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/H/T-REC-H.725-202406-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7965051b4b2f7e18eb98cebcbedcbd4aa786a2ad
--- /dev/null
+++ b/marked/H/T-REC-H.725-202406-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:538a9863e2955ae0909bfc91e3d7b1bdfcfd008ce9388064287aa2678b0fd9dd
+size 130967
diff --git a/marked/H/T-REC-H.725-202406-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/H/T-REC-H.725-202406-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477
--- /dev/null
+++ b/marked/H/T-REC-H.725-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.725-202406-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg b/marked/H/T-REC-H.725-202406-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..614f2996696aff8b445fbc181531b7ea86f8abd9
--- /dev/null
+++ b/marked/H/T-REC-H.725-202406-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9bf76fa9bf2972222aaee96ca4869acf2d31094d67b445eb1691b66a40395046
+size 26777
diff --git a/marked/H/T-REC-H.725-202406-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/H/T-REC-H.725-202406-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..753dcc55393928334850e018df69a42805c68774
--- /dev/null
+++ b/marked/H/T-REC-H.725-202406-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bbde34ffd2281c956c60fcaa7da00cca53d5f0e1d628fa69385b8b02441b5aeb
+size 53732
diff --git a/marked/H/T-REC-H.725-202406-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/H/T-REC-H.725-202406-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cdcb587915e81cdff9480a0057558e78102b89b1
--- /dev/null
+++ b/marked/H/T-REC-H.725-202406-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:299cb3bf6fc1d101cf6fe203b34c778d36343f1301cf89a3dcd311ed8b7b0b7f
+size 65293
diff --git a/marked/H/T-REC-H.725-202406-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg b/marked/H/T-REC-H.725-202406-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f9ca041ea0e5e676118512911168e49a1ad6ea8f
--- /dev/null
+++ b/marked/H/T-REC-H.725-202406-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:67f1865fbc7a749d678145a8b3ba1b099c0fc3ec88cd4cc250418c1efab2265e
+size 250196
diff --git a/marked/H/T-REC-H.725-202406-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg b/marked/H/T-REC-H.725-202406-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7189ce68206af5019a57eb2d772cb128148d4fcd
--- /dev/null
+++ b/marked/H/T-REC-H.725-202406-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e538fa6a4b30758528d2faacc8214bb6f17d0decfea547a0d87f7559fe6e607
+size 39334
diff --git a/marked/H/T-REC-H.725-202406-I_PDF-E/raw.md b/marked/H/T-REC-H.725-202406-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..8683dd0f054ef2a2f8cf362e5f047e0efa21ebff
--- /dev/null
+++ b/marked/H/T-REC-H.725-202406-I_PDF-E/raw.md
@@ -0,0 +1,832 @@
+
+
+# Recommendation **ITU-T H.725 (06/2024)**
+
+SERIES H: Audiovisual and multimedia systems
+
+IPTV multimedia services and applications for IPTV – IPTV terminal devices
+
+---
+
+## **IPTV terminal device: Virtualized model**
+
+![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 grid lines and the letters 'ITU' in a bold, 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                          | 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        |
+| <b>IPTV terminal devices</b>                                    | <b>H.720-H.729</b> |
+| 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.725
+
+# IPTV terminal device: Virtualized model
+
+## Summary
+
+Recommendation ITU-T H.725 specifies the functionalities of a virtualized IPTV terminal device (IPTV TD). Virtualized IPTV TD divides the IPTV terminal function (ITF) into three parts: physical terminal (PT), function platform (FP) and logical subscriber link (LSL). It identifies key features, functional components, and service procedures of virtualized IPTV TD. Functionality partition of the PT, FP, and LSL are also included in this Recommendation.
+
+With this Recommendation, IPTV service providers are able to deploy new IPTV services with lower costs of IPTV terminals and in a more flexible way by following the architecture of virtualized IPTV TD defined in this Recommendation.
+
+## History\*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T H.725    | 2024-06-13 | 16          | 11.1002/1000/15934 |
+
+## Keywords
+
+IPTV TD, service provider.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                      | 2  |
+| 4    | Abbreviations and acronyms .....                               | 2  |
+| 5    | Conventions .....                                              | 3  |
+| 6    | Introduction .....                                             | 3  |
+| 7    | Architecture overview .....                                    | 5  |
+| 8    | Services and key features of virtualized IPTV TD .....         | 5  |
+| 8.1  | Services of virtualized IPTV TD .....                          | 5  |
+| 8.2  | Features of virtualized IPTV TD .....                          | 6  |
+| 9    | Virtualized IPTV TD functional requirement.....                | 7  |
+| 9.1  | Functional requirements for PT .....                           | 7  |
+| 9.2  | Functional requirements for FP .....                           | 7  |
+| 9.3  | Functional requirements for LSL .....                          | 8  |
+| 10   | Virtualized IPTV TD functional architecture .....              | 8  |
+| 11   | Functional components of virtualized IPTV terminal device..... | 10 |
+| 11.1 | Terminal transport functions .....                             | 10 |
+| 11.2 | Content delivery client functions.....                         | 11 |
+| 11.3 | Media client functions .....                                   | 11 |
+| 11.4 | Control client functional block.....                           | 13 |
+| 11.5 | SCP client functions .....                                     | 13 |
+| 11.6 | Application client functions .....                             | 13 |
+| 11.7 | Terminal device management functions.....                      | 13 |
+| 12   | Service procedure .....                                        | 13 |
+| 12.1 | Service initialization .....                                   | 13 |
+| 12.2 | Video service procedure .....                                  | 14 |
+| 13   | Software architecture .....                                    | 14 |
+| 13.1 | Resource abstraction layer (RAL) for PT .....                  | 15 |
+| 13.2 | Service logic adaptation layer for PT .....                    | 15 |
+| 13.3 | Presentation engine layer for PT .....                         | 15 |
+| 13.4 | Application layer for PT .....                                 | 16 |
+| 13.5 | Resource layer for FP .....                                    | 16 |
+| 13.6 | Service layer for FP .....                                     | 16 |
+| 13.7 | Presentation engine layer for FP.....                          | 16 |
+| 13.8 | Application layer for FP .....                                 | 16 |
+
+|                                        | <b>Page</b> |
+|----------------------------------------|-------------|
+| 14 Reference point and protocols ..... | 17          |
+| 14.1 Reference point A1 .....          | 18          |
+| 14.2 Reference point B1 .....          | 18          |
+| 14.3 Reference point C1 .....          | 18          |
+| 14.4 Reference point D1 .....          | 20          |
+| 14.5 Reference point E1 .....          | 20          |
+| Bibliography.....                      | 21          |
+
+# Recommendation ITU-T H.725
+
+# IPTV terminal device: Virtualized model
+
+# 1 Scope
+
+This Recommendation specifies the functionalities of the virtualized Internet protocol television (IPTV) terminal device (IPTV TD), including services and key features, functional requirements, functional architecture, functional components, service procedure, software architecture and reference point.
+
+# 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 (V3) (2022), *IPTV terminal devices: Basic model*.
+- [ITU-T H.722] Recommendation ITU-T H.722 (2014), *IPTV terminal device: Full-fledged model*.
+- [ITU-T H.750] Recommendation ITU-T H.750 (2008), *High-level specification of metadata 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.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 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.2 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 quality of service (QoS) / quality of experience (QoE), security, interactivity and reliability.
+
+- 3.1.3 IPTV terminal device [ITU-T Y.1901]:** A terminal device which has ITF functionality, e.g., an STB.
+- 3.1.4 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.5 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.6 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.7 service and content protection (SCP) [ITU-T Y.1901]:** A combination of service protection and content protection.
+- 3.1.8 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 function platform (FP):** A distributed system viewed as a logical platform which maintains one or a set of virtualized IPTV terminal functionalities and is typically deployed at the network/service provider premises.
+- 3.2.2 logical subscriber link (LSL):** A logical connection between PT and FP which contains both control and content messages.
+- 3.2.3 physical terminal (PT):** A physical end user device which maintains the non-virtualized IPTV terminal functionality and is typically located at the residential customer premises.
+- 3.2.4 virtualized IPTV TD (vTD):** An architecture of IPTV terminal device that separates the functions of IPTV terminal device [ITU-T H.720] into three partitions: physical terminal (PT), function platform (FP) and logical subscriber link (LSL).
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|       |                                            |
+|-------|--------------------------------------------|
+| CDN   | Content Delivery Network                   |
+| CSS   | Cascading Style Sheets                     |
+| DSLAM | Digital Subscriber Line Access Multiplexer |
+| ECG   | Electronic Content Guide                   |
+| EPG   | Electronic Programme Guide                 |
+| FEC   | Forward Error Correction                   |
+| FP    | Function Platform                          |
+| HLS   | HTTP Live Streaming                        |
+| IPTV  | Internet Protocol Television               |
+| LAN   | Local Area Network                         |
+| LSL   | Logical Subscriber Link                    |
+
+|       |                                                 |
+|-------|-------------------------------------------------|
+| NVRAM | Non-Volatile Random Access Memory               |
+| OLT   | Optical Line Terminal                           |
+| PT    | Physical Platform                               |
+| QoE   | Quality of Experience                           |
+| QoS   | Quality of Service                              |
+| RAL   | Resource Abstraction Layer                      |
+| RAM   | Random Access Memory                            |
+| RTMP  | Real-Time Messaging Protocol                    |
+| SADS  | Service and Application Discovery and Selection |
+| SCP   | Service and Content Protection                  |
+| SNA   | Service Navigation Application                  |
+| TCP   | Transmission Control Protocol                   |
+| TD    | Terminal Device                                 |
+| USB   | Universal Serial Bus                            |
+| VoD   | Video on Demand                                 |
+| VxLAN | Virtual Extensible 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 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 the specification.
+
+# 6 Introduction
+
+An Internet protocol television (IPTV) service provider provides end-to-end solutions for distributing contents to users via terminal devices (TDs). Figure 6-1 depicts the current infrastructure for IPTV service. This model allows operators to provide IPTV video service and some other value-added services. The flourish of video service exerts extra stress on IPTV TD performance. Current service model can lead to a number of problems:
+
+- Excessive IPTV TD cost. The rising demand of home video services calls for higher requirements for IPTV TD.
+- New service delivery difficulties. The IPTV TD bears most of the functions of the existing video services and once a new service is to be deployed, the elements in the infrastructure may be upgraded to endorse the service.
+
+- High failure rates. A full-fledged IPTV TD has complex configuration procedures and software architecture. This obstructs the IPTV TD service fulfilment and challenges the operation and maintenance procedure.
+
+![Figure 6-1: Current IPTV service architecture diagram. It shows four vertical boxes representing different entities: End-user, Network provider, Service provider, and Content provider. The End-user box contains a monitor and an IPTV TD device. The Network provider box contains a router and a server. The Service provider box contains a server. The Content provider box contains a globe icon. Solid lines connect the IPTV TD to the router, the router to the service provider server, and the service provider server to the content provider. A small label 'H.725(24)' is at the bottom right.](f4fdd410cdb84df81274da55721e56fb_img.jpg)
+
+Figure 6-1: Current IPTV service architecture diagram. It shows four vertical boxes representing different entities: End-user, Network provider, Service provider, and Content provider. The End-user box contains a monitor and an IPTV TD device. The Network provider box contains a router and a server. The Service provider box contains a server. The Content provider box contains a globe icon. Solid lines connect the IPTV TD to the router, the router to the service provider server, and the service provider server to the content provider. A small label 'H.725(24)' is at the bottom right.
+
+**Figure 6-1 – Current IPTV service architecture**
+
+Virtualized IPTV TD migrates a set of IPTV TD functionalities from home devices to the network side, i.e., the operator network. Figure 6-2 shows the virtualized model architecture and the coexistence of legacy IPTV TD.
+
+Key to Figure 6-2:
+
+- The green line indicates the communication link for legacy IPTV TD.
+- The red line indicates the communication link for virtualized IPTV TD.
+- Function platform (FP) can be deployed in an independent or distributed way. This figure only lists one possible deployment location for the function platform as an independent server.
+
+Possible deployment locations for the function platform may be access network devices (Digital subscriber line access multiplexer (DSLAM) or optical line terminal (OLT)) or some other places before the core router. Since deployment possibilities depend on existing network architecture, the numerating of deployment locations is out of scope in this Recommendation.
+
+![Figure 6-2: Coexistence of legacy IPTV TD and virtualized IPTV TD architecture diagram. It shows four vertical boxes: End-user, Network provider, Service provider, and Content provider. The End-user box contains a monitor with a 'Legacy IPTV TD' and another monitor with a 'Physical terminal'. The Network provider box contains a router, a 'Function platform' server, and a service server. The Service provider box contains a server. The Content provider box contains a globe icon. A green dashed line connects the Legacy IPTV TD to the Service provider server. A red dashed line connects the Physical terminal to the Function platform server. Solid lines connect the router to the Service provider server and the Service provider server to the Content provider. A small label 'H.725(24)' is at the bottom right.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg)
+
+Figure 6-2: Coexistence of legacy IPTV TD and virtualized IPTV TD architecture diagram. It shows four vertical boxes: End-user, Network provider, Service provider, and Content provider. The End-user box contains a monitor with a 'Legacy IPTV TD' and another monitor with a 'Physical terminal'. The Network provider box contains a router, a 'Function platform' server, and a service server. The Service provider box contains a server. The Content provider box contains a globe icon. A green dashed line connects the Legacy IPTV TD to the Service provider server. A red dashed line connects the Physical terminal to the Function platform server. Solid lines connect the router to the Service provider server and the Service provider server to the Content provider. A small label 'H.725(24)' is at the bottom right.
+
+**Figure 6-2 – Coexistence of legacy IPTV TD and virtualized IPTV TD architecture**
+
+In this case, depicted in Figure 6-2, legacy IPTV TD and physical terminal coexist in the end user domain. For virtualized IPTV TD, physical terminal should establish a connection to the function platform through LSL and the function platform uses an IP-based connection to communicate with a service provider.
+
+In virtualized architecture, FP can be treated as one or a set of network functions that runs on one or multiple cloud/entity servers. Virtualized IPTV TD architecture can reduce IPTV TD hardware costs, improve new service deployment flexibility, and simplify service configuration procedures.
+
+# 7 Architecture overview
+
+Figure 7-1 shows the conceptual architecture of IPTV vTD and other functional components of the overall IPTV architecture. A more detailed description of virtualized IPTV terminal functions is provided in clause 8.
+
+![Figure 7-1 – Virtualized IPTV terminal device architecture overview. The diagram shows three main functional blocks: End-user functions (pink), Applications functions (blue), and Management functions (grey). The End-user functions block contains Virtualized IPTV terminals (which include a Function platform and a Physical terminal connected by LSL) and Home network functions. The Applications functions block contains Service control functions (yellow) and Content delivery functions (orange). The Management functions block is a single grey box. Dashed lines with dots indicate connections: Virtualized IPTV terminals to Applications functions, Function platform to Service control functions, Physical terminal to Service control functions and Management functions, Home network functions to Network functions (green), and Service control functions to Content delivery functions.](d26959f4514c26ca19c3d6f00da85956_img.jpg)
+
+Figure 7-1 – Virtualized IPTV terminal device architecture overview. The diagram shows three main functional blocks: End-user functions (pink), Applications functions (blue), and Management functions (grey). The End-user functions block contains Virtualized IPTV terminals (which include a Function platform and a Physical terminal connected by LSL) and Home network functions. The Applications functions block contains Service control functions (yellow) and Content delivery functions (orange). The Management functions block is a single grey box. Dashed lines with dots indicate connections: Virtualized IPTV terminals to Applications functions, Function platform to Service control functions, Physical terminal to Service control functions and Management functions, Home network functions to Network functions (green), and Service control functions to Content delivery functions.
+
+Figure 7-1 – Virtualized IPTV terminal device architecture overview
+
+# 8 Services and key features of virtualized IPTV TD
+
+Virtualized IPTV TD should support all the services available to the IPTV terminal device: basic model [ITU-T H.721]. Besides, a virtualized IPTV TD is recommended to additionally support the services listed in the following clauses.
+
+Also, it is recommended to provide advanced capabilities, features, and interfaces to support all the IPTV service use cases defined in [b-ITU-T Y Sup.20].
+
+## 8.1 Services of virtualized IPTV TD
+
+### 8.1.1 Extended home networking
+
+In virtual architecture, the FP on the network side manages multiple physical platforms (PTs)' requests and makes it possible to manage multiple users within a virtual local network domain. Thus, user-to-user interaction services within the same FP such as content-sharing and interactive-game can be realized with low time latency which extends the home network.
+
+### 8.1.2 On-line storage service
+
+Virtualized IPTV TD should support online storage to facilitate the storage of user's files. Files such as photos and videos can be stored on FP and the storage capacity can be expanded on demand.
+
+## **8.2 Features of virtualized IPTV TD**
+
+### **8.2.1 Network attachment and service discovery**
+
+This is the process that enables end-users to connect to a particular service and to consume a linear TV service or a video on demand (VoD) service, after connecting their IPTV TD to the network. The details of service discovery can be found in [ITU-T H.770].
+
+#### **8.2.1.1 Terminal device attachment and initialization**
+
+PTs need to connect to FP via a physical connection (applicable protocols are found in [ITU-T H.721] Table 3 – Protocols for terminal device attachment and initialization).
+
+It is recommended that PTs can automatically connect to and register to FP once powered on. After authenticating, the PT and FP logically perform as a virtualized IPTV TD.
+
+#### **8.2.1.2 Service provider entry points**
+
+When FP and PT are connected and initialized, they need to get to the entry points of the IPTV service providers. FP can access the service provider discovery information server with an entry point.
+
+#### **8.2.1.3 Service provider discovery and service attachment**
+
+After obtaining the entry point to access the service provider, the FP gets the service provider discovery information file, which includes the location of services to attach in the file. The FP then selects a particular IPTV service to attach, the service provider information provides the necessary information for obtaining the programmes and channels for electronic programme guide (EPG), etc. The details and description of the discovery procedures and data formats mentioned in this clause are included in [ITU-T H.770]. The FP can analyse all the information and send the display information (e.g., portal EPG pages, VoD programmes or linear TV channels) to the PT according to the end-user's service selection.
+
+### **8.2.2 Security**
+
+There are some security concerns and requirements that are addressed and supported by the IPTV terminal device. Refer to clause 6.3 of [ITU-T Y.1901] for details of the security requirements.
+
+Besides, the following three security items should be further explained in virtualized IPTV TD architecture.
+
+##### **8.2.2.1 Service security items**
+
+Service security functionalities mainly authenticate whether the terminal is a legitimate virtualized IPTV TD and authorize the usage of services. The PT should first authenticate to the FP before the FP can authenticate to the server-side service and content protection (SCP) functionalities. The communication process between PT and FP should also be encrypted to provide information and service security.
+
+##### **8.2.2.2 Content protection items**
+
+Content protection functionalities are integral to IPTV services and can handle the content usage conditions and decryption keys necessary for the consumption of contents.
+
+Content protection functionalities are recommended to be deployed at the PT side. The function is the management and acquisition of rights and keys from the server side SCP functionalities. FP just transfers the requests and encrypts data caching in it.
+
+There is a secure communication (applicable security specifications are found in Table 5 of [ITU-T H.721]) channel by the mutual authentication among FP, TP and server-side SCP functionalities.
+
+##### 8.2.2.3 Storage protection items
+
+To make sure that the storage for different PTs in FP is logically independent, each storage space for PT should be isolated. Isolation of storage resources is essential in realizing information security.
+
+#### 8.2.3 Privacy
+
+Privacy data and sessions are not recommended to be stored in FP. PT and FP are required to have the capability to delete private information. The private information includes caching pictures, data, etc.
+
+### 8.2.4 Quality of service (QoS)
+
+In the delivery of the streaming content, packet losses and asynchronous communication may cause video and audio quality degradation. In order to make prolonged and stable playback possible, QoS functions and error recovery functions are recommended to be deployed in PT. Refer to [ITU-T H.721] for details of QoS. To provide stable network connections for vTD architecture and eliminate the latency between FP and PT, the following two aspects can be taken into consideration:
+
+##### 8.2.4.1 FP deployment location
+
+Deploying FP nearer to user-side can reduce transmission and processing latency between FP and PT. Whether FP is deployed in a standalone server or a set of distributed servers, the current network architecture, the amount of PTs that one FP is to manage are factors that should be taken into consideration when determining the location of FP.
+
+##### 8.2.4.2 Establish specific communication channels for management message
+
+Dedicated communication channel in LSL for management message can guarantee the user's interactive process. The management message can be transmitted through VxLan (virtual extensible local area network (LAN)) or through other protocols. This scheme can ensure that multiple users' operations can be responded in time.
+
+The overall architecture is illustrated in Figure 8-1.
+
+![Diagram showing the communication channels between a Physical terminal and a Function platform. A green double-headed arrow labeled 'Management channel' connects them, and a blue double-headed arrow labeled 'Content channel' also connects them. The diagram is labeled H.725(24) at the bottom right.](5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg)
+
+```
+graph LR; PT[Physical terminal] <--> |Management channel| FP[Function platform]; PT <--> |Content channel| FP; H725_24[H.725(24)]
+```
+
+Diagram showing the communication channels between a Physical terminal and a Function platform. A green double-headed arrow labeled 'Management channel' connects them, and a blue double-headed arrow labeled 'Content channel' also connects them. The diagram is labeled H.725(24) at the bottom right.
+
+Figure 8-1 – Specific channels for virtualized IPTV terminal
+
+# 9 Virtualized IPTV TD functional requirement
+
+This clause is specific to the functional requirements after virtualization, including requirements for PT, FP and LSL.
+
+## 9.1 Functional requirements for PT
+
+PTR-01: The PT is required to have the FP's address configured (domain name is preferred) to initialize the connection to the FP. The FP's address can be configured as a factory configuration or pre-configured when the service template is issued by a network management system.
+
+PTR-02: The PT is recommended to maintain the SCP client functions to ensure the content and copyright protection.
+
+## 9.2 Functional requirements for FP
+
+FPR-01: The FP is required to support seamless IPTV service for different types of PT.
+
+FPR-02: The FP is recommended to support connections with multiple PTs while maintaining the independence of each PT.
+
+FPR-03: The FP is recommended to manage all the PTs connecting to the FP and enable the information interaction between different PTs.
+
+FPR-04: The FP is recommended to dynamically adjust the bandwidth and the computing resources to make better use of the virtualized resources.
+
+FPR-05: Different FPs can optionally be connected to enlarge the range of interoperable PTs or to make better use of FP resources.
+
+FPR-06: One FP can optionally handover the connected PT to other FP on the premise that the service of the PT is not influenced.
+
+## **9.3 Functional requirements for LSL**
+
+LSLR-01: The LSL is required to allow the use of encryption protocols to ensure the information security between PT and FP.
+
+LSLR-02: The LSL is required to support both management protocols and content delivery protocols (RTSP, RTP, HTTP, etc.) for PT and FP.
+
+LSLR-03: The LSL is recommended to ensure the network bandwidth to guarantee the transmission of management data and content data.
+
+# **10 Virtualized IPTV TD functional architecture**
+
+The functional architecture of virtualized IPTV TD is shown in Figure 10-1.
+
+Key to Figure 10-1:
+
+- The architecture of the function platform (FP) represents the functional blocks which can be virtualized.
+- It is recommended that the function platform (FP) should have all the necessary functional blocks in order to support different kinds of physical terminals (PT).
+- The dotted lines in PT represent that the functional blocks are optional and can be virtualized and migrated to the function platform (FP) side if needed.
+- The dotted lines in FP represent that the functional blocks are optional and can act as supplementary functional blocks to PT's corresponding the functional blocks.
+
+![Functional architecture block diagram of virtualized IPTV terminal device. The diagram is split into two main sections: Function platform (FP) on the top and Physical terminal (PT) on the bottom, separated by a dashed red line. The FP section includes Application client functions (SADS client, IPTV application client), SCP client functions (Service protection client), and Content delivery client functions (Media client functions: Storage, Codecs, Media control, Metadata management; Unicast content delivery, Multicast content delivery, Error recovery). The PT section includes similar Application client functions, SCP client functions (Service protection, Content protection), Control client, and Content delivery client functions (Media client functions: Demux/mux, Storage, Codecs, Media control, Metadata management; Unicast content delivery, Multicast content delivery, Error recovery). Both sides have vertical management and transport function blocks. The FP side is labeled 'Network side' and the PT side is labeled 'End-user side'.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg)
+
+The diagram illustrates the functional architecture of a virtualized IPTV terminal device, divided into two main components: the Function platform (FP) and the Physical terminal (PT).
+
+**Function platform (FP) - Network side:**
+
+- Terminal device management for FP:** A vertical block on the left side.
+- Application client function for FP:** Contains "SADS client functional block for FP" and "IPTV application client for FP".
+- SCP client functions:** Contains "Service protection client functional block".
+- Content delivery client functions for FP:** Contains:
+  - Media client functions for FP:** Storage, Codecs, Media control, Metadata management.
+  - Unicast content delivery client functional block for FP
+  - Multicast content delivery client functional block
+  - Error recovery client functional block
+- IPTV terminal transport functions for FP:** A vertical block on the right side.
+
+**Physical terminal (PT) - End-user side:**
+
+- Terminal device management for PT:** A vertical block on the left side.
+- Application client function for PT:** Contains "SADS client functional block for PT" and "IPTV application client for PT".
+- SCP client functions:** Contains "Service protection client functional block" and "Content protection client functional block".
+- Control client functional block:** A separate block below the SCP functions.
+- Content delivery client functions for PT:** Contains:
+  - Media client functions for PT:** Demux/mux, Storage, Codecs, Media control, Metadata management.
+  - Unicast content delivery client functional block for PT
+  - Multicast content delivery client functional block
+  - Error recovery client functional block
+- IPTV terminal transport functions for PT:** A vertical block on the right side.
+
+A dashed red line separates the FP and PT sections. The FP section is labeled "Network side" and the PT section is labeled "End-user side".
+
+H.725(24)
+
+Functional architecture block diagram of virtualized IPTV terminal device. The diagram is split into two main sections: Function platform (FP) on the top and Physical terminal (PT) on the bottom, separated by a dashed red line. The FP section includes Application client functions (SADS client, IPTV application client), SCP client functions (Service protection client), and Content delivery client functions (Media client functions: Storage, Codecs, Media control, Metadata management; Unicast content delivery, Multicast content delivery, Error recovery). The PT section includes similar Application client functions, SCP client functions (Service protection, Content protection), Control client, and Content delivery client functions (Media client functions: Demux/mux, Storage, Codecs, Media control, Metadata management; Unicast content delivery, Multicast content delivery, Error recovery). Both sides have vertical management and transport function blocks. The FP side is labeled 'Network side' and the PT side is labeled 'End-user side'.
+
+Figure 10-1 – Functional architecture block diagram of virtualized IPTV terminal device
+
+# 11 Functional components of virtualized IPTV terminal device
+
+There can be various deployment options of physical terminals and function platforms depending on the segmentation of functional blocks. It is recommended that the function platform should have all the functions that can be virtualized to accommodate physical terminals with different functional blocks. Table 11-1 shows the function requirement of the physical terminal and function platform.
+
+**Table 11-1 – Function requirements of the physical terminal and function platform**
+
+| Functions/Functional blocks       |                                                                        | Physical terminal | Function platform |
+|-----------------------------------|------------------------------------------------------------------------|-------------------|-------------------|
+| IPTV terminal transport functions |                                                                        | M                 | M                 |
+| Terminal device management        |                                                                        | M                 | M                 |
+| Content delivery client functions | Unicast content delivery client function                               | M                 | M                 |
+|                                   | Multicast content delivery client function                             | O                 | M                 |
+|                                   | Error recovery client function                                         | M                 | M                 |
+| Media client functions            | Demux/mux                                                              | M                 | ×                 |
+|                                   | Storage                                                                | M                 | M                 |
+|                                   | Codecs                                                                 | M                 | M                 |
+|                                   | Media control                                                          | M                 | M                 |
+|                                   | Metadata management                                                    | O                 | M                 |
+| Control client functions          | Control client functional block                                        | M                 | ×                 |
+| SCP client functions              | Content protection client function                                     | M                 | ×                 |
+|                                   | Service protection client function                                     | M                 | ×                 |
+| Application client functions      | IPTV application client function                                       | O                 | M                 |
+|                                   | Service and application discovery and selection (SADS) client function | O                 | M                 |
+
+NOTES:
+
+- M stands for mandatory and O stands for optional.
+- The functional block of the same name in the physical terminal and function platform should together fulfil the functionalities of the IPTV terminal function.
+- The optional functional block of the physical terminal may be replaced or may work together with the same-name functional block of the function platform.
+
+## 11.1 Terminal transport functions
+
+The terminal transport functions are a logical block that takes in data such as video and audio data transmitted via IP packets. Both FP and PT have terminal transport functions.
+
+Terminal transport functions for PT comprise all the terminal transport functionalities defined in [ITU-T H.721], including communication interface, communication processing, and network attachment processing. Terminal transport functions for FP are required to have communication connection and communication processing functionality, which can communicate with the IPTV service platform and PTs.
+
+## **11.2 Content delivery client functions**
+
+The content delivery client functions to receive and control the delivery of the content from the content delivery and storage functions. Both FP and PT have content delivery client functions. After receiving the content, the content delivery client functions can optionally use the SCP client functions to decrypt and decode the content and can also optionally support playback control [ITU-T Y.1910].
+
+### **11.2.1 Unicast content delivery client functional block**
+
+The unicast content delivery client functional block receives the content from the unicast delivery functional block within the content delivery and storage functions. Both FP and PT have this functionality, the functional block for FP communicates with the content delivery control functional block within the content delivery and storage functions for the control of the unicast stream [ITU-T Y.1910]. When PT requests the VoD programme to FP, FP requests the programme to the content delivery network (CDN) to obtain the unicast stream, then FP forwards the unicast stream to PT.
+
+### **11.2.2 Error recovery client functional block**
+
+The content delivery client functions can optionally include an error recovery client functional block. Both FP and PT optionally have this functionality. This functional block performs error recovery on the content streams in conjunction with the error recovery functional block within the content delivery functions [ITU-T Y.1910]. When packet loss happens in a network, PT and FP can check it and fulfil error recovery functionality.
+
+## **11.3 Media client functions**
+
+Media client functions receive content from the content delivery client functions and process the contents to the appropriate data formats. Media client functions also achieve playback and trick mode functionalities. Both FP and PT have media client functions.
+
+### **11.3.1 Media control functional block**
+
+Media control functional block controls the following playback and trick mode functionalities. Both FP and PT have this functionality. PT requests playback and trick mode to FP, FP receives the signal and sends appropriate streams to PT.
+
+### **11.3.2 Multicast content delivery client functional block**
+
+The multicast content delivery client functional block receives the content from the multicast delivery functional block within the content delivery and storage functions. The functional block communicates with the multicast control point functional block for the selection of the multicast stream [ITU-T Y.1910]. When PT requests a linear TV programme from FP, FP joins the multicast group and obtains the multicast stream, then FP converts the multicast stream to the unicast stream and sends it to PT. This functional block can be virtualized and deployed in FP while the PT can also retain this functional block if needed.
+
+### **11.3.3 Codec functional block**
+
+The codec functional block receives the stream from the content delivery functional block and decodes it to the appropriate data formats as to render or provide it to the output interface. PT has this functionality, and this functionality can be virtualized to reduce the workload of the PT codec block. FP receives encrypted and encoded streamed data, the codec functional block for PT receives a decrypt key from the SCP client functions and decrypts streamed data before decoding, if the content is encrypted. If the QoS of the network between FP and PT cannot guarantee the transmission of streams, FP may trans-code the streams in a high compression ratio to adapt to the network quality, so the streams can be transmitted continuously.
+
+#### **11.3.4 Storage functional block**
+
+The storage functional block stores data and contents. Both FP and PT have this functionality.
+
+##### **11.3.4.1 Storage functional block for FP**
+
+The storage functional block for FP is required to store the following data.
+
+- Portal contents displayed on the PT.
+- Application data for the resident capabilities of the PT (e.g., EPG and electronic content guide (ECG)).
+- Individual contents stored by users and recommended programme files pushed by the service provider.
+- Contents delivered from CDN and to be cached.
+
+##### **11.3.4.2 Storage functional block for PT**
+
+The storage functional block for PT is required to handle the following buffers and temporary data. These temporary data are usually stored in RAM.
+
+- Jitter buffer so that the media client functions can continuously receive stream data from the content delivery client functions, even if there is a jitter due to network conditions.
+- Buffer to process forward error correction (FEC)-based error recovery mechanism. The size of this buffer depends on which FEC algorithm is chosen.
+
+The storage functional block is required to store the following permanent data if these are required to be used even after the PT restarts. These permanent data are usually stored in non-volatile random access memory (NVRAM).
+
+- Parental control information, including enable/disable of the parental control, parental guidance level, and password for parental control.
+- Network information that is manually configured by the end user or pre-configured before shipping.
+
+#### **11.3.5 Demux/mux**
+
+The Demux/mux functional entity is responsible for the following functions:
+
+- De-multiplexing of video, audio and data streams.
+- Optional re-multiplexing functionality to combine video, audio and/or data streams, for potential distribution over the home network.
+- Embedding of content tracing information if required by the content provider and not done previously.
+
+The Demux/mux functional block should be placed in the PT side.
+
+#### **11.3.6 Metadata management**
+
+The metadata, as described in [ITU-T H.750] is to be handled. This functionality can be virtualized to the FP side and it is optional for the PT to retain this functionality. It is recommended that the PT have capabilities to requests metadata from FP, and FP can receive metadata from the service provider and send it back to PT. PT can manage metadata and display a service list for the end-users. It is recommended that the FP have capabilities to retrieve metadata and to temporarily store it as cache. It is recommended that the service navigation application (SNA) on the FP be able to interact with the service provider side applications (e.g., metadata server), so that it can provide the user with content searching based on metadata (e.g., by title, genre, cast, keyword, popularity, or review).
+
+## 11.4 Control client functional block
+
+The control client functional block allows the ITF to initiate service requests to the IPTV service control functional block in order to prepare for the connection to the content delivery functions [ITU-T Y.1910].
+
+## 11.5 SCP client functions
+
+The service and content protection (SCP) client functional entity receives and manages rights and keys and provides content keys for content consumption. It is recommended that PT retain all the functionality for security considerations and FP can remain parts of the functionality as a supplementary to PT. The SCP client functions request a licence by transmitting to the SCP server a message which includes the ID concerning the rights and keys that identify the targeted rights and keys. During the playback of VoD streaming service content, a set of rights and keys is delivered from the SCP server to the PT via FP. The SCP client then sets the content key onto the descriptor of the renderer. When PT receives the encrypted content stream, the encrypted content is decrypted by the renderer using the content key, generating the decoded audio and video data.
+
+## 11.6 Application client functions
+
+### 11.6.1 IPTV application client functions
+
+This functional block interacts with its server-side counterpart to perform session management, service authorization, presentation of the content metadata, and execution of the service logic for service consumption [ITU-T Y.1910]. This functionality can be virtualized and migrated to the FP side and it's optional for PT.
+
+### 11.6.2 SADS client functions
+
+The service and application discovery and selection (SADS) client functions support the process of service provider discovery, service discovery and service selection. This functionality can be virtualized and migrated to the FP side and it is optional for PT. The PT initiates selection and discovery requests to FP, and then FP communicates with a relevant service provider to obtain service information. The FP analyses all information and sends the display information (e.g., portal EPG pages, VoD programmes or linear TV channels) to the PT according to the end-users' service selection.
+
+## 11.7 Terminal device management functions
+
+Remote management is closely related to this functional block. For details of remote management, see [ITU-T H.622.1]. Both FP and PT have this functionality. Terminal device (TD) management for PT is responsible for the management of terminal devices of PT, such as device trouble shooting, logs report, configuration updating and firmware updating, and so on. Terminal device management for FP is responsible for the management of FP, such as log reports and configuration updating.
+
+# 12 Service procedure
+
+## 12.1 Service initialization
+
+The service initialization procedure is listed in Figure 12-1:
+
+- a) After booting, the physical platform (PT) starts the registration process to function platform (FP).
+- b) FP processes the registration message and verifies the legitimacy of PT.
+- c) Once registration is successful, FP then sends the service authentication request to the IPTV service platform.
+- d) IPTV service platform handles the authentication request and replies to FP.
+
+- e) The electronic programme guide (EPG) is forwarded to PT by FP.
+
+![Sequence diagram for Service initialization showing interactions between PT, FP, and IPTV service platform.](83852ec55d4802521a727926336bedab_img.jpg)
+
+```
+
+sequenceDiagram
+    participant PT
+    participant FP
+    participant IPTV service platform
+    Note right of IPTV service platform: H.725(24)
+    PT->>FP: Register to FP
+    FP->>IPTV service platform: Service authentication request
+    IPTV service platform-->>FP: Authentication reply
+    FP-->>PT: EPG streaming
+  
+```
+
+Sequence diagram for Service initialization showing interactions between PT, FP, and IPTV service platform.
+
+**Figure 12-1 – Service initialization**
+
+## **12.2 Video service procedure**
+
+The service procedure for linear TV/video on-demand is illustrated in Figure 12-2:
+
+- a) PT forwards the service selection operation to FP.
+- b) FP establishes the connection to the IPTV service platform and requests to start a multicast/unicast service. The IPTV service platform then streams the content to FP.
+- c) FP receives the streaming and forwards it to PT.
+
+![Sequence diagram for Video service procedure showing interactions between PT, FP, and IPTV service platform.](2eb23c2210154279f8013a1594fbcc5a_img.jpg)
+
+```
+
+sequenceDiagram
+    participant PT
+    participant FP
+    participant IPTV service platform
+    Note right of IPTV service platform: H.725(24)
+    PT->>FP: Forward the service selection operation
+    FP->>IPTV service platform: Request to start a service
+    IPTV service platform-->>FP: Content streaming
+    FP-->>PT: Content streaming
+  
+```
+
+Sequence diagram for Video service procedure showing interactions between PT, FP, and IPTV service platform.
+
+**Figure 12-2 – Video service procedure**
+
+# **13 Software architecture**
+
+The diagram in Figure 13-1 presents the software architecture of a virtualized IPTV terminal.
+
+Key to Figure 13-1:
+
+- The solid lines represent the mandatory software layers/modules of virtualized IPTV TD.
+- The dotted lines represent the optional software layers/modules of virtualized IPTV TD.
+- Resources in FP software architecture can be virtual machine resources based on a cloud server or entity server.
+
+![Figure 13-1 – Software architecture of virtualized TD. The diagram is divided into two sections: FP software architecture and PT software architecture. FP software architecture shows four layers: Application layer (Applications), Presentation engine layer (Presentation engine), Service layer (Service components), and Resource layer (Resources). PT software architecture shows four layers: Application layer (Applications), Presentation engine layer (Presentation engine), Service logic adaptation layer (Service components: System manager, Media manager, Communication, Application manager, Metadata, ...), and Resource abstraction layer (RAL) which connects to Resources (HW and SW).](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg)
+
+The diagram illustrates the software architecture of virtualized TD, divided into FP (Function Platform) and PT (Physical Terminal) architectures.
+
+**FP software architecture**
+
+- Application layer** → Applications
+- Presentation engine layer** → Presentation engine
+- Service layer** → Service components
+- Resource layer** → Resources
+
+**PT software architecture**
+
+- Application layer** → Applications
+- Presentation engine layer** → Presentation engine
+- Service logic adaptation layer** → Service components (System manager, Media manager, Communication, Application manager, Metadata, ...)
+- Resource abstraction layer** → RAL → Resources (HW and SW)
+
+H.725(24)
+
+Figure 13-1 – Software architecture of virtualized TD. The diagram is divided into two sections: FP software architecture and PT software architecture. FP software architecture shows four layers: Application layer (Applications), Presentation engine layer (Presentation engine), Service layer (Service components), and Resource layer (Resources). PT software architecture shows four layers: Application layer (Applications), Presentation engine layer (Presentation engine), Service logic adaptation layer (Service components: System manager, Media manager, Communication, Application manager, Metadata, ...), and Resource abstraction layer (RAL) which connects to Resources (HW and SW).
+
+**Figure 13-1 – Software architecture of virtualized TD**
+
+## 13.1 Resource abstraction layer (RAL) for PT
+
+RAL exists for each hardware and operating system and provides the necessary interface to lower layers (e.g., random access memory (RAM), network access, hard drive, universal serial bus (USB) port, etc.) [ITU-T H.720].
+
+## 13.2 Service logic adaptation layer for PT
+
+There are several service components in the service logic adaptation layer. Service components in this layer are closely related to the services and applications PT can offer.
+
+For PT, the service logic adaptation layer contains certain service components which are needed to accomplish PT functions. In general, some service components such as system management, and media management are mandatory. Other components such as metadata and application manager are optional depending on the functional partitioning results of the physical terminal and function platform.
+
+## 13.3 Presentation engine layer for PT
+
+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 defined in [ITU-T H.722].
+
+For PT, the presentation engine layer is optional depending on the functional partitioning results of physical terminal and function platform.
+
+The options of placing the presentation engine layer are shown as follows.
+
+- Presentation engine layer is vacant in PT.
+- Presentation engine layer for PT contains necessary components and serves as a complement for FP's presentation engine layer.
+
+## **13.4 Application layer for PT**
+
+Application layer can be supported by the presentation engine layer. An application can either have full or restricted access to the presentation engine layer features. Some particular applications may directly access the service logic adaptation layer [ITU-T H.722].
+
+For PT, application layer is optional depending on the functional partitioning results of physical terminal and function platform.
+
+The options of placing the application layer are shown as follows.
+
+- Application layer is vacant in PT.
+- Application layer for PT contains necessary components and serves as a complement for FP's application layer.
+
+## **13.5 Resource layer for FP**
+
+Usually, FP is deployed on a virtual machine and the common physical resources are virtualized into computing, network and storage abilities. Resource layer for FP refers to the virtualized resources which can support the execution of the above layers/services.
+
+## **13.6 Service layer for FP**
+
+The service layer for FP is made of service components. The service components can offer functionalities common to all implementations (e.g., service selection and presentation). The following service components can be realized in the FP's service layer:
+
+- System and resource management.
+- Media management component.
+- Communication component.
+- Metadata access component.
+- User interaction component (User interaction component supports event reception and dispatching from PT to service provider [ITU-T Y.1901]).
+
+## **13.7 Presentation engine layer for FP**
+
+The presentation engine layer may include various engines along with a set of high-level services, such as document style (cascading style sheets (CSS) for IPTV), mark-up language, etc. The engines and services for the function platform should take adequate consideration of the physical terminal's presentation engine layer deployment situation to ensure the operation of related services.
+
+## **13.8 Application layer for FP**
+
+Application layer is made of several applications either downloaded or resident. An application for a function platform is powered by a presentation engine layer (e.g., HTML browser). Applications in the function platform and physical terminal (if there is one) should work together to meet all the application requirements.
+
+# 14 Reference point and protocols
+
+Figure 14-1 identifies the IPTV reference points for virtualized architecture.
+
+![Diagram of IPTV reference points for virtualized architecture showing Function platform (FP) and Physical terminal (PT) layers with various client functions and reference points A1, C1, D1, B1, E1.](d734a6ea1b381280f043fcf70391b6db_img.jpg)
+
+The diagram illustrates the IPTV reference points for virtualized architecture, divided into two main layers: Function platform (FP) and Physical terminal (PT).
+
+**Function platform (FP) Layer:**
+
+- Application client function for FP:** Contains SADS client functional block for FP and IPTV application client for FP.
+- SCP client functions:** Contains Service protection client functional block.
+- Content delivery client functions for FP:** Contains Media client functions for FP (Storage, Codecs, Media control, Metadata management), Unicast content delivery client functional block for FP, Multicast content delivery client functional block for FP, and Error recovery client functional block.
+- Terminal device management for FP:** Vertical block on the left side.
+- IPTV terminal transport functions for FP:** Vertical block on the right side.
+
+**Physical terminal (PT) Layer:**
+
+- Application client function for PT:** Contains SADS client functional block for PT and IPTV application client for PT.
+- SCP client functions:** Contains Service protection client functional block and Content protection client functional block.
+- Control client functional block:** Standalone block between SCP and Content delivery functions.
+- Content delivery client functions for PT:** Contains Media client functions for PT (Demux/mux, Storage, Codecs, Media control, Metadata management), Unicast content delivery client functional block for PT, Multicast content delivery client functional block for PT, and Error recovery client functional block.
+- Terminal device management for PT:** Vertical block on the left side.
+- IPTV terminal transport functions for PT:** Vertical block on the right side.
+
+**Reference Points:**
+
+- A1:** Between Terminal device management for FP and Terminal device management for PT.
+- C1:** Between Application client function for FP and Application client function for PT.
+- D1:** Between Content delivery client functions for FP and Content delivery client functions for PT.
+- B1:** Between IPTV terminal transport functions for FP and IPTV terminal transport functions for PT.
+- E1:** Between IPTV terminal transport functions for FP and IPTV terminal transport functions for PT.
+
+H.725(24)
+
+Diagram of IPTV reference points for virtualized architecture showing Function platform (FP) and Physical terminal (PT) layers with various client functions and reference points A1, C1, D1, B1, E1.
+
+Figure 14-1 – Reference points of virtualized terminal devices
+
+## **14.1 Reference point A1**
+
+The A1 reference point is between the terminal device management function for FP and PT.
+
+This reference point is used to deliver basic management information and the operating state of PT and FP. The message content may include network configuration, volume control, power management, etc. Communication protocol can be transmission control protocol (TCP) to convey control messages.
+
+Remote management is closely related to this functional block. For details on remote management, see [ITU-T H.622.1].
+
+## **14.2 Reference point B1**
+
+The B1 reference point is between the application client function for PT and FP.
+
+This reference point is used to deliver applications and related content between the function platform and the physical terminal. For some scenarios, there may be no application client function for PT, and then the data should be delivered directly to the content delivery client function or other related functions. Communication protocols can be HTTP live streaming (HLS) or real-time messaging protocol (RTMP) depending on the video streaming type. HTTP(s) is also included to establish the service process.
+
+## **14.3 Reference point C1**
+
+The C1 reference point is between SCP client function for PT and FP.
+
+For content protection client functional block, FP just forwards the messages between PT's content protection client functional block and content protection block. Details are to be consulted in clause 7.2 of [b-ITU-T X.1191].
+
+For service protection functional block, this reference point is used to deliver the authentication and authorization messages between PT and FP. There may be no service protection functional block in FP, and in this case the authentication and authorization message should be forwarded by FP directly. Communication protocol can be TCP.
+
+## **14.4 Reference point D1**
+
+The D1 reference point is between content delivery client functions for PT and FP. This reference point is used to receive and control the content between PT and FP. After receiving the content, the content delivery function for PT can optionally use the service and content protection (SCP) client function to decrypt and decode the content. Communication protocols can be HTTP live streaming (HLS) or real-time messaging protocol (RTMP) depending on the video streaming type. TCP protocol may also be included.
+
+## **14.5 Reference point E1**
+
+The E1 reference point is between terminal transport functions for PT and terminal transport functions for FP.
+
+This reference point is used to deliver basic IP connectivity and configurations between PT and FP. Details concerning terminal transport functions can be found in [ITU-T H.622.1] and [ITU-T H.721]. Communication protocols can be transmission control protocol (TCP) to convey configuration messages.
+
+# Bibliography
+
+- [b-ITU-T X.1191] Recommendation ITU-T X.1191 (2009), *Functional requirements and architecture for IPTV security aspects.*
+- [b-ITU-T Y Sup.20] ITU-T Y.1900-series (2012), *Supplement on scenarios and use cases of mobile IPTV.*
+
+
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.741.1-201206-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5093faf1cbf4a6535925dde3d6aabc58c67480c6
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:83e951e7f20f0248dd7bdad5a30a92c97ca2bf22fee32f7af6ecdb634e9cbd2f
+size 23210
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1c85221248f072f5ab1c41f8f43008e18ef5db0d
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f27c5515902407f6400f30d8951b4be65ea367f6b939327ab3b5f0f438e5a457
+size 27677
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..527ea8b96f6161416fd91b73988c0a5c981571f4
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88eaf27927372a46323229851e116b6bc4cab972bc2db0fedf7eb7d816430618
+size 44417
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b446a38b0be47bb434e4ef280ec56813ab505e35
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0f111df46ad45df81ee2017811b14b14d121e1b2841a88099d7280f20d154148
+size 82829
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1e4269203bdfff77526ffc34d1a9213d84a23d56
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ac0e67363df7f81baa07070bb79ebe1a69025e65c04291b46f27d198be5553fa
+size 86854
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cfc35636bcdd790cfb3c05a6db7d86e3d0797d62
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:30d7c07c07db38bc48b05288a558d6410a68fc3292016e3559027d3b303159bf
+size 9175
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/409498e57b1f988b2b604d12cd997002_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/409498e57b1f988b2b604d12cd997002_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ef23cef8237b7b18de5458ca43a6af1830737c55
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/409498e57b1f988b2b604d12cd997002_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:abf11f50dacdb5134c6d7051fa1577e7e2c74a8cfb68f1f2e04d30cd7861485c
+size 78089
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..89bf861fe40cb7f162a17599bf5f0fae3003f020
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1a4120bbcfd43988f9128fc4642a8072dbe49c95a5b3512f8c596318340a811d
+size 47820
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9c73b4b9e24760131f7dc07b2ab57f1096ae9819
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:879659cb632cac1aa64b162ea05899c2e5c1de01be659366bd3e4663afe78197
+size 12529
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ad0674134e591f225eb3ff3df7d176efc3e75bca
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a268bf251a23a0b785453040cee3bd545c730a639e42390cfed92a2f11b0fbe
+size 13969
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..156ebbc21001df8342caf2c689d7b8eac84075da
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2b168b82995e43544aef069494831bed681febc5088c768773a96bfb92b7449f
+size 16419
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b668e9dd97bb822861659b5a2a442606b3b3971e
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5da5a46f3b8506ee34605105054fd5151ad51383a320473f780d6600571f3500
+size 48935
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4a5832b725df9fbc21ee90dc365a9df058065225
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:82a65092dc7c21206f67835f79bc1800879bf6dfe5077a1fd634a942a68c1f24
+size 14068
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3c1faf42528bf9239abe1b7adaeec5fa4250c6a2
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f9a4f280ab39e7c6eba4d01e643beb6992c24c6951224bb49969e046937388fb
+size 65792
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1dd6e186977c6e17da1ec628275564276a4e541b
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f697f7f51f3e15f506be6b6cd421d867e9715e83cecee0bedda2d809b75fcbf3
+size 40006
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/6470d350326789d5306eabcb76533951_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/6470d350326789d5306eabcb76533951_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..74c57ed0b47f6c71c0486cf7086964eaa182965b
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/6470d350326789d5306eabcb76533951_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3c2115bd564b0a2e21230c96d7c10b9ea745702624f6a8dc00f594abe6f11f5f
+size 58725
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/719ef0f734259484038b2434e5dc3f24_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..48888c704f35581f7d199bccd94f8bc35518dfcc
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/719ef0f734259484038b2434e5dc3f24_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b7fae21dcd765fb1da38f1eb8a0be676d0bb26be2fe3ce1d152418a06d5a3ea3
+size 35629
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d5d2e521b924361551dff8ba95cba2ab64269369
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:34d8c7718909abbfafdd61cf237f9aff44cc8f1530231fb0b9396290938c98ec
+size 22822
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..634838d98c924e5d6ff94741f84047a0fa70bffb
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a84262f1e2fa4fab529348cc1191edf288874f143a884d3b48c0123c930888ff
+size 3066
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6e63332c237bc673a8edf5d7fb5334b09de2387e
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:61d62ab847226a10dd4887a7649873cd72ad5848dcc8e2338ebb62105918add6
+size 12207
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6056d5582942c0d3d01d07dd1ac968902b5c62a1
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eb2105b56e35235ac616998b36b14a21fec14f5bcdbf170dcbf7d0dee922fc80
+size 62624
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/836b0790cef5469a167fa8931df4e408_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/836b0790cef5469a167fa8931df4e408_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5ef35ce6e3db4ffd0cde843cbf282afadbe8ee66
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/836b0790cef5469a167fa8931df4e408_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c369624f0cd3a06de98fe7746dcc3660a120a70f590030d6c6a6633a86d31944
+size 79028
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/875c6f4f441fdd3ca7e1908fd1582983_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/875c6f4f441fdd3ca7e1908fd1582983_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2c062355cf455748ed711e42c9a7a0642df8d34b
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/875c6f4f441fdd3ca7e1908fd1582983_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0027451c8dacd64a87dee7f08774283bca8d9c21266287f85557007c04cd4758
+size 69324
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/9b686adccf125267a013fa25721231a3_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/9b686adccf125267a013fa25721231a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e1104402e7d8141bf16deab328d137c58020c9a1
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/9b686adccf125267a013fa25721231a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:28327f3d901fc0f9bd1414ffcbb7574a36118542fb1ffa9646d5276fbc650db1
+size 32296
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..002224aff9577e6283dee968b6ff0b327b5bed86
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b760060d3873b6d5a620770819cd2d477ef796abdce3c4ae759394f95e916787
+size 41980
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..da419eafffb56f4f6b0cc03c6c72fa9c09a3b203
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ef9ff642d1da57fa6ab44f066ed01f6c49948abbf28737796d3a6530f44363fc
+size 11941
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-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.741.1-201206-I_PDF-E/ae0a735d106290c594b0bafb1f5e72e7_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/ae0a735d106290c594b0bafb1f5e72e7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6bc5dffd8856e41b6599b7c25c13f7d9510ad439
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/ae0a735d106290c594b0bafb1f5e72e7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2ea21237b58506dd8224c753b8363d2f8f87b60ad4f4ef17856bd94a606d0f2f
+size 75119
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..afad2e6cd3174413f67949fde886adbaae532ac8
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:78ecf45c294f4d0146b8b04db13e5aeafd110ca4e1dfb31c54fd88f06949cd36
+size 4218
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..581f114b9269e16489b46d5382e5d4728013d383
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6324088c7c78dfef37680af3dec38e3b8fa2e4cfc8ff26613e695be01fa43e72
+size 8020
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..22e979bf19d63423aec86e73a95c536872af65df
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8eb8e10dfe8d1957aabda3e6846f7abc53bb4ecd66fdf07d72e8dc6e0f882f6b
+size 57021
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fa8d9de7dd9d43a917c9a7bd58d60dd9bccfebaa
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ff21148c89e39321b1cf388b26084fdfba67780d537146d1e442cb0ea3769722
+size 27148
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ba38206d1ac496a36e786fffb25bef9c3a7be638
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3d20c98c106c8f0e9cd9ccb70019c6477c2e12b5b423cdafc490a507c0cf8af2
+size 101181
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b2282f9e88e383ecb41c40c4a19c447b26785837
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1ca787e57c9c087415de8d828e4be3da5082800fd1b1fd7c01e055155c50fa4e
+size 41314
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..95489ef752d97ac8711f4cb31eab28d92fb01f83
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d30cf20be5b461eca381aba99fbb32dd9399ba237a3b972f8f03395c182a740a
+size 26269
diff --git a/marked/H/T-REC-H.741.1-201206-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/H/T-REC-H.741.1-201206-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a4acbb3015eed9c04bce8395d1a225ed2272c2c5
--- /dev/null
+++ b/marked/H/T-REC-H.741.1-201206-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d4cfd7e8970803045558681b863d84a365122006b7bb0a5288c4c9126d96f77
+size 39371
diff --git a/marked/H/T-REC-H.741.2-201206-I_PDF-E/raw.md b/marked/H/T-REC-H.741.2-201206-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..5099d90a9e4aae2372a90de7b92f6acd3a47e7e3
--- /dev/null
+++ b/marked/H/T-REC-H.741.2-201206-I_PDF-E/raw.md
@@ -0,0 +1,1538 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.741.2**
+
+(06/2012)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+IPTV multimedia services and applications for IPTV –  
+IPTV application event handling
+
+---
+
+**IPTV application event handling: Data structures  
+of audience measurement for IPTV services**
+
+Recommendation ITU-T H.741.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        |
+| <b>IPTV application event handling</b>                                        | <b>H.740–H.749</b> |
+| 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.2
+
+# **IPTV application event handling: Data structures of audience measurement 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.2 specifies the data elements and structures of the payloads used in audience measurement messages.
+
+## **History**
+
+| Edition | Recommendation | Approval   | Study Group |
+|---------|----------------|------------|-------------|
+| 1.0     | ITU-T H.741.2  | 2012-06-29 | 16          |
+
+## **Keywords**
+
+Audience measurement, audience rating service, audience viewership, contents rating, data structures, distributed content service, end-user permission, engagement metrics, interactive services, IPTV application event handling, linear TV, metadata, monitoring, 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                | 4    |
+| 4 Abbreviations and acronyms .....                           | 4    |
+| 5 Conventions .....                                          | 5    |
+| 6 Data elements and structures for audience measurement..... | 5    |
+| 6.1 Data elements for audience measurement .....             | 7    |
+| 6.2 Data structures for audience measurement.....            | 21   |
+| Bibliography.....                                            | 54   |
+
+
+
+# Recommendation ITU-T H.741.2
+
+## **IPTV application event handling: Data structures of audience measurement for IPTV services**
+
+## **1 Scope**
+
+This Recommendation describes the data structures of audience measurement for IPTV services. It specifies elements and data structures of the payloads used in audience measurement messages between TD-AMFs and aggregation functions. 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.1] Recommendation ITU-T H.741.1 (2012), *IPTV application event handling: Audience measurement operations 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.891] Recommendation ITU-T X.891 (2005) | ISO/IEC 24824-1:2007, *Information technology – Generic applications of ASN.1: Fast infoset.*
+- [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 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).*
+- [IETF RFC 5246] IETF RFC 5246 (2008), *The Transport Layer Security (TLS) Protocol Version 1.2.*
+- [ISO 19136] ISO 19136:2007, *Geographic information – Geography Markup Language (GML).*
+- [ISO/IEC 23001-1] ISO/IEC 23001-1:2006, *Information technology – MPEG systems technologies – Part 1: Binary MPEG format for XML.*
+- [W3C XMLPath] W3C Recommendation (2010), *XML Path Language (XPath) 2.0 (Second Edition).*
+- [W3C XMLSchemaP2] W3C Recommendation (2001), *XML Schema Part 2: Datatypes.*
+
+## 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 Amd.1]: 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 that 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 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 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.8 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.9 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.10 content (object)** [b-ITU-T T.174]: Encoded generic value, media or non-media data.
+
+**3.1.11 electronic content guide (ECG)** [b-ITU-T H.721]: A service navigation application used especially for streamed and downloaded content. ECG deals with metadata unlike SI used in terrestrial broadcasting.
+
+**3.1.12 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.13 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.14 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.15 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.1.16 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.17 IPTV terminal device** [b-ITU-T Y.1901]: A terminal device which has IPTV terminal function (ITF) functionality, e.g., an STB.
+
+**3.1.18 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.19 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.20 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.21 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.22 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.23 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.24 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.25 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.26 service** [b-ITU-T Y.101]: A structure set of capabilities intended to support applications.
+
+**3.1.27 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.28 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.29 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.30 set-top box (STB)** [b-ITU-T J.183]: A hardware box that contains 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.31 stream** [b-ITU-T J.200]: A unidirectional continuous flow of content.
+
+**3.1.32 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.33 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**
+
+This Recommendation defines the following term:
+
+**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.
+
+## **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|        |                                               |
+|--------|-----------------------------------------------|
+| AM     | Audience Measurement                          |
+| AMF    | Audience Measurement Function                 |
+| BEEP   | Block Extensible Exchange Protocol            |
+| EDID   | Extended Display Identification Data          |
+| EISA   | Extended Industry Standard Architecture       |
+| EPG    | Electronic Programme Guide                    |
+| HMAC   | Hash-based Message Authentication Code        |
+| ID     | IDentifier                                    |
+| OTP    | One Time Password                             |
+| OUI    | Organizational Unique Identifier              |
+| PC     | Personal Computer                             |
+| PIP    | Picture In Picture                            |
+| QoE    | Quality of Experience                         |
+| QoS    | Quality of Service                            |
+| RFC    | Request for Comments                          |
+| SOAP   | Simple Object Access Protocol                 |
+| SP     | Service Provider                              |
+| TD-AMF | Terminal Device Audience Measurement Function |
+| TFTP   | Trivial File Transfer Protocol                |
+
+|         |                                                                                                         |
+|---------|---------------------------------------------------------------------------------------------------------|
+| TLS     | Transport Layer Security                                                                                |
+| TLS-SRP | Transport Layer Security – Secure Remote Password                                                       |
+| TV      | Television                                                                                              |
+| UTC     | Coordinated Universal Time                                                                              |
+| VESA    | Video Equipment Standards Association                                                                   |
+| XML     | Extensible Markup Language                                                                              |
+| XMPP    | Extensible Messaging and Presence Protocol ([b-IETF RFC 6120], [b-IETF RFC 6121] and [b-IETF RFC 6122]) |
+
+## 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'.](c78c2eefd86269d1740ab85a916f24f2_img.jpg)
+
+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'.](18442e4e239480f0c3c95b547aa8fde2_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 Data elements and structures for audience measurement
+
+This clause specifies the data elements used in audience measurement in terms of identifying name, format, values, and in some cases defaults and/or privacy classification. Data elements may be newly defined or are re-used from other sources. This clause also defines data structures in terms of relationships among the data elements. The data structures are defined for use in messages between
+
+a terminal device audience measurement function (TD-AMF) and aggregation functions, and for information to be provided to a TD-AMF independently of those messages. Data structures are defined for messages for unicast and multicast delivery.
+
+The notation is used in the following tables to facilitate the specification of the corresponding schema:
+
+- *Support*: 1 = mandatory (one instance), 0-1 = optional (maximum 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.
+
+In the following tables containing data structures, an alternative representation may be shown which illustrates the data structure. In the event of discrepancy between an alternative representation and the previous table, the correct information is to be found in the table.
+
+Data types used in clause 6.1 are shown in Table 1.
+
+**Table 1 – Data types used in ITU-T H.741.2**
+
+| Type         | Name          | Notes/reference                                                                                                                                                                       |
+|--------------|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ca:civicAddr | Civic Address | Defined in [IETF RFC 5139].                                                                                                                                                           |
+| URL          | URL           | Defined in [IETF RFC 3986] as URI= scheme ":" hier-part [ "?" query ] [ "#" fragment ].<br>Examples of official IANA-registered (URI) schemes include FTP, TFTP, SOAP, BEEP and XMPP. |
+| xs:date      | Date          | Defines a date value. The lexical form is CCYY-MM-DD where "CC" represents the century, "YY" the year, "MM" the month and "DD" the day.<br>Defined in [W3C XMLSchemaP2].              |
+| xs:dateTime  | Date and time | The format of dateTime is YYYY-MM-DDThh:mm:ss.s+zzzzz.<br>Defined in [W3C XMLSchemaP2].                                                                                               |
+| xs:float     | Float         | Float is patterned after the IEEE single-precision 32-bit floating point type.<br>Defined in [W3C XMLSchemaP2].                                                                       |
+| gml:Point    | Point         | A point consists of a <Point> element with a child <coords> element. Within <coords> the latitude and longitude values are separated by a space.<br>Defined in [ISO 19136].           |
+
+**Table 1 – Data types used in ITU-T H.741.2**
+
+| Type                   | Name                                 | Notes/reference                                                                                                                                                                                                                                                                                                                                                                                     |
+|------------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| isd:H770IDType         | Identifier                           | An example following [b-ITU-T H.770] is:<br><pre>&lt;xsd:simpleType name="H.770IDType"&gt;   &lt;xsd:union&gt;     &lt;xsd:simpleType&gt;       &lt;restriction         base="gt:IIFIDType" /&gt;     &lt;/xsd:simpleType&gt;     &lt;xsd:simpleType&gt;       &lt;restriction         base="gt:ipAddressType" /&gt;     &lt;/xsd:simpleType&gt;   &lt;/xsd:union&gt; &lt;/xsd:simpleType&gt;</pre> |
+| xs:integer             | Integer                              | The integer data type is used to specify a numeric value without a fractional component.<br>Defined in [W3C XMLSchemaP2].                                                                                                                                                                                                                                                                           |
+| nonEmptyString         | Non-empty string                     | A string having at least one character.<br>Defined as xs:string with restriction of minLength = 1.                                                                                                                                                                                                                                                                                                  |
+| xs:hexbinary           | Hexadecimal                          | Represents binary data as hexadecimal digits.<br>Defined in [W3C XMLSchemaP2].                                                                                                                                                                                                                                                                                                                      |
+| xs:integer enumeration | Integer with enumeration restriction | Restricted integer values.<br>Defined in [W3C XMLSchemaP2].                                                                                                                                                                                                                                                                                                                                         |
+| xs:nonNegativeInteger  | Non-negative integer                 | An integer containing only non-negative values (0,1,2,..).<br>Defined in [W3C XMLSchemaP2].                                                                                                                                                                                                                                                                                                         |
+| xs:positiveInteger     | Positive integer                     | An integer containing only positive values (1,2,..).<br>Defined in [W3C XMLSchemaP2].                                                                                                                                                                                                                                                                                                               |
+| xs:string              | String                               | The string data type can contain characters, line feeds, carriage returns, and tab characters.<br>Defined in [W3C XMLSchemaP2].                                                                                                                                                                                                                                                                     |
+| xs:string enumeration  | String with enumeration restriction  | Restricted string values.<br>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.<br>Defined in [W3C XMLSchemaP2].                                                                                                                                                                                                                                                   |
+| xs:unsignedShort       | Unsigned short                       | Integer with maximum value of 65'535.<br>Defined in [W3C XMLSchemaP2].                                                                                                                                                                                                                                                                                                                              |
+| xpath                  | Xpath                                | Path to and including the target element or attribute.<br>Defined in [W3C XMLPath].                                                                                                                                                                                                                                                                                                                 |
+
+### 6.1 Data elements for audience measurement
+
+The data elements for audience measurement fall into the following categories:
+
+- 1) Data elements related to the user (user device information, user information).
+- 2) Data elements related to the capture of measurements of end-user behaviours.
+
+- 3) Data elements related to privacy.
+- 4) Data elements related to messaging.
+
+Data elements related to categories 1) and 2) above are specified in the following clauses; those relating to categories 3) and 4) above are specified in clause 6.2.
+
+#### 6.1.1 User device data elements
+
+The AM data elements associated with a user's device, including capabilities, identification, configuration and usage, are included in Table 2.
+
+**Table 2 – End-user device elements used in audience measurement**
+
+| Element                      | Description                                                                                                                | Support/<br>type (Note 3)                 | Notes or value domain                                                                                                                                                                                        |
+|------------------------------|----------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| AMFCapabilityProfile         | Container to list capabilities supported by the TD-AMF implementation.                                                     | Note 1                                    |                                                                                                                                                                                                              |
+| TransportCapabilitiesList    | Element of AMFCapabilityProfile<br>Container to list transport protocols and delivery modes supported.                     | 1                                         |                                                                                                                                                                                                              |
+| TransportProtocolMode        | Element of TransportCapabilitiesList<br>Indicates the combination(s) of transport protocol and delivery mode(s) supported. | 1-*<br>xs:string<br>enumeration           | Values are out of the scope of AM.                                                                                                                                                                           |
+| SecurityCapabilities         | Element of AMFCapabilityProfile<br>Container to list security capabilities supported.                                      | 1                                         |                                                                                                                                                                                                              |
+| CryptographicProtocol        | Element of SecurityCapabilities<br>Indicates the cryptographic protocol(s) supported.                                      | 1-*<br>xs:string<br>enumeration<br>Note 4 | Values: 'TLS','TLS-SRP', 'OTP', 'HMAC'<br>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]. Only 'TLS' is mandatory. |
+| PermissionOperationModes     | Element of AMFCapabilityProfile<br>Container to list permission modes supported.                                           | 1                                         |                                                                                                                                                                                                              |
+| PermissionMode               | Element of PermissionOperationModes<br>Indicates the permission mode(s) supported.                                         | 1-*<br>xs:string<br>enumeration           | Values: 'External', 'Internal', 'Hybrid'.                                                                                                                                                                    |
+| ConfigurationPackageDelivery | Element of AMFCapabilityProfile<br>Container to list configuration modes supported.                                        | 1                                         |                                                                                                                                                                                                              |
+| ConfigurationMode            | Element of ConfigurationPackageDelivery<br>Indicates the configuration mode(s) supported.                                  | 1-*<br>xs:string<br>enumeration           | Values: 'Push', 'Pull', 'Hybrid'.                                                                                                                                                                            |
+
+**Table 2 – End-user device elements used in audience measurement**
+
+| Element                                   | Description                                                                                               | Support/<br>type (Note 3)       | Notes or value domain                                                                                                                                                                                                                                                                                                                                                            |
+|-------------------------------------------|-----------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Measurement<br>TriggerMethod              | Element of AMFCapabilityProfile<br>Container to list measurement<br>trigger(s) supported.                 | 1                               |                                                                                                                                                                                                                                                                                                                                                                                  |
+| EventTrigger                              | Element of<br>MeasurementTriggerMethod<br>Indicates the event triggers<br>supported.                      | 0-*<br>xs:string<br>enumeration | Values: "VideoResize",<br>"VideoZoom", "VideoObscure",<br>"AudioVolume", "Configuration<br>Change", "UserChange",<br>"UserInfoChange",<br>"DisplayStatus",<br>"AudioLanguageChange", and<br>"CaptionLanguageChange"<br>NOTE – Service start and<br>service stop events specified in<br>[ITU-T H.741.3] must be<br>supported so they do not need to<br>be explicitly listed here. |
+| TimeSample<br>Trigger                     | Element of<br>MeasurementTriggerMethod<br>Indicates the time sample triggers<br>supported.                | 0-*<br>xs:string<br>enumeration | Values: "UserPresent",<br>"TDLocation", "DeviceInfo",<br>"UserBioInfo", "GenericUser<br>Info", "EventCount",<br>"UserList",<br>"PermitBlockedInfo" and<br>"ChannelPlaying"<br>NOTE – The "ChannelPlaying"<br>capability is specified in<br>[ITU-T H.741.3].                                                                                                                      |
+| ServiceStart<br>Trigger                   | Element of<br>MeasurementTriggerMethod<br>Indicates the service start sample<br>triggers supported.       | 0-*<br>xs:string<br>enumeration | Values: "TDLocation",<br>"DeviceInfo", "UserBioInfo",<br>"GenericUserInfo", "UserList",<br>and "PermitBlockedInfo".                                                                                                                                                                                                                                                              |
+| ReportDelivery<br>Modes                   | Element of AMFCapabilityProfile<br>Container to list report delivery<br>mode(s) supported.                | 1                               |                                                                                                                                                                                                                                                                                                                                                                                  |
+| DeliveryMode                              | Element of ReportDeliveryModes<br>Indicates the report delivery<br>mode(s) supported.                     | 1-*<br>xs:string<br>enumeration | Values: 'ImmediatePush',<br>'Delayed Push', 'Pull',<br>'DelayedPushAndPull'.                                                                                                                                                                                                                                                                                                     |
+| Operational<br>Management<br>Capabilities | Element of AMFCapabilityProfile<br>Container to list operational<br>management capabilities<br>supported. | 1                               |                                                                                                                                                                                                                                                                                                                                                                                  |
+
+**Table 2 – End-user device elements used in audience measurement**
+
+| Element                | Description                                                                                                            | Support/<br>type (Note 3)                        | Notes or value domain                                                                                                                                                                                                                                                                                                                                                                                                   |
+|------------------------|------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Operational Management | Element of OperationalManagement Capabilities<br>Indicates the operational management capabilities supported.          | 1-*<br>xs:string<br>enumeration                  | Values: 'Acknowledgements', 'MulticastThresholdRanges', 'MulticastErrorReporting', 'MulticastUserInfo', 'MulticastDeviceType', 'MulticastMAC', 'ContentFiltering', "ChannelsMeasured", "ChannelChangeFilter", "NavMethodReporting" and "ControlDeviceReporting"<br>NOTE – "ChannelsMeasured", "ChannelChangeFilter", "NavMethodReporting" and "ControlDeviceReporting" capabilities are specified in [ITU-T H.741.3].   |
+| Compression            | Element of AMFCapabilityProfile<br>Container to list compression/decompression algorithms supported for XML payloads.  | 0-*<br>xs:string<br>enumeration<br>Default 'EXT' | Values: 'None', 'BiM', 'ZLIB', 'Infoset', or 'EXT'.<br>See Note 5.                                                                                                                                                                                                                                                                                                                                                      |
+| ServiceInstance ID     | Identifies the instance of a specific IPTV service. Distinguishes among services when multiple services are displayed. | xs:integer                                       | A ServiceInstanceID is allocated by a TD-AMF to each specific service when it starts providing unrestricted content, or when a service providing previously restricted content starts providing unrestricted content. It is de-allocated when that specific service ends, or when that service provides restricted content.<br>ServiceInstanceID has an initial value of 0, and is incremented by 1, before allocation. |
+| Caption Language       | It identifies the caption language now being used for the indicated service.                                           | xml:lang                                         |                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| AudioLanguage          | It identifies the audio language now being used for the indicated service.                                             | xml:lang                                         |                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| TVInformation          | Container for TV information.                                                                                          |                                                  | Elements related to a TV connected to a STB.                                                                                                                                                                                                                                                                                                                                                                            |
+| TVManuf                | Element of TVInformation<br>Identifies TV device manufacturer.                                                         | 0-1<br>2 bytes                                   | NOTE – EISA 3-character Plug and Play ID (PNPID) assigned by Microsoft.<br>See [b-VESA EDID].                                                                                                                                                                                                                                                                                                                           |
+
+**Table 2 – End-user device elements used in audience measurement**
+
+| Element                       | Description                                                                                            | Support/<br>type (Note 3)               | Notes or value domain                                                                                                                        |
+|-------------------------------|--------------------------------------------------------------------------------------------------------|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| TVModel                       | Element of TVInformation<br>Identifies the model number<br>of the TV.                                  | 0-1<br>2 bytes                          | NOTE – Vendor assigned code.<br>See [b-VESA EDID].                                                                                           |
+| TVSerialNum                   | Element of TVInformation<br>Identifies the serial number<br>of the TV.                                 | 0-1<br>4 bytes                          | NOTE – Vendor assigned code.<br>See [b-VESA EDID].                                                                                           |
+| IPTV-TV<br>Information        | Container for IPTV-capable TV<br>information.                                                          |                                         | Elements related to an<br>IPTV-capable TV.                                                                                                   |
+| IPTV-TVManuf                  | Element of IPTV-TVInformation<br>Identifies TV device manufacturer.                                    | 0-1<br>6 Hex ASCII<br>characters        | NOTE – IEEE 24-bit<br>organizationally unique<br>identifier OUI requiring<br>registration with the IEEE<br>Registration Authority.           |
+| IPTV-TVModel                  | Element of IPTV-TVInformation<br>Identifies the model number<br>of the TV.                             | 0-1<br>xs:string                        | Manufacturer assigned value.                                                                                                                 |
+| IPTV-TV<br>SerialNum          | Element of IPTV-TVInformation<br>Identifies the serial number<br>of the TV.                            | 0-1<br>xs:string                        | Manufacturer assigned value.                                                                                                                 |
+| AudioAmplifier<br>Information | Container for audio system<br>information. Note 2.                                                     |                                         | Elements related to an audio<br>system connected to a STB.                                                                                   |
+| AudioAmplifier<br>Manuf       | Element of<br>AudioAmplifierInformation<br>Identifies audio system device<br>manufacturer.             | 0-1<br>2 bytes                          | NOTE – EISA 3-character Plug<br>and Play ID (PNPID) assigned<br>by Microsoft.<br>See [b-VESA EDID].                                          |
+| AudioAmplifier<br>Model       | Element of<br>AudioAmplifierInformation<br>Identifies the model number of the<br>audio system device.  | 0-1<br>2 bytes                          | NOTE – Vendor assigned code<br>See [b-VESA EDID].                                                                                            |
+| AudioAmplifier<br>SerialNum   | Element of<br>AudioAmplifierInformation<br>Identifies the serial number of the<br>audio system device. | 0-1<br>4 bytes                          | NOTE – Vendor assigned code<br>See [b-VESA EDID].                                                                                            |
+| STBInformation                | Container for STB information.                                                                         |                                         |                                                                                                                                              |
+| STBManuf                      | Element of STB information<br>Identifies STB device<br>manufacturer.                                   | 0-1<br>6-byte Hex<br>ASCII<br>character | NOTE – IEEE 24-bit<br>organizational unique identifier<br>(OUI) value assigned to the<br>manufacturer by the IEEE<br>Registration Authority. |
+| STBModel                      | Element of STB information<br>Identifies STB model.                                                    | 0-1<br>nonEmpty<br>String               | Manufacturer assigned value.                                                                                                                 |
+
+**Table 2 – End-user device elements used in audience measurement**
+
+| Element                     | Description                                                                         | Support/<br>type (Note 3)               | Notes or value domain                                                                                                                        |
+|-----------------------------|-------------------------------------------------------------------------------------|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| STBSerialNum                | Element of STB information<br>Identifies STB serial number.                         | 0-1<br>nonEmpty<br>String               | Manufacturer assigned value.                                                                                                                 |
+| MobileDevice<br>Information | Container for Mobile device<br>information.                                         |                                         |                                                                                                                                              |
+| MobileDevice<br>Manuf       | Element of<br>MobileDeviceInformation<br>Identifies mobile device<br>manufacturer.  | 0-1<br>6-byte Hex<br>ASCII<br>character | NOTE – IEEE 24-bit<br>organizational unique identifier<br>(OUI) value assigned to the<br>manufacturer by the IEEE<br>Registration Authority. |
+| MobileDevice<br>Model       | Element of<br>MobileDeviceInformation<br>Identifies mobile device model.            | 0-1<br>nonEmpty<br>String               | Manufacturer assigned value.                                                                                                                 |
+| MobileDevice<br>SerialNum   | Element of<br>MobileDeviceInformation<br>Identifies mobile device serial<br>number. | 0-1<br>nonEmpty<br>String               | Manufacturer assigned value.                                                                                                                 |
+| PCInformation               | Container for PC information.                                                       |                                         |                                                                                                                                              |
+| PCManuf                     | Element of PCInformation<br>Identifies PC manufacturer.                             | 0-1<br>6-byte Hex<br>ASCII<br>character | NOTE – IEEE 24-bit<br>organizational unique identifier<br>(OUI) value assigned to the<br>manufacturer by the IEEE<br>Registration Authority. |
+| PCModel                     | Element of PCInformation<br>Identifies PC model.                                    | 0-1<br>nonEmpty<br>String               | Manufacturer assigned value.                                                                                                                 |
+| PCSerialNum                 | Element of PCInformation<br>Identifies PC serial number.                            | 0-1<br>nonEmpty<br>String               | Manufacturer assigned value.                                                                                                                 |
+| ImageSize                   | Container for size of image.                                                        |                                         | Image corresponds to the video<br>stream rendered on the screen.                                                                             |
+| ImageWidth                  | Element of ImageSize<br>Image width.                                                | xs:positive<br>Integer                  | Number of pixels in width of<br>image.                                                                                                       |
+| ImageHeight                 | Element of ImageSize<br>Image height.                                               | xs:positive<br>Integer                  | Number of pixels in height of<br>image.                                                                                                      |
+| ZoomFactor                  | Indicates the factor by which the<br>contents of the image is zoomed.               | xs:float                                | A value of 1.0 indicates that no<br>zoom is applied.                                                                                         |
+| Obscuration                 | Indicates the percentage of image<br>obscured.                                      | xs:float                                | NOTE – % based on number of<br>pixels obscured (not related to<br>transparency).                                                             |
+| Volume<br>Direction         | Indicates a rise or fall in audio<br>volume setting.                                | xs:string<br>enumeration                | Values: up, down, mute,<br>unmute.                                                                                                           |
+
+**Table 2 – End-user device elements used in audience measurement**
+
+| Element                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Description                                              | Support/<br>type (Note 3) | Notes or value domain                                                                             |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|---------------------------|---------------------------------------------------------------------------------------------------|
+| ControlDevice                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Indicates the device type used to navigate to a service. | xs:integer enumeration    | Values: 0=STB remote control, 1=STB, 2=STB keyboard, 10=PC, 20=tablet, 30=mobile phone, 40=other. |
+| <p>NOTE 1 – The listed capabilities are supported by a TD-AMF. If a capability is not listed then it is not supported, unless otherwise specified.</p> <p>NOTE 2 – The audio system corresponds to components such as the A/V Receiver/Amplifier referred to in [b-HDMI].</p> <p>NOTE 3 – The value of "other" for enumerated valued elements indicates that the element information is available but does not match one of the defined enumerated values.</p> <p>NOTE 4 – 'TLS' or 'SRPTLS' is required to be present.</p> <p>NOTE 5 – For BiM see [ISO/IEC 23001-1], for ZLIB (including GZIP) see [ETSI TS 102 472], for (Fast) Infoset see [ITU-T X.891], and for EXI see [b-W3C EXI].</p> |                                                          |                           |                                                                                                   |
+
+Figures 1 to 7 contain alternative representations of the data structures in Table 2.
+
+```
+
+AMFCapabilityProfile
+| TransportCapabilitiesList (1)
+| | TransportProtocolMode (1-*)
+| SecurityCapabilities (1)
+| | CryptographicProtocol (1-*)
+| PermissionOperationModes (1)
+| | PermissionMode (1-*)
+| ConfigurationPackageDelivery (1)
+| | ConfigurationMode (1-*)
+| MeasurementTriggerMethod (1)
+| | EventTrigger (0-*)
+| | TimeSampleTrigger (0-*)
+| | ServiceStartTrigger (0-*)
+| ReportDeliveryModes (1)
+| | DeliveryMode (1-*)
+| OperationalManagementCapabilities (1)
+| | OperationalManagement (1-*)
+| Compression (0-*)
+
+```
+
+**Figure 1 – Alternative representation of AMFCapabilityProfile data structure**
+
+```
+TVInformation
+| TVManuf (0-1)
+| TVModel (0-1)
+| TVSerialNum (0-1)
+```
+
+**Figure 2 – Alternative representation of TVInformation data structure**
+
+```
+IPTV-TVInformation
+| IPTV-TVManuf (0-1)
+| IPTV-TVModel (0-1)
+| IPTV-TVSerialNum (0-1)
+```
+
+**Figure 3 – Alternative representation of IPTV-TVInformation data structure**
+
+```
+AudioAmplifierInformation
+| AudioAmplifierManuf (0-1)
+| AudioAmplifierModel (0-1)
+| AudioAmplifierSerialNum (0-1)
+```
+
+**Figure 4 – Alternative representation of AudioAmplifierInformation data structure**
+
+```
+STBInformation
+| STBManuf (0-1)
+| STBModel (0-1)
+| STBSerialNum (0-1)
+```
+
+**Figure 5 – Alternative Representation of STBInformation data structure**
+
+```
+MobileDeviceInformation
+| MobileDeviceManuf (0-1)
+| MobileDeviceModel (0-1)
+| MobileDeviceSerialNum (0-1)
+```
+
+**Figure 6 – Alternative representation of MobileDeviceInformation data structure**
+
+```
+PCInformation
+| PCManuf (0-1)
+| PCModel (0-1)
+| PCSerialNum (0-1)
+```
+
+**Figure 7 – Alternative representation of PCInformation data structure**
+
+#### **6.1.2 User information data elements**
+
+The AM data elements associated with a user's information fall into the following categories:
+
+- 1) User information that is asserted by a user;
+- 2) User (related) information that is generated by the AM system.
+
+The AM data elements associated with each of the above categories are included in Tables 3 and 4.
+
+**Table 3 – End-user info asserted by end user, service-common elements**
+
+| Element                        | Description                                                                                                  | Support/ type                                      | Notes or value domain                                                                                                                                                                                                                                                             |
+|--------------------------------|--------------------------------------------------------------------------------------------------------------|----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| PermissionLevel                | Defines sets of end-user information that are permitted by the end user to be used for audience measurement. | xs:nonNegativeInteger<br>enumeration<br>Default: 0 | Values:<br>0 = No information,<br>1 = Only distinguishability information,<br>2 = Distinguishability and non-identifying generic end-user information,<br>3 = Identifying end-user information and non-identifying generic end-user information.<br>Not "controlled" information. |
+| ControlledUserInfo TypeString  | Identifies controlled end-user information type.                                                             | 0-*<br>nonEmptyString                              | "Controlled" information<br>NOTE – Used only for permission level 3.<br>repoValues are out of the scope of this Recommendation, e.g., Gender, AgeRange, Nationality, NumberOfChildren, MaritalStatus, Occupation, etc.                                                            |
+| ControlledUserInfo ValueString | Attribute of ControlledUserInfoType<br>Identifies controlled end-user information value.                     | 1<br>nonEmptyString                                | Values are out of the scope of this Recommendation, e.g., Female, 30-40, Spanish, 6, Married, Engineer, etc.                                                                                                                                                                      |
+| ControlledUserInfo TypeDate    | Identifies controlled end-user information type.                                                             | 0-*<br>nonEmptyString                              | "Controlled" information<br>NOTE – Used only for permission level 3.<br>Values are out of the scope of this Recommendation, e.g., Birthday.                                                                                                                                       |
+| ControlledUserInfo ValueDate   | Attribute of ControlledUserInfoTypeDate<br>Identifies controlled end-user information value.                 | 1<br>xs:date                                       | Values are out of the scope of this Recommendation, e.g., 2012-09-24.                                                                                                                                                                                                             |
+| ControlledUserInfo TypeAddress | Identifies controlled end-user information type.                                                             | 0-*<br>nonEmptyString                              | "Controlled" information<br>NOTE – Used only for permission level 3.<br>Values are out of the scope of this Recommendation, e.g., BirthLocation, UserResidentialAddress.                                                                                                          |
+
+**Table 3 – End-user info asserted by end user, service-common elements**
+
+| Element                         | Description                                                                                      | Support/ type         | Notes or value domain                                                                                                                                         |
+|---------------------------------|--------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ControlledUserInfo ValueAddress | Attribute of ControlledUserInfoType Address<br>Identifies controlled end-user information value. | 1<br>ca:civicAddr     | Values are out of the scope of this Recommendation, e.g., Fr 502, Fr 501.                                                                                     |
+| GenericUserInfoType             | Identifies generic end-user information type.                                                    | 0-*<br>nonEmptyString | NOTE – Used only for permission level 2 or 3. Values are out of scope of this Recommendation, e.g., interests, favourite programmes, favourite channels, etc. |
+| GenericUserInfo Value           | Attribute of GenericUserInfoType<br>Identifies generic end-user information value.               | 1<br>nonEmptyString   | Values are out of the scope of this Recommendation, e.g., gardening or a list of interests.                                                                   |
+
+**Table 4 – User info generated by system, service-common elements**
+
+| Element        | Description                                                                        | Type                                              | Notes or value domain                                                                                                                                                                                                                       |
+|----------------|------------------------------------------------------------------------------------|---------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TDLocation     | Container for location elements includes latitude and longitude.                   | gml:Point                                         | "Controlled" information<br>NOTE – TDLocation reports may be filtered when terminal device location changes by less than the reporting distance threshold per NothingNewReportMode or omitted when geographic location data is unavailable. |
+| UserPresent    | Container for end-user presence information from one source.                       |                                                   | Not "controlled" information<br>NOTE – Multiple sources may provide presence information.                                                                                                                                                   |
+| PresenceMethod | Element of UserPresent<br>Indicates method used to detect presence of an end user. | 0-1<br>nonEmpty String<br>Default: remote keypush | Values: remotekeypush (Note 1), others are TBD. Not "controlled" information.                                                                                                                                                               |
+| PresenceTime   | Element of UserPresent<br>Indicates last time when presence was detected.          | 0-1<br>xs:time                                    |                                                                                                                                                                                                                                             |
+
+**Table 4 – User info generated by system, service-common elements**
+
+| Element                    | Description                                                                                                                       | Type                                   | Notes or value domain                                                                                                                                                                                                        |
+|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| PresenceConfidence         | Element of UserPresent<br>Indicates confidence that any end user is present.                                                      | 0-1<br>xs:float                        | %, examples are 100% immediately after any kind of end-user interaction, decreasing as time elapses.<br>Actual values are out of scope of AM.                                                                                |
+| UserList                   | Container for one or more end-user(s) information.                                                                                | 0-1                                    | NOTE – Only end users who have given permission levels 1-3 per Table 3 are included. An empty UserList indicates no permitting users or no users.                                                                            |
+| UserIDInfo                 | Element of UserList<br>Container for individual end-user information.                                                             | 0-*                                    |                                                                                                                                                                                                                              |
+| AnonUserID                 | Element of UserIDInfo<br>Anonymous end-user ID<br>Generated number which persistently is used for one end user.                   | 0-1<br>xs:positive Integer<br>(Note 2) | Value: IPTV service provider unique.<br>NOTE – Used for permission level 1 or 2 per Table 3.<br>Generation of this number is outside scope of AM.<br>Not "controlled" information.                                           |
+| UserID                     | Element of UserIDInfo<br>This element uniquely identifies an end user.                                                            | 0-1<br>nonEmpty String<br>(Note 2)     | "Controlled" information<br>NOTE – Must be IPTV service provider unique. Generation of this string is outside scope of AM. Used for permission level 3.                                                                      |
+| UserIDMethod               | Element of UserIDInfo<br>Identifies the method used to detect the end user associated with this UserID or AnonUserID.             | 0-1<br>nonEmpty String                 | NOTE – Identity detection methods are outside the scope of AM.<br>Not "controlled" information.                                                                                                                              |
+| UserIDConfidence           | Element of UserIDInfo<br>Indicates estimate of confidence in anonymous or non-anonymous end-user IDs provided.                    | 0-1<br>xs:float                        | NOTE – %, examples are 100% for single subscriber mobile phone, 90% for just logged in user on a single user device. 0% if no information on a TV.<br>Actual values are out of scope of AM.<br>Not "controlled" information. |
+| ServiceProvider Identifier | This element contains the identifier of the IPTV service provider for which the audience measurement is proposed by the end user. | H770IdType                             | NOTE – Examples are defined in [b-ITU-T H.IPTV-MDSD] following [b-ITU-T H.770].                                                                                                                                              |
+
+**Table 4 – User info generated by system, service-common elements**
+
+| Element                | Description                                                                                                                                                                                                                                                                       | Type                                          | Notes or value domain                                                                                                                                                               |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| SubscriberID           | This element contains the identification of the subscriber to the services of the associated service provider.                                                                                                                                                                    | Nonempty String                               | Uniquely assigned by an IPTV service provider. Multiple end-users may be represented by a single SubscriberID.                                                                      |
+| PermitBlockedInfo      | Container for flags indicating that configured measurements were blocked due to a constraining end-user permit.                                                                                                                                                                   |                                               | Not "controlled" information<br>To be reported for any permission level if the PermitBlockedInfo sampleset identifier is configured.                                                |
+| PermissionLevelFlag    | Element of PermitBlockedInfo<br>Indicates the permission level which is constraining the configuration.<br>One or more of the following is true:<br>a) Biographic end user info is not reportable;<br>b) Generic end user info is not reportable;<br>c) No AM info is reportable. | 0-1<br>xs:integer<br>enumerated<br>Default: 0 | NOTE – Dependent upon the value of DefaultPermissionLevel or PermissionLevel in the user permit as defined in Table 20 and the configured measurements.<br>Values: 0, 1 or 2.       |
+| TerminalDeviceTypeFlag | Element of PermitBlockedInfo<br>Indicates that the terminal type which is not allowed to report.                                                                                                                                                                                  | 0-1                                           | NOTE – Dependent upon the value of TerminalDeviceType in the user permit as defined in Table 20 and the TD-AMF type.<br>Values: as defined by TerminalDeviceType in Table 20.       |
+| ChannelFlag            | Element of PermitBlockedInfo<br>Indicates that one or more configured linearTV channels are not reportable.                                                                                                                                                                       | 0-1<br>xs:boolean<br>Default: False           | NOTE – Dependent upon the values of ChannelQualifier in the user permit and defined in [ITU-T H.741.3] and the configured measurements.                                             |
+| ContentClassFlag       | Element of PermitBlockedInfo<br>Indicates the content classes of the user permit content class restriction which are further constraining the configuration package.                                                                                                              | 0-1                                           | Defined as AllContentClassExceptList in Table 10.<br>NOTE – Dependent upon the differences in values of AllContentClassExceptList in the user permit and the configuration package. |
+
+NOTE 1 – Remote key push is one of several optional methods to indicate presence detection. If supported, any key push on a remote control causes the time of last key push to be recorded.  
+NOTE 2 – Either AnonUserID or UserID must be present.
+
+Figures 8 to 10 contain alternative representations of the data structures in Table 4.
+
+```
+
+UserPresent
+| PresenceMethod (0-1)
+| PresenceTime (0-1)
+| PresenceConfidence (0-1)
+
+```
+
+**Figure 8 – Alternative representation of UserPresent data structure**
+
+```
+
+UserList
+| UserIDInfo (0-*)
+| | AnonUserID (0-1) (Note 2)
+| | UserID (0-1) (Note 2)
+| | UserIDMethod (0-1)
+| | UserIDConfidence (0-1)
+
+```
+
+**Figure 9 – Alternative representation of UserList data structure**
+
+```
+
+PermitBlockedInfo (0-1)
+| PermissionLevelFlag (0-1)
+| TerminalDeviceTypeFlag (0-1)
+| ChannelFlag (0-1)
+
+```
+
+**Figure 10 – Alternative representation of PermitBlockedInfo data structure**
+
+#### 6.1.3 Types of service-common events
+
+The AM system may measure the events listed in Table 5. If these are configured they are to be reported. These service-common events may occur across multiple IPTV services.
+
+**Table 5 – Types of service-common events**
+
+| Event        | Description                                                                                                                                | Notes or value domain                                                                                                                                                                 |
+|--------------|--------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| VideoResize  | Indicates that the end user has collapsed or expanded the video. Causes the VideoResize data structure defined in Table 21 to be reported. | Includes entering or leaving picture in picture (PIP), shrinking for the electronic programme guide (EPG), etc. measured by width and height of video as an integer number of pixels. |
+| VideoZoom    | Indicates that the end user has changed the zoom factor. Causes the VideoZoom data structure defined in Table 21 to be reported.           | Includes selections of zoom factor.                                                                                                                                                   |
+| VideoObscure | Indicates that the video obscuration has changed. Causes the VideoObscure data structure defined in Table 21 to be reported.               | Includes application end-user interface obscuring video.                                                                                                                              |
+| AudioVolume  | Indicates that the end user has changed the audio volume. Causes the AudioVolume data structure defined in Table 21 to be reported.        | Includes mute and unmute.                                                                                                                                                             |
+
+**Table 5 – Types of service-common events**
+
+| Event                 | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | Notes or value domain                                                                                                                                                                                     |
+|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ConfigurationChange   | Indicates that the end user has changed their device's configuration or capabilities. Causes the ConfigurationChange data structure defined in Table 21 to be reported.                                                                                                                                                                                                                                                                                                                    | Includes changes of the following elements defined in Table 2:<br>– AMFCapabilityProfile<br>– TVInformation<br>– AudioAmplifierInformation                                                                |
+| UserChange            | Indicates that a TD-AMF has detected a change in permitting end user(s) present at an end-user device. Causes the UserList data structure defined in Table 21 to be reported.                                                                                                                                                                                                                                                                                                              | NOTE – End users who have given permission levels 1-3 per Table 3 are included.                                                                                                                           |
+| UserInfoChange        | Indicates that an end user has changed their end-user information. Causes the UserInfoChange data structure defined in Table 21 to be reported.<br>UserInfoChange has a reporting parameter to be carried by EventParameter1, which indicates if only non-identifying or both non-identifying and identifying end-user info are to be reported. It is mandatory and only used for external permission mode. It has enumerated values PL2 or PL3 corresponding to permission levels 2 or 3. | NOTE – End users who have given permission levels 2-3 per Table 3 are included.                                                                                                                           |
+| AudioLanguageChange   | Indicates that an end user has changed the audio language. Causes the AudioLanguageChange data structure defined in Table 21 to be reported.                                                                                                                                                                                                                                                                                                                                               |                                                                                                                                                                                                           |
+| CaptionLanguageChange | Indicates that an end user has changed the caption language. Causes the CaptionLanguageChange data structure defined in Table 21 to be reported.                                                                                                                                                                                                                                                                                                                                           |                                                                                                                                                                                                           |
+| DisplayStatus         | Indicates a change in the display status of the IPTV Service output of the terminal device. Causes the DisplayStatus element defined in Table 21 to be reported.                                                                                                                                                                                                                                                                                                                           | Reportable when the terminal device audience measurement function (TD-AMF) is able to detect a connected screen's display status e.g., if the TV is connected by interfaces such as HDMI v1.3a or higher. |
+
+#### 6.1.4 Service-common sample types
+
+The sample set identifiers in Table 6 are used to indicate elements to be reported when scheduled time sampling or service start sampling is used.
+
+**Table 6 – Service-common sample set identifiers**
+
+| <b>Sample set identifier</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                          | <b>Description</b>                                                                                                                                                                                                                                                                                                                                                                                                                                     | <b>Scheduled time sampling</b> | <b>Service start sampling</b> |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-------------------------------|
+| UserPresent                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Indicates that the UserPresent data structure, defined in Table 4, is to be reported when sampled.                                                                                                                                                                                                                                                                                                                                                     | Applicable                     | Not applicable                |
+| TDLocation                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Indicates that the geographic location data structure, TDLocation, defined in Table 4, is to be sampled.<br>TDLocation has a reporting distance threshold parameter to be carried by SampleSetQualifier, which indicates the distance in metres between subsequent locations above which a report is generated. It is optional, of type string with a default value "30".                                                                              | Applicable                     | Applicable                    |
+| DeviceInfo                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Indicates that the device information data structure, DeviceInformation, defined in Table 21, is to be reported when sampled.                                                                                                                                                                                                                                                                                                                          | Applicable                     | Applicable                    |
+| UserBioInfo                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Indicates that the end-user biographic information data structure, UserBiographicInformation, defined in Table 3, is to be reported when sampled.                                                                                                                                                                                                                                                                                                      | Applicable                     | Applicable                    |
+| GenericUserInfo                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Indicates that the GenericUserInfo data structure, defined in Table 2, is to be reported when sampled.                                                                                                                                                                                                                                                                                                                                                 | Applicable                     | Applicable                    |
+| EventCount                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Indicates the integer count of events data structure, EventCount, defined in Table 21, is to be reported.<br>The counting period is delimited by either periodicity or "leave-content events" (Note 2). Either will terminate the current event count and start a new event count.<br>The list of events to be counted may be identified by default (Note 1) or explicitly in a parameter list of strings, carried by SampleSetQualifiers in Table 11. | Applicable                     | Not applicable                |
+| UserList                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Indicates that the UserList data structure, defined in Table 21, is to be reported when sampled.                                                                                                                                                                                                                                                                                                                                                       | Applicable                     | Applicable                    |
+| PermitBlockedInfo                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Indicates that the PermitBlockedInfo data structure, defined in Table 4, is to be reported when sampled. Only to be used with internal or hybrid permission modes.                                                                                                                                                                                                                                                                                     | Applicable                     | Applicable                    |
+| NOTE 1 – "In-content" events are any events where the user continues to view the same content after the event. Current "In-content events" include: VideoResize, VideoZoom, VideoObscure, AudioVolume, AudioLanguageChange, CaptionLanguageChange and AudioFocus.<br>NOTE 2 – "Leave-content events" are any events where the user no longer views the same content after the event. Current "Leave-content events" include: LinearChannelStart, LinearChannelStop and DisplayStatus. |                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                |                               |
+
+### 6.2 Data structures for audience measurement
+
+The following data structures include elements and containers defined previously, plus additional elements and containers.
+
+The order of the following data structures is such that later structures build on the earlier structures.
+
+The use of data structures within AM messages is shown in Table 7.
+
+**Table 7 – Messages where data structures are used**
+
+| Message                                                                                               | Error | Acknowledge | Measurement report request | AMF configuration package | Configuration package request | Configuration package request response | Audience measurement report package |
+|-------------------------------------------------------------------------------------------------------|-------|-------------|----------------------------|---------------------------|-------------------------------|----------------------------------------|-------------------------------------|
+| Configuration request message                                                                         |       |             |                            |                           | X                             |                                        |                                     |
+| Configuration request error message                                                                   | X     |             |                            |                           |                               |                                        |                                     |
+| Configuration request response message                                                                |       |             |                            | (X)<br>Note               |                               | X                                      |                                     |
+| Configuration response error message                                                                  | X     |             |                            |                           |                               |                                        |                                     |
+| Configuration message                                                                                 |       |             |                            | X                         |                               |                                        |                                     |
+| Configuration error message                                                                           | X     |             |                            |                           |                               |                                        |                                     |
+| Configuration ack message                                                                             |       | X           |                            |                           |                               |                                        |                                     |
+| Measurement report request message                                                                    |       |             | X                          |                           |                               |                                        |                                     |
+| Measurement report request error message                                                              | X     |             |                            |                           |                               |                                        |                                     |
+| Measurement report message                                                                            |       |             |                            |                           |                               |                                        | X                                   |
+| Measurement report error message                                                                      | X     |             |                            |                           |                               |                                        |                                     |
+| NOTE – The AMF configuration package data structure is inside Configuration package request response. |       |             |                            |                           |                               |                                        |                                     |
+
+#### 6.2.1 Data structure for "error"
+
+The data structure listed in Table 8 is used to report an AM message error.
+
+Figure 11 contains an alternative representation of an error message data structure.
+
+**Table 8 – Data structure for "error message"**
+
+| Element (Note 2) | Description                                                                    | Support/ type                      | Notes or value domain                                                                                                    |
+|------------------|--------------------------------------------------------------------------------|------------------------------------|--------------------------------------------------------------------------------------------------------------------------|
+| Error            | Container which indicates that the following is an AM error message.           | 1                                  |                                                                                                                          |
+| Accepted         | Element of Error<br>Indicates that the errored message was partially accepted. | 0-1<br>xs:Boolean<br>Default: true | NOTE – This element is applicable for non-high-level errors for ConfigPackageError, ReportRequestError, or Report Error. |
+| HighLevelError   | Element of Error<br>Container for the report of a high level error.            | 0-1<br>(Note 1)                    |                                                                                                                          |
+
+**Table 8 – Data structure for "error message"**
+
+| <b>Element<br/>(Note 2)</b> | <b>Description</b>                                                                                                                           | <b>Support/<br/>type</b>        | <b>Notes or value domain</b>                                                                                                                                                             |
+|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| HighLevelError Code         | Element of HighLevelError<br>This element indicates the type of high level error.                                                            | 1<br>xs:string<br>enumeration   | Values: '0' = not well-formed XML message (syntax error), '1' = invalid XML message (not compliant with the schema), '2' = sourced major version is not equal to the receiver's version. |
+| RootElement                 | Element of HighLevelError<br>This element includes the name of the root element of the erroneous message.                                    | 1<br>nonEmpty<br>String         | NOTE – The values include "AMFConfigPackage", "ConfigPackageRequest Response" or the unrecognized element name of a message.                                                             |
+| ConfigPackage Error         | Element of Error<br>Container for information of an errored configuration package message or configuration package request response message. | 0-1<br>(Note 1)                 |                                                                                                                                                                                          |
+| PackageID                   | Element of ConfigPackageError<br>This element contains the identifier of the configuration package with an error.                            | 1                               | NOTE – Defined in Table 16.                                                                                                                                                              |
+| PackageVersion              | Element of ConfigPackageError<br>This element contains the version of the configuration package with an error.                               | 0-1                             | NOTE – Defined in Table 16.                                                                                                                                                              |
+| ConfigPackage ErrorInfo     | Element of ConfigPackageError<br>Container for information about a single error.                                                             | 1-*                             |                                                                                                                                                                                          |
+| ErrorCode                   | Element of ConfigPackageErrorInfo<br>It identifies the error code.                                                                           | 1<br>xs: string<br>enumeration  | Values : '1' = Element not supported, '2' = Element information not available, '3' = element not permitted, '4' = event not supported.                                                   |
+| ErrorElement                | Element of ErrorCode<br>Indicates associated element or attribute.                                                                           | 0 - *<br>xpath                  | Values: path to and including the error element or attribute.                                                                                                                            |
+| ErrorEvent                  | Element of ErrorCode<br>Indicates associated event.                                                                                          | 0-*<br>xs:string<br>enumeration | Values: One of the defined event names.<br>This element is only used for ErrorCode 4.                                                                                                    |
+| ReportRequest Error         | Element of Error<br>Indicates that an error was detected in a measurement report request msg.                                                | 0-1<br>(Note 1)                 |                                                                                                                                                                                          |
+
+**Table 8 – Data structure for "error message"**
+
+| <b>Element<br/>(Note 2)</b> | <b>Description</b>                                                                            | <b>Support/<br/>type</b>       | <b>Notes or value domain</b>                                                                             |
+|-----------------------------|-----------------------------------------------------------------------------------------------|--------------------------------|----------------------------------------------------------------------------------------------------------|
+| ReportRequest<br>ErrorInfo  | Element of ReportRequestError<br>Container for information about a single error.              | 1-*                            |                                                                                                          |
+| ErrorCode                   | Element of ReportRequestErrorInfo<br>It identifies the error code.                            | 1<br>xs: string<br>enumeration | Values: "1"= Requested measurement request ID which was not previously configured.                       |
+| ErrorElement                | Element of ErrorCode<br>Indicates associated element or attribute.                            | 0-*<br>xpath                   | Values: path to and including the error element or attribute.                                            |
+| Measurement<br>RequestID    | Element of ErrorCode<br>Requested measurement request Id which was not previously configured. | 0-*                            | Defined in Table 9.<br>This element is only used for ErrorCode 5.                                        |
+| ReportError                 | Element of Error<br>Indicates that an error was detected in a measurement report msg.         | 0-1<br>(Note 1)                |                                                                                                          |
+| ReportErrorInfo             | Element of ReportError<br>Container for information about a single error.                     | 1-*                            |                                                                                                          |
+| ErrorCode                   | Element of ReportErrorInfo<br>It identifies the error code.                                   | 1<br>xs: string<br>enumeration | Values: "1" = Element or attribute value unknown, "2" = Known but unexpected element or attribute value. |
+| ErrorElement                | Element of ErrorCode<br>Indicates associated element or attribute.                            | 0-*<br>xpath                   | Values: path to and including the error element or attribute.                                            |
+| Measurement<br>RequestID    | Element of ErrorCode<br>Report received containing a unrequested MeasurementRequestID.        | 0-*                            | Defined in Table 9.<br>This element is only used for ErrorCode 6.                                        |
+| ConfigRequest<br>Error      | Element of Error<br>Indicates that an error was detected in a configuration request msg.      | 0-1<br>(Note 1)                |                                                                                                          |
+| ConfigRequest<br>ErrorInfo  | Element of ConfigRequestError<br>Container for information about a single error.              | 1-*                            |                                                                                                          |
+| ErrorCode                   | Element of ConfigRequestErrorInfo<br>It identifies the error code.                            | 1<br>xs:string<br>enumeration  | Values : "1" = Element or attribute value unknown.                                                       |
+| ErrorElement                | Element of ErrorCode<br>Indicates associated element or attribute.                            | 0-*<br>xpath                   | Values: path to and including the error element or attribute.                                            |
+
+**Table 8 – Data structure for "error message"**
+
+NOTE 1 – Only one of these elements is present in a message.
+
+NOTE 2 – Sampleset is an element, an error in sampleset is reported by the appropriate element error code.
+
+```
+Error (1)
+| Accepted (0-1)
+| HighLevelError(0-1) (Note 1)
+| | HighLevelErrorCode (1)
+| | RootElement (1)
+| ConfigPackageError (0-1) (Note 1)
+| | PackageID (1)
+| | PackageVersion (0-1)
+| | ConfigPackageErrorInfo (1-*)
+| | | ErrorCode (1)
+| | | | ErrorElement (0-*)
+| | | | ErrorEvent (0-*)
+| ReportRequestError (0-1) (Note 1)
+| | ReportRequestErrorInfo (1-*)
+| | ErrorCode (1)
+| | | ErrorElement (0-*)
+| | | MeasurementRequestID (0-*)
+| ReportError (0-1) (Note 1)
+| | ReportErrorInfo (1-*)
+| | ErrorCode (1)
+| | | ErrorElement (0-*)
+| | | MeasurementRequestID (0-*)
+| ConfigRequestError (0-1) (Note 1)
+| | ConfigRequestErrorInfo (1-*)
+| | ErrorCode (1)
+| | | ErrorElement (0-*)
+```
+
+**Figure 11 – Alternative representation of Error data structure**
+
+#### 6.2.2 Data structure for "measurement request"
+
+The data structure of measurement request consists of four logical parts; the first part includes the metadata elements to specify which services are to be measured, as shown in Table 9.
+
+Figure 12 contains an alternative representation of Table 9 data structure.
+
+**Table 9 – First part of metadata elements in "measurement request"**
+
+| Element               | Description                                                                                                                                                      | Support/<br>type         | Notes or value domain                                                                                                                                                                                          |
+|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Measurement Request   | Container                                                                                                                                                        |                          |                                                                                                                                                                                                                |
+| Measurement RequestID | Element of MeasurementRequest<br>Identification of the measurement request.                                                                                      | 1<br>xs:positive Integer | Value: AM service provider unique.<br>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 measurement request. |
+| LinearTV Qualifier    | Element of MeasurementRequest<br>This element identifies that the LinearTV service is to be measured and contains the qualifiers of the services to be measured. | 0-1                      | NOTE – Defined in [ITU-T H.741.3].                                                                                                                                                                             |
+
+```
+
+MeasurementRequest
+| MeasurementRequestID (1)
+| LinearTVQualifier (0-1)
+
+```
+
+**Figure 12 – Alternative representation of first part of MeasurementRequest data structure**
+
+Table 10 specifies elements which provide the ability to filter measurements across services based upon content class.
+
+Figure 13 contains an alternative representation of Table 10 data structure.
+
+**Table 10 – Data structure for AMF "content filtering"**
+
+| Element                    | Description                                                                  | Support/type          | Notes or value domain                                                                              |
+|----------------------------|------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------------------------------------------------|
+| AllContentClass ExceptList | Element of MeasurementRequest<br>List of content classes not to be measured. | 0-1                   | NOTE – If AllContentClass ExceptList is not present then measurements are not filtered by content. |
+| ContentClass Domain        | Element of AllContentClassExceptList<br>Content class domain identifier.     | 1-*<br>nonEmptyString | NOTE – Value is the name of a standard or organisation that defines content classes.               |
+| ContentClassID             | Element of ContentClassDomain<br>Content class identifier.                   | 1-*<br>nonEmptyString | NOTE – Value is the name of a content class.                                                       |
+
+```
+
+AllContentClassExceptList (0-1)
+| ContentClassDomain (1-*)
+| | ContentClassID (1-*)
+
+```
+
+**Figure 13 – Alternative representation of content filtering data structure**
+
+Table 11 describes the next part of the metadata elements for audience measurement request which is about "Measurement schedule".
+
+This measurement schedule section allows the requesting of a service to be measured in the same way at different periods of the day. It allows definition of several measurement periods (MeasurementPeriod) and the method of how a measurement report is to be triggered, either periodically and/or on specific events.
+
+When events and samples cover the same elements, an event which occurs between two sample times delays the next sample time until the subsequent scheduled sample time.
+
+Figure 14 contains an alternative representation of Table 11 data structure.
+
+**Table 11 – Measurement schedule metadata for "measurement request"**
+
+| Element              | Description                                                                      | Support/<br>type                           | Notes or Value domain                                                                                                                                                             |
+|----------------------|----------------------------------------------------------------------------------|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Measurement Schedule | Element of MeasurementRequest<br>Container for time period for measurement.      | 1-*                                        |                                                                                                                                                                                   |
+| Measurement Period   | Element of MeasurementSchedule<br>Container for a measurement period.            | 0-*                                        |                                                                                                                                                                                   |
+| DayOfTheWeek         | Element of MeasurementPeriod<br>Day of the week at which measurement starts.     | 0-*<br>xs:nonNegativeInteger<br>Default: 0 | Value list: 0 = "everyday",<br>1 = "Monday", 2 = "Tuesday",<br>3 = "Wednesday",<br>4 = "Thursday", 5 = "Friday",<br>6 = "Saturday", 7 = "Sunday",<br>8 = "weekday", 9 = "weekend" |
+| StartTime            | Element of MeasurementPeriod<br>Time of the day at which the measurement starts. | 0-*<br>xs:time                             | If omitted refer to DefaultMeasurementStartTime in Table 13.                                                                                                                      |
+| EndTime              | Element of MeasurementPeriod<br>Time of the day at which the measurement stops.  | 0-*<br>xs:time<br>Default 23:59:59.99      | NOTE – Default is at end of day. Omitting both StartTime and EndTime results in measurement for complete day.                                                                     |
+| EventTrigger         | Element of MeasurementSchedule<br>Measurement trigger of event type.             | 0-*                                        |                                                                                                                                                                                   |
+| Event                | Element of EventTrigger<br>Events which trigger a measurement from the TD-AMF.   | 0-*<br>nonEmpty String                     | See Table 5 for service-common events and [ITU-T H.741.3] for service dependent events including default events.                                                                  |
+| EventParameter1      | Attribute of Event.                                                              | 0-1<br>xs:string                           | Some events require a parameter which is carried here.                                                                                                                            |
+
+**Table 11 – Measurement schedule metadata for "measurement request"**
+
+| Element               | Description                                                                                                                          | Support/<br>type                                             | Notes or Value domain                                                                                                                                                |
+|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Priority              | Element of EventTrigger<br>Priority to consider keeping an event-driven measurement report when storage is congested.                | 0-1<br>xs:nonNegativeInteger<br>Default: 0                   | Value: 0-10<br>NOTE – Higher integer value indicates higher priority. 0 value indicates not to store the event data.<br>See Note 1.                                  |
+| TimeTrigger           | Element of MeasurementSchedule<br>Measurement trigger of time type.                                                                  | 0-1                                                          |                                                                                                                                                                      |
+| SampleSet             | Element of TimeTrigger<br>Defined sets of elements to be sampled.                                                                    | 0-*                                                          | NOTE – No default service-common sample set identifiers have yet been specified.                                                                                     |
+| SampleSet Identifier  | Attribute of SampleSet<br>Defined sets of elements to be sampled.<br>A set may include just one element.                             | 1<br>xs:string enumeration                                   | The values of service-common sample set identifiers are defined in Table 6.<br>The values of service-specific sample set identifiers are defined in [ITU-T H.741.3]. |
+| SampleSet Qualifier   | Element of SampleSet                                                                                                                 | 0-*<br>xs:string enumeration                                 | NOTE – Parameters relating to the sample set identifier attribute.                                                                                                   |
+| Periodicity           | Element of TimeTrigger<br>Periodicity at which a measurement is to be made (expressed in seconds).                                   | 1<br>xs:positive Integer                                     |                                                                                                                                                                      |
+| Priority              | Element of TimeTrigger<br>Priority to consider keeping a time-driven measurement report when storage is congested.                   | 0-1<br>xs:nonNegativeInteger<br>Default: 0                   | Value: 0-10<br>NOTE – Higher integer value indicates higher priority. 0 value indicates not to store the sampled data.<br>See Note 1.                                |
+| NothingNew ReportMode | Element of TimeTrigger<br>This element states what to do in case that there is no change since the last measurement snapshot.        | 0-1<br>xs:nonNegativeInteger<br>Default: 0                   | 0: ignore AM sample.<br>1: create empty AM sample (see Note 2).<br>2: create a complete AM sample.                                                                   |
+| ServiceStart Trigger  | Element of MeasurementSchedule<br>Measurement trigger of time type.                                                                  | 0-1                                                          |                                                                                                                                                                      |
+| Interval              | Element of ServiceStartTrigger<br>It indicates in a number of days when the Service Start event is to generate a measurement report. | 0-1<br>xs:positive Integer<br>Default: at each service start | Value: N number of days<br>NOTE – A sample occurs at the first service start every N days.                                                                           |
+
+**Table 11 – Measurement schedule metadata for "measurement request"**
+
+| Element              | Description                                                                                                                | Support/<br>type                           | Notes or Value domain                                                                                                                                                |
+|----------------------|----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| SampleSet            | Element of ServiceStartTrigger<br>Defined sets of elements to be sampled.                                                  | 0-*                                        | NOTE – No default service-common sample set identifiers have yet been specified.                                                                                     |
+| SampleSet Identifier | Attribute of SampleSet<br>Defined sets of elements to be sampled.<br>A set may include just one element.                   | 1<br>xs:string<br>enumeration              | The values of service-common sample set identifiers are defined in Table 6.<br>The values of service-specific sample set identifiers are defined in [ITU-T H.741.3]. |
+| SampleSet Qualifier  | Element of SampleSet                                                                                                       | 0-*<br>xs:string<br>enumeration            | NOTE – Parameters relating to the sample set identifier attribute.                                                                                                   |
+| Priority             | Element of ServiceStartTrigger<br>Priority to consider keeping a time-driven measurement report when storage is congested. | 0-1<br>xs:nonNegativeInteger<br>Default: 0 | Value: 0-10<br>NOTE – Higher integer value indicates higher priority. 0 value indicates not to store the service start data.<br>See Note 1.                          |
+
+NOTE 1 – The priorities of EventTrigger, TimeTrigger and ServiceStartTrigger use the same scale.
+
+NOTE 2 – An empty report includes only the mandatory elements of the measurement report.
+
+```
+
+MeasurementSchedule (1-*)
+| MeasurementPeriod (0-*)
+| | DayOfTheWeek (0-*)
+| | StartTime (0-*)
+| | EndTime (0-*)
+| EventTrigger (0-*)
+| | Event (0-*) [EventParameter1 (0-1)]
+| | Priority (0-1)
+| TimeTrigger (0-1)
+| | SampleSet (0-*) [SampleSetIdentifier (1)]
+| | | SampleSetQualifier (0-*)
+| | Periodicity (1)
+| | Priority (0-1)
+| | NothingNewReportMode (0-1)
+| ServiceStartTrigger (0-1)
+| | Interval (0-1)
+| | SampleSet (0-*) [SampleSetIdentifier (1) ]
+| | | SampleSetQualifier (0-*)
+| | Priority (0-1)
+
+```
+
+**Figure 14 – Alternative representation of MeasurementSchedule data structure**
+
+Table 12 describes the next part of the metadata elements for audience measurement request which is about "Measurement delivery metadata".
+
+This measurement delivery schedule section allows aggregation functions to specify how measurement reports are delivered to the aggregation function.
+
+Figure 15 contains an alternative representation of the measurement delivery schedule data structure.
+
+**Table 12 – Measurement delivery metadata for "measurement request"**
+
+| Element                             | Description                                                                                                                                                     | Support/<br>type              | Notes or value domain                                                                                                                                                                                                                                                                                                                                              |
+|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Measurement<br>Delivery<br>Schedule | Element of MeasurementRequest<br>Description of the mechanism to be used to decide on how to make the measurement report available to the aggregation function. | 0-1<br>Note 1                 |                                                                                                                                                                                                                                                                                                                                                                    |
+| DeliveryAddress                     | Element of MeasurementDeliverySchedule<br>URL to be used to send measurement reports from the TD-AMF.                                                           | 0-*<br>URL                    | NOTE – A delivery address may already be specified in the AM aggregation function discovery process or in the measurement request set structure.<br>There is no specific order or preference in the address list if there are different URL types specified. If multiple addresses are of the same URL type, then the preference is given by the order.            |
+| Retransmit<br>Number                | Element of MeasurementDeliverySchedule<br>Number of transmission retries when a measurement report is not acknowledged by the aggregation function.             | 0-1<br>xs:positive<br>Integer | NOTES<br>– A retransmit number may already be specified in the measurement request set structure.<br>– The maximum number of transmission attempts to deliver a measurement report is "RetransmitNumber" + 1.                                                                                                                                                      |
+| Storage<br>Congestion<br>Policy     | Element of MeasurementDeliverySchedule<br>This element indicates what the TD-AMF does in case of storage congestion for this measurement request.               | 0-1                           | 0 = immediately push the oldest measurement reports to free up storage sufficiently, and if push fails, apply the following.<br>1 = drop enough of the lowest priority events and/or sample values to free space for new higher priority events and/or sample values. Age of lowest priority events and/or sample values is to be used as a tie-breaking criteria. |
+
+**Table 12 – Measurement delivery metadata for "measurement request"**
+
+| Element                       | Description                                                                                                                                                           | Support/<br>type             | Notes or value domain                                                                                                                                                                                                                                                           |
+|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ImmediatePush                 | Element of MeasurementDeliverySchedule<br>This element indicates that the measurement delivery takes place immediately with possible grouping of measurement reports. | 0-1<br>See Note 2            |                                                                                                                                                                                                                                                                                 |
+| MeasurementReportNumberByPush | Element of "ImmediatePush"<br>This element indicates the number of measurement reports which are to be grouped together before a push delivery is attempted.          | 0-1<br>xs:positiveInteger    | 1 = each measurement report is pushed as soon as produced.                                                                                                                                                                                                                      |
+| MaxTimeBetweenDelivery        | Element of "ImmediatePush"<br>This element indicates the maximum delay in seconds between two measurement report delivery.                                            | 0-1<br>xs:nonNegativeInteger | 0 = infinite<br>NOTES:<br>– This allows sending the last measurement reports without waiting for the number of stored measurement reports to reach the number required for measurement groupings.<br>– This makes sense only if MeasurementReportNumberByPush is bigger than 1. |
+| DelayedDelivery               | Element of MeasurementDeliverySchedule<br>This element indicates that the measurement delivery is to take place during specific delivery windows.                     | 0-1<br>See Note 2            |                                                                                                                                                                                                                                                                                 |
+| DeliveryWindow                | Element of "DelayedDelivery"<br>This element is a container for the start and end time of a measurement delivery window.                                              | 0-*                          | NOTE – Several delivery windows are possible.                                                                                                                                                                                                                                   |
+| StartDeliveryWindowTime       | Element of "DeliveryWindow"<br>Time of the day at which the stored audience measurement reports could start to be delivered.                                          | 0-1<br>xs:time               |                                                                                                                                                                                                                                                                                 |
+| EndDeliveryWindowTime         | Element of "DeliveryWindow"<br>Last time of the day at which the audience measurement report could be delivered.                                                      | 0-1<br>xs:time               |                                                                                                                                                                                                                                                                                 |
+| Pull                          | Element of MeasurementDeliverySchedule<br>This element indicates that the measurement reports are to be delivered only on request from the aggregation functions.     | 0-1<br>See Note 2            |                                                                                                                                                                                                                                                                                 |
+
+**Table 12 – Measurement delivery metadata for "measurement request"**
+
+| Element                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | Description                                                                                                                                                                                        | Support/<br>type  | Notes or value domain                            |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------|
+| DelayedPush<br>AndPull                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Element of<br>MeasurementDeliverySchedule<br>This element indicates that<br>measurement reports are to be<br>delivered on request from the<br>aggregation functions or during<br>delivery windows. | 0-1<br>See Note 2 |                                                  |
+| DeliveryWindow                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Element of "DelayedPushAndPull"<br>This element is a container for the<br>start and end time of a<br>measurement delivery window.                                                                  | 0-*               | NOTE – Several delivery<br>windows are possible. |
+| StartDelivery<br>WindowTime                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Element of "DeliveryWindow"<br>Time of the day at which the stored<br>audience measurement reports<br>could start to be delivered.                                                                 | 0-1<br>xs:time    |                                                  |
+| EndDelivery<br>WindowTime                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Element of "DeliveryWindow"<br>Last time of the day at which the<br>audience measurement report<br>could be delivered.                                                                             | 0-1<br>xs:time    |                                                  |
+| <p>NOTE 1 – If MeasurementDeliverySchedule is not present then the default is immediatePush mode. The associated elements (delivery address, retransmit number and storage congestion policy) are specified in the AM aggregation function discovery process, or as configured in the measurement request set, or by default.</p> <p>NOTE 2 – If MeasurementDeliverySchedule is present, one of either immediatePush, delayedPush, pull, or delayedPushAndPull may be present. If none of them is present, then the default is immediatePush mode.</p> |                                                                                                                                                                                                    |                   |                                                  |
+
+```
+
+MeasurementDeliverySchedule (0-1)
+| DeliveryAddress (0-*)
+| RetransmitNumber (0-1)
+| StorageCongestionPolicy (0-1)
+| ImmediatePush (0-1)
+| | MeasurementReportNumberByPush (0-1)
+| | MaxTimeBetweenDelivery (0-1)
+| DelayedDelivery (0-1)
+| | DeliveryWindow (0-*)
+| | | StartDeliveryWindowTime (0-1)
+| | | EndDeliveryWindowTime (0-1)
+| Pull (0-1)
+| DelayedPushAndPull (0-1)
+| | DeliveryWindow (0-*)
+| | | StartDeliveryWindowTime (0-*)
+| | | EndDeliveryWindowTime (0-*)
+
+```
+
+**Figure 15 – Alternative representation of MeasurementDeliverySchedule data structure**
+
+##### 6.2.2.1 "Delayed push" measurement reporting policy
+
+When the report delivery period starts for a measurement request or a set of measurement requests, the TD-AMF selects a random delivery time for reporting between the delivery window start time and end time.
+
+When the randomly selected delivery time is reached, the TD-AMF pushes all stored measurement reports corresponding to this or these measurement requests in time order to the aggregation function. Following completion of delivery, the TD-AMF stops pushing further measurement reports until the next report delivery window. New measurement reports for this or these measurement requests are stored again after the last stored measurement report has been delivered.
+
+#### 6.2.3 Data structure for "measurement request set"
+
+As some elements may be repeated in a number of measurement requests with the same value, a measurement request set is defined to provide an optimization mechanism to include default values for elements which have the same value in a number of measurement requests. Multiple measurement request sets may be present in a configuration package.
+
+There are four possible levels to set values:
+
+- Highest priority level – configured in an individual measurement request
+- Second level – default in a measurement request
+- Third level – configured in a measurement request set
+- Fourth level – default in a measurement request set
+
+The values configured in each measurement request supersede those configured here.
+
+Figure 16 contains an alternative representation of the metadata elements of Table 13 in a measurement request set.
+
+**Table 13 – Metadata elements in "measurement request set"**
+
+| Element                                    | Description                                                                                                                                                                              | Support/<br>type               | Notes or value domain                                                                                                                                                                                                                          |
+|--------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Measurement RequestSet                     | This element is a container for a general default section containing elements with identical values for a set of measurement requests and the corresponding set of measurement requests. | 1-*                            | NOTE – Extended in [ITU-T H.741.3].                                                                                                                                                                                                            |
+| DefaultAll ContentClass ExceptList         | Element of MeasurementRequestSet<br>Default list of content classes not to be measured.                                                                                                  | 0-1                            | NOTE – Refer to "AllContentClassExceptList" element in Table 10.                                                                                                                                                                               |
+| Default Measurement Period                 | Element of MeasurementRequestSet<br>Default Measurement Period.                                                                                                                          | 0-*                            | Defined as MeasurementPeriod in Table 11.                                                                                                                                                                                                      |
+| DefaultDayOf TheWeek                       | Element of MeasurementRequestSet<br>Default DayOfTheWeek for measurement.                                                                                                                | 0-*                            | NOTE – For encoding, refer to "DayOfTheWeek" element in Table 11.                                                                                                                                                                              |
+| Default Measurement StartTime              | Element of MeasurementRequestSet<br>Default start time for measurement.                                                                                                                  | 0-1<br>Default:<br>00:00:00.00 | NOTES<br>– Default is at 0000 hours (12 am) at start of day. For encoding, refer to "StartTime" element in Table 11.<br>– Omitting both Default Measurement StartTime and Default Measurement EndTime results in measurement for complete day. |
+| Default Measurement EndTime                | Element of MeasurementRequestSet<br>Default end time for measurement.                                                                                                                    | 0-1                            | NOTE – For encoding, refer to "EndTime" element in Table 11.                                                                                                                                                                                   |
+| DefaultTime Driven Measurement Periodicity | Element of MeasurementRequestSet<br>Default periodicity for time driven audience measurement.                                                                                            | 0-1                            | NOTE – For encoding, refer to "Periodicity" element in "TimeTrigger" element of Table 11.                                                                                                                                                      |
+| DefaultNothing NewReportMode               | Element of MeasurementRequestSet<br>Default behaviour when there is no change since the last measurement snapshot.                                                                       | 0-1                            | NOTE – For encoding, refer to "NothingNewReportMode" element in "TimeTrigger" element of Table 11.                                                                                                                                             |
+| DefaultInterval                            | Element of MeasurementRequestSet<br>Default Interval                                                                                                                                     | 0-1                            | NOTE – For encoding, refer to "Interval" element in Table 11.                                                                                                                                                                                  |
+
+**Table 13 – Metadata elements in "measurement request set"**
+
+| Element                                 | Description                                                                                                                                                                          | Support/<br>type            | Notes or value domain                                                                                                                                                                                                              |
+|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| DefaultDelivery Address                 | Element of MeasurementRequestSet<br>Default URL to be used to send measurement report packages from the TD-AMF.                                                                      | 0-*                         | NOTE – For encoding, refer to "DeliveryAddress" element in MeasurementDeliverySchedule element of Table 12.                                                                                                                        |
+| Default Retransmit Number               | Element of MeasurementRequestSet<br>Default number of transmission retries when a measurement report package is not acknowledged at the transport layer by the aggregation function. | 0-1                         | NOTE – For encoding, refer to "RetransmitNumber" element in MeasurementDeliverySchedule element of Table 12.                                                                                                                       |
+| DefaultStorage Congestion Policy        | Element of MeasurementRequestSet<br>Default storage congestion policy.                                                                                                               | 0-1<br>Default: 1           | NOTE – For encoding, refer to the "StorageCongestionPolicy" element in Table 12.                                                                                                                                                   |
+| Default Measurement ReportNumber ByPush | Element of MeasurementRequestSet<br>Default MeasurementReportNumberBy Push.                                                                                                          | 0-1<br>Default: 1           | NOTE – For encoding, refer to "MeasurementReportNumberBy Push" element in Table 12.                                                                                                                                                |
+| DefaultMaxTime Between Delivery         | Element of MeasurementRequestSet<br>Default MaxTimeBetweenDelivery                                                                                                                   | 0-1<br>Default: 0           | NOTE – For encoding, refer to "MaxTimeBetweenDelivery" element in Table 12.                                                                                                                                                        |
+| DefaultDelivery Window                  | Element of MeasurementRequestSet<br>Element to group default start and end times of delivery window                                                                                  | 0-*                         | As defined by DeliveryWindow of Table 12.                                                                                                                                                                                          |
+| DefaultStart DeliveryWindow Time        | Element of MeasurementRequestSet<br>Default StartDeliveryWindowTime                                                                                                                  | 0-1<br>Default: 00:00:00.00 | NOTES<br>– For encoding, refer to "StartDeliveryWindowTime" element in Table 12.<br>– Default is start of day. Omitting both StartDelivery WindowTime and End DeliveryWindowTime results in permitting reporting for complete day. |
+| DefaultEnd DeliveryWindow Time          | Element of MeasurementRequestSet<br>Default EndDeliveryWindowTime                                                                                                                    | 0-1<br>Default: 23:59:59.99 | NOTES<br>– For encoding, refer to "EndDeliveryWindowTime" element in Table 12.<br>– Default is at end of day. Omitting both StartDelivery WindowTime and End DeliveryWindowTime results in permitting reporting for complete day.  |
+
+**Table 13 – Metadata elements in "measurement request set"**
+
+| Element                                      | Description                                                                                               | Support/<br>type | Notes or value domain                                                                |
+|----------------------------------------------|-----------------------------------------------------------------------------------------------------------|------------------|--------------------------------------------------------------------------------------|
+| DefaultService<br>StartPermit<br>BlockedInfo | Element of<br>MeasurementRequestSet<br>Default sampleset identifier for<br>service start trigger sampling | 0-1              | NOTE – Refer to<br>PermitBlockedInfo element in<br>Table 6.                          |
+| DefaultTime<br>TriggerPermit<br>BlockedInfo  | Element of<br>MeasurementRequestSet<br>Default sampleset identifier for<br>time trigger sampling          | 0-1              | NOTE – Refer to<br>PermitBlockedInfo element in<br>Table 6.                          |
+| Measurement<br>Request                       | Element of<br>MeasurementRequestSet<br>Individual measurement requests                                    | 1-*              | NOTE – For encoding, refer to<br>"measurement request" data<br>structure of Table 9. |
+
+```
+
+MeasurementRequestSet (1-*)
+| DefaultMeasurementPeriod (0-*)
+| DefaultAllContentClassExceptList (0-1)
+| DefaultDayOfWeek (0-*)
+| DefaultMeasurementStartTime (0-1)
+| DefaultMeasurementEndTime (0-1)
+| DefaultTimeDrivenMeasurementPeriodicity (0-1)
+| DefaultNothingNewReportMode (0-1)
+| DefaultInterval (0-1)
+| DefaultDeliveryAddress (0-*)
+| DefaultRetransmitNumber (0-1)
+| DefaultStorageCongestionPolicy (0-1)
+| DefaultMeasurementReportNumberByPush (0-1)
+| DefaultMaxTimeBetweenDelivery (0-1)
+| DefaultDeliveryWindow (0-*)
+| DefaultStartDeliveryWindowTime (0-1)
+| DefaultEndDeliveryWindowTime (0-1)
+| DefaultServiceStartPermitBlockedInfo (0-1)
+| DefaultTimeTriggerPermitBlockedInfo (0-1)
+| MeasurementRequest (1-*)
+
+```
+
+**Figure 16 – Alternative representation of MeasurementRequestSet data structure**
+
+#### 6.2.4 Data structure for "measurement request set filter"
+
+The following filters support different sets of measurement requests in a single AMF configuration package for different TD-AMFs.
+
+**Table 14 – Metadata elements in "measurement request set filter request"**
+
+| Element                     | Description                                                                                                             | Support/<br>type | Notes or value domain                                                          |
+|-----------------------------|-------------------------------------------------------------------------------------------------------------------------|------------------|--------------------------------------------------------------------------------|
+| MeasurementRequestSetFilter | This a container for filters which conditionally indicate measurement requests to be processed.                         | 0-*              |                                                                                |
+| UserInfoTarget              | Element of MeasurementRequestSetFilter<br>Container for elements specifying user info to be used for targeting TD-AMFs. | 1-*              | Defined in [ITU-T H.741.4].                                                    |
+| MeasurementRequestID        | Element of MeasurementRequestSetFilter<br>Individual measurement requests conditionally processed by filters.           | 1-*              | NOTE – For encoding, refer to "measurement request" data structure of Table 9. |
+
+#### 6.2.5 Data structure for "measurement report request"
+
+**Table 15 – Metadata elements in "measurement report request"**
+
+| Element                  | Description                                                                       | Support/<br>type           | Notes or value domain                                                                                                                                      |
+|--------------------------|-----------------------------------------------------------------------------------|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| MeasurementReportRequest | Container for a measurement report request.                                       | 1                          | NOTE – A measurement report request with no MeasurementRequestIDs indicates that a TD-AMF is to respond with available data from all measurement requests. |
+| MeasurementRequestID     | Element of MeasurementReportRequest<br>Identification of the measurement request. | 0-*<br>xs:positive Integer | NOTE – indicates that a TD-AMF is to respond with available data from this specific measurement request.                                                   |
+
+#### 6.2.6 Data structure for "AMF configuration package"
+
+The AMF configuration package in Table 16 is a set of elements provided by the aggregation function to configure the operation of the audience measurement function.
+
+Figure 17 contains an alternative representation of the AMF configuration package data structure.
+
+**Table 16 – Data structure of the "AMF configuration package"**
+
+| Element          | Description                                                                     | Support/<br>type         | Notes or value domain              |
+|------------------|---------------------------------------------------------------------------------|--------------------------|------------------------------------|
+| AMFConfigPackage | Container for all the elements of the AMF configuration package.                | 1                        |                                    |
+| PackageID        | Element of AMFConfigPackage<br>Identification of the AMF configuration package. | 1<br>xs:positive Integer | Value: AM service provider unique. |
+
+**Table 16 – Data structure of the "AMF configuration package"**
+
+| Element                     | Description                                                                                                                                                | Support/<br>type                              | Notes or value domain                                                                                                                       |
+|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|
+| PackageVersion              | Attribute of PackageID<br>This attribute contains the version of the configuration package                                                                 | 0-1<br>xs:positiveInteger                     |                                                                                                                                             |
+| EffectivityDateAndTime      | Element of AMFConfigPackage<br>This element identifies the date and time at which this AMF configuration package is to be applied to the TD-AMF operation. | 0-1<br>xs:dateTime<br>Default:<br>immediately |                                                                                                                                             |
+| UserPermitInfo              | Element of AMFConfigPackage<br>This element is a container for an end-user permit with end-user identifier and last update date.                           | 0-*                                           | NOTE – This element is only for hybrid permission mode and is mandatory for this mode. It is not to be present in internal permission mode. |
+| LastUpdateDateAndTime       | Element of UserPermitInfo<br>This element indicates the date and time of the creation or last update of the end-user permit.                               | 0-1<br>xs:dateTime                            |                                                                                                                                             |
+| UserPermit                  | Element of UserPermitInfo<br>This element includes all end-user permissions for the audience measurement of the IPTV service provider.                     | 1                                             | NOTE – For encoding, refer to Table 20.                                                                                                     |
+| MeasurementRequestSet       | Element of AMFConfigPackage<br>Container for an individual measurement request set.                                                                        | 1-*                                           | NOTE – For encoding, refer to Table 13.                                                                                                     |
+| MeasurementRequestSetFilter | Element of AMFConfigPackage<br>This a container for filters which conditionally indicate measurement requests to be processed.                             | 0-*                                           | NOTE – For encoding, refer to Table 14.                                                                                                     |
+
+```
+
+AMFConfigPackage (1)
+  | PackageID (1) [ PackageVersion (0-1)]
+  | EffectivityDateAndTime (0-1)
+  | UserPermitInfo (0-*)
+  | | LastUpdateDateAndTime (0-1)
+  | | UserPermit (1)
+  | MeasurementRequestSet (1-*)
+  | MeasurementRequestSetFilter (0-*)
+
+```
+
+**Figure 17 – Alternative representation of AMFConfigPackage data structure**
+
+#### 6.2.7 Data structure for "acknowledge"
+
+The data structure in Table 17 is used to report an AM message acknowledge.
+
+**Table 17 – Data structure for "acknowledge message"**
+
+| Element | Description                                                                        | Support/<br>type | Notes or value domain |
+|---------|------------------------------------------------------------------------------------|------------------|-----------------------|
+| Ack     | Container which indicates that the following is an AM message acknowledge message. | 1                |                       |
+
+#### **6.2.8 Data structure for "configuration package request"**
+
+The configuration package request may be used by audience measurement function to ask for an AMF configuration package or to check if the current or future configuration package at the TD-AMF is still valid.
+
+The data structure of the AMF configuration package request is specified in Table 18.
+
+Figure 18 contains an alternative representation of the AMF configuration package request data structure.
+
+**Table 18 – Data structure of "configuration package request"**
+
+| Element                    | Description                                                                                                                                                          | Support/<br>type                                         | Notes or value domain                                                                                                                                                  |
+|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ConfigPackage Request      | This element is a container for the configuration package request.                                                                                                   | 1                                                        |                                                                                                                                                                        |
+| Terminal DeviceID          | Element of ConfigPackageRequest<br>This element uniquely identifies the end user's terminal device based on the device's MAC address.                                | 1<br>xs:hexBinary<br>length =<br>16 octets<br>(128 bits) |                                                                                                                                                                        |
+| TerminalDevice Type        | Element of ConfigPackageRequest<br>This element identifies a specific type of IPTV terminal device.                                                                  | 1                                                        | Defined in Table 20.                                                                                                                                                   |
+| ServiceProvider Identifier | Element of ConfigPackageRequest<br>This element contains the identifier of the IPTV service provider for which the Audience Measurement is proposed by the end user. | 0-1                                                      | Defined in Table 4.                                                                                                                                                    |
+| SubscriberID               | Element of ConfigPackageRequest<br>This element contains the identification of the subscriber to the services of the above service provider.                         | 1                                                        | Defined in Table 4.                                                                                                                                                    |
+| UserPermitInfo             | Element of ConfigPackageRequest<br>This element is a container for an end-user permit with end-user identifier and last update date.                                 | 0-*                                                      | NOTE – This element is only for hybrid permission mode and is mandatory for this mode. It is not to be present in internal permission mode.<br>As defined in Table 16. |
+| AMFCapability Profile      | Element of ConfigPackageRequest<br>This element indicates the AM profile supported by the IPTV terminal device.                                                      | 0-1                                                      | NOTE – Defined in Table 2.                                                                                                                                             |
+
+**Table 18 – Data structure of "configuration package request"**
+
+| Element             | Description                                                                                                                               | Support/<br>type | Notes or value domain       |
+|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------|------------------|-----------------------------|
+| Current Measurement | Element of ConfigPackageRequest<br>Container for all the elements related to the current measurement.                                     | 0-1              |                             |
+| PackageID           | Element of CurrentMeasurement<br>This element contains the identifier of the configuration package currently in use in the TD-AMF.        | 1                | NOTE – Defined in Table 16. |
+| PackageVersion      | Attribute of PackageID<br>This attribute contains the version of the configuration package.                                               | 0-1              | NOTE – Defined in Table 16. |
+| Future Measurement  | Element of ConfigPackageRequest<br>Container for all the elements related to the future measurement.                                      | 0-1              |                             |
+| PackageID           | Element of FutureMeasurement<br>This element contains the identifier of the configuration package to be used in the future by the TD-AMF. | 1                | NOTE – Defined in Table 16. |
+| PackageVersion      | Attribute of PackageID<br>This attribute contains the version of the configuration package to be used in the future by the TD-AMF.        | 0-1              | NOTE – Defined in Table 16. |
+
+```
+
+ConfigPackageRequest (1)
+| TerminalDeviceID (1)
+| TerminalDeviceType (1)
+| ServiceProviderIdentifier (0-1)
+| SubscriberID (1)
+| UserPermitInfo (0-*)
+| AMFCapabilityProfile (0-1)
+| CurrentMeasurement (1)
+| | PackageID (1) [ PackageVersion (0-1) ]
+| FutureMeasurement (0-1)
+| | PackageID (1) [ PackageVersion (0-1) ]
+
+```
+
+**Figure 18 – Alternative representation of ConfigPackageRequest data structure**
+
+#### 6.2.9 Data structure for "configuration package request response"
+
+The response from the aggregation function to the configuration package request is defined in Table 19.
+
+Figure 19 contains an alternative representation of the configuration package request response data structure.
+
+**Table 19 – Data structure of the "configuration package request response"**
+
+| Element                          | Description                                                                                                                                                                     | Support/type                                 | Notes or value domain                                                                                                                                                                                                                                                                                                                 |
+|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ConfigPackage Request Response   | Container for all the elements of the response to the configuration package request.                                                                                            | 1                                            |                                                                                                                                                                                                                                                                                                                                       |
+| Configuration PackageCheck Delay | Element of ConfigPackageRequestResponse<br>Identifies the delay (days) from activation of the first configuration package until availability of a new one is to be checked for. | 0-1<br>xs:positive Integer                   | Used for configuration pull mode and configuration hybrid mode, Not used for push (only) mode.                                                                                                                                                                                                                                        |
+| Immediate Measurement Directive  | Element of ConfigPackageRequestResponse<br>Container for all the elements of the response about audience measurement to be made now.                                            | 0-1                                          |                                                                                                                                                                                                                                                                                                                                       |
+| Code                             | Element of ImmediateMeasurementDirective<br>This element includes the response for immediate measurement.                                                                       | 0-1<br>xs:string enumeration<br>Default: "1" | "1" = No AM required: means no audience measurement is required now by the aggregation function.<br>"2" = No Conf Package Change: no change to the TD-AMF configuration package currently used in the TD-AMF.<br>"3" = Conf Package Present: configuration package included in this response is to be taken into account from now on. |
+| AMFConfig Package                | Element of ImmediateMeasurementDirective<br>This element is a container for a configuration package.<br>This element is present only if Response = '3' (Conf Package Present).  | 0-1                                          | NOTE – Defined in Table 16.                                                                                                                                                                                                                                                                                                           |
+| Future Measurement Directive     | Element of ConfigPackageRequestResponse<br>Container for all the elements of the response about audience measurement to be made in the future.                                  | 0-1                                          |                                                                                                                                                                                                                                                                                                                                       |
+
+**Table 19 – Data structure of the "configuration package request response"**
+
+| Element           | Description                                                                                                                                                                 | Support/type                                    | Notes or value domain                                                                                                                                                                                                                                                                                                                                                                   |
+|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Code              | Element of FutureMeasurementDirective<br>This element includes the response for future measurements.                                                                        | 0-1<br>xs:string<br>enumeration<br>Default: "1" | "1" = No Future Conf Package: means that there is no configuration package with a future effectivity date and time.<br>"2" = No Conf Package Change: no change to the future TD-AMF configuration package(s) already available in the TD-AMF.<br>"3" = Conf Package Present: means that this response includes a configuration package to be taken into account for future measurement. |
+| AMFConfig Package | Element of FutureMeasurementDirective<br>This element is a container for a configuration package.<br>This element is present only if Response = "3" (Conf Package Present). | 0-1                                             | NOTE – Defined in Table 16.                                                                                                                                                                                                                                                                                                                                                             |
+
+NOTE 1 – To deactivate the current configuration package or to not require measurement, either use the "1" (No AM required code) for ImmediateMeasurementDirective or an empty "ConfigPackageRequest Response".
+
+NOTE 2 – To keep the current configuration package and to provide a future one, configure the ImmediateMeasurement Code as "2" (No Conf Package Change) and FutureMeasurementDirective Code as "3" (configuration package present).
+
+```
+
+ConfigPackageRequestResponse (1)
+| ConfigurationPackageCheckDelay (0-1)
+| ImmediateMeasurementDirective (0-1)
+| | Code (0-1)
+| | AMFConfigPackage (0-1)
+| FutureMeasurementDirective (0-1)
+| | Code (0-1)
+| | AMFConfigPackage (0-1)
+
+```
+
+**Figure 19 – Alternative representation of ConfigPackageRequestResponse data structure**
+
+#### 6.2.10 Data structure for "user permit"
+
+Table 20 defines the data structure for "user permit".
+
+Figure 20 contains an alternative representation of the user permit data structure.
+
+**Table 20 – Data structure of "user permit"**
+
+| Element                                  | Description                                                                                                                                                                                               | Support/<br>type               | Notes or value domain                                                                                                  |
+|------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|------------------------------------------------------------------------------------------------------------------------|
+| UserPermit                               | Container for all sets of end-user permission associated to services of a IPTV service provider.                                                                                                          | 1                              |                                                                                                                        |
+| ExpirationDate                           | Element of UserPermit<br>Indicates the end date for which permission was given.                                                                                                                           | 0-1<br>xs:date                 | NOTE – This field may be regulated in certain countries.                                                               |
+| Default<br>PermissionLevel               | Element of UserPermit<br>Identification of the end-user permission level for all services offered by a IPTV service provider accessed from all IPTV terminal devices.                                     | 0-1                            | NOTE – Defined as Permission Level in Table 3.                                                                         |
+| DefaultAll<br>ContentClass<br>ExceptList | Element of UserPermit<br>List of content classes not to be measured.                                                                                                                                      | 0-1                            | NOTE – Defined as AllContent ClassExceptList in Table 10.                                                              |
+| AnonUserID                               | Element of UserPermit.<br>Anonymous end-user ID<br>Generated number which is persistently used for one end user                                                                                           | 0-*                            | Defined in Table 4<br>NOTE – To be included if there is a permission level in this permit with a value less than 3.    |
+| UserID                                   | Element of UserPermit<br>This element uniquely identifies an end user.                                                                                                                                    | 0-*                            | Defined in Table 4<br>NOTE – To be included if there is a permission level in this permit with a value of more than 2. |
+| UserPermission<br>Set                    | Element of UserPermit<br>Container for an end-user permission set associated with specific services.                                                                                                      | 0-*                            |                                                                                                                        |
+| PermissionLevel                          | Element of UserPermissionSet<br>Identification of the end-user permission level as specified in this Recommendation.                                                                                      | 0-1                            | NOTE – If not present then refer to DefaultPermissionLevel.                                                            |
+| UserPermission                           | Element of UserPermissionSet<br>Container for an end-user permission.                                                                                                                                     | 1-*                            |                                                                                                                        |
+| ChannelQualifier                         | Element of UserPermission<br>Container for the elements allowing to select the specific services for which this end-user permission is granted among all LinearTV services of this IPTV service provider. | 0-1                            | NOTE – Defined in [ITU-T H.741.3].                                                                                     |
+| TerminalDevice<br>Set                    | Element of UserPermission<br>This container identifies the list of IPTV terminal devices for which this end-user permission applies.                                                                      | 0-1<br>Default: all<br>of them |                                                                                                                        |
+
+**Table 20 – Data structure of "user permit"**
+
+| Element                       | Description                                                                                      | Support/<br>type                   | Notes or value domain                                                                                |
+|-------------------------------|--------------------------------------------------------------------------------------------------|------------------------------------|------------------------------------------------------------------------------------------------------|
+| TerminalDevice<br>Type        | Element of TerminalDeviceSet<br>This element identifies a specific type of IPTV terminal device. | 1-*<br>xs:hexBinary<br>enumeration | Values: 0=STB, 1=TV, 2=Mobile, 3=PC, 4=Tablet, 5=Other.                                              |
+| AllContentClass<br>ExceptList | Element of UserPermission<br>List of content classes not to be measured.                         | 0-1                                | NOTES<br>– Defined in Table 10.<br>– If not present then refer to DefaultAllContentClass ExceptList. |
+
+```
+
+UserPermit (1)
+| ExpirationDate (0-1)
+| DefaultPermissionLevel (0-1)
+| DefaultAllContentClassExceptList (0-1)
+| AnonUserID (0-1)
+| UserID (0-1)
+| UserPermissionSet (0-*)
+| | PermissionLevel (0-1)
+| | UserPermission (1-*)
+| | | ChannelQualifier (0-1)
+| | | TerminalDeviceSet (0-1)
+| | | | TerminalDeviceType (1-*)
+| | | AllContentClassExceptList (0-1)
+
+```
+
+**Figure 20 – Alternative representation of UserPermit data structure**
+
+#### **6.2.11 Data structure for "measurement report" with service-common events and/or samples**
+
+Table 21 defines the data structure for a measurement report including service-common events and/or samples. Multiple elements which are associated with a single trigger time may be included in a particular instance of MeasurementReport.
+
+Figure 21 contains an alternative representation of the "MeasurementReport" data structure.
+
+**Table 21 – Data structure for "measurement report" with service-common events and/or samples**
+
+| Element                          | Description                                                                                                                                                                                                                                           | Support/<br>type                          | Notes or value domain                                                                                                                                 |
+|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|
+| MeasurementReport                | Element of AMReportPackage<br>Container for a measurement report .                                                                                                                                                                                    | 0-1                                       | NOTE – Extended in [ITU-T H.741.3].                                                                                                                   |
+| MeasurementRequestID             | Element of MeasurementReport<br>This element identifies the measurement request which generated this measurement report.                                                                                                                              | 1                                         | NOTE – Defined in Table 9.                                                                                                                            |
+| MeasurementReport<br>TriggerTime | Element of MeasurementReport<br>This element identifies the time at which the measurement report was created or the measurement period ended.                                                                                                         | 1<br>xs:date<br>Time                      | NOTE – This is the time that an event or sample value was measured, or the start or end of a measurement period. Specify an offset from the UTC time. |
+| DisplayStatus                    | Element of MeasurementReport<br>Element to report DisplayStatus event which occurs when there is a change in the display status of the IPTV Service output of the terminal device.                                                                    | 0-1<br>xs:string<br>enumeration           | Values: 'turned off', 'turned on'<br>NOTE – Services being displayed may be determined by correlation with ServiceStart and ServiceStop events.       |
+| AudioFocus                       | Element of MeasurementReport<br>Container to report AudioFocus event which occurs when the audio focus of the IPTV terminal device changes among multiple concurrent IPTV or other services such that the audio of a particular service is presented. | 0-1                                       |                                                                                                                                                       |
+| ServiceInstanceID                | Element of AudioFocus<br>Identifies the instance of the specific IPTV service which is/was last presenting audio.                                                                                                                                     | 1<br>(Note 2)                             | Defined in Table 2.                                                                                                                                   |
+| IPTVFocus                        | Element of AudioFocus<br>Indicates whether the audio focus is associated with an IPTV service.                                                                                                                                                        | 0-1<br>xs:<br>boolean<br>Default:<br>True | True, False.                                                                                                                                          |
+| CaptionLanguage<br>Change        | Element of MeasurementReport<br>Container to report CaptionLanguageChange event.                                                                                                                                                                      | 0-1                                       |                                                                                                                                                       |
+| ServiceInstanceID                | Element of CaptionLanguageChange<br>Identifies the instance of a specific service.                                                                                                                                                                    | 1                                         | Defined in Table 2.                                                                                                                                   |
+
+**Table 21 – Data structure for "measurement report" with service-common events and/or samples**
+
+| <b>Element</b>             | <b>Description</b>                                                                                                    | <b>Support/<br/>type</b> | <b>Notes or value domain</b>                                                   |
+|----------------------------|-----------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------------------------|
+| CaptionLanguage            | Element of CaptionLanguageChange<br>It identifies the caption language now being used for the indicated service.      | 1                        | Defined in Table 2.                                                            |
+| AudioLanguageChange        | Element of MeasurementReport<br>Container to report AudioLanguageChange event.                                        | 0-1                      |                                                                                |
+| ServiceInstanceID          | Element of AudioLanguageChange<br>Identifies the instance of a specific service.                                      | 1                        | Defined in Table 2.                                                            |
+| AudioLanguage              | Element of AudioLanguageChange<br>Identifies the audio language now being used for the indicated service.             | 1                        | Defined in Table 2.                                                            |
+| AudioVolume                | Element of MeasurementReport<br>Indicates that the end user has changed the audio volume.                             | 0-1                      | This element is activated by configuring event AudioVolume of Table 5.         |
+| ServiceInstanceID          | Element of AudioVolume<br>Identifies the instance of a specific service.                                              | 1                        | Defined in Table 2.                                                            |
+| VolumeDirection            | Element of AudioVolume<br>Indicates how the end user has changed the audio volume.                                    | 1                        | Defined in Table 2.                                                            |
+| ConfigurationChange        | Element of MeasurementReport<br>Indicates that the end user has changed their device's configuration or capabilities. | 0-1                      | This element is activated by configuring event ConfigurationChange of Table 5. |
+| AMFCapabilityProfile       | Element of ConfigurationChange<br>This element indicates the AM profile supported by the IPTV terminal device.        | 0-1                      | Defined in Table 2.                                                            |
+| TVInformation              | Element of ConfigurationChange<br>Container for TV information.                                                       | 0-1                      | Defined in Table 2.                                                            |
+| AudioAmplifier Information | Element of ConfigurationChange<br>Container for audio system information.                                             | 0-1                      | Defined in Table 2.                                                            |
+| VideoObscure               | Element of MeasurementReport<br>Indicates that the end user has changed the amount of video obscured.                 | 0-1                      | This element is activated by configuring event VideoObscure of Table 5.        |
+
+**Table 21 – Data structure for "measurement report" with service-common events and/or samples**
+
+| <b>Element</b>    | <b>Description</b>                                                                               | <b>Support/<br/>type</b>                           | <b>Notes or value domain</b>                                                          |
+|-------------------|--------------------------------------------------------------------------------------------------|----------------------------------------------------|---------------------------------------------------------------------------------------|
+| ServiceInstanceID | Element of VideoObscure<br>Identifies the instance of a specific service.                        | 1                                                  | Defined in Table 2.                                                                   |
+| Obscuration       | Element of VideoObscure<br>Indicates the percentage of image obscured.                           | 1                                                  | Defined in Table 2.                                                                   |
+| VideoZoom         | Element of MeasurementReport<br>Indicates that the end user has changed the zoom factor.         | 0-1                                                | This element is activated by configuring event VideoZoom of Table 5.                  |
+| ServiceInstanceID | Element of VideoZoom<br>Identifies the instance of a specific service.                           | 1                                                  | Defined in Table 2.                                                                   |
+| ZoomFactor        | Element of VideoZoom<br>Indicates video image zoom factor multiple.                              | 1                                                  | Defined in Table 2.                                                                   |
+| VideoResize       | Element of MeasurementReport<br>Indicates that the end user has collapsed or expanded the video. | 0-1                                                | This element is activated by configuring event VideoResize of Table 5.                |
+| ServiceInstanceID | Element of VideoResize<br>Identifies the instance of a specific service.                         | 1                                                  | Defined in Table 2.                                                                   |
+| ImageWidth        | Element of VideoResize<br>Width of video.                                                        | 1                                                  | Defined in Table 2.                                                                   |
+| ImageHeight       | Element of VideoResize<br>Height of video.                                                       | 1                                                  | Defined in Table 2.                                                                   |
+| EventCount        | Element of MeasurementReport<br>Indicates the number of events during eventcount period.         | 0-*                                                | This element is activated by configuring sample set identifier EventCount of Table 6. |
+| EventsCounted     | Element of EventCount<br>Indicates the number of events during EventCount period.                | 0-1<br>xs:<br>nonNegative<br>Integer<br>Default: 0 |                                                                                       |
+| ServiceInstanceID | Element of EventCount<br>Identifies the instance of a specific service.                          | 1                                                  | Defined in Table 2.                                                                   |
+| StartTime         | Element of EventCount<br>Time when EventCount period started.                                    | 1<br>xs:time                                       |                                                                                       |
+
+**Table 21 – Data structure for "measurement report" with service-common events and/or samples**
+
+| <b>Element</b>                 | <b>Description</b>                                                                                                                   | <b>Support/<br/>type</b> | <b>Notes or value domain</b>                                                                                           |
+|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------|------------------------------------------------------------------------------------------------------------------------|
+| DeviceInformation              | Element of MeasurementReport<br>This is a container for device information of STB, TV, IPTV-TV, Mobile, PC and audio system devices. | 0-1                      | This element is activated by configuring sample set identifier DeviceInfo of Table 6.                                  |
+| STBInformation                 | Element of DeviceInformation<br>Container for STB information.                                                                       | 0-1                      | Defined in Table 2.                                                                                                    |
+| AudioAmplifier Information     | Element of DeviceInformation<br>Container for audio system information.                                                              | 0-1                      | Defined in Table 2.                                                                                                    |
+| TVInformation                  | Element of DeviceInformation<br>Container for TV information.                                                                        | 0-1                      | Defined in Table 2.                                                                                                    |
+| IPTV-TVInformation             | Element of DeviceInformation<br>Container for IPTV TV information.                                                                   | 0-1                      | Defined in Table 2.                                                                                                    |
+| MobileDevice Information       | Element of DeviceInformation<br>Container for Mobile device information.                                                             | 0-1                      | Defined in Table 2.                                                                                                    |
+| PCInformation                  | Element of DeviceInformation<br>Container for PC information.                                                                        | 0-1                      | Defined in Table 2.                                                                                                    |
+| UserBiographic Information     | Element of MeasurementReport<br>This is a container for an end-users' biographic information.                                        | 0-1                      | This element is activated by configuring sample set identifier UserBioInfo of Table 6.<br>Used for permission level 3. |
+| UserIdBioInfo                  | Element of UserBiographicInformation<br>This is a container for an end-users' biographic information.                                | 1-*                      |                                                                                                                        |
+| UserId                         | Element of UserIdBioInfo<br>This element uniquely identifies an end user.                                                            | 0-1                      | Defined in Table 4.                                                                                                    |
+| ControlledUserInfo TypeString  | Element of UserIdBioInfo<br>Identifies controlled end-user information type.                                                         | 0-*                      | Defined in Table 3.                                                                                                    |
+| ControlledUserInfo TypeDate    | Element of UserIdBioInfo<br>Identifies controlled end-user information type.                                                         | 0-*                      | Defined in Table 3.                                                                                                    |
+| ControlledUserInfo TypeAddress | Element of UserIdBioInfo<br>Identifies controlled end-user information type.                                                         | 0-*                      | Defined in Table 3.                                                                                                    |
+
+**Table 21 – Data structure for "measurement report" with service-common events and/or samples**
+
+| <b>Element</b>       | <b>Description</b>                                                                                                                                 | <b>Support/<br/>type</b> | <b>Notes or value domain</b>                                                                                                     |
+|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|----------------------------------------------------------------------------------------------------------------------------------|
+| TDLocation           | Element of MeasurementReport<br>Container for location elements.                                                                                   | 0-1                      | Defined in Table 4.                                                                                                              |
+| UserList             | Element of MeasurementReport<br>Container for one or more end-user(s) information.                                                                 | 0-1                      | Defined in Table 4.<br>NOTE – Only end users who have given permission levels 1-3 per Table 3 are included.                      |
+| UserPresent          | Element of MeasurementReport<br>Container for end-user presence information from one source.                                                       | 0-*                      | Defined in Table 4.                                                                                                              |
+| GenericUserInfo      | Element of MeasurementReport<br>This element is a container for end user and generic end-user info to be reported for end users present.           | 0-1                      | This element is activated by configuring sample set identifier GenericUserInfo of Table 6.<br>Used for permission levels 2 or 3. |
+| UserIDGenericInfo    | Element of GenericUserInfo<br>Container for individual end-user information.                                                                       | 1-*                      |                                                                                                                                  |
+| AnonUserID           | Element of UserIDGenericInfo<br>Generated number which persistently is used for one end user.                                                      | 0-1<br>(Note 1)          | Defined in Table 4.                                                                                                              |
+| UserID               | Element of UserIDGenericInfo<br>This element uniquely identifies an end user.                                                                      | 0-1<br>(Note 1)          | Defined in Table 4.                                                                                                              |
+| GenericUserInfoType  | Element of UserIDGenericInfo<br>Identifies generic end-user information type.                                                                      | 0-*                      | Defined in Table 4.                                                                                                              |
+| GenericUserInfoValue | Attribute of GenericUserInfoType<br>Identifies generic end-user information value.                                                                 | 1                        | Defined in Table 4.                                                                                                              |
+| UserInfoChange       | Element of MeasurementReport<br>Indicates that an end user has changed their end-user information.<br>Container for end-user ID and end-user info. | 0-1                      | NOTE – End users who have given permission levels 2-3 per Table 3 are included.                                                  |
+| AnonUserID           | Element of UserInfoChange<br>Generated number which persistently is used for one end user.                                                         | 0-1<br>(Note 1)          | Defined in Table 4.                                                                                                              |
+
+**Table 21 – Data structure for "measurement report" with service-common events and/or samples**
+
+| <b>Element</b>                 | <b>Description</b>                                                                                                                              | <b>Support/<br/>type</b> | <b>Notes or value domain</b> |
+|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|------------------------------|
+| UserID                         | Element of UserInfoChange<br>This element uniquely identifies an end user.                                                                      | 0-1<br>(Note 1)          | Defined in Table 4.          |
+| ControlledUserInfo TypeString  | Element of UserInfoChange<br>Identifies controlled end-user information type.                                                                   | 0-*                      | Defined in Table 3.          |
+| ControlledUserInfo TypeDate    | Element of UserInfoChange<br>Identifies controlled end-user information type.                                                                   | 0-*                      | Defined in Table 3.          |
+| ControlledUserInfo TypeAddress | Element of UserInfoChange<br>Identifies controlled end-user information type.                                                                   | 0-*                      | Defined in Table 3.          |
+| GenericUserInfoType            | Element of UserInfoChange<br>Identifies generic end-user information type.                                                                      | 0-*                      | Defined in Table 3.          |
+| GenericUserInfoValue           | Attribute of GenericUserInfoType<br>Identifies generic end-user information value.                                                              | 1                        | Defined in Table 3.          |
+| PermitBlockedInfo              | Element of MeasurementReport<br>Container for flags indicating that configured measurements were blocked due to a constraining end-user permit. | 0-1                      | NOTE – Defined in Table 4.   |
+
+NOTE 1 – Either AnonUserID or UserID must be present.  
+NOTE 2 – The ServiceInstanceID of an IPTV service is reported when it becomes the audio focus of the end user, the ServiceInstanceID of an IPTV service which loses audio focus is reported only when a non-IPTV service or an IPTV service which is not to be reported becomes the focus.
+
+```
+
+MeasurementReport (0-1)
+| MeasurementRequestID (1)
+| MeasurementReportTriggerTime (1)
+| DisplayStatus (0-1)
+| AudioFocus (0-1)
+| | ServiceInstanceID (1)
+| | IPTVFocus (0-1)
+| CaptionLanguageChange (0-1)
+| | ServiceInstanceID (1)
+| | CaptionLanguage (1)
+| AudioLanguageChange (0-1)
+| | ServiceInstanceID (1)
+| | AudioLanguage (1)
+| AudioVolume (0-1)
+| | ServiceInstanceID (1)
+| | VolumeDirection (1)
+| VideoObscure (0-1)
+| | ServiceInstanceID (1)
+| | Obscuration (1)
+| VideoZoom (0-1)
+| | ServiceInstanceID (1)
+| | ZoomFactor (1)
+| VideoResize (0-1)
+| | ServiceInstanceID (1)
+| | ImageWidth (1)
+| | ImageHeight (1)
+| EventCount (0-*)
+| | EventsCounted (0-1)
+| | ServiceInstanceID (1)
+| | StartTime (1)
+| DeviceInformation (0-1)
+| | STBInformation (0-1)
+| | AudioAmplifierInformation (0-1)
+| | TVInformation (0-1)
+| | MobileDeviceInformation (0-1)
+| | PCInformation (0-1)
+| UserBiographicInformation (0-1)
+| | UserIdBioInfo (1-*)
+| | | UserId (0-1)
+| | | ControlledUserInfoTypeString (0-*) [ ControlledUserInfoValueString (1) ]
+| | | ControlledUserInfoTypeDate (0-*) [ ControlledUserInfoValueDate (1) ]
+| | | ControlledUserInfoTypeAddress (0-*) [ ControlledUserInfoValueAddress (1) ]
+
+```
+
+```
+
+| TDLocation (0-1)
+| UserList (0-1)
+| | UserIDInfo (1-*)
+| | | AnonUserID (0-1)
+| | | UserID (0-1)
+| | | UserIDMethod (0-1)
+| | | UserIDConfidence (0-1)
+| UserPresent (0-*)
+| | PresenceMethod (0-1)
+| | PresenceTime (0-1)
+| | PresenceConfidence (0-1)
+| GenericUserInfo (0-1)
+| | UserIDGenericInfo (1-*)
+| | | AnonUserID (0-1)
+| | | UserID (0-1)
+| | | GenericUserInfoType (0-*) [ GenericUserInfoValue (1) ]
+| UserInfoChange (0-1)
+| | AnonUserID (0-1)
+| | UserID (0-1)
+| | ControlledUserInfoTypeString (0-*) [ ControlledUserInfoValueString (1) ]
+| | ControlledUserInfoTypeDate (0-*) [ ControlledUserInfoValueDate (1) ]
+| | ControlledUserInfoTypeAddress (0-*) [ ControlledUserInfoValueAddress (1) ]
+| | GenericUserInfoType (0-*) [ GenericUserInfoValue (1) ]
+| PermitBlockedInfo (0-1)
+| | PermissionLevelFlag (0-1)
+| | TerminalDeviceTypeFlag (0-1)
+| | ChannelFlag (0-1)
+
+```
+
+**Figure 21 – Alternative representation of MeasurementReport data structure**
+
+##### 6.2.11.1 Metadata for identification of end users
+
+It may be assumed that the user of a single-end-user device is the same most of the time: as an example, a single mobile phone subscriber. However, a set of family mobile phones may only have the associated subscriber identity rather than the end user of each phone. In the case of a shared device such as a TV, it is less evident that it is the subscriber who is watching rather than others. For shared devices like TVs, multiple simultaneous viewers may be watching. Furthermore, certain devices, such as TVs, may be left playing out content without any viewer present.
+
+This is why the following elements are defined: "UserIDConfidence", support for multiple simultaneous end-user information, and code flags to identify techniques used to detect the presence of one or more end users, to distinguish among anonymous end users, and to identify end users.
+
+#### 6.2.12 Data structure for "audience measurement report package"
+
+As there may be several measurement reports ready for delivery to the aggregation functions, a data structure for measurement reporting is defined to be able to include one or more measurement reports if necessary.
+
+Figure 22 contains an alternative representation of the "audience measurement report package" data structure.
+
+**Table 22 – Data structure for audience measurement report package**
+
+| Element                          | Description                                                                                                                                                                   | Support/<br>type                                         | Notes or value domain                                                 |
+|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|-----------------------------------------------------------------------|
+| AMReportPackage                  | Container for a set of measurement reports.                                                                                                                                   | 1                                                        |                                                                       |
+| SubscriberID                     | Element of AMReportPackage<br>This element contains the identification of the subscriber to the services of the associated service provider.                                  | 0-1                                                      | Defined in Table 4.<br>Required when configuration push mode is used. |
+| TerminalDeviceID                 | Element of AMReportPackage<br>This element uniquely identifies the end user's terminal device based on the device's MAC address.                                              | 1<br>xs:hexBinary<br>length = 16<br>octets<br>(128 bits) |                                                                       |
+| StorageCongestionImpactedService | Element of AMReportPackage<br>ServiceInstanceID impacted by dropping information due to storage congestion policy and priority since the previous measurement report message. | 0-*                                                      | Defined as ServiceInstanceID in Table 2.                              |
+| ServiceStopDropped               | Attribute of StorageCongestionImpactedService<br>Indicates that the ServiceStop event has been dropped for this ServiceInstanceID.                                            | 0-1<br>xs:boolean<br>Default:<br>False                   |                                                                       |
+| MeasurementReport                | Element of AMReportPackage<br>Container for a measurement report.                                                                                                             | 1-*<br>(Note)                                            | Defined in Table 21 and extended in [ITU-T H.741.3].                  |
+
+NOTE – If an empty report is ready to be sent and there are no non-empty reports ready to be sent, then the empty report is sent in the measurement report package. If a non-empty report is ready to be sent, then it is recommended to ignore the empty report . When there are multiple empty reports ready, only the most recent empty report is required to be sent in the measurement report package.
+
+```
+
+AMReportPackage (1)
+| SubscriberID (0-1)
+| TerminalDeviceID (1)
+| StorageCongestionImpactedService (0-*) [ ServiceStopDropped (0-1) ]
+| MeasurementReport (1-*)
+
+```
+
+**Figure 22 – Alternative representation of AMReportPackage data structure**
+
+## 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*.
+- [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 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.1153] Recommendation ITU-T X.1153 (2011), *Management framework of a one time password-based authentication service*.
+- [b-ITU-T X.1191] Recommendation ITU-T X.1191 (2009), *Functional requirements and architecture for IPTV security aspects*.
+- [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-IETF RFC 5054] IETF RFC 5054 (2007), *Using the Secure Remote Password (SRP) Protocol for TLS Authentication*.
+- [b-IETF RFC 6120] IETF RFC 6120 (2011), *Extensible Messaging and Presence Protocol (XMPP): Core*.
+- [b-IETF RFC 6121] IETF RFC 6121 (2011), *Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence*.
+- [b-IETF RFC 6122] IETF RFC 6122 (2011), *Extensible Messaging and Presence Protocol (XMPP): Address Format*.
+
+- [b-FIPS PUB 198-1] National Institute of Standards and Technology (NIST), FIPS PUB 198-1 (2008), *The Keyed-Hash Message Authentication Code (HMAC)*.  
+[http://csrc.nist.gov/publications/fips/fips198-1/FIPS-198-1\\_final.pdf](http://csrc.nist.gov/publications/fips/fips198-1/FIPS-198-1_final.pdf)
+- [b-HDMI] High-Definition Multimedia Interface (HDMI), *HDMI Specification Version 1.3a, 2006*.  
+<http://www.hdmi.org/index.aspx>
+- [b-VESA EDID] Video Electronics Standards Association (VESA) E-EDID™ Standard (2006), *VESA enhanced extended display identification data standard: Release A, Revision 2, September 25, 2006*.  
+<http://www.vesa.org/>
+
+
+
+
+
+## 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.3-201206-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/H/T-REC-H.741.3-201206-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5f5e9f83438991e26216de68690a6aa3744b937f
--- /dev/null
+++ b/marked/H/T-REC-H.741.3-201206-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88113ebe75ca5ad6229bc7c97c10f56ddaa8e92c3e215b6cee0c561723577d68
+size 23816
diff --git a/marked/H/T-REC-H.741.3-201206-I_PDF-E/392a79ccd95e682ccd08f35ab2e64144_img.jpg b/marked/H/T-REC-H.741.3-201206-I_PDF-E/392a79ccd95e682ccd08f35ab2e64144_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8462ef3564c6240c1f702a810d6074f6879505c6
--- /dev/null
+++ b/marked/H/T-REC-H.741.3-201206-I_PDF-E/392a79ccd95e682ccd08f35ab2e64144_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e6139f77f213d57fd2dd881b4cbc7ea104aa74eca5edd231d1ccf491bd6dc118
+size 65925
diff --git a/marked/H/T-REC-H.741.3-201206-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg b/marked/H/T-REC-H.741.3-201206-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4cb97d1fe849546932dfeca8319bf432ab8afdfb
--- /dev/null
+++ b/marked/H/T-REC-H.741.3-201206-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8879edbd6df943616e6de280b9c44b19952f82573004e9c17f012902b8682ce3
+size 3832
diff --git a/marked/H/T-REC-H.741.3-201206-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/H/T-REC-H.741.3-201206-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4938d3e2a636695b3ca3033a4312800df6866e1f
--- /dev/null
+++ b/marked/H/T-REC-H.741.3-201206-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aebc0cc70feec42aa2fa6dab7102ca4675b50bcc96092b9d19a54fcd81cf216c
+size 39257
diff --git a/marked/H/T-REC-H.741.3-201206-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.741.3-201206-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994
--- /dev/null
+++ b/marked/H/T-REC-H.741.3-201206-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.741.3-201206-I_PDF-E/b0211cee4b20034939d883ac0d70f696_img.jpg b/marked/H/T-REC-H.741.3-201206-I_PDF-E/b0211cee4b20034939d883ac0d70f696_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0f65b1f1af081aab9a00bb92c1fb1dc7f55f8edd
--- /dev/null
+++ b/marked/H/T-REC-H.741.3-201206-I_PDF-E/b0211cee4b20034939d883ac0d70f696_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:20c954c3b6bb4ec2ca5abd1bfc0d258bbb7717ad17bac5a5b97981fd1a3d10e1
+size 4571
diff --git a/marked/H/T-REC-H.741.3-201206-I_PDF-E/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg b/marked/H/T-REC-H.741.3-201206-I_PDF-E/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f99528eb82ad2066b905e46db9c58c4f1b32b68f
--- /dev/null
+++ b/marked/H/T-REC-H.741.3-201206-I_PDF-E/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d6d3cd6c10abc19f5ead464df4293f467ebbf06663e8185e9bfc71856ddb2530
+size 17721
diff --git a/marked/H/T-REC-H.741.3-201206-I_PDF-E/raw.md b/marked/H/T-REC-H.741.3-201206-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..f25ba958db24db37fc7ab097430f94a7580a8a6b
--- /dev/null
+++ b/marked/H/T-REC-H.741.3-201206-I_PDF-E/raw.md
@@ -0,0 +1,1124 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.741.3**
+
+(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 for IPTV distributed content  
+services**
+
+Recommendation ITU-T H.741.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        |
+| <b>IPTV application event handling</b>                                        | <b>H.740–H.749</b> |
+| 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.3
+
+# **IPTV application event handling: Audience measurement for IPTV distributed content 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.3 specifies audience measurement for IPTV distributed content services and, in particular, linear TV services. It describes specific configuration for linear TV and metadata and data structures used in the payload of AM messages. The informative appendices discuss specific implementation considerations for linear TV-specific implementation considerations, provide examples and describe capabilities and profiles.
+
+## **History**
+
+| Edition | Recommendation | Approval   | Study Group |
+|---------|----------------|------------|-------------|
+| 1.0     | ITU-T H.741.3  | 2012-06-29 | 16          |
+
+## **Keywords**
+
+Audience measurement, audience rating service, audience viewership, contents rating, data structures, distributed content service, engagement metrics, implementation guidelines, IPTV application event handling, linear TV, metadata.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                                                                   | 3    |
+| 4 Abbreviations and acronyms .....                                                                              | 3    |
+| 5 Conventions .....                                                                                             | 4    |
+| 6 Overview .....                                                                                                | 4    |
+| 7 Specific audience measurement for linear TV.....                                                              | 5    |
+| 7.1 Audience measurement configuration for linear TV .....                                                      | 5    |
+| 7.2 Linear TV metadata .....                                                                                    | 6    |
+| Appendix I – Implementation considerations .....                                                                | 15   |
+| I.1 Considerations regarding the enabling of control device reporting .....                                     | 15   |
+| I.2 Considerations regarding the enabling of navigation method reporting .....                                  | 15   |
+| I.3 Considerations for specifying channels to be measured.....                                                  | 15   |
+| I.4 Considerations for using channel change filtering and how to choose the value .....                         | 16   |
+| Appendix II – Examples of configuration and reporting of the terminal device audience measurement function..... | 17   |
+| II.1 Configuration example .....                                                                                | 17   |
+| II.2 Example measurement reports associated with example configuration of Figure II.1 .....                     | 20   |
+| II.3 Picture-in-picture (PIP) example .....                                                                     | 24   |
+| Appendix III – Audience measurement capability profiles .....                                                   | 29   |
+| Bibliography.....                                                                                               | 30   |
+
+
+
+# Recommendation ITU-T H.741.3
+
+# **IPTV application event handling: Audience measurement for IPTV distributed content services**
+
+## **1 Scope**
+
+This Recommendation describes audience measurement for IPTV distributed content services. This includes specific events and samples, configuration and reporting for linear TV services. Subsequent releases will address additional IPTV distributed content 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.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.770] Recommendation ITU-T H.770 (2009), *Mechanisms for service discovery and selection for IPTV services.*
+
+## **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 measurement** [ITU-T H.741.0]: The measurement of people's engagement with IPTV services.
+- 3.1.5 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.6 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.7 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.8 content (object)** [b-ITU-T T.174]: Encoded generic value, media or non-media data.
+
+**3.1.9 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.10 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.11 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.12 IPTV terminal device** [b-ITU-T Y.1901]: A terminal device which has IPTV terminal function (ITF) functionality, e.g., an STB.
+
+**3.1.13 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.14 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.15 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.16 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.17 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.18 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.19 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.20 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.21 service** [b-ITU-T Y.101]: A structure set of capabilities intended to support applications.
+
+**3.1.22 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.23 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.24 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.25 set-top box (STB)** [b-ITU-T J.183]: A hardware box that contains 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.26 stream** [b-ITU-T J.200]: A unidirectional continuous flow of content.
+
+**3.1.27 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.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 audio-visual media player.
+
+### **3.2 Terms defined in this Recommendation**
+
+This Recommendation defines the following terms:
+
+**3.2.1 channel surfing**: The action by an end user of holding down a navigation key which causes linear TV services to be skipped.
+
+**3.2.2 mosaic**: A display in which many services are received and displayed simultaneously in the format of a matrix of icons.
+
+**3.2.3 picture-in-picture**: A service displayed over a small part of the main service display. Sound is usually from the main service only.
+
+## **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                   |
+|------|-----------------------------------|
+| AM   | Audience Measurement              |
+| AMF  | Audience Measurement Function     |
+| API  | Application Programming Interface |
+| EPG  | Electronic Programme Guide        |
+| HD   | High Definition                   |
+| HTTP | Hypertext Transfer Protocol       |
+| ID   | Identifier                        |
+| ms   | milliseconds                      |
+| PIP  | Picture-In-Picture                |
+
+|        |                                               |
+|--------|-----------------------------------------------|
+| QoE    | Quality of Experience                         |
+| QoS    | Quality of Service                            |
+| SP     | Service Provider                              |
+| TD-AMF | Terminal Device Audience Measurement Function |
+| TV     | Television                                    |
+
+## 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/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'.](54fabc351eda5228d2fa28cd9ba07971_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 the context of IPTV architecture:
+
+![A rectangular box containing the words 'Functional block'.](b0211cee4b20034939d883ac0d70f696_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.
+
+## 6 Overview
+
+Audience measurement (AM) configuration, reporting and data structures for service-common events and samples are specified in [ITU-T H.741.1] and [ITU-T H.741.2]. This Recommendation specifies configuration, reporting and data structures for linear TV events and samples.
+
+# 7 Specific audience measurement for linear TV
+
+An IPTV terminal device may have different ways of displaying TV channels. For example, a TV channel may be displayed on the full screen of a TV, whereas some TVs may simultaneously receive two TV channels and display them both, one in full screen and the other in a picture-in-picture (PIP) mode. Subsequent channel changes may occur either on the full screen or in the reduced window for the second channel. Usually the audio channel is the one of the full screen TV channels.
+
+A second alternative to full-screen display is when more than one TV channels may be displayed simultaneously, for example, in a mosaic. The audio channel is usually assigned to one TV channel for which the end user has shown more interest.
+
+A "channel start" event, when configured and allowed, generates an audience-measurement report indicating the new channel and how it is displayed. If a "channel start" event follows a previously delivered service, then the report will also indicate that the previous service is no longer active.
+
+A "channel stop" event indicates that the displayed TV channel associated with the "channel start" event is no longer being measured. This may occur for one of several reasons, for instance:
+
+- Sampling of the linear TV channel playing is supported.
+- The navigation methods used in linear TV are identifiable.
+- The control device used in linear TV is identifiable.
+
+### 7.1 Audience measurement configuration for linear TV
+
+The AM configuration of linear TV is part of the AM configuration "Configuration of services to be measured", as described in [ITU-T H.741.1]. Each measurement request is configured to indicate whether linear TV measurements are to be made. Linear TV services may be configured with associated parameters as follows.
+
+#### 7.1.1 Channels to be measured
+
+Either all channels or a list of channels to be measured may be configured. Alternatively, an "all channel except" list may be configured.
+
+#### 7.1.2 Summarization and filtering
+
+Configuration of a channel change filter time between channel change events can be used to filter out unneeded reports. When configured, reports relating to infrequently used channels may be additionally delayed by the channel change filter time. In Figure 1 below, the report for event A is delayed until the channel change filter time following event A. The report for event B will not be reported. The report for event C will be determined depending upon the subsequent occurrence of another event within the channel change filter time.
+
+![Figure 1 – Channel change report filtering diagram](ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg)
+
+The diagram illustrates the timing of channel change reports relative to a 'Channel change filter time'. A horizontal timeline at the top shows three vertical arrows representing events A, B, and C. Event A is followed by a horizontal double-headed arrow labeled 'Report A', which ends at the start of a longer horizontal double-headed arrow labeled 'Channel change filter time'. Event B occurs while the filter time from event A is still active. Event C occurs after the filter time from event A has expired. A horizontal double-headed arrow labeled 'Don't report B' is shown between events B and C. A vertical line on the left is labeled 'Sequence of "channel start" and/or "channel stop" events'.
+
+Figure 1 – Channel change report filtering diagram
+
+Figure 1 – Channel change report filtering
+
+When event A is a channel start event, in order to minimize the reporting latency regarding leaving channel A, a channel stop event for A, using the measurement time of event B, is reported when event C occurs.
+
+![Figure 2: Channel change filtered reporting following channel start event. The diagram shows a timeline with three vertical lines representing events A, B, and C. Event A is labeled 'Sequence of "channel start" followed by "channel start" and/or "channel stop" events'. A horizontal double-headed arrow from A to B is labeled 'Channel change filter time'. A horizontal arrow from A to B is labeled 'Report "channel start" A'. Event B is a vertical line. Event C is a vertical line. A horizontal double-headed arrow from B to C is labeled 'Report "channel stop" A'. A horizontal arrow from B to C is labeled 'Don't report B'. The diagram is labeled H.741.3(12)_F02 at the bottom right.](007b053fe94a8348f75128a584503fd0_img.jpg)
+
+Figure 2: Channel change filtered reporting following channel start event. The diagram shows a timeline with three vertical lines representing events A, B, and C. Event A is labeled 'Sequence of "channel start" followed by "channel start" and/or "channel stop" events'. A horizontal double-headed arrow from A to B is labeled 'Channel change filter time'. A horizontal arrow from A to B is labeled 'Report "channel start" A'. Event B is a vertical line. Event C is a vertical line. A horizontal double-headed arrow from B to C is labeled 'Report "channel stop" A'. A horizontal arrow from B to C is labeled 'Don't report B'. The diagram is labeled H.741.3(12)\_F02 at the bottom right.
+
+**Figure 2 – Channel change filtered reporting following channel start event**
+
+#### 7.1.3 Service navigation method
+
+The reporting of which method was used to change channel may be configured.
+
+#### 7.1.4 Control device
+
+The reporting of which device was used to change channel may be configured.
+
+### 7.2 Linear TV metadata
+
+The notation used in Tables 1 to 6 facilitates the specification of the corresponding schema:
+
+- *Support*: 1 = mandatory (one instance), 0-1 = optional (maximum 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
+
+In the following tables containing data structures, an alternative representation may be shown which illustrates the data structure. In the event of discrepancy between an alternative representation and the table, the correct information is to be found in the table.
+
+Table 1 summarizes audience measurement elements for linear TV.
+
+**Table 1 – Audience measurement elements for linear TV**
+
+| Element           | Definition                                                                                                                                | Type | Notes or value domain                                          |
+|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------|------|----------------------------------------------------------------|
+| ServiceInstanceID | Identifies the instance of a specific service. Distinguishes among services when multiple services are displayed.                         |      | Defined in [ITU-T H.741.2]                                     |
+| ServiceIdentifier | Contains the "unique name for the service within the service provider's domain" (according to [ITU-T H.770]) which starts to be received. |      | NOTE – Defined in [ITU-T H.770] with the encoding in Figure 3. |
+
+**Table 1 – Audience measurement elements for linear TV**
+
+| Element             | Definition                                                                                                                                                              | Type                   | Notes or value domain                                                                                                                                                                                                                     |
+|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ChannelChangeFilter | Reports channel start and channel stop events only when the time following an event, without either subsequent event occurring, is greater than ChannelChangeFilter ms. | xs:integer             | Values: time in milliseconds, 0 means report all channel start and channel stop events.<br>NOTE – This sets the minimum time to report latency for channel start and channel stop events, to at least the specified time in milliseconds. |
+| ControlDevice       | Indicates the device type used to navigate to a channel.                                                                                                                |                        | Defined in [ITU-T H.741.2]                                                                                                                                                                                                                |
+| StartNavMethod      | Indicates the method used to navigate to a channel.                                                                                                                     | xs:integer enumeration | Values:<br>0 = up/down arrow,<br>1 = channel surfing,<br>2 = scheduled channel change,<br>3 = EPG,<br>4 = Last (previous),<br>5 = Favourite,<br>6 = number entry,<br>7 = unknown,<br>8 = other                                            |
+| StopNavMethod       | Indicates the method used to navigate away from a channel.                                                                                                              | xs:integer enumeration | Values:<br>0 = up/down arrow<br>1 = channel surfing<br>2 = scheduled channel change<br>3 = EPG<br>4 = Last (previous)<br>5 = Favourite<br>6 = number entry<br>7 = unknown<br>8 = other<br>999 = turn off terminal device                  |
+| ViewMode            | Identifies the viewing mode of the linear TV service which starts to be received.                                                                                       | xs:integer enumeration | 0 = unknown<br>1 = full screen<br>2 = Picture-in-Picture<br>3 = Mosaic<br>4 = Other                                                                                                                                                       |
+
+NOTE – The value of "unknown" for enumerated valued elements indicates that element information is not available; the value of "other" indicates that the element information is available but does not match one of the defined enumerated values.
+
+```
+
+<xsd:complexType name="IndividualServiceType">
+  <xsd:sequence>
+    <xsd:element name="ServiceIdentifier" type="H770IdType"/>
+    <xsd:element name="ServiceProviderIdentifier"
+      type="H770IdType" minOccurs="0"/>
+    <xsd:element name="AdditionalServiceDescriptionLocation"
+      type="anyURI" minOccurs="0"/>
+    <xsd:element name="LogicalChannelNumber"
+      type="xsd:positiveInteger" minOccurs="0"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+```
+
+**Figure 3 – XML encoding for ServiceIdentifier in linear TV audience measurement**
+
+ViewMode is an element to identify how the channel being received is rendered on the terminal device when started. The display modes are listed below:
+
+- Full screen (means that only the linear TV video is displayed, independent of the percentage of the display covered by the video).
+- Picture-in-picture (means a second service is displayed over a small part of the display of the main service. Sound is usually from the main service only).
+- Mosaic (in which many linear TV channels are received and displayed simultaneously in the same format as a matrix of small TV screens).
+- Other – includes presentation of video in other modes.
+
+Table 2 provides information regarding events which are specific to the linear service.
+
+**Table 2 – Types of linear TV events**
+
+| Event               | Definition                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Notes or value domain                                                                 |
+|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|
+| Linear ChannelStart | This event occurs when a user starts watching a TV channel or switches to another TV channel for which AM reporting is authorized by the user and configured to be reported about by the SP. It causes reporting of the ChannelStart data structure defined in Table 6.                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                                                       |
+| Linear ChannelStop  | This event occurs:<br>1) when a user stops watching a linear TV service without starting another linear TV service;<br>2) when a user switches to another channel for which reporting is forbidden by the user or is configured not to be reported about by the service provide (SP);<br>3) when the content of a specified class starts playing although it is forbidden to be measured by the user or configured not to be measured by the SP;<br>4) following restoration from a communications loss to indicate the time at which a channel was no longer being received;<br>5) when it causes reporting of the ChannelStop data structure defined in Table 6.<br>This event may also occur during channel change filtering. | NOTE – An example of case 5 is when an AM operation is restored following power-down. |
+
+When a measurement request includes LinearTVQualifier, and is configured with EventTrigger, then the events LinearChannelStart and LinearChannelStop are by default included in the events to be measured and reported, having the highest priority.
+
+The sample set identifiers in Table 3 are used to indicate elements to be reported when scheduled time sampling is used.
+
+**Table 3 – Sample set identifier for linear TV**
+
+| Sample set identifier | Description                                                                                         |
+|-----------------------|-----------------------------------------------------------------------------------------------------|
+| ChannelPlaying        | Indicates that the ChannelPlaying data structure defined in Table 6 is to be reported when sampled. |
+
+#### 7.2.1 Linear TV elements for "measurement request"
+
+The specific elements to be inserted in a measurement request data structure for linear TV service are specified in Table 4.
+
+**Table 4 – "LinearTVQualifier" extension to "measurement request" data structure**
+
+| Element               | Definition                                                                                                                                          | Support/<br>type             | Notes or value<br>domain                          |
+|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|---------------------------------------------------|
+| LinearTVQualifier     | This element indicates that LinearTV services are to be measured and is a container for the identification of the LinearTV services to be measured. | 0-1                          |                                                   |
+| NavMethod             | Element of LinearTVQualifier<br>Indicates that the navigation method is to be reported for channel start and channel stop events.                   | 0-1<br>Integer<br>enumerated | 0 = do not report<br>1 = report                   |
+| ControlDevice         | Element of LinearTVQualifier<br>Indicates that the device type used for channel navigation is to be reported.                                       | 0-1                          | Defined as<br>ControlDevice in<br>[ITU-T H.741.2] |
+| ViewMode              | Element of LinearTVQualifier<br>Indicates that the ViewMode is to be reported for channel start events.                                             | 0-1<br>Integer<br>enumerated | 0 = do not report<br>1 = report                   |
+| Obscuration           | Element of LinearTVQualifier<br>Indicates that the Obscuration is to be reported for channel start events.                                          | 0-1<br>Integer<br>enumerated | 0 = do not report<br>1 = report                   |
+| ChannelQualifier      | Element of LinearTVQualifier<br>Container for channel qualification elements.                                                                       | 0-1                          |                                                   |
+| ChannelList           | Element of ChannelQualifier<br>List of channel IDs (service identifiers) to be measured.                                                            | 0-1<br>(Note)                |                                                   |
+| ServiceIdentifier     | Element of ChannelList.<br>This element identifies a specific LinearTV channel to be measured.                                                      | 1-*                          | Defined in Table 1                                |
+| AllChannelsExceptList | Element of ChannelQualifier<br>List of channel IDs (service identifiers) not to be measured.                                                        | 0-1<br>(Note)                |                                                   |
+| ServiceIdentifier     | Element of AllChannelsExceptList.<br>This element identifies a specific LinearTV channel not to be measured.                                        | 1-*                          | Defined in Table 1                                |
+
+**Table 4 – "LinearTVQualifier" extension to "measurement request" data structure**
+
+| Element                                                                                                                                                | Definition                                                                                                                                                                                           | Support/<br>type | Notes or value<br>domain |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------------------------|
+| ChannelChangeFilter                                                                                                                                    | Element of LinearTVQualifier<br>Only report channel start and channel stop events when the time following an event without either subsequent event occurring is greater than ChannelChangeFilter ms. | 0-1              | Defined in Table 1       |
+| NOTE – Either "ChannelList" or "AllChannelsExceptList" may be present, or neither of them. When neither of them is present, this means "all channels". |                                                                                                                                                                                                      |                  |                          |
+
+Figure 4 contains an alternative representation of the measurement request extension data structure.
+
+```
+
+LinearTVQualifier (0-1)
+| NavMethod (0-1)
+| ControlDevice (0-1)
+| ChannelQualifier (0-1)
+| | ChannelList (0-1)
+| | | ServiceIdentifier (1-*)
+| | AllChannelsExceptList (0-1)
+| | | ServiceIdentifier (1-*)
+| ChannelChangeFilter (0-1)
+
+```
+
+**Figure 4 – Alternative representation of measurement request extension data structure**
+
+#### 7.2.2 Linear TV elements for "measurement request set"
+
+As some elements may be repeated in a number of measurement requests with the same value, a measurement request set is defined to provide an optimization mechanism to include default values for elements which have the same value in a number of measurement requests. Multiple measurement request sets may be present in a configuration package.
+
+There are four possible levels to set values:
+
+- Highest priority – configured in individual measurement request
+- Second level – default in measurement request
+- Third level – configured in measurement request set
+- Fourth level – default in measurement request set
+
+The values configured in each measurement request supersede those configured in Table 5.
+
+Figure 5 contains an alternative representation of the MeasurementRequestSet extension data structure.
+
+**Table 5 – Linear TV extension to "MeasurementRequestSet" data structure**
+
+| <b>Element</b>             | <b>Description</b>                                                                                                                                                                                         | <b>Support/<br/>type</b>        | <b>Notes or value domain</b>                |
+|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|---------------------------------------------|
+| MeasurementRequestSet      | This element is a container for a general default section containing elements with identical values for a set of measurement requests and the corresponding set of measurement requests.                   | 1-*                             | Defined in [ITU-T H.741.2]                  |
+| DefaultNavMethod           | Element of MeasurementRequest Set.<br>Indicates that the navigation method is to be reported for channel start and channel stop events.                                                                    | 0-1<br>Default=0                | Defined as NavMethod in Table 4             |
+| DefaultControlDevice       | Element of MeasurementRequest Set.<br>Indicates the device type used to navigate to a service.                                                                                                             | 0-1<br>Default=0                | Defined as ControlDevice in [ITU-T H.741.2] |
+| DefaultViewMode            | Element of MeasurementRequest Set.<br>Indicates that the ViewMode is to be reported for channel start events.                                                                                              | 0-1<br>Default=0                | Defined as ViewMode in Table 1              |
+| DefaultObscuration         | Element of MeasurementRequest Set.<br>Indicates that the Obscuration is to be reported for channel start events.                                                                                           | 0-1<br>Default=0                | Defined as Obscuration in Table 4           |
+| DefaultChannelQualifier    | Element of MeasurementRequest Set.<br>Container for channel qualification elements.                                                                                                                        | 0-1<br>Default=<br>All channels | Defined as ChannelQualifier in Table 4      |
+| DefaultChannelChangeFilter | Element of MeasurementRequest Set.<br>Only report channel start and channel stop events when the time following an event without either subsequent event occurring is greater than ChannelChangeFilter ms. | 0-1<br>Default:0                | Defined as ChannelChangeFilter in Table 1   |
+
+```
+
+MeasurementRequestSet
+| DefaultNavMethod
+| DefaultControlDevice
+| DefaultViewMode
+| DefaultObscuration
+| DefaultChannelQualifier
+| DefaultChannelChangeFilter
+
+```
+
+**Figure 5 – Alternative representation of MeasurementRequestSet extension data structure**
+
+#### 7.2.3 Linear TV elements for "audience measurement report package"
+
+NOTE – The measurement report header already contains the report creation time.
+
+The data structure in Table 6 is part of the data structure for the audience measurement report package of [ITU-T H.741.0]. Multiple elements which are associated with a single trigger time may be included in a particular instance of MeasurementReport.
+
+Figure 6 contains an alternative representation of the Measurement Report extension data structure.
+
+**Table 6 – Linear TV extension to "MeasurementReport" data structure**
+
+| Element                    | Description                                                                                                                                                                    | Support/type | Notes or value domain                                                                                                                                    |
+|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Measurement Report         | Element of AMReportPackage. Container for a measurement report.                                                                                                                | 1-*          | Defined in [ITU-T H.741.2]                                                                                                                               |
+| ChannelStart               | Element of MeasurementReport Indicates that a channel start event has taken place.                                                                                             | 0-1          |                                                                                                                                                          |
+| ControlDevice              | Element of ChannelStart Indicates the device type used to navigate to a channel.                                                                                               | 0-1          | Defined in Table 1                                                                                                                                       |
+| StartNavMethod             | Element of ChannelStart Indicates the method used to navigate to a channel.                                                                                                    | 0-1          | Defined in Table 1                                                                                                                                       |
+| PreviousService InstanceID | Element of ChannelStart Identifies the instance of the previous specific service.                                                                                              | 0-1          | Defined as ServiceInstanceID in Table 1<br>Reported when ChannelStart follows a ChannelStart.<br>Not reported when a ChannelStart follows a ChannelStop. |
+| ServiceInstanceID          | Element of ChannelStart Identifies the instance of the current specific service.                                                                                               | 1            | Defined in Table 1                                                                                                                                       |
+| ServiceIdentifier          | Element of ChannelStart This element contains the "unique name for the service within the service provider's domain" (according to [ITU-T H.770]) which starts to be received. | 1            | Defined in Table 1                                                                                                                                       |
+
+**Table 6 – Linear TV extension to "MeasurementReport" data structure**
+
+| Element           | Description                                                                                                                                                                         | Support/type | Notes or value domain                                                                           |
+|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-------------------------------------------------------------------------------------------------|
+| ViewMode          | Element of ChannelStart<br>Identifies the viewing mode of the linear TV service which starts to be received.                                                                        | 0-1          | Defined in Table 1                                                                              |
+| Obscuration       | Element of ChannelStart<br>Indicates the percentage of image obscured.                                                                                                              | 0-1          | Defined in [ITU-T H.741.2]                                                                      |
+| ChannelStop       | Element of MeasurementReport<br>It indicates that a channel stop event has taken place.                                                                                             | 0-1          |                                                                                                 |
+| ControlDevice     | Element of ChannelStop<br>Indicates the device type used to navigate to a channel.                                                                                                  | 0-1          | Defined in Table 1                                                                              |
+| StopNavMethod     | Element of ChannelStop<br>Indicates the method used to navigate away from a channel.                                                                                                | 0-1          | Defined in Table 1                                                                              |
+| ServiceInstanceID | Element of ChannelStop<br>Identifies the instance of a specific service.                                                                                                            | 1            | Defined in Table 1                                                                              |
+| ChannelPlaying    | Element of MeasurementReport<br>Container for channel(s) playing information.                                                                                                       | 0-*          | NOTE – This element is activated by configuring sample set identifier ChannelPlaying of Table 3 |
+| ServiceIdentifier | Element of ChannelPlaying<br>This element contains the "unique name for the service within the service provider's domain" (according to [ITU-T H.770]) which starts to be received. | 1            | Defined in Table 1                                                                              |
+| ServiceInstanceID | Element of ServiceIdentifier<br>Identifies the instance of a specific service.                                                                                                      | 1            | Defined in Table 1                                                                              |
+
+```
+
+MeasurementReport (1-*)
+| ChannelStart (0-1)
+| | ControlDevice (0-1)
+| | StartNavMethod (0-1)
+| | PreviousServiceInstanceID (0-1)
+| | ServiceInstanceID (1)
+| | ServiceIdentifier (1)
+| | ViewMode (0-1)
+| | Obscuration (0-1)
+| ChannelStop (0-1)
+| | ControlDevice (0-1)
+| | StopNavMethod (0-1)
+| | ServiceInstanceID (1)
+| ChannelPlaying (0-*)
+| | ServiceIdentifier (0-1)
+| | | ServiceInstanceID (1)
+
+```
+
+**Figure 6 – Alternative representation of MeasurementReport extension data structure**
+
+## Appendix I
+
+### Implementation considerations
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### I.1 Considerations regarding the enabling of control device reporting
+
+Conditions that may lead to this reporting option being enabled include:
+
+- 1) When a stakeholder wants information regarding the control devices used by an audience; for example,
+  - a) to understand the statistical distribution of control devices used in order to guide product investments;
+  - b) to combine with other information. For example:
+    - i) to combine control device information with display device information to provide a count of tablets in use to control HD TVs.
+    - ii) to combine with navigation methods to obtain a better end-user signature.
+
+### I.2 Considerations regarding the enabling of navigation method reporting
+
+Conditions that may lead to this reporting option being enabled include the following:
+
+- 1) If a client application is deployed to distinguish between end users based upon behavioural usage patterns, then information provided by reporting navigation methods may improve the application's ability to distinguish among end users.
+  - a) If the client application receives AM reports, then it is recommended that this reporting be enabled.
+  - b) If the client application uses an API to communicate with the AMF, then it may not be necessary to enable this reporting.
+- 2) If a server application is deployed to distinguish between end users based upon behavioural usage patterns, then information provided by reporting navigation methods may improve the application's ability to distinguish among end users. If the server application is part of the aggregation functions, or has an API to communicate with aggregation functions, then it may be advisable to enable this reporting.
+
+### I.3 Considerations for specifying channels to be measured
+
+There are three methods for specifying channels to be measured: specification by inclusion, specification by exclusion, or measurement of all channels (default).
+
+Channel specification by inclusion. Conditions that may lead to this method being selected include:
+
+- 1) Not all channels are desired to be measured.
+- 2) The list of channels to be measured is smaller than the list of channels not to be measured.
+
+Channel specification by exclusion. Conditions that may lead to this method being selected include:
+
+- 1) Not all channels are desired to be measured.
+- 2) The list of channels to be measured is larger than the list of channels not to be measured.
+
+### **I.4 Considerations for using channel change filtering and how to choose the value**
+
+In order to reduce bandwidth and processing, the channel change filter prevents channel change reports when channels are frequently changed, for example, as occurs during sequential up-arrow channel changing. If reporting of transitional channels to a final channel is not desired, then it is recommended that channel change filtering be used. Conditions that may help choose the filter period include:
+
+- 1) sufficient time to allow a button push;
+- 2) Insufficient time for an end user to get a meaningful impression of the content, i.e., it is too short a viewing period to be considered "watching".
+
+## Appendix II
+
+### Examples of configuration and reporting of the terminal device audience measurement function
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### II.I Configuration example
+
+Assuming the following example requirements:
+
+- 1) General
+  - a) An external permission mode with permission level 3
+  - b) The configuration package is to become effective immediately
+  - c) All reports are to be sent to the same address
+  - d) Re-transmission of up to five additional times following transport non-acknowledgement from aggregation functions.
+- 2) For most linear channels:
+  - a) Measure all channels except Channels 50, 53, 58 and 60. Do not measure religious content.
+  - b) Events to be measured and reported include:
+    - i) channel change events
+    - ii) only channel start and channel stop events when the time following an event without either subsequent event occurring is greater than two seconds
+    - iii) the following with the channel start event:
+      - (1) channel identifier
+      - (2) channel change (navigation) method
+      - (3) viewing mode (e.g., full screen, picture-in-picture)
+      - (4) content identifier
+      - (5) event time
+    - iv) the following with the channel stop event
+      - (1) event time
+  - c) Information to be frequently sampled and reported, include:
+    - i) channel identifier
+    - ii) content identifier info
+    - iii) sample times
+  - d) Measurement times
+    - i) Always
+  - e) Reporting
+    - i) Report batches of events within 60 seconds of any event
+    - ii) Measurements will be stored if the AMF is unable to send reports
+- 3) For specific linear channels:
+  - a) Collect both events and samples for Channels 50, 53, 58 and 60. Do not measure religious content.
+  - b) Events to be measured and reported include:
+
+- i) Channel change events
+- ii) Report only channel start and channel stop events when the time following an event without either subsequent event occurring is greater than two seconds
+- iii) Report the following with the channel start event:
+  - (1) channel identifier
+  - (2) channel change (navigation) method
+  - (3) viewing mode (e.g., full screen, picture-in-picture)
+  - (4) content identifier
+  - (5) event time
+- iv) Report the following with the channel stop event:
+  - (1) event time
+- c) Measurement times:
+  - i) Always.
+  - ii) Time sampling every five minutes.
+  - iii) Ignore the sample if its value is the same as the previous sample's value.
+- d) Reporting:
+  - i) Upon demand by aggregation functions
+  - ii) Measurements will be stored if the AMF is unable to send reports
+  - iii) Samples will be stored with lower priority than events
+
+The example solution in Figure II.1 shows values assigned to the configuration package data structure to meet the above requirements. Relevant defaults are shown in grey; it is not required that they be explicitly included in the configuration.
+
+```
+
+AMFConfigPackage (1)
+  PackageID (1) = 2345
+  @PackageVersion (0-1) = 2
+  EffectivityDateAndTime (0-1) = immediately
+  MeasurementRequestSet (1-*)
+    DefaultDeliveryAddress (0-*) = http://defaultdeliveryaddress.com
+    DefaultRetransmitNumber (0-1) = 5
+    MeasurementRequest (1-*)
+      MeasurementRequestID (1) = 1
+      LinearTVQualifier (0-1)
+        NavMethod (0-1) = 1 (report)
+        ControlDevice = 0 (do not report)
+        ChannelQualifier (0-1)
+          AllChannelsExceptList (0-1)
+            ServiceIdentifier (1-*) = "channel50"
+            ServiceIdentifier (1-*) = "channel53"
+            ServiceIdentifier (1-*) = "channel58"
+            ServiceIdentifier (1-*) = "channel60"
+          ChannelChangeFilter (0-1) = 2000
+
+```
+
+```
+
+AllContentClassExceptList (0-1)
+  ContentClassDomain (1-*) = "TV-Anytime"
+  ContentClassID (1-*) = "Religious"
+MeasurementSchedule (1-*)
+  MeasurementPeriod (0-*)
+    DayOfTheWeek (0-*) = 0 (everyday)
+    StartTime (0-*) = 00:00:00.00
+    EndTime (0-*) = 23:59:59.99
+  EventTrigger (0-*)
+  TimeTrigger (0-1)
+  SampleSet (0-*)
+    @SampleSetIdentifier (1) = ChannelPlaying
+    Periodicity (1) = 300
+    Priority (0-1) = 1
+    NothingNewReportMode (0-1) = 2 (create a complete AM sample)
+MeasurementDeliverySchedule (0-1)
+  ImmediatePush (0-1)
+    MeasurementReportNumberByPush (0-1) = 3
+    MaxTimeBetweenDelivery (0-1) = 60
+MeasurementRequest (1-*)
+  MeasurementRequestID (1) = 2
+  LinearTVQualifier (0-1)
+    NavMethod (0-1) = 1
+    ControlDevice = 0 (do not report)
+    ChannelQualifier (0-1)
+      ChannelList (0-1)
+        ServiceIdentifier (1-*) = "channel50"
+        ServiceIdentifier (1-*) = "channel53"
+        ServiceIdentifier (1-*) = "channel58"
+        ServiceIdentifier (1-*) = "channel60"
+    ChannelChangeFilter (0-1) = 2000
+AllContentClassExceptList (0-1)
+  ContentClassDomain (1-*) = "TV-Anytime"
+  ContentClassID (1-*) = "Religious"
+MeasurementSchedule (1-*)
+  MeasurementPeriod (0-*)
+    DayOfTheWeek (0-*) = 0 (everyday)
+    StartTime (0-*) = 00:00:00.00
+    EndTime (0-*) = 23:59:59.99
+
+```
+
+```
+
+EventTrigger (0-*)
+MeasurementDeliverySchedule (0-1)
+StorageCongestionPolicy (0-1) = 1 (drop sufficient)
+Pull (0-1)
+
+```
+
+**Figure II.1 – Example of an AMF configuration package**
+
+NOTE 1 – Sample times and event times – MeasurementReportTriggerTime is used to report the time that an event occurs or an element is sampled. No additional configuration for this is needed.
+
+NOTE 2 – Content ID info could be derived from content source and time for LinearTV.
+
+### II.2 Example measurement reports associated with example configuration of Figure II.1
+
+Given the example configuration of Figure II.1, example end-user behaviours are assumed which, together with the configuration, result in a series of measurement reports being delivered.
+
+![Figure II.2: Example of end-user behaviours and measurement reports. The diagram shows two measurement requests (MR 1 and MR 2) over a timeline from 1:58 to 21:59. MR 1 is for all channels except 50, 53, 58, and 60 with immediate delivery. MR 2 is for channels 50, 53, 58, and 60 with pull delivery. Behaviours include channel starts and stops for Ch48, Ch49, Ch50, Ch53, Ch54, and Ch60, corresponding to service periods A, B, C, and D. Report packages (1) through (6) are shown being delivered, with (1)-(3) being immediate reports and (4)-(6) being pulled reports. A 'Pulled report H.741.3(12)_FII.2' is also indicated.](392a79ccd95e682ccd08f35ab2e64144_img.jpg)
+
+Figure II.2: Example of end-user behaviours and measurement reports. The diagram shows two measurement requests (MR 1 and MR 2) over a timeline from 1:58 to 21:59. MR 1 is for all channels except 50, 53, 58, and 60 with immediate delivery. MR 2 is for channels 50, 53, 58, and 60 with pull delivery. Behaviours include channel starts and stops for Ch48, Ch49, Ch50, Ch53, Ch54, and Ch60, corresponding to service periods A, B, C, and D. Report packages (1) through (6) are shown being delivered, with (1)-(3) being immediate reports and (4)-(6) being pulled reports. A 'Pulled report H.741.3(12)\_FII.2' is also indicated.
+
+**Figure II.2 – Example of end-user behaviours and measurement reports**
+
+It is assumed that the navigation method used is the remote control up/down arrow. All reports of measurement request 1 are delayed by up to one minute to allow for aggregation. All reports of both measurement requests will be delayed by at least two seconds (channel change filter time). Religious programmes are considered restricted and measurements regarding them are not to be reported. Channel 49 is assumed to be playing only religious programmes during this example. This example shows how sampling ChannelPlaying in real-time may prevent long report latency.
+
+Six reports packages indicated in Figure II.1 are delivered as follows:
+
+- 1) Per measurement request 1, at 0158 hours the first measurement of channel start event on Ch48 for service period A is taken and delivered immediately after a one-minute delay, with the T0 sample value of ChannelPlaying as report package (1). The service is subsequently sampled every five minutes, including ChannelPlaying, and it generates a sequence of similar report packages (2) with timestamps from 0158 hours to 0428 hours.
+- 2) Per measurement request 1, at 0432 hours the channel is changed to Ch49, which is showing restricted content; this is reported as a channel stop event in report package (3) and delivered immediately after a one-minute delay. The new service is not measured.
+
+- 3) Per measurement request 2, at 0905 hours the channel is changed to Ch50, which is showing non-restricted content, and the channel start is measured and stored.
+- 4) Per channel change filtering in both measurement requests 1 and 2, after being tuned to Ch50, the up arrow is pressed three times every 0.5 seconds to get to Ch53, which is showing non-restricted content, at 11:15:00.0 to Ch51, at 11:15:00.5 to Ch52, and at 11:15:01.0 to Ch53. Per Figure 2 in clause 7.1.2, a ChannelStop report is generated for Ch50 at 11:15:00.5. A ChannelStart report is generated for Ch53 at 11:15:01.0. Both reports are stored for later delivery.
+- 5) Per measurement request 1, at 1705 hours the channel is changed to Ch54, which is showing non-restricted content, and delivered immediately after a one-minute delay, with the T0 sample value of ChannelPlaying, as report package (4). ChannelPlaying is subsequently sampled every five minutes and it generates a sequence of similar report packages (5) with timestamps from 1705 hours through 2155 hours.
+- 6) At 2000 hours, aggregation functions pull the report package (6), which contains the previously stored channel start measurements from 0905 hours and 1115 hours.
+- 7) At 2159 hours, the device is powered down and a channel stop report is stored. It will be delivered when the device is powered up, which may cause long reporting latency. The use of time sampling reported the check-pointed ChannelPlaying values in real-time (6).
+
+The contents of the six example AM report packages are as follows.
+
+AM report package (1) is delayed one minute after service start of service period A, due to ChannelStart event and ChannelPlaying T0 sample value change (see Figure II.3).
+
+```
+AMReportPackage (1)
+| SubscriberID (0-1) = "WorldspGold012345678"
+| TerminalDeviceID (1) = 6233446
+| MeasurementReport (1-*)
+| | MeasurementRequestID (1) = 1
+| | MeasurementReportTriggerTime (1) = 01:58:00.0
+| | ChannelStart (0-1)
+| | | StartNavMethod (0-1) = 0 (up/down arrow)
+| | | ServiceInstanceID (1) = 1
+| | | ServiceIdentifier (1) = "Channel48"
+| | | ViewMode (0-1) = 1 (fullscreen)
+| MeasurementReport (1-*)
+| | MeasurementRequestID (1) = 2
+| | MeasurementReportTriggerTime (1) = 01:58:00.0
+| | ChannelPlaying (0-*)
+| | | ServiceIdentifier (0-1) = "Channel48"
+| | | | ServiceInstanceID (1) = 1
+```
+
+**Figure II.3 – Example report package 1**
+
+The series of similar AM report packages (2) is delayed one minute after each sample time from 0158 hours to 0428 hours (see Figure II.4).
+
+```
+
+AMReportPackage (1)
+| SubscriberID (0-1) = "WorldspGold012345678"
+| TerminalDeviceID (1) = 6233446
+| MeasurementReport (1-*)
+| | MeasurementRequestID (1) = 1
+| | MeasurementReportTriggerTime (1) = 01:58:00.0 to 4.28:00.0
+| | ChannelPlaying (0-*)
+| | | ServiceIdentifier (0-1) = "Channel148"
+| | | | ServiceInstanceID (1) = 1
+
+```
+
+**Figure II.4 – Example report package 2**
+
+AM report package (3) is delayed one minute after service stop of service period A (see Figure II.5).
+
+```
+
+AMReportPackage (1)
+| SubscriberID (0-1) = "WorldspGold012345678"
+| TerminalDeviceID (1) = 6233446
+| MeasurementReport (1-*)
+| | MeasurementRequestID (1) = 1
+| | MeasurementReportTriggerTime (1) = 04:32:00
+| | ChannelStop (0-1)
+| | | StopNavMethod (0-1) = 0
+| | | ServiceInstanceID (1) = 1
+
+```
+
+**Figure II.5 – Example report package 3**
+
+AM report package (4) is delayed one minute after service start of service period D, due to ChannelStart event and ServiceIdentifier T0 sample value change (see Figure II.6).
+
+```
+
+AMReportPackage (1)
+| SubscriberID (0-1) = WorldspGold012345678
+| TerminalDeviceID (1) = 6233446
+| MeasurementReport (1-*)
+| | MeasurementRequestID (1) = 1
+| | MeasurementReportTriggerTime (1) = 17:05:00.0
+| | ChannelStart (0-1)
+| | | StartNavMethod (0-1) = 0 (up/down arrow)
+| | | PreviousServiceInstanceID = 3
+| | | ServiceInstanceID (1) = 4
+| | | ServiceIdentifier (1) = "Channel54"
+| | | ViewMode (0-1) = 1 (fullscreen)
+| MeasurementReport (1-*)
+| | MeasurementRequestID (1) = 1
+| | MeasurementReportTriggerTime (1) = 17:05:00.0
+| | ChannelPlaying (0-*)
+| | | ServiceIdentifier (0-1) = "Channel54"
+| | | | ServiceInstanceID (1) = 4
+
+```
+
+**Figure II.6 – Example report package 4**
+
+The series of similar AM report packages (5) is delayed one minute after each sample time from 1710 hours to 2155 hours (see Figure II.7).
+
+```
+
+AMReportPackage (1)
+| SubscriberID (0-1) = "WorldspGold012345678"
+| TerminalDeviceID (1) = 6233446
+| MeasurementReport (1-*)
+| | MeasurementRequestID (1) = 1
+| | MeasurementReportTriggerTime (1) = 17:10:00.0 to 21:55:00.0
+| | ChannelPlaying (0-*)
+| | | ServiceIdentifier (0-1) = "Channel54"
+| | | | ServiceInstanceID (1) = 4
+
+```
+
+**Figure II.7 – Example Report Package 5**
+
+AM report package (6) that is pulled at 20:00 hours includes stored measurements from 0905 hours and 1115 hours (see Figure II.8).
+
+```
+
+AMReportPackage (1)
+| SubscriberID (0-1) = "WorldspGold012345678"
+| TerminalDeviceID (1) = 6233446
+| MeasurementReport (1-*)
+| | MeasurementRequestID (1) = 2
+| | MeasurementReportTriggerTime (1) = 09:05:00.0
+| | ChannelStart (0-1)
+| | | StartNavMethod (0-1) = 0 (up/down arrow)
+| | | ServiceInstanceID (1) = 2
+| | | ServiceIdentifier (1) = "Channel50"
+| | | ViewMode (0-1) = 1 (fullscreen)
+| MeasurementReport (1-*)
+| | MeasurementRequestID (1) = 2
+| | MeasurementReportTriggerTime (1) = 11:15:00.5
+| | ChannelStop (0-1)
+| | | StopNavMethod (0-1) = 0 (up/down arrow)
+| | | ServiceInstanceID (1) = 2
+| MeasurementReport (1-*)
+| | MeasurementRequestID (1) = 2
+| | MeasurementReportTriggerTime (1) = 11:15:01.0
+| | ChannelStart (0-1)
+| | | StartNavMethod (0-1) = 0 (up/down arrow)
+| | | ServiceInstanceID (1) = 3
+| | | ServiceIdentifier (1) = "Channel53"
+| | | ViewMode (0-1) = 1 (fullscreen)
+
+```
+
+**Figure II.8 – Example report package 6**
+
+NOTE – If the remote control's up-arrow had been held down instead of being pushed three times, then StopNavMethod and StartNavMethod would have indicated channel surfing for the second and third measurement reports above. The switch time between channels would be determined by the IPTV system.
+
+### II.3 Picture-in-picture (PIP) example
+
+Assume the configuration package in Figure II.9.
+
+```
+
+AMFConfigPackage (1)
+  PackageID (1) = 9345
+  @PackageVersion (0-1) = 2
+  EffectivityDateAndTime (0-1) = immediately
+  MeasurementRequestSet (1-*)
+    DefaultDeliveryAddress (0-*) = http://defaultdeliveryaddress.com
+    DefaultRetransmitNumber (0-1) = 5
+    DefaultControlDevice (0-1) = 0 (do not report)
+    DefaultViewMode (0-1) = 1 (report)
+    DefaultObscuration (0-1) = 1 (report)
+    MeasurementRequest (1-*)
+      MeasurementRequestID (1) = 1
+      LinearTVQualifier (0-1)
+        NavMethod (0-1) = 1 (report)
+        ChannelQualifier (0-1) (all channels)
+        ChannelChangeFilter (0-1) = 2000
+      AllContentClassExceptList (0-1) (not filtered by content)
+      MeasurementSchedule (1-*)
+        MeasurementPeriod (0-*)
+          DayOfTheWeek (0-*) = 0 (everyday)
+          StartTime (0-*) = 00:00:00.00
+          EndTime (0-*) = 23:59:59.99
+        EventTrigger (0-*)
+          Event (0-*) = VideoResize
+          Event (0-*) = VideoObscure
+          Event (0-*) = AudioVolume
+        MeasurementDeliverySchedule (0-1)
+          ImmediatePush (0-1)
+          MeasurementReportNumberByPush (0-1) = 1
+
+```
+
+**Figure II.9 – PIP example configuration package**
+
+The operation of PIP, including swapping the sub-picture and main picture, and resizing and moving the sub-picture, varies depending upon the implementation. In this example, it is assumed: that a new sub-picture is added at one-fourth screen size and muted, that the larger picture generates audio, that a swap operation is available, and that any PIP dialogue shown on the screen is ignored for simplicity.
+
+Then the following end-user behaviours would result in AM report generation of three immediate reports.
+
+![Figure II.10: PIP example of end-user behaviours and measurement reports. The diagram shows a timeline for 'Configuration MR 1' labeled 'All channels, all day measurement schedule, immediate delivery'. Below the timeline, 'Behaviours' are marked with three events: 1) At 3:32, 'Linear channel start (Ch51)' occurs, starting 'Service period A'. 2) At 9:05, 'Linear channel PIP start (Ch50)' occurs, starting 'Service period B'. 3) At 13:55, 'Linear channel PIP swap (Ch50, Ch51)' occurs. Below the timeline, 'Report packages' (1), (2), and (3) are shown being delivered. Package (1) is delayed from the 3:32 event. Packages (2) and (3) are labeled as 'Immediate reports'.](692541e65db4dc852988ce77ebb60ce5_img.jpg)
+
+Figure II.10: PIP example of end-user behaviours and measurement reports. The diagram shows a timeline for 'Configuration MR 1' labeled 'All channels, all day measurement schedule, immediate delivery'. Below the timeline, 'Behaviours' are marked with three events: 1) At 3:32, 'Linear channel start (Ch51)' occurs, starting 'Service period A'. 2) At 9:05, 'Linear channel PIP start (Ch50)' occurs, starting 'Service period B'. 3) At 13:55, 'Linear channel PIP swap (Ch50, Ch51)' occurs. Below the timeline, 'Report packages' (1), (2), and (3) are shown being delivered. Package (1) is delayed from the 3:32 event. Packages (2) and (3) are labeled as 'Immediate reports'.
+
+**Figure II.10 – PIP example of end-user behaviours and measurement reports**
+
+Three reports packages indicated in Figure II.2 are delivered as follows, per measurement request 1:
+
+- 1) At 0332 hours, the first measurement of a channel start event on channel Ch51 is taken and delivered two seconds later due to channel change filtering, as report package (1).
+- 2) At 0905 hours, a second channel Ch50 started in PIP is measured with an auto-muted event, obscuring one-quarter of the screen of display Ch51. Measurements are delivered two seconds later due to channel change filtering, as report package (2).
+- 3) At 1355 hours, an end user causes a swap of the sub-picture Ch50, with the main picture Ch51, causing video resize and video obscure events for both channels, and an audio focus event. Measurements are delivered immediately as report package (3).
+
+The contents of the three example AM report packages are as follows:
+
+The AM report package (1) is delayed two seconds after service start of service period A, due to ChannelStart event (see Figure II.11).
+
+```
+AMReportPackage (1)
+| SubscriberID (0-1) = "WorldspGold012345678"
+| TerminalDeviceID (1) = 6233446
+| MeasurementReport (1-*)
+| | MeasurementRequestID (1) = 1
+| | MeasurementReportTriggerTime (1) = 03:32:00.0
+| | ChannelStart (0-1)
+| | | StartNavMethod (0-1) = 0 (up/down arrow)
+| | | ServiceInstanceID (1) = 1
+| | | ServiceIdentifier (1) = "Channel51"
+| | | ViewMode (0-1) = 1 (fullscreen)
+| | | Obscuration (0-1) = 0.0 (not obscured)
+```
+
+**Figure II.11 – PIP example report package 1**
+
+AM report package (2) is delayed two seconds after service start of service period A, due to ChannelStart event (see Figure II.12).
+
+```
+
+AMReportPackage (1)
+| SubscriberID (0-1) = "WorldspGold012345678"
+| TerminalDeviceID (1) = 6233446
+| MeasurementReport (1-*)
+| | MeasurementRequestID (1) = 1
+| | MeasurementReportTriggerTime (1) = 09:05:00.0
+| | ChannelStart (0-1)
+| | | StartNavMethod (0-1) = 8 (other)
+| | | PreviousServiceInstanceID (0-1) = 1
+| | | ServiceInstanceID (1) = 2
+| | | ServiceIdentifier (1) = "Channel50"
+| | | ViewMode (0-1) = 2 (Picture-in-Picture)
+| | | Obscuration (0-1) = 0.0 (not obscured)
+| | AudioVolume (0-1)
+| | | ServiceInstanceID (1) = 2 (associated with Ch50 service)
+| | | VolumeDirection (1) = "mute"
+| | VideoObscure (0-1)
+| | | ServiceInstanceID (1) = 1 (associated with Ch51 service)
+| | | Obscuration (1) = 0.25 (25% obscured)
+
+```
+
+**Figure II.12 – PIP example report package 2**
+
+AM report package (3) is delivered immediately after the PIP swap procedure (see Figure II.13).
+
+```
+
+AMReportPackage (1)
+| SubscriberID (0-1) = "WorldspGold012345678"
+| TerminalDeviceID (1) = 6233446
+| MeasurementReport (1-*)
+| | MeasurementRequestID (1) = 1
+| | MeasurementReportTriggerTime (1) = 13:55:00.0
+| | VideoObscure (0-1)
+| | | ServiceInstanceID (1) = 1 (associated with Ch51 service)
+| | | Obscuration (1) = 0.00 (0% obscured)
+| | VideoObscure (0-1)
+| | | ServiceInstanceID (1) = 2 (associated with Ch50 service)
+| | | Obscuration (1) = 0.25 (25% obscured)
+| | VideoResize (0-1)
+| | | ServiceInstanceID (1) = 1 (associated with Ch51 service)
+| | | ImageWidth (1) = 810
+| | | ImageHeight (1) = 540
+| | VideoResize (0-1)
+| | | ServiceInstanceID (1) = 2 (associated with Ch50 service)
+
+```
+
+```
+| | | ImageWidth (1) = 1920
+| | | ImageHeight (1) = 1080
+| | AudioFocus (0-1)
+| | | ServiceInstanceID (1) = 2 (associated with Ch50 service)
+| | | IPTVFocus (0-1) = true
+```
+
+**Figure II.13 – PIP example report package 3**
+
+## Appendix III
+
+### Audience measurement capability profiles
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Table III.1 lists the capabilities of the terminal device audience measurement function (TD-AMF).
+
+**Table III.1 – TD-AMF capability list**
+
+| Capability area        | Capability                  | References   |
+|------------------------|-----------------------------|--------------|
+| Measurement Triggers   | Event                       | Table 2      |
+|                        | Time sampling               | Table 3      |
+| Operational Management | Channels to be measured     | Clause 7.1.1 |
+|                        | Channel change filtering    | Clause 7.1.2 |
+|                        | Navigation method reporting | Clause 7.1.3 |
+|                        | Control device reporting    | Clause 7.1.4 |
+
+These capabilities are included in the capability data structure depicted in Table 2 of [ITU-T H.741.2].
+
+A set of AM capability profiles as a quick way to identify sub-sets 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, 2, or 3, etc., which would relate to a specific sub-set of capability options from Table III.1 and service-common capability options listed in an appendix of [ITU-T H.741.1]. The definition of such capability profiles is for further study.
+
+## 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] Recommendation ITU-T H.740 (2010), *Application event handling 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 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.*
+
+
+
+## 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.4-201206-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.741.4-201206-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dad02182b30e94f721c7f50726f60641c96df521
--- /dev/null
+++ b/marked/H/T-REC-H.741.4-201206-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:45bf920a7798c0111eed0c87f3f277105f8935167814eaedd42f96a3f983bba0
+size 4024
diff --git a/marked/H/T-REC-H.741.4-201206-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg b/marked/H/T-REC-H.741.4-201206-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0366f28e31905f2e73f2aec259e5c3912299aace
--- /dev/null
+++ b/marked/H/T-REC-H.741.4-201206-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f26fe88ffbc7cec8ece50a886365d08fb0f42924fc0126a78773dce3be3330d5
+size 4326
diff --git a/marked/H/T-REC-H.741.4-201206-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/H/T-REC-H.741.4-201206-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a70b6de292476b2f313df6d9499006038a9b18b8
--- /dev/null
+++ b/marked/H/T-REC-H.741.4-201206-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aaca926dda6d03e616b1e7855caad3e52e9afa4309b66d94d1263b7cedf1888e
+size 3099
diff --git a/marked/H/T-REC-H.741.4-201206-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.741.4-201206-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7dcc714a23c412bf391ed532493561adc3f6c07e
--- /dev/null
+++ b/marked/H/T-REC-H.741.4-201206-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7e4213ffb0b312a95fbc1944aad4f59561a17daf1478b72a02e85cf63383875a
+size 6626
diff --git a/marked/H/T-REC-H.741.4-201206-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/H/T-REC-H.741.4-201206-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c8731fcca21a4c61b1d460e2d79e8f929a92ab96
--- /dev/null
+++ b/marked/H/T-REC-H.741.4-201206-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c79731a2a5ab01c0ba565a0c49acd87670a2a59043af4588f93909f343293bd9
+size 5650
diff --git a/marked/H/T-REC-H.741.4-201206-I_PDF-E/raw.md b/marked/H/T-REC-H.741.4-201206-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..e42c0dd0a14065f3518a27cd21ddd7576a00eef1
--- /dev/null
+++ b/marked/H/T-REC-H.741.4-201206-I_PDF-E/raw.md
@@ -0,0 +1,756 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.741.4**
+
+(06/2012)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+IPTV multimedia services and applications for IPTV –  
+IPTV application event handling
+
+---
+
+**IPTV application event handling: Transport  
+mechanisms for audience measurement**
+
+Recommendation ITU-T H.741.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, 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        |
+| <b>IPTV application event handling</b>                                        | <b>H.740–H.749</b> |
+| 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.4
+
+# **IPTV application event handling: Transport mechanisms for audience measurement**
+
+## **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.4 specifies the data elements and structures of the transport delivery-dependent XML and binary headers, used in audience measurement messages. Appendix I provides an analysis of AM to understand its transport protocol requirements.
+
+## **History**
+
+| Edition | Recommendation | Approval   | Study Group |
+|---------|----------------|------------|-------------|
+| 1.0     | ITU-T H.741.4  | 2012-06-29 | 16          |
+
+## **Keywords**
+
+Audience measurement, audience rating service, audience viewership, contents rating, data structures, distributed content service, elements, engagement metrics, end-user permission, interactive services, IPTV application event handling, linear TV, metadata, monitoring, personalized service, transport.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                                     | 2    |
+| 4 Abbreviations and acronyms .....                                                | 2    |
+| 5 Conventions .....                                                               | 3    |
+| 6 Messages for data structure delivery .....                                      | 4    |
+| 6.1 Elements used in delivery.....                                                | 5    |
+| 6.2 Delivery of the data structure "configuration package request" .....          | 13   |
+| 6.3 Delivery of the data structure "configuration package request response" ..... | 13   |
+| 6.4 Delivery of the data structure "AMF configuration package" .....              | 15   |
+| 6.5 Delivery of the data structure "Measurement report request" .....             | 17   |
+| 6.6 Delivery of the data structure "AM report package" .....                      | 19   |
+| 6.7 Delivery of the data structure "Ack" .....                                    | 19   |
+| 6.8 Delivery of the data structure "Error".....                                   | 20   |
+| Appendix I – Transport protocol considerations for audience measurement .....     | 21   |
+| I.1 AM message size characteristics .....                                         | 21   |
+| I.2 AM message reliability needs .....                                            | 22   |
+| I.3 AM message QoS needs.....                                                     | 23   |
+| I.4 AM message integrity needs .....                                              | 23   |
+| I.5 AM message encryption needs.....                                              | 23   |
+| Bibliography.....                                                                 | 24   |
+
+
+
+# Recommendation ITU-T H.741.4
+
+## **IPTV application event handling: Transport mechanisms for audience measurement**
+
+## **1 Scope**
+
+This Recommendation describes transport mechanisms for audience measurement (AM). It specifies how the data structures defined in [ITU-T H.741.2] and [ITU-T H.741.3] are exchanged over different transport protocols. The term 'transport protocol' as used in this Recommendation refers to the protocol in which AM messages are encapsulated for delivery to a remote device.
+
+## **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.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 X.1191] Recommendation ITU-T X.1191 (2009), *Functional requirements and architecture for IPTV security aspects.*
+
+## **3 Definitions**
+
+### **3.1 Terms defined elsewhere**
+
+This Recommendation uses the following terms defined elsewhere:
+
+- 3.1.1 aggregation functions** [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 measurement** [ITU-T H.741.0]: The measurement of people's engagement with IPTV services.
+
+**3.1.5 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.6 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.7 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.8 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. Following [ITU-T X.1191] Annex A.
+
+**3.1.9 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.10 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.11 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.12 multicast sub-addressing** [ITU-T H.741.1]: The use of elements in a multicast message to determine if the message is intended for the receiving TD-AMF.
+
+**3.1.13 service** [b-ITU-T Y.101]: A structure set of capabilities intended to support applications.
+
+**3.1.14 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.15 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.16 set-top box (STB)** [b-ITU-T J.183]: A hardware box that contains 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.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**
+
+This Recommendation does not define any particular term.
+
+## **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|     |                               |
+|-----|-------------------------------|
+| AM  | Audience Measurement          |
+| AMF | Audience Measurement Function |
+| BiM | Binary MPEG format for XML    |
+
+|        |                                               |
+|--------|-----------------------------------------------|
+| EXI    | Efficient XML Interchange                     |
+| GZIP   | GNU Zip                                       |
+| ID     | Identifier                                    |
+| MPEG   | Moving Picture Experts Group                  |
+| PC     | Personal Computer                             |
+| SP     | Service Provider                              |
+| STB    | Set-Top Box                                   |
+| TD-AMF | Terminal Device Audience Measurement Function |
+| TV     | Television                                    |
+| UTC    | Coordinated Universal Time                    |
+| XML    | Extensible Markup Language                    |
+| ZLIB   | Z LIBrary – A data compression library        |
+
+## 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 keyword "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 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'.](a234352dfaccdc24745c88eef7724cc6_img.jpg)
+
+A rounded rectangular box containing the word 'Functions'.
+
+The keywords "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'.](99bae07626f60f9ede10e2e387ef7051_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.
+
+In order to facilitate the specification of the corresponding schema, the notation used in tables defining elements and data structures is:
+
+- *Support*: 1 = mandatory (one instance), 0-1 = optional (maximum 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.
+
+Following tables containing data structures, an alternative representation may be shown which illustrates the data structure. In the event of discrepancy between an alternative representation and the table, the correct information is to be found in the table.
+
+## 6 Messages for data structure delivery
+
+The data structures defined in [ITU-T H.741.2] may be delivered by one of multiple transport protocols; they may all be delivered by unicast, and some may be delivered by multicast, as indicated in Table 1.
+
+Each of the three messages may be either unicast or multicast:
+
+- configuration request response message
+- configuration message
+- measurement report request message.
+
+When the message name is to be distinguished, the word unicast or multicast is prefixed to the above message names, e.g., multicast configuration message.
+
+**Table 1 – Delivery mechanisms for each data structure**
+
+| <b>Data structure</b>                  | <b>Unicast</b> | <b>Multicast</b> |
+|----------------------------------------|----------------|------------------|
+| Configuration package request          | X              |                  |
+| Configuration package request response | X              | X                |
+| Configuration package                  | X              | X                |
+| Measurement report request             | X              | X                |
+| AM report package                      | X              |                  |
+| Ack                                    | X              |                  |
+| Error                                  | X              |                  |
+
+This clause focuses on the differences between unicast and multicast for delivery over transport protocols that can carry only XML. It distinguishes between elements to be used for delivery over transport protocols which can carry only XML and those which can carry binary.
+
+All unicast and multicast messages have delivery elements which may be included in XML or a binary header, as depicted in Figure 1.
+
+![](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+|                           |             |
+|---------------------------|-------------|
+| Delivery dependent<br>XML | XML Payload |
+|---------------------------|-------------|
+
+AM message structure for XML-only transport protocols
+
+![](e9314c83043183351ed74908e9bf2f90_img.jpg)
+
+|               |             |
+|---------------|-------------|
+| Binary Header | XML Payload |
+|---------------|-------------|
+
+AM message structure for binary-capable transport protocols
+
+**Figure 1 – Structure of an AM message**
+
+Unicast and multicast delivery elements include:
+
+- A message type identifier to distinguish among AM messages.
+- A message expiration time after which the message is not accepted.
+- AM protocol version numbers to indicate interoperability and incompatibility.
+- A message identifier to support correlation among messages.
+
+In addition, multicast delivery elements include:
+
+- A message integrity check and signature for authentication.
+- An element to control acknowledge or error responses, so that problem AM messages may be reported.
+- Sub-addressing elements to qualify the intended target sub-set of TD-AMFs.
+
+The delivery elements of the uncompressed binary header may be used to determine if the XML payload is to be uncompressed and parsed.
+
+See clause 7.1.1 of [ITU-T H.741.1] for descriptions of the capabilities provided by these elements.
+
+### **6.1 Elements used in delivery**
+
+The details of delivery elements are specified in Table 2. The applicability of each element to XML-only or binary-capable transport protocols is indicated.
+
+**Table 2 – Elements used in delivery**
+
+| <b>Element</b>              | <b>Description</b>                                                                                                                                                                                                                                                                                                                                                                               | <b>Support/type</b>                                      | <b>Notes or value domain</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | <b>XML</b> | <b>Binary</b> |
+|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------|
+| MessageType                 | Indicates the AM message type                                                                                                                                                                                                                                                                                                                                                                    | xs:hexBinary<br>enumeration<br>length = 1 octet (8 bits) | Values: 0 = configuration request message, 1 = unicast configuration request response message, 2 = multicast configuration request response message, 3 = unicast configuration message, 4 = multicast configuration message, 5 = unicast measurement report request message, 6 = multicast measurement report request message, 7 = measurement report message, 8 = configuration ack message, 9 = error message                                                                                                                                                                                                                                          | X          | X             |
+| Protocol Version<br>MajorID | Indicates the major protocol version of this message.<br>Differences in major protocol versions indicate incompatibility where mandatory functions have changed so that an older version receiver would not be able to interoperate with a newer version source if it simply ignored the elements and attributes it did not understand and took the actions defined in the older recommendation. | xs:hexBinary<br>length = 1 octet (8 bits)                | NOTE 1 – The source sets the value of the protocol version to the highest version it supports. The version of this AM recommendation is 1.0.<br>NOTE 2 – When the sourced major version is not equal to the receiver's version, the message is not to be further processed by the receiver, and an error is to be returned.<br>NOTE 3 – When the major version identifier is equal to the receiver supported version it is to be processed. The receiver sets the value of the protocol version in the response message header to either the value supplied by the sender or the highest protocol version supported by the receiver, whichever is lower. | X          | X             |
+
+**Table 2 – Elements used in delivery**
+
+| <b>Element</b>           | <b>Description</b>                                                                                                                                                                                                                                                                                   | <b>Support/type</b>                              | <b>Notes or value domain</b>                                                                                                                                                                                                         | <b>XML</b> | <b>Binary</b> |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------|
+| Protocol Version MinorID | Indicates the minor protocol version of this message, generated by the source of the message. Differences in minor protocol versions indicate compatibility.<br>The minor version number is incremented only if significant new capabilities have been added to the AM protocol (e.g., new message). | xs:hexBinary<br>length = 1 octet (8 bits)        | NOTE – The sourced minor version is ignored by a receiver with a smaller minor version, but may be used to constrain use of certain capabilities by the entity with the larger minor version number (e.g., do not send new message). | X          | X             |
+| MessageID                | Message identifier.                                                                                                                                                                                                                                                                                  | xs:hexBinary<br>length = 8 octets (64 bits)      | Value: AM service provider unique. Uniquely generated by either TD-AMF or aggregation functions. Supports correlation of response to message being responded to.                                                                     | X          | X             |
+| Expiration Time          | Security element indicating the message expiration time.                                                                                                                                                                                                                                             | xs:dateTime                                      | NOTE – This is the time of message transmission plus recommended ten minutes. Specify an offset from the UTC time. Used to protect against replay attacks, see [ITU-T H.741.1] clause 9.                                             | X          |               |
+| Expiration Time          | Security element indicating the message expiration time.                                                                                                                                                                                                                                             | NTP 64-bit timestamp format<br>[b-IETF RFC 5905] | NOTE – This is the time of message transmission plus recommended 10 minutes. Specify an offset from the UTC time. Used to protect against replay attacks, see [ITU-T H.741.1] clause 9.                                              |            | X             |
+| Digest                   | Integrity check element covering all XML elements in a message.                                                                                                                                                                                                                                      | xs:hexBinary<br>length = 32 octets (256 bits)    | NOTE – The cryptographic hash function is SHA-256. See [b-FIPS PUB 180-3].                                                                                                                                                           | X          | X             |
+| Signature                | Security element indication of authentication.                                                                                                                                                                                                                                                       | xs:hexBinary<br>length = 128 octets (1024 bits)  | NOTE – The public-key cryptographic algorithm is RSA-1024. See [b-FIPS PUB 186-3].                                                                                                                                                   | X          | X             |
+
+**Table 2 – Elements used in delivery**
+
+| <b>Element</b>                 | <b>Description</b>                                                                                                                                                                                                                                                              | <b>Support/type</b>                                      | <b>Notes or value domain</b>                                                                                                                                                                      | <b>XML</b> | <b>Binary</b> |
+|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------|
+| Response Qualifier             | Qualifies which type(s) of special responses are requested.                                                                                                                                                                                                                     | xs:hexBinary<br>enumeration<br>length = 1 octet (8 bits) | Values:<br>0 = no acknowledge or error response requested,<br>1 = error message response requested only,<br>2 = both acknowledge and error messages requested,<br>3 = acknowledge requested only. | X          | X             |
+| Terminal DeviceTarget ListSize | Specifies the total size in octets of the following TerminalDeviceTarget fields.                                                                                                                                                                                                | 1<br>xs:hexBinary<br>length = 4 octet (32 bits)          |                                                                                                                                                                                                   |            | X             |
+| Terminal DeviceTarget          | Identifies a terminal device, target of this message, uniquely identifies an end user's terminal device based on hashing of the device's MAC address.                                                                                                                           | xs:hexBinary<br>length = 16 octets (128 bits)            | Using MD5 algorithm.<br>See [b-IETF RFC 6151].                                                                                                                                                    | X          | X             |
+| Lower Threshold                | It indicates the threshold to be used with the generation of a random number between 0 and 10000 by the TD-AMF to decide if the receiving terminal device accepts the configuration message (random number above lower threshold) or not (random number below lower threshold). | xs:hexBinary<br>length = 2 octet (16 bits)<br>Default: 0 |                                                                                                                                                                                                   | X          | X             |
+
+**Table 2 – Elements used in delivery**
+
+| <b>Element</b>             | <b>Description</b>                                                                                                                                                                                                                                                                   | <b>Support/type</b>                                                                          | <b>Notes or value domain</b>                                                                                                                                                                                 | <b>XML</b> | <b>Binary</b> |
+|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------|
+| Upper Threshold            | It indicates the threshold to be used with the generation of a random number between 0 and 10000 by the TD-AMF to decide if the receiving terminal device is to accept the configuration message (random number below upper threshold) or not (random number above upper threshold). | xs:hexBinary<br>length = 2 octet (16 bits)<br>Default: 10000                                 |                                                                                                                                                                                                              | X          | X             |
+| Terminal DeviceType Target | This element identifies a terminal device type, target of this message.                                                                                                                                                                                                              | nonEmptyString<br>Enumeration<br>Default: qualification by terminal device type is not used. | Values: STB, TV, mobile, PC, tablet, other.                                                                                                                                                                  | X          |               |
+| Terminal DeviceType Target | This element identifies a terminal device type, target of this message.                                                                                                                                                                                                              | 1<br>8 bits                                                                                  | Device types indicated by bit flag = 1.<br>Bit 7 = STB, Bit 6 = TV, Bit 5 = Mobile, Bit 4 = PC, Bit 3 = Tablet, Bit 2 = Other<br>Value = 0 indicates that qualification by terminal device type is not used. |            | X             |
+| UserInfo TargetListSize    | Specifies the total size in octets of the following UserInfoTypeSize, UserInfoTypeString, IgnoreIfUnavailable, EndUserValueSize and UserInfoValueString fields.                                                                                                                      | 1<br>xs:hexBinary<br>length = 4 octet (32 bits)                                              |                                                                                                                                                                                                              |            | X             |
+| UserInfoType Size          | Specifies the total size in octets of the following UserInfoTypeString field.                                                                                                                                                                                                        | xs:hexBinary<br>length = 1 octet (8 bits)                                                    |                                                                                                                                                                                                              |            | X             |
+| IgnoreIf Unavailable       | Element to indicate how to handle UserInfoTypeString when information about the specified type is unavailable.                                                                                                                                                                       | xs:hexBinary<br>length = 1 octet (8 bits)<br>default Bit 7=0                                 | Values: Bit 7 = 1 indicates ignore if unavailable.                                                                                                                                                           |            | X             |
+
+**Table 2 – Elements used in delivery**
+
+| <b>Element</b>       | <b>Description</b>                                                                                                                                                                      | <b>Support/type</b>                       | <b>Notes or value domain</b>                                                                                                                                                                                                                             | <b>XML</b> | <b>Binary</b> |
+|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------|
+| EndUser ValueSize    | Specifies the total size in octets of the following UserInfoValueString field.                                                                                                          | xs:hexBinary<br>length = 1 octet (8 bits) |                                                                                                                                                                                                                                                          |            | X             |
+| UserInfo Target      | Container for elements specifying user info to be used for targeting TD-AMFs.                                                                                                           |                                           |                                                                                                                                                                                                                                                          | X          |               |
+| UserInfoType String  | Element of UserInfoTarget<br>Element to match to ControlledUserInfo TypeString or GenericUserInfoType<br>A match indicates that User Info is used to identify a target of this message. | 1<br>nonEmptyString                       | ControlledUserInfoTypeString and GenericUserInfoType are defined in Table 3 of [ITU-T H.741.2].<br>NOTE 1 – ControlledUserInfoTypeString is used only for permission level 3.<br>NOTE 2 – GenericUserInfoType is used only for permission level 2 or 3.  | X          |               |
+| IgnoreIf Unavailable | Element of UserInfoTarget<br>Element to indicate how to handle UserInfo TypeString when information about the specified type is unavailable                                             | 0-1<br>xs:Boolean<br>default = False      | NOTE – If true, then the associated value of UserInfoTypeString is ignored if information about the specified type is unavailable.                                                                                                                       | X          |               |
+| UserInfoValue String | Element of UserInfoTarget<br>Element to match to ControlledUserInfoValue String or GenericUserInfoValue<br>A match indicates that this TD-AMF is a target of this message               | 1<br>nonEmptyString                       | ControlledUserInfoValueString and Generic UserInfoValue are defined in [ITU-T H.741.2] Table 3<br>NOTE 1 – ControlledUserInfoValueString is used only for permission level 3.<br>NOTE 2 – GenericUserInfoValue is used only for permission level 2 or 3. | X          |               |
+| Compression          | Indicates the compression/decompression algorithm used for the XML payload.                                                                                                             |                                           | Defined in [ITU-T H.741.2]                                                                                                                                                                                                                               | X          |               |
+
+**Table 2 – Elements used in delivery**
+
+| Element                                                                                                                                                         | Description                                                                 | Support/type                                             | Notes or value domain                                            | XML | Binary |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|----------------------------------------------------------|------------------------------------------------------------------|-----|--------|
+| Compression                                                                                                                                                     | Indicates the compression/decompression algorithm used for the XML payload. | xs:hexBinary<br>enumeration<br>length = 1 octet (8 bits) | Values: 0=None, 1=BiM, 2=ZLIB, 3=Infoset, or 4=EXI.<br>See NOTE. |     | X      |
+| NOTE – 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]. |                                                                             |                                                          |                                                                  |     |        |
+
+Figure 2 contains the alternative representation of the delivery-dependent XML UserInfoTarget data structure defined in Table 2:
+
+```
+UserInfoTarget
+| UserInfoTypeString (1)
+| IgnoreIfUnavailable (0-1)
+| UserInfoValueString (1)
+```
+
+**Figure 2 – Alternative representation of the delivery-dependent XML UserInfoTarget data structure**
+
+A similar representation can be made for binary headers. The inclusion of elements which indicate the total sizes of other elements or groups of elements (i.e., TerminalDeviceTargetListSize and UserInfoTargetListSize) is recommended, independent of whether any elements are quantified. In the representation shown in Figures 3 and 4, the sets of elements under the total size elements are similar to (0-\*) for the XML representations.
+
+```
+TerminalDeviceTargetListSize (1)
+| TerminalDeviceTarget
+| .
+| .
+| TerminalDeviceTarget
+```
+
+**Figure 3 – Alternative representation of the binary TerminalDeviceTargetListSize data structure**
+
+```
+UserInfoTargetListSize (1)
+| UserInfoTypeSize
+| | UserInfoTypeString
+| IgnoreIfUnavailable
+| EndUserValueSize
+| | UserInfoValueString
+| .
+| .
+| UserInfoTypeSize
+| | UserInfoTypeString
+| IgnoreIfUnavailable
+| EndUserValueSize
+| | UserInfoValueString
+```
+
+**Figure 4 – Alternative representation of the binary UserInfoTargetListSize data structure**
+
+The following clauses define the data structures of AM messages for delivery using unicast or multicast transport delivery mechanisms. In the following tables, the partition between the delivery-dependent XML and the XML payload are indicated by a double line.
+
+In cases where multicast is supported either directly by the network, or by transport protocols which support multicast by replicating unicast messages on the network, the data structures of Table 5, Table 7 and Table 9 are to be used.
+
+### 6.2 Delivery of the data structure "configuration package request"
+
+A unicast transport delivery mechanism is used by TD-AMFs during a pull sequence to deliver the configuration package request data structure.
+
+The data structure of the "configuration request message" is as indicated in Table 3.
+
+**Table 3 – Data structure for the "configuration request message"**
+
+| Element                  | Description                                                                                                                                                                                                                                                                                                                                                                                      | Support/<br>type | Notes or value domain                       |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|---------------------------------------------|
+| MessageType              | Indicates configuration package request message.                                                                                                                                                                                                                                                                                                                                                 | 1                | Defined in Table 2.                         |
+| Expiration Time          | Security element indicating the message expiration time.                                                                                                                                                                                                                                                                                                                                         | 1                | Defined in Table 2.                         |
+| Protocol Version MajorID | Indicates the major protocol version of this message.<br>Differences in major protocol versions indicate incompatibility where mandatory functions have changed so that an older version receiver would not be able to interoperate with a newer version source if it simply ignored the elements and attributes it did not understand and took the actions defined in the older recommendation. | 1                | Defined in Table 2.                         |
+| Protocol Version MinorID | Indicates the minor protocol version of this message, generated by the source of the message. Differences in minor protocol versions indicate compatibility.<br>The minor version number is incremented only if significant new capabilities have been added to the AM protocol (e.g., new message).                                                                                             | 1                | Defined in Table 2.                         |
+| MessageID                | Element of ConfigRequestMsg<br>Message identifier.                                                                                                                                                                                                                                                                                                                                               | 1                | Defined in Table 2.<br>Generated by TD-AMF. |
+| Compression              | Indicates the compression/decompression algorithm used for the XML payload.                                                                                                                                                                                                                                                                                                                      | 0-1              | Defined in Table 2.                         |
+| Config Package Request   | Element of ConfigRequestMsg<br>Container for a configuration package request data structure.                                                                                                                                                                                                                                                                                                     | 1                | Defined in [ITU-T H.741.2].                 |
+
+### 6.3 Delivery of the data structure "configuration package request response"
+
+A unicast transport delivery mechanism may be used by aggregation functions during a pull sequence to deliver the configuration package request response data structure.
+
+A multicast transport delivery mechanism may be used by aggregation functions during a push sequence to deliver the configuration package request response data structure.
+
+For unicast, the data structure of the "unicast configuration request response message" is indicated in Table 4.
+
+**Table 4 – Data structure for "unicast configuration request response message"**
+
+| Element                        | Description                                                                 | Support/<br>type | Notes or value domain                                                        |
+|--------------------------------|-----------------------------------------------------------------------------|------------------|------------------------------------------------------------------------------|
+| MessageType                    | Indicates package request response message.                                 | 1                | Defined in Table 2.                                                          |
+| ExpirationTime                 | Security element indicating the message expiration time.                    | 1                | Defined in Table 2.                                                          |
+| ProtocolVersion MajorID        | Indicates the major protocol version of this message.                       | 1                | Defined in Table 2.                                                          |
+| ProtocolVersion MinorID        | Indicates the minor protocol version of this message.                       | 1                | Defined in Table 2.                                                          |
+| MessageID                      | Element of UnicastConfigRequestResponse Msg<br>Message identifier.          | 1                | Defined in Table 2.<br>Generated by TD-AMF in configuration request message. |
+| Compression                    | Indicates the compression/decompression algorithm used for the XML payload. | 0-1              | Defined in Table 2.                                                          |
+| ConfigPackage Request Response | Container for a configuration package request response data structure.      | 1                | Defined in [ITU-T H.741.2].                                                  |
+
+For multicast, the data structure of the "multicast configuration request response message" is indicated in Table 5.
+
+**Table 5 – Data structure for "multicast configuration request response message"**
+
+| Element                 | Description                                                                 | Support/<br>type | Notes or value domain                                                                            |
+|-------------------------|-----------------------------------------------------------------------------|------------------|--------------------------------------------------------------------------------------------------|
+| MessageType             | Indicates configuration package request response sent over multicast.       | 1                | Defined in Table 2.                                                                              |
+| ExpirationTime          | Security element indicating the message expiration time.                    | 1                | Defined in Table 2.                                                                              |
+| Digest                  | Integrity check element covering all XML elements.                          | 1                | Defined in Table 2.                                                                              |
+| Signature               | Security element indication of authentication.                              | 1                | Defined in Table 2.                                                                              |
+| ProtocolVersion MajorID | Indicates the major protocol version of this message.                       | 1                | Defined in Table 2.                                                                              |
+| ProtocolVersion MinorID | Indicates the minor protocol version of this message.                       | 1                | Defined in Table 2.                                                                              |
+| MessageID               | Message identifier.                                                         | 1                | Defined in Table 2.<br>Generated by aggregation functions, may be used by TD-AMF error messages. |
+| Compression             | Indicates the compression/decompression algorithm used for the XML payload. | 0-1              | Defined in Table 2.                                                                              |
+
+**Table 5 – Data structure for "multicast configuration request response message"**
+
+| Element                       | Description                                                                                                                                           | Support/<br>type | Notes or value domain                                                                                                      |
+|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|----------------------------------------------------------------------------------------------------------------------------|
+| ResponseQualifier             | Qualifies which type(s) of special responses are requested.                                                                                           | 1                | Defined in Table 2.<br>Restricted values:<br>0 = no error response requested<br>1 = error message response requested only. |
+| TerminalDevice Target         | Identifies a terminal device, target of this message, uniquely identifies an end user's terminal device based on hashing of the device's MAC address. | 0-*              | Defined in Table 2.                                                                                                        |
+| UserInfoTarget                | Container for elements specifying user info to be used for targeting TD-AMFs.                                                                         | 0-*              | Defined in Table 2.                                                                                                        |
+| ConfigPackage RequestResponse | Container for a configuration package request response.                                                                                               | 1                | Defined in [ITU-T H.741.2].                                                                                                |
+
+### 6.4 Delivery of the data structure "AMF configuration package"
+
+A unicast transport delivery mechanism may be used by aggregation functions during a push sequence to deliver the AMF configuration package data structure.
+
+A multicast transport delivery mechanism may be used by aggregation functions during a push sequence to deliver the AMF configuration package data structure.
+
+For unicast, the structure of the "unicast configuration message" is indicated in Table 6 and, for multicast transport, the structure of the "multicast configuration message" is indicated in Table 7.
+
+**Table 6 – Data structure for the "unicast configuration message"**
+
+| Element                           | Description                                                                 | Support/<br>type | Notes or value domain                                        |
+|-----------------------------------|-----------------------------------------------------------------------------|------------------|--------------------------------------------------------------|
+| MessageType                       | Indicates a configuration package sent over multicast.                      | 1                | Defined in Table 2.                                          |
+| ExpirationTime                    | Security element indicating the message expiration time.                    | 1                | Defined in Table 2.                                          |
+| ProtocolVersion MajorID           | Indicates the major protocol version of this message.                       | 1                | Defined in Table 2.                                          |
+| ProtocolVersion MinorID           | Indicates the minor protocol version of this message.                       | 1                | Defined in Table 2.                                          |
+| MessageID                         | Message identifier.                                                         | 1                | Defined in Table 2. Generated by aggregation functions.      |
+| Compression                       | Indicates the compression/decompression algorithm used for the XML payload. | 0-1              | Defined in Table 2.                                          |
+| ImmediateAnd Future Configuration | Container for the immediate and future configuration directives.            | 1                | Defined as ConfigPackage RequestResponse in [ITU-T H.741.2]. |
+
+**Table 7 – Data structure for the "multicast configuration message"**
+
+| Element                   | Description                                                                                                                                                                                                                                                                          | Support/<br>type | Notes or value domain                                   |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|---------------------------------------------------------|
+| MessageType               | Indicates a configuration package sent over multicast.                                                                                                                                                                                                                               | 1                | Defined in Table 2.                                     |
+| ExpirationTime            | Security element indicating the message expiration time.                                                                                                                                                                                                                             | 1                | Defined in Table 2.                                     |
+| Digest                    | Integrity check element covering all XML elements.                                                                                                                                                                                                                                   | 1                | Defined in Table 2.                                     |
+| Signature                 | Security element indication of authentication.                                                                                                                                                                                                                                       | 1                | Defined in Table 2.                                     |
+| ProtocolVersion MajorID   | Indicates the major protocol version of this message.                                                                                                                                                                                                                                | 1                | Defined in Table 2.                                     |
+| ProtocolVersion MinorID   | Indicates the minor protocol version of this message.                                                                                                                                                                                                                                | 1                | Defined in Table 2.                                     |
+| MessageID                 | Message identifier.                                                                                                                                                                                                                                                                  | 1                | Defined in Table 2. Generated by aggregation functions. |
+| LowerThreshold            | It indicates the threshold to be used with the generation of a random number between 0 and 10000 by the TD-AMF to decide if the receiving terminal device accepts the configuration message (random number above lower threshold) or not (random number below lower threshold).      | 1<br>Note 2      | Defined in Table 2.                                     |
+| UpperThreshold            | It indicates the threshold to be used with the generation of a random number between 0 and 10000 by the TD-AMF to decide if the receiving terminal device is to accept the configuration message (random number below upper threshold) or not (random number above upper threshold). | 1<br>Note 2      | Defined in Table 2.                                     |
+| Response Qualifier        | Qualifies which type(s) of special responses are requested.                                                                                                                                                                                                                          | 1                | Defined in Table 2.                                     |
+| TerminalDevice Target     | Identifies a terminal device, target of this message, uniquely identifies an end user's terminal device based on hashing of the device's MAC address.                                                                                                                                | 0-*              | Defined in Table 2.                                     |
+| TerminalDevice TypeTarget | This element identifies a terminal device type, target of this message.                                                                                                                                                                                                              | 0-*              | Defined in Table 2.                                     |
+| UserInfoTarget            | Container for elements specifying user info to be used for targeting TD-AMFs.                                                                                                                                                                                                        | 0-*              | Defined in Table 2.                                     |
+| Compression               | Indicates the compression/decompression algorithm used for the XML payload.                                                                                                                                                                                                          | 0-1              | Defined in Table 2.                                     |
+
+**Table 7 – Data structure for the "multicast configuration message"**
+
+| Element                         | Description                                                      | Support/<br>type | Notes or value domain                                        |
+|---------------------------------|------------------------------------------------------------------|------------------|--------------------------------------------------------------|
+| ImmediateAndFutureConfiguration | Container for the immediate and future configuration directives. | 1<br>Note 1      | Defined as ConfigPackage RequestResponse in [ITU-T H.741.2]. |
+
+NOTE 1 – The code element within ImmediateAndFutureConfiguration has enumeration including code as "2" (no configuration package change), which is not to be used here.  
+NOTE 2 – The conditions of both LowerThreshold and UpperThreshold must be met to accept the configuration message. If the values of LowerThreshold and UpperThreshold are the same, then thresholds are not used.
+
+### 6.5 Delivery of the data structure "Measurement report request"
+
+A unicast transport delivery mechanism may be used by aggregation functions during a pull sequence to deliver the measurement report request data structure.
+
+A multicast transport delivery mechanism may be used by aggregation functions during a pull sequence to deliver the measurement report request data structure.
+
+For unicast transport, the structure of the "unicast measurement report request message" is given in Table 8, and for multicast transport, the structure of the "multicast measurement report request message" is as shown in Table 9.
+
+**Table 8 – Data structure for "unicast measurement report request message"**
+
+| Element                   | Description                                                                 | Support/type | Notes or value domain                                   |
+|---------------------------|-----------------------------------------------------------------------------|--------------|---------------------------------------------------------|
+| MessageType               | Indicates a unicast configuration package request response message.         | 1            | Defined in Table 2.                                     |
+| Expiration Time           | Security element indicating the message expiration time.                    | 1            | Defined in Table 2.                                     |
+| Protocol Version MajorID  | Indicates the major protocol version of this message.                       | 1            | Defined in Table 2.                                     |
+| Protocol Version MinorID  | Indicates the minor protocol version of this message.                       | 1            | Defined in Table 2.                                     |
+| MessageID                 | Message identifier.                                                         | 1            | Defined in Table 2. Generated by aggregation functions. |
+| Compression               | Indicates the compression/decompression algorithm used for the XML payload. | 0-1          | Defined in Table 2.                                     |
+| Measurement ReportRequest | Container for a measurement report request data structure.                  | 1            | Defined in [ITU-T H.741.2].                             |
+
+**Table 9 – Data structure for "multicast measurement report request message"**
+
+| Element                    | Description                                                                                                                                                                                                                                                                       | Support/<br>type | Notes or value domain                                      |
+|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|------------------------------------------------------------|
+| Message Type               | Indicates a multicast configuration package request response message.                                                                                                                                                                                                             | 1                | Defined in Table 2.                                        |
+| Expiration Time            | Security element indicating the message expiration time.                                                                                                                                                                                                                          | 1                | Defined in Table 2.                                        |
+| Digest                     | Integrity check element covering all XML elements.                                                                                                                                                                                                                                | 1                | Defined in Table 2.                                        |
+| Signature                  | Security element indication of authentication                                                                                                                                                                                                                                     | 1                | Defined in Table 2.                                        |
+| Protocol Version MajorID   | Indicates the major protocol version of this message.                                                                                                                                                                                                                             | 1                | Defined in Table 2.                                        |
+| Protocol Version MinorID   | Indicates the minor protocol version of this message.                                                                                                                                                                                                                             | 1                | Defined in Table 2.                                        |
+| MessageID                  | Element of MulticastMeasReportRequestMsg Message identifier.                                                                                                                                                                                                                      | 1                | Defined in Table 2.<br>Generated by aggregation functions. |
+| Response Qualifier         | Element of MulticastMeasReportRequestMsg This element qualifies which type(s) of special responses are requested.                                                                                                                                                                 | 1<br>(Note 1)    | Defined in Table 2.                                        |
+| Terminal Device Target     | Identifies a terminal device, target of this message, uniquely identifies an end user's terminal device based on hashing of the device's MAC address.                                                                                                                             | 0-*              | Defined in Table 2.                                        |
+| Lower Threshold            | Indicates the threshold to be used with the generation of a random number between 0 and 10000 by the TD-AMF to decide if the receiving terminal device accepts the configuration message (random number above lower threshold) or not (random number below lower threshold).      | 1<br>(Note 2)    | Defined in Table 2.                                        |
+| Upper Threshold            | Indicates the threshold to be used with the generation of a random number between 0 and 10000 by the TD-AMF to decide if the receiving terminal device is to accept the configuration message (random number below upper threshold) or not (random number above upper threshold). | 1<br>(Note 2)    | Defined in Table 2.                                        |
+| Compression                | Indicates the compression/decompression algorithm used for the XML payload.                                                                                                                                                                                                       | 0-1              | Defined in Table 2.                                        |
+| Measurement Report Request | Container for a measurement report request data structure.                                                                                                                                                                                                                        | 1                | Defined in [ITU-T H.741.2].                                |
+
+NOTE 1 – Only ResponseQualifier values 0 or 1 are permitted in this structure.  
+NOTE 2 – The conditions of both LowerThreshold and UpperThreshold must be met to accept the configuration message. If the values of LowerThreshold and UpperThreshold are the same, then thresholds are not used.
+
+### 6.6 Delivery of the data structure "AM report package"
+
+A unicast transport delivery mechanism may be used by a TD-AMF during a pull or push sequence to deliver the data structure of a set of measurement reports. See Table 10.
+
+**Table 10 – Data structure for the "measurement report message"**
+
+| Element                  | Description                                                                 | Support/type | Notes or value domain                                                                                                                       |
+|--------------------------|-----------------------------------------------------------------------------|--------------|---------------------------------------------------------------------------------------------------------------------------------------------|
+| MessageType              | Indicates a measurement report message.                                     | 1            | Defined in Table 2.                                                                                                                         |
+| Expiration Time          | Security element indicating the message expiration time.                    | 1            | Defined in Table 2.                                                                                                                         |
+| Signature                | Security element indication of authentication.                              | 1            | Defined in Table 2.                                                                                                                         |
+| Protocol Version MajorID | Indicates the major protocol version of this message.                       | 1            | Defined in Table 2.                                                                                                                         |
+| Protocol Version MinorID | Indicates the minor protocol version of this message.                       | 1            | Defined in Table 2.                                                                                                                         |
+| MessageID                | Message identifier.                                                         | 1            | Defined in Table 2. Generated by TD-AMF if push delivery. Generated by aggregation function in measurement report request if pull delivery. |
+| Compression              | Indicates the compression/decompression algorithm used for the XML payload. | 0-1          | Defined in Table 2.                                                                                                                         |
+| AMReport Package         | Container for data structure of a set of measurement reports.               | 1            | Defined in [ITU-T H.741.2].                                                                                                                 |
+
+### 6.7 Delivery of the data structure "Ack"
+
+A unicast transport delivery mechanism may be used by a TD-AMF during a push sequence to deliver the ack data structure. See Table 11.
+
+**Table 11 – Data structure for the "configuration ack message"**
+
+| Element                  | Description                                              | Support/type | Notes or value domain |
+|--------------------------|----------------------------------------------------------|--------------|-----------------------|
+| MessageType              | Indicates an acknowledge message.                        | 1            | Defined in Table 2.   |
+| Expiration Time          | Security element indicating the message expiration time. | 1            | Defined in Table 2.   |
+| Protocol Version MajorID | Indicates the major protocol version of this message.    | 1            | Defined in Table 2.   |
+| Protocol Version MinorID | Indicates the minor protocol version of this message.    | 1            | Defined in Table 2.   |
+
+**Table 11 – Data structure for the "configuration ack message"**
+
+| Element     | Description                                                                 | Support/type | Notes or value domain       |
+|-------------|-----------------------------------------------------------------------------|--------------|-----------------------------|
+| MessageID   | Message identifier of the configuration message being responded to.         | 1            | Defined in Table 2.         |
+| Compression | Indicates the compression/decompression algorithm used for the XML payload. | 0-1          | Defined in Table 2.         |
+| Ack         | Container for acknowledge message.                                          | 1            | Defined in [ITU-T H.741.2]. |
+
+### 6.8 Delivery of the data structure "Error"
+
+A unicast transport delivery mechanism may be used by a TD-AMF or aggregation functions during a push or pull sequence to deliver the error data structure. See Table 12.
+
+All five error messages (configuration request error message, configuration response error message, configuration error message, measurement report request error message, and measurement report error message) are identical to the "Error" data structure.
+
+**Table 12 – Data structure for the "error message"**
+
+| Element                 | Description                                                                 | Support/type | Notes or value domain       |
+|-------------------------|-----------------------------------------------------------------------------|--------------|-----------------------------|
+| MessageType             | Indicates an error message.                                                 | 1            | Defined in Table 2.         |
+| ExpirationTime          | Security element indicating the message expiration time.                    | 1            | Defined in Table 2.         |
+| ProtocolVersion MajorID | Indicates the major protocol version of this message.                       | 1            | Defined in Table 2.         |
+| ProtocolVersion MinorID | Indicates the minor protocol version of this message.                       | 1            | Defined in Table 2.         |
+| MessageID               | Message identifier of the message being responded to.                       | 1            | Defined in Table 2.         |
+| Compression             | Indicates the compression/decompression algorithm used for the XML payload. | 0-1          | Defined in Table 2.         |
+| Error                   | Container for error message.                                                | 1            | Defined in [ITU-T H.741.2]. |
+
+## Appendix I
+
+## Transport protocol considerations for audience measurement
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Following the specification of the audience measurement (AM) application, this appendix examines AM and its considerations for designers and the selection of suitable transport protocol(s).
+
+AM has eleven message types (see [ITU-T H.741.0]) of which all can be unicast at the application level; they are to be transported as unicast. Three of the (downstream direction) message types can be multicast at the application level; these are best transported using network multicast but may be replicated at the transport level using unicast (which increases network congestion). AM defines both unicast messages and multicast message for these three message types. It is recommended that the multicast version be used when multicast by replicated unicast is used. Appendix II of [ITU-T H.741.1] provides considerations for unicast vs multicast implementation.
+
+### I.1 AM message size characteristics
+
+Table I.1 describes whether unicast and/or multicast protocols can be used for each message type. It provides relative message size range estimates of each message with dependencies which increase size. S=Small, M=Medium, and L=Large.
+
+**Table I.1 – Relative size characteristics of AM message types**
+
+| Message                                  | Unicast | Multicast | Relative size range | Dependencies that increase message size                                                                   |
+|------------------------------------------|---------|-----------|---------------------|-----------------------------------------------------------------------------------------------------------|
+| Configuration request message            | X       |           | M-M                 | Hybrid permission mode                                                                                    |
+| Configuration request error message      | X       |           | S-S                 | Number of errors                                                                                          |
+| Configuration request response message   | X       | Y         | S-M                 | Configuration complexity and second configuration                                                         |
+| Configuration response error message     | X       |           | S-S                 | Number of errors                                                                                          |
+| Configuration message                    | X       | Y         | S-M                 | Configuration complexity and second configuration                                                         |
+| Configuration ack/error message          | X       |           | S-S                 | Number of errors                                                                                          |
+| Measurement report request message       | X       | Y         | S-S                 | Number of measurement requests                                                                            |
+| Measurement report request error message | X       |           | S-S                 | Number of errors                                                                                          |
+| Measurement report message               | X       |           | S-L                 | Batched reporting, scheduled push delivery or pull delivery modes. Maximum size limited by TD-AMF storage |
+| Measurement report error message         | X       |           | S-S                 | Number of errors                                                                                          |
+
+### I.2 AM message reliability needs
+
+It is expected that AM be used for both aggregate and individual end-user device use cases. For aggregate use cases, e.g., viewership count, a statistical result is sufficient. It is not required that continual and proper participation in AM be guaranteed for every end-user device. For individual use cases, e.g., input for personalized recommendation engines, the historical information is sufficient. Again, it is not required that continual and proper participation in AM be guaranteed for every end-user device. It is therefore acceptable that any AM message type may infrequently fail to be delivered. However, since report messages may be very large when scheduled or pull delivery modes are used, it is recommended that reliability be sufficient to assure delivery of large report messages. In considering the partitioning of reliability between the AM application and transport protocols, it should be noted that, at an application level, AM supports a report message retry count and multiple delivery destination addresses.
+
+It is acceptable to use different transport protocols for different message types.
+
+AM functional aspects that suffer from a loss of reliability are: timeliness in delivery and loss of data. Table I.2 describes the need for reliability for each message type described in [ITU-T H.741.0] and the impact when messages are not delivered.
+
+**Table I.2 – AM message reliability needs**
+
+| <b>Message</b>                           | <b>Reliability need</b>                    | <b>Impact of non-delivery of message</b>                                            |
+|------------------------------------------|--------------------------------------------|-------------------------------------------------------------------------------------|
+| Configuration request message            | Low                                        | Message retry, possible gap in measurements, or wrong measurements                  |
+| Configuration request error message      | Low                                        | Message retry, possible gap in measurements, or wrong measurements                  |
+| Configuration request response message   | Low                                        | Message retry, possible gap in measurements, or wrong measurements                  |
+| Configuration response error message     | Low                                        | Message retry, possible gap in measurements, or wrong measurements                  |
+| Configuration message                    | Low                                        | Possible gap in measurements or wrong measurements                                  |
+| Configuration ack/error message          | Low                                        | Lower system health confidence, possible gap in measurements, or wrong measurements |
+| Measurement report request message       | Low                                        | Loss of stored measured data                                                        |
+| Measurement report request error message | Low                                        | Loss of stored measured data                                                        |
+| Measurement report message               | Higher if large message sizes are expected | Loss of measured data                                                               |
+| Measurement report error message         | Low                                        | Loss of measured data                                                               |
+
+When considering higher reliability in the transport of report messages, it should be borne in mind that the more highly reliable transport protocols may require substantially more states to be stored by aggregation servers in large-scale deployments, and may have an impact on their requirements.
+
+### **I.3 AM message QoS needs**
+
+The impact of loss is described in clause I.2. Furthermore, since jitter and delay are not important for the operation of AM, AM traffic may be marked as bulk class or equivalent.
+
+### **I.4 AM message integrity needs**
+
+The integrity of AM messaging is important for its operation. Since AM includes an integrity check via cryptographic hash in the delivery-dependent XML and binary header, it does not require that transport protocols provide integrity checks.
+
+### **I.5 AM message encryption needs**
+
+AM report messages (upstream direction) can contain controlled information which must be encrypted. Since AM includes support for encryption, it does not require that transport protocols provide encryption.
+
+## Bibliography
+
+- [b-ITU-T H.720] Recommendation ITU-T H.720 (2008), *Overview of IPTV terminal devices and end systems*.
+- [b-ITU-T H.740] Recommendation ITU-T H.740 (2010), *Application event handling 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 M.1400] Recommendation ITU-T M.1400 (2001), *Designations for interconnections among network operators*.
+- [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), *Requirement for the support of IPTV services*.
+- [b-ITU-T Y.1910] Recommendation ITU-T Y.1910 (2008), *IPTV functional architecture*.
+- [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-IETF RFC 5905] IETF RFC 5905 (2010), *Network Time Protocol Version 4: Protocol and Algorithms Specification*.
+- [b-IETF RFC 6151] IETF RFC 6151 (2011), *Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms*.
+- [b-ISO 19136] ISO 19136:2007, *Geographic information – Geography Markup Language (GML)*.
+- [b-ISO/IEC 23001-1] ISO/IEC 23001-1:2006/Cor 1:2007, *Information technology – MPEG systems technologies – Part 1: Binary MPEG format for XML*.
+- [b-FIPS PUB 180-3] National Institute of Standards and Technology (NIST), FIPS PUB 180-3 (2008), *Secure Hash Standard (SHS)*.
+- [b-FIPS PUB 186-3] National Institute of Standards and Technology (NIST), FIPS PUB 186-3 (2009), *Digital Signature Standard*.
+- [b-W3C EXI] W3C Recommendation (2011), *Efficient XML Interchange (EXI) Format 1.0*.  
+<http://www.w3.org/TR/exi/>
+
+
+
+## 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/marked/H/T-REC-H.742.0-201607-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a459d99094c502359cf94134a02e9ffb4fd46995
--- /dev/null
+++ b/marked/H/T-REC-H.742.0-201607-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6a38422564a351690000e7db2be76a571be03a37b65e3da01b386fc44ea19784
+size 72018
diff --git a/marked/H/T-REC-H.742.0-201607-I_PDF-E/35127fe87029df6f5f0b2ee85f6193f1_img.jpg b/marked/H/T-REC-H.742.0-201607-I_PDF-E/35127fe87029df6f5f0b2ee85f6193f1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..10696b48cf0968833c8f0e04158f686ef642909f
--- /dev/null
+++ b/marked/H/T-REC-H.742.0-201607-I_PDF-E/35127fe87029df6f5f0b2ee85f6193f1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d475d041cf2ea26134911a61ff13dd80e490c109de2e70a4450654e361e274f7
+size 41735
diff --git a/marked/H/T-REC-H.742.0-201607-I_PDF-E/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg b/marked/H/T-REC-H.742.0-201607-I_PDF-E/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e681891f199e531338bd0d676d61ae9dda43aa20
--- /dev/null
+++ b/marked/H/T-REC-H.742.0-201607-I_PDF-E/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:297f26176e0c8fe12812e1b97d170275491f5c23059c9636dcfc041d024771ae
+size 34692
diff --git a/marked/H/T-REC-H.742.0-201607-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/H/T-REC-H.742.0-201607-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7a740da51f89ed3777f4b793a2425a48226acf0d
--- /dev/null
+++ b/marked/H/T-REC-H.742.0-201607-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ad7ccdc83a8a6dcba31f87da128b5c6992a222943b2f8221764c2d6b49fd02cb
+size 63630
diff --git a/marked/H/T-REC-H.742.0-201607-I_PDF-E/43837b056625d3d6ce615e4c02f163bb_img.jpg b/marked/H/T-REC-H.742.0-201607-I_PDF-E/43837b056625d3d6ce615e4c02f163bb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d732ecc200eed82ce221becb19b3a261b1ca3f1e
--- /dev/null
+++ b/marked/H/T-REC-H.742.0-201607-I_PDF-E/43837b056625d3d6ce615e4c02f163bb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e6b9b99fc572fa7d335ddb11af81bf9c53642150d35576d54530312d972b8ad8
+size 57235
diff --git a/marked/H/T-REC-H.742.0-201607-I_PDF-E/552ca016af3d6240648ab5a2cad97f60_img.jpg b/marked/H/T-REC-H.742.0-201607-I_PDF-E/552ca016af3d6240648ab5a2cad97f60_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..be1a85e63ecc336a2609db86c29d562e68684762
--- /dev/null
+++ b/marked/H/T-REC-H.742.0-201607-I_PDF-E/552ca016af3d6240648ab5a2cad97f60_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e570613942be82c72f32983f136068a6db20cab88e014149ab51ad96b6ce9007
+size 51023
diff --git a/marked/H/T-REC-H.742.0-201607-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/H/T-REC-H.742.0-201607-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9e9fa6a7cbe134e353040c34de1cbf9d7b06c3be
--- /dev/null
+++ b/marked/H/T-REC-H.742.0-201607-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b50f14af223ae7504dbfc463953bad5ad93b282a3facef0ffad6227f39f53004
+size 55904
diff --git a/marked/H/T-REC-H.742.0-201607-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.742.0-201607-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..529e4f72f14cdf7f41f56cfbfb26655bf8181c59
--- /dev/null
+++ b/marked/H/T-REC-H.742.0-201607-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.742.0-201607-I_PDF-E/b7c99649d8de39a814e0bad989d50b12_img.jpg b/marked/H/T-REC-H.742.0-201607-I_PDF-E/b7c99649d8de39a814e0bad989d50b12_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6b96bcaf098937bebfc8668ffa90f108610d2531
--- /dev/null
+++ b/marked/H/T-REC-H.742.0-201607-I_PDF-E/b7c99649d8de39a814e0bad989d50b12_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b7201215787b3968b07b6a81016bf0c5f3996ef8e7277fc7975260c1a1b0111c
+size 4276
diff --git a/marked/H/T-REC-H.742.0-201607-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.742.0-201607-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7c437549eaf196d48a8d8099bd5da212fc64d2b7
--- /dev/null
+++ b/marked/H/T-REC-H.742.0-201607-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e1a4f4d231e45d4253b376804c1051cb2239b0e89860bc2e42509235b05797bb
+size 37752
diff --git a/marked/H/T-REC-H.742.0-201607-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/H/T-REC-H.742.0-201607-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f909899774c6fbe12188ca67687e0c09418d2646
--- /dev/null
+++ b/marked/H/T-REC-H.742.0-201607-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9795e82c5d91863b8891aaad353e3d21993d7839c220b2db4e39fa893267ea27
+size 147304
diff --git a/marked/H/T-REC-H.742.0-201607-I_PDF-E/f5aaecb6473222e3d65f65164fab048e_img.jpg b/marked/H/T-REC-H.742.0-201607-I_PDF-E/f5aaecb6473222e3d65f65164fab048e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b144fb9dbb194e7d2ee63c180562c22373d0f086
--- /dev/null
+++ b/marked/H/T-REC-H.742.0-201607-I_PDF-E/f5aaecb6473222e3d65f65164fab048e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:814e7813f5c4e1decdb557eee2a6e705719ce576cfca96a4edbb2a703772ea96
+size 3177
diff --git a/marked/H/T-REC-H.742.0-201607-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.742.0-201607-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7ffd1f4ff7d43b348693d8294b6ef482f4e0603e
--- /dev/null
+++ b/marked/H/T-REC-H.742.0-201607-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e9e7de473d9d87a67935b40f3b5b156930089290b122d2c9656f0411d9ea14af
+size 84037
diff --git a/marked/H/T-REC-H.751-201303-I_PDF-E/raw.md b/marked/H/T-REC-H.751-201303-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..8eb098276f21d58df54bacd649b48d8fecb90303
--- /dev/null
+++ b/marked/H/T-REC-H.751-201303-I_PDF-E/raw.md
@@ -0,0 +1,1424 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.751**
+
+(03/2013)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+IPTV multimedia services and applications for IPTV –  
+IPTV metadata
+
+# --- **Metadata for rights information interoperability in IPTV services**
+
+Recommendation ITU-T H.751
+
+# 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        |
+| <b>IPTV metadata</b>                                                          | <b>H.750–H.759</b> |
+| 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.751
+
+# Metadata for rights information interoperability in IPTV services
+
+## Summary
+
+Recommendation ITU-T H.751 defines the common semantics and core elements of rights information interoperability (RII) for Internet Protocol television (IPTV) systems and/or equipment that allow multimedia content to be legally used across different platforms. The rights information includes rights- and security-related metadata that is described in Recommendation ITU-T H.750. This Recommendation describes rights-related information such as content ID, permission issuer ID and permission receiver ID, which are used to bridge between rights-related metadata. It should be noted, however, that rights management and content protection technology are beyond the scope of this Recommendation. This Recommendation is technically aligned with the specification in IEC 62698, *Multimedia home server systems – Rights information interoperability for IPTV*.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group |
+|---------|----------------|------------|-------------|
+| 1.0     | ITU-T H.751    | 2013-03-16 | 16          |
+
+## Keywords
+
+Metadata, permission, rights information.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                               | 3  |
+| 4     | Abbreviations and acronyms .....                                        | 3  |
+| 5     | Conventions .....                                                       | 4  |
+| 6     | Introduction: the RII environment.....                                  | 4  |
+| 6.1   | General .....                                                           | 4  |
+| 6.2   | Permission subjects .....                                               | 5  |
+| 6.3   | Permission limit components .....                                       | 5  |
+| 7     | Permission subject identifiers .....                                    | 6  |
+| 7.1   | Content identifier.....                                                 | 6  |
+| 7.2   | Issuer identifier.....                                                  | 6  |
+| 7.3   | Receiver identifier .....                                               | 6  |
+| 8     | Permission classification .....                                         | 6  |
+| 8.1   | Disclosure class .....                                                  | 7  |
+| 8.2   | Purpose class .....                                                     | 7  |
+| 8.3   | Charge model class.....                                                 | 7  |
+| 8.4   | Sponsor class .....                                                     | 7  |
+| 8.5   | Territory class.....                                                    | 8  |
+| 8.6   | Usage class .....                                                       | 8  |
+| 8.7   | Compilation class .....                                                 | 9  |
+| 9     | Permission limit components.....                                        | 9  |
+| 9.1   | General usage condition .....                                           | 9  |
+| 9.2   | Extended usage condition.....                                           | 11 |
+| 10    | Data management condition .....                                         | 11 |
+| 11    | Data export condition .....                                             | 12 |
+|       | Appendix I – Security-related issues .....                              | 14 |
+| I.1   | Tamper detection .....                                                  | 14 |
+| I.2   | Keeping secret .....                                                    | 15 |
+|       | Appendix II – Syntax (encoding).....                                    | 16 |
+| II.1  | General .....                                                           | 16 |
+| II.2  | Digital rights permission code syntaxes tables of the 23 scenarios..... | 16 |
+|       | Appendix III – Background to rights information interoperability.....   | 20 |
+| III.1 | General .....                                                           | 20 |
+| III.2 | Relationship between rights and digital permissions .....               | 21 |
+
+|                                                                                                                                                                             | Page |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|
+| Appendix IV – Two basic technologies for enabling RII .....                                                                                                                 | 23   |
+| IV.1    Code language technology that carries the shared elements that identify<br>the scattered content and the parties associated with that content.....                  | 23   |
+| IV.2    Code language technology that carries the shared elements of the specific<br>content consumer services.....                                                         | 25   |
+| IV.3    Common semantics for RII .....                                                                                                                                      | 26   |
+| IV.4    Core elements and common semantics for RII.....                                                                                                                     | 26   |
+| Appendix V – Rights information metadata elements corresponding to existing SCP<br>systems.....                                                                             | 28   |
+| V.1    SCP1 .....                                                                                                                                                           | 28   |
+| V.2    SCP System 2, with Download license, EXPORT for Copy with Direct<br>Key Delivery .....                                                                               | 30   |
+| V.3    SCP System 3, with Download license, EXTRACT with Direct Key<br>Delivery, Download .....                                                                             | 31   |
+| V.4    SCP System 4, with Download license, EXTRACT with Direct Key<br>Delivery, VOD streaming.....                                                                         | 32   |
+| V.5    SCP System 3, with Download license, EXTRACT with Direct Key<br>Delivery, Download .....                                                                             | 33   |
+| V.6    SCP System 4, with Download license, EXTRACT with Direct Key<br>Delivery, VOD streaming.....                                                                         | 34   |
+| V.7    SCP System 5, with, Broadcast license, EXTRACT with IndirectKey<br>Delivery license, Terrestrial re-distribution/BS(Broadcasting satellite) re-<br>distribution..... | 35   |
+| V.8    SCP System 6, with Broadcast license, EXTRACT with DirectKey<br>Delivery license, IP multicast.....                                                                  | 36   |
+| V.9    SCP System 9, for mobile IPTV terminal .....                                                                                                                         | 38   |
+| V.10   SCP System 10, for recording media (e.g., DVD), basic .....                                                                                                          | 39   |
+| V.11   SCP System 11, for recording media (e.g., DVD), extended .....                                                                                                       | 40   |
+| Appendix VI – Examples of media formats.....                                                                                                                                | 41   |
+| Bibliography.....                                                                                                                                                           | 42   |
+
+# Recommendation ITU-T H.751
+
+# Metadata for rights information interoperability in IPTV services
+
+# 1 Scope
+
+This Recommendation gives the high-level specification of the metadata for rights information interoperability, including representation of the minimum required elements. The rights information interoperability (RII) metadata provide descriptive and contextual classification for representing rights information using the permission framework. RII is concerned with finding the greatest common denominators in rights expressions that include the minimum required components when trying to implement the mutual use of rights information.
+
+This Recommendation defines the common semantics and core elements of rights information interoperability for IPTV systems and/or equipment that require multimedia content to be legally used across different platforms.
+
+The rights information includes rights- and security-related metadata that is described in [ITU-T H.750].
+
+Rights-related information, such as content ID, permission issuer ID and permission receiver ID, which is used to bridge between rights-related metadata, is considered in this Recommendation. It should be noted, however, that rights management and content protection technology are beyond the scope of this Recommendation.
+
+This Recommendation is technically aligned with the specification in [IEC 62698].
+
+## 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.750] Recommendation ITU-T H.750 (2008), *High-level specification of metadata for IPTV services*.
+- [IEC 62227] IEC 62227 (2008), *Multimedia home server systems – Digital rights permission code subdivisions*.
+- [IEC 62698] IEC 62698:2013, *Multimedia home server systems – Rights information interoperability for IPTV*.
+- [ISO 3166-1] ISO 3166-1 (2009), *Codes for the representation of names of countries and their subdivisions – Part 1: Country codes*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 authentication** [b-ITU-T X.800]: See data origin authentication and peer-entity authentication.
+
+**3.1.2 content export** [b-ITU-T X.1191]: Process of exporting securely the IPTV content from the IPTV terminal to another terminal owned by the user entitled to use it.
+
+**3.1.3 content protection** [b-ITU-T Y.1901]: Ensuring that an end-user can only use the content they have already acquired in accordance with the rights that they have been granted by the rights holder.
+
+**3.1.4 data origin authentication** [b-ITU-T X.800]: The corroboration that the source of data received is as claimed.
+
+**3.1.5 digital signature** [b-ITU-T X.800]: Data appended to, or a cryptographic transformation (see cryptography) of a data unit that allows a recipient of the data unit to prove the source and integrity of the data unit and protect against forgery e.g., by the recipient.
+
+**3.1.6 distribution** [b-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.7 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.8 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 key** [b-ITU-T X.800]: A sequence of symbols that controls the operations of encipherment and decipherment.
+
+**3.1.10 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.11 peer-entity authentication** [b-ITU-T X.800]: The corroboration that a peer entity in an association is the one claimed.
+
+**3.1.12 PkiPath** [b-ITU-T X.509]: The data type PkiPath is used to represent a certification path for ITU-T X.509 digital certificates. Within the sequence, the order of public-key certificates is such that the subject of the first certificate is the issuer of the second certificate, etc.
+
+**3.1.13 rights** [b-ITU-T X.1191]: Referring to the ability to perform a predefined set of utilization functions for a content item; these utilization functions include permissions (e.g., to view/hear, copy, modify, record, excerpt, sample, keep for a certain period, distribute), restrictions (e.g., play/view/hear for multiple number of times, play/view/hear for certain number of hours), and obligations (e.g., payment, content tracing) that apply to the content and provide the liberty of use as granted to the end user.
+
+**3.1.14 rights expression** [b-ITU-T X.1191]: Syntactic embodiment of rights in concrete, formal form.
+
+**3.1.15 service** [b-ITU-T Y.101]: A structure set of capabilities intended to support applications.
+
+**3.1.16 service and content protection** [b-ITU-T X.1191]: A combination of service protection and content protection or the system or implementation thereof.
+
+**3.1.17 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.18 tamper-resistant** [b-ITU-T X.1191]: Resistance to tampering by either the personal users/attackers of a product, package, or system with physical/software access to it.
+
+**3.1.19 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.20 transcoding** [b-ITU-T X.1191]: Process of transforming multimedia content such as images, text, audio, and video from the original format to a different format or quality.
+
+**3.1.21 video on demand (VoD)** [b-ITU-T Y.1910]: A service in which the end user can, on demand, select and view 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 term:
+
+**3.2.1 information interoperability:** The term used to describe the ability to meaningfully exchange information among separately developed systems, where the separate systems are able to understand the format, meaning and also the quality of the information being exchanged.<sup>1</sup>
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|        |                                            |
+|--------|--------------------------------------------|
+| AAC    | Advanced Audio Coding                      |
+| CD     | Compact Disc                               |
+| CM     | Commercial Message                         |
+| DRPC   | Digital Rights Permission Code             |
+| DSA    | Digital Signature Algorithm                |
+| DVD    | Digital Versatile Disk                     |
+| EC-DSA | Elliptic Curve Digital Signature Algorithm |
+| GC     | Group Contents                             |
+| GIF    | Graphic Interchange Format                 |
+| HD     | High Definition                            |
+| HDD    | Hard Disk Drive                            |
+| ID     | Identifier                                 |
+| IPTV   | Internet Protocol Television               |
+| JPEG   | Joint Photographic Experts Group           |
+| MP3    | MPEG Audio Layer-3                         |
+
+---
+
+<sup>1</sup> Based on [http://www.webopedia.com/TERM/I/information\\_interoperability.html](http://www.webopedia.com/TERM/I/information_interoperability.html)
+
+|      |                                     |
+|------|-------------------------------------|
+| MPEG | Moving Picture Experts Group        |
+| PCM  | Pulse Code Modulation               |
+| PNG  | Portable Network Graphics           |
+| RII  | Rights Information Interoperability |
+| RSA  | Rivest Shamir Adleman               |
+| SCP  | Service and Content Protection      |
+| SHA  | Secure Hash Algorithm               |
+| VOD  | Video On Demand                     |
+
+## 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 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 this Recommendation.
+
+# 6 Introduction: the RII environment
+
+### 6.1 General
+
+This Recommendation gives the high-level standard of the metadata for rights information interoperability, including representation of the minimum recommended elements.
+
+The RII metadata provides descriptive and contextual classification for representing rights information using the permission framework.
+
+RII is concerned with finding the greatest common denominators in rights expressions that include the minimum required components when trying to implement the mutual use of rights information. In other words, RII is about conveying rights information in units of groups of context expressions called permissions.
+
+This Recommendation considers the constituent components of permissions. Permissions can encode "what, from whom and to whom" and "under what conditions" using context expressions. When permissions are sent to a terminal, the minimum required components are the subject information in the permissions that corresponds to the "what, from whom and to whom" part, and the content usage information that corresponds to the "under what conditions" part.
+
+### 6.2 Permission subjects
+
+One permission subject is the issuer information that expresses the "from whom" part of the permissions. This information is held by the service provider and, in RII, its minimum recommended component is the rights-holder ID.
+
+Only the issuer ID is included because in RII it is sufficient if the service provider and the terminal can identify who is granting the permissions. It is not necessary to send all of the issuer information from the server to the terminal. Therefore, the rights-holder ID corresponds to the issuer ID in RII context expressions. The service provider receives the digital rights permission code from the terminal and loads the rights holder ID included in the issuer ID to identify the rights holder who granted the permissions.
+
+Another permission subject is receiver information that expresses the "to whom" part of the permissions. In RII, that minimum required component is the user ID/device ID.
+
+Only the receiver ID is included because in RII it is sufficient if the service provider and the terminal can identify to whom the permissions are being granted. Therefore, the user ID/device ID corresponds to the receiver ID in RII context expressions. The terminal receives the digital rights permission code from the service provider and determines whether or not the user ID/device ID included in the receiver ID corresponds to the local terminal, or if the service provider receives the digital rights permission code from the terminal and loads the user ID/device ID included in the receiver ID to identify the user to whom permissions were granted.
+
+Another permission subject is information about the content for which permissions are being granted, which is expressed in the "what" part. In RII, that minimum required component is the content ID.
+
+Only the content ID is included in RII because it is sufficient for the service provider and the terminal to be able to identify the content for which permissions are being granted. The terminal receives the digital-rights permission code from the service provider and determines that the content that corresponds to the content ID is being granted.
+
+### 6.3 Permission limit components
+
+One permission limit component is the type of permission (hereinafter referred to as "the permission classification component"), which expresses stipulations about what is being granted. These permissions are agreed upon between the issuer and the receiver. This is information that the receiver needs to be able to check offline.
+
+In RII, those minimum required components are the following types, which indicate:
+
+- whether the permission content being granted is public or not (hereinafter referred to as "the disclosure class");
+- the purpose of use being granted (hereinafter referred to as the "purpose class");
+- the billing format being granted (hereinafter referred to as the "charge model class");
+- the request format being granted (hereinafter referred to as the "request class");
+- the sponsor format being granted (hereinafter referred to as the "sponsor class");
+- the usage format being granted (hereinafter referred to as the "usage class"); and
+- the territory being granted, (hereinafter referred to as the "territory class").
+
+These permissions limit components are included in RII because it is necessary to be able to see the information, even in an offline environment that is not connected to a network. This is so that the terminal can determine what types of permission are being granted between the service provider and the terminal.
+
+Another permission limit component contains limiting conditions that are in addition to the restrictions in the items granted above. These are mainly information that limits the type of permissions stipulated by the usage class. In RII, those minimum required components are:
+
+- the permission usage format and its limiting conditions (hereinafter referred to as "normal usage limits");
+- content usage limits for compliant terminals (hereinafter referred to as the "permission management system limits"); and
+- the limits on output of the content to non-compliant terminals or media (hereinafter referred to as the "simultaneous output limits").
+
+These permissions limit components are included in RII because it is necessary that the rights they correspond be seen on the terminal, even in an offline environment that is not connected to a network. This is so that the terminal can determine under what conditions the types of permissions are limited between the service provider and the terminal.
+
+RII does not provide a method of encoding context expressions for permissions and the encoding method should make use of existing standardized technology. Clause II.2 shows the example of adding context expressions stated using natural language in [IEC 62227].
+
+RII is a set of items to be considered when content is distributed and permission for such distribution is generated. Therefore, RII is not defined from a technical perspective, but rather on the basis of permission information that rights holders actually employ in the field. RII itself does not have the ability to regulate content usage behaviour.
+
+Restricting the use of content to terms specified in the permission is either an administrative issue or an issue related to service and content protection (SCP) systems. RII does not have an exclusive policy. Implementers of each SCP or content distribution system can choose their own subset and RII usage scheme, based on their necessity and resources. For example, they can limit the application to simply displaying the permissions but not use them for rights management.
+
+## **7 Permission subject identifiers**
+
+There are three permission subject identifiers: Content identifier assigned to the subject content, issuer identifier assigned respectively to each permission issuer, and receiver identifier assigned to each permission receiver.
+
+### **7.1 Content identifier**
+
+The content identifier is information to uniquely identify the content. It is required that a content identifier be assigned to each content that is subject to permission.
+
+### **7.2 Issuer identifier**
+
+The issuer identifier is information to uniquely identify the permission issuer. The issuer identifier may be used not only to identify a rights holder, a service provider and a home server, but also for consumption tracking, rights reporting and content management.
+
+### **7.3 Receiver identifier**
+
+The receiver identifier is information to uniquely identify the permission receiver. The receiver identifier may be used to identify an end-user, a device or a set of end users.
+
+## **8 Permission classification**
+
+Permission classification indicates the class of the permission. It should be described according to the conditions indicated in the permission agreement.
+
+### 8.1 Disclosure class
+
+Disclosure class includes classification indicating whether a given permission is a closed permission for a specified player, or an open permission for an unspecified group of players. The closed permission information can be accessed by the permission issuer and receiver. Possible values are "open permission", "closed permission" and "other". Open permission is the permission that is received according to previously arranged default conditions. Closed permission is the permission that is received through a separate, individually negotiated contract.
+
+Clause 5.6.4 in [IEC 62227] on disclosure classes specifies a permission classification for signalling and carrying disclosure information. Informative clause B.2 of [b-IEC 62636] addresses permission actors and permission classifications and provides use-case scenarios for implementing disclosure class.
+
+### 8.2 Purpose class
+
+Purpose class includes classification indicating the purpose of content usage, such as commercial, public, education, not-for-profit and promotion. To ensure the consumption of content under the condition could be subject to domain management. Possible values are "commercial", "public", "non-profit", "promotion", "education" and "other".
+
+Commercial permission is the permission for a business use. Public permission is the permission for a public use. Non-profit permission is the permission for a public use. Promotion permission is the permission for a promotion use. Education permission is the permission for an education use.
+
+Clause 5.6.5 of [IEC 62227] addresses usage purpose class and specifies a permission classification for signalling and carrying usage purpose information. Clauses 5 and B.2 (informative) of [b-IEC 62636] provide use-case scenarios for implementing usage purpose class.
+
+### 8.3 Charge model class
+
+Charge model class defines classification including the charge method such as free-of-charge and for-charge. It might include "pay-per-view" (charged per viewing), and "subscription" (fixed periodic charge) categories. These conditions should not be used at the same time; if one is selected, the other is not used. Possible values are "free of charge", "pay per use", "subscription", and "coupon".
+
+Clause 5.6.6 of [IEC 62227] specifies a permission classification for signalling and carrying charge model information. Informative clause B.2 of [b-IEC 62636] provides use-case scenarios for implementing charge model classes.
+
+### 8.4 Sponsor class
+
+Sponsor class includes classification indicating the sponsor type such as advertising model, premium model, coupon model and consumption information disclosure model.
+
+The advertising model describes the condition of viewing ads in the content consumption. The premium, coupon and consumption information disclosure models describe the conditions for the content acquisition. In the premium model there can be a specific advertiser to sponsor a specific content. In the coupon model there can be multiple advertiser to sponsor the content. In the disclosure model, the content can be exchanged for end-user's consumption information. The control of trick play and the function of point exchange are required to be implemented for these models. Possible values are "No sponsor", "Advertisement model without force viewing", "Advertisement model with force viewing", "Advertisement model with pre/post viewing", "Advertisement model with alternative viewing", "Advertisement model with blanket viewing", "Premium model", "Coupon model", "Privacy information disclosure model" and "Other".
+
+Clause 5.6.9 in [IEC 62227] on sponsor classes specifies a permission classification for signalling and carrying sponsor information. Clauses 5.17 and 5.18 in [b-IEC 62636] describe use-case scenarios on download and streaming of free content with advertising that illustrate the implementation of sponsor class.
+
+### 8.5 Territory class
+
+Territory class includes classification indicating the territory of content consumption such as country and region. It is required to implement the technology, such as domain management, to specify the territory in which contents are consumed. Possible values are region code, country code (ISO 3166-1) and postal code.
+
+Clause 5.6.10 in [IEC 62227] specifies a permission classification for signalling and carrying territory information. Clause B.2 of [b-IEC 62636] provides a use-case scenario for implementing territory class.
+
+### 8.6 Usage class
+
+Usage class includes classification indicating the usage type such as transmission type, store type, reuse type, and redistribution type based on usage environment.
+
+Clause 5.6.11 in [IEC 62227] on usage class specifies a permission classification for signalling and carrying usage information. Clause B.2 of [b-IEC 62636] provides a use-case scenario for implementing usage class.
+
+The elements required in the usage class are as follows:
+
+- Transmission type expresses a distribution form of content into target domains and conformance devices. For example, if the value is "download", the content can be downloaded into conformance devices. Possible values are "broadcast", "streaming", "download" and "physical media".
+  - Clause 5.6.11.2 in [IEC 62227] on the usage\_type field specifies a permission classification for signalling and carrying usage class information.
+- Store type expresses an accumulation form of contents in the target domains and conformance devices. Possible values are "fixation" and "non-fixation". For example, if the value is "fixation", the content can be stored in conforming devices.
+  - Clause 5.6.11.2 in [IEC 62227] on the usage\_type field specifies a permission classification for signalling and carrying usage class information.
+- Reuse type expresses the secondary usage type of contents in target domains and compliant devices. Possible values are enable or disable secondary usage, move, copy, export, share, edit, modify and super distribution.
+  - The following clauses in [IEC 62227] specify a permission classification for signalling and carrying usage class information: 5.6.11.4 for the move\_flag field, 5.6.11.5 for the copy\_flag field, 5.6.11.6 for the export\_flag field, 5.6.11.7 for the share\_flag field, 5.6.11.8 for the edit\_flag field, 5.6.11.9 for the modify\_flag field, and 5.6.11.10 for the super\_distribution\_flag field.
+- Redistribution type expresses the forwarding type of contents from target domains and compliant devices (e.g., enable or disable).
+  - Clause 5.6.11.3 in [IEC 62227] specifies the redistribution\_type field on permission classification for signalling and carrying usage class information.
+
+### 8.7 Compilation class
+
+Compilation class includes classification indicating content whether or not the permission issuer is allowed to combine and sell multiple pieces of content. It is required to ensure consistency in playback with playlist. Possible values are true if play-list enable, false if play-list disable and other.
+
+Clause 5.7.3.2.6 in [IEC 62227] specifies the playlist\_parameter field on permission conditions for signalling and carrying compilation information.
+
+## 9 Permission limit components
+
+Permission limit components include information indicating the restriction of the permission conditions that is described in the permission classification. It can be described for restricting the conditions indicated in the permission agreement.
+
+### 9.1 General usage condition
+
+General usage condition is an element comprising a usage form and its limit conditions under which the content can be permitted to be used in target domains and compliant devices. It includes information restricting the usage condition for content consumption such as playback usage, print usage and execution usage.
+
+Playback usage is an element of the usage form that the content can be rendered temporarily under keeping perceptible. Playback usage condition expresses the limit that the content can be permitted to playback in target domains and compliant devices.
+
+Clause 5.7.3.2 of [IEC 62227] on playback usage condition descriptor specifies a permission constraint for signalling and carrying playback condition.
+
+Print usage is an element of the usage form that the content can be rendered permanently on the physically fixed object. Print usage condition expresses the limit that the content can be permitted to print in target domains and compliant devices.
+
+Clause 5.7.3.3 of [IEC 62227] on print usage condition descriptors specifies a permission constraint for signalling and carrying print condition.
+
+Execution usage is an element of the usage form that the content can be rendered temporarily with the calculation process. Execution usage condition expresses the limit that the content can be permitted to execute in target domains and compliant devices.
+
+Clause 5.7.3.4 of [IEC 62227] on execute usage condition descriptors specifies a permission constraint for signalling and carrying execution condition.
+
+#### 9.1.1 Quality limits
+
+Component **quality limits** includes information indicating the quality of distributed content. Permission issuers typically represent it as qualitative levels such as LEVEL1 (high quality), LEVEL2 (standard quality), LEVEL3 (low quality) and LEVEL4 (other). For example if the value is "LEVEL1", the content can be permitted to use (play, print or execute) with the best quality. Possible values are "LEVEL1", "LEVEL2", "LEVEL3" and "LEVEL4":
+
+- Clause 5.7.3.2.4 of [IEC 62227] defines the quality\_parameter field on quality condition for playback usage (high quality, standard, low quality, and extension).
+- Clause 5.7.3.3.4 of [IEC 62227] defines the quality\_parameter field on quality conditions for print usage (high quality, standard, low quality, and extension).
+- Clause 5.7.3.4.4 of [IEC 62227] defines the service\_level\_parameter field on quality conditions for execution usage (full control, standard, trial and extension).
+
+#### 9.1.2 Lifetime limits
+
+Component **lifetime limits** includes information indicating the usage lifetime of distributed content. Permission issuers typically specify a time period, a day count or a date range.
+
+Elements required in **lifetime limits** are as follows:
+
+- Time period expresses the number of hours during which use (play, print or execute) of the content is permitted in target domains and compliant devices. For example, if the value is 24, the content can be used for 24 hours after received in a compliant device. Possible values are natural numbers and the unit is hour (e.g., 24 hours, 48 hours).
+  - Various clauses of [IEC 62227] apply. Clause 5.7.3.2.13 defines the time\_period\_parameter field that can be used to describe the element for the same meaning on playback usage. Clause 5.7.3.3.11 defines the time\_period\_parameter field that can be used to describe the element for the same meaning on print usage. Clause 5.7.3.4.12 defines the time\_period\_parameter field that can be used to describe the element for the same meaning on playback usage.
+- Day count expresses the number of days during which use (play, print or execute) of the content is permitted in target domains and compliant devices. For example, if the value is 7, the content can be used for 7 days after received in a compliant device. Possible values are natural values and the unit is day (e.g., 1 day, 7 days).
+  - Various clauses of [IEC 62227] apply. Clause 5.7.3.2.14 defines the day\_count\_parameter field that can be used to describe the element for the same meaning on playback usage. Clause 5.7.3.3.12 defines the day\_count\_parameter field that can be used to describe the element for the same meaning on print usage. Clause 5.7.3.4.12 defines the day\_count\_parameter field that can be used to describe the element for the same meaning on execution usage.
+- Date period expresses a date range during which use (play, print or execute) of the content is permitted in target domain and compliant devices. Possible values are dates (start date and end date) and the unit is date (e.g., period from start date to end date). For example, if the value is from 2010/11/01 to 2010/11/30, the content can be used from 1 to 30 November 2010.
+  - Various clauses of [IEC 62227] apply. Clause 5.7.3.2.15 defines the start\_date\_parameter field that can be used to describe the element for the same meaning on playback usage. Clause 5.7.3.3.13 defines the start\_date\_parameter field that can be used to describe the element for the same meaning on print usage. Clause 5.7.3.4.14 defines the start\_date\_parameter field that can be used to describe the element for the same meaning on playback usage.
+  - Various clauses of [IEC 62227] apply. Clause 5.7.3.2.16 defines the end\_date\_parameter field that can be used to describe the element for the same meaning on playback usage. Clause 5.7.3.3.14 defines the end\_date\_parameter field that can be used to describe the element for the same meaning on print usage. Clause 5.7.3.4.15 defines the end\_date\_parameter field that can be used to describe the element for the same meaning on playback usage.
+
+#### 9.1.3 Permission management system limits
+
+Component **permission management system limits** include information indicating which content management method should be used for the permission management, such as digital watermark, rights report and digital copy protection.
+
+For example, if the value is "digital copy protection", a compliant device is required to protect the content using a SCP system on its usage time (playing, printing or executing). Possible values are
+
+"digital copy protection", "digital watermark" and "rights report". It may take a value of  $-1$  for "other" meaning.
+
+Various clauses of [IEC 62227] apply. Clause 5.7.3.2.5 (permission\_management\_model\_parameter) can be used to describe the element for the same meaning on playback usage. Clause 5.7.3.3.5 (permission\_management\_model\_parameter) can be used to describe the element for the same meaning on print usage. Clause 5.7.3.4.5 (permission\_management\_model\_parameter) can be used to describe the element for the same meaning on execute usage.
+
+#### 9.1.4 Simultaneous output limits
+
+Component **simultaneous output limits** includes information indicating the permitted number of simultaneous output for each content consumption. For example, if the value is 2, a compliant device is permitted to simultaneously export the content toward two displays during its allowed usage time (playing, printing or executing). Valid values are non-negative integers, and  $-1$  to designate "other".
+
+Clause 5.7.3.2.17 of [IEC 62227] defines the simultaneous\_output\_parameter field that can be used to describe the element for the same meaning on playback usage.
+
+### 9.2 Extended usage condition
+
+Extended usage condition includes information indicating the extended condition to the regular usage condition. This condition is for further study.
+
+## 10 Data management condition
+
+Data management condition includes information indicating the condition that is subject to saving the original content or re-issuing permissions. The device shall be able to control consumption by end-users of a variety of services and contents under the specific conditions described for data management.
+
+Permission issuers typically specify encryption flag, copy count, transcode type, expiration date, and other usage condition about the data management.
+
+Elements required in data management condition are listed below.
+
+- Encryption flag indicates whether the content needs to be encrypted or not. Possible values are true if encryption is required, false if encryption is not required and other.
+  - Clause 5.9.3.3 of [IEC 62227] (encryption\_flag) can be used to describe the element for the same meaning.
+- Copy count expresses the number of times that the content can be permitted to copy in target domains and compliant devices. If the value is 1, there can be two copies including the original one. Possible values are non-negative integers and  $-1$  to designate "other".
+  - Clause 5.9.3.4 of [IEC 62227] on copy count can be used to describe the element for the same meaning.
+- Move count expresses the number of times that the content can be permitted to mobile in target domains and compliant devices. "Move" usually means a combination of copying the content and deleting the original one. Possible values are non-negative integers and  $-1$  to designate "other".
+  - Clause 5.9.3.5 of [IEC 62227] on move count can describe the element for the same meaning.
+- Transcode type expresses the type of transcoding in which the content can be permitted to be stored in target domains and compliant devices. Examples of possible values are found in Appendix VI.
+
+- Clause 5.9.3.6 of [IEC 62227] on transcode type can describe the element for the same meaning.
+- Maximum transcode rate expresses the highest bit rate at which the content is permitted to be transcoded for storing in target domains and compliant devices. Possible values are non-negative real numbers and the unit is kbit/s.
+  - Clause 5.9.3.7 of [IEC 62227] on maximum transcode rate can describe the element for the same meaning.
+- Minimum transcode rate expresses the lowest bit rate at which the content is permitted to be transcoded for storing in target domains and compliant devices. Possible values are non-negative real numbers and the unit is kbit/s.
+  - Clause 5.9.3.8 of [IEC 62227] on minimum transcode rate can describe the element for the same meaning.
+- Expiration date expresses the limit date until which the content is permitted to be stored in target domains and compliant devices. Possible values are dates, using the date format defined in [ITU-T H.750].
+  - Clause 5.9.3.9 of [IEC 62227] on expiration date can describe the element for the same meaning.
+- Sublicense count expresses the number of times sub-licenses are permitted to be issued in target domains and compliant devices. Possible values are non-negative integers.
+  - Clause 5.9.3.10 of [IEC 62227] on sublicense count can describe the element for the same meaning.
+- Time-line edit flag indicates whether editing the content with respect to a time-line (i.e., the content is shortened time-wise) and saving the resulting content is permitted. Possible values are `true` (time-line edit enabled), `false` (time-line edit disabled) and `other`.
+  - Clause 5.9.3.11 of [IEC 62227] on time-line edit can describe the element for the same meaning.
+
+## 11 Data export condition
+
+The data export condition includes information indicating the conditions to which the export of the original content to non-compliant objects is subjected. The device shall be able to control end-user consumption of a variety of services and content under the specific conditions described for data export.
+
+Permission issuers typically specify storage media, encoding type, control type, time period, day count, date period, and other usage conditions regarding content export.
+
+The elements required in data export condition are as follows:
+
+- Encryption flag indicates indicate whether the content needs to be encrypted or not. Possible values are `true` (encryption required), `false` (encryption not required), and `other`.
+  - Clause 5.9.3.3 of [IEC 62227] (`encryption_flag`) can be used to describe the element for the same meaning.
+- Copy count expresses the number of times the content can be permitted to be copied in target domains and compliant devices. Possible values are non-negative integers and `-1` to designate "other". For example, if the value is 1, there can be two copies, including the original one.
+  - Clause 5.9.3.4 of [IEC 62227] on copy count can be used to describe the element for the same meaning.
+
+- Move count expresses the number of times that the content can be permitted to be moved in target domains and compliant devices. "Move" usually means a combination of copying the content and deleting original one. Possible values are non-negative integers and –1 to designate "other".
+  - Clause 5.9.3.5 of [IEC 62227] on move count can be used to describe the element for the same meaning.
+- Transcode type expresses the type of transcoding in which the content can be permitted to be stored in the target domain and compliant devices. Examples of possible values are found in Appendix VI.
+  - Clause 5.9.3.6 of [IEC 62227] on transcode type can be used to describe the element for the same meaning.
+- Maximum transcode rate expresses the highest bit rate at which the content may be transcoded for storage in the target domain and compliant devices. Possible values are non-negative real numbers and the unit is kbit/s.
+  - Clause 5.9.3.7 of [IEC 62227] on maximum transcode rate can be used to describe the element for the same meaning.
+- Minimum transcode rate expresses the lowest bit rate at which the content may be transcoded for storage in target domains and compliant devices. Possible values are non-negative real numbers and the unit is kbit/s.
+  - Clause 5.9.3.8 of [IEC 62227] on minimum transcode rate can be used to describe the element for the same meaning.
+- Expiration date expresses the limit date until which the content may be stored in target domains and compliant devices. The possible value is date, formatted as defined in [ITU-T H.750].
+  - Clause 5.9.3.9 of [IEC 62227] on expiration date can be used to describe the element for the same meaning.
+- Sublicense count expresses the number of times for which sub-licenses can be issued in target domains and compliant devices. Possible values are non-negative integers.
+  - Clause 5.9.3.10 of [IEC 62227] on sub-license count can be used to describe the element for the same meaning.
+- Time-line edit flag indicates whether editing the content with respect to a time-line (i.e., the content is shortened time-wise) and saving the resulting content is permitted. Possible values are true (time-line edit enabled), false (time-line edit disabled) and other.
+  - Clause 5.9.3.11 of [IEC 62227] on time-line edit can be used to describe the element for the same meaning.
+
+## Appendix I
+
+## Security-related issues
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### I.1 Tamper detection
+
+#### I.1.1 General
+
+Since distribution format data representing digital rights permissions require screening to detect whether or not they have been falsified by anyone, they must include a digital signature.
+
+The elliptic curve digital signature algorithm (EC-DSA) with secure hash algorithm (SHA) and the Rivest Shamir Adleman (RSA)/DSA with SHA are given as applicable examples of digital signature algorithms. The concrete standard of the signature is implementation-dependent.
+
+The basic composition of distribution format data is depicted in Table I.1.
+
+**Table I.1 – Basic composition of distribution format data**
+
+| Description                                                                                                                            | Digital rights permissions data              | Digital signature                                                                                                                     | Certificate or PkiPath                                                      |
+|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|
+| Relevant information:<br>– Position in the PkiPath hierarchy<br>– Signature algorithm<br>– Key length<br>– Encryption parameters, etc. | Data representing digital rights permissions | Digital signature of digital rights permissions data, which is generated through algorithm and standard specified in the description. | Certificate or chain of certificates to authenticate the digital signature. |
+
+#### I.1.2 Authentication
+
+The issuer of digital rights permissions data generates a public/private key pair and obtains a certificate of the public key from the appropriate certification authority.
+
+The issuer generates the digital signature of the digital rights permissions data by using the above private key, and makes the distribution format data by adding the signature and the certificate to the digital rights permissions data.
+
+Standards of certificates for digital signature of digital rights permissions data are to comply with [b-ITU-T X.509].
+
+If the certificate contains a certificate chain, PkiPath defined in [b-ITU-T X.509] is used.
+
+![A hierarchical diagram of a PKI path. At the top is 'Root CA'. Below it are 'Certificate for CA1' and 'Certificate for CA2'. 'Certificate for CA1' points to 'Certificate for rights permissions data issuer1'. 'Certificate for CA2' points to 'Certificate for rights permissions data issuer2'. A 'PkiPath' box contains two certificates: 'Certificate for CA2 issued by Root CA' and 'Certificate for digital rights permissions data issuer2 issued by CA2'. Arrows show the flow from Root CA to the PkiPath box, and from the PkiPath box to 'Certificate for rights permissions data issuer2'. A legend at the bottom left defines 'CA: Certification Authority'. A label 'H.751(13)_Fl.1' is at the bottom right.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg)
+
+```
+
+graph TD
+    RootCA[Root CA] --> CertCA1[Certificate for CA1]
+    RootCA --> CertCA2[Certificate for CA2]
+    CertCA1 --> Issuer1[Certificate for rights permissions data issuer1]
+    CertCA2 --> Issuer2[Certificate for rights permissions data issuer2]
+    subgraph PkiPath
+        direction TB
+        P1[Certificate for CA2 issued by Root CA]
+        P2[Certificate for digital rights permissions data issuer2 issued by CA2]
+    end
+    RootCA --> PkiPath
+    PkiPath --> Issuer2
+    CA[CA: Certification Authority]
+    H751[H.751(13)_Fl.1]
+  
+```
+
+A hierarchical diagram of a PKI path. At the top is 'Root CA'. Below it are 'Certificate for CA1' and 'Certificate for CA2'. 'Certificate for CA1' points to 'Certificate for rights permissions data issuer1'. 'Certificate for CA2' points to 'Certificate for rights permissions data issuer2'. A 'PkiPath' box contains two certificates: 'Certificate for CA2 issued by Root CA' and 'Certificate for digital rights permissions data issuer2 issued by CA2'. Arrows show the flow from Root CA to the PkiPath box, and from the PkiPath box to 'Certificate for rights permissions data issuer2'. A legend at the bottom left defines 'CA: Certification Authority'. A label 'H.751(13)\_Fl.1' is at the bottom right.
+
+**Figure I.1 – Example of PkiPath**
+
+Figure I.1 shows an example of PkiPath. The depth of the PkiPath hierarchy depends on how each service or system is implemented. This information needs to be specified in the description area of the distribution format data.
+
+#### I.1.3 Signature
+
+The following algorithms are applicable for signature generation and verification:
+
+- EC-DSA with SHA
+- RSA/DSA with SHA
+
+The key lengths and encryption parameters of EC-DSA, RSA/DSA and SHA depend on the implementation of each service or system. This information needs to be specified in the description area of the distribution format data.
+
+### I.2 Keeping secret
+
+The decision as to whether distribution format data representing digital rights permissions is to be kept secret is either service or system dependent.
+
+If the digital rights permissions data have to be kept secret, the protection mechanism will be service or system dependent, and is outside the scope of this Recommendation.
+
+# Appendix II
+
+## Syntax (encoding)
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### II.1 General
+
+Considering the implementation of IPTV services, metadata need to be encoded by a common standardized format. Interoperability requires that the representation scheme of rights-related metadata be based on a common syntax. This clause shows the typical 23 use-cases scenarios that are described in [b-IEC 62636]:
+
+- Content purchase
+- Rental with time or playback limit
+- Subscription
+- Two scenarios on direct retrieval of content from a device
+- Unlimited play
+- Preview
+- Multiple permissions for a multipart content format
+- Inheritance
+- Export of content
+- Combinations of constraint elements
+- Recordable media
+- Ringtones
+- Download or streaming of free content with advertising
+- Giveaways
+- Coupons (discount points)
+- Privacy information disclosure
+- Copying nine times with unlimited moving
+- Subscription games
+- Software rental
+
+In the next clause, these scenarios are divided into permission conditions tables using the syntax in [IEC 62227].
+
+### II.2 Digital rights permission code syntaxes tables of the 23 scenarios
+
+This clause shows digital rights permission code (DRPC) [IEC 62227] syntax tables of the 23 scenarios above that expand the four main elements (ContentID, IssuerID, Receiver ID and Permission conditions) into the sub-elements that specify the practical value for each element in the scenarios (see Tables II.1 to II.6).
+
+In the subscription example scenario, there are three different permission codes: one parent permission code (which represents a permission condition of a subscription contract itself) and two children permission codes (which represent permission conditions of music contents). Further, it is assumed that Receiver ID has the fixed value "HJPC010000000001".
+
+**Table II.1 – Permission actors and permission classifications**
+
+| NO | Content ID       | Scenario                                              | Disclosure Class | Usage Purpose Class | Charge Model Class      | Billing Class | Application Class | Sponsor Class                    | Territory Class | Usage Class                                 | Receiver ID      |
+|----|------------------|-------------------------------------------------------|------------------|---------------------|-------------------------|---------------|-------------------|----------------------------------|-----------------|---------------------------------------------|------------------|
+| 1  | SMJP010000000201 | Content purchase                                      | Open             | Commercial          | Fee-based               | Individual    | Individual        | No Sponsor                       | Reserved        | Download, Reuse, Move, Copy, Export         | UJP1010000000101 |
+| 2  | VPJP010000000202 | Rental with time or playback limit                    | Open             | Commercial          | Fee-based               | Individual    | Individual        | No Sponsor                       | Reserved        | Download                                    | UJP1010000000101 |
+| 3  | SMJP010000000210 | Subscription                                          | Open             | Commercial          | Fee-based, Subscription | Individual    | Individual        | No Sponsor                       | Reserved        | Download, Reuse, Copy                       | UJP1010000000101 |
+| 4  | SMJP010000000211 | Subscription child 1                                  | Open             | Commercial          | Fee-based, Subscription | Individual    | Individual        | No Sponsor                       | Reserved        | Download, Reuse, Copy                       | UJP1010000000101 |
+| 5  | SMJP010000000212 | Subscription child 2                                  | Open             | Commercial          | Fee-based, Subscription | Individual    | Individual        | No Sponsor                       | Reserved        | Download, Reuse, Copy                       | UJP1010000000101 |
+| 6  | SMJP010000000221 | Direct retrieval of content from a device: Scenario 1 | Open             | Commercial          | Fee-based               | Individual    | Individual        | No Sponsor                       | Reserved        | Download                                    | UJP010000000101  |
+| 7  | VFJP010000000222 | Direct retrieval of content from a device: Scenario 2 | Open             | Commercial          | Fee-based               | Individual    | Individual        | No Sponsor                       | Reserved        | Streaming                                   | UJP010000000101  |
+| 8  | VPJP010000000301 | Unlimited play                                        | Open             | Commercial          | Fee-based               | Individual    | Individual        | No Sponsor                       | Reserved        | Download, Reuse, Copy                       | UJP1010000000101 |
+| 9  | VPJP010000000302 | Preview                                               | Open             | Commercial          | Fee-based               | Individual    | Individual        | No Sponsor                       | Reserved        | Streaming                                   | UJP1010000000101 |
+| 10 | TMJP010000000303 | Multiple permissions for a multipart DCF (Lyrics)     | Open             | Commercial          | Fee-based               | Individual    | Individual        | No Sponsor                       | Reserved        | Download                                    | UJP010000000101  |
+| 11 | SMJP010000000303 | Multiple permissions for a multipart DCF (Song)       | Open             | Commercial          | Fee-based               | Individual    | Individual        | No Sponsor                       | Reserved        | Download                                    | UJP010000000101  |
+| 12 | TMJP010000000304 | Inheritance                                           | Open             | Commercial          | Free                    | Individual    | Individual        | No Sponsor                       | Reserved        | Streaming                                   | UJP010000000101  |
+| 13 | VPJP010000000305 | Export of OMA DRM content                             | Open             | Commercial          | Fee-based               | Individual    | Individual        | No Sponsor                       | Reserved        | Download, Reuse, Export                     | UJP010000000101  |
+| 14 | VPJP010000000306 | Combinations of constraint elements                   | Open             | Commercial          | Fee-based               | Individual    | Individual        | No Sponsor                       | Reserved        | Streaming                                   | UJP010000000101  |
+| 15 | VPJP010000000501 | FairPlay                                              | Open             | Commercial          | Fee-based               | Individual    | Individual        | No Sponsor                       | Reserved        | Download, Reuse, Copy, Export               | UJP1010000000101 |
+| 16 | VPJP010000000502 | CPRM                                                  | Open             | Commercial          | Fee-based               | Individual    | Individual        | No Sponsor                       | Reserved        | Download, Reuse, Export                     | UJP1010000000101 |
+| 17 | VPJP010000000503 | SAFIA                                                 | Open             | Commercial          | Fee-based               | Individual    | Individual        | No Sponsor                       | Reserved        | Download, Reuse, Copy, Export               | UJP1010000000101 |
+| 18 | SMJP010000000504 | Ringtones                                             | Open             | Commercial          | Fee-based               | Individual    | Individual        | No Sponsor                       | Reserved        | Download, Reuse, Copy, Export               | UJP010000000101  |
+| 19 | VPJP010000000601 | Download of content free with advertising             | Open             | Commercial          | Free                    | Individual    | Individual        | Time-synchronized Forced Viewing | Reserved        | Download, Reuse, Copy                       | UJP1010000000101 |
+| 20 | VPJP010000000602 | Streaming of content free with advertising            | Open             | Commercial          | Free                    | Individual    | Individual        | Time-synchronized Forced Viewing | Reserved        | Streaming                                   | UJP1010000000101 |
+| 21 | VPJP010000000603 | Giveaways                                             | Open             | Commercial          | Free                    | Individual    | Individual        | Giveaway Model                   | Reserved        | Download, Reuse, Copy                       | UJP1010000000101 |
+| 22 | VPJP010000000604 | Coupons (discount points)                             | Open             | Commercial          | Free                    | Individual    | Individual        | Coupon Model                     | Reserved        | Download, Reuse, Copy                       | UJP1010000000101 |
+| 23 | VPJP010000000605 | Privacy information disclosure                        | Open             | Commercial          | Free                    | Individual    | Individual        | Advertising Model                | Reserved        | Streaming                                   | UJP1010000000101 |
+| 24 | VPJP010000000701 | Copying 9 times with unlimited moving                 | Open             | Commercial          | Fee-based               | Individual    | Individual        | No Sponsor                       | Reserved        | Fixed Broadcast Delivery, Reuse, Move, Copy | UJP1010000000101 |
+| 25 | PGJP010000000101 | Subscription games                                    | Open             | Commercial          | Fee-based               | Individual    | Individual        | No Sponsor                       | Reserved        | Download                                    | UJP1010000000101 |
+| 26 | PSJP010000000101 | Software rental                                       | Open             | Commercial          | Fee-based               | Individual    | Individual        | No Sponsor                       | Reserved        | Download                                    | UJP1010000000101 |
+
+**Table II.2 – Playback usage conditions**
+
+| NO | Content ID      | Quality Parameter           | DRM | Playlist | Num of Playback | Num of Playback Hours | Num of Playback Days | Playback Period                      | Simultaneous Output | Parental Guidance | Countable Time (Seconds) |
+|----|-----------------|-----------------------------|-----|----------|-----------------|-----------------------|----------------------|--------------------------------------|---------------------|-------------------|--------------------------|
+| 1  | SMJP01000000201 | LEVEL1,LEVEL2,LEVEL3,LEVEL4 | DRM | Allow    |                 |                       |                      |                                      |                     | General           |                          |
+| 2  | VPJP01000000202 | LEVEL1,LEVEL2,LEVEL3        | DRM | Forbid   | 240.00:00       | 48:0:0                |                      | 2008/03/26 0:0:0-2008/03/29 11:59:59 |                     | General           | 30                       |
+| 3  | SMJP01000000210 | LEVEL1,LEVEL2,LEVEL3        | DRM | Allow    |                 |                       |                      |                                      |                     | General           |                          |
+| 4  | SMJP01000000211 | LEVEL1,LEVEL2,LEVEL3        | DRM | Allow    |                 |                       |                      |                                      |                     | General           |                          |
+| 5  | SMJP01000000212 | LEVEL1,LEVEL2,LEVEL3        | DRM | Allow    |                 |                       |                      |                                      |                     | General           |                          |
+| 6  | SMJP01000000221 | LEVEL1,LEVEL2,LEVEL3        | DRM | Allow    |                 |                       |                      |                                      |                     | General           |                          |
+| 7  | VFJP01000000222 | LEVEL1,LEVEL2,LEVEL3        | DRM | Allow    |                 |                       |                      |                                      |                     | General           |                          |
+| 8  | VPJP01000000301 | LEVEL1,LEVEL2,LEVEL3,LEVEL4 | DRM | Allow    |                 |                       |                      |                                      |                     | General           |                          |
+| 9  | VPJP01000000302 | LEVEL1,LEVEL2,LEVEL3        | DRM | Allow    | 24:00:00        |                       |                      |                                      |                     | General           | 30                       |
+| 10 | TMJP01000000303 | LEVEL1,LEVEL2,LEVEL3,LEVEL4 | DRM | Forbid   | 24:00:00        |                       |                      |                                      |                     | General           | 30                       |
+| 11 | SMJP01000000303 | LEVEL1,LEVEL2,LEVEL3,LEVEL4 | DRM | Forbid   | 24:00:00        |                       |                      |                                      |                     | General           | 30                       |
+| 12 | TMJP01000000304 | LEVEL1,LEVEL2,LEVEL3,LEVEL4 | DRM | Forbid   | 72:00:00        |                       |                      | 2008/09/01 0:0:0-2008/09/30 11:59:59 |                     | General           | 30                       |
+| 13 | TMJP01000000304 | LEVEL1,LEVEL2,LEVEL3        | DRM | Forbid   | 240:00:00       |                       |                      | 2008/07/01 0:0:0-2008/08/31 11:59:59 |                     | General           | 30                       |
+| 14 | VPJP01000000305 | LEVEL1,LEVEL2,LEVEL3,LEVEL4 | DRM | Allow    |                 |                       |                      |                                      |                     | General           |                          |
+| 15 | VPJP01000000306 | LEVEL1,LEVEL2,LEVEL3        | DRM | Forbid   | 48:00:00        | 0:30:00               |                      | 2008/05/01 0:0:0-2008/06/30 11:59:59 |                     | General           | 30                       |
+| 16 | VPJP01000000306 | LEVEL1,LEVEL2,LEVEL3        | DRM | Forbid   | 240:00:00       | 0:00:30               |                      | 2008/04/01 0:0:0-2008/06/30 11:59:59 |                     | General           | 30                       |
+| 17 | VPJP01000000501 | LEVEL1,LEVEL2,LEVEL3        | DRM | Allow    |                 |                       |                      |                                      |                     | General           |                          |
+| 18 | VPJP01000000502 | LEVEL1,LEVEL2,LEVEL3        | DRM | Allow    |                 |                       |                      |                                      |                     | General           |                          |
+| 19 | VPJP01000000503 | LEVEL1,LEVEL2,LEVEL3        | DRM | Allow    |                 |                       |                      |                                      |                     | General           |                          |
+| 20 | SMJP01000000504 | LEVEL1,LEVEL2,LEVEL3        | DRM | Allow    |                 |                       |                      |                                      |                     | General           |                          |
+| 21 | VPJP01000000601 | LEVEL1,LEVEL2,LEVEL3,LEVEL4 | DRM | Forbid   |                 |                       |                      |                                      |                     | General           |                          |
+| 22 | VPJP01000000602 | LEVEL1,LEVEL2,LEVEL3        | DRM | Forbid   |                 |                       |                      |                                      |                     | General           |                          |
+| 23 | VPJP01000000603 | LEVEL1,LEVEL2,LEVEL3        | DRM | Allow    |                 |                       |                      |                                      |                     | General           |                          |
+| 24 | VPJP01000000604 | LEVEL1,LEVEL2,LEVEL3        | DRM | Allow    |                 |                       |                      |                                      |                     | General           |                          |
+| 25 | VPJP01000000605 | LEVEL1,LEVEL2,LEVEL3        | DRM | Allow    |                 |                       |                      |                                      |                     | General           |                          |
+| 26 | VPJP01000000701 | LEVEL1,LEVEL2,LEVEL3        | DRM | Allow    |                 |                       |                      |                                      |                     | 1 General         |                          |
+
+**Table II.3 – Printout usage conditions**
+
+| Content ID | Quality Parameter | Permission Management Type  | Num of Printouts | Num of Printout Hours | Num of Printout Days | Printout Period                      | Parental Guidance |
+|------------|-------------------|-----------------------------|------------------|-----------------------|----------------------|--------------------------------------|-------------------|
+| 10         | TMJP01000000303   | LEVEL1,LEVEL2,LEVEL3        | DRM              | 1                     |                      |                                      | General           |
+| 12         | TMJP01000000304   | LEVEL1,LEVEL2,LEVEL3,LEVEL4 | DRM              | 10                    |                      | 2008/09/01 0:0:0-2008/09/30 11:59:59 | General           |
+| 12         | TMJP01000000304   | LEVEL1,LEVEL2,LEVEL3,LEVEL4 | DRM              | 3                     |                      | 2008/09/01 0:0:0-2008/09/30 11:59:59 | General           |
+
+**Table II.4 – Execution usage conditions**
+
+| Content ID | Quality Parameter | Permission Management Type | Num of Executions | Num of Execution Hours | Num of Execution Days | Execution Period                     | Parental Guidance | Countable Time (Seconds) |
+|------------|-------------------|----------------------------|-------------------|------------------------|-----------------------|--------------------------------------|-------------------|--------------------------|
+| 25         | PGJP01000000101   | LEVEL1,LEVEL2,LEVEL3       | DRM               |                        |                       | 2008/06/20 0:0:0-2008/06/27 23:59:59 | General           |                          |
+| 26         | PSJP01000000101   | LEVEL1,LEVEL2,LEVEL3       | DRM               |                        |                       | 2008/06/20 0:0:0-2008/06/30 23:59:59 | General           |                          |
+
+**Table II.5 – Data management conditions**
+
+| NO | Content ID      | Target ID       | Encryption Flag | Copy Count | Move Count | Transcode Type | Maximum Transcode Rate | Minimum Transcode Rate | Expiration Date     | Sublicense Count | Timeline Edit |
+|----|-----------------|-----------------|-----------------|------------|------------|----------------|------------------------|------------------------|---------------------|------------------|---------------|
+| 1  | SMJP01000000201 | UJPD01000000201 | TRUE            | ff         | 0          |                |                        |                        | 2008/09/26 0:0:0    | 0                | Forbid        |
+| 2  | VPJP01000000202 | UJPD01000000101 | TRUE            | 0          | 1          |                |                        |                        | 2008/12/31 0:0:0    | 0                | Forbid        |
+| 3  | SMJP01000000210 | UJPD01000000201 | TRUE            | 0          | 0          |                |                        |                        | 2008/07/31 0:0:0    | 0                | Forbid        |
+| 6  | SMJP01000000221 | UJPD01000000101 | TRUE            | 0          | 0          |                |                        |                        | 9999/12/31 0:0:0    | 0                | Forbid        |
+| 8  | VPJP01000000301 |                 | TRUE            | ff         | 0          |                |                        |                        | 9999/12/31 0:0:0    | 0                | Allow         |
+| 10 | TMJP01000000303 | UJPD01000000101 | TRUE            | 0          | 0          |                |                        |                        | 9999/12/31 0:0:0    | 0                | Forbid        |
+| 11 | SMJP01000000303 | UJPD01000000101 | TRUE            | 0          | 0          |                |                        |                        | 9999/12/31 0:0:0    | 0                | Forbid        |
+| 12 | TMJP01000000304 | UJPD01000000101 | TRUE            | 0          | 0          |                |                        |                        | 9999/12/31 0:0:0    | 0                | Forbid        |
+| 15 | VPJP01000000501 | UJPD01000000201 | TRUE            | ff         | 0          |                |                        |                        | 2009/03/26 0:0:0    | ff               | Forbid        |
+| 17 | VPJP01000000503 |                 | TRUE            | ff         | 0          |                |                        |                        | 9999/12/31 0:0:0    | 0                | Allow         |
+| 18 | SMJP01000000504 | UJPD01000000201 | TRUE            | ff         | 0          |                |                        |                        | 9999/12/31 0:0:0    | 0                | Forbid        |
+| 19 | VPJP01000000601 | UJPD01000000201 | TRUE            | ff         | 0          |                |                        |                        | 9999/12/31 0:0:0    | 0                | Forbid        |
+| 21 | VPJP01000000603 | UJPD01000000201 | TRUE            | ff         | 0          |                |                        |                        | 9999/12/31 0:0:0    | 0                | Forbid        |
+| 22 | VPJP01000000604 | UJPD01000000201 | TRUE            | ff         | 0          |                |                        |                        | 9999/12/31 0:0:0    | 0                | Forbid        |
+| 23 | VPJP01000000605 | UJPD01000000201 | TRUE            | ff         | 0          |                |                        |                        | 9999/12/31 0:0:0    | 0                | Forbid        |
+| 24 | VPJP01000000701 |                 | TRUE            | 9          | ff         |                |                        |                        | 9999/12/31 0:0:0    | 0                | Allow         |
+| 25 | PGJP01000000101 | UJPD01000000101 | FALSE           | 0          | 0          |                |                        |                        | 2008/06/30 23:59:59 | 0                | Forbid        |
+| 26 | PSJP01000000101 | UJPD01000000101 | FALSE           | 0          | 0          |                |                        |                        | 2008/06/30 23:59:59 | 0                | Forbid        |
+
+**Table II.6 – Data output conditions**
+
+| Data export condition |                  |                    |               |                 |              |                     |              |             |           |               |
+|-----------------------|------------------|--------------------|---------------|-----------------|--------------|---------------------|--------------|-------------|-----------|---------------|
+| NO                    | Content ID       | Storage Media Type | Encoding Type | Protection Type | Control Type | Move Indicator Flag | Export Count | Time Period | Day Count | Export Period |
+| 1                     | SMJP010000000201 | CD                 |               |                 |              |                     |              |             |           |               |
+| 13                    | VPJP010000000305 | DVD                | MPEG*2,H.264  | CPRM, DTCP      | Copy No More |                     | Copy 9       |             |           |               |
+| 15                    | VPJP010000000501 | CD                 |               |                 |              |                     |              |             |           |               |
+| 16                    | VPJP010000000502 | DVD                | MPEG*2,H.264  | CPRM            | Copy No More |                     | Copy 3       |             |           |               |
+| 17                    | VPJP010000000503 | HDD                |               | SAFIA           | Copy No More |                     | Copy 10      |             |           |               |
+| 18                    | SMJP010000000504 | Flash Memory       |               | CPRM            | Copy No More |                     | Copy 10      |             |           |               |
+
+## Appendix III
+
+## Background to rights information interoperability
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### III.1 General
+
+The distribution of digital content or copyrighted digital work has already been studied from various angles. From the standpoint of digital information distribution in particular, various service and content protection (SCP) systems have been offered, and various distribution models such as "superdistribution" have been proposed. Even though the technology and infrastructure to support digital distribution are now in place, no mechanisms or rules have been established for flexible digital distribution. Such flexible digital distribution would allow easy exchange of content based on individual commitments between content creators and consumers. The reality is that at present, a technological and social environment where there is a sense of trust between copyright holders and consumers who feel safe about information distribution is not always perfectly provided.
+
+Taking movies as a typical case, content creation is generally a group effort, and responsibilities are shared amongst various individuals. As a result, the financial and personal rights related to the final content, and the compensation that must be shared among those involved, are uncertain. Since no technology has yet been established for managing usage fees based on the volume of content consumed, it is difficult to say that appropriate compensation is being consistently distributed to all members of a group.
+
+The result is that while content creators want many more opportunities for their content to be used by consumers, there is no system that makes that possible. Consequently, appropriate permission commitments are not shown and all involved must accept lost opportunities. In addition, the development of technology for the fast-growing market of mobile phones and simple terminals that makes content available to consumers is progressing without interoperability across different service providers. Paradoxically, this results in more inconvenience for the consumer. Moreover, while SCP with a certain level of functionality is available, it does not necessarily meet the needs of consumers. Therefore, consumers are generally forced to purchase content in inconvenient ways, even though it is technologically possible to improve the user experience.
+
+Rights information interoperability (RII) makes it possible to study measures to resolve these problems from two standpoints. The first standpoint is that of engineering – building the infrastructure for a next generation of digital information distribution systems by developing technology that achieves a combination of interoperability and convenience for the consumer. The second is a legal one – building the social infrastructure for next generation rights processing by providing a new framework for the management and exchange of digital rights permission information among rights holders and consumers. RII specifies an ideal system that merges the two together and helps make interoperability a reality for groups of existing SCP systems scattered throughout the world (Figure III.1).
+
+![Diagram illustrating the concept of rights information interoperability across three layers: Layer 3 (Device I/F), Layer 2 (DRM I/F), and Layer 1 (Rights/legal I/F).](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg)
+
+The diagram illustrates a three-layer architecture for rights information interoperability. At the top, icons represent various devices: CDs, a satellite, a radio tower, a smartphone, a car, and a laptop. Below these is Layer 3: Device I/F. Layer 2: DRM I/F (i.e., REL I/F, OMA I/F, CPCM I/F) contains four boxes: 'DRM for Storage media', 'DRM for broadcasting distributor', 'DRM for broadband/mobile', and 'Non DRM (Peer to peer)'. Layer 1: Rights/legal I/F contains five content categories: 'Music', 'Movie/Video/Photo', 'Advertisement', 'Game/Software/E-book', and 'Other (i.e., News, medical info., patent info.)'. Each category has three sub-boxes labeled 'I', 'C', and 'O'. Blue lines connect the DRM boxes in Layer 2 to the corresponding 'I', 'C', and 'O' boxes in Layer 1. A legend at the bottom defines I: Individual, C: Company, and O: Organization. The code H.751(13)\_FIII.1 is in the bottom right.
+
+Diagram illustrating the concept of rights information interoperability across three layers: Layer 3 (Device I/F), Layer 2 (DRM I/F), and Layer 1 (Rights/legal I/F).
+
+**Figure III.1 – Concept: rights information interoperability**
+
+### III.2 Relationship between rights and digital permissions
+
+Digital rights permissions are the specific components by which rights are exercised.
+
+Holders of the rights defined in current copyright law do not contribute to content distribution if they do not effectively use those rights, even though they hold them. Unfortunately, in most situations where rights are currently exercised, digital rights permissions are often used as components for legal prosecution when rights are infringed.
+
+The action of granting digital rights permissions is an action that forms an agreement between (multiple) holders who hold declared rights and (multiple) holders who do not have rights according to copyright law, but who must confirm the granting or refusal of permissions for business usage. It also acknowledges that it is acceptable to enable specific content consumption services.
+
+Proper content distribution should include the mutual actions of granting and receiving digital rights permissions (without requiring a lot of time, if possible). Explicit rights and potential rights show that the rights holders agree that to comprehensively grant all permissions, it is acceptable to enable the specific content consumption services. If that is not confirmed, the situation is not one where digital rights permissions have been obtained. However, not all of these permissions can be confirmed in the various license agreements between the parties involved (see example below). This is where one arrives at the limitations of the law. What compensates for this is technology.
+
+Specifically:
+
+- Component a) code language technology that carries the shared elements that identify the scattered content and the parties associated with that content;
+- Component b) code language technology that carries the shared elements that identify information about the specific content consumption services.
+
+These two components convert the latest information about the multi-layered, intertwining contractual relationships into digital data and show that the rights holders agree that it is acceptable to enable the specific content consumption services for the content that has been converted to digital data. The services, applications and devices technologically interpret that agreement, and enable legal content consumption.
+
+RII is synonymous with management of continually updated digital rights permissions information. Components a) and b) above ensure that, as a minimum, all of the rights defined in the existing copyright law are expressed. It shall also assure future extensibility, meaning that it will be technologically possible to express any new, future agreement that it is acceptable to enable specific content consumption services.
+
+#### III.2.1 Example
+
+Representative rights holder B for film A grants the screening rights as stipulated in Japanese copyright law to a Chinese distributor.
+
+![](0eb742ed939b1846d05da644664fa9b7_img.jpg)
+
+↓
+
+Chinese consumer G enjoys film A that belongs to Japanese representative rights holder B.
+
+Streams it?
+
+Downloads it?
+
+Owns recording media?
+
+In other words, this cannot be expressed using currently existing legal techniques alone. For example, suppose that rights holder company H, who grants the rights permissions for film content A, enters into a business-to-business content usage license agreement with distributor U, who runs a downloading business; in this situation, it is not possible to capture all of the specific service formats in advance. In particular, if one imagines that services that are not yet known will be enabled in the future, the employees responsible for legal affairs must do everything they can to create increasingly dense and unreadable documents that predict forms of content consumption (this may be the case, but there are also limits to how much it is possible to enumerate the extended uses of fair use regulations and rights limit regulations). The physical license agreement generally states the specific conditions, or there is only a general agreement and an actual license agreement or contractual relationship does not exist. In that situation, prior to having a license agreement, it is critical to have information management for content consumption that is supported by technology in order to legally manage the forms of consumption targeted to more finely differentiated final consumers.
+
+Several situations may arise:
+
+- a) Cases where content that one owns and controls is enjoyed, and that form of consumption is agreed upon in a prior contractual relationship;
+- b) Cases where content that one owns and controls is enjoyed, and that form of consumption is not agreed upon in a prior contractual relationship:
+  - 1) cases where it is possible for permissions to be obtained after consumption; and
+  - 2) cases where it is not possible for permissions to be obtained after consumption.
+
+In future content distribution, it is desirable to have this information integrated in advance into the content in some format (without distinguishing between digital and analogue).
+
+# Appendix IV
+
+## Two basic technologies for enabling RII
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### IV.1 Code language technology that carries the shared elements that identify the scattered content and the parties associated with that content
+
+#### IV.1.1 General
+
+In this digital age, digital technology and networked environments are used, and there exists a wide variety of content, content creators and users. The information about them is recorded in the native language of each country as rights-related metadata, and on occasion this information is translated into another language. Even if the individual meaning it points to is the same, there are many cases where rights-related metadata multiplies or is duplicated. RII establishes code language technology that simplifies as much as these pieces of rights-related metadata possible and expresses their common elements.
+
+#### IV.1.2 Rights related metadata and simple tag ID code
+
+Rights related metadata is a general term for information surrounding and related to an object of consumption and enjoyment (film, music, photos, etc.), which is called content or a product, etc.
+
+Rights related metadata can be divided roughly into three types; the whole relationship is explained in Figure IV.1:
+
+- Open metadata: This metadata type comprises metadata that is made open to the public. Examples of open metadata include the product name, official author, etc.
+- Closed metadata: This metadata type comprises metadata that is shared only amongst the parties related to the transaction. Examples of closed metadata include the author's real name, royalty rates, bank info, etc.
+- Bridge metadata: Bridge metadata is the shared ID or detailed usage format code that ties together metadata groups a) and b) for joint management purposes.
+
+![Diagram illustrating the common semantics of metadata. A large light blue rounded rectangle labeled 'Rights related metadata' contains three components: 'Open metadata' (purple box), 'Bridge metadata' (green double-headed arrow), and 'Closed metadata' (yellow box). 'Open metadata' contains 'The content's catalogue information (holder, user and content information, etc.)'. 'Bridge metadata' contains 'IDs and conditions (content ID, rights holder ID, distributor ID, usage conditions)'. 'Closed metadata' contains 'Secret metadata (royalty information, personal information, etc.)'.](84e5b251aa38db522f76f5cc3afcb853_img.jpg)
+
+The diagram shows a large light blue rounded rectangle labeled "Rights related metadata". Inside this rectangle, there are three main components arranged horizontally: a purple box on the left labeled "Open metadata", a green double-headed arrow in the center labeled "Bridge metadata", and a yellow box on the right labeled "Closed metadata".
+
+- Open metadata** (purple box): The content's catalogue information (holder, user and content information, etc.)
+- Bridge metadata** (green double-headed arrow): IDs and conditions (content ID, rights holder ID, distributor ID, usage conditions)
+- Closed metadata** (yellow box): Secret metadata (royalty information, personal information, etc.)
+
+Diagram illustrating the common semantics of metadata. A large light blue rounded rectangle labeled 'Rights related metadata' contains three components: 'Open metadata' (purple box), 'Bridge metadata' (green double-headed arrow), and 'Closed metadata' (yellow box). 'Open metadata' contains 'The content's catalogue information (holder, user and content information, etc.)'. 'Bridge metadata' contains 'IDs and conditions (content ID, rights holder ID, distributor ID, usage conditions)'. 'Closed metadata' contains 'Secret metadata (royalty information, personal information, etc.)'.
+
+H.751(13)\_FIV.1
+
+Figure IV.1 – Common semantics of metadata
+
+Figure IV.2 shows a practical usage example of shared IDs in bridge metadata. As various rights holders are involved with content such as audiovisual work, the consolidation of name-list information is needed for determining the actual rights holders and the royalties that are due to them.
+
+![Diagram illustrating the need for information consolidation for content distribution. It shows two columns: 'Rights information (basically closed information)' on the left and 'Catalogue information (open information)' on the right, connected by a 'Bridging via IDs' arrow. The left column lists entities like 'Name of work', 'Scenario', 'Music', 'Performance', and 'Ingredient content' with their respective IDs and associated rights information (royalty distribution, actual names, bank accounts). The right column lists the same entities with IDs and links to 'Introduction to other related works'.](11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg)
+
+The diagram illustrates the consolidation of 'Rights information (basically closed information)' and 'Catalogue information (open information)' through a shared ID system. A central arrow labeled 'Bridging via IDs' connects the two sides.
+
+**Left Side: Rights information (basically closed information)**
+
+- Name of work** (ID) → Royalty distribution rate between those holding the rights
+- Scenario** (ID) → **Scenario writer** (ID) → Actual name, bank account and royalty distribution rate...
+- Music** (ID) → **Songwriters** (ID), **Composers** (ID), **Orchestrator** (ID) → Actual name, bank account and royalty distribution rate...
+- Performance** (ID) → **Performer** (ID) → Actual name, bank account and royalty distribution rate...
+- Ingredient content** (ID) → **Photographer** (ID), **Illustrator** (ID), **Original writer** (ID) → Actual name, bank account and royalty distribution rate...
+
+**Right Side: Catalogue information (open information)**
+
+- Name of work** (ID) → Introduction to other related works
+- Scenario** (ID) → **Scenario writer** (ID) → Introduction to other related works
+- Music** (ID) → **Songwriters** (ID), **Composers** (ID), **Orchestrator** (ID) → Introduction to other related works
+- Performance** (ID) → **Performer** (ID) → Introduction to other related works
+- Ingredient content** (ID) → **Photographer** (ID), **Illustrator** (ID), **Original writer** (ID) → Introduction to other related works
+
+H.751(13)\_FIV.2
+
+Diagram illustrating the need for information consolidation for content distribution. It shows two columns: 'Rights information (basically closed information)' on the left and 'Catalogue information (open information)' on the right, connected by a 'Bridging via IDs' arrow. The left column lists entities like 'Name of work', 'Scenario', 'Music', 'Performance', and 'Ingredient content' with their respective IDs and associated rights information (royalty distribution, actual names, bank accounts). The right column lists the same entities with IDs and links to 'Introduction to other related works'.
+
+**Figure IV.2 – Need for information consolidation for content distribution**
+
+This name-list information is necessary both in the context of "closed information", information that needs to be shared (e.g., for contracts purposes) only amongst content and rights holders, and of "open information" (e.g., catalogue information for the purpose of gaining a deeper knowledge regarding the content in question) between content holders and users or users and consumers.
+
+For this reason, it is effective to carry out information bridging for both parties, using Holder Rights IDs as a means for association.
+
+#### IV.1.3 Shared ID system
+
+In order to facilitate content distribution from here on out, it is essential that IDs be commonly used through databases to identify contents, rights holders and users, and that mechanisms be improved for access from the outside. Because of this, a shared ID system is necessary. The assignment of IDs shared between the concerned organizations and commercial entities will effectively serve such a function.
+
+##### a) Content ID
+
+In this digital age, there are countless digital files that function as masters on and outside the network. [IEC 62227] specifies the structure of the container carrying the content ID on a shared ID system. The shared ID system has been defined in order to uniquely identify this content. It has a total of 16 digits. First, the types of consumed content are divided into five general attributes. These global attributes are further arranged into established genres, and the content consumption attribute is expressed using two digits. Next, the country of origin for that content is expressed using [b-WIPO ST.3] two-letter country codes.
+
+For example, film content created inside Japan is expressed by VPJP, where "VP" is the abbreviation for "Visual Program". Similarly, photographic content created inside Japan is expressed by "IPJP", where "IP" is the abbreviation for "Image Program".
+
+##### b) Business ID
+
+##### 1) Rights holder ID
+
+Clause 5.5.5 of [IEC 62227] specifies the structure of the container carrying the rights holder ID on shared ID system. This ID commonly identifies the creators, individual rights holders, rights holder companies and rights organizations associated with the content identified using the above content ID.
+
+##### 2) User ID
+
+Clause 5.5.6 of [IEC 62227] specifies the structure of the container carrying the user ID on shared ID system. This ID commonly identifies the distributor, broadcaster, end consumer, device owned by the consumer and service group used by the consumer, using the content identified using the above content ID.
+
+### IV.2 Code language technology that carries the shared elements of the specific content consumer services
+
+#### IV.2.1 General
+
+Carries and expresses the shared elements of specific differentiated content consumption services that cannot be fully expressed using the rights encompassed by copyright law. IEC 62227 specifies the permission classification component and the permission limitation component for specific content consumer services.
+
+#### IV.2.2 Classification
+
+The classification is comprised of seven items defined from a particular legal perspective. There are four core items of the content in question that shall be written in all of the license agreements:
+
+- a) usage purpose;
+- b) whether or not the content consumption is charged or free and whether or not there is a sponsor;
+- c) specific usage consumption format;
+- d) territory of the usage consumption.
+
+In addition, within these four elements there are items that encode:
+
+- whether or not these four elements are open to the public; and
+- if these four elements correspond to requests and claims for business-to-business rights processing.
+
+#### IV.2.3 Limit components
+
+It is recommended that the four core elements discussed above be encoded. In contrast, limit components are only encoded if that encoding is required. However, these are components that express information about SCP or information about the latest services that are backed by new technology that may appear in the future. There are seven items that shall be used to limit specific content consumption:
+
+##### a) Personal Limit Component:
+
+- Compilation permission (free, by product, by album, compilation within the same artist, compilation within the same company);
+
+NOTE – When using group content distribution services, it is possible to bundle and group content in ways that go beyond content genres.
+
+##### b) Transmission and Distribution Machine Setup Control Component
+
+- CM Control (free, consent to skip CM, refuse to skip CM, time-synchronized forced viewing, before and after viewing, time custom viewing, blanket);
+
+- c) Quality Limit Component
+  - Recording Media Limit Component (cf. clause 5.10.4.4 of [IEC 62227], storage\_media\_type field);
+- d) Compression Format Standard (cf. clause 5.9.3.6 of [IEC 62227], transcode type);
+- e) Bit Rate Limit Component (cf. clause 5.9.3.7 of [IEC 62227], maximum transcode rate);
+- f) Lifetime (Life Control) Limit Component (free, count limit, time period limit, expiration limit);
+- g) Security Limit Component (watermark, SCP, rights report).
+
+### IV.3 Common semantics for RII
+
+RII represents a bridge metadata which unites open information and closed information by IDs and conditions.
+
+Bridge metadata are the common semantics for RII, which are organized into three groups:
+
+- "Identification" which is made to identify content holder, content user and content itself;
+- "Classification" which is made to relate permission classifications; and
+- "Limit components" which is made to relate permission conditions on agreements.
+
+These common semantics for RII are illustrated in Figure IV.3.
+
+![Diagram illustrating the common semantics for RII. At the top, 'Rights related metadata' points to 'Open metadata', 'Bridge metadata', and 'Closed metadata'. 'Bridge metadata' is connected to 'Open metadata' and 'Closed metadata' by dashed lines. Below 'Bridge metadata', three arrows point to 'Identification', 'Classification', and 'Limit components', which are grouped together in a box labeled 'Common semantics for RII'.](a05e675f8651ae7ccea1d0d68691d1a9_img.jpg)
+
+```
+
+graph TD
+    RRM([Rights related metadata]) --> OM([Open metadata])
+    RRM --> BM([Bridge metadata])
+    RRM --> CM([Closed metadata])
+    OM -.-> BM
+    CM -.-> BM
+    BM --> ID([Identification])
+    BM --> CL([Classification])
+    BM --> LC([Limit components])
+    subgraph CSRII [Common semantics for RII]
+        ID
+        CL
+        LC
+    end
+  
+```
+
+Diagram illustrating the common semantics for RII. At the top, 'Rights related metadata' points to 'Open metadata', 'Bridge metadata', and 'Closed metadata'. 'Bridge metadata' is connected to 'Open metadata' and 'Closed metadata' by dashed lines. Below 'Bridge metadata', three arrows point to 'Identification', 'Classification', and 'Limit components', which are grouped together in a box labeled 'Common semantics for RII'.
+
+H.751(13)\_FIV.3
+
+**Figure IV.3 – Common semantics for RII**
+
+### IV.4 Core elements and common semantics for RII
+
+Each component for RII is divided into core elements that specify the details of bridge information. Figure IV.4 shows core elements and common semantics for RII.
+
+![A hierarchical diagram showing the core elements and common semantics for RII. It is divided into four main columns: Identification, Classification, Limit components, and Usage form. Identification includes Content, Issuer, and Recipient identifiers. Classification includes Disclosure, Purpose, Application, Sponsor, Territory, and Usage classes. Limit components include Normal usage, Extended usage, Data output, and Data management terms. Usage form includes Device restrictions, Playback control, Recording limits, Quality, Lifetime, Permission, Simultaneous output, and Parental locks, which further lead to Play, Print, and Execute actions.](08dce7ad4c512fdf0c0cde60415fade6_img.jpg)
+
+```
+
+graph LR
+    Identification[Identification] --> C[Content identifier]
+    Identification --> I[Issuer identifier]
+    Identification --> R[Recipient identifier]
+
+    Classification[Classification] --> DC[Disclosure class]
+    Classification --> PC[Purpose class]
+    Classification --> AC[Application class]
+    Classification --> SC[Sponsor class]
+    Classification --> TC[Territory class]
+    Classification --> UC[Usage class]
+
+    LimitComponents[Limit components] --> NT[Normal usage terms]
+    LimitComponents --> ET[Extended usage terms]
+    LimitComponents --> DOT[Data output terms]
+    LimitComponents --> DM[Data management terms]
+
+    UsageForm[Usage form] --> D[Device and person count restrictions]
+    UsageForm --> P[Playback (CM) control]
+    UsageForm --> RL[Recording media limits]
+    UsageForm --> Q[Quality limits]
+    UsageForm --> L[Lifetime limits]
+    UsageForm --> PS[Permission management system limits]
+    UsageForm --> SOL[Simultaneous output limits]
+    UsageForm --> PL[Parental locks]
+
+    D --> Play[Play]
+    D --> Print[Print]
+    D --> Execute[Execute]
+  
+```
+
+H.751(13)\_FIV.4
+
+A hierarchical diagram showing the core elements and common semantics for RII. It is divided into four main columns: Identification, Classification, Limit components, and Usage form. Identification includes Content, Issuer, and Recipient identifiers. Classification includes Disclosure, Purpose, Application, Sponsor, Territory, and Usage classes. Limit components include Normal usage, Extended usage, Data output, and Data management terms. Usage form includes Device restrictions, Playback control, Recording limits, Quality, Lifetime, Permission, Simultaneous output, and Parental locks, which further lead to Play, Print, and Execute actions.
+
+**Figure IV.4 – Core elements and common semantics for RII**
+
+# Appendix V
+
+## Rights information metadata elements corresponding to existing SCP systems
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### V.1 SCP1
+
+| Elements of content protection                                                                                                        | Marlin BB                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Distribution format                                                                                                                   | Content independent<br>Support following container for transporting content data<br>•MP4 ISO/IEC 14496-14:2003<br><br>Other                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| Content usage permission<br><br>1)License requirement→confirmation of contract→ content distribution<br><br>2)Distribution of license | When DRM server receives a license acquisition request from a terminal, it confirms to a customer management system and a contract management system to be able to distribute the requested license. If possible, it distributes the license embedding rendering obligation and output control information (COPY/MOVE/EXPORT) corresponds to the contract.<br><br>DRM server distributes license bound to the target object which is selected from devices, users, subscriptions and domains in accordance with the order of content distributor.<br><br>Any license being bound to a device is available to any user who has the right to use the device.<br><br>Any license being bound to a user is available to the user using any device he has the right to use.<br><br>Any license being bound to a subscription is available to any user who has the subscription using any device he has the right to use.<br><br>Any license being bound to a domain is available to any user using any device belonging to the domain when he has the right to use the device or available to any user belonging to the domain using any device he has the right to use.<br><br>Users that have usage rights of devices are registered in the server DRM system per each device. |
+| Management of permission issuer, receiver and issue date                                                                              | Running dependent<br>Possible to manage through the license distribution log on the center<br><br>Manage users and devices<br>Manage users that have the right to use the specific device and devices available to the specific user<br>Manage available subscription to use a license, users having the subscription and devices that the users have the rights to use.<br>Manage deletion of the rights for users to use a device dynamically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| License storage on a nonvolatile area in a terminal                                                                                   | Available                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| License move/copy                                                                                                                     | Available                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| Encrypted content storage on a nonvolatile area in a terminal                                                                         | Available                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                                                |                                               |                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|------------------------------------------------|-----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Content playback control                       | Playback period                               | It controls playback and output by a code module running on a VM in a DRM client. Code modules are made on a DRM server and are distributed to DRM clients. Even if conditions of playback and output are being changed, client side is independent from a module or a hardware update. It is sufficient to execute a code module on a VM which being transported from DRM server. It is possible to control playback and output flexibly. |
+|                                                | Digital copy control information              |                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|                                                | Serial interface output control               |                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|                                                | analog output copy control                    |                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|                                                | video quality control information             |                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|                                                | decoded content data retention mode           |                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|                                                | decoded content data retention state          |                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|                                                | High speed digital I/F protection information |                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|                                                | CopyRestrictionMode                           |                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|                                                | User-defined information                      |                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| Control information for exporting to other DRM |                                               |                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| Content data concealment                       |                                               | AES + SCTE 52                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| Authentication of DRM systems                  |                                               | Authentication of client DRM and server DRM are implemented by using public certificates which being issued by a certificate authority authorized by MTMO.<br>RSA-D SA (1024bit/2048bit key) with SHA256<br><br>Revocation lists of client DRM and server DRM are available..                                                                                                                                                              |
+| Communication protection between DRMs          |                                               | Concealment of communication data<br>RSA 1024bit,2048bit<br>RSA 1.5   RSA-OAEP<br>AES 128bit<br><br>Check a tamper of communication data<br>RSA - SHA 1   RSA - SHA 256<br><br>Secret data concealment between DRM system nodes<br><br>RSA 1024bit,2048bit<br>RSA 1.5   RSA-OAEP<br>AES 128bit<br><br>Check a falsification of secret data between DRM system nodes.<br>HMAC - SHA1<br>RSA - SHA1   RSA - SHA256                           |
+
+### V.2 SCP System 2, with Download license, EXPORT for Copy with Direct Key Delivery
+
+|                                                                                                                                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Elements of content protection                                                                                                  | Marlin IPTV-ES                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|                                                                                                                                 | Download license                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|                                                                                                                                 | EXPORT for Copy with Direct Key Delivery                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| Distribution format                                                                                                             | Download                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| Content usage permission<br>1)License requirement->confirmation of contract-> content distribution<br>2)Distribution of license | When a DRM server receives a license acquisition request from a terminal, it confirms to a customer management system and contract management system whether the terminal has a rights to get the requested license.<br>If possible, it distributes the license embedding playback control information corresponds to the contract.                                                                                                                                                                                                                                                                                                         |
+| Management of permission issuer, receiver and issue date                                                                        | Running dependent<br>It is possible to manage a license distribution log in the center.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| License storage on a nonvolatile area in a terminal                                                                             | Available                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| License move/copy                                                                                                               | Only available to export to other DRMs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| Encrypted content storage on a nonvolatile area in a terminal                                                                   | Available                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| Content usage control                                                                                                           | Playback period                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|                                                                                                                                 | Digital copy control information                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|                                                                                                                                 | Serial interface output control                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|                                                                                                                                 | Analog output copy control                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|                                                                                                                                 | Video quality control information                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|                                                                                                                                 | Decoded content data retention mode                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|                                                                                                                                 | Decoded content data retention state                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|                                                                                                                                 | High speed digital I/F protection information                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|                                                                                                                                 | CopyRestrictionMode                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|                                                                                                                                 | User-defined information                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| Control information for exporting to other DRM                                                                                  | Following elements are available to be specified a playback control information per each media.<br>Export to DTCP.<br>Export to CPRM for DVD.<br>Export to CPRM for SD Video.<br>Export to CPRM for SD Audio.<br>Export to MG-R (SVR) for Memory Stick PRO.<br>Export to MG-R (SAR) for Memory Stick and Memory Stick PRO.<br>Export to VCPS.<br>Export to MG-R (SVR) for EMPIR.<br>Export to MG-R (SAR) for ATRAC Audio Device.<br>Export to SAFIA for iVDR TV Recording<br>Export to SAFIA for iVDR Audio Recording<br>Export to AACS Blu-ray Disc Recordable for BD-R/RE.<br>Export to AACS Blu-ray Disc Recordable for Red Laser Media. |
+| Content data concealment                                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| Authentication of DRM systems                                                                                                   | Authentication of client DRM and server DRM makes by using a public key certificate which is issued by authentication center which is authorized by MTMO.<br><br>EC-DSA (224bit key) with SHA256<br>Run revocation lists. Client DRM can be revoked per each device. Server DRM can be revoked per license distribution server.                                                                                                                                                                                                                                                                                                             |
+| Communication protection between DRMs                                                                                           | EC-DH (224 bti key) + EC-DSA (224 bit key ) + AES (128 bit key) + SHA 256                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+### V.3 SCP System 3, with Download license, EXTRACT with Direct Key Delivery, Download
+
+|                                                                                                                                 |                                                                                                                                                                                                                                                                                                                                    |                                                                                                                                                                                          |
+|---------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Elements of content protection                                                                                                  | Marlin IPTV-ES                                                                                                                                                                                                                                                                                                                     |                                                                                                                                                                                          |
+|                                                                                                                                 | Download license                                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                          |
+|                                                                                                                                 | EXTRACT with Direct Key Delivery                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                          |
+| Distribution format                                                                                                             | Download                                                                                                                                                                                                                                                                                                                           |                                                                                                                                                                                          |
+| Content usage permission<br>1)License requirement->confirmation of contract-> content distribution<br>2)Distribution of license | When DRM server receives a license acquisition request from a terminal, it confirms to a customer management system and a contract management system to be able to distribute the requested license.<br>If possible, it distributes licenses embedding playback control information corresponds to the contract.                   |                                                                                                                                                                                          |
+| Management of permission issuer, receiver and issue date                                                                        | Running dependent<br>It is possible to manage as a license distribution log on the center                                                                                                                                                                                                                                          |                                                                                                                                                                                          |
+| License storage on a nonvolatile area in a terminal                                                                             | Available                                                                                                                                                                                                                                                                                                                          |                                                                                                                                                                                          |
+| License move/copy                                                                                                               | Not available                                                                                                                                                                                                                                                                                                                      |                                                                                                                                                                                          |
+| Encrypted content storage on a nonvolatile area in a terminal                                                                   | Available                                                                                                                                                                                                                                                                                                                          |                                                                                                                                                                                          |
+| Content usage control                                                                                                           | Playback period                                                                                                                                                                                                                                                                                                                    | NotBefore, NotAfter                                                                                                                                                                      |
+|                                                                                                                                 | Digital copy control information                                                                                                                                                                                                                                                                                                   | DigitalRecordingControlData<br>11 : Copy never<br>* Follow APS Control Data for analog output                                                                                            |
+|                                                                                                                                 | Serial interface output control                                                                                                                                                                                                                                                                                                    | CopyControlType<br>01 : Serial interface encoding output                                                                                                                                 |
+|                                                                                                                                 | Analog output copy control                                                                                                                                                                                                                                                                                                         | APS Control Data<br>00:Copy free<br>01:Pseudo-synchronizing pulse<br>10:Pseudo-synchronizing pulse + two line inverted burst<br>11:Pseudo-synchronizing pulse + four line inverted burst |
+|                                                                                                                                 | Video quality control information                                                                                                                                                                                                                                                                                                  | ImageConstraintToken<br>1 : unbound                                                                                                                                                      |
+|                                                                                                                                 | Decoded content data retention mode                                                                                                                                                                                                                                                                                                | RetentionMode<br>0 : Permit retention                                                                                                                                                    |
+|                                                                                                                                 | Decoded content data retention state                                                                                                                                                                                                                                                                                               | RetentionState<br>111 : 90 minute                                                                                                                                                        |
+|                                                                                                                                 | High speed digital I/F protection information                                                                                                                                                                                                                                                                                      | EncryptionMode<br>1 : non-protection                                                                                                                                                     |
+|                                                                                                                                 | CopyRestrictionMode                                                                                                                                                                                                                                                                                                                |                                                                                                                                                                                          |
+|                                                                                                                                 | User-defined information                                                                                                                                                                                                                                                                                                           | Not defined                                                                                                                                                                              |
+| Control information for exporting to other DRM                                                                                  |                                                                                                                                                                                                                                                                                                                                    |                                                                                                                                                                                          |
+| Content data concealment                                                                                                        | AES ( 128bit key ) + SCTE 52                                                                                                                                                                                                                                                                                                       |                                                                                                                                                                                          |
+| Authentication of DRM systems                                                                                                   | Authentication of client DRM and server DRM makes by using a public key certificate which is issued by authentication center that authorized in MTMO.<br><br>EC-DSA (224bit key) with SHA256<br>Run revocation lists. Client DRM can be revoked by per each devices. Server DRM can be revoked by per license distribution server. |                                                                                                                                                                                          |
+| Communication protection between DRMs                                                                                           | EC-DH (224 bti key) + EC-DSA (224 bit key) + AES (128 bit key) + SHA 256                                                                                                                                                                                                                                                           |                                                                                                                                                                                          |
+
+### V.4 SCP System 4, with Download license, EXTRACT with Direct Key Delivery, VOD streaming
+
+|                                                                                                                                 |                                                                                                                                                                                                                                                                                                                                            |                                                                                                                                                                                          |
+|---------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Elements of content protection                                                                                                  | Marlin IPTV-ES                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                          |
+|                                                                                                                                 | Download license                                                                                                                                                                                                                                                                                                                           |                                                                                                                                                                                          |
+|                                                                                                                                 | EXTRACT with Direct Key Delivery                                                                                                                                                                                                                                                                                                           |                                                                                                                                                                                          |
+| Distribution format                                                                                                             | VOD streaming                                                                                                                                                                                                                                                                                                                              |                                                                                                                                                                                          |
+| Content usage permission<br>1)License requirement->confirmation of contract-> content distribution<br>2)Distribution of license | When DRM server receives a license acquisition request from a terminal, it confirms to a customer management system and a contract management system whether the terminal has the rights to get the requesting license.<br><br>If possible, it distributes the license embedding playback control information corresponds to the contract. |                                                                                                                                                                                          |
+| Management of permission issuer, receiver and issue date                                                                        | Running dependent<br>It is possible to manage as a license distribution log in the center.                                                                                                                                                                                                                                                 |                                                                                                                                                                                          |
+| License storage on a nonvolatile area in a terminal                                                                             | Available                                                                                                                                                                                                                                                                                                                                  |                                                                                                                                                                                          |
+| License move/copy                                                                                                               | Not available                                                                                                                                                                                                                                                                                                                              |                                                                                                                                                                                          |
+| Encrypted content storage on a nonvolatile area in a terminal                                                                   | Not available except for keeping a quality of playback                                                                                                                                                                                                                                                                                     |                                                                                                                                                                                          |
+| Content usage control                                                                                                           | Playback period                                                                                                                                                                                                                                                                                                                            | NotBefore, NotAfter                                                                                                                                                                      |
+|                                                                                                                                 | Digital copy control information                                                                                                                                                                                                                                                                                                           | DigitalRecordingControlData<br>11 : Copy never<br>* Follow APS Control Detail as analog output                                                                                           |
+|                                                                                                                                 | Serial interface output control                                                                                                                                                                                                                                                                                                            | CopyControlType<br>01 : Serial interface encoding output                                                                                                                                 |
+|                                                                                                                                 | Analog output copy control                                                                                                                                                                                                                                                                                                                 | APS Control Data<br>00:Copy free<br>01:Pseudo-synchronizing pulse<br>10:Pseudo-synchronizing pulse + two line inverted burst<br>11:Pseudo-synchronizing pulse + four line inverted burst |
+|                                                                                                                                 | Video quality control information                                                                                                                                                                                                                                                                                                          | ImageConstraintToken<br>1 : unbound                                                                                                                                                      |
+|                                                                                                                                 | Decoded content data retention mode                                                                                                                                                                                                                                                                                                        | RetentionMode<br>0 : Retention                                                                                                                                                           |
+|                                                                                                                                 | Decoded content data retention state                                                                                                                                                                                                                                                                                                       | RetentionState<br>111 : 90 minute                                                                                                                                                        |
+|                                                                                                                                 | High speed digital I/F protection information                                                                                                                                                                                                                                                                                              | EncryptionMode<br>1 : non-protection                                                                                                                                                     |
+|                                                                                                                                 | CopyRestrictionMode                                                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                          |
+|                                                                                                                                 | User-defined information                                                                                                                                                                                                                                                                                                                   | undefined                                                                                                                                                                                |
+| Control information for exporting to other DRM                                                                                  |                                                                                                                                                                                                                                                                                                                                            |                                                                                                                                                                                          |
+| Content data concealment                                                                                                        | AES ( 128bit key ) + SCTE 52                                                                                                                                                                                                                                                                                                               |                                                                                                                                                                                          |
+| Authentication of DRM systems                                                                                                   | Authentication of client DRM and server DRM makes by using a public key certification which is issued by authentication center which authorized by MTMO.<br>EC-DSA (224bit key) with SHA256<br><br>Run revocation lists. Client DRM can be revoked per each device. Server DRM can be revoked per license distribution server.             |                                                                                                                                                                                          |
+| Communication protection between DRMs                                                                                           | EC-DH (224 bti key) + EC-DSA (224 bit key) + AES (128 bit key) + SHA 256                                                                                                                                                                                                                                                                   |                                                                                                                                                                                          |
+
+### V.5 SCP System 3, with Download license, EXTRACT with Direct Key Delivery, Download
+
+|                                                                                                                                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                                                                                          |
+|---------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|
+| Elements of content protection                                                                                                  | Marlin IPTV-ES                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                                                                                          |
+|                                                                                                                                 | Broadcast license                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                                                                                          |
+|                                                                                                                                 | EXTRACT with Indirect Key Delivery license                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                                                                                          |
+| Distribution format                                                                                                             | Terrestrial re-distribution/BS re-distribution                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                                                                                          |
+| Content usage permission<br>1)License requirement->confirmation of contract-> content distribution<br>2)Distribution of license | <p>Permission to playback a content confirms, when a terminal requests a license, to a customer management system and a contract management system whether the terminal has the rights to get a requested license (work key).</p> <p>If possible, DRM server distributes a license embedding information about available channels and available period of reception.</p> <p>Broadcasting data received is permitted to be copied/moved to other media/devices as following to digital copy control information and copy control information set in multiplexed ECM. (Copy/Move are only valid for one generation. It is not possible second generation copy/move)</p> <p>There are no playback period limits for a content which is stored in received devices and for a content which is moved/copied to other media/devices.</p> <p>A playback control information of broadcasting data succeed ones of terrestrial broadcast and BS broadcast playback control information.</p> |                                                                                                                          |
+| Management of permission issuer, receiver and issue date                                                                        | <p>Running dependent</p> <p>It is possible to manage as a license distribution log in the center.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                                                                                          |
+| License storage on a nonvolatile area in a terminal                                                                             | Available                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                                                                                          |
+| License move/copy                                                                                                               | Not available                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                                                                                          |
+| Encrypted content storage on a nonvolatile area in a terminal                                                                   | It is not permitted except for keeping a playback quality.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                                                                                          |
+| Content usage control                                                                                                           | Playback period                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | <p>NotBefore, NotAfter</p> <p>* There is offset period which is possible to be updated license period from NotAfter.</p> |
+|                                                                                                                                 | Digital copy control information                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | It succeeds digital copy control descriptor of SI.                                                                       |
+|                                                                                                                                 | Serial interface output control                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                                                                                          |
+|                                                                                                                                 | Analog output copy control                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                                                                                          |
+|                                                                                                                                 | Video quality control information                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | It succeeds content usage descriptor of SI.                                                                              |
+|                                                                                                                                 | Decoded content data retention mode                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                                                                                          |
+|                                                                                                                                 | Decoded content data retention state                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                                                                                          |
+|                                                                                                                                 | High speed digital I/F protection information                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                                                                                          |
+|                                                                                                                                 | CopyRestrictionMode                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                                                                                          |
+|                                                                                                                                 | User-defined information                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | undefined                                                                                                                |
+| Control information for exporting to other DRM                                                                                  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                                                                                          |
+| Content data concealment                                                                                                        | AES ( 128bit key ) + SCOTE 52                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                                                                                          |
+| Authentication of DRM systems                                                                                                   | <p>Authentication of client DRM and server DRM makes by using a public key certification which is issued in authentication center which is authorized by MTMO.</p> <p>EC-DSA (224bit key) with SHA256</p> <p>Run revocation lists. Client DRM can be revoked per each device. Server DRM can be revoked per license distribution server.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                                                                                          |
+| Communication protection between DRMs                                                                                           | EC-DH (224 bit key) + EC-DSA (224 bit key) + AES (128 bit key) + SHA 256                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                                                                                          |
+
+### V.6 SCP System 4, with Download license, EXTRACT with Direct Key Delivery, VOD streaming
+
+|                                                                                                                                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                                              |
+|---------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Elements of content protection                                                                                                  | Marlin IPTV-ES                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                              |
+|                                                                                                                                 | Broadcasting license.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                                                                                                                                                                              |
+|                                                                                                                                 | EXTRACT with Indirect Key Delivery license                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                              |
+| Distribution format                                                                                                             | IP multicast                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                                                                                                                                                                              |
+| Content usage permission<br>1)License requirement->confirmation of contract-> content distribution<br>2)Distribution of license | <p>Permission to playback a content confirms, when a terminal requests a license, to a customer management system and a contract management system whether the terminal has the rights to get a requested license (work key).</p> <p>If possible, DRM server distributes a license embedding information about available channels and available period of reception.</p> <p>Broadcasting data received is permitted to be copied/moved to other media/devices as following to digital copy control information and copy control information set in multiplexed ECM. (Copy/Move are only valid for one generation. It is not possible second generation copy/move)</p> <p>There are no playback period limits for a content which is stored in received devices and for a content which is moved/copied to other media/devices.</p> <p>Playback control information of broadcasting data is set/modified per channel in the center.</p> |                                                                                                                                                                                                              |
+| Management of permission issuer, receiver and issue date                                                                        | <p>Running dependent</p> <p>It is possible to manage as a license distribution log in the center.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                                                                                                                                                                              |
+| License storage on a nonvolatile area in a terminal                                                                             | Available                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                                                                                                                                                                              |
+| License move/copy                                                                                                               | Not available                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                                                                                                                                                                              |
+| Encrypted content storage on a nonvolatile area in a terminal                                                                   | It is not permitted except for keeping a playback quality.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                              |
+| Content usage control                                                                                                           | Playback period                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | <p>NotBefore, NotAfter</p> <p>* There is offset period which is possible to be updated license period from NotAfter.</p>                                                                                     |
+|                                                                                                                                 | Digital copy control information                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | <p>DigitalRecordingControlData</p> <p>00 : Constrained condition</p> <p>10 : Copy one generation</p> <p>11 : Copy never</p> <p>* Follow APS Control Data as analog output</p>                                |
+|                                                                                                                                 | Serial interface output control                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | <p>CopyControlType</p> <p>01 : Serial interface encoding output</p>                                                                                                                                          |
+|                                                                                                                                 | Analog output copy control                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | <p>APS Control Data</p> <p>00:Copy free</p> <p>01:Pseudo-synchronized pulse</p> <p>10:Pseudo-synchronized pulse + two line inverted burst</p> <p>11:Pseudo-synchronized pulse + four line inverted burst</p> |
+|                                                                                                                                 | Video quality control information                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | <p>ImageConstraintToken</p> <p>1 : unbound</p>                                                                                                                                                               |
+|                                                                                                                                 | Decoded content data retention mode                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | <p>RetentionMode</p> <p>0 : Retention</p>                                                                                                                                                                    |
+|                                                                                                                                 | Decoded content data retention state                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | <p>RetentionState</p> <p>111 : 90 minute</p>                                                                                                                                                                 |
+|                                                                                                                                 | High speed digital I/F protection information                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | <p>EncryptionMode</p> <p>0 : Protect 1 : Non-protect</p>                                                                                                                                                     |
+|                                                                                                                                 | CopyRestrictionMode                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                                                                                                                                                                              |
+|                                                                                                                                 | User-defined information                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | undefined                                                                                                                                                                                                    |
+| Control information for exporting to other DRM                                                                                  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                                              |
+| Content data concealment                                                                                                        | AES ( 128bit key ) + SCTE 52                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                                                                                                                                                                              |
+| Authentication of DRM systems                                                                                                   | <p>Authentication of client DRM and server DRM makes by using a public key certification which is issued in authentication center which is authorized by MTMO.</p> <p>EC-DSA (224bit key) with SHA256</p> <p>Run revocation lists. Client DRM can be revoked per each device. Server DRM can be revoked per license distribution server.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                                                                                                                                                                              |
+| Communication protection between DRMs                                                                                           | EC-DH (224 bti key) + EC-DSA (224 bit key ) + AES (128 bit key) + SHA 256                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                                                                                                                                                                              |
+
+### V.7 SCP System 5, with, Broadcast license, EXTRACT with IndirectKey Delivery license, Terrestrial re-distribution/BS(Broadcasting satellite) re-distribution
+
+|                                                                                                                                 |                                                                                                                                                                                                                                                                                                                                |                                                                                                                                                                                       |
+|---------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Elements of content protection                                                                                                  | Marlin IPTV-ES                                                                                                                                                                                                                                                                                                                 |                                                                                                                                                                                       |
+|                                                                                                                                 | VOD license                                                                                                                                                                                                                                                                                                                    |                                                                                                                                                                                       |
+|                                                                                                                                 | EXTRACT with Simple Key Delivery license                                                                                                                                                                                                                                                                                       |                                                                                                                                                                                       |
+| Distribution format                                                                                                             | VOD streaming                                                                                                                                                                                                                                                                                                                  |                                                                                                                                                                                       |
+| Content usage permission<br>1)Licence requirement->confirmation of contract-> content distribution<br>2)Distribution of licence | When a server DRM receives a licence acquisition request from a terminal, it confirms to a customer management system and contract management system whether the terminal has a rights to get a requested licence. If possible, it distributes the licence embedding playback control information corresponds to the contract. |                                                                                                                                                                                       |
+| Management of permission issuer, receiver and issue date                                                                        | Running dependent<br>It is possible to manage as a licence distribution log in the center                                                                                                                                                                                                                                      |                                                                                                                                                                                       |
+| License storage on a nonvolatile area in a terminal                                                                             | Not available                                                                                                                                                                                                                                                                                                                  |                                                                                                                                                                                       |
+| License move/copy                                                                                                               | Not available                                                                                                                                                                                                                                                                                                                  |                                                                                                                                                                                       |
+| Encrypted content storage on a nonvolatile area in a terminal                                                                   | It is not available except for keeping playback quality.                                                                                                                                                                                                                                                                       |                                                                                                                                                                                       |
+| Content usage control                                                                                                           | Playback period                                                                                                                                                                                                                                                                                                                |                                                                                                                                                                                       |
+|                                                                                                                                 | Digital copy control information                                                                                                                                                                                                                                                                                               | DigitalRecordingControlData<br>11:Copy never<br>* Follow APS Control Detail as analog output                                                                                          |
+|                                                                                                                                 | Serial interface output control                                                                                                                                                                                                                                                                                                | CopyControlType<br>01 : Serial interface encoding output                                                                                                                              |
+|                                                                                                                                 | analog output copy control                                                                                                                                                                                                                                                                                                     | APS Control Data<br>00:Copy free<br>01:Pseudo-synchronized pulse<br>10:Pseudo-synchronized pulse + two line inverted burst<br>11:Pseudo-synchronized pulse + four line inverted burst |
+|                                                                                                                                 | video quality control information                                                                                                                                                                                                                                                                                              | ImageConstraintToken<br>1 :unbound                                                                                                                                                    |
+|                                                                                                                                 | decoded content data retention mode                                                                                                                                                                                                                                                                                            | RetentionMode<br>0 : Retention                                                                                                                                                        |
+|                                                                                                                                 | decoded content data retention state                                                                                                                                                                                                                                                                                           | RetentionState<br>111 : 90 minute                                                                                                                                                     |
+|                                                                                                                                 | High speed digital I/F protection information                                                                                                                                                                                                                                                                                  | EncryptionMode<br>1 : Non protection                                                                                                                                                  |
+|                                                                                                                                 | CopyRestrictionMode                                                                                                                                                                                                                                                                                                            |                                                                                                                                                                                       |
+|                                                                                                                                 | User-defined information                                                                                                                                                                                                                                                                                                       | undefined                                                                                                                                                                             |
+| Control information for exporting to other DRM                                                                                  |                                                                                                                                                                                                                                                                                                                                |                                                                                                                                                                                       |
+| Content data concealment                                                                                                        | AES ( 128bit key ) + SCTE 52                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                       |
+| Authentication of DRM systems                                                                                                   | Authentication of client DRM and server DRM makes by using a public key certification which is issued in authentication center which is authorized by MTMO.<br>EC-DSA (224bit key) with SHA256<br>Run revocation lists. Client DRM can be revoked per each device. Server DRM can be revoked per license distribution server.  |                                                                                                                                                                                       |
+| Communication protection between DRMs                                                                                           | EC-DH (224 bit key) + EC-DSA (224 bit key) + AES (128 bit key) + SHA 256                                                                                                                                                                                                                                                       |                                                                                                                                                                                       |
+
+### V.8 SCP System 6, with Broadcast license, EXTRACT with DirectKey Delivery license, IP multicast
+
+|                                                                                                                                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Elements of content protection                                                                                                  | WM-DRM                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| Distribution format                                                                                                             | Download                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| Content usage permission<br>1)License requirement->confirmation of contract-> content distribution<br>2)Distribution of license | A protected content encrypt by using a key which is encrypted in license and relate to a specific terminal.<br>Both rights and rules which restrict available period and playback count etc are included in the license rather than the content.<br>By separating a license from content, server DRM can issue different licenses for the same content.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| Management of permission issuer, receiver and issue date                                                                        | It is possible in license server                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| License storage on a nonvolatile area in a terminal                                                                             | Available                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| License move/copy                                                                                                               | Not available to other PC and network devices.<br>Available to portable devices/media(In this case, AllowCopy is required.)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| Encrypted content storage on a nonvolatile area in a terminal                                                                   | Available                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| Content usage control                                                                                                           | <p>Playback period</p> <p>Content provider is possible to combine a following constraint alternatively.<br/>         · As following calendar date, a license can be valid or not.<br/>         · A license can be revoked after specific time period from first use.<br/>         · A license can be revoked after specific time period from first install to PCs or devices. As following a playback count condition, a license can be revoked.</p> <p>Digital copy control information</p> <p>&lt;Audio output protection&gt;<br/>         1. Non protection<br/>         2. Obfuscation(Protect by Secure Audio Path. Permit digital output)<br/>         Obfuscation</p> <p>Serial interface output control</p> <p>3. Encryption-Low(Protect by Secure Audio Path. Deny digital output)<br/>         4. Encryption-Middle<br/>         5. Encryption-High</p> <p>Analog output copy control</p> <p>&lt;Video output protection&gt;<br/>         1. Non protection<br/>         2. Obfuscation(For analog video: Copy Generation Management System)<br/>         3. Encryption-Low(For non-compression digital video: High-Bandwidth Digital Content Protection using secure path, such as COPPV1, HDCP up stream protocol etc)<br/>         4. Encryption-Middle<br/>         5. Encryption-High(Compressed digital video: Microsoft Link Protection which has a approximate restriction)</p> <p>Video quality control information</p> <p>Decoded content data retention mode</p> <p>Not available</p> <p>Decoded content data retention state</p> <p>-</p> <p>High speed digital I/F protection information</p> <p>-</p> <p>CopyRestrictionMode</p> <p>-</p> <p>User-defined information</p> <p>-</p> |
+
+|                                                |                                                                                                                                                                                                                                            |
+|------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Control information for exporting to other DRM | Not available                                                                                                                                                                                                                              |
+| Content data concealment                       | As a requirement of network devices, following encryption technology is considering<br>• AES(128 bit) which use both of ECB and CTR mode                                                                                                   |
+| Authentication of DRM systems                  | By linking each terminal to server indently, system security becomes high.<br>If there are terminals who are infringed security, they can be identified in licensing process and revoked.<br>It is possible to revoke by a license server. |
+| Communication protection between DRMs          | As a network device requirement, there are following encryption technologies.<br>• 2048 bit RSA encryption that can store and protect a private key<br>• SHA-256 that has 2048 bit RSA encryption and AES OMAC1                            |
+
+### V.9 SCP System 9, for mobile IPTV terminal
+
+|                                                                                                                                 |                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Elements of content protection                                                                                                  | OMA DRM v2.0                                                                                                                                                                                                                                                                                                                                                          |
+|                                                                                                                                 | CMLA(Content Management License Administrator)                                                                                                                                                                                                                                                                                                                        |
+| Distribution format                                                                                                             | <ul style="list-style-type: none"> <li>Download</li> <li>Streaming</li> </ul>                                                                                                                                                                                                                                                                                         |
+| Content usage permission<br>1)License requirement->confirmation of contract-> content distribution<br>2)Distribution of license | <p>When Server DRM receives a license acquisition requirement from a terminal to a rights holder, it confirms to a customer management system and a contract management system whether the terminal has rights to get the requested license.</p> <p>If possible, it distributes a license embedding a playback control information corresponds to the contract.</p>   |
+| Management of permission issuer, receiver and issue date                                                                        | Content issuer, Rights issuer and DRM agent is defined and it is possible to be managed by rights holder.                                                                                                                                                                                                                                                             |
+| License storage on a nonvolatile area in a terminal                                                                             | Available                                                                                                                                                                                                                                                                                                                                                             |
+| License move/copy                                                                                                               | <p>If these are the devices in the same domain, content and rights object can be shared.</p> <p>If these are the devices which belong to no common domain, only content can be copied.</p>                                                                                                                                                                            |
+| Encrypted content storage on a nonvolatile area in a terminal                                                                   | Available                                                                                                                                                                                                                                                                                                                                                             |
+| Content usage control                                                                                                           | Playback period Describe in rights object                                                                                                                                                                                                                                                                                                                             |
+|                                                                                                                                 | Digital copy control information Out of scope in OMA DRM.<br>In CMLA technical specification, there are description to support HDCP and DTCP                                                                                                                                                                                                                          |
+|                                                                                                                                 | Serial interface output control                                                                                                                                                                                                                                                                                                                                       |
+|                                                                                                                                 | Analog output copy control                                                                                                                                                                                                                                                                                                                                            |
+|                                                                                                                                 | Video quality control information                                                                                                                                                                                                                                                                                                                                     |
+|                                                                                                                                 | Decoded content data retention mode Out of scope in OMA DRM.                                                                                                                                                                                                                                                                                                          |
+|                                                                                                                                 | Decoded content data retention state Out of scope in OMA DRM                                                                                                                                                                                                                                                                                                          |
+|                                                                                                                                 | High speed digital I/F protection information Out of scope in OMA DRM                                                                                                                                                                                                                                                                                                 |
+|                                                                                                                                 | CopyRestrictionMode -                                                                                                                                                                                                                                                                                                                                                 |
+|                                                                                                                                 | User-defined information -                                                                                                                                                                                                                                                                                                                                            |
+| Control information for exporting to other DRM                                                                                  | <p>1)EXPORT is available</p> <p>2)not defined about the way to transport from OMA DRM to other protection mechanisms</p> <p>3)Permission and restriction of following elements are available by rights object</p> <ul style="list-style-type: none"> <li>Export permission</li> <li>DRM system to export</li> <li>Copy/move selection when it is exported.</li> </ul> |
+| Content data concealment                                                                                                        | <p>EncryptionMethod Field</p> <p>0x0...No encryption</p> <p>0x1...AES(128bit) + CBC</p> <p>0x2...AES(128bit) + CTR</p>                                                                                                                                                                                                                                                |
+| Authentication of DRM systems                                                                                                   | <p>A terminal has own secret/public key and certificate.</p> <p>In a certificate, there are maker name, device type, software version, serial number and determine whether rights holder trust a terminal or not by the certificate.</p>                                                                                                                              |
+| Communication protection between DRMs                                                                                           | Rights information is protected by rights information acquisition protocol.                                                                                                                                                                                                                                                                                           |
+
+### V.10 SCP System 10, for recording media (e.g., DVD), basic
+
+|                                                                                                                                   |                                                                                                                                    |
+|-----------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|
+| Elements of content protection                                                                                                    | AACS                                                                                                                               |
+|                                                                                                                                   | Basic title                                                                                                                        |
+|                                                                                                                                   |                                                                                                                                    |
+| Distribution format                                                                                                               | Consumersoftware (Pre-recorded media)<br>Disc for broadcast (Recordable media)                                                     |
+| Content usage permission<br>1) License requirement->confirmation of contract-> content distribution<br>2) Distribution of license | It is possible to decode a content on combination between device key in the playback device and encrypted title keys in the media. |
+| Management of permission issuer, receiver and issue date                                                                          | Basic title does not connect online                                                                                                |
+| License storage on a nonvolatile area in a terminal                                                                               | Basic title does not connect online                                                                                                |
+| License move/copy                                                                                                                 | [Move]<br>It is possible to move title which records in recordable media.<br>[Copy]<br>Not available                               |
+| Encrypted content storage on a nonvolatile area in a terminal                                                                     | Basic title doesn't connect online                                                                                                 |
+| Content usage control                                                                                                             | Playback period                                                                                                                    |
+|                                                                                                                                   | Not available                                                                                                                      |
+|                                                                                                                                   | Digital copy control information                                                                                                   |
+|                                                                                                                                   | For preventing illegal copy, it is required to have a secure digital interface such as HDMI on audio/video output                  |
+|                                                                                                                                   | Serial interface output control                                                                                                    |
+|                                                                                                                                   | Analog output copy control                                                                                                         |
+|                                                                                                                                   | Video quality control information                                                                                                  |
+|                                                                                                                                   | Decoded content data retention mode                                                                                                |
+|                                                                                                                                   | Out of scope                                                                                                                       |
+|                                                                                                                                   | Decoded content data retention state                                                                                               |
+|                                                                                                                                   | Out of scope                                                                                                                       |
+|                                                                                                                                   | High speed digital I/F protection information                                                                                      |
+|                                                                                                                                   | For preventing illegal copy, it is required to secure digital interface such as HDMI on audio/video output                         |
+|                                                                                                                                   | CopyRestrictionMode                                                                                                                |
+|                                                                                                                                   | -                                                                                                                                  |
+|                                                                                                                                   | User-defined information                                                                                                           |
+|                                                                                                                                   | -                                                                                                                                  |
+| Control information for exporting to other DRM                                                                                    | Not available                                                                                                                      |
+| Content data concealment                                                                                                          | AES (256bit)                                                                                                                       |
+| Authentication of DRM systems                                                                                                     | -                                                                                                                                  |
+| Communication protection between DRM systems                                                                                      | -                                                                                                                                  |
+
+### V.11 SCP System 11, for recording media (e.g., DVD), extended
+
+|                                                                                                                                 |                                                                                                                                                                                                                                     |
+|---------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Elements of content protection                                                                                                  | AACS                                                                                                                                                                                                                                |
+|                                                                                                                                 | Extended title                                                                                                                                                                                                                      |
+|                                                                                                                                 |                                                                                                                                                                                                                                     |
+| Distribution format                                                                                                             | <ul style="list-style-type: none"> <li>• Consumer software</li> <li>• Recordable disc for broadcasting</li> <li>• AACS Network Download Content</li> <li>• AACS On-line Enabled Content</li> <li>• AACS Streamed Content</li> </ul> |
+| Content usage permission<br>1)License requirement->confirmation of contract-> content distribution<br>2)Distribution of license | After authentication online by authentication server, the content is decoded by combination of the Device Key in a playback terminal and the Encrypted Title Key in a media .                                                       |
+| Management of permission issuer, receiver and issue date                                                                        | Authentication management by authentication server is running dependent                                                                                                                                                             |
+| License storage on a nonvolatile area in a terminal                                                                             | Only titles which has Cacheable attribute are available                                                                                                                                                                             |
+| License move/copy                                                                                                               | [move]<br>Title recorded in recordable media can be moved.<br>[Copy]<br>It is managed by managed copy. It is required to authenticate online                                                                                        |
+| Encrypted content storage on a nonvolatile area in a terminal                                                                   | <AACS Network Download Content><br>Never Store. Available to record on the media such as BD<br><AACS On-line Enabled Content><br>Available to the title that has Cacheable attribute                                                |
+| Content usage control                                                                                                           | Playback period<br>Only titles that have Cacheable attribute are available<br>It is specified by period, after and before attribute.                                                                                                |
+|                                                                                                                                 | Digital copy control information                                                                                                                                                                                                    |
+|                                                                                                                                 | Serial interface output control                                                                                                                                                                                                     |
+|                                                                                                                                 | Analog output copy control                                                                                                                                                                                                          |
+|                                                                                                                                 | Video quality control information                                                                                                                                                                                                   |
+|                                                                                                                                 | Decoded content data retention mode<br>Out of scope                                                                                                                                                                                 |
+|                                                                                                                                 | Decoded content data retention state<br>Out of scope                                                                                                                                                                                |
+|                                                                                                                                 | High speed digital I/F protection information<br>Out of scope                                                                                                                                                                       |
+|                                                                                                                                 | CopyRestrictionMode<br>-                                                                                                                                                                                                            |
+|                                                                                                                                 | User-defined information<br>-                                                                                                                                                                                                       |
+| Control information for exporting to other DRM                                                                                  | Not available                                                                                                                                                                                                                       |
+| Content data concealment                                                                                                        | AES(128bit)                                                                                                                                                                                                                         |
+| Authentication of DRM systems                                                                                                   | A terminal connect authentication server which is described in Title Usage File of Title and transport content id. Authentication server authenticate it.                                                                           |
+| Communication protection between DRMs                                                                                           | TLS_RSA_WITH_AES_128_CBC_SHA                                                                                                                                                                                                        |
+
+# **Appendix VI**
+
+## **Examples of media formats**
+
+(This appendix does not form an integral part of this Recommendation.)
+
+MPEG-1, MPEG-2, ITU-T H.264, ITU-T H.265, JPEG, GIF, PNG, Linear PCM, AAC, MP3.
+
+# Bibliography
+
+- [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 (2006), *Designations for interconnections among operators' networks.*
+- [b-ITU-T X.509] Recommendation ITU-T X.509 (2005), *Information technology – Open Systems Interconnection – The Directory: Public-key and attribute certificate frameworks.*
+- [b-ITU-T X.800] Recommendation ITU-T X.800 (1991), *Security architecture for open systems interconnection for CCITT applications.*
+- [b-ITU-T X.1191] Recommendation ITU-T X.1191 (2009), *Functional requirements and architecture for IPTV security aspects.*
+- [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-IEC 62636] IEC Technical Report 62636 (2009), *Multimedia home server systems – Implementation of digital rights permission code.*
+- [b-WIPO ST.3] World Intellectual Property Organization (WIPO) Standard ST.3 (2011), *Recommended standard on two-letter codes for the representation of states, other entities and intergovernmental organizations.*
+
+
+
+# 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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.752-201511-I_PDF-E/raw.md b/marked/H/T-REC-H.752-201511-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..ba83ac43420e1f7b332299a973822f2827d6addc
--- /dev/null
+++ b/marked/H/T-REC-H.752-201511-I_PDF-E/raw.md
@@ -0,0 +1,786 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.752**
+
+(11/2015)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+IPTV multimedia services and applications for IPTV –  
+IPTV metadata
+
+# --- **Multimedia content provisioning interface for IPTV services**
+
+Recommendation ITU-T H.752
+
+## 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        |
+| <b>IPTV metadata</b>                                                                        | <b>H.750–H.759</b> |
+| 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.752
+
+# Multimedia content provisioning interface for IPTV services
+
+## Summary
+
+Recommendation ITU-T H.752 describes the metadata elements that are necessary for multimedia content provisioning, such as content description, distribution conditions and the usage log report. Compared to the high-level specification of metadata for Internet protocol television (IPTV) services defined in Recommendation ITU-T H.750, multimedia content provisioning interface for IPTV services focuses on the metadata elements to be used at the interface between content providers and IPTV service providers. This Recommendation specifies the requirement for audio and video (AV) content metadata provisioning, AV content metadata elements and data structure, procedure of exchanges for content between the content providers and IPTV service providers.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T H.752    | 2015-11-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/12649">11.1002/1000/12649</a> |
+
+## Keywords
+
+Content description, content provider, IPTV services, metadata, service provider, VoD.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                             | 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.....                                                             | 3  |
+| 7    | Requirements for AV content metadata provisioning .....                       | 3  |
+| 8    | AV content metadata elements and attributes .....                             | 4  |
+| 8.1  | AV content metadata structure .....                                           | 4  |
+| 8.2  | Data structure for specific AV content elements.....                          | 5  |
+| 8.3  | Content location.....                                                         | 8  |
+| 8.4  | Content provider identification.....                                          | 8  |
+| 8.5  | Transaction information elements and attributes .....                         | 8  |
+| 8.6  | Exchange purpose information.....                                             | 10 |
+| 8.7  | Usage log metadata.....                                                       | 10 |
+| 8.8  | Payment details elements .....                                                | 11 |
+| 9    | Data structures and messages .....                                            | 11 |
+| 9.1  | Data structure of the content declaration.....                                | 11 |
+| 9.2  | Data structure of the usage log report.....                                   | 13 |
+| 10   | Exchanges for content.....                                                    | 13 |
+| 10.1 | Declaration mode (push mode) .....                                            | 13 |
+| 10.2 | Content information request mode (pull mode) .....                            | 14 |
+|      | Annex A – Content provisioning metadata schema: Elements and attributes ..... | 15 |
+|      | Bibliography.....                                                             | 20 |
+
+
+
+# Multimedia content provisioning interface for IPTV services
+
+# 1 Scope
+
+This Recommendation identifies the metadata elements which are necessary for multimedia content provisioning. Two types of audio and video (AV) content metadata are content catalogue metadata and business metadata. Content catalogue metadata describes AV content description and the rights holder of the content. Business metadata describes basic business description and the usage log report.
+
+This Recommendation describes the messages and procedures of exchanges for content between content providers and service providers in the two communication modes (push mode and pull mode).
+
+[ITU-T H.750] already identifies essential elements and attributes concerning content. This Recommendation focuses on the content metadata to be used at the interface between content providers and Internet protocol television (IPTV) service providers.
+
+# 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.1910] Recommendation ITU-T Y.1910 (2008), *IPTV functional architecture*.
+- [ETSI TS 102 471] ETSI TS 102 471 V1.4.1 (2010), *Digital Video Broadcasting (DVB); IP Datacast over DVB-H: Electronic Service Guide (ESG)*.
+- [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*.
+- [ETSI TS 102 822-3-2] ETSI TS 102 822-3-2 V1.6.1 (2010), *Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 3: Metadata; Sub-part 2: System aspects in a uni-directional environment*.
+- [ETSI TS 102 822-3-3] ETSI TS 102 822-3-3 V1.6.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 3: Phase 2 – Extended Metadata Schema*.
+
+- [ETSI TS 102 822-5-1] ETSI TS 102 822-5-1 V1.7.1 (2012), *Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 5: Rights Management and Protection (RMP) Sub-part 1: Information for Broadcast Applications.*
+- [ETSI TS 102 822-6-3] ETSI TS 102 822-6-3 V1.6.1 (2012), *Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 6: Delivery of metadata over a bi-directional network; Sub-part 3: Phase 2 – Exchange of Personal Profile.*
+- [ISO/IEC 15938-5] ISO/IEC 15938-5 (2003), *Information technology – Multimedia content description interface – Part 5: Multimedia description schemes.*
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 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.2 metadata** [b-ITU-T IPTV FG]: 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.3 metadata schema** [ITU-T H.750]: A metadata schema is the representation format for a specifying data model describing target instances.
+
+**3.1.4 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:
+
+|      |                                            |
+|------|--------------------------------------------|
+| AV   | Audio and Video                            |
+| CP   | Content Provider                           |
+| DNS  | Domain Name System                         |
+| ECG  | Electronic Content Guide                   |
+| EPG  | Electronic Programme Guide                 |
+| HTTP | Hypertext Transfer Protocol                |
+| ID   | IDentification                             |
+| IP   | Internet Protocol                          |
+| IPTV | Internet Protocol Television               |
+| ISAN | International Standard Audio-visual Number |
+
+|     |                            |
+|-----|----------------------------|
+| SP  | Service Provider           |
+| TLS | Transport Layer Security   |
+| TVA | TV-Anytime                 |
+| URI | Uniform Resource Indicator |
+| URL | Uniform Resource Locator   |
+| VoD | Video on Demand            |
+
+# 5 Conventions
+
+None.
+
+# 6 Introduction
+
+[ITU-T H.750] identifies AV content metadata elements and attributes for IPTV services, for content discovery from IPTV terminal devices based on [ITU-T Y.1910] and [ITU-T H.720].
+
+This Recommendation identifies the requirements for AV content metadata provisioning and the metadata elements and attributes which could be provided by AV content providers. This Recommendation describes AV content metadata elements and attributes which could be transferred from content providers to IPTV service providers, and be integrated by the IPTV service in electronic programme guide (EPG)/electronic content guide (ECG) for content discovery. It also describes the requirements for AV content usage log information of end-user and payment details transferred from an IPTV service provider to content provider.
+
+Two communication modes are specified between content providers and IPTV service providers for the delivery and management of content metadata and content:
+
+- 1) A push mode in which the content providers take the initiative to declare their content to the IPTV service providers.
+- 2) A pull mode in which the IPTV service providers, having a reference to particular content, request information about this content.
+
+# 7 Requirements for AV content metadata provisioning
+
+The metadata schema for the contents to be transferred between the content provider and IPTV service provider is required to support:
+
+- Req1: the intention of the metadata set (new, replace, append).
+- Req2: the identification of the content provider, source of the metadata set.
+- Req3: the content description with elements such as content identification used by the content provider, title, description, keywords, genre. These elements should be taken from the elements already included in metadata schemas specified for ECG/EPG delivery to end-user terminals.
+- Req4: the business information of the content, such as price, charge type.
+- Req5: the possibility to describe several contents in the same set.
+- Req6: the possibility to group features common to all content such as AV attributes, but also to allow individual contents to have different values for these common features.
+- Req7: the possibility to give content location to allow the transfer of the content itself.
+- Req8: the possibility to give content delivery information, such as distribution area and terminal device to be allowed to receive.
+- Req9: the possibility to get the usage information of the content from the end user.
+
+- Req10: the possibility to get the payment detail of the content from the end user.
+- Req11: the procedure of exchanging content metadata between a content provider and service provider.
+
+NOTE – These requirements are not for a metadata instance, but for a metadata schema. Metadata instances will vary depending on the agreements between an IPTV service provider and content provider.
+
+# **8 AV content metadata elements and attributes**
+
+## **8.1 AV content metadata structure**
+
+The two primary classes of metadata for AV content structure are: "Content Catalogue Metadata" which provides content titles and descriptions, and "Business Metadata" which is used to describe contract details, device control information for distribution, and logs used after content is distributed.
+
+The following are described in Content Catalogue Metadata.
+
+- Element groups indicating the content title and description, which is described in clause 8.2;
+- Element groups representing the rights holder of the content, which is described in clauses 8.3 and 8.4.
+
+Because these elements are pieces of information widely open or available to users, they are public information. These elements are also specific to content, thus they do not vary between usage transactions for the content.
+
+Business Metadata is primarily divided into Permissions Metadata and Usage Log Metadata. Permissions Metadata provides information concerning content usage permissions. Usage Log Metadata is a metadata group containing information used to report usage log information, and to describe usage fee details after actual content is used.
+
+The following are described in Permissions Metadata.
+
+- Element group that provides basic business metadata of the AV content assigned by content providers, which is described in clause 8.5;
+- Element group element group providing transaction conditions, which is described in clause 8.6.
+
+The following are described in Usage Log Metadata.
+
+- Element group metadata group that provides usage logs information, which is described in clause 8.7;
+- Element group element group addressing payment accounting information, which is described in clause 8.8.
+
+Business Metadata consists of element groups necessary for content distribution. Generally, information that comprises Business Metadata is shared only between the content administrator and the content user; it is private information.
+
+![Diagram of AV content metadata structure showing nested boxes for Content metadata, Content catalogue metadata (Public), Business metadata (Private), Permission metadata, and Usage log metadata.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+```
+
+graph TD
+    subgraph Content_metadata [Content metadata]
+        subgraph Content_catalogue_metadata [Content catalogue metadata (Public)]
+            CCM[• Element indicating content name and description (clause 8.2)  
+• Element indicating information concerning contents rights holders (clauses 8.3 and 8.4)]
+        end
+        subgraph Business_metadata [Business metadata (Private)]
+            subgraph Permission_metadata [Permission metadata]
+                PM[• Elements indicating transaction information (clause 8.5)  
+• Elements indicating transaction conditions (clause 8.6)]
+            end
+            subgraph Usage_log_metadata [Usage log metadata]
+                ULM[• Element indicating content usage log information (clause 8.7)  
+• Element indicating payment details (clause 8.8)]
+            end
+        end
+    end
+  
+```
+
+H.752(15)\_F8-1
+
+Diagram of AV content metadata structure showing nested boxes for Content metadata, Content catalogue metadata (Public), Business metadata (Private), Permission metadata, and Usage log metadata.
+
+**Figure 8-1 – AV content metadata structure**
+
+In the following clauses, many tables describe the metadata for AV content; every table includes the following domains:
+
+- **Element/attribute name:** describes the element or attribute name.
+- **Description:** describes a detailed description of the element or attribute.
+- **Support:** clarifies if the element is present, how many instances, default value if any, meaning if element is not present.
+
+NOTE – For example: if the support is (0-1), this means that in the actual data, this element may not be present or present just once.
+
+- **Type:** describes the type or format of the element's value.
+- **Notes or value domain:** describes the notes that need to specifically explain or the possible value of the domain.
+
+NOTE – If the domain of the element is blank, the domain has no particular rule.
+
+## **8.2 Data structure for specific AV content elements**
+
+Data structure for specific AV content elements define descriptive attributes of the AV content. It includes a detailed description, such as title, synopsis, genre and other descriptive metadata about the content.
+
+**Table 8-1 – Data structure for specific AV content elements**
+
+| <b>Element/attribute name</b> | <b>Element or attribute description</b>                                                                                                                                                                                                                                                                                         | <b>Support</b> | <b>Type</b> | <b>Notes or value domain</b> |
+|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-------------|------------------------------|
+| Identifier                    | Content identifier allocated by the content provider.                                                                                                                                                                                                                                                                           | 1              | String      |                              |
+| Title                         | A title of the AV content. An AV content can have multiple titles, e.g., in different languages.                                                                                                                                                                                                                                | 1-*            | String      |                              |
+| MediaTitle                    | A media asset (e.g., image) that can be used as a "title" for the AV content. Content that is not part of the original AV content can be specified and used as a (promotional) AV title.                                                                                                                                        | 0-*            | String      |                              |
+| ShortTitle                    | A shortened version of the AV content title that defines how the title should be truncated for presentation purposes.                                                                                                                                                                                                           | 0-*            | String      |                              |
+| Synopsis                      | A textual description of the AV content.                                                                                                                                                                                                                                                                                        | 0-1            | Container   |                              |
+| PromotionalInformation        | A textual description containing promotional information.                                                                                                                                                                                                                                                                       | 0-*            | Container   |                              |
+| Keyword                       | A list of keywords for the AV content. A keyword can be a single word or an entire phrase made up of multiple words.                                                                                                                                                                                                            | 0-*            | Container   |                              |
+| Genre                         | A genre for the AV content.                                                                                                                                                                                                                                                                                                     | 0-*            | Container   |                              |
+| TVAParentalGuidance           | A parental rating code for the AV content.                                                                                                                                                                                                                                                                                      | 0-1            | Container   |                              |
+| Language                      | Describes one spoken language for the AV content. There may be more than one spoken language specified for an AV content.                                                                                                                                                                                                       | 0-*            | Enumeration |                              |
+| CaptionLanguage               | Describes one language of the caption information included with the programme. The type of the caption information associated with the programme is denoted by the closed attribute. Closed captions can be turned on or off by the user, while open captions (or subtitles) are part of the picture itself and remain visible. | 0-*            | Enumeration |                              |
+| SignLanguage                  | Specifies the sign language provided for the multimedia content and, optionally, qualifies the use of signing as a primary language and/or as a translation of the spoken dialogue.                                                                                                                                             | 0-*            | Enumeration |                              |
+
+**Table 8-1 – Data structure for specific AV content elements**
+
+| <b>Element/attribute name</b> | <b>Element or attribute description</b>                                                                                                 | <b>Support</b> | <b>Type</b> | <b>Notes or value domain</b>                                                                    |
+|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|----------------|-------------|-------------------------------------------------------------------------------------------------|
+| CreditsList                   | The list of credits for the AV content.                                                                                                 | 0-*            | Enumeration | e.g., actor/actress, director, producer, scenario writer                                        |
+| AwardsList                    | The list of awards and/or award nominations for the AV content.                                                                         | 0-*            | Container   |                                                                                                 |
+| RelatedMaterial               | A reference to any other material related to the AV content.                                                                            | 0-*            | Container   |                                                                                                 |
+| ProductionDate                | The date or time period when the AV content was produced.                                                                               | 0-1            | Datetime    |                                                                                                 |
+| ProductionLocation            | The country in which the AV content was produced.                                                                                       | 0-*            | String      | e.g., CHN, USA                                                                                  |
+| CreationCoordinates           | Describes the location(s) and date(s) of creation of the AV content (optional).                                                         | 0-*            | Container   |                                                                                                 |
+| DepictedCoordinates           | Describes the location(s) and date(s) depicted in the AV content.                                                                       | 0-1            | Container   |                                                                                                 |
+| ReleaseInformation            | Information about the country and date of release of the AV content.                                                                    | 0-*            | Container   |                                                                                                 |
+| Duration                      | Indicates the approximate duration of the AV content.                                                                                   | 0-1            | Datetime    |                                                                                                 |
+| OtherIdentifier               | A code that can be used in addition to the Content Provider Identifier to identify a piece of content.                                  | 0-*            | String      | e.g., an ISAN [b-ISO 15706-1] to identify a piece of content or an episode or a version thereof |
+| MemberOf                      | Indicates group membership of the AV content – for a reason other than the special cases of derivation or being an episode of a series. | 0-*            | Container   |                                                                                                 |
+| DerivedFrom                   | Indicates that the AV content is derived from another AV content (e.g., by reducing violent scenes) or possibly an AV content concept.  | 0-1            | Container   |                                                                                                 |
+| EpisodeOf                     | Indicates a series from which the current AV content is an episode.                                                                     | 0-1            | Container   |                                                                                                 |
+
+**Table 8-1 – Data structure for specific AV content elements**
+
+| Element/attribute name  | Element or attribute description                                             | Support | Type        | Notes or value domain           |
+|-------------------------|------------------------------------------------------------------------------|---------|-------------|---------------------------------|
+| PartOfAggregatedProgram | An element used to specify that content is part of an aggregated AV content. | 0-1     | Enumeration | e.g., an Omnibus or a Magazine. |
+| AggregationOf           | An element used to describe an aggregated AV content.                        | 0-1     | Container   |                                 |
+
+NOTE – Container type means a class or a structure defined in the original reference documents, the standards referred to in Annex A.
+
+## 8.3 Content location
+
+The content location in Table 8-2 specifies the location of the current AV content, which is a uniform resource locator (URL). It also specifies the features and capabilities of the AV content protection.
+
+**Table 8-2 – Content location**
+
+| Element/attribute name | Element or attribute description                                                                 | Support | Type      | Notes or value domain                                          |
+|------------------------|--------------------------------------------------------------------------------------------------|---------|-----------|----------------------------------------------------------------|
+| Location               | URL to get the content                                                                           | 1       | URL       |                                                                |
+| ContentProtection      | An element used to specify the features and capabilities of the different AV content protection. | 0-*     | Container | e.g., Authentication, transport layer security (TLS) streaming |
+
+## 8.4 Content provider identification
+
+The content provider identification in Table 8-3 specifies the information of content provider.
+
+**Table 8-3 – Content provider identification**
+
+| Element         | Description                                                                      | Support | Type      | Notes or value domain                                           |
+|-----------------|----------------------------------------------------------------------------------|---------|-----------|-----------------------------------------------------------------|
+| ContentProvider | Container for all information related to a content provider.                     | 1       | Container |                                                                 |
+| CPID            | Element of ContentProvider. The unique identifier given to the content provider. | 1       | String    | e.g., an Internet domain name system (DNS) domain name, an URI. |
+| CPName          | Usual name of the content provider.                                              | 1       | String    |                                                                 |
+
+## 8.5 Transaction information elements and attributes
+
+The transaction information elements and attributes given in Table 8-4 define basic business metadata of the AV content assigned by content providers. It includes the area of delivery, price,
+
+receiving devices and other information. A service provider could provide a related service according to the transaction information received from a content provider. Only one of the elements "Price" or "PriceCategory" should be present in the transaction information.
+
+**Table 8-4 – Transaction information elements and attributes**
+
+| Element                 | Description                                                                                                                                                     | Support | Type      | Notes or value domain                                                                                                                                    |
+|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| AVAttributes            | Container for audio-visual attributes that are applicable to the content as originated.                                                                         | 0-1     | Container | Value include:<br>– Codec or format<br>– Aspect ratios, resolution, bit rate, frame rate for video<br>– Mono, stereo, multi-channel indication for audio |
+| Distribution/Conditions | Container for all elements related to the distribution conditions for a specific content or a set of contents.                                                  | 1       | Container |                                                                                                                                                          |
+| Price                   | Element of DistributionConditions<br>It indicates the price to be charged for the content.                                                                      | 0-1     | Float     |                                                                                                                                                          |
+| PriceCategory           | Element of DistributionConditions<br>It indicates the price category of the content. The values are to be agreed between content provider and service provider. | 0-1     | String    |                                                                                                                                                          |
+| Currency                | Attribute of Price.<br>It indicates the currency.                                                                                                               | 0-1     | String    | Restriction of string<br>Pattern value = "[a-zA-Z]{3}"                                                                                                   |
+| Distribution Area       | Element of DistributionConditions<br>It indicates where the content is allowed to be made available.                                                            | 0-1     | Container | Default: everywhere                                                                                                                                      |
+| Distribution StartDate  | Element of DistributionConditions<br>It indicates the time at which the content can start to be made available.                                                 | 0-1     | Datetime  | Default: now                                                                                                                                             |
+| Distribution EndDate    | Element of DistributionConditions<br>It indicates the time at which the content should stop to be made available.                                               | 0-1     | Datetime  | Default: without limit                                                                                                                                   |
+
+**Table 8-4 – Transaction information elements and attributes**
+
+| Element        | Description                                                                                                     | Support | Type      | Notes or value domain |
+|----------------|-----------------------------------------------------------------------------------------------------------------|---------|-----------|-----------------------|
+| TerminalDevice | Element of DistributionConditions<br>It indicates terminal devices which the content is allowed to be received. | 0-*     | Container |                       |
+
+## 8.6 Exchange purpose information
+
+The exchange purpose information in Table 8-5 is used to give the purpose of the current content metadata instance. It includes three purposes, new, replace and append.
+
+**Table 8-5 – Exchange purpose information**
+
+| Element         | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Support      | Type        | Notes or value domain        |
+|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-------------|------------------------------|
+| ExchangePurpose | An attribute used to give the purpose of the current content metadata instance:<br>New: for a new set of metadata.<br>Replace: for a set of metadata intended to replace another set of metadata already available to the service provider (e.g., to correct typing errors in the synopsis or to add new values to elements. Metadata elements present in the previous version will be removed if they are not present in the new version.<br>Append: for a set of metadata intended to be incorporated in another set of metadata already available to the service provider (e.g., to provide titles in other languages, additional awards). It is also a solution to replace just a few elements instead of resending the full set of metadata. | Default: new | Enumeration | Values: new, replace, append |
+
+## 8.7 Usage log metadata
+
+Usage Log Metadata is transferred from service provider to content provider to report usage log, hence the content provider can use the usage log to analyse the usage information. Based on the usage information, a content provider can know which kind of content is the most popular by the end user, so a content provider could adjust the policy of content providing. Table 8-6 give the content usage log information of a certain period.
+
+**Table 8-6 – Usage Log Metadata**
+
+| Element/attribute name | Description                                                             | Support | Type      | Notes or value domain |
+|------------------------|-------------------------------------------------------------------------|---------|-----------|-----------------------|
+| ContentIdentifier      | Content identifier allocated by the content provider.                   | 1       | String    |                       |
+| NumberOfPaid Customers | The total number of customers that viewed and paid for the content.     | 0-1     | Int       |                       |
+| NumberOf TrailerViews  | The total number of times that trailers of the content has been viewed. | 0-1     | Int       |                       |
+| TotalIncome            | The total fee earned from customers.                                    | 0-1     | Container |                       |
+| PaymentDetails         | Payment details from customers.                                         | 0-*     | Container |                       |
+
+## 8.8 Payment details elements
+
+Payment detail elements in Table 8-7 provide details concerning usage fees based on the usage log and transaction conditions.
+
+**Table 8-7 – Payment details elements**
+
+| Element/attribute name | Description                                                      | Support | Type        | Notes or value domain        |
+|------------------------|------------------------------------------------------------------|---------|-------------|------------------------------|
+| UserID                 | It indicates which user has selected this content.               | 1       | String      |                              |
+| ChargeType             | It indicates the type which the user is charges for the content. | 1       | Enumeration | Values: free, package, times |
+| ChargedFee             | The total fee the user pay for the content.                      | 0-1     | Container   |                              |
+
+# 9 Data structures and messages
+
+A number of data structures are identified to convey content declaration, content information requests and responses and usage log report.
+
+## 9.1 Data structure of the content declaration
+
+Data structure of the content declaration in Table 9-1 describes the request message information which is what content providers send to service providers. It includes the content provider ID, exchange purpose, content location, and so on.
+
+Content declaration information is sent by content providers. It is initiated when content providers would pull or push a content to service provider.
+
+**Table 9-1 – Data structure for content declaration**
+
+| <b>Element</b>                 | <b>Description</b>                                                                                                                                                 | <b>Support</b> | <b>Type</b> | <b>Notes or value domain</b>                |
+|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-------------|---------------------------------------------|
+| ContentDeclaration             | Container for the content declaration.<br>It includes all elements related to a specific content or to several contents.                                           | 1              | Container   |                                             |
+| ExchangePurpose                | Attribute of ContentDeclaration<br>This element indicates how the ContentDeclaration should be considered.                                                         | 0-1            | Enumeration | Values: new, replace, append<br>Default:new |
+| ContentProvider                | Element of ContentDeclaration<br>It contains information about the content provider.                                                                               | 1              | Container   |                                             |
+| GeneralAVAttributes            | Element of ContentDeclaration<br>Container for Audio-visual attributes that are applicable to a set of content.                                                    | 0-1            | Container   |                                             |
+| GeneralDistribution Conditions | Element of ContentDeclaration<br>Container for the distribution conditions applicable to a set of contents.                                                        | 0-1            | Container   |                                             |
+| ContentDescription             | Element of ContentDeclaration<br>It is a container for all elements related to a specific content.                                                                 | 1-*            | Container   |                                             |
+| AVAttributes                   | Element of ContentDescriptionElements<br>Container for Audio-visual attributes that are applicable to the specific content here declared.                          | 0-1            | Container   |                                             |
+| Distribution Conditions        | Element of ContentDescriptionElements<br>Container for the distribution conditions applicable to the specific content declared here.                               | 0-1            | Container   |                                             |
+| ContentLocation                | Element of ContentDescriptionElements<br>It indicates from where the content can be acquired.                                                                      | 1              | AnyURI      |                                             |
+| AdInsertionControl ProviderURL | Element of ContentDeclaration<br>It indicates an URL to be called when the content is requested for viewing by an end user, to get information about ad insertion. | 0-1            | AnyURI      |                                             |
+
+## 9.2 Data structure of the usage log report
+
+Data structure of the usage log report in Table 9-2 describes the usage report information that service providers send to content providers. It includes the content provider ID, usage log, and period of the usage log recorded.
+
+The usage log report is usually sent to content providers by service providers, and is sent based on a schedule that they have determined.
+
+**Table 9-2 – Data structure of the usage log report**
+
+| Element            | Description                                                                                         | Support | Type      | Notes or value domain |
+|--------------------|-----------------------------------------------------------------------------------------------------|---------|-----------|-----------------------|
+| ContentProvider ID | Element of ContentProvider.<br>The unique identifier given to the content provider.                 | 1       | String    | Defined in clause 8.4 |
+| UsageLog           | Container for usage log.<br>It includes all elements related to a usage log in the specific period. | 1-*     | Container | Defined in clause 8.7 |
+| PeriodStartTime    | It indicates the time at which the usage log starts to be recorded.                                 | 1       | Datetime  |                       |
+| PeriodEndTime      | It indicates the time at which the usage log stops being recorded.                                  | 1       | Datetime  |                       |
+| UsageLog Location  | It indicates from where the usage log can be acquired.                                              | 1       | AnyURI    |                       |
+
+# 10 Exchanges for content
+
+## 10.1 Declaration mode (push mode)
+
+IPTV content providers initiate an exchange for content request, and for IPTV service providers' response and get the content from content location.
+
+![Sequence diagram showing the steps of declaration mode (push mode) between Content providers and Service providers.](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Content providers
+    participant Service providers
+    Note left of Content providers: Content providers
+    Content providers->>Service providers: Exchange content request (CPID, purpose, content location)
+    Service providers-->>Content providers: Exchange content response (storage location)
+    Note right of Service providers: Service providers
+    Content providers->>Service providers: Content transmission (content metadata, content)
+    Service providers-->>Content providers: Result notification request
+    Content providers-->>Service providers: Result notification response
+  
+```
+
+The diagram illustrates the interaction between Content providers and Service providers in declaration mode (push mode). The sequence of messages is as follows:
+ 
+
+- The Content providers send an "Exchange content request (CPID, purpose, content location)" to the Service providers.
+- The Service providers respond with an "Exchange content response (storage location)".
+- The Content providers then send a "Content transmission (content metadata, content)" to the Service providers.
+- The Service providers send a "Result notification request" to the Content providers.
+- Finally, the Content providers send a "Result notification response" to the Service providers.
+
+ A small label "H.752(15)\_F10-1" is present at the bottom right of the diagram.
+
+Sequence diagram showing the steps of declaration mode (push mode) between Content providers and Service providers.
+
+**Figure 10-1 – Steps of declaration mode (push mode)**
+
+The diagram in Figure 10-1 gives the general steps of the declaration mode:
+
+- 1) Content providers will push content to service providers. Content providers initiate an exchange content request message to service providers. Service providers receive the request message and send back an exchange content response message.
+- 2) If negotiation between content providers and service providers is successful, service providers will get the content metadata and files from content location.
+- 3) When the content transmission is over, service providers will send a result notification request to content providers. Then content providers reply to the service provider with a result notification response.
+
+## 10.2 Content information request mode (pull mode)
+
+IPTV service providers initiate an exchange for content request, and for IPTV content providers' response. Service providers get the content from content location.
+
+![Sequence diagram illustrating the steps of content information request mode (pull mode) between Content providers and Service providers.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg)
+
+```
+
+sequenceDiagram
+    participant CP as Content providers
+    participant SP as Service providers
+    SP->>CP: Exchange content request (CPID, purpose, storage location)
+    CP-->>SP: Exchange content response (content location)
+    CP->>SP: Content transmission (content metadata, content)
+    SP->>CP: Result notification request
+    CP-->>SP: Result notification response
+
+```
+
+The diagram illustrates the sequence of messages between Content providers and Service providers in pull mode. First, the Service provider sends an 'Exchange content request' containing CPID, purpose, and storage location. The Content provider responds with an 'Exchange content response' specifying the content location. This is followed by 'Content transmission' of metadata and content from the provider to the service. Finally, a 'Result notification request' is sent by the Service provider, and the Content provider acknowledges with a 'Result notification response'. The diagram is indexed as H.752(15)\_F10-2.
+
+Sequence diagram illustrating the steps of content information request mode (pull mode) between Content providers and Service providers.
+
+**Figure 10-2 – Steps of content information request mode (pull mode)**
+
+The diagram in Figure 10-2 gives the general steps of the content information request mode (pull mode):
+
+- 1) Service providers will pull content from content providers. Service providers initiate an exchange content request message to content providers. Content providers receive the request message and send back an exchange content response message.
+- 2) If negotiations between content providers and service providers are successful, service providers will get the content metadata and files from content location.
+- 3) When the content transmission is over, service providers will send a result notification request to content providers. Then content providers reply to the service provider with a result notification response.
+
+# Annex A
+
+### Content provisioning metadata schema: Elements and attributes
+
+(This annex forms an integral part of this Recommendation.)
+
+This annex lists the reference source of elements and attributes of the tables in clauses 8 and 9.
+
+### Data structure for specific AV content elements
+
+- Identifier:
+  - [ITU-T H.750] clause 8.1: Elements for content: Identifier
+- Title:
+  - [ITU-T H.750] clause 8.1: Elements for content: Title/name (secondary title)
+- MediaTitle:
+  - [ISO/IEC 15938-5] clause 9.2.2
+- ShortTitle:
+  - [ETSI TS 102 822-3-1] clause 6.3.4 ShortTitleType
+- Synopsis:
+  - [ETSI TS 102 822-3-1] clause 6.3.4 Synopsis
+- PromotionalInformation:
+  - [ETSI TS 102 822-3-1] clause 6.3.4 PromotionalInformation
+- Keyword:
+  - [ITU-T H.750] clause 8.1: Elements for content: Keyword
+- Genre:
+  - [ITU-T H.750] clause 8.1: Elements for content: Genre
+- TVAParentalGuidance:
+  - [ISO/IEC 15938-5] clause 9.2.3
+- Language:
+  - [ITU-T H.750] clause 8.1: Elements for content: Primary (secondary) spoken language
+- CaptionLanguage:
+  - [ITU-T H.750] clause 8.1: Elements for content: Primary (secondary) caption language (with speed parameter)
+- SignLanguage:
+  - [ISO/IEC 15938-5] clause 9.2.3
+- CreditsList:
+  - [ITU-T H.750] clause 8.1: Elements for content: Credits (e.g., actor/actress, director, producer, scenario writer)
+- AwardsList:
+  - [ITU-T H.750] clause 8.1: Elements for content: Awards
+- RelatedMaterial:
+  - [ITU-T H.750] clause 8.1: Elements for content: Preview, supplementary video and descriptive audio
+
+- [ETSI TS 102 822-3-1] 6.3.4 RelatedMaterial (Program, Group), 6.6.2 RelatedMaterial (Segment, SegmentGroup).
+- [ITU-T H.750] clause 8.1: Elements for content: Related web site
+- ProductionDate:
+  - [ITU-T H.750] clause 8.1: Elements for content: Location and time of production
+- ProductionLocation:
+  - [ITU-T H.750] clause 8.1: Elements for content: Location and time of production
+  - [b-ISO 3166]
+- CreationCoordinates:
+  - [ETSI TS 102 822-3-1] clause 6.3.4 CreationCoordinates
+- DepictedCoordinates:
+  - [ETSI TS 102 822-3-1] clause 6.3.4 DepictedCoordinates
+- ReleaseInformation:
+  - [ITU-T H.750] clause 8.1: Elements for content: Acquisition or delivery schedule, start/end availability, protocol and address
+  - [ETSI TS 102 471] clause 5.7.1 PublishedStartTime, PublishedEndTime.
+- Duration:
+  - [ITU-T H.750] clause 8.1: Elements for content: Duration
+- OtherIdentifier:
+  - [ITU-T H.750] clause 8.1: Elements for collective content: IDs for sub-contents
+  - [ETSI TS 102 822-3-2] clause 4.3.1.3 OtherIdentifier (ProgramInformation)
+- MemberOf:
+  - [ETSI TS 102 822-3-2] clause 4.3.1.3 MemberOf (ProgramInformation)
+- DerivedFrom:
+  - [ETSI TS 102 822-3-2] clause 4.3.1.3 DerivedFrom (ProgramInformation)
+- EpisodeOf:
+  - [ETSI TS 102 822-3-2] clause 4.3.1.3 EpisodeOf (ProgramInformation)
+- PartOfAggregatedProgram:
+  - [ETSI TS 102 822-3-2] clause 4.3.1.3 PartOfAggregatedProgram (ProgramInformation)
+- AggregationOf:
+  - [ETSI TS 102 822-3-2] clause 4.3.1.3 AggregationOf (ProgramInformation)
+
+### **Content location**
+
+- Location:
+  - [ETSI TS 102 822-3-1] clause 6.3.4 ProductionLocation
+  - [b-ISO 3166]
+- ContentProtection:
+  - [ITU-T H.750] clause 10 Rights and security-related metadata for IPTV
+
+### **Content provider identification**
+
+- ContentProvider:
+  - [ITU-T H.750] clause 8.1: Elements for content: Name of content provider, service provider
+
+- CPId:
+  - [ITU-T H.750] clause 8.1: Elements for content: Name of content provider, service provider
+- CPName:
+  - [ITU-T H.750] clause 8.1: Elements for content: Name of content provider, service provider
+
+### **Transaction information elements and attributes**
+
+- AVAttributes:
+  - [ETSI TS 102 822-3-1 V1.8.1] clause 6.3.5
+- DistributionConditions:
+  - [ITU-T H.750] clause 8.1: Elements for usage restrictions, usage rule
+- Price:
+  - [ITU-T H.750] clause 8.1: Elements for collective content: Price and conditions of availability of collective content
+- PriceCategory:
+  - [ITU-T H.750] clause 8.1: Elements for service (or channel): Free or subscribed
+- Currency:
+  - [ETSI TS 102 822-3-1] clause 6.3.3 CurrencyCodeType
+  - [b-ISO 4217]
+- DistributionArea:
+  - [ITU-T H.750] clause 8.1: Elements for usage restrictions, usage rules: Restricted area
+  - [ETSI TS 102 471] clause 5.8.1 UsageConstraints
+- DistributionStartDate:
+  - [ITU-T H.750] clause 8.1: Elements for usage restrictions, usage rules: Expiration date or deletion management information
+- DistributionEndDate:
+  - [ITU-T H.750] clause 8.1: Elements for usage restrictions, usage rules: Expiration date or deletion management information
+- TerminalDevice:
+  - [ETSI TS 102 822-3-2] clause 4.3.1.19 TargetingInformationType TerminalInformation
+
+### **Exchange purpose information**
+
+- ExchangePurpose:
+  - [ETSI TS 102 822-6-3] clause 5.3 Modifying Data
+
+### **Usage Log Metadata**
+
+- ContentIdentifier:
+  - [ITU-T H.750] clause 8.1: Elements for content: Identifier
+- NumberOfPaidCustomers:
+  - No reference, new in ITU-T H.752
+- NumberOfTrailerViews:
+  - [ITU-T H.750] clause 8.1: Elements for user profile or preference: Viewing behaviour
+
+- TotalIncome:
+  - [ISO/IEC 15938-5] clause 10.2.3.3 Financial datatype semantics
+- PaymentDetails:
+  - [ETSI TS 102 822-3-1] clause 6.3.4 PurchaseItem
+
+### **Payment details elements**
+
+- UserID:
+  - [ETSI TS 102 822-3-1] clause 6.5.2.3 UserID
+- ChargeType:
+  - [ITU-T H.750] clause 8.1: Elements for service (or channel): Free or subscribed
+- ChargedFee:
+  - [ISO/IEC 15938-5] clause 10.2.3.3 Financial datatype semantics
+
+### **Data structure of the content declaration**
+
+- ContentDeclaration:
+  - [ETSI TS 102 822-3-3] clause 8.2 Declarations
+- ExchangePurpose:
+  - [ITU-T H.750] clause 9.1: Metadata for content provisioning
+- ContentProvider:
+  - [ITU-T H.750] clause 8.1: Elements for content: Name of content provider, service provider
+- GeneralAVAttributes:
+  - [ETSI TS 102 822-3-1] clause 6.3.5 AVAttributes
+- GeneralDistributionConditions:
+  - [ITU-T H.750] clause 8.1: Elements for usage restrictions, usage rule
+- ContentDescription:
+  - [ITU-T H.750] clause 8.1: Elements for content: Description (synopsis, abstract)
+- AVAttributes:
+  - [ETSI TS 102 822-3-1] clause 6.3.5 AVAttributes
+- DistributionConditions:
+  - [ITU-T H.750] clause 8.1: Elements for usage restrictions, usage rule
+- ContentLocation:
+  - [ETSI TS 102 822-3-1] clause 6.3.5 AVAttributes
+- AdInsertionControlProviderURL:
+  - [ITU-T H.750] clause 8.1: Elements for content: Related web site
+
+### **Data structure of the of the usage log report**
+
+- ContentProviderID:
+  - [ITU-T H.750] clause 8.1: Elements for content: Name of content provider, service provider
+- Usage Log:
+  - [ETSI TS 102 822-3-1] clause 6.5.1.1 Usage history
+
+- PeriodStartTime:
+  - [ETSI TS 102 822-5-1] clause 5.3 Time Window Start Date and Time Window End Date
+- PeriodEndTime:
+  - [ETSI TS 102 822-5-1] clause 5.3 Time Window Start Date and Time Window End Date
+- UsageLogLocation:
+  - No reference, new in ITU-T H.752
+
+## Bibliography
+
+- [b-ITU-T Y.1901] Recommendation ITU-T Y.1901 (2009), *Requirements for the support of IPTV services*.
+- [b-ITU-T IPTV FG] ITU-T IPTV Focus Group Proceedings (2008).  
+<<http://www.itu.int/pub/T-PROC-IPTVFG-2008>>
+- [b-ISO 15706-1] ISO 15706-1 (2002), *Information and documentation – International Standard Audiovisual Number (ISAN) – Part 1: Audiovisual work identifier*.
+- [b-ISO 3166] ISO 3166 (2013), *Codes for the representation of names of countries and their subdivisions*.
+- [b-ISO 4217] ISO 4217 (2015), *Codes for the representation of currencies*.
+
+
+
+## **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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.760-200903-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/H/T-REC-H.760-200903-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..93fa4914987f3336127a98415aa9674f3b24e675
--- /dev/null
+++ b/marked/H/T-REC-H.760-200903-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d1948665e4b65fc9844267456c25f40d86eb567797fa0cc0605c39a14b792b1e
+size 74966
diff --git a/marked/H/T-REC-H.760-200903-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/H/T-REC-H.760-200903-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a0a59f1bcc77b175b6fc09958b98bcec772e6e8f
--- /dev/null
+++ b/marked/H/T-REC-H.760-200903-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1c6694e680ee50cb18ce5a4c775995a337205f51c083b09cb89388160b6f9f2
+size 38221
diff --git a/marked/H/T-REC-H.760-200903-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.760-200903-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..405539c4efeaedbf8e4d1e48c3a1dd5aa724344a
--- /dev/null
+++ b/marked/H/T-REC-H.760-200903-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d230ab81238deafd201cac3283a96772cc2be8db061d0c99aa2ffae31971af5e
+size 7518
diff --git a/marked/H/T-REC-H.760-200903-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/H/T-REC-H.760-200903-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c5c98d799694b5e9d5246bb898666e319c9a8968
--- /dev/null
+++ b/marked/H/T-REC-H.760-200903-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e662bfb65b196d639b83aabc4cdc0a301756bbbb9534fd81b9290fac2c3ca78
+size 61943
diff --git a/marked/H/T-REC-H.760-200903-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/H/T-REC-H.760-200903-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..288ef4a8addc5bbba80e26a2fa74b0b38402c3ea
--- /dev/null
+++ b/marked/H/T-REC-H.760-200903-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7d24668bfa417be45e3f473907fd4f6723930477ed00d6abb2b6e41bb1448969
+size 32758
diff --git a/marked/H/T-REC-H.760-200903-I_PDF-E/a3472689858b068ef469213682965325_img.jpg b/marked/H/T-REC-H.760-200903-I_PDF-E/a3472689858b068ef469213682965325_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..204a2cd7484de0acc4af8f8c77416a9432ac2c17
--- /dev/null
+++ b/marked/H/T-REC-H.760-200903-I_PDF-E/a3472689858b068ef469213682965325_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e992411d0c99629e7fc04da6388bac3d7d85c81fe49271498ee9beb019a82ae9
+size 33102
diff --git a/marked/H/T-REC-H.760-200903-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/H/T-REC-H.760-200903-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2ce264bc36623d8e0b745485fff5433d34689c91
--- /dev/null
+++ b/marked/H/T-REC-H.760-200903-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:04cafe2580c2c661959606fa25441e80d2ae887ec93ce9d1658a6b74a18f8143
+size 104221
diff --git a/marked/H/T-REC-H.760-200903-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/H/T-REC-H.760-200903-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..25460f4aa422cda0c8fbb1f404bee79168998006
--- /dev/null
+++ b/marked/H/T-REC-H.760-200903-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2217dbf92ab90cf1ad5b6e88cdef59f02232f12077f0d1419af8dccf8f49832e
+size 63581
diff --git a/marked/H/T-REC-H.765-201504-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.765-201504-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9002ee68e2b9ebf63d27d39ba8c73bdafb0e6be6
--- /dev/null
+++ b/marked/H/T-REC-H.765-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.765-201504-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/H/T-REC-H.765-201504-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2fe6ef5a621620bcd446835a6487498fedac7618
--- /dev/null
+++ b/marked/H/T-REC-H.765-201504-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:086b81450ac5c69ff723ea355ad3cef10ba6b216ddb1b372f11fe1ceb75f4d53
+size 59964
diff --git a/marked/H/T-REC-H.765-201504-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/H/T-REC-H.765-201504-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a86ea9a799dc3c924731f377133fc49a641c5176
--- /dev/null
+++ b/marked/H/T-REC-H.765-201504-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da6d2fce8bdc7a719f407773acdab433b22949c139820be9cfa13e6524570995
+size 49066
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/04cfca33e3fc26513abe649d7474f733_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/04cfca33e3fc26513abe649d7474f733_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a54e90024235db4b831b1d93583cf4d748e8d31f
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/04cfca33e3fc26513abe649d7474f733_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0ec216e86908fc8e48fa077810078208d836181c2e09e5061a9090175da921f6
+size 23487
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fce59c6aaed96de41f72c402e843e5bca227bc1b
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b6e4e5800a7259ded1a7937f5a4cbcefcf15ef5ed28c41e19b5a62cdbda344d7
+size 74635
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bd7c24e83d75a6b1baa7fb4210f76345166390c9
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5866ab521163bd4f911ae6e27d0a1cf1f491c665e9b87b7d7076098a143f4bff
+size 3944
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..90f6d380e306240737d7dcac5eeabe49f6f831aa
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6a7d9965f27aa509ce8cbe39dafe67b9c379a1f6f321723b1a1dc0f8c8b39f7d
+size 257054
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9ba06765e6584ed61d5fd55ab2f0ec946b938b0e
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6440abfaed50fa7fc222dfc902fa11e98859edf8aae16579dc502e514bff40c6
+size 48132
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d56bf2219bb00f10fcbbb59033c5aa93ecc24d76
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5f8079c5b32bb6cf6833e09263c6dc76cf0877ac7d5a89e0c7c14471796bae51
+size 24653
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7aba5613c5a4f23a3c7d266fa9a177ed06200770
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:de570dd283b7eb55953f9789fd94753273126f66e015503c3813689ea010acb0
+size 75215
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..20c24990dd7eed82b21305fb44cb01edbc27971a
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7a2b2410821b3d9fb67f60960a977def7d82be2328411c01361642be6f867f53
+size 26192
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3eb15709a9c3af88a864c6c2a501241481b125d1
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:46e09ff9135de5063799d446e0637b61338488c17c4f5c94f0828bfcc04eafd7
+size 17262
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..63144661c526ec3a475c502ea912a171f7d4d661
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:73ab948d9a37d0f9704eaf5e1d6ecd3c9b80d9de6752dc9d2f503fbb1efa3361
+size 25782
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6e6962f75d4ebe57796352825ecc16a4da38fb82
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:51f8dfa663a99dac5dc59ffcd0297951a63a397b4814c4d84c5197d6f7ca0e5c
+size 40270
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a800060244eef09430459d996ee77fe917d713b6
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ce328fe02985797e30ccc2d0ca5c1dbef3ab839ed2e12a73febb08acd0d1d61a
+size 73392
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ab2d3a324519aae7b1a32eee7fedcebd640a00d0
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4ad1da2165d755180578a3a6dd4eeabf6a5634262f1953ba25d47b2af85087d1
+size 28432
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1f7aa700be3ed7a94f8aeac5e0a1bff80de1e63b
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b4fbac434955af8cf0dd0104e8373fd22887ae9a620cd35b44bc8c017805968
+size 55263
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9581fae47d7baf350393bf94c00c6db2cf30c63d
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:91a455344b5b311d2538bb1e4ad0a2512cfadba833052da3295783f24948326a
+size 48267
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/9dc9f41d7d76c1add4b190d348cb1533_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/9dc9f41d7d76c1add4b190d348cb1533_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36857c19531c76b44453f623d481b93e0b73c103
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/9dc9f41d7d76c1add4b190d348cb1533_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:37e758efdd19127242b80587a4da2c7951f5f912156e87579e3071a79699eb7d
+size 53768
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..724dd0ecbf5e2fb32767098555df816b804c95db
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:792ca365f482f54f26f7c455bb550524cf333d5ba57d4d2646cb8be85be16017
+size 19003
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c9cc5753e3bb3cf93c5e634ad7642cdfdd0dfa0a
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:25645354c5aa42b7de218fd635b7bec86bda98bda1408ac1f316b20082250496
+size 25378
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..37d214c86538e79f004cc16160a5c72358bb8bc6
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:49375dfdc11c562a9690a4a83dd4758ab731a82ca768b41ddbe37f76967fb665
+size 37915
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7d6810ca47ef4b2cb7e562dab4e1577984f37bcb
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f6d0675ebd00c99a96301667ab964b162023dd2b98da8bcf795e0fc294d0d780
+size 32753
diff --git a/marked/H/T-REC-H.770-201504-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/H/T-REC-H.770-201504-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..49ece2167f70c7b65518ca57a0e75bbd76b121c1
--- /dev/null
+++ b/marked/H/T-REC-H.770-201504-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:297133f4287a0b0c4c9f0bd1d913be5bec91ed042d8c679716936a80745cb09e
+size 33377
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e5641c108050e2d2040d263308f0354a26419051
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cefbb4afeab4dc8fe17edf52812620a03bb4c360ad98792574dd15b19624c708
+size 81436
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3763acd7a0ed56aa30f3f90468c1fb0cb54573eb9045bca3eddf8976b4f0f41d
+size 7219
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e4167f286350ce3fa4f213bdc106a0f3fc22606a
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1c9084a8502940cba41bac8d7b1fb309d6d1599a8188f894ab20052758b30407
+size 92830
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4db70fb4125769311972172a0e8be81e05d7d726
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:86e44bfd3a47d50e7c0beaf6695c305d47223c4d242145bd546482fb090316da
+size 68067
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/2837ffdadcdb1e5bababa56b564e56ed_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1afb03e131a60fe59a946a61621589b7c104a59e
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/2837ffdadcdb1e5bababa56b564e56ed_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:610d697ba8d89bb6b20fee1d404b6e765b2621c4d2eb70232f223bfbe18e24fd
+size 83207
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..92a6518583f9d80da6e6559c3bec9c9538f667a1
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0a967b58e4465ab691342ff18c416b61264bd5baea5038478507ff52f9678688
+size 108013
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..db2f26e34acb24effefc011cfe427b17bd83f2cd
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:01dbf6bfb09a8b3b705ffddf3be2c9d2201e40d73644794faf96a77f44e72e67
+size 97503
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6b95fa2e18e44d04eeb145ebd7795e71f2e1728b
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8d0a5393fc475cb996e12c27ff8a208cbd45e3efc1ba4684a9076cadee6eca0f
+size 68685
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..05ad792c350486da6929c7a210e828d54fd679a0
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88351d56cc5dcf0c86c2a71218dbf0ce7dfda4f1e12762a604eb48d9c0c6c5cc
+size 58322
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..45e71da795071e3228a20d09103336c7736a14f9
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:04497e4eba99f5a8c7f77613135c5270a2878060a68d667faec4152b104d9b0d
+size 112964
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6db87caf48651d79d77bef79e7ef8e6e56c2c9c5
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d28813cc24ff4df26ff2f9cc675e7fbd0e6a4bb777366145315a9b01bd808c4d
+size 131790
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e6ecf8bd3740092b8ceebfb71e0a5eed3cfbff3f
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a8a2fd5e658753cb33ad0a9c1c203d21ac6d1644a76a277835af9f1c01753c68
+size 54511
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cdee6997805a9147bda5bb1c1a90efe5bf7749b3
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6886c1285843024b508575129bf683710696efe110d3a08a9f49c592a78fd892
+size 104616
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6b43a80b59051535e056ae0d98fc8a08a7df0a6a
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7cd80a864fd12993f24ea862103b988f94ab72373b6edce77bb3975e4eeff2b8
+size 53425
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7ff7ca81436f7ddf64b4c80f9234c0b1abd88338
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:db87ddc44c7e6ea6dbbe59193ae832044c5db643ec7fef748b0fe52ce5b3332b
+size 105057
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..35ccd65597707200a0ee099715d9ad3c3749c68c
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a750de11de95c1c697be84597668ffad6290b363bf24d4d7573007d031ab7299
+size 53054
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a50047582741ba09272a13a833644f555a8a6370
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c92215a0285907e79ef7c823e9a755115be56beffef43cd8db3281ee976cce8e
+size 95159
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3fbeb730e36ba5d11beb3804b8428384c7dc2e72
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bb40313ae436c688a23ac0366d65141c20683790c8aa5097992667f8b926135e
+size 84221
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5b99d9b40afb7c3a12d2e1e130dc4299a8b79701
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:74691247785f9787f9f4572565cde35f2f790aac02701d7779c464169fc906a8
+size 79356
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aa04100c38c580c91493c5a18e3798f8afdec30f
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5e795c193172e3e12a195278c09eca58a06a2ff2676d2f3ac93fb0ba60323806
+size 101596
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..08318ad190248c9847424325068f3c344fe42c86
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6dc95a0ecaf47c6104102ec5544c4417880faff1489a59fbd51e817eff9c3bbc
+size 93173
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c5eb122513850733f324dc0124e6637ee8fb3572
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bc464f9ededfe274eda1b32b8abf419be37ab5290de843a0113167df2ab145d5
+size 111582
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3d556b31094eb22c3382c639f8ef92eafd94788d
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:602a09a74998bb085cac29738d4e22c2a26e91e6216c1ae551b7c895a465ceaf
+size 84464
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7bc7508c2b81ef507477b3063022a8737da98c66
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1e3d4191a64dd80525ddb2363008b0ed20993e423380ed15de576864f809bde7
+size 96341
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ed0dc50ddba0d8947eb3eaf5c9a9c16779ab7e4b
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f33148a227afd3b7f3833a8ce777b395f00f009e71f7e49a19d965a1a175aacb
+size 114025
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a6d5b3d790f86fb762b0dee8012e56084c15b3bb
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf1608316ff138147fff86a4728b180b7c977874b90a9d125b2483482102ce7c
+size 108857
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1b2a65dcd13714dfaba2b2f4c04d2b1bb4efec9f
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d5ee3ccbfc8ed33ffdc0a75d92fca5539e3d7252a34d771412b2fe74cb4f2a6c
+size 99836
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg b/marked/H/T-REC-H.770.1-202512-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9c091c201251b5e92233c59c19418d822645d26a
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5abf465bcb91fcf827638ab522e9800ca5164bfc58faedc22625108a9e4c91e9
+size 92003
diff --git a/marked/H/T-REC-H.770.1-202512-I_PDF-E/raw.md b/marked/H/T-REC-H.770.1-202512-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..edac48487571a88217ac6c4dac6c4c1f4e1b3050
--- /dev/null
+++ b/marked/H/T-REC-H.770.1-202512-I_PDF-E/raw.md
@@ -0,0 +1,1366 @@
+
+
+# Recommendation**ITU-T H.770.1 (12/2025)**
+
+SERIES H: Audiovisual and multimedia systems
+
+IPTV multimedia services and applications for IPTV – IPTV service discovery up to consumption
+
+---
+
+### **Service scenarios and high-level requirements for metaverse cross-platform interoperability**
+
+![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        |
+| 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        |
+| <b>IPTV service discovery up to consumption</b>                 | <b>H.770-H.779</b> |
+| 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.770.1
+
+## Service scenarios and high-level requirements for metaverse cross-platform interoperability
+
+## Summary
+
+Recommendation ITU-T H.770.1 specifies service scenarios and high-level requirements for metaverse cross-platform interoperability.
+
+With the increasing number of metaverse platforms being developed, there is a need to create open and seamless interoperable environments between metaverse platforms that foster innovation and collaboration. This Recommendation aims to identify the various intended service scenarios and high-level requirements of four types of metaverse cross-platform interoperability: avatar interoperability, asset interoperability, content interoperability and identity interoperability.
+
+## History\*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T H.770.1  | 2025-12-14 | 21          | 11.1002/1000/16604 |
+
+## Keywords
+
+Metaverse, metaverse cross-platform interoperability, requirements, service scenarios.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <https://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                                              | 1    |
+| 4 Abbreviations and acronyms .....                                                         | 2    |
+| 5 Conventions .....                                                                        | 2    |
+| 6 Overview of metaverse cross-platform interoperability .....                              | 2    |
+| 6.1 Metaverse interoperability .....                                                       | 2    |
+| 6.2 Aspects of metaverse cross-platform interoperability .....                             | 3    |
+| 6.3 Metaverse cross-platform interoperability .....                                        | 5    |
+| 7 Service scenarios of metaverse cross-platform interoperability .....                     | 6    |
+| 7.1 Metaverse search: Cross-platform metaverse content discovery service .....             | 7    |
+| 7.2 Metaverse learning: Content exploration and learning across platforms .....            | 10   |
+| 7.3 Metaverse exhibitions: Cross-platform metaverse exhibitions .....                      | 13   |
+| 7.4 Metaverse safety patrol: Safety patrol service.....                                    | 15   |
+| 7.5 Metaverse SNS: Social networking services in the metaverse.....                        | 18   |
+| 7.6 Metaverse shopping: Cross-platform metaverse shopping.....                             | 22   |
+| 7.7 Metaverse tourism: Seamless exploration across multiple platforms .....                | 23   |
+| 7.8 Metaverse signage: Product promotion with seamless transitions cross-platforms.....    | 25   |
+| 7.9 Metaverse co-working: Cross-platform metaverse co-working .....                        | 29   |
+| 8 High-level requirements for metaverse cross-platform interoperability .....              | 31   |
+| 8.1 General requirements for metaverse cross-platform interoperability.....                | 31   |
+| 8.2 High-level requirements for avatar interoperability .....                              | 31   |
+| 8.3 High-level requirements for asset interoperability .....                               | 31   |
+| 8.4 High-level requirements for content interoperability .....                             | 32   |
+| 8.5 High-level requirements for identity interoperability.....                             | 32   |
+| Appendix I – Use cases of the interoperability between metaverses with digital twins ..... | 33   |
+| I.1 Smart sustainable mobility .....                                                       | 33   |
+| I.2 Cyber physical security .....                                                          | 37   |
+| Bibliography.....                                                                          | 40   |
+
+
+
+# Recommendation ITU-T H.770.1
+
+## Service scenarios and high-level requirements for metaverse cross-platform interoperability
+
+# 1 Scope
+
+This Recommendation specifies service scenarios and high-level requirements for metaverse cross-platform interoperability. The scope of this Recommendation includes the following:
+
+- Service scenarios of the metaverse cross-platform interoperability;
+- High-level requirements for the metaverse cross-platform interoperability.
+
+Some use cases of interoperability are provided in the appendix.
+
+# 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 digital signage (DS)** [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.2 avatar** [b-ISO/IEC 23005-4]: Entity that can be used as a (visual) representation of the user inside the virtual environments.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 metaverse:** An integrative ecosystem of virtual worlds offering immersive experiences to users, that modify pre-existing value and create new value from economic, environmental, social and cultural perspectives.
+
+NOTE – A metaverse can be virtual, augmented, representative of, or associated with the physical world.
+
+**3.2.2 home avatar:** Primary version of an avatar which exists within the original metaverse platform, remaining customizable for its corresponding entity and residing exclusively within a specific metaverse platform or avatar service.
+
+NOTE – The entity includes users, Internet of things (IoT) devices, robots, digital humans, artificial intelligence (AI), system components, etc.
+
+**3.2.3 roaming avatar:** An avatar transitioning across various metaverse platforms from its original metaverse platform, potentially undergoing alterations or transformations to align with the destination platform's compatibility and features.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|       |                                                    |
+|-------|----------------------------------------------------|
+| AI    | Artificial Intelligence                            |
+| API   | Application Programming Interface                  |
+| AR    | Augmented Reality                                  |
+| CMMV  | City Mobility Metaverse                            |
+| DTIFC | Digital Twin Interoperability Functional Component |
+| MAAS  | Mobility-As-A-Service                              |
+| MCDSP | Metaverse Content Discovery Service Provider       |
+| NFT   | Non-Fungible Token                                 |
+| SDMV  | Smart Driving Metaverse                            |
+| SEMV  | Smart Environment Metaverse                        |
+| STMV  | Smart Transportation Metaverse                     |
+| SNS   | Social Networking Service                          |
+| URL   | Uniform Resource Locator                           |
+| VoIP  | Voice over Internet Protocol                       |
+| VR    | Virtual Reality                                    |
+
+# 5 Conventions
+
+The following conventions are used in this Recommendation:
+
+- The keywords "is required to" indicate a requirement that 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 that is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance.
+
+# 6 Overview of metaverse cross-platform interoperability
+
+## 6.1 Metaverse interoperability
+
+In general, virtual worlds in the metaverse are constructed on a single metaverse platform. Since the avatars and digital assets of users are developed in the platform, users can move from one virtual world to another with their avatars and assets (without any modifications) within the platform. In this regard, interoperability of avatars and assets on a single metaverse platform is achieved as a basic feature, as shown by the green line in Figure 6-1.
+
+In a multi-platform environment, as shown in Figure 6-1, the avatar of user Bob created on platform 2 cannot visit virtual world A on platform 1, as the avatar development mechanism and/or data format on platforms 1 and 2 may differ. User Alice has to create or set up another avatar on platform 2 when she wants to visit virtual world B on platform 2. In addition, assets and content created on metaverse platform 1 cannot move to metaverse platform 2, as shown in the blue line of Figure 6-1.
+
+Interoperability is important in the development of the metaverse because it allows developers to create and share content across different platforms. It also allows users to have a seamless and cohesive experience, as they can move between different virtual worlds without creating new accounts or starting from scratch. Relevant standardization activities in other standards development organizations (SDOs) are listed in Appendix I. Standards for metaverse cross-platform interoperability are required.
+
+![Figure 6-1 – Overview of metaverse interoperability](acfc53eca625d62b38aa2563efa95c3e_img.jpg)
+
+The diagram illustrates the concept of metaverse interoperability between two platforms. 
+**Metaverse platform 1** (left) is enclosed in a blue dashed box and contains three virtual worlds: 
+- **Virtual world A**: An oval containing a cityscape, a snowman, trees, a cat, a rabbit, and a gingerbread man. A bicycle is labeled as a "Digital asset".
+- **Virtual world C**: An oval containing a cityscape, a rabbit, a robot, and a landscape. A cityscape image is labeled as "Digital content".
+**Metaverse platform 2** (right) is enclosed in a blue dashed box and contains:
+- **Virtual world B**: An oval containing a planet, stars, a bicycle, a gingerbread man, and a landscape.
+
+Between the platforms is a vertical yellow double-line labeled "Metaverse cross-platform interface". Four yellow boxes highlight interoperability types:
+- **Asset interoperability**: A blue arrow connects the bicycle in Virtual world A to the bicycle in Virtual world B.
+- **Avatar interoperability**: A blue arrow connects the gingerbread man in Virtual world A to the gingerbread man in Virtual world B.
+- **Content interoperability**: A blue arrow connects the digital content in Virtual world C to Virtual world B.
+- **ID interoperability**: Positioned at the base of the interface.
+
+Users are shown outside the platforms:
+- **User: Alice** (left) is connected via a red arrow to an avatar in Virtual world A labeled "Alice (Avatar)". A green arrow also points from her to an avatar in Virtual world C.
+- **User: Bob** (right) is connected via a red arrow to an avatar in Virtual world B labeled "Bob (Avatar)".
+
+The bottom right corner contains the code "H.770.1(25)".
+
+Figure 6-1 – Overview of metaverse interoperability
+
+Figure 6-1 – Overview of metaverse interoperability
+
+## 6.2 Aspects of metaverse cross-platform interoperability
+
+The need for metaverse cross-platform interoperability arises from the fact that there are multiple metaverse platforms being developed by different companies, each with its own set of rules, protocols, and assets. This might cause a fragmented metaverse environment, making it difficult for users to move between different virtual worlds and for developers to create cross-platform applications.
+
+There are different aspects of metaverse cross-platform interoperability to enhance the user experience. This document focuses on the following aspects:
+
+- **Avatar interoperability:** This refers to the ability of digital entities, including users to move avatars between different metaverse platforms while preserving their appearance, identity and functionality. It allows users to create a single avatar that can be used across multiple virtual worlds, eliminating the need to create a new avatar for each platform. By maintaining consistency and continuity of their digital representation, users can engage in various environments and situations, while also facilitating identity recognition and user tracking. Achieving avatar interoperability requires compatibility of avatar attributes such as access rights/agreements, appearance, movements, and behaviours across different platforms. Common standards and protocols for avatar creation, customization, and transfer are essential in ensuring avatar interoperability between platforms.
+- **Asset interoperability:** This refers to the transfer of digital assets, such as tokenized items like non-fungible tokens (NTFs), virtual real estate, and digital currencies, across metaverse platforms. It enables digital entities including users to move and transact their assets across platforms, fostering cross-platform commerce. Achieving asset interoperability involves
+
+leveraging technologies like blockchain to facilitate secure and transparent asset transfers. The establishment of standards and protocols for asset formats and metadata is essential in ensuring compatibility and enabling the interoperability of these digital assets between metaverse platforms.
+
+- **Content interoperability:** This refers to the ability of different metaverse platforms to share and exchange various digital elements associated with activities in the metaverse, such as user-generated content, games, experiences, and applications. This encompasses a diverse range of media formats, including 3D images, animation, sound, text, digital objects and digital elements. It is crucial that such content is compatible and exchangeable across platforms, requiring the establishment of standards and protocols for content formats, metadata, and licensing, as well as for content discovery, storage, and retrieval mechanisms. It also requires the development of tools and technologies that enable creators and developers to easily create, share, and distribute content across different platforms. This eliminates the need to duplicate the content creation process for each platform, streamlining workflows and enhancing collaboration in the metaverse ecosystem, as well as ensuring content storage, retrieval, archiving, and disposition that meet legal and regulatory requirements.
+- **Identity interoperability:** This refers to the transfer of entities' identities between different metaverse platforms. It enables the entities to maintain unified identities across multiple virtual worlds, allowing for a smooth transition between platforms without the need to create new accounts. This encompasses not only the identities of the entities but also identity-related aspects for all entities within the metaverses, such as avatars and their associated items. To achieve identity interoperability, digital identities should be designed to be unique and consistently recognized across metaverse platforms.
+
+The interoperability aspects cannot be strictly divided and there may be some overlap since cross-platform interoperability relates to each interoperability aspect. For example, when an avatar moves to another metaverse platform, it needs to exchange the avatar information, avatar content, identity and assets. Figure 6-2 shows the logical relationship among the four interoperability aspects as follows:
+
+- Users can maintain several distinct user identities/accounts within a platform or across multiple platforms;
+
+NOTE 1 – This allows a single user to take on different online personas suited to various contexts, interests and social circles.
+
+- A single user identity possesses more than one user asset and avatars, enabling a diverse range of personalized experiences and interactions;
+- An avatar and user can hold digital assets, including digital items and digital currencies;
+
+NOTE 2 – Digital currency is an asset used for transactions in the metaverse.
+
+NOTE 3 – An avatar can take avatar-owned assets when moving to another metaverse.
+
+NOTE 4 – Digital assets can be moved by a user between user-owned assets and avatar-owned assets.
+
+- The shapes of digital items and avatars are one of the types of content;
+- Digital items can be attached to avatars, such as fashion items and accessories;
+- Digital items can be worn by avatars, such as clothes, costumes and hats.
+
+By securing interoperability of these aspects, it is possible to ensure interoperability across heterogeneous metaverse platforms.
+
+![Figure 6-2: Relationships among cross-platform interoperability aspects. The diagram illustrates the interconnectedness of Identity, Avatar, Content, and Asset interoperability. Identity interoperability includes Avatar, Asset, and User identities. Avatar interoperability includes Information, Model, Clothes, and Accessory. Content interoperability includes Media, Interact, Object, and Space. Asset interoperability includes Avatar-owned and User-owned assets, which consist of Digital items and Digital currency. Relational descriptions are shown with dashed lines.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+The diagram illustrates the relationships between various interoperability aspects in a metaverse environment. It is structured as follows:
+
+- Identity interoperability** (top right) is the overarching category, which includes:
+  - Avatar identity** (left): Identified by the **Avatar**.
+  - Asset identity** (left): Identified by **Avatar-owned assets** and **User-owned assets**.
+  - User identity** (left): Owns **User-owned assets**.
+- Avatar interoperability** (top center) includes:
+  - Avatar**: Represented by **Information**.
+  - Information**: Part of **Contents interoperability**.
+- Contents interoperability** (center) includes:
+  - Model**, **Clothes**, and **Accessory**: Wearable by the avatar and attachable to the avatar.
+  - Content identity** (right): Identified by **Model**, **Clothes**, and **Accessory**.
+- Asset interoperability** (center) includes:
+  - Avatar-owned assets**: Consists of **Digital items** and **Digital currency**. Movable.
+  - User-owned assets**: Consists of **Digital items** and **Digital currency**.
+- Metaverse content** (bottom) includes:
+  - Media**, **Interact**, **Object**, and **Space**: Represented by icons.
+
+----- Relational description
+
+Figure 6-2: Relationships among cross-platform interoperability aspects. The diagram illustrates the interconnectedness of Identity, Avatar, Content, and Asset interoperability. Identity interoperability includes Avatar, Asset, and User identities. Avatar interoperability includes Information, Model, Clothes, and Accessory. Content interoperability includes Media, Interact, Object, and Space. Asset interoperability includes Avatar-owned and User-owned assets, which consist of Digital items and Digital currency. Relational descriptions are shown with dashed lines.
+
+H.770.1(25)
+
+**Figure 6-2 – Relationships among cross-platform interoperability aspects**
+
+## 6.3 Metaverse cross-platform interoperability
+
+Metaverse cross-platform interoperability refers to the ability of different metaverse platforms to interact seamlessly, allowing digital entities including users to access content, assets and experiences across multiple virtual worlds. This interoperability is achieved by standardized protocols that enable communication and data exchange between different metaverse platforms.
+
+Two different approaches may be considered to achieve interoperability between different metaverse platforms: direct and indirect interoperability.
+
+- **Direct interoperability** refers to the ability of two or more metaverse platforms to directly communicate and exchange data with each other, using a common set of protocols and application programming interfaces (APIs). For example, a user could enter one metaverse platform with their avatar and virtual assets and then move to another platform without having to go through transfer processes. Direct interoperability requires cooperation between the different metaverse platforms and the creation of common standards and protocols for asset and avatar transfer. These standards would need to be agreed upon and implemented by all participating platforms. This is a complex process that requires a lot of coordination and agreement between different parties, but if successful, it would greatly enhance the user experience and create a seamless and interconnected metaverse.
+- **Indirect interoperability** refers to the ability of different metaverse platforms to indirectly communicate and exchange data with each other through data-exchange functions which might be provided by the third-party services, which are services developed and provided by a party other than the company that owns the metaverse platform. The data-exchange functions could offer additional features, functionalities, or experiences to users, complementing the core services provided by the metaverse platform itself. The exchange services could include virtual asset exchanges, ownership and intellectual property rights
+
+management, identity verification, authentication services, and policy interoperability services. For example, a user could export their avatar or digital assets from one platform, and then import them into another platform. While indirect interoperability is less seamless than direct interoperability, it can still provide a way for users and content creators to share and reuse content across different platforms.
+
+Figure 6-3 depicts the concept of metaverse cross-platform interoperability, which implies, for example, being able to use the same avatar and items in different metaverses, or being able to join the same virtual event from different devices.
+
+![Diagram illustrating the concept of metaverse cross-platform interoperability between two platforms, A and B, mediated by third-party services.](042733dc5e8e7f5f30b60adba3266cde_img.jpg)
+
+The diagram shows two metaverse platforms, A and B, each with 'Other functional components' and 'Functional components for interoperability' (Avatar, Content, Assets, Identity). 'Direct interoperability' is shown as a solid double-headed arrow between the functional components of both platforms. 'Indirect interoperability' is shown as a dashed double-headed arrow between the platforms, mediated by a row of 'Third-party services' which includes 'Virtual asset exchanges', 'Ownership and intellectual property rights management', 'Identity verification and authentication services', and others. The reference H.770.1(25) is noted in the bottom right.
+
+Diagram illustrating the concept of metaverse cross-platform interoperability between two platforms, A and B, mediated by third-party services.
+
+**Figure 6-3 – Concept of metaverse cross-platform interoperability**
+
+# 7 Service scenarios of metaverse cross-platform interoperability
+
+This clause describes several notable service scenarios realized by interoperable metaverse platforms. These service scenarios are not fully implemented because no interoperability capability between platforms is provided yet.
+
+Table 7-1 summarizes the relationships of service scenarios and required interoperability aspects which are described in clause 6.
+
+**Table 7-1 – The relationship of service scenarios and interoperability (IOP) aspects**
+
+| Scenario           | Description                                                                                                                                        | Avatar IOP       | Asset IOP                         | Content IOP                         | Identity IOP | Ref. |
+|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-----------------------------------|-------------------------------------|--------------|------|
+| Metaverse search   | This service acts as a directory or marketplace for the metaverse, showcasing various offerings from different creators, providers, or businesses. |                  | Content purchase, Content publish | Content discovery/ preview/mashup   |              | 7.1  |
+| Metaverse learning | Metaverse learning is a virtual school where users, including teachers and students, can connect remotely for learning.                            | Avatar migration |                                   | Content retrieval, Content purchase |              | 7.2  |
+
+**Table 7-1 – The relationship of service scenarios and interoperability (IOP) aspects**
+
+| Scenario                | Description                                                                                                                                            | Avatar IOP                               | Asset IOP                       | Content IOP                                                         | Identity IOP                      | Ref. |
+|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|---------------------------------|---------------------------------------------------------------------|-----------------------------------|------|
+| Metaverse exhibition    | Metaverse exhibition is a virtual exhibition that exists across multiple metaverse platforms.                                                          | Avatar migration                         | Asset migration                 | Media art migration                                                 |                                   | 7.3  |
+| Metaverse safety patrol | Safety patrol can monitor threats in the metaverse, support victims and punish perpetrators to make the metaverse world a safer place.                 | Safety patrol dispatch, Avatar migration |                                 |                                                                     | Reputation query, Access control  | 7.4  |
+| Metaverse SNS           | The metaverse can be a new area of social networking, where users can interact with each other and digital objects in real time in a virtual world.    | Avatar migration                         | Asset migration                 | Social decoration, sharing photos/posts/videos, spatial interaction | Social networking, Access control | 7.5  |
+| Metaverse shopping      | In metaverse shopping, a user can buy/sell virtual items or invest in property.                                                                        | Avatar migration                         | Asset migration                 | Item purchase                                                       |                                   | 7.6  |
+| Metaverse tourism       | The metaverse tourism service allows travel enthusiasts to create customized tourism experiences that take them through different metaverse platforms. | Avatar migration                         | Asset purchase, Asset migration |                                                                     |                                   | 7.7  |
+| Metaverse signage       | Metaverse signage is virtual signage that displays wayfinding information between different metaverse services offered within the platform.            | Avatar migration                         |                                 |                                                                     |                                   | 7.8  |
+| Metaverse co-working    | Metaverse co-working is a virtual co-working service that allows users to collaborate and communicate remotely in a more immersive way.                | Avatar migration                         |                                 | Meeting material migration                                          |                                   | 7.9  |
+
+## 7.1 Metaverse search: Cross-platform metaverse content discovery service
+
+A discovery service in the metaverse is a tool that helps users find and access various virtual experiences, content, or services within the metaverse. This service acts as a directory or marketplace for the metaverse, showcasing various offerings from different creators, providers, or businesses. It is also possible to create mashup services or content by combining content from other distributed metaverse platforms.
+
+### 7.1.1 Description
+
+The contents and service discovery for the metaverse should allow users to search for specific content or services based on keywords, categories, or other criteria and filter results based on factors such as popularity, price, or creator. Furthermore, it is necessary to support multimodal inputs from users. Users can preview content or experiences before purchasing them and read reviews from other users to make informed decisions. Social recommendations can also be available based on the user's social connections, interests, or past experiences in the metaverse.
+
+As it is, a discovery service in the metaverse aims to make it easier for users to find, access, and engage with the vast array of offerings.
+
+Users can search for services that other metaverse platforms provide through the discovery service. It is essential to identify which content is interoperable and which is not, as the distributed metaverse platform will offer independently operated services. Platform service providers can enhance competitiveness by linking with various metaverse platforms to support interoperability. In addition, users can create their own content or services by combining the metaverse content that has been searched and deploying it on their metaverse platforms. Figure 7-1 shows the concept of the metaverse content discovery service scenario.
+
+![Figure 7-1: Concept of the metaverse content discovery service scenario. The diagram illustrates a cross-platform service flow and its underlying infrastructure. The top section shows a linear process: Search (magnifying glass icon), Preview (storefront icon), Purchase (handbag icon), Mash-up (person with headphones icon), and Publish (clothing rack icon). Below this, three 'Metaverse' boxes are connected by dashed double-headed arrows, each labeled with the full process: 'Content discovery, preview, purchase, mash-up, publish'. The bottom section shows three metaverse platforms: 'Metaverse platform B', 'Metaverse platform A', and 'Metaverse platform C'. Platform B and A are connected by double-headed arrows labeled 'Content interoperability' and 'Asset interoperability'. Platform A and C are also connected by similar arrows, with a vertical 'BRIDGE' element between them. All three platforms are connected to a central 'Metaverse content discovery service provider' at the bottom. A small code 'H.770.1(25)' is in the bottom right corner.](bd671b21db63e6fdb2196e9b18502aac_img.jpg)
+
+H.770.1(25)
+
+Figure 7-1: Concept of the metaverse content discovery service scenario. The diagram illustrates a cross-platform service flow and its underlying infrastructure. The top section shows a linear process: Search (magnifying glass icon), Preview (storefront icon), Purchase (handbag icon), Mash-up (person with headphones icon), and Publish (clothing rack icon). Below this, three 'Metaverse' boxes are connected by dashed double-headed arrows, each labeled with the full process: 'Content discovery, preview, purchase, mash-up, publish'. The bottom section shows three metaverse platforms: 'Metaverse platform B', 'Metaverse platform A', and 'Metaverse platform C'. Platform B and A are connected by double-headed arrows labeled 'Content interoperability' and 'Asset interoperability'. Platform A and C are also connected by similar arrows, with a vertical 'BRIDGE' element between them. All three platforms are connected to a central 'Metaverse content discovery service provider' at the bottom. A small code 'H.770.1(25)' is in the bottom right corner.
+
+**Figure 7-1 – Concept of the metaverse content discovery service scenario**
+
+Nevertheless, it can become challenging for users to discover content that matches their interests in numerous dispersed and independent metaverses. In this case, it may be beneficial to have a dedicated metaverse content discovery service provider (MCDSP), which might be provided by third-party service providers to provide an enhanced user experience. An MCDSP can help users navigate the various platforms, find the content and services that meet their needs, and be a central hub to find information about different metaverse platforms and their content. This can include information about virtual real estate, gaming experiences, social networks, virtual events, virtual education and virtual tourist destinations. It is also possible to purchase the content on other platforms by jumping there, but this scenario gives more seamless experience to users since they do not need to know where the content is from.
+
+The MCDSP can also provide users with relevant information about the platforms, such as the types of experiences and activities available, the number of users and the quality of the user experience.
+
+### 7.1.2 Assumptions
+
+The assumptions related to this scenario include the following:
+
+- It is assumed that metaverse platforms A and B provide a standardized interface for searching and exchanging their content and metaverse platform C uses a metaverse bridge to interact with other metaverse platforms using its interface.
+- It is assumed that a user is connected to metaverse platform A.
+- It is assumed that users can create their mash-up content using multiple distributed content sources and publish it onto a specific metaverse platform.
+
+### 7.1.3 Service scenario
+
+This clause describes the typical service flow for metaverse content and service discovery service as shown in Figure 7-2.
+
+![Sequence diagram illustrating service flows for the metaverse content discovery scenario. The diagram shows interactions between a User, Metaverse platform A, Metaverse content discovery service provider (MCDSP), Metaverse platform B, and Metaverse platform C. The User sends a '1. Search' request to platform A. Platform A sends '1-1. Search contents' to the MCDSP. The MCDSP sends '1-2. Content information' to platform B and '1-1. Search contents' to platform C. Platform B sends '1-2. Content information' to platform C. Platform C sends '1-3. List of content information' back to the MCDSP. The MCDSP sends '2-1. Request content for preview' to platform A. Platform A sends '2-2. Restricted content for preview' to platform C. Platform C sends '3-2. Purchased content and receipt (proof of purchase)' back to the MCDSP. The MCDSP sends '3-1. Request purchase of the content' to platform A. Platform A sends '4. Create a mash-up content' to the User. The User sends '5. Publish' to platform A. Platform A sends '5. Publish the mash-up content' to the User.](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg)
+
+```
+
+sequenceDiagram
+    participant User
+    participant A as Metaverse platform A
+    participant MCDSP as Metaverse content discovery service provider
+    participant B as Metaverse platform B
+    participant C as Metaverse platform C
+
+    Note left of User: 1. Search
+    User->>A: 1. Search
+    A->>MCDSP: 1-1. Search contents
+    MCDSP->>B: 1-2. Content information
+    MCDSP->>C: 1-1. Search contents
+    B->>C: 1-2. Content information
+    C->>MCDSP: 1-3. List of content information
+    Note left of User: 2. Preview
+    User->>A: 2. Preview
+    A->>MCDSP: 2-1. Request content for preview
+    MCDSP->>C: 2-2. Restricted content for preview
+    Note left of User: 3. Purchase
+    User->>A: 3. Purchase
+    A->>MCDSP: 3-1. Request purchase of the content
+    MCDSP->>C: 3-2. Purchased content and receipt (proof of purchase)
+    Note left of User: 4. Mash-up
+    User->>A: 4. Mash-up
+    A->>User: 4. Create a mash-up content
+    Note left of User: 5. Publish
+    User->>A: 5. Publish
+    A->>User: 5. Publish the mash-up content
+  
+```
+
+H.770.1(25)
+
+Sequence diagram illustrating service flows for the metaverse content discovery scenario. The diagram shows interactions between a User, Metaverse platform A, Metaverse content discovery service provider (MCDSP), Metaverse platform B, and Metaverse platform C. The User sends a '1. Search' request to platform A. Platform A sends '1-1. Search contents' to the MCDSP. The MCDSP sends '1-2. Content information' to platform B and '1-1. Search contents' to platform C. Platform B sends '1-2. Content information' to platform C. Platform C sends '1-3. List of content information' back to the MCDSP. The MCDSP sends '2-1. Request content for preview' to platform A. Platform A sends '2-2. Restricted content for preview' to platform C. Platform C sends '3-2. Purchased content and receipt (proof of purchase)' back to the MCDSP. The MCDSP sends '3-1. Request purchase of the content' to platform A. Platform A sends '4. Create a mash-up content' to the User. The User sends '5. Publish' to platform A. Platform A sends '5. Publish the mash-up content' to the User.
+
+**Figure 7-2 – Service flows for the metaverse content discovery scenario**
+
+- 1 The user searches for metaverse content using the discovery service. Using the discovery service's intuitive, user-friendly interface, the user searches for specific content based on keywords, categories, or other criteria, including multimodal inputs from the user.
+  - The metaverse platform A sends the user's intention to the MCDSP to request content information through several distributed metaverse platforms.
+  - Each metaverse platform provides content information that matches the query request. It includes the metaverse platform address, hardware requirements, billing information, etc.
+  - The MCDSP gathers and provides the information to the metaverse platform A.
+- 2 The user requests to preview the content or experience before purchasing it and reads reviews from other users to help them make informed decisions. During the preview, users can try the content using their immersive devices.
+  - The metaverse platform A interacts with platform C to get content for preview.
+
+- The metaverse platform C provides content restricted to only preview to platform A.
+- 3 The user purchases a specific digital content from platform C.
+- When the user requests metaverse platform A to purchase the content of platform C, and the platform interacts with platform C to buy it on behalf of the user.
+  - The metaverse platform A interacts with platform C to purchase the content.
+  - The metaverse platform C provides content and its receipt to platform A, and platform A will assign ownership to the user.
+- 4 The user creates a mash-up content on metaverse platforms A.
+- 5 The user publishes and places the mash-up content into metaverse platform A. This user-generated metaverse content can also be searched through the discovery service and used for creating a new service by other users.
+
+## 7.2 Metaverse learning: Content exploration and learning across platforms
+
+A metaverse learning environment is a virtual school where users, including teachers and students, can connect remotely for learning.
+
+### 7.2.1 Description
+
+In the scenario of metaverse learning, a virtual school known as the metaverse school is created, enabling teachers and students to connect through avatars. This approach enables an immersive learning environment and facilitates interactive and collaborative experiences within a virtual classroom. Teachers have the flexibility to create instructional materials by accessing a diverse range of content available from numerous content servers within the metaverse. Similarly, students are not limited to solely using the materials provided by their teachers. They can also learn from relevant content from various content servers, enriching their learning experience.
+
+By creating a metaverse school in virtual space, students and teachers from around the world can seamlessly connect and learn together, regardless of the platform they use. Teachers have the advantage of accessing a wide array of content from various platforms, including 3D models, interactive visualizations, virtual libraries and more. Students, in turn, can access and explore diverse learning materials that cater to their unique learning styles and preferences, without any limitations posed by geography or physical boundaries. This opens up exciting opportunities for remote and distance learning, ensuring that everyone has equal access to quality learning and the ability to maximize their learning potential. Figure 7-3 shows the concept of metaverse learning over cross-platform.
+
+![Figure 7-3: Concept of metaverse learning over cross-platform. The diagram illustrates a cross-platform metaverse learning service architecture. At the top, a 'Cross-platform metaverse learning service' box contains three functional areas: 'Explore contents' (with icons for a hand and a clipboard), 'Purchase contents' (with icons for a wallet and a coin), and 'Submit certification of learning' (with icons for a person, a star, and a document). Below this, three metaverse entities are shown: 'Metaverse library', 'Metaverse school', and 'Metaverse museum'. The library and school are connected by a dashed double-headed arrow labeled 'Avatar migration', 'Content retrieval', and 'Content purchase'. The school and museum are connected by a dashed double-headed arrow labeled 'Avatar migration', 'Content use', and 'Content usage record'. These entities are hosted on three metaverse platforms: 'Metaverse platform B', 'Metaverse platform A', and 'Metaverse platform C'. Platform B hosts the library, Platform A hosts the school, and Platform C hosts the museum. Platforms B and A are connected by a dashed double-headed arrow labeled 'Avatar interoperability' and 'Content interoperability'. Platforms A and C are connected by a dashed double-headed arrow labeled 'Avatar interoperability' and 'Content interoperability'. Below the platforms, three users are shown: 'User A (Teacher)', 'User B (Students)', and 'User C (Students)'. User A is connected to Platform A, while Users B and C are connected to Platform A via a dashed line. At the bottom, a 'Certification service provider' is shown, connected to Platform A and Platform C via dashed lines. The text 'H.770.1(25)' is in the bottom right corner.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg)
+
+Figure 7-3: Concept of metaverse learning over cross-platform. The diagram illustrates a cross-platform metaverse learning service architecture. At the top, a 'Cross-platform metaverse learning service' box contains three functional areas: 'Explore contents' (with icons for a hand and a clipboard), 'Purchase contents' (with icons for a wallet and a coin), and 'Submit certification of learning' (with icons for a person, a star, and a document). Below this, three metaverse entities are shown: 'Metaverse library', 'Metaverse school', and 'Metaverse museum'. The library and school are connected by a dashed double-headed arrow labeled 'Avatar migration', 'Content retrieval', and 'Content purchase'. The school and museum are connected by a dashed double-headed arrow labeled 'Avatar migration', 'Content use', and 'Content usage record'. These entities are hosted on three metaverse platforms: 'Metaverse platform B', 'Metaverse platform A', and 'Metaverse platform C'. Platform B hosts the library, Platform A hosts the school, and Platform C hosts the museum. Platforms B and A are connected by a dashed double-headed arrow labeled 'Avatar interoperability' and 'Content interoperability'. Platforms A and C are connected by a dashed double-headed arrow labeled 'Avatar interoperability' and 'Content interoperability'. Below the platforms, three users are shown: 'User A (Teacher)', 'User B (Students)', and 'User C (Students)'. User A is connected to Platform A, while Users B and C are connected to Platform A via a dashed line. At the bottom, a 'Certification service provider' is shown, connected to Platform A and Platform C via dashed lines. The text 'H.770.1(25)' is in the bottom right corner.
+
+**Figure 7-3 – Concept of metaverse learning over cross-platform**
+
+### 7.2.2 Assumptions
+
+- It is assumed that the metaverse school, the metaverse library, and the metaverse museum exist on metaverse platforms, with each being provided on different metaverse platforms A, B, and C. It is assumed that user A is a teacher and user B and C are students in the metaverse school.
+- It is assumed that the metaverse library offers a variety of content, including learning materials and provides diverse search functionalities, such as topic, media type, running environment and required device type, to facilitate easy content discovery for users. This allows users to find content aligned with their interests or specific needs to create learning materials or engage in learning.
+- It is assumed that the metaverse museum, in addition to its unique functions as a museum, is responsible for providing supplementary content related to students' lessons in the learning area. It is assumed that there is a contractual agreement between the metaverse museum and the metaverse school, specifying designated lists of allowable users and content lists.
+- It is assumed that the metaverse museum manages the records of content utilization, including the list of contents accessed by users, timestamps of usage, learning outcomes, and provides certification marks by a certification service provider, which might be a third-party service provider, to users who have studied the content.
+
+### 7.2.3 Service scenario
+
+This clause describes the typical service flow for the metaverse learning service as shown in Figure 7-4.
+
+![Sequence diagram showing service flows for a metaverse learning scenario. Lifelines include Metaverse platform A (User A: Teacher, User B: Student B, User C: Student C, Metaverse school), Metaverse platform B (Metaverse library), Certification service provider, and Metaverse platform C (Metaverse museum). The sequence involves searching for materials, evaluating them, instructing students, requesting supplementary materials, studying at the museum, and submitting a learning certificate.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UserA as User A (Teacher)
+    participant UserB as User B (Student B)
+    participant UserC as User C (Student C)
+    participant School as Metaverse school
+    participant Library as Metaverse library
+    participant Museum as Metaverse museum
+    participant CSP as Certification service provider
+
+    Note left of UserA: [Avatar icons]
+
+    UserA->>School: 1-1. Search for class material
+    School-->>Library: 1-2. Move to search for contents
+    Library-->>School: 2-2. Return with contents and its usage rights
+    School-->>UserA: 2-1. Evaluate contents
+    UserA->>School: 3-1. Instruct students in a particular subject
+    School-->>UserB: 3-2. Engage in classes and utilize materials
+    School-->>UserC: 3-2. Engage in classes and utilize materials
+    UserA->>School: 4-1. Request supplementary learning materials
+    School-->>Museum: 4-2. Request to submit a certification for learning
+    Museum-->>UserB: 5-1. Move to metaverse museum
+    Museum-->>UserC: 5-1. Move to metaverse museum
+    UserB->>Museum: 5-3. Study additional content at the museum
+    UserC->>Museum: 5-3. Study additional content at the museum
+    Museum-->>CSP: 5-2. Authentication
+    UserB->>School: 6-1. Request to submit the learning certificate
+    UserC->>School: 6-1. Request to submit the learning certificate
+    CSP-->>Museum: 6-2. Certification
+    Museum-->>School: 7-1. Return with a certification
+    School-->>UserA: 7-2. Submit a content learning certification
+  
+```
+
+Sequence diagram showing service flows for a metaverse learning scenario. Lifelines include Metaverse platform A (User A: Teacher, User B: Student B, User C: Student C, Metaverse school), Metaverse platform B (Metaverse library), Certification service provider, and Metaverse platform C (Metaverse museum). The sequence involves searching for materials, evaluating them, instructing students, requesting supplementary materials, studying at the museum, and submitting a learning certificate.
+
+H.770.1(25)
+
+**Figure 7-4 – Service flows for metaverse learning service scenario**
+
+- 1 User A (teacher) enters the metaverse school as their avatar to prepare learning materials for the class. To find the contents required for lesson preparation, User A navigates to the metaverse library and performs searches using various keywords such as subject, media type, execution environment and device requirements.
+- 2 When the desired contents are found, user A checks if there are any issues accessing the contents using the devices utilized in the class. User A decides to purchase the contents to make them available for all users of the metaverse school. The purchased contents and content usage rights are transferred from the metaverse library to the metaverse school. User A completes the lesson materials by combining the contents available at the metaverse school with the contents obtained from the metaverse library.
+- 3 User A, user B and user C participate in virtual classes by entering the metaverse school with their avatars. User B and user C (students) engage in the shared use of content prepared by user A.
+- 4 After the class is over, user A requests user B and user C to learn supplementary contents available at the metaverse museum in order to enhance their understanding of the lesson, and then submit a learning certification.
+- 5 User B and user C enter the metaverse museum with their avatars from the metaverse school. At the museum, their status as authorized users and their access to specific contents are verified. If granted permission, user B and user C can engage in learning the relevant content available at the metaverse museum.
+- 6 The metaverse museum generates and manages records of content utilization, including lists of contents used, usage history and user learning outcomes. The museum also provides user B and user C with learning certification for the contents they have studied. These
+
+certifications may include information such as the user who completed the learning, the contents studied, and the learning outcomes.
+
+7 User B and user C return to the metaverse school with their content learning certification and submit them to user A.
+
+## 7.3 Metaverse exhibitions: Cross-platform metaverse exhibitions
+
+A cross-platform metaverse exhibition provides immersive knowledge that spans multiple metaverse platforms, offering visitors an immersive and enlightening journey. Leveraging advanced technologies, including augmented reality (AR) and virtual reality (VR), attendees can traverse a range of exhibits, interactive installations, and curated digital content. This innovative approach presents a novel way for individuals to immerse themselves in various thematic showcases, irrespective of their physical location.
+
+### 7.3.1 Description
+
+This service scenario outlines a cross-platform metaverse exhibition that harnesses the capabilities of immersive technologies such as AR, VR, haptic sensation, temperature, humidity and scent to deliver an unparalleled viewing experience. Spanning multiple metaverse platforms, the exhibition offers visitors the chance to delve into various digital art pieces, installations, and curated showcases.
+
+Through interactive engagements, attendees can immerse themselves in the stories behind the artworks, interact with dynamic installations and even witness the evolution of pieces in real-time. The seamless integration across platforms ensures that visitors can transition from one platform to another without missing a beat in their viewing experience.
+
+The cross-platform metaverse exhibition breaks geographical boundaries, allowing art enthusiasts from all corners of the globe to experience and interpret a diverse range of artworks, irrespective of their physical location. It transcends the traditional art viewing norms, offering an immersive, interactive, and expansive experience. The convergence of immersive technologies in this space accentuates the depth, making it a revolutionary approach to art exhibitions in the digital age. Figure 7-5 shows the concept of cross-platform metaverse exhibitions.
+
+![Diagram illustrating the concept of cross-platform metaverse exhibitions. It shows a layered architecture: Service layer (Viewing, Taking photos, Purchasing, Discussing), Gallery layer (Painting, Photo, Media art galleries), Platform layer (Platforms A, B, C), and User layer (Users A, B, C). Arrows indicate migration and interoperability between components.](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg)
+
+```
+
+graph TD
+    subgraph Service [Cross-platform metaverse exhibition service]
+        S1[Viewing artworks]
+        S2[Taking photos]
+        S3[Purchasing artworks]
+        S4[Discussing artworks]
+    end
+
+    subgraph Galleries
+        G1[Metaverse painting gallery]
+        G2[Metaverse photo gallery]
+        G3[Metaverse media art gallery]
+    end
+
+    subgraph Platforms
+        P1[Metaverse platform A]
+        P2[Metaverse platform B]
+        P3[Metaverse platform C]
+    end
+
+    subgraph Users
+        U1[User A]
+        U2[User B]
+        U3[User C]
+    end
+
+    G1 <-- Avatar migration --> G2
+    G2 <-- Media art migration / Asset migration --> G3
+
+    P1 <-- Avatar interoperability --> P2
+    P2 <-- Content interoperability / Asset interoperability --> P3
+
+    G1 --- P1
+    G2 --- P2
+    G3 --- P3
+
+    P1 --- U1
+    P2 --- U2
+    P3 --- U3
+  
+```
+
+Diagram illustrating the concept of cross-platform metaverse exhibitions. It shows a layered architecture: Service layer (Viewing, Taking photos, Purchasing, Discussing), Gallery layer (Painting, Photo, Media art galleries), Platform layer (Platforms A, B, C), and User layer (Users A, B, C). Arrows indicate migration and interoperability between components.
+
+**Figure 7-5 – Concept of cross-platform metaverse exhibitions**
+
+### 7.3.2 Assumptions
+
+The assumptions related to this service scenario include the following:
+
+- It is assumed that there are three metaverse exhibitions on metaverse platforms A, B, and C, respectively: a metaverse painting gallery, a metaverse photo gallery and a metaverse media art gallery hosted.
+- It is assumed that the metaverse exhibitions have partnerships with different metaverse platform providers to support cross-platform metaverse exhibition service.
+- It is assumed that the metaverse exhibition has access to advanced technologies such as AR and VR to provide an immersive and interactive experience for visitors.
+- It is assumed that visitors have access to the necessary technology and equipment to access the metaverse exhibitions on different platforms.
+
+### 7.3.3 Service scenario
+
+This clause describes the typical service flow for the service scenario of cross-platform metaverse exhibition service as shown in Figure 7-6.
+
+![Sequence diagram showing service flows for cross-platform metaverse exhibitions across three platforms: A, B, and C.](3da1a07cb87051bf616c9876db958cf0_img.jpg)
+
+The diagram illustrates the service flow for a cross-platform metaverse exhibition. It features three vertical lifelines for Metaverse platform A, Metaverse platform B, and Metaverse platform C. On platform A, User A interacts with the Metaverse painting gallery through steps 1-1 (Viewing artworks) and 1-2 (Taking photos). A dashed line labeled 'User-Avatar interaction' connects User A to an avatar. From the painting gallery, a request (2-1) is sent to platform B's Metaverse photo gallery, which responds (2-2). The user then transitions to platform B, interacting with its avatar. On platform B, the user participates in step 3 (Discussing artworks). A return message (4) goes back to platform A. The user then transitions to platform C, interacting with its avatar. On platform C, the user participates in step 5 (Request access and Access granted) with the Metaverse media art gallery, followed by step 6 (Purchasing a photo). A final return message (7) goes back to platform B. Dashed lines labeled 'User-Avatar interaction' connect the user to avatars on platforms B and C. The diagram is labeled H.770.1(25) at the bottom right.
+
+Sequence diagram showing service flows for cross-platform metaverse exhibitions across three platforms: A, B, and C.
+
+**Figure 7-6 – Service flows for the cross-platform metaverse exhibitions**
+
+Visitors may start by exploring platform A, where they can immerse themselves in a virtual gallery showcasing various paintings. They can then seamlessly transition to platform B, where they can appreciate a photo exhibition detailing the themes and stories behind each captured moment. Finally, on platform C, visitors can engage with media art exhibits, using AR technology to interact and experience art in a whole new dimension.
+
+- 1 User A, B, and C access the metaverse platform A, B, and C, respectively, and visit their respective galleries.
+- 2 User A in the metaverse painting gallery can have a closer look at any artwork using their AR/VR devices.
+- 3 User A can take virtual photos with paintings and seamlessly move to the metaverse photo gallery on metaverse platform B.
+- 4 User A can access the activated photos and learn about the background of each photo through an audio description.
+- 5 User A returns to the metaverse painting gallery on metaverse platform A.
+- 6 User C on the metaverse media art gallery can manipulate and interact with virtual elements of the art using AR tools.
+- 7 User C can seamlessly move to the metaverse photo gallery on metaverse platform B, purchase a photograph, and then return to the metaverse media art gallery on platform C to continue their exploration.
+
+## 7.4 Metaverse safety patrol: Safety patrol service
+
+Safety issues in virtual worlds are not a new phenomenon and users of the metaverse have expressed concerns about safety issues. To protect user safety, metaverse platforms can operate organizations or services such as safety patrol to protect users. Safety patrol can monitor threats in the metaverse, support victims, and punish perpetrators to make the metaverse world a safer place.
+
+### 7.4.1 Description
+
+In virtual reality games, there have been instances of harassment, physical assault, bullying, hate speech, and more. As the metaverse provides users with an increased sensory experience, bad behaviour within the metaverse can be even more serious than current online harassment. Problematic behaviours in virtual reality generally occur in real-time and are difficult to track as they are not typically recorded. Therefore, a safety patrol is necessary to prevent immediate user harm and online harassment. However, it may be difficult for every metaverse to operate its own independent safety patrol. Therefore, a separate provider of metaverse patrol as a service can take on this role, and each metaverse platform can ensure safety through an agreement with this service provider. In this scenario, when the metaverse platform receives a request for help from an online user, it accompanies the user with a safety patrol to monitor the situation nearby and immediately warn users who engage in problematic behaviour. This can be especially useful for protecting children in the metaverse environment. This patrol ensures it can be distinguished from regular users through consistent uniforms or marks. In addition, it warns users who engage in problematic behaviour in advance or reports them to the metaverse platform administrator for future reference. The metaverse platform administrator will impose sanctions on the user based on the report and record it in the reputation management system of the platform to ensure accountability. It is feasible to either employ a safety patrol service as a third-party service or integrate a safety patrol system directly within the metaverse platform. The utilization of the safety patrol service facilitates rapid adoption of new functionalities. Alternatively, constructing the safety patrol system internally within the platform enables the provision of features specifically tailored to that particular environment. However, in either case, it is important to secure mechanisms for interoperability and information sharing to ensure a safe metaverse environment.
+
+Figure 7-7 shows the concept of a safety patrol service over metaverses.
+
+![Figure 7-7: Concept of a safety patrol service over metaverses. The diagram illustrates a three-tier architecture. The top tier is the 'Cross-platform metaverse safety patrol service' containing seven functions: Protect, Patrol, Warn, Report, Reputation, Ban, and Administration, each with a corresponding icon. Below this is the 'Metaverse' layer, consisting of two 'Metaverse' boxes connected by a dashed double-headed arrow labeled 'Avatar interoperability', 'Reputation query', and 'Access control'. The bottom tier includes 'Metaverse platform A' and 'Metaverse platform B'. Platform A contains a 'User reputation management system' and is connected to a 'Safety patrol service provider', an 'AI service provider', and an 'Avatar service provider'. Platform B is connected to a 'User reputation service provider'. A dashed double-headed arrow between platforms A and B is labeled 'Avatar interoperability' and 'Identity interoperability'. A vertical dashed double-headed arrow on the left connects the 'Safety patrol service provider' to the 'Metaverse' layer, labeled 'Safety patrol dispatch'. The text 'H.770.1(25)' is in the bottom right corner.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg)
+
+Figure 7-7: Concept of a safety patrol service over metaverses. The diagram illustrates a three-tier architecture. The top tier is the 'Cross-platform metaverse safety patrol service' containing seven functions: Protect, Patrol, Warn, Report, Reputation, Ban, and Administration, each with a corresponding icon. Below this is the 'Metaverse' layer, consisting of two 'Metaverse' boxes connected by a dashed double-headed arrow labeled 'Avatar interoperability', 'Reputation query', and 'Access control'. The bottom tier includes 'Metaverse platform A' and 'Metaverse platform B'. Platform A contains a 'User reputation management system' and is connected to a 'Safety patrol service provider', an 'AI service provider', and an 'Avatar service provider'. Platform B is connected to a 'User reputation service provider'. A dashed double-headed arrow between platforms A and B is labeled 'Avatar interoperability' and 'Identity interoperability'. A vertical dashed double-headed arrow on the left connects the 'Safety patrol service provider' to the 'Metaverse' layer, labeled 'Safety patrol dispatch'. The text 'H.770.1(25)' is in the bottom right corner.
+
+**Figure 7-7 – Concept of a safety patrol service over metaverses**
+
+As shown in this figure, the patrol is visible and operated through a combination of the AI service provider, avatar service provider, and safety patrol service provider.
+
+### 7.4.2 Assumptions
+
+The assumptions related to this service scenario include the following:
+
+- It is assumed that metaverse platform A has entered into an agreement with a metaverse patrol as a service provider.
+- It is assumed that metaverse platform A has shared its platform's rules and policies with the patrol service provider in advance.
+- It is assumed that metaverse platform A has granted the patrol's avatar the necessary level of authority within the platform.
+- It is assumed that the patrol operates as an AI patrol avatar through collaboration with an avatar service provider and an AI service provider.
+
+### 7.4.3 Service scenario
+
+This clause describes the typical service flow for the metaverse safety patrol service as shown in Figure 7-8.
+
+![Sequence diagram illustrating service flows for a safety patrol service over metaverses. Lifelines include Metaverse of platform A (User A, User B, Admin), Safety patrol service provider, Reputation service provider, and Metaverse of platform B (Admin, User A). The process involves requesting protection, dispatching a patrol, warning and reporting, recording, jumping to another platform, querying reputation, and rejecting access.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UserA_A as User A
+    participant UserB_A as User B
+    participant Admin_A as Admin
+    participant SPSP as Safety patrol service provider
+    participant RSP as Reputation service provider
+    participant Admin_B as Admin
+    participant UserA_B as User A
+
+    Note right of RSP: Reputation service provider
+
+    UserA_A->>Admin_A: 1. Request protection
+    Admin_A->>SPSP: 2. Request patrol
+    SPSP->>UserA_A: 3. Dispatch patrol
+    Note left of UserA_A: Patrol
+    UserA_A->>UserB_A: 4. Warn
+    UserA_A->>Admin_A: 5. Report
+    Admin_A->>Admin_A: 6. Record
+    Admin_A-->>RSP: 
+    UserA_A->>Admin_B: 7. User A jumps to metaverse of platform B
+    UserB_A->>Admin_B: 7. User B jumps to metaverse of platform B
+    Admin_B->>SPSP: 8. Query reputation of user B
+    SPSP-->>RSP: 
+    SPSP->>Admin_B: 9. Reject access of user B
+  
+```
+
+H.770.1(25)
+
+Sequence diagram illustrating service flows for a safety patrol service over metaverses. Lifelines include Metaverse of platform A (User A, User B, Admin), Safety patrol service provider, Reputation service provider, and Metaverse of platform B (Admin, User A). The process involves requesting protection, dispatching a patrol, warning and reporting, recording, jumping to another platform, querying reputation, and rejecting access.
+
+**Figure 7-8 – Service flows for a safety patrol service over metaverses**
+
+- 1 When user A experiences harassment or problematic behaviour, the user requests patrol services through the metaverse platform A.
+- 2 When a request for help is received, the platform requests patrol services from a provider to have a safety patrol accompany the user and monitor the situation.
+  - The patrol prevents problematic situations by being distinguished from regular users through consistent uniforms or marks. Alternatively, an item indicating that the user avatar is protected by the patrol and only revealing the patrol's avatar, when necessary, may be attached to avoid rendering performance issues due to additional avatars.
+  - The patrol uses artificial intelligence provided by an AI service provider to determine if other users' real-time conversations and actions are problematic.
+- 3 The safety patrol monitors users exhibiting potential problematic behaviour and immediately issues warnings if necessary.
+  - The platform requests an AI service provider to make judgments based on the rules and policies of the metaverse platform and user behavioural data.
+  - If necessary, appropriate sanctions can be immediately enforced according to the permissions granted by the platform.
+- 4 Patrols create reports on detected issues and send them to the metaverse platform administrators.
+- 5 The administrator reviews the reports and decides on sanctions for the problematic user, user B.
+- 6 If sanctions are imposed, the reputation management system for that user is updated, and additional measures are reviewed and implemented to prevent recurrence.
+  - User B, subject to sanctions, may be blocked from accessing the metaverse.
+
+- It is also possible to record the sanction record into other systems, such as a reputation service provider, depending on the platform's policy.
+- 7 User A jumps to metaverse platform B and user B follows.
+- 8 The administrator checks the reputation of users A and B.
+- Depending on the situation, other metaverse platforms having an agreement may share reputation information.
+  - This can be done automatically without the intervention of the administrator.
+- 9 The platform rejects the access of user B according to the result of the reputation review.
+
+## 7.5 Metaverse SNS: Social networking services in the metaverse
+
+This service scenario is about social networking services in the metaverse. Users can display content such as NFT assets and user-created content in their personal metaverse social space, and visitors can access and interact with the user's content. Additionally, users can delegate their avatars to artificial intelligence to greet visitors. It is also possible to upload users' photos, video clips and postings within the metaverse social space. Compared to existing SNS services composed of text, images, and videos, metaverse social space can provide an immersive service through interactive 3D content. Traditional SNS provides relatively basic interaction in a 2D environment through sharing text, images, videos, commenting, and liking, primarily delivering information via timelines or feeds. On the other hand, the metaverse offers real-time interaction and a high level of immersion in a 3D or VR environment through avatars, allowing users to have more lifelike experiences in virtual spaces where physical location and exploration are emphasized.
+
+### 7.5.1 Description
+
+The metaverse can be a new area of social networking, where users can interact with each other and digital objects in real time in several virtual worlds over different metaverse platforms. Metaverse social networking service (SNS) provides users with the ability to organize NFT assets, upload personal photos and videos, record daily activities, post photos and text, and communicate with friends through comments and various activities across different platforms. Users can customize the appearance of their avatars, including clothing, accessories and animations, and interact with others in virtual environments, games, and events. Metaverse SNS platforms enable the transfer of avatars and accessories between platforms. Users can expand their social network and participate in various communities and events by promoting interoperability and collaboration between platforms.
+
+Figure 7-9 shows a concept of the metaverse SNS scenario.
+
+![Figure 7-9: Concept of the metaverse social networking service scenario. The diagram shows a 'Cross-platform metaverse spatial social networking service' box containing four service categories: Social posting, Spatial decoration, Immersive social networking, and AI butler. Below this are three 'Metaverse social space' boxes. At the bottom are three 'Metaverse platform' boxes (A, B, C) with user avatars. Arrows show interactions between platforms and social spaces, and between social spaces themselves.](7133ccf78043568ca62ecbcd43628a4a_img.jpg)
+
+The diagram illustrates the concept of a cross-platform metaverse spatial social networking service. At the top, a large box titled "Cross-platform metaverse spatial social networking service" contains four sub-boxes: "Social posting" (with camera, film, and document icons), "Spatial decoration" (with interior design icons), "Immersive social networking" (with people interacting icons), and "AI butler" (with a butler icon). Below this service box are three "Metaverse social space" boxes. At the bottom are three "Metaverse platform" boxes labeled A, B, and C, each with a user avatar. Arrows indicate the following interactions:
+
+- Between Metaverse platform A and Metaverse social space: "Identity interoperability" and "Content interoperability".
+- Between Metaverse platform B and Metaverse social space: "Identity interoperability", "Content interoperability", and "Avatar interoperability".
+- Between Metaverse platform C and Metaverse social space: "Identity interoperability", "Content interoperability", and "Avatar interoperability".
+- Between Metaverse social space (left) and Metaverse social space (middle): "Sharing photos, videos, posts", "Social networking", and "Spatial decoration".
+- Between Metaverse social space (middle) and Metaverse social space (right): "Avatar migration", "Asset migration", "Access control", and "Spatial interaction".
+
+The diagram is labeled H.770.1(25) in the bottom right corner.
+
+Figure 7-9: Concept of the metaverse social networking service scenario. The diagram shows a 'Cross-platform metaverse spatial social networking service' box containing four service categories: Social posting, Spatial decoration, Immersive social networking, and AI butler. Below this are three 'Metaverse social space' boxes. At the bottom are three 'Metaverse platform' boxes (A, B, C) with user avatars. Arrows show interactions between platforms and social spaces, and between social spaces themselves.
+
+**Figure 7-9 – Concept of the metaverse social networking service scenario**
+
+In the concept, a metaverse social space resides on top of metaverse platforms. That is, a metaverse platform can hold multiple metaverses and those platforms can interact with each other directly or via a metaverse bridge. It is also possible to interact with NFT/blockchain service providers, AI service provider, avatar service provider, etc. In this scenario, a user's avatar can either be affiliated with the metaverse platform or a separate avatar service provider.
+
+### 7.5.2 Assumptions
+
+The assumptions related to this service scenario include the following:
+
+- It is assumed that the user's SNS space in the metaverse is called the "metaverse social space".
+- It is assumed that users A, B, and C each own a metaverse social space and, being in a mutual friendship, can freely visit each other's spaces. User C is assumed to have connected artificial intelligence to the avatar to cater to visitors on their behalf.
+
+### 7.5.3 Service scenario
+
+This clause describes the typical service flow for the metaverse social networking service as shown in Figure 7-10.
+
+![Sequence diagram illustrating service flows for a metaverse social networking service across four lifelines: Metaverse of platform A, Metaverse of platform B, Metaverse of platform C, and AI service provider. The diagram shows interactions between User A, User B, User C, and AI avatars. Key steps include: 1. User A decorates their social space; 2. Postsharing from User A to User B; 3-4. Request and grant access from User B to User A; 5. User A interacts with User B's content; 6-1-2. Request and grant access from User A to User C; 7. Notification from User C to User A; 8. User A interacts with User C's AI avatar; 9. Return to home from User A; 10. AI delegation from User A to User C's AI avatar. Dashed lines represent User-Avatar and AI-Avatar interactions.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg)
+
+H.770.1(25)
+
+Sequence diagram illustrating service flows for a metaverse social networking service across four lifelines: Metaverse of platform A, Metaverse of platform B, Metaverse of platform C, and AI service provider. The diagram shows interactions between User A, User B, User C, and AI avatars. Key steps include: 1. User A decorates their social space; 2. Postsharing from User A to User B; 3-4. Request and grant access from User B to User A; 5. User A interacts with User B's content; 6-1-2. Request and grant access from User A to User C; 7. Notification from User C to User A; 8. User A interacts with User C's AI avatar; 9. Return to home from User A; 10. AI delegation from User A to User C's AI avatar. Dashed lines represent User-Avatar and AI-Avatar interactions.
+
+**Figure 7-10 – Service flows for the metaverse social networking service**
+
+- 1 Users create their own metaverse social spaces using the tools provided by each metaverse platform. In this step, users can do the following:
+- Place their digital assets, items, photos, posts, videos, party rooms and playable games that they have purchased as NFTs in their metaverse social space.
+  - Invite friends to their space and make content accessible to other users even when the user is not online.
+  - Grant differentiated access rights to their spaces and content.
+  - Set content display and access conditions when decorating their spaces.
+  - Create multiple metaverse social spaces and specify them as public or private. For private spaces, access can be limited to invited users for a certain period of time.
+  - Place their avatars in their metaverse spaces. These avatars can mimic the user's appearance and behaviours or be set to a different appearance as desired. When the user is offline, an AI-powered avatar greets visiting friends. The avatar only provides information the user has allowed and engages in conversations that align with the user's intentions.
+  - Place portals linked to their friends' metaverse spaces on their own metaverse social space. The connection of these portals is only possible if it is allowed by the bilateral agreement between the user and the friend. These portals only allow movement for
+
+people who are friends with the user, and users who are not friends can only see information that the portal owner has allowed. It is also possible to send friend requests to other users connected to them through portals placed in visited metaverse social spaces.
+
+- 2 User B uploads a post for sharing to the friends and the platform B sends notifications to the friends in other platforms. In this case, this notification will be sent only once to prevent massive respective notification if there are lots of friends in other platforms.
+  - For the posting of a static content, this notification can include a uniform resource locator (URL) or API for the post that is accessible through the interactions among platforms and it may include texts, thumbnails, snapshot, short video clips, etc.
+  - For the posting of an invitation, this notification can include invitations on a specific event, and this can be realized as a portal, or special links available during pertained period.
+- 3 User A sends a request to move to user B's metaverse platform through a portal. The user retains the avatar, identity, and accessories they were using and can either maintain their avatar as it is or change it to fit the other platform.
+  - User can use their avatar as it is without any modification if each platform supports it;
+  - The appearance of the avatar may be altered during the compliance checks to follow the rule or policy of the target metaverse platform;
+  - Items not allowed are disabled if it does not fit the target platform.
+- 4 The metaverse platform checks the user's identity to confirm whether the user has permission to access the metaverse space.
+- 5 User A shares their experience of the content in the metaverse space and engages in conversation or enjoys content such as movies and games together with User B in their metaverse social space using their avatar. Multiple users can participate online at the same time.
+  - Users collaboratively create content and issue NFTs on the metaverse space with other users;
+  - Users exchange their items with each other and the avatars can bring the items to their metaverse social space when they return.
+- 6 User A moves to user C's metaverse social space through user B's portal. User information and avatar model files are received from user A's metaverse platform since that information is maintained in the metaverse platform A.
+- 7 When user A's entry is permitted, notifications such as email, messenger, phone, or text messages may be sent to the user.
+- 8 User C's AI-powered avatar communicates with user A in natural language to leave a message for their friend or request their friend's content. In addition, users can communicate with friends through their avatars. Various contact methods such as mobile phones, voice over Internet protocol (VoIP), email, and messenger can be used.
+- 9 User A returns to their metaverse social networking service (SNS) space.
+- 10 When logging out of metaverse SNS space, user A delegates its avatar to an AI by requesting to the AI service provider.
+  - The user can indicate their preferences regarding whether the avatar can contact the owner or what information can be provided to visiting friends.
+  - Users can check messages or notifications left by visitors to their personal space later when they log in again.
+
+## 7.6 Metaverse shopping: Cross-platform metaverse shopping
+
+In a cross-platform metaverse shopping, users can seamlessly buy, sell and trade digital assets and/or content across platforms. This interconnected ecosystem allows for broader opportunities and increased versatility in virtual transactions.
+
+### 7.6.1 Description
+
+Metaverse platforms offer users access to virtual worlds and economies where they can participate in various activities and acquire digital assets such as virtual currencies, real estate in virtual worlds, and other virtual goods. However, due to the decentralized and fragmented nature of these platforms, some digital assets may be exclusively available on specific platforms.
+
+In such cases, cross-platform metaverse shopping can enable users to buy or sell virtual items or invest in exclusive properties that are not available on their current platform. For example, a user who plays a game on one metaverse platform may find a rare virtual item or exclusive virtual property that is only available on another platform. Without the ability to transfer digital assets, the user would not be able to acquire these items or invest in the property.
+
+By enabling trading and transferring of digital assets between metaverse platforms, users can seamlessly buy, sell, and trade digital assets across platforms. This functionality allows users to diversify their digital asset portfolios, take advantage of exclusive opportunities and maximize the potential value of their digital assets. Additionally, cross-platform metaverse shopping services that support multiple metaverse platforms can facilitate these transactions, making it easier for users to trade and transfer their digital assets across various platforms. Figure 7-11 shows the concept of cross-platform metaverse shopping.
+
+![Figure 7-11: Concept of cross-platform metaverse shopping. The diagram illustrates a cross-platform metaverse shopping service. At the top, a box labeled 'Cross-platform metaverse shopping service' contains three sub-functions: 'Searching items' (with a magnifying glass icon), 'Purchasing items' (with a shopping cart icon), and 'Transferring items' (with a circular arrow icon). Below this service box, 'Metaverse A' and 'Metaverse shop' are shown. A dashed double-headed arrow between them is labeled 'Item purchase', 'Avatar migration', and 'Asset migration'. Below 'Metaverse A' is 'Metaverse platform A', which is connected to 'User A'. Below 'Metaverse shop' is 'Metaverse platform B'. A solid double-headed arrow between 'Metaverse platform A' and 'Metaverse platform B' is labeled 'Avatar interoperability', 'Content interoperability', and 'Asset interoperability'. The label 'H.770.1(25)' is in the bottom right corner.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg)
+
+The diagram illustrates the concept of cross-platform metaverse shopping. At the top, a box labeled "Cross-platform metaverse shopping service" contains three sub-functions: "Searching items" (with a magnifying glass icon), "Purchasing items" (with a shopping cart icon), and "Transferring items" (with a circular arrow icon). Below this service box, "Metaverse A" and "Metaverse shop" are shown. A dashed double-headed arrow between them is labeled "Item purchase", "Avatar migration", and "Asset migration". Below "Metaverse A" is "Metaverse platform A", which is connected to "User A". Below "Metaverse shop" is "Metaverse platform B". A solid double-headed arrow between "Metaverse platform A" and "Metaverse platform B" is labeled "Avatar interoperability", "Content interoperability", and "Asset interoperability". The label "H.770.1(25)" is in the bottom right corner.
+
+Figure 7-11: Concept of cross-platform metaverse shopping. The diagram illustrates a cross-platform metaverse shopping service. At the top, a box labeled 'Cross-platform metaverse shopping service' contains three sub-functions: 'Searching items' (with a magnifying glass icon), 'Purchasing items' (with a shopping cart icon), and 'Transferring items' (with a circular arrow icon). Below this service box, 'Metaverse A' and 'Metaverse shop' are shown. A dashed double-headed arrow between them is labeled 'Item purchase', 'Avatar migration', and 'Asset migration'. Below 'Metaverse A' is 'Metaverse platform A', which is connected to 'User A'. Below 'Metaverse shop' is 'Metaverse platform B'. A solid double-headed arrow between 'Metaverse platform A' and 'Metaverse platform B' is labeled 'Avatar interoperability', 'Content interoperability', and 'Asset interoperability'. The label 'H.770.1(25)' is in the bottom right corner.
+
+Figure 7-11 – Concept of cross-platform metaverse shopping
+
+### 7.6.2 Assumptions
+
+The assumptions related to this service scenario include the following:
+
+- It is assumed that the user has an account on the metaverse shopping.
+- It is assumed that the metaverse shop possesses digital items which the user wants to buy.
+
+### 7.6.3 Service scenario
+
+This clause describes the typical service flow for the service scenario of the cross-platform metaverse shopping service, as shown in Figure 7-12.
+
+![Figure 7-12: Service flows for cross-platform metaverse shopping. The diagram shows a sequence of interactions between User A, Metaverse A, and Metaverse shop on Metaverse platform B. 1. User A searches for an item in Metaverse A. 2-1. User A requests access to the Metaverse shop. 2-2. Access is granted. 3. User A purchases an item in the Metaverse shop. 4. User A returns to Metaverse A with the purchased item. Dashed lines with avatars indicate user-avatar interactions throughout the process. A label H.770.1(25) is in the bottom right corner.](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg)
+
+Figure 7-12: Service flows for cross-platform metaverse shopping. The diagram shows a sequence of interactions between User A, Metaverse A, and Metaverse shop on Metaverse platform B. 1. User A searches for an item in Metaverse A. 2-1. User A requests access to the Metaverse shop. 2-2. Access is granted. 3. User A purchases an item in the Metaverse shop. 4. User A returns to Metaverse A with the purchased item. Dashed lines with avatars indicate user-avatar interactions throughout the process. A label H.770.1(25) is in the bottom right corner.
+
+**Figure 7-12 – Service flows for cross-platform metaverse shopping**
+
+User A searches for a digital item that he or she wants to purchase and finds it in the metaverse shop.
+
+- 1 User A can seamlessly move from metaverse A on the metaverse platform A to the metaverse shop on the metaverse platform B.
+- 2 User A purchases the digital item they searched for.
+- 3 The cross-platform metaverse shopping service validates the transfer of the purchased item and transfers it from the metaverse shopping to metaverse A.
+- 4 User A returns to metaverse A.
+
+## 7.7 Metaverse tourism: Seamless exploration across multiple platforms
+
+The metaverse tourism service allows users (tourists) to select a customized tourism package that takes them through different metaverse platforms. With seamless transitions between platforms, users can explore a variety of attractions and environments, ranging from natural landscapes to virtual concerts and cultural experiences. Additionally, the service provides an opportunity for social interaction with friends and other users, allowing for shared experiences across the metaverse.
+
+### 7.7.1 Description
+
+User A and user B decide to take a metaverse tourism trip together and select a metaverse tourism package that they both like. This metaverse tourism package includes not only the metaverse palace tourism offered by metaverse platform A, but also the metaverse city and metaverse concert tourisms offered by metaverse platform B.
+
+While on a metaverse tourism trip, user A and user B discover a metaverse gift shop on metaverse platform A. To commemorate the trip, they decide to purchase a hat souvenir that they can wear on their avatars while traveling. They can attach the hat souvenir to their avatars while traveling and keep it attached to their avatars as they move between metaverse platforms.
+
+While exploring the virtual world on metaverse platform A, user A and user B see that a metaverse concert that is part of their metaverse tourism package is being offered on metaverse platform B, so they move to metaverse platform B. The metaverse concert is offered on metaverse platform B and
+
+user A and user B decide to attend. Their avatars move from metaverse platform A to metaverse platform B without any registration or signup.
+
+User A and user B attend and enjoy the concert on metaverse platform B, and then user A returns to metaverse platform A to continue the metaverse palace tourism where user A left off. Figure 7-13 shows the concept of cross-platform metaverse tourism.
+
+![Figure 7-13: Concept of the cross-platform metaverse tourism. The diagram illustrates a service flow involving two metaverse platforms, A and B, and an asset service provider. At the top, a 'Cross-platform metaverse tourism package service' is shown, containing three main activities: 'Browse and select metaverse palace' (with icons for a target, hand, and camera), 'Purchase and attach hat souvenir' (with icons for a person and a hat), and 'Attend concert and return' (with icons for a stage and a house). Below this, a flow shows 'Metaverse gift shop' connected to 'Metaverse palace', which is connected via a dashed double-headed arrow labeled 'Avatar migration', 'Asset purchase', and 'Asset migration' to 'Metaverse city hall', which is connected to 'Metaverse concert hall'. Below the package service, 'Metaverse platform A' is connected to 'User A' and 'Metaverse platform B' is connected to 'User B'. A dashed double-headed arrow labeled 'Avatar interoperability' and 'Asset interoperability' connects the two platforms. At the bottom, an 'Asset service provider' is connected to both platforms via dashed lines. The reference code H.770.1(25) is in the bottom right corner.](fa01531ea2c45beeb4036005da3037a4_img.jpg)
+
+Figure 7-13: Concept of the cross-platform metaverse tourism. The diagram illustrates a service flow involving two metaverse platforms, A and B, and an asset service provider. At the top, a 'Cross-platform metaverse tourism package service' is shown, containing three main activities: 'Browse and select metaverse palace' (with icons for a target, hand, and camera), 'Purchase and attach hat souvenir' (with icons for a person and a hat), and 'Attend concert and return' (with icons for a stage and a house). Below this, a flow shows 'Metaverse gift shop' connected to 'Metaverse palace', which is connected via a dashed double-headed arrow labeled 'Avatar migration', 'Asset purchase', and 'Asset migration' to 'Metaverse city hall', which is connected to 'Metaverse concert hall'. Below the package service, 'Metaverse platform A' is connected to 'User A' and 'Metaverse platform B' is connected to 'User B'. A dashed double-headed arrow labeled 'Avatar interoperability' and 'Asset interoperability' connects the two platforms. At the bottom, an 'Asset service provider' is connected to both platforms via dashed lines. The reference code H.770.1(25) is in the bottom right corner.
+
+**Figure 7-13 – Concept of the cross-platform metaverse tourism**
+
+### 7.7.2 Assumptions
+
+The assumptions related to this scenario include the following:
+
+- It is assumed that tourists have the necessary equipment and devices to access various metaverse platforms.
+- It is assumed that there is an established partnership or integration between metaverse platform A and metaverse platform B to ensure seamless transitions between the two platforms.
+- It is assumed that their avatars can seamlessly move from metaverse platform A to metaverse platform B without additional registration or sign-up.
+- It is assumed that their avatars can seamlessly move from metaverse platform A to metaverse platform B without additional registration or sign-up.
+- It is assumed that the platform has implemented appropriate security measures to ensure the safety and privacy of users during the tourism, including measures to prevent unauthorized access to personal information and digital assets.
+
+### 7.7.3 Service scenario
+
+This clause describes the typical service flow for metaverse tourism service, as shown in Figure 7-14.
+
+![Sequence diagram showing service flows for a metaverse tourism scenario between two platforms, Metaverse platform A and Metaverse platform B, with an Asset service provider. The diagram illustrates the interaction between User A and User B as they explore different virtual locations and purchase assets.](c494cd874a082a97b50b3c4d3938f467_img.jpg)
+
+The diagram illustrates the service flows for a metaverse tourism scenario involving two metaverse platforms, Metaverse platform A and Metaverse platform B, and an Asset service provider. The sequence of interactions is as follows:
+
+- 1. Selects a package:** Both User A and User B select a metaverse tourism package.
+- 2-1. Explore metaverse palace:** User A explores the metaverse palace on platform A. User B explores the metaverse palace on platform B.
+- 2-2. Move to platform A:** User B moves from the metaverse palace on platform B to the metaverse palace on platform A.
+- 3-1. Purchase a hat souvenir for avatar:** Both users purchase a hat souvenir for their avatars from the metaverse gift shop on platform A.
+- 3-2. Purchase an asset for a hat souvenir:** Both users purchase an asset for their hat souvenirs from the Asset service provider.
+- 4-1. Attend the metaverse concert:** Both users attend the metaverse concert on platform B.
+- 4-2. Move to platform B:** User A moves from the metaverse palace on platform A to the metaverse concert hall on platform B.
+- 5-1. Continue to explore the metaverse palace:** User A continues to explore the metaverse palace on platform A.
+- 5-2. Returns to platform A:** User B returns from the metaverse concert hall on platform B to the metaverse city hall on platform B.
+- 5-3. Continue to explore metaverse city hall:** User B continues to explore the metaverse city hall on platform B.
+
+H.770.1(25)
+
+Sequence diagram showing service flows for a metaverse tourism scenario between two platforms, Metaverse platform A and Metaverse platform B, with an Asset service provider. The diagram illustrates the interaction between User A and User B as they explore different virtual locations and purchase assets.
+
+**Figure 7-14 – Service flows for the metaverse tourism service scenario**
+
+- 1 User A and user B browse a metaverse tourism package that they both like. The selected metaverse tourism package includes tourisms offered by platform A and platform B.
+- 2 To use the metaverse palace tourism together, user A accesses metaverse palace on metaverse platform A, user B accesses metaverse city tourism on metaverse platform B and then moves to metaverse palace tourism on metaverse platform A.
+- 3 While on the metaverse palace on platform A, user A and user B notice a metaverse gift shop and decide to purchase a souvenir to attach to their avatars during the tourism. The two users purchase a hat as a souvenir provided by asset service provider, which might be a third-party service provider. They can wear it on their avatars as they travel from platform to platform.
+- 4 While exploring the metaverse palace on metaverse platform A, user A and user B see that a metaverse concert that is part of their metaverse tourism package is being offered on metaverse platform B, so they move to metaverse platform B. The metaverse concert is offered on metaverse platform B, and they decide to attend. Their avatars move from metaverse platform A to metaverse platform B without any registration or signup. User A and user B enjoy the metaverse concert on metaverse platform B.
+- 5 User A returns to metaverse platform A to continue the metaverse palace tourism and User B resumes the metaverse city tourism.
+
+## 7.8 Metaverse signage: Product promotion with seamless transitions cross-platforms
+
+Digital signage [b-ITU-T H.780] refers to any type of communication that provides information or guidance to users. In the metaverse, signage can be used for various purposes, such as wayfinding, displaying information, promoting events, and branding in a virtual space:
+
+- Wayfinding: In large virtual worlds, signage can be used to help users navigate and find their way around. This could include directional signs, maps, or landmarks that help users orient themselves within the space;
+- Informational displays: Signage can also be used to display information to users in the metaverse. For example, a museum might use signage to provide information about exhibits or historical artifacts;
+- Event promotion: Signage can be used to promote events or activities within the metaverse. For example, a virtual concert might use signage to advertise the time and location of the event, as well as provide information about the performers;
+- Branding: Just like in the physical world, signage can be used to promote brands and products in the metaverse. This could include billboards, product displays, or even virtual storefronts.
+
+### 7.8.1 Description
+
+Metaverse street signage is virtual signage that displays wayfinding information for different metaverse services located along the metaverse street. In this case, in addition to its primary purpose of providing directions in the virtual space, the metaverse signage provides a link to the metaverse product store, which provides more information about the advertised product.
+
+The metaverse product store is a metaverse dedicated to that brand, built to promote and sell products and can include a virtual storefront or product showcase where users can interact with products in a more immersive way. By creating a service dedicated to a specific brand on one metaverse platform, rather than multiple different metaverse platforms, businesses can effectively showcase their brand and products in the most effective way. User A can access the different metaverses on the platform through signage on metaverse street that provides wayfinding information within the virtual environment. Metaverse signage is accessible on metaverse platform A. A user is browsing the virtual space and comes across a link to a metaverse promoting a specific product. The user decides to enter the metaverse to learn more. When the user clicks the link, the user is redirected to a metaverse product store that provides a virtual store or product showcase. This metaverse is powered by metaverse platform B, a dedicated platform for promoting featured products. This allows avatars to move between different metaverse platforms while maintaining their appearance, identity, and functionality. Instead of having to create a new avatar on each platform the user utilizes, users can create a single avatar that can be used in multiple virtual worlds. Using the same avatar across different platforms not only helps users maintain continuity and identity, but also reduces the time and effort required to create a new avatar for each platform. After exploring the product, the user chooses to return to the metaverse platform A. Signage service providers, as third-party providers, may also provide the way to promote their products and services across multiple metaverse platforms. However, this is not considered in this service scenario. Figure 7-15 shows the concept of cross-platform metaverse signage.
+
+![Figure 7-15: Concept of the metaverse signage service scenario. The diagram illustrates a service flow involving two metaverse platforms, A and B, connected by avatar interoperability. Platform A is connected to User A (Customer) and Platform B to User B (Sales person AI). A 'Cross-platform metaverse signage service' box contains three main actions: 'Navigate and redirect' (with icons for a compass and hand), 'Inspect a product and purchase' (with icons for a magnifying glass, hand, and document), and 'Return to home and received a product' (with icons for a house and parachute). Below this, 'Metaverse signage street' and 'Metaverse product store' are shown with an 'Avatar migration' arrow between them. At the bottom, three service providers (Signage, Payment, and Delivery) are connected via a dashed line to the platforms.](08dce7ad4c512fdf0c0cde60415fade6_img.jpg)
+
+The diagram illustrates the concept of the metaverse signage service scenario. At the top, a large box labeled "Cross-platform metaverse signage service" contains three sub-sections: "Navigate and redirect" (with icons of a compass and a hand), "Inspect a product and purchase" (with icons of a magnifying glass, a hand, and a document), and "Return to home and received a product" (with icons of a house and a parachute). Below this box, two boxes labeled "Metaverse signage street" and "Metaverse product store" are connected by a dashed double-headed arrow labeled "Avatar migration". Below these, two grey boxes labeled "Metaverse platform A" and "Metaverse platform B" are connected by a solid double-headed arrow labeled "Avatar interoperability". "Metaverse platform A" is connected to "User A (Customer)" on the left, and "Metaverse platform B" is connected to "User B (Sales person AI)" on the right. At the bottom, a dashed line connects three boxes: "Signage service provider", "Payment service provider", and "Delivery service provider", which are in turn connected to the metaverse platforms.
+
+Figure 7-15: Concept of the metaverse signage service scenario. The diagram illustrates a service flow involving two metaverse platforms, A and B, connected by avatar interoperability. Platform A is connected to User A (Customer) and Platform B to User B (Sales person AI). A 'Cross-platform metaverse signage service' box contains three main actions: 'Navigate and redirect' (with icons for a compass and hand), 'Inspect a product and purchase' (with icons for a magnifying glass, hand, and document), and 'Return to home and received a product' (with icons for a house and parachute). Below this, 'Metaverse signage street' and 'Metaverse product store' are shown with an 'Avatar migration' arrow between them. At the bottom, three service providers (Signage, Payment, and Delivery) are connected via a dashed line to the platforms.
+
+**Figure 7-15 – Concept of the metaverse signage service scenario**
+
+### 7.8.2 Assumptions
+
+The assumptions related to this scenario include the following:
+
+- It is assumed that the metaverse platform A allows users to navigate the virtual environment and interact with the signage. Signage service provider might be a third-party service provider.
+- It is assumed that metaverse product store of the metaverse platform B is specifically designed to promote branded products through virtual stores or product showcases.
+- It is assumed that the metaverse platform B allows avatars to move from metaverse platform A while preserving their appearance, identity, and functionality.
+
+### 7.8.3 Service scenario
+
+This clause describes the typical service flow for metaverse signage service, as shown in Figure 7-16.
+
+![Sequence diagram illustrating service flows for the metaverse signage service scenario. Lifelines include User A, Metaverse platform A (Metaverse signage street), Payment service provider, Delivery service provider, Metaverse platform B (Metaverse product store), and Sales person AI. The sequence shows navigation, product selection, payment, and delivery across platforms.](7ae836e598020d937ed1478c2ef13025_img.jpg)
+
+```
+
+sequenceDiagram
+    participant User A
+    participant Metaverse platform A as Metaverse platform A  
+Metaverse signage street
+    participant Payment service provider
+    participant Delivery service provider
+    participant Metaverse platform B as Metaverse platform B  
+Metaverse product store
+    participant Sales person AI
+
+    Note left of User A: User A
+    User A->>Metaverse platform A: 1. Navigate and access signage
+    Metaverse platform A-->>User A: 2. Clicks on product link
+    Note right of Metaverse platform A: Avatar
+    Metaverse platform A->>Metaverse platform B: 3. Redirects to metaverse product store
+    Note right of Metaverse platform B: Avatar
+    User A->>Metaverse platform B: 4. Inspects the products
+    User A->>Sales person AI: 5. Communicate with sales person AI about the product
+    Sales person AI-->>User A: 5-1. Responds customer
+    User A->>Metaverse platform B: 6-1. Selects product and proceeds to checkout
+    User A->>Payment service provider: 6-2. Provides payment information and confirms purchase
+    Payment service provider->>Delivery service provider: 
+    Delivery service provider->>Metaverse platform B: 7. Delivers the purchased product
+    Note right of Metaverse platform B: Avatar
+    Metaverse platform B-->>Metaverse platform A: 8. Return to metaverse service platform A and continue exploring
+    Note right of Metaverse platform A: Avatar
+    Metaverse platform A->>User A: 9. Receives the purchased product
+  
+```
+
+Sequence diagram illustrating service flows for the metaverse signage service scenario. Lifelines include User A, Metaverse platform A (Metaverse signage street), Payment service provider, Delivery service provider, Metaverse platform B (Metaverse product store), and Sales person AI. The sequence shows navigation, product selection, payment, and delivery across platforms.
+
+H.770.1(25)
+
+**Figure 7-16 – Service flows for the metaverse signage service scenario**
+
+- 1 User A navigates various metaverses available in the metaverse signage street of metaverse platform A.
+- 2 After navigating the virtual space, user A discovers a link of the metaverse signage that provides detailed information about a specific product. To learn more about this, user A decides to click on the link.
+- 3 The link clicked by user A redirects to a metaverse product store designed for promoting a specific product. This metaverse product store is hosted on metaverse platform B and serves as a virtual store or product showcase. It offers users detailed information about the product and allows them to thoroughly examine and even purchase the product. Cross-platform interoperability makes it easy for users on metaverse platform A to utilize the product marketing metaverse built on metaverse platform B.
+- 4 User A enters the metaverse product store of metaverse platform B. Utilizing virtual reality (VR) technology, user A can examine the product in a more immersive manner.
+- 5 User A can also engage in additional queries and responses about the product with the sales person AI.
+- 6 User A selects the desired product, proceeds with the payment, inputs payment information, and confirms the purchase to the payment service provider, which might be a third-party service provider.
+- 7 The metaverse product store sends a purchase confirmation message to the user A, finalizing the purchase and providing an estimated delivery date. The product will be shipped to the user's address.
+- 8 User A chooses to return to the metaverse signage street of metaverse platform A. User A can continue using the virtual space of metaverse platform A.
+
+9 User A later receives the purchased product at the metaverse product store from delivery service provider, which might be a third-party service provider.
+
+## 7.9 Metaverse co-working: Cross-platform metaverse co-working
+
+Metaverse co-working is a virtual co-working service that allows users to collaborate and communicate remotely in a more immersive way. Users can access the virtual offices for co-working through the metaverse platform.
+
+### 7.9.1 Description
+
+Metaverse co-working entails leveraging metaverse technology to provide virtual co-working services, thereby offering an online work environment while maintaining the offline work environment and eliminating spatial limitations. In other words, it is beyond the typical online work environment of remote work and creates a virtual co-working environment. Users can access the metaverse co-working offices through the metaverse platform and animate their avatars to walk into a co-working office, work in a conference room, give a presentation, and so on. This makes it possible for people to co-work from anywhere, anytime, even if they are in different physical spaces, through the medium of the metaverse.
+
+Figure 7-17 shows the concept of cross-platform metaverse co-working service.
+
+![Diagram illustrating the concept of cross-platform metaverse co-working service. It shows a hierarchy from Users at the bottom, through Metaverse Platforms, to Metaverse Offices, and finally the Co-working Services (Inviting, Meetings, Presentations) at the top. Interoperability and migration paths are shown between the two platform/office stacks.](a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg)
+
+```
+
+    graph TD
+      subgraph Service [Cross-platform metaverse co-working service]
+        IV[Inviting and visiting]
+        M[Meetings]
+        P[Presentations]
+      end
+
+      OfficeA[Metaverse office A] <--> |Avatar migration  
+Meeting material migration| OfficeB[Metaverse office B]
+      PlatformA[Metaverse platform A] <--> |Avatar interoperability  
+Content interoperability| PlatformB[Metaverse platform B]
+
+      UserA[User A] --> PlatformA
+      PlatformA --> OfficeA
+      OfficeA --> Service
+
+      UserB[User B] --> PlatformB
+      PlatformB --> OfficeB
+      OfficeB --> Service
+  
+```
+
+The diagram illustrates the concept of cross-platform metaverse co-working service. At the top, a large box labeled 'Cross-platform metaverse co-working service' contains three sub-sections: 'Inviting and visiting' (with icons of a door and a welcome sign), 'Meetings' (with icons of a group of people and a video conference), and 'Presentations' (with icons of a presentation screen and a group of people). Below this, two boxes labeled 'Metaverse office A' and 'Metaverse office B' are connected by a dashed double-headed arrow labeled 'Avatar migration' and 'Meeting material migration'. Below these offices, two boxes labeled 'Metaverse platform A' and 'Metaverse platform B' are connected by a solid double-headed arrow labeled 'Avatar interoperability' and 'Content interoperability'. At the bottom, 'User A' is connected to 'Metaverse platform A' and 'User B' is connected to 'Metaverse platform B'. The reference code 'H.770.1(25)' is in the bottom right corner.
+
+Diagram illustrating the concept of cross-platform metaverse co-working service. It shows a hierarchy from Users at the bottom, through Metaverse Platforms, to Metaverse Offices, and finally the Co-working Services (Inviting, Meetings, Presentations) at the top. Interoperability and migration paths are shown between the two platform/office stacks.
+
+**Figure 7-17 – Concept of cross-platform metaverse co-working service**
+
+The metaverse co-working service enables real-time collaboration by providing a variety of features and collaboration tools, including voice and text chat, video conferencing, file sharing, and presentation sharing. Meeting material migration provides secure ways of exchanging meeting materials such as files and presentations. Users can also communicate and interact with others through avatars, navigate different spaces, and create a personalized work environment.
+
+An advantageous feature of metaverse co-working is its compatibility across multiple metaverse platforms, ensuring that users can collaborate and communicate with team members and clients, irrespective of the platforms they utilize. This interoperability enhances connectivity and streamlines workflows, promoting efficient and effective remote work dynamics.
+
+### **7.9.2 Assumptions**
+
+The assumptions related to this service scenario include the following:
+
+- It is assumed that user A and B access the metaverse office A and B on the metaverse platform A and B, respectively.
+- It is assumed that there is an invite or join feature between the metaverse office A and B, user B visits to the metaverse office A and joins a meeting in the metaverse office A.
+
+### 7.9.3 Service scenario
+
+This clause describes the typical service flow for the scenario of the metaverse co-working service as shown in Figure 7-18.
+
+![Sequence diagram illustrating the service flows for cross-platform metaverse co-working service between Metaverse platform A and Metaverse platform B.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg)
+
+The diagram illustrates the interaction between two metaverse platforms, A and B, and their respective users and offices. The sequence of events is as follows:
+
+- 1. Send invitation:** User A in Metaverse office A sends an invitation to User B in Metaverse office B.
+- 2. Send invitation message:** Metaverse office A sends the invitation message to Metaverse office B.
+- 3. Accept invitation:** User B in Metaverse office B accepts the invitation.
+- 4-1. Request access:** User B sends a request to access Metaverse office A.
+- 4-2. Access granted:** Metaverse office A grants access to User B.
+- 5. Migrate with presentation file:** User B migrates to Metaverse office A with the presentation file.
+- 6. Meeting and presentations:** User A and User B have a real-time interactive meeting and presentation in Metaverse office A.
+- 7. Return to home with meeting minutes:** User B returns to Metaverse office B with the meeting minutes file.
+
+The diagram also shows *User-Avatar interaction* for both User A and User B, represented by dashed lines between the users and their avatars. The reference code H.770.1(25) is shown in the bottom right corner.
+
+Sequence diagram illustrating the service flows for cross-platform metaverse co-working service between Metaverse platform A and Metaverse platform B.
+
+**Figure 7-18 – Service flows for cross-platform metaverse co-working service**
+
+User A and B work in the metaverse office A and B, respectively and User A wants to invite User B to the metaverse office A for a meeting.
+
+- 1 User A sends user B an invitation to attend a meeting in the metaverse office A and asks to give a presentation. The invitation may include the meeting schedule, location, and a link to share the presentation file.
+- 2 User B accepts the invitation from user A, and moves to the metaverse office A on metaverse platform A. User B takes the presentation file with them.
+- 3 User A and B have a real-time interactive meeting in the metaverse office A. They use their avatars to communicate through voice and gestures, and share their presentations on a virtual screen. User B starts giving a presentation. User A and the other participants can watch user B's presentation in real time, ask questions, and discuss it.
+- 4 During the meeting, user A and B can leverage the features of metaverse office to perform additional collaborative tasks. For example, they can share and edit documents simultaneously, or use a whiteboard to share and organize ideas.
+- 5 After the meeting, user B returns to the metaverse office B with the meeting minutes file.
+
+# 8 High-level requirements for metaverse cross-platform interoperability
+
+The following clauses describe general requirements and high-level requirements for metaverse cross-platform interoperability in the four aspects: avatar, asset, content, and identity.
+
+## 8.1 General requirements for metaverse cross-platform interoperability
+
+This clause lists general requirements for cross-platform interoperability, as shown in Table 8-1.
+
+**Table 8-1 – General requirements for cross-platform interoperability**
+
+| Req.ID    | Requirements                                                                                                                              |
+|-----------|-------------------------------------------------------------------------------------------------------------------------------------------|
+| GENHR-001 | It is recommended that a metaverse platform is interoperable with other metaverse platforms.                                              |
+| GENHR-002 | It is recommended to ensure interoperability between metaverses on heterogeneous platforms.                                               |
+| GENHR-003 | It is recommended to ensure a secure and trusted environment for exchanging information between metaverse platforms.                      |
+| GENHR-004 | It is recommended to ensure performance of cross-platform interactions to satisfy natural conversation with users in different platforms. |
+
+## 8.2 High-level requirements for avatar interoperability
+
+Avatar interoperability enables that an avatar of a metaverse platform can visit other metaverses in another metaverse platform by using the same or similar avatar with the original characteristics. This clause lists high-level requirements regarding avatar interoperability, as shown in Table 8-2.
+
+**Table 8-2 – High-level requirements for avatar interoperability**
+
+| Req.ID    | Requirements                                                                                                                             |
+|-----------|------------------------------------------------------------------------------------------------------------------------------------------|
+| AVIHR-001 | It is recommended to enable avatars to migrate across different metaverse platforms while retaining their original characteristics.      |
+| AVIHR-002 | It is required that each metaverse platform exchange the constraints during the migration procedures for compliance and performance.     |
+| AVIHR-003 | It is recommended to synchronize attributes of avatar after experiencing by roaming avatar across metaverse platforms.                   |
+| AVIHR-004 | It is recommended to ensure avatar's consistent representation across metaverse platforms.                                               |
+| AVIHR-005 | It is required that avatar-related data be accessible across the metaverse platforms.                                                    |
+| AVIHR-006 | It is recommended that visited avatars to follow the constraints of the destination platform while retaining their core characteristics. |
+
+## 8.3 High-level requirements for asset interoperability
+
+This clause lists the high-level requirements essential for achieving digital asset interoperability across multiple metaverse platforms, as shown in Table 8-3.
+
+**Table 8-3 – High-level requirements for asset interoperability**
+
+| Req.ID    | Requirements                                                                                                              |
+|-----------|---------------------------------------------------------------------------------------------------------------------------|
+| ASIHR-101 | It is recommended to ensure a secure and trusted environment for transforming digital assets between metaverse platforms. |
+
+**Table 8-3 – High-level requirements for asset interoperability**
+
+| <b>Req.ID</b> | <b>Requirements</b>                                                                                                                |
+|---------------|------------------------------------------------------------------------------------------------------------------------------------|
+| ASIHR-102     | It is recommended to facilitate the seamless exchange, recognition and use of digital assets across different metaverse platforms. |
+| ASIHR-103     | It is recommended to enable certain identification of digital asset ownership and associated rights across platforms.              |
+
+## **8.4 High-level requirements for content interoperability**
+
+This clause lists the high-level requirements essential for achieving content interoperability across multiple metaverse platforms, as shown in Table 8-4.
+
+**Table 8-4 – High-level requirements for content interoperability**
+
+| <b>Req.ID</b> | <b>Requirements</b>                                                                                                                                          |
+|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| COIHR-101     | It is required that content data, including information for management, searchability and interoperability, be able to transfer between metaverse platforms. |
+| COIHR-102     | It is required to ensure content portability and format compatibility when moving or sharing content across metaverse platforms.                             |
+| COIHR-103     | It is recommended to facilitate secure sharing of user content across metaverse platforms.                                                                   |
+| COIHR-104     | It is required to maintain the integrity and authenticity of content during transfers between platforms.                                                     |
+
+## **8.5 High-level requirements for identity interoperability**
+
+This clause lists the high-level requirements essential for achieving identity interoperability across multiple metaverse platforms, as shown in Table 8-5.
+
+**Table 8-5 – High-level requirements for identity interoperability**
+
+| <b>Req.ID</b> | <b>Requirements</b>                                                                                                                               |
+|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
+| IDIHR-101     | It is recommended to use the same identity of digital entity in the home platform when digital entity moves to other metaverse platforms.         |
+| IDIHR-102     | It is required to follow the identity usage policy of the visiting metaverse platform when the digital entity moves to other metaverse platforms. |
+| IDIHR-103     | It is recommended to support a variety of authentication methods for identity from visited metaverse platforms.                                   |
+| IDIHR-104     | It is recommended to support users in viewing and managing all identities of their digital entity when it moves to other metaverse platforms.     |
+| IDIHR-105     | It is recommended to support users in viewing and managing all avatars associated with their unique identities across the metaverse platforms.    |
+
+# Appendix I
+
+## Use cases of the interoperability between metaverses with digital twins
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### I.1 Smart sustainable mobility
+
+#### I.1.1 Description
+
+Many cities are implementing metaverses with digital twins to facilitate urban planning, environmental management, traffic control, energy management and various other digital transformations by using Internet of things (IoT) to collect and monitor urban data to support decision making and optimization through simulation. The digital twin interoperability functional component (DTIFC) orchestrates the metaverses with digital twins of smart environment, smart driving, and smart transportation to develop a variety of applications that promote environment-friendly mobility.
+
+Figure I.1 provides an overview of metaverse interoperability in the smart sustainable mobility use case.
+
+![Figure I.1: Overview of metaverse interoperability in the smart sustainable mobility use case. The diagram shows a central 'City mobility metaverse' box at the top containing three sub-components: 'Environmental hotspot prediction', 'Eco-driving assistance', and 'Traffic congestion reduction route guide'. Below this, a central vertical arrow labeled 'DTIFC' (Digital Twin Interoperability Functional Component) points down to three separate metaverse boxes at the bottom: 'Smart environment metaverse' (green), 'Smart driving metaverse' (blue), and 'Smart traffic metaverse' (orange). Each of these three metaverses has a list of functions: 'Smart environment metaverse' includes 'Environmental monitoring' and 'Emission control'; 'Smart driving metaverse' includes 'Driving navigation' and 'Participatory sensing'; 'Smart traffic metaverse' includes 'Traffic monitoring' and 'Traffic control'. Arrows also connect the central 'DTIFC' arrow to each of these three metaverses. Small thumbnail images are shown above each metaverse box. A reference code 'H.770.1(25)' is in the bottom right corner.](9f862801bce82634d3b5a1e0a195a799_img.jpg)
+
+H.770.1(25)
+
+Figure I.1: Overview of metaverse interoperability in the smart sustainable mobility use case. The diagram shows a central 'City mobility metaverse' box at the top containing three sub-components: 'Environmental hotspot prediction', 'Eco-driving assistance', and 'Traffic congestion reduction route guide'. Below this, a central vertical arrow labeled 'DTIFC' (Digital Twin Interoperability Functional Component) points down to three separate metaverse boxes at the bottom: 'Smart environment metaverse' (green), 'Smart driving metaverse' (blue), and 'Smart traffic metaverse' (orange). Each of these three metaverses has a list of functions: 'Smart environment metaverse' includes 'Environmental monitoring' and 'Emission control'; 'Smart driving metaverse' includes 'Driving navigation' and 'Participatory sensing'; 'Smart traffic metaverse' includes 'Traffic monitoring' and 'Traffic control'. Arrows also connect the central 'DTIFC' arrow to each of these three metaverses. Small thumbnail images are shown above each metaverse box. A reference code 'H.770.1(25)' is in the bottom right corner.
+
+Figure I.1 – Overview of metaverse interoperability in the smart sustainable mobility use case
+
+#### I.1.2 Assumptions
+
+This use case assumes the following metaverses with digital twins:
+
+- (a) Smart environment metaverse (SEMV)
+  - An environmental monitoring service provider monitors air pollution by collecting observation data from observation stations located at various locations, and if air pollution is expected to worsen, it seeks to improve the environment by restricting emissions at major sources.
+  - In the SEMV's digital twin, the observation network entity aggregates the observation data from the observation station entities. The air pollution prediction entity predicts air pollution by area based on the aggregated observation data. The emission simulation entity creates emission restriction plans for each source based on the air pollution prediction results.
+- (b) Smart driving metaverse (SDMV)
+
+- A carrier or mobility-as-a-service (MaaS) provider monitors the driving conditions and driving environment of individual cars using in-vehicle sensors while guiding driving operations and travel routes according to the conditions, thereby supporting safe and comfortable driving.
+- The SDMV's digital twin consists of a car entity, environmental and driving sensor entities, and driving assistance device entities that guide driving operations and routes. The driving risk prediction entity predicts driving risks using data from the sensor entities. The driving simulation entity proposes driving operations and routes to avoid risks based on the results of driving risk prediction and instructs the driving assistance device entities.
+
+##### (c) Smart transportation metaverse (STMV)
+
+- An intelligent transportation system (ITS) operator uses closed-circuit television (CCTV) cameras and sensors installed around roads to monitor traffic flow and predict the occurrence of congestion. It also develops plans to control traffic flow to reduce congestion.
+- The STMV's digital twin consists of the road network entity that makes up the road entities and the vehicle entities recognized on each road. The traffic congestion prediction entity predicts traffic congestion based on the condition of vehicles on the road. The traffic simulation entity creates a traffic flow plan based on the results of the congestion prediction.
+
+##### (d) City mobility metaverse (CMMV)
+
+- Government staff monitor and simulate urban environments and activities through the city mobility metaverse, which reproduces real urban spaces in virtual space.
+- In the CMMV's digital twin, various applications are developed that realize the smart sustainable mobility by orchestrating the domain-specific metaverses through the digital twin interoperability functional component (DTIFC).
+
+#### I.1.3 Scenario and operational flows
+
+##### I.1.3.1 Environmental hotspot prediction
+
+Environment bureau staff enable detailed environmental monitoring and emission restrictions through environmental hotspot prediction, which predicts the environmental quality of high-traffic areas with a high degree of accuracy using environmental sensors attached to the vehicles in addition to fixed observation stations. For environmental hotspot prediction (see Figure I.2), not only the observation stations of the SEMV's digital twin but also the environmental sensor attached to the car of the SDMV's digital twin is considered as a mobile observation station and incorporated into the observation network to perform air pollution prediction.
+
+- (1) Sensor data in the SDMV's digital twin containing privacy information, such as car trajectories, cannot be accessed externally. Therefore, the DTIFC conducts federated learning between SEMV and SDMV, where the SEMV transfers the air pollution prediction entity to SDMV, SDMV updates it using the locally collected sensor data, and SEMV aggregates the updated entity to refine the original entity.
+- (2) The DTIFC translates the location information and environmental sensor data of the SDMV's digital twin to the observation data of the SEMV's observation station entity during the step (1). This will allow the sensor data collected by the SDMV to be input into the air pollution prediction entity of the SEMV.
+- (3) The CMMV subscribes to the emission restriction plan that is created and published by the emission simulation entity in the SEMV's digital twin through the DTIFC.
+
+![Sequence diagram showing the operational flow for environmental hotspot prediction between City mobility metaverse (CMMV), Smart environment metaverse (SEMV), and Smart driving metaverse (SDMV).](9a5927586a691c4908aa2cf98bd47ebb_img.jpg)
+
+The diagram illustrates the interaction between three metaverses: City mobility metaverse (CMMV), Smart environment metaverse (SEMV), and Smart driving metaverse (SDMV). Each metaverse contains a DTIFC (Digital Twin Interface for Federation and Cooperation).
+
+The sequence of operations is as follows:
+
+- 1) Refine entity:** The SDMV's DTIFC sends a "Transfer air pollution prediction entity" message to the SEMV's DTIFC. The SEMV's DTIFC then performs internal operations labeled "Translate data" and "Update entity" before sending an "Aggregate air pollution prediction entity" message back to the SDMV's DTIFC.
+- 2) Translate data / Update entity:** These are internal operations within the SDMV's DTIFC, occurring after receiving the aggregate entity from the SEMV.
+- 3) Subscribe/Publish emission restriction plan:** The CMMV's DTIFC sends a "Subscribe emission restriction plan" message to the SEMV's DTIFC. The SEMV's DTIFC responds with a "Publish emission restriction plan" message to the CMMV's DTIFC.
+
+The diagram is labeled H.770.1(25) in the bottom right corner.
+
+Sequence diagram showing the operational flow for environmental hotspot prediction between City mobility metaverse (CMMV), Smart environment metaverse (SEMV), and Smart driving metaverse (SDMV).
+
+**Figure I.2 – Operational flow for environmental hotspot prediction**
+
+##### I.1.3.2 Eco-driving assistance
+
+Environment bureau staff determines emission restriction plans to recommend environment-friendly driving operations to drivers in areas with poor environmental quality for improving the city's overall environment quality through eco-driving (see Figure I.3). In the eco-driving assistance, based on the emission restriction plan from the emission simulation of the SEMV's digital twin, emission restriction information is also distributed to cars driving in air pollution areas. In response, the SDMV's digital twin performs a driving simulation with the emission restriction added to the car's environmental data and instructs the driving assistance device entities to perform driving operations to control emissions. Furthermore, when combined with the environmental hotspot prediction, which enhances the air pollution prediction of the SEMV's digital twin using environmental data from cars, more detailed emission simulation becomes possible, and the effectiveness of eco-driving assistance based on emission restriction plans can be enhanced.
+
+- (1) As with the environmental hotspot prediction, the DTIFC handles federation between the SEMV and SDMV to conduct federated learning of the air pollution prediction entity of the SEMV with using the sensor data of the SDMV.
+- (2) As with the environmental hotspot prediction, the DTIFC transforms data from the SDMV to the SEMV to input the sensor data collected by the car entity of SDMV into the air pollution prediction entity of SEMV during the step (1).
+- (3) The CMMV subscribes to the emission restriction plan that is created and published by the emission simulation entity of SEMV. The CMMV determines the emission restriction for cars driving in the area of interest from the emission restriction plan and publishes it to the SDMV that subscribes to it.
+
+![Sequence diagram showing the operational flow for eco-driving support between City mobility metaverse, Smart environment metaverse, and Smart driving metaverse. The diagram includes steps for air pollution prediction and emission restriction planning. Reference labels H.770.1(25) and F.751.28(25) are present.](0b7849dae424b0dd33e6386d2384643a_img.jpg)
+
+```
+
+sequenceDiagram
+    participant CMMV as City mobility metaverse (DTIFC)
+    participant SEMV as Smart environment metaverse (DTIFC)
+    participant SDMV as Smart driving metaverse (DTIFC)
+
+    Note left of CMMV: Determine targets
+    CMMV->>SDMV: Subscribe emission restriction plan
+    CMMV->>SDMV: Subscribe emission restriction
+    SDMV-->>CMMV: Publish emission restriction plan
+    SDMV-->>CMMV: Publish emission restriction
+
+    Note right of SDMV: 2) Translate data, Update entity
+    SDMV->>SEM: Transfer air pollution prediction entity
+    SEM-->>SDMV: Aggregate air pollution prediction entity
+    Note left of SEM: 1) Refine entity
+
+    Note right of SDMV: H.770.1(25), F.751.28(25)
+  
+```
+
+Sequence diagram showing the operational flow for eco-driving support between City mobility metaverse, Smart environment metaverse, and Smart driving metaverse. The diagram includes steps for air pollution prediction and emission restriction planning. Reference labels H.770.1(25) and F.751.28(25) are present.
+
+**Figure I.3 – Operational flow for eco-driving support**
+
+##### I.1.3.3 Traffic congestion reduction route guidance
+
+Transportation bureau staff can prevent serious traffic congestion by recommending routes and congestion pricing that disperse traffic flow so that vehicles are not concentrated on specific roads. For congestion reduction route guidance (see Figure I.4), the application synchronizes a vehicle on a road in the STMV's digital twin with the car entity in the SDMV's digital twin in order to send the recommended route to the vehicle near the congestion reduction route. In addition, based on the traffic flow plan created by the traffic simulation of the STMV's digital twin, the recommended route and congestion pricing information is sent to the SDMV traveling on the road targeted for congestion reduction. Upon receiving this information, the SDMV uses the driving simulation entity to search for a route and directs the route to the driving assistance device entities.
+
+- (1) The DTIFC synchronizes the vehicle entity recognized by the road entity in the STMV and the car entity in the SDMV. Since vehicles on the road change from time to time, the vehicle license plate number recognized by the road entity and the license plate number of the car entity should be identical for synchronization.
+- (2) The CMMV subscribes to the traffic flow plan that is created and published by the traffic simulation entity of the STMV through the DTIFC. The CMMV determines from the traffic flow plan the recommended route for the vehicle on the target road, and then publishes it to the subscribing SDMV through the DTIFC. In doing so, the DTIFC identifies the SDMV of the car that has been synchronized with the target vehicle as the receiver.
+
+![Sequence diagram showing the operational flow for traffic congestion reduction route guidance between three metaverses: City mobility metaverse, Smart transportation metaverse, and Smart driving metaverse. Each metaverse contains a DTIFC component. The flow is divided into two parts: 1) Smart transportation metaverse sends 'Map thing to entity' to Smart driving metaverse, which returns 'Return entity'. 2) City mobility metaverse sends 'Subscribe traffic flow plan' to Smart transportation metaverse, which responds with 'Subscribe recommended route'. Then, an external 'Determine targets' step occurs, followed by 'Publish traffic flow plan' and 'Publish recommended route' from City mobility metaverse to Smart driving metaverse. The diagram is labeled H.770.1(25).](798679874d1c29f8343506a156c79d7e_img.jpg)
+
+```
+
+sequenceDiagram
+    participant CM as City mobility metaverse (DTIFC)
+    participant STM as Smart transportation metaverse (DTIFC)
+    participant SD as Smart driving metaverse (DTIFC)
+
+    Note left of CM: Determine targets
+    Note right of SD: H.770.1(25)
+
+    Note over STM, SD: 1)
+    STM->>SD: Map thing to entity
+    SD-->>STM: Return entity
+
+    Note over CM, STM: 2)
+    CM->>STM: Subscribe traffic flow plan
+    STM-->>SD: Subscribe recommended route
+    CM->>SD: Publish traffic flow plan
+    CM->>SD: Publish recommended route
+  
+```
+
+Sequence diagram showing the operational flow for traffic congestion reduction route guidance between three metaverses: City mobility metaverse, Smart transportation metaverse, and Smart driving metaverse. Each metaverse contains a DTIFC component. The flow is divided into two parts: 1) Smart transportation metaverse sends 'Map thing to entity' to Smart driving metaverse, which returns 'Return entity'. 2) City mobility metaverse sends 'Subscribe traffic flow plan' to Smart transportation metaverse, which responds with 'Subscribe recommended route'. Then, an external 'Determine targets' step occurs, followed by 'Publish traffic flow plan' and 'Publish recommended route' from City mobility metaverse to Smart driving metaverse. The diagram is labeled H.770.1(25).
+
+**Figure I.4 – Operational flow for traffic congestion reduction route guidance**
+
+### I.2 Cyber physical security
+
+#### I.2.1 Description
+
+According to the discussions so far, the classification of the metaverse includes metaverse with digital twins and metaverse with IoT devices. To interoperate these metaverses securely, it is important to ensure the security of the underlying IoT devices and cyber-physical systems, as well as the cybersecurity of the metaverse. Since IoT devices and cyber-physical systems integrate the cyber and physical spaces, security measures should not be limited to cyberspace or individual systems but need to consider the impact on the physical space surrounding the systems. As shown in Figure I.5, when network-connected devices are subjected to cyberattacks, it affects the surrounding physical entities, which in turn also impacts the metaverse with digital twin or IoT devices. The interoperability of digital twins is effective when evaluating the impact of cyberattacks on the physical space.
+
+![Diagram illustrating the cyberattack impact on a metaverse with digital twin or IoT. The diagram is divided into two horizontal sections: 'Virtual world' (top) and 'Physical world' (bottom). In the virtual world, there are three metaverse environments: 'Metaverse B' (represented by blue human icons), 'Metaverse A-I' (represented by blue robot icons), and 'Metaverse A-II' (represented by blue robot icons). Metaverse B is connected to 'Metaverse platform B', and Metaverse A-I and A-II are connected to 'Metaverse platform A'. Arrows labeled 'Security impact' and 'Brokering translation federation' show interactions between these platforms. Below the virtual world, 'Digital twin function (data collection)' boxes connect to the physical world. In the physical world, icons represent humans and robots. Arrows show 'Security impact' from a robot to humans and 'Cyberattack against physical objects/IoT devices' from a human to robots. The reference 'H.770.1(25)' is in the bottom right corner.](cbb2d311b20781a595488445ded48d0a_img.jpg)
+
+Diagram illustrating the cyberattack impact on a metaverse with digital twin or IoT. The diagram is divided into two horizontal sections: 'Virtual world' (top) and 'Physical world' (bottom). In the virtual world, there are three metaverse environments: 'Metaverse B' (represented by blue human icons), 'Metaverse A-I' (represented by blue robot icons), and 'Metaverse A-II' (represented by blue robot icons). Metaverse B is connected to 'Metaverse platform B', and Metaverse A-I and A-II are connected to 'Metaverse platform A'. Arrows labeled 'Security impact' and 'Brokering translation federation' show interactions between these platforms. Below the virtual world, 'Digital twin function (data collection)' boxes connect to the physical world. In the physical world, icons represent humans and robots. Arrows show 'Security impact' from a robot to humans and 'Cyberattack against physical objects/IoT devices' from a human to robots. The reference 'H.770.1(25)' is in the bottom right corner.
+
+**Figure I.5 – Cyberattack impact on metaverse with digital twin or IoT**
+
+#### I.2.2 Assumptions
+
+This use case assumes the following context:
+
+The physical impact of a cyberattack on a metaverse with a digital twin varies depending on the system under attack. The physical impact also causes damage to the surroundings of the system, but the degree of the damage varies depending on the affected target and situation. At this point, by controlling the metaverse with the digital twin, it is possible to simulate the impact of a cyberattack on the physical space. Furthermore, if the affected target can also be represented by the digital twin, the degree of the damage can be estimated.
+
+Therefore, by coordinating the digital twin of the metaverse that is physically affected by a cyberattack and the digital twin that includes the target that is physically affected, it is possible to evaluate what kind of physical damage an attack on a metaverse would cause based on the surrounding circumstances.
+
+#### I.2.3 Scenario and operational flows
+
+This clause describes an application example of the DTIFC for realizing the novel cyber-physical security by ensuring interoperability among multiple digital twins that underlie the metaverse with the digital twins.
+
+As shown in Figure I.6, please check digital twin interoperability functions are used for the security of the cyber-physical system that underlies the metaverse with digital twins or IoT.
+
+- (1) The DTIFC federates data obtained from various digital twins to generate and refine physical impact estimation entity. The DTIFC transfers the physical impact estimation entity from one metaverse with digital twin A-I to A-II. By aggregating the physical impact estimation entity created in other digital twins, the entire estimation entity is refined.
+- (2) Another kind of metaverse with digital twin B subscribes to security information from metaverse with digital twin A. When evaluating how the physical impact of an attack is estimated by one digital twin on a device controlled by another digital twin, different combinations of digital twins require different information. The DTIFC allows digital twins to select and share the necessary information for evaluation for each digital twin combination.
+
+In this process, since each digital twin has different criteria for information and different granularity of information, it is necessary to translate the information by using the DTIFC. As a result, the digital twins of multiple metaverses can estimate the impact of cyberattacks, share the estimation result, and support the countermeasures for cyberattacks on the metaverse.
+
+![Sequence diagram showing the operational flow for cyber-physical security between Metaverse B, Metaverse A-I, and Metaverse A-II. The diagram includes two main interaction sequences: 1) Physical impact estimation and 2) Security information subscription and publishing.](878d9539700bd792e7d12ad6f1203c5d_img.jpg)
+
+```
+sequenceDiagram
+    participant Metaverse B
+    participant Metaverse A-I
+    participant Metaverse A-II
+
+    Note right of Metaverse A-I: 1)
+    Metaverse A-I->>Metaverse A-II: Transfer physical impact estimation entity
+    Note right of Metaverse A-II: Update entity
+    Metaverse A-II-->>Metaverse A-I: Aggregate physical impact estimation entity
+    Note right of Metaverse A-I: Refine entity
+
+    Note right of Metaverse B: 2)
+    Metaverse B->>Metaverse A-I: Subscribe security information
+    Note right of Metaverse A-I: Translate security information
+    Metaverse A-I-->>Metaverse B: Publish security information
+```
+
+The diagram illustrates the operational flow for cyber-physical security across three metaverses: Metaverse B, Metaverse A-I, and Metaverse A-II. Each metaverse contains a DTIFC (Digital Twin Interface and Framework) component. The interaction is divided into two numbered sequences:
+
+- Sequence 1:** Metaverse A-I sends a "Transfer physical impact estimation entity" to Metaverse A-II. Metaverse A-II performs an "Update entity" operation and returns an "Aggregate physical impact estimation entity" to Metaverse A-I. Metaverse A-I then performs a "Refine entity" operation.
+- Sequence 2:** Metaverse B sends a "Subscribe security information" request to Metaverse A-I. Metaverse A-I performs a "Translate security information" operation and returns "Publish security information" to Metaverse B.
+
+The diagram is labeled H.770.1(25) at the bottom right.
+
+Sequence diagram showing the operational flow for cyber-physical security between Metaverse B, Metaverse A-I, and Metaverse A-II. The diagram includes two main interaction sequences: 1) Physical impact estimation and 2) Security information subscription and publishing.
+
+**Figure I.6 – Operational flow for cyber-physical security**
+
+# Bibliography
+
+- [b-ITU-T H.780] Recommendation ITU-T H.780 (2012), *Digital signage: Service requirements and IPTV-based architecture.*
+- [b-ISO/IEC 23005-4] ISO/IEC 23005-4:2018, *Information technology – Media context and control – Part 4: Virtual world object characteristics.*
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.780-201206-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/H/T-REC-H.780-201206-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..171d0cfa226b805d49c152ecf8bd4bca0750ef1c
--- /dev/null
+++ b/marked/H/T-REC-H.780-201206-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3c2594d0b50d03ad172077cfaee097fab62978f89333dde0825557439a6ad888
+size 4322
diff --git a/marked/H/T-REC-H.780-201206-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg b/marked/H/T-REC-H.780-201206-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4ffc7109454cd1c521e7571005fa25707a0e0b0c
--- /dev/null
+++ b/marked/H/T-REC-H.780-201206-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:983d7303369ea4d4fe826e4a1e531cfcf5281e8b567774b3defebed76d90a1ce
+size 51458
diff --git a/marked/H/T-REC-H.780-201206-I_PDF-E/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg b/marked/H/T-REC-H.780-201206-I_PDF-E/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9fdf854ea91a2af2053101a7ce5e246b029bc3f8
--- /dev/null
+++ b/marked/H/T-REC-H.780-201206-I_PDF-E/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a8c6c16274972ea919f2ff874c2423c40867a914bae9ffe8632236ec61498068
+size 117724
diff --git a/marked/H/T-REC-H.780-201206-I_PDF-E/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/marked/H/T-REC-H.780-201206-I_PDF-E/744acfe8d4e31bcf03f95714c2f6e567_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2bb517949264f004cc9e11c9b28af5a4ce4365e6
--- /dev/null
+++ b/marked/H/T-REC-H.780-201206-I_PDF-E/744acfe8d4e31bcf03f95714c2f6e567_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e40538bde1fbffbe3b74574c3b3e122c058058cd3ee357a86053a2e7030427d1
+size 125401
diff --git a/marked/H/T-REC-H.780-201206-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/H/T-REC-H.780-201206-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e0ea630bd39c1c15d7a30b672306202012bc04f5
--- /dev/null
+++ b/marked/H/T-REC-H.780-201206-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0043c73715eb796c55108495d8f5d183564c04240644d9f980d2e74ed8efa932
+size 31789
diff --git a/marked/H/T-REC-H.780-201206-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/H/T-REC-H.780-201206-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..794f9b7c7844b06be63b1a229e073ded6960dfac
--- /dev/null
+++ b/marked/H/T-REC-H.780-201206-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1d69b46c13a0a9ae19c9bc86e2da8d18ed3ba779cd4226cf11dbfe6adde0fc0f
+size 58647
diff --git a/marked/H/T-REC-H.780-201206-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.780-201206-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994
--- /dev/null
+++ b/marked/H/T-REC-H.780-201206-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.780-201206-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/H/T-REC-H.780-201206-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..849729b15da1cd5695ea047f2f624b5578c4cea0
--- /dev/null
+++ b/marked/H/T-REC-H.780-201206-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bd8c18e89e62d9edbada5db1c496e93bf1d37f2a9f828a3cd859e38a7f15d20d
+size 91632
diff --git a/marked/H/T-REC-H.780-201206-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/H/T-REC-H.780-201206-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dabbfca17f0df0340ca787093e7c0536066f9e19
--- /dev/null
+++ b/marked/H/T-REC-H.780-201206-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:948e7481f0748ea3eade247aeefac9f8dbbc71e03e5eb588f17b8bfce931ace6
+size 3407
diff --git a/marked/H/T-REC-H.780-201206-I_PDF-E/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/marked/H/T-REC-H.780-201206-I_PDF-E/e29665b8abcea967ef289c6aff07ae4c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..27f31506ffef5a3fd9974c54b3f21ab319bea87c
--- /dev/null
+++ b/marked/H/T-REC-H.780-201206-I_PDF-E/e29665b8abcea967ef289c6aff07ae4c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9cb424aa621f51581a3c5f84d4654b974a69bc8a9facdf21009a3f40902b5b34
+size 37927
diff --git a/marked/H/T-REC-H.780-201206-I_PDF-E/ebce355620876e10f907f8b71926c112_img.jpg b/marked/H/T-REC-H.780-201206-I_PDF-E/ebce355620876e10f907f8b71926c112_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4265cb344abc030e962af7acdd8bbc73666426b0
--- /dev/null
+++ b/marked/H/T-REC-H.780-201206-I_PDF-E/ebce355620876e10f907f8b71926c112_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bacb1c559260d9d0518621d9a75744700186e0c97d2d16d0bca91b26a42b6aee
+size 36310
diff --git a/marked/H/T-REC-H.780-201206-I_PDF-E/f0a97d0d3818a253c1d2a009966081b1_img.jpg b/marked/H/T-REC-H.780-201206-I_PDF-E/f0a97d0d3818a253c1d2a009966081b1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3efca2a278995eb08960141115cf8d1667ed5d5c
--- /dev/null
+++ b/marked/H/T-REC-H.780-201206-I_PDF-E/f0a97d0d3818a253c1d2a009966081b1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4bcb2a818ef9d861c717865f8552beead9fc74be0fae74a194e3c69625349e77
+size 56911
diff --git a/marked/H/T-REC-H.785.0-201410-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.785.0-201410-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9002ee68e2b9ebf63d27d39ba8c73bdafb0e6be6
--- /dev/null
+++ b/marked/H/T-REC-H.785.0-201410-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.785.0-201410-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/H/T-REC-H.785.0-201410-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fa09116c1012e60fd9f4361414b69628cc442637
--- /dev/null
+++ b/marked/H/T-REC-H.785.0-201410-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dd1ccc768b12d00750be01f5ce06741e7816b90e63219daec10540ba3c765c73
+size 53400
diff --git a/marked/H/T-REC-H.785.0-201410-I_PDF-E/71ab4df17511d75261da8d462d643b1a_img.jpg b/marked/H/T-REC-H.785.0-201410-I_PDF-E/71ab4df17511d75261da8d462d643b1a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..08b7e3a960863e8eae627894a78fdfec5f556313
--- /dev/null
+++ b/marked/H/T-REC-H.785.0-201410-I_PDF-E/71ab4df17511d75261da8d462d643b1a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5561edaf27706b8a76bab0f6f59890cc0aaa268a3817fe3465b4644cdbfe03c7
+size 19548
diff --git a/marked/H/T-REC-H.785.0-201410-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/H/T-REC-H.785.0-201410-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3ae09a1c6b9fb787c2f280d00021e119d0725d88
--- /dev/null
+++ b/marked/H/T-REC-H.785.0-201410-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:78c987cfa67eadfc6d8d430de757270052cd0bffcb66b5374cdc9e6dab9e2888
+size 122912
diff --git a/marked/H/T-REC-H.785.0-201410-I_PDF-E/raw.md b/marked/H/T-REC-H.785.0-201410-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..95356d3fbd2a35253a10603a1c995c780e73a887
--- /dev/null
+++ b/marked/H/T-REC-H.785.0-201410-I_PDF-E/raw.md
@@ -0,0 +1,782 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.785.0**
+
+(10/2014)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+IPTV multimedia services and applications for IPTV –  
+Digital Signage
+
+---
+
+**Digital signage: Requirements for disaster  
+information services**
+
+Recommendation ITU-T H.785.0
+
+ITU-T
+
+![ITU logo: A globe with a red lightning bolt, next to the text '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 "International Telecommunication Union" is written in a blue, sans-serif font, with "ITU" in a larger, bold font above the full name.
+
+ITU logo: A globe with a red lightning bolt, next to the text '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        |
+| <b>Digital Signage</b>                                                                 | <b>H.780–H.789</b> |
+| 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.785.0
+
+## Digital signage: Requirements for disaster information services
+
+## Summary
+
+Recommendation ITU-T H.785.0 describes overall aspects and high-level requirements for disaster information services provided through digital signage. The main services expected to be applied are early warning to lessen damages, reports of up-to-the-minute situations and announcements of traffic status/evacuation sites. The requirements are categorized into eight areas: general, operational management, application/delivery, contents, security, network, terminal device/display and accessibility.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T H.785.0  | 2014-10-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12247">11.1002/1000/12247</a> |
+
+## Keywords
+
+Digital signage, disaster information service.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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   | Overview.....                                                                                                                    | 3    |
+| 6.1 | General disaster information services .....                                                                                      | 3    |
+| 6.2 | Consideration on content of disaster information .....                                                                           | 5    |
+| 6.3 | Flows of disaster information.....                                                                                               | 8    |
+| 6.4 | Types of DS terminal devices.....                                                                                                | 9    |
+| 7   | Requirements .....                                                                                                               | 9    |
+| 7.1 | General .....                                                                                                                    | 9    |
+| 7.2 | Operational management.....                                                                                                      | 11   |
+| 7.3 | Application/delivery .....                                                                                                       | 12   |
+| 7.4 | Content .....                                                                                                                    | 12   |
+| 7.5 | Security.....                                                                                                                    | 13   |
+| 7.6 | Network .....                                                                                                                    | 13   |
+| 7.7 | Terminal device/display .....                                                                                                    | 13   |
+| 7.8 | Accessibility requirements .....                                                                                                 | 14   |
+|     | Appendix I – A sample workflow in disaster situations .....                                                                      | 15   |
+|     | Appendix II – General overview of terminology based on the United Nations<br>International Strategy for Disaster Reduction ..... | 17   |
+|     | Bibliography.....                                                                                                                | 19   |
+
+
+
+## Recommendation ITU-T H.785.0
+
+## Digital signage: Requirements for disaster information services
+
+## 1 Scope
+
+This Recommendation addresses the high-level requirements for digital signage services under disaster situations. Disaster informational services contain three aspects:
+
+- 1) Early warning to lessen damages caused by a disaster
+- 2) Reporting up-to-the minute situations on disaster
+- 3) Announcements of traffic status or evacuation sites.
+
+## 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 alert** [b-ITU-T X.674]: A warning or alarm message concerning an impending danger or problem.
+
+**3.1.2 alert agency** [b-ITU-T X.674]: A national, regional or international entity responsible for the management of alerts.
+
+**3.1.3 content** [ITU-T H.780]: A combination of audio, still image, graphic, video, or data.
+
+NOTE – A variety of formats are classified as "data" (e.g., text, encoded values, multimedia description language introduced by [b-ITU-T H.760]).
+
+**3.1.4 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.5 multimedia** [b-ITU-T T.174]: The property of handling several types of representation media.
+
+**3.1.6 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 end-users.
+
+**3.1.7 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.8 universal design** [b-ITU-T Y.1901]: The design of the products and environments to be useable by all people, to the greatest extent possible by including accessibility features in the original design to prevent the need for adaptation after deployment.
+
+NOTE – The intent of universal design is to simplify life for everyone by making products, communications, and the built environment more usable by as many people as possible at little or no extra cost. Universal design benefits people of all ages and abilities.
+
+### **3.2 Terms defined in this Recommendation**
+
+This Recommendation defines the following terms:
+
+**3.2.1 reconstruction phase:** A later stage of disaster recovery, when definitive repair of the infrastructure affected by a disaster is done.
+
+**3.2.2 restoration phase:** The earlier stage of disaster recovery, when the first steps to restore services to the population affected by a disaster are taken.
+
+## **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|        |                                              |
+|--------|----------------------------------------------|
+| DS     | Digital Signage                              |
+| ETS    | Emergency Telecommunication Service          |
+| ICT    | Information and Communication Technology     |
+| IPTV   | Internet Protocol Television                 |
+| NFC    | Near Field Communication                     |
+| NGN    | Next Generation Networks                     |
+| PGP    | Pretty Good Privacy                          |
+| RFID   | Radio Frequency Identification               |
+| S/MIME | Secure/Multipurpose Internet Mail Extensions |
+| SVG    | Scalable Vector Graphics                     |
+| TD     | Terminal Device                              |
+| TLS    | Transport Layer Security                     |
+| UPS    | Uninterruptable Power Supply                 |
+
+## 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 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.
+
+## 6 Overview
+
+### 6.1 General disaster information services
+
+Information and communication technology (ICT) services treating disaster information are expected to deliver reliable content to people both swiftly and surely, and in a manner that may differ from usual delivery. The content delivered is based on the affected locations and/or damage-levels. From the viewpoint of disseminating content to a large number of people, it is desirable that ICT services be used daily and that they be well recognized by the masses. It is also preferable to provide the disaster information content through diverse communication methods (e.g., terrestrial broadcasting, cellular services, IPTV).
+
+NOTE 1 – [b-TR-FG DR&NRR] presents a number of case studies of the performance of public telecommunication systems in recent disasters.
+
+A variety of access methods gives an opportunity to fill gaps in individual information literacy and accessibility (e.g., an aged person may not be familiar with bi-directional Internet services such as social network services).
+
+Digital signage (DS) services, which are usually provided as a method of presentation in public areas, are ideal for supporting disaster information services. A chief characteristic of DS services is the flexibility for selecting and controlling content delivery according to service timing and the location of the DS terminal device. Large DS screens are commonly set in public places, which as such are useful as a means to deliver announcements in disaster situations.
+
+DS services deal with various aspects of disaster information: to provide early warning to lessen damage caused by disasters; to give up-to-date reports on disaster conditions; to provide the status of public infrastructure in and around affected areas; to give guidance on evacuation routes to shelters; and to report on the safety of victims. That is, DS services are expected to continuously provide disaster-relevant information over a period of time: before disasters, after disasters, in the restoration phase (i.e., an early stage of disaster recovery), and in the reconstruction phase (i.e., a later stage of disaster recovery). Hence, DS terminal devices may be also installed in locations serving as potential evacuation shelters/places.
+
+Classifying service locations in times of disaster is necessary because the content may be altered depending on audience location, which can significantly relate to the degree of damage from the disaster.
+
+The following types of service locations can be assumed for DS services at or during a disaster:
+
+- in shelters, where information on the current situation of a disaster and announcements from the local government can be delivered to evacuees;
+- in places close to residential areas, where information on disaster situations and on evacuation details can be delivered to terminal devices and targeted to people living in those areas;
+- in public places, where information on disaster situations and on evacuation plans can be delivered to persons using public facilities;
+- in tourist resorts, where information on disaster situations and on evacuation plans can be delivered to tourists;
+- at work places, where information on disaster situations and on evacuation plans can be delivered to employees;
+- on roads, where information on disaster situations and on evacuation plans can be delivered to persons in cars.
+
+NOTE 2 – [b-ETSI TS 102 182] introduces some service scenarios in emergency telecommunications. The scenarios include a service to citizens in their own dwelling; this Recommendation especially pays attention, however, to outside-the-home services in public spaces including evacuation shelters/places.
+
+In addition, it is useful to examine the requirements of DS services during disasters from four aspects: ensuring credibility of the information itself; scalability of data delivery; swiftness of data handling and availability of DS systems. Examples of these four aspects are as follows:
+
+- 1) credibility: establishment of data flows from authorities to audience, ensuring security through data transport;
+- 2) scalability: selection and grouping of DS terminal devices, usage of common information delivery platforms and multilingual support;
+- 3) swiftness: preparation of data formats and presentation layouts for disaster information services, establishment of work flows for data handling;
+
+NOTE 3 – It is very possible that sudden surges in streaming video access and other rich content will cause congestion. Measures to counter expected traffic congestion in a disaster situation should also be taken into account; however, details are for further study;
+
+- 4) availability: consideration of a DS terminal device specification that has a certain degree of resistance that enables it to withstand predicted disaster situations during and after the disaster, including the possibility of remote operation.
+
+Requirements on robustness, resilience and related aspects of ICT systems and services are items for further study. Damage to utility infrastructures caused by a huge disaster can affect daily life and businesses in wide areas. Typical types of damage of ICT systems are:
+
+- direct damage (e.g., destruction of aerial cables, collapse of telecommunication base or relay stations); and
+- indirect damage (e.g., loss of electric power).
+
+An interruption of electric power causes significant disruption as ICT systems, which may not have been damaged by the disaster itself, may become non-functional.
+
+NOTE 4 – When long-term power outages occur, fuel for private electric generators in the affected area may be insufficient. Similarly, batteries may be in short supply [b-MIC Report]. Therefore, it is not an exaggerated specification for a DS terminal device to have a secondary power supply unit in order to maintain services. Reduction of power consumption in DS terminal devices is also an effective measure to mitigate the effect of power outages.
+
+NOTE 5 – A DS terminal device may be equipped with an uninterruptable power supply (UPS) that includes storage batteries and/or a private power generator (e.g., a photovoltaic power generator).
+
+Next, important requirements are derived relative to the gathering and delivery of the information. Figure 6-1 illustrates an image of disaster information services provided via DS platforms that aggregates information on disaster and evacuation plans from multiple information sources and delivers this information to various DS terminal devices. Details of the information should be processed according to the requests or the needs of the audience. For example, evacuees may request information about the nearest evacuation shelter or its location information.
+
+![Figure 6-1: A model of emergency information deliveries. The diagram shows a central cloud labeled 'Digital signage platforms for communication under disaster' connected to various information sources and delivery points. On the left, 'Reliable information sources' include Public transport (Railways, Bus, Boats), Government/city office, Newspaper, and News-agency. These provide 'Traffic report' (Traffic jam, Safety routes) and 'News' (Disaster information). A 'Broadcaster' (satellite and tower) also feeds into the central platform. On the right, 'Internet (portal, posting)' provides 'Safety confirmation' and 'Disaster situation'. The central platform then distributes information to 'Metropolitan area' locations (Station public building, Commercial facilities, Designated shelter) and 'Affected area' locations (Temporary housing, Evacuation center). Delivery methods include 'Digital signage' (screens) and 'Mobile' devices. Icons for people and buildings are used to represent different locations and audiences.](e9314c83043183351ed74908e9bf2f90_img.jpg)
+
+Figure 6-1: A model of emergency information deliveries. The diagram shows a central cloud labeled 'Digital signage platforms for communication under disaster' connected to various information sources and delivery points. On the left, 'Reliable information sources' include Public transport (Railways, Bus, Boats), Government/city office, Newspaper, and News-agency. These provide 'Traffic report' (Traffic jam, Safety routes) and 'News' (Disaster information). A 'Broadcaster' (satellite and tower) also feeds into the central platform. On the right, 'Internet (portal, posting)' provides 'Safety confirmation' and 'Disaster situation'. The central platform then distributes information to 'Metropolitan area' locations (Station public building, Commercial facilities, Designated shelter) and 'Affected area' locations (Temporary housing, Evacuation center). Delivery methods include 'Digital signage' (screens) and 'Mobile' devices. Icons for people and buildings are used to represent different locations and audiences.
+
+Figure 6-1 – A model of emergency information deliveries (as per [ITU-T H.780])
+
+A deployment of this sort of service platform has several merits for treating disaster information:
+
+- the audience can accept the information anywhere and anytime through the diverse means of communications to which the audience is accustomed to;
+- if the platform provides a functionality that can transform/transcode original data generated by the information source to diverse media data formats, then the workload of information sources is decreased and the data can be quickly delivered;
+- disaster prevention, recovery actions and their planning can be conducted efficiently because of information sharing amongst public organizations.
+
+Details of information flows are provided in clause 6.2.
+
+### 6.2 Consideration on content of disaster information
+
+There are two types of information in terms of changeability depending on the disaster situation:
+
+- 1) live information: news on a disaster, evacuation orders, traffic status, safety of victims, etc.;
+- 2) static information: evacuation routes, maps, contact points for help, etc.
+
+Organizations doing work in disaster information services should prepare static information in advance of predictable disasters. There are a variety of information sources relevant to digital signage services; therefore, reliability and controllability of information are important points for treating live information. Standard routines on handling both live and static information among organizations should be carefully examined and established in advance.
+
+According to the timeline of the disaster (e.g., before, at or during the disaster, or in the restoration or reconstruction stages), the content of disaster information in digital signage services can be categorized as follows:
+
+- Early warning to prevent or lessen damages:
+
+Early warning services provide advanced notice of a disaster to lessen or avoid damage of the coming disaster.
+
+NOTE 1 – [b-UNISDR terms] defines that an early warning system is a set of capacities needed to generate and disseminate timely and meaningful alert information to enable individuals, communities and organizations threatened by a hazard to prepare for and to act appropriately and in sufficient time to reduce the possibility of harm or loss.
+
+NOTE 2 – To some extent, modern technology can predict a disaster before it causes harm to humans. For example, an earthquake generates primary waves (P-waves) and secondary waves (S-waves) simultaneously: P-waves run faster than S-waves, and P-waves cause less damage than S-waves. The effectiveness of earthquake early warning systems therefore, depends on the accuracy of detection of P-waves.
+
+- Reporting disaster situations by the minute:
+
+Victims wish to receive the latest information on their situation in time of a disaster, such as current status, rescue actions, relief supply delivery, etc.
+
+- Announcements of evacuation plans comprised of information such as traffic situations and evacuation shelters/locations:
+
+Information on evacuation shelters/places/routes is important. Traffic information is required to consider any required rerouting for evacuation and transportation of aid and supplies. Remote areas that are not affected directly can suffer from electric power outages or water disconnection. Especially in metropolitan areas, there is a high possibility that a large majority of commuters may be unable to return home due to such indirect effects; therefore, evacuation plans under several disaster situations should be considered in advance. Victims also wish to know how to obtain supplies.
+
+- Safety confirmation for victims:
+
+Confirmation of the safety of friends and family members is highly sought after information. Information services should provide the communication between these individuals even under heavy traffic congestion times or during shortage of network capacity.
+
+It is also important to prepare a framework for disaster information services based on the varying levels of damage because people in safe areas might be affected remotely because of huge damage on social infrastructures (e.g., electric power, gas and water). Damaged areas can be categorized as follows:
+
+- disaster area: area where a disaster affects people's life;
+- slight/mild disaster area: area where people can continue normal life in the aftermath of a disaster;
+- non-disaster area: area where people are not directly involved in a disaster.
+
+Paying attention to disaster response, showing the following types of content to an audience at or during a disaster should be at least considered:
+
+- General information on the disaster:
+
+When a large-scale disaster occurs, it is necessary to grasp the whole situation of the disaster. In this case, it is better to provide official or authorized information such as government announcements.
+
+- Information on public infrastructure:
+
+Specific information should be provided to locations where people directly or indirectly affected gather, e.g., to convey traffic information and damage situation around the locations.
+
+- Information on specific facilities:
+
+Information should be provided to facilities where DS terminal devices are installed: evacuation routes; announcements to cancel events; special support announcements (e.g., handing out blankets for those who have difficulty returning home), etc.
+
+Table 6-1 shows a mapping of disaster information services from the viewpoint of timeline and spatial relations of a disaster.
+
+**Table 6-1 – Examples of disaster information provided by DS services**
+
+| Location                  | Timeline                                         |                                                                                                       |                                                                                                                                 |                                  |
+|---------------------------|--------------------------------------------------|-------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|----------------------------------|
+|                           | Before disaster                                  | At or during disaster                                                                                 | Restoration phase                                                                                                               | Reconstruction phase<br>(Note 1) |
+| Disaster area             | Early warning:<br>Information on evacuation plan | Information on:<br>– evacuation<br>– disaster (local/national)                                        | Information on:<br>– safety confirmation<br>– contact points of public/private support                                          | (Note 2)                         |
+| Slight/mild disaster area | Early warning:<br>Information on evacuation plan | Information on:<br>– disaster (local/national)<br>– traffic<br>– return home/temporary accommodations | Information on:<br>– local infrastructure (e.g., traffic ban, power cut, water outage, public health)<br>– prevention of rumour | (Note 2)                         |
+| Non-disaster area         | Information on evacuation plan prepared          | Information on disaster (national)                                                                    | Appeals to support victims (e.g., donations, volunteers)                                                                        | (Note 2)                         |
+
+NOTE 1 – The reconstruction phase is assumed to start when there is no major risk of life.  
+NOTE 2 – The effectiveness of DS needs to be further studied. It may be expected that DS services be used as tools for information sharing amongst affected and non-affected people.
+
+ITU-T/ITU-R and other standards development organizations have studied standardization of early warning in social infrastructures such as digital broadcasting and mobile phone services.
+
+NOTE 3 – [b-ITU-R BT.1774-1] provides characteristics of satellite and terrestrial broadcasting systems used for disaster mitigation and relief operations, and [b-ETSI TS 22 268] describes requirements of public warning systems over cellular phone networks. [b-ITU-T H.740] shows a framework for application event handling which includes emergency alert for IPTV services.
+
+Safety confirmation services are also required to take into account scalability, reliability, and bi-directional behaviours of communication services like social infrastructure. These two types of content in DS services are treated mainly by means of linking with other independent early warning systems and safety confirmation systems rather than by a DS system alone. On the other hand, DS services can separately provide effective measures to disseminate other types of content: prepared evacuation plans, reporting disaster information and announcement of regional information.
+
+Finally, another aspect of content is considered. At or during large-scale disasters, sudden surges in the use of streaming video and other rich content as well as large amount of voice calls for safety confirmation will substantially interfere with all IP traffic. DS services usually use rich content like high-definition video. If the content is delivered during or even after a disaster, the altered data format or the data itself should be considered in advance.
+
+NOTE 4 – Examples of expected methods are replacement of large volume data with small volume data, the usage of pre-stored graphics or representations such as scalable vector graphics (SVG) [b-W3C SVG 1.1].
+
+If disaster information is planned to be delivered to a multitude of differing mobile terminal devices, it is also important to study methods to put services into practice.
+
+NOTE 5 – Content adaptation is the technology for converting formats of content in order to adapt content to device capabilities. The technology is especially effective on mobile terminal devices because of their limited capabilities such as computational power, memory, and screen size. Content adaptation provides a way of one source, multi-use without preparation of content to fit each kind of device.
+
+NOTE 6 – Profile management of DS terminal devices may be key to handling unspecified kinds of DS terminal devices. Details are for further study.
+
+### **6.3 Flows of disaster information**
+
+Flows of information can be classified from the viewpoints of information resources:
+
+- straightforward delivery: from public information sources to audience via DS services;
+- indirect delivery: from public information sources to audience through intermediate processes, which may select and convert data;
+- information sharing: from individual information sources to audiences.
+
+Public information sources include national/local governments and public agencies (e.g., traffic agency, meteorological agency), public utilities (e.g., electric power, transportation), and news organizations, which conduct on-the-ground reporting activities. On the other hand, individual information is created and registered by an individual person (e.g., the usage of social networking services on the Internet).
+
+This Recommendation focuses on the provision of information coming from reliable public information sources.
+
+The following diagrams show basic data flows of disaster information from a public information source to audience.
+
+![Flow model showing Public information source to DS service to Audience Flow model showing Public Information source to Intermediary (Aggregator and Disseminator) to DS service to Audience](71ab4df17511d75261da8d462d643b1a_img.jpg)
+
+**a) Straightforward**
+
+```
+
+  graph LR
+    A([Public information source]) --> B[DS service]
+    B --> C([Audience])
+  
+```
+
+**b) Indirect**
+
+```
+
+  graph LR
+    A([Public Information source]) --> B
+    subgraph Intermediary
+      B[Aggregator] --> C[Disseminator]
+    end
+    C --> D[DS service]
+    D --> E([Audience])
+  
+```
+
+H.785.0(14)\_F6-2
+
+**Figure 6-2 – Flow models of emergency information**
+
+Flow model showing Public information source to DS service to Audience Flow model showing Public Information source to Intermediary (Aggregator and Disseminator) to DS service to Audience
+
+The intermediary in Figure 6-2 contains two functional entities: an aggregator that gathers disaster information from multiple information sources; a disseminator that sends the information to a large number of people through various communication methods. For example, a government warning system functioning as an aggregator gathers information relevant to disaster, and a disseminator (e.g., a news organization) delivers the information to the audience by simultaneously using a wide variety of communication channels (such as broadcasting, mobile networks and DS services).
+
+NOTE 1 – Figure 6-2 assumes the platform contains both an aggregator function and a disseminator function.
+
+When communication facilities of a DS system suffer massive damage from a disaster, indirect delivery cannot be pursued (e.g., destruction of underground cables or malfunctioning of communication equipment). In cases such as these, DS services may quickly change from indirect delivery to straightforward delivery, if possible.
+
+Typical information delivery methods assumed according to [ITU-T H.780] are as follows:
+
+- Push mode:
+  - commercial DS servers deliver the information to DS terminal devices;
+  - disaster-service-specific information servers, which are administrated by public agencies, deliver the information to DS terminal devices;
+- Pull mode:
+  - DS terminal devices request the information directly from commercial/official DS servers.
+
+**6.4 Types of DS terminal devices**
+
+Various types of terminal devices can be used as digital signage terminal devices for disaster information services. See [ITU-T H.780].
+
+**7 Requirements**
+
+When digital signage systems provide disaster information services, requirements of [ITU-T H.780] are superseded by this clause.
+
+**7.1 General**
+
+This clause describes general requirements of DS systems providing disaster information services.
+
+- When a government/public agency establishes an official guideline for providing disaster information services, DS systems are required to align with the guideline.
+
+**Rec. ITU-T H.785.0 (10/2014)**          9
+
+NOTE 1 – See [b-ITU-T E.107].
+
+NOTE 2 – The guideline may contain levels of emergency, sample texts for emergency messages and official scripts for presentation, etc.
+
+- When a government/public agency establishes an official criterion for the installation of DS terminal devices for disasters, DS systems are required to obey the criterion.
+
+NOTE 3 – The criterion depends on predictable disaster situations such as waterproofing, earthquake-resistance, etc.
+
+- When DS systems support early warning services, the systems are required to communicate with alerting agencies.
+
+NOTE 4 – A national broadcasting service, which has an infrastructure for public warning, is a good candidate in which to be connected as an alert agency [b-ITU-R BT.1774-1].
+
+- DS systems are recommended to be prepared against the outcome of a disaster from the viewpoint of hardware issues (e.g., spare parts, emergency power supply) and software issues (e.g., provisioning of an operation manual, situational emergency training).
+
+NOTE 5 – See [b-ITU-T E.106].
+
+NOTE 6 – Power outages are a critical issue for ICT systems. The preparation against a power outage includes the usage of electric facilities being available in the locations of the terminal devices and the displays.
+
+- DS systems, when displays are installed in public spaces, are recommended to immediately provide emergency alert information in the case of a disaster (e.g., earthquakes and weather hazards).
+
+NOTE 7 – See [ITU-T H.780].
+
+- DS systems are recommended to use established international standards on disaster information services.
+
+NOTE 8 – There are several well-known multimedia data format standards. [ITU-T X.1303 *bis*] specifies generic message formats for alerting services. Appendix II of [ITU-T H.780] introduces video/audio formats. Also, [b-ITU-T H.265] can be used as video coding.
+
+- DS systems are recommended to ensure interoperability according to international guidelines in times of multi-national disaster (e.g., when international traffic can be affected at or during disaster in a distant area).
+
+NOTE 9 – See [b-ITU-T E.106].
+
+- DS systems are recommended to rotate the presentation of disaster information to the audience during a predetermined period.
+
+- DS systems are recommended to support multiple communication interfaces.
+
+NOTE 10 – For example, if landline facilities in affected areas suffer huge damage, it is expected that telecommunications carriers provide temporary wireless equipment for DS systems.
+
+- DS systems are recommended to regularly announce that DS terminal devices of the services will provide disaster information when disasters happen.
+
+NOTE 11 – See [b-UNISDR HFA].
+
+- DS systems are recommended to regularly show evacuation plans of the places from where individual DS terminal devices resides.
+
+NOTE 12 – See [b-UNISDR HFA].
+
+- DS systems are recommended to be able to stop delivery and/or presentation of the information in order to avoid confusion based on some reasons (e.g., delay, incorrect information).
+
+NOTE 13 – Key resources for handling disaster information services are system operators, equipment, electrical power, networks and contents. The lack of resources can cause trouble with the services. Especially, in the case that a service provider (e.g., a public transportation or a large-scale commercial facility) plans to gather and deliver disaster information, if a pre-determined system cannot be fully realized, the information should not be dealt with. A style of information flow like this is involved in "straight forward delivery" described in clause 6.3.
+
+NOTE 14 – Clause 7.2 describes a requirement for cancellation of presentation of contents.
+
+- If DS services use disaster information from external sources, DS systems are recommended to show the latest information in the sources.
+- DS systems are recommended to update disaster information according to predetermined renewal periods to be used in the case of disasters.
+
+### 7.2 Operational management
+
+This clause describes operational requirements of DS systems providing disaster information services.
+
+- DS systems are required to have the ability to switch presentation of normal content to that of emergency content at or during a disaster, and in a simplified manner, or vice versa.
+
+NOTE 1 – In a general way, it is difficult to change operational modes of systems (e.g., changing configurations from normal mode to emergency mode and vice versa). Details of the operational modes such as timing of alteration are for further study.
+
+NOTE 2 – It is necessary to carefully consider equipping with the functionality to change content automatically because it is assumed that national/local governments request certain content depending on disaster situations.
+
+NOTE 3 – Operators are expected to be busy at or during disaster; therefore, it is important to provide an easy way to switch operational modes.
+
+- DS systems are recommended to have the ability to grasp geographical relations between locations of DS terminal devices and affected areas.
+- DS systems are recommended to support remote control functions that enable operations of DS terminal devices from a non-affected area.
+- DS systems are recommended to provide the capability to force a cancellation of a specific message and/or data already delivered.
+
+NOTE 4 – [b-ITU-T X.1303 *bis*] prepares a code value "Cancel" of the element "msgType". Implementation details are out of the scope of this Recommendation.
+
+- DS systems are recommended to be equipped with a function to administrate the status of DS terminal devices in times of disasters.
+- DS systems, which have multiple streaming channels re-transmitting broadcasting services such as satellite, terrestrial and cable TV services, are recommended to have the ability to select a streaming channel as a disaster information service.
+- DS systems having multiple display screens are recommended to have the ability to select the appropriate display screen to show disaster information.
+- DS systems can optionally enable DS service providers to use a mechanism to interrupt playing groups of content (e.g., regularly scheduled advertisements and programs) in order to allow for the delivery of alert warning messages and associated emergency messages.
+- DS systems can optionally control DS terminal devices remotely as an entire group, as a subgroup, or individually.
+
+NOTE 5 – See clause 8.1.5 of [ITU-T H.780].
+
+- DS systems can optionally have the ability to manage terminal device information (e.g., capabilities of DS terminal devices, status of the devices) by way of receiving information from DS terminal devices.
+
+NOTE 6 – When the systems provide services to unspecified kinds of DS terminal devices or the systems provide services under fluctuating network conditions, this registration method regarding terminal information can be used for content adaptation and/or for adjustment of content delivery [b-ISO/IEC 23009-1].
+
+NOTE 7 – For examples, [b-ETSI TS 102 822-3-3] and [b-ISO/IEC 21000-7] specify details of metadata regarding capabilities of terminal devices.
+
+### 7.3 Application/delivery
+
+This clause describes requirements on the aspects of applications of DS systems including content delivery abilities.
+
+- DS systems are required to have the ability of delivering disaster information to multiple DS terminal devices according to the proximity to the disaster.
+
+- DS systems delivering real-time content for disaster information services are required to take measures against electric power failures in locations where DS applications are relevant to content delivery installations.
+
+NOTE – Data centres, large-scale commercial facilities and buildings are equipped with electric power sources such as power storage units and generators. The measures against power outages include the installation of servers in these locations.
+
+- DS systems are recommended to have duplication of their facilities for content delivery, which are installed in different places.
+
+- DS systems, when disaster information is expected to be directly provided by operators (i.e., operators aggregate and/or summarize the information), are recommended to have duplex facilities for content creation, which are installed in different places.
+
+- DS systems are recommended to have the ability to create and maintain metadata specific to disaster information services.
+
+- DS systems, when disaster information is expected to be directly provided by operators (i.e., operators aggregate and summarize the information), can optionally have the ability to use templates, which have placeholders to insert text and/or image, to create content in a timely manner.
+
+- DS systems can optionally support multi-vendor terminal devices in an integrated manner.
+
+### 7.4 Content
+
+This clause describes requirements of DS systems on the aspects of content handling.
+
+- DS systems are required to show the time when disaster information was updated.
+
+NOTE 1 – Development of measures for preventing confusion based on old information should be taken into account. DS systems are recommended to present disaster information in multiple languages according to the assumed language of victims (foreigners in particular).
+
+- DS systems are recommended to treat metadata regarding sources and senders of disaster information.
+
+NOTE 2 – See [ITU-T X.1303 *bis*].
+
+- DS systems are recommended to display clearly the source from which the information originated.
+
+- DS systems can optionally deliver content specific to a disaster to DS terminal devices in advance, and present the content at times of assumed disaster situations.
+
+NOTE 3 – See [b-ETSI TS 102 182].
+
+### 7.5 Security
+
+This clause describes security requirements of DS systems handling disaster information.
+
+- DS systems are required to prevent unauthorized access to the systems and any associated resources.
+- DS systems, when the systems are directly connected to other service systems, are required to provide protection mechanisms for interconnection with non-authorized systems.
+- DS systems are recommended to verify the integrity of content in case of receiving disaster information prior to display.
+
+NOTE 1 – See [b-ITU-T Y.2205]. Verification can prevent unauthorized modification, deletion and creation.
+
+- DS systems are recommended to establish secure channels with the sources of disaster information.
+
+NOTE 2 – Transport layer security (TLS) [b-IETF RFC 2246] is one of many standards addressing secure communications.
+
+- DS systems can optionally use digital signature schemes for preventing modification of disaster information during transmission.
+
+NOTE 3 – Pretty good privacy (PGP) [b-IETF RFC 4880] and Secure/Multipurpose Internet Mail Extensions (S/MIME) [b-IETF RFC 5751] are well-known standards relevant to digital signatures.
+
+### 7.6 Network
+
+Continuity of information services in damaged areas depends in a large part on disaster relief and network resilience, which is the ability to provide and maintain an acceptable level of service in the face of fault situations (e.g., re-routing in the case of troubles of network facilities in a relay point).
+
+NOTE – ITU-T has studied emergency telecommunications service (ETS); requirements; technical specifications on ETS over NGN are described in [b-ITU-T Y.2201], [b-ITU-T Y.2205] and [b-ITU-T Y.2705]. These requirements and specifications include essential network requirements of disaster information services, and it is better to provide disaster information services over networks fulfilling generic requirements.
+
+- When DS services deliver information to broad areas, DS systems are required to provide services over networks that have abilities of disaster relief and network resilience (e.g., public networks provided by telecommunications carriers).
+
+### 7.7 Terminal device/display
+
+This clause describes requirements of DS terminal devices.
+
+- DS terminal devices are recommended to alter presentation methods according to emergency levels/categories or importance of content (e.g., overlapping disaster information by using marquee text).
+- DS terminal devices can optionally have the ability to receive information other than from IP networks (e.g., receive terrestrial broadcasting directly).
+- DS terminal devices can optionally have light adaptable capabilities to display information regarding disaster events during electrical power outages (e.g., display information regarding evacuation areas/shelters/routes information).
+
+NOTE 1 – Light adaptable capabilities have the following characteristics. DS terminal devices in very dark or very bright environments can automatically adjust their brightness in order to help people easily see the content regarding the disaster. If the DS terminal device is in an electrical power outage situation, the display can show the latest disaster information for a certain period of time.
+
+- Outdoor DS terminal devices can be optionally equipped with their own power supply units consisting power storage and/or generators.
+- DS terminal devices can optionally have the capability to recognize a disaster situation (e.g., temperature change during fire) through various sensing devices and deliver such information to the digital signage server.
+- DS terminal devices can optionally have the capability to interact with each other by means of direct communication methods among terminal devices in order to share disaster information.
+
+NOTE 2 – In case of network failures in times of disasters, residents in the affected area need to share information. Alternative communication methods implemented in DS terminal devices such as radio frequency identification (RFID) or near field communication (NFC) can be used [b-ISO/IEC 18092].
+
+- DS terminal devices can optionally manage and transmit their own profile information, including static information (e.g., identification of terminal device, terminal capabilities) and/or dynamic information (e.g., terminal status) of the devices, to device management functionality.
+
+### 7.8 Accessibility requirements
+
+This clause describes accessibility requirements of DS systems including DS terminal devices.
+
+- DS terminal devices, applications and content for disaster information services are recommended to be designed using principles of universal design.
+
+NOTE 1 – Important disabilities relevant to universal design include hearing, sight, aging and cognitive disabilities, lack of controllability of man-machine interfaces and difficulty of use of terminal devices [b-ITU-R BT.2207-2].
+
+NOTE 2 – See [b-ITU-T F.790].
+
+- DS terminal devices can optionally have specific presentation functionality for disaster information for those who need accessibility support in times of a disaster. (e.g., narration functionality for a person who is visually impaired, sign language functionality for a hearing-impaired person or translation for foreigners).
+
+NOTE 3 – Some accessible broadcast service technologies may be applicable to digital signage services (e.g., speech rate conversion, real-time closed-captioning) [b-ITU-R BT.2207-2].
+
+- DS terminal devices can optionally have accessible means related to emergency calls and confirmation of personal safety for those who needs accessibility support in times of disaster (e.g., voice recognition functionality for a person who is visually impaired or sign language (motion, gesture, etc.) recognition functionality for a hearing-impaired person).
+
+## Appendix I
+
+### A sample workflow in disaster situations
+
+(This appendix does not form an integral part of this Recommendation.)
+
+There are some checkpoints when disaster information is provided over digital signage: readiness of services, preparedness of content, returning to normal operation etc. When service environments, including human resources, are not fully ready, stopping delivery of disaster information services should be considered because the information may have negative impact on human lives.
+
+The following steps are assumed in the workflow displayed in Figure I.1:
+
+- 1) Environment checks: readiness of entire service resources should be checked before starting the services. Basic check points are: sufficient number of operational staff; network connections; electric power; and conditions of the network/computer equipment;
+- 2) Content checking: content and relevant data are updated and sent to a digital signage system. The content and data are provided by reliable sources such as governments or broadcasters;
+
+![Flowchart of disaster information service operations](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg)
+
+```
+graph TD; Start([Start]) --> SR{Service ready?}; subgraph SR [ ]; Operator[Operator]; Power[Power]; Equipment[Equipment]; Network[Network]; end; SR -- Yes --> CR{Contents ready?}; subgraph CR [ ]; Static[Static info]; Live[Live info]; end; CR -- Yes --> PID[Provide disaster information]; PID --> RNO{Resume normal operation?}; RNO -- No --> SR; RNO -- Yes --> QDIS[Quit disaster information services]; QDIS --> End([End]);
+```
+
+The flowchart illustrates the sample flow of operations for disaster information services. It begins with 'Start', leading to a decision diamond 'Service ready?'. This diamond contains four sub-checks: 'Operator', 'Power', 'Equipment', and 'Network'. If 'Yes', it proceeds to another decision diamond 'Contents ready?', which contains 'Static info' and 'Live info'. If 'Yes', it proceeds to a process box 'Provide disaster information'. From there, it reaches a decision diamond 'Resume normal operation?'. If 'No', it loops back to the 'Service ready?' check. If 'Yes', it proceeds to a process box 'Quit disaster information services', which then leads to the 'End' terminal. A 'No' path from the 'Contents ready?' check also leads to the 'End' terminal.
+
+Flowchart of disaster information service operations
+
+H.785.0(14)\_Fl.1
+
+Figure I.1 – Sample flow of operations of disaster information services
+
+- 3) Content delivery: content is sent to DS terminal devices;
+- 4) Situational decision: the digital signage service can resume normal services when disasters are considered to have calmed or ended;
+- 5) Service termination: disaster information services are stopped when pre-conditions are not fully ready or when disasters has ended.
+
+Reliability of the information regarding readiness of content is an item for further study. It is generally desirable that information regarding a disaster is provided by reliable sources such as governments/public agencies On the other hand, from the point of view of swiftness of evacuation and effectiveness of information limited in a narrower area, information from individuals is also useful in disaster situations.
+
+## Appendix II
+
+### General overview of terminology based on the United Nations International Strategy for Disaster Reduction
+
+(This appendix does not form an integral part of this Recommendation.)
+
+An overview of terminology used to describe disasters and hazards is useful in order to develop a common view to help show the variety of areas where digital signage services may be applicable to disaster information services.
+
+One well-known concept in disasters is "Natural disasters are the consequences or effects of natural hazards. They represent a serious breakdown in sustainability and disruption of economic and social progress" [b-UNESCO]. In this way, the meaning of disasters and hazards is different.
+
+United Nations International Strategy for Disaster Reduction (UNISDR) defines the term "disaster" based on the following concept [b-UNISDR terms]:
+
+**[Disaster]:** *A serious disruption of the functioning of a community or a society involving widespread human, material, economic or environmental losses and impacts, which exceeds the ability of the affected community or society to cope using its own resources.*
+
+**NOTE –** *Disasters are often described as a result of the combinations of: the exposure of a hazard; conditions of vulnerability that are present; and insufficient capacity or measures to reduce or cope with the potential negative sequences. Disaster impacts may include loss of life, injury, disease and other negative effects on human physical, mental and social well-being, together with damage to property, destruction of assets, loss of services, social and economic disruption and environmental degradation.*
+
+Natural hazards are naturally-occurring physical phenomena caused either by the rapid or slow onset events having atmospheric, geologic and hydrologic origins on solar, global, regional, national and local scales. They include earthquakes, volcanic eruptions, landslides, tsunamis, floods and drought [b-UNESCO].
+
+On the other hand, [b-UNISDR terms] uses a more general definition of "hazard" including aspects concerning human-factors as follows:
+
+**[Hazard]:** *A dangerous phenomenon, substance, human activity or condition that may cause loss of life, injury or other health impacts, property damage, loss of livelihoods and services, social and economic disruption, or environmental damage.*
+
+A classification of hazard according to [b-UNISDR terms] is as found in Table II.1.
+
+When digital signage systems for disaster information services are deployed, appropriate information sources should be selected depending on types of hazards mentioned-above.
+
+For instance, common alerting protocol (CAP 1.2) [ITU-T X.1303 *bis*], which standardizes a general message format for exchanging all-hazard emergency alerts and public warning over network, has already prepared to an element "category" to fit with these categorization. For example, code values of the element include "Geo": Geophysical (e.g., landslide); "Met": meteorological (e.g., flood); "CBRNE": Chemical, Biological, Radiological, Nuclear or High-Yield Explosive threat of attack. [b-ITU-T H.740] also introduces a use-case of CAP specifications for emergency notifications.
+
+**Table II.1 – Hazard classification**
+
+| <b>Type</b>                | <b>Description</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | <b>Examples</b>                                                                                                                                                                                                                                                                                                                   |
+|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Biological hazard          | Process or phenomenon of organic origin or conveyed by biological vectors, including exposure to pathogenic microorganism, toxins and bioactive substances that may cause serious damage.                                                                                                                                                                                                                                                                                                               | Outbreaks of epidemic diseases, plant or animal contagion, insect or other animal plagues and infestations.                                                                                                                                                                                                                       |
+| Geological hazard          | Geological process or phenomenon that may cause serious damage.                                                                                                                                                                                                                                                                                                                                                                                                                                         | Earthquakes, volcanic activity and emissions, and related geophysical processes such as mass movements, landslides, rockslides, surface collapses and debris or mud flows.<br>NOTE – Tsunamis are difficult to categorize; however, they are essentially an oceanic process that is manifested as a coastal water-related hazard. |
+| Hydrometeorological hazard | Process or phenomenon of atmospheric, hydrological or oceanographic nature that may cause serious damage.                                                                                                                                                                                                                                                                                                                                                                                               | Tropical cyclones (a.k.a. typhoons and hurricanes), thunderstorms, hailstorm, tornados, blizzards, heavy snowfall, avalanches, coastal storm surges, floods including flash floods, drought, heat-waves and cold-spells.                                                                                                          |
+| Socio-natural hazard       | The phenomenon of increased occurrence of certain geophysical and hydrometeorological hazard events that arise from the interaction of natural hazards with overexploited or degraded land and environmental resources.<br>NOTE 1 – This term is used for the circumstances where human activity is increased the occurrence of certain hazards beyond their natural probabilities.<br>NOTE 2 – This is an emerging new concept that is not in widespread use but is of growing professional relevance. | –                                                                                                                                                                                                                                                                                                                                 |
+| Technological hazard       | A hazard originating from technological or industrial conditions, including accidents, dangerous procedures, infrastructure failures or specific human activities that may cause serious damage.                                                                                                                                                                                                                                                                                                        | Industrial pollution, nuclear radiation, toxic waste, dam failures, transport accidents, factory explosions, fires, and chemical spills.                                                                                                                                                                                          |
+
+## Bibliography
+
+- [b-ITU-T E.106] Recommendation ITU-T E.106 (2003), *International Emergency Preference Scheme (IEPS) for disaster relief operations.*
+- [b-ITU-T E.107] Recommendation ITU-T E.107 (2007), *Emergency Telecommunications Service (ETS) and interconnection framework for national implementations of ETS.*
+- [b-ITU-T F.790] Recommendation ITU-T F.790 (2007), *Telecommunications accessibility guidelines for older persons and persons with disabilities.*
+- [b-ITU-T H.265] Recommendation ITU-T H.265 (2013) | ISO/IEC 23008-2:2013, *High efficiency video coding.*
+- [b-ITU-T H.740] Recommendation ITU-T H.740 (2010), *Application event handling for IPTV services.*
+- [b-ITU-T H.760] Recommendation ITU-T H.760 (2009), *Overview of multimedia application frameworks for IPTV services.*
+- [b-ITU-T M.1400] Recommendation ITU-T M.1400 (2006), *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 X.1303 bis] Recommendation ITU-T X.1303 bis (2014), *Common alerting protocol (CAP 1.2).*
+- [b-ITU-T Y.1901] Recommendation ITU-T Y.1901 (2009), *Requirement for the support of IPTV services.*
+- [b-ITU-T Y.2201] Recommendation ITU-T Y.2201 (2009), *Requirements and capabilities for ITU-T NGN.*
+- [b-ITU-T Y.2205] Recommendation ITU-T Y.2205 (2011), *Next Generation Networks – Emergency telecommunications – Technical considerations.*
+- [b-ITU-T Y.2705] Recommendation ITU-T Y.2705 (2013), *Minimum security requirements for interconnection of Emergency Telecommunications Service (ETS).*
+- [b-ITU-R BT.1774-1] Recommendation ITU-R BT.1774-1 (2007), *Use of satellite and terrestrial broadcast infrastructures for public warning, disaster mitigation and relief.*
+- [b-ITU-R BT.2207-2] Report ITU-R BT.2207-2 (2012), *Accessibility to broadcasting services for persons with disabilities.*
+- [b-TR-FG DR&NRR] Technical Report ITU-T FG DR&NRR (2013), *Technical Report on Telecommunications and Disaster Mitigation.*
+- [b-ETSI TS 22 268] ETSI TS 122 268 V11.5.0 (2013-01), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Public Warning System (PWS) requirements (3GPP TS 22.268 version 11.5.0 Release 11).*
+
+- [b-ETSI TS 102 182] ETSI TS 102 182 V1.4.1 (2010-07), *Emergency Communications (EMTEL); Requirements for communications from authorities/organizations to individuals, groups or the general public during emergencies.*
+- [b-ETSI TS 102 410] ETSI TR 102 410 V1.1.1 (2007-08), *Emergency Communications (EMTEL); Basis of requirements for communications between individuals and between individuals and authorities whilst emergencies are in progress.*
+- [b-ETSI TS 102 822-3-3] ETSI TS 102 822-3-3 V1.6.1 (2012-12), *Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 3: Metadata; Sub-part 3: Phase 2 – Extended Metadata Schema.*
+- [b-IETF RFC 2246] IETF RFC 2246 (1999), *The TLS Protocol Version 1.0.*
+- [b-IETF RFC 4880] IETF RFC 4880 (2007), *OpenPGP Message Format.*
+- [b-IETF RFC 5751] IETF RFC 5751 (2010), *Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification.*
+- [b-ISO/IEC 18092] ISO/IEC 18092:2013 (2013), *Information technology – Telecommunications and information exchange between systems – Near Field Communication – Interface and Protocol (NFCIP-1).*
+- [b-ISO/IEC 21000-7] ISO/IEC 21000-7(2013), *Information technology – Multimedia framework (MPEG-21) – Part 7: Digital Item Adaptation.*
+- [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.*
+- [b-MIC Report] Ministry of Internal Affairs and Communications (MIC), Japan (2011), *Maintaining Communications Capabilities during Major Natural Disaster and other Emergency Situations.*  
+<[www.soumu.go.jp/main\\_content/000146938.pdf](http://www.soumu.go.jp/main_content/000146938.pdf)>
+- [b-UNESCO] UNESCO (2007), *Disaster Preparedness and Mitigation.*  
+<<http://www.unesco.org/new/en/natural-sciences/special-themes/disaster-preparedness-and-mitigation/disaster-risk-reduction>>
+- [b-UNISDR HFA] UNISDR HFA (2005), *Hyogo Framework for Action 2005-2015: Building the Resilience of Nations and Communities to Disasters.*  
+<<http://www.unisdr.org/we/coordinate/hfa>>
+- [b-UNISDR terms] UNISDR (2009), *2009 UNISDR Terminology on disaster risk reduction.* <<http://www.unisdr.org/we/inform/publications/7817>>
+- [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                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| 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.812-201711-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/H/T-REC-H.812-201711-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7be7dbdc3989471632ad74a520719197418e9772
--- /dev/null
+++ b/marked/H/T-REC-H.812-201711-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3c6ab03919e5561fb29531d72ce439c1e28da4213abd09dbaea05801dbde0d7b
+size 139455
diff --git a/marked/H/T-REC-H.812-201711-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/marked/H/T-REC-H.812-201711-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1a4c02d537b96bba6744b44e59ccea233fa7a504
--- /dev/null
+++ b/marked/H/T-REC-H.812-201711-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4119f6f45a0f699d5d19eca7ec73e430bbd2e7b9be1d7079b1043f9f41bf5e25
+size 27148
diff --git a/marked/H/T-REC-H.812-201711-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/H/T-REC-H.812-201711-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..19a194c3ee03b4e3ff305726e887842c22df6519
--- /dev/null
+++ b/marked/H/T-REC-H.812-201711-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:225cfc231b5130d22d099af0e44932d432cff03575914bae97d7e8ea38120147
+size 37266
diff --git a/marked/H/T-REC-H.812-201711-I_PDF-E/77464a47f104d0d647b2414591137b64_img.jpg b/marked/H/T-REC-H.812-201711-I_PDF-E/77464a47f104d0d647b2414591137b64_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..90a88658df5091cce6454291b6d81bacd4a3e079
--- /dev/null
+++ b/marked/H/T-REC-H.812-201711-I_PDF-E/77464a47f104d0d647b2414591137b64_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c961702f04573ec2045582c13de12cceb92114b02eb5d33b7a6509855bed54e3
+size 23193
diff --git a/marked/H/T-REC-H.812-201711-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/H/T-REC-H.812-201711-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7ede097c506959d95f716db62da1338537abcc19
--- /dev/null
+++ b/marked/H/T-REC-H.812-201711-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:11fba0c01f611a73dc87871c051f1b9452e394291155f87a5e5b933e7c83aa0a
+size 104488
diff --git a/marked/H/T-REC-H.812-201711-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/H/T-REC-H.812-201711-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6275813a193c81e791a0ec30af9517517ce406d2
--- /dev/null
+++ b/marked/H/T-REC-H.812-201711-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:df2d9ee2c4798e033afa40c502bb82c83c9d1f8f0f9521112123be72911ecae1
+size 145892
diff --git a/marked/H/T-REC-H.812-201711-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.812-201711-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..48fa93b38e6fdfc3d1b86050f5de65f1ad4ed9dc
--- /dev/null
+++ b/marked/H/T-REC-H.812-201711-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:be98fe16aa87ea5f9c67c324bcd1988b0a4fbcebae14b672a978bc305a28a2dd
+size 68680
diff --git a/marked/H/T-REC-H.812-201711-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/H/T-REC-H.812-201711-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..73886e45221091e03364241c0c0b52a09ab4a093
--- /dev/null
+++ b/marked/H/T-REC-H.812-201711-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a37a289bbab32eae01ecb52d034caad0b164fe0c4f07f6cd6125f05be2349246
+size 85891
diff --git a/marked/H/T-REC-H.812-201711-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg b/marked/H/T-REC-H.812-201711-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8bcda2c01451dbc3cddbdce7f60f1edcb3cde5e9
--- /dev/null
+++ b/marked/H/T-REC-H.812-201711-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.812-201711-I_PDF-E/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg b/marked/H/T-REC-H.812-201711-I_PDF-E/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8d5141bd886fee34cdfd08abd43db28f511e1f2b
--- /dev/null
+++ b/marked/H/T-REC-H.812-201711-I_PDF-E/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d916b9f5ab76075f941d519bcde2cfc4e6318d85e1ac9546b6835d752fae9e42
+size 86172
diff --git a/marked/H/T-REC-H.812.1-201711-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.812.1-201711-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..61904c12b802df120c05ae72cd89a3ef2690dd5b
--- /dev/null
+++ b/marked/H/T-REC-H.812.1-201711-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_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.1-201711-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg b/marked/H/T-REC-H.812.1-201711-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ebcdb94f63d4f09c3258175796da925201e1ca67
--- /dev/null
+++ b/marked/H/T-REC-H.812.1-201711-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f04aac54bebf2561cc5bfde3e1d40faf42911fb9ee93ee12c4c8118b99be7649
+size 26920
diff --git a/marked/H/T-REC-H.812.1-201711-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/H/T-REC-H.812.1-201711-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..40b259cbaef2b6cfc60e3ef4eace4629df7656ba
--- /dev/null
+++ b/marked/H/T-REC-H.812.1-201711-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae8562c9dd5743a939c665c01757027e97386908f0377141b67f1bfa24f4ea7d
+size 44824
diff --git a/marked/H/T-REC-H.812.1-201711-I_PDF-E/2aa94b70ba3fadcba8420d9e3128253a_img.jpg b/marked/H/T-REC-H.812.1-201711-I_PDF-E/2aa94b70ba3fadcba8420d9e3128253a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a2a26df63d4661c9a7f837d66d77b5e9ebfcf349
--- /dev/null
+++ b/marked/H/T-REC-H.812.1-201711-I_PDF-E/2aa94b70ba3fadcba8420d9e3128253a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fba53020a193ae1019a16679f2d462ad52635b7c2a1c781d62f89fa8b88b6ddb
+size 9664
diff --git a/marked/H/T-REC-H.812.1-201711-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/H/T-REC-H.812.1-201711-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..526ff2f08e6e9efd33a32abd25568351b11a2cf4
--- /dev/null
+++ b/marked/H/T-REC-H.812.1-201711-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8729d5fab1dda3c05778e908245acb8459d69c400da607604627f60f8ea10df5
+size 54766
diff --git a/marked/H/T-REC-H.812.1-201711-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/H/T-REC-H.812.1-201711-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ea317709121d163fc3c9211c03dbce6150acfc3a
--- /dev/null
+++ b/marked/H/T-REC-H.812.1-201711-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eb3eabb73769ec482f0de58ff3e0a72bc202b5e275ffc7f40bfad5888b12ce45
+size 29040
diff --git a/marked/H/T-REC-H.812.1-201711-I_PDF-E/a48594f1a3fecef5e047a7c3a63b1220_img.jpg b/marked/H/T-REC-H.812.1-201711-I_PDF-E/a48594f1a3fecef5e047a7c3a63b1220_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b440494fd6673cd780b844bf838e9685277cb1ee
--- /dev/null
+++ b/marked/H/T-REC-H.812.1-201711-I_PDF-E/a48594f1a3fecef5e047a7c3a63b1220_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:baebd835a3700d711778d5938bf06b92f70ab0d3c9f7ef28a9f9aef3301a07de
+size 62684
diff --git a/marked/H/T-REC-H.812.1-201711-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/H/T-REC-H.812.1-201711-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..650c010f45b67e059af872ea593943263ed1c667
--- /dev/null
+++ b/marked/H/T-REC-H.812.1-201711-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d59e7638968e9e56fb0c7b3ce276275d89a04190a9ae78e9010e5dbffe8a63d
+size 48862
diff --git a/marked/H/T-REC-H.812.1-201711-I_PDF-E/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/marked/H/T-REC-H.812.1-201711-I_PDF-E/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b15e13174d64a520009bfcf1b874f750d0a75d5f
--- /dev/null
+++ b/marked/H/T-REC-H.812.1-201711-I_PDF-E/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eea161d535dccf7c8fecae19f631ebf6c25e5a804e423192d40b2533535e93e1
+size 49615
diff --git a/marked/H/T-REC-H.812.1-201711-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/H/T-REC-H.812.1-201711-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d14be82a052b5fa72d21c2381d3c72f0e0b2ec0c
--- /dev/null
+++ b/marked/H/T-REC-H.812.1-201711-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:abdb8e84696954f862bbc04f6ba80ed0919278d77e82a96d34e9e0d0ca34ab57
+size 80406
diff --git a/marked/H/T-REC-H.812.1-201711-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg b/marked/H/T-REC-H.812.1-201711-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..861d0156f58f5459f44b2fa89638df4540f1dabe
--- /dev/null
+++ b/marked/H/T-REC-H.812.1-201711-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0461020f6cf0ee0538c4fee6385447a463a5bf14b4b489534efc900166c40126
+size 63603
diff --git a/marked/H/T-REC-H.812.1-201711-I_PDF-E/raw.md b/marked/H/T-REC-H.812.1-201711-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..8372bd865cf39dee72b7d53b4457b6a2560e4daa
--- /dev/null
+++ b/marked/H/T-REC-H.812.1-201711-I_PDF-E/raw.md
@@ -0,0 +1,7381 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.812.1**
+
+(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:  
+Observation Upload capability**
+
+Recommendation ITU-T H.812.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                                               |                    |
+| <b>Personal health systems</b>                                                              | <b>H.810–H.819</b> |
+| 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.1
+
+# Interoperability design guidelines for personal connected health systems: Services interface: Observation Upload 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 additional design guidelines (DGs) that further clarify the underlying standards or specifications by reducing the options or by adding missing features to improve interoperability.
+
+ITU-T H.812.1 defines the additional design guidelines for the Observation Upload Certified Capability Class (CCC), whose function is to transfer an observation measurement from a medical device to a services application over the Services interface (Services-IF).
+
+ITU-T H.812.1 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 (this design guidelines document)
+- 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.1  | 2015-11-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/12654">11.1002/1000/12654</a> |
+| 2.0     | ITU-T H.812.1  | 2016-07-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12914">11.1002/1000/12914</a> |
+| 3.0     | ITU-T H.812.1  | 2017-11-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/13416">11.1002/1000/13416</a> |
+
+## Keywords
+
+CDG, Continua Design Guidelines, healthcare information systems, observation upload, personal connected health systems, personal health devices, services.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....                                         | xi |
+| 0.1   | Organization .....                                        | xi |
+| 0.2   | CCC guideline releases and versioning .....               | xi |
+| 0.3   | What's new.....                                           | xi |
+| 1     | Scope.....                                                | 1  |
+| 2     | References.....                                           | 1  |
+| 3     | Definitions .....                                         | 1  |
+| 4     | Abbreviations and acronyms .....                          | 1  |
+| 5     | Conventions .....                                         | 1  |
+| 6     | Observation Upload use case.....                          | 1  |
+| 6.1   | Observation Upload to the server .....                    | 1  |
+| 6.1.1 | Chosen standards and profiles.....                        | 2  |
+| 6.1.2 | Data payload.....                                         | 2  |
+| 6.1.3 | Services protocol (informative).....                      | 3  |
+| 7     | Behavioural models .....                                  | 3  |
+| 7.1   | SOAP implementation.....                                  | 3  |
+| 7.1.1 | Observation Upload using SOAP .....                       | 3  |
+| 7.2   | REST implementation .....                                 | 5  |
+| 7.2.1 | Capabilities exchange.....                                | 5  |
+| 7.2.2 | Observation Upload using hData .....                      | 7  |
+| 7.3   | Security .....                                            | 8  |
+| 7.3.1 | Secure point-to-point communication.....                  | 9  |
+| 7.3.2 | Auditing.....                                             | 10 |
+| 7.3.3 | Entity identity assertion.....                            | 10 |
+| 7.3.4 | Reliability .....                                         | 12 |
+| 8     | Implementation guidance (informative) .....               | 13 |
+| 8.1   | PHG conceptual model.....                                 | 13 |
+| 8.2   | Overview of operation .....                               | 14 |
+| 8.3   | Certified Capability Classes for Observation Upload ..... | 15 |
+| 8.4   | Sample service description SOAP .....                     | 17 |
+| 8.5   | Device observation consumer WSDL .....                    | 17 |
+| 8.6   | Device observation consumer XSD.....                      | 18 |
+| 8.7   | Messaging examples.....                                   | 18 |
+| 8.8   | Communicate PCD data .....                                | 19 |
+
+###### **Page**
+
+|        |                                                                                     |    |
+|--------|-------------------------------------------------------------------------------------|----|
+| 8.9    | Communicate PCD data response .....                                                 | 19 |
+| 8.10   | CommunicatePCDDData example with security .....                                     | 20 |
+| 8.10.1 | STS request .....                                                                   | 20 |
+| 8.10.2 | STS response .....                                                                  | 21 |
+| 8.10.3 | CommunicatePCDDData request.....                                                    | 24 |
+| 8.10.4 | CommunicatePCDDData response .....                                                  | 25 |
+| 8.11   | hData Observation Upload example.....                                               | 25 |
+| 9      | The PCD-01 document payload.....                                                    | 27 |
+| 9.1    | PCD-01 fundamentals .....                                                           | 27 |
+| 9.1.1  | MSH header.....                                                                     | 28 |
+| 9.1.2  | PID patient info .....                                                              | 28 |
+| 9.1.3  | OBR observation request .....                                                       | 28 |
+| 9.1.4  | OBX observation result.....                                                         | 28 |
+| 9.2    | Document structure .....                                                            | 29 |
+| 9.3    | PHG, MDS and metric OBXes.....                                                      | 30 |
+| 9.4    | Segment structure .....                                                             | 31 |
+| 9.5    | PCD-01 format "on the wire" .....                                                   | 34 |
+| 9.6    | HL7 data types.....                                                                 | 34 |
+| 9.7    | PID segment .....                                                                   | 35 |
+| 10     | OBX segment fundamentals .....                                                      | 36 |
+| 10.1   | Encoding OBX segments .....                                                         | 36 |
+| 10.2   | Object hierarchy .....                                                              | 37 |
+| 10.2.1 | Hierarchy levels.....                                                               | 37 |
+| 10.2.2 | Hierarchy examples .....                                                            | 38 |
+| 10.2.3 | Object hierarchy for compounds .....                                                | 39 |
+| 10.3   | Timestamping .....                                                                  | 39 |
+| 10.4   | The coincident timestamp pair .....                                                 | 41 |
+| 10.5   | PHG-OBXes .....                                                                     | 42 |
+| 10.6   | MDS-OBXes .....                                                                     | 43 |
+| 10.7   | Metric OBXes.....                                                                   | 44 |
+| 10.7.1 | Mapping the 11073 observational attributes in OBX-5 and data type<br>in OBX-2 ..... | 45 |
+| 10.8   | Date-Time-Adjustment.....                                                           | 46 |
+| 11     | Guidelines .....                                                                    | 46 |
+| 11.1   | MSH .....                                                                           | 46 |
+| 11.2   | PID.....                                                                            | 46 |
+| 11.3   | OBR.....                                                                            | 46 |
+| 11.4   | OBX.....                                                                            | 46 |
+
+|                                                                                                 |     |
+|-------------------------------------------------------------------------------------------------|-----|
+| Annex A Normative guidelines for common aspects .....                                           | 48  |
+| Annex B Normative guidelines for hData.....                                                     | 49  |
+| Annex C Normative guidelines for SOAP .....                                                     | 51  |
+| Annex D Normative guidelines data payload .....                                                 | 53  |
+| D.0 Mapping from [ISO/IEEE 11073-20601]to the Continua services .....                           | 55  |
+| D.0.1 Terminologies and conventions.....                                                        | 55  |
+| D.0.2 Protocol-dependent information .....                                                      | 55  |
+| D.0.3 Services-specific nomenclature .....                                                      | 56  |
+| D.0.4 ISO/IEEE 11073-20601 general object/attribute mapping.....                                | 56  |
+| D.1 OBX encoding guidelines.....                                                                | 59  |
+| D.1.1 Guidelines for encoding the PHG-OBX segments.....                                         | 59  |
+| D.1.2 Guidelines for encoding the MDS-OBX segments .....                                        | 64  |
+| D.1.3 Guidelines for encoding the Metric-OBX segments .....                                     | 76  |
+| D.1.4 Special situations .....                                                                  | 94  |
+| D.1.5 Timestamping and time synchronization.....                                                | 98  |
+| D.1.6 Metric object attribute mappings overview .....                                           | 109 |
+| D.1.7 Numeric (subclass of Metric) .....                                                        | 110 |
+| D.1.8 RT-SA (subclass of Metric).....                                                           | 110 |
+| D.1.9 Enumeration (subclass of Metric) .....                                                    | 110 |
+| Annex E Mapping from the IEEE 11073-104xx device specializations to the Continua services ..... | 111 |
+| E.1 PHG.....                                                                                    | 112 |
+| E.1.1 Modelling .....                                                                           | 112 |
+| E.1.2 Containment tree .....                                                                    | 112 |
+| E.2 MDS object .....                                                                            | 113 |
+| E.2.1 Modelling .....                                                                           | 113 |
+| E.2.2 Containment tree .....                                                                    | 113 |
+| E.3 Metric OBXes .....                                                                          | 115 |
+| E.3.1 10404 Pulse oximeter.....                                                                 | 115 |
+| E.3.2 10407 Blood pressure monitor .....                                                        | 121 |
+| E.3.3 10408 Thermometer .....                                                                   | 123 |
+| E.3.4 10415 Weighing scales .....                                                               | 124 |
+| E.3.5 10417 Glucose meter .....                                                                 | 126 |
+| E.3.6 10418 INR meter.....                                                                      | 134 |
+| E.3.7 10441 Cardiovascular fitness and activity monitor .....                                   | 136 |
+| E.3.8 10442 Strength fitness equipment.....                                                     | 153 |
+| E.3.9 10471 Independent living activity hub .....                                               | 157 |
+
+|                                                                    | Page |
+|--------------------------------------------------------------------|------|
+| E.3.10 10472 Adherence monitor.....                                | 168  |
+| E.3.11 10421 Peak expiratory flow monitor .....                    | 171  |
+| E.3.12 10420 Body composition analyser.....                        | 174  |
+| E.3.13 IEEE 10406 basic 1-3 lead ECG.....                          | 176  |
+| E.3.14 10424 Sleep apnoea breathing therapy equipment (SABTE)..... | 180  |
+| E.3.15 ISO/IEEE 11073-10425 continuous glucose monitor.....        | 196  |
+| E.4 HL7 Unsolicited observation result.....                        | 203  |
+| E.4.1 MSH.....                                                     | 203  |
+| E.4.2 PID .....                                                    | 206  |
+| E.4.3 OBR .....                                                    | 208  |
+| E.4.4 OBX.....                                                     | 210  |
+| E.4.5 PV1 .....                                                    | 212  |
+| E.4.6 NTE.....                                                     | 213  |
+| E.4.7 TQ1 .....                                                    | 213  |
+| E.4.8 MSA.....                                                     | 213  |
+| E.4.9 ERR.....                                                     | 214  |
+| E.4.10 HL7 v2.6 error tables .....                                 | 215  |
+| E.5 HL7 Data types – Observations .....                            | 216  |
+| E.5.1 CWE.....                                                     | 217  |
+| E.5.2 DTM.....                                                     | 218  |
+| E.5.3 NM .....                                                     | 218  |
+| E.5.4 ST218 .....                                                  |      |
+| E.5.5 NA - numeric array .....                                     | 218  |
+| E.5.6 XAD .....                                                    | 219  |
+| E.5.7 XPN.....                                                     | 220  |
+| E.6 Other HL7 data types .....                                     | 221  |
+| E.6.1 CX.....                                                      | 221  |
+| E.6.2 ID coded value for HL7 defined tables.....                   | 222  |
+| E.6.3 IS coded value for user-defined tables.....                  | 223  |
+| E.6.4 SI sequence ID .....                                         | 223  |
+| E.6.5 SN structured numeric .....                                  | 223  |
+| E.6.6 XTN .....                                                    | 224  |
+| E.7 HL7 control characters .....                                   | 226  |
+| Bibliography.....                                                  | 227  |
+
+# List of Tables
+
+|                                                                                                                              | Page |
+|------------------------------------------------------------------------------------------------------------------------------|------|
+| Table 8-1 – Certified Capability Classes .....                                                                               | 15   |
+| Table 8-2 – Guidelines for Certified Capability Classes .....                                                                | 15   |
+| Table 9-1 – Simplified PCD-01 table .....                                                                                    | 30   |
+| Table 10-1 – MDS-OBX attributes .....                                                                                        | 44   |
+| Table A.1 – Guidelines for all CCC classes.....                                                                              | 48   |
+| Table A.2 – Observation Upload guidelines for a PHG application.....                                                         | 48   |
+| Table A.3 – Observation Upload guidelines for a services application.....                                                    | 48   |
+| Table B.1 – Observation Upload guidelines for a PHG application using hData.....                                             | 49   |
+| Table B.2 – Observation Upload guidelines for a services application using hData.....                                        | 50   |
+| Table C.1 – Common Observation Upload guidelines using SOAP .....                                                            | 51   |
+| Table C.2 – Observation Upload guidelines for a PHG using SOAP .....                                                         | 52   |
+| Table C.3 – Observation Upload guidelines for a Health & Fitness service using SOAP .....                                    | 52   |
+| Table D.1 – Observation Upload general data payload guidelines.....                                                          | 53   |
+| Table D.2 – Continua services regulation nomenclature codes .....                                                            | 56   |
+| Table D.3 – Continua services PHG production specifications nomenclature codes .....                                         | 63   |
+| Table D.4 – Continua services sensor production specification nomenclature codes .....                                       | 66   |
+| Table D.5 – Primary observational metric attributes .....                                                                    | 77   |
+| Table D.6 – Timestamp cases .....                                                                                            | 84   |
+| Table D.7 – OBX-8 status values.....                                                                                         | 89   |
+| Table D.8 – Measurement status values.....                                                                                   | 90   |
+| Table D.9 – Special data types.....                                                                                          | 91   |
+| Table D.10 – Example blood pressure .....                                                                                    | 93   |
+| Table D.11 – Example AMM feedback .....                                                                                      | 93   |
+| Table D.12 – Bluetooth LE temperature location codes .....                                                                   | 96   |
+| Table D.13 – Qualified time timestamp examples.....                                                                          | 99   |
+| Table D.14 – PHG time elements .....                                                                                         | 100  |
+| Table D.15 – Sensor time elements .....                                                                                      | 101  |
+| Table D.16 – PHG and sensor timestamps .....                                                                                 | 103  |
+| Table D.17 – PHG time behaviours .....                                                                                       | 104  |
+| Table D.18 – HL7 user table for OBX-18-2 .....                                                                               | 106  |
+| Table D.19 – Time synchronization nomenclature codes .....                                                                   | 106  |
+| Table D.20 – Generic metric attributes .....                                                                                 | 109  |
+| Table D.21 – Numeric (subclass of metric) .....                                                                              | 110  |
+| Table D.22 – RT-SA (subclass of metric).....                                                                                 | 110  |
+| Table D.23 – Enumeration (subclass of metric) .....                                                                          | 110  |
+| Table E.1 – Continua-defined MDC codes that are not part of ISO/IEEE 11073-20601 Personal Health Devices data exchanges..... | 111  |
+
+|                                                                                  |     |
+|----------------------------------------------------------------------------------|-----|
+| Table E.2 – PHG containment tree .....                                           | 112 |
+| Table E.3 – MDS containment tree.....                                            | 113 |
+| Table E.4 – Pulse oximeter containment tree .....                                | 115 |
+| Table E.5 – Pulse oximeter OBX encoding – Part 1 .....                           | 117 |
+| Table E.6 – Pulse oximeter OBX encoding – Part 2.....                            | 120 |
+| Table E.7 – Blood pressure monitor containment tree.....                         | 121 |
+| Table E.8 – Blood pressure monitor encoding – Part 1 .....                       | 122 |
+| Table E.9 – Blood pressure monitor encoding – Part 2 .....                       | 122 |
+| Table E.10 – Thermometer containment tree.....                                   | 123 |
+| Table E.11 – Thermometer encoding – Part 1 .....                                 | 124 |
+| Table E.12 – Thermometer encoding – Part 2 .....                                 | 124 |
+| Table E.13 – Weighing scales containment tree .....                              | 125 |
+| Table E.14 – Weighing scales encoding – Part 1 .....                             | 125 |
+| Table E.15 – Weighing scales encoding – Part 2.....                              | 126 |
+| Table E.16 – Glucose meter containment tree .....                                | 126 |
+| Table E.17 – Glucose meter encoding – Part 1 .....                               | 129 |
+| Table E.18 – Glucose meter encoding – part 2 .....                               | 133 |
+| Table E.19 – INR meter containment tree .....                                    | 134 |
+| Table E.20 – INR meter encoding – Part 1 .....                                   | 135 |
+| Table E.21 – INR meter encoding – Part 2 .....                                   | 135 |
+| Table E.22 – Cardiovascular fitness and activity monitor containment tree .....  | 136 |
+| Table E.23 – Cardiovascular fitness and activity monitor encoding – Part 1 ..... | 140 |
+| Table E.24 – Cardiovascular fitness and activity monitor encoding – Part 2 ..... | 146 |
+| Table E.25 – Strength fitness equipment containment tree .....                   | 153 |
+| Table E.26 – Strength fitness equipment encoding – Part 1 .....                  | 154 |
+| Table E.27 – Strength fitness equipment encoding – Part 2 .....                  | 156 |
+| Table E.28 – Independent living activity hub containment tree .....              | 158 |
+| Table E.29 – Independent living activity hub encoding – Part 1 .....             | 159 |
+| Table E.30 – Independent living activity hub encoding – Part 2 .....             | 167 |
+| Table E.31 – Adherence monitor containment tree .....                            | 169 |
+| Table E.32 – Adherence monitor encoding – Part 1 .....                           | 169 |
+| Table E.33 – Adherence monitor encoding – Part 2 .....                           | 170 |
+| Table E.34 – Peak expiratory flow containment tree.....                          | 172 |
+| Table E.35 – Peak expiratory flow monitor encoding – Part 1 .....                | 172 |
+| Table E.36 – Peak expiratory flow monitor encoding – Part 2 .....                | 173 |
+| Table E.37 – Body composition analyser containment tree.....                     | 175 |
+| Table E.38 – Body composition analyser OBX encoding – Part 1 .....               | 175 |
+
+|                                                                                             |     |
+|---------------------------------------------------------------------------------------------|-----|
+| Table E.39 – Body composition analyser OBX encoding – Part 2 .....                          | 176 |
+| Table E.40 – Basic 1-3 lead ECG containment tree .....                                      | 177 |
+| Table E.41 – Basic 1-3 lead ECG OBX encoding – Part 1 .....                                 | 178 |
+| Table E.42 – Basic 1-3 lead ECG OBX encoding – Part 2 .....                                 | 180 |
+| Table E.43 – Sleep apnoea breathing therapy equipment (SABTE) containment tree .....        | 181 |
+| Table E.44 – Sleep apnoea breathing therapy equipment (SABTE) OBX encoding – Part 1 .....   | 184 |
+| Table E.45 – Sleep apnoea breathing therapy equipment (SABTE) OBX encoding – Part 2 .....   | 194 |
+| Table E.46 – Continuous glucose monitor containment tree .....                              | 197 |
+| Table E.47 – Continuous glucose monitor encoding – Part 1 .....                             | 198 |
+| Table E.48 – Insulin pump encoding – Part 2 .....                                           | 201 |
+| Table E.49 – Message header segment .....                                                   | 203 |
+| Table E.50 – Patient identification segment .....                                           | 206 |
+| Table E.51 – Observation request segment .....                                              | 208 |
+| Table E.52 – Single observation segment .....                                               | 210 |
+| Table E.53 – Note segment .....                                                             | 213 |
+| Table E.54 – Message acknowledgement segment .....                                          | 213 |
+| Table E.55 – Error segment .....                                                            | 214 |
+| Table E.56 – HL7 Table 0357 – Message error condition code .....                            | 215 |
+| Table E.57 – HL7 Table 0516 – Error severity .....                                          | 216 |
+| Table E.58 – HL7 data types used in OBX-2 .....                                             | 216 |
+| Table E.59 – CWE .....                                                                      | 217 |
+| Table E.60 – HL7 component table – numeric array .....                                      | 218 |
+| Table E.61 – XAD .....                                                                      | 219 |
+| Table E.62 – XPN .....                                                                      | 220 |
+| Table E.63 – CX .....                                                                       | 221 |
+| Table E.64 – Entity identifier .....                                                        | 222 |
+| Table E.65 – HL7 Component table – ID string datacoded value for HL7 defined tables .....   | 223 |
+| Table E.66 – HL7 component table – IS coded value for user-defined tables string data ..... | 223 |
+| Table E.67 – HL7 component table – SI sequence ID .....                                     | 223 |
+| Table E.68 – HL7 component table – SN structured numeric .....                              | 224 |
+| Table E.69 – XTN .....                                                                      | 225 |
+| Table E.70 – HL7 v2.6 delimiter values .....                                                | 226 |
+
+## List of Figures
+
+### Page
+
+|                                                                                                    |     |
+|----------------------------------------------------------------------------------------------------|-----|
+| Figure 7-1 – Communicate PCD data .....                                                            | 5   |
+| Figure 7-2 – Capability elements for applications supporting hData Observation Uploads .....       | 6   |
+| Figure 7-3 – Capability elements for applications supporting an OAuth 2.0 authentication service . | 6   |
+| Figure 7-4 – Capability elements for applications supporting SOAP Observation Uploads .....        | 7   |
+| Figure 7-5 – Capability elements for applications supporting WS-Trust SAML token service .....     | 7   |
+| Figure 7-6 – hData Observation Upload .....                                                        | 8   |
+| Figure 7-7 – Secure point-to-point communication sequence .....                                    | 9   |
+| Figure 7-8 – Auditing sequence .....                                                               | 10  |
+| Figure 7-9 – Entity identity assertion sequence .....                                              | 11  |
+| Figure 7-10 – WS-RM sequence creation .....                                                        | 13  |
+| Figure 8-1 – PHG block diagram .....                                                               | 15  |
+| Figure 8-2 – Identification and identity cross-referencing interactions .....                      | 17  |
+| Figure 10-1 – Containment hierarchy .....                                                          | 37  |
+| Figure D-1 – PHG and sensor time accuracy selection .....                                          | 105 |
+
+## 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 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 design guidelines for the Observation Upload Certified Capability Class (CCC), whose function is to transfer an observation measurement from the Personal Health Gateway (PHG) to a Health & Fitness application over the Services interface (Services-IF).
+
+This design guidelines document is part of the [ITU-T H.810] subseries "H.810 interoperability design guidelines for personal health systems". 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 overview 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 provides 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 Observation Upload CCC.
+
+**Clause 9: PCD-01 background** – This clause provides an informative description of the PCD-01 document.
+
+**Clause 10: OBX segment fundamentals** – This clause provides background information on generating OBX segments from IEEE 11073-20601 data.
+
+**Clause 11: Guidelines** – This clause provides guidelines for creating a PCD-01 document.
+
+### 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.1
+
+### Interoperability design guidelines for personal connected health systems: Services interface: Observation Upload capability
+
+#### 1 Scope
+
+This design guidelines document defines the design guidelines for the Observation Upload CCCs which are designed to allow the transfer of an observation measurement from a PHG to a services application over the Services interface (Services-IF) in a secure and interoperable way.
+
+#### 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 Observation Upload use case
+
+The Observation Upload use case is focused on the needs identified for transferring patient observation measurements to a server.
+
+Observation Upload can be achieved using either of two methods defined in clause 7 of this design guideline; the choice of which method to use is left to the implementer.
+
+##### 6.1 Observation Upload to the server
+
+Angus has decided that he wishes to improve his general fitness levels after a check-up with his General Practitioner showed that he was becoming overweight and that this could impact his long term health. After some research he decides to sign up to an online service that allows him to use his current smartphone and some additional devices to monitor many of his physical activities.
+
+Initially he tracks his cycle rides using an application on his smartphone which in turn uploads the data collected to the online service.
+
+Angus is also tracking his weight and heart rate using Continua devices that allow him to upload his weight and standing heart rate, both pre and post activity to his service provider that hosts the web application where all his daily measurements are stored.
+
+Having these measurements hosted on a website allows him to track progress over time, share highlights with his social circle and compete against friends.
+
+### **6.1.1 Chosen standards and profiles**
+
+The Continua Services interface (Services-IF) defines a set of interoperable message exchanges between a Services observation sender device and a Services observation receiver. From a high level perspective, these guidelines describe protocol transactions by characterizing the protocol exchange framework and the format of the contained information. The protocol exchange framework describes the required protocol stack and security mechanisms that are used to exchange the data of the protocol.
+
+Devices implementing the Services-IF using SOAP must use the transport guidelines found in Appendix V of [IHE ITI-TF-2] and devices using hData must use guidelines found in clause 7.2 as the message exchange framework, formatting the contained information in accordance with the IHE PCD-01 transaction of the IHE device to the enterprise communication profile in the IHE patient care devices technical framework.
+
+### **6.1.2 Data payload**
+
+The information contained in the data payload must be formatted in accordance with the IHE PCD-01 transaction: Communicate PCD Data. The patient care device (PCD) technical framework constrains the use of HL7 V2.6 messages, requiring that observations be exchanged using the unsolicited observation result message (ORU^R01^ORU\_R01).
+
+The choice of adopting the IHE PCD-01 transaction was motivated by a number of considerations:
+
+The PCD-01 transaction allows the use of common nomenclature, defined by the ISO/IEEE 11073 committee, for all devices. Continued use of this nomenclature over the Services interface simplifies the operation of the PHG, as it is unnecessary to maintain accurate and up to date code translation tables on the PHG. All observation identifiers are based on the terms in [ISO/IEEE 11073-20601], [IEEE 11073-20601A] and the related X73 documents.
+
+Continua addresses the needs of three distinct market segments in remote health monitoring; Health & Fitness, ageing independently and disease management. The form in which data is represented over the Services interface had to be inclusive of Personal Health Devices that are used in each of these market segments. Given the IHE patient care device team's existing work of mapping X73 devices to HL7 observation result messages and some initial groundwork by the Continua Services interface sub-team, it was deemed that the PCD-01 transaction is capable of supporting Personal Health Devices for all three market segments. Furthermore, the PCD-01 transaction is based on HL7 V2.6 [HL7 2.6] and has been shown to be effective in the clinical environment, providing strong evidence that it will be capable of supporting additional Continua use cases and devices in the future.
+
+The PCD-01 transaction has an existing user base and the IHE PCD domain is actively working to validate interoperability based on compliance with this transaction, as well as defining new profiles for related use cases.
+
+The PCD-01 unsolicited observation result provides a well-defined, self-contained message uniform for transmitting one or more observations enabling less stateful message exchange between the Services observation sender and receiver which improves scalability.
+
+HL7 V2.6 messages are supported by the HL7 Messaging Workbench and National Institute of Standards and Technology (NIST) test tooling found under Tools at <https://hl7v2tools.nist.gov/portal>.
+
+One of the motivations for using the HL7 V2.6 messaging structure as opposed to the HL7 V3.0 data representations was the reduction in bandwidth achieved with the more compact HL7 V2.6 messaging structure.
+
+### 6.1.3 Services protocol (informative)
+
+The Continua Services interface (Services-IF) consists of data payload and message exchange framework protocols that are designed to operate across a wide area network. In particular, the Continua Services interface is specified to run over standard private and public TCP/IP networks, such as the Internet. The Continua Services interface does not offer guidelines on the physical, data link or network layers of this network, but does provide detailed guidance on the transport, presentation and application to be used for interoperable communications. There may be specific performance criteria for the underlying network layers, such as message delivery latency, message error rates and message delivery reliability that affect the robust operation of the Continua Services interface that must be taken into account through system-level design. Mechanisms for assurance that such minimum network performance metrics are obtained in any given implementation are beyond the scope of this design guideline and are well documented within networking literature.
+
+## 7 Behavioural models
+
+The following exchange mechanisms are specified for the Observation Upload service:
+
+- Create a new observation measurement on the uploader using SOAP.
+- Create a new observation measurement on the uploader using hData.
+
+The Services interface requires that all connections be initiated from the services sender device for the Observation Upload CCC. The services Observation Upload sender and receiver are required to use transport level security (TLS) for point to point content security. Whether or not the services Observation Upload receiver additionally requires mutual certificate validation in the TLS handshake is up to policy. The services Observation Upload sender is also required to provide an indication that it has been authenticated and that it is authorized to perform this transaction. In the SOAP case, this indication is an SAML 2.0 token and for hData an OAuth 2.0 Bearer token. How the services Observation Upload sender obtains these tokens is not specified by Continua. It depends upon the trust relationship established between the parties. The services Observation Upload receiver 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 services Observation Upload receiver may support both if it supports both hData and SOAP uploads. In either of these cases an out-of-band operation must take place where the user of the services Observation Upload sender establishes some type of account on the receiver allowing the client to obtain these tokens. The observation receiver token service generates these tokens customized for the recipient which it can validate when it receives the upload. On the other hand, the services Observation Upload receiver may require that these tokens be obtained from a third party authorization service (such as a certification authority) with which the services Observation Upload receiver has established a trust relationship. In this case the services Observation Upload receiver is letting the third party authorization service do the leg work of authenticating the client. The services observation receiver may then choose to accept any token that comes from this third party service or it may additionally choose to pass the received token to this service for confirmation before acceptance. The trust relationship details are determined by policy but in all cases Continua requires that Observation Uploads are point to point secure and that the client indicates that it has been authenticated and is thereby authorized to perform the transaction.
+
+## 7.1 SOAP implementation
+
+### 7.1.1 Observation Upload using SOAP
+
+The Continua Services interface uses a web service transport layer defined in Appendix V of [IHE ITI-TF-2], which specifies the usage of SOAP 1.2 over HTTP version 1.1 and otherwise conforms to the Web Services Interoperability Organization's Basic Profile Version 1.1
+
+[OASIS/WS-I BP] and Basic Security Profile 1.0 [OASIS/WS-I BSP]. The services message exchange framework further specifies conformance to the Reliable Secure Profile [WS-I RSP] to constrain the optional use of additional web service standards.
+
+This message exchange framework is motivated by the availability of client and server implementations and a need to ensure the scalability of services observation receiver devices. It was further impacted by a number of additional considerations:
+
+- the desire to have a capable and comprehensive security architecture that is well understood;
+  - The WS-I Basic Security Profile has undergone significant industry vetting and provides the flexibility needed to support both a simple secure tunnel as well as more involved security models.
+- the need to operate across firewalls when the services observation sender device and services observation receiver device are in different administrative domains of control;
+- the need to support a reliable connection over multiple instances of a transport connection which spans both the time domain, as well as cooperating software layers and modules in a back-end service environment;
+  - Using [OASIS WS-I BSP] as a base allows for the accommodation of these concerns through the additional use of the WS-ReliableMessaging and WS-MakeConnection web service standards.
+
+The transport portion of the Continua Services interface (Services-IF) is based on a set of web service standards defined by IETF, W3C and OASIS as profiled by the IHE IT infrastructure technical framework, the WS-I Basic Security Profile and SAML 2.0 for authentication.
+
+Appendix V of [IHE ITI-TF-2] defines a set of interoperability rules and guidance to defining a request-response web services contract that is based on the DEC profile actors defined in the IHE PCD technical framework.
+
+This contract can be expressed via the web services description language (WSDL), and is provided as an informative implementation artefact in clause 8.5. Together with the rules defined in Appendix V of [IHE ITI-TF-2], this service contract can be used to create consistent and interoperable messages which contain the core PCD-01 transaction payloads. For a sample request/response message, please see clauses 8.8 and 8.10. Figure 7-1 shows the sequence diagram for the communicate PCD data transaction.
+
+At a minimum, a certified Continua services observation sender device must implement the device enterprise communications (DEC) device observation reporter actor and be capable of delivering PCD-01 observation result messages that conform to the data and messaging guidelines defined in the Annexes. Similarly, a certified Continua services observation receiver device must implement the DEC device observation consumer actor and conform to the services observation receiver related guidelines/constraints.
+
+Due to the importance of controlling network traffic, it is strongly encouraged that a PHG allows for a mechanism for controlling the frequency of measurement upload.
+
+![Sequence diagram showing communication between a Services observation sender device and a Services observation receiver device. The sender sends a PCD-01 message (unsolicited observation result) to the receiver, and the receiver responds with a PCD data response (general acknowledgement).](9c6461e1e94afae4dec455e69a2ce152_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Sender as Services observation sender device
+    participant Receiver as Services observation receiver device
+    Note left of Sender: 
+    Sender->>Receiver: PCD-01: Communicate PCD data unsolicited observation result
+    Note right of Receiver: 
+    Receiver-->>Sender: Communicate PCD data response general acknowledgement
+    Note right of Receiver: H.812.1(16)_F7-1
+  
+```
+
+Sequence diagram showing communication between a Services observation sender device and a Services observation receiver device. The sender sends a PCD-01 message (unsolicited observation result) to the receiver, and the receiver responds with a PCD data response (general acknowledgement).
+
+**Figure 7-1 – Communicate PCD data**
+
+Using this web services profile as a base, it is possible to layer on additional standards such as those developed in the Organization for the Advancement of Structured Information Standards (OASIS) in order to support enhanced qualities of service, including secure and reliable communication patterns which are required and/or are beneficial in specific scenarios. In order to support these functions in a consistent manner, services observation sender and receiver devices must conform to the constraints upon these standards that are found within the WS-I Basic Security Profile (BSP) v1.0 interoperability profile and the WS-ReliableMessaging v1.1 standard. These additional concerns are covered in clauses 7.3 and 7.3.4, respectively.
+
+## 7.2 REST implementation
+
+### 7.2.1 Capabilities exchange
+
+Observation Upload receivers and senders using hData are required to support capabilities exchange. For Observation Upload receivers and senders using SOAP only supporting this feature is optional. Observation Upload receivers supporting capability exchange must provide a root.xml containing its capabilities as specified in Figure 7-2. Observation Upload senders supporting capability exchange are not required to provide a root.xml though they are allowed to do so. When a root.xml is provided by an application, its capabilities are indicated in the root.xml by including xml elements as shown in Figure 7-2.
+
+The primary purpose of the exchange is to allow PHG applications to discover what capability classes the receiver supports. The capability elements also often provide a URL 'starting point'; for example, where to POST the PCD-01 document for Observation Upload capability classes or where to POST the PHG components of the APB resource in APS establishment for APS capability classes. However, beyond this URL 'starting point', there is no further information about the capability class features provided in these capability elements. For example, what type of shoulder tap method might be supported in the APS is not present; one has to engage in APS establishment to obtain that information.
+
+Figure 7-2 shows the capability elements for Observation Upload applications supporting hData. Note that PHG applications that choose to provide a root.xml will leave the <path> element empty as this element specifies where to POST the PCD-01 document and is only valid for receivers.
+
+Figure 7-3 shows the capability elements for Observation Upload applications supporting an OAuth authentication server. Inclusion of these elements is optional even if the application supports an authentication server.
+
+Figure 7-4 shows the capability elements for exposing SOAP-based Observation Uploads. Inclusion of these elements is optional even if the application supports additional device classes using hData.
+
+Figure 7-5 shows the capability elements for applications that support a security assertion markup language (SAML) token service using WS-Trust. At this time only the Security Token Service (STS) UserName and STS X509 service types are denoted in these elements. Inclusion of these elements is optional even if the application supports additional capability classes using hData.
+
+The presence of any of the capability elements in Figure 7-3 to Figure 7-5 is optional in all cases. The advantage of including them is that it reduces the out-of-band activity required to configure an Observation Upload client.
+
+```
+<profile>
+  <!-- Specified value -->
+  <id>observation-upload-hData</id>
+  <reference>
+    http:// handle.itu.int/11.1002/3000/hData/Upload/2017/01/H.812.1.pdf
+  </reference>
+</profile>
+<section>
+  <!-- chosen by the HFS; empty on PHG -->
+  <path>path/to/payload/post for hData</path>
+  <profileID>observation-upload-hData</profileID>
+  <resourceTypeID>observation</resourceTypeID>
+</section>
+<resourceType>
+  <resourceTypeID>observation</resourceTypeID>
+  <!-- location of reference that describes the Observation upload standard -->
+  <reference>
+    http://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_TF_Vol2.pdf
+  </reference>
+  <representation>
+    <mediaType>application/txt</mediaType>
+    <!-- Schema for the resource -->
+  </representation>
+</resourceType>
+```
+
+**Figure 7-2 – Capability elements for applications supporting hData Observation Uploads**
+
+```
+<profile>
+  <!-- Specified value -->
+  <id>oAUTH</id>
+  <reference>
+    http://handle.itu.int/11.1002/3000/hData/Upload/2017/01/H.812.1.pdf
+  </reference>
+</profile>
+<section>
+  <!-- chosen by the HFS; empty on PHG -->
+  <path>path/to/post for oAUTH token</path>
+  <profileID>oAUTH</profileID>
+</section>
+<resourceType>
+  <resourceTypeID>oAUTH-Bearer</resourceTypeID>
+  <!-- location of reference that describes the Observation upload standard -->
+  <reference>
+    http://tools.ietf.org/html/rfc6750
+  </reference>
+  <representation>
+    <mediaType>application/json</mediaType>
+
+  </representation>
+</resourceType>
+```
+
+**Figure 7-3 – Capability elements for applications supporting an OAuth 2.0 authentication service**
+
+```
+
+<profile>
+  <!-- Specified value -->
+  <id>observation-upload-SOAP</id>
+  <reference>
+    http://handle.itu.int/11.1002/3000/hData/Upload/2017/01/H.812.1.pdf
+  </reference>
+</profile>
+<section>
+  <!-- chosen by the HFS; empty on PHG -->
+  <path>path/to/CommunicatePCDDData</path>
+  <profileID>observation-upload-SOAP</profileID>
+</section>
+
+```
+
+**Figure 7-4 – Capability elements for applications supporting SOAP Observation Uploads**
+
+```
+
+<profile>
+  <!-- Specified value -->
+  <id>STS-Username/STS-X509</id>
+  <reference>
+    http://handle.itu.int/11.1002/3000/hData/Upload/2017/01/H.812.1.pdf
+  </reference>
+</profile>
+<section>
+  <!-- chosen by the HFS; empty on PHG -->
+  <path>path/to/STS-Username or STS-X509 service</path>
+  <profileID>STS-Username/STS-X509</profileID>
+</section>
+
+```
+
+**Figure 7-5 – Capability elements for applications supporting WS-Trust SAML token service**
+
+The capability exchange involves the observation sender device invoking a REST GET transaction to a resource location specified by the capability exchange specification [ITU-T H.812.3]. The transaction requires as a minimum a server certificate validation on the client side TLS but requires no authentication token. The response contains the root.xml of the observation receiver. The observation sender may, if it so desires, invoke a REST POST transaction to the same URL as the GET of the server's root.xml. In this case the transaction does require an authentication token. The server returns a resource locator where the observation sender can access the POSTed document or a code indicating that the transaction is not supported.
+
+Even SOAP-only observation senders can benefit from this transaction by providing the URLs to the respective SOAP service resources so that the only out-of-band action necessary for client configuration is entry of the base URL.
+
+## 7.2.2 Observation Upload using hData
+
+Observation Upload using hData, as shown in Figure 7-6, uses the hData framework standard [HL7 V3 HRF] coupled with the hData REST transport binding standard [OMG/hData RESTful Trans]. These two documents in turn rely on HTTPS and the Internet Standard HTTP and TCP/IP protocol stacks. Observation Upload using REST requires implementation of the hData Content Profile Document for Observation Upload (<http://handle.itu.int/11.1002/3000/hData/Upload/2017/01/H.812.1.pdf>), which contains narrative text and an XML schema, that defines the specific encoding of the mandatory and optional elements of the hData framework that are to be used for Observation Upload.
+
+The REST interface is intended to support a range of use cases from informal health, wellness, fitness and social engagement applications to simple clinical applications. The REST style of HTTP(S) web Services interface is prevalent in consumer Internet applications, such as those routinely found on smartphone and tablet platforms such as iOS and Android. REST web services are increasingly being used in the healthcare domain, as several projects in HL7 (Health Level 7 International, 2013) and IHE (Integrating the Healthcare Enterprise, 2013) demonstrate.
+
+The RESTful resource-oriented model for web services is very simple. Every resource is labelled by a distinct URI and all resources are operated upon by the basic HTTP verbs, GET, POST, PUT, DELETE, etc. The content of the resources is carried in the body of an HTTP message, perhaps URL-encoded for "safe passage" through the Internet. Basic security is provided by using TLS encryption (HTTPS) and authentication is provided by the inclusion of the HTTP Authorize header in each message.
+
+![Sequence diagram for hData Observation Upload showing interactions between a patient, PHG application, authorization server, and service application.](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg)
+
+The diagram illustrates the sequence of interactions for an hData Observation Upload. It features four main entities: Resource owner (patient), Public-client user agent, Authorization server, and Resource server. The Resource owner is shown as being 'Out of scope'. The Public-client user agent is part of a 'PHG application', and the Authorization server and Resource server are part of a 'Service application'. The sequence of messages is as follows:
+ 
+
+- The Resource owner (patient) sends 'Resource owner credentials' to the Public-client user agent.
+- The Public-client user agent then sends 'Resource owner credentials' to the Authorization server.
+- The Authorization server responds with an 'Access token (type = bearer)' to the Public-client user agent.
+- The Public-client user agent sends an 'HTTP POST of PCD-01 document [includes access token]' to the Resource server.
+- The Resource server responds with a 'Response to POST' to the Public-client user agent.
+
+ The diagram is labeled with 'H.812.1(16)\_F7-6' in the bottom right corner.
+
+Sequence diagram for hData Observation Upload showing interactions between a patient, PHG application, authorization server, and service application.
+
+**Figure 7-6 – hData Observation Upload**
+
+The RESTful interface is intended to be light weight in terms of its on-the-wire encoding and low-footprint in terms of the incremental software libraries that would need to be included above and beyond those included in the base SDK of common host platform operating systems. Specific emphasis is given to modern mobile platforms, such as smartphones, but desktop, laptop and embedded systems benefit equally from this simple design concept.
+
+The REST interface is intended to be modular and to be used by multiple Continua Certified Capability Classes. For feature parity with the Services interface as defined in clause 7.1, the REST interface defines one application layer "user" of its services, the Consumer Vitals Upload Use Case.
+
+### 7.3 Security
+
+The Continua Services security guidelines are based on the following concepts, originally defined in [b-ISO 27000]:
+
+- **Confidentiality:** "property that information is not available or disclosed to unauthorized individuals, entities or processes (set of interrelated or interacting activities which transform inputs into outputs)".
+- **Integrity:** "property of protecting the accuracy and completeness of the assets (Assets - anything that has value to the organization. Assets can be various types including: i) information, ii) software such as computer programs, iii) physical such as computer, iv) services)."
+- **Availability:** "property of being accessible and usable upon demand by an authorized entity."
+
+- **Accountability:** "responsibility of an entity for its actions and decisions."
+- **Authentication:** "provision of assurance that the claim characteristic of an entity is correct."
+- **Authorization:** "only fully identified and authenticated entities, equipped with access control credentials, should be able to avail themselves of services provided by systems."
+- **Access control:** "means that access to assets is authorized and restricted based on business and security requirements."
+
+### 7.3.1 Secure point-to-point communication
+
+The secured point-to-point communication will ensure the confidentiality and integrity of the data over the Services-IF. The scope of these guidelines is limited to a session oriented, synchronous and point-to-point communication channel between the Services observation sender device and the Services observation receiver device. Furthermore, the Services observation receiver device is assumed to be a fully trusted device, having full control over the data after reception from the TLS channel. The focus of the guidelines is to provide a secure communication channel through which data can be transmitted and not on the message level security.
+
+The tools used to provide secure communication are selected from the WS-I (Web Services Interoperability) Basic Security Profile (BSP) – TLS v1.0. The Continua guidelines utilize the same set of mechanisms from WS-I BSP for node authentication and secure communication as that of the Integrating the Healthcare Enterprise audit trail and node authentication (IHE ATNA) IT infrastructure profile.
+
+However, unlike audit trail and node authentication (ATNA) which requires mutual TLS authentication, the Continua guidelines do not provide additional guidance regarding the use of TLS v1.0 and instead depend on the guidance that is provided in TLS v1.0. The use of mutual or client-authenticates-server-only TLS is left up to the application.
+
+Figure 7-7 provides an overview of the interactions between the services observation sender device and the services observation receiver device in the context of secured communication in order to provide a basic level of confidentiality and integrity. Though the figure indicates the case of mutual TLS authentication, the services observation receiver device is not required to perform this additional step of authenticating the observation sender device.
+
+![Sequence diagram showing secure point-to-point communication between a Services observation sender device and a Services observation receiver device. The sender sends a PCD-01 message, applies transport level confidentiality and integrity using TLS cipher suites, and sends the data. The receiver decrypts the data and verifies its integrity.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Sender as Services observation sender device
+    participant Receiver as Services observation receiver device
+    Note left of Sender: PCD-01: Communicate PCD data unsolicited observation result
+    Sender->>Receiver: Send data after applying transport level confidentiality and integrity
+    Note right of Receiver: Decrypt the data and verify its integrity
+    Note left of Sender: Apply transport level confidentiality and integrity using TLS cipher suites
+  
+```
+
+The diagram illustrates the sequence of operations for secure point-to-point communication. It features two vertical lifelines: 'Services observation sender device' on the left and 'Services observation receiver device' on the right. 
+ 1. The sender initiates a message labeled 'PCD-01: Communicate PCD data unsolicited observation result'.
+ 2. Simultaneously, a local action on the sender's side is labeled 'Apply transport level confidentiality and integrity using TLS cipher suites'.
+ 3. The sender then transmits the message with the label 'Send data after applying transport level confidentiality and integrity'.
+ 4. Upon receipt, the receiver performs a local action labeled 'Decrypt the data and verify its integrity'.
+
+Sequence diagram showing secure point-to-point communication between a Services observation sender device and a Services observation receiver device. The sender sends a PCD-01 message, applies transport level confidentiality and integrity using TLS cipher suites, and sends the data. The receiver decrypts the data and verifies its integrity.
+
+Figure 7-7 – Secure point-to-point communication sequence
+
+After the successful authentication, mutual or otherwise, transport level data confidentiality and integrity is applied on the transmission between the services observation sender device and services observation receiver device.
+
+The use of TLS applies to hData transactions, as well as SOAP.
+
+### 7.3.2 Auditing
+
+Auditing provides a level of assurance to the healthcare providers so that they can determine an appropriate level of trust for the personal health information based upon the origin of that data. A lower level of data origin authentication can be provided through the combination of audit logs and transport level data integrity controls. This set of actions is the option that is specified in the guidelines. The guidelines allow for the use the IHE ATNA auditing related clauses (clause 3.20, ITI-TF-2) for this purpose. The services observation sender device may implement the audit record source actor and may support record audit event transaction as specified by the IHE ATNA profile. The services observation receiver device may implement the audit record repository actor as specified by IHE ATNA.
+
+Figure 7-8 shows the interactions related to the audit records. Note that it is also possible for other system nodes to implement the audit record repository actor, but that such systems are beyond the scope of the CDG.
+
+An alternative/complementary method of data origin authentication is to provide non-repudiation of origin. The proper use of digital signatures would provide proof of integrity and origin of the data in an immutable and persistent fashion so that it can be verified by an independent party. In this way, use of digital signatures provides a high level of assurance to a healthcare provider that the data is coming from a particular origin and allows them to put a greater degree of trust on its reliability. Although digital signature infrastructure is beyond the scope of the current services guidelines, it is expected that this mechanism will be investigated in future releases of the CDG.
+
+![Sequence diagram illustrating the auditing sequence between a Services observation sender device and a Services observation receiver device.](171115f072e42b379238ed0dd438e9d7_img.jpg)
+
+```
+sequenceDiagram
+    participant Sender as Services observation sender device
+    participant Receiver as Services observation receiver device
+    Note left of Sender: Generate event audit
+    Sender->>Receiver: Record audit event in repository
+    Note right of Receiver: Generate audit reports
+```
+
+The diagram shows a sequence of interactions between two entities: 'Services observation sender device' and 'Services observation receiver device'. The sender device initiates the process by generating an event audit (indicated by a self-loop arrow). It then sends a message labeled 'Record audit event in repository' to the receiver device. The receiver device responds by generating audit reports (indicated by another self-loop arrow). The diagram is labeled H.812.1(16)\_F7-8 at the bottom right.
+
+Sequence diagram illustrating the auditing sequence between a Services observation sender device and a Services observation receiver device.
+
+**Figure 7-8 – Auditing sequence**
+
+### 7.3.3 Entity identity assertion
+
+Entity identity assertion provides the necessary mechanisms that will enable the Services interface to communicate claims about an entity (a person or application) who wants to connect to one of the services on the services observation receiver device. In order to allow a user to connect from the services observation sender device to a service on the services observation receiver device, there is a need to correctly identify the entity. This enables the service provider to make access control decision and audit the information for the purpose of accountability. An example scenario would be that a user wants to log in and connect to a hypertension service on the services observation receiver device, hence the hypertension service needs to identify and validate the claims of the identity provided by the user before granting them access, and will audit the relevant information such as the identity of the requested user.
+
+Without the loss of generality, there could be two main use cases based on the installation of a services observation sender device application program, i.e.:
+
+1. A single service provider provisions an embedded box with embedded services observation sender device application and assertion information (e.g., certificate) which should authenticate and communicate to the service provider's back end (services observation receiver device). This is a static scenario.
+2. A consumer installs a certified services observation sender device application on their mobile phone or PC. The services observation sender device program has the capability to send information to multiple back-ends (services observation receiver devices). During the connection with a service on the services observation device, the services observation sender device application presents its certificate to the particular service in order to grant access to service. This is a more dynamic scenario.
+
+In order to cover both scenarios, these guidelines mandate the support of SAML 2.0 assertions in SOAP uploads and OAuth access tokens in hData uploads. Since SAML is only used in Observation Uploads, it is discussed in this document. OAuth is used in several hData-based capabilities so it is discussed in the common security guidelines clauses in [ITU-T H.812].
+
+### 7.3.3.1 SOAP transactions: SAML 2.0
+
+The specification for the use of SAML in these guidelines is similar to the IHE cross enterprise user assertion (XUA) profile. The IHE XUA profile uses the WS-Security header only with the SAML 2.0 assertions. However, the IHE XUA profile allows the use of the other type of tokens in order to provide identity information such as user name token, with the condition that interoperability has been assured through a policy between the communication parties. In a similar fashion, the Continua design guidelines constrain the WS-Security profile from WS-I BSP by using only the WS-Security header with the SAML 2.0 assertion as a security token and allow the use of any other token for providing the identity information, with the condition that interoperability is assured through policy. In other words, a Continua certified services Observation Upload receiver using SOAP is required to support SAML 2.0 assertions, but is allowed to use other means of identity authentication. The mechanism through which a specific token is obtained is beyond the scope of the CDG. A user could obtain such a token through WS-Trust, SAML 2.0 core protocols, or any other out-of-band mechanisms.
+
+Figure 7-9 shows interactions related to entity assertion on the Services-IF. The full line shows the transaction in the scope of the Continua guidelines while the dotted lines show the transactions that are out of scope of the Continua guidelines.
+
+![Sequence diagram showing entity identity assertion sequence between a Services observation sender device, an Assertion (or token) provider, and a Services observation receiver device.](2734e7f9be3e1dc046f14be2e6c9a085_img.jpg)
+
+```
+sequenceDiagram
+    participant Sender as Services observation sender device
+    participant Provider as Assertion (or token) provider
+    participant Receiver as Services observation receiver device
+
+    Note left of Sender: [Scope: Continua guidelines]
+    Sender->>Provider: Get assertion (or token) i.e., using WS-trust
+    Provider-->>Sender: Provide service user assertion (or token)
+    Note right of Receiver: [Out of scope]
+    Receiver-->>Provider: Other assertion (or token) related transactions e.g., verify assertion
+```
+
+The diagram illustrates the interaction sequence for entity identity assertion. It features three main components: a 'Services observation sender device' (left), an 'Assertion (or token) provider' (center), and a 'Services observation receiver device' (right). The interaction begins with the sender device sending a 'Get assertion (or token) i.e., using WS-trust' request to the provider. The provider responds with a 'Provide service user assertion (or token)'. The receiver device then sends 'Other assertion (or token) related transactions e.g., verify assertion' to the provider. The first two interactions are solid lines, indicating they are within the scope of the Continua guidelines, while the third is a dotted line, indicating it is out of scope. The diagram is labeled H.812.1(16)\_F7-9.
+
+Sequence diagram showing entity identity assertion sequence between a Services observation sender device, an Assertion (or token) provider, and a Services observation receiver device.
+
+Figure 7-9 – Entity identity assertion sequence
+
+### 7.3.4 Reliability
+
+#### 7.3.4.1 SOAP transactions: WS-Reliable messaging
+
+While the Continua Services interface makes use of HTTP over the reliable TCP/IP protocol, message-level delivery cannot be guaranteed due to software component, system and network failures. These failures may be especially common for specific PHG platforms which operate over an intermittent connection such as portable laptops and mobile phones. Even with the use of HTTP response codes, it can be difficult to deal with these failures in a reliable and consistent manner. For instance, if an observation request is sent from the PHG and the connection is terminated before a response code is received, the PHG has no way of knowing whether:
+
+1. the connection was terminated before the services observation receiver device has received the request, or
+2. the services observation receiver device has received the request and generated a response which was lost due to network failure.
+
+For non-critical data, such as the information classified in the "better" reliability category by the Continua end-to-end system architecture quality of service strategy (clause 6 of [ITU-T H.810]), this unknown state may be acceptable to a PHG, meaning that the PHG can safely remove this data from memory.
+
+However, for critical data such as the information classified in the "best" reliability category, a PHG must ensure that the data is delivered successfully. In order to address both situations in the 'best' case, the PHG must "replay" the request to the services observation receiver device in case the data did not get delivered (case 1) but in such a manner that it is possible to detect and remove duplicate messages in the case where the data did get delivered but the sender did not get notified of the delivery (case 2).
+
+This issue of reliable message delivery can be handled at multiple levels and has been built into the HL7 v2 application protocol messaging standard through the use of unique message identifiers and, optionally a sequence identifier in the message header (MSH) segment. However, handling message delivery at the application level has a number of disadvantages.
+
+For instance, consider a services observation receiver device which has received a CommunicatePCDDData request. The receiving device must process the observation result message and take some action, such as forwarding it to another system or persisting it in a database. If this action is lengthy/involved, perhaps due to transactional properties of the system, an acknowledgement of the initial transmission is not sent to the services observation sender device until the application-level response for the request is available. This delay can lead to scaling issues on the services observation receiver device due to the holding of resources associated with each connection. The delay might also lead to confusion on the services observation sender device due to an unacknowledged request that is still being processed. This situation can result in unnecessary "replay" messages from the services observation sender device which increases network traffic.
+
+It is these issues that the OASIS Web Services Reliable Exchange (WS-RX) technical committee addresses along with the WS-ReliableMessaging (WS-RM) and WS-MakeConnection (WS-MC) standards.
+
+Using WS-RM (see Figure 7-10), a PHG may create one or more "sequences" with the services observation receiver device. For instance, a PHG which supported WS-RM and WS-MC might establish a sequence with the "Exactly Once" message delivery to deliver messages that fall into the "best" reliability category in the end-to-end architecture, such as a large set of batched measurements.
+
+![Sequence diagram illustrating WS-RM sequence creation between a Services observation sender device and a Services observation receiver device. The diagram shows four messages: 1. Create sequence() from sender to receiver. 2. CreateSequenceResponse(Identifier=http://example.com/observations) from receiver to sender. 3. CreateSequence(Offer: identifier=http://backchannel.com/controls) from sender to receiver. 4. CreateSequenceResponse(Accept: Identifier=http://backchannel.com/controls) from receiver to sender. The diagram is labeled H.812.1(16)_F7-10.](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Sender as Services observation sender device
+    participant Receiver as Services observation receiver device
+    Note left of Sender: 
+    Sender->>Receiver: Create sequence()
+    activate Receiver
+    Receiver-->>Sender: CreateSequenceResponse(Identifier=http://example.com/observations)
+    deactivate Receiver
+    Note left of Sender: 
+    Sender->>Receiver: CreateSequence(Offer: identifier=http://backchannel.com/controls)
+    activate Receiver
+    Receiver-->>Sender: CreateSequenceResponse(Accept: Identifier=http://backchannel.com/controls)
+    deactivate Receiver
+    Note right of Receiver: H.812.1(16)_F7-10
+  
+```
+
+Sequence diagram illustrating WS-RM sequence creation between a Services observation sender device and a Services observation receiver device. The diagram shows four messages: 1. Create sequence() from sender to receiver. 2. CreateSequenceResponse(Identifier=http://example.com/observations) from receiver to sender. 3. CreateSequence(Offer: identifier=http://backchannel.com/controls) from sender to receiver. 4. CreateSequenceResponse(Accept: Identifier=http://backchannel.com/controls) from receiver to sender. The diagram is labeled H.812.1(16)\_F7-10.
+
+**Figure 7-10 – WS-RM sequence creation**
+
+Using WS-RM policy, it is possible to negotiate a desired QoS for a given exchange, although this capability is beyond the profiling of this version of the services guidelines. In addition to the benefits of declaring quality of service (QoS) properties through policy and the ability to push retry logic into the exchange framework (and out of the application), using WS-RM provides clients with an optimized transport acknowledgement mechanism that can be used to support demanding workflows. When coupled with WS-MakeConnection, the services observation sender device is able to invoke the Communicate PCD Data operation using fire and forget semantics without the risk of unknowingly losing messages.
+
+Another benefit of the WS-ReliableMessaging standard is that it allows for the explicit creation and tear-down of message sequences. For instance, in some cases, it is useful to know when a system across the Services interface is going down for maintenance. These cases are difficult to handle cleanly using traditional web-oriented approaches like HTTP, because a services observation sender device would not know when a service would be unavailable and vice versa. By explicitly closing an RM sequence, a sender or receiver can indicate that they have completed the current sequence and report the final statistics of that session before going down for a planned outage. For instance, if a services observation sender device is able to close an RM sequence before going offline, this would allow an associated services observation receiver device to free any resources related to this sequence, so that it is not left waiting for the next message in the sequence to arrive.
+
+It is important to note, however, that even with the use of the WS-Reliable messaging standard, there is no guarantee of message delivery, only that message delivery will be confirmed or not within a bounded sequence, meaning it is up to the application to set reasonable connection and sequence time-out values.
+
+#### 7.3.4.2 hData transactions
+
+At this time there is no equivalent of WS-Reliable messaging for hData transactions.
+
+### 8 Implementation guidance (informative)
+
+#### 8.1 PHG conceptual model
+
+In the following clauses a conceptual model of a PHG is presented. The model does not define normative behaviour, and the components described are not required to exist in an actual implementation. The model is presented to elucidate how a Services interface could be constructed for a PHG, and to show how the Services interface behaves in the context of an overall system.
+
+The PHG presented here operates on both the Continua Personal Health Device and Services interfaces. The details of the provisioning and configuration of this device are beyond the scope of this release of the guidelines.
+
+## **8.2 Overview of operation**
+
+A Continua PHG collects observations from Personal Health Devices that the PHG is configured to operate with and delivers these observations to services observation receivers.
+
+To perform this operation the PHG must have sufficient knowledge about the information being reported by a device to be able to construct an observation that can be correctly understood when delivered in the context of a single HL7 v2.6 message.
+
+The process is initiated by a device connecting to the PHG using the personal health interfaces. The device delivers information to the PHG in a form defined by the Personal Health Device protocols, typically as changes in values of attributes that are identified by ISO/IEEE 11073-10101 nomenclature. The PHG uses the delivered change information, in conjunction with additional context information about the entity that it is communicating with, to construct an observation in the form of an HL7 V2.6 message as constrained by the IHE PCD-01 transaction. The additional context information is obtained from mechanisms outside the scope of this specification. An example of such a mechanism is a user who configures the PHG with the URI of a health service that supports the Services-IF.
+
+The PHG determines the context of the arriving observation, again from externally provided information that is available to the PHG. This information must ensure that the observation taken is associated with the right person, and comes from a known, properly configured device.
+
+The PHG takes ownership of the observation and determines the destination of the observation, as well as the security context that will be used to deliver the data.
+
+When the PHG is able to establish a connection to the services observation receiver device, it opens a secure connection and delivers the observations maintained in the corresponding persistent session queue.
+
+When a PHG communicates an unsolicited observation result message to the Health & Fitness service, it must wait for confirmation that the transmission has been successful (transport acknowledgement) and that the message was successfully processed on the server (application acknowledgement). When a PHG obtains a transport-level acknowledgement in the form of an HTTP response or WS-ReliableMessaging SequenceAcknowledgement, it can be assured that the message has been received at the services observation receiver device and can safely remove the message from its queue. However, a transport-level acknowledgement does not necessarily indicate that the message has been properly processed. For instance, it is possible that the message was received at the services observation receiver device but was rejected by the application itself. For this purpose, an HL7 application accept-response provides a confirmation that the receiving application has accepted responsibility for this event so that the PHG application may safely remove the data from memory. Similarly, if the PHG receives an application reject or application error response, it may take some form of corrective action such as attempting again later, sending the request to a separate endpoint, or alerting the user.
+
+![Figure 8-1 – PHG block diagram. The diagram shows three 'Personal health device' boxes on the left, each with a green double-headed arrow labeled 'Observations event reports' pointing to a central 'Personal Health Gateway (PHG)' box. From the PHG, three orange double-headed arrows labeled 'Observations PCD-01' point to three 'Health & Fitness service' boxes on the right. A small text 'H.812.1(17)_F8-1' is at the bottom right.](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg)
+
+Figure 8-1 – PHG block diagram. The diagram shows three 'Personal health device' boxes on the left, each with a green double-headed arrow labeled 'Observations event reports' pointing to a central 'Personal Health Gateway (PHG)' box. From the PHG, three orange double-headed arrows labeled 'Observations PCD-01' point to three 'Health & Fitness service' boxes on the right. A small text 'H.812.1(17)\_F8-1' is at the bottom right.
+
+**Figure 8-1 – PHG block diagram**
+
+The system block diagram, shown in Figure 8-1, depicts the overall flow of observations from PAN devices to Health & Fitness services.
+
+The PHG may collect observations from multiple PAN devices at any given point in time and a single PAN device may deliver data to multiple persistent sessions. Likewise, a PHG may deliver these observations to zero or more Health & Fitness services.
+
+### 8.3 Certified Capability Classes for Observation Upload
+
+Table 8-1 shows the Certified Capability Classes defined for the Services-IF interface design guidelines for Observation Upload.
+
+**Table 8-1 – Certified Capability Classes**
+
+| Capability class                    | Continua certified |
+|-------------------------------------|--------------------|
+| SOAP Observation Upload – PHG       | Yes                |
+| SOAP Observation Upload – Services  | Yes                |
+| hData Observation Upload – PHG      | Yes                |
+| hData Observation Upload – Services | Yes                |
+
+The guidelines that are applicable for each of the Certified Capability Classes are referenced in Table 8-2.
+
+**Table 8-2 – Guidelines for Certified Capability Classes**
+
+| Certified Capability Class          | Relevant guidelines                                                   |
+|-------------------------------------|-----------------------------------------------------------------------|
+| SOAP Observation Upload – PHG       | Table A.1, Table A.2, Table C.1, Table C.2<br>PCD-01 Payload: Annex D |
+| SOAP Observation Upload – Services  | Table A.1, Table A.3, Table C.1, Table C.3                            |
+| hData Observation Upload – PHG      | Table A.1, Table A.2, Table B.1<br>PCD-01 Payload: Annex D            |
+| hData Observation Upload – Services | Table A.1, Table A.3,<br>Table B.2                                    |
+
+Identities of patients play a key role in this architecture. The context of most communication is related to a specific patient. Throughout the architecture different identifiers are used to identify the same physical user (patient) in addition to the use of different representations for identities and other identity information.
+
+Regulations and good practices mandate an accurate and reliable linking of health information to a patient identity. As a consequence, the various devices that are part of the architecture must be properly provisioned with identity information such as identifiers and associated credentials, identify the user, and map identities correctly when health information moves from one realm to another.
+
+By definition, identifiers are only well-defined in the realm to which they belong. This corresponds for the various devices/Services to:
+
+- UserID @ PHD: IEEE 11073 Person-Id + System-Id pair
+- UserID @ Services: as defined by the Services service, relates to PIDs in HL7 messages
+- UserID @ HIS: as defined by the HIS service (see [ITU-T H.813] clauses 6.1.1.2, Chosen standards and profiles and 6.1.1.3, Topology).
+
+One must also recognize that some Personal Health Devices have no Person-Id and some other means must be used to map the device observations to a given person.
+
+For each of the identities a user holds at the various devices and services, the user must be able to uniquely identify and (for certain interfaces) be authenticated, mappings between his identifiers must be established, and these mappings must be applied to forward exchanges across interfaces. Conceptually, the mappings may be regarded as pairwise mappings held by the PHG and Health & Fitness service in a mapping table. This mapping assures a consistent end-to-end identity framework is created.
+
+Figure 8-2 presents the identity related interactions between the various actors in the architecture. Below each actor the primary identifier of the user at that actor is listed. The interactions are:
+
+1. Given the set of personal health and services identities, mappings are established and maintained in a PHG mapping table. This mapping is especially needed when there is no non-ambiguous one-to-one mapping. These mappings are managed out-of-band. The management may involve the user, or a services service employee may act as a user's delegate, e.g., a nurse at a disease management organization (DMO). In a typical scenario, it involves associating a certain Personal Health Device with a certain user identity at a services service, e.g., patient 1 linking his weight measurements to DMO 1 and patient 2 linking his activity measurements to DMO 2.
+2. Identifiers are mapped from the Personal Health Devices interface to the Services-IF according to the PHG mapping table. Also, as part of this step any potential ambiguity, e.g., caused by shared Personal Health Devices lacking proper user identification is taken care of. Using the mapping table the PHG populates the PID segment of the PCD-01 message based upon the information received from the Personal Health Device.
+3. Given the set of services and HIS identities, mappings are established and maintained in a services mapping table. IHE PIX transactions may be used for this process where an HIS sender queries for the patient identifier to use for a given patient at an HIS receiver. Alternatively, identities at the HIS-IF are managed out-of-band. A web-centric environment could, for example, apply identify federation protocols.
+4. Identifiers are mapped from the Services-IF to the HIS-IF according to the services mapping table.
+
+The interactions span the full range of deployments. Specific deployments use a subset of the offered functionality tailored to the situation, e.g., self, delegated or out-of-band configuration. The PHG mainly concerns step 2.
+
+The approach is consistent with and meets the requirements identified in [b-CHA UI] on user identification.
+
+![Sequence diagram showing identification and identity cross-referencing interactions between User/delegate, UserID@PHD, PHG, Service device, and HIS device. The diagram illustrates the flow of identity management and measurement data across different devices and systems.](c494cd874a082a97b50b3c4d3938f467_img.jpg)
+
+The diagram illustrates the interaction between five entities: User/delegate, UserID@PHD, PHG (No external user identifiers), UserID@Service, and UserID@HIS. The interactions are as follows:
+
+- Manual/out-of-band manage identity mappings:** A dashed arrow from UserID@PHD to User/delegate.
+- Out-of-band identity management:** A dashed arrow from PHG to UserID@Service.
+- Measurement:** A dashed arrow from UserID@PHD to PHG.
+- Measurement + SAML 2.0 token:** A dashed arrow from PHG to UserID@Service.
+- IHE PIX:** A dashed arrow from UserID@Service to UserID@HIS.
+- Measurement:** A dashed arrow from PHG to UserID@Service.
+- Measurement:** A dashed arrow from UserID@Service to UserID@HIS.
+
+At the bottom of the diagram, the text "H.812.1(17)\_F8-2" is present.
+
+Sequence diagram showing identification and identity cross-referencing interactions between User/delegate, UserID@PHD, PHG, Service device, and HIS device. The diagram illustrates the flow of identity management and measurement data across different devices and systems.
+
+**Figure 8-2 – Identification and identity cross-referencing interactions**
+
+## 8.4 Sample service description SOAP
+
+The Continua services Observation Upload over SOAP interface makes use of the IHE PCD-01: Communicate PCD Data transaction over web services. Web services description language (WSDL) is a W3C standard designed to define a web service through endpoints and operations.
+
+Appendix V of [IHE ITI-TF-2] provides guidance on deriving WSDL files from an IHE transaction. The following artefacts are provided as informative implementation artefacts and should match the versions found in the IHE [ftp://ftp.ihe.net/TF\\_Implementation\\_Material/](ftp://ftp.ihe.net/TF_Implementation_Material/) for PCD.
+
+## 8.5 Device observation consumer WSDL
+
+```
+<?xml version="1.0" encoding="UTF-8"?>
+<wsdl:definitions name="DeviceObservationConsumer"
+  targetNamespace="urn:ihe:pcd:dec:2010"
+  xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
+  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+  xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"
+  xmlns:tns="urn:ihe:pcd:dec:2010">
+  <wsdl:types>
+    <xsd:schema>
+      <xsd:import namespace="urn:ihe:pcd:dec:2010"
+        schemaLocation="DeviceObservationConsumer.xsd"/></xsd:import>
+    </xsd:schema>
+  </wsdl:types>
+  <wsdl:message name="CommunicatePCDData_Message">
+    <wsdl:documentation>Communicate PCD Data</wsdl:documentation>
+    <wsdl:part name="body" element="tns:CommunicatePCDData" />
+  </wsdl:message>
+  <wsdl:message name="CommunicatePCDDataResponse_Message">
+    <wsdl:documentation>Communicate PCD Data Response</wsdl:documentation>
+    <wsdl:part name="body" element="tns:CommunicatePCDDataResponse" />
+  </wsdl:message>
+  <wsdl:portType name="DeviceObservationConsumer_PortType">
+    <wsdl:operation name="CommunicatePCDData">
+      <wsdl:input message="tns:CommunicatePCDData_Message"
+        wsaw:Action="urn:ihe:pcd:2010:CommunicatePCDData" />
+```
+
+```
+
+    <wsdl:output message="tns:CommunicatePCDDataResponse_Message"
+        wsdl:Action="urn:ihe:pcd:2010:CommunicatePCDDataResponse" />
+  </wsdl:operation>
+</wsdl:portType>
+<wsdl:binding name="DeviceObservationConsumer_Binding_Soap12"
+type="tns:DeviceObservationConsumer_PortType">
+  <soap12:binding style="document"
+    transport="http://schemas.xmlsoap.org/soap/http" />
+  <wsdl:operation name="CommunicatePCDData">
+    <soap12:operation soapAction="urn:ihe:pcd:2010:CommunicatePCDData"
+  />
+    <wsdl:input>
+      <soap12:body use="literal" />
+    </wsdl:input>
+    <wsdl:output>
+      <soap12:body use="literal" />
+    </wsdl:output>
+  </wsdl:operation>
+</wsdl:binding>
+<wsdl:service name="DeviceObservationConsumer_Service">
+  <wsdl:port binding="tns:DeviceObservationConsumer_Binding_Soap12"
+name="DeviceObservationConsumer_Port_Soap12">
+    <soap12:address location="http://www.example.org/" />
+  </wsdl:port>
+</wsdl:service>
+</wsdl:definitions>
+
+```
+
+## 8.6 Device observation consumer XSD
+
+```
+
+<?xml version="1.0" encoding="UTF-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema"
+targetNamespace="urn:ihe:pcd:dec:2010" xmlns:tns="urn:ihe:pcd:dec:2010">
+  <element name="CommunicatePCDData" type="tns:UnsolicitedObservationResult"
+  />
+  <element name="CommunicatePCDDataResponse"
+type="tns:GeneralAcknowledgement" />
+
+  <simpleType name="UnsolicitedObservationResult">
+    <restriction base="string" />
+  </simpleType>
+
+  <simpleType name="GeneralAcknowledgement">
+    <restriction base="string" />
+  </simpleType>
+</schema>
+
+```
+
+## 8.7 Messaging examples
+
+In addition to the WSDL-related rules found in Appendix V of [IHE ITI-TF-2], the framework contains a number of conformance constraints for web service consumers and providers. These rules were developed to improve IHE-related web service interoperability and Continua services observation senders and receivers are required to comply.
+
+Note that the contents of the `urn:ihe:pcd:dec:2010:CommunicatePCDData` element must contain the entire contents of a valid PCD-01 Observation Result message. However, based on the character restrictions of XML and web services, there are a number of characters that cannot be used in their literal form (see [http://www.w3.org/International/questions/qa\\_controls#support](http://www.w3.org/International/questions/qa_controls#support) for more information).
+
+Restricted characters, such as "&" and "<cr>", must be escaped using XML predefined character entity references wherever possible (e.g., &amp;). For restricted characters that have no predefined character entity references, numeric character references should be used instead (e.g., &#d;). Messages containing characters which are prohibited from use in XML in both a literal and escaped format are prohibited from being sent over the Continua Services interface.
+
+For a complete list of excluded characters, please see the XML specification at <http://www.w3.org/TR/xml/#syntax>.
+
+The following informative clauses contain a sample CommunicatePCDData message and a typical response. Note that the message is unsecure and would not occur in operations.
+
+## 8.8 Communicate PCD data
+
+```
+<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
+  <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
+    <wsa:To soapenv:mustUnderstand="true">
+http://localhost/DeviceObservationConsumer_Service
+    </wsa:To>
+    <wsa:From soapenv:mustUnderstand="true">
+      <wsa:Address>
+http://www.w3.org/2005/08/addressing/anonymous
+      </wsa:Address>
+    </wsa:From>
+    <wsa:MessageID soapenv:mustUnderstand="true">
+      urn:uuid:A52590343911955D1A1251497585530
+    </wsa:MessageID>
+    <wsa:Action soapenv:mustUnderstand="true">
+      urn:ihe:pcd:2010:CommunicatePCDData
+    </wsa:Action>
+  </soapenv:Header>
+  <soapenv:Body>
+    <CommunicatePCDData xmlns="urn:ihe:pcd:dec:2010">
+MSH|^~\&|AcmeInc^ACDE48234567ABCD^EUI-
+64|||20090713090030+0000||ORU^R01^ORU_R01|MSGID1234|P|2.6|||NE|AL|||IHE_PCD ORU-R01
+2006^HL7^2.16.840.1.113883.9.n.m^HL7
+PID||789567^^Imaginary Hospital^PI||Doe^John^Joseph^^^^L^A|||M
+OBR|1|AB12345^AcmePHGInc^ACDE48234567ABCD^EUI-64|CD12345^AcmePHGInc^ACDE48234567ABCD^EUI-
+64|182777000^monitoring of patient^SNOMED-CT|||20090813095715+0000
+PHG-OBXes
+OBX|n|CWE|68220^MDC_TIME_SYNC_PROTOCOL^MDC|0.0.0.y|532224^MDC_TIME_SYNC_NONE^MDC|||R
+OBX|n+1||528391^MDC_DEV_SPEC_PROFILE_BP^MDC|1|||X|||0123456789ABCDEF^0123456789ABCDEF^EUI-
+64
+OBX|n+2|DTM|67975^MDC_ATTR_TIME_ABS^MDC|1.0.0.x|20091028123702|||R||20091028173702+0000
+More MDS-OBXes
+OBX|m||150020^MDC_PRESS_BLD_NONINV^MDC|1.0.1|||X||20090813095715+0000
+OBX|m+1|NM|150021^MDC_PRESS_BLD_NONINV_SYS^MDC|1.0.1.1|120|266016^MDC_DIM_MMHG^MDC|||R
+OBX|m+2|NM|150022^MDC_PRESS_BLD_NONINV_DIA^MDC|1.0.1.2|80|266016^MDC_DIM_MMHG^MDC|||R
+OBX|m+3|NM|150023^MDC_PRESS_BLD_NONINV_MEAN^MDC|1.0.1.3|100|266016^MDC_DIM_MMHG^MDC|||R
+    </CommunicatePCDData>
+  </soapenv:Body>
+</soapenv:Envelope>
+```
+
+The implementer should note that one source of confusion has been in the difference between the urn:ihe:pcd:2010 qualifier in the wsa:Action value and the urn:ihe:pcd:dec:2010 qualifier in the CommunicatePCDData element attribute. They are not the same.
+
+## 8.9 Communicate PCD data response
+
+```
+<?xml version="1.0" encoding="UTF-8"?>
+<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
+  <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
+    <wsa:Action soapenv:mustUnderstand="true">
+urn:ihe:pcd:2010:CommunicatePCDDataResponse
+    </wsa:Action>
+    <wsa:RelatesTo soapenv:mustUnderstand="true">
+urn:uuid:A52590343911955D1A1251497585530
+    </wsa:RelatesTo>
+  </soapenv:Header>
+  <soapenv:Body>
+    <CommunicatePCDDataResponse xmlns="urn:ihe:pcd:dec:2010">
+```
+
+```
+
+MSH|^~\&|Stepstone|AcmeInc^ACDE48234567ABCD^EUI-
+64||20090726095731+0000||ACK^R01^ACK|AMSGID1234|P|2.6|&#xD;
+MSA|AA|MSGID1234&#xD;
+    </CommunicatePCDDataResponse>
+  </soapenv:Body>
+</soapenv:Envelope>
+
+```
+
+In the above response the 'mustUnderstand' attributes have been added to be consistent with Appendix V of [IHE ITI-TF-2]. The WS addressing specification is not clear on the use of the 'mustUnderstand' attribute in the response for those headers which have the attribute in the request. However, the examples in the WS addressing specification do have matching attributes in the response.
+
+## 8.10 CommunicatePCDData example with security
+
+This example illustrates a scenario where an organization provides a services receiver service that also supports a WS-Trust STS service using the username token option for obtaining a SAML token. A client creates an account with this organization in order to access these services. The account has a user name and password which the client is to use to obtain the SAML token.
+
+When it is time to send data over the Services interface, the PHG first requests an SAML token from the organization using the Username Token STS request. The service scans the username and password in the Username Token and sees that it is a registered user. The service creates a signed SAML token identifying the client and returns it to the user. When data is to be sent, the SAML token is placed into the security header of the CommunicatePCDData transaction. The services service validates the token to see if it is an authenticated and authorized user and if valid handles the received data. In this scenario, the client has instructed the services service to translate any received data to a PHMR document and to send it to a specified repository.
+
+NOTE – The PHMR Implementation Guide is currently undergoing significant revisions as it is transitioning from a draft Standard for trial use (DSTU) to a normative specification in HL7. As such, implementers can expect changes to the HIS interface as soon as the final normative PHMR Implementation Guide is available to be profiled, to be expected as errata to these Design Guidelines or in the next revision.'
+
+Some liberties in the formatting of the messages in the following have been taken to make it readable.
+
+### 8.10.1 STS request
+
+Below is the WS-Trust Username Token request for an SAML 2.0 token. There is an optional 'claims' element used by this particular STS-service for this transaction. The transaction is sent using TLS so on the wire the password is not legible.
+
+```
+
+POST /axis2/services/STS_Username HTTP/1.1
+Content-Type: application/soap+xml; charset=UTF-8;
+action="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue"
+User-Agent: Dalvik/1.6.0 (Linux; U; Android 4.0.4; Nexus S Build/IMM26)
+Host: 192.168.1.3:8443
+Connection: Keep-Alive
+Accept-Encoding: gzip
+Content-Length: 2414
+
+<?xml version='1.0' encoding='UTF-8'?>
+<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
+  <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
+    <wsse:Security soapenv:mustUnderstand="true"
+      xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-
+      secext-1.0.xsd"
+      xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-
+      utility-1.0.xsd">
+      <wsu:Timestamp wsu:Id="Timestamp-3">
+        <wsu:Created>2013-03-01T16:54:53.797</wsu:Created>
+        <wsu:Expires>2013-03-01T16:59:53.797</wsu:Expires>
+
+```
+
+```
+
+</wsu:Timestamp>
+
+<wsse:UsernameToken wsu:Id="UsernameToken-ID">
+  <wsse:Username>Sisansarah</wsse:Username>
+  <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
+username-token-profile-1.0#PasswordText">
+    publicpassword
+  </wsse:Password>
+</wsse:UsernameToken>
+
+</wsse:Security>
+<wsa:To soapenv:mustUnderstand="true">
+  https://192.168.1.3:8443/axis2/services/STS_Username
+</wsa:To>
+<wsa:ReplyTo soapenv:mustUnderstand="true">
+
+<wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Ad
+dress>
+</wsa:ReplyTo>
+<wsa:MessageID soapenv:mustUnderstand="true">urn:uuid:0_1362156893800</wsa:MessageID>
+<wsa:Action
+soapenv:mustUnderstand="true">http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue
+</wsa:Action>
+</soapenv:Header>
+<soapenv:Body>
+  <wst:RequestSecurityToken xmlns:wst="http://docs.oasis-open.org/ws-sx/ws-
+trust/200512">
+    <wst:RequestType>http://docs.oasis-open.org/ws-sx/ws-
+trust/200512/Issue</wst:RequestType>
+    <wst:Lifetime>
+      <wsu:Created xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
+wssecurity-utility-1.0.xsd">2013-03-01T16:59:53.797</wsu:Created>
+      <wsu:Expires xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
+wssecurity-utility-1.0.xsd">2013-03-01T17:04:53.797</wsu:Expires>
+    </wst:Lifetime>
+    <wst:TokenType>
+      http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV2.0
+    </wst:TokenType>
+    <wst:KeyType>http://docs.oasis-open.org/ws-sx/ws-
+trust/200512/SymmetricKey</wst:KeyType>
+    <wst:KeySize>256</wst:KeySize>
+    <wst:Entropy>
+      <wst:BinarySecret Type="http://docs.oasis-open.org/ws-sx/ws-trust/200512/Nonce">
+        i369jzmWbY1MB8uEAQwXghli9iORbIRM4IQCFICrwI=
+      </wst:BinarySecret>
+    </wst:Entropy>
+    <wst:ComputedKeyAlgorithm>
+      http://docs.oasis-open.org/ws-sx/ws-trust/200512/CK/PSHA1
+    </wst:ComputedKeyAlgorithm>
+    <wst:Claims Dialect="SomeURI">Continua</wst:Claims>
+  </wst:RequestSecurityToken>
+</soapenv:Body>
+</soapenv:Envelope>
+
+```
+
+## 8.10.2 STS response
+
+The STS response contains the SAML token which the application removes and inserts into the security header of the CommunicatePCDDData transaction. Recall that obtaining the SAML token is out of band as far as the Continua guidelines are concerned.
+
+```
+
+HTTP/1.1 200 OK
+Server: Apache-Coyote/1.1
+Content-Type: application/soap+xml;action="urn:RequestSecurityTokenResponse";charset=UTF-8
+Transfer-Encoding: chunked
+Date: Fri, 01 Mar 2013 16:54:27 GMT
+
+<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
+xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
+  <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
+    <wsse:Security
+      xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
+      xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
+
+```
+
+
+
+```
+
+eKDMULZJPau6PkJD8Hn94A1EstBDYA70ph3w1moDxYbcG2QLxC1WrFM6aqR3NB92zG8T3Q9X4jxGGWPkd39IndfdDMCAwEAAAMx
+MC8wHQYDVRO1BBYwFAYIKwYBBQUHAwEGCCsGAQUFBWMCMA4GA1UdDwEB/wQEAwIEsDANBgkqhkiG9w0BAQUFAAOBgQBeAOERzydv
+AUNipBKOVg3FcjGTyMg31zo7S1DFg7qTM4FZwUf2zw9XMagVLJRsaWAsj8mqnugTpB4jBJCrCGZ7YEviXz4PnqQjuuov5rXtFIc
+1Bp/PQmQt+LiZ2zln+ffXnSoHEzUsqs5zhdy/uIP0srAtBosdHxL9BJHxd7wQw==</ds:X509Certificate>
+</ds:X509Data>
+</ds:KeyInfo>
+</ds:Signature>
+<saml2:Subject>
+<saml2:SubjectConfirmation Method="urn:oasis:names:tc:SAML:2.0:cm:holder-of-key">
+<saml2:SubjectConfirmationData
+  xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"
+  NotBefore="2013-03-01T16:54:27.792Z"
+  NotOnOrAfter="2013-03-01T17:37:39.792Z"
+  xsi:type="saml2:KeyInfoConfirmationDataType">
+  <ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
+    <xenc:EncryptedKey
+      xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"
+      Id="EK-C82A2592DB5193D51C13621568677947">
+      <xenc:EncryptionMethod
+        Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5"/>
+      <ds:KeyInfo>
+        <wsse:SecurityTokenReference
+          xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
+          <wsse:KeyIdentifier
+            EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"
+            ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#ThumbprintSHA1">
+            EPlMdE3oRinLo8bGg3BLR3uGWT8=
+          </wsse:KeyIdentifier>
+        </wsse:SecurityTokenReference>
+      </ds:KeyInfo>
+      <xenc:CipherData>
+        <xenc:CipherValue>
+JkAWwNH+FdRevF6o9zjB+FTmwxe58jYFeHQ684YNeM5zSLvKna47h/vlOowtnDf5htaBo3uEqp8xPf+IDOYjNQLHfsDHZ60EvVU
+jrHKXALE5pRcFtqX93iiUE/Ke4zpVvGQjyMxer454Qo/SL98xd6v4jpDc/zKMK4iGPO+YaI=
+        </xenc:CipherValue>
+      </xenc:CipherData>
+    </xenc:EncryptedKey>
+  </ds:KeyInfo>
+</saml2:SubjectConfirmationData>
+</saml2:SubjectConfirmation>
+</saml2:Subject>
+<saml2:Conditions NotBefore="2013-03-01T16:54:27.792Z" NotOnOrAfter="2013-03-01T17:37:39.792Z" />
+<saml2:AttributeStatement>
+  <saml2:Attribute
+    Name="program"
+    NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified">
+  <saml2:AttributeValue
+    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    xsi:type="xs:string">
+    Continua
+  </saml2:AttributeValue>
+</saml2:Attribute>
+<saml2:Attribute
+  Name="user"
+  NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified">
+  <saml2:AttributeValue
+    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    xsi:type="xs:string">Sisansarah</saml2:AttributeValue>
+</saml2:Attribute>
+</saml2:AttributeStatement>
+</saml2:Assertion>
+===== End of SAML Token
+
+</wst:RequestedSecurityToken>
+<wst:RequestedProofToken>
+<wst:ComputedKey>
+http://docs.oasis-open.org/ws-sx/ws-trust/200512/CK/PSHA1
+</wst:ComputedKey>
+</wst:RequestedProofToken>
+<wst:Entropy>
+<wst:BinarySecret
+  Type="http://docs.oasis-open.org/ws-sx/ws-trust/200512/Nonce">
+2dDQACinnpN2oNV2kFINXEqAN8SMvTQOGpZKB3IAC9c=
+</wst:BinarySecret>
+</wst:Entropy>
+</wst:RequestSecurityTokenResponse>
+</wst:RequestSecurityTokenResponseCollection>
+</soapenv:Body>
+
+```
+
+</soapenv:Envelope>
+
+### 8.10.3 CommunicatePCDData request
+
+This request is where the PCD-01 payload is sent. For brevity, the SAML token is not shown in the following request, but it is identical to the token delivered by the STS service. Even though the token identifies the user, it is opaque to the user and unmutable since it is signed. The contents are only of interest to the receiver.
+
+```
+POST /axis2/services/Exchange HTTP/1.1
+Content-Type: application/soap+xml; charset=UTF-8; action="urn:ihe:pcd:2010:CommunicatePCDData"
+User-Agent: Dalvik/1.6.0 (Linux; U; Android 4.0.4; Nexus S Build/IMM26)
+Host: 192.168.1.3:8443
+Connection: Keep-Alive
+Accept-Encoding: gzip
+Content-Length: 8348
+
+<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
+xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
+  <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
+    <wsse:Security soapenv:mustUnderstand="true"
+      xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
+      xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
+      <wsu:Timestamp wsu:Id="Timestamp-3">
+        <wsu:Created>2013-03-01T16:54:54.336</wsu:Created>
+        <wsu:Expires>2013-03-01T16:59:54.336</wsu:Expires>
+      </wsu:Timestamp>
+      ===== SAML Token goes here
+    </wsse:Security>
+    <wsa:To soapenv:mustUnderstand="true">https://192.168.1.3:8443/axis2/services/Exchange</wsa:To>
+    <wsa:ReplyTo soapenv:mustUnderstand="true">
+      <wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>
+    </wsa:ReplyTo>
+    <wsa:MessageID soapenv:mustUnderstand="true">urn:uuid:1_1362156894340</wsa:MessageID>
+    <wsa:Action soapenv:mustUnderstand="true">urn:ihe:pcd:2010:CommunicatePCDData</wsa:Action>
+  </soapenv:Header>
+  <soapenv:Body>
+    <pcd:CommunicatePCDData xmlns:pcd="urn:ihe:pcd:dec:2010">
+MSH|^~\&|LNI Example PHG^ECDE3D4E58532D31^EUI-64|||20130301115450.720-0500||ORU^R01^ORU_R01|
+002013030111545720|P|2.6||NE|AL|||IHE PCD ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7&#xD;
+PID||28da0026bc42484^^^&1.19.6.24.109.42.1.3&ISO^PI||Piggy^Sisansarah^L.^^^L&#xD;
+OBR|1|JOXP-PCD^LNI Example PHG^ECDE3D4E58532D31^EUI-64|
+JOXP-PCD^LNI Example PHG^ECDE3D4E58532D31^EUI-64|182777000^monitoring of patient^SNOMED-CT|||
+20130301115452.000-0500|20130301115455.001-0500&#xD;
+OBX|1|531981^MDC_MOC_VMS_MDS_PHG^MDC|0|||X|||ECDE3D4E58532D31^^ECDE3D4E58532D31^EUI-64&#xD;
+OBX|2|CWE|68218^MDC_ATTR_REG_CERT_DATA_AUTH_BODY^MDC|0.0.0.1|2^auth-body-continua||||R&#xD;
+OBX|3|ST|532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC|0.0.0.1.1|2.0||||R&#xD;
+OBX|4|NM|532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC|0.0.0.1.2|4||||R&#xD;
+OBX|5|CWE|68218^MDC_ATTR_REG_CERT_DATA_AUTH_BODY^MDC|0.0.0.2|2^auth-body-continua||||R&#xD;
+OBX|6|CWE|532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC|0.0.0.2.1|1^unregulated(0)||||R&#xD;
+OBX|7|CWE|68218^MDC_ATTR_REG_CERT_DATA_AUTH_BODY^MDC|0.0.0.3|2^auth-body-continua||||R&#xD;
+OBX|8|CWE|532355^MDC_REG_CERT_DATA_CONTINUA_PHG_CERT_LIST^MDC|0.0.0.3.1|0^observation-upload-
+soap||||R&#xD;
+OBX|9|CWE|68220^MDC_TIME_SYNC_PROTOCOL^MDC|0.0.0.4|532234^MDC_TIME_SYNC_NONE^MDC||||R&#xD;
+OBX|10|NM|8221^MDC_TIME_SYNC_ACCURACY^MDC|0.0.0.5|120000000|264339^MDC_DIM_MICRO_SEC^MDC||||R&#xD;
+OBX|11|528391^MDC_DEV_SPEC_PROFILE_BP^MDC|1||||X|||1234567800112233^^1234567800112233^EUI-
+64&#xD;
+OBX|12|ST|531970^MDC_ID_MODEL_MANUFACTURER^MDC|1.0.0.1|Lamprey Networks||||R&#xD;
+OBX|13|ST|531969^MDC_ID_MODEL_NUMBER^MDC|1.0.0.2|Blood Pressure 1.0.0||||R&#xD;
+OBX|14|CWE|68218^MDC_ATTR_REG_CERT_DATA_AUTH_BODY^MDC|1.0.0.3|2^auth-body-continua||||R&#xD;
+OBX|15|ST|532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC|1.0.0.3.1|2.0||||R&#xD;
+OBX|16|NM|532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC|1.0.0.3.2|24583~8199~16391~7||||R&#x
+D;
+OBX|17|CWE|68218^MDC_ATTR_REG_CERT_DATA_AUTH_BODY^MDC|1.0.0.4|2^auth-body-continua||||R&#xD;
+OBX|18|CWE|532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC|1.0.0.4.1|1^unregulated(0)||||R&#xD;
+OBX|19|CWE|68219^MDC_TIME_CAP_STATE^MDC|1.0.0.5|1^mads-time-capab-real-time-clock(0)||||R&#xD;
+OBX|20|CWE|68220^MDC_TIME_SYNC_PROTOCOL^MDC|1.0.0.6|532224^MDC_TIME_SYNC_NONE^MDC||||R&#xD;
+OBX|21|DTM|67975^MDC_ATTR_TIME_ABS^MDC|1.0.0.7|20130301115423.00||||R||20130301115450.733-
+0500&#xD;
+OBX|22||150020^MDC_PRESS_BLD_NONINV^MDC|1.0.1|||X||20130301115452.733-0500&#xD;
+OBX|23|NM|150021^MDC_PRESS_BLD_NONINV_SYS^MDC|1.0.1.1|105|266016^MDC_DIM_MMHG^MDC||||R&#xD;
+OBX|24|NM|150022^MDC_PRESS_BLD_NONINV_DIA^MDC|1.0.1.2|70|266016^MDC_DIM_MMHG^MDC||||R&#xD;
+OBX|25|NM|150023^MDC_PRESS_BLD_NONINV_MEAN^MDC|1.0.1.3|81.7|266016^MDC_DIM_MMHG^MDC||||R&#xD;
+OBX|26|NM|149546^MDC_PULS_RATE_NON_INV^MDC|1.0.0.8|80|264864^MDC_DIM_BEAT_PER_MIN^MDC||||R||201303
+01115453.733-0500&#xD;
+  </pcd:CommunicatePCDData>
+</soapenv:Body>
+</soapenv:Envelope>
+```
+
+```
+</soapenv:Body>
+</soapenv:Envelope>
+```
+
+From the PCD-01 payload it is seen that the sensor is certified for multiple transports; Continua pre-Tcode\* PHGs, USB, Bluetooth and ZigBee. The PHG is on a popular operating system and setting the time synchronization to eyeball and wrist watch which has a default accuracy of 120 seconds. The reason for these settings is that the popular operating system allows for user setting of the clock in addition to external synchronization but the operating system does not provide that information to applications. Note that the PID segment PID-3 CX-4 value is an affinity domain using the OID encoding system which is a universal ID type. CX-4 is an HD data type. See clause 9 for background information on PCD and its related terminology. The '&#xD' is an escaped carriage return (0x0D). If the 0x0D character is not escaped, SOAP receivers will convert this character to a line feed (0x0A) according to standard. Since the 0x0D character is the PCD-01 segment separator, it must be escaped in order to preserve it; otherwise the PCD-01 decoder will not be able to properly parse the message.
+
+NOTE – \*After version 1.0, Continua introduced a Tcode element that indicates the transports the specialization is certified for. The Tcode gets added to the specialization value resulting in a number that would be incomprehensible to version 1.0 PHGs. For backwards compatibility, sensors are allowed to provide the specialization with a Tcode value of 0 so version 1.0 PHGs would understand it.
+
+#### 8.10.4 CommunicatePCDData response
+
+This response has an ERR segment with error 'accepted'. The ERR segment can be used to transfer optional information about the transaction and may be included in responses that contain no error. In this case the server has converted the PCD-01 document to a PHMR document and sent it successfully and that information is indicated in the ERR segment.
+
+```
+HTTP/1.1 200 OK
+Server: Apache-Coyote/1.1
+Content-Type: application/soap+xml;action="urn:ihe:pcd:2010:CommunicatePCDDataResponse";charset=UTF-8
+Transfer-Encoding: chunked
+Date: Fri, 01 Mar 2013 16:54:41 GMT
+
+<?xml version='1.0' encoding='UTF-8'?>
+<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
+  <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
+    <wsse:Security
+      xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
+      xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
+      soapenv:mustUnderstand="true">
+      <wsu:Timestamp wsu:Id="TS-14">
+        <wsu:Created>2013-03-01T16:54:41.458Z</wsu:Created>
+        <wsu:Expires>2013-03-01T16:59:41.458Z</wsu:Expires>
+      </wsu:Timestamp>
+    </wsse:Security>
+    <wsa:Action soapenv:mustUnderstand="true">urn:ihe:pcd:2010:CommunicatePCDDataResponse</wsa:Action>
+    <wsa:RelatesTo soapenv:mustUnderstand="true">urn:uuid:1_1362156894340</wsa:RelatesTo>
+  </soapenv:Header>
+  <soapenv:Body>
+    <pcd:CommunicatePCDDataResponse xmlns:pcd="urn:ihe:pcd:dec:2010">
+MSH|^~\&|LNI^d0bed0bed0beabee^EUI-64|||20130301115441.444-0500||ACK^R01^ACK|
+00120130301115453695|P|2.6|||NE|AL|||IHE PCD ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7&#xd;
+MSA|AA|00120130301115453695&#xd;
+ERR|||0^Message_accepted^HL7|I|||PcdToPHMR: XDS Send was successful. Response: null&#xd;
+    </pcd:CommunicatePCDDataResponse>
+  </soapenv:Body>
+</soapenv:Envelope>
+```
+
+#### 8.11 hData Observation Upload example
+
+The following illustrates an example implementation of an Observation Upload using hData. It involves two stages. The first stage is requesting the OAuth token. How one obtains this token is not specified by Continua. In this case, the username-password method is illustrated. The second
+
+stage is the upload of the PCD-01 document using the OAuth token obtained from the authorization service in stage one.
+
+### 8.11.1.1 OAuth bearer token request
+
+```
+POST /oAUTH_Service HTTP/1.1
+Content-Type: application/x-www-form-urlencoded
+User-Agent: HealthLink-mOXP
+Host: 192.168.1.3:8443
+Connection: Keep-Alive
+Accept: application/x-www-form-urlencoded
+Content-Length: 87
+grant_type=password&username=Sisansarah&password=publicpassword&scope=ObservationUpload
+```
+
+### 8.11.1.2 OAuth bearer token response
+
+```
+HTTP/1.1 200 OK
+Server: Jetty/1.9
+Content-Type: application/json;charset=UTF-8
+Cache-Control: no-store
+Pragma: no-cache
+{
+  "access_token": "2YotnFZFEjrlzCsicMWpAA",
+  "token_type": "Bearer",
+  "expires_in": 3600,
+  "refresh_token": "tGzv3JOkF0XG5Qx2TlKWIA",
+  "scope": "ObservationUpload"
+}
+```
+
+### 8.11.1.3 Observation Upload
+
+Note that the relative URL '/PCD01\_Upload' is obtained from the <path> element in the capability exchange.
+
+```
+POST /PCD01_Upload HTTP/1.1
+Content-Type: application/txt
+User-Agent: HealthLink-mOXP
+Content-Encoding: UTF-8
+Host: 192.168.1.3:8443
+Connection: Keep-Alive
+Accept: application/txt
+Authorization: Bearer 2YotnFZFEjrlzCsicMWpAA
+Content-Length: 2818
+MSH|^~\&|LNI Example PHG^ECDE3D4E58532D31^EUI-64|||20130301115450.720-0500||ORU^R01^ORU_R01|
+002013030111545720|P|2.6|||NE|AL|||IHE PCD ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7&#xD;
+PID||28da0026bc42484^&^&1.19.6.24.109.42.1.3&ISO^PI||Piggy^Sisansarah^L.^&^L&#xD;
+OBR|1|JOXP-PCD^LNI Example PHG^ECDE3D4E58532D31^EUI-64|
+JOXP-PCD^LNI Example PHG^ECDE3D4E58532D31^EUI-64|182777000^monitoring of patient^SNOMED-CT|||
+20130301115452.000-0500|20130301115455.001-0500&#xD;
+OBX|1||531981^MDC MOC VMS MDS_PHG^MDC|0|||X|||ECDE3D4E58532D31^ECDE3D4E58532D31^EUI-64&#xD;
+OBX|2|CWE|68218^MDC_ATTR_REG_CERT_DATA_AUTH_BODY^MDC|0.0.0.1|2^auth-body-continua||||R&#xD;
+OBX|3|ST|532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC|0.0.0.1|2.0||||R&#xD;
+OBX|4|NM|532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC|0.0.0.1.2|4||||R&#xD;
+OBX|5|CWE|68218^MDC_ATTR_REG_CERT_DATA_AUTH_BODY^MDC|0.0.0.2|2^auth-body-continua||||R&#xD;
+OBX|6|CWE|532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC|0.0.0.2.1|1^unregulated(0)||||R&#xD;
+OBX|7|CWE|68218^MDC_ATTR_REG_CERT_DATA_AUTH_BODY^MDC|0.0.0.3|2^auth-body-continua||||R&#xD;
+OBX|8|CWE|532355^MDC_REG_CERT_DATA_CONTINUA_PHG_CERT_LIST^MDC|0.0.0.3.1|0^observation-upload-
+soap||||R&#xD;
+OBX|9|CWE|68220^MDC_TIME_SYNC_PROTOCOL^MDC|0.0.0.4|532234^MDC_TIME_SYNC_NONE^MDC||||R&#xD;
+OBX|10|NM|8221^MDC_TIME_SYNC_ACCURACY^MDC|0.0.0.5|120000000|264339^MDC_DIM_MICRO_SEC^MDC||||R&#xD;
+OBX|11||528391^MDC_DEV_SPEC_PROFILE_BP^MDC|1||||X|||1234567800112233^1234567800112233^EUI-
+64&#xD;
+OBX|12|ST|531970^MDC_ID_MODEL_MANUFACTURER^MDC|1.0.0.1|Lamprey Networks||||R&#xD;
+OBX|13|ST|531969^MDC_ID_MODEL_NUMBER^MDC|1.0.0.2|Blood Pressure 1.0.0||||R&#xD;
+OBX|14|CWE|68218^MDC_ATTR_REG_CERT_DATA_AUTH_BODY^MDC|1.0.0.3|2^auth-body-continua||||R&#xD;
+OBX|15|ST|532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC|1.0.0.3.1|2.0||||R&#xD;
+OBX|16|NM|532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC|1.0.0.3.2|24583~8199~16391~7||||R&#x
+D;
+OBX|17|CWE|68218^MDC_ATTR_REG_CERT_DATA_AUTH_BODY^MDC|1.0.0.4|2^auth-body-continua||||R&#xD;
+OBX|18|CWE|532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC|1.0.0.4.1|1^unregulated(0)||||R&#xD;
+OBX|19|CWE|68219^MDC_TIME_CAP_STATE^MDC|1.0.0.5|1^mds-time-capab-real-time-clock(0)||||R&#xD;
+OBX|20|CWE|68220^MDC_TIME_SYNC_PROTOCOL^MDC|1.0.0.6|532224^MDC_TIME_SYNC_NONE^MDC||||R&#xD;
+OBX|21|DTM|67975^MDC_ATTR_TIME_ABS^MDC|1.0.0.7|20130301115423.00|||R||20130301115450.733-
+```
+
+```
+
+0500&#xD;
+OBX|22||150020^MDC_PRESS_BLD_NONINV^MDC|1.0.1|||||X|||20130301115452.733-0500&#xD;
+OBX|23|NM|150021^MDC_PRESS_BLD_NONINV_SYS^MDC|1.0.1.1|105|266016^MDC_DIM_MMHG^MDC|||||R&#xD;
+OBX|24|NM|150022^MDC_PRESS_BLD_NONINV_DIA^MDC|1.0.1.2|70|266016^MDC_DIM_MMHG^MDC|||||R&#xD;
+OBX|25|NM|150023^MDC_PRESS_BLD_NONINV_MEAN^MDC|1.0.1.3|81.7|266016^MDC_DIM_MMHG^MDC|||||R&#xD;
+OBX|26|NM|149546^MDC_PULS_RATE_NON_INV^MDC|1.0.0.8|80|264864^MDC_DIM_BEAT_PER_MIN^MDC|||||R|||201303
+01115453.733-0500&#xD;
+
+```
+
+### 8.11.1.4 Observation Upload response message
+
+The POST response contains the PCD-01 response message in the body.
+
+```
+
+HTTP/1.1 200 OK
+Server: Jetty/1.9
+Content-Type: application/txt
+Content-Encoding: UTF-8
+Connection: Keep-Alive
+Accept: application/txt
+Content-Length: 297
+MSH|^~\&|LNI^d0bed0bed0beabee^EUI-64|||||20130301115441.444-
+0500||ACK^R01^ACK|
+00120130301115453695|P|2.6|||NE|AL|||||IHE PCD ORU-
+R012006^HL7^2.16.840.1.113883.9.n.m^HL7&#xD;
+MSA|AA|00120130301115453695&#xD;
+ERR|||0^Message_accepted^HL7|I|||||PcdToPHMR: XDS Send was successful. Response:
+null&#xD;
+
+```
+
+## 9 The PCD-01 document payload
+
+A PCD-01 document is used to communicate observations over the Services interface. An observation has certain properties that must be assured by the PHG application to provide proper mapping and understanding by downstream systems. Continua has chosen the PCD-01 document standard as the means to package the observations. PCD-01 is an HL7 version 2 type message. The messages have an XML and an EDI form. Continua requires the EDI form. One advantage of the EDI form is that it is the most efficient of the two messaging formats for transferring data over the wire. It is also human readable.
+
+The PCD-01 payload is independent of the transport method; document creation is the same whether one uses hData or SOAP.
+
+The primary source of guidance for creating PCD-01 documents comes from the IHE Patient Care Device Technical Framework Volume 2 Transactions [IHE PCD-01].
+
+### 9.1 PCD-01 fundamentals
+
+An EDI-formatted PCD-01 document consists of a set of segments that look like the following:
+
+```
+
+OBX|9|NM|150456^MDC_PULS_OXIM_SAT_O2^MDC|1.0.0.5|98|262688^MDC_DIM_PERCENT^
+MDC|||||R
+
+```
+
+Each segment starts with a certain recognized segment header code word (MSH, PID, OBR, OBX, etc.) identifying the segment and is terminated by a carriage return (0x0D).
+
+From Table 3.1.4.1.1-1 in [IHE PCD-01], it is seen that PCD-01 allows seven types of segments, three of which are optional. These optional segments are rare in the Continua home environment and their formatting and construction are given limited discussion. The four segments that are of relevance are the message header (MSH), the patient identifier (PID), the observation request (OBR), and the observation result (OBX).
+
+### 9.1.1 MSH header
+
+The MSH segment is self-explanatory; every document needs some type of header. Most of the information in this segment is static. One of the more important fields in this header is a static entry stating that the document is an unsolicited request. In certain HL7 scenarios a request is made to a department for a service to be performed. Once the service is performed, the response is sent back to the requester. In the unsolicited case, a request is often *assumed*. The end recipient receives the document whenever it is generated. The code ORU^R01^ORU\_R01 in the header indicates that the message is an unsolicited request.
+
+### 9.1.2 PID patient info
+
+The PID segment contains patient information. Most of it is demographic information but there is also a set of required entries representing patient identifier codes that only mean something to the end recipient of the document. These codes must be obtained from the recipient out of band; they are not obtained from the sensor devices. One of these components is the patient ID that uniquely identifies the patient to the receiving application/institution. The patient ID bears no relation to the ISO/IEEE 11073-20601 person id though the PHG may use the person id from a given device as a database key to obtain the values to populate the PID segment.
+
+### 9.1.3 OBR observation request
+
+The OBR segment is the observation request itself and it typically contains the details of the request. In the unsolicited case many of these entries are not applicable and are filled with canned values that indicate the unsolicited nature of the request. The OBR also contains the start and end times of the measurements. A PCD-01 document may have more than one OBR segment though it is common to have only one.
+
+### 9.1.4 OBX observation result
+
+The OBX segments represent the observation results in response to the OBR. In the Continua environment OBX segments are also used to report information about the PHG and the sensor device. Most importantly it reports the observation itself.
+
+Each OBX provides a key/value pair where the key is an observation identifier and the value is the observation value. Supporting items in the OBX provide additional information about the value such as its units (if any) and timestamp. There is also information in the OBX that specifies how the value is formatted (number, string, etc.) so the end user can read it. The observation identifiers come from the medical device communication code set (the partition/nomenclature codes). The data transmitted from the sensor device is mapped to the OBX entries. It is important to note that the Services interface has no corollary concept to ISO/IEEE 11073-20601 entities that are used to format and transfer the data across the Personal Health Device interface such as PM-Stores, Scanners, object handles, attribute value maps and configuration ids. Information to be delivered using the Services interface arriving via these entities must be broken into their constituent observations and translated accordingly.
+
+A second important concept is the observation hierarchy. An observational attribute transmitted from a sensor device often has significant contextual information associated with it. The Services interface requires that this contextual information be grouped into logical collections so that a particular group contains all the data relevant for the complete understanding of an observation. In many cases, a single OBX segment describes the measurement and its context. In some cases additional OBX segments are required. These segments are grouped by the observation hierarchy (also known as the containment hierarchy). The hierarchy entry uses a dotted notation to specify which OBX segments are children of a parent OBX. Examples are an [ISO/IEEE 11073-20601] blood pressure reading that contain systolic pressure, diastolic pressure and mean arterial pressure (plus all associated units) or a pulse oximeter reading containing a supplemental-types attribute. In
+
+the first case the systolic, diastolic and MAP values are child OBXes of the parent OBX that designates the non-invasive blood pressure reading. In the pulse oximeter case there happens to be no field available in OBXes containing the SpO<sub>2</sub> and pulse rate information for the supplemental-types. Thus a child OBX is needed in each case for this information.
+
+For the implementer, the generation of OBX segments constitutes the bulk of the work. Even the simplest possible Continua PCD-01 document will contain several OBX segments.
+
+## 9.2 Document structure
+
+Table 9-1 contains a simplified version of the table in [IHE PCD-01] that contains only the required (**bold** text) and optional segments of a PCD-01 document.
+
+**Table 9-1 – Simplified PCD-01 table**
+
+| Segment      | Meaning                       | Usage           | Cardinality   |
+|--------------|-------------------------------|-----------------|---------------|
+| <b>MSH</b>   | <b>Message Header</b>         | <b>Required</b> | <b>[1..1]</b> |
+| {            | --- PATIENT_RESULT begin      |                 |               |
+|              | --- PATIENT begin             |                 |               |
+| <b>[PID]</b> | <b>Patient Identification</b> | <b>Required</b> | <b>[1..1]</b> |
+| [PV1]        | Patient Visit                 | Optional        | [0..1]        |
+|              | --- PATIENT end               |                 |               |
+| {            | ---ORDER_OBSERVATION begin    |                 |               |
+| <b>OBR</b>   | <b>Observation Request</b>    | <b>Required</b> | <b>[1..*]</b> |
+| [NTE]        | Notes and comments            | Optional        | [0..1]        |
+| [TQ1]        | Timing/Quantity               | Optional        | [0..1]        |
+| {            | --- OBSERVATION begin         |                 |               |
+| <b>OBX</b>   | <b>Observation Result</b>     | <b>Required</b> | <b>[1..*]</b> |
+| [NTE]        | Notes and comments            | Optional        | [0..1]        |
+| }]           | --- OBSERVATION end           |                 |               |
+| }            | --- ORDER_OBSERVATION end     |                 |               |
+| }            | --- PATIENT_RESULT end        |                 |               |
+
+In Table 9-1, the curly bracket symbol ({) shows what each segment scopes and the cardinality shows how many times the segment may appear in a given document. From this table one sees that a PCD-01 document consists of one and only one MSH segment and one and only one PID segment which may be followed by at most one PV1 segment. Note that a PCD-01 document *always* refers to one and only one patient.
+
+A given document contains at least one OBR segment but may contain more. The OBR segment, in turn, scopes at least one OBX segment but may contain more. Each OBR may be followed by one optional NTE and/or TQ1 segment and each OBX may be followed by one NTE segment. Continua makes no requirements about the use of any of the optional segments. Details on the construction and use of these segments are found in [IHE PCD-01] and their usage is up to the implementer.
+
+### 9.3 PHG, MDS and metric OBXes
+
+A Continua PCD-01 document will always contain *several* OBX segments in every OBR segment even if the sensor device sends only a single measurement. The reason for the numerous OBX segments is that Continua requires that the *first* OBR of the document contains a set of OBX segments that describes the features of the PHG. These OBX segments are referred to as **PHG-OBXes**. These PHG-OBXes describe features like what sensor specializations and Continua version the PHG has been certified for, its regulation status, the Health & Fitness service classes it has been certified for, and its time synchronization properties. In addition to the PHG-OBXes, Continua requires that *every* OBR segment also contain a set of OBXes that describe the sensor device. These OBX segments are referred to as **MDS-OBXes** since these segments are populated by values that come from attributes in the sensor's MDS object\*. One then has the OBX segments that represent physiological measurements. These OBX segments are referred to as **Metric-OBXes** since they originate from metric objects\* on the sensor. Metric OBXes are created when the PHG receives scan event reports\* or segment data events\* whose observation scans\* contain at least one observational attribute.
+
+NOTE \* – For Bluetooth low energy (Bluetooth LE) devices the white paper [Bluetooth PHDT] provides the matching between the Bluetooth LE services and attributes and the above [ISO/IEEE 11073-20601] representations. As an example, the MDS-OBXes would be populated from the attributes contained in the device information service and whatever current time algorithm the device supports.
+
+Given the above, the simplest Continua PCD-01 document appears schematically as follows:
+
+```
+MSH
+PID
+OBR
+    Set of PHG-OBXes
+    Set of MDS-OBXes
+    Metric OBXes.
+```
+
+It is also possible for a given OBR segment to contain multiple sets of MDS-OBXes. This situation happens if the application wishes to place data received from multiple sensors or the results of a reassociation of the same sensor in a single OBR. The text in [IHE PCD-01] "An OBR Segment will be used for each set of such OBX segments to establish the equipment context for the observations (i.e., whether the interrogation was done in-clinic or remote)" may suggest otherwise but that statement is not applicable to different sensors in the same environment on the same person. When OBXes for an additional sensor (or reassociation of the same sensor) are included the set of MDS-OBXes for the additional sensors (or reassociated sensor) must also be present. In this case the different sensors are being mapped to the same timeline by the PHG. Thus the PCD-01 document might appear schematically as:
+
+```
+MSH
+PID
+OBR
+    Set of PHG-OBXes
+    Set of MDS-OBXes for sensor 1
+    Metric OBXes for sensor 1
+
+    Set of MDS-OBXes for sensor n
+    Metric OBXes for sensor n
+```
+
+Alternatively, if the application chose to place the OBX segments from each sensor or the reassociation in its own OBR, the document might appear as:
+
+```
+MSH
+PID
+OBR # 1
+    Set of PHG-OBXes
+    Set of MDS-OBXes for sensor 1
+    Metric OBXes for sensor 1
+
+OBR # n
+    Set of MDS-OBXes for sensor n
+    Metric OBXes for sensor n
+```
+
+or as some other combination. Note that in all cases the PHG-OBXes appear *only* in the first OBR of the document.
+
+New OBR segments are *always* generated when the time line of a single sensor is broken; for example, when the PHG receives a date-time-adjustment from the sensor.
+
+## 9.4 Segment structure
+
+Segment entries are referred to as *Fields*. A given Field entry may have several *Components*, and a given component may have *Sub-Components*. Within a Field, a component may be repeated. A set of special delimiter characters is used to separate these entities; a field separator, component separator, sub-component separator and repetition separator. In theory these characters can be
+
+anything and are up to the implementer. However, everyone always uses the same set of separators; the OR-bar (|), carat (^), ampersand (&) and tilde (~), respectively. Furthermore, the PCD-01 specification [IHE PCD-01] *requires* that these four separators are used. There is also an escaping symbol that is defined in the grouping. If the PCD-01 message needs to escape some character, this symbol is used. The use of this symbol would occur when a character in the message is one of the separator symbols. In theory this symbol is also up to the implementer. However, the backslash (\) is always used and once again, the PCD-01 specification [IHE PCD-01] requires that the escape symbol be the backslash. It should be noted that HL7 escapes separators in the following way:
+
+\F\ for the field separator
+
+\S\ for a component separator
+
+\T\ for a sub component separator
+
+\R\ for a repetition separator
+
+\E\ for the escape character.
+
+Thus, if the string "The separator characters |^&~ are used in PCD-01." ever showed up in a string data type in a PCD-01 message, it would appear as:
+
+The separator characters \F\\S\\T\\E\\R are used in PCD-01.
+
+The following is an example of how fields, components, sub-components and repetitions might appear in a segment:
+
+```
+|compa1^compb1^compc1&suba1&subb1^compd1~compa2^compb2^compc2&suba2&subb2^compd2|field2|field3|
+```
+
+They can be empty:
+
+```
+|compa1^^compc1&&subb1^compd1~compa2^^compc2&&subb2^compd2||field3|
+```
+
+The separators (shown **bold** below) are defined at the beginning of the MSH segment, an example of which is as follows:
+
+```
+MSH|^~\&|Example PHG^FEEDABEEDADBBEF^EUI-64||||
+20111128105910.708-0500||ORU^R01^ORU_R01|00320111128105910708|P|2.6|||NE|AL||||
+IHE PCD ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7
+```
+
+The field separator is defined as the first character appearing after the MSH identifier. In the above example it is the standard OR-bar (|). It is legal in generic HL7 messages (but illegal in PCD-01) to do as follows:
+
+```
+MSH=|^~\&=Example PHG^FEEDABEEDADBBEF^EUI-64 
+20111128105910.708-0500==ORU^R01^ORU_R01=00320111128105910708=P=2.6===NE=AL 
+IHE PCD ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7
+```
+
+where the field separator (shown **bold** above) has been defined as the equal (=) sign. If an equal sign appears in any one of the field values, it would need to be escaped with the escape symbol (\) and would look like \F\ in the PCD message where '\F\' would be replaced by '=' when unescaping.
+
+A field is the value contained between the OR-bars. Empty fields are designated by two separators with nothing in them, for example ||. Continua encourages users to terminate the segment when the last non-empty field is in place (it is a '**should**' and not a '**shall**'). A terminating separator is not needed on that last field; the segment terminator is sufficient. The following is desired:
+
+```
+OBX|9|NM|150456^MDC_PULS_OXIM_SAT_O2^MDC|1.0.0.5|98|262688^MDC_DIM_PERCENT^MDC||||R
+```
+
+though it is also legal to do
+
+```
+OBX|9|NM|150456^MDC_PULS_OXIM_SAT_O2^MDC|1.0.0.5|98|262688^MDC_DIM_PERCENT^MDC||||R|
+```
+
+or
+
+```
+OBX|9|NM|150456^MDC_PULS_OXIM_SAT_O2^MDC|1.0.0.5|98|262688^MDC_DIM_PERCENT^MDC||||R|||
+```
+
+It is common practice to refer to the fields of a given segment using the expression 'segment name – number', for example, OBX-3. Appendix B of [IHE PCD-01] makes extensive use of this notation to explain in detail what each field in each segment type contains. In the following segment—
+
+```
+OBX|9|NM|150456^MDC_PULS_OXIM_SAT_O2^MDC|1.0.0.5|98|262688^MDC_DIM_PERCENT^MDC||||R
+```
+
+Where:
+
+- OBX-1 is 9
+- OBX-2 is NM
+- OBX-3 is 150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC
+- OBX-4 is 1.0.0.5,
+- ...
+- OBX-7 is empty,
+- ...
+- OBX-11 is R, and
+- OBX-12 through OBX-20 are all empty and therefore not included.
+
+There are two possible points of confusion when using this notation. Since there may be multiple OBR and OBX segments in a given document, these segments also have sequence numbers. The following section of a PCD-01 document
+
+```
+OBR|1|JOXP-PCD^Example_PHG^FEEDABEDEADBEEF^EUI-64|JOXP-PCD^Example_PHG^FEEDABEDEADBEEF^EUI-64|182777000^monitoring of patient^SNOMED-CT|||20111128105909.236-0500|20111128105911.237-0500
+OBX|1||531981^MDC_MOC_VMS_MDS_PHG^MDC|0|||||X|||||FEEDABEDEADBEEF^^FEEDABEDEADBEEF^EUI-64
+OBX|2|CWE|68218^MDC_ATTR_REG_CERT_DATA_AUTH_BODY^MDC|0.0.0.1|2^auth-body-continua|||||R
+OBX|3|ST|532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC|0.0.0.1.1|1.5|||||R
+OBX|4|NM|532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC|0.0.0.1.2|16391~8199|||||R
+```
+
+illustrates sequence numbers (**bold**). They are given in OBR-1 and OBX-1. It is easy to think that OBX-3 refers to the OBX segment with sequence number 3. It is not. OBX-3 is the third field of any OBX segment. In the case of the OBX with sequence number 3, OBX-3 is the string 532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC.
+
+Given that, there is a twist when identifying the nth field of the MSH header:
+
+```
+MSH|^~\&|Example_PHG^FEEDABEDEADBEEF^EUI-64|||20111128105910.708-0500||ORU^R01^ORU_R01|00320111128105910708|P|2.6|||NE|AL|||||
+IHE_PCD_ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7
+```
+
+One might be inclined to believe that MSH-1 in the example above is the set of characters ^~\&. However, it is the '|' after the MSH designator. That is because the first field in the MSH segment *defines* the field separator which is then used in the rest of the PCD-01 document as a separator. So the first | of the MSH segment (and only the MSH segment) is a field and not a field separator. MSH-2 is ^~\& which defines the remaining separators and escape symbols.
+
+The component separator ^ delineates parts of a single field. A good example for the use of the component separator would be when reporting the three components of an acceleration,  $|x_1^y_1^z_1|$ . All three components are needed to describe the single acceleration measurement. The repetition character ~ would be used if one is reporting a sequence of acceleration measurements (perhaps at different times) within a single field  $|x_1^y_1^z_1~x_2^y_2^z_2~x_3^y_3^z_3|$ . Each  $x_n^y_n^z_n$  entry completely describes a given entity/measurement. The concept is that the component separator is used when the entity or measurement needs to be represented in parts but only when all the parts are put together does one completely describe the entity/measurement. The repetition character is used when the
+
+entity/measurement is of the same type but there are multiple occurrences. Each entry between the repetition characters completely describes the entity/measurement.
+
+An additional example of a field that has components is the patient's name in the PID segment. It consists of several components; family name, first name, middle name, title, suffix, etc. These components are all separated by ^ since together they identify the patient. On the other hand, fields containing lists would use the repetition character. One of the MDS-OBXes reports the specializations supported by a given sensor. If the sensor supports more than one specialization, the specialization entries are separated by ~.
+
+The sub-component separator & is used when a component itself consists of several parts. This situation is rare in the Continua environment.
+
+## 9.5 PCD-01 format "on the wire"
+
+The default encoding of the segments and fields of a PCD-01 document on the wire is using the ASCII-127 character set. However, other formats are allowed including non-alphabetic character sets. The entire list is given in Table 0211 located in Version 2.6 Chapter 2 Control of the HL7 standard. Which character encoding is used is specified in MSH-18. If MSH-18 is empty, the encoding defaults to ASCII-127. However, in Continua where the [ISO/IEEE 11073-20601] specification requires the use of ASCII-127 in string values, PCD-01 tends to be either ASCII-127 or Unicode UTF-8. Using UTF-8 would allow, for example, non ASCII-127 fields in the MSH, PID and OBR segments whose fields are not derived from [ISO/IEEE 11073-20601] transactions while being compatible with the ASCII-127 fields in the OBX segments.
+
+## 9.6 HL7 data types
+
+Each field in each OBX segment is a pre-specified HL7 *data type*. Within a given field the allowed data type may repeat. There are numerous HL7 data types. Some of them are quite complex and contain several components whereas others consist of a single component. Some data types nest other data types. The data type NM is an example of a simple data type. It states that the field is a number (containing only digits, +, - and.). The most common data types that are used in PCD-01 are given in [IHE PCD-01] Table C-1 and are described in detail in [IHE PCD-01] Appendix C. Data types, like segments, are terminated at their last non-empty component. A terminating ^ is also not needed; another terminating symbol will always be present (for example, a field or repetition symbol) and suffices.
+
+Some of the rules for data type usage have been restricted by Continua services design guidelines; in particular which components of the data type are allowed to be empty and which are not. The Coded With Exceptions (CWE) data type is used in these guidelines when representing nomenclature codes. In HL7 this data type has nine components, the first six of which are required. HL7 allows all components to be empty *except* the second. When coding nomenclature codes, Continua allows the second, fourth, fifth and sixth component to be empty and requires entries in the first and third component.
+
+The reason for this deviation from HL7 becomes apparent when one examines how the CWE type is used when encoding nomenclature values. The first component is the code (partition and nomenclature), the second is the reference Id that names the code, and the third is the coding system (which is always MDC in Continua use cases). An example of a CWE encoded oxygen saturation code on the pulse oximeter would be 150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC. A PHG receives *only* the code on the wire. The associated name must be looked up in some type of database. For future specializations and private (proprietary) nomenclature codes, the name of the code may not be known. If the name is allowed to be empty, the PHG can still create a PCD-01 document using just the code and coding system, for example 150456^^MDC. This construction allows the existence of headless service PHGs that simply pass the information collected from sensors to a back end. The same applies when these guidelines are used to encode the ASN.1-BITS fields as a CWE data type.
+
+Data types use the same 'index notation' to identify their components as segments. CWE-2 identifies the second component of the CWE data-type and EI-3 means the third component of the EI data type. There is no such standard designation for the n-th repetition of a data type.
+
+The only HL7 data types used in PCD-01 OBX segments created from ISO/IEEE 11073-20601 sensors are:
+
+- CWE Coded With Exceptions (used for MDC codes, BITS fields and integer enumerations)  
+Used whenever one has a code that has a specific meaning
+- DTM Date Time (used for timestamps)
+- EI Entity Identifier
+- NM A number
+- ST A string
+- NA An array of numbers (used in RTSAs)
+
+The entity identifier (EI) was incorrectly represented in some cases in versions prior to these guidelines and has caused confusion. The EI data type has four components; the first two are used when a locally defined coding system is used, and the last two are used when a universally defined coding system is used. "*EUI-64*"s and "*OID*"s are an example of universal ID types, thus coding something like an ISO/IEEE 11073-20601 system id requires the use of EI-3 for the system id with an EI-4 value of "*EUI-64*". It should also be noted that HL7 requires an entry for EI-1 even in the universal-id case. A compliant entry for "*EUI-64*" type codes in EI-1 would be a duplicate of the EI-3 entry, for example `FEEDABEEDEADBEEF^^FEEDABEEDEADBEEF^EUI-64`. It could also be `Continua_PHG_4.0^^FEEDABEEDEADBEEF^EUI-64`.
+
+The following is NOT correct: `FEEDABEEDEADBEEF^EUI-64`
+
+## 9.7 PID segment
+
+There are two fields in the PID segment that are required. One is the patient identifier (PID-3) and the other is the patient name (PID-5). The patient name is self-explanatory. It is represented by the XPN data type which contains multiple components; family name, given (first) name, middle name, suffixes (like Sr. or Jr.), etc. See Table E.62 for details. The patient identifier, on the other hand, is a set of opaque codes that only mean something to the eventual recipient of the document. In HL7 XDSb transactions these codes are used to authenticate and identify the user to the document registry. The use of these codes is ubiquitous in HL7 Connectathons.
+
+The CX data type contains three required entries, the ID (CX-1) which is a string, the assigning authority which is an HD data type (CX-4), and the identifier type code which is an ID (CX-5). In HL7 CX-5 may be empty. In most cases only the first component of the HD data type is used when representing the assigning authority. The ID and assigning authority are provided by the institution maintaining the registry. The assigning authority is often the affinity domain which is a code that identifies the enterprise the institution belongs to. CX-5 is a string code whose possible values are one of 97 given in Table 0203 in HL7 CH02A DataTypes. The code "PI" is defined as a 'Patient Internal Identifier' which is a number that is unique to a patient within an Assigning Authority. This code suffices for most Continua use cases.
+
+If the assigning authority value in CX-4 is one of the universal identifiers like a EUI-64, ISO, or OID, instead of a local identifier, subfields of the HD data type are required. This situation requires the use of the sub-component delimiter (&). An example would be
+
+```
+PID||28da0026bc42484^^&1.19.6.24.109.42.1.3&ISO^PI||Piggy^Sisansarah^^^^  
+L&#xD;
+```
+
+This type of identity code is ubiquitous identifying HL7 enterprise affinity domains.
+
+The challenge is that none of the necessary data for these fields is provided by the sensors. Therefore, the PHG needs to provide this information, for example, through the use of the ISO/IEEE 11073-20601 person-id and sensor system-id as a key to a database containing all the necessary codes, patient name, and any other PID related demographic information one may wish to provide. If it is known that the end recipient is not going to use the patient identifier (PID-3) one can enter anything into these fields though it may be more appropriate in that case to use PT for CX-5, which is an external patient identifier, instead of PI which is associated with an HL7 affinity domain.
+
+## 10 OBX segment fundamentals
+
+This clause covers the fundamentals of generating OBX segments from 11073-20601 data.
+
+### 10.1 Encoding OBX segments
+
+An OBX segment is a key-value pair where the key indicates what the value is. The key is placed in OBX-3 and the value in OBX-5. The remaining fields provide support and organizational information for this key-value pair. There are 20 possible fields in a PDC-01 OBX segment. Continua PCD-01 OBX segments use about half of them.
+
+The role of each field is illustrated using an OBX segment generated from an ISO/IEEE 11073-20601 scan event report containing a weight measurement. The scan event report's observation-scan contains a basic-nu-observed-value, timestamp, and object handle value. The handle points to the MDC\_MASS\_BODY\_ACTUAL numeric metric object maintained by the PHG for context. The generated segment appears as follows:
+
+```
+OBX|26|NM|188736^MDC_MASS_BODY_ACTUAL^MDC|1.0.0.13|70.7|263875^MDC_DIM_KILO_G^MDC|||R||2012  
+0628145624.000-0500
+```
+
+**OBX-1** is the *sequence number* which in this case is 26. It starts at one and increases by one for each new OBX segment in an OBR. For a new OBR, the process repeats. Its purpose is purely organizational and indicates the order in which the segments are added to the OBR. The '26' in the example indicates there are 25 OBX segments prior to this one in this particular OBR.
+
+**OBX-2** is the HL7 data type of the value which appears in OBX-5. This standard specifies how the ISO/IEEE 11073-20601 attribute value is mapped to the HL7 data type. For example, basic-nu and simple-nu observational attributes are mapped to the NM data type which is a number. Thus the 70.7 in OBX-5 is interpreted as a number.
+
+**OBX-3** states what the value in OBX-5 actually *is* (a temperature, a device serial number, etc.). For Continua PCD-01 OBX-3 is always expressed as an MDC nomenclature code using the CWE data type. In this case OBX-3 comes from the TYPE attribute of the context body-mass metric object maintained by the PHG. The MDC\_MASS\_BODY\_ACTUAL indicates that the number in OBX-5 represents a body mass.
+
+**OBX-4** is the hierarchy. It groups OBX segments together, for example when more than one OBX segments are needed to describe a measurement. The hierarchy is discussed in clause 10.2.
+
+**OBX-5** is the value. In this case it is the body mass 70.7. It is obtained from the basic-nu attribute value. It is possible that OBX-5 is empty but for OBXes containing physiological measurements an empty value only happens if a special value like a NaN is received.
+
+**OBX-6** gives the units for the value in OBX-5. For Continua PCD-01 the units are always expressed as an MDC nomenclature code using the CWE data type. If the measurement has no units (for example the medication monitor feedback entries) this field is empty. In the case above, the MDC\_DIM\_KILO\_G entry is obtained from the unit code attribute of the context body-mass metric object maintained by the PHG. Thus the 70.7 in OBX-5 is kilograms.
+
+**OBX-8** (empty in the example) would be non-empty if the ISO/IEEE 11073-20601 scan event report observation scan contains a Measurement Status attribute or the measurement value is one of the special values (NaN, +/- Infinity, etc.). An entry in OBX-8 will affect the value in OBX-11.
+
+**OBX-11** is a terse indicator of the measurement status. This field is always valued and for physiological measurements it is 'R' (results entered – not verified) unless an OBX-8 entry alters it. For OBX segments that have no OBX-5 value, this entry is 'X' (results cannot be obtained for this observation).
+
+**OBX-14** is the timestamp of the measurement formatted as a DTM data type. Ideally the PHG presents the sensor's timestamp as local time plus offset to UTC time. If the sensor's time synchronization is superior to the PHG's, the PHG uses the sensor's time exclusively. The offset in the DTM data type is the number of hours one adds/subtracts to/from the UTC time to get the local time. The subject of timestamps is complex and the clause D.1.5 Timestamping and time synchronization in the guidelines is dedicated to it.
+
+**OBX-18** is only used in PHG and MDS OBX segments as it identifies the equipment; PHG or sensor.
+
+**OBX-20** is used for indicating the body site of a measurement. In Continua usage it is only populated when a Supplemental-Types attribute has an entry whose partition value is MDC\_PART\_SITES.
+
+## 10.2 Object hierarchy
+
+The object hierarchy is a means to indicate scoping; in other words which OBX segments are children of other OBX segments. It allows OBX segments to be grouped into sets. A "dotted-notation" is used to indicate the hierarchy. This notation consists of a numeric tuple with a dot in-between the members which indicate a particular item's place in the object hierarchy. [IHE PCD-01] defines the hierarchy as containing the following levels:
+
+MDS [. VMD [. CHANNEL [. METRIC [. FACET [. SUBFACET]]]]].
+
+An example might be |3.0.3.2.1.1|. In Figure 10-1 is an example of several 'segments' that illustrate the containment hierarchy concept. For brevity, only the OBX-4 hierarchy field of the OBX segments is shown.
+
+![Figure 10-1 – Containment hierarchy diagram showing a list of hierarchy levels: |1|, |1.0.0.1|, |1.0.0.2|, |1.0.0.2.1|, |1.0.0.2.2|, and |1.0.0.3|. The levels |1.0.0.2.1| and |1.0.0.2.2| are highlighted in blue.](2aa94b70ba3fadcba8420d9e3128253a_img.jpg)
+
+|           |
+|-----------|
+| 1         |
+| 1.0.0.1   |
+| 1.0.0.2   |
+| 1.0.0.2.1 |
+| 1.0.0.2.2 |
+| 1.0.0.3   |
+
+H.812.1(16)\_F10-1
+
+Figure 10-1 – Containment hierarchy diagram showing a list of hierarchy levels: |1|, |1.0.0.1|, |1.0.0.2|, |1.0.0.2.1|, |1.0.0.2.2|, and |1.0.0.3|. The levels |1.0.0.2.1| and |1.0.0.2.2| are highlighted in blue.
+
+**Figure 10-1 – Containment hierarchy**
+
+Since the MDS-tuple in each case above has the same value, all the segments are part of a single MDS object. In the ISO/IEEE 11073-20601 case that would mean they all originate from the same association. Within the segments the set that has the same METRIC-tuple '2' indicates that whatever is being described here needs all three segments to complete the description.
+
+### 10.2.1 Hierarchy levels
+
+The five levels MDS, VMD, CHANNEL, METRIC, FACET and SUBFACET are defined in [IEEE 11073-10201]. In [ISO/IEEE 11073-20601], the virtual medical device (VMD) is not used and thus its 'tuple' value is always 0.
+
+The MDS level in [ISO/IEEE 11073-20601] defines the association. The hierarchy is started with the set |x.0.0.0| or |x| for brevity; it is common practice to leave off trailing tuples that are all 0. 'x' is
+
+the MDS object *instance* and bears no relation to the MDS object handle. 'x' is often 1 but it can be anything except 0 even if there is only one association represented ( $x = 0$  is reserved for PHG-OBXes). If a new association takes place and the OBX segments are placed under the same OBR, a new MDS instance value would be needed. Typically the index is incremented to maintain dictionary ordering but all that is required is that it be different.
+
+Semantically, the CHANNEL is not present in 11073-20601. In [ISO/IEEE 11073-20601] metrics from different sensors, locations, or sources can be represented as coming over different channels. However, the Channel placeholder tuple is 'borrowed' in Continua PCD-01 when compound numeric attributes are translated. The compound TYPE is placed on the channel and the individual compound entries are placed at the METRIC-level instead of placing the TYPE at the METRIC-level and making the compound entries facets. This usage is confusing to new readers familiar with the ISO/IEEE 11073-20601 semantic meaning of a compound value. The reason for its usage is to reduce the number of extra facets and subfacet levels that might be needed in the compound case over that of the non-compound case. If it were possible to have facets of the individual compound entries, then the approach would reduce the need for extra facet levels. At this time the current version of [ISO/IEEE 11073-20601] does not result in any facets or subfacets to the compound entries.
+
+The METRIC object level represents the measurement or item, or as stated in [IHE PCD-01] the "parametric instance". Like the MDS object level, it is an *instance* of a metric and bears no relation to the ISO/IEEE 11073-20601 handle value of a given object. Each new measurement/item is designated by a different instance value even if they come from the same ISO/IEEE 11073-20601 object.
+
+The FACET and SUBFACET are used when an IEEE 11073-20601 measurement or item contains information that cannot find a place in the parent OBX. In a colloquial sense one could say the parent OBX has run out of acceptable fields for this additional information. An example would be a pulse oximeter measurement containing a supplemental-types attribute. The supplemental types attribute contains a list of one or more MDC codes. In the parent OBX, all candidate fields that one could potentially use for these values are already occupied. Thus one needs to create a FACET OBX and place the additional information into the fields of the facet. The facet indicates that both segments are needed to completely describe the measurement.
+
+## 10.2.2 Hierarchy examples
+
+It is important to recall that a set of OBX segments are scoped by an OBR. Thus the n-tuples within the OBX segments scoped by one OBR bear no semantic relation to the OBX segments scoped by another OBR. Furthermore, as stated in [IHE PCD-01], the only requirement on the values of the n-tuples is "These must create unique n-tuples for each OBX. (That is, each OBX in a set grouped within the scope of an OBR segment must be distinct)." There is also no relation between the OBR sequence number and the MDS n-tuple value as has been incorrectly assumed based on prior versions of the design guidelines. Consequently the MDS-tuple of the first association in OBR|2| does not have to be 2 though it could be.
+
+The set of OBX-4 notations in Figure 10-1 could be written as:
+
+```
+|3.0.0.1|  
+|3.0.0.5|  
+  |3.0.0.5.6|  
+  |3.0.0.5.2|  
+|3.0.0.3|
+```
+
+with no loss of semantic information. The relationship between the segments is the same. The following set, on the other hand, would be incorrect if it were to represent the same semantic information as in Figure 10-1.
+
+```
+|3.0.0.11|
+|3.0.0.5|
+|3.0.0.6.6|
+|3.0.0.5.2|
+|3.0.0.3|
+```
+
+since the OBX segment |3.0.0.6.6| is no longer part of the group scoped by |3.0.0.5|. It also has no parent OBX.
+
+That being said, [IHE PCD-01] recommends that implementers use dictionary ordering (as in Figure 10-1). Dictionary ordering also provides some type of time ordering since new metric instances are usually created as new measurements are received. Readers of the document are also likely to appreciate dictionary ordering.
+
+### 10.2.3 Object hierarchy for compounds
+
+Compound numeric measurements in Continua PCD-01 are not treated as another metric instance. Instead, a "channel" tuple is instantiated when a compound numeric is needed. An example would be:
+
+(15 prior metric instances)
+
+```
+|1.0.0.16|
+|1.0.1|      // First compound metric instance
+|1.0.1.1|    // Compound value 1
+|1.0.1.2|    // Compound value 2
+|1.0.1.3|    // entry from an extra descriptive attribute such as supplemental types
+|1.0.0.17|    // Some other non-compound measurement
+|1.0.2|      // Second compound instance
+|1.0.2.1|
+|1.0.2.2|.
+```
+
+Dictionary ordering cannot be easily maintained with the Continua use of the channel for compounds, but one can keep independent dictionary orderings for the compound and non-compound metrics.
+
+### 10.3 Timestamping
+
+In the Continua use case it is generally assumed that sensors will not have the capability to obtain a good sense of time on their own. They will rely on the ISO/IEEE 11073-20601 SetTime action or the user to set the time, use a simple relative time tick, or provide no timestamp at all. In a local environment these time limitations do not pose a problem. However, data that is sent over the Services-IF can travel around the world making it necessary to provide timestamps that can be unambiguously interpreted regardless of destination.
+
+It is also important that the timestamps provided come from the same unbroken timeline otherwise the differences between any two timestamps would be ambiguous. If all sensors were using Universally Coordinated Time (UTC) that would not be a problem but many sensors only have a sense of local time. Thus if the user resets the sensor clock due to time zone changes, daylight saving time, or clock drift, the timeline is broken. A thirty minute difference may suddenly appear to be ninety minutes. There is no way for the PHG to know about this change without some indication from the sensor. ISO/IEEE 11073-20601 sensors that break their timeline while associated are required to send date-time-adjustment notifications. These date-time-adjustments tell the PHG what to add to the previous timestamps to bring those timestamps up to the sensor's current time line. Sensors that are storing data offline are required to begin storing data in new PM segments on time changes indicating so by adding date-time-adjustment attributes in the affected PM segments. ISO/IEEE 11073-20601 sensors are required to assure a contiguous time line, thus if a sensor time-faults (the continuity of the time line has been lost) the sensor is not to send such data.
+
+There are currently proposals in the ISO/IEEE 11073-20601 working group to allow such data to be sent along with an indicator. The indicator allows the PHG to identify the cases where the timestamps may be both unreliable and non-contiguous. At the moment there is no means to indicate in the PCD-01 document that the timeline is non-contiguous; timelines in PCD-01 are always assumed to be contiguous. To handle these cases some type of indicator will be needed in future versions of the PCD-01 standard.
+
+It should also be pointed out that Continua has temporarily allowed sensors that break time continuity due to resource limitations to be certified. In particular, sensors that store data and change their timelines are allowed to do so without the ISO/IEEE 11073-20601 mandated date-time-adjustments. In this case there is no indication that the sensors are not reporting a contiguous timeline. PHGs handling these sensors that wish not to propagate such data over the Services interface will need to keep a black list of such sensors.
+
+In order to assure unambiguous representation of measurement timestamps in all time zones, Continua requires that PHGs supporting Observation Upload be capable of synchronizing to 'qualified' time. The PHG is to map the sensor time line to this qualified time if necessary. To clarify, 'qualified' time is any time synchronized to UTC with or without knowledge of local time. It is highly recommended that Observation Upload PHGs also be local time aware which comes at minimal additional cost once UTC synchronization is in place. It should also be noted that qualified time by itself does not mean accurate; the accuracy of the qualified time depends upon the synchronization method.
+
+In order for the PHG to be able to map the sensor time line to its UTC time line, Continua requires that if the sensor uses timestamps in any of its measurements that the sensor be able to provide the PHG with its sense of current time. Associated with this requirement is that if sensors store any measurements, they must also provide timestamps which means that all sensors that store data must also be capable of providing a current time. The PHG is then able to compare the sensor's sense of current time with its sense of current time and if necessary, translate the sensors time line to its qualified time line. In PCD-01 language, there is a special *coincident timestamp pair* OBX segment that contains this comparison. With the coincident timestamp pair, even sensors that may default back to some fixed factory programmed initial time upon say a battery change will be able to have their timestamps translated to correct qualified values by a properly synchronized PHG.
+
+With sensors that use absolute time it is not possible for the PHG to unambiguously provide the offset in the time zone that the sensor took the measurement. Even though sensor devices report date-time-adjustments when changing their clocks, the PHG does not know if the adjustment is due to clock skew corrections, daylight savings time changes, time zone changes, or some combination of the previous. However, the reader of the document will be able to obtain the original timestamp sent on the wire to the PHG. With sensors that use base offset time, the PHG will be able to present the time zone of the original measurement, even for those sensors that do not use UTC as the base in their base offset time clocks. In all cases it is assumed that when a sensor associates with a PHG, that the current time reported by the sensor is in the time zone of the PHG. If the sensor has been transported across time zones, it may rely on the user to properly adjust its clock before use. Improper use of a sensor by a user is out of scope of these guidelines.
+
+To address the issue of date-time-adjustments, the [IHE PCD-01] specification requires the creation of a new OBR segment. All OBXes in an OBR segment come from the same unbroken timeline whose time range is delimited by OBR-7 and OBR-8. An alternative solution could have been to adjust the sensor's timestamps by the date-time-adjustment values but there would be no knowledge that adjustments occurred or what the reason for the adjustment was. There is no good solution to the latter problem as long as sensors report only local (absolute) times. The use of the ISO/IEEE 11073-20601 base offset time resolves several of these issues. Changing time zones and daylight savings changes can be reflected in the offset which does not affect the base time. Date-time-adjustments only occur if the base time is, for some reason, changed.
+
+In the Continua use case most sensors are expected to have poorer time capabilities than the PHG and the PHG will translate the sensor time lines to its qualified time line. However, if the sensor happens to support an external means of synchronization to UTC that is more accurate than the PHG's clock one does not Service the PHG to translate the sensor's timestamps. In these design guidelines the possibility of superior sensor timestamps is taken into account. The PHG can use the MdsTimeInfo attribute from the sensor to determine who is better synchronized and if the sensor has superior synchronization, the PHG will not translate the times. When more acute care type devices start making their way into the home this case may start to appear.
+
+The next notch upward in sensor sophistication is sensors that can be externally synchronized by the PHG's clock. This capability is out of band with respect to the Personal Health Devices interface. The PHG becomes a time synchronization service and serves as the master clock for the timestamps generated by the sensor, for example using the PHG's Bluetooth clock. In this scenario relative times stamps are typically used where the PHG synchronizes its relative clock to an external NTP source to map the relative times to qualified times. Should this situation apply, these capabilities are reported in the PCD-01 document as noted in the timestamp and time synchronization clause.
+
+#### 10.4 The coincident timestamp pair
+
+The coincident timestamp pair MDS-OBX segment contains both the current time of the sensor and the current time of the PHG and allows one to compare the two timelines. If the sensor did not use timestamps at all, these attributes would not be present and there would be no coincident timestamp pair. In versions prior to these design guidelines the PHG always translated and/or corrected the sensor's timestamp in any measurement to its timeline using the coincident timestamp pair if it existed and placed the translated and/or corrected timestamp in the Metric-OBX. If the sensor provided no timestamp in the measurement, the PHG used the time of reception of the measurement in the Metric-OBX.
+
+In these design guidelines the PHG is first required to check the sensor's time synchronization information as returned in the Mds-Time-Info attribute and determine who is better synchronized (see clause D.1.5.3). The key fields in this attribute used to make this determination are:
+
+- the time capability bits (which also report if the sensor is currently synchronized in addition to its capabilities),
+- the time synchronization protocol (which reports the protocol used to obtain this synchronization), and
+- the time synchronization accuracy.
+
+The rigorous description of the algorithm is given in clause D.1.5.3. If the PHG determines that the sensor is better synchronized, the PHG no longer generates the coincident timestamp pair. The sensor's time capabilities, time synchronization and time synchronization accuracy are reported. When a measurement is received, the sensor's timestamp is used without translation and/or correction but it is formatted to a DTM data type in the Metric-OBX.
+
+If the PHG determines that it is better synchronized than the sensor or the sensor uses one of the relative times, a coincident timestamp pair OBX is required as in the versions prior to these design guidelines. The sensor's time capabilities, time synchronization protocol, and if present the time synchronization accuracy, are also reported. The coincident timestamp pair OBX is created as follows:
+
+OBX-3 contains the MDC code of the sensor's time attribute. It will be either the Date-and-Time, Base-Offset-Time, Relative-Time, or HiRes-Relative-Time attribute. OBX-5 will be the value taken from the attribute formatted as a number if it is one of the relative times and as a DTM timestamp if it is the absolute or base offset time. OBX-2 is then either NM or DTM, accordingly. The PHG's current time is then placed in OBX-14 as a DTM data type regardless of the sensor's time format. In
+
+case of the relative times there will also be an OBX-6 entry for the time units and for the relative time value in OBX-5 a conversion of the ISO/IEEE 11073-20601 value to the required units.
+
+The PHG uses the information in the coincident timestamp OBX to take measurement timestamps provided by the sensor and map them to local time plus offset to UTC time (the offset is the hours *added* to UTC time to get local time so EST is -0500) in Metric-OBXes. The coincident timestamp pair also reveals any differences between the sensor's and PHG's notion of current time. If there are any differences, the PHG notes that difference and applies it to subsequent measurement times stamps received from the sensor. Thus if the sensor clock is noted to be 20 seconds behind the PHG's clock, the PHG will add that 20 seconds to the timestamps in all subsequent Metric OBXes. The coincident timestamp pair also allows one to recreate the original sensor timestamps for auditing purposes; for example in the above case by subtracting 20 seconds from each of the corrected timestamps one will obtain the sensor's timestamp as sent on the wire.
+
+In the case of relative times, the PHG uses the coincident timestamp pair to establish the '0' point on the time axis. If the sensor uses relative time (units are 1/8 ms) it might report a current relative time of 14905355. The PHG notes its current time is January 3rd, 2014, 10:14:40 EST. The PHG then receives a scan event report and the relative time is 14105355. The difference is -800000 which means the measurement was actually taken 100 seconds earlier (this scan event report must have been a temporarily stored measurement). The PHG would then subtract 100 seconds from its time reported in OBX-14 of the coincident timestamp pair OBX and place that result in OBX-14 of the Metric-OBX.
+
+If the PHG receives a measurement that contains no timestamp, the PHG places the time of reception of the measurement into OBX-14 of the Metric-OBX as was done in the versions prior to this version of the guidelines. Furthermore, if the sensor does not use timestamps in any of its measurements, [ISO/IEEE 11073-20601] does not require that the sensor report current time or MdsTimeInfo in its MDS. In that case there will be no coincident timestamp pair in the MDS-OBXes and no time capabilities or time synchronization information.
+
+## 10.5 PHG-OBXes
+
+PHG-OBX segments are unique to Continua. They are created once per PCD-01 document and are placed under the first OBR. The first PHG-OBX segment that occurs is called the top-level OBX and appears as follows:
+
+```
+OBX|1||531981^MDC_MOC_VMS_MDS_PHG^MDC|0|||X|||0000ABEED DEADBEEF^^0000ABEED DEADBEEF^EUI-64
+```
+
+Every field in this OBX is the same for all PHGs except OBX-18 which is the PHG's system Id as an EI-data type. The EI data type has four components and the use of these components depends upon whether the identifier being used is 'local' or universal. [ISO/IEEE 11073-20601] system ids are encoded using the EUI-64 profile which is a universal identifier type. Thus, the universal id type component EI-4 is used instead of the local identifier EI-2. EI-4 is always EUI-64. The system id is the universal identifier which is in EI-3 and if a EUI-64 type, EI-3 is always encoded as a HEX sequence with 16 HEX digits without the 0x prefix commonly used in programming languages. Leading zeros are filled in if needed. EI-1 is a unique identifier of some type and for Continua PHGs and sensors expressing the system Id, EI-1 may have the same value as EI-3 in the same format. In other contexts where the identifier is not universal, EI-1 and EI-2 are used.
+
+The hierarchy in OBX-4 uses the special MDS tuple-value of '0' to indicate that this OBX segment represents the PHG. The single '0' indicates that it is the top-level OBX. It is standard practice to drop trailing zeroes in the hierarchy notation. |0| is short for |0.0.0.0.0.0.0.0|.
+
+OBX-11 is used to represent the status of the measurement. Following [IHE PCD-01] which states "The value of X is used for device related segments where OBX-7 is not used to express the device measurement range capability", one would think that all PHG and MDS OBX segments would have
+
+OBX-11 to set X (measurement not obtainable). However, in [IHE PCD-01] the only device-related segments that appear are what Continua refers to as top-level segments. These special segments have no OBX-2 or OBX-5. What is not considered in [IHE PCD-01] is the case where device information is reported in OBX-5, such as battery level, serial number and current time. Though these OBX segments are clearly device-related, the [IHE PCD-01] specification makes no provision for this case; the specification states that if OBX-11 is set to X it indicates an OBX-5 of null. To be most compatible with the PCD guidelines, device-related OBX segments with non-null OBX-5 values set OBX-11 to R (non-validated measurement received).
+
+The remaining PHG-OBX segments contain certification, regulatory information and time synchronization information. To create these OBX segments the PHG is treated as if it had an [ISO/IEEE 11073-20601] MDS object with a Reg-Cert-Data-List and Mds-Time-Info attribute.
+
+The Continua regulatory information is encoded as follows:
+
+```
+OBX|n|CWE|68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC|0.0.0.x|2^auth-body-continua|||||R
+OBX|n+1|ST|532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC|0.0.0.x.1|4.0|||||R
+OBX|n+2|NM|532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC|0.0.0.x.2|16391~8199|||||R
+OBX|n+3|CWE|68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC|0.0.0.x+1|2^auth-body-continua|||||R
+OBX|n+4|CWE|532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC|0.0.0.x+1.1|1^unregulated-
+device(0)|||||R
+OBX|n+5|CWE|68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC|0.0.0.x+2|2^auth-body-continua|||||R
+OBX|n+6|CWE|532355^MDC_REG_CERT_DATA_CONTINUA_PHG_CERT_LIST^MDC|0.0.0.x+2.1|0^observation-
+upload-soap~2^capability-exchange|||||R
+```
+
+where the 'n' in the sequence number indicates there are *n-1* OBX segments prior to the first one in this group and the 'x' in OBX-4 indicates that there are *x-1* metric instances before the first one in this group (some instances may have facets so *x* and *n* may not be the same).
+
+Only the **bold** OBX-5 fields are dependent upon a given PHG. The MDC codes in OBX-3 are special to the services and are not seen in [ISO/IEEE 11073-20601] exchanges. Encoding the values requires understanding the ASN-1 structure Continua has assigned to the Reg-Cert-Data-List attribute. This structure is defined in clause 6.3.2.6 "X73 component – Regulatory settings" of [ITU-T H.811].
+
+In short:
+
+- OBX[n+1] contains the Continua major and minor version number in OBX-5.
+- OBX[n+2] contains the list of Continua defined codes representing the sensor specializations and transports that the PHG has been certified for in OBX-5.
+- OBX[n+4] contains the regulation status BITs settings in OBX-5.
+- OBX[n+6] contains the Continua defined codes for the Health & Fitness service classes that the PHG has been certified for in OBX-5.
+
+The other required PHG-OBX entry that must occur in every PCD-01 document is the time synchronization used. For example
+
+```
+OBX|n|CWE|68220^MDC_TIME_SYNC_PROTOCOL^MDC|0.0.0.x|532224^MDC_TIME_SYNC_EBWW^MDC|||||R
+```
+
+The reporting of relative times is only of interest when the PHG and sensor synchronize their relative times. There are currently no Continua devices on the market that fall into this use case.
+
+## 10.6 MDS-OBXes
+
+The MDS-OBXes are populated from a subset of the attributes on the sensor's medical device system (MDS) object. Only the following attributes are encoded into OBX segments:
+
+**Table 10-1 – MDS-OBX attributes**
+
+| Attribute                    | Ref Id                      | Requirement                                        |
+|------------------------------|-----------------------------|----------------------------------------------------|
+| System-Type                  | MDC_ATTR_SYS_TYPE           | Required if valued (Note 1)                        |
+| System-Model                 | MDC_ATTR_ID_MODEL           | Required                                           |
+| System-Id                    | MDC_ATTR_SYS_ID             | Required                                           |
+| Production-Specification     | MDC_ATTR_ID_PROD_SPECN      | Required if valued                                 |
+| Mds-Time-Info                | MDC_ATTR_MDS_TIME_INFO      | Some elements required if valued                   |
+| Date-and-Time (Note 2)       | MDC_ATTR_TIME_ABS           | Required if PHG is better synchronized than sensor |
+| Relative-Time (Note 2)       | MDC_ATTR_TIME_REL           | Required if valued                                 |
+| HiRes-Relative-Time (Note 2) | MDC_ATTR_TIME_REL_HI_RES    | Required if valued                                 |
+| Base-Offset-Time (Note 2)    | MDC_ATTR_TIME_BO            | Required if PHG is better synchronized than sensor |
+| Power-Status                 | MDC_ATTR_POWER_STAT         | Optional                                           |
+| Battery-Level                | MDC_ATTR_VAL_BATT_CHARGE    | Optional                                           |
+| Remaining-Battery-Time       | MDC_ATTR_TIME_BATT_REMAIN   | Optional                                           |
+| Reg-Cert-Data-List           | MDC_ATTR_REG_CERT_DATA_LIST | Required if valued                                 |
+| System-Type-Spec-List        | MDC_ATTR_SYS_TYPE_SPEC_LIST | Required if valued.                                |
+| Tick-Resolution              | MDC_TICK_RESOLUTION         | Required if valued                                 |
+
+NOTE 1 – This will not occur with Continua specializations since the System-Type-Spec-List is required and only one of System-Type-Spec-List or System-Type is allowed by [ISO/IEEE 11073-20601].
+
+NOTE 2 – This will result in a coincident timestamp OBX.
+
+There is also a top-level MDS-OBX. Its OBX-4 field is |x| where x is typically 1. An example follows:
+
+```
+OBX|n||528404^MDC_DEV_SPEC_PROFILE_BCA^MDC|1|||||X|||||0022D6014AFBD418^^0022D6014AFBD418^
+EUI-64
+```
+
+where the sequence number n depends upon where in the list of OBX segments this segment is placed. The sensor's system id is placed in OBX-18 as an EI data type and the MDC code for the sensor specialization is placed in OBX-3 as a CWE data type. In the above example the sensor is a body composition analyser. The specialization comes from the System-Type-Spec-List. If there is more than one specialization indicated in the System-Type-Spec-List, the top-level OBX-3 entry contains the special profile 'hydra' which indicates multiple specializations. In that case an extra MDS-OBX is needed that contains the System-Type-Spec-List entries as repeated CWE data types.
+
+```
+OBX|n||528384^MDC_DEV_SPEC_PROFILE_HYDRA^MDC|1|||||X|||||0022D6014AFBD418^^0022D6014AFBD418^
+EUI-64
+OBX|n+1||68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC|1.0.0.1|528404^MDC_DEV_SPEC_PROFILE_BCA^MDC~528
+388^MDC_DEV_SPEC_PROFILE_PULS_OXIM^MDC|||||R
+```
+
+## 10.7 Metric OBXes
+
+Metric OBX segments represent measurements. The [ISO/IEEE 11073-20601] engine of the PHG creates measurements from 'scan event reports' or 'segment data events'. Scan event reports contain 'observation scans' or 'group observation scans', the latter of which is an efficient formatting of a set of observation scans. Segment data events contain 'entries' which contain 'elements' where the
+
+elements are semantically an observation scan. The bottom line is that an observation scan contains a list of attributes that are updated on an object plus the handle to that object. If the handle to that object is a metric object AND at least one of the updated attributes is an observational attribute, the update is a measurement. The PHG's [ISO/IEEE 11073-20601] engine takes the updated attributes and combines them with the contextual attributes for the updated object and creates the final measurement that is dispatched to the user of those measurements. It is the job of the PHG to maintain the contextual attributes and to filter out all 11073-specific maintenance operations. An example of a maintenance operation would be weighing scales switching from kilograms to pounds. The Bluetooth low energy (Bluetooth LE) engine of the PHG would create similarly mapped metric measurement objects from the Bluetooth LE attributes.
+
+The task of the PCD-01 translator is to take that 'final' measurement and create Metric OBX segments from it. The primary work is then to map the observational attributes of the three classes of metric objects into OBX-5.
+
+### 10.7.1 Mapping the 11073 observational attributes in OBX-5 and data type in OBX-2
+
+In [ISO/IEEE 11073-20601] the coding of OBX-5 from the received measurement is the most dynamic. The schematic below summarizes the translations:
+
+Numerics have the following cases:
+
+1. Basic-Nu-Observed-Val and Simple-Nu-Observed-Val use the NM data type.
+2. The Nu-Obs-Value case also uses the NM data type but the PCD-01 translator must process the state, unit-code and metric-Id substructures that are packaged with it. These substructures mirror the Measurement-Status, Unit-Code and Metric-Id attributes.
+3. Compound versions of the above also use the NM data type but an OBX is created for each compound entry and the OBX-3 value is taken from the Metric-Id-List attribute instead of the TYPE or Metric-Id attribute. There is also the Continua mapping of the parent OBX to the 11073-10201 channel.
+4. Compound-Nu-Observed-Val attributes use the NM data type but use the state, unit-code and metric-Id substructures contained within the attribute instead of the context attributes in the object.
+
+Enumerations have three possible data types:
+
+1. ASN-1 BITS fields are encoded as a CWE type similar to MDC codes where the first component is the bit value (0 or 1) and the second component is the normative ASN-1 name and bit number in parentheses. The third component is empty and not present. If more than one bit is set, the component is repeated. For example:
+  - a)  $1^{\wedge}$  device-battery-low(0)
+  - b)  $1^{\wedge}(0)$
+  - c)  $1^{\wedge}$  device-battery-low(0) $\sim 1^{\wedge}$ sensor-read-interrupt(9)
+  - d)  $1^{\wedge}(0)\sim 1^{\wedge}(9)$
+
+In cases a) and c) the name is known and in cases b) and d) it is not. Cases c) and d) represent more than one bit setting.
+
+Typically cleared bits (bit is zero) are not sent though it is legal to do so.
+
+2. OID-enums in [ISO/IEEE 11073-20601] are MDC codes and are encoded as CWE data types exactly like OBX-3.
+3. String-enums are encoded as ST data types which means 'string'.
+
+RTSAs are semantically a sequence or list of complete measurements in time order. However, to represent this measurement the HL7 NA (numeric array) data type is used as a one dimensional vector. This choice is to be consistent with PCD. The one dimensional vector is represented by numerical entries separated by the component separator which in the standard interpretation of component separators indicates that all the components together are needed to describe the measurement. Semantically the interpretation is inconsistent with an RTSA sequence since each entry in the RTSA is an independent measurement in time and one would expect the separator to be the repetition symbol. The implementer needs to be aware of the chosen convention (NOTE). OBX-5 then consists of a sequence of numbers separated by the component separator symbol (^).
+
+NOTE – In the future this representation may change as multi-dimensional waveforms such as the acceleration vector are being considered by PCD.
+
+On the wire RTSA data is scaled into 8, 16 or 32 bit integers to take less space. Support attributes in the RTSA object contain the scaling factors. When populating the OBX-5 field, the on-the-wire values are rescaled to their original values using the support attributes.
+
+## **10.8 Date-Time-Adjustment**
+
+The date-time-adjustment occurs when the sensor's clock is changed while it is recording or storing measurements. It is most likely to occur on sensors using absolute time when changing time zones or due to daylight savings time but it can also happen when adjusting clock skew. On sensors reporting base-offset time date-time-adjustments only occur if the base time is, for some reason, altered.
+
+The value of the date-time-adjustment is the time one needs to add to any previous measurement times to bring the timestamps of those measurements to the current sensor timeline. In PCD-01 a date-time-adjustment is handled by generating a new OBR and restarting the process as if it were a new association. The new OBR will need a new set of MDS-OBXes. The PHG-OBXes do not need to be regenerated.
+
+The date-time-adjustments can also be present in an attribute of a PM segment. Each segment containing a date-time-adjustment that is different requires a new OBR.
+
+[ISO/IEEE 11073-20601] also states that 'small' adjustments do not need to be reported by the sensor. However, what is meant by small is not defined.
+
+## **11 Guidelines**
+
+The locations of the guidelines for creating the PCD-01 document are specified in this clause. The requirements for the MSH, PID and OBR segments are fairly straight forward.
+
+### **11.1 MSH**
+
+The guidelines for creating a Continua compliant MSH segment are in clause E.4.1.
+
+### **11.2 PID**
+
+The guidelines for creating a Continua compliant PID segment are in clause E.4.2.
+
+### **11.3 OBR**
+
+The guidelines for creating a Continua compliant OBR segment are in clause E.4.3.
+
+### **11.4 OBX**
+
+The guidelines for generating the OBX segments consist of several parts.
+
+The basic guidelines are in clause E.4.4 and should be examined first.
+
+The remaining guidelines are in clause D.1 where:
+
+- The guidelines for formulating the PHG OBXes are in clause D.1.1.
+  - There are no attributes on a PHG. 'Fake' attributes that mirror the MDS attributes on a sensor map to one or more OBX segments.
+- The guidelines for formulating the MDS OBXes are in clause D.1.2.
+  - In general attributes from the sensor's MDS object map to one or more OBX segments.
+- The guidelines for formulating the Metric OBXes are in clause D.1.3.
+  - In general *several* attributes from the sensor's metric object map to *one* OBX segment.
+    - TYPE or Metric-Id determines OBX-3
+    - Observational attribute determines OBX-2 and OBX-5
+    - Unit code determines OBX-6
+    - Measurement status determines OBX-8/OBX-11
+    - Timestamp determines OBX-14
+  - Metric objects with compound attributes will map to at least a channel OBX segment and one child OBX segment for each compound entry.
+  - Some metric attributes, if present, result in an extra OBX segment to describe the properties of the attribute. These segments are children.
+- Special conditions are covered in clause D.1.4
+  - Date-Time-Adjustments
+  - OBX-20 replacing OBX-5
+  - Separating stored and live measurements
+  - Measurements with and without timestamps in same association
+  - Multiple devices
+  - Set Time action
+  - Bluetooth low energy
+
+## Annex A
+
+### Normative guidelines for common aspects
+
+(This annex forms an integral part of this Recommendation.)
+
+**Table A.1 – Guidelines for all CCC classes**
+
+| Name                                     | Description                                                                                                                                          | Comments |
+|------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|----------|
+| Services-Transport-Connection-Initiation | All Continua services connections <b>shall</b> be initiated from the PHG application and <b>shall not</b> be initiated from the services application |          |
+
+**Table A.2 – Observation Upload guidelines for a PHG application**
+
+| Name                                           | Description                                                                                                                                         | Comments |
+|------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------|
+| Services-Messaging-Device-Observation-Reporter | Continua PHG applications <b>shall</b> implement the device observation reporter actor of the IHE PCD device enterprise communication (DEC) profile |          |
+
+**Table A.3 – Observation Upload guidelines for a services application**
+
+| Name                                           | Description                                                                                                                                              | Comments |
+|------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|----------|
+| Services-Messaging-Device-Observation-Consumer | Continua services applications <b>shall</b> implement the device observation consumer actor of the IHE PCD device enterprise communication (DEC) profile |          |
+
+## Annex B
+
+### Normative guidelines for hData
+
+(This annex forms an integral part of this Recommendation.)
+
+**Table B.1 – Observation Upload guidelines for a PHG application using hData**
+
+| Name                                       | Description                                                                                                                                                                                                                                                                  | Comments                                                                                                                                                                                                     |
+|--------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Observation-Upload-Enabled-PHG             | Observation Upload enabled PHG application shall comply to the following standards:<br>[HL7 V3 HRF] Specification: hData Record Format, Release 1<br>[OMG/hData REST] Binding for RLUS<br>[OMG/hData RLUS] Retrieve, locate and update service (RLUS)                        |                                                                                                                                                                                                              |
+| Observation-Upload-PHG-Capability-Exchange | A PHG application supporting Observation Upload using hData shall support capability exchange as specified in [ITU-T H.812.3]                                                                                                                                                |                                                                                                                                                                                                              |
+| Observation-Upload-PHG-Root-Support        | A PHG application that chooses to POST a root.xml file to a services application during capability exchange shall provide the profile element in the root.xml in accordance with Figure 7-2.                                                                                 |                                                                                                                                                                                                              |
+| Observation-Upload-Post                    | Observation Upload enabled PHG application shall use HTTP POST with the URL for posting to the services application as specified in the <path> element of the capability profile elements: baseURL/path-as-specified-in-capability-profile for uploading the PCD-01 payload. | For RLUS hData over REST transport, this upload is accomplished by performing an HTTP POST request without query parameters at this URL with the observation measurement document in the body of the request |
+
+**Table B.2 – Observation Upload guidelines for a services application using hData**
+
+| Name                                            | Description                                                                                                                                                                                                                                                                                                                                                                                 | Comments |
+|-------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|
+| Observation-Upload-Enabled-Services             | Observation Upload enabled services application shall comply to the following standards: <ul style="list-style-type: none"> <li>– [HL7 V3 HRF] Version 3 Specification: hData Record Format, Release 1</li> <li>– [OMG/hData RESTful Trans] Binding for RLUS</li> <li>– [OMG/hData RLUS] Retrieve, locate, and update service (RLUS)</li> <li>– [IHE PCD-01] for PCD-01 document</li> </ul> |          |
+| Observation-Upload-Services-Capability-Exchange | A services application supporting Observation Upload using hData shall support capability exchange as specified in [ITU-T H.812.3]                                                                                                                                                                                                                                                          |          |
+| Observation-Upload-Services-Root-Support        | A services application supporting Observation Upload shall provide a root.xml file during capability exchange with profile elements in the root.xml in accordance with Figure 7-2.                                                                                                                                                                                                          |          |
+| Observation-Upload-Services-OAuth-Service       | A services application supporting an OAuth authentication service may indicate support for the service in its root.xml. If the service chooses to add these capability elements, they shall appear as in Figure 7-3.                                                                                                                                                                        |          |
+| Observation-Upload-Services-Document-Create     | Observation Upload enabled services application shall create a PCD-01 document after receiving POST message from the Observation Upload enabled PHG application and send the <HTTP 201> as a response.                                                                                                                                                                                      |          |
+| Observation-Upload-Services-Response-body       | A PCD-01 response message <b>shall</b> be sent in the body of the HTTP response to the POST that carried the original PCD-01 message.                                                                                                                                                                                                                                                       |          |
+| Observation-Upload-Services-Document-Delete     | Observation Upload enabled services application shall not support the deletion of an existing PCD-01 document and shall return HTTP 405 Method Not Allowed as a response to HTTP DELETE request on an Observation Upload URL.                                                                                                                                                               |          |
+
+## Annex C
+
+### Normative guidelines for SOAP
+
+(This annex forms an integral part of this Recommendation.)
+
+**Table C.1 – Common Observation Upload guidelines using SOAP**
+
+| Name                                          | Description                                                                                                                                                                                                                                                             | Comments                                                                                                                                                                                                                                                                                                                                          |
+|-----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Services-Messaging-Infrastructure-Profile-IHE | Continua PHG and services applications <b>shall</b> conform to Appendix V of [IHE ITI-TF-2]                                                                                                                                                                             | Base transport standard                                                                                                                                                                                                                                                                                                                           |
+| Services-Secure-Auditing                      | Continua services application and client components <b>may</b> implement and adhere to the IHE ATNA auditing related clauses (clause 3.20, in Part A of [IHE PCD TF 2012 2])                                                                                            | Profiles referenced by IHE ATNA for auditing:<br>The BSD (Berkeley Software Distribution) Syslog Protocol [IETF RFC 3164];<br>Reliable Delivery for Syslog [IETF RFC 3195];<br>Security Audit and Access Accountability Message XML Data Definitions for Healthcare Applications [IETF RFC 3881]                                                  |
+| Services-Security-Assertion                   | Continua services application and client components <b>shall</b> support the transfer of entity assertion information via the SAML 2.0 token through the WS-Security Header according to the Web Services Security: SAML Token Profile 1.1                              | IHE Cross Enterprise User Assertion (XUA) profile uses the same mechanisms for the cross enterprise authentication of users.<br>The profile does not prohibit the use of other types of tokens (certificates) for an entity, providing that interoperability is being assured through some policy negotiation in an online or out-of-band fashion |
+| Observation-Upload-Capability-Exchange        | Continua services application and client components supporting only SOAP uploads <b>may</b> support capability exchange as indicated in [ITU-T H.812.3]                                                                                                                 | This feature allows a PHG to configure Observation Uploads with fewer out-of-band exchanges.                                                                                                                                                                                                                                                      |
+| Observation-Upload-Root-Support               | Continua services application and client components supporting only SOAP uploads <b>may</b> include capability elements in the root.xml indicating support for SOAP based uploads. If the capability elements are included, they <b>shall</b> be as shown in Figure 7-4 | If the SOAP only upload application chooses to support capability exchange, it must follow the same rules as hData based upload applications. That means a PHG application wishing to POST its root.xml must provide an OAuth token in the POST.                                                                                                  |
+| Services-Transport-QoS-Reliability-Better     | Continua PHG and Services applications <b>may</b> transmit messages from the Continua <i>better</i> QoS bin using a WS-ReliableMessaging sequence configured to use 'AtMostOnce' message delivery                                                                       | WS-Reliable messaging                                                                                                                                                                                                                                                                                                                             |
+| Services-Transport-QoS-Reliability-Best       | Continua PHG and services applications <b>should</b> transmit messages from the Continua <i>best</i> QoS bin using a WS-ReliableMessaging sequence configured to use 'ExactlyOnce' message delivery                                                                     | WS-Reliable messaging                                                                                                                                                                                                                                                                                                                             |
+
+**Table C.2 – Observation Upload guidelines for a PHG using SOAP**
+
+| Name                                                                     | Description                                                                                                        | Comments                                      |
+|--------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|
+| Services-Messaging-Infrastructure-Reliable-Messaging-Sender-Observations | A Continua PHG application <b>may</b> support WS-ReliableMessaging as an RM source for CommunicatePCDData messages | Note that WS-Reliable messaging is SOAP based |
+
+**Table C.3 – Observation Upload guidelines for a Health & Fitness service using SOAP**
+
+| Name                                                                                            | Description                                                                                                                                                                                                                                                       | Comments                                                                                                                                    |
+|-------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|
+| Observation-Upload-SAML-Token-Root-Support                                                      | A Continua services application supporting an SAML token WS-Trust service <b>may</b> include capability elements in the root.xml indicating support for this service. If the capability elements are included, they shall be as shown in the script of Figure 7-5 | This feature is allowed to reduce the number of out-of-band transactions needed to configure the client for SOAP based Observation Uploads. |
+| Services-Messaging-Infrastructure-Reliable-Messaging-Receiver-Observation-Reception             | A Continua services application supporting SOAP uploads <b>shall</b> support WS-ReliableMessaging as an RM destination for CommunicatePCDDataResponse messages                                                                                                    | This requirement applies only to Continua services service components supporting SOAP Observation Uploads.                                  |
+| Services-Messaging-Infrastructure-Reliable-Messaging-Receiver-Observation-Response-Transmission | A Continua services application supporting SOAP uploads <b>shall</b> support WS-ReliableMessaging as an RM source for CommunicatePCDDataResponse messages                                                                                                         | An RM sequence shall only be used if the services sender has provided an RM "Offer" for the services receiver to use                        |
+
+## Annex D
+
+### Normative guidelines data payload
+
+(This annex forms an integral part of this Recommendation.)
+
+This annex gives the general guidelines for creating the PCD-01 payload. Table D.1 provides guidelines of a broad scope. The following subclauses provide the details for mapping ISO/IEEE 11073-20601 data to the Continua services.
+
+**Table D.1 – Observation Upload general data payload guidelines**
+
+| Name                               | Description                                                                                                                                                                                    | Comments                                    |
+|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|
+| Services-Data-Standard             | Continua PHG and services applications <b>shall</b> conform to the IHE PCD TF Patient Care Devices Technical Framework Revision 2.0 except where these constraints conflict with this document | There are no known conflicts                |
+| Services-Data-Standard-Constraints | Continua PHG and services applications [HL7 2.6] message payloads <b>shall</b> conform to the constraints defined in [IHE PCD TF-2]                                                            | Annex F is the reference                    |
+| Services-Data-Standard-Encoding    | Continua PHG and services applications <b>shall</b> use the HL7 2.6 EDI encoding and <b>shall not</b> use the HL7 2.6 XML encoding [HL7 2.6]                                                   | The PCD TF allows both EDI and XML encoding |
+| Services-Data-Coding-MDC           | Continua PHG application observations <b>shall</b> use the medical device communication (MDC) coding system for all observation identifiers (OBX-3, OBX-20)                                    | Minimal translation                         |
+| Services-Data-Measurement-Units    | Continua PHG application observations <b>shall</b> use the medical device communication (MDC) coding system for all non-empty units (OBX-6)                                                    | Minimal translation                         |
+| Services-Data-Minimize-Convention  | Continua PHG applications <b>should</b> terminate all Observation Result segments after their last non-empty sequence                                                                          |                                             |
+| Services-Authoring-MSH             | The Continua PHG application <b>shall</b> generate the MSH segment according to the guidelines specified in clause E.4.1                                                                       |                                             |
+| Services-Authoring-PID             | The Continua PHG application <b>shall</b> generate the PID segment according to the guidelines specified in clause E.4.2                                                                       |                                             |
+| Services-Authoring-OBR             | The Continua PHG application <b>shall</b> generate the OBR segment according to the guidelines specified in clause E.4.3                                                                       |                                             |
+
+**Table D.1 – Observation Upload general data payload guidelines**
+
+| Name                                                             | Description                                                                                                                                                                                                                                                                                                                      | Comments                                                                                                                                                                                                                                                                                                                                                      |
+|------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Services-Data-Client-Device                                      | The PHG application <b>shall</b> provide regulatory and time information in a set of PHG-OBX segments according to clause D.1.1                                                                                                                                                                                                  | Clause D.1.1 provides the detailed guidelines for creating the PHG-OBX segments. These segments expose the identity, regulatory information and time capabilities of the PHG client.                                                                                                                                                                          |
+| Services-Data-Authoring-Device                                   | For observations which originate from a Continua Personal Health Device, the Continua PHG application <b>shall</b> include MDS-level OBX segments according to clause D.1.2                                                                                                                                                      | Clause D.1.2 provides the detailed guidelines for creating the MDS-OBX segments. These segments expose the device type, identity, regulatory information and time capabilities.                                                                                                                                                                               |
+| Services-Data-Authoring-Device-Encoding-Algorithm                | For observations which originate from an [ISO/IEEE 11073-20601] compliant device or that can be mapped to a set of observations as if they came from an [ISO/IEEE 11073-20601] compliant device, the Continua PHG application <b>shall</b> encode the observations into Metric OBX segments according to clauses D.1.3 and D.1.4 | These annexes provide the mappings of observations into OBX segments                                                                                                                                                                                                                                                                                          |
+| Services-Data-Authoring-Device-Encoding-Containment              | For observations which originate from a Continua Personal Health Device, the Continua PHG application <b>shall</b> use the specified containment notation in OBX-4                                                                                                                                                               | Maintain relationships of measurements                                                                                                                                                                                                                                                                                                                        |
+| Services-Data-Authoring-Device-Encoding-Timestamp                | The Continua PHG application <b>shall</b> report all time values in MSH-7, OBR-7, OBR-8 and OBX-14 as UTC or UTC coordinated values expressed as an HL7 date/time (DTM) data type                                                                                                                                                | <p>It is imperative that all measurements can be correlated to a single comprehensive timeline for proper, safe analysis and usage.</p> <p>UTC values are reported using the +/-<i>ZZZZ</i> time zone suffix. If the local time zone is not known -0000 is used.</p> <p>Under special conditions the PHG may fall back to sending unqualified timestamps.</p> |
+| Services-Data-Authoring-Device-Encoding-Nomenclature-Translation | Continua PHG applications <b>shall</b> adjust all nomenclature values that use the "_X" indicator in the name to the corresponding correct base value without the "_X" indicator.                                                                                                                                                | <p>Ensure all nomenclature usage is aligned.</p> <p>This form of the unit code REFID values is called "unity scaling" because there is no SI prefix used</p>                                                                                                                                                                                                  |
+
+## D.0 Mapping from [ISO/IEEE 11073-20601] to the Continua services
+
+### D.0.1 Terminologies and conventions
+
+The following clause provides guidelines for mapping [ISO/IEEE 11073-20601] attributes and objects into OBX segments. The guidelines require the use of ASN.1 terminologies and PCD-01 terminologies. To distinguish the terminologies, the prefix "ASN.1-" will appear before names referencing [ISO/IEEE 11073-20601] ASN.1 attribute structures and substructures if the name is not specifically stated to be an attribute or ASN.1 structure. Attribute names are capitalized and separated by dashes, for example Relative-Time. ASN.1 substructures within attributes are lower case and separated by dashes, for example, ASN.1-component-id. References to the ASN.1 names and attributes are found in [ISO/IEEE 11073-20601] and related specialization standards. The words 'component', 'sub-component' and 'field' refer to the PCD-01 usages of these terms.
+
+To the extent possible, the term 'observation' is used in the guidelines to represent a physiological measurement instead of 'measurement'.
+
+Handling Bluetooth low energy (LE) attributes is done by semantically mapping the BTLE attributes to [ISO/IEEE 11073-20601] attributes and using the guidelines provided in this document to generate the PCD-01 document payload. The Transcoding White Paper [Bluetooth PHDT] provides the mapping.
+
+**PHG-OBX** segments describe the properties of the PHG. Though it may appear that these segments are derived from an [ISO/IEEE 11073-2060] MDS object on the PHG, there is no requirement for the PHG to possess this object or its attributes.
+
+**MDS-OBX** segments describe properties of the sensor. These segments are generated from a subset of the attributes in the sensor's [ISO/IEEE 11073-20601] MDS object. The [ISO/IEEE 11073-20601] Personal Health Devices engine of the PHG obtains these attributes using the [ISO/IEEE 11073-20601] GET request. The Bluetooth low energy PAN engine of the PHG obtains equivalent values for these [ISO/IEEE 11073-20601] attributes from the sensor's device information service and whatever current time mechanism the device supports. The Transcoding White Paper [Bluetooth PHDT] provides the mapping.
+
+**Metric-OBX** segments describe observations. Observations are represented in [ISO/IEEE 11073-20601] metric objects. The [ISO/IEEE 11073-20601] Personal Health Devices engine of the PHG receives observation updates via [ISO/IEEE 11073-20601] scan event reports or segment data events whose ASN.1-observation-scans contain at least one metric value-type *observational* attribute (see NOTES). The update is combined with contextual information maintained by the PHG and the resultant metric object (the observation) is mapped to one or more Metric OBX segments. The Bluetooth low energy PAN engine of the Personal Health Gateway (PHG) maps the GATT attributes received via indications or notifications to equivalent [ISO/IEEE 11073-20601] metric objects which are then mapped to one or more Metric OBX segments. The Transcoding White Paper [Bluetooth PHDT] provides the mapping.
+
+NOTE 1 – [ISO/IEEE 11073-20601] also allows updates of MDS attributes via scan event reports such as the battery level. Though they do not represent physiological observations the reporting of this information may be of interest and it is left up to the implementer whether or not to include them in the PCD-01 document.
+
+NOTE 2 – Segment data events transfer PM segment data but each entry element maps to a metric object and it is the metric object that represents the observation. Thus, all observations are ultimately from one of the sensor's metric objects regardless of whether they use the PM Store/PM Segment, Scanner or Agent-init models to transfer the data.
+
+### D.0.2 Protocol-dependent information
+
+[ISO/IEEE 11073-20601] defines concepts whose sole purpose is to aid in the exchange of APDUs so that the data in the APDUs can be reconstructed into measurements. The PM Store, PM Segment, Scanner, AttributeValue Map, scan event report formats (fixed, variable, group), object handles and
+
+config ids are all examples of these concepts. These items are not reported in the PCD-01 document. One will note that the Bluetooth low energy transcoding white paper [Bluetooth PHDT] is also careful to only map Bluetooth LE features to ISO/IEEE 11073-20601 features that are important for sensor properties and measurements. There is no mapping, for example, of the Bluetooth LE RACP to PM stores and PM segments or Bluetooth LE characteristic descriptors to ISO/IEEE 11073-20601 attributes since these items are all aids in the protocol transfer of information and not the information itself.
+
+### D.0.3 Services-specific nomenclature
+
+Additional nomenclature codes not defined in [ISO/IEEE 11073-20601] are defined by Continua for the PHG- and MDS-OBX segments. These codes are needed as several of the MDS attributes contain multiple ASN.1 substructures, where each substructure requires an OBX segment and thus an OBX-3 key word in order to describe the information. These codes are also used in the PHG-OBX segments to represent analogous information. Table D.2 lists these new codes.
+
+**Table D.2 – Continua services regulation nomenclature codes**
+
+| Partition      | Nomenclature code's common name          | Code |
+|----------------|------------------------------------------|------|
+| MDC_PART_OBJ   | MDC_REG_CERT_DATA_AUTH_BODY              | 2682 |
+| MDC_PART_INFRA | MDC_MOC_VMS_MDS_PHG                      | 7693 |
+| MDC_PART_INFRA | MDC_REG_CERT_DATA_CONTINUA_VERSION       | 8064 |
+| MDC_PART_INFRA | MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST | 8065 |
+| MDC_PART_INFRA | MDC_REG_CERT_DATA_CONTINUA_REG_STATUS    | 8066 |
+| MDC_PART_INFRA | MDC_REG_CERT_DATA_CONTINUA_PHG_CERT_LIST | 8067 |
+
+### D.0.4 ISO/IEEE 11073-20601 general object/attribute mapping
+
+This clause provides detailed guidelines for the mapping of ISO/IEEE 11073-20601 objects and attributes to OBX segments. Only a subset of the ISO/IEEE 11073-20601 objects and attributes are used in this mapping. The guidelines in this annex apply to any sensor whose information and/or observations are mapped to ISO/IEEE 11073-20601 objects and attributes whether or not they are [ISO/IEEE 11073-20601] sensors. An example would be Bluetooth low energy sensors whose transactions have been mapped to the necessary ISO/IEEE 11073-20601 objects and attributes in the Transcoding White Paper [Bluetooth PHDT].
+
+#### D.0.4.1 Nomenclature code mapping
+
+The mapping of [ISO/IEEE 11073-20601] to PCD-01 is primarily through nomenclature codes. In PCD-01 these codes are mapped into an HL7 CWE data type. This encoding occurs so frequently it is worth indicating in detail how the encoding is done.
+
+##### CWE encoding for nomenclature codes:
+
+A nomenclature code is always associated with a partition. In some attributes that only give a nomenclature code the partition is implicit; for example the Unit-Code attribute value always comes from partition 4 (MDC\_PART\_DIM). In other cases the partition is obtained from either the TYPE attribute value's partition or from the presence of an attribute like the Metric-Id-Partition or Enum-Observed-Value-Partition that contains the partition.
+
+- CWE-1 **shall** contain the code. It is computed by (partition code) \*  $2^{16}$  + (nomenclature code) and always presented as a decimal number (not HEX). This component is required.
+- CWE-2 **should** contain the nomenclatures code's reference Id name. This component may be empty if the reference id name is not known, but all efforts should be made to include this
+
+name as it makes the subsequent document much more human readable. Note that OBX-3 in Continua PCD-01 documents is *always* an encoded nomenclature code and without the name the reader will need to look up the associated name given CWE-1.
+
+- CWE-3 **shall** be MDC
+- CWE-4 is empty
+- CWE-5 is an alternate text component that is used to describe extra information. If the sensor includes one of the label string attributes it is placed here.
+
+The above requirements differ slightly from that of HL7 which require that CWE-2 be non-empty and allow all the other components to be empty.
+
+Example: Weighing scales containing a body mass object. The TYPE attribute value for this object gives the partition value, which is 2, and the nomenclature code, which is 57664. The reference id for code 57664 in partition 2 (scada) is MDC\_MASS\_BODY\_ACTUAL. The reference Id as a string must be looked up; it is not present on the wire in an ISO/IEEE 11073-20601 transaction. Thus the encoded value for CWE-1 is  $2 \cdot 2^{16} + 57664 = 188736$ . Note that in HEX the value is 0x0002E140. The partition is the most significant two bytes and the nomenclature the least significant two bytes. The final CWE encoding is:
+
+188736^MDC\_MASS\_BODY\_ACTUAL^MDC
+
+Without the optional CWE-2 name component, it is "188736^^MDC", which is not as easy for a reader to interpret.
+
+#### D.0.4.2 ASN.1 BITS mapping
+
+Though not as ubiquitous as nomenclature codes, the mapping of an [ISO/IEEE 11073-20601] ASN.1-BITS field to a PCD-01 HL7 CWE data type is also discussed in detail as it can be confusing.
+
+##### *CWE encoding for ASN.1 BITS values:*
+
+ASN.1 BITS values are commonly used for flags; for example reporting equipment status, measurement status, time capabilities, etc. In this case only two components of the CWE data type are used; CWE-3 is empty and thus not included in the OBX field. Each bit setting is represented by its own CWE entry. The entries are separated by the repetition symbol (~). However, Continua only requires the entry if the bit is set (1). If the bit is cleared (0), including the entry is optional. Thus for a given bit:
+
+- CWE-1 **shall** be the bit setting. It is either 1 or 0.
+  - If the bit is set, the entry **shall** be present
+  - If the bit is cleared, the entry **may** be present.
+- CWE-2 is the ASN.1 name for this bit which contains the bit position in parentheses appended to the end of the ASN.1 name, for example `mds-time-capab-bo-time(7)`. If the ASN.1 name is not known the name string **may** be absent but the bit position in parentheses **shall** be present, for example `(7)`.
+
+Example: The Mds-Time-Info attribute's time-capabilities are an ASN.1-BITS-16 struct. A sensor indicates that its time capabilities value is as follows: 0100000100010010. Recall that bit 0 is the most significant bit in MDER encoding. From the ASN.1 table for the time capability bits one has
+
+- `mds-time-capab-real-time-clock(0)`
+- `mds-time-capab-set-clock(1)`
+- `mds-time-capab-relative-time(2)`
+- `mds-time-capab-high-res-relative-time(3)`
+- `mds-time-capab-sync-abs-time(4)`
+- `mds-time-capab-sync-rel-time(5)`
+
+- mds-time-capab-sync-hi-res-relative-time (6)
+- mds-time-capab-bo-time (7),
+- mds-time-state-abs-time-synced (8)
+- mds-time-state-rel-time-synced (9)
+- mds-time-state-hi-res-relative-time-synced (10)
+- mds-time-mgr-set-time (11)
+- mds-time-capab-sync-bo-time (12)
+- mds-time-state-bo-time-synced (13)
+- mds-time-state-bo-time-UTC-aligned (14)
+- mds-time-dst-rules-enabled (15)
+
+One can then determine that the value 0100000100010010 indicates that the sensor's clock can be set, it is using base offset time, the PHG is to set its time, and the base offset's time base is UTC. The CWE encoded entry would then be
+
+```
+1^mds-time-capab-set-clock(1)~1^mds-time-capab-bo-time(7)~1^mds-time-mgr-set-time(11)~1^mds-time-state-bo-time-UTC-aligned(14)
+```
+
+or
+
+```
+1^(1)~1^(11)~1^(7)~1^(14)
+```
+
+It is also okay to have
+
+```
+1^(1)~1^mds-time-capab-bo-time(7)~1^(11)~1^(14)
+```
+
+or
+
+```
+1^(1)~0^(2)~1^(11)~1^(7)~1^(14)
+```
+
+Note that no order is required in the sequence of set bits though ordering is recommended.
+
+#### D.0.4.3 FLOAT and SFLOAT mapping
+
+[ISO/IEEE 11073-20601] encodes many of its attribute values as 32-bit FLOAT or 16-bit SFLOATs. The decoding is straightforward. The 32-bit float contains an 8-bit exponent and a 24-bit mantissa which can be independently treated as signed integers for their respective bitness. Thus an 8-bit exponent with value 0x02 is the integer 2 while 0xFE is  $-2$ . However, what is often missed in the translation is the additional semantic meaning of the exponent; it defines not only the value but also the *precision*. Whenever the exponent is positive, the reported value is an integer; it has no fractional component. Thus, if the mantissa is 2 and the exponent 3, the value reported is 2000 ( $2 \times 10^3$ ). On the other hand, if the exponent is negative, it indicates the number being reported has two factional decimal places of precision. Thus if the mantissa is 2 and the exponent  $-3$ , the value reported is 0.002 ( $2 \times 10^{-3}$ ). If the mantissa is 2000 and the exponent  $-3$ , the value reported is 2.000 and not 2 or 2.0 or 2.00. The ' $-3$ ' indicates three decimal places of fractional precision.
+
+- Services observation uploaders **shall** encode FLOAT and SFLOATs according to the indicated precision.
+
+#### D.0.4.4 Sequence number and containment:
+
+The generic rules for the sequence numbers and containment values of OBX segments in an OBR are as follows:
+
+- OBX-1 **shall** start at one for the first OBX segment in an OBR and increase by one for every additional entry.
+- The n-tuple in OBX-4 **shall** be unique within a given OBR.
+  - Remark 1: There is no relationship between the sequence number of the OBR segment and the MDS-tuple value in OBX-4
+  - Remark 2: There is no relationship between the hierarchies in OBR segment N with those in OBR segment M.
+
+- Remark 3: There is no relationship between the metric n-tuple value and the handle value of an ISO/IEEE 11073-20601 object.
+- Remark 4: There is no semantic meaning to the absolute numerical values of the n-tuple in the hierarchy in the sense of order or time; their sole purpose is to establish the scoping (containment) of the segments
+
+In the following clause a normative reference to a single OBX segment is frequently made since certain fields have fixed values. However, in a PCD-01 document the segment will generally appear somewhere in a sequence of OBX segments, thus it is not possible to know ahead of time what the sequence number and value of the MDS-tuple, channel-tuple and metric-tuple are. These values depend upon the other segments already present in the document. To indicate this situation, when an OBX segment is shown with OBX-1 = *n*, the sequence number '*n*' indicates one after the sequence number of the OBX segment prior to it. When an OBX segment is shown with an OBX-4 hierarchy *m.0.c.x*, the '*m*' indicates the MDS instance the segment is a member of, '*c*' indicates the channel instance, and '*x*' indicates the metric instance. If the hierarchy is shown as *m.0.0.x.y*, the '*y*' indicates a facet to the OBX segment with MDS instance *m* and metric instance *x* (currently there is no situation where a channel instance will have a facet so the case *m.0.c.x.y* does not occur). When discussing multiple facets of a single OBX metric instance, different variables are used for the facet-tuple as the order of the facet segments and the numbering of the facet tuple scoped by a given metric instance is up to the implementer. Dictionary (numeric) ordering is preferred to the extent possible.
+
+## D.1 OBX encoding guidelines
+
+### D.1.1 Guidelines for encoding the PHG-OBX segments
+
+There are properties that a PHG possesses that are sent in a special set of 'MDS-value-0' OBX segments. For PHD service components, the values placed in the OBX entries are based upon attributes. However, attributes are not defined on a PHG. For convenience and consistency with the encoding of the OBX entries of the MDS for service components, the PHG will be treated as if it could contain four hypothetical 'PHG' attributes in a hypothetical MDS object:
+
+- a PHG's RegCertDataList attribute which is mandatory;
+- a PHG's MdsTimeInfo attribute which is mandatory;
+- a PHG's RelativeTime attribute which is mandatory if the PHG has a relative time clock that is used in synchronization with relative timestamps on sensor devices;
+- a PHG's HiResRelativeTime attribute which is mandatory if the PHG has a high resolution relative time clock that is used in synchronization with relative timestamps on sensor devices.
+
+The properties of the PHG are populated into these hypothetical attributes as they would be if the PHG were an ISO/IEEE 11073-20601 service component (agent). These hypothetical attributes are only for the convenience of describing the encoding of the PHG OBX segments, and have no meaning outside of that purpose. There is no requirement that these attributes or MDS object exist on the PHG.
+
+PHG-OBX segments describe the properties and features of the PHG.
+
+- Every Continua PCD-01 document **shall** contain one set of PHG-OBX segments.
+- The PHG-OBX segments **shall** be the first OBX segments in the document.
+- The PHG-OBX segments **shall** only be in the first OBR.
+- The PHG-OBX segments **shall** be encoded as dictated in this clause.
+- The MDS-n-tuple in the OBX-4 hierarchy for all PHG-OBX segments **shall** be 0.
+
+- For all PHG-OBX segments, OBX-11 **shall** be 'R' except for the top-level OBX which **shall** be X.
+
+#### D.1.1.1 Top-Level PHG-OBX
+
+There **shall** be a top-level PHG-OBX.
+
+The top level PHG-OBX **shall** be the first OBX segment in the document.
+
+The top level PHG-OBX **shall** be:
+
+OBX|1||531981^MDC\_MOC\_VMS\_MDS\_PHG^MDC|0|||||X|||||obx-18
+
+where *obx-18* **shall** be the PHG's system id encoded as an EI data type where
+
+- EI-1 is some unique identifier. A repeat of EI-3 may be used here.
+- EI-3 is the PHG system id as a 16-digit HEX string (without a 0x prefix).
+- EI-4 is EUI-64.
+
+Example:
+
+OBX|1||531981^MDC\_MOC\_VMS\_MDS\_PHG^MDC|0|||||X|||||0000ABEEDADBEEF^0000ABEEDADBEEF^EUI-64
+
+#### D.1.1.2 Regulation and certification OBX segments
+
+The PHG **shall** report the Continua version and sensor specializations it has been certified for in three OBX segments as follows:
+
+- The first OBX **shall** be the Continua auth body certification OBX segment:
+
+OBX|n|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.x|2^auth-body-continua|||||R
+
+- The Continua version the PHG has been certified for **shall** be encoded into a facet OBX segment as follows:
+
+OBX|n|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|0.0.0.x.y| obx-5|||||R
+
+where *obx-5* **shall** be the Continua version the PHG is certified for as 'major version'.minor version'; for example '1.5'.
+
+Example:
+
+OBX|n|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|0.0.0.x.y|1.5|||||R
+
+- The sensor specializations the PHG has been certified for **shall** be encoded into a facet OBX segment as follows:
+
+OBX|n|NM|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|0.0.0.x.z| obx-5|||||R
+
+where *obx-5* **shall** be the list of 16-bit integers representing the Continua defined transport Tcode and sensor specialization code ( $([MDC\_DEV\_SPEC\_PROFILE\_*] - 4096 + Tcode * 8192)$ ) encoded as an NM data type separated by the repetition symbol '~'. The Tcode values are:
+
+- 0 = Continua version 1 (pre-Tcode value)
+- 1 = USB
+- 2 = Bluetooth
+- 3 = ZigBee
+
+- 4 = Bluetooth Low Energy
+
+Example for a blood pressure cuff (MDC\_DEV\_SPEC\_PROFILE\_BP =4103) supporting Bluetooth (Tcode = 2) and USB (Tcode = 1):
+
+OBX|n|NM|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|0.0.0.x.z|16391~8199|||||R
+
+The entire set:
+
+OBX|n|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.x|2^auth-body-continua|||||R  
+OBX|n+1|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|0.0.0.x.1|5.0|||||R  
+OBX|n+2|NM|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|0.0.0.x.2|16391~8199|||||R
+
+Note that the order of the two facet OBX segments in this group is up to the implementation.
+
+The PHG **shall** report its regulation status in two OBX segments as follows:
+
+- The first OBX **shall** be the Continua auth-body regulation OBX segment:
+
+OBX|n|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.x|2^auth-body-continua|||||R
+
+- The regulation status of the PHG **shall** be encoded into a facet OBX segment as follows:
+
+OBX|n|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|0.0.0.x.y|*obx-5*|||||R
+
+where *obx-5* **shall** be the regulation status BITS encoded as a CWE data type. CWE-1 is the bit setting and CWE-2 the ASN.1 name with the bit position in parentheses. At this time there is only one bit setting defined
+
+- unregulated-device(0)
+
+Example:
+
+OBX|n|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|0.0.0.x.y|1^unregulated-device(0)|||||R
+
+The entire set
+
+OBX|n|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.x|2^auth-body-continua|||||R  
+OBX|n+1|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|0.0.0.x.1|1^unregulated-device(0)|||||R
+
+The PHG **shall** report the services Continua capability classes it is certified for in two OBX segments as follows:
+
+- The first OBX **shall** be the Continua auth body services certification OBX segment.
+
+OBX|n|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.x|2^auth-body-continua|||||R
+
+- The Health & Fitness service classes that the PHG has been certified for **shall** be encoded into a facet OBX segment as follows:
+
+OBX|n|CWE|532355^MDC\_REG\_CERT\_DATA\_CONTINUA\_PHG\_CERT\_LIST^MDC|1.0.0.x.y|*obx-5*|||||R
+
+where *obx-5* **shall** be the list of services Certified Capability Class codes encoded as a CWE data type separated by the repetition character (~). Currently the following are defined:
+
+- 0^observation-upload-soap
+- 1^consent-enabled-soap
+- 2^ capability-exchange
+
+- o 3^observation-upload-hdata
+- o 4^consent-enabled-hdata
+- o 5^questionnaire
+- o 6^aps
+
+Example:
+
+OBX|n+1|CWE|532355^MDC\_REG\_CERT\_DATA\_CONTINUA\_PHG\_CERT\_LIST^MDC|1.0.0.x.1|0^observation-upload-soap~2^capability-exchange~6^aps|||||R
+
+A final example of the entire set of PHG certification and regulation OBXes with the top-level OBX is shown below:
+
+OBX|1||531981^MDC\_MOC\_VMS\_MDS\_PHG^MDC|0|||||X|||||0000ABEDEADBEEF^^0000ABEDEADBEEF^EUI-64  
+ OBX|2|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.1|2^auth-body-continua|||||R  
+ OBX|3|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|0.0.0.1.1|5.0|||||R  
+ OBX|4|NM|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|0.0.0.1.2|16391~8199|||||R  
+ OBX|5|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.2|2^auth-body-continua|||||R  
+ OBX|6|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|0.0.0.2.1|1^unregulated-device(0)|||||R  
+ OBX|7|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.3|2^auth-body-continua|||||R  
+ OBX|8|CWE|532355^MDC\_REG\_CERT\_DATA\_CONTINUA\_PHG\_CERT\_LIST^MDC|0.0.0.3.1|0^observation-upload-soap~2^capability-exchange~6^aps|||||R
+
+### D.1.1.3 System model
+
+The PHG may report information equivalent to that provided by the System-Model attribute. If the PHG reports this information, it shall be encoded as follows for each quantity that is to be specified:
+
+The model number shall be encoded as
+
+OBX|n|ST|531969^MDC\_ID\_MODEL\_NUMBER^MDC|0.0.0.x|obx-5|||||R
+
+where *obx-5* shall be the model-number as a 127-bit ASCII string.
+
+The manufacturer shall be encoded as
+
+OBX|n|ST|531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC|0.0.0.x|obx-5|||||R
+
+where *obx-5* shall be the manufacturer name as a 127-bit ASCII string.
+
+Example:
+
+OBX|n|ST|531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC|0.0.0.x|ContinuaPHGs Inc|||||R  
+ OBX|n+1|ST|531969^MDC\_ID\_MODEL\_NUMBER^MDC|0.0.0.x+1|39597-PHG|||||R
+
+### D.1.1.4 Production specification
+
+The PHG may report equivalent information to that provided by the Production-Specification attribute. If the PHG reports this information, it **shall** be encoded as follows for each quantity that is to be specified:
+
+OBX|n|ST|obx-3|0.0.0.x|obx-5|||||R
+
+where
+
+- *obx-3* is given by Table D.3.
+
+**Table D.3 – Continua services PHG production specifications nomenclature codes**
+
+| Quantity to enter in obx-5                | <i>obx-3 field</i>                   |
+|-------------------------------------------|--------------------------------------|
+| Serial number                             | 531972^MDC_ID_PROD_SPEC_SERIAL^MDC   |
+| Part number                               | 531973^MDC_ID_PROD_SPEC_PART^MDC     |
+| Hardware revision                         | 531974^MDC_ID_PROD_SPEC_HW^MDC       |
+| Software revision                         | 531975^MDC_ID_PROD_SPEC_SW^MDC       |
+| Firmware revision                         | 531976^MDC_ID_PROD_SPEC_FW^MDC       |
+| Protocol                                  | 531977^MDC_ID_PROD_SPEC_PROTOCOL^MDC |
+| Global medical device nomenclature (GMDN) | 531978^MDC_ID_PROD_SPEC_GMDN^MDC     |
+
+- *obx-5* shall be the appropriate 127-bit ASCII alpha-numeric string describing the quantity as specified in the OBX-3 field. Be sure to HL7-escape any separator characters in the string.
+
+#### D.1.1.5 Time synchronization capabilities
+
+The PHG **shall** report its time synchronization capability in an OBX segment encoded as follows:
+
+OBX|n|CWE|68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC|0.0.0.x|*obx-5*| | | | |R
+
+where *obx-5* **shall** be one of the synchronization protocols given in Table D.19. If the PHG has lost synchronization to NTP (its accuracy is less than five minutes) the PHG shall report 532224^MDC\_TIME\_SYNC\_NONE^MDC. Note that the interpretation of the time sync protocol in PCD is different to its meaning in [ISO/IEEE 11073-20601]. In the latter, the time sync protocol reported by the sensor indicates only the *method* by which the sensor synchronizes. The time capabilities bits entry of the Mds-Time-Info attribute indicates whether or not the sensor is actually synchronized. In the PCD environment, the time sync protocol indicates both the method and that it is currently synchronized by that method.
+
+In many of the popular operating systems on which PHGs are run it may not be possible to obtain the time synchronization state and thus accuracy since users are free to change these settings. In these situations it can be difficult to determine if synchronization has been lost. In the 'EBWW' (eyeball and wrist watch) case, a default accuracy is taken to be about two minutes.
+
+Example:
+
+OBX|n|CWE|68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC|0.0.0.x|532234^MDC\_TIME\_SYNC\_EBWW^MDC| | | | |R
+
+#### D.1.1.6 TimeInfo information
+
+The PHG may wish to report some of its time capabilities. It does not make any sense to report a time capabilities BITS field analogous to that provided by the MdsTimeInfo attribute on the sensor device since the synchronization state AND method are indicated by the time synchronization protocol OBX and PHGs are required to be at least UTC aware.
+
+##### D.1.1.6.1 Time synchronization accuracy
+
+The PHG **may** report its time synchronization accuracy if known. If reported the OBX segment **shall** be encoded as follows:
+
+OBX|n|NM|8221^MDC\_TIME\_SYNC\_ACCURRACY^MDC|0.0.0.x|*obx-5*|264339^MDC\_DIM\_MICRO\_SEC^MDC| | | | |R
+
+where *obx-5* **shall** be the 32-bit integer value of the accuracy in microseconds
+
+Example:
+
+OBX|n|NM|8221^MDC\_TIME\_SYNC\_ACCURACY^MDC|m.0.0.x|120000000|264339^MDC\_DIM\_MICRO\_SEC^MDC||||R
+
+#### D.1.1.6.2 Time resolution of absolute or UTC clock
+
+The PHG **may** report the resolution its clock used in the exchange protocol with the sensor. If reported, the OBX segment **shall** be encoded as follows:
+
+OBX|n|NM|68226^MDC\_TIME\_RES\_BO^MDC|0.0.0.x|obx-5|264339^MDC\_DIM\_MICRO\_SEC^MDC||||R
+
+where *obx-5* **shall** be the resolution of the clock in microseconds.
+
+#### D.1.1.6.3 Relative time clocks
+
+The PHG **shall** only report its relative time clock information in the case it is providing a time synchronization service for sensor devices.
+
+#### D.1.1.7 PHG provides time service
+
+If the PHG provides a relative time service that sensor devices can and do synchronize to, the PHG is required to provide additional information regarding this service according to the Timestamp and time synchronization clause. The existence and support of such a time service is out of scope with respect to these design guidelines.
+
+### D.1.2 Guidelines for encoding the MDS-OBX segments
+
+MDS-OBXes describe the properties and features of the sensor. A new [ISO/IEEE 11073-20601] association or the handling of a Date-Time-Adjustment attribute requires the encoding of a new set of MDS-OBX segments. The conditions for a new set of MDS-OBX segments are less clear for Bluetooth low energy sensors. In this specification the mapping to MDS OBXes is defined in terms of the sensor MDS object and its concomitant attributes. There is no requirement that this object or its attributes actually exist on the sensor device or PHG. Any sensor device whose data can be mapped to this object and its attributes by the PHG can be translated to compliant MDS-OBX segments.
+
+- The MDS-OBX segments **shall** be encoded as dictated in this clause.
+- For all MDS-OBX segments, OBX-11 **shall** be 'R', *except* for the top-level OBX which **shall** be 'X'.
+
+#### D.1.2.1 Top-level MDS-OBX (System-Id, System-Type, System-Type-Spec-List Attributes)
+
+Every new association or new OBR **shall** contain a top-level MDS-OBX encoded as follows:
+
+OBX|n||obx-3|m|||||X|||||obx-18
+
+where
+
+*obx-3* **shall** contain the sensor specialization encoded as a CWE data type.
+
+- The sensor specialization **shall** come from either the System-Type attribute or the System-Type-Spec-List attribute. [ISO/IEEE 11073-20601] states that the sensor MDS object can have either the System-Type-Spec-List or System-Type attribute, but *not* both.
+- If the System-Type-Spec-List attribute contains more than one entry
+  - *obx-3* **shall** be set to 528384^MDC\_DEV\_SPEC\_PROFILE\_HYDRA^MDC indicating the sensor supports multiple specializations.
+
+- An additional MDS-OBX **shall** be generated. See System-Type-Spec-List attribute encoding for details.
+
+*obx-18* **shall** contain the sensor's system id encoded as an EI data type where.
+
+- EI-1 is an entity identifier which may be the same as EI-3.
+- EI-3 is the system id as a 16-digit HEX string (without a 0x prefix) taken from the system id of the System-Id attribute.
+- EI-4 is EUI-64.
+
+Example:
+
+```
+OBX|n||528388^MDC_DEV_SPEC_PROFILE_PULS_OXIM^MDC|m|||||X||||||
+0022D6EE4AFBD410^^0022D6EE4AFBD410^EUI-64
+```
+
+The System-Type-Spec-List attribute **shall** only be encoded if it contains more than one entry.
+
+If the System-Type-Spec-List attribute is to be encoded, it **shall** be encoded as follows:
+
+```
+OBX|n|CWE|68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC|m.0.0.x|obx-5|||||R
+```
+
+where
+
+- *obx-5* **shall** contain the list of specialization and/or profile entries as encoded as CWE data types separated by the repetition symbol '⌂'.
+
+Example where the System-Type-Spec-List follows the top-level MDS-OBX and contains the body composition and pulse oximeter specializations:
+
+```
+OBX|n||528384^MDC_DEV_SPEC_PROFILE_HYDRA^MDC|m|||||X||||||0022D6014AFBD4
+18^^0022D6014AFBD418^EUI-64
+OBX|n+1|CWE|68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC|m.0.0.1|528404^MDC_DEV_SP
+EC_PROFILE_BCA^MDC~528388^MDC_DEV_SPEC_PROFILE_PULS_OXIM^MDC|||||R
+```
+
+#### D.1.2.2 System-Model attribute
+
+The System-Model attribute **shall** be translated to the OBX segments as specified in this clause if present. It is required by [ISO/IEEE 11073-20601].
+
+The System-Model attribute **shall** be represented by two OBX segments as follows:
+
+- The ASN.1-model-number **shall** be encoded as
+
+```
+OBX|n|ST|531969^MDC_ID_MODEL_NUMBER^MDC|m.0.0.x|obx-5|||||R
+```
+
+where *obx-5* **shall** be the string obtained from the ASN.1-model-number value of the attribute.
+
+- The ASN.1-manufacturer **shall** be encoded as
+
+```
+OBX|n|ST|531970^MDC_ID_MODEL_MANUFACTURER^MDC|m.0.0.x|obx-5|||||R
+```
+
+where *obx-5* **shall** be the string obtained from the ASN.1-manufacturer value. Be sure to HL7-escape any separator characters in the string.
+
+Examples:
+
+```
+OBX|n|ST|531970^MDC_ID_MODEL_MANUFACTURER^MDC|m.0.0.x|ContinuaSensors Inc|||||R
+OBX|n+1|ST|531969^MDC_ID_MODEL_NUMBER^MDC|m.0.0.x+1|39596-AAA|||||R
+```
+
+#### D.1.2.3 Production-Specification attribute
+
+The Production-Specification attribute **shall** be translated to the OBX segments as specified in this clause if present; Continua requires this attribute and that it has at least the Firmware and Serial
+
+ASN.1-spec-type entries; in [ISO/IEEE 11073-20601] this attribute is optional. The attribute contains a sequence of ASN.1-ProdSpecEntry structs.
+
+The Production-Specification attribute **shall** be encoded into one OBX for each ASN.1-ProdSpecEntry struct present in the attribute as follows:
+
+OBX|n|ST|obx-3|m.0.0.x|obx-5| | | | |R| | | | |obx-18
+
+where for each ASN.1-ProdSpecEntry:
+
+- obx-3 is given by Table D.4.
+
+**Table D.4 – Continua services sensor production specification nomenclature codes**
+
+| ASN.1 spec-type value | obx-3 field                             |
+|-----------------------|-----------------------------------------|
+| unspecified(0)        | 531971^MDC_ID_PROD_SPEC_UNSPECIFIED^MDC |
+| serial(1)             | 531972^MDC_ID_PROD_SPEC_SERIAL^MDC      |
+| part(2)               | 531973^MDC_ID_PROD_SPEC_PART^MDC        |
+| hardware(3)           | 531974^MDC_ID_PROD_SPEC_HW^MDC          |
+| software(4)           | 531975^MDC_ID_PROD_SPEC_SW^MDC          |
+| firmware(5)           | 531976^MDC_ID_PROD_SPEC_FW^MDC          |
+| protocol(6)           | 531977^MDC_ID_PROD_SPEC_PROTOCOL^MDC    |
+| GMDN(7)               | 531978^MDC_ID_PROD_SPEC_GMDN^MDC        |
+
+- obx-5 **shall** be the string obtained from the ASN.1-product-spec for that ASN.1-ProdSpecEntry. Be sure to HL7-escape any separator characters in the string.
+- obx-18 **may** be used to encode the ASN.1-component-id value of the ASN.1 ProdSpecEntry as follows:
+  - The ASN.1-component-id is a 16-bit integer interpreted as a private OID. The Production-Specification attribute contains no additional information with respect to this value. If the value is encoded into obx-18 it shall be encoded as an EI data type as follows:
+    - EI-1 the PrivateOID as digits
+    - EI-2 the name 'PrivateOID'
+    - EI-3 the system id obtained from the System-Id attribute
+    - EI-4 the name 'EUI-64'
+
+Example for a production-specification attribute with three ASN.1- ProdSpecEntry structs where one entry 'BCA&Weight-444.4' needs to be escaped:
+
+OBX|n|ST|531976^MDC\_ID\_PROD\_SPEC\_FW^MDC|m.0.0.x|Revision\_14.5| | | | |R| | | | |  
+64777^PrivateOID^0022D6014AFBD418^EUI-64  
+OBX|n+1|ST|531972^MDC\_ID\_PROD\_SPEC\_SERIAL^MDC|m.0.0.x+1|1203ARF33342| | | | |R  
+OBX|n+2|ST|531975^MDC\_ID\_PROD\_SPEC\_SW^MDC|m.0.0.x+2|BCASensor3.3| | | | |R  
+OBX|n+3|ST|531974^MDC\_ID\_PROD\_SPEC\_HW^MDC|m.0.0.x+3|BCA\T\Weight-  
+444.4| | | | |R
+
+#### D.1.2.4 Date-and-Time attribute
+
+The Date-and-Time attribute **shall** be translated to an OBX segment *if* present *and* the PHG determines that it is better synchronized than the sensor. See clause D.1.3.1.5 for details on how the PHG uses the sensor's Mds-Time-Info attribute to determine who has superior synchronization. Sensors that do not use an absolute timestamp in any measurements need not support this attribute.
+
+If the sensor reports this attribute but does not use it in any observation being scoped by this MDS n-tuple, this OBX shall not be reported. This attribute is the sensor's sense of current time in the current time zone of the PHG.
+
+The date-and-time attribute **shall** be encoded as follows:
+
+OBX|n|DTM|67975^MDC\_ATTR\_TIME\_ABS^MDC|m.0.0.x|obx-5| | | | |R| | |obx-14
+
+where:
+
+- obx-5 **shall** be the time reported in the attribute formatted as a DTM data type.
+- obx-14 **shall** be the PHG's current time formatted as a DTM data type.
+
+In a test situation, the PHG:
+
+- **shall** be able to be synchronized to NTP time
+- the DTM data type in OBX-14 **shall** have the offset added to UTC time to get local time or -0000 if UTC only.
+
+In an operational situation, the PHG:
+
+- **may** report its current time as a local time if synchronization to NTP time is lost or becomes unavailable.
+
+If there is a time fault, it is impossible for the PHG to recover the PHD timeline prior to the time fault. The date-time-adjustment must be known to recover the timeline. When reporting measurements with a time fault, obx-5 shall be empty. Note that the segment with obx-5 being empty is reported in the MDS-OBXes that are associated with the data prior to the time fault. After the time fault the sensor's current time may be some arbitrary factory default, but it can be compared with and aligned to the PHG's current time and thereby corrected.
+
+Example where the association occurred in the eastern time zone of the US during daylight savings time on 30 May at 12:23:16.258, where the sensor is 10 seconds slow:
+
+OBX|n|DTM|67975^MDC\_ATTR\_TIME\_ABS^MDC|m.0.0.x|20130530122306.00| | | | |R| | |20130530122316.258-0400
+
+Note that this OBX is a coincident timestamp pair. The Date-and-Time attribute represents the current time in absolute time format. When the PHG obtains the value of this attribute it is assumed that it is the current time in the time zone of the PHG. Errors by the device user (for example forgetting to change times as the device is taken across time zones) are not and cannot be taken into account.
+
+#### D.1.2.5 Base-Offset-Time
+
+The Base-Offset-Time attribute **shall** be translated to an OBX segment *if present and* the PHG determines that it is better synchronized than the sensor. See clause D.1.3.1.5 for details on how the PHG uses the sensor's Mds-Time-Info attribute to determine who has superior synchronization. Sensors that do not use a base offset timestamp in any measurements need not support this attribute. If the sensor reports this attribute but does not use it in any observation being scoped by this MDS n-tuple, this OBX shall not be reported. The Base-Offset-Time attribute contains a base time plus the offset in minutes to the local time. Note that the definition of the offset is opposite that of the offset in a DTM data type. In base-offset time, one adds the offset to the base time to get local time. In a DTM timestamp, one adds the offset to UTC to get the local time. But what is displayed in a DTM timestamp is the local time and not UTC. This attribute is the sensor's sense of current time in the current time zone of the PHG.
+
+The Base-Offset-Time attribute shall be encoded as follows:
+
+OBX|n|DTM|68225^MDC\_ATTR\_TIME\_BO^MDC|m.0.0.x|obx-5| | | | |R| | |obx-14
+
+where
+
+- *obx-5* shall be the time reported in the attribute formatted as a DTM data type.
+- *obx-14* shall be the PHG's current time formatted as a DTM data type.
+
+In a test situation the PHG:
+
+- shall be able to be synchronized to NTP time
+- the DTM data type in OBX-14 shall have the offset to UTC time or -0000 if UTC only
+
+In an operational situation the PHG:
+
+- may report its current time as a local time if synchronization to NTP time is lost or becomes unavailable.
+
+Example where the association occurred in the eastern time zone of the US during daylight savings time on 30 May at 16:23:16.258:
+
+```
+OBX|n|DTM|68225^MDC_ATTR_TIME_BO^MDC|m.0.0.x|20130530122316.455-  
+0400|||||R||20130530122316.258-0400
+```
+
+Note that this OBX is a coincident timestamp pair. The Base-Offset-Time attribute represents the current time in Base offset time format. When the PHG obtains the value of this attribute it is assumed that it is the current time in the time zone of the PHG; in other words the base time plus offset gives the local current time in the time zone of the PHG. Errors by the device user (for example forgetting to change the offset as the device is taken across time zones) are not and cannot be taken into account.
+
+#### D.1.2.6 Relative-Time attribute
+
+The Relative-Time attribute **shall** be translated to an OBX segment if present. Sensors that do not use a relative timestamp in any measurements need not support this attribute.
+
+The Relative-Time attribute **shall** be encoded as follows:
+
+```
+OBX|n|NM|67983^MDC_ATTR_TIME_REL^MDC|m.0.0.x|obx-  
+5|264339^MDC_DIM_MICRO_SEC^MDC|||||R||obx-14||||obx-18
+```
+
+where:
+
+- *obx-5* shall be the 32-bit integer value of the time reported in the attribute converted from its units of 1/8 milliseconds to microseconds. The sent value is multiplied by 1000 and divided by 8.
+- *obx-14* shall be the PHG's current time formatted as a DTM data type.
+
+In a test situation the PHG:
+
+- shall be able to be synchronized to NTP time
+- the DTM data type in OBX-14 shall have the offset to UTC time or -0000 if UTC-only.
+
+In an operational situation the PHG:
+
+- may report only its current time as a local time if synchronization to NTP time is lost or becomes unavailable.
+- *obx-18* may include an identifier for the timebase used by the sensor for the relative time clock as an EI data type\*. Note that in this case only the first two components of the EI data type are used since the identifier (unlike a EUI-64) is not universal but 'local'.
+
+NOTE \* – Using the [ISO/IEEE 11073-20601] protocol the PHG cannot obtain the sensor's timebase information and the best the PHG can do is state that the timebase is the timebase of the sensor which would
+
+be indicated by EI-1 set to the ASN.1-system-id and EI-2 set to 'TIMEBASE\_ID'. The entry provides no useful information.
+
+The absence of an OBX-18 entry indicates that the PHG does not have any additional information over that which is implied.
+
+The purpose of the OBX-18 entry is in the case where the PHG and sensor are implemented so that both are synchronized by the same relative time clock, for example a master Bluetooth clock. The scenario is likely in a hospital intensive care ward but unlikely in the home environment with Continua sensors. In addition the means to obtain that information is out of band with respect to any of the supported Continua interface protocols. If one has this situation, obx-18 should be appropriately valued.
+
+Example with default timebase:
+
+```
+OBX|n|NM|67983^MDC_ATTR_TIME_REL^MDC|m.0.0.x|536870911875|264339^MDC_DIM_MI  
+CRO_SEC^MDC| |||R|||20130530122316.258-0400;
+```
+
+Example with out-of-band timebase information:
+
+```
+OBX|n|NM|67983^MDC_ATTR_TIME_REL^MDC|m.0.0.x|536870911875|264339^MDC_DIM_MI  
+CRO_SEC^MDC| |||R|||20130530122316.258-0400| |||BT_ABCDEF123456^TIMEBASE_ID;
+```
+
+Note that this OBX is a coincident timestamp pair.
+
+#### D.1.2.7 HiRes-Relative-Time attribute
+
+The HiRes-Relative-time attribute **shall** be translated to an OBX segment if present. Sensors that do not use a high resolution relative timestamp in any measurements need not support this attribute.
+
+The HiRes-Relative-Time attribute **shall** be encoded as follows:
+
+```
+OBX|n|NM|68072^MDC_ATTR_TIME_REL_HI_RES^MDC|m.0.0.x|obx-  
+5|264339^MDC_DIM_MICRO_SEC^MDC| |||R|||obx-14| |||obx-18
+```
+
+where:
+
+- *obx-5* shall be the 64-bit integer value of the time reported in the attribute.
+- *obx-14* shall be the PHG's current time formatted as a DTM data type.
+
+In a test situation the PHG:
+
+- shall be able to be synchronized to NTP time
+- the DTM data type in OBX-14 shall have the offset to UTC time or -0000 if UTC-only.
+
+In an operational situation the PHG:
+
+- may report only its current time as a local time if synchronization to NTP time is lost or becomes unavailable.
+- *obx-18* may include an identifier for the timebase used by the sensor for the high resolution relative time clock as an EI data type. (See clause D.1.2.6 for clarification of this entry). Note that in this case only the first two components of the EI data type are used since the identifier, unlike the identification type EUI-64, is not universal but 'local'.
+
+Example with default timebase:
+
+```
+OBX|n|NM|67983^MDC_ATTR_TIME_REL^MDC|m.0.0.x|1250000|264339^MDC_DIM_MICRO_S  
+EC^MDC| |||R|||20130530122316.258-0400;
+```
+
+Example with out-of-band timebase information:
+
+```
+OBX|n|NM|68072^MDC_ATTR_TIME_REL_HI_RES^MDC|m.0.0.x|1250000|264339^MDC_DIM_  
+MICRO_SEC^MDC| |||R|||20130530122316.258-  
+0400| |||BT_ABCDEF123456^TIMEBASE_ID;
+```
+
+Note that this OBX is a coincident timestamp pair.
+
+#### D.1.2.8 Mds-Time-Info attribute
+
+The Mds-Time-Info attribute **shall** be translated into OBX segments as specified in this clause if present; sensors that do not support any type of real time clock do not need to support this attribute. The Mds-Time-Info attribute is translated into up to six OBX segments.
+
+The information reported in this attribute is used by the PHG to determine who has superior synchronization. See clause D.1.3.1.5 for details.
+
+##### D.1.2.8.1 ASN.1-mds-time-cap-state
+
+The ASN.1-mds-time-cap-state **shall** be encoded as follows:
+
+OBX|n|CWE|68219^MDC\_TIME\_CAP\_STATE^MDC|m.0.0.x|obx-5| | | | |R
+
+where *obx-5* **shall** encode the ASN.1-mds-time-cap-state value as an ASN.1 BITs field as follows:
+
+- each set bit is represented as a CWE data type with the bit setting CWE-1 and the string name followed by the bit position in parentheses in CWE-2
+- set bits **shall** be included in the list
+- cleared bits **may** be included in the list
+- each CWE entry **shall** be separated by the repetition symbol '~'
+- the possible entries **shall** be one or more of (from [ISO/IEEE 11073-20601])
+  - o <0 or 1>^mds-time-capab-real-time-clock(0)
+  - o <0 or 1>^mds-time-capab-set-clock(1)
+  - o <0 or 1>^mds-time-capab-relative-time(2)
+  - o <0 or 1>^mds-time-capab-high-res-relative-time(3)
+  - o <0 or 1>^mds-time-capab-sync-abs-time(4)
+  - o <0 or 1>^mds-time-capab-sync-rel-time(5)
+  - o <0 or 1>^mds-time-capab-sync-hi-res-relative-time(6)
+  - o <0 or 1>^mds-time-capab-bo-time(7)
+  - o <0 or 1>^mds-time-state-abs-time-synced(8)
+  - o <0 or 1>^mds-time-state-rel-time-synced(9)
+  - o <0 or 1>^mds-time-state-hi-res-relative-time-synced(10)
+  - o <0 or 1>^mds-time-mgr-set-time(11)
+  - o <0 or 1>^mds-time-capab-sync-bo-time(12)
+  - o <0 or 1>^mds-time-state-bo-time-synced(13)
+  - o <0 or 1>^mds-time-state-bo-time-UTC-aligned(14)
+  - o <0 or 1>^mds-time-dst-rules-enabled(15)
+
+where the name *mds-time-\** is optional.
+
+Note that settings referring to both Base-Offset time and Absolute-Time are not allowed.
+
+Example (the first is preferred)
+
+OBX|n|CWE|68219^MDC\_TIME\_CAP\_STATE^MDC|m.0.0.x|1^mds-time-capab-real-time-clock(0)~1^mds-time-capab-set-clock(1)~1^mds-time-capab-relative-time(2)~1^mds-time-mgr-set-time(11)| | | | |R
+
+or
+
+OBX|n|CWE|68219^MDC\_TIME\_CAP\_STATE^MDC|m.0.0.x|1^(0)~1^(1)~1^(2)~1^(11)| | | | |R
+
+##### D.1.2.8.2 ASN.1-time-sync-protocol
+
+The semantic meaning for this MDS-OBX entry is different in PCD than in [ISO/IEEE 11073-20601]. In PCD an entry here indicates that the sensor not only uses this method to synchronize, but that it *is* synchronized using this method. The ISO/IEEE 11073-20601 sensor only indicates the
+
+*method* it uses to synchronize in this structure, the ASN.1- mds-time-cap-state indicates whether or not it is synchronized.
+
+Thus, if the ASN.1-time-sync-protocol is not MDC\_TIME\_SYNC\_NONE, the PHG needs to check the ASN.1- mds-time-cap-state first to see if the sensor indicates that it is synchronized. If it is, then then the PHG **shall** report the value in the ASN.1-time-sync-protocol struct in this OBX. If the ASN.1- mds-time-cap-state indicates the device is not synchronized, the value 532224^MDC\_TIME\_SYNC\_NONE^MDC **shall** be reported in the OBX.
+
+The ASN.1-time-sync-protocol MDS-OBX **shall** be encoded as follows:
+
+OBX|n|CWE|68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC|m.0.0.x|obx-5| | | | |R
+
+where
+
+obx-5 **shall** be the reported nomenclature code as a CWE data type if the sensor is synchronized. The attribute reports only the nomenclature code, the partition is implied to be nom-part-infrastruct. The currently defined synchronization protocols as a CWE data type are given in Table D.19. If the sensor is not synchronized, the value 532224^MDC\_TIME\_SYNC\_NONE^MDC **shall** be reported.
+
+Example if synchronized (the first is preferred):
+
+OBX|n|CWE|68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC|m.0.0.x|532234^MDC\_TIME\_SYNC\_EBWW^MDC| | | | |R
+
+or
+
+OBX|n|CWE|68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC|m.0.0.x|532234^MDC| | | | |R
+
+Example if not synchronized
+
+OBX|n|CWE|68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC|m.0.0.x|532224^MDC\_TIME\_SYNC\_NONE^MDC| | | | |R
+
+#### D.1.2.8.3 ASN.1-time-sync-accuracy
+
+The ASN.1-time-sync-accuracy **shall not** be encoded into an OBX segment if the sent value is 0xFFFFFFFF which indicates the accuracy is unknown.
+
+Otherwise the ASN.1-time-sync-accuracy **shall** be encoded as follows:
+
+OBX|n|NM|8221^MDC\_TIME\_SYNC\_ACCURRACY^MDC|m.0.0.x|obx-5|264339^MDC\_DIM\_MICRO\_SEC^MDC| | | | |R
+
+where obx-5 **shall** be the 32-bit integer value of the accuracy reported in the ASN.1-time-sync-accuracy converted from its units of 1/8 milliseconds to microseconds; the sent value is multiplied by 1000 and divided by 8. Note that a sent value of zero indicates an accuracy better than 125 microseconds but it cannot be resolved.
+
+Example:
+
+OBX|n|NM|8221^MDC\_TIME\_SYNC\_ACCURRACY^MDC|m.0.0.x|9000000|264339^MDC\_DIM\_MICRO\_SEC^MDC| | | | |R
+
+#### D.1.2.8.4 ASN.1-time-resolution-abs-time
+
+The ASN.1-time-resolution-abs-time **shall not** be encoded into an OBX segment if the value is 0 which indicates the resolution is unknown. Note that this struct is used for *both* absolute time and base-offset time accuracy; which of the two applies depends upon the capabilities settings. A sensor cannot support both absolute time and base-offset time during an association.
+
+Otherwise the ASN.1-time-resolution-abs-time **shall** be encoded as follows:
+
+OBX|n|NM|obx-3|m.0.0.x|obx-5|264339^MDC\_DIM\_MICRO\_SEC^MDC| | | | |R
+
+- If the mds-time-capab-real-time-clock(0) bit is set then
+
+- *obx-3* **shall** be 68222<sup>MDC\_TIME\_RES\_ABS^MDC</sup>
+  - *obx-5* **shall** be the 16-bit integer value of the resolution reported in the ASN.1-time-resolution-abs-time converted from its units of 1/100ths seconds to microseconds; the value is multiplied by 10,000.
+- If the mds-time-capab-bo-time(7) bit is set then
+- *obx-3* **shall** be 68226<sup>MDC\_TIME\_RES\_BO^MDC</sup>
+  - *obx-5* **shall** be the 16-bit integer value of the resolution reported in the ASN.1-time-resolution-abs-time converted from its units of 1/65536ths of a second to microseconds; the value is multiplied by 1,000,000/65,536.
+
+Example when supporting absolute time with 1-second resolution:
+
+```
+OBX|n|NM|68222^MDC_TIME_RES_ABS^MDC|m.0.0.x|1000000|264339^MDC_DIM_MICRO_SE  
+C^MDC||||R
+```
+
+or when supporting base-offset time with 1/65536-th second resolution:
+
+```
+OBX|n|NM|68226^MDC_TIME_RES_BO^MDC|m.0.0.x|15.26|264339^MDC_DIM_MICRO_SEC^M  
+DC||||R
+```
+
+#### D.1.2.8.5 ASN.1-time-resolution-rel-time
+
+The ASN.1-time-resolution-rel-time **shall not** be encoded into an OBX segment if the sent value is 0 which indicates the resolution is unknown.
+
+Otherwise the ASN.1-time-resolution-rel-time **shall** be encoded as follows:
+
+```
+OBX|n|NM|68223^MDC_TIME_RES_REL^MDC|m.0.0.x|obx-  
+5|264339^MDC_DIM_MICRO_SEC^MDC||||R
+```
+
+where *obx-5* **shall** be the 32-bit integer value of the resolution reported in the ASN.1-time-resolution-rel-time converted from its units of 1/8th milliseconds to microseconds.
+
+Example 1 relative-time unit resolution:
+
+```
+OBX|n|NM|68223^MDC_TIME_RES_REL^MDC|m.0.0.x|125|264339^MDC_DIM_MICRO_SEC^MDC||||R
+```
+
+#### D.1.2.8.6 ASN.1-time-resolution-high-res-time
+
+The ASN.1-time-resolution-high-res-time **shall not** be encoded into an OBX segment if the sent value is 0 which indicates the resolution is unknown.
+
+Otherwise the ASN.1-time-resolution-high-res-time **shall** be encoded as follows:
+
+```
+OBX|n|NM|68224^MDC_TIME_RES_REL_HI_RES^MDC|m.0.0.x|obx-  
+5|264339^MDC_DIM_MICRO_SEC^MDC||||R
+```
+
+where *obx-5* **shall** be the 64-bit integer value of the resolution reported in the ASN.1-time-resolution-high-res-time whose units are microseconds.
+
+Example: 1 µs resolution
+
+```
+OBX|n|NM|68224^MDC_TIME_RES_REL_HI_RES^MDC|m.0.0.x|1|264339^MDC_DIM_MICRO_SEC^MDC||||R
+```
+
+Example of the entire package when supporting absolute, relative and hi-res times:
+
+```
+OBX|n|CWE|68219^MDC_TIME_CAP_STATE^MDC|m.0.0.x|1^mds-time-capab-real-time-clock(0)~1^mds-  
+time-capab-set-clock(1)~1^mds-time-capab-relative-time(2)~1^mds-time-capab-high-res-relative-  
+time(3)~1^mds-time-capab-sync-abs-time(4)||||R  
+OBX|n+1|CWE|68220^MDC_TIME_SYNC_PROTOCOL^MDC|m.0.0.x+1|532234^MDC_TIME_SYNC_EBWW^MDC||||R  
+OBX|n+2|NM|8221^MDC_TIME_SYNC_ACCURRACY^MDC|m.0.0.x+2|9000000|264339^MDC_DIM_MICRO_SEC^MDC|||  
+R
+```
+
+```
+OBX|n+3|NM|68222^MDC_TIME_RES_ABS^MDC|m.0.0.x+3|1000000|264339^MDC_DIM_MICRO_SEC^MDC||||R
+OBX|n+4|NM|68223^MDC_TIME_RES_REL^MDC|m.0.0.x+4|125|264339^MDC_DIM_MICRO_SEC^MDC||||R
+OBX|n+5|NM|68224^MDC_TIME_RES_REL_HI_RES^MDC|m.0.0.x+5|1|264339^MDC_DIM_MICRO_SEC^MDC||||R
+```
+
+### D.1.2.9 Reg-Cert-Data-List attribute
+
+The Reg-Cert-Data-List attribute **shall** be translated into OBX segments as specified in this clause if present. Continua require that sensors have this attribute and the Continua defined auth-body ASN.1 structures. The attribute is optional in [ISO/IEEE 11073-20601].
+
+Each ASN.1-reg-cert entry in the Reg-Cert-Data-List attribute **shall** be encoded as follows:
+
+- The ASN.1-auth-body **shall** be encoded as follows:
+
+```
+OBX|n|CWE|68218^MDC_ATTR_REG_CERT_DATA_AUTH_BODY^MDC|m.0.0.x|obx-5||||R
+```
+
+where *obx-5* **shall** be the ASN.1-auth-body 8-bit integer encoded as a CWE data type where CWE-1 is the integer value and CWE-2 is the name of the value as defined by [ISO/IEEE 11073-20601]. Current defined values expressed as CWE data types are one of:
+
+- o 0^auth-body-empty
+- o 1^auth-body-ieee-11073
+- o 2^auth-body-continua
+- o 254^auth-body-experimental
+- o 255^auth-body-reserved
+
+Example:
+
+```
+OBX|n|CWE|68218^MDC_ATTR_REG_CERT_DATA_AUTH_BODY^MDC|m.0.0.x|2^auth-body-continua||||R
+```
+
+- If the ASN.1-auth-body value is 2 (ASN.1-auth-body-continua) and the ASN.1-auth-body-struct-type is the ASN.1-continua-version-struct (1)
+
+- o The ASN.1-major-IG-version and ASN.1-minor-IG-version **shall** be encoded into an OBX as follows:
+
+```
+OBX|n|ST|532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC|m.0.0.x.y|obx-5||||R
+```
+
+where *obx-5* **shall** be a combination of the ASN.1-major-IG-version value and ASN.1-minor-IG-version value separated by a dot, e.g., '3.5'
+
+Example for version 4.0:
+
+```
+OBX|n|ST|532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC|m.0.0.x.y|4.0||||R
+```
+
+- o The ASN.1-certified-devices component **shall** be encoded into an OBX as follows:
+
+```
+OBX|n|NM|532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC|m.0.0.x.y|obx-5||||R
+```
+
+where *obx-5* **shall** be the list of 16-bit integers representing the Continua defined transport Tcode and sensor specialization code (MDC\_DEV\_\*\_SPEC\_PROFILE\_\* – 4096 + Tcode \* 8192) encoded as an NM data type separated by the repetition symbol '!'.
+
+Example:
+
+```
+OBX|n|NM|532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC|m.0.0.x.y|4^8196~16388~24580~7~8199~16391~24583~8~8200~16392~24584~15~8207~16399~24591~72~8264~16456~24648||||R
+```
+
+- If the ASN.1-auth-body value is 2 (ASN.1-auth-body-continua) and the ASN.1-auth-body-struct-type is the ASN.1-continua-reg-struct (2)
+
+- o The regulation-bit-field **shall** be encoded into an OBX as follows:
+
+OBX|n|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|m.0.0.x.y|o  
+bx-5| | | | |R
+
+where *obx-5* **shall** be the ASN.1-regulation-bit-field BITS value encoded as a CWE data type CWE-1 is the bit setting and CWE-2 the name with the bit position in parentheses. At this time there is only one bit setting defined:
+
+- unregulated-device(0)
+
+Example for unregulated device:
+
+OBX|n|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|m.0.0.x.y|1^unregulated-device(0)| | | | |R
+
+Example for regulated device:
+
+OBX|n|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|m.0.0.x.y| | | | |R
+
+or:
+
+OBX|n|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|m.0.0.x.y|0^unregulated-device(0)| | | | |R
+
+- If the ASN.1-auth-body value is not ASN.1-auth-body-continua no further encoding of the ASN.1-reg-cert component into OBX segments is required. At this time no further ASN.1-reg-cert entry types have been defined. However, if the structures are known corresponding OBX segments **should** be encoded.
+
+An example of the entire Continua Reg-Cert-Data-List attribute encoding is shown below (the example sensor is certified for several specializations and transports):
+
+OBX|n|CWE|68218^MDC\_ATTR\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|m.0.0.x|2^auth-body-continua| | | | |R  
+OBX|n+1|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|m.0.0.x.1|4.0| | | | |R  
+OBX|n+2|NM|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|m.0.0.x.2|4~8196~16388~24580~7~8199~16391~24583~8~8200~16392~24584~15~8207~16399~24591~72~8264~16456~24648| | | | |R  
+OBX|n+3|CWE|68218^MDC\_ATTR\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|m.0.0.x+1|2^auth-body-continua| | | | |R  
+OBX|n+4|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|m.0.0.x+1.1|1^unregulated-device(0)| | | | |R
+
+Note that a MDC\_ATTR\_REG\_CERT\_DATA\_AUTH\_BODY OBX occurs for each ASN.1-reg-cert entry, one of which is the parent of the Continua Version Struct and the other is the parent of the Continua Regulation Status Struct.
+
+#### D.1.2.10 Tick-Resolution attribute
+
+This attribute shall be encoded into an OBX segment as specified in this clause if present as follows:
+
+OBX|n|NM|68229^MDC\_ATTR\_TICK\_RES^MDC|m.0.0.x|obx-5|268992^MDC\_DIM\_TICK^MDC| | | | |R
+
+where *obx-5* shall be the number of ticks per second.
+
+Note that this attribute is currently only required in the MDS object of the ECG specialization when the RR-interval is reported.
+
+Example of 1024 ticks per second:
+
+OBX|n|NM|68229^MDC\_TICK\_RESOLUTION^MDC|m.0.0.x|1024|268992^MDC\_DIM\_TICK^MDC| | | | |R
+
+#### D.1.2.11 Power-Status attribute
+
+The encoding of this attribute into OBX segments is optional. If encoded it shall be encoded as follows:
+
+OBX|n|CWE|67925^MDC\_ATTR\_POWER\_STAT^MDC|m.0.0.x|obx-5| | | | |R
+
+where *obx-5* **shall** be the value of the attribute encoded as a CWE data type. The attribute value is an ASN.1-BITS16 value and is one or more of:
+
+- o onMains(0)
+- o onBattery(1)
+- o chargingFull(8)
+- o chargingTrickle(9)
+- o chargingOff(10).
+
+Example:
+
+OBX|n|NM|67925^MDC\_ATTR\_POWER\_STAT^MDC|m.0.0.x|1^onMains(0)~1^chargingTrickle(9)| | | | |R
+
+#### D.1.2.12 Battery-Level attribute
+
+The encoding of this attribute into OBX segments is optional. If encoded it **shall** be encoded as follows:
+
+OBX|n|NM|67996^MDC\_ATTR\_VAL\_BATT\_CHARGE^MDC|m.0.0.x|obx-5|262688^MDC\_DIM\_PERCENT^MDC| | | |R
+
+where *obx-5* **shall** be the value of the attribute. Note values greater than 100 are undefined and **should not** be transmitted.
+
+Example:
+
+OBX|n|NM|67996^MDC\_ATTR\_VAL\_BATT\_CHARGE^MDC|m.0.0.x|94.3|262688^MDC\_DIM\_PERCENT^MDC| | | |R
+
+#### D.1.2.13 Remaining-Battery-Time attribute
+
+The encoding of this attribute into OBX segments is optional. It is an MDER FLOAT. If encoded it **shall** be encoded as follows:
+
+OBX|n|NM|67976^MDC\_ATTR\_TIME\_BATT\_REMAIN^MDC|m.0.0.x|obx-5|obx-6| | | |R
+
+where
+
+- *obx-5* **shall** be the value given by the ASN.1-value struct
+- *obx-6* **shall** be the value of the ASN.1-unit struct encoded as a CWE data type. The ASN.1-unit value is a nomenclature code from the MDC\_PART\_DIM (4) partition and is one of MDC\_DIM\_MIN, MDC\_DIM\_HR, or MDC\_DIM\_DAY.
+
+Example:
+
+OBX|n|NM|67976^MDC\_ATTR\_TIME\_BATT\_REMAIN^MDC|m.0.0.x|7.22|264384^MDC\_DIM\_HR^MDC| | | |R
+
+#### D.1.2.14 Set Time action
+
+If the sensor requests that its time is to be set, [ISO/IEEE 11073-20601] requires that the PHG must comply. If the sensor responds with a rors (success), the PHG **shall** assume that the sensor times are now synchronized with its clock. If the PHG has already created a coincident timestamp pair OBX from a previous GET request response, a new coincident timestamp pair OBX **shall** be created where OBX-5 and OBX-14 are now based upon the time the PHG sent in the SetTime or SetBOTime action. No new GET request is required. Since the sensor and PHG are synchronized, the PHG need only translate the sensor timestamps in scan event reports to local time plus offset, no
+
+corrections for clock skews are necessary. The sensor may or may not send a date-time-adjustment due to the Set Time action.
+
+If the sensor has already sent observations on the previous timeline, the set time action breaks the timeline and the event needs to be handled as if a date-time-adjustment were received. If the actual adjustment is small (less than some value) then a new OBR is not needed; only an update of the coincident timestamp pair OBX is needed (see clause D.1.4.1).
+
+#### D.1.2.15 Real time MDS-OBX attributes
+
+[ISO/IEEE 11073-20601] allows the sensor to event dynamic and observational MDS attributes in scan event reports, for example, to update the battery level.
+
+- Updates of the Power-Status, Battery-Level and remaining Battery-Time attributes **may** be encoded into their respective OBX segments as defined above.
+- If a current time attribute is sent it **shall not** be encoded into an OBX segment as it does not represent any change in the time line and their inclusion could cause confusion. A change in the time line is indicated by a Date-Time-Adjustment attribute.
+
+#### D.1.3 Guidelines for encoding the Metric-OBX segments
+
+Metric-OBX segments are generated from observations. In [ISO/IEEE 11073-20601], all physiological observations are represented by one of three classes of metric objects and the set of attributes (shown in Table D.20, Table D.21, Table D.22 and Table D.23) that represent observations in those objects. In this specification the mapping to Metric OBXes is defined in terms of these metric objects and their concomitant attributes. *There is no requirement that these objects or attributes actually exist on the sensor device or PHG.* Any sensor device whose data can be mapped to these objects and attributes by the PHG can be translated to compliant Metric-OBX segments.
+
+Unlike the MDS-OBXes where a single attribute can map to one or more OBX segments, several attributes in the metric object representing the observation map to a single OBX segment. For example, in the non-compound case, the TYPE, Metric-Id, Metric-Id-Partition, Unit-code, the chosen observational attribute and timestamp, Measurement-Status, Unit-LabelString, Label-String and Enum-Observed-Value-Partition attributes are used to populate fields of a single OBX segment. The remaining non-protocol-specific attributes form facet OBX segments.
+
+Given the observation in terms of the 11073-20601 metric object the attributes will be either mapped to:
+
+1. a single ISO/IEEE 11073-20601 METRIC-level OBX segment with zero or more facet OBX segments
+2. a single 11073-10201 CHANNEL-level OBX segment with one or more METRIC-level OBX segments.
+
+Case 2 occurs only when the metric object has one of the three possible compound numeric attributes.
+
+The guidelines in this clause are independent of specialization and indicate how one takes a generic metric object representing an observation and converts it into one or more OBX segments. In all cases there will be one parent OBX and zero or more child OBXes. In the non-compound case the parent OBX is at the METRIC-level. In the compound case the parent OBX is at the channel level. As of the writing of these guidelines, there are no cases where a 'child' OBX will also have a child.
+
+For Continua certified Bluetooth low energy devices, the Transcoding White Paper [Bluetooth PHDT] provides the mapping of the characteristic values to hypothetical
+
+ISO/IEEE 11073-20601 metric objects and attributes. Thus the guidelines provided here can be applied to these sensors as well.
+
+Annex E provides a set of tables containing detailed information for specific attributes for the currently defined specializations. The tables will save one from reverting to the specialization documents to find, for example, the possible status bit settings for the pulse oximeter specialization device status measurement, the possible Unit-Codes for the thermometer specialization temperature measurement, etc.
+
+#### D.1.3.1 Case 1: Measurement contains no compound attribute
+
+In case 1 a single OBX segment is often sufficient to represent the observation. This single OBX segment is referred to as the METRIC-level OBX segment in this clause in reference to the 11073-10201 METRIC-level.
+
+The conversion of an observation to PCD-01 OBX segment(s) can be summarized as follows:
+
+- OBX-1 indicates the next OBX segment as always.
+- OBX-2 and OBX-5 are determined by one of the value-type observational attributes of the metric object; there can be one and only one of these attributes in a given observation. OBX-5 is the value and OBX-2 is the data type. The list of [ISO/IEEE 11073-20601] value-type observational attributes and their corresponding data types is shown in Table D.5 (compound attributes are also shown).
+
+**Table D.5 – Primary observational metric attributes**
+
+| OBX-2     | Observational attribute            |
+|-----------|------------------------------------|
+| NM        | Basic-Nu-Observed-Value            |
+| NM        | Simple-Nu-Observed-Value           |
+| NM        | Nu-Observed-Value                  |
+| NA        | Simple-Sa-Observed-Value           |
+| CWE       | Enum-Observed-Value-Simple-Bit-Str |
+| CWE       | Enum-Observed-Value-Basic-Bit-Str  |
+| ST        | Enum-Observed-Value-Simple-Str     |
+| CWE or ST | Enum-Observed-Value                |
+| NM        | Compound-Basic-Nu-Observed-Value   |
+| NM        | Compound-Simple-Nu-Observed-Value  |
+| NM        | Compound-Nu-Observed-Value         |
+
+- OBX-3 is determined by the TYPE, Metric-Id, Metric-Id-Partition and Label-String attributes.
+- OBX-4 shall indicate a new metric n-tuple value; a new metric instance.
+- OBX-6 is determined by the Unit-Code attribute and the Unit-LabelString attribute.
+- OBX-8 and OBX-11 are determined by the presence or lack of a Measurement-Status attribute OR a special numeric value like NaN:
+  - No Measurement-Status or special value, OBX-8 is empty and OBX-11 is R.
+- OBX-14 is determined by one of the timestamp attributes and if there is no timestamp attribute OBX-14 is filled in with the PHG's time of reception of the observation.
+
+- OBX-20 is obtained from the Supplemental-Types attribute if it has any entries with a partition value of MDC\_PART\_SITES; otherwise the entries in the Supplemental-Types attribute are placed in a facet OBX.
+- All the remaining fields are empty.
+- A facet OBX to the above OBX is generated by the presence of the Supplemental-Types, Source-Handle-Reference, Source-Handle-Reference-List, Relative-Time-Stamp, HiRes-Time-Stamp and Sample-Period attribute.
+- For some specializations additional attributes are defined that are not defined in [ISO/IEEE 11073-20601]. These attributes are also handled as facet OBX segments. The pulse oximeter specialization has also added two Measurement-Status bit settings not defined in [ISO/IEEE 11073-20601]. When these bits are set, they are represented as a facet OBX.
+- All other attributes in the Metric object (such as the Attribute Value Map) are not of interest to PCD-01 and are not translated.
+
+When the observation contains no compound attribute, a new metric instance OBX segment that may or may not require facet segments **shall** be encoded as follows:
+
+OBX|n|obx-2|obx-3|m.0.0.x|obx-5|obx-6||obx-8|||obx-11|||obx-14|||||obx-20
+
+where obx-2, obx-3, obx-5, obx-6, obx-8, obx-11, obx-14, and obx-20 are encoded as specified in the following subclauses.
+
+#### D.1.3.1.1 obx-3
+
+OBX-3 is always a CWE-encoded MDC code. The TYPE, Metric-Id, Metric-Id-Partition and Label-String Attributes are used to determine the value entered in the OBX-3 field. One or more of these attributes define what the observation *is*.
+
+- If the Metric-Id attribute is not present,
+  - OBX-3 **shall** be the TYPE attribute value, which contains both the nomenclature and partition code, encoded as a CWE data type. The TYPE attribute is required by [ISO/IEEE 11073-20601] and is always present.
+
+Example:
+
+OBX|n|NM|150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC|m.0.0.x|99|262688^MDC\_DIM\_PERCENT^MDC||||R||20090715070707-0500
+
+- If the Metric-Id attribute is present
+  - The Metric-Id value **shall** be encoded into a CWE data type using the Metric-Id-Partition attribute value for the partition if present or the partition value of the TYPE attribute value if the Metric-Id-Partition attribute is absent.
+  - OBX-3 **shall** either be the Metric-Id value encoded as a CWE data type using the proper partition *or*
+  - OBX-3 **shall** be the TYPE attribute value encoded as a CWE data type and
+  - a facet OBX segment to the METRIC-level OBX segment **shall** be created as follows:
+
+OBX|n|CWE|67883^MDC\_ATTR\_ID\_PHYSIO^MDC|m.0.0.x.y|obx-5|||||obx-11
+
+NOTE – The reason for placing the Metric-Id value into a facet OBX segment is that the original version of the cardiovascular specialization [IEEE 11073-10441] used the Metric-Id to supplement the TYPE attribute and not as a replacement for the TYPE attribute. For example, the Metric-Id would specify 'Average or maximum' but one would not know the average or maximum of what without the TYPE attribute value. Sensors were implemented using this standard and are operational in the field. Thus by placing the Metric-Id attribute value into a
+
+facet OBX segment and maintaining the TYPE attribute value in the METRIC-level OBX segment, the full context of the observation can be read. This shortcoming has been fixed in the new version of the cardiovascular standard.
+
+where
+
+- *obx-5* **shall** be the Metric-Id value encoded as a CWE data type using the proper partition in the computation.
+- *obx-11* **shall** have the same value as the parent OBX-11.
+
+Examples:
+
+Old version of cardiovascular fitness:
+
+Speed Object TYPE value MDC\_HF\_SPEED partition MDC\_PART\_HF,
+
+Metric-Id value indicates maximum value MDC\_HF\_MAX (same partition as TYPE).
+
+Metric-Id replaces TYPE:
+
+```
+OBX|n|NM|16779218^MDC_HF_MAX^MDC|m.0.0.x|504|268704^MDC_DIM_M_PER_MIN^MDC||||R||20090715070707-0500
+```
+
+Metric-Id as facet of METRIC-level OBX containing TYPE:
+
+```
+OBX|n|NM|16777326^MDC_HF_SPEED^MDC|m.0.0.x|404|268704^MDC_DIM_M_PER_MIN^MDC||||R||20090715070707-0500
+OBX|n+1|CWE|67883^MDC_ATTR_ID_PHYSIO^MDC|m.0.0.x.1|16779218^MDC_HF_MAX^MDC||||R
+```
+
+- If the Label-String attribute is present its value **may** be appended to the alternate-text component (CWE-5) of the CWE data type in OBX-3 of the METRIC-level OBX segment. Be sure to HL7-escape any separator characters in the string.
+
+Example:
+
+```
+OBX|n|NM|16779218^MDC_HF_MAX^MDC^^Runner's maximum speed during workout|m.0.0.x|404|268704^MDC_DIM_M_PER_MIN^MDC||||R||20090715070707-0500
+```
+
+or
+
+```
+OBX|n|NM|16777326^MDC_HF_SPEED^MDC^^Runner's maximum speed during workout|m.0.0.x|404|268704^MDC_DIM_M_PER_MIN^MDC||||R||20090715070707-0500
+OBX|n+1|CWE|67883^MDC_ATTR_ID_PHYSIO^MDC|m.0.0.x.1|16779218^MDC_HF_MAX^MDC||||R
+```
+
+#### D.1.3.1.2 obx-6
+
+If present, the Unit-Code attribute value **shall** be encoded as a CWE data type in OBX-6 of the primary OBX segment. The partition code of MDC\_PART\_DIM (4) is assumed; the attribute value has only the nomenclature code.
+
+Example:
+
+```
+OBX|n|NM|188736^MDC_MASS_BODY_ACTUAL^MDC|m.0.0.x|70.7|263875^MDC_DIM_KILO_G^MDC||||R||20120628145624.000-0500
+```
+
+If present, the Unit-LabelString attribute value **may** be appended to the CWE data type in the Alternate-Text component which is of data type ST. Be sure to HL7-escape any separator characters in the string.
+
+Example:
+
+```
+OBX|n|NM|152584^MDC_FLOW_AWAY_EXP_FORCED_PEAK^MDC|m.0.0.x|67.3|264992^MDC_DIM_L_PER_MIN^MDC^^Breathing rate in liters per minute||||R||20090715070707+0800
+```
+
+#### D.1.3.1.3 obx-2 and obx-5
+
+The observational metric attributes define the OBX-2 and OBX-5 fields of the METRIC-level OBX segment.
+
+#### D.1.3.1.3.1 Numeric observational attributes
+
+If the observational attribute is a Basic-Nu-Observed-Value, Simple-Nu-Observed-Value, or Nu-Observed-Value
+
+- OBX-2 **shall** be NM.
+- If the value is a not a special value  
+OBX-5 **shall** be the value of the attribute with precision as indicated by the exponent.
+- If the value is a special value
+  - OBX-5 **shall** be empty and OBX-8 and OBX-11 **shall** be encoded as in clause D.1.3.1.4.2 for handling the special values.
+- If the observational attribute is a Nu-Observed-Val, which contains an ASN.1-state, ASN.1-unit-code and ASN.1-metric-id structure in addition to the value,
+  - the Nu-Observed-Val attribute ASN.1 structs **shall** take precedence over the equivalent attributes (Metric-Id, Measurement-Status, Unit-Code) in the metric object.
+    - The ASN.1-metric-id value **shall** be handled as clause D.1.3.1.1.
+    - The ASN.1-state value **shall** be handled as in clause D.1.3.1.4.
+    - The ASN.1-unit-code value **shall** be handled as in clause D.1.3.1.2.
+
+#### D.1.3.1.3.2 Enumeration observational attributes
+
+There are four types of enumeration observational attributes.
+
+##### D.1.3.1.3.2.1 Enum-Observed-Value-Simple/Basic-Bit-Str attributes
+
+If the observational attribute is an Enum-Observed-Value-Simple-Bit-Str or Enum-Observed-Value-Basic-Bit-Str, ASN.1-BITS string encoding is used. All ASN.1 BITS16 and ASN.1 BITS32 are coded in this manner.
+
+- OBX-2 **shall** be CWE.
+- OBX-5 **shall** encode the ASN.1 BITS settings as a list of CWE data types where each entry is encoded as follows:
+  - CWE-1 **shall** be the bit setting (1 or 0).
+  - CWE-2 **shall** be the ASN.1 name if known concatenated by the bit position in parentheses. The bit position in parentheses **shall** be present whether or not the ASN.1 name is known.
+  - CWE-3 is empty.
+  - There **shall** be an entry for each bit that is set.
+  - There **may** be an entry if the bit is cleared.
+  - Each CWE entry **shall** be separated by the repetition symbol (~).
+
+Example:
+
+- a) 1^device-battery-low(0)
+- b) 1^(0)
+- c) 1^device-battery-low(0)~1^sensor-read-interrupt(9)
+- d) 1^(0)~1^(9)
+
+In cases a) and c) the name is known and in cases b) and c) it is not. Cases c) and d) represent more than one bit setting.
+
+#### D.1.3.1.3.2.2 Enum-Observed-Value-Simple-OID attribute
+
+If the observational attribute is an Enum-Observed-Value-Simple-OID, its value contains a 16-bit nomenclature code.
+
+- OBX-2 **shall** be CWE.
+- OBX-5 **shall** contain the nomenclature code into a CWE data type obtaining the partition as follows:
+  - If the Enum-Observed-Value-Partition attribute is present, the partition value from this attribute **shall** be used in the computation of the code in CWE-1.
+  - If the Enum-Observed-Value-Partition value is MDC\_PART\_SITES.
+    - The encoded value **shall** be still be placed in OBX-5. In versions prior to this version of the guidelines it was placed in OBX-20.
+  - If the Enum-Observed-Value-Partition attribute is absent, the partition value from the TYPE attribute **shall** be used in the computation of the code in CWE-1.
+
+#### D.1.3.1.3.2.3 Enum-Observed-Value-Simple-Str attribute
+
+If the observational attribute is an Enum-Observed-Value-Simple-Str
+
+- OBX-2 **shall** be ST.
+- OBX-5 **shall** be the string of the Enum-Observed-Value-Simple-Str attribute value. Be sure to HL7-escape any separator characters in the string.
+
+#### D.1.3.1.3.2.4 Enum-Observed-Value attribute
+
+If the observational attribute is an Enum-Observed-Value the translation depends upon the type of data contained in the attribute. This attribute contains either an OID type, BITS-16 type, or String. Which of these types are in the attribute is determined by the ASN.1-value ASN.1 CHOICE entry. The CHOICE has one of the currently defined values of 1, 2 or 16.
+
+- If the ASN.1-value CHOICE is 1 the value is an OID.
+  - OBX-2 **shall** be CWE.
+  - OBX-5 **shall** encode the nomenclature code from the ASN.1-value into a CWE data type.
+    - If the Enum-Observed-Value-Partition attribute is present, the partition value from this attribute **shall** be used in the computation of the code in CWE-1.
+    - If the Enum-Observed-Value-Partition value is MDC\_PART\_SITES.
+      - The encoded value **shall** be still be placed in OBX-5. In versions prior to this version of the guidelines it was placed in OBX-20.
+    - If the Enum-Observed-Value-Partition attribute is absent, the partition value from the TYPE attribute **shall** be used in the computation of the code in CWE-1.
+- If the ASN.1-value CHOICE is 2 the value is a string.  
+OBX-2 **shall** be ST.  
+OBX-5 **shall** be the string of the ASN.1-value value.
+
+- If the ASN.1-value CHOICE is 16 the value is an ASN.1-BITS16.
+
+OBX-2 **shall** be CWE.
+
+OBX-5 **shall** encode the ASN.1 BITS settings in the ASN.1-value as a CWE data type as shown in the Enum-Observed-Value-\*-Bit-Str attribute cases.
+
+- The Enum-Observed-Value attribute ASN.1 structs **shall** take precedence over the equivalent attributes (Metric-Id and Measurement-Status) in the metric object.
+  - The ASN.1-metric-id value **shall** be handled as clause D.1.3.1.1.
+  - The ASN.1-state value **shall** be handled as in clause D.1.3.1.4.
+
+#### D.1.3.1.3.3 Simple-Sa-Observed-Value attribute
+
+If the observational attribute is a Simple-Sa-Observed-Value from the RTSA metric object.
+
+- *obx-2* **shall** be NA.
+- *obx-5* **shall** be the repeated sequence of entries in the Simple-Sa-Observed-Value attribute value scaled back to their original values separated by the component symbol (^) and not the repetition symbol (to be consistent with the current PCD representation of waveforms).
+
+PCD is considering handling more complex notations, such as waveforms in multiple dimensions. In that case the time component of the RTSA may, in the future, be represented by the repetition symbol (~).
+
+#### D.1.3.1.4 obx-8 and obx-11
+
+Read clause D.1.3.1.7 for some background information.
+
+If there is no Measurement-Status attribute or special value
+
+- OBX-8 shall be empty.
+- OBX-11 shall be R.
+
+If there is a Measurement-Status attribute
+
+- An entry from Table D.8 in clause D.1.3.1.6.10.3 which maps each bit setting in the Measurement-Status attribute to the appropriate HL7 AbnormalFlags string **shall** be added to OBX-8 using the repetition symbol (~) as needed.
+- OBX-11 shall be encoded with the corresponding OBX-11 value as shown in Table D.8.
+  - If there is more than one measurement status entry and the entries map to different OBX-11 values, 'X' **shall** take precedence over 'R' which **shall** take precedence over 'F'.
+
+#### D.1.3.1.4.1 PulseOx and GCM Measurement-Status attribute bits 14 and 15 special case
+
+If the Measurement-Status attribute has bits 14 or 15 set, these are special to the pulse oximeter and continuous glucose monitor specialization and these two settings are NOT reported in OBX-8 but are reported in a separate facet OBX segment as follows:
+
+OBX|n|CWE|67911^MDC\_ATTR\_MSMT\_STAT^MDC|m.0.0.x.y|obx-5| | | | |obx-11
+
+where
+
+- *obx-5* **shall** be the bit 14 and/or bit 15 entry encoded as a CWE type separated by the repetition symbol (~).
+- *obx-11* **shall** be equal to OBX-11 of the parent.
+
+#### D.1.3.1.4.2 Numeric special values NaN, +INF, -INF, NRes, Reserved
+
+If there is a special value
+
+- An entry from Table D.9 which maps the special value to the appropriate HL7 Abnormal Flags string **shall** be added to OBX-8 using the repetition symbol (~) if needed.
+- OBX-11 shall be encoded with the corresponding OBX-11 value as shown in Table D.9
+  - OBX-5 **shall** be set to empty.  
+NOTE – OBX-5 needs to be set to empty as the [ISO/IEEE 11073-20601] SFLOAT and FLOAT encoded special values convert to valued numbers that will be misinterpreted.
+
+#### D.1.3.1.5 obx-14: Timestamps
+
+First a summary of PHG time requirements:
+
+- The PHG **shall** be able to synchronize to UTC time and **should** be local time aware and **shall** generate qualified timestamps in MSH-7, OBR-7, OBR-8 and OBX-14.
+  - If the PHG is not local time aware, it **shall** set the offset to -0000. The minus sign distinguishes it from a PHG that is local time aware but happens to be in a GMT time zone which, in that case, would use 0000 for the offset.
+- If the PHG loses UTC time knowledge for some reason (no network connection and synchronization accuracy has decreased below some threshold), the PHG **may** fallback to using unqualified timestamps as indicated in clause D.1.5 should it be deemed necessary to still create a PCD-01 document. The fallback allows a PHG to generate a PCD-01 document that does not satisfy all the PCD timestamp requirements. The unqualified timestamp in MSH-7 indicates to the reader that the PHG has lost synchronization to UTC time. A PHG may still be able to report a qualified timestamp in OBR-7, OBR-8 and OBX-14 if the sensor happens to be synchronized to UTC and the PHG is aware of it.
+- The PHG **shall** determine whether the sensor or the PHG is better synchronized to UTC.
+  - It uses the sensor's Mds-Time-Info attribute to make this determination.
+    - The ASN.1-mds-time-caps-state indicates if the sensor is synchronized and to what.
+    - The ASN.1-time-sync-accuracy indicates the accuracy of the synchronization.
+    - The ASN.1-time-sync-protocol indicates the method the sensor uses to synchronize.
+  - If the synchronization method, state of synchronization and synchronization accuracy indicate that the sensor is better synchronized to UTC than the PHG is, the PHG **shall** use the sensor's qualified timestamp without modification. This situation is case 2 in the timestamping and time synchronization clause D.1.5.
+  - If the PHG determines that it has better synchronization it **shall** correct the sensor's timestamps. This situation is case 1 in the timestamping and time synchronization clause and it is what was done in all cases in versions prior to these design guidelines
+- If the sensor provides no timestamp in the observation the PHG **shall** use the time of reception of the observation in OBX-14 regardless of whether case 1 or case 2 applies for time-stamped observations.
+- The reader of the PCD-01 document determines the case from the existence or absence of the coincident timestamp pair MDS-OBX and Mds-Time-Caps MDS-OBX as indicated in Table D.6.
+
+**Table D.6 – Timestamp cases**
+
+| Time usage                   | Coincident timestamp pair OBX | Mds-Time-Caps OBX |
+|------------------------------|-------------------------------|-------------------|
+| PHG corrects sensor time     | YES                           | YES               |
+| Sensor time used uncorrected | NO                            | YES               |
+| PHG uses time of reception   | NO                            | NO                |
+
+OBX-14 guidelines:
+
+- If the sensor provides no timestamp, case 3 of clause D.1.5 applies
+  - OBX-14 **shall** be the time the PHG received the observation as a DTM data type.
+- If the sensor provides a timestamp and it is an absolute or base offset time, case 1 or 2 of clause D.1.5 applies.
+  - OBX-14 **shall** contain either the corrected Sensor timestamp (case 1) or uncorrected Sensor timestamp (case 2) as a DTM data type.
+- If the sensor provides any type of relative timestamp,
+  - OBX-14 **shall** contain the PHG's conversion of this timestamp to a DTM timestamp using the coincident timestamp pair for the respective relative time (see clause 10.4).
+  - The relative time value itself **shall** be provided in its own facet OBX segment as indicated in clause D.1.3.1.6.
+
+#### D.1.3.1.5.1 obx-20
+
+This field is only encoded if there is a Supplemental-Types attribute and if any of the values in the attribute (which is a list of ASN.1 TYPE structs) have an MDC\_PART\_SITES partition. These entries with the MDC\_PART\_SITES partition value **shall** be encoded as a CWE data-type in OBX-20, separated by a repetition symbol (~) if needed. All other entries are encoded into a facet OBX segment as indicated in clause D.1.3.1.6.
+
+#### D.1.3.1.6 Facet OBX segments
+
+The remaining attributes in the Metric Object are all encoded as separate OBX segments which are facets of the METRIC-level OBX segment. If present, these attributes **shall** be handled as indicated in this clause.
+
+##### D.1.3.1.6.1 Supplemental types
+
+This attribute contains a list of partition:nomenclature values.
+
+- If the partition is *not* MDC\_PART\_SITES the attribute shall be encoded as follows:
+
+OBX|n|CWE|68193^MDC\_ATTR\_SUPPLEMENTAL\_TYPES^MDC|m.0.0.x.y|obx-5| | | | |obx-11  
+where
+
+- *obx-5* **shall** be the Supplemental-Types values whose partition is not MDC\_PART\_SITES as a CWE type separated by the repetition symbol (~).
+  - *obx-11* **shall** be equal to OBX-11 of the parent.
+- If the partition is MDC\_PART\_SITES see clause D.1.3.1.5.1.
+
+##### D.1.3.1.6.2 Source handle reference
+
+This attribute contains an ISO/IEEE 11073-20601 handle pointing to another ISO/IEEE 11073-20601 metric object in the Sensor DIM. In PCD-01 handles are a meaningless concept. Thus the
+
+handle value is replaced with the OBX-4 value of the OBX METRIC-level segment that represents the observation being pointed to. Encoding this attribute is optional. If encoded, the attribute **shall** be encoded as follows:
+
+OBX|n|ST|68167^MDC\_ATTR\_SOURCE\_HANDLE\_REF^MDC|m.0.0.x.y|obx-5| | | | |obx-11
+
+where
+
+- *obx-5* **shall** be the OBX-4 entry of the METRIC-level OBX segment this attribute value points to.
+- *obx-11* **shall** be equal to OBX-11 of the parent.
+
+Example: Source handle reference for body mass index in OBX|k+2| points to OBX|k| which contains the weight observation since OBX-5 of OBX|k+2| contains the OBX-4 value of OBX|k|:
+
+- The PHG OBXes
+
+OBX|n||528391^MDC\_DEV\_SPEC\_PROFILE\_SCALE^MDC|1| | | | |X| | | | |0123456789ABCDEF^0123456789ABCDEF^EUI-64
+
+- More MDS OBXes
+
+OBX|k|NM|188736^MDC\_MASS\_BODY\_ACTUAL^MDC|1.0.0.x|80|263875^MDC\_DIM\_KILO\_G^MDC| | | |R  
+ OBX|k+1|NM|188752^MDC\_RATIO\_MASS\_BODY\_LEN\_SQ^MDC|1.0.0.x+1|24.7|264096^MDC\_DIM\_KG\_PER\_M\_SQ^MDC  
+ | | | |R  
+ OBX|k+2|ST|68167^MDC\_ATTR\_SOURCE\_HANDLE\_REF^MDC|1.0.0.x+1.1|1.0.0.x| | | |R
+
+#### D.1.3.1.6.3 Source handle reference list
+
+Same as Source-Handle-Reference except it contains a list of ISO/IEEE 11073-20601 handles. Encoding this attribute is optional. If encoded the attribute **shall** be encoded as follows:
+
+OBX|n|ST|sssss^MDC\_ATTR\_SOURCE\_HANDLE\_REF\_LIST^MDC|m.0.0.x.y|obx-5| | | | |obx-11
+
+where
+
+- *obx-5* **shall** be the OBX-4 entries of the METRIC-level OBX segments this attribute value points to separated by the repetition symbol (~).
+- *obx-11* **shall** be equal to OBX-11 of the parent.
+
+#### D.1.3.1.6.4 Measurement active period
+
+This attribute contains the time over which the observation was taken in the units of seconds. If the value is valid, the attribute **shall** be encoded. If it is a special value, the attribute **should** be encoded. If the attribute is encoded it **shall** be encoded as follows:
+
+OBX|n|NM|68185^MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE^MDC|m.0.0.x.y|obx-5|obx-6| | | |obx-11
+
+where
+
+- *obx-5* **shall** be the value of the attribute as seconds or scaled to microseconds.
+- *obx-6* **shall** be 264320^MDC\_DIM\_SEC^MDC if OBX-5 is in seconds or 264339^MDC\_DIM\_MICRO\_SEC^MDC if OBX-5 is scaled to microseconds. [ISO/IEEE 11073-20601] transmits this attribute in seconds.
+- *obx-11* **shall** be equal to OBX-11 of the parent.
+
+#### D.1.3.1.6.5 Accuracy
+
+Attribute defines the maximum deviation of the actual observation from the sent observation. The deviation is in the units of the observation. The accuracy is an absolute value. The attribute **shall** be encoded as follows:
+
+OBX|n|NM|67914^MDC\_ATTR\_NU\_ACCUR\_MSMT^MDC|m.0.0.x.y|obx-5|obx-6|||||obx-11
+
+where
+
+- *obx-5* **shall** be the value of the attribute.
+- *obx-6* **shall** be the value of the Unit-Code attribute as a CWE data type. It **shall** match OBX-6 of the parent OBX.
+- *obx-11* **shall** be equal to OBX-11 of the parent.
+
+#### D.1.3.1.6.6 Relative timestamp
+
+This attribute gives the relative time in units of 1/8 ms. The attribute **shall** be encoded as follows:
+
+OBX|n|NM|67985^MDC\_ATTR\_TIME\_STAMP\_REL^MDC|m.0.0.x.y|obx-5|264339^MDC\_DIM\_MICRO\_SEC^MDC|||||obx-11||||||obx-18
+
+where
+
+- *obx-5* shall be the 32-bit integer value of the time reported in the attribute converted from its units of 1/8 milliseconds to microseconds.
+- *obx-11* shall be equal to OBX-11 of the parent.
+- *obx-18* may include an identifier for the timebase used by the sensor for the relative time clock as an EI data type if known (see Note in clause D.1.2.6).
+
+#### D.1.3.1.6.7 Hi Res relative timestamp
+
+This attribute gives the relative time in units of microseconds. The attribute **shall** be encoded as follows:
+
+OBX|n|NM|68073^MDC\_ATTR\_TIME\_STAMP\_REL\_HI\_RES^MDC|m.0.0.x.y|obx-5|264339^MDC\_DIM\_MICRO\_SEC^MDC|||||obx-11||||||obx-18
+
+where
+
+- *obx-5* shall be the 64-bit integer value of the time reported in the attribute.
+- *obx-11* shall be equal to OBX-11 of the parent.
+- *obx-18* may include an identifier for the timebase used by the sensor for the relative time clock as an EI data type if known (see note in clause D.1.2.6).
+
+#### D.1.3.1.6.8 Sample-Period
+
+This attribute gives the time in 1/8 milliseconds between the samples in an RTSA observation. The attribute **shall** be encoded as follows:
+
+OBX|n|NM|67981^MDC\_ATTR\_TIME\_PD\_SAMP^MDC|m.0.0.x.y|obx-5|264339^MDC\_DIM\_MICRO\_SEC^MDC|||||obx-11
+
+where:
+
+- *obx-5* shall be the 32-bit integer value of the time reported in the attribute scaled from 1/8 milliseconds to microseconds.
+- *obx-11* **shall** be equal to OBX-11 of the parent.
+
+#### D.1.3.1.6.9 SaFlags in Sa-Specification attribute
+
+The ASN.1-flags struct of the Sa-Specification attribute contains information about the waveform which could be useful for displaying the waveform. This structure **may** be sent by applications. If sent, it **shall** be encoded as a facet OBX as follows:
+
+OBX|n|CWE|531980^MDC\_SA\_SPECN\_FLAGS^MDC OBX|m.0.0.x.y|obx-5| | | | |obx-11
+
+where
+
+- *obx-5* **shall** be encoded as an ASN.1-BITS field from one of the currently defined settings
+  - smooth-curve(0)
+  - delayed-curve(1)
+  - static-scale(2)
+  - sa-ext-val-range(3)
+- *obx-11* **shall** be equal to OBX-11 of the parent.
+
+#### D.1.3.1.6.10 Specialization specific metric attributes
+
+The specialization-specific metric attributes are also encoded as facets.
+
+##### D.1.3.1.6.10.1 Pulse Oximeter
+
+- Alert-Op-State: Indicates whether the thresholds defined in the current limits are off. Note that a set bit means the alarm state is off. The segment **shall** be encoded as
+
+OBX|n|CWE|67846^MDC\_ATTR\_AL\_OP\_STAT^MDC|m.0.0.x.y|obx-5| | | | |obx-11
+
+where
+
+- *obx-5* **shall** be encoded as an Enum-Observed-Value-Basic-Bit-Str attribute value.
+- *obx-11* **shall** be equal to OBX-11 of the parent.
+
+Example:
+
+OBX|n|CWE|67892^MDC\_ATTR\_AL\_OP\_STAT^MDC|m.0.0.x.y|0^limit-alert-off(0)~1^limit-low-off(1)| | | | |R
+
+- Current-Limits: Has the lower followed by upper threshold limits for the said observation. The segment **shall** be encoded as
+
+OBX|n|NM|67892^MDC\_ATTR\_LIMIT\_CURR^MDC|m.0.0.x.y|obx-5|obx-6| | | | |obx-11
+
+where
+
+- *obx-5* **shall** be the two values (lower limit then upper limit) of the attribute separated by the repetition symbol (~).
+- *obx-6* **shall** be the Unit-Code attribute value.
+- *obx-11* **shall** be equal to OBX-11 of the parent.
+
+Example where thresholds are 30.3 beats per minute at the low end and 130.7 at the high end:
+
+OBX|n|NM|67892^MDC\_ATTR\_LIMIT\_CURR^MDC|m.0.0.x.y|30.3~130.7|264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC|| | |R
+
+- Alert-Op-Text-String: Has strings representing the lower followed by upper threshold limits. The segment **shall** be encoded as
+
+OBX|n|ST|68104^MDC\_ATTR\_AL\_OP\_TEXT\_STRING^MDC|m.0.0.x.y|obx-5| | | | |obx-11
+
+where
+
+- **obx-5 shall** be encoded as tuple of two strings (lower limit then upper limit) separated by the repetition symbol (~).
+- **obx-11 shall** be equal to OBX-11 of the parent.
+
+Example:
+
+OBX|n|ST|68104^MDC\_ATTR\_AL\_OP\_TEXT\_STRING^MDC|m.0.0.x.y|lower pulse~upper pulse|||||R
+
+#### D.1.3.1.6.10.2 Adherence medication monitor (AMM)
+
+Context-Key: EI data type giving an EUI-64 context identifier that by itself means nothing but it can be used to identify context for the given medication monitor, for example to determine what the medication actually is and what the feedback questions and answers actually are:
+
+OBX|n|EI|68216^MDC\_ATTR\_CONTEXT\_KEY^MDC|m.0.0.x.y|obx-5|||||R
+
+where
+
+- **obx-5 shall** be encoded as an EI data type where
+  - EI-1 is an entity identifier which may be the same as EI-3.
+  - EI-3 is the attribute value as a 16-digit HEX string (without the 0x prefix).
+  - EI-4 is EUI-64.
+
+Example:
+
+OBX|n|EI|68216^MDC\_ATTR\_CONTEXT\_KEY^MDC|m.0.0.x.y|AMM-Continua\_5555^00925555FD33AB10^EUI-64|||||R
+
+#### D.1.3.1.6.10.3 Continuous glucose monitor
+
+- Threshold-Notification-Text-String: Has a string related to the current threshold notification. The segment **shall** be encoded as
+
+OBX|n|ST|68104^MDC\_THRES\_NOTIF\_TEXT\_STRING^MDC|m.0.0.x.y|obx-5|||||obx-11
+
+where
+
+- **obx-5 shall** encoded as a string. Be sure HL7-escape any separator characters in the string.
+- **obx-11 shall** be equal to OBX-11 of the parent.
+
+Example:
+
+OBX|n|ST|526984^MDC\_ATTR\_THRES\_NOTIF\_TEXT\_STRING^MDC|m.0.0.x.y|patient low threshold|||||R
+
+- Measurement-Confidence-95: Has the lower bound followed by upper bound within which the manufacture is 95% confident that the actual value for the said observation is within. The segment **shall** be encoded as
+
+OBX|n|NM|526988^MDC\_ATTR\_MSMT\_CONFIDENCE\_95^MDC|m.0.0.x.y|obx-5|obx-6|||||obx-11
+
+where
+
+- **obx-5 shall** be the two values (lower bound then upper bound) of the attribute separated by the repetition symbol (~)
+
+- **obx-6** shall be the Unit-Code attribute value.
+- **obx-11** shall be equal to OBX-11 of the parent.
+
+Example:
+
+```
+OBX|n|NM|526988^MDC_ATTR_MSMT_CONFIDENCE_95^MDC|m.0.0.x.y|6.5~7.8|266866^
+MDC_DIM_MILLI_MOLE_PER_L^MDC||||R
+```
+
+#### D.1.3.1.7 Measurement status and special values (NaN, etc.)
+
+[ISO/IEEE 11073-20601] can report the observation status in the Measurement-Status attribute as one or more of the following BITS values:
+
+```
+MeasurementStatus ::= BITS-16 {
+    invalid(0),
+    questionable(1),
+    not-available(2),
+    calibration-ongoing(3),
+    test-data(4),
+    demo-data(5),
+    validated-data(8),      -- relevant, e.g., in an archive
+    early-indication(9),    -- early estimate of value
+    msmt-ongoing(10) -- indicates a new observation is just being taken
+(episodic)
+}
+```
+
+The pulse oximeter and the continuous glucose monitor specializations define two additional bit settings:
+
+- msmt-state-in-alarm(14) – indicates that the observation is outside threshold boundaries.
+- msmt-state-al-inhibited(15) – indicates that the threshold indication is disabled.
+
+The HL7 v2.6 OBX also contains the observation status concept, but allows only 1 value per OBX from the following set of possible values shown in Table D.7.
+
+**Table D.7 – OBX-8 status values**
+
+| Value | Description                                                                              | Comment |
+|-------|------------------------------------------------------------------------------------------|---------|
+| O     | Order received; specimen not yet received                                                |         |
+| I     | No results available; specimen received, procedure incomplete                            |         |
+| S     | No results available; procedure scheduled, but not done                                  |         |
+| A     | Some, but not all, results available                                                     |         |
+| P     | Preliminary: A verified early result is available, final results not yet obtained        |         |
+| C     | Correction to results                                                                    |         |
+| R     | Results stored; not yet verified                                                         |         |
+| F     | Final results; results stored and verified. Can only be changed with a corrected result. |         |
+| X     | No results available; order cancelled.                                                   |         |
+
+Table D.7 indicates that HL7 V2 does not have standard code values for expressing all the possible reasons a sensor can declare data as either 'invalid' or 'questionable', so there is a potential loss in semantic fidelity. However, HL7 v2.6 does provide an 'Abnormal Flags' field in OBX-8 that may be used to provide zero or more codes (of the IS data type) to augment the interpretation of the observation. For use on the Continua Services interface, services Observation Upload devices use
+
+the 'Abnormal Flags' option whose values are shown in Table D.8 to report a standard Measurement Status value in OBX-8.
+
+The OBX-8 settings also affect the OBX-11 'summary status' field as indicated in Table D.8. If more than one measurement status bit is set, the additional settings are included using the repetition symbol (~).
+
+**Table D.8 – Measurement status values**
+
+| <b>MeasurementStatus ::= BITS-16 { ... }</b>                                                            | <b>OBX-8</b> | <b>OBX-11</b> |
+|---------------------------------------------------------------------------------------------------------|--------------|---------------|
+| No bits set $\Rightarrow$ raw device observation; observation okay, has not been reviewed nor validated |              | R             |
+| invalid(0)                                                                                              | INV          | X             |
+| questionable(1)                                                                                         | QUES         | R             |
+| not-available(2)                                                                                        | NAV          | X             |
+| calibration-ongoing(3)                                                                                  | CAL          | R             |
+| test-data(4)                                                                                            | TEST         | R             |
+| demo-data(5)                                                                                            | DEMO         | R             |
+| validated-data(8) -- relevant, e.g., in an archive                                                      |              | F             |
+| early-indication(9) -- early estimate of value                                                          | EARLY        | R             |
+| msmt-ongoing(10) -- indicates that a new observation is just being taken (episodic)                     | BUSY         | X             |
+| msmt-state-in-alarm(14) -- indicates that the metric has an active alarm condition                      | ALACT        | R             |
+| msmt-state-al-inhibited(15) -- metric supports alarming, and alarms are turned off (optional)           | ALINH        | R             |
+
+Observations with a measurement status of validated-data **shall** use the final results code (F).
+
+When the value of OBX-11 is set to 'X', as in the case of invalid, not-available or ongoing observations, it indicates that results **should not** be obtained from the observation. Non-device observations (e.g., physiological METRICS and FACETS) with an OBX-11 status code of 'X' **shall** set the value in OBX-5 to empty for NM data types. Previous versions of the standard stated that the value should be set to INV for all data types but that entry is not legal for the NM and NA data types and has caused problems in the field.
+
+Also note that certain device specializations have extended this list of possible values. For these extended values, the Measurement-Status value **shall** be encoded in a FACET of the METRIC of question.
+
+#### **D.1.3.1.8 Special values (NaN, etc.)**
+
+If a numeric value reports one of the [ISO/IEEE 11073-20601] special values (NaN, **NRes**, **+INFINITY**, **-INFINITY**, or Reserved) the case is also reported as an Abnormal Flags entry in OBX-8. This entry is appended to the Measurement-Status entries if present using the repetition symbol (~). [IHE-PCD-01] provides the codes based upon null flavors to handle invalid or missing data types. The values shown in Table D.9 are those appropriate for the special values.
+
+**Table D.9 – Special data types**
+
+| Missing, special or invalid data type   | OBX-8 | OBX-11 |
+|-----------------------------------------|-------|--------|
+| Value not in domain (Nres and Reserved) | OTH   | X      |
+| Not a number                            | NAN   | X      |
+| Positive infinity                       | PINF  | X      |
+| Negative infinity                       | NINF  | X      |
+
+When a special value is received there is no valid NM data type to represent the condition thus OBX-5 is set to empty.
+
+### D.1.3.2 Case 2: Measurement contains a compound attribute
+
+An observation containing a compound entry, which is always a numeric, is coded almost identically to an observation without a compound entry. The main difference is that the hierarchy is moved up one to the channel-level. Attributes that were previously coded as facets now appear at the metric level.
+
+In a non-compound observation the type of the observation is given by the TYPE attribute or Metric-Id attribute. The partition for the Metric-Id attribute comes from the TYPE attribute unless there is a Metric-Id-Partition attribute.
+
+In a compound attribute there are multiple elements. The overall observation type is given by the TYPE attribute, but the type of each compound element of the observation is given by the entries in the Metric-Id-List attribute in a one-to-one map. The partition for all entries in the Metric-Id-List attribute comes from the TYPE attribute unless there is a Metric-Id-Partition attribute. There is no means in [ISO/IEEE 11073-20601] to map a different partition to each nomenclature code in the Metric-Id-List.
+
+The channel-level OBX is generated from the TYPE attribute, Label-String attribute and the chosen timestamp attribute. Each element of the compound attribute value is specified in its own OBX segment which is a child of the channel-level OBX. Any attribute that generated a facet OBX segment in the non-compound case also appears as a child OBX of the channel-level OBX. Thus, it appears at the same level as the compound-element OBX segments.
+
+#### D.1.3.2.1 Channel-Level OBX
+
+Every observation containing a compound attribute **shall** have a channel-level OBX segment as follows:
+
+OBX|n||obx-3|m.0.c|||||X||obx-14
+
+where
+
+- *obx-3* **shall** be the TYPE attribute value encoded as a CWE data type.
+  - If the Label-String attribute is present it **shall** be entered in CWE-5 of OBX-3.
+- *obx-14* **shall** be coded as described for OBX-14 in clause D.1.3.1.5 in the non-compound case.
+
+Note that the value of X in OBX-11 even though the timestamp and the OBX-3 key value are important components of the overall observation and are needed to completely describe the observation. The reason for the 'X' value is that there is no OBX-5 field.
+
+Example (Blood pressure):
+
+OBX|n||150020^MDC\_PRESS\_BLD\_NONINV^MDC|m.0.c|||||X||20100108091005-0800
+
+with a Label-String attribute:
+
+OBX|n||150020^MDC\_PRESS\_BLD\_NONINV^MDC^^Self-taken  
+measurement|m.0.c|||||X||20100108091005-0800
+
+Example (AMM Feedback):
+
+OBX|n||8532995^MDC\_AI\_MED\_FEEDBACK^MDC|m.0.c|||||X||20101116091005-0500
+
+#### D.1.3.2.2 Simple/Basic compound values OBX segments
+
+The individual element values of the Compound-Simple-Nu-Observed-Value and Compound-Basic-Nu-Observed-Value attributes **shall** be encoded as a child of the channel-level OBX as follows:
+
+OBX|n|NM|obx-3|m.0.c.x|obx-5|obx-6||obx-8|||obx-11
+
+Note that there is no timestamp entry in these segments.
+
+The *obx-3*, *obx-5*, *obx-6*, *obx-8* and *obx-11* fields shall be encoded according to the following subclauses.
+
+##### D.1.3.2.2.1 obx-3 and obx-5
+
+The Metric-Id-List and Metric-Id-Partition determine *obx-3* and Compound attribute determine *obx-5*.
+
+The *obx-3* entry **shall** be encoded as a CWE data type as follows:
+
+- CWE-1 is computed from the nomenclature code obtained from the Metric-Id-List attribute value in a one-to-one map with the entries in the compound attribute where the partition code is obtained from
+  - the Metric-Id-Partition attribute value if present or
+  - the TYPE attribute value if the Metric-Id-Partition attribute is not present.
+- CWE-2 is the corresponding reference-Id.
+- CWE-3 is MDC.
+
+The *obx-5* entry **shall** be taken from the corresponding entry in the compound attribute value in a one to one map with the Metric-Id-List attribute. If one of the compound entries is a special value *obx-5* **shall** be empty in that OBX segment and the *obx-8* and *obx-11* fields of that OBX segment **shall** be encoded as shown in clause D.1.3.1.4.2 for special values.
+
+Table D.10 contains an example of blood pressure measurement that corresponds to the following encoding:
+
+OBX|n|NM|150021^MDC\_PRESS\_BLD\_NONINV\_SYS^MDC|m.0.c.x|120|266016^MDC\_DIM\_MMHG^MDC||||R  
+OBX|n+1|NM|150022^MDC\_PRESS\_BLD\_NONINV\_DIA^MDC|m.0.c.y|80|266016^MDC\_DIM\_MMHG^MDC||||R  
+OBX|n+2|NM|150023^MDC\_PRESS\_BLD\_NONINV\_MEAN^MDC|m.0.c.z||266016^MDC\_DIM\_MMHG^MDC||NAN||X
+
+Table D.11 contains an example of AMM feedback measurement that corresponds to the following encoding:
+
+OBX|n|NM|8532996^MDC\_AI\_MED\_UF\_LOCATION^MDC|m.0.c.x|3|||||R  
+OBX|n+1|NM|8532997^MDC\_AI\_MED\_UF\_RESPONSE^MDC|m.0.c.y|75|||||R
+
+**Table D.10 – Example blood pressure**
+
+| Entry # | Metric-Id-List entry value           | Compound attribute entry value |
+|---------|--------------------------------------|--------------------------------|
+| 1       | 150021^MDC_PRESS_BLD_NONINV_SYS^MDC  | 120                            |
+| 2       | 150022^MDC_PRESS_BLD_NONINV_DIA^MDC  | 80                             |
+| 3       | 150023^MDC_PRESS_BLD_NONINV_MEAN^MDC | NaN                            |
+
+**Table D.11 – Example AMM feedback**
+
+| Entry # | Metric-Id-List entry value         | Compound attribute entry value |
+|---------|------------------------------------|--------------------------------|
+| 1       | 8532996^MDC_AI_MED_UF_LOCATION^MDC | 3                              |
+| 2       | 8532997^MDC_AI_MED_UF_RESPONSE^MDC | 75                             |
+
+#### D.1.3.2.2.2 obx-6
+
+If the Unit-Code attribute is present
+
+- *obx-6* **shall** be taken from the Unit-Code attribute value and coded as a CWE data type and placed in each OBX segment representing one of the compound observation parts.
+- If the Unit-LabelString attribute is present its value **may** be placed in CWE-5 of the *obx-6* field in each case.
+- Otherwise *obx-6* **shall** be empty.
+
+Example:
+
+```
+OBX|n|NM|150021^MDC_PRESS_BLD_NONINV_SYS^MDC|m.0.c.x|120|266016^MDC_DIM_MMHG^MDC||||R
+OBX|n+1|NM|150022^MDC_PRESS_BLD_NONINV_DIA^MDC|m.0.c.y|80|266016^MDC_DIM_MMHG^MDC||||R
+OBX|n+2|NM|150023^MDC_PRESS_BLD_NONINV_MEAN^MDC|m.0.c.z|100|266016^MDC_DIM_MMHG^MDC||||R
+```
+
+Example with Unit-LabelString:
+
+```
+OBX|n|NM|150021^MDC_PRESS_BLD_NONINV_SYS^MDC|m.0.c.x|120|266016^MDC_DIM_MMHG^MDC^^mm
+Mercury||||R
+OBX|n+1|NM|150022^MDC_PRESS_BLD_NONINV_DIA^MDC|m.0.c.y|80|266016^MDC_DIM_MMHG^MDC^^mm
+Mercury||||R
+OBX|n+2|NM|150023^MDC_PRESS_BLD_NONINV_MEAN^MDC|m.0.c.z|100|266016^MDC_DIM_MMHG^MDC^^mm
+Mercury||||R
+```
+
+Note that *obx-6* is the same in all three segments.
+
+#### D.1.3.2.2.3 obx-8 and obx-11
+
+The Measurement-Status attribute values affect all elements of the compound. The encoding is identical to that of the non-compound case except the results are applied to all OBX segments representing the compound elements.
+
+Example where a measurement status of 'measurement ongoing' is received:
+
+```
+OBX|n||8456149^MDC_HF_PIM^MDC^^Proportional Integral Mode
+vector|m.0.c|||||X||20131108091005-0500
+OBX|n+1|NM|8456150^MDC_HF_PIM_X^MDC|m.0.c.1|12.4|268768^MDC_DIM_CENTI_M_PER_SEC_SQ^MDC||BUSY||
+|X
+OBX|n+2|NM|8456151^MDC_HF_PIM_Y^MDC|m.0.c.2|8800.0|268768^MDC_DIM_CENTI_M_PER_SEC_SQ^MDC||BUSY
+|||X
+OBX|n+3|NM|8456152^MDC_HF_PIM_Z^MDC|m.0.c.3|9.5|268768^MDC_DIM_CENTI_M_PER_SEC_SQ^MDC||BUSY|||
+X
+```
+
+Example where a measurement status of 'measurement ongoing' is received and a NaN is received in one of the compound elements:
+
+```
+OBX|n||8456149^MDC_HF_PIM^MDC^^Proportional Integral Mode
+vector|m.0.c|||||X||20131108091005-0500
+```
+
+```
+
+OBX|n+1|NM|8456150^MDC_HF_PIM_X^MDC|m.0.c.1|12.4|268768^MDC_DIM_CENTI_M_PER_SEC_SQ^MDC||BUSY||
+|X
+OBX|n+2|NM|8456151^MDC_HF_PIM_Y^MDC|m.0.c.2|8800.0|268768^MDC_DIM_CENTI_M_PER_SEC_SQ^MDC||BUSY||
+||X
+OBX|n+3|NM|8456152^MDC_HF_PIM_Z^MDC|m.0.c.3||268768^MDC_DIM_CENTI_M_PER_SEC_SQ^MDC||NAN~BUSY||
+|X
+
+```
+
+### D.1.3.2.3 Compound-Nu-Observed-Value attribute
+
+If the observation contains a Compound-Nu-Observed-Value attribute the Unit-Code, Metric-Id-List, Measurement-Status and Unit-Label-String attributes of the metric object are ignored. These attributes **shall**, instead, be obtained from their equivalents within the ASN.1-Nu-Observed-Value structure *for each entry*. The ASN.1-metric-id struct in each ASN.1-Nu-Observed-Value struct replaces the entries that would have been present in the Metric-Id-List attribute.
+
+Recall that the use of this compound attribute in [ISO/IEEE 11073-20601] indicates that these entries, each with a different possible unit and type, *are not independent observations but part of a single observation*. A possible example to illustrate this concept would be a sensor that measures the 3-d acceleration using different units for the x, y and z components, perhaps because the units are orders of magnitude different in the different directions. The Compound-Nu-Observed-Value attribute would contain three Nu-Observed-Value structs, where the ASN.1-metric-id entry would indicate the component (x, y, or z) and the ASN.1-unit-code entry the units. The resultant set of OBX segments might appear as follows:
+
+```
+
+OBX|n||8456149^MDC_HF_PIM^MDC^^Proportional Integral Mode
+vector|m.0.c|||||X||20131108091005-0500
+OBX|n+1|NM|8456150^MDC_HF_PIM_X^MDC|m.0.c.1|12.4|268768^MDC_DIM_CENTI_M_PER_SEC_SQ^MDC||||R
+OBX|n+2|NM|8456151^MDC_HF_PIM_Y^MDC|m.0.c.2|88.0|268751^MDC_DIM_M_PER_SEC_SQ^MDC||||R
+OBX|n+3|NM|8456152^MDC_HF_PIM_Z^MDC|m.0.c.3|10.0|268768^MDC_DIM_CENTI_M_PER_SEC_SQ^MDC||||R
+
+```
+
+### D.1.3.2.4 'Facet' OBX segments
+
+The Supplemental types, Source-Handle-Reference, Source-Handle-Reference-List, Accuracy, and Measurement-Active-Period attributes are encoded exactly as in the non-compound case except the hierarchy is moved up one level so that they are children of the channel-level OBX segment AND the OBX-11 value is set to R; it does NOT inherit the OBX-11 value of the parent. These segments are now at the metric-level instead of the facet level.
+
+Example where a Supplemental types attribute indicating a SPOT observation is present:
+
+```
+
+OBX|n||8456149^MDC_HF_PIM^MDC^^Proportional Integral Mode
+vector|m.0.c|||||X||20131108091005-0500
+OBX|n+1|NM|8456150^MDC_HF_PIM_X^MDC|m.0.c.1|12.4|268768^MDC_DIM_CENTI_M_PER_SEC_SQ^MDC||||R
+OBX|n+2|NM|8456151^MDC_HF_PIM_Y^MDC|m.0.c.2|8800.0|268768^MDC_DIM_CENTI_M_PER_SEC_SQ^MDC||||R
+OBX|n+3|NM|8456152^MDC_HF_PIM_Z^MDC|m.0.c.3|10.0|268768^MDC_DIM_CENTI_M_PER_SEC_SQ^MDC||||R
+OBX|n+4|CWE|68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC|m.0.c.4|150588^MDC_MODALITY_SPOT^MDC||||R
+
+```
+
+## D.1.4 Special situations
+
+### D.1.4.1 Time discontinuities: Date-Time-Adjustments
+
+[IHE PCD-01] requires that the timeline remain unbroken. If there is a discontinuity in the timeline, a new OBR segment is required. With [ISO/IEEE 11073-20601] sensors this situation is indicated by the presence of a Date-Time-Adjustment attribute. A PHG can receive this attribute in scan-event reports or it may be in the list of attributes describing a PM segment. In either case, the PHG is required to create a new OBR segment for the observation data affected by the Date-Time-Adjustment attribute. When creating a new OBR segment a new set of MDS-OBXes is required. If only the required attributes of the MDS are recorded, a new GET request is not needed since all the attribute values are static except for the coincident timestamps. If the date-time-adjustment occurs in agent-init scan event reports (live data), all the PHG needs to do is update the coincident time
+
+stamp OBX by adding to OBX-5 the date-time-adjustment value. For example, if the date-time-adjustment value is 50 minutes, the clock now being used by the sensor is 50 minutes ahead of what it was. OBX-5 in the updated coincident timestamp OBX can be generated by adding 50 minutes to the OBX-5 value in the original coincident timestamp OBX.
+
+If, however, the date-time-adjustment is in a PM segment attribute, the sensor's clock is *already* on the new timeline and the existing coincident timestamp OBX is for that current clock. In this case the PHG needs to generate a coincident timestamp that would have been generated if the sensor had not updated its clock. The PHG can do this task by adjusting the sensor's contribution to the existing coincident timestamp OBX by subtracting the date-time-adjustment value from OBX-5. For example, if the OBX-5 value the existing coincident timestamp OBX is 20140510092232 and the date-time-adjustment value in the PM-Segment Date-Time-Adjustment attribute is 72 minutes, that indicates the current clock is 72 minutes ahead of what it was prior to the change. Thus one subtracts the 72 minutes from OBX-5 to get the time the clock would have had if no time change were made making OBX-5 equal to 20140510092120.
+
+#### D.1.4.2 OBX-20 replacing OBX-5
+
+In the original version of this standard when an Enum-Observed-Value-Partition attribute was received, the encoded value of the respective Enum OID attribute was placed in OBX-20 and not OBX-5. The value **shall** now be placed in OBX-5. The only time OBX-20 is filled is if there is a value in OBX-5; in other words it is supplementary information.
+
+#### D.1.4.3 Stored and live observations
+
+If a sensor device has stored data and also sends live data, the implementor *may* Service to put these observations in separate OBRs. However, separate OBRs are not required unless the observations are on different time lines.
+
+#### D.1.4.4 Multiple devices
+
+An association from a different device is treated just like any new association. One can place the new association in a new OBR or create a new MDS level n-tuple in the same OBR. There is no relation between the OBR sequence number and the MDS level n-tuple value.
+
+#### D.1.4.5 Observations with and without timestamps
+
+[ISO/IEEE 11073-20601] allows a sensor to send observations with and without timestamps in the same association. An example would be a pulse oximeter sending specialization configuration 0x190 observations ('streamed' SpO<sub>2</sub> and Pulse Rate values with no timestamp) and occasional SPOT observations from specialization configuration 0x191 with timestamps in an extended configuration. In the versions prior to these design guidelines this situation did not pose a problem since the PHG always corrected the sensor's timestamps or provided one on the sensor's behalf. In this version of the standard the sensor timestamps may be used without correction. If that sensor also sent observations without timestamps there would be no way to tell that those timestamps are provided by the PHG. The current solution is to place the sensor timestamped observations in one OBR and the PHG timestamped observations in a separate OBR.
+
+#### D.1.4.6 Bluetooth low energy considerations
+
+Given the Transcoding White Paper [Bluetooth PHDT] it might appear that transcoding is an essential step in the mapping of Bluetooth low energy (Bluetooth LE) sensor data to a PDC-01 document. At face value transcoding is costly. However, this step is not necessary. The mapping of Bluetooth LE data to OBX segments is refreshingly simple. The characteristic value attributes typically arrive with all context information. All that is needed is to decode the bytes into their
+
+specified values and place these values directly into the respective fields of the OBX segment. The specialization being handled pre-determines the majority of the nomenclature codes.
+
+As an example consider the temperature measurement characteristic received by indication. The characteristic is a string of bytes containing a 1-byte flags setting, followed by a 4-byte ASN.1 FLOAT temperature value, followed by an optional 7-byte timestamp, followed by an optional 1-byte temperature type field. The flags indicate whether or not the temperature value is in centigrade or fahrenheit, whether or not there is a timestamp, and whether or not there is a type field. This characteristic maps directly to a Metric-OBX and provides all the information needed to fill the mandatory fields. In this case:
+
+- OBX-2 is NM since the data type is a float.
+- OBX-3 is obtained from the Transcoding White Paper [Bluetooth PHDT]; for a the Thermometer specialization it is MDC\_TEMP\_BODY if there is no temperature type field or if there is a temperature type field it is one of the values indicated in Table D.12 depending upon the value of the temperature type. The partition is MDC\_PART\_SCADA (2) in all cases. From these values OBX-3 can be encoded into its CWE data type:
+
+**Table D.12 – Bluetooth LE temperature location codes**
+
+| <b>11073-10408<br/>Temperature nomenclature code</b> | <b>Temperature type description</b> | <b>Temperature type</b> |
+|------------------------------------------------------|-------------------------------------|-------------------------|
+| MDC_TEMP_AXILLA                                      | Armpit                              | 0x01                    |
+| MDC_TEMP_BODY                                        | Body (general)                      | 0x02                    |
+| MDC_TEMP_EAR                                         | Ear (usually ear lobe)              | 0x03                    |
+| MDC_TEMP_FINGER                                      | Finger                              | 0x04                    |
+| MDC_TEMP_GIT                                         | Gastro-intestinal Tract             | 0x05                    |
+| MDC_TEMP_ORAL                                        | Mouth                               | 0x06                    |
+| MDC_TEMP_RECT                                        | Rectum                              | 0x07                    |
+| MDC_TEMP_TOE                                         | Toe                                 | 0x08                    |
+| MDC_TEMP_TYMP                                        | Tympanum (ear drum)                 | 0x09                    |
+|                                                      | Reserved                            | All other values        |
+
+- OBX-5 is the value obtained from the 4-byte ASN.1 FLOAT.
+- OBX-6 is either MDC\_DIM\_DEGC or MDC\_DIM\_FAHR, depending upon the flags setting, encoded as a CWE data type.
+- OBX-11 is R.
+- OBX-14 is obtained from the timestamp (if present). The 7-byte timestamp is formatted as YYYYMMDDHHMMSS. There is no hundredths and it is local. Just as in the [ISO/IEEE 11073-20601] case, one needs to have previously obtained the coincident timestamp via a time characteristic or the current time service to perform any translations. At this time, case 1 and case 3 are the only relevant cases for Bluetooth LE sensors.
+
+If the value of the float is a special value, OBX-8 and OBX-11 are affected according to clause D.1.3.1.4.2.
+
+#### **D.1.4.7 Differences from [IHE PCD-01]**
+
+There are differences between the Continua guidelines and [IHE PCD-01]. They are noted here.
+
+- [IHE PCD-01] states that OBX-5 is empty if OBX-11 is 'X'. In these guidelines, that situation is only true if the OBX-5 value is one of the special values (NaN, +Inf, etc.).
+- [IHE PCD-01] requires that CWE-2 be non-empty. In these guidelines, CWE-2 may be empty but CWE-1 is always non-empty.
+- [IHE PCD-01] requires the existence of a coincident timestamp pair if the sensor reports a timestamp. In these guidelines, no coincident timestamp pair is reported if the PHG does not translate the sensor times (case #2).
+
+## D.1.4.8 Examples
+
+### D.1.4.8.1 Advanced medication monitor
+
+Below is a PCD-01 document created from an association with an advanced medication monitor supporting a dispensing of a fixed amount of medicine, a question/answer user feedback object, and a status object. The PHG supports soap Observation Upload, capability exchange and authenticated persistent sessions. Sensor supports USB, Bluetooth, ZigBee and Continua 1.0.
+
+```
+MSH|^~\&|0xFEEDBEEBEADDEEF|||20140510092236.770-0400||ORU^R01^ORU_R01|1|P|2.6||NE|AL|||IHE_PCD
+ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7
+PID||28da0026bc42484^^1.19.6.24.109.42.1.3^PI||Landstrom^Goran^L.^Sr.^Dr.^PhD^L^^L
+OBR|1|LNI_PHG^LNI MOXP_PHG^0xFEEDBEEBEADDEEF^EUI-64|LNI_PHG^LNI MOXP_PHG^0xFEEDBEEBEADDEEF^EUI-
+64|182777000^monitoring of patient^SNOMED-CT|||20140510092237.061-0400|20140510092236.776-0400
+OBX|1||531981^MDC_MOC_VMS_MDS_PHG^MDC|0|||||X|||||0xFEEDBEEBEADDEEF^0xFEEDBEEBEADDEEF^EUI-64
+OBX|2||CWE|68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC|0.0.0.1|2^auth-body-continua|||||R
+OBX|3||ST|532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC|0.0.0.1.1|5.0|||||R
+OBX|4||NM|532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC|0.0.0.1.2|28676|||||R
+OBX|5||CWE|68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC|0.0.0.2|2^auth-body-continua|||||R
+OBX|6||CWE|532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC|0.0.0.2.1|1^unregulated(0)|||||R
+OBX|7||CWE|68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC|0.0.0.3|2^auth-body-continua|||||R
+OBX|8||CWE|532355^MDC_REG_CERT_DATA_CONTINUA_PHG_CERT_LIST^MDC|0.0.0.3.1|0^observation-upload-
+soap-2^capability-exchange-6^aps|||||R
+OBX|9||CWE|68220^MDC_TIME_SYNC_PROTOCOL^MDC|0.0.0.4|532234^MDC_TIME_SYNC_EBWW^MDC|||||R
+OBX|10||528456^MDC_DEV_SPEC_PROFILE_AI_MED_MINDER^MDC|1|||||X|||||21d60149fad418^^21d60149fad418
+^EUI-64
+OBX|11||ST|531970^MDC_ID_MODEL_MANUFACTURER^MDC|1.0.0.1|Medication Monitor Manufacturers|||||R
+OBX|12||ST|531969^MDC_ID_MODEL_NUMBER^MDC|1.0.0.2|Clinical Trial 0002|||||R
+OBX|13||ST|531972^MDC_ID_PROD_SPEC_SERIAL^MDC|1.0.0.3|1203ARF33342|||||R|||||0^PrivateOID^21d60149
+fad418^EUI-64
+OBX|14||ST|531976^MDC_ID_PROD_SPEC_FW^MDC|1.0.0.4|Revision14.5|||||R|||||0^PrivateOID^21d60149fad4
+18^EUI-64
+OBX|15||CWE|68218^MDC_ATTR_REG_CERT_DATA_AUTH_BODY^MDC|1.0.0.5|2^auth-body-continua|||||R
+OBX|16||ST|532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC|1.0.0.5.1|5.0|||||R
+OBX|17||NM|532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC|1.0.0.5.2|72~8264~16456~24648|||||R
+OBX|18||CWE|68218^MDC_ATTR_REG_CERT_DATA_AUTH_BODY^MDC|1.0.0.6|2^auth-body-continua|||||R
+OBX|19||CWE|532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC|1.0.0.6.1|1^unregulated(0)|||||R
+OBX|20||CWE|67925^MDC_ATTR_POWER_STAT^MDC|1.0.0.7|1^onMains(0)|||||R
+OBX|21||CWE|68219^MDC_TIME_CAP_STATE^MDC|1.0.0.8|1^mds-time-capab-real-time-clock(0)~1^mds-time-
+capab-set-clock(1)~1^mds-time-capab-relative-time(2)~1^mds-time-mgr-set-time(11)|||||R
+OBX|22||CWE|68220^MDC_TIME_SYNC_PROTOCOL^MDC|1.0.0.9|532224^MDC_TIME_SYNC_NONE^MDC|||||R
+OBX|23||NM|68222^MDC_TIME_RES_ABS^MDC|1.0.0.10|1000000|264339^MDC_DIM_MICRO_SEC^MDC|||||R
+OBX|24||DTM|67975^MDC_ATTR_TIME_ABS^MDC|1.0.0.11|20140510092232|||||R|||20140510092234.061-0400
+OBX|25||NM|67983^MDC_ATTR_TIME_REL^MDC|1.0.0.12|2000000|264339^MDC_DIM_MICRO_SEC^MDC|||||R|||20140510
+092234.061-0400
+OBX|26||NM|8532992^MDC_AI_MED_DISPENSED_FIXED^MDC|1.0.0.13|4|||||R|||20140510092237.061-0400
+OBX|27||8532995^MDC_AI_MED_FEEDBACK^MDC|1.0.1|||||X|||20140510092237.061-0400
+OBX|28||NM|8532996^MDC_AI_MED_UF_LOCATION^MDC|1.0.1.1|1|||||R
+OBX|29||NM|8532996^MDC_AI_MED_UF_LOCATION^MDC|1.0.1.2|0|||||R
+OBX|30||8532995^MDC_AI_MED_FEEDBACK^MDC|1.0.2|||||X|||20140510092237.061-0400
+OBX|31||NM|8532996^MDC_AI_MED_UF_LOCATION^MDC|1.0.2.1|2|||||R
+OBX|32||NM|8532996^MDC_AI_MED_UF_LOCATION^MDC|1.0.2.2|1|||||R
+OBX|33||8532995^MDC_AI_MED_FEEDBACK^MDC|1.0.3|||||X|||20140510092237.061-0400
+OBX|34||NM|8532996^MDC_AI_MED_UF_LOCATION^MDC|1.0.3.1|3|||||R
+OBX|35||NM|8532996^MDC_AI_MED_UF_LOCATION^MDC|1.0.3.2|0|||||R
+OBX|36||8532995^MDC_AI_MED_FEEDBACK^MDC|1.0.4|||||X|||20140510092237.061-0400
+OBX|37||NM|8532996^MDC_AI_MED_UF_LOCATION^MDC|1.0.4.1|4|||||R
+OBX|38||NM|8532996^MDC_AI_MED_UF_LOCATION^MDC|1.0.4.2|1|||||R
+OBX|39||CWE|8532994^MDC_AI_MED_STATUS^MDC|1.0.0.14|1^medication-course-
+complete(4)|||||R|||20140510092237.061-0400
+```
+
+### D.1.4.8.2 Pulse oximeter with scale
+
+This sensor supports two specializations and thus reports hydra at the top level.
+
+```
+MSH|^~\&|0xFEEDABEEBEADDEEF|||20140510094932.815-0400||ORU^R01^ORU_R01|5|P|2.6|||NE|AL|||IHE PCD
+ORU-R012006^HL7^2.16.840.1.1.113883.9.n.m^HL7
+PID||28da0026bc42484^^^1.19.6.24.109.42.1.3^PI||Landstrom^Goran^L.^Sr.^Dr.^PhD^L^^L
+OBR||LNI_PHG^LNI MOXP_PHG^0xFEEDABEEBEADDEEF^EUI-64|LNI_PHG^LNI MOXP_PHG^0xFEEDABEEBEADDEEF^EUI-
+64|182777000^monitoring of patient^SNOMED-CT|||20140510094931.835-0400|20140510094932.815-0400
+OBX|1||531981^MDC_MOC_VMS_MDS_PHG^MDC|0|||||X|||||0xFEEDABEEBEADDEEF^^0xFEEDABEEBEADDEEF^EUI-64
+Several PHG-OBXes
+OBX|10||528384^MDC_DEV_SPEC_PROFILE_HYRDA^MDC|1|||||X|||||21d60149fad418^^21d60149fad418^EUI-64
+OBX|11||CWE|68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC|1.0.0.1|528388^MDC_DEV_SPEC_PROFILE_PULS_OXIM^MDC~5
+28399^MDC_DEV_SPEC_PROFILE_SCALE^MDC|||||R
+OBX|12||ST|531970^MDC_ID_MODEL_MANUFACTURER^MDC|1.0.0.2| MultiSensor ModelPOWS|||||R
+OBX|13||ST|531969^MDC_ID_MODEL_NUMBER^MDC|1.0.0.3|MultiSensor002|||||R
+OBX|14||ST|531972^MDC_ID_PROD_SPEC_SERIAL^MDC|1.0.0.4|1203ARF33342|||||R|||||0^PrivateOID^21d60149
+fad418^EUI-64
+OBX|15||ST|531976^MDC_ID_PROD_SPEC_FW^MDC|1.0.0.5|Rev14.5|||||R|||||0^PrivateOID^21d60149fad418^EU
+I-64
+OBX|16||CWE|68218^MDC_ATTR_REG_CERT_DATA_AUTH_BODY^MDC|1.0.0.6|2^auth-body-continua|||||R
+OBX|17||ST|532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC|1.0.0.6.1|5.0|||||R
+OBX|18||NM|532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC|1.0.0.6.2|4~8196~16388~24580~15~8207~1
+6399~24591|||||R
+OBX|19||CWE|68218^MDC_ATTR_REG_CERT_DATA_AUTH_BODY^MDC|1.0.0.7|2^auth-body-continua|||||R
+OBX|20||CWE|532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC|1.0.0.7.1|1^unregulated(0)|||||R
+OBX|21||CWE|67925^MDC_ATTR_POWER_STAT^MDC|1.0.0.8|1^onMains(0)|||||R
+OBX|22||CWE|68219^MDC_TIME_CAP_STATE^MDC|1.0.0.9|1^mds-time-capab-real-time-clock(0)~1^mds-time-
+capab-set-clock(1)~1^mds-time-capab-relative-time(2)~1^mds-time-mgr-set-time(11)|||||R
+OBX|23||CWE|68220^MDC_TIME_SYNC_PROTOCOL^MDC|1.0.0.10|532224^MDC_TIME_SYNC_NONE^MDC|||||R
+OBX|24||NM|68222^MDC_TIME_RES_ABS^MDC|1.0.0.11|1000000|264339^MDC_DIM_MICRO_SEC^MDC|||||R
+OBX|25||DTM|67975^MDC_ATTR_TIME_ABS^MDC|1.0.0.12|20140510094930|||||R|||20140510094930.835-0400
+OBX|26||NM|67983^MDC_ATTR_TIME_REL^MDC|1.0.0.13|2000000|264339^MDC_DIM_MICRO_SEC^MDC|||||R|||20140510
+094930.835-0400
+OBX|27||NM|150456^MDC_PULS_OXIM_SAT_O2^MDC|1.0.0.14|87.5|262688^MDC_DIM_PERCENT^MDC|||||R|||201405100
+94931.835-0400
+OBX|28||NM|188736^MDC_MASS_BODY_ACTUAL^MDC|1.0.0.15|91.8423|263875^MDC_DIM_KILO_G^MDC|||||R|||2014051
+0094931.835-0400
+OBX|29||NM|149530^MDC_PULS_OXIM_PULS_RATE^MDC|1.0.0.16|75.8|264864^MDC_DIM_BEAT_PER_MIN^MDC|||||R|||2
+0140510094931.835-0400
+```
+
+### D.1.5 Timestamping and time synchronization
+
+Timestamps associated with observations sent over the Continua services shall be referenced to a single consistent Coordinated Universal Time (UTC) timeline to facilitate accurate correlation and processing. Ideally, the timestamps should include the local time offset where the observations were made to facilitate correlation with manual records maintained by the patient and caregivers.
+
+Since many Personal Health Devices have only a sense of internal time, and this internal time may not be equivalent to the UTC and local time maintained by the PHG, the Continua Services interface requires the ability to report a coincident timestamp pair. The coincident timestamp pair is formed by capturing the current time from both the device and the PHG as close to simultaneously as is reasonably possible. This capture establishes the time relationship between the PHG and the device's internal time and allows the PHG to report device observations on the UTC timeline.
+
+NOTE – The coincident timestamp pair allows the services receiver to display and record the original device time and the PHG UTC time in the case where the PHG translates timestamps. The coincident timestamp pair can also support an audit of the original timestamps provided by the Personal Health Device.
+
+Three types of timestamps are defined:
+
+- **Qualified time:** A "qualified time" expresses a unique time point along the coordinated universal time (UTC) timescale that is the primary time standard by which the world regulates clocks and time.
+
+Qualified time is expressed as an HL7 V2 "DTM" datatype and must include the time zone offset, expressed either as  $\pm ZZZZ$  (HHMM) if the civil time zone offset is known or  $-0000$  if UTC time (e.g., derived from NTP) is known but the actual civil time zone offset is not. Note
+
+that the unknown civil time zone ( $-0000$ ) is a DG2015 extension to the formal definition of 'qualified time' which includes the civil time zone. The qualified time syntax is:
+
+- **YYYYMMDDHHMMSS[.S[S[S[S]]]] $\pm$ ZZZZ** if civil time zone offset  $\pm$ ZZZZ is known.
+- **YYYYMMDDHHMMSS[.S[S[S[S]]]] $-0000$**  if UTC time is known but civil time zone is not.
+
+Table D.13 contains examples of qualified time timestamps.
+
+**Table D.13 – Qualified time timestamp examples**
+
+| Example             | Description                                                                        |
+|---------------------|------------------------------------------------------------------------------------|
+| 19760104010123-0500 | 1:01:23 AM on 4 January 1976 in the Eastern Standard Time zone (USA)               |
+| 19760704010123-0400 | 1:01:23 AM on 4 July 1976 in the Eastern Daylight Saving Time zone (USA).          |
+| 19760704010523-0000 | 1:01:23 AM on 4 July 1976, Eastern Daylight Saving Time, expressed as UTC.         |
+| 20130722162400+0100 | 4:24:00 PM on 22 July 2013, British Summer Time (BST) (Prince George birth)        |
+| 20131122162400+0000 | 4:24:00 PM on 22 November 2013, Greenwich Mean Time (GMT)                          |
+| 20131122162400-0000 | 4:24:00 PM on 22 November 2013 in London, but expressed as UTC.                    |
+| 20131123012400+0900 | The same time-point, expressed with Tokyo local time-zone offset (on the next day) |
+
+- **unqualified local time:** the syntax is **YYYYMMDDHHMMSS[.S[S[S[S]]]]**, where the time zone offset is omitted: the civil time zone offset and UTC time are both unknown.
+- **synchronized:** a qualified timestamp that is accurate within predefined limits that shall not exceed 5 minutes **DTM<sub>PHG</sub>**: HL7 V2 'DTM' timestamps sent by the PHG in **MSH-7**, **OBR-7**, **OBR-8** and **OBX-14**. These represent the time that will be used by the Services receiver and other enterprise applications.
+
+Note that qualified time does not imply accuracy; it simply means that the time reported is on the UTC time line with local offset (which may also be expressed as  $-0000$ ). Accuracy comes from synchronization and the degree of accuracy is determined by the method and source of synchronization.
+
+To ensure the highest level of interoperability, it is **strongly recommended** that **DTM<sub>PHG</sub>** timestamps use **qualified time** to express a unique timepoint on the UTC timescale. Ideally, the actual civil time zone offset  $\pm$ ZZZZ **should** be used; otherwise, the time zone  $-0000$  may be specified to indicate UTC time. Continua services Observation Upload devices **shall** be capable of being synchronized to a reference time source such as NTP, CDMA, GSM NITZ or other source of reference time. In certain cases (and only as a last resort) unqualified local time may be conveyed by a **DTM<sub>PHG</sub>** timestamp.<sup>1</sup>
+
+<sup>1</sup> Note that in order for an AHD it shall be capable of being synchronized to an external time source.
+
+### D.1.5.1 PHG clock and synchronization
+
+Information regarding the PHG clock and PHG synchronization state are described in Table D.14. By convention, information describing the PHG clock is conveyed by MDS level 0 in OBX-4.
+
+**Table D.14 – PHG time elements**
+
+| Msg segment<br>(Note 1) | Description and comments                                                                                                                                                                                             | Q<br>(Note 2) |
+|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| MSH                     | MSH-7 Date/Time of Message created/sent (DTM <sub>PHG</sub> )                                                                                                                                                        | M             |
+| PID                     |                                                                                                                                                                                                                      | M             |
+| OBR                     | [OBR-7, OBR-8) Default time interval for child OBXs (DTM <sub>PHG</sub> )                                                                                                                                            | M             |
+| OBX 0                   | PHG                                                                                                                                                                                                                  | M             |
+| OBX 0.0.0.1             | MDC_TIME_SYNC_PROTOCOL (OBX-5 specifies the time sync protocol of the PHG; see Table D.19 for the list of valid synchronization profiles)                                                                            | M             |
+| OBX 0.0.0.2             | MDC_TIME_SYNC_ACCURACY (OBX-5 specifies the known or estimated accuracy of DTM <sub>PHG</sub> time, relative to a reference time source such as NTP)                                                                 | O             |
+| OBX 0.0.0.3             | MDC_ATTR_TIME_REL (OBX-5 specifies the relative timestamp value, OBX-14 specifies the corresponding DTM <sub>PHG</sub> , and OBX-18 specifies the unique identity of the timebase provided by the PHG)               | C             |
+| OBX 0.0.0.4             | MDC_TIME_RES_REL (OBX-5 specifies the resolution of the relative clock)                                                                                                                                              | O             |
+| OBX 0.0.0.5             | MDC_ATTR_TIME_REL_HI_RES (OBX-5 specifies the hi-res relative timestamp value, OBX-14 specifies the corresponding DTM <sub>PHG</sub> , and OBX-18 specifies the unique identity of the timebase provided by the PHG) | C             |
+| OBX 0.0.0.6             | MDC_TIME_REL_HI_RES (OBX-5 specifies the resolution of the hi-res relative clock)                                                                                                                                    | O             |
+
+NOTE 1 – The dotted numbers represent the object hierarchy value of OBX-4 and are provided as example values only, except for MDS level 0 which is reserved for observations about the PHG itself.  
+NOTE 2 – Column Q denotes the presence qualifier: M: mandatory, O: option, C: conditional.
+
+The mandatory MDC\_TIME\_SYNC\_PROTOCOL attribute specifies the time sync protocol used by the PHG, drawing from the list of enumerated values listed in Table D.19.
+
+The optional MDC\_TIME\_SYNC\_ACCURACY attribute specifies the estimated accuracy of timestamps sent by the PHG. It is defined as the maximum error of the PHG clock relative to a primary reference clock source such as a NTP, cellular, etc., in seconds. The accuracy is encoded as positive decimal number of seconds (e.g., '10., '5., '0.5,' etc.) or some other scaled unit such as microseconds using the HL7 V2 'NM' datatype and **shall** include an estimate of the cumulative error due to clock drift since the PHG clock was last synchronized.
+
+NOTE – The accuracy of PHG clocks that are synchronized by the Internet 'Network Time Protocol' [IETF RFC 1305] or 'Simple Network Time Protocol' (IETF RFC 2030) can be estimated using the following relationship:  $MDC\_TIME\_SYNC\_ACCURACY = \text{'root dispersion' + } \frac{1}{2} \text{'root delay' + the cumulative clock drift}$  (typically 20 ppm times the elapsed time since the PHG had last synchronized to NTP). Alternative estimates for accuracy may be used if other synchronization protocols or methods are employed. MDC\_TIME\_SYNC\_ACCURACY shall not be reported, however, if the PHG's clock has not been synchronized to a reference source of time.
+
+If MDC\_TIME\_SYNC\_ACCURACY is unknown or exceeds five minutes, MDC\_TIME\_SYNC\_PROTOCOL **shall** be set to MDC\_TIME\_SYNC\_NONE to indicate an uncalibrated and unsynchronized local clock.
+
+#### D.1.5.1.1 PHG provides relative time synchronization services to sensors
+
+If the PHG provides a common relative or high-resolution relative clock service to devices, it **shall** include MDC\_ATTR\_TIME\_REL or MDC\_ATTR\_TIME\_REL\_HI\_RES attribute containing a unique identifier string in OBX-18, described in Table D.18. If the time synchronization between the relative or high-resolution relative clock reported in OBX-5 is known relative to UTC, it shall be disclosed in OBX-14 (this is an example of a coincident timestamp pair where the comparison is between the relative time clock and the UTC-based time clock of the PHG; a coincident time relation between the PHG and the sensor is provided indirectly since the PHG is controlling the sensor's relative time clock). The MDC\_TIME\_RES\_REL and MDC\_TIME\_REL\_HI\_RES attributes specify the resolution of the relative and hi-res relative clocks, respectively; if omitted, the default resolution of 125 µs and 1 µs shall be assumed.
+
+#### D.1.5.2 Sensor clocks and synchronization
+
+Information regarding the sensor clocks and sensor observations are described in Table D.15.
+
+The default time interval for all measurements is specified by [OBR-7, OBR-8) of the containing OBR message segment. A time that falls within this interval can be explicitly specified by a DTM<sub>PHG</sub> time point value specified by OBX-14 at the CHAN, METRIC, FACET or SUBFACET levels. Every OBX-14 timestamp value must be within the interval [OBR-7, OBR-8) specified by the containing OBR.
+
+**Table D.15 – Sensor time elements**
+
+| Msg segment   | Description and comments                                                                                                                                                                                       | Q |
+|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|
+| OBR.          | [OBR-7, OBR-8) Default time interval for child OBXs (DTM <sub>PHG</sub> )                                                                                                                                      | M |
+| OBX.. 1       | MDS for device #1                                                                                                                                                                                              | M |
+| OBX.. 1.0.0.1 | MDC_TIME_CAP_STATE (BITS-16, using MdsTimeCapState obtained from Mds-Time-Info)                                                                                                                                | C |
+| OBX.. 1.0.0.2 | MDC_TIME_SYNC_PROTOCOL (obtained from Mds-Time-Info)                                                                                                                                                           | O |
+| OBX.. 1.0.0.3 | MDC_TIME_SYNC_ACCURACY (sensor absolute or base-offset time accuracy obtained from Mds-Time-Info)                                                                                                              | O |
+| OBX.. 1.0.0.4 | MDC_ATTR_TIME_ABS (OBX-5 specifies the unqualified displayed time and OBX-14 specifies the corresponding DTM <sub>PHG</sub> )                                                                                  | C |
+| OBX.. 1.0.0.5 | MDC_ATTR_TIME_BO (OBX-5 specifies the qualified displayed time and time zone offset and OBX-14 specifies the corresponding DTM <sub>PHG</sub> )                                                                |   |
+| OBX.. 1.0.0.6 | MDC_ATTR_TIME_REL (OBX-5 specifies the relative timestamp value, OBX-14 specifies the corresponding DTM <sub>PHG</sub> , and OBX-18, if present, specifies the unique identity of the timebase*)               |   |
+| OBX.. 1.0.0.7 | MDC_TIME_RES_REL (OBX-5 specifies the resolution of the relative clock and OBX-18, if present, specifies the unique identity of the timebase*) Time resolution obtained from Mds-Time-Info                     |   |
+| OBX.. 1.0.0.8 | MDC_ATTR_TIME_REL_HI_RES (OBX-5 specifies the hi-res relative timestamp value, OBX-14 specifies the corresponding DTM <sub>PHG</sub> , and OBX-18, if present, specifies the unique identity of the timebase*) |   |
+
+**Table D.15 – Sensor time elements**
+
+| Msg segment   | Description and comments                                                                                                                                                                        | Q |
+|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|
+| OBX.. 1.0.0.9 | MDC_TIME_RES_REL_HI_RES (OBX-5 specifies the resolution of the hi-res relative clock, and OBX-18, if present, specifies the unique identity of the timebase) Time resolution from Mds-Time-Info |   |
+| OBX.. 1.0.N.M | For any observation, OBX-14 $DTM_{PHG}$ may be <i>optionally</i> valued with a timepoint that overrides the default [OBR-7, OBR-8] time interval of the containing OBR                          |   |
+| OBR.          | [OBR-7, OBR-8) Default time interval for child OBXs ( $DTM_{PHG}$ )                                                                                                                             | O |
+| OBX.. 2       | MDS for device #2                                                                                                                                                                               | M |
+
+NOTE – Information for OBX-18 must be obtained out of band (it is not provided via the ISO/IEEE 11073-20601 exchanges).
+
+Notes for Table D.14 and Table D.15:
+
+- a. The conversion of sensor time to  $DTM_{PHG}$  may introduce a rounding error of the fractional component due to the conversion of the original binary fractional component expressed in units of 1/65536th of a second to a decimal fraction that is limited to 1/10000th of a second.
+- b. Within the time scope of each MDS object, time discontinuities in the  $MDC\_ATTR\_TIME\_ABS$  displayed time are prohibited. Discontinuities due to daylight savings or other clock adjustments require data on the new displayed timeline be sent under a separate MDS or within a separate message. Since the Base component of the Base Offset time is never discontinuous by definition, any discontinuity is expressed by the offset  $\pm ZZZZ$ . Thus the PHG will not have a problem providing a consistent time base in OBX-14 and it is not necessary to perform the above steps when the offset value changes.
+- c. OBR-7 and OBR-8 establish the default time context for all OBXs within the scope of the containing OBR. If only OBR-7 is specified, the default time context is a time point; if OBR-7 and OBR-8 are both specified, it is a time interval. The default time context can be overridden by a timestamp (representing a point in time) in OBX-14 at the CHAN, METRIC, FACET or SUBFACET levels. Since these guidelines require an OBX-14 entry for all observation OBX segments, the default time context is always overridden. However, OBR-7 and OBR-8 provide the time range for informational purposes.
+- d. The time interval specified by [OBR-7, OBR-8) is a mathematically 'closed' interval for OBR-7 and 'open' for OBR-8. A datum that occurs exactly at the time specified by OBR-8 would be sent in the next time epoch. This allows subsequent OBR segments to represent a continuous sequence of time. For encoding a simple set of episodic measurement, if there is no logical "end" of the observation period, OBR-8 can be set to the message creation time as a logical upper limit for the contained observations
+
+The time information above is provided for each sensor (MDS-level) and is conveyed at the METRIC level in OBX-4, prior to any sensor observations. There are three cases to consider: the first where the PHG translates the original sensor timestamps to the UTC timeline; the second, where the original sensor absolute or base-offset timestamps are reported without translation; and third, the sensor does not communicate a timestamp and the PHG provides timestamps on its behalf.
+
+**Case 1: PHG translates sensor timestamps**
+
+The presence of a coincident timestamp with the presence of time capabilities OBX indicates that the PHG has translated the original sensor timestamps to the UTC or local timeline. The coincident timestamp pair with the sensor timestamp in OBX-5 and the corresponding  $DTM_{PHG}$  in OBX-14 allows the PHG to report sensor observations on the UTC timeline and documents the sensor to
+
+DTM<sub>PHG</sub> conversions for auditing purposes. This information may be used by the Services receiver to reconstruct the original sensor time, assuming that discontinuities do not exist in the original sensor timeline.
+
+The MDC\_TIME\_RES\_REL and MDC\_TIME\_RES\_REL\_HI\_RES MDS-OBX segments specify the resolution of the sensor's relative and hi-res relative clocks, respectively. If these values are not reported (indicates unknown), the default resolution of 125 µs and 1 µs shall be assumed.
+
+### Case 2: PHG does not translate device timestamps
+
+The absence of a coincident timestamp with the presence of time capabilities OBX indicates the original absolute (ABS) sensor time is reported in OBX-14 as an 'unqualified local time' (without a time zone offset) or the original base-offset (BO) sensor time is reported in OBX-14 having a  $\pm ZZZZ$  or  $-0000$  time zone offset.
+
+This option allows the PHG to report the original sensor timestamps in cases where (1) the sensor's qualified base-offset timestamps are presumed to be more accurate than the PHG's or (2) when the PHG is not synchronized to an external time reference and therefore cannot translate reliability.
+
+### Case 3: PHG provides timestamp on behalf of device
+
+The lack of a coincident timestamp and time capabilities OBX indicates that the device is not capable of providing timestamps and that the OBX-14 timestamps in subsequent OBXs are provided by the PHG on behalf of the device.
+
+#### D.1.5.3 PHG and sensor timestamps
+
+Table D.16 shows how sensor timestamps may (or may not) be converted to the UTC timeline, given the (1) PHG clock capability, (2) the type of sensor timestamp and (3) whether a coincident timestamp pair is (or was) associated with the sensor observation. The symbol 'T(\*)' indicates that the sensor time '\*' can be translated to the UTC timeline, and assumes that the coincident timestamp pair exists and is disclosed using the MDC\_ATTR\_TIME\_ { ABS, BO, REL and REL\_HI\_RES } attribute(s). The symbol '\*' indicates the original sensor time may be reported. Additional information such as PHG and sensor synchronization state and accuracy can be used if a choice between T(\*) and \* is permitted.
+
+**Table D.16 – PHG and sensor timestamps**
+
+| Case | PHG clock and timestamps |       |     |            | Device timestamps |                        |                                 |
+|------|--------------------------|-------|-----|------------|-------------------|------------------------|---------------------------------|
+|      | NTP                      | Local | DST | TZ         | Hi-res/Relative   | Absolute (no TZ)       | Base-Offset ( $\pm TZ$ )        |
+| A    | Yes                      | Yes   | Yes | $\pm ZZZZ$ | T(*) $\pm ZZZZ$   | T(*) $\pm ZZZZ$ else * | * $\pm ZZZZ$ or T(*) $\pm ZZZZ$ |
+| B    | Yes                      | Yes   | No  | $\pm ZZZZ$ | T(*) $\pm ZZZZ$   | T(*) $\pm ZZZZ$ else * | * $\pm ZZZZ$ or T(*) $\pm ZZZZ$ |
+| C    | Yes                      | No    | No  | $-0000$    | T(*) $-0000$      | T(*) $-0000$ else *    | * $\pm ZZZZ$ or T(*) $-0000$    |
+| D    | No                       | Yes   | No  | $\pm ZZZZ$ | T(*) $\pm ZZZZ$   | T(*) $\pm ZZZZ$ else * | * $\pm ZZZZ$ or T(*) $\pm ZZZZ$ |
+| E    | No                       | No    | No  | none       | T(*)              | *                      | * $\pm ZZZZ$                    |
+
+**Table D.17 – PHG time behaviours**
+
+| Case | PHG time description                                                     | Qualified | Error    |
+|------|--------------------------------------------------------------------------|-----------|----------|
+| A    | Best: Displayed time and time zone known (by DST rules)                  | Yes       | < 1 s    |
+| B    | Better: Displayed time and time zone known (by external information)     | Yes       | < 1 s    |
+| C    | Good: UTC time known but displayed time and zone unknown                 | Yes       | < 1 s    |
+| D    | Usable: Qualified time but not synchronized (e.g., manually set by user) | Yes       | < 120 s  |
+| E    | Poor: Unqualified and unsynchronized local time (UTC and TZ unknown)     | No        | ≈ 1 hour |
+
+A PHG operating in mode A shall correctly translate all timestamps including all stored observations that straddle a change of DST.
+
+A PHG operating in mode B shall correctly translate most timestamps but will be unable to correctly translate stored observations that straddle a change of DST.
+
+A PHG operating in mode C shall correctly translate timestamps to UTC but will be unable to correctly translate to local time.
+
+A PHG operating in mode D shall translate timestamps but accuracy is unknown.
+
+A PHG operating in mode E shall not translate timestamps.
+
+**Column definitions for PHG clock and timestamp properties:**
+
+**Case** is a label for each combination of **PHG Clock** and **Timestamp** properties, including:
+
+**NTP:** 'Yes' if synchronized to global time reference such as NTP, CDMA, GSM NITZ, ... , 'No' if not.
+
+**Local:** 'Yes' if current local time zone offset is known, 'No' if not.
+
+**DST:** 'Yes' if aware of local Daylight Savings Time rules, 'No' if not.
+
+NOTE – An PHG that supports daylight savings rules is capable of providing the correct offsets to measurements received from a sensor before the daylight savings time change. The timeline is reported in the time zone of the PHG. It is assumed that the date-time-adjustment provided by the sensor is only due to daylight savings changes; no combinations of clock skew or time zone changes are part of the date-time-adjustment value.
+
+**TZ:**  $\pm ZZZZ$  if civil time zone offset known,  $-0000$  if only UTC time is known, 'none' if unknown.
+
+**Qualified:** 'Yes' if "qualified" by having a  $\pm ZZZZ$  or  $-0000$  time zone offset.
+
+**Error:** Nominal error (e.g., "unqualified local time will be incorrect for 23 out of 24 time zones")
+
+**Column definitions for sensor timestamps:**
+
+1. **T(\*)** refers to **translated sensor timestamps**, indicated by presence of a coincident timestamp.
+2. \* indicates an **original sensor timestamp**, indicated by the absence of a coincident timestamp but with time capabilities.
+3.  $\pm ZZZZ$  indicates time-zone offset,  $-0000$  indicates UTC / NTP time, no suffix after T(\*) or \* indicates "local" time.
+4. **XXX else YYY** indicates XXX preferred over YYY; **XXX or YYY** indicates no preference.
+
+NOTE 1 – For TZ = -0000, the services receiver could adjust time zone based on 'local agreement' without loss of accuracy.
+
+NOTE 2 – If PHG is used in a known or restricted geographic area, services receiver could adjust time zone based on 'local agreement'.
+
+### General comments (informative)
+
+For the **Hi-res/Relative** sensor timestamp column, translation  $T(*)$  is required to convert the integer count to the PHG UTC timeline.
+
+For the **Absolute** sensor timestamp column, translation  $T(*)$  is required to convert the absolute time to the PHG UTC timeline as well as local time with timezone offset. The transformation can only be performed if a coincident timestamp pair is captured and does not have any discontinuities due to Daylight Savings or other adjustments during the time interval [OBR-7, OBR-8) since  $T(*)$  is a linear transformation. If this condition cannot be guaranteed it is recommended that the original unqualified local timestamp '\*' be sent instead.
+
+For the **Base-Offset** sensor timestamp column, the original  $\pm ZZZZ$  or translated  $T(*)\pm ZZZZ$  timestamp may be sent, with a preference for the former unless it was necessary for the PHG to correct for sensor clock drift.
+
+For a **PHG clock that is unsynchronized and is unaware of local time** (row/Case E), an **absolute** sensor time shall be sent as an unqualified '\*' timestamp, a **base-offset** sensor time shall be sent as a qualified or unqualified  $\pm ZZZZ$  timestamp, depending upon the base-offset time base alignment, with no correction applied, and a **hi-res/relative** time shall be translated and sent as an unqualified  $T(*)$  timestamp.
+
+### Additional PHG and sensor timestamp selection rules
+
+The previous table indicates a choice between using the PHG translated time  $T(*)$  and the original device time \* for certain combinations of PHG and device timestamps. This section provides further guidance regarding the selection, based on the whether the PHG and/or device time is synchronized, and in the case where both are synchronized, their relative synchronization accuracy (if known).
+
+![Figure D-1 – PHG and sensor time accuracy selection. It contains two diagrams, (a) and (b). Diagram (a) is titled 'Time synchronization' and shows a table for selecting PHG time based on whether PHG and Device are Synced or Unsynced. Diagram (b) is titled 'Time accuracy' and shows a table for selecting PHG time based on whether PHG and Device time accuracy is Known or Unknown. Both diagrams include icons of a computer and a medical device.](a48594f1a3fecef5e047a7c3a63b1220_img.jpg)
+
+**Time synchronization**
+
+|            |                 |                 |                 |
+|------------|-----------------|-----------------|-----------------|
+|            |                 | <b>Device</b>   |                 |
+|            |                 | <b>Synced</b>   | <b>Unsynced</b> |
+| <b>PHG</b> | <b>Synced</b>   | GOTO (b)        | USE PHG time    |
+|            | <b>Unsynced</b> | Use device time | Use device time |
+
+(a)
+
+**Time accuracy**
+
+|            |                |                   |                 |
+|------------|----------------|-------------------|-----------------|
+|            |                | <b>Device</b>     |                 |
+|            |                | <b>Known</b>      | <b>Unknown</b>  |
+| <b>PHG</b> | <b>Known</b>   | Use most accurate | USE PHG time    |
+|            | <b>Unknown</b> | Use device time   | Use device time |
+
+(b)
+
+H.812.1(17)\_FD.1
+
+Figure D-1 – PHG and sensor time accuracy selection. It contains two diagrams, (a) and (b). Diagram (a) is titled 'Time synchronization' and shows a table for selecting PHG time based on whether PHG and Device are Synced or Unsynced. Diagram (b) is titled 'Time accuracy' and shows a table for selecting PHG time based on whether PHG and Device time accuracy is Known or Unknown. Both diagrams include icons of a computer and a medical device.
+
+**Figure D-1 – PHG and sensor time accuracy selection**
+
+### D.1.5.4 HL7 timebase identifier
+
+In Table D.18, this design guidelines document defines the following HL7 user table for OBX-18-2: Namespace ID.
+
+**Table D.18 – HL7 user table for OBX-18-2**
+
+| OBX-18-2    | Description                                                                         | Examples                                                                                         |
+|-------------|-------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|
+| TIMEBASE_ID | A universally unique identifier of the timebase used for a given relative timestamp | 732d2650-2cd1-11df-8a39-0800200c9a66^TIMEBASE_ID<br>BT_HDP-ABCDEF123456-1^TIMEBASE_ID (see Note) |
+
+NOTE – One suggested approach for defining this unique identifier is to use the 3-tuple of the synchronization protocol, an identifier for the synchronization source (e.g., a Bluetooth address), and the 'epoch' of this clock (e.g., an integer value which increments with each new association, or a datetime signifying the start of the last synchronization).
+
+Two relative or high-resolution relative observations are 'comparable' if and only if the OBX-18 values match exactly. Note that this information for sensor devices cannot be obtained using any of the Continua protocols and thus inclusion of an OBX-18 field in the OBX segments describing the sensor relative timestamps is optional.
+
+#### D.1.5.5 Synchronization protocols
+
+Beyond the use of the MDC\_ATTR\_TIME\_ABS, MDC\_ATTR\_TIME\_BO, MDC\_ATTR\_TIME\_REL and MDC\_ATTR\_TIME\_REL\_HI\_RES time code observations, a services observation sender provides additional information about the Personal Health Device clocks by communicating the MDC\_TIME\_SYNC\_PROTOCOL of a given sensor (the sensor device is required to send this information if it supports any type of real time clock). Valid synchronization profiles are shown in Table D.19.
+
+**Table D.19 – Time synchronization nomenclature codes**
+
+| OBX-5                              | Synchronization protocol                                                                                                                                                                                                                                | Part::Code |
+|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|
+| 532224^MDC_TIME_SYNC_NONE^MDC      | An uncalibrated and unsynchronized local clock source<br><br>NOTE – If MDC_TIME_SYNC_ACCURACY is unknown or exceeds five minutes, MDC_TIME_SYNC_PROTOCOL shall be set to MDC_TIME_SYNC_NONE to indicate an uncalibrated and unsynchronized local clock. | 8::7936    |
+| 532234^MDC_TIME_SYNC_EBWW^MDC      | A manually set time, by 'eyeball and wristwatch'                                                                                                                                                                                                        | 8::7946    |
+| 532225^MDC_TIME_SYNC_NTPV3^MDC     | Network Time Protocol Version 3.0 (RFC 1305)                                                                                                                                                                                                            | 8::7937    |
+| 532226^MDC_TIME_SYNC_NTPV4^MDC     | Network Time Protocol Version 4.0 (under dev)                                                                                                                                                                                                           | 8::7938    |
+| 532227^MDC_TIME_SYNC_SNTPV4^MDC    | Simple Network Time Protocol v4 (RFC 2030)                                                                                                                                                                                                              | 8::7939    |
+| 532228^MDC_TIME_SYNC_SNTPV4330^MDC | Simple Network Time Protocol v4 (RFC 4330)                                                                                                                                                                                                              | 8::7940    |
+| 532229^MDC_TIME_SYNC_BTV1^MDC      | Bluetooth Medical Device Profile                                                                                                                                                                                                                        | 8::7941    |
+| 532235^MDC_TIME_SYNC_USB_SOF^MDC   | Synced to the 1kHz USB "start-of-frame" clock                                                                                                                                                                                                           | 8::7947    |
+
+**Table D.19 – Time synchronization nomenclature codes**
+
+| <b>OBX-5</b>                     | <b>Synchronization protocol</b>                     | <b>Part::Code</b> |
+|----------------------------------|-----------------------------------------------------|-------------------|
+| 532230^MDC_TIME_SYNC_RADIO^MDC   | Atomic Clock synchronization through RF             | 8::7942           |
+| 532231^MDC_TIME_SYNC_HL7_NCK^MDC | Synchronized via Health Level 7 NCK (network clock) | 8::7943           |
+| 532232^MDC_TIME_SYNC_CDMA^MDC    | CDMA mobile telecommunications synchronization      | 8::7944           |
+| 532233^MDC_TIME_SYNC_GSM^MDC     | GSM - Network Identity and Time Zone (NITZ)         | 8::7945           |
+
+#### D.1.5.6 Absolute or base offset timestamp accuracy
+
+Absolute or base-offset timestamp 'accuracy' **may** be reported using MDC\_TIME\_SYNC\_ACCURACY. For instance, if the sensor's clock has been synchronized using the Internet 'Network Time Protocol' [RFC 1305], 'Simple Network Time Protocol' [RFC 2030], the HL7 v2.6 'NCK' system clock segment, or another sufficiently capable time synchronization protocol, it is possible to compute the possible drift in accuracy since the device's last synchronization.
+
+NOTE – NTP timestamp accuracy can be estimated from the NTP variables: root dispersion + ½ root delay + the cumulative clock drift (typically 20 ppm times the elapsed time since the PHD had last synchronized to NTP). For other absolute time distribution protocols (e.g., mobile phone) other methods might be used (and are currently beyond the scope of this document).
+
+Estimated values for accuracy may be reported in cases where the agent had acquired and stored data while disconnected from a time synchronization source. However, the PHG can only obtain this information if the sensor populates the respective ASN.1 structures in the Mds-Time-Info attribute. [ISO/IEEE 11073-20601] allows the sensor to populate the time synchronization accuracy field with unknown regardless of its synchronization state.
+
+If MDC\_TIME\_SYNC\_ACCURACY is unknown or exceeds five minutes, MDC\_TIME\_SYNC\_PROTOCOL shall be set to MDC\_TIME\_SYNC\_NONE to indicate an uncalibrated and unsynchronized local clock. Note that this value overrides what the sensor reports in the Mds-Time-Info synchronization protocol field.
+
+MDC\_TIME\_SYNC\_ACCURACY **shall not** be reported for the PHG if the PHG clock has not been synchronized, as sensors that use PHGs as a time synchronization service may rely on this value to determine whether they should update their own clocks and to qualify the accuracy of their own timestamps. Note that [ISO/IEEE 11073-20601] sensors cannot obtain any knowledge about the PHG's time capabilities or synchronization state via the 11073-20601 or any CDG- defined protocol; this information would require the use of a non-Continua protocol or be obtained out of band. The PHG's timestamp accuracy does not include the communication latency between the PHG and the timeserver; it only specifies the known accuracy of the PHG's timestamp relative to a primary reference clock source.<sup>2</sup> The example below is a case where the PHG has determined that it
+
+<sup>2</sup> At the time of this writing, [IEEE 11073-20601] does not specify a high-resolution time synchronization protocol, such as the 'IEEE:1073:3:2:SNTP' IAS service defined in the informative Annex N of [ISO/IEEE 11073-30200-2004]. The latter supports the exchange of 48-octet NTP or SNTP messages between a client (DCC) and server (BCC) using the 'expedited' TTP\_UData transport service (similarly, NTP and SNTP use a 'best effort' UDP/IP transport over UDP port 123).
+
+has superior synchronization capabilities to the sensor as indicated by the presence of the coincident timestamp pair in the MDS-OBXes.
+
+```
+OBX|n|DTM|67975^MDC_ATTR_TIME_ABS^MDC|1.0.0.x|20091028123702| | | |R||20091028173702+0000
+OBX|n+1|CWE|68219^MDC_TIME_CAP_STATE^MDC|1.0.0.x+1|(other set bits)~1^mds-time-capab-sync-abs-
+time(4)~1^mds-time-state-abs-time-synced(8)| | | |R
+OBX|n+2|CWE|68220^MDC_TIME_SYNC_PROTOCOL^MDC|1.0.0.x+2|532228^MDC_TIME_SYNC_SNTPV4330^MDC| | | |R
+OBX|n+3|NM|68221^MDC_TIME_SYNC_ACCURACY^MDC|1.0.0.x+3|1200000|264339^MDC_DIM_MICRO_SEC^MDC| | | |R
+```
+
+### D.1.5.7 Time synchronization examples
+
+#### D.1.5.7.1 Devices using absolute time
+
+This example sends a blood pressure observation (systolic, diastolic and mean arterial pressure) for a patient in Los Angeles taken at 09:10:05 on 8 January 2010 from a Personal Health Device which had an internal time of 14:03:45 1 January 1900 at 14:03:45 on 4 Jan 2010. In practice, for this situation to occur it requires that the sensor associate with the PHG at 14:03:45 on 4 January 2010 and remain associated with the PHG for four days before the measurement is taken at 09:10:05 on 8 January 2010. In addition, the sensor's clock is clearly uninitialized. The resulting PCD-01 message (with several required OBX elements not present for simplicity) is as follows:
+
+```
+MSH|^~\&|AcmeInc^ACDE48234567ABCD^EUI-64| | |20100108091005-
+0800|ORU^R01^ORU_ROI|MSGID1234|P|2.6||NE|AL| | |IHE PCD ORU-R01
+2006^HL7^2.16.840.1.113883.9.n.m^HL7
+PID||789567^^Imaginary Hospital^PI ||Doe^John^Joseph^^^L^A||M
+OBR|1|AB12345^AcmePHGInc^ACDE48234567ABCD^EUI-64|AB12345^AcmePHGInc^ACDE48234567ABCD^EUI-
+64|182777000^monitoring of patient^SNOMED-CT||20100108091005-0800
+Top level PHG OBX
+OBX|2|CWE|68220^MDC_TIME_SYNC_PROTOCOL^MDC|0.0.0.1|532224^MDC_TIME_SYNC_NONE^MDC| | | |R
+More PHG OBXes
+OBX|n||528391^MDC_DEV_SPEC_PROFILE_BP^MDC|1| | | |X| | | |0123456789ABCDEF^^0123456789ABCDEF^EUI-
+64
+More MDS OBXes
+OBX|n+1|DTM|67975^MDC_ATTR_TIME_ABS^MDC|1.0.0.x|19000101140345| | | |R||20100104140345-0800
+OBX|n+2||150020^MDC_PRESS_BLD_NONINV^MDC|1.0.1| | | |X||20100108091005-0800
+OBX|n+3|NM|150021^MDC_PRESS_BLD_NONINV_SYS^MDC|1.0.1.1|120|266016^MDC_DIM_MMHG^MDC| | | |R
+OBX|n+4|NM|150022^MDC_PRESS_BLD_NONINV_DIA^MDC|1.0.1.2|80|266016^MDC_DIM_MMHG^MDC| | | |R
+OBX|n+5|NM|150023^MDC_PRESS_BLD_NONINV_MEAN^MDC|1.0.1.3|100|266016^MDC_DIM_MMHG^MDC| | | |R
+```
+
+At the time of association the sensor's time is 14:03:45 1 January 1900. The actual time is 14:03:45 on 4 January 2010. The PHG notes that the sensor is using absolute time so it assumes that it is the local time of the current time zone where the PHG itself is located and that is Los Angeles. The PHG then computes the difference. Ideally that difference is zero. But in this case the sensor is 40,179 days, 19 hours, 55 minutes and 19 seconds behind. When the sensor takes a measurement some four days later (still associated with the PHG) where it is assumed the sensor's clock advances correctly, the PHG adds the 40,179 days, 19 hours, 55 minutes and 19 seconds to the sensor's newly reported time in the scan event report. This time is then expressed as a DTM timestamp 2010104140345-0800 where UTC is obtained by subtracting the offset – (–8 hours) to the field time 2010104140345 (effectively adding 8). Note that the timestamp is correct since the sensor's error has been compensated for.
+
+#### D.1.5.7.2 Sensors using a Bluetooth clock
+
+The example below shows a PHG that synchronized to an NTP V3 (IETF RFC 1305) time reference using a LAN or Services connection. The PHG also provides a synchronization clock for Bluetooth sensors using its Bluetooth clock and is represented as 64-bit high-resolution relative timestamps with a resolution of 1  $\mu$ sec. The PHG is also aware that the sensor is using this service to generate its [ISO/IEEE 11073-20601] relative timestamps\*. Since the PHG generates the underlying Bluetooth clock, it can correlate the high-resolution relative timestamps with an absolute timestamp if NTP or other reference time is available. The OBXes related to PHG timekeeping are shown below:
+
+```
+
+Top level PHG OBX
+OBX|n|CWE|68220^MDC_TIME_SYNC_PROTOCOL^MDC|0.0.0.x|532225^MDC_TIME_SYNC_NTPV3^MDC||||R
+OBX|n+1|NM|68221^MDC_TIME_SYNC_ACCURACY^MDC|0.0.0.x+1|0.18|264320^MDC_DIM_SEC^MDC||||R
+OBX|n+2|NM|67984^MDC_ATTR_TIME_STAMP_HI_RES^MDC|0.0.0.x+2|43567138204032|264339^MDC_DIM_MICRO_SEC^MD
+C||||R|||20091028123702.1362+0000|||ABCDEF123456^TIMEBASE_ID
+OBX|n+3|NM|68224^MDC_ATTR_TIME_REL^MDC|0.0.0.x+3|1.0|264339^MDC_DIM_MICRO_SEC^MDC||||R|||||BT_ABC
+DEF123456_01^TIMEBASE_ID
+More PHG OBXes
+
+```
+
+The sensor indicates that it uses Bluetooth timestamps, with a time synchronization accuracy of 10 µs, relative to the Bluetooth HDP hi-res timestamps, as shown below:
+
+NOTE – The sensor cannot indicate to the PHG that it uses Bluetooth timestamps using Continua defined Personal Health Device protocols. The information for OBX-18 must be obtained out of band.
+
+```
+
+OBX|m|528388^MDC_DEV_SPEC_PROFILE_PULS_OXIM^MDC|1|||||X|...
+OBX|m+1|CWE|68219^MDC_TIME_CAP_STATE^MDC|1.0.0.2||1^mds-time-capab-sync-hi-res-relative-time(6)~1^
+mds-time-state-hi-res-relative-time-synced(10)||||R
+OBX|m+2|CWE|68220^MDC_TIME_SYNC_PROTOCOL^MDC|1.0.0.3||532229^MDC_TIME_SYNC_BTV1^MDC||||R
+OBX|m+3|NM|68221^MDC_TIME_SYNC_ACCURACY^MDC|1.0.0.4|10|264339^MDC_DIM_MICRO_SEC^MDC||||R
+More MDS OBXes
+OBX|k|NM|150456^MDC_PULS_OXIM_SAT_O2^MDC|1.0.0.x|98|262688^MDC_DIM_PERCENT^MDC||||R
+OBX|k+1|NM|67984^MDC_ATTR_TIME_STAMP_HI_RES^MDC|1.0.0.x.1|132434|264339^MDC_DIM_MICRO_SEC^MDC||||R|
+|||||BT_ABCDEF123456_01^TIMEBASE_ID
+OBX|k+2|NM|150456^MDC_PULS_OXIM_SAT_O2^MDC|1.0.0.x+1|98.1|262688^MDC_DIM_PERCENT^MDC||||R
+OBX|k+3|NM|67984^MDC_ATTR_TIME_STAMP_HI_RES^MDC|1.0.0.x+1.1|232802|264339^MDC_DIM_MICRO_SEC^MDC||||
+R|||||BT_ABCDEF123456_01^TIMEBASE_ID
+
+```
+
+## D.1.6 Metric object attribute mappings overview
+
+The common metric attributes used to code the Metric OBX segments are shown in Table D.20. Attributes not included in the table are not encoded into OBX segments.
+
+**Table D.20 – Generic metric attributes**
+
+| Attribute               | Ref Id                       | Encoding Instructions                 |
+|-------------------------|------------------------------|---------------------------------------|
+| Type                    | MDC_ATTR_ID_TYPE             | OBX-3:clause D.1.3.1.1                |
+| Supplemental-Types      | MDC_ATTR_SUPPLEMENTAL_TYPES  | Facet:clause D.1.3.1.6.2              |
+| Measurement-Status      | MDC_ATTR_MSMT_STAT           | OBX-8:clauses D.1.3.1.4 and D.3.3.1   |
+| Metric-Id               | MDC_ATTR_ID_PHYSIO           | OBX-3:clause D.1.3.1.6                |
+| Metric-Id- List         | MDC_ATTR_ID_PHYSIO_LIST      | OBX-3:clause D.1.3.2.2                |
+| Metric-Id-Partition     | MDC_ATTR_METRIC_ID_PART      | Used by Metric-Id and Metric-Id-List. |
+| Unit-Code               | MDC_ATTR_UNIT_CODE           | OBX-6:clause D.1.3.1.2                |
+| Source-Handle-Reference | MDC_ATTR_SOURCE_HANDLE_REF   | Facet:clause D.1.3.1.6.1              |
+| Label-String            | MDC_ATTR_ID_LABEL_STRING     | OBX-3:clause D.1.3.1.1                |
+| Unit-LabelString        | MDC_ATTR_UNIT_LABEL_STRING   | OBX-6:clause D.1.3.1.2                |
+| Absolute-Time-Stamp     | MDC_ATTR_TIME_STAMP_ABS      | OBX-14:clause D.1.3.1.5               |
+| Base-Offset-Time-Stamp  | MDC_ATTR_TIME_STAMP_BO       | OBX-14:clause D.1.3.1.5               |
+| Relative-Time-Stamp     | MDC_ATTR_TIME_STAMP_REL      | Facet:clause D.1.3.1.6.6              |
+| HiRes-Time-Stamp        | MDC_ATTR_TIME_STAMP_HI_RES   | Facet:clause D.1.3.1.6.7              |
+| Measure-Active-Period   | MDC_ATTR_TIME_PD_MSMT_ACTIVE | Facet:clause D.1.3.1.6.4              |
+
+### D.1.7 Numeric (subclass of Metric)
+
+Attributes not shown in the table **are not** encoded into OBX segments.
+
+**Table D.21 – Numeric (subclass of metric)**
+
+| Attribute                         | Ref Id                         | Encoding instructions     |
+|-----------------------------------|--------------------------------|---------------------------|
+| Simple-Nu-Observed-Value          | MDC_ATTR_NU_VAL_OBS_SIMP       | Clause D.1.3.1.3.1        |
+| Compound-Simple-Nu-Observed-Value | MDC_ATTR_NU_CMPD_VAL_OBS_SIMP  | Clause D.1.3.2.2          |
+| Basic-Nu-Observed-Value           | MDC_ATTR_NU_VAL_OBS_BASIC      | Clause D.1.3.1.3.1        |
+| Compound-Basic-Nu-Observed-Value  | MDC_ATTR_NU_CMPD_VAL_OBS_BASIC | Clause D.1.3.2.2          |
+| Nu-Observed-Value                 | MDC_ATTR_NU_VAL_OBS            | Clause D.1.3.1.3.1        |
+| Compound-Nu-Observed-Value        | MDC_ATTR_NU_CMPD_VAL_OBS       | Clause D.1.3.2.3          |
+| Accuracy                          | MDC_ATTR_NU_ACCUR_MSMT         | Facet: clause D.1.3.1.6.5 |
+
+### D.1.8 RT-SA (subclass of Metric)
+
+Attributes not shown in the table **are not** encoded into OBX segments.
+
+**Table D.22 – RT-SA (subclass of metric)**
+
+| Attribute                | Ref Id                   | Encoding instructions    |
+|--------------------------|--------------------------|--------------------------|
+| Sample-Period            | MDC_ATTR_TIME_PD_SAMP    | Facet:clause D.1.3.1.6.8 |
+| Simple-Sa-Observed-Value | MDC_ATTR_SIMP_SA_OBS_VAL | Clause D.1.3.1.6.8       |
+| Sa-Specification         | MDC_ATTR_SA_SPECN        | Facet:clause D.1.3.1.6.9 |
+
+### D.1.9 Enumeration (subclass of Metric)
+
+Attributes not shown in the table **are not** encoded into OBX segments.
+
+**Table D.23 – Enumeration (subclass of metric)**
+
+| Attribute                          | Ref Id                              | Encoding instructions |
+|------------------------------------|-------------------------------------|-----------------------|
+| Enum-Observed-Value-Simple-OID     | MDC_ATTR_ENUM_OBS_VAL_SIMP_OID      | Clause D.1.3.1.3.2.2  |
+| Enum-Observed-Value-Simple-Bit-Str | MDC_ATTR_ENUM_OBS_VAL_SIMP_BIT_STR  | Clause D.1.3.1.3.2.1  |
+| Enum-Observed-Value-Basic-Bit-Str  | MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR | Clause D.1.3.1.3.2.1  |
+| Enum-Observed-Value-Simple-Str     | MDC_ATTR_ENUM_OBS_VAL_SIMP_STR      | Clause D.1.3.1.3.2.3  |
+| Enum-Observed-Value                | MDC_ATTR_VAL_ENUM_OBS               | Clause D.1.3.1.3.2.4  |
+
+## Annex E
+
+### Mapping from the IEEE 11073-104xx device specializations to the Continua services
+
+(This annex forms an integral part of this Recommendation.)
+
+The following clause gives guidance as to the recommended encoding of the OBX segments. This clause contains the specific guidance for the correct mapping of all devices. Additionally, it gives the hierarchy for the MDS object. The guidance for each device is composed of four elements:
+
+1. **Modelling.** This gives a brief description of the main modelling decisions.
+2. **Transformations.** This gives a list of all transformations to be done for the specific device.
+3. **Containment tree.** This shows the relationship of the individual observations to each other and the device. The hierarchical relationship is denoted by the "..." used in the REFID column. The number of dots indicate the place of that observation in the hierarchy.
+4. **OBX encoding**
+  - a) OBX encoding Part 1. This table shows the data type of the value, observation identifier, observation sub-type (hierarchy) and observation value. Note the actual entries in OBX-4 are not to be taken at face value since they will depend upon OBX segments that may come before those noted in table.
+  - b) OBX encoding Part 2. This table shows the observation units, equipment instance identifier and observation site.
+
+Examples of the primary observations and their encoding are given in the following subclauses.
+
+Table E.1 shows Continua-defined MDC codes that are not part of [ISO/IEEE 11073-20601] Personal Health Devices data exchanges.
+
+**Table E.1 – Continua-defined MDC codes that are not part of ISO/IEEE 11073-20601 Personal Health Devices data exchanges**
+
+| Partition      | Nomenclature code's common name          | Code |
+|----------------|------------------------------------------|------|
+| MDC_PART_OBJ   | MDC_REG_CERT_DATA_AUTH_BODY              | 2682 |
+| MDC_PART_INFRA | MDC_MOC_VMS_MDS_PHG                      | 7693 |
+| MDC_PART_INFRA | MDC_REG_CERT_DATA_CONTINUA_VERSION       | 8064 |
+| MDC_PART_INFRA | MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST | 8065 |
+| MDC_PART_INFRA | MDC_REG_CERT_DATA_CONTINUA_REG_STATUS    | 8066 |
+| MDC_PART_INFRA | MDC_REG_CERT_DATA_CONTINUA_PHG_CERT_LIST | 8067 |
+
+It should be noted that:
+
+The hierarchical notation shown in the OBX-4 column is example only. Particularly for the metric level and lower, they are illustrative only to show the notational level and specific numbers can vary from message to message, as long as the relationships are maintained.
+
+Additionally, the values in columns OBX-5, OBX-18 and OBX-20 are only examples.
+
+## E.1 PHG
+
+### E.1.1 Modelling
+
+The PHG-OBXes are modelled from a hypothetical MDS object on the PHG as described in clause D.1.1.
+
+### E.1.2 Containment tree
+
+Table E.2 shows a PHG containment tree.
+
+**Table E.2 – PHG containment tree**
+
+| REFID                                         | Description                                                                                                                                                            |
+|-----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ... MDC_ATTR_TIME_REL                         | Relative-Time                                                                                                                                                          |
+| ... MDC_ATTR_TIME_REL_HI_RES                  | HiRes-Relative-Time                                                                                                                                                    |
+| ... MDC_TIME_SYNC_PROTOCOL                    | Time-Sync-Protocol<br>(hypothetical decomposition of MDC_ATTR_MDS_TIME_INFO)                                                                                           |
+| ... MDC_TIME_SYNC_ACCURACY                    | Time-Sync-Accuracy<br>(hypothetical decomposition of MDC_ATTR_MDS_TIME_INFO)                                                                                           |
+| ... MDC_TIME_RES_ABS                          | Time-Resolution-Abs-Time<br>(hypothetical decomposition of MDC_ATTR_MDS_TIME_INFO)                                                                                     |
+| ... MDC_TIME_RES_REL                          | Time-Resolution-Rel-Time<br>(hypothetical decomposition of MDC_ATTR_MDS_TIME_INFO)                                                                                     |
+| ... MDC_TIME_RES_REL_HI_RES                   | Time-Resolution-High-Res-Time<br>(hypothetical decomposition of MDC_ATTR_MDS_TIME_INFO)                                                                                |
+| ... MDC_REG_CERT_DATA_AUTH_BODY               | Regulation-Certification-Auth-Body<br>(hypothetical decomposition of MDC_ATTR_REG-CERT-DATA-LIST Authority Body sub element)                                           |
+| .... MDC_REG_CERT_DATA_CONTINUA_VERSION       | Regulation-Certification-Continua-Version<br>(hypothetical decomposition of MDC_ATTR_REG-CERT-DATA-LIST Continua Body Certified Device Version sub element)            |
+| .... MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST | Regulation-Certification-Continua-Certified-Device-List<br>(hypothetical decomposition of MDC_ATTR_REG-CERT-DATA-LIST Continua Body Certified Device List sub element) |
+| ... MDC_REG_CERT_DATA_AUTH_BODY               | Regulation-Certification-Auth-Body<br>(hypothetical decomposition of MDC_ATTR_REG-CERT-DATA-LIST Authority Body sub element)                                           |
+
+**Table E.2 – PHG containment tree**
+
+| REFID                                            | Description                                                                                                                                                 |
+|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| .... MDC_REG_CERT_DATA_CONTINUA_REG_STATUS       | Regulation-Certification-Continua-Regulation-Status (hypothetical decomposition of MDC_ATTR_REG-CERT-DATA-LIST Continua Body Regulation Status sub element) |
+| ... MDC_REG_CERT_DATA_AUTH_BODY                  | Regulation-Certification-Auth-Body (hypothetical decomposition of MDC_ATTR_REG-CERT-DATA-LIST Authority Body sub element)                                   |
+| .... MDC_REG_CERT_DATA_CONTINUA<br>PHG_CERT_LIST | Regulation-Certification-Continua-PHG-Cert-List                                                                                                             |
+
+## E.2 MDS object
+
+### E.2.1 Modelling
+
+All attributes are metrics of the MDS object.
+
+### E.2.2 Containment tree
+
+Table E.3 shows an MDS containment tree.
+
+**Table E.3 – MDS containment tree**
+
+| REFID                                    | Description                                                                    |
+|------------------------------------------|--------------------------------------------------------------------------------|
+| MDC_DEV_SPEC_PROFILE_*                   | Specific device MDS                                                            |
+| ... MDC_ATTR_SYS_TYPE                    | System-Type                                                                    |
+| ... MDC_ATTR_ID_FIELD_MODEL_NUMBER       | System-Model (decomposition of MDC_ATTR_ID_MODEL attribute)                    |
+| ... MDC_ATTR_ID_FIELD_MODEL_MANUFACTURER | System-Manufacturer (decomposition of MDC_ATTR_ID_MODEL attribute)             |
+| ... MDC_ATTR_SYS_ID                      | System-Id                                                                      |
+| ... MDC_ID_PROD_SPEC_UNSPECIFIED         | Production-Specification-Unspecified (decomposition of MDC_ATTR_ID_PROD_SPECN) |
+| ... MDC_ID_PROD_SPEC_SERIAL              | Production-Specification-Serial (decomposition of MDC_ATTR_ID_PROD_SPECN)      |
+| ... MDC_ID_PROD_SPEC_PART                | Production-Specification-Part (decomposition of MDC_ATTR_ID_PROD_SPECN)        |
+| ... MDC_ID_PROD_SPEC_HW                  | Production-Specification-Hardware (decomposition of MDC_ATTR_ID_PROD_SPECN)    |
+| ... MDC_ID_PROD_SPEC_SW                  | Production-Specification-Software (decomposition of MDC_ATTR_ID_PROD_SPECN)    |
+
+**Table E.3 – MDS containment tree**
+
+| <b>REFID</b>                            | <b>Description</b>                                                                                                                                        |
+|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ... MDC_ID_PROD_SPEC_FW                 | Production-Specification-Firmware<br>(decomposition of<br>MDC_ATTR_ID_PROD_SPECN)                                                                         |
+| ... MDC_ID_PROD_SPEC_PROTOCOL           | Production-Specification-Protocol<br>(decomposition of<br>MDC_ATTR_ID_PROD_SPECN)                                                                         |
+| ... MDC_ID_PROD_SPEC_GMDN               | Production-Specification-GMDN<br>(decomposition of<br>MDC_ATTR_ID_PROD_SPECN)                                                                             |
+| ... MDC_ATTR_TIME_ABS                   | Date-and-Time                                                                                                                                             |
+| ... MDC_ATTR_TIME_REL                   | Relative-Time                                                                                                                                             |
+| ... MDC_ATTR_TIME_REL_HI_RES            | HiRes-Relative-Time                                                                                                                                       |
+| ... MDC_TIME_CAP_STATE                  | Mds-Time-Cap-State<br>(decomposition of<br>MDC_ATTR_MDS_TIME_INFO)                                                                                        |
+| ... MDC_TIME_SYNC_PROTOCOL              | Time-Sync-Protocol<br>(decomposition of<br>MDC_ATTR_MDS_TIME_INFO)                                                                                        |
+| ... MDC_TIME_SYNC_ACCURACY              | Time-Sync-Accuracy<br>(decomposition of<br>MDC_ATTR_MDS_TIME_INFO)                                                                                        |
+| ... MDC_TIME_RES_ABS                    | Time-Resolution-Abs-Time<br>(decomposition of<br>MDC_ATTR_MDS_TIME_INFO)                                                                                  |
+| ... MDC_TIME_RES_REL                    | Time-Resolution-Rel-Time<br>(decomposition of<br>MDC_ATTR_MDS_TIME_INFO)                                                                                  |
+| ... MDC_TIME_RES_REL_HI_RES             | Time-Resolution-High-Res-Time<br>(decomposition of<br>MDC_ATTR_MDS_TIME_INFO)                                                                             |
+| ... MDC_ATTR_POWER_STAT                 | Power-Status                                                                                                                                              |
+| ... MDC_ATTR_VAL_BATT_CHARGE            | Battery-Level                                                                                                                                             |
+| ... MDC_ATTR_TIME_BATT_REMAIN           | Remaining-Battery-Time                                                                                                                                    |
+| ... MDC_REG_CERT_DATA_AUTH_BODY         | Regulation-Certification-Auth-Body<br>(decomposition of MDC_ATTR_REG-<br>CERT-DATA-LIST Authority Body sub<br>element)                                    |
+| .... MDC_REG_CERT_DATA_CONTINUA_VERSION | Regulation-Certification-Continua-<br>Version (decomposition of MDC_<br>ATTR_REG-CERT-DATA-LIST<br>Continua Body Certified Device Version<br>sub element) |
+
+**Table E.3 – MDS containment tree**
+
+| REFID                                         | Description                                                                                                                                            |
+|-----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
+| .... MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST | Regulation-Certification-Continua-Certified-Device-List (decomposition of MDC_ATTR_REG-CERT-DATA-LIST Continua Body Certified Device List sub element) |
+| ... MDC_REG_CERT_DATA_AUTH_BODY               | Regulation-Certification-Auth-Body (decomposition of MDC_ATTR_REG-CERT-DATA-LIST Authority Body sub element)                                           |
+| .... MDC_REG_CERT_DATA_CONTINUA_REG_STATUS    | Regulation-Certification-Continua-Regulation-Status (decomposition of MDC_ATTR_REG-CERT-DATA-LIST Continua Body Regulation Status sub element)         |
+| ... MDC_ATTR_SYS_TYPE_SPEC_LIST               | System-Type-Spec-List                                                                                                                                  |
+
+### E.3 Metric OBXes
+
+The following tables give the containment tree and detailed models of the Metric-OBXes for each of the specializations. Note that the absolute values of the OBX-4 containment values in the tables are illustrative only. Their purpose is to show instances and scope. OBX-8, OBX-11, OBX-14 and OBX-20 are also not shown in these tables. These entries depend upon the measurement status attribute or the occurrence of a special value (for example, NaN), the particular time scenario and the use of the supplemental types attribute. Their inclusion would add too much complexity to the tables.
+
+#### E.3.1 10404 Pulse oximeter
+
+##### E.3.1.1 Modelling
+
+This is modelled with the measurements as individual METRIC level observations.
+
+##### E.3.1.2 Transformations
+
+The following transformations are performed in the encoding of this device.
+
+##### E.3.1.3 Containment tree
+
+Table E.4 shows a pulse oximeter containment tree.
+
+**Table E.4 – Pulse oximeter containment tree**
+
+| REFID                            | Description                                                          |
+|----------------------------------|----------------------------------------------------------------------|
+| MDC_DEV_SPEC_PROFILE_PULS_OXIM   | Pulse oximeter MDS                                                   |
+| ... MDC_PULS_OXIM_SAT_O2         | SPO <sub>2</sub>                                                     |
+| .... MDC_ATTR_SUPPLEMENTAL_TYPES | SPO <sub>2</sub> Modality sent as a Supplemental-Type to the reading |
+| .... MDC_ATTR_NU_ACCUR_MSMT      | SPO <sub>2</sub> Accuracy                                            |
+| .... MDC_ATTR_AL_OP_STAT         | SPO <sub>2</sub> Alert-Op-State                                      |
+
+**Table E.4 – Pulse oximeter containment tree**
+
+| <b>REFID</b>                                         | <b>Description</b>                                                                                                    |
+|------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|
+| .... MDC_ATTR_LIMIT_CURR                             | SPO <sub>2</sub> Current-Limits                                                                                       |
+| .... MDC_ATTR_AL_OP_TEXT_STRING                      | SPO <sub>2</sub> Alert-Op-Text-String                                                                                 |
+| ... MDC_ATTR_MSMT_STAT                               | SPO <sub>2</sub> Measurement-Status special cases                                                                     |
+| ... MDC_PULS_OXIM_PULS_RATE                          | Pulse rate                                                                                                            |
+| .... MDC_ATTR_SUPPLEMENTAL_TYPES                     | Pulse rate modality sent as a Supplemental-Type to the reading                                                        |
+| .... MDC_ATTR_NU_ACCUR_MSMT                          | Pulse rate accuracy                                                                                                   |
+| ... MDC_PULS_OXIM_PERF_REL or<br>... MDC_SAT_O2_QUAL | Pulsatile quality                                                                                                     |
+| ... MDC_PULS_OXIM_PLETHM                             | Plethysmographic waveform                                                                                             |
+| .... MDC_ATTR_TIME_PD_SAMP                           | Plethysmographic waveform sample period                                                                               |
+| ... MDC_TRIG                                         | Pulsatile occurrence                                                                                                  |
+| .... MDC_ATTR_SOURCE_HANDLE_REF                      | Source-Handle-Reference<br>point to either the Pulsatile quality numeric object<br>or the Plethysmogram RT-SA object. |
+| ... MDC_PULS_OXIM_PULS_CHAR                          | Pulsatile characteristic                                                                                              |
+| .... MDC_ATTR_SOURCE_HANDLE_REF                      | Source-Handle-Reference<br>point to either the Pulse amplitude numeric object<br>or the Plethysmogram RT-SA object    |
+| ... MDC_PULS_OXIM_DEV_STATUS                         | Device and sensor annunciation Status                                                                                 |
+
+### E.3.1.4 OBX encoding
+
+Table E.5 and Table E.6 show part 1 and part 2 (respectively) of the pulse oximeter OBX encoding.
+
+**Table E.5 – Pulse oximeter OBX encoding – Part 1**
+
+| <b>Description</b>                    | <b>OBX-2</b> | <b>OBX-3</b>                              | <b>OBX-4</b> | <b>OBX-5</b>                                                                                                                                                              |
+|---------------------------------------|--------------|-------------------------------------------|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Pulse oximeter MDS                    |              | 528388^MDC_DEV_SPEC_PROFILE_PULS_OXIM^MDC | 1            |                                                                                                                                                                           |
+| SPO <sub>2</sub>                      | NM           | 150456^MDC_PULS_OXIM_SAT_O2^MDC           | 1.0.0.1      | 93.4                                                                                                                                                                      |
+| SPO <sub>2</sub> Modality             | CWE          | 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC     | 1.0.0.1.1    | 150580^MDC_MODALITY_FAST^MDC or<br>150584^MDC_MODALITY_SLOW^MDC or<br>150588^MDC_MODALITY_SPOT^MDC                                                                        |
+| SPO <sub>2</sub> Accuracy             | NM           | 67914^MDC_ATTR_NU_ACCUR_MSMT^MDC          | 1.0.0.1.2    | 2.3                                                                                                                                                                       |
+| SPO <sub>2</sub> Alert-Op-State       | CWE          | 67846^MDC_ATTR_AL_OP_STAT^MDC             | 1.0.0.1.3    | One of the values...<br><0 or 1>^lim-alert-off(0),<br><0 or 1>^lim-low-off(1), or<br><0 or 1>^lim-high-off(2)                                                             |
+| SPO <sub>2</sub> Current-Limits       | NM           | 67892^MDC_ATTR_LIMIT_CURR^MDC             | 1.0.0.1.4    | This is coded as a tuple of 2 numeric values with a "~" separating the values.<br><lower limit (NM)> ~ <upper limit (NM)><br>Example:<br>75.2~85.2                        |
+| SPO <sub>2</sub> Alert-Op-Text-String | ST           | 68014^MDC_ATTR_AL_OP_TEXT_STRING^MDC      | 1.0.0.1.5    | This is coded as a tuple of 2 string values with a "~" separating the values.<br><lower limit text (ST)> ~ <upper limit text (ST)><br>Example:<br>lower limit~upper limit |
+
+**Table E.5 – Pulse oximeter OBX encoding – Part 1**
+
+| <b>Description</b>                                                       | <b>OBX-2</b> | <b>OBX-3</b>                                                       | <b>OBX-4</b> | <b>OBX-5</b>                                                                                                                                                                  |
+|--------------------------------------------------------------------------|--------------|--------------------------------------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| SPO <sub>2</sub> Measurement-Status<br>(Pulse Oximeter special settings) | CWE          | 67911^MDC_ATTR_MSMT_STAT^MDC                                       | 1.0.0.1.6    | One of the values...<br><0 or 1>^msmt-state-in-alarm(14),<br><0 or 1>^msmt-state-al-inhibited(15)                                                                             |
+| Pulse rate                                                               | NM           | 149530^MDC_PULS_OXIM_PULS_RATE^MDC                                 | 1.0.0.2      | 71                                                                                                                                                                            |
+| Pulse rate modality                                                      | CWE          | 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC                              | 1.0.0.2.1    | 150580^MDC_MODALITY_FAST^MDC or<br>150584^MDC_MODALITY_SLOW^MDC or<br>150588^MDC_MODALITY_SPOT^MDC                                                                            |
+| Pulse rate accuracy                                                      | NM           | 67914^MDC_ATTR_NU_ACCUR_MSMT^MDC                                   | 1.0.0.2.2    | 1.3                                                                                                                                                                           |
+| Pulsatile quality                                                        | NM           | 150448^MDC_PULS_OXIM_PERF_REL^MDC or<br>150320^MDC_SAT_O2_QUAL^MDC | 1.0.0.3      | 85.3                                                                                                                                                                          |
+| Plethysmographic waveform                                                | NA           | 150452^MDC_PULS_OXIM_PLETH^MDC                                     | 1.0.0.4      | 11^22^33^44^55^66^77^88^99^...<br>Note that the actual values of the waveform may need to be computed based on the scaling values in the Scale-And-Range-Specification object |
+| Plethysmographic waveform sample period                                  | NM           | 67981^MDC_ATTR_TIME_PD_SAMP^MDC                                    | 1.0.0.4.1    | 4000                                                                                                                                                                          |
+| Pulsatile occurrence                                                     | CWE          | 184322^MDC_TRIG^MDC                                                | 1.0.0.5      | 184323^MDC_TRIG_BEAT^MDC or<br>184331^MDC_TRIG_BEAT_MAX_INRUSH^MDC or<br>192511^MDC_METRIC_NOS^MDC                                                                            |
+| Source-Handle-Reference                                                  | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC                               | 1.0.0.7.1    | 1.0.0.4                                                                                                                                                                       |
+| Pulsatile characteristic                                                 | CWE          | 150584^MDC_PULS_OXIM_PULS_CHAR^MDC                                 | 1.0.0.6      | One of the values...<br><0 or 1>^pulse-qual-nominal(0),<br><0 or 1>^pulse-qual-marginal(1),<br><0 or 1>^pulse-qual-minimal(2),<br><0 or 1>^pulse-qual-unacceptable(3)         |
+
+**Table E.5 – Pulse oximeter OBX encoding – Part 1**
+
+| <b>Description</b>                    | <b>OBX-2</b> | <b>OBX-3</b>                        | <b>OBX-4</b> | <b>OBX-5</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------------------|--------------|-------------------------------------|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Device and sensor annunciation status | CWE          | 150604^MDC_PULS_OXIM_DEV_STATUS^MDC | 1.0.0.7      | One of the values...<br><0 or 1>^sensor-disconnected(0),<br><0 or 1>^sensor-malfunction(1),<br><0 or 1>^sensor-displaced(2),<br><0 or 1>^sensor-unsupported(3),<br><0 or 1>^sensor-off(4),<br><0 or 1>^sensor-interference(5),<br><0 or 1>^signal-searching(6),<br><0 or 1>^signal-pulse-questionable(7),<br><0 or 1>^signal-non-pulsatile(8),<br><0 or 1>^signal-erratic(9),<br><0 or 1>^signal-low-perfusion(10),<br><0 or 1>^signal-poor(11),<br><0 or 1>^signal-inadequate(12),<br><0 or 1>^signal-processing-irregularity(13),<br><0 or 1>^device-equipment-malfunction(14),<br><0 or 1>^device-extended-update(15) |
+
+**Table E.6 – Pulse oximeter OBX encoding – Part 2**
+
+| <b>Description</b>                      | <b>OBX-6</b>                                                                                                                                              | <b>OBX-18</b>                             | <b>OBX-20</b> |
+|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|---------------|
+| Pulse oximeter MDS                      |                                                                                                                                                           | 0123456789ABCDEF^^0123456789ABCDEF^EUI-64 |               |
+| SPO <sub>2</sub>                        | 262688^MDC_DIM_PERCENT^MDC                                                                                                                                |                                           |               |
+| SPO <sub>2</sub> Modality               |                                                                                                                                                           |                                           |               |
+| SPO <sub>2</sub> Accuracy               | 262688^MDC_DIM_PERCENT^MDC                                                                                                                                |                                           |               |
+| SPO <sub>2</sub> Alert-Op-State         | 262688^MDC_DIM_PERCENT^MDC                                                                                                                                |                                           |               |
+| SPO <sub>2</sub> Current-Limits         | 262688^MDC_DIM_PERCENT^MDC                                                                                                                                |                                           |               |
+| SPO <sub>2</sub> Alert-Op-Text-String   |                                                                                                                                                           |                                           |               |
+| SPO <sub>2</sub> Measurement-Status     |                                                                                                                                                           |                                           |               |
+| Pulse rate                              | 264864^MDC_DIM_BEAT_PER_MIN^MDC                                                                                                                           |                                           |               |
+| Pulse rate modality                     |                                                                                                                                                           |                                           |               |
+| Pulse rate accuracy                     | 264864^MDC_DIM_BEAT_PER_MIN^MDC                                                                                                                           |                                           |               |
+| Pulsatile quality                       | 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 |                                           |               |
+| Plethysmographic waveform               | 262656^MDC_DIM_DIMLESS^MDC or 268738^MDC_DIM_MICRO_ABSORBANCE^MDC                                                                                         |                                           |               |
+| Plethysmographic waveform sample period | 264339^MDC_DIM_MICRO_SEC^MDC                                                                                                                              |                                           |               |
+| Pulsatile occurrence                    |                                                                                                                                                           |                                           |               |
+| Source-Handle-Reference                 |                                                                                                                                                           |                                           |               |
+| Pulsatile characteristic                |                                                                                                                                                           |                                           |               |
+| Source-Handle-Reference                 |                                                                                                                                                           |                                           |               |
+| Device and sensor annunciation status   |                                                                                                                                                           |                                           |               |
+
+### E.3.2 10407 Blood pressure monitor
+
+#### E.3.2.1 Modelling
+
+There is one channel/group to hold all the metric level measurements. This specialization uses compound numeric attributes and the containment Metric-OBX is placed on the channel n-tuple.
+
+#### E.3.2.2 Transformations
+
+The following transformations are performed in the encoding of this device.
+
+#### E.3.2.3 Containment tree
+
+Table E.7 shows a blood pressure monitor containment tree.
+
+**Table E.7 – Blood pressure monitor containment tree**
+
+| REFID                         | Description            |
+|-------------------------------|------------------------|
+| MDC_DEV_SPEC_PROFILE_BP       | Blood pressure MDS     |
+| .. MDC_PRESS_BLD_NONINV       | Systolic/Diastolic/MAP |
+| ... MDC_PRESS_BLD_NONINV_SYS  | Systolic               |
+| ... MDC_PRESS_BLD_NONINV_DIA  | Diastolic              |
+| ... MDC_PRESS_BLD_NONINV_MEAN | Mean arterial pressure |
+| ... MDC_PULS_RATE_NON_INV     | Pulse rate             |
+
+### E.3.2.5 OBX encoding
+
+Table E.8 and Table E.9 show part 1 and part 2 (respectively) of a blood pressure monitor encoding.
+
+**Table E.8 – Blood pressure monitor encoding – Part 1**
+
+| Description            | OBX-2 | OBX-3                                | OBX-4   | OBX-5 |
+|------------------------|-------|--------------------------------------|---------|-------|
+| Blood pressure MDS     |       | 528391^MDC_DEV_SPEC_PROFILE_BP^MDC   | 1       |       |
+| Systolic/Diastolic/MAP |       | 150020^MDC_PRESS_BLD_NONINV^MDC      | 1.0.1   |       |
+| Systolic               | NM    | 150021^MDC_PRESS_BLD_NONINV_SYS^MDC  | 1.0.1.1 | 123.0 |
+| Diastolic              | NM    | 150022^MDC_PRESS_BLD_NONINV_DIA^MDC  | 1.0.1.2 | 85.0  |
+| Mean arterial pressure | NM    | 150023^MDC_PRESS_BLD_NONINV_MEAN^MDC | 1.0.1.3 | 103.0 |
+| Pulse rate             | NM    | 149546^MDC_PULS_RATE_NON_INV^MDC     | 1.0.0.1 | 73    |
+
+**Table E.9 – Blood pressure monitor encoding – Part 2**
+
+| Description            | OBX-6                                                     | OBX-18                                    | OBX-20 |
+|------------------------|-----------------------------------------------------------|-------------------------------------------|--------|
+| Blood pressure MDS     |                                                           | 0123456789ABCDEF^^0123456789ABCDEF^EUI-64 |        |
+| Systolic/Diastolic/MAP |                                                           |                                           |        |
+| Systolic               | 266016^MDC_DIM_MMHG^MDC or 265987^MDC_DIM_KILO_PASCAL^MDC |                                           |        |
+| Diastolic              | 266016^MDC_DIM_MMHG^MDC or 265987^MDC_DIM_KILO_PASCAL^MDC |                                           |        |
+| Mean arterial pressure | 266016^MDC_DIM_MMHG^MDC or 265987^MDC_DIM_KILO_PASCAL^MDC |                                           |        |
+| Pulse rate             | 264864^MDC_DIM_BEAT_PER_MIN^MDC                           |                                           |        |
+
+### E.3.3 10408 Thermometer
+
+#### E.3.3.1 Modelling
+
+The single attribute is modelled as a metric of the thermometer object.
+
+#### E.3.3.2 Transformations
+
+The following transformations are performed in the encoding of this device.
+
+#### E.3.3.3 Containment tree
+
+Table E.10 shows a thermometer containment tree.
+
+**Table E.10 – Thermometer containment tree**
+
+| REFID                                                                                                                                                                                                              | Description     |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|
+| MDC_DEV_SPEC_PROFILE_TEMP                                                                                                                                                                                          | Thermometer MDS |
+| ... MDC_TEMP_AXILLA or<br>... MDC_TEMP_BODY or<br>... MDC_TEMP_EAR or<br>... MDC_TEMP_FINGER or<br>... MDC_TEMP_GIT or<br>... MDC_TEMP_ORAL or<br>... MDC_TEMP_RECT or<br>... MDC_TEMP_TOE or<br>... MDC_TEMP_TYMP | Temperature     |
+
+### E.3.3.5 OBX encoding
+
+Table E.11 and Table E.12 show part 1 and part 2 of a thermometer encoding.
+
+**Table E.11 – Thermometer encoding – Part 1**
+
+| Description     | OBX-2 | OBX-3                                                                                                                                                                                                                                                                             | OBX-4   | OBX-5 |
+|-----------------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------|
+| Thermometer MDS |       | 528392^MDC_DEV_SPEC_PROFILE_TEMP^MDC                                                                                                                                                                                                                                              | 1       |       |
+| Temperature     | NM    | 188452^MDC_TEMP_AXILLA^MDC or<br>150364^MDC_TEMP_BODY^MDC or<br>188428^MDC_TEMP_EAR^MDC or<br>188432^MDC_TEMP_FINGER^MDC or<br>188456^MDC_TEMP_GIT^MDC or<br>188424^MDC_TEMP_ORAL^MDC or<br>188420^MDC_TEMP_RECT^MDC or<br>188448^MDC_TEMP_TOE^MDC or<br>150392^MDC_TEMP_TYMP^MDC | 1.0.0.1 | 98.6  |
+
+**Table E.12 – Thermometer encoding – Part 2**
+
+| Description     | OBX-6                                                 | OBX-18                                        | OBX-20 |
+|-----------------|-------------------------------------------------------|-----------------------------------------------|--------|
+| Thermometer MDS |                                                       | 0123456789ABCDEF^^0123456789<br>ABCDEF^EUI-64 |        |
+| Temperature     | 268192^MDC_DIM_DEGC^MDC or<br>266560^MDC_DIM_FAHR^MDC |                                               |        |
+
+## E.3.4 10415 Weighing scales
+
+### E.3.4.1 Modelling
+
+All attributes are metrics of the weighing scales object.
+
+### E.3.4.2 Transformations
+
+The following transformations are performed in the encoding of this device specialization.
+
+### E.3.4.3 Containment tree
+
+Table E.13 shows a weighing scales containment tree.
+
+**Table E.13 – Weighing scales containment tree**
+
+| REFID                          | Description                                                           |
+|--------------------------------|-----------------------------------------------------------------------|
+| MDC_DEV_SPEC_PROFILE_SCALE     | Weighing scales MDS                                                   |
+| ... MDC_MASS_BODY_ACTUAL       | Body weight                                                           |
+| ... MDC_LEN_BODY_ACTUAL        | Body height                                                           |
+| ... MDC_RATIO_MASS_BODY_LEN_SQ | Body Mass Index                                                       |
+| .... MDC_SOURCE_HANDLE_REF     | Source-Handle-Reference<br>Reference to the corresponding body weight |
+
+### E.3.4.4 OBX encoding
+
+Table E.14 and Table E.15 show part 1 and part 2 (respectively) of a weighing scales encoding.
+
+**Table E.14 – Weighing scales encoding – Part 1**
+
+| Description             | OBX-2 | OBX-3                                 | OBX-4     | OBX-5   |
+|-------------------------|-------|---------------------------------------|-----------|---------|
+| Weighing scales MDS     |       | 528399^MDC_DEV_SPEC_PROFILE_SCALE^MDC | 1         |         |
+| Body weight             | NM    | 188736^MDC_MASS_BODY_ACTUAL^MDC       | 1.0.0.1   | 155.4   |
+| Body height             | NM    | 188740^MDC_LEN_BODY_ACTUAL^MDC        | 1.0.0.2   |         |
+| Body Mass Index         | NM    | 188752^MDC_RATIO_MASS_BODY_LEN_SQ^MDC | 1.0.0.3   | 25.3    |
+| Source-Handle-Reference | ST    | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC  | 1.0.0.3.1 | 1.0.0.1 |
+
+**Table E.15 – Weighing scales encoding – Part 2**
+
+| <b>Description</b>      | <b>OBX-6</b>                                             | <b>OBX-18</b>                             | <b>OBX-20</b> |
+|-------------------------|----------------------------------------------------------|-------------------------------------------|---------------|
+| Weighing scales MDS     |                                                          | 0123456789ABCDEF^^0123456789ABCDEF^EUI-64 |               |
+| Body weight             | 263875^MDC_DIM_KILO_G^MDC                                |                                           |               |
+| Body height             | 263441^MDC_DIM_CENTI_M^MDC or<br>263520^MDC_DIM_INCH^MDC |                                           |               |
+| Body Mass Index         | 264096^MDC_DIM_KG_PER_M_SQ^MDC                           |                                           |               |
+| Source-Handle-Reference |                                                          |                                           |               |
+
+### E.3.5 10417 Glucose meter
+
+#### E.3.5.1 Modelling
+
+The glucose meter object model consists largely of two key observation types, blood glucose and HbA1c. Contextual objects which may provide additional information to these values **may** be linked to a particular source observation through a Source-Handle-Reference FACET-level OBX.
+
+#### E.3.5.2 Transformations
+
+The following transformations are performed in the encoding of this device.
+
+Several nomenclature codes have been harmonized with the underlying base codes. These are pointed out in the tables below.
+
+#### E.3.5.3 Containment tree
+
+Table E.16 shows a glucose meter containment tree.
+
+**Table E.16 – Glucose meter containment tree**
+
+| <b>REFID</b>                                                                                                              | <b>Description</b> |
+|---------------------------------------------------------------------------------------------------------------------------|--------------------|
+| MDC_DEV_SPEC_PROFILE_GLUCOSE                                                                                              | Glucose meter MDS  |
+| ... MDC_CONC_GLU_CAPILLARY_WHOLEBLOOD or<br>... MDC_CONC_GLU_CAPILLARY_PLASMA or<br>... MDC_CONC_GLU_VENOUS_WHOLEBLOOD or | Blood glucose      |
+
+**Table E.16 – Glucose meter containment tree**
+
+| <b>REFID</b>                                                                                                                                                                                                                                                                                                   | <b>Description</b>                                                            |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|
+| ... MDC_CONC_GLU_VENOUS_PLASMA or<br>... MDC_CONC_GLU_ARTERIAL_WHOLEBLOOD or<br>... MDC_CONC_GLU_ARTERIAL_PLASMA or<br>... MDC_CONC_GLU_UNDETERMINED_WHOLEBLOOD or<br>... MDC_CONC_GLU_UNDETERMINED_PLASMA or<br>... MDC_CONC_GLU_ISF                                                                          |                                                                               |
+| ... MDC_CONC_GLU_CONTROL                                                                                                                                                                                                                                                                                       | Control solution                                                              |
+| ... MDC_CTXT_GLU_EXERCISE                                                                                                                                                                                                                                                                                      | Context exercise                                                              |
+| ... MDC_ATTR_TIME_PD_MSMT_ACTIVE                                                                                                                                                                                                                                                                               | Measure active period                                                         |
+| ... MDC_SOURCE_HANDLE_REF                                                                                                                                                                                                                                                                                      | Source-Handle-Reference<br>Reference to the corresponding glucose measurement |
+| ... MDC_CTXT_MEDICATION is the generic code or<br>if specific Metric-Id is specified use it...<br>... MDC_CTXT_MEDICATION_RAPIDACTING or<br>... MDC_CTXT_MEDICATION_SHORTACTING or<br>... MDC_CTXT_MEDICATION_INTERMEDIATEACTING or<br>... MDC_CTXT_MEDICATION_LONGACTING or<br>... MDC_CTXT_MEDICATION_PREMIX | Context medication                                                            |
+| ... MDC_SOURCE_HANDLE_REF                                                                                                                                                                                                                                                                                      | Source-Handle-Reference<br>Reference to the corresponding glucose measurement |
+| ... MDC_CTXT_GLU_CARB is the generic code or<br>if specific Metric-Id is specified use it...<br>... MDC_CTXT_GLU_CARB_BREAKFAST or<br>... MDC_CTXT_GLU_CARB_LUNCH or<br>... MDC_CTXT_GLU_CARB_DINNER or<br>... MDC_CTXT_GLU_CARB_SNACK or                                                                      | Context carbohydrates                                                         |
+
+**Table E.16 – Glucose meter containment tree**
+
+| <b>REFID</b>                                                                                      | <b>Description</b>                                                            |
+|---------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|
+| ... MDC_CTXT_GLU_CARB_DRINK or<br>... MDC_CTXT_GLU_CARB_SUPPER or<br>... MDC_CTXT_GLU_CARB_BRUNCH |                                                                               |
+| .... MDC_SOURCE_HANDLE_REF                                                                        | Source-Handle-Reference<br>Reference to the corresponding glucose measurement |
+| ... MDC_GLU_METER_DEV_STATUS                                                                      | Device and sensor annunciation status                                         |
+| ... MDC_CTXT_GLU_MEAL                                                                             | Context meal                                                                  |
+| .... MDC_SOURCE_HANDLE_REF                                                                        | Source-Handle-Reference<br>Reference to the corresponding glucose measurement |
+| ... MDC_CTXT_GLU_SAMPLELOCATION                                                                   | Context sample location                                                       |
+| .... MDC_SOURCE_HANDLE_REF                                                                        | Source-Handle-Reference<br>Reference to the corresponding glucose measurement |
+| ... MDC_CTXT_GLU_TESTER                                                                           | Context tester                                                                |
+| .... MDC_SOURCE_HANDLE_REF                                                                        | Source-Handle-Reference<br>Reference to the corresponding glucose measurement |
+| ... MDC_CTXT_GLU_HEALTH                                                                           | Context health                                                                |
+| .... MDC_SOURCE_HANDLE_REF                                                                        | Source-Handle-Reference<br>Reference to the corresponding glucose measurement |
+| ... MDC_CONC_HBA1C                                                                                | HbA1c                                                                         |
+
+### E.3.5.4 OBX encoding
+
+Table E.17 and Table E.18 show part 1 and part 2 (respectively) of a glucose meter encoding.
+
+**Table E.17 – Glucose meter encoding – Part 1**
+
+| Description             | OBX-2 | OBX-3                                                                                                                                                                                                                                                                                                                                                                                                                     | OBX-4     | OBX-5   |
+|-------------------------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---------|
+| Glucose meter MDS       |       | 528401^MDC_DEV_SPEC_PROFILE_SCALE^MDC                                                                                                                                                                                                                                                                                                                                                                                     | 1         |         |
+| Blood glucose           | NM    | 160184^MDC_CONC_GLU_CAPILLARY_WHOLEBLOOD^MDC or<br>160188^MDC_CONC_GLU_CAPILLARY_PLASMA^MDC or<br>160192^MDC_CONC_GLU_VENOUS_WHOLEBLOOD^MDC or<br>160196^MDC_CONC_GLU_VENOUS_PLASMA^MDC or<br>160200^MDC_CONC_GLU_ARTERIAL_WHOLEBLOOD^MDC or<br>160204^MDC_CONC_GLU_ARTERIAL_PLASMA^MDC or<br>160364^MDC_CONC_GLU_UNDETERMINED_WHOLEBLOOD or<br>160368^MDC_CONC_GLU_UNDETERMINED_PLASMA or<br>160212^MDC_CONC_GLU_ISF^MDC | 1.0.0.1   | 37.5    |
+| Control solution        | NM    | 160208^MDC_CONC_GLU_CONTROL^MDC                                                                                                                                                                                                                                                                                                                                                                                           | 1.0.0.2   | 37.5    |
+| Context exercise        | NM    | 8417760^MDC_CTXT_GLU_EXERCISE^MDC                                                                                                                                                                                                                                                                                                                                                                                         | 1.0.0.3   | 77.7    |
+| Source-Handle-Reference | ST    | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC                                                                                                                                                                                                                                                                                                                                                                                      | 1.0.0.3.1 | 1.0.0.1 |
+| Measure active period   | NM    | 68185^MDC_ATTR_TIME_PD_MSMT_ACTIVE^MDC                                                                                                                                                                                                                                                                                                                                                                                    | 1.0.0.3.2 | 101.5   |
+| Context medication      | NM    | 8417796^MDC_CTXT_MEDICATION^MDC or<br>8417800^MDC_CTXT_MEDICATION_RAPIDACTING^MDC or<br>8417804^MDC_CTXT_MEDICATION_SHORTACTING^MDC or<br>8417808^MDC_CTXT_MEDICATION_INTERMEDIATEACTING^MDC or<br>8417812^MDC_CTXT_MEDICATION_LONGACTING^MDC or<br>8417816^MDC_CTXT_MEDICATION_PREMIX^MDC                                                                                                                                | 1.0.0.4   | 33.3    |
+
+**Table E.17 – Glucose meter encoding – Part 1**
+
+| Description                           | OBX-2 | OBX-3                                                                                                                                                                                                                                                                                                                                                                                                       | OBX-4     | OBX-5                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------------------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Source-Handle-Reference               | ST    | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC                                                                                                                                                                                                                                                                                                                                                                        | 1.0.0.4.1 | 1.0.0.1                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| Context carbohydrates                 | NM    | 8417764^MDC_CTXT_GLU_CARB^MDC is the generic code or if specific Metric-Id is specified use it...<br>8417768^MDC_CTXT_GLU_CARB_BREAKFAST^MDC or<br>8417772^MDC_CTXT_GLU_CARB_LUNCH^MDC or<br>8417776^MDC_CTXT_GLU_CARB_DINNER^MDC or<br>8417780^MDC_CTXT_GLU_CARB_SNACK^MDC or<br>8417784^MDC_CTXT_GLU_CARB_DRINK^MDC or<br>8417788^MDC_CTXT_GLU_CARB_SUPPER^MDC or<br>8417792^MDC_CTXT_GLU_CARB_BRUNCH^MDC | 1.0.0.5   | 15.7                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| Source-Handle-Reference               | ST    | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC                                                                                                                                                                                                                                                                                                                                                                        | 1.0.0.5.1 | 1.0.0.1                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| Device and sensor annunciation status | CWE   | 8417752^MDC_GLU_METER_DEV_STATUS^MDC                                                                                                                                                                                                                                                                                                                                                                        | 1.0.0.6   | Any of the following value...<br><0 or 1>^device-battery-low(0),<br><0 or 1>^sensor-malfunction(1),<br><0 or 1>^sensor-sample-size-insufficient(2)<br><0 or 1>^sensor-strip-insertion(3),<br><0 or 1>^sensor-strip-type-incorrect(4),<br><0 or 1>^sensor-result-too-high(5),<br><0 or 1>^sensor-result-too-low(6),<br><0 or 1>^sensor-temp-too-high(7),<br><0 or 1>^sensor-temp-too-low(8),<br><0 or 1>^sensor-read-interrupt(9),<br><0 or 1>^device-gen-fault(10) |
+
+**Table E.17 – Glucose meter encoding – Part 1**
+
+| <b>Description</b>      | <b>OBX-2</b> | <b>OBX-3</b>                            | <b>OBX-4</b> | <b>OBX-5</b>                                                                                                                                                                                                                  |
+|-------------------------|--------------|-----------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Context meal            | CWE          | 8417864^MDC_CTXT_GLU_MEAL^MDC           | 1.0.0.7      | 8417868^MDC_CTXT_GLU_MEAL_PREPRANDIAL^MDC or<br>8417872^MDC_CTXT_GLU_MEAL_POSTPRANDIAL^MDC or<br>8417876^MDC_CTXT_GLU_MEAL_FASTING^MDC or<br>8417880^MDC_CTXT_GLU_MEAL_CASUAL^MDC or<br>8417869^MDC_CTXT_GLU_MEAL_BEDTIME^MDC |
+| Source-Handle-Reference | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC    | 1.0.0.7.1    | 1.0.0.1                                                                                                                                                                                                                       |
+| Context sample location | CWE          | 8417844^MDC_CTXT_GLU_SAMPLELOCATION^MDC | 1.0.0.8      | 8417848^MDC_CTXT_GLU_SAMPLELOCATION_FINGER^MDC or<br>8417852^MDC_CTXT_GLU_SAMPLELOCATION_AST^MDC or<br>8417856^MDC_CTXT_GLU_SAMPLELOCATION_EARLOBE^MDC or<br>8417860^MDC_CTXT_GLU_SAMPLELOCATION_CTLSOLUTION^MDC              |
+| Source-Handle-Reference | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC    | 1.0.0.8.1    | 1.0.0.1                                                                                                                                                                                                                       |
+
+**Table E.17 – Glucose meter encoding – Part 1**
+
+| <b>Description</b>      | <b>OBX-2</b> | <b>OBX-3</b>                                                                                                                                                                                                                       | <b>OBX-4</b> | <b>OBX-5</b>                                                                                                                                                                                                           |
+|-------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Context tester          | CWE          | 8417884^MDC_CTXT_GLU_TESTER^MDC<br>is the generic code or if specific Metric-Id is specified use it...<br>8417888^MDC_CTXT_GLU_TESTER_SELF^MDC or<br>8417892^MDC_CTXT_GLU_TESTER_HCP^MDC or<br>8417896^MDC_CTXT_GLU_TESTER_LAB^MDC | 1.0.0.9      |                                                                                                                                                                                                                        |
+| Source-Handle-Reference | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC                                                                                                                                                                                               | 1.0.0.9.1    | 1.0.0.1                                                                                                                                                                                                                |
+| Context health          | CWE          | 8417820^MDC_CTXT_GLU_HEALTH^MDC                                                                                                                                                                                                    | 1.0.0.10     | 8417824^MDC_CTXT_GLU_HEALTH_MINOR^MDC or<br>8417828^MDC_CTXT_GLU_HEALTH_MAJOR^MDC or<br>8417832^MDC_CTXT_GLU_HEALTH_MENSES^MDC or<br>8417836^MDC_CTXT_GLU_HEALTH_STRESS^MDC or<br>8417840^MDC_CTXT_GLU_HEALTH_NONE^MDC |
+| Source-Handle-Reference | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC                                                                                                                                                                                               | 1.0.0.10.1   | 1.0.0.4                                                                                                                                                                                                                |
+| HbA1c                   | NM           | 160220^MDC_CONC_HBA1C^MDC                                                                                                                                                                                                          | 1.0.0.11     | 77.7                                                                                                                                                                                                                   |
+
+**Table E.18 – Glucose meter encoding – part 2**
+
+| <b>Description</b>                       | <b>OBX-6</b>                                                                                                                                           | <b>OBX-18</b>                                 | <b>OBX-20</b> |
+|------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|---------------|
+| Glucose meter MDS                        |                                                                                                                                                        | 0123456789ABCDEF^^0123456<br>789ABCDEF^EUI-64 |               |
+| Blood glucose                            | 264274^MDC_DIM_MILLI_G_PER_DL^MDC or<br>266866^MDC_DIM_MILLI_MOLE_PER_L^MDC                                                                            |                                               |               |
+| Context exercise                         | 262688^MDC_DIM_PERCENT^MDC                                                                                                                             |                                               |               |
+| Source-Handle-Reference                  |                                                                                                                                                        |                                               |               |
+| Measure active period                    | 264320^MDC_DIM_SEC^MDC                                                                                                                                 |                                               |               |
+| Context medication                       | 263890^MDC_DIM_MILLI_G^MDC or<br>263762^MDC_DIM_MILLI_L^MDC                                                                                            |                                               |               |
+| Source-Handle-Reference                  |                                                                                                                                                        |                                               |               |
+| Context carbohydrates                    | 263872^MDC_DIM_G^MDC<br><br>NOTE – The underlying standard uses MDC_DIM_X_G but<br>this is translated to MDC_DIM_G for the Services interface<br>usage |                                               |               |
+| Source-Handle-Reference                  |                                                                                                                                                        |                                               |               |
+| Device and sensor<br>annunciation status |                                                                                                                                                        |                                               |               |
+| Context meal                             |                                                                                                                                                        |                                               |               |
+| Source-Handle-Reference                  |                                                                                                                                                        |                                               |               |
+| Context sample location                  |                                                                                                                                                        |                                               |               |
+| Source-Handle-Reference                  |                                                                                                                                                        |                                               |               |
+| Context tester                           |                                                                                                                                                        |                                               |               |
+| Source-Handle-Reference                  |                                                                                                                                                        |                                               |               |
+| Context health                           |                                                                                                                                                        |                                               |               |
+| Source-Handle-Reference                  |                                                                                                                                                        |                                               |               |
+| HbA1c                                    | 262688^MDC_DIM_PERCENT^MDC                                                                                                                             |                                               |               |
+
+### E.3.6 10418 INR meter
+
+#### E.3.6.1 Modelling
+
+The INR meter object model consists of one key observation type, INR. Contextual objects which may provide additional information to these values **may** be linked to a particular source observation through a Source-Handle-Reference FACET-level OBX.
+
+#### E.3.6.2 Transformations
+
+The following transformations are performed in the encoding of this device.
+
+Several nomenclature codes have been harmonized with the underlying base codes. These are pointed out in the tables below.
+
+#### E.3.6.3 Containment tree
+
+Table E.19 shows an INR meter containment tree.
+
+**Table E.19 – INR meter containment tree**
+
+| REFID                                                                            | Description                                                               |
+|----------------------------------------------------------------------------------|---------------------------------------------------------------------------|
+| MDC_DEV_SPEC_PROFILE_COAG                                                        | INR meter MDS                                                             |
+| ... MDC_RATIO_INR_COAG or<br>... MDC_TIME_PD_COAG or<br>... MDC_QUICK_VALUE_COAG | INR                                                                       |
+| ... MDC_COAG_CONTROL                                                             | Control solution                                                          |
+| ... MDC_ISI_COAG                                                                 | International Sensitivity Index (ISI)                                     |
+| ... MDC_INR_METER_DEV_STATUS                                                     | Device and sensor annunciation status                                     |
+| ... MDC_CTX_T_INR_TESTER                                                         | Context tester                                                            |
+| .... MDC_SOURCE_HANDLE_REF                                                       | Source-Handle-Reference<br>Reference to the corresponding INR measurement |
+
+### E.3.6.4 OBX encoding
+
+Table E.20 and Table E.21 show part 1 and part 2 (respectively) of an INR meter encoding.
+
+**Table E.20 – INR meter encoding – Part 1**
+
+| Description             | OBX-2 | OBX-3                                                                                                                                                                                                                              | OBX-4     | OBX-5   |
+|-------------------------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---------|
+| INR meter MDS           |       | 528406^MDC_DEV_SPEC_PROFILE_COAG^MDC                                                                                                                                                                                               | 1         |         |
+| INR                     | NM    | 160260^MDC_RATIO_INR_COAG^MDC or<br>160264^MDC_TIME_PD_COAG^MDC or<br>160268^MDC_QUICK_VALUE_COAG^MDC                                                                                                                              | 1.0.0.1   | 1.5     |
+| Control solution        | NM    | 160276^MDC_CONC_INR_CONTROL^MDC                                                                                                                                                                                                    | 1.0.0.2   | 2.5     |
+| ISI                     | NM    | 160272^MDC_COAG^MDC                                                                                                                                                                                                                | 1.0.0.3   |         |
+| Context tester          |       | 8417924^MDC_CTXT_INR_TESTER^MDC<br>is the generic code or if specific Metric-Id is specified use it...<br>8417925^MDC_CTXT_INR_TESTER_SELF^MDC or<br>8417926^MDC_CTXT_INR_TESTER_HCP^MDC or<br>8417927^MDC_CTXT_INR_TESTER_LAB^MDC | 1.0.0.4   |         |
+| Source-Handle-Reference | ST    | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC                                                                                                                                                                                               | 1.0.0.4.1 | 1.0.0.1 |
+
+**Table E.21 – INR meter encoding – Part 2**
+
+| Description      | OBX-6                                                                                | OBX-18                                    | OBX-20 |
+|------------------|--------------------------------------------------------------------------------------|-------------------------------------------|--------|
+| INR meter MDS    |                                                                                      | 0123456789ABCDEF^^0123456789ABCDEF^EUI-64 |        |
+| INR              | 268752^MDC_DIM_INR^MDC or<br>264320^MDC_DIM_SEC^MDC or<br>262688^MDC_DIM_PERCENT^MDC |                                           |        |
+| Control solution | 268752^MDC_DIM_INR^MDC                                                               |                                           |        |
+| ISI              | 262656^MDC_DIM_DIMLESS^MDC                                                           |                                           |        |
+| Context tester   |                                                                                      |                                           |        |
+
+| Description             | OBX-6 | OBX-18 | OBX-20 |
+|-------------------------|-------|--------|--------|
+| Source-Handle-Reference |       |        |        |
+
+### E.3.7 10441 Cardiovascular fitness and activity monitor
+
+#### E.3.7.1 Modelling
+
+All observations for this device belong to sessions or subsessions. This natural hierarchy is expressed through the PCD-01 containment hierarchy and shown in the following tables.
+
+#### E.3.7.2 Transformations
+
+The following transformations are performed in the encoding of this device.
+
+Several nomenclature codes have been harmonized with the underlying base codes. These are pointed out in the tables below.
+
+#### E.3.7.3 Containment tree
+
+Table E.22 shows a cardiovascular fitness and activity monitor containment tree.
+
+**Table E.22 – Cardiovascular fitness and activity monitor containment tree**
+
+| REFID                             | Description                                                       |
+|-----------------------------------|-------------------------------------------------------------------|
+| MDC_DEV_SPEC_PROFILE_HF_CARDIO    | Cardiovascular fitness and activity monitor MDS                   |
+| ... MDC_HF_SESSION                | Session                                                           |
+| .... MDC_ATTR_TIME_PD_MSMT_ACTIVE | Measure active period (Session)                                   |
+| ... MDC_HF_SUBSESSION             | Subsession                                                        |
+| .... MDC_ATTR_TIME_PD_MSMT_ACTIVE | Measure active period (Subsession)                                |
+| ... MDC_HF_ALT_LOSS               | Altitude loss                                                     |
+| .... MDC_SOURCE_HANDLE_REF        | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_ALT                    | Altitude                                                          |
+| .... MDC_SOURCE_HANDLE_REF        | Source-Handle-Reference<br>Reference to the corresponding session |
+
+**Table E.22 – Cardiovascular fitness and activity monitor containment tree**
+
+| <b>REFID</b>                      | <b>Description</b>                                                |
+|-----------------------------------|-------------------------------------------------------------------|
+| ... MDC_HF_DISTANCE               | Distance                                                          |
+| .... MDC_SOURCE_HANDLE_REF        | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_ASC_TIME_DIST          | Ascent time and distance                                          |
+| .... MDC_ATTR_TIME_PD_MSMT_ACTIVE | Measure active period                                             |
+| .... MDC_SOURCE_HANDLE_REF        | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_DESC_TIME_DIST         | Descent time and distance                                         |
+| .... MDC_ATTR_TIME_PD_MSMT_ACTIVE | Measure active period                                             |
+| .... MDC_SOURCE_HANDLE_REF        | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_LATITUDE               | Latitude                                                          |
+| .... MDC_SOURCE_HANDLE_REF        | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_LONGITUDE              | Longitude                                                         |
+| .... MDC_SOURCE_HANDLE_REF        | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_SLOPES                 | Slopes                                                            |
+| .... MDC_SOURCE_HANDLE_REF        | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_SPEED                  | Speed                                                             |
+| .... MDC_ATTR_ID_PHYSIO           | Measurement type (Speed)                                          |
+| .... MDC_SOURCE_HANDLE_REF        | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_CAD                    | Cadence                                                           |
+
+**Table E.22 – Cardiovascular fitness and activity monitor containment tree**
+
+| <b>REFID</b>               | <b>Description</b>                                                |
+|----------------------------|-------------------------------------------------------------------|
+| .... MDC_ATTR_ID_PHYSIO    | Measurement type (Cadence)                                        |
+| .... MDC_SOURCE_HANDLE_REF | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_INCLINE         | Incline                                                           |
+| .... MDC_ATTR_ID_PHYSIO    | Measurement type (Incline)                                        |
+| .... MDC_SOURCE_HANDLE_REF | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_HR              | Heart rate                                                        |
+| .... MDC_ATTR_ID_PHYSIO    | Measurement type (Heart Rate)                                     |
+| .... MDC_SOURCE_HANDLE_REF | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_HR_MAX_USER     | Max user heart rate                                               |
+| .... MDC_SOURCE_HANDLE_REF | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_POWER           | Power                                                             |
+| .... MDC_ATTR_ID_PHYSIO    | Measurement type (Power)                                          |
+| .... MDC_SOURCE_HANDLE_REF | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_RESIST          | Resistance                                                        |
+| .... MDC_ATTR_ID_PHYSIO    | Measurement type (Resistance)                                     |
+| .... MDC_SOURCE_HANDLE_REF | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_STRIDE          | Stride length                                                     |
+| .... MDC_ATTR_ID_PHYSIO    | Measurement type (Stride length)                                  |
+| .... MDC_SOURCE_HANDLE_REF | Source-Handle-Reference                                           |
+
+**Table E.22 – Cardiovascular fitness and activity monitor containment tree**
+
+| <b>REFID</b>                  | <b>Description</b>                                                |
+|-------------------------------|-------------------------------------------------------------------|
+|                               | Reference to the corresponding session                            |
+| ... MDC_RESP_RATE             | Breathing rate                                                    |
+| .... MDC_ATTR_ID_PHYSIO       | Measurement type (Breathing rate)                                 |
+| .... MDC_SOURCE_HANDLE_REF    | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_ENERGY             | Energy expended                                                   |
+| .... MDC_SOURCE_HANDLE_REF    | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_CAL_INGEST         | Calories ingested                                                 |
+| .... MDC_SOURCE_HANDLE_REF    | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_CAL_INGEST_CARBO   | Carbohydrate calories ingested                                    |
+| .... MDC_SOURCE_HANDLE_REF    | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_SUST_PA_THRESHOLD  | Sustained physical activity threshold                             |
+| .... MDC_SOURCE_HANDLE_REF    | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_ACTIVITY_INTENSITY | Activity intensity                                                |
+| .... MDC_SOURCE_HANDLE_REF    | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_MASS_BODY_ACTUAL      | Body weight                                                       |
+| .... MDC_SOURCE_HANDLE_REF    | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_LEN_BODY_ACTUAL       | Height                                                            |
+| .... MDC_SOURCE_HANDLE_REF    | Source-Handle-Reference                                           |
+
+**Table E.22 – Cardiovascular fitness and activity monitor containment tree**
+
+| REFID                             | Description                                                       |
+|-----------------------------------|-------------------------------------------------------------------|
+|                                   | Reference to the corresponding session                            |
+| ... MDC_HF_AGE                    | Age                                                               |
+| .... MDC_SOURCE_HANDLE_REF        | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_ACTIVITY_TIME          | Activity time                                                     |
+| .... MDC_ATTR_TIME_PD_MSMT_ACTIVE | Measure active period (Activity time)                             |
+| .... MDC_SOURCE_HANDLE_REF        | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_PROGRAM_ID             | Program identifier                                                |
+| .... MDC_SOURCE_HANDLE_REF        | Source-Handle-Reference<br>Reference to the corresponding session |
+
+### E.3.7.4 OBX encoding
+
+Table E.23 and Table E.24 show part 1 and part 2 (respectively) of a cardiovascular fitness and activity monitor encoding.
+
+**Table E.23 – Cardiovascular fitness and activity monitor encoding – Part 1**
+
+| Description                                     | OBX-2 | OBX-3                                     | OBX-4     | OBX-5                                                                                            |
+|-------------------------------------------------|-------|-------------------------------------------|-----------|--------------------------------------------------------------------------------------------------|
+| Cardiovascular fitness and activity monitor MDS |       | 528425^MDC_DEV_SPEC_PROFILE_HF_CARDIO^MDC | 1         |                                                                                                  |
+| Session                                         | CWE   | 8454267^MDC_HF_SESSION^MDC                | 1.0.0.1   | Any of the MDC_HF_ACT_* values defined in 10441.<br>For example...<br>8455155^MDC_HF_ACT_RUN^MDC |
+| Measure active period (Session)                 | NM    | 68185^MDC_ATTR_TIME_PD_MSMT_ACTIVE^MDC    | 1.0.0.1.1 | 25                                                                                               |
+
+**Table E.23 – Cardiovascular fitness and activity monitor encoding – Part 1**
+
+| <b>Description</b>                 | <b>OBX-2</b> | <b>OBX-3</b>                           | <b>OBX-4</b> | <b>OBX-5</b>                                                                                     |
+|------------------------------------|--------------|----------------------------------------|--------------|--------------------------------------------------------------------------------------------------|
+| Subsession                         | CWE          | 8454268^MDC_HF_SUBSESSION^MDC          | 1.0.0.2      | Any of the MDC_HF_ACT_* values defined in 10441.<br>For example...<br>8455155^MDC_HF_ACT_RUN^MDC |
+| Measure active period (Subsession) | NM           | 68185^MDC_ATTR_TIME_PD_MSMT_ACTIVE^MDC | 1.0.0.2.1    | 25                                                                                               |
+| Altitude gain                      | NM           | 8454244^MDC_HF_ALT_GAIN^MDC            | 1.0.0.3      | 10                                                                                               |
+| Source-Handle-Reference            | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC   | 1.0.0.3.1    | 1.0.0.2                                                                                          |
+| Altitude loss                      | NM           | 8454245^MDC_HF_ALT_LOSS^MDC            | 1.0.0.4      | 10                                                                                               |
+| Source-Handle-Reference            | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC   | 1.0.0.4.1    | 1.0.0.2                                                                                          |
+| Altitude                           | NM           | 8454246^MDC_HF_ALT^MDC                 | 1.0.0.5      | 10                                                                                               |
+| Distance                           | NM           | 8454247^MDC_HF_DISTANCE^MDC            | 1.0.0.6      | 10                                                                                               |
+| Source-Handle-Reference            | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC   | 1.0.0.6.1    | 1.0.0.2                                                                                          |
+| Ascent time and distance           | NM           | 8454248^MDC_HF_ASC_TIME_DIST^MDC       | 1.0.0.7      | 10                                                                                               |
+| Measure active period              | NM           | 68185^MDC_ATTR_TIME_PD_MSMT_ACTIVE^MDC | 1.0.0.7.1    | 25                                                                                               |
+| Source-Handle-Reference            | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC   | 1.0.0.7.2    | 1.0.0.2                                                                                          |
+| Descent time and distance          | NM           | 8454249^MDC_HF_DESC_TIME_DIST^MDC      | 1.0.0.8      | 10                                                                                               |
+| Measure active period              | NM           | 68185^MDC_ATTR_TIME_PD_MSMT_ACTIVE^MDC | 1.0.0.8.1    | 25                                                                                               |
+| Source-Handle-                     | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC   | 1.0.0.8.2    | 1.0.0.2                                                                                          |
+
+**Table E.23 – Cardiovascular fitness and activity monitor encoding – Part 1**
+
+| <b>Description</b>         | <b>OBX-2</b> | <b>OBX-3</b>                         | <b>OBX-4</b> | <b>OBX-5</b>                                                                                                                                    |
+|----------------------------|--------------|--------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------|
+| Reference                  |              |                                      |              |                                                                                                                                                 |
+| Latitude                   | NM           | 8454250^MDC_HF_LATITUDE^MDC          | 1.0.0.9      | 53.2                                                                                                                                            |
+| Source-Handle-Reference    | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC | 1.0.0.9.1    | 1.0.0.2                                                                                                                                         |
+| Longitude                  | NM           | 8454251^MDC_HF_LONGITUDE^MDC         | 1.0.0.10     | 67.7                                                                                                                                            |
+| Source-Handle-Reference    | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC | 1.0.0.10.1   | 1.0.0.2                                                                                                                                         |
+| Slopes                     | NM           | 8454253^MDC_HF_SLOPES^MDC            | 1.0.0.11     | 11                                                                                                                                              |
+| Source-Handle-Reference    | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC | 1.0.0.11.1   | 1.0.0.2                                                                                                                                         |
+| Speed                      | NM           | 8454254^MDC_HF_SPEED^MDC             | 1.0.0.12     | 37.3                                                                                                                                            |
+| Measurement type (Speed)   | CWE          | 67883^MDC_ATTR_ID_PHYSIO^MDC         | 1.0.0.12.1   | 8456144^MDC_HF_MEAN_NULL_EXCLUDE^MDC<br>or<br>8456145^MDC_HF_MEAN_NULL_INCLUDE^MDC<br>or<br>8456146^MDC_HF_MAX^MDC or<br>8456147^MDC_HF_MIN^MDC |
+| Source-Handle-Reference    | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC | 1.0.0.12.2   | 1.0.0.2                                                                                                                                         |
+| Cadence                    | NM           | 8454255^MDC_HF_CAD^MDC               | 1.0.0.13     | 55                                                                                                                                              |
+| Measurement type (Cadence) | CWE          | 67883^MDC_ATTR_ID_PHYSIO^MDC         | 1.0.0.13.1   | 8456144^MDC_HF_MEAN_NULL_EXCLUDE^MDC<br>or<br>8456145^MDC_HF_MEAN_NULL_INCLUDE^MDC<br>or<br>8456146^MDC_HF_MAX^MDC or<br>8456147^MDC_HF_MIN^MDC |
+| Source-Handle-             | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC | 1.0.0.13.2   | 1.0.0.2                                                                                                                                         |
+
+**Table E.23 – Cardiovascular fitness and activity monitor encoding – Part 1**
+
+| <b>Description</b>            | <b>OBX-2</b> | <b>OBX-3</b>                         | <b>OBX-4</b> | <b>OBX-5</b>                                                                                                                                    |
+|-------------------------------|--------------|--------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------|
+| Reference                     |              |                                      |              |                                                                                                                                                 |
+| Incline                       | NM           | 8454256^MDC_HF_INCLINE^MDC           | 1.0.0.14     | 12.7                                                                                                                                            |
+| Measurement type (Incline)    | CWE          | 67883^MDC_ATTR_ID_PHYSIO^MDC         | 1.0.0.14.1   | 8456144^MDC_HF_MEAN_NULL_EXCLUDE^MDC<br>or<br>8456145^MDC_HF_MEAN_NULL_INCLUDE^MDC<br>or<br>8456146^MDC_HF_MAX^MDC or<br>8456147^MDC_HF_MIN^MDC |
+| Source-Handle-Reference       | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC | 1.0.0.14.2   | 1.0.0.2                                                                                                                                         |
+| Heart rate                    | NM           | 8454258^MDC_HF_HR^MDC                | 1.0.0.15     | 77                                                                                                                                              |
+| Measurement type (Heart rate) | CWE          | 67883^MDC_ATTR_ID_PHYSIO^MDC         | 1.0.0.15.1   | 8456144^MDC_HF_MEAN_NULL_EXCLUDE^MDC<br>or<br>8456145^MDC_HF_MEAN_NULL_INCLUDE^MDC<br>or<br>8456146^MDC_HF_MAX^MDC or<br>8456147^MDC_HF_MIN^MDC |
+| Source-Handle-Reference       | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC | 1.0.0.15.2   | 1.0.0.2                                                                                                                                         |
+| Max user heart rate           | NM           | 8454257^MDC_HF_HR_MAX_USER^MDC       | 1.0.0.16     | 99                                                                                                                                              |
+| Power                         | NM           | 8454259^MDC_HF_POWER^MDC             | 1.0.0.17     | 154.2                                                                                                                                           |
+| Measurement type (Power)      | CWE          | 67883^MDC_ATTR_ID_PHYSIO^MDC         | 1.0.0.17.1   | 8456144^MDC_HF_MEAN_NULL_EXCLUDE^MDC<br>or<br>8456145^MDC_HF_MEAN_NULL_INCLUDE^MDC<br>or<br>8456146^MDC_HF_MAX^MDC or<br>8456147^MDC_HF_MIN^MDC |
+
+**Table E.23 – Cardiovascular fitness and activity monitor encoding – Part 1**
+
+| <b>Description</b>                | <b>OBX-2</b> | <b>OBX-3</b>                         | <b>OBX-4</b> | <b>OBX-5</b>                                                                                                                                    |
+|-----------------------------------|--------------|--------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------|
+| Source-Handle-Reference           | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC | 1.0.0.17.2   | 1.0.0.2                                                                                                                                         |
+| Resistance                        | NM           | 8454260^MDC_HF_RESIST^MDC            | 1.0.0.18     | 55                                                                                                                                              |
+| Measurement type (Power)          | CWE          | 67883^MDC_ATTR_ID_PHYSIO^MDC         | 1.0.0.18.1   | 8456144^MDC_HF_MEAN_NULL_EXCLUDE^MDC<br>or<br>8456145^MDC_HF_MEAN_NULL_INCLUDE^MDC<br>or<br>8456146^MDC_HF_MAX^MDC or<br>8456147^MDC_HF_MIN^MDC |
+| Source-Handle-Reference           | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC | 1.0.0.18.2   | 1.0.0.2                                                                                                                                         |
+| Stride length                     | NM           | 8454261^MDC_HF_STRIDE^MDC            | 1.0.0.19     | 56.6                                                                                                                                            |
+| Measurement type (Power)          | CWE          | 67883^MDC_ATTR_ID_PHYSIO^MDC         | 1.0.0.19.1   | 8456144^MDC_HF_MEAN_NULL_EXCLUDE^MDC<br>or<br>8456145^MDC_HF_MEAN_NULL_INCLUDE^MDC<br>or<br>8456146^MDC_HF_MAX^MDC or<br>8456147^MDC_HF_MIN^MDC |
+| Source-Handle-Reference           | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC | 1.0.0.19.2   | 1.0.0.2                                                                                                                                         |
+| Breathing rate                    | NM           | 151562^MDC_RESP_RATE^MDC             | 1.0.0.20     | 51                                                                                                                                              |
+| Measurement type (Breathing rate) | CWE          | 67883^MDC_ATTR_ID_PHYSIO^MDC         | 1.0.0.20.1   | 8456144^MDC_HF_MEAN_NULL_EXCLUDE^MDC<br>or<br>8456145^MDC_HF_MEAN_NULL_INCLUDE^MDC<br>or<br>8456146^MDC_HF_MAX^MDC or<br>8456147^MDC_HF_MIN^MDC |
+| Source-Handle-                    | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC | 1.0.0.20.2   | 1.0.0.2                                                                                                                                         |
+
+**Table E.23 – Cardiovascular fitness and activity monitor encoding – Part 1**
+
+| <b>Description</b>                | <b>OBX-2</b> | <b>OBX-3</b>                          | <b>OBX-4</b> | <b>OBX-5</b> |
+|-----------------------------------|--------------|---------------------------------------|--------------|--------------|
+| Reference                         |              |                                       |              |              |
+| Energy expended                   | NM           | 8454263^MDC_HF_ENERGY^MDC             | 1.0.0.21     | 523.1        |
+| Source-Handle-Reference           | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC  | 1.0.0.21.1   | 1.0.0.2      |
+| Calories ingested                 | NM           | 8454264^MDC_HF_CAL_INGEST^MDC         | 1.0.0.22     | 837.2        |
+| Source-Handle-Reference           | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC  | 1.0.0.22.1   | 1.0.0.2      |
+| Carbohydrate calories ingested    | NM           | 8454265^MDC_HF_CAL_INGEST_CARBO^MDC   | 1.0.0.23     | 433.7        |
+| Source-Handle-Reference           | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC  | 1.0.0.23.1   | 1.0.0.2      |
+| Sustained phys activity threshold | NM           | 8454266^MDC_HF_SUST_PA_THRESHOLD^MDC  | 1.0.0.24     | 45.3         |
+| Source-Handle-Reference           | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC  | 1.0.0.24.1   | 1.0.0.2      |
+| Activity intensity                | NM           | 8454271^MDC_HF_ACTIVITY_INTENSITY^MDC | 1.0.0.25     | 22.2         |
+| Source-Handle-Reference           | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC  | 1.0.0.25.1   | 1.0.0.2      |
+| Body weight                       | NM           | 188736^MDC_MASS_BODY_ACTUAL^MDC       | 1.0.0.26     | 101.8        |
+| Height                            | NM           | 188740^MDC_LEN_BODY_ACTUAL^MDC        | 1.0.0.27     | 72.0         |
+| Age                               | NM           | 8454270^MDC_HF_AGE^MDC                | 1.0.0.28     | 37           |
+
+**Table E.23 – Cardiovascular fitness and activity monitor encoding – Part 1**
+
+| <b>Description</b>                    | <b>OBX-2</b> | <b>OBX-3</b>                           | <b>OBX-4</b> | <b>OBX-5</b>                                                                                                                                                                                                                                                                       |
+|---------------------------------------|--------------|----------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Activity time                         | CWE          | 8454269^MDC_HF_ACTIVITY_TIME^MDC       | 1.0.0.29     | 8455144^MDC_HF_ACT_AMB^MDC or<br>8455145^MDC_HF_ACT_REST^MDC or<br>8455146^MDC_HF_ACT_MOTOR^MDC or<br>8455147^MDC_HF_ACT_LYING^MDC or<br>8455148^MDC_HF_ACT_SLEEP^MDC or<br>8455149^MDC_HF_ACT_PHYS^MDC or<br>8455150^MDC_HF_ACT_SUS_PHYS^MDC or<br>8455151^MDC_HF_ACT_UNKNOWN^MDC |
+| Measure active period (Activity Time) | NM           | 68185^MDC_ATTR_TIME_PD_MSMT_ACTIVE^MDC | 1.0.0.29.1   | 25                                                                                                                                                                                                                                                                                 |
+| Source-Handle-Reference               | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC   | 1.0.0.29.2   | 1.0.0.2                                                                                                                                                                                                                                                                            |
+| Program identifier                    | ST           | 8454252^MDC_HF_PROGRAM_ID^MDC          | 1.0.0.30     | "Pike's Peak hill climb"                                                                                                                                                                                                                                                           |
+| Source-Handle-Reference               | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC   | 1.0.0.30.1   | 1.0.0.2                                                                                                                                                                                                                                                                            |
+
+**Table E.24 – Cardiovascular fitness and activity monitor encoding – Part 2**
+
+| <b>Description</b>             | <b>OBX-6</b> | <b>OBX-18</b>                             | <b>OBX-20</b> |
+|--------------------------------|--------------|-------------------------------------------|---------------|
+| Strength fitness equipment MDS |              | 0123456789ABCDEF^^0123456789ABCDEF^EUI-64 |               |
+| Session                        |              |                                           |               |
+
+**Table E.24 – Cardiovascular fitness and activity monitor encoding – Part 2**
+
+| <b>Description</b>                 | <b>OBX-6</b>                                                                                                                                                                                                               | <b>OBX-18</b> | <b>OBX-20</b> |
+|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|
+| Measure active period (Session)    | 264320^MDC_DIM_SEC^MDC                                                                                                                                                                                                     |               |               |
+| Subsession                         |                                                                                                                                                                                                                            |               |               |
+| Measure active period (Subsession) | 264320^MDC_DIM_SEC^MDC                                                                                                                                                                                                     |               |               |
+| Altitude gain                      | 263424^MDC_DIM_M^MDC or<br>263488^MDC_DIM_FOOT^MDC<br>NOTE – The underlying standard uses<br>MDC_DIM_X_M and MDC_DIM_X_FOOT<br>but this is translated to MDC_DIM_M and<br>MDC_DIM_FOOT for the Services interface<br>usage |               |               |
+| Source-Handle-Reference            |                                                                                                                                                                                                                            |               |               |
+| Altitude loss                      | 263424^MDC_DIM_M^MDC or<br>263488^MDC_DIM_FOOT^MDC<br>NOTE – The underlying standard uses<br>MDC_DIM_X_M and MDC_DIM_X_FOOT<br>but this is translated to MDC_DIM_M and<br>MDC_DIM_FOOT for the Services interface<br>usage |               |               |
+| Source-Handle-Reference            |                                                                                                                                                                                                                            |               |               |
+| Altitude                           | 263424^MDC_DIM_M^MDC or<br>263488^MDC_DIM_FOOT^MDC<br>NOTE – The underlying standard uses<br>MDC_DIM_X_M and MDC_DIM_X_FOOT<br>but this is translated to MDC_DIM_M and<br>MDC_DIM_FOOT for the Services interface<br>usage |               |               |
+
+**Table E.24 – Cardiovascular fitness and activity monitor encoding – Part 2**
+
+| <b>Description</b>        | <b>OBX-6</b>                                                                                                                                                                                                                                                                              | <b>OBX-18</b> | <b>OBX-20</b> |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|
+| Source-Handle-Reference   |                                                                                                                                                                                                                                                                                           |               |               |
+| Distance                  | 263424^MDC_DIM_M^MDC or<br>263488^MDC_DIM_FOOT^MDC or<br>268800^MDC_DIM_STEP^MDC<br>NOTE – The underlying standard uses<br>MDC_DIM_X_M, MDC_DIM_X_FOOT and<br>MDC_DIM_X_STEP but this is translated to<br>MDC_DIM_M, MDC_DIM_FOOT and<br>MDC_DIM_STEP for the Services interface<br>usage |               |               |
+| Source-Handle-Reference   |                                                                                                                                                                                                                                                                                           |               |               |
+| Ascent time and distance  | 263424^MDC_DIM_M^MDC or<br>263488^MDC_DIM_FOOT^MDC or<br>268800^MDC_DIM_STEP^MDC<br>NOTE – The underlying standard uses<br>MDC_DIM_X_M, MDC_DIM_X_FOOT and<br>MDC_DIM_X_STEP but this is translated to<br>MDC_DIM_M, MDC_DIM_FOOT and<br>MDC_DIM_STEP for the Services interface          |               |               |
+| Measure active period     | 264320^MDC_DIM_SEC^MDC                                                                                                                                                                                                                                                                    |               |               |
+| Source-Handle-Reference   |                                                                                                                                                                                                                                                                                           |               |               |
+| Descent time and distance | 263424^MDC_DIM_M^MDC or<br>263488^MDC_DIM_FOOT^MDC or<br>268800^MDC_DIM_STEP^MDC<br>NOTE – The underlying standard uses<br>MDC_DIM_X_M, MDC_DIM_X_FOOT and<br>MDC_DIM_X_STEP but this is translated to<br>MDC_DIM_M, MDC_DIM_FOOT and<br>MDC_DIM_STEP for the Services interface          |               |               |
+
+**Table E.24 – Cardiovascular fitness and activity monitor encoding – Part 2**
+
+| Description                | OBX-6                                                                                                                                                                                                                                                                                                                                                                                                                                                                | OBX-18 | OBX-20 |
+|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|
+| Measure active period      | 264320^MDC_DIM_SEC^MDC                                                                                                                                                                                                                                                                                                                                                                                                                                               |        |        |
+| Source-Handle-Reference    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |        |        |
+| Latitude                   | 262880^MDC_DIM_ANG_DEG^MDC                                                                                                                                                                                                                                                                                                                                                                                                                                           |        |        |
+| Longitude                  | 262880^MDC_DIM_ANG_DEG^MDC                                                                                                                                                                                                                                                                                                                                                                                                                                           |        |        |
+| Slopes                     | 262656^MDC_DIM_DIMLESS^MDC                                                                                                                                                                                                                                                                                                                                                                                                                                           |        |        |
+| Speed                      | 268704^MDC_DIM_M_PER_MIN^MDC, or<br>268832^MDC_DIM_FOOT_PER_MIN^MDC,<br>or<br>268864^MDC_DIM_INCH_PER_MIN^MDC,<br>or<br>268896^MDC_DIM_STEP_PER_MIN^MDC<br>NOTE – The underlying standard uses<br>MDC_DIM_X_M_PER_MIN,<br>MDC_DIM_X_INCH_PER_MIN,<br>MDC_DIM_X_FOOT_PER_MIN and<br>MDC_DIM_X_STEP_PER_MIN but this is<br>translated to MDC_DIM_M_PER_MIN,<br>MDC_DIM_FOOT_PER_MIN,<br>MDC_DIM_INCH_PER_MIN and<br>MDC_DIM_STEP_PER_MIN for the Services<br>interface |        |        |
+| Measurement type (Speed)   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |        |        |
+| Source-Handle-Reference    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |        |        |
+| Cadence                    | 268960^MDC_DIM_RPM^MDC                                                                                                                                                                                                                                                                                                                                                                                                                                               |        |        |
+| Measurement type (Cadence) |                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |        |        |
+
+**Table E.24 – Cardiovascular fitness and activity monitor encoding – Part 2**
+
+| <b>Description</b>            | <b>OBX-6</b>                                                                                                                                          | <b>OBX-18</b> | <b>OBX-20</b> |
+|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|
+| Source-Handle-Reference       |                                                                                                                                                       |               |               |
+| Incline                       | 262688^MDC_DIM_PERCENT^MDC or<br>262880^MDC_DIM_ANG_DEG^MDC                                                                                           |               |               |
+| Measurement type<br>(Incline) |                                                                                                                                                       |               |               |
+| Source-Handle-Reference       |                                                                                                                                                       |               |               |
+| Heart rate                    | 264864^MDC_DIM_BEAT_PER_MIN^MDC                                                                                                                       |               |               |
+| Measurement type (Heart rate) |                                                                                                                                                       |               |               |
+| Source-Handle-Reference       |                                                                                                                                                       |               |               |
+| Max user heart rate           | 264864^MDC_DIM_BEAT_PER_MIN^MDC                                                                                                                       |               |               |
+| Source-Handle-Reference       |                                                                                                                                                       |               |               |
+| Power                         | 266176^MDC_DIM_WATT^MDC<br>NOTE – The underlying standard uses<br>MDC_DIM_X_WATT but this is translated to<br>MDC_DIM_WATT for the Services interface |               |               |
+| Measurement type<br>(Power)   |                                                                                                                                                       |               |               |
+| Source-Handle-Reference       |                                                                                                                                                       |               |               |
+| Resistance                    | Leave blank or use<br>262656^MDC_DIM_DIMLESS^MDC                                                                                                      |               |               |
+| Measurement type<br>(Power)   |                                                                                                                                                       |               |               |
+| Source-Handle-Reference       |                                                                                                                                                       |               |               |
+
+**Table E.24 – Cardiovascular fitness and activity monitor encoding – Part 2**
+
+| Description                       | OBX-6                                                                                                                                                                                                                            | OBX-18 | OBX-20 |
+|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|
+| Stride length                     | 263424^MDC_DIM_M^MDC or<br>263520^MDC_DIM_INCH^MDC<br>NOTE – The underlying standard uses<br>MDC_DIM_X_M and MDC_DIM_X_INCH<br>but this is translated to MDC_DIM_M and<br>MDC_DIM_INCH for the Services interface                |        |        |
+| Measurement type (Stride Length)  |                                                                                                                                                                                                                                  |        |        |
+| Source-Handle-Reference           |                                                                                                                                                                                                                                  |        |        |
+| Breathing rate                    | 264928^MDC_DIM_RESP_PER_MIN^MDC                                                                                                                                                                                                  |        |        |
+| Measurement type (Breathing Rate) |                                                                                                                                                                                                                                  |        |        |
+| Source-Handle-Reference           |                                                                                                                                                                                                                                  |        |        |
+| Energy expended                   | 268928^MDC_DIM_CAL^MDC or<br>266112^MDC_DIM_JOULES^MDC<br>NOTE – The underlying standard uses<br>MDC_DIM_X_CAL and<br>MDC_DIM_X_JOULES but this is translated<br>to MDC_DIM_CAL and MDC_DIM_JOULES<br>for the Services interface |        |        |
+| Source-Handle-Reference           |                                                                                                                                                                                                                                  |        |        |
+| Calories ingested                 | 268928^MDC_DIM_CAL^MDC<br>NOTE – The underlying standard uses<br>MDC_DIM_X_CAL but this is translated to<br>MDC_DIM_CAL for the Services interface                                                                               |        |        |
+
+**Table E.24 – Cardiovascular fitness and activity monitor encoding – Part 2**
+
+| Description                           | OBX-6                                                                                                                                                                                                 | OBX-18 | OBX-20 |
+|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|
+| Carbohydrate calories ingested        | 268928^MDC_DIM_CAL^MDC<br>NOTE – The underlying standard uses MDC_DIM_X_CAL but this is translated to MDC_DIM_CAL for the Services interface                                                          |        |        |
+| Source-Handle-Reference               |                                                                                                                                                                                                       |        |        |
+| Sustained phys activity threshold     | 264352^MDC_DIM_MIN^MDC                                                                                                                                                                                |        |        |
+| Source-Handle-Reference               |                                                                                                                                                                                                       |        |        |
+| Activity intensity                    | 262688^MDC_DIM_PERCENT^MDC                                                                                                                                                                            |        |        |
+| Source-Handle-Reference               |                                                                                                                                                                                                       |        |        |
+| Body weight                           | 263872^MDC_DIM_G^MDC or 263904^MDC_DIM_LB^MDC<br>NOTE – The underlying standard uses DIM_X_G and MDC_DIM_X_LB but this is translated to MDC_DIM_G and MDC_DIM_LB for the Services interface           |        |        |
+| Height                                | 263424^MDC_DIM_M^MDC or 263488^MDC_DIM_FOOT^MDC<br>NOTE – The underlying standard uses MDC_DIM_X_M and MDC_DIM_X_FOOT but this is translated to MDC_DIM_M and MDC_DIM_FOOT for the Services interface |        |        |
+| Age                                   | 264512^MDC_DIM_YR^MDC                                                                                                                                                                                 |        |        |
+| Activity time                         |                                                                                                                                                                                                       |        |        |
+| Measure active period (Activity time) | 264320^MDC_DIM_SEC^MDC                                                                                                                                                                                |        |        |
+
+**Table E.24 – Cardiovascular fitness and activity monitor encoding – Part 2**
+
+| <b>Description</b>      | <b>OBX-6</b> | <b>OBX-18</b> | <b>OBX-20</b> |
+|-------------------------|--------------|---------------|---------------|
+| Source-Handle-Reference |              |               |               |
+| Program identifier      |              |               |               |
+| Source-Handle-Reference |              |               |               |
+
+### E.3.8 10442 Strength fitness equipment
+
+#### E.3.8.1 Modelling
+
+All measurements for this device belong to *sets*. This natural hierarchy is expressed through the PCD-01 containment hierarchy and shown in the following tables.
+
+#### E.3.8.2 Transformations
+
+The following transformations are performed in the encoding of this device.
+
+Several nomenclature codes have been harmonized with the underlying base codes. These are pointed out in the tables below.
+
+#### E.3.8.3 Containment tree
+
+Table E.25 shows a strength fitness equipment containment tree.
+
+**Table E.25 – Strength fitness equipment containment tree**
+
+| <b>REFID</b>                      | <b>Description</b>                                                |
+|-----------------------------------|-------------------------------------------------------------------|
+| MDC_DEV_SPEC_PROFILE_HF_STRENGTH  | Strength fitness equipment MDS                                    |
+| ... MDC_HF_SET                    | Set                                                               |
+| .... MDC_ATTR_TIME_PD_MSMT_ACTIVE | Measure active period                                             |
+| ... MDC_HF_REP_COUNT              | Repetition count                                                  |
+| .... MDC_SOURCE_HANDLE_REF        | Source-Handle-Reference<br>Reference to the corresponding session |
+
+**Table E.25 – Strength fitness equipment containment tree**
+
+| REFID                          | Description                                                       |
+|--------------------------------|-------------------------------------------------------------------|
+| ... MDC_HF_RESISTANCE          | Resistance                                                        |
+| .... MDC_SOURCE_HANDLE_REF     | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_REPETITION          | Repetition                                                        |
+| .... MDC_SOURCE_HANDLE_REF     | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_EXERCISE_POSITION   | Exercise position                                                 |
+| .... MDC_SOURCE_HANDLE_REF     | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_EXERCISE_LATERALITY | Exercise laterality                                               |
+| .... MDC_SOURCE_HANDLE_REF     | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_EXERCISE_GRIP       | Exercise grip                                                     |
+| .... MDC_SOURCE_HANDLE_REF     | Source-Handle-Reference<br>Reference to the corresponding session |
+| ... MDC_HF_EXERCISE_MOVEMENT   | Exercise movement                                                 |
+| .... MDC_SOURCE_HANDLE_REF     | Source-Handle-Reference<br>Reference to the corresponding session |
+
+#### E.3.8.4 OBX encoding
+
+Table E.26 and Table E.27 show part 1 and part 2 (respectively) of a strength fitness equipment encoding.
+
+**Table E.26 – Strength fitness equipment encoding – Part 1**
+
+| Description                | OBX-2 | OBX-3                            | OBX-4 | OBX-5 |
+|----------------------------|-------|----------------------------------|-------|-------|
+| Strength fitness equipment |       | 528426^MDC_DEV_SPEC_PROFILE_HF_S | 1     |       |
+
+**Table E.26 – Strength fitness equipment encoding – Part 1**
+
+| <b>Description</b>      | <b>OBX-2</b> | <b>OBX-3</b>                               | <b>OBX-4</b> | <b>OBX-5</b>                                                                                                      |
+|-------------------------|--------------|--------------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------|
+| MDS                     |              | TRENGTH^MDC                                |              |                                                                                                                   |
+| Set                     | NM           | 8454344^MDC_HF_SET^MDC                     | 1.0.0.1      |                                                                                                                   |
+| Measure active period   | NM           | 68185^MDC_ATTR_TIME_PD_MSMT_AC<br>TIVE^MDC | 1.0.0.1.1    | 25.3                                                                                                              |
+| Repetition count        | NM           | 8454346^MDC_HF_REPETITION_COUNT^<br>MDC    | 1.0.0.2      | 50                                                                                                                |
+| Source-Handle-Reference | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_R<br>EF^MDC   | 1.0.0.2.1    | 1.0.0.1                                                                                                           |
+| Resistance              | NM           | 8454347^MDC_HF_RESISTANCE^MDC              | 1.0.0.3      | 25                                                                                                                |
+| Source-Handle-Reference | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_R<br>EF^MDC   | 1.0.0.3.1    | 1.0.0.1                                                                                                           |
+| Repetition              | NM           | 8454345^MDC_HF_REPETITION^MDC              | 1.0.0.4      | 10                                                                                                                |
+| Source-Handle-Reference | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_R<br>EF^MDC   | 1.0.0.4.1    | 1.0.0.1                                                                                                           |
+| Exercise position       | CWE          | 8454348^MDC_HF_EXERCISE_POSITION<br>^MDC   | 1.0.0.5      | Any of the exercise position values defined in 10442. For example...<br>8455347^MDC_HF_POSITION_INCLINE^MDC       |
+| Source-Handle-Reference | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_R<br>EF^MDC   | 1.0.0.5.1    | 1.0.0.1                                                                                                           |
+| Exercise laterality     | CWE          | 8454349^MDC_HF_EXERCISE_LATERALI<br>TY^MDC | 1.0.0.6      | Any of the exercise laterality values defined in 10442. For example...<br>8455345^MDC_HF_LATERALITY_RIGHT^MD<br>C |
+| Source-Handle-Reference | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_R<br>EF^MDC   | 1.0.0.6.1    | 1.0.0.1                                                                                                           |
+| Exercise grip           | CWE          | 8454350^MDC_HF_EXERCISE_GRIP^MD<br>C       | 1.0.0.7      | Any of the grip values defined in 10442. For example...<br>8455546^MDC_HF_GRIP_UNDERHAND^MDC                      |
+
+**Table E.26 – Strength fitness equipment encoding – Part 1**
+
+| <b>Description</b>      | <b>OBX-2</b> | <b>OBX-3</b>                             | <b>OBX-4</b> | <b>OBX-5</b>                                                                                            |
+|-------------------------|--------------|------------------------------------------|--------------|---------------------------------------------------------------------------------------------------------|
+| Source-Handle-Reference | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_R<br>EF^MDC | 1.0.0.7.1    | 1.0.0.1                                                                                                 |
+| Exercise movement       | CWE          | 8454351^MDC_HF_EXERCISE_MOVEME<br>NT^MDC | 1.0.0.8      | Any of the movement values defined in 10442. For example...<br>8455446^MDC_HF_MOVEMENT_ROTATION^<br>MDC |
+| Source-Handle-Reference | ST           | 68167^MDC_ATTR_SOURCE_HANDLE_R<br>EF^MDC | 1.0.0.8.1    | 1.0.0.1                                                                                                 |
+
+**Table E.27 – Strength fitness equipment encoding – Part 2**
+
+| <b>Description</b>                | <b>OBX-6</b>                                                                                                                                                      | <b>OBX-18</b>                                 | <b>OBX-20</b>                                                                                                |
+|-----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------------------------------------------------------------------|
+| Strength fitness equipment<br>MDS |                                                                                                                                                                   | 0123456789ABCDEF^^012345678<br>9ABCDEF^EUI-64 |                                                                                                              |
+| Set                               |                                                                                                                                                                   |                                               | Any of the muscle sites defined in<br>10442. For example...<br>459284^MDC_MUSC_THORAX_PE<br>CTORAL_MAJOR^MDC |
+| Measure active period             | 264320^MDC_DIM_SEC^MDC                                                                                                                                            |                                               |                                                                                                              |
+| Repetition count                  | Leave blank or<br>262656^MDC_DIM_DIMLESS^MDC                                                                                                                      |                                               |                                                                                                              |
+| Source-Handle-Reference           |                                                                                                                                                                   |                                               |                                                                                                              |
+| Resistance                        | 262656^MDC_DIM_DIMLESS^MDC or<br>263872^MDC_DIM_G^MDC or<br>263904^MDC_DIM_LB^MDC<br>NOTE – The underlying standard uses<br>MDC_DIM_X_G but this is translated to |                                               |                                                                                                              |
+
+**Table E.27 – Strength fitness equipment encoding – Part 2**
+
+| <b>Description</b>      | <b>OBX-6</b>                                                                                                                                                                                                      | <b>OBX-18</b> | <b>OBX-20</b> |
+|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|
+|                         | MDC_DIM_G for the Services interface                                                                                                                                                                              |               |               |
+| Source-Handle-Reference |                                                                                                                                                                                                                   |               |               |
+| Repetition              | 263424^MDC_DIM_M^MDC or<br>263520^MDC_DIM_INCH^MDC<br>NOTE – The underlying standard uses<br>MDC_DIM_X_M and MDC_DIM_X_INCH<br>but this is translated to MDC_DIM_M and<br>MDC_DIM_INCH for the Services interface |               |               |
+| Source-Handle-Reference |                                                                                                                                                                                                                   |               |               |
+| Exercise position       |                                                                                                                                                                                                                   |               |               |
+| Source-Handle-Reference |                                                                                                                                                                                                                   |               |               |
+| Exercise laterality     |                                                                                                                                                                                                                   |               |               |
+| Source-Handle-Reference |                                                                                                                                                                                                                   |               |               |
+| Exercise grip           |                                                                                                                                                                                                                   |               |               |
+| Source-Handle-Reference |                                                                                                                                                                                                                   |               |               |
+| Exercise movement       |                                                                                                                                                                                                                   |               |               |
+| Source-Handle-Reference |                                                                                                                                                                                                                   |               |               |
+
+### **E.3.9 10471 Independent living activity hub**
+
+#### **E.3.9.1 Modelling**
+
+Sensor values are reported using the AI type codes and their bitstring values. Optionally, a FACET value may be transmitted to indicate the sensor identifier and location.
+
+#### **E.3.9.2 Transformations**
+
+The following transformations are performed in the encoding of this device.
+
+- MDC\_ATTR\_SUPPLEMENTAL\_TYPES should be replaced by MDC\_AI\_LOCATION for Services transmission.
+
+- MDC\_ATTR\_SUPPLEMENTAL\_TYPES/MDC\_AI\_LOCATION refIdName should match the MDC\_AI\_LOCATION identifier given by the first 10 bits of the Supplemental-Types attribute and may append " \_<room number>" to this value based upon the value of the lower 6 bits.
+
+### E.3.9.3 Containment tree
+
+Table E.28 shows an Independent living activity hub containment tree.
+
+**Table E.28 – Independent living activity hub containment tree**
+
+| REFID                                 | Description                             |
+|---------------------------------------|-----------------------------------------|
+| MDC_DEV_SPEC_PROFILE_AI_ACTIVITY_HUB  | Independent living activity hub MDS     |
+| ... MDC_AI_TYPE_SENSOR_FALL           | Fall sensor                             |
+| .... MDC_ATTR_SUPPLEMENTAL_TYPES      | Location (Fall sensor)                  |
+| ... MDC_AI_TYPE_SENSOR_PERS           | PERS sensor                             |
+| .... MDC_ATTR_SUPPLEMENTAL_TYPES      | Location (PERS sensor)                  |
+| ... MDC_AI_TYPE_SENSOR_SMOKE          | Environmental sensor – smoke            |
+| .... MDC_ATTR_SUPPLEMENTAL_TYPES      | Location (Environmental sensor – smoke) |
+| ... MDC_AI_TYPE_SENSOR_CO             | Environmental sensor – CO               |
+| .... MDC_ATTR_SUPPLEMENTAL_TYPES      | Location (Environmental sensor – CO)    |
+| ... MDC_AI_TYPE_SENSOR_WATER          | Environmental sensor – water            |
+| .... MDC_ATTR_SUPPLEMENTAL_TYPES      | Location (Environmental sensor – water) |
+| ... MDC_AI_TYPE_SENSOR_GAS            | Environmental sensor – gas              |
+| .... MDC_ATTR_SUPPLEMENTAL_TYPES      | Location (Environmental sensor – gas)   |
+| ... MDC_AI_TYPE_SENSOR_MOTION         | Motion sensor                           |
+| .... MDC_ATTR_SUPPLEMENTAL_TYPES      | Location (Motion sensor)                |
+| ... MDC_AI_TYPE_SENSOR_PROPEXIT       | Property exit sensor                    |
+| .... MDC_ATTR_SUPPLEMENTAL_TYPES      | Location (Exit sensor)                  |
+| ... MDC_AI_TYPE_SENSOR_ENURESIS       | Enuresis sensor                         |
+| .... MDC_ATTR_SUPPLEMENTAL_TYPES      | Location (Enuresis sensor)              |
+| ... MDC_AI_TYPE_SENSOR_CONTACTCLOSURE | Contact closure sensor                  |
+
+**Table E.28 – Independent living activity hub containment tree**
+
+| REFID                            | Description                       |
+|----------------------------------|-----------------------------------|
+| .... MDC_ATTR_SUPPLEMENTAL_TYPES | Location (Contact closure sensor) |
+| ... MDC_AI_TYPE_SENSOR_USAGE     | Usage sensor                      |
+| .... MDC_ATTR_SUPPLEMENTAL_TYPES | Location (Usage sensor)           |
+| ... MDC_AI_TYPE_SENSOR_SWITCH    | Switch sensor                     |
+| .... MDC_ATTR_SUPPLEMENTAL_TYPES | Location (Switch sensor)          |
+| ... MDC_AI_TYPE_SENSOR_DOSAGE    | Medication dosage sensor          |
+| .... MDC_ATTR_SUPPLEMENTAL_TYPES | Location (Dosage sensor)          |
+| ... MDC_AI_TYPE_SENSOR_TEMP      | Temperature sensor                |
+| .... MDC_ATTR_SUPPLEMENTAL_TYPES | Location (Temperature sensor)     |
+
+**E.3.9.4 OBX encoding**
+
+Table E.29 and Table E.30 show part 1 and part 2 (respectively) of an independent living activity hub encoding.
+
+**Table E.29 – Independent living activity hub encoding – Part 1**
+
+| Description                         | OBX-2 | OBX-3                                           | OBX-4   | OBX-5                                                                                                                                                                                                                                                                                           |
+|-------------------------------------|-------|-------------------------------------------------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Independent living activity hub MDS |       | 528455^MDC_DEV_SPEC_PROFILE_AI_ACTIVITY_HUB^MDC | 1       |                                                                                                                                                                                                                                                                                                 |
+| Fall sensor                         | CWE   | 8519681^MDC_AI_TYPE_SENSOR_FALL^MDC             | 1.0.0.1 | One of the following flags...<br><0 or 1>^fall-detected(0)<br>Additionally, optionally, any of the general sensor health flags...<br><0 or 1>^auto-presence-received(16),<br><0 or 1>^auto-presence-failed(17),<br><0 or 1>^low-battery(18),<br><0 or 1>^fault(19),<br><0 or 1>^end-of-life(20) |
+
+**Table E.29 – Independent living activity hub encoding – Part 1**
+
+| Description                  | OBX-2 | OBX-3                                                                | OBX-4     | OBX-5                                                                                                                                                                                                                                                                                                |
+|------------------------------|-------|----------------------------------------------------------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location (Fall sensor)       | CWE   | 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC | 1.0.0.1.1 | Any of the 10471 location codes that are specified in the Supplemental-Types.<br>For example:<br>8523328^MDC_AI_LOCATION_LIVINGROOM^MDC                                                                                                                                                              |
+| PERS sensor                  | CWE   | 8519682^MDC_AI_TYPE_SENSOR_PERS^MDC                                  | 1.0.0.2   | One of the following flags...<br><0 or 1>^pers-activated(0)<br>Additionally, optionally, any of the general sensor health flags...<br><0 or 1>^auto-presence-received(16),<br><0 or 1>^auto-presence-failed(17),<br><0 or 1>^low-battery(18),<br><0 or 1>^fault(19),<br><0 or 1>^end-of-life(20)     |
+| Location (PERS sensor)       | CWE   | 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC | 1.0.0.2.1 | Any of the 10471 location codes that are specified in the Supplemental-Types.<br>For example:<br>8523328^MDC_AI_LOCATION_LIVINGROOM^MDC                                                                                                                                                              |
+| Environmental sensor - smoke | CWE   | 8519683^MDC_AI_TYPE_SENSOR_SMOKE^MDC                                 | 1.0.0.3   | One of the following flags...<br><0 or 1>^condition-detected(0)<br>Additionally, optionally, any of the general sensor health flags...<br><0 or 1>^auto-presence-received(16),<br><0 or 1>^auto-presence-failed(17),<br><0 or 1>^low-battery(18),<br><0 or 1>^fault(19),<br><0 or 1>^end-of-life(20) |
+
+**Table E.29 – Independent living activity hub encoding – Part 1**
+
+| Description                             | OBX-2 | OBX-3                                                                | OBX-4     | OBX-5                                                                                                                                                                                                                                                                                                |
+|-----------------------------------------|-------|----------------------------------------------------------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location (Environmental sensor - smoke) | CWE   | 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC | 1.0.0.3.1 | Any of the 10471 location codes that are specified in the Supplemental-Types.<br>For example:<br>8523328^MDC_AI_LOCATION_LIVINGROOM^MDC                                                                                                                                                              |
+| Environmental sensor - CO               | CWE   | 8519684^MDC_AI_TYPE_SENSOR_CO^MDC                                    | 1.0.0.4   | One of the following flags...<br><0 or 1>^condition-detected(0)<br>Additionally, optionally, any of the general sensor health flags...<br><0 or 1>^auto-presence-received(16),<br><0 or 1>^auto-presence-failed(17),<br><0 or 1>^low-battery(18),<br><0 or 1>^fault(19),<br><0 or 1>^end-of-life(20) |
+| Location (Environmental sensor - CO)    | CWE   | 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC | 1.0.0.4.1 | Any of the 10471 location codes that are specified in the Supplemental-Types.<br>For example:<br>8523328^MDC_AI_LOCATION_LIVINGROOM^MDC                                                                                                                                                              |
+| Environmental sensor - water            | CWE   | 88519685^MDC_AI_TYPE_SENSOR_WATER^MDC                                | 1.0.0.5   | One of the following flags...<br><0 or 1>^condition-detected(0)<br>Additionally, optionally, any of the general sensor health flags...<br><0 or 1>^auto-presence-received(16),<br><0 or 1>^auto-presence-failed(17),<br><0 or 1>^low-battery(18),<br><0 or 1>^fault(19),<br><0 or 1>^end-of-life(20) |
+
+**Table E.29 – Independent living activity hub encoding – Part 1**
+
+| Description                             | OBX-2 | OBX-3                                                                | OBX-4     | OBX-5                                                                                                                                                                                                                                                                                                                                         |
+|-----------------------------------------|-------|----------------------------------------------------------------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location (Environmental sensor - water) | CWE   | 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC | 1.0.0.5.1 | Any of the 10471 location codes that are specified in the Supplemental-Types.<br>For example:<br>8523328^MDC_AI_LOCATION_LIVINGROOM^MDC                                                                                                                                                                                                       |
+| Environmental sensor - gas              | CWE   | 8519686^MDC_AI_TYPE_SENSOR_GAS^MDC                                   | 1.0.0.6   | <0 or 1>^condition-detected(0)<br>Additionally, optionally, any of the general sensor health flags...<br><0 or 1>^auto-presence-received(16),<br><0 or 1>^auto-presence-failed(17),<br><0 or 1>^low-battery(18),<br><0 or 1>^fault(19),<br><0 or 1>^end-of-life(20)                                                                           |
+| Location (Environmental sensor - gas)   | CWE   | 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC | 1.0.0.6.1 | Any of the 10471 location codes that are specified in the Supplemental-Types.<br>For example:<br>8523328^MDC_AI_LOCATION_LIVINGROOM^MDC                                                                                                                                                                                                       |
+| Motion sensor                           | CWE   | 8519687^MDC_AI_TYPE_SENSOR_MOTION^MDC                                | 1.0.0.7   | One of the following flags...<br><0 or 1>^motion-detected(0),<br><0 or 1>^motion-detected-delayed(1),<br><0 or 1>^tamper-detected(2)<br>Additionally, optionally, any of the general sensor health flags...<br><0 or 1>^auto-presence-received(16),<br><0 or 1>^auto-presence-failed(17),<br><0 or 1>^low-battery(18),<br><0 or 1>^fault(19), |
+
+**Table E.29 – Independent living activity hub encoding – Part 1**
+
+| <b>Description</b>       | <b>OBX-2</b> | <b>OBX-3</b>                                                                | <b>OBX-4</b> | <b>OBX-5</b>                                                                                                                                                                                                                                                                                                                                 |
+|--------------------------|--------------|-----------------------------------------------------------------------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          |              |                                                                             |              | <0 or 1>^end-of-life(20)                                                                                                                                                                                                                                                                                                                     |
+| Location (Motion sensor) | CWE          | 8520703^MDC_AI_LOCATION^MDC or<br>68193^MDC_ATTR_SUPPLEMENTAL_TYPES^<br>MDC | 1.0.0.7.1    | Any of the 10471 location codes that are specified in the Supplemental-Types.<br>For example:<br>8523328^MDC_AI_LOCATION_LIVINGROOM^MDC                                                                                                                                                                                                      |
+| Property exit sensor     | CWE          | 8519688^MDC_AI_TYPE_SENSOR_PROPEXIT^<br>MDC                                 | 1.0.0.8      | One of the following flags...<br><0 or 1>^occupant-exit-property(0),<br><0 or 1>^exit-door-left-open(1)<br>Additionally, optionally, any of the general sensor health flags...<br><0 or 1>^auto-presence-received(16),<br><0 or 1>^auto-presence-failed(17),<br><0 or 1>^low-battery(18),<br><0 or 1>^fault(19),<br><0 or 1>^end-of-life(20) |
+| Location (Exit sensor)   | CWE          | 8520703^MDC_AI_LOCATION^MDC or<br>68193^MDC_ATTR_SUPPLEMENTAL_TYPES^<br>MDC | 1.0.0.8.1    | Any of the 10471 location codes that are specified in the Supplemental-Types.<br>For example:<br>8523328^MDC_AI_LOCATION_LIVINGROOM^MDC                                                                                                                                                                                                      |
+| Enuresis sensor          | CWE          | 8519689^MDC_AI_TYPE_SENSOR_ENURESIS^<br>MDC                                 | 1.0.0.9      | One of the following flags...<br><0 or 1>^enuresis-detected(0)<br>Additionally, optionally, any of the general sensor health flags...<br><0 or 1>^auto-presence-received(16),<br><0 or 1>^auto-presence-failed(17),<br><0 or 1>^low-battery(18),                                                                                             |
+
+**Table E.29 – Independent living activity hub encoding – Part 1**
+
+| <b>Description</b>                | <b>OBX-2</b> | <b>OBX-3</b>                                                                | <b>OBX-4</b> | <b>OBX-5</b>                                                                                                                                                                                                                                                                                                                       |
+|-----------------------------------|--------------|-----------------------------------------------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                   |              |                                                                             |              | <0 or 1>^fault(19),<br><0 or 1>^end-of-life(20)                                                                                                                                                                                                                                                                                    |
+| Location (Enuresis sensor)        | CWE          | 8520703^MDC_AI_LOCATION^MDC or<br>68193^MDC_ATTR_SUPPLEMENTAL_TYPES^<br>MDC | 1.0.0.9.1    | Any of the 10471 location codes that are<br>specified in the Supplemental-Types.<br>For example:<br>8523328^MDC_AI_LOCATION_LIVINGROO<br>M^MDC                                                                                                                                                                                     |
+| Contact closure sensor            | CWE          | 8519690^MDC_AI_TYPE_SENSOR_CONTACT<br>CLOSURE^MDC                           | 1.0.0.10     | One of the following flags...<br><0 or 1>^contact-opened(0),<br><0 or 1>^contact-closed(1)<br>Additionally, optionally, any of the general<br>sensor health flags...<br><0 or 1>^auto-presence-received(16),<br><0 or 1>^auto-presence-failed(17),<br><0 or 1>^low-battery(18),<br><0 or 1>^fault(19),<br><0 or 1>^end-of-life(20) |
+| Location (Contact closure sensor) | CWE          | 8520703^MDC_AI_LOCATION^MDC or<br>68193^MDC_ATTR_SUPPLEMENTAL_TYPES^<br>MDC | 1.0.0.10.1   | Any of the 10471 location codes that are<br>specified in the Supplemental-Types.<br>For example:<br>8523328^MDC_AI_LOCATION_LIVINGROO<br>M^MDC                                                                                                                                                                                     |
+| Usage sensor                      | CWE          | 8519691^MDC_AI_TYPE_SENSOR_USAGE^M<br>DC                                    | 1.0.0.11     | One of the following flags...<br><0 or 1>^usage-started(0),<br><0 or 1>^usage-ended(1),<br><0 or 1>^expected-use-start-violation(2),<br><0 or 1>^expected-use-stop-violation(3),<br><0 or 1>^absence-violation(4)                                                                                                                  |
+
+**Table E.29 – Independent living activity hub encoding – Part 1**
+
+| Description              | OBX-2 | OBX-3                                                                | OBX-4      | OBX-5                                                                                                                                                                                                                                                                                                                  |
+|--------------------------|-------|----------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          |       |                                                                      |            | Additionally, optionally, any of the general sensor health flags...<br><0 or 1>^auto-presence-received(16),<br><0 or 1>^auto-presence-failed(17),<br><0 or 1>^low-battery(18),<br><0 or 1>^fault(19),<br><0 or 1>^end-of-life(20)                                                                                      |
+| Location (Usage sensor)  | CWE   | 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC | 1.0.0.11.1 | Any of the 10471 location codes that are specified in the Supplemental-Types.<br>For example:<br>8523328^MDC_AI_LOCATION_LIVINGROOM^MDC                                                                                                                                                                                |
+| Switch sensor            | CWE   | 8519692^MDC_AI_TYPE_SENSOR_SWITCH^MDC                                | 1.0.0.12   | One of the following flags...<br><0 or 1>^switch-on(0),<br><0 or 1>^switch-off(1)<br>Additionally, optionally, any of the general sensor health flags...<br><0 or 1>^auto-presence-received(16),<br><0 or 1>^auto-presence-failed(17),<br><0 or 1>^low-battery(18),<br><0 or 1>^fault(19),<br><0 or 1>^end-of-life(20) |
+| Location (Switch sensor) | CWE   | 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC | 1.0.0.12.1 | Any of the 10471 location codes that are specified in the Supplemental-Types.<br>For example:<br>8523328^MDC_AI_LOCATION_LIVINGROOM^MDC                                                                                                                                                                                |
+
+**Table E.29 – Independent living activity hub encoding – Part 1**
+
+| Description              | OBX-2 | OBX-3                                                                | OBX-4      | OBX-5                                                                                                                                                                                                                                                                                                                                                                                        |
+|--------------------------|-------|----------------------------------------------------------------------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Medication dosage sensor | CWE   | 8519693^MDC_AI_TYPE_SENSOR_DOSAGE^MDC                                | 1.0.0.13   | One of the following flags...<br><0 or 1>^dosage-taken(0),<br><0 or 1>^dosage-missed(1)<br>Additionally, optionally, any of the general sensor health flags...<br><0 or 1>^auto-presence-received(16),<br><0 or 1>^auto-presence-failed(17),<br><0 or 1>^low-battery(18),<br><0 or 1>^fault(19),<br><0 or 1>^end-of-life(20)                                                                 |
+| Location (Dosage sensor) | CWE   | 8520703^MDC_AI_LOCATION^MDC or 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC | 1.0.0.13.1 | Any of the 10471 location codes that are specified in the Supplemental-Types.<br>For example:<br>8523328^MDC_AI_LOCATION_LIVINGROOM^MDC                                                                                                                                                                                                                                                      |
+| Temperature sensor       | CWE   | 8519694^MDC_AI_TYPE_SENSOR_TEMP^MDC                                  | 1.0.0.14   | One of the following flags...<br><0 or 1>^high-temperature-detected(0),<br><0 or 1>^low-temperature-detected(1),<br><0 or 1>^rate-of-change-too-fast(2)<br>Additionally, optionally, any of the general sensor health flags...<br><0 or 1>^auto-presence-received(16),<br><0 or 1>^auto-presence-failed(17),<br><0 or 1>^low-battery(18),<br><0 or 1>^fault(19),<br><0 or 1>^end-of-life(20) |
+
+**Table E.29 – Independent living activity hub encoding – Part 1**
+
+| <b>Description</b>            | <b>OBX-2</b> | <b>OBX-3</b>                                                                | <b>OBX-4</b> | <b>OBX-5</b>                                                                                                                            |
+|-------------------------------|--------------|-----------------------------------------------------------------------------|--------------|-----------------------------------------------------------------------------------------------------------------------------------------|
+| Location (Temperature sensor) | CWE          | 8520703^MDC_AI_LOCATION^MDC or<br>68193^MDC_ATTR_SUPPLEMENTAL_TYPES^<br>MDC | 1.0.0.14.1   | Any of the 10471 location codes that are specified in the Supplemental-Types.<br>For example:<br>8523328^MDC_AI_LOCATION_LIVINGROOM^MDC |
+
+**Table E.30 – Independent living activity hub encoding – Part 2**
+
+| <b>Description</b>                      | <b>OBX-6</b> | <b>OBX-18</b>                             | <b>OBX-20</b> |
+|-----------------------------------------|--------------|-------------------------------------------|---------------|
+| Independent living activity hub MDS     |              | 0123456789ABCDEF^^0123456789ABCDEF^EUI-64 |               |
+| Fall sensor                             |              |                                           |               |
+| Location (Fall sensor)                  |              |                                           |               |
+| PERS sensor                             |              |                                           |               |
+| Location (PERS sensor)                  |              |                                           |               |
+| Environmental sensor - smoke            |              |                                           |               |
+| Location (Environmental sensor - smoke) |              |                                           |               |
+| Environmental sensor - CO               |              |                                           |               |
+| Location (Environmental sensor - CO)    |              |                                           |               |
+| Environmental sensor - water            |              |                                           |               |
+| Location (Environmental sensor - water) |              |                                           |               |
+| Environmental sensor - gas              |              |                                           |               |
+| Location (Environmental sensor - gas)   |              |                                           |               |
+| Motion sensor                           |              |                                           |               |
+| Location (Motion sensor)                |              |                                           |               |
+
+**Table E.30 – Independent living activity hub encoding – Part 2**
+
+| <b>Description</b>                | <b>OBX-6</b> | <b>OBX-18</b> | <b>OBX-20</b> |
+|-----------------------------------|--------------|---------------|---------------|
+| Property Exit sensor              |              |               |               |
+| Location (Exit sensor)            |              |               |               |
+| Enuresis sensor                   |              |               |               |
+| Location (Enuresis sensor)        |              |               |               |
+| Contact closure sensor            |              |               |               |
+| Location (Contact closure sensor) |              |               |               |
+| Usage sensor                      |              |               |               |
+| Location (Usage sensor)           |              |               |               |
+| Switch sensor                     |              |               |               |
+| Location (Switch sensor)          |              |               |               |
+| Medication dosage sensor          |              |               |               |
+| Location (Dosage sensor)          |              |               |               |
+| Temperature sensor                |              |               |               |
+| Location (Temperature sensor)     |              |               |               |
+
+### **E.3.10 10472 Adherence monitor**
+
+#### **E.3.10.1 Modelling**
+
+All attributes are metrics of the Adherence monitor object. Note that the feedback object has a compound attribute and its containment OBX is placed on the channel n-tuple.
+
+#### **E.3.10.2 Transformations**
+
+The following transformations are performed in the encoding of this device.
+
+A nomenclature code has been harmonized with the underlying base code. This is pointed out in the tables below.
+
+### E.3.10.3 Containment tree
+
+Table E.31 shows an adherence monitor containment tree.
+
+**Table E.31 – Adherence monitor containment tree**
+
+| REFID                              | Description               |
+|------------------------------------|---------------------------|
+| MDC_DEV_SPEC_PROFILE_AI_MED_MINDER | Adherence monitor MDS     |
+| ... MDC_AI_MED_DISPENSED_FIXED     | Fixed dosage dispensed    |
+| ... MDC_AI_MED_DISPENSED_VARIABLE  | Variable dosage dispensed |
+| .. MDC_AI_MED_FEEDBACK             | User feedback channel     |
+| ... MDC_AI_MED_UF_LOCATION         | User feedback location    |
+| ... MDC_AI_MED_UF_RESPONSE         | User feedback response    |
+| ... MDC_AI_MED_STATUS              | Status reporter           |
+| ... MDC_ATTR_CONTEXT_KEY           | Context key               |
+
+### E.3.10.4 OBX encoding
+
+Table E.32 and Table E.33 show part 1 and part 2 (respectively) of an adherence monitor encoding
+
+**Table E.32 – Adherence monitor encoding – Part 1**
+
+| Description               | OBX-2 | OBX-3                                             | OBX-4   | OBX-5 |
+|---------------------------|-------|---------------------------------------------------|---------|-------|
+| Adherence monitor MDS     |       | 528456^MDC_DEV_SPEC_PROFILE_AI_M<br>ED_MINDER^MDC | 1       |       |
+| Fixed dosage dispensed    | NM    | 8532992^MDC_AI_MED_DISPENSED_FIX<br>ED^MDC        | 1.0.0.1 | 44    |
+| Variable dosage dispensed | NM    | 8532993^MDC_AI_MED_DISPENSED_VAR<br>IABLE^MDC     | 1.0.0.2 | 1.5   |
+| User feedback channel     | NA    | 8532995^MDC_AI_MED_FEEDBACK^MDC                   | 1.0.1   | 5^3   |
+| User feedback location    | NM    | 8532996^MDC_AI_MED_UF_LOCATION^<br>MDC            | 1.0.1.1 | 5     |
+
+**Table E.32 – Adherence monitor encoding – Part 1**
+
+| <b>Description</b>     | <b>OBX-2</b> | <b>OBX-3</b>                           | <b>OBX-4</b> | <b>OBX-5</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|------------------------|--------------|----------------------------------------|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| User feedback response | NM           | 8532997^MDC_AI_MED_UF_RESPONSE^<br>MDC | 1.0.1.2      | 3                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| Status reporter        | CWE          | 8532994^MDC_AI_MED_STATUS^MDC          | 1.0.0.3      | Any of the status flags...<br><0 or 1>^medication-not-dispensed-as-expected(0)<br><0 or 1>^medication-dispensed-unexpectedly(1)<br><0 or 1>^medication-unfit(2)<br><0 or 1>^medication-expiration(3)<br><0 or 1>^medication-course-complete(4)<br><0 or 1>^medication-taken-incorrectly(5)<br><0 or 1>^medication-course-reloaded(6)<br><0 or 1>^monitor-tamper(7)<br><0 or 1>^monitor-environmental-exceeded-high(8)<br><0 or 1>^monitor-environmental-exceeded-low(9)<br><0 or 1>^monitor-inoperable(10)<br><0 or 1>^consumer-non-compliant-yellow(11)<br><0 or 1>^consumer-non-compliant-red(12) |
+| Context key            | EI           | 68216^MDC_ATTR_CONTEXT_KEY^MDC         | 1.0.0.4      | 0123456789ABCDEF^^0123456789ABCDEF^EUI-64                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+**Table E.33 – Adherence monitor encoding – Part 2**
+
+| <b>Description</b>        | <b>OBX-6</b>                                                   | <b>OBX-18</b>                             | <b>OBX-20</b> |
+|---------------------------|----------------------------------------------------------------|-------------------------------------------|---------------|
+| Adherence monitor MDS     |                                                                | 0123456789ABCDEF^^0123456789ABCDEF^EUI-64 |               |
+| Fixed dosage dispensed    | Leave blank or 262656^MDC_DIM_DIMLESS^MDC                      |                                           |               |
+| Variable dosage dispensed | 236762^MDC_DIM_MILLI_L^MDC or<br>263890^MDC_DIM_MILLI_G^MDC or |                                           |               |
+
+**Table E.33 – Adherence monitor encoding – Part 2**
+
+| <b>Description</b>     | <b>OBX-6</b>                                                                                                                                                         | <b>OBX-18</b> | <b>OBX-20</b> |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|
+|                        | 267616^MDC_DIM_INTL_UNIT^MDC<br>NOTE – The underlying standard uses<br>MDC_DIM_X_INTL_UNIT but this is translated to<br>MDC_DIM_INTL_UNIT for the Services interface |               |               |
+| User feedback channel  | Leave blank or 262656^MDC_DIM_DIMLESS^MDC                                                                                                                            |               |               |
+| User feedback location | Leave blank or 262656^MDC_DIM_DIMLESS^MDC                                                                                                                            |               |               |
+| User feedback response | Leave blank or 262656^MDC_DIM_DIMLESS^MDC                                                                                                                            |               |               |
+| Status reporter        |                                                                                                                                                                      |               |               |
+
+### **E.3.11 10421 Peak expiratory flow monitor**
+
+NOTE – Specialization not final at time of authoring.
+
+#### **E.3.11.1 Modelling**
+
+All attributes are metrics of the peak expiratory flow monitor object.
+
+#### **E.3.11.2 Transformations**
+
+The following transformations are performed in the encoding of this device.
+
+A nomenclature code has been harmonized with the underlying base code. This is pointed out in the tables below.
+
+#### **E.3.11.3 Containment tree**
+
+Table E.34 shows a peak expiratory flow containment tree.
+
+**Table E.34 – Peak expiratory flow containment tree**
+
+| <b>REFID</b>                         | <b>Description</b>        |
+|--------------------------------------|---------------------------|
+| MDC_DEV_SPEC_PROFILE_PEFM            | Peak expiratory flow MDS  |
+| ... MDC_FLOW_AWAY_EXP_FORCED_PEAK    | PEF                       |
+| .... MDC_ATTR_MSMT_STAT              | Measurement status (PEF)  |
+| ... MDC_FLOW_AWAY_EXP_FORCED_PEAK_PB | Personal best             |
+| ... MDC_FLOW_AWAY_EXP_FORCED_PEAK_1S | FEV1                      |
+| .... MDC_ATTR_MSMT_STAT              | Measurement status (FEV1) |
+| ... MDC_FLOW_AWAY_EXP_FORCED_PEAK_6S | FEV6                      |
+| .... MDC_ATTR_MSMT_STAT              | Measurement status (FEV6) |
+
+#### E.3.11.4 OBX encoding
+
+Table E.35 and Table E.36 show part 1 and part 2 (respectively) of a peak expiratory flow monitor encoding.
+
+**Table E.35 – Peak expiratory flow monitor encoding – Part 1**
+
+| <b>Description</b>       | <b>OBX-2</b> | <b>OBX-3</b>                                    | <b>OBX-4</b> | <b>OBX-5</b>                                                                                                                                                                             |
+|--------------------------|--------------|-------------------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Peak expiratory flow MDS |              | 528405^MDC_DEV_SPEC_PROFILE_PEFM^MDC            | 1            |                                                                                                                                                                                          |
+| PEF                      | NM           | 152584^MDC_FLOW_AWAY_EXP_FORCED_<br>PEAK^MDC    | 1.0.0.1      | 67.3                                                                                                                                                                                     |
+| Measurement status (PEF) | CWE          | 67911^MDC_ATTR_MSMT_STAT^MDC                    | 1.0.0.1.1    | Any of the following flags...<br><0 or 1>^msmt-stat-post-med(0) or<br><0 or 1>^msmt-stat-cough(1) or<br><0 or 1>^msmt-stat-short-effort(2) or<br><0 or 1>^msmt-stat-long-time-to-peak(3) |
+| Personal best            | NM           | 152585^MDC_FLOW_AWAY_EXP_FORCED_<br>PEAK_PB^MDC | 1.0.0.2      | 33.5                                                                                                                                                                                     |
+| FEV1                     | NM           | 152586^MDC_FLOW_AWAY_EXP_FORCED_<br>PEAK_1S^MDC | 1.0.0.3      | 44.5                                                                                                                                                                                     |
+
+**Table E.35 – Peak expiratory flow monitor encoding – Part 1**
+
+| <b>Description</b>        | <b>OBX-2</b> | <b>OBX-3</b>                                    | <b>OBX-4</b> | <b>OBX-5</b>                                                                                                                                                                             |
+|---------------------------|--------------|-------------------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Measurement status (FEV1) | CWE          | 67911^MDC_ATTR_MSMT_STAT^MDC                    | 1.0.0.3.1    | Any of the following flags...<br><0 or 1>^msmt-stat-post-med(0) or<br><0 or 1>^msmt-stat-cough(1) or<br><0 or 1>^msmt-stat-short-effort(2) or<br><0 or 1>^msmt-stat-long-time-to-peak(3) |
+| FEV6                      | NM           | 152587^MDC_FLOW_AWAY_EXP_FORCED_<br>PEAK_6S^MDC | 1.0.0.4      | 55.6                                                                                                                                                                                     |
+| Measurement status (FEV6) | CWE          | 67911^MDC_ATTR_MSMT_STAT^MDC                    | 1.0.0.4.1    | Any of the following flags...<br><0 or 1>^msmt-stat-post-med(0) or<br><0 or 1>^msmt-stat-cough(1) or<br><0 or 1>^msmt-stat-short-effort(2) or<br><0 or 1>^msmt-stat-long-time-to-peak(3) |
+
+**Table E.36 – Peak expiratory flow monitor encoding – Part 2**
+
+| <b>Description</b>       | <b>OBX-6</b>                                                                                                                                                                 | <b>OBX-18</b>                             | <b>OBX-20</b> |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|---------------|
+| Peak expiratory flow MDS |                                                                                                                                                                              | 0123456789ABCDEF^^0123456789ABCDEF^EUI-64 |               |
+| PEF                      | 264992^MDC_DIM_L_PER_MIN^MDC<br><br>NOTE – The underlying standard uses<br>MDC_DIM_X_L_PER_MIN but this is translated<br>to MDC_DIM_L_PER_MIN for the Services<br>interface. |                                           |               |
+| Measurement status (PEF) |                                                                                                                                                                              |                                           |               |
+| Personal best            | 264992^MDC_DIM_L_PER_MIN^MDC<br><br>NOTE – The underlying standard uses<br>MDC_DIM_X_L_PER_MIN but this is translated                                                        |                                           |               |
+
+**Table E.36 – Peak expiratory flow monitor encoding – Part 2**
+
+| <b>Description</b>        | <b>OBX-6</b>                                                                                                                           | <b>OBX-18</b> | <b>OBX-20</b> |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|
+|                           | to MDC_DIM_L_PER_MIN for the Services interface.                                                                                       |               |               |
+| FEV1                      | 263744^MDC_DIM_L^MDC<br>NOTE – The underlying standard uses MDC_DIM_X_L but this is translated to MDC_DIM_L for the Services interface |               |               |
+| Measurement status (FEV1) |                                                                                                                                        |               |               |
+| FEV6                      | 263744^MDC_DIM_L^MDC<br>NOTE – The underlying standard uses MDC_DIM_X_L but this is translated to MDC_DIM_L for the Services interface |               |               |
+| Measurement status (FEV6) |                                                                                                                                        |               |               |
+
+### **E.3.12 10420 Body composition analyser**
+
+#### **E.3.12.1 Modelling**
+
+This is modelled with the measurements as individual METRIC level observations.
+
+#### **E.3.12.2 Transformations**
+
+The following transformations are performed in the encoding of this device.
+
+#### **E.3.12.3 Containment tree**
+
+Table E.37 shows a body composition analyser containment tree.
+
+**Table E.37 – Body composition analyser containment tree**
+
+| REFID                          | Description                                                           |
+|--------------------------------|-----------------------------------------------------------------------|
+| MDC_DEV_SPEC_PROFILE_BCA       | Body composition analyzer MDS                                         |
+| ... MDC_BODY_FAT               | Body fat                                                              |
+| ... MDC_LEN_BODY_ACTUAL        | Body height                                                           |
+| ... MDC_MASS_BODY_ACTUAL       | Body weight                                                           |
+| ... MDC_RATIO_MASS_BODY_LEN_SQ | Body Mass Index                                                       |
+| ... MDC_SOURCE_HANDLE_REF      | Source-Handle-Reference<br>Reference to the corresponding body weight |
+| ... MDC_MASS_BODY_FAT_FREE     | Fat free mass                                                         |
+| ... MDC_MASS_BODY_SOFT_LEAN    | Soft lean mass                                                        |
+| ... MDC_BODY_WATER             | Body water                                                            |
+
+### E.3.12.4 OBX encoding
+
+Table E.38 and Table E.39 show part 1 and part 2 (respectively) of a body composition analyser OBX encoding.
+
+**Table E.38 – Body composition analyser OBX encoding – Part 1**
+
+| Description                   | OBX-2 | OBX-3                                 | OBX-4     | OBX-5   |
+|-------------------------------|-------|---------------------------------------|-----------|---------|
+| Body composition analyser MDS |       | 528404^MDC_DEV_SPEC_PROFILE_BCA^MDC   | 1         |         |
+| Body fat                      | NM    | 188748^MDC_BODY_FAT^MDC               | 1.0.0.1   | 28.3    |
+| Body height                   | NM    | 188740^MDC_LEN_BODY_ACTUAL^MDC        | 1.0.0.2   | 175     |
+| Body weight                   | NM    | 188736^MDC_MASS_BODY_ACTUAL^MDC       | 1.0.0.3   | 73.5    |
+| Body Mass Index               | NM    | 188752^MDC_RATIO_MASS_BODY_LEN_SQ^MDC | 1.0.0.4   | 24.0    |
+| Source-Handle-Reference       | ST    | 68167^MDC_ATTR_SOURCE_HANDLE_REF^MDC  | 1.0.0.4.1 | 1.0.0.3 |
+| Fat free mass                 | NM    | 188756^MDC_MASS_BODY_FAT_FREE^MDC     | 1.0.0.5   | 52.6    |
+| Soft lean mass                | NM    | 188760^MDC_MASS_BODY_SOFT_LEAN^MDC    | 1.0.0.6   | 49.1    |
+| Body water                    | NM    | 188764^MDC_BODY_WATER^MDC             | 1.0.0.7   | 38.5    |
+
+**Table E.39 – Body composition analyser OBX encoding – Part 2**
+
+| <b>Description</b>               | <b>OBX-6</b>                                                                           | <b>OBX-18</b>                                 | <b>OBX-20</b> |
+|----------------------------------|----------------------------------------------------------------------------------------|-----------------------------------------------|---------------|
+| Body composition analyser<br>MDS |                                                                                        | 0123456789ABCDEF^^0123456789ABCDEF^<br>EUI-64 |               |
+| Body fat                         | 262688^MDC_DIM_PERCENT^MDC or<br>263875^MDC_DIM_KILO_G^MDC or<br>263904^MDC_DIM_LB^MDC |                                               |               |
+| Body height                      | 263441^MDC_DIM_CENTI_M^MDC or<br>263520^MDC_DIM_INCH^MDC                               |                                               |               |
+| Body weight                      | 263875^MDC_DIM_KILO_G^MDC or<br>263904^MDC_DIM_LB^MDC                                  |                                               |               |
+| Body Mass Index                  | 264096^MDC_DIM_KG_PER_M_SQ^MDC                                                         |                                               |               |
+| Source-Handle-Reference          |                                                                                        |                                               |               |
+| Fat free mass                    | 263875^MDC_DIM_KILO_G^MDC or<br>263904^MDC_DIM_LB^MDC                                  |                                               |               |
+| Soft lean ass                    | 263875^MDC_DIM_KILO_G^MDC or<br>263904^MDC_DIM_LB^MDC                                  |                                               |               |
+| Body water                       | 263875^MDC_DIM_KILO_G^MDC or<br>263904^MDC_DIM_LB^MDC or<br>262688^MDC_DIM_PERCENT^MDC |                                               |               |
+
+### **E.3.13 IEEE 10406 basic 1-3 lead ECG**
+
+#### **E.3.13.1 Modelling**
+
+This is modelled with the measurements as individual METRIC level observations.
+
+#### **E.3.13.2 Transformations**
+
+The following transformations are performed in the encoding of this device.
+
+### E.3.13.3 Containment tree
+
+Table E.40 shows a basic 1-3 lead ECG containment tree.
+
+**Table E.40 – Basic 1-3 lead ECG containment tree**
+
+| REFID                                                                                                                                                                                                                                                                                                                                                                                                                    | Description                                                                              |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|
+| MDC_DEV_SPEC_PROFILE_ECG                                                                                                                                                                                                                                                                                                                                                                                                 | Basic 1-3 Lead ECG MDS                                                                   |
+| ... MDC_ATTR_SYS_TYPE_SPEC_LIST                                                                                                                                                                                                                                                                                                                                                                                          | System-Type-Spec-List, contains profile identifier for Simple ECG and heart rate monitor |
+| ... MDC_ATTR_TICK_RES                                                                                                                                                                                                                                                                                                                                                                                                    | Tick resolution                                                                          |
+| ... MDC_ECG_HEART_RATE or^<br>... MDC_ECG_HEART_RATE_ISNTANT                                                                                                                                                                                                                                                                                                                                                             | Heart rate                                                                               |
+| ... MDC_ECG_TIME_PD_RR_GL                                                                                                                                                                                                                                                                                                                                                                                                | R-R interval                                                                             |
+| ... MDC_ECG_ELEC_POTL or^<br>... MDC_ECG_ELEC_POTL_I or^<br>... MDC_ECG_ELEC_POTL_II or^<br>... MDC_ECG_ELEC_POTL_III or^<br>... MDC_ECG_ELEC_POTL_AVR or^<br>... MDC_ECG_ELEC_POTL_AVL or^<br>... MDC_ECG_ELEC_POTL_AVF or^<br>... MDC_ECG_ELEC_POTL_V1 or^<br>... MDC_ECG_ELEC_POTL_V2 or^<br>... MDC_ECG_ELEC_POTL_V3 or^<br>... MDC_ECG_ELEC_POTL_V4 or^<br>... MDC_ECG_ELEC_POTL_V5 or^<br>... MDC_ECG_ELEC_POTL_V6 | ECG waveform                                                                             |
+| .... MDC_ATTR_TIME_PD_SAMP                                                                                                                                                                                                                                                                                                                                                                                               | ECG waveform sample period                                                               |
+| ... MDC_ECG_DEV_STAT                                                                                                                                                                                                                                                                                                                                                                                                     | Device status                                                                            |
+| ... MDC_ECG_EVT_CTXT_GEN                                                                                                                                                                                                                                                                                                                                                                                                 | Context data trigger                                                                     |
+
+### E.3.13.4 OBX encoding
+
+Table E.41 and Table E.42 show part 1 and part 2 (respectively) of a basic 1-3 lead ECG OBX encoding.
+
+**Table E.41 – Basic 1-3 lead ECG OBX encoding – Part 1**
+
+| Description                | OBX-2 | OBX-3                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | OBX-4     | OBX-5                                                                                                                                                                             |
+|----------------------------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Basic 1-3 Lead ECG MDS     |       | 528384^MDC_DEV_SPEC_PROFILE_HYDRA^MDC                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | 1         |                                                                                                                                                                                   |
+| System-Type-Spec-List      | CWE   | 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | 1.0.0.1   | 528390^MDC_DEV_SPEC_PROFILE_ECG^MDC<br>and at least one of the following two profile values:<br>528524^MDC_DEV_SUB_SPEC_PROFILE_ECG^MDC<br>528525^MDC_DEV_SUB_SPEC_PROFILE_HR^MDC |
+| Tick-Resolution            | NM    | 68229^MDC_ATTR_TICK_RES^MDC                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | 1.0.0.2   | 1024                                                                                                                                                                              |
+| Heart rate                 | NM    | 147842^MDC_ECG_HEART_RATE^MDC or<br>8410590^MDC_ECG_HEART_RATE_INSTANT^MDC                                                                                                                                                                                                                                                                                                                                                                                                                              | 1.0.0.3   | 80                                                                                                                                                                                |
+| R-R interval               | NM    | 147240^MDC_ECG_TIME_PD_RR_GL^MDC                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | 1.0.0.4   | 768                                                                                                                                                                               |
+| ECG waveform               | NA    | 131328^MDC_ECG_ELEC_POTL^MDC or<br>131329^MDC_ECG_ELEC_POTL_I^MDC or<br>131330^MDC_ECG_ELEC_POTL_II^MDC or<br>131389^MDC_ECG_ELEC_POTL_III^MDC or<br>131390^MDC_ECG_ELEC_POTL_AVR^MDC or<br>131391^MDC_ECG_ELEC_POTL_AVL^MDC or<br>131392^MDC_ECG_ELEC_POTL_AVF^MDC or<br>131331^MDC_ECG_ELEC_POTL_V1^MDC or<br>131332^MDC_ECG_ELEC_POTL_V2^MDC or<br>131333^MDC_ECG_ELEC_POTL_V3^MDC or<br>131334^MDC_ECG_ELEC_POTL_V4^MDC or<br>131335^MDC_ECG_ELEC_POTL_V5^MDC or<br>131336^MDC_ECG_ELEC_POTL_V6^MDC | 1.0.0.5   | 11^22^33^44^55^23^33^46^9^...<br>NOTE that the actual values of the waveform may need to be computed based on the scaling values in the Scale-And-Range-Specification object      |
+| ECG waveform Sample-Period | NM    | 67981^MDC_ATTR_TIME_PD_SAMP^MDC                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | 1.0.0.5.1 | 250                                                                                                                                                                               |
+
+**Table E.41 – Basic 1-3 lead ECG OBX encoding – Part 1**
+
+| Description          | OBX-2 | OBX-3                            | OBX-4   | OBX-5                                                                                                                                                                                                                                                                                                                                           |
+|----------------------|-------|----------------------------------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Device status        | CWE   | 8410584^MDC_ECG_DEV_STAT^MDC     | 1.0.0.6 | One of the values...<br><0 or 1>^leadwire-loss(0),<br><0 or 1>^leadsignal-loss(1),<br><0 or 1>^leadwire-loss-first-lead(2),<br><0 or 1>^leadsignal-loss-first-lead(3),<br><0 or 1>^leadwire-loss-second-lead(4),<br><0 or 1>^leadsignal-loss-second-lead(5),<br><0 or 1>^leadwire-loss-third-lead(6),<br><0 or 1>^leadsignal-loss-third-lead(7) |
+| Context data trigger | CWE   | 8410585^MDC_ECG_EVT_CTXT_GEN^MDC | 1.0.0.7 | 8410586^MDC_ECG_EVT_CTXT_USER^MDC or<br>8410587^MDC_ECG_EVT_CTXT_PERIODIC^MDC or<br>8410588^MDC_ECG_EVT_CTXT_DETECTED^MDC or<br>8410589^MDC_ECG_EVT_CTXT_EXTERNAL^MDC                                                                                                                                                                           |
+
+**Table E.42 – Basic 1-3 lead ECG OBX encoding – Part 2**
+
+| <b>Description</b>         | <b>OBX-6</b>                                            | <b>OBX-18</b>                             | <b>OBX-20</b> |
+|----------------------------|---------------------------------------------------------|-------------------------------------------|---------------|
+| Basic 1-3 Lead ECG MDS     |                                                         | 0123456789ABCDEF^^0123456789ABCDEF^EUI-64 |               |
+| System-Type-Spec-List      |                                                         |                                           |               |
+| Tick-Resolution            | 265842^MDC_DIM_PER_SEC^MDC                              |                                           |               |
+| Heart rate                 | 264864^MDC_DIM_BEAT_PER_MIN^MDC                         |                                           |               |
+| R-R interval               | 264338^MDC_DIM_MILLI_SEC^MDC or 268992^MDC_DIM_TICK^MDC |                                           |               |
+| ECG waveform               | 266418^MDC_DIM_MILLI_VOLT^MDC                           |                                           |               |
+| ECG waveform Sample-Period | 264339^MDC_DIM_MICRO_SEC^MDC                            |                                           |               |
+| Device status              |                                                         |                                           |               |
+| Context data trigger       |                                                         |                                           |               |
+
+### **E.3.14 10424 Sleep apnoea breathing therapy equipment (SABTE)**
+
+#### **E.3.14.1 Modelling**
+
+This is modelled with the measurements as individual METRIC level observations.
+
+#### **E.3.14.2 Transformations**
+
+The following transformations are performed in the encoding of this device.
+
+#### **E.3.14.3 Containment tree**
+
+Table E.43 shows a sleep apnoea breathing therapy equipment (SABTE) containment tree.
+
+**Table E.43 – Sleep apnoea breathing therapy equipment (SABTE) containment tree**
+
+| <b>REFID</b>                                                                                                         | <b>Description</b>                                           |
+|----------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------|
+| MDC_DEV_SPEC_PROFILE_SABTE                                                                                           | Sleep apnoea breathing therapy equipment (SABTE) MDS         |
+| ... MDC_PHD_DM_DEV_STAT                                                                                              | PHD DM device status                                         |
+| ... MDC_SABTE_TIME_PD_FLOW_GEN_TOTAL                                                                                 | Duration of flow generation                                  |
+| ... MDC_SABTE_TIME_PD_USAGE_TOTAL or<br>... MDC_SABTE_TIME_PD_USAGE_W_HUM or<br>... MDC_SABTE_TIME_PD_USAGE_WO_HUM   | Duration of patient use                                      |
+| ... MDC_SABTE_TIME_PD_SNORING_TOTAL                                                                                  | Snoring duration                                             |
+| ... MDC_SABTE_TIME_PD_CSR_TOTAL                                                                                      | Cheyne-Stokes respiration (CSR) duration                     |
+| ... MDC_SABTE_TIME_PD_RAMP_SET                                                                                       | Ramp duration setting                                        |
+| ... MDC_SABTE_FLOW_TOTAL or<br>... MDC_SABTE_FLOW_WO_PURGE or<br>... MDC_SABTE_FLOW_RESP                             | Airflow waveform                                             |
+| .... MDC_ATTR_TIME_PD_SAMP                                                                                           | Airflow waveform sample period                               |
+| .. MDC_SABTE_AHI                                                                                                     | Apnoea-Hypopnoea-Index (AHI) compound of uAHI, oAHI and cAHI |
+| ... MDC_SABTE_AHI_UNCLASS                                                                                            | uAHI                                                         |
+| ... MDC_SABTE_AHI_OBSTRUC                                                                                            | oAHI                                                         |
+| ... MDC_SABTE_AHI_CENT                                                                                               | cAHI                                                         |
+| ... MDC_SABTE_AHI_TOTAL or<br>... MDC_SABTE_AHI_UNCLASS or<br>... MDC_SABTE_AHI_OBSTRUC or<br>... MDC_SABTE_AHI_CENT | Apnoea-Hypopnoea-Index (AHI)                                 |
+| ... MDC_SABTE_LVL_HUMID_STAGE_SET or<br>... MDC_SABTE_LVL_HUMID_TEMP_SET or<br>... MDC_SABTE_LVL_HUMID_HUM_SET       | Humidifier level setting                                     |
+| ... MDC_SABTE_LVL_TRIG_SENS_SET                                                                                      | Trigger sensitivity setting                                  |
+| ... MDC_SABTE_LVL_INSP_PRESS_RISE_SET                                                                                | Inspiration pressure rise setting                            |
+
+**Table E.43 – Sleep apnoea breathing therapy equipment (SABTE) containment tree**
+
+| REFID                                                                                                                                                                                                            | Description                                                    |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|
+| ... MDC_SABTE_LVL_ADAPT_SET                                                                                                                                                                                      | Pressure adaption level setting                                |
+| ... MDC_SABTE_MODE_ADAPT_FREEZE_SET                                                                                                                                                                              | Pressure adaption freeze setting                               |
+| ... MDC_SABTE_MODE_AUTOSTARTSTOP_SET                                                                                                                                                                             | Auto start/-stop setting                                       |
+| ... MDC_SABTE_MODE_DEV_SET                                                                                                                                                                                       | Device mode setting                                            |
+| ... MDC_SABTE_MODE_THERAPY_SET                                                                                                                                                                                   | Therapy mode setting                                           |
+| ... MDC_SABTE_PATT_COMPLIANCE_CLS                                                                                                                                                                                | Compliance annotations                                         |
+| ... MDC_SABTE_PATT_EFFICACY_CLS                                                                                                                                                                                  | Efficacy annotations                                           |
+| ... MDC_SABTE_PRESS or<br>... MDC_SABTE_PRESS_TARGET                                                                                                                                                             | Therapy pressure waveform                                      |
+| ... MDC_ATTR_TIME_PD_SAMP                                                                                                                                                                                        | Therapy pressure waveform sample period                        |
+| ... MDC_SABTE_PRESS_MIN or<br>... MDC_SABTE_PRESS_MAX or<br>... MDC_SABTE_PRESS_MEAN or<br>... MDC_SABTE_PRESS_P50 or<br>... MDC_SABTE_PRESS_P90 or<br>... MDC_SABTE_PRESS_P95 or<br>... MDC_SABTE_PRESS_INSTANT | Therapy pressure                                               |
+| ... MDC_SABTE_PRESS_CPAP_SET                                                                                                                                                                                     | Continuous positive airway pressure (P CPAP) setting           |
+| ... MDC_SABTE_PRESS_CPAP_AUTO_MIN_SET                                                                                                                                                                            | Minimal automatic positive airway pressure (Pmin APAP) setting |
+| ... MDC_SABTE_PRESS_CPAP_AUTO_MAX_SET                                                                                                                                                                            | Maximal automatic positive airway pressure (Pmax APAP) setting |
+| ... MDC_SABTE_PRESS_IPAP_SET                                                                                                                                                                                     | Inspiratory positive airway pressure (P IPAP) setting          |
+| ... MDC_SABTE_PRESS_EPAP_SET                                                                                                                                                                                     | Expiratory positive airway pressure (P EPAP) setting           |
+| ... MDC_SABTE_PRESS_RAMP_START_SET                                                                                                                                                                               | Ramp start pressure setting                                    |
+
+**Table E.43 – Sleep apnoea breathing therapy equipment (SABTE) containment tree**
+
+| REFID                                                                                                                                                                                                                                        | Description                    |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|
+| ... MDC_SABTE_RESP_RATE_MIN or<br>... MDC_SABTE_RESP_RATE_MAX or<br>... MDC_SABTE_RESP_RATE_MEAN or<br>... MDC_SABTE_RESP_RATE_P50 or<br>... MDC_SABTE_RESP_RATE_P90 or<br>... MDC_SABTE_RESP_RATE_P95 or<br>... MDC_SABTE_RESP_RATE_INSTANT | Respiratory rate               |
+| ... MDC_SABTE_RESP_RATE_SET                                                                                                                                                                                                                  | Respiratory rate setting       |
+| ... MDC_SABTE_RATIO_IE_MIN or<br>... MDC_SABTE_RATIO_IE_MAX or<br>... MDC_SABTE_RATIO_IE_MEAN or<br>... MDC_SABTE_RATIO_IE_P50 or<br>... MDC_SABTE_RATIO_IE_P90 or<br>... MDC_SABTE_RATIO_IE_P95 or<br>... MDC_SABTE_RATIO_IE_INSTANT        | I:E ratio                      |
+| ... MDC_SABTE_RATIO_IE_SET                                                                                                                                                                                                                   | I:E ratio setting              |
+| ... MDC_SABTE_VOL_LEAK                                                                                                                                                                                                                       | Leakage waveform               |
+| ... MDC_ATTR_TIME_PD_SAMP                                                                                                                                                                                                                    | Leakage waveform sample period |
+| ... MDC_SABTE_VOL_LEAK_MIN or<br>... MDC_SABTE_VOL_LEAK_MAX or<br>... MDC_SABTE_VOL_LEAK_MEAN or<br>... MDC_SABTE_VOL_LEAK_P50 or<br>... MDC_SABTE_VOL_LEAK_P90 or<br>... MDC_SABTE_VOL_LEAK_P95 or<br>... MDC_SABTE_VOL_LEAK_INSTANT        | Leakage                        |
+
+**Table E.43 – Sleep apnoea breathing therapy equipment (SABTE) containment tree**
+
+| REFID                                                                                                                                                                                                                                               | Description               |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| ... MDC_SABTE_VOL_MINUTE_MIN or<br>... MDC_SABTE_VOL_MINUTE_MAX or<br>... MDC_SABTE_VOL_MINUTE_MEAN or<br>... MDC_SABTE_VOL_MINUTE_P50 or<br>... MDC_SABTE_VOL_MINUTE_P90 or<br>... MDC_SABTE_VOL_MINUTE_P95 or<br>... MDC_SABTE_VOL_MINUTE_INSTANT | Respiratory minute volume |
+| ... MDC_SABTE_VOL_TIDAL_MIN or<br>... MDC_SABTE_VOL_TIDAL_MAX or<br>... MDC_SABTE_VOL_TIDAL_MEAN or<br>... MDC_SABTE_VOL_TIDAL_P50 or<br>... MDC_SABTE_VOL_TIDAL_P90 or<br>... MDC_SABTE_VOL_TIDAL_P95 or<br>... MDC_SABTE_VOL_TIDAL_INSTANT        | Tidal volume              |
+
+**E.3.14.4 OBX encoding**
+
+Table E.44 and Table E.45 show part 1 and part 2 (respectively) of a SABTE OBX encoding.
+
+**Table E.44 – Sleep apnoea breathing therapy equipment (SABTE) OBX encoding – Part 1**
+
+| Description                                          | OBX-2 | OBX-3                                     | OBX-4   | OBX-5                                                                                                                                                                                  |
+|------------------------------------------------------|-------|-------------------------------------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Sleep apnoea breathing therapy equipment (SABTE) MDS |       | 528409^MDC_DEV_SPEC_PROFILE_SABTE<br>^MDC | 1       |                                                                                                                                                                                        |
+| PHD DM device status                                 | CWE   | 8408608^MDC_PHD_DM_DEV_STAT^MDC           | 1.0.0.1 | One of the values...<br><0 or 1>^device-status-undetermined(0),<br><0 or 1>^device-status-reset(1),<br><0 or 1>^device-status-error(5),<br><0 or 1>^device-status-error-mechanical(6), |
+
+**Table E.44 – Sleep apnoea breathing therapy equipment (SABTE) OBX encoding – Part 1**
+
+| Description                              | OBX-2 | OBX-3                                                                                                                                       | OBX-4   | OBX-5                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|------------------------------------------|-------|---------------------------------------------------------------------------------------------------------------------------------------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                          |       |                                                                                                                                             |         | <0 or 1>^device-status-error-electronic(7),<br><0 or 1>^device-status-error-software(8),<br><0 or 1>^device-status-error-battery(9),<br><0 or 1>^device-status-service(15),<br><0 or 1>^device-status-service-time-sync-required(16),<br><0 or 1>^device-status-service-calibration-required(17),<br><0 or 1>^device-status-service-replenishment-required(18),<br><0 or 1>^device-status-battery-low(25),<br><0 or 1>^device-status-battery-depleted(26),<br><0 or 1>^device-status-battery-replaced(27),<br><0 or 1>^device-status-battery-interrupted(28) |
+| Duration of flow generation              | NM    | 8410708^MDC_SABTE_TIME_PD_FLOW_GEN_TOTAL^MDC                                                                                                | 1.0.0.2 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| Duration of patient use                  | NM    | 8410712^MDC_SABTE_TIME_PD_USAGE_TOTAL^MDC or<br>8410716^MDC_SABTE_TIME_PD_USAGE_W_HUM ^MDC or<br>8410720^MDC_SABTE_TIME_PD_USAGE_WO_HUM^MDC | 1.0.0.3 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| Snoring duration                         | NM    | 8410724^MDC_SABTE_TIME_PD_SNORING_TOTAL^MDC                                                                                                 | 1.0.0.4 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| Cheyne-Stokes respiration (CSR) duration | NM    | 8410728^MDC_SABTE_TIME_PD_CSR_TOTAL^MDC                                                                                                     | 1.0.0.5 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| Ramp duration setting                    | NM    | 8410744^MDC_SABTE_TIME_PD_RAMP_SET^MDC                                                                                                      | 1.0.0.6 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| Airflow waveform                         | NA    | 8410748^MDC_SABTE_FLOW_TOTAL^MD                                                                                                             | 1.0.0.7 | 11^22^33^44^55^66^77^88^99^...                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+**Table E.44 – Sleep apnoea breathing therapy equipment (SABTE) OBX encoding – Part 1**
+
+| <b>Description</b>                                           | <b>OBX-2</b> | <b>OBX-3</b>                                                                                                                                                  | <b>OBX-4</b> | <b>OBX-5</b>                                                                                                                             |
+|--------------------------------------------------------------|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------|
+|                                                              |              | C or<br>8410752^MDC_SABTE_FLOW_WO_PURGE<br>^MDC or<br>8410756^MDC_SABTE_FLOW_RESP^MDC                                                                         |              | NOTE – The actual values of the waveform may need to be computed based on the scaling values in the Scale-And-Range-Specification object |
+| Airflow waveform sample period                               | NM           | 67981^MDC_ATTR_TIME_PD_SAMP^MDC                                                                                                                               | 1.0.0.7.1    |                                                                                                                                          |
+| Apnoea-Hypopnoea-Index (AHI) compound of uAHI, oAHI and cAHI |              | 8410788^MDC_SABTE_AHI^MDC                                                                                                                                     | 1.0.1.0      |                                                                                                                                          |
+| uAHI                                                         | NM           | 8410796^MDC_SABTE_AHI_UNCLASS^MDC                                                                                                                             | 1.0.1.1      |                                                                                                                                          |
+| oAHI                                                         | NM           | 8410800^MDC_SABTE_AHI_OBSTRUC^MDC                                                                                                                             | 1.0.1.2      |                                                                                                                                          |
+| cAHI                                                         | NM           | 8410804^MDC_SABTE_AHI_CENT^MDC                                                                                                                                | 1.0.1.3      |                                                                                                                                          |
+| Apnoea-Hypopnoea-Index (AHI)                                 | NM           | 8410792^MDC_SABTE_AHI_TOTAL^MDC<br>or<br>8410796^MDC_SABTE_AHI_UNCLASS^MDC<br>or<br>8410800^MDC_SABTE_AHI_OBSTRUC^MDC<br>or<br>8410804^MDC_SABTE_AHI_CENT^MDC | 1.0.0.8      |                                                                                                                                          |
+| Humidifier level setting                                     | NM           | 8410828^MDC_SABTE_LVL_HUMID_STAG<br>E_SET^MDC or<br>8410832^MDC_SABTE_LVL_HUMID_TEMP<br>_SET^MDC or<br>8410836^MDC_SABTE_LVL_HUMID_HUM<br>_SET^MDC            | 1.0.0.9      |                                                                                                                                          |
+| Trigger sensitivity setting                                  | NM           | 8410840^MDC_SABTE_LVL_TRIG_SENS_S<br>ET^MDC                                                                                                                   | 1.0.0.10     |                                                                                                                                          |
+| Inspiration pressure rise setting                            | NM           | 8410844^MDC_SABTE_LVL_INSP_PRESS_                                                                                                                             | 1.0.0.11     |                                                                                                                                          |
+
+**Table E.44 – Sleep apnoea breathing therapy equipment (SABTE) OBX encoding – Part 1**
+
+| <b>Description</b>               | <b>OBX-2</b> | <b>OBX-3</b>                                 | <b>OBX-4</b> | <b>OBX-5</b>                                                                                                                                                                                                                                                                       |
+|----------------------------------|--------------|----------------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                  |              | RISE_SET^MDC                                 |              |                                                                                                                                                                                                                                                                                    |
+| Pressure adaption level setting  | NM           | 8410848^MDC_SABTE_LVL_ADAPT_SET^MDC          | 1.0.0.12     |                                                                                                                                                                                                                                                                                    |
+| Pressure adaption freeze setting | CWE          | 8410868^MDC_SABTE_MODE_ADAPT_FREEZE_SET ^MDC | 1.0.0.13     | 8410869^MDC_SABTE_MODE_ADAPT_FREEZE_OFF^MDC or<br>8410870^MDC_SABTE_MODE_ADAPT_FREEZE_ON^MDC                                                                                                                                                                                       |
+| Autostart/-stop setting          | CWE          | 8410872^MDC_SABTE_MODE_AUTOSTARTSTOP_SET^MDC | 1.0.0.14     | One of the values...<br><0 or 1>^sabte-autostart-on(0),<br><0 or 1>^sabte-autostop-on(1)                                                                                                                                                                                           |
+| Device mode setting              | CWE          | 8410876^MDC_SABTE_MODE_DEV_SET^MDC           | 1.0.0.15     | 8410877^MDC_SABTE_MODE_DEV_UNDETERMINED^MDC or<br>8410878^MDC_SABTE_MODE_DEV_STANDBY^MDC or<br>8410879^MDC_SABTE_MODE_DEV_THERAPY^MDC or<br>8410880^MDC_SABTE_MODE_DEV_MASK_FITTING^MDC or<br>8410881^MDC_SABTE_MODE_DEV_DRYING^MDC or<br>8410882^MDC_SABTE_MODE_DEV_EXPORTING^MDC |
+| Therapy mode setting             | CWE          | 8410888^MDC_SABTE_MODE_THERAPY_SET^MDC       | 1.0.0.16     | 8410889^MDC_SABTE_MODE_THERAPY_UNDETERMINED^MDC or<br>8410890^MDC_SABTE_MODE_THERAPY_CPAP^MDC or<br>8410891^MDC_SABTE_MODE_THERAPY_CPAP_AUTO^MDC or<br>8410892^MDC_SABTE_MODE_THERAPY_BPAP_S^MDC or<br>8410893^MDC_SABTE_MODE_THERAPY                                              |
+
+**Table E.44 – Sleep apnoea breathing therapy equipment (SABTE) OBX encoding – Part 1**
+
+| Description            | OBX-2 | OBX-3                                     | OBX-4    | OBX-5                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|------------------------|-------|-------------------------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                        |       |                                           |          | _BPAP_T^MDC or<br>8410894^MDC_SABTE_MODE_THERAPY<br>_BPAP_ST^MDC or<br>8410895^MDC_SABTE_MODE_THERAPY<br>_BPAP_S_AUTO^MDC or<br>8410896^MDC_SABTE_MODE_THERAPY<br>_BPAP_T_AUTO^MDC or<br>8410897^MDC_SABTE_MODE_THERAPY<br>_BPAP_ST_AUTO^MDC or<br>8410898^MDC_SABTE_MODE_THERAPY<br>_ACSV^MDC                                                                                                                                                                                                                                                                                                                                        |
+| Compliance annotations | CWE   | 8410908^MDC_SABTE_PATT_COMPLIANCE_CLS^MDC | 1.0.0.17 | One of the values...<br><0 or 1>^sabte-annotation-epoch-undetermined-start(0),<br><0 or 1>^sabte-annotation-epoch-undetermined-stop(1),<br><0 or 1>^sabte-annotation-epoch-breathing-artifact-start(2),<br><0 or 1>^sabte-annotation-epoch-breathing-artifact-stop(3),<br><0 or 1>^sabte-annotation-epoch-breathing-spontaneous-start(4),<br><0 or 1>^sabte-annotation-epoch-breathing-spontaneous-stop(5),<br><0 or 1>^sabte-annotation-epoch-breathing-timed-start(6),<br><0 or 1>^sabte-annotation-epoch-breathing-timed-stop(7),<br><0 or 1>^sabte-annotation-epoch-snoring-start(8),<br><0 or 1>^sabte-annotation-epoch-snoring- |
+
+**Table E.44 – Sleep apnoea breathing therapy equipment (SABTE) OBX encoding – Part 1**
+
+| Description | OBX-2 | OBX-3 | OBX-4 | OBX-5                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|-------------|-------|-------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|             |       |       |       | stop(9),<br><0 or 1>^sabte-annotation-epoch-csr-start(10),<br><0 or 1>^sabte-annotation-epoch-csr-stop(11),<br><0 or 1>^sabte-annotation-event-undetermined-start(12),<br><0 or 1>^sabte-annotation-event-undetermined-stop(13),<br><0 or 1>^sabte-annotation-event-flow-limitation-start(14),<br><0 or 1>^sabte-annotation-event-flow-limitation-stop(15),<br><0 or 1>^sabte-annotation-event-hypopnoea-unclassified-start(16),<br><0 or 1>^sabte-annotation-event-hypopnoea-unclassified-stop(17),<br><0 or 1>^sabte-annotation-event-hypopnoea-obstructive-start(18),<br><0 or 1>^sabte-annotation-event-hypopnoea-obstructive-stop(19),<br><0 or 1>^sabte-annotation-event-hypopnoea-central-start(20),<br><0 or 1>^sabte-annotation-event-hypopnoea-central-stop(21),<br><0 or 1>^sabte-annotation-event-apnoea-unclassified-start(22),<br><0 or 1>^sabte-annotation-event-apnoea-unclassified-stop(23),<br><0 or 1>^sabte-annotation-event-apnoea- |
+
+**Table E.44 – Sleep apnoea breathing therapy equipment (SABTE) OBX encoding – Part 1**
+
+| Description                      | OBX-2 | OBX-3                                                                    | OBX-4      | OBX-5                                                                                                                                                                                                                                                                                                                                                            |
+|----------------------------------|-------|--------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                  |       |                                                                          |            | obstructive-start(24),<br><0 or 1>^sabte-annotation-event-apnoea-obstructive-stop(25),<br><0 or 1>^sabte-annotation-event-apnoea-mixed-start(26),<br><0 or 1>^sabte-annotation-event-apnoea-mixed-stop(27),<br><0 or 1>^sabte-annotation-event-apnoea-central-start(28),<br><0 or 1>^sabte-annotation-event-apnoea-central-stop(29)                              |
+| Efficacy annotations             | CWE   | 8410916^MDC_SABTE_PATT_EFFICACY_C<br>LS^MDC                              | 1.0.0.18   | One of the values...<br><0 or 1>^sabte-annotation-session-undetermined-start(0),<br><0 or 1>^sabte-annotation-session-undetermined-stop(1),<br><0 or 1>^sabte-annotation-session-therapy-start(2),<br><0 or 1>^sabte-annotation-session-therapy-stop(3),<br><0 or 1>^sabte-annotation-session-usage-start(4),<br><0 or 1>^sabte-annotation-session-usage-stop(5) |
+| Therapy pressure waveform        | NA    | 8410948^MDC_SABTE_PRESS^MDC or<br>8410968^MDC_SABTE_PRESS_TARGET^M<br>DC | 1.0.0.19   | 11^22^33^44^55^66^77^88^99^...<br>Note that the actual values of the waveform may need to be computed based on the scaling values in the Scale-And-Range-Specification object                                                                                                                                                                                    |
+| Therapy pressure waveform sample | NM    | 67981^MDC_ATTR_TIME_PD_SAMP^MDC                                          | 1.0.0.19.1 |                                                                                                                                                                                                                                                                                                                                                                  |
+
+**Table E.44 – Sleep apnoea breathing therapy equipment (SABTE) OBX encoding – Part 1**
+
+| <b>Description</b>                                             | <b>OBX-2</b> | <b>OBX-3</b>                                                                                                                                                                                                                                                                    | <b>OBX-4</b> | <b>OBX-5</b> |
+|----------------------------------------------------------------|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------|
+| period                                                         |              |                                                                                                                                                                                                                                                                                 |              |              |
+| Therapy pressure                                               | NM           | 8410949^MDC_SABTE_PRESS_MIN^MDC or<br>8410950^MDC_SABTE_PRESS_MAX^MDC<br>or<br>8410951^MDC_SABTE_PRESS_MEAN^MDC<br>or 8410955^MDC_SABTE_PRESS_P50^MDC<br>or 8410957^MDC_SABTE_PRESS_P90^MDC<br>or 8410958^MDC_SABTE_PRESS_P95^MDC<br>or 8410959^MDC_SABTE_PRESS_INSTANT<br>^MDC | 1.0.0.20     |              |
+| Continuous positive airway pressure (P CPAP) setting           | NM           | 8410972^MDC_SABTE_PRESS_CPAP_SET^<br>MDC                                                                                                                                                                                                                                        | 1.0.0.21     |              |
+| Minimal automatic positive airway pressure (Pmin APAP) setting | NM           | 8410976^MDC_SABTE_PRESS_CPAP_AUT<br>O_MIN_SET^MDC                                                                                                                                                                                                                               | 1.0.0.22     |              |
+| Maximal automatic positive airway pressure (Pmax APAP) setting | NM           | 8410980^MDC_SABTE_PRESS_CPAP_AUT<br>O_MAX_SET^MDC                                                                                                                                                                                                                               | 1.0.0.23     |              |
+| Inspiratory positive airway pressure (P IPAP) setting          | NM           | 8410984^MDC_SABTE_PRESS_IPAP_SET^<br>MDC                                                                                                                                                                                                                                        | 1.0.0.24     |              |
+| Expiratory positive airway pressure (P EPAP) setting           | NM           | 8410988^MDC_SABTE_PRESS_EPAP_SET^<br>MDC                                                                                                                                                                                                                                        | 1.0.0.25     |              |
+| Ramp start pressure setting                                    | NM           | 8411004^MDC_SABTE_PRESS_RAMP_STA<br>RT_SET^MDC                                                                                                                                                                                                                                  | 1.0.0.26     |              |
+| Respiratory rate                                               | NM           | 8411009^MDC_SABTE_RESP_RATE_MIN^<br>MDC or<br>8411010^MDC_SABTE_RESP_RATE_MAX^<br>MDC or<br>8411011^MDC_SABTE_RESP_RATE_MEAN<br>^MDC or<br>8411015^MDC_SABTE_RESP_RATE_P50^M<br>DC or                                                                                           | 1.0.0.27     |              |
+
+**Table E.44 – Sleep apnoea breathing therapy equipment (SABTE) OBX encoding – Part 1**
+
+| Description                    | OBX-2 | OBX-3                                                                                                                                                                                                                                                                                                                     | OBX-4      | OBX-5                                                                                                                                                                                  |
+|--------------------------------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                |       | 8411017^MDC_SABTE_RESP_RATE_P90^M<br>DC or<br>8411018^MDC_SABTE_RESP_RATE_P95^M<br>DC or<br>8411019^MDC_SABTE_RESP_RATE_INSTA<br>NT^MDC                                                                                                                                                                                   |            |                                                                                                                                                                                        |
+| Respiratory rate setting       | NM    | 8411044^MDC_SABTE_RESP_RATE_SET^M<br>DC                                                                                                                                                                                                                                                                                   | 1.0.0.28   |                                                                                                                                                                                        |
+| I:E ratio                      | NM    | 8411049^MDC_SABTE_RATIO_IE_MIN^MD<br>C or<br>8411050^MDC_SABTE_RATIO_IE_MAX^M<br>DC or<br>8411051^MDC_SABTE_RATIO_IE_MEAN^<br>MDC or<br>8411055^MDC_SABTE_RATIO_IE_P50^MD<br>C or<br>8411057^MDC_SABTE_RATIO_IE_P90^MD<br>C or<br>8411058^MDC_SABTE_RATIO_IE_P95^MD<br>C or<br>8411059^MDC_SABTE_RATIO_IE_INSTAN<br>T^MDC | 1.0.0.29   |                                                                                                                                                                                        |
+| I:E ratio setting              | NM    | 8411084^MDC_SABTE_RATIO_IE_SET^MD<br>C                                                                                                                                                                                                                                                                                    | 1.0.0.30   |                                                                                                                                                                                        |
+| Leakage waveform               | NA    | 8411088^MDC_SABTE_VOL_LEAK^MDC                                                                                                                                                                                                                                                                                            | 1.0.0.31   | 11^22^33^44^55^66^77^88^99^...<br>Note that the actual values of the waveform<br>may need to be computed based on the scaling<br>values in the Scale-And-Range-Specification<br>object |
+| Leakage waveform sample period | NM    | 67981^MDC_ATTR_TIME_PD_SAMP^MDC                                                                                                                                                                                                                                                                                           | 1.0.0.31.1 |                                                                                                                                                                                        |
+
+**Table E.44 – Sleep apnoea breathing therapy equipment (SABTE) OBX encoding – Part 1**
+
+| Description               | OBX-2 | OBX-3                                                                                                                                                                                                                                                                                                       | OBX-4    | OBX-5 |
+|---------------------------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|-------|
+| Leakage                   | NM    | 8411089^MDC_SABTE_VOL_LEAK_MIN^MDC or<br>8411090^MDC_SABTE_VOL_LEAK_MAX^MDC or<br>8411091^MDC_SABTE_VOL_LEAK_MEAN^MDC or<br>8411095^MDC_SABTE_VOL_LEAK_P50^MDC or<br>8411097^MDC_SABTE_VOL_LEAK_P90^MDC or<br>8411098^MDC_SABTE_VOL_LEAK_P95^MDC or<br>8411099^MDC_SABTE_VOL_LEAK_INSTANT^MDC               | 1.0.0.32 |       |
+| Respiratory minute volume | NM    | 8411129^MDC_SABTE_VOL_MINUTE_MIN^MDC or<br>8411130^MDC_SABTE_VOL_MINUTE_MAX^MDC or<br>8411131^MDC_SABTE_VOL_MINUTE_MEAN^MDC or<br>8411135^MDC_SABTE_VOL_MINUTE_P50^MDC or<br>8411137^MDC_SABTE_VOL_MINUTE_P90^MDC or<br>8411138^MDC_SABTE_VOL_MINUTE_P95^MDC or<br>8411139^MDC_SABTE_VOL_MINUTE_INSTANT^MDC | 1.0.0.33 |       |
+| Tidal volume              | NM    | 8411169^MDC_SABTE_VOL_TIDAL_MIN^MDC or<br>8411170^MDC_SABTE_VOL_TIDAL_MAX^MDC or                                                                                                                                                                                                                            | 1.0.0.34 |       |
+
+**Table E.44 – Sleep apnoea breathing therapy equipment (SABTE) OBX encoding – Part 1**
+
+| Description | OBX-2 | OBX-3                                                                                                                                                                                                                                | OBX-4 | OBX-5 |
+|-------------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|
+|             |       | 8411171^MDC_SABTE_VOL_TIDAL_MEAN<br>^MDC or<br>8411175^MDC_SABTE_VOL_TIDAL_P50^M<br>DC or<br>8411177^MDC_SABTE_VOL_TIDAL_P90^M<br>DC or<br>8411178^MDC_SABTE_VOL_TIDAL_P95^M<br>DC or<br>8411179^MDC_SABTE_VOL_TIDAL_INSTA<br>NT^MDC |       |       |
+
+**Table E.45 – Sleep apnoea breathing therapy equipment (SABTE) OBX encoding – Part 2**
+
+| Description                                                     | OBX-6                                                     | OBX-18                                        | OBX-20 |
+|-----------------------------------------------------------------|-----------------------------------------------------------|-----------------------------------------------|--------|
+| Sleep apnoea breathing therapy equipment (SABTE) MDS            |                                                           | 0123456789ABCDEF^^012345<br>6789ABCDEF^EUI-64 |        |
+| PHD DM device status                                            |                                                           |                                               |        |
+| Duration of flow generation                                     | 264352^MDC_DIM_MIN^MDC                                    |                                               |        |
+| Duration of patient use                                         | 264352^MDC_DIM_MIN^MDC                                    |                                               |        |
+| Snoring duration                                                | 264352^MDC_DIM_MIN^MDC                                    |                                               |        |
+| Cheyne-Stokes respiration (CSR) duration                        | 264352^MDC_DIM_MIN^MDC                                    |                                               |        |
+| Ramp duration setting                                           | 264352^MDC_DIM_MIN^MDC                                    |                                               |        |
+| Airflow waveform                                                | 264992^MDC_DIM_L_PER_MIN^MDC                              |                                               |        |
+| Airflow waveform sample period                                  | 264320^MDC_DIM_SEC^MDC or<br>264339^MDC_DIM_MICRO_SEC^MDC |                                               |        |
+| Apnoea-Hypopnoea-Index (AHI)<br>compound of uAHI, oAHI and cAHI |                                                           |                                               |        |
+
+**Table E.45 – Sleep apnoea breathing therapy equipment (SABTE) OBX encoding – Part 2**
+
+| <b>Description</b>                                             | <b>OBX-6</b>                                              | <b>OBX-18</b> | <b>OBX-20</b> |
+|----------------------------------------------------------------|-----------------------------------------------------------|---------------|---------------|
+| uAHI                                                           | 266876^MDC_DIM_EVT_PER_HR^MDC                             |               |               |
+| oAHI                                                           | 266876^MDC_DIM_EVT_PER_HR^MDC                             |               |               |
+| cAHI                                                           | 266876^MDC_DIM_EVT_PER_HR^MDC                             |               |               |
+| Apnoea-Hypopnoea-Index (AHI)                                   | 266876^MDC_DIM_EVT_PER_HR^MDC                             |               |               |
+| Humidifier level setting                                       | 262688^MDC_DIM_PERCENT^MDC                                |               |               |
+| Trigger sensitivity setting                                    | 262688^MDC_DIM_PERCENT^MDC                                |               |               |
+| Inspiration pressure rise setting                              | 262688^MDC_DIM_PERCENT^MDC                                |               |               |
+| Pressure adaption level setting                                | 262688^MDC_DIM_PERCENT^MDC                                |               |               |
+| Pressure adaption freeze setting                               |                                                           |               |               |
+| Auto start/-stop setting                                       |                                                           |               |               |
+| Device mode setting                                            |                                                           |               |               |
+| Therapy mode setting                                           |                                                           |               |               |
+| Compliance annotations                                         |                                                           |               |               |
+| Efficacy annotations                                           |                                                           |               |               |
+| Therapy pressure waveform                                      | 265986^MDC_DIM_HECTO_PASCAL^MDC                           |               |               |
+| Therapy pressure waveform sample period                        | 264320^MDC_DIM_SEC^MDC or<br>264339^MDC_DIM_MICRO_SEC^MDC |               |               |
+| Therapy pressure                                               | 265986^MDC_DIM_HECTO_PASCAL^MDC                           |               |               |
+| Continuous positive airway pressure (P CPAP) setting           | 265986^MDC_DIM_HECTO_PASCAL^MDC                           |               |               |
+| Minimal automatic positive airway pressure (Pmin APAP) setting | 265986^MDC_DIM_HECTO_PASCAL^MDC                           |               |               |
+| Maximal automatic positive airway pressure (Pmax APAP) setting | 265986^MDC_DIM_HECTO_PASCAL^MDC                           |               |               |
+| Inspiratory positive airway pressure (P                        | 265986^MDC_DIM_HECTO_PASCAL^MDC                           |               |               |
+
+**Table E.45 – Sleep apnoea breathing therapy equipment (SABTE) OBX encoding – Part 2**
+
+| <b>Description</b>                                   | <b>OBX-6</b>                                              | <b>OBX-18</b> | <b>OBX-20</b> |
+|------------------------------------------------------|-----------------------------------------------------------|---------------|---------------|
+| IPAP) setting                                        |                                                           |               |               |
+| Expiratory positive airway pressure (P EPAP) setting | 265986^MDC_DIM_HECTO_PASCAL^MDC                           |               |               |
+| Ramp start pressure setting                          | 265986^MDC_DIM_HECTO_PASCAL^MDC                           |               |               |
+| Respiratory rate                                     | 264928^MDC_DIM_RESP_PER_MIN^MDC                           |               |               |
+| Respiratory rate setting                             | 264928^MDC_DIM_RESP_PER_MIN^MDC                           |               |               |
+| I:E ratio                                            | 262688^MDC_DIM_PERCENT^MDC                                |               |               |
+| I:E ratio setting                                    | 262688^MDC_DIM_PERCENT^MDC                                |               |               |
+| Leakage waveform                                     | 264992^MDC_DIM_L_PER_MIN^MDC                              |               |               |
+| Leakage waveform sample period                       | 264320^MDC_DIM_SEC^MDC or<br>264339^MDC_DIM_MICRO_SEC^MDC |               |               |
+| Leakage                                              | 264992^MDC_DIM_L_PER_MIN^MDC                              |               |               |
+| Respiratory minute volume                            | 264992^MDC_DIM_L_PER_MIN^MDC                              |               |               |
+| Tidal volume                                         | 263762^MDC_DIM_MILLI_L^MDC                                |               |               |
+
+### **E.3.15 ISO/IEEE 11073-10425 continuous glucose monitor**
+
+#### **E.3.15.1 Modelling**
+
+The continuous glucose monitor (CGM) object model consists of a single key observation type, glucose. The other objects that may provide additional information, e.g., glucose trend, may be linked to a particular source observation through a Source-Handle-Reference FACET-level OBX.
+
+#### **E.3.15.2 Transformations**
+
+The following transformations are performed in the encoding of this device.
+
+Several nomenclature codes have been harmonized with the underlying base codes. They are pointed out in the tables below.
+
+### E.3.15.3 Containment tree
+
+Table E.46 shows a continuous glucose monitor containment tree.
+
+**Table E.46 – Continuous glucose monitor containment tree**
+
+| REFID                                                                                                                                                                                                                                                                                                                                                                                             | Description                                             |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|
+| MDC_DEV_SPEC_PROFILE_CGM                                                                                                                                                                                                                                                                                                                                                                          | Continuous glucose monitor (CGM) MDS                    |
+| ... MDC_CONC_GLU_ISF or<br>... MDC_CONC_GLU_CAPILLARY_WHOLEBLOOD or<br>... MDC_CONC_GLU_CAPILLARY_PLASMA or<br>... MDC_CONC_GLU_VENOUS_WHOLEBLOOD or<br>... MDC_CONC_GLU_VENOUS_PLASMA or<br>... MDC_CONC_GLU_ARTERIAL_WHOLEBLOOD or<br>... MDC_CONC_GLU_ARTERIAL_PLASMA or<br>... MDC_CONC_GLU_CONTROL<br>... MDC_CONC_GLU_UNDETERMINED_WHOLEBLOOD or<br>... MDC_CONC_GLU_UNDETERMINED_PLASMA or | Glucose                                                 |
+| ... MDC_PHD_DM_DEV_STAT                                                                                                                                                                                                                                                                                                                                                                           | Personal health device disease management device status |
+| ... MDC_CGM_DEV_STAT                                                                                                                                                                                                                                                                                                                                                                              | CGM status                                              |
+| ... MDC_CGM_SENSOR_CALIBRATION                                                                                                                                                                                                                                                                                                                                                                    | Sensor calibration                                      |
+| ... MDC_CGM_SENSOR_RUN_TIME                                                                                                                                                                                                                                                                                                                                                                       | Sensor run-time                                         |
+| ... MDC_CGM_SENSOR_SAMPLE_INTERVAL                                                                                                                                                                                                                                                                                                                                                                | Glucose sample interval                                 |
+| ... MDC_CONC_GLU_TREND                                                                                                                                                                                                                                                                                                                                                                            | Glucose trend                                           |
+| ... MDC_CONC_GLU_PATIENT_THRESHOLDS_LOW_HIGH                                                                                                                                                                                                                                                                                                                                                      | Patient low/high Thresholds                             |
+| ... MDC_CONC_GLU_THRESHOLDS_HYPO_HYPER                                                                                                                                                                                                                                                                                                                                                            | Device hypo/hyper thresholds                            |
+| ... MDC_CONC_GLU_RATE_THRESHOLDS                                                                                                                                                                                                                                                                                                                                                                  | Glucose rate of change thresholds                       |
+
+### E.3.15.5 OBX encoding
+
+Table E.47 and Table E.48 show part 1 and part 2 (respectively) of a continuous glucose monitor OBX encoding.
+
+**Table E.47 – Continuous glucose monitor encoding – Part 1**
+
+| Description                          | OBX-2 | OBX-3                                                                                                                                                                                                                                                                                                                                                                                                                                                           | OBX-4   | OBX-5                                                                                                                                                                                  |
+|--------------------------------------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Continuous glucose monitor (CGM) MDS |       | 528410^MDC_DEV_SPEC_PROFILE_CGM^MDC                                                                                                                                                                                                                                                                                                                                                                                                                             | 1       |                                                                                                                                                                                        |
+| Glucose                              | NM    | 160212^MDC_CONC_GLU_ISF^MDC or<br>160184^MDC_CONC_GLU_CAPILLARY_WHOLEBLOOD^MDC or<br>160188^MDC_CONC_GLU_CAPILLARY_PLASMA^MDC or<br>160192^MDC_CONC_GLU_VENOUS_WHOLEBLOOD^MDC or<br>160196^MDC_CONC_GLU_VENOUS_PLASMA^MDC or<br>160200^MDC_CONC_GLU_ARTERIAL_WHOLEBLOOD^MDC or<br>160204^MDC_CONC_GLU_ARTERIAL_PLASMA^MDC or<br>160208^MDC_CONC_GLU_CONTROL^MDC or<br>160364^MDC_CONC_GLU_UNDETERMINED_WHOLEBLOOD or<br>160368^MDC_CONC_GLU_UNDETERMINED_PLASMA | 1.0.0.1 | 15.8                                                                                                                                                                                   |
+| PHD DM status                        | CWE   | 8408608^MDC_PHD_DM_DEV_STAT^MDC                                                                                                                                                                                                                                                                                                                                                                                                                                 | 1.0.0.2 | One of the values...<br><0 or 1>^device-status-undetermined(0),<br><0 or 1>^device-status-reset(1),<br><0 or 1>^device-status-error(5),<br><0 or 1>^device-status-error-mechanical(6), |
+
+**Table E.47 – Continuous glucose monitor encoding – Part 1**
+
+| Description | OBX-2 | OBX-3                        | OBX-4   | OBX-5                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|-------------|-------|------------------------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|             |       |                              |         | <0 or 1>^device-status-error-electronic(7),<br><0 or 1>^device-status-error-software(8),<br><0 or 1>^device-status-error-battery(9),<br><0 or 1>^device-status-service(15),<br><0 or 1>^device-status-service-time-sync-required(16),<br><0 or 1>^device-status-service-calibration-required(17),<br><0 or 1>^device-status-service-replenishment-required(18),<br><0 or 1>^device-status-battery-low(25),<br><0 or 1>^device-status-battery-depleted(26),<br><0 or 1>^device-status-battery-replaced(27),<br><0 or 1>^device-status-battery-interrupted(28) |
+| CGM status  | CWE   | 8418060^MDC_CGM_DEV_STAT^MDC | 1.0.0.3 | One of the values...<br><0 or 1>^sensor-session-stopped(0),<br><0 or 1>^sensor-type-incorrect(2),<br><0 or 1>^sensor-malfunction(3),<br><0 or 1>^device-specific-alert(4),<br><0 or 1>^sensor-calibration-not-allowed(7),<br><0 or 1>^sensor-calibration-not-recommended(8),<br><0 or 1>^sensor-calibration-not-required(9),<br><0 or 1>^sensor-temp-too-high(10),<br><0 or 1>^sensor-temp-too-low(11),                                                                                                                                                      |
+
+**Table E.47 – Continuous glucose monitor encoding – Part 1**
+
+| Description                  | OBX-2 | OBX-3                                                | OBX-4   | OBX-5                                                                                                                                                                                                                                                                                                                                                                                   |
+|------------------------------|-------|------------------------------------------------------|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                              |       |                                                      |         | <0 or 1>^sensor-result-below-patient-low(12),<br><0 or 1>^sensor-result-above-patient-high(13),<br><0 or 1>^sensor-low-hypo(14),<br><0 or 1>^sensor-low-hyper(15),<br><0 or 1>^sensor-rate-decrease-exceeded(16),<br><0 or 1>^sensor-rate-increase-exceeded(17),<br><0 or 1>^sensor-result-too-low(18),<br><0 or 1>^sensor-result-too-high(19),<br><0 or 1>^sensor-com-out-of-range(20) |
+| Sensor calibration           | NM    | 8418036^MDC_CGM_SENSOR_CALIBRATION^MDC               | 1.0.0.4 | 6.4                                                                                                                                                                                                                                                                                                                                                                                     |
+| Sensor run-time              | NM    | 8418040^MDC_CGM_SENSOR_RUN_TIME^MDC                  | 1.0.0.5 | 168                                                                                                                                                                                                                                                                                                                                                                                     |
+| Glucose sample interval      | NM    | 8418044^MDC_CGM_SENSOR_SAMPLE_INTERVAL^MDC           | 1.0.0.6 | 15                                                                                                                                                                                                                                                                                                                                                                                      |
+| Glucose trend                | NM    | 8418008^MDC_CONC_GLU_TREND^MDC                       | 1.0.0.7 | 0.2                                                                                                                                                                                                                                                                                                                                                                                     |
+| Patient low/high thresholds  |       | 8418012^MDC_CONC_GLU_PATIENT_THRESHOLDS_LOW_HIGH^MDC | 1.0.1.0 |                                                                                                                                                                                                                                                                                                                                                                                         |
+| Patient low threshold        | NM    | 8418013^MDC_CONC_GLU_PATIENT_THRESHOLD_LOW^MDC       | 1.0.1.1 | 4.0                                                                                                                                                                                                                                                                                                                                                                                     |
+| Patient high threshold       | NM    | 8418014^MDC_CONC_GLU_PATIENT_THRESHOLD_HIGH^MDC      | 1.0.1.2 | 8.0                                                                                                                                                                                                                                                                                                                                                                                     |
+| Device hypo/hyper thresholds |       | 8418016^MDC_CONC_GLU_THRESHOLDS_HYPO_HYPER^MDC       | 1.0.2.0 |                                                                                                                                                                                                                                                                                                                                                                                         |
+
+**Table E.47 – Continuous glucose monitor encoding – Part 1**
+
+| <b>Description</b>                        | <b>OBX-2</b> | <b>OBX-3</b>                                         | <b>OBX-4</b> | <b>OBX-5</b> |
+|-------------------------------------------|--------------|------------------------------------------------------|--------------|--------------|
+| Device hypo threshold                     | NM           | 8418017^MDC_CONC_GLU_THRESHOLD_H<br>YPO^MDC          | 1.0.2.1      | 2.0          |
+| Device hyper threshold                    | NM           | 8418018^MDC_CONC_GLU_THRESHOLD_H<br>YPER^MDC         | 1.0.2.2      | 20.0         |
+| Glucose rate of change thresholds         |              | 8391520^MDC_CONC_GLU_RATE_THRESH<br>OLDS^MDC         | 1.0.3.0      |              |
+| Glucose rate of change increase threshold | NM           | 8391521^MDC_CONC_GLU_RATE_THRESH<br>OLD_INCREASE^MDC | 1.0.3.1      | 0.5          |
+| Glucose rate of change decrease threshold | NM           | 8391522^MDC_CONC_GLU_RATE_THRESH<br>OLD_DECREASE^MDC | 1.0.3.2      | 0.5          |
+
+**Table E.48 – Insulin pump encoding – Part 2**
+
+| <b>Description</b>                 | <b>OBX-6</b>                                                               | <b>OBX-18</b>                                 | <b>OBX-20</b> |
+|------------------------------------|----------------------------------------------------------------------------|-----------------------------------------------|---------------|
+| Insulin pump MDS                   |                                                                            | 0123456789ABCDEF^^01234567<br>89ABCDEF^EUI-64 |               |
+| Bolus delivered                    | 267616^MDC_DIM_X_INTL_UNIT^MDC                                             |                                               |               |
+| Current basal rate setting         | 267840^MDC_DIM_X_INTL_UNIT_PER_HR^MDC                                      |                                               |               |
+| PHD DM device status               |                                                                            |                                               |               |
+| Insulin pump status                |                                                                            |                                               |               |
+| Operational and therapy conditions |                                                                            |                                               |               |
+| Current bolus setting              | 267616^MDC_DIM_X_INTL_UNIT^MDC or<br>267840^MDC_DIM_X_INTL_UNIT_PER_HR^MDC |                                               |               |
+
+**Table E.48 – Insulin pump encoding – Part 2**
+
+| <b>Description</b>          | <b>OBX-6</b>                                                                                                                                                                                 | <b>OBX-18</b> | <b>OBX-20</b> |
+|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|
+| Pending bolus delay         | 264352^MDC_DIM_MIN^MDC or<br>264320^MDC_DIM_SEC^MDC or                                                                                                                                       |               |               |
+| Basal delivered             | 267616^MDC_DIM_X_INTL_UNIT^MDC                                                                                                                                                               |               |               |
+| Insulin reservoir remaining | 267616^MDC_DIM_X_INTL_UNIT^MDC                                                                                                                                                               |               |               |
+| Insulin concentration       | 267712^MDC_DIM_X_INTL_UNIT_PER_L^MDC or<br>267744^MDC_DIM_X_INTL_UNIT_PER_ML^MDC<br>or<br>267680^MDC_DIM_X_INTL_UNIT_PER_M_CUBE^<br>MDC or<br>267648^MDC_DIM_X_INTL_UNIT_PER_CM_CUBE^<br>MDC |               |               |
+
+## E.4 HL7 Unsolicited observation result
+
+The intent of this clause is to provide a quick reference of the HL7 Unsolicited Observation Result (ORU^R01^ORU\_R01) detail from the Services interface usage point of view. To this extent, these tables subset the full information and present only the core data needed. For further information, please refer to the IHE PCD Technical Framework [IHE PCD-TF-2] and/or Chapter 2 (Control) of [HL7 2.6].
+
+The following applies to the usage column found in the tables listed in the following subclauses:
+
+- Shading indicates fields that would have to be present in a minimal message. Please note that, by convention, a segment should terminate after its last non-empty sequence.
+- All entries whose usage indicator is 'X' shall be empty.
+- The '<' and '>' symbols used in the table below are NOT part of the encoding; they are just helpers to delineate the description of the fields.
+- The Data types are given in clause E.5.
+- The following notation is used (also in clauses E.5 and E.6):
+  - C=conditionally required;
+  - CE=conditionally required but may be empty;
+  - O=optional;
+  - R=required;
+  - RE=required but may be empty;
+  - X=not supported.
+
+### E.4.1 MSH
+
+The specifications in this clause are derived from the IHE PCD Technical Framework [IHE PCD-TF-2], Appendix B.
+
+The Message header segment is the first segment of every message. It contains the core common information that applies for the entire message. This segment is required.
+
+Table E.49 shows the core data in a message header segment.
+
+**Table E.49 – Message header segment**
+
+| Element | Usage | Data type | Element name        | Value                                                                                                                                                                                                                                                                                                                                                        |
+|---------|-------|-----------|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| MSH-1   | R     | ST        | Field separator     | <b>Shall</b> be ' '. PCD-01 constrains to the character ' '                                                                                                                                                                                                                                                                                                  |
+| MSH-2   | R     | ST        | Encoding characters | <b>Shall</b> be '^~\&'. PCD-01 constrains to the characters '^~\&'                                                                                                                                                                                                                                                                                           |
+| MSH-3   | R     | HD        | Sending application | Uniquely specify the sending application.<br>The data type ID shall be EUI-64.<br>The Universal ID shall be the PHG's system ID.<br>The Namespace ID should not be empty. A non-empty entry makes the document more human readable.<br>(Note – Not to be confused with an XML namespace.)<br>Encoded as<br><Namespace ID (data type IS)>^<Universal ID (data |
+
+**Table E.49 – Message header segment**
+
+| Element | Usage | Data type | Element name          | Value                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------|-------|-----------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|         |       |           |                       | type ST)^<Universal ID Type (data type ID)><br>Example:<br>'ORIGatewayInc^ABCDE48234567ABCD^EUI-64'                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| MSH-4   | RE    | HD        | Sending facility      | Uniquely specifies the sending facility                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| MSH-5   | RE    | HD        | Receiving application | Uniquely specifies specify the receiving application                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| MSH-6   | RE    | HD        | Receiving facility    | Uniquely specifies the receiving facility                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| MSH-7   | R     | DTM       | Date/Time of message  | <p><b>Shall</b> be the time of the document completion.</p> <p>To clarify the timestamp is when the PCD-01 document is completed and ready for sending. It is not the time of the sending or when one initializes the document in code. Thus if the network is down and the document is sent at a later time, this timestamp is NOT changed to the sending time.</p> <p>Encoded as</p> <p>YYYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]</p> <p><b>Shall</b> contain the Time zone unless the PHG has lost synchronization and is falling back to using unqualified time.</p> <p>A Continua compliant services sender shall be UTC aware and should be local time aware. However, error conditions may prevent the PHG from being able to obtain appropriate time information. This specification allows for the same relaxation of the timestamp generation as in reporting the measurement timestamps.</p> <p>Examples:</p> <p>20090726095730+0000 qualified; in GMT time zone</p> <p>20090726095730-0000 qualified; time zone unknown</p> <p>20090726045730-0500 qualified; in non GMT zone</p> <p>20090726045730 unqualified fallback</p> |
+| MSH-8   | X     | ST        | Security              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| MSH-9   | R     | MSG       | Message type          | <p>This field specifies the message type, trigger event and the message structure ID for the message. For PCD-01 it is the unsolicited request code ORU^R01^ORU_R01</p> <p>Encoded as</p> <p>&lt;Message Code (data type ID)&gt;^&lt;Trigger Event (data type ID)&gt;^&lt;Message Structure (data type ID)&gt;</p> <p><b>Shall</b> be 'ORU^R01^ORU_R01'</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| MSH-10  | R     | ST        | Message control Id    | <p>This Id is echoed back in the acknowledgement. When combined with the sending application in MSH-3, this value shall be uniquely identified.</p> <p>Example:</p> <p>'MSGID123456789'</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+**Table E.49 – Message header segment**
+
+| Element | Usage | Data type | Element name                            | Value                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------|-------|-----------|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| MSH-11  | R     | PT        | Processing Id                           | This field specifies whether to process the message using HL7 defined processing rules.<br>Encoded as<br><Processing ID (data type ID)>^<Processing Mode (data type ID)><br>PCD-01 constrains 'Processing ID' to come from HL7 2.6, table 0103 and 'Processing Mode' to come from HL7 2.6, table 0207 (if it is valued).<br>Example:<br>'P' for production is the typical value. There is also 'D' for debugging and 'T' for training<br>Processing ID shall be present. |
+| MSH-12  | R     | VID       | Version Id                              | This field is the HL7 V2.x version of the message.<br>Encoded as<br><Version ID (data type ID)>^<Internationalization Code (data type CWE)>^<International Version ID (data type CWE)><br><b>Shall</b> be '2.6'. PCD-01 constrains this to '2.6'                                                                                                                                                                                                                         |
+| MSH-13  | RE    | NM        | Sequence number                         | If valued, this number implies that the sequence number protocol is in use. This number would be incremented by one for each subsequent value.<br><b>Should not</b> be valued. The value is not used in IHE PCD                                                                                                                                                                                                                                                          |
+| MSH-14  | X     | ST        | Continuation pointer                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| MSH-15  | R     | ID        | Accept acknowledgement type             | This field specifies when an accept acknowledgement is required in response to the message. (PCD-01 is an unsolicited request and since no formal request has been issued there is nothing to acknowledge.)<br><b>Shall</b> be set to 'NE' for "never"                                                                                                                                                                                                                   |
+| MSH-16  | R     | ID        | Application acknowledgement type        | This specifies when an application acknowledgement is required in response to the message.<br><b>Shall</b> be set to 'AL' for always                                                                                                                                                                                                                                                                                                                                     |
+| MSH-17  | RE    | ID        | Country code                            |                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| MSH-18  | RE    | ID        | Character set                           | When empty it means the message is coded in ASCII-127.                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| MSH-19  | RE    | CWE       | Principal language of message           | When empty it defaults to EN^English^ISO659.                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| MSH-20  | X     | ID        | Alternate character set handling scheme |                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| MSH-21  | R     | EI        | Message profile identifier              | This field contains the formal registered name of the message profile to which the message adheres.<br>Encoded as                                                                                                                                                                                                                                                                                                                                                        |
+
+**Table E.49 – Message header segment**
+
+| Element | Usage | Data type | Element name                       | Value                                                                                                                                                                                                 |
+|---------|-------|-----------|------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|         |       |           |                                    | <Entity Identifier (data type ST)>^<Namespace ID (data type IS)>^<Universal ID (data type ST)>^<Universal ID Type (data type ID)><br>Example<br>'IHE PCD ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7' |
+| MSH-22  | X     | XON       | Sending Responsible Organization   | Business organization that originated the message and is legally accountable. <b>Shall not</b> be valued                                                                                              |
+| MSH-23  | O     | XON       | Receiving Responsible Organization | Business organization that is intended receiver of message and is legally accountable for operating on it                                                                                             |
+| MSH-24  | O     | HD        | Sending Network Address            | Identifier of network location of sender                                                                                                                                                              |
+| MSH-25  | O     | HD        | Receiving Network Address          | Identifier of network location of receiver                                                                                                                                                            |
+
+#### E.4.2 PID
+
+The specifications in this clause are derived from the IHE PCD Technical Framework [IHE PCD-TF-2], Appendix B.
+
+The Patient identification segment conveys the relevant patient information for the subsequent observations. This segment is required.
+
+Table E.50 shows the core data in a patient identification segment.
+
+**Table E.50 – Patient identification segment**
+
+| Element | Usage | DT  | Element name               | Value                                                                                                                                                                                                                                                                |
+|---------|-------|-----|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| PID-1   | X     | SI  | Set ID – PID               |                                                                                                                                                                                                                                                                      |
+| PID-2   | X     | CX  | Patient ID                 |                                                                                                                                                                                                                                                                      |
+| PID-3   | R     | CX  | Patient Identifier List    | A list of identifiers that uniquely identify the patient. See clause E.5.1 for more information on the CX data type. Subfields CX-1, CX-4 and CX-5 shall be non-empty.<br>Example:<br>789567^^Imaginary Hospital^PI<br>28da0026bc42484^^&1.19.6.24.109.42.1.3&ISO^PI |
+| PID-4   | X     | CX  | Alternate Patient ID – PID |                                                                                                                                                                                                                                                                      |
+| PID-5   | R     | XPN | Patient Name               | This field contains the name(s) of the patient. The legal name ('L'), if present, shall occur first. See clause E.5.7 for more information on the XPN data type.<br>Example:<br>Clemens^Samuel^Langhorne^^^^L                                                        |
+
+**Table E.50 – Patient identification segment**
+
+| Element | Usage | DT  | Element name                    | Value                                                                                                                                              |
+|---------|-------|-----|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|
+| PID-6   | RE    | XPN | Mother's Maiden Name            | Mother's family birth name before marriage. May be valued. The legal name ('L'), if present, shall occur first.<br>Example:<br>Langdon^Olivia^^^^L |
+| PID-7   | RE    | DTM | Date/Time of Birth              | Date and Time of birth.<br>Encoded as<br>YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]<br>Time zone is required.<br>Example:<br>'20090726095730-0500'          |
+| PID-8   | RE    | IS  | Administrative Sex              | Code that denotes the patient's sex.<br>Example:<br>"F" for female; "M" for male                                                                   |
+| PID-9   | X     | XPN | Patient Alias                   |                                                                                                                                                    |
+| PID-10  | RE    | CWE | Race                            | Code that denotes patient's race                                                                                                                   |
+| PID-11  | RE    | XAD | Patient Address                 | Mailing address of the patient<br>Example:<br>123 Main St.^Raleigh^North Carolina^27613^M                                                          |
+| PID-12  | X     | IS  | Country Code                    |                                                                                                                                                    |
+| PID-13  | RE    | XTN | Phone Number-Home               | Patient's phone number. If valued, PCD-01 constrains this to two or fewer repetitions with primary phone number to be the first                    |
+| PID-14  | X     | XTN | Phone Number-Business           |                                                                                                                                                    |
+| PID-15  | RE    | CWE | Primary Language                | Code to denote patient's language. If valued, PCD-01 requires these terms to come from ISO639. May be valued                                       |
+| PID-16  | RE    | CWE | Marital Status                  | Code to denote patient's marital status. May be valued                                                                                             |
+| PID-17  | RE    | CWE | Religion                        | Code to denote patient's religion. May be valued                                                                                                   |
+| PID-18  | RE    | CX  | Patient Account Number          | Code to identify account patient charges are to be made to. May be valued                                                                          |
+| PID-19  | X     | ST  | SSN Number-Patient              |                                                                                                                                                    |
+| PID-20  | X     | DLN | Driver's License Number-Patient |                                                                                                                                                    |
+| PID-21  | RE    | CX  | Mother's Identifier             | Used as a field for linkage to mother for newborns. May be valued                                                                                  |
+| PID-22  | RE    | CWE | Ethnic Group                    | Additionally define patient's heritage. May be valued                                                                                              |
+| PID-23  | RE    | ST  | Birth Place                     | Augments PID-11. May be valued                                                                                                                     |
+| PID-24  | RE    | ID  | Multiple Birth Indicator        | Code to denote if patient was part of a multiple birth. May be valued                                                                              |
+| PID-25  | RE    | NM  | Birth Order                     | Denotes birth order for multiple birth participant. May be valued                                                                                  |
+
+**Table E.50 – Patient identification segment**
+
+| Element | Usage | DT  | Element name                | Value                                                                                                                                    |
+|---------|-------|-----|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------|
+| PID-26  | RE    | CWE | Citizenship                 | Patient's country citizenship. May be valued                                                                                             |
+| PID-27  | RE    | CWE | Veteran's Military Status   | Code to denote military status. May be valued                                                                                            |
+| PID-28  | X     | CWE | Nationality                 |                                                                                                                                          |
+| PID-29  | RE    | DTM | Patient Death Date and Time | Date and time of patient's death. May be valued                                                                                          |
+| PID-30  | RE    | ID  | Patient Death Indicator     | Code to denote whether patient is deceased. May be valued                                                                                |
+| PID-31  | RE    | ID  | Identity Unknown Indicator  | Code to denote whether patient's identity is known. May be valued                                                                        |
+| PID-32  | RE    | IS  | Identity Reliability Code   | Code to denote reliability of contained identity. May be valued                                                                          |
+| PID-33  | RE    | DTM | Last Update Date/Time       | Date/Time of last update to the patient's identifying and demographic data in this segment. May be valued                                |
+| PID-34  | RE    | HD  | Last Update Facility        | Identity of the facility that performed the last update to the patient's identifying and demographic data in this segment. May be valued |
+| PID-35  | X     | CWE | Species Code                | No value is assumed to be human. Required but can be empty. <b>Shall not</b> be valued                                                   |
+| PID-36  | X     | CWE | Breed Code                  | Animal breed. <b>Shall not</b> be valued                                                                                                 |
+| PID-37  | X     | ST  | Strain                      | Animal strain. <b>Shall not</b> be valued                                                                                                |
+| PID-38  | X     | CWE | Production Class Code       | Primary use for bred animal. <b>Shall not</b> be valued                                                                                  |
+| PID-39  | X     | CWE | Tribal Citizenship          | Code to denote patient's tribal status. <b>Shall not</b> be valued                                                                       |
+
+#### E.4.3 OBR
+
+The specifications in this clause are derived from the IHE PCD Technical Framework [IHE PCD-TF-2], Appendix B.
+
+The Observation request segment serves as the header to a group of observations. For Services interface purposes, an important aspect of this segment is the time start/end boundaries for the OBX grouping to follow. This segment is required.
+
+Table E.51 shows the core data in an observation request segment.
+
+**Table E.51 – Observation request segment**
+
+| Element | Usage | DT | Element name        | Value                                                                                                                                                                                                                                |
+|---------|-------|----|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| OBR-1   | R     | SI | Set ID OBR          | Sequence number of the order starting with 1 and increasing sequentially.                                                                                                                                                            |
+| OBR-2   | R     | EI | Placer Order Number | PCD-01 requires the 1st, 2nd and 3rd components of this field to be valued. If there is an existing order, this field shall be set to the identifier of the system that has placed that order. However, there is typically no unique |
+
+**Table E.51 – Observation request segment**
+
+| Element | Usage | DT  | Element name                 | Value                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------|-------|-----|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|         |       |     |                              | order for device observations, but rather an assumed "standing order".<br>In this case, 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 services client component, and the third component shall contain the EUI-64 of the device which implements the services client component.<br>Example:<br>AB12345^ORIGatewayInc ICU-04^ACDE48234567ABCD^EUI-64                                                                                                                                                                                                                                                                    |
+| OBR-3   | R     | EI  | Filler Order Number          | PCD-01 constrains the 1st, 2nd and 3rd components to be valued. However, there is typically no outstanding order for device observations, but rather an assumed "standing order".<br>In this case, the first component is an arbitrary order ID string, the second, third and fourth component are used like an HD to identify the application which implements the Services client component, and shall contain the EUI-64 of this device. For "standing orders", this value should match OBR-2.<br>Example:<br>AB12345^ORIGatewayInc ICU-04^ACDE48234567ABCD^EUI-64                                                                                                                                                                     |
+| OBR-4   | R     | CWE | Universal Service Identifier | This field shall contain the identifier code for the requested observation/test/battery. This can refer to specific existing orders, or nonspecific "standing" orders. "Universal" procedure codes from a code set recognized by HL7 should be used when available. Locally defined codes may be used by agreement where standardized codes are not available. <sup>^</sup><br><sup>^</sup><br>When reporting events related to "standing" orders, as is common in patient monitoring, these codes will likely describe a generic service such as: <sup>^</sup><br>266706003^continuous ECG monitoring^SNOMED-CT <sup>^</sup><br>359772000^glucose monitoring at home^SNOMED-CT <sup>^</sup><br>182777000^monitoring of patient^SNOMED-CT |
+| OBR-5   | X     | ID  | Priority – OBR               |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| OBR-6   | X     | DTM | Requested Date/Time          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| OBR-7   | RE    | DTM | Observation Date/Time        | This is the base time for the observations that follow. If any following OBX segments have a timestamp, it shall be equal to or greater than this value. If any following OBX segments do not have a timestamp, then it is assumed to be equal to this OBR time. However, Continua PCD-01 OBX segments that are physiological measurements will always have a                                                                                                                                                                                                                                                                                                                                                                             |
+
+**Table E.51 – Observation request segment**
+
+| Element              | Usage | DT  | Element name              | Value                                                                                                                                                                                                                                                                                          |
+|----------------------|-------|-----|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                      |       |     |                           | timestamp. If the sensor device does not provide one, the PHG enters its time of reception as the timestamp. Thus this field shall always be valued.<br>Example:<br>20091225095715+0500                                                                                                        |
+| OBR-8                | RE    | DTM | Observation End Date/Time | This is the base end time for the observations that follow. If any following OBX segments have a timestamp, it shall be strictly less than this value. Note, <i>not less than or equal to!</i> If there is only one measurement this entry is not required.<br>Example:<br>20100101095715+0500 |
+| OBR-9 through OBR-50 |       |     |                           | <b>Shall not</b> be valued.                                                                                                                                                                                                                                                                    |
+
+#### E.4.4 OBX
+
+The specifications in this clause are derived from the IHE PCD Technical Framework [IHE PCD-TF-2], Appendix B.
+
+This segment is used to convey a single observation as well as the features, capabilities and status of the PHG and sensor device. This is the segment where all the observation detail is conveyed. This segment is required. In operation, Continua PCD-01 documents will always have several OBX segments for every OBR.
+
+Table E.52 shows the core data in a single observation segment.
+
+**Table E.52 – Single observation segment**
+
+| Element | Usage | DT  | Element name           | Value                                                                                                                                                                                                                                                                                           |
+|---------|-------|-----|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| OBX-1   | R     | SI  | Set ID – OBX           | Sequence number of the OBX in this message.                                                                                                                                                                                                                                                     |
+| OBX-2   | C     | ID  | Value Type             | HL7 data type of value in OBX-5. <b>Shall</b> be valued if OBX-5 is valued.<br>For a Services interface usage the most common data types are<br>NM – numeric<br>CWE – coded with exceptions<br>ST – string<br>See HL7 data type detail in clause E.5.<br>Example (weight scale – weight):<br>NM |
+| OBX-3   | R     | CWE | Observation Identifier | An encoded string that uniquely identifies this observation type. This is typically the encoded version of the MDC code of the observation type or metric id. See clause E.5.1 for specifics on how this encoded.<br>Example (weight scale – weight):<br>188736^MDC_MASS_BODY_ACTUAL^MDC        |
+
+**Table E.52 – Single observation segment**
+
+| Element | Usage | DT     | Element name              | Value                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------|-------|--------|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| OBX-4   | R     | ST     | Observation Sub-ID        | Contains the string representing the hierarchical identity of the observation.<br>Example (weight scale – weight):<br>1.0.0.15                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| OBX-5   | C     | varies | Observation Value         | The actual observation value in the format appropriate for the specified data type in OBX-2.<br>Example (weight scale – weight):<br>153.6                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| OBX-6   | C     | CWE    | Units                     | The encoded string that identifies the units for the observation value. This is typically the encoded version of the MDC code for the units. Empty if OBX-5 does not have any units.<br>Example (weight scale – weight):<br>263875^MDC_DIM_KILO_G^MDC                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| OBX-7   | CE    | ST     | References Range          | The reference range for the observation.<br>Example:<br>3.5 – 4.5                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| OBX-8   | CE    | IS     | Abnormal Flags            | A coded value that conveys additional information about the observation. This field is used to convey the MeasurementStatus of each metric when it is reported by the Personal Health Device. D.1.3.1.7 includes a table of IS codes to be used for the IEEE 11073 MeasurementStatus values, along with additional information on handling measurement status. It is also used to code the occurrences of the [ISO/IEEE 11073-20601] special values such as NaN, plus or minus infinity, etc. The codes are given by [IHE PCD-01] Appendix B.8 OBX-8 and in this document in Table D.8 and Table D.9. If this field is valued, it will have an influence on the value of OBX-11. |
+| OBX-9   | X     | NM     | Probability               |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| OBX-10  | CE    | ID     | Nature of Abnormal Test   | <b>Should not be valued</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| OBX-11  | R     | ID     | Observation Result Status | This field conveys additional information about the observations quality/status.<br>For the Services interface, a value of 'R' meaning 'results entered -- not verified', shall be used for unreviewed data captured directly by devices with no specific measurement status information. Note that 'X' is used if the OBX is not a physiological measurement. If the measurement is a physiological measurement and has an OBX-8 entry, the OBX-11 value is given by the table in [IHE PCD-01] Appendix B.8 OBX-8 and in this document in Table D.8 and Table D.9.                                                                                                              |
+
+**Table E.52 – Single observation segment**
+
+| Element          | Usage | DT  | Element name                      | Value                                                                                                                                                                                                                                                                                                                                                          |
+|------------------|-------|-----|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| OBX-12           | X     | DTM | Effective Date of Reference Range |                                                                                                                                                                                                                                                                                                                                                                |
+| OBX-13           | X     | ST  | User Defined Access Checks        |                                                                                                                                                                                                                                                                                                                                                                |
+| OBX-14           | RE    | DTM | Date/Time of Observation          | Optional timestamp specific to this observation. OBR has overall timestamp inherited by all observations if not overridden here. This timestamp shall be greater than or equal to the parent OBR-7. If OBR-8 is valued, then this timestamp shall be strictly less than OBR-8. This field will always be valued in Metric-OBXes in a Continua PCD-01 document. |
+| OBX-15           | RE    | CWE | Producer's ID                     | <b>Should not</b> be valued                                                                                                                                                                                                                                                                                                                                    |
+| OBX-16           | RE    | XCN | Responsible Observer              | <b>Should not</b> be valued                                                                                                                                                                                                                                                                                                                                    |
+| OBX-17           | RE    | CWE | Observation Method                | Coded entry used to denote the method or procedure by which the observation was obtained. In many cases the value specified in OBX-3 implies the method/procedure used in obtaining observation. If it does not then this field may be used to convey an appropriate MDC code                                                                                  |
+| OBX-18           | RE    | EI  | Equipment Instance Identifier     | <b>Should</b> be an EUI-64 which is unique to the originating device of this observation. For Continua devices this entry is only required for the MDS OBXes. See [IHE PCD-01] Appendix B.8 OBX-18.<br>Example:<br>The System-Id of the Personal Health Device information source<br>012345678FEDCBA00^012345678FEDCBA00^EUI-64                                |
+| OBX-19           | CE    | DTM | Date/Time of Analysis             | <b>Should not</b> be valued. Use of OBX-14 is preferred. If valued, this value shall duplicate the OBX-14 value                                                                                                                                                                                                                                                |
+| OBX-20           | RE    | CWE | Observation Site                  | If valued, this field shall contain an appropriate MDC code for the observation. This field might be populated if there are appropriate supplemental types values.                                                                                                                                                                                             |
+| OBX-21 to OBX-25 |       |     |                                   | <b>Should not</b> be valued                                                                                                                                                                                                                                                                                                                                    |
+
+#### E.4.5 PV1
+
+The specifications in this clause are derived from the IHE PCD Technical Framework [IHE PCD-TF-2], Appendix B.
+
+The patient visit segment details the visit specific data for an encounter. It includes account and physical location information. It is unlikely that this segment will be required for the Services interface so the details have been omitted. Information on this segment can be found in [IHE PCD-TF-2] and Chapter 3 (Patient Administration) of [HL7 2.6].
+
+#### E.4.6 NTE
+
+The specifications in this clause are derived from the IHE PCD Technical Framework [IHE PCD-TF-2], Appendix B.
+
+The Note segment can be used for all manner of auxiliary descriptive text to send with the message. The PCD-01 limits its usage to only after the OBR and OBX segments.
+
+Table E.53 shows the core data in a note segment.
+
+**Table E.53 – Note segment**
+
+| Element | Usage | DT  | Element name         | Value                                                                                |
+|---------|-------|-----|----------------------|--------------------------------------------------------------------------------------|
+| NTE-1   | R     | SI  | Set ID               | Number is required for distinguishing when multiple NTE segments appear in a message |
+| NTE-2   | X     | ID  | Source of comment    |                                                                                      |
+| NTE-3   | RE    | FT  | Comment              | The text of the comment                                                              |
+| NTE-4   | X     | CWE | Comment Type         |                                                                                      |
+| NTE-5   | O     | XCN | Entered by           |                                                                                      |
+| NTE-6   | O     | DTM | Entered Date/Time    |                                                                                      |
+| NTE-7   | O     | DTM | Effective start date |                                                                                      |
+| NTE-8   | O     | DTM | Expiration date      |                                                                                      |
+
+#### E.4.7 TQ1
+
+The specifications in this clause are derived from the IHE PCD Technical Framework [IHE PCD-TF-2], Appendix B.
+
+The Timing/Quantity segment details the timing and execution of events and actions. It includes quantity, frequency, priority and timing information. This segment **should not** be used on the Services interface. It is unlikely that this segment will be required for the Services interface, so the details have been omitted. Information on this segment can be found in [IHE PCD-TF-2] and Chapter 4 (Order Entry) of [HL7 2.6].
+
+#### E.4.8 MSA
+
+The specifications in this clause are derived from the IHE PCD Technical Framework [IHE PCD-TF-2], Appendix B.
+
+The message acknowledgement segment contains the information communicated when acknowledging a message.
+
+Table E.54 shows the core data in a message acknowledgement segment.
+
+**Table E.54 – Message acknowledgement segment**
+
+| Element | Usage | DT | Element name         | Value                                                                                                                                                                                                                   |
+|---------|-------|----|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| MSA-1   | R     | ID | Acknowledgement Code | This shall be one of the values found at: <a href="http://www.ihe.net/Technical_Framework/upload/IHE_PCD_TF_Vol2_FT_2011-08-12.pdf">http://www.ihe.net/Technical_Framework/upload/IHE_PCD_TF_Vol2_FT_2011-08-12.pdf</a> |
+| MSA-2   | R     | ST | Message Control Id   | This field contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent                                                                    |
+| MSA-3   | X     | ST | Text Message         |                                                                                                                                                                                                                         |
+
+**Table E.54 – Message acknowledgement segment**
+
+| Element | Usage | DT | Element name                 | Value |
+|---------|-------|----|------------------------------|-------|
+| MSA-4   | X     | NM | Expected Sequence Number     |       |
+| MSA-5   | X     | ID | Delayed Acknowledgement Type |       |
+| MSA-6   | X     | CE | Error Condition              |       |
+| MSA-7   | X     | NM | Message Waiting Number       |       |
+| MSA-8   | X     | ID | Message Waiting Priority     |       |
+
+#### E.4.9 ERR
+
+The specifications in this clause are derived from the IHE PCD Technical Framework [IHE PCD-TF-2], Appendix B.
+
+This segment is used to add comments about an error to the acknowledgement message with an Acknowledgement Code of 'Application Error'. However, this segment **may** be transmitted with any Acknowledgement message including messages that have no error ('message accepted') as the segment can be used to transfer user information. Messages are to be accepted/rejected in their entirety, so if a services observation receiver device reports an ERR segment with severity E (Error) or F (Fatal Error), the Message acknowledgement value **shall** be AE (Application Error) or AR (Application Reject).
+
+Table E.55 shows the core data in an error segment.
+
+**Table E.55 – Error segment**
+
+| Element | Usage | DT  | Element name            | Value                                                                                                                                                                                                                                                                                                                                                   |
+|---------|-------|-----|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ERR-1   | RE    | ELD | Error code and location | Shall not be valued.<br>ERR-1 is included in HL7 2.6 for backward compatibility only.                                                                                                                                                                                                                                                                   |
+| ERR-2   | O     | ERL | Error location          | Should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations.<br>Components: <Segment ID(ST)>^<Segment Sequence(NM)>^<Field Position(NM)>^<Field Repetition(NM)>^<Component Number(NM)>^<Sub-Component Number(NM)> |
+| ERR-3   | R     | CWE | HL7 error code          | If the ERR segment is transmitted, this value shall be set to a valid error code defined in Table E.53                                                                                                                                                                                                                                                  |
+| ERR-4   | R     | ID  | Severity                | If the ERR segment is transmitted, this value shall be set to a valid error code defined in Table E.55                                                                                                                                                                                                                                                  |
+| ERR-5   | O     | CWE | Application error code  |                                                                                                                                                                                                                                                                                                                                                         |
+| ERR-6   | O     | ST  | Application error       |                                                                                                                                                                                                                                                                                                                                                         |
+
+**Table E.55 – Error segment**
+
+| Element | Usage | DT  | Element name            | Value |
+|---------|-------|-----|-------------------------|-------|
+|         |       |     | parameter               |       |
+| ERR-7   | O     | TX  | Diagnostic information  |       |
+| ERR-8   | O     | TX  | User message            |       |
+| ERR-9   | O     | IS  | Inform person indicator |       |
+| ERR-10  | O     | CWE | Override type           |       |
+| ERR-11  | O     | CWE | Override reason code    |       |
+| ERR-12  | O     | XTN | Help desk contact point |       |
+
+**E.4.10 HL7 v2.6 error tables**
+
+Table E.56 shows HL7 Table 0357 with message error condition codes and Table E.57 shows HL7 Table 0516, which indicates error severity.
+
+**Table E.56 – HL7 Table 0357 – Message error condition code**
+
+| Value | Description                | Comment                                                                                                                                                |
+|-------|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0     | Message accepted           | Success. Optional, as the AA conveys success. Used for systems that must always return a status code                                                   |
+| 100   | Segment sequence error     | Error: The message segments were not in the proper order, or required segments are missing                                                             |
+| 101   | Required field missing     | Error: A required field is missing from a segment                                                                                                      |
+| 102   | Data type error            | Error: The field contained data of the wrong data type, e.g., an NM field contained "FOO"                                                              |
+| 103   | Table value not found      | Error: A field of data type ID or IS was compared against the corresponding table, and no match was found                                              |
+| 200   | Unsupported message type   | Rejection: The Message Type is not supported                                                                                                           |
+| 201   | Unsupported event code     | Rejection: The Event Code is not supported                                                                                                             |
+| 202   | Unsupported processing id  | Rejection: The Processing ID is not supported                                                                                                          |
+| 203   | Unsupported version id     | Rejection: The Version ID is not supported                                                                                                             |
+| 204   | Unknown key identifier     | Rejection: The ID of the patient, order, and etc., was not found. Used for transactions other than additions, e.g., transfer of a non-existent patient |
+| 205   | Duplicate key identifier   | Rejection: The ID of the patient, order, and etc., already exists. Used in response to addition transactions (Admit, New Order, etc.)                  |
+| 206   | Application record locked  | Rejection: The transaction could not be performed at the application storage level, e.g., database locked                                              |
+| 207   | Application internal error | Rejection: A catch-all for internal errors not explicitly covered by other codes                                                                       |
+
+**Table E.57 – HL7 Table 0516 – Error severity**
+
+| Value | Description | Comment                                                                  |
+|-------|-------------|--------------------------------------------------------------------------|
+| W     | Warning     | Transaction successful, but there many issues                            |
+| I     | Information | Transaction was successful but includes information e.g., inform patient |
+| E     | Error       | Transaction was unsuccessful                                             |
+| F     | Fatal Error | Message not processed due to application or network failure condition    |
+
+**E.5 HL7 Data types – Observations**
+
+The data types in Table E.58 are derived from Appendix C "*Common Data Types*" of [IHE PCD TF-2] and chapter 2.15, (Table 0440 – Data Types) of [HL7 2.6].
+
+**Table E.58 – HL7 data types used in OBX-2**
+
+| Data type | Data type name                                                                                                                                                                                                                                                         | LEN   | Category                             | Comment                                     |
+|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|--------------------------------------|---------------------------------------------|
+| CF        | Coded element with formatted values                                                                                                                                                                                                                                    | 65536 | Code Values                          |                                             |
+| CWE       | Coded with exceptions                                                                                                                                                                                                                                                  | 705   | Code Values                          |                                             |
+| DT        | Date                                                                                                                                                                                                                                                                   | 8     | Date/Time                            |                                             |
+| DTM       | Date/time                                                                                                                                                                                                                                                              | 24    |                                      |                                             |
+| ED        | Encapsulated data                                                                                                                                                                                                                                                      | 65536 | Specialty/Chapter Specific           | Supports ASCII MIME-encoding of binary data |
+| FT        | Formatted text                                                                                                                                                                                                                                                         | 65536 | Alphanumeric                         |                                             |
+| NA        | Numeric array<br><br>NOTE – Numeric Array is not a valid data type for OBX-3 according to [HL7 2.6] 7.4.2, Table 0125 but is explicitly allowed on the Continua Services interface in order to report waveform data such as RT-SA metrics from [ISO/IEEE 11073-20601]. | 65536 | Specialty/Chapter Specific: waveform | For waveform data only                      |
+| NM        | Numeric                                                                                                                                                                                                                                                                | 16    | Numerical                            |                                             |
+| SN        | Structured numeric                                                                                                                                                                                                                                                     | 36    | Numerical                            |                                             |
+| ST        | String                                                                                                                                                                                                                                                                 | 199   | Alphanumeric                         |                                             |
+| TM        | Time                                                                                                                                                                                                                                                                   | 16    | Date/Time                            |                                             |
+| TX        | Text data                                                                                                                                                                                                                                                              | 65536 | Alphanumeric                         |                                             |
+| XAD       | Extended address                                                                                                                                                                                                                                                       | 631   | Demographics                         | Replaces AD as of v 2.3                     |
+| XCN       | Extended composite ID number and name                                                                                                                                                                                                                                  | 3002  | Code Values                          | Replaces CN as of v 2.3                     |
+| XON       | Extended composite name and ID number for organizations                                                                                                                                                                                                                | 567   | Demographics                         |                                             |
+| XPN       | Extended person name                                                                                                                                                                                                                                                   | 1103  | Demographics                         | Replaces PN as of v 2.3                     |
+
+### E.5.1 CWE
+
+The specifications in this clause are derived from the IHE PCD Technical Framework [IHE PCD-TF-2], Appendix C.
+
+Table E.59 shows the details for the coded with exceptions (CWE) data type.
+
+**Table E.59 – CWE**
+
+| Name                               | Usage | DT | Comment                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|------------------------------------|-------|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Identifier                         | R     | ST | This is the actual code, unique to the coding system in component 3.<br>For MDC codes this value shall be the integer formed by treating the code partition as the high 16 bits of a 32 bit number and the particular code as the lower 16 bits.<br>Example:<br>MDC_MASS_BODY_ACTUAL has value 57664 in partition MDC_PART_SCADA. Hence, this would be 2::57664.<br>$(2 * 65536) + 57664 = 188736$ . Hence, the identifier would be 188736.<br>For values derived from ASN.1 BITS fields, this value shall be '1' for "true" or "on" and '0' for "false" or "off"                 |
+| Text                               | RE    | ST | This is the textual form of the code point.<br>PCD-01 specifies this field usage as 'R', but for Services interface usage this has been relaxed to 'RE'. This value should be present if known.<br>For MDC codes, this value shall match the normative Reference Id of the nomenclature code if known.<br>Example: Continuing the previous example this field would be valued "MDC_MASS_BODY_ACTUAL".<br>For values derived from ASN.1 BITS fields, this value shall match the normative identifier of the bit field's name if known, followed by the bit position in parentheses |
+| Name of Coding System              | RE    | ID | This is the name of the coding scheme used for the identifier/text. For MDC codes, this shall be set to 'MDC'<br>For values derived from ASN.1 BITS fields, this value shall not be valued                                                                                                                                                                                                                                                                                                                                                                                        |
+| Alternate Identifier               | RE    | ST | Typically not used for Services interface                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| Alternate Text                     | RE    | ST | Rarely used for the Services interface but used encoding the Unit-LabelString attribute value to the Unit-Code attribute value                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| Name of Alternate Coding System    | RE    | ID | Typically not used for Services interface                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| Coding System Version ID           | C     | ST | Typically not used for Services interface                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| Alternate Coding System Version ID | O     | ST | Typically not used for Services interface                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| Original Text                      | O     | ST | Typically not used for Services interface                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+#### E.5.1.1 Examples
+
+```
+'188736^MDC_MASS_BODY_ACTUAL^MDC'
+'263075^MDC_DIM_KILO_G^MDC'
+```
+
+## E.5.2 DTM
+
+The date/time data type is a string encoded as follows:
+
+- YYYY[MM[DD[HH[MM[SS[.S[S[S[S]]]]]]]]][+/-ZZZZ]
+- -0000 is used to indicate a DTM that is UTC aware but not local time aware.
+- 0000 indicates a DTM that is both UTC and local time aware and happens to be in a GMT time zone.
+
+### E.5.2.1 Example
+
+'20090726095730+0000'
+
+## E.5.3 NM
+
+The numeric is a sequence of characters that specify a number. Only digits, '+', '-' and '.' Characters are allowed.
+
+### E.5.3.1 Examples
+
+123  
+-57.633
+
+## E.5.4 ST
+
+The string data type is merely character data.
+
+### E.5.4.1 Example
+
+"arbitrary collection of characters"
+
+## E.5.5 NA - numeric array
+
+The specifications in this clause are extracted from 2.A Data Types of [HL7 2.6].
+
+Table E.60 describes the HL7 component table for a numeric array data type.
+
+**Table E.60 – HL7 component table – numeric array**
+
+| SEQ | LEN | DT | OPT | TBL# | COMPONENT NAME | COMMENTS | SEC.REF. |
+|-----|-----|----|-----|------|----------------|----------|----------|
+| 1   | 16  | NM | R   |      | Value1         |          |          |
+| 2   | 16  | NM | O   |      | Value2         |          |          |
+| 3   | 16  | NM | O   |      | Value3         |          |          |
+| 4   | 16  | NM | O   |      | Value4         |          |          |
+
+Definition: This data type is used to represent a series (array) of numeric values. A field of this type may contain a one-dimensional array (vector or row) of numbers. Also, by allowing the field to repeat, a two-dimensional array (table) of numbers may be transmitted using this format, with each row of the table represented as one repetition of the field. Arrays that have one or more values not present may be transmitted using this data type. "Not present" values are represented as two adjacent component delimiters. If the absent values occur at the end of a row, the trailing component delimiters may be omitted. If an entire row of a table has no values, no component delimiters are necessary (in this case, there will be two adjacent repetition delimiters).
+
+**Maximum length:** 65536
+
+### E.5.5.1 Example 1: vector of eight numbers
+
+|                                |
+|--------------------------------|
+| 125^34^-22^-234^569^442^-212^6 |
+|--------------------------------|
+
+### E.5.5.2 Example 2:3 x 3 array of numbers
+
+|                                        |
+|----------------------------------------|
+| 1.2^-3.5^5.2~2.0^3.1^-6.2~3.5^7.8^-1.3 |
+|----------------------------------------|
+
+### E.5.5.3 Example 3: 5 x 4 array of numbers with the values in positions (1,1), (2,2), (2,3), (3,3), (3,4), (4,1), (4,2), (4,3) and (4,4) not present
+
+|                              |
+|------------------------------|
+| ^2^3^4~5^^8~9^10~17^18^19^20 |
+|------------------------------|
+
+## E.5.6 XAD
+
+The specifications in this clause are derived from the IHE PCD Technical Framework [IHE PCD-TF-2], Appendix C.
+
+Table E.61 shows elements of the extended address (XAD) data type.
+
+**Table E.61 – XAD**
+
+| Name                         | Usage | DT  | Comment                                                                                                   |
+|------------------------------|-------|-----|-----------------------------------------------------------------------------------------------------------|
+| Street Address               | R     | SAD | Street address<br>Example:<br>"100 Main St."                                                              |
+| Other Designation            | O     | ST  | Second line of address.                                                                                   |
+| City                         | R     | ST  | City element of address<br>Example:<br>"Raleigh"                                                          |
+| State or Province            | R     | ST  | State or province element of address<br>Example:<br>"NC" or "North Carolina"                              |
+| Zip or Postal Code           | R     | ST  | Postal code element of address<br>Example:<br>"27613"                                                     |
+| Country                      | O     | ID  | Country element of address                                                                                |
+| Address Type                 | R     | ID  | Code that denotes the type of address. PCD-01 requires this value to be "M" to indicate "mailing address" |
+| Other Geographic Designation | O     | ID  | Code to denote any other designation. Not typically used for Services interface                           |
+| County/Parish Code           | O     | IS  | Code to denote the county address is within. Not typically used for Services interface                    |
+| Census Tract                 | O     | IS  | Code to denote the census tract address is within. Not typically used for Services interface              |
+| Address Representation Code  | O     | ID  | Code to denote the representation code. Not typically used for Services interface                         |
+| Address Validity Range       | X     | DR  | Never used                                                                                                |
+| Effective Date               | O     | DTM | Start date of address validity. Not typically used for Services interface                                 |
+| Expiration Date              | O     | DTM | Stop date of address validity. Not typically used for Services interface                                  |
+
+**Table E.61 – XAD**
+
+| Name                  | Usage | DT  | Comment                                                                                                         |
+|-----------------------|-------|-----|-----------------------------------------------------------------------------------------------------------------|
+| Expiration Reason     | O     | CWE | Reason code to denote why address validity has ended. Not typically used for Services interface                 |
+| Temporary Indicator   | O     | ID  | Code that denotes whether address is temporary. Not typically used for Services interface                       |
+| Bad Address Indicator | O     | ID  | Code to denote whether address is bad. Not typically used for Services interface                                |
+| Address Usage         | O     | ID  | Code to denote intention of address usage. Not typically used for Services interface                            |
+| Addressee             | O     | ST  | Element identifies the "Care of" or "C/O" line of address. Not typically used for Services interface            |
+| Comment               | O     | ST  | Arbitrary description text. Not typically used for Services interface                                           |
+| Preference Order      | O     | NM  | Defines order of preference when multiple addresses are given. Not typically used for Services interface        |
+| Protection Code       | O     | CWE | Code to denote any special sensitivity in handling of address. Not typically used for Services interface        |
+| Address Identifier    | O     | EI  | Unique identifier to enable a linking of address to multiple people. Not typically used for Services interface. |
+
+**E.5.6.1 Examples**
+
+|                                              |
+|----------------------------------------------|
+| 123 Main St.^^Raleigh^North Carolina^27613^M |
+|----------------------------------------------|
+
+**E.5.7 XPN**
+
+The specifications in this clause are derived from the IHE PCD Technical Framework [IHE PCD-TF-2], Appendix C.
+
+Table E.62 shows the core data in the extended person name (XPN) data type.
+
+**Table E.62 – XPN**
+
+| Name                                       | Usage | DT | Comment                                                                                                                       |
+|--------------------------------------------|-------|----|-------------------------------------------------------------------------------------------------------------------------------|
+| Family Name                                | RE    | FN | Family or last name. According to [IHE PCD-01] this entry is required if known to the sender. Not clear how that is testable. |
+| Given Name                                 | RE    | ST | First name                                                                                                                    |
+| Second and Further Given Names or Initials | RE    | ST | Middle name(s) separated by spaces                                                                                            |
+| Suffix                                     | RE    | ST | Suffix e.g., Jr. or III                                                                                                       |
+| Prefix                                     | RE    | ST | Prefix e.g., Dr.                                                                                                              |
+| Degree                                     | X     | IS | Never used                                                                                                                    |
+| Name Type Code                             | R     | ID | Code to indicate type of name. Common codes would be "L" for legal name or "A" for alias name                                 |
+| Name Representation Code                   | RE    | ID | Code to indicate representation codes. The most common code would be "A" for alphabetic.                                      |
+
+**Table E.62 – XPN**
+
+| Name                | Usage | DT  | Comment                                                                                                   |
+|---------------------|-------|-----|-----------------------------------------------------------------------------------------------------------|
+| Name Context        | RE    | CWE | Context in which name is used. Not typically used for Services interface                                  |
+| Name Validity Range | X     | DR  | Never used                                                                                                |
+| Name Assembly Order | RE    | ID  | Code to indicate display order. Not typically used for Services interface                                 |
+| Effective Date      | RE    | DTM | Start date of the name's validity. Not typically used for Services interface                              |
+| Expiration Date     | RE    | DTM | End date of the name's validity. Not typically used for Services interface                                |
+| Professional Suffix | RE    | ST  | Specifies abbreviation(s) denoting professional qualifications. Not typically used for Services interface |
+
+**E.5.7.1 Examples**
+
+```
+Clemens^Samuel^Langhorne^^^^^L
+Twain^Mark^^^^^^^A
+```
+
+**E.6 Other HL7 data types**
+
+The specifications in this clause are derived from the IHE PCD Technical Framework Volume 2, Revision 2.0 [IHE PCD TF 2012 2].
+
+This clause contains the definition of a number of common data types used in the PCD-01 transaction, but are not used as observations. Please see [IHE PCD-01] or [HL7 v2.6] for a complete list of data types.
+
+**E.6.1 CX**
+
+Table E.63 shows details of the HL7 CX data type.
+
+**Table E.63 – CX**
+
+| Name                 | Usage | DT  | Comment                                                                                                                                                                    |
+|----------------------|-------|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ID Number            | R     | ST  | The value of the identifier                                                                                                                                                |
+| Check Digit          | RE    | ST  | Check digit. Not typically used for Services interface                                                                                                                     |
+| Check Digit Scheme   | RE    | ID  | Code to indicate how check digit was calculated. Not typically used for Services interface                                                                                 |
+| Assigning Authority  | R     | HD  | Unique name of the system/organization that creates the data.                                                                                                              |
+| Identifier Type Code | RE    | ID  | A code to indicate the scheme for the identifier. A very common type code is "PI" which indicates it is a Patient Internal Identifier or a code unique to the organization |
+| Assigning Facility   | RE    | HD  | Place where identifier was first assigned. Not typically used for Services interface                                                                                       |
+| Effective Date       | RE    | DT  | Date for identifier validity to start. Not typically used for Services interface                                                                                           |
+| Expiration Date      | RE    | DT  | Date for identifier validity to end. Not typically used for Services interface                                                                                             |
+| Assigning            | RE    | CWE | Geo-political body that assigned identifier. Not typically                                                                                                                 |
+
+**Table E.63 – CX**
+
+| Name                           | Usage | DT  | Comment                                                                                  |
+|--------------------------------|-------|-----|------------------------------------------------------------------------------------------|
+| Jurisdiction                   |       |     | used for Services interface                                                              |
+| Assigning Agency or Department | RE    | CWE | Agency or department that assigned identifier. Not typically used for Services interface |
+
+**E.6.1.1 Examples**
+
+```
+789567^^Imaginary Hospital^PI
+P12345^^Imaginary Hospital
+```
+
+**E.6.1.2 EI**
+
+The specifications in this clause are derived from Appendix C in the IHE PCD Technical Framework Volume 2, Revision 2.0 [IHE PCD TF 2012 2].
+
+Table E.64 shows the core data in an entity identifier.
+
+**Table E.64 – Entity identifier**
+
+| Name              | Usage | DT | Comment                                                                                                |
+|-------------------|-------|----|--------------------------------------------------------------------------------------------------------|
+| Entity Identifier | R     | ST | Always required. PCD-01 constrains this to be 16 characters unless extended due to national extensions |
+| Namespace ID      | RE    | IS | May be used without components 3 and 4                                                                 |
+| Universal ID      | ST    | ID | May be used in conjunction with component 4 but without component 2                                    |
+| Universal ID Type | RE    | ID | May be used in conjunction with component 3 but without component 2. EUI-64 is a universal ID type.    |
+
+The important issue with this data type is whether or not one is using a universal ID type or Namespace ID. A Universal ID Type would be a EUI-64 such as a system id. A time base might be a case where a Namespace ID would be used. The distinction has caused confusion in versions prior to DG2015.
+
+**E.6.1.3 Examples**
+
+```
+0123456789ABCDEF^^0123456789ABCDEF^EUI-64 (universal id case)
+AB12345^RiversideHospital (local id case)
+BT_ABCDEF123456_01^TIMEBASE_ID (local id case)
+AB12345^^1.2.840.45.67^ISO (universal id case)
+AB12345^RiversideHospital^1.2.840.45.67^ISO (universal id case)
+```
+
+**E.6.2 ID coded value for HL7 defined tables**
+
+The specifications in this clause are derived from the [HL7 v2.6], clause 2.A on data types.
+
+Table E.65 shows the core data in a HL7 Component table for ID string datacoded value for HL7 defined tables.
+
+**Table E.65 – HL7 Component table – ID string datacoded value for HL7 defined tables**
+
+| SEQ | LEN | DT | OPT | TBL# | COMPONENT NAME                     | COMMENTS | SEC.REF. |
+|-----|-----|----|-----|------|------------------------------------|----------|----------|
+|     |     |    |     |      | Coded value for HL7-defined tables |          |          |
+
+**Maximum length:** Varies dependent on length of longest code in code set.
+
+The value of such a field follows the formatting rules for an ST field except that it is drawn from a table of legal values. There shall be an HL7 table number associated with ID data types. An example of an ID field is OBR-25-result status. This data type should be used only for HL7 tables (see clause 2.5.3.6 "Table" in [HL7 2.6]). The reverse is not true, since in some circumstances it is more appropriate to use the CNE or CWE data type for HL7 tables.
+
+### E.6.3 IS coded value for user-defined tables
+
+The specifications in this clause are derived from the [HL7 v2.6], clause 2.A on data types.
+
+Table E.66 shows the core data in a HL7 component table for IS coded value for user-defined tables string data.
+
+**Table E.66 – HL7 component table – IS coded value for user-defined tables string data**
+
+| SEQ | LEN | DT | OPT | TBL# | COMPONENT NAME                      | COMMENTS | SEC.REF. |
+|-----|-----|----|-----|------|-------------------------------------|----------|----------|
+|     | 20  |    |     |      | Coded Value for User-Defined Tables |          |          |
+
+**Maximum length:** 20
+
+The value of such a field follows the formatting rules for an ST field except that it is drawn from a site-defined (or user-defined) table of legal values. There shall be an HL7 table number associated with IS data types. An example of an IS field is the Degree field defined in the XPN data type. This data type should be used only for user-defined tables. What this means is that IS data types are always parts of another data type and do not appear as stand-alone field entries. The reverse is not true, since in some circumstances, it is more appropriate to use the CWE data type for user-defined tables instead of the IS data type.
+
+### E.6.4 SI sequence ID
+
+The specifications in this clause are derived from the [HL7 v2.6], clause 2.A on data types.
+
+Table E.67 shows the core data in a HL7 Component table for SI sequence ID.
+
+**Table E.67 – HL7 component table – SI sequence ID**
+
+| SEQ | LEN | DT | OPT | TBL# | COMPONENT NAME | COMMENTS | SEC.REF. |
+|-----|-----|----|-----|------|----------------|----------|----------|
+|     | 4   |    |     |      | Sequence ID    |          |          |
+
+**Definition:** A non-negative integer in the form of a NM field. The uses of this data type are defined in the chapters defining the segments and messages in which it appears.
+
+**Maximum length:** 4. This allows for a number between 0 and 9999 to be specified.
+
+### E.6.5 SN structured numeric
+
+The specifications in this clause are derived from the HL7 v2.6, 2.A Data Types.
+
+Table E.68 shows the core data in a HL7 Component table for a SN structured numeric data type.
+
+**Table E.68 – HL7 component table – SN structured numeric**
+
+| SEQ | LEN | DT | OPT | TBL# | COMPONENT NAME   | COMMENTS | SEC.REF. |
+|-----|-----|----|-----|------|------------------|----------|----------|
+| 1   | 2   | ST | O   |      | Comparator       |          |          |
+| 2   | 15  | NM | O   |      | Num1             |          |          |
+| 3   | 1   | ST | O   |      | Separator/Suffix |          |          |
+| 4   | 15  | NM | O   |      | Num2             |          |          |
+
+**Definition:** The structured numeric data type is used to unambiguously express numeric clinical results along with qualifications. This enables receiving systems to store the components separately, and facilitates the use of numeric database queries. The corresponding sets of values indicated with the <comparator> and <separator/suffix> components are intended to be the authoritative and complete set of values. If additional values are needed for the <comparator> and <separator/suffix> components, they should be submitted to HL7 for inclusion in the Standard.
+
+If <num1> and <num2> are both non-null, then the separator/suffix must be non-null. If the separator is "–", the data range is inclusive; e.g., <num1> – <num2> defines a range of numbers x, so that:<num1> <=x<= <num2>.
+
+**Maximum length:** 36
+
+**E.6.5.1 Comparator (ST)**
+
+Defined as greater than, less than, greater than or equal, less than or equal, equal, and not equal, respectively (= ">" or "<" or ">=" or "<=" or "=" or "<>")
+
+If this component is not valued, it defaults to equal ("=").
+
+**E.6.5.2 Num1 (NM)**
+
+A number.
+
+**E.6.5.3 Separator/Suffix (ST)**
+
+"–" or "+" or "/" or "." or ":"
+
+**E.6.5.4 Examples**
+
+```
+|>^100| (greater than 100)
+|^100^-^200| (equal to range of 100 through 200)
+|^1:^228| (ratio of 1 to 128, e.g., the results of a serological test)
+|^2^+| (categorical response, e.g., occult blood positivity)
+```
+
+**E.6.5.5 Num2 (NM)**
+
+A number or null depending on the measurement.
+
+**E.6.6 XTN**
+
+The specifications in this clause are derived from the IHE PCD Technical Framework Volume 2, Revision 2.0 [IHE PCD TF 2012 2].
+
+Table E.69 shows the details for the XTN data type.
+
+**Table E.69 – XTN**
+
+| Name                                | Usage | DT  | Comment                                                                                                                                                                                                                          |
+|-------------------------------------|-------|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Telephone Number                    | X     | ST  |                                                                                                                                                                                                                                  |
+| Telecommunication Use Code          | R     | ID  | Code to denote the use of the number.<br>PCD-01 constrains this value to be either "PRN" for primary residence number or "NET" for network/email address                                                                         |
+| Telecommunication Equipment Type    | R     | ID  | Code to denote equipment type.<br>PCD-01 constrains this value to be either "PH" for telephone when XTN.2 is "PRN" or "Internet" for internet address when XTN.2 is "NET" or "X.400" for X.400 email address when XTN.2 is "NET" |
+| Communication Address               | RE    | ST  | When valued this would contain the email address                                                                                                                                                                                 |
+| Country Code                        | RE    | NM  | Contains the telephone country code                                                                                                                                                                                              |
+| Area/City Code                      | RE    | NM  | Contains the telephone area/city code                                                                                                                                                                                            |
+| Local Number                        | RE    | NM  | Contains the core phone number                                                                                                                                                                                                   |
+| Extension                           | RE    | NM  | Contains the contact extension                                                                                                                                                                                                   |
+| Any Text                            | RE    | ST  | Arbitrary comment text to accompany the phone number.<br>Example:<br>"do not call on weekends"                                                                                                                                   |
+| Extension Prefix                    | RE    | ST  | Contains codes used to establish call with a company's internal phone system                                                                                                                                                     |
+| Speed Dial Code                     | X     | ST  |                                                                                                                                                                                                                                  |
+| Unformatted Telephone Number        | X     | ST  |                                                                                                                                                                                                                                  |
+| Effective Start Date                | O     | DTM | Start date of the telecommunication number's validity.<br>Not typically used for Services interface                                                                                                                              |
+| Expiration Date                     | O     | DTM | End date of the telecommunication number's validity.<br>Not typically used for Services interface                                                                                                                                |
+| Expiration Reason                   | O     | CWE | Code to explain why number's validity ended. Not typically used for Services interface                                                                                                                                           |
+| Protection Code                     | O     | CWE | Code to indicate sensitivity of the contained number. Not typically used for Services interface                                                                                                                                  |
+| Shared Telecommunication Identifier | O     | EI  | This field allows a unique identifier to be assigned to the contained number so that it can be referenced. Not typically used for Services interface                                                                             |
+| Preference Order                    | O     | NM  | This field indicates the preferred order if there are multiple numbers specified. Not typically used for Services interface                                                                                                      |
+
+#### E.6.6.1 Examples
+
+```
+^PRN^PH^^^919^5554321
+^NET^Internet^bubba@boguscompany.com
+```
+
+## E.7 HL7 control characters
+
+Table E.70 shows the HL7 v2.6 delimiter values.
+
+**Table E.70 – HL7 v2.6 delimiter values**
+
+| Delimiter              | Suggested value | Encoding character position | Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|------------------------|-----------------|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Segment terminator     | <cr>            | –                           | Terminates a segment record. This value cannot be changed by implementers                                                                                                                                                                                                                                                                                                                                                                            |
+| Field separator        |                 | –                           | Separates two adjacent data fields within a segment. It also separates the segment ID from the first data field in each segment                                                                                                                                                                                                                                                                                                                      |
+| Component separator    | ^               | 1                           | Separates adjacent components of data fields where allowed                                                                                                                                                                                                                                                                                                                                                                                           |
+| Repetition separator   | ~               | 2                           | Separates multiple occurrences of a field where allowed                                                                                                                                                                                                                                                                                                                                                                                              |
+| Escape character       | \               | 3                           | Escape character for use with any field represented by an ST, TX or FT data type, or for use with the data (fourth) component of the ED data type. If no escape characters are used in a message, this character may be omitted. However, it must be present if subcomponents are used in the message. Best practice is to always include this character. For the Continua services transaction, this entry <b>shall</b> always be present in MSH-2. |
+| Subcomponent separator | &               | 4                           | Separates adjacent subcomponents of data fields where allowed. If there are no subcomponents, this character may be omitted. Best practice is to always include this character. For the Continua services transaction, this entry <b>shall</b> always be present in MSH-2.                                                                                                                                                                           |
+
+## **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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/H/T-REC-H.812.3-201711-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4d928399572e0fd7f3c160f179dcc0500d0db1ac
--- /dev/null
+++ b/marked/H/T-REC-H.812.3-201711-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7e9672d5a8d08713d19d79976b10e82a5b1ccd21aa94725a655815c391498d1c
+size 65882
diff --git a/marked/H/T-REC-H.812.3-201711-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg b/marked/H/T-REC-H.812.3-201711-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5caf5310aaae11627e370b6cc6202ded72ddaeb8
--- /dev/null
+++ b/marked/H/T-REC-H.812.3-201711-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9fbc98b6c52d67e15173f388ebb1e21e287b943f9a15d7b86d57b7a6891c0338
+size 84759
diff --git a/marked/H/T-REC-H.812.3-201711-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.812.3-201711-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3e8b3edb933c778e951f7381b66db05729e6dd83
--- /dev/null
+++ b/marked/H/T-REC-H.812.3-201711-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f3177ab19236cec92fd1395248c2901b389b007b6f1bb7f01b0905ac99648a93
+size 4146
diff --git a/marked/H/T-REC-H.812.4-201711-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.812.4-201711-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bd7c24e83d75a6b1baa7fb4210f76345166390c9
--- /dev/null
+++ b/marked/H/T-REC-H.812.4-201711-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5866ab521163bd4f911ae6e27d0a1cf1f491c665e9b87b7d7076098a143f4bff
+size 3944
diff --git a/marked/H/T-REC-H.812.4-201711-I_PDF-E/398674b42e3466add6d47f420c136494_img.jpg b/marked/H/T-REC-H.812.4-201711-I_PDF-E/398674b42e3466add6d47f420c136494_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1921014c3efe4640196068f07d90210e8df64520
--- /dev/null
+++ b/marked/H/T-REC-H.812.4-201711-I_PDF-E/398674b42e3466add6d47f420c136494_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bed2ce65e139fcf74974836a778c109b4d7e0f657b4ec0f0ef4f777fa89038ae
+size 53707
diff --git a/marked/H/T-REC-H.812.4-201711-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg b/marked/H/T-REC-H.812.4-201711-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1857da6adfd92d42f942d47a6d65d32791b05f33
--- /dev/null
+++ b/marked/H/T-REC-H.812.4-201711-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:70159285add42a89b0489e69c7d8f9712cc73c73a2333b4378bd8bc3f717caa0
+size 62932
diff --git a/marked/H/T-REC-H.812.4-201711-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/H/T-REC-H.812.4-201711-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dfdf78fdf767fc44397fa76f8f4184d57c6527cc
--- /dev/null
+++ b/marked/H/T-REC-H.812.4-201711-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:588fc8e6a59e5f32aa6b5fd43284c105678e8d23bf19e3cfeebbdb26f35d623f
+size 147927
diff --git a/marked/H/T-REC-H.812.4-201711-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/H/T-REC-H.812.4-201711-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..929455fada8c7797c986e717b617b72c0cb65802
--- /dev/null
+++ b/marked/H/T-REC-H.812.4-201711-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ccfdf14259df62cdad12940f16d02423977e017dbea93196b65ec79770c59b06
+size 134405
diff --git a/marked/H/T-REC-H.812.4-201711-I_PDF-E/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg b/marked/H/T-REC-H.812.4-201711-I_PDF-E/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e63635aad9db7f6aa64f4fd96893e77cad6a7741
--- /dev/null
+++ b/marked/H/T-REC-H.812.4-201711-I_PDF-E/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cb5a05798998f45cbe4c374ad8b00b14a8e40436e06bd07bbd76f91322da8550
+size 66024
diff --git a/marked/H/T-REC-H.812.4-201711-I_PDF-E/ea4fd10a9a501c602f2bea0f7f711877_img.jpg b/marked/H/T-REC-H.812.4-201711-I_PDF-E/ea4fd10a9a501c602f2bea0f7f711877_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..122b125ca5e75c4e7aa7146e42bad5dadecdbac2
--- /dev/null
+++ b/marked/H/T-REC-H.812.4-201711-I_PDF-E/ea4fd10a9a501c602f2bea0f7f711877_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aff8b1d773a16361d243f5c1f50b67dccc56c36f003e487ad39fef2f9a0f8f3f
+size 22058
diff --git a/marked/H/T-REC-H.821-201704-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/marked/H/T-REC-H.821-201704-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3bb1ac5456eb06ae520dc1e0d89c2a91ff977d53
--- /dev/null
+++ b/marked/H/T-REC-H.821-201704-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b65209e173214c44d4acddbd07b4f4c54e886783470c7ca028ab86ef065a87f4
+size 62539
diff --git a/marked/H/T-REC-H.821-201704-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg b/marked/H/T-REC-H.821-201704-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..319c0a9aa645e93852365d13ef4334b84e554e81
--- /dev/null
+++ b/marked/H/T-REC-H.821-201704-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0f7f5236a103d3bc93ad67dfa3c83662b3290f9dea71fb2942b169a5cf0abdb9
+size 27470
diff --git a/marked/H/T-REC-H.821-201704-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg b/marked/H/T-REC-H.821-201704-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2eed7be719f1b606d5645b5eaf5bbe996abeff01
--- /dev/null
+++ b/marked/H/T-REC-H.821-201704-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a0b84dbd18050be9b0d2200332082c104a4dabe3a651a18da42a0074384b0a66
+size 28886
diff --git a/marked/H/T-REC-H.821-201704-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg b/marked/H/T-REC-H.821-201704-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6079e90804d4d8b9f6f5c0ca5faa75a97ea9ec86
--- /dev/null
+++ b/marked/H/T-REC-H.821-201704-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:12e70c688a8cba12daa58bb7c0f81ce2a6d5c90eb685e97dd71a141574314a4a
+size 108067
diff --git a/marked/H/T-REC-H.821-201704-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/H/T-REC-H.821-201704-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4084e6512b20ee17a203163babbc9c1891bd6a24
--- /dev/null
+++ b/marked/H/T-REC-H.821-201704-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7afc110eb7cab3ab62c85f4a885d4a8c73d342742ad25357695789df9bd54ffd
+size 39248
diff --git a/marked/H/T-REC-H.821-201704-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/H/T-REC-H.821-201704-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cdafbf242204b1dbf144a50f7effe105b7888362
--- /dev/null
+++ b/marked/H/T-REC-H.821-201704-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8d7d21bcd46043fe808595f8351daeda8899df08c4e284fa3516f4fe64b1e737
+size 37916
diff --git a/marked/H/T-REC-H.821-201704-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/H/T-REC-H.821-201704-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c93017b56d60b6560c37dd01d1de259c00285cd4
--- /dev/null
+++ b/marked/H/T-REC-H.821-201704-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9a4a7c6dbbbce07ba75e70a8ffebed795744e27f0366bfb80c2c243ea781733a
+size 36939
diff --git a/marked/H/T-REC-H.821-201704-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg b/marked/H/T-REC-H.821-201704-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..601f265aff2341be9694ad8fccaf19e68dce1801
--- /dev/null
+++ b/marked/H/T-REC-H.821-201704-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8fd21de6f37eec4ce1bd89131b5f3db0571277e917231127b6fbcb85b873d0b1
+size 71794
diff --git a/marked/H/T-REC-H.821-201704-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/H/T-REC-H.821-201704-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3303fbcd1824a35646e0089209fe47aaddd0a8aa
--- /dev/null
+++ b/marked/H/T-REC-H.821-201704-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9ba2d4b41f40f6b7513b6ef14e60dc1d6462738aca6181e71a4fdac94baed85f
+size 28692
diff --git a/marked/H/T-REC-H.821-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg b/marked/H/T-REC-H.821-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a713c9d3a38a0b0ded423795a4e6fb9889f1cf7e
--- /dev/null
+++ b/marked/H/T-REC-H.821-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5ac2e2cf21c51a63df761924b63730e9562d1cb9210d5b37a96e62976d508279
+size 4125
diff --git a/marked/H/T-REC-H.821-201704-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg b/marked/H/T-REC-H.821-201704-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4e364bcc70ea91bca2182b3bb91c5766766cb04f
--- /dev/null
+++ b/marked/H/T-REC-H.821-201704-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1513e35bdc043a7b70b25e5bfe437ee9b3c63fb8ee3883075adc58e42108618e
+size 37394
diff --git a/marked/H/T-REC-H.821-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.821-201704-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..3c4afd6596246e6f25fe47ed345b90c38ca43e44
--- /dev/null
+++ b/marked/H/T-REC-H.821-201704-I_PDF-E/raw.md
@@ -0,0 +1,5622 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.821**
+
+(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: Healthcare information system interface**
+
+Recommendation ITU-T H.821
+
+# 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        |
+| <b>Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN)</b> | <b>H.820–H.859</b> |
+| 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.821
+
+# Conformance of ITU-T H.810 personal health system: Healthcare information system interface
+
+## Summary
+
+Recommendation ITU-T H.821 provides a test suite structure (TSS) and the test purposes (TP) for the healthcare information system (HIS) 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.821 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, HIS Interface (Version 1.6, 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.821    | 2014-10-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/12248">11.1002/1000/12248</a> |
+| 2.0     | ITU-T H.821    | 2016-07-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12920">11.1002/1000/12920</a> |
+| 3.0     | ITU-T H.821    | 2017-04-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/13200">11.1002/1000/13200</a> |
+
+## Keywords
+
+Conformance testing, Continua Design Guidelines, e-health, health record network interface, healthcare information system, ITU-T H.810.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                                                   | 4   |
+| 6     | Test suite structure (TSS) .....                                                                    | 5   |
+| 7     | Electronic attachment .....                                                                         | 6   |
+|       | Annex A Test purposes .....                                                                         | 7   |
+| A.1   | TP definition conventions.....                                                                      | 7   |
+| A.2   | Test purposes structure .....                                                                       | 7   |
+| A.3   | Group 1.1: HIS direct sender (XDR) message acquisition and validation (DSMA) .....                  | 14  |
+| A.4   | Group 1.2: HIS indirect sender (XDM) message acquisition and validation (ISMA) .....                | 16  |
+| A.5   | Group 1.3: HIS message syntactic validation (XSV) .....                                             | 18  |
+| A.6   | Group 1.4: HIS message body (PHM report) CDG CDA conformance (CCDA) .....                           | 19  |
+| A.7   | Group 1.5: HIS message body (PHM report) CDG CCD conformance (CCCD).....                            | 22  |
+| A.8   | Group 1.6: HIS message header (metadata) semantic validation (mapping with PHM report) (XMSV) ..... | 25  |
+| A.9   | Group 1.7: HIS adherence monitor validation (AM) .....                                              | 27  |
+| A.10  | Group 1.8: HIS ATNA validation (ATNA) .....                                                         | 27  |
+| A.11  | Group 1.9: HIS document digital signature validation (DSG) .....                                    | 32  |
+| A.12  | Group 1.10: HIS patient identification validation (PIX) .....                                       | 34  |
+| A.13  | Group 1.11: HIS consent management (CM) .....                                                       | 56  |
+|       | Annex B Testable item mapping, validation and XML schemas .....                                     | 85  |
+| B.1   | Testable item mapping validation between PHMR and metadata.....                                     | 85  |
+| B.1.1 | For TP/HIS/SEN/XSV/BV-000 .....                                                                     | 85  |
+| B.1.2 | For TP/HIS/SEN/XMSV/BV-000 .....                                                                    | 88  |
+| B.2   | Testable item syntactic validation by XSD (XML schema language) file .....                          | 98  |
+| B.2.1 | For TP/HIS/SEN/CCDA/BV-000 .....                                                                    | 98  |
+| B.3   | Testable item syntactic validation against XML reference document file .....                        | 100 |
+
+|       |                                                                                  |     |
+|-------|----------------------------------------------------------------------------------|-----|
+| B.3.1 | For TP/HIS/SEN/CCDA/BV-000 .....                                                 | 100 |
+| B.4   | Testable item syntactic and/or semantic validation by Schematron 1.5.....        | 106 |
+| B.4.1 | For TP/HIS/SEN/CCDA/BV-000 .....                                                 | 106 |
+| B.4.2 | For TP/HIS/SEN/CCCD/BV-000 .....                                                 | 121 |
+| B.4.3 | For TP/HIS/SEN/AM/BV-000.....                                                    | 139 |
+| B.4.4 | For TP/SEN/HIS/DSG/BV-000 .....                                                  | 140 |
+| B.5   | Schema for RFC 3881 verification.....                                            | 143 |
+| B.6   | Schema for XML advanced electronic signatures (XAdES).....                       | 149 |
+| B.7   | Schema for XML-signature syntax and processing (Xmldsig) .....                   | 158 |
+| B.8   | Testable item mapping validation between signature document and<br>metadata..... | 164 |
+|       | Bibliography.....                                                                | 171 |
+
+**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, HIS Interface (Version 1.6, 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 uses "TSS&TP_1.5_HRN_Sender_v1.1.doc" as a baseline and adds new features included in [b-CDG 2011]: <ul style="list-style-type: none"> <li>Digital signature, Patient ID and Consent management</li> </ul>                                                                                                                                    |
+| 1.2     | 2013-05-24 | Initial release for Test Tool DG2012. This is the same version as "TSS&TP_DG2011_HRN_Sender_v1.2.doc" because the Test Tool DG2012 scope did not include HRN enhancements                                                                                                                                                                                                              |
+| 1.2     | 2014-01-24 | Initial release for Test Tool DG2013. This is the same version as "TSS&TP_DG2012_HRN_Sender_v1.2.doc" because the new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013] did not include HRN enhancements.                                                                                                                                                                       |
+| 1.3     | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_HRN_Sender_v1.2.doc" as a baseline and adds new features included in Documentation Enhancements: <ul style="list-style-type: none"> <li>"Other PICS" row added</li> </ul>                                                                                                                    |
+| 1.4     | 2015-07-01 | Initial release for Test Tool DG2015. It uses "TSS&TP_DG2013_HRN_Sender_v1.3.doc" as a baseline and adds some fixes found in the documentation [b-ITU-T H.810 (2015)]/[b-CDG 2015]: <ul style="list-style-type: none"> <li>Section number has changed in the IETF RFC 3881. Now it is "Section 6" instead.</li> <li>Change from "Section 4" to "Annex B.5" for consistency.</li> </ul> |
+| 1.5     | 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.6     | 2017-03-14 | Minor editorial changes ( <i>Service</i> instead of <i>System</i> ).                                                                                                                                                                                                                                                                                                                   |
+
+
+
+# Recommendation ITU-T H.821
+
+# Conformance of ITU-T H.810 personal health system: Healthcare information system interface
+
+# 1 Scope
+
+The scope of this Recommendation<sup>1</sup> is to provide a test suite structure (TSS) and the test purposes (TP) for the healthcare information system (HIS) interface based on the requirements defined in [ITU-T H.813], which is part of the ITU-T H.810-series and is a transposition of the Continua Design Guidelines (CDG) [ITU-T H.810 (2016)]. The objective of this test specification is to provide a high probability of interoperability between different devices through the HIS interface to transfer patient information from a Health & Fitness Service (HIS sender) to a healthcare information system (HIS receiver).
+
+This Recommendation focuses only on the TSS and TP for the HIS sender because, at this moment, certification of the HIS receiver is out of the scope of the developed test tool.
+
+# 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.813] Recommendation ITU-T H.813 (2016), *Interoperability design guidelines for personal health systems: Healthcare information system (HIS) interface*.
+- [HL7 CDA IG] Health Level Seven (2011), *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\\_CONSENTDIR\\_DSTU\\_2011JAN.pdf](http://www.hl7.org/documentcenter/public/standards/dstu/CDAR2_IG%20_CONSENTDIR_DSTU_2011JAN.pdf)
+- [HL7 CDA-PHMR] Health Level Seven (2010), *HL7 Implementation Guide for CDA Release 2: Personal Healthcare Monitoring Report, DSTU Release 1.1*.  
+[http://www.hl7.org/documentcenter/public/standards/dstu/CDAR2\\_IG\\_PHMRTS\\_R1.1\\_DSTU\\_2010OCT.zip](http://www.hl7.org/documentcenter/public/standards/dstu/CDAR2_IG_PHMRTS_R1.1_DSTU_2010OCT.zip)
+- [IETF RFC 3195] IETF RFC 3195 (2001), *Reliable Delivery for syslog*.  
+<https://datatracker.ietf.org/doc/rfc3195>
+
+---
+
+<sup>1</sup> 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.
+
+- [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 ITF PIX PDQ] IHE ITF PIX PDQ (2010), *IHE IT Infrastructure, Technical Framework Supplement – Patient Identifier Cross-Reference HL7 V3 (PIXV3) and Patient Demographic Query HL7 V3 (PDQV3) – Trial Implementation*.  
+[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_ITI\\_Suppl\\_PIX\\_PDQ\\_HL7v3\\_Rev2-1\\_TI\\_2010-08-10.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_ITI_Suppl_PIX_PDQ_HL7v3_Rev2-1_TI_2010-08-10.pdf)
+- [IHE ITI-TF-1] IHE ITI TF 1 (2009), *IHE IT Infrastructure Technical Framework, Volume 1 (ITI TF-1): Integration Profiles, Revision 6.0*.  
+[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_ITI\\_TF\\_6-0\\_Vol1\\_FT\\_2009-08-10-2.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_6-0_Vol1_FT_2009-08-10-2.pdf)
+- [IHE ITI-TF-2] IHE ITI TF 2 (2009), *IHE IT Infrastructure Technical Framework, Volume 2 (ITI TF-2), Revision 6.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\\_6-0\\_Vol2a\\_FT\\_2009-08-10.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_6-0_Vol2a_FT_2009-08-10.pdf)  
+[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_ITI\\_TF\\_6-0\\_Vol2b\\_FT\\_2009-08-10.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_6-0_Vol2b_FT_2009-08-10.pdf)  
+[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_ITI\\_TF\\_6-0\\_Vol2x\\_FT\\_2009-08-10.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_6-0_Vol2x_FT_2009-08-10.pdf)
+- [IHE TFS XUA++] IHE TFS XUA++ (2010), *IHE IT Infrastructure (ITI), Technical Framework Supplement: Cross-Enterprise User Assertion - Attribute Extension (XUA++)*. Trial Implementation.  
+[http://www.ihe.net/Technical\\_Framework/upload/IHE\\_ITI\\_Suppl\\_XUA-\\_Rev1-1\\_TI\\_2010-08-10.pdf](http://www.ihe.net/Technical_Framework/upload/IHE_ITI_Suppl_XUA-_Rev1-1_TI_2010-08-10.pdf)
+- [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*.
+
+# 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:
+
+|      |                                     |
+|------|-------------------------------------|
+| AM   | Adherence Monitor                   |
+| ATNA | Audit Trail and Node Authentication |
+| ATS  | Abstract Test Suite                 |
+| CDA  | Clinical Document Architecture      |
+| CDG  | Continua Design Guidelines          |
+| CGM  | Continuous Glucose Monitor          |
+| DSG  | Digital Signature Validation        |
+
+|        |                                                       |
+|--------|-------------------------------------------------------|
+| DUT    | Device Under Test                                     |
+| ebXML  | electronic business using extensible Markup Language  |
+| EHR    | Electronic Health Record                              |
+| GUI    | Graphical User Interface                              |
+| HIS    | Healthcare Information System                         |
+| HFS    | Health & Fitness Service                              |
+| HFSS   | Health & Fitness Service Sender                       |
+| HFSR   | Health & Fitness Service Receiver                     |
+| HRN    | Health Record Network                                 |
+| HTTP   | Hypertext Transfer Protocol                           |
+| HTTPS  | Hypertext Transfer Protocol Secure                    |
+| INR    | International Normalized Ratio                        |
+| IP     | Insulin Pump                                          |
+| IUT    | Implementation Under Test                             |
+| MDS    | Medical Device System                                 |
+| MTOM   | Message Transmission Optimization Mechanism           |
+| NFC    | Near Field Communication                              |
+| NTP    | Network Time Protocol                                 |
+| PAN    | Personal Area Network                                 |
+| PCO    | Point of Control and Observation                      |
+| PCT    | Protocol Conformance Testing                          |
+| PHD    | Personal Health Device                                |
+| PHDC   | Personal Healthcare Device Class                      |
+| PHM    | Personal Healthcare Monitoring (report)               |
+| PHG    | Personal Health Gateway                               |
+| PHR    | Personal Healthcare Record                            |
+| PICS   | Protocol Implementation Conformance Statement         |
+| PIXIT  | Protocol Implementation extra Information for Testing |
+| PO     | Point of Observation                                  |
+| SABTE  | Sleep Apnoea Breathing Therapy Equipment              |
+| SCR    | Static Conformance Review                             |
+| S/MIME | Secure/Multipurpose Internet Mail Extensions          |
+| SMTP   | Simple Mail Transfer Protocol                         |
+| SOAP   | Simple Object Access Protocol                         |
+| SUT    | System Under Test                                     |
+| SSL    | Secure Socket Layer                                   |
+| TCWG   | Test and Certification Working Group                  |
+
+|       |                                                |
+|-------|------------------------------------------------|
+| TE    | Test Equipment                                 |
+| TI    | Testable Item                                  |
+| TLS   | Transport Level Security                       |
+| TP    | Test Purpose                                   |
+| TSS   | Test Suite Structure                           |
+| USB   | Universal Serial Bus                           |
+| XDM   | cross-enterprise Document Media interchange    |
+| XDR   | cross-enterprise Document Reliable interchange |
+| XDS   | cross-enterprise Document Sharing              |
+| XDS.b | cross-enterprise Document Sharing-b            |
+| XML   | extensible Markup Language                     |
+| XOP   | XML-binary Optimized Packaging                 |
+| XPath | XML Path language                              |
+| XSD   | XML Schema                                     |
+| WAN   | Wide Area Network                              |
+| WDM   | Windows Driver Model                           |
+| WS    | Web Service                                    |
+
+# 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 healthcare information system (HIS) interface are described in Annex A and have been divided into two main groups:
+
+- **Group 1:** HIS sender (SEN)
+  - **Group 1.1:** HIS direct sender (XDR) message acquisition and validation (DSMA)
+
+- **Group 1.2:** HIS indirect sender (XDM) message acquisition and validation (ISMA)
+- **Group 1.3:** HIS message syntactic validation (XSV)
+- **Group 1.4:** HIS message body (PHM report) CDG CDA conformance (CCDA)
+- **Group 1.5:** HIS message body (PHM report) CDG CCD conformance (CCCD)
+- **Group 1.6:** HIS message header (Metadata) semantic validation (mapping with PHM report) (XMSV)
+- **Group 1.7:** HIS adherence monitor validation (AM)
+- **Group 1.8:** HIS ATNA validation (ATNA)
+- **Group 1.9:** HIS document digital signature validation (DSG)
+- **Group 1.10:** HIS patient identification validation (PIX)
+- **Group 1.11:** HIS consent management (CM)
+
+– **Group 2:** HIS receiver (REC)
+
+NOTE – TPs for Group 2 are for further study.
+
+# 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 <http://handle.itu.int/11.1002/2000/12067>.
+
+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>/<DUT>/<GR>/<XX> – <NNN>). It is specified according to the naming convention defined below:
+  - Each test purpose identifier is introduced by the prefix "TP".
+  - <TT>: This is the test tool that will be used in the test case.
+    - HIS: Healthcare Information System
+  - <DUT>: This is the device under test.
+    - SEN: HIS sender
+    - REC: HIS receiver (not used because it is out of scope of the developed test tool)
+  - <GR>: This identifies a group of test cases.
+  - <XX>: This identifies the type of testing.
+    - BV: Valid behaviour test
+    - BI: Invalid behaviour test
+  - <NNN>: 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.
+- **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 Test purposes structure
+
+The HIS protocol is based on the interchange of a single but complex XML message from the HIS sender (Health & Fitness Service) to the HIS receiver (Healthcare Information System). The HIS test tool has to verify the sender mode of the protocol only, which includes the HTTP and SOAP (HIS direct sender) or SMTP and S/MIME (HIS indirect sender) communication and the syntax and
+
+semantics of the XML message transmitted from the HIS sender. Test cases defined to implement these verifications are described below:
+
+- **HIS direct sender (XDR) message acquisition and validation (DSMA):** This test case runs the HTTP/HTTPS server (configured with TLS and a key length of 128 bits) and the web service (WS) that is going to receive the XDR message from the HIS direct sender under test (XDR Transport). Once the HIS sender has sent the message and if it conforms with the HTTP/HTTPS and SOAP 1.2 protocols [b-SOAP 1.2], it will be received by the web server and stored in an internal structure that will be used by the subsequent XDR test cases. If there is an error with the communication, the test case timeout expires and it shows the HTTP/HTTPS server log which verifies that there has been a communication error or the received message is not conformant to minimal XML syntax requirements. This test case also runs the audit record repository server (configured with TLS) that is going to receive the audit record message from the HIS direct sender. Once the HIS sender has sent the audit record message and if it conforms with the RFC 3195 protocol it will be stored in a file that will be used in subsequent XDR test cases. In case of errors in the communication, the test case timeout expires and it shows the audit repository log. Figure A.1 shows message acquisition and HTTP and SOAP validation.
+
+![Diagram illustrating message acquisition and validation for XDR and Audit record messages from the HIS direct sender under test.](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg)
+
+The diagram shows the flow of two messages from the 'HIS direct sender under test' (yellow box) to the 'HIS test tool' (blue box). Inside the test tool, there are two servers: 'Web server' and 'Audit repository server', each represented by a gear icon. The 'XDR message with PHMR and metadata' is sent to the 'Web server', which responds with 'Validation OK' to a 'Stored message' box. The 'Audit record message' is sent to the 'Audit repository server', which also responds with 'Validation OK' to a 'Stored log message' box. Additionally, both servers send an 'Error report' to a central 'Validation ERROR' box. The diagram is labeled H.821(17)\_FA.1 at the bottom right.
+
+Diagram illustrating message acquisition and validation for XDR and Audit record messages from the HIS direct sender under test.
+
+**Figure A.1 – Message acquisition and HTTP and SOAP validation**
+
+- **HIS indirect sender (XDM) message acquisition and validation (ISMA):** This test case runs the SMTP mail server (configured with transport level security (TLS) and a key length of 128 bits) that is going to receive the XDM message from the HIS indirect sender (XDM transport) under test. Once the HIS sender under test has sent the message and if it conforms to the SMTP protocol and S/MIME standard, it will be received by the mail server and stored in an internal structure that will be used by the subsequent XDM test cases. If there is an error with the communication, the test case timeout expires and it shows the mail server log which verifies that there has been a communication error or that the received message is not conformant to minimal XML syntax requirements. This test case also runs the audit record repository server (configured with TLS) that is going to receive the audit record message from the HIS indirect sender. Once the HIS sender has sent the audit record message and if it conforms with the RFC 3195 protocol it will be stored in a file that will be used in subsequent test cases. In case of errors in the communication, the
+
+test case timeout expires and it shows the audit repository log. Figure A.2 shows message acquisition and SMTP and S/MIME validation.
+
+![Figure A.2: Message acquisition and SMTP and S/MIME validation diagram. The diagram shows two message flows. The first flow starts with an 'XDM message with PHMR and metadata' from the 'HIS indirect sender under test' (yellow box) to a 'Mail server' (gears icon), then to a 'Mail client' (gears icon), and finally to the 'HIS test tool' (grey box) with a 'Validation OK' result, leading to a 'Stored message' (note icon). The second flow starts with an 'Audit record message' from the 'HIS indirect sender under test' to an 'Audit repository server' (gears icon), then to an 'Error report' (green note icon) with a 'Validation ERROR' result, and finally to the 'HIS test tool' with a 'Validation OK' result, leading to a 'Stored audit record message' (note icon). The label 'H.821(17)_FA.2' is at the bottom right.](c85ded401105f62f2d6ff26b3b5eb4af_img.jpg)
+
+Figure A.2: Message acquisition and SMTP and S/MIME validation diagram. The diagram shows two message flows. The first flow starts with an 'XDM message with PHMR and metadata' from the 'HIS indirect sender under test' (yellow box) to a 'Mail server' (gears icon), then to a 'Mail client' (gears icon), and finally to the 'HIS test tool' (grey box) with a 'Validation OK' result, leading to a 'Stored message' (note icon). The second flow starts with an 'Audit record message' from the 'HIS indirect sender under test' to an 'Audit repository server' (gears icon), then to an 'Error report' (green note icon) with a 'Validation ERROR' result, and finally to the 'HIS test tool' with a 'Validation OK' result, leading to a 'Stored audit record message' (note icon). The label 'H.821(17)\_FA.2' is at the bottom right.
+
+**Figure A.2 – Message acquisition and SMTP and S/MIME validation**
+
+- **HIS message syntax validation (XSV):** The HIS message is based on the IHE XDS profile, and corresponds to the specific form of ebXML "Provide And Register Document Set-b Request" element. The syntax verification of the HIS message is based on the conformance with the XSD template that describes the XML format of the ebXML message. This verification is performed with an XSD validation, a one step verification that includes all testable items related to the syntax of the HIS message. Its result is an XSD error report that shows details about any syntax errors detected. In this test case, the personal healthcare monitoring (PHM) report document is seen as a codec document (base-64 codification) or as part of the MIME multipart message (binary) using the message transmission optimization mechanism (MTOM), so its syntax will not have been checked yet. Figure A.3 shows message syntax validation.
+
+![Figure A.3: Message syntax validation diagram. The diagram shows a 'Stored message' (note icon) being processed by an 'XSD validation' block (gears icon) within the 'HIS test tool' (grey box). The result is either 'Validation OK' (leading to a black circle) or 'Validation ERROR' (leading to an 'XSD error report' (green note icon)). The label 'H.821(17)_FA.3' is at the bottom right.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg)
+
+Figure A.3: Message syntax validation diagram. The diagram shows a 'Stored message' (note icon) being processed by an 'XSD validation' block (gears icon) within the 'HIS test tool' (grey box). The result is either 'Validation OK' (leading to a black circle) or 'Validation ERROR' (leading to an 'XSD error report' (green note icon)). The label 'H.821(17)\_FA.3' is at the bottom right.
+
+**Figure A.3 – Message syntax validation**
+
+- **Message body (PHM reports) CDG CDA (CCDA) validation:** This test case validates the syntax and semantics of the PHM report with the CDA format and CDG CDA constraints. It is done in two steps, the first using an XSD template and the second using Schematron validation [b-ISO/IEC 19757-3]. Syntax validation is performed using both steps due to the fact that some syntactic testable items might be out of scope of the XSD template, whereas semantic validation is performed using the Schematron template. Figure A.4 shows message body (PHM reports) CDG CDA validation.
+
+![Flowchart of Message body (PHM reports) CDG CDA validation process](ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg)
+
+The diagram illustrates the validation process for PHM reports using CDG CDA. It starts with a 'Stored message' box on the left. An arrow points to a box labeled 'XSD validation' containing three interlocking gears. From this box, an arrow points to another box labeled 'Schematron validation' also containing three interlocking gears. From the 'Schematron validation' box, an arrow points to a black circle labeled 'Validation OK'. A line also branches from the 'XSD validation' box down to a green box labeled 'Error report', with the label 'Validation ERROR' above the arrow. The entire process is enclosed in a blue rectangular frame with the text 'HIS test tool' in the top right corner. The identifier 'H.821(17)\_FA.4' is located at the bottom right of the frame.
+
+Flowchart of Message body (PHM reports) CDG CDA validation process
+
+**Figure A.4 – Message body (PHM reports) CDG CDA validation**
+
+- **Message body (PHM reports) CDG CCD validation (CCCD):** This test case validates the syntax and semantics of the PHM report with the CCD format and CDG CCD constraints. It is done in two steps, the first using an XML file and the second using Schematron validation. Syntax validation is performed using both steps due to the fact that some syntactic testable items might be out of scope of the XML file, whereas semantic validation is performed using the Schematron template. Figure A.5 shows message body (PHM reports) CDG CCD validation.
+
+![Flowchart of Message body (PHM reports) CDG CCD validation process](9b9d2abd741ed4bafe7f78f89961c663_img.jpg)
+
+The diagram illustrates the validation process for PHM reports using CDG CCD. It starts with a 'Stored message' box on the left. An arrow points to a box labeled 'Validation against an Xml file' containing three interlocking gears. From this box, an arrow points to another box labeled 'Schematron validation' also containing three interlocking gears. From the 'Schematron validation' box, an arrow points to a black circle labeled 'Validation OK'. A line also branches from the 'Validation against an Xml file' box down to a green box labeled 'Error report', with the label 'Validation ERROR' above the arrow. The entire process is enclosed in a blue rectangular frame with the text 'HIS test tool' in the top right corner. The identifier 'H.821(17)\_FA.5' is located at the bottom right of the frame.
+
+Flowchart of Message body (PHM reports) CDG CCD validation process
+
+**Figure A.5 – Message body (PHM reports) CDG CCD validation**
+
+- **Message header (metadata) semantic validation (XMSV) (Mapping with PHM reports):** The semantics test of the message metadata includes testable items related to the mapping of the metadata fields of the HIS message with the message body (PHM report) ones using XPath expressions. The errors detected with the mapping will be sent to the error report file. Figure A.6 shows message metadata semantic validation.
+
+![Figure A.6: Message metadata semantic validation flowchart. A 'Stored message' is input to a 'Header fields mapping' block (represented by gears). The 'HIS test tool' performs the validation. The output is either 'Validation OK' (leading to a black circle) or 'Validation ERROR' (leading to an 'Error report' box).](7f25db95ce3916c0e09803b861a2f7bc_img.jpg)
+
+```
+
+graph LR
+    subgraph HIS_test_tool [HIS test tool]
+        direction TB
+        HFM[Header fields mapping] -- "Validation OK" --> OK(( ))
+        HFM -- "Validation ERROR" --> ER[Error report]
+    end
+    SM[Stored message] --> HFM
+    style OK fill:black,stroke:none
+    style ER fill:#90EE90,stroke:none
+    style SM fill:#D3D3D3,stroke:none
+    style HFM fill:white,stroke:none
+  
+```
+
+H.821(17)\_FA.6
+
+Figure A.6: Message metadata semantic validation flowchart. A 'Stored message' is input to a 'Header fields mapping' block (represented by gears). The 'HIS test tool' performs the validation. The output is either 'Validation OK' (leading to a black circle) or 'Validation ERROR' (leading to an 'Error report' box).
+
+**Figure A.6 – Message metadata semantic validation**
+
+- **Medication adherence monitor CDG validation (AM):** This test case validates the syntax and semantics of the PHM report with the CDG constraints for medication adherence monitors. This is done using Schematron validation. Figure A.7 shows adherence monitor CDG validation.
+
+![Figure A.7: Adherence monitor CDG validation flowchart. A 'Stored message' is input to a 'Schematron validation' block (represented by gears). The 'HIS test tool' performs the validation. The output is either 'Validation OK' (leading to a black circle) or 'Validation ERROR' (leading to an 'Error report' box).](10781f43062bf3e9601a1e086710556c_img.jpg)
+
+```
+
+graph LR
+    subgraph HIS_test_tool [HIS test tool]
+        direction TB
+        SV[Schematron validation] -- "Validation OK" --> OK(( ))
+        SV -- "Validation ERROR" --> ER[Error report]
+    end
+    SM[Stored message] --> SV
+    style OK fill:black,stroke:none
+    style ER fill:#90EE90,stroke:none
+    style SM fill:#D3D3D3,stroke:none
+    style SV fill:white,stroke:none
+  
+```
+
+H.821(17)\_FA.7
+
+Figure A.7: Adherence monitor CDG validation flowchart. A 'Stored message' is input to a 'Schematron validation' block (represented by gears). The 'HIS test tool' performs the validation. The output is either 'Validation OK' (leading to a black circle) or 'Validation ERROR' (leading to an 'Error report' box).
+
+**Figure A.7 – Adherence monitor CDG validation**
+
+- **Audit trail and node authentication (ATNA) validation:** ATNA testing is performed using two different test cases applicable to both XDR and XDM communication.
+  - The first test case validates the syntax and semantics of the audit record received by the audit repository server during the message acquisition and validation (DSMA or ISMA). The syntactic validation is performed using an XSD template and the semantic validation is performed using Schematron validation. Figure A.8 shows ATNA message validation.
+
+![Flowchart of ATNA message validation process. A 'Stored audit record message' is processed through 'XSD validation' and 'Schematron validation' using the 'HIS test tool'. If 'Validation OK', it ends. If 'Validation ERROR', an 'Error report' is generated.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg)
+
+```
+
+graph LR
+    A[Stored audit record message] --> B[XSD validation]
+    B --> C[Schematron validation]
+    C --> D[Validation OK]
+    D --> E(( ))
+    B --> F[Validation ERROR]
+    F --> G[Error report]
+  
+```
+
+H.821(17)\_FA.8
+
+Flowchart of ATNA message validation process. A 'Stored audit record message' is processed through 'XSD validation' and 'Schematron validation' using the 'HIS test tool'. If 'Validation OK', it ends. If 'Validation ERROR', an 'Error report' is generated.
+
+**Figure A.8 – ATNA message validation**
+
+- The second test case checks the behaviour of the audit record sender when the audit record receiver is not ready to receive the audit message. In this case, the audit record sender must store the audit record message and send it when the audit record receiver is available. Figure A.9 shows audit record sender error verification.
+
+![Flowchart of audit record sender error verification. It starts with 'XDR/XDM message ready to be sent', followed by 'XDR/XDS message sent'. A decision 'Audit repository connected?' leads to 'Store audit record' if No, or 'All pending audit records have been received?' if Yes. If No to the second decision, an 'Error report' is generated. If Yes, it leads to 'Pass verdict'. A feedback loop exists from 'Store audit record' back to the start.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg)
+
+```
+
+graph TD
+    A([XDR/XDM message ready to be sent]) --> B[XDR/XDS message sent]
+    B --> C{Audit repository connected?}
+    C -- No --> D[Store audit record]
+    D --> A
+    C -- Yes --> E{All pending audit records have been received?}
+    E -- No --> F[Error report]
+    E -- Yes --> G([Pass verdict])
+  
+```
+
+H.821(17)\_FA.9
+
+Flowchart of audit record sender error verification. It starts with 'XDR/XDM message ready to be sent', followed by 'XDR/XDS message sent'. A decision 'Audit repository connected?' leads to 'Store audit record' if No, or 'All pending audit records have been received?' if Yes. If No to the second decision, an 'Error report' is generated. If Yes, it leads to 'Pass verdict'. A feedback loop exists from 'Store audit record' back to the start.
+
+**Figure A.9 – Audit record sender error verification**
+
+– **HIS document digital signature validation (DSG) syntax and semantics:** This test case validates the syntax and semantics of the digital signature document, as well as validating the signature of the PHM report. In order to do so, the test case enables the simulated HIS receiver to receive the XDS message and to extract both the PHM report and the digital signature document. The test case also checks the syntax and the semantics of the DSG document using an XSD schema and Schematron validation. Finally the test tool uses the PHM report and the DSG document to verify the signature. Figure A.10 shows document digital signature validation (DSG) syntax and semantics.
+
+![Sequence diagram illustrating the HIS document digital signature validation (DSG) syntax and semantics process. The diagram shows interactions between a Non repudiation enable HIS sender under test, a Web server, an Audit repository server, and an HIS test tool. The process involves receiving XDR and Audit record messages, validating them, storing them, and then performing XSD, Schematron, and Signature validation on the extracted DSG document and PHM report.](812e188283162af0b54fb3e30ffee51b_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Sender as Non repudiation enable HIS sender under test
+    participant WebServer as Web server
+    participant AuditServer as Audit repository server
+    participant HISTool as HIS test tool
+
+    Note left of Sender: XDR message with PHMR, DSG and metadata
+    Sender->>WebServer: XDR message
+    WebServer-->>HISTool: Validation OK
+    WebServer-->>AuditServer: 
+    Note left of Sender: Audit record message
+    Sender->>AuditServer: Audit record message
+    AuditServer-->>HISTool: Validation OK
+    AuditServer-->>ErrorReport1: Validation ERROR
+    AuditServer-->>StoredLog: Stored log message
+
+    Note right of HISTool: Stored XDR message
+    Note right of HISTool: Digital signature document
+    Note right of HISTool: PHM report
+
+    Note right of HISTool: XSD validation
+    Note right of HISTool: Schematron validation
+    Note right of HISTool: Signature validation
+
+    StoredXDR[Stored XDR message]-->>XSDVal[XSD validation]
+    StoredXDR-->>SchematronVal[Schematron validation]
+    StoredXDR-->>SignatureVal[Signature validation]
+
+    PHMReport[PHM report]-->>SignatureVal
+    DSGDoc[Digital signature document]-->>SignatureVal
+
+    XSDVal-->>SchematronVal
+    SchematronVal-->>SignatureVal
+
+    XSDVal-->>ErrorReport2: Validation ERROR
+    SchematronVal-->>ErrorReport2
+    SignatureVal-->>FinalOK: Validation OK
+  
+```
+
+The diagram illustrates the flow of data and validation steps. On the left, the 'Non repudiation enable HIS sender under test' sends an 'XDR message with PHMR, DSG and metadata' to the 'Web server' and an 'Audit record message' to the 'Audit repository server'. The 'Web server' sends a 'Validation OK' message to the 'HIS test tool'. The 'Audit repository server' sends a 'Validation OK' message to the 'HIS test tool', an 'Error report' (Validation ERROR), and a 'Stored log message'. The 'HIS test tool' stores the 'XDR message', extracts the 'Digital signature document' and 'PHM report', and performs 'XSD validation', 'Schematron validation', and 'Signature validation'. The 'XSD validation' and 'Schematron validation' steps are sequential, with the 'XSD validation' outputting a 'Validation ERROR' to an 'Error report'. The 'Signature validation' step receives inputs from the 'XSD validation', 'Schematron validation', 'PHM report', and 'Digital signature document', and outputs a 'Validation OK' result.
+
+Sequence diagram illustrating the HIS document digital signature validation (DSG) syntax and semantics process. The diagram shows interactions between a Non repudiation enable HIS sender under test, a Web server, an Audit repository server, and an HIS test tool. The process involves receiving XDR and Audit record messages, validating them, storing them, and then performing XSD, Schematron, and Signature validation on the extracted DSG document and PHM report.
+
+H.821(17)\_FA.10
+
+Figure A.10 – Document digital signature validation (DSG) syntax and semantics
+
+### A.3 Group 1.1: HIS direct sender (XDR) message acquisition and validation (DSMA)
+
+|                      |                                                                                                                                                                                                                                                 |                 |
+|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|
+| <b>TP Id</b>         | TP/HIS/SEN/DSMA/BV-000                                                                                                                                                                                                                          |                 |
+| <b>TP label</b>      | HIS Direct Sender (XDR) Message Acquisition and Validation                                                                                                                                                                                      |                 |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                     | [ITU-T H.813]   |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                           | RDC_XDR-2; M    |
+|                      |                                                                                                                                                                                                                                                 | RDC_XDR-3; M    |
+|                      |                                                                                                                                                                                                                                                 | RDC_XDR-5; M    |
+|                      |                                                                                                                                                                                                                                                 | RDC_XDR-7; M    |
+|                      |                                                                                                                                                                                                                                                 | MGDC_XDR-3; M   |
+|                      |                                                                                                                                                                                                                                                 | MGDC_XDR-5; M   |
+|                      |                                                                                                                                                                                                                                                 | GenSDC_XDR-1; M |
+|                      |                                                                                                                                                                                                                                                 | GenSDC_XDR-2; M |
+|                      |                                                                                                                                                                                                                                                 | GenSDC_XDR-4; R |
+|                      | <b>Spec</b>                                                                                                                                                                                                                                     | [HE ITI-TF-1]   |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                           | XDSMD-1; M      |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-4; O      |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-17; M     |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-18; M     |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-20; M     |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-23; M     |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-24; M     |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-25; M     |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-26; M     |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-27; M     |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-30; M     |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-32; M     |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-33; M     |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-34; M     |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-35; M     |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-36; M     |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-37; M     |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-40; C     |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-41; M     |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-42; R     |
+|                      |                                                                                                                                                                                                                                                 | XDSMD-44; M     |
+|                      |                                                                                                                                                                                                                                                 | AuditTT-1       |
+|                      |                                                                                                                                                                                                                                                 | Audit_RT-2      |
+|                      |                                                                                                                                                                                                                                                 | ChainTrust-3    |
+|                      |                                                                                                                                                                                                                                                 | Audit_RT-3      |
+|                      |                                                                                                                                                                                                                                                 | OtherCert-2     |
+|                      |                                                                                                                                                                                                                                                 | Rel_Syslog-1    |
+|                      |                                                                                                                                                                                                                                                 | HTTP_Conn-1     |
+|                      |                                                                                                                                                                                                                                                 | Rel_Syslog-2    |
+|                      |                                                                                                                                                                                                                                                 | HTTP_Conn-2     |
+| <b>Test purpose</b>  | Check that:<br>HIS message is received from the SUT and it is conformant to the HTTPS and SOAP protocols<br>[AND]<br>Is conformant to minimal XML requirements<br>[AND]<br>Audit Record message is conformant to minimal transport requirements |                 |
+| <b>Applicability</b> | C_HRN_SEN_000 AND C_HRN_SEN_001                                                                                                                                                                                                                 |                 |
+| <b>Other PICS</b>    |                                                                                                                                                                                                                                                 |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b>  | The SUT is ready to send the message to the test equipment (TE)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated HIS receiver (test tool) initiates the server applications and the web service (as an XDR receiver) which will receive the HIS message from the HIS direct sender under test during a specific time.</li> <li>2. The simulated HIS receiver (test tool) initiates the audit repository that will receive the ATNA message.</li> <li>3. The simulated HIS receiver (test tool) sends a public certificate to the HIS direct sender under test and it has to accept it.</li> <li>4. The audit repository of the simulated HIS receiver (test tool) sends a public certificate to the secure application with the following characteristics: <ol style="list-style-type: none"> <li>a. X509 certificate</li> <li>b. based on RSA key</li> <li>c. key length in the range of 1024-4096.</li> </ol> </li> <li>5. The HIS direct sender under test sends an XDR message to the simulated HIS receiver (test tool) which receives the message and verifies that it conforms to HTTP/HTTPS and SOAP 1.2 protocols; if TLS is used, the encryption suite should be TLS_RSA_WITH_AES_128_CBC_SHA.</li> <li>6. The MIME header for this metadata part shall be set to text/xml</li> <li>7. Attributes that shall be present in the SOAP envelope: <ol style="list-style-type: none"> <li>a. @eb:id</li> <li>b. @xlink:href</li> <li>c. @xlink:role=http://www.ihe.net/roles/iti/xds/SubmitObjectsRequest</li> <li>d. eb:Schema:@eb:location=http://www.ihe.net/schemas/iti/xds/SubmitObjectsRequest<br/>eb:version=1.0.</li> </ol> </li> <li>8. The registry metadata in an XML file containing the SubmitObjectsRequest shall be inside the payload of the SOAP message.</li> <li>9. Check that if the message contains a "multipart document": <ol style="list-style-type: none"> <li>a. The multipart packaging transmits the MIME-type of each part.</li> <li>b. Each part containing a document has associated with it a document ID that is unique within the scope of this message.</li> <li>c. Each part shall contain a Content-Location header set to the name of "start" part file preceded by the name of the "sub-directory" where to save the part.</li> </ol> </li> <li>10. The HIS direct sender under test sends an audit record message to the audit repository.</li> <li>11. The audit repository receives the audit record message and verifies that: <ol style="list-style-type: none"> <li>a. TLS is used and the encryption suite is TLS_RSA_WITH_AES_128_CBC_SHA.</li> <li>b. It conforms to a reliable syslog's COOKED profile ([IETF RFC 3195]).</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The received HIS message conforms to the HTTP/HTTPS and SOAP 1.2 protocols and conforms to the minimal XML requirements (i.e. it contains a well-formed XML document with the PHM report attachment).</li> <li>• Checked values are as detailed in steps 5 to 9.</li> <li>• In step 4, the HIS sender under test must accept the public certificate.</li> <li>• The received audit message conforms to Reliable Syslog ([IETF RFC 3195]) and complies with the values detailed in step 11.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              | The test tool stores the received XDR message and audit record message in internal files that will be used by the subsequent test cases.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+### A.4 Group 1.2: HIS indirect sender (XDM) message acquisition and validation (ISMA)
+
+|                 |                                                                     |                   |
+|-----------------|---------------------------------------------------------------------|-------------------|
+| <b>TP Id</b>    | TP/HIS/SEN/ISMA/BV-000                                              |                   |
+| <b>TP label</b> | HIS indirect sender (XDM) Message Acquisition and Validation (ISMA) |                   |
+| <b>Coverage</b> | <b>Spec</b>                                                         | [ITU-T H.813]     |
+|                 | <b>Testable items</b>                                               | RIC_XDM-2; M      |
+|                 |                                                                     | RIC_XDM-3; R      |
+|                 |                                                                     | RIC_XDM-4; O      |
+|                 |                                                                     | MGIC_XDM-18; M    |
+|                 |                                                                     | RIC_XDM-5; M      |
+|                 |                                                                     | RIC_XDM-6; M      |
+|                 |                                                                     | MGIC_XDM-1; M     |
+|                 |                                                                     | MGIC_XDM-2; M     |
+|                 |                                                                     | MGIC_XDM-3; M     |
+|                 |                                                                     | MGIC_XDM-4; M     |
+|                 |                                                                     | MGIC_XDM-5; M     |
+|                 |                                                                     | MGIC_XDM-6; M     |
+|                 |                                                                     | MGIC_XDM-7; M     |
+|                 |                                                                     | MGIC_XDM-8; M     |
+|                 |                                                                     | MGIC_XDM-9; M     |
+|                 |                                                                     | MGIC_XDM-10; M    |
+|                 |                                                                     | MGIC_XDM-11; M    |
+|                 |                                                                     | MGIC_XDM-12; M    |
+|                 |                                                                     | MGIC_XDM-13; M    |
+|                 |                                                                     | MGIC_XDM-14; M    |
+|                 |                                                                     | MGIC_XDM-16; R    |
+|                 |                                                                     | MGIC_XDM-17; R    |
+|                 |                                                                     | GenSIC_XDM-1; M   |
+|                 |                                                                     | GenSIC_XDM-2; M   |
+|                 |                                                                     | GenO_XDM-2; R     |
+|                 | <b>Spec</b>                                                         | [IHE ITI-TF-1]    |
+|                 | <b>Testable items</b>                                               | ActTrans_XDM-1; M |
+|                 |                                                                     | ZIPOverEma-1; C   |
+|                 |                                                                     | MediaCont-1; O    |
+|                 |                                                                     | MessS_XDM-2; M    |
+|                 |                                                                     | MessS_XDM-3; O    |
+|                 |                                                                     | MedF_XDM-3; M     |
+|                 |                                                                     | MedF_XDM-4; M     |
+|                 |                                                                     | ContOverw-1; M    |
+|                 |                                                                     | ContOverw-2; M    |
+|                 |                                                                     | ContOverw-3; M    |
+|                 |                                                                     | ContOverw-5; M    |
+|                 |                                                                     | ContOverw-6; M    |
+|                 |                                                                     | ContOverw-7; M    |
+|                 |                                                                     | ContOverw-8; M    |
+|                 |                                                                     | ContOverw-9; O    |
+|                 |                                                                     | ContOverw-10; M   |
+|                 |                                                                     | ContOverw-11; M   |
+|                 |                                                                     | ContOverw12; M    |
+|                 |                                                                     | ContOverw-13; O   |
+|                 |                                                                     | ContOverw-14; M   |
+|                 |                                                                     | ContOverw-15; M   |
+|                 |                                                                     | ContOverw-16; M   |
+|                 |                                                                     | ContOverw-17; O   |
+|                 |                                                                     | ContOverw-18; M   |
+|                 |                                                                     | ContOverw-19; M   |
+|                 |                                                                     | ContOverw-20; M   |
+|                 |                                                                     | ContOverw-21 M    |
+|                 |                                                                     | ContOverw-22; R   |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|
+|                          | ContOverw-23; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ContOverw-24; O  |
+|                          | ContOverw-25; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ContOverw-26; M  |
+|                          | ContOverw-27; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ContOverw-28; M  |
+|                          | ContOverw-29; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ContOverw-30; M  |
+|                          | RespMsg_XDM-1; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | RespMsg_XDM-2; R |
+|                          | MedialD-2; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | MedialD-4; M     |
+|                          | MedialD-5; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | MedialD-6; R     |
+|                          | BasicPat-1; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | BasicPat-2; C    |
+|                          | BasicPat-3; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | BasicPat-4; C    |
+|                          | BasicPat-5; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | BasicPat-6; C    |
+|                          | BasicPat-7; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | BasicPat-8; C    |
+|                          | SecConsider-2; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | SecConsider-3; M |
+|                          | SecConsider-4; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | AuditTTT-1       |
+|                          | Audit_RT-2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | ChainTrust-3     |
+|                          | Audit_RT-3                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | OtherCert-2      |
+|                          | Rel_Syslog-1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | HTTP_Conn-1      |
+|                          | Rel_Syslog-2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | HTTP_Conn-2      |
+| <b>Test purpose</b>      | Check that:<br>HIS message is received from the SUT and it is conformant to the XDM specifications<br>[AND]<br>Audit Record message is conformant to minimal transport requirements                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                  |
+| <b>Applicability</b>     | C_HRN_SEN_000 AND C_HRN_SEN_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                  |
+| <b>Initial condition</b> | The SUT is ready to send an email containing a ZIP file to the test tool.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated HIS receiver (test tool) initiates the SMTP client that will receive the XDM message from the HIS sender under test during a specific time.</li> <li>2. The simulated HIS receiver (test tool) initiates the audit repository that will receive the ATNA message.</li> <li>3. The audit repository of the simulated HIS receiver (test tool) will send a public certificate to the secure application with the following characteristics and it has to be accepted: <ol style="list-style-type: none"> <li>a. X509 certificate</li> <li>b. based on RSA key</li> <li>c. key length in the range of 1024-4096.</li> </ol> </li> <li>4. The HIS indirect sender under test sends an XDM message to the simulated HIS indirect receiver (test tool).</li> <li>5. The HIS indirect receiver (test tool) receives the message and verifies that it conforms to SMTP and S/MIME protocols.</li> <li>6. Check within the email subject:</li> </ol> |                  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ol style="list-style-type: none"> <li>a. Email subject shall start with XDM/1.0/DDM.</li> <li>b. It is recommended to add the document ID (within the subject).</li> </ol> <ol style="list-style-type: none"> <li>7. Check within the email attachments: <ol style="list-style-type: none"> <li>a. The email message shall contain a ZIP file.</li> </ol> </li> <li>8. The ZIP's contents are extracted and the resulting structure is checked: <ol style="list-style-type: none"> <li>a. files "README.TXT" and "INDEX.HTM" and the folder "IHE_XDM" are in the root directory level;</li> <li>b. the "IHE_XDM" folder shall contain only one subfolder named "SUBSET01";</li> <li>c. file "METADATA.XML" exists;</li> <li>d. "METADATA.XML" file has to contain a "URI" element referencing the location of the PHM report file;</li> <li>e. The PHM file is located in the specified element of the METADATA.XML;</li> <li>f. executable files (.exe, .msi, .bat, .com) are not allowed.</li> </ol> </li> <li>9. The test tool stores the documents in an internal structure (i.e. file) that will be used by the subsequent test cases.</li> <li>10. The HIS direct sender under test sends an audit record message to the audit repository.</li> <li>11. The audit repository receives the audit record message and verifies: <ol style="list-style-type: none"> <li>a. TLS is used and the encryption suite is TLS_RSA_WITH_AES_128_CBC_SHA.</li> <li>b. It conforms to a reliable syslog's COOKED profile ([IETF RFC 3195]).</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• Email must conform to steps 3 to 5.</li> <li>• Attached zip file must be conformant to step 6.</li> <li>• The received audit message conforms to Reliable Syslog ([IETF RFC 3195])</li> <li>• Checked values are as detailed in steps 3 and 11.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              | The test tool stores the received XDM message and audit record message in internal files that will be used by the subsequent test cases.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+### A.5 Group 1.3: HIS message syntactic validation (XSV)
+
+|                 |                                  |               |               |
+|-----------------|----------------------------------|---------------|---------------|
+| <b>TP Id</b>    | TP/HIS/SEN/XSV/BV-000            |               |               |
+| <b>TP label</b> | HIS Message Syntactic Validation |               |               |
+| <b>Coverage</b> | <b>Spec</b>                      | [ITU-T H.813] |               |
+|                 | <b>Testable items</b>            | GenDFG 2; M   | GenDFG 3; M   |
+|                 |                                  | GenDFG 4; M   | GenDFG 5; M   |
+|                 |                                  | GenDFG 6; M   | GenDFG 7; R   |
+|                 |                                  | GenDFG 8; M   | XDSSSMD-1; O  |
+|                 |                                  | XDSSSMD-8; M  | XDSSSMD-12; M |
+|                 |                                  | XDSSSMD-13; M | XDSDEMD-7; M  |
+|                 |                                  | XDSDEMD-13; M | XDSDEMD-18; M |
+|                 |                                  | XDSDEMD-19; M | XDSDEMD-29; M |
+|                 |                                  | XDSDEMD-30; M | XDSDEMD-33; M |
+|                 |                                  | XDSDEMD-41; M | XDSDEMD-42; M |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                |             |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-------------|--|
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | XDSDEMD-43; M  |             |  |
+|                           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [IHE ITI-TF-1] |             |  |
+| <b>Testable items</b>     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | XDSMD-6; O     | XDSMD-28; M |  |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | XDSMD-29; M    |             |  |
+| <b>Test purpose</b>       | Check that:<br>HIS message syntax is based on the conformance with the XDS profile and SNOMED specifications.                                                                                                                                                                                                                                                                                                                                                              |                |             |  |
+| <b>Applicability</b>      | C_HRN_SEN_000                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                |             |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                |             |  |
+| <b>Initial condition</b>  | HIS message has been received and saved as an XML file in the test tool.                                                                                                                                                                                                                                                                                                                                                                                                   |                |             |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The test tool checks the mapping of the metadata fields with the message body of the structure received (stored in the test tool during the execution of test case TP/HIS/SEN/DSMA/BV-000) from HIS direct senders OR (stored in the test tool during the execution of TP/HIS/SEN/ISMA/BV-000) from HIS indirect senders under test using XPath.</li> <li>Details of the XPath constraints can be found in clause B.1.1.</li> </ol> |                |             |  |
+| <b>Pass/Fail criteria</b> | The received HIS message conforms to the XSD template that describes the XML format structure. This implies that all mandatory elements shall be present, that all recommended elements should be present and that optional elements may be present.                                                                                                                                                                                                                       |                |             |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                |             |  |
+
+### A.6 Group 1.4: HIS message body (PHM report) CDG CDA conformance (CCDA)
+
+|                 |                                                   |                 |                 |
+|-----------------|---------------------------------------------------|-----------------|-----------------|
+| <b>TP Id</b>    | TP/HIS/SEN/CCDA/BV-000                            |                 |                 |
+| <b>TP label</b> | HIS Message Body (PHM Report) CDG CDA Conformance |                 |                 |
+| <b>Coverage</b> | <b>Spec</b>                                       | [HL7 CDA-PHMR]  |                 |
+|                 | <b>Testable items</b>                             | CONF-PHMR-1; M  | CONF-PHMR-2; M  |
+|                 |                                                   | CONF-PHMR-3; M  | CONF-PHMR-4; M  |
+|                 |                                                   | CONF-PHMR-5; R  | CONF-PHMR-6; R  |
+|                 |                                                   | CONF-PHMR-7; M  | CONF-PHMR-8; M  |
+|                 |                                                   | CONF-PHMR-9; M  | CONF-PHMR-10; M |
+|                 |                                                   | CONF-PHMR-11; M | CONF-PHMR-12; M |
+|                 |                                                   | CONF-PHMR-13; M | CONF-PHMR-14; M |
+|                 |                                                   | CONF-PHMR-15; M | CONF-PHMR-16; R |
+|                 |                                                   | CONF-PHMR-17; M | CONF-PHMR-18; M |
+|                 |                                                   | CONF-PHMR-19; M | CONF-PHMR-20; M |
+|                 |                                                   | CONF-PHMR-21; M | CONF-PHMR-22; M |
+|                 |                                                   | CONF-PHMR-23; M | CONF-PHMR-24; M |
+
+|  |  |                 |                 |
+|--|--|-----------------|-----------------|
+|  |  | CONF-PHMR-25; M | CONF-PHMR-26; M |
+|  |  | CONF-PHMR-27; R | CONF-PHMR-28; O |
+|  |  | CONF-PHMR-29; M | CONF-PHMR-30; M |
+|  |  | CONF-PHMR-31; M | CONF-PHMR-32; R |
+|  |  | CONF-PHMR-33; M | CONF-PHMR-34; O |
+|  |  | CONF-PHMR-35; O | CONF-PHMR-36; M |
+|  |  | CONF-PHMR-37; M | CONF-PHMR-38; M |
+|  |  | CONF-PHMR-39; M | CONF-PHMR-40; M |
+|  |  | CONF-PHMR-41; M | CONF-PHMR-42; M |
+|  |  | CONF-PHMR-43; M | CONF-PHMR-44; M |
+|  |  | CONF-PHMR-45; M | CONF-PHMR-46; M |
+|  |  | CONF-PHMR-47; M | CONF-PHMR-48; M |
+|  |  | CONF-PHMR-49; M | CONF-PHMR-50; R |
+|  |  | CONF-PHMR-51; M | CONF-PHMR-52; M |
+|  |  | CONF-PHMR-53; R | CONF-PHMR-54; M |
+|  |  | CONF-PHMR-55; O | CONF-PHMR-56; C |
+|  |  | CONF-PHMR-57; M | CONF-PHMR-58; R |
+|  |  | CONF-PHMR-59; O | CONF-PHMR-60; M |
+|  |  | CONF-PHMR-61; C | CONF-PHMR-62; C |
+|  |  | CONF-PHMR-63; C | CONF-PHMR-64; R |
+|  |  | CONF-PHMR-65; R | CONF-PHMR-66; M |
+|  |  | CONF-PHMR-67; R | CONF-PHMR-68; R |
+|  |  | CONF-PHMR-69; M | CONF-PHMR-70; M |
+|  |  | CONF-PHMR-72; O | CONF-PHMR-71; M |
+|  |  | CONF-PHMR-74; O | CONF-PHMR-73; O |
+|  |  | CONF-PHMR-76; M | CONF-PHMR-75; O |
+|  |  | CONF-PHMR-78; M | CONF-PHMR-77; M |
+|  |  | CONF-PHMR-80; M | CONF-PHMR-79; O |
+|  |  | CONF-PHMR-82; R | CONF-PHMR-81; M |
+|  |  | CONF-PHMR-84; M | CONF-PHMR-83; M |
+|  |  | CONF-PHMR-86; M | CONF-PHMR-85; M |
+|  |  | CONF-PHMR-88; M | CONF-PHMR-87; M |
+
+|                          |                                                                                                                                                                                     |                              |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|
+|                          | CONF-PHMR-90; M                                                                                                                                                                     | CONF-PHMR-89; M              |
+|                          | CONF-PHMR-92; M                                                                                                                                                                     | CONF-PHMR-91; M              |
+|                          | CONF-PHMR-94; M                                                                                                                                                                     | CONF-PHMR-93; M              |
+|                          | CONF-PHMR-96; M                                                                                                                                                                     | CONF-PHMR-95; M              |
+|                          | CONF-PHMR-98; M                                                                                                                                                                     | CONF-PHMR-97; M              |
+|                          | CONF-PHMR-100; M                                                                                                                                                                    | CONF-PHMR-99; M              |
+|                          | CONF-PHMR-102; M                                                                                                                                                                    | CONF-PHMR-101; M             |
+|                          | CONF-PHMR-104; M                                                                                                                                                                    | CONF-PHMR-103; M             |
+|                          | CONF-PHMR-106; M                                                                                                                                                                    | CONF-PHMR-105; M             |
+|                          | CONF-PHMR-108; M                                                                                                                                                                    | CONF-PHMR-107; R             |
+|                          | CONF-PHMR-110; M                                                                                                                                                                    | CONF-PHMR-109; M             |
+|                          | CONF-PHMR-112; R                                                                                                                                                                    | CONF-PHMR-111; M             |
+|                          | CONF-PHMR-114; R                                                                                                                                                                    | CONF-PHMR-113; R             |
+|                          | CONF-PHMR-116; M                                                                                                                                                                    | CONF-PHMR-115; M             |
+|                          | CONF-PHMR-118; M                                                                                                                                                                    | CONF-PHMR-117; M             |
+|                          | CONF-PHMR-120; M                                                                                                                                                                    | CONF-PHMR-119; M             |
+|                          | CONF-PHMR-122; M                                                                                                                                                                    | CONF-PHMR-121; M             |
+|                          | CONF-PHMR-124; C                                                                                                                                                                    | CONF-PHMR-123; M             |
+|                          | CONF-PHMR-126; M                                                                                                                                                                    | CONF-PHMR-125; M             |
+|                          | CONF-PHMR-128; M                                                                                                                                                                    | CONF-PHMR-127; M             |
+|                          | CONF-PHMR-130; C                                                                                                                                                                    | CONF-PHMR-129; R             |
+|                          | GenDF-3; M                                                                                                                                                                          | GenDF-4; M                   |
+|                          | GenDF-5; M                                                                                                                                                                          | GenDF-7; O                   |
+|                          | CONF-PHMR-133; M                                                                                                                                                                    | CONF-PHMR-134; M             |
+|                          | G1_Snom_1; M – G1_Snom_33; M                                                                                                                                                        | G2_Snom_1; M – G2_Snom_18; M |
+|                          | G3_Snom_1; M – G3_Snom_39; M                                                                                                                                                        | G4_Snom_1; M – G4_Snom_22; M |
+| <b>Test purpose</b>      | Check that:<br>PHM Report syntax is based on the conformance with the CDA R2 standard and Continua constraints                                                                      |                              |
+| <b>Applicability</b>     | C_HRN_SEN_000                                                                                                                                                                       |                              |
+| <b>Other PICS</b>        |                                                                                                                                                                                     |                              |
+| <b>Initial condition</b> | HIS message has been received and saved as an XML file in the test tool.                                                                                                            |                              |
+| <b>Test procedure</b>    | 1. The test tool verifies that the syntax of the PHM report of the received HIS message from the HIS direct sender under test (stored in the test tool during the execution of test |                              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>case TP/HIS/SEN/DSMA/BV-000) OR from the HIS indirect sender under test (stored in the test tool during the execution of TP/HIS/SEN/ISMA/BV-000) is based on the conformance with the CDA R2 standard and CDG constraints. This verification uses an XML template (XSD).</p> <p>Details on the XSD constraints can be found in clause B.2.1.</p> <p>2. The test tool verifies that the snomed codes are correctly translated using an XML file. Details can be found in clause B.3.1.</p> <p>3. The test tool verifies that the semantics of the PHM report of the received HIS message HIS direct sender under test (stored in the test tool during the execution of test case TP/HIS/SEN/DSMA/BV-000) OR from the HIS indirect sender under test (stored in the test tool during the execution of TP/HIS/SEN/ISMA/BV-000) is based on the conformance with the CDA R2 standard and CDG constraints. This verification uses Schematron.</p> <p>Details on the Schematron constraints can be found in clause B.4.1.</p> |
+| <b>Pass/Fail criteria</b> | The CDA R2 standard and CDG constraints syntax and semantic verification of the message is based on the conformance with the XSD template and the Schematron template. This implies that all mandatory elements shall be present, that all recommended elements should be present and that optional elements may be present.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Notes</b>              | Constraint CONF-PHMR-81 has an opened bug (bug 287) in CDG to clarify the structure of manufacturerModelName node.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+### A.7 Group 1.5: HIS message body (PHM report) CDG CCD conformance (CCCD)
+
+|                 |                                                   |                |
+|-----------------|---------------------------------------------------|----------------|
+| <b>TP Id</b>    | TP/HIS/SEN/CCCD/BV-000                            |                |
+| <b>TP label</b> | HIS Message Body (PHM Report) CDG CCD Conformance |                |
+| <b>Coverage</b> | <b>Spec</b>                                       | [ITU-T H.813]  |
+|                 | <b>Testable items</b>                             | GenDF 9; M     |
+|                 |                                                   | GenDF 13; M    |
+|                 |                                                   | GenDF 14; M    |
+|                 | <b>Spec</b>                                       | GenDF 15; R    |
+|                 |                                                   | GenDF 16; M    |
+|                 | <b>Testable items</b>                             | [HL7 CDA-PHMR] |
+|                 |                                                   | CONF-371; M    |
+|                 |                                                   | CONF-372; M    |
+|                 |                                                   | CONF-373; M    |
+|                 |                                                   | CONF-374;M     |
+|                 |                                                   | CONF-375; R    |
+|                 |                                                   | CONF-304; M    |
+|                 |                                                   | CONF-305; M    |
+|                 |                                                   | CONF-306; M    |
+|                 |                                                   | CONF-307; R    |
+|                 |                                                   | CONF-308; R    |
+|                 |                                                   | CONF-309; R    |
+|                 |                                                   | CONF-310; R    |
+|                 |                                                   | CONF-311; R    |
+|                 |                                                   | CONF-312; O    |
+|                 |                                                   | CONF-313; O    |
+|                 |                                                   | CONF-314;O     |
+|                 |                                                   | CONF-316; M    |
+|                 |                                                   | CONF-317; M    |
+|                 |                                                   | CONF-318; M    |
+|                 |                                                   | CONF-319; R    |
+|                 |                                                   | CONF-320; R    |
+|                 |                                                   | CONF-321; O    |
+|                 |                                                   | CONF-322; O    |
+|                 |                                                   | CONF-323; O    |
+
+|  |  |              |              |
+|--|--|--------------|--------------|
+|  |  | CONF-324; O  | CONF-325; O  |
+|  |  | CONF-327; O  | CONF-328; C  |
+|  |  | CONF-329; M  | CONF-330; O  |
+|  |  | CONF-331; M  | CONF-332; M  |
+|  |  | CONF-333; M  | CONF-334; O  |
+|  |  | CONF-335 ; M | CONF-336 ; M |
+|  |  | CONF-337; M  | CONF-338; O  |
+|  |  | CONF-339; M  | CONF-340; M  |
+|  |  | CONF-341; M  | CONF-342; M  |
+|  |  | CONF-343; M  | CONF-344; M  |
+|  |  | CONF-345; M  | CONF-346; M  |
+|  |  | CONF-347; M  | CONF-348; O  |
+|  |  | CONF-349; M  | CONF-350; O  |
+|  |  | CONF-351; O  | CONF-352; M  |
+|  |  | CONF-353; M  | CONF-354; M  |
+|  |  | CONF-355; O  | CONF-356; M  |
+|  |  | CONF-357; M  | CONF-358; M  |
+|  |  | CONF-359; R  | CONF-363; M  |
+|  |  | CONF-364; O  | CONF-365; O  |
+|  |  | CONF-366; O  | CONF-367; R  |
+|  |  | CONF-368; O  | CONF-369; O  |
+|  |  | CONF-381; M  | CONF-382; M  |
+|  |  | CONF-383; M  | CONF-384; M  |
+|  |  | CONF-385; R  | CONF-386;M   |
+|  |  | CONF-393; M  | CONF-394; M  |
+|  |  | CONF-395; M  | CONF-396; M  |
+|  |  | CONF-397; M  | CONF-398; R  |
+|  |  | CONF-399; R  | CONF-400; M  |
+|  |  | CONF-402; M  | CONF-403; O  |
+|  |  | CONF-405; M  | CONF-407; M  |
+|  |  | CONF-408; M  | CONF-409; M  |
+|  |  | CONF-410; M  | CONF-411; R  |
+
+|  |             |             |
+|--|-------------|-------------|
+|  | CONF-412; M | CONF-413; R |
+|  | CONF-414; O | CONF-415; M |
+|  | CONF-416; M | CONF-417; M |
+|  | CONF-418; R | CONF-419; R |
+|  | CONF-420; M | CONF-15; M  |
+|  | CONF-16; M  | CONF-17; M  |
+|  | CONF-18; M  | CONF-19; R  |
+|  | CONF-20; M  | CONF-21; M  |
+|  | CONF-22; M  | CONF-23; M  |
+|  | CONF-24; M  | CONF-25; M  |
+|  | CONF-26; M  | CONF-27; M  |
+|  | CONF-123; M | CONF-124; M |
+|  | CONF-125; M | CONF-126; M |
+|  | CONF-127; R | CONF-128; R |
+|  | CONF-129; O | CONF-133; R |
+|  | CONF-134; O | CONF-135; O |
+|  | CONF-136; M | CONF-137; M |
+|  | CONF-138; M | CONF-139; M |
+|  | CONF-145; M | CONF-146; M |
+|  | CONF-147; M | CONF-148; M |
+|  | CONF-149; M | CONF-150; O |
+|  | CONF-151; M | CONF-152; O |
+|  | CONF-153; R | CONF-154; M |
+|  | CONF-155; M | CONF-156; M |
+|  | CONF-157; M | CONF-158; R |
+|  | CONF-159; O | CONF-160; O |
+|  | CONF-162; O | CONF-163; M |
+|  | CONF-164; M | CONF-165; O |
+|  | CONF-166; M | CONF-167; M |
+|  | CONF-287; M | CONF-288; M |
+|  | CONF-289; M | CONF-290; M |
+|  | CONF-291; M | CONF-292; M |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |             |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+|                           | CONF-293; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | CONF-294; M |
+|                           | CONF-295; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | CONF-282; M |
+|                           | CONF-283; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | CONF-284; M |
+|                           | CONF-285; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | CONF-286; M |
+|                           | CONF-448; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | CONF-449; M |
+|                           | CONF-450; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | CONF-451; R |
+|                           | CONF-225; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | CONF-226; M |
+|                           | CONF-227; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | CONF-228; M |
+|                           | CONF-229; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | CONF-230; M |
+|                           | CONF-388;M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | CONF-389;M  |
+|                           | CONF-390;M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | CONF-391;M  |
+| <b>Test purpose</b>       | Check that:<br>PHM Report syntax is based on the conformance with the CCD standard and Continua constraints                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |             |
+| <b>Applicability</b>      | C_HRN_SEN_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |             |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |             |
+| <b>Initial condition</b>  | HIS message has been received and saved as an XML file in the test tool.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |             |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The test tool verifies that the semantics of the PHM report of the received HIS message from the HIS direct sender under test (stored in the test tool during the execution of test case TP/HIS/SEN/DSMA/BV-000) OR from the HIS indirect sender under test (stored in the test tool during the execution of TP/HIS/SEN/ISMA/BV-000) is based on the conformance with the CCD standard and CDG constraints. This verification uses Schematron.</li> <li>Details of the Schematron constraints can be found in clause B.4.2.</li> </ol> |             |
+| <b>Pass/Fail criteria</b> | The CCD standard and CDG constraints syntax and semantic verification of the message is based on conformance with the Schematron template. This implies that all mandatory elements shall be present, that recommended elements should be present and that optional elements may be present.                                                                                                                                                                                                                                                                                  |             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |             |
+
+### A.8 Group 1.6: HIS message header (metadata) semantic validation (mapping with PHM report) (XMSV)
+
+|                 |                                                                                    |               |
+|-----------------|------------------------------------------------------------------------------------|---------------|
+| <b>TP Id</b>    | TP/HIS/SEN/XMSV/BV-000                                                             |               |
+| <b>TP label</b> | HIS Message Header (Metadata) Semantic Validation (Mapping with PHM Report) (XMSV) |               |
+| <b>Coverage</b> | <b>Spec</b>                                                                        | [ITU-T H.813] |
+|                 | <b>Testable items</b>                                                              | MGDC_XDR-6; R |
+|                 |                                                                                    | PHMAG 1; M    |
+|                 |                                                                                    | XDSSSMD-2; M  |
+|                 |                                                                                    | XDSSSMD-4; M  |
+|                 |                                                                                    | MGDC_XDR-7; M |
+|                 |                                                                                    | PHMAG 2; M    |
+|                 |                                                                                    | XDSSSMD-3; M  |
+|                 |                                                                                    | XDSSSMD-5; M  |
+
+|                           |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |               |
+|---------------------------|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+|                           |  | XDSSSMD-6; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | XDSSSMD-7; O  |
+|                           |  | XDSSSMD-9; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | XDSSSMD-10; M |
+|                           |  | XDSSSMD-11; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | XDSSSMD-14; M |
+|                           |  | XDSSSMD-15; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | XDSDEMD-1; O  |
+|                           |  | XDSDEMD-2; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | XDSDEMD-3; M  |
+|                           |  | XDSDEMD-4; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | XDSDEMD-5; M  |
+|                           |  | XDSDEMD-6; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | XDSDEMD-8; O  |
+|                           |  | XDSDEMD-9; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | XDSDEMD-10; M |
+|                           |  | XDSDEMD-11; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | XDSDEMD-12; M |
+|                           |  | XDSDEMD-14; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | XDSDEMD-15; O |
+|                           |  | XDSDEMD-16; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | XDSDEMD-17; O |
+|                           |  | XDSDEMD-20; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | XDSDEMD-21; M |
+|                           |  | XDSDEMD-22; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | XDSDEMD-23; M |
+|                           |  | XDSDEMD-24; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | XDSDEMD-25; O |
+|                           |  | XDSDEMD-26; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | XDSDEMD-27; O |
+|                           |  | XDSDEMD-28; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | XDSDEMD-31; M |
+|                           |  | XDSDEMD-32; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | XDSDEMD-34; M |
+|                           |  | XDSDEMD-35; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | XDSDEMD-36; M |
+|                           |  | XDSDEMD-37; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | XDSDEMD-38; M |
+|                           |  | XDSDEMD-39; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | XDSDEMD-40; O |
+| <b>Test purpose</b>       |  | Check that:<br>Specific elements of the header (metadata) match up with elements of the body of the message body (PHM Report)                                                                                                                                                                                                                                                                                                                                                                             |               |
+| <b>Applicability</b>      |  | C_HRN_SEN_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |               |
+| <b>Other PICS</b>         |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |               |
+| <b>Initial condition</b>  |  | HIS message has been received and saved as an XML file in the test tool.                                                                                                                                                                                                                                                                                                                                                                                                                                  |               |
+| <b>Test procedure</b>     |  | <ol style="list-style-type: none"> <li>The test tool checks the mapping of the metadata fields with the message body of the structure received from the HIS direct sender under test (stored in the test tool during the execution of test case TP/HIS/SEN/DSMA/BV-000) OR from the HIS indirect sender under test (stored in the test tool during the execution of TP/HIS/SEN/ISMA/BV-000) using XPath queries.</li> <li>Details of the mapping constraints can be found are in clause B.1.2.</li> </ol> |               |
+| <b>Pass/Fail criteria</b> |  | The metadata fields of the HIS message match the message body ones that have been specified in the mapping section of the CDG. This implies that all mandatory elements shall be present, that recommended elements should be present and that optional elements may be present.                                                                                                                                                                                                                          |               |
+| <b>Notes</b>              |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |               |
+
+### A.9 Group 1.7: HIS adherence monitor validation (AM)
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |               |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| <b>TP Id</b>              | TP/HIS/SEN/AM/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |               |
+| <b>TP label</b>           | HIS Adherence Monitor Validation (AM)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ITU-T H.813] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | GenMDG-1; M   |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | GenMDG-2; M   |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | GenMDG-3; M   |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | GenMDG-4; M   |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | GenMDG-5; M   |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | GenMDG-6; M   |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | GenMDG-7; M   |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | GenMDG-8; M   |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | MMG-1; M      |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | MMG-2; M      |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | MMG-3; M      |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | MMG-4; M      |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | MMG-5; M      |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>PHM Report syntax is based on the conformance with the CDA R2 standard and Continua constraints</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |               |
+| <b>Applicability</b>      | C_HRN_SEN_000 AND C_HRN_SEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |               |
+| <b>Other PICS</b>         | C_HRN_SEN_005                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |               |
+| <b>Initial condition</b>  | The HIS message has been received and saved as an XML file in the test tool.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>Value of the PICS C_HRN_SEN_005 is checked.</li> <li>The test tool verifies that the semantics of the PHM report of the received message from the HIS direct sender under test (stored in the test tool during the execution of test case TP/HIS/SEN/DSMA/BV-000) or from the HIS indirect sender under test (stored in the test tool during the execution of TP/HIS/SEN/ISMA/BV-000) is based on the conformance with the CDA R2 standard and CDG constraints related to adherence monitor device specialization. This verification uses Schematron.</li> <li>Details of the Schematron constraints can be found in clause B.4.3.</li> </ol> |               |
+| <b>Pass/Fail criteria</b> | <p>The CDA R2 standard and CDG constraints syntax and semantic verification of the message is based on the conformance with the Schematron template. This implies that all mandatory elements shall be present, that all recommended elements should be present and that optional elements may be present.</p> <p>PICS C_HRN_SEN_005 shall be set to 'TRUE'.</p>                                                                                                                                                                                                                                                                                                                     |               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |               |
+
+### A.10 Group 1.8: HIS ATNA validation (ATNA)
+
+|                 |                                                              |                |
+|-----------------|--------------------------------------------------------------|----------------|
+| <b>TP Id</b>    | TP/HIS/SEN/ATNA/PHMR/BV-000                                  |                |
+| <b>TP label</b> | HIS ATNA validation (ATNA) Audit Record Syntax and Semantics |                |
+| <b>Coverage</b> | <b>Spec</b>                                                  | [IHE ITI-TF-1] |
+|                 | <b>Testable items</b>                                        | 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   |
+|                           | 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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                 |
+| <b>Test purpose</b>       | Check that:<br>Audit log message is received from the SUT and it is conformant to the ATNA specifications                                                                                                                                                                                                                                                                                                                                                                                                                        |                 |
+| <b>Applicability</b>      | C_HRN_SEN_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                 |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                 |
+| <b>Initial condition</b>  | Audit record message has been received and saved as XML file into the test tool.                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                 |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The test tool checks the syntax and semantics of the received audit record file from the HIS direct sender under test (stored in the test tool during the execution of test case TP/HIS/SEN/DSMA/BV-000) OR from the HIS indirect sender under test (stored in the test tool during the execution of TP/HIS/SEN/ISMA/BV-000)</li> <li>The ATNA XML log is checked for compliance with [IETF RFC 3881] using the XSD schema in clause B.5.</li> </ol>                                      |                 |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The ATNA XML log file conforms to the RFC 3881 schema included in clause B.5.</li> <li>The attribute "code" of the element EventID is set to "110106".</li> <li>The value of the attribute EventDateTime of the element EventIdentification is inside a one minute bracket of the reception time of the XDR or XDM message.</li> </ul>                                                                                                                                                    |                 |
+| <b>Notes</b>              | <ul style="list-style-type: none"> <li>All network time protocol (NTP) -related testable items (TIs) have been changed to non-testable because accuracy cannot be guaranteed due to operating systems / platform limitations (e.g. no better than 2 seconds in Windows, see <a href="http://support.microsoft.com/kb/939322">http://support.microsoft.com/kb/939322</a>).</li> <li>In NTP terminology, a "time client" is always a whole system; however, this test is only testing the application (the HIS sender).</li> </ul> |                 |
+
+|                 |                                  |
+|-----------------|----------------------------------|
+| <b>TP Id</b>    | TP/HIS/SEN/ATNA/PIX/BV-000       |
+| <b>TP label</b> | HIS Patient Identity Feed – ATNA |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                         |                  |  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------|--|
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [IHE ITI-TF-2], Volume 2b, Section 3.40 |                  |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | SecurityReq-2; M                        | SecurityReq-3; M |  |
+| <b>Test purpose</b>       | Check that:<br><br>When SUT sends a Patient Identity Feed message, then an audit log message is received from the SUT and it is conformant to the ATNA specifications                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                         |                  |  |
+| <b>Applicability</b>      | C_HRN_SEN_000 AND (C_HRN_SEN_008 OR C_HRN_SEN_009 OR C_HRN_SEN_011)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                         |                  |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                         |                  |  |
+| <b>Initial condition</b>  | The SUT is ready to send a PIX message using SOAP 1.2 to the simulated PIXManager service or DocumentRegistry service launched in the test tool.                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                         |                  |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The HIS sender under test sends a SOAP 1.2 message containing a patient identity feed to the simulated receiver running in the test tool.</li> <li>2. The HIS sender under test sends the corresponding audit record message to the audit repository.</li> <li>3. The audit repository receives the audit record message and verifies that: <ol style="list-style-type: none"> <li>a. TLS is used and the encryption suite is TLS_RSA_WITH_AES_128_CBC_SHA.</li> </ol> </li> <li>4. It conforms to a reliable syslog's COOKED profile ([IETF RFC 3195])</li> </ol> |                                         |                  |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The ATNA XML log file conforms to the RFC 3881 schema included in clause B.5.</li> <li>• In the audit record, the EventDateTime attribute of the EventIdentification element is set at least one minute before the expedition time of the SOAP message sent in step 1.</li> <li>• The received audit message conforms to a reliable syslog's COOKED profile ([IETF RFC 3195])</li> </ul>                                                                                                                                                                            |                                         |                  |  |
+| <b>Notes</b>              | The current version (v6) used of the IHE ITI documents ([IHE ITI-TF-1] and [IHE ITI-TF-2]) does not define the exact ATNA message to be sent with the PIX message. Once a decision is made to use v8, this test case will be updated to reflect the additional constraints of the IHE.                                                                                                                                                                                                                                                                                                                       |                                         |                  |  |
+
+|                          |                                                                                                                                                                                                                                                                                                |                                         |                  |  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------|--|
+| <b>TP Id</b>             |                                                                                                                                                                                                                                                                                                | TP/HIS/SEN/ATNA/PIX/BV-001              |                  |  |
+| <b>TP label</b>          |                                                                                                                                                                                                                                                                                                | HIS PIXV3 Query – ATNA                  |                  |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                    | [IHE ITI-TF-2], Volume 2b, Section 3.40 |                  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                          | SecurityReq-2; M                        | SecurityReq-3; M |  |
+| <b>Test purpose</b>      | Check that:<br><br>When SUT sends a PIXV3 Query, then an audit log message is received from the SUT and it is conformant to the ATNA specifications                                                                                                                                            |                                         |                  |  |
+| <b>Applicability</b>     | C_HRN_SEN_000 AND (C_HRN_SEN_008 OR C_HRN_SEN_009 OR C_HRN_SEN_011)                                                                                                                                                                                                                            |                                         |                  |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                |                                         |                  |  |
+| <b>Initial condition</b> | The SUT is ready to send a PIX message using SOAP 1.2 to the simulated PIXManager service or DocumentRegistry service launched in the test tool.                                                                                                                                               |                                         |                  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The HIS sender under test sends a SOAP 1.2 message containing a PIX query to the simulated receiver running in the test tool.</li> <li>2. The HIS sender under test sends the corresponding audit record message to the audit repository.</li> </ol> |                                         |                  |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>3. The audit repository receives the audit record message and verifies that:</p> <ol style="list-style-type: none"> <li>TLS is used and the encryption suite is TLS_RSA_WITH_AES_128_CBC_SHA.</li> </ol> <p>4. It conforms to a reliable syslog's COOKED profile ([IETF RFC 3195])</p>                                                                                                                                    |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The ATNA XML log file conforms to the RFC 3881 schema included in clause B.5.</li> <li>In the audit record, the EventDateTime attribute of the EventIdentification element is set at least one minute before the expedition time of the SOAP message sent in step 1.</li> <li>The received audit message conforms to a reliable syslog's COOKED profile ([IETF RFC 3195]).</li> </ul> |
+| <b>Notes</b>              | <p>The current version (v6) used of the IHE ITI documents ([IHE ITI-TF-1] and [IHE ITI-TF-2]) does not define the exact ATNA message to be sent with the PIX message. Once a decision is made to use v8, this test case will be updated to reflect the additional constraints of the IHE.</p>                                                                                                                                |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                         |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|
+| <b>TP Id</b>              | TP/HIS/SEN/ATNA/CM/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                         |
+| <b>TP label</b>           | HIS Repository Retrieve Document Set Transaction – ATNA                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                         |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [IHE ITI-TF-2], Volume 2b, Section 3.40 |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | RepSecCons_01                           |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>When SUT receives a Retrieve Document Set Transaction, then an audit log message is received from the SUT and it is conformant to the ATNA specifications</p>                                                                                                                                                                                                                                                                                                                                                                                                    |                                         |
+| <b>Applicability</b>      | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                         |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                         |
+| <b>Initial condition</b>  | <p>The SUT is ready to send a PIX message using SOAP 1.2 to the simulated PIXManager service or DocumentRegistry service launched in the test tool.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                |                                         |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The test tool sends a SOAP 1.2 message containing a PIX query to the XDS.b repository of the HIS sender under test.</li> <li>The HIS sender under test sends the corresponding audit record message to the audit repository.</li> <li>The audit repository receives the audit record message and verifies that:               <ol style="list-style-type: none"> <li>TLS is used and the encryption suite is TLS_RSA_WITH_AES_128_CBC_SHA.</li> </ol> </li> <li>It conforms to a reliable syslog's COOKED profile ([IETF RFC 3195]).</li> </ol> |                                         |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The ATNA XML log file conforms to the RFC 3881 schema included in clause B.5.</li> <li>In the audit record, the EventDateTime attribute of the EventIdentification element is set at least one minute before the expedition time of the SOAP message sent in step 1.</li> <li>The received audit message conforms to a reliable syslog's COOKED profile ([IETF RFC 3195]).</li> </ul>                                                                                                                                                           |                                         |
+| <b>Notes</b>              | <p>The current version (v6) used of the IHE ITI documents ([IHE ITI-TF-1] and [IHE ITI-TF-2]) does not define the exact ATNA message to be sent by the XDS.b repository. Once it has been decided to use v8, this test case will be updated to reflect the additional constraints of the IHE.</p>                                                                                                                                                                                                                                                                                      |                                         |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                         |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|
+| <b>TP Id</b>              | TP/HIS/SEN/ATNA/CM/BV-001                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                         |
+| <b>TP label</b>           | HIS Registry Query Transaction – ATNA                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                         |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [IHE ITI-TF-2], Volume 2b, Section 3.40 |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | RegSecCons_01                           |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>When SUT receives a Retrieve Document Set Transaction, then an audit log message is received from the SUT and it is conformant to the ATNA specifications</p>                                                                                                                                                                                                                                                                                                                                                                                      |                                         |
+| <b>Applicability</b>      | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                         |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                         |
+| <b>Initial condition</b>  | The SUT is ready to send a PIX message using SOAP 1.2 to the simulated PIXManager service or DocumentRegistry service launched in the test tool.                                                                                                                                                                                                                                                                                                                                                                                                                         |                                         |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The test tool sends a SOAP 1.2 message containing a PIX query to the XDS.b repository of the HIS sender under test.</li> <li>The HIS sender under test sends the corresponding audit record message to the audit repository.</li> <li>The audit repository receives the audit record message and verifies that: <ol style="list-style-type: none"> <li>TLS is used and the encryption suite is TLS_RSA_WITH_AES_128_CBC_SHA.</li> </ol> </li> <li>It conforms to a reliable syslog's COOKED profile ([IETF RFC 3195]).</li> </ol> |                                         |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The ATNA XML log file conforms to the RFC 3881 schema included in clause B.5.</li> <li>In the audit record, the EventDateTime attribute of the EventIdentification element is set at least one minute before the expedition time of the SOAP message sent in step 1.</li> <li>The received audit message conforms to a reliable syslog's COOKED profile ([IETF RFC 3195]).</li> </ul>                                                                                                                                             |                                         |
+| <b>Notes</b>              | <p>The current (v6) version used of the IHE ITI documents ([IHE ITI-TF-1] and [IHE ITI-TF-2]) does not define the exact ATNA message to be sent by the XDS.b Repository. Once it has been decided to use v8, this test case will be updated to reflect the additional constraints of the IHE.</p>                                                                                                                                                                                                                                                                        |                                         |
+
+|                          |                                                                                                                                                                                          |                |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|
+| <b>TP Id</b>             | TP/HIS/SEN/ATNA/GEN/BV-000                                                                                                                                                               |                |
+| <b>TP label</b>          | HIS ATNA validation (ATNA) Audit Record Behaviour                                                                                                                                        |                |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                              | [IHE ITI-TF-1] |
+|                          | <b>Testable items</b>                                                                                                                                                                    | Audit_MT-1; M  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If Audit Record repository is not available, the IHE actor shall store the Audit Record in a local buffer until the Audit Record Repository is available again</p> |                |
+| <b>Applicability</b>     | C_HRN_SEN_000                                                                                                                                                                            |                |
+| <b>Other PICS</b>        | C_SEN_HRN_001, C_SEN_HRN_002                                                                                                                                                             |                |
+| <b>Initial condition</b> | The SUT is ready to send an email containing an XDR or XDM report to the test tool.                                                                                                      |                |
+| <b>Test procedure</b>    | If C_SEN_HRN_001 then:                                                                                                                                                                   |                |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ol style="list-style-type: none"> <li>1. The test tool initiates the server applications and the web service which will receive the HIS message from the HIS direct sender under test during a specific time.</li> <li>2. The audit repository server is intentionally not initiated.</li> <li>3. The simulated HIS receiver (test tool) sends a public certificate to the HIS direct sender under test which has to accept it.</li> <li>4. The HIS direct sender under test sends an XDR message to the test tool.</li> <li>5. The test tool receives the XDR message but it does not receive the ATNA message because its ATNA receiver was intentionally disabled above.</li> <li>6. Wait for one minute.</li> <li>7. The test tool initiates the audit repository receiver that will receive the audit record message.</li> <li>8. Force the HIS sender to resend the waiting audit record message.</li> <li>9. The test tool captures the audit record message.</li> </ol> <p>If C_SEN_HRN_002 then:</p> <ol style="list-style-type: none"> <li>1. The test tool initiates the SMTP client that will receive the XDM message from the HIS sender under test during a specific time.</li> <li>2. The audit repository server is not intentionally initiated.</li> <li>3. The HIS receiver of the test tool sends a public certificate to the HIS direct sender under test and it has to accept it.</li> <li>4. The HIS indirect sender under test sends an XDM message to the test tool.</li> <li>5. The test tool receives the XDM message but it does not receive the ATNA message because its ATNA receiver is disabled.</li> <li>6. Wait for one minute.</li> <li>7. The test tool initiates the audit repository receiver that will receive the audit record message.</li> <li>8. Force the HIS sender to send the waiting audit record message.</li> <li>9. The test tool captures the audit record message.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The received audit record message EventDateTime attribute of the EventIdentification element in the ATNA XML log has to be set to the expedition time of the first HIS message.</li> <li>• In case there are more than two audit record messages received in step 8, one of them shall comply with the previous stored point.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              | In step 7, the way to force the HIS sender to send the waiting audit record depends on the exact sender implementation; a typical strategy could be to send another PHM report and then send the old audit record along with the newer one.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+### A.11 Group 1.9: HIS document digital signature validation (DSG)
+
+|                 |                                                                      |                                                                  |
+|-----------------|----------------------------------------------------------------------|------------------------------------------------------------------|
+| <b>TP Id</b>    | TP/HIS/SEN/DSG/BV-000                                                |                                                                  |
+| <b>TP label</b> | HIS Document Digital Signature validation (DSG) Syntax and Semantics |                                                                  |
+| <b>Coverage</b> | <b>Spec</b>                                                          | [ITU-T H.813]                                                    |
+|                 | <b>Testable items</b>                                                | Non_Repud_1      Non_Repud_2                                     |
+|                 | <b>Spec</b>                                                          | [IHE ITI-TF-1]                                                   |
+|                 | <b>Testable items</b>                                                | DSGContent_1      DSGContent_2<br>DSGContent_3      DSGContent_4 |
+
+|                          |  |                                                                                                                                                                                                                                                                                                                                                               |                      |
+|--------------------------|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|
+|                          |  | DSGContent_5                                                                                                                                                                                                                                                                                                                                                  | DSGContent_6         |
+|                          |  | DSGContent_7                                                                                                                                                                                                                                                                                                                                                  | DSGContent_8         |
+|                          |  | DSGContent_9                                                                                                                                                                                                                                                                                                                                                  | DSGContent_10        |
+|                          |  | DSGContent_11                                                                                                                                                                                                                                                                                                                                                 | DSGContent_12        |
+|                          |  | DSGContent_13                                                                                                                                                                                                                                                                                                                                                 | DSGContent_14        |
+|                          |  | DSGContent_15                                                                                                                                                                                                                                                                                                                                                 | DSGContent_16        |
+|                          |  | DSGContent_17                                                                                                                                                                                                                                                                                                                                                 | DSGContent_18        |
+|                          |  | DSGContent_19                                                                                                                                                                                                                                                                                                                                                 | DSGContent_20        |
+|                          |  | DSGEntryAttribute_1                                                                                                                                                                                                                                                                                                                                           | DSGEntryAttribute_2  |
+|                          |  | DSGEntryAttribute_3                                                                                                                                                                                                                                                                                                                                           | DSGEntryAttribute_4  |
+|                          |  | DSGEntryAttribute_5                                                                                                                                                                                                                                                                                                                                           | DSGEntryAttribute_6  |
+|                          |  | DSGEntryAttribute_7                                                                                                                                                                                                                                                                                                                                           | DSGEntryAttribute_8  |
+|                          |  | DSGEntryAttribute_9                                                                                                                                                                                                                                                                                                                                           | DSGEntryAttribute_10 |
+|                          |  | DSGEntryAttribute_11                                                                                                                                                                                                                                                                                                                                          | DSGEntryAttribute_12 |
+|                          |  | DSGEntryAttribute_13                                                                                                                                                                                                                                                                                                                                          | DSGEntryAttribute_14 |
+|                          |  | DSGEntryAttribute_15                                                                                                                                                                                                                                                                                                                                          | DSGEntryAttribute_16 |
+|                          |  | DSGEntryAttribute_17                                                                                                                                                                                                                                                                                                                                          | DSGEntryAttribute_18 |
+|                          |  | DSGEntryAttribute_19                                                                                                                                                                                                                                                                                                                                          | DSGEntryAttribute_20 |
+|                          |  | DSGEntryAttribute_21                                                                                                                                                                                                                                                                                                                                          | DSGEntryAttribute_22 |
+|                          |  | DSGEntryAttribute_23                                                                                                                                                                                                                                                                                                                                          | DSGEntryAttribute_24 |
+|                          |  | DSGEntryAttribute_24                                                                                                                                                                                                                                                                                                                                          | Signature_1          |
+|                          |  | Signature_2                                                                                                                                                                                                                                                                                                                                                   | Signature_3          |
+|                          |  | Signature_4                                                                                                                                                                                                                                                                                                                                                   | Signature_5          |
+|                          |  | Signature_6                                                                                                                                                                                                                                                                                                                                                   | Signature_7          |
+|                          |  | Signature_8                                                                                                                                                                                                                                                                                                                                                   |                      |
+| <b>Test purpose</b>      |  | Check that:<br>Digital Signature document is based on the conformance with the IHE profile and Continua Constraints                                                                                                                                                                                                                                           |                      |
+| <b>Applicability</b>     |  | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_006                                                                                                                                                                                                                                                                                                             |                      |
+| <b>Other PICS</b>        |  |                                                                                                                                                                                                                                                                                                                                                               |                      |
+| <b>Initial condition</b> |  | The SUT is ready to send an XDS.b submission set by XDR to the test tool.                                                                                                                                                                                                                                                                                     |                      |
+| <b>Test procedure</b>    |  | <ol style="list-style-type: none"> <li>The test tool initiates the server applications and the web service which will receive the HIS message from the HIS direct sender under test during a specific time.</li> <li>The simulated HIS receiver (test tool) sends a public certificate to the HIS direct sender under test which has to accept it.</li> </ol> |                      |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ol style="list-style-type: none"> <li>3. The test tool initiates the audit repository receiver.</li> <li>4. The HIS direct sender under test sends an XDR message to the test tool.</li> <li>5. The test tool captures the audit record message.</li> <li>6. The test tool extracts the PHM record and the digital signature document from the XDS.b.</li> <li>7. The digital signature document is checked for compliance with the XAdES specification through the schemas in Annex B. (Due to the fact that XAdES is an extension of XmlDsig, its schema is also used.)</li> <li>8. The digital signature document is checked for IHE constraints using Schematron.</li> <li>9. The test tool checks that the digital signature document is the signature of the accompanying PHM report.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• Syntax of the signature document conforms with the XML advanced electronic signatures specification.</li> <li>• IHE restrictions are met by the received signature document specified in clause B.4.4.</li> <li>• The digital signature document found in the XDS message is the signature of the PHM report of the same XDS message.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+### A.12 Group 1.10: HIS patient identification validation (PIX)
+
+|                 |                                                |                                                                      |                     |                     |
+|-----------------|------------------------------------------------|----------------------------------------------------------------------|---------------------|---------------------|
+| <b>TP Id</b>    | TP/HIS/SEN/PIX/BV-000                          |                                                                      |                     |                     |
+| <b>TP label</b> | HIS Patient Identity Feed – Add Patient Record |                                                                      |                     |                     |
+| <b>Coverage</b> | <b>Spec</b>                                    | [ITU-T H.813]                                                        |                     |                     |
+|                 | <b>Testable items</b>                          | PIMG-1; M                                                            | PIMG-2; O           |                     |
+|                 | <b>Spec</b>                                    | [IHE ITF PIX PDQ], Patient Identifier Cross-Reference HL7 V3 (PIXV3) |                     |                     |
+|                 | <b>Testable items</b>                          | PatientRecord-3; M                                                   | PatientRecord-6; M  | PatientRecord-7; M  |
+|                 |                                                | PatientRecord-8; M                                                   | PatientRecord-9; M  | PatientRecord-10; O |
+|                 |                                                | PatientRecord-11; O                                                  | PatientRecord-12; M | PatientRecord-13; M |
+|                 |                                                | PatientRecord-14; M                                                  | PatientRecord-15; M | PatientRecord-16; M |
+|                 |                                                | PatientRecord-17; M                                                  | PatientRecord-18; M | PatientRecord-19; M |
+|                 |                                                | PatientRecord-20; M                                                  | PatientRecord-21; M | PatientRecord-22; O |
+|                 |                                                | PatientRecord-23; O                                                  | PatientRecord-24; M | PatientRecord-25; M |
+|                 |                                                | PatientRecord-26; M                                                  | PatientRecord-27; O | PatientRecord-28; O |
+|                 |                                                | PatientRecord-29; O                                                  | PatientRecord-30; O | PatientRecord-31; O |
+|                 |                                                | PatientRecord-32; O                                                  | PatientRecord-33; O | PatientRecord-34; O |
+|                 |                                                | PatientRecord-35; O                                                  | PatientRecord-36; O | PatientRecord-37; O |
+|                 |                                                | PatientRecord-38; O                                                  | PatientRecord-39; O | PatientRecord-40; C |
+|                 |                                                | PatientRecord-41; C                                                  | PatientRecord-42; O | PatientRecord-43; C |
+|                 |                                                | PatientRecord-44; C                                                  | PatientRecord-45; C | PatientRecord-46; O |
+
+|                       |                                                                                  |                     |                     |
+|-----------------------|----------------------------------------------------------------------------------|---------------------|---------------------|
+|                       | PatientRecord-47; C                                                              | PatientRecord-48; C | PatientRecord-49; C |
+|                       | PatientRecord-50; C                                                              | PatientRecord-51; C | PatientRecord-52; C |
+|                       | PatientRecord-53; C                                                              | PatientRecord-54; O | PatientRecord-55; C |
+|                       | PatientRecord-56; C                                                              | PatientRecord-57; C | PatientRecord-58; O |
+|                       | PatientRecord-59; C                                                              | PatientRecord-60; C | PatientRecord-61; M |
+|                       | PatientRecord-62; M                                                              | PatientRecord-63; M | PatientRecord-64; M |
+|                       | PatientRecord-66; M                                                              | PatientRecord-67; M | PatientRecord-4; M  |
+|                       | PatientRecord-65; M                                                              |                     |                     |
+| <b>Spec</b>           | [IHE ITF PIX PDQ], Patient Identifier Cross-Reference HL7 V3 (PIXV3), Appendix E |                     |                     |
+| <b>Testable items</b> | IIDataType-1; M                                                                  | IIDataType-2; C     | IIDataType-3; C     |
+|                       | IIDataType-17; M                                                                 | IIDataType-18; M    | IIDataType-19; O    |
+|                       | IIDataType-20; O                                                                 | IIDataType-21; M    |                     |
+| <b>Spec</b>           | [IHE ITF PIX PDQ], Patient Identifier Cross-Reference HL7 V3 (PIXV3), Appendix O |                     |                     |
+| <b>Testable items</b> | PayloadIM-1; M                                                                   | PayloadIM-2; M      | PayloadIM-3; M      |
+|                       | PayloadIM-4; M                                                                   | PayloadIM-5; O      | PayloadIM-6; M      |
+|                       | PayloadIM-7; M                                                                   | PayloadIM-8; M      | PayloadIM-9; M      |
+|                       | PayloadIM-10; O                                                                  | PayloadIM-11; M     | PayloadIM-12; M     |
+|                       | PayloadIM-13; M                                                                  | PayloadIM-14; M     | PayloadIM-15; M     |
+|                       | PayloadIM-16; M                                                                  | PayloadIM-17; M     | PayloadIM-18; M     |
+|                       | PayloadIM-19; O                                                                  | PayloadIM-20; O     | PayloadIM-21; O     |
+|                       | PayloadIM-22; O                                                                  | PayloadIM-23; O     | PayloadIM-24; C     |
+|                       | PayloadIM-25; O                                                                  | PayloadIM-26; C     | PayloadIM-27; C     |
+|                       | PayloadIM-28; C                                                                  | PayloadIM-29; C     | PayloadIM-30; C     |
+|                       | PayloadIM-31; M                                                                  | EventIM-1; M        | EventIM-2; M        |
+|                       | EventIM-3; M                                                                     | EventIM-4; M        | EventIM-5; M        |
+|                       | EventIM-6; M                                                                     | EventIM-7; O        | EventIM-8; M        |
+|                       | EventIM-9; M                                                                     | EventIM-10; M       | EventIM-11; M       |
+|                       | EventIM-12; M                                                                    | EventIM-13; M       | EventIM-14; M       |
+|                       | EventIM-15; M                                                                    | EventIM-16; M       | EventIM-17; M       |
+|                       | EventIM-18; C                                                                    | EventIM-19; M       | EventIM-20; O       |
+|                       | EventIM-21; O                                                                    | EventIM-22; C       | EventIM-23; C       |
+|                       | EventIM-24; C                                                                    | EventIM-25; C       | EventIM-26; C       |
+
+|                          |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |               |               |
+|--------------------------|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|
+|                          |  | EventIM-27; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | EventIM-28; C | EventIM-29; C |
+|                          |  | EventIM-30; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | EventIM-31; M | EventIM-32; M |
+|                          |  | EventIM-33; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | EventIM-34; O | EventIM-35; O |
+|                          |  | EventIM-36; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | EventIM-37; C | EventIM-38; C |
+|                          |  | EventIM-39; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | EventIM-40; C | EventIM-41; C |
+|                          |  | EventIM-42; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | EventIM-43; C | EventIM-44; C |
+| <b>Test purpose</b>      |  | <p>Check that:</p> <p>Continua HIS senders shall implement the Patient Identity Source actor of IHE ITI-44: Patient Identity Feed HL7 V3 in order to submit new patient identifiers to the HIS receiver or third party exchanges</p> <p>[AND]</p> <p>Continua HIS senders may implement the Patient Identity Source actor of IHE ITI-44: Patient Identity Feed HL7 V3 in order to submit new device registration to the HIS receiver or third party exchanges</p> <p>[AND]</p> <p>Message Payload and Control Act and Transmission Wrappers are based on the conformance with the IHE profile.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |               |               |
+| <b>Applicability</b>     |  | C_HRN_SEN_000 AND (C_HRN_SEN_008 OR C_HRN_SEN_009)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |               |               |
+| <b>Other PICS</b>        |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |               |               |
+| <b>Initial condition</b> |  | The SUT is ready to send a PIX message using SOAP 1.2 to the simulated PIXManager service or DocumentRegistry service launched in the test tool.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |               |               |
+| <b>Test procedure</b>    |  | <ol style="list-style-type: none"> <li>1. The HIS sender under test sends a SOAP 1.2 message containing a patient registry record added to the simulated receiver running in the test tool.</li> <li>2. The test tool receives the SOAP message and checks that: <ol style="list-style-type: none"> <li>a. the version of the SOAP is 1.2, that is the namespace of the envelope is <a href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</a>.</li> <li>b. The action of the transaction is "urn:hl7-org:v3:PRPA_IN201301UV02".</li> <li>c. The SOAP body has only one child that is a PRPA_IN201301UV02 element with the namespace "urn:hl7-org:v3".</li> </ol> </li> <li>3. The test tool checks the control act and transmission wrappers and the message payload as follows: <ol style="list-style-type: none"> <li>a. The following optional class attributes are omitted: <ul style="list-style-type: none"> <li><input type="checkbox"/> Message.profileId</li> <li><input type="checkbox"/> Message.responseCode</li> <li><input type="checkbox"/> Message.attachmentText</li> <li><input type="checkbox"/> Sender.telecom</li> <li><input type="checkbox"/> Receiver.telecom</li> <li><input type="checkbox"/> Device.desc</li> <li><input type="checkbox"/> Device.existenceTime.</li> </ul> </li> <li>b. The following optional classes are omitted: <ul style="list-style-type: none"> <li><input type="checkbox"/> AttentionLine</li> <li><input type="checkbox"/> RespondTo</li> <li><input type="checkbox"/> LocatedEntity</li> </ul> </li> </ol> </li> </ol> |               |               |
+
+- scopedRole(Organization).
+- c. id element of type II is required, that is @root and @extension attributes are present in this id element. @assigningAuthorityName attribute is not present and @Displayable attribute can be present.
+- d. creationTime element of type TS is required, that is @value with a valid time value is present.
+- e. If versionCode element is present, its value must be "V3PR1".
+- f. The value of interactionId/@extension attribute is set to "PRPA\_IN201301UV02".
+- g. sequenceNumber element of type INT can be present.
+- h. The value of processingModeCode/@code attribute is set to "T".
+- i. The acceptAckCode/@code attribute is set to "AL".
+- j. Sender element is present and inside it:
+  - @typeCode attribute is present and its value is set to "SND".
+  - A device element is present and inside it:
+    - @classCode attribute is present and its value is set to "DEV"
+    - @determinerCode attribute is present and its value is set to "INSTANCE".
+    - At least one Device/id element is present, Device/id/@root is an ISO OID and Device/id/@extension does not have a value, Device/id/@assigningAuthorityName is not present and Device/id/@Displayable attribute can be present.
+    - Device/name element can be present
+    - telecom element can be present
+    - manufacturerModelName element can be present
+    - softwareName element can be present.
+- k. There is only one receiver element and inside it:
+  - @typeCode attribute is present and its value is set to "RCV".
+  - A device element is present and inside it:
+    - @classCode attribute is present and its value is set to "DEV"
+    - @determinerCode attribute is present and its value is set to "INSTANCE".
+    - At least one Device/id element is present, Device/id/@root is an ISO OID and Device/id/@extension does not have a value, Device/id/@assigningAuthorityName is not present and Device/id/@Displayable attribute can be present.
+    - Device/name element can be present
+    - telecom element can be present
+    - manufacturerModelName element can be present
+    - softwareName element can be present.
+- l. If Agent element is present:
+  - @classCode attribute is present and its value is set to "AGNT".
+- m. If Organization element is present:
+  - @classCode attribute is present and its value is set to "ORG".
+  - @determinerCode attribute is present and its value is set to "INSTANCE".
+  - At least one Organization/id element is present.
+  - Organization/name element can be present.
+  - Organization/telecom element can be present.
+- n. ControlActProcess element is present and inside this element:
+  - The following optional class attributes are omitted:
+
+- ControlActProcess.text
+- ControlActProcess.priorityCode
+- ControlActProcess.reasonCode.
+- @classCode attribute is present and its value is set to "CACT".
+- @moodCode attribute is present and its value is one of the following:
+  - "INT" – intent
+  - "RQO" – request
+  - "EVN" – event, occurrence
+  - "PRP" – proposal
+  - "RMD" – recommendation
+  - "APT" – appointment
+  - "ARQ" – appointment request
+  - "PRMS" – promise.
+- id element can be present.
+- code element shall be set to "PRPA\_TE201301UV02".
+- effectiveTime element can be present.
+- languageCode element can be present.
+- Participation elements are not present.
+- The reasonOf act relationship is not present.
+- The following act relationships to the RegistrationEvent are not present:
+  - inFullfilmentOf
+  - definition
+  - subject2.
+- subject element is present and:
+  - @typeCode attribute is present and its value is set to "SUBJ"
+  - @contextConductionInd attribute is present and its value is set to "false".
+- RegistrationEvent element is present and:
+  - @classCode attribute is present and its value is set to "REG"
+  - @moodCode attribute is present and its value is set to "EVN"
+  - id element can be present
+  - statusCode/@code attribute is set to "active"
+  - effectiveTime element can be present, but if it is present, author/Time element must be valued with the same time expression
+  - subject1/typeCode attribute is present and its value is set to "SBJ"
+  - RegisteredRole element can be present
+  - author element can be present, but if it is present:
+    - i. @typeCode attribute is present and its value is set to "AUT"
+    - ii. @contextControlCode attribute can be present and if it is present, its value is set to "AP"
+    - iii. AssignedEntity element can be present and if it is present, it should be a person, it may be a device or organization and it shall not be a non-person living object
+    - iv. time element can be present, but if it is valued, the RegistrationEvent/effectiveTime element must be valued with the same time expression
+    - v. modeCode element can be present.
+
+- Custodian element is present and:
+  - i. @typeCode attribute is present and its value is set to "CST"
+  - ii. @contextControlCode attribute can be present and if it is present, its value is set to "CST"
+  - iii. assignedEntity element is either an organization or a device.
+- ReplacementOf element is not present.
+- o. A patient element is present as a child of subject1 element and in this element:
+  - @classCode attribute is present and its value is set to "PAT".
+  - At least one id element is present.
+  - statusCode element is present and its value is set to "active".
+  - confidentialityCode element can be present.
+  - veryImportantPersonCode can be present.
+  - The provider organization element is present, and:
+    - the provider organization needs to be identified by an id attribute, and at least one of address, telecommunications address, or contact person should be present
+    - id element has only a root, expressed as an ISO OID.
+    - The following roles are omitted:
+      - asPatientOfOtherProvider
+      - birthPlace
+      - guarantor
+      - guardian
+      - contactParty
+      - asMember
+      - careGiver
+      - asStudent
+    - The following participations are omitted:
+      - subjectOf (administrativeObservation)
+      - coveredPartyOf (coverage).
+  - patientPerson element is present and:
+    - @classCode attribute is present and its value is set to "PSN"
+    - @determinerCode attribute is present and its value is set to "INSTANCE"
+    - One or more name elements are present
+    - More than one telecom elements can be present
+    - administrativeGenderCode element can be present
+    - birthTime element can be present
+    - deceasedInd element can be present
+    - deceasedTime element can be present
+    - multipleBirthInd element can be present
+    - multipleBirthOrderNumber element can be present
+    - addr elements can be present
+    - maritalStatusCode element can be present
+    - religiousAffiliationCode element can be present
+    - raceCode element can be present
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>- ethnicGroupCode element can be present</li> <li>- One or more asOtherIDs elements can be present, but if it is present: <ul style="list-style-type: none"> <li>i. @classCode attribute is present and its value is set to the corresponding role</li> <li>ii. at least one id element is present and OtherIDs/id/@root is identical to scopingOrganization/id/@root</li> <li>iii. scopingOrganization element is present and scopingOrganization/id/@extension does not have any value</li> </ul> </li> <li>- PersonalRelationship element can be present and if it is present: <ul style="list-style-type: none"> <li>i. @classCode attribute is present and its value is set to "PRS"</li> <li>ii. id element can be present</li> <li>iii. code element is present</li> </ul> </li> <li>- Citizen element can be present and if it is present: <ul style="list-style-type: none"> <li>i. @classCode attribute is present and its value is set to "CIT"</li> <li>ii. One or more id element can be present</li> <li>iii. Nation element is present and <ul style="list-style-type: none"> <li>• @classCode attribute is present and its value is set to "NAT"</li> <li>• @determinerCode attribute is present and its value is set to "INSTANCE"</li> <li>• code element is present</li> <li>• name element can be present</li> </ul> </li> </ul> </li> <li>- Employee element can be present and if it is present: <ul style="list-style-type: none"> <li>i. @classCode attribute is present and its value is set to "EMP"</li> <li>ii. statusCode element can be present</li> <li>iii. occupationCode element can be present.</li> </ul> </li> <li>- LanguageCommunication can be present and if it is present: <ul style="list-style-type: none"> <li>i. languageCode element is present</li> <li>ii. preferenceInd element can be present.</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The relationship holder of the personal relationship is restricted to being a person (using CMET COCT_MT030207UV).</li> <li>• When the patient role is scoped by a provider organization, only patient IDs assigned by the provider organization are allowed in the patient class, the root element of the patient IDs shall match the root element of the provider organization ID, and the provider organization ID shall have no extension element.</li> <li>• When any other role associated with the Person class of the patient is scoped by an organization, the root element of the role IDs shall match the root element of the scoping organization ID, and the scoping organization ID shall have no extension element.</li> <li>• All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                 |                                                   |               |           |
+|-----------------|---------------------------------------------------|---------------|-----------|
+| <b>TP Id</b>    | TP/HIS/SEN/PIX/BV-001                             |               |           |
+| <b>TP label</b> | HIS Patient Identity Feed – Revise Patient Record |               |           |
+| <b>Coverage</b> | <b>Spec</b>                                       | [ITU-T H.813] |           |
+|                 | <b>Testable items</b>                             | PIMG-1; M     | PIMG-2; O |
+
+|                       |                                                                                  |                     |                     |
+|-----------------------|----------------------------------------------------------------------------------|---------------------|---------------------|
+| <b>Spec</b>           | [IHE ITF PIX PDQ], Patient Identifier Cross-Reference HL7 V3 (PIXV3)             |                     |                     |
+| <b>Testable items</b> | PatientRecord-3 ; M                                                              | PatientRecord-6; M  | PatientRecord-7; M  |
+|                       | PatientRecord-8; M                                                               | PatientRecord-9; M  | PatientRecord-10; O |
+|                       | PatientRecord-11; O                                                              | PatientRecord-12; M | PatientRecord-13; M |
+|                       | PatientRecord-14; M                                                              | PatientRecord-15; M | PatientRecord-16; M |
+|                       | PatientRecord-17; M                                                              | PatientRecord-18; M | PatientRecord-19; M |
+|                       | PatientRecord-20; M                                                              | PatientRecord-21; M | PatientRecord-22; O |
+|                       | PatientRecord-23; O                                                              | PatientRecord-24; M | PatientRecord-25; M |
+|                       | PatientRecord-26; M                                                              | PatientRecord-27; O | PatientRecord-28; O |
+|                       | PatientRecord-29; O                                                              | PatientRecord-30; O | PatientRecord-31; O |
+|                       | PatientRecord-32; O                                                              | PatientRecord-33; O | PatientRecord-34; O |
+|                       | PatientRecord-35; O                                                              | PatientRecord-36; O | PatientRecord-37; O |
+|                       | PatientRecord-38; O                                                              | PatientRecord-39; O | PatientRecord-40; C |
+|                       | PatientRecord-41; C                                                              | PatientRecord-42; O | PatientRecord-43; C |
+|                       | PatientRecord-44; C                                                              | PatientRecord-45; C | PatientRecord-46; O |
+|                       | PatientRecord-47; C                                                              | PatientRecord-48; C | PatientRecord-49; C |
+|                       | PatientRecord-50; C                                                              | PatientRecord-51; C | PatientRecord-52; C |
+|                       | PatientRecord-53; C                                                              | PatientRecord-54; O | PatientRecord-55; C |
+|                       | PatientRecord-56; C                                                              | PatientRecord-57; C | PatientRecord-58; O |
+|                       | PatientRecord-59; C                                                              | PatientRecord-60; C | PatientRecord-61; M |
+|                       | PatientRecord-62; M                                                              | PatientRecord-63; M | PatientRecord-64; M |
+|                       | PatientRecord-66; M                                                              | PatientRecord-67; M | PatientRecord-4; M  |
+|                       | PIM-9; M                                                                         | PatientRecord-65; M |                     |
+| <b>Spec</b>           | [IHE ITF PIX PDQ], Patient Identifier Cross-Reference HL7 V3 (PIXV3), Appendix E |                     |                     |
+| <b>Testable items</b> | IIDDataType-1; M                                                                 | IIDDataType-2; C    | IIDDataType-3; C    |
+|                       | IIDDataType-17; M                                                                | IIDDataType-18; M   | IIDDataType-19; O   |
+|                       | IIDDataType-20; O                                                                | IIDDataType-21; M   |                     |
+| <b>Spec</b>           | [IHE ITF PIX PDQ], Patient Identifier Cross-Reference HL7 V3 (PIXV3), Appendix O |                     |                     |
+| <b>Testable items</b> | PayloadIM-1; M                                                                   | PayloadIM-2; M      | PayloadIM-3; M      |
+|                       | PayloadIM-4; M                                                                   | PayloadIM-5; O      | PayloadIM-6; M      |
+|                       | PayloadIM-7; M                                                                   | PayloadIM-8; M      | PayloadIM-9; M      |
+|                       | PayloadIM-10; O                                                                  | PayloadIM-11; M     | PayloadIM-12; M     |
+
+|                          |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                 |                 |
+|--------------------------|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------|
+|                          |  | PayloadIM-13; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PayloadIM-14; M | PayloadIM-15; M |
+|                          |  | PayloadIM-16; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PayloadIM-17; M | PayloadIM-18; M |
+|                          |  | PayloadIM-19; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PayloadIM-20; O | PayloadIM-21; O |
+|                          |  | PayloadIM-22; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PayloadIM-23; O | PayloadIM-24; C |
+|                          |  | PayloadIM-25; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PayloadIM-26; C | PayloadIM-27; C |
+|                          |  | PayloadIM-28; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PayloadIM-29; C | PayloadIM-30; C |
+|                          |  | PayloadIM-31; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | EventIM-1; M    | EventIM-2; M    |
+|                          |  | EventIM-3; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | EventIM-4; M    | EventIM-5; M    |
+|                          |  | EventIM-6; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | EventIM-7; O    | EventIM-8; M    |
+|                          |  | EventIM-9; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | EventIM-10; M   | EventIM-11; M   |
+|                          |  | EventIM-12; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-13; M   | EventIM-14; M   |
+|                          |  | EventIM-15; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-16; M   | EventIM-17; M   |
+|                          |  | EventIM-18; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-19; M   | EventIM-20; O   |
+|                          |  | EventIM-21; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-22; C   | EventIM-23; C   |
+|                          |  | EventIM-24; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-25; C   | EventIM-26; C   |
+|                          |  | EventIM-27; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-28; C   | EventIM-29; C   |
+|                          |  | EventIM-30; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-31; M   | EventIM-32; M   |
+|                          |  | EventIM-33; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-34; O   | EventIM-35; O   |
+|                          |  | EventIM-36; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-37; C   | EventIM-38; C   |
+|                          |  | EventIM-39; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-40; C   | EventIM-41; C   |
+|                          |  | EventIM-42; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-43; C   | EventIM-44; C   |
+| <b>Test purpose</b>      |  | <p>Check that:</p> <p>Continua HIS senders shall implement the Patient Identity Source actor of IHE ITI-44: Patient Identity Feed HL7 V3 in order to submit new patient identifiers to the HIS receiver or third party exchanges</p> <p>[AND]</p> <p>Continua HIS senders may implement the Patient Identity Source actor of IHE ITI-44: Patient Identity Feed HL7 V3 in order to submit new device registration to the HIS receiver or third party exchanges</p> <p>[AND]</p> <p>Message Payload and Control Act and Transmission Wrappers are based on the conformance with the IHE profile.</p> |                 |                 |
+| <b>Applicability</b>     |  | C_HRN_SEN_000 AND (C_HRN_SEN_008 OR C_HRN_SEN_009)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                 |                 |
+| <b>Other PICS</b>        |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                 |                 |
+| <b>Initial condition</b> |  | The SUT is ready to send a PIX message using SOAP 1.2 to the simulated PIXManager service or DocumentRegistry service launched in the test tool.                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                 |                 |
+| <b>Test procedure</b>    |  | 1. The HIS sender under test sends a SOAP 1.2 message containing a "Patient Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                 |                 |
+
+Record Revised" to the simulated receiver running in the test tool.
+
+2. The test tool receives the SOAP message and checks that:
+  - a. the version of the SOAP is 1.2, that is the namespace of the envelope is <http://www.w3.org/2003/05/soap-envelope>.
+  - b. The action of the transaction is  
+"urn:hl7-org:v3:PRPA\_IN201302UV02".
+  - c. The SOAP body has only one child that is a PRPA\_IN201302UV02 element with the namespace "urn:hl7-org:v3".
+3. The test tool checks the control act and transmission wrappers and the message payload as follows:
+  - a. The following optional class attributes are omitted:
+    - Message.profileId
+    - Message.responseCode
+    - Message.attachmentText
+    - Sender.telecom
+    - Receiver.telecom
+    - Device.desc
+    - Device.existenceTime.
+  - b. The following optional classes are omitted:
+    - AttentionLine
+    - RespondTo
+    - LocatedEntity
+    - scopedRole(Organization).
+  - c. id element of type II is required, that is @root and @extension attributes are present in this id element. @assigningAuthorityName attribute is not present and @Displayable attribute can be present.
+  - d. creationTime element of type TS is required, that is @value with a valid time value is present.
+  - e. If versionCode element is present, its value must be "V3PR1".
+  - f. The value of interactionId/@extension attribute is set to "PRPA\_IN201302UV02".
+  - g. sequenceNumber element of type INT can be present.
+  - h. The value of processingModeCode/@code attribute is set to "T".
+  - i. The acceptAckCode/@code attribute is set to "AL".
+  - j. Sender element is present and inside it:
+    - @typeCode attribute is present and its value is set to "SND".
+    - A device element is present and inside it:
+      - @classCode attribute is present and its value is set to "DEV"
+      - @determinerCode attribute is present and its value is set to "INSTANCE".
+      - At least one Device/id element is present, Device/id/@root is an ISO OID and Device/id/@extension does not have a value, Device/id/@assigningAuthorityName is not present and Device/id/@Displayable attribute can be present
+      - Device/name element can be present
+      - telecom element can be present
+      - manufacturerModelName element can be present
+      - softwareName element can be present.
+  - k. There is only one receiver element and inside it:
+
+- @typeCode attribute is present and its value is set to "RCV".
+- A device element is present and inside it:
+  - @classCode attribute is present and its value is set to "DEV"
+  - @determinerCode attribute is present and its value is set to "INSTANCE"
+  - At least one Device/id element is present, Device/id/@root is an ISO OID and Device/id/@extension does not have a value, Device/id/@assigningAuthorityName is not present and Device/id/@Displayable attribute can be present
+  - Device/name element can be present
+  - telecom element can be present
+  - manufacturerModelName element can be present
+  - softwareName element can be present.
+- l. If Agent element is present:
+  - @classCode attribute is present and its value is set to "AGNT".
+- m. If Organization element is present:
+  - @classCode attribute is present and its value is set to "ORG"
+  - @determinerCode attribute is present and its value is set to "INSTANCE"
+  - At least one Organization/id element is present
+  - Organization/name element can be present
+  - Organization/telecom element can be present.
+- n. ControlActProcess element is present and inside this element:
+  - The following optional class attributes are omitted:
+    - ControlActProcess.text
+    - ControlActProcess.priorityCode
+    - ControlActProcess.reasonCode.
+  - @classCode attribute is present and its value is set to "CACT".
+  - @moodCode attribute is present and its value is one of the following:
+    - "INT" – intent
+    - "RQO" – request
+    - "EVN" – event, occurrence
+    - "PRP" – proposal
+    - "RMD" – recommendation
+    - "APT" – appointment
+    - "ARQ" – appointment request
+    - "PRMS" – promise.
+  - id element can be present.
+  - code element shall be set to "PRPA\_TE201302UV02".
+  - effectiveTime element can be present.
+  - languageCode element can be present.
+  - Participation elements are not present.
+  - The reasonOf act relationship is not present.
+  - The following act relationships to the RegistrationEvent are not present:
+    - inFullfilmentOf
+    - definition
+    - subject2.
+
+- subject element is present and:
+  - @typeCode attribute is present and its value is set to "SUBJ"
+  - @contextConductionInd attribute is present and its value is set to "false".
+- RegistrationEvent element is present and:
+  - @classCode attribute is present and its value is set to "REG"
+  - @moodCode attribute is present and its value is set to "EVN"
+  - id element can be present
+  - statusCode/@code attribute is set to "active"
+  - effectiveTime element can be present, but if it is present, author/Time element must be valued with the same time expression
+  - subject1/typeCode attribute is present and its value is set to "SBJ"
+  - RegisteredRole element can be present
+  - author element can be present, but if it is present:
+    - i. @typeCode attribute is present and its value is set to "AUT".
+    - ii. @contextControlCode attribute can be present and if it is present, its value is set to "AP".
+    - iii. AssignedEntity element can be present and if it is present, it should be a person, it may be a device or organization and it shall not be a non-person living object.
+    - iv. time element can be present, but if it is valued, the RegistrationEvent/effectiveTime element must be valued with the same time expression.
+    - v. modeCode element can be present.
+  - Custodian element is present and:
+    - i. @typeCode attribute is present and its value is set to "CST".
+    - ii. @contextControlCode attribute can be present and if it is present, its value is set to "CST".
+    - iii. assignedEntity element is either an organization or a device.
+  - ReplacementOf element is not present.
+- o. A patient element is present as a child of subject1 element and in this element:
+  - @classCode attribute is present and its value is set to "PAT".
+  - At least one id element is present.
+  - statusCode element is present and its value is set to "active".
+  - confidentialityCode element can be present.
+  - veryImportantPersonCode can be present.
+  - The provider organization element is present, and:
+    - the provider organization needs to be identified by an id attribute, and at least one of address, telecommunications address, or contact person should be present
+    - id element has only a root, expressed as an ISO OID.
+    - The following roles are omitted:
+      - asPatientOfOtherProvider
+      - birthPlace
+      - guarantor
+      - guardian
+      - contactParty
+      - asMember
+
+- careGiver
+- asStudent.
+- The following participations are omitted:
+  - subjectOf (administrativeObservation)
+  - coveredPartyOf (coverage).
+- ❑ patientPerson element is present and:
+  - @classCode attribute is present and its value is set to "PSN"
+  - @determinerCode attribute is present and its value is set to "INSTANCE"
+  - One or more name elements are present
+  - More than one telecom elements can be present
+  - administrativeGenderCode element can be present
+  - birthTime element can be present
+  - deceasedInd element can be present
+  - deceasedTime element can be present
+  - multipleBirthInd element can be present
+  - multipleBirthOrderNumber element can be present
+  - addr elements can be present
+  - maritalStatusCode element can be present
+  - religiousAffiliationCode element can be present
+  - raceCode element can be present
+  - ethnicGroupCode element can be present
+  - One or more asOtherIDs elements can be present, but if it is present:
+    - i. @classCode attribute is present and its value is set to the corresponding role.
+    - ii. At least one id element is present and OtherIDs/id/@root is identical to scopingOrganization/id/@root.
+    - iii. scopingOrganization element is present and scopingOrganization/id/@extension does not have any value.
+  - PersonalRelationship element can be present and if it is present:
+    - i. @classCode attribute is present and its value is set to "PRS"
+    - ii. id element can be present
+    - iii. code element is present.
+  - Citizen element can be present and if it is present:
+    - i. @classCode attribute is present and its value is set to "CIT"
+    - ii. One or more id element can be present
+    - iii. Nation element is present and
+      - @classCode attribute is present and its value is set to "NAT"
+      - @determinerCode attribute is present and its value is set to "INSTANCE"
+      - code element is present
+      - name element can be present.
+  - Employee element can be present and if it is present:
+    - i. @classCode attribute is present and its value is set to "EMP"
+    - ii. statusCode element can be present
+    - iii. occupationCode element can be present.
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li style="text-indent: -1em; margin-left: 1em;">- LanguageCommunication can be present and if it is present: <ul style="list-style-type: none"> <li style="margin-left: 2em;">i. languageCode element is present</li> <li style="margin-left: 2em;">ii. preferenceInd element can be present.</li> </ul> </li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li style="text-indent: -1.5em; margin-left: 1.5em;">• The relationship holder of the personal relationship is restricted to being a person (using CMET COCT_MT030207UV).</li> <li style="text-indent: -1.5em; margin-left: 1.5em;">• When the patient role is scoped by a provider organization, only patient IDs assigned by the provider organization are allowed in the patient class, the root element of the patient IDs shall match the root element of the provider organization ID, and the provider organization ID shall have no extension element.</li> <li style="text-indent: -1.5em; margin-left: 1.5em;">• When any other role associated with the person class of the patient is scoped by an organization, the root element of the role IDs shall match the root element of the scoping organization ID, and the scoping organization ID shall have no extension element.</li> <li style="text-indent: -1.5em; margin-left: 1.5em;">• All steps are as specified within the test procedure above.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                 |                                                                        |                                                                                  |                  |                  |
+|-----------------|------------------------------------------------------------------------|----------------------------------------------------------------------------------|------------------|------------------|
+| <b>TP Id</b>    | TP/HIS/SEN/PIX/BV-002                                                  |                                                                                  |                  |                  |
+| <b>TP label</b> | HIS Patient Identity Management – Patient Registry Duplicates Resolved |                                                                                  |                  |                  |
+| <b>Coverage</b> | <b>Spec</b>                                                            | [ITU-T H.813]                                                                    |                  |                  |
+|                 | <b>Testable items</b>                                                  | PIMG-1; M                                                                        | PIMG-2; O        |                  |
+|                 | <b>Spec</b>                                                            | [IHE ITF PIX PDQ], Patient Identifier Cross-Reference HL7 V3 (PIXV3)             |                  |                  |
+|                 | <b>Testable items</b>                                                  | PIM-2; M                                                                         | PIM-4; M         | PIM-5; M         |
+|                 |                                                                        | PIM-6; M                                                                         | PIM-7; M         | PIM-8; M         |
+|                 |                                                                        | PIM-10; M                                                                        | PIM-11; M        | PIM-12; M        |
+|                 |                                                                        | PIM-13; M                                                                        | PIM-14; M        | PIM-15; M        |
+|                 |                                                                        | PIM-16; M                                                                        | PIM-17; M        | PIM-18; M        |
+|                 |                                                                        | PIM-19; M                                                                        | PIM-20; M        | PIM-22; M        |
+|                 |                                                                        | PIM-23; M                                                                        | PIM-24; M        | PIM-25; M        |
+|                 |                                                                        | PIM-26; M                                                                        | PIM-3; M         | PIM-21; M        |
+|                 | <b>Spec</b>                                                            | [IHE ITF PIX PDQ], Patient Identifier Cross-Reference HL7 V3 (PIXV3), Appendix E |                  |                  |
+|                 | <b>Testable items</b>                                                  | IIDataType-1; M                                                                  | IIDataType-2; C  | IIDataType-3; C  |
+|                 |                                                                        | IIDataType-17; M                                                                 | IIDataType-18; M | IIDataType-19; O |
+|                 |                                                                        | IIDataType-20; O                                                                 | IIDataType-21; M |                  |
+|                 | <b>Spec</b>                                                            | [IHE ITF PIX PDQ], Patient Identifier Cross-Reference HL7 V3 (PIXV3), Appendix O |                  |                  |
+|                 | <b>Testable items</b>                                                  | PayloadIM-1; M                                                                   | PayloadIM-2; M   | PayloadIM-3; M   |
+|                 |                                                                        | PayloadIM-4; M                                                                   | PayloadIM-5; O   | PayloadIM-6; M   |
+|                 |                                                                        | PayloadIM-7; M                                                                   | PayloadIM-8; M   | PayloadIM-9; M   |
+
+|                          |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                 |                 |
+|--------------------------|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------|
+|                          |  | PayloadIM-10; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PayloadIM-11; M | PayloadIM-12; M |
+|                          |  | PayloadIM-13; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PayloadIM-14; M | PayloadIM-15; M |
+|                          |  | PayloadIM-16; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PayloadIM-17; M | PayloadIM-18; M |
+|                          |  | PayloadIM-19; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PayloadIM-20; O | PayloadIM-21; O |
+|                          |  | PayloadIM-22; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PayloadIM-23; O | PayloadIM-24; C |
+|                          |  | PayloadIM-25; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PayloadIM-26; C | PayloadIM-27; C |
+|                          |  | PayloadIM-28; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PayloadIM-29; C | PayloadIM-30; C |
+|                          |  | PayloadIM-31; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | EventIM-1; M    | EventIM-2; M    |
+|                          |  | EventIM-3; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | EventIM-4; M    | EventIM-5; M    |
+|                          |  | EventIM-6; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | EventIM-7; O    | EventIM-8; M    |
+|                          |  | EventIM-9; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | EventIM-10; M   | EventIM-11; M   |
+|                          |  | EventIM-12; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-13; M   | EventIM-14; M   |
+|                          |  | EventIM-15; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-16; M   | EventIM-17; M   |
+|                          |  | EventIM-18; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-19; M   | EventIM-20; O   |
+|                          |  | EventIM-21; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-22; C   | EventIM-23; C   |
+|                          |  | EventIM-24; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-25; C   | EventIM-26; C   |
+|                          |  | EventIM-27; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-28; C   | EventIM-29; C   |
+|                          |  | EventIM-30; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-31; M   | EventIM-32; M   |
+|                          |  | EventIM-33; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-34; O   | EventIM-35; O   |
+|                          |  | EventIM-36; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-37; C   | EventIM-38; C   |
+|                          |  | EventIM-39; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-40; C   | EventIM-41; C   |
+|                          |  | EventIM-42; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EventIM-43; C   | EventIM-44; C   |
+| <b>Test purpose</b>      |  | <p>Check that:</p> <p>Continua HIS senders shall implement the Patient Identity Source actor of IHE ITI-44: Patient Identity Feed HL7 V3 in order to submit new patient identifiers to the HIS receiver or third party exchanges</p> <p>[AND]</p> <p>Continua HIS senders may implement the Patient Identity Source actor of IHE ITI-44: Patient Identity Feed HL7 V3 in order to submit new device registration to the HIS receiver or third party exchanges</p> <p>[AND]</p> <p>Message Payload and Control Act and Transmission Wrappers are based on the conformance with the IHE profile.</p> |                 |                 |
+| <b>Applicability</b>     |  | C_HRN_SEN_000 AND (C_HRN_SEN_008 OR C_HRN_SEN_009)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                 |                 |
+| <b>Other PICS</b>        |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                 |                 |
+| <b>Initial condition</b> |  | The SUT is ready to send a PIX message using SOAP 1.2 to the simulated PIXManager service or DocumentRegistry service launched in the test tool.                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                 |                 |
+
+|                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <p><b>Test procedure</b></p> | <ol style="list-style-type: none"> <li>1. The HIS sender under test sends a SOAP 1.2 message containing a "Patient Registry Duplicates Resolved" to the simulated receiver running in the test tool.</li> <li>2. The test tool receives the SOAP message and checks that:           <ol style="list-style-type: none"> <li>a. the version of the SOAP is 1.2, that is the namespace of the envelope is <a href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</a>.</li> <li>b. The action of the transaction is "urn:hl7-org:v3:PRPA_IN201304UV02".</li> <li>c. The SOAP body has only one child that is a PRPA_IN201304UV02 element which namespace is "urn:hl7-org:v3".</li> </ol> </li> <li>3. The test tool checks the control act and transmission wrappers and the message payload as follows:           <ol style="list-style-type: none"> <li>a. The following optional class attributes are omitted:               <ul style="list-style-type: none"> <li><input type="checkbox"/> Message.profileId</li> <li><input type="checkbox"/> Message.responseCode</li> <li><input type="checkbox"/> Message.attachmentText</li> <li><input type="checkbox"/> Sender.telecom</li> <li><input type="checkbox"/> Receiver.telecom</li> <li><input type="checkbox"/> Device.desc</li> <li><input type="checkbox"/> Device.existenceTime.</li> </ul> </li> <li>b. The following optional classes are omitted:               <ul style="list-style-type: none"> <li><input type="checkbox"/> AttentionLine</li> <li><input type="checkbox"/> RespondTo</li> <li><input type="checkbox"/> LocatedEntity</li> <li><input type="checkbox"/> scopedRole(Organization).</li> </ul> </li> <li>c. id element of type II is required, that is @root and @extension attributes are present in this id element. @assigningAuthorityName attribute is not present and @Displayable attribute can be present.</li> <li>d. creationTime element of type TS is required, that is @value with a valid time value is present.</li> <li>e. If versionCode element is present, its value must be "V3PR1".</li> <li>f. The value of interactionId/@extension attribute is set to "PRPA_IN201304UV02".</li> <li>g. sequenceNumber element of type INT can be present.</li> <li>h. The value of processingModeCode/@code attribute is set to "T".</li> <li>i. The acceptAckCode/@code attribute is set to "AL".</li> <li>j. Sender element is present and inside it:               <ul style="list-style-type: none"> <li><input type="checkbox"/> @typeCode attribute is present and its value is set to "SND".</li> <li><input type="checkbox"/> A device element is present and inside it:                   <ul style="list-style-type: none"> <li>- @classCode attribute is present and its value is set to "DEV"</li> <li>- @determinerCode attribute is present and its value is set to "INSTANCE".</li> <li>- At least one Device/id element is present, Device/id/@root is an ISO OID and Device/id/@extension does not have a value, Device/id/@assigningAuthorityName is not present and Device/id/@Displayable attribute can be present</li> <li>- Device/name element can be present</li> <li>- telecom element can be present</li> <li>- manufacturerModelName element can be present</li> <li>- softwareName element can be present.</li> </ul> </li> </ul> </li> </ol> </li> </ol> |
+|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+- k. There is only one receiver element and inside it:
+- @typeCode attribute is present and its value is set to "RCV".
+  - A device element is present and inside it:
+    - @classCode attribute is present and its value is set to "DEV"
+    - @determinerCode attribute is present and its value is set to "INSTANCE".
+    - At least one Device/id element is present, Device/id/@root is an ISO OID and Device/id/@extension does not have a value, Device/id/@assigningAuthorityName is not present and Device/id/@Displayable attribute can be present
+    - Device/name element can be present
+    - telecom element can be present
+    - manufacturerModelName element can be present
+    - softwareName element can be present.
+- l. If Agent element is present:
+- @classCode attribute is present and its value is set to "AGNT"
+- m. If Organization element is present:
+- @classCode attribute is present and its value is set to "ORG"
+  - @determinerCode attribute is present and its value is set to "INSTANCE"
+  - At least one Organization/id element is present
+  - Organization/name element can be present
+  - Organization/telecom element can be present.
+- n. ControlActProcess element is present and inside this element:
+- The following optional class attributes are omitted:
+    - ControlActProcess.text
+    - ControlActProcess.priorityCode
+    - ControlActProcess.reasonCode.
+  - @classCode attribute is present and its value is set to "CACT"
+  - @moodCode attribute is present and its value is one of the following:
+    - "INT" – intent
+    - "RQO" – request
+    - "EVN" – event, occurrence
+    - "PRP" – proposal
+    - "RMD" – recommendation
+    - "APT" – appointment
+    - "ARQ" – appointment request
+    - "PRMS" – promise.
+  - id element can be present.
+  - code element shall be set to "PRPA\_TE201304UV02".
+  - effectiveTime element can be present.
+  - languageCode element can be present.
+  - Participation elements are not present.
+  - The reasonOf act relationship is not present.
+  - The following act relationships to the RegistrationEvent are not present:
+    - inFullfilmentOf
+    - definition
+
+- subject2
+- ❑ subject element is present and:
+  - @typeCode attribute is present and its value is set to "SUBJ"
+  - @contextConductionInd attribute is present and its value is set to "false".
+- ❑ RegistrationEvent element is present and:
+  - @classCode attribute is present and its value is set to "REG"
+  - @moodCode attribute is present and its value is set to "EVN"
+  - id element can be present
+  - statusCode/@code attribute is set to "active"
+  - effectiveTime element can be present, but if it is present, author/Time element must be valued with the same time expression
+  - subject1/typeCode attribute is present and its value is set to "SBJ"
+  - RegisteredRole element can be present
+  - author element can be present, but if it is present:
+    - i. @typeCode attribute is present and its value is set to "AUT".
+    - ii. @contextControlCode attribute can be present and if it is present, its value is set to "AP".
+    - iii. AssignedEntity element can be present and if it is present, it should be a person, it may be a device or organization and it shall not be a non-person living object.
+    - iv. time element can be present, but if it is valued, the RegistrationEvent/effectiveTime element must be valued with the same time expression.
+    - v. modeCode element can be present.
+  - Custodian element is present and:
+    - i. @typeCode attribute is present and its value is set to "CST".
+    - ii. @contextControlCode attribute can be present and if it is present, its value is set to "CST".
+    - iii. assignedEntity element is either an organization or a device.
+  - ReplacementOf element is present and:
+    - i. @typeCode attribute is present and its value is set to "RPLC".
+    - ii. PriorRegistration element is present and:
+      - @classCode attribute is present and its value is set to "REG"
+      - @moodCode attribute is present and its value is set to "EVN"
+      - id element can be present
+      - statusCode element is present and its value is set to "obsolete"
+      - PriorRegisteredRole element is present and its element id is present.
+- o. A patient element is present as a child of subject1 element and in this element:
+  - ❑ @classCode attribute is present and its value is set to "PAT".
+  - ❑ At least one id element is present.
+  - ❑ statusCode element is present and its value is set to "active".
+  - ❑ All other optional elements are not present.
+  - ❑ The provider organization element can be present, and:
+    - the provider organization needs to be identified by an id attribute, and at least one of address, telecommunications address, or contact person should be present
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>- id element has only a root, expressed as an ISO OID, and it matches the root of the Patient/id element.</li> <li>❑ patientPerson element is present and: <ul style="list-style-type: none"> <li>- @classCode attribute is present and its value is set to "PSN"</li> <li>- @determinerCode attribute is present and its value is set to "INSTANCE"</li> <li>- one or more name elements are present</li> <li>- all other optional elements are not present.</li> </ul> </li> </ul>                                                                                                                                                                                                                                                                                                                                   |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The relationship holder of the personal relationship is restricted to being a person (using CMET COCT_MT030207UV).</li> <li>• When the patient role is scoped by a provider organization, only patient IDs assigned by the provider organization are allowed in the patient class, the root element of the patient IDs shall match the root element of the provider organization ID, and the provider organization ID shall have no extension element.</li> <li>• When any other role associated with the person class of the patient is scoped by an organization, the root element of the role IDs shall match the root element of the scoping organization ID, and the scoping organization ID shall have no extension element.</li> <li>• All steps are as specified within the test procedure above.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                 |                                                          |                                                                                  |                  |
+|-----------------|----------------------------------------------------------|----------------------------------------------------------------------------------|------------------|
+| <b>TP Id</b>    | TP/HIS/SEN/PIX/BV-003                                    |                                                                                  |                  |
+| <b>TP label</b> | HIS PIXV3 Query – Patient Registry Get Identifiers Query |                                                                                  |                  |
+| <b>Coverage</b> |                                                          |                                                                                  |                  |
+|                 | <b>Spec</b>                                              | [ITU-T H.813]                                                                    |                  |
+|                 | <b>Testable items</b>                                    | PIMG-3; O                                                                        |                  |
+|                 | <b>Spec</b>                                              | [IHE ITF PIX PDQ], Patient Identifier Cross-Reference HL7 V3 (PIXV3)             |                  |
+|                 | <b>Testable items</b>                                    | GetID-1; M                                                                       | GetID-5; M       |
+|                 |                                                          | GetID-8; M                                                                       | GetID-9; M       |
+|                 |                                                          | GetID-11; M                                                                      | GetID-12; M      |
+|                 |                                                          | GetID-14; M                                                                      | GetID-15; M      |
+|                 |                                                          | GetID-17; M                                                                      | GetID-18; M      |
+|                 |                                                          | GetID-20; M                                                                      | GetID-22; M      |
+|                 |                                                          | GetID-24; M                                                                      | GetID-25; M      |
+|                 |                                                          | GetID-28; M                                                                      | GetID-2; M       |
+|                 |                                                          |                                                                                  | GetID-27; M      |
+|                 | <b>Spec</b>                                              | [IHE ITF PIX PDQ], Patient Identifier Cross-Reference HL7 V3 (PIXV3), Appendix E |                  |
+|                 | <b>Testable items</b>                                    | IIDataType-1; M                                                                  | IIDataType-2; C  |
+|                 |                                                          | IIDataType-17; M                                                                 | IIDataType-18; M |
+|                 |                                                          | IIDataType-20; O                                                                 | IIDataType-21; M |
+|                 | <b>Spec</b>                                              | [IHE ITF PIX PDQ], Patient Identifier Cross-Reference HL7 V3 (PIXV3), Appendix O |                  |
+|                 | <b>Testable</b>                                          | PayloadIM-1; M                                                                   | PayloadIM-2; M   |
+|                 |                                                          |                                                                                  | PayloadIM-3; M   |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                  |                  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|------------------|
+| <b>items</b>             | PayloadIM-4; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | PayloadIM-5; O   | PayloadIM-6; M   |
+|                          | PayloadIM-7; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | PayloadIM-8; M   | PayloadIM-9; M   |
+|                          | PayloadIM-10; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | PayloadIM-11; M  | PayloadIM-12; M  |
+|                          | PayloadIM-13; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | PayloadIM-14; M  | PayloadIM-15; M  |
+|                          | PayloadIM-16; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | PayloadIM-17; M  | PayloadIM-18; M  |
+|                          | PayloadIM-19; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | PayloadIM-20; O  | PayloadIM-21; O  |
+|                          | PayloadIM-22; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | PayloadIM-23; O  | PayloadIM-24; C  |
+|                          | PayloadIM-25; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | PayloadIM-26; C  | PayloadIM-27; C  |
+|                          | PayloadIM-28; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | PayloadIM-29; C  | PayloadIM-30; C  |
+|                          | PayloadIM-31; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | QueryReqlM-1; M  | QueryReqlM-2; M  |
+|                          | QueryReqlM-3; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | QueryReqlM-4; M  | QueryReqlM-5; O  |
+|                          | QueryReqlM-6; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | QueryReqlM-7; M  | QueryReqlM-8; M  |
+|                          | QueryReqlM-9; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | QueryReqlM-10; O | QueryReqlM-11; C |
+|                          | QueryReqlM-12; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | QueryReqlM-13; C | QueryReqlM-14; C |
+|                          | QueryReqlM-15; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                  |                  |
+| <b>Test purpose</b>      | Check that:<br><br>Continua HIS senders and receivers may implement the Patient Identifier Cross-reference Consumer actor of IHE ITI-45: PIXV3 Query transaction in order to map between their local identifiers and the identifiers used for exchange<br><br>[AND]<br><br>Message Payload and Control Act and Transmission Wrappers are based on the conformance with the IHE profile.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                  |                  |
+| <b>Applicability</b>     | C_HRN_SEN_000 AND C_HRN_SEN_011                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                  |                  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                  |                  |
+| <b>Initial condition</b> | The SUT is ready to send a PIX message using SOAP 1.2 to the simulated PIXManager service launched in the test tool.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                  |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The HIS sender under test sends a SOAP 1.2 message containing a "Patient Registry Get Identifiers" query to the simulated receiver running in the test tool.</li> <li>2. The test tool receives the SOAP message and checks that: <ol style="list-style-type: none"> <li>a. the version of the SOAP is 1.2, that is the namespace of the envelope is <a href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</a>.</li> <li>b. The action of the transaction is<br/>"urn:hl7-org:v3:PRPA_IN201309UV02".</li> <li>c. The SOAP body has only one child that is a PRPA_IN201309UV02 element with the namespace "urn:hl7-org:v3".</li> </ol> </li> <li>3. The test tool checks the control act and transmission wrappers and the message payload as follows: <ol style="list-style-type: none"> <li>a. The following optional class attributes are omitted: <ul style="list-style-type: none"> <li><input type="checkbox"/> Message.profileId</li> <li><input type="checkbox"/> Message.responseCode</li> </ul> </li> </ol> </li> </ol> |                  |                  |
+
+- Message.attachmentText
+- Sender.telecom
+- Receiver.telecom
+- Device.desc
+- Device.existenceTime.
+
+b. The following optional classes are omitted:
+
+- AttentionLine
+- RespondTo
+- LocatedEntity
+- scopedRole(Organization).
+
+c. id element of type II is required, that is @root and @extension attributes are present in this id element. @assigningAuthorityName attribute is not present and @Displayable attribute can be present.
+
+d. creationTime element of type TS is required, that is @value with a valid time value is present.
+
+e. If versionCode element is present, its value must be "V3PR1".
+
+f. The value of interactionId/@extension attribute is set to "PRPA\_IN201304UV02".
+
+g. sequenceNumber element of type INT can be present.
+
+h. The value of processingModeCode/@code attribute is set to "T".
+
+i. The acceptAckCode/@code attribute is set to "AL".
+
+j. Sender element is present and inside it:
+
+- @typeCode attribute is present and its value is set to "SND".
+- A device element is present and inside it:
+  - @classCode attribute is present and its value is set to "DEV"
+  - @determinerCode attribute is present and its value is set to "INSTANCE".
+  - At least one Device/id element is present, Device/id/@root is an ISO OID and Device/id/@extension does not have a value, Device/id/@assigningAuthorityName is not present and Device/id/@Displayable attribute can be present
+  - Device/name element can be present
+  - telecom element can be present
+  - manufacturerModelName element can be present
+  - softwareName element can be present.
+
+k. There is only one receiver element and inside it:
+
+- @typeCode attribute is present and its value is set to "RCV".
+- A device element is present and inside it:
+  - @classCode attribute is present and its value is set to "DEV"
+  - @determinerCode attribute is present and its value is set to "INSTANCE".
+  - At least one Device/id element is present, Device/id/@root is an ISO OID and Device/id/@extension does not have a value, Device/id/@assigningAuthorityName is not present and Device/id/@Displayable attribute can be present
+  - Device/name element can be present
+  - telecom element can be present
+  - manufacturerModelName element can be present
+  - softwareName element can be present.
+
+l. If Agent element is present:
+
+- @classCode attribute is present and its value is set to "AGNT".
+
+m. If Organization element is present:
+
+- @classCode attribute is present and its value is set to "ORG".
+- @determinerCode attribute is present and its value is set to "INSTANCE".
+- At least one Organization/id element is present.
+- Organization/name element can be present.
+- Organization/telecom element can be present.
+
+n. ControlActProcess element is present and inside this element:
+
+- The following optional class attributes are omitted:
+  - ControlActProcess.text
+  - ControlActProcess.priorityCode
+  - ControlActProcess.reasonCode.
+- The following participations related to the ControlActProcess are not present:
+  - overseer
+  - dataEnterer
+  - informationRecipient.
+- @classCode attribute is present and its value is set to "CACT".
+- @moodCode attribute is present and its value is set to "RQO".
+- id element can be present.
+- code element shall be set to "PRPA\_TE201309UV02".
+- effectiveTime element can be present.
+- languageCode element can be present.
+- authorOrPerformer element is present and:
+  - @typeCode attribute is present and its value is set to "AUT"
+  - @contextConductionInd attribute can be present and if it is present, its value is set to "AP"
+  - time element can be present
+  - modeCode element can be present.
+- QueryByParameter element is present and:
+  - queryId element is present
+  - statusCode element is present and its attribute @code is set to "new"
+  - responsePriorityCode element is present and its attribute @code is set to "1"
+  - the optional attributes responseElementGroupId, modifyCode and executionAndDeliveryTime are not present.
+  - A parameterList element is present and:
+    - i. DataSource element can be present, but if it is present:
+      - a value element is present, the value/@root attribute is a valid ISO OID and the value/@extension attribute is not present
+      - a semanticsText element is present and its value is set to "DataSource.id"
+      - DataSource parameter provides the assigning authority identifier for a specific domain using the DataSource/value attribute
+      - DataSource/value/@extension attribute is not provided, and the DataSource/value/@root attribute contains a valid ISO
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p style="text-align: right;">OID</p> <ul style="list-style-type: none"> <li>• the value of Patient.id.root attribute matches the DataSource/value/@root attribute representing the corresponding assigning authority.</li> </ul> <p>ii. Exactly one patientIdentifier element is present and:</p> <ol style="list-style-type: none"> <li>1. Exactly one PatientIdentifier/value element is present and it is a valid ISO OID and the value/@extension attribute is valued.</li> <li>2. Exactly one semanticsText element is present and its value is set to "Patient.id".</li> </ol>                                                                                                                                           |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• When the patient role is scoped by a provider organization, only patient IDs assigned by the provider organization are allowed in the patient class, the root element of the patient IDs shall match the root element of the provider organization ID, and the provider organization ID shall have no extension element.</li> <li>• When any other role associated with the person class of the patient is scoped by an organization, the root element of the role IDs shall match the root element of the scoping organization ID, and the scoping organization ID shall have no extension element.</li> <li>• All steps are as specified within the test procedure above.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+### A.13 Group 1.11: HIS consent management (CM)
+
+|                 |                               |                                                                  |                      |               |
+|-----------------|-------------------------------|------------------------------------------------------------------|----------------------|---------------|
+| <b>TP Id</b>    | TP/HIS/SEN/CM/BV-000          |                                                                  |                      |               |
+| <b>TP label</b> | Metadata Syntactic Validation |                                                                  |                      |               |
+| <b>Coverage</b> | <b>Spec</b>                   | [IHE ITI-TF-2]                                                   |                      |               |
+|                 | <b>Testable items</b>         | ProvideScope1; M                                                 | ProvideProtocol9; M  |               |
+|                 | <b>Spec</b>                   | [ITU-T H.813], HIS Interface requirements for Consent Management |                      |               |
+|                 | <b>Testable items</b>         | ConsentSenderXDR3; M                                             | ConsentSenderXDR5; M | XDSDEMD-1; O  |
+|                 |                               | XDSDEMD-2; M                                                     | XDSDEMD-3; M         | XDSDEMD-4; M  |
+|                 |                               | XDSDEMD-5; M                                                     | XDSDEMD-6; M         | XDSDEMD-7; M  |
+|                 |                               | XDSDEMD-8; O                                                     | XDSDEMD-9; O         | XDSDEMD-10; M |
+|                 |                               | XDSDEMD-11; M                                                    | XDSDEMD-12; M        | XDSDEMD-13; M |
+|                 |                               | XDSDEMD-14; M                                                    | XDSDEMD-15; O        | XDSDEMD-16; M |
+|                 |                               | XDSDEMD-17; O                                                    | XDSDEMD-18; M        | XDSDEMD-19; M |
+|                 |                               | XDSDEMD-20; M                                                    | XDSDEMD-21; M        | XDSDEMD-22; M |
+|                 |                               | XDSDEMD-23; M                                                    | XDSDEMD-24; M        | XDSDEMD-25; O |
+|                 |                               | XDSDEMD-26; O                                                    | XDSDEMD-27; O        | XDSDEMD-28; M |
+|                 |                               | XDSDEMD-29; M                                                    | XDSDEMD-30; M        | XDSDEMD-31; M |
+|                 |                               | XDSDEMD-32; M                                                    | XDSDEMD-33; M        | XDSDEMD-34; M |
+|                 |                               | XDSDEMD-35; M                                                    | XDSDEMD-35; M        | XDSDEMD-37; M |
+|                 |                               | XDSDEMD-38; M                                                    | XDSDEMD-39; M        | XDSDEMD-40; O |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |               |               |               |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|---------------|
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | XDSDEMD-41; M | XDSDEMD-42; M | XDSDEMD-43; M |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>A Provide and Register Document Set-b transaction shall carry:</p> <ul style="list-style-type: none"> <li>- Metadata describing zero or more documents</li> <li>- Within metadata, one XDSDocumentEntry object per document</li> <li>- XDS Submission Set definition along with the linkage to new documents and references to existing documents</li> <li>- Zero or more XDS Folder definitions along with the linkage to new or existing documents</li> <li>- Zero or more documents</li> </ul> <p>[AND]</p> <p>The &lt;ihe:ProvideAndRegisterDocumentSetRequest/&gt; element is defined as:</p> <ul style="list-style-type: none"> <li>- One &lt;lcm:SubmitObjectsRequest/&gt; element that contains the submission set metadata</li> <li>- Zero or more &lt;ihe:Document/&gt; elements that contain the base64encoded data for the documents being submitted to the Document Repository. The &lt;ihe:Document/&gt; also includes the document id attribute (ihe:Document/@id) of type xsd:anyURI to match the document ExtrinsicObject id in the metadata and providing the necessary linkage</li> </ul> <p>[AND]</p> <p>The consent document transmitted by the Consent Enabled HIS sender shall contain the same Patient Identifier as the HIS measurement message(s).</p> |               |               |               |
+| <b>Applicability</b>      | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_007                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |               |               |               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |               |               |               |
+| <b>Initial condition</b>  | The SUT is ready to send an XDS.b submission set by XDR to the test tool. This submission set contains one patient consent document.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |               |               |               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The HIS sender under test sends a "Provide and Register document Set-b Request" message to the test tool.</li> <li>2. Check there is only one &lt;ProvideAndRegisterDocumentSetRequest/&gt; element and that it contains: <ol style="list-style-type: none"> <li>a. only one &lt;lcm:SubmitObjectsRequest/&gt; element that contains: <ul style="list-style-type: none"> <li>o an XDSDocumentEntry (ExtrinsicObject) element for each document;</li> <li>o an XDS submission set definition along with the linkage to new documents and references to existing documents (RegistryPackage element);</li> <li>o zero or more XDS folder definitions along with the linkage to new or existing documents;</li> <li>o zero or more &lt;ihe:Document/&gt; elements.</li> </ul> </li> </ol> </li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                           |               |               |               |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• All steps are as specified within the test procedure above.</li> <li>• The received XDS.b message conforms to the XSD template that describes the XML format structure; this implies that all mandatory elements shall be present, that recommended elements should be present and that optional elements may be present.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |               |               |               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |               |               |               |
+
+|                 |                              |                                                                  |                      |  |
+|-----------------|------------------------------|------------------------------------------------------------------|----------------------|--|
+| <b>TP Id</b>    | TP/HIS/SEN/CM/BV-001         |                                                                  |                      |  |
+| <b>TP label</b> | Consent Directive Validation |                                                                  |                      |  |
+| <b>Coverage</b> | <b>Spec</b>                  | [ITU-T H.813], HIS Interface requirements for Consent Management |                      |  |
+|                 | <b>Testable</b>              | ConsentSenderXDR1; M                                             | ConsentSenderXDR2; M |  |
+
+|  |                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                 |                |
+|--|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----------------|
+|  | <b>items</b>          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                 |                |
+|  | <b>Spec</b>           | [HL7 CDA IG]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                 |                |
+|  | <b>Testable items</b> | CONF-CD-1; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | CONF-CD-2; M    | CONF-CD-2.2; M |
+|  |                       | CONF-CD-3; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | CONF-CD-4; O    | CONF-CD-4.2; O |
+|  |                       | CONF-CD-4.3; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | CONF-CD-4.4; O  | CONF-CD-5; O   |
+|  |                       | CONF-CD-6; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | CONF-CD-7; O    | CONF-CD-8; O   |
+|  |                       | CONF-CD-9; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | CONF-CD-10; M   | CONF-CD-11; M  |
+|  |                       | CONF-CD-12; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | CONF-CD-12.2; O | CONF-CD-13; M  |
+|  |                       | CONF-CD-14; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | CONF-CD-15; M   | CONF-CD-16; M  |
+|  |                       | CONF-CD-17; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | CONF-CD-18; M   | CONF-CD-19; R  |
+|  |                       | CONF-CD-20; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | CONF-CD-21; O   | CONF-CD-22; R  |
+|  |                       | CONF-CD-23; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | CONF-CD-24; O   | CONF-CD-25; M  |
+|  |                       | CONF-CD-26; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | CONF-CD-27; M   | CONF-CD-28; O  |
+|  |                       | CONF-CD-29; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | CONF-CD-30; R   | CONF-CD-31; O  |
+|  |                       | CONF-CD-32; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | CONF-CD-33; O   | CONF-CD-34; M  |
+|  |                       | CONF-CD-35; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | CONF-CD-36; R   | CONF-CD-37; O  |
+|  |                       | CONF-CD-38; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | CONF-CD-39; O   | CONF-CD-41; C  |
+|  |                       | CONF-CD-42; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                 |                |
+|  | <b>Test purpose</b>   | <p>Check that:</p> <p>A document conforming to the CDA R2 General Header template shall include the ClinicalDocument/templateId “2.16.840.1.113883.10.20.3”</p> <p>[AND]</p> <p>ClinicalDocument/templateId element shall be present with the value “2.16.840.1.113883.3.445.1”</p> <p>[AND]</p> <p>Each Privacy Consent Directive must specify a healthcare client whose IIHI is affected by the privacy consent directive.</p> <p>[AND]</p> <p>ClinicalDocument/author element shall be present and specify a templateId if “2.16.840.1.113883.3.445.2”</p> <p>[AND]</p> <p>ClinicalDocument/author/functionCode/ may be present to specify function/relationship of the author to the client who is the record target. This element may be used to specify the client’s relationship to the Substitute Decision Maker – if one is involved in the creation of the privacy consent directive</p> <p>[AND]</p> <p>Information Recipient is used to specify the recipients of the Privacy Consent Directive. In the case of consultations and referrals, the Privacy Consent Directive recipient may be the same person/entity as the intended recipient of the client IIHI that is disclosed as a result of the permission granted using the Privacy Consent Directive.</p> <p>[AND]</p> |                 |                |
+
+The legalAuthenticator is as defined in CDA. For a Privacy Consent Document this element may be either the client or their Substitute Decision Maker. If necessary, the Signatures section may provide the signature associated with the consentor's signature.
+
+[AND]
+
+In some cases, a Privacy Consent Document may identify and record the signature of a person who witnessed the consentor's signature. This may occur if the authenticator/consenter makes a mark instead of a signature.
+
+[AND]
+
+ClinicalDocument/documentationOf/serviceEvent/ element with a templateId of "2.16.840.1.113883.3.445.3" may be present
+
+[AND]
+
+ClinicalDocument/documentationOf/serviceEvent/id element may be present
+
+[AND]
+
+ClinicalDocument/documentationOf/serviceEvent/effectiveTime element may be present
+
+[AND]
+
+ClinicalDocument/documentationOf/serviceEvent/effectiveTime/low/@value element may be present. It may be different than the value of the ClinicalDocument/documentationOf/serviceEvent/effectiveTime/@value and represents the first time the Privacy Consent Directive takes effect
+
+[AND]
+
+ClinicalDocument/documentationOf/serviceEvent/effectiveTime/high/@value element may be present to specify the date/time when the Privacy Consent Directives expires
+
+[AND]
+
+ClinicalDocument/documentationOf/serviceEvent/code/@code attribute shall be present and indicates the OID of the externally identified and defined privacy policy corresponding to the "Privacy Policy Acknowledgement Document"
+
+[AND]
+
+ClinicalDocument/documentationOf/serviceEvent/code/@codeSystem attribute shall be present and indicates the assigning authority of the externally identified and defined privacy policy corresponding to the "Privacy Policy Acknowledgement Document"
+
+[AND]
+
+ClinicalDocument/documentationOf/serviceEvent/code/@codeSystemName attribute may be present and be a descriptive text of the privacy policy being acknowledged.
+
+[AND]
+
+A Privacy Consent Directive may replace a previous (revoked) or expired Privacy Consent Directive.
+
+[AND]
+
+A Privacy Consent Directive shall have a structuredBody element
+
+[AND]
+
+A Privacy Consent Directive shall contain a Privacy Consent Directive Details section
+
+[AND]
+
+This section shall include the templateId for the Privacy Consent Directive section with the value "2.16.840.1.113883.3.445.17" and a title of "Privacy Consent Directive Details".
+
+[AND]
+
+This section shall include an entry element with templateId of "2.16.840.1.113883.3.445.4" and a typeCode of "COMP" to organize the structure of a Privacy Consent Directive entry.
+
+[AND]
+
+This entry element shall include an act element with templateId of "2.16.840.1.113883.3.445.5" and a moodCode of "DEF" to specify the execution of a Privacy Consent Directive.
+
+[AND]
+
+The act element shall include a code element to specify the purpose of use for which the privacy consent is applicable
+
+[AND]
+
+This section should include one or more entry/act/informant/[`@typeCode='CST'`] elements with a templateId of “2.16.840.1.113883.3.445.6” to represent the custodian of the referenced IIHI. This may be different than the custodian of the Privacy Consent Directive document identified in the header. Note, if the informant is different from the custodian of the IIHI, then the informant is re-disclosing, which typically is not allowed.
+
+[AND]
+
+This section should include one or more entry/act/participant/[`@typeCode='IRCP'`] elements with a templateId of “2.16.840.1.113883.3.445.7” to represent the provider organization or person intended to use, access, collect information as allowed or prevented by the action specified in this privacy consent directive.
+
+[AND]
+
+The participant element may include participantRole/codeSystem specification of “2.16.840.1.113883.11.19682” corresponding to the receiving provider's role [DYNAMIC].
+
+[AND]
+
+The participantRole element should include playingEntity element corresponding to the organization or provider intended to receive the information specified in this Privacy Consent Directive document.
+
+[AND]
+
+This section should include one or more entry/act/participant/ elements to represent the provider organization or person intended to use, access, collect information, as allowed or prevented by the action specified in this privacy consent directive.
+
+[AND]
+
+This section may include an entry/act/entryRelationship with a templateId of “2.16.840.1.113883.3.445.8” to represent the action allowed and problem associated with the information allowed by the Privacy Consent Directive.
+
+[AND]
+
+This entryRelationship shall include an act element with default `classCode="ACT"` and `moodCode="DEF"`.
+
+[AND]
+
+This act element should include a `@negationInd` attribute with a default value of “false” indicating that the action specified is enabled, and a value of “true” if the action is not allowed by the Privacy Consent Directive. When the `negationInd` attribute is not transmitted, the receiver must assume the default (specified action is enabled).
+
+[AND]
+
+The act element shall include a code element with default of `codeSystem="2.16.840.1.113883.5.4"` to specify the Privacy Consent Directive operation or action [DYNAMIC].
+
+[AND]
+
+This section may include an entry/act/entryRelationship/ with a templateId of “2.16.840.1.113883.3.445.9” to represent the entire set of protected information (IIHI) including specific attributes of that information (e.g., category type, related diagnosis, sensitivity/confidentiality).
+
+[AND]
+
+The observation element should include one or more organizer/component/observation/[`@moodCode='DEF'`]/ elements with a templateId of “2.16.840.1.113883.3.445.10” to specify each information type (IIHI) included in the authorization contained in the Privacy Consent Directive document.
+
+[AND]
+
+The observation element should include a code element to specify the code corresponding to the information type (IIHI) included in the authorization contained in the Privacy Consent Directive document.
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | <p>[AND]</p> <p>The observation element may include a precondition[@typeCode="PRCN"]/ element with a templateId of “2.16.840.1.113883.3.445.11” to specify the diagnosis or problem associated with the information.</p> <p>[AND]</p> <p>The observation element may include a precondition[@typeCode="PRCN"]/ element with a templateId of “2.16.840.1.113883.3.445.12” to specify the sensitivity of the protected information (IIHI) specified in Privacy Consent Directive.</p> <p>[AND]</p> <p>This section may include an entry/act/entryRelationship with a templateId of “2.16.840.1.113883.3.445.13” to represent references to Privacy Policies on which the Privacy Consent Directive is based along with the information recipient Obligation.</p> <p>[AND]</p> <p>The component element shall include an act/code element to specify the Privacy Policy or regulation that is basis for requesting the authorizations specified in the Privacy Consent Directive.</p> <p>[AND]</p> <p>The component element may include a precondition element with a templateId of “2.16.840.1.113883.3.445.14” and an element of @typeCode="PRCN" to specify any additional obligations imposed on the recipient of the IIHI referenced in the Privacy Consent Directive.</p> <p>[AND]</p> <p>The component element should include a criterion[classCode="OBS"]/code element to specify the coded obligations imposed on the recipient of the IIHI referenced in the Privacy Consent Directive.</p> <p>[AND]</p> <p>This section may include an entry/act/entryRelationship with a templateId of “2.16.840.1.113883.3.445.15” to include a scanned image of the paper-based Privacy Consent Directive.</p> <p>[AND]</p> <p>The entryRelationship element should include an observationMedia[@classCode="OBS"] element to embed a scanned document representation of the Privacy Consent Directive including required signatures.</p> <p>[AND]</p> <p>This section may include an entry/act/entryRelationship with a templateId of “2.16.840.1.113883.3.445.16” to represent an alternative representation of the Privacy Consent Directive (e.g.,ODRL, XrML, XACML).</p> <p>[AND]</p> <p>If included, this section shall include the templateId for the Signatures section “2.16.840.1.113883.3.445.18” and a title of “Signatures”.</p> <p>[AND]</p> <p>This section may include the entry/observationMedia for each signature (e.g.,legalAuthenticator, authenticator) or a scanned version of the entire privacy consent directive form including the signatures.</p> |
+| <b>Applicability</b>     | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_007                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Initial condition</b> | The SUT is ready to send an XDS.b submission set by XDR to the test tool. This submission set contains one patient consent document.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The HIS sender under test sends a "Provide and Register document Set-b Request" message containing a CDA referenced in its body.</li> <li>Check the following elements of the clinical document sent by the HIS sender under</li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+test:
+
+- a. A templateId = "2.16.840.1.113883.10.20.3".
+- b. Another templateId = "2.16.840.1.113883.3.445.1".
+- c. recordTarget element is present.
+- d. author element:
+  - o /templateId = "2.16.840.1.113883.3.445.2"
+  - o /functionCode may be present.
+- e. intendedRecipient element: the "Privacy Consent Directive" recipient may be the same person/entity as the intended recipient.
+- f. legalAuthenticator element may be either the client or their "Substitute Decision Maker" and if necessary, the signatures section may provide the signature associated with the consenter's signature.
+- g. authenticator element may be present.
+- h. documentationOf/serviceEvent/ element with a templateId of "2.16.840.1.113883.3.445.3" may be present and within this element:
+  - o id element may be present
+  - o effectiveTime element may be present
+  - o effectiveTime/low/@value element may be present
+  - o effectiveTime/high/@value element may be present
+  - o code/@code attribute is present
+  - o code/@codeSystem attribute is present
+  - o code/@codeSystemName attribute may be present.
+- i. relatedDocument element may be present.
+- j. component/structuredBody element is present and within this element:
+  - o component/section with templateId = "2.16.840.1.113883.3.445.17" is present
+  - o component/section/title = Privacy Consent Directive Details
+  - o component/section/entry is present
+  - o component/section/entry/templateId = "2.16.840.1.113883.3.445.4"
+  - o component/section/entry/@typeCode = "COMP"
+  - o component/section/entry/act/templateId = "2.16.840.1.113883.3.445.5"
+  - o component/section/entry/act/@moodCode = "DEF"
+  - o component/section/entry/act/code is present
+  - o component/section/entry/act/informant/@typeCode = 'CST'
+  - o one or more component/section/entry/act/participant should be present.
+  - o one or more component/section/entry/act/participant/@typeCode = 'IRCP' and component/section/entry/act/participant/templateId = "2.16.840.1.113883.3.445.7" should be present.
+  - o component/section/entry/act/participant/participantRole/code/@codeSystem = "2.16.840.1.113883.11.19682" may be present.
+  - o component/section/entry/act/participant/participantRole should include a playingEntity element.
+  - o component/section/entry/act/entryRelationship may be present with a templateId = "2.16.840.1.113883.3.445.8" and if it is present:
+    - /act element is present with classCode = "ACT" and moodCode = "DEF"
+    - /act/@negationId with a value of "false" or "true" should be present
+    - /act/code/@codeSystem = "2.16.840.1.113883.5.4" is present.
+  - o component/section/entry/act/entryRelationship may be present with a templateId = "2.16.840.1.113883.3.445.9" and if it is present:
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>- it should include one or more<br/>/organizer/component/observation/@moodCode = 'DEF' with a templateId = "2.16.840.1.113883.3.445.10"</li> <li>- /organizer/component/observation should include a code element</li> <li>- /organizer/component/observation may include a precondition/@typeCode = "PRCN" element with a templateId = "2.16.840.1.113883.3.445.11"</li> <li>- /organizer/component/observation may include a precondition/@typeCode = "PRCN" element with a templateId = "2.16.840.1.113883.3.445.12".</li> <li>o component/section/entry/act/entryRelationship may be present with a templateId = "2.16.840.1.113883.3.445.13" and if it is present: <ul style="list-style-type: none"> <li>- /act/code is present</li> <li>- /act/precondition may be present with templateId = "2.16.840.1.113883.3.445.14" and @typeCode = "PRCN"</li> <li>- /act/precondition/criterion/[@classCode = "OBS"]/code should be present.</li> </ul> </li> <li>o component/section/entry/act/entryRelationship may be present with a templateId = "2.16.840.1.113883.3.445.15" and if it is present: <ul style="list-style-type: none"> <li>- /observationMedia/@classCode = "OBS" should be present</li> </ul> </li> <li>o component/section/entry/act/entryRelationship may be present with a templateId = "2.16.840.1.113883.3.445.16"</li> <li>o component/section with templateId = "2.16.840.1.113883.3.445.18" and a title of "Signatures" may be present, and if present this section may include the entry/observationMedia for each signature.</li> </ul> |
+| <b>Pass/Fail criteria</b> | All steps are as specified within the test procedure above.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                          |                                                                                                                                                                                                      |                                                |                  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|------------------|
+| <b>TP Id</b>             | TP/HIS/SEN/CM/BV-002                                                                                                                                                                                 |                                                |                  |
+| <b>TP label</b>          | HIS Repository Retrieve Document Set Transaction – Protocol Requirements                                                                                                                             |                                                |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                          | [IHE ITI-TF-2], Volume 2b, Transactions Part B |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                | ProtocolReq_2; M                               | ProtocolReq_4; M |
+|                          | <b>Spec</b>                                                                                                                                                                                          | [IHE ITI-TF-2], Volume 2x, Appendix V          |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                | IHE-WSA101; M                                  |                  |
+| <b>Test purpose</b>      | Check that:<br>Continua HIS senders implement SOAP 1.2 for Retrieve Document Set transaction<br>[AND]<br>Continua HIS senders implement MTOM with XOP Encoding for Retrieve Document Set transaction |                                                |                  |
+| <b>Applicability</b>     | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012                                                                                                                                                    |                                                |                  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                      |                                                |                  |
+| <b>Initial condition</b> | The SUT (document repository) is ready to receive a "Retrieve Document Set Request" from the test tool (simulated document consumer).                                                                |                                                |                  |
+| <b>Test procedure</b>    | 1. The test tool sends a "Retrieve Document Set Request" to the HIS sender under test.<br>2. The HIS sender under test processes the request and sends a "Retrieve Document Set                      |                                                |                  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>Response" to the test tool.</p> <p>3. The test tool checks that:</p> <ol style="list-style-type: none"> <li>a. the message received use SOAP 1.2.</li> <li>b. The message received use MTOM with XOP encoding.</li> <li>c. All &lt;wsa:Action&gt; elements shall have the mustUnderstand attribute set (mustUnderstand='1').</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The "Retrieve Document Set Response" shall use SOAP 1.2.</li> <li>• The "Retrieve Document Set Response" shall use MTOM with XOP encoding.</li> <li>• All steps are as specified within the test procedure above.</li> </ul>                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                            |
+
+|                 |                                                                                            |                                                                  |                              |                              |                |
+|-----------------|--------------------------------------------------------------------------------------------|------------------------------------------------------------------|------------------------------|------------------------------|----------------|
+| <b>TP Id</b>    | TP/HIS/SEN/CM/BV-003                                                                       |                                                                  |                              |                              |                |
+| <b>TP label</b> | HIS Repository Retrieve Document Set Transaction – Consent Document Retrieval successfully |                                                                  |                              |                              |                |
+| <b>Coverage</b> | <b>Spec</b>                                                                                | [ITU-T H.813], HIS Interface requirements for Consent Management |                              |                              |                |
+|                 | <b>Testable items</b>                                                                      | ConsentSenderXDSb-1; M                                           | ConsentSenderXDSb-3; M       | ConsentSenderXDSb-5; M       |                |
+|                 |                                                                                            | ConsentSenderXDSb-6; M                                           |                              |                              |                |
+|                 | <b>Spec</b>                                                                                | [IHE ITI-TF-2], Volume 2b, Transactions Part B                   |                              |                              |                |
+|                 | <b>Testable items</b>                                                                      | DocSetRequestActions_1; M                                        | DocSetResponseSemantics_1; M | DocSetResponseSemantics_2; M |                |
+|                 |                                                                                            | DocSetResponseSemantics_3; M                                     | DocSetResponseSemantics_4; M | DocSetResponseSemantics_5; M |                |
+|                 |                                                                                            | DocSetResponseSemantics_6; M                                     | DocSetResponseSemantics_7; M | DocSetResponseActions_1; M   |                |
+|                 |                                                                                            | DocSetResponseActions_2; M                                       | ProtocolReq_9; M             | ProtocolReq_10; M            |                |
+|                 |                                                                                            | ProtocolReq_11; M                                                | ProtocolReq_12; M            | ProtocolReq_14; M            |                |
+|                 |                                                                                            | ProtocolReq_15; M                                                | ProtocolReq_16; M            |                              |                |
+|                 |                                                                                            | <b>Spec</b>                                                      | [HL7 CDA IG]                 |                              |                |
+|                 |                                                                                            | <b>Testable items</b>                                            | CONF-CD-1; M                 | CONF-CD-2; M                 | CONF-CD-2.2; M |
+|                 | CONF-CD-3; M                                                                               |                                                                  | CONF-CD-4; O                 | CONF-CD-4.2; O               |                |
+|                 | CONF-CD-4.3; O                                                                             |                                                                  | CONF-CD-4.4; O               | CONF-CD-5; O                 |                |
+|                 | CONF-CD-6; O                                                                               |                                                                  | CONF-CD-7; O                 | CONF-CD-8; O                 |                |
+|                 | CONF-CD-9; O                                                                               |                                                                  | CONF-CD-10; M                | CONF-CD-11; M                |                |
+|                 | CONF-CD-12; O                                                                              |                                                                  | CONF-CD-12.2; O              | CONF-CD-13; M                |                |
+|                 | CONF-CD-14; M                                                                              |                                                                  | CONF-CD-15; M                | CONF-CD-16; M                |                |
+|                 | CONF-CD-17; M                                                                              |                                                                  | CONF-CD-18; M                | CONF-CD-19; R                |                |
+|                 | CONF-CD-20; R                                                                              |                                                                  | CONF-CD-21; O                | CONF-CD-22; R                |                |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |               |               |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|
+|                          | CONF-CD-23; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | CONF-CD-24; O | CONF-CD-25; M |
+|                          | CONF-CD-26; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | CONF-CD-27; M | CONF-CD-28; O |
+|                          | CONF-CD-29; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | CONF-CD-30; R | CONF-CD-31; O |
+|                          | CONF-CD-32; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | CONF-CD-33; O | CONF-CD-34; M |
+|                          | CONF-CD-35; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | CONF-CD-36; R | CONF-CD-37; O |
+|                          | CONF-CD-38; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | CONF-CD-39; O | CONF-CD-41; C |
+|                          | CONF-CD-42; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |               |               |
+| <b>Test purpose</b>      | Check that:<br>Continua HIS sender returns with the consent document requested by the Test Tool<br>[AND]<br>Continua HIS sender response conforms with IHE specifications                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |               |               |
+| <b>Applicability</b>     | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |               |               |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |               |               |
+| <b>Initial condition</b> | The SUT (document repository) is ready to receive a "Retrieve Document Set Request" from the test tool (simulated document consumer).<br>[AND]<br>The SUT (document repository) stores at least one consent document in its repository.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |               |               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The test tool sends a well-formed "Retrieve Document Set Request" to the HIS sender under test requesting a consent document stored in the SUT repository.</li> <li>2. The HIS sender under test processes the request and sends a "Retrieve Document Set Response" to the test tool.</li> <li>3. The test tool checks that: <ol style="list-style-type: none"> <li>a. If the request includes a homeCommunityId, the response shall include a homeCommunityId and its value shall be equal to the request homeCommunityId value.</li> <li>b. The element repositoryUniqueId shall be present in the response and its value shall be equal to the value of the request repositoryUniqueId element.</li> <li>c. The element documentUniqueId shall be present in the response and its value shall be equal to the value of the request documentUniqueId element.</li> <li>d. The response includes a document in base64binary encoded format.</li> <li>e. The mimeType element of the retrieved document shall exist in the response.</li> <li>f. The /ClinicalDocument/id@root of the consent document retrieved shall be equal to the documentUniqueId of the request.</li> <li>g. The &lt;ihe:RetrieveDocumentResponse/&gt; element shall include a /ihe:RetrieveDocumentSetResponse/rs:RegistryResponse element.</li> <li>h. The &lt;ihe:RetrieveDocumentResponse/&gt; element may include an optional sequence of &lt;ihe:DocumentResponse/&gt; elements.</li> <li>i. If a homeCommunityId is present in the request for the document, the RetrieveDocumentResponse element for the document shall include an &lt;ihe:HomeCommunityId/&gt; and its value shall be equal to the value of the homeCommunityId element of the request for the document.</li> <li>j. Each &lt;ihe:DocumentResponse/&gt; element shall include an &lt;ihe:RepositoryUniqueId/&gt; and its value shall be equal to the value of the /RetrieveDocumentSetRequest/DocumentRequest /RepositoryUniqueId of the request for the document.</li> <li>k. Each &lt;ihe:DocumentResponse/&gt; element shall include an &lt;ihe:DocumentUniqueId/&gt; and its value shall be equal to the value of the</li> </ol> </li> </ol> |               |               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>/RetrieveDocumentSetRequest/DocumentRequest /DocumentUniqueId of the request for the document.</p> <ul style="list-style-type: none"> <li>l. Each &lt;ihe:DocumentResponse/&gt; element shall include an &lt;ihe:Document/&gt; containing the retrieved document in base64binary encoded format.</li> <li>m. Each &lt;ihe:DocumentResponse/&gt; element shall include an &lt;ihe:mimeType/&gt; containing the MIME type of the retrieved document.</li> <li>n. The /RetrieveDocumentSetResponse/rs:RegistryResponse/@status attributes provide the overall status of the request which shall contain the value: urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success.</li> <li>o. For each document requested in a /RetrieveDocumentSetRequest/DocumentRequest element, if a warning is reported when retrieving the document, then a /RetrieveDocumentSetResponse/rs:RegistryResponse/rs:RegistryErrorList/ rs:RegistryError element shall be returned with: <ul style="list-style-type: none"> <li>i. @severity is urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Warning</li> <li>ii. @errorCode is specified</li> <li>iii. @codeContext contains the warning message</li> <li>iv. @location contains the DocumentUniqueId of the document requested.</li> </ul> </li> <li>p. For each document requested in a /RetrieveDocumentSetRequest/DocumentRequest element, if a warning is reported when retrieving the document, then the document shall be returned in an instance of /RetrieveDocumentSetResponse/DocumentResponse/Document as base64binary encoded data.</li> <li>q. For each document requested in a /RetrieveDocumentSetRequest/DocumentRequest element, if the document is successfully retrieved (without warning) then no /RetrieveDocumentSetResponse/rs:RegistryResponse/rs:RegistryErrorList/ rs:RegistryError element shall be present and a /RetrieveDocumentSetResponse/DocumentResponse/Document element shall be returned containing the document as base64binary encoded data.</li> <li>r. The /RetrieveDocumentSetResponse/rs:RegistryResponse/ rs:ResponseSlotList element is not present.</li> <li>s. The /RetrieveDocumentSetResponse/rs:RegistryResponse /@requestId attribute is not present.</li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The "Retrieve Document Set Response" with the consent document requested in base64binary encoded format shall be returned in response.</li> <li>• All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                      |                                                                                                                                                                                                 |                                                |                           |                              |
+|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|---------------------------|------------------------------|
+| <b>TP Id</b>         | TP/HIS/SEN/CM/BV-004                                                                                                                                                                            |                                                |                           |                              |
+| <b>TP label</b>      | HIS Repository Retrieve Document Set Transaction – Consent Document Retrieval failure                                                                                                           |                                                |                           |                              |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                     | [IHE ITI-TF-2], Volume 2b, Transactions Part B |                           |                              |
+|                      | <b>Testable items</b>                                                                                                                                                                           | DocSetRequestActions_1; M                      | DocSetRequestActions_2; M | DocSetResponseSemantics_8; M |
+|                      |                                                                                                                                                                                                 | ProtocolReq_11; M                              | ProtocolReq_13; M         |                              |
+| <b>Test purpose</b>  | Check that:<br>The SUT (Document Repository) returns a failure to the request made by the Test Tool<br>[AND]<br>The SUT (Document Repository) failure response conforms with IHE specifications |                                                |                           |                              |
+| <b>Applicability</b> | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012                                                                                                                                               |                                                |                           |                              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Initial condition</b>  | <p>The SUT (document repository) is ready to receive a "Retrieve Document Set Request" from the test tool (simulated document consumer).</p> <p>[AND]</p> <p>The SUT (document repository) responds with a failure when requested for a specific documentUniqueId (PIXIT I_HRN_SEN_008) (because it is not present in the repository, for example).</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The test tool sends a "Retrieve Document Set Request" to the HIS sender under test requesting a consent document with documentUniqueId equal to PIXIT I_HRN_SEN_008.</li> <li>2. The HIS sender under test processes the request and sends a "Retrieve Document Set Response" to the test tool.</li> <li>3. The test tool checks that: <ol style="list-style-type: none"> <li>a. the response contains error codes.</li> <li>b. The /RetrieveDocumentSetResponse/rs:RegistryResponse/@status attributes provide the overall status of the request which shall contain the value:<br/>urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure</li> <li>c. For each document requested in a /RetrieveDocumentSetRequest/DocumentRequest element, if an error is reported when retrieving a document, then a /RetrieveDocumentSetResponse/rs:RegistryResponse/rs:RegistryErrorList/rs:RegistryError element shall be returned with: <ol style="list-style-type: none"> <li>i. @severity is urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error</li> <li>ii. @errorCode is specified</li> <li>iii. @codeContext contains the error message</li> <li>iv. @location contains the DocumentUniqueId of the document requested.</li> </ol> </li> <li>d. No RetrievedDocumentSetResponse/DocumentResponse element shall be returned.</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• A failed "Retrieve Document Set Response" shall be returned.</li> <li>• No document shall be returned in the "Retrieve Document Set Response".</li> <li>• All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                     |                                                                                                                                                                                                                                                                                                                                                       |                                                |               |                  |
+|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|---------------|------------------|
+| <b>TP Id</b>        | TP/HIS/SEN/CM/BV-005                                                                                                                                                                                                                                                                                                                                  |                                                |               |                  |
+| <b>TP label</b>     | HIS Repository Retrieve Document Set Transaction – WSDL Requirements                                                                                                                                                                                                                                                                                  |                                                |               |                  |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                           | [IHE ITI-TF-2], Volume 2b, Transactions Part B |               |                  |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                 | ProtocolReq_1; M                               |               | ProtocolReq_7; M |
+|                     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                           | [IHE ITI-TF-2], Volume 2x, Appendix V          |               |                  |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                 | Namespaces; M                                  | IHE-WSP201; R | IHE-WSP205; M    |
+|                     |                                                                                                                                                                                                                                                                                                                                                       | IHE-WSP207; M                                  | IHE-WSP208; M | IHE-WSP211; M    |
+| <b>Test purpose</b> | Check that:<br>Retrieve Document Set transaction of the WSDL definition of the SUT (Document Repository) imports (xsd:import) the following types: in the /definitions/types section:<br>namespace="urn:ihe:iti:xds-b:2007", schema="IHEXDS.xsd"<br><p>[AND]</p> In the Retrieve Document Set transaction of the WSDL definition of the SUT (Document |                                                |               |                  |
+
+Repository) the /definitions/message/part/@element attribute of the Retrieve Document Set Request message shall be defined as "ihe:RetrieveDocumentSetRequest"
+
+[AND]
+
+In the Retrieve Document Set transaction of the WSDL definition of the SUT (Document Repository) the /definitions/message/part/@element attribute of the Retrieve Document Set Response message shall be defined as "ihe:RetrieveDocumentSetResponse"
+
+[AND]
+
+In the Retrieve Document Set transaction of the WSDL definition of the SUT (Document Repository) the /definitions/portType/operation/input/@wsaw:Action attribute for the Retrieve Document Set Request message shall be defined as "urn:ihe:iti:2007:RetrieveDocumentSet"
+
+[AND]
+
+In the Retrieve Document Set transaction of the WSDL definition of the SUT (Document Repository) the /definitions/portType/operation/output/@wsaw:Action attribute for the Retrieve Document Set Response message shall be defined as "urn:ihe:iti:2007:RetrieveDocumentSetResponse"
+
+[AND]
+
+In the Retrieve Document Set transaction of the WSDL definition of the SUT (Document Repository) the /definitions/binding/operation/soap12:operation/@soapAction attribute shall be defined as "urn:ihe:iti:2007:RetrieveDocumentSet"
+
+[AND]
+
+The WSDL definition of the SUT (Document Repository) uses the following namespaces:
+
+| Prefix               | Namespace                                 | Specification                                                  |
+|----------------------|-------------------------------------------|----------------------------------------------------------------|
+| wsdl<br>(or default) | http://schemas.xmlsoap.org/wsdl/          | WSDL 1.1 binding for SOAP 1.1<br>WSDL 1.1 binding for SOAP 1.2 |
+| wsoap12              | http://schemas.xmlsoap.org/wsdl/soap12/   | WSDL 1.1 binding for SOAP 1.2                                  |
+| wsa                  | http://www.w3.org/2005/08/addressing      | WSA 1.0 - Core                                                 |
+| wsaw                 | http://www.w3.org/2006/05/addressing/wsdl | WSA 1.0 - WSDL binding*                                        |
+| soap12               | http://www.w3.org/2003/05/soap-envelope   | SOAP 1.2                                                       |
+| xsd                  | http://www.w3.org/2001/XMLSchema          | XML Schema                                                     |
+| xsi                  | http://www.w3.org/2001/XMLSchema-instance | XML Schema                                                     |
+
+[AND]
+
+The WSDL definition of the SUT (Document Repository) should 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.x binding -> {NAME}\_Binding\_Soap1x
+
+SOAP 1.x port -> {NAME}\_Port\_Soap1x
+
+[AND]
+
+The WSDL definition of the SUT (Document Repository) shall define two WSDL messages for each request-response transaction
+
+[AND]
+
+The WSDL definition of the SUT (Document Repository) shall include an attribute wsaw:Action for each input and output message defined in the WSDL portType operation
+
+|                          | <p>[AND]</p> <p>All operations defined in the WSDL definition of the SUT (Document Repository) shall use wsdl:operation/wsdl:input/@wsaw:Action = "urn:ihe:{Domain}:{Year}:{Transaction name}" and wsdl:operation/wsdl:output/@wsaw:Action = "urn:ihe:{Domain}:{Year}:{Transaction name}Response"</p> <p>[AND]</p> <p>In the WSDL definition of the SUT (Document Repository), 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</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                                    |           |               |                      |                                  |                                                                    |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|-----------|---------------|----------------------|----------------------------------|--------------------------------------------------------------------|---------|-----------------------------------------|-------------------------------|-----|--------------------------------------|----------------|------|-------------------------------------------|-------------------------|--------|-----------------------------------------|----------|
+| <b>Applicability</b>     | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                                    |           |               |                      |                                  |                                                                    |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                                    |           |               |                      |                                  |                                                                    |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |
+| <b>Initial condition</b> | The test tools retrieves the WSDL definition of the SUT (document repository).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                                    |           |               |                      |                                  |                                                                    |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |
+| <b>Test procedure</b>    | <p>1. The test tool checks:</p> <ol style="list-style-type: none"> <li>a. The "Retrieve Document Set" transaction of the WSDL definition of the SUT (Document repository) imports (xsd:import) the following types: in the /definitions/types section: namespace="urn:ihe:iti:xds-b:2007", schema="IHEXDS.xsd".</li> <li>b. In the "Retrieve Document Set" transaction of the WSDL definition of the SUT (document repository), the /definitions/message/part/@element attribute of the "Retrieve Document Set Request" message shall be defined as "ihe:RetrieveDocumentSetRequest".</li> <li>c. In the "Retrieve Document Set" transaction of the WSDL definition of the SUT (document repository), the /definitions/message/part/@element attribute of the "Retrieve Document Set Response" message shall be defined as "ihe:RetrieveDocumentSetResponse".</li> <li>d. In the "Retrieve Document Set" transaction of the WSDL definition of the SUT (document repository), the /definitions/portType/operation/input/@wsaw:Action attribute for the "Retrieve Document Set Request" message shall be defined as "urn:ihe:iti:2007:RetrieveDocumentSet".</li> <li>e. In the "Retrieve Document Set" transaction of the WSDL definition of the SUT (document repository), the /definitions/portType/operation/output/@wsaw:Action attribute for the "Retrieve Document Set Response" message shall be defined as "urn:ihe:iti:2007:RetrieveDocumentSetResponse".</li> <li>f. In the "Retrieve Document Set" transaction of the WSDL definition of the SUT (document repository), the /definitions/binding/operation/soap12:operation/@soapAction attribute shall be defined as "urn:ihe:iti:2007:RetrieveDocumentSet".</li> <li>g. The WSDL definition of the SUT (document repository) uses the following namespaces: <table border="1" data-bbox="518 1559 1359 2065"> <thead> <tr> <th>Prefix</th> <th>Namespace</th> <th>Specification</th> </tr> </thead> <tbody> <tr> <td>wsdl<br/>(or default)</td> <td>http://schemas.xmlsoap.org/wsdl/</td> <td>WSDL 1.1 binding for SOAP 1.1<br/><br/>WSDL 1.1 binding for SOAP 1.2</td> </tr> <tr> <td>wsoap12</td> <td>http://schemas.xmlsoap.org/wsdl/soap12/</td> <td>WSDL 1.1 binding for SOAP 1.2</td> </tr> <tr> <td>wsa</td> <td>http://www.w3.org/2005/08/addressing</td> <td>WSA 1.0 – Core</td> </tr> <tr> <td>wsaw</td> <td>http://www.w3.org/2006/05/addressing/wsdl</td> <td>WSA 1.0 – WSDL binding*</td> </tr> <tr> <td>soap12</td> <td>http://www.w3.org/2003/05/soap-envelope</td> <td>SOAP 1.2</td> </tr> </tbody> </table> </li> </ol> | Prefix                                                             | Namespace | Specification | wsdl<br>(or default) | http://schemas.xmlsoap.org/wsdl/ | WSDL 1.1 binding for SOAP 1.1<br><br>WSDL 1.1 binding for SOAP 1.2 | wsoap12 | http://schemas.xmlsoap.org/wsdl/soap12/ | WSDL 1.1 binding for SOAP 1.2 | wsa | http://www.w3.org/2005/08/addressing | WSA 1.0 – Core | wsaw | http://www.w3.org/2006/05/addressing/wsdl | WSA 1.0 – WSDL binding* | soap12 | http://www.w3.org/2003/05/soap-envelope | SOAP 1.2 |
+| Prefix                   | Namespace                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Specification                                                      |           |               |                      |                                  |                                                                    |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |
+| wsdl<br>(or default)     | http://schemas.xmlsoap.org/wsdl/                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | WSDL 1.1 binding for SOAP 1.1<br><br>WSDL 1.1 binding for SOAP 1.2 |           |               |                      |                                  |                                                                    |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |
+| wsoap12                  | http://schemas.xmlsoap.org/wsdl/soap12/                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | WSDL 1.1 binding for SOAP 1.2                                      |           |               |                      |                                  |                                                                    |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |
+| wsa                      | http://www.w3.org/2005/08/addressing                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | WSA 1.0 – Core                                                     |           |               |                      |                                  |                                                                    |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |
+| wsaw                     | http://www.w3.org/2006/05/addressing/wsdl                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | WSA 1.0 – WSDL binding*                                            |           |               |                      |                                  |                                                                    |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |
+| soap12                   | http://www.w3.org/2003/05/soap-envelope                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | SOAP 1.2                                                           |           |               |                      |                                  |                                                                    |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |            |                                  |            |     |                                           |            |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------|------------|-----|-------------------------------------------|------------|
+|                           | <table border="1" style="width: 100%;"> <tr> <td>xsd</td> <td>http://www.w3.org/2001/XMLSchema</td> <td>XML Schema</td> </tr> <tr> <td>xsi</td> <td>http://www.w3.org/2001/XMLSchema-instance</td> <td>XML Schema</td> </tr> </table> <p>h. The WSDL definition of the SUT (document repository) should use the following naming convention for WSDL artefacts:</p> <ul style="list-style-type: none"> <li>i. message request -&gt; {Transaction Name}_Message</li> <li>ii. message response -&gt; {Transaction Name}_Response_Message</li> <li>iii. portType -&gt; {NAME}_PortType</li> <li>iv. Operation -&gt; {NAME}_{Transaction Name}[_OperationID]</li> <li>v. SOAP 1.x binding -&gt; {NAME}_Binding_Soap1x</li> <li>vi. SOAP 1.x port -&gt; {NAME}_Port_Soap1x</li> </ul> <p>i. The WSDL definition of the SUT (document repository) shall define two WSDL messages for each request-response transaction.</p> <p>j. The WSDL definition of the SUT (document repository) shall include an attribute wsaw:Action for each input and output message defined in the WSDL portType operation.</p> <p>k. All operations defined in the WSDL definition of the SUT (document repository) shall use wsdl:operation/wsdl:input/@wasw:Action = "urn:ihe:{Domain}:{Year}:{Transaction name}" and wsdl:operation/wsdl:output/@wsaw:Action = "urn:ihe:{Domain}:{Year}:{Transaction name}Response"</p> <p>l. In the WSDL definition of the SUT (document repository), 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 of the corresponding WSDL operation defined in the WSDL portType.</p> | xsd        | http://www.w3.org/2001/XMLSchema | XML Schema | xsi | http://www.w3.org/2001/XMLSchema-instance | XML Schema |
+| xsd                       | http://www.w3.org/2001/XMLSchema                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | XML Schema |                                  |            |     |                                           |            |
+| xsi                       | http://www.w3.org/2001/XMLSchema-instance                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | XML Schema |                                  |            |     |                                           |            |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |            |                                  |            |     |                                           |            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |            |                                  |            |     |                                           |            |
+
+|                          |                                                                                                                                               |                                         |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|
+| <b>TP Id</b>             | TP/HIS/SEN/CM/BV-006                                                                                                                          |                                         |
+| <b>TP label</b>          | HIS Repository Retrieve Document Set Transaction – XUA SAML Assertion of type Holder Of Key                                                   |                                         |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                   | [ITU-T H.813]                           |
+|                          | <b>Testable items</b>                                                                                                                         | ConsentXDSb-8; M                        |
+|                          | <b>Spec</b>                                                                                                                                   | [IHE ITI-TF-2], Volume 2b, Section 3.40 |
+|                          | <b>Testable items</b>                                                                                                                         | Assertion-4; O      ExpActions-1; M     |
+| <b>Test purpose</b>      | Check that:<br>HIS sender does not report any error when it receives a correct SAML 2.0 Assertion                                             |                                         |
+| <b>Applicability</b>     | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012 AND C_HRN_SEN_014                                                                           |                                         |
+| <b>Other PICS</b>        |                                                                                                                                               |                                         |
+| <b>Initial condition</b> | The SUT is ready to receive a "Retrieve Document Set" message using SOAP 1.2 from the simulated HIS receiver launched by the test tool.       |                                         |
+| <b>Test procedure</b>    | 1. The simulated HIS receiver sends a SOAP 1.2 message containing an SAML 2.0 assertion of type "Holder of Key" to the HIS sender under test. |                                         |
+
+|                           |                                                                                                               |
+|---------------------------|---------------------------------------------------------------------------------------------------------------|
+|                           | 2. The HIS sender under test responds to the "Retrieve Document Set" correctly.                               |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>All steps are as specified within the test procedure above.</li> </ul> |
+| <b>Notes</b>              |                                                                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                    |                                         |                 |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|-----------------|
+| <b>TP Id</b>              | TP/HIS/SEN/CM/BV-007                                                                                                                                                                                                                                                               |                                         |                 |
+| <b>TP label</b>           | HIS Repository Retrieve Document Set Transaction – XUA with mandatory information only                                                                                                                                                                                             |                                         |                 |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                        | [ITU-T H.813]                           |                 |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                              | ConsentXDSb-8; M                        |                 |
+|                           | <b>Spec</b>                                                                                                                                                                                                                                                                        | [IHE ITI-TF-2], Volume 2b, Section 3.40 |                 |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                              | Assertion-3; M                          | ExpActions-1; M |
+| <b>Test purpose</b>       | Check that:<br>HIS sender does not report any error when it receives a correct SAML 2.0 Assertion                                                                                                                                                                                  |                                         |                 |
+| <b>Applicability</b>      | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012                                                                                                                                                                                                                                  |                                         |                 |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                    |                                         |                 |
+| <b>Initial condition</b>  | The SUT is ready to receive a "Retrieve Document Set" message using SOAP 1.2 from the simulated HIS receiver launched by the test tool.                                                                                                                                            |                                         |                 |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated HIS receiver sends a SOAP 1.2 message containing an SAML 2.0 assertion of type "Holder of Key" to the HIS sender under test.</li> <li>The HIS sender under test responds to the "Retrieve Document Set" correctly.</li> </ol> |                                         |                 |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                      |                                         |                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                    |                                         |                 |
+
+|                      |                                                                                                   |                                         |                 |
+|----------------------|---------------------------------------------------------------------------------------------------|-----------------------------------------|-----------------|
+| <b>TP Id</b>         | TP/HIS/SEN/CM/BV-008                                                                              |                                         |                 |
+| <b>TP label</b>      | HIS Repository Retrieve Document Set Transaction – XUA with mandatory and optional information    |                                         |                 |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                       | [ITU-T H.813]                           |                 |
+|                      | <b>Testable items</b>                                                                             | ConsentXDSb-8; M                        |                 |
+|                      | <b>Spec</b>                                                                                       | [IHE ITI-TF-2], Volume 2b, Section 3.40 |                 |
+|                      | <b>Testable items</b>                                                                             | Assertion-3; M                          | Assertion-9 ; O |
+|                      |                                                                                                   | ExpActions-6; O                         | ExpActions-1; M |
+| <b>Test purpose</b>  | Check that:<br>HIS sender does not report any error when it receives a correct SAML 2.0 Assertion |                                         |                 |
+| <b>Applicability</b> | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012                                                 |                                         |                 |
+| <b>Other PICS</b>    |                                                                                                   |                                         |                 |
+
+|                           |                                                                                                                                                                                                                                                                                    |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b>  | The SUT is ready to receive a "Retrieve Document Set" message using SOAP 1.2 from the simulated HIS receiver launched by the test tool.                                                                                                                                            |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated HIS receiver sends a SOAP 1.2 message containing an SAML 2.0 assertion of type "Holder of Key" to the HIS sender under test.</li> <li>The HIS sender under test responds to the "Retrieve Document Set" correctly.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                    |
+
+|                           |                                                                                                                                                                                                                                                                                    |                                         |                 |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|-----------------|
+| <b>TP Id</b>              | TP/HIS/SEN/CM/BV-009                                                                                                                                                                                                                                                               |                                         |                 |
+| <b>TP label</b>           | HIS Repository Retrieve Document Set Transaction – XUA++ with optional parameter 'subject role'                                                                                                                                                                                    |                                         |                 |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                        | [ITU-T H.813]                           |                 |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                              | ConsentXDSb-9; O                        |                 |
+|                           | <b>Spec</b>                                                                                                                                                                                                                                                                        | [IHE ITI-TF-2], Volume 2b, Section 3.40 |                 |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                              | Assertion-3; M                          | ExpActions-1; M |
+|                           | <b>Spec</b>                                                                                                                                                                                                                                                                        | [IHE TFS XUA++]                         |                 |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                              | ATNA++2; C                              | ATNA++3; O      |
+| <b>Test purpose</b>       | Check that:<br>HIS sender does not report any error when it receives a correct SAML 2.0 Assertion                                                                                                                                                                                  |                                         |                 |
+| <b>Applicability</b>      | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012 AND C_HRN_SEN_013                                                                                                                                                                                                                |                                         |                 |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                    |                                         |                 |
+| <b>Initial condition</b>  | The SUT is ready to receive a "Retrieve Document Set" message using SOAP 1.2 from the simulated HIS receiver launched by the test tool.                                                                                                                                            |                                         |                 |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated HIS receiver sends a SOAP 1.2 message containing an SAML 2.0 assertion of type "Holder of Key" to the HIS sender under test.</li> <li>The HIS sender under test responds to the "Retrieve Document Set" correctly.</li> </ol> |                                         |                 |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                      |                                         |                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                    |                                         |                 |
+
+|                 |                                                                                                 |                                         |  |
+|-----------------|-------------------------------------------------------------------------------------------------|-----------------------------------------|--|
+| <b>TP Id</b>    | TP/HIS/SEN/CM/BV-010                                                                            |                                         |  |
+| <b>TP label</b> | HIS Repository Retrieve Document Set Transaction – XUA++ with optional parameter 'auth consent' |                                         |  |
+| <b>Coverage</b> | <b>Spec</b>                                                                                     | [ITU-T H.813]                           |  |
+|                 | <b>Testable items</b>                                                                           | ConsentXDSb-9; O                        |  |
+|                 | <b>Spec</b>                                                                                     | [IHE ITI-TF-2], Volume 2b, Section 3.40 |  |
+
+|                           |                                                                                                                                                                                                                                                                                    |                 |                 |            |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------|------------|
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                              | Assertion-3; M  | ExpActions-1; M |            |
+|                           | <b>Spec</b>                                                                                                                                                                                                                                                                        | [IHE TFS XUA++] |                 |            |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                              | ATNA++5; C      | ATNA++6; O      | ATNA++7; O |
+| <b>Test purpose</b>       | Check that:<br>HIS sender does not report any error when it receives a correct SAML 2.0 Assertion                                                                                                                                                                                  |                 |                 |            |
+| <b>Applicability</b>      | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012 AND C_HRN_SEN_013                                                                                                                                                                                                                |                 |                 |            |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                    |                 |                 |            |
+| <b>Initial condition</b>  | The SUT is ready to receive a "Retrieve Document Set" message using SOAP 1.2 from the simulated HIS receiver launched by the test tool.                                                                                                                                            |                 |                 |            |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated HIS receiver sends a SOAP 1.2 message containing an SAML 2.0 assertion of type "Holder of Key" to the HIS sender under test.</li> <li>The HIS sender under test responds to the "Retrieve Document Set" correctly.</li> </ol> |                 |                 |            |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                      |                 |                 |            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                    |                 |                 |            |
+
+|                           |                                                                                                                                                                                                                                                                                    |                                         |                 |  |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|-----------------|--|
+| <b>TP Id</b>              | TP/HIS/SEN/CM/BV-011                                                                                                                                                                                                                                                               |                                         |                 |  |
+| <b>TP label</b>           | HIS Repository Retrieve Document Set Transaction – XUA++ with optional parameter 'purpose of use'                                                                                                                                                                                  |                                         |                 |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                        | [ITU-T H.813]                           |                 |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                              | ConsentXDSb-9; O                        |                 |  |
+|                           | <b>Spec</b>                                                                                                                                                                                                                                                                        | [IHE ITI-TF-2], Volume 2b, Section 3.40 |                 |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                              | Assertion-3; M                          | ExpActions-1; M |  |
+|                           | <b>Spec</b>                                                                                                                                                                                                                                                                        | [IHE TFS XUA++]                         |                 |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                              | ATNA++11; O                             |                 |  |
+| <b>Test purpose</b>       | Check that:<br>HIS sender does not report any error when it receives a correct SAML 2.0 Assertion                                                                                                                                                                                  |                                         |                 |  |
+| <b>Applicability</b>      | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012 AND C_HRN_SEN_013                                                                                                                                                                                                                |                                         |                 |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                    |                                         |                 |  |
+| <b>Initial condition</b>  | The SUT is ready to receive a "Retrieve Document Set" message using SOAP 1.2 from the simulated HIS receiver launched by the test tool.                                                                                                                                            |                                         |                 |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated HIS receiver sends a SOAP 1.2 message containing an SAML 2.0 assertion of type "Holder of Key" to the HIS sender under test.</li> <li>The HIS sender under test responds to the "Retrieve Document Set" correctly.</li> </ol> |                                         |                 |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                      |                                         |                 |  |
+
+|              |  |
+|--------------|--|
+| <b>Notes</b> |  |
+|--------------|--|
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                                      |                        |                         |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|------------------------|-------------------------|
+| <b>TP Id</b>              | TP/HIS/SEN/CM/BV-012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                                      |                        |                         |
+| <b>TP label</b>           | HIS Registry Stored Query. SOAP requirements                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                                      |                        |                         |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [ITU-T H.813]                                                        |                        |                         |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | ConsentSenderXDSb-4; M                                               | ConsentSenderXDSb-7; M | ConsentSenderXDSb-10; M |
+|                           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [IHE ITI-TF-2], Volume 2a, Transactions Part A, Sections 3.1 to 3.28 |                        |                         |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | RefStd_01; M                                                         |                        |                         |
+| <b>Test purpose</b>       | Check that:<br>Continua HIS senders implement SOAP 1.2 for Retrieve Document Set transaction.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                                      |                        |                         |
+| <b>Applicability</b>      | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                                      |                        |                         |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                                      |                        |                         |
+| <b>Initial condition</b>  | The SUT is ready to receive an AdhocQuery request using SOAP 1.2 from the test tool.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                                      |                        |                         |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The test tool sends a SOAP 1.2 message containing a correctly formatted FindDocuments AdhocQueryRequest using the PatientId provided in the PIXIT with the \$XDSDocumentEntryPatientID and the \$XDSDocumentEntryStatus element.</li> <li>2. The SUT receives the message and answers with an AdhocQueryResponse with the metadata of the required documents.</li> <li>3. The test tool receives the message and checks that: <ol style="list-style-type: none"> <li>a. the version of the SOAP is 1.2, that is the namespace of the envelope is <a href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</a>.</li> <li>b. The action of the transaction is "urn:ihe:iti:2007:RegistryStoredQueryResponse".</li> <li>c. The SOAP body has only one child that is an AdhocQueryResponse element whose namespace is "urn:oasis:names:tc:ebxml-reg-rep:xsd:query:3.0".</li> </ol> </li> </ol> |                                                                      |                        |                         |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                                      |                        |                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                                      |                        |                         |
+
+|                 |                                                                                   |                                                                      |                       |                        |
+|-----------------|-----------------------------------------------------------------------------------|----------------------------------------------------------------------|-----------------------|------------------------|
+| <b>TP Id</b>    | TP/HIS/SEN/CM/BV-013                                                              |                                                                      |                       |                        |
+| <b>TP label</b> | HIS Registry Stored Query. FindDocuments Query valid behaviour. Required Elements |                                                                      |                       |                        |
+| <b>Coverage</b> | <b>Spec</b>                                                                       | [ITU-T H.813]                                                        |                       |                        |
+|                 | <b>Testable items</b>                                                             | ConsentSenderXDS_4; M                                                | ConsentSenderXDS_7; M | ConsentSenderXDS_10; M |
+|                 | <b>Spec</b>                                                                       | [IHE ITI-TF-2], Volume 2a, Transactions Part A, Sections 3.1 to 3.28 |                       |                        |
+|                 | <b>Testable items</b>                                                             | RefStd_01; M                                                         | StatusValues_02; M    | FindDoc_01; M          |
+|                 |                                                                                   | FindDoc_02; O                                                        | FindDoc_03; O         | FindDoc_04; O          |
+|                 |                                                                                   | FindDoc_05; O                                                        | FindDoc_06; O         | FindDoc_07; O          |
+
+|                           |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                    |                      |
+|---------------------------|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------------------|
+|                           |  | FindDoc_08; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | FindDoc_09; O      | FindDoc_10; O        |
+|                           |  | FindDoc_11; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | FindDoc_12; O      | FindDoc_13; O        |
+|                           |  | FindDoc_14; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | FindDoc_15; M      | CodingSMValues_01; M |
+|                           |  | Exp_Actions_01; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Exp_Actions_02; M  | Exp_Actions_03; M    |
+|                           |  | Exp_Actions_04; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Exp_Actions_05; M  | Exp_Actions_06; M    |
+|                           |  | WebServTrasnport_02; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | StatusValues_01; M | Ebr&Ebs_01; M        |
+|                           |  | CodingScheme_01; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                    |                      |
+| <b>Test purpose</b>       |  | Check that:<br>HIS sender correctly answers a FindDocuments AdhocQueryRequest which petitions for an existing document.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                    |                      |
+| <b>Applicability</b>      |  | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                    |                      |
+| <b>Other PICS</b>         |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                    |                      |
+| <b>Initial condition</b>  |  | The SUT is ready to receive an AdhocQuery request using SOAP 1.2 from the test tool.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                    |                      |
+| <b>Test procedure</b>     |  | <ol style="list-style-type: none"> <li>1. The test tool sends a SOAP 1.2 message containing a correctly formatted FindDocuments AdhocQueryRequest with the following parameters: <ol style="list-style-type: none"> <li>a. \$XDSDocumentEntryPatientID set to I_HRN_SEN_001</li> <li>b. \$XDSDocumentEntryStatus set to: 'urn:oasis:names:tc:ebxml-regrep:StatusType:Approved'.</li> </ol> </li> <li>2. The SUT receives the message and answers with an AdhocQueryResponse with the metadata of the required documents.</li> <li>3. The test tool receives the message and checks the structure with a parser and the provided schemas. Additionally, the following are checked: <ol style="list-style-type: none"> <li>a. The "value" element of the ExternalIdentifier with id=" urn:uuid:db9f4438-ffff-435f-9d34-d76190728637" matches the PatientId of the AdhocQueryRequest.</li> <li>b. The ExtrinsicObject @status attribute is set to "urn:oasis:names:tc:ebxml-regrep:StatusType:Approved".</li> </ol> </li> </ol> |                    |                      |
+| <b>Pass/Fail criteria</b> |  | <ul style="list-style-type: none"> <li>• All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                    |                      |
+| <b>Notes</b>              |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                    |                      |
+
+|                 |                                                                                 |                                                                      |                       |                        |
+|-----------------|---------------------------------------------------------------------------------|----------------------------------------------------------------------|-----------------------|------------------------|
+| <b>TP Id</b>    | TP/HIS/SEN/CM/BV-014                                                            |                                                                      |                       |                        |
+| <b>TP label</b> | HIS Registry Stored Query. FindDocuments Query valid partial success behaviour. |                                                                      |                       |                        |
+| <b>Coverage</b> | <b>Spec</b>                                                                     | [ITU-T H.813]                                                        |                       |                        |
+|                 | <b>Testable items</b>                                                           | ConsentSenderXDS_4; M                                                | ConsentSenderXDS_7; M | ConsentSenderXDS_10; M |
+|                 | <b>Spec</b>                                                                     | [IHE ITI-TF-2], Volume 2a, Transactions Part A, Sections 3.1 to 3.28 |                       |                        |
+|                 | <b>Testable items</b>                                                           | RefStd_01; M                                                         | StatusValues_03; M    | CodingSMValues_01; M   |
+|                 |                                                                                 | Exp_Actions_01; M                                                    | Exp_Actions_02; M     | Exp_Actions_03; M      |
+|                 |                                                                                 | Exp_Actions_04; M                                                    | Exp_Actions_05; M     | Exp_Actions_06; M      |
+|                 |                                                                                 | WebServTrasnport_02; M                                               | StatusValues_01; M    | Ebr&Ebs_01; M          |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                    |  |  |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|--|--|
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | CodingScheme_01; M |  |  |
+| <b>Test purpose</b>       | Check that:<br>HIS sender correctly answers a FindDocuments AdhocQueryRequest which petitions for a non-existing document.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                    |  |  |
+| <b>Applicability</b>      | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                    |  |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                    |  |  |
+| <b>Initial condition</b>  | The SUT is ready to receive an AdhocQuery request using SOAP 1.2 from the test tool.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                    |  |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The test tool sends a SOAP 1.2 message containing a correctly formatted FindDocuments AdhocQueryRequest with the \$XDSDocumentEntryPatientID and the \$XDSDocumentEntryStatus elements: <ol style="list-style-type: none"> <li>a. \$XDSDocumentEntryPatientID set to I_HRN_SEN_008</li> <li>b. \$XDSDocumentEntryStatus set to: 'urn:oasis:names:tc:ebxml-regrep:StatusType:Approved'.</li> </ol> </li> <li>2. The SUT receives the message and answers with an AdhocQueryResponse with the metadata of the required documents.</li> <li>3. The test tool receives the message and checks the structure with a parser and the provided schemas. Additionally, the following are checked: <ol style="list-style-type: none"> <li>a. The "value" element of the ExternalIdentifier with id="urn:uuid:db9f4438-ffff-435f-9d34-d76190728637" matches the PatientId of the AdhocQueryRequest.</li> <li>b. The ExtrinsicObject @status attribute is set to "urn:oasis:names:tc:ebxml-regrep:StatusType:Approved".</li> </ol> </li> </ol> |                    |  |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                    |  |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                    |  |  |
+
+|                      |                                                                                          |                                                                      |                       |                        |
+|----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------|-----------------------|------------------------|
+| <b>TP Id</b>         | TP/HIS/SEN/CM/BV-015                                                                     |                                                                      |                       |                        |
+| <b>TP label</b>      | HIS Registry Stored Query. FindDocuments Query invalid behaviour                         |                                                                      |                       |                        |
+| <b>Coverage</b>      | <b>Spec</b>                                                                              | [ITU-T H.813]                                                        |                       |                        |
+|                      | <b>Testable items</b>                                                                    | ConsentSenderXDS_4; M                                                | ConsentSenderXDS_7; M | ConsentSenderXDS_10; M |
+|                      | <b>Spec</b>                                                                              | [IHE ITI-TF-2], Volume 2a, Transactions Part A, Sections 3.1 to 3.28 |                       |                        |
+|                      | <b>Testable items</b>                                                                    | RefStd_01; M                                                         | StatusValues_04; M    | CodingSMValues_01; M   |
+|                      |                                                                                          | Exp_Actions_01; M                                                    | Exp_Actions_02 ; M    | Exp_Actions_03 ; M     |
+|                      |                                                                                          | Exp_Actions_04 ; M                                                   | Exp_Actions_05 ; M    | Exp_Actions_06 ; M     |
+|                      |                                                                                          | WebServTrasnport_02; M                                               | StatusValues_01; M    | Ebr&Ebs_01; M          |
+|                      |                                                                                          | CodingScheme_01; M                                                   |                       |                        |
+| <b>Test purpose</b>  | Check that:<br>HIS sender correctly answers a malformed FindDocuments AdhocQueryRequest. |                                                                      |                       |                        |
+| <b>Applicability</b> | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012                                        |                                                                      |                       |                        |
+| <b>Other PICS</b>    |                                                                                          |                                                                      |                       |                        |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b>  | The SUT is ready to receive an AdhocQuery request using SOAP 1.2 from the test tool.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Test Procedure</b>     | <ol style="list-style-type: none"> <li>1. Test Tool sends a SOAP 1.2 message containing a correctly formatted FindDocuments AdhocQueryRequest using the PatientId provided in the PIXIT with the \$XDSDocumentEntryPatientID and the \$XDSDocumentEntryStatus elements</li> <li>2. SUT receives the message and answers with an AdhocQueryResponse with the metadata of the required documents</li> <li>3. Test Tool receives the message and checks the structure with a parser and the provided schemas. Additionally the following elements' value is checked: <ol style="list-style-type: none"> <li>a. The "value" element of the ExternalIdentifier with id="urn:uuid:db9f4438-ffff-435f-9d34-d76190728637" matches the PatientId of the AdhocQueryRequest</li> </ol> The ExtrinsicObject @status attribute is set to "urn:oasis:names:tc:ebxml-regrep:StatusType:Approved"</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                |                         |
+|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-------------------------|
+| <b>TP Id</b>        | TP/HIS/SEN/CM/BV-016                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                |                         |
+| <b>TP label</b>     | HIS Registry Stored Query. WSDL Requirements                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                |                         |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [IHE ITI-TF-2], Volume 2b, Transactions Part B |                         |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | WebServTrasnpport_01; M                        | WebServTrasnpport_02; M |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | WebServTrasnpport_04; M                        | WebServTrasnpport_05; M |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | WebServTrasnpport_09; M                        | WebServTrasnpport_10; R |
+|                     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [IHE ITI-TF-2], Volume 2x, Appendix V          |                         |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | Namespaces; M                                  | IHE-WSP201; R           |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | IHE-WSP207; M                                  | IHE-WSP208; M           |
+| <b>Test purpose</b> | <p>Check that:</p> <p>Registry Stored Query transaction of the WSDL definition of the SUT (Document Registry) imports (xsd:import) the following types: in the /definitions/types section:<br/> namespace="urn:ihe:iti:xds-b:2007", schema="query.xsd"</p> <p>[AND]</p> <p>In the Registry Stored Query transaction of the WSDL definition of the SUT (Document Registry) the /definitions/message/part/@element attribute of the Registry Stored Query message shall be defined as "ihe:RegistryStoredQuery"</p> <p>[AND]</p> <p>In the Registry Stored Query transaction of the WSDL definition of the SUT (Document Registry) the /definitions/message/part/@element attribute of the Registry Stored Query Response message shall be defined as "ihe: RegistryStoredQueryResponse"</p> <p>[AND]</p> <p>In the Registry Stored Query transaction of the WSDL definition of the SUT (Document Registry) the /definitions/portType/operation/input/@wsaw:Action attribute for the Registry Stored Query Request message shall be defined as "urn:ihe:iti:2007:RegistryStoredQuery"</p> <p>[AND]</p> <p>In the Registry Stored Query transaction of the WSDL definition of the SUT (Document Registry) the /definitions/portType/operation/output/@wsaw:Action attribute for the Registry Stored Query Response message shall be defined as "urn:ihe:iti:2007:RegistryStoredQueryResponse"</p> |                                                |                         |
+
+[AND]
+
+In the Registry Stored Query transaction of the WSDL definition of the SUT (Document Registry the /definitions/binding/operation/soap12:operation/@soapAction attribute shall be defined as "urn:ihe:iti:2007:RegistryStoredQuery"
+
+[AND]
+
+The WSDL definition of the SUT (Document Registry) uses the following namespaces:
+
+| Prefix            | Namespace                                 | Specification                                                            |
+|-------------------|-------------------------------------------|--------------------------------------------------------------------------|
+| wsdl (or default) | http://schemas.xmlsoap.org/wsdl/          | WSDL 1.1<br>binding for SOAP 1.1<br><br>WSDL 1.1<br>binding for SOAP 1.2 |
+| wsoap12           | http://schemas.xmlsoap.org/wsdl/soap12/   | WSDL 1.1<br>binding for SOAP 1.2                                         |
+| wsa               | http://www.w3.org/2005/08/addressing      | WSA 1.0 - Core                                                           |
+| wsaw              | http://www.w3.org/2006/05/addressing/wsdl | WSA 1.0 - WSDL binding*                                                  |
+| soap12            | http://www.w3.org/2003/05/soap-envelope   | SOAP 1.2                                                                 |
+| xsd               | http://www.w3.org/2001/XMLSchema          | XML Schema                                                               |
+| xsi               | http://www.w3.org/2001/XMLSchema-instance | XML Schema                                                               |
+
+[AND]
+
+The WSDL definition of the SUT (Document Registry) should 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.x binding -> {NAME}\_Binding\_Soap1x
+- SOAP 1.x port -> {NAME}\_Port\_Soap1x
+
+[AND]
+
+The WSDL definition of the SUT (Document Registry) shall define two WSDL messages for each request-response transaction
+
+[AND]
+
+The WSDL definition of the SUT (Document Registry) shall include an attribute wsaw:Action for each input and output message defined in the WSDL portType operation
+
+[AND]
+
+All operations defined in the WSDL definition of the SUT (Document Registry) shall use wsdl:operation/wsdl:input/@wasw:Action = "urn:ihe:{Domain}:{Year}:{Transaction name}" and wsdl:operation/wsdl:output/@wsaw:Action = "urn:ihe:{Domain}:{Year}:{Transaction name}Response"
+
+[AND]
+
+In the WSDL definition of the SUT (Document Registry), 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
+
+**Applicability**
+
+C\_HRN\_SEN\_000 AND C\_HRN\_SEN\_001 AND C\_HRN\_SEN\_012
+
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                                |           |               |                   |                                  |                                                                |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |     |                                  |            |     |                                           |            |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|-----------|---------------|-------------------|----------------------------------|----------------------------------------------------------------|---------|-----------------------------------------|-------------------------------|-----|--------------------------------------|----------------|------|-------------------------------------------|-------------------------|--------|-----------------------------------------|----------|-----|----------------------------------|------------|-----|-------------------------------------------|------------|
+| <b>Initial condition</b> | The test tool retrieves the WSDL definition of the SUT (document registry).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                                |           |               |                   |                                  |                                                                |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |     |                                  |            |     |                                           |            |
+| <b>Test procedure</b>    | <p>1. The test tool checks:</p> <ul style="list-style-type: none"> <li>a. The "Registry Stored Query" transaction of the WSDL definition of the SUT (document registry) imports (xsd:import) the following types: in the /definitions/types section: namespace="urn:ihe:iti:xds-b:2007", schema="IHEXDS.xsd".</li> <li>b. In the "Registry Stored Query" transaction of the WSDL definition of the SUT (document registry), the /definitions/message/part/@element attribute of the "Registry Stored Query Request" message shall be defined as "ihe:RegistryStoredQueryRequest".</li> <li>c. In the "Registry Stored Query" transaction of the WSDL definition of the SUT (document registry), the /definitions/message/part/@element attribute of the "Registry Stored Query Response" message shall be defined as "ihe:RegistryStoredQueryResponse".</li> <li>d. In the "Registry Stored Query" transaction of the WSDL definition of the SUT (document registry), the /definitions/portType/operation/input/@wsaw:Action attribute for the "Registry Stored Query Request" message shall be defined as "urn:ihe:iti:2007:RegistryStoredQuery".</li> <li>e. In the "Registry Stored Query" transaction of the WSDL definition of the SUT (document registry), the /definitions/portType/operation/output/@wsaw:Action attribute for the "Registry Stored Query Response" message shall be defined as "urn:ihe:iti:2007:RegistryStoredQueryResponse".</li> <li>f. In the "Registry Stored Query" transaction of the WSDL definition of the SUT (document registry), the /definitions/binding/operation/soap12:operation/@soapAction attribute shall be defined as "urn:ihe:iti:2007:RegistryStoredQuery".</li> <li>g. The WSDL definition of the SUT (document registry) uses the following namespaces:           <table border="1" style="width: 100%; margin-top: 10px;"> <thead> <tr> <th>Prefix</th> <th>Namespace</th> <th>Specification</th> </tr> </thead> <tbody> <tr> <td>wsdl (or default)</td> <td>http://schemas.xmlsoap.org/wsdl/</td> <td>WSDL 1.1 binding for SOAP 1.1<br/>WSDL 1.1 binding for SOAP 1.2</td> </tr> <tr> <td>wsoap12</td> <td>http://schemas.xmlsoap.org/wsdl/soap12/</td> <td>WSDL 1.1 binding for SOAP 1.2</td> </tr> <tr> <td>wsa</td> <td>http://www.w3.org/2005/08/addressing</td> <td>WSA 1.0 – Core</td> </tr> <tr> <td>wsaw</td> <td>http://www.w3.org/2006/05/addressing/wsdl</td> <td>WSA 1.0 – WSDL binding*</td> </tr> <tr> <td>soap12</td> <td>http://www.w3.org/2003/05/soap-envelope</td> <td>SOAP 1.2</td> </tr> <tr> <td>xsd</td> <td>http://www.w3.org/2001/XMLSchema</td> <td>XML Schema</td> </tr> <tr> <td>xsi</td> <td>http://www.w3.org/2001/XMLSchema-instance</td> <td>XML Schema</td> </tr> </tbody> </table> </li> <li>h. The WSDL definition of the SUT (document registry) should use the following naming convention for WSDL artefacts:           <ul style="list-style-type: none"> <li>i. message request -&gt; {Transaction Name}_Message</li> <li>ii. message response -&gt; {Transaction Name}_Response_Message</li> <li>iii. portType -&gt; {NAME}_PortType</li> <li>iv. Operation -&gt; {NAME}_{Transaction Name}[_OperationID]</li> <li>v. SOAP 1.x binding -&gt; {NAME}_Binding_Soap1x</li> <li>vi. SOAP 1.x port -&gt; {NAME}_Port_Soap1x</li> </ul> </li> <li>i. The WSDL definition of the SUT (document registry) shall define two WSDL messages for each request-response transaction.</li> </ul> | Prefix                                                         | Namespace | Specification | wsdl (or default) | http://schemas.xmlsoap.org/wsdl/ | WSDL 1.1 binding for SOAP 1.1<br>WSDL 1.1 binding for SOAP 1.2 | wsoap12 | http://schemas.xmlsoap.org/wsdl/soap12/ | WSDL 1.1 binding for SOAP 1.2 | wsa | http://www.w3.org/2005/08/addressing | WSA 1.0 – Core | wsaw | http://www.w3.org/2006/05/addressing/wsdl | WSA 1.0 – WSDL binding* | soap12 | http://www.w3.org/2003/05/soap-envelope | SOAP 1.2 | xsd | http://www.w3.org/2001/XMLSchema | XML Schema | xsi | http://www.w3.org/2001/XMLSchema-instance | XML Schema |
+| Prefix                   | Namespace                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Specification                                                  |           |               |                   |                                  |                                                                |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |     |                                  |            |     |                                           |            |
+| wsdl (or default)        | http://schemas.xmlsoap.org/wsdl/                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | WSDL 1.1 binding for SOAP 1.1<br>WSDL 1.1 binding for SOAP 1.2 |           |               |                   |                                  |                                                                |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |     |                                  |            |     |                                           |            |
+| wsoap12                  | http://schemas.xmlsoap.org/wsdl/soap12/                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | WSDL 1.1 binding for SOAP 1.2                                  |           |               |                   |                                  |                                                                |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |     |                                  |            |     |                                           |            |
+| wsa                      | http://www.w3.org/2005/08/addressing                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | WSA 1.0 – Core                                                 |           |               |                   |                                  |                                                                |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |     |                                  |            |     |                                           |            |
+| wsaw                     | http://www.w3.org/2006/05/addressing/wsdl                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | WSA 1.0 – WSDL binding*                                        |           |               |                   |                                  |                                                                |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |     |                                  |            |     |                                           |            |
+| soap12                   | http://www.w3.org/2003/05/soap-envelope                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | SOAP 1.2                                                       |           |               |                   |                                  |                                                                |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |     |                                  |            |     |                                           |            |
+| xsd                      | http://www.w3.org/2001/XMLSchema                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | XML Schema                                                     |           |               |                   |                                  |                                                                |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |     |                                  |            |     |                                           |            |
+| xsi                      | http://www.w3.org/2001/XMLSchema-instance                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | XML Schema                                                     |           |               |                   |                                  |                                                                |         |                                         |                               |     |                                      |                |      |                                           |                         |        |                                         |          |     |                                  |            |     |                                           |            |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>j. The WSDL definition of the SUT (document registry) shall include an attribute <code>wsaw:Action</code> for each input and output message defined in the WSDL <code>portType</code> operation.</p> <p>k. All operations defined in the WSDL definition of the SUT (document registry) shall use <code>wsdl:operation/wsdl:input/@wasw:Action = "urn:ihe:{Domain}:{Year}:{Transaction name}"</code> and <code>wsdl:operation/wsdl:output/@wsaw:Action = "urn:ihe:{Domain}:{Year}:{Transaction name}Response"</code>.</p> <p>l. In the WSDL definition of the SUT (document registry), for each operation defined in the WSDL <code>portType</code> a <code>wsoap:operation/@soapAction</code> attribute shall be provided. The value of <code>wsoap:operation/@soapAction</code> shall be consistent with the name of the corresponding WSDL operation defined in the WSDL <code>portType</code>.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                           |                                                                                                                                                                                                                                  |                                         |                 |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|-----------------|
+| <b>TP Id</b>              | TP/HIS/SEN/CM/BV-017                                                                                                                                                                                                             |                                         |                 |
+| <b>TP label</b>           | HIS Registry Stored Query – XUA SAML Assertion of type Holder Of Key                                                                                                                                                             |                                         |                 |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                      | [ITU-T H.813]                           |                 |
+|                           | <b>Testable items</b>                                                                                                                                                                                                            | ConsentXDSb-8; M                        |                 |
+|                           | <b>Spec</b>                                                                                                                                                                                                                      | [IHE ITI-TF-2], Volume 2b, Section 3.40 |                 |
+|                           | <b>Testable items</b>                                                                                                                                                                                                            | Assertion-4; O                          | ExpActions-1; M |
+| <b>Test purpose</b>       | Check that:<br>HIS sender does not report any error when it receives a correct SAML 2.0 Assertion                                                                                                                                |                                         |                 |
+| <b>Applicability</b>      | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012 AND C_HRN_SEN_014                                                                                                                                                              |                                         |                 |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                  |                                         |                 |
+| <b>Initial condition</b>  | The SUT is ready to receive a "Registry Stored Query" message using SOAP 1.2 from the simulated HIS receiver launched by the test tool.                                                                                          |                                         |                 |
+| <b>Test procedure</b>     | 1. The simulated HIS receiver sends a SOAP 1.2 message containing an SAML 2.0 assertion of type "Holder of Key" to the HIS sender under test.<br>2. The HIS sender under test responds to the "Registry Stored Query" correctly. |                                         |                 |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>All steps are as specified within the test procedure above.</li> </ul>                                                                                                                    |                                         |                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                  |                                         |                 |
+
+|                 |                                                                 |                                         |  |
+|-----------------|-----------------------------------------------------------------|-----------------------------------------|--|
+| <b>TP Id</b>    | TP/HIS/SEN/CM/BV-018                                            |                                         |  |
+| <b>TP label</b> | HIS Registry Stored Query – XUA with mandatory information only |                                         |  |
+| <b>Coverage</b> | <b>Spec</b>                                                     | [ITU-T H.813]                           |  |
+|                 | <b>Testable items</b>                                           | ConsentXDSb-8; M                        |  |
+|                 | <b>Spec</b>                                                     | [IHE ITI-TF-2], Volume 2b, Section 3.40 |  |
+
+|                           |                                                                                                                                                                                                                                                                                                             |                |                 |  |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-----------------|--|
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                       | Assertion-3; M | ExpActions-1; M |  |
+| <b>Test purpose</b>       | Check that:<br>HIS sender does not report any error when it receives a correct SAML 2.0 Assertion                                                                                                                                                                                                           |                |                 |  |
+| <b>Applicability</b>      | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012                                                                                                                                                                                                                                                           |                |                 |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                             |                |                 |  |
+| <b>Initial condition</b>  | The SUT is ready to receive a "Registry Stored Query" message using SOAP 1.2 from the simulated HIS receiver launched by the test tool.                                                                                                                                                                     |                |                 |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated HIS receiver sends a SOAP 1.2 message containing an SAML 2.0 assertion of type "Bearer" with mandatory information only to the HIS sender under test.</li> <li>The HIS sender under test responds to the "Registry Stored Query" correctly.</li> </ol> |                |                 |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                                               |                |                 |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                             |                |                 |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                     |                                         |                 |                 |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|-----------------|-----------------|
+| <b>TP Id</b>              | TP/HIS/SEN/CM/BV-019                                                                                                                                                                                                                                                                                                |                                         |                 |                 |
+| <b>TP label</b>           | HIS Registry Stored Query – XUA with mandatory and optional information                                                                                                                                                                                                                                             |                                         |                 |                 |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                         | [ITU-T H.813]                           |                 |                 |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                               | ConsentXDSb-8; M                        |                 |                 |
+|                           | <b>Spec</b>                                                                                                                                                                                                                                                                                                         | [IHE ITI-TF-2], Volume 2b, Section 3.40 |                 |                 |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                               | Assertion-3; M                          | Assertion-9 ; O | ExpActions-1; M |
+|                           |                                                                                                                                                                                                                                                                                                                     | ExpActions-6; O                         |                 |                 |
+| <b>Test purpose</b>       | Check that:<br>HIS sender does not report any error when it receives a correct SAML 2.0 Assertion                                                                                                                                                                                                                   |                                         |                 |                 |
+| <b>Applicability</b>      | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012                                                                                                                                                                                                                                                                   |                                         |                 |                 |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                     |                                         |                 |                 |
+| <b>Initial condition</b>  | The SUT is ready to receive a "Registry Stored Query" message using SOAP 1.2 from the simulated HIS receiver launched by the test tool.                                                                                                                                                                             |                                         |                 |                 |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated HIS receiver sends a SOAP 1.2 message containing an SAML 2.0 assertion of type "Bearer" with mandatory and optional information to the HIS sender under test.</li> <li>The HIS sender under test responds to the "Registry Stored Query" correctly.</li> </ol> |                                         |                 |                 |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                                                       |                                         |                 |                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                     |                                         |                 |                 |
+
+|                 |                                                                          |
+|-----------------|--------------------------------------------------------------------------|
+| <b>TP Id</b>    | TP/HIS/SEN/CM/BV-020                                                     |
+| <b>TP label</b> | HIS Registry Stored Query – XUA++ with optional parameter 'subject role' |
+
+|                           |                                                                                                                                                                                                                                                                                                   |                                         |                 |  |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|-----------------|--|
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                       | [ITU-T H.813]                           |                 |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                             | ConsentXDSb-9; O                        |                 |  |
+|                           | <b>Spec</b>                                                                                                                                                                                                                                                                                       | [IHE ITI-TF-2], Volume 2b, Section 3.40 |                 |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                             | Assertion-3; M                          | ExpActions-1; M |  |
+| <b>Test purpose</b>       | Check that:<br>HIS sender does not report any error when it receives a correct SAML 2.0 Assertion                                                                                                                                                                                                 |                                         |                 |  |
+| <b>Applicability</b>      | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012 AND C_HRN_SEN_013                                                                                                                                                                                                                               |                                         |                 |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                   |                                         |                 |  |
+| <b>Initial condition</b>  | The SUT is ready to receive a "Registry Stored Query" message using SOAP 1.2 from the simulated HIS receiver launched by the test tool.                                                                                                                                                           |                                         |                 |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated HIS receiver sends a SOAP 1.2 message containing an SAML 2.0 assertion with optional parameter "subject role" to the HIS sender under test.</li> <li>The HIS sender under test responds to the "Registry Stored Query" correctly.</li> </ol> |                                         |                 |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                                     |                                         |                 |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                   |                                         |                 |  |
+
+|                           |                                                                                                                                                                                                                                                                                                    |                                         |                 |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|-----------------|--|
+| <b>TP Id</b>              | TP/HIS/SEN/CM/BV-021                                                                                                                                                                                                                                                                               |                                         |                 |  |
+| <b>TP label</b>           | HIS Registry Stored Query – XUA++ with optional parameter 'authz consent'                                                                                                                                                                                                                          |                                         |                 |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                        | [ITU-T H.813]                           |                 |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                              | ConsentXDSb-9; O                        |                 |  |
+|                           | <b>Spec</b>                                                                                                                                                                                                                                                                                        | [IHE ITI-TF-2], Volume 2b, Section 3.40 |                 |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                              | Assertion-3; M                          | ExpActions-1; M |  |
+| <b>Test purpose</b>       | Check that:<br>HIS sender does not report any error when it receives a correct SAML 2.0 Assertion                                                                                                                                                                                                  |                                         |                 |  |
+| <b>Applicability</b>      | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012 AND C_HRN_SEN_013                                                                                                                                                                                                                                |                                         |                 |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                    |                                         |                 |  |
+| <b>Initial condition</b>  | The SUT is ready to receive a "Registry Stored Query" message using SOAP 1.2 from the simulated HIS receiver launched by the test tool.                                                                                                                                                            |                                         |                 |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated HIS receiver sends a SOAP 1.2 message containing an SAML 2.0 assertion with optional parameter "authz consent" to the HIS sender under test.</li> <li>The HIS sender under test responds to the "Registry Stored Query" correctly.</li> </ol> |                                         |                 |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                                      |                                         |                 |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                    |                                         |                 |  |
+
+|                           |                                                                                                                                                                                                                                                                                                     |                                         |                 |  |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|-----------------|--|
+| <b>TP Id</b>              | TP/HIS/SEN/CM/BV-022                                                                                                                                                                                                                                                                                |                                         |                 |  |
+| <b>TP label</b>           | HIS Registry Stored Query – XUA++ with optional parameter 'purpose of use'                                                                                                                                                                                                                          |                                         |                 |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                         | [ITU-T H.813]                           |                 |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                               | ConsentXDSb-9; O                        |                 |  |
+|                           | <b>Spec</b>                                                                                                                                                                                                                                                                                         | [IHE ITI-TF-2], Volume 2b, Section 3.40 |                 |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                               | Assertion-3; M                          | ExpActions-1; M |  |
+| <b>Test purpose</b>       | Check that:<br>HIS sender does not report any error when it receives a correct SAML 2.0 Assertion                                                                                                                                                                                                   |                                         |                 |  |
+| <b>Applicability</b>      | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012 AND C_HRN_SEN_013                                                                                                                                                                                                                                 |                                         |                 |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                     |                                         |                 |  |
+| <b>Initial condition</b>  | The SUT is ready to receive a "Registry Stored Query" message using SOAP 1.2 from the simulated HIS receiver launched by the test tool.                                                                                                                                                             |                                         |                 |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated HIS receiver sends a SOAP 1.2 message containing an SAML 2.0 assertion with optional parameter 'purpose of use' to the HIS sender under test.</li> <li>The HIS sender under test responds to the "Registry Stored Query" correctly.</li> </ol> |                                         |                 |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                                       |                                         |                 |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                     |                                         |                 |  |
+
+|                 |                                                 |                      |                      |               |
+|-----------------|-------------------------------------------------|----------------------|----------------------|---------------|
+| <b>TP Id</b>    | TP/HIS/SEN/CM/BV-023                            |                      |                      |               |
+| <b>TP label</b> | HIS Registry and Repository information mapping |                      |                      |               |
+| <b>Coverage</b> | <b>Spec</b>                                     | [ITU-T H.813]        |                      |               |
+|                 | <b>Testable items</b>                           | ConsentSenderXDR3; M | ConsentSenderXDR5; M | XDSDEMD-1; O  |
+|                 |                                                 | XDSDEMD-2; M         | XDSDEMD-3; M         | XDSDEMD-4; M  |
+|                 |                                                 | XDSDEMD-5; M         | XDSDEMD-6; M         | XDSDEMD-7; M  |
+|                 |                                                 | XDSDEMD-8; O         | XDSDEMD-9; O         | XDSDEMD-10; M |
+|                 |                                                 | XDSDEMD-11; M        | XDSDEMD-12; M        | XDSDEMD-13; M |
+|                 |                                                 | XDSDEMD-14; M        | XDSDEMD-15; O        | XDSDEMD-16; M |
+|                 |                                                 | XDSDEMD-17; O        | XDSDEMD-18; M        | XDSDEMD-19; M |
+|                 |                                                 | XDSDEMD-20; M        | XDSDEMD-21; M        | XDSDEMD-22; M |
+|                 |                                                 | XDSDEMD-23; M        | XDSDEMD-24; M        | XDSDEMD-25; O |
+|                 |                                                 | XDSDEMD-26; O        | XDSDEMD-27; O        | XDSDEMD-28; M |
+|                 |                                                 | XDSDEMD-29; M        | XDSDEMD-30; M        | XDSDEMD-31; M |
+|                 |                                                 | XDSDEMD-32; M        | XDSDEMD-33; M        | XDSDEMD-34; M |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                         |                     |               |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|---------------------|---------------|--|
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | XDSDEMD-35; M                           | XDSDEMD-35; M       | XDSDEMD-37; M |  |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | XDSDEMD-38; M                           | XDSDEMD-39; M       | XDSDEMD-40; O |  |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | XDSDEMD-41; M                           | XDSDEMD-42; M       | XDSDEMD-43; M |  |
+|                           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [IHE ITI-TF-2], Volume 2b, Section 3.40 |                     |               |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ProvideScope1; M                        | ProvideProtocol9; M |               |  |
+| <b>Test purpose</b>       | Check that:<br>HIS sender correctly implements Registry and Repository actors                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                         |                     |               |  |
+| <b>Applicability</b>      | C_HRN_SEN_000 AND C_HRN_SEN_001 AND C_HRN_SEN_012 AND C_HRN_SEN_013                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                         |                     |               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                         |                     |               |  |
+| <b>Initial condition</b>  | The SUT is ready to receive a "Registry Stored Query" message using SOAP 1.2 and a "Retrieve Document Set" using SOAP 1.2 from the simulated HIS receiver launched by the test tool.                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                         |                     |               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated HIS receiver sends a SOAP 1.2 message containing an AdhocQueryRequest to the registry.</li> <li>2. The HIS sender under test responds to the "Registry Stored Query" correctly.</li> <li>3. The simulated HIS receiver sends a SOAP 1.2 message containing a 2Retrieve Document Set" to the registry.</li> <li>4. The HIS sender under test responds to the "Retrieve Document Set".</li> <li>5. The test tool checks that: <ol style="list-style-type: none"> <li>a. the consent directive document Uniqueld maps onto Registry Query Response XSDocumentEntry.Uniqueld.</li> </ol> </li> </ol> |                                         |                     |               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• All steps are as specified within the test procedure above.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                         |                     |               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                         |                     |               |  |
+
+# Annex B
+
+## Testable item mapping, validation and XML schemas
+
+(This annex forms an integral part of this Recommendation.)
+
+### B.1 Testable item mapping validation between PHMR and metadata
+
+The following mapping tables describe the specific test tool message interchange for each of the test purposes noted in Annex A. As the interchange of messages is quite simple (reception of the PHM report from the HIS sender and return of an ACK response), it is important to break out the PHM report content and its mapping with the metadata headers to ensure that each of them has been verified.
+
+#### B.1.1 For TP/HIS/SEN/XSV/BV-000
+
+**Table B-1-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/XSV/BV-000**
+
+| TI                                                                                                            | Validation type | Constraint                                                                                                                                                                                                                                                                                                                                                   | Qualifier                                      |                                                                                                               |                                                |
+|---------------------------------------------------------------------------------------------------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|---------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| XDSDEMD-18; M                                                                                                 | Mapping         | <p>There are no PHM report elements; however, if an element appears, the structure of the metadata elements is checked:</p> <table border="1" style="width: 100%;"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>@"//*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/rim:Slot[@name='hash']"</td> </tr> </table> | xPath of METADATA element                      | @"//*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/rim:Slot[@name='hash']" | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of METADATA element                                                                                     |                 |                                                                                                                                                                                                                                                                                                                                                              |                                                |                                                                                                               |                                                |
+| @"//*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/rim:Slot[@name='hash']" |                 |                                                                                                                                                                                                                                                                                                                                                              |                                                |                                                                                                               |                                                |
+| XDSDEMD-33; M                                                                                                 | Mapping         | <p>There are no PHM report elements, however, if an element appears, the structure of the metadata elements is checked:</p> <table border="1" style="width: 100%;"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>@"//*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/rim:Slot[@name='size']"</td> </tr> </table> | xPath of METADATA element                      | @"//*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/rim:Slot[@name='size']" | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of METADATA element                                                                                     |                 |                                                                                                                                                                                                                                                                                                                                                              |                                                |                                                                                                               |                                                |
+| @"//*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/rim:Slot[@name='size']" |                 |                                                                                                                                                                                                                                                                                                                                                              |                                                |                                                                                                               |                                                |
+| XDSDEMD-7; M                                                                                                  | Mapping         | <p>There are no PHM report elements, however, if an element appears, the structure of the metadata elements is checked:</p>                                                                                                                                                                                                                                  | MANDATORY: FAIL if constraint is not satisfied |                                                                                                               |                                                |
+
+**Table B-1-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/XSV/BV-000**
+
+| TI            | Validation type | Constraint                                                                                                                                                                                                                                                                                                                                          | Qualifier                                      |
+|---------------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+|               |                 | <p>xPath of METADATA element</p> <p>@''/*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/rim:Classification[@classificationScheme='um:uuid:41a5887f-8865-4c09-adf7-e362475b143a']"</p>                                                                                                                             |                                                |
+| XDSDEMD-16; M | Mapping         | <p>There are no PHM report elements, however, if an element appears, the structure of the metadata elements is checked:</p> <p>xPath of METADATA element</p> <p>@''/*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/rim:Classification[@classificationScheme='um:uuid:a09d5840-386c-46f2-b5ad-9c3699a4309d']"</p> | MANDATORY: FAIL if constraint is not satisfied |
+| XDSDEMD-19; M | Mapping         | <p>There are no PHM report elements, however, if an element appears, the structure of the metadata elements is checked:</p> <p>xPath of METADATA element</p> <p>@''/*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/rim:Classification[@classificationScheme='um:uuid:f33fb8ac-18af-42cc-ae0e-ed0b0bdb91e1']"</p> | MANDATORY: FAIL if constraint is not satisfied |
+| XDSDEMD-29; M | Mapping         | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <p>xPath of METADATA element</p> <p>@''/*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/rim:Classification[@classificationScheme='um:uuid:cccf5598-8b07-4b77-a05e-ae952c785ead']"</p>                                  | MANDATORY: FAIL if constraint is not satisfied |
+| XDSDEMD-24; M | Mapping         | <p>There are no PHM report elements, however, if an element appears, the structure of the metadata elements is checked:</p> <p>xPath of METADATA element</p> <p>@''/*[local-</p>                                                                                                                                                                    | MANDATORY: FAIL if constraint is not satisfied |
+
+**Table B-1-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/XSV/BV-000**
+
+| TI                                                                                                                                                                                         | Validation type | Constraint                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Qualifier                 |                                                                                                                                                                                            |                                                                                                                        |                                                |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+|                                                                                                                                                                                            |                 | name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/@mimeType"                                                                                                                                                                                                                                                                                                                                                                           |                           |                                                                                                                                                                                            |                                                                                                                        |                                                |
+| XDSSSDMD-13; M                                                                                                                                                                             | Mapping         | <p>There are no PHM report elements, however, if an element appears, the structure of the metadata elements is checked:</p> <table border="1"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>@"/*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/@id"</td> </tr> <tr> <td>@"/*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:RegistryPackage/rim:Slot[@name='submissionTime']"</td> </tr> </table> | xPath of METADATA element | @"/*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/@id"                                                                                                  | @"/*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:RegistryPackage/rim:Slot[@name='submissionTime']" | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of METADATA element                                                                                                                                                                  |                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                           |                                                                                                                                                                                            |                                                                                                                        |                                                |
+| @"/*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/@id"                                                                                                  |                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                           |                                                                                                                                                                                            |                                                                                                                        |                                                |
+| @"/*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:RegistryPackage/rim:Slot[@name='submissionTime']"                                                                     |                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                           |                                                                                                                                                                                            |                                                                                                                        |                                                |
+| XDSSSDMD-8; M                                                                                                                                                                              | Mapping         | <p>There are no PHM report elements, however, if an element appears, the structure of the metadata elements is checked:</p> <table border="1"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>@"/*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:RegistryPackage/rim:Classification[@classificationScheme='urn:uuid:aa543740-bdda-424e-8c96-df4873be8500']"</td> </tr> </table>                                                      | xPath of METADATA element | @"/*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:RegistryPackage/rim:Classification[@classificationScheme='urn:uuid:aa543740-bdda-424e-8c96-df4873be8500']"            | MANDATORY: FAIL if constraint is not satisfied                                                                         |                                                |
+| xPath of METADATA element                                                                                                                                                                  |                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                           |                                                                                                                                                                                            |                                                                                                                        |                                                |
+| @"/*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:RegistryPackage/rim:Classification[@classificationScheme='urn:uuid:aa543740-bdda-424e-8c96-df4873be8500']"            |                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                           |                                                                                                                                                                                            |                                                                                                                        |                                                |
+| XDSSSDMD-12; M                                                                                                                                                                             | Mapping         | <p>There are no PHM report elements, however, if an element appears, the structure of the metadata elements is checked:</p> <table border="1"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>@"/*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:RegistryPackage/rim:ExternalIdentifier[@identificationScheme='urn:uuid:554ac39e-e3fe-47fe-b233-965d2a147832']/@value"</td> </tr> </table>                                           | xPath of METADATA element | @"/*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:RegistryPackage/rim:ExternalIdentifier[@identificationScheme='urn:uuid:554ac39e-e3fe-47fe-b233-965d2a147832']/@value" | MANDATORY: FAIL if constraint is not satisfied                                                                         |                                                |
+| xPath of METADATA element                                                                                                                                                                  |                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                           |                                                                                                                                                                                            |                                                                                                                        |                                                |
+| @"/*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:RegistryPackage/rim:ExternalIdentifier[@identificationScheme='urn:uuid:554ac39e-e3fe-47fe-b233-965d2a147832']/@value" |                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                           |                                                                                                                                                                                            |                                                                                                                        |                                                |
+| XDSDEMD-18; M                                                                                                                                                                              | Mapping         | <p>There are no PHM report elements, however, if an element appears, the structure of the metadata elements is checked:</p> <table border="1"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>@"/*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/rim:Slot[@name='hash']"</td> </tr> </table>                                                                                                                         | xPath of METADATA element | @"/*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/rim:Slot[@name='hash']"                                                                               | MANDATORY: FAIL if constraint is not satisfied                                                                         |                                                |
+| xPath of METADATA element                                                                                                                                                                  |                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                           |                                                                                                                                                                                            |                                                                                                                        |                                                |
+| @"/*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/rim:Slot[@name='hash']"                                                                               |                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                           |                                                                                                                                                                                            |                                                                                                                        |                                                |
+
+#### B.1.2 For TP/HIS/SEN/XMSV/BV-000
+
+**Table B-1-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/XMSV/BV-000**
+
+| TI                                                                                         | Validation type                                                                        | Constraint                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Qualifier                                                   |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|---------------------------|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------------------------------------------|---------------------------------------------------------------------------------|-----------------------------------------------------------------|--------------------------------------------------------------------------------------|------------------------------------------------|
+| MGDC_XDR-6; R                                                                              | C# code                                                                                | The CDG HIS Sender application should not include information that is not present within the PHM report.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | RECOMMENDED: WARNING message if constraint is not satisfied |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| MGDC_XDR-7; M                                                                              | Mapping                                                                                | This testable item is implicitly tested in the rest of the testable items.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | MANDATORY: FAIL if constraint is not satisfied              |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| PHMAG-1; M                                                                                 | C# code                                                                                | CDG HIS Senders shall communicate all attachments referenced or contained in the PHM report document.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | MANDATORY: FAIL if constraint is not satisfied              |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| PHMAG-2; M                                                                                 | C# code                                                                                | CDG HIS Senders shall communicate all attachments specified in the PHM report in the same message.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | MANDATORY: FAIL if constraint is not satisfied              |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| XDSDEMD-1; O                                                                               | Mapping                                                                                | <p>There are no PHM report elements, if the element appears the structure of the metadata elements is checked:</p> <table border="1"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>/@status</td> </tr> </table>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | xPath of METADATA element                                   | /@status                  | OPTIONAL: INFO message if constraint is not satisfied                                      |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| xPath of METADATA element                                                                  |                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                             |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| /@status                                                                                   |                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                             |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| XDSDEMD-2; M                                                                               | Mapping                                                                                | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:representedOrganization/v3:name/text()</td> <td>/rim:Classification/rim:Slot[@name='authorInstitution']/rim:ValueList/rim:Value/text()</td> </tr> <tr> <td>/v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:assignedPerson/v3:name</td> <td>/rim:Classification/rim:Slot[@name='authorPerson']/rim:ValueList/rim:Value/text()</td> </tr> <tr> <td>/v3:ClinicalDocument/v3:author/v3:participationFunction/text()</td> <td>/rim:Classification/rim:Slot[@name='authorRole']/rim:ValueList/rim:Value/text()</td> </tr> <tr> <td>/v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:code/text()</td> <td>/rim:Classification/rim:Slot[@name='authorSpecialty']/rim:ValueList/rim:Value/text()</td> </tr> </tbody> </table> | xPath of PHM report element                                 | xPath of METADATA element | /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:representedOrganization/v3:name/text() | /rim:Classification/rim:Slot[@name='authorInstitution']/rim:ValueList/rim:Value/text() | /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:assignedPerson/v3:name | /rim:Classification/rim:Slot[@name='authorPerson']/rim:ValueList/rim:Value/text() | /v3:ClinicalDocument/v3:author/v3:participationFunction/text() | /rim:Classification/rim:Slot[@name='authorRole']/rim:ValueList/rim:Value/text() | /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:code/text() | /rim:Classification/rim:Slot[@name='authorSpecialty']/rim:ValueList/rim:Value/text() | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                                | xPath of METADATA element                                                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                             |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:representedOrganization/v3:name/text() | /rim:Classification/rim:Slot[@name='authorInstitution']/rim:ValueList/rim:Value/text() |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                             |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:assignedPerson/v3:name                 | /rim:Classification/rim:Slot[@name='authorPerson']/rim:ValueList/rim:Value/text()      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                             |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| /v3:ClinicalDocument/v3:author/v3:participationFunction/text()                             | /rim:Classification/rim:Slot[@name='authorRole']/rim:ValueList/rim:Value/text()        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                             |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:code/text()                            | /rim:Classification/rim:Slot[@name='authorSpecialty']/rim:ValueList/rim:Value/text()   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                             |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+
+**Table B-1-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/XMSV/BV-000**
+
+| TI                                                                                         | Validation type                                                                        | Constraint                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Qualifier                   |                           |                                                                                            |                                                                                        |                                                |
+|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|---------------------------|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|------------------------------------------------|
+| XDSDEMD-3; M                                                                               | Mapping                                                                                | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:representedOrganization/v3:name/text()</td> <td>/rim:Classification/rim:Slot[@name='authorInstitution']/rim:ValueList/rim:Value/text()</td> </tr> </tbody> </table> | xPath of PHM report element | xPath of METADATA element | /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:representedOrganization/v3:name/text() | /rim:Classification/rim:Slot[@name='authorInstitution']/rim:ValueList/rim:Value/text() | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                                | xPath of METADATA element                                                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                             |                           |                                                                                            |                                                                                        |                                                |
+| /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:representedOrganization/v3:name/text() | /rim:Classification/rim:Slot[@name='authorInstitution']/rim:ValueList/rim:Value/text() |                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                             |                           |                                                                                            |                                                                                        |                                                |
+| XDSDEMD-4; M                                                                               | Mapping                                                                                | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:assignedPerson/v3:name</td> <td>/rim:Classification/rim:Slot[@name='authorPerson']/rim:ValueList/rim:Value/text()</td> </tr> </tbody> </table>                      | xPath of PHM report element | xPath of METADATA element | /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:assignedPerson/v3:name                 | /rim:Classification/rim:Slot[@name='authorPerson']/rim:ValueList/rim:Value/text()      | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                                | xPath of METADATA element                                                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                             |                           |                                                                                            |                                                                                        |                                                |
+| /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:assignedPerson/v3:name                 | /rim:Classification/rim:Slot[@name='authorPerson']/rim:ValueList/rim:Value/text()      |                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                             |                           |                                                                                            |                                                                                        |                                                |
+| XDSDEMD-5; M                                                                               | Mapping                                                                                | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:participationFunction/v3:code/text()</td> <td>/rim:Classification/rim:Slot[@name='authorRole']/rim:ValueList/rim:Value/text()</td> </tr> </tbody> </table>          | xPath of PHM report element | xPath of METADATA element | /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:participationFunction/v3:code/text()   | /rim:Classification/rim:Slot[@name='authorRole']/rim:ValueList/rim:Value/text()        | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                                | xPath of METADATA element                                                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                             |                           |                                                                                            |                                                                                        |                                                |
+| /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:participationFunction/v3:code/text()   | /rim:Classification/rim:Slot[@name='authorRole']/rim:ValueList/rim:Value/text()        |                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                             |                           |                                                                                            |                                                                                        |                                                |
+| XDSDEMD-6; M                                                                               | Mapping                                                                                | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:participationFunction/text()</td> <td>/rim:Classification/rim:Slot[@name='authorSpecialty']/rim:ValueList/rim:Value/text()</td> </tr> </tbody> </table>             | xPath of PHM report element | xPath of METADATA element | /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:participationFunction/text()           | /rim:Classification/rim:Slot[@name='authorSpecialty']/rim:ValueList/rim:Value/text()   | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                                | xPath of METADATA element                                                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                             |                           |                                                                                            |                                                                                        |                                                |
+| /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:participationFunction/text()           | /rim:Classification/rim:Slot[@name='authorSpecialty']/rim:ValueList/rim:Value/text()   |                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                             |                           |                                                                                            |                                                                                        |                                                |
+
+**Table B-1-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/XMSV/BV-000**
+
+| TI                                                                                                                             | Validation type                                                                                                                | Constraint                                                                                                                                                                                                                                                                                                                                                                                                              | Qualifier                   |                                                                                                                                |                                                       |                                                                                                                                |                                                |
+|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| XDSDEMD-8; O                                                                                                                   | Mapping                                                                                                                        | <p>There are no PHM report elements, if the element appears the structure of the metadata elements is checked</p> <table border="1"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>/rim:Classification[@classificationScheme='urn:uuid:41a5887f-8865-4c09-adf7-e362475b143a']/rim:Name/rim:LocalizedString/@value</td> </tr> </table>                                                                          | xPath of METADATA element   | /rim:Classification[@classificationScheme='urn:uuid:41a5887f-8865-4c09-adf7-e362475b143a']/rim:Name/rim:LocalizedString/@value | OPTIONAL: INFO message if constraint is not satisfied |                                                                                                                                |                                                |
+| xPath of METADATA element                                                                                                      |                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                         |                             |                                                                                                                                |                                                       |                                                                                                                                |                                                |
+| /rim:Classification[@classificationScheme='urn:uuid:41a5887f-8865-4c09-adf7-e362475b143a']/rim:Name/rim:LocalizedString/@value |                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                         |                             |                                                                                                                                |                                                       |                                                                                                                                |                                                |
+| XDSDEMD-9; O                                                                                                                   | Mapping                                                                                                                        | <p>There are no PHM report elements, if the element appears the structure of the metadata elements is checked</p> <table border="1"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>/rim:Description/rim:LocalizedString/@value</td> </tr> </table>                                                                                                                                                             | xPath of METADATA element   | /rim:Description/rim:LocalizedString/@value                                                                                    | OPTIONAL: INFO message if constraint is not satisfied |                                                                                                                                |                                                |
+| xPath of METADATA element                                                                                                      |                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                         |                             |                                                                                                                                |                                                       |                                                                                                                                |                                                |
+| /rim:Description/rim:LocalizedString/@value                                                                                    |                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                         |                             |                                                                                                                                |                                                       |                                                                                                                                |                                                |
+| XDSDEMD-10; M                                                                                                                  | Mapping                                                                                                                        | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <tr> <td>xPath of PHM report element</td> <td>xPath of METADATA element</td> </tr> <tr> <td>/v3:ClinicalDocument/v3:confidentialityCode/@code</td> <td>/rim:Classification[@classificationScheme='urn:uuid:f4f85eac-e6cb-4883-b524-f2705394840f']/@nodeRepresentation</td> </tr> </table>                 | xPath of PHM report element | xPath of METADATA element                                                                                                      | /v3:ClinicalDocument/v3:confidentialityCode/@code     | /rim:Classification[@classificationScheme='urn:uuid:f4f85eac-e6cb-4883-b524-f2705394840f']/@nodeRepresentation                 | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                                                                    | xPath of METADATA element                                                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                         |                             |                                                                                                                                |                                                       |                                                                                                                                |                                                |
+| /v3:ClinicalDocument/v3:confidentialityCode/@code                                                                              | /rim:Classification[@classificationScheme='urn:uuid:f4f85eac-e6cb-4883-b524-f2705394840f']/@nodeRepresentation                 |                                                                                                                                                                                                                                                                                                                                                                                                                         |                             |                                                                                                                                |                                                       |                                                                                                                                |                                                |
+| XDSDEMD-11; M                                                                                                                  | Mapping                                                                                                                        | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <tr> <td>xPath of PHM report element</td> <td>xPath of METADATA element</td> </tr> <tr> <td>/v3:ClinicalDocument/v3:confidentialityCode/@code</td> <td>/rim:Classification[@classificationScheme='urn:uuid:f4f85eac-e6cb-4883-b524-f2705394840f']/rim:Name/rim:LocalizedString/@value</td> </tr> </table> | xPath of PHM report element | xPath of METADATA element                                                                                                      | /v3:ClinicalDocument/v3:confidentialityCode/@code     | /rim:Classification[@classificationScheme='urn:uuid:f4f85eac-e6cb-4883-b524-f2705394840f']/rim:Name/rim:LocalizedString/@value | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                                                                    | xPath of METADATA element                                                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                         |                             |                                                                                                                                |                                                       |                                                                                                                                |                                                |
+| /v3:ClinicalDocument/v3:confidentialityCode/@code                                                                              | /rim:Classification[@classificationScheme='urn:uuid:f4f85eac-e6cb-4883-b524-f2705394840f']/rim:Name/rim:LocalizedString/@value |                                                                                                                                                                                                                                                                                                                                                                                                                         |                             |                                                                                                                                |                                                       |                                                                                                                                |                                                |
+
+**Table B-1-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/XMSV/BV-000**
+
+| TI                                                                                                                             | Validation type                                                                                                | Constraint                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Qualifier                   |                                                                                                                                |                                                                    |                                                                                                                |                                                |
+|--------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| XDSDEMD-12; M                                                                                                                  | Mapping                                                                                                        | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:effectiveTime/@value</td> <td>/rim:Slot[@name='creationTime']/rim:ValueList/rim:Value/text()</td> </tr> </tbody> </table>                                                                       | xPath of PHM report element | xPath of METADATA element                                                                                                      | /v3:ClinicalDocument/v3:effectiveTime/@value                       | /rim:Slot[@name='creationTime']/rim:ValueList/rim:Value/text()                                                 | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                                                                    | xPath of METADATA element                                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                             |                                                                                                                                |                                                                    |                                                                                                                |                                                |
+| /v3:ClinicalDocument/v3:effectiveTime/@value                                                                                   | /rim:Slot[@name='creationTime']/rim:ValueList/rim:Value/text()                                                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                             |                                                                                                                                |                                                                    |                                                                                                                |                                                |
+| XDSDEMD-14; M                                                                                                                  | Mapping                                                                                                        | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:documentationOf/v3:serviceEvent/@classCode</td> <td>/rim:Classification[@classificationScheme='urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4']/@nodeRepresentation</td> </tr> </tbody> </table> | xPath of PHM report element | xPath of METADATA element                                                                                                      | /v3:ClinicalDocument/v3:documentationOf/v3:serviceEvent/@classCode | /rim:Classification[@classificationScheme='urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4']/@nodeRepresentation | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                                                                    | xPath of METADATA element                                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                             |                                                                                                                                |                                                                    |                                                                                                                |                                                |
+| /v3:ClinicalDocument/v3:documentationOf/v3:serviceEvent/@classCode                                                             | /rim:Classification[@classificationScheme='urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4']/@nodeRepresentation |                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                             |                                                                                                                                |                                                                    |                                                                                                                |                                                |
+| XDSDEMD-15; O                                                                                                                  | Mapping                                                                                                        | <p>There are no PHM report elements, if the element appears the structure of the metadata elements is checked</p> <table border="1"> <thead> <tr> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/rim:Classification[@classificationScheme='urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4']/rim:Name/rim:LocalizedString/@value</td> </tr> </tbody> </table>                                                                           | xPath of METADATA element   | /rim:Classification[@classificationScheme='urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4']/rim:Name/rim:LocalizedString/@value | OPTIONAL: INFO message if constraint is not satisfied              |                                                                                                                |                                                |
+| xPath of METADATA element                                                                                                      |                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                             |                                                                                                                                |                                                                    |                                                                                                                |                                                |
+| /rim:Classification[@classificationScheme='urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4']/rim:Name/rim:LocalizedString/@value |                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                             |                                                                                                                                |                                                                    |                                                                                                                |                                                |
+| XDSDEMD-16; M                                                                                                                  | Mapping                                                                                                        | <p>There are no PHM report elements, if the element appears the structure of the metadata elements is checked:</p> <table border="1"> <thead> <tr> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/rim:Classification[@classificationScheme='urn:uuid:a09d5840-386c-46f2-b5ad-9c3699a4309d']</td> </tr> </tbody> </table>                                                                                                              | xPath of METADATA element   | /rim:Classification[@classificationScheme='urn:uuid:a09d5840-386c-46f2-b5ad-9c3699a4309d']                                     | MANDATORY: FAIL if constraint is not satisfied                     |                                                                                                                |                                                |
+| xPath of METADATA element                                                                                                      |                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                             |                                                                                                                                |                                                                    |                                                                                                                |                                                |
+| /rim:Classification[@classificationScheme='urn:uuid:a09d5840-386c-46f2-b5ad-9c3699a4309d']                                     |                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                             |                                                                                                                                |                                                                    |                                                                                                                |                                                |
+
+**Table B-1-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/XMSV/BV-000**
+
+| TI                                                                                                                             | Validation type                                                     | Constraint                                                                                                                                                                                                                                                                                                                                           | Qualifier                   |                                                                                                                                |                                                       |                                                                     |                                                |
+|--------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|---------------------------------------------------------------------|------------------------------------------------|
+| XDSDEMD-17; O                                                                                                                  | Mapping                                                             | <p>There are no PHM report elements, if the element appears the structure of the metadata elements is checked</p> <table border="1"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>/rim:Classification[@classificationScheme='urn:uuid:a09d5840-386c-46f2-b5ad-9c3699a4309d']/rim:Name/rim:LocalizedString/@value</td> </tr> </table>       | xPath of METADATA element   | /rim:Classification[@classificationScheme='urn:uuid:a09d5840-386c-46f2-b5ad-9c3699a4309d']/rim:Name/rim:LocalizedString/@value | OPTIONAL: INFO message if constraint is not satisfied |                                                                     |                                                |
+| xPath of METADATA element                                                                                                      |                                                                     |                                                                                                                                                                                                                                                                                                                                                      |                             |                                                                                                                                |                                                       |                                                                     |                                                |
+| /rim:Classification[@classificationScheme='urn:uuid:a09d5840-386c-46f2-b5ad-9c3699a4309d']/rim:Name/rim:LocalizedString/@value |                                                                     |                                                                                                                                                                                                                                                                                                                                                      |                             |                                                                                                                                |                                                       |                                                                     |                                                |
+| XDSDEMD-20; M                                                                                                                  | Mapping                                                             | <p>There are no PHM report elements, if the element appears the structure of the metadata elements is checked:</p> <table border="1"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>/rim:Classification[@classificationScheme='urn:uuid:f33fb8ac-18af-42cc-ae0e-ed0b0bdb91e1']/rim:Name/rim:LocalizedString/@value</td> </tr> </table>      | xPath of METADATA element   | /rim:Classification[@classificationScheme='urn:uuid:f33fb8ac-18af-42cc-ae0e-ed0b0bdb91e1']/rim:Name/rim:LocalizedString/@value | MANDATORY: FAIL if constraint is not satisfied        |                                                                     |                                                |
+| xPath of METADATA element                                                                                                      |                                                                     |                                                                                                                                                                                                                                                                                                                                                      |                             |                                                                                                                                |                                                       |                                                                     |                                                |
+| /rim:Classification[@classificationScheme='urn:uuid:f33fb8ac-18af-42cc-ae0e-ed0b0bdb91e1']/rim:Name/rim:LocalizedString/@value |                                                                     |                                                                                                                                                                                                                                                                                                                                                      |                             |                                                                                                                                |                                                       |                                                                     |                                                |
+| XDSDEMD-21; M                                                                                                                  | Mapping                                                             | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <tr> <td>xPath of PHM report element</td> <td>xPath of METADATA element</td> </tr> <tr> <td>/v3:ClinicalDocument/v3:intendedRecipient</td> <td>/rim:Slot[@name='intendedRecipient']/rim:ValueList/rim:Value/text()</td> </tr> </table> | xPath of PHM report element | xPath of METADATA element                                                                                                      | /v3:ClinicalDocument/v3:intendedRecipient             | /rim:Slot[@name='intendedRecipient']/rim:ValueList/rim:Value/text() | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                                                                    | xPath of METADATA element                                           |                                                                                                                                                                                                                                                                                                                                                      |                             |                                                                                                                                |                                                       |                                                                     |                                                |
+| /v3:ClinicalDocument/v3:intendedRecipient                                                                                      | /rim:Slot[@name='intendedRecipient']/rim:ValueList/rim:Value/text() |                                                                                                                                                                                                                                                                                                                                                      |                             |                                                                                                                                |                                                       |                                                                     |                                                |
+| XDSDEMD-22; M                                                                                                                  | Mapping                                                             | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <tr> <td>xPath of PHM report element</td> <td>xPath of METADATA element</td> </tr> <tr> <td>/v3:ClinicalDocument/v3:languageCode/@code</td> <td>/rim:Slot[@name='languageCode']/rim:ValueList/rim:Value/text()</td> </tr> </table>     | xPath of PHM report element | xPath of METADATA element                                                                                                      | /v3:ClinicalDocument/v3:languageCode/@code            | /rim:Slot[@name='languageCode']/rim:ValueList/rim:Value/text()      | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                                                                    | xPath of METADATA element                                           |                                                                                                                                                                                                                                                                                                                                                      |                             |                                                                                                                                |                                                       |                                                                     |                                                |
+| /v3:ClinicalDocument/v3:languageCode/@code                                                                                     | /rim:Slot[@name='languageCode']/rim:ValueList/rim:Value/text()      |                                                                                                                                                                                                                                                                                                                                                      |                             |                                                                                                                                |                                                       |                                                                     |                                                |
+
+**Table B-1-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/XMSV/BV-000**
+
+| TI                                                                                            | Validation type                                                      | Constraint                                                                                                                                                                                                                                                                                                                                                                                                                           | Qualifier                   |                                                                                               |                                                                                        |                                                                      |                                                |
+|-----------------------------------------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|-----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------------------|
+| XDSDEMD-23; M                                                                                 | Mapping                                                              | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:legalAuthenticator/v3:assignedEntity/v3:assignedPerson/v3:name</td> <td>/rim:Slot[@name='legalAuthenticator']/rim:ValueList/rim:Value/text()</td> </tr> </tbody> </table> | xPath of PHM report element | xPath of METADATA element                                                                     | /v3:ClinicalDocument/v3:legalAuthenticator/v3:assignedEntity/v3:assignedPerson/v3:name | /rim:Slot[@name='legalAuthenticator']/rim:ValueList/rim:Value/text() | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                                   | xPath of METADATA element                                            |                                                                                                                                                                                                                                                                                                                                                                                                                                      |                             |                                                                                               |                                                                                        |                                                                      |                                                |
+| /v3:ClinicalDocument/v3:legalAuthenticator/v3:assignedEntity/v3:assignedPerson/v3:name        | /rim:Slot[@name='legalAuthenticator']/rim:ValueList/rim:Value/text() |                                                                                                                                                                                                                                                                                                                                                                                                                                      |                             |                                                                                               |                                                                                        |                                                                      |                                                |
+| XDSDEMD-24; M                                                                                 | Mapping                                                              | <p>There are no PHM report elements, if the element appears the structure of the metadata elements is checked:</p> <table border="1"> <thead> <tr> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/@mimeType</td> </tr> </tbody> </table>                                                                                                                                                                        | xPath of METADATA element   | /@mimeType                                                                                    | MANDATORY: FAIL if constraint is not satisfied                                         |                                                                      |                                                |
+| xPath of METADATA element                                                                     |                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                      |                             |                                                                                               |                                                                                        |                                                                      |                                                |
+| /@mimeType                                                                                    |                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                      |                             |                                                                                               |                                                                                        |                                                                      |                                                |
+| XDSDEMD-25; O                                                                                 | Mapping                                                              | <p>There are no PHM report elements, if the element appears the structure of the metadata elements is checked:</p> <table border="1"> <thead> <tr> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/rim:Association[@targetObject='urn:uuid:a6e06ca8-0c75-4064-9e5c-88b9045a96f6']</td> </tr> </tbody> </table>                                                                                                   | xPath of METADATA element   | /rim:Association[@targetObject='urn:uuid:a6e06ca8-0c75-4064-9e5c-88b9045a96f6']               | OPTIONAL: INFO message if constraint is not satisfied                                  |                                                                      |                                                |
+| xPath of METADATA element                                                                     |                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                      |                             |                                                                                               |                                                                                        |                                                                      |                                                |
+| /rim:Association[@targetObject='urn:uuid:a6e06ca8-0c75-4064-9e5c-88b9045a96f6']               |                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                      |                             |                                                                                               |                                                                                        |                                                                      |                                                |
+| XDSDEMD-26; O                                                                                 | Mapping                                                              | <p>There are no PHM report elements, if the element appears the structure of the metadata elements is checked:</p> <table border="1"> <thead> <tr> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/rim:Association[@targetObject='urn:uuid:a6e06ca8-0c75-4064-9e5c-88b9045a96f6']/@sourceObject</td> </tr> </tbody> </table>                                                                                     | xPath of METADATA element   | /rim:Association[@targetObject='urn:uuid:a6e06ca8-0c75-4064-9e5c-88b9045a96f6']/@sourceObject | OPTIONAL: INFO message if constraint is not satisfied                                  |                                                                      |                                                |
+| xPath of METADATA element                                                                     |                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                      |                             |                                                                                               |                                                                                        |                                                                      |                                                |
+| /rim:Association[@targetObject='urn:uuid:a6e06ca8-0c75-4064-9e5c-88b9045a96f6']/@sourceObject |                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                      |                             |                                                                                               |                                                                                        |                                                                      |                                                |
+| XDSDEMD-27; O                                                                                 | Mapping                                                              | <p>There are no PHM report elements, if the element appears the structure of the metadata elements is checked:</p> <table border="1"> <thead> <tr> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/rim:ObjectRef[@id='urn:uuid:a6e06ca8-0c75-4064-9e5c-88b9045a96f6']</td> </tr> </tbody> </table>                                                                                                               | xPath of METADATA element   | /rim:ObjectRef[@id='urn:uuid:a6e06ca8-0c75-4064-9e5c-88b9045a96f6']                           | OPTIONAL: INFO message if constraint is not satisfied                                  |                                                                      |                                                |
+| xPath of METADATA element                                                                     |                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                      |                             |                                                                                               |                                                                                        |                                                                      |                                                |
+| /rim:ObjectRef[@id='urn:uuid:a6e06ca8-0c75-4064-9e5c-88b9045a96f6']                           |                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                      |                             |                                                                                               |                                                                                        |                                                                      |                                                |
+
+**Table B-1-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/XMSV/BV-000**
+
+| TI                                                                                      | Validation type                                                                                     | Constraint                                                                                                                                                                                                                                                                                                                                                                                                                             | Qualifier                   |                           |                                                                                         |                                                                                                     |                                                |
+|-----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|---------------------------|-----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|------------------------------------------------|
+| XDSDEMD-28; M                                                                           | Mapping                                                                                             | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:recordTarget/v3:patientRole/v3:id</td> <td>/rim:ExternalIdentifier[@identificationScheme='urn:uuid:58a6f841-87b3-4a3e-92fd-a8ffe98427']/@value</td> </tr> </tbody> </table> | xPath of PHM report element | xPath of METADATA element | /v3:ClinicalDocument/v3:recordTarget/v3:patientRole/v3:id                               | /rim:ExternalIdentifier[@identificationScheme='urn:uuid:58a6f841-87b3-4a3e-92fd-a8ffe98427']/@value | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                             | xPath of METADATA element                                                                           |                                                                                                                                                                                                                                                                                                                                                                                                                                        |                             |                           |                                                                                         |                                                                                                     |                                                |
+| /v3:ClinicalDocument/v3:recordTarget/v3:patientRole/v3:id                               | /rim:ExternalIdentifier[@identificationScheme='urn:uuid:58a6f841-87b3-4a3e-92fd-a8ffe98427']/@value |                                                                                                                                                                                                                                                                                                                                                                                                                                        |                             |                           |                                                                                         |                                                                                                     |                                                |
+| XDSDEMD-31; M                                                                           | Mapping                                                                                             | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:documentationOf/v3:serviceEvent/v3:effectiveTime/v3:low/@value</td> <td>/rim:Slot[@name='serviceStartTime']/rim:ValueList/rim:Value/text()</td> </tr> </tbody> </table>     | xPath of PHM report element | xPath of METADATA element | /v3:ClinicalDocument/v3:documentationOf/v3:serviceEvent/v3:effectiveTime/v3:low/@value  | /rim:Slot[@name='serviceStartTime']/rim:ValueList/rim:Value/text()                                  | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                             | xPath of METADATA element                                                                           |                                                                                                                                                                                                                                                                                                                                                                                                                                        |                             |                           |                                                                                         |                                                                                                     |                                                |
+| /v3:ClinicalDocument/v3:documentationOf/v3:serviceEvent/v3:effectiveTime/v3:low/@value  | /rim:Slot[@name='serviceStartTime']/rim:ValueList/rim:Value/text()                                  |                                                                                                                                                                                                                                                                                                                                                                                                                                        |                             |                           |                                                                                         |                                                                                                     |                                                |
+| XDSDEMD-32; M                                                                           | Mapping                                                                                             | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:documentationOf/v3:serviceEvent/v3:effectiveTime/v3:high/@value</td> <td>/rim:Slot[@name='serviceStopTime']/rim:ValueList/rim:Value/text()</td> </tr> </tbody> </table>     | xPath of PHM report element | xPath of METADATA element | /v3:ClinicalDocument/v3:documentationOf/v3:serviceEvent/v3:effectiveTime/v3:high/@value | /rim:Slot[@name='serviceStopTime']/rim:ValueList/rim:Value/text()                                   | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                             | xPath of METADATA element                                                                           |                                                                                                                                                                                                                                                                                                                                                                                                                                        |                             |                           |                                                                                         |                                                                                                     |                                                |
+| /v3:ClinicalDocument/v3:documentationOf/v3:serviceEvent/v3:effectiveTime/v3:high/@value | /rim:Slot[@name='serviceStopTime']/rim:ValueList/rim:Value/text()                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                        |                             |                           |                                                                                         |                                                                                                     |                                                |
+| XDSDEMD-34; M                                                                           | Mapping                                                                                             | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:recordTarget/v3:patientRole/v3:id</td> <td>/rim:Slot[@name='sourcePatientId']/rim:ValueList/rim:Value/text()</td> </tr> </tbody> </table>                                   | xPath of PHM report element | xPath of METADATA element | /v3:ClinicalDocument/v3:recordTarget/v3:patientRole/v3:id                               | /rim:Slot[@name='sourcePatientId']/rim:ValueList/rim:Value/text()                                   | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                             | xPath of METADATA element                                                                           |                                                                                                                                                                                                                                                                                                                                                                                                                                        |                             |                           |                                                                                         |                                                                                                     |                                                |
+| /v3:ClinicalDocument/v3:recordTarget/v3:patientRole/v3:id                               | /rim:Slot[@name='sourcePatientId']/rim:ValueList/rim:Value/text()                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                        |                             |                           |                                                                                         |                                                                                                     |                                                |
+| XDSDEMD-35; M                                                                           | Mapping                                                                                             | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:recordTarget/v3:patientRole</td> <td>/rim:Slot[@name='sourcePatientInfo']/rim:ValueList</td> </tr> </tbody> </table>                                                        | xPath of PHM report element | xPath of METADATA element | /v3:ClinicalDocument/v3:recordTarget/v3:patientRole                                     | /rim:Slot[@name='sourcePatientInfo']/rim:ValueList                                                  | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                             | xPath of METADATA element                                                                           |                                                                                                                                                                                                                                                                                                                                                                                                                                        |                             |                           |                                                                                         |                                                                                                     |                                                |
+| /v3:ClinicalDocument/v3:recordTarget/v3:patientRole                                     | /rim:Slot[@name='sourcePatientInfo']/rim:ValueList                                                  |                                                                                                                                                                                                                                                                                                                                                                                                                                        |                             |                           |                                                                                         |                                                                                                     |                                                |
+
+**Table B-1-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/XMSV/BV-000**
+
+| TI                                        | Validation type                                                                                                                | Constraint                                                                                                                                                                                                                                                                                                                                                                                                                                        | Qualifier                   |                           |                                                       |                                                                                                                                |                                                |
+|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|---------------------------|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| XDSDEMD-36; M                             | Mapping                                                                                                                        | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:title/text()</td> <td>/rim:Name/rim:LocalizedString/@value</td> </tr> </tbody> </table>                                                                                                | xPath of PHM report element | xPath of METADATA element | /v3:ClinicalDocument/v3:title/text()                  | /rim:Name/rim:LocalizedString/@value                                                                                           | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element               | xPath of METADATA element                                                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                             |                           |                                                       |                                                                                                                                |                                                |
+| /v3:ClinicalDocument/v3:title/text()      | /rim:Name/rim:LocalizedString/@value                                                                                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                             |                           |                                                       |                                                                                                                                |                                                |
+| XDSDEMD-37; M                             | Mapping                                                                                                                        | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:code/@code</td> <td>/rim:Classification[@classificationScheme='urn:uuid:f0306f51-975f-434e-a61c-c59651d33983']/@nodeRepresentation</td> </tr> </tbody> </table>                        | xPath of PHM report element | xPath of METADATA element | /v3:ClinicalDocument/v3:code/@code                    | /rim:Classification[@classificationScheme='urn:uuid:f0306f51-975f-434e-a61c-c59651d33983']/@nodeRepresentation                 | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element               | xPath of METADATA element                                                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                             |                           |                                                       |                                                                                                                                |                                                |
+| /v3:ClinicalDocument/v3:code/@code        | /rim:Classification[@classificationScheme='urn:uuid:f0306f51-975f-434e-a61c-c59651d33983']/@nodeRepresentation                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                             |                           |                                                       |                                                                                                                                |                                                |
+| XDSDEMD-38; M                             | Mapping                                                                                                                        | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:code/@displayName</td> <td>/rim:Classification[@classificationScheme='urn:uuid:f0306f51-975f-434e-a61c-c59651d33983']/rim:Name/rim:LocalizedString/@value</td> </tr> </tbody> </table> | xPath of PHM report element | xPath of METADATA element | /v3:ClinicalDocument/v3:code/@displayName             | /rim:Classification[@classificationScheme='urn:uuid:f0306f51-975f-434e-a61c-c59651d33983']/rim:Name/rim:LocalizedString/@value | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element               | xPath of METADATA element                                                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                             |                           |                                                       |                                                                                                                                |                                                |
+| /v3:ClinicalDocument/v3:code/@displayName | /rim:Classification[@classificationScheme='urn:uuid:f0306f51-975f-434e-a61c-c59651d33983']/rim:Name/rim:LocalizedString/@value |                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                             |                           |                                                       |                                                                                                                                |                                                |
+| XDSDEMD-39; M                             | Mapping                                                                                                                        | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:id</td> <td>/rim:ExternalIdentifier[@identificationScheme='urn:uuid:2e82c1f6-a085-4c72-9da3-8640a32e42ab']/@value</td> </tr> </tbody> </table>                                         | xPath of PHM report element | xPath of METADATA element | /v3:ClinicalDocument/v3:id                            | /rim:ExternalIdentifier[@identificationScheme='urn:uuid:2e82c1f6-a085-4c72-9da3-8640a32e42ab']/@value                          | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element               | xPath of METADATA element                                                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                             |                           |                                                       |                                                                                                                                |                                                |
+| /v3:ClinicalDocument/v3:id                | /rim:ExternalIdentifier[@identificationScheme='urn:uuid:2e82c1f6-a085-4c72-9da3-8640a32e42ab']/@value                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                             |                           |                                                       |                                                                                                                                |                                                |
+| XDSDEMD-40; O                             | Mapping                                                                                                                        | <p>There are no PHM report elements, if the element appears the structure of the metadata elements is checked:</p> <table border="1"> <thead> <tr> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/rim:Slot[@name='URI']</td> </tr> </tbody> </table>                                                                                                                                                                         | xPath of METADATA element   | /rim:Slot[@name='URI']    | OPTIONAL: INFO message if constraint is not satisfied |                                                                                                                                |                                                |
+| xPath of METADATA element                 |                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                             |                           |                                                       |                                                                                                                                |                                                |
+| /rim:Slot[@name='URI']                    |                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                             |                           |                                                       |                                                                                                                                |                                                |
+
+**Table B-1-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/XMSV/BV-000**
+
+| TI                                                                                         | Validation type                                                                        | Constraint                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Qualifier                   |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|---------------------------|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------------------------------------------|---------------------------------------------------------------------------------|-----------------------------------------------------------------|--------------------------------------------------------------------------------------|------------------------------------------------|
+| XDSSSDMD-1; O                                                                              | Mapping                                                                                | <p>There are no PHM report elements, if the element appears the structure of the metadata elements is checked:</p> <table border="1"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>/@status</td> </tr> </table>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | xPath of METADATA element   | /@status                  | OPTIONAL: INFO message if constraint is not satisfied                                      |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| xPath of METADATA element                                                                  |                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                             |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| /@status                                                                                   |                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                             |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| XDSSSDMD-2; M                                                                              | Mapping                                                                                | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th><th>xPath of METADATA element</th></tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:representedOrganization/v3:name/text()</td><td>/rim:Classification/rim:Slot[@name='authorInstitution']/rim:ValueList/rim:Value/text()</td></tr> <tr> <td>/v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:assignedPerson/v3:name</td><td>/rim:Classification/rim:Slot[@name='authorPerson']/rim:ValueList/rim:Value/text()</td></tr> <tr> <td>/v3:ClinicalDocument/v3:author/v3:participationFunction/text()</td><td>/rim:Classification/rim:Slot[@name='authorRole']/rim:ValueList/rim:Value/text()</td></tr> <tr> <td>/v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:code/text()</td><td>/rim:Classification/rim:Slot[@name='authorSpecialty']/rim:ValueList/rim:Value/text()</td></tr> </tbody> </table> | xPath of PHM report element | xPath of METADATA element | /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:representedOrganization/v3:name/text() | /rim:Classification/rim:Slot[@name='authorInstitution']/rim:ValueList/rim:Value/text() | /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:assignedPerson/v3:name | /rim:Classification/rim:Slot[@name='authorPerson']/rim:ValueList/rim:Value/text() | /v3:ClinicalDocument/v3:author/v3:participationFunction/text() | /rim:Classification/rim:Slot[@name='authorRole']/rim:ValueList/rim:Value/text() | /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:code/text() | /rim:Classification/rim:Slot[@name='authorSpecialty']/rim:ValueList/rim:Value/text() | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                                | xPath of METADATA element                                                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                             |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:representedOrganization/v3:name/text() | /rim:Classification/rim:Slot[@name='authorInstitution']/rim:ValueList/rim:Value/text() |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                             |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:assignedPerson/v3:name                 | /rim:Classification/rim:Slot[@name='authorPerson']/rim:ValueList/rim:Value/text()      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                             |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| /v3:ClinicalDocument/v3:author/v3:participationFunction/text()                             | /rim:Classification/rim:Slot[@name='authorRole']/rim:ValueList/rim:Value/text()        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                             |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:code/text()                            | /rim:Classification/rim:Slot[@name='authorSpecialty']/rim:ValueList/rim:Value/text()   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                             |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| XDSSSDMD-3; M                                                                              | Mapping                                                                                | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th><th>xPath of METADATA element</th></tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:representedOrganization/v3:name/text()</td><td>/rim:Classification/rim:Slot[@name='authorInstitution']/rim:ValueList/rim:Value/text()</td></tr> </tbody> </table>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | xPath of PHM report element | xPath of METADATA element | /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:representedOrganization/v3:name/text() | /rim:Classification/rim:Slot[@name='authorInstitution']/rim:ValueList/rim:Value/text() | MANDATORY: FAIL if constraint is not satisfied                             |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| xPath of PHM report element                                                                | xPath of METADATA element                                                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                             |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:representedOrganization/v3:name/text() | /rim:Classification/rim:Slot[@name='authorInstitution']/rim:ValueList/rim:Value/text() |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                             |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| XDSSSDMD-4; M                                                                              | Mapping                                                                                | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th><th>xPath of METADATA element</th></tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:assignedPerson/v3:name</td><td>/rim:Classification/rim:Slot[@name='authorPerson']/rim:ValueList/rim:Value/text()</td></tr> </tbody> </table>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | xPath of PHM report element | xPath of METADATA element | /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:assignedPerson/v3:name                 | /rim:Classification/rim:Slot[@name='authorPerson']/rim:ValueList/rim:Value/text()      | MANDATORY: FAIL if constraint is not satisfied                             |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| xPath of PHM report element                                                                | xPath of METADATA element                                                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                             |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+| /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:assignedPerson/v3:name                 | /rim:Classification/rim:Slot[@name='authorPerson']/rim:ValueList/rim:Value/text()      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                             |                           |                                                                                            |                                                                                        |                                                                            |                                                                                   |                                                                |                                                                                 |                                                                 |                                                                                      |                                                |
+
+**Table B-1-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/XMSV/BV-000**
+
+| TI                                                                                       | Validation type                                                                 | Constraint                                                                                                                                                                                                                                                                                                                                                                                                                                       | Qualifier                   |                                             |                                                                                          |                                                                                 |                                                |
+|------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|---------------------------------------------|------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|------------------------------------------------|
+| XDSSSMD-5; M                                                                             | Mapping                                                                         | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:participationFunction/v3:code/text</td> <td>/rim:Classification/rim:Slot[@name='authorRole']/rim:ValueList/rim:Value/text()</td> </tr> </tbody> </table>  | xPath of PHM report element | xPath of METADATA element                   | /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:participationFunction/v3:code/text   | /rim:Classification/rim:Slot[@name='authorRole']/rim:ValueList/rim:Value/text() | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                              | xPath of METADATA element                                                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                             |                                             |                                                                                          |                                                                                 |                                                |
+| /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:participationFunction/v3:code/text   | /rim:Classification/rim:Slot[@name='authorRole']/rim:ValueList/rim:Value/text() |                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                             |                                             |                                                                                          |                                                                                 |                                                |
+| XDSSSMD-6; M                                                                             | Mapping                                                                         | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:participationFunction/v3:code/text()</td> <td>rim:Classification/rim:Slot[@name='authorRole']/rim:ValueList/rim:Value/text()</td> </tr> </tbody> </table> | xPath of PHM report element | xPath of METADATA element                   | /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:participationFunction/v3:code/text() | rim:Classification/rim:Slot[@name='authorRole']/rim:ValueList/rim:Value/text()  | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                              | xPath of METADATA element                                                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                             |                                             |                                                                                          |                                                                                 |                                                |
+| /v3:ClinicalDocument/v3:author/v3:assignedAuthor/v3:participationFunction/v3:code/text() | rim:Classification/rim:Slot[@name='authorRole']/rim:ValueList/rim:Value/text()  |                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                             |                                             |                                                                                          |                                                                                 |                                                |
+| XDSSSMD-7; O                                                                             | Mapping                                                                         | <p>There are no PHM report elements, if the element appears the structure of the metadata elements is checked:</p> <table border="1"> <thead> <tr> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/rim:Description/rim:LocalizedString/@value</td> </tr> </tbody> </table>                                                                                                                                                   | xPath of METADATA element   | /rim:Description/rim:LocalizedString/@value | OPTIONAL: INFO message if constraint is not satisfied                                    |                                                                                 |                                                |
+| xPath of METADATA element                                                                |                                                                                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                             |                                             |                                                                                          |                                                                                 |                                                |
+| /rim:Description/rim:LocalizedString/@value                                              |                                                                                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                             |                                             |                                                                                          |                                                                                 |                                                |
+| XDSSSMD-9; O                                                                             | Mapping                                                                         | <p>The following PHM report elements (if present) shall be equal to metadata elements:</p> <table border="1"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> </tbody> </table>                                                                                                                                                                                                      | xPath of PHM report element | xPath of METADATA element                   | OPTIONAL: INFO message if constraint is not satisfied                                    |                                                                                 |                                                |
+| xPath of PHM report element                                                              | xPath of METADATA element                                                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                             |                                             |                                                                                          |                                                                                 |                                                |
+| XDSSSMD-10; M                                                                            | Mapping                                                                         | <p>There are no PHM report elements, if the element appears the structure of the metadata elements is checked:</p> <table border="1"> <thead> <tr> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/@id</td> </tr> </tbody> </table>                                                                                                                                                                                          | xPath of METADATA element   | /@id                                        | MANDATORY: FAIL if constraint is not satisfied                                           |                                                                                 |                                                |
+| xPath of METADATA element                                                                |                                                                                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                             |                                             |                                                                                          |                                                                                 |                                                |
+| /@id                                                                                     |                                                                                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                             |                                             |                                                                                          |                                                                                 |                                                |
+
+**Table B-1-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/XMSV/BV-000**
+
+| TI                                                        | Validation type                                                                                      | Constraint                                                                                                                                                                                                                                                                                                                                                                                                                                            | Qualifier                   |                           |                                                           |                                                                                                      |                                                |
+|-----------------------------------------------------------|------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|---------------------------|-----------------------------------------------------------|------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| XDSSSMD-11; M                                             | Mapping                                                                                              | The following PHM report elements (if present) shall be equal to metadata elements: <table border="1" style="width: 100%;"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:recordTarget/v3:patientRole/v3:id</td> <td>/rim:ExternalIdentifier[@identificationScheme='urn:uuid:6b5ae1a-874d-4603-a4bc-96a0a7b38446']/@value</td> </tr> </tbody> </table> | xPath of PHM report element | xPath of METADATA element | /v3:ClinicalDocument/v3:recordTarget/v3:patientRole/v3:id | /rim:ExternalIdentifier[@identificationScheme='urn:uuid:6b5ae1a-874d-4603-a4bc-96a0a7b38446']/@value | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                               | xPath of METADATA element                                                                            |                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                             |                           |                                                           |                                                                                                      |                                                |
+| /v3:ClinicalDocument/v3:recordTarget/v3:patientRole/v3:id | /rim:ExternalIdentifier[@identificationScheme='urn:uuid:6b5ae1a-874d-4603-a4bc-96a0a7b38446']/@value |                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                             |                           |                                                           |                                                                                                      |                                                |
+| XDSSSMD-14; M                                             | Mapping                                                                                              | The following PHM report elements (if present) shall be equal to metadata elements: <table border="1" style="width: 100%;"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:title/text()</td> <td>/rim:Name/rim:LocalizedString/@value</td> </tr> </tbody> </table>                                                                                      | xPath of PHM report element | xPath of METADATA element | /v3:ClinicalDocument/v3:title/text()                      | /rim:Name/rim:LocalizedString/@value                                                                 | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                               | xPath of METADATA element                                                                            |                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                             |                           |                                                           |                                                                                                      |                                                |
+| /v3:ClinicalDocument/v3:title/text()                      | /rim:Name/rim:LocalizedString/@value                                                                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                             |                           |                                                           |                                                                                                      |                                                |
+| XDSSSMD-15; M                                             | Mapping                                                                                              | The following PHM report elements (if present) shall be equal to metadata elements: <table border="1" style="width: 100%;"> <thead> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/v3:ClinicalDocument/v3:id</td> <td>/rim:ExternalIdentifier[@identificationScheme='urn:uuid:96fd7c-d067-4183-912e-bf5ee74998a8']/@value</td> </tr> </tbody> </table>                                 | xPath of PHM report element | xPath of METADATA element | /v3:ClinicalDocument/v3:id                                | /rim:ExternalIdentifier[@identificationScheme='urn:uuid:96fd7c-d067-4183-912e-bf5ee74998a8']/@value  | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                               | xPath of METADATA element                                                                            |                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                             |                           |                                                           |                                                                                                      |                                                |
+| /v3:ClinicalDocument/v3:id                                | /rim:ExternalIdentifier[@identificationScheme='urn:uuid:96fd7c-d067-4183-912e-bf5ee74998a8']/@value  |                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                             |                           |                                                           |                                                                                                      |                                                |
+
+### **B.2 Testable item syntactic validation by XSD (XML schema language) file**
+
+#### **B.2.1 For TP/HIS/SEN/CCDA/BV-000**
+
+**Table B-2-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI              | Validation type                  | Constraint                                                                                                                                                                                                                                                                                                                                                             | Qualifier                                      |
+|-----------------|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| CONF-PHMR-1; M  | Syntactic validation by XSD file | <pre>&lt;xs:schema targetNamespace="urn:h7-org:v3" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="urn:h7-org:v3"   xmlns:mif="urn:h7-org:v3/mif" elementFormDefault="qualified"&gt;   &lt;xs:include schemaLocation="CONTINUA_POCD_MT000040.xsd"/&gt;   &lt;xs:element name="ClinicalDocument" type="POCD_MT000040.ClinicalDocument"/&gt; &lt;/xs:schema&gt;</pre> | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-15; M | Syntactic validation by XSD file | <pre>&lt;xs:complexType name="POCD_MT000040.ClinicalDocument"&gt;   &lt;xs:sequence&gt;</pre>                                                                                                                                                                                                                                                                          | MANDATORY: FAIL if constraint is not satisfied |
+
+**Table B-2-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI              | Validation type                  | Constraint                                                                                                                                                                                                                                                                               | Qualifier                                      |
+|-----------------|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+|                 |                                  | <xs:element name="title" type="ST" />                                                                                                                                                                                                                                                    |                                                |
+| CONF-PHMR-17; M | Syntactic validation by XSD file | <xs:complexType name="POCD_MT000040.ClinicalDocument"><br><xs:sequence><br><xs:element name="languageCodedTitle" type="CS" />                                                                                                                                                            | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-23; M | Syntactic validation by XSD file | ClinicalDocument/copyTime is not present in the XSD schema, if present there will be a FAIL                                                                                                                                                                                              | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-24; M | Syntactic validation by XSD file | <xs:complexType name="POCD_MT000040.RecordTarget"><br><xs:sequence><br><xs:element name="patientRole" type="POCD_MT000040.PatientRole" />                                                                                                                                                | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-29; M | Syntactic validation by XSD file | <xs:complexType name="POCD_MT000040.Author"><br><xs:sequence><br><xs:element name="time" type="TS" />                                                                                                                                                                                    | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-30; M | Syntactic validation by XSD file | <xs:complexType name="POCD_MT000040.AssignedAuthor"><br><xs:sequence><br><xs:element name="id" type="II" maxOccurs="unbounded"/>                                                                                                                                                         | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-31; M | Syntactic validation by XSD file | <xs:complexType name="POCD_MT000040.AssignedAuthor"><br><xs:choice><br><xs:element name="assignedPerson" type="POCD_MT000040.Person" maxOccurs="unbounded"/><br><xs:element name="assignedAuthoringDevice" type="POCD_MT000040.AuthoringDevice" maxOccurs="unbounded" /><br></xs:choice> | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-42; M | Syntactic validation by XSD file | <xs:complexType name="POCD_MT000040.ServiceEvent"><br><xs:sequence><br><xs:element name="effectiveTime" type="IVL_TS" />                                                                                                                                                                 | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-43; M | Syntactic validation by XSD file | <xs:complexType name="POCD_MT000040.StructuredBody">                                                                                                                                                                                                                                     | MANDATORY: FAIL if constraint is not satisfied |
+
+### B.3 Testable item syntactic validation against XML reference document file
+
+#### B.3.1 For TP/HIS/SEN/CCDA/BV-000
+
+**Table B-3-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI         | Validation type                  | Constraint                                                                                                            | Qualifier                                      |
+|------------|----------------------------------|-----------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| G1_Snom_1  | Syntactic validation by XML file | <Code MDC="MDC_CONC_GLU_CAPILLARY_PLASMA" conceptID="434911002" descriptionID="2774413018" fullyID="2774414012"/>     | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_2  | Syntactic validation by XML file | <Code MDC="MDC_CONC_GLU_VENOUS_PLASMA" conceptID="434911002" descriptionID="2774413018" fullyID="2774414012"/>        | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_3  | Syntactic validation by XML file | <Code MDC="MDC_CONC_GLU_ARTERIAL_PLASMA" conceptID="434911002" descriptionID="2774413018" fullyID="2774414012"/>      | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_4  | Syntactic validation by XML file | <Code MDC="MDC_CONC_GLU_CAPILLARY_WHOLEBLOOD" conceptID="434912009" descriptionID="2774415013" fullyID="2774416014"/> | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_5  | Syntactic validation by XML file | <Code MDC="MDC_CONC_GLU_VENOUS_WHOLEBLOOD" conceptID="434912009" descriptionID="2774415013" fullyID="2774416014"/>    | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_6  | Syntactic validation by XML file | <Code MDC="MDC_CONC_GLU_ARTERIAL_WHOLEBLOOD" conceptID="434912009" descriptionID="2774415013" fullyID="2774416014"/>  | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_7  | Syntactic validation by XML file | <Code MDC="MDC_CONC_GLU_CONTROL" conceptID="434913004" descriptionID="2774417017" fullyID="2774418010"/>              | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_8  | Syntactic validation by XML file | <Code MDC="MDC_CONC_GLU_ISF" conceptID="434910001" descriptionID="2774412011" fullyID="2774411016"/>                  | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_9  | Syntactic validation by XML file | <Code MDC="MDC_CONC_HBA1C" conceptID="365845005" descriptionID="489331011" fullyID="772274010"/>                      | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_10 | Syntactic validation by XML file | <Code MDC="MDC_MASS_BODY_ACTUAL" conceptID="27113001" descriptionID="45352010" fullyID="757644016"/>                  | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_11 | Syntactic validation by XML file | <Code MDC="MDC_LEN_BODY_ACTUAL" conceptID="50373000" descriptionID="495662010" fullyID="788154012"/>                  | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_12 | Syntactic validation by XML file | <Code MDC="MDC_RATIO_MASS_BODY_LEN_SQ" conceptID="60621009" descriptionID="100716012" fullyID="799594012"/>           | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_13 | Syntactic validation by XML file | <Code MDC="MDC_PRESS_BLD_NONINV_SYS" conceptID="271649006" descriptionID="106507015" fullyID="664067013"/>            | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_14 | Syntactic validation by XML file | <Code MDC="MDC_PRESS_BLD_NONINV_DIA" conceptID="271650006" descriptionID="406508013" fullyID="664068015"/>            | MANDATORY: FAIL if constraint is not satisfied |
+
+**Table B-3-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI         | Validation type                  | Constraint                                                                                                                                                                                                        | Qualifier                                      |
+|------------|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| G1_Snom_15 | Syntactic validation by XML file | <Code MDC="MDC_PRESS_BLD_NONINV_MEAN" conceptID="6797001" descriptionID="500884018" fullyID="807753012"/>                                                                                                         | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_16 | Syntactic validation by XML file | <Code MDC="MDC_PULS_RATE_NON_INV" conceptID="78564009" descriptionID="130365016" fullyID="819518016"/>                                                                                                            | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_17 | Syntactic validation by XML file | <Code MDC="MDC_TEMP_BODY" conceptID="386725007" descriptionID="1480858013" fullyID="1460904011"/>                                                                                                                 | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_18 | Syntactic validation by XML file | <Code MDC="MDC_TEMP_FINGER" conceptID="433588001" descriptionID="2771281010" fullyID="2760794019"/>                                                                                                               | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_19 | Syntactic validation by XML file | <Code MDC="MDC_TEMP_EAR" conceptID="415974002" descriptionID="2534421019" fullyID="2530951014"/>                                                                                                                  | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_20 | Syntactic validation by XML file | <Code MDC="MDC_TEMP_TOE" conceptID="433776001" descriptionID="2768039016" fullyID="2745011013"/>                                                                                                                  | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_21 | Syntactic validation by XML file | <Code MDC="MDC_TEMP_GIT" conceptID="431598003" descriptionID="2769062014" fullyID="2747764015"/>                                                                                                                  | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_22 | Syntactic validation by XML file | <Code MDC="MDC_TEMP_AXILLA" conceptID="415882003" descriptionID="2534419012" fullyID="2530949010"/>                                                                                                               | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_23 | Syntactic validation by XML file | <Code MDC="MDC_TEMP_ORAL" conceptID="415945006" descriptionID="2534418016" fullyID="253094019"/>                                                                                                                  | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_24 | Syntactic validation by XML file | <Code MDC="MDC_TEMP_RECT" conceptID="307047009" descriptionID="450211011" fullyID="703520017"/>                                                                                                                   | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_25 | Syntactic validation by XML file | <Code MDC="MDC_TEMP_TYMP" conceptID="415974002" descriptionID="2534421019" fullyID="2530951014"/>                                                                                                                 | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_26 | Syntactic validation by XML file | <Code MDC="MDC_PULS_OXIM_SAT_O2" conceptID="431314004" descriptionID="2772010012" fullyID="2735642016"/>                                                                                                          | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_27 | Syntactic validation by XML file | <Code MDC="MDC_PULS_OXIM_PULS_RATE" conceptID="78564009" descriptionID="130365016" fullyID="819518016"/>                                                                                                          | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_28 | Syntactic validation by XML file | <Code MDC="MDC_PULS_OXIM_PERF_REL" conceptID="431591009" descriptionID="2769937011" fullyID="2736894010"/><br><Code MDC="MDC_SAT_O2_QUAL" conceptID="431591009" descriptionID="2769937011" fullyID="2736894010"/> | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_29 | Syntactic validation by XML file | <Code MDC="MDC_PULS_OXIM_PLETH" conceptID="250864000" descriptionID="373962018" fullyID="641309010"/>                                                                                                             | MANDATORY: FAIL if constraint is not satisfied |
+
+**Table B-3-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI         | Validation type                  | Constraint                                                                                                                                           | Qualifier                                      |
+|------------|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| G1_Snom_30 | Syntactic validation by XML file | <Code MDC="MDC_FLOW_AWAY_EXP_FORCED_PEAK" conceptID="251940009" descriptionID="375280019" fullyID="642506016"/>                                      | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_31 | Syntactic validation by XML file | <Code MDC="MDC_FLOW_AWAY_EXP_FORCED_PEAK_PB" conceptID="251936000" descriptionID="375276012" fullyID="642501014"/>                                   | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_32 | Syntactic validation by XML file | <Code MDC="MDC_VOL_AWAY_EXP_FORCED_1S" conceptID="59328004" descriptionID="498401010" fullyID="798158012"/>                                          | MANDATORY: FAIL if constraint is not satisfied |
+| G1_Snom_33 | Syntactic validation by XML file | <Code MDC="MDC_VOL_AWAY_EXP_FORCED_EXP_6S" conceptID="165041004" descriptionID="256687019" fullyID="546438012"/>                                     | MANDATORY: FAIL if constraint is not satisfied |
+| G2_Snom_1  | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line. | MANDATORY: FAIL if constraint is not satisfied |
+| G2_Snom_2  | Syntactic validation by XML file | <Code MDC="MDC_CONT_GLU_SAMPLELOCATION_FINGER" conceptID="125685002" descriptionID="473565013" fullyID="729542015"/>                                 | MANDATORY: FAIL if constraint is not satisfied |
+| G2_Snom_3  | Syntactic validation by XML file | <Code MDC="MDC_CONT_GLU_SAMPLELOCATION_EARLOBE" conceptID="113327001" descriptionID="383219015" fullyID="648683014"/>                                | MANDATORY: FAIL if constraint is not satisfied |
+| G2_Snom_4  | Syntactic validation by XML file | <Code MDC="MDC_CONT_GLU_MEAL_PREPRANDIAL" conceptID="307165006" descriptionID="450357011" fullyID="703654021"/>                                      | MANDATORY: FAIL if constraint is not satisfied |
+| G2_Snom_5  | Syntactic validation by XML file | <Code MDC="MDC_CONT_GLU_MEAL_POSTPRANDIAL" conceptID="225758001" descriptionID="339227016" fullyID="613042015"/>                                     | MANDATORY: FAIL if constraint is not satisfied |
+| G2_Snom_6  | Syntactic validation by XML file | <Code MDC="MDC_CONT_GLU_MEAL_FASTING" conceptID="16985007" descriptionID="478017015" fullyID="744117012"/>                                           | MANDATORY: FAIL if constraint is not satisfied |
+| G2_Snom_7  | Syntactic validation by XML file | <Code MDC="MDC_CONT_GLU_MEAL_CASUAL" conceptID="255226008" descriptionID="380387010" fullyID="646234012"/>                                           | MANDATORY: FAIL if constraint is not satisfied |
+| G2_Snom_8  | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line. | MANDATORY: FAIL if constraint is not satisfied |
+| G2_Snom_9  | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line. | MANDATORY: FAIL if constraint is not satisfied |
+| G2_Snom_10 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line. | MANDATORY: FAIL if constraint is not satisfied |
+| G2_Snom_11 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line. | MANDATORY: FAIL if constraint is not satisfied |
+| G2_Snom_12 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line. | MANDATORY: FAIL if constraint is not satisfied |
+
+**Table B-3-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI         | Validation type                  | Constraint                                                                                                                                            | Qualifier                                      |
+|------------|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| G2_Snom_13 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line.  | MANDATORY: FAIL if constraint is not satisfied |
+| G2_Snom_14 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line.  | MANDATORY: FAIL if constraint is not satisfied |
+| G2_Snom_15 | Syntactic validation by XML file | <Code MDC="MDC_MODALITY_FAST" conceptID="433204000" descriptionID="2768695014" fullyID="2743645015"/>                                                 | MANDATORY: FAIL if constraint is not satisfied |
+| G2_Snom_16 | Syntactic validation by XML file | <Code MDC="MDC_MODALITY_SLOW" conceptID="433204000" descriptionID="2768695014" fullyID="2743645015"/>                                                 | MANDATORY: FAIL if constraint is not satisfied |
+| G2_Snom_17 | Syntactic validation by XML file | <Code MDC="MDC_MODALITY_SPOT" conceptID="431314004" descriptionID="2772010012" fullyID="2735642016"/>                                                 | MANDATORY: FAIL if constraint is not satisfied |
+| G2_Snom_18 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line.  | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_19 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line.  | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_20 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line.  | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_21 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line.  | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_22 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line.. | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_23 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line.  | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_24 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line.  | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_25 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line.  | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_26 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line.  | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_27 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line.  | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_28 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line.  | MANDATORY: FAIL if constraint is not satisfied |
+
+**Table B-3-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI         | Validation type                  | Constraint                                                                                                                                           | Qualifier                                      |
+|------------|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| G3_Snom_29 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line. | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_30 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line. | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_31 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line. | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_32 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line. | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_33 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line. | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_34 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line. | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_35 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line. | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_36 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line. | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_37 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line. | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_38 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line. | MANDATORY: FAIL if constraint is not satisfied |
+| G3_Snom_39 | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line. | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_1  | Syntactic validation by XML file | <code unit="% ref="MDC_DIM_PERCENT"/>                                                                                                                | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_2  | Syntactic validation by XML file | <code unit="{beat}/min" ref="MDC_DIM_BEAT_PER_MIN"/>                                                                                                 | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_3  | Syntactic validation by XML file | <code unit="mm[Hg]" ref="MDC_DIM_MMHG"/>                                                                                                             | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_4  | Syntactic validation by XML file | <code unit="kPa" ref="MDC_KILO_PASCAL"/>                                                                                                             | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_5  | Syntactic validation by XML file | There is no conversion in the table for this TI. If a conversion shows up, the test tool will produce a FAIL with a text indicating the faulty line. | MANDATORY: FAIL if constraint is not satisfied |
+
+**Table B-3-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI         | Validation type                  | Constraint                                           | Qualifier                                      |
+|------------|----------------------------------|------------------------------------------------------|------------------------------------------------|
+| G4_Snom_6  | Syntactic validation by XML file | <code unit="Cel" ref="MDC_DIM_DEGC"/>                | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_7  | Syntactic validation by XML file | <code unit="[degF]" ref="MDC_DIM_FAHR"/>             | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_8  | Syntactic validation by XML file | <code unit="kg" ref="MDC_DIM_KILO_G"/>               | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_9  | Syntactic validation by XML file | <code unit="[lb_av]" ref="MDC_DIM_LB"/>              | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_10 | Syntactic validation by XML file | <code unit="cm" ref="MDC_DIM_CENTI_M"/>              | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_11 | Syntactic validation by XML file | <code unit="[in_i]" ref="MDC_DIM_INCH"/>             | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_12 | Syntactic validation by XML file | <code unit="kg/m2" ref="MDC_DIM_KG_PER_M_SQ"/>       | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_13 | Syntactic validation by XML file | <code unit="mmol/L" ref="MDC_DIM_MILLI_MOLE_PER_L"/> | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_14 | Syntactic validation by XML file | <code unit="[Cal]" ref="MDC_DIM_KCAL"/>              | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_15 | Syntactic validation by XML file | <code unit="mg/dL" ref="MDC_DIM_MILLI_G_PER_DL"/>    | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_16 | Syntactic validation by XML file | <code unit="1" ref="MDC_DIM_DIMLESS"/>               | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_17 | Syntactic validation by XML file | <code unit="mL" ref="MDC_DIM_MILLI_L"/>              | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_18 | Syntactic validation by XML file | <code unit="mg" ref="MDC_DIM_MILLI_G"/>              | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_19 | Syntactic validation by XML file | <code unit="[iU]" ref="MDC_DIM_INTL_UNIT"/>          | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_20 | Syntactic validation by XML file | <code unit="[iU]/h" ref="MDC_DIM_INTL_UNIT_PER_HR"/> | MANDATORY: FAIL if constraint is not satisfied |
+| G4_Snom_21 | Syntactic validation by XML file | <code unit="L/min" ref="MDC_DIM_INTL_UNIT_PER_HR"/>  | MANDATORY: FAIL if constraint is not satisfied |
+
+**Table B-3-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI         | Validation type                  | Constraint                       | Qualifier                                      |
+|------------|----------------------------------|----------------------------------|------------------------------------------------|
+| G4_Snom_22 | Syntactic validation by XML file | <code unit="L" ref="MDC_DIM_L"/> | MANDATORY: FAIL if constraint is not satisfied |
+
+### B.4 Testable item syntactic and/or semantic validation by Schematron 1.5
+
+#### B.4.1 For TP/HIS/SEN/CCDA/BV-000
+
+**Table B-4-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI           | Validation type       | Constraint                                                                                                                                | Qualifier                                             |
+|--------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|
+| CONF-PHMR-2  | Schematron validation | Context: ClinicalDocument<br>Test: templateId/@root='2.16.840.1.113883.10.20.9'                                                           | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-2  | Schematron validation | Context: ClinicalDocument<br>Test: not(templateId/@root='2.16.840.1.113883.10.20.3')                                                      | OPTIONAL: INFO message if constraint is not satisfied |
+| CONF-PHMR-2  | Schematron validation | Context: ClinicalDocument<br>Test: templateId/@root='2.16.840.1.113883.10.20.3'                                                           | OPTIONAL: INFO message if constraint is not satisfied |
+| CONF-PHMR-3  | Schematron validation | Context: ClinicalDocument<br>Test: not ( code/@code='53576-5')                                                                            | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-13 | Schematron validation | Context: / ClinicalDocument/ id[contains(@root, '-')]<br>Test: not (string-length(@root) = 36)                                            | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-13 | Schematron validation | Context: / ClinicalDocument/ id[contains(@root, '-')]<br>Test: not (translate(substring(@root, 1, 8),'ABCDEFabcdef0123456789',"") = "")   | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-13 | Schematron validation | Context: / ClinicalDocument/ id[contains(@root, '-')]<br>Test: not (translate(substring(@root, 10, 4),'ABCDEFabcdef0123456789',"") = "")  | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-13 | Schematron validation | Context: / ClinicalDocument/ id[contains(@root, '-')]<br>Test: not (translate(substring(@root, 15, 4),'ABCDEFabcdef0123456789',"") = "")  | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-13 | Schematron validation | Context: / ClinicalDocument/ id[contains(@root, '-')]<br>Test: not (translate(substring(@root, 20, 4),'ABCDEFabcdef0123456789',"") = "")  | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-13 | Schematron validation | Context: / ClinicalDocument/ id[contains(@root, '-')]<br>Test: not (translate(substring(@root, 25, 12),'ABCDEFabcdef0123456789',"") = "") | MANDATORY: FAIL if constraint is not satisfied        |
+
+**Table B-4-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI           | Validation type       | Constraint                                                                                                                                      | Qualifier                                                         |
+|--------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|
+| CONF-PHMR-14 | Schematron validation | Context: / ClinicalDocument/ id[contains(@root, '.')] Test: not (translate(substring(@root, 1, 1) , '012', '') = "")                            | MANDATORY: FAIL if constraint is not satisfied                    |
+| CONF-PHMR-14 | Schematron validation | Context: / ClinicalDocument/ id[contains(@root, '.')] Test: not (translate(@root, '0123456789.', '') = "")                                      | MANDATORY: FAIL if constraint is not satisfied                    |
+| CONF-PHMR-12 | Schematron validation | Context: id[not(contains(@root, ".") or contains(@root, "-") or @nullFlavor)] Test: not (false())                                               | MANDATORY: FAIL if constraint is not satisfied                    |
+| CONF-PHMR-13 | Schematron validation | Context: / ClinicalDocument/ id[contains(@root, '-')] Test: not (substring(@root, 9, 1) = '-')                                                  | RECOMMENDED: WARNING message if constraint is not satisfied       |
+| CONF-PHMR-13 | Schematron validation | Context: / ClinicalDocument/ id[contains(@root, '-')] Test: not (substring(@root, 14, 1) = '-')                                                 | RECOMMENDED: WARNING message if constraint is not satisfied       |
+| CONF-PHMR-13 | Schematron validation | Context: / ClinicalDocument/ id[contains(@root, '-')] Test: not (substring(@root, 19, 1) = '-')                                                 | RECOMMENDED: WARNING message if constraint is not satisfied       |
+| CONF-PHMR-13 | Schematron validation | Context: / ClinicalDocument/ id[contains(@root, '-')] Test: not (substring(@root, 24, 1) = '-')                                                 | RECOMMENDED: WARNING message if constraint is not satisfied       |
+| CONF-PHMR-14 | Schematron validation | Context: / ClinicalDocument/ id[contains(@root, '.')] Test: not (not(contains(@root, '.'))))                                                    | RECOMMENDED: WARNING message if constraint is not satisfied       |
+| CONF-PHMR-21 | Schematron validation | Context: ClinicalDocument Test: not ((not ( setId) and not ( versionNumber)) or (( setId) and ( versionNumber))))                               | MANDATORY: FAIL if constraint is not satisfied                    |
+| CONF-PHMR-22 | Schematron validation | Context: ClinicalDocument/ setId Test: not (@root != ../ id/@root or @extension != ../ id/@extension)                                           | MANDATORY: FAIL if constraint is not satisfied                    |
+| CONF-PHMR-37 | Schematron validation | Context: ClinicalDocument/ informationRecipient Test: not ( intendedRecipient/ informationRecipient or intendedRecipient/ receivedOrganization) | MANDATORY: FAIL if constraint is not satisfied - PHMR-37-optional |
+| CONF-PHMR-37 | Schematron validation | context: ClinicalDocument Test: informationRecipient                                                                                            | OPTIONAL: INFO message if constraint is not satisfied             |
+| CONF-PHMR-37 | Schematron validation | Context: ClinicalDocument Test: not ( informationRecipient)                                                                                     | OPTIONAL: INFO message if constraint is not satisfied             |
+| CONF-PHMR-38 | Schematron validation | Context: legalAuthenticator/ assignedEntity Test: not ( assignedPerson or representedOrganization)                                              | MANDATORY: FAIL if constraint is not satisfied                    |
+
+**Table B-4-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI           | Validation type       | Constraint                                                                                                                                                                                                                                                                                                                                                | Qualifier                                                   |
+|--------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|
+| CONF-PHMR-39 | Schematron validation | Context: authenticator<br>Test: not ( assignedEntity/ assignedPerson)                                                                                                                                                                                                                                                                                     | MANDATORY: FAIL if constraint is not satisfied              |
+| CONF-PHMR-39 | Schematron validation | context: ClinicalDocument<br>Test: ( authenticator)                                                                                                                                                                                                                                                                                                       | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF-PHMR-39 | Schematron validation | Context: ClinicalDocument<br>Test: not (( authenticator))                                                                                                                                                                                                                                                                                                 | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF-PHMR-41 | Schematron validation | Context: serviceEvent<br>Test: not ((@classCode='MPROT') or not(@classCode))                                                                                                                                                                                                                                                                              | MANDATORY: FAIL if constraint is not satisfied              |
+| CONF-PHMR-8  | Schematron validation | Context: ClinicalDocument/ effectiveTime or ClinicalDocument/ author/ time or ClinicalDocument/ dataEntrer/ time or ClinicalDocument/ legalAuthenticator/ time or ClinicalDocument/ authenticator/ time or ClinicalDocument/ encompassingEncounter/ effectiveTime<br>Test: not ((string-length(@value)>=8))                                               | MANDATORY: FAIL if constraint is not satisfied              |
+| CONF-PHMR-8  | Schematron validation | Context: ClinicalDocument/ effectiveTime or ClinicalDocument/ author/ time or ClinicalDocument/ dataEntrer/ time or ClinicalDocument/ legalAuthenticator/ time or ClinicalDocument/ authenticator/ time or ClinicalDocument/ encompassingEncounter/ effectiveTime<br>Test: not (contains(translate(@value,"+-","ZZ"),"Z"))                                | MANDATORY: FAIL if constraint is not satisfied              |
+| CONF-PHMR-8  | Schematron validation | Context: ClinicalDocument/ effectiveTime or author/ time or ClinicalDocument/ dataEntrer/ time or ClinicalDocument/ legalAuthenticator/ time or ClinicalDocument/ authenticator/ time or encompassingEncounter/ effectiveTime<br>Test: not ((string-length(@value)>=14))                                                                                  | RECOMMENDED: WARNING message if constraint is not satisfied |
+| CONF-PHMR-9  | Schematron validation | Context: asOrganizationPartOf/ effectiveTime or asMaintainedEntity/ effectiveTime or relatedEntity/ effectiveTime or serviceEvent/ effectiveTime/ low or serviceEvent/ effectiveTime/ high or ClinicalDocument/ participant/ time or serviceEvent/ performer/ time or encounterParticipant/ time<br>Test: not ((string-length(@value)>=4))                | MANDATORY: FAIL if constraint is not satisfied              |
+| CONF-PHMR-9  | Schematron validation | Context: asOrganizationPartOf/ effectiveTime or asMaintainedEntity/ effectiveTime or relatedEntity/ effectiveTime or serviceEvent/ effectiveTime/ low or serviceEvent/ effectiveTime/ high or ClinicalDocument/ participant/ time or serviceEvent/ performer/ time or encounterParticipant/ time<br>Test: not ((string-length(@value)>=8))                | RECOMMENDED: WARNING message if constraint is not satisfied |
+| CONF-PHMR-9  | Schematron validation | Context: asOrganizationPartOf/ effectiveTime or asMaintainedEntity/ effectiveTime or relatedEntity/ effectiveTime or serviceEvent/ effectiveTime/ low or serviceEvent/ effectiveTime/ high or ClinicalDocument/ participant/ time or serviceEvent/ performer/ time or encounterParticipant/ time<br>Test: not (contains(translate(@value,"+-","ZZ"),"Z")) | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF-PHMR-9  | Schematron validation | context: asOrganizationPartOf/ effectiveTime or asMaintainedEntity/ effectiveTime or relatedEntity/ effectiveTime or serviceEvent/ effectiveTime/ low or serviceEvent/ effectiveTime/ high or ClinicalDocument/ participant/ time or serviceEvent/ performer/ time or encounterParticipant/ time<br>Test: contains(translate(@value,"+-","ZZ"),"Z")       | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF-PHMR-5  | Schematron validation | Context: patientRole or assignedAuthor or associatedEntity<br>Test: not ( addr and telecom )                                                                                                                                                                                                                                                              | RECOMMENDED: WARNING message if constraint is not satisfied |
+
+**Table B-4-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI           | Validation type       | Constraint                                                                                                                                                                                                                                                               | Qualifier                                                         |
+|--------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|
+| CONF-PHMR-6  | Schematron validation | Context: ClinicalDocument/ guardian or ClinicalDocument/ dataEntrer/ assignedEntity or ClinicalDocument/ relatedEntity or ClinicalDocument/ intendedRecipient or ClinicalDocument/ relatedSubject or ClinicalDocument/ participantRole<br>Test: not ( addr and telecom ) | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF-PHMR-28 | Schematron validation | context: recordTarget/ patientRole<br>Test: providerOrganization                                                                                                                                                                                                         | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-PHMR-28 | Schematron validation | Context: recordTarget/ patientRole<br>Test: not ( providerOrganization)                                                                                                                                                                                                  | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-PHMR-32 | Schematron validation | Context: ClinicalDocument<br>Test: not ( author/ assignedAuthor/ assignedPerson)                                                                                                                                                                                         | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF-PHMR-10 | Schematron validation | Context: telecom<br>Test: not ((@nullFlavor) or (@value))                                                                                                                                                                                                                | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-10 | Schematron validation | Context: telecom<br>Test: not ((substring(@value,1,4) = "tel:" and string-length( concat( translate(substring(@value,5,1),"+0123456789()-.", ""),<br>translate(substring(@value,6),"0123456789()-.", "")) ) = 0 ) or (@nullFlavor))                                      | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-10 | Schematron validation | Context: telecom<br>Test: not (not(substring(@value,1,4) = "tel:") or string-length( concat( translate(substring(@value,5,1),"+()-.", ""),<br>translate(substring(@value,6),"()-.", "")) ) > 0)                                                                          | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-18 | Schematron validation | Context: ClinicalDocument/ languageCode<br>Test: not ((string-length(@code)=2) or (string-length(@code)=5 and substring(@code,3,1) = '-'))                                                                                                                               | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-18 | Schematron validation | Context: ClinicalDocument/ languageCode<br>Test: not (substring(@code,1,2) = document("voc.xml")/systems/system[@codeSystemName="ISO639-1"]/code/@value)                                                                                                                 | MANDATORY: FAIL if<br>constraint is not satisfied:                |
+| CONF-PHMR-18 | Schematron validation | Context: ClinicalDocument/ languageCode<br>Test: not (substring(@code,1,2) = document("voc.xml")/systems/system[@codeSystemName="ISO639-1"]/code/@value)                                                                                                                 | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-19 | Schematron validation | Context: ClinicalDocument/ languageCode<br>Test: not (string-length(@code) = 2 or substring(@code,4,2) = document("voc.xml")/systems/system[@codeSystemName="ISO3166-1"]/code/@value)                                                                                    | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-20 | Schematron validation | Context: ClinicalDocument/ languageCode<br>Test: string-length(@code) = 2 or substring(@code,4,2) = document("voc.xml")/systems/system[@codeSystemName="ISO3166-1"]/code/@value                                                                                          | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-25 | Schematron validation | Context: patient/birthTime<br>Test: (string-length(@value)>=4) or (@nullFlavor)                                                                                                                                                                                          | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-25 | Schematron validation | Context: patient/birthTime<br>Test: (string-length(@value)>=8) or (@nullFlavor)                                                                                                                                                                                          | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+
+**Table B-4-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI           | Validation type       | Constraint                                                                                                                               | Qualifier                                                                                         |
+|--------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|
+| CONF-PHMR-25 | Schematron validation | Context: patient/birthTime<br>Test: contains(translate(@value,"+","-","ZZ"),"Z")                                                         | OPTIONAL: INFO message if constraint is not satisfied                                             |
+| CONF-PHMR-25 | Schematron validation | Context: patient/birthTime<br>Test: contains(translate(@value,"+","-","ZZ"),"Z")                                                         | OPTIONAL: INFO message if constraint is not satisfied                                             |
+| CONF-PHMR-2  | Schematron validation | Context: ClinicalDocument<br>Test: not ( templateId/@root='2.16.840.1.113883.10.20.9')                                                   | MANDATORY: FAIL if constraint is not satisfied                                                    |
+| CONF-PHMR-25 | Schematron validation | Context: patient/ birthTime<br>Test: not ((string-length(@value)>=4) or (@nullFlavor) )                                                  | MANDATORY: FAIL if constraint is not satisfied                                                    |
+| CONF-PHMR-25 | Schematron validation | Context: patient/ birthTime<br>Test: not ((string-length(@value)>=8) or (@nullFlavor) )                                                  | RECOMMENDED: WARNING message if constraint is not satisfied                                       |
+| CONF-PHMR-25 | Schematron validation | Context: patient/ administrativeGenderCode<br>Test: not ((@code='M' or @code='F' or @code='UN') and @codeSystem='2.16.840.1.113883.5.1') | RECOMMENDED: WARNING message if constraint is not satisfied                                       |
+| CONF-PHMR-25 | Schematron validation | Context: patient/ birthTime<br>Test: not (contains(translate(@value,"+","-","ZZ"),"Z"))                                                  | OPTIONAL: INFO message if constraint is not satisfied                                             |
+| CONF-PHMR-25 | Schematron validation | context: patient/ birthTime<br>Test: contains(translate(@value,"+","-","ZZ"),"Z")                                                        | OPTIONAL: INFO message if constraint is not satisfied                                             |
+| CONF-PHMR-33 | Schematron validation | Context: dataEnterer<br>Test: not ( assignedEntity/ assignedPerson)                                                                      | MANDATORY: FAIL if constraint is not satisfied                                                    |
+| CONF-PHMR-33 | Schematron validation | context: dataEnterer<br>Test: time                                                                                                       | OPTIONAL: INFO message if constraint is not satisfied                                             |
+| CONF-PHMR-33 | Schematron validation | Context: dataEnterer<br>Test: not ( time)                                                                                                | OPTIONAL: INFO message if constraint is not satisfied                                             |
+| CONF-PHMR-35 | Schematron validation | Context: informant<br>Test: not (( assignedEntity/ assignedPerson) or ( relatedEntity/ relatedPerson))                                   | MANDATORY: FAIL if constraint is not satisfied                                                    |
+| CONF-PHMR-35 | Schematron validation | context: ClinicalDocument<br>Test: informant                                                                                             | INFO: CONF-PHMR-35: The informant element MAY be present. The informant element IS present. Line: |
+| CONF-PHMR-35 | Schematron validation | Context: ClinicalDocument<br>Test: not ( informant)                                                                                      | INFO: CONF-PHMR-35: The informant element MAY be present. The informant element                   |
+
+**Table B-4-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI            | Validation type       | Constraint                                                                                                                                                                 | Qualifier                                                         |
+|---------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|
+|               |                       |                                                                                                                                                                            | IS NOT present. Line: CONF-PHMR-133                               |
+| CONF-PHMR-133 | Schematron validation | Context: *[ section]<br>Test: not (not( text/ reference) or ( text/ reference and entry// text/ reference))                                                                | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF-PHMR-133 | Schematron validation | context: *[ section/ text]<br>Test: // content/@ID                                                                                                                         | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-PHMR-133 | Schematron validation | Context: *[ section/ text]<br>Test: not (// content/@ID)                                                                                                                   | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-PHMR-133 | Schematron validation | Context: *[ observation/ value/@xsi:type="IVL_PQ"/ value/@xsi:type="IVL_PQ"]<br>Test: not ( low)                                                                           | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-133 | Schematron validation | Context: *[ observation/ value/@xsi:type="IVL_PQ"/ value/@xsi:type="IVL_PQ"]<br>Test: not ( high)                                                                          | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-134 | Schematron validation | Context: *[ value/@xsi:type="PPD_PQ"/ value/@xsi:type="PPD_PQ"]<br>Test: not (@value)                                                                                      | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-134 | Schematron validation | Context: *[ value/@xsi:type="PPD_PQ"/ value/@xsi:type="PPD_PQ"]<br>Test: not ( standardDeviation)                                                                          | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-134 | Schematron validation | Context: *[ value/@xsi:type="PPD_PQ"/ value/@xsi:type="PPD_PQ"]<br>Test: not ( standardDeviation/@value)                                                                   | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-69  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.4"]<br>Test: not (self:: organizer[@classCode='CLUSTER'][@moodCode='EVN'])                                         | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-71  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.4"]<br>Test: not ( participant[@typeCode='SBJ'] and participant// templateId[@root='2.16.840.1.113883.10.20.9.9']) | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-72  | Schematron validation | context: *[ templateId/@root="2.16.840.1.113883.10.20.9.4"]<br>Test: component// templateId[@root='2.16.840.1.113883.10.20.9.10']                                          | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-PHMR-73  | Schematron validation | context: *[ templateId/@root="2.16.840.1.113883.10.20.9.4"]<br>Test: component// templateId[@root='2.16.840.1.113883.10.20.9.5']                                           | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-PHMR-74  | Schematron validation | context: *[ templateId/@root="2.16.840.1.113883.10.20.9.4"]<br>Test: component// templateId[@root='2.16.840.1.113883.10.20.9.6']                                           | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-PHMR-75  | Schematron validation | context: *[ templateId/@root="2.16.840.1.113883.10.20.9.4"]<br>Test: component// templateId[@root='2.16.840.1.113883.10.20.9.3']                                           | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-PHMR-72  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.4"]<br>Test: not ( component// templateId[@root='2.16.840.1.113883.10.20.9.10'])                                   | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+
+**Table B-4-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI           | Validation type       | Constraint                                                                                                                                       | Qualifier                                             |
+|--------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|
+| CONF-PHMR-73 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.4"]<br>Test: not ( component// templateId[@root="2.16.840.1.113883.10.20.9.5"])          | OPTIONAL: INFO message if constraint is not satisfied |
+| CONF-PHMR-74 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.4"]<br>Test: not ( component// templateId[@root="2.16.840.1.113883.10.20.9.6"])          | OPTIONAL: INFO message if constraint is not satisfied |
+| CONF-PHMR-75 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.4"]<br>Test: not ( component// templateId[@root="2.16.840.1.113883.10.20.9.3"])          | OPTIONAL: INFO message if constraint is not satisfied |
+| CONF-PHMR-90 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.5"]<br>Test: not (self:: observation)                                                    | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-90 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.5"]<br>Test: not (@moodCode='DEF')                                                       | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-90 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.5"]<br>Test: not (@classCode='OBS')                                                      | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-92 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.5"]<br>Test: not ( code)                                                                 | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-92 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.5"]<br>Test: not ( code/@code='MDC_ATTR_NU_RANGE_MSMT' or not( code))                    | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-92 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.5"]<br>Test: not ( code/@codeSystem="2.16.840.1.113883.6.24" or not( code))              | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-93 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.5"]<br>Test: not ( value)                                                                | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-93 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.5"]<br>Test: not (( value/@xsi:type='IVL_PQ') or ( value/@xsi:type='ST') or not( value)) | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-94 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.6"]<br>Test: not (self:: observation)                                                    | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-94 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.6"]<br>Test: not (@moodCode='DEF')                                                       | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-94 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.6"]<br>Test: not (@classCode='OBS')                                                      | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-96 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.6"]<br>Test: not ( code)                                                                 | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-96 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.6"]<br>Test: not ( code/@code="17441009" or not( code))                                  | MANDATORY: FAIL if constraint is not satisfied        |
+
+**Table B-4-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI            | Validation type       | Constraint                                                                                                                                                                                          | Qualifier                                      |
+|---------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| CONF-PHMR-96  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.6"]<br>Test: not ( code/@codeSystem='2.16.840.1.113883.6.96' or not( code))                                                                 | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-97  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.6"]<br>Test: not ( value)                                                                                                                   | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-97  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.6"]<br>Test: not (( value/@xsi:type='PQ') or ( value/@xsi:type='ST') or not( value))                                                        | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-97  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.6"]<br>Test: not ((string( value[@xsi:type="PQ"]/@unit) = document("UCUM.xml")/Codes/code/@unit) or not( value) or ( value/@xsi:type="ST")) | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-98  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.3"]<br>Test: not (self:: observation)                                                                                                       | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-98  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.3"]<br>Test: not (@moodCode='DEF')                                                                                                          | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-98  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.3"]<br>Test: not (@classCode='OBS')                                                                                                         | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-98  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.3"]<br>Test: not ( code)                                                                                                                    | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-101 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.3"]<br>Test: not ( code/@code='MDC_ATTR_NU_ACCUR_MSMT' or not( code))                                                                       | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-100 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.3"]<br>Test: not ( code/@codeSystem='2.16.840.1.113883.6.24' or not( code))                                                                 | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-101 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.3"]<br>Test: not ( value)                                                                                                                   | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-101 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.3"]<br>Test: not (( value/@xsi:type='PQ') or ( value/@xsi:type='ST') or not( value))                                                        | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-102 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.8"]<br>Test: not (self:: observation)                                                                                                       | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-102 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.8"]<br>Test: not (@moodCode='EVN')                                                                                                          | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-102 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.8"]<br>Test: not (@classCode='OBS')                                                                                                         | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-105 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.8"]<br>Test: not ( code)                                                                                                                    | MANDATORY: FAIL if constraint is not satisfied |
+
+**Table B-4-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI            | Validation type       | Constraint                                                                                                                                                                                                                                                                                            | Qualifier                                                      |
+|---------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|
+| CONF-PHMR-105 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.8"]<br>Test: not (( code/@codeSystem="2.16.840.1.113883.6.96") or ( code/@codeSystem="2.16.840.1.113883.6.24") or not( code))                                                                                                                 | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-PHMR-106 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.8"]<br>Test: not ( value)                                                                                                                                                                                                                     | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-PHMR-106 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.8"]<br>Test: not (( value[@xsi:type='PQ']) or not( value))                                                                                                                                                                                    | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-PHMR-107 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.8"]<br>Test: not ( participant)                                                                                                                                                                                                               | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-PHMR-104 | Schematron validation | context: *[ templateId/@root="2.16.840.1.113883.10.20.9.8"]<br>Test: ( id and count( statusCode)=1 and count( code)=1 and count( value)=1 and not( referenceRange/ observationRange/ code) and value[@xsi:type='PQ'] and count( effectiveTime)<2 and templateId/@root="2.16.840.1.113883.10.20.1.31') | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-449      | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: not (self.: participantRole)                                                                                                                                                                                                     | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-450      | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: not (@classCode='MANU')                                                                                                                                                                                                          | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-78       | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: not ( id)                                                                                                                                                                                                                        | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-78       | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: not ( id/@root="1.2.840.10004.1.1.1.0.0.1.0.0.1.2680" or not( id))                                                                                                                                                               | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-80       | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: not (( playingDevice/ code/@codeSystem="2.16.840.1.113883.6.24") or ( playingDevice/ code/@codeSystem="2.16.840.1.113883.6.96"))                                                                                                 | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-80       | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: not (not( playingDevice/ code/@codeSystem="2.16.840.1.113883.6.96") or ( playingDevice/ code/@codeSystem="2.16.840.1.113883.6.96" and playingDevice/ code/ translation))                                                         | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-81       | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: not (( playingDevice/ manufacturerModelName))                                                                                                                                                                                    | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-81       | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: not (not( playingDevice/ manufacturerModelName) or contains( playingDevice/ manufacturerModelName,'Model'))                                                                                                                      | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-81       | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: not (not( playingDevice/ manufacturerModelName) or contains( playingDevice/ manufacturerModelName,'Serial number'))                                                                                                              | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-81       | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: not (not( playingDevice/ manufacturerModelName) or contains( playingDevice/ manufacturerModelName,'Part number'))                                                                                                                | MANDATORY: FAIL if constraint is not satisfied                 |
+
+**Table B-4-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI       | Validation type       | Constraint                                                                                                                                                                                             | Qualifier                                                      |
+|----------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|
+| CONF-81  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: not (not( playingDevice/ manufacturerModelName) or contains( playingDevice/ manufacturerModelName,'Hardware revision'))           | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-81  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: not (not( playingDevice/ manufacturerModelName) or contains( playingDevice/ manufacturerModelName,'Software revision'))           | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-81  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: not (not( playingDevice/ manufacturerModelName) or contains( playingDevice/ manufacturerModelName,'Protocol revision'))           | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-81  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: not (not( playingDevice/ manufacturerModelName) or contains( playingDevice/ manufacturerModelName,'Unspecified'))                 | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-82  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: not ( scopingEntity/ desc)                                                                                                        | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-451 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: not (( id and scopingEntity) or not( id))                                                                                         | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-879 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: not ( code/@nullFlavor='OTH')                                                                                                     | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-79  | Schematron validation | context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: code/@nullFlavor='OTH'                                                                                                            | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-79  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: not ( code/ originalText)                                                                                                         | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-79  | Schematron validation | context: *[ templateId/@root="2.16.840.1.113883.10.20.9.9"]<br>Test: code/ originalText                                                                                                                | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-68  | Schematron validation | Context: structuredBody// effectiveTime<br>Test: not (contains(translate(@value,"+","ZZ"),"Z") or ( contains(translate( low/@value,"+","ZZ"),"Z") and contains(translate( high/@value,"+","ZZ"),"Z"))) | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-68  | Schematron validation | Context: structuredBody// effectiveTime<br>Test: not ((string-length(@value)>=10) or((string-length( low/@value)>=10) and (string-length( high/@value)>=10)) )                                         | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-66  | Schematron validation | Context: observation<br>Test: not (( entryRelationship/ act and value) or not( value))                                                                                                                 | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-66  | Schematron validation | context: observation<br>Test: ( entryRelationship/ act and value)                                                                                                                                      | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+
+**Table B-4-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI           | Validation type       | Constraint                                                                                                                                                                              | Qualifier                                                      |
+|--------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|
+| CONF-PHMR-49 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.7"]<br>Test: not ( templateId[@root="2.16.840.1.113883.10.20.9.1"])                                                             | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-PHMR-50 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.7"]<br>Test: not (// templateId[@root="2.16.840.1.113883.10.20.9.4"])                                                           | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-PHMR-45 | Schematron validation | Context: section<br>Test: not ( code)                                                                                                                                                   | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-PHMR-46 | Schematron validation | Context: section<br>Test: not ( text or // section)                                                                                                                                     | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-PHMR-47 | Schematron validation | Context: structuredBody<br>Test: not ( component// section/ templateId[@root="2.16.840.1.113883.10.20.1.7"])                                                                            | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-PHMR-48 | Schematron validation | Context: structuredBody<br>Test: not ( component// section/ templateId[@root="2.16.840.1.113883.10.20.1.16"] or component// section/ templateId[@root="2.16.840.1.113883.10.20.1.14"])  | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-PHMR-61 | Schematron validation | context: structuredBody<br>Test: component// section/ templateId[@root="2.16.840.1.113883.10.20.1.13"]                                                                                  | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-PHMR-62 | Schematron validation | context: structuredBody<br>Test: component// section/ templateId[@root="2.16.840.1.113883.10.20.1.8"]                                                                                   | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-PHMR-63 | Schematron validation | context: structuredBody<br>Test: component// section/ templateId[@root="2.16.840.1.113883.10.20.1.5"]                                                                                   | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-PHMR-48 | Schematron validation | context: structuredBody<br>Test: component// section/ templateId[@root="2.16.840.1.113883.10.20.1.16"] and component// section/ templateId[@root="2.16.840.1.113883.10.20.1.14"]        | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-PHMR-61 | Schematron validation | Context: structuredBody<br>Test: not ( component// section/ templateId[@root="2.16.840.1.113883.10.20.1.13"])                                                                           | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-PHMR-62 | Schematron validation | Context: structuredBody<br>Test: not ( component// section/ templateId[@root="2.16.840.1.113883.10.20.1.8"])                                                                            | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-PHMR-63 | Schematron validation | Context: structuredBody<br>Test: not ( component// section/ templateId[@root="2.16.840.1.113883.10.20.1.5"])                                                                            | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-PHMR-48 | Schematron validation | Context: structuredBody<br>Test: not ( component// section/ templateId[@root="2.16.840.1.113883.10.20.1.16"] and component// section/ templateId[@root="2.16.840.1.113883.10.20.1.14"]) | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-PHMR-57 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.14"]<br>Test: not ( templateId[@root="2.16.840.1.113883.10.20.9.14"])                                                           | MANDATORY: FAIL if constraint is not satisfied                 |
+
+**Table B-4-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI           | Validation type       | Constraint                                                                                                                                                                                 | Qualifier                                                         |
+|--------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|
+| CONF-PHMR-58 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.14"]<br>Test: not ( entry// templateId[@root="2.16.840.1.113883.10.20.9.8"])                                                       | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF-PHMR-59 | Schematron validation | context: *[ templateId/@root="2.16.840.1.113883.10.20.1.14"]<br>Test: entry// templateId[@root="2.16.840.1.113883.10.20.9.12"]                                                             | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-PHMR-59 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.14"]<br>Test: not ( entry// templateId[@root="2.16.840.1.113883.10.20.9.12"])                                                      | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-PHMR-52 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.16"]<br>Test: not ( templateId[@root="2.16.840.1.113883.10.20.9.2"])                                                               | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-49 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.7"]<br>Test: not ( templateId[@root="2.16.840.1.113883.10.20.9.1"])                                                                | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-54 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.16"]<br>Test: not ( entry// templateId[@root="2.16.840.1.113883.10.20.9.8"])                                                       | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF-PHMR-55 | Schematron validation | context: *[ templateId/@root="2.16.840.1.113883.10.20.1.16"]<br>Test: entry// templateId[@root="2.16.840.1.113883.10.20.9.12"]                                                             | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-PHMR-55 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.16"]<br>Test: not ( entry// templateId[@root="2.16.840.1.113883.10.20.9.12"])                                                      | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-PHMR-84 | Schematron validation | Context: *[ participant/@typeCode="SBJ" and not( participant/ participantRole/<br>templateId/@root="2.16.840.1.113883.10.20.9.9")]/ participant/ participantRole<br>Test: not (count(*)=1) | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-85 | Schematron validation | Context: *[ participant/@typeCode="SBJ" and not( participant/ participantRole/<br>templateId/@root="2.16.840.1.113883.10.20.9.9")]/ participant/ participantRole<br>Test: not (count(*)=1) | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-86 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.10"]<br>Test: not (self:: observation)                                                                                             | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-86 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.10"]<br>Test: not (@moodCode='DEF')                                                                                                | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-86 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.10"]<br>Test: not (@classCode='OBS')                                                                                               | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-88 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.10"]<br>Test: not ( code)                                                                                                          | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-88 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.10"]<br>Test: not ( code/@code='MDC_ATTR_TIME_PD_SAMP' or not( code))                                                              | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+
+**Table B-4-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI            | Validation type       | Constraint                                                                                                                                                                                                                   | Qualifier                                      |
+|---------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| CONF-PHMR-88  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.10"]<br>Test: not ( code/@codeSystem='2.16.840.1.113883.6.24' or not( code))                                                                                         | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-89  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.10"]<br>Test: not ( value)                                                                                                                                           | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-89  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.10"]<br>Test: not ( value/@xsi:type='PQ' or not( value))                                                                                                             | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-89  | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.10"]<br>Test: not ( value/@unit='ms' or not( value))                                                                                                                 | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-108 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.12"]<br>Test: not (self:: observation)                                                                                                                               | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-108 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.12"]<br>Test: not (@moodCode='EVN')                                                                                                                                  | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-108 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.12"]<br>Test: not (@classCode='OBSSER')                                                                                                                              | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-110 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.12"]<br>Test: not ( code)                                                                                                                                            | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-110 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.12"]<br>Test: not (( code/@codeSystem='2.16.840.1.113883.6.96' or not( code))                                                                                        | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-111 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.12"]<br>Test: not ( effectiveTime)                                                                                                                                   | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-111 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.12"]<br>Test: not (descendant:: effectiveTime/ high)                                                                                                                 | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-111 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.12"]<br>Test: not (descendant:: effectiveTime/ low)                                                                                                                  | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-113 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.12"]<br>Test: not (( entryRelationship/ observationMedia and entryRelationship/ observationMedia/ value/ reference) or not(<br>entryRelationship/ observationMedia)) | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-115 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.12"]<br>Test: not (count( entryRelationship[@typeCode='COMP']// templateId[@root='2.16.840.1.113883.10.20.9.13'])=1)                                                 | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-116 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.12"]<br>Test: not ( entryRelationship[@typeCode='COMP']// templateId[@root='2.16.840.1.113883.10.20.9.11'])                                                          | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-PHMR-112 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.12"]<br>Test: not ( participant)                                                                                                                                     | RECOMMENDED:<br>WARNING message if             |
+
+**Table B-4-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI            | Validation type       | Constraint                                                                                                                                                          | Qualifier                                                         |
+|---------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|
+|               |                       |                                                                                                                                                                     | constraint is not satisfied                                       |
+| CONF-PHMR-113 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.12"]<br>Test: not ( entryRelationship/ observationMedia)                                                    | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF-PHMR-114 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.12"]<br>Test: not ( entryRelationship[@typeCode='COMP']/ observation[@classCode='OBSCOR'][@moodCode='EVN']) | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF-PHMR-117 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.13"]<br>Test: not (self:: observation)                                                                      | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-117 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.13"]<br>Test: not (@moodCode='EVN')                                                                         | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-117 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.13"]<br>Test: not (@classCode='OBS')                                                                        | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-119 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.13"]<br>Test: not ( code)                                                                                   | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-119 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.13"]<br>Test: not ( code/@code ='TIME_ABSOLUTE' or not( code))                                              | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-119 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.13"]<br>Test: not ( code/@codeSystem ='2.16.840.1.113883.5.4' or not( code))                                | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-120 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.13"]<br>Test: not ( value)                                                                                  | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-120 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.13"]<br>Test: not ( value/@xsi:type='GLIST_TS' or not( value))                                              | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-120 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.13"]<br>Test: not ( value/ head or not( value))                                                             | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-120 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.13"]<br>Test: not ( value/ increment or not( value))                                                        | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-121 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.11"]<br>Test: not (self:: observation)                                                                      | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-PHMR-121 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.11"]<br>Test: not (@moodCode='EVN')                                                                         | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+
+**Table B-4-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI            | Validation type       | Constraint                                                                                                                                   | Qualifier                                             |
+|---------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|
+| CONF-PHMR-121 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.11"]<br>Test: not (@classCode='OBS')                                                 | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-123 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.11"]<br>Test: not ( code)                                                            | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-123 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.11"]<br>Test: not ( code/@codeSystem='2.16.840.1.113883.6.96' or not( code))         | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-124 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.11"]<br>Test: not (( value and value/@xsi:type='SLIST_PQ' ) or not( value))          | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-124 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.11"]<br>Test: not (( value/ origin and value) or (not( value)))                      | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-124 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.11"]<br>Test: not (( value/ scale and value) or (not( value)))                       | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-124 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.11"]<br>Test: not (( value/ digits and value) or (not( value)))                      | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-124 | Schematron validation | context: *[ templateId/@root="2.16.840.1.113883.10.20.9.11"]<br>Test: value                                                                  | OPTIONAL: INFO message if constraint is not satisfied |
+| CONF-PHMR-124 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.11"]<br>Test: not ( value)                                                           | OPTIONAL: INFO message if constraint is not satisfied |
+| CONF-PHMR-125 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.7"]<br>Test: not (self:: observation)                                                | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-125 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.7"]<br>Test: not (@moodCode='EVN')                                                   | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-125 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.7"]<br>Test: not (@classCode='OBS')                                                  | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-127 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.7"]<br>Test: not ( code)                                                             | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-127 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.7"]<br>Test: not ( code/@codeSystem='2.16.840.1.113883.6.24' or not( code))          | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-128 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.7"]<br>Test: not ( value)                                                            | MANDATORY: FAIL if constraint is not satisfied        |
+| CONF-PHMR-128 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.7"]<br>Test: not (( value/@xsi:type='CS') or ( value/@xsi:type='ST') or not( value)) | MANDATORY: FAIL if constraint is not satisfied        |
+
+**Table B-4-1 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCDA/BV-000**
+
+| TI            | Validation type       | Constraint                                                                                              | Qualifier                                                         |
+|---------------|-----------------------|---------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|
+| CONF-PHMR-129 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.9.7"]<br>Test: not ( participant/@typeCode='SBJ') | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| GenDF-3       | Schematron validation | Context: ClinicalDocument<br>Test: not (informationRecipient)                                           | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| GenDF-4       | Schematron validation | Context: ClinicalDocument<br>Test: not (custodian)                                                      | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| GenDF-5       | Schematron validation | Context: ClinicalDocument/author/assignedAuthor<br>Test: not (representedOrganization)                  | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| GenDF-7       | Schematron validation | Context: ClinicalDocument/author/assignedAuthor<br>Test: not (assignedAuthoringDevice)                  | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+
+#### **B.4.2 For TP/HIS/SEN/CCCD/BV-000**
+
+**Table B-4-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCCD/BV-000**
+
+| TI       | Validation type       | Constraint                                                                                                                                                                                               | Qualifier                                         |
+|----------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|
+| CONF-123 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]<br>Test: not (self::cda:section)                                                                                                          | MANDATORY: FAIL if<br>constraint is not satisfied |
+| CONF-123 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]<br>Test: not (cda:text)                                                                                                                   | MANDATORY: FAIL if<br>constraint is not satisfied |
+| CONF-124 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]<br>Test: not (cda:code[@code='47420-5'][@codeSystem="2.16.840.1.113883.6.1"]or not(cda:code))                                             | MANDATORY: FAIL if<br>constraint is not satisfied |
+| CONF-126 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]<br>Test: not (cda:title)                                                                                                                  | MANDATORY: FAIL if<br>constraint is not satisfied |
+| CONF-136 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: not ( count(//cda:templateId[@root="2.16.840.1.113883.10.20.1.44"]) )=1 ) | MANDATORY: FAIL if<br>constraint is not satisfied |
+| CONF-128 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: not ( count(cda:code )=1)                                                 | MANDATORY: FAIL if<br>constraint is not satisfied |
+| CONF-128 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.5.31"]<br>Test: not ( count(cda:code )=1 )                                              | MANDATORY: FAIL if<br>constraint is not satisfied |
+| CONF-137 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.5.31"]<br>Test: not (count(//cda:templateId[@root="2.16.840.1.113883.10.20.1.44"])=1)   | MANDATORY: FAIL if<br>constraint is not satisfied |
+
+**Table B-4-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCCD/BV-000**
+
+| TI       | Validation type       | Constraint                                                                                                                                                                                                                                                                                                                    | Qualifier                                                         |
+|----------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|
+| CONF-123 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]<br>Test: not (descendant::*[cda:templateId/@root="2.16.840.1.113883.10.20.1.27"]  <br>descendant::*[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"])                                                                                                      | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF-127 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]<br>Test: not (contains(translate(cda:title,'QWERTYUIOPASDFGHJKLZXCVBNM','qwertyuiopasdfghjklzxcvbnm'),'functional<br>status') or not(cda:title))                                                                                                               | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF-133 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.5.31"]<br>Test: not ((cda:value[@type="CE" or @type="CD"] and cda:observation/cda:value/@codeSystem=<br>cda:observation/cda:code/@codeSystem) or not(cda:observation/cda:value[@type="CE" or @type="CD"] ) ) | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF-134 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"]<br>Test: cda:value/cda:translation                                                                                                                                                                      | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-134 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"]<br>Test: not (cda:value/cda:translation)                                                                                                                                                                | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-129 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: cda:code[@codeSystem="2.16.840.1.113883.1.11.20.6"]                                                                                                                                            | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-135 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: cda:code[@codeSystem="2.16.840.1.113883.6.254"]                                                                                                                                                | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-129 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: not (cda:code[@codeSystem="2.16.840.1.113883.1.11.20.6"])                                                                                                                                      | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-135 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: not (cda:code[@codeSystem="2.16.840.1.113883.6.254"])                                                                                                                                          | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-129 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: cda:code[@codeSystem="2.16.840.1.113883.1.11.20.6"]                                                                                                                                            | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-135 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: cda:code[@codeSystem="2.16.840.1.113883.6.254"]                                                                                                                                                | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-134 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: cda:value[@type="CE" or @type="CD"]                                                                                                                                                            | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-129 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: not (cda:code[@codeSystem="2.16.840.1.113883.1.11.20.6"])                                                                                                                                      | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-135 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: not (cda:code[@codeSystem="2.16.840.1.113883.6.254"])                                                                                                                                          | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-134 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.5"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: not (cda:value[@type="CE" or @type="CD"])                                                                                                                                                      | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-371 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.7"]<br>Test: not (self::cda:section)                                                                                                                                                                                                                               | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-371 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.7"]<br>Test: not (cda:text)                                                                                                                                                                                                                                        | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+
+**Table B-4-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCCD/BV-000**
+
+| TI       | Validation type       | Constraint                                                                                                                                                                                           | Qualifier                                                      |
+|----------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|
+| CONF-372 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.7"]<br>Test: not (cda:code)                                                                                                               | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-373 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.7"]<br>Test: not (cda:code[@code='46264-8'][@codeSystem='2.16.840.1.113883.6.1'] or not(cda:code)))                                       | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-374 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.7"]<br>Test: not (cda:title)                                                                                                              | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-371 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.7"]<br>Test: not (descendant::*[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"])                                                     | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-375 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.7"]<br>Test: not (contains(translate(cda:title,'QWERTYUIOPASDFGHJKLZXCVBNM','qwertyuiopasdfghjklzxcvbnm'),'equipment'))                   | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-371 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.7"]<br>Test: descendant::*[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]                                                           | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-371 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.7"]<br>Test: not (descendant::*[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"])                                                     | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-15  | Schematron validation | Context: cda:structuredBody<br>Test: not (count(cda:component/cda:section/cda:templateId[@root='2.16.840.1.113883.10.20.1.13']) < 2)                                                                 | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-15  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.13"]<br>Test: not (self::cda:section)                                                                                                     | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-15  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.13"]<br>Test: not (cda:text)                                                                                                              | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-16  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.13"]<br>Test: not (cda:code[@code='48764-5'][@codeSystem='2.16.840.1.113883.6.1'] or not(cda:code)))                                      | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-18  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.13"]<br>Test: not (cda:title)                                                                                                             | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-15  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.13"]<br>Test: not (descendant::*[cda:templateId/@root="2.16.840.1.113883.10.20.1.30"])                                                    | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-19  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.13"]<br>Test: not (contains(translate(cda:title,'QWERTYUIOPASDFGHJKLZXCVBNM','qwertyuiopasdfghjklzxcvbnm'),'purpose') or not(cda:title))) | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-15  | Schematron validation | Context: cda:structuredBody<br>Test: cda:component/cda:section/cda:templateId[@root='2.16.840.1.113883.10.20.1.13']                                                                                  | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-15  | Schematron validation | Context: cda:structuredBody<br>Test: not (cda:component/cda:section/cda:templateId[@root='2.16.840.1.113883.10.20.1.13'])                                                                            | OPTIONAL: INFO message if constraint is not satisfied          |
+
+**Table B-4-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCCD/BV-000**
+
+| TI       | Validation type       | Constraint                                                                                                                                                                                                                                                                                                                                                                   | Qualifier                                                      |
+|----------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|
+| CONF-388 | Schematron validation | Context: cda:structuredBody<br>Test: not (count(cda:component/cda:section/cda:templateId[@root="2.16.840.1.113883.10.20.1.14"]< 2))                                                                                                                                                                                                                                          | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-388 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.14"]<br>Test: not (self::cda:section)                                                                                                                                                                                                                                                                             | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-388 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.14"]<br>Test: not (cda:text)                                                                                                                                                                                                                                                                                      | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-389 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.14"]<br>Test: not (cda:code)                                                                                                                                                                                                                                                                                      | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-390 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.14"]<br>Test: not (cda:code[@code='30954-2'][@codeSystem='2.16.840.1.113883.6.1'] or not(cda:code))                                                                                                                                                                                                               | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-391 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.14"]<br>Test: not (cda:title)                                                                                                                                                                                                                                                                                     | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-388 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.14"]<br>Test: not ((descendant::*[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"] and<br>descendant::*[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"]/descendant::*[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]) or not(descendant::*[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"]))) | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-388 | Schematron validation | Context: cda:structuredBody<br>Test: not (cda:component/cda:section/cda:templateId[@root="2.16.840.1.113883.10.20.1.14"])                                                                                                                                                                                                                                                    | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-388 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.14"]<br>Test: not (descendant::*[cda:templateId/@root="2.16.840.1.113883.10.20.1.35"])                                                                                                                                                                                                                            | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-392 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.14"]<br>Test: not (contains(translate(cda:title,'QWERTYUIOPASDFGHJKLZXCVBNM','qwertyuiopasdfghjklzxcvbnm'),'results') or not (cda:title))                                                                                                                                                                         | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-381 | Schematron validation | Context: cda:structuredBody<br>Test: not (count(cda:component/cda:section/cda:templateId[@root="2.16.840.1.113883.10.20.1.16"]< 2))                                                                                                                                                                                                                                          | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-381 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.16"]<br>Test: not (self::cda:section)                                                                                                                                                                                                                                                                             | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-381 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.16"]<br>Test: not (cda:text)                                                                                                                                                                                                                                                                                      | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-382 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.16"]<br>Test: not (cda:code)                                                                                                                                                                                                                                                                                      | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-383 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.16"]<br>Test: not (cda:code[@code='8716-3'][@codeSystem='2.16.840.1.113883.6.1'] or not(cda:code))                                                                                                                                                                                                                | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-384 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.16"]<br>Test: not (cda:title)                                                                                                                                                                                                                                                                                     | MANDATORY: FAIL if constraint is not satisfied                 |
+
+**Table B-4-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCCD/BV-000**
+
+| TI       | Validation type       | Constraint                                                                                                                                                                                                                                                                                                                                                                                                                                   | Qualifier                                                         |
+|----------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|
+| CONF-381 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.16"]<br>Test: not ((descendant::*[cda:templateId/@root="2.16.840.1.113883.10.20.1.35"] and<br>descendant::*[cda:templateId/@root="2.16.840.1.113883.10.20.1.35"]/descendant::*[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]) or not(descendant::*[cda:templateId/@root="2.16.840.1.113883.10.20.1.35"])))                                                                 | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-381 | Schematron validation | Context: cda:structuredBody<br>Test: not (cda:component/cda:section/cda:templateId[@root="2.16.840.1.113883.10.20.1.16"])                                                                                                                                                                                                                                                                                                                    | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF-381 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.16"]<br>Test: not (descendant::*[cda:templateId/@root="2.16.840.1.113883.10.20.1.35"])                                                                                                                                                                                                                                                                                            | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF-385 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.16"]<br>Test: not (contains(translate(cda:title,'QWERTYUIOPASDFGHJKLZXCVBNM','qwertyuiopasdfghjklzxcvbnm'),'vital signs') or<br>not (cda:title))                                                                                                                                                                                                                                  | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF-304 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (self::cda:substanceAdministration)                                                                                                                                                                                                                                                                                                                             | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-305 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (@moodCode='EVN' or @moodCode='INT')                                                                                                                                                                                                                                                                                                                            | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-306 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (cda:id)                                                                                                                                                                                                                                                                                                                                                        | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-312 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (count(cda:maxDoseQuantity) < 2)                                                                                                                                                                                                                                                                                                                                | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-313 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (count(cda:performer) < 2)                                                                                                                                                                                                                                                                                                                                      | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-338 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (count(cda:observation/cda:templateId[@root="2.16.840.1.113883.10.20.1.46"]) < 2)                                                                                                                                                                                                                                                                               | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-350 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (count(cda:observation/cda:templateId[@root="2.16.840.1.113883.10.20.1.47"]) < 2)                                                                                                                                                                                                                                                                               | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-354 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (count(cda:consumable)=1 and cda:consumable/cda:templateId[@root="2.16.840.1.113883.10.20.1.53"])                                                                                                                                                                                                                                                               | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-329 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not ((cda:entryRelationship[@typeCode='RSON']//cda:templateId[@root="2.16.840.1.113883.10.20.1.28"]) or<br>cda:entryRelationship[@typeCode='RSON']//cda:templateId[@root="2.16.840.1.113883.10.20.1.28"]) or<br>(cda:entryRelationship[@typeCode='RSON']//cda:templateId[@root="2.16.840.1.113883.10.20.1.27"]) or<br>not(cda:entryRelationship[@typeCode='RSON'])) | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-348 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.54"]<br>Test: not (count(cda:observation/cda:templateId[@root="2.16.840.1.113883.10.20.1.55"]) < 2)                                                                                                                                                                                                                        | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+
+**Table B-4-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCCD/BV-000**
+
+| TI       | Validation type       | Constraint                                                                                                                                                                                | Qualifier                                                      |
+|----------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|
+| CONF-349 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]//[cda:templateId/@root="2.16.840.1.113883.10.20.1.54"]<br>Test: not (ancestor::*[cda:entryRelationship/@typeCode='CAUS']) | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-339 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]//[cda:templateId/@root="2.16.840.1.113883.10.20.1.46"]<br>Test: not (ancestor::*[cda:entryRelationship/@typeCode='SUBJ']) | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-307 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (count(cda:statusCode)=1)                                                                                    | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-308 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (cda:effectiveTime)                                                                                          | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-309 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (count(cda:routeCode)=1)                                                                                     | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-310 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (cda:routeCode[@codeSystem="2.16.840.1.113883.5.112"])                                                       | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-311 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (count(cda:doseQuantity)=1 or count(cda:rateQuantity)=1 )                                                    | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-350 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: count(cda:observation/cda:templateId[@root="2.16.840.1.113883.10.20.1.47"])=1                                    | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-312 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: count(cda:maxDoseQuantity) =1                                                                                    | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-313 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: count(cda:performer) =1                                                                                          | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-350 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (count(cda:observation/cda:templateId[@root="2.16.840.1.113883.10.20.1.47"])=1)                              | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-312 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (count(cda:maxDoseQuantity) =1)                                                                              | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-313 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (count(cda:performer) =1)                                                                                    | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-327 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: cda:precondition/cda:Criterion                                                                                   | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-328 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: cda:entryRelationship[@typeCode='RSON']                                                                          | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-327 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (cda:precondition/cda:Criterion )                                                                            | OPTIONAL: INFO message if constraint is not satisfied          |
+
+**Table B-4-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCCD/BV-000**
+
+| TI       | Validation type       | Constraint                                                                                                                                                                                                                                                                                                  | Qualifier                                                   |
+|----------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|
+| CONF-328 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (cda:entryRelationship[@typeCode='RSON'])                                                                                                                                                                                      | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF-330 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: //cda:templateId[@root="2.16.840.1.113883.10.20.1.49"]                                                                                                                                                                             | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF-330 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (//cda:templateId[@root="2.16.840.1.113883.10.20.1.49"])                                                                                                                                                                       | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF-348 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: //cda:templateId[@root="2.16.840.1.113883.10.20.1.54"]                                                                                                                                                                             | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF-348 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (//cda:templateId[@root="2.16.840.1.113883.10.20.1.54"])                                                                                                                                                                       | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF-348 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: count(cda:entryRelationship/cda:observation/cda:templateId[@root="2.16.840.1.113883.10.20.1.46"])=1                                                                                                                                | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF-338 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (count(cda:entryRelationship/cda:observation/cda:templateId[@root="2.16.840.1.113883.10.20.1.46"])=1)                                                                                                                          | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF-368 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: //cda:templateId[@root="2.16.840.1.113883.10.20.1.52"]                                                                                                                                                                             | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF-368 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (//cda:templateId[@root="2.16.840.1.113883.10.20.1.52"])                                                                                                                                                                       | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF-314 | Schematron validation | context: cda:ClinicalDocument<br>Test: cda:authorization/cda:consent                                                                                                                                                                                                                                        | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF-314 | Schematron validation | Context: cda:ClinicalDocument<br>Test: not (cda:authorization/cda:consent)                                                                                                                                                                                                                                  | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF-145 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.27"]<br>Test: not (self::cda:act[@classCode='ACT'][@moodCode='EVN'])                                                                                                                                                                             | MANDATORY: FAIL if constraint is not satisfied              |
+| CONF-148 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.27"]<br>Test: not (cda:id)                                                                                                                                                                                                                       | MANDATORY: FAIL if constraint is not satisfied              |
+| CONF-149 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.27"]<br>Test: not (cda:code/@nullFlavor='NA' or not(cda:code))                                                                                                                                                                                   | MANDATORY: FAIL if constraint is not satisfied              |
+| CONF-150 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.27"]<br>Test: not (count(cda:effectiveTime) < 2)                                                                                                                                                                                                 | MANDATORY: FAIL if constraint is not satisfied              |
+| CONF-151 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.27"]<br>Test: not (cda:entryRelationship)                                                                                                                                                                                                        | MANDATORY: FAIL if constraint is not satisfied              |
+| CONF-153 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.27"]<br>Test: not (cda:entryRelationship[@typeCode='SUBJ']/cda:observation/cda:templateId[@root="2.16.840.1.113883.10.20.1.28"] or cda:entryRelationship[@typeCode='SUBJ']/cda:observation/cda:templateId[@root="2.16.840.1.113883.10.20.1.18"]) | RECOMMENDED: WARNING message if constraint is not satisfied |
+| CONF-150 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.27"]<br>Test: count(cda:effectiveTime) =1                                                                                                                                                                                                        | OPTIONAL: INFO message if constraint is not satisfied       |
+
+**Table B-4-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCCD/BV-000**
+
+| TI       | Validation type       | Constraint                                                                                                                                                                   | Qualifier                                                      |
+|----------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|
+| CONF-152 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.27"]<br>Test: cda:entryRelationship/cda:observation/cda:templateId[@root="2.16.840.1.113883.10.20.1.28"]          | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-150 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.27"]<br>Test: not (count(cda:effectiveTime) =1)                                                                   | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-152 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.27"]<br>Test: not (cda:entryRelationship/cda:observation/cda:templateId[@root="2.16.840.1.113883.10.20.1.28"])    | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-154 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: not (self::cda:observation[@moodCode='EVN'])                                                        | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-156 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: not (count(cda:statusCode)=1)                                                                       | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-157 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: not (cda:statusCode/@code='completed' or not(cda:statusCode))                                       | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-162 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: not (count(//cda:templateId[@root="2.16.840.1.113883.10.20.1.50"]) < 2)                             | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-165 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: not (count(//cda:templateId[@root="2.16.840.1.113883.10.20.1.51"]) < 2)                             | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-158 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: not (count(cda:effectiveTime)=1)                                                                    | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-162 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: count(//cda:templateId[@root="2.16.840.1.113883.10.20.1.50"]) =1                                    | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-165 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: count(//cda:templateId[@root="2.16.840.1.113883.10.20.1.51"]) =1                                    | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-159 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: cda:code[@codeSystem="2.16.840.1.113883.1.11.20.14"]                                                | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-160 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: cda:entryRelationship[@typeCode="SUBJ"]/cda:templateId[@root="2.16.840.1.113883.10.20.1.38"]        | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-162 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: not (count(//cda:templateId[@root="2.16.840.1.113883.10.20.1.50"]) =1)                              | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-165 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: not (count(//cda:templateId[@root="2.16.840.1.113883.10.20.1.51"]) =1)                              | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-159 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: not (cda:code[@codeSystem="2.16.840.1.113883.1.11.20.14"])                                          | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-160 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.28"]<br>Test: not (cda:entryRelationship[@typeCode="SUBJ"]//cda:templateId[@root="2.16.840.1.113883.10.20.1.38"]) | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF-20  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.30"]<br>Test: not (self::cda:act)                                                                                 | MANDATORY: FAIL if constraint is not satisfied                 |
+
+**Table B-4-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCCD/BV-000**
+
+| TI        | Validation type       | Constraint                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | Qualifier                                      |
+|-----------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| CONF-21   | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.30"]<br>Test: not (self::cda:act[@classCode='ACT'])                                                                                                                                                                                                                                                                                                                                                                            | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-22   | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.30"]<br>Test: not (self::cda:act[@moodCode='EVN'])                                                                                                                                                                                                                                                                                                                                                                             | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-26   | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.30"]<br>Test: not (count(cda:statusCode) = 1)                                                                                                                                                                                                                                                                                                                                                                                  | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-24   | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.30"]<br>Test: not (cda:statusCode[@code='completed'] or not(cda:statusCode))                                                                                                                                                                                                                                                                                                                                                   | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-25   | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.30"]<br>Test: not (cda:code[@code='23745001'][@codeSystem='2.16.840.1.113883.6.96'] or not(cda:code))                                                                                                                                                                                                                                                                                                                          | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-26   | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.30"]<br>Test: not (count(cda:entryRelationship[@typeCode='RSON'])=1)                                                                                                                                                                                                                                                                                                                                                           | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-27   | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.30"]<br>Test: not (cda:entryRelationship[@typeCode='RSON']/cda:act or cda:entryRelationship[@typeCode='RSON']/cda:encounter or cda:entryRelationship[@typeCode='RSON']/cda:observation or cda:entryRelationship[@typeCode='RSON']/cda:procedure or cda:entryRelationship[@typeCode='RSON']/cda:substanceAdministration or cda:entryRelationship[@typeCode='RSON']/cda:supply or not(cda:entryRelationship[@typeCode='RSON']))) | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 407 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: not (self::cda:observation)                                                                                                                                                                                                                                                                                                                                                                                      | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 408 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: not (@moodCode='EVN')                                                                                                                                                                                                                                                                                                                                                                                            | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 409 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: not (cda:id)                                                                                                                                                                                                                                                                                                                                                                                                     | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 410 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: not (count(cda:statusCode)=1)                                                                                                                                                                                                                                                                                                                                                                                    | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 412 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: not (count(cda:code)=1)                                                                                                                                                                                                                                                                                                                                                                                          | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 416 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: not (count(cda:value)=1)                                                                                                                                                                                                                                                                                                                                                                                         | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 420 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: not (not(cda:referenceRange/cda:observationRange/cda:code))                                                                                                                                                                                                                                                                                                                                                      | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 414 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: not ((not(cda:code/cda:methodCode) and count(cda:methodCode)<2) or cda:code)                                                                                                                                                                                                                                                                                                                                     | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 415 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: not (not(cda:code/cda:methodCode) or not(cda:methodCode) or (cda:methodCode and cda:code/cda:methodCode and cda:methodCode!=cda:code/cda:methodCode))                                                                                                                                                                                                                                                            | MANDATORY: FAIL if constraint is not satisfied |
+
+**Table B-4-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCCD/BV-000**
+
+| TI        | Validation type       | Constraint                                                                                                                                                                                                         | Qualifier                                                         |
+|-----------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|
+| CONF- 413 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: not (cda:code[@codeSystem="2.16.840.1.113883.6.1" or @codeSystem="2.16.840.1.113883.6.96"] or not(cda:code))                              | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF- 411 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: not (count(cda:effectiveTime)=1)                                                                                                          | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF- 418 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: not (count(cda:interpretationCode)=1)                                                                                                     | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF- 419 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: not (cda:referenceRange)                                                                                                                  | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF- 413 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: cda:code[@codeSystem="2.16.840.1.113883.6.12"]                                                                                            | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF- 414 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: (not(cda:code/cda:methodCode) and count(cda:methodCode)=1)                                                                                | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF- 413 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: not (cda:code[@codeSystem="2.16.840.1.113883.6.12"])                                                                                      | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF- 414 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"]<br>Test: not ((not(cda:code/cda:methodCode) and count(cda:methodCode)=1))                                                                          | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF- 393 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"]<br>Test: not (self::cda:organizer)                                                                                                                 | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF- 394 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"]<br>Test: not (@moodCode="EVN")                                                                                                                     | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF- 395 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"]<br>Test: not (cda:id)                                                                                                                              | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF- 396 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"]<br>Test: not (count(cda:statusCode)=1)                                                                                                             | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF- 397 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"]<br>Test: not (count(cda:code)=1)                                                                                                                   | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF- 402 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"]<br>Test: not (cda:component)                                                                                                                       | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF- 405 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"]<br>Test: not (cda:component/cda:observation[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"])                                                  | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF- 400 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"]<br>Test: not (not(cda:code/cda:specimen) or not(cda:specimen) or (cda:specimen and cda:code/cda:specimen and cda:specimen!=cda:code/cda:specimen)) | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+
+**Table B-4-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCCD/BV-000**
+
+| TI       | Validation type       | Constraint                                                                                                                                                                                   | Qualifier                                                         |
+|----------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|
+| CONF-398 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"]<br>Test: not (cda:code[@codeSystem="2.16.840.1.113883.6.1" or @codeSystem="2.16.840.1.113883.6.96"])                         | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF-399 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"]<br>Test: not ((not(cda:code/cda:specimen) and cda:specimen) or cda:code/cda:specimen)                                        | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF-403 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"]<br>Test: cda:component/cda:entryRelationship/cda:procedure                                                                   | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-398 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"]<br>Test: cda:code[@codeSystem="2.16.840.1.113883.6.12" or @codeSystem="2.16.840.1.113883.1.11.20.16"]                        | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-403 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"]<br>Test: not (cda:component/cda:entryRelationship/cda:procedure)                                                             | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-398 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.32"]<br>Test: not (cda:code[@codeSystem="2.16.840.1.113883.6.12" or @codeSystem="2.16.840.1.113883.1.11.20.16"])                  | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-316 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: not (self::cda:supply)                                                                                              | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-317 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: not (@moodCode='EVN' or @moodCode='INT')                                                                            | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-318 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: not (cda:id)                                                                                                        | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-321 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: not (count(cda:repeatNumber) < 2)                                                                                   | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-322 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: not (count(cda:quantity) < 2)                                                                                       | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-325 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: not (count(cda:participant[@typeCode='LOC']) < 2)                                                                   | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-351 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: not (count(cda:entryRelationship/cda:observation/cda:templateId[@root="2.16.840.1.113883.10.20.1.47"]) < 2)         | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-355 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: not (count(cda:product) < 2 or (cda:product and cda:product/cda:templateId[@root="2.16.840.1.113883.10.20.1.53"]))) | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-337 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.43"]<br>Test: not (ancestor::*[cda:entryRelationship/@typeCode='SUBJ'])    | MANDATORY: FAIL if<br>constraint is not satisfied                 |
+| CONF-319 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: not (count(cda:statusCode)=1)                                                                                       | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+
+**Table B-4-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCCD/BV-000**
+
+| TI       | Validation type       | Constraint                                                                                                                                                                         | Qualifier                                                         |
+|----------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|
+| CONF-320 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: not (count(cda:effectiveTime)=1)                                                                          | RECOMMENDED:<br>WARNING message if<br>constraint is not satisfied |
+| CONF-321 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: count(cda:repeatNumber)=1                                                                                 | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-322 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: count(cda:quantity) =1                                                                                    | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-323 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: cda:supply/cda:author                                                                                     | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-324 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: cda:supply/cda:performer                                                                                  | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-325 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: count(cda:participant[@typeCode="LOC"]) =1                                                                | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-334 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: //cda:templateId[@root="2.16.840.1.113883.10.20.1.43"]                                                    | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-351 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: count(cda:entryRelationship/cda:observation/cda:templateId[@root="2.16.840.1.113883.10.20.1.47"])=1       | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-355 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: cda:product/cda:templateId[@root="2.16.840.1.113883.10.20.1.53"]                                          | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-321 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: not (count(cda:repeatNumber)=1)                                                                           | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-322 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: not (count(cda:quantity) =1)                                                                              | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-323 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: not (cda:supply/cda:author)                                                                               | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-324 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: not (cda:supply/cda:performer)                                                                            | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-325 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: not (count(cda:participant[@typeCode="LOC"]) =1)                                                          | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-334 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: not (//cda:templateId[@root="2.16.840.1.113883.10.20.1.43"])                                              | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-351 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: not (count(cda:entryRelationship/cda:observation/cda:templateId[@root="2.16.840.1.113883.10.20.1.47"])=1) | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-355 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]<br>Test: not (cda:product/cda:templateId[@root="2.16.840.1.113883.10.20.1.53"])                                    | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+| CONF-369 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.52"]<br>Test: *                                                  | OPTIONAL: INFO message if<br>constraint is not satisfied          |
+
+**Table B-4-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCCD/BV-000**
+
+| TI        | Validation type       | Constraint                                                                                                                                                                                                         | Qualifier                                                   |
+|-----------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|
+| CONF-369  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.34"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.52"]<br>Test: not (*)                                                                            | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF-393  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.35"]<br>Test: not (self::cda:organizer)                                                                                                                 | MANDATORY: FAIL if constraint is not satisfied              |
+| CONF-394  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.35"]<br>Test: not (@moodCode='EVN')                                                                                                                     | MANDATORY: FAIL if constraint is not satisfied              |
+| CONF-395  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.35"]<br>Test: not (cda:id)                                                                                                                              | MANDATORY: FAIL if constraint is not satisfied              |
+| CONF-396  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.35"]<br>Test: not (count(cda:statusCode)=1)                                                                                                             | MANDATORY: FAIL if constraint is not satisfied              |
+| CONF-397  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.35"]<br>Test: not (count(cda:code)=1)                                                                                                                   | MANDATORY: FAIL if constraint is not satisfied              |
+| CONF-402  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.35"]<br>Test: not (cda:component)                                                                                                                       | MANDATORY: FAIL if constraint is not satisfied              |
+| CONF-400  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.35"]<br>Test: not (not(cda:code/cda:specimen) or not(cda:specimen) or (cda:specimen and cda:code/cda:specimen and cda:specimen!=cda:code/cda:specimen)) | MANDATORY: FAIL if constraint is not satisfied              |
+| CONF-405  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.35"]<br>Test: not (cda:component/cda:observation[cda:templateId/@root="2.16.840.1.113883.10.20.1.31"])                                                  | MANDATORY: FAIL if constraint is not satisfied              |
+| CONF-398  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.35"]<br>Test: not (cda:code[@codeSystem="2.16.840.1.113883.6.1" or @codeSystem="2.16.840.1.113883.6.96"] or not(cda:code))                              | RECOMMENDED: WARNING message if constraint is not satisfied |
+| CONF-399  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.35"]<br>Test: not ((not(cda:code/cda:specimen) and cda:specimen) or cda:code/cda:specimen)                                                              | RECOMMENDED: WARNING message if constraint is not satisfied |
+| CONF-403  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.35"]<br>Test: cda:component/cda:entryRelationship/cda:procedure                                                                                         | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF-398  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.35"]<br>Test: cda:code[@codeSystem="2.16.840.1.113883.6.12" or @codeSystem="2.16.840.1.113883.1.11.20.16"]                                              | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF-403  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.35"]<br>Test: not (cda:component/cda:entryRelationship/cda:procedure)                                                                                   | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF-398  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.35"]<br>Test: not (cda:code[@codeSystem="2.16.840.1.113883.6.12" or @codeSystem="2.16.840.1.113883.1.11.20.16"])                                        | OPTIONAL: INFO message if constraint is not satisfied       |
+| CONF- 335 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.43"]<br>Test: not (self::cda:act)                                                                                                                       | MANDATORY: FAIL if constraint is not satisfied              |
+| CONF- 336 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.43"]<br>Test: not (@moodCode='INT')                                                                                                                     | MANDATORY: FAIL if constraint is not satisfied              |
+
+**Table B-4-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCCD/BV-000**
+
+| TI        | Validation type       | Constraint                                                                                                                                                     | Qualifier                                      |
+|-----------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| CONF- 340 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.46"]<br>Test: not (self::cda:observation)                                                           | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 341 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.46"]<br>Test: not (@classCode='OBS')                                                                | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 342 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.46"]<br>Test: not (@moodCode='EVN')                                                                 | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 343 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.46"]<br>Test: not (count(cda:statusCode)=1)                                                         | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 344 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.46"]<br>Test: not (count(cda:code)=1)                                                               | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 345 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.46"]<br>Test: not (cda:code[@code='30973-2'][@codeSystem='2.16.840.1.113883.6.1'] or not(cda:code)) | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 346 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.46"]<br>Test: not (count(cda:value)=1)                                                              | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 347 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.46"]<br>Test: not (cda:value[@xsi:type='INT'] or not(cda:value))                                    | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-352  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.47"]<br>Test: not (self::cda:observation)                                                           | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-352  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.47"]<br>Test: not (//parent::*[cda:entryRelationship/@typeCode='REFR'])                             | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-352  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.47"]<br>Test: not (@classCode='OBS')                                                                | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-352  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.47"]<br>Test: not (@moodCode='EVN')                                                                 | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-352  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.47"]<br>Test: not (count(cda:code)=1)                                                               | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-352  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.47"]<br>Test: not (cda:code[@code='33999-4'][@codeSystem='2.16.840.1.113883.6.1'] or not(cda:code)) | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-352  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.47"]<br>Test: not (count(cda:statusCode)=1)                                                         | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-352  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.47"]<br>Test: not (cda:statusCode[@code='completed'] or not(cda:statusCode))                        | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-352  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.47"]<br>Test: not (count(cda:value[@xsi:type='CE'])=1 or not (cda:value))                           | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-331  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.49"]<br>Test: not (self::cda:act)                                                                   | MANDATORY: FAIL if constraint is not satisfied |
+
+**Table B-4-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCCD/BV-000**
+
+| TI        | Validation type       | Constraint                                                                                                                                    | Qualifier                                      |
+|-----------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| CONF-332  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.49"]<br>Test: not (@moodCode='INT')                                                | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-333  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.49"]<br>Test: not (ancestor::*[cda:entryRelationship/@typeCode='SUBJ'])            | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-163  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.50"]<br>Test: not (self::cda:observation)                                          | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 163 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.50"]<br>Test: not (parent::*[cda:entryRelationship/@typeCode='REFR'])              | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 163 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.50"]<br>Test: not (@classCode='OBS')                                               | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 163 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.50"]<br>Test: not (@moodCode='EVN')                                                | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 163 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.50"]<br>Test: not (count(cda:code)=1)                                              | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 163 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.50"]<br>Test: not (cda:code[@code='33999-4'][@codeSystem='2.16.840.1.113883.6.1']) | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 163 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.50"]<br>Test: not (count(cda:statusCode)=1)                                        | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 163 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.50"]<br>Test: not (cda:statusCode[@code='completed'])                              | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 163 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.50"]<br>Test: not (count(cda:value[@type='CE'])=1)                                 | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 164 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.50"]<br>Test: not (cda:value/@codeSystem='2.16.840.1.113883.1.11.20.13')           | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 166 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.51"]<br>Test: not (self::cda:observation)                                          | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 166 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.51"]<br>Test: not (parent::*[cda:entryRelationship/@typeCode='REFR'])              | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 166 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.51"]<br>Test: not (@classCode='OBS')                                               | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 166 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.51"]<br>Test: not (@moodCode='EVN')                                                | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 166 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.51"]<br>Test: not (count(cda:code)=1)                                              | MANDATORY: FAIL if constraint is not satisfied |
+| CONF- 166 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.51"]<br>Test: not (count(cda:statusCode)=1)                                        | MANDATORY: FAIL if constraint is not satisfied |
+
+**Table B-4-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCCD/BV-000**
+
+| TI        | Validation type       | Constraint                                                                                                                                                                                                                        | Qualifier                                                      |
+|-----------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|
+| CONF- 166 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.51"]<br>Test: not (cda:statusCode/@code='completed')                                                                                                                   | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF- 166 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.51"]<br>Test: not (count(cda:value[@type='CE'])=1)                                                                                                                     | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF- 166 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.51"]<br>Test: not (cda:code/@code='11323-3' and cda:code/@codeSystem='2.16.840.1.113883.6.1')                                                                          | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF- 167 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.51"]<br>Test: not (cda:value/@codeSystem='2.16.840.1.113883.1.11.20.12')                                                                                               | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF- 356 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.53"]<br>Test: not (self::cda:manufacturedProduct)                                                                                                                      | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF- 357 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.53"]<br>Test: not (count(cda:manufacturedMaterial)=1)                                                                                                                  | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF- 358 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.53"]<br>Test: not (count(cda:manufacturedMaterial/cda:code)=1)                                                                                                         | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF- 363 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.53"]<br>Test: not (count(cda:manufacturedMaterial/cda:code/cda:originalText)=1)                                                                                        | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF- 364 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.53"]<br>Test: not (count(cda:manufacturedMaterial/cda:name)< 2)                                                                                                        | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF- 365 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.53"]<br>Test: not (count(cda:manufacturerOrganization)< 2)                                                                                                             | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF- 359 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.53"]<br>Test: not (cda:manufacturedMaterial/cda:code[@codeSystem='2.16.840.1.113883.6.88'] or cda:manufacturedMaterial/cda:code[@codeSystem='2.16.840.1.113883.6.59']) | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF- 367 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.53"]<br>Test: not ((cda:id and cda:manufacturerOrganization) or not(cda:id))                                                                                           | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF- 364 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.53"]<br>Test: count(cda:manufacturedMaterial/cda:name)=1                                                                                                               | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF- 365 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.53"]<br>Test: count(cda:manufacturerOrganization)=1                                                                                                                    | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF- 366 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.53"]<br>Test: cda:id                                                                                                                                                   | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF- 359 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.53"]<br>Test: cda:manufacturedMaterial/cda:code[@codeSystem='2.16.840.1.113883.1.11.20.8']                                                                             | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF- 364 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.53"]<br>Test: not (count(cda:manufacturedMaterial/cda:name)=1)                                                                                                         | OPTIONAL: INFO message if constraint is not satisfied          |
+
+**Table B-4-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCCD/BV-000**
+
+| TI        | Validation type       | Constraint                                                                                                                                                                                                                            | Qualifier                                                      |
+|-----------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|
+| CONF- 365 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.53"]<br>Test: not (count(cda:manufacturerOrganization)=1)                                                                                                                  | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF- 366 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.53"]<br>Test: not (cda:id)                                                                                                                                                 | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF- 359 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.53"]<br>Test: not (cda:manufacturedMaterial/cda:code[@codeSystem="2.16.840.1.113883.1.11.20.8"])                                                                           | OPTIONAL: INFO message if constraint is not satisfied          |
+| CONF- 138 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.44"]<br>Test: not (self::cda:observation)                                                                                                                                  | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF- 138 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.44"]<br>Test: not (ancestor::*[cda:entryRelationship/@typeCode="REFR"])                                                                                                    | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF- 138 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.44"]<br>Test: not (@classCode='OBS')                                                                                                                                       | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF- 138 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.44"]<br>Test: not (@moodCode='EVN')                                                                                                                                        | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF- 138 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.44"]<br>Test: not (count(cda:code)=1)                                                                                                                                      | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF- 138 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.44"]<br>Test: not (cda:code[@code='33999-4'][@codeSystem="2.16.840.1.113883.6.1"])                                                                                         | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF- 138 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.44"]<br>Test: not (count(cda:statusCode)=1)                                                                                                                                | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF- 138 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.44"]<br>Test: not (cda:statusCode[@code='completed'])                                                                                                                      | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF- 138 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.44"]<br>Test: not (count(cda:value[@xsi:type='CE'])=1)                                                                                                                     | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF- 138 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.44"]<br>Test: not (cda:value/@codeSystem="2.16.840.1.113883.1.11.20.5")                                                                                                    | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-449  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.52"]<br>Test: not (self::cda:participantRole)                                                                                                                              | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-450  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.52"]<br>Test: not (@classCode='MANU')                                                                                                                                      | MANDATORY: FAIL if constraint is not satisfied                 |
+| CONF-451  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.52"]<br>Test: not ((cda:id and cda:scopingEntity) or not(cda:id))                                                                                                          | RECOMMENDED:<br>WARNING message if constraint is not satisfied |
+| CONF-448  | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.29"]<br>Test: not ((self::cda:act   self::cda:observation   self::cda:procedure) and cda:participant[@typeCode="DEV"]/cda:templateId/@root="2.16.840.1.113883.10.20.1.52") | OPTIONAL: INFO message if constraint is not satisfied          |
+
+**Table B-4-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCCD/BV-000**
+
+| TI       | Validation type       | Constraint                                                                                                                                                                                                                          | Qualifier                                                |
+|----------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|
+| CONF-448 | Schematron validation | context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.29"]<br>Test: (self::cda:act   self::cda:observation   self::cda:procedure) and<br>cda:participant[@typeCode="DEV"]/cda:templateId[@root="2.16.840.1.113883.10.20.1.52"] | OPTIONAL: INFO message if<br>constraint is not satisfied |
+| CONF-282 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.54"]<br>Test: not (self::cda:observation)                                                                                                                                | MANDATORY: FAIL if<br>constraint is not satisfied        |
+| CONF-283 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.54"]<br>Test: not (@classCode='OBS')                                                                                                                                     | MANDATORY: FAIL if<br>constraint is not satisfied        |
+| CONF-284 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.54"]<br>Test: not (@moodCode='EVN')                                                                                                                                      | MANDATORY: FAIL if<br>constraint is not satisfied        |
+| CONF-285 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.54"]<br>Test: not (count(cda:statusCode)=1)                                                                                                                              | MANDATORY: FAIL if<br>constraint is not satisfied        |
+| CONF-286 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.54"]<br>Test: not (cda:statusCode[@code='completed'] or not(cda:statusCode))                                                                                             | MANDATORY: FAIL if<br>constraint is not satisfied        |
+| CONF-287 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.55"]<br>Test: not (self::cda:observation)                                                                                                                                | MANDATORY: FAIL if<br>constraint is not satisfied        |
+| CONF-289 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.55"]<br>Test: not (@classCode='OBS')                                                                                                                                     | MANDATORY: FAIL if<br>constraint is not satisfied        |
+| CONF-290 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.55"]<br>Test: not (@moodCode='EVN')                                                                                                                                      | MANDATORY: FAIL if<br>constraint is not satisfied        |
+| CONF-291 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.55"]<br>Test: not (count(cda:statusCode)=1)                                                                                                                              | MANDATORY: FAIL if<br>constraint is not satisfied        |
+| CONF-292 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.55"]<br>Test: not (cda:statusCode[@code='completed'] or not(cda:statusCode))                                                                                             | MANDATORY: FAIL if<br>constraint is not satisfied        |
+| CONF-293 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.55"]<br>Test: not (count(cda:code)=1)                                                                                                                                    | MANDATORY: FAIL if<br>constraint is not satisfied        |
+| CONF-294 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.55"]<br>Test: not (cda:code[@code="SEV"][@codeSystem="2.16.840.1.113883.10.20.1.54"] or not(cda:code))                                                                   | MANDATORY: FAIL if<br>constraint is not satisfied        |
+| CONF-295 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.55"]<br>Test: not (count(cda:value)=1)                                                                                                                                   | MANDATORY: FAIL if<br>constraint is not satisfied        |
+| CONF-348 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.54"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.55"]<br>Test: not (count(cda:observation/cda:templateId[@root="2.16.840.1.113883.10.20.1.55"]) < 2 )              | MANDATORY: FAIL if<br>constraint is not satisfied        |
+| CONF-288 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.54"]/*[cda:templateId/@root="2.16.840.1.113883.10.20.1.55"]<br>Test: not (ancestor::*[cda:entryRelationship/@typeCode='SUBJ'])                                           | MANDATORY: FAIL if<br>constraint is not satisfied        |
+| CONF-225 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.38"]<br>Test: not (self::cda:observation)                                                                                                                                | MANDATORY: FAIL if<br>constraint is not satisfied        |
+| CONF-226 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.38"]<br>Test: not (@classCode='OBS')                                                                                                                                     | MANDATORY: FAIL if<br>constraint is not satisfied        |
+
+**Table B-4-2 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/CCCD/BV-000**
+
+| TI       | Validation type       | Constraint                                                                                                                                        | Qualifier                                      |
+|----------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| CONF-227 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.38 "]<br>Test: not (@moodCode='EVN')                                                   | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-228 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.38 "]<br>Test: not (cda:code[@code='397659008'][@codeSystem='2.16.840.1.113883.6.96']) | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-229 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.38 "]<br>Test: not (count(cda:statusCode)=1)                                           | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-230 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.38 "]<br>Test: not (cda:statusCode[@code='completed'] or not(cda:statusCode))          | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-231 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.38 "]<br>Test: not (count(cda:value)=1)                                                | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-287 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.55"]<br>Test: not (self::cda:observation)                                              | MANDATORY: FAIL if constraint is not satisfied |
+| CONF-289 | Schematron validation | Context: *[cda:templateId/@root="2.16.840.1.113883.10.20.1.55"]<br>Test: not (@classCode='OBS')                                                   | MANDATORY: FAIL if constraint is not satisfied |
+
+#### **B.4.3 For TP/HIS/SEN/AM/BV-000**
+
+**Table B-4-3 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/AM/BV-000**
+
+| TI       | Validation type       | Constraint                                                                                                                                                                                                  | Qualifier                                      |
+|----------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| GenMDG-1 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not ( routeCode[@codeSystem='2.16.840.1.113883.5.112'])                                                                               | MANDATORY: FAIL if constraint is not satisfied |
+| GenMDG-2 | Schematron validation | Context: structureBody<br>Test: not (( templateId/ @root="2.16.840.1.113883.10.20.1.8") and ( templateId/ @root="2.16.840.1.113883.10.20.1.16") and not( templateId/ @root="2.16.840.1.113883.10.20.1.14")) | MANDATORY: FAIL if constraint is not satisfied |
+| GenMDG-3 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.8"]<br>Test: not ( substanceAdministration)                                                                                                         | MANDATORY: FAIL if constraint is not satisfied |
+| GenMDG-4 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.8"]<br>Test: not ( substanceAdministration[@moodCode='EVN'])                                                                                        | MANDATORY: FAIL if constraint is not satisfied |
+| GenMDG-5 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.8"]<br>Test: not ( substanceAdministration/ consumable)                                                                                             | MANDATORY: FAIL if constraint is not satisfied |
+
+**Table B-4-3 – Testable item mapping validation between PHMR and metadata for TP/HIS/SEN/AM/BV-000**
+
+| TI       | Validation type       | Constraint                                                                                                                                                                          | Qualifier                                             |
+|----------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|
+| GenMDG-6 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.8"]<br>Test: not ( substanceAdministration/ code)                                                                           | MANDATORY: FAIL if constraint is not satisfied        |
+| GenMDG-7 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.8"]<br>Test: not (( entryRelationship/ observation/ code[@type]) and ( entryRelationship/ observation/ value[@value]))      | OPTIONAL: INFO message if constraint is not satisfied |
+| GenMDG-7 | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.8"]<br>Test: not ( participant[@typeCode='SBJ'])                                                                            | MANDATORY: FAIL if constraint is not satisfied        |
+| MMG-1    | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (( substanceAdministration/ effectiveTime))                                                               | MANDATORY: FAIL if constraint is not satisfied        |
+| MMG-1    | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (( substanceAdministration/ doseQuantity))                                                                | MANDATORY: FAIL if constraint is not satisfied        |
+| MMG-1    | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (( substanceAdministration/ consumable))                                                                  | MANDATORY: FAIL if constraint is not satisfied        |
+| MMG-1    | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (( substanceAdministration/ routeCode))                                                                   | MANDATORY: FAIL if constraint is not satisfied        |
+| MMG-2    | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (( substanceAdministration[@routeCode='2.16.840.1.113883.5.112'])))                                       | MANDATORY: FAIL if constraint is not satisfied        |
+| MMG-3    | Schematron validation | Context: substanceAdministration<br>Test: not (( substanceAdministration[@classCode='SBADM']))                                                                                      | MANDATORY: FAIL if constraint is not satisfied        |
+| MMG-3    | Schematron validation | Context: substanceAdministration<br>Test: not (( substanceAdministration[@moodCode='INT']))                                                                                         | MANDATORY: FAIL if constraint is not satisfied        |
+| MMG-5    | Schematron validation | Context: *[ templateId/@root="2.16.840.1.113883.10.20.1.24"]<br>Test: not (( observation[@code='2.16.840.1.113883.6.1' or '2.16.840.1.113883.6.96' or '2.16.840.1.113883.6.254']))) | MANDATORY: FAIL if constraint is not satisfied        |
+
+#### **B.4.4 For TP/SEN/HIS/DSG/BV-000**
+
+**Table B-4-4 – Testable item mapping validation between PHMR and metadata for TP/SEN/HIS/DSG/BV-000**
+
+| TI            | Validation type       | Constraint                                                                                                            | Qualifier                                      |
+|---------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| DSG_Content_3 | Schematron validation | Context: ds:Canonicalization<br>Test: not (@Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments") | MANDATORY: FAIL if constraint is not satisfied |
+
+**Table B-4-4 – Testable item mapping validation between PHMR and metadata for TP/SEN/HIS/DSG/BV-000**
+
+| TI             | Validation type       | Constraint                                                                                            | Qualifier                                      |
+|----------------|-----------------------|-------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| DSG_Content_4  | Schematron validation | Context: ds:SignatureMethod<br>Test: not (@Algorithm= http://www.w3.org/2001/04/xmlenc#sha256)        | MANDATORY: FAIL if constraint is not satisfied |
+| DSG_Content_5  | Schematron validation | Context: ds:DigestMethod<br>Test: not (http://www.w3.org/2001/04/xmlenc#sha256 )                      | MANDATORY: FAIL if constraint is not satisfied |
+| DSG_Content_6  | Schematron validation | Context: ds:SignedInfo/ds:Reference<br>Test: not (@URI='#IHEManifest')                                | MANDATORY: FAIL if constraint is not satisfied |
+| DSG_Content_7  | Schematron validation | Context: ds:SignedInfo/ds:Reference<br>Test: not (@Type='http://www.w3.org/2000/09/xmldsig#Manifest') | MANDATORY: FAIL if constraint is not satisfied |
+| DSG_Content_8  | Schematron validation | Context: ds:Signature<br>Test: not (ds:KeyInfo/ds:X509Data/ds:X509Certificate)                        | MANDATORY: FAIL if constraint is not satisfied |
+| DSG_Content_9  | Schematron validation | Context: ds:KeyInfo/ds:X509Data<br>Test: not (ds:X509Certificate!=")                                  | MANDATORY: FAIL if constraint is not satisfied |
+| DSG_Content_10 | Schematron validation | Context: ds:Object<br>Test: not (xad:QualifyingProperties )                                           | MANDATORY: FAIL if constraint is not satisfied |
+| DSGContent_11  | Schematron validation | Context: xad:SignedSignatureProperties<br>Test: not (xad:SigningTime )                                | MANDATORY: FAIL if constraint is not satisfied |
+| DSGContent_12  | Schematron validation | Context: xad:QualifyingProperties<br>Test: not (xad:SigningCertificate )                              | MANDATORY: FAIL if constraint is not satisfied |
+| DSGContent_13  | Schematron validation | Context: xad:SignedSignatureProperties<br>Test: not (xad:SignaturePolicyIdentifier )                  | MANDATORY: FAIL if constraint is not satisfied |
+| DSGContent_14  | Schematron validation | Context: ds:Object<br>Test: not (ds:SignatureProperties )                                             | MANDATORY: FAIL if constraint is not satisfied |
+| DSGContent_15  | Schematron validation | Context: ds:SignatureProperties<br>Test: not (xad:SignatureProperty )                                 | MANDATORY: FAIL if constraint is not satisfied |
+| DSGContent_16  | Schematron validation | Context: ds:SignatureProperty<br>Test: not (@Id='purposeOfSignature' )                                | MANDATORY: FAIL if constraint is not satisfied |
+| DSGContent_17  | Schematron validation | Context: ds:Object<br>Test: not (ds:Manifest )                                                        | MANDATORY: FAIL if constraint is not satisfied |
+| DSGContent_18  | Schematron validation | Context: ds:Manifest<br>Test: not (@Id='IHEManifest' )                                                | MANDATORY: FAIL if constraint is not satisfied |
+| DSGContent_19  | Schematron validation | Context: ds:Manifest/ds:Reference<br>Test: not (@URI )                                                | MANDATORY: FAIL if constraint is not satisfied |
+
+**Table B-4-4 – Testable item mapping validation between PHMR and metadata for TP/SEN/HIS/DSG/BV-000**
+
+| TI            | Validation type       | Constraint                                                                                                                                             | Qualifier                                      |
+|---------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| DSGContent_20 | Schematron validation | Context: ds:Manifest/ds:Reference/ds:Transforms/ds:Transform<br>Test: not (@Algorithm='http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments' ) | MANDATORY: FAIL if constraint is not satisfied |
+
+### B.5 Schema for RFC 3881 verification
+
+NOTE – This schema is based on the one found in clause 6 of [IETF RFC 3881].
+
+```
+<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
+  elementFormDefault="qualified" attributeFormDefault="unqualified">
+  <xs:element name="AuditMessage">
+    <xs:complexType>
+      <xs:sequence>
+        <xs:element name="EventIdentification"
+          type="EventIdentificationType" />
+        <xs:element name="ActiveParticipant"
+          maxOccurs="unbounded">
+          <xs:complexType>
+            <xs:complexContent>
+              <xs:extension base="ActiveParticipantType" />
+            </xs:complexContent>
+          </xs:complexType>
+        </xs:element>
+        <xs:element name="AuditSourceIdentification"
+          type="AuditSourceIdentificationType"
+          maxOccurs="unbounded" />
+        <xs:element name="ParticipantObjectIdentification"
+          type="ParticipantObjectIdentificationType" minOccurs="0"
+          maxOccurs="unbounded" />
+      </xs:sequence>
+    </xs:complexType>
+  </xs:element>
+  <xs:complexType name="EventIdentificationType">
+    <xs:sequence>
+      <xs:element name="EventID" type="CodedValueType" />
+      <xs:element name="EventTypeCode" type="CodedValueType"
+        minOccurs="0" maxOccurs="unbounded" />
+    </xs:sequence>
+    <xs:attribute name="EventActionCode" use="optional">
+      <xs:simpleType>
+        <xs:restriction base="xs:string">
+          <xs:enumeration value="C">
+            <xs:annotation>
+              <xs:appinfo>Create</xs:appinfo>
+            </xs:annotation>
+          </xs:enumeration>
+          <xs:enumeration value="R">
+            <xs:annotation>
+              <xs:appinfo>Read</xs:appinfo>
+            </xs:annotation>
+          </xs:enumeration>
+          <xs:enumeration value="U">
+            <xs:annotation>
+              <xs:appinfo>Update</xs:appinfo>
+            </xs:annotation>
+          </xs:enumeration>
+          <xs:enumeration value="D">
+            <xs:annotation>
+              <xs:appinfo>Delete</xs:appinfo>
+            </xs:annotation>
+          </xs:enumeration>
+          <xs:enumeration value="E">
+            <xs:annotation>
+              <xs:documentation>Execute</xs:documentation>
+            </xs:annotation>
+          </xs:enumeration>
+        </xs:restriction>
+      </xs:simpleType>
+    </xs:attribute>
+  </xs:complexType>
+</xs:schema>
+```
+
+```
+
+        </xs:simpleType>
+      </xs:attribute>
+      <xs:attribute name="EventDateTime" type="xs:dateTime"
+        use="required" />
+      <xs:attribute name="EventOutcomeIndicator" use="required">
+        <xs:simpleType>
+          <xs:restriction base="xs:integer">
+            <xs:enumeration value="0">
+              <xs:annotation>
+                <xs:appinfo>Success</xs:appinfo>
+              </xs:annotation>
+            </xs:enumeration>
+            <xs:enumeration value="4">
+              <xs:annotation>
+                <xs:appinfo>Minor failure</xs:appinfo>
+              </xs:annotation>
+            </xs:enumeration>
+            <xs:enumeration value="8">
+              <xs:annotation>
+                <xs:appinfo>Serious failure</xs:appinfo>
+              </xs:annotation>
+            </xs:enumeration>
+            <xs:enumeration value="12">
+              <xs:annotation>
+                <xs:appinfo>
+                  Major failure; action made unavailable
+                </xs:appinfo>
+              </xs:annotation>
+            </xs:enumeration>
+          </xs:restriction>
+        </xs:simpleType>
+      </xs:attribute>
+    </xs:complexType>
+    <xs:complexType name="AuditSourceIdentificationType">
+      <xs:sequence>
+        <xs:element name="AuditSourceTypeCode" type="CodedValueType"
+          minOccurs="0" maxOccurs="unbounded" />
+      </xs:sequence>
+      <xs:attribute name="AuditEnterpriseSiteID" type="xs:string"
+        use="optional" />
+      <xs:attribute name="AuditSourceID" type="xs:string"
+        use="required" />
+    </xs:complexType>
+    <xs:complexType name="ActiveParticipantType">
+      <xs:sequence minOccurs="0">
+        <xs:element name="RoleIDCode" type="CodedValueType"
+          minOccurs="0" maxOccurs="unbounded" />
+      </xs:sequence>
+      <xs:attribute name="UserID" type="xs:string" use="required" />
+      <xs:attribute name="AlternativeUserID" type="xs:string"
+        use="optional" />
+      <xs:attribute name="UserName" type="xs:string" use="optional" />
+      <xs:attribute name="UserIsRequestor" type="xs:boolean"
+        use="optional" default="true" />
+      <xs:attribute name="NetworkAccessPointID" type="xs:string"
+        use="optional" />
+      <xs:attribute name="NetworkAccessPointTypeCode"
+        use="optional">
+        <xs:simpleType>
+          <xs:restriction base="xs:unsignedByte">
+            <xs:enumeration value="1">
+              <xs:annotation>
+                <xs:appinfo>
+                  Machine Name, including DNS name
+                </xs:appinfo>
+              </xs:annotation>
+            </xs:enumeration>
+          </xs:restriction>
+        </xs:simpleType>
+      </xs:attribute>
+    </xs:complexType>
+
+```
+
+```
+
+                    </xs:appinfo>
+                </xs:annotation>
+            </xs:enumeration>
+            <xs:enumeration value="2">
+                <xs:annotation>
+                    <xs:appinfo>IP Address</xs:appinfo>
+                </xs:annotation>
+            </xs:enumeration>
+            <xs:enumeration value="3">
+                <xs:annotation>
+                    <xs:appinfo>Telephone Number</xs:appinfo>
+                </xs:annotation>
+            </xs:enumeration>
+        </xs:restriction>
+    </xs:simpleType>
+</xs:attribute>
+</xs:complexType>
+<xs:complexType name="ParticipantObjectIdentificationType">
+    <xs:sequence>
+        <xs:element name="ParticipantObjectIDTypeCode"
+            type="CodedValueType" />
+        <xs:choice minOccurs="0">
+            <xs:element name="ParticipantObjectName"
+                type="xs:string" minOccurs="0" />
+            <xs:element name="ParticipantObjectQuery"
+                type="xs:base64Binary" minOccurs="0" />
+        </xs:choice>
+        <xs:element name="ParticipantObjectDetail"
+            type="TypeValuePairType" minOccurs="0" maxOccurs="unbounded"
+        />
+    </xs:sequence>
+    <xs:attribute name="ParticipantObjectID" type="xs:string"
+        use="required" />
+    <xs:attribute name="ParticipantObjectTypeCode" use="optional">
+        <xs:simpleType>
+            <xs:restriction base="xs:unsignedByte">
+                <xs:enumeration value="1">
+                    <xs:annotation>
+                        <xs:appinfo>Person</xs:appinfo>
+                    </xs:annotation>
+                </xs:enumeration>
+                <xs:enumeration value="2">
+                    <xs:annotation>
+                        <xs:appinfo>System object</xs:appinfo>
+                    </xs:annotation>
+                </xs:enumeration>
+                <xs:enumeration value="3">
+                    <xs:annotation>
+                        <xs:appinfo>Organization</xs:appinfo>
+                    </xs:annotation>
+                </xs:enumeration>
+                <xs:enumeration value="4">
+                    <xs:annotation>
+                        <xs:appinfo>Other</xs:appinfo>
+                    </xs:annotation>
+                </xs:enumeration>
+            </xs:restriction>
+        </xs:simpleType>
+    </xs:attribute>
+    <xs:attribute name="ParticipantObjectTypeCodeRole"
+        use="optional">
+        <xs:simpleType>
+            <xs:restriction base="xs:unsignedByte">
+                <xs:enumeration value="1">
+
+```
+
+```
+
+        <xs:annotation>
+          <xs:appinfo>Patient</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="2">
+        <xs:annotation>
+          <xs:appinfo>Location</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="3">
+        <xs:annotation>
+          <xs:appinfo>Report</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="4">
+        <xs:annotation>
+          <xs:appinfo>Resource</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="5">
+        <xs:annotation>
+          <xs:appinfo>Master file</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="6">
+        <xs:annotation>
+          <xs:appinfo>User</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="7">
+        <xs:annotation>
+          <xs:appinfo>List</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="8">
+        <xs:annotation>
+          <xs:appinfo>Doctor</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="9">
+        <xs:annotation>
+          <xs:appinfo>Subscriber</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="10">
+        <xs:annotation>
+          <xs:appinfo>Guarantor</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="11">
+        <xs:annotation>
+          <xs:appinfo>
+            Security User Entity
+          </xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="12">
+        <xs:annotation>
+          <xs:appinfo>Security User Group</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="13">
+        <xs:annotation>
+          <xs:appinfo>Security Resource</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+
+```
+
+```
+
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="14">
+        <xs:annotation>
+          <xs:appinfo>
+            Security Granularity Definition
+          </xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="15">
+        <xs:annotation>
+          <xs:appinfo>Provider</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="16">
+        <xs:annotation>
+          <xs:appinfo>Report Destination</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="17">
+        <xs:annotation>
+          <xs:appinfo>Report Library</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="18">
+        <xs:annotation>
+          <xs:appinfo>Schedule</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="19">
+        <xs:annotation>
+          <xs:appinfo>Customer</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="20">
+        <xs:annotation>
+          <xs:appinfo>Job</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="21">
+        <xs:annotation>
+          <xs:appinfo>Job Stream</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="22">
+        <xs:annotation>
+          <xs:appinfo>Table</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="23">
+        <xs:annotation>
+          <xs:appinfo>Routing Criteria</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+      <xs:enumeration value="24">
+        <xs:annotation>
+          <xs:appinfo>Query</xs:appinfo>
+        </xs:annotation>
+      </xs:enumeration>
+    </xs:restriction>
+  </xs:simpleType>
+</xs:attribute>
+<xs:attribute name="ParticipantObjectDataLifeCycle"
+  use="optional">
+
+```
+
+```
+
+<xs:simpleType>
+  <xs:restriction base="xs:unsignedByte">
+    <xs:enumeration value="1">
+      <xs:annotation>
+        <xs:appinfo>
+          Origination / Creation
+        </xs:appinfo>
+      </xs:annotation>
+    </xs:enumeration>
+    <xs:enumeration value="2">
+      <xs:annotation>
+        <xs:appinfo>
+          Import / Copy from original
+        </xs:appinfo>
+      </xs:annotation>
+    </xs:enumeration>
+    <xs:enumeration value="3">
+      <xs:annotation>
+        <xs:appinfo>Amendment</xs:appinfo>
+      </xs:annotation>
+    </xs:enumeration>
+    <xs:enumeration value="4">
+      <xs:annotation>
+        <xs:appinfo>Verification</xs:appinfo>
+      </xs:annotation>
+    </xs:enumeration>
+    <xs:enumeration value="5">
+      <xs:annotation>
+        <xs:appinfo>Translation</xs:appinfo>
+      </xs:annotation>
+    </xs:enumeration>
+    <xs:enumeration value="6">
+      <xs:annotation>
+        <xs:appinfo>Access / Use</xs:appinfo>
+      </xs:annotation>
+    </xs:enumeration>
+    <xs:enumeration value="7">
+      <xs:annotation>
+        <xs:appinfo>De-identification</xs:appinfo>
+      </xs:annotation>
+    </xs:enumeration>
+    <xs:enumeration value="8">
+      <xs:annotation>
+        <xs:appinfo>
+          Aggregation, summarization, derivation
+        </xs:appinfo>
+      </xs:annotation>
+    </xs:enumeration>
+    <xs:enumeration value="9">
+      <xs:annotation>
+        <xs:appinfo>Report</xs:appinfo>
+      </xs:annotation>
+    </xs:enumeration>
+    <xs:enumeration value="10">
+      <xs:annotation>
+        <xs:appinfo>
+          Export / Copy to target
+        </xs:appinfo>
+      </xs:annotation>
+    </xs:enumeration>
+    <xs:enumeration value="11">
+      <xs:annotation>
+        <xs:appinfo>Disclosure</xs:appinfo>
+      </xs:annotation>
+    </xs:enumeration>
+  </xs:restriction>
+</xs:simpleType>
+
+```
+
+```
+
+    </xs:enumeration>
+    <xs:enumeration value="12">
+      <xs:annotation>
+        <xs:appinfo>
+          Receipt of disclosure
+        </xs:appinfo>
+      </xs:annotation>
+    </xs:enumeration>
+    <xs:enumeration value="13">
+      <xs:annotation>
+        <xs:appinfo>Archiving</xs:appinfo>
+      </xs:annotation>
+    </xs:enumeration>
+    <xs:enumeration value="14">
+      <xs:annotation>
+        <xs:appinfo>Logical deletion</xs:appinfo>
+      </xs:annotation>
+    </xs:enumeration>
+    <xs:enumeration value="15">
+      <xs:annotation>
+        <xs:appinfo>
+          Permanent erasure / Physical destruction
+        </xs:appinfo>
+      </xs:annotation>
+    </xs:enumeration>
+  </xs:restriction>
+</xs:simpleType>
+</xs:attribute>
+<xs:attribute name="ParticipantObjectSensitivity"
+  type="xs:string" use="optional" />
+</xs:complexType>
+<xs:complexType name="CodedValueType">
+  <xs:attribute name="code" type="xs:string" use="required" />
+  <xs:attributeGroup ref="CodeSystem" />
+  <xs:attribute name="displayName" type="xs:string"
+    use="optional" />
+  <xs:attribute name="originalText" type="xs:string"
+    use="optional" />
+</xs:complexType>
+<xs:complexType name="TypeValuePairType">
+  <xs:attribute name="type" type="xs:string" use="required" />
+  <xs:attribute name="value" type="xs:base64Binary"
+    use="required" />
+</xs:complexType>
+<xs:attributeGroup name="CodeSystem">
+  <xs:attribute name="codeSystem" type="OID" use="optional" />
+  <xs:attribute name="codeSystemName" type="xs:string"
+    use="optional" />
+</xs:attributeGroup>
+<xs:simpleType name="OID">
+  <xs:restriction base="xs:string">
+    <xs:whiteSpace value="collapse" />
+  </xs:restriction>
+</xs:simpleType>
+</xs:schema>
+
+```
+
+### B.6 Schema for XML advanced electronic signatures (XAdES)
+
+```
+
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema targetNamespace="http://uri.etsi.org/01903/v1.1.1#"
+  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+  xmlns="http://uri.etsi.org/01903/v1.1.1#"
+  xmlns:ds="http://www.w3.org/2000/09/xmldsig#" elementFormDefault="qualified">
+
+```
+
+```
+
+<xsd:import
+                namespace="http://www.w3.org/2000/09/xmldsig#"
+schemaLocation="xmldsig-core-schema.xsd"/>
+<!-- Start auxiliary types definitions: AnyType, ObjectIdentifierType,
+EncapsulatedPKIDataType and TimestampType-->
+
+<!-- Start AnyType -->
+
+<xsd:element name="Any" type="AnyType"/><xsd:complexType name="AnyType"
+mixed="true">
+  <xsd:sequence>
+    <xsd:any namespace="##any"/>
+  </xsd:sequence>
+  <xsd:anyAttribute namespace="##any"/>
+</xsd:complexType>
+
+<!-- End AnyType -->
+
+<!-- Start ObjectIdentifierType-->
+
+<xsd:element name="ObjectIdentifier" type="ObjectIdentifierType"/>
+<xsd:complexType name="ObjectIdentifierType">
+  <xsd:sequence>
+    <xsd:element name="Identifier" type="IdentifierType"/>
+    <xsd:element name="Description" type="xsd:string" minOccurs="0"/>
+    <xsd:element
+                name="DocumentationReferences"
+type="DocumentationReferencesType" minOccurs="0"/>
+  </xsd:sequence>
+</xsd:complexType>
+<xsd:complexType name="IdentifierType">
+  <xsd:simpleContent>
+    <xsd:extension base="xsd:anyURI">
+      <xsd:attribute name="Qualifier" type="QualifierType" use="optional"/>
+    </xsd:extension>
+  </xsd:simpleContent>
+</xsd:complexType>
+<xsd:simpleType name="QualifierType">
+  <xsd:restriction base="xsd:string">
+    <xsd:enumeration value="OIDAsURI"/>
+    <xsd:enumeration value="OIDAsURN"/>
+  </xsd:restriction>
+</xsd:simpleType>
+<xsd:complexType name="DocumentationReferencesType">
+  <xsd:sequence maxOccurs="unbounded">
+    <xsd:element name="DocumentationReference" type="xsd:anyURI"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<!-- End ObjectIdentifierType-->
+
+<!-- Start EncapsulatedPKIDataType-->
+
+<xsd:element name="EncapsulatedPKIData" type="EncapsulatedPKIDataType"/>
+<xsd:complexType name="EncapsulatedPKIDataType">
+  <xsd:simpleContent>
+    <xsd:extension base="xsd:base64Binary">
+      <xsd:attribute name="Id" type="xsd:ID" use="optional"/>
+    </xsd:extension>
+  </xsd:simpleContent>
+</xsd:complexType>
+
+<!-- End EncapsulatedPKIDataType -->
+
+<!-- Start TimestampType -->
+
+```
+
+```
+
+<xsd:element name="TimeStamp" type="TimeStampType"/>
+<xsd:complexType name="TimeStampType">
+  <xsd:sequence>
+    <xsd:element name="HashDataInfo" type="HashDataInfoType"
+maxOccurs="unbounded"/>
+    <xsd:choice>
+      <xsd:element name="EncapsulatedTimeStamp" type="EncapsulatedPKIDataType"/>
+      <xsd:element name="XMLTimeStamp" type="AnyType"/>
+    </xsd:choice>
+  </xsd:sequence>
+</xsd:complexType>
+<xsd:complexType name="HashDataInfoType">
+  <xsd:sequence>
+    <xsd:element name="Transforms" type="ds:TransformsType" minOccurs="0"/>
+  </xsd:sequence>
+  <xsd:attribute name="uri" type="xsd:anyURI" use="required"/>
+</xsd:complexType>
+
+<!-- End TimeStampType -->
+
+<!-- End auxiliary types definitions-->
+
+<!-- Start container types -->
+
+<!-- Start QualifyingProperties -->
+
+<xsd:element name="QualifyingProperties" type="QualifyingPropertiesType"/>
+<xsd:complexType name="QualifyingPropertiesType">
+  <xsd:sequence>
+    <xsd:element name="SignedProperties" type="SignedPropertiesType"
+minOccurs="0"/>
+    <xsd:element name="UnsignedProperties" type="UnsignedPropertiesType"
+minOccurs="0"/>
+  </xsd:sequence>
+  <xsd:attribute name="Target" type="xsd:anyURI" use="required"/>
+  <xsd:attribute name="Id" type="xsd:ID" use="optional"/>
+</xsd:complexType>
+
+<!-- End QualifyingProperties -->
+
+<!-- Start SignedProperties-->
+
+<xsd:element name="SignedProperties" type="SignedPropertiesType"/>
+<xsd:complexType name="SignedPropertiesType">
+  <xsd:sequence>
+    <xsd:element name="SignedSignatureProperties"
+type="SignedSignaturePropertiesType"/>
+    <xsd:element name="SignedDataObjectProperties"
+type="SignedDataObjectPropertiesType" minOccurs="0"/>
+  </xsd:sequence>
+  <xsd:attribute name="Id" type="xsd:ID" use="optional"/>
+</xsd:complexType>
+
+<!-- End SignedProperties-->
+
+<!-- Start UnsignedProperties-->
+
+<xsd:element name="UnsignedProperties" type="UnsignedPropertiesType" />
+<xsd:complexType name="UnsignedPropertiesType">
+  <xsd:sequence>
+    <xsd:element name="UnsignedSignatureProperties"
+type="UnsignedSignaturePropertiesType" minOccurs="0"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+```
+
+```
+
+    <xsd:element
+      name="UnsignedDataObjectProperties"
+      type="UnsignedDataObjectPropertiesType" minOccurs="0"/>
+  </xsd:sequence>
+  <xsd:attribute name="Id" type="xsd:ID" use="optional"/>
+</xsd:complexType>
+
+<!-- End UnsignedProperties-->
+
+<!-- Start SignedSignatureProperties-->
+
+<xsd:element
+      name="SignedSignatureProperties"
+      type="SignedSignaturePropertiesType" />
+<xsd:complexType name="SignedSignaturePropertiesType">
+  <xsd:sequence>
+    <xsd:element name="SigningTime" type="xsd:dateTime"/>
+    <xsd:element name="SigningCertificate" type="CertIDListType"/>
+    <xsd:element
+      name="SignaturePolicyIdentifier"
+      type="SignaturePolicyIdentifierType"/>
+    <xsd:element
+      name="SignatureProductionPlace"
+      type="SignatureProductionPlaceType" minOccurs="0"/>
+    <xsd:element name="SignerRole" type="SignerRoleType" minOccurs="0"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<!-- End SignedSignatureProperties-->
+
+<!-- Start SignedDataObjectProperties-->
+
+<xsd:element
+      name="SignedDataObjectProperties"
+      type="SignedDataObjectPropertiesType"/>
+<xsd:complexType name="SignedDataObjectPropertiesType">
+  <xsd:sequence>
+    <xsd:element
+      name="DataObjectFormat"
+      type="DataObjectFormatType"
+      minOccurs="0" maxOccurs="unbounded"/>
+    <xsd:element
+      name="CommitmentTypeIndication"
+      type="CommitmentTypeIndicationType" minOccurs="0" maxOccurs="unbounded"/>
+    <xsd:element
+      name="AllDataObjectsTimeStamp"
+      type="TimeStampType"
+      minOccurs="0" maxOccurs="unbounded"/>
+    <xsd:element
+      name="IndividualDataObjectsTimeStamp"
+      type="TimeStampType"
+      minOccurs="0" maxOccurs="unbounded"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<!-- End SignedDataObjectProperties-->
+
+<!-- Start UnsignedSignatureProperties-->
+
+<xsd:element
+      name="UnsignedSignatureProperties"
+      type="UnsignedSignaturePropertiesType"/>
+<xsd:complexType name="UnsignedSignaturePropertiesType">
+  <xsd:sequence>
+    <xsd:element
+      name="CounterSignature"
+      type="CounterSignatureType"
+      minOccurs="0" maxOccurs="unbounded"/>
+    <xsd:element
+      name="SignatureTimeStamp"
+      type="TimeStampType"
+      minOccurs="0"
+      maxOccurs="unbounded"/>
+    <xsd:element
+      name="CompleteCertificateRefs"
+      type="CompleteCertificateRefsType" minOccurs="0"/>
+    <xsd:element
+      name="CompleteRevocationRefs"
+      type="CompleteRevocationRefsType"
+      minOccurs="0"/>
+    <xsd:choice>
+      <xsd:element name="SigAndRefsTimeStamp" type="TimeStampType" minOccurs="0"
+        maxOccurs="unbounded"/>
+      <xsd:element name="RefsOnlyTimeStamp" type="TimeStampType" minOccurs="0"
+        maxOccurs="unbounded"/>
+    </xsd:choice>
+  </xsd:sequence>
+</xsd:complexType>
+
+```
+
+```
+
+    </xsd:choice>
+    <xsd:element name="CertificateValues" type="CertificateValuesType"
+minOccurs="0"/>
+    <xsd:element name="RevocationValues" type="RevocationValuesType"
+minOccurs="0"/>
+    <xsd:element name="ArchiveTimeStamp" type="TimeStampType" minOccurs="0"
+maxOccurs="unbounded"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<!-- End UnsignedSignatureProperties-->
+
+<!-- Start UnsignedDataObjectProperties-->
+
+<xsd:element name="UnsignedDataObjectProperties"
+type="UnsignedDataObjectPropertiesType" />
+<xsd:complexType name="UnsignedDataObjectPropertiesType">
+  <xsd:sequence>
+    <xsd:element name="UnsignedDataObjectProperty" type="AnyType" minOccurs="0"
+maxOccurs="unbounded"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<!-- End UnsignedDataObjectProperties-->
+
+<!-- Start QualifyingPropertiesReference-->
+
+<xsd:element name="QualifyingPropertiesReference"
+type="QualifyingPropertiesReferenceType"/>
+<xsd:complexType name="QualifyingPropertiesReferenceType">
+  <xsd:sequence>
+    <xsd:element name="Transforms" type="ds:TransformsType" minOccurs="0"/>
+  </xsd:sequence>
+  <xsd:attribute name="URI" type="xsd:anyURI" use="required"/>
+  <xsd:attribute name="Id" type="xsd:ID" use="optional"/>
+</xsd:complexType>
+
+<!-- End QualifyingPropertiesReference-->
+
+<!-- End container types -->
+
+<!-- Start SigningTime element -->
+
+<xsd:element name="SigningTime" type="xsd:dateTime"/>
+
+<!-- End SigningTime element -->
+
+<!-- Start SigningCertificate -->
+
+<xsd:element name="SigningCertificate" type="CertIDListType"/>
+<xsd:complexType name="CertIDListType">
+  <xsd:sequence>
+    <xsd:element name="Cert" type="CertIDType" maxOccurs="unbounded"/>
+  </xsd:sequence>
+</xsd:complexType>
+<xsd:complexType name="CertIDType">
+  <xsd:sequence>
+    <xsd:element name="CertDigest" type="DigestAlgAndValueType"/>
+    <xsd:element name="IssuerSerial" type="ds:X509IssuerSerialType"/>
+  </xsd:sequence>
+</xsd:complexType>
+<xsd:complexType name="DigestAlgAndValueType">
+  <xsd:sequence>
+    <xsd:element name="DigestMethod" type="ds:DigestMethodType"/>
+
+```
+
+```
+
+    <xsd:element name="DigestValue" type="ds:DigestValueType"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<!-- End SigningCertificate -->
+
+<!-- Start SignaturePolicyIdentifier -->
+
+<xsd:element
+                                name="SignaturePolicyIdentifier"
+type="SignaturePolicyIdentifierType"/>
+<xsd:complexType name="SignaturePolicyIdentifierType">
+  <xsd:choice>
+    <xsd:element name="SignaturePolicyId" type="SignaturePolicyIdType"/>
+    <xsd:element name="SignaturePolicyImplied"/>
+  </xsd:choice>
+</xsd:complexType>
+<xsd:complexType name="SignaturePolicyIdType">
+  <xsd:sequence>
+    <xsd:element name="SigPolicyId" type="ObjectIdentifierType"/>
+    <xsd:element ref="ds:Transforms" minOccurs="0"/>
+    <xsd:element name="SigPolicyHash" type="DigestAlgAndValueType"/>
+    <xsd:element name="SigPolicyQualifiers" type="SigPolicyQualifiersListType"
+minOccurs="0"/>
+  </xsd:sequence>
+</xsd:complexType>
+<xsd:complexType name="SigPolicyQualifiersListType">
+  <xsd:sequence>
+    <xsd:element
+                                name="SigPolicyQualifier"
+                                type="AnyType"
+maxOccurs="unbounded"/>
+  </xsd:sequence>
+</xsd:complexType>
+<xsd:element name="SPURI" type="xsd:anyURI"/>
+<xsd:element name="SPUserNotice" type="SPUserNoticeType"/>
+<xsd:complexType name="SPUserNoticeType">
+  <xsd:sequence>
+    <xsd:element name="NoticeRef" type="NoticeReferenceType" minOccurs="0"/>
+    <xsd:element name="ExplicitText" type="xsd:string" minOccurs="0"/>
+  </xsd:sequence>
+</xsd:complexType>
+<xsd:complexType name="NoticeReferenceType">
+  <xsd:sequence>
+    <xsd:element name="Organization" type="xsd:string"/>
+    <xsd:element name="NoticeNumbers" type="IntegerListType"/>
+  </xsd:sequence>
+</xsd:complexType>
+<xsd:complexType name="IntegerListType">
+  <xsd:sequence>
+    <xsd:element
+                                name="int"
+                                type="xsd:integer"
+                                minOccurs="0"
+maxOccurs="unbounded"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<!-- End SignaturePolicyIdentifier -->
+
+<!-- Start CounterSignature -->
+
+<xsd:element name="CounterSignature" type="CounterSignatureType"/>
+<xsd:complexType name="CounterSignatureType">
+  <xsd:sequence>
+    <xsd:element ref="ds:Signature"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+```
+
+```
+
+<!-- End CounterSignature -->
+
+<!-- Start DataObjectFormat -->
+
+<xsd:element name="DataObjectFormat" type="DataObjectFormatType"/>
+<xsd:complexType name="DataObjectFormatType">
+  <xsd:sequence>
+    <xsd:element name="Description" type="xsd:string" minOccurs="0"/>
+    <xsd:element name="ObjectIdentifier" type="ObjectIdentifierType"
+      minOccurs="0"/>
+    <xsd:element name="MimeType" type="xsd:string" minOccurs="0"/>
+    <xsd:element name="Encoding" type="xsd:anyURI" minOccurs="0"/>
+  </xsd:sequence>
+  <xsd:attribute name="ObjectReference" type="xsd:anyURI" use="required"/>
+</xsd:complexType>
+
+<!-- End DataObjectFormat -->
+
+<!-- Start CommitmentTypeIndication -->
+
+<xsd:element name="CommitmentTypeIndication"
+  type="CommitmentTypeIndicationType"/>
+<xsd:complexType name="CommitmentTypeIndicationType">
+  <xsd:sequence>
+    <xsd:element name="CommitmentTypeId" type="ObjectIdentifierType"/>
+    <xsd:choice>
+      <xsd:element name="ObjectReference" type="xsd:anyURI" minOccurs="0"
+        maxOccurs="unbounded"/>
+      <xsd:element name="AllSignedDataObjects"/>
+    </xsd:choice>
+    <xsd:element name="CommitmentTypeQualifiers"
+      type="CommitmentTypeQualifiersListType" minOccurs="0"/>
+  </xsd:sequence>
+</xsd:complexType>
+<xsd:complexType name="CommitmentTypeQualifiersListType">
+  <xsd:sequence>
+    <xsd:element name="CommitmentTypeQualifier" type="AnyType" minOccurs="0"
+      maxOccurs="unbounded"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<!-- End CommitmentTypeIndication -->
+
+<!-- Start SignatureProductionPlace -->
+
+<xsd:element name="SignatureProductionPlace"
+  type="SignatureProductionPlaceType"/>
+<xsd:complexType name="SignatureProductionPlaceType">
+  <xsd:sequence>
+    <xsd:element name="City" type="xsd:string" minOccurs="0"/>
+    <xsd:element name="StateOrProvince" type="xsd:string" minOccurs="0"/>
+    <xsd:element name="PostalCode" type="xsd:string" minOccurs="0"/>
+    <xsd:element name="CountryName" type="xsd:string" minOccurs="0"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<!-- End SignatureProductionPlace -->
+
+<!-- Start SignerRole -->
+
+<xsd:element name="SignerRole" type="SignerRoleType"/>
+<xsd:complexType name="SignerRoleType">
+  <xsd:sequence>
+    <xsd:element name="ClaimedRoles" type="ClaimedRolesListType"
+
+```
+
+```
+
+    minOccurs="0"/>
+    <xsd:element name="CertifiedRoles" type="CertifiedRolesListType"
+      minOccurs="0"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<xsd:complexType name="ClaimedRolesListType">
+  <xsd:sequence>
+    <xsd:element name="ClaimedRole" type="AnyType" maxOccurs="unbounded"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<xsd:complexType name="CertifiedRolesListType">
+  <xsd:sequence>
+    <xsd:element name="CertifiedRole" type="EncapsulatedPKIDataType"
+      maxOccurs="unbounded"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<!-- End SignerRole -->
+
+<xsd:element name="AllDataObjectsTimeStamp" type="TimeStampType"/>
+
+<xsd:element name="IndividualDataObjectsTimeStamp" type="TimeStampType"/>
+
+<xsd:element name="SignatureTimeStamp" type="TimeStampType"/>
+
+<!-- Start CompleteCertificateRefs -->
+
+<xsd:element name="CompleteCertificateRefs" type="CompleteCertificateRefsType"/>
+
+<xsd:complexType name="CompleteCertificateRefsType">
+  <xsd:sequence>
+    <xsd:element name="CertRefs" type="CertIDListType" />
+  </xsd:sequence>
+  <xsd:attribute name="Id" type="xsd:ID" use="optional"/>
+</xsd:complexType>
+
+<!-- End CompleteCertificateRefs -->
+
+<!-- Start CompleteRevocationRefs-->
+
+<xsd:element name="CompleteRevocationRefs" type="CompleteRevocationRefsType"/>
+
+<xsd:complexType name="CompleteRevocationRefsType">
+  <xsd:sequence>
+    <xsd:element name="CRLRefs" type="CRLRefsType" minOccurs="0"/>
+    <xsd:element name="OCSPRefs" type="OCSPRefsType" minOccurs="0"/>
+    <xsd:element name="OtherRefs" type="OtherCertStatusRefsType" minOccurs="0"/>
+  </xsd:sequence>
+  <xsd:attribute name="Id" type="xsd:ID" use="optional"/>
+</xsd:complexType>
+
+<xsd:complexType name="CRLRefsType">
+  <xsd:sequence>
+    <xsd:element name="CRLRef" type="CRLRefType" maxOccurs="unbounded"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<xsd:complexType name="CRLRefType">
+  <xsd:sequence>
+    <xsd:element name="DigestAlgAndValue" type="DigestAlgAndValueType"/>
+
+```
+
+```
+
+    <xsd:element name="CRLIdentifier" type="CRLIdentifierType" minOccurs="0"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<xsd:complexType name="CRLIdentifierType">
+  <xsd:sequence>
+    <xsd:element name="Issuer" type="xsd:string"/>
+    <xsd:element name="IssueTime" type="xsd:dateTime" />
+    <xsd:element name="Number" type="xsd:integer" minOccurs="0"/>
+  </xsd:sequence>
+  <xsd:attribute name="URI" type="xsd:anyURI" use="optional"/>
+</xsd:complexType>
+
+<xsd:complexType name="OCSPRefsType">
+  <xsd:sequence>
+    <xsd:element name="OCSPRef" type="OCSPRefType" maxOccurs="unbounded"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<xsd:complexType name="OCSPRefType">
+  <xsd:sequence>
+    <xsd:element name="OCSPIdentifier" type="OCSPIdentifierType"/>
+    <xsd:element name="DigestAlgAndValue" type="DigestAlgAndValueType"
+      minOccurs="0"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<xsd:complexType name="OCSPIdentifierType">
+  <xsd:sequence>
+    <xsd:element name="ResponderID" type="xsd:string"/>
+    <xsd:element name="ProducedAt" type="xsd:dateTime"/>
+  </xsd:sequence>
+  <xsd:attribute name="URI" type="xsd:anyURI" use="optional"/>
+</xsd:complexType>
+
+<xsd:complexType name="OtherCertStatusRefsType">
+  <xsd:sequence>
+    <xsd:element name="OtherRef" type="AnyType" maxOccurs="unbounded"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<!-- End CompleteRevocationRefs-->
+
+<xsd:element name="SigAndRefsTimeStamp" type="TimeStampType"/>
+
+<xsd:element name="RefsOnlyTimeStamp" type="TimeStampType"/>
+
+<!-- Start CertificateValues -->
+
+<xsd:element name="CertificateValues" type="CertificateValuesType"/>
+
+<xsd:complexType name="CertificateValuesType">
+  <xsd:choice minOccurs="0" maxOccurs="unbounded">
+    <xsd:element name="EncapsulatedX509Certificate" type="EncapsulatedPKIDataType"/>
+    <xsd:element name="OtherCertificate" type="AnyType"/>
+  </xsd:choice>
+  <xsd:attribute name="Id" type="xsd:ID" use="optional"/>
+</xsd:complexType>
+
+<!-- End CertificateValues -->
+
+<!-- Start RevocationValues-->
+
+```
+
+```
+<xsd:element name="RevocationValues" type="RevocationValuesType"/>
+
+<xsd:complexType name="RevocationValuesType">
+  <xsd:sequence>
+    <xsd:element name="CRLValues" type="CRLValuesType" minOccurs="0"/>
+    <xsd:element name="OCSPValues" type="OCSPValuesType" minOccurs="0"/>
+    <xsd:element name="OtherValues"                type="OtherCertStatusValuesType"
+minOccurs="0"/>
+  </xsd:sequence>
+  <xsd:attribute name="Id" type="xsd:ID" use="optional"/>
+</xsd:complexType>
+
+<xsd:complexType name="CRLValuesType">
+  <xsd:sequence>
+    <xsd:element name="EncapsulatedCRLValue" type="EncapsulatedPKIDataType"
+        maxOccurs="unbounded"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<xsd:complexType name="OCSPValuesType">
+  <xsd:sequence>
+    <xsd:element name="EncapsulatedOCSPValue"
+        type="EncapsulatedPKIDataType" maxOccurs="unbounded"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<xsd:complexType name="OtherCertStatusValuesType">
+  <xsd:sequence>
+    <xsd:element name="OtherValue" type="AnyType" maxOccurs="unbounded"/>
+  </xsd:sequence>
+</xsd:complexType>
+
+<!-- End RevocationValues-->
+
+<xsd:element name="ArchiveTimeStamp" type="TimeStampType"/>
+
+</xsd:schema>
+```
+
+### B.7 Schema for XML-signature syntax and processing (Xmldsig)
+
+```
+<?xml version="1.0" encoding="utf-8"?>
+
+<!-- Schema for XML Signatures
+    http://www.w3.org/2000/09/xmldsig#
+    $Revision: 1.1 $ on $Date: 2002/02/08 20:32:26 $ by $Author: reagle $
+
+    Copyright 2001 The Internet Society and W3C (Massachusetts Institute
+    of Technology, Institut National de Recherche en Informatique et en
+    Automatique, Keio University). All Rights Reserved.
+    http://www.w3.org/Consortium/Legal/
+
+    This document is governed by the W3C Software License [1] as described
+    in the FAQ [2].
+
+    [1] http://www.w3.org/Consortium/Legal/copyright-software-19980720
+    [2] http://www.w3.org/Consortium/Legal/IPR-FAQ-20000620.html#DTD
+-->
+```
+
+```
+<schema xmlns="http://www.w3.org/2001/XMLSchema"
+    xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
+    targetNamespace="http://www.w3.org/2000/09/xmldsig#"
+    version="0.1" elementFormDefault="qualified">
+```
+
+```
+
+<!-- Basic Types Defined for Signatures -->
+
+<simpleType name="CryptoBinary">
+  <restriction base="base64Binary">
+    </restriction>
+  </simpleType>
+
+<!-- Start Signature -->
+
+<element name="Signature" type="ds:SignatureType"/>
+<complexType name="SignatureType">
+  <sequence>
+    <element ref="ds:SignedInfo"/>
+    <element ref="ds:SignatureValue"/>
+    <element ref="ds:KeyInfo" minOccurs="0"/>
+    <element ref="ds:Object" minOccurs="0" maxOccurs="unbounded"/>
+  </sequence>
+  <attribute name="Id" type="ID" use="optional"/>
+</complexType>
+
+<element name="SignatureValue" type="ds:SignatureValueType"/>
+<complexType name="SignatureValueType">
+  <simpleContent>
+    <extension base="base64Binary">
+      <attribute name="Id" type="ID" use="optional"/>
+    </extension>
+  </simpleContent>
+</complexType>
+
+<!-- Start SignedInfo -->
+
+<element name="SignedInfo" type="ds:SignedInfoType"/>
+<complexType name="SignedInfoType">
+  <sequence>
+    <element ref="ds:CanonicalizationMethod"/>
+    <element ref="ds:SignatureMethod"/>
+    <element ref="ds:Reference" maxOccurs="unbounded"/>
+  </sequence>
+  <attribute name="Id" type="ID" use="optional"/>
+</complexType>
+
+<element name="CanonicalizationMethod" type="ds:CanonicalizationMethodType"/>
+<complexType name="CanonicalizationMethodType" mixed="true">
+  <sequence>
+    <any namespace="##any" minOccurs="0" maxOccurs="unbounded"/>
+    <!-- (0,unbounded) elements from (1,1) namespace -->
+  </sequence>
+  <attribute name="Algorithm" type="anyURI" use="required"/>
+</complexType>
+
+<element name="SignatureMethod" type="ds:SignatureMethodType"/>
+<complexType name="SignatureMethodType" mixed="true">
+  <sequence>
+    <element name="HMACOutputLength" type="ds:HMACOutputLengthType" minOccurs="0"/>
+    <any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
+    <!-- (0,unbounded) elements from (1,1) external namespace -->
+  </sequence>
+  <attribute name="Algorithm" type="anyURI" use="required"/>
+</complexType>
+
+<!-- Start Reference -->
+
+<element name="Reference" type="ds:ReferenceType"/>
+
+```
+
+```
+
+<complexType name="ReferenceType">
+  <sequence>
+    <element ref="ds:Transforms" minOccurs="0"/>
+    <element ref="ds:DigestMethod"/>
+    <element ref="ds:DigestValue"/>
+  </sequence>
+  <attribute name="Id" type="ID" use="optional"/>
+  <attribute name="URI" type="anyURI" use="optional"/>
+  <attribute name="Type" type="anyURI" use="optional"/>
+</complexType>
+
+<element name="Transforms" type="ds:TransformsType"/>
+<complexType name="TransformsType">
+  <sequence>
+    <element ref="ds:Transform" maxOccurs="unbounded"/>
+  </sequence>
+</complexType>
+
+<element name="Transform" type="ds:TransformType"/>
+<complexType name="TransformType" mixed="true">
+  <choice minOccurs="0" maxOccurs="unbounded">
+    <any namespace="##other" processContents="lax"/>
+    <!-- (1,1) elements from (0,unbounded) namespaces -->
+    <element name="XPath" type="string"/>
+  </choice>
+  <attribute name="Algorithm" type="anyURI" use="required"/>
+</complexType>
+
+<!-- End Reference -->
+
+<element name="DigestMethod" type="ds:DigestMethodType"/>
+<complexType name="DigestMethodType" mixed="true">
+  <sequence>
+    <any namespace="##other" processContents="lax" minOccurs="0"
+maxOccurs="unbounded"/>
+  </sequence>
+  <attribute name="Algorithm" type="anyURI" use="required"/>
+</complexType>
+
+<element name="DigestValue" type="ds:DigestValueType"/>
+<simpleType name="DigestValueType">
+  <restriction base="base64Binary"/>
+</simpleType>
+
+<!-- End SignedInfo -->
+
+<!-- Start KeyInfo -->
+
+<element name="KeyInfo" type="ds:KeyInfoType"/>
+<complexType name="KeyInfoType" mixed="true">
+  <choice maxOccurs="unbounded">
+    <element ref="ds:KeyName"/>
+    <element ref="ds:KeyValue"/>
+    <element ref="ds:RetrievalMethod"/>
+    <element ref="ds:X509Data"/>
+    <element ref="ds:PGPData"/>
+    <element ref="ds:SPKIData"/>
+    <element ref="ds:MgmtData"/>
+    <any processContents="lax" namespace="##other"/>
+    <!-- (1,1) elements from (0,unbounded) namespaces -->
+  </choice>
+  <attribute name="Id" type="ID" use="optional"/>
+</complexType>
+
+```
+
+```
+
+<element name="KeyName" type="string"/>
+<element name="MgmtData" type="string"/>
+
+<element name="KeyValue" type="ds:KeyValueTypa"/>
+<complexType name="KeyValueTypa" mixed="true">
+  <choice>
+    <element ref="ds:DSAKeyValue"/>
+    <element ref="ds:RSAKeyValue"/>
+    <any namespace="##other" processContents="lax"/>
+  </choice>
+</complexType>
+
+<element name="RetrievalMethod" type="ds:RetrievalMethodTypa"/>
+<complexType name="RetrievalMethodTypa">
+  <sequence>
+    <element ref="ds:Transforms" minOccurs="0"/>
+  </sequence>
+  <attribute name="URI" type="anyURI"/>
+  <attribute name="Type" type="anyURI" use="optional"/>
+</complexType>
+
+<!-- Start X509Data -->
+
+<element name="X509Data" type="ds:X509DataType"/>
+<complexType name="X509DataType">
+  <sequence maxOccurs="unbounded">
+    <choice>
+      <element name="X509IssuerSerial" type="ds:X509IssuerSerialTypa"/>
+      <element name="X509SKI" type="base64Binary"/>
+      <element name="X509SubjectName" type="string"/>
+      <element name="X509Certificate" type="base64Binary"/>
+      <element name="X509CRL" type="base64Binary"/>
+      <any namespace="##other" processContents="lax"/>
+    </choice>
+  </sequence>
+</complexType>
+
+<complexType name="X509IssuerSerialTypa">
+  <sequence>
+    <element name="X509IssuerName" type="string"/>
+    <element name="X509SerialNumber" type="integer"/>
+  </sequence>
+</complexType>
+
+<!-- End X509Data -->
+
+<!-- Begin PGPData -->
+
+<element name="PGPData" type="ds:PGPDataType"/>
+<complexType name="PGPDataType">
+  <choice>
+    <sequence>
+      <element name="PGPKeyID" type="base64Binary"/>
+      <element name="PGPKeyPacket" type="base64Binary" minOccurs="0"/>
+      <any namespace="##other" processContents="lax" minOccurs="0"
+        maxOccurs="unbounded"/>
+    </sequence>
+    <sequence>
+      <element name="PGPKeyPacket" type="base64Binary"/>
+      <any namespace="##other" processContents="lax" minOccurs="0"
+        maxOccurs="unbounded"/>
+    </sequence>
+  </choice>
+</complexType>
+
+```
+
+```
+
+<!-- End PGPData -->
+
+<!-- Begin SPKIData -->
+
+<element name="SPKIData" type="ds:SPKIDataType"/>
+<complexType name="SPKIDataType">
+  <sequence maxOccurs="unbounded">
+    <element name="SPKISexp" type="base64Binary"/>
+    <any namespace="##other" processContents="lax" minOccurs="0"/>
+  </sequence>
+</complexType>
+
+<!-- End SPKIData -->
+
+<!-- End KeyInfo -->
+
+<!-- Start Object (Manifest, SignatureProperty) -->
+
+<element name="Object" type="ds:ObjectType"/>
+<complexType name="ObjectType" mixed="true">
+  <sequence minOccurs="0" maxOccurs="unbounded">
+    <any namespace="##any" processContents="lax"/>
+  </sequence>
+  <attribute name="Id" type="ID" use="optional"/>
+  <attribute name="MimeType" type="string" use="optional"/> <!-- add a grep
+facet -->
+  <attribute name="Encoding" type="anyURI" use="optional"/>
+</complexType>
+
+<element name="Manifest" type="ds:ManifestType"/>
+<complexType name="ManifestType">
+  <sequence>
+    <element ref="ds:Reference" maxOccurs="unbounded"/>
+  </sequence>
+  <attribute name="Id" type="ID" use="optional"/>
+</complexType>
+
+<element name="SignatureProperties" type="ds:SignaturePropertiesType"/>
+<complexType name="SignaturePropertiesType">
+  <sequence>
+    <element ref="ds:SignatureProperty" maxOccurs="unbounded"/>
+  </sequence>
+  <attribute name="Id" type="ID" use="optional"/>
+</complexType>
+
+<element name="SignatureProperty" type="ds:SignaturePropertyType"/>
+<complexType name="SignaturePropertyType" mixed="true">
+  <choice maxOccurs="unbounded">
+    <any namespace="##other" processContents="lax"/>
+    <!-- (1,1) elements from (1,unbounded) namespaces -->
+  </choice>
+  <attribute name="Target" type="anyURI" use="required"/>
+  <attribute name="Id" type="ID" use="optional"/>
+</complexType>
+
+<!-- End Object (Manifest, SignatureProperty) -->
+
+<!-- Start Algorithm Parameters -->
+
+<simpleType name="HMACOutputLengthType">
+  <restriction base="integer"/>
+</simpleType>
+
+```
+
+```
+
+<!-- Start KeyValue Element-types -->
+
+<element name="DSAKeyValue" type="ds:DSAKeyValue"/>
+<complexType name="DSAKeyValue">
+  <sequence>
+    <sequence minOccurs="0">
+      <element name="P" type="ds:CryptoBinary"/>
+      <element name="Q" type="ds:CryptoBinary"/>
+    </sequence>
+    <element name="G" type="ds:CryptoBinary" minOccurs="0"/>
+    <element name="Y" type="ds:CryptoBinary"/>
+    <element name="J" type="ds:CryptoBinary" minOccurs="0"/>
+    <sequence minOccurs="0">
+      <element name="Seed" type="ds:CryptoBinary"/>
+      <element name="PgenCounter" type="ds:CryptoBinary"/>
+    </sequence>
+  </sequence>
+</complexType>
+
+<element name="RSAKeyValue" type="ds:RSAKeyValue"/>
+<complexType name="RSAKeyValue">
+  <sequence>
+    <element name="Modulus" type="ds:CryptoBinary"/>
+    <element name="Exponent" type="ds:CryptoBinary"/>
+  </sequence>
+</complexType>
+
+<!-- End KeyValue Element-types -->
+
+<!-- End Signature -->
+
+</schema>
+
+```
+
+### B.8 Testable item mapping validation between signature document and metadata
+
+**Table B-8 – Testable item mapping validation between signature document and metadata**
+
+| TI                                    | Validation<br>type                                                                     | Constraint                                                                                                                                                                                                                                                                                                                                                                | Qualifier                 |                                       |                                                |                                                                                        |                                                |
+|---------------------------------------|----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|---------------------------------------|------------------------------------------------|----------------------------------------------------------------------------------------|------------------------------------------------|
+| DSG_Content_2                         | Mapping                                                                                | The following DSG elements shall be equal to metadata elements: <table border="1" style="width: 100%;"> <thead> <tr> <th>xPath of DSG element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/ds:Signature[@Id]</td> <td>/rim:Classification/rim:Slot[@name='authorInstitution']/rim:ValueList/rim:Value/text()</td> </tr> </tbody> </table>     | xPath of DSG element      | xPath of METADATA element             | /ds:Signature[@Id]                             | /rim:Classification/rim:Slot[@name='authorInstitution']/rim:ValueList/rim:Value/text() | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of DSG element                  | xPath of METADATA element                                                              |                                                                                                                                                                                                                                                                                                                                                                           |                           |                                       |                                                |                                                                                        |                                                |
+| /ds:Signature[@Id]                    | /rim:Classification/rim:Slot[@name='authorInstitution']/rim:ValueList/rim:Value/text() |                                                                                                                                                                                                                                                                                                                                                                           |                           |                                       |                                                |                                                                                        |                                                |
+| DSGEntryAttribute_1                   | Mapping                                                                                | There are no DSG elements to be mapped in the metadata; however, if the element appears, the structure of the metadata element is checked against the following Xpath query: <table border="1" style="width: 100%;"> <thead> <tr> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>//rim:Slot[@name="authorInstitution"]</td> </tr> </tbody> </table>   | xPath of METADATA element | //rim:Slot[@name="authorInstitution"] | MANDATORY: FAIL if constraint is not satisfied |                                                                                        |                                                |
+| xPath of METADATA element             |                                                                                        |                                                                                                                                                                                                                                                                                                                                                                           |                           |                                       |                                                |                                                                                        |                                                |
+| //rim:Slot[@name="authorInstitution"] |                                                                                        |                                                                                                                                                                                                                                                                                                                                                                           |                           |                                       |                                                |                                                                                        |                                                |
+| DSGEntryAttribute_2                   | Mapping                                                                                | The following DSG elements shall be equal to metadata elements: <table border="1" style="width: 100%;"> <thead> <tr> <th>xPath of DSG element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>//xad:X509IssuerName/text()</td> <td>/rim:Classification/rim:Slot[@name='authorPerson']/rim:ValueList/rim:Value/text()</td> </tr> </tbody> </table> | xPath of DSG element      | xPath of METADATA element             | //xad:X509IssuerName/text()                    | /rim:Classification/rim:Slot[@name='authorPerson']/rim:ValueList/rim:Value/text()      | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of DSG element                  | xPath of METADATA element                                                              |                                                                                                                                                                                                                                                                                                                                                                           |                           |                                       |                                                |                                                                                        |                                                |
+| //xad:X509IssuerName/text()           | /rim:Classification/rim:Slot[@name='authorPerson']/rim:ValueList/rim:Value/text()      |                                                                                                                                                                                                                                                                                                                                                                           |                           |                                       |                                                |                                                                                        |                                                |
+| DSGEntryAttribute_3                   | Mapping                                                                                | There are no DSG elements to be mapped in the metadata; however, if the element appears the structure of the metadata element is checked against the following Xpath query : <table border="1" style="width: 100%;"> <thead> <tr> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>//rim:Slot[@name="authorRole"]</td> </tr> </tbody> </table>          | xPath of METADATA element | //rim:Slot[@name="authorRole"]        | MANDATORY: FAIL if constraint is not satisfied |                                                                                        |                                                |
+| xPath of METADATA element             |                                                                                        |                                                                                                                                                                                                                                                                                                                                                                           |                           |                                       |                                                |                                                                                        |                                                |
+| //rim:Slot[@name="authorRole"]        |                                                                                        |                                                                                                                                                                                                                                                                                                                                                                           |                           |                                       |                                                |                                                                                        |                                                |
+| DSGEntryAttribute_4                   | Mapping                                                                                | There are no DSG elements to be mapped in the metadata; however, if the element appears the structure of the metadata element is checked against the following Xpath query: <table border="1" style="width: 100%;"> <thead> <tr> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>//rim:Slot[@name="authorSpeciality"]</td> </tr> </tbody> </table>     | xPath of METADATA element | //rim:Slot[@name="authorSpeciality"]  | MANDATORY: FAIL if constraint is not satisfied |                                                                                        |                                                |
+| xPath of METADATA element             |                                                                                        |                                                                                                                                                                                                                                                                                                                                                                           |                           |                                       |                                                |                                                                                        |                                                |
+| //rim:Slot[@name="authorSpeciality"]  |                                                                                        |                                                                                                                                                                                                                                                                                                                                                                           |                           |                                       |                                                |                                                                                        |                                                |
+
+**Table B-8 – Testable item mapping validation between signature document and metadata**
+
+| TI                                                                                                                                                          | Validation type                                                                                                | Constraint                                                                                                                                                                                                                                                                                                                                                                                                                                   | Qualifier                   |                                                                                                                                                             |                                                        |                                                                                                                |                                                |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| DSGEntryAttribute_5                                                                                                                                         | Mapping                                                                                                        | <p>There are no DSG elements to be mapped in the metadata; however, if the element appears the structure of the metadata element is checked against the following Xpath query:</p> <table border="1"> <tr> <th>xPath of METADATA element</th> </tr> <tr> <td>/rim:Classification[@classificationScheme='urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4']/@nodeRepresentation/text()='urn:oid:1.3.6.1.4.1.19376.1.2.1.1.1'</td> </tr> </table> | xPath of METADATA element   | /rim:Classification[@classificationScheme='urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4']/@nodeRepresentation/text()='urn:oid:1.3.6.1.4.1.19376.1.2.1.1.1' | MANDATORY: FAIL if constraint is not satisfied         |                                                                                                                |                                                |
+| xPath of METADATA element                                                                                                                                   |                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                              |                             |                                                                                                                                                             |                                                        |                                                                                                                |                                                |
+| /rim:Classification[@classificationScheme='urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4']/@nodeRepresentation/text()='urn:oid:1.3.6.1.4.1.19376.1.2.1.1.1' |                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                              |                             |                                                                                                                                                             |                                                        |                                                                                                                |                                                |
+| DSGEntryAttribute_6                                                                                                                                         | Mapping                                                                                                        | <p>There are no DSG elements to be mapped in the metadata; however, if the element appears the structure of the metadata element is checked against the following Xpath query:</p> <table border="1"> <tr> <th>xPath of METADATA element</th> </tr> <tr> <td>/rim:Classification[@classificationScheme='urn:uuid:f4f85eac-e6cb-4883-b524-f2705394840f']/@nodeRepresentation/text()='1.2.840.10065.1.12.1.5'</td> </tr> </table>              | xPath of METADATA element   | /rim:Classification[@classificationScheme='urn:uuid:f4f85eac-e6cb-4883-b524-f2705394840f']/@nodeRepresentation/text()='1.2.840.10065.1.12.1.5'              | MANDATORY: FAIL if constraint is not satisfied         |                                                                                                                |                                                |
+| xPath of METADATA element                                                                                                                                   |                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                              |                             |                                                                                                                                                             |                                                        |                                                                                                                |                                                |
+| /rim:Classification[@classificationScheme='urn:uuid:f4f85eac-e6cb-4883-b524-f2705394840f']/@nodeRepresentation/text()='1.2.840.10065.1.12.1.5'              |                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                              |                             |                                                                                                                                                             |                                                        |                                                                                                                |                                                |
+| DSGEntryAttribute_7                                                                                                                                         | Mapping                                                                                                        | <p>The following DSG elements shall be equal to metadata elements:</p> <table border="1"> <tr> <th>xPath of DSG element</th> <th>xPath of METADATA element</th> </tr> <tr> <td>//xad:SignedSignatureProperties/xad:SigningTime/text()</td> <td>/rim:Slot[@name='creationTime']/rim:ValueList/rim:Value/text()</td> </tr> </table>                                                                                                            | xPath of DSG element        | xPath of METADATA element                                                                                                                                   | //xad:SignedSignatureProperties/xad:SigningTime/text() | /rim:Slot[@name='creationTime']/rim:ValueList/rim:Value/text()                                                 | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of DSG element                                                                                                                                        | xPath of METADATA element                                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                              |                             |                                                                                                                                                             |                                                        |                                                                                                                |                                                |
+| //xad:SignedSignatureProperties/xad:SigningTime/text()                                                                                                      | /rim:Slot[@name='creationTime']/rim:ValueList/rim:Value/text()                                                 |                                                                                                                                                                                                                                                                                                                                                                                                                                              |                             |                                                                                                                                                             |                                                        |                                                                                                                |                                                |
+| DSGEntryAttribute_8                                                                                                                                         | Mapping                                                                                                        | <p>There are no DSG elements to be mapped in the metadata; however, if the element appears the structure of the metadata element is checked against the following Xpath query:</p> <table border="1"> <tr> <th>xPath of METADATA element</th> </tr> <tr> <td>/@id</td> </tr> </table>                                                                                                                                                        | xPath of METADATA element   | /@id                                                                                                                                                        | MANDATORY: FAIL if constraint is not satisfied         |                                                                                                                |                                                |
+| xPath of METADATA element                                                                                                                                   |                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                              |                             |                                                                                                                                                             |                                                        |                                                                                                                |                                                |
+| /@id                                                                                                                                                        |                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                              |                             |                                                                                                                                                             |                                                        |                                                                                                                |                                                |
+| DSGEntryAttribute_9                                                                                                                                         | Mapping                                                                                                        | <p>The following DSG elements (if present) shall be equal to metadata elements:</p> <table border="1"> <tr> <th>xPath of PHM report element</th> <th>xPath of METADATA element</th> </tr> <tr> <td>//ds:SignatureProperty/Text()</td> <td>/rim:Classification[@classificationScheme='urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4']/@nodeRepresentation</td> </tr> </table>                                                                 | xPath of PHM report element | xPath of METADATA element                                                                                                                                   | //ds:SignatureProperty/Text()                          | /rim:Classification[@classificationScheme='urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4']/@nodeRepresentation | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of PHM report element                                                                                                                                 | xPath of METADATA element                                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                              |                             |                                                                                                                                                             |                                                        |                                                                                                                |                                                |
+| //ds:SignatureProperty/Text()                                                                                                                               | /rim:Classification[@classificationScheme='urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4']/@nodeRepresentation |                                                                                                                                                                                                                                                                                                                                                                                                                                              |                             |                                                                                                                                                             |                                                        |                                                                                                                |                                                |
+
+**Table B-8 – Testable item mapping validation between signature document and metadata**
+
+| TI                                                                                                                                                                               | Validation type | Constraint                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Qualifier                 |                                                                                                                                                                                  |                                                |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| DSGEntryAttribute_11                                                                                                                                                             | Mapping         | <p>There are no DSG elements to be mapped in the metadata; however, if the element appears the structure of the metadata element is checked against the following Xpath query:</p> <table border="1"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>/rim:Classification[@classificationScheme=urn:uuid:a09d5840-386c-46f2-b5ad-9c3699a4309d']/@nodeRepresentation /text()=http://www.w3.org/2000/09/xmldsig#</td> </tr> </table>                         | xPath of METADATA element | /rim:Classification[@classificationScheme=urn:uuid:a09d5840-386c-46f2-b5ad-9c3699a4309d']/@nodeRepresentation /text()=http://www.w3.org/2000/09/xmldsig#                         | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of METADATA element                                                                                                                                                        |                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                           |                                                                                                                                                                                  |                                                |
+| /rim:Classification[@classificationScheme=urn:uuid:a09d5840-386c-46f2-b5ad-9c3699a4309d']/@nodeRepresentation /text()=http://www.w3.org/2000/09/xmldsig#                         |                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                           |                                                                                                                                                                                  |                                                |
+| DSGEntryAttribute_12                                                                                                                                                             | Mapping         | <p>There are no DSG elements to be mapped in the metadata; however, if the element appears the structure of the metadata element is checked against the following Xpath query:</p> <table border="1"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>/rim:Slot/@name='hash'</td> </tr> </table>                                                                                                                                                           | xPath of METADATA element | /rim:Slot/@name='hash'                                                                                                                                                           | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of METADATA element                                                                                                                                                        |                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                           |                                                                                                                                                                                  |                                                |
+| /rim:Slot/@name='hash'                                                                                                                                                           |                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                           |                                                                                                                                                                                  |                                                |
+| DSGEntryAttribute_13                                                                                                                                                             | Mapping         | <p>There are no DSG elements to be mapped in the metadata; however, if the element appears the structure of the metadata element is checked against the following Xpath query:</p> <table border="1"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>@"//*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/rim:Classification[@classificationScheme='urn:uuid:f33fb8ac-18af-42cc-ae0e-ed0b0bdb91e1']"</td> </tr> </table> | xPath of METADATA element | @"//*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/rim:Classification[@classificationScheme='urn:uuid:f33fb8ac-18af-42cc-ae0e-ed0b0bdb91e1']" | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of METADATA element                                                                                                                                                        |                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                           |                                                                                                                                                                                  |                                                |
+| @"//*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/rim:Classification[@classificationScheme='urn:uuid:f33fb8ac-18af-42cc-ae0e-ed0b0bdb91e1']" |                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                           |                                                                                                                                                                                  |                                                |
+| DSGEntryAttribute_14                                                                                                                                                             | Mapping         | <p>There are no DSG elements to be mapped in the metadata; however, if the element appears the structure of the metadata element is checked against the following Xpath query:</p> <table border="1"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>/rim:Slot[@name='languageCode']/rim:ValueList/rim:Value/text()='art'</td> </tr> </table>                                                                                                             | xPath of METADATA element | /rim:Slot[@name='languageCode']/rim:ValueList/rim:Value/text()='art'                                                                                                             | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of METADATA element                                                                                                                                                        |                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                           |                                                                                                                                                                                  |                                                |
+| /rim:Slot[@name='languageCode']/rim:ValueList/rim:Value/text()='art'                                                                                                             |                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                           |                                                                                                                                                                                  |                                                |
+
+**Table B-8 – Testable item mapping validation between signature document and metadata**
+
+| TI                                                                                                                                                                               | Validation type                                                    | Constraint                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Qualifier                 |                                                                                                                                                                                  |                                                        |                                                                    |                                                |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|--------------------------------------------------------------------|------------------------------------------------|
+| DSGEntryAttribute_15                                                                                                                                                             | Mapping                                                            | <p>There are no DSG elements to be mapped in the metadata; however, if the element appears the structure of the metadata element is checked against the following Xpath query:</p> <table border="1"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>/rim:Slot[@name='legalAuthenticator']/rim:ValueList/rim:Value/text()='art'</td> </tr> </table>                                                                                                       | xPath of METADATA element | /rim:Slot[@name='legalAuthenticator']/rim:ValueList/rim:Value/text()='art'                                                                                                       | MANDATORY: FAIL if constraint is not satisfied         |                                                                    |                                                |
+| xPath of METADATA element                                                                                                                                                        |                                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                           |                                                                                                                                                                                  |                                                        |                                                                    |                                                |
+| /rim:Slot[@name='legalAuthenticator']/rim:ValueList/rim:Value/text()='art'                                                                                                       |                                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                           |                                                                                                                                                                                  |                                                        |                                                                    |                                                |
+| DSGEntryAttribute_16                                                                                                                                                             | Mapping                                                            | <p>There are no DSG elements to be mapped in the metadata; however, if the element appears the structure of the metadata element is checked against the following Xpath query:</p> <table border="1"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>/@mimeType='text/xml'</td> </tr> </table>                                                                                                                                                            | xPath of METADATA element | /@mimeType='text/xml'                                                                                                                                                            | MANDATORY: FAIL if constraint is not satisfied         |                                                                    |                                                |
+| xPath of METADATA element                                                                                                                                                        |                                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                           |                                                                                                                                                                                  |                                                        |                                                                    |                                                |
+| /@mimeType='text/xml'                                                                                                                                                            |                                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                           |                                                                                                                                                                                  |                                                        |                                                                    |                                                |
+| DSGEntryAttribute_17                                                                                                                                                             | Mapping                                                            | <p>There are no DSG elements to be mapped in the metadata; however, if the element appears the structure of the metadata element is checked against the following Xpath query:</p> <table border="1"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>/rim:ExternalIdentifier[@identificationScheme='urn:uuid:58a6f841-87b3-4a3e-92fd-a8ffe98427']/@value</td> </tr> </table>                                                                              | xPath of METADATA element | /rim:ExternalIdentifier[@identificationScheme='urn:uuid:58a6f841-87b3-4a3e-92fd-a8ffe98427']/@value                                                                              | MANDATORY: FAIL if constraint is not satisfied         |                                                                    |                                                |
+| xPath of METADATA element                                                                                                                                                        |                                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                           |                                                                                                                                                                                  |                                                        |                                                                    |                                                |
+| /rim:ExternalIdentifier[@identificationScheme='urn:uuid:58a6f841-87b3-4a3e-92fd-a8ffe98427']/@value                                                                              |                                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                           |                                                                                                                                                                                  |                                                        |                                                                    |                                                |
+| DSGEntryAttribute_18                                                                                                                                                             | Mapping                                                            | <p>There are no DSG elements to be mapped in the metadata; however, if the element appears the structure of the metadata element is checked against the following Xpath query:</p> <table border="1"> <tr> <td>xPath of METADATA element</td> </tr> <tr> <td>@"//*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/rim:Classification[@classificationScheme='urn:uuid:cccf5598-8b07-4b77-a05e-ae952c785ead']"</td> </tr> </table> | xPath of METADATA element | @"//*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/rim:Classification[@classificationScheme='urn:uuid:cccf5598-8b07-4b77-a05e-ae952c785ead']" | MANDATORY: FAIL if constraint is not satisfied         |                                                                    |                                                |
+| xPath of METADATA element                                                                                                                                                        |                                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                           |                                                                                                                                                                                  |                                                        |                                                                    |                                                |
+| @"//*[local-name()='SubmitObjectsRequest']/rim:RegistryObjectList/rim:ExtrinsicObject/rim:Classification[@classificationScheme='urn:uuid:cccf5598-8b07-4b77-a05e-ae952c785ead']" |                                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                           |                                                                                                                                                                                  |                                                        |                                                                    |                                                |
+| DSGEntryAttribute_19                                                                                                                                                             | Mapping                                                            | <p>The following DSG elements shall be equal to metadata elements</p> <table border="1"> <tr> <td>xPath of DSG element</td> <td>xPath of METADATA element</td> </tr> <tr> <td>//xad:SignedSignatureProperties/xad:SisgingTime/text()</td> <td>/rim:Slot[@name='ServiceStartTime']/rim:ValueList/rim:Value/text()</td> </tr> </table>                                                                                                                              | xPath of DSG element      | xPath of METADATA element                                                                                                                                                        | //xad:SignedSignatureProperties/xad:SisgingTime/text() | /rim:Slot[@name='ServiceStartTime']/rim:ValueList/rim:Value/text() | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of DSG element                                                                                                                                                             | xPath of METADATA element                                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                           |                                                                                                                                                                                  |                                                        |                                                                    |                                                |
+| //xad:SignedSignatureProperties/xad:SisgingTime/text()                                                                                                                           | /rim:Slot[@name='ServiceStartTime']/rim:ValueList/rim:Value/text() |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                           |                                                                                                                                                                                  |                                                        |                                                                    |                                                |
+
+**Table B-8 – Testable item mapping validation between signature document and metadata**
+
+| TI                                                                                                                           | Validation<br>type                                                | Constraint                                                                                                                                                                                                                                                                                                                                                                                                                                  | Qualifier                   |                                                                                                                              |                                                         |                                                                   |                                                |
+|------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|-------------------------------------------------------------------|------------------------------------------------|
+| DSGEntryAttribute_20                                                                                                         | Mapping                                                           | The following DSG elements shall be equal to metadata elements<br><table border="1"> <thead> <tr> <th>xPath of DSG element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>//xad:SignedSignatureProperties/xad:SisgingTime/text()</td> <td>/rim:Slot[@name='ServiceStopTime']/rim:ValueList/rim:Value/text()</td> </tr> </tbody> </table>                                                                           | xPath of DSG element        | xPath of METADATA element                                                                                                    | //xad:SignedSignatureProperties/xad:SisgingTime/text()  | /rim:Slot[@name='ServiceStopTime']/rim:ValueList/rim:Value/text() | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of DSG element                                                                                                         | xPath of METADATA element                                         |                                                                                                                                                                                                                                                                                                                                                                                                                                             |                             |                                                                                                                              |                                                         |                                                                   |                                                |
+| //xad:SignedSignatureProperties/xad:SisgingTime/text()                                                                       | /rim:Slot[@name='ServiceStopTime']/rim:ValueList/rim:Value/text() |                                                                                                                                                                                                                                                                                                                                                                                                                                             |                             |                                                                                                                              |                                                         |                                                                   |                                                |
+| DSGEntryAttribute_21                                                                                                         | Mapping                                                           | There are no DSG elements to be mapped in the metadata; however, if the element appears the structure of the metadata element is checked against the following Xpath query:<br><table border="1"> <thead> <tr> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/rim:Slot[@name='sourcePatientId']</td> </tr> </tbody> </table>                                                                                           | xPath of METADATA element   | /rim:Slot[@name='sourcePatientId']                                                                                           | MANDATORY: FAIL if constraint is not satisfied          |                                                                   |                                                |
+| xPath of METADATA element                                                                                                    |                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                             |                             |                                                                                                                              |                                                         |                                                                   |                                                |
+| /rim:Slot[@name='sourcePatientId']                                                                                           |                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                             |                             |                                                                                                                              |                                                         |                                                                   |                                                |
+| DSGEntryAttribute_22                                                                                                         | Mapping                                                           | There are no DSG elements to be mapped in the metadata; however, if the element appears the structure of the metadata element is checked against the following Xpath query:<br><table border="1"> <thead> <tr> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/rim:Slot[@name='sourcePatientInfo']</td> </tr> </tbody> </table>                                                                                         | xPath of METADATA element   | /rim:Slot[@name='sourcePatientInfo']                                                                                         | MANDATORY: FAIL if constraint is not satisfied          |                                                                   |                                                |
+| xPath of METADATA element                                                                                                    |                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                             |                             |                                                                                                                              |                                                         |                                                                   |                                                |
+| /rim:Slot[@name='sourcePatientInfo']                                                                                         |                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                             |                             |                                                                                                                              |                                                         |                                                                   |                                                |
+| DSGEntryAttribute_23                                                                                                         | Mapping                                                           | The following DSG Report elements (if present) shall be equal to metadata elements:<br><table border="1"> <thead> <tr> <th>xPath of DSG Report element</th> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/ds:SignatureProperty/[@Id='purposeofSignature']/text()</td> <td>/rim:Name/rim:LocalizedString/@value</td> </tr> </tbody> </table>                                                                           | xPath of DSG Report element | xPath of METADATA element                                                                                                    | /ds:SignatureProperty/[@Id='purposeofSignature']/text() | /rim:Name/rim:LocalizedString/@value                              | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of DSG Report element                                                                                                  | xPath of METADATA element                                         |                                                                                                                                                                                                                                                                                                                                                                                                                                             |                             |                                                                                                                              |                                                         |                                                                   |                                                |
+| /ds:SignatureProperty/[@Id='purposeofSignature']/text()                                                                      | /rim:Name/rim:LocalizedString/@value                              |                                                                                                                                                                                                                                                                                                                                                                                                                                             |                             |                                                                                                                              |                                                         |                                                                   |                                                |
+| DSGEntryAttribute_24                                                                                                         | Mapping                                                           | There are no DSG elements to be mapped in the metadata; however, if the element appears the structure of the metadata element is checked against the following Xpath query:<br><table border="1"> <thead> <tr> <th>xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td>/rim:Classification[@classificationScheme='urn:uuid:f0306f51-975f-434e-a61c-c59651d33983']/rim:Name/rim:Value/@value='E1762'</td> </tr> </tbody> </table> | xPath of METADATA element   | /rim:Classification[@classificationScheme='urn:uuid:f0306f51-975f-434e-a61c-c59651d33983']/rim:Name/rim:Value/@value='E1762' | MANDATORY: FAIL if constraint is not satisfied          |                                                                   |                                                |
+| xPath of METADATA element                                                                                                    |                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                             |                             |                                                                                                                              |                                                         |                                                                   |                                                |
+| /rim:Classification[@classificationScheme='urn:uuid:f0306f51-975f-434e-a61c-c59651d33983']/rim:Name/rim:Value/@value='E1762' |                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                             |                             |                                                                                                                              |                                                         |                                                                   |                                                |
+
+**Table B-8 – Testable item mapping validation between signature document and metadata**
+
+| TI                                                     | Validation type                      | Constraint                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Qualifier                   |                           |                                                        |                                      |                                                |
+|--------------------------------------------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|---------------------------|--------------------------------------------------------|--------------------------------------|------------------------------------------------|
+| DSGEntryAttribute_25                                   | Mapping                              | <p>There are no DSG elements to be mapped in the metadata; however, if the element appears the structure of the metadata element is checked against the following Xpath query:</p> <table border="1" data-bbox="582 418 1653 491"> <thead> <tr> <th data-bbox="582 418 1102 454">xPath of DSG Report element</th> <th data-bbox="1102 418 1653 454">xPath of METADATA element</th> </tr> </thead> <tbody> <tr> <td data-bbox="582 454 1102 491">/ds:SignatureProperty[@Id='purposeofSignature']/text()</td> <td data-bbox="1102 454 1653 491">/rim:Name/rim:LocalizedString/@value</td> </tr> </tbody> </table> | xPath of DSG Report element | xPath of METADATA element | /ds:SignatureProperty[@Id='purposeofSignature']/text() | /rim:Name/rim:LocalizedString/@value | MANDATORY: FAIL if constraint is not satisfied |
+| xPath of DSG Report element                            | xPath of METADATA element            |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                             |                           |                                                        |                                      |                                                |
+| /ds:SignatureProperty[@Id='purposeofSignature']/text() | /rim:Name/rim:LocalizedString/@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-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-ISO/IEC 19757-3] ISO/IEC 19757-3:2016, *Information technology – Document Schema Definition Languages (DSDL) – Part 3: Rule-based validation – Schematron*.
+- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003-12), *ETSI drafting rules*.  
+<https://docbox.etsi.org/MTS/MTS/10-PromotionalMaterial/MBS-20111118/Referenced%20Documents/Drafting%20Rules.pdf>
+- [b-HIS Sender PICS & PIXIT] HIS Sender DG2016 *PICS and PIXIT excel sheet v1.7*.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-SOAP 1.2] W3C SOAP 1.2 (2007), *SOAP Version 1.2 (Second Edition)*.  
+<http://www.w3.org/TR/soap/>
+
+
+
+
+
+# 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.1-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.830.1-201704-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..eb9be23c436fee93dad09bbf341c03d44660eb68
--- /dev/null
+++ b/marked/H/T-REC-H.830.1-201704-I_PDF-E/raw.md
@@ -0,0 +1,1099 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.830.1**
+
+(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 1: Web services  
+interoperability: Health & Fitness Service sender**
+
+Recommendation ITU-T H.830.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        |
+| 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        |
+| <b>Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN)</b> | <b>H.820–H.859</b> |
+| 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.1
+
+## Conformance of ITU-T H.810 personal health system: Services interface Part 1: Web services interoperability: Health & Fitness Service sender
+
+## Summary
+
+Recommendation ITU-T H.830.1 provides a test suite structure (TSS) and the test purposes (TP) for Web services interoperability for 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.1 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Services Interface; Part 1: Web Services Interoperability. HFS Sender (Version 1.6, 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.831    | 2015-01-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/12249">11.1002/1000/12249</a> |
+| 1.0     | ITU-T H.830.1  | 2015-01-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/12587">11.1002/1000/12587</a> |
+| 2.0     | ITU-T H.830.1  | 2016-07-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12921">11.1002/1000/12921</a> |
+| 3.0     | ITU-T H.830.1  | 2017-04-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/13201">11.1002/1000/13201</a> |
+
+## Keywords
+
+Conformance testing, Continua Design Guidelines, e-health, Health & Fitness Service sender, ITU-T H.810, personal connected health devices, Services interface, Web services interoperability.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.1.1 – Basic profile (BP) .....          | 9  |
+| A.3     | Subgroup 1.1.2 – Basic security profile (BSP)..... | 14 |
+| A.4     | Subgroup 1.1.3 – Reliable messaging (RM) .....     | 23 |
+|         | 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 Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Services Interface; Part 1: Web Services Interoperability. HFS Sender (Version 1.6, 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. It is the same version as "TSS&TP_1.5_WAN_PART_1_(SEN WS-I)_v1.2.doc" because new features included in [b-CDG 2011] do not affect the test procedures specified in this document.                                                         |
+| 1.2     | 2013-05-24 | Initial release for Test Tool DG2012. It is the same version as "TSS&TP_DG2011_WAN_PART_1_(SEN WS-I)_v1.2.doc" because new features included in [b-CDG 2012] do not affect the test procedures specified in this document.                                                      |
+| 1.2     | 2014-01-24 | Initial release for Test Tool DG2013. It is the same version as "TSS&TP_DG2012_WAN_PART_1_(SEN WS-I)_v1.2.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.3     | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_WAN_PART_1_(SEN WS-I)_v1.2.doc" as baseline and it adds new features included in Documentation Enhancements: <ul style="list-style-type: none"> <li>"Other PICS" row added</li> </ul> |
+| 1.4     | 2015-07-01 | Initial release for Test Tool DG2015: <ul style="list-style-type: none"> <li>Test suite structure modified.</li> <li>Applicability modified due to the inclusion of hData OU.</li> </ul>                                                                                        |
+| 1.5     | 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.6     | 2017-03-14 | Editorial: added insulin pump and continuous glucose monitor specializations to the TSS list in clause 6.                                                                                                                                                                       |
+
+## Recommendation ITU-T H.830.1
+
+## Conformance of ITU-T H.810 personal health system: Services interface Part 1: Web services interoperability: Health & Fitness Service sender
+
+# 1 Scope
+
+The scope of this Recommendation<sup>1</sup> is to provide a test suite structure (TSS) and the test purposes (TP) for the Services interface based on the requirements defined in 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 1.
+
+- **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*.
+
+---
+
+<sup>1</sup> 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.*  
+<http://www.ws-i.org/Profiles/BasicProfile-1.1.html>
+- [OASIS/WS-I BSP] OASIS/WS-I (2007), *Basic Security Profile Version 1.0.*  
+<http://www.ws-i.org/Profiles/BasicSecurityProfile-1.0.html>
+- [OASIS WS-I RM] OASIS (2007), *Web Services Reliable Messaging (WS-Reliable Messaging) Version 1.1.*  
+<http://docs.oasis-open.org/ws-rx/wsm/200702/wsm-1.1-spec-cs-01.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          |
+| ATS  | Abstract Test Suite                 |
+| ATNA | Audit Trail and Node Authentication |
+| CDG  | Continua Design Guidelines          |
+| CGM  | Continuous Glucose Monitor          |
+| DUT  | Device Under Test                   |
+| EPR  | Endpoint Reference                  |
+| 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                                   |
+| 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                         |
+| STR   | Security Token Reference                              |
+| TCRL  | Test Case Reference List                              |
+| TCWG  | Test and Certification Working Group                  |
+| TLS   | Transport Level Security                              |
+| TP    | Test Purpose                                          |
+| URI   | Uniform Resource Identifier                           |
+| 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 subgroup 1.1 (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 <http://handle.itu.int/11.1002/2000/12067>.
+
+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>/<DUT>/<GR>/<SGR>/<XX> – <NNN>). It is specified according to the naming convention defined below:
+  - Each test purpose identifier is introduced by the prefix "TP".
+  - <TT>: This is the test tool that will be used in the test case.
+    - HFS: Health & Fitness Services Interface
+  - <DUT>: This is the device under test.
+    - SEN: HFS sender
+    - REC: HFS receiver
+  - <GR>: This identifies a group of test cases.
+  - <SGR>: This identifies a subgroup of test cases.
+  - <XX>: This identifies the type of testing.
+    - BV: Valid behaviour test
+    - BI: Invalid behaviour test
+  - <NNN>: 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 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 – Basic profile (BP)
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                 |                            |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----------------------------|
+| <b>TP Id</b>              | TP/HFS/SEN/WSI/BP/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                 |                            |
+| <b>TP label</b>           | SOAP Envelope Structure                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                 |                            |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [OASIS/WS-I BP] |                            |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | BP-R9980; M     | BP-R9981; M                |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | BP-R1008; M     | BP-R1009; M                |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | BP-R1032; M     | BP-R1014; M<br>BP-R1033; R |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>An Envelope must conform to the structure specified in SOAP1.2 Section 5.1, "SOAP Envelope"</p> <p>[AND]</p> <p>an Envelope must have exactly zero or one child elements of the soap:Body element</p> <p>[AND]</p> <p>the children of the soap:body element in an Envelope must be namespace qualified</p> <p>[AND]</p> <p>An Envelope must not contain a Document Type Declaration (DTD) or Processing Instructions</p> <p>[AND]</p> <p>an Envelope should not contain the namespace declaration<br/>xmlns:xml="http://www.w3.org/XML/1998/namespace"</p> <p>[AND]</p> <p>the soap:envelope, soap:header and soap:body elements must not have attributes in the namespace "http://schemas.xmlsoap.org/soap/envelope/"</p> |                 |                            |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                 |                            |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                 |                            |
+| <b>Initial condition</b>  | <p>The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respective service according to its needs.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                 |                            |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The HFS sender under test sends the SOAP message to the HFS receiver.</li> <li>Check that the captured message has the following structure:           <pre>&lt;soap:Envelope 'namespace'&gt;   &lt;soap:Header&gt;     ...   &lt;/soap:Header&gt;   &lt;soap:Body&gt;     <i>Here are the children of soap:Envelope</i>   &lt;/soap:Body&gt; &lt;/soap:Envelope&gt;</pre> <p>where soap:Header is optional and it is recommended that the namespace is not http://www.w3.org/XML/1998/namespace.</p> </li> </ol>                                                                                                                                                                                          |                 |                            |
+| <b>Pass/Fail criteria</b> | <p>Check that:</p> <ul style="list-style-type: none"> <li>The message has, in this order, an envelope, an optional header and a body.</li> <li>The namespaces that appear in the soap message are qualified.</li> <li>Soap:envelope, soap:header and soap:body do not have attributes in the namespace "http://schemas.xmlsoap.org/soap/envelope/".</li> <li>There is no DTD or processing instructions in the envelope.</li> <li>The SOAP envelope's namespace is "http://www.w3.org/2003/05/soap-envelope" to</li> </ul>                                                                                                                                                                                                                       |                 |                            |
+
+|              |                                                                                                                                                                                                   |
+|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|              | support SOAP 1.2 [b-SOAP 1.2].                                                                                                                                                                    |
+| <b>Notes</b> | BP-R2201 and BP-R2210 imply that there may be at most one child element of the soap:Body.<br>The referenced errata, NE05, would not be allowed by Continua (not compliant with the WS-I Profile). |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                 |             |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------|
+| <b>TP Id</b>              | TP/HFS/SEN/WSI/BP/BV-001                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                 |             |
+| <b>TP label</b>           | SOAP encodingStyle Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                 |             |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [OASIS/WS-I BP] |             |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | BP-R1005; M     | BP-R1006; M |
+| <b>Test purpose</b>       | Check that:<br>An Envelope must not contain soap:encodingStyle attributes on any of the elements whose namespace name is "http://schemas.xmlsoap.org/soap/envelope/"<br>[AND]<br>an Envelope must not contain soap:encodingStyle attributes on any element that is a child of soap:body.<br>[AND]<br>an Envelope described in an rpc-literal binding must not contain soap:encodingStyle attribute on any element that is a grandchild of soap:Body                                                                                               |                 |             |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                 |             |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                 |             |
+| <b>Initial condition</b>  | The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respective service according to its needs.                                                                                                                                                                                                                                                                                                                                              |                 |             |
+| <b>Test procedure</b>     | 1. Make the HFS sender under test send a SOAP message.<br>2. Check within the captured message:<br>a. If the soap:encodingStyle attribute is present, that the envelope contains:<br><ul style="list-style-type: none"> <li><input type="checkbox"/> a namespace which is not "http://schemas.xmlsoap.org/soap/envelope/"</li> <li><input type="checkbox"/> an element that is not a child of soap:Body.</li> <li><input type="checkbox"/> If an rpc-literal binding is used, check that the element is not a grandchild of soap:body.</li> </ul> |                 |             |
+| <b>Pass/Fail criteria</b> | If present, the soap:encodingStyle attribute is as specified within the test procedure above.                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                 |             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                 |             |
+
+|                          |                                                                                                                         |                 |             |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------|-----------------|-------------|
+| <b>TP Id</b>             | TP/HFS/SEN/WSI/BP/BV-002                                                                                                |                 |             |
+| <b>TP label</b>          | Use of SOAP in HTTP                                                                                                     |                 |             |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                             | [OASIS/WS-I BP] |             |
+|                          | <b>Testable items</b>                                                                                                   | BP-R1132; M     | BP-R1140; M |
+| <b>Test purpose</b>      | Check that:<br>A HTTP request message must use the HTTP POST method.<br>[AND]<br>A Message shall be sent using HTTP/1.1 |                 |             |
+| <b>Applicability</b>     | C_SEN_000 AND C_SEN_GEN_003                                                                                             |                 |             |
+| <b>Other PICS</b>        |                                                                                                                         |                 |             |
+| <b>Initial condition</b> | The simulated HFS receiver has a WebService enabled and the HFS sender under test is ready to send an HTTP request.     |                 |             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the HFS sender under test send a message to the simulated HFS receiver using the HTTP protocol.</li> <li>2. Check in the HTTP header of the captured message that: <ol style="list-style-type: none"> <li>a. the HTTP version is 1.1</li> <li>b. POST method is used.</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | Check that all values are as specified in the HTTP header.                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                |                 |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--|
+| <b>TP Id</b>              | TP/HFS/SEN/WSI/BP/BV-003                                                                                                                                                                                                                                                                                                                                       |                 |  |
+| <b>TP label</b>           | HTTP Status Codes                                                                                                                                                                                                                                                                                                                                              |                 |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                    | [OASIS/WS-I BP] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                          | BP-R1131; O     |  |
+| <b>Test purpose</b>       | Check that:<br>A consumer may automatically redirect a request when it encounters a "307 Temporary Redirect" HTTP status code in a response                                                                                                                                                                                                                    |                 |  |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                    |                 |  |
+| <b>Other PICS</b>         | C_SEN_WSI_001                                                                                                                                                                                                                                                                                                                                                  |                 |  |
+| <b>Initial condition</b>  | The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has an HTTP request ready to be sent to the respective service according to its needs.                                                                                                                                                          |                 |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the HFS sender under test send an HTTP request to the HFS receiver.</li> <li>2. The simulated HFS receiver responds with "307 Temporary Redirect" as the status code.</li> <li>3. If C_SEN_WSI_001=TRUE, the HFS sender redirects the request, or else the HFS sender does not redirect the request.</li> </ol> |                 |  |
+| <b>Pass/Fail criteria</b> | If C_SEN_WSI_001=TRUE, the HFS sender redirects the request to the http address indicated in the "307 Temporary Redirect" HTTP response.                                                                                                                                                                                                                       |                 |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                |                 |  |
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                 |             |
+|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------|
+| <b>TP Id</b>        | TP/HFS/SEN/WSI/BP/BV-004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                 |             |
+| <b>TP label</b>     | Messages using wsdl descriptions                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                 |             |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [OASIS/WS-I BP] |             |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | BP-R2211; M     | BP-R2212; M |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | BP-R2214; M     | BP-R2213; M |
+| <b>Test purpose</b> | Check that:<br>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<br>[AND]<br>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)<br>[AND]<br>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<br>[AND]<br>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. |                 |             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Other PICS</b>         | C_SEN_WSI_021                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Initial condition</b>  | The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respective service according to its needs.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Wait until the HFS sender under test sends a SOAP message or, if necessary, force it to send a SOAP message.</li> <li>2. Take the WSDL description of the web service using its URL and check the soap envelope of the captured message:<br/>           If an rpc-literal binding is used:           <ol style="list-style-type: none"> <li>a. If the soapbind:body element of the description is an empty string, there is no part accessor elements.</li> <li>b. If the soapbind:body element of the description is not empty, check that the part accessor of the envelope is present and that there is no xsi:nil attribute with a value of "1" or "true".</li> </ol>           If doc-literal binding is used:           <ol style="list-style-type: none"> <li>a. If the value of the parts attribute of soapbind:body is an empty string, the envelope does not have element content in soap:Body element.</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | Check that the envelope is as specified in step 2.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                    |                 |  |  |  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--|--|--|
+| <b>TP Id</b>              | TP/HFS/SEN/WSI/BP/BV-005                                                                                                                                                                                                                                                                                                                                           |                 |  |  |  |
+| <b>TP label</b>           | Port Types                                                                                                                                                                                                                                                                                                                                                         |                 |  |  |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                        | [OASIS/WS-I BP] |  |  |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                              | BP-R2301; M     |  |  |  |
+| <b>Test purpose</b>       | Check that:<br><br>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                                                                                                       |                 |  |  |  |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                        |                 |  |  |  |
+| <b>Other PICS</b>         | C_SEN_WSI_021                                                                                                                                                                                                                                                                                                                                                      |                 |  |  |  |
+| <b>Initial condition</b>  | The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respective service according to its needs.                                                                                                                                                               |                 |  |  |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Wait until the HFS sender under test sends a SOAP message or, if necessary, force it to send a SOAP message.</li> <li>2. Take the WSDL description of the web service using its URL and check the wsdl:parts elements in the wsdl:message.</li> <li>3. Compare their order with the soap:Body elements order.</li> </ol> |                 |  |  |  |
+| <b>Pass/Fail criteria</b> | In step 3, check that the order of the wsdl:parts are the same as the order of the elements in the soap:Body.                                                                                                                                                                                                                                                      |                 |  |  |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                    |                 |  |  |  |
+
+|                 |                          |                 |             |
+|-----------------|--------------------------|-----------------|-------------|
+| <b>TP Id</b>    | TP/HFS/SEN/WSI/BP/BV-006 |                 |             |
+| <b>TP label</b> | SOAP Binding             |                 |             |
+| <b>Coverage</b> | <b>Spec</b>              | [OASIS/WS-I BP] |             |
+|                 | <b>Testable items</b>    | BP-R2742; O     | BP-R2743; O |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>       | <p>Check that:</p> <p>An envelope may contain fault with a detail element that is not described by a soapbind:fault element in the corresponding WSDL description</p> <p>[AND]</p> <p>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</p>                                                                       |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_WSI_034 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Other PICS</b>         | C_SEN_WSI_021                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Initial condition</b>  | The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respective service according to its needs.                                                                                                                                                                                                                                                          |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Wait until the HFS sender under test sends a SOAP message or, if necessary, force it to send a SOAP message.</li> <li>2. The simulated HFS receiver responds with a message that will cause that HFS sender to generate a fault.</li> <li>3. The HFS sender under test sends a fault message.</li> <li>4. Check the envelope's fault detail element and the SOAP header block's header processing fault.</li> </ol> |
+| <b>Pass/Fail criteria</b> | In step 2, verify that the detail element cannot be described by the soapbind:fault element of the WSDL description, and that the header block cannot be described by a soapbind:headerfault element of the WSDL description.                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                 |             |
+|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------|
+| <b>TP Id</b>        | TP/HFS/SEN/WSI/BP/BV-006_B                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                 |             |
+| <b>TP label</b>     | SOAP Binding 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                 |             |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | [OASIS/WS-I BP] |             |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | BP-R2712; M     | BP-R2735; M |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | BP-R2737; M     | BP-R2738; M |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | BP-R2752; O     | BP-R2753; O |
+| <b>Test purpose</b> | <p>Check that:</p> <p>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</p> <p>[AND]</p> <p>An envelope described with an rpc-literal binding must place the part accessor elements for parameters and return value in no namespace</p> <p>[AND]</p> <p>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</p> <p>[AND]</p> <p>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</p> <p>[AND]</p> <p>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</p> <p>[AND]</p> <p>An Envelope may contain SOAP header blocks that are not described in the wsdl:binding that describes it</p> |                 |             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>[AND]</p> <p>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</p> <p>[AND]</p> <p>An envelope containing SOAP header blocks that are not described in the appropriate wsd:binding may have the mustUnderstand attribute on such SOAP header blocks set to '1'.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Other PICS</b>         | C_SEN_WSI_021                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Initial condition</b>  | The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respective service according to its needs.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>Wait until the HFS sender under test sends any SOAP message or, if necessary, force it to send any SOAP message.</li> <li>Check the captured message.</li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Pass/Fail criteria</b> | <p>Look into the WSDL description of the web service and check:</p> <ul style="list-style-type: none"> <li>in step 2: <ul style="list-style-type: none"> <li>if the SOAP header block is not described in the wsd:binding, it may 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;</li> <li>that all soapbind:headers specified in wsd:input or wsd:output of a wsd:operation of a wsd:binding are included in the envelope;</li> <li>if an rpc-literal binding is used; that the part accessor of the envelope has a local name equal to the name of the attribute of the wsd:part element; that it is not placed in a namespace; and that its descendants have a namespace qualified by the schema in which the part accessor types are defined;</li> <li>if a doc-literal binding is used, that the child element of the soap:Body is an instance of the global element declaration referenced by the corresponding wsd:message part.</li> </ul> </li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+## A.3 Subgroup 1.1.2 – Basic security profile (BSP)
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                            |
+|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|
+| <b>TP Id</b>        | TP/HFS/SEN/WSI/BSP/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                            |
+| <b>TP label</b>     | TLS Ciphersuites                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                            |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [OASIS/WS-I BSP]           |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | BSP-322; R      BSP-323; R |
+|                     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [ITU-T H.812]              |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | SecGuidelines2; M          |
+| <b>Test purpose</b> | <p>Check that:</p> <p>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</p> <p>[AND]</p> <p>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.</p> <p>The Profile recommends against the use of the following ciphersuites due to their lack of confidentiality services:</p> <ul style="list-style-type: none"> <li>- TLS_RSA_WITH_NULL_SHA</li> </ul> |                            |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>- TLS_RSA_WITH_NULL_MD5</li> </ul> <p>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.</p> <p>[AND]</p> <p>Continua HFS client and service components shall support AES cipher as specified in RFC 3268.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Other PICS</b>         | C_SEN_WSI_002, C_SEN_WSI_027, C_SEN_WSI_028, C_SEN_WSI_029, C_SEN_WSI_030                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Initial condition</b>  | The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respective service according to its needs.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>If an instance is FIPS compliant (C_SEN_WSI_002=true): <ol style="list-style-type: none"> <li>Load the simulated HFS receiver supporting TLS_RSA_FIPS_WITH_AES_128_CBC_SHA.</li> <li>Make the HFS sender under test establish a TLS connection.</li> <li>Check in the TLS handshake that the HFS sender under test SHOULD not support: <ul style="list-style-type: none"> <li><input type="checkbox"/> any ciphersuites with an DH_anon in their symbolic name</li> <li><input type="checkbox"/> any ciphersuites with a MD5 in their symbolic name</li> <li><input type="checkbox"/> any of the following ciphersuites: <ul style="list-style-type: none"> <li>• TLS_RSA_WITH_NULL_SHA</li> <li>• TLS_RSA_WITH_NULL_MD5</li> </ul> </li> <li><input type="checkbox"/> any ciphersuites that use 40 or 56 bit keys.</li> </ul> </li> <li>Check that the HFS sender under test supports TLS_RSA_FIPS_WITH_AES_128_CBC_SHA</li> <li>Close the connection.</li> </ol> </li> <li>If an instance is not FIPS compliant (C_SEN_WSI_002=false): <ol style="list-style-type: none"> <li>Load the simulated HFS receiver supporting TLS_RSA_WITH_AES_128_CBC_SHA.</li> <li>Make the HFS sender under test establish a TLS connection.</li> <li>Check in the TLS handshake that the HFS sender under test does not support (these are recommendations only): <ul style="list-style-type: none"> <li><input type="checkbox"/> any ciphersuites with an DH_anon in their symbolic name</li> <li><input type="checkbox"/> any ciphersuites with a MD5 in their symbolic name</li> <li><input type="checkbox"/> any of the following ciphersuites: <ul style="list-style-type: none"> <li>• TLS_RSA_WITH_NULL_SHA</li> <li>• TLS_RSA_WITH_NULL_MD5</li> </ul> </li> <li><input type="checkbox"/> any ciphersuites that use 40 or 56 bit keys.</li> </ul> </li> <li>Check that the HFS sender under test supports: TLS_RSA_WITH_AES_128_CBC_SHA.</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• If C_SEN_WSI_002 is supported, the HFS sender under test must support TLS_RSA_FIPS_WITH_AES_128_CBC_SHA.</li> <li>• If C_SEN_WSI_002 is not supported, the HFS sender under test must support TLS_RSA_WITH_AES_128_CBC_SHA.</li> <li>• The ciphersuites supported must match with these PICS: C_SEN_WSI_027, C_SEN_WSI_028, C_SEN_WSI_029, C_SEN_WSI_030.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>TP Id</b>              | TP/HFS/SEN/WSI/BSP/BV-001                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                           |                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |  |  |
+|---------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|
+| <b>TP label</b>           |                       | Security Policy                                                                                                                                                                                                                                                                                                                                                                                                                                                   |  |  |
+| <b>Coverage</b>           | <b>Spec</b>           | [OASIS/WS-I BSP]                                                                                                                                                                                                                                                                                                                                                                                                                                                  |  |  |
+|                           | <b>Testable items</b> | BSP-R3105; O                                                                                                                                                                                                                                                                                                                                                                                                                                                      |  |  |
+| <b>Test purpose</b>       |                       | <p>Check that:</p> <p>An HFS sender may agree in an out of band fashion with an HFS receiver on required and allowed signed and/or encrypted message content and security tokens</p>                                                                                                                                                                                                                                                                              |  |  |
+| <b>Applicability</b>      |                       | C_SEN_000 AND C_SEN_WSI_003 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                     |  |  |
+| <b>Other PICS</b>         |                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |  |  |
+| <b>Initial condition</b>  |                       | The simulated HFS receiver has a WebService enabled with many different services. The HFS sender under test and the simulated HFS receiver have never been partners in a message exchange.                                                                                                                                                                                                                                                                        |  |  |
+| <b>Test procedure</b>     |                       | <ol style="list-style-type: none"> <li>Make the HFS sender under test send its supported configuration to the HFS receiver, including supported encryption and/or signatures and security tokens.</li> <li>The simulated HFS receiver waits for a SOAP message from the HFS sender.</li> <li>The simulated HFS receiver checks the received message, ensuring that the HFS sender agrees or disagrees in an out of band fashion with the HFS receiver.</li> </ol> |  |  |
+| <b>Pass/Fail criteria</b> |                       | Step 3 is achieved.                                                                                                                                                                                                                                                                                                                                                                                                                                               |  |  |
+| <b>Notes</b>              |                       | This is WS-Trust negotiation.                                                                                                                                                                                                                                                                                                                                                                                                                                     |  |  |
+
+|                          |                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |              |              |
+|--------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------|
+| <b>TP Id</b>             |                       | TP/HFS/SEN/WSI/BSP/BV-003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |              |              |
+| <b>TP label</b>          |                       | Basic Profile Clarification                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |              |              |
+| <b>Coverage</b>          | <b>Spec</b>           | [OASIS/WS-I BSP]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |              |              |
+|                          | <b>Testable items</b> | BSP-R5801; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | BSP-R5805; M | BSP-R5813; M |
+| <b>Test purpose</b>      |                       | <p>Check that:</p> <p>bp11:R2301 must be true after any SOAP Message Security has been reversed for the Envelope. 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”.</p> <p>[AND]</p> <p>bp11:R2712 must be true after any SOAP Message Security has been reversed for the Envelope. 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”</p> <p>[AND]</p> <p>With respect to bp11:R2738 verification of an Envelope must occur after SOAP Message Security has been reversed. 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”.</p> |              |              |
+| <b>Applicability</b>     |                       | C_SEN_000 AND C_SEN_WSI_003 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |              |              |
+| <b>Other PICS</b>        |                       | C_SEN_WSI_021                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |              |              |
+| <b>Initial condition</b> |                       | The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respective service according to its needs.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |              |              |
+| <b>Test procedure</b>    |                       | <ol style="list-style-type: none"> <li>Make the HFS sender under test send a SOAP message using security.</li> <li>As the simulated HFS receiver knows its description (wsdl), after reversing the SOAP message security, check that: <ol style="list-style-type: none"> <li>The order of the elements in the soap:body is the same as the wsdl:parts in the wsdl:message.</li> <li>The envelope includes all soapbind:headers specified on a wsdl:input or wsdl:output of a wsdl:operation of a wsdl:binding.</li> </ol> </li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                   |              |              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | c. If doc-literal binding is used, it 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.                                                                                                                                                                                                                                                                               |
+| <b>Pass/Fail criteria</b> | All steps are as specified within the test procedure above.                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Notes</b>              | "Reversing SOAP Message Security" means removing the various impacts of applying "SOAP Message Security" that may have been applied since the MESSAGE (BP1.0) or ENVELOPE (BP 1.1) was originally created for that recipient according to the BP. This may mean decrypting relevant portions of the XML or removing XML signature elements or making other reverse transformations as appropriate to the aspects of SOAP message security that were applied in the specific circumstance. |
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                  |              |              |
+|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------------|--------------|
+| <b>TP Id</b>        | TP/HFS/SEN/WSI/BSP/BV-005                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                  |              |              |
+| <b>TP label</b>     | Timestamp element                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                  |              |              |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [OASIS/WS-I BSP] |              |              |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | BSP-R3227; M     | BSP-R3203; M | BSP-R3224; R |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | BSP-R3221; M     | BSP-R3222; M | BSP-R3220; R |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | BSP-R3229; R     | BSP-R3213; M | BSP-R3215; M |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | BSP-R3225; M     | BSP-R3226; M | BSP-R3217; M |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | BSP-R3223; M     |              |              |
+| <b>Test purpose</b> | <p>Check that:</p> <p>A SECURITY_HEADER must not contain more than one Timestamp</p> <p>[AND]</p> <p>A Timestamp must contain exactly one Created</p> <p>[AND]</p> <p>Any Timestamp must not contain more than one Expires</p> <p>[AND]</p> <p>Any Timestamp containing an Expires must contain a Created that precedes its sibling Expires</p> <p>[AND]</p> <p>Any Timestamp must not contain anything other than Created or Expires elements</p> <p>[AND]</p> <p>Any Created should not contain a seconds value with more than three digits to the right of the decimal (milliseconds).</p> <p>[AND]</p> <p>Any Expires should not contain a seconds value with more than three digits to the right of the decimal (milliseconds).</p> <p>[AND]</p> <p>Any Created containing second values must specify seconds values less than 60</p> <p>[AND]</p> <p>Any Expires containing second values must specify seconds values less than 60</p> <p>[AND]</p> <p>Any Created must not include a ValueType attribute</p> <p>[AND]</p> <p>Any Expires must not include a ValueType attribute</p> <p>[AND]</p> <p>Any Created must contain time values in UTC format as specified by the XML Schema type (dateTime).</p> <p>[AND]</p> |                  |              |              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | Any Expires must contain time values in UTC format as specified by the XML Schema type (dateTime).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_WSI_004 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Other PICS</b>         | C_SEN_WSI_021                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Initial condition</b>  | The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respective service according to its needs.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the HFS sender under test send a SOAP message using a Timestamp element.</li> <li>2. Check in the captured message that: <ol style="list-style-type: none"> <li>a. Timestamp is present and there is only one. For example: <pre>&lt;wsu:Timestamp wsu:Id="timestamp"&gt;   &lt;wsu:Created&gt;2001-09-13T08:42:00Z&lt;/wsu:Created&gt;   &lt;wsu:Expires&gt;2001-10-13T09:00:00Z&lt;/wsu:Expires&gt; &lt;/wsu:Timestamp&gt;</pre> </li> <li>b. Only one Created element is present and inside it: <ul style="list-style-type: none"> <li><input type="checkbox"/> ValueType attribute is not included</li> <li><input type="checkbox"/> UTC format is used in time values</li> <li><input type="checkbox"/> seconds values are less than 60 and its decimal values are recommended to be less than 3 digits to the right.</li> </ul> </li> <li>c. If the Expires element is present, only one, it comes after the Created element and: <ul style="list-style-type: none"> <li><input type="checkbox"/> ValueType attribute is not included</li> <li><input type="checkbox"/> UTC format is used in time values</li> <li><input type="checkbox"/> seconds values are less than 60 and its decimal values are recommended to be less than 3 digits to the right.</li> </ul> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The elements in step 2 are as specified within the test procedure above.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                  |              |              |
+|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------------|--------------|
+| <b>TP Id</b>        | TP/HFS/SEN/WSI/BSP/BV-006                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                  |              |              |
+| <b>TP label</b>     | Security Token References – Direct References                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                  |              |              |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [OASIS/WS-I BSP] |              |              |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | BSP-R3061; M     | BSP-R3057; M | BSP-R3064; M |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | BSP-R3059; M     | BSP-R3058; M | BSP-R3062; M |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | BSP-R3027; M     | BSP-R3211; M |              |
+| <b>Test purpose</b> | Check that:<br>A SECURITY_TOKEN_REFERENCE must provide exactly one token reference<br>[AND]<br>Any STR_REFERENCE must not reference a SECURITY_TOKEN_REFERENCE<br>[AND]<br>Any STR_REFERENCE must not reference an STR_EMBEDDED<br>[AND]<br>Any STR_REFERENCE must specify a ValueType attribute<br>[AND]<br>Any STR_REFERENCE ValueType attribute must contain a value for the referenced SECURITY_TOKEN specified by the corresponding security token profile.<br>[AND]<br>Any STR_REFERENCE must specify a URI attribute |                  |              |              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>[AND]</p> <p>Any SECURITY_TOKEN_REFERENCE must not contain an STR_KEY_NAME</p> <p>[AND]</p> <p>Any SECURITY_TOKEN_REFERENCE must not reference a ds:KeyInfo element</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_WSI_016 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Initial condition</b>  | The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respective service according to its needs.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Test procedure</b>     | <p>1. Make the HFS sender under test send a SOAP message using a security token reference (STR) with an STR_Reference.</p> <pre>&lt;wsse:SecurityTokenReference wsu:Id="..."&gt;<br/>  &lt;wsse:Reference URI="..." ValueType="..."/&gt;<br/>&lt;/wsse:SecurityTokenReference&gt;</pre> <p>2. Check in the captured message that:</p> <ol style="list-style-type: none"> <li>There is only one STR_Reference within the SECURITY_TOKEN_REFERENCE.</li> <li>STR_Reference does not reference another SECURITY_TOKEN_REFERENCE or an STR_Embedded.</li> <li>URI Attribute is present.</li> <li>ValueType attribute is present and it contains a value for the referenced security token specified by the corresponding security token profile (e.g., X.509 certificate token).</li> <li>SECURITY_TOKEN_REFERENCE does not contain an STR_KEY_NAME and does not reference a ds:KeyInfo element.</li> </ol> |
+| <b>Pass/Fail criteria</b> | Check that SECURITY_TOKEN_REFERENCE is as specified in steps 1 and 2.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                  |              |              |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------------|--------------|
+| <b>TP Id</b>             | TP/HFS/SEN/WSI/BSP/BV-007                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                  |              |              |
+| <b>TP label</b>          | Security Token References – Key Identifier                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                  |              |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [OASIS/WS-I BSP] |              |              |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | BSP-R3054; M     | BSP-R3063; M | BSP-R3070; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | BSP-R3071; M     |              |              |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Any STR_KEY_IDENTIFIER must specify a ValueType attribute</p> <p>[AND]</p> <p>Any STR_KEY_IDENTIFIER ValueType attribute must contain a value specified within the security token profile associated with the referenced SECURITY_TOKEN</p> <p>[AND]</p> <p>Any STR_KEY_IDENTIFIER that refers to a SECURITY_TOKEN other than a SAML_TOKEN must specify an EncodingType attribute</p> <p>[AND]</p> <p>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".</p> |                  |              |              |
+| <b>Applicability</b>     | C_SEN_000 AND C_SEN_WSI_017 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                  |              |              |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                  |              |              |
+| <b>Initial condition</b> | The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respective service according to its needs.                                                                                                                                                                                                                                                                                                                                                                                                 |                  |              |              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test procedure</b>     | 1. Make the HFS sender under test send a SOAP message using a security token reference (STR) with a key identifier reference: <pre>&lt;wsse:SecurityTokenReference&gt;   &lt;wsse:KeyIdentifier wsu:Id="..."     ValueType="..."     EncodingType="..."&gt;     ...   &lt;/wsse:KeyIdentifier&gt; &lt;/wsse:SecurityTokenReference&gt;</pre> 2. Check in the captured message that: <ol style="list-style-type: none"> <li>ValueType is present and contains a value specified within the security token profile associated with the referenced security token.</li> <li>If an SAML token is referenced, the encodingType attribute is not present.</li> <li>If the referenced token is different from the SAML token, the encodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary".</li> </ol> |
+| <b>Pass/Fail criteria</b> | In step 2, attributes are as specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                  |              |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------------|
+| <b>TP Id</b>             | TP/HFS/SEN/WSI/BSP/BV-008                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                  |              |
+| <b>TP label</b>          | Security Token References – Embedded References                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                  |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [OASIS/WS-I BSP] |              |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | BSP-R3060; M     | BSP-R3025; M |
+| <b>Test purpose</b>      | Check that:<br><br>Any STR_EMBEDDED must contain only a single child element which is an INTERNAL_SECURITY_TOKEN<br>[AND]<br>Any INTERNAL_SECURITY_TOKEN contained in an STR_EMBEDDED must be in the same format as if it were a child of a SECURITY_HEADER<br>[AND]<br>Any STR_EMBEDDED must not contain a wsse:SecurityTokenReference child element                                                                                                                                                                                                                                                                |                  |              |
+| <b>Applicability</b>     | C_SEN_000 AND C_SEN_WSI_018 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                  |              |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                  |              |
+| <b>Initial condition</b> | The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respective service according to its needs.                                                                                                                                                                                                                                                                                                                                                                                                                 |                  |              |
+| <b>Test procedure</b>    | 1. Make the HFS sender under test send a SOAP message using a security token reference (STR) with an embedded reference: <pre>&lt;wsse:SecurityTokenReference&gt;   &lt;wsse:Embedded wsu:Id="..."&gt;     ...   &lt;/wsse:Embedded&gt; &lt;/wsse:SecurityTokenReference&gt;</pre> 2. Check in the captured message that: <ol style="list-style-type: none"> <li>STR_EMBEDDED has only one child element that is an internal security token, and it is in the same format as if it were a child of a security header.</li> <li>STR_EMBEDDED does not contain a wsse:SecurityTokenReference child element.</li> </ol> |                  |              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | In step 2, "Security Token Reference Embedded" are as specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              | <p>An internal token reference is a reference to a token that is contained in the same message. An example of an incorrect and a correct format are:</p> <p>INCORRECT:</p> <pre>&lt;!-- This example is incorrect because the wsse:Embedded element carries the data for the X.509 certificate directly rather than as a wsse:BinarySecurityToken element --&gt; &lt;wsse:SecurityTokenReference&gt;   &lt;wsse:Embedded wsu:Id="SomeCert"&gt; lui+Jy4WYKGJW5xM3aHnLxOpGVlpzSg4V486hHFe7sHET/uxxVBovT7JV1A2RnWSWkXm9jAEdsm/...   &lt;/wsse:Embedded&gt; &lt;/wsse:SecurityTokenReference&gt;</pre> <p>CORRECT:</p> <pre>&lt;wsse:SecurityTokenReference&gt;   &lt;wsse:Embedded wsu:Id="TheEmbeddedElementAroundSomeCert"&gt;     &lt;wsse:BinarySecurityToken wsu:Id="SomeCert"       ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"       EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"&gt; lui+Jy4WYKGJW5xM3aHnLxOpGVlpzSg4V486hHFe7sHET/uxxVBovT7JV1A2RnWSWkXm9jAEdsm/...     &lt;/wsse:BinarySecurityToken&gt;   &lt;/wsse:Embedded&gt; &lt;/wsse:SecurityTokenReference&gt;</pre> |
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                  |              |
+|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------------|
+| <b>TP Id</b>        | TP/HFS/SEN/WSI/BSP/BV-009                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                  |              |
+| <b>TP label</b>     | Security Token References – Internal References                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                  |              |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [OASIS/WS-I BSP] |              |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | BSP-R3022; M     | BSP-R3023; M |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | BSP-R5205; M     | BSP-R3067; M |
+| <b>Test purpose</b> | <p>Check that:</p> <p>Any SECURITY_TOKEN_REFERENCE that references an INTERNAL_SECURITY_TOKEN which has a wsu:Id attribute must contain an STR_REFERENCE or STR_EMBEDDED</p> <p>[AND]</p> <p>Any SECURITY_TOKEN_REFERENCE that references an INTERNAL_SECURITY_TOKEN that is referenced several times should contain an STR_REFERENCE rather than an STR_EMBEDDED</p> <p>[AND]</p> <p>Any STR_REFERENCE to an INTERNAL_SECURITY_TOKEN having an ID attribute must contain a URI attribute with a Shorthand XPointer value</p> <p>[AND]</p> <p>Any INTERNAL_SECURITY_TOKEN that is not contained in an STR_EMBEDDED must precede all SECURITY_TOKEN_REFERENCE elements that reference it in the SOAP Envelope</p> <p>[AND]</p> <p>Any STR_REFERENCE that is a descendant of an ENCRYPTED_DATA must not use a Shorthand XPointer to refer to an INTERNAL_SECURITY_TOKEN located in a SECURITY_HEADER other than the SECURITY_HEADER containing a reference</p> |                  |              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | (EK_REFERENCE_LIST or an ENC_REFERENCE_LIST) to the ENCRYPTED_DATA                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_WSI_019 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Initial condition</b>  | The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respective service according to its needs.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the HFS sender under test send a SOAP message including a SecurityTokenReference with an internal reference.</li> <li>2. Check in the captured message that: <ol style="list-style-type: none"> <li>a. The SECURITY_TOKEN_REFERENCE references an internal security token.</li> <li>b. The SECURITY_TOKEN_REFERENCE contains an STR_Reference or STR_Embedded. It is recommended to be an STR_Reference.</li> <li>c. The STR_Reference to an INTERNAL_SECURITY_TOKEN which has an ID attribute contains a URI attribute with a shorthand XPointer value.</li> <li>d. The INTERNAL_SECURITY_TOKEN precedes all SECURITY_TOKEN_REFERENCE elements that reference it in the SOAP envelope.</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | References are as specified within the test procedure above.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              | The internal token reference is a reference to a token that is contained in the same message.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                     |                  |  |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--|
+| <b>TP Id</b>              | TP/HFS/SEN/WSI/BSP/BV-010                                                                                                                                                                                                                                                                                                                           |                  |  |
+| <b>TP label</b>           | Security Token References – External References                                                                                                                                                                                                                                                                                                     |                  |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                         | [OASIS/WS-I BSP] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                               | BSP-R3024; M     |  |
+| <b>Test purpose</b>       | Check that:<br>Any EXTERNAL_TOKEN_REFERENCE that can use an STR_REFERENCE must contain an STR_REFERENCE                                                                                                                                                                                                                                             |                  |  |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_WSI_020 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                       |                  |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                     |                  |  |
+| <b>Initial condition</b>  | The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respective service according to its needs.                                                                                                                                                |                  |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the HFS sender under test send a SOAP message including a SecurityTokenReference with an external reference.</li> <li>2. Check in the text file that: <ol style="list-style-type: none"> <li>a. It is recommended that the external token reference contain an STR_Reference.</li> </ol> </li> </ol> |                  |  |
+| <b>Pass/Fail criteria</b> | References are as specified within the test procedure above.                                                                                                                                                                                                                                                                                        |                  |  |
+| <b>Notes</b>              | The external token reference is a reference to a token that is not contained in the same message.                                                                                                                                                                                                                                                   |                  |  |
+
+|                 |                           |                  |              |              |
+|-----------------|---------------------------|------------------|--------------|--------------|
+| <b>TP Id</b>    | TP/HFS/SEN/WSI/BSP/BV-023 |                  |              |              |
+| <b>TP label</b> | SAML Token                |                  |              |              |
+| <b>Coverage</b> | <b>Spec</b>               | [OASIS/WS-I BSP] |              |              |
+|                 | <b>Testable items</b>     | BSP-R6601; M     | BSP-R6602; M | BSP-R6609; M |
+|                 |                           | BSP-R6603; M     | BSP-R6604; M | BSP-R6605; M |
+|                 |                           | BSP-R6606; M     | BSP-R6607; M | BSP-R6608; M |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>       | <p>Check that:</p> <p>Any SAML_SC_KEY_INFO must not contain a reference to a SAML_TOKEN</p> <p>[AND]</p> <p>Any STR_KEY_IDENTIFIER that references a INTERNAL_SAML_TOKEN must include a ValueType attribute</p> <p>[AND]</p> <p>Any STR_KEY_IDENTIFIER that references a EXTERNAL_SAML_TOKEN must include a ValueType attribute</p> <p>[AND]</p> <p>Any STR_KEY_IDENTIFIER ValueType attribute that references SAML_TOKEN must have a value of "http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLID"</p> <p>[AND]</p> <p>Any STR_KEY_IDENTIFIER that references a SAML_TOKEN must not include an EncodingType attribute</p> <p>[AND]</p> <p>Any STR_KEY_IDENTIFIER that references a SAML_TOKEN must have a value encoded as an xs:string</p> <p>[AND]</p> <p>Any SECURITY_TOKEN_REFERENCE that references an EXTERNAL_SAML_TOKEN must contain a SAML_AUTHORITY_BINDING</p> <p>[AND]</p> <p>Any AuthorityKind attribute of a SAML_AUTHORITY_BINDING must have a value of saml:AssertionIdReference</p> <p>[AND]</p> <p>Any SECURITY_TOKEN_REFERENCE that references an INTERNAL_SAML_TOKEN must not contain a SAML_AUTHORITY_BINDING</p> |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Initial condition</b>  | The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respective service according to its needs.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the HFS sender under test send a SOAP message using an SAML token.</li> <li>2. Check in the captured message that the expected saml:Assertion element confirms that: <ol style="list-style-type: none"> <li>a. SAML KeyInfo does not contain a reference to an SAML token.</li> <li>b. In an STR KeyIdentifier that references an SAML token: <ul style="list-style-type: none"> <li><input type="checkbox"/> EncodingType attribute is not present.</li> <li><input type="checkbox"/> ValueType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLID".</li> <li><input type="checkbox"/> The Value encoded is an xs:string.</li> </ul> </li> <li>c. If a security token reference references an external SAML token: <ul style="list-style-type: none"> <li><input type="checkbox"/> saml:AuthorityBinding element is present</li> <li><input type="checkbox"/> AuthorityKind = Value of saml:AssertionIdReference.</li> </ul> </li> </ol> </li> </ol>                                                                                                                                   |
+| <b>Pass/Fail criteria</b> | The SAML token element is as specified within the test procedure above.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+## A.4 Subgroup 1.1.3 – Reliable messaging (RM)
+
+|                 |                          |
+|-----------------|--------------------------|
+| <b>TP Id</b>    | TP/HFS/SEN/WSI/RM/BV-000 |
+| <b>TP label</b> | Protocol Preconditions   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                           |                 |                   |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------------|
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                               | [OASIS WS-I RM] |                   |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                     | Namespace; M    | ProtocolPrec 2; M |
+| <b>Test purpose</b>       | Check that:<br>The XML namespace URI that MUST be used by implementations of this specification is:<br>http://docs.oasis-open.org/ws-rx/wsrm/200702<br><br>[AND]<br><br>The RM Source MUST have successfully created a Sequence with the RM Destination                                                                                                                                                                   |                 |                   |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_WSI_021 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                             |                 |                   |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                           |                 |                   |
+| <b>Initial condition</b>  | The HFS sender under test and the simulated HFS receiver are in the "None" sequence state.                                                                                                                                                                                                                                                                                                                                |                 |                   |
+| <b>Test procedure</b>     | 1. The HFS sender under test sends a CreateSequence message with an offer element to the HFS receiver.<br>2. The simulated HFS receiver responds with a CreateSequenceResponse message accepting the offer.<br>3. The HFS sender sends a Sequence message.<br>4. The HFS receiver responds with its Sequence message and a SequenceAcknowledgement element.<br>5. The HFS sender sends a SequenceAcknowledgement element. |                 |                   |
+| <b>Pass/Fail criteria</b> | Check that in every wsrm element its XML namespace is:<br>xmlns:wsrm=" http://docs.oasis-open.org/ws-rx/wsrm/200702", and in step 1 the CreateSequence request is made.                                                                                                                                                                                                                                                   |                 |                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                           |                 |                   |
+
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                          |                     |
+|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------|
+| <b>TP Id</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | TP/HFS/SEN/WSI/RM/BV-001 |                     |
+| <b>TP label</b>      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Delivery Assurances      |                     |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [OASIS WS-I RM]          |                     |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | DelivAssurance 4; C      | DelivAssurance 7; C |
+|                      | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [ITU-T H.812]            |                     |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | CommonReq 2; O           | CommonReq 3; R      |
+| <b>Test purpose</b>  | Check that:<br><br>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.<br><br>[AND]<br><br>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<br><br>[AND]<br><br>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.<br><br>[AND]<br><br>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. |                          |                     |
+| <b>Applicability</b> | C_SEN_000 AND C_SEN_WSI_021 AND (C_SEN_WSI_023 OR C_SEN_WSI_024) AND<br>C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                          |                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                               |
+| <b>Initial condition</b>  | The HFS sender under test and the simulated HFS receiver are in the "None" sequence state. The simulated HFS receiver is able to avoid the response to a CreateSequence message.                                                                                                                                              |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the HFS sender send a CreateSequence message.</li> <li>2. The simulated HFS receiver does not respond to that message.</li> <li>3. If C_SEN_WSI_023, the HFS sender may retry transmission.</li> <li>4. If C_SEN_WSI_024, the HFS sender should retry transmission.</li> </ol> |
+| <b>Pass/Fail criteria</b> | All steps are as specified within the test procedure above.                                                                                                                                                                                                                                                                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                 |                |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----------------|
+| <b>TP Id</b>              | TP/HFS/SEN/WSI/RM/BV-003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                 |                |
+| <b>TP label</b>           | Consideration on the Use of "Piggy-Backing"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                 |                |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | [OASIS WS-I RM] |                |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | PiggyBack 1; O  | PiggyBack 2; M |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>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.</p> <p>[AND]</p> <p>Reference parameters MUST be considered when determining whether two EPRs are targeted to the same Endpoint</p> <p>[AND]</p> <p>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.</p>                                                                                                                                                                                                                                                                                                                                                                 |                 |                |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_WSI_021 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                 |                |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                 |                |
+| <b>Initial condition</b>  | The HFS sender under test and the simulated HFS receiver are in the "None" sequence state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                 |                |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The HFS sender under test sends a CreateSequence message with an offer element.</li> <li>2. The simulated HFS receiver responds with CreateSequenceResponse accepting the offer.</li> <li>3. The HFS sender sends a Sequence message.</li> <li>4. The HFS receiver responds with a SOAP message including a SequenceAcknowledgement header block and a Sequence header block (indicating that it is the last message).</li> <li>5. The HFS sender responds including a SequenceAcknowledgement header block. <ul style="list-style-type: none"> <li><input type="checkbox"/> If the SOAP message also contains a CloseSequence header block or any other header block (piggy-backing), all the header blocks will have the same EPR (endpoint reference).</li> <li><input type="checkbox"/> If not, any other header block is sent in the same SOAP message, the HFS sender under test sends a message for every other RM-element (not piggy-backing).</li> </ul> </li> </ol> |                 |                |
+| <b>Pass/Fail criteria</b> | In step 5, If the HFS sender sends only one message with more than one header block (piggy-backing), the EPR is the same for every header block.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                 |                |
+| <b>Notes</b>              | 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 that there is only one "wsa:To" element in the soap:header.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                 |                |
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                   |                   |
+|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------------|
+| <b>TP Id</b>        | TP/HFS/SEN/WSI/RM/BV-004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                   |                   |
+| <b>TP label</b>     | Sequence Creation                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                   |                   |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [OASIS WS-I RM]   |                   |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | WSAddress 1; C    | SeqCreation 1; M  |
+| SeqCreation 5; M    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | SeqCreation 7; M  | SeqCreation 8; M  |
+| SeqCreation 9; O    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | SeqCreation 10; M | SeqCreation 11; M |
+| SeqCreation 12; M   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | SeqCreation 14; O | SeqCreation 15; O |
+| SeqCreation 22; O   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                   |                   |
+| <b>Test purpose</b> | <p>Check that:</p> <p>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.</p> <p>[AND]</p> <p>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</p> <p>[AND]</p> <p>The RM Source MAY include an offer to create an inbound Sequence within the CreateSequence message.</p> <p>[AND]</p> <p>The RM Source MUST NOT send wsrm:CreateSequence element as a header block.</p> <p>[AND]</p> <p>The RM Source MUST include wsrm:AcksTo element in any CreateSequence message it sends. This element is of type wsa:EndpointReferenceType (as specified by WS-Addressing). It specifies the endpoint reference to which messages containing SequenceAcknowledgement header blocks and faults related to the created Sequence are to be sent, unless otherwise noted in this specification</p> <p>[AND]</p> <p>Implementations MUST NOT use an endpoint reference in the AcksTo element that would prevent the sending of Sequence Acknowledgements back to the RM Source.</p> <p>[AND]</p> <p>wsrm:Expires element, if present, of type xs:duration specifies the RM Source's requested duration for the Sequence. The RM Destination MAY either accept the requested duration or assign a lesser value of its choosing. A value of "PT0S" indicates that the Sequence will never expire. Absence of the element indicates an implied value of "PT0S"</p> <p>[AND]</p> <p>The RM Source MUST set the value of wsrm:Identifier element to an absolute URI (conformant with RFC3986) that uniquely identifies the offered Sequence</p> <p>[AND]</p> <p>An RM Source MUST include wsrm:Endpoint element, of type wsa:EndpointReferenceType (as specified by WS-Addressing). This element specifies the endpoint reference to which Sequence Lifecycle Messages, Acknowledgement Requests, and fault messages related to the offered Sequence are to be sent.</p> <p>[AND]</p> <p>Implementations MUST NOT use an endpoint reference in the Endpoint element that would prevent the sending of Sequence Lifecycle Message, etc.</p> <p>[AND]</p> <p>wsrm:Expires element within wsrm:Offer, if present, of type xs:duration specifies the duration for the offered Sequence. A value of "PT0S" indicates that the offered Sequence will never expire. Absence of the element indicates an implied value of "PT0S"</p> |                   |                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>[AND]</p> <p>wsrm:IncompleteSequenceBehaviour element, if present in wsrm:Offer element within wsrm:CreateSequence 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.</p> <p>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.</p> <p>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.</p> <p>The default value of "NoDiscard" indicates that no acknowledged messages in the Sequence will be discarded.</p> <p>[AND]</p> <p>If a CreateSequenceResponse is returned without a child Accept in response to a CreateSequence that did contain a child Offer, then the RM Source MAY immediately reclaim any resources associated with the unused offered Sequence.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_WSI_021 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Initial condition</b>  | The HFS sender under test and the simulated HFS receiver are in the "None" sequence state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Wait until the HFS sender under test sends a CreateSequence message.</li> <li>2. Check that the captured message has the following properties: <ol style="list-style-type: none"> <li>a. In the header block: <ul style="list-style-type: none"> <li><input type="checkbox"/> wsa:Action = http://docs.oasis-open.org/ws-rx/wsrm/200702/CreateSequence.</li> <li><input type="checkbox"/> wsrm:CreateSequence is not present.</li> </ul> </li> <li>b. In the body of the message: <ul style="list-style-type: none"> <li><input type="checkbox"/> wsrm:AcksTo of type wsa:EndpointReferenceType is present and defines a valid endpoint.</li> <li><input type="checkbox"/> wsrm:Expires element, if present: <ul style="list-style-type: none"> <li>• its type is xs:duration.</li> </ul> </li> <li><input type="checkbox"/> If an offer element is present: <ul style="list-style-type: none"> <li>• wsrm:IncompleteSequenceBehaviour element may be present. Possible values are: "discard", "DiscardEntireSequence", "DiscardFollowingFirstGap" and "NoDiscard".</li> <li>• wsrm:Identifier value is an absolute URI that uniquely identifies the offered Sequence.</li> <li>• wsrm:Expires element, if present, its type is xs:duration.</li> <li>• wsrm:Endpoint element is present and its type is wsa:EndpointReferenceType, and it defines a valid endpoint.</li> </ul> </li> </ul> </li> </ol> </li> <li>3. The simulated HFS receiver responds using a CreateSequenceResponse message without an accept element or a CreateSequenceRefused fault.</li> <li>4. If an offer element is present: <ul style="list-style-type: none"> <li><input type="checkbox"/> The HFS sender can reclaim the resources.</li> </ul> </li> </ol> |
+| <b>Pass/Fail criteria</b> | All elements are as specified within the test procedure above.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                 |                          |
+|-----------------|--------------------------|
+| <b>TP Id</b>    | TP/HFS/SEN/WSI/RM/BV-005 |
+| <b>TP label</b> | Closing a Sequence       |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                  |                 |                 |  |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-----------------|-----------------|--|--|
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [OASIS WS-I RM]  |                 |                 |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | WSAddress 1; C   | SeqClosing 1; O | SeqClosing 2; M |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | SeqClosing 4; R  | SeqClosing 8; O | SeqClosing 9; M |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | SeqClosing 10; R |                 |                 |  |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>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.</p> <p>[AND]</p> <p>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.</p> <p>[AND]</p> <p>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</p> <p>[AND]</p> <p>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</p> <p>[AND]</p> <p>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</p> <p>[AND]</p> <p>The RM Source SHOULD include wsrm:LastMessageNumber element in any CloseSequence message it sends.</p> |                  |                 |                 |  |  |
+| <b>Applicability</b>     | C_SEN_000 AND C_SEN_WSI_021 AND C_SEN_WSI_032 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                  |                 |                 |  |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                  |                 |                 |  |  |
+| <b>Initial condition</b> | The HFS sender under test and the simulated HFS receiver are in the "Created" sequence state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                  |                 |                 |  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The HFS sender under test starts to send a Sequence message including an AckRequested element or indicating that it is the last message in the header block of the last message.</li> <li>2. The simulated HFS receiver accepts all messages and if an offer was sent by the HFS sender, it also sends a Sequence message indicating that it is the last message.</li> <li>3. The HFS sender sends with a SequenceAcknowledgement message.</li> <li>4. If the HFS sender sends a CloseSequenceMessage then check the received message: <ol style="list-style-type: none"> <li>a. In the header block: <input type="checkbox"/> wsa:Action = http://docs.oasis-open.org/ws-rx/wsrm/200702/CloseSequence.</li> <li>b. In the body of the message, within the CloseSequence element: <input type="checkbox"/> wsrm:Identifier value = an absolute URI of the closing sequence. <input type="checkbox"/> The presence of wsrm:LastMsgNumber is recommended, and if it is present it must be the same in all CloseSequence elements of that closing sequence.</li> </ol> </li> <li>5. Or else, if C_SEN_WSI_032 = TRUE then force the HFS sender to close the sequence and check the received message. <ol style="list-style-type: none"> <li>a. In the header block: <input type="checkbox"/> wsa:Action = http://docs.oasis-open.org/ws-rx/wsrm/200702/CloseSequence.</li> </ol> </li> </ol>                                                                                                                                                                                                                                                             |                  |                 |                 |  |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>b. In the body of the message, within the CloseSequence element:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> wsrm:Identifier value = an absolute URI of the closing sequence.</li> <li><input type="checkbox"/> The presence of wsrm:LastMsgNumber is recommended, and if it is present it must be the same in all CloseSequence elements of that closing sequence.</li> </ul> <p>6. The simulated HFS receiver responds with a CloseSequenceResponse.</p> |
+| <b>Pass/Fail criteria</b> | All elements are as specified within the test procedure above.                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                  |                  |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|------------------|
+| <b>TP Id</b>             | TP/HFS/SEN/WSI/RM/BV-005_B                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                  |                  |
+| <b>TP label</b>          | Closing a Sequence Response                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                  |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [OASIS WS-I RM]  |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | WSAddress 1; C   | SeqClosing 1; O  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | SeqClosing 12; M | SeqClosing 11; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>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.</p> <p>[AND]</p> <p>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.</p> <p>[AND]</p> <p>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</p> <p>[AND]</p> <p>The responder (RM Source or RM Destination) MUST include wsrm: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.</p>                                                                                                                                                                                                                                                                             |                  |                  |
+| <b>Applicability</b>     | C_SEN_000 AND C_SEN_WSI_021 AND NOT(C_SEN_WSI_032) AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                  |                  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                  |                  |
+| <b>Initial condition</b> | The HFS sender under test and the simulated HFS receiver are in the "Created" sequence state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                  |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Run the HFS sender under test (make sure that the HFS sender has something, a measure or anything else, to send).</li> <li>2. Wait until the HFS sender sends a CreateSequence message.</li> <li>3. The simulated HFS receiver responds with a CreateSequenceResponse. If an offer is sent by the HFS sender in step 2, the HFS receiver accepts the offer.</li> <li>4. The HFS sender under test starts to send a Sequence message including an AckRequested element or indicating that it is the last message in the header block of the last message.</li> <li>5. The simulated HFS receiver accepts all messages and if an offer was sent by the HFS sender, it also sends a Sequence message indicating that it is the last message.</li> <li>6. The HFS sender sends with a SequenceAcknowledgement message.</li> <li>7. The simulated HFS receiver sends a CloseSequence element in the body of the message, including a correct LastMessageNumber.</li> <li>8. The HFS sender responds with a CloseSequenceResponse message including: <ul style="list-style-type: none"> <li>a. In the header block: <ul style="list-style-type: none"> <li><input type="checkbox"/> wsa:Action = http://docs.oasis-open.org/ws-rx/wsrm/200702/CloseSequenceResponse.</li> </ul> </li> </ul> </li> </ol> |                  |                  |
+
+|                           |                                                                                                                                                                                               |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>b. In the body of the message:</p> <p><input type="checkbox"/> a CloseSequenceResponse element with a wsm:Identifier element that is an absolute URI of the closing sequence response.</p> |
+| <b>Pass/Fail criteria</b> | All elements are as specified within the test procedure above.                                                                                                                                |
+| <b>Notes</b>              |                                                                                                                                                                                               |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                      |                      |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------|
+| <b>TP Id</b>             | TP/HFS/SEN/WSI/RM/BV-006                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                      |                      |
+| <b>TP label</b>          | Sequence Termination                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                      |                      |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [OASIS WS-I RM]      |                      |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | WSAddress 1; M       | SeqTermination 1; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | SeqTermination 4; O  | SeqTermination 5; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | SeqTermination 11; M | SeqTermination 12; R |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>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.</p> <p>[AND]</p> <p>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</p> <p>[AND]</p> <p>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</p> <p>[AND]</p> <p>A wsm:TerminateSequence element MAY be sent by an RM Source to indicate it has completed its use of the Sequence</p> <p>[AND]</p> <p>The RM Source MUST NOT send wsm:TerminateSequence element as a header block</p> <p>[AND]</p> <p>Once wsm:TerminateSequence element is sent, other than this element, the RM Source MUST NOT send any additional message to the RM Destination referencing this Sequence</p> <p>[AND]</p> <p>The RM Source or RM Destination MUST include wsm: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</p> <p>[AND]</p> <p>/wsm:TerminateSequence/wsm: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.</p> |                      |                      |
+| <b>Applicability</b>     | C_SEN_000 AND C_SEN_WSI_021 AND C_SEN_WSI_033 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                      |                      |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                      |                      |
+| <b>Initial condition</b> | The HFS sender under test and the simulated HFS receiver are in the "Created" sequence state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                      |                      |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The HFS sender sends Sequence messages including an AckRequested element or indicating that it is the last message in the header block of the last message.</li> <li>The HFS receiver under test responds using a SequenceAcknowledgement header block, accepting all messages.</li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                      |                      |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>3. If the HFS sender under test sends a TerminateSequence element in the body of the message, the expected messages are:</p> <p>a. In the header block:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> wsa:Action = http://docs.oasis-open.org/ws-rx/wsrm/200702/TerminateSequence</li> <li><input type="checkbox"/> wsrm: TerminateSequence is not present.</li> </ul> <p>b. In the body of the message, within the TerminateSequence element:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> wsrm:Identifier value is an absolute URI of the terminating sequence.</li> <li><input type="checkbox"/> It is recommended that a LastMsgNumber element is present, and, if present, it must be equal to the LastMsgNumber of any CloseSequence message.</li> </ul> <p>4. If the HFS sender has sent a TerminateSequence element, the simulated HFS receiver responds with a TerminateSequenceResponse message, including its Identifier element as an absolute URI.</p> <p>5. Once the sequence is terminated, the HFS sender under test does not send any message referencing that terminated sequence.</p> |
+| <b>Pass/Fail criteria</b> | All elements are as specified within the test procedure above.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                      |                      |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------|
+| <b>TP Id</b>             | TP/HFS/SEN/WSI/RM/BV-006_B                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                      |                      |
+| <b>TP label</b>          | Sequence Termination Response                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                      |                      |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [OASIS WS-I RM]      |                      |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | WSAddress 1; M       | SeqTermination 10; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | SeqTermination 14; M | SeqTermination 15; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>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.</p> <p>[AND]</p> <p>Upon receipt of a TerminateSequence the RM Source MUST NOT send any additional messages (with the exception of the corresponding TerminateSequenceResponse) for this Sequence.</p> <p>[AND]</p> <p>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</p> <p>[AND]</p> <p>The responder (RM Source or RM Destination) MUST include this 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.</p> <p>[AND]</p> <p>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.</p> |                      |                      |
+| <b>Applicability</b>     | C_SEN_000 AND C_SEN_WSI_021 AND NOT(C_SEN_WSI_033) AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                      |                      |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                      |                      |
+| <b>Initial condition</b> | The HFS sender under test and the simulated HFS receiver are in the "Created" sequence state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                      |                      |
+| <b>Test procedure</b>    | <p>1. The HFS sender sends Sequence messages including an AckRequested element or indicating that it is the last message in the header block of the last message.</p> <p>2. The HFS receiver under test responds using a SequenceAcknowledgement header</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                      |                      |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>block, accepting all messages.</p> <p>3. The simulated HFS receiver sends a TerminateSequence element in the body of the message, with a correct LastMsgNumber.</p> <p>4. The HFS sender responds only with a message including:</p> <ol style="list-style-type: none"> <li>In the header block: <ul style="list-style-type: none"> <li><input type="checkbox"/> wsa:Action = http://docs.oasis-open.org/ws-rx/wsrn/200702/TerminateSequenceResponse</li> <li><input type="checkbox"/> wsrn: TerminateSequenceResponse is not present.</li> </ul> </li> <li>In the body of the message within the TerminateSequenceResponse element: <ul style="list-style-type: none"> <li><input type="checkbox"/> wsrn:Identifier element as an absolute URI of the terminating sequence.</li> </ul> </li> </ol> <p>5. Once the sequence is terminated, the HFS sender under test does not send any message referencing that terminated sequence.</p> |
+| <b>Pass/Fail criteria</b> | All elements are as specified within the test procedure above.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                  |                |                |
+|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|----------------|----------------|
+| <b>TP Id</b>         | TP/HFS/SEN/WSI/RM/BV-007                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                  |                |                |
+| <b>TP label</b>      | Sequences                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                  |                |                |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [OASIS WS-I RM]  |                |                |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ProtocolInv 1; M | Sequences 1; M | Sequences 2; M |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Sequences 3; M   | Sequences 5; M | Sequences 6; M |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Sequences 7; M   | Sequences 8; M |                |
+| <b>Test purpose</b>  | <p>Check that:</p> <p>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.</p> <p>[AND]</p> <p>The RM Source MUST include a Sequence header block in all messages for which reliable transfer is REQUIRED</p> <p>[AND]</p> <p>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</p> <p>[AND]</p> <p>The RM Source MUST NOT include more than one Sequence header block in any message</p> <p>[AND]</p> <p>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.</p> <p>[AND]</p> <p>An RM Source that includes a Sequence header block in a SOAP envelope MUST include wsrn:Identifier element in that header block</p> <p>[AND]</p> <p>The RM Source MUST set the value of wsrn:Identifier element to the absolute URI (conformant with RFC3986) that uniquely identifies the Sequence</p> <p>[AND]</p> <p>The RM Source MUST include wsrn:MessageNumber element within any Sequence headers it creates. This element is of type MessageNumberType.</p> |                  |                |                |
+| <b>Applicability</b> | C_SEN_000 AND C_SEN_WSI_021 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                  |                |                |
+| <b>Other PICS</b>    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                  |                |                |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b>  | The HFS sender under test and the simulated HFS receiver are in the "Created" sequence state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Wait until the HFS sender under test sends Sequence message/s including an AckRequested element or indicating that it is the last message in the last message header block.</li> <li>2. The expected message/s are: <ul style="list-style-type: none"> <li><input type="checkbox"/> wsrm:MessageNumber element is of type MessageNumberType and starts in 1 and increments by 1 in every sequential message.</li> <li><input type="checkbox"/> There is only one Sequence header block in each message.</li> <li><input type="checkbox"/> wsrm:Identifier element must be present in the header block and must be an absolute URI that uniquely identifies the sequence.</li> <li><input type="checkbox"/> mustUnderstand attribute = "1" or "true".</li> </ul> </li> <li>3. The simulated HFS receiver responds using a SequenceAcknowledgement header block accepting all messages received.</li> </ol> |
+| <b>Pass/Fail criteria</b> | All elements are as specified in step 2.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                 |                 |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------|
+| <b>TP Id</b>             | TP/HFS/SEN/WSI/RM/BV-010                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                 |                 |
+| <b>TP label</b>          | Unknown Sequence Fault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                 |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [OASIS WS-I RM] |                 |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | UnknownSeq 1; M | UnknownSeq 2; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Faults 1; R     | Faults 2; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                 | UnknownSeq 3; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                 | Faults 3; M     |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>UnknownSequence has the following properties:</p> <p>[Code] HFS Sender</p> <p>[Subcode] wsrm:UnknownSequence</p> <p>[Reason] The value of wsrm:Identifier is not a known Sequence identifier</p> <p>[Detail] &lt;wsrm:Identifier ...&gt; xs:anyURI &lt;/wsrm:Identifier&gt;</p> <p>[AND]</p> <p>An Endpoint MUST generate an UnknownSequence fault in response to a message containing an unknown or terminated Sequence identifier</p> <p>[AND]</p> <p>An Endpoint that receives an UnknownSequence fault MUST terminate the Sequence if not otherwise terminated</p> <p>[AND]</p> <p>Destinations that generate faults related to known sequences SHOULD transmit those faults.</p> <p>[AND]</p> <p>If transmitted, faults MUST be transmitted to the same [destination] as Acknowledgement messages</p> <p>[AND]</p> <p>Entities that generate WS-ReliableMessaging faults MUST include as the [action] property the default fault action IRI: <a href="http://docs.oasis-open.org/ws-rx/wsrm/200702/fault">http://docs.oasis-open.org/ws-rx/wsrm/200702/fault</a>.</p> |                 |                 |
+| <b>Applicability</b>     | C_SEN_000 AND C_SEN_WSI_021 AND C_SEN_WSI_034 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                 |                 |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                 |                 |
+| <b>Initial condition</b> | The HFS sender under test and the simulated HFS receiver are in the "None" sequence state. The simulated HFS receiver is able to send a CloseSequence message in the "None" sequence state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                 |                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated HFS receiver transmits a CloseSequence message with an unknown</li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                 |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>identifier.</p> <p>2. The HFS sender under test generates an UnknownSequence fault. It is recommended that the fault is transmitted to the HFS receiver.</p> <p>3. That message includes the following properties:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> wsa:Action = <a href="http://docs.oasis-open.org/ws-rx/wsrm/200702/fault">http://docs.oasis-open.org/ws-rx/wsrm/200702/fault</a></li> <li><input type="checkbox"/> Code = HFS Sender</li> <li><input type="checkbox"/> Subcode = wsrm:UnknownSequence</li> <li><input type="checkbox"/> Reason = The value if wsrm:Identifier is not a known Sequence identifier</li> <li><input type="checkbox"/> Detail = &lt;wsrm:Identifier...&gt; xs:anyURI &lt;/wsrm:Identifier&gt;.</li> </ul> |
+| <b>Pass/Fail criteria</b> | All elements are as specified in step 3.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                 |                 |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------|
+| <b>TP Id</b>             | TP/HFS/SEN/WSI/RM/BV-011                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                 |                 |
+| <b>TP label</b>          | Invalid Acknowledgement Fault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                 |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [OASIS WS-I RM] |                 |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | InvalidAck 1; M | InvalidAck 2; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | Faults 2; M     | Faults 3; M     |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>InvalidAcknowledgement fault has the following properties:</p> <p>[Code] HFS Sender</p> <p>[Subcode] wsrm:InvalidAcknowledgement</p> <p>[Reason] The SequenceAcknowledgement violates the cumulative Acknowledgement invariant.</p> <p>[Detail] &lt;wsrm:SequenceAcknowledgement ...&gt; ... &lt;/wsrm:SequenceAcknowledgement&gt;</p> <p>[AND]</p> <p>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.</p> <p>[AND]</p> <p>Destinations that generate faults related to known sequences SHOULD transmit those faults.</p> <p>[AND]</p> <p>If transmitted, faults MUST be transmitted to the same [destination] as Acknowledgement messages</p> <p>[AND]</p> <p>Entities that generate WS-ReliableMessaging faults MUST include as the [action] property the default fault action IRI: <a href="http://docs.oasis-open.org/ws-rx/wsrm/200702/fault">http://docs.oasis-open.org/ws-rx/wsrm/200702/fault</a>.</p> |                 |                 |
+| <b>Applicability</b>     | C_SEN_000 AND C_SEN_WSI_021 AND C_SEN_WSI_034 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                 |                 |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                 |                 |
+| <b>Initial condition</b> | The HFS sender under test and the simulated HFS receiver are in the "Created" sequence state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                 |                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The HFS sender under test starts to send Sequence messages with their respective message number.</li> <li>2. Wait until the HFS sender sends an AckRequested element or indicates that the message is the last one.</li> <li>3. The simulated HFS receiver responds with a SequenceAcknowledgement with an AckRange, a None and a Nack element.</li> <li>4. The HFS sender generates an InvalidAcknowledgement fault. It is recommended that the</li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                 |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>fault is transmitted to the HFS receiver.</p> <p>5. That message includes the following properties:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> wsa:Action = http://docs.oasis-open.org/ws-rx/wsrm/200702/fault</li> <li><input type="checkbox"/> Code = HFS Sender</li> <li><input type="checkbox"/> Subcode = wsrm:InvalidAcknowledgement</li> <li><input type="checkbox"/> Reason = &lt;any&gt;</li> <li><input type="checkbox"/> Detail = &lt;any related to the message that produces the fault&gt;.</li> </ul> |
+| <b>Pass/Fail criteria</b> | All elements are as specified in step 5.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                  |                      |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|
+| <b>TP Id</b>              | TP/HFS/SEN/WSI/RM/BV-012                                                                                                                                                                                                                                                                                                                                         |                      |
+| <b>TP label</b>           | Message Number Rollover                                                                                                                                                                                                                                                                                                                                          |                      |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                      | [OASIS WS-I RM]      |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                            | MessageNumrRoll 4; R |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>RM Source SHOULD continue to retransmit undelivered messages until the Sequence is closed or terminated.</p>                                                                                                                                                                                                                               |                      |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_WSI_021 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                    |                      |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                  |                      |
+| <b>Initial condition</b>  | <p>The HFS sender under test and the simulated HFS receiver are in the "Created" sequence state. The simulated HFS receiver is able to send a MessageNumberRollover fault instead of a SequenceAcknowledgement message.</p>                                                                                                                                      |                      |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The HFS sender under test transmits a Sequence message.</li> <li>2. The simulated HFS receiver generates a MessageNumberRollover fault, which is transmitted to the HFS sender.</li> <li>3. The HFS sender should retransmit undelivered messages until the HFS receiver closes or terminates the sequence.</li> </ol> |                      |
+| <b>Pass/Fail criteria</b> | The HFS sender should retransmit undelivered messages in step 3.                                                                                                                                                                                                                                                                                                 |                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                  |                      |
+
+|                          |                                                                                                                                                                                                                                                                                                     |                 |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|
+| <b>TP Id</b>             | TP/HFS/SEN/WSI/RM/BV-012_A                                                                                                                                                                                                                                                                          |                 |
+| <b>TP label</b>          | Create Sequence Refused                                                                                                                                                                                                                                                                             |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                         | [OASIS WS-I RM] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                               | SeqRefused 3; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The Action Upon Reception is Sequence Terminated when the HFS receiver does not wish to create a new Sequence.</p>                                                                                                                                                            |                 |
+| <b>Applicability</b>     | C_SEN_000 AND C_SEN_WSI_021 AND C_SEN_GEN_003                                                                                                                                                                                                                                                       |                 |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                     |                 |
+| <b>Initial condition</b> | <p>The HFS sender under test and the simulated HFS receiver are in the "None" sequence state. The simulated HFS receiver is able to send a CreateSequenceRefused fault instead of a CreateSequenceResponse message.</p>                                                                             |                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Wait until the HFS sender under test sends a CreateSequence message to the simulated HFS receiver.</li> <li>2. The simulated HFS receiver responds with a CreateSequenceRefused fault.</li> <li>3. The HFS sender must terminate the sequence.</li> </ol> |                 |
+
+|                           |                                                                                        |
+|---------------------------|----------------------------------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | The HFS sender terminates the sequence when it receives a CreateSequenceRefused fault. |
+| <b>Notes</b>              |                                                                                        |
+
+|                           |                                                                                                                                                                                                                                                                                                                          |                     |  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|--|
+| <b>TP Id</b>              | TP/HFS/SEN/WSI/RM/BV-012_B                                                                                                                                                                                                                                                                                               |                     |  |
+| <b>TP label</b>           | Sequence Closed Fault                                                                                                                                                                                                                                                                                                    |                     |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                              | [OASIS WS-I RM]     |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                    | SeqClosedFault 3; M |  |
+| <b>Test purpose</b>       | Check that:<br>The Action Upon Reception is Sequence Closed                                                                                                                                                                                                                                                              |                     |  |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_WSI_021 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                            |                     |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                          |                     |  |
+| <b>Initial condition</b>  | The HFS sender under test and the simulated HFS receiver are in the CreatedSequence state. The simulated HFS receiver is able to send a SequenceClosed fault instead of a SequenceAcknowledgement message.                                                                                                               |                     |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The HFS sender under test sends a sequence to the simulated HFS receiver sending an AckRequested message or indicating that it is the last message.</li> <li>The simulated HFS receiver sends a SequenceClosed fault.</li> <li>The HFS sender must close the sequence.</li> </ol> |                     |  |
+| <b>Pass/Fail criteria</b> | The HFS sender closes the sequence when it receives a SequenceClosed fault.                                                                                                                                                                                                                                              |                     |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                          |                     |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                           |                 |                |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----------------|
+| <b>TP Id</b>              | TP/HFS/SEN/WSI/RM/BV-015                                                                                                                                                                                                                                                                                                  |                 |                |
+| <b>TP label</b>           | Securing Sequences Using WS-Security                                                                                                                                                                                                                                                                                      |                 |                |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                               | [OASIS WS-I RM] |                |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                     | SecSeqWSS 5; R  | SecSeqWSS 6; R |
+| <b>Test purpose</b>       | Check that:<br>The RM Source SHOULD include the UsesSequenceSTR element as a SOAP header block within the CreateSequence message. This element MUST include a soap:mustUnderstand attribute with a value of "true".                                                                                                       |                 |                |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_WSI_021 AND C_SEN_WSI_003 AND C_SEN_GEN_003                                                                                                                                                                                                                                                           |                 |                |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                           |                 |                |
+| <b>Initial condition</b>  | The HFS sender under test and the simulated HFS receiver are in the "None" sequence state.                                                                                                                                                                                                                                |                 |                |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>Wait until the HFS sender under test sends a CreateSequence message.</li> <li>It is recommended that the received message includes a UsesSequenceSTR element in the header block. If the element is included, it MUST include a soap:mustUnderstand attribute = "true".</li> </ol> |                 |                |
+| <b>Pass/Fail criteria</b> | The recommended element in step 2 is as specified within the test procedure above.                                                                                                                                                                                                                                        |                 |                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                           |                 |                |
+
+|                 |                                  |                    |                    |
+|-----------------|----------------------------------|--------------------|--------------------|
+| <b>TP Id</b>    | TP/HFS/SEN/WSI/RM/BV-016         |                    |                    |
+| <b>TP label</b> | Securing Sequences Using SSL/TLS |                    |                    |
+| <b>Coverage</b> | <b>Spec</b>                      | [OASIS WS-I RM]    |                    |
+|                 | <b>Testable items</b>            | SecSeqSSL/TLS 1; M | SecSeqSSL/TLS 2; O |
+|                 |                                  |                    | SecSeqSSL/TLS 3; M |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>       | <p>Check that:</p> <p>If the RM Source wishes to bind a Sequence to the underlying SSL/TLS sessions(s) it MUST include the UsesSequenceSSL element as a SOAP header block within the CreateSequence message.</p> <p>[AND]</p> <p>The RM Source MAY include wsrn:UsesSequenceSSL element as a SOAP header block of a CreateSequence message to indicate to the RM Destination that the resulting Sequence is to be bound to the TLS session that was used to carry the CreateSequence message</p> <p>[AND]</p> <p>If wsrn:UsesSequenceSSL element is included, the RM Source MUST mark this header with a soap:mustUnderstand attribute with a value of "true".</p> |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_WSI_021 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Initial condition</b>  | The HFS sender under test and the simulated HFS receiver are in the "None" sequence state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Wait until the HFS sender under test sends a CreateSequence message.</li> <li>2. If the HFS sender binds a sequence to the underlying SSL/TLS sessions(s) it includes the UsesSequenceSSL element as a SOAP header block within the CreateSequence message, with a soap:mustUnderstand attribute = "true".</li> </ol>                                                                                                                                                                                                                                                                                                    |
+| <b>Pass/Fail criteria</b> | If the HFS sender binds the sequence to the underlying TSL session, elements are as specified in step 2.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+# 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*.  
+<https://docbox.etsi.org/MTS/MTS/10-PromotionalMaterial/MBS-20111118/Referenced%20Documents/Drafting%20Rules.pdf>
+- [b-HFSR PICS & PIXIT] Services HFS Receiver DG2016 PICS and PIXIT excel sheet v1.7  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-HFSS PICS & PIXIT] Services HFS Sender DG2016 PICS and PIXIT excel sheet v1.7  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-SOAP 1.2] W3C SOAP 1.2 (2007), *SOAP Version 1.2 (Second Edition)*.  
+<http://www.w3.org/TR/soap>
+
+
+
+# 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg b/marked/H/T-REC-H.830.2-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ca0dce65df64f4fb10a81b8f87284f793e4b1d3d
--- /dev/null
+++ b/marked/H/T-REC-H.830.2-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.5-201704-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.830.5-201704-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426
--- /dev/null
+++ b/marked/H/T-REC-H.830.5-201704-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.830.6-201704-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.830.6-201704-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426
--- /dev/null
+++ b/marked/H/T-REC-H.830.6-201704-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.830.6-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.830.6-201704-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..761344dcd19adaf68734439159d0d6fb5ddf4330
--- /dev/null
+++ b/marked/H/T-REC-H.830.6-201704-I_PDF-E/raw.md
@@ -0,0 +1,2750 @@
+
+
+**ITU-T**
+
+**H.830.6**
+
+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 6: PCD-01 HL7  
+messages: Health & Fitness Service receiver**
+
+Recommendation ITU-T H.830.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        |
+| 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        |
+| <b>Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN)</b> | <b>H.820–H.859</b> |
+| 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.6
+
+## Conformance of ITU-T H.810 personal health system: Services interface Part 6: PCD-01 HL7 messages: Health & Fitness Service receiver
+
+## Summary
+
+Recommendation ITU-T H.830.6 provides a test suite structure (TSS) and the test purposes (TP) for PCD-01 HL7 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.6 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Services Interface; Part 6: PCD-01 HL7 Messages. HFS Receiver (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.836                 | 2015-01-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/12254">11.1002/1000/12254</a> |
+| 1.0     | ITU-T H.830.6               | 2015-01-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/12592">11.1002/1000/12592</a> |
+| 2.0     | ITU-T H.830.6               | 2016-07-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12927">11.1002/1000/12927</a> |
+| 3.0     | ITU-T H.830.6               | 2017-04-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/13213">11.1002/1000/13213</a> |
+| 3.1     | ITU-T H.830.6 (2017) Cor. 1 | 2017-11-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/13425">11.1002/1000/13425</a> |
+
+## Keywords
+
+Conformance testing, Continua Design Guidelines, e-health, ITU-T H.810, PCD-01 HL7 messages, personal connected health devices, Health & Fitness Service receiver, Services interface.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 2.4.1: General (GEN).....                                      | 8  |
+| A.3     | Subgroup 2.4.2: Design guidelines (DG) .....                            | 33 |
+| A.4     | Subgroup 2.4.3: Pulse oximeter (PO).....                                | 33 |
+| A.5     | Subgroup 2.4.4: Blood pressure monitor (BPM).....                       | 36 |
+| A.6     | Subgroup 2.4.5: Thermometer (TH).....                                   | 39 |
+| A.7     | Subgroup 2.4.6: Weighing scales (WEG) .....                             | 42 |
+| A.8     | Subgroup 2.4.7: Glucose meter (GL) .....                                | 45 |
+| A.9     | Subgroup 2.4.8: Cardiovascular fitness and activity monitor (CV) .....  | 48 |
+| A.10    | Subgroup 2.4.9: Strength fitness equipment (ST) .....                   | 51 |
+| A.11    | Subgroup 2.4.10: Independent living activity hub (HUB) .....            | 54 |
+| A.12    | Subgroup 2.4.11: Adherence monitor (AM) .....                           | 57 |
+| A.13    | Subgroup 2.4.12: Peak expiratory flow monitor (PF) .....                | 60 |
+| A.14    | Subgroup 2.4.13: Body composition analyser (BCA).....                   | 63 |
+| A.15    | Subgroup 2.4.14: Basic electrocardiograph (ECG).....                    | 66 |
+| A.16    | Subgroup 2.4.15: International normalized ratio (INR) .....             | 69 |
+| A.17    | Subgroup 2.4.16: Sleep apnoea breathing therapy equipment (SABTE) ..... | 73 |
+| A.18    | Subgroup 2.4.17: Insulin pump (IP) .....                                | 76 |
+| A.19    | Subgroup 2.4.18: Continuous glucose monitor (CGM) .....                 | 79 |
+|         | Bibliography.....                                                       | 83 |
+
+**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, Services Interface; Part 6: PCD-01 HL7 Messages. HFS Receiver (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_6_(REC 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_6_(REC PCD-01)_v1.2" as baseline and adds new features included in [b-CDG 2012]: <ul style="list-style-type: none"> <li>• Adds glucose meter new spec version</li> <li>• Adds body composition analyser device specialization</li> <li>• Adds basic electrocardiograph device specialization</li> </ul>                                                                                 |
+| 1.4     | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_WAN_PART_6_(REC PCD-01)_v1.3.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]: <ul style="list-style-type: none"> <li>• Adds glucose meter BLE</li> <li>• Adds BLE SSP support</li> <li>• Adds NFC new transport</li> <li>• Adds INR device specialization</li> </ul>                                                                                    |
+| 1.5     | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_WAN_PART_6_(REC PCD-01)_v1.4.doc" as a baseline and it adds new features included in Documentation Enhancements: <ul style="list-style-type: none"> <li>• "Other PICS" row has been added</li> </ul>                                                                                                                                                                  |
+| 1.6     | 2015-07-01 | Initial release for Test Tool DG2015. It uses "TSS&TP_DG2011_WAN_PART_6_(REC PCD-01)_v1.5" as a baseline and adds new features included in Continua DG 2015: <ul style="list-style-type: none"> <li>• Changes in test suite structure</li> <li>• Added international normalized ratio device specialization</li> <li>• Added sleeping apnoea breathing therapy equipment device specialization</li> <li>• Added support for hData Observation Upload</li> </ul> |
+| 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.6
+
+## Conformance of ITU-T H.810 personal health system: Services interface Part 6: PCD-01 HL7 messages: Health & Fitness Service receiver
+
+## 1 Scope
+
+The scope of this Recommendation<sup>1</sup> 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 6.
+
+- 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*.
+
+---
+
+<sup>1</sup> 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                    |
+| ATS   | Abstract Test Suite                           |
+| ATNA  | Audit Trail and Node Authentication           |
+| 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             |
+| 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                  |
+| 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                  |
+| TLS   | Transport Level Security                              |
+| TP    | Test Purpose                                          |
+| TSS   | Test Suite Structure                                  |
+| USB   | Universal Serial Bus                                  |
+| URI   | Uniform Resource Identifier                           |
+| 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.4.1 to 2.4.16 (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 <http://handle.itu.int/11.1002/2000/12067>.
+
+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>/<DUT>/<GR>/<SGR>/<XX> – <NNN>). It is specified according to the naming convention defined below:
+  - Each test purpose identifier is introduced by the prefix "TP".
+  - <TT>: This is the test tool that will be used in the test case.
+    - HFS: Health & Fitness Services Interface
+  - <DUT>: This is the device under test.
+    - SEN: HFS sender
+    - REC: HFS receiver
+  - <GR>: This identifies a group of test cases.
+  - <SGR>: This identifies a subgroup of test cases.
+  - <XX>: This identifies the type of testing.
+    - BV: Valid behaviour test
+    - BI: Invalid behaviour test
+  - <NNN>: 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.4.1: General (GEN)
+
+|                 |                                   |
+|-----------------|-----------------------------------|
+| <b>TP Id</b>    | TP/HFS/REC/PCD-01-DATA/GEN/BV-000 |
+| <b>TP label</b> | MSH Segment                       |
+
+|                          |                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                     |                       |
+|--------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|-----------------------|
+| <b>Coverage</b>          | <b>Spec</b>           | [ITU-T H.812.1]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                     |                       |
+|                          | <b>Testable items</b> | MSH-1; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | MSH-2; M            | MSH-3; M              |
+|                          |                       | MSH-4; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | MSH-5; M            | MSH-6; M              |
+|                          |                       | MSH-7; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | MSH-8; M            | MSH-9; M              |
+|                          |                       | MSH-10; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | MSH-11; M           | MSH-12; M             |
+|                          |                       | MSH-13; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | MSH-14; M           | MSH-15; M             |
+|                          |                       | MSH-16; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | MSH-17; M           | MSH-18; M             |
+|                          |                       | MSH-19; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | MSH-20; M           | MSH-21; M             |
+|                          |                       | MSH-22; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | MSH-23; M           | MSH-24; M             |
+|                          |                       | MSH-25; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | HL7Concept 2; M     | CWEDataType 1; M      |
+|                          |                       | CWEDataType 2; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | CWEDataType 3; C    | DateTimeDataType 1; M |
+|                          |                       | NumericDataType 1; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | StringDataType 1; M | IDDataType 1; M       |
+|                          |                       | ISDataType 1; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | EIDataType 1; M     | EIDataType 2; O       |
+|                          |                       | EIDataType 3; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | EIDataType 4; O     | EIUse1; C             |
+|                          |                       | EIUse2; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | EIUse3; C           | EIUse4; C             |
+|                          | <b>Spec</b>           | [IHE PCD-TF-2]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                     |                       |
+|                          | <b>Testable items</b> | HDUse1; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | HDUse2; C           | HDUse3; C             |
+|                          |                       | HD-1; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | HD-2; M             | HD-3; M               |
+| <b>Test purpose</b>      |                       | Check that:<br>The elements of the MSH segment of a message<br>[AND]<br>The data type of each element.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                     |                       |
+| <b>Applicability</b>     |                       | C_REC_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                     |                       |
+| <b>Other PICS</b>        |                       | C_REC_DATA_001, C_REC_DATA_002, C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                     |                       |
+| <b>Initial condition</b> |                       | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                     |                       |
+| <b>Test procedure</b>    |                       | <ol style="list-style-type: none"> <li>1. The simulated HFS sender sends an HL7 message inside a SOAP body including an observation.</li> <li>2. The HFS receiver under test responds using another HL7 message. Check in the captured message that: <ol style="list-style-type: none"> <li>a. Only one MSH segment is present and: <ul style="list-style-type: none"> <li><li><input type="checkbox"/> The character ' ' is the separator element.</li></li> <li><li><input type="checkbox"/> MSH-2 = ^~\&amp; (for Encoding characters element).</li></li> <li><li><input type="checkbox"/> MSH-3 = &lt;Namespace ID (data type IS)&gt;^&lt;Universal ID (data type ST)&gt;^&lt;Universal Type (data type ID)&gt; <ul style="list-style-type: none"> <li>• If C_REC_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</li> <li>• If C_REC_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</li> <li>• Otherwise, if Universal Type (HD-3) is valued, it takes one of the following values:</li> </ul> </li></li> </ul> </li> </ol> </li> </ol> |                     |                       |
+
+- 'DNS' - An Internet dotted name. Either in ASCII or as integers.
+- 'GUID' - is the 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, MSH-6 may be empty, but if they are not empty, they have the same encoding as MSH-3.
+- MSH-7 is encoded as YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ].
+- MSH-8 is empty
+- MSH-9 = ACK^R01^ACK
+- MSH-10 is a string (that uniquely identifies the message)
+- MSH-11 = <Processing ID (data type ID)>^<Processing Mode (data type ID)>  
+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'
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• '8859/5'</li> <li>• '8859/6'</li> <li>• '8859/7'</li> <li>• '8859/8'</li> <li>• '8859/9'</li> <li>• '8859/15'</li> <li>• 'ISO IR14'</li> <li>• 'ISO IR87'</li> <li>• 'ISO IR159'</li> <li>• 'GB 18030-2000'</li> <li>• 'KS X 1001'</li> <li>• 'CNS 11643-1992'</li> <li>• 'BIG-5'</li> <li>• 'UNICODE'</li> <li>• 'UNICODE UTF-8'</li> <li>• 'UNICODE UTF-16'</li> <li>• 'UNICODE UTF-32'</li> </ul> <p><input type="checkbox"/> MSH-19 may be empty, but if it is valued, it is encoded as CWE data type:<br/> <i>&lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt;Name of Coding System (ID)&gt; ^&lt;Alternate Identifier (ST)&gt;^&lt;Alternate Text (ST)&gt;^&lt;Name of Alternate Coding System (ID)&gt;^&lt;Coding System Version ID (ST)&gt;^&lt;Alternate Coding System Version ID (ST)&gt;^&lt;Original Text (ST)&gt;</i></p> <p>where CWE-1 is required, CWE-2 to CWE-6 are required but may be empty and the rest can be present.</p> <p><input type="checkbox"/> MSH-20 is empty</p> <p><input type="checkbox"/> MSH-21 = <i>&lt;Entity Identifier (data type ST)&gt; ^ &lt;Namespace ID (data type IS)&gt; ^ &lt;Universal ID (data type ST)&gt; ^ &lt;Universal ID Type (data type ID)&gt;</i>, where NamespaceID and UniversalID are 'HL7'</p> <p><input type="checkbox"/> MSH-22, MSH-23, MSH-24, MSH-25 are empty</p> |
+| <b>Pass/Fail criteria</b> | In step 2, all elements are as specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                 |                                   |                       |                      |
+|-----------------|-----------------------------------|-----------------------|----------------------|
+| <b>TP Id</b>    | TP/HFS/REC/PCD-01-DATA/GEN/BV-001 |                       |                      |
+| <b>TP label</b> | MSA and Segment Sequence Error    |                       |                      |
+| <b>Coverage</b> | <b>Spec</b>                       | [ITU-T H.812.1]       |                      |
+|                 | <b>Testable items</b>             | MSAUse; M             | MSA-1; M             |
+|                 |                                   | MSA-3; M              | MSA-4; M             |
+|                 |                                   | MSA-6; M              | MSA-7; M             |
+|                 |                                   | ERRUse 1; O           | ERRUse 2; M          |
+|                 |                                   | ERR-2; R              | ERR-3; M             |
+|                 |                                   | ERR-5; M              | ERR-6; M             |
+|                 |                                   | CWEDataType 1; M      | CWEDataType 2; M     |
+|                 |                                   | CWEDataType 4; R      | NumericDataType 1; M |
+|                 |                                   | DateTimeDataType 1; M | EIDataType 1; M      |
+|                 |                                   | EIDataType 3; M       | EIDataType 4; M      |
+|                 |                                   |                       | EIUse1; C            |
+
+|                          |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                  |                   |
+|--------------------------|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-------------------|
+|                          |  | EIUse2; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | EIUse3; C        | EIUse4; C         |
+|                          |  | 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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                  |                   |
+| <b>Test purpose</b>      |  | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                  |                   |
+| <b>Applicability</b>     |  | C_REC_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                  |                   |
+| <b>Other PICS</b>        |  | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                  |                   |
+| <b>Initial condition</b> |  | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                  |                   |
+| <b>Test procedure</b>    |  | 1. The simulated HFS sender sends the following HL7 message without an MSH segment inside a SOAP body to make the HFS receiver respond with another HL7 message:<br>PID   789567^^^Imaginary Hospital^PI  Doe^John^Joseph^^^L<br>OBR 1 POTest^AT4_AHD^1234567890ABCDEF^EUI-64 POTest^AT4_AHD^1234567890ABCDEF^EUI-64 182777000^monitoring of patient^SNOMED-CT   20100813095715+0000<br>OBX 1 531981^MDC_MOC_VMS_MDS_AHD^MDC 0     X     FEEDABEEDEADBE EF^EUI-64<br>OBX 2 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.1 2^auth-body-continua     R<br>OBX 3 ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 0.0.0.1.1 6.1     R<br>OBX 4 NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 0.0.0.1.2 8196~16388     R<br>OBX 5 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.2 2^auth-body-continua     R<br>OBX 6 CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC 0.0.0.2.1 1^unregulated-device(0)     R<br>OBX 7 CWE 68220^MDC_TIME_SYNC_PROTOCOL^MDC 0.0.0.3 532224^MDC_TIME_SYNC_NONE^MDC     R<br>OBX 8 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.4 2^auth-body-continua     R<br>OBX 9 CWE 64515^MDC_REG_CERT_DATA_CONTINUA_AHD_CERT_LIST^MDC 0.0.0.4.1 0~1     R<br>OBX 10 528388^MDC_DEV_SPEC_PROFILE_PULS_OXIM^MDC 1     X     1234567890ABCDEF^EUI-64<br>OBX 11 ST 531969^MDC_ID_MODEL_NUMBER^MDC 1.0.0.1 PulseOx v1. 5     R<br>OBX 12 ST 531970^MDC_ID_MODEL_MANUFACTURER^MDC 1.0.0.2 AT4 Wireless     R<br>OBX 13 DTM 67975^MDC_ATTR_TIME_ABS^MDC 1.0.0.3 20100813095715+0000     R   20100813095715+0000<br>OBX 14 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.4 2^auth-body-continua     R<br>OBX 15 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.5 2^auth-body-continua     R |                  |                   |
+
+OBX|16|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.4.1|1.5|||||R
+
+OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|1.0.0.4.2|16388|||||R
+
+OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.0.0.5.1|0^unregulated-device(0)|||||R
+
+OBX|19|NM|150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC|1.0.0.8|80.5|262688^MDC\_DI\_M\_PERCENT^MDC|||||R||20100813095715+0000
+
+OBX|20|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|1.0.0.9|70|264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC|||||R||20100813095715+0000
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+- a. Only one MSA segment is present and:
+    - MSA-1 is 'AE' – Accept Acknowledgment: Application Error
+    - MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+    - MSA-3 to MSA-8 are empty
+  - b. If the ERR segment referring to the MSA is present:
+    - ERR-1 is empty
+    - ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>
+    - ERR-3 starts with the error code '100', other optional subfields might be included
+    - ERR-4 is set to:
+      - 'E' – Error
+    - ERR-5 and ERR-6 are empty
+    - ERR-7 may be empty, but if it is valued, it is a text data
+    - ERR-8 may be empty, but if it is valued, it is a text data
+    - ERR-9 may be empty, but if it is valued, it is one of these values:
+      - 'PAT'
+      - 'NPAT'
+      - 'USR'
+      - 'HD'
+    - ERR-10 may be empty, but if it is valued, it is encoded as: <Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+    - ERR-11 may be empty, but if it is valued, it is encoded as: <Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+    - ERR-12 may be empty, but if it is valued, it is encoded as: <WITHDRAWN Constituent> ^ <Telecommunication Use Code (ID)> ^ <Telecommunication Equipment Type (ID)> ^ <Communication Address (ST)> ^ <Country Code (NM)> ^ <Area/City Code (NM)> ^ <Local Number (NM)> ^ <Extension (NM)> ^ <Any Text (ST)> ^ <Extension Prefix (ST)> ^ <Speed Dial Code (ST)> ^ <Unformatted Telephone Number (ST)> ^ <Effective Start Date (DTM)> ^ <Expiration Date (DTM)> ^ <Expiration Reason (CWE)> ^ <Protection Code (CWE)> ^ <Shared Telecommunication Identifier (EI)> ^ <Preference Order (NM)>
+
+Where:
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• Expiration Reason subcomponents are: &lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt;Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</li> <li>• Protection code subcomponents are: &lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt;Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</li> <li>• Shared Telecommunication Identifier subcomponents are: &lt;Entity Identifier (ST)&gt;&amp;&lt;Namespace ID (IS)&gt;&amp;&lt;Universal ID (ST)&gt;&amp;&lt;Universal ID Type (ID)&gt;</li> </ul> <p>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.</p> |
+| <b>Pass/Fail criteria</b> | In step2, all elements in each segment are as specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|                          |                                                                                                                                                                                       |                       |                      |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|
+| <b>TP Id</b>             | TP/HFS/REC/PCD-01-DATA/GEN/BV-002                                                                                                                                                     |                       |                      |
+| <b>TP label</b>          | MSA and Required Field Missing Error                                                                                                                                                  |                       |                      |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                           | [ITU-T H.812.1]       |                      |
+|                          | <b>Testable items</b>                                                                                                                                                                 | MSAUse; M             | MSA-1; M             |
+|                          |                                                                                                                                                                                       | MSA-3; M              | MSA-4; M             |
+|                          |                                                                                                                                                                                       | MSA-6; M              | MSA-7; M             |
+|                          |                                                                                                                                                                                       | ERRUse 1; O           | ERRUse 2; M          |
+|                          |                                                                                                                                                                                       | ERR-2; R              | ERR-3; M             |
+|                          |                                                                                                                                                                                       | ERR-5; M              | ERR-6; M             |
+|                          |                                                                                                                                                                                       | CWEDataType 1; M      | CWEDataType 2; M     |
+|                          |                                                                                                                                                                                       | CWEDataType 4; R      | NumericDataType 1; M |
+|                          |                                                                                                                                                                                       | DateTimeDataType 1; M | EIDataType 1; M      |
+|                          |                                                                                                                                                                                       | EIDataType 3; M       | EIDataType 4; M      |
+|                          |                                                                                                                                                                                       | EIUse2; C             | EIUse3; C            |
+|                          |                                                                                                                                                                                       | IDDataType 1; M       | ISDataType 1; M      |
+|                          |                                                                                                                                                                                       | XTNDataType 2; M      | XTNDataType 3; M     |
+|                          |                                                                                                                                                                                       | XTNDataType 5; M      | XTNDataType 6; M     |
+|                          |                                                                                                                                                                                       | XTNDataType 8; M      | XTNDataType 9; M     |
+|                          |                                                                                                                                                                                       | XTNDataType 11; M     |                      |
+| <b>Test purpose</b>      | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                |                       |                      |
+| <b>Applicability</b>     | C_REC_000                                                                                                                                                                             |                       |                      |
+| <b>Other PICS</b>        | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                        |                       |                      |
+| <b>Initial condition</b> | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation.                                              |                       |                      |
+| <b>Test procedure</b>    | 1. The simulated HFS sender sends the following HL7 message with an MSH segment including a MSH-7 empty inside a SOAP body to make the HFS receiver respond with another HL7 message: |                       |                      |
+
+MSH|^~\&|AT4\_AHD^1234567890ABCDEF^EUI-  
+ 64|||||ORU^R01^ORU\_R01|MSGID12|P|2.6|||NE|AL|||||HE PCD ORU-  
+ R012006^HL7^2.16.840.1.113883.9.n.m^HL7
+
+PID|||789567^^^Imaginary Hospital^P|||Doe^John^Joseph^^^L
+
+OBR|1|POTest^AT4\_AHD^1234567890ABCDEF^EUI-  
+ 64|POTest^AT4\_AHD^1234567890ABCDEF^EUI-64|182777000^monitoring of  
+ patient^SNOMED-CT|||20100813095715+0000
+
+OBX|1||531981^MDC\_MOC\_VMS\_MDS\_AHD^MDC|0|||||X|||||FEEDABEEDEADBE  
+EF^EUI-64
+
+OBX|2|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.1|2^auth-  
+body-continua|||||R
+
+OBX|3|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|0.0.0.1.1|  
+6.1|||||R
+
+OBX|4|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|0.  
+0.0.1.2|8196~16388|||||R
+
+OBX|5|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.2|2^auth-  
+body-continua|||||R
+
+OBX|6|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|0.0  
+.0.2.1|1^unregulated-device(0)|||||R
+
+OBX|7|CWE|68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC|0.0.0.3|532224^MDC\_TIM  
+E\_SYNC\_NONE^MDC|||||R
+
+OBX|8|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.4|2^auth-  
+body-continua|||||R
+
+OBX|9|CWE|64515^MDC\_REG\_CERT\_DATA\_CONTINUA\_AHD\_CERT\_LIST^MDC|0  
+.0.0.4.1|0~1|||||R
+
+OBX|10||528388^MDC\_DEV\_SPEC\_PROFILE\_PULS\_OXIM^MDC|1|||||X|||||123456  
+7890ABCDEF^EUI-64
+
+OBX|11|ST|531969^MDC\_ID\_MODEL\_NUMBER^MDC|1.0.0.1|PulseOx v1. 5|||||R
+
+OBX|12|ST|531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC|1.0.0.2|AT4  
+Wireless|||||R
+
+OBX|13|DTM|67975^MDC\_ATTR\_TIME\_ABS^MDC|1.0.0.3|20100813095715+0000|||  
+R||20100813095715+0000
+
+OBX|14|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.4|2^auth-  
+body-continua|||||R
+
+OBX|15|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.5|2^auth-  
+body-continua|||||R
+
+OBX|16|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.4.1  
+|1.5|||||R
+
+OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|  
+1.0.0.4.2|16388|||||R
+
+OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.  
+0.0.5.1|0^unregulated-device(0)|||||R
+
+OBX|19|NM|150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC|1.0.0.8|90|262688^MDC\_DIM  
+\_PERCENT^MDC|||||R||20100813095715+0000
+
+OBX|20|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|1.0.0.9|80|264864^MDC  
+\_DIM\_BEAT\_PER\_MIN^MDC|||||R||20100813095715+0000
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+- a. Only one MSA segment is present and:
+    - MSA-1 is 'AE' – Accept Acknowledgment: Application Error
+    - MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+    - MSA-3 to MSA-8 are empty
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>b. If the ERR segment referring to the MSA is present:</p> <ul style="list-style-type: none"><li><input type="checkbox"/> ERR-1 is empty</li><li><input type="checkbox"/> ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <i>&lt;Segment ID (ST)&gt; ^ &lt;Segment Sequence (NM)&gt; ^ &lt;Field Position (NM)&gt; ^ &lt;Field Repetition (NM)&gt; ^ &lt;Component Number (NM)&gt; ^ &lt;Sub-Component Number (NM)&gt;</i></li><li><input type="checkbox"/> ERR-3 starts with the error code '101', other optional subfields might be included</li><li><input type="checkbox"/> ERR-4 is set to:<ul style="list-style-type: none"><li>• 'E' – Error</li></ul></li><li><input type="checkbox"/> ERR-5 and ERR-6 are empty</li><li><input type="checkbox"/> ERR-7 may be empty, but if it is valued, it is a text data</li><li><input type="checkbox"/> ERR-8 may be empty, but if it is valued, it is a text data</li><li><input type="checkbox"/> ERR-9 may be empty, but if it is valued, it is one of these values:<ul style="list-style-type: none"><li>• 'PAT'</li><li>• 'NPAT'</li><li>• 'USR'</li><li>• 'HD'</li></ul></li><li><input type="checkbox"/> ERR-10 may be empty, but if it is valued, it is encoded as: <i>&lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt; Name of Coding System (ID)&gt;</i> the rest of the elements of the CWE data type are not used in the Services interface.</li><li><input type="checkbox"/> ERR-11 may be empty, but if it is valued, it is encoded as: <i>&lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt; Name of Coding System (ID)&gt;</i> the rest of the elements of the CWE data type are not used in the Services interface.</li><li><input type="checkbox"/> ERR-12 may be empty, but if it is valued, it is encoded as: <i>&lt;WITHDRAWN Constituent&gt;^&lt;Telecommunication Use Code (ID)&gt;^&lt;Telecommunication Equipment Type (ID)&gt;^&lt;Communication Address (ST)&gt;^&lt;Country Code (NM)&gt;^&lt;Area/City Code (NM)&gt;^&lt;Local Number (NM)&gt;^&lt;Extension (NM)&gt;^&lt;Any Text (ST)&gt;^&lt;Extension Prefix (ST)&gt;^&lt;Speed Dial Code (ST)&gt;^&lt;Unformatted Telephone Number (ST)&gt;^&lt;Effective Start Date (DTM)&gt;^&lt;Expiration Date (DTM)&gt;^&lt;Expiration Reason (CWE)&gt;^&lt;Protection Code (CWE)&gt;^&lt;Shared Telecommunication Identifier (EI)&gt;^&lt;Preference Order (NM)&gt;</i></li></ul> <p>Where:</p> <ul style="list-style-type: none"><li>• Expiration Reason subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt;&amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li><li>• Protection code subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt;&amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li><li>• Shared Telecommunication Identifier subcomponents are: <i>&lt;Entity Identifier (ST)&gt;&amp;&lt;Namespace ID (IS)&gt;&amp;&lt;Universal ID (ST)&gt;&amp;&lt;Universal ID Type (ID)&gt;</i></li></ul> <p>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.</p> |
+| <b>Pass/Fail criteria</b> | In step 2, all elements in each segment are as specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |                      |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|
+| <b>TP Id</b>             | TP/HFS/REC/PCD-01-DATA/GEN/BV-003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |                      |
+| <b>TP label</b>          | MSA and Data Type Error                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |                      |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ITU-T H.812.1]       |                      |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MSAUse; M             | MSA-1; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MSA-3; M              | MSA-4; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MSA-6; M              | MSA-7; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | ERRUse 1; O           | ERRUse 2; M          |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | ERR-2; R              | ERR-3; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | ERR-5; M              | ERR-6; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | CWEDataType 1; M      | CWEDataType 2; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | CWEDataType 4; R      | NumericDataType 1; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | DateTimeDataType 1; M | EIDataType 1; M      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | EIDataType 3; M       | EIDataType 4; M      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | EIUse2; C             | EIUse3; C            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | IDDataType 1; M       | ISDataType 1; M      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | XTNDataType 2; M      | XTNDataType 3; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | XTNDataType 5; M      | XTNDataType 6; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | XTNDataType 8; M      | XTNDataType 9; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | XTNDataType 11; M     |                      |
+| <b>Test purpose</b>      | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |                      |
+| <b>Applicability</b>     | C_REC_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |                      |
+| <b>Other PICS</b>        | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |                      |
+| <b>Initial condition</b> | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |                      |
+| <b>Test procedure</b>    | 1. The simulated HFS sender sends the following HL7 message including a wrong data type in the first OBX segment inside a SOAP body to make the HFS receiver respond with another HL7 message:<br>MSH ^~\& AT4_AHD^1234567890ABCDEF^EUI-64   20101015102130+0000  ORU^R01^ORU_R01  MSGID1 P 2.6   NE AL    IHE PCD ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7<br>PID   789567^^Imaginary Hospital^PI  Doe^John^Joseph^^^L<br>OBR 1 POTest^AT4_AHD^1234567890ABCDEF^EUI-64 POTest^AT4_AHD^1234567890ABCDEF^EUI-64 182777000^monitoring of patient^SNOMED-CT   20100522083542+0000<br>OBX 1  531981^MDC_MOC_VMS_MDS_AHD^MDC 0    X    FEEDABEEDEADBE EF^EUI-64<br>OBX 2 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.1 2^auth-body-continua    R<br>OBX 3 ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 0.0.0.1.1 6.1    R<br>OBX 4 NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 0.0.0.1.2 8196~16388    R<br>OBX 5 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.2 2^auth-body-continua    R |                       |                      |
+
+OBX|6|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|0.0.2.1|1^unregulated-device(0)||||R
+
+OBX|7|ST|68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC|0.0.0.3|532224^MDC\_TIME\_SYNC\_NONE^MDC||||R
+
+OBX|8|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.4|2^auth-body-continua||||R
+
+OBX|9|CWE|64515^MDC\_REG\_CERT\_DATA\_CONTINUA\_AHD\_CERT\_LIST^MDC|0.0.0.4.1|0~1||||R
+
+OBX|10||528388^MDC\_DEV\_SPEC\_PROFILE\_PULS\_OXIM^MDC|1||||X||||1234567890ABCDEF^EUI-64
+
+OBX|11|ST|531969^MDC\_ID\_MODEL\_NUMBER^MDC|1.0.0.1|PulseOx v1.5||||R
+
+OBX|12|ST|531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC|1.0.0.2|AT4 Wireless||||R
+
+OBX|13|DTM|67975^MDC\_ATTR\_TIME\_ABS^MDC|1.0.0.3|20100522083542+0000||||R||20100522083542+0000
+
+OBX|14|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.4|2^auth-body-continua||||R
+
+OBX|15|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.5|2^auth-body-continua||||R
+
+OBX|16|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.4.1|1.5||||R
+
+OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|1.0.0.4.2|16388||||R
+
+OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.0.0.5.1|0^unregulated-device(0)||||R
+
+OBX|19|NM|150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC|1.0.0.8|76|262688^MDC\_DIM\_PERCENT^MDC||||R||20100522083542+0000
+
+OBX|20|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|1.0.0.9|100|264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC||||R||20100522083542+0000
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+  - a. Only one MSA segment is present and:
+    - MSA-1 is 'AE' – Accept Acknowledgment: Application Error
+    - MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+    - MSA-3 to MSA-8 are empty
+  - b. If ERR segment referring to the MSA is present:
+    - ERR-1 is empty
+    - ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>
+    - ERR-3 starts with the error code '102', other optional subfields might be included
+    - ERR-4 is set to:
+      - 'E' – Error
+    - ERR-5 and ERR-6 are empty
+    - ERR-7 may be empty, but if it is valued, it is a text data
+    - ERR-8 may be empty, but if it is valued, it is a text data
+    - ERR-9 may be empty, but if it is valued, it is one of these values:
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• 'PAT'</li> <li>• 'NPAT'</li> <li>• 'USR'</li> <li>• 'HD'</li> </ul> <ul style="list-style-type: none"> <li>❑ ERR-10 may be empty, but if it is valued, it is encoded as: <i>&lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt;Name of Coding System (ID)&gt;</i> the rest of the elements of the CWE data type are not used in the Services interface.</li> <li>❑ ERR-11 may be empty, but if it is valued, it is encoded as: <i>&lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt;Name of Coding System (ID)&gt;</i> the rest of the elements of the CWE data type are not used in the Services interface.</li> <li>❑ ERR-12 may be empty, but if it is valued, it is encoded as: <i>&lt;WITHDRAWN Constituent&gt;^&lt;Telecommunication Use Code (ID)&gt;^&lt;Telecommunication Equipment Type (ID)&gt;^&lt;Communication Address (ST)&gt;^&lt;Country Code (NM)&gt;^&lt;Area/City Code (NM)&gt;^&lt;Local Number (NM)&gt;^&lt;Extension (NM)&gt;^&lt;Any Text (ST)&gt;^&lt;Extension Prefix (ST)&gt;^&lt;Speed Dial Code (ST)&gt;^&lt;Unformatted Telephone Number (ST)&gt;^&lt;Effective Start Date (DTM)&gt;^&lt;Expiration Date (DTM)&gt;^&lt;Expiration Reason (CWE)&gt;^&lt;Protection Code (CWE)&gt;^&lt;Shared Telecommunication Identifier (EI)&gt;^&lt;Preference Order (NM)&gt;</i></li> </ul> <p>Where:</p> <ul style="list-style-type: none"> <li>• Expiration Reason subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt;Name of Coding System (ID)&gt;&amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li> <li>• Protection code subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt;Name of Coding System (ID)&gt;&amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li> <li>• Shared Telecommunication Identifier subcomponents are: <i>&lt;Entity Identifier (ST)&gt;&amp;&lt;Namespace ID (IS)&gt;&amp;&lt;Universal ID (ST)&gt;&amp;&lt;Universal ID Type (ID)&gt;</i></li> </ul> <p>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.</p> |
+| <b>Pass/Fail criteria</b> | In step 2, all elements in each segment are as specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                 |                                     |                       |                      |                     |
+|-----------------|-------------------------------------|-----------------------|----------------------|---------------------|
+| <b>TP Id</b>    | TP/HFS/REC/PCD-01-DATA/GEN/BV-004   |                       |                      |                     |
+| <b>TP label</b> | MSA and Table Value not found Error |                       |                      |                     |
+| <b>Coverage</b> | <b>Spec</b>                         | [ITU-T H.812.1]       |                      |                     |
+|                 | <b>Testable items</b>               | MSAUse; M             | MSA-1; M             | MSA-2; M            |
+|                 |                                     | MSA-3; M              | MSA-4; M             | MSA-5; M            |
+|                 |                                     | MSA-6; M              | MSA-7; M             | MSA-8; M            |
+|                 |                                     | ERRUse 1; O           | ERRUse 2; M          | ERR-1; M            |
+|                 |                                     | ERR-2; R              | ERR-3; M             | ERR-4; M            |
+|                 |                                     | ERR-5; M              | ERR-6; M             | ERR-7; O            |
+|                 |                                     | CWEDataType 1; M      | CWEDataType 2; M     | CWEDataType 3; C    |
+|                 |                                     | CWEDataType 4; R      | NumericDataType 1; M | StringDataType 1; M |
+|                 |                                     | DateTimeDataType 1; M | EIDataType 1; M      | EIDataType 2; M     |
+|                 |                                     | EIDataType 3; M       | EIDataType 4; M      | EIUse1; C           |
+|                 |                                     | EIUse2; C             | EIUse3; C            | EIUse4; C           |
+
+|                          |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                  |                   |
+|--------------------------|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-------------------|
+|                          |  | 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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                  |                   |
+| <b>Test purpose</b>      |  | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                  |                   |
+| <b>Applicability</b>     |  | C_REC_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                  |                   |
+| <b>Other PICS</b>        |  | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                  |                   |
+| <b>Initial condition</b> |  | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                  |                   |
+| <b>Test procedure</b>    |  | 1. The simulated HFS sender sends the following HL7 message with an MSH segment including a MSH-15 = ' <b>XXX</b> ' inside a SOAP body to make the HFS receiver respond with another HL7 message:<br><br>MSH ^~\& AT4_AHD^1234567890ABCDEF^EUI-64   20100930102130+0000  <br>ORU^R01^ORU_R01 MSGID123 P 2.6    <b>XXX</b>  AL   IHE PCD ORU-<br>R012006^HL7^2.16.840.1.113883.9.n.m^HL7<br><br>PID   789567^^Imaginary Hospital^PI  Doe^John^Joseph^^^L<br><br>OBR 1 POTest^AT4_AHD^1234567890ABCDEF^EUI-64 POTest^AT4_AHD^<br>1234567890ABCDEF^EUI-64 182777000^monitoring of patient^SNOMED-CT   <br>20100713150214+0000<br><br>OBX 1  531981^MDC_MOC_VMS_MDS_AHD^MDC 0     X     FEEDABEEDEADBE<br>EF^EUI-64<br><br>OBX 2 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.1 2^auth-<br>body-continua     R<br><br>OBX 3 ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 0.0.0.1.1 <br>6.1     R<br><br>OBX 4 NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 0.<br>0.0.1.2 8196~16388     R<br><br>OBX 5 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.2 2^auth-<br>body-continua     R<br><br>OBX 6 CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC 0.<br>0.2.1 1^unregulated-device(0)     R<br><br>OBX 7 CWE 68220^MDC_TIME_SYNC_PROTOCOL^MDC 0.0.0.3 532224^MDC_TIM<br>E_SYNC_NONE^MDC     R<br><br>OBX 8 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.4 2^auth-<br>body-continua     R<br><br>OBX 9 CWE 64515^MDC_REG_CERT_DATA_CONTINUA_AHD_CERT_LIST^MDC 0<br>.0.0.4.1 0~1     R<br><br>OBX 10  528388^MDC_DEV_SPEC_PROFILE_PULS_OXIM^MDC 1     X     123456<br>7890ABCDEF^EUI-64<br><br>OBX 11 ST 531969^MDC_ID_MODEL_NUMBER^MDC 1.0.0.1 PulseOx v1. 5     R<br><br>OBX 12 ST 531970^MDC_ID_MODEL_MANUFACTURER^MDC 1.0.0.2 AT4<br>Wireless     R<br><br>OBX 13 DTM 67975^MDC_ATTR_TIME_ABS^MDC 1.0.0.3 20100713150214+0000   <br>  R  20100713150214+0000<br><br>OBX 14 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.4 2^auth-<br>body-continua     R<br><br>OBX 15 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.5 2^auth-<br>body-continua     R |                  |                   |
+
+OBX|16|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.4.1|1.5|  
+R
+
+OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|1.0.0.4.2|16388|  
+R
+
+OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.0.0.5.1|0^unregulated-device(0)|  
+R
+
+OBX|19|NM|150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC|1.0.0.8|99.1|262688^MDC\_DI\_M\_PERCENT^MDC|  
+R|20100713150214+0000
+
+OBX|20|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|1.0.0.9|82|264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC|  
+R|20100713150214+0000
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+- a. Only one MSA segment is present and:
+    - MSA-1 is 'AE' – Accept Acknowledgment: Application Error
+    - MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+    - MSA-3 to MSA-8 are empty
+  - b. If the ERR segment referring to the MSA is present:
+    - ERR-1 is empty
+    - ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>
+    - ERR-3 starts with the error code '103', other optional subfields might be included
+    - ERR-4 is set to:
+      - 'E' – Error
+    - ERR-5 and ERR-6 are empty
+    - ERR-7 may be empty, but if it is valued, it is a text data
+    - ERR-8 may be empty, but if it is valued, it is a text data
+    - ERR-9 may be empty, but if it is valued, it is one of these values:
+      - 'PAT'
+      - 'NPAT'
+      - 'USR'
+      - 'HD'
+    - ERR-10 may be empty, but if it is valued, it is encoded as: <Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+    - ERR-11 may be empty, but if it is valued, it is encoded as: <Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+    - ERR-12 may be empty, but if it is valued, it is encoded as: <WITHDRAWN Constituent> ^ <Telecommunication Use Code (ID)> ^ <Telecommunication Equipment Type (ID)> ^ <Communication Address (ST)> ^ <Country Code (NM)> ^ <Area/City Code (NM)> ^ <Local Number (NM)> ^ <Extension (NM)> ^ <Any Text (ST)> ^ <Extension Prefix (ST)> ^ <Speed Dial Code (ST)> ^ <Unformatted Telephone Number (ST)> ^ <Effective Start Date (DTM)> ^ <Expiration Date (DTM)> ^ <Expiration Reason (CWE)> ^ <Protection Code (CWE)> ^ <Shared Telecommunication Identifier (EI)> ^ <Preference Order (NM)>
+
+Where:
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• Expiration Reason subcomponents are: &lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt;Name of Coding System (ID)&gt;&amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</li> <li>• Protection code subcomponents are: &lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt;Name of Coding System (ID)&gt;&amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</li> <li>• Shared Telecommunication Identifier subcomponents are: &lt;Entity Identifier (ST)&gt;&amp;&lt;Namespace ID (IS)&gt;&amp;&lt;Universal ID (ST)&gt;&amp;&lt;Universal ID Type (ID)&gt;</li> </ul> <p>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.</p> |
+| <b>Pass/Fail criteria</b> | In step 2, all elements in each segment are as specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                          |                                                                                                                                                                                               |                       |                      |                     |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|---------------------|
+| <b>TP Id</b>             | TP/HFS/REC/PCD-01-DATA/GEN/BV-005                                                                                                                                                             |                       |                      |                     |
+| <b>TP label</b>          | MSA and Unsupported Message Type Error                                                                                                                                                        |                       |                      |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                   | [ITU-T H.812.1]       |                      |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                         | MSAUse; M             | MSA-1; M             | MSA-2; M            |
+|                          |                                                                                                                                                                                               | MSA-3; M              | MSA-4; M             | MSA-5; M            |
+|                          |                                                                                                                                                                                               | MSA-6; M              | MSA-7; M             | MSA-8; M            |
+|                          |                                                                                                                                                                                               | ERRUse 1; O           | ERRUse 2; M          | ERR-1; M            |
+|                          |                                                                                                                                                                                               | ERR-2; R              | ERR-3; M             | ERR-4; M            |
+|                          |                                                                                                                                                                                               | ERR-5; M              | ERR-6; M             | ERR-7; O            |
+|                          |                                                                                                                                                                                               | CWEDataType 1; M      | CWEDataType 2; M     | CWEDataType 3; C    |
+|                          |                                                                                                                                                                                               | CWEDataType 4; R      | NumericDataType 1; M | StringDataType 1; M |
+|                          |                                                                                                                                                                                               | DateTimeDataType 1; M | EIDataType 1; M      | EIDataType 2; M     |
+|                          |                                                                                                                                                                                               | EIDataType 3; M       | EIDataType 4; M      | EIUse1; C           |
+|                          |                                                                                                                                                                                               | EIUse2; C             | EIUse3; C            | EIUse4; C           |
+|                          |                                                                                                                                                                                               | 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     |                      |                     |
+| <b>Test purpose</b>      | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                        |                       |                      |                     |
+| <b>Applicability</b>     | C_REC_000                                                                                                                                                                                     |                       |                      |                     |
+| <b>Other PICS</b>        | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                |                       |                      |                     |
+| <b>Initial condition</b> | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation.                                                      |                       |                      |                     |
+| <b>Test procedure</b>    | 1. The simulated HFS sender sends the following HL7 message with an MSH segment including a MSH-9 = ACK^A01^ACK inside a SOAP body to make the HFS receiver respond with another HL7 message: |                       |                      |                     |
+
+MSH|^~\&|AT4\_AHD^1234567890ABCDEF^EUI-64|||20100930102130+0000||ACK^A01^ACK|MSGID12345|P|2.6||NE|AL|||IHE PCD ORU-R012006^HL7^2.16.840.1.1.13883.9.n.m^HL7
+
+PID|||789567^^Imaginary Hospital^P||Doe^John^Joseph^^^L
+
+OBR|1|POTest^AT4\_AHD^1234567890ABCDEF^EUI-64|POTest^AT4\_AHD^1234567890ABCDEF^EUI-64|182777000^monitoring of patient^SNOMED-CT|||20100910102736+0000
+
+OBX|1||531981^MDC\_MOC\_VMS\_MDS\_AHD^MDC|0|||||X|||||FEEDABEEDEADBE EF^EUI-64
+
+OBX|2|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.1|2^auth-body-continua||||R
+
+OBX|3|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|0.0.0.1.1|6.1||||R
+
+OBX|4|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|0.0.0.1.2|8196~16388||||R
+
+OBX|5|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.2|2^auth-body-continua||||R
+
+OBX|6|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|0.0.0.2.1|1^unregulated-device(0)||||R
+
+OBX|7|CWE|68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC|0.0.0.3|532224^MDC\_TIME\_SYNC\_NONE^MDC||||R
+
+OBX|8|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.4|2^auth-body-continua||||R
+
+OBX|9|CWE|64515^MDC\_REG\_CERT\_DATA\_CONTINUA\_AHD\_CERT\_LIST^MDC|0.0.0.4.1|0~1||||R
+
+OBX|10||528388^MDC\_DEV\_SPEC\_PROFILE\_PULS\_OXIM^MDC|1|||||X|||||1234567890ABCDEF^EUI-64
+
+OBX|11|ST|531969^MDC\_ID\_MODEL\_NUMBER^MDC|1.0.0.1|PulseOx v1.5||||R
+
+OBX|12|ST|531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC|1.0.0.2|AT4 Wireless||||R
+
+OBX|13|DTM|67975^MDC\_ATTR\_TIME\_ABS^MDC|1.0.0.3|20100910102736+0000||||R|||20100910102736+0000
+
+OBX|14|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.4|2^auth-body-continua||||R
+
+OBX|15|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.5|2^auth-body-continua||||R
+
+OBX|16|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.4.1|1.5||||R
+
+OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|1.0.0.4.2|16388||||R
+
+OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.0.0.5.1|0^unregulated-device(0)||||R
+
+OBX|19|NM|150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC|1.0.0.8|83.2|262688^MDC\_DIM\_PERCENT^MDC||||R|||20100910102736+0000
+
+OBX|20|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|1.0.0.9|79|264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC||||R|||20100910102736+0000
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+  - a. Only one MSA segment is present and:
+    - MSA-1 is 'AR' – Accept Acknowledgment: Application Reject
+    - MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+    - MSA-3 to MSA-8 are empty
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>b. If ERR segment referring to the MSA is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> ERR-1 is empty</li> <li><input type="checkbox"/> ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <i>&lt;Segment ID (ST)&gt; ^ &lt;Segment Sequence (NM)&gt; ^ &lt;Field Position (NM)&gt; ^ &lt;Field Repetition (NM)&gt; ^ &lt;Component Number (NM)&gt; ^ &lt;Sub-Component Number (NM)&gt;</i></li> <li><input type="checkbox"/> ERR-3 starts with the error code '200', other optional subfields might be included</li> <li><input type="checkbox"/> ERR-4 is set to: <ul style="list-style-type: none"> <li>• 'E' – Error</li> </ul> </li> <li><input type="checkbox"/> ERR-5 and ERR-6 are empty</li> <li><input type="checkbox"/> ERR-7 may be empty, but if it is valued, it is a text data</li> <li><input type="checkbox"/> ERR-8 may be empty, but if it is valued, it is a text data</li> <li><input type="checkbox"/> ERR-9 may be empty, but if it is valued, it is one of these values: <ul style="list-style-type: none"> <li>• 'PAT'</li> <li>• 'NPAT'</li> <li>• 'USR'</li> <li>• 'HD'</li> </ul> </li> <li><input type="checkbox"/> ERR-10 may be empty, but if it is valued, it is encoded as: <i>&lt;Identifier (ST)&gt; ^ &lt;Text (ST)&gt; ^ &lt; Name of Coding System (ID)&gt;</i> the rest of the elements of the CWE data type are not used in the Services interface.</li> <li><input type="checkbox"/> ERR-11 may be empty, but if it is valued, it is encoded as: <i>&lt;Identifier (ST)&gt; ^ &lt;Text (ST)&gt; ^ &lt; Name of Coding System (ID)&gt;</i> the rest of the elements of the CWE data type are not used in the Services interface.</li> <li><input type="checkbox"/> ERR-12 may be empty, but if it is valued, it is encoded as: <i>&lt;WITHDRAWN Constituent&gt; ^ &lt;Telecommunication Use Code (ID)&gt; ^ &lt;Telecommunication Equipment Type (ID)&gt; ^ &lt;Communication Address (ST)&gt; ^ &lt;Country Code (NM)&gt; ^ &lt;Area/City Code (NM)&gt; ^ &lt;Local Number (NM)&gt; ^ &lt;Extension (NM)&gt; ^ &lt;Any Text (ST)&gt; ^ &lt;Extension Prefix (ST)&gt; ^ &lt;Speed Dial Code (ST)&gt; ^ &lt;Unformatted Telephone Number (ST)&gt; ^ &lt;Effective Start Date (DTM)&gt; ^ &lt;Expiration Date (DTM)&gt; ^ &lt;Expiration Reason (CWE)&gt; ^ &lt;Protection Code (CWE)&gt; ^ &lt;Shared Telecommunication Identifier (EI)&gt; ^ &lt;Preference Order (NM)&gt;</i></li> </ul> <p>Where:</p> <ul style="list-style-type: none"> <li>• Expiration Reason subcomponents are: <i>&lt;Identifier (ST)&gt; &amp; &lt;Text (ST)&gt; &amp; &lt; Name of Coding System (ID)&gt; &amp; &lt;Alternate Identifier (ST)&gt; &amp; &lt;Alternate Text (ST)&gt; &amp; &lt;Name of Alternate Coding System (ID)&gt; &amp; &lt;Coding System Version ID (ST)&gt; &amp; &lt;Alternate Coding System Version ID (ST)&gt; &amp; &lt;Original Text (ST)&gt;</i></li> <li>• Protection code subcomponents are: <i>&lt;Identifier (ST)&gt; &amp; &lt;Text (ST)&gt; &amp; &lt; Name of Coding System (ID)&gt; &amp; &lt;Alternate Identifier (ST)&gt; &amp; &lt;Alternate Text (ST)&gt; &amp; &lt;Name of Alternate Coding System (ID)&gt; &amp; &lt;Coding System Version ID (ST)&gt; &amp; &lt;Alternate Coding System Version ID (ST)&gt; &amp; &lt;Original Text (ST)&gt;</i></li> <li>• Shared Telecommunication Identifier subcomponents are: <i>&lt;Entity Identifier (ST)&gt; &amp; &lt;Namespace ID (IS)&gt; &amp; &lt;Universal ID (ST)&gt; &amp; &lt;Universal ID Type (ID)&gt;</i></li> </ul> <p>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.</p> |
+| <b>Pass/Fail criteria</b> | In step 2, all elements in each segment are as specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |                      |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|
+| <b>TP Id</b>             | TP/HFS/REC/PCD-01-DATA/GEN/BV-006                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |                      |
+| <b>TP label</b>          | MSA and Unsupported Event Code Error                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |                      |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ITU-T H.812.1]       |                      |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MSAUse; M             | MSA-1; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | MSA-3; M              | MSA-4; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | MSA-6; M              | MSA-7; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | ERRUse 1; O           | ERRUse 2; M          |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | ERR-2; R              | ERR-3; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | ERR-5; M              | ERR-6; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | CWEDataType 1; M      | CWEDataType 2; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | CWEDataType 4; R      | NumericDataType 1; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | DateTimeDataType 1; M | EIDataType 1; M      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EIDataType 3; M       | EIDataType 4; M      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EIUse2; C             | EIUse3; C            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | IDDataType 1; M       | ISDataType 1; M      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | XTNDataType 2; M      | XTNDataType 3; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | XTNDataType 5; M      | XTNDataType 6; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | XTNDataType 8; M      | XTNDataType 9; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | XTNDataType 11; M     |                      |
+| <b>Test purpose</b>      | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                       |                      |
+| <b>Applicability</b>     | C_REC_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |                      |
+| <b>Other PICS</b>        | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |                      |
+| <b>Initial condition</b> | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |                      |
+| <b>Test procedure</b>    | 1. The simulated HFS sender sends the following HL7 message with an MSH segment including a wrong event code: MSH-9 = ORU^R02^ORU_R02 inside a SOAP body to make the HFS receiver respond with another HL7 message:<br>MSH ^~\& AT4_AHD^1234567890ABCDEF^EUI-64   20100930102130+0000  ORU^R02^ORU_R02 MSGID1234 P 2.6  NE AL    IHE PCD ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7<br>PID   789567^^Imaginary Hospital^PI  Doe^John^Joseph^^^L<br>OBR 1 POTest^AT4_AHD^1234567890ABCDEF^EUI-64 POTest^AT4_AHD^1234567890ABCDEF^EUI-64 182777000^monitoring of patient^SNOMED-CT   20100813095715+0000<br>OBX 1  531981^MDC_MOC_VMS_MDS_AHD^MDC 0    X    FEEDABEEDEADBE EF^EUI-64<br>OBX 2 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.1 2^auth-body-continua    R<br>OBX 3 ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 0.0.0.1.1 6.1    R<br>OBX 4 NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 0.0.0.1.2 8196~16388    R<br>OBX 5 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.2 2^auth-body-continua    R |                       |                      |
+
+OBX|6|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|0.0.2.1|1^unregulated-device(0)|||||R
+
+OBX|7|CWE|68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC|0.0.0.3|532224^MDC\_TIME\_SYNC\_NONE^MDC|||||R
+
+OBX|8|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.4|2^auth-body-continua|||||R
+
+OBX|9|CWE|64515^MDC\_REG\_CERT\_DATA\_CONTINUA\_AHD\_CERT\_LIST^MDC|0.0.0.4.1|0~1|||||R
+
+OBX|10||528388^MDC\_DEV\_SPEC\_PROFILE\_PULS\_OXIM^MDC|1|||||X|||||1234567890ABCDEF^EUI-64
+
+OBX|11|ST|531969^MDC\_ID\_MODEL\_NUMBER^MDC|1.0.0.1|PulseOx v1.5|||||R
+
+OBX|12|ST|531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC|1.0.0.2|AT4 Wireless|||||R
+
+OBX|13|DTM|67975^MDC\_ATTR\_TIME\_ABS^MDC|1.0.0.3|20100813095715+0000|||||R||20100813095715+0000
+
+OBX|14|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.4|2^auth-body-continua|||||R
+
+OBX|15|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.5|2^auth-body-continua|||||R
+
+OBX|16|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.4.1|1.5|||||R
+
+OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|1.0.0.4.2|16388|||||R
+
+OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.0.0.5.1|0^unregulated-device(0)|||||R
+
+OBX|19|NM|150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC|1.0.0.8|80.5|262688^MDC\_DIM\_PERCENT^MDC|||||R||20100813095715+0000
+
+OBX|20|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|1.0.0.9|70|264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC|||||R||20100813095715+0000
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+  - a. Only one MSA segment is present and:
+    - MSA-1 is 'AR' – Accept Acknowledgment: Application Reject
+    - MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+    - MSA-3 to MSA-8 are empty
+  - b. If ERR segment referring to the MSA is present:
+    - ERR-1 is empty
+    - ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>
+    - ERR-3 starts with the error code '201', other optional subfields might be included
+    - ERR-4 is set to:
+      - 'E' – Error
+    - ERR-5 and ERR-6 are empty
+    - ERR-7 may be empty, but if it is valued, it is a text data
+    - ERR-8 may be empty, but if it is valued, it is a text data
+    - ERR-9 may be empty, but if it is valued, it is one of these values:
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• 'PAT'</li> <li>• 'NPAT'</li> <li>• 'USR'</li> <li>• 'HD'</li> </ul> <p><input type="checkbox"/> ERR-10 may be empty, but if it is valued, it is encoded as: <i>&lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt; Name of Coding System (ID)&gt;</i> the rest of the elements of the CWE data type are not used in the Services interface.</p> <p><input type="checkbox"/> ERR-11 may be empty, but if it is valued, it is encoded as: <i>&lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt; Name of Coding System (ID)&gt;</i> the rest of the elements of the CWE data type are not used in the Services interface.</p> <p><input type="checkbox"/> ERR-12 may be empty, but if it is valued, it is encoded as: <i>&lt;WITHDRAWN Constituent&gt;^&lt;Telecommunication Use Code (ID)&gt;^&lt;Telecommunication Equipment Type (ID)&gt;^&lt;Communication Address (ST)&gt;^&lt;Country Code (NM)&gt;^&lt;Area/City Code (NM)&gt;^&lt;Local Number (NM)&gt;^&lt;Extension (NM)&gt;^&lt;Any Text (ST)&gt;^&lt;Extension Prefix (ST)&gt;^&lt;Speed Dial Code (ST)&gt;^&lt;Unformatted Telephone Number (ST)&gt;^&lt;Effective Start Date (DTM)&gt;^&lt;Expiration Date (DTM)&gt;^&lt;Expiration Reason (CWE)&gt;^&lt;Protection Code (CWE)&gt;^&lt;Shared Telecommunication Identifier (EI)&gt;^&lt;Preference Order (NM)&gt;</i></p> <p>Where:</p> <ul style="list-style-type: none"> <li>• Expiration Reason subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li> <li>• Protection code subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li> <li>• Shared Telecommunication Identifier subcomponents are: <i>&lt;Entity Identifier (ST)&gt;&amp;&lt;Namespace ID (IS)&gt;&amp;&lt;Universal ID (ST)&gt;&amp;&lt;Universal ID Type (ID)&gt;</i></li> </ul> <p>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.</p> |
+| <b>Pass/Fail criteria</b> | In step 2, all elements in each segment are as specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                 |                                          |                       |                      |                     |
+|-----------------|------------------------------------------|-----------------------|----------------------|---------------------|
+| <b>TP Id</b>    | TP/HFS/REC/PCD-01-DATA/GEN/BV-007        |                       |                      |                     |
+| <b>TP label</b> | MSA and Unsupporting Processing Id Error |                       |                      |                     |
+| <b>Coverage</b> | <b>Spec</b>                              | [ITU-T H.812.1]       |                      |                     |
+|                 | <b>Testable items</b>                    | MSAUse; M             | MSA-1; M             | MSA-2; M            |
+|                 |                                          | MSA-3; M              | MSA-4; M             | MSA-5; M            |
+|                 |                                          | MSA-6; M              | MSA-7; M             | MSA-8; M            |
+|                 |                                          | ERRUse 1; O           | ERRUse 2; M          | ERR-1; M            |
+|                 |                                          | ERR-2; R              | ERR-3; M             | ERR-4; M            |
+|                 |                                          | ERR-5; M              | ERR-6; M             | ERR-7; O            |
+|                 |                                          | CWEDataType 1; M      | CWEDataType 2; M     | CWEDataType 3; C    |
+|                 |                                          | CWEDataType 4; R      | NumericDataType 1; M | StringDataType 1; M |
+|                 |                                          | DateTimeDataType 1; M | EIDataType 1; M      | EIDataType 2; M     |
+|                 |                                          | EIDataType 3; M       | EIDataType 4; M      | EIUse1; C           |
+|                 |                                          | EIUse2; C             | EIUse3; C            | EIUse4; C           |
+
+|                          |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                  |                   |
+|--------------------------|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-------------------|
+|                          |  | 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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                  |                   |
+| <b>Test purpose</b>      |  | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                  |                   |
+| <b>Applicability</b>     |  | C_REC_000 AND (NOT (C_SEN_DATA_003 AND C_SEN_DATA_004 AND C_SEN_DATA_005))                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                  |                   |
+| <b>Other PICS</b>        |  | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                  |                   |
+| <b>Initial condition</b> |  | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                  |                   |
+| <b>Test procedure</b>    |  | 1. The simulated HFS sender sends the following HL7 message with an MSH segment sending a not supported Processing (MSH-11 = 'M') inside a SOAP body to make the HFS receiver respond with another HL7 message:<br>MSH ^~\& AT4_AHD^1234567890ABCDEF^EUI-64   20100930102130+0000  ORU^R01^ORU_R01 MSGID123456 M 2.6   NE AL     H E PCD ORU-R012006^HL7^2.16.840.1.1.13883.9.n.m^HL7<br>PID   789567^^Imaginary Hospital^PI  Doe^John^Joseph^^^L<br>OBR 1 POTest^AT4_AHD^1234567890ABCDEF^EUI-64 POTest^AT4_AHD^1234567890ABCDEF^EUI-64 182777000^monitoring of patient^SNOMED-CT   20100813095715+0000<br>OBX 1  531981^MDC_MOC_VMS_MDS_AHD^MDC 0     X     FEEDABEEDEADBE EF^EUI-64<br>OBX 2  CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.1 2^auth-body-continua     R<br>OBX 3  ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 0.0.0.1.1 6.1     R<br>OBX 4  NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 0.0.0.1.2 8196~16388     R<br>OBX 5  CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.2 2^auth-body-continua     R<br>OBX 6  CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC 0.0.0.2.1 1^unregulated-device(0)     R<br>OBX 7  CWE 68220^MDC_TIME_SYNC_PROTOCOL^MDC 0.0.0.3 532224^MDC_TIME_SYNC_NONE^MDC     R<br>OBX 8  CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.4 2^auth-body-continua     R<br>OBX 9  CWE 64515^MDC_REG_CERT_DATA_CONTINUA_AHD_CERT_LIST^MDC 0.0.0.4.1 0~1     R<br>OBX 10  528388^MDC_DEV_SPEC_PROFILE_PULS_OXIM^MDC 1     X     1234567890ABCDEF^EUI-64<br>OBX 11  ST 531969^MDC_ID_MODEL_NUMBER^MDC 1.0.0.1 PulseOx v1.5     R<br>OBX 12  ST 531970^MDC_ID_MODEL_MANUFACTURER^MDC 1.0.0.2 AT4 Wireless     R<br>OBX 13  DTM 67975^MDC_ATTR_TIME_ABS^MDC 1.0.0.3 20100813095715+0000     R   20100813095715+0000<br>OBX 14  CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.4 2^auth-body-continua     R |                  |                   |
+
+OBX|15|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.5|2^auth-body-continua|||||R
+
+OBX|16|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.4.1|1.5|||||R
+
+OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|1.0.0.4.2|16388|||||R
+
+OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.0.0.5.1|0^unregulated-device(0)|||||R
+
+OBX|19|NM|150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC|1.0.0.8|85.9|262688^MDC\_DI\_M\_PERCENT^MDC|||||R||20100813095715+0000
+
+OBX|20|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|1.0.0.9|77|264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC|||||R||20100813095715+0000
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+  - a. Only one MSA segment is present and:
+    - MSA-1 is 'AR' – Accept Acknowledgment: Application Reject
+    - MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+    - MSA-3 to MSA-8 are empty
+  - b. If the ERR segment referring to the MSA is present:
+    - ERR-1 is empty
+    - ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>
+    - ERR-3 starts with the error code '202', other optional subfields might be included
+    - ERR-4 is set to:
+      - 'E' – Error
+    - ERR-5 and ERR-6 are empty
+    - ERR-7 may be empty, but if it is valued, it is a text data
+    - ERR-8 may be empty, but if it is valued, it is a text data
+    - ERR-9 may be empty, but if it is valued, it is one of these values:
+      - 'PAT'
+      - 'NPAT'
+      - 'USR'
+      - 'HD'
+    - ERR-10 may be empty, but if it is valued, it is encoded as: <Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+    - ERR-11 may be empty, but if it is valued, it is encoded as: <Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+    - ERR-12 may be empty, but if it is valued, it is encoded as: <WITHDRAWN Constituent> ^ <Telecommunication Use Code (ID)> ^ <Telecommunication Equipment Type (ID)> ^ <Communication Address (ST)> ^ <Country Code (NM)> ^ <Area/City Code (NM)> ^ <Local Number (NM)> ^ <Extension (NM)> ^ <Any Text (ST)> ^ <Extension Prefix (ST)> ^ <Speed Dial Code (ST)> ^ <Unformatted Telephone Number (ST)> ^ <Effective Start Date (DTM)> ^ <Expiration Date (DTM)> ^ <Expiration Reason (CWE)> ^ <Protection
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>Code (CWE)^&lt;Shared Telecommunication Identifier (EI)^&lt;Preference Order (NM)&gt;</p> <p>Where:</p> <ul style="list-style-type: none"> <li>• Expiration Reason subcomponents are: &lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt;Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</li> <li>• Protection code subcomponents are: &lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt;Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</li> <li>• Shared Telecommunication Identifier subcomponents are: &lt;Entity Identifier (ST)&gt;&amp;&lt;Namespace ID (IS)&gt;&amp;&lt;Universal ID (ST)&gt;&amp;&lt;Universal ID Type (ID)&gt;</li> </ul> <p>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.</p> |
+| <b>Pass/Fail criteria</b> | In step 2, all elements in each segment are as specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                          |                                                                                                                                          |                       |                      |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|
+| <b>TP Id</b>             | TP/HFS/REC/PCD-01-DATA/GEN/BV-008                                                                                                        |                       |                      |
+| <b>TP label</b>          | MSA and Unsupported Version Id Error                                                                                                     |                       |                      |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                              | [ITU-T H.812.1]       |                      |
+|                          | <b>Testable items</b>                                                                                                                    | MSAUse; M             | MSA-1; M             |
+|                          |                                                                                                                                          | MSA-3; M              | MSA-4; M             |
+|                          |                                                                                                                                          | MSA-6; M              | MSA-7; M             |
+|                          |                                                                                                                                          | ERRUse 1; O           | ERRUse 2; M          |
+|                          |                                                                                                                                          | ERR-2; R              | ERR-3; M             |
+|                          |                                                                                                                                          | ERR-5; M              | ERR-6; M             |
+|                          |                                                                                                                                          | CWEDataType 1; M      | CWEDataType 2; M     |
+|                          |                                                                                                                                          | CWEDataType 4; R      | NumericDataType 1; M |
+|                          |                                                                                                                                          | DateTimeDataType 1; M | EIDataType 1; M      |
+|                          |                                                                                                                                          | EIDataType 3; M       | EIDataType 4; M      |
+|                          |                                                                                                                                          | EIUse2; C             | EIUse3; C            |
+|                          |                                                                                                                                          | IDDataType 1; M       | ISDataType 1; M      |
+|                          |                                                                                                                                          | XTNDataType 2; M      | XTNDataType 3; M     |
+|                          |                                                                                                                                          | XTNDataType 5; M      | XTNDataType 6; M     |
+|                          |                                                                                                                                          | XTNDataType 8; M      | XTNDataType 9; M     |
+|                          |                                                                                                                                          | XTNDataType 11; M     |                      |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The elements of every segment of the message</p> <p>[AND]</p> <p>The data type of each element.</p>                |                       |                      |
+| <b>Applicability</b>     | C_REC_000                                                                                                                                |                       |                      |
+| <b>Other PICS</b>        | C_REC_DATA_003, C_REC_DATA_004                                                                                                           |                       |                      |
+| <b>Initial condition</b> | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation. |                       |                      |
+
+|                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <p><b>Test procedure</b></p> | <ol style="list-style-type: none"> <li data-bbox="450 168 1428 1881"> <p>1. The simulated HFS sender sends the following HL7 message with an MSH segment sending a MSH-12 = '2.5' inside a SOAP body to make the the HFS receiver respond with another HL7 message:</p> <pre> MSH ^~\&amp; AT4_AHD^1234567890ABCDEF^EUI-64   20100930102130+0000  ORU^R01^ORU_R01 MSGID1235 P 2.5  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_AHD^1234567890ABCDEF^EUI-64 POTest^AT4_AHD^1234567890ABCDEF^EUI-64 182777000^monitoring of patient^SNOMED-CT   20100322172147+0000  OBX 1  531981^MDC_MOC_VMS_MDS_AHD^MDC 0     X     FEEDABEEDEADBE EF^EUI-64  OBX 2 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.1 2^auth-body-continua     R  OBX 3 ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 0.0.0.1.1 6.1     R  OBX 4 NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 0.0.0.1.2 8196~16388     R  OBX 5 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.2 2^auth-body-continua     R  OBX 6 CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC 0.0.0.2.1 1^unregulated-device(0)     R  OBX 7 CWE 68220^MDC_TIME_SYNC_PROTOCOL^MDC 0.0.0.3 532224^MDC_TIME_SYNC_NONE^MDC     R  OBX 8 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.4 2^auth-body-continua     R  OBX 9 CWE 64515^MDC_REG_CERT_DATA_CONTINUA_AHD_CERT_LIST^MDC 0.0.0.4.1 0~1     R  OBX 10  528388^MDC_DEV_SPEC_PROFILE_PULS_OXIM^MDC 1     X     1234567890ABCDEF^EUI-64  OBX 11 ST 531969^MDC_ID_MODEL_NUMBER^MDC 1.0.0.1 PulseOx v1.5     R  OBX 12 ST 531970^MDC_ID_MODEL_MANUFACTURER^MDC 1.0.0.2 AT4 Wireless     R  OBX 13 DTM 67975^MDC_ATTR_TIME_ABS^MDC 1.0.0.3 20100322172147+0000     R  20100322172147+0000  OBX 14 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.5 2^auth-body-continua     R  OBX 15 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.6 2^auth-body-continua     R  OBX 16 ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 1.0.0.5.1 1.5     R  OBX 17 NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 1.0.0.5.2 16388     R  OBX 18 CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC 1.0.0.6.1 0^unregulated-device(0)     R  OBX 19 NM 150456^MDC_PULS_OXIM_SAT_O2^MDC 1.0.0.8 77.1 262688^MDC_DIM_PERCENT^MDC     R  20100322172147+0000  OBX 20 NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC 1.0.0.9 92 264864^MDC_DIM_BEAT_PER_MIN^MDC     R  20100322172147+0000 </pre> </li> <li data-bbox="450 1899 1428 2027"> <p>2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:</p> <ol style="list-style-type: none"> <li data-bbox="497 1971 965 2027"> <p>a. Only one MSA segment is present and:</p> <p><input type="checkbox"/> MSA-1 is 'AR' – Accept Acknowledgment: Application Reject</p> </li> </ol> </li> </ol> |
+|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent</li> <li><input type="checkbox"/> MSA-3 to MSA-8 are empty</li> </ul> <p>b. If the ERR segment referring to the MSA is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> ERR-1 is empty</li> <li><input type="checkbox"/> ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: &lt;Segment ID (ST)&gt; ^ &lt;Segment Sequence (NM)&gt; ^ &lt;Field Position (NM)&gt; ^ &lt;Field Repetition (NM)&gt; ^ &lt;Component Number (NM)&gt; ^ &lt;Sub-Component Number (NM)&gt;</li> <li><input type="checkbox"/> ERR-3 starts with the error code '203', other optional subfields might be included</li> <li><input type="checkbox"/> ERR-4 is set to: <ul style="list-style-type: none"> <li>• 'E' – Error</li> </ul> </li> <li><input type="checkbox"/> ERR-5 and ERR-6 are empty</li> <li><input type="checkbox"/> ERR-7 may be empty, but if it is valued, it is a text data</li> <li><input type="checkbox"/> ERR-8 may be empty, but if it is valued, it is a text data</li> <li><input type="checkbox"/> ERR-9 may be empty, but if it is valued, it is one of these values: <ul style="list-style-type: none"> <li>• 'PAT'</li> <li>• N'PAT'</li> <li>• USR</li> <li>• HD</li> </ul> </li> <li><input type="checkbox"/> ERR-10 may be empty, but if it is valued, it is encoded as: &lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt; Name of Coding System (ID)&gt; the rest of the elements of the CWE data type are not used in the Services interface.</li> <li><input type="checkbox"/> ERR-11 may be empty, but if it is valued, it is encoded as: &lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt; Name of Coding System (ID)&gt; the rest of the elements of the CWE data type are not used in the Services interface.</li> <li><input type="checkbox"/> ERR-12 may be empty, but if it is valued, it is encoded as: &lt;WITHDRAWN Constituent&gt;^&lt;Telecommunication Use Code (ID)&gt;^&lt;Telecommunication Equipment Type (ID)&gt;^&lt;Communication Address (ST)&gt;^&lt;Country Code (NM)&gt;^&lt;Area/City Code (NM)&gt;^&lt;Local Number (NM)&gt;^&lt;Extension (NM)&gt;^&lt;Any Text (ST)&gt;^&lt;Extension Prefix (ST)&gt;^&lt;Speed Dial Code (ST)&gt;^&lt;Unformatted Telephone Number (ST)&gt;^&lt;Effective Start Date (DTM)&gt;^&lt;Expiration Date (DTM)&gt;^&lt;Expiration Reason (CWE)&gt;^&lt;Protection Code (CWE)&gt;^&lt;Shared Telecommunication Identifier (EI)&gt;^&lt;Preference Order (NM)&gt;</li> </ul> <p>Where:</p> <ul style="list-style-type: none"> <li>• Expiration Reason subcomponents are: &lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</li> <li>• Protection code subcomponents are: &lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</li> <li>• Shared Telecommunication Identifier subcomponents are: &lt;Entity Identifier (ST)&gt;&amp;&lt;Namespace ID (IS)&gt;&amp;&lt;Universal ID (ST)&gt;&amp;&lt;Universal ID Type (ID)&gt;</li> </ul> <p>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.</p> |
+| <b>Pass/Fail criteria</b> | In step 2, all elements in each segment are as specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|              |  |
+|--------------|--|
+| <b>Notes</b> |  |
+|--------------|--|
+
+### A.3 Subgroup 2.4.2: Design guidelines (DG)
+
+No test cases have been defined in this subgroup.
+
+### A.4 Subgroup 2.4.3: Pulse oximeter (PO)
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |                      |                     |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|---------------------|
+| <b>TP Id</b>             | TP/HFS/REC/PCD-01-DATA/PO/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |                      |                     |
+| <b>TP label</b>          | MSA and ERR segments                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |                      |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [ITU-T H.812.1]       |                      |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | MSAUse; M             | MSA-1; M             | MSA-2; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | MSA-3; M              | MSA-4; M             | MSA-5; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | MSA-6; M              | MSA-7; M             | MSA-8; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | ERRUse 1; O           | ERRUse 2; M          | ERR-1; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | ERR-2; R              | ERR-3; M             | ERR-4; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | ERR-5; M              | ERR-6; M             | ERR-7; O            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | CWEDataType 1; M      | CWEDataType 2; M     | CWEDataType 3; C    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | CWEDataType 4; R      | NumericDataType 1; M | StringDataType 1; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | DateTimeDataType 1; M | EIDataType 1; M      | EIDataType 2; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | EIDataType 3; M       | EIDataType 4; M      | EIUse1; C           |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | EIUse2; C             | EIUse3; C            | EIUse4; C           |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | 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     |                      |                     |
+| <b>Test purpose</b>      | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                       |                      |                     |
+| <b>Applicability</b>     | C_REC_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |                      |                     |
+| <b>Other PICS</b>        | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |                      |                     |
+| <b>Initial condition</b> | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation of a pulse oximeter device.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |                      |                     |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated HFS sender sends the following HL7 message, including the mandatory objects of a pulse oximeter device inside a SOAP body to make the HFS receiver respond with another HL7 message.<br/><br/> MSH ^~\&amp; AT4_AHD^1234567890ABCDEF^EUI-64   <current>  ORU^R01^ORU_R01 MSGID<random> P 2.6  NE AL    IHE PCD ORU-R012006^HL7^2.16.840.1.1.13883.9.n.m^HL7<br/><br/> PID   789567^^Imaginary Hospital^PI  Doe^John^Joseph^^^L<br/><br/> OBR 1 POTest^AT4_AHD^1234567890ABCDEF^EUI-64 POTest^AT4_AHD^1234567890ABCDEF^EUI-64 182777000^monitoring of patient^SNOMED-CT   20100903124015+0000<br/><br/> OBX 1  531981^MDC_MOC_VMS_MDS_AHD^MDC 0    X    FEEDABEEDEADBE EF^EUI-64<br/><br/> OBX 2 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.1 2^auth-body-continua    R </random></current></li> </ol> |                       |                      |                     |
+
+OBX|3|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|0.0.0.1.1|6.1|||||R
+
+OBX|4|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|0.0.0.1.2|8196~16388|||||R
+
+OBX|5|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.2|2^auth-body-continua|||||R
+
+OBX|6|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|0.0.0.2.1|1^unregulated-device(0)|||||R
+
+OBX|7|CWE|68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC|0.0.0.3|532224^MDC\_TIME\_SYNC\_NONE^MDC|||||R
+
+OBX|8|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.4|2^auth-body-continua|||||R
+
+OBX|9|CWE|64515^MDC\_REG\_CERT\_DATA\_CONTINUA\_AHD\_CERT\_LIST^MDC|0.0.0.4.1|0~1|||||R
+
+OBX|10||528388^MDC\_DEV\_SPEC\_PROFILE\_PULS\_OXIM^MDC|1|||||X|||||1234567890ABCDEF^EUI-64
+
+OBX|11|ST|531969^MDC\_ID\_MODEL\_NUMBER^MDC|1.0.0.1|PulseOx v1.5|||||R
+
+OBX|12|ST|531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC|1.0.0.2|AT4 Wireless|||||R
+
+OBX|13|DTM|67975^MDC\_ATTR\_TIME\_ABS^MDC|1.0.0.3|20100903124015+0000|||||R||20100903124015+0000
+
+OBX|14|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.4|2^auth-body-continua|||||R
+
+OBX|15|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.5|2^auth-body-continua|||||R
+
+OBX|16|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.4.1|1.5|||||R
+
+OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|1.0.0.4.2|16388|||||R
+
+OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.0.0.5.1|0^unregulated-device(0)|||||R
+
+OBX|19|NM|150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC|1.0.0.6|92.3|262688^MDC\_DIM\_PERCENT^MDC|||||R||20100903124015+0000
+
+OBX|20|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|1.0.0.7|71|264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC|||||R||20100903124015+0000
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+- a. Only one MSA segment is present and:
+    - MSA-1 is one of the following values:
+      - 'AA' – Accept Acknowledgment: Application Accept
+      - 'AR' – Accept Acknowledgment: Application Reject
+    - MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+    - MSA-3 to MSA-8 are empty
+  - b. If the ERR segment referring to the MSA is present:
+    - If the HFS receiver reports an ERR segment with a severity (ERR-4) E (Error) or F (Fatal Error), the Message Acknowledgement value shall be CR (Commit Reject)
+    - ERR-1 is empty
+    - ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><i>Repetition (NM) &gt; ^ &lt;Component Number (NM) &gt; ^ &lt;Sub-Component Number (NM)&gt;</i></p> <ul style="list-style-type: none"> <li><input type="checkbox"/> ERR-3 starts with one of the following valid error condition codes and other optional subfields might be included: <ul style="list-style-type: none"> <li>• '0' – Accepted</li> <li>• '206' – Application record locked</li> <li>• '207' – Application internal error</li> </ul> </li> <li><input type="checkbox"/> ERR-4 is set to one of these valid error severity values: <ul style="list-style-type: none"> <li>• 'W' – Warning</li> <li>• 'I' – Information</li> <li>• 'E' – Error</li> <li>• 'F' – Fatal error.</li> </ul> </li> <li><input type="checkbox"/> ERR-5 and ERR-6 are empty</li> <li><input type="checkbox"/> ERR-7 may be empty, but if it is valued, it is a text data</li> <li><input type="checkbox"/> ERR-8 may be empty, but if it is valued, it is a text data</li> <li><input type="checkbox"/> ERR-9 may be empty, but if it is valued, it is one of these values: <ul style="list-style-type: none"> <li>• 'PAT'</li> <li>• 'NPAT'</li> <li>• 'USR'</li> <li>• 'HD'</li> </ul> </li> <li><input type="checkbox"/> ERR-10 may be empty, but if it is valued, it is encoded as: <i>&lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt; Name of Coding System (ID)&gt;</i> the rest of the elements of the CWE data type are not used in the Services interface.</li> <li><input type="checkbox"/> ERR-11 may be empty, but if it is valued, it is encoded as: <i>&lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt; Name of Coding System (ID)&gt;</i> the rest of the elements of the CWE data type are not used in the Services interface.</li> <li><input type="checkbox"/> ERR-12 may be empty, but if it is valued, it is encoded as: <i>&lt;WITHDRAWN Constituent&gt;^&lt;Telecommunication Use Code (ID)&gt;^&lt;Telecommunication Equipment Type (ID)&gt;^&lt;Communication Address (ST)&gt;^&lt;Country Code (NM)&gt;^&lt;Area/City Code (NM)&gt;^&lt;Local Number (NM)&gt;^&lt;Extension (NM)&gt;^&lt;Any Text (ST)&gt;^&lt;Extension Prefix (ST)&gt;^&lt;Speed Dial Code (ST)&gt;^&lt;Unformatted Telephone Number (ST)&gt;^&lt;Effective Start Date (DTM)&gt;^&lt;Expiration Date (DTM)&gt;^&lt;Expiration Reason (CWE)&gt;^&lt;Protection Code (CWE)&gt;^&lt;Shared Telecommunication Identifier (EI)&gt;^&lt;Preference Order (NM)&gt;</i></li> </ul> <p>Where:</p> <ul style="list-style-type: none"> <li>• Expiration Reason subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt; &amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li> <li>• Protection code subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt; &amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li> <li>• Shared Telecommunication Identifier subcomponents are: <i>&lt;Entity Identifier (ST)&gt;&amp;&lt;Namespace ID (IS)&gt;&amp;&lt;Universal ID (ST)&gt;&amp;&lt;Universal ID Type (ID)&gt;</i></li> </ul> <p>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.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2, all elements in each segment are as specified above</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|              |                                                                                                                                                                                                                                                                                                                                                                                                              |
+|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|              | <ul style="list-style-type: none"> <li>Verify that the HFS receiver under test is able to accept the data and time stamps (e.g., if there is a log verify the date and the data are displayed in some form that indicates the correct date and time and the correct data as transmitted). Date and time of the measurement: 2010-09-03 12:40:15 UTC, Values: SpO2=92.3 [%] and PulseRate=71 [bpm]</li> </ul> |
+| <b>Notes</b> |                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+### A.5 Subgroup 2.4.4: Blood pressure monitor (BPM)
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |                      |                     |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|---------------------|
+| <b>TP Id</b>             | TP/HFS/REC/PCD-01-DATA/BPM/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                       |                      |                     |
+| <b>TP label</b>          | MSA and ERR segments                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |                      |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [ITU-T H.812.1]       |                      |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | MSAUse; M             | MSA-1; M             | MSA-2; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | MSA-3; M              | MSA-4; M             | MSA-5; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | MSA-6; M              | MSA-7; M             | MSA-8; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | ERRUse 1; O           | ERRUse 2; M          | ERR-1; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | ERR-2; R              | ERR-3; M             | ERR-4; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | ERR-5; M              | ERR-6; M             | ERR-7; O            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | CWEDataType 1; M      | CWEDataType 2; M     | CWEDataType 3; C    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | CWEDataType 4; R      | NumericDataType 1; M | StringDataType 1; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | DateTimeDataType 1; M | EIDataType 1; M      | EIDataType 2; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | EIDataType 3; M       | EIDataType 4; M      | EIUse1; C           |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | EIUse2; C             | EIUse3; C            | EIUse4; C           |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | 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     |                      |                     |
+| <b>Test purpose</b>      | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                       |                      |                     |
+| <b>Applicability</b>     | C_REC_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |                      |                     |
+| <b>Other PICS</b>        | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |                      |                     |
+| <b>Initial condition</b> | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation of a blood pressure device.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |                      |                     |
+| <b>Test procedure</b>    | 1. The simulated HFS sender sends the following HL7 message, including the mandatory objects of a blood pressure device inside a SOAP body, to make the HFS receiver respond. The message sent is:<br><br>MSH ^~\& AT4_AHD^1234567890ABCDEF^EUI-64   <current time in UTC>  ORU^R01^ORU_R01 MSGID<random number> P 2.6  NE AL    IHE PCD ORU-R012006^HL7^2.16.840.1.1.13883.9.n.m^HL7<br><br>PID   789567^^^Imaginary Hospital^PI  Doe^John^Joseph^^^L<br><br>OBR 1 BPMTest^AT4_AHD^1234567890ABCDEF^EUI-64 BPMTest^AT4_AHD^1234567890ABCDEF^EUI-64 182777000^monitoring of patient^SNOMED-CT   20100916145110+0000<br><br>OBX 1  531981^MDC_MOC_VMS_MDS_AHD^MDC 0     X     FEEDABEEDEADBE EF^EUI-64<br><br>OBX 2 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.1 2^auth-body-continua     R |                       |                      |                     |
+
+OBX|3|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|0.0.0.1.1|6.1|||||R
+
+OBX|4|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|0.0.1.2|8199~7|||||R
+
+OBX|5|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.2|2^auth-body-continua|||||R
+
+OBX|6|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|0.0.0.2.1|1^unregulated-device(0)|||||R
+
+OBX|7|CWE|68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC|0.0.0.3|532224^MDC\_TIME\_SYNC\_NONE^MDC|||||R
+
+OBX|8|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.4|2^auth-body-continua|||||R
+
+OBX|9|CWE|64515^MDC\_REG\_CERT\_DATA\_CONTINUA\_AHD\_CERT\_LIST^MDC|0.0.0.4.1|0~1|||||R
+
+OBX|10||528391^MDC\_DEV\_SPEC\_PROFILE\_BP^MDC|1|||||X|||||1234567890ABCDEF^EUI-64
+
+OBX|11|ST|531969^MDC\_ID\_MODEL\_NUMBER^MDC|1.0.0.1|BloodPressure v1.5|||||R
+
+OBX|12|ST|531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC|1.0.0.2|AT4 Wireless|||||R
+
+OBX|13|DTM|67975^MDC\_ATTR\_TIME\_ABS^MDC|1.0.0.3|20100916145110+0000|||||R||20100916145110+0000
+
+OBX|14|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.4|2^auth-body-continua|||||R
+
+OBX|15|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.5|2^auth-body-continua|||||R
+
+OBX|16|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.4.1|1.5|||||R
+
+OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|1.0.0.4.2|8199|||||R
+
+OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.0.0.5.1|0^unregulated-device(0)|||||R
+
+OBX|19||150020^MDC\_PRESS\_BLD\_NONINV^MDC|1.0.1|||||X||20100916145110+0000
+
+OBX|20|NM|150021^MDC\_PRESS\_BLD\_NONINV\_SYS^MDC|1.0.1.1|120|266016^MDC\_DIM\_MMHG^MDC|||||R
+
+OBX|21|NM|150022^MDC\_PRESS\_BLD\_NONINV\_DIA^MDC|1.0.1.2|80|266016^MDC\_DIM\_MMHG^MDC|||||R
+
+OBX|22|NM|150023^MDC\_PRESS\_BLD\_NONINV\_MEAN^MDC|1.0.1.3|100|266016^MDC\_DIM\_MMHG^MDC|||||R
+
+OBX|23|NM|149546^MDC\_PULS\_RATE\_NON\_INV^MDC|1.0.0.8|82|264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC|||||R||20100916145110+0000
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+
+a. Only one MSA segment is present and:
+
+MSA-1 is one of the following values:
+
+- 'AA' – Accept Acknowledgment: Application Accept
+- 'AR' – Accept Acknowledgment: Application Reject
+
+MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+
+MSA-3 to MSA-8 are empty
+
+b. If the ERR segment referring to the MSA is present:
+
+- If the HFS receiver reports an ERR segment with severity E (error) or F (fatal error), the Message Acknowledgement value shall be CR (commit reject)
+  - ERR-1 is empty
+  - ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: *<Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>*
+  - ERR-3 starts with one of the following valid error condition codes and other optional subfields might be included:
+    - '0' – Message accepted
+    - '206' – Application record locked
+    - '207' – Application internal error
+  - ERR-4 is set to one of these valid error severity values:
+    - 'W' – Warning
+    - 'I' – Information
+    - 'E' – Error
+    - 'F' – Fatal error.
+  - ERR-5 and ERR-6 are empty
+  - ERR-7 may be empty, but if it is valued, it is a text data
+  - ERR-8 may be empty, but if it is valued, it is a text data
+  - ERR-9 may be empty, but if it is valued, it is one of these values:
+    - 'PAT'
+    - 'NPAT'
+    - 'USR'
+    - 'HD'
+  - ERR-10 may be empty, but if it is valued, it is encoded as: *<Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)>* the rest of the elements of the CWE data type are not used in the Services interface.
+  - ERR-11 may be empty, but if it is valued, it is encoded as: *<Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)>* the rest of the elements of the CWE data type are not used in the Services interface.
+  - ERR-12 may be empty, but if it is valued, it is encoded as: *<WITHDRAWN Constituent> ^ <Telecommunication Use Code (ID)> ^ <Telecommunication Equipment Type (ID)> ^ <Communication Address (ST)> ^ <Country Code (NM)> ^ <Area/City Code (NM)> ^ <Local Number (NM)> ^ <Extension (NM)> ^ <Any Text (ST)> ^ <Extension Prefix (ST)> ^ <Speed Dial Code (ST)> ^ <Unformatted Telephone Number (ST)> ^ <Effective Start Date (DTM)> ^ <Expiration Date (DTM)> ^ <Expiration Reason (CWE)> ^ <Protection Code (CWE)> ^ <Shared Telecommunication Identifier (EI)> ^ <Preference Order (NM)>*
+- Where:
+- Expiration Reason subcomponents are: *<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)>*
+  - Protection code subcomponents are: *<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)>*
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>Shared Telecommunication Identifier subcomponents are: &lt;Entity Identifier (ST)&gt;&amp;&lt;Namespace ID (IS)&gt;&amp;&lt;Universal ID (ST)&gt;&amp;&lt;Universal ID Type (ID)&gt;</li> </ul> <p>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.</p>                                                                                                                                                                   |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>In step 2, all elements in each segment are as specified above</li> <li>Verify that the HFS receiver under test is able to accept the data and time stamps (e.g., if there is a log verify the date and the data are displayed in some form that indicates the correct date and time and the correct data as transmitted). Date and time of the measurement: 2010-09-16 14:51:10 UTC, Values: Systolic=120 [mmHg], Diastolic=80 [mmHg], Mean=100 [mmHg], and PulseRate=82 [bpm]</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+### A.6 Subgroup 2.4.5: Thermometer (TH)
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |                      |                     |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|---------------------|
+| <b>TP Id</b>             | TP/HFS/REC/PCD-01-DATA/TH/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |                      |                     |
+| <b>TP label</b>          | MSA and ERR segments                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |                      |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ITU-T H.812.1]       |                      |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                               | MSAUse; M             | MSA-1; M             | MSA-2; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | MSA-3; M              | MSA-4; M             | MSA-5; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | MSA-6; M              | MSA-7; M             | MSA-8; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ERRUse 1; O           | ERRUse 2; M          | ERR-1; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ERR-2; R              | ERR-3; M             | ERR-4; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ERR-5; M              | ERR-6; M             | ERR-7; O            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | CWEDataType 1; M      | CWEDataType 2; M     | CWEDataType 3; C    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | CWEDataType 4; R      | NumericDataType 1; M | StringDataType 1; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | DateTimeDataType 1; M | EIDataType 1; M      | EIDataType 2; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | EIDataType 3; M       | EIDataType 4; M      | EIUse1; C           |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | EIUse2; C             | EIUse3; C            | EIUse4; C           |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | 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     |                      |                     |
+| <b>Test purpose</b>      | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                                                                                                                                                                                                                                                                              |                       |                      |                     |
+| <b>Applicability</b>     | C_REC_000                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |                      |                     |
+| <b>Other PICS</b>        | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |                      |                     |
+| <b>Initial condition</b> | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation of a thermometer device.                                                                                                                                                                                                                                                                                    |                       |                      |                     |
+| <b>Test procedure</b>    | 1. The simulated HFS sender sends the following HL7 message, including the mandatory objects of a thermometer device inside a SOAP body to make the HFS receiver respond with another HL7 message.<br><br>MSH ^~\& AT4_AHD^1234567890ABCDEF^EUI-64   <current time in UTC>  ORU^R01^ORU_R01 MSGID<random number> P 2.6  NE AL   IHE PCD ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7<br><br>PID   789567^^Imaginary Hospital^PI  Doe^John^Joseph^^^L |                       |                      |                     |
+
+OBR|1|THTest^AT4\_AHD^1234567890ABCDEF^EUI-64|THTest^AT4\_AHD^1234567890ABCDEF^EUI-64|182777000^monitoring of patient^SNOMED-CT|||20100916145110+0000  
+ OBX|1||531981^MDC\_MOC\_VMS\_MDS\_AHD^MDC|0|||||X|||||FEEDABEEDEADBE EF^EUI-64  
+ OBX|2|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.1|2^auth-body-continua|||||R  
+ OBX|3|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|0.0.0.1.1|6.1|||||R  
+ OBX|4|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|0.0.0.1.2|8200~16392~32776|||||R  
+ OBX|5|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.2|2^auth-body-continua|||||R  
+ OBX|6|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|0.0.2.1|1^unregulated-device(0)|||||R  
+ OBX|7|CWE|68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC|0.0.0.3|532224^MDC\_TIME\_SYNC\_NONE^MDC|||||R  
+ OBX|8|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.4|2^auth-body-continua|||||R  
+ OBX|9|CWE|64515^MDC\_REG\_CERT\_DATA\_CONTINUA\_AHD\_CERT\_LIST^MDC|0.0.0.4.1|0~1|||||R  
+ OBX|10||528392^MDC\_DEV\_SPEC\_PROFILE\_TEMP^MDC|1|||||X|||||1234567890ABCDEF^EUI-64  
+ OBX|11|ST|531969^MDC\_ID\_MODEL\_NUMBER^MDC|1.0.0.1|Thermometer v1.5|||||R  
+ OBX|12|ST|531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC|1.0.0.2|AT4 Wireless|||||R  
+ OBX|13|DTM|67975^MDC\_ATTR\_TIME\_ABS^MDC|1.0.0.3|20100916145110+0000|||||R|||20100916145110+0000  
+ OBX|14|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.4|2^auth-body-continua|||||R  
+ OBX|15|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.5|2^auth-body-continua|||||R  
+ OBX|16|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.4.1|1.5|||||R  
+ OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|1.0.0.4.2|16392|||||R  
+ OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.0.0.5.1|0^unregulated-device(0)|||||R  
+ OBX|19|NM|150364^MDC\_TEMP\_BODY^MDC|1.0.0.6|36.5|268192^MDC\_DIM\_DEG C^MDC|||||R|||20100916145110+0000
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+  - a. Only one MSA segment is present and:
+    - MSA-1 is one of the following values:
+      - 'AA' – Accept Acknowledgment: Application Accept
+      - 'AR' – Accept Acknowledgment: Application Reject
+    - MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+    - MSA-3 to MSA-8 are empty
+  - b. If the ERR segment referring to the MSA is present:
+    - If the HFS receiver reports an ERR segment with severity E (Error) or F (Fatal Error), the Message Acknowledgement value shall be CR (Commit Reject)
+
+- ERR-1 is empty
+- ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>
+- ERR-3 starts with one of the following valid error condition codes and other optional subfields might be included:
+  - '0' – Message accepted
+  - '206' – Application record locked
+  - '207' – Application internal error
+- ERR-4 is set to one of these valid error severity values:
+  - 'W' – Warning
+  - 'I' – Information
+  - 'E' – Error
+  - 'F' – Fatal error.
+- ERR-5 and ERR-6 are empty
+- ERR-7 may be empty, but if it is valued, it is a text data
+- ERR-8 may be empty, but if it is valued, it is a text data
+- ERR-9 may be empty, but if it is valued, it is one of these values:
+  - 'PAT'
+  - 'NPAT'
+  - 'USR'
+  - 'HD'
+- ERR-10 may be empty, but if it is valued, it is encoded as: <Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+- ERR-11 may be empty, but if it is valued, it is encoded as: <Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+- ERR-12 may be empty, but if it is valued, it is encoded as: <WITHDRAWN Constituent> ^ <Telecommunication Use Code (ID)> ^ <Telecommunication Equipment Type (ID)> ^ <Communication Address (ST)> ^ <Country Code (NM)> ^ <Area/City Code (NM)> ^ <Local Number (NM)> ^ <Extension (NM)> ^ <Any Text (ST)> ^ <Extension Prefix (ST)> ^ <Speed Dial Code (ST)> ^ <Unformatted Telephone Number (ST)> ^ <Effective Start Date (DTM)> ^ <Expiration Date (DTM)> ^ <Expiration Reason (CWE)> ^ <Protection Code (CWE)> ^ <Shared Telecommunication Identifier (EI)> ^ <Preference Order (NM)>
+
+Where:
+
+- Expiration Reason subcomponents are: <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)>
+- Protection code subcomponents are: <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)>
+- Shared Telecommunication Identifier subcomponents are: <Entity Identifier (ST)> & <Namespace ID (IS)> & <Universal ID (ST)> & <Universal ID Type (ID)>
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | 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.                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>In step 2, all elements in each segment are as specified above</li> <li>Verify that the HFS receiver under test is able to accept the data and time stamps (e.g., if there is a log verify the date and the data are displayed in some form that indicates the correct date and time and the correct data as transmitted). Date and time of the measurement: 2010-09-16 14:51:10 UTC, Value: Body temperature= 36.5 [°C]</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+### A.7 Subgroup 2.4.6: Weighing scales (WEG)
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |                      |                     |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|---------------------|
+| <b>TP Id</b>             | TP/HFS/REC/PCD-01-DATA/WEG/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |                      |                     |
+| <b>TP label</b>          | MSA and ERR segments                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |                      |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [ITU-T H.812.1]       |                      |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | MSAUse; M             | MSA-1; M             | MSA-2; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | MSA-3; M              | MSA-4; M             | MSA-5; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | MSA-6; M              | MSA-7; M             | MSA-8; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | ERRUse 1; O           | ERRUse 2; M          | ERR-1; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | ERR-2; R              | ERR-3; M             | ERR-4; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | ERR-5; M              | ERR-6; M             | ERR-7; O            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | CWEDataType 1; M      | CWEDataType 2; M     | CWEDataType 3; C    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | CWEDataType 4; R      | NumericDataType 1; M | StringDataType 1; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | DateTimeDataType 1; M | EIDataType 1; M      | EIDataType 2; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | EIDataType 3; M       | EIDataType 4; M      | EIUse1; C           |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | EIUse2; C             | EIUse3; C            | EIUse4; C           |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | 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     |                      |                     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |                      |                     |
+| <b>Test purpose</b>      | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |                      |                     |
+| <b>Applicability</b>     | C_REC_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |                      |                     |
+| <b>Other PICS</b>        | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |                      |                     |
+| <b>Initial condition</b> | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation of a weighing scales device.                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |                      |                     |
+| <b>Test procedure</b>    | 1. The simulated HFS sender sends the following HL7 message, including the mandatory object of a weighing scales device inside a SOAP body to make the HFS receiver respond with another HL7 message:<br><br>MSH ^~\& AT4_AHD^1234567890ABCDEF^EUI-64   <current time in UTC>  ORU^R01^ORU_R01 MSGID<random number> P 2.6  NE AL   IHE PCD ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7<br><br>PID   789567^^^Imaginary Hospital^PI  Doe^John^Joseph^^^^L<br><br>OBR 1 WEGTest^AT4_AHD^1234567890ABCDEF^EUI-64 WEGTest^AT4_AHD^1234567890ABCDEF^EUI-64 182777000^monitoring of patient^SNOMED-CT   20100916145510+0000 |                       |                      |                     |
+
+OBX|1|531981^MDC\_MOC\_VMS\_MDS\_AHD^MDC|0|||||X|||||FEEDABEEDEADBE  
+EF^EUI-64
+
+OBX|2|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.1|2^auth-  
+body-continua|||||R
+
+OBX|3|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|0.0.0.1.1|  
+6.1|||||R
+
+OBX|4|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|0.  
+0.0.1.2|8207~24591~16399|||||R
+
+OBX|5|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.2|2^auth-  
+body-continua|||||R
+
+OBX|6|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|0.0  
+.0.2.1|1^unregulated-device(0)|||||R
+
+OBX|7|CWE|68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC|0.0.0.3|532224^MDC\_TIM  
+E\_SYNC\_NONE^MDC|||||R
+
+OBX|8|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.4|2^auth-  
+body-continua|||||R
+
+OBX|9|CWE|64515^MDC\_REG\_CERT\_DATA\_CONTINUA\_AHD\_CERT\_LIST^MDC|0  
+.0.0.4.1|0~1|||||R
+
+OBX|10||528399^MDC\_DEV\_SPEC\_PROFILE\_SCALE^MDC|1|||||X|||||1234567890  
+ABCDEF^EUI-64
+
+OBX|11|ST|531969^MDC\_ID\_MODEL\_NUMBER^MDC|1.0.0.1|WeighingScale  
+v1.5|||||R
+
+OBX|12|ST|531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC|1.0.0.2|AT4  
+Wireless|||||R
+
+OBX|13|DTM|67975^MDC\_ATTR\_TIME\_ABS^MDC|1.0.0.3|20100916145510+0000|||  
+R||20100916145510+0000
+
+OBX|14|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.4|2^auth-  
+body-continua|||||R
+
+OBX|15|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.5|2^auth-  
+body-continua|||||R
+
+OBX|16|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.4.1  
+|1.5|||||R
+
+OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|  
+1.0.0.4.2|16399|||||R
+
+OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.  
+0.0.5.1|0^unregulated-device(0)|||||R
+
+OBX|19|NM|188736^MDC\_MASS\_BODY\_ACTUAL^MDC|1.0.0.6|80|263875^MDC\_DI  
+M\_KILO\_G^MDC|||||R||20100916145510+0000
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+- a. Only one MSA segment is present and:
+    - MSA-1 is one of the following values:
+      - 'AA' – Accept Acknowledgment: Application Accept
+      - 'AR' – Accept Acknowledgment: Application Reject
+    - MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+    - MSA-3 to MSA-8 are empty
+  - b. If the ERR segment referring to the MSA is present:
+    - If the HFS receiver reports an ERR segment with severity E (Error) or F (Fatal Error), the Message Acknowledgement value shall be CR (Commit Reject)
+    - ERR-1 is empty
+
+- ❑ ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>
+  - ❑ ERR-3 starts with one of the following valid error condition codes and other optional subfields might be included:
+    - '0' – Message accepted
+    - '206' – Application record locked
+    - '207' – Application internal error
+  - ❑ ERR-4 is set to one of these valid error severity values:
+    - 'W' – Warning
+    - 'I' – Information
+    - 'E' – Error
+    - 'F' – Fatal error.
+  - ❑ ERR-5 and ERR-6 are empty
+  - ❑ ERR-7 may be empty, but if it is valued, it is a text data
+  - ❑ ERR-8 may be empty, but if it is valued, it is a text data
+  - ❑ ERR-9 may be empty, but if it is valued, it is one of these values:
+    - 'PAT'
+    - 'NPAT'
+    - 'USR'
+    - 'HD'
+  - ❑ ERR-10 may be empty, but if it is valued, it is encoded as: <Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+  - ❑ ERR-11 may be empty, but if it is valued, it is encoded as: <Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+  - ❑ ERR-12 may be empty, but if it is valued, it is encoded as: <WITHDRAWN Constituent> ^ <Telecommunication Use Code (ID)> ^ <Telecommunication Equipment Type (ID)> ^ <Communication Address (ST)> ^ <Country Code (NM)> ^ <Area/City Code (NM)> ^ <Local Number (NM)> ^ <Extension (NM)> ^ <Any Text (ST)> ^ <Extension Prefix (ST)> ^ <Speed Dial Code (ST)> ^ <Unformatted Telephone Number (ST)> ^ <Effective Start Date (DTM)> ^ <Expiration Date (DTM)> ^ <Expiration Reason (CWE)> ^ <Protection Code (CWE)> ^ <Shared Telecommunication Identifier (EI)> ^ <Preference Order (NM)>
+- Where:
+- Expiration Reason subcomponents are: <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)>
+  - Protection code subcomponents are: <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)>
+  - Shared Telecommunication Identifier subcomponents are: <Entity Identifier (ST)> & <Namespace ID (IS)> & <Universal ID (ST)> & <Universal ID Type (ID)>
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | 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.                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>In step 2, all elements in each segment are as specified above</li> <li>Verify that the HFS receiver under test is able to accept the data and time stamps (e.g., if there is a log verify the date and the data are displayed in some form that indicates the correct date and time and the correct data as transmitted). Date and time of the measurement: 2010-09-16 14:55:10 UTC, Values: Body Mass = 80 [kg]</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+### A.8 Subgroup 2.4.7: Glucose meter (GL)
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |                      |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|
+| <b>TP Id</b>             | TP/HFS/REC/PCD-01-DATA/GL/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |                      |
+| <b>TP label</b>          | MSA and ERR segments                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |                      |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ITU-T H.812.1]       |                      |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MSAUse; M             | MSA-1; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | MSA-3; M              | MSA-4; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | MSA-6; M              | MSA-7; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | ERRUse 1; O           | ERRUse 2; M          |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | ERR-2; R              | ERR-3; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | ERR-5; M              | ERR-6; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | CWEDataType 1; M      | CWEDataType 2; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | CWEDataType 4; R      | NumericDataType 1; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | DateTimeDataType 1; M | EIDataType 1; M      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EIDataType 3; M       | EIDataType 4; M      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EIUse2; C             | EIUse3; C            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | IDDataType 1; M       | ISDataType 1; M      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | XTNDataType 2; M      | XTNDataType 3; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | XTNDataType 5; M      | XTNDataType 6; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | XTNDataType 8; M      | XTNDataType 9; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | XTNDataType 11; M     |                      |
+| <b>Test purpose</b>      | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                       |                      |
+| <b>Applicability</b>     | C_REC_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |                      |
+| <b>Other PICS</b>        | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |                      |
+| <b>Initial condition</b> | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation of a glucose meter device.                                                                                                                                                                                                                                                                                                                                                                                                                                   |                       |                      |
+| <b>Test procedure</b>    | 1. The simulated HFS sender sends the following HL7 message, including the mandatory object of a glucose meter device inside a SOAP body to make the HFS receiver respond with another HL7 message:<br>MSH ^~\& AT4_AHD^1234567890ABCDEF^EUI-64   <current time in UTC>  ORU^R01^ORU_R01 MSGID<random number> P 2.6   NE AL   IHE PCD ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7<br>PID   789567^^Imaginary Hospital^PI  Doe^John^Joseph^^^L<br>OBR 1 GLTest^AT4_AHD^1234567890ABCDEF^EUI-64 GLTest^AT4_AHD^1234567890ABCDEF^EUI-64 182777000^monitoring of patient^SNOMED-CT   20100910141527+0000 |                       |                      |
+
+OBX|1|531981^MDC\_MOC\_VMS\_MDS\_AHD^MDC|0|||||X|||||FEEDABEEDEADBE  
+EF^EUI-64
+
+OBX|2|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.1|2^auth-  
+body-continua|||||R
+
+OBX|3|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|0.0.0.1.1|  
+6.1|||||R
+
+OBX|4|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|0.  
+0.0.1.2|17~8209~24593|||||R
+
+OBX|5|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.2|2^auth-  
+body-continua|||||R
+
+OBX|6|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|0.0  
+.0.2.1|1^unregulated-device(0)|||||R
+
+OBX|7|CWE|68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC|0.0.0.3|532224^MDC\_TIM  
+E\_SYNC\_NONE^MDC|||||R
+
+OBX|8|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.4|2^auth-  
+body-continua|||||R
+
+OBX|9|CWE|64515^MDC\_REG\_CERT\_DATA\_CONTINUA\_AHD\_CERT\_LIST^MDC|0  
+.0.0.4.1|0~1|||||R
+
+OBX|10||528401^MDC\_DEV\_SPEC\_PROFILE\_GLUCOSE^MDC|1|||||X|||||1234567  
+890ABCDEF^EUI-64
+
+OBX|11|ST|531969^MDC\_ID\_MODEL\_NUMBER^MDC|1.0.0.1|Glucose Meter  
+v1.0|||||R
+
+OBX|12|ST|531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC|1.0.0.2|AT4  
+Wireless|||||R
+
+OBX|13|DTM|67975^MDC\_ATTR\_TIME\_ABS^MDC|1.0.0.3|20100910141527+0000|||  
+|R||20100910141527+0000
+
+OBX|14|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.4|2^auth-  
+body-continua|||||R
+
+OBX|15|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.5|2^auth-  
+body-continua|||||R
+
+OBX|16|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.4.1  
+|1.0|||||R
+
+OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|  
+1.0.0.4.2|8209|||||R
+
+OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.  
+0.0.5.1|0^unregulated-device(0)|||||R
+
+OBX|19|NM|160184^MDC\_CONC\_GLU\_CAPILLARY\_WHOLEBLOOD^MDC|1.0.0.8|3  
+8|264274^MDC\_DIM\_MILLI\_G\_PER\_DL^MDC|||||R||20100910141527+0000
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+- a. Only one MSA segment is present and:
+    - MSA-1 is one of the following values:
+      - 'AA' – Accept Acknowledgment: Application Accept
+      - 'AR' – Accept Acknowledgment: Application Reject
+    - MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+    - MSA-3 to MSA-8 are empty
+  - b. If the ERR segment referring to the MSA is present:
+    - If the HFS receiver reports an ERR segment with severity E (Error) or F (Fatal Error), the Message Acknowledgement value shall be CR (Commit Reject)
+    - ERR-1 is empty
+
+- ❑ ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>
+  - ❑ ERR-3 starts with one of the following valid error condition codes and other optional subfields might be included:
+    - '0' – Message accepted
+    - '206' – Application record locked
+    - '207' – Application internal error
+  - ❑ ERR-4 is set to one of these valid error severity values:
+    - 'W' – Warning
+    - 'I' – Information
+    - 'E' – Error
+    - 'F' – Fatal error.
+  - ❑ ERR-5 and ERR-6 are empty
+  - ❑ ERR-7 may be empty, but if it is valued, it is a text data
+  - ❑ ERR-8 may be empty, but if it is valued, it is a text data
+  - ❑ ERR-9 may be empty, but if it is valued, it is one of these values:
+    - 'PAT'
+    - 'NPAT'
+    - 'USR'
+    - 'HD'
+  - ❑ ERR-10 may be empty, but if it is valued, it is encoded as: <Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+  - ❑ ERR-11 may be empty, but if it is valued, it is encoded as: <Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+  - ❑ ERR-12 may be empty, but if it is valued, it is encoded as: <WITHDRAWN Constituent> ^ <Telecommunication Use Code (ID)> ^ <Telecommunication Equipment Type (ID)> ^ <Communication Address (ST)> ^ <Country Code (NM)> ^ <Area/City Code (NM)> ^ <Local Number (NM)> ^ <Extension (NM)> ^ <Any Text (ST)> ^ <Extension Prefix (ST)> ^ <Speed Dial Code (ST)> ^ <Unformatted Telephone Number (ST)> ^ <Effective Start Date (DTM)> ^ <Expiration Date (DTM)> ^ <Expiration Reason (CWE)> ^ <Protection Code (CWE)> ^ <Shared Telecommunication Identifier (EI)> ^ <Preference Order (NM)>
+- Where:
+- Expiration Reason subcomponents are: <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)>
+  - Protection code subcomponents are: <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)>
+  - Shared Telecommunication Identifier subcomponents are: <Entity Identifier (ST)> & <Namespace ID (IS)> & <Universal ID (ST)> & <Universal ID Type (ID)>
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | 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.                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>In step 2, all elements in each segment are as specified above</li> <li>Verify that the HFS receiver under test is able to accept the data and time stamps (e.g., if there is a log verify the date and the data are displayed in some form that indicates the correct date and time and the correct data as transmitted). Date and time of the measurement: 2010-09-10 14:15:27 UTC, Values: Glucose capillary= 38 [mg/dl]</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+### A.9 Subgroup 2.4.8: Cardiovascular fitness and activity monitor (CV)
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                       |                      |                     |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|---------------------|
+| <b>TP Id</b>             | TP/HFS/REC/PCD-01-DATA/CV/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |                      |                     |
+| <b>TP label</b>          | MSA and ERR segments                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |                      |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [ITU-T H.812.1]       |                      |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | MSAUse; M             | MSA-1; M             | MSA-2; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MSA-3; M              | MSA-4; M             | MSA-5; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MSA-6; M              | MSA-7; M             | MSA-8; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | ERRUse 1; O           | ERRUse 2; M          | ERR-1; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | ERR-2; R              | ERR-3; M             | ERR-4; M            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | ERR-5; M              | ERR-6; M             | ERR-7; O            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | CWEDataType 1; M      | CWEDataType 2; M     | CWEDataType 3; C    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | CWEDataType 4; R      | NumericDataType 1; M | StringDataType 1; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | DateTimeDataType 1; M | EIDataType 1; M      | EIDataType 2; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | EIDataType 3; M       | EIDataType 4; M      | EIUse1; C           |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | EIUse2; C             | EIUse3; C            | EIUse4; C           |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | 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     |                      |                     |
+| <b>Test purpose</b>      | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                       |                      |                     |
+| <b>Applicability</b>     | C_REC_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |                      |                     |
+| <b>Other PICS</b>        | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |                      |                     |
+| <b>Initial condition</b> | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation of a cardiovascular device.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |                      |                     |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated HFS sender sends the following HL7 message, including the mandatory Session object and an optional object of a cardiovascular device inside a SOAP body to make the HFS receiver respond with another HL7 message:<br/><br/> MSH ^~\&amp; AT4_AHD^1234567890ABCDEF^EUI-64   &lt;current time in UTC&gt;  ORU^R01^ORU_R01 MSGID&lt;random number&gt; P 2.6   NE AL   IHE PCD ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7<br/><br/> PID   789567^^Imaginary Hospital^PI  Doe^John^Joseph^^^L<br/><br/> OBR 1 CVTest^AT4_AHD^1234567890ABCDEF^EUI-64 CVTest^AT4_AHD^1234567890ABCDEF^EUI-64 182777000^monitoring of patient^SNOMED-CT   20100910141527+0000</li> </ol> |                       |                      |                     |
+
+OBX|1||531981^MDC\_MOC\_VMS\_MDS\_AHD^MDC|0|||||X|||||FEEDABEEDEADBE  
+EF^EUI-64
+
+OBX|2|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.1|2^auth-  
+body-continua|||||R
+
+OBX|3|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|0.0.0.1.1|  
+6.1|||||R
+
+OBX|4|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|0.  
+0.0.1.2|41~8233|||||R
+
+OBX|5|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.2|2^auth-  
+body-continua|||||R
+
+OBX|6|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|0.0  
+.0.2.1|1^unregulated-device(0)|||||R
+
+OBX|7|CWE|68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC|0.0.0.3|532224^MDC\_TIM  
+E\_SYNC\_NONE^MDC|||||R
+
+OBX|8|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.4|2^auth-  
+body-continua|||||R
+
+OBX|9|CWE|64515^MDC\_REG\_CERT\_DATA\_CONTINUA\_AHD\_CERT\_LIST^MDC|0  
+.0.0.4.1|0~1|||||R
+
+OBX|10||528425^MDC\_DEV\_SPEC\_PROFILE\_HF\_CARDIO^MDC|1|||||X|||||123456  
+7890ABCDEF^EUI-64
+
+OBX|11|ST|531969^MDC\_ID\_MODEL\_NUMBER^MDC|1.0.0.1|CardioV v1.5|||||R
+
+OBX|12|ST|531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC|1.0.0.2|AT4  
+Wireless|||||R
+
+OBX|13|DTM|67975^MDC\_ATTR\_TIME\_ABS^MDC|1.0.0.3|20100910141527+0000|||  
+||R||20100910141527+0000
+
+OBX|14|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.4|2^auth-  
+body-continua|||||R
+
+OBX|15|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.5|2^auth-  
+body-continua|||||R
+
+OBX|16|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.4.1  
+|1.5|||||R
+
+OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|  
+1.0.0.4.2|41|||||R
+
+OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.  
+0.0.5.1|0^unregulated-device(0)|||||R
+
+OBX|19|CWE|8454267^MDC\_HF\_SESSION^MDC|1.0.0.6|8455155^MDC\_HF\_ACT\_R  
+UN^MDC|||||R||20100910141527+0000
+
+OBX|20|NM|68185^MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE^MDC|1.0.0.6.1|25|26432  
+04^MDC\_DIM\_SEC^MDC|||||R
+
+OBX|21|NM|8454254^MDC\_HF\_SPEED^MDC|1.0.0.7|38.1|26870^MDC\_DIM\_M\_PER  
+\_MIN^MDC|||||R||20100910141527+0000
+
+OBX|22|CWE|67883^MDC\_ATTR\_ID\_PHYSIO^MDC|1.0.0.7.1|8456146^MDC\_HF\_M  
+AX^MDC|||||R
+
+OBX|23|ST|68167^MDC\_ATTR\_SOURCE\_HANDLE\_REF^MDC|1.0.0.7.2|1.0.0.8|||||R
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+
+a. Only one MSA segment is present and:
+
+MSA-1 is one of the following values:
+
+- 'AA' – Accept Acknowledgment: Application Accept
+- 'AR' – Accept Acknowledgment: Application Reject
+
+MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+
+- MSA-3 to MSA-8 are empty
+  - b. If the ERR segment referring to the MSA is present:
+    - If the HFS receiver reports an ERR segment with severity E (Error) or F (Fatal Error), the Message Acknowledgement value shall be CR (Commit Reject)
+    - ERR-1 is empty
+    - ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>
+    - ERR-3 starts with one of the following valid error condition codes and other optional subfields might be included:
+      - '0' – Message accepted
+      - '206' – Application record locked
+      - '207' – Application internal error
+    - ERR-4 is set to one of these valid error severity values:
+      - 'W' – Warning
+      - 'I' – Information
+      - 'E' – Error
+      - 'F' – Fatal error.
+    - ERR-5 and ERR-6 are empty
+    - ERR-7 may be empty, but if it is valued, it is a text data
+    - ERR-8 may be empty, but if it is valued, it is a text data
+    - ERR-9 may be empty, but if it is valued, it is one of these values:
+      - 'PAT'
+      - 'NPAT'
+      - 'USR'
+      - 'HD'
+    - ERR-10 may be empty, but if it is valued, it is encoded as: <Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+    - ERR-11 may be empty, but if it is valued, it is encoded as: <Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+    - ERR-12 may be empty, but if it is valued, it is encoded as: <WITHDRAWN Constituent> ^ <Telecommunication Use Code (ID)> ^ <Telecommunication Equipment Type (ID)> ^ <Communication Address (ST)> ^ <Country Code (NM)> ^ <Area/City Code (NM)> ^ <Local Number (NM)> ^ <Extension (NM)> ^ <Any Text (ST)> ^ <Extension Prefix (ST)> ^ <Speed Dial Code (ST)> ^ <Unformatted Telephone Number (ST)> ^ <Effective Start Date (DTM)> ^ <Expiration Date (DTM)> ^ <Expiration Reason (CWE)> ^ <Protection Code (CWE)> ^ <Shared Telecommunication Identifier (EI)> ^ <Preference Order (NM)>
+- Where:
+- Expiration Reason subcomponents are: <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)>
+  - Protection code subcomponents are: <Identifier (ST)>&<Text (ST)>&< Name of Coding System (ID)> &<Alternate Identifier (ST)>&<Alternate Text (ST)>&<Name of Alternate Coding System (ID)>&<Coding System
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><i>Version ID (ST)&gt;&lt;Alternate Coding System Version ID (ST)&gt;&lt;Original Text (ST)&gt;</i></p> <ul style="list-style-type: none"> <li>Shared Telecommunication Identifier subcomponents are: <i>&lt;Entity Identifier (ST)&gt;&lt;Namespace ID (IS)&gt;&lt;Universal ID (ST)&gt;&lt;Universal ID Type (ID)&gt;</i></li> </ul> <p>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.</p>   |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>In step 2, all elements in each segment are as specified above.</li> <li>Verify that the HFS receiver under test is able to accept the data and time stamps (e.g., if there is a log verify the date and the data are displayed in some form that indicates the correct date and time and the correct data as transmitted). Date and time of the measurement: 2010-09-10 14:15:27 UTC, Values: Speed= 38.1 [m/min]</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+### A.10 Subgroup 2.4.9: Strength fitness equipment (ST)
+
+|                          |                                                                                                                                                                                                                                                                                  |                       |                      |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|
+| <b>TP Id</b>             | TP/HFS/REC/PCD-01-DATA/ST/BV-000                                                                                                                                                                                                                                                 |                       |                      |
+| <b>TP label</b>          | MSA and ERR segments                                                                                                                                                                                                                                                             |                       |                      |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                      | [ITU-T H.812.1]       |                      |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                            | MSAUse; M             | MSA-1; M             |
+|                          |                                                                                                                                                                                                                                                                                  | MSA-3; M              | MSA-4; M             |
+|                          |                                                                                                                                                                                                                                                                                  | MSA-6; M              | MSA-7; M             |
+|                          |                                                                                                                                                                                                                                                                                  | ERRUse 1; O           | ERRUse 2; M          |
+|                          |                                                                                                                                                                                                                                                                                  | ERR-2; R              | ERR-3; M             |
+|                          |                                                                                                                                                                                                                                                                                  | ERR-5; M              | ERR-6; M             |
+|                          |                                                                                                                                                                                                                                                                                  | CWEDataType 1; M      | CWEDataType 2; M     |
+|                          |                                                                                                                                                                                                                                                                                  | CWEDataType 4; R      | NumericDataType 1; M |
+|                          |                                                                                                                                                                                                                                                                                  | DateTimeDataType 1; M | EIDataType 1; M      |
+|                          |                                                                                                                                                                                                                                                                                  | EIDataType 3; M       | EIDataType 4; M      |
+|                          |                                                                                                                                                                                                                                                                                  | EIUse2; C             | EIUse3; C            |
+|                          |                                                                                                                                                                                                                                                                                  | IDDataType 1; M       | ISDataType 1; M      |
+|                          |                                                                                                                                                                                                                                                                                  | XTNDataType 2; M      | XTNDataType 3; M     |
+|                          |                                                                                                                                                                                                                                                                                  | XTNDataType 5; M      | XTNDataType 6; M     |
+|                          |                                                                                                                                                                                                                                                                                  | XTNDataType 8; M      | XTNDataType 9; M     |
+|                          |                                                                                                                                                                                                                                                                                  | XTNDataType 11; M     |                      |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The elements of every segment of the message</p> <p>[AND]</p> <p>The data type of each element.</p>                                                                                                                                                        |                       |                      |
+| <b>Applicability</b>     | C_REC_000                                                                                                                                                                                                                                                                        |                       |                      |
+| <b>Other PICS</b>        | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                   |                       |                      |
+| <b>Initial condition</b> | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation of a strength fitness device.                                                                                                            |                       |                      |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated HFS sender sends the following HL7 message, including the mandatory Set object and an optional object of a strength fitness device inside a SOAP body to make the HFS receiver respond with another HL7 message:</li> </ol> |                       |                      |
+
+MSH|^~\&|AT4\_AHD^1234567890ABCDEF^EUI-64|||current time in  
+ UTC>||ORU^R01^ORU\_R01|MSGID<random number>|P|2.6||NE|AL|||||IHE PCD  
+ ORU-R012006^HL7^2.16.840.1.1.13883.9.n.m^HL7
+
+PID|||789567^^^Imaginary Hospital^PI||Doe^John^Joseph^^^L
+
+OBR|1|STTest^AT4\_AHD^1234567890ABCDEF^EUI-  
+ 64|STTest^AT4\_AHD^1234567890ABCDEF^EUI-64|182777000^monitoring of  
+ patient^SNOMED-CT|||20100919211841+0000
+
+OBX|1||531981^MDC\_MOC\_VMS\_MDS\_AHD^MDC|0|||||X|||||FEEDABEEDEADBE  
+EF^EUI-64
+
+OBX|2|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.1|2^auth-  
+body-continua|||||R
+
+OBX|3|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|0.0.0.1.1|  
+6.1|||||R
+
+OBX|4|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|0.  
+0.0.1.2|42~8234~16426|||||R
+
+OBX|5|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.2|2^auth-  
+body-continua|||||R
+
+OBX|6|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|0.0  
+.0.2.1|1^unregulated-device(0)|||||R
+
+OBX|7|CWE|68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC|0.0.0.3|532224^MDC\_TIM  
+E\_SYNC\_NONE^MDC|||||R
+
+OBX|8|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.4|2^auth-  
+body-continua|||||R
+
+OBX|9|CWE|64515^MDC\_REG\_CERT\_DATA\_CONTINUA\_AHD\_CERT\_LIST^MDC|0  
+.0.0.4.1|0~1|||||R
+
+OBX|10||528426^MDC\_DEV\_SPEC\_PROFILE\_HF\_STRENGTH^MDC|1|||||X|||||123  
+4567890ABCDEF^EUI-64
+
+OBX|11|ST|531969^MDC\_ID\_MODEL\_NUMBER^MDC|1.0.0.1|StrengthFitness  
+v1.5|||||R
+
+OBX|12|ST|531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC|1.0.0.2|AT4  
+Wireless|||||R
+
+OBX|13|DTM|67975^MDC\_ATTR\_TIME\_ABS^MDC|1.0.0.3|20100919211841+0000|||  
+R||20100919211841+0000
+
+OBX|14|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.4|2^auth-  
+body-continua|||||R
+
+OBX|15|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.5|2^auth-  
+body-continua|||||R
+
+OBX|16|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.4.1  
+|1.5|||||R
+
+OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|  
+1.0.0.4.2|16426|||||R
+
+OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.  
+0.0.5.1|0^unregulated-device(0)|||||R
+
+OBX|19|NM|8454344^MDC\_HF\_SET^MDC|1.0.0.6|||||R||20100919211841+0000|||||  
+459284^MDC\_MUSC\_THORAX\_PECTORAL\_MAJOR^MDC
+
+OBX|20|NM|68185^MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE^MDC|1.0.0.6.1|25|26432  
+0^MDC\_DIM\_SEC^MDC|||||R
+
+OBX|21|NM|8454346^MDC\_HF\_REPETITION\_COUNT^MDC|1.0.0.7|12|262656^MDC  
+\_DIM\_DIMLESS^MDC|||||R||20100919211841+0000
+
+OBX|22|ST|68167^MDC\_ATTR\_SOURCE\_HANDLE\_REF^MDC|1.0.0.7.1|1.0.0.6|||||R
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+  - a. Only one MSA segment is present and:
+    - MSA-1 is one of the following values:
+
+- 'AA' – Accept Acknowledgment: Application Accept
+  - 'AR' – Accept Acknowledgment: Application Reject
+- MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+  - MSA-3 to MSA-8 are empty
+- b. If the ERR segment referring to the MSA is present:
+- If the HFS receiver reports an ERR segment with severity E (Error) or F (Fatal Error), the Message Acknowledgement value shall be CR (Commit Reject)
+  - ERR-1 is empty
+  - ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>
+  - ERR-3 starts with one of the following valid error condition codes and other optional subfields might be included:
+    - '0' – Message accepted
+    - '206' – Application record locked
+    - '207' – Application internal error
+  - ERR-4 is set to one of these valid error severity values:
+    - 'W' – Warning
+    - 'I' – Information
+    - 'E' – Error
+    - 'F' – Fatal error.
+  - ERR-5 and ERR-6 are empty
+  - ERR-7 may be empty, but if it is valued, it is a text data
+  - ERR-8 may be empty, but if it is valued, it is a text data
+  - ERR-9 may be empty, but if it is valued, it is one of these values:
+    - 'PAT'
+    - 'NPAT'
+    - 'USR'
+    - 'HD'
+  - ERR-10 may be empty, but if it is valued, it is encoded as: <Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+  - ERR-11 may be empty, but if it is valued, it is encoded as: <Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+  - ERR-12 may be empty, but if it is valued, it is encoded as: <WITHDRAWN Constituent> ^ <Telecommunication Use Code (ID)> ^ <Telecommunication Equipment Type (ID)> ^ <Communication Address (ST)> ^ <Country Code (NM)> ^ <Area/City Code (NM)> ^ <Local Number (NM)> ^ <Extension (NM)> ^ <Any Text (ST)> ^ <Extension Prefix (ST)> ^ <Speed Dial Code (ST)> ^ <Unformatted Telephone Number (ST)> ^ <Effective Start Date (DTM)> ^ <Expiration Date (DTM)> ^ <Expiration Reason (CWE)> ^ <Protection Code (CWE)> ^ <Shared Telecommunication Identifier (EI)> ^ <Preference Order (NM)>
+- Where:
+- Expiration Reason subcomponents are: <Identifier (ST)> & <Text (ST)> & < Name of Coding System (ID)> & <Alternate Identifier (ST)> & <Alternate Text (ST)> & <Name of Alternate Coding System (ID)> & <Coding System
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><i>Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></p> <ul style="list-style-type: none"> <li>• Protection code subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt;Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li> <li>• Shared Telecommunication Identifier subcomponents are: <i>&lt;Entity Identifier (ST)&gt;&amp;&lt;Namespace ID (IS)&gt;&amp;&lt;Universal ID (ST)&gt;&amp;&lt;Universal ID Type (ID)&gt;</i></li> </ul> <p>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.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2, all elements in each segment are as specified above</li> <li>• Verify that the HFS receiver under test is able to accept the data and time stamps (e.g., if there is a log verify the date and the data are displayed in some form that indicates the correct date and time and the correct data as transmitted). Date and time of the measurement: 2010-09-19 21:18:41 UTC, Values: Repetition Count = 12 [dimless]</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+### A.11 Subgroup 2.4.10: Independent living activity hub (HUB)
+
+|                          |                                                                                                                                                                              |                       |                      |                     |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|---------------------|
+| <b>TP Id</b>             | TP/HFS/REC/PCD-01-DATA/HUB/BV-000                                                                                                                                            |                       |                      |                     |
+| <b>TP label</b>          | MSA and ERR segments                                                                                                                                                         |                       |                      |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                  | [ITU-T H.812.1]       |                      |                     |
+|                          | <b>Testable items</b>                                                                                                                                                        | MSAUse; M             | MSA-1; M             | MSA-2; M            |
+|                          |                                                                                                                                                                              | MSA-3; M              | MSA-4; M             | MSA-5; M            |
+|                          |                                                                                                                                                                              | MSA-6; M              | MSA-7; M             | MSA-8; M            |
+|                          |                                                                                                                                                                              | ERRUse 1; O           | ERRUse 2; M          | ERR-1; M            |
+|                          |                                                                                                                                                                              | ERR-2; R              | ERR-3; M             | ERR-4; M            |
+|                          |                                                                                                                                                                              | ERR-5; M              | ERR-6; M             | ERR-7; O            |
+|                          |                                                                                                                                                                              | CWEDataType 1; M      | CWEDataType 2; M     | CWEDataType 3; C    |
+|                          |                                                                                                                                                                              | CWEDataType 4; R      | NumericDataType 1; M | StringDataType 1; M |
+|                          |                                                                                                                                                                              | DateTimeDataType 1; M | EIDataType 1; M      | EIDataType 2; M     |
+|                          |                                                                                                                                                                              | EIDataType 3; M       | EIDataType 4; M      | EIUse1; C           |
+|                          |                                                                                                                                                                              | EIUse2; C             | EIUse3; C            | EIUse4; C           |
+|                          |                                                                                                                                                                              | 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     |                      |                     |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The elements of every segment of the message</p> <p>[AND]</p> <p>The data type of each element.</p>                                                    |                       |                      |                     |
+| <b>Applicability</b>     | C_REC_000                                                                                                                                                                    |                       |                      |                     |
+| <b>Other PICS</b>        | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                               |                       |                      |                     |
+| <b>Initial condition</b> | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation of an independent living hub device. |                       |                      |                     |
+
+|                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <p><b>Test procedure</b></p> | <ol style="list-style-type: none"> <li>1. The simulated HFS sender sends the following HL7 message, including one of the optional objects of an independent living hub device inside a SOAP body to make the HFS receiver respond with another HL7 message: <p>MSH ^~\&amp; AT4_AHD^1234567890ABCDEF^EUI-64   &lt;current time in UTC&gt;  ORU^R01^ORU_R01 MSGID&lt;random number&gt; P 2.6   NE AL   IHE PCD ORU-R012006^HL7^2.16.840.1.1.13883.9.n.m^HL7</p> <p>PID   789567^^^Imaginary Hospital^PI  Doe^John^Joseph^^^L</p> <p>OBR 1 HUBTest^AT4_AHD^1234567890ABCDEF^EUI-64 HUBTest^AT4_AHD^1234567890ABCDEF^EUI-64 182777000^monitoring of patient^SNOMED-CT   20100920203341+0000</p> <p>OBX 1  531981^MDC_MOC_VMS_MDS_AHD^MDC 0     X     FEEDABEEDEADBE EF^EUI-64</p> <p>OBX 2 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.1 2^auth-body-continua    R</p> <p>OBX 3 ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 0.0.0.1.1 6.1    R</p> <p>OBX 4 NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 0.0.0.1.2 71~8263~16455    R</p> <p>OBX 5 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.2 2^auth-body-continua    R</p> <p>OBX 6 CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC 0.0.0.2.1 1^unregulated-device(0)    R</p> <p>OBX 7 CWE 68220^MDC_TIME_SYNC_PROTOCOL^MDC 0.0.0.3 532224^MDC_TIME_SYNC_NONE^MDC    R</p> <p>OBX 8 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.4 2^auth-body-continua    R</p> <p>OBX 9 CWE 64515^MDC_REG_CERT_DATA_CONTINUA_AHD_CERT_LIST^MDC 0.0.0.4.1 0~1    R</p> <p>OBX 10  528455^MDC_DEV_SPEC_PROFILE_AI_ACTIVITY_HUB^MDC 1     X     1234567890ABCDEF^EUI-64</p> <p>OBX 11 ST 531969^MDC_ID_MODEL_NUMBER^MDC 1.0.0.1 HUB v1.5    R</p> <p>OBX 12 ST 531970^MDC_ID_MODEL_MANUFACTURER^MDC 1.0.0.2 AT4 Wireless    R</p> <p>OBX 13 DTM 67975^MDC_ATTR_TIME_ABS^MDC 1.0.0.3 20100920203341+0000    R</p> <p>OBX 14 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.4 2^auth-body-continua    R</p> <p>OBX 15 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.5 2^auth-body-continua    R</p> <p>OBX 16 ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 1.0.0.4.1 1.5    R</p> <p>OBX 17 NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 1.0.0.4.2 16455    R</p> <p>OBX 18 CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC 1.0.0.5.1 0^unregulated-device(0)    R</p> <p>OBX 19 CWE 8519681^MDC_AI_TYPE_SENSOR_FALL^MDC 1.0.0.6 1^fall-detected(0)    R</p> <p>OBX 20 CWE 8520703^MDC_AI_LOCATION^MDC 1.0.0.6.1 8522816^MDC_AI_LOCATION_BEDROOMMASTER^MDC    R</p> </li> <li>2. The HFS receiver under test responds using another HL7 message. Check in the captured message that: <ol style="list-style-type: none"> <li>a. Only one MSA segment is present and: <ul style="list-style-type: none"> <li><input type="checkbox"/> MSA-1 is one of the following values: <ul style="list-style-type: none"> <li>• 'AA' – Accept Acknowledgment: Application Accept</li> </ul> </li> </ul> </li> </ol> </li> </ol> |
+|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+- 'AR' – Accept Acknowledgment: Application Reject
+  - MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+  - MSA-3 to MSA-8 are empty
+- b. If the ERR segment referring to the MSA is present:
+- If the HFS receiver reports an ERR segment with severity E (Error) or F (Fatal Error), the Message Acknowledgement value shall be CR (Commit Reject)
+  - ERR-1 is empty
+  - ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>
+  - ERR-3 starts with one of the following valid error condition codes and other optional subfields might be included:
+    - '0' – Message accepted
+    - '206' – Application record locked
+    - '207' – Application internal error
+  - ERR-4 is set to one of these valid error severity values:
+    - 'W' – Warning
+    - 'I' – Information
+    - 'E' – Error
+    - 'F' – Fatal error.
+  - ERR-5 and ERR-6 are empty
+  - ERR-7 may be empty, but if it is valued, it is a text data
+  - ERR-8 may be empty, but if it is valued, it is a text data
+  - ERR-9 may be empty, but if it is valued, it is one of these values:
+    - 'PAT'
+    - 'NPAT'
+    - 'USR'
+    - 'HD'
+  - ERR-10 may be empty, but if it is valued, it is encoded as: <Identifier (ST)>^<Text (ST)>^< Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+  - ERR-11 may be empty, but if it is valued, it is encoded as: <Identifier (ST)>^<Text (ST)>^< Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+  - ERR-12 may be empty, but if it is valued, it is encoded as: <WITHDRAWN Constituent>^<Telecommunication Use Code (ID)>^<Telecommunication Equipment Type (ID)>^<Communication Address (ST)>^<Country Code (NM)>^<Area/City Code (NM)>^<Local Number (NM)>^<Extension (NM)>^<Any Text (ST)>^<Extension Prefix (ST)>^<Speed Dial Code (ST)>^<Unformatted Telephone Number (ST)>^<Effective Start Date (DTM)>^<Expiration Date (DTM)>^<Expiration Reason (CWE)>^<Protection Code (CWE)>^<Shared Telecommunication Identifier (EI)>^<Preference Order (NM)>
+- Where:
+- Expiration Reason subcomponents are: <Identifier (ST)>&<Text (ST)>&< Name of Coding System (ID)> &<Alternate Identifier (ST)>&<Alternate Text (ST)>&<Name of Alternate Coding System (ID)>&<Coding System
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><i>Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></p> <ul style="list-style-type: none"> <li>• Protection code subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt;Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li> <li>• Shared Telecommunication Identifier subcomponents are: <i>&lt;Entity Identifier (ST)&gt;&amp;&lt;Namespace ID (IS)&gt;&amp;&lt;Universal ID (ST)&gt;&amp;&lt;Universal ID Type (ID)&gt;</i></li> </ul> <p>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.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2, all elements in each segment are as specified above</li> <li>• Verify that the HFS receiver under test is able to accept the data and time stamps (e.g., if there is a log verify the date and the data are displayed in some form that indicates the correct date and time and the correct data as transmitted). Date and time of the measurement: 2010-09-20 20:33:41 UTC, Values: Fall Sensor = "fall detected" [dimless]</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+### A.12 Subgroup 2.4.11: Adherence monitor (AM)
+
+|                          |                                                                                                                                                                         |                       |                      |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|
+| <b>TP Id</b>             | TP/HFS/REC/PCD-01-DATA/AM/BV-000                                                                                                                                        |                       |                      |
+| <b>TP label</b>          | MSA and ERR segments                                                                                                                                                    |                       |                      |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                             | [ITU-T H.812.1]       |                      |
+|                          | <b>Testable items</b>                                                                                                                                                   | MSAUse; M             | MSA-1; M             |
+|                          |                                                                                                                                                                         | MSA-3; M              | MSA-4; M             |
+|                          |                                                                                                                                                                         | MSA-6; M              | MSA-7; M             |
+|                          |                                                                                                                                                                         | ERRUse 1; O           | ERRUse 2; M          |
+|                          |                                                                                                                                                                         | ERR-2; R              | ERR-3; M             |
+|                          |                                                                                                                                                                         | ERR-5; M              | ERR-6; M             |
+|                          |                                                                                                                                                                         | CWEDataType 1; M      | CWEDataType 2; M     |
+|                          |                                                                                                                                                                         | CWEDataType 4; R      | NumericDataType 1; M |
+|                          |                                                                                                                                                                         | DateTimeDataType 1; M | EIDataType 1; M      |
+|                          |                                                                                                                                                                         | EIDataType 3; M       | EIDataType 4; M      |
+|                          |                                                                                                                                                                         | EIUse2; C             | EIUse3; C            |
+|                          |                                                                                                                                                                         | IDDataType 1; M       | ISDataType 1; M      |
+|                          |                                                                                                                                                                         | XTNDataType 2; M      | XTNDataType 3; M     |
+|                          |                                                                                                                                                                         | XTNDataType 5; M      | XTNDataType 6; M     |
+|                          |                                                                                                                                                                         | XTNDataType 8; M      | XTNDataType 9; M     |
+|                          |                                                                                                                                                                         | XTNDataType 11; M     |                      |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The elements of every segment of the message</p> <p>[AND]</p> <p>The data type of each element.</p>                                               |                       |                      |
+| <b>Applicability</b>     | C_REC_000                                                                                                                                                               |                       |                      |
+| <b>Other PICS</b>        | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                          |                       |                      |
+| <b>Initial condition</b> | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation of an adherence monitor device. |                       |                      |
+
+|                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test procedure</b> | <p>1. The simulated HFS sender sends the following HL7 message, including the mandatory object of the standard configuration (7201) adherence monitor device inside a SOAP body to make the HFS receiver respond with another HL7 message:</p> <pre> MSH ^~\&amp; AT4_AHD^1234567890ABCDEF^EUI-64  &lt;current time in UTC&gt;  ORU^R01^ORU_R01 MSGID&lt;random number&gt; P 2.6  NE AL     IHE PCD ORU-R012006^HL7^2.16.840.1.1.13883.9.n.m^HL7  PID   789567^^^Imaginary Hospital^PI  Doe^John^Joseph^^^L  OBR 1 AMTest^AT4_AHD^1234567890ABCDEF^EUI- 64 AMTest^AT4_AHD^1234567890ABCDEF^EUI-64 182777000^monitoring of patient^SNOMED-CT   20100921123934+0000  OBX 1  531981^MDC_MOC_VMS_MDS_AHD^MDC 0     X     FEEDABEEDEADBE EF^EUI-64  OBX 2 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.1 2^auth- body-continua     R  OBX 3 ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 0.0.0.1.1  6.1     R  OBX 4 NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 0. 0.0.1.2 16456~8264     R  OBX 5 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.2 2^auth- body-continua     R  OBX 6 CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC 0.0 .0.2.1 1^unregulated-device(0)     R  OBX 7 CWE 68220^MDC_TIME_SYNC_PROTOCOL^MDC 0.0.0.3 532224^MDC_TIM E_SYNC_NONE^MDC     R  OBX 8 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.4 2^auth- body-continua     R  OBX 9 CWE 64515^MDC_REG_CERT_DATA_CONTINUA_AHD_CERT_LIST^MDC 0 .0.0.4.1 0~1     R  OBX 10  528456^MDC_DEV_SPEC_PROFILE_AI_MED_MINDER^MDC 1     X     1 234567890ABCDEF^EUI-64  OBX 11 ST 531969^MDC_ID_MODEL_NUMBER^MDC 1.0.0.1 Adherence Mon v1.5     R  OBX 12 ST 531970^MDC_ID_MODEL_MANUFACTURER^MDC 1.0.0.2 AT4 Wireless     R  OBX 13 DTM 67975^MDC_ATTR_TIME_ABS^MDC 1.0.0.3 20100921123934+0000      R  20100921123934+0000  OBX 14 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.4 2^auth- body-continua     R  OBX 15 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.5 2^auth- body-continua     R  OBX 16 ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 1.0.0.4.1  1.5     R  OBX 17 NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC  1.0.0.4.2 16456     R  OBX 18 CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC 1. 0.0.5.1 0^unregulated-device(0)     R  OBX 19 NM 8532992^MDC_AI_MED_DISPENSED_FIXED^MDC 1.0.0.6 44 262656^ MDC_DIM_DIMLESS^MDC     R  20100921123934+0000  OBX 20 CWE 8532994^MDC_AI_MED_STATUS^MDC 1.0.0.7 1^medication-course- complete(4)     R  OBX 21  8532995^MDC_AI_MED_FEEDBACK^MDC 1.0.1     X  OBX 22 NM 8532996^MDC_AI_MED_UF_LOCATION^MDC 1.0.1.1 5     R  20100921 123934+0000 </pre> |
+|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+OBX|23|NM|8532997^MDC\_AI\_MED\_UF\_RESPONSE^MDC|1.0.1.2|3|||||R|||2010092  
+1123934+0000
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+
+a. Only one MSA segment is present and:
+
+- MSA-1 is one of the following values:
+  - 'AA' – Accept Acknowledgment: Application Accept
+  - 'AR' – Accept Acknowledgment: Application Reject
+- MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+- MSA-3 to MSA-8 are empty
+
+b. If the ERR segment referring to the MSA is present:
+
+- If the HFS receiver reports an ERR segment with severity E (Error) or F (Fatal Error), the Message Acknowledgement value shall be CR (Commit Reject)
+- ERR-1 is empty
+- ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>
+- ERR-3 starts with one of the following valid error condition codes and other optional subfields might be included:
+  - '0' – Message accepted
+  - '206' – Application record locked
+  - '207' – Application internal error
+- ERR-4 is set to one of these valid error severity values:
+  - 'W' – Warning
+  - 'I' – Information
+  - 'E' – Error
+  - 'F' – Fatal error.
+- ERR-5 and ERR-6 are empty
+- ERR-7 may be empty, but if it is valued, it is a text data
+- ERR-8 may be empty, but if it is valued, it is a text data
+- ERR-9 may be empty, but if it is valued, it is one of these values:
+  - 'PAT'
+  - 'NPAT'
+  - 'USR'
+  - 'HD'
+- ERR-10 may be empty, but if it is valued, it is encoded as: <Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+- ERR-11 may be empty, but if it is valued, it is encoded as: <Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)> the rest of the elements of the CWE data type are not used in the Services interface.
+- ERR-12 may be empty, but if it is valued, it is encoded as: <WITHDRAWN Constituent> ^ <Telecommunication Use Code (ID)> ^ <Telecommunication Equipment Type (ID)> ^ <Communication Address (ST)> ^ <Country Code (NM)> ^ <Area/City Code (NM)> ^ <Local Number (NM)> ^ <Extension (NM)> ^ <Any Text (ST)> ^ <Extension Prefix (ST)> ^ <Speed Dial Code (ST)> ^ <Unformatted Telephone Number (ST)> ^ <Effective Start Date
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>(DTM)&gt;^&lt;Expiration Date (DTM)&gt;^&lt;Expiration Reason (CWE)&gt;^&lt;Protection Code (CWE)&gt;^&lt;Shared Telecommunication Identifier (EI)&gt;^&lt;Preference Order (NM)&gt;</p> <p>Where:</p> <ul style="list-style-type: none"> <li>• Expiration Reason subcomponents are: &lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt;Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</li> <li>• Protection code subcomponents are: &lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt;Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</li> <li>• Shared Telecommunication Identifier subcomponents are: &lt;Entity Identifier (ST)&gt;&amp;&lt;Namespace ID (IS)&gt;&amp;&lt;Universal ID (ST)&gt;&amp;&lt;Universal ID Type (ID)&gt;</li> </ul> <p>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.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2, all elements in each segment are as specified above</li> <li>• Verify that the HFS receiver under test is able to accept the data and time stamps (e.g., if there is a log verify the date and the data are displayed in some form that indicates the correct date and time and the correct data as transmitted). Date and time of the measurements: 2010-09-21 12:39:34 UTC, Values: Fixed Dosage Dispensed = 44 [dimless], Status = "medication course completed", Feedback Location = 5 [dimless] and Feedback Response = 3 [dimless]</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              | <p>[AT4]: Possible Continua DG v2011 bug. Step 2.d shows the expected OBX segment as specified in Continua DG v2011 – Appendix J Table J-29. Based on similarity between BPM and AM compound values, we understand that correct OBX segment should be:</p> <p>User Feedback Channel object follows this OBX encoding:</p> <ul style="list-style-type: none"> <li>• OBX-2 is empty</li> <li>• OBX-3 = 8532995^MDC_AI_MED_FEEDBACK^MDC</li> <li>• 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.</li> <li>• OBX-5 is empty</li> <li>• OBX-11 = 'X'</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+### A.13 Subgroup 2.4.12: Peak expiratory flow monitor (PF)
+
+|                 |                                  |                                                                                                                                                              |                                                                                                                                                           |                                                                                                                                                 |
+|-----------------|----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>TP Id</b>    | TP/HFS/REC/PCD-01-DATA/PF/BV-000 |                                                                                                                                                              |                                                                                                                                                           |                                                                                                                                                 |
+| <b>TP label</b> | MSA and ERR segments             |                                                                                                                                                              |                                                                                                                                                           |                                                                                                                                                 |
+| <b>Coverage</b> | <b>Spec</b>                      | [ITU-T H.812.1]                                                                                                                                              |                                                                                                                                                           |                                                                                                                                                 |
+|                 | <b>Testable items</b>            | MSAUse; M<br>MSA-3; M<br>MSA-6; M<br>ERRUse 1; O<br>ERR-2; R<br>ERR-5; M<br>CWEDataType 1; M<br>CWEDataType 4; R<br>DateTimeDataType 1; M<br>EIDataType 3; M | MSA-1; M<br>MSA-4; M<br>MSA-7; M<br>ERRUse 2; M<br>ERR-3; M<br>ERR-6; M<br>CWEDataType 2; M<br>NumericDataType 1; M<br>EIDataType 1; M<br>EIDataType 4; M | MSA-2; M<br>MSA-5; M<br>MSA-8; M<br>ERR-1; M<br>ERR-4; M<br>ERR-7; O<br>CWEDataType 3; C<br>StringDataType 1; M<br>EIDataType 2; M<br>EIUse1; C |
+
+|                          |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                  |                   |
+|--------------------------|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-------------------|
+|                          |  | EIUse2; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | EIUse3; C        | EIUse4; C         |
+|                          |  | 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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                  |                   |
+| <b>Test purpose</b>      |  | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                  |                   |
+| <b>Applicability</b>     |  | C_REC_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                  |                   |
+| <b>Other PICS</b>        |  | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                  |                   |
+| <b>Initial condition</b> |  | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation of a peak flow device.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                  |                   |
+| <b>Test procedure</b>    |  | 1. The simulated HFS sender sends the following HL7 message, including the mandatory objects of a peak flow device inside a SOAP body to make the HFS receiver respond with another HL7 message:<br>MSH ^~\& AT4_AHD^1234567890ABCDEF^EUI-64   <current time in UTC>  ORU^R01^ORU_R01 MSGID<random number> P 2.6  NE AL    IHE PCD ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7<br>PID   789567^^Imaginary Hospital^PI  Doe^John^Joseph^^^L<br>OBR 1 PFTest^AT4_AHD^1234567890ABCDEF^EUI-64 PFTest^AT4_AHD^1234567890ABCDEF^EUI-64 182777000^monitoring of patient^SNOMED-CT   20100921124034+0000<br>OBX 1 531981^MDC_MOC_VMS_MDS_AHD^MDC 0     X     FEEDABEEDEADBE EF^EUI-64<br>OBX 2 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.1 2^auth-body-continua     R<br>OBX 3 ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 0.0.0.1.1 6.1     R<br>OBX 4 NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 0.0.0.1.2 16405~8213~24597     R<br>OBX 5 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.2 2^auth-body-continua     R<br>OBX 6 CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC 0.0.0.2.1 1^unregulated-device(0)     R<br>OBX 7 CWE 68220^MDC_TIME_SYNC_PROTOCOL^MDC 0.0.0.3 532224^MDC_TIME_SYNC_NONE^MDC     R<br>OBX 8 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.4 2^auth-body-continua     R<br>OBX 9 CWE 64515^MDC_REG_CERT_DATA_CONTINUA_AHD_CERT_LIST^MDC 0.0.0.4.1 0~1     R<br>OBX 10 528405^MDC_DEV_SPEC_PROFILE_PEFM^MDC 1     X     1234567890ABCDEF^EUI-64<br>OBX 11 ST 531969^MDC_ID_MODEL_NUMBER^MDC 1.0.0.1 Peak Flow v1.5     R<br>OBX 12 ST 531970^MDC_ID_MODEL_MANUFACTURER^MDC 1.0.0.2 AT4 Wireless     R<br>OBX 13 DTM 67975^MDC_ATTR_TIME_ABS^MDC 1.0.0.3 20100921124034+0000     R  20100921124034+0000<br>OBX 14 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.4 2^auth-body-continua     R |                  |                   |
+
+OBX|15|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.5|2^auth-body-continua||||R
+
+OBX|16|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.4.1|1.5||||R
+
+OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|1.0.0.4.2|16405||||R
+
+OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.0.0.5.1|0^unregulated-device(0)||||R
+
+OBX|19|NM|152584^MDC\_FLOW\_AWAY\_EXP\_FORCED\_PEAK^MDC|1.0.0.6|67|264992^MDC\_DIM\_L\_PER\_MIN^MDC||||R||20100921124034+0000
+
+OBX|20|NM|152585^MDC\_FLOW\_AWAY\_EXP\_FORCED\_PEAK\_PB^MDC|1.0.0.7|35|264992^MDC\_DIM\_L\_PER\_MIN^MDC||||R||20100921124034+0000
+
+OBX|21|NM|152586^MDC\_FLOW\_AWAY\_EXP\_FORCED\_PEAK\_1S^MDC|1.0.0.8|48|263744^MDC\_DIM\_L^MDC||||R||20100921124034+0000
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+- a. Only one MSA segment is present and:
+    - MSA-1 is one of the following values:
+      - 'AA' – Accept Acknowledgment: Application Accept
+      - 'AR' – Accept Acknowledgment: Application Reject
+    - MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+    - MSA-3 to MSA-8 are empty
+  - b. If the ERR segment referring to the MSA is present:
+    - If the HFS receiver reports an ERR segment with severity E (Error) or F (Fatal Error), the Message Acknowledgement value shall be CR (Commit Reject)
+    - ERR-1 is empty
+    - ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>
+    - ERR-3 starts with one of the following valid error condition codes and other optional subfields might be included:
+      - '0' – Message accepted
+      - '206' – Application record locked
+      - '207' – Application internal error
+    - ERR-4 is set to one of these valid error severity values:
+      - 'W' – Warning
+      - 'I' – Information
+      - 'E' – Error
+      - 'F' – Fatal error.
+    - ERR-5 and ERR-6 are empty
+    - ERR-7 may be empty, but if it is valued, it is a text data
+    - ERR-8 may be empty, but if it is valued, it is a text data
+    - ERR-9 may be empty, but if it is valued, it is one of these values:
+      - 'PAT'
+      - 'NPAT'
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• 'USR'</li> <li>• 'HD'</li> </ul> <ul style="list-style-type: none"> <li>❑ ERR-10 may be empty, but if it is valued, it is encoded as: <i>&lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt; Name of Coding System (ID)&gt;</i> the rest of the elements of the CWE data type are not used in the Services interface.</li> <li>❑ ERR-11 may be empty, but if it is valued, it is encoded as: <i>&lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt; Name of Coding System (ID)&gt;</i> the rest of the elements of the CWE data type are not used in the Services interface.</li> <li>❑ ERR-12 may be empty, but if it is valued, it is encoded as: <i>&lt;WITHDRAWN Constituent&gt;^&lt;Telecommunication Use Code (ID)&gt;^&lt;Telecommunication Equipment Type (ID)&gt;^&lt;Communication Address (ST)&gt;^&lt;Country Code (NM)&gt;^&lt;Area/City Code (NM)&gt;^&lt;Local Number (NM)&gt;^&lt;Extension (NM)&gt;^&lt;Any Text (ST)&gt;^&lt;Extension Prefix (ST)&gt;^&lt;Speed Dial Code (ST)&gt;^&lt;Unformatted Telephone Number (ST)&gt;^&lt;Effective Start Date (DTM)&gt;^&lt;Expiration Date (DTM)&gt;^&lt;Expiration Reason (CWE)&gt;^&lt;Protection Code (CWE)&gt;^&lt;Shared Telecommunication Identifier (EI)&gt;^&lt;Preference Order (NM)&gt;</i></li> </ul> <p>Where:</p> <ul style="list-style-type: none"> <li>• Expiration Reason subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li> <li>• Protection code subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li> <li>• Shared Telecommunication Identifier subcomponents are: <i>&lt;Entity Identifier (ST)&gt;&amp;&lt;Namespace ID (IS)&gt;&amp;&lt;Universal ID (ST)&gt;&amp;&lt;Universal ID Type (ID)&gt;</i></li> </ul> <p>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.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2, all elements in each segment are as specified above</li> <li>• Verify that the HFS receiver under test is able to accept the data and time stamps (e.g., if there is a log verify the date and the data are displayed in some form that indicates the correct date and time and the correct data as transmitted). Date and time of measurements: 2010-09-21 12:40:34 UTC, Values: PEF = 67 [l/min], Personal Best = 35 [l/min], FEV1 = 48 [l]</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+### A.14 Subgroup 2.4.13: Body composition analyser (BCA)
+
+|                 |                                   |                  |                      |                     |
+|-----------------|-----------------------------------|------------------|----------------------|---------------------|
+| <b>TP Id</b>    | TP/HFS/REC/PCD-01-DATA/BCA/BV-000 |                  |                      |                     |
+| <b>TP label</b> | MSA and ERR segments              |                  |                      |                     |
+| <b>Coverage</b> | <b>Spec</b>                       | [ITU-T H.812.1]  |                      |                     |
+|                 | <b>Testable items</b>             | MSAUse; M        | MSA-1; M             | MSA-2; M            |
+|                 |                                   | MSA-3; M         | MSA-4; M             | MSA-5; M            |
+|                 |                                   | MSA-6; M         | MSA-7; M             | MSA-8; M            |
+|                 |                                   | ERRUse 1; O      | ERRUse 2; M          | ERR-1; M            |
+|                 |                                   | ERR-2; R         | ERR-3; M             | ERR-4; M            |
+|                 |                                   | ERR-5; M         | ERR-6; M             | ERR-7; O            |
+|                 |                                   | CWEDataType 1; M | CWEDataType 2; M     | CWEDataType 3; C    |
+|                 |                                   | CWEDataType 4; R | NumericDataType 1; M | StringDataType 1; M |
+
+|                          |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                  |                   |
+|--------------------------|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-------------------|
+|                          |  | DateTimeDataType 1; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | EIDataType 1; M  | EIDataType 2; M   |
+|                          |  | EIDataType 3; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EIDataType 4; M  | EIUse1; C         |
+|                          |  | EIUse2; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | EIUse3; C        | EIUse4; C         |
+|                          |  | 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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                  |                   |
+| <b>Test purpose</b>      |  | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                  |                   |
+| <b>Applicability</b>     |  | C_REC_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                  |                   |
+| <b>Other PICS</b>        |  | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                  |                   |
+| <b>Initial condition</b> |  | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation of a body composition analyser device.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                  |                   |
+| <b>Test procedure</b>    |  | 1. The simulated HFS sender sends the following HL7 message inside a SOAP body to make the HFS receiver respond with another HL7 message:<br>MSH ^~\& AT4_AHD^1234567890ABCDEF^EUI-64   <current time in UTC> ORU^R01^ORU_R01 MSGID<random number> P 2.6  NE AL   IHE PCD ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7<br>PID   789567^^Imaginary Hospital^PI  Doe^John^Joseph^^^L<br>OBR 1 THTest^AT4_AHD^1234567890ABCDEF^EUI-64 THTest^AT4_AHD^1234567890ABCDEF^EUI-64 182777000^monitoring of patient^SNOMED-CT   20100916145110+0000<br>OBX 1  531981^MDC_MOC_VMS_MDS_AHD^MDC 0     X     FEEDABEEDEADBE EF^EUI-64<br>OBX 2 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.1 2^auth-body-continua     R<br>OBX 3 ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 0.0.0.1.1 6.1     R<br>OBX 4 NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 0.0.0.1.2 8212~16404~24596     R<br>OBX 5 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.2 2^auth-body-continua     R<br>OBX 6 CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC 0.0.0.2.1 1^unregulated-device(0)     R<br>OBX 7 CWE 68220^MDC_TIME_SYNC_PROTOCOL^MDC 0.0.0.3 532224^MDC_TIME_SYNC_NONE^MDC     R<br>OBX 8 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.4 2^auth-body-continua     R<br>OBX 9 CWE 64515^MDC_REG_CERT_DATA_CONTINUA_AHD_CERT_LIST^MDC 0.0.0.4.1 0~1     R<br>OBX 10  528404^MDC_DEV_SPEC_PROFILE_BCA^MDC 1     X     1234567890ABCDEF^EUI-64<br>OBX 11 ST 531969^MDC_ID_MODEL_NUMBER^MDC 1.0.0.1 Body Composition Analyzer v3.0     R<br>OBX 12 ST 531970^MDC_ID_MODEL_MANUFACTURER^MDC 1.0.0.2 AT4 Wireless     R |                  |                   |
+
+OBX|13|DTM|67975^MDC\_ATTR\_TIME\_ABS^MDC|1.0.0.3|20100916145110+0000|||  
+ ||R||20100916145110+0000
+
+OBX|14|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.4|2^auth-  
+ body-continua||||R
+
+OBX|15|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.5|2^auth-  
+ body-continua||||R
+
+OBX|16|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.4.1  
+ |3.0||||R
+
+OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|  
+ 1.0.0.4.2|16404||||R
+
+OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.  
+ 0.0.5.1|0^unregulated-device(0)||||R
+
+OBX|19|NM|188748^MDC\_BODY\_FAT^MDC|1.0.0.6|25|262688^MDC\_DIM\_PERCEN  
+ T^MDC||||R||20100916145110+0000
+
+OBX|20|NM|188740^MDC\_LEN\_BODY\_ACTUAL^MDC|1.0.0.7|175|263441^MDC\_DI  
+ M\_CENTI\_M^MDC||||R||20100916145110+0000
+
+OBX|21|NM|188736^MDC\_MASS\_BODY\_ACTUAL^MDC|1.0.0.8|73.5|263875^MDC\_  
+ DIM\_KILO\_G^MDC||||R||20100916145510+0000
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+- a. Only one MSA segment is present and:
+    - MSA-1 is one of the following values:
+      - 'AA' – Accept Acknowledgment: Application Accept
+      - 'AR' – Accept Acknowledgment: Application Reject
+    - MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+    - MSA-3 to MSA-8 are empty
+  - b. If the ERR segment referring to the MSA is present:
+    - If the HFS receiver reports an ERR segment with severity E (Error) or F (Fatal Error), the Message Acknowledgement value shall be CR (Commit Reject)
+    - ERR-1 is empty
+    - ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>
+    - ERR-3 starts with one of the following valid error condition codes and other optional subfields might be included:
+      - '0' – Message accepted
+      - '206' – Application record locked
+      - '207' – Application internal error
+    - ERR-4 is set to one of these valid error severity values:
+      - 'W' – Warning
+      - 'I' – Information
+      - 'E' – Error
+      - 'F' – Fatal error.
+    - ERR-5 and ERR-6 are empty
+    - ERR-7 may be empty, but if it is valued, it is a text data
+    - ERR-8 may be empty, but if it is valued, it is a text data
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> ERR-9 may be empty, but if it is valued, it is one of these values: <ul style="list-style-type: none"> <li>• 'PAT'</li> <li>• 'NPAT'</li> <li>• 'USR'</li> <li>• 'HD'</li> </ul> </li> <li><input type="checkbox"/> ERR-10 may be empty, but if it is valued, it is encoded as: <i>&lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt; Name of Coding System (ID)&gt;</i> the rest of the elements of the CWE data type are not used in the Services interface.</li> <li><input type="checkbox"/> ERR-11 may be empty, but if it is valued, it is encoded as: <i>&lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt; Name of Coding System (ID)&gt;</i> the rest of the elements of the CWE data type are not used in the Services interface.</li> <li><input type="checkbox"/> ERR-12 may be empty, but if it is valued, it is encoded as: <i>&lt;WITHDRAWN Constituent&gt;^&lt;Telecommunication Use Code (ID)&gt;^&lt;Telecommunication Equipment Type (ID)&gt;^&lt;Communication Address (ST)&gt;^&lt;Country Code (NM)&gt;^&lt;Area/City Code (NM)&gt;^&lt;Local Number (NM)&gt;^&lt;Extension (NM)&gt;^&lt;Any Text (ST)&gt;^&lt;Extension Prefix (ST)&gt;^&lt;Speed Dial Code (ST)&gt;^&lt;Unformatted Telephone Number (ST)&gt;^&lt;Effective Start Date (DTM)&gt;^&lt;Expiration Date (DTM)&gt;^&lt;Expiration Reason (CWE)&gt;^&lt;Protection Code (CWE)&gt;^&lt;Shared Telecommunication Identifier (EI)&gt;^&lt;Preference Order (NM)&gt;</i> <p>Where:</p> <ul style="list-style-type: none"> <li>• Expiration Reason subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li> <li>• Protection code subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li> <li>• Shared Telecommunication Identifier subcomponents are: <i>&lt;Entity Identifier (ST)&gt;&amp;&lt;Namespace ID (IS)&gt;&amp;&lt;Universal ID (ST)&gt;&amp;&lt;Universal ID Type (ID)&gt;</i></li> </ul> <p>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.</p> </li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2, all elements in each segment are as specified above</li> <li>• Verify that the HFS receiver under test is able to accept the data and time stamps (e.g., if there is a log verify the date and the data are displayed in some form that indicates the correct date and time and the correct data as transmitted). Date and time of measurements 2010-09-16 14:51:10 UTC, Values: Body Fat, 25 [%]; Body Height, 175 [cm] and Body Weight, 73.5 [Kg]</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+### A.15 Subgroup 2.4.14: Basic electrocardiograph (ECG)
+
+|                 |                                   |                 |             |
+|-----------------|-----------------------------------|-----------------|-------------|
+| <b>TP Id</b>    | TP/HFS/REC/PCD-01-DATA/ECG/BV-000 |                 |             |
+| <b>TP label</b> | MSA and ERR segments              |                 |             |
+| <b>Coverage</b> | <b>Spec</b>                       | [ITU-T H.812.1] |             |
+|                 | <b>Testable items</b>             | MSAUse; M       | MSA-1; M    |
+|                 |                                   | MSA-3; M        | MSA-4; M    |
+|                 |                                   | MSA-6; M        | MSA-7; M    |
+|                 |                                   | ERRUse 1; O     | ERRUse 2; M |
+|                 |                                   | ERR-2; R        | ERR-3; M    |
+|                 |                                   |                 | ERR-4; M    |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                      |                     |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|---------------------|
+|                          | ERR-5; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | ERR-6; M             | ERR-7; O            |
+|                          | CWEDataType 1; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | CWEDataType 2; M     | CWEDataType 3; C    |
+|                          | CWEDataType 4; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumericDataType 1; M | StringDataType 1; M |
+|                          | DateTimeDataType 1; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | EIDataType 1; M      | EIDataType 2; M     |
+|                          | EIDataType 3; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | EIDataType 4; M      | EIUse1; C           |
+|                          | EIUse2; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | EIUse3; C            | EIUse4; C           |
+|                          | 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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                      |                     |
+| <b>Test purpose</b>      | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                      |                     |
+| <b>Applicability</b>     | C_REC_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                      |                     |
+| <b>Other PICS</b>        | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                      |                     |
+| <b>Initial condition</b> | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a SOAP message with an observation of a basic electrocardiograph device.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                      |                     |
+| <b>Test procedure</b>    | 1. The simulated HFS sender sends the following HL7 message inside a SOAP body to make the HFS receiver respond with another HL7 message:<br>MSH ^~\& AT4_AHD^1234567890ABCDEF^EUI-64   <current time in UTC>  ORU^R01^ORU_R01 MSGID<random number> P 2.6  NE AL    IHE PCD ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7<br>PID   789567^^Imaginary Hospital^PI  Doe^John^Joseph^^^L<br>OBR 1 THTTest^AT4_AHD^1234567890ABCDEF^EUI-64 THTTest^AT4_AHD^1234567890ABCDEF^EUI-64 182777000^monitoring of patient^SNOMED-CT   20100916145110+0000<br>OBX 1  531981^MDC_MOC_VMS_MDS_AHD^MDC 0    X    FEEDABEEDEADBE EF^EUI-64<br>OBX 2 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.1 2^auth-body-continua    R<br>OBX 3 ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 0.0.0.1.1 6.1    R<br>OBX 4 NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 0.0.0.1.2 8204~8332    R<br>OBX 5 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.2 2^auth-body-continua    R<br>OBX 6 CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC 0.0.0.2.1 1^unregulated-device(0)    R<br>OBX 7 CWE 68220^MDC_TIME_SYNC_PROTOCOL^MDC 0.0.0.3 532224^MDC_TIME_SYNC_NONE^MDC    R<br>OBX 8 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.4 2^auth-body-continua    R<br>OBX 9 CWE 64515^MDC_REG_CERT_DATA_CONTINUA_AHD_CERT_LIST^MDC 0.0.0.4.1 0~1    R<br>OBX 10  528384^MDC_DEV_SPEC_PROFILE_HYDRA^MDC 1    X    1234567890 ABCDEF^EUI-64 |                      |                     |
+
+OBX|11|CWE|68186^MDC\_ATTR\_SYS\_TYPE\_SPEC\_LIST^MDC|1.0.0.1|528390^MDC\_DEV\_SPEC\_PROFILE\_ECG^MDC~528525^MDC\_DEV\_SUB\_SPEC\_PROFILE\_HR^MDC|||||R|||20110808135003+0000
+
+OBX|12|ST|531969^MDC\_ID\_MODEL\_NUMBER^MDC|1.0.0.2|Basic Electrocardiograph v3.0|||||R
+
+OBX|13|ST|531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC|1.0.0.3|AT4 Wireless|||||R
+
+OBX|14|DTM|67975^MDC\_ATTR\_TIME\_ABS^MDC|1.0.0.4|20100916145110+0000|||||R|||20100916145110+0000
+
+OBX|15|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.5|2^auth-body-continua|||||R
+
+OBX|16|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.6|2^auth-body-continua|||||R
+
+OBX|17|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.5.1|3.0|||||R
+
+OBX|18|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|1.0.0.5.2|8204~8332|||||R
+
+OBX|19|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.0.0.6.1|0^unregulated-device(0)|||||R
+
+OBX|20|NM|147842^MDC\_ECG\_HEART\_RATE^MDC|1.0.0.7|80|264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC|||||R|||20100916145110+0000
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+  - a. Only one MSA segment is present and:
+    - MSA-1 is one of the following values:
+      - 'AA' – Accept Acknowledgment: Application Accept
+      - 'AR' – Accept Acknowledgment: Application Reject
+    - MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+    - MSA-3 to MSA-8 are empty
+  - b. If the ERR segment referring to the MSA is present:
+    - If the HFS receiver reports an ERR segment with severity E (Error) or F (Fatal Error), the Message Acknowledgement value shall be CR (Commit Reject)
+    - ERR-1 is empty
+    - ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>
+    - ERR-3 starts with one of the following valid error condition codes and other optional subfields might be included:
+      - '0' – Message accepted
+      - '206' – Application record locked
+      - '207' – Application internal error
+    - ERR-4 is set to one of these valid error severity values:
+      - 'W' – Warning
+      - 'I' – Information
+      - 'E' – Error
+      - 'F' – Fatal error.
+    - ERR-5 and ERR-6 are empty
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> ERR-7 may be empty, but if it is valued, it is a text data</li> <li><input type="checkbox"/> ERR-8 may be empty, but if it is valued, it is a text data</li> <li><input type="checkbox"/> ERR-9 may be empty, but if it is valued, it is one of these values: <ul style="list-style-type: none"> <li>• 'PAT'</li> <li>• 'NPAT'</li> <li>• 'USR'</li> <li>• 'HD'</li> </ul> </li> <li><input type="checkbox"/> ERR-10 may be empty, but if it is valued, it is encoded as: &lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt; Name of Coding System (ID)&gt; the rest of the elements of the CWE data type are not used in the Services interface.</li> <li><input type="checkbox"/> ERR-11 may be empty, but if it is valued, it is encoded as: &lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt; Name of Coding System (ID)&gt; the rest of the elements of the CWE data type are not used in Services interface.</li> <li><input type="checkbox"/> ERR-12 may be empty, but if it is valued, it is encoded as: &lt;WITHDRAWN Constituent&gt;^&lt;Telecommunication Use Code (ID)&gt;^&lt;Telecommunication Equipment Type (ID)&gt;^&lt;Communication Address (ST)&gt;^&lt;Country Code (NM)&gt;^&lt;Area/City Code (NM)&gt;^&lt;Local Number (NM)&gt;^&lt;Extension (NM)&gt;^&lt;Any Text (ST)&gt;^&lt;Extension Prefix (ST)&gt;^&lt;Speed Dial Code (ST)&gt;^&lt;Unformatted Telephone Number (ST)&gt;^&lt;Effective Start Date (DTM)&gt;^&lt;Expiration Date (DTM)&gt;^&lt;Expiration Reason (CWE)&gt;^&lt;Protection Code (CWE)&gt;^&lt;Shared Telecommunication Identifier (EI)&gt;^&lt;Preference Order (NM)&gt;</li> </ul> <p>Where:</p> <ul style="list-style-type: none"> <li>• Expiration Reason subcomponents are: &lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</li> <li>• Protection code subcomponents are: &lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</li> <li>• Shared Telecommunication Identifier subcomponents are: &lt;Entity Identifier (ST)&gt;&amp;&lt;Namespace ID (IS)&gt;&amp;&lt;Universal ID (ST)&gt;&amp;&lt;Universal ID Type (ID)&gt;</li> </ul> <p>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.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2, all elements in each segment are as specified above</li> <li>• Verify that the HFS receiver under test is able to accept the data and time stamps (e.g., if there is a log verify the date and the data are displayed in some form that indicates the correct date and time and the correct data as transmitted). Date and time of measurement: 2010-09-16 14:51:10 UTC, Value: Heart Rate, 80 [beats per min.].</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+### A.16 Subgroup 2.4.15: International normalized ratio (INR)
+
+|                 |                                   |                 |          |
+|-----------------|-----------------------------------|-----------------|----------|
+| <b>TP Id</b>    | TP/HFS/REC/PCD-01-DATA/INR/BV-000 |                 |          |
+| <b>TP label</b> | MSA and ERR segments              |                 |          |
+| <b>Coverage</b> | <b>Spec</b>                       | [ITU-T H.812.1] |          |
+|                 | <b>Testable items</b>             | MSAUUse; M      | MSA-1; M |
+|                 |                                   | MSA-3; M        | MSA-4; M |
+|                 |                                   |                 | MSA-2; M |
+|                 |                                   |                 | MSA-5; M |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                      |                     |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|---------------------|
+|                          | MSA-6; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | MSA-7; M             | MSA-8; M            |
+|                          | ERRUse 1; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | ERRUse 2; M          | ERR-1; M            |
+|                          | ERR-2; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | ERR-3; M             | ERR-4; M            |
+|                          | ERR-5; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | ERR-6; M             | ERR-7; O            |
+|                          | CWEDataType 1; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | CWEDataType 2; M     | CWEDataType 3; C    |
+|                          | CWEDataType 4; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | NumericDataType 1; M | StringDataType 1; M |
+|                          | DateTimeDataType 1; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | EIDataType 1; M      | EIDataType 2; M     |
+|                          | EIDataType 3; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | EIDataType 4; M      | EIUse1; C           |
+|                          | EIUse2; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | EIUse3; C            | EIUse4; C           |
+|                          | 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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                      |                     |
+| <b>Test purpose</b>      | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                      |                     |
+| <b>Applicability</b>     | C_REC_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                      |                     |
+| <b>Other PICS</b>        | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                      |                     |
+| <b>Initial condition</b> | The receiver under test has published a WebService and the simulated sender is ready to send a message with an Observation of an International Normalized Ratio device.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                      |                     |
+| <b>Test procedure</b>    | 1. The simulated sender sends the following HL7 message, including the mandatory objects of a Pulse Oximeter device to make the receiver respond with another HL7 message.<br>MSH ^~\& AT4_AHD^1234567890ABCDEF^EUI-64   <current time in UTC>  ORU^R01^ORU_R01 MSGID<random number> P 2.6   NE AL    IHE PCD ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7<br>PID   789567^^Imaginary Hospital^PI  Doe^John^Joseph^^^L<br>OBR 1 POTest^AT4_AHD^1234567890ABCDEF^EUI-64 POTest^AT4_AHD^1234567890ABCDEF^EUI-64 182777000^monitoring of patient^SNOMED-CT   20100903124015+0000<br>OBX 1  531981^MDC_MOC_VMS_MDS_AHD^MDC 0    X    FEEDABEEDEADBE EF^EUI-64<br>OBX 2 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.1 2^auth-body-continua    R<br>OBX 3 ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 0.0.0.1.1 6.1    R<br>OBX 4 NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 0.0.0.1.2 8196~16388    R<br>OBX 5 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.2 2^auth-body-continua    R |                      |                     |
+
+OBX|6|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|0.0.0.2.1|1^unregulated-device(0)|||||R
+
+OBX|7|CWE|68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC|0.0.0.3|532224^MDC\_TIME\_SYNC\_NONE^MDC|||||R
+
+OBX|8|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.4|2^auth-body-continua|||||R
+
+OBX|9|CWE|64515^MDC\_REG\_CERT\_DATA\_CONTINUA\_AHD\_CERT\_LIST^MDC|0.0.0.4.1|0~1|||||R
+
+OBX|10||528406^MDC\_DEV\_SPEC\_PROFILE\_COAG^MDC|1|||||X|||||0123456789ABCDEF^0123456789ABCDEF^EUI-64
+
+OBX|11|ST|531969^MDC\_ID\_MODEL\_NUMBER^MDC|1.0.0.1||INR v1.5|||||R
+
+OBX|12|ST|531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC|1.0.0.2||AT4 Wireless|||||R
+
+OBX|13|DTM|67975^MDC\_ATTR\_TIME\_ABS^MDC|1.0.0.3|20100903124015+0000|||||R||20150316145510+0000
+
+OBX|14|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.4|2^auth-body-continua|||||R
+
+OBX|15|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.5|2^auth-body-continua|||||R
+
+OBX|16|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.4.1|6.1|||||R
+
+OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|1.0.0.4.2|16388|||||R
+
+OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.0.0.5.1|0^unregulated-device(0)|||||R
+
+OBX|19|NM|160260^MDC\_RATIO\_INR\_COAG^MDC|1.0.0.1|0.9|268752^MDC\_DIM\_INR^MDC|||||R||20150316145510+0000
+
+2. HFS receiver under test responds using another HL7 message. Check in the captured message that:
+  - a. Only one MSA segment is present and:
+    - MSA-1 is one of the following values:
+      - 'AA' – Accept Acknowledgment: Application Accept
+      - 'AR' – Accept Acknowledgment: Application Reject
+    - MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+    - MSA-3 to MSA-8 are empty
+  - b. If ERR segment referring to the MSA is present:
+    - If the HFS receiver reports an ERR segment with Severity (ERR-4) E (Error) or F (Fatal Error), the Message Acknowledgement value shall be CR (Commit Reject)
+    - ERR-1 is empty
+    - ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>
+    - ERR-3 starts with one of the following valid error condition codes and other optional subfields might be included:
+      - '0' – Accepted
+      - '206' – Application record locked
+      - '207' – Application internal error
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><input type="checkbox"/> ERR-4 is set to one of these valid error severity values:</p> <ul style="list-style-type: none"> <li>• 'W' – Warning</li> <li>• 'I' – Information</li> <li>• 'E' – Error</li> <li>• 'F' – Fatal error.</li> </ul> <p><input type="checkbox"/> ERR-5 and ERR-6 are empty</p> <p><input type="checkbox"/> ERR-7 may be empty, but if it is valued, it is a text data</p> <p><input type="checkbox"/> ERR-8 may be empty, but if it is valued, it is a text data</p> <p><input type="checkbox"/> ERR-9 may be empty, but if it is valued, it is one of these values:</p> <ul style="list-style-type: none"> <li>• 'PAT'</li> <li>• 'NPAT'</li> <li>• 'USR'</li> <li>• 'HD'</li> </ul> <p><input type="checkbox"/> ERR-10 may be empty, but if it is valued, it is encoded as: <i>&lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt; Name of Coding System (ID)&gt; the rest of the element of the CWE data type are not used in Services Interface.</i></p> <p><input type="checkbox"/> ERR-11 may be empty, but if it is valued, it is encoded as: <i>&lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt; Name of Coding System (ID)&gt; the rest of the element of the CWE data type are not used in Services Interface.</i></p> <p><input type="checkbox"/> ERR-12 may be empty, but if it is valued, it is encoded as: <i>&lt;WITHDRAWN Constituent&gt;^&lt;Telecommunication Use Code (ID)&gt;^&lt;Telecommunication Equipment Type (ID)&gt;^&lt;Communication Address (ST)&gt;^&lt;Country Code (NM)&gt;^&lt;Area/City Code (NM)&gt;^&lt;Local Number (NM)&gt;^&lt;Extension (NM)&gt;^&lt;Any Text (ST)&gt;^&lt;Extension Prefix (ST)&gt;^&lt;Speed Dial Code (ST)&gt;^&lt;Unformatted Telephone Number (ST)&gt;^&lt;Effective Start Date (DTM)&gt;^&lt;Expiration Date (DTM)&gt;^&lt;Expiration Reason (CWE)&gt;^&lt;Protection Code (CWE)&gt;^&lt;Shared Telecommunication Identifier (EI)&gt;^&lt;Preference Order (NM)&gt;</i></p> <p>Where:</p> <ul style="list-style-type: none"> <li>• Expiration Reason subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li> <li>• Protection code subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li> <li>• Shared Telecommunication Identifier subcomponents are: <i>&lt;Entity Identifier (ST)&gt;&amp;&lt;Namespace ID (IS)&gt;&amp;&lt;Universal ID (ST)&gt;&amp;&lt;Universal ID Type (ID)&gt;</i></li> </ul> <p>Where XTN-2, XTN-3 are required and XTN-4 to XTN-10 are required but may be empty. The rest are not supported.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2, all elements in each segment are as specified above</li> <li>• Verify that the HFS receiver under test is able to accept the data and time stamps (e.g. if there is a log verify the date and the data are displayed in some form that indicates the correct date and time and the correct data as transmitted). Date and time of the measurement: 2015-03-16 14:55:10 UTC, Value: INR=0.9 [INR Units]</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |                      |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|
+| <b>TP Id</b>             | TP/HFS/REC/PCD-01-DATA/SABTE/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |                      |
+| <b>TP label</b>          | MSA and ERR segments                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |                      |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ITU-T H.812.1]       |                      |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                               | MSAUse; M             | MSA-1; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | MSA-3; M              | MSA-4; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | MSA-6; M              | MSA-7; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ERRUse 1; O           | ERRUse 2; M          |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ERR-2; R              | ERR-3; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ERR-5; M              | ERR-6; M             |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | CWEDataType 1; M      | CWEDataType 2; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | CWEDataType 4; R      | NumericDataType 1; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | DateTimeDataType 1; M | EIDataType 1; M      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | EIDataType 3; M       | EIDataType 4; M      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | EIUse2; C             | EIUse3; C            |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | IDDataType 1; M       | ISDataType 1; M      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | XTNDataType 2; M      | XTNDataType 3; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | XTNDataType 5; M      | XTNDataType 6; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | XTNDataType 8; M      | XTNDataType 9; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     | XTNDataType 11; M     |                      |
+| <b>Test purpose</b>      | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                                                                                                                                                                                                                                                                              |                       |                      |
+| <b>Applicability</b>     | C_REC_000                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |                      |
+| <b>Other PICS</b>        | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |                      |
+| <b>Initial condition</b> | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a message with an Observation of a Sleep Apnoea Breathing Therapy Equipment device.                                                                                                                                                                                                                                                            |                       |                      |
+| <b>Test procedure</b>    | 1. The simulated HFS sender sends the following HL7 message, including the mandatory objects of a Sleep Apnoea Breathing Therapy Equipment device to make the receiver respond with another HL7 message.<br>MSH ^~& AT4_AHD^1234567890ABCDEF^EUI-64   <current time in UTC>  ORU^R01^ORU_R01 MSGID<random number> P 2.6  NE AL     IHE PCD ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7<br>PID   789567^^^Imaginary Hospital^PI  Doe^John^Joseph^^^L |                       |                      |
+
+OBR|1|POTest^AT4\_AHD^1234567890ABCDEF^EUI-64|POTest^AT4\_AHD^1234567890ABCDEF^EUI-64|182777000^monitoring of patient^SNOMED-CT|||20150316145510+0000  
+ OBX|1|531981^MDC\_MOC\_VMS\_MDS\_AHD^MDC|0|||||X|||||FEEDABEEDEADBE EF^EUI-64  
+ OBX|2|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.1|2^auth-body-continua|||||R  
+ OBX|3|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|0.0.0.1.1|6.1|||||R  
+ OBX|4|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|0.0.0.1.2|8196~16388|||||R  
+ OBX|5|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.2|2^auth-body-continua|||||R  
+ OBX|6|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|0.0.0.2.1|1^unregulated-device(0)|||||R  
+ OBX|7|CWE|68220^MDC\_TIME\_SYNC\_PROTOCOL^MDC|0.0.0.3|532224^MDC\_TIME\_SYNC\_NONE^MDC|||||R  
+ OBX|8|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|0.0.0.4|2^auth-body-continua|||||R  
+ OBX|9|CWE|64515^MDC\_REG\_CERT\_DATA\_CONTINUA\_AHD\_CERT\_LIST^MDC|0.0.0.4.1|0~1|||||R  
+ OBX|10||528409^MDC\_DEV\_SPEC\_PROFILE\_SABTE^MDC|1|||||X|||||0123456789 ABCDEF^0123456789ABCDEF^EUI-64  
+ OBX|11|ST|531969^MDC\_ID\_MODEL\_NUMBER^MDC|1.0.0.1|SABTE v1.5|||||R  
+ OBX|12|ST|531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC|1.0.0.2|AT4 Wireless|||||R  
+ OBX|13|DTM|67975^MDC\_ATTR\_TIME\_ABS^MDC|1.0.0.3|20150316145510+0000|||||R|||20150316145510+0000  
+ OBX|14|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.4|2^auth-body-continua|||||R  
+ OBX|15|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.5|2^auth-body-continua|||||R  
+ OBX|16|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.4.1|6.1|||||R  
+ OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|1.0.0.4.2|16388|||||R  
+ OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.0.0.5.1|0^unregulated-device(0)|||||R  
+ OBX|19|NM|8410708^MDC\_SABTE\_TIME\_PD\_FLOW\_GEN\_TOTAL^MDC|1.0.0.6|67|264352^MDC\_DIM\_MIN^MDC|||||R|||20150316145510+0000  
+ OBX|20|NM|8410712^MDC\_SABTE\_TIME\_PD\_USAGE\_TOTAL^MDC|1.0.0.7|55|264352^MDC\_DIM\_MIN^MDC|||||R|||20150316145510+0000  
+ OBX|21|CWE|8410876^MDC\_SABTE\_MODE\_DEV\_SET^MDC|1.0.0.8|8410877^MDC\_SABTE\_MODE\_DEV\_UNDETERMINED^MDC|||||R|||20150316145510+0000  
+ OBX|22|CWE|8410888^MDC\_SABTE\_MODE\_THERAPY\_SET^MDC|1.0.0.9|8410889^MDC\_SABTE\_MODE\_THERAPY\_UNDETERMINED^MDC|||||R|||20150316145510+0000
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+  - a. Only one MSA segment is present and:
+    - MSA-1 is one of the following values:
+      - 'AA' – Accept Acknowledgment: Application Accept
+      - 'AR' – Accept Acknowledgment: Application Reject
+
+- MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+  - MSA-3 to MSA-8 are empty
+- b. If ERR segment referring to the MSA is present:
+- If the HFS receiver reports an ERR segment with Severity (ERR-4) E (Error) or F (Fatal Error), the Message Acknowledgement value shall be CR (Commit Reject)
+  - ERR-1 is empty
+  - ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: *<Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>*
+  - ERR-3 starts with one of the following valid error condition codes and other optional subfields might be included:
+    - '0' – Accepted
+    - '206' – Application record locked
+    - '207' – Application internal error
+  - ERR-4 is set to one of these valid error severity values:
+    - 'W' – Warning
+    - 'I' – Information
+    - 'E' – Error
+    - 'F' – Fatal error.
+  - ERR-5 and ERR-6 are empty
+  - ERR-7 may be empty, but if it is valued, it is a text data
+  - ERR-8 may be empty, but if it is valued, it is a text data
+  - ERR-9 may be empty, but if it is valued, it is one of these values:
+    - 'PAT'
+    - 'NPAT'
+    - 'USR'
+    - 'HD'
+  - ERR-10 may be empty, but if it is valued, it is encoded as: *<Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)>* the rest of the element of the CWE data type are not used in Services Interface.
+  - ERR-11 may be empty, but if it is valued, it is encoded as: *<Identifier (ST)> ^ <Text (ST)> ^ < Name of Coding System (ID)>* the rest of the element of the CWE data type are not used in Services Interface.
+  - ERR-12 may be empty, but if it is valued, it is encoded as: *<WITHDRAWN Constituent> ^ <Telecommunication Use Code (ID)> ^ <Telecommunication Equipment Type (ID)> ^ <Communication Address (ST)> ^ <Country Code (NM)> ^ <Area/City Code (NM)> ^ <Local Number (NM)> ^ <Extension (NM)> ^ <Any Text (ST)> ^ <Extension Prefix (ST)> ^ <Speed Dial Code (ST)> ^ <Unformatted Telephone Number (ST)> ^ <Effective Start Date (DTM)> ^ <Expiration Date (DTM)> ^ <Expiration Reason (CWE)> ^ <Protection Code (CWE)> ^ <Shared Telecommunication Identifier (EI)> ^ <Preference Order (NM)>*
+- Where:
+- Expiration Reason subcomponents are: *<Identifier (ST)> & <Text (ST)> & < Name of Coding System (ID)> & <Alternate Identifier (ST)> & <Alternate Text (ST)> & <Name of Alternate Coding System (ID)> & <Coding System*
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><i>Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></p> <ul style="list-style-type: none"> <li>• Protection code subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt;Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li> <li>• Shared Telecommunication Identifier subcomponents are: <i>&lt;Entity Identifier (ST)&gt;&amp;&lt;Namespace ID (IS)&gt;&amp;&lt;Universal ID (ST)&gt;&amp;&lt;Universal ID Type (ID)&gt;</i></li> </ul> <p>Where XTN-2, XTN-3 are required and XTN-4 to XTN-10 are required but may be empty. The rest are not supported.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2, all elements in each segment are as specified above</li> <li>• Verify that the HFS receiver under test is able to accept the data and time stamps (e.g. if there is a log verify the date and the data are displayed in some form that indicates the correct date and time and the correct data as transmitted). Date and time of the measurement: 2015-03-16 14:55:10 UTC, Values: DPU=55 [min], DFG=67 [min], Device mode set='Device mode undetermined (22269)', Therapy mode set='Therapy mode undetermined (22269)'.</li> </ul>                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+### A.18 Subgroup 2.4.17: Insulin pump (IP)
+
+|                       |                                  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |  |           |          |          |          |          |          |          |          |          |             |             |          |          |          |          |          |          |          |                  |                  |                  |                  |                      |                     |                       |                 |                 |                 |                 |           |           |           |           |                 |                 |                  |                  |                  |                  |                  |                  |                  |                  |                  |
+|-----------------------|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-----------|----------|----------|----------|----------|----------|----------|----------|----------|-------------|-------------|----------|----------|----------|----------|----------|----------|----------|------------------|------------------|------------------|------------------|----------------------|---------------------|-----------------------|-----------------|-----------------|-----------------|-----------------|-----------|-----------|-----------|-----------|-----------------|-----------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|
+| <b>TP Id</b>          | TP/HFS/REC/PCD-01-DATA/IP/BV-000 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |  |           |          |          |          |          |          |          |          |          |             |             |          |          |          |          |          |          |          |                  |                  |                  |                  |                      |                     |                       |                 |                 |                 |                 |           |           |           |           |                 |                 |                  |                  |                  |                  |                  |                  |                  |                  |                  |
+| <b>TP label</b>       | MSA and ERR segments             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |  |           |          |          |          |          |          |          |          |          |             |             |          |          |          |          |          |          |          |                  |                  |                  |                  |                      |                     |                       |                 |                 |                 |                 |           |           |           |           |                 |                 |                  |                  |                  |                  |                  |                  |                  |                  |                  |
+| <b>Coverage</b>       | <b>Spec</b>                      | [ITU-T H.812.1]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |  |           |          |          |          |          |          |          |          |          |             |             |          |          |          |          |          |          |          |                  |                  |                  |                  |                      |                     |                       |                 |                 |                 |                 |           |           |           |           |                 |                 |                  |                  |                  |                  |                  |                  |                  |                  |                  |
+|                       | <b>Testable items</b>            | <table border="1"> <tr> <td>MSAUse; M</td> <td>MSA-1; M</td> <td>MSA-2; M</td> </tr> <tr> <td>MSA-3; M</td> <td>MSA-4; M</td> <td>MSA-5; M</td> </tr> <tr> <td>MSA-6; M</td> <td>MSA-7; M</td> <td>MSA-8; M</td> </tr> <tr> <td>ERRUse 1; O</td> <td>ERRUse 2; M</td> <td>ERR-1; M</td> </tr> <tr> <td>ERR-2; R</td> <td>ERR-3; M</td> <td>ERR-4; M</td> </tr> <tr> <td>ERR-5; M</td> <td>ERR-6; M</td> <td>ERR-7; O</td> </tr> <tr> <td>CWEDataType 1; M</td> <td>CWEDataType 2; M</td> <td>CWEDataType 3; C</td> </tr> <tr> <td>CWEDataType 4; R</td> <td>NumericDataType 1; M</td> <td>StringDataType 1; M</td> </tr> <tr> <td>DateTimeDataType 1; M</td> <td>EIDataType 1; M</td> <td>EIDataType 2; M</td> </tr> <tr> <td>EIDataType 3; M</td> <td>EIDataType 4; M</td> <td>EIUse1; C</td> </tr> <tr> <td>EIUse2; C</td> <td>EIUse3; C</td> <td>EIUse4; C</td> </tr> <tr> <td>IDDataType 1; M</td> <td>ISDataType 1; M</td> <td>XTNDataType 1; M</td> </tr> <tr> <td>XTNDataType 2; M</td> <td>XTNDataType 3; M</td> <td>XTNDataType 4; M</td> </tr> <tr> <td>XTNDataType 5; M</td> <td>XTNDataType 6; M</td> <td>XTNDataType 7; M</td> </tr> <tr> <td>XTNDataType 8; M</td> <td>XTNDataType 9; M</td> <td>XTNDataType 10; M</td> </tr> </table> |  | MSAUse; M | MSA-1; M | MSA-2; M | MSA-3; M | MSA-4; M | MSA-5; M | MSA-6; M | MSA-7; M | MSA-8; M | ERRUse 1; O | ERRUse 2; M | ERR-1; M | ERR-2; R | ERR-3; M | ERR-4; M | ERR-5; M | ERR-6; M | ERR-7; O | CWEDataType 1; M | CWEDataType 2; M | CWEDataType 3; C | CWEDataType 4; R | NumericDataType 1; M | StringDataType 1; M | DateTimeDataType 1; M | EIDataType 1; M | EIDataType 2; M | EIDataType 3; M | EIDataType 4; M | EIUse1; C | EIUse2; C | EIUse3; C | EIUse4; C | 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 |
+| MSAUse; M             | MSA-1; M                         | MSA-2; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |  |           |          |          |          |          |          |          |          |          |             |             |          |          |          |          |          |          |          |                  |                  |                  |                  |                      |                     |                       |                 |                 |                 |                 |           |           |           |           |                 |                 |                  |                  |                  |                  |                  |                  |                  |                  |                  |
+| MSA-3; M              | MSA-4; M                         | MSA-5; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |  |           |          |          |          |          |          |          |          |          |             |             |          |          |          |          |          |          |          |                  |                  |                  |                  |                      |                     |                       |                 |                 |                 |                 |           |           |           |           |                 |                 |                  |                  |                  |                  |                  |                  |                  |                  |                  |
+| MSA-6; M              | MSA-7; M                         | MSA-8; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |  |           |          |          |          |          |          |          |          |          |             |             |          |          |          |          |          |          |          |                  |                  |                  |                  |                      |                     |                       |                 |                 |                 |                 |           |           |           |           |                 |                 |                  |                  |                  |                  |                  |                  |                  |                  |                  |
+| ERRUse 1; O           | ERRUse 2; M                      | ERR-1; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |  |           |          |          |          |          |          |          |          |          |             |             |          |          |          |          |          |          |          |                  |                  |                  |                  |                      |                     |                       |                 |                 |                 |                 |           |           |           |           |                 |                 |                  |                  |                  |                  |                  |                  |                  |                  |                  |
+| ERR-2; R              | ERR-3; M                         | ERR-4; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |  |           |          |          |          |          |          |          |          |          |             |             |          |          |          |          |          |          |          |                  |                  |                  |                  |                      |                     |                       |                 |                 |                 |                 |           |           |           |           |                 |                 |                  |                  |                  |                  |                  |                  |                  |                  |                  |
+| ERR-5; M              | ERR-6; M                         | ERR-7; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |  |           |          |          |          |          |          |          |          |          |             |             |          |          |          |          |          |          |          |                  |                  |                  |                  |                      |                     |                       |                 |                 |                 |                 |           |           |           |           |                 |                 |                  |                  |                  |                  |                  |                  |                  |                  |                  |
+| CWEDataType 1; M      | CWEDataType 2; M                 | CWEDataType 3; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |  |           |          |          |          |          |          |          |          |          |             |             |          |          |          |          |          |          |          |                  |                  |                  |                  |                      |                     |                       |                 |                 |                 |                 |           |           |           |           |                 |                 |                  |                  |                  |                  |                  |                  |                  |                  |                  |
+| CWEDataType 4; R      | NumericDataType 1; M             | StringDataType 1; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |  |           |          |          |          |          |          |          |          |          |             |             |          |          |          |          |          |          |          |                  |                  |                  |                  |                      |                     |                       |                 |                 |                 |                 |           |           |           |           |                 |                 |                  |                  |                  |                  |                  |                  |                  |                  |                  |
+| DateTimeDataType 1; M | EIDataType 1; M                  | EIDataType 2; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |  |           |          |          |          |          |          |          |          |          |             |             |          |          |          |          |          |          |          |                  |                  |                  |                  |                      |                     |                       |                 |                 |                 |                 |           |           |           |           |                 |                 |                  |                  |                  |                  |                  |                  |                  |                  |                  |
+| EIDataType 3; M       | EIDataType 4; M                  | EIUse1; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |  |           |          |          |          |          |          |          |          |          |             |             |          |          |          |          |          |          |          |                  |                  |                  |                  |                      |                     |                       |                 |                 |                 |                 |           |           |           |           |                 |                 |                  |                  |                  |                  |                  |                  |                  |                  |                  |
+| EIUse2; C             | EIUse3; C                        | EIUse4; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |  |           |          |          |          |          |          |          |          |          |             |             |          |          |          |          |          |          |          |                  |                  |                  |                  |                      |                     |                       |                 |                 |                 |                 |           |           |           |           |                 |                 |                  |                  |                  |                  |                  |                  |                  |                  |                  |
+| 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 |  |  |
+| <b>Test purpose</b>      | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                   |  |  |
+| <b>Applicability</b>     | C_REC_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                   |  |  |
+| <b>Other PICS</b>        | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                   |  |  |
+| <b>Initial condition</b> | The HFS receiver under test has published a WebService and the simulated HFS sender is ready to send a message with an Observation of an insulin pump device.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                   |  |  |
+| <b>Test procedure</b>    | 1. The simulated HFS sender sends the following HL7 message, including the mandatory objects of an Insulin Pump device to make the HFS receiver respond with another HL7 message.<br>MSH ^~\& AT4_AHD^1234567890ABCDEF^EUI-64   <current time in UTC>  ORU^R01^ORU_R01 MSGID<random number> P 2.6  NE AL   IHE PCD ORU-R012006^HL7^2.16.840.1.113883.9.n.m^HL7<br>PID   789567^^Imaginary Hospital^PI  Doe^John^Joseph^^^L<br>OBR 1 POTest^AT4_AHD^1234567890ABCDEF^EUI-64 POTest^AT4_AHD^1234567890ABCDEF^EUI-64 182777000^monitoring of patient^SNOMED-CT   20160903124015+0000<br>OBX 1  531981^MDC_MOC_VMS_MDS_AHD^MDC 0     X     device^^FEEDABEED EADBEEF^EUI-64<br>OBX 2 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.1 2^auth-body-continua     R<br>OBX 3 ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 0.0.0.1.1 6.1     R<br>OBX 4 NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 0.0.0.1.2 16403     R<br>OBX 5 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.2 2^auth-body-continua     R<br>OBX 6 CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC 0.0.0.2.1 1^unregulated-device(0)     R<br>OBX 7 CWE 68220^MDC_TIME_SYNC_PROTOCOL^MDC 0.0.0.3 532224^MDC_TIME_SYNC_NONE^MDC     R<br>OBX 8 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.4 2^auth-body-continua     R<br>OBX 9 CWE 64515^MDC_REG_CERT_DATA_CONTINUA_AHD_CERT_LIST^MDC 0.0.0.4.1 0~1     R<br>OBX 10  528403^MDC_DEV_SPEC_PROFILE_INSULIN_PUMP^MDC 1     X     0123456789ABCDEF^0123456789ABCDEF^EUI-64<br>OBX 11 ST 531969^MDC_ID_MODEL_NUMBER^MDC 1.0.0.1 IP v1.0     R<br>OBX 12 ST 531970^MDC_ID_MODEL_MANUFACTURER^MDC 1.0.0.2 AT4 Wireless     R<br>OBX 13 DTM 67975^MDC_ATTR_TIME_ABS^MDC 1.0.0.3 20160316135510+0000     R  20160316145510+0000<br>OBX 14 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.4 2^auth-body-continua     R<br>OBX 15 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 1.0.0.5 2^auth-body-continua     R<br>OBX 16 ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 1.0.0.4.1 6.1     R |                   |  |  |
+
+OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|1.0.0.4.2|16403|||||R
+
+OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.0.0.5.1|0^unregulated-device(0)|||||R
+
+OBX|19|NM|8418344^MDC\_INS\_BOLUS^MDC|1.0.0.6|1|267616^MDC\_DIM\_X\_INTL\_UNIT^MDC|||||R||20160903124015+0000
+
+OBX|20|NM|8418300^MDC\_INS\_BASAL\_RATE\_SETTING^MDC|1.0.0.7|2|267840^MDC\_DIM\_X\_INTL\_UNIT\_PER\_HR^MDC|||||R||20160903124015+0000
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+  - a. Only one MSA segment is present and:
+    - MSA-1 is one of the following values:
+      - 'AA' – Accept Acknowledgment: Application Accept
+      - 'AR' – Accept Acknowledgment: Application Reject
+    - MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+    - MSA-3 to MSA-8 are empty
+  - b. If ERR segment referring to the MSA is present:
+    - If the HFS receiver reports an ERR segment with Severity (ERR-4) E (Error) or F (Fatal Error), the Message Acknowledgement value shall be CR (Commit Reject)
+    - ERR-1 is empty
+    - ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>
+    - ERR-3 starts with one of the following valid error condition codes and other optional subfields might be included:
+      - '0' – Accepted
+      - '206' – Application record locked
+      - '207' – Application internal error
+    - ERR-4 is set to one of these valid error severity values:
+      - 'W' – Warning
+      - 'I' – Information
+      - 'E' – Error
+      - 'F' – Fatal error.
+    - ERR-5 and ERR-6 are empty
+    - ERR-7 may be empty, but if it is valued, it is a text data
+    - ERR-8 may be empty, but if it is valued, it is a text data
+    - ERR-9 may be empty, but if it is valued, it is one of these values:
+      - 'PAT'
+      - 'NPAT'
+      - 'USR'
+      - 'HD'
+    - ERR-10 may be empty, but if it is valued, it is encoded as: <Identifier (ST)>^<Text (ST)>^< Name of Coding System (ID)> the rest of the element of the CWE data type are not used in Services Interface.
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><input type="checkbox"/> ERR-11 may be empty, but if it is valued, it is encoded as: <i>&lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt; Name of Coding System (ID)&gt;</i> the rest of the element of the CWE data type are not used in Services Interface.</p> <p><input type="checkbox"/> ERR-12 may be empty, but if it is valued, it is encoded as: <i>&lt;WITHDRAWN Constituent&gt;^&lt;Telecommunication Use Code (ID)&gt;^&lt;Telecommunication Equipment Type (ID)&gt;^&lt;Communication Address (ST)&gt;^&lt;Country Code (NM)&gt;^&lt;Area/City Code (NM)&gt;^&lt;Local Number (NM)&gt;^&lt;Extension (NM)&gt;^&lt;Any Text (ST)&gt;^&lt;Extension Prefix (ST)&gt;^&lt;Speed Dial Code (ST)&gt;^&lt;Unformatted Telephone Number (ST)&gt;^&lt;Effective Start Date (DTM)&gt;^&lt;Expiration Date (DTM)&gt;^&lt;Expiration Reason (CWE)&gt;^&lt;Protection Code (CWE)&gt;^&lt;Shared Telecommunication Identifier (EI)&gt;^&lt;Preference Order (NM)&gt;</i></p> <p>Where:</p> <ul style="list-style-type: none"> <li>• Expiration Reason subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li> <li>• Protection code subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li> <li>• Shared Telecommunication Identifier subcomponents are: <i>&lt;Entity Identifier (ST)&gt;&amp;&lt;Namespace ID (IS)&gt;&amp;&lt;Universal ID (ST)&gt;&amp;&lt;Universal ID Type (ID)&gt;</i></li> </ul> <p>Where XTN-2, XTN-3 are required and XTN-4 to XTN-10 are required but may be empty. The rest are not supported.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2, all elements in each segment are as specified above</li> <li>• Verify that the HFS receiver under test is able to accept the data and time stamps (e.g. if there is a log verify the date and the data are displayed in some form that indicates the correct date and time and the correct data as transmitted). Date and time of the measurement: 2016-09-03 12:40:15 UTC, Values: Bolus Delivered=1 [IU], Current Basal Rate Setting=2 [IU/h].</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+## A.19 Subgroup 2.4.18: Continuous glucose monitor (CGM)
+
+|                 |                                   |                 |             |          |
+|-----------------|-----------------------------------|-----------------|-------------|----------|
+| <b>TP Id</b>    | TP/HFS/REC/PCD-01-DATA/CGM/BV-000 |                 |             |          |
+| <b>TP label</b> | MSA and ERR segments              |                 |             |          |
+| <b>Coverage</b> | <b>Spec</b>                       | [ITU-T H.812.1] |             |          |
+|                 | <b>Testable items</b>             | MSAUse; M       | MSA-1; M    | MSA-2; M |
+|                 |                                   | MSA-3; M        | MSA-4; M    | MSA-5; M |
+|                 |                                   | MSA-6; M        | MSA-7; M    | MSA-8; M |
+|                 |                                   | ERRUse 1; O     | ERRUse 2; M | ERR-1; M |
+|                 |                                   | ERR-2; R        | ERR-3; M    | ERR-4; M |
+|                 |                                   | ERR-5; M        | ERR-6; M    | ERR-7; O |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                      |                     |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|---------------------|
+|                          | CWEDataType 1; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | CWEDataType 2; M     | CWEDataType 3; C    |
+|                          | CWEDataType 4; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | NumericDataType 1; M | StringDataType 1; M |
+|                          | DateTimeDataType 1; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | EIDataType 1; M      | EIDataType 2; M     |
+|                          | EIDataType 3; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | EIDataType 4; M      | EIUse1; C           |
+|                          | EIUse2; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | EIUse3; C            | EIUse4; C           |
+|                          | 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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                      |                     |
+| <b>Test purpose</b>      | Check that:<br>The elements of every segment of the message<br>[AND]<br>The data type of each element.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                      |                     |
+| <b>Applicability</b>     | C_REC_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                      |                     |
+| <b>Other PICS</b>        | C_REC_DATA_003, C_REC_DATA_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                      |                     |
+| <b>Initial condition</b> | The HFS receiver under test has published a Web Service and the simulated HFS sender is ready to send a message with an Observation of a Continuous Glucose Monitor device.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                      |                     |
+| <b>Test procedure</b>    | 1. The simulated HFS sender sends the following HL7 message, including the mandatory objects of a Continuous Glucose Monitor device to make the HFS receiver respond with another HL7 message.<br><br>MSH ^~\& AT4_AHD^1234567890ABCDEF^EUI-64   <current time in UTC>  ORU^R01^ORU_R01 MSGID<random number> P 2.6  NE AL   IHE PCD ORU-R012006^HL7^2.16.840.1.1.13883.9.n.m^HL7<br><br>PID   789567^^Imaginary Hospital^PI  Doe^John^Joseph^^^L<br><br>OBR 1 POTest^AT4_AHD^1234567890ABCDEF^EUI-64 POTest^AT4_AHD^1234567890ABCDEF^EUI-64 182777000^monitoring of patient^SNOMED-CT   20160903124015+0000<br><br>OBX 1 531981^MDC_MOC_VMS_MDS_AHD^MDC 0    X    device^^FEEDABEED EADBEEF^EUI-64<br><br>OBX 2 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.1 2^auth-body-continua    R<br><br>OBX 3 ST 532352^MDC_REG_CERT_DATA_CONTINUA_VERSION^MDC 0.0.0.1.1 6.1    R<br><br>OBX 4 NA 532353^MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST^MDC 0.0.0.1.2 16403    R<br><br>OBX 5 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.2 2^auth-body-continua    R<br><br>OBX 6 CWE 532354^MDC_REG_CERT_DATA_CONTINUA_REG_STATUS^MDC 0.0.0.2.1 1^unregulated-device(0)    R<br><br>OBX 7 CWE 68220^MDC_TIME_SYNC_PROTOCOL^MDC 0.0.0.3 532224^MDC_TIME_SYNC_NONE^MDC    R<br><br>OBX 8 CWE 68218^MDC_REG_CERT_DATA_AUTH_BODY^MDC 0.0.0.4 2^auth-body-continua    R |                      |                     |
+
+OBX|9|CWE|64515^MDC\_REG\_CERT\_DATA\_CONTINUA\_AHD\_CERT\_LIST^MDC|0.0.4.1|0~1|||||R
+
+OBX|10||528410^MDC\_DEV\_SPEC\_PROFILE\_CGM^MDC|1|||||X|||||0123456789ABCDEF^0123456789ABCDEF^EUI-64
+
+OBX|11|ST|531969^MDC\_ID\_MODEL\_NUMBER^MDC|1.0.0.1|CGM v1.0|||||R
+
+OBX|12|ST|531970^MDC\_ID\_MODEL\_MANUFACTURER^MDC|1.0.0.2|AT4 Wireless|||||R
+
+OBX|13|DTM|67975^MDC\_ATTR\_TIME\_ABS^MDC|1.0.0.3|20160316135510+0000|||||R||20160316145510+0000
+
+OBX|14|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.4|2^auth-body-continua|||||R
+
+OBX|15|CWE|68218^MDC\_REG\_CERT\_DATA\_AUTH\_BODY^MDC|1.0.0.5|2^auth-body-continua|||||R
+
+OBX|16|ST|532352^MDC\_REG\_CERT\_DATA\_CONTINUA\_VERSION^MDC|1.0.0.4.1|6.1|||||R
+
+OBX|17|NA|532353^MDC\_REG\_CERT\_DATA\_CONTINUA\_CERT\_DEV\_LIST^MDC|1.0.0.4.2|16410|||||R
+
+OBX|18|CWE|532354^MDC\_REG\_CERT\_DATA\_CONTINUA\_REG\_STATUS^MDC|1.0.0.5.1|0^unregulated-device(0)|||||R
+
+OBX|19|NM|160212^MDC\_CONC\_GLU\_ISF^MDC|1.0.0.6|15.8|264274^MDC\_DIM\_MILLI\_G\_PER\_DL^MDC|||||R||20160903124015+0000
+
+2. The HFS receiver under test responds using another HL7 message. Check in the captured message that:
+- a. Only one MSA segment is present and:
+    - MSA-1 is one of the following values:
+      - 'AA' – Accept Acknowledgment: Application Accept
+      - 'AR' – Accept Acknowledgment: Application Reject
+    - MSA-2 contains the message control ID from the MSH-10 (Message Control ID) of the incoming message for which this acknowledgement is being sent
+    - MSA-3 to MSA-8 are empty
+  - b. If ERR segment referring to the MSA is present:
+    - If the HFS receiver reports an ERR segment with Severity (ERR-4) E (Error) or F (Fatal Error), the Message Acknowledgement value shall be CR (Commit Reject)
+    - ERR-1 is empty
+    - ERR-2 should be valued with the location in the message related to the identified error, warning, or message. This field is repeated for errors which result from the combination of multiple locations. Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>
+    - ERR-3 starts with one of the following valid error condition codes and other optional subfields might be included:
+      - '0' – Accepted
+      - '206' – Application record locked
+      - '207' – Application internal error
+    - ERR-4 is set to one of these valid error severity values:
+      - 'W' – Warning
+      - 'I' – Information
+      - 'E' – Error
+      - 'F' – Fatal error.
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> ERR-5 and ERR-6 are empty</li> <li><input type="checkbox"/> ERR-7 may be empty, but if it is valued, it is a text data</li> <li><input type="checkbox"/> ERR-8 may be empty, but if it is valued, it is a text data</li> <li><input type="checkbox"/> ERR-9 may be empty, but if it is valued, it is one of these values: <ul style="list-style-type: none"> <li>• 'PAT'</li> <li>• 'NPAT'</li> <li>• 'USR'</li> <li>• 'HD'</li> </ul> </li> <li><input type="checkbox"/> ERR-10 may be empty, but if it is valued, it is encoded as: <i>&lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt; Name of Coding System (ID)&gt;</i> the rest of the element of the CWE data type are not used in Services Interface.</li> <li><input type="checkbox"/> ERR-11 may be empty, but if it is valued, it is encoded as: <i>&lt;Identifier (ST)&gt;^&lt;Text (ST)&gt;^&lt; Name of Coding System (ID)&gt;</i> the rest of the element of the CWE data type are not used in Services Interface.</li> <li><input type="checkbox"/> ERR-12 may be empty, but if it is valued, it is encoded as: <i>&lt;WITHDRAWN Constituent&gt;^&lt;Telecommunication Use Code (ID)&gt;^&lt;Telecommunication Equipment Type (ID)&gt;^&lt;Communication Address (ST)&gt;^&lt;Country Code (NM)&gt;^&lt;Area/City Code (NM)&gt;^&lt;Local Number (NM)&gt;^&lt;Extension (NM)&gt;^&lt;Any Text (ST)&gt;^&lt;Extension Prefix (ST)&gt;^&lt;Speed Dial Code (ST)&gt;^&lt;Unformatted Telephone Number (ST)&gt;^&lt;Effective Start Date (DTM)&gt;^&lt;Expiration Date (DTM)&gt;^&lt;Expiration Reason (CWE)&gt;^&lt;Protection Code (CWE)&gt;^&lt;Shared Telecommunication Identifier (EI)&gt;^&lt;Preference Order (NM)&gt;</i></li> </ul> <p>Where:</p> <ul style="list-style-type: none"> <li>• Expiration Reason subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li> <li>• Protection code subcomponents are: <i>&lt;Identifier (ST)&gt;&amp;&lt;Text (ST)&gt;&amp;&lt; Name of Coding System (ID)&gt; &amp;&lt;Alternate Identifier (ST)&gt;&amp;&lt;Alternate Text (ST)&gt;&amp;&lt;Name of Alternate Coding System (ID)&gt;&amp;&lt;Coding System Version ID (ST)&gt;&amp;&lt;Alternate Coding System Version ID (ST)&gt;&amp;&lt;Original Text (ST)&gt;</i></li> <li>• Shared Telecommunication Identifier subcomponents are: <i>&lt;Entity Identifier (ST)&gt;&amp;&lt;Namespace ID (IS)&gt;&amp;&lt;Universal ID (ST)&gt;&amp;&lt;Universal ID Type (ID)&gt;</i></li> </ul> <p>Where XTN-2, XTN-3 are required and XTN-4 to XTN-10 are required but may be empty. The rest are not supported.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2, all elements in each segment are as specified above</li> <li>• Verify that the HFS receiver under test is able to accept the data and time stamps (e.g. if there is a log verify the date and the data are displayed in some form that indicates the correct date and time and the correct data as transmitted). Date and time of the measurement: 2016-09-03 12:40:15 UTC, Values: Glucose concentration from interstitial fluid =15.8 [mg/dl]'. </li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+# 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*.  
+<https://docbox.etsi.org/MTS/MTS/10-PromotionalMaterial/MBS-20111118/Referenced%20Documents/Drafting%20Rules.pdf>
+- [b-HFSR PICS & PIXIT] Services HFS Receiver DG2016 *PICS and PIXIT excel sheet v1.7*.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-HFSS PICS & PIXIT] Services HFS Sender DG2016 *PICS and PIXIT excel sheet v1.7*.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-SOAP 1.2] W3C SOAP 1.2 (2007), *SOAP Version 1.2 (Second Edition)*.  
+<http://www.w3.org/TR/soap>
+
+
+
+
+
+# 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.7-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg b/marked/H/T-REC-H.830.7-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..61904c12b802df120c05ae72cd89a3ef2690dd5b
--- /dev/null
+++ b/marked/H/T-REC-H.830.7-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_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.830.7-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.830.7-201704-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..06069da52d4fc8f2205a74282b26c83374e34a72
--- /dev/null
+++ b/marked/H/T-REC-H.830.7-201704-I_PDF-E/raw.md
@@ -0,0 +1,884 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.830.7**
+
+(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 7: Consent  
+management: Health & Fitness Service sender**
+
+Recommendation ITU-T H.830.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                                                                                       | 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        |
+| <b>Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN)</b> | <b>H.820–H.859</b> |
+| 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.7
+
+## Conformance of ITU-T H.810 personal health system: Services interface Part 7: Consent management: Health & Fitness Service sender
+
+## Summary
+
+Recommendation ITU-T H.830.7 provides a test suite structure (TSS) and the test purposes (TP) for consent management 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.7 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Services Interface; Part 7: Consent Management. HFS Sender (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.837    | 2015-01-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/12255">11.1002/1000/12255</a> |
+| 1.0     | ITU-T H.830.7  | 2015-01-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/12593">11.1002/1000/12593</a> |
+| 2.0     | ITU-T H.830.7  | 2016-07-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12926">11.1002/1000/12926</a> |
+| 3.0     | ITU-T H.830.7  | 2017-04-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/13208">11.1002/1000/13208</a> |
+
+## Keywords
+
+Conformance testing, Consent Management, Continua Design Guidelines, e-health, Health & Fitness Service sender, ITU-T H.810, personal connected health devices, Services Interface.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.5.1: HFS XDR transaction (TRANS) .....           | 9  |
+| A.3     | Subgroup 1.5.2: HFS metadata validation (META).....         | 10 |
+| A.4     | Subgroup 1.5.3: HFS consent directive validation (CDV)..... | 17 |
+|         | 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, Services Interface; Part 7: Consent Management. HFS Sender (Version 1.5, 2017-03-14), that was developed by the Continua 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. This uses "TSS&TP_DG2011_WAN_PART_7_(SEN CM)_v1.0" as a baseline and it adds minor modifications included in [b-CDG 2012] for consent management.                                                                                                |
+| 1.1     | 2014-01-24 | Initial release for Test Tool DG2013. This is the same version as "TSS&TP_DG2012_WAN_PART_7_(SEN CM)_v1.1.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.2     | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_WAN_PART_7_(SEN CM)_v1.1.doc" as baseline and it adds new features included in Documentation Enhancements: <ul style="list-style-type: none"> <li>"Other PICS" row has been added</li> </ul> |
+| 1.3     | 2015-07-01 | Initial release for Test Tool DG2015: <ul style="list-style-type: none"> <li>Test suite structure and applicability modified</li> </ul>                                                                                                                                                |
+| 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.7
+
+## Conformance of ITU-T H.810 personal health system: Services interface Part 7: Consent management: Health & Fitness Service sender
+
+# 1 Scope
+
+The scope of this Recommendation<sup>1</sup> 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 7.
+
+- 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*.
+
+---
+
+<sup>1</sup> 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), <i>Interoperability design guidelines for personal health systems: Services interface: Observation upload certified capability class.</i>                                                                                                                                                                                                              |
+| [ITU-T H.812.2] | Recommendation ITU-T H.812.2 (2016), <i>Interoperability design guidelines for personal health systems: Services interface: Questionnaires certified capability class.</i>                                                                                                                                                                                                                  |
+| [ITU-T H.812.3] | Recommendation ITU-T H.812.3 (2016), <i>Interoperability design guidelines for personal health systems: Services interface: Capability exchange certified capability class.</i>                                                                                                                                                                                                             |
+| [ITU-T H.812.4] | Recommendation ITU-T H.812.4 (2016), <i>Interoperability design guidelines for personal health systems: Services interface: Authenticated persistent session certified capability class.</i>                                                                                                                                                                                                |
+| [HL7 CDA IG]    | Health Level Seven (2011), <i>HL7 Implementation Guide for Clinical Document Architecture, Release 2: Consent Directives, Release 1, HL7 Draft Standard for Trial Use.</i><br><a href="http://www.hl7.org/documentcenter/public/standards/dstu/CDAR2_IG%20_CONSENTDIR_DSTU_2011JAN.pdf">http://www.hl7.org/documentcenter/public/standards/dstu/CDAR2_IG%20_CONSENTDIR_DSTU_2011JAN.pdf</a> |
+| [IHE ITI TF-2b] | IHE IT TF-2b (2009), <i>IHE ITI Infrastructure Technical Framework, Volume 2b: Transactions Part B. Revision 6.0 Final Text.</i><br><a href="http://www.ihe.net/technical_framework/upload/ihe_iti_tf_6-0_vol2b_ft_2009-08-10.pdf">www.ihe.net/technical_framework/upload/ihe_iti_tf_6-0_vol2b_ft_2009-08-10.pdf</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:
+
+|       |                                                      |
+|-------|------------------------------------------------------|
+| 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                            |
+| SABTE  | Sleep Apnoea Breathing Therapy Equipment              |
+| 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                      |
+| 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                                                                                                   | –           |
+
+**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 1.5.1 to 1.5.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 <http://handle.itu.int/11.1002/2000/12067>.
+
+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>/<DUT>/<GR>/<SGR>/<XX> – <NNN>). It is specified according to the naming convention defined below:
+  - Each test purpose identifier is introduced by the prefix "TP".
+  - <TT>: This is the test tool that will be used in the test case.
+    - HFS: Health & Fitness Services Interface
+  - <DUT>: This is the device under test.
+    - SEN: HFS sender
+    - REC: HFS receiver
+  - <GR>: This identifies a group of test cases.
+  - <SGR>: This identifies a subgroup of test cases.
+  - <XX>: This identifies the type of testing.
+    - BV: Valid behaviour test
+    - BI: Invalid behaviour test
+  - <NNN>: 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 1.5.1: HFS XDR transaction (TRANS)
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                           |                                             |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|---------------------------------------------|
+| <b>TP Id</b>             | TP/HFS/SEN/CM/TRANS/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                           |                                             |
+| <b>TP label</b>          | Provide and Register Document Set-b Transaction Request                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                           |                                             |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ITU-T H.812]                             |                                             |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | ConsentSender3; M                         |                                             |
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [IHE ITI TF-2b]                           |                                             |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | ProvideProtocol12; M<br>ProvideSource1; M | ProvideProtocol13; M<br>ProvideProtocol2; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Consent Enabled HFS sender shall send the consent document at least once to the HFS receiver</p> <p>[AND]</p> <p>The Document Source shall generate Provide and Register Document Set-b transactions in MTOM/XOP format.</p> <p>[AND]</p> <p>The Document Source shall accept the response message in MTOM/XOP format.</p> <p>[AND]</p> <p>The Provide and Register Document Set-b transaction shall use SOAP12 and MTOM with XOP encoding.</p> <p>[AND]</p> <p>An implementation of the Document Source actor shall be capable of submit one or more documents.</p>                                                                                                                                                                                                                                                                                                                                                                                                                     |                                           |                                             |
+| <b>Applicability</b>     | C_SEN_000 AND C_SEN_GEN_002 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                           |                                             |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                           |                                             |
+| <b>Initial condition</b> | <p>The HFS simulated receiver has a WebService enabled with a consent management service.</p> <p>The HFS sender under test has a clinical document architecture (CDA) ready to be sent to the respective service according to its needs.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                           |                                             |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The HFS sender under test sends a "Provide and Register Document Set-b Request" message.</li> <li>2. Check that:           <ol style="list-style-type: none"> <li>a. In the HTTP header:               <ul style="list-style-type: none"> <li>• action="urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b"</li> <li>• Content-Type = multipart/related</li> <li>• boundary element is a MIMEBoundary</li> <li>• type = "application/xop+xml"</li> </ul> </li> <li>b. In the SOAP message               <ul style="list-style-type: none"> <li>• The namespace of the SOAP envelope is "http://www.w3.org/2003/05/soap-envelope" (SOAP 1.2)</li> <li>• There are one or more xsdb:Document elements in the SOAP Body.</li> </ul> </li> </ol> </li> <li>3. The simulated HFS receiver responds with a "Provide and Register Document Set-b Response" message</li> <li>4. The HFS sender under test accepts the message (it does not give any error message).</li> </ol> |                                           |                                             |
+
+|                           |                                                             |
+|---------------------------|-------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | All steps are as specified within the test procedure above. |
+| <b>Notes</b>              |                                                             |
+
+### A.3 Subgroup 1.5.2: HFS metadata validation (META)
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                   |                     |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|
+| <b>TP Id</b>             | TP/HFS/SEN/CM/META/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                   |                     |
+| <b>TP label</b>          | Metadata Syntactic Validation                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                   |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [IHE ITI TF-2b]   |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | ProvideScope1; M  | ProvideProtocol9; M |
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [ITU-T H.812]     |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | ConsentSender4; M | ConsentSender 5; M  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>A Provide and Register Document Set-b transaction shall carry:</p> <ul style="list-style-type: none"> <li>- Metadata describing zero or more documents</li> <li>- Within metadata, one XDSDocumentEntry object per document</li> <li>- XDS Submission Set definition along with the linkage to new documents and references to existing documents</li> <li>- Zero or more XDS Folder definitions along with the linkage to new or existing documents</li> <li>- Zero or more documents</li> </ul> <p>[AND]</p> <p>The &lt;ihe:ProvideAndRegisterDocumentSetRequest/&gt; element is defined as:</p> <ul style="list-style-type: none"> <li>- One &lt;lcm:SubmitObjectsRequest/&gt; element that contains the submission set metadata</li> <li>- Zero or more &lt;ihe:Document/&gt; elements that contain the base64encoded data for the documents being submitted to the Document Repository. The &lt;ihe:Document/&gt; also includes the document id attribute (ihe:Document/@id) of type xsd:anyURI to match the document ExtrinsicObject id in the metadata and providing the necessary linkage</li> </ul> <p>[AND]</p> <p>The consent document transmitted by the Consent Enabled HFS sender shall contain the same Patient Identifier as the HFS Observation measurement message(s).</p> |                   |                     |
+| <b>Applicability</b>     | C_SEN_000 AND C_SEN_GEN_002 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                   |                     |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                   |                     |
+| <b>Initial condition</b> | <p>The simulated HFS receiver has a WebService enabled with a consent management service and a CommunicatePCDDData service. The HFS sender under test has a CDA ready to be sent to the respective service according to its needs.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                   |                     |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The HFS sender under test sends a "Provide and Register Document Set-b Request" message to the consent management service and a "PCD-01" message to the CommunicatePCDDData service.</li> <li>2. Check that in the SOAP body:           <ol style="list-style-type: none"> <li>a. There is only one &lt;ProvideAndRegisterDocumentSetRequest/&gt; element, and that it contains:               <ul style="list-style-type: none"> <li>o Only one &lt;lcm:SubmitObjectsRequest/&gt; element, that contains:                   <ul style="list-style-type: none"> <li>- A XDSDocumentEntry (ExtrinsicObject) element for each document</li> <li>- An XDS Submission Set definition along with the linkage to new</li> </ul> </li> </ul> </li> </ol> </li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                   |                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>documents and references to existing documents (RegistryPackage element)</p> <ul style="list-style-type: none"> <li>- Zero or more XDS Folder definitions along with the linkage to new or existing documents. <ul style="list-style-type: none"> <li>o Zero or more &lt;ihe:Document/&gt; elements.</li> </ul> </li> </ul> <p>b. The PID-3 element of the "PCD-01" message is equal to SubmitObjectsRequest/RegistryObjectList/ExtrinsicObject/Slot[@name = sourcePatientId]/ValueList/Value element of the metadata, and:</p> <ul style="list-style-type: none"> <li>o Subfields CX-1 and CX-4 are present.</li> <li>o Subfield CX-5 is not present.</li> </ul> |
+| <b>Pass/Fail criteria</b> | All steps are as specified within the test procedure above.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                 |                 |
+|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------|
+| <b>TP Id</b>        | TP/HFS/SEN/CM/META/BV-001                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                 |                 |
+| <b>TP label</b>     | Metadata Submission Set Validation                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                 |                 |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ITU-T H.812]   |                 |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | WANXDSSub-1; O  | WANXDSSub-2; M  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | WANXDSSub-4; M  | WANXDSSub-5; M  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | WANXDSSub-7; O  | WANXDSSub-8; M  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | WANXDSSub-10; M | WANXDSSub-11; M |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | WANXDSSub-13; M | WANXDSSub-14; M |
+| <b>Test purpose</b> | <p>Check that:</p> <p>availabilityStatus element MAY be present<br/>[AND]</p> <p>author element SHALL be equal to Consent Directive /ClinicalDocument/author<br/>[AND]</p> <p>authorInstitution element SHALL be equal to Consent Directive /ClinicalDocument/author/assignedAuthor/representedOrganization<br/>[AND]</p> <p>authorPerson element SHALL be equal to Consent Directive /ClinicalDocument/author/assignedAuthor/assignedPerson<br/>[AND]</p> <p>authorRole element SHALL be equal to Consent Directive /ClinicalDocument/author/assignedAuthor/participationFunction<br/>[AND]</p> <p>authorSpecialty element SHALL be equal to Consent Directive /ClinicalDocument/author/assignedAuthor/code<br/>[AND]</p> <p>comments element MAY be present<br/>[AND]</p> <p>contentTypeCode element SHALL be present<br/>[AND]</p> <p>contentTypeCodeDisplayName element MAY be present</p> |                 |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>[AND]</p> <p>entryUUID element SHALL be equal to Consent Directive unique ID for submission set</p> <p>[AND]</p> <p>patientId element SHALL be mapped from /ClinicalDocument/recordTarget/patientRole/id</p> <p>[AND]</p> <p>sourceId element SHALL be present</p> <p>[AND]</p> <p>submissionTime element SHALL be present</p> <p>[AND]</p> <p>title element SHALL be equal to Consent Directive /ClinicalDocument/title</p> <p>[AND]</p> <p>uniqueId element SHALL be equal to Consent Directive /ClinicalDocument/id</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_GEN_002 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Initial condition</b>  | The simulated HFS receiver has a WebService enabled with a consent management service. The HFS sender under test has a CDA ready to be sent to the respective service according to its needs.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The HFS sender under test sends a "Provide and Register Document Set-b Request" message containing a CDA referenced in its body</li> <li>2. Check the following elements of the "Metadata in Submission Set" section sent by the HFS sender under test and its concordance with the clinical document: <ol style="list-style-type: none"> <li>a. availabilityStatus element may be present</li> <li>b. author element is equal to Consent Directive /ClinicalDocument/author</li> <li>c. authorInstitution element is equal to Consent Directive /ClinicalDocument/author/assignedAuthor/representedOrganization</li> <li>d. authorPerson element is equal to Consent Directive /ClinicalDocument/author/assignedAuthor/assignedPerson</li> <li>e. authorRole element is equal to Consent Directive /ClinicalDocument/author/participationFunction</li> <li>f. authorSpecialty element Is equal to Consent Directive /ClinicalDocument/author/assignedAuthor/code</li> <li>g. comments element may be present</li> <li>h. contentTypeCode element Is present</li> <li>i. entryUUID element is equal to Consent Directive unique ID for submission set</li> <li>j. patientId element is mapped from /ClinicalDocument/recordTarget/patientRole/id</li> <li>k. sourceId element is present</li> <li>l. submissionTime element is present</li> <li>m. title element is equal to Consent Directive /ClinicalDocument/title</li> <li>n. uniqueId element is equal to Consent Directive /ClinicalDocument/id.</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | All steps are as specified within the test procedure above.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                 |                                    |
+|-----------------|------------------------------------|
+| <b>TP Id</b>    | TP/HFS/SEN/CM/META/BV-002          |
+| <b>TP label</b> | Metadata Document Entry Validation |
+
+|                     |                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                      |                      |
+|---------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------|
+| <b>Coverage</b>     | <b>Spec</b>           | [ITU-T H.812]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                      |                      |
+|                     | <b>Testable items</b> | WANXDSDocEntry-1; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | WANXDSDocEntry-2; M  | WANXDSDocEntry-3; M  |
+|                     |                       | WANXDSDocEntry-4; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | WANXDSDocEntry-5; M  | WANXDSDocEntry-6; M  |
+|                     |                       | WANXDSDocEntry-7; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | WANXDSDocEntry-8; O  | WANXDSDocEntry-9; O  |
+|                     |                       | WANXDSDocEntry-10; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | WANXDSDocEntry-11; M | WANXDSDocEntry-12; M |
+|                     |                       | WANXDSDocEntry-13; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | WANXDSDocEntry-14; M | WANXDSDocEntry-15; O |
+|                     |                       | WANXDSDocEntry-16; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | WANXDSDocEntry-17; O | WANXDSDocEntry-18; M |
+|                     |                       | WANXDSDocEntry-19; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | WANXDSDocEntry-20; M | WANXDSDocEntry-21; M |
+|                     |                       | WANXDSDocEntry-22; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | WANXDSDocEntry-23; M | WANXDSDocEntry-24; M |
+|                     |                       | WANXDSDocEntry-25; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | WANXDSDocEntry-26; O | WANXDSDocEntry-27; O |
+|                     |                       | WANXDSDocEntry-28; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | WANXDSDocEntry-29; M | WANXDSDocEntry-30; M |
+|                     |                       | WANXDSDocEntry-31; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | WANXDSDocEntry-32; M | WANXDSDocEntry-33; M |
+|                     |                       | WANXDSDocEntry-34; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | WANXDSDocEntry-35; M | WANXDSDocEntry-36; M |
+|                     |                       | WANXDSDocEntry-37; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | WANXDSDocEntry-38; M | WANXDSDocEntry-39; M |
+|                     |                       | WANXDSDocEntry-40; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | WANXDSDocEntry-41; M | WANXDSDocEntry-42; M |
+|                     |                       | WANXDSDocEntry-43; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                      |                      |
+| <b>Test purpose</b> |                       | Check that:<br>availabilityStatus element MAY be present<br>[AND]<br>author element SHALL be equal to Consent Directive /ClinicalDocument/author<br>[AND]<br>authorInstitution element SHALL be equal to Consent Directive /ClinicalDocument/author/assignedAuthor/representedOrganization/name, id<br>[AND]<br>authorPerson element SHALL be equal to Consent Directive /ClinicalDocument/author/assignedAuthor/assignedPerson<br>[AND]<br>authorRole element SHALL be equal to Consent Directive /ClinicalDocument/author/assignedAuthor/participationFunction/code<br>[AND]<br>authorSpecialty element SHALL be equal to Consent Directive /ClinicalDocument/author/assignedAuthor/participationFunction<br>[AND]<br>classCode element SHALL be present and SHALL use the LOINC code 57016-8<br>[AND]<br>classCodeDisplayName element MAY be present<br>[AND]<br>Comments element MAY be present<br>[AND]<br>confidentialityCode element SHALL be equal to Consent Directive |                      |                      |
+
+/ClinicalDocument/confidentialityCode  
+[AND]  
+confidentialityCodeDisplayName element SHALL be equal to Consent Directive  
+/ClinicalDocument/confidentialityCode  
+[AND]  
+creationTime element SHALL be equal to Consent Directive /ClinicalDocument/effectiveTime  
+[AND]  
+entryUUID element SHALL be present  
+[AND]  
+eventCodeList element SHALL be equal to Consent Directive  
+/ClinicalDocument/documentationOf/serviceEvent/code  
+[AND]  
+eventCodeDisplayNameList element MAY be present  
+[AND]  
+formatCode element SHALL be present and equal to “urn:continua:cd:2011”  
+[AND]  
+formatCodeDisplayName element MAY be present  
+[AND]  
+hash element SHALL be present  
+[AND]  
+healthcareFacilityTypeCode element SHALL be present  
+[AND]  
+healthcareFacilityTypeCodeDisplayName element MAY be present  
+[AND]  
+languageCode element SHALL be equal to Consent Directive  
+/ClinicalDocument/languageCode  
+[AND]  
+legalAuthenticator element SHALL be equal to Consent Directive  
+/ClinicalDocument/legalAuthenticator  
+[AND]  
+mime type element SHALL be equal to Consent Directive text/xml  
+[AND]  
+parentDocument element MAY come from  
+/ClinicalDocument/relatedDocument/parentDocument  
+[AND]  
+parentDocumentId element MAY come from  
+/ClinicalDocument/relatedDocument/parentDocument/id  
+[AND]  
+parentDocumentRelationship element MAY come from  
+/ClinicalDocument/relatedDocument/typeId  
+[AND]  
+patientId element SHALL be equal to Consent Directive  
+/ClinicalDocument/recordTarget/patientRole/id  
+[AND]  
+practiceSettingCode element SHALL be present  
+[AND]  
+practiceSettingCodeDisplayName element SHALL be present
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | <p>[AND]</p> <p>serviceStartTime element SHALL be equal to Consent Directive /ClinicalDocument/documentationOf/serviceEvent/effectiveTime/low</p> <p>[AND]</p> <p>serviceStopTime element SHALL be equal to Consent Directive /ClinicalDocument/documentationOf/serviceEvent/effectiveTime/high</p> <p>[AND]</p> <p>size element SHALL be present</p> <p>[AND]</p> <p>sourcePatientId element SHALL be equal to Consent Directive /ClinicalDocument/recordTarget/patientRole/id</p> <p>[AND]</p> <p>sourcePatientInfo element SHALL be equal to Consent Directive /ClinicalDocument/recordTarget/patientRole/id</p> <p>[AND]</p> <p>title element SHALL be equal to Consent Directive /ClinicalDocument/title</p> <p>[AND]</p> <p>typeCode element SHALL be equal to Consent Directive /ClinicalDocument/code/@code</p> <p>[AND]</p> <p>typeCodeDisplayName element SHALL be equal to Consent Directive /ClinicalDocument/code/@displayName</p> <p>[AND]</p> <p>uniqueId element SHALL be equal to Consent Directive /ClinicalDocument/id</p> <p>[AND]</p> <p>URI element MAY be present</p> <p>[AND]</p> <p>parentDocument element SHALL NOT be present</p> <p>[AND]</p> <p>parentDocumentId element SHALL NOT be present</p> <p>[AND]</p> <p>parentDocumentRelationship element SHALL NOT be present</p> |
+| <b>Applicability</b>     | C_SEN_000 AND C_SEN_GEN_002 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Initial condition</b> | The simulated HFS receiver has a WebService enabled with a consent management service. The HFS sender under test has a CDA ready to be sent to the respective service according to its needs.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The HFS sender under test sends a "Provide and Register Document Set-b Request" message containing a CDA referenced in its body</li> <li>2. Check the following elements of the metadata in the "Document Entry" section sent by the HFS sender under test and its concordance with the clinical document: <ol style="list-style-type: none"> <li>a. availabilityStatus element may be present</li> <li>b. author element is equal to Consent Directive /ClinicalDocument/author</li> <li>c. authorInstitution element is equal to Consent Directive /ClinicalDocument/author/assignedAuthor/representedOrganization/name, id</li> <li>d. authorPerson element is equal to Consent Directive /ClinicalDocument/author/assignedAuthor/assignedPerson</li> </ol> </li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+- e. authorRole element is equal to Consent Directive /ClinicalDocument/author/assignedAuthor/code
+- f. authorSpecialty element is equal to Consent Directive /ClinicalDocument/author/assignedAuthor/code/@code
+- g. classCode element is equal to LOINC code 57016-8
+- h. classCodeDisplayName element may be present
+- i. comments element may be present
+- j. confidentialityCode element is equal to Consent Directive /ClinicalDocument/confidentialityCode
+- k. confidentialityCodeDisplayName element is equal to Consent Directive /ClinicalDocument/confidentialityCode
+- l. creationTime element is equal to Consent Directive /ClinicalDocument/effectiveTime
+- m. entryUUID element is present
+- n. eventCodeDisplayNameList element may be present
+- o. formatCode element is equal to "urn:continua:cd:2011"
+- p. formatCodeDisplayName element may be present
+- q. hash element is present
+- r. healthcareFacilityTypeCode element is present
+- s. healthcareFacilityTypeCodeDisplayName element may be present
+- t. languageCode element is equal to Consent Directive /ClinicalDocument/languageCode
+- u. legalAuthenticator element is equal to Consent Directive /ClinicalDocument/legalAuthenticator
+- v. mimeType element is equal to Consent Directive text/xml
+- w. parentDocument element may come from /ClinicalDocument/relatedDocument/parentDocument
+- x. parentDocumentId element may come from /ClinicalDocument/relatedDocument/parentDocument/id
+- y. parentDocumentRelationship element may come from /ClinicalDocument/relatedDocument/typeId
+- z. patientId element is equal to Consent Directive /ClinicalDocument/recordTarget/patientRole/id
+- aa. practiceSettingCode element Is present
+- bb. practiceSettingCodeDisplayName element Is present
+- cc. serviceStartTime element is equal to Consent Directive /ClinicalDocument/documentationOf/serviceEvent/effectiveTime/low
+- dd. serviceStopTime element is equal to Consent Directive /ClinicalDocument/documentationOf/serviceEvent/effectiveTime/high
+- ee. size element is present
+- ff. sourcePatientId element is equal to Consent Directive /ClinicalDocument/recordTarget/patientRole/id
+- gg. sourcePatientInfo element is equal to Consent Directive /ClinicalDocument/recordTarget/patientRole/id
+- hh. title element is equal to Consent Directive /ClinicalDocument/title
+- ii. typeCode element is equal to Consent Directive /ClinicalDocument/code/@code
+- jj. typeCodeDisplayName element is equal to Consent Directive /ClinicalDocument/code/@displayName
+- kk. uniqueId element is equal to Consent Directive /ClinicalDocument/id
+- ll. URI element may be present
+
+|                           |                                                             |
+|---------------------------|-------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | All steps are as specified within the test procedure above. |
+| <b>Notes</b>              |                                                             |
+
+### A.4 Subgroup 1.5.3: HFS consent directive validation (CDV)
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                |                 |                |
+|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-----------------|----------------|
+| <b>TP Id</b>        | TP/HFS/SEN/CM/CDV/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                |                 |                |
+| <b>TP label</b>     | Consent Directive Validation                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                |                 |                |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [HL7 CDA IG]   |                 |                |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | CONF-CD-1; M   | CONF-CD-2; M    | CONF-CD-2.2; M |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | CONF-CD-3; M   | CONF-CD-4; O    | CONF-CD-4.2; O |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | CONF-CD-4.3; O | CONF-CD-4.4; O  | CONF-CD-5; O   |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | CONF-CD-6; O   | CONF-CD-7; O    | CONF-CD-8; O   |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | CONF-CD-9; O   | CONF-CD-10; M   | CONF-CD-11; M  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | CONF-CD-12; O  | CONF-CD-12.2; O | CONF-CD-13; M  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | CONF-CD-14; M  | CONF-CD-15; M   | CONF-CD-16; M  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | CONF-CD-17; M  | CONF-CD-18; M   | CONF-CD-19; R  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | CONF-CD-20; R  | CONF-CD-21; O   | CONF-CD-22; R  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | CONF-CD-23; R  | CONF-CD-24; O   | CONF-CD-25; M  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | CONF-CD-26; M  | CONF-CD-27; M   | CONF-CD-28; O  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | CONF-CD-29; R  | CONF-CD-30; R   | CONF-CD-31; O  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | CONF-CD-32; O  | CONF-CD-33; O   | CONF-CD-34; M  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | CONF-CD-35; O  | CONF-CD-36; R   | CONF-CD-37; O  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | CONF-CD-38; R  | CONF-CD-39; O   | CONF-CD-41; C  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | CONF-CD-42; O  |                 |                |
+| <b>Test purpose</b> | <p>Check that:</p> <p>A document conforming to the CDA R2 General Header template shall include the ClinicalDocument/templateId "2.16.840.1.113883.10.20.3"</p> <p>[AND]</p> <p>ClinicalDocument/templateId element shall be present with the value "2.16.840.1.113883.3.445.1"</p> <p>[AND]</p> <p>Each Privacy Consent Directive must specify a healthcare client whose IIHI is affected by the privacy consent directive.</p> <p>[AND]</p> <p>ClinicalDocument/author element shall be present and specify a templateId if "2.16.840.1.113883.3.445.2"</p> <p>[AND]</p> <p>ClinicalDocument/author/functionCode/ may be present to specify function/relationship of the author to the client who is the record target. This element may be used to specify the client's relationship to the Substitute Decision Maker – if one is involved in the creation of the privacy</p> |                |                 |                |
+
+consent directive
+
+[AND]
+
+Information Recipient is used to specify the recipients of the Privacy Consent Directive. In the case of consultations and referrals, the Privacy Consent Directive recipient may be the same person/entity as the intended recipient of the client IIHI that is disclosed as a result of the permission granted using the Privacy Consent Directive.
+
+[AND]
+
+The legalAuthenticator is as defined in CDA. For a Privacy Consent Document this element may be either the client or their Substitute Decision Maker. If necessary, the Signatures section may provide the signature associated with the consenter's signature.
+
+[AND]
+
+In some cases, a Privacy Consent Document may identify and record the signature of a person who witnessed the consenter's signature. This may occur if the authenticator/consenter makes a mark instead of a signature.
+
+[AND]
+
+ClinicalDocument/documentationOf/serviceEvent/ element with a templateId of "2.16.840.1.113883.3.445.3" may be present
+
+[AND]
+
+ClinicalDocument/documentationOf/serviceEvent/id element may be present
+
+[AND]
+
+ClinicalDocument/documentationOf/serviceEvent/effectiveTime element may be present
+
+[AND]
+
+ClinicalDocument/documentationOf/serviceEvent/effectiveTime/low/@value element may be present. It may be different than the value of the ClinicalDocument/documentationOf/serviceEvent/effectiveTime/@value and represents the first time the Privacy Consent Directive takes effect
+
+[AND]
+
+ClinicalDocument/documentationOf/serviceEvent/effectiveTime/high/@value element may be present to specify the date/time when the Privacy Consent Directives expires
+
+[AND]
+
+ClinicalDocument/documentationOf/serviceEvent/code/@code attribute shall be present and indicates the OID of the externally identified and defined privacy policy corresponding to the "Privacy Policy Acknowledgement Document"
+
+[AND]
+
+ClinicalDocument/documentationOf/serviceEvent/code/@codeSystem attribute shall be present and indicates the assigning authority of the externally identified and defined privacy policy corresponding to the "Privacy Policy Acknowledgement Document"
+
+[AND]
+
+ClinicalDocument/documentationOf/serviceEvent/code/@codeSystemName attribute may be present and be a descriptive text of the privacy policy being acknowledged.
+
+[AND]
+
+A Privacy Consent Directive may replace a previous (revoked) or expired Privacy Consent Directive.
+
+[AND]
+
+/ClinicalDocument/confidentialityCode/@code SHALL be present and SHALL be equal to "R"
+
+[AND]
+
+/ClinicalDocument/confidentialityCode/@codeSystem SHALL be present and SHALL be equal to 2.16.840.1.113883.5.25
+
+[AND]
+
+If present, /ClinicalDocument/confidentialityCode/@codeSystemName SHALL be equal to "Confidentiality"
+
+[AND]
+
+If present, /ClinicalDocument/confidentialityCode/@displayName SHALL be equal to "Restricted"[AND]
+
+A Privacy Consent Directive shall have a structuredBody element
+
+[AND]
+
+A Privacy Consent Directive shall contain a Privacy Consent Directive Details section
+
+[AND]
+
+This section shall include the templateId for the Privacy Consent Directive section with the value "2.16.840.1.113883.3.445.17" and a title of "Privacy Consent Directive Details".
+
+[AND]
+
+This section shall include an entry element with templateId of "2.16.840.1.113883.3.445.4" and a typeCode of "COMP" to organize the structure of a Privacy Consent Directive entry.
+
+[AND]
+
+This entry element shall include an act element with templateId of "2.16.840.1.113883.3.445.5" and a moodCode of "DEF" to specify the execution of a Privacy Consent Directive.
+
+[AND]
+
+The act element shall include a code element to specify the purpose of use for which the privacy consent is applicable
+
+[AND]
+
+This section should include one or more entry/act/informant/[ @typeCode='CST'] elements with a templateId of "2.16.840.1.113883.3.445.6" to represent the custodian of the referenced IIHI. This may be different than the custodian of the Privacy Consent Directive document identified in the header. Note, if the informant is different from the custodian of the IIHI, then the informant is re-disclosing, which typically is not allowed.
+
+[AND]
+
+This section should include one or more entry/act/participant/[ @typeCode='IRCP'] elements with a templateId of "2.16.840.1.113883.3.445.7" to represent the provider organization or person intended to use, access, collect information as allowed or prevented by the action specified in this privacy consent directive.
+
+[AND]
+
+The participant element may include participantRole/codeSystem specification of "2.16.840.1.113883.11.19682" corresponding to the receiving provider's role [DYNAMIC].
+
+[AND]
+
+The participantRole element should include playingEntity element corresponding to the organization or provider intended to receive the information specified in this Privacy Consent Directive document.
+
+[AND]
+
+This section should include one or more entry/act/participant/ elements to represent the provider organization or person intended to use, access, collect information, as allowed or prevented by the action specified in this privacy consent directive.
+
+[AND]
+
+This section may include an entry/act/entryRelationship with a templateId of "2.16.840.1.113883.3.445.8" to represent the action allowed and problem associated with the information allowed by the Privacy Consent Directive.
+
+[AND]
+
+This entryRelationship shall include an act element with default classCode="ACT" and moodCode="DEF".
+
+[AND]
+
+This act element should include a @negationId attribute with a default value of "false" indicating that the action specified is enabled, and a value of "true" if the action is not allowed by the Privacy Consent Directive. When the negationId attribute is not transmitted, the receiver must assume the default (specified action is enabled).
+
+[AND]
+
+The act element shall include a code element with default of codeSystem="2.16.840.1.113883.5.4" to specify the Privacy Consent Directive operation or action [DYNAMIC].
+
+[AND]
+
+This section may include an entry/act/entryRelationship/ with a templateId of "2.16.840.1.113883.3.445.9" to represent the entire set of protected information (IIHI) including specific attributes of that information (e.g., category type, related diagnosis, sensitivity/confidentiality).
+
+[AND]
+
+The observation element should include one or more organizer/component/observation[@moodCode='DEF']/ elements with a templateId of "2.16.840.1.113883.3.445.10" to specify each information type (IIHI) included in the authorization contained in the Privacy Consent Directive document.
+
+[AND]
+
+The observation element should include a code element to specify the code corresponding to the information type (IIHI) included in the authorization contained in the Privacy Consent Directive document.
+
+[AND]
+
+The observation element may include a precondition[@typeCode="PRCN"]/ element with a templateId of "2.16.840.1.113883.3.445.11" to specify the diagnosis or problem associated with the information.
+
+[AND]
+
+The observation element may include a precondition[@typeCode="PRCN"]/ element with a templateId of "2.16.840.1.113883.3.445.12" to specify the sensitivity of the protected information (IIHI) specified in Privacy Consent Directive.
+
+[AND]
+
+This section may include an entry/act/entryRelationship with a templateId of "2.16.840.1.113883.3.445.13" to represent references to Privacy Policies on which the Privacy Consent Directive is based along with the information recipient Obligation.
+
+[AND]
+
+The component element shall include an act/code element to specify the Privacy Policy or regulation that is basis for requesting the authorizations specified in the Privacy Consent Directive.
+
+[AND]
+
+The component element may include a precondition element with a templateId of "2.16.840.1.113883.3.445.14" and an element of @typeCode="PRCN" to specify any additional obligations imposed on the recipient of the IIHI referenced in the Privacy Consent Directive.
+
+[AND]
+
+The component element should include a criterion[classCode="OBS"]/code element to specify the coded obligations imposed on the recipient of the IIHI referenced in the Privacy Consent Directive.
+
+[AND]
+
+This section may include an entry/act/entryRelationship with a templateId of "2.16.840.1.113883.3.445.15" to include a scanned image of the paper-based Privacy Consent Directive.
+
+[AND]
+
+The entryRelationship element should include an observationMedia[@classCode="OBS"] element to embed a scanned document representation of the Privacy Consent Directive including required signatures.
+
+[AND]
+
+This section may include an entry/act/entryRelationship with a templateId of "2.16.840.1.113883.3.445.16" to represent an alternative representation of the Privacy Consent Directive (e.g.,ODRL, XrML, XACML).
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | <p>[AND]</p> <p>If included, this section shall include the templateId for the Signatures section “2.16.840.1.113883.3.445.18” and a title of “Signatures”.</p> <p>[AND]</p> <p>This section may include the entry/observationMedia for each signature (e.g.,legalAuthenticator, authenticator) or a scanned version of the entire privacy consent directive form including the signatures.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Applicability</b>     | C_SEN_000 AND C_SEN_GEN_002 AND C_SEN_GEN_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Initial condition</b> | The simulated HFS receiver has a webservice enabled with a consent management service. The HFS sender under test has a CDA ready to be sent to the respective service according to its needs.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The HFS sender under test sends a "Provide and Register Document Set-b Request" message containing a CDA referenced in its body</li> <li>2. Check the following elements of the Clinical Document sent by the HFS sender under test: <ol style="list-style-type: none"> <li>a. A templateId = "2.16.840.1.113883.10.20.3"</li> <li>b. Another templateId = "2.16.840.1.113883.3.445.1"</li> <li>c. code attribute of the confidentialityCode element is present and equal to "R".</li> <li>d. codeSystem attribute of the confidentialityCode element is present and equal to 2.16.840.1.113883.5.25.</li> <li>e. If present, codeSystemName of the confidentialityCode element is present and equal to "Confidentiality".</li> <li>f. If present, displayName attribute of the confidentialityCode element is equal to "Restricted".</li> <li>g. recordTarget element is present</li> <li>h. author element: <ul style="list-style-type: none"> <li>o /templateId = "2.16.840.1.113883.3.445.2"</li> <li>o /functionCode may be present</li> </ul> </li> <li>i. intendedRecipient element: the Privacy Consent Directive recipient may be the same person/entity as the intended recipient</li> <li>j. legalAuthenticator element may be either the client or their Substitute Decision Maker and if necessary, the Signatures section may provide the signature associated with the consenter's signature</li> <li>k. authenticator element may be present</li> <li>l. documentationOf/serviceEvent/ element with a templateId of "2.16.840.1.113883.3.445.3" may be present and within this element: <ul style="list-style-type: none"> <li>o id element may be present</li> <li>o effectiveTime element may be present</li> <li>o effectiveTime/low/@value element may be present</li> <li>o effectiveTime/high/@value element may be present</li> <li>o code/@code attribute is present</li> <li>o code/@codeSystem attribute is present</li> <li>o code/@codeSystemName attribute may be present</li> </ul> </li> <li>m. relatedDocument element may be present</li> <li>n. component/structuredBody element is present and within this element: <ul style="list-style-type: none"> <li>o component/section with templateId = "2.16.840.1.113883.3.445.17" is present</li> <li>o component/section/title = Privacy Consent Directive Details</li> </ul> </li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>○ component/section/entry is present</li> <li>○ component/section/entry/templateId = "2.16.840.1.113883.3.445.4"</li> <li>○ component/section/entry/@typeCode = "COMP"</li> <li>○ component/section/entry/act/templateId = "2.16.840.1.113883.3.445.5"</li> <li>○ component/section/entry/act/@moodCode = "DEF"</li> <li>○ component/section/entry/act/code is present</li> <li>○ component/section/entry/act/informant/@typeCode = 'CST'</li> <li>○ one or more component/section/entry/act/participant should be present</li> <li>○ one or more component/section/entry/act/participant/@typeCode = 'IRCP' and component/section/entry/act/participant/templateId = "2.16.840.1.113883.3.445.7" should be present</li> <li>○ component/section/entry/act/participant/participantRole/code/@codeSystem = "2.16.840.1.113883.11.19682" may be present</li> <li>○ component/section/entry/act/participant/participantRole should include a playingEntity element</li> <li>○ component/section/entry/act/entryRelationship may be present with a templateId = "2.16.840.1.113883.3.445.8" and if it is present: <ul style="list-style-type: none"> <li>- /act element is present with classCode = "ACT" and moodCode = "DEF"</li> <li>- /act/@negationId with a value of "false" or "true" should be present</li> <li>- /act/code/@codeSystem = "2.16.840.1.113883.5.4" is present</li> </ul> </li> <li>○ component/section/entry/act/entryRelationship may be present with a templateId = "2.16.840.1.113883.3.445.9" and if it is present: <ul style="list-style-type: none"> <li>- it should include one or more /organizer/component/observation/@moodCode = 'DEF' with a templateId = "2.16.840.1.113883.3.445.10"</li> <li>- /organizer/component/observation should include a code element</li> <li>- /organizer/component/observation may include a precondition/@typeCode = "PRCN" element with a templateId = "2.16.840.1.113883.3.445.11"</li> <li>- /organizer/component/observation may include a precondition/@typeCode = "PRCN" element with a templateId = "2.16.840.1.113883.3.445.12"</li> </ul> </li> <li>○ component/section/entry/act/entryRelationship may be present with a templateId = "2.16.840.1.113883.3.445.13" and if it is present: <ul style="list-style-type: none"> <li>- /act/code is present</li> <li>- /act/precondition may be present with templateId = "2.16.840.1.113883.3.445.14" and @typeCode = "PRCN"</li> <li>- /act/precondition/criterion/[@classCode = "OBS"]/code should be present</li> </ul> </li> <li>○ component/section/entry/act/entryRelationship may be present with a templateId = "2.16.840.1.113883.3.445.15" and if it is present: <ul style="list-style-type: none"> <li>- /observationMedia/@classCode = "OBS" should be present</li> </ul> </li> <li>○ component/section/entry/act/entryRelationship may be present with a templateId = "2.16.840.1.113883.3.445.16"</li> <li>○ component/section with templateId = "2.16.840.1.113883.3.445.18" and a title of "Signatures" may be present, and if present this section may include the entry/observationMedia for each signature</li> </ul> |
+| <b>Pass/Fail criteria</b> | All steps are as specified within the test procedure above.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+# 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*.  
+<https://docbox.etsi.org/MTS/MTS/10-PromotionalMaterial/MBS-20111118/Referenced%20Documents/Drafting%20Rules.pdf>
+- [b-HFSR PICS & PIXIT] Services HFS Receiver DG2016 PICS and PIXIT excel sheet v1.7  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-HFSS PICS & PIXIT] Services HFS Sender DG2016 PICS and PIXIT excel sheet v1.7  
+<http://handle.itu.int/11.1002/2000/12067>
+
+
+
+
+
+# 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg b/marked/H/T-REC-H.830.8-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ca0dce65df64f4fb10a81b8f87284f793e4b1d3d
--- /dev/null
+++ b/marked/H/T-REC-H.830.8-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.9-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.830.9-201704-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..3090365fb7d0af3c17451f3f7e9d151570468981
--- /dev/null
+++ b/marked/H/T-REC-H.830.9-201704-I_PDF-E/raw.md
@@ -0,0 +1,497 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.830.9**
+
+(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 9: hData  
+Observation Upload: Health & Fitness Service  
+sender**
+
+Recommendation ITU-T H.830.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.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        |
+| <b>Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN)</b> | <b>H.820–H.859</b> |
+| 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.9
+
+## Conformance of ITU-T H.810 personal health system: Services interface Part 9: hData Observation Upload: Health & Fitness Service sender
+
+## Summary
+
+Recommendation ITU-T H.830.9 provides a test suite structure (TSS) and the test purposes (TP) for hData Observation Upload 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.9 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Services Interface; Part 9: hData Observation Upload: HFS Sender (Version 1.2, 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.830.9  | 2015-11-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/12660">11.1002/1000/12660</a> |
+| 2.0     | ITU-T H.830.9  | 2016-07-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12929">11.1002/1000/12929</a> |
+| 3.0     | ITU-T H.830.9  | 2017-04-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/13212">11.1002/1000/13212</a> |
+
+## Keywords
+
+Conformance testing, Continua Design Guidelines, e-health, ITU-T H.810, personal connected health devices, hData Observation Upload, Health & Fitness Service sender, Services interface.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.6.1: General (GEN).....         | 9    |
+| Bibliography.....                              | 10   |
+
+**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 9: hData Observation Upload: HFS Sender (Version 1.2, 2017-03-14), that was developed by the Personal Connected Health Alliance. Observation Upload. 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     | 2015-07-01 | Initial release for Test Tool DG2015 based on the requirements in [b-ITU-T H.810 (2015)]/[b-CDG 2015].                                   |
+| 1.1     | 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.2     | 2017-03-14 | Editorial: added insulin pump and continuous glucose monitor specializations to the TSS list in clause 6.                                |
+
+# Recommendation ITU-T H.830.9
+
+## Conformance of ITU-T H.810 personal health system: Services interface Part 9: hData Observation Upload: Health & Fitness Service sender
+
+# 1 Scope
+
+The scope of this Recommendation<sup>1</sup> is to provide 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 9.
+
+- 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.811] Recommendation ITU-T H.811 (2016), *Interoperability design guidelines for personal health systems: Personal health devices interface*.
+
+---
+
+<sup>1</sup> 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]   | Recommendation ITU-T H.812 (2016), <i>Interoperability design guidelines for personal health systems: Services interface: Common certified capability class.</i>                             |
+| [ITU-T H.812.1] | Recommendation ITU-T H.812.1 (2016), <i>Interoperability design guidelines for personal health systems: Services interface: Observation upload certified capability class.</i>               |
+| [ITU-T H.812.2] | Recommendation ITU-T H.812.2 (2016), <i>Interoperability design guidelines for personal health systems: Services interface: Questionnaires certified capability class.</i>                   |
+| [ITU-T H.812.3] | Recommendation ITU-T H.812.3 (2016), <i>Interoperability design guidelines for personal health systems: Services interface: Capability exchange certified capability class.</i>              |
+| [ITU-T H.812.4] | Recommendation ITU-T H.812.4 (2016), <i>Interoperability design guidelines for personal health systems: Services interface: Authenticated persistent session certified capability class.</i> |
+| [ITU-T H.813]   | Recommendation ITU-T H.813 (2016), <i>Interoperability design guidelines for personal health systems: Healthcare information system interface.</i>                                           |
+| [IETF RFC 6749] | IETF RFC 6749 (2012), <i>The OAuth 2.0 Authorization Framework.</i> <a href="http://tools.ietf.org/html/rfc6749">http://tools.ietf.org/html/rfc6749</a>                                      |
+| [IETF RFC 6750] | IETF RFC 6750 (2012), <i>The OAuth 2.0 Authorization Framework: Bearer Token Usage.</i> <a href="http://tools.ietf.org/html/rfc6750">http://tools.ietf.org/html/rfc6750</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:
+
+|      |                                     |
+|------|-------------------------------------|
+| ATNA | Audit Trail and Node Authentication |
+| AHD  | Application Hosting Device          |
+| CDA  | Clinical Document Architecture      |
+| 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                            |
+| 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  |
+| SABTE | Sleep Apnoea Breathing Therapy Equipment       |
+| SCR   | Static Conformance Review                      |
+| SOAP  | Simple Object Access Protocol                  |
+| TCRL  | Test Case Reference List                       |
+| TCWG  | Test and Certification Working Group           |
+| TP    | Test Purpose                                   |
+| TLS   | Transport Level Security                       |
+| TSS   | Test Suite Structure                           |
+| USB   | Universal Serial Bus                           |
+| URI   | Uniform Resource Identifier                    |
+| WAN   | Wide Area Network                              |
+| WDM   | Windows Driver Model                           |
+| WS    | Web Service                                    |
+| WSI   | Web Services Interoperability                  |
+| WSDL  | Web Service Description Language               |
+| XDR   | Cross-Enterprise Document Reliable Interchange |
+| 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 subgroup 1.6.1 (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 <http://handle.itu.int/11.1002/2000/12067>.
+
+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>/<DUT>/<GR>/<SGR>/<XX> – <NNN>). Is specified according to the naming convention defined below:
+  - Each test purpose identifier is introduced by the prefix "TP".
+  - <TT>: This is the test tool that will be used in the test case.
+    - HFS: Health & Fitness Services Interface
+  - <DUT>: This is the device under test.
+    - SEN: HFS sender
+    - REC: HFS receiver
+  - <GR>: This identifies a group of test cases.
+  - <SGR>: This identifies a subgroup of test cases.
+  - <XX>: This identifies the type of testing.
+    - BV: Valid behaviour test
+    - BI: Invalid behaviour test
+  - <NNN>: 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 protocol implementation conformance statement (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 device under test (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.6.1: General (GEN)
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                 |             |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------|
+| <b>TP Id</b>              | TP/HFS/SEN/HDATA/GEN/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                 |             |
+| <b>TP label</b>           | hData Observation Upload. HFS Sender Application                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                 |             |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ITU-T H.812]   |             |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | RESTSec 3;M     | RESTSec 4;M |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | CommonReq 5;M   |             |
+|                           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ITU-T H.812.1] |             |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | hData 2;M       | hData 4;M   |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>SUT uses hData observation upload to send a PCD-01 message using TLS 1.1 and Oauth v2.0 bearer token.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                 |             |
+| <b>Applicability</b>      | C_SEN_000 AND C_SEN_GEN_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                 |             |
+| <b>Other PICS</b>         | C_SEN_GEN_005                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                 |             |
+| <b>Initial condition</b>  | <p>Simulated HFS receiver has an hData WebService that requires TLS 1.1 and Oauth v2.0 authorization token enabled and ready to receive a PCD-01 message. Simulated HFS receiver also provides an Oauth v2.0 token for authorization using resource owner password credentials grant type that requires TLS 1.1.</p>                                                                                                                                                                                                                                                                                                                                       |                 |             |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1 HFS application under test using hData observation upload has a PCD-01 message ready to be sent.</li> <li>2 HFS application uses provided client_id, client_secret, username and password parameters to obtain an Oauth v2.0 bearer token from the test tool using resource owner password credentials grant type and TLS 1.1 security.</li> <li>3 HFS application uses the authorization request header field method as defined in Section 2.1 of RFC6750 [IETF RFC 6749] to send the obtained bearer token with the PCD-01 message to the test tool according to RFC6750 and using TLS 1.1 security.</li> </ol> |                 |             |
+| <b>Pass/fail criteria</b> | <ul style="list-style-type: none"> <li>• HFS application under test supports capability exchange as specified in [ITU-T H.812.3].</li> <li>• Observation upload enabled HFS application uses HTTP POST with the provided URL for uploading the PCD-01 payload.</li> <li>• HFS application under test uses the provided "bearer" token according to RFC6750 to request access to upload an observation to the Simulated HFS Device [IETF RFC 6750].</li> <li>• HFS application uses TLS 1.1 and Oauth v2.0 bearer token using authorization request header field method to send a PCD-01 message to the test tool.</li> </ul>                               |                 |             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                 |             |
+
+# 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.  
+<https://docbox.etsi.org/MTS/MTS/10-PromotionalMaterial/MBS-20111118/Referenced%20Documents/Drafting%20Rules.pdf>
+- [b-HFSR PICS & PIXIT] Services HFS Receiver DG2016 PICS and PIXIT excel sheet v1.7.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-HFSS PICS & PIXIT] Services HFS Sender DG2016 PICS and PIXIT excel sheet v1.7.  
+<http://handle.itu.int/11.1002/2000/12067>
+
+
+
+# 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg b/marked/H/T-REC-H.840-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8bcda2c01451dbc3cddbdce7f60f1edcb3cde5e9
--- /dev/null
+++ b/marked/H/T-REC-H.840-201704-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.841-202008-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.841-202008-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..50a5b6d379457154dc1f5f5c61a52b1e6e6acc2a
--- /dev/null
+++ b/marked/H/T-REC-H.841-202008-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fbd21ce6fadf05bb370f48d3a8ed9bd1cfb65ea818dd42ffd1bdb92a88aa4d7d
+size 3707
diff --git a/marked/H/T-REC-H.841-202008-I_PDF-E/raw.md b/marked/H/T-REC-H.841-202008-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..dbee79a28baf4f2394920dece24429f4c266c9c4
--- /dev/null
+++ b/marked/H/T-REC-H.841-202008-I_PDF-E/raw.md
@@ -0,0 +1,4602 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.841**
+
+(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 1: Optimized Exchange Protocol:  
+Personal Health Device**
+
+Recommendation ITU-T H.841
+
+# 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        |
+| <b>Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN)</b> | <b>H.820–H.859</b> |
+| 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.841
+
+## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 1: Optimized Exchange Protocol: Personal Health Device
+
+## Summary
+
+Recommendation ITU-T H.841 provides a test suite structure (TSS) and the test purposes (TP) for personal health devices using the IEEE 11073-20601 optimized exchange protocol 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.841 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 1: Optimized Exchange Protocol. Personal Health Device (Version 1.11, 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.841    | 2015-01-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/12258">11.1002/1000/12258</a> |
+| 2.0     | ITU-T H.841    | 2016-07-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12934">11.1002/1000/12934</a> |
+| 3.0     | ITU-T H.841    | 2017-04-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/13215">11.1002/1000/13215</a> |
+| 4.0     | ITU-T H.841    | 2018-08-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/13678">11.1002/1000/13678</a> |
+| 5.0     | ITU-T H.841    | 2020-08-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/14344">11.1002/1000/14344</a> |
+
+## Keywords
+
+Conformance testing, Continua Design Guidelines, e-health, ITU-T H.810, IEEE 11073-20601 optimized exchange protocol, Personal Health Devices Interface, personal area network, personal connected health devices, Personal Health Devices interface, touch area network.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 (TSS) .....                          | 5   |
+| 7       | Electronic attachment .....                               | 7   |
+| Annex A | Test purposes .....                                       | 8   |
+| A.1     | TP definition conventions.....                            | 8   |
+| A.2     | Subgroup 1.2.1 – PHD domain information model (DIM) ..... | 9   |
+| A.3     | Subgroup 1.2.2 – PHD service model (SER) .....            | 97  |
+| A.4     | Subgroup 1.2.3 – PHD communication model (COM).....       | 107 |
+|         | Bibliography.....                                         | 167 |
+
+**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 1: Optimized Exchange Protocol. Personal Health Device (Version 1.11, 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.4     | 2012-10-05 | Initial release for Test Tool DG2011. This uses "TSS&TP_1.5_PAN-LAN_PART_1_v1.3.doc" as a baseline and adds new features included in [b-CDG 2011]: <ul style="list-style-type: none"> <li>• Person ID and Errata</li> </ul>                                                                                                                                         |
+| 1.5     | 2013-05-24 | Initial release for Test Tool DG2012. This uses "TSS&TP_DG2011_PAN-LAN_PART_1_v1.4.doc" as a baseline and adds new features included in [b-CDG 2012]: <ul style="list-style-type: none"> <li>• Adds glucose meter</li> <li>• Adds body composition analyser device specialization</li> <li>• Adds basic electrocardiograph device specialization</li> </ul>         |
+| 1.6     | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_PAN-LAN_PART_1_v1.5.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]: <ul style="list-style-type: none"> <li>• Adds glucose meter BLE</li> <li>• Adds BLE SSP support</li> <li>• Adds NFC new transport</li> <li>• Adds INR device specialization</li> </ul> |
+| 1.7     | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_PLT_PART_1_v1.6.doc" as a baseline and adds new features included in Documentation Enhancements: <ul style="list-style-type: none"> <li>• "Other PICS" row added</li> </ul>                                                                                               |
+| 1.8     | 2015-07-01 | Initial release for Test Tool DG2015. It uses "TSS&TP_DG2013_PLT_PART_1_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_1_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_1_v1.9.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2016)]/[b-CDG 2016]                                                                                                                                                                                               |
+| 1.11    | 2017-03-14 | Updates the baseline in "TSS&TP_DG2016_PHD_PART_1_v1.10.doc" as part of the Maintenance 2016 activity: <ul style="list-style-type: none"> <li>• Updates the applicability for TP/PLT/PHD/OPX/COM/BV-054_A</li> </ul>                                                                                                                                                |
+| 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:2018)<br>Updates related to the changes included in the glucose meter device specialization (ISO/IEEE 11073-10417:2017)                                                                                                         |
+| 1.13    | 2020-06-02 | Updates related to the inclusion of the value "7946" according to H.812.1 in [b-CDG 2017], corresponding to "MDC_TIME_SYNC_EBWW", and according to Bugzilla 1164 and 1165.                                                                                                                                                                                          |
+
+# Recommendation ITU-T H.841
+
+## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 1: Optimized Exchange Protocol: Personal Health Device
+
+## 1 Scope
+
+The scope of this Recommendation<sup>1</sup> 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 1.
+
+- **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
+
+---
+
+<sup>1</sup> 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 Annex A.
+
+- Part 8: Continua Design Guidelines. Personal Health Gateway BLE
+- 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*.
+
+[ITU-T H.811] Recommendation ITU-T H.811 (2017), *Personal Health Devices Interface design guidelines*.
+
+[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-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.  
+<https://www.iso.org/standard/66717.html> with  
+<https://www.iso.org/standard/71886.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                            |
+| 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 |
+| 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                                  |
+| 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         |
+
+**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 Personal Health Devices interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroups 1.2.1, 1.2.2 and 1.2.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)
+- 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 <http://handle.itu.int/11.1002/2000/12067>. 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/<TT>/<DUT>/<GR>/<SGR>/<XX> – <NNN>). It is specified according to the naming convention defined below:
+  - Each test purpose identifier is introduced by the prefix "TP".
+  - <TT>: 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)
+  - <DUT>: This is the device under test:
+    - PHD: Personal Health Device
+    - PHG: Personal Health Gateway
+  - <GR>: This identifies a group of test cases.
+  - <SGR>: This identifies a subgroup of test cases.
+  - <XX>: This identifies the type of testing:
+    - BV: Valid behaviour test
+    - BI: Invalid behaviour test
+  - <NNN>: 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.2.1 – PHD domain information model (DIM)
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                    |                     |
+|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------|---------------------|
+| <b>TP Id</b>        | TP/PLT/PHD/OXP/DIM/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                    |                     |
+| <b>TP label</b>     | MDS Object: Mandatory, Conditional and Optional Attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                    |                     |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                    |                     |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MDSClass 1; M                                                 | MDSClass 2; M      | MDSClassAttr 2; M   |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MDSClassAttr 3; C                                             | MDSClassAttr 4; M  | MDSClassAttr 5; M   |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MDSClassAttr 6; M                                             | MDSClassAttr 7; C  | MDSClassAttr 8; O   |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MDSClassAttr 9; C                                             | MDSClassAttr 10; C | MDSClassAttr 11; C  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MDSClassAttr 12; C                                            | MDSClassAttr 13; C | MDSClassAttr 14; O  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MDSClassAttr 15; O                                            | MDSClassAttr 16; O | MDSClassAttr 17; O  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MDSClassAttr 18; C                                            | MDSClassAttr 19; O | MDSService 1; M     |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MDSService 4; M                                               | OperNormProc 2; M  | OperNormProc 3; M   |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | ConfNormalProc 21; M                                          | CommonCharac 3; M  | ConfNormalProc 1; M |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | OperNormProc 6; M                                             | MDSMethod 7; O     | ConfEventRep 28; M  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | ConfEventRep 33; O                                            | ConfEventRep 34; M | MDSMethod 6; M      |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | BaseTimOffset3; M                                             |                    |                     |
+|                     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [b-ITU-T H.810 (2015)]                                        |                    |                     |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | Regulatory 4; M                                               | Regulatory 5; O    |                     |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | multi_func_LAN 1; M                                           |                    |                     |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | General 2; M                                                  |                    |                     |
+| <b>Test purpose</b> | <p>Check that:</p> <p>The Personal Health Device (PHD) supports a Get command that requests all attributes</p> <p>[AND]</p> <p>The PHD reports its MDS object attributes to the Personal Health Gateway (PHG) using a Data message with the “Remote Operation Response   Get” response.</p> <p>[AND]</p> <p>MDS object contains all mandatory attributes, conditional attributes as required by their conditions and it may contain optional attributes</p> <p>[AND]</p> <p>The total size of the response does not exceed the maximum APDU size established by the specialization</p> <p>[AND]</p> <p>MDS object attributes are static /dynamic or observational.</p> <p>[AND]</p> <p>The handle is entered in the obj-handle field and it is not included in the attribute ID list of the request or in the attribute list of the response.</p> <p>[AND]</p> <p>The MDS object is not considered part of the configuration.</p> <p>[AND]</p> |                                                               |                    |                     |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | <p>Changes to any non-static attributes values on PM-stores or the MDS may be reported to the PHG in event reports at the discretion of the PHD</p> <p>[AND]</p> <p>A profile is expected to be identified by a name and a nomenclature value</p> <p>[AND]</p> <p>The PHD shall not include the Base Offset Time in any Continua configurations except for basic electrocardiograph (ECG), insulin pump (IP), continuous glucose monitor (CGM) and power status monitor (PSM) device specializations.</p> <p>[AND]</p> <p>If the base time (seconds field) is aligned with UTC (with an accuracy appropriate to the application), then this shall be designated by setting the mds-time-bo-time-utc-aligned bit in the Mds-Time-Info attribute.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Applicability</b>     | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Other PICS</b>        | C_AG_OXP_006, C_AG_OXP_007, C_AG_OXP_008, C_AG_OXP_009, C_AG_OXP_010, C_AG_OXP_011, C_AG_OXP_014, C_AG_OXP_015, C_AG_OXP_041, C_AG_OXP_071, C_AG_OXP_120, C_AG_OXP_188                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the MDS object and its attributes are not present in the Configuration Event Report.</li> <li>5. The simulated PHG issues "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. Record the invoke-id of the message sent.</li> <li>6. 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:</li> </ol> <p>Verify that the invoke-id is mirrored from the Get request.</p> <p>Verify that the DataApdu contains the SEQUENCE GetResultSimple (0x02 0x03)</p> <ol style="list-style-type: none"> <li>a. Verify that the GetResultSimple.obj-handle = 0x00 0x00</li> <li>b. The GetResultSimple contains an AttributeList: <ul style="list-style-type: none"> <li><input type="checkbox"/> AttributeList.count = number of implemented attributes that are included in the GET response. (must be greater than 3)</li> <li><input type="checkbox"/> AttributeList.length = the length of the remainder of the APDU</li> </ul> </li> </ol> <p>Mandatory Attributes</p> <ol style="list-style-type: none"> <li>a. Mandatory attribute HANDLE shall not be present.</li> <li>b. Mandatory attribute System-Model <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_MODEL (0x09 0x28)</li> <li><input type="checkbox"/> attribute-value.length = 0xXX 0xXX</li> <li><input type="checkbox"/> attribute-value = SystemModel</li> <li><input type="checkbox"/> SystemModel.manufacturer = OCTET STRING</li> <li><input type="checkbox"/> length = 0xXX 0xXX, where X is even and equal to the length of the value</li> <li><input type="checkbox"/> value = &lt;Check with PIXITS&gt;</li> <li><input type="checkbox"/> SystemModel.model-number = OCTET STRING</li> <li><input type="checkbox"/> length = 0xXX 0xXX, where X is even and equal to the length of the value</li> <li><input type="checkbox"/> value = &lt;Check with PIXITS&gt;</li> </ul> </li> <li>c. Mandatory attribute System-Id <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SYS_ID (0x09 0x84)</li> </ul> </li> </ol> |
+
+- attribute-type = OCTET STRING
+- attribute-value.length = 10 bytes
+- attribute-value = OCTET STRING(Size(8))
+- size = 0x00 0x08
+- value = <Check with PIXITS>
+
+#### d. Mandatory attribute Dev-Configuration-Id
+
+- attribute-id = MDC\_ATTR\_DEV\_CONFIG\_ID (0x0A 0x44)
+- attribute-type = ConfigId
+- attribute-value.length = 2 bytes
+- attribute-value = <between 0x00 0x01 and 0x7F 0xFF>
+
+##### Conditional and Optional Attributes
+
+#### e. One and only one of [System-Type-Spec\_List] or [System-Type] shall be present.
+
+#### f. IF System-Type attribute is present:
+
+- attribute-id = MDC\_ATTR\_SYS\_TYPE (0x09 0x86)
+- attribute-type = TYPE
+- attribute-value.length = 4 bytes
+- attribute-value = One of the supported specializations:
+  - MDC\_DEV\_SPEC\_PROFILE\_PULSE\_OXIM (0x10 0x04)
+  - MDC\_DEV\_SPEC\_PROFILE\_BP (0x10 0x06)
+  - MDC\_DEV\_SPEC\_PROFILE\_TEMP (0x10 0x07)
+  - MDC\_DEV\_SPEC\_PROFILE\_SCALE (0x10 0x0F)
+  - MDC\_DEV\_SPEC\_PROFILE\_GLUCOSE (0x10 0x11)
+  - MDC\_DEV\_SPEC\_PROFILE\_HF\_CARDIO (0x10 0x29)
+  - MDC\_DEV\_SPEC\_PROFILE\_HF\_STRENGTH (0x10 0x30)
+  - MDC\_DEV\_SPEC\_PROFILE\_AI\_ACTIVITY\_HUB (0x10 0x47)
+  - MDC\_DEV\_SPEC\_PROFILE\_AI\_MED\_MINDER (0x10 0x48)
+  - MDC\_DEV\_SPEC\_PROFILE\_PEAK\_FLOW (0x10 0x15)
+  - MDC\_DEV\_SPEC\_PROFILE\_BCA (0x10 0x14)
+  - MDC\_DEV\_SPEC\_PROFILE\_ECG (0x10 0x06)
+  - MDC\_DEV\_SPEC\_PROFILE\_COAG (0x10 0x12)
+  - MDC\_DEV\_SPEC\_PROFILE\_SABTE(0x10 0x19)
+  - MDC\_DEV\_SPEC\_PROFILE\_INSULIN\_PUMP (0x10 0x13)
+  - MDC\_DEV\_SPEC\_PROFILE\_CGM (0x10 0x1A)
+  - MDC\_DEV\_SPEC\_PROFILE\_PSM (0x10 0x1C)
+
+#### g. IF System-Type-Spec-List attribute is present
+
+- attribute-id = MDC\_ATTR\_SYS\_TYPE\_SPEC\_LIST (0x0A 0x5A)
+- attribute-type = TypeVerList
+- attribute-value.count = N (record for next step)
+- attribute-value.length = N\*4 bytes
+- attribute-value = N of the following supported specializations:
+  - MDC\_DEV\_SPEC\_PROFILE\_PULSE\_OXIM (0x10 0x04)
+  - MDC\_DEV\_SPEC\_PROFILE\_BP (0x10 0x06)
+  - MDC\_DEV\_SPEC\_PROFILE\_TEMP (0x10 0x07)
+  - MDC\_DEV\_SPEC\_PROFILE\_SCALE (0x10 0x0F)
+
+- MDC\_DEV\_SPEC\_PROFILE\_GLUCOSE (0x10 0x11)
+- MDC\_DEV\_SPEC\_PROFILE\_HF\_CARDIO (0x10 0x29)
+- MDC\_DEV\_SPEC\_PROFILE\_HF\_STRENGTH (0x10 0x30)
+- MDC\_DEV\_SPEC\_PROFILE\_AI\_ACTIVITY\_HUB (0x10 0x47)
+- MDC\_DEV\_SPEC\_PROFILE\_AI\_MED\_MINDER (0x10 0x48)
+- MDC\_DEV\_SPEC\_PROFILE\_PEAK\_FLOW (0x10 0x15)
+- MDC\_DEV\_SPEC\_PROFILE\_BCA (0x10 0x14)
+- MDC\_DEV\_SPEC\_PROFILE\_ECG (0x10 0x06)
+- MDC\_DEV\_SPEC\_PROFILE\_COAG (0x10 0x12)
+- MDC\_DEV\_SPEC\_PROFILE\_SABTE(0x10 0x19)
+- MDC\_DEV\_SPEC\_PROFILE\_INSULIN\_PUMP (0x10 0x13)
+- MDC\_DEV\_SPEC\_PROFILE\_CGM (0x10 0x1A)
+- MDC\_DEV\_SPEC\_PROFILE\_PSM (0x10 0x1C)
+- Profiles for cardiovascular fitness and monitor specialization: If the PHD supports Step Counter profile THEN the PHD shall support Cardiovascular specialization
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_STEP\_COUNTER (0x10 0x68)
+- Profiles for activity hub specialization: If the PHD supports any of the profiles defined for Activity Hub THEN the PHD shall support Activity Hub specialization:
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_FALL\_SENSOR (0x10 0x75)
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_PERS\_SENSOR (0x10 0x76)
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_SMOKE\_SENSOR (0x10 0x77)
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_CO\_SENSOR (0x10 0x78)
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_WATER\_SENSOR (0x10 0x79)
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_GAS\_SENSOR (0x10 0x7A)
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_MOTION\_SENSOR (0x10 0x7B)
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_PROPEXIT\_SENSOR (0x10 0x7C)
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_ENURESIS\_SENSOR (0x10 0x7D)
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_CONTACTCLOSURE\_SENSOR (0x10 0x7E)
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_USAGE\_SENSOR (0x10 0x7F)
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_SWITCH\_SENSOR (0x10 0x80)
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_DOSAGE\_SENSOR (0x10 0x81)
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_TEMP\_SENSOR (0x10 0x82)
+- Profiles for basic electrocardiograph specialization: If the PHD supports any of the profiles defined for basic electrocardiograph THEN the PHD shall support basic electrocardiograph specialization:
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_ECG (0x10 0x8C)
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_HR (0x10 0x8D)
+- Profiles for SABTE specialization: If PHD supports any of the profiles defined for SABTE THEN PHD shall support SABTE specialization,
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_CPAP (0x10 0x94)
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_CPAP\_AUTO (0x10 0x95)
+  - MDC\_DEV\_SUB\_SPEC\_PROFILE\_BPAP (0x10 0x96)
+- Profiles for power status monitor specialization: If the PHD supports any of the
+
+profiles defined for Power Status THEN the PHD shall support power status monitor specialization:
+
+- MDC\_DEV\_SUB\_SPEC\_PROFILE\_EIGHT\_OR\_LESS\_BATTERIES (0x10 0x99)
+- MDC\_DEV\_SUB\_SPEC\_PROFILE\_MORE\_THAN\_EIGHT\_BATTERIES (0x10 0x9A)
+
+#### h. IF Attribute-Value-Map is present
+
+- attribute-id = MDC\_ATTR\_ATTRIBUTE\_VAL\_MAP (0X0A 0X55)
+- attribute-type = AttrValMap
+- attribute-value.count = M
+- attribute-value.length = M\*4 bytes
+- attribute-value = <check that M attributes are defined here>
+
+#### i. IF MDS TimeInfo is present
+
+- attribute-id = MDC\_ATTR\_MDS\_TIME\_INFO (0X0A 0X45)
+- attribute-type = MdsTimeInfo
+- attribute-value.length = 16 bytes
+- attribute-value =
+  - mds-time-cap-state:
+    - IF (C\_AG\_OXP\_006 = TRUE) THEN mds-time-capab-real-time-clock = 1 ELSE mds-time-capab-real-time-clock = 0
+    - IF (C\_AG\_OXP\_008 = TRUE) THEN mds-time-capab-set-clock = 1 ELSE mds-time-capab-set-clock = 0
+    - IF (C\_AG\_OXP\_010 = TRUE) THEN mds-time-capab-relative-time = 1 ELSE mds-time-capab-relative-time = 0
+    - IF (C\_AG\_OXP\_011 = TRUE) THEN mds-time-capab-high-res-relative-time = 1 ELSE mds-time-capab-high-res-relative-time = 0
+    - IF (C\_AG\_OXP\_014 = TRUE) THEN mds-time-capab-bo-time = 1 ELSE mds-time-capab-bo-time = 0
+    - IF (C\_AG\_OXP\_015 = TRUE) THEN mds-time-bo-time-utc-aligned(14) = 1 ELSE mds-time-bo-time-utc-aligned(14) = 0
+    - IF (C\_AG\_OXP\_007 = TRUE AND C\_AG\_OXP\_009 = TRUE) THEN mds-time-capab-sync-abs-time = 1 or 0 ELSE mds-time-capab-sync-abs-time = 0
+    - IF (C\_AG\_OXP\_007= TRUE AND C\_AG\_OXP\_010 = TRUE) THEN mds-time-capab-sync-rel-time = 1 or 0 ELSE mds-time-capab-sync-rel-time = 0
+    - IF (C\_AG\_OXP\_007 = TRUE AND C\_AG\_OXP\_011 = TRUE) THEN mds-time-capab-sync-hi-res-relative-time = 1 or 0 ELSE mds-time-capab-sync-hi-res-relative-time = 0.
+    - IF (C\_AG\_OXP\_007 = TRUE AND C\_AG\_OXP\_014 = TRUE) THEN mds-time-capab-sync-bo-time = 1 or 0 ELSE mds-time-capab-sync-bo-time = 0
+    - IF (C\_AG\_OXP\_007 = TRUE) THEN mds-time-capab-sync-abs-time = 1 OR mds-time-capab-sync-res-time = 1 OR mds-time-capab-sync-hi-res-relative-time = 1 OR mds-time-capab-sync-bo-time = 1
+    - Only one of mds-time-capab-real-time-clock and mds-time-capab-bo-time bits shall be set to 1.
+    - Only one of mds-time-capab-sync-abs-time and mds-time-capab-sync-bo-time bits shall be set to 1.
+    - Only one of mds-time-state-abs-time-synced and mds-time-state-bo-time-synced shall be set to 1
+  - Time-sync-protocol:
+
+- IF (C\_AG\_OXP\_007 = FALSE) THEN time-sync-protocol = MDC\_TIME\_SYNC\_NONE ELSE time-sync-protocol = (MDC\_TIME\_SYNC\_EBWW or MDC\_TIME\_SYNC\_NTPV3 or MDC\_TIME\_SYNC\_NTPV4 or MDC\_TIME\_SYNC\_SNTPV4 or MDC\_TIME\_SYNC\_SNTPV4330 or MDC\_TIME\_SYNC\_BTV1)
+
+##### ▪ Time-sync-accuracy:
+
+- IF (C\_AG\_OXP\_007= FALSE) THEN time-sync-accuracy = 0xFFFFFFFF
+
+##### ▪ Time-resolution-abs-time:
+
+- IF (C\_AG\_OXP\_009 = FALSE AND C\_AG\_OXP\_014 = FALSE) THEN time-resolution-abs-time = 0x0000
+
+###### ▪ Time-resolution-rel-time:
+
+- IF (C\_AG\_OXP\_010= FALSE) THEN time-resolution-rel-time = 0x0000
+
+###### ▪ Time-resolution-high-res-time:
+
+- IF (C\_AG\_OXP\_011 = FALSE) THEN time-resolution-high-res-time = 0x0000
+
+#### j. IF attribute Date-and-Time is present
+
+- attribute-id = MDC\_ATTR\_TIME\_ABS (0x09 0x87)
+- 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
+- If Date-and-Time is present THEN Base-Offset-Time shall not be present.
+
+#### k. IF (C\_AG\_OXP\_014 = TRUE) THEN Base-Offset-Time attribute shall be present ELSE Base-Offset-Time attribute shall not be present
+
+- attribute-id = MDC\_ATTR\_TIME\_BO (0x0A 0x81)
+- attribute-type = BaseOffsetTime
+- attribute-value.length = 8 bytes
+- If Base-Offset-Time is present THEN Date-and-Time shall not be present.
+
+#### l. IF Relative-Time attribute is present
+
+- attribute-id = MDC\_ATTR\_TIME\_REL (0x09 0x8F)
+- attribute-type = RelativeTime
+- attribute-value.length = 4 bytes
+- Verify that C\_AG\_OXP\_010 is set to True
+
+#### m. IF HiRes-Relative-Time attribute is present
+
+- attribute-id = MDC\_ATTR\_TIME\_REL\_HI\_RES (0x09 0xE9)
+- attribute-type = HighResRelativeTime
+- attribute-value.length = 8 bytes
+
+#### n. IF Date-and-Time-Adjustment attribute is present
+
+- attribute-id = MDC\_ATTR\_TIME\_ABS\_ADJUST (0x0A 0X62)
+
+- attribute-type = AbsoluteTimeAdjust
+- attribute-value.length = 6 bytes
+- attribute-value = 0
+- Note: If queried with Get MDS command, this attribute shall be not present or 0.
+- o. IF Production-Specification attribute is present
+  - attribute-id = MDC\_ATTR\_ID\_PROD\_SPECN (0X09 0X2D)
+  - attribute-type = ProductionSpec
+  - attribute-value.length = <even>
+  - attribute-value = <Vendor specific>
+- p. IF Power-Status attribute is present
+  - attribute-id = MDC\_ATTR\_POWER\_STAT (0X09 0X55)
+  - attribute-type = PowerStatus
+  - attribute-value.length = 2 bytes
+  - attribute-value = <not relevant for this test>
+- q. IF Battery-Level attribute is present
+  - attribute-id = MDC\_ATTR\_VAL\_BATT\_CHARGE (0X09 0X9C)
+  - 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"
+- r. IF Remain-Battery-Time attribute is present
+  - attribute-id = MDC\_ATTR\_TIME\_BATT\_REMAIN (0X09 0X88)
+  - 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) or MDC\_DIM\_DAY (0x08 0xE0) >
+- s. IF attribute Reg Cert Data List is present
+  - attribute-id = MDC\_ATTR\_REG\_CERT\_DATA\_LIST (0X0A 0X4B)
+  - attribute-type = RegCertDataList
+  - attribute-value.length = < Variable to be checked>
+  - attribute-value = <Depends on the Authorization body, checked on the Design Guidelines>
+- t. IF Confirm Timeout attribute is present:
+  - attribute-id = MDC\_ATTR\_CONFIRM-TIMEOUT (0x09 0x14)
+  - attribute-type = RelativeTime
+  - attribute-value.length = 4 bytes
+
+Furthermore, if MDS Scan Event Reports are sent by the PHD to report data for MDS object:
+
+7. Wait for a Scan Event Report from the PHD.
+  - a. If the PHD sends Fixed Format Event Report for an MDS object, an Attribute-Value-Map has to be received in the GET response.
+  - b. If the PHD sends Variable Format Event Report for an MDS object, the attributes whose values can be reported will be the attributes defined as dynamic\observational: Attribute-Value-Map, Mds-Time-Info, Date-and-Time or Base-Offset-Time, Relative-Time, HiRes-Relative-Time, Date-and-Time-Adjustment, Power-Status, Battery-Level, Remaining-Battery-Time. Dynamic attribute Confirm-Timeout is recommended not to be present. If Static attributes are present, the value shall remain unchanged. Handle, System-Type, System-Model, System-Id, Dev-
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | Configuration-Id, Production-Specification, Reg-Cert-Data-List, System-Type-Spec-List.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• All checked values are as specified in the test procedure.</li> <li>• 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): <ul style="list-style-type: none"> <li>○ Pulse oximeter → 9216 octets</li> <li>○ Weighing scales → 896 octets</li> <li>○ Glucose meter → 5120 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ Blood pressure → 896 octets</li> <li>○ Thermometer → 896 octets</li> <li>○ Independent activity hub → 5120 octets</li> <li>○ Cardiovascular → 64512 octets or 6624 octets if it supports Step Counter Profile</li> <li>○ Strength → 64512 octets</li> <li>○ Adherence monitor → 1024 octets</li> <li>○ Peak flow → 2030 octets</li> <li>○ Body composition analyser → 7730 octets</li> <li>○ Basic ECG/Simple ECG → 7168 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ Basic ECG/Heart rate → 1280 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ International normalized ratio → 896 octets or 64512 if the PHD supports PM-Store</li> <li>○ Insulin pump → 7168 octets or 5120 if PHD supports PM-Store</li> <li>○ Sleep apnoea breathing therapy equipment → 64512 octets</li> <li>○ Continuous glucose monitor → 896 octets or 5120 if PHD supports PM-Store</li> <li>○ Power status monitor → 940 octets for Simple PSM profile or 1660 if PHD supports Advanced PSM profile</li> </ul> </li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                 |                                                               |                     |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-000_B                                                                                                                                                                                                                                                                                                                     |                                                               |                     |
+| <b>TP label</b>          | MDS Object: Dev-Configuration-Id and System-Id semantic feature                                                                                                                                                                                                                                                                                 |                                                               |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                           | MDSCClassAttr 6; M                                            | ConfNormalProc 2; M |
+| <b>Test purpose</b>      | Check that:<br><br>The Dev-Configuration-Id is consistent between the Configuring state and the Operating state.<br><br>[AND]<br><br>The PHD uses a “Remote Operation Invoke   Confirmed Event Report” data message with an event-type of MDC_NOTI_CONFIG to send its configuration to the PHG                                                  |                                                               |                     |
+| <b>Applicability</b>     | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                    |                                                               |                     |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_291, C_AG_OXP_292, C_AG_OXP_293                                                                                                                                                                                                                                                                            |                                                               |                     |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                             |                                                               |                     |
+| <b>Test procedure</b>    | 1. The simulated PHG receives an association request from the PHD under test with a dev-config-id and a system-id.<br><br>2. The simulated PHG responds with a result = accepted-unknown-config.<br><br>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. |                                                               |                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>4. Record the field config-report-id.</p> <p>5. If the config-report-id is that of the configuration being tested, the simulated PHG responds with a rors-cmip-confirmed-event-report with result "accepted", else the PHG responds with result "unsupported-config".</p> <p>6. Repeat step 5 until the config-report-id is set to the configuration being tested.</p> <p>7. IF C_AG_OXP_293 THEN:</p> <ul style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 THEN it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> <li>d. Operating state is reached.</li> </ul> <p>8. ELSE IF C_AG_OXP_291 OR C_AG_OXP_292 THEN:</p> <ul style="list-style-type: none"> <li>a. Once in Operating state, 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.</li> <li>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.</li> </ul> <p>9. Disconnect the device and connect it again. The simulated PHG receives an association request from the PHD. Check the system-id.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• Dev-Config-Id must be the same in step 1 and step 4</li> <li>• Dev-Config-Id must be the same in step 6 and in step 9</li> <li>• System-Id must be the same in steps 1, 7 or 8, and 9</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                          |                                                                                                                                                                                                                                                                                                    |                                                               |                    |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-000_C                                                                                                                                                                                                                                                                        |                                                               |                    |
+| <b>TP label</b>          | MDS Object: Confirm-Timeout attribute, semantic feature                                                                                                                                                                                                                                            |                                                               |                    |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                    |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                              | MDSClassAttr 19; M                                            | OperErrorCond 5; M |
+|                          |                                                                                                                                                                                                                                                                                                    | TimeOutVar 1; C                                               | OperErrorCond 6; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If the attribute Confirm-Timeout is supported, then its value matches with the actual timeout value that the PHD uses for the Confirmed Event Report generated from the MDS object.</p> <p>[AND]</p> <p>If the attribute is not present, the PHD shall use the value 3 s</p> |                                                               |                    |
+| <b>Applicability</b>     | (C_AG_OXP_182 OR C_AG_OXP_183 OR C_AG_OXP_184 OR C_AG_OXP_189) AND C_AG_OXP_053 AND C_AG_OXP_000                                                                                                                                                                                                   |                                                               |                    |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                    |                                                               |                    |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                   |                                                               |                    |
+| <b>Test procedure</b>    | <p>1. Record the Confirm-Timeout value from the Get MDS operation. If the attribute is not present in the MDS its value shall be TOcer-mds (3s).</p> <p>2. Take a measurement with the PHD under test that will provoke an MDS event report to</p>                                                 |                                                               |                    |
+
+|                           |                                                                                                                                                                                                                                      |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | be sent.<br>3. The PHD sends a "Remote Operation Invoke   Confirmed Event Report".<br>4. The simulated PHG does not respond for at least the time specified in the field Confirm-Timeout or 3 s if Confirm-Timeout is not supported. |
+| <b>Pass/Fail criteria</b> | The PHD must wait the specified time before unassociating.                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                       |                       |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------|-----------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-001_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                       |                       |
+| <b>TP label</b>          | Static Numeric attributes derived from Metrics class and Dynamic Numeric attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                       |                       |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                       |                       |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | MetricClassAttr 1; M                                          | MetricClassAttr 2; M  | MetricClassAttr 3; O  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MetricClassAttr 4; M                                          | MetricClassAttr 5; O  | MetricClassAttr 7; O  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MetricClassAttr 8; O                                          | MetricClassAttr 9; C  | MetricClassAttr 10; O |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MetricClassAttr 11; O                                         | MetricClassAttr 12; C | MetricClassAttr 13; O |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MetricClassAttr 14; O                                         | MetricClassAttr 15; O | MetricClassAttr 16; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MetricClassAttr 17; C                                         | MetricClassAttr 18; C | MetricClassAttr 19; O |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | NumClass 1; M                                                 | NumClass 2; M         | NumClassAttr 1; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | NumClassAttr 2; C                                             | NumClassAttr 3; C     | NumClassAttr 4; C     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | NumClassAttr 5; C                                             | NumClassAttr 6; C     | NumClassAttr 7; C     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | NumClassAttr 8; O                                             | ConfNormalProc 1;M    | ConfEventRep 29; M    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | ConfEventRep 30; M                                            | ConfEventRep 31; C    | ConfEventRep 33; O    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | ConfEventRep 33; O                                            |                       |                       |
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [b-ITU-T H.810 (2015)]                                        |                       |                       |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Communication 6; M                                            | General 2; M          |                       |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Numeric class is derived from the Metric base class. It inherits all mandatory attributes and conditional attributes as required by their conditions and it may import optional attributes.</p> <p>[AND]</p> <p>The nomenclature code to identify the Numeric class is MDC_MOC_VMO_METRIC_NU</p> <p>[AND]</p> <p>Static, dynamic and observational attributes.</p> <p>[AND]</p> <p>Changes to any attribute values of metric and scanner objects shall be reported to the PHG in scan event reports prior to sending event reports that depend on those values (e.g. scan-handle-attr-val-map and a group format event report or unit-code and the observed value).</p> <p>[AND]</p> <p>Continua PAN service components shall not include the Base Offset Time in any Continua configurations except for Basic electrocardiograph (ECG) device specialization.</p> |                                                               |                       |                       |
+| <b>Applicability</b>     | C_AG_OXP_040 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                       |                       |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_041, C_AG_OXP_046, C_AG_OXP_047, C_AG_OXP_182, C_AG_OXP_183, C_AG_OXP_184, C_AG_OXP_189, C_AG_OXP_190, C_AG_OXP_192, C_AG_OXP_193, C_AG_OXP_194, C_AG_OXP_195, C_AG_OXP_196, C_AG_OXP_197, C_AG_OXP_198, C_AG_OXP_199, C_AG_OXP_200, C_AG_OXP_201, C_AG_OXP_202, C_AG_OXP_203, C_AG_OXP_230, C_AG_OXP_231, C_AG_OXP_232, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                       |                       |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                       |                       |
+| <b>Test procedure</b>    | 1. The PHD under test sends and 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. Numeric class attributes must be (ConfigReport -> ConfigObject-> AttributeList):
+  - a. Mandatory attribute Handle shall be present.
+    - attribute-type = HANDLE
+    - attribute-length = 2 bytes
+    - attribute-value = must be unique and non-zero. Actual value may be specified by the Device Specialization.
+  - b. Mandatory attribute Type shall be present in ConfigReport
+    - attribute-id = MDC\_ATTR\_ID\_TYPE (0X09 0X2F)
+    - attribute-type = TYPE
+    - attribute-value = SEQUENCE OF (SIZE 6)
+    - attribute-value = <Not relevant in this test>
+  - c. Mandatory attribute Metric-Spec-Small should be present
+    - attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL
+    - attribute-type = MetricSpecSmall
+    - attribute-value.length = 2 bytes
+    - attribute-value =
+      - IF C\_AG\_OXP\_201=TRUE and C\_AG\_OXP\_041=FALSE THEN mss-avail-stored-data(1)=1(There is at least one object that has mss-avail.stored-data(1)=1)
+      - IF C\_AG\_OXP\_201=TRUE and C\_AG\_OXP\_041=TRUE THEN mss-avail-stored-data(1)=1 or 0
+  - d. Only one attribute of Metric-Id and Metric-Id-List shall be present.
+  - e. If Metric-Id-List attribute is supported, it should be present in ConfigReport
+    - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+    - attribute-type = MetricIdList
+    - attribute-value.length = SEQUENCE OF (SIZE 2)
+    - 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.
+    - IF the PHD supports Metric-Id-List at least for a Numeric object (C\_AG\_OXP\_190 =TRUE) THEN this attribute shall be present at least for one object, ELSE this attribute is not present.
+  - f. IF Metric-Id attribute is supported, it should be present in ConfigReport
+    - attribute-id = MDC\_ATTR\_ID\_PHYSIO
+    - attribute-type = OID-Type
+    - attribute-value.length = 2 bytes
+  - g. IF Attribute-Value-Map is supported, it should be present in ConfigReport
+    - attribute-id = MDC\_ATTR\_ATTRIBUTE\_VAL\_MAP (0X0A 0X5A)
+    - attribute-type = AttrValMap
+    - attribute-count = n (record for next attribute field)
+    - attribute-value.length = n\*4 bytes
+    - attribute-value = <n attributes will be declared, each one will have 4 bytes
+
+composed of:
+
+- attribute-id = 2 bytes (MDC\_ATTR\_\*).
+- Attribute-length = 0x00 0x02: (2 bytes to declare the length of the attribute, but the contents of the attribute in the event report is not these 2 bytes length)
+
+h. IF Supplemental-Types attribute is supported, it shall be present in ConfigReport:
+
+- attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+- attribute-type = SupplementalTypeList
+- attribute-value.length = SEQUENCE OF (SIZE (4) )
+- attribute-value = <Not relevant in this test>
+
+i. IF attribute Metric-Structure-Small is supported, it should be present in ConfigReport:
+
+- 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 (0x00)
+    - ms-struct-compound (0x01)
+    - ms-struct-reserved (0x02)
+    - ms-struct-compound-simple (0x03)
+  - ms-compound-no = one of the following:
+    - IF ms-struct = ms-struct-simple THEN = 0
+    - ELSE = maximum number of components in a compound value
+
+j. IF attribute Metric-Id-Partition is supported, it should be present in ConfigReport
+
+- attribute-id = MDC\_ATTR\_METRIC\_ID\_PART
+- attribute-type = NomPartition
+- attribute-value.length = 2 bytes
+- 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)
+
+- k. IF attribute Unit-Code is supported, it should be present in ConfigReport:
+  - attribute-id = MDC\_ATTR\_UNIT\_CODE
+  - attribute-type = OID-Type
+  - attribute-value.length = 2 bytes
+  - attribute-value = One of MDC\_PART\_DIM (may be defined in the specialization)
+- l. IF attribute Source-Handle-Reference is supported, it should be present in ConfigReport:
+  - attribute-id = MDC\_ATTR\_SOURCE\_HANDLE\_REF
+  - attribute-type = HANDLE
+  - attribute-value.length = 2 bytes
+  - attribute-value = < The value of an existing object's handle >
+- m. IF attribute Label-String is supported, it should be present in ConfigReport:
+  - attribute-id = MDC\_ATTR\_ID\_LABEL\_STRING
+  - attribute-type = OCTET STRING
+  - attribute-value.length =
+  - attribute-value = <Textual representation of attribute Type, Printable ASCII>
+- n. IF attribute Unit-Label-String is supported, it should be present in ConfigReport:
+  - attribute-id = MDC\_ATTR\_UNIT\_LABEL\_STRING
+  - attribute-type = OCTET STRING
+  - attribute-value.length =
+  - attribute-value = <Textual representation of attribute Unit-Code, Printable ASCII>
+- o. IF attribute Accuracy is supported, it shall be present in ConfigReport:
+  - attribute-id = MDC\_ATTR\_NU\_ACCUR\_MSMT
+  - attribute-type = FLOAT-Type
+  - attribute-value.length = 4 bytes
+  - attribute-value = <Not relevant in this test>
+- p. IF attribute Measure-Active-Period is supported, it should be present in ConfigReport:
+  - attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE
+  - attribute-type = FLOAT-Type
+  - attribute-value.length = 4 bytes
+  - attribute-value = <Not relevant in this test>
+- q. Time-stamp attributes (Absolute-Time-Stamp, Base-Offset-Time, Relative-Time-Stamp and HiRes-Time-Stamp), observed values attributes (Simple-Nu-Observed-Value, Basic-Nu-Observed-Value, Nu-Observed-Value, Compound-Simple-Nu-Observed-Value, Compound-Basic-Nu-Observed-Value, Compound-Nu-Observed-Value) and Measurement-Status shall not be present if mss-cat-setting and/or mss-cat-manual bit of the Metric-Spec-Small attribute is set to 0. If any of these bits is set to 1, observational attributes may be present in ConfigReport.
+
+Furthermore if MDS event reports are sent by the PHD, (the PHD sends fixed format value messages to report dynamic data for Numeric Objects or uses variable format event report, C\_AG\_OXP\_182 = TRUE or C\_AG\_OXP\_189 = TRUE):
+
+##### 5. 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.
+6. Take a measurement with the PHD
+  7. Wait for an event report from the PHD
+    - a. One of {Simple-Nu-Observed-Value, Basic-Nu-Observed-Value, Nu-Observed-Value, Compound-Nu-Observed-Value, Compound-Simple-Nu-Observed-Value, Compound-Basic-Nu-Observed-Value} shall be present
+    - b. IF attribute Simple-Nu-Observed-Value is present
+      - attribute-id = MDC\_ATTR\_NU\_VAL\_OBS\_SIMP
+      - attribute-type = SimpleNuObsValue
+      - attribute-value.length = 4 bytes
+      - attribute-value = <Not relevant in this test>
+    - c. IF attribute Basic-Nu-Observed-Value is present
+      - attribute-id = MDC\_ATTR\_NU\_VAL\_OBS\_BASIC
+      - attribute-type = BasicNuObsValue
+      - attribute-value.length = 2 bytes
+      - attribute-value = <Not relevant in this test>
+    - d. IF attribute Nu-Observed-Value is present
+      - attribute-id = MDC\_ATTR\_NU\_VAL\_OBS
+      - attribute-type = NuObsValue
+      - attribute-value.length = 10 bytes
+      - attribute-value = <Not relevant in this test>
+    - e. IF attribute Compound-Simple-Nu-Observed-Value is present
+      - attribute-id = MDC\_ATTR\_NU\_CMPD\_VAL\_OBS\_SIMP
+      - attribute-type = SimpleNuObsValueCmp
+      - attribute-value.length = SEQUENCE OF (SIZE (4))
+      - attribute-value = <Not relevant in this test>
+    - f. IF 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 = <Not relevant in this test>
+    - g. IF attribute Compound-Nu-Observed-Value is present
+      - attribute-id = MDC\_ATTR\_NU\_CMPD\_VAL\_OBS
+      - attribute-type = NuObsValueCmp
+      - attribute-value.length = SEQUENCE OF (SIZE (10))
+      - attribute-value = <Not relevant in this test>
+    - h. IF attribute Measure-Active-Period is present
+      - attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE
+      - attribute-type = FLOAT-Type
+
+- attribute-value.length = 4 bytes
+- attribute-value = <Not relevant in this test>
+- i. IF attribute Absolute-Time-Stamp is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_ABS
+  - attribute-type = AbsoluteTime
+  - attribute-value.length = 8 bytes
+  - attribute-value = <Not relevant in this test>
+    - century =
+    - year ≤ 99
+    - month ≤ 12
+    - day ≤ 31
+    - hour ≤ 24
+    - minute ≤ 60
+    - second ≤ 60
+    - sec-fractions ≤ 100
+  - If an PHD stores data, it shall associate a time stamp with the data.
+  - If an PHD supports Absolute-Time-Stamp, Base-Offset-Time-Stamp attribute shall not be supported.
+- j. IF (C\_AG\_OXP\_014 = TRUE) THEN Attribute Base-Offset-Time-Stamp may be present ELSE it shall not be present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+  - attribute-type = BaseOffsetTime
+  - attribute-value.length = 8 bytes
+  - attribute-value = <Not relevant in this test>
+  - If an PHD stores data, it shall associate a time stamp with the data.
+  - If an PHD supports Base-Offset-Time-Stamp, Absolute-Time-Stamp attribute shall not be supported.
+- k. IF attribute Relative-Time-Stamp is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_REL
+  - attribute-type = RelativeTime
+  - attribute-value.length = 4 bytes
+  - attribute-value = <Not relevant in this test>
+  - If a PHD stores data, it shall associate a time stamp with the data
+- l. IF attribute HiRes-Time-Stamp is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_REL\_HI\_RES
+  - attribute-type = HighResRelativeTime
+  - attribute-value.length = 8 bytes
+  - attribute-value = <Not relevant in this test>
+- m. IF 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>
+- n. Check dynamic attributes that can be present: Metric-Structure-Small, Metric-Id, Metric-Id-List, Metric-Id-Partition, Unit-Code, Source-Handle-Reference, Label-String, Unit-Label-String, Measure-Active-Period
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              | <p>Checking that "IF C_AG_OXP_201=FALSE THEN mss-avail-stored data(1)=0" for MetricSpecSmall attribute has been removed because [ISO/IEEE 11073-20601-2015A] has specified (subsection A.11.3) that "The setting of bits 0 to 5 is primarily informational and shall be set if the condition is true but- a PHG cannot assume that if they are set the behaviour will be observed".</p> <p>According to Device Specialization spec, standard configurations (most of them) state the value for bit mss-avail-stored-data to 1, even if the PHD cannot store measurements.</p> <p>So, if the test procedure checks that if C_AG_OXP_201=FALSE then mss-avail-stored-data = 0 the test case will give a FAIL verdict and it would not be correct according to what [ISO/IEEE 11073-20601-2015A] states in clause A.11.3.</p> |
+
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                       |                       |
+|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------|-----------------------|
+| <b>TP Id</b>         | TP/PLT/PHD/OXP/DIM/BV-001_B                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                       |                       |
+| <b>TP label</b>      | Static Enumerated attributes derived from Metrics class and Dynamic Enumerated attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                       |                       |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                       |                       |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | MetricClassAttr 1; M                                          | MetricClassAttr 2; M  | MetricClassAttr 3; O  |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | MetricClassAttr 4; M                                          | MetricClassAttr 5; O  | MetricClassAttr 7; O  |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | MetricClassAttr 8; O                                          | MetricClassAttr 9; C  | MetricClassAttr 10; O |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | MetricClassAttr 11; O                                         | MetricClassAttr 12; C | MetricClassAttr 13; O |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | MetricClassAttr 14; O                                         | MetricClassAttr 15; O | MetricClassAttr 16; C |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | MetricClassAttr 17; C                                         | MetricClassAttr 18; C | MetricClassAttr 19; O |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | EnumClass 2; M                                                | EnumClass 3; M        | EnumClassAttr 1; M    |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | EnumClassAttr 2; C                                            | EnumClassAttr 3; C    | EnumClassAttr 4; C    |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | EnumClassAttr 5; C                                            | EnumClassAttr 6; C    | EnumClassAttr 7; O    |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ConfNormalProc 1; M                                           | ConfEventRep 29; M    | ConfEventRep 30; M    |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ConfEventRep 31; C                                            | ConfEventRep 33; O    |                       |
+|                      | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [b-ITU-T H.810 (2015)]                                        |                       |                       |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Communication 6; M                                            | General 2; M          |                       |
+| <b>Test purpose</b>  | <p>Check that:</p> <p>Enumerated class is derived from the Metric base class. It inherits all mandatory attributes and conditional attributes as required by their conditions and it may import optional attributes.</p> <p>[AND]</p> <p>The nomenclature code to identify the Enumerated class is MDC_MOC_VMO_METRIC_ENUM.</p> <p>[AND]</p> <p>Static, dynamic and observational attributes.</p> <p>[AND]</p> <p>Changes to any attribute values of metric and scanner objects shall be reported to the PHG in scan event reports prior to sending event reports that depend on those values (e.g. scan-handle-attr-val-map and a group format event report or unit-code and the observed value).</p> <p>[AND]</p> <p>Continua PAN service components shall not include the Base Offset Time in any Continua configurations except for Basic electrocardiograph (ECG) device specialization.</p> |                                                               |                       |                       |
+| <b>Applicability</b> | C_AG_OXP_043 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                       |                       |
+| <b>Other PICS</b>    | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_041, C_AG_OXP_046, C_AG_OXP_047, C_AG_OXP_182, C_AG_OXP_183, C_AG_OXP_184, C_AG_OXP_189, C_AG_OXP_190, C_AG_OXP_192, C_AG_OXP_193, C_AG_OXP_194, C_AG_OXP_195, C_AG_OXP_196, C_AG_OXP_197, C_AG_OXP_198, C_AG_OXP_199, C_AG_OXP_200, C_AG_OXP_201, C_AG_OXP_202, C_AG_OXP_203, C_AG_OXP_230, C_AG_OXP_231, C_AG_OXP_232,                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                       |                       |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Enumeration object attributes must be (ConfigReport -&gt; ConfigObject-&gt; AttributeList): <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle shall not be present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 2 bytes</li> <li><input type="checkbox"/> attribute-value = must be unique and non-zero. Actual value may be specified by the Device Specialization.</li> </ul> </li> <li>b. Mandatory attribute Type shall be present in ConfigReport: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE (0X09 0X2F)</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = SEQUENCE OF (SIZE 6)</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small should be present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Checked in the specializations &gt; <ul style="list-style-type: none"> <li>▪ IF C_AG_OXP_202=TRUE and C_AG_OXP_041=FALSE THEN mss-avail-stored-data(1)=1 (There is at least one object that has mss-avail-stored-data(1) = 1)</li> <li>▪ IF C_AG_OXP_202=TRUE and C_AG_OXP_041=TRUE THEN mss-avail-stored-data(1)=1 or 0</li> </ul> </li> </ul> </li> <li>d. Only one attribute of Metric-Id and Metric-Id-List shall be present.</li> <li>e. IF Metric-Id-List attribute is supported, it should be present in ConfigReport: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIST</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value.length = SEQUENCE OF (SIZE 2)</li> <li><input type="checkbox"/> attribute-value =</li> <li><input type="checkbox"/> 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.</li> </ul> </li> <li>f. IF Metric-Id attribute is supported, it should be present in ConfigReport: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>g. IF Attribute-Value-Map is supported, it should be present in ConfigReport: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP (0X0A 0X55)</li> <li><input type="checkbox"/> attribute-type = AttrValMap</li> <li><input type="checkbox"/> attribute-count = n (record for next attribute field)</li> <li><input type="checkbox"/> attribute-value.length = n*4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;n attributes will be declared, each one will have 4 bytes composed of:</li> </ul> </li> </ol> </li> </ol> |
+
+- attribute-id = 2 bytes (MDC\_ATTR\_\*)
+
+- Attribute-length = 0x00 0x02: (2 bytes to declare the length of the attribute, but the contents of the attribute in the event report is not these 2 bytes length)
+
+h. IF Supplemental-Types attribute is supported, it shall be present in ConfigReport:
+
+- attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+
+- attribute-type = SupplementalTypeList
+
+- attribute-value.length = SEQUENCE OF (SIZE (4) )
+
+- attribute-value = <Not relevant in this test>
+
+i. IF attribute Metric-Structure-Small is supported, it should be present in ConfigReport:
+
+- 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
+
+j. IF attribute Metric-Id-Partition is supported, it should be present in ConfigReport:
+
+- attribute-id = MDC\_ATTR\_METRIC\_ID\_PART
+
+- attribute-type = NomPartition
+
+- attribute-value.length = 2 bytes
+
+- 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)
+
+k. IF attribute Unit-Code is supported, it should be present in ConfigReport:
+
+- attribute-id = MDC\_ATTR\_UNIT\_CODE
+- attribute-type = OID-Type
+- attribute-value.length = 2 bytes
+- attribute-value = One of MDC\_PART\_DIM (may be defined in the specialization)
+- l. IF attribute Source-Handle-Reference is supported, it should be present in ConfigReport:
+  - attribute-id = MDC\_ATTR\_SOURCE\_HANDLE\_REF
+  - attribute-type = HANDLE
+  - attribute-value.length = 2 bytes
+  - attribute-value = < The value of an existing object's handle >
+- m. IF attribute Label-String is supported, it should be present in ConfigReport
+  - attribute-id = MDC\_ATTR\_ID\_LABEL\_STRING
+  - attribute-type = OCTET STRING
+  - attribute-value.length =
+  - attribute-value = <Textual representation of attribute Type, Printable ASCII>
+- n. IF attribute Unit-Label-String is supported, it should be present in ConfigReport:
+  - attribute-id = MDC\_ATTR\_UNIT\_LABEL\_STRING
+  - attribute-type = OCTET STRING
+  - attribute-value.length =
+  - attribute-value = <Textual representation of attribute Unit-Code, Printable ASCII>
+- o. IF attribute Measure-Active-Period is supported, it should be present in ConfigReport:
+  - attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE
+  - attribute-type = FLOAT-Type
+  - attribute-value.length = 4 bytes
+  - attribute-value = <Not relevant for this test>
+- p. IF attribute Enum-Observed-Value-Partition is supported it should be present in ConfigReport:
+  - attribute-id = MDC\_ATTR\_ENUM\_OBS\_VAL\_PART
+  - attribute-type = NomPartition
+  - attribute-value.length = 2 bytes
+  - 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)
+
+- q. Time-stamp attributes (Absolute-Time-Stamp, Base-Offset-Time, Relative-Time-Stamp and HiRes-Time-Stamp), observed values attributes (Enum-Observed-Value-Simple-OID, Enum-Observed-Value-Simple-Bit-Str, Enum-Observed-Value-Simple-Str, Enum-Observed-Value-Basic-Bit-Str, Enum-Observed-Value) and Measurement-Status shall not be present if mss-cat-setting and/or mss-cat-manual bit of the Metric-Spec-Small attribute is set to 0. If any of these bits is set to 1, observational attributes may be present in ConfigReport.
+
+Furthermore if MDS event reports are sent by the PHD (the PHD sends fixed format value messages to report dynamic data for Enumeration Objects or uses variable format event report, C\_AG\_OXP\_183=TRUE or C\_AG\_OXP\_189=TRUE):
+
+##### 5. 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.
+
+##### 6. Take a measurement with the PHD.
+
+##### 7. Wait for an event report from the PHD:
+
+- a. One of Enum-Observed-Value-Simple-OID, Enum-Observed-Value-Simple-Bit-Str, Enum-Observed-Value-Simple-Str, Enum-Observed-Value-Basic-Bit-Str, Enum-Observed-Value shall be present.
+- b. IF attribute Measure-Active-Period is present
+  - attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE
+  - attribute-type = FLOAT-Type
+  - attribute-value.length = 4 bytes
+  - attribute-value = <Not relevant for this test>
+- c. IF attribute Enum-Observed-Value-Simple-OID is present
+  - attribute-id = MDC\_ATTR\_ENUM\_OBS\_VAL\_SIMP\_OID
+  - attribute-type = OID-Type
+  - attribute-value.length = 2 bytes
+  - attribute-value = <Not relevant in this test>
+- d. IF 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 = <Not relevant in this test>
+- e. IF 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 = <Not relevant in this test>
+- f. IF attribute Enum-Observed-Value-Simple-Str is present
+  - attribute-id = MDC\_ATTR\_ENUM\_OBS\_VAL\_SIMP\_STR
+  - attribute-type = EnumPrintableString
+  - attribute-value.length = <Variable>
+  - attribute-value = <ASCII printable>
+- g. IF attribute Enum-Observed-Value is present
+  - attribute-id = MDC\_ATTR\_VAL\_ENUM\_OBS
+  - attribute-type = EnumObsValue
+  - attribute-value.length = <Variable>
+  - attribute-value = <Checked in each specialization>
+- h. IF attribute Enum-Observed-Value-Partition is present
+  - attribute-id = MDC\_ATTR\_ENUM\_OBS\_VAL\_PART
+  - attribute-type = NomPartition
+  - attribute-value.length = 2 bytes
+  - 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)
+- i. IF attribute Absolute-Time-Stamp is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_ABS
+  - attribute-type = AbsoluteTime
+  - attribute-value.length = 8 bytes
+  - attribute-value =
+    - century =
+    - year ≤ 99
+    - month ≤ 12
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>▪ day ≤ 31</li> <li>▪ hour ≤ 24</li> <li>▪ minute ≤ 60</li> <li>▪ second ≤ 60</li> <li>▪ sec-fractions ≤ 100</li> </ul> <ul style="list-style-type: none"> <li><input type="checkbox"/> If an PHD stores data, it shall associate a time stamp with the data (This case will be tested in TP/PLT/PHD/SER/BV-007)</li> <li><input type="checkbox"/> If an PHD supports Absolute-Time-Stamp, Base-Offset-Time-Stamp attribute shall not be supported.</li> </ul> <ul style="list-style-type: none"> <li>j. IF (C_AG_OXP_014 = TRUE) THEN Attribute Base-Offset-Time-Stamp may be present ELSE it shall not be present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> <li><input type="checkbox"/> If a PHD stores data, it shall associate a time stamp with the data.</li> <li><input type="checkbox"/> If a PHD supports Base-Offset-Time-Stamp, Absolute-Time-Stamp attribute shall not be supported.</li> </ul> </li> <li>k. IF attribute Relative-Time-Stamp is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_REL</li> <li><input type="checkbox"/> attribute-type = RelativeTime</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> </li> <li>l. If a PHD stores data, it shall associate a time stamp with the data</li> <li>m. IF attribute HiResRelative-Time-Stamp is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_REL_HI_RES</li> <li><input type="checkbox"/> attribute-type = HighResRelativeTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> </li> <li>n. IF attribute Measurement Status is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;not relevant for this test&gt;</li> </ul> </li> <li>o. Check dynamic attributes that can be present: Metric-Structure-Small, Metric-Id, Metric-Id-List, Metric-Id-Partition, Unit-Code, Source-Handle-Reference, Label-String, Unit-Label-String, Measure-Active-Period</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              | <p>Checking that "IF C_AG_OXP_202=FALSE THEN mss-avail-stored data(1)=0" for MetricSpecSmall attribute has been removed because [ISO/IEEE 11073-20601-2015A] has specified (clause A.11.3) that "The setting of bits 0 to 5 is primarily informational and shall be set if the condition is true but-- a PHG cannot assume that if they are set the behaviour will be observed".</p> <p>According to the Device Specialization spec, standard configurations (most of them) state the value for bit mss-avail-stored-data to 1, even if the PHD cannot store measurements.</p> <p>So if test procedure checks that if C_AG_OXP_202=FALSE then mss-avail-stored-data =0 the test case will give a FAIL verdict, and it would not be correct according to what [ISO/IEEE 11073-20601-2015A] states (clause A.11.3).</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                       |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-001_C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                       |
+| <b>TP label</b>          | Static RealTime-SA attributes derived from Metrics class and Dynamic RealTime-SA attributes.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                       |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                       |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | MetricClassAttr 1; M                                          | MetricClassAttr 2; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MetricClassAttr 4; M                                          | MetricClassAttr 5; O  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MetricClassAttr 8; O                                          | MetricClassAttr 9; C  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MetricClassAttr 11; O                                         | MetricClassAttr 12; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MetricClassAttr 14; O                                         | MetricClassAttr 15; O |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MetricClassAttr 17; C                                         | MetricClassAttr 18; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | ArrayClass 1; M                                               | ArrayClass 2; M       |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | ArrayClassAttr 2; M                                           | ArrayClassAttr 3; M   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | ConfNormalProc 1; M                                           | ConfEventRep 29; M    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | ConfEventRep 31; C                                            | ConfEventRep 33; O    |
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [b-ITU-T H.810 (2015)]                                        |                       |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Communication 6; M                                            | General 2; M          |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>RT-SA class is derived from the Metric base class. It inherits all mandatory attributes and conditional attributes as required by their conditions and it may import optional attributes.</p> <p>[AND]</p> <p>The nomenclature code to identify the RT-SA class is MDC_MOC_VMO_METRIC_SA_RT.</p> <p>[AND]</p> <p>Static, dynamic and observational attributes.</p> <p>[AND]</p> <p>Changes to any attribute values of metric and scanner objects shall be reported to the PHG in scan event reports prior to sending event reports that depend on those values (e.g. scan-handle-attr-val-map and a group format event report or unit-code and the observed value).</p> <p>[AND]</p> <p>Continua PAN service components shall not include the Base Offset Time in any Continua configurations except for Basic electrocardiograph (ECG) device specialization.</p> |                                                               |                       |
+| <b>Applicability</b>     | C_AG_OXP_042 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                       |
+| <b>Other PICS</b>        | C_AG_OXP_009,C_AG_OXP_014, C_AG_OXP_041, C_AG_OXP_046, C_AG_OXP_047, C_AG_OXP_182, C_AG_OXP_183, C_AG_OXP_184, C_AG_OXP_189, C_AG_OXP_190, C_AG_OXP_192, C_AG_OXP_193, C_AG_OXP_194, C_AG_OXP_195, C_AG_OXP_196, C_AG_OXP_197, C_AG_OXP_198, C_AG_OXP_199, C_AG_OXP_200, C_AG_OXP_201, C_AG_OXP_202, C_AG_OXP_203, C_AG_OXP_230, C_AG_OXP_231, C_AG_OXP_232, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                       |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                       |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. RealTime-SA object attributes must be(ConfigReport -&gt; ConfigObject-&gt; AttributeList): <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle shall not be present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = must be unique and non-zero. Actual value may be specified</li> </ul> </li> </ol> </li> </ol>          |                                                               |                       |
+
+by the Device Specialization.
+
+- b. Mandatory attribute Type shall be present in ConfigReport:
+  - attribute-id = MDC\_ATTR\_ID\_TYPE (0X09 0X2F)
+  - attribute-type = TYPE
+  - attribute-value = SEQUENCE OF (SIZE 6)
+  - attribute-value = <Not relevant in this test>
+- c. Mandatory attribute Metric-Spec-Small should be present
+  - attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL
+  - attribute-type = MetricSpecSmall
+  - attribute-value.length = 2 bytes
+  - attribute-value = <Checked in the specializations>
+    - Bit mss-avail-store-data must be set to 0
+- d. Only one attribute of Metric-Id and Metric-Id-List shall be present.
+- e. If Metric-Id-List attribute is supported, it should be present in ConfigReport:
+  - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+  - attribute-type = MetricIdList
+  - attribute-value.length = SEQUENCE OF (SIZE 2)
+  - 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.
+- f. IF Metric-Id attribute is supported, it should be present in ConfigReport:
+  - attribute-id = MDC\_ATTR\_ID\_PHYSIO
+  - attribute-type = OID-Type
+  - attribute-value.length = 2 bytes
+- g. IF Attribute-Value-Map is supported, it should be present in ConfigReport:
+  - attribute-id = MDC\_ATTR\_ATTRIBUTE\_VAL\_MAP (0X0A 0X55)
+  - attribute-type = AttrValMap
+  - attribute-count = n (record for next attribute field)
+  - attribute-value.length = n\*4 bytes
+  - attribute-value = <n attributes will be declared, each one will have 4 bytes composed of:
+    - attribute-id = 2 bytes (MDC\_ATTR\_\*)
+    - Attribute-length = 0x00 0x02: (2 bytes to declare the length of the attribute, but the contents of the attribute in the event report is not these 2 bytes length)
+- h. IF Supplemental-Types attribute is supported, it shall be present in ConfigReport:
+  - attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+  - attribute-type = SupplementalTypeList
+  - attribute-value.length = SEQUENCE OF (SIZE (4) )
+  - attribute-value = <Not relevant in this test>
+- i. IF attribute Metric-Structure-Small is supported, it should be present in ConfigReport:
+  - 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
+
+j. IF attribute Metric-Id-Partition is supported, it should be present in ConfigReport:
+
+attribute-id = MDC\_ATTR\_METRIC\_ID\_PART
+
+attribute-type = NomPartition
+
+attribute-value.length = 2 bytes
+
+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)
+
+k. IF attribute Unit-Code is supported, it should be present in ConfigReport:
+
+attribute-id = MDC\_ATTR\_UNIT\_CODE
+
+attribute-type = OID-Type
+
+attribute-value.length = 2 bytes
+
+attribute-value = One of MDC\_PART\_DIM (may be defined in the specialization)
+
+l. IF attribute Source-Handle-Reference is supported, it should be present in ConfigReport:
+
+attribute-id = MDC\_ATTR\_SOURCE\_HANDLE\_REF
+
+attribute-type = HANDLE
+
+attribute-value.length = 2 bytes
+
+attribute-value = < The value of an existing object's handle >
+
+m. IF attribute Label-String is supported, it should be present in ConfigReport:
+
+attribute-id = MDC\_ATTR\_ID\_LABEL\_STRING
+
+attribute-type = OCTET STRING
+
+- attribute-value.length =
+  - attribute-value = <Textual representation of attribute Type, Printable ASCII>
+- n. IF attribute Unit-Label-String is supported, it should be present in ConfigReport:
+- attribute-id = MDC\_ATTR\_UNIT\_LABEL\_STRING
+  - attribute-type = OCTET STRING
+  - attribute-value.length =
+  - attribute-value = <Textual representation of attribute Unit-Code, Printable ASCII>
+- o. IF attribute Measure-Active-Period is supported, it should be present in ConfigReport:
+- attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE
+  - attribute-type = FLOAT-Type
+  - attribute-value.length = 4 bytes
+  - attribute-value = <Not relevant in this test>
+- p. Mandatory attribute Sample-Period shall be present in ConfigReport:
+- attribute-id = MDC\_ATTR\_TIME\_PD\_SAMP
+  - attribute-type = RelativeTime
+  - attribute-value.length = 4 bytes
+  - attribute-value = <Not relevant in this test>
+- q. Mandatory attribute Scale-and-Range-Specification shall be present in ConfigReport:
+- attribute-id = MDC\_ATTR\_SCALE\_SPECN\_I8;  
+MDC\_ATTR\_SCALE\_SPECN\_I16; MDC\_ATTR\_SCALE\_SPECN\_I32
+  - attribute-type = ScaleRangeSpec8 OR ScaleRangeSpec16 OR ScaleRangeSpec32
+  - attribute-value.length = 1, 2 OR 4 bytes, depending of the type
+  - attribute-value = <Not relevant in this test>
+- r. Mandatory attribute Sa-Specification shall be present in ConfigReport:
+- attribute-id = MDC\_ATTR\_SA\_SPECN
+  - attribute-type = SaSpec
+  - attribute-value.length = 6 bytes
+  - attribute-value = <Not relevant in this test>
+- s. Time-stamp attributes (Absolute-Time-Stamp, Base-Offset-Time, Relative-Time-Stamp and HiRes-Time-Stamp), observed values attributes (Simple-Sa-Observed-Value) and Measurement-Status shall not be present if mss-cat-setting and/or mss-cat-manual bit of the Metric-Spec-Small attribute is set to 0. If any of these bits is set to 1, observational attributes may be present in ConfigReport.
+
+Furthermore, if MDS event reports are sent by the PHD (the PHD sends fixed format value messages to report dynamic data for RT-SA Objects or uses variable format event report, C\_AG\_OXP\_184=TRUE or C\_AG\_OXP\_189=TRUE):
+
+##### 5. 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.
+
+6. Take a measurement with the PHD
+
+7. Wait for an event report from the PHD
+  - a. IF attribute Absolute-Time-Stamp is present
+    - attribute-id = MDC\_ATTR\_TIME\_STAMP\_ABS
+    - attribute-type = AbsoluteTime
+    - attribute-value.length = 8 bytes
+    - attribute-value = <Not relevant in this test>
+      - century =
+      - year  $\leq$  99
+      - month  $\leq$  12
+      - day  $\leq$  31
+      - hour  $\leq$  24
+      - minute  $\leq$  60
+      - second  $\leq$  60
+      - sec-fractions  $\leq$  100
+    - If a PHD stores data, it shall associate a time stamp with the data.
+    - If a PHD supports Absolute-Time-Stamp, Base-Offset-Time-Stamp attribute shall not be supported.
+  - b. IF (C\_AG\_OXP\_014 = TRUE) THEN Attribute Base-Offset-Time-Stamp may be present ELSE it shall not be present
+    - attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+    - attribute-type = BaseOffsetTime
+    - attribute-value.length = 8 bytes
+    - attribute-value = <Not relevant in this test>
+    - If a PHD stores data, it shall associate a time stamp with the data.
+    - If a PHD supports Base-Offset-Time-Stamp, Absolute-Time-Stamp attribute shall not be supported.
+  - c. IF attribute Measure-Active-Period is present
+    - attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE
+    - attribute-type = FLOAT-Type
+    - attribute-value.length = 4 bytes
+    - attribute-value = <Not relevant in this test>
+  - d. IF attribute Relative-Time-Stamp is present
+    - attribute-id = MDC\_ATTR\_TIME\_STAMP\_REL
+    - attribute-type = RelativeTime
+    - attribute-value.length = 4 bytes
+    - attribute-value = <Not relevant in this test>
+  - e. IF a PHD stores data, it shall associate a time stamp with the data
+  - f. IF attribute HiResRelative-Time-Stamp is present
+    - attribute-id = MDC\_ATTR\_TIME\_STAMP\_REL\_HI\_RES
+    - attribute-type = HighResRelativeTime
+    - attribute-value.length = 8 bytes
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</p> <p>g. IF attribute Measurement Status is present</p> <p><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</p> <p><input type="checkbox"/> attribute-type = MeasurementStatus</p> <p><input type="checkbox"/> attribute-value.length = 2 bytes</p> <p><input type="checkbox"/> attribute-value = &lt;not relevant for this test&gt;</p> <p>h. Mandatory attribute Simple-Sa-Observed-Value</p> <p><input type="checkbox"/> attribute-id = MDC_ATTR_SIMP_SA_OBS_VAL</p> <p><input type="checkbox"/> attribute-type = OCTET STRING</p> <p><input type="checkbox"/> attribute-value.length = The length shall be even with padding bytes at the end.</p> <p><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</p> <p>i. Check dynamic attributes that may be present: Metric-Structure-Small, Metric-Id, Metric-Id-List, Metric-Id-Partition, Unit-Code, Source-Handle-Reference, Label-String, Unit-Label-String, Measure-Active-Period</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/DIM/BV-001_D                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |
+| <b>TP label</b>           | RealTime-SA: Sa-Specification semantic                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | ArrayClassAttr 4; M                                           |
+| <b>Test purpose</b>       | Check that:<br>The Sa-Specification attribute is of type SaSpec                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |
+| <b>Applicability</b>      | C_AG_OXP_042 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |
+| <b>Other PICS</b>         | C_AG_OXP_046, C_AG_OXP_047, C_AG_OXP_180                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |
+| <b>Test procedure</b>     | 1. Take a measurement with the PHD of a value stored in a RT-SA object.<br>2. Wait until the PHG receives an event report, the attributes of interest are:<br>a. Scale-and-Range-Specification:<br><input type="checkbox"/> Attribute-value = See below<br><input type="checkbox"/> lower-* -value = <Record for comparison><br><input type="checkbox"/> upper-* -value = <Record for comparison><br>b. Simple-Sa-Observed-Value<br><input type="checkbox"/> Attribute-value = <Record for comparison> |                                                               |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>Upper values must be <math>\geq</math> than the lower values</li> <li>Measurement Value must be in the allowed range.</li> </ul>                                                                                                                                                                                                                                                                                                                                |                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |
+
+|                     |                                                                                               |                                                               |
+|---------------------|-----------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>        | TP/PLT/PHD/OXP/DIM/BV-001_E                                                                   |                                                               |
+| <b>TP label</b>     | Numeric attributes: Metric-Id-List Semantic                                                   |                                                               |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                     | <b>Testable items</b>                                                                         | MetricClassAttr 9; C                                          |
+| <b>Test purpose</b> | The order of the Metric-Id-List shall correspond to the order of the elements in the compound |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | observed value.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Applicability</b>      | C_AG_OXP_190 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Other PICS</b>         | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_071, C_AG_OXP_188, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. IF C_AG_OXP_293 THEN: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 THEN it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG</li> </ul> </li> </ol> </li> <li>5. Make the PHD send measurements for objects that support Metric-Id-List.</li> <li>6. Wait for event reports.</li> <li>7. The Compound Simple and Basic Numeric observed value will be taken from the Event Report received in step 4 and this information and the Metric-Id-List will be showed to the operator using a pop-up.</li> </ol> |
+| <b>Pass/Fail criteria</b> | The operator checks in step 7 that the order of the Metric-Id-List corresponds to the order of the elements in the compound observed value.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes</b>              | If the PHD does not send the Metric-Id-List value in the ConfigReport, the PHD will send it in an MDS-Event Report before sending an observation (compound value). SE is allowed for the Metric-Id-List.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                 |                                                                   |                                                               |                      |
+|-----------------|-------------------------------------------------------------------|---------------------------------------------------------------|----------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/OXP/DIM/BV-002_A                                       |                                                               |                      |
+| <b>TP label</b> | PM-Store Object: Mandatory, Conditional and Optional Attributes 1 |                                                               |                      |
+| <b>Coverage</b> | <b>Spec</b>                                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                      |
+|                 | <b>Testable items</b>                                             | StoreClass 1; M                                               | StoreClassAttr 1; M  |
+|                 |                                                                   | StoreClassAttr 3; M                                           | StoreClassAttr 4; O  |
+|                 |                                                                   | StoreClassAttr 6; M                                           | StoreClassAttr 7; O  |
+|                 |                                                                   | StoreClassAttr 9; M                                           | StoreClassAttr 11; M |
+|                 |                                                                   | PersStoreMtrDatTransf 25; M                                   |                      |
+|                 | <b>Spec</b>                                                       | [b-ITU-T H.810 (2015)]                                        |                      |
+|                 | <b>Testable items</b>                                             | Communication 6; M                                            |                      |
+|                 | <b>Spec</b>                                                       | [ISO/IEEE 11073-10472]                                        |                      |
+|                 | <b>Testable items</b>                                             | MM_PMStoreAttr6; C                                            |                      |
+|                 | <b>Spec</b>                                                       | [IEEE 11073-10406]                                            |                      |
+|                 | <b>Testable items</b>                                             | PerPMStoreAtt2; M                                             | AperPMStoreAtt2; M   |
+|                 |                                                                   | PMStoreServ2; M                                               | PMStoreServ1; M      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PM-Store objects contain all mandatory attributes, conditional attributes as required by their conditions and it may contain optional attributes</p> <p>[AND]</p> <p>The nomenclature code to identify the PM-Store class is MDC_MOC_VMO_PMSTORE</p> <p>[AND]</p> <p>The handle value is placed in the obj-handle field of the message and is not present in the attribute-id list of the request or the attribute-list of the response.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_071, C_AG_OXP_187, C_AG_OXP_188, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Record the handle for the PM-Store object.</li> <li>5. 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.</li> <li>6. The PHD issues a GET response with the PM-Store attributes it supports:<br/> Verify the invoke-id is mirrored from the Get request. <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle shall not be present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test case&gt;</li> </ul> </li> <li>b. Mandatory attribute PM-Store-Capab <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li> <li><input type="checkbox"/> attribute-type = PmStoreCapab</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = one or more of the following bits may be set: <ul style="list-style-type: none"> <li>▪ pmsc-var-no-of-segm (bit 0)</li> <li>▪ IF C_AG_OXP_187 then bit 4 (pmsc-epi-seg-entries) must be set</li> <li>▪ IF C_AG_OXP_188 then bit 5 (pmsc-peri-seg-entries) must be set</li> <li>▪ pmsc-abs-time-select (bit 6)</li> <li>▪ pmsc-clear-segm-by-list-sup (bit 7)</li> <li>▪ pmsc-clear-segm-by-time-sup (bit 8)</li> <li>▪ pmsc-clear-segm-remove (bit 9)</li> <li>▪ pmsc-multi-person (bit 12)</li> <li>▪ All other bits shall be set to zero</li> </ul> </li> </ul> </li> <li>c. Mandatory attribute Store-Sample-Algorithm <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STORE_SAMPLE_ALG</li> <li><input type="checkbox"/> attribute-type = StoSampleAlg</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = One of the next <ul style="list-style-type: none"> <li>▪ st-alg-nos(0x00 0x00)</li> <li>▪ st-alg-moving-average(0x00 0x01)</li> </ul> </li> </ul> </li> </ol> </li> </ol> |
+
+- st-alg-recursive(0x00 0x02)
+- st-alg-min-pick(0x00 0x03)
+- st-alg-max-pick(0x00 0x04)
+- st-alg-median(0x00 0x05)
+- st-alg-trended(0x02 0x00)
+- st-alg-no-downsampling(0x04 0x00)
+- st-alg-manuf-specific-start(0xF0 0x0061440)
+- st-alg-manuf-specific-end(0xFF 0xFF)
+
+#### 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. Mandatory attribute Number-Of-Segments
+
+- attribute-id = MDC\_ATTR\_NUM\_SEG
+- attribute-type = INT-U16
+- attribute-value.length = 2 bytes
+- attribute-value = <not relevant for this test>
+
+#### f. IF attribute Clear-Timeout
+
+- attribute-id = MDC\_ATTR\_CLEAR\_TIMEOUT
+- attribute-type = RelativeTime
+- attribute-value.length = 4 bytes
+- attribute-value = <Not relevant in this test>
+- IF the PHD supports the clear segment action, Clear-Timeout attribute is mandatory.
+
+#### g. IF 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>
+
+#### h. IF Storage-Capacity-Count is present
+
+- attribute-id = MDC\_ATTR\_METRIC\_STORE\_CAPAC\_CNT
+- attribute-type = INT-U32
+- attribute-value.length = 4 bytes
+- attribute-value = See relation with next attribute
+
+#### i. IF Storage-Usage-Count is present
+
+- attribute-id = MDC\_ATTR\_METRIC\_STORE\_USAGE\_CNT
+- attribute-type = INT-U32
+- attribute-value.length = 4 bytes
+- attribute-value = always  $\leq$  than Storage-Capacity-Count
+
+#### j. IF attribute PM-Store-Label
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_LABEL_STRING</li> <li><input type="checkbox"/> attribute-type = OCTET STRING</li> <li><input type="checkbox"/> attribute-value.length =</li> <li><input type="checkbox"/> attribute-value = Printable ASCII</li> </ul> <p>7. IF C_AG_OXP_293 THEN</p> <ul style="list-style-type: none"> <li>a. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 THEN it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ul> <p>8. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection set to all-segments.</p> <p>9. The PHD issues a response (rors-cmip-confirmed-action) with the PM-Segment attributes it supports in the SegmentInfoList structure.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• All checked values are as specified in the test procedure.</li> <li>• IF in step 6.f the Sample-Period was not present it must be present in each PM-Segment.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                     |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-002_B                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                     |
+| <b>TP label</b>          | PM-Store Object: Mandatory, Conditional and Optional Attributes 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | StoreClassAttr 9; M                                           | StoreClassAttr 2; M |
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-10472]                                        |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MM_PMStoreAttr5; C                                            |                     |
+| <b>Test purpose</b>      | Check that:<br>PM-Store object includes the Number-Of-Segments attribute<br>[AND]<br>The Number-Of-Segments attribute is of type INT-U16<br>[AND]<br>A PM-Store object may include the Store-Usage-Count attribute<br>The Store-Usage-Count attribute shall be of type INT-U32                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                     |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |                     |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                     |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                     |
+| <b>Test procedure</b>    | 1. Make sure there are no measurements being taken.<br>2. 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.<br>3. The PHD issues a GET response with the PM-Store attributes. The attributes of interest are: <ul style="list-style-type: none"> <li>a. Mandatory attribute PM-Store-Capab <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li> <li><input type="checkbox"/> attribute-type = PmStoreCapab</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> </ul> |                                                               |                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>▪ pm-sc-var-no-of-segm. Record state for later comparison</li> </ul> </li> </ul> <p>b. Mandatory attribute Number-Of-Segments</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NUM_SEG</li> <li><input type="checkbox"/> attribute-type = INT-U16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;record for later comparison&gt;</li> </ul> <p>4. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection set to all-segments:</p> <p>a. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_GET_INFO</li> <li><input type="checkbox"/> SegmSelection = all-segments</li> </ul> <p>5. The PHD issues a response (rors-cmip-confirmed-action) with the PM-Segment attributes it supports in the SegmentInfoList structure:</p> <p>a. Verify the invoke-id is mirrored from the Get request a.</p> <p>b. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Response   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_GET_INFO</li> <li><input type="checkbox"/> SegmentInfoList = &lt;Attributes of the segments&gt;</li> </ul> <p>6. Record the number of existing Segments.</p> <p>7. If the PHD can record measurements in PM-Store while it is connected then take measurements whose values are stored in a PM-Segment.</p> <p>8. Repeat steps 2 through 5.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>▪ In step 2.a, if bit pm-sc-var-no-of-segm is not set, the number of segments stated in step 2.b and checked in step 5.b must remain unchanged.</li> <li>▪ The PM-Store attribute Number-Of-Segments value must contain the exact number of segments recorded in step 6.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                          |                                                                                                                                                                                                                                                                                |                                                               |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-002_C                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>TP label</b>          | PM-Store Object: Clear-Timeout Semantics                                                                                                                                                                                                                                       |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                          | StoreClassAttr 11; M                                          |  |
+| <b>Test purpose</b>      | Check that:<br><br>The value of Clear-Timeout attribute matches with the actual timeout value that the PHD uses to wait for a response to the Clear-Segments action                                                                                                            |                                                               |  |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_000 AND C_AG_OXP_071                                                                                                                                                                                                                                 |                                                               |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                               |                                                               |  |
+| <b>Test procedure</b>    | 1. Take a measurement that would be placed in the PM-Store.<br>2. 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.<br>3. The PHD issues a GET response with the PM-Store attributes. |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>4. Record the value of the Clear-Timeout Attribute (time in seconds = attribute-value*125/1e6).</p> <p>5. The simulated PHG sends a Segment Clear to one of the PM-Segments:</p> <p>a. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> <li><input type="checkbox"/> SegmSelection = all-segments</li> </ul> <p>6. The PHD under test operation response:</p> <p>Verify the invoke-id is mirrored from the Get request.</p> <p>a. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Response   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> </ul> |
+| <b>Pass/Fail criteria</b> | The PHG has to receive the confirmation in less than the value specified in the Clear-Timeout attribute.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-002_D                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |  |
+| <b>TP label</b>          | PM-Store Object: Episodic Semantics                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | StoreClassAttr 2; M                                           |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If PM-Store has some or all PM-Segments than contain episodic entries then it has to contain explicit time stamp information</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_187 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |  |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Make sure there are no measurements being taken.</li> <li>2. The simulated PHG receives an association request from the PHD under test.</li> <li>3. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>4. The PHD responds with a "Remote Operation Invoke   Confirmed Event Report" message: <ul style="list-style-type: none"> <li>a. Event-type=MDC_NOTI_CONFIG</li> </ul> </li> <li>5. IF C_AG_OXP_293 THEN: <ul style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 THEN it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the</li> </ul> </li> </ul> </li> </ol> |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>PHG.</p> <ol style="list-style-type: none"> <li>6. Check that the PM-Store-Capab attribute has the pmsc-epi-seg-entries bit set.</li> <li>7. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection set to all-segments.</li> <li>8. The PHD shall respond to the Get-Segment-Info, indicating the attributes of the PM-Segment.</li> <li>9. Check the PM-Segment-Entry-Map to make sure that a Time-Stamp is associated with the measurement data.</li> <li>10. Take measurements with the PHD under test.</li> <li>11. The simulated PHG sends a request for the PM-Segment Data to one of the PM-Segments that contains data (sends the Action MDC_ACT_SEG_TRIG_XFER).</li> <li>12. The PHD issues an action response.</li> <li>13. The PHD under test starts Data transfer: <ol style="list-style-type: none"> <li>a. Data APDU <ol style="list-style-type: none"> <li><input type="checkbox"/> Invoke   CfmEventReport</li> <li><input type="checkbox"/> Action = MDC_NOTI_SEGMENT_DATA</li> <li><input type="checkbox"/> SegmentDataEvent</li> </ol> </li> </ol> </li> <li>14. The simulated PHG responds to transferred data APDU's.</li> </ol> |
+| <b>Pass/Fail criteria</b> | The PM-Segment-Entry-Map contains a Time-Stamp associated with measurement data and it has the correct format in the SegmentDataEvent received.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                      |
+|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|----------------------|
+| <b>TP Id</b>        | TP/PLT/PHD/OXP/DIM/BV-002_E                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |                      |
+| <b>TP label</b>     | PM-Store Object: Mandatory, Conditional and Optional Attributes 3 Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                      |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                      |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | StoreClass 1; M                                               | StoreClassAttr 1; M  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | StoreClassAttr 3; M                                           | StoreClassAttr 4; O  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | StoreClassAttr 6; M                                           | StoreClassAttr 7; O  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | StoreClassAttr 9; M                                           | StoreClassAttr 11; M |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ConfEventRep 30; M                                            | ConfEventRep 31; C   |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PM-StoreService 3; O                                          | StoreClassAttr 8; C  |
+|                     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [b-ITU-T H.810 (2015)]                                        |                      |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Communication 6; M                                            |                      |
+| <b>Test purpose</b> | <p>Check that:</p> <p>PM-Store objects contain all mandatory attributes, conditional attributes as required by their conditions and it may contain optional attributes</p> <p>[AND]</p> <p>The nomenclature code to identify the PM-Store class is MDC_MOC_VMO_PMSTORE</p> <p>[AND]</p> <p>Static, dynamic and observational attributes.</p> <p>[AND]</p> <p>A PHD may also send scan event reports providing the PHG with updates of the current attribute values, but this is not a mandated PHD behaviour.</p> <p>[AND]</p> <p>Changes to any non-static attributes values on PM-stores or the MDS may be reported to the PHG in event reports at the discretion of the PHD</p> |                                                               |                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_071, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. The PM-Store object attributes must be(ConfigReport -&gt; ConfigObject-&gt; AttributeList): <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle shall not be present. <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = must be unique and non-zero. Actual value may be specified by the Device Specialization.</li> </ul> </li> <li>b. Mandatory attribute PM-Store-Capab shall be present in ConfigReport: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li> <li><input type="checkbox"/> attribute-type = PmStoreCapab</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> </li> <li>c. Mandatory attribute Store-Sample-Algorithm shall be present in ConfigReport: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STORE_SAMPLE_ALG</li> <li><input type="checkbox"/> attribute-type = StoSampleAlg</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> </li> <li>d. IF Storage-Capacity-Count is supported, it shall be present in ConfigReport: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STORE_CAPAC_CNT</li> <li><input type="checkbox"/> attribute-type = INT-U32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> </li> <li>e. IF Storage-Usage-Count is supported, it should be present in ConfigReport: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STORE_USAGE_CNT</li> <li><input type="checkbox"/> attribute-type = INT-U32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> </li> <li>f. Mandatory attribute Operational-State should be present in ConfigReport: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_OP_STAT</li> <li><input type="checkbox"/> attribute-type = OperationalState</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> </li> <li>g. IF attribute PM-Store-Label is supported, it shall be present in ConfigReport: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_LABEL_STRING</li> <li><input type="checkbox"/> attribute-type = OCTET STRING</li> <li><input type="checkbox"/> attribute-value.length =</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> </li> <li>h. IF attribute Sample-Period is supported, it shall be present in ConfigReport: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_SAMP</li> </ul> </li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = RelativeTime</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> <ul style="list-style-type: none"> <li>i. Mandatory attribute Number-Of-Segments should be present in ConfigReport: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NUM_SEG</li> <li><input type="checkbox"/> attribute-type = INT-U16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;not relevant for this test&gt;</li> </ul> </li> <li>j. If attribute Clear-Timeout is supported, it should be present in ConfigReport: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_CLEAR_TIMEOUT</li> <li><input type="checkbox"/> attribute-type = RelativeTime</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> </li> </ul> <p>Furthermore if MDS event reports are sent by the PHD:</p> <ul style="list-style-type: none"> <li>5. IF C_AG_OXP_293 THEN: <ul style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 THEN it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ul> </li> <li>6. Take a measurement with the PHD.</li> <li>7. Wait for a variable format event report from the PHD, check that dynamic attributes for PM-Store may be reported (Store-Usage-Count, Operational-State, Number-Of-Segments, Clear-Timeout).</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                    |  |  |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------|--|--|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-003_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                    |  |  |
+| <b>TP label</b>          | PM-Segment Object: Mandatory, Conditional and Optional Attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                    |  |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                    |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | PM-SegmAttr 1; M                                              | PM-SegmAttr 2; M   |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | PM-SegmAttr 5; C                                              | PM-SegmAttr 6; O   |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | PM-SegmAttr 8; O                                              | PM-SegmAttr 9; O   |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | PM-SegmAttr 11; O                                             | PM-StoreMeth 10; M |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | PM-StoreMeth 1; M                                             | PM-SegmAttr 19; C  |  |  |
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [IEEE 11073-10406]                                            |                    |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | PerPMStoreAtt12; C                                            | PMStoreObjMeth2; M |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | PerPMSegObj2; M                                               | PerPMSegObj3; C    |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | PerPMSegObj5; C                                               | PerPMSegObj6; O    |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | PerPMSegObj8; C                                               | PerPMSegObj9; C    |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | PerPMSegObj12; M                                              | PerPMSegObj13; O   |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | PerPMSegObj15; O                                              | PerPMSegObj16; M   |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | AperPMSegObj1; M                                              | AperPMSegObj2; M   |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | AperPMSegObj4; M                                              | AperPMSegObj5; O   |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | AperPMSegObj7; M                                              | AperPMSegObj8; M   |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | AperPMSegObj10; C                                             | AperPMSegObj11; C  |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | AperPMSegObj13; O                                             | AperPMSegObj14; M  |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | AperPMSegObj16; M                                             |                    |  |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [b-ITU-T H.810 (2015)]                                        |                    |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | General 2; M                                                  |                    |  |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If a PHD supports the PM-store class, the support of the Get-Segment-Info is mandatory</p> <p>[AND]</p> <p>Its PM-Segment objects contain all mandatory and conditional attributes as required by their conditions which may also contain optional attributes</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                    |  |  |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                    |  |  |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_188                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                    |  |  |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                    |  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>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.</li> <li>The PHD issues a GET response with the PM-Store attributes. Check for the existence of: <ol style="list-style-type: none"> <li>attribute Sample-Period is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_SAMP</li> <li><input type="checkbox"/> attribute-type = RelativeTime</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> </li> </ol> </li> <li>The simulated PHG shall send a Get-Segment-Info object action for the PM-Segment object with SegmSelection = all-segments to indicate the PM-Segment attributes of all</li> </ol> |                                                               |                    |  |  |
+
+available PM-Segments.
+
+4. The PHD issues a "rors-cmip-confirmed-action" response with the PM-Segment attributes it supports:
+
+Verify the invoke-id is mirrored from the Get request.
+
+- a. Mandatory attribute Instance-Number
+
+- attribute-id = MDC\_ATTR\_ID\_INSTNO
+- attribute-type = InstNumber
+- attribute-length = 2 bytes
+- attribute-value = unique in its PM-Store (This is why we ask for all the attributes of all the PM-Segment)
+
+- b. Mandatory attribute PM-Segment-Entry-Map
+
+- attribute-id = MDC\_ATTR\_PM\_SEG\_MAP
+- attribute-type = PmSegmentEntryMap
+- attribute-value = SEQUENCE, it must match the entries
+
+- c. Mandatory attribute Operational-State
+
+- attribute-id = MDC\_ATTR\_OP\_STAT
+- attribute-type = OperationalState
+- attribute-value.length = 2 bytes
+- attribute-value = {disabled(0), enabled(1), notAvailable(2)}
+
+- d. Mandatory attribute Transfer-Timeout
+
+- attribute-id = MDC\_ATTR\_TRANSFER\_TIMEOUT
+- attribute-type = RelativeTime
+- attribute-value.length = 4 bytes
+
+- e. IF attribute PM-Seg-Person-Id is present
+
+- attribute-id = MDC\_ATTR\_PM\_SEG\_PERSON\_ID
+- attribute-type = PersonId
+- attribute-value.length = 2 bytes
+- attribute-value =
+- If the PM-Store is able to store data for multiple persons it shall set the pmsc-multi-person bit in the PM-Store-Capab attribute. If this bit is set, all PM-Segment instances contained in the PM-Store shall support the PM-Seg-Person-Id attribute, check with the attributes obtained in step 2.
+
+- f. IF attribute Sample-Period is present
+
+- attribute-id = MDC\_ATTR\_TIME\_PD\_SAMP
+- attribute-type = RelativeTime
+- attribute-value.length = 4 bytes
+- attribute-value =
+- IF in step 2 Sample-Period was not present and values are sampled periodically this attribute must be present either in the PM-Store or alternatively in each PM-Segment. If values are sampled, then the pmsc-peri-seg-entries bit in the PM-Store-Capab attribute shall be set, check with attributes obtained in step 2 The [Sample-Period] attribute must be present in either the PM-Store or alternatively in each of the PM-Segments if values are sampled periodically - so the time difference for 2 entries in the Fixed-Segment-Data is constant (the pmsc-peri-seg-entries bit in the Pm-Store-Capab attribute is set).
+
+- g. IF 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 =
+- If the PHD ever adjusts the Date-and-Time, this attribute reports the time adjustment.
+
+h. IF attribute Segment-Label is present
+
+- attribute-id = MDC\_ATTR\_PM\_SEG\_LABEL\_STRING
+- attribute-type = OCTET STRING
+- attribute-value.length = consistent with value
+- attribute-value = <printable ASCII>
+
+i. IF(C\_AG\_OXP\_009 = TRUE) THEN attribute Segment-Start-Abs-Time may be present ELSE it shall not be present
+
+- attribute-id = MDC\_ATTR\_TIME\_START\_SEG
+- attribute-type = AbsoluteTime
+- attribute-value.length = 8 bytes
+- attribute-value =
+  - century =
+  - year  $\leq$  99
+  - month  $\leq$  12
+  - day  $\leq$  31
+  - hour  $\leq$  24
+  - minute  $\leq$  60
+  - second  $\leq$  60
+  - sec-fractions  $\leq$  100
+- Note: This attribute is required if the PHD supports actions on the segment by time (i.e., the pmsc-abs-time-select and/or the pmsc-clear-segm-bytime- sup bits are set) this attribute shall be present.
+- If this attribute is used, the Segment-Start-BO-Time shall not be used.
+
+j. IF (C\_AG\_OXP\_009 = TRUE) THAN attribute Segment-End-Abs-Time may be present ELSE it hall not be present
+
+- attribute-id = MDC\_ATTR\_TIME\_END\_SEG
+- attribute-type = AbsoluteTime
+- attribute-value.length = 8 bytes
+- attribute-value =
+  - century =
+  - year  $\leq$  99
+  - month  $\leq$  12
+  - day  $\leq$  31
+  - hour  $\leq$  24
+  - minute  $\leq$  60
+  - second  $\leq$  60
+  - sec-fractions  $\leq$  100
+- Note: This attribute is required if the PHD supports actions on the segment by time (i.e., the pmsc-abs-time-select and/or the pmsc-clear-segm-bytime- sup bits are set) this attribute shall be present.
+- If this attribute is used, the Segment-End-BO-Time shall not be used.
+
+k. IF (C\_AG\_OXP\_014 = TRUE) THEN attribute Segment-Start-BO-Time may be present ELSE it shall not be present
+
+- attribute-id = MDC\_ATTR\_TIME\_START\_SEG\_BO
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> <li><input type="checkbox"/> If this attribute is used, the Segment-Start-Abs-Time shall not be used.</li> </ul> <p>l. IF (C_AG_OXP_014 = TRUE) THEN attribute Segment-End-BO-Time may be present ELSE it shall not be present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_START_SEG_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> <li><input type="checkbox"/> If this attribute is used, the Segment-End-Abs-Time shall not be used</li> </ul> <p>m. IF attribute Segment-Usage-Count is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SEG_USAGE_CNT</li> <li><input type="checkbox"/> attribute-type = INT-U32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = check that it has the number of stored entries</li> </ul> <p>n. IF attribute Segment-Statistics</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SEG_STATS</li> <li><input type="checkbox"/> attribute-type = SegmentStatistics</li> <li><input type="checkbox"/> attribute-value.length = must be consistent with EntryMap</li> <li><input type="checkbox"/> attribute-value =</li> </ul> <p>o. IF attribute Confirm-Timeout is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_CONFIRM_TIMEOUT</li> <li><input type="checkbox"/> attribute-type = RelativeTime</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value =</li> </ul> <p>5. Repeat steps 3 and 4 for every Segment.</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-003_B                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |
+| <b>TP label</b>          | PM-Segment Object: Semantic of Segment Statistic attribute                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                | PM-SegmAttr 11; O                                             |
+| <b>Test purpose</b>      | Check that:<br>Segment-Statistics attribute values matches with the min/max/mean of the segment data content.                                                                                                                                                                                                                                                                                                                        |                                                               |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_074 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                     |                                                               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG sends a "roiv-cmip-confirmed-action", action-type MDC_ACT_SEG_GET_INFO, with SegmSelection (all-segments).</li> <li>2. The PHD responds with a "rors-cmip-confirmed-action", action-type MDC_ACT_SEG_GET_INFO, giving information about the attributes of every PM-Segment. For every segment, the Segment-Statistic attribute is recorded if it is supported</li> </ol> |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>by the PHD.</p> <ol style="list-style-type: none"> <li>3. The simulated PHG sends a "roiv-cmip-confirmed-action", action-type MDC_ACT_SEG_TRIG_XFER for a PM-Segment that supports the Segment-Statistic attribute.</li> <li>4. The PHD sends a "rors-cmip-confirmed-action", action-type MDC_ACT_SEG_TRIG_XFER, with TrigSegmDataXferRsp "tsxr-successful".</li> <li>5. The PHD sends a "roiv-cmip-confirmed-event-report", action-type MDC_NOTI_SEGMENT_DATA.</li> <li>6. Record the segment-data-event-entries in step 5, calculate the min, max or mean for every entry and compare it with the Segment-Statistic attribute value.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The maximum of every entry recorded in step 5 is not higher than the max defined in the SegmentStatistic attribute recorded in step 2 if SegStatType is "segm-stat-type-maximum".</li> <li>• The minimum of every entry recorded in step 5 is not lower than the min defined in the SegmentStatistic attribute recorded in step 2 if SegStatType is "segm-stat-type-minimum".</li> <li>• The mean of every entry recorded in step 5 matches the mean defined in the SegmentStatistic attribute recorded in step 2 if SegStatType is "segm-stat-type-average".</li> </ul>                                    |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/OPX/DIM/BV-003_C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>TP label</b>          | PM-Segment Object: Semantic of PM-Seg-Person-Id attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | PM-SegmAttr 3; O                                              |  |
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | [b-ITU-T H.810 (2015)]                                        |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | General 6; C                                                  |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If the PM-Store is able to store data for multiple persons, it sets the pmsc-multi-person bit in the PM-Store-Capab attribute.</p> <p>[AND]</p> <p>If this bit is set, all PM-Segment instances contained in the PM-Store supports the PM-Seg-Person-Id attribute</p> <p>[AND]</p> <p>Continua 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 pmsc-multi-person bit in the PM-Store-Capab PM-Store object attribute</p>                                                                                                                          |                                                               |  |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_035 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>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.</li> <li>2. The PHD issues a GET response with the PM-Store attributes.</li> <li>3. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection set to all-segments to indicate all PM-Segments attributes.</li> <li>4. The PHD issues a response with the PM-Segment attributes it supports.</li> <li>5. The simulated PHG sends a request for the PM-Segment Data.</li> <li>6. The PHD issues an action response (action: MDC_ACT_SEG_TRIG_XFER, action-info-args: TrigSegmDataXferRsp).</li> </ol> |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                             |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | 7. The PHD under test sends a Segment-Data-Event message.                                                                                                                                                                                                                   |
+| <b>Pass/Fail criteria</b> | The pmsc-multi-person bit in the PM-Store-Capab attribute must be set and all PM-Segment instances contained in the PM-Store must contain the PM-Seg-Person-Id attribute.<br>In step 7, measurements stored in the PM-Stored have to be assigned correctly to every person. |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |               |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/DIM/BV-003_D                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |               |
+| <b>TP label</b>           | PM-Segment Object: semantic of data-and-Time Adjustment attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |               |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | PM-SegmAttr 9; O                                              | AbsTime 15; C |
+| <b>Test purpose</b>       | Check that:<br>If the PHD adjusts the Date-and-Time, then this attribute report the time adjustment                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |               |
+| <b>Applicability</b>      | C_AG_OXP_041 AND C_AG_OXP_012 AND C_AG_OXP_000 AND C_AG_OXP_016                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |               |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Take a measurement with PHD.</li> <li>2. Make a noticeable change in change in the Date or Time of the PHD.</li> <li>3. Take a new measurement.</li> <li>4. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with an attribute-id-list set to 0 to indicate all PM-Segments attributes.</li> <li>5. The PHD issues a response with the PM-Segment attributes it supports, the attribute of interest: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_ABS_ADJUST</li> <li><input type="checkbox"/> attribute-type = absolute-time-adjust</li> <li><input type="checkbox"/> attribute-length = 6 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Must contain the adjustment (+-44505 years)&gt;</li> </ul> </li> </ol> |                                                               |               |
+| <b>Pass/Fail criteria</b> | The PM-Segment attribute Date-and-Time-Adjustment must inform of the change.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |               |
+
+|                          |                                                                                                                                                                                                                                                                                                                         |                                                               |               |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-003_E                                                                                                                                                                                                                                                                                             |                                                               |               |
+| <b>TP label</b>          | PM-Segment Object: semantic of data-and-Time Adjustment attribute. Disconnected                                                                                                                                                                                                                                         |                                                               |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |               |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                   | PM-SegmAttr 9; O                                              | AbsTime 15; C |
+| <b>Test purpose</b>      | Check that:<br>If the PHD adjusts the Date-and-Time, then this attribute report the time adjustment                                                                                                                                                                                                                     |                                                               |               |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_012 AND C_AG_OXP_000                                                                                                                                                                                                                                                                          |                                                               |               |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                |                                                               |               |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                     |                                                               |               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Take measurements with PHD that are stored in a segment.</li> <li>2. Make a noticeable change in change in the Date or Time of the PHD.</li> <li>3. Take a new measurement.</li> <li>4. The simulated PHG receives an association request from the PHD under test.</li> </ol> |                                                               |               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>5. The simulated PHG responds with a result = accepted-unknown-config.</p> <p>6. 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.</p> <p>7. IF C_AG_OXP_293 THEN:</p> <ul style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 THEN it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ul> <p>8. Once in the Operating state, the simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with an attribute-id-list set to 0 to indicate all PM-Segment attributes.</p> <p>9. The PHD issues a response with the PM-Segment attributes it supports, the attribute of interest:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_ABS_ADJUST</li> <li><input type="checkbox"/> attribute-type = absolute-time-adjust</li> <li><input type="checkbox"/> attribute-length = 6 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Must contain the adjustment (+-44505 years)&gt;</li> </ul> |
+| <b>Pass/Fail criteria</b> | The PM-Segment attribute Date-and-Time-Adjustment must inform of the change.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                    |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-005                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                    |
+| <b>TP label</b>          | PM-Segment Object. Confirm Timeout                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                    |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                    |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | PM-SegmAttr 13; O                                             | OperErrorCond 5; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | TimeOutVar 2; C                                               | OperErrorCond 6; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If Confirm-Timeout attribute is supported, then its value matches with the actual timeout value that the PHD uses for the Confirmed Event Report generated from the PM-Store Object</p> <p>[AND]</p> <p>TOcer-pms: If the attribute is not present, the PHD shall use the value 3 s.</p>                                                                                                                                                                                                                                                                                    |                                                               |                    |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                    |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                    |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                    |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG shall send a Get-Segment-Info object action for the PM-Segment object with SegmSelection set to all-segments to indicate all PM-Segments attributes.</li> <li>2. Record the Confirm-Timeout value from the Get PM-Segment operation. If the attribute is not present its value shall be 3 s(TOcer-pms ).</li> <li>3. The simulated PHG sends a request for the PM-Segment Data with SegmSelection = Segment-id-list.</li> <li>4. The PHD issues a response with the PM-Segments attributes (action: MDC_ACT_SEG_GET_INFO).</li> </ol> |                                                               |                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>5. The simulated PHG sends a request for the PM-Segment Data.</p> <p>6. The PHD issues an action response (action: MDC_ACT_SEG_TRIG_XFER, action-info-args: TrigSegmDataXferRsp).</p> <p>7. The PHD under test sends a Segment-Data-Event message.</p> <p>8. The simulated PHG does not respond for at least the time specified in the field Confirm-Timeout.</p> <p>9. The PHD waits the Confirm-Timeout time and then it must send an abort message to the PHG and move to the Unassociated state.</p> |
+| <b>Pass/Fail criteria</b> | The PHD waits TO <sub>cer-pms</sub> time and then it must send an abort message to the PHG and changes to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                     |                      |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------------|----------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-008                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                     |                      |
+| <b>TP label</b>          | EpiCfgScanner Object: Mandatory, Conditional and Optional Attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                     |                      |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                     |                      |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | ScanClassAttr 1; M                                            | ScanClassAttr 2; M  | ScanClassAttr 4; C   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ScanClassAttr 6; C                                            | CfgScanAttr 1; M    | CfgScanAttr 2; C     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | CfgScanAttr 5; O                                              | EpiCfgScanAttr 1; O | EpiCfgScanClass 3; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ConfNormalProc 1; M                                           | ConfEventRep 29; M  | ConfEventRep 30; M   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ConfEventRep 31; C                                            | ConfEventRep 33; O  |                      |
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [IEEE 11073-10406]                                            |                     |                      |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | EpiScanObjAttr1; M                                            | EpiScanObjAttr2; M  | EpiScanObjAttr3; C   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | EpiScanObjAttr4; C                                            | EpiScanObjAttr5; M  | EpiScanObjAttr6; O   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | EpiScanObjAttr7; O                                            |                     |                      |
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [b-ITU-T H.810 (2015)]                                        |                     |                      |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Communication 6; M                                            |                     |                      |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Scanner objects contain all mandatory attributes, conditional attributes as required by their conditions and it may contain optional attributes</p> <p>[AND]</p> <p>The nomenclature code to identify the Episodic Configurable Scanner class is MDC_MOC_SCAN_CFG_EPI</p> <p>[AND]</p> <p>Two consecutive event reports shall not have a time interval less than Min-Reporting-Interval</p> <p>[AND]</p> <p>Episodic Scanner Object attributes are static, dynamic or observational.</p> <p>[AND]</p> <p>Changes to any attribute values of metric and scanner objects shall be reported to the PHG in scan event reports prior to sending event reports that depend on those values (e.g. scan-handle-attr-val-map and a group format event report or unit-code and the observed value).</p> |                                                               |                     |                      |
+| <b>Applicability</b>     | C_AG_OXP_047 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                     |                      |
+| <b>Other PICS</b>        | C_AG_OXP_144, C_AG_OXP_180                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                     |                      |
+| <b>Initial condition</b> | The simulated PHG and PHD under test have been associated, but the PHD configuration is unknown for simulated PHG, so the PHD and the simulated PHG will be in the Configuring state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                     |                      |
+| <b>Test procedure</b>    | <p>1. The simulated PHG receives an association request from the PHD under test.</p> <p>2. The simulated PHG responds with a result = accepted-unknown-config.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                     |                      |
+
+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. The Configurable Episodic Scanner object (ConfigReport -> ConfigObject-> AttributeList) must have:
+  - a. Mandatory attribute Handle shall not be present
+    - attribute-type = HANDLE
+    - attribute-value = 2 bytes
+    - attribute-value = <Must be unique but not relevant in this test>
+  - b. Mandatory attribute Operational-State should be present un ConfigReport:
+    - attribute-id = MDC\_ATTR\_OP\_STAT
+    - attribute-type = OperationalState
+    - attribute-value.length = 2 bytes
+    - attribute-value = 0 at start
+  - c. IF attribute Scan-Handle-List is supported, it should be present in ConfigReport:
+    - attribute-id = MDC\_ATTR\_SCAN\_HANDLE\_LIST
+    - attribute-type = HANDLEList
+    - attribute-value.length =
+    - attribute-value = <Not Relevant for this test>
+  - d. IF attribute Scan-Handle-Attr-Val-Map is supported, it should be present in ConfigReport:
+    - attribute-id = MDC\_ATTR\_SCAN\_HANDLE\_ATTR\_VAL\_MAP
+    - attribute-type = HANDLEAttrValMap
+    - attribute-value.count = N
+    - attribute-value.length = <Variable>
+    - attribute-value = <Not Relevant for this test>
+  - e. Mandatory attribute Confirm-Mode should be present in ConfigReport:
+    - attribute-id = MDC\_ATTR\_CONFIRM\_MODE
+    - attribute-type = ConfirmMode
+    - attribute-value = One of:
+      - unconfirmed (0x00 0x00)
+      - confirmed (0x00 0x01)
+  - f. Optional Confirm-Timeout should be present in ConfigReport:
+    - attribute-id = MDC\_ATTR\_CONFIRM\_TIMEOUT
+    - attribute-type = RelativeTime
+    - attribute-value.length = 4 bytes
+    - attribute-value = <Not relevant for this test>
+  - g. IF attribute Transmit-Window is supported, it should be present in ConfigReport:
+    - attribute-id = MDC\_ATTR\_TX\_WIND
+    - attribute-type = INT-U16
+    - attribute-value.length = 2 bytes
+    - attribute-value = 1
+  - h. Optional attribute Min-Reporting-Interval should be present in ConfigReport:
+    - attribute-id = MDC\_ATTR\_SCAN\_REP\_PD\_MIN
+    - attribute-type = RelativeTime
+    - attribute-value.length = 4 bytes
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><input type="checkbox"/> attribute-value = &lt;defined by vendor&gt; IF the PHD supports Min-Reporting-Interval attribute (C_AG_OXP_144) THEN at least there is a scanner object that supports this attribute, ELSE, no scanner objects support this attribute.</p> <p>5. Furthermore check if Variable MDS Scan Event Reports are sent by the PHD for the Scanner object:</p> <ol style="list-style-type: none"> <li>Wait for a Scan Event Report from the PHD. <ul style="list-style-type: none"> <li>Attributes whose values may be reported will be the attributes defined as dynamic: Operational-State, Scan-Handle-List, Scan-Handle-Attr-Val-Map, Confirm-Mode, Confirm-Timeout, Transmit-Window and Min-Reporting-Interval.</li> </ul> </li> <li>Set to enable the Operational-State for the Episodic Scanner object to make the Scanner object send event reports: <ul style="list-style-type: none"> <li>If the PHD sends Unbuf-Scan-Report-Fixed or Variable, Scan-Handle-List attributes shall be received previously.</li> <li>If the PHD sends Unbuf-Scan-Report-Grouped, Scan-Handle-Attr-Val-Map attributes shall be received previously.</li> </ul> </li> <li>Set to disable the Operation-State for the Episodic Scanner object and repeat step 5b for every episodic scanner object.</li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                       |                      |
+|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------|----------------------|
+| <b>TP Id</b>         | TP/PLT/PHD/OXP/DIM/BV-009                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                       |                      |
+| <b>TP label</b>      | PeriCfgScanner Object: Mandatory, Conditional and Optional Attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                       |                      |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                       |                      |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | ScanClassAttr 1; M                                            | ScanClassAttr 2; M    | ScanClassAttr 4; C   |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ScanClassAttr 6; C                                            | CfgScanAttr 1; M      | CfgScanAttr 2; C     |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | CfgScanAttr 5; O                                              | PeriCfgScanClass 2; M | PeriCfgScanAttr 1; M |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ConfNormalProc 1; M                                           | ConfEventRep 29; M    | ConfEventRep 30; M   |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ConfEventRep 31; C                                            | ConfEventRep 33; O    |                      |
+|                      | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [IEEE 11073-10406]                                            |                       |                      |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | PerScanObjAttr1; M                                            | PerScanObjAttr2; M    | PerScanObjAttr3; C   |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PerScanObjAttr4; O                                            | PerScanObjAttr5; M    | PerScanObjAttr6; O   |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PerScanObjAttr7; O                                            | PerScanObjAttr8; M    |                      |
+|                      | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [b-ITU-T H.810 (2015)]                                        |                       |                      |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Communication 6; M                                            |                       |                      |
+| <b>Test purpose</b>  | <p>Check that:</p> <p>Scanner objects contain all mandatory attributes, conditional attributes as required by their conditions and it may contain optional attributes</p> <p>[AND]</p> <p>The nomenclature code to identify the Periodic Configurable Scanner class is MDC_MOC_SCAN_CFG_PERI</p> <p>[AND]</p> <p>Periodic Scanner Object attributes are static, dynamic or observational.</p> <p>[AND]</p> <p>Changes to any attribute values of metric and scanner objects shall be reported to the PHG in scan event reports prior to sending event reports that depend on those values (e.g. scan-handle-attr-val-map and a group format event report or unit-code and the observed value).</p> |                                                               |                       |                      |
+| <b>Applicability</b> | C_AG_OXP_046 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                       |                      |
+| <b>Other PICS</b>    | C_AG_OXP_144, C_AG_OXP_180                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                       |                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b> | The simulated PHG and 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.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. The Configurable Periodic Scanner object (ConfigReport -&gt; ConfigObject-&gt; AttributeList) must have: <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle shall not be present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 2 bytes</li> <li><input type="checkbox"/> attribute-value = must be unique&lt;Not relevant in this test&gt;</li> </ol> </li> <li>b. Mandatory attribute Operational-State should be present in ConfigReport: <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_OP_STAT</li> <li><input type="checkbox"/> attribute-type = OperationalState</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = 0 at start</li> </ol> </li> <li>c. IF Attribute Scan-Handle-List is supported, it should be present in ConfigReport: <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SCAN_HANDLE_LIST</li> <li><input type="checkbox"/> attribute-type = HANDLEList</li> <li><input type="checkbox"/> attribute-value.length =</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>d. IF attribute Scan-Handle-Attr-Val-Map is supported, it should be present in ConfigReport: <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SCAN_HANDLE_ATTR_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = HANDLEAttrValMap</li> <li><input type="checkbox"/> attribute-value.count = N</li> <li><input type="checkbox"/> attribute-value.length = &lt;Variable&gt;</li> <li><input type="checkbox"/> attribute-value = N metric-derived object must be specified here, verify the correct format of the object and that the handle points to the object.</li> </ol> </li> <li>e. Mandatory attribute Confirm-Mode should be present in ConfigReport: <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_CONFIRM_MODE</li> <li><input type="checkbox"/> attribute-type = ConfirmMode</li> <li><input type="checkbox"/> attribute-value = One of: <ul style="list-style-type: none"> <li>▪ unconfirmed (0x00 0x00)</li> <li>▪ confirmed (0x00 0x01)</li> </ul> </li> </ol> </li> <li>f. Optional Confirm-Timeout should be present in ConfigReport: <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_CONFIRM_TIMEOUT</li> <li><input type="checkbox"/> attribute-type = RelativeTime</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;.</li> </ol> </li> <li>g. IF attribute Transmit-Window is supported, it should be present in ConfigReport: <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TX_WIND</li> <li><input type="checkbox"/> attribute-type = INT-U16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ol> </li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value = 1</li> </ul> <p>h. Mandatory attribute Reporting-Interval should be present in ConfigReport:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SCAN_REP_PD</li> <li><input type="checkbox"/> attribute-type = RelativeTime</li> <li><input type="checkbox"/> attribute-length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>5. Furthermore check if the Variable MDS Scan Event Reports are sent by the PHD for the Scanner object:</p> <ol style="list-style-type: none"> <li>a. Wait for a Scan Event Report from the PHD. <ul style="list-style-type: none"> <li>• Attributes whose values may be reported will be the attributes defined as dynamic: Operational-State, Scan-Handle-List, Scan-Handle-Attr-Val-Map, Confirm-Mode, Confirm-Timeout, Transmit-Window and Reporting-Interval.</li> </ul> </li> <li>b. Set to enable Operational-State for the Periodic Scanner object to make the Scanner object send event reports: <ul style="list-style-type: none"> <li>• If the PHD sends a Buf-Scan-Report-Fixed or Variable, Scan-Handle-List attributes shall be received previously.</li> <li>• If the PHD sends a Buf-Scan-Report-Grouped, Scan-Handle-Attr-Val-Map attributes shall be received previously.</li> </ul> </li> <li>c. Set to disable Operation-State for Periodic Scanner object and repeat step 5b for every periodic scanner object.</li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                   |               |
+|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-------------------|---------------|
+| <b>TP Id</b>        | TP/PLT/PHD/OXP/DIM/BV-010                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                   |               |
+| <b>TP label</b>     | MDS objects methods and events. PHD data transmission                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                   |               |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                   |               |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | MDSEvent 2; C                                                 | MDSEvent 3; C     | MDSEvent 4; C |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | MDSEvent 5; C                                                 | CommonCharac 3; M |               |
+|                     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [b-ITU-T H.810 (2015)]                                        |                   |               |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | General 7; C                                                  |                   |               |
+| <b>Test purpose</b> | <p>Check that:</p> <p>If the PHD uses Variable Format Event Reporting and reports on a single patient, then it uses the MDS-Dynamic-Data-Update-Var Event to report dynamic data and the type of the Data APDU is ScanReportInfoVar</p> <p>[OR]</p> <p>If the PHD uses Fixed Format Event Reporting and reports on a single patient, then it uses the MDS-Dynamic-Data-Update-Fixed Event to report dynamic data and the type of the Data APDU is ScanReportInfoFixed</p> <p>[OR]</p> <p>If the PHD uses Variable Format Event Reporting and reports on multiple patients, then it uses the MDS-Dynamic-Data-Update-MP-Var Event to report dynamic data and the type of the Data APDU is ScanReportInfoMPVar</p> <p>[OR]</p> <p>If the PHD uses Fixed Format Event Reporting and reports on multiple patients, then it uses the MDS-Dynamic-Data-Update-MP-Fixed Event to report dynamic data and the type of the Data APDU is ScanReportInfoMPFixed</p> <p>[OR]</p> <p>The total size of the response does not exceed the maximum APDU size established by the specialization</p> |                                                               |                   |               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | [AND]<br>Continua PAN 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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Applicability</b>      | C_AG_OXP_000 AND (C_AG_OXP_182 OR C_AG_OXP_183 OR C_AG_OXP_184 OR C_AG_OXP_189)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Other PICS</b>         | C_AG_OXP_010, C_AG_OXP_031, C_AG_OXP_041, C_AG_OXP_053                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Take some measurements with the PHD under test.</li> <li>2. Wait until the PHD sends event reports with the data: <ol style="list-style-type: none"> <li>a. APDU Type = 0xE7 0x00</li> <li>b. Invoke-Id <ol style="list-style-type: none"> <li><input type="checkbox"/> Length = 2 bytes</li> <li><input type="checkbox"/> Value = &lt;Not relevant for this Test Case&gt;</li> </ol> </li> <li>c. CHOICE <ol style="list-style-type: none"> <li><input type="checkbox"/> Length = 2 bytes</li> <li><input type="checkbox"/> Value = 0x01 0x00 (Unconfirmed) OR 0x01 0x01 (Confirmed)</li> </ol> </li> <li>d. Obj-Handle <ol style="list-style-type: none"> <li><input type="checkbox"/> Length = 2 bytes</li> <li><input type="checkbox"/> Value = 0 (MDS object)</li> </ol> </li> <li>e. Event-Time <ol style="list-style-type: none"> <li><input type="checkbox"/> Length = 4 bytes</li> <li><input type="checkbox"/> Value = &lt;0xFF 0xFF 0xFF 0xFF&gt; If NOT C_AG_OXP_010</li> </ol> </li> <li>f. IF the data is from one person and uses a variable format event reporting, it must be: <ol style="list-style-type: none"> <li><input type="checkbox"/> Event-type = MDC_NOTI_SCAN_REPORT_VAR</li> <li><input type="checkbox"/> Event-info parameter = ScanReportInfoVar</li> </ol> </li> <li>g. IF the data is from one person and uses a fixed format event reporting, it must be: <ol style="list-style-type: none"> <li><input type="checkbox"/> Event-type = MDC_NOTI_SCAN_REPORT_FIXED</li> <li><input type="checkbox"/> Event-info parameter = ScanReportInfoFixed</li> </ol> </li> <li>h. IF the data is from multiple persons and uses a variable format event reporting, it must be: <ol style="list-style-type: none"> <li><input type="checkbox"/> Event-type = MDC_NOTI_SCAN_REPORT_MP_VAR</li> <li><input type="checkbox"/> Event-info parameter = ScanReportInfoMPVar</li> </ol> </li> <li>i. IF the data is from multiple persons and uses a fixed format event reporting, it must be: <ol style="list-style-type: none"> <li><input type="checkbox"/> Event-type = MDC_NOTI_SCAN_REPORT_MP_FIXED</li> <li><input type="checkbox"/> Event-info parameter = ScanReportInfoMPFixed</li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• All checked values are as specified in the test procedure.</li> <li>• The total size of the event report cannot exceed the maximum APDU size established by the specialization.</li> <li>• If the PHD does not support confirmed event reports (C_AG_OXP_053= FALSE), the PHD cannot send confirmed event reports.</li> <li>• If the PHD does not use variable event report (C_AG_OXP_189= FALSE ), the PHD cannot send variable event reports.</li> <li>• If the PHD supports multi-person event reports for one or more metric object (ScanReportPer* ) (C_AG_OXP_031= TRUE ), the PHD has to send multi-person event reports.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|              |                                                                                                                                                                                                                                                           |
+|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|              | <ul style="list-style-type: none"> <li>If C_AG_OXP_031= TRUE and MP event reports have been received, a pop-up will show the received measurements to make the operator identify if measurements have been correctly assigned to every person.</li> </ul> |
+| <b>Notes</b> |                                                                                                                                                                                                                                                           |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                    |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-011                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                    |
+| <b>TP label</b>          | MDS objects methods. PHD real-time clock (RTC). Absolute-Time                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                    |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                    |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | MDSMethod 4; M                                                | AbsTime 1;C        |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MDSMethod 6; M                                                | BaseTimOffset2 ; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The PHD replies to a Set-Time method with a rors-cmip-confirmed-action response. If the PHD supports Set-Time, it shall respond with a rors-cmip-confirmed-action, but the action-info-args is empty in this response.</p> <p>[AND]</p> <p>The PHD when responding to a Set-Base-Offset-Time method shall do so using a rors-cmip-confirmed-action response. The PHD indicates whether the Set-Base-Offset-Time command is valid by using the mds-time-capab-set-clock bit in the Mds-Time-Info attribute.</p> <p>[AND]</p> <p>If the PHD supports Set-Base-Offset-Time, it shall respond with a rors-cmip-confirmed-action, but the action-info-args is empty in this response.</p> <p>[AND]</p> <p>If the base time seconds field and base time fraction of a second field are set to 0x0 in the arguments of the Set-Base-Offset-Time action (these values being undefined in NTP), then only the offset to local time shall be set. If the base time (seconds field) is aligned with UTC (with an accuracy appropriate to the application), then this shall be designated by setting the mds-time-bo-time-utc-aligned bit in the Mds-Time-Info attribute.</p> <p>[AND]</p> <p>The base time should be set with respect to some reference time, and shall be set so that the offset to any local time can be accommodated by the maximum value of the offset field</p>                                                                                                                                                                                          |                                                               |                    |
+| <b>Applicability</b>     | (C_AG_OXP_007 OR C_AG_OXP_008) AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                    |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                    |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                    |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHG sends a Get request for the MDS object with an attribute-id-list set to 0 read all the attributes.</li> <li>Check the Value of the MdsTimeCapab bits in the MDS-Time-Info-Attribute <ul style="list-style-type: none"> <li><input type="checkbox"/> IF C_AG_OXP_009 = TRUE THEN check that mds-time-capab-real-time-clock(0) is set to TRUE indicating support of an RTC, ELSE this bit is set to FALSE.</li> <li><input type="checkbox"/> IF C_AG_OXP_008 = TRUE THEN check that mds-time-capab-set-clock(1) is set to TRUE indicating support of the Set Time Action ELSE this bit is set to FALSE.</li> <li><input type="checkbox"/> IF C_AG_OXP_014 = TRUE THEN check that mds-time-capab-bo-time(7) is set to TRUE indicating support of Base-Offset-Time and record the value of Base-Offset-Time attribute (MDC_ATTR_TIME_BO) ELSE this bit is set to FALSE indicating PHD does not support of a Base-Offset-Time.</li> </ul> </li> <li>IF Set Time Action is supported and C_AG_OXP_009 = TRUE: <ol style="list-style-type: none"> <li>The simulated PHG sends a SET action: <ul style="list-style-type: none"> <li><input type="checkbox"/> CHOICE = SetTimeInvoke</li> <li><input type="checkbox"/> action-type = MDC_ACT_SET_TIME</li> <li><input type="checkbox"/> the action-info-args are SetTimeInvoke <ul style="list-style-type: none"> <li>date-time = century ≤ 99, year ≤ 99, month ≤ 12, day ≤ 31, hour ≤ 24, minute ≤ 60, second ≤ 60, sec-fractions ≤ 100</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                                                               |                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• accuracy = 0</li> </ul> <ol style="list-style-type: none"> <li>b. The PHD under test response must be a rors-cmip-confirmed-action but the action-info-args shall be empty in this response.</li> <li>c. The simulated PHG sends a Get request for the MDS object with an attribute-id-list set to 0 read all the attributes. The Date-and-Time attribute value matches with the Absolute Time set in step 3.a.</li> </ol> <ol style="list-style-type: none"> <li>4. IF Set Time Action is supported and C_AG_OXP_014 = TRUE:           <ol style="list-style-type: none"> <li>a. The simulated PHG sends a SET action:               <ul style="list-style-type: none"> <li><input type="checkbox"/> CHOICE = SetBOTimeInvoke</li> <li><input type="checkbox"/> action-type = MDC_ACT_SET_BO_TIME</li> <li><input type="checkbox"/> the action-info-args are SetBOTimeInvoke                   <ul style="list-style-type: none"> <li>• date-time = bo-seconds = 0x00 0x00 0x00 0x00, bo-fractions = 0x00 0x00, bo-time-offset =&lt;original bo-time-offset&gt; + 60</li> </ul> </li> </ul> </li> <li>b. The PHD under test response must be a rors-cmip-confirmed-action but the action-info-args shall be empty in this response.</li> <li>c. The simulated PHG sends a Get request for the MDS object with an attribute-id-list set to 0 read all the attributes. The Base-Offset-Time attribute value matches with Base-Offset-Time set in step 4.a.</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• All checked values are as specified in the test procedure and check that the time has been set correctly in step 3.c or 4.c if that action was possible.</li> <li>• If Set Time Action and Base-Offset-Time is supported, then the value of bo-seconds and bo-fractions in step 2 and step 4.c shall be the same and only bo-time-offset is set.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                      |  |  |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|----------------------|--|--|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                      |  |  |
+| <b>TP label</b>          | MDS object events. PHD configuration event                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                      |  |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                      |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | MDSEvent 1; M                                                 | MetricClassAttr 1; M |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | ScanClassAttr 1; M                                            | StoreClassAttr 1; M  |  |  |
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-10419]                                        |                      |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | SchStoreObjIP 1; M                                            |                      |  |  |
+| <b>Test purpose</b>      | Check that:<br>MDS object sends the MDS-Configuration-Event with an Event-Info parameter of type ConfigReport. Only confirmed mode.<br>[AND]<br>Each object shall have a unique identifier assigned by the PHD                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                      |  |  |
+| <b>Applicability</b>     | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                      |  |  |
+| <b>Other PICS</b>        | C_AG_OXP_010, C_AG_OXP_040, C_AG_OXP_041, C_AG_OXP_042, C_AG_OXP_043, C_AG_OXP_046, C_AG_OXP_047                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |                      |  |  |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                      |  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>3. The PHD responds with a "Remote Operation Invoke   Confirmed Event Report" (roiv-cmip-confirmed-event-report) message:           <ol style="list-style-type: none"> <li>a. APDU Type               <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00</li> </ul> </li> </ol> </li> </ol> |                                                               |                      |  |  |
+
+- This value is for association request "prst" (PrstApdu).
+
+#### 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 PHG shall have the same invoke-id.
+
+#### c. obj-handle (EventReportArgumentSimple)
+
+- field- type = HANDLE
+- field-length = 2 bytes
+- field- value = 0x00 0x00
+- This obj-handle represents MDS-Object.
+
+#### d. event-time (EventReportArgumentSimple)
+
+- field- type = Relative Time
+- field-length = 4 bytes
+- If the PHD does not support relative time clock:
+- field-value =
+  - IF NOT C\_AG\_OXP\_010 THEN = 0xFF 0xFF 0xFF 0xFF
+
+#### e. event-type (EventReportArgumentSimple)
+
+- field- type = OID-Type
+- field-length = 2 bytes
+- field- value = 0x0D 0x1C (MDC\_NOTI\_CONFIG)
+
+#### f. config-report-id (ConfigReport)
+
+- field- type = ConfigId
+- field-length = 2 bytes
+- field- value = <between 0x00 0x01 and 0x7F 0xFF>
+
+#### g. obj-class (ConfigReport → ConfigObjectList (ConfigObject))
+
+- field- type = OID-Type
+- field-length = 2 bytes
+- field- value = 0x00 0x06 (MDC\_MOC\_VMO\_METRIC\_NU) or 0x00 0x09 (MDC\_MOC\_VMO\_METRIC\_SA-RT) or 0x00 0x05 (MDC\_MOC\_VMO\_METRIC\_ENUM) or 0x00 0x12 (MDC\_MOC\_SCAN\_CFG\_EPI) 0x00 0x13 (MDC\_MOC\_SCAN\_CFG\_PERI) or 0x00 0x3D (MDC\_MOC\_VMO\_PMSTORE) or 0x00 0x51 (MDC\_MOC\_VMO\_SCHEDSTORE ) or a value between 0xF000 and 0xFBFF
+- IF the PHD supports at least one numeric object (C\_AG\_OXP\_040=TRUE) then MDC\_MOC\_VMO\_METRIC\_NU shall be present, ELSE no numeric object is present.
+- IF the PHD supports at least one PM-Store object (C\_AG\_OXP\_041=TRUE) then MDC\_MOC\_VMO\_PMSTORE shall be present, ELSE no PM-Store object is present.
+- IF the PHD supports at least one RT-SA object (C\_AG\_OXP\_042=TRUE) then MDC\_MOC\_VMO\_METRIC\_SA-RT shall be present, ELSE no RT-SA object is present.
+- IF the PHD supports at least one enumerated object (C\_AG\_OXP\_043=TRUE) then MDC\_MOC\_VMO\_METRIC\_ENUM shall be present, ELSE no enumerated object is present.
+- IF the PHD supports at least one periodic scanner object (C\_AG\_OXP\_046=TRUE) then MDC\_MOC\_SCAN\_CFG\_PERI shall be present, ELSE no periodic scanner object is present.
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>▪ IF the PHD supports at least one episodic scanner object (C_AG_OXP_047=TRUE) then MDC_MOC_SCAN_CFG_EPI shall be present, ELSE no episodic scanner object is present.</li> <li>▪ IF PHD supports at least one schedule store object (C_AG_IP_012=TRUE OR C_AG_IP_013=TRUE OR C_AG_IP_014=TRUE) then MDC_MOC_VMO_SCHEDSTORE shall be present, ELSE no episodic scanner object is present.</li> </ul> <p>h. obj-handle ( ConfigReport → ConfigObjectList (ConfigObject))</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = &lt;Check that each object have a unique identifier and non -zero&gt;</li> </ul> <p>i. attribute-id ( ConfigReport → ConfigObjectList (ConfigObject)→Attribute List)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = &lt;between 0x0913 (2323) and 0x0A77 (2679)&gt; or &lt;between 0xF000(61440) and 0xFBFF(64511)&gt;</li> </ul>                                                                                                                                                                                                                                               |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• All checked values are as specified in the test procedure.</li> <li>• 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): <ul style="list-style-type: none"> <li>○ Pulse oximeter → 9216 octets</li> <li>○ Weighing scales → 896 octets</li> <li>○ Glucose meter → 5210 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ Blood pressure → 896 octets</li> <li>○ Thermometer → 896 octets</li> <li>○ Independent activity hub → 5120 octets</li> <li>○ Cardiovascular → 64512 octets or 6624 octets if the PHD supports Step Counter Profile</li> <li>○ Strength → 64512 octets</li> <li>○ Adherence monitor → 1024 octets</li> <li>○ Peak flow → 2030 octets</li> <li>○ Body composition analyser → 7730 octets</li> <li>○ Basic ECG/Simple ECG → 7168 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ Basic ECG/Heart rate → 1280 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ International normalized ratio → 896 octets or 64512 if the PHD supports PM-Store</li> <li>○ Insulin pump → 7168 octets or 5120 if PHD supports PM-Store</li> <li>○ Continuous glucose monitor → 896 octets or 5120 if PHD supports PM-Store.</li> <li>○ Power status monitor → 940 octets for Simple PSM profile or 1660 for Advanced PSM profile</li> </ul> </li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                 |                                                |                                                               |
+|-----------------|------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/OXP/DIM/BV-013                      |                                                               |
+| <b>TP label</b> | PM-Store object methods. Clear-Segments method |                                                               |
+| <b>Coverage</b> | <b>Spec</b>                                    | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                 | <b>Testable</b>                                | PM-StoreMeth 1; O      PM-StoreMeth 2; C                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                             |                             |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|-----------------------------|
+| <b>items</b>             | PM-StoreMeth 8; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | PersStoreMtrDatTransf 20; M | PersStoreMtrDatTransf 21; M |
+|                          | PersStoreMtrDatTransf 22; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | PersStoreMtrDatTransf 23; M | PM-StoreMeth 6; M           |
+|                          | PM-StoreMeth 20; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | PM-StoreMeth 21; C          | PM-StoreMeth 7; M           |
+|                          | PM-StoreMeth 30; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | PM-StoreMeth 31; M          |                             |
+| <b>Spec</b>              | [b-ITU-T H.810 (2015)]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                             |                             |
+| <b>Testable items</b>    | Communication 1; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                             |                             |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The PHD may support PM-segment clearing. If the PHD supports this function (indicated by the pmsc-clear-segm-all-sup, pmsc-clear-segm-by-list-sup, and pmsc-clear-segm-by-time-sup flags in the PM-Store-Capab attribute being set), then it shall support clearing all segments (pmsc-clear-segm-all-sup)</p> <p>[AND]</p> <p>PHD supports the Clear-Segment (all segments) method and it responds to Clear-Segment requests with a Data APDU with an operation type rors-cmip-confirmed-action</p> <p>[AND]</p> <p>According to PM-Store-Capab attribute this method removes all entries from the specified PM-Segment, leaving it empty, or it removes the defined PM-Segment completely</p> <p>[AND]</p> <p>The Instance-Number of all other PM-Segments is unaffected by clearing a segment</p> <p>[AND]</p> <p>If any of the selected segments are cleared, success (rors) shall be reported. However, success does not necessarily mean that all targeted segments were actually cleared (and potentially removed) since there maybe a subset that were protected or enabled.</p> <p>[AND]</p> <p>Otherwise, the return code shall be MDC_RET_CODE_UNKNOWN which indicates that only PHD protected segments where encountered during the operation</p>                         |                             |                             |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_071 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                             |                             |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                             |                             |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state and the PHD has at least one PM-Segment with data stored.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                             |                             |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Make sure the PHD under test is not taking measurements which are stored in PM-Segments.</li> <li>2. 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.</li> <li>3. The PHD under test issues a GET response with the PM-Store attributes. Record the values of the PM-Store-Capab attribute. <ol style="list-style-type: none"> <li>a. PM-Store-Capab: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li> <li><input type="checkbox"/> attribute-type = PmStoreCapab</li> <li><input type="checkbox"/> attribute-value = Record the value of bit 10 (Indicates that PM-Segments in the SegmSelection data type can be cleared by segment selection –all segments). This bit shall be set to 1.</li> </ul> </li> </ol> </li> <li>4. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection set to all-segments.</li> <li>5. The PHD issues a response (rors-cmip-confirmed-action) with the PM-Segment attributes it supports.</li> <li>6. The simulated PHG sends a Clear-Segment: <ol style="list-style-type: none"> <li>a. Data APDU</li> </ol> </li> </ol> |                             |                             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> <li><input type="checkbox"/> SegmSelection = all-segments</li> </ul> <p>7. If the PHD does not protect all segments, the PHD under test operation response will be:</p> <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Response   Confirmed Action</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> <li><input type="checkbox"/> Check the invoke-id of the response is mirrored from the request.</li> </ul> </li> </ul> <p>8. If the PHD does protect all segments, the PHD under test operation response will be:</p> <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Roer</li> <li><input type="checkbox"/> ErrorResult = no-allowed-by-object (24) and return code shall be MDC_RET_CODE_UNKNOWN.</li> <li><input type="checkbox"/> Check the invoke-id of the response is mirrored from the request</li> </ul> </li> </ul> <p>9. Delay</p> <p>10. If the PHD has sent the confirmation in step 7, the simulated PHG sends a request for the PM-Segment Data to obtain all the segments:</p> <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> SegmSelection = &lt;Instance number of the selected PM-Segment that contained data before the clear-segment action&gt;</li> </ul> </li> </ul> <p>11. The PHD under test issues an action response with the Data:</p> <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Response   Confirmed Action</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> TrigSegmXferRsp = <ul style="list-style-type: none"> <li>• IF pmsc-clear-segm-remove of the PM-Store-Capab attribute is NOT set then <ul style="list-style-type: none"> <li><input type="checkbox"/> TrigSegmXferRsp = tsxr-fail-segm-empty</li> </ul> </li> <li>• ELSE then <ul style="list-style-type: none"> <li><input type="checkbox"/> TrigSegmXferRsp = tsxr-fail-no-such-segment</li> </ul> </li> </ul> </li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 7, the PHD must send a confirmation if the PHD does not protect any segments, otherwise the PHD shall send a roer message (step 8).</li> <li>• If the PHD sends the confirmation in step 7, the PHD shall send the response specified in step 11 at least for a segment.</li> <li>• After APDU received by the simulated PHG in step 11, the PHD does not send any message of type "Segment-data-event" with data stored.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                             |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-013_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                             |
+| <b>TP label</b>          | PM-Store object methods. Clear-Segments List method                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                             |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                             |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | PM-StoreMeth 1; O                                             | PM-StoreMeth 2; C           |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | PM-StoreMeth 8; O                                             | PersStoreMtrDatTransf 20; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | PersStoreMtrDatTransf 22; O                                   | PersStoreMtrDatTransf 23; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | PersStoreMtrDatTransf 24; M                                   | PM-StoreMeth 6; M           |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If the PHD supports the Clear-Segment (list of segments) method, then it responds to Clear-Segment requests with a Data APDU with an operation type rors-cmip-confirmed-action</p> <p>[AND]</p> <p>According to PM-Store-Capab attribute this method removes all entries from the specified PM-Segment, leaving it empty, or it removes the defined PM-Segment completely</p> <p>[AND]</p> <p>The Instance-Number of all other PM-Segments is unaffected by clearing a segment</p> <p>[AND]</p> <p>The PHD may support PM-segment clearing. If the PHD supports this function(indicated by the pmsc-clear-segm-all-sup, pmsc-clear-segm-by-list-sup, and pmsc-clear-segm-by-time-sup flags in the PM-Store-Capab attribute being set) then it may support clearing a particular list of segments (pmsc-clear-segm-by-list-sup)</p> <p>[AND]</p> <p>If the PHD supports the segm-id-list choice in the SegmSelection action-info-args of the Clear-Segments method, the PHD shall set the pmsc-clear-segm-by-list-sup flag in the PM-Store-Capab attribute.</p> <p>[AND]</p> <p>If the PHG invokes the Clear-Segments method but the PHD does not support the particular action (list of segments or range of segments), then the PHD shall respond with a roer DataApdu with an RoerErrorValue of "not-allowed-by-object".</p> |                                                               |                             |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_071 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                             |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                             |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state and the PHD has at least two PM-Segments with data stored.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                             |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Make sure the PHD is not taking measures which are stored in PM-Segments.</li> <li>2. 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.</li> <li>3. The PHD issues a GET response with the PM-Store attributes, check the values of the PM-Store-Capab attribute: <ol style="list-style-type: none"> <li>a. PM-Store-Capab: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li> <li><input type="checkbox"/> attribute-type = PmStoreCapab</li> <li><input type="checkbox"/> attribute-value = Record the value of bit 7 (Indicates that PM-Segments in the SegmSelection data type can be cleared by defining a list)</li> </ul> </li> </ol> </li> <li>4. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection set to all-segments.</li> <li>5. The PHD issues a response (rors-cmip-confirmed-action) with the PM-Segment attributes it supports.</li> </ol> <p>IF bit 7 of PmStoreCapab was set:</p>                                                                                                                                                                                               |                                                               |                             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ol style="list-style-type: none"> <li>6. The simulated PHG sends a Clear-Segment: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> <li><input type="checkbox"/> SegmSelection = segm-id-list (list of integers containing 2 of the instance numbers obtained in step 5)</li> </ul> </li> </ol> </li> <li>7. The PHD under test operation response: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Response   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> </ul> </li> </ol> </li> <li>8. Delay.</li> <li>9. The simulated PHG sends a request for the PM-Segment Data of one of the cleared PM-Segments: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> SegmSelection = &lt;Instance number of the selected PM-Segment that contained data before the clear-segment action&gt;</li> </ul> </li> </ol> </li> <li>10. The PHD issues an action response with the Data <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> TrigSegmXferRsp = <ul style="list-style-type: none"> <li>▪ IF pmsc-clear-segm-remove is NOT set then <ul style="list-style-type: none"> <li>o TrigSegmXferRsp = tsxr-fail-segm-empty</li> </ul> </li> <li>▪ ELSE then <ul style="list-style-type: none"> <li>o TrigSegmXferRsp = tsxr-fail-no-such-segment</li> </ul> </li> </ul> </li> </ul> </li> </ol> </li> </ol> <p>IF bit 7 of PMStoreCapab was NOT set</p> <ol style="list-style-type: none"> <li>11. The simulated PHG sends a Clear-Segment: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> <li><input type="checkbox"/> SegmSelection = segm-id-list (list of integers containing 2 of the instance numbers obtained in step 5)</li> </ul> </li> </ol> </li> <li>12. The PHD under test operation response: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Roer</li> <li><input type="checkbox"/> ErrorResult = not-allowed-by-object (24)</li> </ul> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 7, the PHD must send a confirmation</li> <li>• The last APDU received by the simulated PHG has no data</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|              |  |
+|--------------|--|
+| <b>Notes</b> |  |
+|--------------|--|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                             |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-013_B                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                             |
+| <b>TP label</b>          | PM-Store object methods. Clear-Segments Time Range method 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                             |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                             |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PM-StoreMeth 1; O                                             | PM-StoreMeth 2; C           |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | PM-StoreMeth 8; O                                             | PersStoreMtrDatTransf 20; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | PersStoreMtrDatTransf 22; O                                   | PersStoreMtrDatTransf 23; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               | PM-StoreMeth 6; M           |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               | PersStoreMtrDatTransf 21; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               | PM-StoreMeth 19; M          |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If PHD supports the Clear-Segment (time range) method, then it responds to Clear-Segment requests with a Data APDU with an operation type rors-cmip-confirmed-action</p> <p>[AND]</p> <p>According to PM-Store-Capab attribute this method removes all entries from the specified PM-Segment, leaving it empty, or it removes the defined PM-Segment completely</p> <p>[AND]</p> <p>The Instance-Number of all other PM-Segments is unaffected by clearing a segment</p> <p>[AND]</p> <p>For PM-Segments cleared using the by time method, only PM-Segments having Segment-Start-Abs-Time and Segment-End-Abs-Time fields entirely within the specified time period are cleared.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                             |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_071 AND C_AG_OXP_072 AND C_AG_OXP_009 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                             |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                             |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state and the PHD supports at least one PM-Segment with data stored.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                             |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Make sure the PHD under test is not taking measurements which are stored in PM-Segments.</li> <li>2. 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.</li> <li>3. The PHD under test issues a GET response with the PM-Store attributes, record the values of the PM-Store-Capab attribute: <ol style="list-style-type: none"> <li>a. PM-Store-Capab: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li> <li><input type="checkbox"/> attribute-type = PmStoreCapab</li> <li><input type="checkbox"/> attribute-value = Record the value of bit 8 (Indicates that PM-Segments in the SegmSelection data type can be cleared by defining an AbsTimeRange)</li> </ul> </li> </ol> </li> <li>4. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection set to all-segments.</li> <li>5. The PHD issues a response (rors-cmip-confirmed-action) with the PM-Segment attributes it supports, record the attributes "Segment-Start-Abs-Time" and "Segment-End-Abs-Time" of every PM-Segment.</li> </ol> <p>IF bit 8 of PMStoreCapab was set:</p> <ol style="list-style-type: none"> <li>6. The simulated PHG sends a Clear-Segment: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> </ul> </li> </ol> </li> </ol> |                                                               |                             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> SegmSelection = abs-time-range, selecting a range with its boundaries set to an earlier date of any of the existing segments.</li> </ul> <p>7. The PHD under test operation response:<br/> IF NOT Protocol Version 3</p> <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Roer</li> <li><input type="checkbox"/> ErrorResult = no-such-action (9)</li> </ul> </li> </ul> <p>ELSE</p> <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Response   Confirmed Action</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> </ul> </li> </ul>                                                                               |
+| <b>Pass/Fail criteria</b> | In step 7 the PHD must send the specified error.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              | <p>Error code was not clearly defined in the spec.</p> <p>In the new edition of [ISO/IEEE 11073-20601-2015A], the clear-segment using time range has been clarified. "For PM-segments cleared using the by time method, only PM-segments having Segment-Start-Abs-Time and Segment-End-Abs-Time fields entirely within the specified time period are cleared.", but if the PHG sends a Clear-Segment but the segment has not a Segment-Start-Abs-Time and Segment-End-Abs-Time within the specified time-period, the PHD will send a Roer message.</p> <p>At this point, it would be up to the PHD what error code (Roer message) to send (No-such-action, not-allowed-by-object, or both). If one wants to clear the segment due to all the internal timestamps that were saved in the segment as falling inside the given time period, then the PHD could do that. Returning an error is also possible.</p> |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                             |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/EXP/DIM/BV-013_C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                             |
+| <b>TP label</b>          | PM-Store object methods. Clear-Segments Time Range method 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                             |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                             |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | PM-StoreMeth 1; O                                             | PM-StoreMeth 2; C           |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | PM-StoreMeth 8; O                                             | PersStoreMtrDatTransf 20; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | PersStoreMtrDatTransf 22; O                                   | PersStoreMtrDatTransf 23; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If PHD supports the Clear-Segment (time range) method, then it responds to Clear-Segment requests with a Data APDU with an operation type rors-cmip-confirmed-action</p> <p>[AND]</p> <p>According to PM-Store-Capab attribute this method removes all entries from the specified PM-Segment, leaving it empty, or it removes the defined PM-Segment completely</p> <p>[AND]</p> <p>The Instance-Number of all other PM-Segments is unaffected by clearing a segment</p> <p>[AND]</p> <p>For PM-Segments cleared using the by time method, only PM-Segments having Segment-Start-Abs-Time and Segment-End-Abs-Time fields entirely within the specified time period are cleared.</p> |                                                               |                             |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_071 AND C_AG_OXP_072 AND C_AG_OXP_009 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                             |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                             |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state and the PHD has at least one PM-Segment with data stored.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make sure the PHD is not taking measures which are stored in PM-Segments.</li> <li>2. 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.</li> <li>3. The PHD issues a GET response with the PM-Store attributes, record the values of the PM-Store-Capab attribute: <ol style="list-style-type: none"> <li>a. PM-Store-Capab: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li> <li><input type="checkbox"/> attribute-type = PmStoreCapab</li> <li><input type="checkbox"/> attribute-value = Record the value of bit 8 (Indicates that PM-Segments in the SegmSelection data type can be cleared by defining an AbsTimeRange)</li> </ul> </li> </ol> </li> <li>4. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection set to all-segments.</li> <li>5. The PHD issues a response (rors-cmip-confirmed-action) with the PM-Segment attributes it supports, record the attributes "Segment-Start-Abs-Time" and "Segment-End-Abs-Time" of every PM-Segment.</li> </ol> <p>IF bit 8 of PMStoreCapab was set:</p> <ol style="list-style-type: none"> <li>6. The simulated PHG sends a Clear-Segment: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> <li><input type="checkbox"/> SegmSelection = abs-time-range, selecting a range with its boundaries set to a later date of any of the existing segments.</li> </ul> </li> </ol> </li> <li>7. The PHD under test operation response:</li> </ol> <p>IF NOT Protocol Version 3</p> <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Roer</li> <li><input type="checkbox"/> ErrorResult = no-such-action (9)</li> </ul> </li> </ol> <p>ELSE</p> <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Response   Confirmed Action</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> </ul> </li> </ol> |
+| <b>Pass/Fail criteria</b> | In step 7 the PHD must send the specified error.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              | See Note for test case TP/PLT/PHD/OXP/DIM/BV-013_B.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                     |                                                                                                                                                                                         |                                                               |                             |
+|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------------|
+| <b>TP Id</b>        | TP/PLT/PHD/OXP/DIM/BV-013_D                                                                                                                                                             |                                                               |                             |
+| <b>TP label</b>     | PM-Store object methods. Clear-Segments Time Range method 3                                                                                                                             |                                                               |                             |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                             | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                             |
+|                     | <b>Testable items</b>                                                                                                                                                                   | PM-StoreMeth 1; O                                             | PM-StoreMeth 2; C           |
+|                     |                                                                                                                                                                                         | PM-StoreMeth 8; O                                             | PersStoreMtrDatTransf 20; M |
+| <b>Test purpose</b> | Check that:<br><br>If PHD supports the Clear-Segment (time range) method, then it responds to Clear-Segment requests with a Data APDU with an operation type rors-cmip-confirmed-action |                                                               |                             |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | <p>[AND]</p> <p>According to PM-Store-Capab attribute this method removes all entries from the specified PM-Segment, leaving it empty, or it removes the defined PM-Segment completely</p> <p>[AND]</p> <p>The Instance-Number of all other PM-Segments is unaffected by clearing a segment</p> <p>[AND]</p> <p>For PM-Segments cleared using the by time method, only PM-Segments having Segment-Start-Abs-Time and Segment-End-Abs-Time fields entirely within the specified time period are cleared.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_071 AND C_AG_OXP_072 AND C_AG_OXP_009 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state and the PHD has at least one PM-Segment with data stored.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"><li>1. Make sure the PHD is not taking measures which are stored in PM-Segments.</li><li>2. 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.</li><li>3. The PHD issues a GET response with the PM-Store attributes, record the values of the PM-Store-Capab attribute:<ol style="list-style-type: none"><li>a. PM-Store-Capab:<ul style="list-style-type: none"><li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li><li><input type="checkbox"/> attribute-type = PmStoreCapab</li><li><input type="checkbox"/> attribute-value = Record the value of bit 8 (Indicates that PM-Segments in the SegmSelection data type can be cleared by defining an AbsTimeRange)</li></ul></li></ol></li><li>4. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection set to all-segments.</li><li>5. The PHD issues a response (rors-cmip-confirmed-action) with the PM-Segment attributes it supports, record the attributes "Segment-Start-Abs-Time" and "Segment-End-Abs-Time" of every PM-Segment.</li></ol> <p>IF bit 8 oft PMStoreCapab was set:</p> <ol style="list-style-type: none"><li>6. The simulated PHG sends a Clear-Segment:<ol style="list-style-type: none"><li>a. Data APDU<ul style="list-style-type: none"><li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li><li><input type="checkbox"/> HANDLE = obj-handle</li><li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li><li><input type="checkbox"/> SegmSelection = abs-time-range, selecting a range with one of its boundaries set to an earlier date of any of the existing segments and the other set to date contained between Segment-Start-Abs-Time and Segment-End-Abs-Time of one of the PM-Segments</li></ul></li></ol></li><li>7. The PHD under test operation response:<p>IF NOT Protocol Version 3</p><ol style="list-style-type: none"><li>a. Data APDU<ul style="list-style-type: none"><li><input type="checkbox"/> Type = Roer</li><li><input type="checkbox"/> ErrorResult = no-such-action (9)</li></ul></li></ol><p>Else</p><ol style="list-style-type: none"><li>b. Data APDU<ul style="list-style-type: none"><li><input type="checkbox"/> Type = Response   Confirmed Action</li></ul></li><li>c. HANDLE = obj-handle<ul style="list-style-type: none"><li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li></ul></li></ol></li></ol> |
+
+|                           |                                                     |
+|---------------------------|-----------------------------------------------------|
+| <b>Pass/Fail criteria</b> | In step 7 the PHD must send the specified error.    |
+| <b>Notes</b>              | See Note for test case TP/PLT/PHD/OXP/DIM/BV-013_B. |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                             |                             |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------------|-----------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-013_E                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                             |                             |
+| <b>TP label</b>          | PM-Store object methods. Clear-Segments Time Range method 4                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                             |                             |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                             |                             |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | PM-StoreMeth 1; O                                             | PM-StoreMeth 2; C           | PM-StoreMeth 6; M           |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | PM-StoreMeth 8; O                                             | PersStoreMtrDatTransf 20; M | PersStoreMtrDatTransf 21; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | PersStoreMtrDatTransf 22; O                                   | PersStoreMtrDatTransf 23; M | PM-StoreMeth 19; M          |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If PHD supports the Clear-Segment (time range) method, then it responds to Clear-Segment requests with a Data APDU with an operation type rors-cmip-confirmed-action</p> <p>[AND]</p> <p>According to PM-Store-Capab attribute this method removes all entries from the specified PM-Segment, leaving it empty, or it removes the defined PM-Segment completely</p> <p>[AND]</p> <p>The Instance-Number of all other PM-Segments is unaffected by clearing a segment</p> <p>[AND]</p> <p>For PM-Segments cleared using the by time method, only PM-Segments having Segment-Start-Abs-Time and Segment-End-Abs-Time fields entirely within the specified time period are cleared.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                             |                             |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_071 AND C_AG_OXP_072 AND C_AG_OXP_009 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                             |                             |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                             |                             |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state and the PHD has at least one PM-Segment with data stored.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                             |                             |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Make sure the PHD is not taking measures which are stored in PM-Segments.</li> <li>2. 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.</li> <li>3. The PHD issues a GET response with the PM-Store attributes, record the values of the PM-Store-Capab attribute: <ol style="list-style-type: none"> <li>a. PM-Store-Capab: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li> <li><input type="checkbox"/> attribute-type = PmStoreCapab</li> <li><input type="checkbox"/> attribute-value = Record the value of bit 8 (Indicates that PM-Segments in the SegmSelection data type can be cleared by defining an AbsTimeRange)</li> </ul> </li> </ol> </li> <li>4. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection set to all-segments.</li> <li>5. The PHD issues a response (rors-cmip-confirmed-action) with the PM-Segment attributes it supports, record the attributes "Segment-Start-Abs-Time" and "Segment-End-Abs-Time" of every PM-Segment.</li> </ol> <p>IF bit 8 of PMStoreCapab was set:</p> <ol style="list-style-type: none"> <li>6. The simulated PHG sends a Clear-Segment: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> </ul> </li> </ol> </li> </ol> |                                                               |                             |                             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><input type="checkbox"/> SegmSelection = abs-time-range, selecting a range with one of its boundaries set between Segment-Start-Abs-Time and Segment-End-Abs-Time of one of the PM-Segments and the other set to a later date of any of the existing segments</p> <p>7. The PHD under test operation response:</p> <p>IF NOT Protocol Version 3</p> <p>a. Data APDU</p> <p><input type="checkbox"/> Type = Roer</p> <p><input type="checkbox"/> ErrorResult = no-such-action (9)</p> <p>ELSE</p> <p>b. Data APDU</p> <p><input type="checkbox"/> Type = Response   Confirmed Action</p> <p>c. HANDLE = obj-handle</p> <p><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</p> |
+| <b>Pass/Fail criteria</b> | In step 7 the PHD must send the specified error.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes</b>              | See Note for test case TP/PLT/PHD/OXP/DIM/BV-013_B.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                             |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-013_F                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                             |
+| <b>TP label</b>          | PM-Store object methods. Clear-Segments Time Range method 5                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                             |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                             |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | PM-StoreMeth 1; O                                             | PM-StoreMeth 2; C           |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | PM-StoreMeth 8; O                                             | PersStoreMtrDatTransf 20; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | PersStoreMtrDatTransf 22; O                                   | PersStoreMtrDatTransf 23; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If PHD supports the Clear-Segment (time range) method, then it responds to Clear-Segment requests with a Data APDU with an operation type rors-cmip-confirmed-action</p> <p>[AND]</p> <p>According to PM-Store-Capab attribute this method removes all entries from the specified PM-Segment, leaving it empty, or it removes the defined PM-Segment completely</p> <p>[AND]</p> <p>The Instance-Number of all other PM-Segments is unaffected by clearing a segment</p> <p>[AND]</p> <p>For PM-Segments cleared using the by time method, only PM-Segments having Segment-Start-Abs-Time and Segment-End-Abs-Time fields entirely within the specified time period are cleared.</p> |                                                               |                             |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_071 AND C_AG_OXP_072 AND C_AG_OXP_009 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                             |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                             |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state and the PHD has at least one PM-Segment with data stored.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                             |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>Make sure the PHD is not taking measures which are stored in PM-Segments.</li> <li>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.</li> <li>The PHD issues a GET response with the PM-Store attributes, record the values of the PM-Store-Capab attribute: <ol style="list-style-type: none"> <li>PM-Store-Capab:</li> </ol> </li> </ol>                                                                                                                                                                                                                                 |                                                               |                             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li> <li><input type="checkbox"/> attribute-type = PmStoreCapab</li> <li><input type="checkbox"/> attribute-value = Record the value of bit 8 (Indicates that PM-Segments in the SegmSelection data type can be cleared by defining an AbsTimeRange)</li> </ul> <p>4. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection set to all-segments.</p> <p>5. The PHD issues a response (rors-cmip-confirmed-action) with the PM-Segment attributes it supports, record the attributes "Segment-Start-Abs-Time" and "Segment-End-Abs-Time" of every PM-Segment.</p> <p>IF bit 8 of PMStoreCapab was set:</p> <p>6. The simulated PHG sends a Clear-Segment:</p> <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> <li><input type="checkbox"/> SegmSelection = abs-time-range, selecting a range with its boundaries set to Segment-Start-Abs-Time and Segment-End-Abs-Time of one of the PM-Segments</li> </ul> </li> </ul> <p>7. The PHD under test operation response:</p> <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Response   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> </ul> </li> </ul> <p>8. Delay.</p> <p>9. The simulated PHG sends a request for the PM-Segment Data of one of the cleared PM-Segments:</p> <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> SegmSelection = &lt;Instance number of the selected PM-Segment that contained data before the clear-segment action in step 6&gt;</li> </ul> </li> </ul> <p>10. The PHD issues an action response with the Data:</p> <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> TrigSegmXferRsp = <ul style="list-style-type: none"> <li>▪ IF pmsc-clear-segm-remove is NOT set then <ul style="list-style-type: none"> <li>o TrigSegmXferRsp = tsxr-fail-segm-empty</li> </ul> </li> <li>▪ ELSE then <ul style="list-style-type: none"> <li>o TrigSegmXferRsp = tsxr-fail-no-such-segment</li> </ul> </li> </ul> </li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 7 the PHD must send a confirmation</li> <li>• In step 10 the TrigSegmXferRsp must be the specified</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              | See Note for test case TP/PLT/PHD/OXP/DIM/BV-013_B.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                              |                             |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|-----------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-013_G                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                              |                             |
+| <b>TP label</b>          | PM-Store object methods. Clear-Segments Time Range method 6                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                              |                             |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-20601-2016C] |                             |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | PM-StoreMeth 1; O            | PM-StoreMeth 2; C           |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PM-StoreMeth 8; O            | PersStoreMtrDatTransf 20; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PersStoreMtrDatTransf 22; O  | PersStoreMtrDatTransf 23; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PM-StoreMeth 23; C           | PersStoreMtrDatTransf 24; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If PHD supports the Clear-Segment (time range) method, then it responds to Clear-Segment requests with a Data APDU with an operation type rors-cmip-confirmed-action</p> <p>[AND]</p> <p>According to PM-Store-Capab attribute this method removes all entries from the specified PM-Segment, leaving it empty, or it removes the defined PM-Segment completely</p> <p>[AND]</p> <p>The Instance-Number of all other PM-Segments is unaffected by clearing a segment</p> <p>[AND]</p> <p>The PHD may support PM-segment clearing. If the PHD supports this function(indicated by the pmsc-clear-segm-all-sup, pmsc-clear-segm-by-list-sup, and pmsc-clear-segm-by-time-sup flags in the PM-Store-Capab attribute being set) then it may support the time range selection criteria (pmsc-clear-segm-by-time-sup)</p> <p>[AND]</p> <p>For PM-Segments cleared using the by time method, only PM-Segments having Segment-Start-Abs-Time and Segment-End-Abs-Time fields entirely within the specified time period are cleared.</p> <p>[AND]</p> <p>If the PHD supports the abs-time-range choice in the SegmSelection action-info-args of the Clear-Segments method, the PHD shall set the pmsc-clear-segm-by-time-sup flag in the PM-Store-Capab attribute.</p> <p>[AND]</p> <p>If the PHG invokes the Clear-Segments method but the PHD does not support the particular action (list of segments or range of segments), then the PHD shall respond with a roer DataApdu with a RoerErrorValue of "not-allowed-by-object".</p> |                              |                             |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_071 AND C_AG_OXP_009 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                              |                             |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                              |                             |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state and the PHD has at least one PM-Segment with data stored.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                              |                             |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Make sure the PHD is not taking measures which are stored in PM-Segments.</li> <li>2. 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.</li> <li>3. The PHD issues a GET response with the PM-Store attributes, record the values of the PM-Store-Capab attribute: <ol style="list-style-type: none"> <li>a. PM-Store-Capab: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li> <li><input type="checkbox"/> attribute-type = PmStoreCapab</li> <li><input type="checkbox"/> attribute-value = Record the value of bit 8 (Indicates that PM-Segments in the SegmSelection data type can be cleared by defining an AbsTimeRange)</li> </ul> </li> </ol> </li> </ol> <p>IF bit 8 of PMStoreCapab was set:</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                              |                             |
+
+4. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection set to all-segments.
+  5. The PHD issues a response (rors-cmip-confirmed-action) with the PM-Segment attributes it supports, record the attributes "Segment-Start-Abs-Time" and "Segment-End-Abs-Time" of every PM-Segment.
+  6. The simulated PHG sends a Clear-Segment:
+    - a. Data APDU
+      - Type = Invoke | Confirmed Action
+      - HANDLE = obj-handle
+      - Action = MDC\_ACT\_SEG\_CLEAR
+      - SegmSelection = abs-time-range, selecting a range with its boundaries set to include inside from Segment-Start-Abs-Time to Segment-End-Abs-Time of one of the PM-Segments
+  7. The PHD under test operation response:
+    - a. Data APDU
+      - Type = Response | Confirmed Action
+      - HANDLE = obj-handle
+      - Action = MDC\_ACT\_SEG\_CLEAR
+  8. Delay.
+  9. The simulated PHG sends a request for the PM-Segment Data of one of the cleared PM-Segments:
+    - a. Data APDU
+      - Type = Invoke | Confirmed Action
+      - HANDLE = obj-handle
+      - Action = MDC\_ACT\_SEG\_TRIG\_XFER
+      - SegmSelection = <Instance number of the selected PM-Segment that contained data before the clear-segment action in step 6>
+  10. The PHD issues an action response with the Data
+    - a. Data APDU
+      - Type = Invoke | Confirmed Action
+      - HANDLE = obj-handle
+      - Action = MDC\_ACT\_SEG\_TRIG\_XFER
+      - TrigSegmXferRsp =
+        - IF pmsc-clear-segm-remove is NOT set then
+          - o TrigSegmXferRsp = tsxr-fail-segm-empty
+        - ELSE then
+          - o TrigSegmXferRsp = tsxr-fail-no-such-segment
+- IF bit 8 of PMStoreCapab was NOT set
+11. Simulated PHG sends a Clear-Segment:
+    - a. Data APDU
+      - Type = Invoke | Confirmed Action,
+      - HANDLE = obj-handle
+      - Action = MDC\_ACT\_SEG\_CLEAR
+      - SegmSelection = abs-time-range, selecting a range with its boundaries set to the absolute minimum of Absolute-Time type and to the absolute maximum of the Absolute-Time type
+  12. The PHD under test operation response:
+
+|                           |                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>IF NOT Protocol Version 3</p> <p>a. Data APDU</p> <p><input type="checkbox"/> Type = Roer</p> <p><input type="checkbox"/> ErrorResult = no-such-action (9)</p> <p>Else</p> <p>b. Data APDU</p> <p><input type="checkbox"/> Type = Response   Confirmed Action</p> <p>c. HANDLE = obj-handle</p> <p><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>In step 7 the PHD must send a confirmation</li> <li>In step 10 the TrigSemgXferRsp must be the specified</li> <li>If the PHD does not support Clear-Segment by time, the PHD must send a roer (not-allowed-by -object) message.</li> </ul>                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                               |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                     |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OPX/DIM/BV-014                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                     |
+| <b>TP label</b>          | PM-Store object methods. Clear-Segments method 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | PM-StoreMeth 7; M                                             | StoreClassAttr 6; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If all of the selected segments fail to clear (reason being protected or in Enabled state, the PHD shall reply with a not-allowed-by-object error (roer). The return code shall be set to MDC_RET_CODE_OBJ_BUSY if any of the segments failed due to being in Enabled state.</p> <p>[AND]</p> <p>Deletion of all selected PM-segments is not guaranteed by this method. While a PM-segment has the Operational-State attribute set to enabled it will not perform the requested deletion.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                     |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_000 AND C_AG_OXP_071 AND C_AG_OXP_018                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                     |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                     |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                     |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>Take measurements with the PHD of a value that is stored on a PM-Segment.</li> <li>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.</li> <li>The PHD issues a GET response with the PM-Store attributes.</li> <li>The simulated PHG shall send a Get-Segment-Info object action with segmSelection set to all-segments to check what Segments are in use.</li> <li>The simulated PHG sends a Clear-Segment to all segments: <ol style="list-style-type: none"> <li>Data APDU <p><input type="checkbox"/> Type = Invoke   Confirmed Action,</p> <p><input type="checkbox"/> HANDLE = obj-handle</p> <p><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</p> <p><input type="checkbox"/> SegmSelection = all-segments</p> </li> </ol> </li> <li>The PHD under test operation response: <ol style="list-style-type: none"> <li>Data APDU <p><input type="checkbox"/> Type = roer</p> <p><input type="checkbox"/> value = not-allowed-by-object</p> </li> </ol> </li> </ol> |                                                               |                     |
+
+|                           |                                                                                                                                             |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> value-returncode = MDC_RET_CODE_OBJ_BUSY                                                                           |
+| <b>Pass/Fail criteria</b> | The PHD must respond with the specified error.                                                                                              |
+| <b>Notes</b>              | The purpose of this test is to check that it is not possible to clear a segment that is in use, i.e. operational-state set to 1 by the PHD. |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                              |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/OPX/DIM/BV-015                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                              |  |
+| <b>TP label</b>          | PM-Store Object. Get-Segment-Id-List method                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                              |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | PM-StoreMeth 35              |  |
+| <b>Test purpose</b>      | Check that:<br>The PHD may support the Get-Segment-Id-List method<br>[AND]<br>Values in the PM-Store-Capab attribute represent that support<br>[AND]<br>PHD response is as expected                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                              |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_041 AND C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                              |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                              |  |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                              |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>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.</li> <li>2. The PHD under test issues a GET response with the PM-Store attributes it supports, check the values of the PM-Store-Capab attribute: <ol style="list-style-type: none"> <li>a. Data APDU <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li> <li><input type="checkbox"/> attribute-type = PMStoreCapab</li> <li><input type="checkbox"/> attribute-value = one or more of the following bits may be set: <ul style="list-style-type: none"> <li>▪ pmsc-var-no-of-segm (0)</li> <li>▪ pmsc-segm-id-list-select(3)</li> <li>▪ pmsc-epi-seg-entries(4)</li> <li>▪ pmsc-peri-seg-entries(5)</li> <li>▪ pmsc-abs-time-select(6)</li> <li>▪ pmsc-clear-segm-by-list-sup(7)</li> <li>▪ pmsc-clear-segm-by-time-sup(8)</li> <li>▪ pmsc-clear-segm-remove(9)</li> <li>▪ pmsc-clear-segm-all-sup(10)</li> <li>▪ pmsc -multi-person(12)</li> <li>▪ pmsc-get-segm-id-list-sup(14) (record for later use)</li> </ul> </li> </ol> </li> </ol> </li> </ol> <p>IF pmsc-get-segm-id-list-sup(14) is NOT set</p> <ol style="list-style-type: none"> <li>3. The simulated PHG sends a request for the PM-Store to retrieve a list of the instance numbers of all the PM-segments it contains <ol style="list-style-type: none"> <li>a. Data APDU <ol style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_GET_ID_LIST</li> </ol> </li> </ol> </li> </ol> |                              |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><input type="checkbox"/> &lt;empty&gt;</p> <p>4. The PHD under test issues a response:</p> <p>a. Data APDU</p> <p><input type="checkbox"/> Type = Roer</p> <p><input type="checkbox"/> ErrorResult = not-allowed-by-object (24)</p> <p>IF pmsc -get-segm-id-list-sup(14) is set</p> <p>5. The simulated PHG sends a request for the PM-Store to retrieve a list of the instance numbers of all the schedule segments it contains</p> <p>a. Data APDU</p> <p><input type="checkbox"/> Type = Invoke   Confirmed Action,</p> <p><input type="checkbox"/> HANDLE = obj-handle</p> <p><input type="checkbox"/> Action = MDC_ACT_SEG_GET_ID_LIST</p> <p><input type="checkbox"/> &lt;empty&gt;</p> <p>6. The PHD under test issues a response with the PM-Segments instance numbers</p> <p>a. Data APDU</p> <p><input type="checkbox"/> Type = Response   Confirmed Action,</p> <p><input type="checkbox"/> HANDLE = obj-handle</p> <p><input type="checkbox"/> Action = MDC_ACT_SEG_GET_ID_LIST</p> <p><input type="checkbox"/> SegmentIdList</p> |
+| <b>Pass/Fail criteria</b> | The PHD properly sends the required list of PM-segment ids in supported cases or the specified error otherwise.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                     |
+|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------------|
+| <b>TP Id</b>        | TP/PLT/PHD/OXP/DIM/BV-016                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                     |
+| <b>TP label</b>     | PM-Store object methods. Trig-Segment-Data-Xfer method 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                     |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                     |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | PM-StoreMeth 13; M                                            | PM-StoreMeth 14; M  |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | PM-StoreEvent 2; M                                            | CommonCharac 3; M   |
+|                     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [IEEE 11073-10406]                                            |                     |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | PMStoreObjMeth3; M                                            | PMStoreObjEvent1; M |
+| <b>Test purpose</b> | <p>Check that:</p> <p>The PHD supports the Trig-Segment-Data-Xfer method</p> <p>[AND]</p> <p>If PHD receives the Trig-Segment-Data-Xfer request method, then it responds with an operation type of rors-cmip-confirmed-action</p> <p>[AND]</p> <p>If PHD receives the Trig-Segment-Data-Xfer request method, then it responds with an action-info-args type TrigSegmDataXferRsp</p> <p>[AND]</p> <p>Once the data transfer is triggered via a Trig-Segment-Data-Xfer method, the PHD sends Segment-Data-Event messages until the complete Fixed-Segment-Data is transferred or the transfer is aborted by the PHG or PHD</p> <p>[AND]</p> <p>When sending a Segment-Data-Event event, the event type is MDC_NOTI_SEGMENT_DATA</p> <p>[AND]</p> |                                                               |                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>When sending a [Segment-Data-Event] event the event-info parameter is SegmentDataEvent.</p> <p>[AND]</p> <p>The total size of the response does not exceed the maximum APDU size established by the specialization</p> <p>[AND]</p> <p>If an PHD supports the PM-store class, the support of the Get-Segment-Info and Trig-Segment-Data-Xfer methods is mandatory</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Applicability</b>      | C_AG_OXP_041 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state and the PHD has at least one PM-Segment with more data loaded that the maximum allowed by specialization.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG issues a GET for the PM-Store object.</li> <li>2. The PHD under test responds with the attributes of the PM-Store.</li> <li>3. The simulated PHG issues a Get-Segment-Info with SegmSelection set to all-segments.</li> <li>4. The simulated PHG sends a request for the PM-Segment Data to one of the PM-Segments that contains data: <ol style="list-style-type: none"> <li>a. Data APDU <ol style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> TrigSegmDataXferReq = &lt;Instance number of the selected PM-Segment that contains the data&gt;</li> </ol> </li> </ol> </li> <li>5. The PHD issues an action response: <ol style="list-style-type: none"> <li>a. Data APDU <ol style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> </ol> </li> <li>b. Action = MDC_ACT_SEG_TRIG_XFER <ol style="list-style-type: none"> <li><input type="checkbox"/> TrigSegmDataXferRsp = &lt;Same Instance number&gt;   tsxr-successful (0x00 0x00)</li> </ol> </li> </ol> </li> <li>6. The PHD under test starts Data transfer: <ol style="list-style-type: none"> <li>a. Data APDU <ol style="list-style-type: none"> <li><input type="checkbox"/> Invoke   CfmEventReport</li> <li><input type="checkbox"/> Action = MDC_NOTI_SEGMENT_DATA</li> <li><input type="checkbox"/> SegmentDataEvent</li> </ol> </li> </ol> </li> <li>7. The simulated PHG response to transferred data APDU's: <ol style="list-style-type: none"> <li>a. Data APDU <ol style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_NOTI_SEGMENT_DATA</li> <li><input type="checkbox"/> SegmentDataResult</li> </ol> </li> </ol> </li> <li>8. The PHD under test repeats steps 6 and 7 until all the data is transferred.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• All checked values are as specified in the test procedure</li> <li>• Data is transferred</li> <li>• 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): <ul style="list-style-type: none"> <li>○ Pulse oximeter → 9216 octets</li> </ul> </li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|              | <ul style="list-style-type: none"> <li>○ Weighing scales → 896 octets</li> <li>○ Glucose meter → 5120 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ Blood pressure → 896 octets</li> <li>○ Thermometer → 896 octets</li> <li>○ Independent activity hub → 5120 octets</li> <li>○ Cardiovascular → 64512 octets or 6624 octets if it supports Step Counter Profile</li> <li>○ Strength → 64512 octets</li> <li>○ Adherence monitor → 1024 octets</li> <li>○ Peak flow → 2030 octets</li> <li>○ Body composition analyser → 7730 octets</li> <li>○ Basic ECG/Simple ECG → 7168 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ Basic ECG/Heart rate → 1280 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ International normalized ratio → 896 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ Insulin pump → 7168 octets or 5120 if PHD supports PM-Store</li> <li>○ Continuous glucose monitor → 896 octets or 5120 if PHD supports PM-Store</li> <li>○ Power status monitor → 940 octets for Simple PSM profile or 1660 for Advanced PSM profile</li> </ul> |
+| <b>Notes</b> |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-017                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |
+| <b>TP label</b>          | PM-Store object methods. Trig-Segment-Data-Xfer method 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | PM-StoreMeth 16; M      PM-SegmAttr 4; M                      |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PM-Segment object includes the Operational-State attribute and</p> <p>The [Operational-State] attribute shall be of type [OperationalState]</p> <p>If PM-Segment is having data activity added to it, then Operational-State attribute is set to 'enabled', otherwise, it is set to 'disabled'.</p> <p>[AND]</p> <p>If Trig-Segment-Data-Xfer method is invoked on a PM-Segment that has an Operational-State of "enabled", then the PHD shall replies with a not-allowed-by-object error (roer) with a return code of MDC_RET_CODE_OBJ_BUSY</p>                                                     |                                                               |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_000 AND C_AG_OXP_018                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state and the PHD has at least one PM-Segment.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG issues a GET for the PM-Store object.</li> <li>2. The PHD under test responds with the attributes of the PM-Store.</li> <li>3. The simulated PHG issues a Get-Segment-Info with SegmSelection set to all-segments.</li> <li>4. The simulated PHG sends a request for the PM-Segment Data to one of the PM-Segments that is being used (OperationalState bit enabled): <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> </ul> </li> </ul> </li> </ol> |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> TrigSegmDataXferReq = &lt;Instance number of the selected PM-Segment that contains the data&gt;</li> </ul> <p>5. The PHD issues a "roer" message with reason = not-allowed-by-object (24) and return code = MDC_RET_CODE_OBJ_BUSY.</p> |
+| <b>Pass/Fail criteria</b> | The PHD must respond with the specified error.                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                    |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/DIM/BV-020                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                    |
+| <b>TP label</b>           | Scanner object services. SET Operational-State service                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                    |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                    |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ScanClassServ 1; M                                            |                    |
+|                           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [IEEE 11073-10406]                                            |                    |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | PerScanObjAttr9; M                                            | EpiScanObjAttr9; M |
+| <b>Test purpose</b>       | Check that:<br>A PHD that has scanner derived objects supports the SET service for the Operational-State attribute of the scanner objects.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                    |
+| <b>Applicability</b>      | (C_AG_OXP_046 OR C_AG_OXP_047) AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                    |
+| <b>Other PICS</b>         | C_AG_OXP_180                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                    |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                    |
+| <b>Test procedure</b>     | 1. The simulated PHG sends the scanner a SET Operational-State attribute: <ul style="list-style-type: none"> <li>a. If C_AG_OXP_180, THEN APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Remote Operation Invoke   Confirmed Event Report</li> <li><input type="checkbox"/> roiv-cmip-confirmed-set</li> <li><input type="checkbox"/> attribute = OperationalState</li> <li><input type="checkbox"/> value = 0</li> </ul> </li> <li>b. If not C_AG_OXP_180, THEN APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Remote Operation Invoke   Event Report</li> <li><input type="checkbox"/> roiv-cmip-set</li> <li><input type="checkbox"/> attribute = OperationalState</li> <li><input type="checkbox"/> value = 0</li> </ul> </li> </ul> 2. If C_AG_OXP_180, the PHD under test must respond with a confirmation ELSE no response for roiv-cmip-set will be received.<br><br>If C_AG_OXP_180, verify the invoke-id is mirrored from the Set request: <ul style="list-style-type: none"> <li>a. APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action</li> <li><input type="checkbox"/> result = accepted</li> </ul> </li> </ul> |                                                               |                    |
+| <b>Pass/Fail criteria</b> | The procedure is executed without errors.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                    |
+| <b>Notes</b>              | The semantics of the Operational-State Attribute are tested in TP/PLT/PHD/EXP/COM/BV-056.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                    |
+
+|                 |                                                         |
+|-----------------|---------------------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/EXP/DIM/BV-021                               |
+| <b>TP label</b> | CfgScanner object Attributes. Confirm-Timeout operation |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                  |                    |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|------------------|--------------------|
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                  |                    |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | CfgScanAttr 3; C                                              | CfgScanAttr 4; C | OperErrorCond 5; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | OperErrorCond 6; M                                            | TimeOutVar 3; C  |                    |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If a Configurable Scanner is operating in confirmed mode then the value of attribute Confirm-Timeout matches with the actual timeout value that the PHD uses for the Confirmed Event Report generated from the Scanner object.</p> <p>[AND]</p> <p>TOcer-scan: If the attribute is not present, the PHD shall use the value 3 s.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                  |                    |
+| <b>Applicability</b>     | (C_AG_OXP_046 OR C_AG_OXP_047) AND C_AG_OXP_053 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                  |                    |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_180, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                  |                    |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                  |                    |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>3. The PHD responds with a "Remote Operation Invoke   Confirmed Event Report" message with a MDC_NOTI_CONFIG event to send its configuration to the PHG, record the Scanner attribute Confirm-Timeout, if it is not present the simulated PHG will use 3s as a default value.</li> <li>4. IF C_AG_OXP_293 THEN: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 THEN it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ol> </li> <li>5. Wait for the PHD under test and the simulated PHG to reach the Operating state.</li> <li>6. Take some measurements in the PHD.</li> <li>7. The simulated PHG sets the Operational state of the scanner to 1: <ol style="list-style-type: none"> <li>a. If C_AG_OXP_180 THEN APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Remote Operation Invoke   Confirmed Event Report</li> <li><input type="checkbox"/> roiv-cmip-confirmed-set</li> <li><input type="checkbox"/> attribute = OperationalState</li> <li><input type="checkbox"/> value = 1</li> </ul> </li> <li>b. If not C_AG_OXP_180 THEN APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Remote Operation Invoke   Event Report</li> <li><input type="checkbox"/> roiv-cmip-set</li> <li><input type="checkbox"/> attribute = OperationalState</li> <li><input type="checkbox"/> value = 1</li> </ul> </li> </ol> </li> <li>8. If C_AG_OXP_180 the PHD under test must respond with a confirmation <ol style="list-style-type: none"> <li>a. APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action</li> </ul> </li> </ol> </li> </ol> |                                                               |                  |                    |
+
+|                           |                                                                                                                                                                            |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> result = accepted<br>9. Wait until the PHD under test starts to send data.<br>10. The PHG must not respond for at least the Confirm-Timeout time. |
+| <b>Pass/Fail criteria</b> | The PHD must wait for a Confirmed Event Report Response message for a Confirm-TimeOut period. If the time expires, the PHD must send an abort to the PHG.                  |
+| <b>Notes</b>              |                                                                                                                                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                       |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-023                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                       |
+| <b>TP label</b>          | EpiCfgScanner object. Reports                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                       |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                       |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EpiCFgScanClass 1; M                                          | EpiCFgScanClass 2; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ScanClassConcep8; C                                           | ScanClassConcep9; C   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | EpiCfgScanEvent 1; C                                          | EpiCfgScanEvent 28; M |
+| <b>Test purpose</b>      | Check that:<br>The PHD sends a report of an episodic scanner whenever one of the observed attributes changes its value<br>[AND]<br>The PHD supports at least one of the events identified in Table 16 of the spec (Unbuf-Scan-Report-Var; Unbuf-Scan-Report-Fixed; Unbuf-Scan-Report-Grouped; Unbuf-Scan-Report-MP-Var; Unbuf-Scan-Report-MP-Fixed; Unbuf-Scan-Report-MP-Grouped).<br>[AND]<br>Episodic scanners using the group, variable or fixed format shall create scan event reports where:<br>If the scanner is episodic and no AttributeChangeSets are collected, the scan event report shall not be sent.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                       |
+| <b>Applicability</b>     | C_AG_OXP_047 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                       |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_010, C_AG_OXP_014, C_AG_OXP_180, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                       |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |                       |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. The Configurable Episodic Scanner object attribute of interest for this test is: <ol style="list-style-type: none"> <li>a. Attribute Min-Interval-Reporting <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SCAN_REP_PD_MIN</li> <li><input type="checkbox"/> attribute-type = RelativeTime</li> <li><input type="checkbox"/> attribute-length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Record for later comparison&gt;</li> </ul> </li> </ol> </li> <li>5. IF C_AG_OXP_293 THEN: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 THEN it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                                                               |                       |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> <ol style="list-style-type: none"> <li>6. The simulated PHG sets the Operational state of the scanner to 1.</li> <li>7. Take a measurement with the PHD under test.</li> <li>8. Check that the simulated PHG receives the Event sent by the PHD with the changed value and reports it with a grouped type event: <ol style="list-style-type: none"> <li>a. PrstApdu <ul style="list-style-type: none"> <li><input type="checkbox"/> Remote Operation Invoke   Confirmed Event Report</li> <li><input type="checkbox"/> Type = MDC_NOTI_UNBUF_SCAN_REPORT_GROUPED (0x0D 0x24) or MDC_NOTI_UNBUF_SCAN_REPORT_VAR (0x0D 0x22) or MDC_NOTI_UNBUF_SCAN_REPORT_FIXED (0x0D 0x23) or MDC_NOTI_UNBUF_SCAN_REPORT_MP_GROUPED (0x0D 0x27) or MDC_NOTI_UNBUF_SCAN_REPORT_MP_VAR (0x0D 0x25) or MDC_NOTI_UNBUF_SCAN_REPORT_MP_FIXED (0x0D 0x26)</li> </ul> </li> </ol> </li> <li>9. Take measurements faster than the Reporting Interval recorded in step 4.</li> <li>10. Wait for the next event report.</li> <li>11. If it is possible, force the PHD not to change the values that are collected by the scanner object.</li> <li>12. Wait for the next event report.</li> <li>13. Check that no scanner event report is sent.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHD sends an event report when the attribute changes</li> <li>• The received events are of grouped, variable or fixed type</li> <li>• The event reports are not sent at a rate faster than the minimum reporting interval</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                     |                                                                                                                                                                  |                                                               |                       |                       |
+|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------|-----------------------|
+| <b>TP Id</b>        | TP/PLT/PHD/OXP/DIM/BV-027                                                                                                                                        |                                                               |                       |                       |
+| <b>TP label</b>     | EpiCfgScanner object events. Unbuf-Scan-Report                                                                                                                   |                                                               |                       |                       |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                      | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                       |                       |
+|                     | <b>Testable items</b>                                                                                                                                            | EpiCfgScanEvent 10; C                                         | EpiCfgScanEvent 11; C | EpiCfgScanEvent 13; C |
+|                     |                                                                                                                                                                  | EpiCfgScanEvent 30; C                                         | EpiCfgScanEvent 22; C | EpiCfgScanEvent 23; C |
+|                     |                                                                                                                                                                  | EpiCfgScanEvent 25; C                                         | EpiCfgScanEvent 33; C | EpiCfgScanEvent 2; C  |
+|                     |                                                                                                                                                                  | EpiCfgScanEvent 3; C                                          | EpiCfgScanEvent 5; C  | EpiCfgScanEvent 6; C  |
+|                     |                                                                                                                                                                  | EpiCfgScanEvent 7; C                                          | EpiCfgScanEvent 9; C  | EpiCfgScanEvent 14; C |
+|                     |                                                                                                                                                                  | EpiCfgScanEvent 15; C                                         | EpiCfgScanEvent 17; C | EpiCfgScanEvent 18; C |
+|                     |                                                                                                                                                                  | EpiCfgScanEvent 19; C                                         | EpiCfgScanEvent 21; C | EpiCfgScanEvent 28; C |
+|                     |                                                                                                                                                                  | EpiCfgScanEvent 29; C                                         | EpiCfgScanEvent 31; C | EpiCfgScanEvent 32; C |
+|                     |                                                                                                                                                                  | ScannerGeneral1; O                                            |                       |                       |
+|                     | <b>Spec</b>                                                                                                                                                      | [IEEE 11073-10406]                                            |                       |                       |
+|                     | <b>Testable items</b>                                                                                                                                            | EpiScanObjEv1; M                                              | EpiScanObjEv3; M      | EpiScanObjEv4; M      |
+|                     |                                                                                                                                                                  | EpiScanObjEv5; M                                              | EpiScanObjEv6; M      | EpiScanObjEv6; M      |
+|                     |                                                                                                                                                                  | EpiScanObjEv7; M                                              | EpiScanObjEv8; M      | ObjAccServ2; O        |
+|                     | <b>Spec</b>                                                                                                                                                      | [b-ITU-T H.810 (2015)]                                        |                       |                       |
+|                     | <b>Testable items</b>                                                                                                                                            | General 7; C                                                  |                       |                       |
+| <b>Test purpose</b> | Check that:<br>If an Episodic Scanner uses Unbuf-Scan-Report-Grouped Events to report updated data, then it uses the ScanReportInfoGrouped Event-info parameter. |                                                               |                       |                       |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | <p>[AND]</p> <p>If an Episodic Scanner uses Unbuf-Scan-Report-MP-Grouped events to report updated data, then it uses the ScanReportInfoMPGrouped Event-info parameter.</p> <p>[AND]</p> <p>If an Episodic Scanner uses Unbuf-Scan-Report-Var events to report updated data, then it uses the ScanReportInfoVar Event-info parameter.</p> <p>[AND]</p> <p>If an Episodic Scanner uses Unbuf-Scan-Report-MP-Var events to report updated data, then it uses the ScanReportInfoMPVar Event-info parameter.</p> <p>[AND]</p> <p>If an Episodic Scanner uses Unbuf-Scan-Report-Fixed events to report updated data, then it uses the ScanReportInfoFixed Event-info parameter.</p> <p>[AND]</p> <p>If an Episodic Scanner uses Unbuf-Scan-Report-MP-Fixed events to report updated data, then it uses the ScanReportInfoMPFixed Event-info parameter.</p> <p>[AND]</p> <p>The event is triggered whenever data values change.</p> <p>[AND]</p> <p>If it reports data in confirmed mode (Confirmed-Mode attribute value is 1), then the PHD uses a roiv-cmip-confirmed-event-report operation.</p> <p>[AND]</p> <p>If it reports data in unconfirmed mode (Confirmed-Mode attribute value is 0), then the PHD uses a roiv-cmip-event-report operation.</p> <p>[AND]</p> <p>Continua PAN 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.</p> |
+| <b>Applicability</b>     | C_AG_OXP_047 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Other PICS</b>        | C_AG_OXP_033, C_AG_OXP_180                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Take some measurements with the PHD under test.</li> <li>2. The simulated PHG sets the Operational state of the scanner to 1.</li> <li>3. Wait until the PHD under test starts to send its data.</li> <li>4. Check that the PHD uses the ScanReportInfGrouped Event-info parameter, whenever data values change: <ol style="list-style-type: none"> <li>a. PrstApdu <ul style="list-style-type: none"> <li><input type="checkbox"/> Remote Operation Invoke   Confirmed Event Report OR   Event Report</li> <li><input type="checkbox"/> Event-Type = MDC_NOTI_UNBUF_SCAN_REPORT_GROUPED (0x0D 0x24) <ul style="list-style-type: none"> <li><input type="checkbox"/> scanReportInfoGrouped:SEQUENCE of: <ul style="list-style-type: none"> <li>▪ data-req-id = &lt;Not relevant for this test&gt;</li> <li>▪ scan-report-no = &lt;counter for detection of missing scan reports&gt;</li> <li>▪ obs-scan-grouped = SEQUENCE OF octet strings</li> </ul> </li> <li><input type="checkbox"/> Or MDC_NOTI_UNBUF_SCAN_REPORT_MP_GROUPED (0x0D 0x27) <ul style="list-style-type: none"> <li><input type="checkbox"/> ScanReportInfoMPGrouped.scan-per-grouped = SEQUENCE of: <ul style="list-style-type: none"> <li>▪ person-id.value = &lt;record for comparison&gt;</li> <li>▪ obs-scan-grouped = &lt;Not relevant for this Test&gt;</li> </ul> </li> </ul> </li> <li><input type="checkbox"/> Or MDC_NOTI_UNBUF_SCAN_REPORT_VAR (0x0D 0x22)</li> </ul> </li> </ul> </li> </ol> </li> </ol>         |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> ScanReportInfoVar= SEQUENCE of:           <ul style="list-style-type: none"> <li>▪ data-req-id = &lt;Not relevant for this test&gt;</li> <li>▪ scan-report-no = &lt;counter for detection of missing scan reports&gt;</li> <li>▪ obs-scan-var = SEQUENCE OF ObservationScan</li> </ul> </li> <li><input type="checkbox"/> Or MDC_NOTI_UNBUF_SCAN_REPORT_MP_VAR (0x0D 0x25)           <ul style="list-style-type: none"> <li><input type="checkbox"/> ScanReportInfoMPVar.scan-per-var = SEQUENCE of:               <ul style="list-style-type: none"> <li>▪ person-id.value = &lt;record for comparison&gt;</li> <li>▪ obs-scan-var = &lt;Not relevant for this Test&gt;</li> </ul> </li> </ul> </li> <li><input type="checkbox"/> Or MDC_NOTI_UNBUF_SCAN_REPORT_FIXED (0x0D 0x23)           <ul style="list-style-type: none"> <li><input type="checkbox"/> ScanReportInfoFixed= SEQUENCE of:               <ul style="list-style-type: none"> <li>▪ data-req-id = &lt;Not relevant for this test&gt;</li> <li>▪ scan-report-no = &lt;counter for detection of missing scan reports&gt;</li> <li>▪ obs-scan-fixed = SEQUENCE OF ObservationScanFixed</li> </ul> </li> </ul> </li> <li><input type="checkbox"/> Or MDC_NOTI_UNBUF_SCAN_REPORT_MP_FIXED (0x0D 0x26)           <ul style="list-style-type: none"> <li><input type="checkbox"/> ScanReportInfoMPFixed.scan-per-fixed = SEQUENCE of:               <ul style="list-style-type: none"> <li>▪ person-id.value = &lt;record for comparison&gt;</li> <li>▪ obs-scan-fixed = &lt;Not relevant for this Test&gt;</li> </ul> </li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHD sends data using grouped, variable or fixed event reports.</li> <li>• If the PHD supports multi-person event reports for one or more episodic scanner object (C_AG_OXP_033= TRUE) THEN the PHD uses MP Unbuf Event report, and check that every person-id is different from each other or "unknown-person-id" (65535).</li> <li>• If C_AG_OXP_033= TRUE and MP event reports have been received, a pop-up will show the received measurements to make the operator identify if measurements have been correctly assigned to every person.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                      |  |  |
+|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|----------------------|--|--|
+| <b>TP Id</b>         | TP/PLT/PHD/OXP/DIM/BV-032_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                      |  |  |
+| <b>TP label</b>      | PeriCfgScanner object Attribute. Reporting interval attribute 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                      |  |  |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                      |  |  |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | PeriCfgScanClass 1; M                                         | PeriCfgScanAttr 2; M |  |  |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | PeriCfgScanClass 3; R                                         | ScanClassConcep8; C  |  |  |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | PeriCfgScanEvent 26; M                                        |                      |  |  |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | ScanClassConcep9; C                                           |                      |  |  |
+| <b>Test purpose</b>  | <p>Check that:</p> <p>A periodic scanner in the active Operating state sends an event report at a rate of one per reporting interval, where the reporting interval is the value of the Reporting-Interval attribute.</p> <p>[AND]</p> <p>The same objects and attributes are included in each report regardless of whether their values have changed.</p> <p>[AND]</p> <p>When a period configurable scanner is enabled by a PHG, scan reports should be sent within a reasonable time and synchronized to the reporting interval of the scanner. The time between the scanner being enabled and the sending of the first scan report should be within the reporting interval plus 15 seconds.</p> <p>[AND]</p> <p>Periodic scanners using the group, variable or fixed format shall create scan event reports where:</p> <p>If the scanner is periodic and no AttributeChangeSets are collected, an empty scan event report shall be sent when the period expires.</p> |                                                               |                      |  |  |
+| <b>Applicability</b> | C_AG_OXP_046 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                      |  |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICS</b>         | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_180, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Initial condition</b>  | The simulated PHG and 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.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. The Configurable Periodic Scanner object attribute of interest for this test is: <ol style="list-style-type: none"> <li>a. Mandatory attribute Reporting-Interval <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SCAN_REP_PD</li> <li><input type="checkbox"/> attribute-type = RelativeTime</li> <li><input type="checkbox"/> attribute-length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt; Record for later comparison &gt;</li> </ol> </li> </ol> </li> <li>5. IF C_AG_OXP_293 THEN: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ol style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 THEN it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ol> </li> </ol> </li> <li>6. The simulated PHG sets the Operational state of the scanner to 1.</li> <li>7. Take several measurements.</li> <li>8. Wait until the PHD under test starts to send its data.</li> <li>9. Wait for the next event report.</li> <li>10. If it is possible, force the PHD not to change the values that are collected by scanner object.</li> <li>11. Wait for the next event report.</li> <li>12. Check that an empty event report is sent.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <p>The Event reports must arrive periodically with a period the same as the time defined in Reporting-Interval.</p> <p>The time between the scanner being enabled (step 6) and the sending of the first scan report (step 7) should not exceed the reporting interval plus 15 seconds.</p> <p>An empty Scan Event Report is sent by the PHD under test when the value has not changed (step 12).</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                 |                                                                 |                                                               |                        |
+|-----------------|-----------------------------------------------------------------|---------------------------------------------------------------|------------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/OXP/DIM/BV-032_B                                     |                                                               |                        |
+| <b>TP label</b> | PeriCfgScanner object Attribute. Reporting interval attribute 2 |                                                               |                        |
+| <b>Coverage</b> | <b>Spec</b>                                                     | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                        |
+|                 | <b>Testable items</b>                                           | PeriCfgScanClass 1; M                                         | PeriCfgScanAttr 2; M   |
+|                 |                                                                 |                                                               | PeriCfgScanEvent 26; M |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>       | <p>Check that:</p> <p>Event Reports include measurements that are acquired faster than reporting interval</p> <p>[AND]</p> <p>A periodic scanner in the active Operating state sends an event report at a rate of one per reporting interval, where the reporting interval is the value of the Reporting-Interval attribute.</p> <p>[AND]</p> <p>The same objects and attributes are included in each report regardless of whether their values have changed</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Applicability</b>      | C_AG_OXP_046 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Other PICS</b>         | C_AG_OXP_180                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Initial condition</b>  | The simulated PHG and 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.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. The Configurable Periodic Scanner object attribute of interest for this test is: <ol style="list-style-type: none"> <li>a. Mandatory attribute Reporting-Interval <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SCAN_REP_PD</li> <li><input type="checkbox"/> attribute-type = RelativeTime</li> <li><input type="checkbox"/> attribute-length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt; Record for later comparison &gt;</li> </ol> </li> </ol> </li> <li>5. The simulated PHG sets the Operational state of the scanner to 1.</li> <li>6. Wait until the PHD under test sends two event reports.</li> <li>7. Take measurements faster than the Reporting Interval recorded in step 4.</li> <li>8. Wait for the next event report.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 6 verify that the received observed value is the same for the two events (same objects and attributes, but not attribute value).</li> <li>• Verify that in step 8 the received event contains a number of measurements higher than the number of measurements received in step 6.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              | <p>In last paragraph of clause 6.3.9.5.1 there is an example where states that it must send ALL the measurements, not only the last change. It has to send all the registered observations.</p> <p>Example: A Periodic Configurable Scanner is set up to 'scan' two Metric objects with a Reporting-Interval of 1 sec. The two objects update their corresponding observed value periodically with an interval of 1 sec and ½ sec respectively. The Periodic Configurable Scanner then issues Event Reports every second containing one observation scan of Metric object #1 and two observation scans of Metric object #2.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                 |                                               |                                                               |                        |
+|-----------------|-----------------------------------------------|---------------------------------------------------------------|------------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/OXP/DIM/BV-036                     |                                                               |                        |
+| <b>TP label</b> | PeriCfgScanner object events. Buf-Scan-Report |                                                               |                        |
+| <b>Coverage</b> | <b>Spec</b>                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                        |
+|                 | <b>Testable items</b>                         | PeriCfgScanEvent 10; C                                        | PeriCfgScanEvent 11; C |
+|                 |                                               | PeriCfgScanEvent 1; C                                         | PeriCfgScanEvent 22; C |
+|                 |                                               | PeriCfgScanEvent 25; C                                        | PeriCfgScanEvent 2; C  |
+|                 |                                               | PeriCfgScanEvent 5; C                                         | PeriCfgScanEvent 6; C  |
+|                 |                                               | PeriCfgScanEvent 9; C                                         | PeriCfgScanEvent 14; C |
+|                 |                                               | PeriCfgScanEvent 17; C                                        | PeriCfgScanEvent 18; C |
+|                 |                                               |                                                               | PeriCfgScanEvent 13; C |
+|                 |                                               |                                                               | PeriCfgScanEvent 23; C |
+|                 |                                               |                                                               | PeriCfgScanEvent 3; C  |
+|                 |                                               |                                                               | PeriCfgScanEvent 7; C  |
+|                 |                                               |                                                               | PeriCfgScanEvent 15; C |
+|                 |                                               |                                                               | PeriCfgScanEvent 19; C |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                    |                  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|------------------|
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | PeriCfgScanEvent 21; C | ScannerGeneral1; O |                  |
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [IEEE 11073-10406]     |                    |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | PerScanObjEv1; M       | PerScanObjEv3; M   | PerScanObjEv4; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | PerScanObjEv5; M       | PerScanObjEv6; M   | PerScanObjEv7; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | PerScanObjEv8; M       | ObjAccServ2; O     |                  |
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [b-ITU-T H.810 (2015)] |                    |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | General 7; C           |                    |                  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If a Periodic Configurable Scanner uses Buf-Scan-Report-Grouped Events to report updated data, then it uses the ScanReportInfoGrouped Event-Info parameter.</p> <p>[AND]</p> <p>If a Periodic Configurable Scanner uses Buf-Scan-Report-MP-Grouped Events to report updated data, then it uses the ScanReportInfoMPGrouped Event-Info parameter.</p> <p>[AND]</p> <p>If a Periodic Configurable Scanner uses Buf-Scan-Report-Var Events to report updated data, then it uses the ScanReportInfoVar Event-Info parameter.</p> <p>[AND]</p> <p>If a Periodic Configurable Scanner uses Buf-Scan-Report-MP-Var Events to report updated data, then it uses the ScanReportInfoMPVar Event-Info parameter.</p> <p>[AND]</p> <p>If a Periodic Configurable Scanner uses Buf-Scan-Report-Fixed Events to report updated data, then it uses the ScanReportInfoFixed Event-Info parameter.</p> <p>[AND]</p> <p>If a Periodic Configurable Scanner uses Buf-Scan-Report-MP-Fixed Events to report updated data, then it uses the ScanReportInfoMPFixed Event-Info parameter.</p> <p>[AND]</p> <p>If it reports data in confirmed mode (Confirmed-Mode attribute value is 1), then the PHD uses a roiv-cmip-confirmed-event-report operation.</p> <p>[AND]</p> <p>If it reports data in unconfirmed mode (Confirmed-Mode attribute value is 0), then the PHD uses a roiv-cmip-event-report operation.</p> <p>[AND]</p> <p>The PHD supports at least one of the events identified in Table 18 of the spec (Buf-Scan-Report-Var; Buf -Scan-Report-Fixed; Buf -Scan-Report-Grouped; Buf -Scan-Report-MP-Var; Buf -Scan-Report-MP-Fixed; Buf -Scan-Report-MP-Grouped).</p> <p>[AND]</p> <p>Continua PAN 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</p> |                        |                    |                  |
+| <b>Applicability</b>     | C_AG_OXP_046 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                    |                  |
+| <b>Other PICS</b>        | C_AG_OXP_034, C_AG_OXP_180                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                    |                  |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                    |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Make a change to one of the observed values by the PHD under test.</li> <li>2. The simulated PHG sets the Operational state of the scanner to 1.</li> <li>3. Wait until the PHD under test starts to send its data.</li> <li>4. Check that the simulated PHG receives the Event send by the PHD with the changed value and reports it with a grouped type event: <ol style="list-style-type: none"> <li>a. DataApdu</li> </ol> </li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                    |                  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> Remote Operation Invoke   Confirmed Event Report or   Event Report</li> <li><input type="checkbox"/> Event-Type = MDC_NOTI_BUF_SCAN_REPORT_GROUPED (0x0D 0x2A) <ul style="list-style-type: none"> <li><input type="checkbox"/> ScanReportInfoGrouped:SEQUENCE of: <ul style="list-style-type: none"> <li>▪ data-req-id = &lt;Not relevant for this test&gt;</li> <li>▪ scan-report-no = &lt;counter for detection of missing scan reports&gt;</li> <li>▪ obs-scan-grouped = SEQUENCE OF octet strings</li> </ul> </li> </ul> </li> <li><input type="checkbox"/> Or MDC_NOTI_BUF_SCAN_REPORT_MP_GROUPED (0x0D 0x2D) <ul style="list-style-type: none"> <li><input type="checkbox"/> ScanReportInfoMPGrouped.scan-per-grouped = SEQUENCE of: <ul style="list-style-type: none"> <li>▪ person-id.value = &lt;record for comparison&gt;</li> <li>▪ obs-scan-grouped = &lt;Not relevant for this Test&gt;</li> </ul> </li> </ul> </li> <li><input type="checkbox"/> Or MDC_NOTI_BUF_SCAN_REPORT_VAR (0x0D 0x28) <ul style="list-style-type: none"> <li><input type="checkbox"/> ScanReportInfoVar= SEQUENCE of: <ul style="list-style-type: none"> <li>▪ data-req-id = &lt;Not relevant for this test&gt;</li> <li>▪ scan-report-no = &lt;counter for detection of missing scan reports&gt;</li> <li>▪ obs-scan-var = SEQUENCE OF ObservationScan</li> </ul> </li> </ul> </li> <li><input type="checkbox"/> Or MDC_NOTI_BUF_SCAN_REPORT_MP_VAR (0x0D 0x2B) <ul style="list-style-type: none"> <li><input type="checkbox"/> ScanReportInfoMPVar.scan-per-var = SEQUENCE of: <ul style="list-style-type: none"> <li>▪ person-id.value = &lt;record for comparison&gt;</li> <li>▪ obs-scan-var = &lt;Not relevant for this Test&gt;</li> </ul> </li> </ul> </li> <li><input type="checkbox"/> Or MDC_NOTI_BUF_SCAN_REPORT_FIXED (0x0D 0x29) <ul style="list-style-type: none"> <li><input type="checkbox"/> ScanReportInfoFixed= SEQUENCE of: <ul style="list-style-type: none"> <li>▪ data-req-id = &lt;Not relevant for this test&gt;</li> <li>▪ scan-report-no = &lt;counter for detection of missing scan reports&gt;</li> <li>▪ obs-scan-fixed = SEQUENCE OF ObservationScanFixed</li> </ul> </li> </ul> </li> <li><input type="checkbox"/> Or MDC_NOTI_BUF_SCAN_REPORT_MP_FIXED (0x0D 0x2C) <ul style="list-style-type: none"> <li><input type="checkbox"/> ScanReportInfoMPFixed.scan-per-fixed = SEQUENCE of: <ul style="list-style-type: none"> <li>▪ person-id.value = &lt;record for comparison&gt;</li> <li>▪ obs-scan-fixed = &lt;Not relevant for this Test&gt;</li> </ul> </li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHD sends grouped, variable or fixed format event reports.</li> <li>• If the PHD supports multi-person event reports for one or more periodic scanner object (C_AG_OXP_034= TRUE) THEN the PHD uses MP Buf Event report, check that every person-id is different from each other or "unknown-person-id" (65535).</li> <li>• If C_AG_OXP_034 = TRUE and MP event reports have been received, a pop-up will show the received measurements to make the operator identify if the measurements have been correctly assigned to every person.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                     |                                                                                                                                                                                                                             |                                                               |  |
+|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>        | TP/PLT/PHD/OXP/DIM/BV-042                                                                                                                                                                                                   |                                                               |  |
+| <b>TP label</b>     | CfgScanner object. Confirm-Mode attribute                                                                                                                                                                                   |                                                               |  |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                     | <b>Testable items</b>                                                                                                                                                                                                       | CfgScanAttr 1;M                                               |  |
+| <b>Test purpose</b> | <p>Check that:</p> <p>IF Confirmed-Mode attribute value is 1, THEN the PHD uses a roiv-cmip-confirmed-event-report operation.</p> <p>IF Confirmed-Mode attribute value is 0, THEN the PHD uses a roiv-cmip-event-report</p> |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | operation                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Applicability</b>      | (C_AG_OXP_046 OR C_AG_OXP_047) AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Other PICS</b>         | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_180, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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 the Scanner attribute Confirm-Mode.</li> <li>4. IF C_AG_OXP_293 THEN: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 THEN it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ol> </li> <li>5. Wait for the PHD under test and the simulated PHG to reach the Operating state.</li> <li>6. The simulated PHG sets the Operational state of the scanner to 1.</li> <li>7. Wait until the PHD under test starts to send data.</li> <li>8. Check that the simulated PHG receives the Event sent by the PHD:<br/> IF the Confirm-Mode recorded in step 3, is "confirmed": <ol style="list-style-type: none"> <li>a. PrstApdu <ul style="list-style-type: none"> <li><input type="checkbox"/> Remote Operation Invoke   Confirmed Event Report</li> </ul> </li> </ol> IF the Confirm-Mode recorded in step 3, is "unconfirmed": <ol style="list-style-type: none"> <li>a. PrstApdu <ul style="list-style-type: none"> <li><input type="checkbox"/> Remote Operation Invoke   Event Report</li> </ul> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | IF the Confirm-Mode value is confirmed THEN the PHD sends a Confirmed Event Report.<br>IF the Confirm-mode value is unconfirmed THEN the PHD sends an Unconfirmed Event Report.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                      |                                                                                                                                                                                                                                                                                                   |                                                               |
+|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>         | TP/PLT/PHD/OXP/DIM/BV-043                                                                                                                                                                                                                                                                         |                                                               |
+| <b>TP label</b>      | PM-Store object. Change Unit Code attribute                                                                                                                                                                                                                                                       |                                                               |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                             | StoreClassGen 1; M                                            |
+| <b>Test purpose</b>  | Check that:<br>If an attribute value in a PM-segment depends on another attribute value not stored in the PM-segment, then that dependent attribute shall not change value during the lifetime of the PM-segment. Otherwise, the PHD shall store the dependent attribute value in the PM-segment. |                                                               |
+| <b>Applicability</b> | (C_AG_OXP_073) AND C_AG_OXP_000 AND C_AG_DGC_018                                                                                                                                                                                                                                                  |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make a change to the contextual attribute Unit-Code for an object that is stored in the PM-Store.</li> <li>2. The simulated PHG sends a request (Get-Segment-Info) for the PM-Segment attributes with SegmSelection = 1 to obtain all the segments for the PM-Store: <ol style="list-style-type: none"> <li>a. Data APDU <ol style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_GET_INFO</li> <li><input type="checkbox"/> SegmSelection = all-segments</li> </ol> </li> </ol> </li> <li>3. The PHD issues a response with the PM-Segments attributes: <ol style="list-style-type: none"> <li>a. Data APDU <ol style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_GET_INFO</li> <li><input type="checkbox"/> SegmentInfoList: Record value for PM-Segment-Entry-Map attribute</li> </ol> </li> </ol> </li> <li>4. Repeat steps 1 and 2 for every PM-Store.</li> </ol> |
+| <b>Pass/Fail criteria</b> | In step 2, there is at least one segment that stores Unit-code attribute (PM-Segment-Entry-Map).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                     |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/DIM/BV-044                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                     |
+| <b>TP label</b>          | PeriCfgScanner object. Reporting interval and FIFO                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | ScanClassConcep4; M                                           | ScanClassConcep7; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The periodic scanner also requires that the rate of generation of all collected AttributeChangeSets shall have a fixed timing relationship with each other and with the period of the periodic scanner.</p> <p>[AND]</p> <p>The periodic scanner shall insert AttributeChangeSets from the same object in the scan event report in FIFO order.</p>                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                     |
+| <b>Applicability</b>     | C_AG_OXP_046 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                     |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_180, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                     |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                     |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Record attribute for Periodic Scanner Object: <ol style="list-style-type: none"> <li>a. Mandatory attribute Reporting-Interval <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SCAN_REP_PD</li> <li><input type="checkbox"/> attribute-type = RelativeTime</li> <li><input type="checkbox"/> attribute-length = 4 bytes</li> </ol> </li> </ol> </li> </ol> |                                                               |                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><input type="checkbox"/> attribute-value = &lt; Record for later comparison &gt;</p> <p>5. IF C_AG_OXP_293 THEN:</p> <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>IF the mds-time-mgr-set-time bit is set:           <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and:               <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 THEN it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ol> <p>6. Wait for 4 * Reporting Interval (the reasonable time for the scanner being enabled and the sending of the first scan report) or 4*15 seconds, whichever is greater.</p> <p>7. Set the Operational State to 1 for the Periodic Scanner object.</p> <p>8. Wait until the PHD under test starts to send its data and record it.</p> <p>9. Set the Operational State to 0 for the Periodic Scanner object.</p> <p>10. Wait for 4 * Reporting Interval or 4*15 seconds, whichever is greater.</p> <p>11. Set the Operational State to 1 for the Periodic Scanner object.</p> <p>12. Wait until the PHD under test starts to send its data and record it.</p> |
+| <b>Pass/Fail criteria</b> | In steps 8 and 12 the same number of observations must be received from the PHD.<br>In step 12, check that measurements have been received following a FIFO sequence.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                             |
+|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------------|
+| <b>TP Id</b>        | TP/PLT/PHD/OXP/DIM/BV-045                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                             |
+| <b>TP label</b>     | PM-Store object methods. Clear-Segments Base-Offset-Time Range method 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                             |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                             |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | PM-StoreMeth 1; O                                             | PM-StoreMeth 2; C           |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | PM-StoreMeth 8; O                                             | PersStoreMtrDatTransf 20; M |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | PersStoreMtrDatTransf 22; O                                   | PersStoreMtrDatTransf 23; M |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | PM-StoreMeth 33; M                                            | PM-StoreMeth 6; M           |
+| <b>Test purpose</b> | <p>Check that:</p> <p>If the PHD supports the Clear-Segment (time range) method, then it responds to Clear-Segment requests with a Data APDU with an operation type rors-cmip-confirmed-action</p> <p>[AND]</p> <p>According to PM-Store-Capab attribute this method removes all entries from the specified PM-Segment, leaving it empty, or it removes the defined PM-Segment completely</p> <p>[AND]</p> <p>The Instance-Number of all other PM-Segments is unaffected by clearing a segment</p> <p>[AND]</p> <p>For PM-segments cleared using the by time method and using base time with offset, only PM-Segments having Segment-Start-BO-Time and Segment-End-BO-Time fields entirely within the specified time period are cleared. In using Segment-Start-BO-Time and Segment-End-BO-Time, the base time shall have a valid time (i.e., a non-zero value).</p> |                                                               |                             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Applicability</b>      | C_AG_OXP_041 AND C_AG_OXP_071 AND C_AG_OXP_072 AND C_AG_OXP_014 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state and the PHD supports at least one PM-Segment with data stored.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make sure the PHD under test is not taking measurements which are stored in PM-Segments.</li> <li>2. 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.</li> <li>3. The PHD under test issues a GET response with the PM-Store attributes, record the values of the PM-Store-Capab attribute: <ol style="list-style-type: none"> <li>a. PM-Store-Capab: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li> <li><input type="checkbox"/> attribute-type = PmStoreCapab</li> <li><input type="checkbox"/> attribute-value = Record the value of bit 8 (Indicates that PM-Segments in the SegmSelection data type can be cleared by defining a time range)</li> </ul> </li> </ol> </li> <li>4. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection set to all-segments.</li> <li>5. The PHD issues a response (rors-cmip-confirmed-action) with the PM-Segment attributes it supports, record the attributes "Segment-Start-BO-Time" and "Segment-End-BO-Time" of every PM-Segment.</li> </ol> <p>IF bit 8 of PMStoreCapab was set:</p> <ol style="list-style-type: none"> <li>6. The simulated PHG sends a Clear-Segment: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> <li><input type="checkbox"/> SegmSelection = bo-time-range, selecting a range with its boundaries that are not within the Segment-Start-BO-Time and Segment-End-BO-Time</li> </ul> </li> </ol> </li> <li>7. The PHD under test operation response: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Roer</li> <li><input type="checkbox"/> ErrorResult = no-such-action (9)</li> </ul> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | In step 7 the PHD must send the specified error.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Notes</b>              | <p>Error code was not clearly defined in the spec.</p> <p>In the new edition of [ISO/IEEE 11073-20601-2015A], the clear-segment using time range has been clarified. "For PM-segments cleared using the by time method, only PM-segments having Segment-Start-Abs-Time and Segment-End-Abs-Time fields entirely within the specified time period are cleared.", but if the PHG sends a Clear-Segment but the segment has not a Segment-Start-Abs-Time and Segment-End-Abs-Time within the specified time-period, the PHD will send a Roer message.</p> <p>At this point, it would be up to the PHD what error code (Roer message) to send (No-such-action, not-allowed-by-object, or both). If one wants to clear the segment due to all the internal timestamps that were saved in the segment as falling inside the given time period, then the PHD could do that. Returning an error is also possible.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|                 |                                                                         |                                                               |                   |
+|-----------------|-------------------------------------------------------------------------|---------------------------------------------------------------|-------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/OXP/DIM/BV-046                                               |                                                               |                   |
+| <b>TP label</b> | PM-Store object methods. Clear-Segments Base-Offset-Time Range method 2 |                                                               |                   |
+| <b>Coverage</b> | <b>Spec</b>                                                             | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                   |
+|                 | <b>Testable</b>                                                         | PM-StoreMeth 1; O                                             | PM-StoreMeth 2; C |
+|                 |                                                                         |                                                               | PM-StoreMeth 6; M |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                             |                             |                             |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|-----------------------------|-----------------------------|
+|                          | <b>items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | PM-StoreMeth 8; O           | PersStoreMtrDatTransf 20; M | PersStoreMtrDatTransf 21; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | PersStoreMtrDatTransf 22; O | PersStoreMtrDatTransf 23; M | PM-StoreMeth 32; M          |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | PM-StoreMeth 33; M          | PM-StoreMeth 23; C          | PersStoreMtrDatTransf 24; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If PHD supports the Clear-Segment (time range) method, then it responds to Clear-Segment requests with a Data APDU with an operation type rors-cmip-confirmed-action</p> <p>[AND]</p> <p>According to PM-Store-Capab attribute this method removes all entries from the specified PM-Segment, leaving it empty, or it removes the defined PM-Segment completely</p> <p>[AND]</p> <p>The Instance-Number of all other PM-Segments is unaffected by clearing a segment</p> <p>[AND]</p> <p>The PHD may support PM-segment clearing. If the PHD supports this function(indicated by the pmsc-clear-segm-all-sup, pmsc-clear-segm-by-list-sup, and pmsc-clear-segm-by-time-sup flags in the PM-Store-Capab attribute being set) then it may support the time range selection criteria (pmsc-clear-segm-by-time-sup)</p> <p>[AND]</p> <p>For PM-segments cleared using the by time method and using base time with offset, only PM-Segments having Segment-Start-BO-Time and Segment-End-BO-Time fields entirely within the specified time period are cleared. In using Segment-Start-BO-Time and Segment-End-BO-Time, the base time shall have a valid time (i.e., a non-zero value). If the offset field has a value 0x7FFF (32767), then only PM-segments having base time entirely within the specified base time period are cleared, otherwise for any other value of offset field only PM-segments having local time (base time with offset added) entirely within the specified time period are cleared.</p> <p>[AND]</p> <p>If the PHG invokes the Clear-Segments method but the PHD does not support the particular action (list of segments or range of segments), then the PHD shall respond with a roer DataApdu with a RoerErrorValue of "not-allowed-by-object".</p> |                             |                             |                             |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_071 AND C_AG_OXP_014 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                             |                             |                             |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                             |                             |                             |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state and the PHD has at least one PM-Segment with data stored.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                             |                             |                             |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Make sure the PHD is not taking measures which are stored in PM-Segments.</li> <li>2. 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.</li> <li>3. The PHD issues a GET response with the PM-Store attributes, record the values of the PM-Store-Capab attribute: <ol style="list-style-type: none"> <li>a. PM-Store-Capab: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li> <li><input type="checkbox"/> attribute-type = PmStoreCapab</li> <li><input type="checkbox"/> attribute-value = Record the value of bit 8 (Indicates that PM-Segments in the SegmSelection data type can be cleared by defining a TimeRange)</li> </ul> </li> </ol> <p>IF bit 8 of PMStoreCapab was set:</p> </li> <li>4. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection set to all-segments.</li> <li>5. The PHD issues a response (rors-cmip-confirmed-action) with the PM-Segment attributes it supports, record the attributes "Segment-Start-BO-Time" and "Segment-BO-Abs-Time" of every PM-Segment.</li> <li>6. The simulated PHG sends a Clear-Segment:</li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                             |                             |                             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ol style="list-style-type: none"> <li style="margin-left: 2em;">a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> <li><input type="checkbox"/> SegmSelection = bo-time-range, selecting a range with its boundaries set to Segment-Start-BO-Time and to Segment-End-BO-Time of one of the PM-Segments.</li> </ul> </li> <li>7. The PHD under test operation response: <ol style="list-style-type: none"> <li style="margin-left: 2em;">a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Response   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> </ul> </li> </ol> </li> <li>8. Delay.</li> <li>9. The simulated PHG sends a request for the PM-Segment Data of one of the cleared PM-Segments: <ol style="list-style-type: none"> <li style="margin-left: 2em;">a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> SegmSelection = &lt;Instance number of the selected PM-Segment that contained data before the clear-segment action in step 6&gt;</li> </ul> </li> </ol> </li> <li>10. The PHD issues an action response with the Data <ol style="list-style-type: none"> <li style="margin-left: 2em;">a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> TrigSegmXferRsp = <ul style="list-style-type: none"> <li>▪ IF pmsc-clear-segm-remove(9) = 0 THEN TrigSegmXferRsp = tsxr-fail-segm-empty ELSE TrigSegmXferRsp = tsxr-fail-no-such-segment</li> </ul> </li> </ul> </li> </ol> </li> </ol> <p>IF bit 8 of PMStoreCapab was NOT set</p> <ol style="list-style-type: none"> <li>11. Simulated PHG sends a Clear-Segment: <ol style="list-style-type: none"> <li style="margin-left: 2em;">a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> <li><input type="checkbox"/> SegmSelection = bo-time-range, selecting a range with its boundaries set to the a minimum of Base-Offset-Time type and to the absolute of the Base-Offset-Time type</li> </ul> </li> </ol> </li> <li>12. The PHD under test operation response: <ol style="list-style-type: none"> <li style="margin-left: 2em;">a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Roer</li> <li><input type="checkbox"/> ErrorResult = no-allowed-by-object (24)</li> </ul> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 7 the PHD must send a confirmation</li> <li>• In step 10 the TrigSemgXferRsp must be the specified</li> <li>• If the PHD does not support Clear-Segment by time, the PHD must send roer (not-allowed-by -object)</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+### A.3 Subgroup 1.2.2 – PHD service model (SER)
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                |
+|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|
+| <b>TP Id</b>        | TP/PLT/PHD/OXP/SER/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                |
+| <b>TP label</b>     | Object Access Services: No-Such-Action Error                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | ObjAccessServ 3; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | DataTrans 2; O |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | PersStoreMtrDatTransf 24; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | MDSMethod 6; M |
+|                     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [b-ITU-T H.810 (2015)]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                |
+| <b>Test purpose</b> | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | General 2; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                |
+|                     | <p>Check that:</p> <p>If a request for a confirmed action is received by a PHD that does not support the action, the PHD replies with an error (roer) value of no-such-action</p> <p>[AND]</p> <p>If the PHG invokes the Clear-Segments method but the PHD does not support this function at all then the PHD shall respond with a roer DataApdu with an RoerErrorValue of “no-such-action”.</p> <p>[AND]</p> <p>If the PHD supports Set-Time, it shall respond with a rors-cmip-confirmed-action. If the PHD does not support Set-Time, it shall respond with a no-such-action error (roer).</p> <p>[AND]</p> <p>If the PHD does not support Set-Base-Offset-Time, it shall respond with a no-such-action error (roer)</p> <p>[AND]</p> <p>PHD shall not include the Base Offset Time in any Continua configurations except for Basic electrocardiograph (ECG) and Insulin Pump (IP) device specializations.</p> |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                |
+|                     | <b>Applicability</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                |
+|                     | <b>Other PICS</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | C_AG_OXP_008, C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_071                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                |
+|                     | <b>Initial condition</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                |
+|                     | <b>Test procedure</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | <ol style="list-style-type: none"> <li>The simulated PHG sends a roiv-cmip-confirmed-action with action-type = MDC_ACT_DATA_REQUEST.</li> <li>The PHD under test shall reply with an error. The expected fields sent by the PHD are:               <ol style="list-style-type: none"> <li>Error-value                   <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = INT-U16</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field- value = no-such-action(9)</li> </ul> </li> </ol> </li> <li>IF the PHD under test does not support Set Time (i.e., C_AG_OXP_008 = FALSE) OR the PHD under test supports Set Time for Base-Offset-Time (i.e., C_AG_OXP_008 = TRUE and C_AG_OXP_014 = TRUE) THEN the simulated PHG sends a roiv-cmip-confirmed-action with action-type = MDC_ACT_SET_TIME using Absolute-Time (SetTimeInvoke).</li> <li>The PHD under test shall reply with an error. The expected fields sent by the PHD are:               <ol style="list-style-type: none"> <li>Error-value                   <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = INT-U16</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field- value = no-such-action(9)</li> </ul> </li> </ol> </li> <li>IF the PHD under test does not support Set Time (i.e., C_AG_OXP_008 = FALSE) OR the PHD under test supports Set Time for Absolute-Time Time (i.e., C_AG_OXP_008 = TRUE and C_AG_OXP_009 = TRUE) THEN the PHG sends a roiv-cmip-confirmed-action with action-type = MDC_ACT_SET_BO_TIME using Base-Offset-Time</li> </ol> |                |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>(SetBOTimeInvoke).</p> <p>6. The PHD under test shall reply with an error. The expected fields sent by the PHD are:</p> <p>a. Error-value</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = INT-U16</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field- value = no-such-action(9)</li> </ul> <p>7. IF C_AG_OXP_041 and does not support the Clear-Segment action then the simulated PHG sends a roiv-cmip-confirmed-action with action-type = MDC_ACT_SEG_CLR.</p> <p>8. The PHD under test shall reply with an error. The expected fields sent by the PHD are:</p> <p>a. Error-value</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = INT-U16</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field- value = no-such-action(9)</li> </ul> <p>9. IF C_AG_OXP_041 and it does not support selection by time range THEN the simulated PHG sends a roiv-cmip-confirmed-action with action-type = MDC_ACT_SEG_GET_INFO and SegmSelection = abs-time-range (if the PHD supports Absolute Time) or SegmSelection = bo-time-range (if the PHD supports Base Offset Time)</p> <p>10. The PHD under test shall reply with an error. The expected fields sent by the PHD are</p> <p>a. Error-value</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = INT-U16</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field- value = no-such-action(9)</li> </ul> |
+| <b>Pass/Fail criteria</b> | The PHD under test sends a No-Such-Action Error and the invoke-id is mirrored from the roiv-cmip-* messages.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                      |
+|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|----------------------|
+| <b>TP Id</b>        | TP/PLT/PHD/OXP/SER/BV-001                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                      |
+| <b>TP label</b>     | Configuration event report: dev-configuration-id is locally unique                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                      |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                      |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | ConfEventRep 2; C                                             | ConfEventRep 6; M    |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | ConfEventRep 24; M                                            | ConfEventRep 25; R   |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | ConfNormalProc 14;M                                           | ConfExitCond 4; C    |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | AgentStateMach 79; M                                          | ConfNormalProc 25; R |
+| <b>Test purpose</b> | <p>Check that:</p> <p>If PHD has multiple device configurations, the assigned Dev-Configuration-Id values are locally unique</p> <p>[AND]</p> <p>The PHD transfers its configuration the PHG using a configuration event report</p> <p>[AND]</p> <p>The PHD consistently uses the Dev-Configuration-Id for subsequent associations.</p> <p>[AND]</p> <p>If the PHD receives an unsupported configuration message, the PHD sends a further configuration. This process is repeated until the PHD has attempted all configurations. When it sends an Association Release message with a reason code of no-more-configurations to indicate that it is unable to operate with the PHG the PHD moves to Disassociating state.</p> <p>[AND]</p> <p>The same Dev-Configuration-Id shall not be used by an PHD for subsequent associations to identify a different device configuration.</p> |                                                               |                      |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>[AND]</p> <p>An PHD should use the same value for Dev-Configuration-Id in future Association Requests with the PHG to denote the same configuration of the device.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The PHD under test sends an Association Request to the simulated PHG. The expected fields sent by the PHD are: <ol style="list-style-type: none"> <li>a. dev-config-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = ConfigId</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field- value = Record it for comparison</li> </ol> </li> <li>b. Data-Req-Mode-Capab: <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 4 bytes</li> <li><input type="checkbox"/> field- value = 0xXX 0xXX 0x01 0xXX (Agent initiated)</li> </ol> </li> </ol> </li> <li>2. The simulated PHG responds with an accepted-unknown-config.</li> <li>3. The PHD sends a configuration event report, with the following fields: dev-config-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = ConfigId</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field- value = &lt;Record this Value&gt;</li> </ol> </li> <li>4. The simulated PHG responds with an unsupported-configuration.</li> <li>5. The PHD sends a new configuration event report with a new configuration (if it has more).</li> <li>6. Repeat the last two steps recording all the ConfigId-values until the PHD sends a ReleaseRequest with the reason "no-more-configurations" and the PHD moves to the Disassociating state.</li> <li>7. The simulated PHG responds with a Release Response message.</li> <li>8. Wait for the PHD under test to send an Association Request.</li> <li>9. Repeat steps 2 to 5 until the PHD under test sends a Release Request with the reason "no-more-configurations".</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• Dev-config-id is the same for the two first messages and every other ConfigId must be different from all others before the Release Request of step 6</li> <li>• The PHD shall send a Release-request (no-more-configurations) in step 6</li> <li>• Verify that the PHD should use the same Dev-Config-Id in steps 2 – 5 and that in step 9 and in every received configuration in step 9 it is the same as one of the received in the configuration messages in step 3</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/SER/BV-001_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>TP label</b>           | Configuration event report: Maximum Size                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | CommonCharac 3; M                                             |  |
+| <b>Test purpose</b>       | Check that:<br><br>The total size of the response does not exceed the maximum APDU size established by the specialization                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |  |
+| <b>Other PICS</b>         | C_AG_OXP_041                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |  |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The PHD under test sends an Association Request to the simulated PHG.</li> <li>2. The simulated PHG responds with an "accepted-unknown".</li> <li>3. The PHD under test sends its configuration with an event report. Record the size of the event report.</li> <li>4. The simulated PHG responds with an unsupported-configuration.</li> <li>5. The PHD under test sends a new configuration event report with a new configuration (if it has more). Record the size of the event report.</li> <li>6. Repeat the last two steps recording all the ConfigId-values until the PHD sends a ReleaseRequest with the reason "no-more-configurations".</li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• 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): <ul style="list-style-type: none"> <li>○ Pulse oximeter → 9216 octets</li> <li>○ Weighing scales → 896 octets</li> <li>○ Glucose meter → 5120 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ Blood pressure → 896 octets</li> <li>○ Thermometer → 896 octets</li> <li>○ Independent activity hub → 5120 octets</li> <li>○ Cardiovascular → 64512 octets or 6624 octets if the PHD supports Step Counter Profile</li> <li>○ Strength → 64512 octets</li> <li>○ Adherence monitor → 1024 octets</li> <li>○ Peak flow → 2030 octets</li> <li>○ Body composition analyser → 7730 octets</li> <li>○ Basic ECG/Simple ECG → 7168 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ Basic ECG/Heart rate → 1280 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ International normalized ratio → 896 octets or 64512 if the PHD supports PM-Store</li> <li>○ Insulin pump → 7168 octets or 5120 if PHD supports PM-Store</li> <li>○ Continuous glucose monitor → 896 octets or 5120 if PHD supports PM-Store</li> <li>○ Power status monitor → 940 octets for Simple PSM profile or 1660 for Advanced PSM profile</li> </ul> </li> </ul> |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                                            |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/SER/BV-002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |                                            |
+| <b>TP label</b>           | Configuration event report: Change attributes values                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                                            |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                                            |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ConfEventRep 10; O                                            | ConfEventRep 13; M      ConfEventRep 14; M |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>If the PHD adds new attributes to an object or changes attribute values during the association, then it does not send a new configuration.</p> <p>[AND]</p> <p>In subsequent associations, when a previously used Dev-Configuration-Id is specified, the configuration being referenced does not include any changes made during a prior association.</p> <p>[AND]</p> <p>The PHD only makes persistent changes to a configuration by re-associating and specifying a different Dev-Configuration-Id and the new configuration desired at configuration time</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                                            |
+| <b>Applicability</b>      | C_AG_OXP_098 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                                            |
+| <b>Other PICS</b>         | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                                            |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                                            |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The PHD under test sends an Association Request to the simulated PHG.</li> <li>2. The simulated PHG responds with an accepted-unknown-config.</li> <li>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.</li> <li>4. If ConfigId (ConfigReport) matches the tested configuration, the simulated PHG responds with "accepted-config" and records the ConfigReport received in step 3.</li> <li>5. IF C_AG_OXP_293 THEN: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ol> </li> <li>6. Wait for the PHD under test to reach Operating state.</li> <li>7. Make a change to the attribute or add it.</li> <li>8. Check that the event report informing about the attribute change or addition is received.</li> <li>9. Send a release-request to the PHD under test with reason normal (0).</li> <li>10. Make the PHD try to re-associate.</li> <li>11. The simulated PHG responds with an accepted-unknown-config.</li> <li>12. Check the attribute that has been changed or added is not present when the PHD sends the ConfigReport.</li> </ol> |                                                               |                                            |
+| <b>Pass/Fail criteria</b> | Changes made to the attribute must not be present in the second association.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                                            |
+| <b>Notes</b>              | The attribute that is changed in step 7 must be an attribute whose "initial" value is defined in the ConfigReport.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                     |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/SER/BV-004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                     |
+| <b>TP label</b>          | PHD transmits data in a fixed format Event Report                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | FormatEventRep 1; M                                           | FormatEventRep 4; O |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | FormatEventRep 6; M                                           | FormatEventRep 7; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               | PersonEventRep 2; O |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If PHD transmits data in fixed format, then it reports the object handle and the attribute values are in the same order and size as specified in the Attribute-Value-Map</p> <p>[AND]</p> <p>These Attribute-Value-Map attribute shall be defined and transmitted to the PHG before fixed format event report transfer commences</p> <p>[AND]</p> <p>The order of these elements is defined by the order in which the attribute identifiers are listed in the Attribute-Value-Map. The PHD controls the order and communicates it to the PHG via the Attribute-Value-Map attribute</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                     |
+| <b>Applicability</b>     | (C_AG_OXP_182 OR C_AG_OXP_183 OR C_AG_OXP_184) AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                     |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                     |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Configuring state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                     |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The PHD under test sends its configuration to the simulated PHG. Save the number of measurement objects (config-obj-list.count=n).</li> <li>2. Every measurement object has an obj-handle and one or more attributes. The objects of interest for this test cases are all the metric derived ones (Obj-class=MDC_MOC_VMO_METRIC_ENUM 0x00 0x05, Obj-class=MDC_MOC_VMO_METRIC_NU 0x00 0x06, or Obj-class=MDC_MOC_VMO_METRIC_SA_RT 0x00 0x09). For each of them, check: <ol style="list-style-type: none"> <li>a. Attribute Attribute-Val-Map <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP (0x0A 0x55)</li> <li><input type="checkbox"/> AttrValMap.count = N (number of objects for this measurement object)</li> <li><input type="checkbox"/> AttrValMap.length = L</li> </ol> </li> <li>b. For each attribute (of the N present) check the ID and the length at which it will be transmitted <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type=MDC_ATTR_*</li> <li><input type="checkbox"/> field-value=0xXX 0xXX, where the length will be declared (K).</li> </ol> </li> </ol> </li> <li>3. IF C_AG_OXP_293 THEN: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ol style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 THEN it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ol> </li> </ol> </li> <li>4. Wait for the PHD under test to reach the Operating state and take some measurements.</li> <li>5. When the PHD under test sends an event report to the simulated PHG with measurement observations, check the following: <ol style="list-style-type: none"> <li><input type="checkbox"/> event-type= MDC_NOTI_SCAN_REPORT_FIXED (0X0D 0X1D)</li> </ol> </li> </ol> |                                                               |                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> ObservationScanFixed.count= P (where P&lt;=N, and it is the number of objects reported in this event report)</li> <li><input type="checkbox"/> obj-handle = &lt;It has to be the same that obj-handle of the Measurement object sent in the PHD's configuration&gt;</li> <li><input type="checkbox"/> obs-val-data.length= 0xXX 0xXX, where the value is the length "K".</li> <li><input type="checkbox"/> The actual observed measurement value will come in the next field, but this value is of no interest for this test case</li> </ul> <p>IF the Absolute-Time attribute is present in the Attribute-Val-Map THEN:</p> <ol style="list-style-type: none"> <li>6. Record the value of the received Time Stamp</li> <li>7. 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.</li> <li>8. 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, record the Date-and-Time value.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The Fixed Event report contains the same list of attributes (and sizes) in the same order that was declared in the configuration message</li> <li>• The Time Stamp and Date-and-Time values are coherent</li> <li>• The Attr-Val-Map for an object has to be received prior to the measurement (Config Report or MDS Event Report)</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                     |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/SER/BV-004_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                     |
+| <b>TP label</b>          | PHD transmits data in variable format Event Report                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | FormatEventRep 4; O                                           | PersonEventRep 2; O |
+| <b>Test purpose</b>      | Check that:<br>If PHD transmits data in variable format, then the event report fits to specified format                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                     |
+| <b>Applicability</b>     | C_AG_OXP_189 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                     |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                     |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                     |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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 the attribute Attribute-Value-Map.</li> <li>4. IF C_AG_OXP_293 THEN: <ul style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 THEN it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ul> </li> </ol> |                                                               |                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>5. Once in the Operating state take a measurement with the PHD under test.</p> <p>6. Wait for the event report from the PHD under test.</p> <p>7. When the PHD under test sends an event report to the simulated PHG with measurement observations, check the following:</p> <ul style="list-style-type: none"> <li>a. If the data is from a single person <ul style="list-style-type: none"> <li><input type="checkbox"/> Event-type = MDC_NOTI_SCAN_REPORT_VAR</li> <li><input type="checkbox"/> Event-info parameter = ScanReportInfoVar</li> <li><input type="checkbox"/> attribute.identification-field = &lt;Variable&gt;</li> <li><input type="checkbox"/> Value-length = &lt;Variable&gt;</li> <li><input type="checkbox"/> Value = &lt;Not relevant for this Test&gt;</li> </ul> </li> <li>b. If the data is from multiple persons <ul style="list-style-type: none"> <li><input type="checkbox"/> Event-type = MDC_NOTI_SCAN_REPORT_MP_VAR</li> <li><input type="checkbox"/> Event-info parameter = ScanReportInfoMPVar</li> <li><input type="checkbox"/> attribute.identification-field = &lt;Variable&gt;</li> <li><input type="checkbox"/> Value-length = &lt;Variable&gt;</li> <li><input type="checkbox"/> Value = &lt;Not relevant for this Test&gt;</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• Variable format event report contains the listed fields.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                     |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/SER/BV-005                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                     |
+| <b>TP label</b>          | PHD transmits data in a grouped format Event Report (Scanner Objects)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | FormatEventRep 2; M                                           | PersonEventRep 2; O |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ConfNormalProc 4; M                                           | FormatEventRep 8; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If PHD transmit data in a grouped format, then it reports the scanner object's handle along with the scanned objects' attribute values in the same order and size as specified in the Scan-Handle-Attr-Val-Map</p> <p>[AND]</p> <p>This attribute (Scan-Handle-Attr-Value-Map) shall be defined before grouped event report transfer commences.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                     |
+| <b>Applicability</b>     | (C_AG_OXP_046 OR C_AG_OXP_047) AND C_AG_OXP_048 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                     |
+| <b>Other PICS</b>        | C_AG_OXP_041 , C_AG_OXP_180                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                     |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Configuring state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                     |
+| <b>Test procedure</b>    | <p>1. When the PHD under test sends its configuration to the simulated PHG, the number of the measurement object (config-obj-list.count=n) must be saved.</p> <p>2. Every measurement object has an obj-handle and one or more attributes:</p> <ul style="list-style-type: none"> <li>a. Attribute Scan-Handle-Value-Map <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SCAN_HANDLE_ATTR_VAL_MAP (0x0A 0x53)</li> <li><input type="checkbox"/> HandleAttrValMap.count = N (number of object for this measurement object)</li> <li><input type="checkbox"/> HandleAttrValMap.length = L</li> </ul> </li> <li>b. For each attribute (of the L present) its length is needed: <ul style="list-style-type: none"> <li><input type="checkbox"/> HandleAttrValMap = &lt;One of an actual metric derived object&gt;</li> <li><input type="checkbox"/> HandleAttrValMap.count = K (number attributes of this object)</li> <li><input type="checkbox"/> HandleAttrValMap.length = M</li> </ul> </li> </ul> |                                                               |                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>3. The sum of the length values is the total length of the measurement data for this object, in this case, the sum of all the M's</p> <p>4. When the PHD under test sends an event report to the simulated PHG with a measurement observation, the format of this message is:</p> <p>a. PrstApdu (0xE7 0x00)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> obj-handle = &lt;It has to be the same that obj-handle of the Measurement object sent in the PHD's configuration&gt;</li> <li><input type="checkbox"/> event-type = MDC_NOTI_BUF_SCAN_REPORT_GROUPED or MDC_NOTI_UNBUF_SCAN_REPORT_GROUPED</li> <li><input type="checkbox"/> grouped-length = L &lt;This length has to be the same as the total length of the measurement data for this object, it is the sum calculated when the PHD sent its configuration&gt;</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The metric derived objects must appear in the event report in the same order as were declared on the configuration report. The length of the event report must match the length indicated by the Handle-Attribute-Value-Map and cannot exceed the maximum APDU size established by the specialization: <ul style="list-style-type: none"> <li>○ Pulse oximeter → 9216 octets</li> <li>○ Weighing scales → 896 octets</li> <li>○ Glucose meter → 5120 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ Blood pressure → 896 octets</li> <li>○ Thermometer → 896 octets</li> <li>○ Independent activity hub → 5120 octets</li> <li>○ Cardiovascular → 64512 octets or 6624 octets if it supports Step Counter Profile</li> <li>○ Strength → 64512 octets</li> <li>○ Adherence monitor → 1024 octets</li> <li>○ Peak flow → 2030 octets</li> <li>○ Body composition analyser → 7730 octets</li> <li>○ Basic ECG/Simple ECG → 7168 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ Basic ECG/Heart rate → 1280 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ International normalized ratio → 896 octets or 64512 if the PHD supports PM-Store</li> <li>○ Insulin pump → 7168 octets or 5120 if PHD supports PM-Store</li> <li>○ Continuous glucose monitor → 896 octets or 5120 if PHD supports PM-Store</li> <li>○ Power status monitor → 940 octets for Simple PSM profile or 1660 for Advanced PSM profile</li> </ul> </li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                     |                                                                                                                                                                                                                                                                                                                          |                                                               |                 |
+|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------|
+| <b>TP Id</b>        | TP/PLT/PHD/EXP/SER/BV-007                                                                                                                                                                                                                                                                                                |                                                               |                 |
+| <b>TP label</b>     | Temporarily Stored Measurements                                                                                                                                                                                                                                                                                          |                                                               |                 |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                 |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                    | TempStored 1; O                                               | TempStored 2; C |
+|                     |                                                                                                                                                                                                                                                                                                                          | TempStored 7; R                                               | TempStored 8; M |
+| <b>Test purpose</b> | <p>Check that:</p> <p>Only Metric derived objects that are not real time arrays (Numeric and Enumeration objects) are supported as Temporarily Stored Measurements</p> <p>[AND]</p> <p>Temporarily Stored Measurements requires the use of time stamp attributes (Date-and-Time, Relative-Time, HiRes-Relative-Time)</p> |                                                               |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>[AND]</p> <p>The PHD ensures ownership of the measurements is successfully transferred to the PHG by using confirmed event reports</p> <p>[AND]</p> <p>the PHD does not provide more than 25 Temporarily Stored Measurements in order to limit the amount of data transported by this mechanism</p> <p>[AND]</p> <p>The total size of the response does not exceed the maximum APDU size established by the specialization</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Applicability</b>      | C_AG_OXP_032 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Other PICS</b>         | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_041, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The PHD under test takes more than 25 measurements before connecting to the simulated PHG.</li> <li>2. The PHD under test gets connected to the simulated PHG. The Metric-Spec-Small attribute sent in ConfigReport is recorded for numeric and enumeration objects.</li> <li>3. IF C_AG_OXP_293 THEN: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 THEN it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ol> </li> <li>4. Once in the Operating state, check that: <ol style="list-style-type: none"> <li>a. No more than 25 Temporary Stored Measurements are sent in the same event report.</li> <li>b. That the event reports used to transmit the measurements should be confirmed.</li> <li>c. That every Temporary Stored Measurement sent has a Time Stamp attribute (Date-and-Time, Relative-Time, HIRes-Relative-Time or Base-Offset-Time)</li> <li>d. Data sent is Enumerated or Numeric.</li> <li>e. Metric-Spec-Small – mss-avail-stored-data bit is set.</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The conditions in step 4 are met</li> <li>• 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): <ul style="list-style-type: none"> <li>○ Pulse oximeter → 9216 octets</li> <li>○ Weighing scales → 896 octets</li> <li>○ Glucose meter → 5120 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ Blood pressure → 896 octets</li> <li>○ Thermometer → 896 octets</li> <li>○ Independent activity hub → 5120 octets</li> <li>○ Cardiovascular → 64512 octets or 6624 octets if the PHD supports Step Counter Profile</li> <li>○ Strength → 64512 octets</li> </ul> </li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+|              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|              | <ul style="list-style-type: none"> <li>○ Adherence monitor → 1024 octets</li> <li>○ Peak flow → 2030 octets</li> <li>○ Body composition analyser → 7730 octets</li> <li>○ Basic ECG/Simple ECG → 7168 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ Basic ECG/Heart rate → 1280 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ International normalized ratio → 896 octets or 64512 if the PHD supports PM-Store</li> <li>○ Insulin pump → 7168 octets or 5120 if PHD supports PM-Store</li> <li>○ Continuous glucose monitor → 896 octets or 5120 if PHD supports PM-Store</li> <li>○ Power status monitor → 940 octets for Simple PSM profile or 1660 for Advanced PSM profile</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b> | <p>It is possible that the PHD supports Temporarily Stored Measurements (TSM) for a set of objects and that it does not support TSM for other set of objects.</p> <p>The test tool identifies the objects that support TSM using the Metric-Spec-Small attribute – mss-avail-stored-data(1) bit. When this bit is set to 1 in one object, the test tool assumes that this object stores TSM, although it is not totally sure because this bit is "informational".</p> <p>From [ISO/IEEE 11073-20601-2015A] clause A.11.3:</p> <ul style="list-style-type: none"> <li>• IF object stores TSM THEN mss-avail-stored-data(1) SHALL be set to 1</li> <li>• IF object does not store TSM THEN mss-avail-stored-data(1) MAY be set to 1 or 0</li> </ul> <p>If the PHD under test sets mss-avail-stored-data(1) bit to 1 for one object but this object does not store TSM and the PHD does not include the time stamp in event report, the test tool gives a FAIL verdict since the test tool identifies that this object stores TSM. When the vendor implements this behaviour in a device, a waiver may be required to complete the Certification. See Bugzilla #840 and contact Continua TOM for further details (<a href="http://continua.plugfest.com/show_bug.cgi?id=840">http://continua.plugfest.com/show_bug.cgi?id=840</a>).</p> |
+
+### A.4 Subgroup 1.2.3 – PHD communication model (COM)
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                  |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/COM/BV-003_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                  |
+| <b>TP label</b>          | Communication Characteristics: Reliable virtual channel 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | CommuCharac 2; M                                              | CommuCharac 3; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The “reliable” virtual channel (i.e. a “reliable” transport service) of the Type 1 transport profiles is used for all messages related to the association procedure: aarq, rlre</p> <p>[AND]</p> <p>The “reliable” virtual channel (i.e. a “reliable” transport service) of the Type 1 transport profiles is used for all messages related to the Confirmed service mechanism (prst.roiv-cmip-confirmed-action, prst.roiv-cmip-confirmed-event-report, prst.roiv-cmip-get, prst.roiv-cmip-confirmed-set) (prst.rors-cmip-confirmed-action, prst.rors-cmip-confirmed-event-report, prst.rors-cmip-get, prst.rors-cmip-confirmed-set)</p> |                                                               |                  |
+| <b>Applicability</b>     | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                  |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                  |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The PHD under test sends an Association Request to the simulated PHG.</li> <li>2. The simulated PHG sends an Association Response with result = accepted-unknown-config.</li> <li>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.</li> <li>4. IF C_AG_OXP_293 THEN:</li> </ol>                                                                                                                                                                                                                 |                                                               |                  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set:               <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and:                   <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 THEN it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ol> <ol style="list-style-type: none"> <li>5. Wait until the PHD under test reaches the Operating state.</li> <li>6. 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.</li> <li>7. The PHD responds with a "rors-cmip-get".</li> <li>8. IF C_AG_OXP_041 THEN               <ol style="list-style-type: none"> <li>a. The simulated PHG sends a Get request for the PM-Store with an attribute-id-list set to 0 to indicate all PM-Store attributes.</li> <li>b. The PHD under test issues a GET response.</li> <li>c. 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.</li> <li>d. The PHD under test issues a "rors-cmip-confirmed-action" response.</li> </ol> </li> <li>9. IF (C_AG_OXP_046 OR C_AG_OXP_047) THEN               <ol style="list-style-type: none"> <li>a. The simulated PHG sends a "roiv-cmip-confirmed-set" to set the OperationalState of the scanner object to 1.</li> <li>b. The PHD under test responds with a "rors-cmip-set".</li> </ol> </li> <li>10. The simulated PHG sends a Release Request to the PHD under test with reason = normal(0).</li> <li>11. The PHD under test responds with a Release Response.</li> </ol> |
+| <b>Pass/Fail criteria</b> | The "reliable" virtual channel must be used in steps 1, 3, 7, 8.b, 8.d, 9.b and 11.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                          |                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/EXP/COM/BV-003_B                                                                                                                                                                                                                                                                                                 |                                                               |  |
+| <b>TP label</b>          | Communication Characteristics: Reliable virtual channel 2                                                                                                                                                                                                                                                                   |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                       | CommuCharac 2; M                                              |  |
+| <b>Test purpose</b>      | Check that:<br><br>The "reliable" virtual channel (i.e. a "reliable" transport service) of the Type 1 transport profiles is used for all messages related to the association procedure: rlrq                                                                                                                                |                                                               |  |
+| <b>Applicability</b>     | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The PHD under test sends an Association Request from the PHD under test.</li> <li>2. The simulated PHG sends an Association Response with result = accepted-unknown-config.</li> <li>3. The PHD under test responds with a "Remote Operation Invoke   Confirmed Event"</li> </ol> |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>Report" message with an MDC_NOTI_CONFIG event to send its configuration to the simulated PHG.</p> <p>4. The simulated PHG responds with a "unsupported-config", waits for a new configuration and keeps responding with "unsupported-config" to every new configuration.</p> <p>5. The PHD under test sends a Release Request.</p> |
+| <b>Pass/Fail criteria</b> | The "reliable" virtual channel must be used for the Release Request.                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                       |
+
+|                           |                                                                                                                                                                                                     |                                                               |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-003_C                                                                                                                                                                         |                                                               |
+| <b>TP label</b>           | Communication Characteristics: Reliable virtual channel 3                                                                                                                                           |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                         | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                               | CommuCharac 2; M                                              |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>The "reliable" virtual channel (i.e. a "reliable" transport service) of the Type 1 transport profiles is used for all messages related to the association procedure: abrt</p> |                                                               |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                        |                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                     |                                                               |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                    |                                                               |
+| <b>Test procedure</b>     | <p>1. The simulated PHG sends a Release Response to the PHD under test.</p> <p>2. The PHD responds with an Abort message.</p>                                                                       |                                                               |
+| <b>Pass/Fail criteria</b> | The "reliable" virtual channel must be used for the Abort message.                                                                                                                                  |                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                     |                                                               |
+
+|                           |                                                                                                                                                                                                        |                                                               |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-003_D                                                                                                                                                                            |                                                               |
+| <b>TP label</b>           | Communication Characteristics: Reliable virtual channel 4                                                                                                                                              |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                            | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                                  | CommuCharac 4; M                                              |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>The "reliable" virtual channel (i.e. a "reliable" transport service) of the Type 1 transport profiles is used for all messages related to fault or abnormal conditions: roer</p> |                                                               |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                           |                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                        |                                                               |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                       |                                                               |
+| <b>Test procedure</b>     | <p>1. The simulated PHG sends a roiv-cmip-confirmed-action with action-type = MDC_ACT_DATA_REQUEST.</p> <p>2. The PHD under test shall reply with a "roer" with reason = no-such-action (9).</p>       |                                                               |
+| <b>Pass/Fail criteria</b> | The "reliable" virtual channel must be used for the "roer" message.                                                                                                                                    |                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                        |                                                               |
+
+|                 |                                                   |                                                               |
+|-----------------|---------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/OXP/COM/BV-006_A                       |                                                               |
+| <b>TP label</b> | Agent State machine. Accepted known configuration |                                                               |
+| <b>Coverage</b> | <b>Spec</b>                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                 | <b>Testable items</b>                             | AgentStateMach 21; M                                          |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>       | Check that:<br><br>If aare(accepted) is received while in the Associating state, then the PHD under test moves to the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Applicability</b>      | C_AG_OXP_000 AND (C_AG_OXP_291 OR C_AG_OXP_292)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test (the PHD passes to the Associating state).</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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 simulated PHG. The configuration report is reported.</li> <li>4. The simulated PHG sends an abort message.</li> <li>5. The simulated PHG and the PHD move to the Unassociated state.</li> <li>6. The simulated PHG receives an association request from the PHD under test.</li> <li>7. The simulated PHG responds with a result = accepted.</li> <li>8. The PHD must change to the Operating state. <ul style="list-style-type: none"> <li>• IF the PHD supports the Scanner object: The simulated PHG sends a Set command for the Scanner object and the PHD shall reply.</li> <li>• ELSE IF the PHD under test supports PM-Store, the simulated PHG sends a Get Segment Info action and the PHD shall reply.</li> <li>• ELSE the simulated PHG waits to receive measurements from the PHD.</li> </ul> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The PHD under test has passed to the Operating state after the last step.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                    |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/COM/BV-006_B                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                    |
+| <b>TP label</b>          | Agent State machine                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                    |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                    |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | AgentStateMach 64; M                                          | ObjAccessServ 4; C |
+| <b>Test purpose</b>      | Check that:<br><br>If roiv-* is received while in the Operating state, then the PHD transmits a (rors-*, roer-*, or rorj-*) and remains in the same state.<br><br>[AND]<br><br>If an error occurs in executing a confirmed action, then the error shall be indicated by returning an error (roer) with an appropriate error value and, where appropriate, additional information on the error may be included in the parameter field using one of the return codes from the return codes partition.                                                                                                                                         |                                                               |                    |
+| <b>Applicability</b>     | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                    |
+| <b>Other PICS</b>        | C_AG_OXP_071, C_AG_OXP_180                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                    |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                    |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG sends a "roiv-cmip-get" to the PHD, to get all the attributes for an MDS object.</li> <li>2. The PHD responds with a "rors-cmip-get" message.</li> <li>3. IF C_AG_OXP_180 THEN the simulated PHG sends a "roiv-cmip-confirmed-set", setting to default value the attribute Operational State for a scanner object.<br/><br/> IF NOT C_AG_OXP_180 THEN the simulated PHG sends a roiv-cmip-set, setting to default value the attribute Operational State for a scanner object.</li> <li>4. IF C_AG_OXP_180 THEN the PHD responds with a rors-cmip-confirmed-set if it</li> </ol> |                                                               |                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>supports a scanner object, otherwise it responds with a roer-* or rorj-*.</p> <p>IF NOT C_AG_OXP_180 the PHD does not respond if it supports a scanner object, otherwise it responds with a roer-* or rorj-*.</p> <ol style="list-style-type: none"> <li>5. The simulated PHG sends a "roiv-cmip-confirmed-action", action-type MDC_ACT_DATA_REQUEST.</li> <li>6. The PHD responds with a "rors-cmip-confirmed-action", "roer-*" or "rorj-*".</li> <li>7. The simulated PHG sends a "roiv-cmip-confirmed-action", action-type MDC_ACT_SET_TIME.</li> <li>8. The PHD responds with a "rors-cmip-confirmed-action", "roer-*" or "rorj-*".</li> <li>9. The simulated PHG sends a "roiv-cmip-confirmed-action", action-type MDC_ACT_SEG_GET_INFO.</li> <li>10. The PHD responds with a "rors-cmip-confirmed-action" if the PM-Store object is supported by the PHD, otherwise it responds with a "roer-*" or "rorj-*".</li> <li>11. The simulated PHG sends a "roiv-cmip-confirmed-action", action-type MDC_ACT_SEG_TRIG_XFER.</li> <li>12. The PHD responds with a "rors-cmip-confirmed-action" if the PM-Store object is supported by the PHD, otherwise, a "roer-*" or "rorj-*".</li> <li>13. The simulated PHG sends a "roiv-cmip-confirmed-action", action-type MDC_ACT_SEG_CLR (all-segments). If the PHD supports Clear-Segment action, THEN the test tool performs a GET request to read the Clear-Timeout attribute for Pm-Store.</li> <li>14. The PHD responds with a "rors-cmip-confirmed-action" if the PM-Store object is supported by the PHD and it supports Clear-Segment action, otherwise, a "roer-*" or "rorj-*".</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHD replies with messages specified in steps 2, 4, 6, 8, 10, 12 and 14 of the test procedure.</li> <li>• If the PHD sends a roer message, check that the error value is correct and that a parameter may be included.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                      |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|----------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/COM/BV-007                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                      |
+| <b>TP label</b>          | Agent State machine. Accepted unknown configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                      |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                      |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | AgentStateMach 22; M                                          | AgentStateMach 53; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ConfProc 1; M                                                 | ConfExitCond 3; M    |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If aare(accepted-unknown-config) is received while in the Associating state, then the PHD moves to "Sending Config" state. The PHG has accepted the association but it does not have a configuration.</p> <p>[AND]</p> <p>When a PHD receives a response that the configuration is unknown, it moves to the Configuring state and follow the procedures specified to transfer its configuration</p> <p>[AND]</p> <p>If a rors-cmip-confirmed-event-report (accepted-config) is received while in the Waiting Approval state, then the PHD moves to the Operating state.</p> |                                                               |                      |
+| <b>Applicability</b>     | C_AG_OXP_000 AND (C_AG_OXP_291 OR C_AG_OXP_292)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                      |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                      |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Unassociated state                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                      |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test (the PHD passes to the Associating state).</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> </ol>                                                                                                                                                                                                                                                                                                                                         |                                                               |                      |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>3. The PHD under test shall go to the "Sending Config" substate, and responds with a "Remote Operation Invoke   Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG (the PHD shall go to the "waiting-approval" substate).</p> <p>4. The simulated PHG sends a "Remote Operation Response   Confirmed Event Report" with result "accepted-config".</p> <p>5. The PHD under test shall move to the Operating state.</p> <ul style="list-style-type: none"> <li>• IF the PHD under test supports the Scanner object: The simulated PHG sends a Set command for the Scanner object and the PHD under test shall reply.</li> <li>• ELSE IF the PHD under test supports PM-Store the simulated PHG sends a Get Segment Info action and the PHD shall reply.</li> <li>• ELSE the simulated PHG waits for receiving measurements from the PHD under test.</li> </ul> |
+| <b>Pass/Fail criteria</b> | The PHD under test has passed to the Operating state after the last step.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                           |                                                                                                                                                                                                                                                                                 |                                                               |  |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-009                                                                                                                                                                                                                                                       |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Leaving the Operating State 1                                                                                                                                                                                                                              |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                           | AgentStateMach 59; M                                          |  |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>If aarq is received while in the Operating state, then the PHD transmits an abrt(Abort-reason undefined) and moves to Unassociated state.</p>                                                                                                             |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                 |                                                               |  |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                |                                                               |  |
+| <b>Test procedure</b>     | <p>1. The simulated PHG sends an Association Request to the PHD under test.</p> <p>2. The PHD under test responds with an Abort message abrt(Abort-reason undefined).</p>                                                                                                       |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHD transmits correctly the Abort message (abrt) with reason undefined and changes to the Unassociated state.</li> <li>• The simulated PHG must not receive any message other than an Association Request after step 2.</li> </ul> |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                 |                                                               |  |
+
+|                          |                                                                                                                                                                     |                                                               |  |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/COM/BV-010                                                                                                                                           |                                                               |  |
+| <b>TP label</b>          | Agent State machine. Leaving the Operating State 2                                                                                                                  |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                         | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                               | AgentStateMach 60; M                                          |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If aare is received while in Operating state, then the PHD transmits an abrt(Abort-reason undefined) and moves to the Unassociated state.</p> |                                                               |  |
+| <b>Applicability</b>     | C_AG_OXP_000                                                                                                                                                        |                                                               |  |
+| <b>Other PICS</b>        |                                                                                                                                                                     |                                                               |  |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                    |                                                               |  |
+| <b>Test procedure</b>    | <p>1. The simulated PHG sends an Association Response.</p> <p>2. The PHD responds with an Abort message abrt(Abort-reason undefined).</p>                           |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                             |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The PHD transmits correctly the Abort message (abrt) with reason undefined and changes to the Unassociated state.</li> <li>The simulated PHG must not receive any message other than an Association Request after step 2.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                             |
+
+|                           |                                                                                                                                                                                                                                                                                         |                                                               |  |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-011                                                                                                                                                                                                                                                               |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Leaving the Operating State 3                                                                                                                                                                                                                                      |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                   | AgentStateMach 61; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br><br>If rlrq is received while in the Operating state, then the PHD transmits an rlre (normal) and moves to the Unassociated state                                                                                                                                        |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                        |                                                               |  |
+| <b>Test procedure</b>     | 1. The simulated PHG sends an Association Release Request (Rlrq) message to the PHD under test, with reason =0 (normal).<br><br>2. The PHD under test shall respond with an Association Release Response (Rlre) message with reason =0 (normal) and shall go to the Unassociated state. |                                                               |  |
+| <b>Pass/Fail criteria</b> | The PHD under test transmits correctly the Rlre message.                                                                                                                                                                                                                                |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                         |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                        |                                                               |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-012                                                                                                                                                                                                                                                              |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Leaving the Operating State 4                                                                                                                                                                                                                                     |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                  | AgentStateMach 62; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br><br>If rlre is received while in the Operating state, then the PHD transmits an abrt(Abort-reason undefined) and moves to the Unassociated state.                                                                                                                       |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                       |                                                               |  |
+| <b>Test procedure</b>     | 1. The simulated PHG sends an Association Release Response to the PHD under test, with reason =0 (normal)<br><br>2. The PHD under test responds with an Abort message abrt(Abort-reason undefined).                                                                                    |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The PHD under test transmits correctly the Abort message abrt(Abort-reason undefined) and changes to the Unassociated state.</li> <li>The simulated PHG must not receive any message other than an Association Request after step 2.</li> </ul> |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                        |                                                               |  |
+
+|                 |                                          |                                                               |  |
+|-----------------|------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>    | TP/PLT/PHD/OXP/COM/BV-013                |                                                               |  |
+| <b>TP label</b> | Agent State machine. Association timeout |                                                               |  |
+| <b>Coverage</b> | <b>Spec</b>                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                     |                      |                      |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------|----------------------|
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | AgentStateMach 2; M | AgentStateMach 16; M | AgentStateMach 17; M |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | AssocErrorCond 1; M | AssocErrorCond 2; M  | AssocErrorCond 3; M  |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>If timeout and maximum retry limit are not reached while in the Associating state, then the PHD continues transmitting aarq</p> <p>[AND]</p> <p>In the case of timeout, the PHD attempts to associate up to the maximum retry count is reached or association is successful.</p> <p>[AND]</p> <p>If timeout and maximum retry limit are reached when sending aarq, then the PHD transmits an abort message abrt(Abort-reason response-timeout) and moves to the Unassociated state.</p> <p>[AND]</p> <p>If the TOassoc period expires, the PHD shall re-transmit the Association Request message with a new TOassoc period. This process shall be repeated until an Association Response is received or RCassoc (retry count: association procedure) attempts have been made after the first timeout, whichever comes first. This results in a maximum of RCassoc + 1 Association Requests</p> |                     |                      |                      |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                     |                      |                      |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                     |                      |                      |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                     |                      |                      |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated PHG receives an association request from the PHD under test (and PHD under test passes to the Associating state).</li> <li>The simulated PHG does NOT respond with any message.</li> <li>The PHD under test shall wait for the TOassoc timer to expire (10 seconds) and retransmit a new association request.</li> <li>Steps 2-3 shall be repeated until the Retry Count has reached (=3).</li> <li>As the PHG has not answered to any of the 4 messages, the PHD under test shall send an abort message abrt(Abort-reason response-timeout) to the PHG and shall pass to the Unassociated state.</li> </ol>                                                                                                                                                                                                                                                    |                     |                      |                      |
+| <b>Pass/Fail criteria</b> | The TOassoc timer and the RC values are properly implemented and in the last step the PHD under test shall transmit an Abort message (abrt) with reason response-timeout.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                     |                      |                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                     |                      |                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                             |                                                               |  |  |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|--|
+| <b>TP Id</b>             |                                                                                                                                                                                                                                                                                                                                             | TP/PLT/PHD/OXP/COM/BV-020                                     |  |  |
+| <b>TP label</b>          |                                                                                                                                                                                                                                                                                                                                             | Agent State machine. Connected Associating 1                  |  |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                       | AgentStateMach 20; M                                          |  |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If aarq is received while in Associating state, then the PHD transmits an aare(rejected permanent) and moves to the Unassociated state</p>                                                                                                                                                                            |                                                               |  |  |
+| <b>Applicability</b>     |                                                                                                                                                                                                                                                                                                                                             | C_AG_OXP_000                                                  |  |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                             |                                                               |  |  |
+| <b>Initial condition</b> |                                                                                                                                                                                                                                                                                                                                             | The PHD under test is in the connected Associating state.     |  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHG issues an Association Request</li> <li>The PHD under test sends an Association Response message to the PHG: <ul style="list-style-type: none"> <li>reason = rejected-permanent(1),</li> <li>data-proto-id=data-proto-id-empty</li> <li>data-proto-info=omit</li> </ul> </li> </ol> |                                                               |  |  |
+
+|                           |                                                                                                                                                                                                                                        |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The PHD sends the detailed AARE message and changes to the Unassociated state</li> <li>The simulated PHG must not receive any message other than an Association Request after step 2</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                        |
+
+|                           |                                                                                                                                                                                                                                                                        |                                                               |  |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-021                                                                                                                                                                                                                                              |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Connected Associating 2                                                                                                                                                                                                                           |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                  | AgentStateMach 24; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br><br>If rlrq is received during Associating state, then the PHD transmits an abort message abrt(Abort-reason undefined) and moves to the Unassociated state.                                                                                             |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Initial condition</b>  | The PHD under test is in the connected Associating state.                                                                                                                                                                                                              |                                                               |  |
+| <b>Test procedure</b>     | 1. The simulated PHG issues a Release Request.<br><br>2. The PHD under test sends an abort message abrt(Abort-reason undefined) to the PHG and shall pass to the Unassociated state.                                                                                   |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The PHD under test sends the Abort message (abrt) with reason undefined and changes to the Unassociated state</li> <li>The simulated PHG must not receive any message other than an Association Request after step 2</li> </ul> |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                        |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                         |                                                               |  |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-022                                                                                                                                                                                                                               |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Connected Associating 2                                                                                                                                                                                                            |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                             | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                   | AgentStateMach 25; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br><br>If rlre is received during association state, then the PHD transmits an an abrt(Abort-reason undefined) and moves to the Unassociated state.                                                                                         |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                            |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Initial condition</b>  | The PHD under test is in the connected Associating state.                                                                                                                                                                                               |                                                               |  |
+| <b>Test procedure</b>     | 1. The simulated PHG issues a Release Response with reason = normal(0).<br><br>2. The PHD under test sends an abort message (Abort-reason undefined) to the PHG and shall pass to the Unassociated state.                                               |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The PHD sends the Abort message (Abort-reason undefined) and changes to the Unassociated state</li> <li>The simulated PHG must not receive any message other than an Association Request after step 2</li> </ul> |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                         |                                                               |  |
+
+|                 |                                              |  |  |
+|-----------------|----------------------------------------------|--|--|
+| <b>TP Id</b>    | TP/PLT/PHD/OXP/COM/BV-023                    |  |  |
+| <b>TP label</b> | Agent State machine. Connected Associating 4 |  |  |
+
+|                           |                                                                                                                                                                                                                                                                                                    |                                                               |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                              | AgentStateMach 27; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br><br>If prst (any APDU not covered in 3.* (corrupt, unknown, unexpected, etc.) is received during Associating state, then the PHD transmits an abort message abrt (Abort-reason undefined) and moves to the Unassociated state                                                       |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                                                       |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Initial condition</b>  | The PHD under test is in the connected Associating state.                                                                                                                                                                                                                                          |                                                               |  |
+| <b>Test procedure</b>     | 1. The simulated PHG issues a "roiv-cmip-get" command with the handle set to 0 (to request the MDS object) and the attribute-idlist set to "all-attributes".<br><br>2. The PHD under test sends an abort message abrt(Abort-reason undefined) to the PHG and shall pass to the Unassociated state. |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The PHD sends the Abort message (abrt) with reason undefined and changes to the Unassociated state</li> <li>The simulated PHG must not receive any message other than an Association Request after step 2</li> </ul>                                        |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                    |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                             |                                                               |  |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              |                                                                                                                                                                                                                                                             | TP/PLT/PHD/OXP/COM/BV-023_A                                   |  |
+| <b>TP label</b>           |                                                                                                                                                                                                                                                             | Agent State machine. Connected Associating 5                  |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                       | AgentStateMach 27; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br><br>If prst (any APDU not covered in 3.* (corrupt, unknown, unexpected, etc.) is received during Associating state, then the PHD transmits an abort message abrt (Abort-reason undefined) and moves to the Unassociated state                |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>Initial condition</b>  | The PHD under test is in the connected Associating state.                                                                                                                                                                                                   |                                                               |  |
+| <b>Test procedure</b>     | 1. The simulated PHG sends a badly formatted message.<br><br>2. The PHD under test sends an abort message abrt(Abort-reason undefined) to the PHG and shall pass to the Unassociated state.                                                                 |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The PHD sends the Abort message (abrt) with reason undefined and changes to the Unassociated state</li> <li>The simulated PHG must not receive any message other than an Association Request after step 2</li> </ul> |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                             |                                                               |  |
+
+|                     |                                                                                                                                                               |                                                                          |  |
+|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|--|
+| <b>TP Id</b>        |                                                                                                                                                               | TP/PLT/PHD/OXP/COM/BV-030                                                |  |
+| <b>TP label</b>     |                                                                                                                                                               | Agent State machine. Connected Associated Configuring Waiting Approval 1 |  |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C]            |  |
+|                     | <b>Testable items</b>                                                                                                                                         | AgentStateMach 45; M                                                     |  |
+| <b>Test purpose</b> | Check that:<br><br>If aarq is received while in the Waiting Approval state, then the PHD transmits an abrt (reason undefined) and moves to Unassociated state |                                                                          |  |
+
+|                           |                                                                                                                                                                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                    |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                 |
+| <b>Initial condition</b>  | The PHD under test is in the Waiting Approval state.                                                                                                                                                                                                            |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG issues an Association Request.</li> <li>2. The PHD under test sends an abort message abrt(Abort-reason undefined) to the PHG and shall pass to the Unassociated state.</li> </ol>                   |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHD sends the Abort message (abrt) with reason undefined and changes to the Unassociated state</li> <li>• The simulated PHG must not receive any message other than an Association Request after step 2</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                 |
+
+|                           |                                                                                                                                                                                                                                                                          |                                                               |  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-031                                                                                                                                                                                                                                                |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Connected Associated Configuring Waiting Approval 2                                                                                                                                                                                                 |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                    | AgentStateMach 46; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br>If aare is received while in Waiting Approval state, then the PHD transmits an abrt (reason undefined) and moves to the Unassociated state.                                                                                                               |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                          |                                                               |  |
+| <b>Initial condition</b>  | The PHD under test is in the Waiting Approval state.                                                                                                                                                                                                                     |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG issues an Association Response with reason = accepted(0).</li> <li>2. The PHD under test sends an abort message abrt(Abort-reason undefined) to the PHG and shall pass to the Unassociated state.</li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHD sends the Abort message (abrt) with reason undefined and changes to the Unassociated state</li> <li>• The simulated PHG must not receive any message other than an Association Request after step 2</li> </ul>          |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                          |                                                               |  |
+
+|                           |                                                                                                                                                                                                               |                                                               |  |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-032                                                                                                                                                                                     |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Connected Associated Configuring Waiting Approval 3                                                                                                                                      |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                         | AgentStateMach 47; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br>If rlrq is received while in Waiting Approval state, then the PHD transmits a rlre and moves to the Unassociated state.                                                                        |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                  |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                               |                                                               |  |
+| <b>Initial condition</b>  | The PHD under test is in the Waiting Approval state.                                                                                                                                                          |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG issues a Release Request.</li> <li>2. The PHD under test sends a Release Response to the PHG and shall pass to the Unassociated state.</li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHD under test sends the Release Response message and changes to the</li> </ul>                                                                                  |                                                               |  |
+
+|              |                                                                                                                                                                           |
+|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|              | <p>Unassociated state</p> <ul style="list-style-type: none"> <li>The simulated PHG must not receive any message other than an Association Request after step 2</li> </ul> |
+| <b>Notes</b> |                                                                                                                                                                           |
+
+|                           |                                                                                                                                                                                                                                                                    |                                                               |  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-033                                                                                                                                                                                                                                          |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Connected Associated Configuring Waiting Approval 4                                                                                                                                                                                           |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                              | AgentStateMach 48; M                                          |  |
+| <b>Test purpose</b>       | If rlre is received while in Waiting Config state, then the PHD transmits an abrt (reason undefined) and moves to the Unassociated state.                                                                                                                          |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                       |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Initial condition</b>  | The PHD under test is in the Waiting Approval state.                                                                                                                                                                                                               |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated PHG issues a Release Response with reason = normal(0).</li> <li>The PHD under test sends an abort message abrt(Abort-reason undefined) to the PHG and shall pass to the Unassociated state.</li> </ol>        |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The PHD under test sends the Abort message (abrt) with reason undefined and changes to the Unassociated state</li> <li>Simulated PHG must not receive any message other than an Association Request after step 2</li> </ul> |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                    |                                                               |  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |                   |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/COM/BV-034                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                   |
+| <b>TP label</b>          | Agent State machine. Connected Associated Configuring Waiting Approval 5                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                   |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | AgentStateMach 50; M                                          | OperNormProc 5; R |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If roiv-cmip-get, handle=0 is received while in Waiting Approval state, then the PHD transmits an rors-cmip-get with the MDS attributes or roer not-allowed-by-object if request is not for all attributes and PHD does not support the request and PHD remains in Waiting Approval state.</p> <p>[AND]</p> <p>If the PHG requests specific MDS object attributes, as indicated by the elements in attribute-id-list, and if this capability is not implemented, then the PHD shall respond with an error (roer) message with an error-value of not-allowed-by-object,</p>                                                                       |                                                               |                   |
+| <b>Applicability</b>     | C_AG_OXP_000 AND (C_AG_OXP_291 OR C_AG_OXP_292)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |                   |
+| <b>Other PICS</b>        | C_AG_OXP_100                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                   |
+| <b>Initial condition</b> | The PHD under test is in the connected associated configuring Waiting Approval state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                   |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHG issues a "roiv-cmip-get" command with the handle set to 0 (to request the MDS object) and the attribute-id list set to MDC_ATTR_SYS_ID.</li> <li>The PHD under test responds with a "rors-cmip-get" message or a roer message (not-allowed-by-object).</li> <li>The PHD under test remains in Waiting Approval state.</li> <li>The simulated PHG responds with a rors-cmip-confirmed-event-report with result "unsupported-config".</li> <li>The PHD responds with a roiv-cmip-confirmed-event report message with an MDC_NOTI_CONFIG event to send its configuration to the PHG or Rlrq (no-more-</li> </ol> |                                                               |                   |
+
+|                           |                                                            |
+|---------------------------|------------------------------------------------------------|
+|                           | configurations).                                           |
+| <b>Pass/Fail criteria</b> | The process detailed above must be successfully completed. |
+| <b>Notes</b>              |                                                            |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-034_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Get Request Sending Configuring                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | AgentStateMach 37; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br>If roiv-cmip-get, handle=0 is received while in Sending Config state, then the PHD transmits an rors-cmip-get with the MDS attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000 AND (C_AG_OXP_291 OR C_AG_OXP_292)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The PHD under test sends an Association Request to the simulated PHG.</li> <li>2. The simulated PHG responses with an accepted-unknown-config.</li> <li>3. The simulated PHG issues "roiv-cmip-get" command with the handle set to 0 (to request the MDS object) and the attribute-idlist set to "all-attributes".</li> <li>4. The PHD under test responds with a "rors-cmip-get" message in which the attribute=list contains a list of all implemented attributes of the MDS object.</li> <li>5. The PHD under test must send its configuration.</li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | The process detailed above must be completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-035                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Connected Associated Configuring Waiting Approval 6                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | AgentStateMach 51; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br>If roiv-* but not (roiv-cmip-get, handle=0) is received while in Waiting Approval state, then the PHD transmits a roer (no-such-object-instance) and remains in Waiting Approval state.                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>Initial condition</b>  | The PHD under test is in the connected associated configuring Waiting Approval state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG issues a GET with handle = 1.</li> <li>2. The PHD under test must send a "roer" with reason = no-such-object-instance(1).</li> <li>3. The PHD under test remains in the Waiting Approval state.</li> <li>4. The simulated PHG responds with a rors-cmip-confirmed-event-report with result "unsupported-config".</li> <li>5. The PHD responds with a roiv-cmip-confirmed-event report message with an MDC_NOTI_CONFIG event to send its configuration to the PHG or Rlrq (no-more-configurations).</li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | The process detailed above must be successfully completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                        |                                                               |  |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/EXP/COM/BV-036_A                                                                                                                                                                                                                                            |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Connected Associated Configuring Waiting Approval 7                                                                                                                                                                                               |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                  | AgentStateMach 54; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br><br>If rors-*, roer-*, or roj-*, but not rors-cmip-confirmed-event-report is received while PHD is in "Waiting Approval" state, an PHD shall transmit an abrt(reason undefined) and move to the Unassociated state.                                     |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Initial condition</b>  | The PHD under test is in the connected associated configuring Waiting Approval state.                                                                                                                                                                                  |                                                               |  |
+| <b>Test procedure</b>     | 1. The simulated PHG issues a Prst message, rors-cmip- get.<br><br>2. The PHD under test sends an abort message abrt(Abort-reason undefined) to the PHG and shall pass to the Unassociated state.                                                                      |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The PHD under test sends the Abort message (abrt) with reason undefined and changes to the Unassociated state</li> <li>The simulated PHG must not receive any message other than an Association Request after step 2</li> </ul> |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                        |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                        |                                                               |  |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/EXP/COM/BV-036_B                                                                                                                                                                                                                                            |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Connected Associated Configuring Waiting Approval 8                                                                                                                                                                                               |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                  | AgentStateMach 54; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br><br>If rors-*, roer-*, or roj-*, but not rors-cmip-confirmed-event-report is received while PHD is in "Waiting Approval" state, an PHD shall transmit an abrt(reason undefined) and move to the Unassociated state.                                     |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Initial condition</b>  | The PHD under test is in the connected associated configuring Waiting Approval state.                                                                                                                                                                                  |                                                               |  |
+| <b>Test procedure</b>     | 1. The simulated PHG issues a roer message.<br><br>2. The PHD under test sends an abort message abrt(Abort-reason undefined) to the PHG and shall pass to the Unassociated state.                                                                                      |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The PHD under test sends the abort message (abrt) with reason undefined and changes to the Unassociated state</li> <li>The simulated PHG must not receive any message other than an Association Request after step 2</li> </ul> |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                        |                                                               |  |
+
+|                     |                                                                          |                                                               |  |
+|---------------------|--------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>        | TP/PLT/PHD/EXP/COM/BV-036_C                                              |                                                               |  |
+| <b>TP label</b>     | Agent State machine. Connected Associated Configuring Waiting Approval 9 |                                                               |  |
+| <b>Coverage</b>     | <b>Spec</b>                                                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                     | <b>Testable items</b>                                                    | AgentStateMach 54; M                                          |  |
+| <b>Test purpose</b> | Check that:                                                              |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                    |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | If rors-*, roer-*, or rorj-*, but not rors-cmip-confirmed-event-report is received while the PHD is in "Waiting Approval" state, a PHD shall transmit an abrt(reason undefined) and move to the Unassociated state.                                                |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                       |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                    |
+| <b>Initial condition</b>  | The PHD under test is in the connected associated configuring Waiting Approval state.                                                                                                                                                                              |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated PHG issues a rorj message.</li> <li>The PHD under test sends an abort message abrt(Abort-reason undefined) to the PHG and shall pass to the Unassociated state.</li> </ol>                                    |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The PHD under test sends the Abort message (abrt) with reason undefined and changes to Unassociated state</li> <li>The simulated PHG must not receive any message other than an Association Request after step 2</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-037                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Connected Disassociation 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | AgentStateMach 70; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br><br>If aarq is received while in the Disassociating state, then the PHD transmits an abrt (Abort-reason undefined) and moves to Unassociated state                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+| <b>Initial condition</b>  | The PHD is in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The PHD under test sends an Association Request to the simulated PHG.</li> <li>The simulated PHG responds with an accepted-unknown-config.</li> <li>The PHD sends a configuration event report.</li> <li>The simulated PHG responds with an unsupported-configuration.</li> <li>The PHD sends a new configuration event report with a new configuration (if it has more).</li> <li>Repeat the last two steps recording all the ConfigId-values until the PHD sends a ReleaseRequest with reason "no-more-configurations". The PHD moves to the Disassociating state.</li> <li>The simulated PHG sends an AARQ message.</li> <li>The PHD responds with an Abort message (abrt) with reason undefined.</li> <li>The PHD and the PHG move to the Unassociated state.</li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The PHD sends the Abort message (abrt) with reason undefined and changes to the Unassociated state</li> <li>The simulated PHG must not receive any message other than an Association Request after step 9</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |  |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-038                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Connected Disassociation 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | AgentStateMach 71; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br><br>If aare is received while in Disassociating state, the PHD shall transmit an abrt (reason undefined) and move to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |  |
+| <b>Initial condition</b>  | The PHD is in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The PHD under test sends an Association Request to the simulated PHG.</li> <li>2. The simulated PHG responds with an accepted-unknown-config.</li> <li>3. The PHD sends a configuration event report.</li> <li>4. The simulated PHG responds with an unsupported-configuration.</li> <li>5. The PHD sends a new configuration event report with a new configuration (if it has more).</li> <li>6. Repeat the last two steps recording all the ConfigId-values until the PHD sends a ReleaseRequest with reason "no-more-configurations". The PHD moves to the Disassociating state.</li> <li>7. The simulated PHG sends an AARE message.</li> <li>8. The PHD responses with an Abort message (abrt) with reason undefined.</li> <li>9. The PHD and the PHG move to the Unassociated state.</li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHD sends the Abort message (abrt) with reason undefined and changes to Unassociated state</li> <li>• The simulated PHG must not receive any message other than an Association Request after step 9</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/COM/BV-039                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>TP label</b>          | Agent State machine. Connected Disassociation 3                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | AgentStateMach 72; M                                          |  |
+| <b>Test purpose</b>      | Check that:<br><br>If rlrq is received while in Disassociating state, the PHD shall transmit a rlre (normal) and remain in the same state                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>Applicability</b>     | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+| <b>Initial condition</b> | The PHD is in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The PHD under test sends an Association Request to the simulated PHG.</li> <li>2. The simulated PHG responds with an accepted-unknown-config.</li> <li>3. The PHD sends a configuration event report.</li> <li>4. The simulated PHG responds with an unsupported-configuration.</li> <li>5. The PHD sends a new configuration event report with a new configuration (if it has more).</li> <li>6. Repeat the last two steps recording all the ConfigId-values until the PHD sends a</li> </ol> |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                            |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | ReleaseRequest with reason "no-more-configurations". The PHD moves to the Disassociating state.<br>7. The simulated PHG sends a Rlrq message (reason=normal).<br>8. The PHD responses with a Rlre message.<br>9. The PHD and PHG remain in the same state. |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHD sends the Rlre message and remain in the same state</li> <li>• The simulated PHG must not receive any message other than an Association Request after step 9</li> </ul>                                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                            |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-040_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Connected Disassociation 4                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | AgentStateMach 76; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br>If roer is received while in the Disassociating state, then the PHD transmits an abrt (Abort-reason undefined) and moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |
+| <b>Initial condition</b>  | The PHD is in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The PHD under test sends an Association Request to the simulated PHG.</li> <li>2. The simulated PHG responses with an accepted-unknown-config.</li> <li>3. The PHD sends a configuration event report.</li> <li>4. The simulated PHG responds with an unsupported-configuration.</li> <li>5. The PHD sends a new configuration event report with a new configuration (if it has more).</li> <li>6. Repeat the last two steps recording all the ConfigId-values until the PHD sends a ReleaseRequest with reason "no-more-configurations". The PHD moves to the Disassociating state.</li> <li>7. The simulated PHG sends a Roer message.</li> <li>8. The PHD responds with an Abort message (reason undefined).</li> <li>9. The PHD and the PHG move to the Unassociated state.</li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHD sends the Abort (reason undefined) message and changes to the Unassociated state</li> <li>• The simulated PHG must not receive any message other than an Association Request after step 9</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |
+
+|                      |                                                                                                                                                              |                                                               |  |
+|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>         | TP/PLT/PHD/OXP/COM/BV-040_B                                                                                                                                  |                                                               |  |
+| <b>TP label</b>      | Agent State machine. Connected Disassociation 5                                                                                                              |                                                               |  |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                  | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                      | <b>Testable items</b>                                                                                                                                        | AgentStateMach 76; M                                          |  |
+| <b>Test purpose</b>  | Check that:<br>If rorj is received while in the Disassociating state, then the PHD transmits an abrt (reason undefined).and moves to the Unassociated state. |                                                               |  |
+| <b>Applicability</b> | C_AG_OXP_000                                                                                                                                                 |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                       |
+| <b>Initial condition</b>  | The PHD is in the Disassociating state.                                                                                                                                                                                                               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG sends an Rorj message.</li> <li>2. The PHD responds with an Abort message (reason undefined).</li> <li>3. The PHD and the PHG move to the Unassociated state.</li> </ol>                  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHD sends the Abort message (reason undefined) and changes to the Unassociated state</li> <li>• The simulated PHG must not receive any message other than an Association Request after step 9</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                       |
+
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                      |
+|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|----------------------|
+| <b>TP Id</b>         | TP/PLT/PHD/OXP/COM/BV-042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                      |
+| <b>TP label</b>      | Association request format                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                      |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                      |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | AssocRequest 3; C                                             | AssocRequest 4; C    |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | AssocRequest 6; M                                             |                      |
+|                      | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [b-ITU-T H.810 (2015)]                                        |                      |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | General 3; M                                                  | Dev.Information 9; M |
+| <b>Test purpose</b>  | <p>Check that:</p> <p>If a PHD sets the data-proto-id to data-proto-id-20601, then it adheres to the abstract syntax definitions specified for data types and message exchange.</p> <p>[AND]</p> <p>The data-proto-info field is filled in with a PhdAssociationInformation structure which defines the following information:</p> <ul style="list-style-type: none"> <li>- The version of the data exchange protocol.</li> <li>- The specific DataApdu encoding rule(s) supported by the PHD. The PHD sets one or more of the encoding-rules bits.</li> <li>- The PHD always supports MDER. That is, the mder bit of encoding-rules is set by the PHD.</li> <li>- The PHD may offer other encoding rules, besides MDER, to the PHG by setting other bits in the encoding-rules.</li> <li>- The version of the nomenclature used a field indicating all functional units and optional features supported by the PHD.</li> <li>- The system type (PHD in this case).</li> <li>- A unique System-Id of the PHD. The PHD uses EUI-64 to identify itself.</li> <li>- A dev-config-id, which identifies the current configuration of the PHD.</li> <li>- A data-req-mode-capab, which defines the data request modes supported by the PHD.</li> <li>- An option-list that contains a list of additional attributes the PHD wishes to communicate.</li> </ul> <p>[AND]</p> <p>The PHD shall place at most one data-proto element containing the field data-proto-id set to data-proto-id-20601 in the data-proto-list.</p> <p>[AND]</p> <p>Continua service components supporting a device specialization other than the basic electrocardiograph (ECG) shall set only the version 1 bit in the protocol version field of the PHDAssociationInformation structure in the AARQ.</p> |                                                               |                      |
+| <b>Applicability</b> | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICS</b>        | C_AG_OXP_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The PHD under test sends an AARQ message to the simulated PHG. The expected fields sent by the PHD are: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length =2 bytes</li> <li><input type="checkbox"/> field-value =0xE2 0x00 (AareApdu)</li> </ol> </li> <li>b. The following two bytes indicate the length of the message.</li> <li>c. assoc-version <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = AssociationVersion</li> <li><input type="checkbox"/> field-length =BITS-32</li> <li><input type="checkbox"/> field-value = <ol style="list-style-type: none"> <li>▪ Only one bit can be set</li> </ol> </li> </ol> </li> <li>d. The following four bytes indicate: <ol style="list-style-type: none"> <li><input type="checkbox"/> data-proto-list.count ( two bytes) = At most there is a data-proto-id set to data-proto-id-20601</li> <li><input type="checkbox"/> Length of the message (two bytes)</li> </ol> </li> <li>e. data-proto-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = DataProtoId</li> <li><input type="checkbox"/> field-length =INT-U16</li> <li><input type="checkbox"/> field-value = 0x50 0x79 (20601)</li> <li><input type="checkbox"/> data-proto-id=20601 indicates exchange protocol follows this standard, and data-proto-info shall contain PhdAssociationInformation.</li> </ol> </li> <li>f. The DataProto.Info field must contain two bytes and indicates the data-proto-info.length</li> <li>g. protocol-version <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = Protocol Version</li> <li><input type="checkbox"/> field-length =BITS-32</li> <li><input type="checkbox"/> IF the PHD supports insulin pump (IP) (C_AG_OXP_158 = TRUE) THEN <ol style="list-style-type: none"> <li>▪ field-value = At least bit protocol-version3(2) is set to 1 (0x20 0x00 0x00 0x00 OR 0xA0 0x00 0x00 0x00 OR 0x60 0x00 0x00 0x00 OR 0xE0 0x00 0x00 0x00)</li> <li>▪ This value shows that version 3 of the data exchange protocol is supported (protocol-version3(2)=1).</li> </ol> </li> <li><input type="checkbox"/> IF the PHD supports power status monitor (PSM) with Simple PSM or Advanced PSM profile (C_AG_OXP_270 = TRUE OR C_AG_OXP_271 = TRUE) THEN <ol style="list-style-type: none"> <li>▪ field-value = At least bit protocol-version3(2) and bit protocol-version2(1) are set to 1 (0x60 0x00 0x00 0x00 OR 0xE0 0x00 0x00 0x00)</li> <li>▪ This value shows that version 2 and 3 of the data exchange protocol are supported (protocol-version3(2)=1 protocol-version2(1)=1).</li> </ol> </li> <li><input type="checkbox"/> IF PHD supports basic electrocardiograph (ECG) or international normalized ratio (INR) or continuous glucose monitor (CGM) device specialization (C_AG_OXP_165 = TRUE OR C_AG_OXP_164 = TRUE OR C_AG_OXP_163 = TRUE OR C_AG_OXP_157 = TRUE) THEN <ol style="list-style-type: none"> <li>▪ field-value = At least bit protocol-version2(1) is set to 1 (0x40 0x00 0x00 0x00 OR 0xC0 0x00 0x00 0x00)</li> <li>▪ This value shows that version 2 of the data exchange protocol is supported (protocol-version2(1)=1).</li> </ol> </li> </ol> </li> </ol> </li> </ol> <p>ELSE</p> |
+
+▪ field-value = 0x80 0x00 0x00 0x00
+
+▪ This value shows that version 1 of the data exchange protocol is supported (protocol-version1(0)=1).
+
+#### h. encoding rules
+
+field-type = EncodingRules
+
+field-length = BITS-16
+
+field-value= depends on the encoding rules supported/selected.
+
+▪ Bit 0 (mder) must always be set
+
+▪ and xer(1) or/and per(2) may be set (optional).
+
+#### i. 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).
+
+#### j. functional-units
+
+field-type = FunctionalUnits
+
+field-length = 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
+
+#### k. system type
+
+field-type = SystemType
+
+field-length = BITS-32
+
+field-value = 0x00 0x80 0x00 0x00 (sys-type-agent)
+
+#### l. system-id
+
+field-type = OCTET STRING
+
+field-length = 0x00 0x0A
+
+field-value = 0x00 0x0X 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.
+
+#### m. dev-config-id
+
+field-type = ConfigId
+
+field-length = INT-U16
+
+field-value = <Not relevant for this Test>
+
+#### n. Data-Req-Mode-Capab:
+
+field-type = DataReqModeCapab
+
+field-length = INT-U16
+
+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
+
+#### o. option-list:
+
+|                           |                                                                         |
+|---------------------------|-------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> field-type: AttributeList                      |
+| <b>Pass/Fail criteria</b> | The structure and values of the association request message is correct. |
+| <b>Notes</b>              |                                                                         |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHD/EXP/COM/BV-049                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |
+| <b>TP label</b>           | Configuring Procedure 4                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                           | ConfErrorCond 1; M      ConfErrorCond 2; M                    |
+| <b>Test purpose</b>       | Check that:<br><br>In the Configuring state, the PHD waits for the "Remote Operation Response   Confirmed Event Report   MDC_NOTI_CONFIG" message for an TO <sub>config</sub> period.<br>[AND]<br>If the TO <sub>config</sub> period expires, then the PHD sends an Association Abort message to the PHG and transition back to the Unassociated state                                                          |                                                               |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                             |                                                               |
+| <b>Test procedure</b>     | 1. The simulated PHG receives an association request from the PHD under test (the PHD passes to the Associating state).<br>2. The simulated PHG responds with an Association Response with result = "accepted-unknown-config".<br>3. The PHD under test sends a configuration event report.<br>4. The simulated PHG does not respond to the configuration event report for more than TO <sub>config</sub> time. |                                                               |
+| <b>Pass/Fail criteria</b> | The PHD must wait for a TO <sub>config</sub> . If the time expires, the PHD must send an abort to the PHG.                                                                                                                                                                                                                                                                                                      |                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/EXP/COM/BV-051                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+| <b>TP label</b>          | Non-standard configuration, Dev-config-id                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ConfNormalProc 20; C      ConfEventRep 21; M                  |
+| <b>Test purpose</b>      | Check that:<br><br>A PHD that has a non-standard configuration assigns a unique identifier to its configuration by generating a value for dev-config-id in the range between extended-config-start and extended-config-end, inclusive.                                                                                                                                                                                                                                                                                    |                                                               |
+| <b>Applicability</b>     | C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |
+| <b>Test procedure</b>    | 1. The simulated PHG receives an association request from the PHD under test with a dev-config-id and a system-id.<br>2. The simulated PHG responds with a result = accepted-unknown-config.<br>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.<br>4. The simulated PHG responds with a rors-cmip-confirmed-event-report with result "accepted" if the Config-Id received in step 3 is the configuration that is being tested, in |                                                               |
+
+|                           |                                                                                                                                                                  |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | this case ConfigReport is recorded. Otherwise, the PHG responds with a rors-cmip-confirmed-event-report with result "unsupported-config" and step 3 is repeated. |
+|                           | 5. Check the config-report-id in the ConfigReport recorded in step 4.                                                                                            |
+| <b>Pass/Fail criteria</b> | The config-report-id value checked in step 5 is in the range between the extended-config-start (16384) and the extended-config-end (32767), inclusive.           |
+| <b>Notes</b>              |                                                                                                                                                                  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                   |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/ OXP/COM/BV-052_B                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                   |
+| <b>TP label</b>          | Operating procedures. Specific Attributes request                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                   |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [b-ITU-T H.810 (2015)] |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | OperNormProc 4; O      | OperNormProc 5; R |
+| <b>Test purpose</b>      | <p>Check that</p> <p>The PHD under test supports retrieval of a specific list of attributes</p> <p>[AND]</p> <p>If the PHG requests specific MDS object attributes, indicated by the elements in attribute-id-list, and the PHD supports this capability, then the PHD shall respond with a rors-cmip-get message in which the attribute-list contains a list of the requested attributes of the MDS object that are implemented. It is not required for an PHD to support this capability. If this capability is not implemented then the PHD shall respond with an error (roer) message with an error-value of not-allowed-by-object,</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |                   |
+| <b>Applicability</b>     | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                   |
+| <b>Other PICS</b>        | C_AG_OXP_100                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                   |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                   |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG issues a "Remote Operation Invoke   Get" command with: <ol style="list-style-type: none"> <li>a. Obj-handle set to 0 (to request an MDS object)</li> <li>b. attribute-id-list.count=1 and a single AVA_Type MDC_ATTR_DEV_CONFIG_ID (0X0A 0X44) to retrieve the mandatory "Dev-Configuration-Id" attribute</li> </ol> </li> <li>2. The PHD under test responds with: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_100 THEN: with a "rors-cmip-get" service message which contains the "Dev-Configuration-Id"</li> <li>• ELSE: with a "roer" service message with error-value set to not-allowed-by-object (24)</li> </ul> </li> <li>3. The simulated PHG issues a "Remote Operation Invoke   Get" command with: <ol style="list-style-type: none"> <li>a. Obj-handle set to 0 (to request an MDS object)</li> <li>b. attribute-id-list empty to request all the attributes of MDS</li> </ol> </li> <li>4. The PHD responds with a "rors-cmip-get" service message which contains all the supported attributes of the MDS.</li> <li>5. The simulated PHG issues a "Remote Operation Invoke   Get" command with <ol style="list-style-type: none"> <li>a. Obj-handle set to 0</li> <li>b. attribute-id-list set to an attribute NOT supported by the PHD</li> </ol> </li> <li>6. The PHD responds with a "rors-cmip-get" service message: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_100 THEN: attribute-list must be empty</li> <li>• ELSE: with a "roer" service message with error-value set to not-allowed-by-object (24)</li> </ul> </li> <li>7. The simulated PHG issues a "Remote Operation Invoke   Get" command with <ol style="list-style-type: none"> <li>a. Obj-handle set to 0</li> <li>b. attribute-id-list contains one supported attribute and one unsupported attribute</li> </ol> </li> <li>8. The PHD responds with a "rors-cmip-get" service message:</li> </ol> |                        |                   |
+
+|                           |                                                                                                                                                                                                                                                                                         |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• IF C_AG_OXP_100 THEN: attribute-list must contain the supported attribute</li> <li>• ELSE: with a "roer" service message with error-value set to not-allowed-by-object (24)</li> </ul>                                                         |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2 the PHD properly sends the requested attribute or the error (not-allowed-by-object )</li> <li>• In steps 6 and 8 the received attribute list must be empty if NOT C_AG_OXP_100 or the roer if the action is not supported</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                         |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                        |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/EXP/COM/BV-053                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                        |
+| <b>TP label</b>          | Operating procedures. Agent-initiated transmission 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |                        |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                        |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | MeasureDataTransf 4; C                                        | MeasureDataTransf 5; C |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The PHD indicates that support Agent-Initiated measurements via the DataReqModeCapab structure or the PHD has one or more instances of a Scanner object in the PHD's configuration</p> <p>[AND]</p> <p>The PHD uses the Event Report Service to send a spontaneous measurement to the PHG without being requested by the PHG first.</p> <p>[AND]</p> <p>The PHD uses for this purpose a DataApdu message in a "Remote Operation Invoke   Event Report" command and one of the MDC_NOTI_SCAN_REPORT_* event-types</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                        |
+| <b>Applicability</b>     | C_AG_OXP_000 AND (C_AG_OXP_182 OR C_AG_OXP_183 OR C_AG_OXP_184 OR C_AG_OXP_189)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                        |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                        |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the disconnected Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                        |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The PHD under test must send an Association Request to the simulated PHG which contains the DataReqModeFlags field (of the DataReqModeCapab attribute).</li> <li>2. Check the value of the bit 15 (data-req-supp-init-agent). Check that if the bit is not set, there is at least one Scanner object in the PHD under test.</li> <li>3. IF C_AG_OXP_293 THEN: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 THEN it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ol> </li> <li>4. Once the device is in the Operating state take a measurement and check that, if the bit was set, the PHD under test sends the measurement value to the simulated PHG without the PHG requesting it using a "Remote Operation Invoke   Confirmed Event Report" or a "Remote Operation Invoke   Event Report" message with one of the MDC_NOTI_SCAN_REPORT_* event-types. Record the scan-report-no for later comparison and check data-req-id.</li> </ol> |                                                               |                        |
+
+|                           |                                                                                                                                                                                                                                   |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | 5. Take another measurement, record the scan-report-no of the event and check data-req-id.                                                                                                                                        |
+| <b>Pass/Fail criteria</b> | The PHD is able to send agent-initiated measurement reports, uses a correct event-type for doing so and the scan-report-no of the second event has increased once unit Data-req-id is set to data-req-id-agent-initiated (61440). |
+| <b>Notes</b>              |                                                                                                                                                                                                                                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-053_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |  |
+| <b>TP label</b>           | Operating procedures. Invoke-id                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | AgentStateMach 50;M                                           |  |
+| <b>Test purpose</b>       | Check that:<br>In the remote operation invoke messages (roiv-*), invoke-id is an opaque handle that allows the sender of the message to identify the associated response message (if any). Since the handle is opaque the receiver can make no other assumptions about invoke-id.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG issues a "roiv-cmip-get" command with the handle set to 0, an empty attribute-id-list to indicate all attributes and invoke-id =20. Record the invoke-id of the message sent.</li> <li>2. The PHD responds with a "rors-cmip-get" service and the invoke id is 20.</li> <li>3. The simulated PHG issues a "roiv-cmip-get" command with the handle set to 0, an empty attribute-id-list to indicate all attributes and invoke-id =15. Record the invoke-id of the message sent.</li> <li>4. The PHD responds with a "rors-cmip-get" service and the invoke id is 15.</li> <li>5. The simulated PHG issues a "roiv-cmip-get" command with the handle set to 0, an empty attribute-id-list to indicate all attributes and invoke-id =30. Record the invoke-id of the message sent.</li> <li>6. The PHD responds with a "rors-cmip-get" service and the invoke id is 30.</li> <li>7. The simulated PHG issues a "roiv-cmip-get" command with the handle set to 0, an empty attribute-id-list to indicate all attributes and invoke-id =20. Record the invoke-id of the message sent.</li> <li>8. The PHD responds with a "rors-cmip-get" service and the invoke id is 20.</li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | In steps 2, 4, 6 and 8, the invoke-id has the correct value.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |
+
+|                      |                                                                                                                                                                                                                                                |                                                               |  |
+|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>         | TP/PLT/PHD/OXP/COM/BV-054                                                                                                                                                                                                                      |                                                               |  |
+| <b>TP label</b>      | Agent-initiated transmission.Scan-report-no                                                                                                                                                                                                    |                                                               |  |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                    | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                          | MeasureDataTransf 46; M                                       |  |
+| <b>Test purpose</b>  | Check that:<br>An agent-initiated transfer from the MDS or scanner objects, by way of contrast, establishes a flow that terminates only when the association is broken. Thus for the agent-initiated transfer, the scan-report-no starts at 0, |                                                               |  |
+| <b>Applicability</b> | C_AG_OXP_000 AND (C_AG_OXP_182 OR C_AG_OXP_183 OR C_AG_OXP_184 OR C_AG_OXP_189 OR C_AG_OXP_046 OR C_AG_OXP_047)                                                                                                                                |                                                               |  |
+| <b>Other PICS</b>    | C_AG_OXP_180                                                                                                                                                                                                                                   |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                      |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. If the PHD supports the scanner object, the simulated PHG sends a Set action to set the Operational-State of the scanner to 1 (enabled).</li> <li>2. Check that the first MDS-Event-Report, for the Metric object or Scanner object, scan-report-no starts at 0.</li> </ol> |
+| <b>Pass/Fail criteria</b> | In step 2, the scan-report-no shall be 0.                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                       |
+
+|                           |                                                                                                                                                                                        |                              |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-054_A                                                                                                                                                            |                              |  |
+| <b>TP label</b>           | Agent-initiated transmission. Separate scan-report-no                                                                                                                                  |                              |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                            | [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                  | MeasureDataTransf 52; M      |  |
+| <b>Test purpose</b>       | Check that:<br>There will be a separate scan-report-no for confirmed (data-req-id 0xF000) and unconfirmed (data-req-id 0xF001) scan event reports.                                     |                              |  |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_053 AND C_AG_OXP_293 AND NOT C_AG_OXP_268 AND NOT C_AG_OXP_269                                                                                               |                              |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                        |                              |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                   |                              |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. PHD sends some measurements using unconfirmed event reports</li> <li>2. PHD sends some measurements using confirmed event reports</li> </ol> |                              |  |
+| <b>Pass/Fail criteria</b> | In step 2, verify that scan-report-no sequences from unconfirmed and confirmed event reports are independent.                                                                          |                              |  |
+| <b>Notes</b>              |                                                                                                                                                                                        |                              |  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                                                    |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|----------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/COM/BV-056                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                                                    |
+| <b>TP label</b>          | Operating procedures. Agent-initiated transmission. Scanner objects                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                                                    |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                                                    |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MeasureDataTransf 9; M<br>ScanClassAttr 3; M                  | MeasureDataTransf 10; C<br>MeasureDataTransf 47; M |
+| <b>Test purpose</b>      | Check that:<br>Scanner objects begin with Operational-State disabled on PHD with bi-directional communication until the PHG enables it<br>[AND]<br>The data-req-id field in the Scan Report is set to data-req-id-agent-initiated.<br>[AND]<br>If the Scanner's Operational-State attribute is set to disabled halts transmission of Event Reports, then the scan-report-no will continue counting where it was halted before<br>[AND]<br>This attribute (Operational-State) indicates if the scanner is sending event reports or not. If the scanner is sending event reports, the attribute value shall be set to enabled; otherwise, it shall be set to disabled. |                                                               |                                                    |
+| <b>Applicability</b>     | (C_AG_OXP_046 OR C_AG_OXP_047) AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                                                    |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_180, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                                                    |
+| <b>Initial condition</b> | The simulated PHG is in the Waiting Config state and the PHD under test is in the Sending Config state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                                                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The PHD under test must send its configuration to the PHG. The scanner object must have the Operational-State set to 0.</li> <li>2. IF C_AG_OXP_293 THEN: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ol style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 THEN it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ol> </li> </ol> </li> <li>3. The simulated PHG sends a Set action to set the Operational-State of the scanner to 1 (enabled): <ol style="list-style-type: none"> <li>a. APDU <ol style="list-style-type: none"> <li><input type="checkbox"/> Type = Remote Operation Invoke   Confirmed Event Report</li> <li><input type="checkbox"/> roiv-cmip-confirmed-set</li> <li><input type="checkbox"/> attribute = OperationalState</li> <li><input type="checkbox"/> value = 1</li> </ol> </li> </ol> </li> <li>4. Several measurements are taken with the PHD under test. The Data-req-id field will be checked</li> <li>5. Once the PHD under test starts to transmit its data, the PHG sets the Operational-State to 0: <ol style="list-style-type: none"> <li>a. APDU <ol style="list-style-type: none"> <li><input type="checkbox"/> Type = Remote Operation Invoke   Confirmed set</li> <li><input type="checkbox"/> roiv-cmip-confirmed-set</li> <li><input type="checkbox"/> attribute = OperationalState</li> <li><input type="checkbox"/> value = 0</li> </ol> </li> </ol> </li> <li>6. The PHD must stop sending its data. Record the last scan-report-no.</li> <li>7. The simulated PHG resumes the PHD data transmission by setting the Operational-State back to 1: <ol style="list-style-type: none"> <li>a. APDU <ol style="list-style-type: none"> <li><input type="checkbox"/> Type = Remote Operation Invoke   Confirmed set</li> <li><input type="checkbox"/> roiv-cmip-confirmed-set</li> <li><input type="checkbox"/> attribute = OperationalState</li> <li><input type="checkbox"/> value = 1</li> </ol> </li> </ol> </li> <li>8. Several measurements are taken with the PHD under test. Check that the scan-report-no starts counting where it halted before (step 4).</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 4, the PHD has to start to transmit data and the data-req-id field is set to data-req-id-agent-initiated</li> <li>• In step 6, the PHD has to stop to transmit data</li> <li>• In step 8, the PHD has to start again to transmit data and scan-report-no has to start counting where it was halted in step 4</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                                                  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/COM/BV-072                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                                                  |
+| <b>TP label</b>          | Operating procedures. PM-Store                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |                                                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                                                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | PersStoreMtrDatTransf 3; M<br>PM-StoreMeth 27; O              | PersStoreMtrDatTransf 4; M<br>PM-StoreMeth 26; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The PHD supports a get-segment-info request to all segments and a particular segment</p> <p>[AND]</p> <p>The PHD may support a get-segment-info request for a time range selection criteria according to pmsc-abs-time-select in the PM-Store-Capab attribute</p> <p>[AND]</p> <p>The PHD shall support the all-segments choice in the SegmSelection action-info-args of the Get- Segment-Info method.</p> <p>[AND]</p> <p>The PHD may support the segm-id-list and/ or abs-time-range choice in the SegmSelection action-info-args of the Get-Segment-Info method. In this case the PHD shall set the pmsc-segm-id-list-select and/ or pmsc-abs-time-select flag in the PM-Store-Capab attribute.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                                                  |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                                                  |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                                                  |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                                                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>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.</li> <li>2. The PHD under test issues a GET response with the PM-Store attributes it supports, check the values of the PM-Store-Capab attribute: <ol style="list-style-type: none"> <li>a. PM-Store-Capab: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li> <li><input type="checkbox"/> attribute-type = PmStoreCapab</li> <li><input type="checkbox"/> attribute-value = Record the value of bit 6 (Indicates that PM-Segments in the SegmSelection data type can be selected by defining an abs-time-range) and bit 3 (indicates that PM-Segments in the SegmSelection data type can be selected by defining a list of segment identifiers)</li> </ul> </li> </ol> </li> <li>3. The simulated PHG sends a request for the PM-Segment Data with SegmSelection = 1 to obtain all the segments: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_GET_INFO</li> <li><input type="checkbox"/> SegmSelection = all-segments</li> </ul> </li> </ol> </li> <li>4. The PHD under test issues a response with the PM-Segments attributes <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_GET_INFO</li> <li><input type="checkbox"/> SegmentInfoList</li> </ul> </li> </ol> <p>IF bit 3 of PmStoreCapab was set:</p> </li> <li>5. The simulated PHG sends a request for the PM-Segment Data with SegmSelection = segm-id-list which is known because in the previous phase the information of all the segments was retrieved:</li> </ol> |                                                               |                                                  |
+
+- a. Data APDU
+    - Type = Invoke | Confirmed Action,
+    - HANDLE = obj-handle
+    - Action = MDC\_ACT\_SEG\_GET\_INFO
+    - SegmSelection = segm-id-list (List of integers with the instance numbers of the selected Segments)
+6. The PHD under test issues a response with the required PM-Segments attributes:
+- a. Data APDU
+    - Type = Invoke | Confirmed Action,
+    - HANDLE = obj-handle
+    - Action = MDC\_ACT\_SEG\_GET\_INFO
+    - SegmentInfoList
+- IF Protocol Version 3
+7. Simulated PHG sends a Get-Segment-Info:
+- a. Data APDU
+    - Type = Invoke | Confirmed Action,
+    - HANDLE = obj-handle
+    - Action = MDC\_ACT\_SEG\_GET\_INFO
+    - SegmSelection = segm-id-list (empty list)
+8. The PHD under test issues a response with
+- a. Data APDU
+    - Type = Invoke | Confirmed Action,
+    - HANDLE = obj-handle
+    - Action = MDC\_ACT\_SEG\_GET\_INFO
+    - SegmentInfoList = (empty list)
+- IF bit 3 of PMStoreCapab was NOT set:
+9. The simulated PHG sends a Get-Segment-Info:
+- a. Data APDU
+    - Type = Invoke | Confirmed Action,
+    - HANDLE = obj-handle
+    - Action = MDC\_ACT\_SEG\_GET\_INFO
+    - SegmSelection = segm-id-list (List of integers with the instance numbers of the selected Segments)
+10. The PHD under test operation response:
+- a. Data APDU
+    - Type = Roer
+    - ErrorResult = no-such-action (9) or not-allowed-by-object (24)
+- IF bit 6 of PmStoreCapab was set AND the PHD reports absolute-time:
+11. The simulated PHG sends a Get-Segment-Info:
+- a. Data APDU
+    - Type = Invoke | Confirmed Action,
+    - HANDLE = obj-handle
+    - Action = MDC\_ACT\_SEG\_GET\_INFO
+    - SegmSelection = abs-time-range, selecting a range with its boundaries set to an earlier date of any of the existing segments.
+
+12. The PHD under test operation response:
+  - a. Data APDU
+    - Type = Roer
+    - ErrorResult = no-such-action (9)
+13. The simulated PHG sends a Get-Segment-Info:
+  - a. Data APDU
+    - Type = Invoke | Confirmed Action,
+    - HANDLE = obj-handle
+    - Action = MDC\_ACT\_SEG\_GET\_INFO
+    - SegmSelection = abs-time-range, selecting a range with its boundaries set to a later date than any of the existing segments
+14. The PHD under test operation response:
+  - a. Data APDU
+    - Type = Roer
+    - ErrorResult = no-such-action (9)
+15. The simulated PHG sends a Get-Segment-Info:
+  - a. Data APDU
+    - Type = Invoke | Confirmed Action,
+    - HANDLE = obj-handle
+    - Action = MDC\_ACT\_SEG\_GET\_INFO
+    - SegmSelection = abs-time-range, selecting a range with one of its boundaries set to an earlier date than any of the existing segments and the other set to a date contained between Segment-Start-Abs-Time and Segment-End-Abs-Time of one of the PM-Segments
+16. The PHD under test operation response:
+ 
+
+IF NOT Protocol Version 3
+
+  - a. Data APDU
+    - Type = Roer
+    - ErrorResult = no-such-action (9)
+
+ELSE
+
+  - b. Data APDU
+    - Type = Response | Confirmed Action
+    - HANDLE = obj-handle
+  - c. Action = \_ACT\_SEG\_GET\_INFO
+    - SegmentInfoList = {empty}
+17. The simulated PHG sends a Get-Segment-Info:
+  - a. Data APDU
+    - Type = Invoke | Confirmed Action,
+    - HANDLE = obj-handle
+    - Action = MDC\_ACT\_SEG\_GET\_INFO
+    - SegmSelection = abs-time-range, selecting a range with one of its boundaries set to a date contained between Segment-Start-Abs-Time and Segment-End-Abs-Time of one of the PM-Segments and the other set to a date later than any of the existing segments
+18. The PHD under test operation response:
+ 
+
+IF NOT Protocol Version 3
+
+  - a. Data APDU
+
+- Type = Roer
+- ErrorResult = no-such-action (9)
+
+ELSE
+
+- b. Data APDU
+  - Type = Response | Confirmed Action
+  - HANDLE = obj-handle
+  - c. Action = \_ACT\_SEG\_GET\_INFO  SegmentInfoList = {empty}
+
+19. The simulated PHG sends a Get-Segment-Info:
+
+- a. Data APDU
+  - Type = Invoke | Confirmed Action,
+  - HANDLE = obj-handle
+  - Action = MDC\_ACT\_SEG\_GET\_INFO
+  - SegmSelection = abs-time-range, selecting a range with its boundaries set to Segment-Start-Abs-Time and Segment-End-Abs-Time of one of the PM-Segments
+
+20. The PHD under test operation response:
+
+- a. Data APDU
+  - Type = Invoke | Confirmed Action,
+  - HANDLE = obj-handle
+  - Action = MDC\_ACT\_SEG\_GET\_INFO
+  - SegmentInfoList = Containing the attributes of the selected Segments
+
+21. The simulated PHG sends a Get-Segment-Info:
+
+- a. Data APDU
+  - Type = Invoke | Confirmed Action,
+  - HANDLE = obj-handle
+  - Action = MDC\_ACT\_SEG\_GET\_INFO
+  - SegmSelection = abs-time-range, selecting a range with its boundaries set to include inside from Segment-Start-Abs-Time to Segment-End-Abs-Time one of the PM-Segments
+
+22. The PHD under test operation response:
+
+- a. Data APDU
+  - Type = Invoke | Confirmed Action,
+  - HANDLE = obj-handle
+  - Action = MDC\_ACT\_SEG\_GET\_INFO
+  - SegmentInfoList = Containing the attributes of the selected Segments
+
+IF bit 6 of PmStoreCapab was set AND the PHD reports the base-offset-time:
+
+23. The simulated PHG sends a Get-Segment-Info:
+
+- a. Data APDU
+  - Type = Invoke | Confirmed Action,
+  - HANDLE = obj-handle
+  - Action = MDC\_ACT\_SEG\_GET\_INFO
+  - SegmSelection = bo-time-range, selecting a range with its boundaries set to an earlier date than any of the existing segments.
+
+24. The PHD under test operation response:
+
+IF NOT Protocol Version 3
+
+- a. Data APDU
+
+- Type = Roer
+- ErrorResult = no-such-action (9)
+
+ELSE
+
+b. Data APDU
+
+- Type = Response | Confirmed Action
+- HANDLE = obj-handle
+
+c. Action = \_ACT\_SEG\_GET\_INFO
+
+- SegmentInfoList = {empty}
+
+25. The simulated PHG sends a Get-Segment-Info:a.
+
+- Type = Invoke | Confirmed Action,
+- HANDLE = obj-handle
+- Action = MDC\_ACT\_SEG\_GET\_INFO
+- SegmSelection = bo-time-range, selecting a range with its boundaries set to a later date than any of the existing segments.
+
+26. The PHD under test operation response:
+
+IF NOT Protocol Version 3
+
+a. Data APDU
+
+- Type = Roer
+- ErrorResult = no-such-action (9)
+
+ELSE
+
+b. Data APDU
+
+- Type = Response | Confirmed Action
+- HANDLE = obj-handle
+
+c. Action = \_ACT\_SEG\_GET\_INFO
+
+- SegmentInfoList = {empty}
+
+27. The simulated PHG sends a Get-Segment-Info:
+
+a. Data APDU
+
+- Type = Invoke | Confirmed Action,
+- HANDLE = obj-handle
+- Action = MDC\_ACT\_SEG\_GET\_INFO
+- SegmSelection = bo-time-range, selecting a range with one of its boundaries set to an earlier date than any of the existing segments and the other set to a date contained between Segment-Start-Bo-Time and Segment-End-Bo-Time of one of the PM-Segments
+
+28. The PHD under test operation response:
+
+IF NOT Protocol Version 3
+
+a. Data APDU
+
+- Type = Roer
+- ErrorResult = no-such-action (9)
+
+ELSE
+
+b. Data APDU
+
+- Type = Response | Confirmed Action
+- HANDLE = obj-handle
+
+c. Action = \_ACT\_SEG\_GET\_INFO
+
+- SegmentInfoList = {empty}
+
+29. The simulated PHG sends a Get-Segment-Info:
+
+a. Data APDU
+
+- Type = Invoke | Confirmed Action,
+- HANDLE = obj-handle
+- Action = MDC\_ACT\_SEG\_GET\_INFO
+- SegmSelection = bo-time-range, selecting a range with one of its boundaries set to a date contained between Segment-Start-Bo-Time and Segment-End-Bo-Time of one of the PM-Segments and the other set to a later date than any of the existing segments
+
+30. The PHD under test operation response:
+
+IF NOT Protocol Version 3
+
+a. Data APDU
+
+- Type = Roer
+- ErrorResult = no-such-action (9)
+
+ELSE
+
+b. Data APDU
+
+- Type = Response | Confirmed Action
+- HANDLE = obj-handle
+
+c. Action = \_ACT\_SEG\_GET\_INFO
+
+- SegmentInfoList = {empty}
+
+31. The simulated PHG sends a Get-Segment-Info:
+
+a. Data APDU
+
+- Type = Invoke | Confirmed Action,
+- HANDLE = obj-handle
+- Action = MDC\_ACT\_SEG\_GET\_INFO
+- SegmSelection = bo-time-range, selecting a range with its boundaries set to Segment-Start-Bo-Time and Segment-End-Bo-Time of one of the PM-Segments
+
+32. The PHD under test operation response:
+
+a. Data APDU
+
+- Type = Invoke | Confirmed Action,
+- HANDLE = obj-handle
+- Action = MDC\_ACT\_SEG\_GET\_INFO
+- SegmentInfoList = Containing the attributes of the selected Segments
+
+33. The simulated PHG sends a Get-Segment-Info:
+
+a. Data APDU
+
+- Type = Invoke | Confirmed Action,
+- HANDLE = obj-handle
+- Action = MDC\_ACT\_SEG\_GET\_INFO
+- SegmSelection = bo-time-range, selecting a range with its boundaries set to include inside from Segment-Start-Bo-Time to Segment-End-Bo-Time of one of the PM-Segments
+
+34. The PHD under test operation response:
+
+a. Data APDU
+
+- Type = Invoke | Confirmed Action,
+- HANDLE = obj-handle
+- Action = MDC\_ACT\_SEG\_GET\_INFO
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><input type="checkbox"/> SegmentInfoList = Containing the attributes of the selected Segments</p> <p>IF bit 6 of PMStoreCapab was NOT set:</p> <p>35. The simulated PHG sends a Get-Segment-Info:</p> <p>a. Data APDU</p> <p><input type="checkbox"/> Type = Invoke   Confirmed Action,</p> <p><input type="checkbox"/> HANDLE = obj-handle</p> <p><input type="checkbox"/> Action = MDC_ACT_SEG_GET_INFO</p> <p><input type="checkbox"/> SegmSelection = abs-time-range, selecting a range with its boundaries set to the absolute minimum of Absolut-Time type and to the absolute maximum of the Absolute-Time type</p> <p>36. The PHD under test operation response:</p> <p>IF NOT Protocol Version 3</p> <p>a. Data APDU</p> <p><input type="checkbox"/> Type = Roer</p> <p><input type="checkbox"/> ErrorResult = no-such-action (9) or not-allowed-by-object (24)</p> <p>ELSE</p> <p>b. Data APDU</p> <p><input type="checkbox"/> Type = Response   Confirmed Action</p> <p><input type="checkbox"/> HANDLE = obj-handle</p> <p>c. Action = _ACT_SEG_GET_INFO</p> <p><input type="checkbox"/> SegmentInfoList = {empty}</p> |
+| <b>Pass/Fail criteria</b> | The PHD properly sends the required PM-Segment attributes in all cases (all-segments, specific segments and time range selected segments) or the specified error.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              | For Clear-Segment, [ISO/IEEE 11073-20601-2015A] has defined the error code not-allowed-by-object when the PHD does not support the particular action (list of segments or range of segments), but for Get- Segment-Info any error code is defined. For this reason both error codes have been added to the test procedure because the error code used previously is not clearly defined in the change request.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OPX/COM/BV-073                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+| <b>TP label</b>          | Operating procedures. Error Code                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | PersStoreMtrDatTransf 6; M                                    |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If there is an error when the PHG access to a segment of a PM-Store, then the PHD returns an appropriate error code in the response and ignores the transmit request</p>                                                                                                                                                                                                                                                                                                                                            |                                                               |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>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.</li> <li>The simulated PHG sends a request for the PM-Segment Data with SegmSelection = all-segments.</li> <li>The simulated PHG sends a request for the PM-Store Data to a non-existent Segment: <p>a. Data APDU</p> <p><input type="checkbox"/> Type = Invoke   Confirmed Action,</p> <p><input type="checkbox"/> HANDLE = obj-handle</p> </li> </ol> |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> TrigSegmDataXferReq</li> </ul> <p>4. The PHD issues a response:</p> <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> TrigSegmDataXferRsp = tsxr-fail-no-such-segment(1)</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | The response from PHD under test must be of type tsxr-fail-no-such-segment(1).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                              |  |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-073_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                              |  |
+| <b>TP label</b>           | Operating procedures. Transfer PM-Segment content                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                              |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | PersStoreMtrDatTransf 6; M   |  |
+| <b>Test purpose</b>       | Check that:<br>If the PHG accesses successfully to a segment of a PM-Store, then the PHD sends a tsxr-successful response code to indicate that it has received the request and it can be honoured                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                              |  |
+| <b>Applicability</b>      | C_AG_OXP_041 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                              |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                              |  |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                              |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>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.</li> <li>2. The simulated PHG sends a request for the PM-Segment Data with SegmSelection = all-segments.</li> <li>3. The simulated PHG sends a request for the PM-Store Data to a Segment: <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> TrigSegmDataXferReq</li> </ul> </li> </ul> </li> <li>4. The PHD issues a response: <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> TrigSegmDataXferRsp</li> <li><input type="checkbox"/> Check that the invoke-id of the response is mirrored from the request</li> </ul> </li> </ul> </li> </ol> |                              |  |
+| <b>Pass/Fail criteria</b> | TrigSegmDataXferRsp must be one of: <ul style="list-style-type: none"> <li>• tsxr-successful(0)</li> <li>• tsxr-fail-clear-in-process(2)</li> <li>• tsxr-fail-segm-empty(3)</li> <li>• tsxr-fail-not-otherwise-specified(512)</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                              |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                              |  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                                                                                |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/EXP/COM/BV-074                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                                                                                |
+| <b>TP label</b>          | Operating procedures. Segment Data Event                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                                                                                |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                                                                                |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | PersStoreMtrDatTransf 7; M<br>PersStoreMtrDatTransf 10; M     | PersStoreMtrDatTransf 8; M<br>PersStoreMtrDatTransf 12; M<br>CommonCharac 3; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The PHD sends confirmed Segment-Data-Event event reports until all entries in the PM-Segment are sent to the PHG or the transfer is aborted by either the sevsta-agent-abort or sevsta-manager-abort bits</p> <p>[AND]</p> <p>The PHD fills in the SegmentDataEvent structure with information about the segment being sent.</p> <p>[AND]</p> <p>The PHD always sets any sevsta-manager-* bits to 0.</p> <p>[AND]</p> <p>If the message contains the first entry and/or the last entry of the data entries, then the PHD sets the sevsta-first-entry and/or sevsta-last-entry bits, respectively</p> <p>[AND]</p> <p>When transferring a segment, the PHD uses the segm-data-event-entries field to send all the entries.</p> <p>[AND]</p> <p>The total size of the response does not exceed the maximum APDU size established by the specialization</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                                                                                |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                                                                                |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                                                                                |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                                                                                |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Take some measurements with the PHD under test.</li> <li>2. 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.</li> <li>3. The PHD issues a GET response with the PM-Store attributes it supports.</li> <li>4. The simulated PHG sends a request for the PM-Segment info with SegmSelection = 1 to obtain all the segments: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_GET_INFO</li> <li><input type="checkbox"/> SegmSelection = all-segments</li> </ul> </li> </ol> </li> <li>5. The PHD issues a response with the PM-Segments attributes: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_GET_INFO</li> <li><input type="checkbox"/> SegmentInfoList</li> </ul> </li> </ol> </li> <li>6. The simulated PHG sends a request for a PM-Segment Data: <ol style="list-style-type: none"> <li>a. Data APDU</li> </ol> </li> </ol> |                                                               |                                                                                |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> TrigSegmDataXferReq</li> </ul> <p>7. The PHD issues a response:</p> <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> TrigSegmDataXferRsp</li> </ul> </li> </ul> <p>8. The PHD under test starts a Data transfer:</p> <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Invoke   CfmEventReport</li> <li><input type="checkbox"/> Action = MDC_NOTI_SEGMENT_DATA</li> <li><input type="checkbox"/> SegmentDataEvent</li> <li><input type="checkbox"/> Segm-data-event-entries = Data</li> </ul> </li> </ul> <p>9. The simulated PHG responds to transferred data APDU's:</p> <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_NOTI_SEGMENT_DATA</li> <li><input type="checkbox"/> SegmentDataResult</li> </ul> </li> </ul> <p>10. Steps 8 and 9 are repeated until all the data has been sent.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHD replies to the Get request with the requested Data and sevsta-manager-* bits to 0</li> <li>• In the first Data event sent sevsta-first-entry bit must be set by the PHD</li> <li>• In the last data event sent the sevsta-last-entry bit must be set by the PHD</li> <li>• In step 7 the total size of the message cannot exceed the maximum APDU size established by the specialization: <ul style="list-style-type: none"> <li>○ Pulse oximeter → 9216 octets</li> <li>○ Weighing scales → 896 octets</li> <li>○ Glucose meter → 5120 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ Blood pressure → 896 octets</li> <li>○ Thermometer → 896 octets</li> <li>○ Independent activity hub → 5120 octets</li> <li>○ Cardiovascular → 64512 octets or 6624 octets if the PHD supports Step Counter Profile</li> <li>○ Strength → 64512 octets</li> <li>○ Adherence monitor → 1024 octets</li> <li>○ Peak flow → 2030 octets</li> <li>○ Body composition analyser → 7730 octets</li> <li>○ Basic ECG/Simple ECG → 7168 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ Basic ECG/Heart rate → 1280 octets or 64512 octets if the PHD supports PM-Store</li> <li>○ International normalized ratio → 896 octets or 64512 if the PHD supports PM-Store</li> </ul> </li> </ul>                                                                                                                                                                                                                                              |
+
+|              |                                                                                                                                                                                                                                                                                                           |
+|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|              | <ul style="list-style-type: none"> <li>○ Insulin pump → 7168 octets or 5102 if PHD supports PM-Store</li> <li>○ Continuous glucose monitor → 896 octets or 5120 if PHD supports PM-Store</li> <li>○ Power status monitor → 940 octets for Simple PSM profile and 1660 for Advanced PSM profile</li> </ul> |
+| <b>Notes</b> |                                                                                                                                                                                                                                                                                                           |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/ OXP/COM/BV-076                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>TP label</b>          | Operating procedures. PM-Segment structure                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | PersStoreMtrDatTransf 15;<br>M                                |  |
+| <b>Test purpose</b>      | Check that:<br><br>Each entry of the Segment Data is formatted according to the structure defined in the PM-Segment PM-Segment-Entry-Map.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>Applicability</b>     | C_AG_OXP_041 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>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.</li> <li>2. The PHD issues a GET response with the PM-Store attributes.</li> <li>3. The simulated PHG issues a Get-Segment-Info action with SemgSelection set to all-segments, for this test we are interested in: <ol style="list-style-type: none"> <li>a. Mandatory attribute PM-Segment-Entry-Map <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_SEG_MAP</li> <li><input type="checkbox"/> attribute-type = PmSegmentEntryMap</li> <li><input type="checkbox"/> attribute-value =</li> </ul> </li> </ol> </li> <li>4. The simulated PHG sends a request for the PM-Segment that contains data: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> TrigSegmDataXferReq</li> </ul> </li> </ol> </li> <li>5. The PHD issues an action response: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> TrigSegmDataXferRsp</li> </ul> </li> </ol> </li> <li>6. The PHD under test starts Data transfer: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Invoke   CfmEventReport</li> <li><input type="checkbox"/> Action = MDC_NOTI_SEGMENT_DATA</li> <li><input type="checkbox"/> SegmentDataEvent: <ul style="list-style-type: none"> <li>–sevtsta-first-entry(0)=1</li> <li>–segm-data-event-entries=Data</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>7. The simulated PHG responds to transferred data APDU's with an abort transfer:</p> <p>b. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_NOTI_SEGMENT_DATA</li> <li><input type="checkbox"/> SegmentDataResult</li> </ul> <p style="padding-left: 40px;">-sevtsta-manager-abort(12)=1</p> |
+| <b>Pass/Fail criteria</b> | The format of the data has to coincide with the format expressed in the PmSegmentEntryMap field and the PHD does not send any SegmentDataEvent after step 7.                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|------------------|
+| <b>TP Id</b>              | TP/PLT/PHD/EXP/COM/BV-080                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                  |
+| <b>TP label</b>           | Release Request. Outstanding invoke-id                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | DisassocProc 3;M                                              | DisassocProc 4;M |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>Should a PHD receive an Association Release Request when it has an outstanding invoke-id, it shall respond with an Association Release Respond and assume that it shall receive no response to its request.</p> <p>[AND]</p> <p>After the side that received the Association Release Request sends the Association Release Response, it shall transition to the Unassociated state</p> <p>[AND]</p> <p>When the peer receives the Association Release Response, it shall transition to the Unassociated state</p>                                                                                    |                                                               |                  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                  |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |                  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an Associating Request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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. TOconfig is started.</li> <li>4. The simulated PHG sends a Release Request with Reason = 0 "normal".</li> <li>5. The PHD under test responds with a Release Response and changes to the Unassociated state.</li> <li>6. Wait for a time equal to TOconfig.</li> </ol> |                                                               |                  |
+| <b>Pass/Fail criteria</b> | <p>During the period of step 6 the PHD does not send any abort message.</p> <p>After that point, the only message that may be received by the PHG is a new Association request.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                  |
+
+|                 |                                                    |                                                               |  |
+|-----------------|----------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>    | TP/PLT/PHD/EXP/COM/BV-081_A                        |                                                               |  |
+| <b>TP label</b> | Disassociating procedure. Release Request Reason 1 |                                                               |  |
+| <b>Coverage</b> | <b>Spec</b>                                        | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                 | <b>Testable items</b>                              | DisassocProc 2; M                                             |  |
+
+|                           |                                                                                                                                                                             |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>       | Check that:<br>The Association Release Request contains a ReleaseRequestReason with reason = normal to indicate the reason for releasing the association                    |
+| <b>Applicability</b>      | C_AG_OXP_186 AND C_AG_OXP_000                                                                                                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                             |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                            |
+| <b>Test procedure</b>     | 1. Force the PHD to send a Release Request.<br>2. Check that the PHG receives a Release Request with reason = normal (0).                                                   |
+| <b>Pass/Fail criteria</b> | The Association Release Request contains a ReleaseRequestReason to indicate the reason for releasing the association. The Reason code shall be the one described in step 2. |
+| <b>Notes</b>              |                                                                                                                                                                             |
+
+|                           |                                                                                                                                                                                                     |                                                               |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-081_B                                                                                                                                                                         |                                                               |
+| <b>TP label</b>           | Disassociating procedure. Release Request Reason 2                                                                                                                                                  |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                         | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                               | DisassocProc 2; M                                             |
+| <b>Test purpose</b>       | Check that:<br>The Association Release Request contains a ReleaseRequestReason with reason = configuration-changed to indicate the reason for releasing the association                             |                                                               |
+| <b>Applicability</b>      | C_AG_OXP_191 AND C_AG_OXP_000                                                                                                                                                                       |                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                     |                                                               |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                    |                                                               |
+| <b>Test procedure</b>     | 1. Change the configuration of the PHD under test (adding or removing objects from the DIM).<br>2. Check that the simulated PHG receives a Release Request with reason = configuration-changed (2). |                                                               |
+| <b>Pass/Fail criteria</b> | The Association Release Request contains a ReleaseRequestReason to indicate the reason for releasing the association. The Reason code shall be the one described in step 2.                         |                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                     |                                                               |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/COM/BV-081_C                                                                                                                                                                                                                                                                                                                                                                      |                                                               |
+| <b>TP label</b>          | Disassociating procedure. Release Request Reason 3                                                                                                                                                                                                                                                                                                                                               |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                      | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                            | DisassocProc 2; M                                             |
+| <b>Test purpose</b>      | Check that:<br>The Association Release Request contains a ReleaseRequestReason with reason = no-more-configurations to indicate the reason for releasing the association                                                                                                                                                                                                                         |                                                               |
+| <b>Applicability</b>     | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                 |                                                               |
+| <b>Test procedure</b>    | 1. Disconnect and again connect the PHD under test to the simulated PHG.<br>2. The simulated PHG receives an association request from the PHD under test.<br>3. The simulated PHG responds with a result = accepted-unknown-config.<br>4. 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. |                                                               |
+
+|                           |                                                                                                                               |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------|
+|                           | 5. The simulated PHG responds with an "unsupported-config".<br>6. Repeat steps 4 and 5 until the PHD sends a Release Request. |
+| <b>Pass/Fail criteria</b> | The Association Release Request contains a ReleaseRequestReason = no-more-configurations (1).                                 |
+| <b>Notes</b>              |                                                                                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                   |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-------------------|
+| <b>TP Id</b>              | TP/PLT/PHD/OPX/COM/BV-083                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                   |
+| <b>TP label</b>           | Disassociating procedure. Association Release Response                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                   |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                   |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | DisassocProc 8; M                                             | DisassocProc 9; M |
+| <b>Test purpose</b>       | Check that:<br><br>When the PHD sends an Association Release message and waits for an Association Release Response message for a TO <sub>release</sub> period without receives it, then the PHD sends an Association Abort message and moves to Unassociated state                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                   |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                   |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                   |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                   |
+| <b>Test procedure</b>     | 1. IF the PHD under test can be forced by the user to send a release request, send it. If not, follow this procedure: <ol style="list-style-type: none"> <li>Disconnect and again connect the PHD under test to the simulated PHG.</li> <li>The simulated PHG receives an association request from the PHD under test.</li> <li>The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>The simulated PHG responds with an "unsupported-config".</li> <li>Repeat steps d and e until the PHD sends a Release Request.</li> </ol> 2. Once the PHD under test has sent a Release Request: <ol style="list-style-type: none"> <li>The simulated PHG does not respond to the request for at least TO<sub>Release</sub> (3 seg.).</li> </ol> |                                                               |                   |
+| <b>Pass/Fail criteria</b> | The PHD waits the TO <sub>Release</sub> time and then it must send an abort message to the PHG.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                   |
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |              |
+|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------|
+| <b>TP Id</b>        | TP/PLT/PHD/OPX/COM/BV-084                                                                                                                                                                                                                                                                                                                                                                         |                                                               |              |
+| <b>TP label</b>     | Absolute time 1                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |              |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |              |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                             | TimeCoord 1; C                                                | AbsTime 1; C |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                   | AbsTime 3; C                                                  | AbsTime 5; C |
+| <b>Test purpose</b> | Check that:<br><br>All bits references in the subclauses are part of this attribute [Mds-time-Info]<br>[AND]<br>If the PHD has an internal real-time clock (RTC), then it indicates this capability by setting the mds-time-capab-real-time-clock bit<br>[AND]<br>If the PHD supports the Set-Time action, then it indicates this capability by setting the mds-time-capab-set-clock bit<br>[AND] |                                                               |              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>The PHD indicates whether it synchronizes absolute time using the mds-time-capab-sync-abs-time bit</p> <p>[AND]</p> <p>The mds-time-state-abs-time-synced bit is set only when the PHD believes its wall clock time is synchronized with the external clock source.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Applicability</b>      | C_AG_OXP_009 AND C_AG_OXP_013 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Other PICS</b>         | C_AG_OXP_007                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG issues "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.</li> <li>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. The attribute of interest of this test is MDSTimeInfo: <ol style="list-style-type: none"> <li>a. Mds-Time-Info: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MDS_TIME_INFO (0X0A 0X45)</li> <li><input type="checkbox"/> attribute-type = MdsTimeInfo</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> mds-time-capab-real-time-clock must be set</li> </ul> </li> <li>b. IF the PHD can synchronize its absolute time then: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MDS_TIME_INFO (0X0A 0X45)</li> <li><input type="checkbox"/> attribute-type = MdsTimeInfo</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> mds-time-capab-sync-abs-time must be set</li> <li><input type="checkbox"/> time-sync-protocol field must indicate what protocol is used for synchronization</li> </ul> </li> </ol> </li> <li>3. IF mds-time-capab-sync-abs-time = 1 THEN: <ol style="list-style-type: none"> <li>a. Ask the test operator to connect the external source that is going to be used to synchronize the PHD AbsoluteTime</li> <li>b. The simulated PHG issues 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.</li> <li>c. 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: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MDS_TIME_INFO (0X0A 0X45)</li> <li><input type="checkbox"/> attribute-type = MdsTimeInfo</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> mds-time-capab-sync-abs-time must be set</li> <li><input type="checkbox"/> mds-time-state-abs-time-synced must be set</li> </ul> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | Check that the attribute mds-time-cap-state has correct values.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                     |                                                                                                                    |                                                               |                 |
+|---------------------|--------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------|
+| <b>TP Id</b>        | TP/PLT/PHD/OMP/COM/BV-085_A                                                                                        |                                                               |                 |
+| <b>TP label</b>     | Absolute time 2                                                                                                    |                                                               |                 |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                        | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                 |
+|                     | <b>Testable items</b>                                                                                              | AbsTime 11; C                                                 | MDSService 7; O |
+| <b>Test purpose</b> | <p>Check that:</p> <p>If a PHD is associated with a PHG when Date-and-Time is adjusted, then it sends an event</p> |                                                               |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | report that contains the new Date-and-Time.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Applicability</b>      | C_AG_OXP_006 AND C_AG_OXP_009 AND C_AG_OXP_012 AND C_AG_OXP_000 AND C_AG_OXP_016                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Take a measurement with the PHD.</li> <li>2. Make a noticeable change in the Date or Time of the PHD.</li> <li>3. Take a new measurement.</li> <li>4. Wait for a roiv-cmip-event-report OR a roiv-cmip-confirmed-event-report from the PHD.</li> <li>5. Verify that the device sends a variable format event report to update the Date-and-Time attribute on the MDS before it sends any measurement updates and that every measure taken before the time change is sent in the same event report.</li> </ol> |
+| <b>Pass/Fail criteria</b> | The PHD transmitted data comes from the same unbroken timeline which means that every measure taken before the time change has a date-and-time-adjustment.                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/COM/BV-085_B                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>TP label</b>          | Absolute time 2: PM-Store                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | AbsTime 14; C                                                 |  |
+| <b>Test purpose</b>      | Check that:<br><br>If a PHD collects PM-Store measurements and the Date-and-Time is adjusted, then the PHD ensures that each PM-Segment includes only measurements from the same unbroken timeline                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Applicability</b>     | C_AG_OXP_012 AND C_AG_OXP_041 AND C_AG_OXP_000 AND C_AG_OXP_016                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. While the PHD is disconnected, make it store measurements in PM-Segments of every PM-Store, after doing this, connect the PHD.</li> <li>2. The simulated PHG receives an association request from the PHD under test.</li> <li>3. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>4. The PHD responds with a "Remote Operation Invoke   Confirmed Event Report" message: <ul style="list-style-type: none"> <li>o Event-type=MDC_NOTI_CONFIG</li> </ul> </li> <li>5. IF C_AG_OXP_293 THEN: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 THEN it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ol> </li> <li>6. Record the PM-Store handle, PM-Store-Capab and Number-Of-Segments of every PM-Store object.</li> <li>7. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object</li> </ol> |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>with SegmSelection set to all-segments.</p> <ol style="list-style-type: none"> <li>8. The PHD shall respond to the Get-Segment-Info, indicating the attributes of the PM-Segment.</li> <li>9. Make a noticeable change in the Date or Time of the PHD.</li> <li>10. Take a new measurement.</li> <li>11. The simulated PHG shall send a Get-command for every PM-Store.</li> <li>12. The PHD shall respond to the Get command, indicating the attributes of the PM-Store. Record.</li> <li>13. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection set to all-segments.</li> <li>14. The PHD shall respond to the Get-Segment-Info, indicating the attributes of the PM-Segment: <ul style="list-style-type: none"> <li>○ The Date-and-Time adjustment attribute is present</li> <li>○ If the pm-sc-var-no-of-segm is set to 1 (PM-Store-Capab) then verify that the Pm-Store has created a new segment</li> </ul> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• If the pm-sc-var-no-of-segm is set to 1, the number of segments recorded in step 6 has increased in step 12 and the Date and Time Adjustment is present for every new added segment</li> <li>• If the pm-sc-var-no-of-segm is set to 0, the Date and Time Adjustment is present at least for one segment</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |               |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-085_C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |               |
+| <b>TP label</b>           | Absolute time 2: Store and Forward                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |               |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | AbsTime 12; C                                                 | AbsTime 13; C |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>If a PHD collects temporary measurements and the Date-and-Time is adjusted, then the PHD ensures that all measurements included in an event report come from the same unbroken timeline</p> <p>[AND]</p> <p>The first reported data in the event report shall be the MDS attribute Date-and-Time-Adjustment that defines the number of 1/100th of seconds to add to align with the current clock (e.g. if the clock was advanced by 60 minutes, this would report 360000) followed by measurement data.</p> |                                                               |               |
+| <b>Applicability</b>      | C_AG_OXP_009 AND C_AG_OXP_012 AND C_AG_OXP_032 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |               |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the disconnected state.                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Take some measurements with the PHD under test.</li> <li>2. Make a change in the Date or Time of the PHD by advancing its clock 60 minutes.</li> <li>3. Take new measurements.</li> <li>4. Connect the PHD under test to the simulated PHG.</li> <li>5. Once in the Operating state the PHG has to receive a variable event report containing the Date-and-Time-Adjustment attribute with the value = 360000.</li> </ol>                                                                |                                                               |               |
+| <b>Pass/Fail criteria</b> | The PHD recorded data before the Time change must be in a different segment than those recorded after the time change.                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                   |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-------------------|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-086                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                   |
+| <b>TP label</b>           | Relative time 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                   |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                   |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | RelativeTime 2; C                                             | RelativeTime 5; C |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>The PHD indicates that supports relative time by setting the mds-time-capab-relative-time bit in the Mds-Time-Info attribute</p> <p>[AND]</p> <p>The PHD indicates whether it synchronizes relative time using the mds-time-capab-sync-rel-time bit.</p> <p>[AND]</p> <p>If synchronization is supported, then the mds-time-state-rel-time-synced bit is set only when the PHD believes its relative clock is synchronized with the external source</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                   |
+| <b>Applicability</b>      | C_AG_OXP_010 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                   |
+| <b>Other PICS</b>         | C_AG_OXP_007, C_AG_OXP_008                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                   |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                   |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG issues 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.</li> <li>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: <ol style="list-style-type: none"> <li>a. Mds-Time-Info shall be present: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MDS_TIME_INFO (0X0A 0X45)</li> <li><input type="checkbox"/> attribute-type = MdsTimeInfo</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> mds-time-capab-relative-time must be set</li> </ul> </li> <li>b. IF the PHD can synchronize its relative timer then: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MDS_TIME_INFO (0X0A 0X45)</li> <li><input type="checkbox"/> attribute-type = MdsTimeInfo</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> mds-time-capab-sync-rel-time must be set</li> <li><input type="checkbox"/> time-sync-protocol field must indicate what protocol is used for synchronization</li> </ul> </li> </ol> </li> <li>3. IF the mds-time-capab-sync-rel-time = 1 THEN: <ol style="list-style-type: none"> <li>a. Ask the test operator to connect the external source that is going to be used to synchronize the PHD Relative-Time.</li> <li>b. The simulated PHG issues 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.</li> <li>c. 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: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MDS_TIME_INFO (0X0A 0X45)</li> <li><input type="checkbox"/> attribute-type = MdsTimeInfo</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> mds-time-capab-sync-rel-time must be set</li> <li><input type="checkbox"/> mds-time-state -rel-time-synced must be set</li> </ul> </li> </ol> </li> </ol> |                                                               |                   |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                   |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |                         |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/EXP/COM/BV-087                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                         |
+| <b>TP label</b>          | High-resolution Relative time                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                         |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                         |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Hi-resRelativeTime 1; C                                       | Hi-resRelativeTime 4; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Hi-resRelativeTime 6; C                                       | Hi-resRelativeTime 5; C |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The PHD indicates support for high resolution relative time by setting the mds-time-capab-high-res-relative-time bit in the Mds-Time-Info attribute</p> <p>[AND]</p> <p>If synchronization is supported, then the PHD sets mds-time-state-hi-res-relative-time-synced bit only when it believes its relative clock is synchronized with the external source.</p> <p>[AND]</p> <p>When the PHD disconnects from the clock synchronization source, it clears the synced bit as soon as it exceeds the accuracy of the clock synchronization parameters.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |                         |
+| <b>Applicability</b>     | C_AG_OXP_011 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                         |
+| <b>Other PICS</b>        | C_AG_OXP_007, C_AG_OXP_008                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                         |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                         |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG issues 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.</li> <li>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: <ol style="list-style-type: none"> <li>a. To support Hires-Relative Time: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MDS_TIME_INFO (0X0A 0X45)</li> <li><input type="checkbox"/> attribute-type = MdsTimeInfo</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> mds-time-capab-high-res-relative-time must be set</li> </ul> </li> <li>b. IF the PHD can synchronize its High Resolution Relative timer then: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MDS_TIME_INFO (0X0A 0X45)</li> <li><input type="checkbox"/> attribute-type = MdsTimeInfo</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> mds-time-capab-sync-hi-res-relative-time must be set</li> <li><input type="checkbox"/> time-sync-protocol field must indicate what protocol is used for synchronization</li> </ul> </li> </ol> </li> <li>3. IF the mds-time-capab-sync-hi-res-relative-time = 1 THEN: <ol style="list-style-type: none"> <li>c. Ask the test operator to connect the external source that is going to be used to synchronize the PHD Hi-Resolution-Relative-Time.</li> <li>d. The simulated PHG issues 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.</li> <li>e. 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: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MDS_TIME_INFO (0X0A 0X45)</li> <li><input type="checkbox"/> attribute-type = MdsTimeInfo</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> mds-time-capab-sync-hi-res-relative-time must be set</li> <li><input type="checkbox"/> mds-time-state-hi-resrelative-time-synced must be set</li> <li><input type="checkbox"/> time-sync-accuracy will be recorded.</li> </ul> </li> </ol> </li> </ol> |                                                               |                         |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>f. Ask the test operator to disconnect the external source that has been used to synchronize the PHD Hi-Resolution-Relative-Time.</p> <p>g. Wait a time interval longer than the time specified in time-sync-accuracy; if it is undefined, the test operator has to wait a discretionary time that is enough to exceed the accuracy of the clock synchronization.</p> <p>h. The simulated PHG issues 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.</p> <p>i. 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:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MDS_TIME_INFO (0X0A 0X45)</li> <li><input type="checkbox"/> attribute-type = MdsTimeInfo</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> mds-time-state-hi-resrelative-time-synced must be clear</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/COM/BV-088                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |  |
+| <b>TP label</b>          | Base-Offset-Time 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | BaseTimOffset1; M                                             |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If the base time is changed, then the time adjustment shall be indicated using the same mechanisms as for absolute time.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Applicability</b>     | C_AG_OXP_014 AND C_AG_OXP_013 AND C_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>Other PICS</b>        | C_AG_OXP_007                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |  |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG issues 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.</li> <li>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. The attribute of interest of this test is MDSTimeInfo: <ol style="list-style-type: none"> <li>a. Mds-Time-Info: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MDS_TIME_INFO (0X0A 0X45)</li> <li><input type="checkbox"/> attribute-type = MdsTimeInfo</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> mds-time-capab-bo-time must be set</li> </ul> </li> <li>b. IF the PHD can synchronize its base-offset-time (i.e., C_AG_OXP_007 = TRUE) THEN: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MDS_TIME_INFO (0X0A 0X45)</li> <li><input type="checkbox"/> attribute-type = MdsTimeInfo</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> mds-time-capab-sync-bo-time must be set</li> <li><input type="checkbox"/> time-sync-protocol = MDC_TIME_SYNC_EBWW or MDC_TIME_SYNC_NTPV3 or MDC_TIME_SYNC_NTPV4 or MDC_TIME_SYNC_SNTPV4 or MDC_TIME_SYNC_SNTPV4330 or MDC_TIME_SYNC_BTV1</li> </ul> </li> </ol> </li> <li>3. IF mds-time-capab-sync-bo-time = 1 THEN:</li> </ol> |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ol style="list-style-type: none"> <li>a. Ask the test operator to connect the external source that is going to be used to synchronize the PHD Base-Offset time.</li> <li>b. The simulated PHG issues 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.</li> <li>c. 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: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MDS_TIME_INFO (0X0A 0X45)</li> <li><input type="checkbox"/> attribute-type = MdsTimeInfo</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> mds-time-capab-sync-bo-time must be set</li> <li><input type="checkbox"/> mds-time-state-bo-time-synced must be set</li> </ul> </li> </ol> |
+| <b>Pass/Fail criteria</b> | Check the attribute mds-time-cap-state has correct values.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-092                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>TP label</b>           | Supported Standard Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | ConfNormalProc 16; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br>The PHD sends the supported standard configurations as a fall back if the extended configurations are unsupported.                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_001 AND C_AG_OXP_002 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. The simulated PHG responds with a "unsupported-config".</li> <li>5. Repeat steps 3 and 4 until the PHD sends a Release Request with reason = "no-more-configurations".</li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | The PHD under test must send at least one configuration with dev-config-id = <between 0x00 0x01 and 0x3F 0xFF > (standard range values) as a fallback if the extended configurations are not supported by the simulated PHG.                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |
+
+|                      |                                                                           |                                                               |  |
+|----------------------|---------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>         | TP/PLT/PHD/OXP/COM/BV-093                                                 |                                                               |  |
+| <b>TP label</b>      | Operating State. Abort message                                            |                                                               |  |
+| <b>Coverage</b>      | <b>Spec</b>                                                               | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                      | <b>Testable items</b>                                                     | AgentStateMach 63; M                                          |  |
+| <b>Test purpose</b>  | Check that:<br>If abrt received, then the PHD moves to Unassociated state |                                                               |  |
+| <b>Applicability</b> | C_AG_OXP_000                                                              |                                                               |  |
+| <b>Other PICS</b>    |                                                                           |                                                               |  |
+
+|                           |                                                                                                                                                                        |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b>  | The simulated PHG and PHD are in the Operating state.                                                                                                                  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG sends an Abort message to the PHD under test.</li> <li>2. Wait for an event report for the PHD.</li> </ol> |
+| <b>Pass/Fail criteria</b> | The simulated PHG must not receive any message other than an Association Request.                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                        |
+
+|                           |                                                                                                                                                                                                                                                                 |                                                               |  |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-096_A                                                                                                                                                                                                                                     |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Connected Associated Configuring Waiting Approval 11                                                                                                                                                                                       |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                           | AgentStateMach 78; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br><br>If prst (Any APDU not covered in 5.* (corrupt, unknown, unexpected, etc) is received while in the Waiting Approval state, then the PHD transmits an abort message abrt (reason undefined) and moves to Unassociated state                    |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                 |                                                               |  |
+| <b>Initial condition</b>  | The PHD under test is in the Waiting Approval state.                                                                                                                                                                                                            |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG sends a badly formatted message.</li> <li>2. The PHD under test sends an abort message abrt(Abort-reason undefined) to the PHG and shall pass to the Unassociated state.</li> </ol>                 |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHD sends the Abort message (abrt) with reason undefined and changes to the Unassociated state</li> <li>• The simulated PHG must not receive any message other than an Association Request after step 2</li> </ul> |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                 |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                            |                                                               |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-097                                                                                                                                                                                                                                                  |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Leaving Operating State 5                                                                                                                                                                                                                             |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                      | AgentStateMach 80; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br><br>If prst (Any APDU not covered in 2.* (corrupt, unknown, unexpected, etc)) is received while in Operating state, then the PHD transmits an abrt (reason undefined) and moves to Unassociated state.                                                      |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                               |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>Initial condition</b>  | The PHD under test is in the Operating state.                                                                                                                                                                                                                              |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG issues a Prst message, rors-cmip- get.</li> <li>2. The PHD under test sends an abort message abrt(Abort-reason undefined) to the PHG and shall pass to the Unassociated state.</li> </ol>                      |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHD under test sends the Abort message (abrt) with reason undefined and changes to the Unassociated state</li> <li>• The simulated PHG must not receive any message other than an Association Request after step 2</li> </ul> |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                            |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                        |                                                               |  |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OPX/COM/BV-097_A                                                                                                                                                                                                                                            |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Leaving Operating State 6                                                                                                                                                                                                                         |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                  | AgentStateMach 80; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br><br>If prst (Any APDU not covered in 8.* (corrupt, unknown, unexpected, etc)) is received while in Operating state, then the PHD transmits an abrt (reason undefined) and moves to Unassociated state                                                   |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Initial condition</b>  | The PHD under test is in the Operating state.                                                                                                                                                                                                                          |                                                               |  |
+| <b>Test procedure</b>     | 1. The simulated PHG sends a badly formatted message.<br>2. The PHD under test sends an abort message abrt(Abort-reason undefined) to the PHG and shall pass to the Unassociated state.                                                                                |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The PHD under test sends the Abort message (abrt) with reason undefined and changes to the Unassociated state</li> <li>The simulated PHG must not receive any message other than an Association Request after step 2</li> </ul> |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                        |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OPX/COM/BV-098_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Connected Disassociation 7                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | AgentStateMach 81; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br><br>If prst (Any APDU not covered in 9.* (corrupt, unknown, unexpected, etc) is received while in the Disassociating state, then the PHD transmits an abrt (Abort-reason undefined) and moves to Unassociated state                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Initial condition</b>  | The PHD is in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |  |
+| <b>Test procedure</b>     | 1. The PHD under test sends an Association Request to the simulated PHG.<br>2. The simulated PHG responds with an accepted-unknown-config.<br>3. The PHD under test sends a configuration event report.<br>4. The simulated PHG responds with an unsupported-configuration.<br>5. The PHD sends a new configuration event report with a new configuration (if it has more).<br>6. Repeat the last two steps recording all the ConfigId-values until the PHD sends a Release Request with the reason "no-more-configurations". The PHD moves to the Disassociating state.<br>7. The simulated PHG sends a badly formatted message.<br>8. The PHD responds with an Abort message (abrt) with reason undefined.<br>9. The PHD and the PHG move to the Unassociated state. |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The PHD under test sends the abort message (abrt) with reason undefined and changes to the Unassociated state</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+
+|              |                                                                                                                                                  |
+|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
+|              | <ul style="list-style-type: none"> <li>The simulated PHG must not receive any message other than an Association Request after step 9.</li> </ul> |
+| <b>Notes</b> |                                                                                                                                                  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-099                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>TP label</b>           | Operating procedures. PM-Store Specific Attributes request                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | PersStoreMtrDatTransf 2; C                                    |  |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>The attribute-id-list shall be left empty to query for all attributes of the PM-store object. Alternatively, specific attributes of an object may be queried by listing the desired Attribute IDs found in Table 9. It is not required for a PHD to support this capability. If this capability is not implemented then the PHD shall respond with an error (roer) message with an error-value of not-allowed-by-object</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_041                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |
+| <b>Other PICS</b>         | C_AG_OXP_101                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated PHG issues a "Remote Operation Invoke   Get" command with:               <ol style="list-style-type: none"> <li>the Obj-handle set to PM-Store object handle (to request its attributes)</li> <li>the attribute-id-list.count=1 and a single AVA_Type MDC_ATTR_PM_STORE_CAPAB (0X0A 0X4D) to retrieve the mandatory "PM-Store-Capab" attribute</li> </ol> </li> <li>The PHD under test responds with:               <ul style="list-style-type: none"> <li>IF C_AG_OXP_101 THEN: with a "rors-cmip-get" service message which contains the "PM-Store-Capab"</li> <li>ELSE: with a "roer" service message with the error-value set to not-allowed-by-object (24)</li> </ul> </li> <li>The simulated PHG issues a "Remote Operation Invoke   Get" command with:               <ol style="list-style-type: none"> <li>the Obj-handle set to PM-Store object handle (to request its attributes)</li> <li>the attribute-id-list empty to request all the attributes of PM-Store object</li> </ol> </li> <li>The PHD responds with a "rors-cmip-get" service message which contains all the supported attributes of the PM-Store object.</li> <li>The simulated PHG issues a "Remote Operation Invoke   Get" command with:               <ol style="list-style-type: none"> <li>the Obj-handle set to PM-Store object handle (to request its attributes)</li> <li>the attribute-id-list set to an attribute NOT supported by the PM-Store object</li> </ol> </li> <li>The PHD responds with a "rors-cmip-get" service message:               <ul style="list-style-type: none"> <li>IF C_AG_OXP_101 THEN: the attribute-list must be empty</li> <li>ELSE: with a "roer" service message with the error-value set to not-allowed-by-object (24)</li> </ul> </li> <li>The simulated PHG issues a "Remote Operation Invoke   Get" command with:               <ol style="list-style-type: none"> <li>the Obj-handle set to PM-Store object handle (to request its attributes)</li> <li>the attribute-id-list contains one supported attribute and one unsupported attribute</li> </ol> </li> <li>The PHD responds with a "rors-cmip-get" service message:               <ul style="list-style-type: none"> <li>IF C_AG_OXP_101 THEN: the attribute-list must contain the supported attribute</li> <li>ELSE: with a "roer" service message with the error-value set to not-allowed-by-object (24)</li> </ul> </li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>In step 2 the PHD properly sends the requested attribute or the error</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+
+|              |                                                                                                                                                                         |
+|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|              | <ul style="list-style-type: none"> <li>In steps 6 and 8 the received attribute list must be empty if NOT C_AG_OXP_101 or roer if the action is not supported</li> </ul> |
+| <b>Notes</b> |                                                                                                                                                                         |
+
+|                           |                                                                                                                                                                                                                                                                                      |                                                               |  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-100                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Leaving the Configuring/Waiting GetMDS Substate 1                                                                                                                                                                                                               |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                | AgentStateMach 91; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br><br>If Rlrq is received while in the Configuring/Waiting GetMDS substate, a PHD shall transmit an Rlre (normal) and move to the Unassociated state                                                                                                                    |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_293                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                      |                                                               |  |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in Configuring state. The PHD is in the Configuring/Waiting GetMDS substate and the Simulated PHG is in the Configuring/Sending GetMDS substate.                                                                                            |                                                               |  |
+| <b>Test procedure</b>     | 1. The simulated PHG sends an Association Release Request (Rlrq) message to the PHD under test with reason=0 (normal)<br><br>2. The PHD under test shall respond with an Association Release Response (Rlre) message with reason=0 (normal), and shall go to the Unassociated state. |                                                               |  |
+| <b>Pass/Fail criteria</b> | The PHD under test transmits correctly the Rlre message                                                                                                                                                                                                                              |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                      |                                                               |  |
+
+|                          |                                                                                                                                                                                                 |                                                               |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/COM/BV-101                                                                                                                                                                       |                                                               |  |
+| <b>TP label</b>          | Agent State machine. Leaving the Configuring/Waiting GetMDS Substate 2                                                                                                                          |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                     | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                           | AgentStateMach 92; M                                          |  |
+| <b>Test purpose</b>      | Check that:<br><br>If Rlre is received while in the Configuring/Waiting GetMDS substate, then PHD transmits an Abrt (Abort-reason undefined) and moves to the Unassociated state.               |                                                               |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_293                                                                                                                                                                   |                                                               |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                 |                                                               |  |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in Configuring state. PHD is in the Configuring/Waiting GetMDS substate and Simulated PHG is in the Configuring/Sending GetMDS substate.               |                                                               |  |
+| <b>Test procedure</b>    | 1. The simulated PHG sends Association Release Response to the PHD under test, with reason=0 (normal)<br><br>2. The PHD under test responds with an Abort message (Abrt) with reason undefined. |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                    |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The PHD under test transmits correctly the Abort message (Abrt) with reason undefined and changes to Unassociated state.</li> <li>The simulated PHG must not receive any message other than an Association Request after step 2.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                    |
+
+|                           |                                                                                                                                                                                   |                                                               |  |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-102                                                                                                                                                         |                                                               |  |
+| <b>TP label</b>           | Configuring/Waiting GetMDS Substate. Abort message                                                                                                                                |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                             | AgentStateMach 93; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br>If abrt received, then the PHD moves to Unassociated state                                                                                                         |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_293                                                                                                                                                     |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                   |                                                               |  |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in Configuring state. PHD is in the Configuring/Waiting GetMDS substate and Simulated PHG is in the Configuring/Sending GetMDS substate. |                                                               |  |
+| <b>Test procedure</b>     | 1. The simulated PHG sends an Abort Message to the PHD under test<br>2. Wait for an event report for PHD.                                                                         |                                                               |  |
+| <b>Pass/Fail criteria</b> | The simulated PHG must not receive any message other than an Association Request.                                                                                                 |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                   |                                                               |  |
+
+|                          |                                                                                                                                                                                                                                  |                                                               |  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/COM/BV-103                                                                                                                                                                                                        |                                                               |  |
+| <b>TP label</b>          | Agent State machine. Leaving the Configuring/Waiting GetMDS Substate 3                                                                                                                                                           |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                      | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                            | AgentStateMach 94; M                                          |  |
+| <b>Test purpose</b>      | Check that:<br>If prst (Any APDU not covered in 8.* (corrupt, unknown, unexpected, etc)) is received while in Configuring/Waiting GetMDS substate, then PHD transmits an abrt (reason undefined) and moves to Unassociated state |                                                               |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_293                                                                                                                                                                                                    |                                                               |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                  |                                                               |  |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in Configuring state. PHD is in the Configuring/Waiting GetMDS substate and Simulated PHG is in the Configuring/Sending GetMDS substate.                                                |                                                               |  |
+| <b>Test procedure</b>    | 1. The simulated PHG issues a Prst message, rors-cmip- get.<br>2. The PHD under test sends an abort message abrt(reason undefined) to the PHG and shall pass to the Unassociated state                                           |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                         |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The PHD under test sends the Abort message abrt(reason undefined) and changes to Unassociated</li> <li>The simulated PHG must not receive any message other than an Association Request after step 2.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                         |
+
+|                           |                                                                                                                                                                                                                                                                                                        |                                                               |  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-104                                                                                                                                                                                                                                                                              |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Connected Associated Configuring/Waiting GetMDS 1                                                                                                                                                                                                                                 |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                  | AgentStateMach 95; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br><br>If roiv-cmip-get (handle = 0) is received while in Waiting GetMDS substate, then PHD transmits a rors-cmip-get (MDS attributes) and moves to Waiting SetTime substate or Operating state.                                                                                           |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_293                                                                                                                                                                                                                                                                          |                                                               |  |
+| <b>Other PICS</b>         | C_AG_OXP_004                                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in Configuring state. PHD is in the Configuring/Waiting GetMDS substate and Simulated PHG is in the Configuring/Sending GetMDS substate.                                                                                                                      |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated PHG issues GET with (handle = 0)</li> <li>The PHD under test must send a rors-cmip-get with MDS attributes.</li> <li>IF C_AG_OXP_004, PHD under test moves in Waiting SetTime substate. ELSE, PHD under test moves to Operating state.</li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | Process detailed above must be successfully completed                                                                                                                                                                                                                                                  |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                        |                                                               |  |
+
+|                          |                                                                                                                                                                                                          |                                                               |  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/COM/BV-105                                                                                                                                                                                |                                                               |  |
+| <b>TP label</b>          | Agent State machine. Connected Associated Configuring/Waiting GetMDS 2                                                                                                                                   |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                    | AgentStateMach 96; M                                          |  |
+| <b>Test purpose</b>      | Check that:<br><br>If roiv-* but not (roiv-cmip-get, handle=0) is received while in Waiting GetMDS substate, then PHD transmits a roer (no-such-object-instance) and remains in Waiting GetMDS substate. |                                                               |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_293                                                                                                                                                                            |                                                               |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                          |                                                               |  |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in Configuring state. PHD is in the Configuring/Waiting GetMDS substate and Simulated PHG is in the Configuring/Sending GetMDS substate.                        |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG issues a roiv-cmip-get (handle = 1)</li> <li>2. The PHD under test must send a "roer" with reason = no-such-object-instance(1)</li> <li>3. The PHD under test remains in Waiting GetMDS substate.</li> <li>4. The simulated PHG responds with a roiv-cmip-get (handle = 0).</li> <li>5. The PHD responds with a rors-cmip-get (MDS Attributes)</li> </ol> |
+| <b>Pass/Fail criteria</b> | Process detailed above must be successfully completed.                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                           |                                                                                                                                                                                                                                                                                                                                          |                                                               |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHD/OPX/COM/BV-106                                                                                                                                                                                                                                                                                                                |                                                               |
+| <b>TP label</b>           | Agent State machine. Leaving the Configuring/Waiting SetTime Substate 1                                                                                                                                                                                                                                                                  |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                    | AgentStateMach 101; M                                         |
+| <b>Test purpose</b>       | Check that:<br>If Rlrq is received while in the Configuring/Waiting SetTime substate, a PHD shall transmit an Rlre (normal) and move to the Unassociated state                                                                                                                                                                           |                                                               |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_293 AND C_AG_OXP_004                                                                                                                                                                                                                                                                                           |                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                          |                                                               |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in Configuring state. PHD is in the Configuring/Waiting SetTime substate and Simulated PHG is in the Configuring/Sending SetTime substate.                                                                                                                                                      |                                                               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG sends an Association Release Request (Rlrq) message to the PHD under test with reason=0 (normal)</li> <li>2. The PHD under test shall respond with an Association Release Response (Rlre) message with reason=0 (normal), and shall go to the Unassociated state.</li> </ol> |                                                               |
+| <b>Pass/Fail criteria</b> | PHD under test transmits correctly the Rlre message                                                                                                                                                                                                                                                                                      |                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                          |                                                               |
+
+|                          |                                                                                                                                                                                         |                                                               |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/OPX/COM/BV-107                                                                                                                                                               |                                                               |
+| <b>TP label</b>          | Agent State machine. Leaving the Configuring/Waiting SetTime Substate 2                                                                                                                 |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                             | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                                                   | AgentStateMach 102; M                                         |
+| <b>Test purpose</b>      | Check that:<br>If Rlre is received while in the Configuring/Waiting SetTime substate, then PHD transmits an Abrt (reason undefined) and moves to the Unassociated state.                |                                                               |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_293 AND C_AG_OXP_004                                                                                                                                          |                                                               |
+| <b>Other PICS</b>        |                                                                                                                                                                                         |                                                               |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in Configuring state. The PHD is in the Configuring/Waiting SetTime substate and Simulated PHG is in the Configuring/Sending SetTime substate. |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                        |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | Configuring/Waiting SetTime substate and the simulated PHG is in the Configuring/Sending SetTime substate.                                                                                                                                                                             |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated PHG sends an Association Release Response to the PHD under test, with reason=0 (normal)</li> <li>The PHD under test responds with an Abort message (Abrt) with reason undefined.</li> </ol>                                       |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The PHD under test transmits correctly the Abort message (Abrt) with reason undefined and changes to the Unassociated state.</li> <li>The simulated PHG must not receive any message other than an Association Request after step 2.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                        |
+
+|                           |                                                                                                                                                                                                 |                                                               |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-108                                                                                                                                                                       |                                                               |
+| <b>TP label</b>           | Configuring/Waiting SetTime Substate. Abort message                                                                                                                                             |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                     | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                           | AgentStateMach 103; M                                         |
+| <b>Test purpose</b>       | Check that:<br>If an abort message abrt is received, then the PHD moves to Unassociated state                                                                                                   |                                                               |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_293 AND C_AG_OXP_004                                                                                                                                                  |                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                 |                                                               |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Configuring state. The PHD is in the Configuring/Waiting SetTime substate and the simulated PHG is in the Configuring/Sending SetTime substate. |                                                               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated PHG sends an Abort Message to the PHD under test</li> <li>Wait for an event report for PHD.</li> </ol>                                     |                                                               |
+| <b>Pass/Fail criteria</b> | The simulated PHG must not receive any message other than an Association Request.                                                                                                               |                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                 |                                                               |
+
+|                      |                                                                                                                                                                                                                                            |                                                               |
+|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>         | TP/PLT/PHD/OXP/COM/BV-109                                                                                                                                                                                                                  |                                                               |
+| <b>TP label</b>      | Agent State machine. Leaving the Configuring/Waiting SetTime Substate 3                                                                                                                                                                    |                                                               |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                      | AgentStateMach 104; M                                         |
+| <b>Test purpose</b>  | Check that:<br>If prst (Any APDU not covered in 10.* (corrupt, unknown, unexpected, etc)) is received while in Configuring/Waiting SetTime substate, then the PHD transmits an abrt (reason undefined) and moves to the Unassociated state |                                                               |
+| <b>Applicability</b> | C_AG_OXP_000 AND C_AG_OXP_293 AND C_AG_OXP_004                                                                                                                                                                                             |                                                               |
+| <b>Other PICS</b>    |                                                                                                                                                                                                                                            |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                   |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Configuring state. The PHD is in the Configuring/Waiting SetTime substate and the simulated PHG is in the Configuring/Sending SetTime substate.                                                                   |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated PHG issues a Prst message, rors-cmip- get.</li> <li>The PHD under test sends an abort message abrt(reason undefined) to the PHG and shall pass to the Unassociated state</li> </ol>                          |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The PHD under test sends the Abort message abrt(reason undefined) and changes to the Unassociated state</li> <li>The simulated PHG must not receive any message other than an Association Request after step 2.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                   |
+
+|                           |                                                                                                                                                                                                                                                            |                                                               |  |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-110                                                                                                                                                                                                                                  |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Connected Associated Configuring/Waiting SetTime 1                                                                                                                                                                                    |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                      | AgentStateMach 105; M                                         |  |
+| <b>Test purpose</b>       | Check that:<br><br>If roiv-cmip-confirmed-action (set time) is received while in Waiting SetTime substate, then PHD transmits a rors-cmip-confirmed-action (set time) and moves to Operating state.                                                        |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_293 AND C_AG_OXP_004                                                                                                                                                                                                             |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Configuring state. The PHD is in the Configuring/Waiting SetTime substate and the simulated PHG is in the Configuring/Sending SetTime substate.                                                            |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated PHG issues a roiv-cmip-confirmed-action (set time)</li> <li>The PHD under test must send a rors-cmip-confirmed-action (set time)</li> <li>The PHD under test moves to the Operating state.</li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | Process detailed above must be successfully completed                                                                                                                                                                                                      |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                            |                                                               |  |
+
+|                      |                                                                                                                                                                                                                         |                                                               |  |
+|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>         | TP/PLT/PHD/OXP/COM/BV-111                                                                                                                                                                                               |                                                               |  |
+| <b>TP label</b>      | Agent State machine. Connected Associated Configuring/Waiting SetTime 2                                                                                                                                                 |                                                               |  |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                             | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                      | <b>Testable items</b>                                                                                                                                                                                                   | AgentStateMach 106; M                                         |  |
+| <b>Test purpose</b>  | Check that:<br><br>If roiv-cmip-confirmed-action (but not set time) is received while in Waiting SetTime substate, then the PHD transmits a roer (no-such-object-instance) and remains in the Waiting SetTime substate. |                                                               |  |
+| <b>Applicability</b> | C_AG_OXP_000 AND C_AG_OXP_293 AND C_AG_OXP_004                                                                                                                                                                          |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Configuring state. The PHD is in the Configuring/Waiting SetTime substate and the simulated PHG is in the Configuring/Sending SetTime substate.                                                                                                                                                                                                                                                                |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG issues a roiv-cmip-confirmed-action (but not set time)</li> <li>2. The PHD under test must send a "roer" with reason = no-such-object-instance(1)</li> <li>3. The PHD under test remains in the Waiting SetTime substate.</li> <li>4. The simulated PHG issues a roiv-cmip-confirmed-action (set time)</li> <li>5. The PHD under test must send a rors-cmip-confirmed-action (set time)</li> </ol> |
+| <b>Pass/Fail criteria</b> | Process detailed above must be successfully completed                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |  |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-112                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Accepted known configuration Protocol Version 3                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | AgentStateMach 82; M                                          |  |
+| <b>Test purpose</b>       | Check that:<br>If aare(accepted) is received while in the Associating state, then PHD under test moves to the Operating state                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |  |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in Unassociated state                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Simulated PHG receives an association request from the PHD under test (PHD passes to Associating state).</li> <li>2. Simulated PHG responds with a result = accepted-unknown-config</li> <li>3. 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 simulated PHG. Configuration report is reported.</li> <li>4. Simulated PHG sends an abrt message.</li> <li>5. Simulated PHG and PHD moves to Unassociated state.</li> <li>6. Simulated PHG receives an association request from the PHD under test</li> <li>7. Simulated PHG responds with a result = accepted.</li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | The PHD under test has passed to Configuring/Waiting GetMDS substate after last step.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |  |
+
+|                 |                                                                        |                                                               |  |
+|-----------------|------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>    | TP/PLT/PHD/OXP/COM/BV-113                                              |                                                               |  |
+| <b>TP label</b> | Agent State machine. Connected Associated Configuring/Sending Config 1 |                                                               |  |
+| <b>Coverage</b> | <b>Spec</b>                                                            | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                      |  |  |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|--|--|
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | AgentStateMach 83; M |  |  |
+| <b>Test purpose</b>       | Check that:<br>If roiv-cmip-get (handle = 0) is received while in Sending Config substate, then PHD transmits a roer (no-such-object-instance) and remains in Sending Config substate.                                                                                                                                                                                                                                                                                                                                                                      |                      |  |  |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                      |  |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                      |  |  |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Configuring state. The PHD is in the Configuring/Sending Config substate and the simulated PHG is in the Configuring/ Waiting for Config substate.                                                                                                                                                                                                                                                                                                                                                          |                      |  |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated PHG issues a roiv-cmip-get (handle = 0)</li> <li>The PHD under test must send a "roer" with reason = no-such-object-instance(1)</li> <li>The PHD under test remains in Sending Config substate.</li> <li>The simulated PHG responds with a rors-cmip-confirmed-event-report with result "unsupported-config".</li> <li>The PHD responds with a roiv-cmip-confirmed-event report message with an MDC_NOTI_CONFIG event to send its configuration to the PHG or Rlrq (no-more-configurations)</li> </ol> |                      |  |  |
+| <b>Pass/Fail criteria</b> | Process detailed above must be successfully completed                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                      |  |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                      |  |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |  |  |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-114                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |  |
+| <b>TP label</b>           | Agent State machine. Connected Associated Configuring/Waiting Approval 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | AgentStateMach 84; M                                          |  |  |
+| <b>Test purpose</b>       | Check that:<br>If roiv-cmip-get (handle = 0) is received while in Waiting Approval substate, then PHD transmits a roer (no-such-object-instance) and remains in Waiting Approval substate.                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |  |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |  |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |  |  |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Configuring state. The PHD is in the Configuring/Waiting Approval substate and the simulated PHG is in the Configuring/Checking Config substate.                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated PHG issues a roiv-cmip-get (handle = 0)</li> <li>The PHD under test must send a "roer" with reason = no-such-object-instance(1)</li> <li>The PHD under test remains in Waiting Approval substate.</li> <li>The simulated PHG responds with a rors-cmip-confirmed-event-report with result "unsupported-config".</li> <li>The PHD responds with a roiv-cmip-confirmed-event report message with an MDC_NOTI_CONFIG event to send its configuration to the PHG or Rlrq (no-more-configurations)</li> </ol> |                                                               |  |  |
+| <b>Pass/Fail criteria</b> | Process detailed above must be successfully completed                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |  |
+
+|              |  |
+|--------------|--|
+| <b>Notes</b> |  |
+|--------------|--|
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/OXP/COM/BV-115                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>TP label</b>           | Agent State machine. Connected Associated Configuring/Waiting Approval 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | AgentStateMach 85; M                                          |  |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>If roiv-cmip-confirmed-action (set time) is received while in Waiting Approval substate, then PHD transmits a roer (no-such-object-instance) and remains in Waiting Approval substate.</p>                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+| <b>Initial condition</b>  | The simulated PHG and PHD under test are in the Configuring state. The PHD is in the Configuring/Waiting Approval substate and the simulated PHG is in the Configuring/Checking Config substate.                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated PHG issues a roiv-cmip-confirmed-action (set time)</li> <li>The PHD under test must send a "roer" with reason = no-such-object-instance(1)</li> <li>The PHD under test remains in Waiting Approval substate.</li> <li>The simulated PHG responds with a rors-cmip-confirmed-event-report with result "unsupported-config".</li> <li>The PHD responds with a roiv-cmip-confirmed-event report message with an MDC_NOTI_CONFIG event to send its configuration to the PHG or Rlrq (no-more-configurations)</li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | Process detailed above must be successfully completed                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+
+|                          |                                                                                                                                                                                                                                  |                                                               |  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/OXP/COM/BV-116                                                                                                                                                                                                        |                                                               |  |
+| <b>TP label</b>          | Agent State machine. Connected Associated Configuring/Waiting Approval 3                                                                                                                                                         |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                      | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                            | AgentStateMach 86; M                                          |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If roiv-cmip-confirmed-action (but not set time) is received while in Waiting Approval substate, then the PHD transmits a roer (no-such-object-instance) and remains in the Waiting Approval substate.</p> |                                                               |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_293                                                                                                                                                                                                    |                                                               |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                  |                                                               |  |
+| <b>Initial condition</b> | The simulated PHG and PHD under test are in the Configuring state. The PHD is in the Configuring/Waiting Approval substate and the simulated PHG is in the Configuring/Checking Config substate.                                 |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHG issues a roiv-cmip-confirmed-action (but not set time)</li> </ol>                                                                                                       |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ol style="list-style-type: none"> <li>2. The PHD under test must send a "roer" with reason = no-such-object-instance(1)</li> <li>3. The PHD under test remains in the Waiting Approval substate.</li> <li>4. The simulated PHG responds with a rors-cmip-confirmed-event-report with result "unsupported-config".</li> <li>5. The PHD responds with a roiv-cmip-confirmed-event report message with an MDC_NOTI_CONFIG event to send its configuration to the PHG or Rlrq (no-more-configurations)</li> </ol> |
+| <b>Pass/Fail criteria</b> | Process detailed above must be successfully completed                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+## 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-CDG 2017] Personal Connected Health Alliance, Continua Design Guidelines (2017), "Keratin", *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*.  
+[www.etsi.org/deliver/etsi\\_i\\_ets/300400\\_300499/300406/01\\_60/ets\\_300406e01p.pdf](http://www.etsi.org/deliver/etsi_i_ets/300400_300499/300406/01_60/ets_300406e01p.pdf)
+- [b-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003-12), *ETSI drafting rules*.  
+<https://docbox.etsi.org/MTS/MTS/10-PromotionalMaterial/MBS-20111118/Referenced%20Documents/Drafting%20Rules.pdf>
+- [b-PHD PICS & PIXIT] PHD PICS and PIXIT Test Tool v8.0.0.0 – Excel sheet v1.13.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-PHG PICS & PIXIT] PHG PICS and PIXIT Test Tool v8.0.0.0 – Excel sheet v1.11.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-TI] PHD Testable items. Test Tool v8.0.0.0 – Excel sheet v1.10.  
+<http://handle.itu.int/11.1002/2000/12067>
+
+
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.842-201911-I_PDF-E/raw.md b/marked/H/T-REC-H.842-201911-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..135df36c39b1045bea1b3d77fe3e8cce1a95f887
--- /dev/null
+++ b/marked/H/T-REC-H.842-201911-I_PDF-E/raw.md
@@ -0,0 +1,2913 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.842**
+
+(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 2: Optimized Exchange Protocol: Personal  
+Health Gateway**
+
+Recommendation ITU-T H.842
+
+# 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        |
+| <b>Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN)</b> | <b>H.820–H.859</b> |
+| 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.842
+
+## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 2: Optimized Exchange Protocol: Personal Health Gateway
+
+## Summary
+
+Recommendation ITU-T H.842 provides a test suite structure (TSS) and the test purposes (TPs) for personal health gateways (PHGs) using the IEEE 11073-20601 optimized exchange protocol 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.842 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 2: Optimized Exchange Protocol: Personal Health Gateway (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.842    | 2015-01-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/12259">11.1002/1000/12259</a> |
+| 2.0     | ITU-T H.842    | 2016-07-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12935">11.1002/1000/12935</a> |
+| 3.0     | ITU-T H.842    | 2017-04-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/13216">11.1002/1000/13216</a> |
+| 4.0     | ITU-T H.842    | 2018-08-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/13679">11.1002/1000/13679</a> |
+| 5.0     | ITU-T H.842    | 2019-11-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/14116">11.1002/1000/14116</a> |
+
+## Keywords
+
+Conformance testing, Continua Design Guidelines, e-health, IEEE 11073-20601 optimized exchange protocol, 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 <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.2.1: General (GEN).....                       | 11   |
+| A.3 Subgroup 2.2.2: PHD domain information model (DIM) ..... | 11   |
+| A.4 Subgroup 2.2.3: PHD service model (SER) .....            | 75   |
+| A.5 Subgroup 2.2.4: PHD communication model (COM).....       | 84   |
+| Bibliography.....                                            | 125  |
+
+**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 2: Optimized Exchange Protocol: Personal Health Gateway (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_PAN-LAN_PART_2_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_2_v1.2.doc" as a baseline and adds new features included in [b-CDG 2012]: <ul style="list-style-type: none"> <li>• Adds glucose meter new spec version</li> <li>• Adds body composition analyser device specialization</li> <li>• Adds basic electrocardiograph device specialization</li> </ul> |
+| 1.4     | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_PAN-LAN_PART_2_v1.3.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]: <ul style="list-style-type: none"> <li>• Adds glucose meter BLE</li> <li>• Adds BLE SSP support</li> <li>• Adds NFC new transport</li> <li>• Adds INR Device Specialization</li> </ul>          |
+| 1.5     | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_PLT_PART_2_v1.4.doc" as a baseline and adds new features included in Documentation Enhancements: <ul style="list-style-type: none"> <li>• "Other PICS" row has been added</li> </ul>                                                                                               |
+| 1.6     | 2015-07-01 | Initial Release for Test Tool DG2015. It uses "TSS&TP_DG2013_PHT_PART_2_v1.5.doc" as a baseline and adds new features included in [ITU-T H.810 (2015)]/[b-CDG 2015]                                                                                                                                                                                                          |
+| 1.7     | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2015_PHT_PART_2_v1.6.doc" as a baseline and adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016]                                                                                                                                                                                                          |
+| 1.8     | 2017-03-14 | Updates the baseline in "TSS&TP_DG2016_PHD_PART_2_v1.7.doc" as part of the Maintenance 2016 activity: <ul style="list-style-type: none"> <li>• Update the applicability row for TP/PLT/PHG/OPX/DIM/BV-046</li> </ul>                                                                                                                                                         |
+| 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]<br>Updates related to the changes included in the glucose meter device specialization [ISO/IEEE 11073-10417]                                                                                                                            |
+| 1.10    | 2018-10-17 | Updates related to the inclusion of the power status monitor of Personal Health Devices device specialization [ISO/IEEE 11073-10427] test cases.                                                                                                                                                                                                                             |
+| 1.11    | 2019-06-13 | Second maintenance release for Test Tool DG2017. It uses ITU-T H.842 (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 2: Optimized Exchange Protocol: Personal Health Gateway
+
+## 1 Scope
+
+The scope of this Recommendation<sup>1</sup> is to provide a test suite structure (TSS) and the test purposes (TP) for the Personal Health Devices (PHD) 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 2.
+
+- 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
+
+---
+
+<sup>1</sup> 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 Annex A.
+
+- 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-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.  
+<https://www.iso.org/standard/54331.html> with  
+<https://www.iso.org/standard/63972.html>
+- [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.  
+<https://www.iso.org/standard/66717.html> with  
+<https://www.iso.org/standard/71886.html>
+- [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*.  
+<https://www.iso.org/standard/54572.html>
+- [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)*.  
+<https://www.iso.org/standard/61876.html>
+- [ISO/IEEE 11073-10407] ISO/IEEE 11073-10407:2010, *Health informatics – Personal health device communication – Part 10407: Device specialization – Blood pressure monitor*.  
+<https://www.iso.org/standard/54573.html>
+- [ISO/IEEE 11073-10408] ISO/IEEE 11073-10408:2010, *Health informatics – Personal health device communication – Part 10408: Device specialization – Thermometer*.  
+<https://www.iso.org/standard/54310.html>
+
+- [ISO/IEEE 11073-10415] ISO/IEEE 11073-10415:2010, *Health informatics – Personal health device communication – Part 10415: Device specialization – Weighing scale.*  
+<https://www.iso.org/standard/54310.html>
+- [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/70739.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, (Revision of IEEE Std 11073-10441-2008).*  
+<https://www.iso.org/standard/64868.html>
+
+|                        |                                                                                                                                                                                                                                                                                                                    |
+|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [ISO/IEEE 11073-10442] | ISO/IEEE 11073-10442:2015, <i>Health informatics – Personal health device communication – Part 10442: Device specialization – Strength fitness equipment.</i><br><a href="http://standards.ieee.org/findstds/standard/11073-10442-2008.html">http://standards.ieee.org/findstds/standard/11073-10442-2008.html</a> |
+| [ISO/IEEE 11073-10471] | ISO/IEEE 11073-10471:2010, <i>Health informatics – Personal health device communication – Part 10471: Device specialization – Independent living activity hub.</i><br><a href="https://www.iso.org/standard/54328.html">https://www.iso.org/standard/54328.html</a>                                                |
+| [ISO/IEEE 11073-10472] | ISO/IEEE 11073-10472-2012, <i>Health informatics – Personal health device communication – Part 10472: Device specialization – Medication monitor.</i><br><a href="https://www.iso.org/standard/54364.html">https://www.iso.org/standard/54364.html</a>                                                             |
+
+## 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                                  |
+| MDS  | Medical Device System                         |
+| NFC  | Near Field Communication                      |
+| PAN  | Personal Area Network                         |
+| 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
+
+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 2.2.1, 2.2.2, 2.2.3 and 2.2.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)
+    - 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 <http://handle.itu.int/11.1002/2000/12067>. 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>/<DUT>/<GR>/<SGR>/<XX> – <NNN>). It is specified according to the naming convention defined below:
+  - Each test purpose identifier is introduced by the prefix "TP".
+  - <TT>: 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)
+  - <DUT>: This is the device under test:
+    - PHD: Personal Health Device
+    - PHG: Personal Health Gateway
+  - <GR>: This identifies a group of test cases.
+  - <SGR>: This identifies a subgroup of test cases.
+  - <XX>: This identifies the type of testing:
+    - BV: Valid behaviour test
+    - BI: Invalid behaviour test
+  - <NNN>: 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 (DUT) 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: General (GEN)
+
+There are no test cases defined in this subgroup.
+
+## A.3 Subgroup 2.2.2: PHD domain information model (DIM)
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHG/OPX/DIM/BV-000_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>TP label</b>          | Episodic Scanner object not supported                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Episodic Scanner object, declared by the vendor as "not supported", is really not supported by the Personal Health Gateway (PHG) under test.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_001)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Initial condition</b> | The simulated Personal Health Device (PHD) and the PHG under test are in the unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG.</li> <li>2. IF the PHG under test responds with an Association Response (rejected-*) or an Abort, THEN the PHG shall not move to the Operating state and the test procedure ends.</li> <li>3. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN the simulated PHD sends a configuration event report with the config-report-id set to an extended Config-Id, including an episodic scanner object. <ol style="list-style-type: none"> <li>a. IF the PHG under test responds with rors-cmip-confirmed-event-report (unsupported-config) or Release Request or Abort THEN: <ul style="list-style-type: none"> <li><input type="checkbox"/> IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li><input type="checkbox"/> IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ul> </li> <li>b. IF the PHG under test responds with rors-cmip-confirmed-event-report (accepted-config) THEN: <ul style="list-style-type: none"> <li><input type="checkbox"/> IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state and PHG is forced to enable the scanner object.</li> <li><input type="checkbox"/> IF C_MAN_OXP_085 THEN: <ol style="list-style-type: none"> <li>i. 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.</li> <li>ii. 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.</li> <li>iii. Once in Operating state PHG is forced to enable the scanner object.</li> </ol> </li> </ul> </li> </ol> </li> <li>4. IF the PHG under test responds with an Association Response (accepted) THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state, PHG is forced to enable the scanner object.</li> <li>b. IF C_MAN_OXP_085 THEN: <ul style="list-style-type: none"> <li><input type="checkbox"/> 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.</li> </ul> </li> </ol> </li> </ol> |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> 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.</li> <li><input type="checkbox"/> Once in operating PHG is forced to enable the scanner object.</li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2 or step 3.a, the PHG does not move to the operating or Configuring/Setting GetMDS state.</li> <li>• In step 3.b or step 4, the PHG does not send the Set action to enable the scanner object.</li> </ul>                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHG/EXP/DIM/BV-000_B                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |
+| <b>TP label</b>          | Periodic Scanner object not supported                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>Test purpose</b>      | Check that:<br>Periodic Scanner object, declared by the vendor as "not supported", is really not supported by the PHG under test.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_006)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG.</li> <li>2. IF the PHG under test responds with an Association Response (rejected-*) or an Abort, THEN the PHG shall not move to Operating state and the test procedure ends.</li> <li>3. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN the simulated PHD sends a configuration event report with the config-report-id set to an extended Config-Id, including a periodic scanner object. <ol style="list-style-type: none"> <li>a. IF the PHG under test responds with a rors-cmip-confirmed-event-report (unsupported-config) or a Release Request or an Abort THEN: <ul style="list-style-type: none"> <li><input type="checkbox"/> IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li><input type="checkbox"/> IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ul> </li> <li>b. IF the PHG under test responds with a rors-cmip-confirmed-event-report (accepted-config) THEN: <ul style="list-style-type: none"> <li><input type="checkbox"/> IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state and PHG is forced to enable the scanner object.</li> <li><input type="checkbox"/> IF C_MAN_OXP_085 THEN: <ol style="list-style-type: none"> <li>i. 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.</li> <li>ii. 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.</li> <li>iii. Once in Operating state PHG is forced to enable the scanner object.</li> </ol> </li> </ul> </li> </ol> </li> <li>4. IF the PHG under test responds with an Association Response (accepted) THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state, PHG is forced to enable the scanner object.</li> <li>b. IF C_MAN_OXP_085 THEN:</li> </ol> </li> </ol> |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li data-bbox="555 163 1426 255"><input type="checkbox"/> 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.</li> <li data-bbox="555 266 1426 356"><input type="checkbox"/> 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.</li> <li data-bbox="555 367 1326 389"><input type="checkbox"/> Once in Operating state PHG is forced to enable the scanner object.</li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li data-bbox="458 412 1401 470">• In step 2 or step 3.a, the PHG does not move to the operating or Configuring/Setting GetMDS state</li> <li data-bbox="458 481 1375 539">• In step 3.b or step 4, the PHG does not send the Set action to enable the scanner object</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/DIM/BV-000_C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+| <b>TP label</b>          | PM-Store object not supported                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>Test purpose</b>      | Check that:<br>PM-Store object, declared by the vendor as "not supported", is really not supported by the PHG under test.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_003)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |  |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li data-bbox="458 1104 1219 1131">1. The simulated PHD sends an Association Request to the PHG.</li> <li data-bbox="458 1144 1422 1202">2. IF the PHG under test responds with an Association Response (rejected-*) or an Abort, THEN the PHG shall not move to Operating state and the test procedure ends.</li> <li data-bbox="458 1216 1426 1301">3. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN the simulated PHD sends a configuration event report with the config-report-id set to an extended Config-Id, including a PM-Store object. <ol style="list-style-type: none"> <li data-bbox="504 1314 1394 1373">a. IF the PHG under test responds with a rors-cmip-confirmed-event-report (unsupported-config) or a Release Request or an Abort THEN: <ul style="list-style-type: none"> <li data-bbox="555 1386 1426 1444"><input type="checkbox"/> IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li data-bbox="555 1456 1426 1514"><input type="checkbox"/> IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ul> </li> <li data-bbox="504 1527 1394 1585">b. IF the PHG under test responds with a rors-cmip-confirmed-event-report (accepted-config) THEN: <ul style="list-style-type: none"> <li data-bbox="555 1599 1426 1657"><input type="checkbox"/> IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state and PHG is forced to enable the scanner object.</li> <li data-bbox="0 0 1 2"><input type="checkbox"/> IF C_MAN_OXP_085 THEN: <ol style="list-style-type: none"> <li data-bbox="663 1697 1426 1789">i. 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.</li> <li data-bbox="663 1803 1426 1895">ii. 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.</li> <li data-bbox="663 1908 1426 1966">iii. Once in Operating state PHG is forced to trigger (Trig-Segment-Data-Xfer) the PM-Store.</li> </ol> </li> </ul> </li> </ol> </li> <li data-bbox="458 1980 1347 2007">4. IF the PHG under test responds with an Association Response (accepted) THEN: <ol style="list-style-type: none"> <li data-bbox="504 2020 1426 2078">a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state, PHG is forced to trigger (Trig-Segment-Data-Xfer) the PM-Store.</li> </ol> </li> </ol> |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>b. IF C_MAN_OXP_085 THEN:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> 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.</li> <li><input type="checkbox"/> 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.</li> <li><input type="checkbox"/> Once in Operating state PHG is forced to trigger (Trig-Segment-Data-Xfer) the PM-Store.</li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2 or step 3.a, the PHG does not move to the operating or Configuring/Sending GetMDS state</li> <li>• In step 3.b or step 4, the PHG does not send the Trig-Segment-Data-Xfer action</li> <li>• Once in the Operating state, the PHG does send actions for the PM-Store (Get-Segment-Info, Clear-Segment or GET for PM-Store object)</li> </ul>                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |              |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/DIM/BV-001                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |              |
+| <b>TP label</b>          | PHG configuring a real-time clock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |              |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | MDSMethod 3;M                                                 | AbsTime 6; C |
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [b-ITU-T H.810 (2015)]                                        |              |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Communication 14;M                                            |              |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The PHG when invoking the Set-Time method shall do so using a roiv-cmip-confirmed-action request.</p> <p>[AND]</p> <p>If the PHD has the mds-time-mgr-set-time bit set, the PHG shall invoke the Set-Time action command to set the absolute time on the PHD</p> <p>[AND]</p> <p>The Set-Time shall be sent within a TO<sub>config</sub> time period after receiving the attribute from an MDS Get message</p>                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |              |
+| <b>Applicability</b>     | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |              |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |              |
+| <b>Initial condition</b> | <p>The simulated PHD and the PHG under test are in the Unassociated state. The PHD has the MDSTimeInfo attribute with the mds-time-mgr-set-time and mds-time-capab-set-clock bits set.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test.</li> <li>2. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN: <ol style="list-style-type: none"> <li>a. IF the PHG under test sends a GET request while it is in the Configuring state, within TO<sub>config</sub> seconds the PHG shall set the time of the simulated PHD, ELSE wait until the Operating state is reached.</li> <li>b. If the PHG under test did not send a GET request, then force the PHG under test to request MDS attributes.</li> <li>c. The simulated PHD sends a rors-cmip-get with MDS attributes (with the mds-time-mgr-set-time bit set).</li> </ol> </li> <li>3. IF C_MAN_OXP_085 THEN: <ol style="list-style-type: none"> <li>a. PHG under test sends a GET request while it is in Configuring/Sending GetMDS substate.</li> </ol> </li> </ol> |                                                               |              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>b. The simulated PHD sends rors-cmip-get with MDS attributes (with the mds-time-mgr-set-time bit set).</p> <p>4. After receiving MDS attributes within TO<sub>config</sub> seconds, the PHG under test shall set the time of the simulated PHD:</p> <p>a. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Remote Operation Invoke   Confirmed Action</li> <li><input type="checkbox"/> Handle = 0 (MDS object)</li> <li><input type="checkbox"/> Action = 0x0C 0x17 (MDC_ACT_SET_TIME)</li> <li><input type="checkbox"/> SetTimeInvoke = SEQUENCE: <ul style="list-style-type: none"> <li>▪ date-time.length = 8 bytes</li> <li>▪ date-time.value = &lt;Record for comparison&gt;</li> <li>▪ Accuracy = 0</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The format of the received message must be the one specified</li> <li>• Verify that the time is set to the time of the PHG under test</li> <li>• Verify that Set-Time is sent within the TO<sub>config</sub> time period after receiving the rors-cmip-get with MDS attributes, in the Configuring state (step 2a or 3b) or the Operating state (step 2c)</li> </ul>                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |               |  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------|--|
+| <b>TP Id</b>             | TP/PLT/PHG/EXP/DIM/BV-001_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |               |  |
+| <b>TP label</b>          | PHG configuring a Base-Offset-Time clock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |               |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | MDSMethod 5;M                                                 | AbsTime 18; M |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The PHG when invoking the Set-Base-Offset-Time method shall do so using a roiv-cmip-confirmed-action request.</p> <p>[AND]</p> <p>The Set-Base-Offset-Time shall be sent within a TO<sub>config</sub> time period after receiving the attribute from an MDS Get message</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |               |  |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND (C_MAN_OXP_029 OR C_MAN_OXP_030)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |               |  |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |               |  |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state. The PHD has the MDSTimeInfo attribute with the mds-time-capab-set-clock(1), mds-time-capab-bo-time(7) and mds-time-mgr-set-time(11) bits set.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test.</li> <li>2. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN: <ol style="list-style-type: none"> <li>a. If the PHG under test sends a GET request while it is in the Configuring state, within TO<sub>config</sub> seconds the PHG shall set the time of the simulated PHD, ELSE wait until the Operating state is reached.</li> <li>b. If the PHG under test did not send a GET request, then force the PHG under test to request MDS attributes.</li> <li>c. The simulated PHD sends a rors-cmip-get with MDS attributes (the bits mds-time-capab-bo-time(7) and mds-time-mgr-set-time(11) are set).</li> </ol> </li> <li>3. IF C_MAN_OXP_085 THEN: <ol style="list-style-type: none"> <li>a. PHG under test sends a GET request while it is in Configuring/Sending GetMDS substate.</li> <li>b. The simulated PHD sends rors-cmip-get with MDS attributes (the bits mds-time-capab-bo-time(7) and mds-time-mgr-set-time(11) are set).</li> </ol> </li> </ol> |                                                               |               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>4. After receiving MDS attributes within TOconfig seconds, the PHG under test shall set the time of the simulated PHD:</p> <p>a. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Remote Operation Invoke   Confirmed Action</li> <li><input type="checkbox"/> Handle = 0 (MDS object)</li> <li><input type="checkbox"/> Action = 0x0C 0x1D (MDC_ACT_SET_BO_TIME)</li> <li><input type="checkbox"/> SetBOTimeInvoke = SEQUENCE: <ul style="list-style-type: none"> <li>▪ date-time.length = 8 bytes</li> <li>▪ date-time.value = &lt;Record for comparison&gt;</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The format of the received message must be the one specified</li> <li>• Verify that the time is set to the time of the PHG under test</li> <li>• Verify that a Set-Base-Offset-Time is sent within the TOconfig time period after receiving the rors-cmip-get with MDS attributes, in the Configuring state (step 2a or 3b) or the Operating state (step 4)</li> </ul>                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                                        |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|----------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OPX/DIM/BV-002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                                        |
+| <b>TP label</b>          | MDS services. PHG requesting MDS object attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                                        |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                                        |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | MDSService 3;O                                                | MDSService 5; R      ConfEventRep 5; O |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The PHG may request the MDS object attributes of the PHD in which case the PHG shall send the "Remote Operation Invoke   Get" command (see roiv-cmip-get in B.10.2) with the reserved handle value of 0</p> <p>[AND]</p> <p>Due to the nature of the attributes reported in the MDS Object, the PHG should send the Get MDS Object request right after sending the Association Response.[AND]</p> <p>Even if PHG knows the PHD's device configuration, the PHG may ask to enter the Configuring state in order to check attributes from the MDS object before deciding to accept the association.</p>                                                                                                                                                                                                                                                                                                                             |                                                               |                                        |
+| <b>Applicability</b>     | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                                        |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                                        |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                                        |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with an extended dev-config-id previously unknown to the PHG.</li> <li>2. The PHG under test sends an AARE with an "accepted-unknown-config".</li> <li>3. Check that the PHG under test has sent the GET request while it is in the Configuring state.</li> <li>4. The simulated PHD sends a configuration event report.</li> <li>5. The PHG responds to the configuration event report.</li> <li>6. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG under test reaches the Operating state.</li> <li>7. IF C_MAN_OXP_085 THEN: <ol style="list-style-type: none"> <li>a. PHG under test sends a GET request while it is in Configuring/Sending GetMDS substate.</li> <li>b. The simulated PHD sends rors-cmip-get with MDS attributes (the bits mds-time-capab-bo-time(7) and mds-time-mgr-set-time(11) are set).</li> </ol> </li> </ol> |                                                               |                                        |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>8. If the PHG under test did not automatically send a GET request for the MDS object or if it has not sent the GET request while in the Configuring state, force the PHG under test to send a GET to the MDS.</p> <p>9. Whether the above Get request was sent via automatic behavior or was forced, the received message from the PHD shall be:</p> <ul style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ul> </li> <li>b. invoke-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value= &lt;Not relevant for this Test&gt;</li> </ul> </li> <li>c. CHOICE <ul style="list-style-type: none"> <li><input type="checkbox"/> field-value = 0x01 0x03 (Remote Operation Invoke   Get)</li> </ul> </li> <li>d. obj-handle <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0</li> </ul> </li> <li>e. attribute-id-list <ul style="list-style-type: none"> <li><input type="checkbox"/> count = 0x00 0x00</li> <li><input type="checkbox"/> length = 0x00 0x00</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The format of the received message shall be the one specified</li> <li>• It is recommended that the GET MDS is received while PHG under test is in the Configuring state.</li> </ul> <p>NOTE: If the GET request for the MDS object is received from the PHG under test while in the Configuring state, it is checked in accordance step 9 above.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                    |
+|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------|
+| <b>TP Id</b>         | TP/PLT/PHG/OPX/DIM/BV-004_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                    |
+| <b>TP label</b>      | PM-Store object methods. Clear-Segments method 1 (all-segment).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                    |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                    |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | PM-StoreMeth 9; O                                             | PM-StoreMeth 18; O |
+| <b>Test purpose</b>  | <p>Check that:</p> <p>Support for the Clear-Segments method is optional.</p> <p>[AND]</p> <p>If a PHG invokes the Clear-Segments method, it shall use operation type roiv-cmip-confirmed-action.</p> <p>If a PHG invokes the Clear-Segments method, it shall use the Action-type MDC_ACT_SEG_CLR</p> <p>If a PHG invokes the Clear-Segments method, it shall use the action-info-args SegmSelection structure (all-segments)</p> <p>[AND]</p> <p>The PHG shall support at least the all segments choice in the SegmSelection action-info-args of the Clear-Segments method</p> |                                                               |                    |
+| <b>Applicability</b> | C_MAN_OXP_000 AND C_MAN_OXP_003 AND (C_MAN_OXP_040 OR C_MAN_OXP_041 OR C_MAN_OXP_042)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                    |
+| <b>Other PICS</b>    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state. The simulated PHD has at least one segment with data stored and PMStoreCapab bits 4 and 10 set.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Test procedure</b>     | <p>IF a UI feature exists such that the PHG can clear the segments:</p> <ol style="list-style-type: none"> <li>Make the PHG under test perform a Clear Segment with parameter all-segments.</li> </ol> <p>IF the PHG under test can clear the segments automatically after a transfer, then perform the action to clear the segments.</p> <p>Either way:</p> <ol style="list-style-type: none"> <li>The simulated PHD receives the message: <ol style="list-style-type: none"> <li>APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ul> </li> <li>invoke-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value= This value identifies the message; the confirmed response that will be sent by the simulated PHD shall have the same invoke-id.</li> </ul> </li> <li>CHOICE <ul style="list-style-type: none"> <li><input type="checkbox"/> value = 0x01 0x07 (roiv-cmip-confirmed-action)</li> </ul> </li> <li>obj-handle <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = &lt;Handle of an existing PM-Store&gt;</li> </ul> </li> <li>action-type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0C 0x0C (MDC_ACT_SEG_CLR)</li> </ul> </li> <li>action-info-args <ul style="list-style-type: none"> <li><input type="checkbox"/> SegmSelection = <ul style="list-style-type: none"> <li>▪ all-segments (0)</li> </ul> </li> </ul> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message must be the one specified above.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                    |
+|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------|
+| <b>TP Id</b>        | TP/PLT/PHG/OXP/DIM/BV-004_B                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                    |
+| <b>TP label</b>     | PM-Store Class methods. Clear-Segments method 2 (Time Range).                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                    |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                      | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                    |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                            | PM-StoreMeth 9; O                                             | PM-StoreMeth 18; O |
+| <b>Test purpose</b> | <p>Check that:</p> <p>Support for the Clear-Segments method is optional.</p> <p>[AND]</p> <p>If a PHG invokes the Clear-Segments method, it shall use operation type roiv-cmip-confirmed-action.</p> <p>If a PHG invokes the Clear-Segments method, it shall use the Action-type MDC_ACT_SEG_CLR</p> <p>If a PHG invokes the Clear-Segments method, it shall use the action-info-args SegmSelection structure (AbsTimeRange)</p> |                                                               |                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_003 AND C_MAN_OXP_041                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state. The simulated PHD has at least one segment with data stored and PMStoreCapab bits 4, 8 and 10 set.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Test procedure</b>     | <p>IF a UI feature exists such that the PHG can clear the segments:</p> <ol style="list-style-type: none"> <li>1. Make the PHG under test perform a Segment Clear with parameter SegmSelection = AbsTimeRange</li> </ol> <p>IF the PHG under test can clear the segments automatically after a transfer, perform the action.</p> <p>Either way:</p> <ol style="list-style-type: none"> <li>2. Make the PHG under test perform a Segment Clear by time range.</li> <li>3. The simulated PHD receives the message: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ul> </li> <li>b. invoke-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = This value identifies the message; the confirmed response that will be sent by the simulated PHD shall have the same invoke-id.</li> </ul> </li> <li>c. CHOICE <ul style="list-style-type: none"> <li><input type="checkbox"/> value = 0x01 0x07 (roiv-cmip-confirmed-action)</li> </ul> </li> <li>d. obj-handle <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = &lt;Handle of an existing PM-Store&gt;</li> </ul> </li> <li>e. action-type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0C 0x0C (MDC_ACT_SEG_CLR)</li> </ul> </li> <li>f. action-info-args <ul style="list-style-type: none"> <li><input type="checkbox"/> SegmSelection = AbsTimeRange <ul style="list-style-type: none"> <li>▪ from-time = AbsTime</li> <li>▪ to-time = AbsTime</li> </ul> </li> </ul> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message must be the one specified above.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                     |                                                                            |                                                               |                    |
+|---------------------|----------------------------------------------------------------------------|---------------------------------------------------------------|--------------------|
+| <b>TP Id</b>        | TP/PLT/PHG/OXP/DIM/BV-004_C                                                |                                                               |                    |
+| <b>TP label</b>     | PM-Store Class methods. Clear-Segments method 3 (segm-id-list)             |                                                               |                    |
+| <b>Coverage</b>     | <b>Spec</b>                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                    |
+|                     | <b>Testable items</b>                                                      | PM-StoreMeth 9; O                                             | PM-StoreMeth 18; O |
+| <b>Test purpose</b> | Check that:<br>Support for the Clear-Segments method is optional.<br>[AND] |                                                               |                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>If a PHG invokes the Clear-Segments method, it shall use operation type roiv-cmip-confirmed-action.</p> <p>If a PHG invokes the Clear-Segments method, it shall use the Action-type MDC_ACT_SEG_CLR</p> <p>If a PHG invokes the Clear-Segments method, it shall use the action-info-args SegmSelection structure (segm-id-list)</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_003 AND C_MAN_OXP_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state. The simulated PHD has at least one segment with data stored and PMStoreCapab bits 4, 7 and 10 set.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Test procedure</b>     | <p>IF a UI feature exists such that the PHG can clear the segments:</p> <ol style="list-style-type: none"> <li>1. Make the PHG under test perform a Segment Clear with parameter SegmSelection = segm-id-list.</li> </ol> <p>IF the PHG under test can clear the segments automatically after a transfer, perform the action.</p> <p>Either way:</p> <ol style="list-style-type: none"> <li>2. Make the PHG under test perform a Segment Clear of a specific Segment.</li> <li>3. The simulated PHD receives the message: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ul> </li> <li>b. invoke-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = This value identifies the message; the confirmed response that will be sent by the simulated PHD shall have the same invoke-id.</li> </ul> </li> <li>c. CHOICE <ul style="list-style-type: none"> <li><input type="checkbox"/> value = 0x01 0x07 (roiv-cmip-confirmed-action)</li> </ul> </li> <li>d. obj-handle <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = &lt;Handle of an existing PM-Store&gt;</li> </ul> </li> <li>e. action-type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0C 0x0C (MDC_ACT_SEG_CLR)</li> </ul> </li> <li>f. action-info-args <ul style="list-style-type: none"> <li><input type="checkbox"/> SegmSelection = segm-id-list (must contain the instance number of the selected Segment)</li> </ul> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message must be the one specified above.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+|                 |                                                                          |                                                               |
+|-----------------|--------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHG/OXP/DIM/BV-004_D                                              |                                                               |
+| <b>TP label</b> | PM-Store Class methods. Clear-Segments method 4 (Base-Offset-Time Range) |                                                               |
+| <b>Coverage</b> | <b>Spec</b>                                                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                 | <b>Testable items</b>                                                    | PM-StoreMeth 9; O      PM-StoreMeth 18; O                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>       | <p>Check that:</p> <p>Support for the Clear-Segments method is optional.</p> <p>[AND]</p> <p>If a PHG invokes the Clear-Segments method, it shall use operation type roiv-cmip-confirmed-action.</p> <p>If a PHG invokes the Clear-Segments method, it shall use the Action-type MDC_ACT_SEG_CLR</p> <p>If a PHG invokes the Clear-Segments method, it shall use the action-info-args SegmSelection structure (BOTimeRange)</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_003 AND C_MAN_OXP_080 AND (C_MAN_OXP_029 OR C_MAN_OXP_030)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state. The simulated PHD has at least one segment with data stored and PMStoreCapab bits 4, 8 and 10 set.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Test procedure</b>     | <p>IF a UI feature exists such that the PHG can clear the segments:</p> <ol style="list-style-type: none"> <li>1. Make the PHG under test perform a Segment Clear with parameter SegmSelection = BOTimeRange.</li> </ol> <p>IF the PHG under test can clear the segments automatically after a transfer, perform the action.</p> <p>Either way:</p> <ol style="list-style-type: none"> <li>2. Make the PHG under test perform a Segment Clear by time range.</li> <li>3. The simulated PHD receives the message: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ol> </li> <li>b. invoke-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = This value identifies the message; the confirmed response that will be sent by the simulated PHD shall have the same invoke-id.</li> </ol> </li> <li>c. CHOICE <ol style="list-style-type: none"> <li><input type="checkbox"/> value = 0x01 0x07 (roiv-cmip-confirmed-action)</li> </ol> </li> <li>d. obj-handle <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = &lt;Handle of an existing PM-Store&gt;</li> </ol> </li> <li>e. action-type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0C 0x0C (MDC_ACT_SEG_CLR)</li> </ol> </li> <li>f. action-info-args <ol style="list-style-type: none"> <li><input type="checkbox"/> SegmSelection = BOTimeRange <ol style="list-style-type: none"> <li>▪ from-time = BaseOffsetTime</li> <li>▪ to-time = BaseOffsetTime</li> </ol> </li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message must be the one specified above.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                    |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/DIM/BV-005_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                    |
+| <b>TP label</b>           | PM-Store Class methods. Get-Segment-info method (all-Segments)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                    |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                    |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | PM-StoreMeth 12; O                                            | PM-StoreMeth 17; M |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | PersStoreMtrDatTransf 26; O                                   | PM-StoreMeth 28; M |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>If a PHG invokes the Get-Segment-Info method, it shall use operation type roiv-cmip-confirmed-action.</p> <p>If a PHG invokes the Get-Segment-Info method, it shall use the Action-type MDC_ACT_SEG_GET_INFO</p> <p>If a PHG invokes the Get-Segment-Info method, it shall use the action-info-args SegmSelection (all-segments)</p> <p>[AND]</p> <p>If a PHG supports the PM-store class, the support of the Get-Segment-Info and Trig-Segment-Data-Xfer methods is mandatory</p> <p>[AND]</p> <p>If the PHG supports sending the Get-Segment-Info method, the PHG shall support at least the choice all-segments in the SegmSelection action-info-args of the Get-Segment-Info method. The PHG may support additional choices.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                    |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                    |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                    |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state. The simulated PHD has at least one segment with data stored and PMStoreCapab indicates that it supports all the possible actions.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                    |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test perform a GetSegmentInfo action to recover the information of all the segments.</li> <li>2. The simulated PHD receives the message: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ul> </li> <li>b. invoke-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = This value identifies the message; the confirmed response that will be sent by the simulated PHD shall have the same invoke-id.</li> </ul> </li> <li>c. obj-handle <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = &lt;Handle of an existing PM-Store&gt;</li> </ul> </li> <li>d. action-type (roiv-cmip-confirmed-action) <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0C 0x0D (MDC_ACT_SEG_GET_INFO)</li> </ul> </li> <li>e. action-info-args <ul style="list-style-type: none"> <li><input type="checkbox"/> SegmSelection = all-segments (0)</li> </ul> </li> </ol> </li> </ol> |                                                               |                    |
+| <b>Pass/Fail criteria</b> | The PHG shall perform a Get Segment Action (all-segments) and the format of the received message must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                    |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/DIM/BV-005_B                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+| <b>TP label</b>           | PM-Store Class methods. Get-Segment-info method (segment-id-list)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | PM-StoreMeth 12; O                                            |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>A PHG may invoke the Get-Segment-Info method</p> <p>If a PHG invokes the Get-Segment-Info method, it shall use operation type roiv-cmip-confirmed-action.</p> <p>If a PHG invokes the Get-Segment-Info method, it shall use the Action-type MDC_ACT_SEG_GET_INFO</p> <p>If a PHG invokes the Get-Segment-Info method, it shall use the action-info-args SegmSelection (segm-id-list)</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_003 AND C_MAN_OXP_045                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state. The simulated PHD has at least one segment with data stored and PMStoreCapab indicates that it supports all the possible actions.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test perform a GetSegmentinfo action to recover only the information of one segment:</li> <li>2. The simulated PHD receives the message: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ul> </li> <li>b. invoke-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = This value identifies the message; the confirmed response that will be sent by the simulated PHD shall have the same invoke-id.</li> </ul> </li> <li>c. obj-handle <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = &lt;Handle of an existing PM-Store&gt;</li> </ul> </li> <li>d. action-type (roiv-cmip-confirmed-action) <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0C 0x0D (MDC_ACT_SEG_GET_INFO)</li> </ul> </li> <li>e. action-info-args <ul style="list-style-type: none"> <li><input type="checkbox"/> SegmSelection = segm-id-list <ul style="list-style-type: none"> <li>▪ SegmIdList = &lt;List of the selected segments' instance numbers&gt;</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                                                               |
+| <b>Pass/Fail criteria</b> | The format of the received message must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |
+
+|                 |                                                              |                                                               |
+|-----------------|--------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHG/OXP/DIM/BV-005_C                                  |                                                               |
+| <b>TP label</b> | PM-Store Class methods. Get-Segment-info method (time range) |                                                               |
+| <b>Coverage</b> | <b>Spec</b>                                                  | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                    |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|--|
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PM-StoreMeth 12; O |  |
+| <b>Test purpose</b>       | Check that:<br>A PHG may invoke the Get-Segment-Info method<br>If a PHG invokes the Get-Segment-Info method, it shall use operation type roiv-cmip-confirmed-action.<br>If a PHG invokes the Get-Segment-Info method, it shall use the Action-type MDC_ACT_SEG_GET_INFO<br>If a PHG invokes the Get-Segment-Info method, it shall use the action-info-args SegmSelection (abs-time-range)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                    |  |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_003 AND C_MAN_AG_OXP_044                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                    |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                    |  |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state. The simulated PHD has at least one segment with data stored and PMStoreCapab indicates that it supports all the possible actions.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                    |  |
+| <b>Test procedure</b>     | 1. Make the PHG under test perform a GetSegmentinfo action to recover the information of a time range.<br>2. The simulated PHD receives the message: <ol style="list-style-type: none"> <li>APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ul> </li> <li>invoke-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = This value identifies the message; the confirmed response that will be sent by the simulated PHD shall have the same invoke-id.</li> </ul> </li> <li>obj-handle <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = &lt;Handle of an existing PM-Store&gt;</li> </ul> </li> <li>action-type (roiv-cmip-confirmed-action) <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0C 0x0D (MDC_ACT_SEG_GET_INFO)</li> </ul> </li> <li>action-info-args <ul style="list-style-type: none"> <li><input type="checkbox"/> SegmentSelectiont = abs-time-range <ul style="list-style-type: none"> <li>▪ AbsTimeRange.from-time = &lt;Selected date of beginning&gt;</li> <li>▪ AbsTimeRange.to-time = &lt;Selected date of ending&gt;</li> </ul> </li> </ul> </li> </ol> |                    |  |
+| <b>Pass/Fail criteria</b> | The format of the received message must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                    |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                    |  |
+
+|                     |                                                                            |                                                               |  |
+|---------------------|----------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>        | TP/PLT/PHG/OXP/DIM/BV-005_D                                                |                                                               |  |
+| <b>TP label</b>     | PM-Store Class methods. Get-Segment-info method 4 (Base-Offset-Time range) |                                                               |  |
+| <b>Coverage</b>     | <b>Spec</b>                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                     | <b>Testable items</b>                                                      | PM-StoreMeth 12; O                                            |  |
+| <b>Test purpose</b> | Check that:                                                                |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>A PHG may invoke the Get-Segment-Info method</p> <p>If a PHG invokes the Get-Segment-Info method, it shall use operation type roiv-cmip-confirmed-action.</p> <p>If a PHG invokes the Get-Segment-Info method, it shall use the Action-type MDC_ACT_SEG_GET_INFO</p> <p>If a PHG invokes the Get-Segment-Info method, it shall use the action-info-args SegmSelection (bo-time-range)</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_003 AND C_MAN_OXP_081 AND (C_MAN_OXP_029 OR C_MAN_OXP_030)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state. The simulated PHD has at least one segment with data stored and PMStoreCapab indicates that it supports all the possible actions.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test perform a GetSegmentinfo action to recover the information of a time range.</li> <li>2. The simulated PHD receives the message: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ul> </li> <li>b. invoke-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = This value identifies the message; the confirmed response that will be sent by the simulated PHD shall have the same invoke-id.</li> </ul> </li> <li>c. obj-handle <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = &lt;Handle of an existing PM-Store&gt;</li> </ul> </li> <li>d. action-type (roiv-cmip-confirmed-action) <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0C 0x0D (MDC_ACT_SEG_GET_INFO)</li> </ul> </li> <li>e. action-info-args <ul style="list-style-type: none"> <li><input type="checkbox"/> SegmentSelectiont = bo-time-range <ul style="list-style-type: none"> <li>▪ BOTimeRange.from-time = &lt;Selected date of beginning&gt;</li> <li>▪ BOTimeRange.to-time = &lt;Selected date of ending&gt;</li> </ul> </li> </ul> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                     |                                                                                                                                       |                                                               |                    |
+|---------------------|---------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------|
+| <b>TP Id</b>        | TP/PLT/PHG/OXP/DIM/BV-006                                                                                                             |                                                               |                    |
+| <b>TP label</b>     | PM-Store Class methods. Trig-Segment-Data-Xfer method                                                                                 |                                                               |                    |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                           | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                    |
+|                     | <b>Testable items</b>                                                                                                                 | PM-StoreMeth 15; O                                            | PM-StoreMeth 17; M |
+| <b>Test purpose</b> | <p>Check that:</p> <p>If a PHG invokes the Trig-Segment-Data-Xfer method, it shall use operation type roiv-cmip-confirmed-action.</p> |                                                               |                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>If a PHG invokes the Trig-Segment-Data-Xfer method, it shall use the Action-type MDC_ACT_SEG_TRIG_XFER</p> <p>If a PHG invokes the Trig-Segment-Data-Xfer method, it shall use the action-info-args TrigSegmDataXferReq</p> <p>[AND]</p> <p>If a PHG supports the PM-store class, the support of the Get-Segment-Info and Trig-Segment-Data-Xfer methods is mandatory.</p> <p>[AND]</p> <p>The PHG sends the ACTION method to the PHD with the handle of the PM-store object to access. The argument to this ACTION method is the instance number of the segment to transfer</p> <p>[AND]</p> <p>If Protocol Version 3, the PHG must send Get-Segment-Info or Get-Segment-Id-List at the beginning of accessing any PM-Store object</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state. The simulated PHD has at least one segment with data stored and PMStoreCapab indicates that it supports all the possible actions.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test perform a Trig-Segment-Data-Xfer.</li> <li>2. The simulated PHD receives the message: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ul> </li> <li>b. invoke-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = This value identifies the message; the confirmed response that will be sent by the simulated PHD shall have the same invoke-id.</li> </ul> </li> <li>c. obj-handle <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = &lt;Handle of an existing PM-Store&gt;</li> </ul> </li> <li>d. action-type (roiv-cmip-confirmed-action) <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0C 0x1C (MDC_ACT_SEG_TRIG_XFER)</li> </ul> </li> <li>e. action-info-args <ul style="list-style-type: none"> <li><input type="checkbox"/> TrigSegmDataXferReq.seg-inst-no = &lt;One of the existing PM-Segments' instance number&gt;</li> </ul> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The PHG shall perform a Trig-Segment-Data-Xfer Action and the format of the received message must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                 |                                              |                                                               |
+|-----------------|----------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHG/OXP/DIM/BV-007_A                  |                                                               |
+| <b>TP label</b> | PM-Store Class methods. Segment-Data-Event 1 |                                                               |
+| <b>Coverage</b> | <b>Spec</b>                                  | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                 | <b>Testable</b>                              | PM-StoreEvent 3; M                                            |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |  |  |  |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|
+|                           | <b>items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |  |  |  |
+| <b>Test purpose</b>       | Check that:<br>PHGs must respond to Segment-Data-Event events when received<br>When responding to a Segment-Data-Event event the event-reply-info parameter shall be SegmentDataResult.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |  |  |  |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |  |  |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |  |  |  |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state. The simulated PHD has at least one segment with data stored and PMStoreCapab indicates that it supports all the possible actions.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  |  |  |
+| <b>Test procedure</b>     | 1. Make the PHG under test perform a Trig-Segment-Data-Xfer.<br>2. The simulated PHD responds to the message with a "TrigSegmDataXferRsp".<br>3. The simulated PHD sends a Confirmed event report:<br><ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Remote Operation Invoke   Confirmed Event ReportAction</li> <li><input type="checkbox"/> HANDLE = PM-Store obj-handle</li> <li><input type="checkbox"/> Action = 0x0D 0x21 (MDC_NOTI_SEGMENT_DATA)</li> <li><input type="checkbox"/> SegmentDataEvent.SegmDataEventDescr = SEQUENCE: <ul style="list-style-type: none"> <li>▪ segm-instance</li> <li>▪ segmt-evt-entry-index</li> <li>▪ segmt-evt-entry-count</li> <li>▪ segmt-evt-status = Bit 0 must be set</li> </ul> </li> </ul> </li> </ul> 4. The PHG under test sends a response to the previous message:<br><ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Remote Operation Invoke   Confirmed ActionEvent Report</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = 0x0D 0x21 (MDC_NOTI_SEGMENT_DATA)</li> <li><input type="checkbox"/> SegmentDataResult = SEQUENCE: <ul style="list-style-type: none"> <li>▪ segm-instance = &lt;The one previously sent by the simulated PHD&gt;</li> <li>▪ segmt-evt-entry-index = &lt;The one previously sent by the simulated PHD&gt;</li> <li>▪ segmt-evt-entry-count = &lt;The one previously sent by the simulated PHD&gt;</li> <li>▪ segmt-evt-status = Bits 0, 1 must be the same as those previously recorded. Bit 4 must NOT be set. One of bits 8 or 12 must be set.</li> </ul> </li> </ul> </li> </ul> |  |  |  |
+| <b>Pass/Fail criteria</b> | The format of the received message must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |  |  |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |  |  |  |
+
+|                      |                                                                                                                                                                                         |                                                               |  |  |
+|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|--|
+| <b>TP Id</b>         | TP/PLT/PHG/OXP/DIM/BV-007_B                                                                                                                                                             |                                                               |  |  |
+| <b>TP label</b>      | PM-Store Class methods. Segment-Data-Event 2                                                                                                                                            |                                                               |  |  |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                             | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |  |
+|                      | <b>Testable items</b>                                                                                                                                                                   | PM-StoreEvent 3; M                                            |  |  |
+| <b>Test purpose</b>  | Check that:<br>PHGs must respond to Segment-Data-Event events when received<br>When responding to a Segment-Data-Event event the event-reply-info parameter shall be SegmentDataResult. |                                                               |  |  |
+| <b>Applicability</b> | C_MAN_OXP_000 AND C_MAN_OXP_003                                                                                                                                                         |                                                               |  |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state. The simulated PHD has at least one segment with data stored and PMStoreCapab indicates that it supports all the possible actions.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test perform a Trig-Segment-Data-Xfer.</li> <li>2. The simulated PHD responds to the message with a "TrigSegmDataXferRsp".</li> <li>3. The simulated PHD sends a Confirmed event report: <ol style="list-style-type: none"> <li>a. Data APDU <ol style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Event Report</li> <li><input type="checkbox"/> HANDLE = PM-Store obj-handle</li> <li><input type="checkbox"/> Action = 0x0D 0x21 (MDC_NOTI_SEGMENT_DATA)</li> <li><input type="checkbox"/> SegmentDataEvent.SegmDataEventDescr = SEQUENCE: <ol style="list-style-type: none"> <li>▪ segm-instance</li> <li>▪ segm-evt-entry-index</li> <li>▪ segm-evt-entry-count</li> <li>▪ segm-evt-status = Bit 4 (sevtsta-agent-abort) must be set</li> </ol> </li> </ol> </li> </ol> </li> <li>4. The PHG under test sends a response to the previous message: <ol style="list-style-type: none"> <li>a. Data APDU <ol style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Event Report</li> <li><input type="checkbox"/> HANDLE = PM-Store obj-handle</li> <li><input type="checkbox"/> Action = 0x0D 0x21 (MDC_NOTI_SEGMENT_DATA)</li> <li><input type="checkbox"/> SegmentDataResult = SEQUENCE: <ol style="list-style-type: none"> <li>▪ segm-instance = &lt;The one previously sent by the simulated PHD&gt;</li> <li>▪ segm-evt-entry-index = &lt;The one previously sent by the simulated PHD&gt;</li> <li>▪ segm-evt-entry-count = &lt;The one previously sent by the simulated PHD&gt;</li> <li>▪ segm-evt-status = Bits 4 and 8 must be set</li> </ol> </li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                                            |
+|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------------------------------|
+| <b>TP Id</b>         | TP/PLT/PHG/OPX/DIM/BV-013                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                                            |
+| <b>TP label</b>      | EpiCfgScanner Class events. Unbuf-Scan-Report-Grouped                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                                            |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                                            |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | EpiCfgScanEvent 12;C<br>ScanClassAttr 3; M                    | ObjAccessServ 2;M<br>EpiCfgScanEvent 34; C |
+| <b>Test purpose</b>  | <p>Check that:</p> <p>If an Episodic Scanner uses Unbuf-Scan-Report-Grouped Events to report updated data; and it reports data in confirmed mode, a PHG shall use a rors-cmip-confirmed-event-report operation to acknowledge the operation.</p> <p>[AND]</p> <p>The PHG shall use the SET action to request a change in the value of this attribute (Operational State)</p> <p>[AND]</p> <p>If a PHG supports episodic scanners, it shall support all the events identified in Table 16 (Episodic configurable scanner object events).</p> |                                                               |                                            |
+| <b>Applicability</b> | C_MAN_OXP_000 AND C_MAN_OXP_001                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                                            |
+| <b>Other PICS</b>    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                                            |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test set the OperationalState attribute of an episodic scanner of the simulated PHD to 1: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ol> </li> <li>b. invoke-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = It is not relevant</li> </ol> </li> <li>c. CHOICE <ol style="list-style-type: none"> <li><input type="checkbox"/> value = 0x01 0x05 (roiv-cmip-confirmed-set)</li> </ol> </li> <li>d. obj-handle <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = Scanner HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 21 &lt;Handle of the Episodic scanner&gt;</li> </ol> </li> <li>e. Modification-list <ol style="list-style-type: none"> <li><input type="checkbox"/> modify-operator.count = 1</li> <li><input type="checkbox"/> modify-operator.length = 2 bytes</li> <li><input type="checkbox"/> modify-operator.value = 0 (replace)</li> <li><input type="checkbox"/> attribute.type = 0x09 0x53 (MDC_ATTR_OP_STAT)</li> <li><input type="checkbox"/> attribute.value = 1</li> </ol> </li> </ol> </li> <li>2. The simulated PHD responds to the message with a "rors-cmip-confirmed-set".</li> <li>3. The simulated PHD sends a confirmed event report of the episodic scanner (MDC_NOTI_UNBUF_SCAN_REPORT_GROUPED) to the PHG under test:</li> <li>4. The PHG under test responds with a "rors-confirmed-event-report": <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ol> </li> <li>b. invoke-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = The same as the one sent by the simulated PHD.</li> </ol> </li> <li>c. obj-handle <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 21 &lt;Handle of the Episodic scanner&gt;</li> </ol> </li> <li>d. event-type (rors-confirmed-event-report) <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0D 0x24 (MDC_NOTI_UNBUF_SCAN_REPORT_GROUPED)</li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received messages in steps 1 and 4 must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                   |                       |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-------------------|-----------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/DIM/BV-016                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                   |                       |
+| <b>TP label</b>           | EpiCfgScanner Class events. Unbuf-Scan-Report-MP-Grouped                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                   |                       |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                   |                       |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | EpiCfgScanEvent 24;C                                          | ObjAccessServ 2;M | EpiCfgScanEvent 34; C |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>If an Episodic Scanner uses Unbuf-Scan-Report-MP-Grouped Events to report updated data; and it reports data in confirmed mode, a PHG shall use a rors-cmip-confirmed-event-report operation to acknowledge the operation.</p> <p>[AND]</p> <p>If a PHG supports episodic scanners, it shall support all the events identified in Table 16 (Episodic configurable scanner object events).</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                   |                       |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_001 AND C_MAN_OXP_037                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                   |                       |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                   |                       |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                   |                       |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test set the OperationalState attribute of an episodic scanner of the simulated PHD to 1.</li> <li>2. The simulated PHD responds to the message with a "rors-cmip-confirmed-set".</li> <li>3. The simulated PHD sends a confirmed event report of the episodic scanner (MDC_NOTI_UNBUF_SCAN_REPORT_MP_GROUPED) to the PHG under test:</li> <li>4. The PHG under test responds with a "rors-confirmed-event-report": <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ol> </li> <li>b. invoke-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = The same as the one sent by the simulated PHD.</li> </ol> </li> <li>c. obj-handle <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 21 &lt;Handle of the Episodic scanner&gt;</li> </ol> </li> <li>d. event-type (rors-confirmed-event-report) <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0D 0x27 (MDC_NOTI_UNBUF_SCAN_REPORT_MP_GROUPED)</li> </ol> </li> </ol> </li> </ol> |                                                               |                   |                       |
+| <b>Pass/Fail criteria</b> | The format of the received message must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                   |                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                   |                       |
+
+|                     |                                                      |                                                               |                   |                        |
+|---------------------|------------------------------------------------------|---------------------------------------------------------------|-------------------|------------------------|
+| <b>TP Id</b>        | TP/PLT/PHG/OXP/DIM/BV-019                            |                                                               |                   |                        |
+| <b>TP label</b>     | PeriCfgScanner Class events. Buf-Scan-Report-Grouped |                                                               |                   |                        |
+| <b>Coverage</b>     | <b>Spec</b>                                          | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                   |                        |
+|                     | <b>Testable items</b>                                | PeriCfgScanEvent 12;C                                         | ObjAccessServ 2;M | PeriCfgScanEvent 27; C |
+| <b>Test purpose</b> | Check that:                                          |                                                               |                   |                        |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | <p>If a Periodic Configurable Scanner uses Buf-Scan-Report-Grouped Events to report updated data; and it reports data in confirmed mode, a PHG shall use a rors-cmip-confirmed-event-report operation to acknowledge the operation.</p> <p>[AND]</p> <p>If a PHG supports periodic scanners, it shall support all the events identified in Table 18 (Periodic configurable scanner object events).</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND C_MAN_OXP_006                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Make the PHG under test set the OperationalState attribute of a periodic scanner of the simulated PHD to 1: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ul> </li> <li>b. invoke-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = The same as the one sent by the simulated PHD.</li> </ul> </li> <li>c. CHOICE <ul style="list-style-type: none"> <li><input type="checkbox"/> value = 0x01 0x05 (roiv-cmip-confirmed-set)</li> </ul> </li> <li>d. obj-handle <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = Scanner HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 20 &lt;Handle of the Periodic scanner&gt;</li> </ul> </li> <li>e. Modification-list <ul style="list-style-type: none"> <li><input type="checkbox"/> modify-operator.count = 1</li> <li><input type="checkbox"/> modify-operator.length = 2 bytes</li> <li><input type="checkbox"/> modify-operator.value = 0 (replace)</li> <li><input type="checkbox"/> attribute.type = 0x09 0x53 (MDC_ATTR_OP_STAT)</li> <li><input type="checkbox"/> attribute.value = 1</li> </ul> </li> </ol> </li> <li>2. The simulated PHD responds to the message with a "rors-cmip-confirmed-set".</li> <li>3. The simulated PHD sends a confirmed event report of the periodic scanner (MDC_NOTI_BUF_SCAN_REPORT_GROUPED) to the PHG under test:</li> <li>4. The PHG under test responds with a "rors-confirmed-event-report": <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ul> </li> <li>b. invoke-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = The same as the one sent by the simulated PHD.</li> </ul> </li> <li>c. obj-handle <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 20&lt;Handle of the Periodic scanner&gt;</li> </ul> </li> <li>d. event-type (rors-confirmed-event-report)</li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                          |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> field-type = OID-Type<br><input type="checkbox"/> field-length = 2 bytes<br><input type="checkbox"/> field-value = 0x0D 0x2A (MDC_NOTI_BUF_SCAN_REPORT_GROUPED) |
+| <b>Pass/Fail criteria</b> | The format of the received message must be the one specified.                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                          |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                   |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/DIM/BV-022                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                   |
+| <b>TP label</b>           | PeriCfgScanner Class events. Buf-Scan-Report-MP-Grouped                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                   |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                   |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | PeriCfgScanEvent 24;C                                         | ObjAccessServ 2;M |
+| <b>Test purpose</b>       | Check that:<br><br>If a Periodic Configurable Scanner uses Buf-Scan-Report-MP-Grouped Events to report updated data; and it reports data in confirmed mode, a PHG shall use a rors-cmip-confirmed-event-report operation to acknowledge the operation.<br><br>[AND]<br><br>If a PHG supports periodic scanners, it shall support all the events identified in Table 18 (Periodic configurable scanner object events).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                   |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_006 AND C_MAN_OXP_037                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                   |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                   |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                   |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test set the OperationalState attribute of an episodic scanner of the simulated PHD to 1.</li> <li>2. The simulated PHD responds to the message with a "rors-cmip-confirmed-set".</li> <li>3. The simulated PHD sends a confirmed event report of the periodic scanner (MDC_NOTI_BUF_SCAN_REPORT_MP_GROUPED) to the PHG under test:</li> <li>4. The PHG under test responds with a "rors-confirmed-event-report":               <ol style="list-style-type: none"> <li>a. APDU Type                   <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ul> </li> <li>b. invoke-id                   <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = The same as the one sent by the simulated PHD.</li> </ul> </li> <li>c. obj-handle                   <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 20 &lt;Handle of the Periodic scanner&gt;</li> </ul> </li> <li>d. event-type (rors-confirmed-event-report)                   <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0D 0x2D (MDC_NOTI_BUF_SCAN_REPORT_MP_GROUPED)</li> </ul> </li> </ol> </li> </ol> |                                                               |                   |
+| <b>Pass/Fail criteria</b> | The format of the received message must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|--|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/DIM/BV-024                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |  |
+| <b>TP label</b>           | Information Model Extensibility rules 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | InfoExt 2;M                                                   |  |  |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>An implementation of a PHG system shall process a message fully by skipping any unknown attributes (e.g., vendor specified attributes) and ignoring the assigned data values of such attributes, without protocol errors. The implementation may log the occurrence of such attributes as appropriate.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |  |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |  |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an AARQ with an extended dev-config-id previously unknown to the PHG under test.</li> <li>2. The PHG under test sends an AARE with an "accepted-unknown-config".</li> <li>3. The simulated PHD sends a configuration event report whose first object has a unknown vendor attribute defined (attribute id 0xF0 0x01): <ol style="list-style-type: none"> <li>a. 0xF0 0x01 <ol style="list-style-type: none"> <li><input type="checkbox"/> value.length = 2</li> <li><input type="checkbox"/> value = 0xFF 0xFF</li> </ol> </li> <li>b. The rest of the configuration is the same as one of the PHG supported standard configurations.</li> </ol> </li> <li>4. The PHG answers the configuration event report and reaches the Operating state.</li> <li>5. The simulated PHD sends a confirmed fixed event report (sending a known attribute).</li> <li>6. The PHG sends a rors-cmip-confirmed-event-report for data sent in step 5.</li> <li>7. The simulated PHD sends a confirmed Variable event report updating the value of the unknown attribute: <ol style="list-style-type: none"> <li>a. obj-handle = 1</li> <li>b. 0xF0 0x01 <ol style="list-style-type: none"> <li><input type="checkbox"/> value.length = 2</li> <li><input type="checkbox"/> value = 0xFF 0xFE</li> </ol> </li> </ol> </li> <li>8. The PHG sends a rors-cmip-confirmed-event-report message for data sent in step 7.</li> <li>9. The simulated PHD sends a confirmed fixed event report (sending a known attribute).</li> <li>10. The PHG sends a rors-cmip-confirmed-event-report for data sent in step 9.</li> </ol> |                                                               |  |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHG shall ignore the private nomenclature code and moves to Operating state</li> <li>• In step 5 the response cannot be an abort message</li> <li>• The PHG shall ignore the data received Var Event Report, but without protocol violations, so it has to send a confirmation response for data sent in step 6</li> <li>• In step 10 the response cannot be an abort message</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |  |
+
+|                 |                                                    |                                                               |                 |                 |
+|-----------------|----------------------------------------------------|---------------------------------------------------------------|-----------------|-----------------|
+| <b>TP Id</b>    | TP/PLT/PHG/OXP/DIM/BV-025                          |                                                               |                 |                 |
+| <b>TP label</b> | Manager State Machine: Association Response Format |                                                               |                 |                 |
+| <b>Coverage</b> | <b>Spec</b>                                        | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                 |                 |
+|                 | <b>Testable items</b>                              | ManagerStateMach 65; M                                        | AssocResp 2;M   | AssocResp 8; M  |
+|                 |                                                    | AssocResp 9; M                                                | AssocResp 10; M | AssocResp 11; M |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |  |  |  |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--|--|
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [b-ITU-T H.810 (2015)] |  |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | General 4; M           |  |  |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If aarq received while in Unassociated state, a PHG shall move to connected associating state</p> <p>[AND]</p> <p>The encoding-rules field contains the one and only one, DataApdu encoding rule shall be chosen by the PHG, if the result field is equal to accepted or accepted-unknown-config</p> <p>[AND]</p> <p>The dev-config-id field shall be manager-config-response in the response.</p> <p>[AND]</p> <p>The data-req-mode-capab field shall be zero in the response.</p> <p>[AND]</p> <p>The option-list field is not currently used by this standard. This field should be an empty list.</p> <p>[AND]</p> <p>The protocol-version field contains the version of the common data protocol chosen by the PHG if the result field is equal to accepted or accepted-unknown-config</p> <p>The nomenclature-version field contains the version of the nomenclature chosen by the PHG if the result field is equal to accepted or accepted-unknown-config.</p> <p>The functional-units field indicates the common functional units and optional features chosen by the PHG if the result field is equal to accepted or accepted-unknown-config.</p> <p>The system-type field contains the system type.</p> <p>The system-id field has the unique system ID of the PHG</p> <p>[AND]</p> <p>Continua client components shall support associations with Continua LAN service components where only the version 1 bit of the protocol-version is set in the PHDAssociationInformation structure in the AARQ.</p> <p>In that case, the Continua client components shall respond with the version 1 bit of the protocol version set in the PHDAssociationInformation structure in the AARE and shall follow the ISO/IEEE Std 11073-20601-2008 specification along with all corrections and clarifications included in the [ISO/IEEE Std 11073-20601-2015A]</p> |                        |  |  |  |
+| <b>Applicability</b>     | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |  |  |  |
+| <b>Other PICS</b>        | C_MAN_OXP_016, C_MAN_OXP_018, C_MAN_OXP_019, C_MAN_OXP_020,<br>C_MAN_OXP_024, C_MAN_OXP_025, C_MAN_OXP_026, C_MAN_OXP_027,<br>C_MAN_OXP_029, C_MAN_OXP_067, C_MAN_OXP_069, C_MAN_OXP_071,<br>C_MAN_OXP_072, C_MAN_OXP_076, C_MAN_OXP_021, C_MAN_OXP_022,<br>C_MAN_OXP_023, C_MAN_OXP_030, C_MAN_OXP_077                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |  |  |  |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |  |  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHD sends an Association Request to the PHG under test: <ul style="list-style-type: none"> <li><input type="checkbox"/> dev-config-id <ul style="list-style-type: none"> <li>▪ IF (C_MAN_OXP_016 OR C_MAN_OXP_018 OR C_MAN_OXP_019 OR C_MAN_OXP_020 OR C_MAN_OXP_024 OR C_MAN_OXP_025 OR C_MAN_OXP_026 OR C_MAN_OXP_027 OR C_MAN_OXP_029 OR C_MAN_OXP_067 OR C_MAN_OXP_069 OR C_MAN_OXP_071 OR C_MAN_OXP_072 OR C_MAN_OXP_076) THEN dev-config-id set to one of the supported standard configurations</li> <li>▪ IF (C_MAN_OXP_021 OR C_MAN_OXP_022 OR C_MAN_OXP_023 OR C_MAN_OXP_030 OR C_MAN_OXP_077) THEN dev-config-id set to an extended dev-config-id.</li> </ul> </li> <li><input type="checkbox"/> encoding rules = 0xE0 0x00</li> <li><input type="checkbox"/> protocol-version</li> </ul> </li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |  |  |  |
+
+- IF the PHG applies for Basic ECG, INR, SABTE or CGM certification only THEN protocol-version = 0x40 0x00 0x00 0x00
+  - IF the PHG applies for Insulin Pump or Glucose Meter certification only THEN protocol-version = 0x20 0x00 0x00 0x00
+  - IF the PHG applies for Power Status Monitor certification only THEN protocol-version = 0x60 0x00 0x00 0x00
+  - ELSE protocol-version = 0x80 0x00 0x00 0x00
+- ❑ nomenclature-version = 0x80 0x00 0x00 0x00
+  - ❑ functional-units = 0x00 0x00 0x00 0x00
+  - ❑ system-type = 0x00 0x80 0x00 0x00
+  - ❑ data-req-mode-capab =
+    - data-req-mode-flags = 0x00 0x01
+    - data-req-init-agent-count = 1
+    - data-req-init-manager-count = 0
+  - ❑ option-list = <absent>
+2. The PHG under test responds with an Association Response:
+- a. APDU Type
+    - field-length = 2 bytes
+    - field-value = 0xE3 0x00 (AareAdpu)
+  - b. Result
+    - field-length = 2 bytes
+    - field-value = one of :
+      - 0x00 0x00 (accepted-config)
+      - 0x00 0x03 (accepted-unknown-config)
+  - c. Data-Proto-Id
+    - field.type = DataProtoId
+    - field.length = 2 bytes
+    - field.value = <The one sent in the AARQ>
+  - d. The DataProto.Info field must contain two bytes indicating the data-protocol.info.length
+  - e. protocol-version
+    - field-type = Protocol Version
+    - field-length = BITS-32
+    - IF the PHG applies for Basic ECG, INR, SABTE or CGM certification only THEN
+      - field-value = 0x40 0x00 0x00 0x00
+      - This value shows that version 2 of the data exchange protocol is supported (protocol-version2(1)=1)
+    - ELSE IF the PHG applies for Insulin Pump or Glucose Meter certification only THEN
+      - field-value = 0x20 0x00 0x00 0x00
+      - This value shows that version 3 of the data exchange protocol is supported (protocol-version3(2)=1)
+    - ELSE IF the PHG applies for Power Status Monitor certification only THEN
+      - field-value = 0x40 0x00 0x00 0x00 OR 0x20 0x00 0x00 0x00 OR 0x60 0x00 0x00 0x00
+      - This value shows that version 2 OR version 3 of the data exchange
+
+protocol are supported (protocol-version2(1)=1 OR protocol-version3(2)=1)
+
+ELSE
+
+- field-value = 0x80 0x00 0x00 0x00
+- This value shows that version 1 of the data exchange protocol is supported (protocol-version1(0)=1).
+
+#### f. encoding rules
+
+- field-type = EncodingRules
+- field-length = BITS-16
+- field-value = One of the following must be set.
+  - Bit 0 (mder)
+  - Bit 1 (xer)
+  - Bit 2 (per)
+
+#### g. nomenclature version
+
+- field-type = NomenclatureVersion
+- field-length = BITS-32
+- field-value = 0x80 0x00 0x00 0x00 (nom-version1)
+
+#### h. functional-units
+
+- field-type = FunctionalUnits
+- field-length = 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 = BITS-32
+- field-value = 0x80 0x00 0x00 0x00 (sys-type-manager)
+
+#### j. system-id
+
+- field-type = OCTET STRING
+- field-length = 0x00 0x08
+- field-value = <Check with PIXITs>
+
+#### k. dev-config-id
+
+- field-type = ConfigId
+- field-length = INT-U16
+- field-value = 0x00 0x00 (manager-config-response)
+
+#### l. Data-Req-Mode-Capab:
+
+- field-type = DataReqModeCapab
+- field-length = INT-U16
+- field-value = 0x00 0x00
+
+#### m. option-list should be:
+
+- field-type: AttributeList
+- list.count = 0
+- list.length = 0
+
+|                           |                                                               |
+|---------------------------|---------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | The format of the received message must be the one specified. |
+| <b>Notes</b>              |                                                               |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                     |                   |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|-------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/DIM/BV-036                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                     |                   |
+| <b>TP label</b>          | BCD time format - fixed format event report                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                     |                   |
+| <b>Coverage</b>          | <b>Spec</b> [ISO/IEEE 11073-10415]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                     |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | WeightNumClass 30;C |                   |
+|                          | <b>Spec</b> [ISO/IEEE 11073-10417]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                     |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | BloodGL 12;C        |                   |
+|                          | <b>Spec</b> [ISO/IEEE 11073-10407]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                     |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | SystDiast_31;C      | PulsRat_30;C      |
+|                          | <b>Spec</b> [ISO/IEEE 11073-10408]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                     |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Num Objec Temp19;C  |                   |
+|                          | <b>Spec</b> [ISO/IEEE 11073-10472]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                     |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | VarDosage16; C      | UserFeedback16; C |
+|                          | <b>Spec</b> [ISO/IEEE 11073-10421]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                     |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | PEF16; C            | PersBest16; C     |
+|                          | <b>Spec</b> [ISO/IEEE 11073-10420]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                     |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | BodyFat31; C        | BodyHeight30; C   |
+| <b>Test purpose</b>      | Check that:<br>For Standard-Configuration, the Attribute-Value-Map attribute shall be present<br>The value of the Attribute-Value-Map attribute shall be MDC_ATTR_NU_VAL_OBS_SIMP, then MDC_ATTR_TIME_STAMP_ABS                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                     |                   |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND (C_MAN_OXP_019 OR C_MAN_OXP_020 OR C_MAN_OXP_024 OR C_MAN_OXP_025 OR C_MAN_OXP_016 OR C_MAN_OXP_018 OR C_MAN_OXP_027)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                     |                   |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                     |                   |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Operating state using the standard configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                     |                   |
+| <b>Test procedure</b>    | IF C_MAN_OXP_019 (the PHG supports glucose meter specialization)<br>1. The simulated PHD sends a confirmed fixed event report for handle 1 (Blood Glucose object) containing an observation and a time stamp with century = 0x19, year = 0x99, month = 0x12, day = 0x25, hour = 0x23, minute = 0x59, second = 0x30, sec-fractions = 0x75.<br>2. The simulated PHD waits until it receives a confirmation from the PHG under test.<br>IF C_MAN_OXP_020 (the PHG supports blood pressure monitor specialization)<br>1. The simulated PHD sends a confirmed fixed event report for handle 1 (Systolic/Diastolic/MAP object) and handle 2 (Pulse Rate object) containing an observation and a time stamp with century = 0x19, year = 0x99, month = 0x12, day = 0x25, hour = 0x23, minute = 0x59, second = 0x30, sec-fractions = 0x75.<br>2. The simulated PHD waits until it receives a confirmation from the PHG under test.<br>IF C_MAN_OXP_024 (the PHG supports weighing scales specialization) |                     |                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ol style="list-style-type: none"> <li>The simulated PHD sends a confirmed fixed event report for handle 1 (Body Weight object) containing an observation and a time stamp with century = 0x19, year = 0x99, month = 0x12, day = 0x25, hour = 0x23, minute = 0x59, second = 0x30, sec-fractions = 0x75.</li> <li>The simulated PHD waits until it receives a confirmation from the PHG under test.</li> </ol> <p>IF C_MAN_OXP_025 (the PHG supports thermometer specialization)</p> <ol style="list-style-type: none"> <li>The simulated PHD sends a confirmed fixed event report for handle 1 (Body Temperature object) containing an observation and a time stamp with century = 0x19, year = 0x99, month = 0x12, day = 0x25, hour = 0x23, minute = 0x59, second = 0x30, sec-fractions = 0x75.</li> <li>The simulated PHD waits until it receives a confirmation from the PHG under test.</li> </ol> <p>IF C_MAN_OXP_016 (the PHG supports adherence monitor specialization)</p> <ol style="list-style-type: none"> <li>The simulated PHD sends a confirmed fixed event report for handle 2 (Variable Dosage Medication object), handle 3 (Status Reporter) and handle 4 (User Feedback) containing an observation and a time stamp with century = 0x19, year = 0x99, month = 0x12, day = 0x25, hour = 0x23, minute = 0x59, second = 0x30, sec-fractions = 0x75.</li> <li>The simulated PHD waits until it receives a confirmation from the PHG under test.</li> </ol> <p>IF C_MAN_OXP_018 (the PHG supports peak flow specialization)</p> <ol style="list-style-type: none"> <li>The simulated PHD sends a confirmed fixed event report for handle 1 (PEF), handle 2 (Personal Best), handle 3 (FEV1) and handle 5 (Reading Status) containing an observation and a time stamp with century = 0x19, year = 0x99, month = 0x12, day = 0x25, hour = 0x23, minute = 0x59, second = 0x30, sec-fractions = 0x75.</li> <li>The simulated PHD waits until it receives a confirmation from the PHG under test.</li> </ol> <p>IF C_MAN_OXP_027 (the PHG supports body composition analyser specialization)</p> <ol style="list-style-type: none"> <li>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 and a time stamp with century = 0x19, year = 0x99, month = 0x12, day = 0x25, hour = 0x23, minute = 0x59, second = 0x30, sec-fractions = 0x75</li> <li>The simulated PHD waits until it receives a confirmation from the PHG under test.</li> </ol> |
+| <b>Pass/Fail criteria</b> | Verify that the PHG under test is able to accept the data and time stamps and applies the date properly as 12/25/1999 23:59:30.75 (e.g., if there is a UI verify the date is displayed in some form that indicates the correct date and time as transmitted).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                     |                                                                                                                                                                                                                                      |                                              |
+|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|
+| <b>TP Id</b>        | TP/PLT/PHG/OXP/DIM/BV-037                                                                                                                                                                                                            |                                              |
+| <b>TP label</b>     | BCD time format - variable format event report                                                                                                                                                                                       |                                              |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                          | [ISO/IEEE 11073-10415]                       |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                | WeightNumClass 30;C                          |
+|                     | <b>Spec</b>                                                                                                                                                                                                                          | [ISO/IEEE 11073-10407]                       |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                | SystDiast_31;C PulsRat_30;C                  |
+|                     | <b>Spec</b>                                                                                                                                                                                                                          | [ISO/IEEE 11073-10404]                       |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                | PulseRateNumObjAttr 30;C SpO2NumObjAttr 13;C |
+|                     | <b>Spec</b>                                                                                                                                                                                                                          | [ISO/IEEE 11073-10408]                       |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                | Num Objec Temp19;C                           |
+| <b>Test purpose</b> | Check that:<br><br>For [Standard-Configuration], If fixed format is used and the standard configuration is not adjusted, the Absolute-Time-Stamp attribute is mandatory; otherwise, the conditions from ISO/IEEE P11073-20601 apply. |                                              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Applicability</b>      | C_MAN_OXP_000 AND (C_MAN_OXP_020 OR C_MAN_OXP_024 OR C_MAN_OXP_025 OR C_MAN_OXP_026)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state using the standard configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Test procedure</b>     | <p>IF C_MAN_OXP_020 (the PHG supports blood pressure monitor specialization)</p> <ol style="list-style-type: none"> <li>The simulated PHD sends a confirmed variable event report for handle 1 (Systolic/Diastolic/MAP object) and handle 2 (Pulse Rate object) containing a time stamp with century = 0x19, year = 0x20, month = 0x11, day = 0x18, hour = 0x21, minute = 0x22, second = 0x23, sec-fractions = 0x90 and an observation (in that order).</li> <li>The simulated PHD waits until it receives a confirmation from the PHG under test.</li> </ol> <p>IF C_MAN_OXP_024 (the PHG supports weighing scales specialization)</p> <ol style="list-style-type: none"> <li>The simulated PHD sends a confirmed variable event report for handle 1 (Body Weight object) containing a time stamp with century = 0x19, year = 0x20, month = 0x11, day = 0x18, hour = 0x21, minute = 0x22, second = 0x23, sec-fractions = 0x90 and an observation (in that order).</li> <li>The simulated PHD waits until it receives a confirmation from the PHG under test.</li> </ol> <p>IF C_MAN_OXP_025 (the PHG supports thermometer specialization)</p> <ol style="list-style-type: none"> <li>The simulated PHD sends a confirmed variable event report for handle 1 (Body Temperature object) containing a time stamp with century = 0x19, year = 0x20, month = 0x11, day = 0x18, hour = 0x21, minute = 0x22, second = 0x23, sec-fractions = 0x90 and an observation (in that order).</li> <li>The simulated PHD waits until it receives a confirmation from the PHG under test.</li> </ol> <p>IF C_MAN_OXP_026 (the PHG supports pulse oximeter specialization)</p> <ol style="list-style-type: none"> <li>The simulated PHD sends a confirmed variable event report for handle 1 (SpO<sub>2</sub> object) and handle 10 (Pulse Rate object) containing a time stamp with century = 0x19, year = 0x20, month = 0x11, day = 0x18, hour = 0x21, minute = 0x22, second = 0x23, sec-fractions = 0x90 and an observation (in that order).</li> <li>The simulated PHD waits until it receives a confirmation from the PHG under test.</li> </ol> |
+| <b>Pass/Fail criteria</b> | Verify that the PHG under test is able to accept the data and time stamps and applies the date properly as 11/18/1920 21:22:23.90 (e.g., if there is a UI verify the date is displayed in some form that indicates the correct date and time as transmitted).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                       |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/DIM/BV-038                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                       |
+| <b>TP label</b>          | EpiCfgScanner Class events. Unbuf-Scan-Report-Var                                                                                                                                                                                                                                                                                                                                                           |                                                               |                       |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                       |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                       | EpiCfgScanEvent 4; C                                          | EpiCfgScanEvent 34; C |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If an Episodic Scanner uses Unbuf-Scan-Report-Var Events to report updated data; and it reports data in confirmed mode, a PHG shall use a rors-cmip-confirmed-event-report operation to acknowledge the operation.</p> <p>[AND]</p> <p>If a PHG supports episodic scanners, it shall support all the events identified in Table 16 (Episodic configurable scanner object events).</p> |                                                               |                       |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND C_MAN_OXP_001                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                       |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                       |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                        |                                                               |                       |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>Make the PHG under test set the OperationalState attribute of an episodic scanner of the simulated PHD to 1.</li> </ol>                                                                                                                                                                                                                                              |                                                               |                       |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ol style="list-style-type: none"> <li>2. The simulated PHD responds to the message with a "rors-cmip-confirmed-set".</li> <li>3. The simulated PHD sends a confirmed event report of the episodic scanner (MDC_NOTI_UNBUF_SCAN_REPORT_VAR) to the PHG under test:</li> <li>4. The PHG under test responds with a "rors-confirmed-event-report": <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ol> </li> <li>b. invoke-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = The same as the one sent by the simulated PHD.</li> </ol> </li> <li>c. obj-handle <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 21 &lt;Handle of the Episodic scanner&gt;</li> </ol> </li> <li>d. event-type (rors-confirmed-event-report) <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0D 0x24 (MDC_NOTI_UNBUF_SCAN_REPORT_VAR)</li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received messages in steps 1 and 4 must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                       |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/DIM/BV-039                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                       |
+| <b>TP label</b>          | EpiCfgScanner Class events. Unbuf-Scan-Report-MP-Var                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                       |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                       |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | EpiCfgScanEvent 16;C                                          | EpiCfgScanEvent 34; C |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If an Episodic Scanner uses Unbuf-Scan-Report-MP-Var Events to report updated data; and it reports data in confirmed mode, a PHG shall use a rors-cmip-confirmed-event-report operation to acknowledge the operation.</p> <p>[AND]</p> <p>If a PHG supports episodic scanners, it shall support all the events identified in Table 16 (Episodic configurable scanner object events).</p>                                                                                                                                                                                                                                                                                                                  |                                                               |                       |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND C_MAN_OXP_001 AND C_MAN_OXP_037                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                       |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                       |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                       |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Make the PHG under test set the OperationalState attribute of an Episodic Scanner of the simulated PHD to 1.</li> <li>2. The simulated PHD responds to the message with a "rors-cmip-confirmed-set".</li> <li>3. The simulated PHD sends a confirmed event report of the episodic scanner (MDC_NOTI_UNBUF_SCAN_REPORT_MP_VAR) to the PHG under test:</li> <li>4. The PHG under test responds with a "rors-confirmed-event-report": <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ol> </li> </ol> </li> </ol> |                                                               |                       |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>b. invoke-id</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = The same as the one sent by the simulated PHD.</li> </ul> <p>c. obj-handle</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 21 &lt;Handle of the Episodic scanner&gt;</li> </ul> <p>d. event-type (rors-confirmed-event-report)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0D 0x27 (MDC_NOTI_UNBUF_SCAN_REPORT_MP_VAR)</li> </ul> |
+| <b>Pass/Fail criteria</b> | The format of the received message must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                        |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/DIM/BV-040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                        |
+| <b>TP label</b>          | PeriCfgScanner Class events. Buf-Scan-Report-Var                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                        |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                        |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | PeriCfgScanEvent 4;C                                          | PeriCfgScanEvent 27; C |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If a Periodic Configurable Scanner uses Buf-Scan-Report-Var Events to report updated data; and it reports data in confirmed mode, a PHG shall use a rors-cmip-confirmed-event-report operation to acknowledge the operation.</p> <p>[AND]</p> <p>If a PHG supports periodic scanners, it shall support all the events identified in Table 18 (Periodic configurable scanner object events).</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                        |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND C_MAN_OXP_006                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                        |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                        |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                        |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Make the PHG under test set the OperationalState attribute of a periodic scanner of the simulated PHD to 1.</li> <li>2. The simulated PHD responds to the message with a "rors-cmip-confirmed-set".</li> <li>3. The simulated PHD sends a confirmed event report of the periodic scanner (MDC_NOTI_BUF_SCAN_REPORT_VAR) to the PHG under test:</li> <li>4. The PHG under test responds with a "rors-confirmed-event-report": <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ul> </li> <li>b. invoke-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = The same as the one sent by the simulated PHD.</li> </ul> </li> <li>c. obj-handle <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> </ul> </li> </ol> </li> </ol> |                                                               |                        |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> field-value = 20<Handle of the Periodic scanner><br>d. event-type (rors-confirmed-event-report) <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0D 0x2A (MDC_NOTI_BUF_SCAN_REPORT_VAR)</li> </ul> |
+| <b>Pass/Fail criteria</b> | The format of the received message must be the one specified.                                                                                                                                                                                                                                                                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                        |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|------------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/DIM/BV-041                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                        |
+| <b>TP label</b>           | PeriCfgScanner Class events. Buf-Scan-Report-MP-Var                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                        |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                        |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | PeriCfgScanEvent 16;C                                         | PeriCfgScanEvent 27; C |
+| <b>Test purpose</b>       | Check that:<br><br>If a Periodic Configurable Scanner uses Buf-Scan-Report-MP-Var Events to report updated data; and it reports data in confirmed mode, a PHG shall use a rors-cmip-confirmed-event-report operation to acknowledge the operation.<br><br>[AND]<br><br>If a PHG supports periodic scanners, it shall support all the events identified in Table 18 (Periodic configurable scanner object events).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                        |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_006 AND C_MAN_OXP_037                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                        |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                        |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                        |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test set the OperationalState attribute of an episodic scanner of the simulated PHD to 1.</li> <li>2. The simulated PHD responds to the message with a "rors-cmip-confirmed-set".</li> <li>3. The simulated PHD sends a confirmed event report of the periodic scanner (MDC_NOTI_BUF_SCAN_REPORT_MP_VAR) to the PHG under test:</li> <li>4. The PHG under test responds with a "rors-confirmed-event-report":           <ol style="list-style-type: none"> <li>a. APDU Type               <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ul> </li> <li>b. invoke-id               <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = The same as the one sent by the simulated PHD.</li> </ul> </li> <li>c. obj-handle               <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 20 &lt;Handle of the Periodic scanner&gt;</li> </ul> </li> <li>d. event-type (rors-confirmed-event-report)               <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0D 0x2D (MDC_NOTI_BUF_SCAN_REPORT_MP_VAR)</li> </ul> </li> </ol> </li> </ol> |                                                               |                        |
+| <b>Pass/Fail criteria</b> | The format of the received message must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                        |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                       |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/DIM/BV-042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                       |
+| <b>TP label</b>           | EpiCfgScanner Class events. Unbuf-Scan-Report-Fixed                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                       |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                       |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | EpiCfgScanEvent 8; C                                          | EpiCfgScanEvent 34; C |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>If an Episodic Scanner uses Unbuf-Scan-Report-Fixed Events to report updated data; and it reports data in confirmed mode, a PHG shall use a rors-cmip-confirmed-event-report operation to acknowledge the operation.</p> <p>[AND]</p> <p>If a PHG supports episodic scanners, it shall support all the events identified in Table 16 (Episodic configurable scanner object events).</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                       |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_001                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                       |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                       |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                       |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test set the OperationalState attribute of an episodic scanner of the simulated PHD to 1.</li> <li>2. The simulated PHD responds to the message with a "rors-cmip-confirmed-set".</li> <li>3. The simulated PHD sends a confirmed event report of the episodic scanner (MDC_NOTI_UNBUF_SCAN_REPORT_FIXED) to the PHG under test:</li> <li>4. The PHG under test responds with a "rors-confirmed-event-report": <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ul> </li> <li>b. invoke-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = The same as the one sent by the simulated PHD.</li> </ul> </li> <li>c. obj-handle <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 21 &lt;Handle of the Episodic scanner&gt;</li> </ul> </li> <li>d. event-type (rors-confirmed-event-report) <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0D 0x24 (MDC_NOTI_UNBUF_SCAN_REPORT_FIXED)</li> </ul> </li> </ol> </li> </ol> |                                                               |                       |
+| <b>Pass/Fail criteria</b> | The format of the received messages in steps 1 and 4 must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                       |
+
+|                     |                                                        |                                                               |                       |
+|---------------------|--------------------------------------------------------|---------------------------------------------------------------|-----------------------|
+| <b>TP Id</b>        | TP/PLT/PHG/OXP/DIM/BV-043                              |                                                               |                       |
+| <b>TP label</b>     | EpiCfgScanner Class events. Unbuf-Scan-Report-MP-Fixed |                                                               |                       |
+| <b>Coverage</b>     | <b>Spec</b>                                            | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                       |
+|                     | <b>Testable items</b>                                  | EpiCfgScanEvent 20;C                                          | EpiCfgScanEvent 34; C |
+| <b>Test purpose</b> | Check that:                                            |                                                               |                       |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>If an Episodic Scanner uses Unbuf-Scan-Report-MP-Fixed Events to report updated data; and it reports data in confirmed mode, a PHG shall use a rors-cmip-confirmed-event-report operation to acknowledge the operation.</p> <p>[AND]</p> <p>If a PHG supports episodic scanners, it shall support all the events identified in Table 16 (Episodic configurable scanner object events).</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_001 AND C_MAN_OXP_037                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test set the OperationalState attribute of an episodic scanner of the simulated PHD to 1.</li> <li>2. The simulated PHD responds to the message with a "rors-cmip-confirmed-set".</li> <li>3. The simulated PHD sends a confirmed event report of the episodic scanner (MDC_NOTI_UNBUF_SCAN_REPORT_MP_FIXED) to the PHG under test:</li> <li>4. The PHG under test responds with a "rors-confirmed-event-report": <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ol> </li> <li>b. invoke-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = The same as the one sent by the simulated PHD.</li> </ol> </li> <li>c. obj-handle <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 21 &lt;Handle of the Episodic scanner&gt;</li> </ol> </li> <li>d. event-type (rors-confirmed-event-report) <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0D 0x27 (MDC_NOTI_UNBUF_SCAN_REPORT_MP_FIXED)</li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                        |
+|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|------------------------|
+| <b>TP Id</b>         | TP/PLT/PHG/OXP/DIM/BV-044                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                        |
+| <b>TP label</b>      | PeriCfgScanner Class events. Buf-Scan-Report-Fixed                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                        |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                        |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                    | PeriCfgScanEvent 8;C                                          | PeriCfgScanEvent 27; C |
+| <b>Test purpose</b>  | <p>Check that:</p> <p>If an Periodic Configurable Scanner uses Buf-Scan-Report-Fixed Events to report updated data; and it reports data in confirmed mode, a PHG shall use a rors-cmip-confirmed-event-report operation to acknowledge the operation.</p> <p>[AND]</p> <p>If a PHG supports periodic scanners, it shall support all the events identified in Table 18 (Periodic configurable scanner object events).</p> |                                                               |                        |
+| <b>Applicability</b> | C_MAN_OXP_000 AND C_MAN_OXP_006                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                        |
+| <b>Other PICS</b>    |                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                        |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test set the OperationalState attribute of a periodic scanner of the simulated PHD to 1.</li> <li>2. The simulated PHD responds to the message with a "rors-cmip-confirmed-set".</li> <li>3. The simulated PHD sends a confirmed event report of the periodic scanner (MDC_NOTI_BUF_SCAN_REPORT_FIXED) to the PHG under test:</li> <li>4. The PHG under test responds with a "rors-confirmed-event-report": <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ol> </li> <li>b. invoke-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = The same as the one sent by the simulated PHD.</li> </ol> </li> <li>c. obj-handle <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 20&lt;Handle of the Periodic scanner&gt;</li> </ol> </li> <li>d. event-type (rors-confirmed-event-report) <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0D 0x2A (MDC_NOTI_BUF_SCAN_REPORT_FIXED)</li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                        |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/DIM/BV-045                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                        |
+| <b>TP label</b>          | PeriCfgScanner Class events. Buf-Scan-Report-MP-Fixed                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                        |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                        |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | PeriCfgScanEvent 20;C                                         | PeriCfgScanEvent 27; C |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If an Periodic Configurable Scanner uses Buf-Scan-Report-MP-Fixed Events to report updated data; and it reports data in confirmed mode, a PHG shall use a rors-cmip-confirmed-event-report operation to acknowledge the operation.</p> <p>[AND]</p> <p>If a PHG supports periodic scanners, it shall support all the events identified in Table 18 (Periodic configurable scanner object events).</p>                                                                                                                             |                                                               |                        |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND C_MAN_OXP_006 AND C_MAN_OXP_037                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                        |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                        |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                        |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Make the PHG under test set the OperationalState attribute of an episodic scanner of the simulated PHD to 1.</li> <li>2. The simulated PHD responds to the message with a "rors-cmip-confirmed-set".</li> <li>3. The simulated PHD sends a confirmed event report of the periodic scanner (MDC_NOTI_BUF_SCAN_REPORT_MP_FIXED) to the PHG under test:</li> <li>4. The PHG under test responds with a "rors-confirmed-event-report": <ol style="list-style-type: none"> <li>a. APDU Type</li> </ol> </li> </ol> |                                                               |                        |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ul> <p>b. invoke-id</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = The same as the one sent by the simulated PHD.</li> </ul> <p>c. obj-handle</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 20 &lt;Handle of the Periodic scanner&gt;</li> </ul> <p>d. event-type (rors-confirmed-event-report)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0D 0x2D (MDC_NOTI_BUF_SCAN_REPORT_MP_FIXED)</li> </ul> |
+| <b>Pass/Fail criteria</b> | The format of the received message must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/DIM/BV-046                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |
+| <b>TP label</b>          | Scan Handle List - Fixed & Variable format event report                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | ScanClassAttr 5;M                                             |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If the Scan-Handle-List attribute is included in the [Scanner object], the PHG shall not assume the order of the objects contained in the event reports is the same as the order of the Scan-Handle-List.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND (C_MAN_OXP_001 OR C_MAN_OXP_006) AND<br>(C_MAN_OXP_016 OR C_MAN_OXP_018 OR C_MAN_OXP_019 OR C_MAN_OXP_020<br>OR C_MAN_OXP_026 OR C_MAN_OXP_027 OR C_MAN_OXP_030 OR<br>C_MAN_OXP_067 OR C_MAN_OXP_071 OR (C_MAN_OXP_022 AND (C_MAN_ST_001<br>OR C_MAN_ST_002 OR C_MAN_ST_003 OR C_MAN_ST_004 OR C_MAN_ST_005 OR<br>C_MAN_ST_006 OR C_MAN_ST_007)) OR (MAN_OXP_023 AND (C_MAN_CV_001 OR<br>C_MAN_CV_002 OR C_MAN_CV_003 OR C_MAN_CV_004 OR C_MAN_CV_005 OR<br>C_MAN_CV_006 OR C_MAN_CV_007 OR C_MAN_CV_008 OR C_MAN_CV_009 OR<br>C_MAN_CV_010 OR C_MAN_CV_011 OR C_MAN_CV_012 OR C_MAN_CV_013 OR<br>C_MAN_CV_014 OR C_MAN_CV_015 OR C_MAN_CV_016 OR C_MAN_CV_017 OR<br>C_MAN_CV_018 OR C_MAN_CV_019 OR C_MAN_CV_020 OR C_MAN_CV_021 OR<br>C_MAN_CV_022 OR C_MAN_CV_023 OR C_MAN_CV_024 OR C_MAN_CV_025 OR<br>C_MAN_CV_026 OR C_MAN_CV_027 OR C_MAN_CV_028 OR C_MAN_CV_029)) |                                                               |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Operating state using the extended configuration that contains at least two metric objects and one scanner object.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Make the PHG under test set the OperationalState attribute of a periodic scanner or episodic scanner, whichever is supported by the PHG, of the simulated PHD to 1.</li> <li>2. The simulated PHD responds to the message with a "rors-cmip-confirmed-set".</li> <li>3. The simulated PHD sends a Confirmed Variable Scanner object report of the periodic/episodic scanner (MDC_NOTI_BUF_SCAN_REPORT_VAR/MDC_NOTI_UNBUF_SCAN_REPORT_VAR) to the PHG under test. The order of the objects in the Variable Scanner Object Event is different from the order established in Scan-Handle-List attribute.</li> <li>4. The PHG under test responds with a "rors-confirmed-event-report".</li> </ol>                                                                                                                                                    |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>5. The simulated PHD sends a Confirmed Fixed Scanner object of the periodic/episodic scanner (MDC_NOTI_BUF_SCAN_REPORT_FIXED/ MDC_NOTI_UNBUF_SCAN_REPORT_FIXED) to the PHG under test. The order of the objects in the Fixed Scanner Event report is different from the order established in the Scan-Handle-List attribute.</p> <p>6. The PHG under test responds with a "rors-confirmed-event-report":</p> |
+| <b>Pass/Fail criteria</b> | Verify that the PHG under test is able to accept the data and assign the measurements correctly to every object when it receives the Scanner Object Event Report in step 4 and step 6.                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/DIM/BV-047                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |
+| <b>TP label</b>           | Not configuring a real-time clock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | AbsTime 7;M                                                   |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>In this case, neither the mds-time-mgr-set-time nor the mds-time-capab-set-clock bits shall be set and the PHG shall not attempt to set the clock.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |
+| <b>Other PICS</b>         | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Unassociated state. The PHD has the MDSTimeInfo attribute with the mds-time-mgr-set-time and mds-time-capab-set-clock bits set to 0.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test.</li> <li>2. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN: <ol style="list-style-type: none"> <li>a. IF the PHG sends a GET request while it is in the Configuring state, the simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>b. Wait until the Operating state is reached.</li> <li>c. If the PHG under test did not set automatically the GET Mds in the Configuring state, force the PHG to request MDS attributes.</li> <li>d. The simulated PHD sends rors-cmip-get with MDS attributes.</li> </ol> </li> <li>3. IF C_MAN_OXP_085 THEN: <ol style="list-style-type: none"> <li>a. PHG sends a GET request while it is in Configuring/Sending GetMDS state, and simulated PHD sends rors-cmip-get with MDS attributes.</li> </ol> </li> <li>4. The PHG under test shall not set the time of the simulated PHD.</li> </ol> |                                                               |
+| <b>Pass/Fail criteria</b> | Verify that the PHG does not send the Set-Time message.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |
+
+|                      |                                                                                                                                     |                                                               |
+|----------------------|-------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>         | TP/PLT/PHG/OXP/DIM/BV-048                                                                                                           |                                                               |
+| <b>TP label</b>      | Not supported specialization - Glucose meter                                                                                        |                                                               |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                         | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                      | <b>Testable items</b>                                                                                                               | ManagerProc 3;M                                               |
+| <b>Test purpose</b>  | <p>Check that:</p> <p>A specialization declared by the vendor as "not supported" is really not supported by the PHG under test.</p> |                                                               |
+| <b>Applicability</b> | C_MAN_OXP_000 AND NOT(C_MAN_OXP_055)                                                                                                |                                                               |
+| <b>Other PICS</b>    |                                                                                                                                     |                                                               |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with the dev-config-id set to 0x06 0xA4 (glucose meter).</li> <li>2. IF the PHG under test responds with an Association Response (rejected-*) or an Abort, THEN:           <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>b. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>3. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN the simulated PHD sends a configuration event report with the config-report-id set to 0x06 0xA4 and including the glucose meter standard configuration objects.           <ol style="list-style-type: none"> <li>a. IF the PHG under test responds with a rors-cmip-confirmed-event-report (unsupported-config) or a Release Request or Abort THEN               <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THENthe PHG shall not move to Operating state and the Test Procedure ends.</li> <li>ii. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>b. IF the PHG under test responds with a rors-cmip-confirmed-event-report (accepted-config) THEN               <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state</li> <li>ii. IF C_MAN_OXP_085 THEN:                   <ul style="list-style-type: none"> <li>❑ The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>❑ The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>❑ The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li>❑ The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> </li> <li>iii. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration:                   <ul style="list-style-type: none"> <li>❑ If the PHG under test responds with a roer, roj, rlrq or Abort then the test procedure ends.</li> <li>❑ If the PHG under test responds with a rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the test procedure ends.</li> </ul> </li> </ol> </li> </ol> </li> <li>4. IF the PHG under test responds with an Association Response (accepted) THEN:           <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>b. IF C_MAN_OXP_085 THEN:               <ol style="list-style-type: none"> <li>i. The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>ii. The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>iii. The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li>iv. The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ol> </li> <li>c. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration:               <ol style="list-style-type: none"> <li>i. If PHG under test responds with roer, roj, rlrq or Abort then Test Procedure ends.</li> </ol> </li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>ii. If PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends</p>                                                                                                                                                                                                   |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>In step 2 or step 3.a, the PHG does not move to the Operating state (2.a and 3.a.i) or Configuring/Sending GetMDS (2.b and 3.a.ii).</li> <li>In step 3.b or step 4, the PHG does not accept the received measurement or if PHG accepts the measurement then it shall not store or display the received measurement.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHG/OPX/DIM/BV-049                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+| <b>TP label</b>          | Not supported specialization - Blood Pressure Monitor                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | ManagerProc 3;M                                               |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>A specialization declared by the vendor as "not supported" is really not supported by the PHG under test.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_056)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |  |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHD sends an Association Request to the PHG under test with dev-config-id set to 0x02 0xBC (blood pressure monitor).</li> <li>IF the PHG under test responds with an Association Response (rejected-*) or an Abort, THEN: <ol style="list-style-type: none"> <li>IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to the Operating state and the test procedure ends.</li> <li>IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN the simulated PHD sends a configuration event report with config-report-id set to 0x02 0xBC and including blood pressure monitor standard configuration objects. <ol style="list-style-type: none"> <li>IF the PHG under test responds with a rors-cmip-confirmed-event-report (unsupported-config) or a Release Request or Abort THEN: <ol style="list-style-type: none"> <li>IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>IF the PHG under test responds with a rors-cmip-confirmed-event-report (accepted-config) THEN: <ol style="list-style-type: none"> <li>IF C_MAN_OXP_084 OR C_MAN_OXP_085 THEN the PHG moves to the Operating state,</li> <li>IF C_MAN_OXP_085: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li><input type="checkbox"/> The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li><input type="checkbox"/> The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> </li> </ol> </li> </ol> </li> <li>The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration:</li> </ol> |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> If the PHG under test responds with a roer, rorj, rlrq or Abort then the test procedure ends.</li> <li><input type="checkbox"/> If the PHG under test responds with a rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the test procedure ends.</li> </ul> <p>4. IF the PHG under test responds with an Association Response (accepted) THEN:</p> <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>b. IF C_MAN_OXP_085 THEN:           <ol style="list-style-type: none"> <li>i. The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>ii. The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>iii. The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li>iv. The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ol> </li> <li>c. simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration:           <ol style="list-style-type: none"> <li>i. If the PHG under test responds with a roer, rorj, rlrq or Abort then the test procedure ends.</li> <li>ii. If the PHG under test responds with a rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the test procedure ends.</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2 or step 3.a, the PHG does not move to the Operating state (2.a and 3.a.i) or Configuring/Sending GetMDS (2.b and 3.a.ii).</li> <li>• In step 3.b or step 4, the PHG does not accept the received measurement or if the PHG accepts the measurement then it shall not store or display the received measurement.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/DIM/BV-050                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+| <b>TP label</b>          | Not supported specialization - Independent living activity hub                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | ManagerProc 3;M                                               |
+| <b>Test purpose</b>      | Check that:<br>A specialization declared by the vendor as "not supported" is really not supported by the PHG under test.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_057)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with the dev-config-id set to an extended Config-Id.</li> <li>2. IF the PHG under test responds with an Association Response (rejected-*) or an Abort, THEN:           <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to the Operating state and the test procedure ends.</li> <li>b. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> </ol> |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>3. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN simulated PHD sends a configuration event report including an extended configuration for the independent living activity hub.</p> <ol style="list-style-type: none"> <li>IF the PHG under test responds with rors-cmip-confirmed-event-report (unsupported-config) or a Release Request or an Abort THEN: <ol style="list-style-type: none"> <li>IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>IF the PHG under test responds with a rors-cmip-confirmed-event-report (accepted-config) THEN: <ol style="list-style-type: none"> <li>IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>IF C_MAN_OXP_085 THEN: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li><input type="checkbox"/> The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li><input type="checkbox"/> The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> </li> <li>The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration for every object present in the configuration: <ul style="list-style-type: none"> <li><input type="checkbox"/> If PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li><input type="checkbox"/> If PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure end</li> </ul> </li> </ol> </li> </ol> <p>4. IF the PHG under test responds with an Association Response (accepted) THEN:</p> <ol style="list-style-type: none"> <li>IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to the Operating state.</li> <li>IF C_MAN_OXP_085 THEN: <ol style="list-style-type: none"> <li>The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li>The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ol> </li> <li>The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration for every object present in the configuration: <ol style="list-style-type: none"> <li>If PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li>If PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends.</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2 or step 3.a, the PHG does not move to the Operating state (2.a and 3.a.i) or Configuring/Sending GetMDS (2.b and 3.a.ii).</li> <li>• In step 3.b or step 4, the PHG does not accept the received measurement or if the PHG accepts the measurement then it shall not store or display the received measurement.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHG/OPX/DIM/BV-051                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>TP label</b>          | Not supported specialization - Strength fitness equipment                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | ManagerProc 3;M                                               |  |
+| <b>Test purpose</b>      | Check that:<br>A specialization declared by the vendor as "not supported" is really not supported by the PHG under test.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_058)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with the dev-config-id set to an extended Config-Id.</li> <li>2. IF the PHG under test responds with an Association Response (rejected-*) or an Abort, THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>b. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>3. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN the simulated PHD sends a configuration event report including an extended configuration for the strength fitness equipment. <ol style="list-style-type: none"> <li>a. IF the PHG under test responds with a rors-cmip-confirmed-event-report (unsupported-config) or Release Request or an Abort THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>ii. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS state and the Test Procedure ends.</li> </ol> </li> <li>b. IF PHG under test responds with rors-cmip-confirmed-event-report (accepted-config) THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>ii. IF C_MAN_OXP_085 THEN: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li><input type="checkbox"/> The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li><input type="checkbox"/> The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> </li> <li>iii. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ul style="list-style-type: none"> <li><input type="checkbox"/> If PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li><input type="checkbox"/> If PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure end.</li> </ul> </li> </ol> </li> </ol> </li> <li>4. IF the PHG under test responds with an Association Response (accepted) THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>b. IF C_MAN_OXP_085 THEN:</li> </ol> </li> </ol> |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ol style="list-style-type: none"> <li>i. The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>ii. The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>iii. The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li>iv. The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ol> <p>c. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration:</p> <ol style="list-style-type: none"> <li>i. If PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li>ii. If PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2 or step 3.a, the PHG does not move to the Operating state (2.a and 3.a.i) or Configuring/Sending GetMDS (2.b and 3.a.ii).</li> <li>• In step 3.b or step 4, the PHG does not accept the received measurement or if the PHG accepts the measurement then it shall not store or display the received measurement.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/DIM/BV-052                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+| <b>TP label</b>          | Not supported specialization - Cardiovascular fitness and activity monitor                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ManagerProc 3;M                                               |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>A specialization declared by the vendor as "not supported" is really not supported by the PHG under test.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_059)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with the dev-config-id set to an extended Config-Id.</li> <li>2. IF the PHG under test responds with an Association Response (rejected-*) or an Abort, THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>b. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>3. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN the simulated PHD sends a configuration event report including an extended configuration for the cardiovascular fitness and activity monitor. <ol style="list-style-type: none"> <li>a. IF the PHG under test responds with a rors-cmip-confirmed-event-report (unsupported-config) or Release Request or an Abort THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>ii. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>b. IF PHG under test responds with rors-cmip-confirmed-event-report (accepted-config) THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> </ol> </li> </ol> </li> </ol> |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>ii. IF C_MAN_OXP_085 THEN: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li><input type="checkbox"/> The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li><input type="checkbox"/> The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> </li> <li>iii. simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ul style="list-style-type: none"> <li><input type="checkbox"/> If the PHG under test responds with a roer, rorj, rlrq or an Abort then the test procedure ends.</li> <li><input type="checkbox"/> If the PHG under test responds with a rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the test procedure ends.</li> </ul> </li> </ul> <p>4. IF the PHG under test responds with an Association Response (accepted) THEN:</p> <ul style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>b. IF C_MAN_OXP_085 THEN: <ul style="list-style-type: none"> <li>i. The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>ii. The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>iii. The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li>iv. The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> </li> <li>c. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ul style="list-style-type: none"> <li>i. If the PHG under test responds with a roer, rorj, rlrq or an Abort then the test procedure ends.</li> <li>ii. If the PHG under test responds with a rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the test procedure ends.</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>In step 2 or step 3.a, the PHG does not move to the Operating state (2.a and 3.a.i) or Configuring/Sending GetMDS (2.b and 3.a.ii).</li> <li>In step 3.b or step 4, the PHG does not accept the received measurement or if the PHG accepts the measurement then it shall not store or display the received measurement.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                          |                                                                                                                                     |                                                               |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/DIM/BV-053                                                                                                           |                                                               |  |
+| <b>TP label</b>          | Not supported specialization - Weighing scale                                                                                       |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                         | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                               | ManagerProc 3;M                                               |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>A specialization declared by the vendor as "not supported" is really not supported by the PHG under test.</p> |                                                               |  |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_060)                                                                                                |                                                               |  |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                         |                                                               |  |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                             |                                                               |  |
+
+|                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <p><b>Test procedure</b></p> | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with the dev-config-id set to 0x05 0xDC (weighing scales).</li> <li>2. IF the PHG under test responds with an Association Response (rejected-*) or an Abort, THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>b. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>3. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN the simulated PHD sends a configuration event report with the config-report-id set to 0x05 0xDC and including weighing scales standard configuration objects. <ol style="list-style-type: none"> <li>a. IF the PHG under test responds with rors-cmip-confirmed-event-report (unsupported-config) or Release Request or Abort THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>ii. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>b. IF the PHG under test responds with rors-cmip-confirmed-event-report (accepted-config) THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>ii. IF C_MAN_OXP_085 THEN: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li><input type="checkbox"/> The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li><input type="checkbox"/> The simulated PHD responds to the PHG under test so it moves to Operating..</li> </ul> </li> <li>iii. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ul style="list-style-type: none"> <li><input type="checkbox"/> If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li><input type="checkbox"/> If the PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure end.</li> </ul> </li> </ol> </li> </ol> </li> <li>4. IF the PHG under test responds with an Association Response (accepted) THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>b. IF C_MAN_OXP_085 THEN: <ol style="list-style-type: none"> <li>i. The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>ii. The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>iii. The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li>iv. The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ol> </li> <li>c. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ol style="list-style-type: none"> <li>i. If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li>ii. If the PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends.</li> </ol> </li> </ol> </li> </ol> |
+|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>In step 2 or step 3.a, the PHG does not move to the Operating state (2.a and 3.a.i) or Configuring/Sending GetMDS (2.b and 3.a.ii).</li> <li>In step 3.b or step 4, the PHG does not accept the received measurement or if the PHG accepts the measurement then it shall not store or display the received measurement.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OPX/DIM/BV-054                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |
+| <b>TP label</b>          | Not supported specialization - Thermometer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | ManagerProc 3;M                                               |
+| <b>Test purpose</b>      | Check that:<br>A specialization declared by the vendor as "not supported" is really not supported by the PHG under test.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_061)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHD sends an Association Request to the PHG under test with the dev-config-id set to 0x03 0x20 (thermometer).</li> <li>IF the PHG under test responds with an Association Response (rejected-*) or an Abort, THEN: <ol style="list-style-type: none"> <li>IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN the simulated PHD sends a configuration event report with the config-report-id set to 0x03 0x20 and including thermometer standard configuration objects. <ol style="list-style-type: none"> <li>IF the PHG under test responds with rors-cmip-confirmed-event-report (unsupported-config) or Release Request or Abort THEN: <ol style="list-style-type: none"> <li>IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>IF the PHG under test responds with rors-cmip-confirmed-event-report (accepted-config) THEN: <ol style="list-style-type: none"> <li>IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>IF C_MAN_OXP_085 THEN: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li><input type="checkbox"/> The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li><input type="checkbox"/> The simulated PHD responds to the PHG under test so it moves to Operating..</li> </ul> </li> <li>The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ul style="list-style-type: none"> <li><input type="checkbox"/> If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> If the PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure end</li> </ul> <p>4. IF the PHG under test responds with an Association Response (accepted) THEN:</p> <ul style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>b. IF C_MAN_OXP_085 THEN: <ul style="list-style-type: none"> <li>i. The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>ii. The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>iii. The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li>iv. The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> </li> <li>c. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ul style="list-style-type: none"> <li>i. If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li>ii. If the PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends.</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2 or step 3.a, the PHG does not move to the Operating state (2.a and 3.a.i) or Configuring/Sending GetMDS (2.b and 3.a.ii).</li> <li>• In step 3.b or step 4, the PHG does not accept the received measurement or if the PHG accepts the measurement then it shall not store or display the received measurement.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/DIM/BV-055                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+| <b>TP label</b>          | Not supported specialization - Pulse Oximeter                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable Items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ManagerProc 3;M                                               |
+| <b>Test purpose</b>      | Check that:<br>A specialization declared by the vendor as "not supported" is really not supported by the PHG under test.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_062)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with the dev-config-id set to 0x01 0x90 (pulse oximeter).</li> <li>2. IF the PHG under test responds with an Association Response (rejected-*) or an Abort, THEN: <ul style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>b. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ul> </li> <li>3. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN the simulated PHD sends a configuration event report with the config-report-id set to 0x01 0x90 and including the pulse oximeter standard configuration objects. <ul style="list-style-type: none"> <li>a. IF the PHG under test responds with rors-cmip-confirmed-event-report (unsupported-config) or Release Request or Abort THEN: </li> </ul> </li> </ol> |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>ii. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> <ol style="list-style-type: none"> <li>b. IF the PHG under test responds with rors-cmip-confirmed-event-report (accepted-config) THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>ii. IF C_MAN_OXP_085 THEN: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li><input type="checkbox"/> The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li><input type="checkbox"/> The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> </li> <li>iii. The simulated PHD sends a unconfirmed fixed event report with one measurement for every object present in the configuration: <ul style="list-style-type: none"> <li><input type="checkbox"/> If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li><input type="checkbox"/> If time-out expires and no message is received PHG shall not store or display the received measurement and the Test Procedure end</li> </ul> </li> </ol> </li> </ol> <ol style="list-style-type: none"> <li>4. IF the PHG under test responds with an Association Response (accepted) THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>b. IF C_MAN_OXP_085 THEN: <ol style="list-style-type: none"> <li>i. The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>ii. The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>iii. The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li>iv. The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ol> </li> <li>c. The simulated PHD sends a unconfirmed fixed event report with one measurement for every object present in the configuration: <ol style="list-style-type: none"> <li>i. If PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li>ii. If time-out expires and no message is received PHG shall not store or display the received measurement and the Test Procedure ends.</li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2 or step 3.a, the PHG does not move to Operating state (2.a and 3.a.i) or Configuring/Sending GetMDS (2.b and 3.a.ii).</li> <li>• In step 3.b or step 4, the PHG does not accept the received measurement or if the PHG accepts the measurement then it shall not store or display the received measurement.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                     |                                                  |                                                               |  |
+|---------------------|--------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>        | TP/PLT/PHG/OXP/DIM/BV-056                        |                                                               |  |
+| <b>TP label</b>     | Not supported specialization - Adherence Monitor |                                                               |  |
+| <b>Coverage</b>     | <b>Spec</b>                                      | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                     | <b>Testable items</b>                            | ManagerProc 3;M                                               |  |
+| <b>Test purpose</b> | Check that:                                      |                                                               |  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | A specialization declared by the vendor as "not supported" is really not supported by the PHG under test.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_052)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with the dev-config-id set to 0x1C 0x20 (adherence monitor).</li> <li>2. IF the PHG under test responds with an Association Response (rejected-*) or an Abort, THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>b. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>3. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN the simulated PHD sends a configuration event report with the config-report-id set to 0x1C 0x20 and including the adherence monitor standard configuration objects. <ol style="list-style-type: none"> <li>a. IF the PHG under test responds with rors-cmip-confirmed-event-report (unsupported-config) or Release Request or Abort THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>ii. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>b. IF the PHG under test responds with rors-cmip-confirmed-event-report (accepted-config) THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>ii. IF C_MAN_OXP_085 THEN: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li><input type="checkbox"/> The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li><input type="checkbox"/> The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> </li> <li>iii. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ul style="list-style-type: none"> <li><input type="checkbox"/> If PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li><input type="checkbox"/> If PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure end</li> </ul> </li> </ol> </li> </ol> </li> <li>4. IF the PHG under test responds with an Association Response (accepted) THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>b. IF C_MAN_OXP_085 THEN: <ol style="list-style-type: none"> <li>i. The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>ii. The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>iii. The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li>iv. The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ol> </li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>c. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration:</p> <ol style="list-style-type: none"> <li>i. If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li>ii. If the PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2 or step 3.a, the PHG does not move to the Operating state (2.a and 3.a.i) or Configuring/Sending GetMDS (2.b and 3.a.ii).</li> <li>• In step 3.b or step 4, the PHG does not accept the received measurement or if the PHG accepts the measurement then it shall not store or display the received measurement.</li> </ul>                                                                                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHG/OPX/DIM/BV-058                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>TP label</b>          | Not supported specialization - Peak Flow                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ManagerProc 3;M                                               |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>A specialization declared by the vendor as "not supported" is really not supported by the PHG under test.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_054)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |
+| <b>Initial condition</b> | The simulated PHD and PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with the dev-config-id set to 0x08 0x34 (peak flow).</li> <li>2. IF the PHG under test responds with an Association Response (rejected-*) or an Abort, THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>b. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>3. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN the simulated PHD sends a configuration event report with the config-report-id set to 0x08 0x34 and including the peak flow standard configuration objects. <ol style="list-style-type: none"> <li>a. IF the PHG under test responds with rors-cmip-confirmed-event-report (unsupported-config) or Release Request or Abort THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>ii. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>b. IF the PHG under test responds with rors-cmip-confirmed-event-report (accepted-config) THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>ii. IF C_MAN_OXP_085 THEN: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li><input type="checkbox"/> The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li> <ul style="list-style-type: none"> <li><input type="checkbox"/> The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> </li> <li>iii. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ul style="list-style-type: none"> <li><input type="checkbox"/> If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li><input type="checkbox"/> If the PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure end</li> </ul> </li> <li>4. IF the PHG under test responds with an Association Response (accepted) THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>b. IF C_MAN_OXP_085 THEN: <ol style="list-style-type: none"> <li>i. The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>ii. The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>iii. The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li>iv. The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ol> </li> <li>c. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ol style="list-style-type: none"> <li>i. If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li>ii. If the PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends.</li> </ol> </li> </ol> </li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2 or step 3.a, the PHG does not move to the Operating state (2.a and 3.a.i) or Configuring/Sending GetMDS (2.b and 3.a.ii).</li> <li>• In step 3.b or step 4, the PHG does not accept the received measurement or if the PHG accepts the measurement then it shall not store or display the received measurement.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHG/EXP/DIM/BV-059                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |  |
+| <b>TP label</b>          | Not supported specialization - Body Composition Analyser                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                      | ManagerProc 3;M                                               |  |
+| <b>Test purpose</b>      | Check that:<br>A specialization declared by the vendor as "not supported" is really not supported by the PHG under test.                                                                                                                                                                                                                                                                                                                                                   |                                                               |  |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_051)                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with the dev-config-id set to 0x07 0xD0 (body composition analyser).</li> <li>2. IF the PHG under test responds with an Association Response (rejected-*) or an Abort, THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> </ol> </li> </ol> |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p style="margin-left: 40px;">b. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</p> <p>3. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN the simulated PHD sends a configuration event report with the config-report-id set to 0x07 0xD0 and including the body composition analyser configuration objects.</p> <p style="margin-left: 20px;">a. IF the PHG under test responds with rors-cmip-confirmed-event-report (unsupported-config) or Release Request or Abort THEN:</p> <p style="margin-left: 40px;">i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</p> <p style="margin-left: 40px;">ii. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS and the Test Procedure ends..</p> <p style="margin-left: 20px;">b. IF the PHG under test responds with rors-cmip-confirmed-event-report (accepted-config) THEN:</p> <p style="margin-left: 40px;">i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</p> <p style="margin-left: 40px;">ii. IF C_MAN_OXP_085 THEN:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li><input type="checkbox"/> The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li><input type="checkbox"/> The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> <p style="margin-left: 40px;">iii. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li><input type="checkbox"/> If the PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure end</li> </ul> <p>4. IF the PHG under test responds with an Association Response (accepted) THEN:</p> <p style="margin-left: 20px;">a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</p> <p style="margin-left: 20px;">b. IF C_MAN_OXP_085 THEN:</p> <ul style="list-style-type: none"> <li>i. The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>ii. The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>iii. The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li>iv. The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> <p style="margin-left: 20px;">c. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration:</p> <ul style="list-style-type: none"> <li>i. If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li>ii. If the PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends.</li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2 or step 3.a, the PHG does not move to the Operating state (2.a and 3.a.i) or Configuring/Sending GetMDS (2.b and 3.a.ii).</li> <li>• In step 3.b or step 4, the PHG does not accept the received measurement or if the PHG accepts the measurement then it shall not store or display the received measurement.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|              |  |
+|--------------|--|
+| <b>Notes</b> |  |
+|--------------|--|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHG/OPX/DIM/BV-060                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+| <b>TP label</b>          | Not supported specialization - Basic ECG specialization/Heart Rate profile                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | ManagerProc 3;M                                               |  |
+| <b>Test purpose</b>      | Check that:<br>A specialization declared by the vendor as "not supported" is really not supported by the PHG under test.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_064)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |  |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with the dev-config-id set to 0x02 0x58 (heart rate profile).</li> <li>2. IF the PHG under test responds with an Association Response (rejected-*) or an Abort, THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>b. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>3. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN the simulated PHD sends a configuration event report with the config-report-id set to 0x02 0x58 and including the Heart Rate Profile configuration objects. <ol style="list-style-type: none"> <li>a. IF the PHG under test responds with rors-cmip-confirmed-event-report (unsupported-config) or Release Request or Abort THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>ii. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>b. IF the PHG under test responds with rors-cmip-confirmed-event-report (accepted-config) THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>ii. IF C_MAN_OXP_085 THEN: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li><input type="checkbox"/> The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li><input type="checkbox"/> The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> </li> <li>iii. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ul style="list-style-type: none"> <li><input type="checkbox"/> If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li><input type="checkbox"/> If the PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure end</li> </ul> </li> </ol> </li> </ol> </li> <li>4. IF the PHG under test responds with an Association Response (accepted) THEN:</li> </ol> |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>b. IF C_MAN_OXP_085 THEN: <ol style="list-style-type: none"> <li>i. The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>ii. The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>iii. The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li>iv. The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ol> </li> <li>c. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ol style="list-style-type: none"> <li>i. If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li>ii. If the PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends.</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2 or step 3.a, the PHG does not move to the Operating state (2.a and 3.a.i) or Configuring/Sending GetMDS (2.b and 3.a.ii).</li> <li>• In step 3.b or step 4, the PHG does not accept the received measurement or if the PHG accepts the measurement then it shall not store or display the received measurement.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/DIM/BV-061                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |
+| <b>TP label</b>          | Not supported specialization - Basic ECG specialization/Simple ECG profile                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | ManagerProc 3;M                                               |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>A specialization declared by the vendor as "not supported" is really not supported by the PHG under test.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_065)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with the dev-config-id set to an extended Config-Id.</li> <li>2. IF the PHG under test responds with an Association Response (rejected-*) or an Abort, THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>b. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>3. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN the simulated PHD sends a configuration event report including an extended configuration for the Simple ECG Profile (one RT-SA object for the ECG Waveform and one scanner referenced to RT-SA): <ol style="list-style-type: none"> <li>a. IF PHG under test responds with rors-cmip-confirmed-event-report (unsupported-config) or Release Request or Abort THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>ii. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> </ol> </li> </ol> |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>b. IF PHG under test responds with rors-cmip-confirmed-event-report (accepted-config) THEN:</p> <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>ii. IF C_MAN_OXP_085 THEN:           <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li><input type="checkbox"/> The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li><input type="checkbox"/> The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> </li> <li>iii. The Test Tool requests to Test Operator to enable the scanner           <ul style="list-style-type: none"> <li><input type="checkbox"/> If the PHG does not enable the scanner then Test Procedure ends.</li> <li><input type="checkbox"/> If the PHG enables the scanner then simulated PHD sends a confirmed Unbuf-Scan-Report-Fixed with one measurement for RT-SA:               <ul style="list-style-type: none"> <li>• If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li>• If the PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure end</li> </ul> </li> </ul> </li> </ol> <p>4. IF the PHG under test responds with an Association Response (accepted) THEN:</p> <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>b. IF C_MAN_OXP_085 THEN:           <ol style="list-style-type: none"> <li>i. The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>ii. The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>iii. The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li>iv. The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ol> </li> <li>c. The Test Tool requests to Test Operator to enable the scanner           <ol style="list-style-type: none"> <li>i. If thePHG does not enable the scanner then Test Procedure ends</li> <li>ii. If thePHG enables the scanner then simulated PHD sends a confirmed Unbuf-Scan-Report-Fixed with one measurement for RT-SA:               <ul style="list-style-type: none"> <li><input type="checkbox"/> If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li><input type="checkbox"/> If the PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends.</li> </ul> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2 or step 3.a, the PHG does not move to the Operating state (2.a and 3.a.i) or Configuring/Sending GetMDS (2.b and 3.a.ii).</li> <li>• In step 3.b or step 4, the PHG does not accept the received measurement or if PHG accepts the measurement then it shall not store or display the received measurement.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                 |                                                               |                                                               |
+|-----------------|---------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHG/OPX/DIM/BV-062                                     |                                                               |
+| <b>TP label</b> | Not supported specialization - International Normalized Ratio |                                                               |
+| <b>Coverage</b> | <b>Spec</b>                                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                 | <b>Testable items</b>                                         | ManagerProc 3;M                                               |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>      | Check that:<br>A specialization declared by the vendor as "not supported" is really not supported by the PHG under test.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_066)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with the dev-config-id set to 0x07 0x08 (international normalized ratio).</li> <li>2. IF the PHG under test responds with an Association Response (rejected-*) or an Abort, THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>b. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>3. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN the simulated PHD sends a configuration event report with the config-report-id set to 0x07 0x08 and including the international normalized ratio configuration objects. <ol style="list-style-type: none"> <li>a. IF the PHG under test responds with rors-cmip-confirmed-event-report (unsupported-config) or Release Request or Abort THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>ii. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>b. IF the PHG under test responds with rors-cmip-confirmed-event-report (accepted-config) THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>ii. IF C_MAN_OXP_085 THEN: <ol style="list-style-type: none"> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li><input type="checkbox"/> The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li><input type="checkbox"/> The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ol> </li> <li>iii. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ol style="list-style-type: none"> <li><input type="checkbox"/> If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li><input type="checkbox"/> If the PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure end</li> </ol> </li> </ol> </li> </ol> </li> <li>4. IF the PHG under test responds with an Association Response (accepted) THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>b. IF C_MAN_OXP_085 THEN: <ol style="list-style-type: none"> <li>i. The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>ii. The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>iii. The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> </ol> </li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>iv. The simulated PHD responds to the PHG under test so it moves to Operating.</p> <p>c. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration:</p> <ol style="list-style-type: none"> <li>i. If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li>ii. If the PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2 or step 3.a, the PHG does not move to the Operating state (2.a and 3.a.i) or Configuring/Sending GetMDS (2.b and 3.a.ii).</li> <li>• In step 3.b or step 4, the PHG does not accept the received measurement or if the PHG accepts the measurement then it shall not store or display the received measurement.</li> </ul>                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/EXP/DIM/BV-063                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |
+| <b>TP label</b>          | Not supported specialization – Sleep Apnoea Breathing Therapy Equipment                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | ManagerProc 3;M                                               |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>A specialization declared by the vendor as "not supported" is really not supported by the PHG under test.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_068)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in Unassociated state                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with dev-config-id set to 0x09 0x60 (Sleep Apnoea Breathing Therapy Equipment)</li> <li>2. IF the PHG under test responds with an Association Response (rejected-*) or Abort, THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>b. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>3. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN simulated PHD sends a configuration event report with config-report-id set to 0x07 0x08 and including International Normalized Ratio configuration objects. <ol style="list-style-type: none"> <li>a. IF the PHG under test responds with rors-cmip-confirmed-event-report (unsupported-config) or Release Request or Abort THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>ii. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>b. IF the PHG under test responds with rors-cmip-confirmed-event-report (accepted-config) THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>ii. IF C_MAN_OXP_085 THEN:</li> </ol> </li> </ol> </li> </ol> |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li><input type="checkbox"/> The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li><input type="checkbox"/> The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> <p style="margin-left: 20px;">iii. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration:</p> <ul style="list-style-type: none"> <li>i. If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li>ii. If the PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure end</li> </ul> <p>4. IF the PHG under test responds with an Association Response (accepted) THEN:</p> <ul style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>b. IF C_MAN_OXP_085 THEN: <ul style="list-style-type: none"> <li>i. The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>ii. The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>iii. The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li>iv. The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> </li> <li>c. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ul style="list-style-type: none"> <li>i. If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li>ii. If the PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends.</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2 or step 3.a, PHG does not move to Operating state (2.a and 3.a.i) or Configuring/Sending GetMDS (2.b and 3.a.ii).</li> <li>• In step 3.b or step 4, PHG does not accept the received measurement or if PHG accepts the measurement then it shall not store or display the received measurement.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|                      |                                                                                                                          |                                                                                                                                                                                                                                                               |                 |  |
+|----------------------|--------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--|
+| <b>TP Id</b>         | TP/PLT/PHG/OXP/DIM/BV-064                                                                                                |                                                                                                                                                                                                                                                               |                 |  |
+| <b>TP label</b>      | Not supported specialization – Insulin Pump                                                                              |                                                                                                                                                                                                                                                               |                 |  |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                              | [ISO/IEEE 11073-20601-2015A]                                                                                                                                                                                                                                  |                 |  |
+|                      | <b>Testable items</b>                                                                                                    | <table border="0" style="width: 100%; border-collapse: collapse;"> <tr> <td style="width: 33%; border-right: 1px solid black;">ManagerProc 3;M</td> <td style="width: 33%; border-right: 1px solid black;"></td> <td style="width: 34%;"></td> </tr> </table> | ManagerProc 3;M |  |
+| ManagerProc 3;M      |                                                                                                                          |                                                                                                                                                                                                                                                               |                 |  |
+| <b>Test purpose</b>  | Check that:<br>A specialization declared by the vendor as "not supported" is really not supported by the PHG under test. |                                                                                                                                                                                                                                                               |                 |  |
+| <b>Applicability</b> | C_MAN_OXP_000 AND NOT(C_MAN_OXP_070)                                                                                     |                                                                                                                                                                                                                                                               |                 |  |
+| <b>Other PICS</b>    | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                              |                                                                                                                                                                                                                                                               |                 |  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b> | The The simulated PHD and the PHG under test are in Unassociated state                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with dev-config-id set to 0x07 0x6C (Insulin Pump)</li> <li>2. IF the PHG under test responds with an Association Response (rejected-*) or Abort, THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>b. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>3. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN simulated PHD sends a configuration event report with config-report-id set to 0x07 0x6C and including Insulin Pump configuration objects. <ol style="list-style-type: none"> <li>a. IF the PHG under test responds with rors-cmip-confirmed-event-report (unsupported-config) or Release Request or Abort THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>ii. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>b. IF the PHG under test responds with rors-cmip-confirmed-event-report (accepted-config) THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>ii. IF C_MAN_OXP_085 THEN: <ul style="list-style-type: none"> <li><li><input type="checkbox"/> The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li></li> <li><li><input type="checkbox"/> The simulated PHD sends rors-cmip-get with MDS attributes.</li></li> <li><li><input type="checkbox"/> The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li></li> <li><li><input type="checkbox"/> The simulated PHD responds to the PHG under test so it moves to Operating.</li></li> </ul> </li> <li>iii. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ul style="list-style-type: none"> <li><li><input type="checkbox"/> If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li></li> <li><li><input type="checkbox"/> If the PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends</li></li> </ul> </li> </ol> </li> </ol> </li> <li>4. IF the PHG under test responds with an Association Response (accepted) THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>b. IF C_MAN_OXP_085 THEN: <ol style="list-style-type: none"> <li>i. The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>ii. The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>iii. The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li>iv. The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ol> </li> <li>c. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ol style="list-style-type: none"> <li>i. If the PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> </ol> </li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>ii. If the PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends</p>                                                                                                                                                                                   |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>In step 2 or step 3.a, PHG does not move to Operating state (2.a and 3.a.i) or Configuring/Sending GetMDS (2.b and 3.a.ii).</li> <li>In step 3.b or step 4, PHG does not accept the received measurement or if PHG accepts the measurement then it shall not store or display the received measurement.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                           |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                              |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/DIM/BV-065                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                              |
+| <b>TP label</b>          | Not supported specialization – Continuous Glucose Monitor                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [ISO/IEEE 11073-20601-2015A] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ManagerProc 3;M              |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>A specialization declared by the vendor as "not supported" is really not supported by the PHG under test.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                              |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_072)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                              |
+| <b>Other PICS</b>        | C_MAN_OXP_083, C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                              |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in Unassociated state                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHD sends an Association Request to the PHG under test with dev-config-id set to 0x09 0xC4 (Continuous Glucose Monitor)</li> <li>IF the PHG under test responds with an Association Response (rejected-*) or Abort, THEN: <ol style="list-style-type: none"> <li>IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN simulated PHD sends a configuration event report with config-report-id set to 0x09 0xC4 and including Continuous Glucose Monitor configuration objects. <ol style="list-style-type: none"> <li>IF the PHG under test responds with rors-cmip-confirmed-event-report (unsupported-config) or Release Request or Abort THEN: <ol style="list-style-type: none"> <li>IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG shall not move to Operating state and the Test Procedure ends.</li> <li>IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>IF the PHG under test responds with rors-cmip-confirmed-event-report (accepted-config) THEN: <ol style="list-style-type: none"> <li>IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>IF C_MAN_OXP_085 THEN: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li><input type="checkbox"/> The simulated PHD sends rors-cmip-get with MDS attributes.</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li><input type="checkbox"/> The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> <p>iii. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> If PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li><input type="checkbox"/> If PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends</li> </ul> <p>4. IF the PHG under test responds with an Association Response (accepted) THEN:</p> <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_083 OR C_MAN_OXP_084 THEN the PHG moves to Operating state.</li> <li>b. IF C_MAN_OXP_085 THEN: <ul style="list-style-type: none"> <li>i. The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>ii. The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>iii. The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li>iv. The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> </li> <li>c. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ul style="list-style-type: none"> <li>i. If PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li>ii. If PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends</li> </ul> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2 or step 3.a, PHG does not move to Operating state (2.a and 3.a.i) or Configuring/Sending GetMDS (2.b and 3.a.ii).</li> <li>• In step 3.b or step 4, PHG does not accept the received measurement or if PHG accepts the measurement then it shall not store or display the received measurement.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                          |                                                                                                                          |                              |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------|------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/DIM/BV-066                                                                                                |                              |
+| <b>TP label</b>          | Not supported specialization – Power Status Monitor with Simple PSM profile                                              |                              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                              | [ISO/IEEE 11073-20601-2015A] |
+|                          | <b>Testable items</b>                                                                                                    | ManagerProc 3;M              |
+| <b>Test purpose</b>      | Check that:<br>A specialization declared by the vendor as "not supported" is really not supported by the PHG under test. |                              |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_074)                                                                                     |                              |
+| <b>Other PICS</b>        | C_MAN_OXP_084, C_MAN_OXP_085                                                                                             |                              |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in Unassociated state                                                       |                              |
+
+|                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test procedure</b> | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with dev-config-id set to 0x0A8C (2700)</li> <li>2. IF the PHG under test responds with an Association Response (rejected-*) or Abort, THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_084 THEN the PHG shall not move to operating state and the Test Procedure ends.</li> <li>b. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>3. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN simulated PHD sends a configuration event report with config-report-id set to one of the ones mentioned in step 1 and including power status monitor configuration objects. <ol style="list-style-type: none"> <li>a. IF the PHG under test responds with rors-cmip-confirmed-event-report (unsupported-config) or Release Request or Abort THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_084 THEN the PHG shall not move to operating state and the Test Procedure ends.</li> <li>ii. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>b. IF the PHG under test responds with rors-cmip-confirmed-event-report (accepted-config) THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_084 THEN the PHG moves to operating state.</li> <li>ii. IF C_MAN_OXP_085 THEN: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li><input type="checkbox"/> The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li><input type="checkbox"/> The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> </li> <li>iii. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ul style="list-style-type: none"> <li><input type="checkbox"/> If PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li><input type="checkbox"/> If PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends</li> </ul> </li> </ol> </li> </ol> </li> <li>4. IF the PHG under test responds with an Association Response (accepted) THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_084 THEN the PHG moves to operating state.</li> <li>b. IF C_MAN_OXP_085 THEN: <ol style="list-style-type: none"> <li>i. The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>ii. The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>iii. The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li>iv. The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ol> </li> <li>c. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ol style="list-style-type: none"> <li>i. If PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li>ii. If PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends</li> </ol> </li> </ol> </li> </ol> |
+|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                           |                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2 or step 3.a, PHG does not move to operating state (2.a and 3.a.i) or Configuring/Sending GetMDS (2.b and 3.a.ii).</li> <li>• In step 3.b or step 4, PHG does not accept the received measurement or if PHG accepts the measurement then it shall not store or display the received measurement.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                               |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                              |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/DIM/BV-067                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                              |
+| <b>TP label</b>          | Not supported specialization – Power Status Monitor with Advanced PSM profile                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [ISO/IEEE 11073-20601-2015A] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ManagerProc 3;M              |
+| <b>Test purpose</b>      | Check that:<br>A specialization declared by the vendor as "not supported" is really not supported by the PHG under test.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                              |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND NOT(C_MAN_OXP_075)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                              |
+| <b>Other PICS</b>        | C_MAN_OXP_084, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                              |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in Unassociated state                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with dev-config-id set to an extended configuration between 0x4000-0x7FFF (Power Status Monitor with Advanced PSM profile)</li> <li>2. IF the PHG under test responds with an Association Response (rejected-*) or Abort, THEN: <ol style="list-style-type: none"> <li>a. IF C_MAN_OXP_084 THEN the PHG shall not move to operating state and the Test Procedure ends.</li> <li>b. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>3. IF the PHG under test responds with an Association Response (accepted-unknown-config) THEN simulated PHD sends a configuration event report with config-report-id set to one of the ones mentioned in step 1 and including power status monitor configuration objects. <ol style="list-style-type: none"> <li>a) IF the PHG under test responds with rors-cmip-confirmed-event-report (unsupported-config) or Release Request or Abort THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_084 THEN the PHG shall not move to operating state and the Test Procedure ends.</li> <li>ii. IF C_MAN_OXP_085 THEN the PHG shall not move to Configuring/Sending GetMDS substate and the Test Procedure ends.</li> </ol> </li> <li>b) IF the PHG under test responds with rors-cmip-confirmed-event-report (accepted-config) THEN: <ol style="list-style-type: none"> <li>i. IF C_MAN_OXP_084 THEN the PHG moves to operating state.</li> <li>ii. IF C_MAN_OXP_085 THEN: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li><input type="checkbox"/> The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li><input type="checkbox"/> The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li> <ul style="list-style-type: none"> <li> <ul style="list-style-type: none"> <li><input type="checkbox"/> The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> </li> <li>iii. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ul style="list-style-type: none"> <li><input type="checkbox"/> If PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li><input type="checkbox"/> If PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends</li> </ul> </li> </ul> </li> <li>4. IF the PHG under test responds with an Association Response (accepted) THEN: <ul style="list-style-type: none"> <li>a. IF C_MAN_OXP_084 THEN the PHG moves to operating state.</li> <li>b. IF C_MAN_OXP_085 THEN: <ul style="list-style-type: none"> <li>i. The PHG under test moves to Configuring/Sending GetMDS substate and issues a roiv-cmip-get command.</li> <li>ii. The simulated PHD sends rors-cmip-get with MDS attributes.</li> <li>iii. The PHG under test moves to Configuring/Sending Set Time and issues a Set Time action command.</li> <li>iv. The simulated PHD responds to the PHG under test so it moves to Operating.</li> </ul> </li> <li>c. The simulated PHD sends a confirmed fixed event report with one measurement for every object present in the configuration: <ul style="list-style-type: none"> <li>i. If PHG under test responds with roer, rorj, rlrq or Abort then Test Procedure ends.</li> <li>ii. If PHG under test responds with rors-cmip-confirmed-event-report then it shall not store or display the received measurement and the Test Procedure ends</li> </ul> </li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 2 or step 3.a, PHG does not move to operating state (2.a and 3.a.i) or Configuring/Sending GetMDS (2.b and 3.a.ii).</li> <li>• In step 3.b or step 4, PHG does not accept the received measurement or if PHG accepts the measurement then it shall not store or display the received measurement.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+## A.4 Subgroup 2.2.3: PHD service model (SER)
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/SER/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+| <b>TP label</b>          | Configuration event report. Configuration Response Format                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ObjAccessServ 2;M      ConfNormalProc 8;M                     |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The PHG shall respond (to the configuration event) with a "Remote Operation Response   Confirmed Event Report" message with an event-type of MDC_NOTI_CONFIG filling in the ConfigReportRsp structure or with an appropriate roer error message with a suitable return code.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |
+| <b>Applicability</b>     | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state. The PHG must not have any configuration memorised.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD test sends an Association Request to the PHG under test with an unknown configuration to the PHG dev-config-id in the extended range.</li> <li>2. The PHG under test responds with an Association Response with "accepted-unknown-config".</li> <li>3. The simulated PHD sends a configuration event report with an extended configuration supported by the PHD.</li> <li>4. The PHG under test must respond with:</li> <li>5. Received message by the PHD must be:           <ol style="list-style-type: none"> <li>a. APDU Type               <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstAdpu)</li> </ul> </li> <li>b. Invoke-id               <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = INT-U16</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = It must be the same as the invoke-id of the simulated PHD's message.</li> </ul> </li> <li>c. Obj-Handle:               <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x00</li> </ul> </li> <li>d. Event-time:               <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = INT-U32</li> <li><input type="checkbox"/> field-length = 4 bytes</li> <li><input type="checkbox"/> field-value: &lt;Relative time&gt; OR &lt;0xFF 0xFF 0xFF 0xFF&gt;</li> </ul> </li> <li>e. Event-type:               <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0D 0x1C (MDC_NOTI_CONFIG)</li> </ul> </li> <li>f. The following six bytes indicates:               <ul style="list-style-type: none"> <li><input type="checkbox"/> Event-replay-info.length (2 bytes)</li> <li><input type="checkbox"/> ConfigReportRsp.config-report-id:it must be the same as the config-report-id of the simulated PHD's message</li> </ul> </li> </ol> </li> </ol> |                                                               |
+
+|                           |                                                                                                                                              |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> ConfigReportRsp.config-result:One of: <ul style="list-style-type: none"> <li>▪ accepted-config:0x00 0x00</li> </ul> |
+| <b>Pass/Fail criteria</b> | The message sent by the PHG under test must be the one specified.                                                                            |
+| <b>Notes</b>              | We just want to test the format of the report, the unsupported-config behaviour is tested in TP/PLT/PHG/OPX/COM/BV-005                       |
+
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                                                                                                                                 |                       |
+|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| <b>TP Id</b>        | TP/PLT/PHG/OPX/SER/BV-003_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                                                                                                                                 |                       |
+| <b>TP label</b>     | Fixed format event report. Single-person unconfirmed event report.                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                 |                       |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C]                                                                                                   |                       |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | ObjAccessServ 2;M                                                                                                                                               | MeasureDataTransf 8;C |
+|                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | FormatEventRep 3;M                                                                                                                                              | PersonEventRep 1;M    |
+|                     | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [b-ITU-T H.810 (2015)]                                                                                                                                          |                       |
+| <b>Test purpose</b> | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | Conformance 1; M                                                                                                                                                |                       |
+|                     | <p>Check that:</p> <p>A PHG receiving a confirmed event report from the PHD shall respond with either a rors-cmip-confirmed-event-report or an appropriate roer error message with a suitable return code.</p> <p>[AND]</p> <p>If a PHD uses agent-initiated measurements and if the Unconfirmed Event Report is used, the PHG shall not respond.</p> <p>[AND]</p> <p>A PHG shall support single-person event reports.</p> <p>[AND]</p> <p>A PHG shall support fixed format event reports.</p> |                                                                                                                                                                 |                       |
+|                     | <b>Applicability</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | C_MAN_OXP_000                                                                                                                                                   |                       |
+|                     | <b>Other PICS</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                                                                                                                                 |                       |
+|                     | <b>Initial condition</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The simulated PHD and the PHG under test are in the Operating state.                                                                                            |                       |
+|                     | <b>Test procedure</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | 1. The simulated PHD test sends an unconfirmed Fixed event report to the PHG under test.<br><br>2. Verify that the PHG under test does not send a confirmation. |                       |
+|                     | <b>Pass/Fail criteria</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | In step 2 no confirmation can be received by the simulated PHD.                                                                                                 |                       |
+|                     | <b>Notes</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                                                                                                                                 |                       |
+
+|                     |                                                                                                                                                                                                                |                                                               |                       |
+|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------|
+| <b>TP Id</b>        | TP/PLT/PHG/OPX/SER/BV-003_B                                                                                                                                                                                    |                                                               |                       |
+| <b>TP label</b>     | Fixed format event report. Single-person confirmed event report.                                                                                                                                               |                                                               |                       |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                    | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                       |
+|                     | <b>Testable items</b>                                                                                                                                                                                          | ObjAccessServ 2;M                                             | MeasureDataTransf 7;C |
+|                     |                                                                                                                                                                                                                | FormatEventRep 3;M                                            | PersonEventRep 1;M    |
+|                     | <b>Spec</b>                                                                                                                                                                                                    | [b-ITU-T H.810 (2015)]                                        |                       |
+| <b>Test purpose</b> | <b>Testable items</b>                                                                                                                                                                                          | Conformance 1; M                                              |                       |
+|                     | <p>Check that:</p> <p>A PHG receiving a confirmed event report from the PHD shall respond with either a rors-cmip-confirmed-event-report or an appropriate roer error message with a suitable return code.</p> |                                                               |                       |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | [AND]<br>A PHG shall support single-person event reports.<br>[AND]<br>A PHG shall support fixed format event reports.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends a confirmed Fixed event report to the PHG under test.</li> <li>2. The PHG under test sends a confirmation: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstAdpu)</li> </ol> </li> <li>b. Invoke-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = INT-U16</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = It must be the same as the invoke-id of the simulated PHD's message.</li> </ol> </li> <li>c. The following two bytes indicate: <ol style="list-style-type: none"> <li><input type="checkbox"/> message type = 0x02 0x01 (Remote Operation Response   Confirmed Event Report)</li> </ol> </li> <li>d. Obj-Handle: <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0 (MDS object)</li> </ol> </li> <li>e. Event-time: <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = INT-U32</li> <li><input type="checkbox"/> field-length = 4 bytes</li> <li><input type="checkbox"/> field-value: &lt;Not relevant for this Test&gt;</li> </ol> </li> <li>f. Event-type: <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0D 0x1D (MDC_NOTI_SCAN_REPORT_FIXED)</li> </ol> </li> <li>g. event-reply-info <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 0 bytes (0x00 0x00)</li> <li><input type="checkbox"/> field-value = empty (0x00 0x00)</li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The confirmation message must be like the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|                 |                                                                   |                                                               |                       |
+|-----------------|-------------------------------------------------------------------|---------------------------------------------------------------|-----------------------|
+| <b>TP Id</b>    | TP/PLT/PHG/OXP/SER/BV-003_C                                       |                                                               |                       |
+| <b>TP label</b> | Fixed format event report. Multi-person unconfirmed event report. |                                                               |                       |
+| <b>Coverage</b> | <b>Spec</b>                                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                       |
+|                 | <b>Testable items</b>                                             | ObjAccessServ 2;M                                             | MeasureDataTransf 8;C |
+|                 |                                                                   | FormatEventRep 3;M                                            | PersonEventRep 1;M    |
+|                 | <b>Spec</b>                                                       | [b-ITU-T H.810 (2015)]                                        |                       |
+|                 | <b>Testable items</b>                                             | Conformance 1; M                                              |                       |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>       | <p>Check that:</p> <p>A PHG receiving a confirmed event report from the PHD shall respond with either a rors-cmip-confirmed-event-report or an appropriate roer error message with a suitable return code.</p> <p>[AND]</p> <p>If a PHD uses agent-initiated measurements and if the Unconfirmed Event Report is used, the PHG shall not respond.</p> <p>[AND]</p> <p>A PHG shall support multi-person event reports.</p> <p>[AND]</p> <p>A PHG shall support fixed format event reports.</p> |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated PHD test sends a unconfirmed Fixed Multiple Person event report to the PHG under test.</li> <li>The PHG under test does not send a confirmation.</li> </ol>                                                                                                                                                                                                                                                                              |
+| <b>Pass/Fail criteria</b> | In step 2 no confirmation can be received by the simulated PHD.                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                    |  |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------|--|--|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/SER/BV-003_D                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                    |  |  |
+| <b>TP label</b>          | Fixed format event report. Multi-person confirmed event report.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                    |  |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                    |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | ObjAccessServ 2;M                                             | PersonEventRep 1;M |  |  |
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [b-ITU-T H.810 (2015)]                                        |                    |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Conformance 1; M                                              |                    |  |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>A PHG receiving a confirmed event report from the PHD shall respond with either a rors-cmip-confirmed-event-report or an appropriate roer error message with a suitable return code.</p> <p>[AND]</p> <p>A PHG shall support multi-person event reports.</p> <p>[AND]</p> <p>A PHG shall support fixed format event reports.</p>                                                                                                                                                                                                       |                                                               |                    |  |  |
+| <b>Applicability</b>     | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                    |  |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                    |  |  |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                    |  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHD test sends a confirmed Fixed Multi Person event report to the PHG under test.</li> <li>The PHG under test sends a confirmation: <ol style="list-style-type: none"> <li>APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstAdpu)</li> </ul> </li> <li>Invoke-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = INT-U16</li> </ul> </li> </ol> </li> </ol> |                                                               |                    |  |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = It must be the same as the invoke-id of the simulated PHD's message.</li> </ul> <p>c. The following two bytes indicate:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> message type = 0x02 0x01 (Remote Operation Response   Confirmed Event Report)</li> </ul> <p>d. Obj-Handle:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0 (MDS object)</li> </ul> <p>e. Event-time:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = INT-U32</li> <li><input type="checkbox"/> field-length = 4 bytes</li> <li><input type="checkbox"/> field-value: &lt;Not relevant for this Test&gt;</li> </ul> <p>f. Event-type:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x0D 0x1F (MDC_NOTI_SCAN_REPORT_MP_FIXED)</li> </ul> |
+| <b>Pass/Fail criteria</b> | The confirmation message must be like the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                       |                    |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------|--------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/SER/BV-003_E                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                       |                    |
+| <b>TP label</b>          | Variable format event report. Single-person unconfirmed event report.                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                       |                    |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                       |                    |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | ObjAccessServ 2;M                                             | MeasureDataTransf 8;C | PersonEventRep 1;M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | FormatEventRep 3;M                                            |                       |                    |
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [b-ITU-T H.810 (2015)]                                        |                       |                    |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Conformance 1; M                                              |                       |                    |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>A PHG receiving a confirmed event report from the PHD shall respond with either a rors-cmip-confirmed-event-report or an appropriate roer error message with a suitable return code.</p> <p>[AND]</p> <p>If a PHD uses agent-initiated measurements and if the Unconfirmed Event Report is used, the PHG shall not respond.</p> <p>[AND]</p> <p>A PHG shall support single-person event reports.</p> <p>[AND]</p> <p>A PHG shall support variable format event reports.</p> |                                                               |                       |                    |
+| <b>Applicability</b>     | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                       |                    |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                       |                    |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                       |                    |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD test sends an unconfirmed variable event report to the PHG under test. The unconfirmed variable event report contains just one Observation Scan with information about Metric-Spec-Small attributes for metric objects that are present in the PHD's configuration.</li> <li>2. The PHG under test cannot send a confirmation.</li> </ol>                                                                                             |                                                               |                       |                    |
+
+|                           |                                                                 |
+|---------------------------|-----------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | In step 2 no confirmation can be received by the simulated PHD. |
+| <b>Notes</b>              |                                                                 |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                       |  |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------|--|--|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/SER/BV-003_F                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                       |  |  |
+| <b>TP label</b>          | Variable format event report. Single-person confirmed event report.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                       |  |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                       |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ObjAccessServ 2;M                                             | MeasureDataTransf 7;C |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | FormatEventRep 3;M                                            | PersonEventRep 1;M    |  |  |
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [b-ITU-T H.810 (2015)]                                        |                       |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Conformance 1; M                                              |                       |  |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>A PHG receiving a confirmed event report from the PHD shall respond with either a rors-cmip-confirmed-event-report or an appropriate roer error message with a suitable return code.</p> <p>[AND]</p> <p>A PHG shall support single-person event reports.</p> <p>[AND]</p> <p>A PHG shall support variable format event reports.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                       |  |  |
+| <b>Applicability</b>     | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                       |  |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                       |  |  |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                       |  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD test sends a confirmed variable event report to the PHG under test.</li> <li>2. The PHG under test sends a confirmation:           <ol style="list-style-type: none"> <li>a. APDU Type               <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstAdpu)</li> </ul> </li> <li>b. Invoke-id               <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = INT-U16</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = It must be the same as the invoke-id of the simulated PHD's message.</li> </ul> </li> <li>c. The following two bytes indicates               <ul style="list-style-type: none"> <li><input type="checkbox"/> message type= 0x02 0x01 (Remote Operation Response   Confirmed Event Report)</li> </ul> </li> <li>d. Obj-Handle:               <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0 (MDS object)</li> </ul> </li> <li>e. Event-time:               <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = INT-U32</li> <li><input type="checkbox"/> field-length = 4 bytes</li> <li><input type="checkbox"/> field-value: &lt;Not relevant for this Test&gt;</li> </ul> </li> <li>f. Event-type:               <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> </ul> </li> </ol> </li> </ol> |                                                               |                       |  |  |
+
+|                           |                                                                             |
+|---------------------------|-----------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> field-value = 0x0D 0x1E (MDC_NOTI_SCAN_REPORT_VAR) |
+| <b>Pass/Fail criteria</b> | The confirmation message must be like the one specified.                    |
+| <b>Notes</b>              |                                                                             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                       |                    |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------|--------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/SER/BV-003_G                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |                       |                    |
+| <b>TP label</b>           | Variable format event report. Multi-person unconfirmed event report.                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                       |                    |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                       |                    |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                         | ObjAccessServ 2;M                                             | MeasureDataTransf 8;C | PersonEventRep 1;M |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                               | FormatEventRep 3;M                                            |                       |                    |
+|                           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [b-ITU-T H.810 (2015)]                                        |                       |                    |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                         | Conformance 1; M                                              |                       |                    |
+| <b>Test purpose</b>       | Check that:<br>A PHG receiving a confirmed event report from the PHD shall respond with either a rors-cmip-confirmed-event-report or an appropriate roer error message with a suitable return code.<br>[AND]<br>If a PHD uses agent-initiated measurements and if the Unconfirmed Event Report is used, the PHG shall not respond.<br>[AND]<br>A PHG shall support multi-person event reports.<br>[AND]<br>A PHG shall support variable format event reports. |                                                               |                       |                    |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                       |                    |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                       |                    |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                       |                    |
+| <b>Test procedure</b>     | 1. The simulated PHD sends an unconfirmed Variable Multiple Person event report to the PHG under test.<br>2. The PHG under test cannot send a confirmation.                                                                                                                                                                                                                                                                                                   |                                                               |                       |                    |
+| <b>Pass/Fail criteria</b> | In step 2 no confirmation can be received by the simulated PHD.                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                       |                    |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                       |                    |
+
+|                     |                                                                                                                                                                                                                                                                          |                                                               |                    |                    |
+|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------|--------------------|
+| <b>TP Id</b>        | TP/PLT/PHG/OXP/SER/BV-003_H                                                                                                                                                                                                                                              |                                                               |                    |                    |
+| <b>TP label</b>     | Variable format event report. Multi-person confirmed event report                                                                                                                                                                                                        |                                                               |                    |                    |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                    |                    |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                    | ObjAccessServ 2;M                                             | PersonEventRep 1;M | FormatEventRep 3;M |
+|                     | <b>Spec</b>                                                                                                                                                                                                                                                              | [b-ITU-T H.810 (2015)]                                        |                    |                    |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                    | Conformance 1; M                                              |                    |                    |
+| <b>Test purpose</b> | Check that:<br>A PHG receiving a confirmed event report from the PHD shall respond with either a rors-cmip-confirmed-event-report or an appropriate roer error message with a suitable return code.<br>[AND]<br>A PHG shall support multi-person event reports.<br>[AND] |                                                               |                    |                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | A PHG shall support variable format event reports.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends a confirmed Variable Multi Person event report to the PHG under test.</li> <li>2. The PHG under test sends a confirmation: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstAdpu)</li> </ol> </li> <li>b. Invoke-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = INT-U16</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = It must be the same that the invoke-id of the simulated PHD's message.</li> </ol> </li> <li>c. The following two bytes indicate: <ol style="list-style-type: none"> <li><input type="checkbox"/> message type= 0x02 0x01 (Remote Operation Response   Confirmed Event Report)</li> </ol> </li> <li>d. Obj-Handle: <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0 (MDS object)</li> </ol> </li> <li>e. Event-time: <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = INT-U32</li> <li><input type="checkbox"/> field-length = 4 bytes</li> <li><input type="checkbox"/> field-value: &lt;Not relevant for this Test&gt;</li> </ol> </li> <li>f. Event-type: <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value= 0x0D 0x20 (MDC_NOTI_SCAN_REPORT_MP_VAR)</li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The confirmation message must be like the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|                          |                                                                                                                                                                                                                                          |                                                               |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/SER/BV-004                                                                                                                                                                                                                |                                                               |
+| <b>TP label</b>          | Multi-person support                                                                                                                                                                                                                     |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                    | PersonEventRep 1;M      FormatEventRep 3;M                    |
+| <b>Test purpose</b>      | Check that:<br>A PHG shall support both single-person and multi-person event reports.<br>[AND]<br>A PHG shall support variable format and fixed format, and if the PHG supports scanners, it shall support grouped format event reports. |                                                               |
+| <b>Applicability</b>     | C_MAN_OXP_000                                                                                                                                                                                                                            |                                                               |
+| <b>Other PICS</b>        | C_MAN_OXP_037                                                                                                                                                                                                                            |                                                               |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                     |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends a confirmed Fixed Multi Person event report to the PHG under test with two different measurements assigned to different person-ids.</li> <li>2. The PHG under test sends a confirmation.</li> <li>3. The simulated PHG sends a new confirmed Fixed Multi Person with two different measurements from those in step 1 to the PHG under test.</li> <li>4. The PHG under test sends a confirmation.</li> </ol> |
+| <b>Pass/Fail criteria</b> | IF C_MAN_OXP_037 = TRUE THEN the PHG under test correctly assigns the measurements to the correct person, ELSE the PHG under test does not assign the measurements correctly to every person.                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/SER/BV-005                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |
+| <b>TP label</b>           | Reserved Value Standard Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | ConfEventRep 17;M                                             |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>All unused values in the standard range are reserved for future use, A PHG encountering such a reserved value shall assume the value to be an extended unsupported unrecognized standard configuration and use it as described in 8.7.3.3 and 8.8.3.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND (C_MAN_OXP_016 OR C_MAN_OXP_018 OR C_MAN_OXP_019 OR C_MAN_OXP_020 OR C_MAN_OXP_024 OR C_MAN_OXP_025 OR C_MAN_OXP_026 OR C_MAN_OXP_027 OR C_MAN_OXP_029 OR C_MAN_OXP_067 OR C_MAN_OXP_071 OR C_MAN_OXP_073 OR C_MAN_OXP_076)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with a dev-config-id set to an id in the standard range (reserved value).</li> <li>2. The PHG under test responds with an Association Response: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE3 0x00 (AareAdpu)</li> </ul> </li> <li>b. Result <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x03 (accepted-unknown-config) or 0x00 0x00 (accepted) or 0x00 0x07 (rejected-unauthorized) or 0x00 0x01 (rejected-permanent) or 0x00 0x06 (rejected-unknown)</li> </ul> </li> </ol> </li> <li>3. IF the PHG responds with "accepted-unknown-config", the simulated PHD sends its configuration.</li> <li>4. The PHG under test sends a configuration response with accepted-config or unsupported-config.</li> </ol> |                                                               |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The response of step 2 shall have a value = "accepted-unknown-config" or "accepted" or "rejected-unauthorized" or "rejected-permanent" or "rejected-unknown".</li> <li>• The response of step 4 shall have a config-result = "unsupported-config" or "accepted-config".</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+
+## A.5 Subgroup 2.2.4: PHD communication model (COM)
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                   |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-004                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                   |
+| <b>TP label</b>           | Manager State Machine:TO <sub>config</sub>                                                                                                                                                                                                                                                                                                                                                         |                                                               |                   |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                   |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                              | ManagerStateMach 1;M                                          | ConfErrorCond 3;M |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>The PHG shall wait in the Waiting for Config state for at least TO<sub>config</sub> seconds before sending an Association Abort message</p> <p>[AND]</p> <p>The PHG shall wait at least TO<sub>config</sub> seconds in the Waiting for Configuration state for the configuration information prior to sending an Abort message and returning to the Unassociated state.</p>  |                                                               |                   |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                   |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                   |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                            |                                                               |                   |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated PHD sends an Association Request to the PHG under test with a dev-config-id unknown to the PHG and set on the extended range.</li> <li>The PHG under test responds with an Association Response with AssociateResult = "accepted-unknown-config".</li> <li>The simulated PHD intentionally does not send its configuration at all.</li> </ol> |                                                               |                   |
+| <b>Pass/Fail criteria</b> | The PHG under test waits for I_MAN_OXP_008 us and then sends an Abort message                                                                                                                                                                                                                                                                                                                      |                                                               |                   |
+| <b>Notes</b>              | Due to the delay introduced by the transport layer and decoder for the received APDU, the test tool accuracy may not be enough to measure this time-out. To get better accuracy it is necessary to run this test case using a hardware sniffer.                                                                                                                                                    |                                                               |                   |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                      |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|----------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/COM/BV-005                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                      |
+| <b>TP label</b>          | Manager State Machine:Unsupported Config                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                      |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                      |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ManagerStateMach 2;M                                          | ConfNormalProc 12 ;M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If the PHG does not accept the configuration, it shall send a configuration response with an unsupported-config result</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |                      |
+| <b>Applicability</b>     | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                      |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |                      |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                      |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>Configure the simulated PHD to support one specialization that is not supported by the PHG and a second specialization that is supported by the PHG. In particular, make sure the following two attributes have values corresponding at least to the supported specialization in the MDS object:System-Type-Spec-List and Reg-Cert-Data-List.</li> <li>The simulated PHD sends an Association Request to the PHG under test with a dev-config-id set to the unsupported device specialization (preferably a standard config).</li> <li>The PHG under test responds with an Association Response with AssociateResult = "accepted-unknown-config".</li> <li>If the PHG under test sends a GET request for the MDS object, the simulated PHD shall respond with the MDS information.</li> <li>If PHG supports all specializations, the PHD sends a Config Report with an extended config-id and only OEM Objects; otherwise, the simulated PHD sends a Config report from the selected specialization that is not supported by the PHG.</li> </ol> |                                                               |                      |
+
+|                           |                                                                                                                                                  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | 6. The PHG under test sends a config response.                                                                                                   |
+| <b>Pass/Fail criteria</b> | The response of step 6 shall have a config-result = "unsupported-config". IF the config-result is not unsupported-config, the verdict is inconc. |
+| <b>Notes</b>              | There is no guarantee that the PHG will not accept the configuration.                                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                                                                   |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-------------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/COM/BV-006                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |                                                                   |
+| <b>TP label</b>          | Manager State Machine:Accepted Config                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                                                                   |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                                                                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ConfEventRep 5;M<br>ManagerProc 4;M                           | ConfEventRep 23;M<br>ConfNormalProc 11; M<br>ManagerStateMach 3;M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If the PHG does not already know the PHD's device configuration (e.g., based on a previous association phase), the PHG asks for the PHD's device configuration.</p> <p>[AND]</p> <p>If the configuration is not known, the PHG shall respond with an accepted-unknown-config response</p> <p>[AND]</p> <p>If the PHG accepts the configuration, it shall send a configuration response with an accepted-config result</p> <p>[AND]</p> <p>If the PHG does not recognize the value in the dev-config-id field, the PHG shall send an Association Response message with the result field set to accepted-unknown-config and transition to the Configuring state.</p> <p>[AND]</p> <p>If the PHG accepts the configuration, it responds with an accepted-config message and both PHG and PHD move to the Operating state.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                                                                   |
+| <b>Applicability</b>     | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                                                                   |
+| <b>Other PICS</b>        | C_MAN_OXP_046                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                                                                   |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |                                                                   |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with a previously unknown dev-config-id set in the extended range.</li> <li>2. The PHG under test responds with an Association Response with result = "accepted-unknown-config".</li> <li>3. Wait until Operating state is reached.</li> <li>4. The PHD sends an abort message.</li> <li>5. The simulated PHD sends the same Association Request to the PHG as in step 5.</li> <li>6. IF C_MAN_OXP_046 = TRUE the PHG under test responds with an Association Response: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE3 0x00 (AareAdpu)</li> </ul> </li> <li>b. Result <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x00 (accepted)</li> </ul> </li> </ol> </li> </ol> <p>IF C_MAN_OXP_046 = FALSE the PHG under test responds with an Association Response:</p> <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> </ul> </li> </ol> |                                                               |                                                                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> field-value = 0xE3 0x00 (AareAdpu)</li> <li>b. Result <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x03 (accepted-unknown-config)</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 6 must be the one specified.                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                         |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                                          |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OPX/COM/BV-007_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                                          |
+| <b>TP label</b>           | Manager State machine:Operating - Unassociated 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                                          |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                                          |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ConfEventRep 22;M<br>ConfExitCond 1;M                         | ManagerStateMach 49;M<br>ManagerProc 3;M |
+| <b>Test purpose</b>       | Check that:<br>If the PHG already understands that configuration either because it was preloaded via an installation program or the PHD previously associated with the PHG, then the PHG shall respond with the configuration accepted response<br>[AND]<br>If PHG receives rlrq while in Operating state, the PHG shall transmit rlre(normal) and move to the Unassociated state.<br>[AND]<br>If the PHG recognizes the value in the dev-config-id field as representing a known standard device specialization, or a configuration from a previous association, the PHG shall send an Association Response message with a result field of accepted and transition to the Operating state or may send an Association Response message with a result field of accepted-unknown-config to force the PHD to enter Configuring state in order to check attributes from the MDS object prior to final acceptance of the association. |                                                               |                                          |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                                          |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                                          |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                                          |
+| <b>Test procedure</b>     | 1. The simulated PHD sends a Release Request with reason = "normal".<br>2. The PHG under test responds with a Release Response and moves to the Unassociated state:<br>a. APDU Type:<br><input type="checkbox"/> field-length = 2 bytes<br><input type="checkbox"/> field-value = 0xE5 0x00 (RlreApdu)<br>b. ReleaseResponseReason:<br><input type="checkbox"/> field-length = 2 bytes<br><input type="checkbox"/> field-value = 0x00 0x00 (normal)                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                                          |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                                          |
+
+|                 |                                                     |                                                               |  |
+|-----------------|-----------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>    | TP/PLT/PHG/OPX/COM/BV-007_B                         |                                                               |  |
+| <b>TP label</b> | Manager State machine:Unassociated - Unassociated 2 |                                                               |  |
+| <b>Coverage</b> | <b>Spec</b>                                         | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                 | <b>Testable items</b>                               | ManagerStateMach 12;M                                         |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>       | Check that:<br>If a are received while in Unassociated state, a PHG shall transmit an abrt (reason undefined) and remain in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Response to the PHG under test.</li> <li>2. The PHG under test responds with and Association Abort message: <ol style="list-style-type: none"> <li>a. APDU Type: <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00</li> </ul> </li> <li>b. Abort-Reason: <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x00 (undefined)</li> </ul> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-007_C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+| <b>TP label</b>           | Manager State machine:Unassociated - Unassociated 3                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ManagerStateMach 13;M                                         |
+| <b>Test purpose</b>       | Check that:<br>If rlrq received while in Unassociated state, a PHG shall transmit an abrt (reason undefined) and remain in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends a Release Request message to the PHG under test.</li> <li>2. The PHG under test responds with an Association Abort message: <ol style="list-style-type: none"> <li>a. APDU Type: <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00</li> </ul> </li> <li>b. Abort-Reason: <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x00 (undefined)</li> </ul> </li> </ol> </li> </ol> |                                                               |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+
+|                     |                                                     |                                                               |
+|---------------------|-----------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>        | TP/PLT/PHG/OXP/COM/BV-007_D                         |                                                               |
+| <b>TP label</b>     | Manager State machine:Unassociated - Unassociated 4 |                                                               |
+| <b>Coverage</b>     | <b>Spec</b>                                         | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                     | <b>Testable items</b>                               | ManagerStateMach 16;M                                         |
+| <b>Test purpose</b> | Check that:                                         |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | If prst (Any APDU not covered in 2.* (corrupt, unknown, unexpected, etc.) received while in Unassociated state, a PHG shall transmit an abrt(Abort-reason undefined) and remain in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends a Configuration Event report to the PHG under test.</li> <li>2. The PHG under test responds with an Association Abort message: <ol style="list-style-type: none"> <li>a. APDU Type: <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00</li> </ul> </li> <li>b. Abort-Reason: <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x00 (undefined)</li> </ul> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-007_E                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+| <b>TP label</b>           | Manager State machine:Unassociated. Corrupt-unknown-unexpected APDU                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ManagerStateMach 16;M                                         |
+| <b>Test purpose</b>       | Check that:<br><br>If prst (Any APDU not covered in 2.* (corrupt, unknown, unexpected, etc.) received while in Unassociated state, a PHG shall transmit an abrt(Abort-reason undefined) and remain in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an invalid APDU.</li> <li>2. The PHG under test responds with an Association Abort message: <ol style="list-style-type: none"> <li>a. APDU Type: <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00</li> </ul> </li> <li>b. Abort-Reason: <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x00 (undefined)</li> </ul> </li> </ol> </li> </ol> |                                                               |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+
+|                 |                                             |                                                               |
+|-----------------|---------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHG/OXP/COM/BV-008_A                 |                                                               |
+| <b>TP label</b> | Manager State machine:Configuring Waiting 1 |                                                               |
+| <b>Coverage</b> | <b>Spec</b>                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                 | <b>Testable items</b>                       | ManagerStateMach 27;M                                         |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>       | Check that:<br>If PHG receives Rx roiv-* but not matching in any other 6* state, while in Waiting state, the PHG shall transmit an abrt(Abort-reason undefined) and moves to Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with a dev-config-id set to an id in the extended range unknown to the PHG.</li> <li>2. The PHG under test responds with an Association Response: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE3 0x00 (AareAdpu)</li> </ul> </li> <li>b. Result <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x03 (accepted-unknown-config)</li> </ul> </li> </ol> </li> <li>3. The simulated PHD sends a "roiv-cmip-get".</li> <li>4. The PHG under test responds with an Association Abort message: <ol style="list-style-type: none"> <li>a. APDU Type: <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00</li> </ul> </li> <li>b. Abort-Reason: <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x00 (undefined)</li> </ul> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 4 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/COM/BV-008_B                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+| <b>TP label</b>          | Manager State machine:Configuring Waiting 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | ManagerStateMach 27;M                                         |
+| <b>Test purpose</b>      | Check that:<br>If PHG receives Rx roiv-* but not matching in any other 6* state, while in Waiting state, the PHG shall transmit an abrt(Abort-reason undefined) and moves to Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |
+| <b>Applicability</b>     | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with a dev-config-id set to an id in the extended range unknown to the PHG.</li> <li>2. The PHG under test responds with an Association Response: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE3 0x00 (AareAdpu)</li> </ul> </li> <li>b. Result <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> </ul> </li> </ol> </li> </ol> |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> field-value = 0x00 0x03 (accepted-unknown-config)</li> </ul> <ol style="list-style-type: none"> <li>3. The simulated PHD sends a "roiv-cmip-set".</li> <li>4. The PHG under test responds with an Association Abort message: <ul style="list-style-type: none"> <li>a. APDU Type: <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00</li> </ul> </li> <li>b. Abort-Reason: <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x00 (undefined)</li> </ul> </li> </ul> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 4 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-008_C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>TP label</b>           | Manager State machine:Configuring Waiting 3                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | ManagerStateMach 27;M                                         |  |
+| <b>Test purpose</b>       | Check that:<br>If PHG receives Rx roiv-* but not matching in any other 6* state while in Waiting state, the PHG shall transmit abrt(Abort-reason undefined) and moves to Unassociated state                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with a dev-config-id set to an id in the extended range unknown to the PHG.</li> <li>2. The PHG under test responds with an Association Response: <ul style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE3 0x00 (AareAdpu)</li> </ul> </li> <li>b. Result <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x03 (accepted-unknown-config)</li> </ul> </li> </ul> </li> <li>3. The simulated PHD sends a "roiv-cmip-confirmed-set".</li> <li>4. The PHG under test responds with an Association Abort message: <ul style="list-style-type: none"> <li>a. APDU Type: <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00</li> </ul> </li> <li>b. Abort-Reason: <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x00 (undefined)</li> </ul> </li> </ul> </li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 4 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-008_D                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |  |
+| <b>TP label</b>           | Manager State machine:Configuring Waiting 4                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | ManagerStateMach 27;M                                         |  |
+| <b>Test purpose</b>       | Check that:<br>If PHG receives Rx roiv-* but not matching in any other 6* state while in Waiting state, the PHG shall transmit an abrt(Abort-reason undefined) and moves to Unassociated state                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+| <b>Test procedure</b>     | 1. The simulated PHD sends an Association Request to the PHG under test with a dev-config-id set to an id in the extended range unknown to the PHG.<br>2. The PHG under test responds with an Association Response:<br>a. APDU Type<br><input type="checkbox"/> field-length = 2 bytes<br><input type="checkbox"/> field-value = 0xE3 0x00 (AareAdpu)<br>b. Result<br><input type="checkbox"/> field-length = 2 bytes<br><input type="checkbox"/> field-value = 0x00 0x03 (accepted-unknown-config)<br>3. The simulated PHD sends a "roiv-cmip-action".<br>4. The PHG under test responds with an Association Abort message:<br>a. APDU Type:<br><input type="checkbox"/> field-length = 2 bytes<br><input type="checkbox"/> field-value = 0xE6 0x00<br>b. Abort-Reason:<br><input type="checkbox"/> field-length = 2 bytes<br><input type="checkbox"/> field-value = 0x00 0x00 (undefined) |                                                               |  |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 4 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+
+|                          |                                                                                                                                                                                                                     |                                                               |  |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/COM/BV-008_E                                                                                                                                                                                         |                                                               |  |
+| <b>TP label</b>          | Manager State machine:Configuring Waiting 5                                                                                                                                                                         |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                         | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                               | ManagerStateMach 27;M                                         |  |
+| <b>Test purpose</b>      | Check that:<br>If PHG receives Rx roiv-* but not matching in any other 6* state while in Waiting state, the PHG shall transmit an abrt(Abort-reason undefined) and moves to Unassociated state                      |                                                               |  |
+| <b>Applicability</b>     | C_MAN_OXP_000                                                                                                                                                                                                       |                                                               |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                     |                                                               |  |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                             |                                                               |  |
+| <b>Test procedure</b>    | 1. The simulated PHD sends an Association Request to the PHG under test with a dev-config-id set to an id in the extended range unknown to the PHG.<br>2. The PHG under test responds with an Association Response: |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ol style="list-style-type: none"> <li>a. APDU Type           <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE3 0x00 (AareAdpu)</li> </ul> </li> <li>b. Result           <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x03 (accepted-unknown-config)</li> </ul> </li> </ol> <ol style="list-style-type: none"> <li>3. The simulated PHD sends a "roiv-cmip-confirmed-action".</li> <li>4. The PHG under test responds with an Association Abort message:           <ol style="list-style-type: none"> <li>a. PDU Type:               <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00</li> </ul> </li> <li>b. Abort-Reason:               <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x00 (undefined)</li> </ul> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 4 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                  |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHG/ OXP/COM/BV-009                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                  |  |
+| <b>TP label</b>          | Invalid Association Request management.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                  |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | ManagerProc 1; M                                              | ManagerProc 2; M |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>When a PHG receives an Association Request, it shall compare the protocol and operating parameters with its own and determine whether the PHD is compatible with the PHG. If the connection is bi-directional, the PHG shall report the outcome of this assessment in the result field of an Association Response.</p> <p>[AND]</p> <p>A PHG may reject the association for any of the possible rejection reasons enumerated in 8.7.3.2. If the PHG rejects the Association, it shall transition to the Unassociated state.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                  |  |
+| <b>Applicability</b>     | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                  |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                  |  |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with the data-proto-id set to a protocol unknown to the PHG.</li> <li>2. The PHG under test responds with an Association Response:               <ol style="list-style-type: none"> <li>a. APDU Type                   <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE3 0x00 (AareAdpu)</li> </ul> </li> <li>b. Result                   <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x04 (rejected-no-common-protocol)</li> </ul> </li> <li>c. Data-Proto                   <ul style="list-style-type: none"> <li><input type="checkbox"/> data-proto-id = 0x00 0x00 (data-proto-id-empty)</li> <li><input type="checkbox"/> data-proto-info = &lt;empty&gt;</li> </ul> </li> </ol> </li> </ol> |                                                               |                  |  |
+
+3. The simulated PHD sends an Association Request to the PHG under test with the data proto-id set to data-proto-id set to "data-proto-id-20601" data-proto-info containing an invalid attribute (encodingRules='0000000000000000'0)
+4. The PHG under test responds with an Association Response:
+  - a. APDU Type
+    - field-length = 2 bytes
+    - field-value = 0xE3 0x00 (AareAdpu)
+  - b. Result
+    - field-length = 2 bytes
+    - field-value = 0x00 0x05 (rejected-no-common-parameters)
+  - c. Data-Proto
+    - data-proto-id = 0x00 0x00 (data-proto-id-empty)
+    - data-proto-info = <empty>
+5. The simulated PHD sends an Association Request to the PHG under test with assoc-version set to an incorrect AssociationVersion
+6. The PHG under test responds with an Association Response:
+  - a. APDU Type
+    - field-length = 2 bytes
+    - field-value = 0xE3 0x00 (AareAdpu)
+  - b. Result
+    - field-length = 2 bytes
+    - field-value = 0x00 0x08 (rejected-unsupported-assoc-version)
+  - c. Data-Proto
+    - data-proto-id = 0x00 0x00 (data-proto-id-empty)
+    - data-proto-info = <empty>
+7. The simulated PHD sends an Association Request to the PHG under test with data-proto-id set to a protocol unknown to the PHG and a data-proto-id set to data-proto-id-20601 as a second option
+8. The PHG under test responds with an Association Response:
+  - a. APDU Type
+    - field-length = 2 bytes
+    - field-value = 0xE3 0x00 (AareAdpu)
+  - b. Result
+    - field-length = 2 bytes
+    - field-value = 0x00 0x00 (accepted) OR 0x00 0x03 (accepted-unknown)
+  - c. Data-Proto
+    - data-proto-id = 0x00 0x00 (data-proto-id-20601)
+9. The simulated PHD sends a Release Request message.
+10. The PHG under test responds with a Release Response message.
+11. The simulated PHD sends an Association Request to the PHG under test with a data-proto-id set to data-proto-id-20601 to the PHG and a data-proto-id set to a protocol unknown as a second option.
+12. The PHG under test responds with an Association Response:
+  - a. APDU Type
+    - field-length = 2 bytes
+    - field-value = 0xE3 0x00 (AareAdpu)
+  - b. Result
+
+|                           |                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x00 (accepted) OR 0x00 0x03 (accepted-unknown)</li> <li>c. Data-Proto <ul style="list-style-type: none"> <li><input type="checkbox"/> data-proto-id = 0x00 0x00 (data-proto-id-20601)</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The format of the received message in steps 2, 4, 6, 8 and 12 must be the ones specified</li> <li>In steps 4 and 6, Aare must be received from the PHG (after rejecting Aarq, the PHG has transitioned to the Unassociated state)</li> </ul>                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                           |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-010                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |
+| <b>TP label</b>           | Configuring.Waiting Config state. Association Request                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | ManagerStateMach 21;M                                         |
+| <b>Test purpose</b>       | Check that:<br>If PHG receives aarq while in Waiting state, the PHG shall transmit an abrt (reason undefined) and move to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+| <b>Initial condition</b>  | The PHG under test is in the waiting for config state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated PHD sends an Association Request to the PHG under test.</li> <li>The PHG under test responds with an Association Abort message and moves to the Unassociated state: <ol style="list-style-type: none"> <li>APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00 (AbrtApdu)</li> </ul> </li> <li>reason <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = Abort-reason</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = One of the following: <ul style="list-style-type: none"> <li>▪ undefined(0)</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                                                               |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+
+|                      |                                                                                                                                                   |                                                               |
+|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>         | TP/PLT/PHG/OXP/COM/BV-011                                                                                                                         |                                                               |
+| <b>TP label</b>      | Configuring.Waiting Config state. Association Response                                                                                            |                                                               |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                      | <b>Testable items</b>                                                                                                                             | ManagerStateMach 22;M                                         |
+| <b>Test purpose</b>  | Check that:<br>If PHG receives aare while in Waiting state, the PHG shall transmit an abrt (reason undefined) and move to the Unassociated state. |                                                               |
+| <b>Applicability</b> | C_MAN_OXP_000                                                                                                                                     |                                                               |
+| <b>Other PICS</b>    |                                                                                                                                                   |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b>  | The PHG under test is in the waiting for config state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Response to the PHG under test.</li> <li>2. The PHG under test responds with an Association Abort message and moves to the Unassociated state: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00 (AbrtApdu)</li> </ol> </li> <li>b. reason <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = Abort-reason</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = One of the following: <ul style="list-style-type: none"> <li>▪ undefined(0)</li> </ul> </li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |
+| <b>TP label</b>           | Configuring.Waiting Config state. Release Request                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | ManagerStateMach 23;M                                         |
+| <b>Test purpose</b>       | Check that:<br>If PHG receives rlrq while in Waiting state, the PHG shall transmit rlre(normal) and move to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |
+| <b>Initial condition</b>  | The PHG under test is in the waiting for config state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Release Request to the PHG under test.</li> <li>2. The PHG under test responds with an Release Response message and moves to the Unassociated state: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE5 0x00 (RlreApdu)</li> </ol> </li> <li>b. reason <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = ReleaseResponseReason</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = normal (0)</li> </ol> </li> </ol> </li> </ol> |                                                               |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |
+
+|                 |                                                    |                                                               |
+|-----------------|----------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHG/OXP/COM/BV-013                          |                                                               |
+| <b>TP label</b> | Configuring.Waiting Config state. Release Response |                                                               |
+| <b>Coverage</b> | <b>Spec</b>                                        | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                 | <b>Testable items</b>                              | ManagerStateMach 24;M                                         |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>       | Check that:<br>If PHG receives rlre while in Waiting state, the PHG shall transmit an abrt(Abort-reason undefined) and move to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Initial condition</b>  | The PHG under test is in the waiting for config state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Release Response to the PHG under test.</li> <li>2. The PHG under test responds with an Association Abort message and moves to the Unassociated state: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00 (AbrtApdu)</li> </ol> </li> <li>b. reason <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = Abort-reason</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = One of the following: <ul style="list-style-type: none"> <li>▪ undefined(0)</li> </ul> </li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-014                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |
+| <b>TP label</b>           | Operating state. Association Request                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | ManagerStateMach 47;M                                         |
+| <b>Test purpose</b>       | Check that:<br>If PHG receives aarq while in Operating state, the PHG shall transmit an abrt (reason undefined) and move to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+| <b>Initial condition</b>  | The PHG under test is in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test.</li> <li>2. The PHG under test responds with an Association Abort message and moves to the Unassociated state: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00 (AbrtApdu)</li> </ol> </li> <li>b. reason <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = Abort-reason</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = One of the following: <ul style="list-style-type: none"> <li>▪ undefined(0)</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                                                               |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-015                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>TP label</b>           | Operating state. Association Response                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ManagerStateMach 48;M                                         |  |
+| <b>Test purpose</b>       | Check that:<br>If PHG receives aare while in Operating state, the PHG shall transmit an abrt(Abort-reason undefined) and move to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |  |
+| <b>Initial condition</b>  | The PHG under test is in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated PHD sends an Association Response to the PHG under test.</li> <li>The PHG under test responds with an Association Abort message and moves to the Unassociated state: <ol style="list-style-type: none"> <li>APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00 (AbrtApdu)</li> </ul> </li> <li>reason <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = Abort-reason</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = One of the following: <ul style="list-style-type: none"> <li>▪ undefined(0)</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/COM/BV-016                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |  |
+| <b>TP label</b>          | Operating state. Release Response                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | ManagerStateMach 50;M                                         |  |
+| <b>Test purpose</b>      | Check that:<br>If PHG receives rlre while in Operating state, the PHG shall transmit an abrt (reason undefined) and move to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Applicability</b>     | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>Initial condition</b> | The PHG under test is in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHD sends a Release Response to the PHG under test.</li> <li>The PHG under test responds with an Association Abort message and moves to the Unassociated state: <ol style="list-style-type: none"> <li>APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00 (AbrtApdu)</li> </ul> </li> <li>reason <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = Abort-reason</li> </ul> </li> </ol> </li> </ol> |                                                               |  |
+
+|                           |                                                                                                                                                                                     |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> field-length = 2 bytes<br><input type="checkbox"/> field-value = One of the following:<br><ul style="list-style-type: none"> <li>▪ undefined(0)</li> </ul> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the PHG moves to the Unassociated state.                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-017                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |
+| <b>TP label</b>           | Disassociating state. Association Request                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | ManagerStateMach 58;M                                         |
+| <b>Test purpose</b>       | Check that:<br>If aarq is received while in Disassociating state, the PHG shall transmit abrt (reason undefined) and move to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_043                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+| <b>Initial condition</b>  | The PHG under test is in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test release the association.</li> <li>2. The simulated PHD responds to the Association Release Request with an Association Request.</li> <li>3. The PHG under test responds with an Association Abort message and moves to the Unassociated state: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00 (AbrtApdu)</li> </ul> </li> <li>b. reason <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = Abort-reason</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = One of the following: <ul style="list-style-type: none"> <li>▪ undefined(0)</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                                                               |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 3 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+
+|                          |                                                                                                                                                          |                                                               |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/COM/BV-018                                                                                                                                |                                                               |
+| <b>TP label</b>          | Disassociating state. Association Response                                                                                                               |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                    | ManagerStateMach 59;M                                         |
+| <b>Test purpose</b>      | Check that:<br>If PHG receives aare while in Disassociating state, the PHG shall transmit an abrt (reason undefined) and move to the Unassociated state. |                                                               |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND C_MAN_OXP_043                                                                                                                          |                                                               |
+| <b>Other PICS</b>        |                                                                                                                                                          |                                                               |
+| <b>Initial condition</b> | The PHG under test is in the Operating state.                                                                                                            |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test release the association.</li> <li>2. The simulated PHD responds to the Association Release Request with an Association Response (AareAPDU).</li> <li>3. The PHG under test responds with an Association Abort message and moves to the Unassociated state: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00 (AbrtApdu)</li> </ol> </li> <li>b. reason <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = Abort-reason</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = One of the following: <ul style="list-style-type: none"> <li>▪ undefined(0)</li> </ul> </li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 3 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/ OXP/COM/BV-019                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |                  |
+| <b>TP label</b>          | Disassociating state. Release Request                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | ManagerStateMach 60;M                                         | DisassocProc 6;M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If PHG receives rlrq while in Disassociating state, the PHG shall transmit rlre(normal) and move to the Unassociated state.</p> <p>[AND]</p> <p>If both the PHG and the PHD simultaneously move to the Disassociating state such that one or both receive an Association Release Request while in the Disassociating state, then the receiver(s) shall respond to the request to avoid deadlock</p> <p>[AND]</p> <p>Note that this also means it is possible to receive an Association Release Request while in the Unassociated state. In such a case, an Association Release Response shall be sent.</p>                                                                                                                                                                                                                                                           |                                                               |                  |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND C_MAN_OXP_043                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |                  |
+| <b>Initial condition</b> | The PHG under test is in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Make the PHG under test release the association.</li> <li>2. The simulated PHD responds to the Association Release Request with an Association Release Request (RlrqApdu).</li> <li>3. The PHG under test responds with an Association Release Response <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00 (RlreApdu)</li> </ol> </li> <li>b. reason <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = ReleaseResponseReason</li> <li><input type="checkbox"/> field-length = 2 bytes (INT-U16)</li> <li><input type="checkbox"/> field-value = normal(0)</li> </ol> </li> </ol> </li> <li>4. The PHD responds to the Rlrq message with an Rlre message.</li> </ol> |                                                               |                  |
+
+|                           |                                                                                                                     |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the PHG moves to the Unassociated state. |
+| <b>Notes</b>              |                                                                                                                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-020_B                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>TP label</b>           | Dissociating state. Rors-cmip-get                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | ManagerStateMach 64;M                                         |  |
+| <b>Test purpose</b>       | Check that:<br>If rors-cmip-get is received while in the Disassociating state, a PHG shall transmit an abrt (reason undefined) and move to Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_043                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+| <b>Initial condition</b>  | The PHG under test is in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test release the association.</li> <li>2. The simulated PHD responds to the Association Release Request with a "rors-cmip-get" (PrstAPDU).</li> <li>3. The PHG under test responds with an Association Abort message and moves to the Unassociated state: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00 (AbrtApdu)</li> </ul> </li> <li>b. reason <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = Abort-reason</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = One of the following: <ul style="list-style-type: none"> <li>▪ undefined(0)</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+
+|                          |                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/COM/BV-020_C                                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>TP label</b>          | Dissociating state. Rors-cmip-confirmed-set                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                   | ManagerStateMach 64;M                                         |  |
+| <b>Test purpose</b>      | Check that:<br>If rors-cmip-confirmed-set is received while in the Disassociating state, a PHG shall transmit an abrt (reason undefined) and move to Unassociated state.                                                                                                                                                |                                                               |  |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND C_MAN_OXP_043                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Initial condition</b> | The PHG under test is in the Operating state.                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Make the PHG under test release the association.</li> <li>2. The simulated PHD responds to the Association Release Request with a "rors-cmip-confirmed-set" (PrstAPDU).</li> <li>3. The PHG under test responds with an Association Abort message and moves to the</li> </ol> |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | Unassociated state:<br>a. APDU Type<br><input type="checkbox"/> field-length = 2 bytes<br><input type="checkbox"/> field-value = 0xE6 0x00 (AbrtApdu)<br>b. reason<br><input type="checkbox"/> field-type = Abort-reason<br><input type="checkbox"/> field-length = 2 bytes<br><input type="checkbox"/> field-value = One of the following:<br><ul style="list-style-type: none"> <li>▪ undefined(0)</li> </ul> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-020_D                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |
+| <b>TP label</b>           | Dissociating state. Rors-cmip-confirmed-action                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | ManagerStateMach 64;M                                         |
+| <b>Test purpose</b>       | Check that:<br>If rors-cmip-confirmed-action is received while in the Disassociating state, a PHG shall transmit an abrt (reason undefined) and move to Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_043                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |
+| <b>Initial condition</b>  | The PHG under test is in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |
+| <b>Test procedure</b>     | 1. Make the PHG under test release the association.<br>2. The simulated PHD responds to the Association Release Request with a "rors-cmip-confirmed-action" (PrstAPDU).<br>3. The PHG under test responds with an Association Abort message and moves to the Unassociated state:<br>a. APDU Type<br><input type="checkbox"/> field-length = 2 bytes<br><input type="checkbox"/> field-value = 0xE6 0x00 (AbrtApdu)<br>b. reason<br><input type="checkbox"/> field-type = Abort-reason<br><input type="checkbox"/> field-length = 2 bytes<br><input type="checkbox"/> field-value = One of the following:<br><ul style="list-style-type: none"> <li>▪ undefined(0)</li> </ul> |                                                               |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |
+
+|                 |                             |                                                               |
+|-----------------|-----------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHG/OXP/COM/BV-020_E |                                                               |
+| <b>TP label</b> | Dissociating state. Roer    |                                                               |
+| <b>Coverage</b> | <b>Spec</b>                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                 | <b>Testable items</b>       | ManagerStateMach 64;M                                         |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>       | Check that:<br>If roer is received while in the Disassociating state, a PHG shall transmit an abrt (reason undefined) and move to Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_043                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Initial condition</b>  | The PHG under test is in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test release the association.</li> <li>2. The simulated PHD responds to the Association Release Request with a "roer" (PrstAPDU).</li> <li>3. The PHG under test responds with an Association Abort message and moves to the Unassociated state: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00 (AbrtApdu)</li> </ol> </li> <li>b. reason <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = Abort-reason</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = One of the following: <ul style="list-style-type: none"> <li>▪ undefined(0)</li> </ul> </li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+|                          |                                                                                                                                                       |                                                               |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/EXP/COM/BV-020_F                                                                                                                           |                                                               |
+| <b>TP label</b>          | Dissociating state. Rorj                                                                                                                              |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                           | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                 | ManagerStateMach 64;M                                         |
+| <b>Test purpose</b>      | Check that:<br>If rorj is received while in the Disassociating state, a PHG shall transmit an abrt (reason undefined) and move to Unassociated state. |                                                               |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND C_MAN_OXP_043                                                                                                                       |                                                               |
+| <b>Other PICS</b>        |                                                                                                                                                       |                                                               |
+| <b>Initial condition</b> | The PHG under test is in the Operating state.                                                                                                         |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test release the association.</li> <li>2. The simulated PHD responds to the Association Release Request with a "rorj" (PrstAPDU).</li> <li>3. The PHG under test responds with an Association Abort message and moves to the Unassociated state: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00 (AbrtApdu)</li> </ul> </li> <li>b. reason <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = Abort-reason</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = One of the following: <ul style="list-style-type: none"> <li>▪ undefined(0)</li> </ul> </li> </ul> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |  |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|--|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-022_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |  |
+| <b>TP label</b>           | Encoding Rules. MDER and XER                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | AssocResp 2;M                                                 |  |  |
+| <b>Test purpose</b>       | Check that:<br>The encoding-rules field contains the one and only one DataApdu encoding rule shall be chosen by the PHG, if the result field is equal to accepted or accepted-unknown-config                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |  |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |  |
+| <b>Initial condition</b>  | The PHG under test is in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with the encoding rules filed set to MDER and XER.</li> <li>2. The PHG under test must respond with an Association Response, the field of interest is: <ol style="list-style-type: none"> <li>a. Encoding rules <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = ProtocolVersion</li> <li><input type="checkbox"/> field-length = 2 bytes (BITS-16)</li> <li><input type="checkbox"/> field-value = only one bit is set</li> </ul> </li> </ol> </li> </ol> |                                                               |  |  |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the selected encoding rules must be either MDER or XER.                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |  |
+
+|                     |                              |                                                               |  |  |
+|---------------------|------------------------------|---------------------------------------------------------------|--|--|
+| <b>TP Id</b>        | TP/PLT/PHG/OXP/COM/BV-022_B  |                                                               |  |  |
+| <b>TP label</b>     | Encoding Rules. MDER and PER |                                                               |  |  |
+| <b>Coverage</b>     | <b>Spec</b>                  | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |  |
+|                     | <b>Testable items</b>        | AssocResp 2;M                                                 |  |  |
+| <b>Test purpose</b> | Check that:                  |                                                               |  |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | The encoding-rules field contains the one and only one DataApdu encoding rule shall be chosen by the PHG, if the result field is equal to accepted or accepted-unknown-config                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Initial condition</b>  | The PHG under test is in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with the encoding rules field set to MDER and PER.</li> <li>2. The PHG under test must respond with an Association Response, the field of interest is: <ol style="list-style-type: none"> <li>a. Encoding rules <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = ProtocolVersion</li> <li><input type="checkbox"/> field-length = 2 bytes (BITS-16)</li> <li><input type="checkbox"/> field-value = only one bit is set</li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the selected encoding rules must be either MDER or PER.                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-022_C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |
+| <b>TP label</b>           | Encoding Rules. MDER, XER and PER                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | AssocResp 2;M                                                 |
+| <b>Test purpose</b>       | Check that:<br>The encoding-rules field contains the one and only one DataApdu encoding rule shall be chosen by the PHG, if the result field is equal to accepted or accepted-unknown-config                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |
+| <b>Initial condition</b>  | The PHG under test is in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with the encoding rules field set to MDER, XER and PER.</li> <li>2. The PHG under test must respond with an Association Response, the field of interest is: <ol style="list-style-type: none"> <li>a. Encoding rules <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = ProtocolVersion</li> <li><input type="checkbox"/> field-length = 2 bytes (BITS-16)</li> <li><input type="checkbox"/> field-value = only one bit is set</li> </ol> </li> </ol> </li> </ol> |                                                               |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the selected encoding rules must be MDER or XER or PER.                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |
+
+|                     |                                                                             |                                                               |
+|---------------------|-----------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>        | TP/PLT/PHG/OXP/COM/BV-023                                                   |                                                               |
+| <b>TP label</b>     | Encoding Rules. MDER                                                        |                                                               |
+| <b>Coverage</b>     | <b>Spec</b>                                                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                     | <b>Testable items</b>                                                       | AssocResp 3;M      MessageEncod 1;M                           |
+| <b>Test purpose</b> | Check that:<br>The PHG shall always support MDER enabling interoperability. |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | [AND]<br>Both PHG and PHD shall support the Medical Device Encoding Rules (MDER) as defined in ISO/IEEE Std 11073-20101.                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Initial condition</b>  | The PHG under test is in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with the encoding rules field set to MDER.</li> <li>2. The PHG under test must respond with an Association Response, the field of interest is: <ol style="list-style-type: none"> <li>a. Encoding rules <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = ProtocolVersion</li> <li><input type="checkbox"/> field-length = 2 bytes (BITS-16)</li> <li><input type="checkbox"/> field-value = bit 0 must be set</li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |                           |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/COM/BV-031                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                           |
+| <b>TP label</b>          | Operating procedures. Persistently stored metric data transfer 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |                           |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                           |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | PersStoreMtrDatTransf 1;O                                     | PersStoreMtrDatTransf 2;C |
+| <b>Test purpose</b>      | Check that:<br><br>If the PHG queries each PM-Store to determine the number of PM-Segments that exist within the PM-Store, the attribute-id-list shall be left empty to query for all attributes of the PM-store object.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                           |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND C_MAN_OXP_003 AND C_MAN_OXP_048                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                           |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |                           |
+| <b>Initial condition</b> | The PHG under test is in the Operating state. The simulated PHD has one PM-Store.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                           |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Make the PHG under test perform a GET service to the PM-Store.</li> <li>2. The received message by the simulated PHD must be: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ol> </li> <li>b. invoke-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>c. CHOICE: <ol style="list-style-type: none"> <li><input type="checkbox"/> field-value = 0x01 0x03 (roiv-cmip-get)</li> </ol> </li> <li>d. obj-Handle: <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = &lt;The handle of the simulated PHD's PM-Store&gt;</li> </ol> </li> <li>e. attribute-Id-List: <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = AttributeIdList</li> </ol> </li> </ol> </li> </ol> |                                                               |                           |
+
+|                           |                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> field-count = 0x00 0x00<br><input type="checkbox"/> field-length = 0x00 0x00 |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified.                               |
+| <b>Notes</b>              |                                                                                                       |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                            |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|----------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/COM/BV-032                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |                            |
+| <b>TP label</b>          | Operating procedures. Persistently stored metric data transfer 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |                            |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                            |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | PersStoreMtrDatTransf 16;M                                    | PersStoreMtrDatTransf 17;M |
+| <b>Test purpose</b>      | Check that:<br><br>When the PHG receives an Event report, it shall reply with a SegmentDataResult response that shall contain the same store-handle, segm-instance number, segm-evt-entry-index, and segm-evt-entry-count.<br><br>[AND]<br><br>In the segm-evt-status, the PHG shall set the sevsta-manager-confirm bit.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                            |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND C_MAN_OXP_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                            |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |                            |
+| <b>Initial condition</b> | The PHG under test is in the Operating state. The simulated PHD has one PM-Store with at least one Segment that contains data.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                            |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Make the PHG under test retrieve the information stored in a PM-Segment.</li> <li>2. The simulated PHD responds to the TrigSegmDataXferReq with an appropriate TrigSegmDataXferRsp message.</li> <li>3. The simulated PHD sends a SegmentDataEvent to the PHG.</li> <li>4. The PHG under test must respond with a SegmentDataResult message, the fields of interest are: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ul> </li> <li>b. invoke-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = &lt;The same of the sent SegmentDataEvent&gt;</li> </ul> </li> <li>c. CHOICE: <ul style="list-style-type: none"> <li><input type="checkbox"/> field-value = 0x02 0x01 (rors-cmip-confirmed-event-report)</li> </ul> </li> <li>d. Obj-Handle: <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE <ul style="list-style-type: none"> <li>• field-length = 2 bytes</li> <li>• field-value = &lt; The same of the sent SegmentDataEvent &gt;</li> </ul> </li> </ul> </li> <li>e. CurrentTime <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = RelativeTime</li> <li><input type="checkbox"/> field-length = 4 bytes</li> <li><input type="checkbox"/> field-value = &lt;Not relevant for this test&gt;</li> </ul> </li> <li>f. event-type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = OID-Type</li> <li><input type="checkbox"/> field-length = 2 bytes</li> </ul> </li> </ol> </li> </ol> |                                                               |                            |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> field-value = 0x0D 0x21 (MDC_NOTI_SEGMENT_DATA)<br>g. SegmentDataResult<br><input type="checkbox"/> field-length = 12 bytes<br><input type="checkbox"/> field-value = <ul style="list-style-type: none"> <li>• segm-instance.value = &lt; The same of the sent SegmentDataEvent &gt;</li> <li>• segm-evt-entry-index.value = &lt; The same of the sent SegmentDataEvent &gt;</li> <li>• segm-evt-entry-count.value = &lt; The same of the sent SegmentDataEvent &gt;</li> <li>• segm-evt-status.value = Bit 8 (sevtsta-manager-confirm)</li> </ul> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 4 must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-033_A                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |
+| <b>TP label</b>           | Operating procedures. Error conditions. Timeout confirmed action 1                                                                                                                                                                                                                                                                                                                                                                    |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                 | OperErrorCond 3;M      OperErrorCond 4;M                      |
+| <b>Test purpose</b>       | Check that:<br><br>After sending a Confirmed Action invoke message, the PHG shall wait for a Confirmed Action response message for a TOca (timeout: confirmed action service) period by default unless another timeout applies (e.g., TOclr-pms overrides TOca as described in 8.9.5.6)....<br>[AND]<br>If the TOca expires, the PHG shall send an Association Abort message to the PHD and transition back to the Unassociated state |                                                               |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |
+| <b>Initial condition</b>  | The PHG under test is in the Operating state. The PHD has a MDSTimeInfo attribute which indicates that it supports settable time and Absolute Time and Relative Time and the PHG is encouraged to set the time.                                                                                                                                                                                                                       |                                                               |
+| <b>Test procedure</b>     | 1. Make the PHG under test set the Absolute Time of the simulated PHD.<br>2. The simulated PHD does not answer to the confirmed action for at least TOca time.                                                                                                                                                                                                                                                                        |                                                               |
+| <b>Pass/Fail criteria</b> | The PHG under test must wait for a Confirmed Action Report Response message for a TOca period. When the time expires, the PHG under test must send an abort to the simulated PHD and moves to the Unassociated state.                                                                                                                                                                                                                 |                                                               |
+| <b>Notes</b>              | Due to the delay introduced by the transport layer and decoder for the received APDU, the test tool accuracy may not be enough to measure this time-out. To get better accuracy, it is necessary to run this test case using a hardware sniffer.                                                                                                                                                                                      |                                                               |
+
+|                     |                                                                                                                                                                                                                                                                                                      |                                                               |
+|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>        | TP/PLT/PHG/OXP/COM/BV-033_B                                                                                                                                                                                                                                                                          |                                                               |
+| <b>TP label</b>     | Operating procedures. Error conditions. Timeout confirmed action 2                                                                                                                                                                                                                                   |                                                               |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                                | OperErrorCond 3;M      OperErrorCond 4;M                      |
+| <b>Test purpose</b> | Check that:<br><br>After sending a Confirmed Action invoke message, the PHG shall wait for a Confirmed Action response message for a TOca (timeout: confirmed action service) period by default unless another timeout applies (e.g., TOclr-pms overrides TOca as described in 8.9.5.6)....<br>[AND] |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                             |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | If the TOca expires, the PHG shall send an Association Abort message to the PHD and transition back to the Unassociated state                                                                                                                                               |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_003                                                                                                                                                                                                                                             |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                             |
+| <b>Initial condition</b>  | The PHG under test is in the Operating state, the PHD has one PM-Store.                                                                                                                                                                                                     |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>If the PHG did not perform a GetSegmentInfo on its own, make the PHG under test perform a GetSegmentInfo action.</li> <li>In both cases the simulated PHD does not answer to the confirmed action for at least TOca time.</li> </ol> |
+| <b>Pass/Fail criteria</b> | The PHG under test must wait for a Confirmed Action Report message for a TOca period. When the time expires, the PHG under test must send an abort to the simulated PHD and moves to the Unassociated state.                                                                |
+| <b>Notes</b>              | Due to the delay introduced by the transport layer and decoder for the received APDU, the test tool accuracy may not be enough to measure this time-out. To get better accuracy, it is necessary to run this test case using a hardware sniffer.                            |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHG/EXP/COM/BV-035_A                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>TP label</b>           | Operating procedures. Error conditions. Timeout Get service 1                                                                                                                                                                                                                                                                                              |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                      | OperErrorCond 8;M                                             |  |
+| <b>Test purpose</b>       | Check that:<br>If the RTOget expires, the PHG shall send an Association Abort message to its peer and transition back to the Unassociated state.                                                                                                                                                                                                           |                                                               |  |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                              |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>Initial condition</b>  | The PHG under test is in the Operating state.                                                                                                                                                                                                                                                                                                              |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>If the PHG under test did not send automatically a GET request for the MDS object, make the PHG under test perform a GET for the MDS object.</li> <li>Whether it was an automatic behaviour of the PHG under test or a forced one, the simulated PHD does not answer to the GET for at least TOget time.</li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | The PHG under test must wait for a Confirmed Event Report Response message for a TOget period. When the time expires, the PHG under test must send an abort to the simulated PHD and moves to the Unassociated state.                                                                                                                                      |                                                               |  |
+| <b>Notes</b>              | Due to the delay introduced by the transport layer and decoder for the received APDU, the test tool accuracy may not be enough to measure this time-out. To get better accuracy, it is necessary to run this test case using a hardware sniffer.                                                                                                           |                                                               |  |
+
+|                          |                                                                                                                                                 |                                                               |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHG/EXP/COM/BV-035_B                                                                                                                     |                                                               |  |
+| <b>TP label</b>          | Operating procedures. Error conditions. Timeout Get service 2                                                                                   |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                     | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                           | OperErrorCond 8;M                                             |  |
+| <b>Test purpose</b>      | Check that:<br>If the TOget expires, the PHG shall send an Association Abort message to its peer and transition back to the Unassociated state. |                                                               |  |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND C_MAN_OXP_003 AND C_MAN_OXP_048                                                                                               |                                                               |  |
+| <b>Other PICS</b>        |                                                                                                                                                 |                                                               |  |
+| <b>Initial condition</b> | The PHG under test is in the Operating state.                                                                                                   |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. If the PHG under test did not send automatically a GET Service to the PM-Store object, make the PHG under test perform a GET to the PM-Store object.</li> <li>2. Whether it was an automatic behaviour of the PHG under test or a forced one, the simulated PHD does not answer to the GET for at least TO<sub>get</sub> time.</li> </ol> |
+| <b>Pass/Fail criteria</b> | The PHG under test must wait for a Confirmed Event Report Response message for a TO <sub>get</sub> period. When the time expires, the PHG under test must send an abort to the simulated PHD and moves to the Unassociated state.                                                                                                                                                   |
+| <b>Notes</b>              | Due to the delay introduced by the transport layer and decoder for the received APDU, the test tool accuracy may not be enough to measure this time-out. To get better accuracy, it is necessary to run this test case using a hardware sniffer.                                                                                                                                    |
+
+|                           |                                                                                                                                                                                                                                                  |                                                               |  |  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|--|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-036_B                                                                                                                                                                                                                      |                                                               |  |  |
+| <b>TP label</b>           | Operating procedures. Error conditions. Timeout Set service                                                                                                                                                                                      |                                                               |  |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                      | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                            | OperErrorCond 10;M                                            |  |  |
+| <b>Test purpose</b>       | Check that:<br>If the TO <sub>cs</sub> expires, the PHG shall send an Association Abort message to the PHD and transition back to the Unassociated state                                                                                         |                                                               |  |  |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND (C_MAN_OXP_006 OR C_MAN_OXP_001)                                                                                                                                                                                               |                                                               |  |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                  |                                                               |  |  |
+| <b>Initial condition</b>  | The PHG under test is in the Operating state, the simulated PHD's scanner is disabled.                                                                                                                                                           |                                                               |  |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test perform a SET Service to the Scanner's OperationalState.</li> <li>2. The simulated PHD does not answer to the SET for at least TO<sub>cs</sub> time.</li> </ol>                |                                                               |  |  |
+| <b>Pass/Fail criteria</b> | The PHG under test must wait for a Confirmed Event Report Response message for a TO <sub>cs</sub> period. When the time expires, the PHG under test must send an abort to the simulated PHD and moves to the Unassociated state.                 |                                                               |  |  |
+| <b>Notes</b>              | Due to the delay introduced by the transport layer and decoder for the received APDU, the test tool accuracy may not be enough to measure this time-out. To get better accuracy, it is necessary to run this test case using a hardware sniffer. |                                                               |  |  |
+
+|                          |                                                                                                                                                                                                                                                                                                                   |                                                               |                     |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/COM/BV-037                                                                                                                                                                                                                                                                                         |                                                               |                     |  |
+| <b>TP label</b>          | Operating procedures. Error conditions. Timeout clear-segments                                                                                                                                                                                                                                                    |                                                               |                     |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                     |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                             | OperErrorCond 12;M                                            | StoreClassAttr 10;M |  |
+| <b>Test purpose</b>      | Check that:<br>If, after the PHG sends an Invoke Confirmed Action (Clear Segment) command, the TO <sub>clr-pms</sub> expires prior to the PHG receiving the corresponding Response Confirmed Action message, the PHG shall send an Association Abort message to the PHD and transition to the Unassociated state. |                                                               |                     |  |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND C_MAN_OXP_003 AND (C_MAN_OXP_040 OR C_MAN_OXP_041 OR C_MAN_OXP_042)                                                                                                                                                                                                                             |                                                               |                     |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                   |                                                               |                     |  |
+| <b>Initial condition</b> | The PHG under test is in the Operating state and the simulated PHD has at least one segment with data.                                                                                                                                                                                                            |                                                               |                     |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Make the PHG under test perform a ClearSegment action to one of the simulated PHD's segments.</li> <li>2. The simulated PHD does not answer to the ClearSegment for at least TO<sub>cer-pms</sub> time.</li> </ol>                                                      |                                                               |                     |  |
+
+|                           |                                                                                                                                                                                                                                                  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | The PHG under test must wait for a Confirmed Action Report message for a TOclr-pms period (as stated in the PMS.Clear-Timeout attribute). When the time expires, the PHG under test must send an abort to the simulated PHD.                     |
+| <b>Notes</b>              | Due to the delay introduced by the transport layer and decoder for the received APDU, the test tool accuracy may not be enough to measure this time-out. To get better accuracy, it is necessary to run this test case using a hardware sniffer. |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                     |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/EXP/COM/BV-039                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |                     |
+| <b>TP label</b>           | Operating procedures. Error conditions. Timeout special segment transfer of the PM-Store object                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                     |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                     |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | PM-SegmAttr 14;M                                              | PM-SegmAttr 15;M    |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | OperErrorCond 15; M                                           | OperErrorCond 17; M |
+| <b>Test purpose</b>       | Check that:<br><br>If the TOsp-pms expires (minimum time that the PHG shall wait for the complete transfer of PM-Segment information), the PHG shall send an Association Abort message to the PHD and transition back to the Unassociated state.<br><br>[AND]<br><br>After sending a Confirmed Action (MDC_ACT_SEG_TRIG_XFER) invoke message and receiving the response, the PHG shall wait up to a TOsp-pms (timeout: special segment transfer timeout of the PM-store object) period for a Confirmed Event Report (segm-evt-status=sevtsta-last-entry, semg-data-event-entries) invoke message |                                                               |                     |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                     |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |                     |
+| <b>Initial condition</b>  | The PHG under test is in the Operating state and the simulated PHD has at least one segment with data.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                     |
+| <b>Test procedure</b>     | 1. Make the PHG under test perform a Trig-Segment-Data-Xfer.<br>2. The simulated PHD sends a TriggerResponse with TrigSegmXferRsp = tsxr_successful.<br>3. The PHD does not send any SegmentData Event for at least TOsp-pms time.                                                                                                                                                                                                                                                                                                                                                               |                                                               |                     |
+| <b>Pass/Fail criteria</b> | The PHG under test must wait for the last SegmentData Event message for a TOsp-pms period (as stated in the Transfer-Timeout attribute). When the time expires, the PHG under test must send an abort to the simulated PHD.                                                                                                                                                                                                                                                                                                                                                                      |                                                               |                     |
+| <b>Notes</b>              | Due to the delay introduced by the transport layer and decoder for the received APDU, the test tool accuracy may not be enough to measure this time-out. To get better accuracy, it is necessary to run this test case using a hardware sniffer.                                                                                                                                                                                                                                                                                                                                                 |                                                               |                     |
+
+|                          |                                                                                                                                          |                                                               |  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHG/EXP/COM/BV-040                                                                                                                |                                                               |  |
+| <b>TP label</b>          | Disassociating procedure. Association Release Reason                                                                                     |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                    | DisassocProc 2;M                                              |  |
+| <b>Test purpose</b>      | Check that:<br><br>The Association Release Request contains a ReleaseRequestReason to indicate the reason for releasing the association. |                                                               |  |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND C_MAN_OXP_043                                                                                                          |                                                               |  |
+| <b>Other PICS</b>        |                                                                                                                                          |                                                               |  |
+| <b>Initial condition</b> | The PHG under test is in the Operating state.                                                                                            |                                                               |  |
+| <b>Test procedure</b>    | 1. Make the PHG under test release the Association.<br>2. The received message by the simulated PHD must be:                             |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | a. APDU Type:<br><ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE4 0x00 (RlrqApdu)</li> </ul> b. Reason<br><ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = ReleaseRequestReason</li> <li><input type="checkbox"/> field-length = 2 bytes (INT-U16)</li> <li><input type="checkbox"/> field-value = One of the following:</li> <ul style="list-style-type: none"> <li>▪ normal (0)</li> </ul> </ul> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                           |                                                               |                  |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-042                                                                                                                                                                                                                                                                                                                                 |                                                               |                  |
+| <b>TP label</b>           | Disassociating procedure. Association Release Request Reason 2                                                                                                                                                                                                                                                                                            |                                                               |                  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                               | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                     | DisassocProc 8;M                                              | DisassocProc 9;M |
+| <b>Test purpose</b>       | Check that:<br><br>After sending an Association Release message, the PHG shall wait for an Association Release Response message for a TOrelease (timeout: association release procedure) period.<br><br>[AND]<br><br>If the TOrelease expires, the PHG shall send an Association Abort message to its peer and transition back to the Unassociated state. |                                                               |                  |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_043                                                                                                                                                                                                                                                                                                                           |                                                               |                  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                           |                                                               |                  |
+| <b>Initial condition</b>  | The PHG under test is in the Operating state.                                                                                                                                                                                                                                                                                                             |                                                               |                  |
+| <b>Test procedure</b>     | 1. Make the PHG under test release the Association.<br>2. The simulated PHD does not send any message for at least the Torelease time.                                                                                                                                                                                                                    |                                                               |                  |
+| <b>Pass/Fail criteria</b> | The PHG under test must wait for a Release Response message for a Torelease period. When the time expires, the PHG under test must send an abort to the simulated PHD.                                                                                                                                                                                    |                                                               |                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                           |                                                               |                  |
+
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |                      |
+|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|----------------------|
+| <b>TP Id</b>         | TP/PLT/PHG/OXP/COM/BV-043                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |                      |
+| <b>TP label</b>      | Unrecognized standard configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |                      |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |                      |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | ConfNormalProc 18;C                                           | ConfNormalProc 24; O |
+| <b>Test purpose</b>  | Check that:<br><br>If the PHG does not recognize the standard configuration (e.g., the PHG was released prior to the device specialization being released), it shall send a response of standard-config-unknown.<br><br>[AND]<br><br>If the PHG is able to interoperate with the provided standard configuration, it may accept that configuration. If the PHG stores configurations, it may store this configuration for future reference when any PHD uses this standard configuration identification and henceforth treat the configuration as recognized. |                                                               |                      |
+| <b>Applicability</b> | C_MAN_OXP_000 AND NOT(C_MAN_OXP_032) AND (C_MAN_OXP_016 OR<br>C_MAN_OXP_018 OR C_MAN_OXP_019 OR C_MAN_OXP_020 OR C_MAN_OXP_024                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | OR C_MAN_OXP_025 OR C_MAN_OXP_026 OR C_MAN_OXP_027 OR<br>C_MAN_OXP_029 OR C_MAN_OXP_067 OR C_MAN_OXP_071 OR C_MAN_OXP_073<br>OR C_MAN_OXP_076 OR C_MAN_OXP_077)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Other PICS</b>        | C_MAN_OXP_046, C_MAN_OXP_085                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Initial condition</b> | The PHG under test is in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request with the attribute dev-config-id set to the standard configuration defined in the device specialization.</li> <li>2. The PHG under test sends an Association Response with the result = "accepted-unknown-config".</li> <li>3. The simulated PHD sends a Configuration Event Report with the config-report-id set to the same dev-config-id of step 1 and an empty ConfigObjectList.</li> <li>4. The PHG under test must respond with a "rors-cmip-confirmed-event-report" and the fields of interest are: <ol style="list-style-type: none"> <li>a. ConfigReportRsp.config-report-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = It must be the same as the device-config-id of the simulated PHD's message</li> </ol> </li> <li>b. ConfigReportRsp.config-result <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x02 (standard-config-unknown)</li> </ol> </li> </ol> </li> <li>5. The simulated PHD sends the full configuration information (ConfigObjectList completed, no empty).</li> <li>6. The PHG under test must respond with a "rors-cmip-confirmed-event-report" and the fields of interest are: <ol style="list-style-type: none"> <li>a. ConfigReportRsp.config-report-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = It must be the same as the device-config-id of the simulated PHD's message</li> </ol> </li> <li>b. ConfigReportRsp.config-result <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x00 (accepted-config) or 0x00 0x01 (unsupported-config)</li> </ol> </li> </ol> </li> <li>7. IF C_MAN_OXP_085 THEN: <ol style="list-style-type: none"> <li>a. The simulated PHD moves to Configuring/Waiting GetMDS.</li> <li>b. PHG under test issues a roiv-cmip-get command.</li> <li>c. The simulated PHD sends a rors-cmip-get with MDS attributes, and moves to Operating.</li> </ol> </li> <li>8. IF the PHG and the simulated PHD are in the Operating state, the simulated PHD sends a Rlrq(normal) to the PHG. If the PHG and the simulated PHD are in the Configuring state, the simulated PHD sends an Rlrq (no-more-configurations) to the PHG.</li> <li>9. The PHG sends a Release Response.</li> <li>10. IF C_MAN_OXP_046 = TRUE, the simulated PHD sends an aarq with the config-report-id set to the same dev-config-id of step 1, the PHG under test may respond with an Association Response: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE3 0x00 (AareAdpu)</li> </ol> </li> <li>b. Result <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x00 (accepted-config)</li> </ol> </li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | The PHG under test must respond with a "standard-config-unknown" result in step 4. In step 6 and 10, the PHG may accept the configuration.                                                                                                                                                                                                                               |
+| <b>Notes</b>              | At this moment, all Continua Device Specs only support the Standard Dev-Config-id defined in the Device Specialization spec, and according to subsection 7.4.3.5.1 "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 in that particular standard." |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-044                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>TP label</b>           | Extended configuration - Empty ConfigObjectList                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | ConfNormalProc 26;M                                           |  |
+| <b>Test purpose</b>       | Check that:<br>A PHD may send an extended configuration with an empty config-object-list. This can happen, for instance, when a PHD accepts plug-in components, but presently does not have any inserted. The PHG responds with either accepted-config or unsupported-config.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+| <b>Initial condition</b>  | The PHG under test is in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request with the attribute dev-config-id set to an extended configuration.</li> <li>2. The PHG under test sends an Association Response with the result = "accepted-unknown-config".</li> <li>3. The simulated PHD sends a Configuration Event Report with config-report-id set to the same dev-config-id of step 1 and an empty ConfigObjectList.</li> <li>4. The PHG under test must respond with a "rors-cmip-confirmed-event-report" and the fields of interest are: <ol style="list-style-type: none"> <li>a. ConfigReportRsp.config-report-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = It must be the same as the device-config-id of the simulated PHD's message</li> </ul> </li> <li>b. ConfigReportRsp.config-result <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x00 (accepted-config) or 0x00 0x01(unsupported-config)</li> </ul> </li> </ol> </li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | The PHG under test must respond with an "accepted-config" or an "unsupported-config" result in step 4.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+
+|                      |                                                                                                                      |                                                               |  |
+|----------------------|----------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>         | TP/PLT/PHG/OXP/COM/BV-045                                                                                            |                                                               |  |
+| <b>TP label</b>      | Get Specific Attribute List PM-Store                                                                                 |                                                               |  |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                          | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                      | <b>Testable items</b>                                                                                                | PersStoreMtrDatTransf 2;C                                     |  |
+| <b>Test purpose</b>  | Check that:<br>Specific attributes of an object may be queried by listing the desired Attribute IDs found in Table 9 |                                                               |  |
+| <b>Applicability</b> | C_MAN_OXP_000 AND C_MAN_OXP_003 AND C_MAN_OXP_049                                                                    |                                                               |  |
+| <b>Other PICS</b>    |                                                                                                                      |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b>  | The PHG under test is in the Operating state. The simulated PHD has one PM-Store.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test perform a GET request to a specific list of PM-Store attributes.</li> <li>2. The received message by the simulated PHD must be: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00 (PrstApdu)</li> </ol> </li> <li>b. invoke-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = InvokeIDType</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>c. CHOICE: <ol style="list-style-type: none"> <li><input type="checkbox"/> field-value = 0x01 0x03 (roiv-cmip-get)</li> </ol> </li> <li>d. Obj-Handle: <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = HANDLE</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = &lt;The handle of the simulated PHD's PM-Store&gt;</li> </ol> </li> <li>e. Attribute-Id-List: <ol style="list-style-type: none"> <li><input type="checkbox"/> field-type = AttributeIdList</li> <li><input type="checkbox"/> field-count = &lt;It contains one attribute or more&gt;</li> <li><input type="checkbox"/> field-value = &lt;Attribute-Id match Attribute-id defined for PM-Store attributes (Table 9)&gt;</li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/ OXP/COM/BV-046                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |
+| <b>TP label</b>          | Manager State machine:Configuring Waiting. Corrupt-unknown-unexpected APDU                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | ManagerStateMach 78;M                                         |
+| <b>Test purpose</b>      | Check that:<br><br>If prst (Any APDU not covered in 6.* (corrupt, unknown, unexpected, etc.) received while in Configuring-Waiting state, a PHG shall transmit an abrt(Abort-reason undefined) and remain in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |
+| <b>Applicability</b>     | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test with a dev-config-id set to an id in the extended range unknown to the PHG.</li> <li>2. The PHG under test responds with an Association Response: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE3 0x00 (AareAdpu)</li> </ol> </li> <li>b. Result <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x03 (accepted-unknown-config)</li> </ol> </li> </ol> </li> </ol> |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>3. The simulated PHD sends an invalid apdu.</p> <p>4. The PHG under test responds with an Association Abort message:</p> <p>a. APDU Type:</p> <p><input type="checkbox"/> field-length = 2 bytes</p> <p><input type="checkbox"/> field-value = 0xE6 0x00</p> <p>b. Abort-Reason:</p> <p><input type="checkbox"/> field-length = 2 bytes</p> <p><input type="checkbox"/> field-value = 0x00 0x00 (undefined)</p> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 4 must be the one specified.                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>              | TP/PLT/PHG/ OXP/COM/BV-047                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |
+| <b>TP label</b>           | Manager State machine:Operating. Corrupt-unknown-unexpected APDU                                                                                                                                                                                                                                                                                                                                                   |                                                               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                              | ManagerStateMach 80;M                                         |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>If prst (Any APDU not covered in 8.* (corrupt, unknown, unexpected, etc.) received while in Operating state, a PHG shall transmit an abrt(Abort-reason undefined) and remain in the Unassociated state.</p>                                                                                                                                                                                  |                                                               |
+| <b>Applicability</b>      | C_MAN_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |
+| <b>Initial condition</b>  | The PHG under test is in the Operating state.                                                                                                                                                                                                                                                                                                                                                                      |                                                               |
+| <b>Test procedure</b>     | <p>1. The simulated PHD sends an invalid apdu.</p> <p>2. The PHG under test responds with an Association Abort message:</p> <p>a. APDU Type:</p> <p><input type="checkbox"/> field-length = 2 bytes</p> <p><input type="checkbox"/> field-value = 0xE6 0x00</p> <p>b. Abort-Reason:</p> <p><input type="checkbox"/> field-length = 2 bytes</p> <p><input type="checkbox"/> field-value = 0x00 0x00 (undefined)</p> |                                                               |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified.                                                                                                                                                                                                                                                                                                                                            |                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |
+
+|                      |                                                                                                                                                                                                                                        |                                                               |
+|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>         | TP/PLT/PHG/ OXP/COM/BV-048                                                                                                                                                                                                             |                                                               |
+| <b>TP label</b>      | Manager State machine:Disassociating. Corrupt-unknown-unexpected APDU                                                                                                                                                                  |                                                               |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                            | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                  | ManagerStateMach 81;M                                         |
+| <b>Test purpose</b>  | <p>Check that:</p> <p>If prst (Any APDU not covered in 9.* (corrupt, unknown, unexpected, etc.) received while in disassociating state, a PHG shall transmit an abrt(Abort-reason undefined) and remain in the Unassociated state.</p> |                                                               |
+| <b>Applicability</b> | C_MAN_OXP_000 AND C_MAN_OXP_043                                                                                                                                                                                                        |                                                               |
+| <b>Other PICS</b>    |                                                                                                                                                                                                                                        |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b>  | The PHG under test is in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Make the PHG under test release the association.</li> <li>2. The simulated PHD responds to the Association Release Request with an invalid APDU.</li> <li>3. The PHG under test responds with an Association Abort message: <ol style="list-style-type: none"> <li>a. APDU Type: <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00</li> </ul> </li> <li>b. Abort-Reason: <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0x00 0x00 (undefined)</li> </ul> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 3 must be the one specified.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHG/EXP/COM/BV-049                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |  |
+| <b>TP label</b>           | Configuring.Sending GetMDS substate. Association Request                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | ManagerStateMach 86;M                                         |  |
+| <b>Test purpose</b>       | Check that:<br><br>If the PHG receives aarq while in Sending GetMDS substate, the PHG shall transmit an abrt (reason undefined) and move to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_088                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>Initial condition</b>  | PHG under test is in Sending GetMDS substate                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Request to the PHG under test</li> <li>2. The PHG under test responds with an Association Abort message and moves to the Unassociated state: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00 (AbrtApdu)</li> </ul> </li> <li>b. reason <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = Abort-reason</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = One of the following: <ul style="list-style-type: none"> <li>▪ undefined(0)</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the PHG moves to Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|--|
+| <b>TP Id</b>              | TP/PLT/PHG/EXP/COM/BV-050                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |  |
+| <b>TP label</b>           | Configuring.Sending GetMDS substate. Association Response                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | ManagerStateMach 87;M                                         |  |  |
+| <b>Test purpose</b>       | Check that:<br>If the PHG receives aare while in Sending GetMDS substate, the PHG shall transmit an abrt (reason undefined) and move to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |  |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_088                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |  |
+| <b>Initial condition</b>  | The PHG under test is in Sending GetMDS substate                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |  |  |
+| <b>Test procedure</b>     | 1. The simulated PHD sends an Association Response to the PHG under test<br>2. The PHG under test responds with an Association Abort message and moves to the Unassociated state:<br>a. APDU Type<br><input type="checkbox"/> field-length = 2 bytes<br><input type="checkbox"/> field-value = 0xE6 0x00 (AbrtApdu)<br>b. reason<br><input type="checkbox"/> field- type = Abort-reason<br><input type="checkbox"/> field-length = 2 bytes<br><input type="checkbox"/> field-value = One of the following:<br><ul style="list-style-type: none"> <li>▪ undefined(0)</li> </ul> |                                                               |  |  |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the PHG moves to Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |  |
+
+|                          |                                                                                                                                                                     |                                                               |  |  |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|--|
+| <b>TP Id</b>             | TP/PLT/PHG/EXP/COM/BV-051                                                                                                                                           |                                                               |  |  |
+| <b>TP label</b>          | Configuring.Sending GetMDS substate. Release Request                                                                                                                |                                                               |  |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                         | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |  |
+|                          | <b>Testable items</b>                                                                                                                                               | ManagerStateMach 88;M                                         |  |  |
+| <b>Test purpose</b>      | Check that:<br>If the PHG receives rlrq while in Sending GetMDS substate, the PHG shall transmit rlre(normal) and move to the Unassociated state.                   |                                                               |  |  |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND C_MAN_OXP_088                                                                                                                                     |                                                               |  |  |
+| <b>Other PICS</b>        |                                                                                                                                                                     |                                                               |  |  |
+| <b>Initial condition</b> | The PHG under test is in Sending GetMDS substate                                                                                                                    |                                                               |  |  |
+| <b>Test procedure</b>    | 1. The simulated PHD sends an Association Release Request to the PHG under test<br>2. The PHG under test responds with an Release Response message and moves to the |                                                               |  |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | Unassociated state:<br>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE5 0x00 (RlreApdu)</li> </ul> b. reason <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = ReleaseResponseReason</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = normal (0)</li> </ul> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-052                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |  |
+| <b>TP label</b>           | Configuring.Sending GetMDS substate. Release Response                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | ManagerStateMach 89;M                                         |  |
+| <b>Test purpose</b>       | Check that:<br>If the PHG receives rlre while in Sending GetMDS substate, the PHG shall transmit an abrt(Abort-reason undefined) and move to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_088                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>Initial condition</b>  | The PHG under test is in Sending GetMDS substate                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |
+| <b>Test procedure</b>     | 1. The simulated PHD sends an Association Release Response to the PHG under test<br>2. The PHG under test responds with an Association Abort message and moves to the Unassociated state: <ul style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00 (AbrtApdu)</li> </ul> </li> <li>b. reason <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = Abort-reason</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = One of the following: <ul style="list-style-type: none"> <li>▪ undefined(0)</li> </ul> </li> </ul> </li> </ul> |                                                               |  |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |
+
+|                 |                                                     |
+|-----------------|-----------------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHG/OXP/COM/BV-053                           |
+| <b>TP label</b> | Manager State machine: Configuring Sending GetMDS 1 |
+
+|                           |                                                                                                                                                                                                                                                                                              |                                                               |  |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|--|
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                  | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                        | ManagerStateMach 92;M                                         |  |  |
+| <b>Test purpose</b>       | Check that:<br><br>If the PHG receives Rx roiv-cmip-get (handle = 0) while in Sending GetMDS substate, it responds with roiv-cmip-get (handle = 0) and stays in the same state                                                                                                               |                                                               |  |  |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_088                                                                                                                                                                                                                                                              |                                                               |  |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                              |                                                               |  |  |
+| <b>Initial condition</b>  | The simulated PHD and PHG under test are in Configuring state. The simulated PHD is in Waiting GetMDS substate, and PHG under test is in Sending GetMDS substate.                                                                                                                            |                                                               |  |  |
+| <b>Test procedure</b>     | 1. The simulated PHD sends a "roiv-cmip-get" (handle = 0)<br>2. The PHG under test responds with a "roiv-cmip-get" (handle = 0).<br>3. The simulated PHD sends a "rors-cmip-get" (handle = 0) with mds-time-mgr-set-time(0), while in Sending GetMDS substate, PHG moves to Operating state. |                                                               |  |  |
+| <b>Pass/Fail criteria</b> | In Step 2, the simulated PHD receives a "roiv-cmip-get" (handle = 0) and PHG under test stays in Sending GetMDS substate.<br><br>In Step 3, PHG moves to Operating state.                                                                                                                    |                                                               |  |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                              |                                                               |  |  |
+
+|                           |                                                                                                                                                                                                                       |                                                               |  |  |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|--|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-054                                                                                                                                                                                             |                                                               |  |  |
+| <b>TP label</b>           | Manager State machine: Configuring Sending GetMDS 2                                                                                                                                                                   |                                                               |  |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                           | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                 | ManagerStateMach 93;M                                         |  |  |
+| <b>Test purpose</b>       | Check that:<br><br>If the PHG receives Rx roiv-* but not roiv-cmip-get (handle = 0), while in Sending GetMDS substate, the PHG shall stay in the same state                                                           |                                                               |  |  |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_088                                                                                                                                                                                       |                                                               |  |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                       |                                                               |  |  |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Configuring state. The simulated PHD is in Waiting GetMDS substate, and PHG under test is in Sending GetMDS substate.                                             |                                                               |  |  |
+| <b>Test procedure</b>     | 1. The simulated PHD sends a "roiv-cmip-get" (handle = 1)<br>2. The simulated PHD sends a "rors-cmip-get" (handle = 0) with mds-time-mgr-set-time(0), while in Sending GetMDS substate, PHG moves to Operating state. |                                                               |  |  |
+| <b>Pass/Fail criteria</b> | In Step 1, PHG stays in Sending GetMDS substate.<br><br>In Step 2, PHG moves to Operating state.                                                                                                                      |                                                               |  |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                       |                                                               |  |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |  |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|--|
+| <b>TP Id</b>              | TP/PLT/PHG/EXP/COM/BV-055                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |  |  |
+| <b>TP label</b>           | Manager State machine: Configuring Sending GetMDS 3                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | ManagerStateMach 94;M                                         |  |  |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>If the PHG receives Rx rors-cmip-get (handle = 0) with mds-time-mgr-set-time(1) while in the Sending GetMDS substate, the PHG shall transmit a roiv-cmip-confirmed-action (set time) and move to Sending SetTime substate.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |  |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_088                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |  |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Configuring state. The simulated PHD is in the Waiting GetMDS substate, and the PHG under test is in Sending GetMDS substate.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends a "rors-cmip-get" (handle = 0) with mds-time-mgr-set-time (1).</li> <li>2. The PHG under test shall respond with a roiv-cmip-confirmed-action (set time) and move to Sending SetTime substate: <ol style="list-style-type: none"> <li>a. Type = Remote Operation Invoke   Confirmed Action</li> <li>b. Handle = 0 (MDS object)</li> <li>c. Action = 0x0C 0x17 (MDC_ACT_SET_TIME) OR 0x0C 0x1D (MDC_ACT_SET_BO_TIME)</li> <li>d. SetTimeInvoke = SEQUENCE: <ul style="list-style-type: none"> <li><input type="checkbox"/> date-time.length = 8 bytes</li> <li><input type="checkbox"/> date-time.value = &lt;Record for comparison&gt;</li> <li><input type="checkbox"/> Accuracy = 0.</li> </ul> </li> </ol> </li> </ol> |                                                               |  |  |
+| <b>Pass/Fail criteria</b> | The simulated PHD receives a roiv-cmip-confirmed-action (set time) and the PHG under test moves to Sending SetTime substate                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |  |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |  |  |
+
+|                          |                                                                                                                                                                                               |                                                               |  |  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|--|
+| <b>TP Id</b>             | TP/PLT/PHG/EXP/COM/BV-056                                                                                                                                                                     |                                                               |  |  |
+| <b>TP label</b>          | Manager State machine: Configuring Sending GetMDS 4                                                                                                                                           |                                                               |  |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                         | ManagerStateMach 94;M                                         |  |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If the PHG receives Rx rors-cmip-get (handle = 0) with mds-time-mgr-set-time(0) while in the Sending GetMDS substate, the PHG shall move to the Operating substate.</p> |                                                               |  |  |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND C_MAN_OXP_088                                                                                                                                                               |                                                               |  |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                               |                                                               |  |  |
+| <b>Initial condition</b> | The simulated PHD and the PHG under test are in the Configuring state. The simulated PHD is in the Waiting GetMDS substate, and the PHG under test is in the Sending GetMDS substate.         |                                                               |  |  |
+
+|                           |                                                                                                                                                     |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test procedure</b>     | 1. The simulated PHD sends a "rors-cmip-get" (handle = 0) with mds-time-mgr-set-time(0)<br>2. The PHG under test shall move to the Operating state. |
+| <b>Pass/Fail criteria</b> | The PHG under test moves to the Operating state.                                                                                                    |
+| <b>Notes</b>              |                                                                                                                                                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-057                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>TP label</b>           | Configuring.Sending SetTime substate. Association Request                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | ManagerStateMach 99;M                                         |  |
+| <b>Test purpose</b>       | Check that:<br>If PHG receives aarq while in Sending SetTime substate, the PHG shall transmit an abrt (reason undefined) and move to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_088                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+| <b>Initial condition</b>  | PHG under test is in Sending SetTime substate                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |
+| <b>Test procedure</b>     | 1. Simulated PHD sends an Association Request to the PHG under test<br>2. PHG under test responds with an Association Abort message and moves to the Unassociated state:<br>a. APDU Type<br><input type="checkbox"/> field-length = 2 bytes<br><input type="checkbox"/> field-value = 0xE6 0x00 (AbrtApdu)<br>b. reason<br><input type="checkbox"/> field- type = Abort-reason<br><input type="checkbox"/> field-length = 2 bytes<br><input type="checkbox"/> field-value = One of the following:<br>▪ undefined(0) |                                                               |  |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and PHG moves to Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |  |
+
+|                     |                                                                                                                                                                     |                                                               |  |
+|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>        | TP/PLT/PHG/OXP/COM/BV-058                                                                                                                                           |                                                               |  |
+| <b>TP label</b>     | Configuring.Sending SetTime substate. Association Response                                                                                                          |                                                               |  |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                         | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                     | <b>Testable items</b>                                                                                                                                               | ManagerStateMach 100;M                                        |  |
+| <b>Test purpose</b> | Check that:<br>If the PHG receives an aare while in Sending SetTime substate, the PHG shall transmit an abrt (reason undefined) and move to the Unassociated state. |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_088                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Initial condition</b>  | The PHG under test is in the Sending SetTime substate                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Response to the PHG under test</li> <li>2. The PHG under test responds with an Association Abort message and moves to the Unassociated state: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE6 0x00 (AbrtApdu)</li> </ol> </li> <li>b. reason <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = Abort-reason</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = One of the following: <ul style="list-style-type: none"> <li>▪ undefined(0)</li> </ul> </li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHG/OXP/COM/BV-059                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                                                               |
+| <b>TP label</b>          | Configuring.Sending SetTime substate. Release Request                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | ManagerStateMach 101;M                                        |
+| <b>Test purpose</b>      | Check that:<br>If the PHG receives rlrq while in Sending SetTime substate, the PHG shall transmit rlre(normal) and move to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |
+| <b>Applicability</b>     | C_MAN_OXP_000 AND C_MAN_OXP_088                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |
+| <b>Initial condition</b> | The PHG under test is in the Sending SetTime substate                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD sends an Association Release Request to the PHG under test</li> <li>2. The PHG under test responds with an Release Response message and moves to the Unassociated state: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE5 0x00 (RlreApdu)</li> </ol> </li> <li>b. reason <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = ReleaseResponseReason</li> <li><input type="checkbox"/> field-length = 2 bytes <ul style="list-style-type: none"> <li>▪ field-value = normal (0)</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                                                               |
+
+|                           |                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and PHG moves to the Unassociated state. |
+| <b>Notes</b>              |                                                                                                                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHG/OXP/COM/BV-060                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |
+| <b>TP label</b>           | Configuring.Sending SetTime substate. Release Response                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | ManagerStateMach 102;M                                        |  |
+| <b>Test purpose</b>       | Check that:<br>If the PHG receives rlre while in the Sending SetTime substate, the PHG shall transmit an abrt(Abort-reason undefined) and move to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_088                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Initial condition</b>  | The PHG under test is in the Sending SetTime substate                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |  |
+| <b>Test procedure</b>     | 1. The simulated PHD sends an Association Release Response to the PHG under test<br>2. The PHG under test responds with an Association Abort message and moves to the Unassociated state:<br>a. APDU Type<br><input type="checkbox"/> field-length = 2 bytes<br><input type="checkbox"/> field-value = 0xE6 0x00 (AbrtApdu)<br>b. reason<br><input type="checkbox"/> field- type = Abort-reason<br><input type="checkbox"/> field-length = 2 bytes<br><input type="checkbox"/> field-value = One of the following:<br><ul style="list-style-type: none"> <li>▪ undefined(0)</li> </ul> |                                                               |  |
+| <b>Pass/Fail criteria</b> | The format of the received message in step 2 must be the one specified and the PHG moves to the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+
+|                      |                                                                                                                                                                |                                                               |  |
+|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>         | TP/PLT/PHG/OXP/COM/BV-061                                                                                                                                      |                                                               |  |
+| <b>TP label</b>      | Manager State machine: Configuring Sending SetTime 1                                                                                                           |                                                               |  |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                    | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                      | <b>Testable items</b>                                                                                                                                          | ManagerStateMach 105;M                                        |  |
+| <b>Test purpose</b>  | Check that:<br>If the PHG receives Rx rors-cmip-confirmed-action (set time), while in the Sending SetTime substate, the PHG shall move to the Operating state. |                                                               |  |
+| <b>Applicability</b> | C_MAN_OXP_000 AND C_MAN_OXP_088                                                                                                                                |                                                               |  |
+
+|                           |                                                                                                                                                                                          |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICS</b>         |                                                                                                                                                                                          |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Configuring state. The simulated PHD is in the Waiting SetTime substate, and the PHG under test is in the Sending SetTime substate.  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends a "rors-cmip-confirmed-action" (set time)</li> <li>2. The PHG under test shall move to the Operating state.</li> </ol> |
+| <b>Pass/Fail criteria</b> | The PHG under test moves to the Operating state.                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                          |
+
+|                           |                                                                                                                                                                                                                                                             |                                                               |  |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHG/EXP/COM/BV-062                                                                                                                                                                                                                                   |                                                               |  |
+| <b>TP label</b>           | Manager State machine: Configuring Sending SetTime 2                                                                                                                                                                                                        |                                                               |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                       | ManagerStateMach 106;M                                        |  |
+| <b>Test purpose</b>       | Check that:<br>If the PHG receives Rx rors-* (other than rors-cmip-confirmed-action (set time)), roer-* or rorj-*, while in the Sending SetTime substate, the PHG shall stay in the same state.                                                             |                                                               |  |
+| <b>Applicability</b>      | C_MAN_OXP_000 AND C_MAN_OXP_088                                                                                                                                                                                                                             |                                                               |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>Initial condition</b>  | The simulated PHD and the PHG under test are in the Configuring state. The simulated PHD is in the Waiting SetTime substate, and the PHG under test is in the Sending SetTime substate.                                                                     |                                                               |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD sends a "rors-cmip-get" (handle = 0)</li> <li>2. The simulated PHD sends a "rors-cmip-confirmed-action" (set time)</li> <li>3. The PHG under test shall move to the Operating state.</li> </ol> |                                                               |  |
+| <b>Pass/Fail criteria</b> | In Step 1, the PHG stays in the Sending SetTime substate.<br>In Step 3, the PHG moves to the Operating state.                                                                                                                                               |                                                               |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                             |                                                               |  |
+
+# 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*.  
+<https://docbox.etsi.org/MTS/MTS/10-PromotionalMaterial/MBS-20111118/Referenced%20Documents/Drafting%20Rules.pdf>
+- [b-PHD PICS & PIXIT] PHD PICS and PIXIT Test Tool v7.0.2.0 – Excel sheet v1.13.  
+<https://handle.itu.int/11.1002/2000/12067>
+- [b-PHG PICS & PIXIT] PHG PICS and PIXIT Test Tool v7.0.2.0 – Excel sheet v1.11.  
+<https://handle.itu.int/11.1002/2000/12067>
+- [b-TI] PHD Testable items. Test Tool v7.0.2.0 – Excel sheet v1.10.  
+<https://handle.itu.int/11.1002/2000/12067>
+
+
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.844-201911-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5b8574df486bc58a33ff5f2473183a88bc9ddfc8
--- /dev/null
+++ b/marked/H/T-REC-H.844-201911-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:08de7b2e184c81f3853b7551738fccb754fa8ed39d47491adb569f67afead859
+size 4203
diff --git a/marked/H/T-REC-H.845.1-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg b/marked/H/T-REC-H.845.1-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ca0dce65df64f4fb10a81b8f87284f793e4b1d3d
--- /dev/null
+++ b/marked/H/T-REC-H.845.1-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.1-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.845.1-201704-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..dfee68508a21ed810ec2bd68e9dafafa8e8c483a
--- /dev/null
+++ b/marked/H/T-REC-H.845.1-201704-I_PDF-E/raw.md
@@ -0,0 +1,918 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.845.1**
+
+(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 5A: Weighing scales**
+
+Recommendation ITU-T H.845.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        |
+| 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        |
+| <b>Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN)</b> | <b>H.820–H.859</b> |
+| 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.1
+
+## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5A: Weighing scales
+
+## Summary
+
+Recommendation ITU-T H.845.1 provides a test suite structure (TSS) and the test purposes (TP) for weighing scales 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.1 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5A: Device Specializations. Personal Health Device (Weighing Scale) (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.1  | 2015-01-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/12262">11.1002/1000/12262</a> |
+| 2.0     | ITU-T H.845.1  | 2016-07-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12938">11.1002/1000/12938</a> |
+| 3.0     | ITU-T H.845.1  | 2017-04-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/13219">11.1002/1000/13219</a> |
+
+## 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, touch area network, weighing scales.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.1: Weighing scales (WEG) ..... | 10   |
+| 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, Personal Health Device Interface; Part 5A: Device Specializations. Personal Health Device (Weighing Scale) (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_5A_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. It uses "TSS&TP_DG2011_PAN-LAN_PART_5A_v1.2.doc" as a baseline and adds new features included in [b-CDG 2012]: <ul style="list-style-type: none"> <li>max APDU size for GM, BCA and ECG</li> </ul>                                                                                                                   |
+| 1.4     | 2014-01-24 | Initial release for Test Tool DG2013. It uses "TSS&TP_DG2012_PAN-LAN_PART_5A_v1.3.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]: <ul style="list-style-type: none"> <li>Adds glucose meter BLE</li> <li>Adds BLE SSP support</li> <li>Adds NFC new transport</li> <li>Adds INR device specialization</li> </ul> |
+| 1.5     | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_PLT_PART_5A_v1.4.doc" as a baseline and adds new features included in Documentation Enhancements: <ul style="list-style-type: none"> <li>"Other PICS" row added</li> </ul>                                                                                       |
+| 1.5     | 2015-07-01 | Initial release for Test Tool DG2015. It is the same version as "TSS&TP_DG2013_PLT_PART_5A_v1.4.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.6     | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2015_PLT_PART_5A_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.1
+
+## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5A: Weighing scales
+
+# 1 Scope
+
+The scope of this Recommendation<sup>1</sup> 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 5A.
+
+- 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
+
+---
+
+<sup>1</sup> 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.  
+<https://www.iso.org/standard/54331.html> with  
+<https://www.iso.org/standard/63972.html>
+- [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.  
+<https://www.iso.org/standard/66717.html> with  
+<https://www.iso.org/standard/71886.html>
+- [ISO/IEEE 11073-10415] ISO/IEEE 11073-10415-2010, *Health Informatics – Personal health device communication – Part 10415: Device specialization – Weighing scale*.
+
+# 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                          |
+| PCHA  | Personal Connected Health Alliance                    |
+| 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                                  |
+
+# 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.1 (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 <http://handle.itu.int/11.1002/2000/12067>.
+
+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>/<DUT>/<GR>/<SGR>/<XX> – <NNN>). It is specified according to the naming convention defined below:
+  - Each test purpose identifier is introduced by the prefix "TP".
+  - <TT>: 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)
+  - <DUT>: This is the device under test.
+    - PHD: Personal Health Device
+    - PHG: Personal Health Gateway
+  - <GR>: This identifies a group of test cases.
+  - <SGR>: This identifies a subgroup of test cases.
+  - <XX>: This identifies the type of testing.
+    - BV: Valid behaviour test
+    - BI: Invalid behaviour test
+  - <NNN>: 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 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.1: Weighing scales (WEG)
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |                    |                   |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|-------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/WEG/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                    |                   |
+| <b>TP label</b>          | MDS Object for Standard - Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                    |                   |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [ISO/IEEE 11073-10415] |                    |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | MDSClassAttr 1; M      | MDSClassAttr 2; M  | MDSClassAttr 3; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | MDSClassAttr 4; M      | MDSClassAttr 5; R  | MDSClassAttr 6; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | MDSClassAttr 7; R      | MDSClassAttr 8; M  | MDSServices 1; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Weighing.InfoExt 3; C  | Weighing.Oper 1; M |                   |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The Personal Health Device (PHD) supports a Get command that requests all attributes</p> <p>[AND]</p> <p>The MDS Object contains the attributes specified for a Weighing Scale PHD.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                    |                   |
+| <b>Applicability</b>     | C_AG_OXP_174 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                    |                   |
+| <b>Other PICS</b>        | C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                    |                   |
+| <b>Initial condition</b> | The simulated Personal Health Gateway (PHG) and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                    |                   |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG issues a "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.</li> <li>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:<br/> MDS attributes: <ol style="list-style-type: none"> <li>a. Mandatory attribute Dev-Configuration-Id <ul style="list-style-type: none"> <li><input type="checkbox"/> If NOT C_AG_OXP_181 then attribute-value = 0x05DC (1500)</li> <li><input type="checkbox"/> If C_AG_OXP_181 then attribute-value = &lt; between 0x4000 and 0x7FFF &gt;</li> </ul> </li> <li>b. Attribute System-Type must not be present.</li> <li>c. Mandatory attribute System-model <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_MODEL (0x09 0x28)</li> <li><input type="checkbox"/> attribute-type = SystemModel</li> <li><input type="checkbox"/> attribute-value.length = &lt;Variable&gt;</li> <li><input type="checkbox"/> attribute-value ={Manufacturer, Model}</li> </ul> </li> <li>d. If recommended Power-Status attribute is present: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_POWER_STAT</li> <li><input type="checkbox"/> attribute-type = PowerStatus</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>▪ ON_MAINS (0x8000) or ON_BATTERY(0x4000)</li> </ul> Only one of the following may be active: <ul style="list-style-type: none"> <li>▪ chargingFull(8),</li> <li>▪ chargingTrickle(9),</li> <li>▪ chargingOff(10).</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                        |                    |                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>e. If recommended Battery-Level attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_VAL_BATT_CHARGE</li> <li><input type="checkbox"/> attribute-type = BITS-16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;value between 0 and 100&gt; If value &gt;100, the meaning of the value is "undefined"</li> </ul> <p>f. If recommended Remaining-Battery-Time attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_BATT_REMAIN</li> <li><input type="checkbox"/> attribute-type = BatMeasure</li> <li><input type="checkbox"/> attribute-value.length = 6 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;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) &gt;</li> </ul> <p>g. Mandatory attribute System-Type-Spec-List</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SYS_TYPE_SPEC_LIST</li> <li><input type="checkbox"/> attribute-type = TypeVerList</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = {MDC_DEV_SPEC_PROFILE_SCALE (0x10 0x0F), 1}</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                               |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  |               |                     |                     |                     |                     |                     |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|---------------|---------------------|---------------------|---------------------|---------------------|---------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|----------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/WEG/BV-001                                                                                                                                                                                                                                                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  |               |                     |                     |                     |                     |                     |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |
+| <b>TP label</b>          | Body Weight Object for Standard Configuration                                                                                                                                                                                                                                                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  |               |                     |                     |                     |                     |                     |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-10415]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |  |               |                     |                     |                     |                     |                     |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                         | <table border="1" style="width: 100%;"> <tr> <td>Concepts 2; M</td> <td>WeightNumClass 2; M</td> <td>WeightNumClass 3; M</td> </tr> <tr> <td>WeightNumClass 4; M</td> <td>WeightNumClass 6; R</td> <td>WeightNumClass 8; M</td> </tr> <tr> <td>WeightNumClass 10; R</td> <td>WeightNumClass 12; O</td> <td>WeightNumClass 14; R</td> </tr> <tr> <td>WeightNumClass 16; R</td> <td>WeightNumClass 18; R</td> <td>WeightNumClass 20; M</td> </tr> <tr> <td>WeightNumClass 22; M</td> <td>WeightNumClass 23; R</td> <td>WeightNumClass 25; R</td> </tr> <tr> <td>WeightNumClass 27; C</td> <td>WeightNumClass 28; R</td> <td>WeightNumClass 30; C</td> </tr> </table> |  | Concepts 2; M | WeightNumClass 2; M | WeightNumClass 3; M | WeightNumClass 4; M | WeightNumClass 6; R | WeightNumClass 8; M | WeightNumClass 10; R | WeightNumClass 12; O | WeightNumClass 14; R | WeightNumClass 16; R | WeightNumClass 18; R | WeightNumClass 20; M | WeightNumClass 22; M | WeightNumClass 23; R | WeightNumClass 25; R | WeightNumClass 27; C | WeightNumClass 28; R |
+| Concepts 2; M            | WeightNumClass 2; M                                                                                                                                                                                                                                                                           | WeightNumClass 3; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |  |               |                     |                     |                     |                     |                     |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |
+| WeightNumClass 4; M      | WeightNumClass 6; R                                                                                                                                                                                                                                                                           | WeightNumClass 8; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |  |               |                     |                     |                     |                     |                     |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |
+| WeightNumClass 10; R     | WeightNumClass 12; O                                                                                                                                                                                                                                                                          | WeightNumClass 14; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |  |               |                     |                     |                     |                     |                     |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |
+| WeightNumClass 16; R     | WeightNumClass 18; R                                                                                                                                                                                                                                                                          | WeightNumClass 20; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |  |               |                     |                     |                     |                     |                     |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |
+| WeightNumClass 22; M     | WeightNumClass 23; R                                                                                                                                                                                                                                                                          | WeightNumClass 25; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |  |               |                     |                     |                     |                     |                     |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |
+| WeightNumClass 27; C     | WeightNumClass 28; R                                                                                                                                                                                                                                                                          | WeightNumClass 30; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |  |               |                     |                     |                     |                     |                     |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |
+| <b>Test purpose</b>      | <p>Check that:<br/>Body Weight Object contains the attributes specified for Standard Configuration</p>                                                                                                                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  |               |                     |                     |                     |                     |                     |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |
+| <b>Applicability</b>     | C_AG_OXP_174 AND (NOT C_AG_OXP_181) AND C_AG_OXP_000                                                                                                                                                                                                                                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  |               |                     |                     |                     |                     |                     |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                               |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  |               |                     |                     |                     |                     |                     |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |
+| <b>Initial condition</b> | 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.                                                                                                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  |               |                     |                     |                     |                     |                     |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHG receives an association request from the PHD under test.</li> <li>The simulated PHG responds with a result = accepted-unknown-config.</li> <li>The PHD responds with a "Remote Operation Invoke   Confirmed Event Report"</li> </ol> |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  |               |                     |                     |                     |                     |                     |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |                      |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.</p> <ol style="list-style-type: none"> <li>4. Check that the field Dev-Config-Id is set to 0x05DC (1500); if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>5. Once the PHD under test sends a standard configuration, check that the only object present in the configuration shall be the Body Weight.</li> <li>6. Body Weight object attributes must be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_HANDLE</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 1</li> </ul> </li> <li>b. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x02(MDC_PART_SCADA), 0xE1 0x40(MDC_MASS_BODY_ACTUAL 57664)</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small (for standard and extended configuration) <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>▪ bit 0 (mss-avail-intermittent(0)) must be set</li> <li>▪ bit 1 (mss-avail-stored-data(1)) must be set</li> <li>▪ bit 2 (mss-upd-aperiodic(2)) must be set</li> <li>▪ bit 3 (mss-msmt-aperiodic(3)) must be set</li> <li>▪ bit 9 (mss-acc-agent-initiated) must be set</li> </ul> </li> </ul> </li> <li>d. Mandatory attribute Unit-Code <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type</li> <li><input type="checkbox"/> attribute-value.length = INT-U16</li> <li><input type="checkbox"/> attribute-value = MDC_DIM_KILO_G</li> </ul> </li> <li>e. Mandatory attribute Attribute-Value-Map <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = AttrValMap (sequence of attribute-id(OID-Type) and attribute-length( INT-U16) )</li> <li><input type="checkbox"/> attribute-value map.length = 8 bytes</li> <li><input type="checkbox"/> attribute-value = MDC_ATTR_NU_VAL_OBS_SIMPLE   MDC_ATTR_TIME_STAMP_ABS</li> </ul> </li> </ol> </li> <li>7. Check that there are no more present attributes in the initial configuration.</li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure. Besides, the only object present in the configuration shall be the Body Weight.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                 |                                               |                        |
+|-----------------|-----------------------------------------------|------------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/WEG/BV-002                   |                        |
+| <b>TP label</b> | Body Weight Object for Extended Configuration |                        |
+| <b>Coverage</b> | <b>Spec</b>                                   | [ISO/IEEE 11073-10415] |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                      |                      |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------|
+| <b>Testable items</b>    | Concepts 2; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | WeightNumClass 2; M  | WeightNumClass 5; M  |
+|                          | WeightNumClass 7; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | WeightNumClass 9; M  | WeightNumClass 11; R |
+|                          | WeightNumClass 13; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | WeightNumClass 15; R | WeightNumClass 17; R |
+|                          | WeightNumClass 19; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | WeightNumClass 21; M | WeightNumClass 24; R |
+|                          | WeightNumClass 26; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | WeightNumClass 29; R |                      |
+| <b>Test purpose</b>      | Check that:<br>Body Weight Object contains the attributes specified for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                      |                      |
+| <b>Applicability</b>     | C_AG_OXP_174 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                      |                      |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                      |                      |
+| <b>Initial condition</b> | 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.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                      |                      |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is in the extended range. If it is not, the simulated PHG must respond with an "unsupported-config" and wait for a new configuration. Repeat this step until a Dev-config-Id in the extended range is received.</li> <li>5. Once the PHD under test sends an extended configuration, Body Weight object attributes must be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x02(MDC_PART_SCADA) , 0xE1 0x40(MDC_MASS_BODY_ACTUAL 57664)</li> </ol> </li> <li>b. If Supplemental-Types is present: <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length = Sequence of TYPE (TYPE.length= 4 bytes)</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec_Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>▪ Bit 0 (mss-avail-intermittent(0)) must be set.</li> <li>▪ Bit 1 (mss-avail-stored-data(1)) must be set.</li> <li>▪ Bit 2 (mss-upd-aperiodic(2)) must be set.</li> <li>▪ Bit 3 (mss-msmt-aperiodic(3)) must be set.</li> <li>▪ Bit 9 (mss-acc-agent-initiated(9)) must be set.</li> </ol> </li> </ol> </li> <li>d. If attribute Metric-Structure-Small is present: <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> </ol> </li> </ol> </li> </ol> |                      |                      |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value.length = Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8))</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>e. If attribute Measurement-Status is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes.(BITS-16)</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>f. If attribute Metric-Id is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> </ul> <p>g. Only one attribute of Metric-Id and Metric-Id-List shall be present.</p> <p>h. If attribute Metric-Id-List is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIS</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value.length= SEQUENCE OF OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> <li><input type="checkbox"/> 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.</li> </ul> <p>i. If attribute Metric-Id-Part is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition</li> <li><input type="checkbox"/> attribute-value.length = INT-U16</li> <li><input type="checkbox"/> attribute-value =&lt;Not relevant for this test&gt;</li> </ul> <p>j. Mandatory attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type</li> <li><input type="checkbox"/> attribute-value.length = INT-U16</li> <li><input type="checkbox"/> attribute-value = MDC_DIM_KILO_G OR MDC_DIM_LB</li> </ul> <p>k. If attribute Source-Handle-Reference is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value.length = INT-U16</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>l. If attribute Measure-Active-Period is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type</li> <li><input type="checkbox"/> attribute-value.length = INT-U32</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>m. If attribute Accuracy is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> </ul> |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                           |                                                                                                                                      |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> attribute-value.length = 4 bytes<br><input type="checkbox"/> attribute-value = <Not relevant for this test> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                           |
+| <b>Notes</b>              |                                                                                                                                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                      |                      |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------------|----------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/WEG/BV-003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |                      |                      |
+| <b>TP label</b>          | Body Height Object                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |                      |                      |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-10415] |                      |                      |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Concepts 4; M          | HeightNumClass 1; O  | HeightNumClass 4; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | HeightNumClass 5; R    | HeightNumClass 6; M  | HeightNumClass 7; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | HeightNumClass 8; R    | HeightNumClass 9; R  | HeightNumClass 10; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | HeightNumClass 11; R   | HeightNumClass 12; M | HeightNumClass 13; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | HeightNumClass 14; R   | HeightNumClass 15; R |                      |
+| <b>Test purpose</b>      | Check that:<br>Body Height Object contains the attributes specified for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                      |                      |
+| <b>Applicability</b>     | C_AG_OXP_174 AND C_AG_OXP_181 AND C_AG_WEG_059 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                      |                      |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                      |                      |
+| <b>Initial condition</b> | 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.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                      |                      |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is in the extended range; if it is not, the simulated PHG must respond with an "unsupported-config" and wait for a new configuration.</li> <li>5. Once the PHD under test sends an extended configuration, check that the Height object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value=0x00 0x02(MDC_PART_SCADA) , 0xE1 0x44(MDC_LEN_BODY_ACTUAL 57668)</li> </ol> </li> <li>b. If not recommended attribute Supplemental-Types is present: <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length = SEQUENCE OF (SIZE 4)</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec_Small</li> </ol> </li> </ol> |                        |                      |                      |
+
+- 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
+  - Bit 12 (mss-cat-manual(12)) Must be set, the metric is acquired manually.
+
+d. If not recommended attribute Metric-Structure-Small is present:
+
+- 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
+
+e. 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>
+
+f. Only one attribute of Metric-Id and Metric-Id-List shall be present.
+
+g. If not recommended attribute Metric-Id is present:
+
+- attribute-id = MDC\_ATTR\_ID\_PHYSIO
+- attribute-type = OID-Type
+- attribute-value.length =INT-U16
+
+h. 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.
+
+i. If not recommended attribute Metric-Id-Partition is present:
+
+- attribute-id = MDC\_ATTR\_METRIC\_ID\_PART
+- attribute-type = NomPartition
+- attribute-value.length = INT-U16
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>j. Mandatory attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type</li> <li><input type="checkbox"/> attribute-value.length = INT-U16</li> <li><input type="checkbox"/> attribute-value = MDC_DIM_CENTI_M or MDC_DIM_INCH</li> </ul> <p>k. If not recommended attribute Source-Handle-Reference is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value.length = INT-U16</li> </ul> <p>l. If not recommended attribute Measurement-Active-Period:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type</li> <li><input type="checkbox"/> attribute-value.length = INT-U32</li> </ul> <p>m. If recommended attribute Accuracy is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = FLOAT-Type (INT-U32)</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                          |                                                                                                                                                                                                                                                                                                                      |                        |                    |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/WEG/BV-004                                                                                                                                                                                                                                                                                          |                        |                    |
+| <b>TP label</b>          | Body Mass Index Object                                                                                                                                                                                                                                                                                               |                        |                    |
+| <b>overage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-10415] |                    |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                | MassNumClass 1; O      | MassNumClass 3; M  |
+|                          |                                                                                                                                                                                                                                                                                                                      | MassNumClass 5; M      | MassNumClass 6; R  |
+|                          |                                                                                                                                                                                                                                                                                                                      | MassNumClass 8; R      | MassNumClass 9; R  |
+|                          |                                                                                                                                                                                                                                                                                                                      | MassNumClass 11; M     | MassNumClass 12; M |
+|                          |                                                                                                                                                                                                                                                                                                                      | MassNumClass 14; R     | MassNumClass 4; R  |
+|                          |                                                                                                                                                                                                                                                                                                                      |                        | MassNumClass 7; R  |
+|                          |                                                                                                                                                                                                                                                                                                                      |                        | MassNumClass 10; R |
+|                          |                                                                                                                                                                                                                                                                                                                      |                        | MassNumClass 13; R |
+| <b>Test purpose</b>      | Check that:<br>Body Mass Index Object contains the attributes specified for Extended Configuration                                                                                                                                                                                                                   |                        |                    |
+| <b>Applicability</b>     | C_AG_OXP_174 AND C_AG_WEG_056 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                      |                        |                    |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                      |                        |                    |
+| <b>Initial condition</b> | 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.                                                                                                                        |                        |                    |
+| <b>Test procedure</b>    | 1. The simulated PHG receives an association request from the PHD under test.<br>2. The simulated PHG responds with a result = accepted-unknown-config.<br>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 simulated PHG must respond with an "unsupported-config" and wait for a new configuration.
+5. Once the PHD under test sends an extended configuration, check that Body Mass Index Object attributes are:
+  - a. Mandatory attribute Type
+    - attribute-id = MDC\_ATTR\_ID\_TYPE
+    - attribute-type = TYPE
+    - attribute-value=0x00 0x02(MDC\_PART\_SCADA) , 0xE1 0x50(MDC\_RATIO\_MASS\_BODY\_LEN\_SQ 57680)
+  - 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)
+  - 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.
+      - If bit 14 is set(mss-cat\_calculation(14)) is set, the metric represents a calculated value.
+  - d. 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
+  - e. 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>
+  - f. Only one attribute of Metric-Id and Metric-Id-List shall be present.
+  - g. If not recommended attribute Metric-Id is present:
+    - attribute-id = MDC\_ATTR\_ID\_PHYSIO
+
+- attribute-type = OID-Type
+- attribute-value.length =INT-U16
+- attribute-value =
+
+h. 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.
+
+i. 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 = 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)
+
+j. Mandatory attribute Unit-Code
+
+- attribute-id = MDC\_ATTR\_UNIT\_CODE
+- attribute-type = OID-Type
+- attribute-value.length = INT-U16
+- attribute-value = MDC\_DIM\_KG\_PER\_M\_SQ
+
+k. 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 =
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>l. Mandatory attribute Source-Handle-Reference</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value.length = INT-U16</li> <li><input type="checkbox"/> attribute-value = It must be equal to the handle of another metric object in the configuration and it must point to an object that has a type of MDC_MASS_BODY_ACTUAL.</li> </ul> <p>m. If recommended attribute Accuracy is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = FLOAT-Type (INT-U32)</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                       |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/WEG/BV-005                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                       |
+| <b>TP label</b>          | Events for Update Data                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                       |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-10415] |                       |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MDSEvents 3; M         | MDSEvents 4; M        |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MDSEvents 6; M         | Weighing.Service 1; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        | Weighing.Service 2; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Agent-initiated mode is supported for measurement data transmission and all types of event reports are used in confirmed mode</p> <p>[AND]</p> <p>The PHD sends the MDS-Dynamic-Data-Update-Fixed using a confirmed event report and it includes the event-info ScanReportInfoFixed</p> <p>[OR]</p> <p>The PHD sends the MDS-Dynamic-Data-Update-Var using a confirmed event report and it includes the event-info ScanReportInfoVar</p> <p>[OR]</p> <p>The PHD sends the MDS-Dynamic-Data-Update-MP-Fixed using a confirmed event report and it includes the event-info ScanReportInfoMPFixed</p> <p>[OR]</p> <p>The PHD sends the MDS-Dynamic-Data-Update-MP-Var using a confirmed event report and it includes the event-info ScanReportInfoMPVar</p> |                        |                       |
+| <b>Applicability</b>     | C_AG_OXP_174 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)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                       |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                       |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                       |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Take measurements for every supported object in the PHD under test.</li> <li>2. Wait to receive every event report and check: <ul style="list-style-type: none"> <li>a. message <ul style="list-style-type: none"> <li>▪ field- type = Event Report</li> </ul> </li> </ul> </li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                       |
+
+|                           |                                                                                                                                                                                                                                                                                                        |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>▪ field-length = 2 bytes</li> <li>▪ field- value=0x01 0x01 (EventReportArgumentSimple, confirmed)</li> </ul> <p>This field identifies the type of message sent by the PHD; for the confirmed event configuration, roiv-cmip-confirmed-event-report.</p>         |
+| <b>Pass/Fail criteria</b> | <p>Check that every received report is one of the following Data APDU and that it is confirmed.</p> <ul style="list-style-type: none"> <li>• MDC_NOTI_SCAN_REPORT_FIXED</li> <li>• MDC_NOTI_SCAN_REPORT_MP_FIXED</li> <li>• MDC_NOTI_SCAN_REPORT_VAR</li> <li>• MDC_NOTI_SCAN_REPORT_MP_VAR</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                        |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                           |                            |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|----------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/WEG/BV-011                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                           |                            |
+| <b>TP label</b>          | Communication Model: Association Procedure                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                           |                            |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-10415]    |                            |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Weighing.Methods 5; M     | Weighing.Association 1; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Weighing.Association 5; M | Weighing.Association 10; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                           | Weighing.Association 11; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The association procedure data exchange is correct</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                           |                            |
+| <b>Applicability</b>     | C_AG_OXP_174 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                           |                            |
+| <b>Other PICS</b>        | C_AG_OXP_002, C_AG_OXP_017                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                           |                            |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                           |                            |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHG receives an association request from the PHD under test, the relevant field for this test:           <ol style="list-style-type: none"> <li>functional – units               <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = FunctionalUnits</li> <li><input type="checkbox"/> field-length = 4 bytes</li> <li>▪ Bit 0 must be 0.</li> <li>▪ Bits 1 and 2 may be set</li> <li>▪ The rest of the bits must not be set</li> </ul> </li> <li>dev-config-id               <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = ConfigId</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field- value =                   <ul style="list-style-type: none"> <li>▪ 0x05DC (1500) for standard configuration.</li> <li>▪ Between 0x40 0x00 and 0x7F 0xFF for extended configuration.</li> </ul> </li> </ul> </li> <li>data-req-mode-flags (DataReqModeCapab)               <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = DataReqModeFlags</li> <li><input type="checkbox"/> field-length = BITS-16</li> </ul> <p>If the PHD implements only the weighing scales specialization</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- value = data-req-supp-init-agent will be set.</li> </ul> </li> </ol> </li> </ol> |                           |                            |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>d. data-req-init-agent-count (DataReqModeCapab)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = INT-U8</li> <li><input type="checkbox"/> field-length = = INT-U8</li> </ul> <p>If the PHD implements only this Device Specialization:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- value = 0x01</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked attributes have proper values.                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                  |  |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------|--|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/WEG/BV-012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                  |  |  |
+| <b>TP label</b>          | Configuring Procedure                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                  |  |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [ISO/IEEE 11073-10415] |                  |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Concepts 3; C          | MDSEvents 1; M   |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | HeightNumClass 3; M    | MassNumClass2; M |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | HeightNumClass 2; C    |                  |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Weighing.Config 1; M   |                  |  |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The configuring procedure is correct</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                  |  |  |
+| <b>Applicability</b>     | C_AG_OXP_174 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                  |  |  |
+| <b>Other PICS</b>        | C_AG_OXP_010, C_AG_WEG_056, C_AG_WEG_059, C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                  |  |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                  |  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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. <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = PrstApdu</li> <li><input type="checkbox"/> field-length =2 bytes</li> <li><input type="checkbox"/> field-value =0xE7 0x00</li> <li><input type="checkbox"/> This value is for presentation APDU "prst" (PrstApdu).</li> </ul> </li> <li>b. The following two bytes indicates the length of the message (could be helpful to analyse the fields).</li> <li>c. The following two bytes indicate the length of the OCTET STRING that contains the DataApdu (could be helpful to analyse the fields).</li> <li>d. invoke-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = InvokeIDType</li> <li><input type="checkbox"/> field-length =INT-U16</li> <li><input type="checkbox"/> field- value= <ul style="list-style-type: none"> <li><input type="checkbox"/> This value identifies the message, the confirmed response that will be sent by the simulated PHG shall have the same invoke-id.</li> </ul> </li> </ul> </li> <li>e. Message <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type =</li> <li><input type="checkbox"/> field-length =two bytes</li> <li><input type="checkbox"/> field- value=0x01 0x01 (EventReportArgumentSimple)</li> </ul> </li> </ol> </li> </ol> |                        |                  |  |  |
+
+- 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 =INT-U16
+- h. event-time (EventReportArgumentSimple)
+  - field- type = Relative Time
+  - field-length =INT-U32
+  - If the 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 =INT-U16
+  - 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. It is the start of ConfigReport.
+- k. config-report-id (ConfigReport)
+  - field- type = ConfigId
+  - field-length = INT-U16
+  - field- value=
+    - 0x 05DC for standard configuration.
+    - <between 0x40 0x00 and 0x7F 0xFF> 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 one ObjectList)
+- m. The following two bytes indicate the length for ConfigObjectList, this value shall not be 0.
+- n. obj-class ( ConfigReport = ConfigObjectList (ConfigObject))
+  - field- type = OID-Type
+  - field-length = INT-U16
+  - field- value= 0 x00 0x06 (MDC\_MOC\_VMO\_METRIC\_NU --6) OR 0x00 0x25 (MDC\_MOC\_VMS\_MDS\_SIMP --37)
+  - MDS- Object and Numeric object are only required for the weighing scales PHD, and for this reason only two classes identify codes that are possible.
+- o. obj-handle ( ConfigReport = ConfigObjectList (ConfigObject))
+  - field- type = HANDLE
+  - field-length = INT-U16
+  - field- value=
+- p. The following two bytes indicate the number of Attributes; this value shall not be 0. ( ConfigReport = ConfigObjectList (ConfigObject) = AttributeList)
+- q. The following two bytes indicates the length (bytes) for the Attributes List; this value shall not be 0.
+- r. attribute-id ( ConfigReport = ConfigObjectList (ConfigObject) = Attribute List)
+  - field- type = OID-Type
+  - field-length = INT-U16
+- s. The following two bytes indicate the attribute-value.length, (i.e., length for the
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>attribute value); this value shall not be 0.</p> <ul style="list-style-type: none"> <li>t. attribute-value( ConfigReport = ConfigObjectList (ConfigObject) □ Attribute List); this value depends on the attribute type.</li> <li>u. The last three fields will repeat until the number of bytes for Attributes List is completed.</li> <li>v. If Configuration is Standard then the body height numeric and body mass numeric object cannot be present. <ul style="list-style-type: none"> <li>□ For every obj-class we have analysed in the message <ul style="list-style-type: none"> <li>▪ attribute-id = MDC_ATTR_ID_TYPE</li> <li>▪ attribute-value !=MDC_PART_SCADA   MDC_LEN_BODY_ACTUAL OR MDC_PART_SCADA   MDC_RATIO_MASS_BODY_LEN_SQ</li> </ul> </li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | Attributes of the configuration are properly formatted.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |               |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/WEG/BV-016                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |               |
+| <b>TP label</b>          | Body mass and body height numeric objects                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-10415] |               |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Concepts 5; C          | Concepts 6; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The body mass index (BMI) is a measure for indicating an over- or under-weight condition of a person and is defined as the individual's body weight, in kilograms, divided by the square of height, in meters</p> <p>[AND]</p> <p>In the case where pounds and inches are used as measurement units instead of kilograms and meters, the BMI may be calculated as follows <math>BMI = 703 \times (\text{body weight in lb} / \text{body height squared in inc}^2)</math></p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |               |
+| <b>Applicability</b>     | C_AG_OXP_174 AND C_AG_WEG_056 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |               |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. IF C_AG_OXP_293 THEN: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li>□ The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>▪ IF C_AG_OXP_009 THEN it issues the Set-Time action command.</li> <li>▪ IF C_AG_OXP_014 THEN it issues the Set-Base-Offset-Time action command.</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                        |               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</p> <p>5. Take weight and height measurements with the PHD under test.</p> <p>6. Wait for the simulated PHG to receive an event report with the weight, height and BMI.</p>                                                                         |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• Check PICS to make sure that if the BMI PIC is set, the Height PIC must also be set.</li> <li>• If the BMI object is present, the Height object must be present too.</li> <li>• Check that the BMI values are coherent with the height and weight values according to the formula defined in the specification.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |  |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/WEG/BV-017                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |  |
+| <b>TP label</b>           | Config Changes Service. Contextual Attribute.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-10415] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | WeightNumClass 1;M     |  |
+|                           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [b-ITU-T H.810 (2015)] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Communication 8; M     |  |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>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</p> <p>[AND]</p> <p>Service component reports configuration changes to future measurements only</p>                                                                                                                                                                                                                                                                                           |                        |  |
+| <b>Applicability</b>      | C_AG_OXP_174 AND C_AG_WEG_060 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. If an attribute that is going to be changed is reported in the fixed format event report, take some measurements with the PHD under test.</li> <li>2. Make a change to the contextual attribute Unit-Code for Body Weight Object (Pounds to kg or kg to pounds.)</li> <li>3. The PHD shall send an MDS event report indicating the new contextual attribute value.</li> <li>4. Take some more measurements.</li> <li>5. Wait for the PHG to receive new event reports from the PHD which reports the measurements from step 4.</li> </ol> |                        |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHD sends an MDS event report to inform of the contextual attribute that has been changed.</li> <li>• Data has changed in accordance with the new contextual attribute.</li> </ul>                                                                                                                                                                                                                                                                                                                                                     |                        |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/WEG/BV-018                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |  |
+| <b>TP label</b>           | Config Changes Service. Height object Contextual Attribute.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-10415] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | WeightNumClass 1;M     |  |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>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.</p>                                                                                                                                                                                                                                                                                                                                                                                             |                        |  |
+| <b>Applicability</b>      | C_AG_OXP_174 AND C_AG_WEG_059 AND C_AG_WEG_061 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>If an attribute that is going to be changed is reported in the fixed format event report, take some measurements with the PHD under test.</li> <li>Make a change to the contextual attribute Unit-Code for Body Height Object (centimetres to inches or inches to centimetres).</li> <li>The PHD shall send an MDS event report indicating the new contextual attribute value.</li> <li>Take some more measurements.</li> <li>Wait for the PHG to receive new event reports from the PHD which reports the measurements from step 4.</li> </ol> |                        |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>The PHD sends an MDS event report to inform of the contextual attribute that has been changed.</li> <li>Data has changed in accordance with the new contextual attribute.</li> </ul>                                                                                                                                                                                                                                                                                                                                                            |                        |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |  |
+
+|                      |                                                                                                                                                                                                                                                                                                         |                                                               |  |
+|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>         | TP/PLT/PHD/CLASS/WEG/BV-019                                                                                                                                                                                                                                                                             |                                                               |  |
+| <b>TP label</b>      | Operating State. PHG to PHD Maximum APDU Size                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                   | CommonCharac 3; M                                             |  |
+|                      | <b>Spec</b>                                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-10415]                                        |  |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                   | Weighing.CommModel 2; M                                       |  |
+| <b>Test purpose</b>  | <p>Check that:</p> <p>The total size of the response do not exceed of the maximum APDU size established by the specialization</p> <p>[AND]</p> <p>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</p> |                                                               |  |
+| <b>Applicability</b> | C_AG_OXP_000 AND C_AG_OXP_174                                                                                                                                                                                                                                                                           |                                                               |  |
+| <b>Other PICS</b>    | C_AG_OXP_041, C_AG_OXP_100                                                                                                                                                                                                                                                                              |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b>  | The simulated PHG and the PHD are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG issues the "Remote Operation Invoke   Get" command with: <ol style="list-style-type: none"> <li>a. Obj-handle set to 0 (to request the MDS object)</li> <li>b. attribute-id-list.count = 103</li> <li>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</li> </ol> </li> <li>2. Check the response of the PHD.</li> <li>3. The simulated PHG issues the "Remote Operation Invoke   Get" command with the handle set to 0 (to request the MDS object) and an empty attribute-id-list to indicate all attributes.</li> <li>4. Check the response of the PHD.</li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• 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 will respond with a roer message or rorj(resource-limitation) message; a WARNING will appear. <ul style="list-style-type: none"> <li>○ 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): <ul style="list-style-type: none"> <li>▪ Pulse oximeter -&gt; 9216 octets</li> <li>▪ Weighing scales -&gt; 896 octets</li> <li>▪ Glucose meter -&gt; 5120 octets or 64512 octets if PHD supports PM-Store</li> <li>▪ Blood pressure -&gt; 896 octets</li> <li>▪ Thermometer -&gt; 896 octets</li> <li>▪ Independent activity hub -&gt; 5120 octets</li> <li>▪ Cardiovascular -&gt; 64512 octets or 6624 octets PHD under test only supports Step Counter Profile</li> <li>▪ Strength -&gt; 64512 octets:</li> <li>▪ Adherence monitor -&gt; 1024 octets</li> <li>▪ Peak flow -&gt; 2030 octets</li> <li>▪ Body composition analyser -&gt; 7730 octets</li> <li>▪ Basic ECG/Simple ECG -&gt; 7168 octets or 64512 octets if PHD supports PM-Store</li> <li>▪ Basic ECG/Heart rate -&gt; 1280 octets or 64512 octets if PHD supports PM-Store</li> <li>▪ International normalized ratio -&gt; 896 octets or 64512 if PHD supports PM-Store</li> </ul> </li> <li>○ In case it responds with a roer, the reason must not be protocol-violation (code value 23)</li> </ul> </li> <li>• In step 4, the PHD must respond with a rors-cmip-get message.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+# 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.11.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-PHG PICS & PIXIT] Personal Health Gateway DG2016 PICS and PIXIT excel sheet v1.9.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-TCRL] Test Case Reference List\_DG2016\_v1.11.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-TI] Continua DG2016 PHD Testable items excel sheet v1.8.  
+<http://handle.itu.int/11.1002/2000/12067>
+
+
+
+## **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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.12-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.845.12-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..61904c12b802df120c05ae72cd89a3ef2690dd5b
--- /dev/null
+++ b/marked/H/T-REC-H.845.12-201704-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.845.12-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.845.12-201704-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..6ab976ed1ab3517467e5502764ca0ef635bc54ac
--- /dev/null
+++ b/marked/H/T-REC-H.845.12-201704-I_PDF-E/raw.md
@@ -0,0 +1,1413 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.845.12**
+
+(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 5L: Body composition analyser**
+
+Recommendation ITU-T H.845.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        |
+| 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        |
+| <b>Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN)</b> | <b>H.820–H.859</b> |
+| 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.12
+
+# Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5L: Body composition analyser
+
+## Summary
+
+Recommendation ITU-T H.845.12 provides a test suite structure (TSS) and the test purposes (TP) for body composition analysers 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.12 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5L: Device Specializations. Personal Health Device (Body Composition Analyzer) (Version 1.3, 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.12 | 2015-01-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/12272">11.1002/1000/12272</a> |
+| 2.0     | ITU-T H.845.12 | 2016-07-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12949">11.1002/1000/12949</a> |
+| 3.0     | ITU-T H.845.12 | 2017-04-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/13229">11.1002/1000/13229</a> |
+
+## Keywords
+
+Body composition analyser, 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, touch area network.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.12 – Body composition analyser (BCA) ..... | 10 |
+|         | 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 5L: Device Specializations. Personal Health Device (Body Composition Analyzer) (Version 1.3, 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     | 2013-05-24 | Initial release for Test Tool DG2012 based on the requirements in [b-CDG 2012].                                                                                                                                                                                                                                                                                 |
+| 1.1     | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_PAN-LAN_PART_5L_v1.0.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]: <ul style="list-style-type: none"><li>• Adds glucose meter BLE</li><li>• Adds BLE SSP support</li><li>• Adds NFC new transport</li><li>• Adds INR device specialization</li></ul> |
+| 1.2     | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_PLT_PART_5L_v1.1.doc" as a baseline and adds new features included in Documentation Enhancements: <ul style="list-style-type: none"><li>• "Other PICS" row added</li></ul>                                                                                            |
+| 1.2     | 2015-07-01 | Initial release for Test Tool DG2015. It is the same version as "TSS&TP_DG2013_PLT_PART_5L_v1.1.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.3     | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2015_PLT_PART_5L_v1.2.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 5L: Body composition analyser
+
+## 1 Scope
+
+The scope of this Recommendation<sup>1</sup> 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 5L.
+
+- 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
+
+---
+
+<sup>1</sup> 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 (2016)] Recommendation ITU-T H.810 (2016), *Interoperability design guidelines for personal health systems*.
+- [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-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.  
+<https://www.iso.org/standard/54331.html> with  
+<https://www.iso.org/standard/63972.html>
+- [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.  
+<https://www.iso.org/standard/66717.html> with  
+<https://www.iso.org/standard/71886.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
+
+|       |                                                       |
+|-------|-------------------------------------------------------|
+| 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                         |
+| 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.12 (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 <http://handle.itu.int/11.1002/2000/12067>.
+
+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>/<DUT>/<GR>/<SGR>/<XX> – <NNN>). It is specified according to the naming convention defined below:
+  - Each test purpose identifier is introduced by the prefix "TP".
+  - <TT>: 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)
+  - <DUT>: This is the device under test:
+    - PHD: Personal Health Device
+    - PHG: Personal Health Gateway
+  - <GR>: This identifies a group of test cases.
+  - <SGR>: This identifies a subgroup of test cases.
+  - <XX>: This identifies the type of testing:
+    - BV: Valid behaviour test
+    - BI: Invalid behaviour test
+  - <NNN>: 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.12 – Body composition analyser (BCA)
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                     |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/BCA/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                     |
+| <b>TP label</b>          | Get MDS Object for body composition analyser specialization: Mandatory, Conditional and Optional Attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-10420] |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | MDSCClassAttrr 1; M    | MDSCClassAttrr 2; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | MDSCClassAttrr 4; M    | MDSCClassAttrr 5; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | MDSCClassAttrr 7; M    | MDSCClassAttrr 8; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | MDSCClassAttrr 10; R   | MDSServices 1; M    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | OperProc2; M           | MDSServices 3; M    |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The PHD supports a Get command that requests all attributes</p> <p>[AND]</p> <p>The MDS Object contains the attributes specified for a body composition analyser PHD.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                     |
+| <b>Applicability</b>     | C_AG_OXP_167 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                     |
+| <b>Other PICS</b>        | C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                     |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                     |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>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.</li> <li>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:           <p>MDS Attributes:</p> <ol style="list-style-type: none"> <li>a. Conditional attribute System-Type shall not be present.               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SYS_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;not relevant &gt;</li> </ul> </li> <li>b. Mandatory attribute System-Type-Spec_List               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SYS_TYPE_SPEC_LIST</li> <li><input type="checkbox"/> attribute-type = TypeVerList</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes attribute-value = MDC_DEV_SPEC_PROFILE_BCA, 1</li> </ul> </li> <li>c. Mandatory attribute System-model               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_MODEL</li> <li><input type="checkbox"/> attribute-type = SystemModel</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value = {Manufacturer, Model}</li> </ul> </li> <li>d. Mandatory attribute Dev-Configuration-Id               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_DEV_CONFIG_ID</li> <li><input type="checkbox"/> attribute-type = ConfigId</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value =                   <ul style="list-style-type: none"> <li>– IF NOT C_AG_OXP_181 then attribute-value = 0x07D0</li> <li>– ELSE attribute-value = &lt; between 0x4000 and 0x7FFF&gt;</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                        |                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>e. Recommended attribute Power-Status</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_POWER_STAT</li> <li><input type="checkbox"/> attribute-type = PowerStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value =<br/>ON_MAINS (0x8000) or ON_BATTERY(0x4000)</li> </ul> <p>Only one of the following may be active:</p> <ul style="list-style-type: none"> <li>▪ chargingFull(8),</li> <li>▪ chargingTrickle(9),</li> <li>▪ chargingOff(10).</li> <li>▪ The rest of the bits must not be set</li> </ul> <p>f. Recommended attribute Remain-Battery-Time</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_BATT_REMAIN (0x09 0x88)</li> <li><input type="checkbox"/> attribute-type = BatMeasure</li> <li><input type="checkbox"/> attribute-value.length = 6 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;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) or MDC_DIM_DAY (0x08 0xE0) &gt;</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                    |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/BCA/BV-001                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |                    |
+| <b>TP label</b>          | MDS Configuration objects events for body composition analyser PHD                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                    |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [ISO/IEEE 11073-10420] |                    |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | MDSEvents 1; M         | BCA_NumGen1; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | BodyHeight1; M         | WeightNumClass 1;M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | FatFreeMass1; O        | SoftLeanMass1; O   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | BCAExtRules3; M        | ConfigProc1; M     |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>A body composition analyser PHD shall send the [MDS-Configuration-Event] using a [Confirmed] event report. The [MDS-Configuration-Event] shall include the event-info [ConfigReport].</p> <p>[AND]</p> <p>Check objects supported by the PHD (standard /extended configuration)</p>                                                                                                                                                                                                                                                                                                                                                                |                        |                    |
+| <b>Applicability</b>     | C_AG_OXP_167 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                    |
+| <b>Other PICS</b>        | C_AG_OXP_010, C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                    |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                    |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = PrstApdu</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE7 0x00</li> </ul> </li> </ol> </li> </ol> |                        |                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>b. invoke-id</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = InvokeIDType</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field- value = &lt;Not relevant for this test&gt;</li> </ul> <p>c. message</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = roiv-cmip-confirmed-event-report</li> <li><input type="checkbox"/> field-length = two bytes</li> <li><input type="checkbox"/> field- value = 0x01 0x01 (EventReportArgumentSimple)</li> </ul> <p>d. obj-handle (EventReportArgumentSimple)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = HANDLE</li> <li><input type="checkbox"/> field-length = INT-U16</li> </ul> <p>e. event-time (EventReportArgumentSimple)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = Relative Time</li> <li><input type="checkbox"/> field-length = INT-U32</li> <li><input type="checkbox"/> field-value = <ul style="list-style-type: none"> <li>• IF NOT C_AG_OXP_010 THEN value = 0xFF 0xFF 0xFF 0xFF</li> </ul> </li> </ul> <p>f. event-type (EventReportArgumentSimple)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = OID-Type</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field- value = 0x0D 0x1C (MDC_NOTI_CONFIG)</li> </ul> <p>g. config-report-id (ConfigReport)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = ConfigId</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field- value = <ul style="list-style-type: none"> <li>– IF NOT C_AG_OXP_181 then attribute-value = 0x07D0</li> <li>– ELSE attribute-value = &lt; between 0x4000 and 0x7FFF &gt;</li> </ul> </li> </ul> <p>h. obj-class ( ConfigReport → ConfigObjectList (ConfigObject)). To check the objects that are supported by the PHD, Type Attribute will be checked in AttributeList.</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = OID-Type</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field- value = <ul style="list-style-type: none"> <li>– Three mandatory numeric objects for body fat, body height and body weight.</li> <li>– Four optional numeric objects for body mass index, fat free mass, soft lean mass and body water.</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                     |                                              |                        |                |
+|---------------------|----------------------------------------------|------------------------|----------------|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/BCA/BV-002                  |                        |                |
+| <b>TP label</b>     | MDS objects events Body composition analyser |                        |                |
+| <b>Coverage</b>     | <b>Spec</b>                                  | [ISO/IEEE 11073-10420] |                |
+|                     | <b>Testable items</b>                        | MDSEvents 3; M         | MDSEvents 4; M |
+|                     |                                              | MDSEvents 6; M         | ObjAccServ1; M |
+|                     |                                              | ObjAccServ3; M         | ObjAccServ6; O |
+| <b>Test purpose</b> | Check that:                                  |                        |                |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | <p>The PHD sends the MDS-Dynamic-Data-Update-Fixed using a confirmed event report and it includes the event-info ScanReportInfoFixed.</p> <p>[AND/OR]</p> <p>The PHD sends the MDS-Dynamic-Data-Update-Var using a confirmed event report and it includes the event-info ScanReportInfoVar.</p> <p>[AND]</p> <p>Event reports shall be used in confirmed mode.</p> <p>[AND]</p> <p>Agent-initiated mode shall be supported for measurement data transmission.</p> <p>[AND]</p> <p>A body composition analyser PHD may support either one or both single-person and multi-person event reports</p> <p>[AND]</p> <p>A body composition analyser PHD with standard configuration shall use the fixed format data update messages method for transmitting measurement data</p> <p>[AND]</p> <p>A body composition analyser PHD with extended configuration may use either fixed or variable format data update messages for transmitting measurement data.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Applicability</b>     | C_AG_OXP_167 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)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_181, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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 the tested configuration is received.</li> <li>5. Record the PHD configuration.</li> <li>6. IF C_AG_OXP_293: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ol> </li> <li>7. Take Measurements for every supported object in the PHD under test.</li> <li>8. Wait to receive every event report and check: <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = Event Report</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> 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.</li> </ul> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• Check that every received MDS Event report is one of the following Data APDU and that it is confirmed.</li> <li>• 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. <ul style="list-style-type: none"> <li>• MDC_NOTI_SCAN_REPORT_FIXED</li> <li>• MDC_NOTI_SCAN_REPORT_MP_FIXED</li> </ul> </li> <li>• For Extended Configuration, an MDS Event Report is sent by the PHD under test to report measurements for every object: <ul style="list-style-type: none"> <li>• MDC_NOTI_SCAN_REPORT_FIXED</li> <li>• MDC_NOTI_SCAN_REPORT_MP_FIXED</li> <li>• MDC_NOTI_SCAN_REPORT_VAR</li> <li>• MDC_NOTI_SCAN_REPORT_MP_VAR</li> </ul> </li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                      |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/BCA/BV-003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                      |
+| <b>TP label</b>          | Body Weight Object for Standard Configuration (0x07D0)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                      |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-10420] |                      |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | WeightNumClass 1; M    | WeightNumClass 2; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | WeightNumClass 5; R    | WeightNumClass 7; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | WeightNumClass 11; O   | WeightNumClass 13; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | WeightNumClass 17; R   | WeightNumClass 19; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | WeightNumClass 22; R   | WeightNumClass 24; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | WeightNumClass 27; R   | WeightNumClass 29; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | Concepts 4; M          | ConfigProc2; M       |
+| <b>Test purpose</b>      | Check that:<br>Body Weight Numeric Object contains the attributes specified for Standard Configuration (0x07D0)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                      |
+| <b>Applicability</b>     | C_AG_OXP_167 AND (NOT C_AG_OXP_181) AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                      |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                      |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                      |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is set to 0x07D0. 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 0x07D0 is received.</li> <li>5. Once the PHD under test sends a standard configuration, check the Body Weight object.</li> <li>6. The Body Weight object contents shall be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_HANDLE</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x01</li> </ul> </li> <li>b. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> </ul> </li> </ol> </li> </ol> |                        |                      |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value = 0x00 0x02(MDC_PART_SCADA), 0xE1 0x40(MDC_MASS_BODY_ACTUAL 57664)</li> <li>c. Mandatory attribute Metric-Spec-Small <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 0 (mss-avail-intermittent(0)) is set.</li> <li>• Bit 1 (mss-avail-stored-data(1)) is set.</li> <li>• Bit 2 (mss-upd-aperiodic(2)) is set.</li> <li>• Bit 3 (mss-msmt-aperiodic(3)) is set.</li> <li>• Bit 9 (mss-acc-agent-initiated(9)) is set.</li> <li>• Bit 12 (mss-cat-manual(12)) is set.</li> </ul> </li> </ul> </li> <li>d. Mandatory attribute Unit-Code <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = MDC_DIM_KILO_G</li> </ul> </li> <li>e. Mandatory attribute Attribute-Value-Map <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = AttrValMap</li> <li><input type="checkbox"/> attribute-count = 2</li> <li><input type="checkbox"/> attribute-value = (MDC_ATTR_NU_VAL_OBS_SIMP,4 MDC_ATTR_TIME_STAMP_ABS,8)</li> </ul> </li> </ul> <p>7. Check that no other attributes are present in the initial configuration.</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                          |                                                                                                                                                                                                                                             |                        |                      |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/BCA/BV-004                                                                                                                                                                                                                 |                        |                      |
+| <b>TP label</b>          | Body Weight Object for Extended Configuration                                                                                                                                                                                               |                        |                      |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                 | [ISO/IEEE 11073-10420] |                      |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                       | WeightNumClass 1; M    | WeightNumClass 4; M  |
+|                          |                                                                                                                                                                                                                                             | WeightNumClass 8; M    | WeightNumClass 10; R |
+|                          |                                                                                                                                                                                                                                             | WeightNumClass 14; R   | WeightNumClass 16; R |
+|                          |                                                                                                                                                                                                                                             | WeightNumClass 20; M   | WeightNumClass 23; R |
+|                          |                                                                                                                                                                                                                                             | WeightNumClass 28; R   | Concepts 4; M        |
+| <b>Test purpose</b>      | Check that:<br>Body Weight Numeric Object contains the attributes specified for Extended Configuration                                                                                                                                      |                        |                      |
+| <b>Applicability</b>     | C_AG_OXP_167 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                              |                        |                      |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                             |                        |                      |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                     |                        |                      |
+| <b>Test procedure</b>    | 1. The simulated PHG receives an association request from the PHD under test.<br>2. The simulated PHG responds with a result = accepted-unknown-config.<br>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. 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 Body Weight object:
+6. The Body Weight object contents shall be:
+  - a. Mandatory attribute Type
+    - attribute-id = MDC\_ATTR\_ID\_TYPE
+    - attribute-type = TYPE
+
+attribute-value = 0x00 0x02(MDC\_PART\_SCADA), 0xE1 0x40(MDC\_MASS\_BODY\_ACTUAL 57664)
+  - 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>
+  - c. Mandatory attribute Metric-Spec-Small
+    - attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL
+    - attribute-type = MetricSpecSmall
+    - attribute-value.length = 2 bytes
+    - attribute-value ≠ 0x00 0x00
+      - Bit 0 (mss-avail-intermittent(0)) is set.
+      - Bit 1 (mss-avail-stored-data(1)) is set.
+      - Bit 2 (mss-upd-aperiodic(2)) 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 = <Not relevant for this test>
+  - e. 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>
+  - 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>
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>h. IF Not recommended attribute Metric-Id-Partition is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>i. Mandatory attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = MDC_DIM_KILO_G OR MDC_DIM_LB</li> </ul> <p>j. IF Not recommended attribute Source-Handle-Reference is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>k. IF Not recommended attribute Measure-Active-Period</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>l. IF Recommended attribute Accuracy is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                     |                                                                                                                 |                        |                 |
+|---------------------|-----------------------------------------------------------------------------------------------------------------|------------------------|-----------------|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/BCA/BV-005                                                                                     |                        |                 |
+| <b>TP label</b>     | Body Height Object for Standard Configuration (0x07D0)                                                          |                        |                 |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                     | [ISO/IEEE 11073-10420] |                 |
+|                     | <b>Testable items</b>                                                                                           | BodyHeight1; M         | BodyHeight2; M  |
+|                     |                                                                                                                 | BodyHeight6; R         | BodyHeight8; M  |
+|                     |                                                                                                                 | BodyHeight12; O        | BodyHeight14; R |
+|                     |                                                                                                                 | BodyHeight18; R        | BodyHeight20; M |
+|                     |                                                                                                                 | BodyHeight24; R        | BodyHeight26; O |
+|                     |                                                                                                                 | BodyHeight30; C        | BodyHeight32; C |
+|                     |                                                                                                                 | BodyHeight36; R        | BodyHeight38; C |
+|                     |                                                                                                                 | BodyHeight42; C        | BodyHeight44; C |
+|                     |                                                                                                                 | BodyHeight48; C        | BodyHeight50; R |
+|                     |                                                                                                                 | Concepts 3; M          | ConfigProc2; M  |
+| <b>Test purpose</b> | Check that:<br>Body Height Numeric Object contains the attributes specified for Standard Configuration (0x07D0) |                        |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Applicability</b>      | C_AG_OXP_167 AND (NOT C_AG_OXP_181) AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is set to 0x07D0. 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 0x07D0 is received.</li> <li>5. Once the PHD under test sends a standard configuration, check the Body Height object:</li> <li>6. The Body Height object contents shall be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_HANDLE</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x02</li> </ol> </li> <li>b. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x02(MDC_PART_SCADA), 0xE1 0x44(MDC_LEN_BODY_ACTUAL)</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• Bit 0 (mss-avail-intermittent(0)) is set.</li> <li>• Bit 1 (mss-avail-stored-data(1)) is set.</li> <li>• Bit 2 (mss-upd-aperiodic(2)) is set.</li> <li>• Bit 3 (mss-msmt-aperiodic(3)) is set.</li> <li>• Bit 9 (mss-acc-agent-initiated(9)) is set.</li> <li>• Bit 12 (mss-cat-manual(12)) is set.</li> </ol> </li> </ol> </li> <li>d. Mandatory attribute Unit-Code <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = MDC_DIM_CENTI_M</li> </ol> </li> <li>e. Mandatory attribute Attribute-Value-Map <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = AttrValMap</li> <li><input type="checkbox"/> attribute-count = 2</li> <li><input type="checkbox"/> attribute-value = (MDC_ATTR_NU_VAL_OBS_SIMP,4 MDC_ATTR_TIME_STAMP_ABS,8)</li> </ol> </li> </ol> </li> <li>7. Check that no other attributes are present in the initial configuration.</li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                 |  |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|--|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/BCA/BV-006                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                 |  |  |
+| <b>TP label</b>          | Body Height Object for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |                 |  |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-10420] |                 |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | BodyHeight1; M         | BodyHeight3; M  |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | BodyHeight7; R         | BodyHeight9; M  |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | BodyHeight13; R        | BodyHeight15; R |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | BodyHeight19; R        | BodyHeight21; M |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | BodyHeight25; R        | BodyHeight27; O |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | BodyHeight31; C        | BodyHeight33; C |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | BodyHeight37; R        | BodyHeight39; C |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | BodyHeight43; C        | BodyHeight45; C |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | BodyHeight49; C        | BodyHeight51; R |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Concepts 3; M          |                 |  |  |
+| <b>Test purpose</b>      | Check that:<br>Body Height Numeric Object contains the attributes specified for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                 |  |  |
+| <b>Applicability</b>     | C_AG_OXP_167 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                 |  |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                 |  |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                 |  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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.</li> <li>5. Once the PHD under test sends the tested configuration, check the Body Height object:</li> <li>6. The Body Height object contents shall be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> </ol> attribute-value = 0x00 0x02(MDC_PART_SCADA), 0xE1 0x44(MDC_LEN_BODY_ACTUAL) </li> <li>b. IF Not Recommended attribute Supplemental-Types <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;Sequence of TYPE (TYPE.length = 4 bytes)</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 0 (mss-avail-intermittent(0)) is set.</li> <li>• Bit 1 (mss-avail-stored-data(1)) is set.</li> <li>• Bit 2 (mss-upd-aperiodic(2)) is set.</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                        |                 |  |  |
+
+- Bit 3 (mss-msmt-aperiodic(3)) is set.
+- Bit 9 (mss-acc-agent-initiated(9)) is set.
+- Bit 12 (mss-cat-manual(12)) 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 = <Not relevant for this test>
+
+e. 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>
+
+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. 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\_CENTI\_M or MDC\_DIM\_INCH
+
+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 = <Not relevant for this test>
+
+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 Recommended attribute Accuracy is present
+
+- attribute-id = MDC\_ATTR\_NU\_ACCUR\_MSMT
+
+|                           |                                                                                                                                                                                                        |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)<br><input type="checkbox"/> attribute-value.length = 4 bytes<br><input type="checkbox"/> attribute-value = <Not relevant for this test> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                        |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                |               |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/BCA/BV-007                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                |               |
+| <b>TP label</b>          | Body Fat Object for Standard Configuration (0x07D0)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-10420] |                |               |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | BodyFat1; M            | BodyFat2; O    | BodyFat3; M   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | BodyFat5; M            | BodyFat7; R    | BodyFat9; M   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | BodyFat11; R           | BodyFat13; O   | BodyFat15; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | BodyFat17; R           | BodyFat19; R   | BodyFat21; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | BodyFat23; M           | BodyFat25; R   | BodyFat27; O  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | BodyFat29; O           | BodyFat31; C   | BodyFat33; C  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | BodyFat35; C           | BodyFat37; R   | BodyFat39; C  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | BodyFat41; C           | BodyFat43; C   | BodyFat45; C  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | BodyFat47; C           | BodyFat49; C   | BodyFat51; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | BodyFat53; M           | ConfigProc2; M | Concepts 2; M |
+| <b>Test purpose</b>      | Check that:<br>Body Fat Numeric Object contains the attributes specified for Standard Configuration (0x07D0)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                |               |
+| <b>Applicability</b>     | C_AG_OXP_167 AND (NOT C_AG_OXP_181) AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                |               |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                |               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                |               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is set to 0x07D0. 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 0x07D0 is received.</li> <li>5. Once the PHD under test sends a standard configuration, check the Body Fat object.</li> <li>6. The Body Fat contents shall be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_HANDLE</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x03</li> </ul> </li> <li>b. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_SCADA   MDC_BODY_FAT</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall</li> </ul> </li> </ol> </li> </ol> |                        |                |               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00           <ul style="list-style-type: none"> <li>• Bit 0 (mss-avail-intermittent(0)) is set.</li> <li>• Bit 1 (mss-avail-stored-data(1)) is set.</li> <li>• Bit 2 (mss-upd-aperiodic(2)) is set.</li> <li>• Bit 3 (mss-msmt-aperiodic(3)) is set.</li> <li>• Bit 9 (mss-acc-agent-initiated(9)) is set.</li> <li>• Bit 14 (mss-cat-calculation(14)) is set.</li> </ul> </li> </ul> <p>d. Mandatory recommended attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = MDC_DIM_PERCENT.</li> </ul> <p>e. Mandatory attribute Attribute-Value-Map</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = AttrValMap</li> <li><input type="checkbox"/> attribute-count = 2</li> <li><input type="checkbox"/> attribute-value = (MDC_ATTR_NU_VAL_OBS_SIMP,4<br/>MDC_ATTR_TIME_STAMP_ABS,8)</li> </ul> <p>f. IF Recommended attribute Accuracy is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = FLOAT-Type (INT-U32)</li> </ul> <p>7. Check that no other attributes are present in the initial configuration.</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                          |                                                                                                     |                        |               |
+|--------------------------|-----------------------------------------------------------------------------------------------------|------------------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/BCA/BV-008                                                                         |                        |               |
+| <b>TP label</b>          | Body Fat Object for Extended Configuration                                                          |                        |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                         | [ISO/IEEE 11073-10420] |               |
+|                          | <b>Testable items</b>                                                                               | BodyFat2; O            | BodyFat4; M   |
+|                          |                                                                                                     | BodyFat8; R            | BodyFat10; M  |
+|                          |                                                                                                     | BodyFat14; R           | BodyFat16; C  |
+|                          |                                                                                                     | BodyFat20; C           | BodyFat22; M  |
+|                          |                                                                                                     | BodyFat26; R           | BodyFat28; O  |
+|                          |                                                                                                     | BodyFat32; C           | BodyFat34; C  |
+|                          |                                                                                                     | BodyFat38; R           | BodyFat40; C  |
+|                          |                                                                                                     | BodyFat44; C           | BodyFat46; C  |
+|                          |                                                                                                     | BodyFat50; C           | BodyFat52; R  |
+|                          |                                                                                                     |                        | Concepts 2; M |
+| <b>Test purpose</b>      | Check that:<br>Body Fat Numeric Object contains the attributes specified for Extended Configuration |                        |               |
+| <b>Applicability</b>     | C_AG_OXP_167 AND C_AG_OXP_181 AND C_AG_OXP_000                                                      |                        |               |
+| <b>Other PICS</b>        |                                                                                                     |                        |               |
+| <b>Initial condition</b> | 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 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 Body Fat object.
+6. The Body Fat object contents shall be:
+  - a. Mandatory attribute Type
+    - attribute-id = MDC\_ATTR\_ID\_TYPE
+    - attribute-type = TYPE
+    - attribute-value = MDC\_PART\_SCADA | MDC\_BODY\_FAT
+  - 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>
+  - c. Mandatory attribute Metric-Spec-Small
+    - attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL
+    - attribute-type = MetricSpecSmall
+    - attribute-value.length = 2 bytes
+    - attribute-value = <Not relevant for this test>
+  - 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 = <Not relevant for this test>
+  - e. 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>
+  - f. IF Conditional 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 Conditional 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. Mandatory attribute Unit-Code
+  - attribute-id = MDC\_ATTR\_UNIT\_CODE
+  - attribute-type = OID-Type
+  - attribute-value.length = 2 bytes
+  - attribute-value = MDC\_DIM\_PERCENT or MDC\_DIM\_KILO\_G or MDC\_DIM\_LB
+- 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 = <Not relevant for this test>
+- 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 Compound-Simple-Nu-Observed-Value is present
+  - attribute-id = MDC\_ATTR\_NU\_CMPD\_VAL\_OBS\_SIMP
+  - attribute-type = SimpleNuObsValueCmp
+  - attribute-value.length = <variable>
+  - attribute-value = <Not relevant for this test>
+- 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 Recommended attribute Accuracy is present
+
+|                           |                                                                                                                                                                                                                                                                          |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT<br><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)<br><input type="checkbox"/> attribute-value.length = 4 bytes<br><input type="checkbox"/> attribute-value = <Not relevant for this test> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                          |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                    |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/BCA/BV-009                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                    |
+| <b>TP label</b>          | Body Mass Index Object for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                    |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-10420] |                    |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | BodyMassIndex1; O      | BodyMassIndex2; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | BodyMassIndex4; M      | BodyMassIndex5; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | BodyMassIndex7; R      | BodyMassIndex8; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | BodyMassIndex10; R     | BodyMassIndex11; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | BodyMassIndex13; C     | BodyMassIndex14; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | BodyMassIndex16; O     | BodyMassIndex17; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | BodyMassIndex19; C     | BodyMassIndex20; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | BodyMassIndex22; C     | BodyMassIndex23; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | BodyMassIndex25; C     | BodyMassIndex26; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Concepts 5; O          |                    |
+| <b>Test purpose</b>      | Check that:<br>Body Mass Index Numeric Object contains the attributes specified for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                    |
+| <b>Applicability</b>     | C_AG_OXP_167 AND C_AG_OXP_181 AND C_AG_BCA_001 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                    |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                    |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                    |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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.</li> <li>5. Once the PHD under test sends the tested configuration, check the Body Mass Index object.</li> <li>6. The Body Mass Index object contents shall be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE<br/> <input type="checkbox"/> attribute-type = TYPE<br/> <input type="checkbox"/> attribute-value = MDC_PART_SCADA   MDC_RATIO_MASS_BODY_LEN_SQ </li> <li>b. IF Not Recommended attribute Supplemental-Types <input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES<br/> <input type="checkbox"/> attribute-type = SupplementalTypeList<br/> <input type="checkbox"/> attribute-value.length = &lt;variable&gt;Sequence of TYPE (TYPE.length = 4 bytes)<br/> <input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt; </li> </ol> </li> </ol> |                        |                    |
+
+- c. Mandatory attribute Metric-Spec-Small
+  - attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL
+  - attribute-type = MetricSpecSmall
+  - 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 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 14 (mss-cat\_calculation(14)) must be set 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 = <Not relevant for this test>
+- e. 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>
+- 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. Mandatory attribute Unit-Code
+  - attribute-id = MDC\_ATTR\_UNIT\_CODE
+  - attribute-type = OID-Type
+  - attribute-value.length = 2 bytes
+  - attribute-value = MDC\_DIM\_KG\_PER\_M\_SQ
+- j. Conditional attribute Attribute-Value-Map
+  - attribute-id = MDC\_ATTR\_ATTRIBUTE\_VAL\_MAP
+  - attribute-type = AttrValMap
+  - attribute-count = 2
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>k. Mandatory attribute Source-Handle-Reference is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = It must be equal to the handle of another metric object in the configuration and it must point to an object that has a type of MDC_MASS_BODY_ACTUAL.</li> </ul> <p>l. IF Not recommended attribute Measure-Active-Period</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>m. IF Not recommended Compound-Simple-Nu-Observed-Value is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_SIMP</li> <li><input type="checkbox"/> attribute-type = SimpleNuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>n. IF Not recommended attribute Basic-Nu-Observed-Value is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>o. IF Not recommended attribute Compound-Basic-Nu-Observed-Value is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>p. IF Not recommended attribute Nu-Observed-Value is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS</li> <li><input type="checkbox"/> attribute-type = NuObsValue</li> <li><input type="checkbox"/> attribute-value.length = 10 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>q. Not recommended attribute Compound-Nu-Observed-Value</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_SIMP</li> <li><input type="checkbox"/> attribute-type = NuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>r. IF Recommended attribute Accuracy is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/BCA/BV-010                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                  |
+| <b>TP label</b>          | Fat Free Mass Object for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-10420] |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | FatFreeMass1; O        | FatFreeMass2; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | FatFreeMass4; M        | FatFreeMass5; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | FatFreeMass7; R        | FatFreeMass8; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | FatFreeMass10; R       | FatFreeMass11; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | FatFreeMass13; C       | FatFreeMass14; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | FatFreeMass16; O       | FatFreeMass17; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | FatFreeMass19; C       | FatFreeMass20; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | FatFreeMass22; C       | FatFreeMass23; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | FatFreeMass25; C       | FatFreeMass26; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Concepts 6; O          | FatFreeMass27; R |
+| <b>Test purpose</b>      | Check that:<br>Fat Free Mass Numeric Object contains the attributes specified for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                  |
+| <b>Applicability</b>     | C_AG_OXP_167 AND C_AG_OXP_181 AND C_AG_BCA_004 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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.</li> <li>5. Once the PHD under test sends the tested configuration, check the Fat Free Mass object.</li> <li>6. The Fat Free Mass object contents shall be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_SCADA   MDC_MASS_BODY_FAT_FREE</li> </ul> </li> <li>b. IF Not Recommended attribute Supplemental-Types <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;Sequence of TYPE (TYPE.length = 4 bytes)</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> </li> <li>d. IF Not recommended attribute Metric-Structure-Small is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> </ul> </li> </ol> </li> </ol> |                        |                  |
+
+- attribute-type = MetricStructureSmall
+- attribute-length = 2 bytes
+- attribute-value = <Not relevant for this test>
+- e. 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>
+- 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. Mandatory attribute Unit-Code
+  - attribute-id = MDC\_ATTR\_UNIT\_CODE
+  - attribute-type = OID-Type
+  - attribute-value.length = 2 bytes
+  - attribute-value = MDC\_DIM\_KILO\_G or MDC\_DIM\_LB
+- j. Conditional attribute Attribute-Value-Map
+  - attribute-id = MDC\_ATTR\_ATTRIBUTE\_VAL\_MAP
+  - attribute-type = AttrValMap
+  - attribute-count = 2
+  - attribute-value = <Not relevant for this test>
+- k. 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>
+- l. 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>
+- m. IF Not recommended Compound-Simple-Nu-Observed-Value is present
+  - attribute-id = MDC\_ATTR\_NU\_CMPD\_VAL\_OBS\_SIMP
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-type = SimpleNuObsValueCmp</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> <li>n. IF Not recommended attribute Basic-Nu-Observed-Value is present</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-value.length = 2bytes</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> <li>o. IF Not recommended attribute Compound-Basic-Nu-Observed-Value is present</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_BASIC</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-type = BasicNuObsValueCmp</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> <li>p. IF Not recommended attribute Nu-Observed-Value is present</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-type = NuObsValue</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-value.length = 10bytes</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> <li>q. Not recommended attribute Compound-Nu-Observed-Value</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_SIMP</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-type = NuObsValueCmp</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> <li>r. IF Recommended attribute Accuracy is present</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+|                 |                                                  |                        |                   |                   |
+|-----------------|--------------------------------------------------|------------------------|-------------------|-------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/BCA/BV-011                      |                        |                   |                   |
+| <b>TP label</b> | Soft Lean Mass Object for Extended Configuration |                        |                   |                   |
+| <b>Coverage</b> | <b>Spec</b>                                      | [ISO/IEEE 11073-10420] |                   |                   |
+|                 | <b>Testable items</b>                            | SoftLeanMass1; O       | SoftLeanMass2; M  | SoftLeanMass3; M  |
+|                 |                                                  | SoftLeanMass4; M       | SoftLeanMass5; R  | SoftLeanMass6; M  |
+|                 |                                                  | SoftLeanMass7; R       | SoftLeanMass8; R  | SoftLeanMass9; R  |
+|                 |                                                  | SoftLeanMass10; R      | SoftLeanMass11; R | SoftLeanMass12; M |
+|                 |                                                  | SoftLeanMass13; C      | SoftLeanMass14; R | SoftLeanMass15; O |
+|                 |                                                  | SoftLeanMass16; O      | SoftLeanMass17; C | SoftLeanMass18; C |
+|                 |                                                  | SoftLeanMass19; C      | SoftLeanMass20; R | SoftLeanMass21; C |
+|                 |                                                  | SoftLeanMass22; C      | SoftLeanMass23; C | SoftLeanMass24; C |
+|                 |                                                  | SoftLeanMass25; C      | SoftLeanMass26; C | SoftLeanMass27; R |
+|                 |                                                  | Concepts 7; O          |                   |                   |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>      | Check that:<br>Soft Lean Mass Numeric Object contains the attributes specified for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Applicability</b>     | C_AG_OXP_167 AND C_AG_OXP_181 AND C_AG_BCA_003 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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.</li> <li>5. Once the PHD under test sends the tested configuration, check the Soft Lean Mass object.</li> <li>6. The Soft Lean Mass object contents shall be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_SCADA   MDC_MASS_BODY_SOFT_LEAN</li> </ol> </li> <li>b. IF Not Recommended attribute Supplemental-Types <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;Sequence of TYPE (TYPE.length = 4 bytes)</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>d. IF Not recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>e. IF Recommended attribute Measurement-Status is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>f. IF Not recommended attribute Metric-Id is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>g. IF Not Recommended attribute Metric-Id-List is present</li> </ol> </li> </ol> |
+
+- 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. Mandatory attribute Unit-Code
+  - attribute-id = MDC\_ATTR\_UNIT\_CODE
+  - attribute-type = OID-Type
+  - attribute-value.length = 2 bytes
+  - attribute-value = MDC\_DIM\_KILO\_G or MDC\_DIM\_LB
+- j. Conditional attribute Attribute-Value-Map
+  - attribute-id = MDC\_ATTR\_ATTRIBUTE\_VAL\_MAP
+  - attribute-type = AttrValMap
+  - attribute-count = 2
+  - attribute-value = <Not relevant for this test> attribute-value = <Not relevant for this test>
+- k. 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>
+- l. 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>
+- m. 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 = <variable>
+  - attribute-value = <Not relevant for this test>
+- n. 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>
+- o. 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>
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>p. IF Not recommended attribute Nu-Observed-Value is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS</li> <li><input type="checkbox"/> attribute-type = NuObsValue</li> <li><input type="checkbox"/> attribute-value.length = 10bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>q. Not recommended attribute Compound-Nu-Observed-Value</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_SIMP</li> <li><input type="checkbox"/> attribute-type = NuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>r. IF Recommended attribute Accuracy is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/BCA/BV-012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                |
+| <b>TP label</b>          | Body Water Object for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-10420] |                |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | BodyWater1; O          | BodyWater2; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | BodyWater4; M          | BodyWater5; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | BodyWater7; R          | BodyWater8; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | BodyWater10; R         | BodyWater11; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | BodyWater13; C         | BodyWater14; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | BodyWater16; O         | BodyWater17; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | BodyWater19; C         | BodyWater20; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | BodyWater22; C         | BodyWater23; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | BodyWater25; C         | BodyWater26; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | BodyWater28; O         | Concepts 8; O  |
+| <b>Test purpose</b>      | Check that:<br>Body Water Numeric Object contains the attributes specified for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                |
+| <b>Applicability</b>     | C_AG_OXP_167 AND C_AG_OXP_181 AND C_AG_BCA_002 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |                |
+| <b>Test procedure</b>    | 1. The simulated PHG receives an association request from the PHD under test.<br>2. The simulated PHG responds with a result = accepted-unknown-config.<br>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.<br>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.<br>5. Once the PHD under test sends the tested configuration, check the Body Water object.<br>6. The Body Water object contents shall be: |                        |                |
+
+- a. Mandatory attribute Type
+  - attribute-id = MDC\_ATTR\_ID\_TYPE
+  - attribute-type = TYPE
+  - attribute-value = MDC\_PART\_SCADA | MDC\_BODY\_WATER
+- 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>
+- c. Mandatory attribute Metric-Spec-Small
+  - attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL
+  - attribute-type = MetricSpecSmall
+  - attribute-value.length = 2 bytes
+  - attribute-value = <Not relevant for this test>
+- 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 = <Not relevant for this test>
+- e. 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>
+- 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. Mandatory attribute Unit-Code
+  - attribute-id = MDC\_ATTR\_UNIT\_CODE
+  - attribute-type = OID-Type
+  - attribute-value.length = 2 bytes
+  - attribute-value = MDC\_DIM\_KILO\_G or MDC\_DIM\_LB or MDC\_DIM\_PERCENT.
+
+- The PHD is allowed to report two body water objects, one in kilograms (kg) and the other in percent (%).
+
+#### j. Conditional attribute Attribute-Value-Map
+
+- attribute-id = MDC\_ATTR\_ATTRIBUTE\_VAL\_MAP
+- attribute-type = AttrValMap
+- attribute-count = 2
+- attribute-value = <Not relevant for this test> attribute-value = <Not relevant for this test>
+
+#### k. 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>
+
+##### l. 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>
+
+##### m. 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 = <variable>
+- attribute-value = <Not relevant for this test>
+
+##### n. 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>
+
+##### o. 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>
+
+##### p. 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>
+
+##### q. 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>
+
+##### r. IF Recommended attribute Accuracy is present
+
+- attribute-id = MDC\_ATTR\_NU\_ACCUR\_MSMT
+
+|                           |                                                                                                                                                                                                        |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)<br><input type="checkbox"/> attribute-value.length = 4 bytes<br><input type="checkbox"/> attribute-value = <Not relevant for this test> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                        |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |             |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-------------|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/BCA/BV-013                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |             |
+| <b>TP label</b>           | Operating State. PHG to PHD Maximum APDU Size                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |             |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |             |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | CommonCharac 3; M                                             |             |
+|                           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-10420]                                        |             |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | CommChar1;M                                                   | CommChar2;M |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>The total size of the response does not exceed the maximum APDU size established by the specialization</p> <p>[AND]</p> <p>A body composition analyser PHD implementing only this device specialization shall be capable of receiving any APDU up to a size of Nrx.</p> <p>For this standard, Nrx shall be 1230 octets.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                               |             |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_167                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                               |             |
+| <b>Other PICS</b>         | C_AG_OXP_041, C_AG_OXP_100                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |             |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |             |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG issues a "Remote Operation Invoke   Get" command with: <ol style="list-style-type: none"> <li>a. Obj-handle set to 0 (to request for an MDS object)</li> <li>b. attribute-id-list.count = 606</li> <li>c. attribute-id-list: (MDC_ATTR_ID_MODEL, MDC_ATTR_SYS_ID, MDC_ATTR_DEV_CONFIG_ID) repeated 202 times</li> </ol> </li> <li>2. Check the response of the PHD.</li> <li>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.</li> <li>4. Check the response of the PHD.</li> </ol>                                                                                                                                                                                                                                                                                                                                                           |                                                               |             |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• 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. <ul style="list-style-type: none"> <li>○ 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): <ul style="list-style-type: none"> <li>▪ Pulse oximeter → 9216 octets</li> <li>▪ Weighing scales → 896 octets</li> <li>▪ Glucose meter → 5120 octets or 64512 octets if the PHD supports PM-Store</li> <li>▪ Blood pressure → 896 octets</li> <li>▪ Thermometer → 896 octets</li> <li>▪ Independent activity hub → 5120 octets</li> <li>▪ Cardiovascular → 64512 octets or 6624 octets if the PHD under test only</li> </ul> </li> </ul> </li> </ul> |                                                               |             |
+
+|              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|              | <p>supports Step Counter Profile</p> <ul style="list-style-type: none"> <li>▪ Strength → 64512 octets:</li> <li>▪ Adherence monitor → 1024 octets</li> <li>▪ Peak flow → 2030 octets</li> <li>▪ Body composition Analyser → 7730 octets</li> <li>▪ Body composition Analyser → 7730 octets</li> <li>▪ Basic ECG/Simple ECG → 7168 octets or 64512 octets if the PHD supports PM-Store</li> <li>▪ Basic ECG/Heart rate → 1280 octets or 64512 octets if the PHD supports PM-Store</li> <li>▪ International normalized ratio → 896 octets or 64512 if the PHD supports PM-Store</li> <li>○ In the case where it responds with a roer, the reason must not be protocol-violation (23).</li> <li>• In step 4, the PHD must respond with a rors-cmip-get message.</li> </ul> |
+| <b>Notes</b> |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/BCA/BV-014                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                  |
+| <b>TP label</b>          | Association Body composition analyser PHD                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-10420] |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | AgProcAsReq1; M        | AgProcAsReq2; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | AgProcAsReq4; M        | AgProcAsReq5; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | AgProcAsReq7; M        | AgProcAsReq8; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | AgProcAsReq10; M       | AgProcAsReq11; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | MDSMethods 4; M        |                  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>During the association procedure, the Body composition analyser PHD sends the correct association request to the simulated PHG</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                  |
+| <b>Applicability</b>     | C_AG_OXP_167 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |                  |
+| <b>Other PICS</b>        | C_AG_OXP_002, C_AG_OXP_017                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                  |
+| <b>Test procedure</b>    | <p>1. The PHD sends a message to associate to the simulated PHG, the expected fields sent by the PHD are:</p> <ul style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = AarqApdu</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field-value = 0xE2 0x00.</li> </ul> </li> <li>b. assoc-version <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = AssociationVersion</li> <li><input type="checkbox"/> field-length = BITS-32</li> <li><input type="checkbox"/> field- value = 0x80 0x00 0x00 0x00</li> </ul> </li> <li>c. data-proto-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = DataProtoId(INT-U16)</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field- value = 0x50 0x79 (20601)</li> </ul> </li> <li>d. protocol-version</li> </ul> |                        |                  |
+
+- 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 not 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 =
+  - <0x07D0> 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 only Body composition analyser specialization → Bit 15 is set (data-req-supp-init-agent(15))
+
+##### l. data-req-init-agent-count (DataReqModeCapab)
+
+- field- type = INT-U8
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field.value = 0x01</li> </ul> m. data-req-init-manager-count (DataReqModeCapab) <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = INT-U8</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field.value = 0x00</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked attributes have proper values.                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |  |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/BCA/BV-015                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |  |
+| <b>TP label</b>           | Set Time Body composition analyser PHD                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-10420] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | MDSMethods 1; C        |  |
+| <b>Test purpose</b>       | Check that:<br>If the PHD supports the Absolute-Time-Stamp attribute, this method (Set Time) shall be implemented                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |  |
+| <b>Applicability</b>      | C_AG_OXP_167 AND C_AG_OXP_000 AND C_AG_OXP_009                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |  |
+| <b>Test procedure</b>     | 1. The simulated PHG sends a SET action: <ul style="list-style-type: none"> <li><input type="checkbox"/> CHOICE = SetTimeInvoke</li> <li><input type="checkbox"/> action-type = MDC_ACT_SET_TIME</li> <li><input type="checkbox"/> the action-info-args are SetTimeInvoke <ul style="list-style-type: none"> <li>▪ date-time = &lt;century, year ≤ 99 month ≤ 12 day ≤ 31 hour ≤ 24 minute ≤ 60 second ≤ 60 sec-fractions ≤ 100&gt;</li> <li>▪ accuracy = 0</li> </ul> </li> </ul> 2. The PHD under test response shall be a rors-cmip-confirmed-action: <ul style="list-style-type: none"> <li><input type="checkbox"/> action-type = MDC_ACT_SET_TIME</li> <li><input type="checkbox"/> action-info-args shall be empty.</li> </ul> |                        |  |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |  |
+
+|                      |                                                                                                                                                                                                                                                                        |                        |  |
+|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>         | TP/PLT/PHD/CLASS/BCA/BV-016                                                                                                                                                                                                                                            |                        |  |
+| <b>TP label</b>      | Config Changes Service. Contextual Attribute.                                                                                                                                                                                                                          |                        |  |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-10420] |  |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                  | BCA_NumGen3; M         |  |
+| <b>Test purpose</b>  | Check that:<br>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<br>[AND]<br>Service component reports configuration changes to future measurements only |                        |  |
+| <b>Applicability</b> | C_AG_OXP_174 AND C_AG_BCA_005 AND C_AG_OXP_000                                                                                                                                                                                                                         |                        |  |
+| <b>Other PICS</b>    |                                                                                                                                                                                                                                                                        |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>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.</li> <li>2. Make a change to the contextual attribute Unit-Code for Body Weight object (Pounds to kg or kg to pounds).</li> <li>3. The PHD shall send an MDS event report indicating the new contextual attribute value.</li> <li>4. Take some more measurements.</li> <li>5. Wait for the PHG to receive new event reports from the PHD, which report the measurements from step 4.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>▪ The PHD sends an MDS event report to inform about the contextual attribute that has been changed.</li> <li>▪ Data has changed accordingly to a new contextual attribute.</li> </ul>                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |  |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/BCA/BV-017                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |  |
+| <b>TP label</b>           | Config Changes Service. Body Height object Contextual Attribute.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-10420] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | BCA_NumGen3; M         |  |
+| <b>Test purpose</b>       | Check that:<br><br>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                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |  |
+| <b>Applicability</b>      | C_AG_OXP_174 AND C_AG_BCA_006 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>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.</li> <li>2. Make a change to the contextual attribute Unit-Code for Body Height object (centimetres to inches or inches to centimetres).</li> <li>3. The PHD shall send an MDS event report indicating the new contextual attribute value.</li> <li>4. Take some more measurements.</li> <li>5. Wait for the PHG to receive new event reports from the PHD, which report the measurements from step 4.</li> </ol> |                        |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>▪ The PHD sends an MDS event report to inform about the contextual attribute that has been changed.</li> <li>▪ Data has changed accordingly to a new contextual attribute.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                         |                        |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |  |
+
+|                     |                                                                                                                                                                                                                                                                                    |                        |  |
+|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/BCA/BV-018                                                                                                                                                                                                                                                        |                        |  |
+| <b>TP label</b>     | Config Changes Service. Body Fat object Contextual Attribute.                                                                                                                                                                                                                      |                        |  |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-10420] |  |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                              | BCA_NumGen3; M         |  |
+| <b>Test purpose</b> | Check that:<br><br>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<br><br>[AND]<br><br>Service component reports configuration changes to future measurements only |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Applicability</b>      | C_AG_OXP_174 AND C_AG_BCA_007 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>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.</li> <li>2. Make a change to the contextual attribute Unit-Code for Body Weight object (Pounds to kg or kg to pounds).</li> <li>3. The PHD shall send an MDS event report indicating the new contextual attribute value.</li> <li>4. Take some more measurements.</li> <li>5. Wait for the PHG to receive new event reports from the PHD, which report the measurements from step 4.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>▪ The PHD sends an MDS event report to inform about the contextual attribute that has been changed.</li> <li>▪ Data has changed accordingly to a new contextual attribute.</li> </ul>                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+## 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.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-PHG PICS & PIXIT] Personal Health Gateway DG2016 PICS and PIXIT excel sheet v1.9.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-TCRL] Test Case Reference List\_DG2016\_v1.11.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-TI] Continua DG2016 PHD Testable items excel sheet v1.8.  
+<http://handle.itu.int/11.1002/2000/12067>
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.13-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.845.13-201704-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..0180ea43aba3030dcab94b09a5121ee09e264d9a
--- /dev/null
+++ b/marked/H/T-REC-H.845.13-201704-I_PDF-E/raw.md
@@ -0,0 +1,1365 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.845.13**
+
+(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 5M: Basic electrocardiograph**
+
+Recommendation ITU-T H.845.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        |
+| 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        |
+| <b>Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN)</b> | <b>H.820–H.859</b> |
+| 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.13
+
+## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5M: Basic electrocardiograph
+
+## Summary
+
+Recommendation ITU-T H.845.13 provides a test suite structure (TSS) and the test purposes (TP) for basic electrocardiograph 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.13 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5M: Device Specializations. Personal Health Device (Basic Electrocardiograph) (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.845.13 | 2015-01-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/12273">11.1002/1000/12273</a> |
+| 2.0     | ITU-T H.845.13 | 2016-07-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12950">11.1002/1000/12950</a> |
+| 3.0     | ITU-T H.845.13 | 2017-04-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/13230">11.1002/1000/13230</a> |
+
+## Keywords
+
+Basic electrocardiograph, 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, touch area network.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.13: Basic electrocardiograph (ECG) ..... | 9  |
+|         | Bibliography.....                                     | 49 |
+
+**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 5M: Device Specializations. Personal Health Device (Basic Electrocardiograph) (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     | 2013-05-24 | Initial release for Test Tool DG2012.                                                                                                                                                                                                                                                                                                                           |
+| 1.1     | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_PAN-LAN_PART_5M_v1.0.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]: <ul style="list-style-type: none"><li>• Adds glucose meter BLE</li><li>• Adds BLE SSP support</li><li>• Adds NFC new transport</li><li>• Adds INR device specialization</li></ul> |
+| 1.2     | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_PLT_PART_5M_v1.1.doc" as a baseline and adds new features included in Documentation Enhancements: <ul style="list-style-type: none"><li>• "Other PICS" row added</li></ul>                                                                                            |
+| 1.3     | 2015-07-01 | Initial release for Test Tool DG2015. It uses "TSS&TP_DG2013_PLT_PART_5M_v1.2.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2015)]/[b-CDG 2015]                                                                                                                                                                                          |
+| 1.4     | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2015_PLT_PART_5M_v1.3.doc" as a baseline and adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016]                                                                                                                                                                                            |
+
+## Recommendation ITU-T H.845.13
+
+## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5M: Basic electrocardiograph
+
+## 1 Scope
+
+The scope of this Recommendation<sup>1</sup> 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 5M.
+
+- 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
+
+---
+
+<sup>1</sup> 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.  
+<https://www.iso.org/standard/54331.html> with  
+<https://www.iso.org/standard/63972.html>
+- [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.  
+<https://www.iso.org/standard/66717.html> with  
+<https://www.iso.org/standard/71886.html>
+- [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)*.  
+<https://www.iso.org/standard/61876.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:
+
+DUT            Device Under Test
+
+|       |                                                       |
+|-------|-------------------------------------------------------|
+| CDG   | Continua Design Guidelines                            |
+| CGM   | Continuous Glucose Monitor                            |
+| INR   | International Normalized Ratio                        |
+| IP    | Insulin Pump                                          |
+| MDS   | Medical Device System                                 |
+| NFC   | Near Field Communication                              |
+| PAN   | Personal Area Network                                 |
+| 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                         |
+| 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 |
+|------------------|------------------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| 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.13 (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 <http://handle.itu.int/11.1002/2000/12067>.
+
+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>/<DUT>/<GR>/<SGR>/<XX> – <NNN>). It is specified according to the naming convention defined below:
+  - Each test purpose identifier is introduced by the prefix "TP".
+  - <TT>: 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)
+  - <DUT>: This is the device under test:
+    - PHD: Personal Health Device
+    - PHG: Personal Health Gateway
+  - <GR>: This identifies a group of test cases.
+  - <SGR>: This identifies a subgroup of test cases.
+  - <XX>: This identifies the type of testing:
+    - BV: Valid behaviour test
+    - BI: Invalid behaviour test
+  - <NNN>: 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 device under test (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.13: Basic electrocardiograph (ECG)
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                 |                  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ECG/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                 |                  |
+| <b>TP label</b>          | Get MDS Object for Basic ECG specialization/Heart Rate profile: Mandatory, Conditional and Optional Attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                 |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [ISO/IEEE 11073-10406] |                 |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ECG_MDSAttr1; M        | ECG_MDSAttr2; M | ECG_MDSAttr3; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | ECG_MDSAttr4; M        | ECG_MDSAttr5; M | ECG_MDSAttr6; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | ECG_MDSAttr7; R        | ECG_MDSAttr8; R | ECG_MDSAttr10; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | OperProc2; M           |                 |                  |
+| <b>Test purpose</b>      | Check that:<br>The PHD supports a Get command that requests all attributes<br>[AND]<br>The MDS Object contains the attributes specified for a Heart Rate PHD.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                 |                  |
+| <b>Applicability</b>     | C_AG_OXP_164 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                 |                  |
+| <b>Other PICS</b>        | C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |                 |                  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                 |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>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.</li> <li>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:<br/> MDS Attributes: <ol style="list-style-type: none"> <li>a. Not Recommended attribute System-Type. <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SYS_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;not relevant&gt;</li> </ul> </li> <li>b. Mandatory attribute System-Type-Spec-List <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SYS_TYPE_SPEC_LIST</li> <li><input type="checkbox"/> attribute-type = TypeVerList</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes attribute-value = {MDC_DEV_SPEC_PROFILE_ECG, 1} and {MDC_DEV_SUB_SPEC_PROFILE_HR, 1}</li> </ul> </li> <li>c. Mandatory attribute System-model <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_MODEL</li> <li><input type="checkbox"/> attribute-type = SystemModel</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value = {Manufacturer, Model}</li> </ul> </li> </ol> </li> </ol> |                        |                 |                  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>d. Mandatory attribute Dev-Configuration-Id</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_DEV_CONFIG_ID</li> <li><input type="checkbox"/> attribute-type = ConfigId</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>– IF NOT C_AG_OXP_181 then attribute-value = 0x0258</li> <li>– ELSE attribute-value = &lt; between 0x4000 and 0x7FFF&gt;</li> </ul> </li> </ul> <p>e. Recommended attribute Power-Status</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_POWER_STAT</li> <li><input type="checkbox"/> attribute-type = PowerStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = <p>ON_MAINS (0x8000) or ON_BATTERY(0x4000)</p> <p>Only one of the following may be active:</p> <ul style="list-style-type: none"> <li>▪ chargingFull(8),</li> <li>▪ chargingTrickle(9),</li> <li>▪ chargingOff(10).</li> <li>▪ The rest of the bits must not be set</li> </ul> </li> </ul> <p>f. Recommended attribute Battery-Level</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_VAL_BATT_CHARGE (0X09 0X9C)</li> <li><input type="checkbox"/> attribute-type = INT-U16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;value between 0 and 100&gt; If value &gt;100, the meaning of the value is “undefined”</li> </ul> <p>g. Recommended attribute Remain-Battery-Time</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_BATT_REMAIN (0X09 0X88)</li> <li><input type="checkbox"/> attribute-type = BatMeasure</li> <li><input type="checkbox"/> attribute-value.length = 6 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;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) or MDC_DIM_DAY (0x08 0xE0) &gt;</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                 |                                                                                                                |                        |                  |
+|-----------------|----------------------------------------------------------------------------------------------------------------|------------------------|------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/ECG/BV-001                                                                                    |                        |                  |
+| <b>TP label</b> | Get MDS Object for Basic ECG specialization/Simple ECG profile: Mandatory, Conditional and Optional Attributes |                        |                  |
+| <b>Coverage</b> | <b>Spec</b>                                                                                                    | [ISO/IEEE 11073-10406] |                  |
+|                 | <b>Testable items</b>                                                                                          | ECG_MDSAttr1; M        | ECG_MDSAttr2; M  |
+|                 |                                                                                                                | ECG_MDSAttr4; M        | ECG_MDSAttr5; M  |
+|                 |                                                                                                                | ECG_MDSAttr7; R        | ECG_MDSAttr8; R  |
+|                 |                                                                                                                | OperProc2; M           | ECG_MDSAttr10; M |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>      | Check that:<br>The PHD supports a Get command that requests all attributes<br>[AND]<br>The MDS Object contains the attributes specified for a Simple ECG PHD.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Applicability</b>     | C_AG_OXP_165 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Other PICS</b>        | C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>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.</li> <li>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:           <p>MDS Attributes:</p> <ol style="list-style-type: none"> <li>a. Not recommended attribute System-Type               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SYS_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;not relevant&gt;</li> </ul> </li> <li>b. Mandatory attribute System-Type-Spec-List               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SYS_TYPE_SPEC_LIST</li> <li><input type="checkbox"/> attribute-type = TypeVerList</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes attribute-value = {MDC_DEV_SPEC_PROFILE_ECG, 1} and {MDC_DEV_SUB_SPEC_PROFILE_ECG, 1}</li> </ul> </li> <li>c. Mandatory attribute System-model               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_MODEL</li> <li><input type="checkbox"/> attribute-type = SystemModel</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value = {Manufacturer, Model}</li> </ul> </li> <li>d. Mandatory attribute Dev-Configuration-Id               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_DEV_CONFIG_ID</li> <li><input type="checkbox"/> attribute-type = ConfigId</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt; between 0x4000 and 0x7FFF&gt;</li> </ul> </li> <li>e. Recommended attribute Power-Status               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_POWER_STAT</li> <li><input type="checkbox"/> attribute-type = PowerStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value =                   <p>ON_MAINS (0x8000) or ON_BATTERY(0x4000)</p> <p>Only one of the following may be active:</p> <ul style="list-style-type: none"> <li>▪ chargingFull(8),</li> <li>▪ chargingTrickle(9),</li> <li>▪ chargingOff(10).</li> <li>▪ The rest of the bits must not be set</li> </ul> </li> </ul> </li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>f. Recommended attribute Battery-Level</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_VAL_BATT_CHARGE (0X09 0X9C)</li> <li><input type="checkbox"/> attribute-type = INT-U16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;value between 0 and 100&gt; If value &gt;100, the meaning of the value is “undefined”</li> </ul> <p>g. Recommended attribute Remain-Battery-Time</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_BATT_REMAIN (0X09 0X88)</li> <li><input type="checkbox"/> attribute-type = BatMeasure</li> <li><input type="checkbox"/> attribute-value.length = 6 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;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) or MDC_DIM_DAY (0x08 0xE0) &gt;</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |                      |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ECG/BV-002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                      |
+| <b>TP label</b>          | MDS Configuration objects events for Basic ECG specialization/Heart Rate profile                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                      |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [ISO/IEEE 11073-10406] |                      |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | ECG_MDSEvent1; M       | ECG_NumGen1; M       |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | ECG_EnumGen1; M        | HeartRate1; C        |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | HeartRateProfile2; O   | HeartRateProfile3; O |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | HeartRateProfile5; M   | ConfigProc1; M       |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>A Basic ECG PHD shall send the [MDS-Configuration-Event] using a [Confirmed] event report. The [MDS-Configuration-Event] shall include the event-info [ConfigReport].</p> <p>[AND]</p> <p>Check objects supported by the Heart Rate PHD (standard /extended configuration)</p>                                                                                                                                                                                                                                                                                                                                                                                         |                        |                      |
+| <b>Applicability</b>     | C_AG_OXP_164 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                      |
+| <b>Other PICS</b>        | C_AG_OXP_010, C_AG_OXP_181, C_AG_ECG_001, C_AG_ECG_002, C_AG_ECG_003, C_AG_ECG_004, C_AG_ECG_005                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                      |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                      |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = PrstApdu</li> <li><input type="checkbox"/> field-length =2 bytes</li> <li><input type="checkbox"/> field-value =0xE7 0x00</li> </ul> </li> <li>b. invoke-id</li> </ol> </li> </ol> |                        |                      |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = InvokeIDType</li> <li><input type="checkbox"/> field-length =INT-U16</li> <li><input type="checkbox"/> field- value=&lt;Not relevant for this test&gt;</li> </ul> <p>c. message</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = roiv-cmip-confirmed-event-report</li> <li><input type="checkbox"/> field-length =two bytes</li> <li><input type="checkbox"/> field- value=0x01 0x01 (EventReportArgumentSimple)</li> </ul> <p>d. obj-handle (EventReportArgumentSimple)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = HANDLE</li> <li><input type="checkbox"/> field-length =INT-U16</li> </ul> <p>e. event-time (EventReportArgumentSimple)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = Relative Time</li> <li><input type="checkbox"/> field-length =INT-U32</li> <li><input type="checkbox"/> field-value = <ul style="list-style-type: none"> <li>• IF NOT C_AG_OXP_010 THEN value = 0xFF 0xFF 0xFF 0xFF</li> </ul> </li> </ul> <p>f. event-type (EventReportArgumentSimple)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = OID-Type</li> <li><input type="checkbox"/> field-length =INT-U16</li> <li><input type="checkbox"/> field- value=0x 0D 0x 1C (MDC_NOTI_CONFIG)</li> </ul> <p>g. config-report-id (ConfigReport)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = ConfigId</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field- value = <ul style="list-style-type: none"> <li>– IF NOT C_AG_OXP_181 then attribute-value = 0x0258</li> <li>– ELSE attribute-value = &lt; between 0x4000 and 0x7FFF &gt;</li> </ul> </li> </ul> <p>h. obj-class ( ConfigReport → ConfigObjectList (ConfigObject)). To check the objects that are supported by the PHD, Type Attribute will be checked in AttributeList.</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = OID-Type</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field- value = <ul style="list-style-type: none"> <li>– One mandatory numeric object for Heart Rate.</li> <li>– One optional numeric object for R-R Interval.</li> <li>– Up to three optional RT-SA objects for ECG Waveforms.</li> <li>– Two optional enumeration objects for Device Status and Context Data Trigger.</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                 |                                                                                  |                        |                |
+|-----------------|----------------------------------------------------------------------------------|------------------------|----------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/ECG/BV-003                                                      |                        |                |
+| <b>TP label</b> | MDS Configuration objects events for Basic ECG specialization/Simple ECG profile |                        |                |
+| <b>Coverage</b> | <b>Spec</b>                                                                      | [ISO/IEEE 11073-10406] |                |
+|                 | <b>Testable</b>                                                                  | ECG_MDSEvent1; M       | ECG_NumGen1; M |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                      |                      |                      |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------|----------------------|
+|                          | <b>items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ECG_EnumGen1; M      | SimpleECGProfile1; M | SimpleECGProfile2; O |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | SimpleECGProfile3; O | SimpleECGProfile4; O | SimpleECGProfile5; O |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | ConfigProc1; M       |                      |                      |
+| <b>Test purpose</b>      | Check that:<br>A Basic ECG PHD shall send the [MDS-Configuration-Event] using a [Confirmed] event report. The [MDS-Configuration-Event] shall include the event-info [ConfigReport].<br>[AND]<br>Check objects supported by the Simple ECG PHD (standard /extended configuration)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                      |                      |                      |
+| <b>Applicability</b>     | C_AG_OXP_165 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                      |                      |                      |
+| <b>Other PICS</b>        | C_AG_OXP_010, C_AG_OXP_181, C_AG_ECG_001, C_AG_ECG_002, C_AG_ECG_003, C_AG_ECG_004, C_AG_ECG_005                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                      |                      |                      |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                      |                      |                      |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = PrstApdu</li> <li><input type="checkbox"/> field-length =2 bytes</li> <li><input type="checkbox"/> field-value =0xE7 0x00</li> </ol> </li> <li>b. invoke-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = InvokeIDType</li> <li><input type="checkbox"/> field-length =INT-U16</li> <li><input type="checkbox"/> field- value=&lt;Not relevant for this test&gt;</li> </ol> </li> <li>c. message <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = roiv-cmip-confirmed-event-report</li> <li><input type="checkbox"/> field-length =two bytes</li> <li><input type="checkbox"/> field- value=0x01 0x01 (EventReportArgumentSimple)</li> </ol> </li> <li>d. obj-handle (EventReportArgumentSimple) <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = HANDLE</li> <li><input type="checkbox"/> field-length =INT-U16</li> </ol> </li> <li>e. event-time (EventReportArgumentSimple) <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = Relative Time</li> <li><input type="checkbox"/> field-length =INT-U32</li> <li><input type="checkbox"/> field-value = <ul style="list-style-type: none"> <li>• IF NOT C_AG_OXP_010 THEN value = 0xFF 0xFF 0xFF 0xFF</li> </ul> </li> </ol> </li> <li>f. event-type (EventReportArgumentSimple) <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = OID-Type</li> <li><input type="checkbox"/> field-length =INT-U16</li> <li><input type="checkbox"/> field- value=0x 0D 0x 1C (MDC_NOTI_CONFIG)</li> </ol> </li> <li>g. config-report-id (ConfigReport) <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = ConfigId</li> </ol> </li> </ol> </li> </ol> |                      |                      |                      |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field- value = &lt; between 0x4000 and 0x7FFF &gt;</li> <li>h. obj-class ( ConfigReport → ConfigObjectList (ConfigObject)). To check the objects that are supported by the PHD, the Type Attribute will be checked in AttributeList.           <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = OID-Type</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field- value =               <ul style="list-style-type: none"> <li>– One to three mandatory RT-SA objects for ECG Waveforms numeric objects for.</li> <li>– Two optional numeric objects, one for Heart Rate and other for R-R Interval.</li> <li>– Two optional enumeration objects, one for Device Status and the other for Context Data Trigger.</li> </ul> </li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                    |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ECG/BV-004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                    |
+| <b>TP label</b>          | MDS objects events Basic ECG specialization                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                    |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-10406] |                    |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ECG_MDSEvent3; M       | ECG_MDSEvents 4; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | ECG_MDSEvents 6; M     | ObjAccServ1; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | ObjAccServ4; M         | ObjAccServ5; O     |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The PHD sends the MDS-Dynamic-Data-Update-Fixed using a confirmed or unconfirmed event report and it includes the event-info ScanReportInfoFixed.</p> <p>[AND/OR]</p> <p>The PHD sends the MDS-Dynamic-Data-Update-Var using a confirmed or unconfirmed event report and it includes the event-info ScanReportInfoVar.</p> <p>[AND]</p> <p>Agent-initiated mode shall be supported for measurement data transmission.</p> <p>[AND]</p> <p>A Simple ECG or Heart Rate PHD may support either one or both single-person and multi-person event reports</p> <p>[AND]</p> <p>A Heart Rate PHD with standard configuration shall use the fixed format data update messages method for transmitting measurement data</p> <p>[AND]</p> <p>A Simple ECG or Heart Rate PHD with extended configuration may use either fixed or variable format data update messages for transmitting measurement data.</p> |                        |                    |
+| <b>Applicability</b>     | (C_AG_OXP_164 OR C_AG_OXP_165) 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)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                    |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_181, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                    |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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 the tested configuration is received.</li> <li>5. Record the PHD configuration.</li> <li>6. IF C_AG_OXP_293: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ol> </li> <li>7. Take Measurements for every supported object in the PHD under test.</li> <li>8. Wait to receive every event report and check: <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = Event Report</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> 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.</li> </ul> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• Check that every received MDS Event report is one of the following Data APDU and that it is confirmed.</li> <li>• 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: <ul style="list-style-type: none"> <li><input type="checkbox"/> MDC_NOTI_SCAN_REPORT_FIXED</li> <li><input type="checkbox"/> MDC_NOTI_SCAN_REPORT_MP_FIXED</li> </ul> </li> <li>• For Extended Configuration, an MDS Event Report is sent by the PHD under test to report measurements for every object: <ul style="list-style-type: none"> <li><input type="checkbox"/> MDC_NOTI_SCAN_REPORT_FIXED</li> <li><input type="checkbox"/> MDC_NOTI_SCAN_REPORT_MP_FIXED</li> <li><input type="checkbox"/> MDC_NOTI_SCAN_REPORT_VAR</li> <li><input type="checkbox"/> MDC_NOTI_SCAN_REPORT_MP_VAR</li> </ul> </li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                 |                                                       |                        |               |
+|-----------------|-------------------------------------------------------|------------------------|---------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/ECG/BV-005                           |                        |               |
+| <b>TP label</b> | Heart rate Object for Standard Configuration (0x0258) |                        |               |
+| <b>Coverage</b> | <b>Spec</b>                                           | [ISO/IEEE 11073-10406] |               |
+|                 | <b>Testable</b>                                       | HeartRate2; M          | HeartRate4; M |
+
+HeartRate6; R
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                |                |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------------|
+| <b>items</b>             | HeartRate8; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | HeartRate10; R | HeartRate12; O |
+|                          | HeartRate14; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | HeartRate16; R | HeartRate18; R |
+|                          | HeartRate20; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | HeartRate22; M | HeartRate24; R |
+|                          | HeartRate26; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | HeartRate28; O | HeartRate30; R |
+|                          | HeartRate32; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | HeartRate34; C | HeartRate36; R |
+|                          | HeartRate38; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | HeartRate40; R | HeartRate42; R |
+|                          | HeartRate44; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | HeartRate46; R | HeartRate48; R |
+|                          | HeartRate50; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | HeartRate52; R | HeartRate54; M |
+|                          | HeartRate55; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | HeartRate56; C | ConfigProc2; M |
+| <b>Test purpose</b>      | Check that:<br>Heart Rate Numeric Object contains the attributes specified for Standard Configuration (0x0258)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                |                |
+| <b>Applicability</b>     | C_AG_OXP_164 AND (NOT C_AG_OXP_181) AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                |                |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                |                |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                |                |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is set to 0x0258. 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 0x0258 is received.</li> <li>5. Once the PHD under test sends a standard configuration, check Heart Rate object.</li> <li>6. The Heart Rate object contents shall be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_HANDLE</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x01</li> </ol> </li> <li>b. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x02 (MDC_PART_SCADA), 0x41 0x82 (MDC_ECG_HEART_RATE 16770)</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 1 (mss-avail-stored-data(1)) is set.</li> <li>• Bit 9 (mss-acc-agent-initiated(9)) is set.</li> <li>• IF bit 3 (mss-msmt-aperiodic) is set THEN bit 5 (mss-msmt-btb-metric)</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                |                |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>d. Mandatory attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = MDC_DIM_BEAT_PER_MIN</li> </ul> <p>e. Mandatory attribute Attribute-Value-Map</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = AttrValMap</li> <li><input type="checkbox"/> attribute-count = 2</li> <li><input type="checkbox"/> attribute-value = (MDC_ATTR_NU_VAL_OBS_BASIC, 2<br/>MDC_ATTR_TIME_STAMP_REL, 4)</li> </ul> <p>7. Check that no other attributes are present in the initial configuration.</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                          |                                                                                                                                                                                                                                                                                                                            |                        |                |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ECG/BV-006                                                                                                                                                                                                                                                                                                |                        |                |
+| <b>TP label</b>          | Heart Rate Object for Extended Configuration                                                                                                                                                                                                                                                                               |                        |                |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-10406] |                |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                      | HeartRate3; M          | HeartRate5; M  |
+|                          |                                                                                                                                                                                                                                                                                                                            | HeartRate9; M          | HeartRate11; R |
+|                          |                                                                                                                                                                                                                                                                                                                            | HeartRate15; R         | HeartRate17; R |
+|                          |                                                                                                                                                                                                                                                                                                                            | HeartRate21; M         | HeartRate23; C |
+|                          |                                                                                                                                                                                                                                                                                                                            | HeartRate27; O         | HeartRate29; O |
+|                          |                                                                                                                                                                                                                                                                                                                            | HeartRate33; C         | HeartRate35; C |
+|                          |                                                                                                                                                                                                                                                                                                                            | HeartRate39; R         | HeartRate41; C |
+|                          |                                                                                                                                                                                                                                                                                                                            | HeartRate45; C         | HeartRate47; C |
+|                          |                                                                                                                                                                                                                                                                                                                            | HeartRate51; C         | HeartRate53; R |
+|                          |                                                                                                                                                                                                                                                                                                                            | HeartRate56; C         |                |
+| <b>Test purpose</b>      | Check that:<br>Heart Rate Numeric Object contains the attributes specified for Extended Configuration                                                                                                                                                                                                                      |                        |                |
+| <b>Applicability</b>     | (C_AG_OXP_164 OR C_AG_OXP_165) AND C_AG_ECG_001 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                          |                        |                |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_046, C_AG_OXP_047, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                       |                        |                |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                    |                        |                |
+| <b>Test procedure</b>    | 1. The simulated PHG receives an association request from the PHD under test.<br>2. The simulated PHG responds with a result = accepted-unknown-config.<br>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. 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 Heart Rate object.
+6. The Heart Rate object contents shall be:
+  - a. Mandatory attribute Type
+    - attribute-id = MDC\_ATTR\_ID\_TYPE
+    - attribute-type = TYPE
+    - attribute-value = one of these values:
+      - 0x00 0x02 (MDC\_PART\_SCADA), 0x41 0x82 (MDC\_ECG\_HEART\_RATE 16770)
+      - 0x00 0x80 (MDC\_PART\_DM 182), 0x55 0xDE (MDC\_ECG\_HEART\_RATE\_INSTANT 21982)
+  - 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>
+  - c. Mandatory attribute Metric-Spec-Small
+    - attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL
+    - attribute-type = MetricSpecSmall
+    - attribute-value.length = 2 bytes
+    - attribute-value =
+      - IF bit 3 (mss-msmt-aperiodic) is set THEN bit 5 (mss-msmt-btb-metric)
+  - 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 = <Not relevant for this test>
+  - e. IF Optional 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>
+  - 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
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> i. Mandatory attribute Unit-Code <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = MDC_DIM_BEAT_PER_MIN</li> </ul> j. IF Not recommended attribute Source-Handle-Reference is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> k. IF Not recommended attribute Measure-Active-Period <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> l. IF Not Recommended attribute Accuracy is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                 |                                                |                        |                 |                 |
+|-----------------|------------------------------------------------|------------------------|-----------------|-----------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/ECG/BV-007                    |                        |                 |                 |
+| <b>TP label</b> | R-R Interval Object for Extended Configuration |                        |                 |                 |
+| <b>Coverage</b> | <b>Spec</b>                                    | [ISO/IEEE 11073-10406] |                 |                 |
+|                 | <b>Testable items</b>                          | RRInterval1; M         | RRInterval2; M  | RRInterval3; R  |
+|                 |                                                | RRInterval4; M         | RRInterval5; R  | RRInterval6; O  |
+|                 |                                                | RRInterval7; R         | RRInterval8; R  | RRInterval9; R  |
+|                 |                                                | RRInterval10; M        | RRInterval11; C | RRInterval12; R |
+|                 |                                                | RRInterval13; O        | RRInterval14; O | RRInterval15; C |
+|                 |                                                | RRInterval16; C        | RRInterval17; C | RRInterval18; C |
+|                 |                                                | RRInterval19; R        | RRInterval20; C | RRInterval21; C |
+|                 |                                                | RRInterval22; C        | RRInterval23; C | RRInterval24; C |
+|                 |                                                | RRInterval25; C        | RRInterval26; R | RRInterval27; M |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>      | Check that:<br>R-R Interval Numeric Object contains the attributes specified for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Applicability</b>     | (C_AG_OXP_164 OR C_AG_OXP_165) AND C_AG_ECG_002 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_046, C_AG_OXP_047, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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.</li> <li>5. Once the PHD under test sends the tested configuration, check the R-R Interval object.</li> <li>6. The R-R Interval object contents shall be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x02 (MDC_PART_SCADA), 0x3F 0x28 (MDC_ECG_TIME_PD_RR_GL 16168)</li> </ol> </li> <li>b. IF Not Recommended attribute Supplemental-Types <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;Sequence of TYPE (TYPE.length= 4 bytes)</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>• Bit 3 (mss-msmt-aperiodic) is set</li> <li>• Bit 5 (mss-msmt-btb-metric) is set</li> </ul> </li> </ol> </li> <li>d. IF Not recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>e. IF Optional attribute Measurement-Status is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>f. IF Not recommended attribute Metric-Id is present</li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO<br><input type="checkbox"/> attribute-type = OID-Type(INT-U16)<br><input type="checkbox"/> attribute-value.length = 2 bytes<br><input type="checkbox"/> attribute-value = <Not relevant for this test><br>g. IF Not Recommended attribute Metric-Id-List is present<br><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIS<br><input type="checkbox"/> attribute-type = MetricIdList<br><input type="checkbox"/> attribute-value = <Not relevant for this test><br>h. IF Not recommended attribute Metric-Id-Partition is present<br><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART<br><input type="checkbox"/> attribute-type = NomPartition(INT-U16)<br><input type="checkbox"/> attribute-value.length = 2 bytes<br><input type="checkbox"/> attribute-value = <Not relevant for this test><br>i. Mandatory attribute Unit-Code<br><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE<br><input type="checkbox"/> attribute-type = OID-Type<br><input type="checkbox"/> attribute-value.length = 2 bytes<br><input type="checkbox"/> attribute-value = MDC_DIM_MILLI_SEC or MDC_DIM_TICK<br>j. IF Not recommended attribute Source-Handle-Reference is present<br><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF<br><input type="checkbox"/> attribute-type = HANDLE(INT-U16)<br><input type="checkbox"/> attribute-value.length = 2 bytes<br><input type="checkbox"/> attribute-value = <Not relevant for this test><br>k. IF Not recommended attribute Measure-Active-Period<br><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE<br><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)<br><input type="checkbox"/> attribute-value.length = 4 bytes<br><input type="checkbox"/> attribute-value = <Not relevant for this test><br>l. IF Not Recommended attribute Accuracy is present<br><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT<br><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)<br><input type="checkbox"/> attribute-value.length = 4 bytes<br><input type="checkbox"/> attribute-value = <Not relevant for this test> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                 |                                                       |                        |                 |
+|-----------------|-------------------------------------------------------|------------------------|-----------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/ECG/BV-008                           |                        |                 |
+| <b>TP label</b> | Tick-Resolution attribute for R-R Interval Tick units |                        |                 |
+| <b>Coverage</b> | <b>Spec</b>                                           | [ISO/IEEE 11073-10406] |                 |
+|                 | <b>Testable items</b>                                 | ECG_MDSAttr9; C        | RRInterval28; C |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>       | Check that:<br>If the PHD implements the R-R interval object and uses MDC_DIM_TICK for the corresponding Unit-Code attribute, the Tick-Resolution attribute shall be implemented.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Applicability</b>      | (C_AG_OXP_164 OR C_AG_OXP_165) AND C_AG_ECG_002 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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.</li> <li>5. Once the PHD under test sends the tested configuration, check the R-R Interval object: <ol style="list-style-type: none"> <li>a. Mandatory attribute Unit-Code <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = MDC_DIM_MILLI_SEC or MDC_DIM_TICK</li> </ul> </li> </ol> </li> <li>6. IF the Unit-code of the R-R Interval object is MDC_DIM_TICK THEN <ol style="list-style-type: none"> <li>i. 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.</li> <li>ii. 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: <ol style="list-style-type: none"> <li>a. Conditional attribute Tick-Resolution is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TICK_RES</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> </li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+|                 |                                                |                        |               |               |
+|-----------------|------------------------------------------------|------------------------|---------------|---------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/ECG/BV-009                    |                        |               |               |
+| <b>TP label</b> | ECG waveform Object for Extended Configuration |                        |               |               |
+| <b>Coverage</b> | <b>Spec</b>                                    | [ISO/IEEE 11073-10406] |               |               |
+|                 | <b>Testable items</b>                          | Waveform1; M           | Waveform2; M  | Waveform3; R  |
+|                 |                                                | Waveform4; M           | Waveform5; O  | Waveform6; R  |
+|                 |                                                | Waveform7; R           | Waveform8; R  | Waveform9; M  |
+|                 |                                                | Waveform10; C          | Waveform11; R | Waveform12; O |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |               |               |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|
+|                          | Waveform13; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Waveform14; C | Waveform15; C |
+|                          | Waveform16; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Waveform17; C | Waveform18; R |
+|                          | Waveform19; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Waveform20; M | Waveform21; M |
+|                          | Waveform22; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |               |               |
+| <b>Test purpose</b>      | Check that:<br>ECG waveform RT-SA Object contains the attributes specified for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |               |               |
+| <b>Applicability</b>     | (C_AG_OXP_164 OR C_AG_OXP_165) AND C_AG_ECG_003 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |               |               |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_041, C_AG_OXP_046, C_AG_OXP_047, C_AG_OXP_180, C_AG_OXP_183, C_AG_OXP_189, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |               |               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |               |               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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.</li> <li>5. Once the PHD under test sends the tested configuration, check the ECG waveform object.</li> <li>6. The ECG waveform object contents shall be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE (0x09 0x2F)</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = one of these values: <ul style="list-style-type: none"> <li>• 0x00 0x02 (MDC_PART_SCADA), 0x01 0x00 (MDC_ECG_ELEC_POTL 256)</li> <li>• 0x00 0x02 (MDC_PART_SCADA), 0x01 0x01 (MDC_ECG_ELEC_POTL_I 257)</li> <li>• 0x00 0x02 (MDC_PART_SCADA), 0x01 0x02 (MDC_ECG_ELEC_POTL_II 258)</li> <li>• 0x00 0x02 (MDC_PART_SCADA), 0x01 0x3D (MDC_ECG_ELEC_POTL_III 317)</li> <li>• 0x00 0x02 (MDC_PART_SCADA), 0x01 0x3E (MDC_ECG_ELEC_POTL_AVR 318)</li> <li>• 0x00 0x02 (MDC_PART_SCADA), 0x01 0x3F (MDC_ECG_ELEC_POTL_AVL 319)</li> <li>• 0x00 0x02 (MDC_PART_SCADA), 0x01 0x40 (MDC_ECG_ELEC_POTL_AVF 320)</li> <li>• 0x00 0x02 (MDC_PART_SCADA), 0x01 0x03 (MDC_ECG_ELEC_POTL_V1 259)</li> <li>• 0x00 0x02 (MDC_PART_SCADA), 0x01 0x04 (MDC_ECG_ELEC_POTL_V2 260)</li> <li>• 0x00 0x02 (MDC_PART_SCADA), 0x01 0x05 (MDC_ECG_ELEC_POTL_V3 261)</li> <li>• 0x00 0x02 (MDC_PART_SCADA), 0x01 0x06</li> </ul> </li> </ul> </li> </ol> </li> </ol> |               |               |
+
+(MDC\_ECG\_ELEC\_POTL\_V4 262)
+
+- 0x00 0x02 (MDC\_PART\_SCADA), 0x01 0x07 (MDC\_ECG\_ELEC\_POTL\_V5 263)
+- 0x00 0x02 (MDC\_PART\_SCADA), 0x01 0x08 (MDC\_ECG\_ELEC\_POTL\_V6 264)
+
+- b. If Not Recommended attribute Supplemental-Types is present
+  - attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES (0x0A 0x61 )
+  - attribute-type = SupplementalTypeList
+  - attribute.value.lengnth= 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 0x40
+    - Bit 9 (mss-acc-agent-initiated(9)) is set
+- d. IF Optional 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>
+- e. 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>
+- f. 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>
+- 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 = <Not relevant for this test>
+- h. Mandatory attribute Unit-Code
+  - attribute-id = MDC\_ATTR\_UNIT\_CODE (0x09 0x96)
+  - attribute-type = OID-Type
+  - attribute-value.length = 2 bytes
+  - attribute-value = MDC\_DIM\_MILLI\_VOLT
+- 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 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>
+
+#### k. Mandatory attribute Sample-Period
+
+- attribute-id = MDC\_ATTR\_TIME\_PD\_SAMP
+- attribute-type = RelativeTime
+- attribute-value.length = 4 bytes
+- attribute-value = <Not relevant in this test>
+
+#### l. Mandatory attribute Scale-and-Range-Specification
+
+- attribute-id = MDC\_ATTR\_SCALE\_SPECN\_I8 or MDC\_ATTR\_SCALE\_SPECN\_I16 or MDC\_ATTR\_SCALE\_SPECN\_I32
+- attribute-type = ScaleRangeSpec8 OR ScaleRangeSpec16 OR ScaleRangeSpec32
+- attribute-value.length = 1, 2 OR 4 bytes, depending on the type
+- attribute-value = <Not relevant in this test>
+
+#### m. Mandatory attribute Sa-Specification
+
+- attribute-id = MDC\_ATTR\_SA\_SPECN
+- attribute-type = SaSpec
+- attribute-value.length = 6 bytes
+- attribute-value = <Not relevant in this test>
+
+#### 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. IF the PHD under sends the ECG waveforms RT-SA observations through a scanner object THEN the simulated PHG enables the scanner and receives the RT-SA event reports. The attribute of interest is:
+
+##### a. Mandatory attribute Type
+
+- attribute-id = MDC\_ATTR\_SIMP\_SA\_OBS\_VAL ((x0A 0x48)
+- attribute-type = OCTET STRING
+- attribute-value = <length must be even>
+
+#### 9. IF the PHD under sends the ECG waveforms RT-SA observations through a PM-Store object THEN the simulated PHG sends a request for PM-Store data (TrigSegmDataXfer) and the PHD sends the RT-SA stored data. The attribute of interest is:
+
+##### a. Mandatory attribute Type
+
+- attribute-id = MDC\_ATTR\_SIMP\_SA\_OBS\_VAL ((x0A 0x48)
+- attribute-type = OCTET STRING
+- attribute-value = <length must be even>
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Pass/Fail Criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              | MetricSpecSmall must set bit mss-acc-agent-initiated(9) to TRUE because Scanner events are agent-initiated by intent in [ISO/IEEE 11073-20601-2015A] in spite of the fact that the PHG enables/disables these objects (see bugzilla #856 for further details, <a href="http://continua.plugfest.com/show_bug.cgi?id=856">http://continua.plugfest.com/show_bug.cgi?id=856</a> ). |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ECG/BV-010                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |  |
+| <b>TP label</b>          | ECG waveform data availability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-10406] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Waveform23; M          |  |
+| <b>Test purpose</b>      | Check that:<br>The ECG waveform data shall be made available only through a scanner object or PM-Store object                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |  |
+| <b>Applicability</b>     | (C_AG_OXP_164 OR C_AG_OXP_165) AND C_AG_ECG_003 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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.</li> <li>5. Check that ECG waveform RT-SA object/s is/are present and record its/their object handle/s.</li> <li>6. If the PHD supports PM-Store: <ol style="list-style-type: none"> <li>a. The simulated PHG sends a Get-Segment-Info object action for the PM-Store object with SegmSelection = all-segment</li> <li>b. The PHD issues a response (rors-cmip-confirmed-action) with the PM-Segment attributes it supports in the SegmentInfoList structure</li> </ol> </li> <li>7. Check that all ECG waveform RT-SA object/s handle/s are referenced in the Scanner or PM-Store objects: <ol style="list-style-type: none"> <li>a. If EpiCfgScanner object (MDC_MOC_SCAN_CFG_EPI) or PeriCfgScanner (MDC_MOC_SCAN_CFG_PERI) is present <ol style="list-style-type: none"> <li>i. IF Attribute Scan-Handle-List is supported: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SCAN_HANDLE_LIST</li> <li><input type="checkbox"/> attribute-type = HANDLEList</li> <li><input type="checkbox"/> attribute-value.length = &lt;Variable&gt;</li> <li><input type="checkbox"/> attribute-value = It must include references to ECG waveform RT-SA objects handles</li> </ul> </li> <li>ii. IF attribute Scan-Handle-Attr-Val-Map is supported: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SCAN_HANDLE_ATTR_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = HANDLEAttrValMap</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value.count = N</li> <li><input type="checkbox"/> attribute-value.length = &lt;Variable&gt;</li> <li><input type="checkbox"/> attribute-value = It must include references to ECG waveform RT-SA objects handles</li> </ul> <p>b. If the PM-Store object (MDC_MOC_VMO_PMSTORE) is present, then check the PM-Segment-Entry-Map of each PM-Segment</p> <p>8. Check the MDS event reports sent by the PHD under test.</p>                                                                                             |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 7.a, all ECG waveform RT-SA objects implemented by the PHD under test must be referenced in the Scan-Handle-List or Scan-Handle-Attr-Val-Map attributes.</li> <li>• In step 7.b, all ECG waveform RT-SA objects implemented by the PHD under test must be referenced (through the PM-Segment-Entry-Map attribute) at least one time in the set of PM-Segments implemented by PM-Store objects.</li> <li>• In step 8, the MDS event report sent by the PHD under test must not include the ECG waveform RT-SA object observations.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                   |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ECG/BV-011                                                                                                                                                                                                                                                                                                                                                                                           |                        |                   |
+| <b>TP label</b>          | Device Status Object for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                       |                        |                   |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-10406] |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                 | DeviceStatus1; M       | DeviceStatus2; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                       | DeviceStatus4; M       | DeviceStatus5; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                       | DeviceStatus7; R       | DeviceStatus8; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                       | DeviceStatus10; R      | DeviceStatus11; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                       | DeviceStatus13; O      | DeviceStatus14; O |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                       | DeviceStatus16; C      | DeviceStatus17; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                       | DeviceStatus19; R      | DeviceStatus20; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                       | DeviceStatus22; M      | DeviceStatus23; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                       | DeviceStatus25; R      | DeviceStatus27; O |
+| <b>Test purpose</b>      | Check that:<br>Device Status Enumeration Object contains the attributes specified for Extended Configuration                                                                                                                                                                                                                                                                                                          |                        |                   |
+| <b>Applicability</b>     | (C_AG_OXP_164 OR C_AG_OXP_165) AND C_AG_ECG_004 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                     |                        |                   |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_046, C_AG_OXP_047, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                  |                        |                   |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                               |                        |                   |
+| <b>Test procedure</b>    | 1. The simulated PHG receives an association request from the PHD under test.<br>2. The simulated PHG responds with a result = accepted-unknown-config.<br>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.<br>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. Once the PHD under test sends the tested configuration, check the Device Status object.
+
+6. The Device Status object contents shall be:
+
+a. Mandatory attribute Type
+
+- attribute-id = MDC\_ATTR\_ID\_TYPE
+- attribute-type = TYPE
+- attribute-value = MDC\_PART\_PHD\_DM, MDC\_ECG\_DEV\_STAT
+
+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>
+
+c. 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>
+
+d. IF Optional 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>
+
+e. 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>
+
+f. 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>
+
+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 = <Not relevant for this test>
+
+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 = <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 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>
+- k. IF Not Recommended 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 = <Not relevant for this test>
+- l. 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= <Not relevant for this test>
+- m. IF PHD supports fixed or variable format MDS event report and it does not support PM-Store or Scanner THEN 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:
+    - leadwire-loss(0)
+    - leadsignal-loss(1)
+    - leadwire-loss-first-lead(2)
+    - leadsignal-loss-first-lead(3)
+    - leadwire-loss-second-lead(4)
+    - leadsignal-loss-second-lead(5)
+    - leadwire-loss-third-lead(6)
+    - leadsignal-loss-third-lead(7)
+    - The rest of the bits must not be set
+- n. 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 = <variable>
+  - attribute-value = <Not relevant for this test>
+- o. IF Not Recommended attribute Enum-Observed-Value is present
+  - attribute-id= MDC\_ATTR\_VAL\_ENUM\_OBS
+  - attribute-type = EnumObsValue
+  - attribute-value.length = <variable>
+  - attribute-value = <Not relevant for this test>
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>p. IF Not recommended attribute Enum-Observed-Value-Partition is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value-length=2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                      |                      |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------------|----------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ECG/BV-012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                      |                      |
+| <b>TP label</b>          | Context Data Trigger Object for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                      |                      |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-10406] |                      |                      |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | ContextDataTrig1; M    | ContextDataTrig2; M  | ContextDataTrig3; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | ContextDataTrig4; M    | ContextDataTrig5; R  | ContextDataTrig6; O  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | ContextDataTrig7; R    | ContextDataTrig8; R  | ContextDataTrig9; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | ContextDataTrig10; R   | ContextDataTrig11; C | ContextDataTrig12; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | ContextDataTrig13; O   | ContextDataTrig14; O | ContextDataTrig15; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | ContextDataTrig16; C   | ContextDataTrig17; C | ContextDataTrig18; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | ContextDataTrig19; R   | ContextDataTrig20; M | ContextDataTrig21; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | ContextDataTrig22; R   | ContextDataTrig23; R | ContextDataTrig24; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | ContextDataTrig25; R   |                      |                      |
+| <b>Test purpose</b>      | Check that:<br>Context Data Trigger Enumeration Object contains the attributes specified for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                      |                      |
+| <b>Applicability</b>     | (C_AG_OXP_164 OR C_AG_OXP_165) AND C_AG_ECG_005 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                      |                      |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_046, C_AG_OXP_047, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                      |                      |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                      |                      |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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 the tested extended configuration is received.</li> <li>5. Once the PHD under test sends the tested configuration, check the Context Data Trigger object.</li> <li>6. The Context Data Trigger object contents shall be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> </ul> </li> </ol> </li> </ol> |                        |                      |                      |
+
+- attribute-type = TYPE
+- attribute-value = MDC\_PART\_PHD\_DM, MDC\_ECG\_EVT\_CTX\_T\_GEN
+- 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>
+- c. 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>
+- d. IF Optional 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>
+- e. 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>
+- f. 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>
+- 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 = <Not relevant for this test>
+- 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 = <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 Not recommended attribute Measure-Active-Period
+  - attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE
+  - attribute-type = FLOAT-Type (INT-U32)
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><input type="checkbox"/> attribute-value.length = 4 bytes</p> <p><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</p> <p>k. IF PHD supports fixed or variable format MDS event report and it does not support PM-Store or Scanner THEN Mandatory attribute Enum-Observed-Value-Simple-OID is present</p> <p><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIMP_OID</p> <p><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</p> <p><input type="checkbox"/> attribute-value.length = 2 bytes</p> <p><input type="checkbox"/> attribute-value = One of these values:</p> <ul style="list-style-type: none"> <li>• MDC_ECG_EVT_CTXT_USER (21978)</li> <li>• MDC_ECG_EVT_CTXT_PERIODIC (21979)</li> <li>• MDC_ECG_EVT_CTXT_DETECTED (21980)</li> <li>• MDC_ECG_EVT_CTXT_EXTERNAL (21981)</li> </ul> <p>l. IF Not Recommended attribute Enum-Observed-Value-Simple-Bit-Str is present</p> <p><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIMP_BIT_STR</p> <p><input type="checkbox"/> attribute-type = BITS-32</p> <p><input type="checkbox"/> attribute-value.length = BITS-32</p> <p><input type="checkbox"/> attribute-value= &lt;Not relevant for this test&gt;</p> <p>m. IF Not Recommended attribute Enum-Observed-Value-Basic-Bit-Str is present</p> <p><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR</p> <p><input type="checkbox"/> attribute-type = BITS-16</p> <p><input type="checkbox"/> attribute-value.length = 2 bytes</p> <p><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</p> <p>n. IF Not Recommended attribute Enum-Observed-Value-Simple-Str is present</p> <p><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_STR</p> <p><input type="checkbox"/> attribute-type = EnumPrintableString</p> <p><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</p> <p><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</p> <p>o. IF Not Recommended attribute Enum-Observed-Value is present</p> <p><input type="checkbox"/> attribute-id= MDC_ATTR_VAL_ENUM_OBS</p> <p><input type="checkbox"/> attribute-type = EnumObsValue</p> <p><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</p> <p><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</p> <p>p. IF Not recommended attribute Enum-Observed-Value-Partition is present</p> <p><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_PART</p> <p><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</p> <p><input type="checkbox"/> attribute-value.length=2 bytes</p> <p><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|                 |                                                                                              |
+|-----------------|----------------------------------------------------------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/ECG/BV-013                                                                  |
+| <b>TP label</b> | PM-Store Object for Basic ECG specialization Extended Configuration. Disable agent-initiated |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                       |  |  |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|--|--|
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | transmissions (MDS Event Reports and Scanner objects) |  |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-10406]                                |  |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | ECG_PMStoreGen2; M                                    |  |  |
+| <b>Test purpose</b>       | Check that:<br>Any configuration with a PM-store shall disable agent-initiated transmission as well as the use of scanner objects and support manager-initiated transmission of data recorded in PM-stores.                                                                                                                                                                                                                                                                                                         |                                                       |  |  |
+| <b>Applicability</b>      | (C_AG_OXP_164 OR C_AG_OXP_165) AND C_AG_OXP_041 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                       |  |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                       |  |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                       |  |  |
+| <b>Test procedure</b>     | 1. Check if the PHD configuration includes scanner objects.<br>2. 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.<br>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.<br>4. The simulated PHG asks for measurement.<br>5. Check event reports that are sent by the PHD. |                                                       |  |  |
+| <b>Pass/Fail criteria</b> | In step 1, the PHD configuration shall not include scanner objects.<br>In step 5, the PHD shall not send the data with MDS event reports.                                                                                                                                                                                                                                                                                                                                                                           |                                                       |  |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                       |  |  |
+
+|                      |                                                                                                                                                                                                                                                                                                                                                                 |                        |                    |                   |
+|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|-------------------|
+| <b>TP Id</b>         | TP/PLT/PHD/CLASS/ECG/BV-014                                                                                                                                                                                                                                                                                                                                     |                        |                    |                   |
+| <b>TP label</b>      | PM-Store Object for Basic ECG specialization Extended Configuration. Periodic PM-Store                                                                                                                                                                                                                                                                          |                        |                    |                   |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-10406] |                    |                   |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                           | PerPMStoreAtt4; M      | PerPMStoreAtt5; M  | PerPMStoreAtt8; M |
+|                      |                                                                                                                                                                                                                                                                                                                                                                 | PerPMStoreAtt9; M      | PerPMStoreAtt14; M |                   |
+| <b>Test purpose</b>  | Check that:<br>The pm-sc-epi-seg-entries bit of the [PM-Store-Capab] attribute shall not be set<br>[AND]<br>The pm-sc-peri-seg-entries bit of the [PM-Store-Capab] shall be set<br>[AND]<br>[Store-Capacity-Count] attribute shall be present<br>[AND]<br>[Store-Usage-Count] attribute shall be present<br>[AND]<br>[Clear-Timeout] attribute shall be present |                        |                    |                   |
+| <b>Applicability</b> | (C_AG_OXP_164 OR C_AG_OXP_165) AND C_AG_OXP_041 AND C_AG_OXP_188 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                              |                        |                    |                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Record the handle for the PM-Store objects.</li> <li>5. For each PM-Store objects: <ol style="list-style-type: none"> <li>i. 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.</li> <li>ii. The PHD issues a GET response with the PM-Store attributes it supports. <ol style="list-style-type: none"> <li>IF the PmStoreCapab attribute - Bit 5 (pmsc-peri-seg-entries) is set to TRUE THEN <ol style="list-style-type: none"> <li>a. Mandatory attribute PM-Store-Capab <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li> <li><input type="checkbox"/> attribute-type = PmStoreCapab</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = <ol style="list-style-type: none"> <li>• Bit 4 (pmsc-epi-seg-entries) must be set to FALSE</li> <li>• Bit 5 (pmsc-peri-seg-entries) must be set to TRUE</li> </ol> </li> </ol> </li> <li>b. Mandatory attribute Storage-Capacity-Count is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STORE_CAPAC_CNT</li> <li><input type="checkbox"/> attribute-type = INT-U32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = See relation with next attribute</li> </ol> </li> <li>c. Mandatory attribute Storage-Usage-Count is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STORE_USAGE_CNT</li> <li><input type="checkbox"/> attribute-type = INT-U32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = always <math>\leq</math> than Storage-Cpacity-Count</li> </ol> </li> <li>d. Mandatory attribute Clear-Timeout is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_CLEAR_TIMEOUT</li> <li><input type="checkbox"/> attribute-type = RelativeTime</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ol> </li> </ol> </li> <li>ELSE skip the PM-Store object and check the next one</li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+  
+
+|                 |                                                                                        |
+|-----------------|----------------------------------------------------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/ECG/BV-015                                                            |
+| <b>TP label</b> | PM-Store Object for Basic ECG specialization Extended Configuration. Episodic PM-Store |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                     |                     |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------|---------------------|
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-10406] |                     |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | AperPMStoreAtt4; M     | AperPMStoreAtt5; M  | AperPMStoreAtt8; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | AperPMStoreAtt9; M     | AperPMStoreAtt12; R | AperPMStoreAtt14; M |
+| <b>Test purpose</b>      | Check that:<br>The pmsc-epi-seg-entries bit of the [PM-Store-Capab] attribute shall be set<br>[AND]<br>The pmsc-peri-seg-entries bit of the [PM-Store-Capab] shall not be set<br>[AND]<br>[Store-Capacity-Count] attribute shall be present<br>[AND]<br>[Store-Usage-Count] attribute shall be present<br>[AND]<br>[Sample-Period] attribute is not recommended<br>[AND]<br>[Clear-Timeout] attribute shall be present                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                     |                     |
+| <b>Applicability</b>     | (C_AG_OXP_164 OR C_AG_OXP_165) AND C_AG_OXP_041 AND C_AG_OXP_187 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                     |                     |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                     |                     |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                     |                     |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Record the handle for the PM-Store objects.</li> <li>5. For each PM-Store objects: <ol style="list-style-type: none"> <li>i. 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.</li> <li>ii. The PHD issues a GET response with the PM-Store attributes it supports<br/> IF PmStoreCapab attribute - Bit 4 (pmsc-epi-seg-entries) is set to TRUE THEN <ol style="list-style-type: none"> <li>a. Mandatory attribute PM-Store-Capab <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li> <li><input type="checkbox"/> attribute-type = PmStoreCapab</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>• Bit 4 (pmsc-epi-seg-entries) must be set to TRUE</li> <li>• Bit 5 (pmsc-peri-seg-entries) must be set to FALSE</li> </ul> </li> </ul> </li> <li>b. Mandatory attribute Storage-Capacity-Count is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STORE_CAPAC_CNT</li> <li><input type="checkbox"/> attribute-type = INT-U32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = See relation with next attribute</li> </ul> </li> <li>c. Mandatory attribute Storage-Usage-Count is present</li> </ol> </li> </ol> </li> </ol> |                        |                     |                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STORE_USAGE_CNT</li> <li><input type="checkbox"/> attribute-type = INT-U32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = always <math>\leq</math> than Storage-Cpacity-Count</li> </ul> <p>d. Not recommended attribute Sample-Period is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_SAMP</li> <li><input type="checkbox"/> attribute-type = RelativeTime</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> <p>e. Mandatory attribute Clear-Timeout is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_CLEAR_TIMEOUT</li> <li><input type="checkbox"/> attribute-type = RelativeTime</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> <p>ELSE skip the PM-Store object and check the next one</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ECG/BV-016                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |  |
+| <b>TP label</b>          | Periodic PM-Store for Basic ECG specialization/Simple ECG profile                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-10406] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | ECG_PersStoreM1; M     |  |
+| <b>Test purpose</b>      | Check that:<br>A PHD that supports PM-store and that has a type value set to<br>DEV_SUB_SPEC_PROFILE_ECG shall implement the periodic PM-store object                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |  |
+| <b>Applicability</b>     | C_AG_OXP_165 AND C_AG_OXP_041 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |  |
+| <b>Other PICS</b>        | C_AG_OXP_187, C_AG_OXP_188                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Check PICS C_AG_OXP_187 and C_AG_OXP_188 values.</li> <li>2. The simulated PHG receives an association request from the PHD under test.</li> <li>3. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>4. 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.</li> <li>5. Record the handle for the PM-Store objects.</li> <li>6. For all PM-Store objects <ol style="list-style-type: none"> <li>i. 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.</li> <li>ii. The PHD issues a GET response with the PM-Store attributes it supports: <ol style="list-style-type: none"> <li>a. Mandatory attribute PM-Store-Capab <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = PmStoreCapab</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>• Bit 4 (pmsc-epi-seg-entries) must be set to FALSE</li> <li>• Bit 5 (pmsc-peri-seg-entries) must be set to TRUE</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 1, the PICS C_AG_OXP_187 is set to FALSE and the PICS C_AG_OXP_188 is set to TRUE.</li> <li>• In step 6, checked values of PM-Stroe-Capab bits are as specified in the test procedure.</li> </ul>                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                    |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ECG/BV-017                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                    |
+| <b>TP label</b>          | Mandatory Clear-Segments (all-segments) method for Basic ECG specialization                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                    |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-10406] |                    |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | PMStoreObjMeth1; M     | ECG_PMStoreGen3; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>A Basic electrocardiograph (ECG) (1- to 3-lead ECG) PHD shall support the [Clear-Segments] method with [Confirmed] mode. The PHD shall support the [Clear-Segments] method by setting the pmsc-clear-segm-by-all-sup bit for the [PM-Store-Capab] attribute</p> <p>[AND]</p> <p>The data held in PM-store objects may be deleted by user actions via the PHG or user interface on the device, and the capacity is limited only by the PHD's data storage capabilities.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                    |
+| <b>Applicability</b>     | (C_AG_OXP_164 OR C_AG_OXP_165) AND C_AG_OXP_041 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                    |
+| <b>Other PICS</b>        | C_AG_OXP_071                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                    |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state and the PHD has at least one PM-Segment with data stored.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                    |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Check the PICS C_AG_OXP_071 value</li> <li>2. Make sure the PHD under test is not taking measurements which are stored in PM-Segments.</li> <li>3. 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.</li> <li>4. The PHD under test issues a GET response with the PM-Store attributes. Check the values of the PM-Store-Capab attribute. <ol style="list-style-type: none"> <li>a. PM-Store-Capab: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li> <li><input type="checkbox"/> attribute-type = PmStoreCapab</li> <li><input type="checkbox"/> attribute-value = At least bit pmsc-clear-segm-all-sup(10) is set to TRUE (this bit indicates that PM-Segments in the SegmSelection data type can be cleared by segment selection –all segments)</li> </ul> </li> </ol> </li> <li>5. The simulated PHG sends a Clear-Segment: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> </ul> </li> </ol> </li> </ol> |                        |                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> <li><input type="checkbox"/> SegmSelection = all-segments</li> </ul> <p>6. If the PHD does not protect all segments, the PHD under test operation response will be:</p> <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Response   Confirmed Action</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> <li><input type="checkbox"/> Check the invoke-id of the response is mirrored from the request.</li> </ul> </li> </ol> <p>7. If the PHD does protect all segments, the PHD under test operation response will be:</p> <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Roer</li> <li><input type="checkbox"/> ErrorResult = no-allowed-by-object (24) and return code shall be MDC_RET_CODE_UNKNOWN.</li> <li><input type="checkbox"/> Check the invoke-id of the response is mirrored from the request</li> </ul> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 1, the PICS C_AG_OXP_071 is set to TRUE.</li> <li>• In step 6, the PHD must send a confirmation if the PHD does not protect any segments, otherwise the PHD shall send a roer message (step 7).</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |                  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ECG/BV-018                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                  |
+| <b>TP label</b>          | PM-Segment Start/Stop Time attributes (Absolute or Base Offset Time) for Basic ECG specialization                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-10406] |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | PerPMSegObj18; M       | PerPMSegObj19; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | AperPMSegObj17; M      | PerPMSegObj20; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>For each implemented periodic session PM-segment object, a PHD shall either implement the [Segment-Start-Abs-Time] attribute and the [Segment-End-Abs-Time] attribute or it shall implement the [Segment-Start-BO-Time] attribute and the [Segment-End-BO-Time] attribute.</p> <p>[AND]</p> <p>If [Segment-Start-Abs-Time] and [Segment-End-Abs-Time] are used, then absolute time stamps shall be used in the entries of the PM-segment.</p> <p>[AND]</p> <p>If [Segment-Start-BO-Time] and [Segment-End-BO-Time] are used, then base-offset time stamps shall be used in the entries of the PM-segment.</p> |                        |                  |
+| <b>Applicability</b>     | (C_AG_OXP_164 OR C_AG_OXP_165) AND C_AG_OXP_041 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                  |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                  |
+| <b>Test procedure</b>    | 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. The PHD issues a "rors-cnip-confirmed-action" response with the PM-Segment attributes it supports:
+
+IF C\_AG\_OXP\_009 = TRUE (PHD supports Absolute Time) THEN
+
+- a. Conditional attribute Segment-Start-Abs-Time shall be present
+
+- attribute-id = MDC\_ATTR\_TIME\_START\_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
+
+- b. Conditional attribute Segment-End-Abs-Time shall be present
+
+- 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. Conditional attribute Segment-Start-BO-Time shall not be present
+
+- attribute-id = MDC\_ATTR\_TIME\_START\_SEG\_BO
+- attribute-type = BaseOffsetTime
+- attribute-value.length = 8 bytes
+- attribute-value = <Not relevant in this test>
+
+- d. Conditional attribute Segment-End-BO-Time shall not be present
+
+- attribute-id = MDC\_ATTR\_TIME\_START\_SEG\_BO
+- attribute-type = BaseOffsetTime
+- attribute-value.length = 8 bytes
+- attribute-value = <Not relevant in this test>
+
+- e. Mandatory attribute PM-Segment-Entry-Map shall be present
+
+- attribute-id = MDC\_ATTR\_PM\_SEG\_MAP
+- attribute-type = PmSegmentEntryMap
+- attribute-value = SEQUENCE
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>▪ segm-entry-header = seg-elem-hdr-absolute-time(0)</li> </ul> <p>AND/OR</p> <ul style="list-style-type: none"> <li>▪ segm-entry-elem-list = The attr-val-map of all elements of this sequence includes MDC_ATTR_TIME_STAMP_ABS attribute</li> </ul> <p>IF C_AG_OXP_014 = TRUE (the PHD supports Base Offset Time) THEN</p> <ol style="list-style-type: none"> <li>a. Conditional attribute Segment-Start-Abs-Time shall not be present           <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_START_SEG</li> <li><input type="checkbox"/> attribute-type = AbsoluteTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> </li> <li>b. Conditional attribute Segment-End-Abs-Time shall not be present           <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_END_SEG</li> <li><input type="checkbox"/> attribute-type = AbsoluteTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> </li> <li>c. Conditional attribute Segment-Start-BO-Time shall be present           <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_START_SEG_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> </li> <li>d. Conditional attribute Segment-End-BO-Time shall be present           <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_START_SEG_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> </li> <li>e. Mandatory attribute PM-Segment-Entry-Map shall be present           <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_SEG_MAP</li> <li><input type="checkbox"/> attribute-type = PmSegmentEntryMap</li> <li><input type="checkbox"/> attribute-value = SEQUENCE               <ul style="list-style-type: none"> <li>▪ segm-entry-header = seg-elem-hdr-bo-time(3)</li> </ul> <p>AND/OR</p> <ul style="list-style-type: none"> <li>▪ segm-entry-elem-list = The attr-val-map of all elements of this sequence includes the MDC_ATTR_TIME_STAMP_BO attribute</li> </ul> </li> </ul> </li> </ol> <p>3. Repeat step 1 and 2 for every PM-Store.</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|                 |                                                                                   |                        |
+|-----------------|-----------------------------------------------------------------------------------|------------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/ECG/BV-019                                                       |                        |
+| <b>TP label</b> | Segment-entry-header for Basic ECG specialization with aperiodic PM-Store objects |                        |
+| <b>Coverage</b> | <b>Spec</b>                                                                       | [ISO/IEEE 11073-10406] |
+|                 | <b>Testable</b>                                                                   | AperPMSegObj18; M      |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |  |  |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|
+|                           | <b>items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |  |  |
+| <b>Test purpose</b>       | Check that:<br>For each entry in an implemented aperiodic PM-segment object, a PHD shall include one of the time formats in the segm-entry-header.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |  |  |
+| <b>Applicability</b>      | C_AG_OXP_164 AND C_AG_OXP_041 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |  |  |
+| <b>Other PICS</b>         | C_AG_OXP_009, C_AG_OXP_014                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |  |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. For all PM-Store objects: <ol style="list-style-type: none"> <li>i. 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.</li> <li>ii. The PHD issues a GET response with the PM-Store attributes it supports <ol style="list-style-type: none"> <li>a. Mandatory attribute PM-Store-Capab <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_CAPAB</li> <li><input type="checkbox"/> attribute-type = PmStoreCapab</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>• Check Bit 4 (pmsc-epi-seg-entries) value</li> </ul> </li> </ol> </li> </ol> </li> </ol> </li> <li>2. For all PM-Store objects which its PM-Store-Capab Attribute – Bit4 (pmsc-epi-seg-entries) is set to TRUE, the simulated PHG sends 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.</li> <li>3. The PHD issues a “rors-cmip-confirmed-action” response with the PM-Segment attributes it supports: <p>IF C_AG_OXP_009 = TRUE (PHD supports Absolute Time) THEN</p> <ol style="list-style-type: none"> <li>a. Mandatory attribute PM-Segment-Entry-Map shall be present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_SEG_MAP</li> <li><input type="checkbox"/> attribute-type = PmSegmentEntryMap</li> <li><input type="checkbox"/> attribute-value = SEQUENCE <ul style="list-style-type: none"> <li>▪ segm-entry-header = seg-elem-hdr-absolute-time(0)</li> <li>▪ segm-entry-elem-list = &lt;Not relevant for this test&gt;</li> </ul> </li> </ol> </li> </ol> <p>IF C_AG_OXP_014 = TRUE (PHD supports Base Offset Time) THEN</p> <ol style="list-style-type: none"> <li>a. Mandatory attribute PM-Segment-Entry-Map shall be present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_SEG_MAP</li> <li><input type="checkbox"/> attribute-type = PmSegmentEntryMap</li> <li><input type="checkbox"/> attribute-value = SEQUENCE <ul style="list-style-type: none"> <li>▪ segm-entry-header = seg-elem-hdr-bo-time(3)</li> <li>▪ segm-entry-elem-list = &lt;Not relevant for this test&gt;</li> </ul> </li> </ol> </li> </ol> </li> <li>4. Repeat step 2 and 3 for every PM-Store.</li> </ol> |  |  |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |  |  |
+
+|                 |                                                                                       |
+|-----------------|---------------------------------------------------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/ECG/BV-020                                                           |
+| <b>TP label</b> | EpiCfgScanner Object for Basic ECG specialization. Mandatory attribute Min-Reporting- |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |  |  |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--|
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Interval               |  |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-10406] |  |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | EpiScanObjAttr8; M     |  |  |
+| <b>Test purpose</b>       | Check that:<br>For [Extended-Configuration], the [Min-Reporting-Interval] attribute shall be present.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |  |  |
+| <b>Applicability</b>      | (C_AG_OXP_164 OR C_AG_OXP_165) AND C_AG_OXP_047 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |  |  |
+| <b>Other PICS</b>         | C_AG_OXP_144, C_AG_OXP_180                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |  |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |  |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Check the PICS C_AG_OXP_144 value.</li> <li>2. The simulated PHG receives an association request from the PHD under test.</li> <li>3. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>4. 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.</li> <li>5. The Configurable Episodic Scanner object (ConfigReport → ConfigObject → AttributeList) must include the following attribute: <ol style="list-style-type: none"> <li>a. Mandatory attribute Min-Reporting-Interval shall be present: <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SCAN_REP_PD_MIN</li> <li><input type="checkbox"/> attribute-type = RelativeTime</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> </li> </ol> </li> </ol> |                        |  |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 1, the PICS C_AG_OXP_144 is set to TRUE.</li> <li>• In step 5, all Episodic Scanners included in ConfigReport must include the attribute Min-Reporting-Interval.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |  |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |  |  |
+
+|                     |                                                                                                                                                                                                                                                                                |                                                              |             |
+|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------|-------------|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/ECG/BV-021                                                                                                                                                                                                                                                    |                                                              |             |
+| <b>TP label</b>     | Operating State. PHG to PHD Maximum APDU Size                                                                                                                                                                                                                                  |                                                              |             |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-20601-2015A] and [ISO/IEE 11073-20601-2016C] |             |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                          | CommonCharac 3; M                                            |             |
+|                     | <b>Spec</b>                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-10406]                                       |             |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                          | CommChar1;M                                                  | CommChar2;M |
+| <b>Test purpose</b> | Check that:<br>The total size of the response do not exceed of the maximum APDU size established by the specialization<br>[AND]<br>A basic ECG (1- to 3-lead ECG) PHD implementing only this device specialization shall be capable of receiving any APDU up to a size of Nrx. |                                                              |             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | For this standard, Nrx shall be 256 octets.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Applicability</b>      | C_AG_OXP_000 AND (C_AG_OXP_164 OR C_AG_OXP_165)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Other PICS</b>         | C_AG_OXP_041, C_AG_OXP_100                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Initial condition</b>  | The simulated PHG and the PHD are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG issues a "Remote Operation Invoke   Get" command with: <ol style="list-style-type: none"> <li>a. Obj-handle set to 0 (to request for MDS object)</li> <li>b. attribute-id-list.count = 119</li> <li>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</li> </ol> </li> <li>2. Check the response of the PHD.</li> <li>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.</li> <li>4. Check the response of the PHD.</li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• 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. <ul style="list-style-type: none"> <li>○ 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): <ul style="list-style-type: none"> <li>▪ Pulse oximeter → 9216 octets</li> <li>▪ Weighing scales → 896 octets</li> <li>▪ Glucose meter → 5120 octets or 64512 octets if the PHD supports PM-Store</li> <li>▪ Blood pressure → 896 octets</li> <li>▪ Thermometer → 896 octets</li> <li>▪ Independent activity hub → 5120 octets</li> <li>▪ Cardiovascular → 64512 octets or 6624 octets if the PHD under test only supports Step Counter Profile</li> <li>▪ Strength → 64512 octets:</li> <li>▪ Adherence monitor → 1024 octets</li> <li>▪ Peak flow → 2030 octets</li> <li>▪ Body composition analyser → 7730 octets</li> <li>▪ Basic ECG/Simple ECG → 7168 octets or 64512 octets if PHD supports PM-Store</li> <li>▪ Basic ECG/Heart rate → 1280 octets or 64512 octets if the PHD supports PM-Store</li> <li>▪ International normalized ratio → 896 octets or 64512 if the PHD supports PM-Store</li> </ul> </li> <li>○ In the case where it responds with a roer, the reason must not be protocol-violation (23).</li> </ul> </li> <li>• In step 4, the PHD must respond with a rors-cmip-get message.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                   |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ECG/BV-022                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |                   |
+| <b>TP label</b>          | Association Basic ECG PHD                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                   |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-10406] |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | AgProcAsReq1; M        | AgProcAsReq2; M   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | AgProcAsReq4; M        | AgProcAsReq5; O   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | AgProcAsReq9; M        | AgProcAsReq10; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | AgProcAsReq12; M       | AgProcAsReq13; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | AgProcAsReq15; M       | ECG_MDSMethod7; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>During the association procedure, Body composition analyser PHD sends the correct association request to the simulated PHG</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                   |
+| <b>Applicability</b>     | (C_AG_OXP_164 OR C_AG_OXP_165) AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                   |
+| <b>Other PICS</b>        | C_AG_OXP_002, C_AG_OXP_017                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                   |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                   |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The PHD sends a message to associate with the simulated PHG, the expected fields sent by the PHD are: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = AarqApdu</li> <li><input type="checkbox"/> field-length =2 bytes</li> <li><input type="checkbox"/> field-value =0xE2 0x00.</li> </ul> </li> <li>b. assoc-version <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = AssociationVersion</li> <li><input type="checkbox"/> field-length =BITS-32</li> <li><input type="checkbox"/> field- value=0x80 0x00 0x00 0x00</li> </ul> </li> <li>c. data-proto-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = DataProtoId(INT-U16)</li> <li><input type="checkbox"/> field-length =2 bytes</li> <li><input type="checkbox"/> field- value=0x50 0x79 (20601)</li> </ul> </li> <li>d. protocol-version <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = Protocol Version</li> <li><input type="checkbox"/> field-length = 4 bytes</li> <li><input type="checkbox"/> field- value= At least bit protocol-version2(1) is set to 1 (0x40 0x00 0x00 0x00 OR 0xC0 0x00 0x00 0x00)</li> </ul> </li> <li>e. encoding rules <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = EncodingRules</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field- value= <ul style="list-style-type: none"> <li>▪ Bit 0 must be set (support MDER)</li> <li>▪ Bits 1 and 2 may be set</li> <li>▪ The rest of the bits must be 0</li> </ul> </li> </ul> </li> <li>f. nomenclature-version</li> </ol> </li> </ol> |                        |                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = NomenclatureVersion</li> <li><input type="checkbox"/> field-length = 4 bytes</li> <li><input type="checkbox"/> field- value=0x80 0x00 0x00 0x00</li> <li><input type="checkbox"/> This value indicates version1 is supported (nom-version1(0) is set).</li> </ul> <p>g. functional-units</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = FunctionalUnits</li> <li><input type="checkbox"/> field-length = 4 bytes</li> <li><input type="checkbox"/> field-value = <ul style="list-style-type: none"> <li>▪ Bit 0 must not be set, only bit 1 or 2 may be set to 1.</li> </ul> </li> </ul> <p>h. System type</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = SystemType</li> <li><input type="checkbox"/> field-length = 4 bytes</li> <li><input type="checkbox"/> field- value = 0x00 0x80 0x00 0x00 (sys-type-agent)</li> </ul> <p>i. System-Id</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = OCTET STRING</li> <li><input type="checkbox"/> field-length = 8 bytes</li> <li><input type="checkbox"/> field- value = 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX (octet string length = 8   EUI-64 manufacturer and device )</li> <li><input type="checkbox"/> This value will be the System Id attribute of an MDS object and the received value will be compared with the value defined in PIXIT I_AG_OXP_001 and I_AG_OXP_002.</li> </ul> <p>j. dev-config-id</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = ConfigId(INT-U16)</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field- value = <ul style="list-style-type: none"> <li>▪ &lt;0x07D0&gt; for Basic ECG/Heart Rate profile standard configuration</li> <li>▪ &lt;between 0x40 0x00 and 0x7F 0xFF &gt; for extended configuration.</li> </ul> </li> </ul> <p>k. data-req-mode-flags (DataReqModeCapab)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = DataReqModeFlags</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> If PHD supports only Basic ECG specialization → Bit 15 is set (data-req-supp-init-agent(15))</li> </ul> <p>l. data-req-init-agent-count (DataReqModeCapab)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = INT-U8</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field.value = 0x01</li> </ul> <p>m. data-req-init-manager-count (DataReqModeCapab)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = INT-U8</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field.value = 0x00</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked attributes have proper values.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/ECG/BV-023                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |  |
+| <b>TP label</b>           | Set Time (Absolute Time) Basic ECG PHD                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-10406] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | ECG_MDSMethod2; M      |  |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>If the PHD supports the [Absolute-Time-Stamp] attribute, the Set-Time method shall be implemented.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |  |
+| <b>Applicability</b>      | (C_AG_OXP_164 OR C_AG_OXP_165) AND C_AG_OXP_000 AND C_AG_OXP_009                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG sends a SET action: <ul style="list-style-type: none"> <li><input type="checkbox"/> CHOICE = SetTimeInvoke</li> <li><input type="checkbox"/> action-type = MDC_ACT_SET_TIME</li> <li><input type="checkbox"/> the action-info-args are SetTimeInvoke <ul style="list-style-type: none"> <li>▪ date-time = &lt;century, year ≤ 99 month ≤ 12 day ≤ 31 hour ≤ 24 minute ≤ 60 second ≤ 60 sec-fractions ≤ 100&gt;</li> <li>▪ accuracy = 0</li> </ul> </li> </ul> </li> <li>2. The PHD under test response shall be a rors-cmip-confirmed-action: <ul style="list-style-type: none"> <li><input type="checkbox"/> action-type = MDC_ACT_SET_TIME</li> <li><input type="checkbox"/> action-info-args shall be empty.</li> </ul> </li> </ol> |                        |  |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                |                        |  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ECG/BV-024                                                                                                                                                                                                                                                                                                                    |                        |  |
+| <b>TP label</b>          | Set Time (Base Offset Time) Basic ECG PHD                                                                                                                                                                                                                                                                                                      |                        |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-10406] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                          | ECG_MDSMethod4; M      |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If the PHD supports the [Base-Offset-Time-Stamp] attribute, the Set-Base-Offset-Time method shall be implemented</p>                                                                                                                                                                                                     |                        |  |
+| <b>Applicability</b>     | (C_AG_OXP_164 OR C_AG_OXP_165) AND C_AG_OXP_000 AND C_AG_OXP_014                                                                                                                                                                                                                                                                               |                        |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                |                        |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                           |                        |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG sends a SET action: <ul style="list-style-type: none"> <li><input type="checkbox"/> CHOICE = SetBOTimeInvoke</li> <li><input type="checkbox"/> action-type = MDC_ACT_SET_BO_TIME</li> <li><input type="checkbox"/> the action-info-args are SetBOTimeInvoke</li> </ul> </li> </ol> |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>▪ date-time = bo-seconds = 0x00 0x00 0x00 0x00, bo-fractions = 0x00 0x00, bo-time-offset = 0x3C</li> </ul> <p>2. The PHD under test response shall be a rors-cmip-confirmed-action:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> action-type = MDC_ACT_SET_BO_TIME</li> <li><input type="checkbox"/> action-info-args shall be empty.</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+## 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.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-PHG PICS & PIXIT] Personal Health Gateway DG2016 PICS and PIXIT excel sheet v1.9.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-TCRL] Test Case Reference List\_DG2016\_v1.11  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-TI] Continua DG2016 PHD Testable items excel sheet v1.8  
+<http://handle.itu.int/11.1002/2000/12067>
+
+
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.14-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.845.14-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bd7c24e83d75a6b1baa7fb4210f76345166390c9
--- /dev/null
+++ b/marked/H/T-REC-H.845.14-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5866ab521163bd4f911ae6e27d0a1cf1f491c665e9b87b7d7076098a143f4bff
+size 3944
diff --git a/marked/H/T-REC-H.845.14-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.845.14-201704-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..748e3645f5d7b507f5a903439e9deedb949c8144
--- /dev/null
+++ b/marked/H/T-REC-H.845.14-201704-I_PDF-E/raw.md
@@ -0,0 +1,1378 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.845.14**
+
+(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 5N: International normalized ratio**
+
+Recommendation ITU-T H.845.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        |
+| 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        |
+| <b>Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN)</b> | <b>H.820–H.859</b> |
+| 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.14
+
+## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5N: International normalized ratio
+
+## Summary
+
+Recommendation ITU-T H.845.14 provides a test suite structure (TSS) and the test purposes (TP) for devices measuring the international normalized ratio 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.14 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5N: Device Specializations. Personal Health Device (International Normalized Ratio, INR) (Version 1.3, 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.14 | 2015-01-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/12274">11.1002/1000/12274</a> |
+| 2.0     | ITU-T H.845.14 | 2016-07-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12951">11.1002/1000/12951</a> |
+| 3.0     | ITU-T H.845.14 | 2017-04-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/13231">11.1002/1000/13231</a> |
+
+## Keywords
+
+Conformance testing, Continua Design Guidelines, e-health, IEEE 11073 device specialization, international normalized ratio, 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 <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                               | 3    |
+| 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.14 – International normalized ratio (INR) ..... | 9    |
+| Bibliography.....                                                | 50   |
+
+**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 5N: Device Specializations. Personal Health Device (International Normalized Ratio -INR-) (Version 1.3, 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     | 2014-01-24 | Initial release for Test Tool DG2013 based on the requirements in [b-ITU-T H.810 (2013)]/[b-CDG 2013].                                                                                                                                                               |
+| 1.1     | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_PLT_PART_5N_v1.0.doc" as a baseline and adds new features included in Documentation Enhancements: <ul style="list-style-type: none"><li>• "Other PICS" row added</li></ul> |
+| 1.2     | 2015-07-01 | Initial release for Test Tool DG2015. It uses "TSS&TP_DG2013_PLT_PART_5N_v1.1.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2015)]/[b-CDG 2015]                                                                                               |
+| 1.3     | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2015_PLT_PART_5N_v1.2.doc" as a baseline and adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016]                                                                                                 |
+
+## Recommendation ITU-T H.845.14
+
+## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5N: International normalized ratio
+
+## 1 Scope
+
+The scope of this Recommendation<sup>1</sup> 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 5N.
+
+- 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
+
+---
+
+<sup>1</sup> 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-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-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.  
+<https://www.iso.org/standard/54331.html> with  
+<https://www.iso.org/standard/63972.html>
+- [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.  
+<https://www.iso.org/standard/66717.html> with  
+<https://www.iso.org/standard/71886.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                                   |
+| 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.14 (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 <http://handle.itu.int/11.1002/2000/12067>.
+
+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>/<DUT>/<GR>/<SGR>/<XX> – <NNN>). It is specified according to the naming convention defined below:
+  - Each test purpose identifier is introduced by the prefix "TP".
+  - <TT>: 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)
+  - <DUT>: This is the device under test:
+    - PHD: Personal Health Device
+    - PHG: Personal Health Gateway
+  - <GR>: This identifies a group of test cases.
+  - <SGR>: This identifies a subgroup of test cases.
+  - <XX>: This identifies the type of testing:
+    - BV: Valid behaviour test
+    - BI: Invalid behaviour test
+  - <NNN>: 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 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.14 – International normalized ratio (INR)
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                         |                 |                 |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------|-----------------|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/INR/BV-000_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                         |                 |                 |
+| <b>TP label</b>           | Get MDS Object for INR monitor specialization: Mandatory, Conditional and Optional Attributes.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                         |                 |                 |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-10418C] |                 |                 |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | MDSINR Atr 1; M         | MDSINR Atr 2; M | MDSINR Atr 4; M |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | MDSINR Atr 5; M         |                 |                 |
+| <b>Test purpose</b>       | Check that:<br>The MDS Object contains the attributes specified for a INR Monitor PHD                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                         |                 |                 |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_163                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                         |                 |                 |
+| <b>Other PICS</b>         | C_AG_OXP_181, C_AG_INR_001, C_AG_INR_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                         |                 |                 |
+| <b>Initial condition</b>  | The simulated Personal Health Gateway (PHG) and the Personal Health Device (PHD) under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                         |                 |                 |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG issues a "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.</li> <li>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.<br/>MDS Attributes: <ol style="list-style-type: none"> <li>a. Attribute System-Type must not be present.</li> <li>b. Mandatory attribute System-Type-Spec_List <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SYS_TYPE_SPEC_LIST</li> <li><input type="checkbox"/> attribute-type = TypeVerList</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes for each configuration supported</li> <li><input type="checkbox"/> attribute-value = {MDC_DEV_SPEC_PROFILE_COAG, 1} must be found in the list</li> </ul> </li> <li>c. Mandatory attribute System-model <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_MODEL (0x09 0x28)</li> <li><input type="checkbox"/> attribute-type = SystemModel</li> <li><input type="checkbox"/> attribute-value.length = &lt;Variable&gt;</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>• Manufacturer = Check against PIXIT I_AG_OXP_003</li> <li>• Model = Check against PIXIT I_AG_OXP_004</li> </ul> </li> </ul> </li> <li>d. Mandatory attribute Dev-Configuration-Id <ul style="list-style-type: none"> <li><input type="checkbox"/> IF C_AG_INR_001 THEN attribute-value = 0x0708 (1800)</li> <li><input type="checkbox"/> IF C_AG_INR_002 THEN attribute-value = 0x0709 (1801)</li> <li><input type="checkbox"/> IF C_AG_OXP_181 THEN attribute-value = &lt; between 0x4000 and 0x7FFF &gt;</li> </ul> </li> </ol> </li> </ol> |                         |                 |                 |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                         |                 |                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                         |                 |                 |
+
+|                 |                                                                  |
+|-----------------|------------------------------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/INR/BV-000_B                                    |
+| <b>TP label</b> | MDS Configuration objects events for INR monitor specialization. |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                         |  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--|
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-10418C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MDSEvents 1; M          |  |
+| <b>Test purpose</b>      | Check that:<br><br>INR monitor PHD sends the MDS-Configuration-Event using a Confirmed event report and it includes the event-info ConfigReport                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                         |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_163                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                         |  |
+| <b>Other PICS</b>        | C_AG_OXP_010, C_AG_OXP_181, C_AG_INR_001, C_AG_INR_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                         |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                         |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = PrstApdu</li> <li><input type="checkbox"/> field-length =2 bytes</li> <li><input type="checkbox"/> field-value =0xE7 0x00</li> </ol> </li> <li>b. invoke-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = InvokeIDType</li> <li><input type="checkbox"/> field-length =INT-U16</li> <li><input type="checkbox"/> field- value =&lt;Not relevant for this test&gt;</li> </ol> </li> <li>c. message <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = roiv-cmip-confirmed-event-report</li> <li><input type="checkbox"/> field-length =two bytes</li> <li><input type="checkbox"/> field- value =0x01 0x01 (EventReportArgumentSimple)</li> </ol> </li> <li>d. obj-handle (EventReportArgumentSimple) <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = HANDLE</li> <li><input type="checkbox"/> field-length =INT-U16</li> </ol> </li> <li>e. event-time (EventReportArgumentSimple) <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = Relative Time</li> <li><input type="checkbox"/> field-length =INT-U32</li> <li><input type="checkbox"/> field-value = <ul style="list-style-type: none"> <li>• IF NOT C_AG_OXP_010 THEN value = 0xFF 0xFF 0xFF 0xFF</li> </ul> </li> </ol> </li> <li>f. event-type (EventReportArgumentSimple) <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = OID-Type</li> <li><input type="checkbox"/> field-length =INT-U16</li> <li><input type="checkbox"/> field- value=0x0D 0x1C (MDC_NOTI_CONFIG)</li> </ol> </li> <li>g. config-report-id (ConfigReport) <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = ConfigId</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field value = &lt;It matches the tested configuration&gt; <ul style="list-style-type: none"> <li>• IF C_AG_INR_001 THEN attribute-value = 0x 0708 (1800)</li> <li>• IF C_AG_INR_002 THEN attribute-value = 0x 0709 (1801)</li> <li>• IF C_AG_OXP_181 THEN &lt;between 0x40 0x00 and 0x7F 0xFF &gt; for extended configuration.</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                         |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>h. obj-class ( ConfigReport → ConfigObjectList (ConfigObject))</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = OID-Type</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field- value = At least one MDC_MOC_VMO_METRIC_NU</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                      |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |                 |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/INR/BV-000_C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                         |                 |
+| <b>TP label</b>           | MDS objects events for INR monitor specialization.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                         |                 |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-10418C] |                 |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MDSEvents 3; M          | MDSEvents 4; M  |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MDSEvents 6; M          | MDSEvents 7; M  |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MDSEvents 9; M          | MDSEvents 10; M |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         | ObjAccServ 1; M |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>Agent-initiated mode is supported for measurement data transmission and all types of event reports are used in confirmed mode</p> <p>[AND]</p> <p>The PHD sends the MDS-Dynamic-Data-Update-Fixed using a confirmed event report and it includes the event-info ScanReportInfoFixed</p> <p>[OR]</p> <p>The PHD sends the MDS-Dynamic-Data-Update-Var using a confirmed event report and it includes the event-info ScanReportInfoVar</p> <p>[OR]</p> <p>The PHD sends the MDS-Dynamic-Data-Update-MP-Fixed using a confirmed event report and it includes the event-info ScanReportInfoMPFixed</p> <p>[OR]</p> <p>The PHD sends the MDS-Dynamic-Data-Update-MP-Var using a confirmed event report and it includes the event-info ScanReportInfoMPVar</p> |                         |                 |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_163 AND (C_AG_OXP_182 OR C_AG_OXP_183 OR C_AG_OXP_184 OR C_AG_OXP_189)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                         |                 |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |                 |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                         |                 |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Take measurements for every supported object in the PHD under test.</li> <li>2. Wait to receive every event report and check: <ul style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = Event Report</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field- value=0x01 0x01 (EventReportArgumentSimple, confirmed)</li> </ul> <p>This field identifies the type of message sent by the PHD, for the confirmed event configuration, roiv-cmip-confirmed-event-report.</p> </li> </ul> </li> </ol>                                                                                                                  |                         |                 |
+| <b>Pass/Fail criteria</b> | <p>Check that every received report is one of the following confirmed Data APDU</p> <ul style="list-style-type: none"> <li>• MDC_NOTI_SCAN_REPORT_FIXED</li> <li>• MDC_NOTI_SCAN_REPORT_MP_FIXED</li> <li>• MDC_NOTI_SCAN_REPORT_VAR</li> <li>• MDC_NOTI_SCAN_REPORT_MP_VAR</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                         |                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                         |              |                |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------------|----------------|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/INR/BV-001                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                         |              |                |
+| <b>TP label</b>           | Objects for INR monitor specialization – Standard Configuration (1800 or 1801)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                         |              |                |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-10418C] |              |                |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | INR 1; M                | CtrlCal 2; M | ProthTime 7; M |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | QuickVal 2; M           | ISI 2; M     | Target 2; M    |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | CurrentMed 2; M         |              |                |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>Only the INR Numeric object with Type MDC_RATIO_INR_COAG is supported by an INR monitor PHD for Standard Configuration 1800 (0x0708).</p> <p>[AND]</p> <p>INR Numeric object with Type MDC_RATIO_INR_COAG is supported by an INR PHD for Standard Configuration 1801 (0x0709).</p> <p>[AND]</p> <p>The Control Calibration Numeric object is supported by an INR monitor PHD for Standard Configuration 1801 (0x0709).</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                         |              |                |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_163 AND (NOT C_AG_OXP_181)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                         |              |                |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                         |              |                |
+| <b>Initial condition</b>  | The simulated PHG and the PHD are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                         |              |                |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"><li>The simulated PHG receives an association request from the PHD under test.</li><li>The simulated PHG responds with a result = accepted-unknown-config.</li><li>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.</li><li>Check that the field Dev-Config-Id is set to 0x0708 (1800) OR 0x0709 (1801), if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li><li>Once the PHD under test sends a standard configuration, check that:<br/>IF (Dev-Config-Id = 0x0708) THEN Attribute-List:<ol style="list-style-type: none"><li>attribute-value (ConfigReport → ConfigObjectList (ConfigObject) → Attribute List), this value depends on the attribute Type. The values to be checked are:<ul style="list-style-type: none"><li><input type="checkbox"/> INR Object is present → MDC_PART_SCADA (0x00 0x02), MDC_RATIO_INR_COAG (0x72 0x04)</li></ul></li></ol>IF (Dev-Config-Id = 0x0709) THEN Attribute-List:<ol style="list-style-type: none"><li>attribute-value (ConfigReport → ConfigObjectList (ConfigObject) → Attribute List), this value depends on the attribute Type. The values to be checked are:<ul style="list-style-type: none"><li><input type="checkbox"/> INR Object is present → MDC_PART_SCADA (0x00 0x02), MDC_RATIO_INR_COAG (0x72 0x04)</li><li><input type="checkbox"/> Control calibration Object is present → MDC_PART_SCADA (0x00 0x02), MDC_COAG_CONTROL (0x72 0x14)</li></ul></li></ol></li></ol> |                         |              |                |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure and no other object listed.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                         |              |                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                         |              |                |
+
+|                 |                                                                 |                         |                |                 |
+|-----------------|-----------------------------------------------------------------|-------------------------|----------------|-----------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/INR/BV-002                                     |                         |                |                 |
+| <b>TP label</b> | Objects for INR monitor specialization – Extended Configuration |                         |                |                 |
+| <b>Coverage</b> | <b>Spec</b>                                                     | [ISO/IEEE 11073-10418C] |                |                 |
+|                 | <b>Testable items</b>                                           | INR 1; M                | DevSenAn 3; R  | ProthTime 6; O  |
+|                 |                                                                 | CtrlCal 1; O            | ProthTime 6; O | QuickVal 1; O   |
+|                 |                                                                 | ISI 1; O                | Target 1; O    | CurrentMed 1; O |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                    |                |  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------------|--|
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | ContextTester 2; R | BatchCode 1; M |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The INR Numeric object is supported by an INR monitor PHD.</p> <p>[AND]</p> <p>Control Calibration, Prothrombin Time, Quick Value, International Sensitivity Index (ISI), INR Target Level, Current Medication Level, New Medication Level Numeric or Control Calibration objects can be implemented by the vendor.</p> <p>[AND]</p> <p>PHD should support Device and Sensor Status Annunciation object to transmit these occurrences.</p> <p>[AND]</p> <p>PHD should support Context Tester object to transmit these occurrences.</p> <p>[AND]</p> <p>PHD shall support Batch Code object.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                    |                |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                    |                |  |
+| <b>Other PICS</b>        | C_AG_INR_003, C_AG_INR_004, C_AG_INR_005, C_AG_INR_006, C_AG_INR_007, C_AG_INR_008, C_AG_INR_009, C_AG_INR_010, C_AG_INR_012, C_AG_INR_013,                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                    |                |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                    |                |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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.</li> <li>5. Once the PHD under test sends an extended configuration, check that:           <p>Attribute-List:</p> <ol style="list-style-type: none"> <li>a. attribute-value( ConfigReport → ConfigObjectList (ConfigObject)→Attribute List), this value depends on the attribute type. The values we have to check are:               <ul style="list-style-type: none"> <li><input type="checkbox"/> INR numeric Object is present → MDC_PART_SCADA (0x00 0x02), MDC_RATIO_INR_COAG (0x72 0x04)</li> <li><input type="checkbox"/> Any of these objects may be present:                   <ul style="list-style-type: none"> <li>• IF C_AG_INR_003 THEN Control Calibration numeric object is present → MDC_PART_SCADA (0x00 0x02), MDC_COAG_CONTROL (0x72 0x14)</li> <li>• IF C_AG_INR_004 THEN Prothrombin time numeric object is present → MDC_PART_SCADA (0x00 0x02), MDC_TIME_PD_COAG (0x72 0x08)</li> <li>• IF C_AG_INR_005 THEN Quick value numeric object is present → MDC_PART_SCADA (0x00 0x02), MDC_QUICK_VALUE_COAG (0x72 0x0C)</li> <li>• IF C_AG_INR_006 THEN ISI numeric object is present → MDC_PART_SCADA (0x00 0x02), MDC_ISI_COAG (0x72 0x10)</li> <li>• IF C_AG_INR_007 THEN INR Target level numeric object is present → MDC_PART_SCADA (0x00 0x02), MDC_TARGET_LEVEL_COAG (0x72 0x78)</li> <li>• IF C_AG_INR_008 THEN Current medication level numeric object is present → MDC_PART_SCADA (0x00 0x02), MDC_MED_CURRENT_COAG (0x72 0x7C)</li> <li>• IF C_AG_INR_009 THEN New medication level numeric object is present → MDC_PART_SCADA (0x00 0x02), MDC_MED_NEW_COAG (0x72 0x80)</li> <li>• IF C_AG_INR_010 THEN Device and sensor status enumeration object is present → MDC_PART_PHD_DM (0x00 0x80),</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                    |                |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>MDC_INR_METER_DEV_STATUS (0x72 0x75)</p> <ul style="list-style-type: none"> <li>IF C_AG_INR_012 THEN Context tester enumeration object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_CTXT_INR_TESTER (0x72 0x84)</li> <li>IF C_AG_INR_013 THEN Batch code enumeration object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_BATCHCODE_COAG (0x72 0x74)</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                     |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                         |              |              |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------------|--------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/INR/BV-003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                         |              |              |
+| <b>TP label</b>          | INR Numeric Object – Standard configuration (1800 or 1801)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                         |              |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-10418C] |              |              |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | NumObj 2; M             | NumObj 4; M  | NumObj 6; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | NumObj 8; M             | NumObj 10; R | NumObj 12; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | NumObj 14; R            | NumObj 16; R | NumObj 18; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | NumObj 20; M            | NumObj 22; M | NumObj 24; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | NumObj 26; O            | NumObj 28; O | NumObj 30; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | NumObj 32; R            | NumObj 34; C | NumObj 36; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | NumObj 38; R            | NumObj 40; C | NumObj 42; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | NumObj 44; R            | NumObj 46; C | NumObj 48; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | NumObj 50; C            | NumObj 52; R |              |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | INR 2; M                | INR 4; M     | INR 6; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | INR 8; M                | INR 10; M    | INR 12; C    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | INR 14; C               | INR 18; R    | INR 20; R    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | INR 22; C               | INR 24; C    | INR 26; R    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | INR 28; R               | INR 31; M    |              |
+| <b>Test purpose</b>      | Check that:<br>The INR Numeric object contains the attributes specified for Standard Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                         |              |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_163 AND (NOT C_AG_OXP_181)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |              |              |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                         |              |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                         |              |              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>Check that the field Dev-Config-Id is set to 0x0708 (1800) or Dev-Config-Id is set to 0x0709 (1801); if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>Once the PHD under test sends a standard configuration, check that the INR object attributes are: <ol style="list-style-type: none"> <li>Mandatory attribute Handle <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_HANDLE</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x01</li> </ul> </li> <li>Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> IF (Dev-Config-Id = 0x0708) OR (Dev-Config-Id = 0x0709):</li> </ul> </li> </ol> </li> </ol> |                         |              |              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• attribute-id = MDC_ATTR_ID_TYPE</li> <li>• attribute-type = TYPE</li> <li>• attribute-value = MDC_PART_SCADA (0x00 0x02),<br/>MDC_RATIO_INR_COAG (0x72 0x04).</li> </ul> <p>c. Mandatory attribute Metric-Spec-Small</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00</li> <ul style="list-style-type: none"> <li>• Bit 0 (mss-avail-intermittent(0)), must be set</li> <li>• Bit 1 (mss-avail-stored-data(1)), must be set</li> <li>• Bit 2 (mss-upd-aperiodic(2)), must be set</li> <li>• Bit 3 (mss-msmt-aperiodic(3)), must be set</li> <li>• Bit 9 (mss-acc-agent-initiated(9)), must be set</li> <li>• The other bits have to be 0.</li> </ul> </ul> <p>d. Mandatory attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_INR</li> </ul> <p>e. Mandatory attribute Attribute-Value-Map</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = AttrValMap (sequence of attribute-id(OID-Type) and attribute-length( INT-U16) )</li> <li><input type="checkbox"/> attribute-value.length=&lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value= MDC_ATTR_NU_VAL_OBS_BASIC<br/>MDC_ATTR_TIME_STAMP_BO</li> </ul> <p>f. No other attribute shall be present at configuration</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                     |                                             |                         |              |
+|---------------------|---------------------------------------------|-------------------------|--------------|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/INR/BV-004                 |                         |              |
+| <b>TP label</b>     | INR Numeric Object – Extended configuration |                         |              |
+| <b>Coverage</b>     | <b>Spec</b>                                 | [ISO/IEEE 11073-10418C] |              |
+|                     | <b>Testable items</b>                       | NumObj 3; M             | NumObj 5; R  |
+|                     |                                             | NumObj 9; R             | NumObj 11; R |
+|                     |                                             | NumObj 15; R            | NumObj 17; R |
+|                     |                                             | NumObj 23; R            | NumObj 31; R |
+|                     |                                             | NumObj 45; C            | NumObj 47; C |
+|                     |                                             | NumObj 51; R            |              |
+|                     |                                             | INR 5; M                | INR 7; M     |
+|                     |                                             | INR 9; M                | INR 11; C    |
+|                     |                                             | INR 19; R               | INR 25; C    |
+| <b>Test purpose</b> | Check that:                                 |                         |              |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | The International Normalized Ratio Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that the INR object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_SCADA (0x00 0x02)   MDC_RATIO_INR_COAG (0x72 0x04)</li> </ol> </li> <li>b. Not recommended Supplemental –Types Attribute <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes)</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 3 must be set (mss-msmt-aperiodic(3))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> </ol> </li> </ol> </li> <li>d. IF Not recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8))))</li> </ol> </li> <li>e. IF Not recommended attribute Measurement-Status is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> </ol> </li> <li>f. IF Not recommended attribute Metric-Id is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length= 2 bytes</li> </ol> </li> <li>g. IF Not recommended attribute Metric-Id-List is present</li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIST</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value.length= SEQUENCE OF OID-Type (INT-U16)</li> </ul> h. IF Not recommended attribute Metric-Id-Partition is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> i. Mandatory attribute Unit-Code <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_INR</li> </ul> j. IF Not recommended attribute Source-Handle-Reference is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> k. IF recommended attribute Base-Offset-Time-Stamp is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> l. IF Not recommended attribute Measure-Active-Period <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> m. IF recommended attribute Basic-Nu-Observed-Value <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> n. IF NOT Recommended attribute Accuracy is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+|                 |                                                                    |                         |              |              |
+|-----------------|--------------------------------------------------------------------|-------------------------|--------------|--------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/INR/BV-005                                        |                         |              |              |
+| <b>TP label</b> | Control Calibration Numeric Object – Standard configuration (1801) |                         |              |              |
+| <b>Coverage</b> | <b>Spec</b>                                                        | [ISO/IEEE 11073-10418C] |              |              |
+|                 | <b>Testable items</b>                                              | NumObj 2; M             | NumObj 4; M  | NumObj 6; R  |
+|                 |                                                                    | NumObj 8; M             | NumObj 10; R | NumObj 12; R |
+|                 |                                                                    | NumObj 14; R            | NumObj 16; R | NumObj 18; R |
+|                 |                                                                    | NumObj 20; M            | NumObj 22; M | NumObj 24; R |
+|                 |                                                                    | NumObj 26; O            | NumObj 28; O | NumObj 30; C |
+|                 |                                                                    | NumObj 32; R            | NumObj 34; C | NumObj 36; C |
+
+|                          |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |               |               |
+|--------------------------|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|
+|                          |  | NumObj 38; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 40; C  | NumObj 42; C  |
+|                          |  | NumObj 44; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 46; C  | NumObj 48; C  |
+|                          |  | NumObj 50; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 52; R  |               |
+|                          |  | CtrlCal 4; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | CtrlCal 6; M  | CtrlCal 7; M  |
+|                          |  | CtrlCal 9; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | CtrlCal 11; R | CtrlCal 13; R |
+| <b>Test purpose</b>      |  | Check that:<br>The Control Calibration Numeric object contains the attributes specified for Standard Configuration (1801).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |               |               |
+| <b>Applicability</b>     |  | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_INR_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |               |               |
+| <b>Other PICS</b>        |  | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |               |               |
+| <b>Initial condition</b> |  | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |               |               |
+| <b>Test procedure</b>    |  | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set to 0x0709 (1801); if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends a standard configuration, check that the Control Calibration object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_HANDLE</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x02</li> </ol> </li> <li>b. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> IF Dev-Config-Id = 0x0709: <ul style="list-style-type: none"> <li>• attribute-id = MDC_ATTR_ID_TYPE</li> <li>• attribute-type = TYPE</li> <li>• attribute-value = MDC_PART_SCADA (0x00 0x02), MDC_COAG_CONTROL (0x72 0x14)</li> </ul> </li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 0 (mss-avail-intermittent(0)), must be set</li> <li>• Bit 1 (mss-avail-stored-data(1)), must be set</li> <li>• Bit 2 (mss-upd-aperiodic(2)), must be set</li> <li>• Bit 3 (mss-msmt-aperiodic(3)), must be set</li> <li>• Bit 9 (mss-acc-agent-initiated(9)), must be set</li> <li>• The other bits have to be 0.</li> </ul> </li> </ol> </li> <li>d. Mandatory attribute Unit-Code <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_INR</li> </ol> </li> <li>e. Mandatory attribute Attribute-Value-Map</li> </ol> </li> </ol> |               |               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = AttrValMap (sequence of attribute-id(OID-Type) and attribute-length( INT-U16) )</li> <li><input type="checkbox"/> attribute-value.length=&lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value= MDC_ATTR_NU_VAL_OBS_BASIC<br/>MDC_ATTR_TIME_STAMP_BO</li> </ul> <p>f. IF recommended attribute Base-Offset-Time-Stamp is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> <p>g. IF recommended attribute Basic-Nu-Observed-Value</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> <p>h. No other attribute shall be present at configuration</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                                                                                             |                                                                                                              |  |  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|--|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/INR/BV-006                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                                                                                             |                                                                                                              |  |  |
+| <b>TP label</b>          | Control Calibration Numeric Object – Extended configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                                                                                             |                                                                                                              |  |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-10418C]                                                                                                     |                                                                                                              |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | NumObj 3; M<br>NumObj 9; R<br>NumObj 15; R<br>NumObj 23; R<br>NumObj 45; C<br>NumObj 51; R<br>CtrlCal 3; M<br>CtrlCal 10; R | NumObj 5; R<br>NumObj 11; R<br>NumObj 17; R<br>NumObj 31; R<br>NumObj 47; C<br>CtrlCal 5; M<br>CtrlCal 12; R |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | NumObj 7; M<br>NumObj 13; R<br>NumObj 19; M<br>NumObj 41; C<br>NumObj 49; C<br>CtrlCal 8; M                                 |                                                                                                              |  |  |
+| <b>Test purpose</b>      | Check that:<br>The Control Calibration Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                                                                                             |                                                                                                              |  |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_OXP_181 AND C_AG_INR_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                                                                                             |                                                                                                              |  |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                                                                                             |                                                                                                              |  |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                                                                                             |                                                                                                              |  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that the Control Calibration object attributes are:               <ol style="list-style-type: none"> <li>a. Mandatory attribute Type                   <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> </ul> </li> </ol> </li> </ol> |                                                                                                                             |                                                                                                              |  |  |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <ul style="list-style-type: none"> <li> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value = MDC_PART_SCADA (0x00 0x02)   MDC_COAG_CONTROL (0x72 0x14)</li> </ul> </li> <li>b. Not recommended Supplemental –Types Attribute <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes)</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 3 must be set (mss-msmt-aperiodic(3))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> </ul> </li> </ul> </li> <li>d. IF Not recommended attribute Metric-Structure-Small is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))</li> </ul> </li> <li>e. IF Not recommended attribute Measurement-Status is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> </ul> </li> <li>f. IF Not recommended attribute Metric-Id is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length= 2 bytes</li> </ul> </li> <li>g. IF Not recommended attribute Metric-Id-List is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIST</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value.length= SEQUENCE OF OID-Type (INT-U16)</li> </ul> </li> <li>h. IF Not recommended attribute Metric-Id-Partition is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>i. Mandatory attribute Unit-Code <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_INR</li> </ul> </li> <li>j. IF Not recommended attribute Source-Handle-Reference is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> </ul> </li> </ul> |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li>k. IF recommended attribute Base-Offset-Time-Stamp is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> </li> <li>l. IF Not recommended attribute Measure-Active-Period <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> <li>m. IF recommended attribute Basic-Nu-Observed-Value <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> </li> <li>n. IF NOT Recommended attribute Accuracy is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                         |                |                |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------|----------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/INR/BV-007                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |                |                |
+| <b>TP label</b>          | Prothrombin Time Numeric Object – Extended configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                         |                |                |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-10418C] |                |                |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | <b>Testable items</b>   |                |                |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 3; M             | NumObj 5; R    | NumObj 7; M    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 9; R             | NumObj 11; R   | NumObj 13; R   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 15; R            | NumObj 17; R   | NumObj 19; M   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 23; R            | NumObj 31; R   | NumObj 41; C   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 45; C            | NumObj 47; C   | NumObj 49; C   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 51; R            |                |                |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ProthTime 1; M          | ProthTime 2; M | ProthTime 3; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ProthTime 4; M          | ProthTime 5; M |                |
+| <b>Test purpose</b>      | Check that:<br>The Prothrombin Time Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                         |                |                |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_OXP_181 AND C_AG_INR_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                         |                |                |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                         |                |                |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                         |                |                |
+| <b>Test procedure</b>    | 1. The simulated PHG receives an association request from the PHD under test.<br>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.<br>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.<br>4. Once the PHD under test sends an extended configuration, check that the Prothrombin Time object attributes are: |                         |                |                |
+
+- a. Mandatory attribute Type
+  - attribute-id = MDC\_ATTR\_ID\_TYPE
+  - attribute-type = TYPE
+  - attribute-value = MDC\_PART\_SCADA (0x00 0x02) | MDC\_TIME\_PD\_COAG (0x72 0x08)
+- b. Not recommended Supplemental –Types Attribute
+  - attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+  - attribute-type = SupplementalTypeList
+  - attribute-value.length =<variable> (Sequence of TYPE (TYPE.length= 4 bytes
+- 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 3 must be set (mss-msmt-aperiodic(3))
+    - Bit 9 must be set (mss-acc-agent-initiated(9))
+- d. IF Not recommended attribute Metric-Structure-Small is present
+  - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+  - attribute-type = MetricStructureSmall
+  - attribute-value.length = <variable>(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8))))
+- e. IF Not recommended attribute Measurement-Status is present
+  - attribute-id = MDC\_ATTR\_MSMT\_STAT
+  - attribute-type = MeasurementStatus (BITS-16)
+  - attribute-value.length =2 bytes
+- 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
+- g. IF Not recommended attribute Metric-Id-List is present
+  - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+  - attribute-type = MetricIdList
+  - attribute-value.length= SEQUENCE OF OID-Type (INT-U16)
+- 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
+- i. 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\_SEC
+- j. IF Not recommended attribute Source-Handle-Reference is present
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> k. IF recommended attribute Base-Offset-Time-Stamp is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> l. IF Not recommended attribute Measure-Active-Period <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> m. IF recommended attribute Basic-Nu-Observed-Value <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> n. IF NOT Recommended attribute Accuracy is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |               |               |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/INR/BV-008                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                         |               |               |
+| <b>TP label</b>          | Quick Value Numeric Object – Extended configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                         |               |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-10418C] |               |               |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | NumObj 3; M             | NumObj 5; R   | NumObj 7; M   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | NumObj 9; R             | NumObj 11; R  | NumObj 13; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | NumObj 15; R            | NumObj 17; R  | NumObj 19; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | NumObj 23; R            | NumObj 31; R  | NumObj 41; C  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | NumObj 45; C            | NumObj 47; C  | NumObj 49; C  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | NumObj 51; R            |               |               |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | QuickVal 3; M           | QuickVal 4; M | QuickVal 5; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | QuickVal 6; R           | QuickVal 7; R |               |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |               |               |
+| <b>Test purpose</b>      | Check that:<br>The Quick Value Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                         |               |               |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_OXP_181 AND C_AG_INR_005                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |               |               |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                         |               |               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                         |               |               |
+| <b>Test procedure</b>    | 1. The simulated PHG receives an association request from the PHD under test.<br>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.<br>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.<br>4. Once the PHD under test sends an extended configuration, check that the Quick Value |                         |               |               |
+
+object attributes are:
+
+#### a. Mandatory attribute Type
+
+- attribute-id = MDC\_ATTR\_ID\_TYPE
+- attribute-type = TYPE
+- attribute-value = MDC\_PART\_SCADA (0x00 0x02) | MDC\_QUICK\_VALUE\_COAG (0x72 0x0C)
+
+#### b. Not recommended Supplemental –Types Attribute
+
+- attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+- attribute-type = SupplementalTypeList
+- attribute-value.length =<variable> (Sequence of TYPE (TYPE.length= 4 bytes
+
+#### 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 3 must be set (mss-msmt-aperiodic(3))
+  - Bit 9 must be set (mss-acc-agent-initiated(9))
+
+#### d. IF Not recommended attribute Metric-Structure-Small is present
+
+- attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+- attribute-type = MetricStructureSmall
+- attribute-value.length = <variable>(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))
+
+#### e. IF Not recommended attribute Measurement-Status is present
+
+- attribute-id = MDC\_ATTR\_MSMT\_STAT
+- attribute-type = MeasurementStatus (BITS-16)
+- attribute-value.length =2 bytes
+
+#### 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
+
+#### g. IF Not recommended attribute Metric-Id-List is present
+
+- attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+- attribute-type = MetricIdList
+- attribute-value.length= SEQUENCE OF OID-Type (INT-U16)
+
+#### 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
+
+#### i. 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
+
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                            |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|
+| j. IF Not recommended attribute Source-Handle-Reference is present<br><ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> k. IF recommended attribute Base-Offset-Time-Stamp is present<br><ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> l. IF Not recommended attribute Measure-Active-Period<br><ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> m. IF recommended attribute Basic-Nu-Observed-Value<br><ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> n. IF NOT Recommended attribute Accuracy is present<br><ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |                                                            |
+| <b>Pass/Fail criteria</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | All checked values are as specified in the test procedure. |
+| <b>Notes</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                         |              |              |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------------|--------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/INR/BV-009                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                         |              |              |
+| <b>TP label</b>          | ISI Numeric Object – Extended configuration                                                                                                                                                                                                                                                                                                                                                                                                                                          |                         |              |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-10418C] |              |              |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                | NumObj 3; M             | NumObj 5; R  | NumObj 7; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | NumObj 9; R             | NumObj 11; R | NumObj 13; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | NumObj 15; R            | NumObj 17; R | NumObj 19; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | NumObj 23; R            | NumObj 31; R | NumObj 41; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | NumObj 45; C            | NumObj 47; C | NumObj 49; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | NumObj 51; R            |              |              |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | ISI 3; M                | ISI 4; M     | ISI 5; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | ISI 6; R                | ISI 7; R     |              |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                         |              |              |
+| <b>Test purpose</b>      | Check that:<br>The ISI Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                  |                         |              |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_OXP_181 AND C_AG_INR_006                                                                                                                                                                                                                                                                                                                                                                                                                      |                         |              |              |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                             |                         |              |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                              |                         |              |              |
+| <b>Test procedure</b>    | 1. The simulated PHG receives an association request from the PHD under test.<br>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.<br>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration. |                         |              |              |
+
+4. Once the PHD under test sends an extended configuration, check that the ISI object attributes are:
+  - a. Mandatory attribute Type
+    - attribute-id = MDC\_ATTR\_ID\_TYPE
+    - attribute-type = TYPE
+    - attribute-value = MDC\_PART\_SCADA (0x00 0x02) | MDC\_ ISI \_COAG (0x72 0x10)
+  - b. Not recommended Supplemental –Types Attribute
+    - attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+    - attribute-type = SupplementalTypeList
+    - attribute-value.length =<variable> (Sequence of TYPE (TYPE.length= 4 bytes)
+  - 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 3 must be set (mss-msmt-aperiodic(3))
+      - Bit 9 must be set (mss-acc-agent-initiated(9))
+  - d. IF Not recommended attribute Metric-Structure-Small is present
+    - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+    - attribute-type = MetricStructureSmall
+    - attribute-value.length = <variable>(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))
+  - e. IF Not recommended attribute Measurement-Status is present
+    - attribute-id = MDC\_ATTR\_MSMT\_STAT
+    - attribute-type = MeasurementStatus (BITS-16)
+    - attribute-value.length =2 bytes
+  - 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
+  - g. IF Not recommended attribute Metric-Id-List is present
+    - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+    - attribute-type = MetricIdList
+    - attribute-value.length= SEQUENCE OF OID-Type (INT-U16)
+  - 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
+  - i. Mandatory attribute Unit-Code
+    - attribute-id = MDC\_ATTR\_UNIT\_CODE
+    - attribute-type = OID-Type(INT-U16)
+    - attribute-value.length = 2 bytes
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><input type="checkbox"/> attribute-value= MDC_DIM_DIMLESS</p> <p>j. IF Not recommended attribute Source-Handle-Reference is present</p> <p><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</p> <p><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</p> <p><input type="checkbox"/> attribute-value.length = 2 bytes</p> <p>k. IF recommended attribute Base-Offset-Time-Stamp is present</p> <p><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</p> <p><input type="checkbox"/> attribute-type = BaseOffsetTime</p> <p><input type="checkbox"/> attribute-value.length = 8 bytes</p> <p>l. IF Not recommended attribute Measure-Active-Period</p> <p><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</p> <p><input type="checkbox"/> attribute-type = FLOAT type</p> <p><input type="checkbox"/> attribute-value.length = 4 bytes</p> <p>m. IF recommended attribute Basic-Nu-Observed-Value</p> <p><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</p> <p><input type="checkbox"/> attribute-type = BasicNuObsValue</p> <p><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</p> <p>n. IF NOT Recommended attribute Accuracy is present</p> <p><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</p> <p><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</p> <p><input type="checkbox"/> attribute-value.length = 4 bytes</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                          |                                                                                                                                                                                                                                                                                                                |                         |              |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/INR/BV-010                                                                                                                                                                                                                                                                                    |                         |              |
+| <b>TP label</b>          | Target Level for INR Numeric Object – Extended configuration                                                                                                                                                                                                                                                   |                         |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-10418C] |              |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                          | NumObj 3; M             | NumObj 5; R  |
+|                          |                                                                                                                                                                                                                                                                                                                | NumObj 9; R             | NumObj 11; R |
+|                          |                                                                                                                                                                                                                                                                                                                | NumObj 15; R            | NumObj 17; R |
+|                          |                                                                                                                                                                                                                                                                                                                | NumObj 23; R            | NumObj 31; R |
+|                          |                                                                                                                                                                                                                                                                                                                | NumObj 45; C            | NumObj 47; C |
+|                          |                                                                                                                                                                                                                                                                                                                | NumObj 51; R            |              |
+|                          |                                                                                                                                                                                                                                                                                                                | Target 3; M             | Target 4; M  |
+|                          |                                                                                                                                                                                                                                                                                                                | Target 6; M             | Target 7; R  |
+| <b>Test purpose</b>      | Check that:<br>The Target Level for INR Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                           |                         |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_OXP_181 AND C_AG_INR_007                                                                                                                                                                                                                                                |                         |              |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                       |                         |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                        |                         |              |
+| <b>Test procedure</b>    | 1. The simulated PHG receives an association request from the PHD under test.<br>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, the PHG responds with an "unsupported-config" and waits for a new configuration.
+4. Once the PHD under test sends an extended configuration, check that the Target Level for INR 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\_TARGET\_LEVEL\_COAG (0x72 0x78)
+  - b. Not recommended Supplemental –Types Attribute
+    - attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+    - attribute-type = SupplementalTypeList
+    - attribute-value.length =<variable> (Sequence of TYPE (TYPE.length= 4 bytes)
+  - 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 9 must be set (mss-acc-agent-initiated(9))
+      - Bit 12 may be set (mss-cat-manual(12)) if this value is entered manually
+      - Bit 13 must be set (mss-cat-setting(13))
+  - d. IF Not recommended attribute Metric-Structure-Small is present
+    - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+    - attribute-type = MetricStructureSmall
+    - attribute-value.length = <variable>(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8))))
+  - e. IF Not recommended attribute Measurement-Status is present
+    - attribute-id = MDC\_ATTR\_MSMT\_STAT
+    - attribute-type = MeasurementStatus (BITS-16)
+    - attribute-value.length =2 bytes
+  - 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
+  - g. IF Not recommended attribute Metric-Id-List is present
+    - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+    - attribute-type = MetricIdList
+    - attribute-value.length= SEQUENCE OF OID-Type (INT-U16)
+  - 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
+  - i. Mandatory attribute Unit-Code
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_INR</li> </ul> <p>j. IF Not recommended attribute Source-Handle-Reference is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>k. IF recommended attribute Base-Offset-Time-Stamp is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> <p>l. IF Not recommended attribute Measure-Active-Period</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>m. IF recommended attribute Basic-Nu-Observed-Value</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> <p>n. IF NOT Recommended attribute Accuracy is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|                          |                                                                                                                             |                         |                 |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/INR/BV-011                                                                                                 |                         |                 |
+| <b>TP label</b>          | Current Level of Medication Numeric Object – Extended configuration                                                         |                         |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                 | [ISO/IEEE 11073-10418C] |                 |
+|                          | <b>Testable items</b>                                                                                                       | NumObj 3; M             | NumObj 5; R     |
+|                          |                                                                                                                             | NumObj 9; R             | NumObj 11; R    |
+|                          |                                                                                                                             | NumObj 15; R            | NumObj 17; R    |
+|                          |                                                                                                                             | NumObj 23; R            | NumObj 31; R    |
+|                          |                                                                                                                             | NumObj 45; C            | NumObj 47; C    |
+|                          |                                                                                                                             | NumObj 51; R            |                 |
+|                          |                                                                                                                             | CurrentMed 3; M         | CurrentMed 4; M |
+|                          |                                                                                                                             | CurrentMed 6; M         | CurrentMed 7; R |
+| <b>Test purpose</b>      | Check that:<br>The Current Level of Medication Numeric object contains the attributes specified for Extended Configuration. |                         |                 |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_OXP_181 AND C_AG_INR_008                                                             |                         |                 |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                    |                         |                 |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                     |                         |                 |
+
+|                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test procedure</b> | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that the Current Level of Medication object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80)   MDC_MED_CURRENT_COAG (0x72 0x7C)</li> </ul> </li> <li>b. Not recommended Supplemental –Types Attribute <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes)</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> <li>• Bit 12 may be set (mss-cat-manual(12)) if this value is entered manually</li> <li>• Bit 13 must be set (mss-cat-setting(13))</li> </ul> </li> </ul> </li> <li>d. IF Not recommended attribute Metric-Structure-Small is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))</li> </ul> </li> <li>e. IF Not recommended attribute Measurement-Status is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> </ul> </li> <li>f. IF Not recommended attribute Metric-Id is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length= 2 bytes</li> </ul> </li> <li>g. IF Not recommended attribute Metric-Id-List is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIST</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value.length= SEQUENCE OF OID-Type (INT-U16)</li> </ul> </li> <li>h. IF Not recommended attribute Metric-Id-Partition is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> </ul> </li> </ol> </li> </ol> |
+|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> i. Mandatory attribute Unit-Code <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_MILLI_G</li> </ul> j. IF Not recommended attribute Source-Handle-Reference is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> k. IF recommended attribute Base-Offset-Time-Stamp is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> l. IF Not recommended attribute Measure-Active-Period <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> m. IF recommended attribute Basic-Nu-Observed-Value <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> n. IF NOT Recommended attribute Accuracy is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                     |                                                                                                                                     |                         |               |               |
+|---------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------|---------------|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/INR/BV-012                                                                                                         |                         |               |               |
+| <b>TP label</b>     | Recommended New Level of Medication Numeric Object – Extended configuration                                                         |                         |               |               |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                         | [ISO/IEEE 11073-10418C] |               |               |
+|                     | <b>Testable items</b>                                                                                                               | NumObj 3; M             | NumObj 5; R   | NumObj 7; M   |
+|                     |                                                                                                                                     | NumObj 9; R             | NumObj 11; R  | NumObj 13; R  |
+|                     |                                                                                                                                     | NumObj 15; R            | NumObj 17; R  | NumObj 19; M  |
+|                     |                                                                                                                                     | NumObj 23; R            | NumObj 31; R  | NumObj 41; C  |
+|                     |                                                                                                                                     | NumObj 45; C            | NumObj 47; C  | NumObj 49; C  |
+|                     |                                                                                                                                     | NumObj 51; R            |               |               |
+|                     |                                                                                                                                     | RecomMed 3; M           | RecomMed 4; M | RecomMed 5; M |
+|                     |                                                                                                                                     | RecomMed 6; R           | RecomMed 7; R |               |
+|                     |                                                                                                                                     |                         |               |               |
+| <b>Test purpose</b> | Check that:<br>The Recommended New Level of Medication Numeric object contains the attributes specified for Extended Configuration. |                         |               |               |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_OXP_181 AND C_AG_INR_009                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that the recommended New Level of Medication object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80)   MDC_MED_NEW_COAG (0x72 0x80)</li> </ol> </li> <li>b. Not recommended Supplemental -Types Attribute <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes)</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> <li>• Bit 14 must be set (mss-cat-calculation(14))</li> </ol> </li> </ol> </li> <li>d. IF Not recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8))))</li> </ol> </li> <li>e. IF Not recommended attribute Measurement-Status is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> </ol> </li> <li>f. IF Not recommended attribute Metric-Id is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length= 2 bytes</li> </ol> </li> <li>g. IF Not recommended attribute Metric-Id-List is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIST</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value.length= SEQUENCE OF OID-Type (INT-U16)</li> </ol> </li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>h. IF Not recommended attribute Metric-Id-Partition is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>i. Mandatory attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_MILLI_G</li> </ul> <p>j. IF Not recommended attribute Source-Handle-Reference is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>k. IF recommended attribute Base-Offset-Time-Stamp is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> <p>l. IF Not recommended attribute Measure-Active-Period</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>m. IF recommended attribute Basic-Nu-Observed-Value</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> <p>n. IF NOT Recommended attribute Accuracy is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                      |                                                                                                                                           |                                                                |                                                                 |
+|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|-----------------------------------------------------------------|
+| <b>TP Id</b>         | TP/PLT/PHD/CLASS/INR/BV-013                                                                                                               |                                                                |                                                                 |
+| <b>TP label</b>      | Device and Sensor annunciation status Enumeration Object – Extended configuration                                                         |                                                                |                                                                 |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                               | [ISO/IEEE 11073-10418C]                                        |                                                                 |
+|                      | <b>Testable items</b>                                                                                                                     | EnumObj 2; M<br>EnumObj 5; R<br>DevSenAn 1; M<br>DevSenAn 8; R | EnumObj 3; R<br>EnumObj 19; O<br>DevSenAn 5; M<br>DevSenAn 9; R |
+| <b>Test purpose</b>  | Check that:<br><br>Device and Sensor annunciation status Enumeration Object contains the attributes specified for Extended Configuration. |                                                                |                                                                 |
+| <b>Applicability</b> | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_OXP_181 AND C_AG_INR_010                                                                           |                                                                |                                                                 |
+| <b>Other PICS</b>    | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                  |                                                                |                                                                 |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is in the extended range, if it is not, the simulated PHG must respond with an "unsupported-config" and waits for a new configuration.</li> <li>5. Once the PHD under test sends an extended configuration, check that all Device and Sensor annunciation status objects have: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80),<br/>MDC_INR_METER_DEV_STATUS (0x72 0x75)</li> </ol> </li> <li>b. IF Not recommended attribute Supplemental-Types is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt;(Sequence of TYPE (TYPE.length = 4 bytes))</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec_Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 3 must be set (mss-msmt-aperiodic(3))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> </ol> </li> </ol> </li> <li>d. IF Not recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length = 1byte(INT-U8) + ms-comp-no = 1byte(INT-U8))))</li> </ol> </li> <li>e. IF Not recommended attribute Measurement-Status <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus(BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ol> </li> <li>f. IF Not recommended attribute Metric-Id is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = Only one attribute of Metric-Id and Metric-Id-List shall be present.</li> </ol> </li> <li>g. IF Not recommended attribute Metric-Id is present-List <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIS</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> </ol> </li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><input type="checkbox"/> attribute-value.length= &lt;variable&gt;(SEQUENCE OF OID-Type (INT-U16))</p> <p>h. IF Not recommended attribute Metric-Id-Partition is present</p> <p><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</p> <p><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</p> <p><input type="checkbox"/> attribute-value.length = 2 bytes</p> <p>i. IF Not recommended attribute Unit-Code is present</p> <p><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</p> <p><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</p> <p><input type="checkbox"/> attribute-value.length = 2 bytes</p> <p>j. IF Not recommended attribute Source-Handle-Reference is present</p> <p><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</p> <p><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</p> <p><input type="checkbox"/> attribute-value.length = 2 bytes</p> <p>k. IF recommended attribute Base-Offset-Time-Stamp is present</p> <p><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</p> <p><input type="checkbox"/> attribute-type = BaseOffsetTime</p> <p><input type="checkbox"/> attribute-value.length = 8 bytes</p> <p>l. IF Not recommended attribute Measure-Active-Period</p> <p><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</p> <p><input type="checkbox"/> attribute-type = FLOAT type</p> <p><input type="checkbox"/> attribute-value.length = 4 bytes</p> <p>m. IF Mandatory attribute Enum-Observed-Value-Basic-Bit-Str is present</p> <p><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR</p> <p><input type="checkbox"/> attribute-type = BITS-16</p> <p><input type="checkbox"/> attribute-value.length = 2 bytes</p> <p><input type="checkbox"/> attribute-value = inr-device-battery-low   inr-sensor-malfunction   inr-sensor-sample-size-insufficient   inr-sensor-strip-insertion   inr-sensor-strip-type-incorrect   inr-sensor-result-too-high   inr-sensor-result-too-low   inr-sensor-temp-too-high   inr-sensor-temp-too-low   inr-sensor-read-interrupt   inr-device-gen-fault   inr-sensor-calibration due</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                     |                                                                                                 |                         |                    |
+|---------------------|-------------------------------------------------------------------------------------------------|-------------------------|--------------------|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/INR/BV-014                                                                     |                         |                    |
+| <b>TP label</b>     | Context Tester Enumeration Object – Extended configuration                                      |                         |                    |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                     | [ISO/IEEE 11073-10418C] |                    |
+|                     | <b>Testable items</b>                                                                           | EnumObj 2; M            | EnumObj 3; R       |
+|                     |                                                                                                 | EnumObj 5; R            | EnumObj 6; R       |
+|                     |                                                                                                 | EnumObj 8; R            | EnumObj 9; R       |
+|                     |                                                                                                 | EnumObj 12; R           | EnumObj 16; C      |
+|                     |                                                                                                 | EnumObj 20; C           | EnumObj 21; C      |
+|                     |                                                                                                 | EnumObj 23; C           | ContextTester 3; M |
+|                     |                                                                                                 | ContextTester 4; M      | ContextTester 5; R |
+|                     |                                                                                                 |                         | ContextTester 6; M |
+| <b>Test purpose</b> | Check that:<br>Context Tester Enumeration Object contains the attributes specified for Extended |                         |                    |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_OXP_181 AND C_AG_INR_012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is in the extended range, if it is not, the simulated PHG must respond with an "unsupported-config" and waits for a new configuration.</li> <li>5. Once the PHD under test sends an extended configuration, check that all Context Tester objects have: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80),<br/>MDC_CTXT_INR_TESTER (0x72 0x84)</li> </ol> </li> <li>b. IF Not recommended attribute Supplemental-Types is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt;(Sequence of TYPE (TYPE.length= 4 bytes))</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec_Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 3 must be set (mss-msmt-aperiodic(3))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> </ol> </li> </ol> </li> <li>d. IF Not recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8))))</li> </ol> </li> <li>e. IF Not recommended attribute Measurement-Status <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus(BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> </ol> </li> <li>f. IF Not recommended attribute Metric-Id is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = Only one attribute of Metric-Id and Metric-Id-List shall be present.</li> </ol> </li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>g. IF Not recommended attribute Metric-Id is present-List</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIS</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value.length= &lt;variable&gt;(SEQUENCE OF OID-Type (INT-U16))</li> </ul> <p>h. IF Not recommended attribute Metric-Id-Partition is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>i. IF Not recommended attribute Unit-Code is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>j. IF Not recommended attribute Source-Handle-Reference is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>k. IF recommended attribute Base-Offset-Time-Stamp is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> <p>l. IF Not recommended attribute Measure-Active-Period</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>m. Mandatory attribute Enum-Observed-Value-Simple_OID is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIMP_OID</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute.value= One of the following nomenclature value will be used: <ul style="list-style-type: none"> <li>• MDC_CTXT_INR_TESTER_SELF (0x72 0x85) OR</li> <li>• MDC_CTXT_INR_TESTER_HCP (0x72 0x86) OR</li> <li>• MDC_CTXT_INR_TESTER_LAB (0x72 0x87)</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                 |                                                        |                         |               |
+|-----------------|--------------------------------------------------------|-------------------------|---------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/INR/BV-015                            |                         |               |
+| <b>TP label</b> | Batch Code Enumeration Object – Extended configuration |                         |               |
+| <b>Coverage</b> | <b>Spec</b>                                            | [ISO/IEEE 11073-10418C] |               |
+|                 | <b>Testable items</b>                                  | EnumObj 2; M            | EnumObj 3; R  |
+|                 |                                                        | EnumObj 5; R            | EnumObj 6; R  |
+|                 |                                                        | EnumObj 8; R            | EnumObj 9; R  |
+|                 |                                                        | EnumObj 12; R           | EnumObj 16; C |
+|                 |                                                        | EnumObj 20; C           | EnumObj 21; C |
+|                 |                                                        |                         | EnumObj 4; M  |
+|                 |                                                        |                         | EnumObj 7; R  |
+|                 |                                                        |                         | EnumObj 10; R |
+|                 |                                                        |                         | EnumObj 17; C |
+|                 |                                                        |                         | EnumObj 22; C |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                |                |                |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------------|----------------|
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | EnumObj 23; C  | EnumObj 24; C  | BatchCode 2; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | BatchCode 3; M | BatchCode 4; M | BatchCode 5; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | BatchCode 6; M |                |                |
+| <b>Test purpose</b>      | Check that:<br>Batch Code Object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                |                |                |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_OXP_181 AND C_AG_INR_013                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                |                |                |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                |                |                |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                |                |                |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is in the extended range, if it is not, the simulated PHG must respond with an "unsupported-config" and waits for a new configuration.</li> <li>5. Once the PHD under test sends an extended configuration, check that all Batch Code objects have: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80),<br/>MDC_BATCHCODE_COAG (0x72 0x74)</li> </ol> </li> <li>b. IF Not recommended attribute Supplemental-Types is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt;(Sequence of TYPE (TYPE.length= 4 bytes))</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec_Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 3 must be set (mss-msmt-aperiodic(3))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> </ol> </li> </ol> </li> <li>d. IF Not recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8))))</li> </ol> </li> <li>e. IF Not recommended attribute Measurement-Status <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus(BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> </ol> </li> <li>f. IF Not recommended attribute Metric-Id is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> </ol> </li> </ol> </li> </ol> |                |                |                |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = Only one attribute of Metric-Id and Metric-Id-List shall be present.</li> </ul> <p>g. IF Not recommended attribute Metric-Id is present-List</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIS</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value.length= &lt;variable&gt;(SEQUENCE OF OID-Type (INT-U16))</li> </ul> <p>h. IF Not recommended attribute Metric-Id-Partition is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>i. IF Not recommended attribute Unit-Code is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>j. IF Not recommended attribute Source-Handle-Reference is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>k. IF recommended attribute Base-Offset-Time-Stamp is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> <p>l. IF Not recommended attribute Measure-Active-Period</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>m. Mandatory attribute Enum-Observed-Value-Simple-Str is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIMP_STR</li> <li><input type="checkbox"/> attribute-type = BITS-16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                      |                                                                                              |                         |                                       |
+|----------------------|----------------------------------------------------------------------------------------------|-------------------------|---------------------------------------|
+| <b>TP Id</b>         | TP/PLT/PHD/CLASS/INR/BV-016                                                                  |                         |                                       |
+| <b>TP label</b>      | PM-Store Attributes for Extended Configuration                                               |                         |                                       |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                  | [ISO/IEEE 11073-10418C] |                                       |
+|                      | <b>Testable items</b>                                                                        | PMStrObjAtt 1; M        | PMStrObjAtt 5; M                      |
+|                      |                                                                                              | PMStrObjAtt 8; M        | PMStrObjAtt 9; R                      |
+|                      |                                                                                              |                         | PMStrObjAtt 6; M<br>PMStrObjAtt 12; M |
+| <b>Test purpose</b>  | Check that:<br>PM-Store Object contains the attributes specified for Extended Configuration. |                         |                                       |
+| <b>Applicability</b> | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_OXP_041 AND C_AG_OXP_181                              |                         |                                       |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. The handle for the PM-Store attribute must be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = must be unique and non-zero. Actual value may be specified by the Device Specialization.</li> </ol> </li> </ol> </li> <li>5. 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.</li> <li>6. The PHD issues a GET response with the PM-Store attributes it supports: <ol style="list-style-type: none"> <li>a. Mandatory Store-Capacity-Count <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STORE_CAPAC_CNT</li> <li><input type="checkbox"/> attribute-type = INT-U32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = See relation with next attribute</li> </ol> </li> <li>b. Mandatory attribute Store-Usage-Count <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STORE_USAGE_CNT</li> <li><input type="checkbox"/> attribute-type = INT-U32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = consistent with actual number of segments present and always <math>\leq</math> than Storage-Capacity-Count</li> </ol> </li> <li>c. Mandatory attribute PM-Store-Label <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_LABEL_STRING</li> <li><input type="checkbox"/> attribute-type = OCTET STRING</li> <li><input type="checkbox"/> attribute-value.length = &lt;Variable&gt;</li> <li><input type="checkbox"/> attribute-value = Printable ASCII</li> </ol> </li> <li>d. IF Not Recommended attribute Sample-Period is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_SAMP</li> <li><input type="checkbox"/> attribute-type = RelativeTime</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                 |                                              |                         |                 |
+|-----------------|----------------------------------------------|-------------------------|-----------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/INR/BV-017                  |                         |                 |
+| <b>TP label</b> | PM Segment Object for Extended Configuration |                         |                 |
+| <b>Coverage</b> | <b>Spec</b>                                  | [ISO/IEEE 11073-10418C] |                 |
+|                 | <b>Testable items</b>                        | PMStoreObj 5; M         | PMStoreObj 6; O |
+|                 |                                              | PMSegObj 6; M           | PMSegObj 7; M   |
+|                 |                                              | PMSegObj 10; M          | PMStoreObj 7; M |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>       | Check that:<br>PM-Segment contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_OXP_041 AND C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>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.</li> <li>2. 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.</li> <li>3. The PHD issues a response with the PM-Segment attributes it supports: <ol style="list-style-type: none"> <li>a. Mandatory attribute Segment-Label <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_SEG_LABEL_STRING</li> <li><input type="checkbox"/> attribute-type = OCTET STRING</li> <li><input type="checkbox"/> attribute-value.length = consistent with value</li> <li><input type="checkbox"/> attribute-value = &lt;printable ASCII&gt;</li> </ol> </li> <li>b. Mandatory attribute Segment-Start-BO-Time <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_START_SEG_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>c. Mandatory attribute Segment-End-BO-Time <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_END_SEG_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>d. Mandatory attribute Segment-Usage-Count <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SEG_USAGE_CNT</li> <li><input type="checkbox"/> attribute-type = INT-U32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;not relevant in this test&gt;</li> </ol> </li> <li>e. Mandatory attribute PM-Segment-Entry-Map <ol style="list-style-type: none"> <li><input type="checkbox"/> SegmentEntryHeader.value = One of the next must be set: <ul style="list-style-type: none"> <li>• seg-elem-hdr-relative-time(1)</li> <li>• seg-elem-hdr-hires-relative-time(2)</li> <li>• seg-elem-hdr-bo-time(3)</li> </ul> </li> <li><input type="checkbox"/> SegmEntryElem: &lt;Record the fields for later comparison&gt;</li> </ol> </li> </ol> </li> <li>4. Repeat steps 3 and 4 for every Segment.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• All checked values are as specified in the test procedure.</li> <li>• Every segm-entry-header must contain one of the time formats.</li> <li>• At least one PM-Segment must reference the INR in its PM-Segm-Entry-Map.</li> <li>• If there are more than one PM-Segment, the rest of them must reference one of the objects defined in the spec in its PM-Segm-Entry-Map.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                         |                 |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/INR/BV-017_A                                                                                                                                                                                                                                                                                                                                                                                                                                          |                         |                 |
+| <b>TP label</b>           | PM-Segment Object for Extended Configuration.MDS Event Reports                                                                                                                                                                                                                                                                                                                                                                                                         |                         |                 |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-10418C] |                 |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                  | PMStoreObj 3; M         | PMStoreObj 4; M |
+| <b>Test purpose</b>       | Check that:<br>Any configuration with a PM Store for persistent storage shall disable agent-initiated transmission and enable access to PM-Store transmissions                                                                                                                                                                                                                                                                                                         |                         |                 |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_OXP_041 AND C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                        |                         |                 |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                         |                 |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                   |                         |                 |
+| <b>Test procedure</b>     | 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.<br><br>2. 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.<br><br>3. The simulated PHG asks for a measurement.<br><br>4. Check the event reports that are sent by the PHD. |                         |                 |
+| <b>Pass/Fail criteria</b> | In step 4, the PHD shall not send the data with MDS event reports.                                                                                                                                                                                                                                                                                                                                                                                                     |                         |                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                         |                 |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                         |                |                |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------|----------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/INR/BV-018                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                         |                |                |
+| <b>TP label</b>          | Communication Model: Association Procedure                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                         |                |                |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-10418C] |                |                |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | AgProcAs 1; M           | AgProcAs 2; M  | AgProcAs 4; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | AgProcAs 5; M           | AgProcAs 6; M  | AgProcAs 7; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | AgProcAs 8; M           | AgProcAs 9; M  | AgProcAs 10; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | AgProcAs 11; M          | AgProcAs 12; M | MDSMethods 3;M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | AgProcAs 13; O          |                |                |
+| <b>Test purpose</b>      | Check that:<br>The association procedure data exchange is correct                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                         |                |                |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_163                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                         |                |                |
+| <b>Other PICS</b>        | C_AG_OXP_002, C_AG_OXP_017                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                         |                |                |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                         |                |                |
+| <b>Test procedure</b>    | 1. The PHD sends a message to associate with the simulated PHG, the expected fields sent by the PHD are:<br>a. APDU Type<br><input type="checkbox"/> field- type = AarqApdu<br><input type="checkbox"/> field-length =2 bytes<br><input type="checkbox"/> field-value =0xE2 0x00.<br>b. assoc-version<br><input type="checkbox"/> field- type = AssociationVersion<br><input type="checkbox"/> field-length =BITS-32<br><input type="checkbox"/> field- value=0x80 0x00 0x00 0x00<br>c. data-proto-id<br><input type="checkbox"/> 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 (0x40 0x00 0x00 0x00 OR 0xC0 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 =
+  - 0x07 0x08 OR 0x07 0x09 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
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• If the PHD supports Agent-initiated measurement transfer → Bit 15 is set (data-req-supp-init-agent(15))</li> <li>• If the PHD supports requesting objects based on the object handle → Bit 6 will be set (data-req-supp-scope-handle(6)).</li> <li>• If the PHD supports single response → Bit 8 will be set (data-req-supp-mode-single-rsp(8)).</li> <li>• If the PHD supports time unlimited data request → Bit 10 will be set (data-req-supp-mode-time-no-limit(10)).</li> </ul> <p>l. data-req-init-agent-count (DataReqModeCapab)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = INT-U8</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field.value = 0x01</li> </ul> <p>m. data-req-init-manager-count (DataReqModeCapab)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = INT-U8</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field.value = 0x00</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                         |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/INR/BV-019                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                         |  |
+| <b>TP label</b>          | PM Segment Object for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-10418C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | PMStrObjMeth 1; M       |  |
+| <b>Test purpose</b>      | Check that:<br>INR monitor supports the Clear-Segments method with Confirmed mode                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                         |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_OXP_041 AND C_AG_OXP_071                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                         |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                         |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state and the PHD has at least one PM-Segment with data stored.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                         |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Take measurements with the PHD of a value that is stored on a PM-Segment.</li> <li>2. 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.</li> <li>3. The PHD issues a GET response with the PM-Store attributes, record the values of the PMStoreCapab attribute.</li> <li>4. The simulated PHG shall send a Get-Segment-Info object action with a segmSelection set to all-segments to check that there are no segments in use.</li> <li>5. The simulated PHG sends a Clear-Segment to all segments: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> <li><input type="checkbox"/> SegmSelection = all-segments</li> </ul> </li> </ol> </li> <li>6. The PHD under test operation response: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Response   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> </ul> </li> </ol> </li> </ol> |                         |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> </ul> <p>7. Delay.</p> <p>8. The simulated PHG sends a request for the PM-Segment Data with SegmSelection = all-segments to obtain all the segments:</p> <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> SegmSelection = &lt;Instance number of the selected PM-Segment that contained data before the clear-segment action&gt;</li> </ul> </li> </ul> <p>9. The PHD issues an action response with the Data:</p> <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Response   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> TrigSegmXferRsp = <ul style="list-style-type: none"> <li>• IF pmsc-clear-segm-remove is NOT set THEN TrigSegmXferRsp = tsxr-fail-segm-empty</li> <li>• ELSE TrigSegmXferRsp = tsxr-fail-no-such-segment</li> </ul> </li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                               |  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/INR/BV-021                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                               |  |
+| <b>TP label</b>          | Operating State. PHG to PHD Maximum APDU Size                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | CommonCharac 3; M                                             |  |
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [ISO/IEEE 11073-10418C]                                       |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ComChar 2; M                                                  |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The total size of the response does not exceed of the maximum APDU size established by the specialization</p> <p>[AND]</p> <p>An INR 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</p>                                                                                                                                                                                                                                                         |                                                               |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_163                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_100                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG issues a "Remote Operation Invoke   Get" command with: <ol style="list-style-type: none"> <li>a. Obj-handle set to 0 (to request an MDS object)</li> <li>b. attribute-id-list.count = 103</li> <li>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</li> </ol> </li> <li>2. Check the response of the PHD.</li> <li>3. The simulated PHG issues a "Remote Operation Invoke   Get" command with the handle</li> </ol> |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | 4. Check the response of the PHD.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• 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. <ul style="list-style-type: none"> <li>○ 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): <ul style="list-style-type: none"> <li>▪ Pulse oximeter → 9216 octets</li> <li>▪ Weighing scales → 896 octets</li> <li>▪ Glucose meter → 5120 octets or 64512 octets if the PHD supports PM-Store</li> <li>▪ Blood pressure → 896 octets</li> <li>▪ Thermometer → 896 octets</li> <li>▪ Independent activity hub → 5120 octets</li> <li>▪ Cardiovascular → 64512 octets or 6624 octets if the PHD under test only supports the Step Counter Profile</li> <li>▪ Strength → 64512 octets:</li> <li>▪ Adherence monitor → 1024 octets</li> <li>▪ Peak flow → 2030 octets</li> <li>▪ Body composition analyser → 7730 octets</li> <li>▪ Basic ECG/Simple ECG → 7168 octets or 64512 octets if the PHD supports PM-Store</li> <li>▪ Basic ECG/Heart rate → 1280 octets or 64512 octets if the PHD supports PM-Store</li> <li>▪ International normalized ratio → 896 octets or 64512 if the PHD supports PM-Store</li> </ul> </li> <li>○ In the case where it responds with a roer, the reason must not be protocol-violation (23)</li> </ul> </li> <li>• In step 4, the PHD must respond with a rors-cmip-get message.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                          |                                                                                                                                                                                                                                                                                                                   |                         |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/INR/BV-022                                                                                                                                                                                                                                                                                       |                         |  |
+| <b>TP label</b>          | INR measurement above the capabilities of the device sensor                                                                                                                                                                                                                                                       |                         |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-10418C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                             | INR 29; M               |  |
+| <b>Test purpose</b>      | Check that:<br><br>In standard configurations 1800 (0x0708) and 1801 (0x0709), an INR measurement that is above the capabilities of the device sensor shall be indicated with an observed value of +INFINITY                                                                                                      |                         |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_163 AND (C_AG_INR_001 OR C_AG_INR_002) AND (NOT C_AG_OXP_181)                                                                                                                                                                                                                           |                         |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                   |                         |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                              |                         |  |
+| <b>Test procedure</b>    | 1. Place in the device sensor an INR sample with an INR level above the capabilities of the device sensor and acquire a measurement with the PHD under test.<br><br>2. The test tool simulated PHG waits to receive an event report from the PHD under test. The event report shall contain the following values: |                         |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> event-type = MDC_NOTI_SCAN_REPORT_FIXED (0x0D 0x1D)</li> <li><input type="checkbox"/> obj-handle = 1 (1st Measurement is INR)</li> <li><input type="checkbox"/> obs-val-data = <ul style="list-style-type: none"> <li>• Basic-Nu-Observed-Value = 0x07FE</li> <li>• Base-Offset-Time-Stamp = &lt;Not relevant for this Test Case&gt;</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Notes</b>              | The vendor must provide an INR sample (or a simulated INR solution) with an INR level above the capabilities of device sensor.                                                                                                                                                                                                                                                                                                           |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                         |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/INR/BV-023                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                         |
+| <b>TP label</b>           | INR measurement below the capabilities of the device sensor                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                         |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-10418C] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | INR 30; M               |
+| <b>Test purpose</b>       | Check that:<br>In standard configurations 1800 (0x0708) and 1801 (0x709), an INR measurement that is below the capabilities of the device sensor shall be indicated with an observed value of – INFINITY.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                         |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_163 AND (C_AG_INR_001 OR C_AG_INR_002) AND (NOT C_AG_OXP_181)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                         |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                         |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                         |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>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.</li> <li>2. The test tool simulated PHG waits to receive an event report from the PHD, under test. The event report shall contain the following values: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> event-type = MDC_NOTI_SCAN_REPORT_FIXED (0x0D 0x1D)</li> <li><input type="checkbox"/> obj-handle = 1 (1st Measurement is INR)</li> <li><input type="checkbox"/> obs-val-data = <ul style="list-style-type: none"> <li>• Basic-Nu-Observed-Value = 0x0802</li> <li>• Base-Offset-Time-Stamp = &lt;Not relevant for this Test Case&gt;</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                         |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                         |
+| <b>Notes</b>              | The vendor must provide an INR sample (or a simulated INR solution) with an INR level below the capabilities of device sensor.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |
+
+|                      |                                                                                                                                                                                                                        |                         |
+|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
+| <b>TP Id</b>         | TP/PLT/PHD/CLASS/INR/BV-024                                                                                                                                                                                            |                         |
+| <b>TP label</b>      | Control Calibration measurement above the capabilities of the device sensor                                                                                                                                            |                         |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                            | [ISO/IEEE 11073-10418C] |
+|                      | <b>Testable items</b>                                                                                                                                                                                                  | CtrlCal 6; M            |
+| <b>Test purpose</b>  | Check that:<br>In standard configurations 1800 (0x0708) and 1801 (0x709), a Control Calibration measurement that is above the capabilities of the device sensor shall be indicated with an observed value of +INFINITY |                         |
+| <b>Applicability</b> | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_INR_002 AND (NOT C_AG_OXP_181)                                                                                                                                                  |                         |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Place in the device sensor a control calibration sample with an INR level above the capabilities of the device sensor and check it with the PHD under test.</li> <li>2. The test tool simulated PHG waits to receive an event report from the PHD under test. The event report shall contain the following values: <ol style="list-style-type: none"> <li>a. Data APDU <ol style="list-style-type: none"> <li><input type="checkbox"/> event-type = MDC_NOTI_SCAN_REPORT_FIXED (0x0D 0x1D)</li> <li><input type="checkbox"/> obj-handle = 2 (Control Calibration)</li> <li><input type="checkbox"/> obs-val-data = <ul style="list-style-type: none"> <li>• Basic-Nu-Observed-Value = 0x07FE</li> <li>• Base-Offset-Time-Stamp = &lt;Not relevant for this Test Case&gt;</li> </ul> </li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              | The vendor must provide a Control Calibration with an INR level above the capabilities of device sensor.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                         |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/INR/BV-025                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                         |
+| <b>TP label</b>           | Control Calibration measurement below the capabilities of the device sensor                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                         |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-10418C] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | CtrlCal 7; M            |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>In standard configurations 1800 (0x0708) and 1801 (0x0709), a Control Solution measurement that is below the capabilities of the device sensor shall be indicated with an observed value of -INFINITY</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                         |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_INR_002 AND (NOT C_AG_OXP_181)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                         |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                         |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                         |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Place in the device sensor a control calibration sample with an INR level above the capabilities of the device sensor and check it with the PHD under test.</li> <li>2. The test tool simulated PHG waits to receive an event report from the PHD, under test. The event report shall contain the following values: <ol style="list-style-type: none"> <li>a. Data APDU <ol style="list-style-type: none"> <li><input type="checkbox"/> event-type = MDC_NOTI_SCAN_REPORT_FIXED (0x0D 0x1D)</li> <li><input type="checkbox"/> obj-handle = 2 (Control Calibration)</li> <li><input type="checkbox"/> obs-val-data = <ul style="list-style-type: none"> <li>• Basic-Nu-Observed-Value = 0x0802</li> <li>• Base-Offset-Time-Stamp = &lt;Not relevant for this Test Case&gt;</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                         |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                         |
+| <b>Notes</b>              | The vendor must provide a Control Calibration with an INR level below the capabilities of device sensor.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                         |
+
+|                 |                                         |                         |
+|-----------------|-----------------------------------------|-------------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/INR/BV-026             |                         |
+| <b>TP label</b> | Set Time (Base Offset Time) INR monitor |                         |
+| <b>Coverage</b> | <b>Spec</b>                             | [ISO/IEEE 11073-10418C] |
+|                 | <b>Testable</b>                         | MDSMethods 5; M         |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |  |  |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|
+|                           | <b>items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |  |  |
+| <b>Test purpose</b>       | Check that:<br><br>If the PHD supports the [Base-Offset-Time-Stamp] attribute, the Set-Base-Offset-Time method shall be implemented                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |  |  |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_163 AND C_AG_OXP_014                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |  |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |  |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |  |  |
+| <b>Test procedure</b>     | 1. The simulated PHG sends a SET action: <ul style="list-style-type: none"> <li><input type="checkbox"/> CHOICE = SetBOTimeInvoke</li> <li><input type="checkbox"/> action-type = MDC_ACT_SET_BO_TIME</li> <li><input type="checkbox"/> the action-info-args are SetBOTimeInvoke <ul style="list-style-type: none"> <li>▪ date-time = bo-seconds = 0x00 0x00 0x00 0x00, bo-fractions = 0x00 0x00, bo-time-offset = 0x3C</li> </ul> </li> </ul> 2. The PHD under test response shall be a rors-cmip-confirmed-action: <ul style="list-style-type: none"> <li><input type="checkbox"/> action-type = MDC_ACT_SET_BO_TIME</li> <li><input type="checkbox"/> action-info-args shall be empty.</li> </ul> |  |  |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |  |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |  |  |
+
+## 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.11. <http://handle.itu.int/11.1002/2000/12067>
+- [b-PHG PICS & PIXIT] Personal Health Gateway DG2016 PICS and PIXIT excel sheet v1.9. <http://handle.itu.int/11.1002/2000/12067>
+- [b-TCRL] Test Case Reference List\_DG2016\_v1.11.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-TI] Continua DG2016 PHD Testable items excel sheet v1.8.  
+<http://handle.itu.int/11.1002/2000/12067>
+
+
+
+## **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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.15-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.845.15-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..61904c12b802df120c05ae72cd89a3ef2690dd5b
--- /dev/null
+++ b/marked/H/T-REC-H.845.15-201704-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.845.15-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.845.15-201704-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..829971f557aa41ce4aeafaf91f3e649b45ec4c9e
--- /dev/null
+++ b/marked/H/T-REC-H.845.15-201704-I_PDF-E/raw.md
@@ -0,0 +1,3241 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.845.15**
+
+(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 5O: Sleep apnoea breathing therapy  
+equipment**
+
+Recommendation ITU-T H.845.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        |
+| 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        |
+| <b>Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN)</b> | <b>H.820–H.859</b> |
+| 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.15
+
+## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5O: Sleep apnoea breathing therapy equipment
+
+## Summary
+
+Recommendation ITU-T H.845.15 provides a test suite structure (TSS) and the test purposes (TP) for sleep apnoea breathing therapy equipment in the Personal Health Devices 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.15 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Procedures, Personal Health Devices Interface; Part 5O: Device Specializations. Personal Health Device (Sleep Apnoea Breathing Therapy Equipment, SABTE) (Version 1.1, 2016-09-20).
+
+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.15 | 2015-11-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/12678">11.1002/1000/12678</a> |
+| 2.0     | ITU-T H.845.15 | 2016-07-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12952">11.1002/1000/12952</a> |
+| 3.0     | ITU-T H.845.15 | 2017-04-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/13232">11.1002/1000/13232</a> |
+
+## 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, sleep apnoea breathing therapy equipment, touch area network.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                                                       | 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 (TSS) .....                                        | 5   |
+| 7       | Electronic attachment .....                                             | 7   |
+| Annex A | Test purposes .....                                                     | 8   |
+| A.1     | TP definition conventions.....                                          | 8   |
+| A.2     | Subgroup 1.3.15: Sleep apnoea breathing therapy equipment (SABTE) ..... | 9   |
+|         | Bibliography.....                                                       | 116 |
+
+**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 5O: Device Specializations. Personal Health Device (Sleep Apnoea Breathing Therapy Equipment -SABTE-) (Version 1.1, 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     | 2015-07-01 | Initial release for Test Tool DG2015 based on the requirements in [b-ITU-T H.810 (2015)]/[b-CDG 2015].                                                                 |
+| 1.1     | 2016-09-20 | Initial release for Test Tool DG2016. This uses "TSS&TP_DG2015_PLT_PART_5O_v1.0.doc" as a baseline and adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016] |
+
+## Recommendation ITU-T H.845.15
+
+## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5O: Sleep apnoea breathing therapy equipment
+
+## 1 Scope
+
+The scope of this Recommendation<sup>1</sup> 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 5O.
+
+- 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)
+
+---
+
+<sup>1</sup> 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
+
+## 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 (2015), *Interoperability design guidelines for personal health systems: TAN/PAN/LAN interface*.
+- [ITU-T H.812] Recommendation ITU-T H.812 (2015), *Interoperability design guidelines for personal health systems: WAN interface*.
+- [ITU-T H.812.1] Recommendation ITU-T H.812.1 (2015), *Interoperability design guidelines for personal health systems: WAN interface: Observation upload*.
+- [ITU-T H.812.2] Recommendation ITU-T H.812.2 (2015), *Interoperability design guidelines for personal health systems: WAN interface: Questionnaires*.
+- [ITU-T H.812.3] Recommendation ITU-T H.812.3 (2015), *Interoperability design guidelines for personal health systems: WAN interface: Capability exchange*.
+- [ITU-T H.812.4] Recommendation ITU-T H.812.4 (2015), *Interoperability design guidelines for personal health systems: WAN interface: Authenticated persistent session*.
+- [ITU-T H.813] Recommendation ITU-T H.813 (2015), *Interoperability design guidelines for personal health systems: HRN interface*.
+- [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>
+- [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.  
+<https://www.iso.org/standard/54331.html> with  
+<https://www.iso.org/standard/63972.html>
+
+[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.  
+<https://www.iso.org/standard/66717.html> with  
+<https://www.iso.org/standard/71886.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                    |
+| 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            |
+| PCT  | Protocol Conformance Testing                  |
+| PCO  | Point of Control and Observation              |
+| PCHA | Personal Connected Health Alliance            |
+| 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].                                                                          | –           |
+
+**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.3.15 (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 <http://handle.itu.int/11.1002/2000/12067>.
+
+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>/<DUT>/<GR>/<SGR>/<XX> – <NNN>). It is specified according to the naming convention defined below:
+  - Each test purpose identifier is introduced by the prefix "TP".
+  - <TT>: 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)
+  - <DUT>: This is the device under test.
+    - PHD: Personal Health Device
+    - PHG: Personal Health Gateway
+  - <GR>: This identifies a group of test cases.
+  - <SGR>: This identifies a subgroup of test cases.
+  - <XX>: This identifies the type of testing.
+    - BV: Valid behaviour test
+    - BI: Invalid behaviour test
+  - <NNN>: 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.15: Sleep apnoea breathing therapy equipment (SABTE)
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                    |                    |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|--------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-000_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                    |                    |
+| <b>TP label</b>          | Get MDS Object for SABTE specialization: Mandatory, Conditional and Optional Attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                    |                    |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-10424] |                    |                    |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MDSSABTE Attr 1; M     | MDSSABTE Attr 3; M | MDSSABTE Attr 5; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MDSSABTE Attr 6; M     | MDSSABTE Attr 7; M |                    |
+| <b>Test purpose</b>      | Check that:<br>The MDS Object contains the attributes specified for a SABTE Personal Health Device (PHD)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                    |                    |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                    |                    |
+| <b>Other PICS</b>        | C_AG_OXP_159, C_AG_OXP_160, C_AG_OXP_161, C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                    |                    |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                    |                    |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>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.</li> <li>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:<br/>MDS attributes: <ol style="list-style-type: none"> <li>Attribute System-Type must not be present.</li> <li>Mandatory attribute System-Type-Spec_List <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SYS_TYPE_SPEC_LIST</li> <li><input type="checkbox"/> attribute-type = TypeVerList</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes for each configuration supported</li> <li><input type="checkbox"/> attribute-value = {MDC_DEV_SPEC_PROFILE_SABTE, 1} and <ul style="list-style-type: none"> <li>• IF C_AG_OXP_161 THEN {MDC_DEV_SUB_SPEC_PROFILE_CPAP,1}</li> <li>• IF C_AG_OXP_160 THEN {MDC_DEV_SUB_SPEC_PROFILE_CPAP_AUTO,1}</li> <li>• IF C_AG_OXP_159 THEN {MDC_DEV_SUB_SPEC_PROFILE_BPAP,1}</li> </ul> </li> </ul> </li> <li>Mandatory attribute System-model <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_MODEL (0x09 0x28)</li> <li><input type="checkbox"/> attribute-type = SystemModel</li> <li><input type="checkbox"/> attribute-value.length = &lt;Variable&gt;</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>• Manufacturer = Check against PIXIT I_AG_OXP_003</li> <li>• Model = Check against PIXIT I_AG_OXP_004</li> </ul> </li> </ul> </li> <li>Mandatory attribute Dev-Configuration-Id <ul style="list-style-type: none"> <li><input type="checkbox"/> IF NOT C_AG_OXP_181 THEN attribute-value = 0x0960 (2400)</li> <li><input type="checkbox"/> IF C_AG_OXP_181 THEN attribute-value = &lt;between 0x4000 and 0x7FFF &gt;</li> </ul> </li> <li>Mandatory attribute Production-Specification <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PROD_SPECN</li> </ul> </li> </ol> </li> </ol> |                        |                    |                    |
+
+|                           |                                                                                                                          |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> attribute-type = ProductionSpec<br><input type="checkbox"/> attribute-value.length = <Variable> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                               |
+| <b>Notes</b>              |                                                                                                                          |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-000_B                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |  |
+| <b>TP label</b>          | MDS Configuration objects events for SABTE specialization                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-10424] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | MDSEvents 1; M         |  |
+| <b>Test purpose</b>      | Check that:<br>SABTE PHD sends the MDS-Configuration-Event using a Confirmed event report and it includes the event-info ConfigReport                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |  |
+| <b>Other PICS</b>        | C_AG_OXP_010, C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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: <ol style="list-style-type: none"> <li>a. APDU Type <input type="checkbox"/> field- type = PrstApdu <input type="checkbox"/> field-length =2 bytes <input type="checkbox"/> field-value =0xE7 0x00 </li> <li>b. invoke-id <input type="checkbox"/> field- type = InvokeIDType <input type="checkbox"/> field-length =INT-U16 <input type="checkbox"/> field- value =&lt;Not relevant for this test&gt; </li> <li>c. message <input type="checkbox"/> field- type = roiv-cmip-confirmed-event-report <input type="checkbox"/> field-length =two bytes <input type="checkbox"/> field- value =0x01 0x01 (EventReportArgumentSimple) </li> <li>d. obj-handle (EventReportArgumentSimple) <input type="checkbox"/> field- type = HANDLE <input type="checkbox"/> field-length =INT-U16 </li> <li>e. event-time (EventReportArgumentSimple) <input type="checkbox"/> field- type = Relative Time <input type="checkbox"/> field-length =INT-U32 <input type="checkbox"/> field-value = <ul style="list-style-type: none"> <li>• IF NOT C_AG_OXP_010 THEN value = 0xFF 0xFF 0xFF 0xFF</li> </ul> </li> <li>f. event-type (EventReportArgumentSimple)</li> </ol> </li> </ol> |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = OID-Type</li> <li><input type="checkbox"/> field-length =INT-U16</li> <li><input type="checkbox"/> field- value=0x0D 0x1C (MDC_NOTI_CONFIG)</li> </ul> <p>g. config-report-id (ConfigReport)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = ConfigId</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field value = &lt;It matches the tested configuration&gt; <ul style="list-style-type: none"> <li>• IF NOT C_AG_OXP_181 THEN attribute-value = 0x 0960 (2400)</li> <li>• IF C_AG_OXP_181 THEN &lt;between 0x40 0x00 and 0x7F 0xFF &gt; for extended configuration.</li> </ul> </li> </ul> <p>h. obj-class ( ConfigReport → ConfigObjectList (ConfigObject))</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = OID-Type</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field- value = At least one MDC_MOC_VMO_METRIC_NU</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                 |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-000_C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                 |
+| <b>TP label</b>          | MDS objects events for SABTE specialization                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-10424] |                 |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MDSEvents 3; M         | MDSEvents 4; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MDSEvents 6; M         | MDSEvents 7; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MDSEvents 9; M         | MDSEvents 10; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        | ObjAccServ 1; M |
+| <b>Test purpose</b>      | Check that:<br>Agent-initiated mode is supported for measurement data transmission and all types of event reports are used in confirmed or unconfirmed mode<br>[AND]<br>The PHD sends the MDS-Dynamic-Data-Update-Fixed using a confirmed or unconfirmed event report and it includes the event-info ScanReportInfoFixed<br>[OR]<br>The PHD sends the MDS-Dynamic-Data-Update-Var using a confirmed or unconfirmed event report and it includes the event-info ScanReportInfoVar<br>[OR]<br>The PHD sends the MDS-Dynamic-Data-Update-MP-Fixed using a confirmed or unconfirmed event report and it includes the event-info ScanReportInfoMPFixed<br>[OR]<br>The PHD sends the MDS-Dynamic-Data-Update-MP-Var using a confirmed or unconfirmed event report and it includes the event-info ScanReportInfoMPVar |                        |                 |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND (C_AG_OXP_182 OR C_AG_OXP_183 OR C_AG_OXP_184 OR C_AG_OXP_189)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                 |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                 |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Take measurements for every supported object in the PHD under test.</li> <li>2. Wait to receive every event reports and check: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = Event Report</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field- value = 0x01 0x00 (EventReportArgumentSimple, unconfirmed) OR 0x01 0x01 (EventReportArgumentSimple, confirmed)</li> </ol> This field identifies the type of message sent by the PHD for the unconfirmed event configuration, roiv-cmip-event-report, OR for the confirmed event configuration, roiv-cmip-confirmed-event-report. </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | Check that every received report is one of the following confirmed or unconfirmed Data APDU. <ul style="list-style-type: none"> <li>• MDC_NOTI_SCAN_REPORT_FIXED</li> <li>• MDC_NOTI_SCAN_REPORT_MP_FIXED</li> <li>• MDC_NOTI_SCAN_REPORT_VAR</li> <li>• MDC_NOTI_SCAN_REPORT_MP_VAR</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |              |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-001                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |              |
+| <b>TP label</b>          | Objects for SABTE specialization - Standard Configuration (2400)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [ISO/IEEE 11073-10424] |              |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | DPU 1; M               | DFG 1; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | TherMode 1; M          | DevMode 1; M |
+| <b>Test purpose</b>      | Check that:<br><br>Duration of Patient Use Numeric object with Type MDC_SABTE_TIME_PD_USAGE_TOTAL is supported by a SABTE PHD for Standard Configuration 2400 (0x0960).<br>[AND]<br>Duration of Flow Generation Numeric object with Type MDC_SABTE_TIME_PD_FLOW_GEN_TOTAL is supported by a SABTE PHD for Standard Configuration 2400 (0x0960).<br>[AND]<br>Device Mode Set Enumeration object with Type MDC_SABTE_MODE_DEV_SET is supported by a SABTE PHD for Standard Configuration 2400 (0x0960).<br>[AND]<br>Therapy Mode Set Enumeration object with Type MDC_SABTE_MODE_THERAPY_SET is supported by a SABTE PHD for Standard Configuration 2400 (0x0960). |                        |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND (NOT_C_AG_OXP_181)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |              |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> </ol>                                                                                                                                                                                                                                                                               |                        |              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>4. Check that the field Dev-Config-Id is set to 0x0960 (2400); if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</p> <p>5. Once the PHD under test sends a standard configuration, check that:<br/> IF (Dev-Config-Id = 0x0960) THEN Attribute-List:</p> <ol style="list-style-type: none"> <li>attribute-value (ConfigReport → ConfigObjectList (ConfigObject) → Attribute List), this value depends on the attribute Type. The values we have to check are: <ul style="list-style-type: none"> <li><input type="checkbox"/> Duration of Patient Use numeric object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_TIME_PD_USAGE_TOTAL (0x56 0x58)</li> <li><input type="checkbox"/> Duration of Flow Generation numeric object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_TIME_PD_FLOW_GEN_TOTAL (0x56 0x54)</li> <li><input type="checkbox"/> Device Mode Set enumeration object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_MODE_DEV_SET (0x56 0xFC)</li> <li><input type="checkbox"/> Therapy Mode Set enumeration object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_MODE_THERAPY_SET (0x57 0x08)</li> </ul> </li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure and no other object listed.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                     |                                                                                                                                                                                                                                                                                                    |                        |                |               |
+|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------|---------------|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/SABTE/BV-002                                                                                                                                                                                                                                                                      |                        |                |               |
+| <b>TP label</b>     | Objects for SABTE specialization - Extended Configuration                                                                                                                                                                                                                                          |                        |                |               |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-10424] |                |               |
+|                     | <b>Testable items</b>                                                                                                                                                                                                                                                                              | DPU 1; M               | DFG 1; M       | AHI 1; O      |
+|                     |                                                                                                                                                                                                                                                                                                    | CAHI 1; O              | TherPress 1; O | Leak 1; O     |
+|                     |                                                                                                                                                                                                                                                                                                    | RespRate 1; O          | TidalVol 1; O  | RespVol 1; O  |
+|                     |                                                                                                                                                                                                                                                                                                    | IER 1; O               | SnorDur 1; O   | CSR 1; O      |
+|                     |                                                                                                                                                                                                                                                                                                    | HumidLvl 1; O          | RSPS 1; O      | RDS 1; O      |
+|                     |                                                                                                                                                                                                                                                                                                    | PALS 1; O              | PCPAP 1; C     | PminAPAP 1; C |
+|                     |                                                                                                                                                                                                                                                                                                    | PmaxAPAP 1; C          | PIPAP 1; C     | PEPAP 1; C    |
+|                     |                                                                                                                                                                                                                                                                                                    | RespSet 1; O           | IERSet 1; O    | TSS 1; O      |
+|                     |                                                                                                                                                                                                                                                                                                    | IPRS 1; O              | TPWave 1; O    | LeakWave 1; O |
+|                     |                                                                                                                                                                                                                                                                                                    | AirWave 1; O           | CompAn 2; O    | EffAn 2; O    |
+|                     |                                                                                                                                                                                                                                                                                                    | PHDDM 2; O             | DevMode 1; M   | TherMode 1; M |
+|                     |                                                                                                                                                                                                                                                                                                    | AutoSS 2; R            | AutoSS 3; O    | PAFS 2; R     |
+|                     |                                                                                                                                                                                                                                                                                                    | PAFS 3; O              |                |               |
+| <b>Test purpose</b> | Check that:<br>Duration of Patient Use and Duration of Flow Generation Numeric objects are supported by a SABTE PHD.<br>[AND]<br>Apnoea-Hypopnoea Index, Compound Apnoea-Hypopnoea Index, Therapy Pressure, Leakage, Respiratory Rate, Tidal Volume, Respiratory Minute Volume, I:E Ratio, Snoring |                        |                |               |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | <p>Duration, CSR Duration, Humidifier Level Set, Ramp Start Pressure Set, Ramp Duration Set, Pressure Adaption Level Set, P CPAP Set, Pmin APAP Set, Pmax APAP Set, P IPAP Set, P EPAP Set, Respiratory Rate Set, I:E Ratio Set, Trigger Sensitivity Set or Inspiration Pressure Rise Set numeric objects can be implemented by the vendor.</p> <p>[AND]</p> <p>Therapy Pressure Waveform, Leakage Waveform and Airflow Waveform RT-SA objects can be implemented by the vendor.</p> <p>[AND]</p> <p>Device Mode Set and Therapy Mode Set Enumeration objects are supported by a SABTE PHD.</p> <p>[AND]</p> <p>Compliance Annotations, Efficacy Annotations, PHD DM Status, Autostart/-stop Set and Pressure Adaption Freeze Set Enumeration objects can be implemented by the vendor.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Other PICS</b>        | C_AG_SABTE_001, C_AG_SABTE_002, C_AG_SABTE_003, C_AG_SABTE_004, C_AG_SABTE_005, C_SABTE_006, C_AG_SABTE_007, C_AG_SABTE_008, C_AG_SABTE_009, C_AG_SABTE_010, C_AG_SABTE_011, C_AG_SABTE_012, C_AG_SABTE_013, C_AG_SABTE_014, C_AG_SABTE_015, C_SABTE_016, C_AG_SABTE_017, C_AG_SABTE_018, C_AG_SABTE_019, C_AG_SABTE_020, C_AG_SABTE_021, C_AG_SABTE_022, C_AG_SABTE_023, C_AG_SABTE_024, C_AG_SABTE_025, C_SABTE_026, C_AG_SABTE_027, C_AG_SABTE_028, C_AG_SABTE_029, C_AG_SABTE_030, C_AG_SABTE_031, C_AG_OXP_161, C_AG_OXP_160, C_AG_OXP_159                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Initial condition</b> | The simulated PHG and the PHD are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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.</li> <li>5. Once the PHD under test sends an extended configuration, check that:<br/> Attribute-List: <ol style="list-style-type: none"> <li>a. attribute-value( ConfigReport → ConfigObjectList (ConfigObject)→Attribute List), this value depends on the attribute type. The values we have to check are: <ul style="list-style-type: none"> <li>• Duration of Patient Use numeric object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_TIME_PD_USAGE_TOTAL (0x56 0x58)</li> <li>• Duration of Flow Generation numeric object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_TIME_PD_FLOW_GEN_TOTAL (0x56 0x54)</li> <li>• Device Mode Set enumeration object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_MODE_DEV_SET (0x56 0xFC)</li> <li>• Therapy Mode Set enumeration object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_MODE_THERAPY_SET (0x57 0x08)</li> </ul> <input type="checkbox"/> Any of these objects may be present, depending on the profile. <ul style="list-style-type: none"> <li>• IF C_AG_SABTE_001 THEN Apnoea-Hypopnoea Index numeric Object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_AHI_TOTAL (0x56 0xA8) or MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_AHI_UNCLASS (0x56 0xAC) or MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_AHI_OBSTRUC (0x56 0xB0) or MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_AHI_CENT (0x56 0xB4).</li> <li>• IF C_AG_SABTE_002 THEN Compound Apnoea-Hypopnoea Index numeric Object is present → MDC_PART_PHD_DM (0x00 0x80),</li> </ul> </li> </ol> </li> </ol> |
+
+MDC\_SABTE\_AHI (0x56 0xA4).
+
+- IF C\_AG\_SABTE\_003 THEN Therapy Pressure numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_PRESS\_INSTANT (0x57 0x4F) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_PRESS\_MIN (0x57 0x45) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_PRESS\_MAX (0x57 0x46) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_PRESS\_MEAN (0x57 0x47) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_PRESS\_P50 (0x57 0x4B) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_PRESS\_P90 (0x57 0x4D) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_PRESS\_P95 (0x57 0x4E).
+- IF C\_AG\_SABTE\_004 THEN Leakage numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_LEAK\_INSTANT (0x57 0xDB) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_LEAK\_MIN (0x57 0xD1) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_LEAK\_MAX (0x57 0xD2) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_LEAK\_MEAN (0x57 0xD3) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_LEAK\_P50 (0x57 0xD7) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_LEAK\_P90 (0x57 0xD9) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_LEAK\_P95 (0x57 0xDA).
+- IF C\_AG\_SABTE\_005 THEN Respiratory Rate numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_RESP\_RATE\_INSTANT (0x57 0x8B) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_RESP\_RATE\_MIN (0x57 0x81) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_RESP\_RATE\_MAX (0x57 0x82) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_RESP\_RATE\_MEAN (0x57 0x83) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_RESP\_RATE\_P50 (0x57 0x87) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_RESP\_RATE\_P90 (0x57 0x89) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_RESP\_RATE\_P95 (0x57 0x8A).
+- IF C\_AG\_SABTE\_006 THEN Tidal Volume numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_TIDAL\_INSTANT (0x58 0x2B) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_TIDAL\_MIN (0x58 0x21) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_TIDAL\_MAX (0x58 0x22) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_TIDAL\_MEAN (0x58 0x23) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_TIDAL\_P50 (0x58 0x27) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_TIDAL\_P90 (0x58 0x29) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_TIDAL\_P95 (0x58 0x2A).
+- IF C\_AG\_SABTE\_007 THEN Respiratory Minute Volume numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_MINUTE\_INSTANT (0x58 0x03) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_MINUTE\_MIN (0x57 0xF9) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_MINUTE\_MAX (0x57 0xFA) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_MINUTE\_MEAN (0x57 0xFB) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_MINUTE\_P50 (0x57 0xFF) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_MINUTE\_P90 (0x58 0x01) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_VOL\_MINUTE\_P95 (0x58 0x02).
+- IF C\_AG\_SABTE\_008 THEN I:E Ratio numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_RATIO\_IE\_INSTANT (0x57 0xB3) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_RATIO\_IE\_MIN (0x57 0xA9) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_RATIO\_IE\_MAX (0x57 0xAA) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_RATIO\_IE\_MEAN (0x57 0xAB) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_RATIO\_IE\_P50 (0x57 0xAF) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_RATIO\_IE\_P90 (0x57 0xB1) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_RATIO\_IE\_P95 (0x57
+
+0xB2).
+
+- IF C\_AG\_SABTE\_009 THEN Snoring Duration numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_TIME\_PD\_SNORING\_TOTAL (0x56 0x64).
+- IF C\_AG\_SABTE\_010 THEN CSR Duration numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_TIME\_PD\_CSR\_TOTAL (0x56 0x68).
+- IF C\_AG\_SABTE\_011 THEN Humidifier Level Set numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_LVL\_HUMID\_STAGE\_SET (0x56 0xCC) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_LVL\_HUMID\_TEMP\_SET (0x56 0xD0) or MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_LVL\_HUMID\_HUM\_SET (0x56 0xD4).
+- IF C\_AG\_SABTE\_012 THEN Ramp Start Pressure Set numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_PRESS\_RAMP\_START\_SET (0x57 0x7C).
+- IF C\_AG\_SABTE\_013 THEN Ramp Duration Set numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_TIME\_PD\_RAMP\_SET (0x56 0x78).
+- IF C\_AG\_SABTE\_014 THEN Pressure Adaption Level Set numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_LVL\_ADAPT\_SET (0x56 0xE0)
+- IF C\_AG\_OXP\_159 THEN Pressure Adaption Level Set numeric Object is NOT present
+- IF (C\_AG\_SABTE\_015 OR C\_AG\_OXP\_161) THEN P CPAP Set numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_PRESS\_CPAP\_SET (0x57 0x5C)
+- IF (C\_AG\_OXP\_160 OR C\_AG\_OXP\_159) THEN P CPAP Set numeric Object is NOT present
+- IF (C\_AG\_SABTE\_016 OR C\_AG\_OXP\_160) THEN Pmin APAP Set numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_PRESS\_CPAP\_AUTO\_MIN\_SET (0x57 0x60)
+- IF (C\_AG\_OXP\_161 OR C\_AG\_OXP\_159) THEN Pmin APAP Set numeric Object is NOT present
+- IF (C\_AG\_SABTE\_017 OR C\_AG\_OXP\_160) THEN Pmax APAP Set numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_PRESS\_CPAP\_AUTO\_MAX\_SET (0x57 0x64)
+- IF (C\_AG\_OXP\_161 OR C\_AG\_OXP\_159) THEN Pmax APAP Set numeric Object is NOT present
+- IF (C\_AG\_SABTE\_018 OR C\_AG\_OXP\_159) THEN P IPAP Set numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_PRESS\_IPAP\_SET (0x57 0x68)
+- IF (C\_AG\_OXP\_160 OR C\_AG\_OXP\_161) THEN P IPAP Set numeric Object is NOT present
+- IF (C\_AG\_SABTE\_019 OR C\_AG\_OXP\_159) THEN P EPAP Set numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_PRESS\_EPAP\_SET (0x57 0x6C)
+- IF (C\_AG\_OXP\_160 OR C\_AG\_OXP\_161) THEN P EPAP Set numeric Object is NOT present
+- IF C\_AG\_SABTE\_020 THEN Respiratory Rate Set numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_RESP\_RATE\_SET (0x57 0xA4)
+- IF (C\_AG\_OXP\_160 OR C\_AG\_OXP\_161) THEN Respiratory Rate Set numeric Object is NOT present
+- IF C\_AG\_SABTE\_021 THEN I:E Ratio Set numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_SABTE\_RATIO\_IE\_SET (0x57
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>0xCC)</p> <ul style="list-style-type: none"> <li>• IF (C_AG_OXP_160 OR C_AG_OXP_161) THEN I:E Ratio Set numeric Object is NOT present</li> <li>• IF C_AG_SABTE_022 THEN Trigger Sensitivity Set numeric Object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_LVL_TRIG_SENS_SET (0x56 0xD8)</li> <li>• IF (C_AG_OXP_160 OR C_AG_OXP_161) THEN Trigger Sensitivity Set numeric Object is NOT present</li> <li>• IF C_AG_SABTE_023 THEN Inspiration Pressure Rise Set numeric Object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_LVL_INSP_PRESS_RISE_SET (0x56 0xDC)</li> <li>• IF C_AG_OXP_161 THEN Inspiration Pressure Rise Set numeric Object is NOT present</li> <li>• IF C_AG_SABTE_024 THEN Therapy Pressure Waveform RT-SA object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_PRESS (0x57 0x44) or MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_PRESS_TARGET (0x57 0x58).</li> <li>• IF C_AG_SABTE_025 THEN Leakage Waveform RT-SA object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_VOL_LEAK (0x57 0xD0).</li> <li>• IF C_AG_SABTE_026 THEN Airflow Waveform RT-SA object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_FLOW_TOTAL (0x56 0x7C) or MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_FLOW_WO_PURGE (0x56 0x80) or MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_FLOW_RESP (0x56 0x84).</li> <li>• IF C_AG_SABTE_027 THEN Compliance Annotations enumeration object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_PATT_COMPLIANCE_CLS (0x57 0x1C).</li> <li>• IF C_AG_SABTE_028 THEN Efficacy Annotations enumeration object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_PATT_EFFICACY_CLS (0x57 0x24).</li> <li>• IF C_AG_SABTE_029 THEN PHD DM Status enumeration object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_PHD_DM_DEV_STAT (0x4E 0x20).</li> <li>• IF C_AG_SABTE_030 THEN Autostart/-stop Set enumeration object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_MODE_AUTOSTARTSTOP_SET (0x56 0xF8).</li> <li>• IF C_AG_SABTE_031 THEN Pressure Adaption Freeze Set enumeration object is present → MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_MODE_ADAPT_FREEZE_SET (0x56 0xF4)</li> <li>• IF C_AG_OXP_159 THEN Pressure Adaption Freeze Set numeric Object is NOT present</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+|                 |                                                                        |              |              |
+|-----------------|------------------------------------------------------------------------|--------------|--------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/SABTE/BV-003                                          |              |              |
+| <b>TP label</b> | Duration of Patient Use Numeric Object - Standard configuration (2400) |              |              |
+| <b>Coverage</b> | [ISO/IEEE 11073-10424]                                                 |              |              |
+|                 | <b>Spec</b>                                                            |              |              |
+|                 | <b>Testable items</b>                                                  | NumObj 2; M  | NumObj 4; M  |
+|                 |                                                                        | NumObj 6; R  |              |
+|                 |                                                                        | NumObj 8; M  | NumObj 10; R |
+|                 |                                                                        | NumObj 12; R |              |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |              |              |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------|
+|                          | NumObj 14; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | NumObj 16; R | NumObj 18; R |
+|                          | NumObj 20; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | NumObj 22; M | NumObj 24; R |
+|                          | NumObj 26; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | NumObj 28; O | NumObj 30; C |
+|                          | NumObj 32; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | NumObj 34; C | NumObj 36; C |
+|                          | NumObj 38; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | NumObj 40; C | NumObj 42; C |
+|                          | NumObj 44; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | NumObj 46; C | NumObj 48; C |
+|                          | NumObj 50; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | NumObj 52; R |              |
+|                          | DPU 2; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | DPU 4; M     | DPU 6; M     |
+|                          | DPU 8; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | DPU 10; M    | DPU 12; R    |
+|                          | DPU 14; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |              |              |
+| <b>Test purpose</b>      | Check that:<br>The DPU Numeric object contains the attributes specified for Standard Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |              |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND (NOT C_AG_OXP_181)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |              |              |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |              |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |              |              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set to 0x0960 (2400); if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends a standard configuration, check that SABTE Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_HANDLE</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x01</li> </ol> </li> <li>b. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> IF (Dev-Config-Id = 0x0960): <ul style="list-style-type: none"> <li>• attribute-id = MDC_ATTR_ID_TYPE</li> <li>• attribute-type = TYPE</li> <li>• attribute-value = MDC_PART_PHD_DM (0x00 0x80),<br/>MDC_SABTE_TIME_PD_USAGE_TOTAL (0x56 0x58).</li> </ul> </li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 0 (mss-avail-intermittent(0)), must be set</li> <li>• Bit 1 (mss-avail-stored-data(1)), must be set</li> </ul> </li> </ol> </li> </ol> </li> </ol> |              |              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• Bit 2 (mss-upd-aperiodic(2)), must be set</li> <li>• Bit 3 (mss-msmt-aperiodic(3)), must be set</li> <li>• Bit 9 (mss-acc-agent-initiated(9)), must be set</li> <li>• The other bits have to be 0.</li> </ul> <p>d. Mandatory attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_MIN</li> </ul> <p>e. Mandatory attribute Attribute-Value-Map</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = AttrValMap (sequence of attribute-id(OID-Type) and attribute-length( INT-U16) )</li> <li><input type="checkbox"/> attribute-value.length=&lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value= MDC_ATTR_NU_VAL_OBS_BASIC, then MDC_ATTR_TIME_STAMP_BO</li> </ul> <p>f. No other attribute shall be present at configuration.</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|                          |                                                                                                                         |                        |              |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------|------------------------|--------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-004                                                                                           |                        |              |
+| <b>TP label</b>          | Duration of Patient Use Numeric Object - Extended configuration                                                         |                        |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                             | [ISO/IEEE 11073-10424] |              |
+|                          | <b>Testable items</b>                                                                                                   | NumObj 3; M            | NumObj 5; R  |
+|                          |                                                                                                                         | NumObj 9; R            | NumObj 11; R |
+|                          |                                                                                                                         | NumObj 15; C           | NumObj 17; R |
+|                          |                                                                                                                         | NumObj 23; R           | NumObj 31; R |
+|                          |                                                                                                                         | NumObj 45; C           | NumObj 47; C |
+|                          |                                                                                                                         | NumObj 51; R           |              |
+|                          |                                                                                                                         | DPU 5; M               | DPU 7; M     |
+|                          |                                                                                                                         | DPU 13; R              |              |
+| <b>Test purpose</b>      | Check that:<br>The Duration of Patient Use Numeric object contains the attributes specified for Extended Configuration. |                        |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181                                                                          |                        |              |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                |                        |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                 |                        |              |
+| <b>Test procedure</b>    | 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, the PHG responds with an "unsupported-config" and waits for a new configuration.
+4. Once the PHD under test sends an extended configuration, check that Duration of Patient Use Object attributes are:
+
+NOTE – "Mandatory", "Recommended" and "Not Recommended" are attribute types defined in the 11073-20601 Optimized exchange protocol.
+
+#### a. Mandatory attribute Type
+
+- attribute-id = MDC\_ATTR\_ID\_TYPE
+- attribute-type = TYPE
+- attribute-value = MDC\_PART\_PHD\_DM (0x00 0x80) |  
+MDC\_SABTE\_TIME\_PD\_USAGE\_TOTAL (0x56 0x58) or  
+MDC\_PART\_PHD\_DM (0x00 0x80) |  
+MDC\_SABTE\_TIME\_PD\_USAGE\_W\_HUM (0x56 0x5C) or  
+MDC\_PART\_PHD\_DM (0x00 0x80) |  
+MDC\_SABTE\_TIME\_PD\_USAGE\_WO\_HUM (0x56 0x60).
+
+#### b. IF Not Recommended Supplemental-Types attribute is present
+
+- attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+- attribute-type = SupplementalTypeList
+- attribute-value.length =<variable> (Sequence of TYPE (TYPE.length= 4 bytes
+
+#### 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 3 must be set (mss-msmt-aperiodic(3))
+  - Bit 9 must be set (mss-acc-agent-initiated(9))
+
+#### d. IF Not Recommended attribute Metric-Structure-Small is present
+
+- attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+- attribute-type = MetricStructureSmall
+- attribute-value.length = <variable>(Sequence of (ms-struct.length =1byte (INT-U8) + ms-comp-no =1byte(INT-U8)))
+
+#### e. IF Not Recommended attribute Measurement-Status is present
+
+- attribute-id = MDC\_ATTR\_MSMT\_STAT
+- attribute-type = MeasurementStatus (BITS-16)
+- attribute-value.length =2 bytes
+
+#### 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
+
+#### g. IF Not Recommended attribute Metric-Id-List is present
+
+- attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value.length= SEQUENCE OF OID-Type (INT-U16)</li> </ul> <p>h. IF Not Recommended attribute Metric-Id-Partition is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>i. Mandatory attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_MIN</li> </ul> <p>j. IF Not Recommended attribute Source-Handle-Reference is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>k. IF Recommended attribute Base-Offset-Time-Stamp is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> <p>l. IF Not Recommended attribute Measure-Active-Period is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>m. IF Recommended attribute Basic-Nu-Observed-Value is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> <p>n. IF Not Recommended attribute Accuracy is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 byte</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+|                 |                                                                |                        |              |
+|-----------------|----------------------------------------------------------------|------------------------|--------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/SABTE/BV-005                                  |                        |              |
+| <b>TP label</b> | Apnoea-Hypopnoea Index Numeric Object - Extended configuration |                        |              |
+| <b>Coverage</b> | <b>Spec</b>                                                    | [ISO/IEEE 11073-10424] |              |
+|                 | <b>Testable items</b>                                          | NumObj 3; M            | NumObj 5; R  |
+|                 |                                                                | NumObj 9; R            | NumObj 11; R |
+|                 |                                                                |                        | NumObj 7; M  |
+|                 |                                                                |                        | NumObj 13; R |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |              |              |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------|
+|                          | NumObj 15; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 17; R | NumObj 19; M |
+|                          | NumObj 23; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 31; R | NumObj 41; C |
+|                          | NumObj 45; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 47; C | NumObj 49; C |
+|                          | NumObj 51; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |              |              |
+|                          | AHI 2; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | AHI 3; M     | AHI 4; M     |
+|                          | AHI 5; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |              |              |
+| <b>Test purpose</b>      | Check that:<br>The Apnoea-Hypopnoea Index Numeric object contains the attributes specified for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |              |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_001                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |              |              |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |              |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |              |              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that Apnoea-Hypopnoea Index Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_AHI_TOTAL (0x56 0xA8) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_AHI_UNCLASS (0x56 0xAC) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_AHI_OBSTRUC (0x56 0xB0) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_AHI_CENT (0x56 0xB4).</li> </ol> </li> <li>b. IF Not Recommended Supplemental-Types attribute is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> <li>• Bit 14 must be set (mss-cat-calculation(14))</li> </ol> </li> </ol> </li> <li>d. IF Not Recommended attribute Metric-Structure-Small is present</li> </ol> </li> </ol> |              |              |
+
+- attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+- attribute-type = MetricStructureSmall
+- attribute-value.length = <variable>(Sequence of (ms-struct.length = 1byte(INT-U8) + ms-comp-no = 1byte(INT-U8))))
+- e. IF Not Recommended attribute Measurement-Status is present
+  - attribute-id = MDC\_ATTR\_MSMT\_STAT
+  - attribute-type = MeasurementStatus (BITS-16)
+  - attribute-value.length = 2 bytes
+- 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
+- g. IF Not Recommended attribute Metric-Id-List is present
+  - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+  - attribute-type = MetricIdList
+  - attribute-value.length= SEQUENCE OF OID-Type (INT-U16)
+- 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
+- i. 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\_EVT\_PER\_HR
+- 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
+- k. IF Recommended attribute Base-Offset-Time-Stamp is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+  - attribute-type = BaseOffsetTime
+  - attribute-value.length = 8 bytes
+- l. IF Not Recommended attribute Measure-Active-Period is present
+  - attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE
+  - attribute-type = FLOAT type
+  - attribute-value.length = 4 bytes
+- m. IF Recommended attribute Basic-Nu-Observed-Value is present
+  - attribute-id = MDC\_ATTR\_NU\_VAL\_OBS\_BASIC
+  - attribute-type = BasicNuObsValue
+  - attribute-value.length = SFLOAT-Type (INT-U16)
+- n. IF Not Recommended attribute Accuracy is present
+  - attribute-id = MDC\_ATTR\_NU\_ACCUR\_MSMT
+
+|                           |                                                                                                                            |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)<br><input type="checkbox"/> attribute-value.length = 4 byte |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                 |
+| <b>Notes</b>              |                                                                                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |              |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-006                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |              |
+| <b>TP label</b>          | Compound Apnoea-Hypopnoea Index Numeric Object - Extended configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [ISO/IEEE 11073-10424] |              |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 3; M            | NumObj 5; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | NumObj 9; R            | NumObj 11; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | NumObj 15; C           | NumObj 17; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | NumObj 23; R           | NumObj 31; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | NumObj 45; C           | NumObj 47; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | NumObj 51; R           |              |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | CAHI 2; M              | CAHI 3; M    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | CAHI 5; M              | CAHI 6; R    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | CAHI 8; R              | CAHI 9; R    |
+| <b>Test purpose</b>      | Check that:<br><br>The Compound Apnoea-Hypopnoea Index Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |              |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that Compound Apnoea-Hypopnoea Index Object attributes are:               <ol style="list-style-type: none"> <li>a. Mandatory attribute Type                   <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_AHI (0x56 0xA4).</li> </ul> </li> <li>b. IF Not Recommended Supplemental-Types attribute is present                   <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> </ul> </li> </ol> </li> </ol> |                        |              |
+
+attribute-value.length =<variable> (Sequence of TYPE (TYPE.length= 4 bytes
+
+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))
+
+- Bit 14 must be set (mss-cat-calculation(14))
+
+d. IF Not Recommended attribute Metric-Structure-Small is present
+
+attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+
+attribute-type = MetricStructureSmall
+
+attribute-value.length = <variable>(Sequence of (ms-struct.length = 1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))
+
+e. IF Not Recommended attribute Measurement-Status is present
+
+attribute-id = MDC\_ATTR\_MSMT\_STAT
+
+attribute-type = MeasurementStatus (BITS-16)
+
+attribute-value.length =2 bytes
+
+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
+
+g. Mandatory attribute Metric-Id-List
+
+attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+
+attribute-type = MetricIdList
+
+attribute-value.length= SEQUENCE OF OID-Type (INT-U16)
+
+attribute-value = MDC\_SABTE\_AHI\_UNCLASS, then MDC\_SABTE\_AHI\_OBSTRUC, then MDC\_SABTE\_AHI\_CENTRAL.
+
+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
+
+i. 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\_EVT\_PER\_HR
+
+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
+
+k. IF Recommended attribute Base-Offset-Time-Stamp is present
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> l. IF Not Recommended attribute Measure-Active-Period is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> m. IF Not Recommended attribute Simple-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_SIMP</li> <li><input type="checkbox"/> attribute-type = SimpleNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> n. IF Not Recommended attribute Basic-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> o. IF Recommended attribute Compound-Basic-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> p. IF Not Recommended attribute Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS</li> <li><input type="checkbox"/> attribute-type = NuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> q. IF Not Recommended attribute Accuracy is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 byte</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+|                 |                       |                                                          |              |              |
+|-----------------|-----------------------|----------------------------------------------------------|--------------|--------------|
+| <b>TP Id</b>    |                       | TP/PLT/PHD/CLASS/SABTE/BV-007                            |              |              |
+| <b>TP label</b> |                       | Therapy Pressure Numeric Object - Extended configuration |              |              |
+| <b>Coverage</b> | <b>Spec</b>           | [ISO/IEEE 11073-10424]                                   |              |              |
+|                 | <b>Testable items</b> | NumObj 3; M                                              | NumObj 5; R  | NumObj 7; M  |
+|                 |                       | NumObj 9; R                                              | NumObj 11; R | NumObj 13; R |
+|                 |                       | NumObj 15; C                                             | NumObj 17; R | NumObj 19; M |
+|                 |                       | NumObj 23; R                                             | NumObj 31; R | NumObj 41; C |
+|                 |                       | NumObj 45; C                                             | NumObj 47; C | NumObj 49; C |
+|                 |                       | NumObj 51; R                                             |              |              |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                |                |                |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------------|----------------|
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | TherPress 2; M | TherPress 3; M | TherPress 4; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | TherPress 5; M |                |                |
+| <b>Test purpose</b>      | Check that:<br>The Therapy Pressure Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                |                |                |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                |                |                |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                |                |                |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                |                |                |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that Therapy Pressure Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_PRESS_INSTANT (0x57 0x4F) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_PRESS_MIN (0x57 0x45) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_PRESS_MAX (0x57 0x46) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_PRESS_MEAN (0x57 0x47) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_PRESS_P50 (0x57 0x4B) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_PRESS_P90 (0x57 0x4D) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_PRESS_P95 (0x57 0x4E)</li> </ol> </li> <li>b. IF Not Recommended Supplemental-Types attribute is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes)</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 3 must be set (mss-msmt-aperiodic(3))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> </ol> </li> </ol> </li> <li>d. IF Not Recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =</li> </ol> </li> </ol> </li> </ol> |                |                |                |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>1byte(INT-U8) + ms-comp-no = 1byte(INT-U8)))</p> <ul style="list-style-type: none"> <li>e. IF Not Recommended attribute Measurement-Status is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>f. IF Not Recommended attribute Metric-Id is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length= 2 bytes</li> </ul> </li> <li>g. IF Not Recommended attribute Metric-Id-List is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIST</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value.length= SEQUENCE OF OID-Type (INT-U16)</li> </ul> </li> <li>h. IF Not Recommended attribute Metric-Id-Partition is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>i. Mandatory attribute Unit-Code <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_HECTO_PASCAL</li> </ul> </li> <li>j. IF Not Recommended attribute Source-Handle-Reference is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>k. IF Recommended attribute Base-Offset-Time-Stamp is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> </li> <li>l. IF Not Recommended attribute Measure-Active-Period is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> <li>m. IF Recommended attribute Basic-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> </li> <li>n. IF Not Recommended attribute Accuracy is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|              |  |
+|--------------|--|
+| <b>Notes</b> |  |
+|--------------|--|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |              |              |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------|--------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-008                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |              |              |
+| <b>TP label</b>          | Leakage Numeric Object - Extended configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |              |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-10424] |              |              |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | NumObj 3; M            | NumObj 5; R  | NumObj 7; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 9; R            | NumObj 11; R | NumObj 13; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 15; C           | NumObj 17; R | NumObj 19; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 23; R           | NumObj 31; R | NumObj 41; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 45; C           | NumObj 47; C | NumObj 49; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 51; R           |              |              |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Leak 2; M              | Leak 3; M    | Leak 4; M    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Leak 5; M              |              |              |
+| <b>Test purpose</b>      | Check that:<br>The Leakage Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |              |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |              |              |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |              |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |              |              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that Leakage Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_LEAK_INSTANT (0x57 0xDB) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_LEAK_MIN (0x57 0xD1) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_LEAK_MAX (0x57 0xD2) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_LEAK_MEAN (0x57 0xD3) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_LEAK_P50 (0x57 0xD7) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_LEAK_P90 (0x57 0xD9) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_LEAK_P95 (0x57 0xDA).</li> </ul> </li> <li>b. IF Not Recommended Supplemental-Types attribute is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes)</li> </ul> </li> </ol> </li> </ol> |                        |              |              |
+
+- 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  $\neq$  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))
+- d. IF Not Recommended attribute Metric-Structure-Small is present
+  - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+  - attribute-type = MetricStructureSmall
+  - attribute-value.length = <variable>(Sequence of (ms-struct.length = 1byte(INT-U8) + ms-comp-no = 1byte(INT-U8))))
+- e. IF Not Recommended attribute Measurement-Status is present
+  - attribute-id = MDC\_ATTR\_MSMT\_STAT
+  - attribute-type = MeasurementStatus (BITS-16)
+  - attribute-value.length = 2 bytes
+- 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
+- g. IF Not Recommended attribute Metric-Id-List is present
+  - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+  - attribute-type = MetricIdList
+  - attribute-value.length = SEQUENCE OF OID-Type (INT-U16)
+- 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
+- i. 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\_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
+- k. IF Recommended attribute Base-Offset-Time-Stamp is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+  - attribute-type = BaseOffsetTime
+  - attribute-value.length = 8 bytes
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>l. IF Not Recommended attribute Measure-Active-Period is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>m. IF Recommended attribute Basic-Nu-Observed-Value is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> <p>n. IF Not Recommended attribute Accuracy is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                                                                                              |                                                                                              |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-009                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                                                                                              |                                                                                              |
+| <b>TP label</b>          | Respiratory Rate Numeric Object - Extended configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                                                                                              |                                                                                              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-10424]                                                                                                       |                                                                                              |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | NumObj 3; M<br>NumObj 9; R<br>NumObj 15; C<br>NumObj 23; R<br>NumObj 45; C<br>NumObj 51; R<br>RespRate 2; M<br>RespRate 5; R | NumObj 5; R<br>NumObj 11; R<br>NumObj 17; R<br>NumObj 31; R<br>NumObj 47; C                  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                                                                                              | NumObj 7; M<br>NumObj 13; R<br>NumObj 19; M<br>NumObj 41; C<br>NumObj 49; C<br>RespRate 3; M |
+| <b>Test purpose</b>      | Check that:<br>The Respiratory Rate Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                                                                                              |                                                                                              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_005                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                                                                                                              |                                                                                              |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                                                                                              |                                                                                              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                                                                                              |                                                                                              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration</li> <li>4. Once the PHD under test sends an extended configuration, check that Respiratory Rate</li> </ol> |                                                                                                                              |                                                                                              |
+
+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\_SABTE\_RESP\_RATE\_INSTANT (0x57 0x8B) or MDC\_PART\_PHD\_DM  
+(0x00 0x80) | MDC\_SABTE\_RESP\_RATE\_MIN (0x57 0x81) or  
+MDC\_PART\_PHD\_DM (0x00 0x80) | MDC\_SABTE\_RESP\_RATE\_MAX (0x57  
+0x82) or MDC\_PART\_PHD\_DM (0x00 0x80) |  
+MDC\_SABTE\_RESP\_RATE\_MEAN (0x57 0x83) or MDC\_PART\_PHD\_DM  
+(0x00 0x80) | MDC\_SABTE\_RESP\_RATE\_P50 (0x57 0x87) or  
+MDC\_PART\_PHD\_DM (0x00 0x80) | MDC\_SABTE\_RESP\_RATE\_P90 (0x57  
+0x89) or MDC\_PART\_PHD\_DM (0x00 0x80) | MDC\_SABTE\_RESP\_RATE\_P95  
+(0x57 0x8A)
+
+#### b. IF Not Recommended Supplemental-Types attribute is present
+
+- attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+- attribute-type = SupplementalTypeList
+- attribute-value.length =<variable> (Sequence of TYPE (TYPE.length= 4 bytes
+
+#### 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 3 must be set (mss-msmt-aperiodic(3))
+  - Bit 9 must be set (mss-acc-agent-initiated(9))
+
+#### d. IF Not Recommended attribute Metric-Structure-Small is present
+
+- attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+- attribute-type = MetricStructureSmall
+- attribute-value.length = <variable>(Sequence of (ms-struct.length =  
+1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))
+
+#### e. IF Not Recommended attribute Measurement-Status is present
+
+- attribute-id = MDC\_ATTR\_MSMT\_STAT
+- attribute-type = MeasurementStatus (BITS-16)
+- attribute-value.length =2 bytes
+
+#### 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
+
+#### g. IF Not Recommended attribute Metric-Id-List is present
+
+- attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+- attribute-type = MetricIdList
+- attribute-value.length= SEQUENCE OF OID-Type (INT-U16)
+
+#### h. IF Not Recommended attribute Metric-Id-Partition is present
+
+- attribute-id = MDC\_ATTR\_METRIC\_ID\_PART
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li>i. Mandatory attribute Unit-Code <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_RESP_PER_MIN</li> </ul> </li> <li>j. IF Not Recommended attribute Source-Handle-Reference is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>k. IF Recommended attribute Base-Offset-Time-Stamp is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> </li> <li>l. IF Not Recommended attribute Measure-Active-Period is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> <li>m. IF Recommended attribute Basic-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> </li> <li>n. IF Not Recommended attribute Accuracy is present is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                 |                                                      |                        |              |              |
+|-----------------|------------------------------------------------------|------------------------|--------------|--------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/SABTE/BV-010                        |                        |              |              |
+| <b>TP label</b> | Tidal Volume Numeric Object - Extended configuration |                        |              |              |
+| <b>Coverage</b> | <b>Spec</b>                                          | [ISO/IEEE 11073-10424] |              |              |
+|                 | <b>Testable items</b>                                | NumObj 3; M            | NumObj 5; R  | NumObj 7; M  |
+|                 |                                                      | NumObj 9; R            | NumObj 11; R | NumObj 13; R |
+|                 |                                                      | NumObj 15; C           | NumObj 17; R | NumObj 19; M |
+|                 |                                                      | NumObj 23; R           | NumObj 31; R | NumObj 41; C |
+|                 |                                                      | NumObj 45; C           | NumObj 47; C | NumObj 49; C |
+|                 |                                                      | NumObj 51; R           |              |              |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |               |               |               |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|---------------|
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | TidalVol 2; M | TidalVol 3; M | TidalVol 4; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | TidalVol 5; R |               |               |
+| <b>Test purpose</b>      | Check that:<br>The Tidal Volume Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |               |               |               |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_006                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |               |               |               |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |               |               |               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |               |               |               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that Tidal Volume Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_TIDAL_INSTANT (0x58 0x2B) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_TIDAL_MIN (0x58 0x21) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_TIDAL_MAX (0x58 0x22) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_TIDAL_MEAN (0x58 0x23) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_TIDAL_P50 (0x58 0x27) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_TIDAL_P90 (0x58 0x29) or MDC_PART_PHD_DM (0x00 0x80)</li> </ol> </li> <li>b. IF Not Recommended Supplemental-Types attribute is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes)</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 3 must be set (mss-msmt-aperiodic(3))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> </ol> </li> </ol> </li> <li>d. IF Not Recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))</li> </ol> </li> </ol> </li> </ol> |               |               |               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>e. IF Not Recommended attribute Measurement-Status is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>f. IF Not Recommended attribute Metric-Id is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length= 2 bytes</li> </ul> <p>g. IF Not Recommended attribute Metric-Id-List is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIST</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value.length= SEQUENCE OF OID-Type (INT-U16)</li> </ul> <p>h. IF Not Recommended attribute Metric-Id-Partition is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>i. Mandatory attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_MILLI_L</li> </ul> <p>j. IF Not Recommended attribute Source-Handle-Reference is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>k. IF Recommended attribute Base-Offset-Time-Stamp is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> <p>l. IF Not Recommended attribute Measure-Active-Period is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>m. IF Recommended attribute Basic-Nu-Observed-Value is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> <p>n. IF Not Recommended attribute Accuracy is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |              |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-011                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |              |
+| <b>TP label</b>          | Respiratory Minute Volume Numeric Object - Extended configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-10424] |              |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | NumObj 3; M            | NumObj 5; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 9; R            | NumObj 11; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 15; C           | NumObj 17; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 23; R           | NumObj 31; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 45; C           | NumObj 47; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 51; R           |              |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | RespVol 2; M           | RespVol 3; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | RespVol 5; R           |              |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The Respiratory Minute Volume Numeric object contains the attributes specified for Extended Configuration.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_007                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |              |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that Respiratory Minute Volume Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_MINUTE_INSTANT (0x58 0x03) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_MINUTE_MIN (0x57 0xF9) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_MINUTE_MAX (0x57 0xFA) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_MINUTE_MEAN (0x57 0xFB) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_MINUTE_P50 (0x57 0xFF) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_MINUTE_P90 (0x58 0x01) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_VOL_MINUTE_P95 (0x58 0x02)</li> </ul> </li> <li>b. IF Not Recommended Supplemental-Types attribute is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small</li> </ol> </li> </ol> |                        |              |
+
+- attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL
+- attribute-type = MetricSpecSmall (BITS-16)
+- attribute-value.length = 2 bytes
+- attribute-value  $\neq$  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))
+
+d. IF Not Recommended attribute Metric-Structure-Small is present
+
+- attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+- attribute-type = MetricStructureSmall
+- attribute-value.length = <variable>(Sequence of (ms-struct.length = 1byte(INT-U8) + ms-comp-no = 1byte(INT-U8))))
+
+e. IF Not Recommended attribute Measurement-Status is present
+
+- attribute-id = MDC\_ATTR\_MSMT\_STAT
+- attribute-type = MeasurementStatus (BITS-16)
+- attribute-value.length = 2 bytes
+
+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
+
+g. IF Not Recommended attribute Metric-Id-List is present
+
+- attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+- attribute-type = MetricIdList
+- attribute-value.length = SEQUENCE OF OID-Type (INT-U16)
+
+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
+
+i. 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\_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
+
+k. IF Recommended attribute Base-Offset-Time-Stamp is present
+
+- attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+- attribute-type = BaseOffsetTime
+- attribute-value.length = 8 bytes
+
+l. IF Not Recommended attribute Measure-Active-Period is present
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> m. IF Recommended attribute Basic-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> n. IF Not Recommended attribute Accuracy is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |              |              |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------|--------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |              |              |
+| <b>TP label</b>          | I:E Ratio Numeric Object - Extended configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |              |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-10424] |              |              |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | NumObj 3; M            | NumObj 5; R  | NumObj 7; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | NumObj 9; R            | NumObj 11; R | NumObj 13; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | NumObj 15; C           | NumObj 17; R | NumObj 19; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | NumObj 23; R           | NumObj 31; R | NumObj 41; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | NumObj 45; C           | NumObj 47; C | NumObj 49; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | NumObj 51; R           |              |              |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | IER 2; M               | IER 3; M     | IER 4; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | IER 5; R               |              |              |
+| <b>Test purpose</b>      | Check that:<br>The I:E Ratio Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |              |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_008                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |              |              |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |              |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |              |              |
+| <b>Test procedure</b>    | 1. The simulated PHG receives an association request from the PHD under test.<br>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.<br>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.<br>4. Once the PHD under test sends an extended configuration, check that I:E Ratio Object attributes are:<br>a. Mandatory attribute Type |                        |              |              |
+
+- attribute-id = MDC\_ATTR\_ID\_TYPE
+- attribute-type = TYPE
+- attribute-value = MDC\_PART\_PHD\_DM (0x00 0x80) | MDC\_SABTE\_RATIO\_IE\_INSTANT (0x57 0xB3) or MDC\_PART\_PHD\_DM (0x00 0x80) | MDC\_SABTE\_RATIO\_IE\_MIN (0x57 0xA9) or MDC\_PART\_PHD\_DM (0x00 0x80) | MDC\_SABTE\_RATIO\_IE\_MAX (0x57 0xAA) or MDC\_PART\_PHD\_DM (0x00 0x80) | MDC\_SABTE\_RATIO\_IE\_MEAN (0x57 0xAB) or MDC\_PART\_PHD\_DM (0x00 0x80) | MDC\_SABTE\_RATIO\_IE\_P50 (0x57 0xAF) or MDC\_PART\_PHD\_DM (0x00 0x80) | MDC\_SABTE\_RATIO\_IE\_P90 (0x57 0xB1) or MDC\_PART\_PHD\_DM (0x00 0x80) | MDC\_SABTE\_RATIO\_IE\_P95 (0x57 0xB2)
+
+#### b. IF Not Recommended Supplemental-Types attribute is present
+
+- attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+- attribute-type = SupplementalTypeList
+- attribute-value.length =<variable> (Sequence of TYPE (TYPE.length= 4 bytes
+
+#### 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))
+  - Bit 14 must be set (mss-cat-calculation(14))
+
+#### d. IF Not Recommended attribute Metric-Structure-Small is present
+
+- attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+- attribute-type = MetricStructureSmall
+- attribute-value.length = <variable>(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))
+
+#### e. IF Not Recommended attribute Measurement-Status is present
+
+- attribute-id = MDC\_ATTR\_MSMT\_STAT
+- attribute-type = MeasurementStatus (BITS-16)
+- attribute-value.length =2 bytes
+
+#### 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
+
+#### g. IF Not Recommended attribute Metric-Id-List is present
+
+- attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+- attribute-type = MetricIdList
+- attribute-value.length= SEQUENCE OF OID-Type (INT-U16)
+
+#### 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
+
+#### i. Mandatory attribute Unit-Code
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_PERCENT</li> <li style="margin-left: -20px;">j. IF Not Recommended attribute Source-Handle-Reference is present</li> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li style="margin-left: -20px;">k. IF Recommended attribute Base-Offset-Time-Stamp is present</li> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> <li style="margin-left: -20px;">l. IF Not Recommended attribute Measure-Active-Period is present</li> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li style="margin-left: -20px;">m. IF Recommended attribute Basic-Nu-Observed-Value is present</li> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> <li style="margin-left: -20px;">n. IF Not Recommended attribute Accuracy is present</li> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+|                     |                                                          |                        |              |              |
+|---------------------|----------------------------------------------------------|------------------------|--------------|--------------|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/SABTE/BV-013                            |                        |              |              |
+| <b>TP label</b>     | Snoring Duration Numeric Object - Extended configuration |                        |              |              |
+| <b>Coverage</b>     | <b>Spec</b>                                              | [ISO/IEEE 11073-10424] |              |              |
+|                     | <b>Testable items</b>                                    | NumObj 3; M            | NumObj 5; R  | NumObj 7; M  |
+|                     |                                                          | NumObj 9; R            | NumObj 11; R | NumObj 13; R |
+|                     |                                                          | NumObj 15; C           | NumObj 17; R | NumObj 19; M |
+|                     |                                                          | NumObj 23; R           | NumObj 31; R | NumObj 41; C |
+|                     |                                                          | NumObj 45; C           | NumObj 47; C | NumObj 49; C |
+|                     |                                                          | NumObj 51; R           |              |              |
+|                     |                                                          | SnorDur 2; M           | SnorDur 3; M | SnorDur 4; M |
+|                     |                                                          | SnorDur 5; R           |              |              |
+| <b>Test purpose</b> | Check that:                                              |                        |              |              |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | The Snoring Duration Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_009                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that Snoring Duration Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80),<br/>MDC_SABTE_TIME_PD_SNORING_TOTAL (0x56 0x64)</li> </ol> </li> <li>b. IF Not Recommended Supplemental-Types attribute is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes)</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> <li>• Bit 14 must be set (mss-cat-calculation(14))</li> </ol> </li> </ol> </li> <li>d. IF Not Recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8))))</li> </ol> </li> <li>e. IF Not Recommended attribute Measurement-Status is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> </ol> </li> <li>f. IF Not Recommended attribute Metric-Id is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length= 2 bytes</li> </ol> </li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>g. IF Not Recommended attribute Metric-Id-List is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIST</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value.length= SEQUENCE OF OID-Type (INT-U16)</li> </ul> <p>h. IF Not Recommended attribute Metric-Id-Partition is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>i. Mandatory attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_MIN</li> </ul> <p>j. IF Not Recommended attribute Source-Handle-Reference is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>k. IF Recommended attribute Base-Offset-Time-Stamp is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> <p>l. IF Not Recommended attribute Measure-Active-Period is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>m. IF Recommended attribute Basic-Nu-Observed-Value is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> <p>n. IF Not Recommended attribute Accuracy is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                 |                                                      |                        |              |
+|-----------------|------------------------------------------------------|------------------------|--------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/SABTE/BV-014                        |                        |              |
+| <b>TP label</b> | CSR Duration Numeric Object - Extended configuration |                        |              |
+| <b>Coverage</b> | <b>Spec</b>                                          | [ISO/IEEE 11073-10424] |              |
+|                 | <b>Testable items</b>                                | NumObj 3; M            | NumObj 5; R  |
+|                 |                                                      | NumObj 9; R            | NumObj 11; R |
+|                 |                                                      |                        | NumObj 7; M  |
+|                 |                                                      |                        | NumObj 13; R |
+
+|                          |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |              |              |
+|--------------------------|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------|
+|                          |  | NumObj 15; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | NumObj 17; R | NumObj 19; M |
+|                          |  | NumObj 23; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | NumObj 31; R | NumObj 41; C |
+|                          |  | NumObj 45; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | NumObj 47; C | NumObj 49; C |
+|                          |  | NumObj 51; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |              |              |
+|                          |  | CSR 2; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | CSR 3; M     | CSR 4; M     |
+|                          |  | CSR 5; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |              |              |
+| <b>Test purpose</b>      |  | Check that:<br>The CSR Duration Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |              |              |
+| <b>Applicability</b>     |  | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_010                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |              |              |
+| <b>Other PICS</b>        |  | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |              |              |
+| <b>Initial condition</b> |  | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |              |              |
+| <b>Test procedure</b>    |  | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that CSR Duration Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80),<br/>MDC_SABTE_TIME_PD_CSR_TOTAL (0x56 0x68)</li> </ol> </li> <li>b. IF Not Recommended Supplemental-Types attribute is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> <li>• Bit 14 must be set (mss-cat-calculation(14))</li> </ul> </li> </ol> </li> <li>d. IF Not Recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> </ol> </li> </ol> </li> </ol> |              |              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p style="margin-left: 40px;"><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))</p> <p>e. IF Not Recommended attribute Measurement-Status is present</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-type = MeasurementStatus (BITS-16)</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-value.length =2 bytes</p> <p>f. IF Not Recommended attribute Metric-Id is present</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-value.length= 2 bytes</p> <p>g. IF Not Recommended attribute Metric-Id-List is present</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIST</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-type = MetricIdList</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-value.length= SEQUENCE OF OID-Type (INT-U16)</p> <p>h. IF Not Recommended attribute Metric-Id-Partition is present</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-value.length = 2 bytes</p> <p>i. Mandatory attribute Unit-Code</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-value.length = 2 bytes</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-value= MDC_DIM_MIN</p> <p>j. IF Not Recommended attribute Source-Handle-Reference is present</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-value.length = 2 bytes</p> <p>k. IF Recommended attribute Base-Offset-Time-Stamp is present</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-type = BaseOffsetTime</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-value.length = 8 bytes</p> <p>l. IF Not Recommended attribute Measure-Active-Period is present</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-type = FLOAT type</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-value.length = 4 bytes</p> <p>m. IF Recommended attribute Basic-Nu-Observed-Value is present</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-type = BasicNuObsValue</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</p> <p>n. IF Not Recommended attribute Accuracy is present</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</p> <p style="margin-left: 40px;"><input type="checkbox"/> attribute-value.length = 4 bytes</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|              |  |
+|--------------|--|
+| <b>Notes</b> |  |
+|--------------|--|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |              |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-015                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |              |
+| <b>TP label</b>          | Duration of Flow Generation Numeric Object - Standard configuration (2400)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [ISO/IEEE 11073-10424] |              |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | NumObj 2; M            | NumObj 4; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | NumObj 8; M            | NumObj 10; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | NumObj 14; R           | NumObj 16; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | NumObj 20; M           | NumObj 22; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | NumObj 26; O           | NumObj 28; O |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | NumObj 32; R           | NumObj 34; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | NumObj 38; R           | NumObj 40; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | NumObj 44; C           | NumObj 46; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | NumObj 50; C           | NumObj 52; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | DFG 2; M               | DFG 4; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | DFG 8; M               | DFG 10; M    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | DFG 14; M              |              |
+| <b>Test purpose</b>      | Check that:<br>The Duration of Flow Generation Numeric object contains the attributes specified for Standard Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND (NOT C_AG_OXP_181)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |              |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set to 0x0960 (2400); if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends a standard configuration, check that Duration of Flow Generation Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_HANDLE</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x02</li> </ul> </li> <li>b. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> IF (Dev-Config-Id = 0x0960): <ul style="list-style-type: none"> <li>• attribute-id = MDC_ATTR_ID_TYPE</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                        |              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• attribute-type = TYPE</li> <li>• attribute-value = MDC_PART_PHD_DM (0x00 0x80),<br/>MDC_SABTE_TIME_PD_FLOW_GEN_TOTAL (0x56 0x54).</li> </ul> <p>c. Mandatory attribute Metric-Spec-Small</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00</li> <ul style="list-style-type: none"> <li>• Bit 0 (mss-avail-intermittent(0)), must be set</li> <li>• Bit 1 (mss-avail-stored-data(1)), must be set</li> <li>• Bit 2 (mss-upd-aperiodic(2)), must be set</li> <li>• Bit 3 (mss-msmt-aperiodic(3)), must be set</li> <li>• Bit 9 (mss-acc-agent-initiated(9)), must be set</li> <li>• The other bits have to be 0.</li> </ul> </ul> <p>d. Mandatory attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_MIN</li> </ul> <p>e. Mandatory attribute Attribute-Value-Map</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = AttrValMap (sequence of attribute-id(OID-Type) and attribute-length( INT-U16) )</li> <li><input type="checkbox"/> attribute-value.length=&lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value= MDC_ATTR_NU_VAL_OBS_SIMP, then<br/>MDC_ATTR_TIME_STAMP_BO</li> </ul> <p>f. No other attribute shall be present at configuration.</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                 |                                                                     |                        |              |
+|-----------------|---------------------------------------------------------------------|------------------------|--------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/SABTE/BV-016                                       |                        |              |
+| <b>TP label</b> | Duration of Flow Generation Numeric Object - Extended configuration |                        |              |
+| <b>Coverage</b> | <b>Spec</b>                                                         | [ISO/IEEE 11073-10424] |              |
+|                 | <b>Testable items</b>                                               | NumObj 3; M            | NumObj 5; R  |
+|                 |                                                                     | NumObj 9; R            | NumObj 11; R |
+|                 |                                                                     | NumObj 15; C           | NumObj 17; R |
+|                 |                                                                     | NumObj 23; R           | NumObj 31; R |
+|                 |                                                                     | NumObj 45; C           | NumObj 47; C |
+|                 |                                                                     | NumObj 51; R           |              |
+|                 |                                                                     | DFG 5; M               | DFG 7; M     |
+|                 |                                                                     |                        | DFG 9; M     |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |           |  |  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|--|--|
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | DFG 13; R |  |  |
+| <b>Test purpose</b>      | Check that:<br>The Duration of Flow Generation Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |           |  |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |           |  |  |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |           |  |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |           |  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that Duration of Flow Generation Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80),<br/>MDC_SABTE_TIME_PD_FLOW_GEN_TOTAL (0x56 0x54)</li> </ol> </li> <li>b. IF Not Recommended Supplemental-Types attribute is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 2 must be set (mss-msmt-aperiodic(3))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> </ol> </li> </ol> </li> <li>d. IF Not Recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))</li> </ol> </li> <li>e. IF Not Recommended attribute Measurement-Status is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> </ol> </li> <li>f. IF Not Recommended attribute Metric-Id is present</li> </ol> </li> </ol> |           |  |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length= 2 bytes</li> </ul> <p>g. IF Not Recommended attribute Metric-Id-List is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIST</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value.length= SEQUENCE OF OID-Type (INT-U16)</li> </ul> <p>h. IF Not Recommended attribute Metric-Id-Partition is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>i. Mandatory attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_MIN</li> </ul> <p>j. IF Not Recommended attribute Source-Handle-Reference is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>k. IF Recommended attribute Base-Offset-Time-Stamp is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> <p>l. IF Not Recommended attribute Measure-Active-Period is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>m. IF Recommended attribute Simple-Nu-Observed-Value is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_SIMP</li> <li><input type="checkbox"/> attribute-type = SimpleNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>n. IF Not Recommended attribute Accuracy is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |               |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-017                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |               |
+| <b>TP label</b>          | Humidifier Level Set Numeric Object - Extended configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-10424] |               |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | NumObj 3; M            | NumObj 5; R   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 9; R            | NumObj 11; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 15; C           | NumObj 17; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 23; R           | NumObj 31; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 45; C           | NumObj 47; C  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 51; R           |               |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | HumidLvl 2; M          | HumidLvl 3; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | HumidLvl 5; R          | HumidLvl 6; M |
+| <b>Test purpose</b>      | Check that:<br>The Humidifier Level Set Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |               |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_011                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |               |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that Humidifier Level Set Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_LVL_HUMID_STAGE_SET (0x56 0xCC) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_LVL_HUMID_TEMP_SET (0x56 0xD0) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_LVL_HUMID_HUM_SET (0x56 0xD4)</li> </ul> </li> <li>b. IF Not Recommended Supplemental-Types attribute is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> </ol> </li> </ol> |                        |               |
+
+- attribute-value  $\neq$  0x00 0x00
+    - 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))
+    - Bit 13 must be set (mss-cat-setting(13))
+- d. IF Not Recommended attribute Metric-Structure-Small is present
+  - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+  - attribute-type = MetricStructureSmall
+  - attribute-value.length = <variable>(Sequence of (ms-struct.length = 1byte(INT-U8) + ms-comp-no = 1byte(INT-U8)))
+- e. IF Not Recommended attribute Measurement-Status is present
+  - attribute-id = MDC\_ATTR\_MSMT\_STAT
+  - attribute-type = MeasurementStatus (BITS-16)
+  - attribute-value.length = 2 bytes
+- 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
+- g. IF Not Recommended attribute Metric-Id-List is present
+  - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+  - attribute-type = MetricIdList
+  - attribute-value.length = SEQUENCE OF OID-Type (INT-U16)
+- 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
+- i. 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
+- 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
+- k. IF Recommended attribute Base-Offset-Time-Stamp is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+  - attribute-type = BaseOffsetTime
+  - attribute-value.length = 8 bytes
+- l. IF Not Recommended attribute Measure-Active-Period is present
+  - attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE
+  - attribute-type = FLOAT type
+  - attribute-value.length = 4 bytes
+- m. IF Recommended attribute Basic-Nu-Observed-Value is present
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC<br><input type="checkbox"/> attribute-type = BasicNuObsValue<br><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)<br><input type="checkbox"/> attribute-value = between 0 and 100.<br>n. IF Not Recommended attribute Accuracy is present<br><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT<br><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)<br><input type="checkbox"/> attribute-value.length = 4 bytes |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |              |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-018                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |              |
+| <b>TP label</b>          | Ramp Start Pressure Set Numeric Object - Extended configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-10424] |              |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | NumObj 3; M            | NumObj 5; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 9; R            | NumObj 11; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 15; C           | NumObj 17; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 23; R           | NumObj 31; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 45; C           | NumObj 47; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 51; R           |              |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | RSPS 2; M              | RSPS 3; M    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | RSPS 5; R              |              |
+| <b>Test purpose</b>      | Check that:<br>The Ramp Start Pressure Set Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |              |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |              |
+| <b>Test procedure</b>    | 1. The simulated PHG receives an association request from the PHD under test.<br>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.<br>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.<br>4. Once the PHD under test sends an extended configuration, check that Ramp Start Pressure Set Object attributes are:<br>a. Mandatory attribute Type<br><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE<br><input type="checkbox"/> attribute-type = TYPE |                        |              |
+
+- attribute-value = MDC\_PART\_PHD\_DM (0x00 0x80),  
+MDC\_SABTE\_PRESS\_RAMP\_START\_SET (0x57 0x7C)
+- b. IF Not Recommended Supplemental-Types attribute is present
+  - attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+  - attribute-type = SupplementalTypeList
+  - attribute-value.length =<variable> (Sequence of TYPE (TYPE.length= 4 bytes
+- 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  $\neq$  0x00 0x00
+    - 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))
+    - Bit 13 must be set (mss-cat-setting(13))
+- d. IF Not Recommended attribute Metric-Structure-Small is present
+  - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+  - attribute-type = MetricStructureSmall
+  - attribute-value.length = <variable>(Sequence of (ms-struct.length  
+=1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))
+- e. IF Not Recommended attribute Measurement-Status is present
+  - attribute-id = MDC\_ATTR\_MSMT\_STAT
+  - attribute-type = MeasurementStatus (BITS-16)
+  - attribute-value.length =2 bytes
+- 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
+- g. IF Not Recommended attribute Metric-Id-List is present
+  - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+  - attribute-type = MetricIdList
+  - attribute-value.length= SEQUENCE OF OID-Type (INT-U16)
+- 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
+- i. 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\_HECTO\_PASCAL
+- j. IF Not Recommended attribute Source-Handle-Reference is present
+  - attribute-id = MDC\_ATTR\_SOURCE\_HANDLE\_REF
+  - attribute-type = HANDLE (INT-U16)
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li>k. IF Recommended attribute Base-Offset-Time-Stamp is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> </li> <li>l. IF Not Recommended attribute Measure-Active-Period is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> <li>m. IF Recommended attribute Basic-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> </li> <li>n. IF Not Recommended attribute Accuracy is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+|                          |                                                                                                                   |                                                                                            |                                                                             |                                                                             |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|-----------------------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-019                                                                                     |                                                                                            |                                                                             |                                                                             |
+| <b>TP label</b>          | Ramp Duration Set Numeric Object - Extended configuration                                                         |                                                                                            |                                                                             |                                                                             |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                       | [ISO/IEEE 11073-10424]                                                                     |                                                                             |                                                                             |
+|                          | <b>Testable items</b>                                                                                             | NumObj 3; M<br>NumObj 9; R<br>NumObj 15; C<br>NumObj 23; R<br>NumObj 45; C<br>NumObj 51; R | NumObj 5; R<br>NumObj 11; R<br>NumObj 17; R<br>NumObj 31; R<br>NumObj 47; C | NumObj 7; M<br>NumObj 13; R<br>NumObj 19; M<br>NumObj 41; C<br>NumObj 49; C |
+|                          |                                                                                                                   | RDS 2; M<br>RDS 5; R                                                                       | RDS 3; M                                                                    | RDS 4; M                                                                    |
+| <b>Test purpose</b>      | Check that:<br>The Ramp Duration Set Numeric object contains the attributes specified for Extended Configuration. |                                                                                            |                                                                             |                                                                             |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_013                                                 |                                                                                            |                                                                             |                                                                             |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                          |                                                                                            |                                                                             |                                                                             |
+| <b>Initial condition</b> | 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, the PHG responds with an "unsupported-config" and waits for a new configuration.
+4. Once the PHD under test sends an extended configuration, check that Ramp Duration Set 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\_SABTE\_TIME\_PD\_RAMP\_SET (0x56 0x78)
+  - b. IF Not Recommended Supplemental-Types attribute is present
+    - attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+    - attribute-type = SupplementalTypeList
+    - attribute-value.length =<variable> (Sequence of TYPE (TYPE.length= 4 bytes)
+  - 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 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))
+      - Bit 13 must be set (mss-cat-setting(13))
+  - d. IF Not Recommended attribute Metric-Structure-Small is present
+    - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+    - attribute-type = MetricStructureSmall
+    - attribute-value.length = <variable>(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))
+  - e. IF Not Recommended attribute Measurement-Status is present
+    - attribute-id = MDC\_ATTR\_MSMT\_STAT
+    - attribute-type = MeasurementStatus (BITS-16)
+    - attribute-value.length =2 bytes
+  - 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
+  - g. IF Not Recommended attribute Metric-Id-List is present
+    - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+    - attribute-type = MetricIdList
+    - attribute-value.length= SEQUENCE OF OID-Type (INT-U16)
+  - h. IF Not Recommended attribute Metric-Id-Partition is present
+    - attribute-id = MDC\_ATTR\_METRIC\_ID\_PART
+    - attribute-type = NomPartition (INT-U16)
+
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                            |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|
+| <ul style="list-style-type: none"> <li style="margin-left: 40px;"><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li>i. Mandatory attribute Unit-Code <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_MIN</li> </ul> </li> <li>j. IF Not Recommended attribute Source-Handle-Reference is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>k. IF Recommended attribute Base-Offset-Time-Stamp is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> </li> <li>l. IF Not Recommended attribute Measure-Active-Period is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> <li>m. IF Recommended attribute Basic-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> </li> <li>n. IF Not Recommended attribute Accuracy is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> </ul> |                                                            |
+| <b>Pass/Fail criteria</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | All checked values are as specified in the test procedure. |
+| <b>Notes</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                            |
+
+|                 |                                                                     |                        |              |              |
+|-----------------|---------------------------------------------------------------------|------------------------|--------------|--------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/SABTE/BV-020                                       |                        |              |              |
+| <b>TP label</b> | Pressure Adaption Level Set Numeric Object - Extended configuration |                        |              |              |
+| <b>Coverage</b> | <b>Spec</b>                                                         | [ISO/IEEE 11073-10424] |              |              |
+|                 | <b>Testable items</b>                                               | NumObj 3; M            | NumObj 5; R  | NumObj 7; M  |
+|                 |                                                                     | NumObj 9; R            | NumObj 11; R | NumObj 13; R |
+|                 |                                                                     | NumObj 15; C           | NumObj 17; R | NumObj 19; M |
+|                 |                                                                     | NumObj 23; R           | NumObj 31; R | NumObj 41; C |
+|                 |                                                                     | NumObj 45; C           | NumObj 47; C | NumObj 49; C |
+|                 |                                                                     | NumObj 51; R           |              |              |
+|                 |                                                                     | PALS 2; M              | PALS 3; M    | PALS 4; M    |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |           |           |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|--|
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | PALS 5; R | PALS 6; M |  |
+| <b>Test purpose</b>      | Check that:<br>The Pressure Adaption Level Set Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |           |           |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_014                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |           |           |  |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |           |           |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |           |           |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that Pressure Adaption Level Set Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80), MDC_SABTE_LVL_ADAPT_SET (0x56 0xE0)</li> </ol> </li> <li>b. IF Not Recommended Supplemental-Types attribute is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes)</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> <li>• Bit 13 must be set (mss-cat-setting(13))</li> </ol> </li> </ol> </li> <li>d. IF Not Recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))</li> </ol> </li> <li>e. IF Not Recommended attribute Measurement-Status is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> </ol> </li> <li>f. IF Not Recommended attribute Metric-Id is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> </ol> </li> </ol> </li> </ol> |           |           |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length= 2 bytes</li> <li>g. IF Not Recommended attribute Metric-Id-List is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIST</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value.length= SEQUENCE OF OID-Type (INT-U16)</li> </ul> </li> <li>h. IF Not Recommended attribute Metric-Id-Partition is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>i. Mandatory attribute Unit-Code <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_PERCENT</li> </ul> </li> <li>j. IF Not Recommended attribute Source-Handle-Reference is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>k. IF Recommended attribute Base-Offset-Time-Stamp is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> </li> <li>l. IF Not Recommended attribute Measure-Active-Period is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> <li>m. IF Recommended attribute Basic-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value = between 0 and 100</li> </ul> </li> <li>n. IF Not Recommended attribute Accuracy is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                 |                                                    |                        |
+|-----------------|----------------------------------------------------|------------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/SABTE/BV-021                      |                        |
+| <b>TP label</b> | P CPAP Set Numeric Object - Extended configuration |                        |
+| <b>Coverage</b> | <b>Spec</b>                                        | [ISO/IEEE 11073-10424] |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |              |              |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------|
+| <b>Testable items</b>    | NumObj 3; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | NumObj 5; R  | NumObj 7; M  |
+|                          | NumObj 9; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | NumObj 11; R | NumObj 13; R |
+|                          | NumObj 15; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 17; R | NumObj 19; M |
+|                          | NumObj 23; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 31; R | NumObj 41; C |
+|                          | NumObj 45; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 47; C | NumObj 49; C |
+|                          | NumObj 51; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |              |              |
+|                          | PCPAP 2; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | PCPAP 3; M   | PCPAP 4; M   |
+|                          | PCPAP 5; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |              |              |
+| <b>Test purpose</b>      | Check that:<br>The P CPAP Set Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |              |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_015                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |              |              |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |              |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |              |              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that P CPAP Set Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_PRESS_CPAP_SET (0x57 0x5C)</li> </ol> </li> <li>b. IF Not Recommended Supplemental-Types attribute is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> <li>• Bit 13 must be set (mss-cat-setting(13))</li> </ol> </li> </ol> </li> <li>d. IF Not Recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> </ol> </li> </ol> </li> </ol> |              |              |
+
+- attribute-type = MetricStructureSmall
+- attribute-value.length = <variable>(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8))))
+- e. IF Not Recommended attribute Measurement-Status is present
+  - attribute-id = MDC\_ATTR\_MSMT\_STAT
+  - attribute-type = MeasurementStatus (BITS-16)
+  - attribute-value.length =2 bytes
+- 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
+- g. IF Not Recommended attribute Metric-Id-List is present
+  - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+  - attribute-type = MetricIdList
+  - attribute-value.length= SEQUENCE OF OID-Type (INT-U16)
+- 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
+- i. 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\_HECTO\_PASCAL
+- 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
+- k. IF Recommended attribute Base-Offset-Time-Stamp is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+  - attribute-type = BaseOffsetTime
+  - attribute-value.length = 8 bytes
+- l. IF Not Recommended attribute Measure-Active-Period is present
+  - attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE
+  - attribute-type = FLOAT type
+  - attribute-value.length = 4 bytes
+- m. IF Recommended attribute Basic-Nu-Observed-Value is present
+  - attribute-id = MDC\_ATTR\_NU\_VAL\_OBS\_BASIC
+  - attribute-type = BasicNuObsValue
+  - attribute-value.length = SFLOAT-Type (INT-U16)
+- n. 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
+
+|                           |                                                            |
+|---------------------------|------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure. |
+| <b>Notes</b>              |                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |               |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-022                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |               |
+| <b>TP label</b>          | Pmin APAP Set Numeric Object - Extended configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [ISO/IEEE 11073-10424] |               |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | NumObj 3; M            | NumObj 5; R   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | NumObj 9; R            | NumObj 11; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | NumObj 15; C           | NumObj 17; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | NumObj 23; R           | NumObj 31; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | NumObj 45; C           | NumObj 47; C  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | NumObj 51; R           |               |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | PminAPAP 2; M          | PminAPAP 3; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | PminAPAP 5; R          |               |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The Pmin APAP Set Numeric object contains the attributes specified for Extended Configuration.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |               |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_016                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |               |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that Pmin APAP Set Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_PRESS_CPAP_AUTO_MIN_SET (0x57 0x60)</li> </ul> </li> <li>b. IF Not Recommended Supplemental-Types attribute is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes)</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> </ul> </li> </ol> </li> </ol> |                        |               |
+
+attribute-value.length = 2 bytes
+
+attribute-value  $\neq$  0x00 0x00
+
+- 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))
+- Bit 13 must be set (mss-cat-setting(13))
+
+d. IF Not Recommended attribute Metric-Structure-Small is present
+
+attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+
+attribute-type = MetricStructureSmall
+
+attribute-value.length = <variable>(Sequence of (ms-struct.length = 1byte(INT-U8) + ms-comp-no = 1byte(INT-U8))))
+
+e. IF Not Recommended attribute Measurement-Status is present
+
+attribute-id = MDC\_ATTR\_MSMT\_STAT
+
+attribute-type = MeasurementStatus (BITS-16)
+
+attribute-value.length = 2 bytes
+
+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
+
+g. IF Not Recommended attribute Metric-Id-List is present
+
+attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+
+attribute-type = MetricIdList
+
+attribute-value.length = SEQUENCE OF OID-Type (INT-U16)
+
+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
+
+i. 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\_HECTO\_PASCAL
+
+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
+
+k. IF Recommended attribute Base-Offset-Time-Stamp is present
+
+attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+
+attribute-type = BaseOffsetTime
+
+attribute-value.length = 8 bytes
+
+l. IF Not Recommended attribute Measure-Active-Period is present
+
+attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE
+
+attribute-type = FLOAT type
+
+attribute-value.length = 4 bytes
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>m. IF Recommended attribute Basic-Nu-Observed-Value is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> <p>n. IF Not Recommended attribute Accuracy is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |               |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-023                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |               |
+| <b>TP label</b>          | Pmax APAP Set Numeric Object - Extended configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-10424] |               |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | NumObj 3; M            | NumObj 5; R   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 9; R            | NumObj 11; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 15; C           | NumObj 17; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 23; R           | NumObj 31; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 45; C           | NumObj 47; C  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | NumObj 51; R           |               |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | PmaxAPAP 2; M          | PmaxAPAP 3; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | PmaxAPAP 5; R          |               |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The Pmax APAP Set Numeric object contains the attributes specified for Extended Configuration.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |               |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_017                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |               |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that Pmax APAP Set Object attributes are: <ul style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> </ul> </li> </ul> </li> </ol> |                        |               |
+
+- attribute-value = MDC\_PART\_PHD\_DM (0x00 0x80) |  
+MDC\_SABTE\_PRESS\_CPAP\_AUTO\_MAX\_SET (0x57 0x64)
+- b. IF Not Recommended Supplemental-Types attribute is present
+  - attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+  - attribute-type = SupplementalTypeList
+  - attribute-value.length =<variable> (Sequence of TYPE (TYPE.length= 4 bytes
+- 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  $\neq$  0x00 0x00
+    - 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))
+    - Bit 13 must be set (mss-cat-setting(13))
+- d. IF Not Recommended attribute Metric-Structure-Small is present
+  - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+  - attribute-type = MetricStructureSmall
+  - attribute-value.length = <variable>(Sequence of (ms-struct.length  
+=1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))
+- e. IF Not Recommended attribute Measurement-Status is present
+  - attribute-id = MDC\_ATTR\_MSMT\_STAT
+  - attribute-type = MeasurementStatus (BITS-16)
+  - attribute-value.length =2 bytes
+- 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
+- g. IF Not Recommended attribute Metric-Id-List is present
+  - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+  - attribute-type = MetricIdList
+  - attribute-value.length= SEQUENCE OF OID-Type (INT-U16)
+- 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
+- i. 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\_HECTO\_PASCAL
+- j. IF Not Recommended attribute Source-Handle-Reference is present
+  - attribute-id = MDC\_ATTR\_SOURCE\_HANDLE\_REF
+  - attribute-type = HANDLE (INT-U16)
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li>k. IF Recommended attribute Base-Offset-Time-Stamp is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> </li> <li>l. IF Not Recommended attribute Measure-Active-Period is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> <li>m. IF Recommended attribute Basic-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> </li> <li>n. IF Not Recommended attribute Accuracy is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+|                          |                                                                                                            |                        |              |              |
+|--------------------------|------------------------------------------------------------------------------------------------------------|------------------------|--------------|--------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-024                                                                              |                        |              |              |
+| <b>TP label</b>          | P IPAP Set Numeric Object - Extended configuration                                                         |                        |              |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                | [ISO/IEEE 11073-10424] |              |              |
+|                          | <b>Testable items</b>                                                                                      | NumObj 3; M            | NumObj 5; R  | NumObj 7; M  |
+|                          |                                                                                                            | NumObj 9; R            | NumObj 11; R | NumObj 13; R |
+|                          |                                                                                                            | NumObj 15; C           | NumObj 17; R | NumObj 19; M |
+|                          |                                                                                                            | NumObj 23; R           | NumObj 31; R | NumObj 41; C |
+|                          |                                                                                                            | NumObj 45; C           | NumObj 47; C | NumObj 49; C |
+|                          |                                                                                                            | NumObj 51; R           |              |              |
+|                          |                                                                                                            | PIPAP 2; M             | PIPAP 3; M   | PIPAP 4; M   |
+|                          |                                                                                                            | PIPAP 5; R             |              |              |
+| <b>Test purpose</b>      | Check that:<br>The P IPAP Set Numeric object contains the attributes specified for Extended Configuration. |                        |              |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_018                                          |                        |              |              |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                   |                        |              |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                    |                        |              |              |
+| <b>Test procedure</b>    | 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, the PHG responds with an "unsupported-config" and waits for a new configuration.
+4. Once the PHD under test sends an extended configuration, check that P IPAP Set 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\_SABTE\_PRESS\_IPAP\_SET (0x57 0x68)
+  - b. IF Not Recommended Supplemental-Types attribute is present
+    - attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+    - attribute-type = SupplementalTypeList
+    - attribute-value.length =<variable> (Sequence of TYPE (TYPE.length= 4 bytes)
+  - 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 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))
+      - Bit 13 must be set (mss-cat-setting(13))
+  - d. IF Not Recommended attribute Metric-Structure-Small is present
+    - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+    - attribute-type = MetricStructureSmall
+    - attribute-value.length = <variable>(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))
+  - e. IF Not Recommended attribute Measurement-Status is present
+    - attribute-id = MDC\_ATTR\_MSMT\_STAT
+    - attribute-type = MeasurementStatus (BITS-16)
+    - attribute-value.length =2 bytes
+  - 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
+  - g. IF Not Recommended attribute Metric-Id-List is present
+    - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+    - attribute-type = MetricIdList
+    - attribute-value.length= SEQUENCE OF OID-Type (INT-U16)
+  - 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
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>i. Mandatory attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_HECTO_PASCAL</li> </ul> <p>j. IF Not Recommended attribute Source-Handle-Reference is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>k. IF Recommended attribute Base-Offset-Time-Stamp is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> <p>l. IF Not Recommended attribute Measure-Active-Period is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>m. IF Recommended attribute Basic-Nu-Observed-Value is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> <p>n. IF Not Recommended attribute Accuracy is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+|                 |                                                    |                        |              |
+|-----------------|----------------------------------------------------|------------------------|--------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/SABTE/BV-025                      |                        |              |
+| <b>TP label</b> | P EPAP Set Numeric Object - Extended configuration |                        |              |
+| <b>Coverage</b> | <b>Spec</b>                                        | [ISO/IEEE 11073-10424] |              |
+|                 | <b>Testable items</b>                              |                        |              |
+|                 |                                                    | NumObj 3; M            | NumObj 5; R  |
+|                 |                                                    | NumObj 9; R            | NumObj 11; R |
+|                 |                                                    | NumObj 15; C           | NumObj 17; R |
+|                 |                                                    | NumObj 23; R           | NumObj 31; R |
+|                 |                                                    | NumObj 45; C           | NumObj 47; C |
+|                 |                                                    | NumObj 51; R           |              |
+|                 |                                                    | PEPAP 2; M             | PEPAP 3; M   |
+|                 |                                                    | PEPAP 5; R             |              |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>      | Check that:<br>The P EPAP Set Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_019                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that P EPAP Set Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80)  <br/>MDC_SABTE_PRESS_EPAP_SET (0x57 0x6C)</li> </ol> </li> <li>b. IF Not Recommended Supplemental-Types attribute is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> <li>• Bit 13 must be set (mss-cat-setting(13))</li> </ul> </li> </ol> </li> <li>d. IF Not Recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))</li> </ol> </li> <li>e. IF Not Recommended attribute Measurement-Status is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> </ol> </li> <li>f. IF Not Recommended attribute Metric-Id is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length= 2 bytes</li> </ol> </li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>g. IF Not Recommended attribute Metric-Id-List is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIST</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value.length= SEQUENCE OF OID-Type (INT-U16)</li> </ul> <p>h. IF Not Recommended attribute Metric-Id-Partition is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>i. Mandatory attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_HECTO_PASCAL</li> </ul> <p>j. IF Not Recommended attribute Source-Handle-Reference is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>k. IF Recommended attribute Base-Offset-Time-Stamp is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> <p>l. IF Not Recommended attribute Measure-Active-Period is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>m. IF Recommended attribute Basic-Nu-Observed-Value is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> <p>n. IF Not Recommended attribute Accuracy is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                 |                                                              |                        |              |
+|-----------------|--------------------------------------------------------------|------------------------|--------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/SABTE/BV-026                                |                        |              |
+| <b>TP label</b> | Respiratory Rate Set Numeric Object - Extended configuration |                        |              |
+| <b>Coverage</b> | <b>Spec</b>                                                  | [ISO/IEEE 11073-10424] |              |
+|                 | <b>Testable items</b>                                        | NumObj 3; M            | NumObj 5; R  |
+|                 |                                                              | NumObj 9; R            | NumObj 11; R |
+|                 |                                                              |                        | NumObj 7; M  |
+|                 |                                                              |                        | NumObj 13; R |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |              |              |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------|
+|                          | NumObj 15; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | NumObj 17; R | NumObj 19; M |
+|                          | NumObj 23; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | NumObj 31; R | NumObj 41; C |
+|                          | NumObj 45; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | NumObj 47; C | NumObj 49; C |
+|                          | NumObj 51; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |              |              |
+|                          | RespSet 2; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | RespSet 3; M | RespSet 4; M |
+|                          | RespSet 5; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |              |              |
+| <b>Test purpose</b>      | Check that:<br>The Respiratory Rate Set Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |              |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_020                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |              |              |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |              |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |              |              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that Respiratory Rate Set Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_RESP_RATE_SET (0x57 0xA4)</li> </ol> </li> <li>b. IF Not Recommended Supplemental-Types attribute is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> <li>• Bit 13 must be set (mss-cat-setting(13))</li> </ol> </li> </ol> </li> <li>d. IF Not Recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))</li> </ol> </li> </ol> </li> </ol> |              |              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>e. IF Not Recommended attribute Measurement-Status is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>f. IF Not Recommended attribute Metric-Id is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length= 2 bytes</li> </ul> <p>g. IF Not Recommended attribute Metric-Id-List is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIST</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value.length= SEQUENCE OF OID-Type (INT-U16)</li> </ul> <p>h. IF Not Recommended attribute Metric-Id-Partition is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>i. Mandatory attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_RESP_PER_MIN</li> </ul> <p>j. IF Not Recommended attribute Source-Handle-Reference is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>k. IF Recommended attribute Base-Offset-Time-Stamp is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> <p>l. IF Not Recommended attribute Measure-Active-Period is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>m. IF Recommended attribute Basic-Nu-Observed-Value is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> <p>n. IF Not Recommended attribute Accuracy is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |              |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-027                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |              |
+| <b>TP label</b>          | I:E Ratio Set Numeric Object - Extended configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-10424] |              |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | NumObj 3; M            | NumObj 5; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 9; R            | NumObj 11; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 15; C           | NumObj 17; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 23; R           | NumObj 31; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 45; C           | NumObj 47; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | NumObj 51; R           |              |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | IERSet 2; M            | IERSet 3; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | IERSet 5; R            |              |
+| <b>Test purpose</b>      | Check that:<br>The I:E Ratio Set Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_021                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |              |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that I:E Ratio Set Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_RATIO_IE_SET (0x57 0xCC)</li> </ul> </li> <li>b. IF Not Recommended Supplemental-Types attribute is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes)</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                        |              |
+
+- Bit 2 must be set (mss-upd-aperiodic(2))
+- Bit 9 must be set (mss-acc-agent-initiated(9))
+- Bit 13 must be set (mss-cat-setting(13))
+
+- d. IF Not Recommended attribute Metric-Structure-Small is present
+- attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+  - attribute-type = MetricStructureSmall
+  - attribute-value.length = <variable>(Sequence of (ms-struct.length = 1byte(INT-U8) + ms-comp-no = 1byte(INT-U8))))
+- e. IF Not Recommended attribute Measurement-Status is present
+- attribute-id = MDC\_ATTR\_MSMT\_STAT
+  - attribute-type = MeasurementStatus (BITS-16)
+  - attribute-value.length = 2 bytes
+- 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
+- g. IF Not Recommended attribute Metric-Id-List is present
+- attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+  - attribute-type = MetricIdList
+  - attribute-value.length = SEQUENCE OF OID-Type (INT-U16)
+- 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
+- i. 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
+- 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
+- k. IF Recommended attribute Base-Offset-Time-Stamp is present
+- attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+  - attribute-type = BaseOffsetTime
+  - attribute-value.length = 8 bytes
+- l. IF Not Recommended attribute Measure-Active-Period is present
+- attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE
+  - attribute-type = FLOAT type
+  - attribute-value.length = 4 bytes
+- m. IF Recommended attribute Basic-Nu-Observed-Value is present
+- attribute-id = MDC\_ATTR\_NU\_VAL\_OBS\_BASIC
+  - attribute-type = BasicNuObsValue
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li style="text-indent: 40px;"><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> <li style="text-indent: 10px;">n. IF Not Recommended attribute Accuracy is present</li> <li style="text-indent: 40px;"><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li style="text-indent: 40px;"><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li style="text-indent: 40px;"><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |              |              |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------|--------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-028                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |              |              |
+| <b>TP label</b>          | Trigger Sensitivity Set Numeric Object - Extended configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |              |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-10424] |              |              |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | NumObj 3; M            | NumObj 5; R  | NumObj 7; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | NumObj 9; R            | NumObj 11; R | NumObj 13; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | NumObj 15; C           | NumObj 17; R | NumObj 19; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | NumObj 23; R           | NumObj 31; R | NumObj 41; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | NumObj 45; C           | NumObj 47; C | NumObj 49; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | NumObj 51; R           |              |              |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | TSS 2; M               | TSS 3; M     | TSS 4; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | TSS 5; R               | TSS 6; M     |              |
+| <b>Test purpose</b>      | Check that:<br>The Trigger Sensitivity Set Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |              |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_022                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |              |              |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |              |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |              |              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that Trigger Sensitivity Set Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_LVL_TRIG_SENS_SET (0x56 0xD8)</li> </ul> </li> <li>b. IF Not Recommended Supplemental-Types attribute is present</li> </ol> </li> </ol> |                        |              |              |
+
+- attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+- attribute-type = SupplementalTypeList
+- attribute-value.length =<variable> (Sequence of TYPE (TYPE.length= 4 bytes
+
+#### 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 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))
+  - Bit 13 must be set (mss-cat-setting(13))
+
+#### d. IF Not Recommended attribute Metric-Structure-Small is present
+
+- attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+- attribute-type = MetricStructureSmall
+- attribute-value.length = <variable>(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))
+
+#### e. IF Not Recommended attribute Measurement-Status is present
+
+- attribute-id = MDC\_ATTR\_MSMT\_STAT
+- attribute-type = MeasurementStatus (BITS-16)
+- attribute-value.length =2 bytes
+
+#### 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
+
+#### g. IF Not Recommended attribute Metric-Id-List is present
+
+- attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+- attribute-type = MetricIdList
+- attribute-value.length= SEQUENCE OF OID-Type (INT-U16)
+
+#### 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
+
+#### i. 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
+
+#### 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
+
+#### k. IF Recommended attribute Base-Offset-Time-Stamp is present
+
+- attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> l. IF Not Recommended attribute Measure-Active-Period is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> m. IF Recommended attribute Basic-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value = between 0 and 100</li> </ul> n. IF Not Recommended attribute Accuracy is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|                          |                                                                                                                                                                                                                                                    |                        |              |              |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------|--------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-029                                                                                                                                                                                                                      |                        |              |              |
+| <b>TP label</b>          | Inspiration Pressure Rise Set Numeric Object - Extended configuration                                                                                                                                                                              |                        |              |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                        | [ISO/IEEE 11073-10424] |              |              |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                              | NumObj 3; M            | NumObj 5; R  | NumObj 7; M  |
+|                          |                                                                                                                                                                                                                                                    | NumObj 9; R            | NumObj 11; R | NumObj 13; R |
+|                          |                                                                                                                                                                                                                                                    | NumObj 15; C           | NumObj 17; R | NumObj 19; M |
+|                          |                                                                                                                                                                                                                                                    | NumObj 23; R           | NumObj 31; R | NumObj 41; C |
+|                          |                                                                                                                                                                                                                                                    | NumObj 45; C           | NumObj 47; C | NumObj 49; C |
+|                          |                                                                                                                                                                                                                                                    | NumObj 51; R           |              |              |
+|                          |                                                                                                                                                                                                                                                    | IPRS 2; M              | IPRS 3; M    | IPRS 4; M    |
+|                          |                                                                                                                                                                                                                                                    | IPRS 5; R              | IPRS 6; M    |              |
+| <b>Test purpose</b>      | Check that:<br>The Inspiration Pressure Rise Set Numeric object contains the attributes specified for Extended Configuration.                                                                                                                      |                        |              |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_023                                                                                                                                                                                  |                        |              |              |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                           |                        |              |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                            |                        |              |              |
+| <b>Test procedure</b>    | 1. The simulated PHG receives an association request from the PHD under test.<br>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, the PHG responds with an "unsupported-config" and waits for a new configuration.
+4. Once the PHD under test sends an extended configuration, check that Inspiration Pressure Rise Set 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\_SABTE\_LVL\_INSP\_PRESS\_RISE\_SET (0x56 0xDC)
+  - b. IF Not Recommended Supplemental-Types attribute is present
+    - attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+    - attribute-type = SupplementalTypeList
+    - attribute-value.length =<variable> (Sequence of TYPE (TYPE.length= 4 bytes)
+  - 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 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))
+      - Bit 13 must be set (mss-cat-setting(13))
+  - d. IF Not Recommended attribute Metric-Structure-Small is present
+    - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+    - attribute-type = MetricStructureSmall
+    - attribute-value.length = <variable>(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))
+  - e. IF Not Recommended attribute Measurement-Status is present
+    - attribute-id = MDC\_ATTR\_MSMT\_STAT
+    - attribute-type = MeasurementStatus (BITS-16)
+    - attribute-value.length =2 bytes
+  - 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
+  - g. IF Not Recommended attribute Metric-Id-List is present
+    - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+    - attribute-type = MetricIdList
+    - attribute-value.length= SEQUENCE OF OID-Type (INT-U16)
+  - 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
+  - i. Mandatory attribute Unit-Code
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_PERCENT</li> </ul> j. IF Not Recommended attribute Source-Handle-Reference is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> k. IF Recommended attribute Base-Offset-Time-Stamp is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> l. IF Not Recommended attribute Measure-Active-Period is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> m. IF Recommended attribute Basic-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value = between 0 and 100</li> </ul> n. IF Not Recommended attribute Accuracy is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|                     |                                                                   |                                                                                                                    |               |               |
+|---------------------|-------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|---------------|---------------|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/SABTE/BV-030                                     |                                                                                                                    |               |               |
+| <b>TP label</b>     | Therapy Pressure Waveform RT-SA Object for Extended Configuration |                                                                                                                    |               |               |
+| <b>Coverage</b>     | <b>Spec</b>                                                       | [ISO/IEEE 11073-10424]                                                                                             |               |               |
+|                     | <b>Testable items</b>                                             | RTSAObj2; M                                                                                                        | RTSAObj 3; R  | RTSAObj 4; M  |
+|                     |                                                                   | RTSAObj 5; R                                                                                                       | RTSAObj 6; R  | RTSAObj 7; R  |
+|                     |                                                                   | RTSAObj 8; R                                                                                                       | RTSAObj 9; M  | RTSAObj 11; R |
+|                     |                                                                   | RTSAObj 15; R                                                                                                      | RTSAObj 19; M | RTSAObj 20; M |
+|                     |                                                                   | RTSAObj 21; M                                                                                                      | RTSAObj 22; M | TPWave 2; M   |
+|                     |                                                                   | TPWave 3; M                                                                                                        |               |               |
+| <b>Test purpose</b> |                                                                   | Check that:<br>Therapy Pressure Waveform RT-SA Object contains the attributes specified for Extended Configuration |               |               |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_024                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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.</li> <li>5. Once the PHD under test sends the tested configuration, check Therapy Pressure waveform object: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE <ol style="list-style-type: none"> <li>▪ attribute-value = MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_PRESS (0x57 0x44) or MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_PRESS_TARGET (0x57 0x58)</li> </ol> </li> </ol> </li> <li>b. IF Not Recommended attribute Supplemental-Types is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute.value.length= Sequence of TYPE (TYPE.length= 4 bytes)</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (2 bytes)</li> <li><input type="checkbox"/> attribute-value = 0x00 0x00</li> </ol> </li> <li>d. IF Recommended attribute Measurement-Status is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>e. IF Not Recommended attribute Metric-Id is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>f. IF Not Recommended attribute Metric-Id-List is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIS</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li>g. IF Not Recommended attribute Metric-Id-Partition is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition(INT-U16)</li> </ol> </li> </ol> </li> </ol> |
+
+- attribute-value.length = 2 bytes
+  - attribute-value = <Not relevant for this test>
+  - h. Mandatory attribute Unit-Code
+    - attribute-id = MDC\_ATTR\_UNIT\_CODE
+    - attribute-type = OID-Type
+    - attribute-value.length = 2 bytes
+    - attribute-value = MDC\_DIM\_HECTO\_PASCAL
+  - 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 Not Recommended attribute Measure-Active-Period is present
+    - 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>
+  - k. Mandatory attribute Sample-Period
+    - attribute-id = MDC\_ATTR\_TIME\_PD\_SAMP
+    - attribute-type = RelativeTime
+    - attribute-value.length = 4 bytes
+    - attribute-value = <Not relevant in this test>
+  - l. Mandatory attribute Simple-Sa-Observed-Value
+    - attribute-id = MDC\_ATTR\_SIMP\_SA\_OBS\_VAL
+    - attribute-type = OCTET STRING
+    - attribute-value = <length must be even>
+  - m. Mandatory attribute Scale-and-Range-Specification
+    - attribute-id = MDC\_ATTR\_SCALE\_SPECN\_I8 or  
+MDC\_ATTR\_SCALE\_SPECN\_I16 or MDC\_ATTR\_SCALE\_SPECN\_I32
+    - attribute-type = ScaleRangeSpec8 OR ScaleRangeSpec16 OR  
+ScaleRangeSpec32
+    - attribute-value.length = 1, 2 OR 4 bytes, depending on the type
+    - attribute-value = <Not relevant in this test>
+  - n. Mandatory attribute Sa-Specification
+    - attribute-id = MDC\_ATTR\_SA\_SPECN
+    - attribute-type = SaSpec
+    - attribute-value.length = 6 bytes
+    - attribute-value = <Not relevant in this test>
+6. 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:
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• IF C_AG_OXP_005 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> <p><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</p> <p>7. If the PHD under test sends the Therapy Pressure waveforms RT-SA observations through a scanner object THEN the simulated PHG enables the scanner and receives the RT-SA event reports. The attribute of interest is:</p> <p>a. Mandatory attribute Type</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SIMP_SA_OBS_VAL ((x0A 0x48)</li> <li><input type="checkbox"/> attribute-type = OCTET STRING</li> <li><input type="checkbox"/> attribute-value = &lt;length must be even&gt;</li> </ul> <p>8. IF the PHD under test sends the Therapy Pressure waveforms RT-SA observations through a PM-Store object THEN the simulated PHG sends a request for PM-Store data (TrigSegmDataXfer) and the PHD sends the RT-SA stored data. The attribute of interest is:</p> <p>a. Mandatory attribute Type</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SIMP_SA_OBS_VAL ((x0A 0x48)</li> <li><input type="checkbox"/> attribute-type = OCTET STRING</li> <li><input type="checkbox"/> attribute-value = &lt;length must be even&gt;</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              | [AT4 wireless]: MetricSpecSmall must set bit mss-acc-agent-initiated(9) to TRUE because Scanner events are agent-initiated by intent in [ISO/IEEE 11073-20601-2015A] in spite of the fact the PHG enables/disables these objects (see bugzilla #856 for further details, <a href="http://continua.plugfest.com/show_bug.cgi?id=856">http://continua.plugfest.com/show_bug.cgi?id=856</a> ).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                          |                                                                                                                                                                                                                 |                        |               |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-031                                                                                                                                                                                   |                        |               |
+| <b>TP label</b>          | Leakage Waveform RT-SA Object for Extended Configuration                                                                                                                                                        |                        |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                     | [ISO/IEEE 11073-10424] |               |
+|                          | <b>Testable items</b>                                                                                                                                                                                           | RTSAObj2; M            | RTSAObj 3; R  |
+|                          |                                                                                                                                                                                                                 | RTSAObj 5; R           | RTSAObj 6; R  |
+|                          |                                                                                                                                                                                                                 | RTSAObj 8; R           | RTSAObj 9; M  |
+|                          |                                                                                                                                                                                                                 | RTSAObj 15; R          | RTSAObj 19; M |
+|                          |                                                                                                                                                                                                                 | RTSAObj 21; M          | RTSAObj 22; M |
+|                          |                                                                                                                                                                                                                 | RTSAObj 23; M          | RTSAObj 24; M |
+| <b>Test purpose</b>      | Check that:<br>Leakage Waveform RT-SA Object contains the attributes specified for Extended Configuration                                                                                                       |                        |               |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_025                                                                                                                                               |                        |               |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                        |                        |               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                         |                        |               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> </ol> |                        |               |
+
+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. 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. Once the PHD under test sends the tested configuration, check Leakage Waveform object:
+  - a. Mandatory attribute Type
+    - attribute-id = MDC\_ATTR\_ID\_TYPE
+    - attribute-type = TYPE
+      - attribute-value = MDC\_PART\_PHD\_DM (0x00 0x80) |  
+MDC\_SABTE\_VOL\_LEAK (0x57 0xD0)
+  - b. IF Not Recommended attribute Supplemental-Types is present
+    - attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+    - attribute-type = SupplementalTypeList
+    - attribute.value.length= 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
+    - attribute-type = MetricSpecSmall (2 bytes)
+    - attribute-value = 0x00 0x00
+  - d. 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>
+  - e. 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>
+  - f. 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>
+  - 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 = <Not relevant for this test>
+  - h. Mandatory attribute Unit-Code
+    - attribute-id = MDC\_ATTR\_UNIT\_CODE
+    - attribute-type = OID-Type
+    - attribute-value.length = 2 bytes
+    - attribute-value = MDC\_DIM\_L\_PER\_MIN
+
+- 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 Not Recommended attribute Measure-Active-Period is present
+    - 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>
+  - k. Mandatory attribute Sample-Period
+    - attribute-id = MDC\_ATTR\_TIME\_PD\_SAMP
+    - attribute-type = RelativeTime
+    - attribute-value.length = 4 bytes
+    - attribute-value = <Not relevant in this test>
+  - l. Mandatory attribute Simple-Sa-Observed-Value
+    - attribute-id = MDC\_ATTR\_SIMP\_SA\_OBS\_VAL
+    - attribute-type = OCTET STRING
+    - attribute-value = <length must be even>
+  - m. Mandatory attribute Scale-and-Range-Specification
+    - attribute-id = MDC\_ATTR\_SCALE\_SPECN\_I8 or  
+MDC\_ATTR\_SCALE\_SPECN\_I16 or MDC\_ATTR\_SCALE\_SPECN\_I32
+    - attribute-type = ScaleRangeSpec8 OR ScaleRangeSpec16 OR  
+ScaleRangeSpec32
+    - attribute-value.length = 1, 2 OR 4 bytes, depending on the type
+    - attribute-value = <Not relevant in this test>
+  - n. Mandatory attribute Sa-Specification
+    - attribute-id = MDC\_ATTR\_SA\_SPECN
+    - attribute-type = SaSpec
+    - attribute-value.length = 6 bytes
+    - attribute-value = <Not relevant in this test>
+6. 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\_005 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. If the PHD under test sends the Leakage waveforms RT-SA observations through a scanner object THEN the simulated PHG enables the scanner and receives the RT-SA event reports. The attribute of interest is:
+- a. Mandatory attribute Type
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SIMP_SA_OBS_VAL ((x0A 0x48)</li> <li><input type="checkbox"/> attribute-type = OCTET STRING</li> <li><input type="checkbox"/> attribute-value = &lt;length must be even&gt;</li> </ul> <p>8. If the PHD under test sends the Leakage waveforms RT-SA observations through a PM-Store object THEN the simulated PHG sends a request for PM-Sore data (TrigSegmDataXfer) and the PHD sends the RT-SA stored data. The attribute of interest is:</p> <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SIMP_SA_OBS_VAL ((x0A 0x48)</li> <li><input type="checkbox"/> attribute-type = OCTET STRING</li> <li><input type="checkbox"/> attribute-value = &lt;length must be even&gt;</li> </ul> </li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              | [AT4 wireless]: MetricSpecSmall must set bit mss-acc-agent-initiated(9) to TRUE because Scanner events are agent-initiated by intent in [ISO/IEEE 11073-20601-2015A] in spite of the fact the PHG enables/disables these objects (see bugzilla #856 for further details, <a href="http://continua.plugfest.com/show_bug.cgi?id=856">http://continua.plugfest.com/show_bug.cgi?id=856</a> ).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |               |               |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-032                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |               |               |
+| <b>TP label</b>          | Airflow Waveform RT-SA Object for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |               |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-10424] |               |               |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | RTSAObj2; M            | RTSAObj 3; R  | RTSAObj 4; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | RTSAObj 5; R           | RTSAObj 6; R  | RTSAObj 7; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | RTSAObj 8; R           | RTSAObj 9; M  | RTSAObj 11; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | RTSAObj 15; R          | RTSAObj 19; M | RTSAObj 20; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | RTSAObj 21; M          | RTSAObj 22; M | AirWave 2; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | AirWave 3; M           |               |               |
+| <b>Test purpose</b>      | Check that:<br>Airflow Waveform RT-SA Object contains the attributes specified for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |               |               |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_026                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |               |               |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |               |               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |               |               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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.</li> <li>5. Once the PHD under test sends the tested configuration, check Airflow Waveform object: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> </ul> </li> </ol> </li> </ol> |                        |               |               |
+
+- attribute-type = TYPE
+  - attribute-value = MDC\_PART\_PHD\_DM (0x00 0x80) |  
+MDC\_SABTE\_FLOW\_TOTAL (0x56 0x7C) or MDC\_PART\_PHD\_DM (0x00 0x80) | MDC\_SABTE\_FLOW\_WO\_PURGE (0x56 0x80) or  
+MDC\_PART\_PHD\_DM (0x00 0x80) | MDC\_SABTE\_FLOW\_RESP (0x56 0x84)
+- b. IF Not Recommended attribute Supplemental-Types is present
+  - attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+  - attribute-type = SupplementalTypeList
+  - attribute.value.length= 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 (2 bytes)
+  - attribute-value = 0x00 0x00
+- d. 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>
+- e. 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>
+- f. 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>
+- 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 = <Not relevant for this test>
+- h. Mandatory attribute Unit-Code
+  - attribute-id = MDC\_ATTR\_UNIT\_CODE
+  - attribute-type = OID-Type
+  - attribute-value.length = 2 bytes
+  - attribute-value = MDC\_DIM\_L\_PER\_MIN
+- 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 Not Recommended attribute Measure-Active-Period is present
+
+- 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>
+
+#### k. Mandatory attribute Sample-Period
+
+- attribute-id = MDC\_ATTR\_TIME\_PD\_SAMP
+- attribute-type = RelativeTime
+- attribute-value.length = 4 bytes
+- attribute-value = <Not relevant in this test>
+
+#### l. Mandatory attribute Simple-Sa-Observed-Value
+
+- attribute-id = MDC\_ATTR\_SIMP\_SA\_OBS\_VAL
+- attribute-type = OCTET STRING
+- attribute-value = <length must be even>
+
+#### m. Mandatory attribute Scale-and-Range-Specification
+
+- attribute-id = MDC\_ATTR\_SCALE\_SPECN\_I8 or MDC\_ATTR\_SCALE\_SPECN\_I16 or MDC\_ATTR\_SCALE\_SPECN\_I32
+- attribute-type = ScaleRangeSpec8 OR ScaleRangeSpec16 OR ScaleRangeSpec32
+- attribute-value.length = 1, 2 OR 4 bytes, depending on the type
+- attribute-value = <Not relevant in this test>
+
+#### n. Mandatory attribute Sa-Specification
+
+- attribute-id = MDC\_ATTR\_SA\_SPECN
+- attribute-type = SaSpec
+- attribute-value.length = 6 bytes
+- attribute-value = <Not relevant in this test>
+
+#### 6. 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\_005 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. IF the PHD under test sends the Airflow waveforms RT-SA observations through a scanner object THEN the simulated PHG enables the scanner and receives the RT-SA event reports. The attribute of interest is:
+
+#### a. Mandatory attribute Type
+
+- attribute-id = MDC\_ATTR\_SIMP\_SA\_OBS\_VAL ((x0A 0x48)
+- attribute-type = OCTET STRING
+- attribute-value = <length must be even>
+
+#### 8. IF the PHD under test sends the Airflow waveforms RT-SA observations through a PM-Store object THEN the simulated PHG sends a request for PM-Sore data (TrigSegmDataXfer) and the PHD sends the RT-SA stored data. The attribute of interest is:
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>a. Mandatory attribute Type</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SIMP_SA_OBS_VAL ((x0A 0x48)</li> <li><input type="checkbox"/> attribute-type = OCTET STRING</li> <li><input type="checkbox"/> attribute-value = &lt;length must be even&gt;</li> </ul>                                                                           |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              | [AT4 wireless]: MetricSpecSmall must set bit mss-acc-agent-initiated(9) to TRUE because Scanner events are agent-initiated by intent in [ISO/IEEE 11073-20601-2015A] in spite of the fact the PHG enables/disables these objects (see bugzilla #856 for further details, <a href="http://continua.plugfest.com/show_bug.cgi?id=856">http://continua.plugfest.com/show_bug.cgi?id=856</a> ). |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |               |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-033                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |               |
+| <b>TP label</b>          | Compliance Annotations Enumeration Object - Extended configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-10424] |               |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | EnumObj 3; M           | EnumObj 5; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | EnumObj 9; R           | EnumObj 11; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | EnumObj 15; R          | EnumObj 17; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | EnumObj 23; R          | EnumObj 31; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | CompAn 3; M            | CompAn 4; M   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | CompAn 8; O            | CompAn 9; M   |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Compliance Annotations Enumeration Object contains the attributes specified for Extended Configuration.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |               |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_027                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |               |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is in the extended range; if it is not, the simulated PHG must respond with an "unsupported-config" and waits for a new configuration.</li> <li>5. Once the PHD under test sends an extended configuration, check that all Compliance Annotations Objects have: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_PATT_COMPLIANCE_CLS (0x57 0x1C)</li> </ul> </li> <li>b. IF Not Recommended attribute Supplemental-Types is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> </ul> </li> </ol> </li> </ol> |                        |               |
+
+attribute-value.length = <variable>(Sequence of TYPE (TYPE.length= 4 bytes))
+
+#### 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 3 must be set (mss-msmt-aperiodic(3))
+
+- Bit 9 must be set (mss-acc-agent-initiated(9))
+
+#### d. IF Not Recommended attribute Metric-Structure-Small is present
+
+attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+
+attribute-type = MetricStructureSmall
+
+attribute-value.length = <variable>(Sequence of (ms-struct.length = 1byte(INT-U8) + ms-comp-no = 1byte(INT-U8)))
+
+#### e. IF Not Recommended attribute Measurement-Status is present
+
+attribute-id = MDC\_ATTR\_MSMT\_STAT
+
+attribute-type = MeasurementStatus(BITS-16)
+
+attribute-value.length = 2 bytes
+
+#### 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 = Only one attribute of Metric-Id and Metric-Id-List shall be present.
+
+#### g. IF Not Recommended attribute Metric-Id-List is present
+
+attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIS
+
+attribute-type = MetricIdList
+
+attribute-value.length= <variable>(SEQUENCE OF OID-Type (INT-U16))
+
+#### 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
+
+#### i. 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
+
+#### 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
+
+#### k. IF Recommended attribute Base-Offset-Time-Stamp is present
+
+attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> <li>l. IF Not Recommended attribute Measure-Active-Period is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> <li>m. Mandatory attribute Enum-Observed-Value-Basic-Bit-Str <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = sabte-annotation-session-undetermined-start   sabte-annotation-session-undetermined-stop   sabte-annotation-session-therapy-start   sabte-annotation-session-therapy-stop   sabte-annotation-session-usage-start   sabte-annotation-session-usage-stop</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |               |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-034                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |               |
+| <b>TP label</b>          | Efficacy Annotations Enumeration Object - Extended configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-10424] |               |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | EnumObj 3; M           | EnumObj 5; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | EnumObj 9; R           | EnumObj 11; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | EnumObj 15; R          | EnumObj 17; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | EnumObj 23; R          | EnumObj 31; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | EffAn 4; M             | EffAn 5; M    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | EffAn 8; O             | EffAn 9; M    |
+| <b>Test purpose</b>      | Check that:<br>Efficacy Annotations Enumeration Object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |               |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_028                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |               |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is in the extended range; if it is not, the simulated PHG must respond with an "unsupported-config" and waits for a new configuration.</li> <li>5. Once the PHD under test sends an extended configuration, check that all Efficacy Annotations Objects have:</li> </ol> |                        |               |
+
+- a. Mandatory attribute Type
+  - attribute-id = MDC\_ATTR\_ID\_TYPE
+  - attribute-type = TYPE
+  - attribute-value = MDC\_PART\_PHD\_DM (0x00 0x80) |  
+MDC\_SABTE\_PATT\_EFFICACY\_CLS (0x57 0x24)
+- b. IF Not Recommended attribute Supplemental-Types is present
+  - attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+  - attribute-type = SupplementalTypeList
+  - attribute-value.length =<variable>(Sequence of TYPE (TYPE.length= 4 bytes))
+- 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  $\neq$  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))
+- d. IF Not Recommended attribute Metric-Structure-Small is present
+  - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+  - attribute-type = MetricStructureSmall
+  - attribute-value.length = <variable>(Sequence of (ms-struct.length  
+=1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))
+- e. IF Not Recommended attribute Measurement-Status is present
+  - attribute-id = MDC\_ATTR\_MSMT\_STAT
+  - attribute-type = MeasurementStatus(BITS-16)
+  - attribute-value.length =2 bytes
+- 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 = Only one attribute of Metric-Id and Metric-Id-List shall be present.
+- g. IF Not Recommended attribute Metric-Id-List is present
+  - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIS
+  - attribute-type = MetricIdList
+  - attribute-value.length= <variable>(SEQUENCE OF OID-Type (INT-U16))
+- 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
+- i. IF Not recommended attribute Unit-Code is present
+  - attribute-id = MDC\_ATTR\_UNIT\_CODE
+  - attribute-type = OID-Type (INT-U16)
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li>j. IF Not Recommended attribute Source-Handle-Reference is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>k. IF Recommended attribute Base-Offset-Time-Stamp is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> </li> <li>l. IF Not Recommended attribute Measure-Active-Period is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> <li>m. Mandatory attribute Enum-Observed-Value-Basic-Bit-Str <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute.value= sabte-annotation-epoch-undetermined-start   sabte-annotation-epoch-undetermined-stop   sabte-annotation-epoch-breathing-artifact-start   sabte-annotation-epoch-breathing-artifact-stop   sabte-annotation-epoch-breathing-spontaneous-start   sabte-annotation-epoch-breathing-spontaneous-stop   sabte-annotation-epoch-breathing-timed-start   sabte-annotation-epoch-breathing-timed-stop   sabte-annotation-epoch-snoring-start   sabte-annotation-epoch-snoring-stop   sabte-annotation-epoch-csr-start   sabte-annotation-epoch-csr-stop   sabte-annotation-event-undetermined-start   sabte-annotation-event-undetermined-stop   sabte-annotation-event-flow-limitation-start   sabte-annotation-event-flow-limitation-stop   sabte-annotation-event-hypopnoea-unclassified-start   sabte-annotation-event-hypopnoea-unclassified-stop   sabte-annotation-event-hypopnoea-obstructive-start   sabte-annotation-event-hypopnoea-obstructive-stop   sabte-annotation-event-hypopnoea-central-start   sabte-annotation-event-hypopnoea-central-stop   sabte-annotation-event-apnoea-unclassified-start   sabte-annotation-event-apnoea-unclassified-stop   sabte-annotation-event-apnoea-obstructive-start   sabte-annotation-event-apnoea-obstructive-stop   sabte-annotation-event-apnoea-mixed-start   sabte-annotation-event-apnoea-mixed-stop   sabte-annotation-event-apnoea-central-start   sabte-annotation-event-apnoea-central-stop</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                 |                                                           |                        |               |               |
+|-----------------|-----------------------------------------------------------|------------------------|---------------|---------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/SABTE/BV-035                             |                        |               |               |
+| <b>TP label</b> | PHD DM Status Enumeration Object - Extended configuration |                        |               |               |
+| <b>Coverage</b> | <b>Spec</b>                                               | [ISO/IEEE 11073-10424] |               |               |
+|                 | <b>Testable items</b>                                     | EnumObj 3; M           | EnumObj 5; R  | EnumObj 7; M  |
+|                 |                                                           | EnumObj 9; R           | EnumObj 11; R | EnumObj 13; R |
+|                 |                                                           | EnumObj 15; R          | EnumObj 17; R | EnumObj 19; R |
+|                 |                                                           | EnumObj 23; R          | EnumObj 31; R | EnumObj 37; R |
+|                 |                                                           | PHDDM 4; M             | PHDDM 5; M    | PHDDM 7; M    |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |            |            |  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------|--|
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | PHDDM 8; M | PHDDM 9; M |  |
+| <b>Test purpose</b>      | Check that:<br>PHD DM Status Enumeration Object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |            |            |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_029                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |            |            |  |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |            |            |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |            |            |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is in the extended range; if it is not, the simulated PHG must respond with an "unsupported-config" and waits for a new configuration.</li> <li>5. Once the PHD under test sends an extended configuration, check that all PHD DM Status Objects have: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80)  <br/>MDC_PHD_DM_DEV_STAT (0x4E 0x20)</li> </ol> </li> <li>b. IF Not Recommended attribute Supplemental-Types is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt;(Sequence of TYPE (TYPE.length= 4 bytes))</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec_Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> </ol> </li> </ol> </li> <li>d. IF Not Recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8))))</li> </ol> </li> <li>e. IF Not Recommended attribute Measurement-Status is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus(BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> </ol> </li> <li>f. IF Not Recommended attribute Metric-Id is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> </ol> </li> </ol> </li> </ol> |            |            |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = Only one attribute of Metric-Id and Metric-Id-List shall be present.</li> </ul> <p>g. IF Not Recommended attribute Metric-Id-List is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIS</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value.length= &lt;variable&gt;(SEQUENCE OF OID-Type (INT-U16))</li> </ul> <p>h. IF Not Recommended attribute Metric-Id-Partition is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>i. IF Not recommended attribute Unit-Code is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>j. IF Not Recommended attribute Source-Handle-Reference is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>k. IF Recommended attribute Base-Offset-Time-Stamp is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> <p>l. IF Not Recommended attribute Measure-Active-Period is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>m. Mandatory attribute Enum-Observed-Value-Simple-Str</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIMP_STR</li> <li><input type="checkbox"/> attribute-type = BITS-16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = device-status-undetermined   device-status-reset   device-status-error   device-status-error-mechanical   device-status-error-electronic   device-status-error-software   device-status-error-battery   device-status-service   device-status-service-time-sync-required   device-status-service-calibration-required   device-status-service-replenishment-required   device-status-battery-low   device-status-battery-depleted   device-status-battery-replaced   device-status-battery-interrupted</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                 |                                                                    |
+|-----------------|--------------------------------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/SABTE/BV-036                                      |
+| <b>TP label</b> | Device Mode Set Enumeration Object - Standard configuration (2400) |
+
+|                          |                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |               |               |  |
+|--------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|--|
+| <b>Coverage</b>          | <b>Spec</b>           | [ISO/IEEE 11073-10424]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |               |               |  |
+|                          | <b>Testable items</b> | EnumObj 2; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | EnumObj 4; M  | EnumObj 6; R  |  |
+|                          |                       | EnumObj 8; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | EnumObj 10; R | EnumObj 12; R |  |
+|                          |                       | EnumObj 14; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | EnumObj 16; R | EnumObj 18; R |  |
+|                          |                       | EnumObj 20; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | EnumObj 22; M | EnumObj 24; R |  |
+|                          |                       | EnumObj 26; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | EnumObj 28; O | EnumObj 30; C |  |
+|                          |                       | EnumObj 32; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | EnumObj 34; C | EnumObj 36; C |  |
+|                          |                       | EnumObj 38; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | EnumObj 40; C | EnumObj 42; C |  |
+|                          |                       | EnumObj 44; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | EnumObj 46; C | EnumObj 48; C |  |
+|                          |                       | EnumObj 50; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |               |               |  |
+|                          |                       | DevMode 4; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | DevMode 6; M  | DevMode 8; M  |  |
+|                          |                       | DevMode 10; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | DevMode 12; M |               |  |
+| <b>Test purpose</b>      |                       | Check that:<br>The Device Mode Set enumeration object contains the attributes specified for Standard Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |               |               |  |
+| <b>Applicability</b>     |                       | C_AG_OXP_000 AND C_AG_OXP_162 AND (NOT C_AG_OXP_181)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |               |               |  |
+| <b>Other PICS</b>        |                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |               |               |  |
+| <b>Initial condition</b> |                       | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |               |               |  |
+| <b>Test procedure</b>    |                       | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set to 0x0960 (2400); if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration</li> <li>4. Once the PHD under test sends a standard configuration, check that Device Mode Set Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_HANDLE</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x03</li> </ol> </li> <li>b. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> IF (Dev-Config-Id = 0x0960): <ul style="list-style-type: none"> <li>• attribute-id = MDC_ATTR_ID_TYPE</li> <li>• attribute-type = TYPE</li> <li>• attribute-value = MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_MODE_DEV_SET (0x56 0xFC).</li> </ul> </li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ol> </li> </ol> </li> </ol> |               |               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value <math>\neq</math> 0x00 0x00           <ul style="list-style-type: none"> <li>• Bit 1 (mss-avail-stored-data(1)), must be set</li> <li>• Bit 2 (mss-upd-aperiodic(2)), must be set</li> <li>• Bit 9 (mss-acc-agent-initiated(9)), must be set</li> <li>• Bit 13 (mss-cat-setting(13)), must be set</li> <li>• The other bits have to be 0.</li> </ul> </li> </ul> <p>d. Mandatory attribute Attribute-Value-Map</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = AttrValMap (sequence of attribute-id(OID-Type) and attribute-length( INT-U16) )</li> <li><input type="checkbox"/> attribute-value.length=&lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value= MDC_ATTR_ENUM_OBS_VAL_SIMP_OID, then MDC_ATTR_TIME_STAMP_BO</li> </ul> <p>e. Mandatory attribute Enum-Observed-Value-Simple-OID is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ENUM_OBS_VAL_SIMP_OID</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = One of the following nomenclature values will be used:           <ul style="list-style-type: none"> <li>▪ MDC_SABTE_MODE_DEV_UNDETERMINED (0x56 0xFD)</li> <li>▪ MDC_SABTE_MODE_DEV_STANDBY (0x56 0xFE)</li> <li>▪ MDC_SABTE_MODE_DEV_THERAPY (0x56 0xFF)</li> <li>▪ MDC_SABTE_MODE_DEV_MASK_FITTING (0x57 0x00)</li> <li>▪ MDC_SABTE_MODE_DEV_DRYING (0x57 0x01)</li> <li>▪ MDC_SABTE_MODE_DEV_EXPORTING (0x57 0x02)</li> </ul> </li> </ul> <p>f. No other attribute shall be present at configuration.</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                     |                                                                                                                     |                                                                                                 |                                                                                 |
+|---------------------|---------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/SABTE/BV-037                                                                                       |                                                                                                 |                                                                                 |
+| <b>TP label</b>     | Device Mode Set Enumeration Object - Extended configuration                                                         |                                                                                                 |                                                                                 |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                         | [ISO/IEEE 11073-10424]                                                                          |                                                                                 |
+|                     | <b>Testable items</b>                                                                                               | EnumObj 3; M<br>EnumObj 9; R<br>EnumObj 15; R<br>EnumObj 23; R<br>DevMode 5; M<br>DevMode 11; M | EnumObj 5; R<br>EnumObj 11; R<br>EnumObj 17; R<br>EnumObj 31; R<br>DevMode 7; M |
+| <b>Test purpose</b> | Check that:<br>The Device Mode Set enumeration Object contains the attributes specified for Extended Configuration. |                                                                                                 |                                                                                 |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that Device Mode Set Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_MODE_DEV_SET (0x56 0xFC)</li> </ol> </li> <li>b. IF Not Recommended Supplemental-Types attribute is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> <li>• Bit 13 must be set (mss-cat-setting(13))</li> </ol> </li> </ol> </li> <li>d. IF Not Recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))</li> </ol> </li> <li>e. IF Not Recommended attribute Measurement-Status is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> </ol> </li> <li>f. IF Not Recommended attribute Metric-Id is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length= 2 bytes</li> </ol> </li> <li>g. IF Not Recommended attribute Metric-Id-List is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIST</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> </ol> </li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value.length= SEQUENCE OF OID-Type (INT-U16)</li> <li>h. IF Not Recommended attribute Metric-Id-Partition is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>i. IF Not Recommended attribute Unit-Code is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>j. IF Not Recommended attribute Source-Handle-Reference is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>k. IF Recommended attribute Base-Offset-Time-Stamp is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> </li> <li>l. IF Not Recommended attribute Measure-Active-Period <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> <li>m. IF Recommended attribute Enum-Observed-Value-Simple-OID <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ENUM_OBS_VAL_SIMP_OID</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = One of the following nomenclature values will be used: <ul style="list-style-type: none"> <li>▪ MDC_SABTE_MODE_DEV_UNDETERMINED (0x56 0xFD)</li> <li>▪ MDC_SABTE_MODE_DEV_STANDBY (0x56 0xFE)</li> <li>▪ MDC_SABTE_MODE_DEV_THERAPY (0x56 0xFF)</li> <li>▪ MDC_SABTE_MODE_DEV_MASK_FITTING (0x57 0x00)</li> <li>▪ MDC_SABTE_MODE_DEV_DRYING (0x57 0x01)</li> <li>▪ MDC_SABTE_MODE_DEV_EXPORTING (0x57 0x02)</li> </ul> </li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                       |                                                                     |                        |               |
+|-----------------------|---------------------------------------------------------------------|------------------------|---------------|
+| <b>TP Id</b>          | TP/PLT/PHD/CLASS/SABTE/BV-038                                       |                        |               |
+| <b>TP label</b>       | Therapy Mode Set Enumeration Object - Standard configuration (2400) |                        |               |
+| <b>Coverage</b>       | <b>Spec</b>                                                         | [ISO/IEEE 11073-10424] |               |
+| <b>Testable items</b> | EnumObj 2; M                                                        | EnumObj 4; M           | EnumObj 6; R  |
+|                       | EnumObj 8; M                                                        | EnumObj 10; R          | EnumObj 12; R |
+|                       | EnumObj 14; R                                                       | EnumObj 16; R          | EnumObj 18; R |
+
+|                          |  |                                                                                                                      |                |               |
+|--------------------------|--|----------------------------------------------------------------------------------------------------------------------|----------------|---------------|
+|                          |  | EnumObj 20; R                                                                                                        | EnumObj 22; M  | EnumObj 24; R |
+|                          |  | EnumObj 26; O                                                                                                        | EnumObj 28; O  | EnumObj 30; C |
+|                          |  | EnumObj 32; R                                                                                                        | EnumObj 34; C  | EnumObj 36; C |
+|                          |  | EnumObj 38; R                                                                                                        | EnumObj 40; C  | EnumObj 42; C |
+|                          |  | EnumObj 44; C                                                                                                        | EnumObj 46; C  | EnumObj 48; C |
+|                          |  | EnumObj 50; C                                                                                                        |                |               |
+|                          |  | TherMode 4; M                                                                                                        | TherMode 6; M  | TherMode 8; M |
+|                          |  | TherMode 10; M                                                                                                       | TherMode 12; M |               |
+| <b>Test purpose</b>      |  | Check that:<br>The Therapy Mode Set enumeration object contains the attributes specified for Standard Configuration. |                |               |
+| <b>Applicability</b>     |  | C_AG_OXP_000 AND C_AG_OXP_162 AND (NOT C_AG_OXP_181)                                                                 |                |               |
+| <b>Other PICS</b>        |  |                                                                                                                      |                |               |
+| <b>Initial condition</b> |  | The simulated PHG and the PHD under test are in the Unassociated state.                                              |                |               |
+
+|                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test procedure</b> | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set to 0x0960 (2400); if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends a standard configuration, check that Therapy Mode Set Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_HANDLE</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x04</li> </ul> </li> <li>b. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> IF (Dev-Config-Id = 0x0960): <ul style="list-style-type: none"> <li>• attribute-id = MDC_ATTR_ID_TYPE</li> <li>• attribute-type = TYPE</li> <li>• attribute-value = MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_MODE_THERAPY_SET (0x57 0x08).</li> </ul> </li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 1 (mss-avail-stored-data(1)), must be set</li> <li>• Bit 2 (mss-upd-aperiodic(2)), must be set</li> <li>• Bit 9 (mss-acc-agent-initiated(9)), must be set</li> <li>• Bit 13 (mss-cat-setting(13)), must be set</li> <li>• The other bits have to be 0.</li> </ul> </li> </ul> </li> <li>d. Mandatory attribute Attribute-Value-Map <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = AttrValMap (sequence of attribute-id(OID-Type) and attribute-length( INT-U16) )</li> <li><input type="checkbox"/> attribute-value.length=&lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value= MDC_ATTR_ENUM_OBS_VAL_SIMP_OID, then MDC_ATTR_TIME_STAMP_BO</li> </ul> </li> <li>e. Mandatory attribute Enum-Observed-Value-Simple-OID is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ENUM_OBS_VAL_SIMP_OID</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = One of the following nomenclature values will be used: <ul style="list-style-type: none"> <li>▪ MDC_SABTE_MODE_THERAPY_UNDETERMINED (0x56 0xFD)</li> <li>▪ MDC_SABTE_MODE_THERAPY_CPAP (0x57 0x09)</li> <li>▪ MDC_SABTE_MODE_THERAPY_CPAP_AUTO (0x57 0x0A)</li> <li>▪ MDC_SABTE_MODE_THERAPY_BPAP_S (0x57 0x0B)</li> <li>▪ MDC_SABTE_MODE_THERAPY_BPAP_T (0x57 0x0C)</li> <li>▪ MDC_SABTE_MODE_THERAPY_BPAP_ST (0x57 0x0D)</li> </ul> </li> </ul> </li> </ol> </li> </ol> |
+|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                           |                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>▪ MDC_SABTE_MODE_THERAPY_BPAP_S_AUTO (0x57 0x0E)</li> <li>▪ MDC_SABTE_MODE_THERAPY_BPAP_T_AUTO (0x57 0x0F)</li> <li>▪ MDC_SABTE_MODE_THERAPY_BPAP_ST_AUTO (0x57 0x10)</li> <li>▪ MDC_SABTE_MODE_THERAPY_ACSV (0x57 0x11)</li> </ul> <p>f. No other attribute shall be present at configuration.</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |               |               |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-039                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |               |               |
+| <b>TP label</b>          | Therapy Mode Set Enumeration Object - Extended configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |               |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-10424] |               |               |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | EnumObj 3; M           | EnumObj 5; R  | EnumObj 7; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EnumObj 9; R           | EnumObj 11; R | EnumObj 13; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EnumObj 15; R          | EnumObj 17; R | EnumObj 19; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EnumObj 23; R          | EnumObj 31; R | EnumObj 37; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | TherMode 5; M          | TherMode 7; M | TherMode 9; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | TherMode 11; M         |               |               |
+| <b>Test purpose</b>      | Check that:<br>The Therapy Mode Set enumeration Object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |               |               |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |               |               |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |               |               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |               |               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an extended configuration, check that Therapy Mode Set Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80)  <br/>MDC_SABTE_MODE_THERAPY_SET (0x57 0x08)</li> </ul> </li> <li>b. IF Not Recommended Supplemental-Types attribute is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes)</li> </ul> </li> </ol> </li> </ol> |                        |               |               |
+
+- 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  $\neq$  0x00 0x00
+    - 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))
+    - Bit 13 must be set (mss-cat-setting(13))
+- d. IF Not Recommended attribute Metric-Structure-Small is present
+  - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+  - attribute-type = MetricStructureSmall
+  - attribute-value.length = <variable>(Sequence of (ms-struct.length = 1byte(INT-U8) + ms-comp-no = 1byte(INT-U8))))
+- e. IF Not Recommended attribute Measurement-Status is present
+  - attribute-id = MDC\_ATTR\_MSMT\_STAT
+  - attribute-type = MeasurementStatus (BITS-16)
+  - attribute-value.length = 2 bytes
+- 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
+- g. IF Not Recommended attribute Metric-Id-List is present
+  - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+  - attribute-type = MetricIdList
+  - attribute-value.length = SEQUENCE OF OID-Type (INT-U16)
+- 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
+- i. 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
+- 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
+- k. IF Recommended attribute Base-Offset-Time-Stamp is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+  - attribute-type = BaseOffsetTime
+  - attribute-value.length = 8 bytes
+- l. IF Not Recommended attribute Measure-Active-Period is present
+  - attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>m. IF Recommended attribute Enum-Observed-Value-Simple-OID is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ENUM_OBS_VAL_SIMP_OID</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = One of the following nomenclature values will be used: <ul style="list-style-type: none"> <li>▪ MDC_SABTE_MODE_THERAPY_UNDETERMINED (0x56 0xFD)</li> <li>▪ MDC_SABTE_MODE_THERAPY_CPAP (0x57 0x09)</li> <li>▪ MDC_SABTE_MODE_THERAPY_CPAP_AUTO (0x57 0x0A)</li> <li>▪ MDC_SABTE_MODE_THERAPY_BPAP_S (0x57 0x0B)</li> <li>▪ MDC_SABTE_MODE_THERAPY_BPAP_T (0x57 0x0C)</li> <li>▪ MDC_SABTE_MODE_THERAPY_BPAP_ST (0x57 0x0D)</li> <li>▪ MDC_SABTE_MODE_THERAPY_BPAP_S_AUTO (0x57 0x0E)</li> <li>▪ MDC_SABTE_MODE_THERAPY_BPAP_T_AUTO (0x57 0x0F)</li> <li>▪ MDC_SABTE_MODE_THERAPY_BPAP_ST_AUTO (0x57 0x10)</li> <li>▪ MDC_SABTE_MODE_THERAPY_ACSV (0x57 0x11)</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                      |                        |               |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-040                                                                                                                                                                                                                                                                                        |                        |               |
+| <b>TP label</b>          | Autostart/-stop Set Enumeration Object - Extended configuration                                                                                                                                                                                                                                                      |                        |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-10424] |               |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                | EnumObj 3; M           | EnumObj 5; R  |
+|                          |                                                                                                                                                                                                                                                                                                                      | EnumObj 9; R           | EnumObj 11; R |
+|                          |                                                                                                                                                                                                                                                                                                                      | EnumObj 15; R          | EnumObj 17; R |
+|                          |                                                                                                                                                                                                                                                                                                                      | EnumObj 23; R          | EnumObj 31; R |
+|                          |                                                                                                                                                                                                                                                                                                                      | AutoSS 4; M            | AutoSS 5; M   |
+|                          |                                                                                                                                                                                                                                                                                                                      | AutoSS 10; M           |               |
+| <b>Test purpose</b>      | Check that:<br>Autostart/-stop Set Enumeration Object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                  |                        |               |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_030                                                                                                                                                                                                                                                    |                        |               |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                      |                        |               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                              |                        |               |
+| <b>Test procedure</b>    | 1. The simulated PHG receives an association request from the PHD under test.<br>2. The simulated PHG responds with a result = accepted-unknown-config.<br>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 simulated PHG must respond with an "unsupported-config" and waits for a new configuration.
+5. Once the PHD under test sends an extended configuration, check that all Autostart/-stop Set Objects have:
+  - a. Mandatory attribute Type
+    - attribute-id = MDC\_ATTR\_ID\_TYPE
+    - attribute-type = TYPE
+    - attribute-value = MDC\_PART\_PHD\_DM (0x00 0x80) | MDC\_SABTE\_MODE\_AUTOSTARTSTOP\_SET (0x56 0xF8)
+  - b. IF Not Recommended attribute Supplemental-Types is present
+    - attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+    - attribute-type = SupplementalTypeList
+    - attribute-value.length =<variable>(Sequence of TYPE (TYPE.length= 4 bytes))
+  - 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 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))
+      - Bit 13 must be set (mss-cat-setting(13))
+  - d. IF Not Recommended attribute Metric-Structure-Small is present
+    - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+    - attribute-type = MetricStructureSmall
+    - attribute-value.length = <variable>(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8))))
+  - e. IF Not Recommended attribute Measurement-Status
+    - attribute-id = MDC\_ATTR\_MSMT\_STAT
+    - attribute-type = MeasurementStatus(BITS-16)
+    - attribute-value.length =2 bytes
+  - 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 = Only one attribute of Metric-Id and Metric-Id-List shall be present.
+  - g. IF Not Recommended attribute Metric-Id-List is present
+    - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIS
+    - attribute-type = MetricIdList
+    - attribute-value.length= <variable>(SEQUENCE OF OID-Type (INT-U16))
+  - 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
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>i. IF Not recommended attribute Unit-Code is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>j. IF Not Recommended attribute Source-Handle-Reference is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>k. IF Recommended attribute Base-Offset-Time-Stamp is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> <p>l. IF Not Recommended attribute Measure-Active-Period is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>m. Mandatory attribute Enum-Observed-Value-Simple-Str</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIMP_STR</li> <li><input type="checkbox"/> attribute-type = BITS-16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = sabte-autostart-on   sabte-autostop-on</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|                          |                                                                                                                                         |                        |               |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-041                                                                                                           |                        |               |
+| <b>TP label</b>          | Pressure Adaption Freeze Set Enumeration Object - Extended configuration                                                                |                        |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                             | [ISO/IEEE 11073-10424] |               |
+|                          | <b>Testable items</b>                                                                                                                   | EnumObj 3; M           | EnumObj 5; R  |
+|                          |                                                                                                                                         | EnumObj 9; R           | EnumObj 11; R |
+|                          |                                                                                                                                         | EnumObj 15; R          | EnumObj 17; R |
+|                          |                                                                                                                                         | EnumObj 23; R          | EnumObj 31; R |
+|                          |                                                                                                                                         | PAFS 6; M              | PAFS 7; M     |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Pressure Adaption Freeze Set Enumeration Object contains the attributes specified for Extended Configuration.</p> |                        |               |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_031                                                                       |                        |               |
+| <b>Other PICS</b>        |                                                                                                                                         |                        |               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                 |                        |               |
+
+|                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test procedure</b> | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is in the extended range; if it is not, the simulated PHG must respond with an "unsupported-config" and waits for a new configuration.</li> <li>5. Once the PHD under test sends an extended configuration, check that all Pressure Adaption Freeze Set Objects have: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80)   MDC_SABTE_MODE_ADAPT_FREEZE_SET (0x56 0xF4)</li> </ul> </li> <li>b. IF Not recommended attribute Supplemental-Types is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt;(Sequence of TYPE (TYPE.length= 4 bytes))</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec_Small <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> <li>• Bit 13 must be set (mss-cat-setting(13))</li> </ul> </li> </ul> </li> <li>d. IF Not recommended attribute Metric-Structure-Small is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))</li> </ul> </li> <li>e. IF Not recommended attribute Measurement-Status <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus(BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> </ul> </li> <li>f. IF Not recommended attribute Metric-Id is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = Only one attribute of Metric-Id and Metric-Id-List shall be present.</li> </ul> </li> <li>g. IF Not recommended attribute Metric-Id-List is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIS</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value.length= &lt;variable&gt;(SEQUENCE OF OID-Type (INT-U16))</li> </ul> </li> <li>h. IF Not recommended attribute Metric-Id-Partition is present</li> </ol> </li> </ol> |
+|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li>i. IF Not recommended attribute Unit-Code is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>j. IF Not recommended attribute Source-Handle-Reference is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>k. IF recommended attribute Base-Offset-Time-Stamp is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> </li> <li>l. IF Not recommended attribute Measure-Active-Period is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> <li>m. Mandatory attribute Enum-Observed-Value-Simple-OID is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIMP_OID</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = one of the following nomenclature values will be used: <ul style="list-style-type: none"> <li>• MDC_SABTE_MODE_ADAPT_FREEZE_OFF (0x56 0xF5) OR</li> <li>• MDC_SABTE_MODE_ADAPT_FREEZE_ON (0x56 0xF6)</li> </ul> </li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                      |                                                                                                                                                                                                                                                                                                                                                                       |                        |                   |
+|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|
+| <b>TP Id</b>         | TP/PLT/PHD/CLASS/SABTE/BV-042                                                                                                                                                                                                                                                                                                                                         |                        |                   |
+| <b>TP label</b>      | SABTE: PM-Store, PM-Segment attributes                                                                                                                                                                                                                                                                                                                                |                        |                   |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-10424] |                   |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                 | PMStrObjAtt 11; O      | PMStrObjAtt 12; O |
+| <b>Test purpose</b>  | Check that:<br><br>If the measurements are periodic and the Sample-Period is not defined in each of the components' PMSegment object attributes, the Sample-Period shall be defined in the PM-Store attribute<br><br>[AND]<br><br>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 |                        |                   |
+| <b>Applicability</b> | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_041 AND C_AG_OXP_181                                                                                                                                                                                                                                                                                                       |                        |                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. The handle for the PM-Store attribute must be: <ul style="list-style-type: none"> <li>a. Mandatory attribute Handle <ul style="list-style-type: none"> <li><li><input type="checkbox"/> attribute-type = HANDLE</li></li> <li><li><input type="checkbox"/> attribute-value.length = 2 bytes</li></li> <li><li><input type="checkbox"/> attribute-value = must be unique and non-zero. Actual value may be specified by the Device Specialization.</li></li> </ul> </li> </ul> </li> <li>5. 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.</li> <li>6. The PHD issues a GET response with the PM-Store attributes it supports: <ul style="list-style-type: none"> <li>a. Conditional attribute Sample-Period <ul style="list-style-type: none"> <li><li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_SAMP</li></li> <li><li><input type="checkbox"/> attribute-type = RelativeTime</li></li> <li><li><input type="checkbox"/> attribute-value.length= 4 bytes</li></li> <li><li><input type="checkbox"/> attribute-value= &lt;Not relevant for this Test&gt;</li></li> </ul> </li> </ul> </li> <li>7. The simulated PHG shall send a Get-Segment-Info object action for the PM-Store object with SegmSelection set to all-segments <ul style="list-style-type: none"> <li>a. Conditional attribute Sample-Period <ul style="list-style-type: none"> <li><li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_SAMP</li></li> <li><li><input type="checkbox"/> attribute-type = RelativeTime</li></li> <li><li><input type="checkbox"/> attribute-value.length= 4 bytes</li></li> <li><li><input type="checkbox"/> attribute-value= &lt;Not relevant for this test&gt;</li></li> </ul> </li> </ul> </li> </ol> |
+| <b>Pass/Fail criteria</b> | Attribute Sample-Period shall be implemented in PM-Store if it is not implemented in every PM-Segment.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                      |                                                                                         |                        |                 |                 |
+|----------------------|-----------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|
+| <b>TP Id</b>         | TP/PLT/PHD/CLASS/SABTE/BV-043                                                           |                        |                 |                 |
+| <b>TP label</b>      | PM Segment Object for Extended Configuration                                            |                        |                 |                 |
+| <b>Coverage</b>      | <b>Spec</b>                                                                             | [ISO/IEEE 11073-10424] |                 |                 |
+|                      | <b>Testable items</b>                                                                   | PMStoreObj 5; M        | PMStoreObj 6; O | PMStoreObj 7; M |
+|                      |                                                                                         | PMSegObj 6; M          | PMSegObj 7; M   | PMSegObj 8; M   |
+|                      |                                                                                         | PMSegObj 10; M         |                 |                 |
+| <b>Test purpose</b>  | Check that:<br>PM-Segment contains the attributes specified for Extended Configuration. |                        |                 |                 |
+| <b>Applicability</b> | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_041 AND C_AG_OXP_181                         |                        |                 |                 |
+| <b>Other PICS</b>    |                                                                                         |                        |                 |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>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.</li> <li>2. 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.</li> <li>3. The PHD issues a response with the PM-Segment attributes it supports: <ol style="list-style-type: none"> <li>a. Recommended attribute Segment-Start-BO-Time <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_START_SEG_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> </li> <li>b. Recommended attribute Segment-End-BO-Time <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_END_SEG_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> </li> <li>c. Mandatory attribute PM-Segment-Entry-Map <ul style="list-style-type: none"> <li><input type="checkbox"/> SegmentEntryHeader.value = One of the next must be set: <ul style="list-style-type: none"> <li>• seg-elem-hdr-relative-time(1)</li> <li>• seg-elem-hdr-hires-relative-time(2)</li> <li>• seg-elem-hdr-bo-time(3)</li> </ul> </li> <li><input type="checkbox"/> SegmentEntryElem: &lt; Record the fields for later comparison&gt;</li> </ul> </li> </ol> </li> <li>4. Repeat step 3 and 4 for every Segment</li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+|                          |                                                                                                                                                                                                                                     |                        |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-043_A                                                                                                                                                                                                     |                        |  |
+| <b>TP label</b>          | PM-Segment Object for Extended Configuration.MDS Event Reports                                                                                                                                                                      |                        |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                         | [ISO/IEEE 11073-10424] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                               | PMStoreObj 3; M        |  |
+| <b>Test purpose</b>      | Check that:<br>Any configuration with a PM-store for longer term storage shall disable agent-initiated transmission as well as the use of scanner objects and support manager-initiated transmission of data recorded in PM-stores. |                        |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_041 AND C_AG_OXP_181                                                                                                                                                                     |                        |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                     |                        |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Check if PHD configuration includes scanner objects.</li> <li>2. 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.</li> <li>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.</li> <li>4. The simulated PHG asks for measurement.</li> <li>5. Check event reports that are sent by the PHD.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <p>In step 1, the PHD configuration shall not include scanner objects</p> <p>In step 5, the PHD shall not send the data with MDS event reports</p>                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                 |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-044                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                 |
+| <b>TP label</b>          | Communication Model: Association Procedure                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-10424] |                 |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | AgProcAs 1; M          | AgProcAs 2; M   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | AgProcAs 5; M          | AgProcAs 6; M   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | AgProcAs 8; M          | AgProcAs 9; M   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | AgProcAs 11; M         | AgProcAs 12; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | AgProcAs 14; O         | MDSMethods 6; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The association procedure data exchange is correct</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                 |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                 |
+| <b>Other PICS</b>        | C_AG_OXP_002, C_AG_OXP_017                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |                 |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The PHD sends a message to associate to the simulated PHG, the expected fields sent by the PHD are: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = AarqApdu</li> <li><input type="checkbox"/> field-length =2 bytes</li> <li><input type="checkbox"/> field-value =0xE2 0x00.</li> </ol> </li> <li>b. assoc-version <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = AssociationVersion</li> <li><input type="checkbox"/> field-length =BITS-32</li> <li><input type="checkbox"/> field- value=0x80 0x00 0x00 0x00</li> </ol> </li> <li>c. data-proto-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = DataProtoId(INT-U16)</li> <li><input type="checkbox"/> field-length =2 bytes</li> <li><input type="checkbox"/> field- value=0x50 0x79 (20601)</li> </ol> </li> <li>d. protocol-version</li> </ol> </li> </ol> |                        |                 |
+
+- field- type = Protocol Version
+- field-length = 4 bytes
+- field- value= At least bit protocol-version2(1) is set to 1 (0x40 0x00 0x00 0x00 OR 0xC0 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 0x60 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)).
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• IF the PHD supports single response → Bit 8 will be set (data-req-supp-mode-single-rsp(8)).</li> <li>• If the PHD supports time unlimited data request → Bit 10 will be set (data-req-supp-mode-time-no-limit(10)).</li> </ul> <p>l. data-req-init-agent-count (DataReqModeCapab)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = INT-U8</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field.value = 0x01</li> </ul> <p>m. data-req-init-manager-count (DataReqModeCapab)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = INT-U8</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field.value = 0x00</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-045                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |  |
+| <b>TP label</b>          | PM Segment Object for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-10424] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | PMStrObjMeth 1; M      |  |
+| <b>Test purpose</b>      | Check that:<br>SABTE supports the Clear-Segments method with Confirmed mode                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_041 AND C_AG_OXP_071                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state and the PHD has at least one PM-Segment with data stored                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Take measurements with the PHD of a value that is stored on a PM-Segment.</li> <li>2. 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.</li> <li>3. The PHD issues a GET response with the PM-Store attributes, record the values of PMStoreCapab attribute.</li> <li>4. The simulated PHG shall send a Get-Segment-Info object action with segmSelection set to all-segments to check that there are no Segments in use.</li> <li>5. The simulated PHG sends a Clear-Segment to all segments: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> <li><input type="checkbox"/> SegmSelection = all-segments</li> </ul> </li> </ol> </li> <li>6. The PHD under test operation response: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Response   Confirmed Action,</li> </ul> </li> </ol> </li> </ol> |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> </ul> <p>7. Delay</p> <p>8. The simulated PHG sends a request for the PM-Segment Data with SegmSelection = all-segments to obtain all the segments:</p> <ul style="list-style-type: none"> <li>a. Data APDU           <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> SegmSelection = &lt;Instance number of the selected PM-Segment that contained data before the clear-segment action&gt;</li> </ul> </li> </ul> <p>9. The PHD issues an action response with the Data</p> <ul style="list-style-type: none"> <li>a. Data APDU           <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Response   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> TrigSegmXferRsp =               <ul style="list-style-type: none"> <li>• If pmsc-clear-segm-remove is NOT set THEN TrigSegmXferRsp = tsxr-fail-segm-empty</li> <li>• ELSE TrigSegmXferRsp = tsxr-fail-no-such-segment</li> </ul> </li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                          |                                                                                                                                                                                                                                                                                                                                     |                                                               |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-046                                                                                                                                                                                                                                                                                                       |                                                               |
+| <b>TP label</b>          | Operating State. PHG to PHD Maximum APDU Size                                                                                                                                                                                                                                                                                       |                                                               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                               | CommonCharac 3; M                                             |
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-10424]                                        |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                               | ComChar 2; M                                                  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Check that the total size of the response do not exceed of the maximum APDU size established by the specialization</p> <p>[AND]</p> <p>A SABTE 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 8192 octets</p> |                                                               |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_162                                                                                                                                                                                                                                                                                                       |                                                               |
+| <b>Other PICS</b>        | C_AG_OXP_041, C_AG_OXP_100                                                                                                                                                                                                                                                                                                          |                                                               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state                                                                                                                                                                                                                                                                 |                                                               |
+| <b>Test procedure</b>    | <p>1. The simulated PHG issues "Remote Operation Invoke   Get" command with:</p>                                                                                                                                                                                                                                                    |                                                               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ol style="list-style-type: none"> <li>a. Obj-handle set to 0 (to request for MDS object)</li> <li>b. attribute-id-list.count = 103</li> <li>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</li> </ol> <ol style="list-style-type: none"> <li>2. Check the response of the PHD.</li> <li>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.</li> <li>4. Check the response of the PHD.</li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• 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. <ul style="list-style-type: none"> <li>○ If the response is a get response, the total size of the response can not exceed the sum of the APDU sizes of the supported specializations (limited to an absolute limit of 64512 octets): <ul style="list-style-type: none"> <li>▪ Pulse Oximeter -&gt; 9216 octets</li> <li>▪ Weighing Scale -&gt; 896 octets</li> <li>▪ Glucose Meter -&gt; 5120 octets or 64512 octets if PHD supports PM-Store</li> <li>▪ Blood Pressure -&gt; 896 octets</li> <li>▪ Thermometer -&gt; 896 octets</li> <li>▪ Independent Activity Hub -&gt; 5120 octets</li> <li>▪ Cardiovascular -&gt; 64512 octets or 6624 octets PHD under test only supports Step Counter Profile</li> <li>▪ Strength -&gt; 64512 octets:</li> <li>▪ Adherence Monitor -&gt; 1024 octets</li> <li>▪ Peak Flow -&gt; 2030 octets</li> <li>▪ Body Composition Analyser -&gt; 7730 octets</li> <li>▪ Basic ECG/Simple ECG -&gt; 7168 octets or 64512 octets if PHD supports PM-Store</li> <li>▪ Basic ECG/Heart Rate -&gt; 1280 octets or 64512 octets if PHD supports PM-Store</li> <li>▪ International Normalized Ratio -&gt; 896 octets or 64512 if PHD supports PM-Store</li> <li>▪ Sleep apnoea breathing therapy equipment -&gt; 64512 octets.</li> </ul> </li> <li>○ In case it responds with a roer, the reason must not be protocol-violation (23)</li> </ul> </li> <li>• In step 4, the PHD must respond with a rors-cmip-get message.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                     |                                                                                                                   |                        |  |
+|---------------------|-------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/SABTE/BV-047                                                                                     |                        |  |
+| <b>TP label</b>     | Set Time (Absolute Time) SABTE                                                                                    |                        |  |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                       | [ISO/IEEE 11073-10424] |  |
+|                     | <b>Testable items</b>                                                                                             | MDSMethods 2; M        |  |
+| <b>Test purpose</b> | Check that:<br>If the PHD supports the [Absolute-Time-Stamp] attribute, the Set -Time method shall be implemented |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_009                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Test procedure</b>     | 1. The simulated PHG sends a SET action: <ul style="list-style-type: none"> <li><input type="checkbox"/> CHOICE = SetTimeInvoke</li> <li><input type="checkbox"/> action-type = MDC_ACT_SET_TIME</li> <li><input type="checkbox"/> the action-info-args are SetTimeInvoke <ul style="list-style-type: none"> <li>▪ date-time = &lt;century, year ≤ 99, month ≤ 12, day ≤ 31, hour ≤ 24, minute ≤ 60, second ≤ 60, sec-fractions ≤ 100&gt;</li> <li>▪ accuracy = 0</li> </ul> </li> </ul> 2. The PHD under test response shall be a rors-cmip-confirmed-action: <ul style="list-style-type: none"> <li><input type="checkbox"/> action-type = MDC_ACT_SET_TIME</li> <li><input type="checkbox"/> action-info-args shall be empty.</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/SABTE/BV-048                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |
+| <b>TP label</b>           | Set Time (Base Offset Time) SABTE                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-10424] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MDSMethods 4; M        |
+| <b>Test purpose</b>       | Check that:<br>If the PHD supports the [Base-Offset-Time-Stamp] attribute, the Set-Base-Offset-Time method shall be implemented                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_014                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |
+| <b>Test procedure</b>     | 1. The simulated PHG sends a SET action: <ul style="list-style-type: none"> <li><input type="checkbox"/> CHOICE = SetBOTimeInvoke</li> <li><input type="checkbox"/> action-type = MDC_ACT_SET_BO_TIME</li> <li><input type="checkbox"/> the action-info-args are SetBOTimeInvoke <ul style="list-style-type: none"> <li>▪ date-time = bo-seconds = 0x00 0x00 0x00 0x00, bo-fractions = 0x00 0x00, bo-time-offset = 0x3C</li> </ul> </li> </ul> 2. The PHD under test response shall be a rors-cmip-confirmed-action: <ul style="list-style-type: none"> <li><input type="checkbox"/> action-type = MDC_ACT_SET_BO_TIME</li> <li><input type="checkbox"/> action-info-args shall be empty.</li> </ul> |                        |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |
+
+|                           |                                                                                                                                                                                                                                |                        |  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/SABTE/BV-049                                                                                                                                                                                                  |                        |  |
+| <b>TP label</b>           | Compound apnoea hypopnoea index classification not supported                                                                                                                                                                   |                        |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                    | [ISO/IEEE 11073-10424] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                          | CAHI 10; M             |  |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>If a PHD does not support a classification, the corresponding value shall be reported as the special value Not a Number (NaN).</p>                                                                       |                        |  |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_162 AND C_AG_OXP_181 AND C_AG_SABTE_032                                                                                                                                                              |                        |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                |                        |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                           |                        |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>Make a Compound apnoea hypopnoea index measurement with a classification not supported</li> <li>Wait for the simulated PHG to receive the event report with the measurement.</li> </ol> |                        |  |
+| <b>Pass/Fail criteria</b> | The value of the uAHI, oAHI or cAHI measurements must be NaN.                                                                                                                                                                  |                        |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                |                        |  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/SABTE/BV-050                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |  |
+| <b>TP label</b>          | RT-SA data availability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-10424] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | RTSAObj 23; M          |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The RT-SA data shall be made available only through a scanner object or PM-Store object</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |  |
+| <b>Applicability</b>     | C_AG_OXP_162 AND (C_AG_SABTE_024 OR C_AG_SABTE_025 OR C_AG_SABTE_026) AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHG receives an association request from the PHD under test.</li> <li>The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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.</li> <li>Check that RT-SA object/s is/are present and record its/their object handle/s</li> <li>If the PHD supports PM-Store: <ol style="list-style-type: none"> <li>The simulated PHG sends a Get-Segment-Info object action for the PM-Store object with SegmSelection = all-segment.</li> <li>The PHD issues a response (rors-cmip-confirmed-action)with the PM-Segment</li> </ol> </li> </ol> |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>attributes it supports in the SegmentInfoList structure.</p> <p>7. Check that all RT-SA object/s handle/s are referenced in Scanner or PM-Store objects.</p> <ol style="list-style-type: none"> <li>a. If EpiCfgScanner object (MDC_MOC_SCAN_CFG_EPI) or PeriCfgScanner (MDC_MOC_SCAN_CFG_PERI) is present           <ol style="list-style-type: none"> <li>i. IF Attribute Scan-Handle-List is supported:               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SCAN_HANDLE_LIST</li> <li><input type="checkbox"/> attribute-type = HANDLEList</li> <li><input type="checkbox"/> attribute-value.length = &lt;Variable&gt;</li> <li><input type="checkbox"/> attribute-value = It must include references to RT-SA objects handles</li> </ul> </li> <li>ii. IF attribute Scan-Handle-Attr-Val-Map is supported:               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SCAN_HANDLE_ATTR_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = HANDLEAttrValMap</li> <li><input type="checkbox"/> attribute-value.count = N</li> <li><input type="checkbox"/> attribute-value.length = &lt;Variable&gt;</li> <li><input type="checkbox"/> attribute-value = It must include references to RT-SA objects handles</li> </ul> </li> </ol> </li> <li>b. If PM-Store object (MDC_MOC_VMO_PMSTORE) is present, then check the PM-Segment-Entry-Map of each PM-Segment.</li> </ol> <p>8. Check the MDS event reports sent by the PHD under test.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 7.a, all RT-SA objects implemented by the PHD under test must be referenced in Scan-Handle-List or Scan-Handle-Attr-Val-Map attributes.</li> <li>• In step 7.b, all RT-SA objects implemented by the PHD under test must be referenced (through PM-Segment-Entry-Map attribute) in at least one time in the set of PM-Segments implemented by PM-Store objects.</li> <li>• In step 8, the MDS event report sent by the PHD under test must not include RT-SA object observations.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+## 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.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-PHG PICS & PIXIT] Personal Health Gateway DG2016 PICS and PIXIT excel sheet v1.9.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-TCRL] Test Case Reference List\_DG2016\_v1.11.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-TI] Continua DG2016 PHD Testable items excel sheet v1.8.  
+<http://handle.itu.int/11.1002/2000/12067>
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.2-201808-I_PDF-E/raw.md b/marked/H/T-REC-H.845.2-201808-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..7135f5e995923a69f2fb16f16d08c3d4abf99e22
--- /dev/null
+++ b/marked/H/T-REC-H.845.2-201808-I_PDF-E/raw.md
@@ -0,0 +1,1841 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.845.2**
+
+(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  
+5B: Glucose meter**
+
+Recommendation ITU-T H.845.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        |
+| <b>Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN)</b> | <b>H.820–H.859</b> |
+| 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.2
+
+### Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5B: Glucose meter
+
+## Summary
+
+Recommendation ITU-T H.845.2 provides a test suite structure (TSS) and the test purposes (TPs) for glucose meters 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.845.2 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5B: Device Specializations. Personal Health Device (Glucose Meter) (Version 1.6, 2016-09-20), which 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 (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.845.2  | 2015-01-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/12263">11.1002/1000/12263</a> |
+| 2.0     | ITU-T H.845.2  | 2016-07-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12939">11.1002/1000/12939</a> |
+| 3.0     | ITU-T H.845.2  | 2017-04-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/13220">11.1002/1000/13220</a> |
+| 4.0     | ITU-T H.845.2  | 2018-08-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/13682">11.1002/1000/13682</a> |
+
+## Keywords
+
+Conformance testing, Continua Design Guidelines, e-health, glucose meter, IEEE 11073 device specialization, 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 <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 .....                            | 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 .....                   | 4    |
+| 7 Electronic attachment .....                  | 7    |
+| Annex A Test procedures.....                   | 8    |
+| A.1 Test purpose definition conventions.....   | 8    |
+| A.2 Subgroup 1.3.2: Glucose meter (GL) .....   | 10   |
+| Bibliography.....                              | 67   |
+
+**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
+
+This Recommendation is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5B: Device Specializations. Personal Health Device (Glucose Meter) (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_5B_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_5B_v1.2.doc" as a baseline and adds new features included in [b-CDG 2012]: <ul style="list-style-type: none"> <li>• New GM spec version</li> <li>• Max APDU size for GM, BCA and ECG</li> </ul>                                                                                          |
+| 1.4     | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_PAN-LAN_PART_5B_v1.3.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]: <ul style="list-style-type: none"> <li>• Adds glucose meter BLE</li> <li>• Adds BLE SSP support</li> <li>• Adds NFC new transport</li> <li>• Adds INR device specialization</li> </ul> |
+| 1.5     | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_PLT_PART_5B_v1.4.doc" as a baseline and adds new features included in Documentation Enhancements: <ul style="list-style-type: none"> <li>• "Other PICS" row added</li> </ul>                                                                                               |
+| 1.5     | 2015-07-01 | Initial release for Test Tool DG2015. It is the same version as "TSS&TP_DG2013_PLT_PART_5B_v1.4.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.6     | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2015_PLT_PART_5B_v1.5.doc" as a baseline and adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016]                                                                                                                                                                                                 |
+| 1.7     | 2018-02-27 | Initial release for Test Tool DG2017. It adds updates and new features included in [ISO/IEEE 11073-10417:2017]                                                                                                                                                                                                                                                       |
+
+## Recommendation ITU-T H.845.2
+
+### Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5B: Glucose meter
+
+# 1 Scope
+
+The scope of this Recommendation<sup>1</sup> is to provide a test suite structure (TSS) and the test purposes (TPs) for the Personal Health Devices (PHD) 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 TPs for the Personal Health Devices interface have been divided into the parts specified below. This Recommendation covers Part 5, subpart 5B.
+
+- 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
+
+---
+
+<sup>1</sup> 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.
+
+- 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 connected health systems: Introduction*.
+- [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/70739.html>
+- [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.  
+<https://www.iso.org/standard/66717.html> with  
+<https://www.iso.org/standard/71886.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. 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:
+
+|     |                                |
+|-----|--------------------------------|
+| DUT | Device Under Test              |
+| CDG | Continua Design Guidelines     |
+| CGM | Continuous Glucose Monitor     |
+| 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              |
+| SCR   | Static Conformance Review                             |
+| SDP   | Service Discovery Protocol                            |
+| 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 | [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 TPs for the PHD interface have been divided into the main subgroups specified below. Annex A describes the TPs for subgroup 1.3.2: (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 (PICSs) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded from <http://handle.itu.int/11.1002/2000/12067>. 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 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/<TT>/<DUT>/<GR>/<SGR>/<XX> – <NNN>). It is specified according to the naming convention defined below:
+  - Each TP identifier is introduced by the prefix "TP".
+  - <TT>: 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)
+  - <DUT>: This is the device under test
+    - PHD: Personal Health Device
+    - PHG: Personal Health Gateway
+  - <GR>: This identifies a group of test cases.
+  - <SGR>: This identifies a subgroup of test cases.
+  - <XX>: This identifies the type of testing
+    - BV: Valid behaviour test
+    - BI: Invalid behaviour test
+  - <NNN>: 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 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 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 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.2: Glucose meter (GL)
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                 |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-000_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                 |
+| <b>TP label</b>          | Get MDS Object for Glucose meter specialization: Mandatory, Conditional and Optional Attributes.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-10417] |                 |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | MDSGL Atr 1; M         | MDSGL Atr 2; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | MDSGL Atr 5; M         | MDSGL Atr 10; R |
+| <b>Test purpose</b>      | Check that:<br>The MDS Object contains the attributes specified for a Glucose Meter Personal Health Device (PHD).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                 |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |                 |
+| <b>Other PICSs</b>       | C_AG_GL_024, C_AG_GL_025, C_AG_GL_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                 |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated Personal Health Device (PHG) issues "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.</li> <li>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:<br/> MDS attributes: <ol style="list-style-type: none"> <li>a. Attribute System-Type must not be present.</li> <li>b. Mandatory attribute System-Type-Spec_List <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SYS_TYPE_SPEC_LIST</li> <li><input type="checkbox"/> attribute-type = TypeVerList</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes for each configuration supported</li> <li><input type="checkbox"/> attribute-value = {MDC_DEV_SPEC_PROFILE_GLUCOSE , 3} must be found in the list</li> </ul> </li> <li>c. Mandatory attribute System-model <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_MODEL (0x09 0x28)</li> <li><input type="checkbox"/> attribute-type = SystemModel</li> <li><input type="checkbox"/> attribute-value.length = &lt;Variable&gt;</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>• Manufacturer = Check against PIXIT I_AG_OXP_003</li> <li>• Model = Check against PIXIT I_AG_OXP_004</li> </ul> </li> </ul> </li> <li>d. Mandatory attribute Dev-Configuration-Id <ul style="list-style-type: none"> <li><input type="checkbox"/> IF C_AG_GL_024 THEN attribute-value = 0x06A5 (1701)</li> <li><input type="checkbox"/> IF C_AG_GL_025 THEN attribute-value = 0x06A6 (1702)</li> <li><input type="checkbox"/> IF C_AG_OXP_181 THEN attribute-value = &lt; between 0x4000 and 0x7FFF &gt;</li> </ul> </li> <li>e. Recommended attribute Base-Offset-Time <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> </li> </ol> </li> </ol> |                        |                 |
+
+|                           |                                                            |
+|---------------------------|------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure. |
+| <b>Notes</b>              |                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-000_B                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |  |
+| <b>TP label</b>          | MDS Configuration objects events for Glucose meter specialization.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [ISO/IEEE 11073-10417] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | MDSEvents 1; M         |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Glucose Meter PHD sends the MDS-Configuration-Event using a Confirmed event report and it includes the event-info ConfigReport</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |  |
+| <b>Other PICSSs</b>      | C_AG_OXP_010, , C_AG_GL_024, C_AG_GL_025, C_AG_GL_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = PrstApdu</li> <li><input type="checkbox"/> field-length =2 bytes</li> <li><input type="checkbox"/> field-value =0xE7 0x00</li> </ol> </li> <li>b. invoke-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = InvokeIDType</li> <li><input type="checkbox"/> field-length =INT-U16</li> <li><input type="checkbox"/> field- value =&lt;Not relevant for this test&gt;</li> </ol> </li> <li>c. message <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = roiv-cmip-confirmed-event-report</li> <li><input type="checkbox"/> field-length =two bytes</li> <li><input type="checkbox"/> field- value =0x01 0x01 (EventReportArgumentSimple)</li> </ol> </li> <li>d. obj-handle (EventReportArgumentSimple) <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = HANDLE</li> <li><input type="checkbox"/> field-length =INT-U16</li> </ol> </li> <li>e. event-time (EventReportArgumentSimple) <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = Relative Time</li> <li><input type="checkbox"/> field-length =INT-U32</li> <li><input type="checkbox"/> field-value = <ul style="list-style-type: none"> <li>• IF NOT C_AG_OXP_010 THEN value = 0xFF 0xFF 0xFF 0xFF</li> </ul> </li> </ol> </li> <li>f. event-type (EventReportArgumentSimple) <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = OID-Type</li> </ol> </li> </ol> </li> </ol> |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length =INT-U16</li> <li><input type="checkbox"/> field- value=0x0D 0x1C (MDC_NOTI_CONFIG)</li> </ul> <p>g. config-report-id (ConfigReport)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = ConfigId</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field value = &lt;It matches the tested configuration&gt; <ul style="list-style-type: none"> <li>• IF C_AG_GL_024 THEN attribute-value = 0x 06A5 (1701)</li> <li>• IF C_AG_GL_025 THEN attribute-value = 0x 06A6 (1702)</li> <li>• IF C_AG_OXP_181 THEN &lt;between 0x40 0x00 and 0x7F 0xFF &gt; for extended configuration.</li> </ul> </li> </ul> <p>h. obj-class ( ConfigReport → ConfigObjectList (ConfigObject))</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = OID-Type</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field- value = At least one MDC_MOC_VMO_METRIC_NU</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                 |
+|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|
+| <b>TP Id</b>         | TP/PLT/PHD/CLASS/GL/BV-000_C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                 |
+| <b>TP label</b>      | MDS objects events for Glucose meter specialization.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                 |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-10417] |                 |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | MDSEvents 3; M         | MDSEvents 4; M  |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MDSEvents 6; M         | MDSEvents 7; M  |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MDSEvents 9; M         | MDSEvents 10; M |
+|                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        | PMStoreObj 4; M |
+| <b>Test purpose</b>  | <p>Check that:</p> <p>Agent-initiated mode is supported for measurement data transmission and all types of event reports are used in confirmed mode</p> <p>[AND]</p> <p>The PHD sends the MDS-Dynamic-Data-Update-Fixed using a confirmed event report and it includes the event-info ScanReportInfoFixed</p> <p>[OR]</p> <p>The PHD sends the MDS-Dynamic-Data-Update-Var using a confirmed event report and it includes the event-info ScanReportInfoVar</p> <p>[OR]</p> <p>The PHD sends the MDS-Dynamic-Data-Update-MP-Fixed using a confirmed event report and it includes the event-info ScanReportInfoMPFixed</p> <p>[OR]</p> <p>The PHD sends the MDS-Dynamic-Data-Update-MP-Var using a confirmed event report and it includes the event-info ScanReportInfoMPVar</p> |                        |                 |
+| <b>Applicability</b> | C_AG_OXP_000 AND C_AG_OXP_178 AND (C_AG_OXP_182 OR C_AG_OXP_183 OR C_AG_OXP_184 OR C_AG_OXP_189)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                 |
+| <b>Other PICSSs</b>  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Take measurements for every supported object in the PHD under test.</li> <li>2. Wait to receive every event report and check: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = Event Report</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field- value=0x01 0x01 (EventReportArgumentSimple, confirmed)</li> </ol> </li> </ol> </li> </ol> <p>This field identifies the type of message sent by the PHD, for the confirmed event configuration, roiv-cmip-confirmed-event-report.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• Check that every received report is one of the following confirmed Data APDU</li> <li>• MDC_NOTI_SCAN_REPORT_FIXED</li> <li>• MDC_NOTI_SCAN_REPORT_MP_FIXED</li> <li>• MDC_NOTI_SCAN_REPORT_VAR</li> <li>• MDC_NOTI_SCAN_REPORT_MP_VAR</li> </ul>                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-001                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                  |
+| <b>TP label</b>          | Objects for Glucose meter specialization - Standard Configuration (1701 or 1702)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-10417] |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | BloodGL 1; M           | BloodGL 4; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | CtrlSol 1; M           | ContextMeal 4; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Blood glucose Numeric Object with Type MDC_CONC_GLU_UNDETERMINED_PLASMA is supported by a Glucose Meter PHD for Standard Configurations 1701 (0x06A5) and 1702 (0x06A6).</p> <p>[AND]</p> <p>Control solution Numeric Object is supported by a Glucose Meter PHD for Standard Configurations 1701 (0x06A5) and 1702 (0x06A6).</p> <p>[AND]</p> <p>Context meal Enumeration Object is supported by a Glucose Meter PHD for Standard Configuration 1702 (0x06A6)</p>                                                                                                                                                                   |                        |                  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND (NOT_C_AG_OXP_181)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                  |
+| <b>Other PICSs</b>       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                  |
+| <b>Initial condition</b> | The simulated PHG and the PHD are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is set to 0x06A5 (1701) OR 0x06A6 (1702), if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>5. Once the PHD under test sends a standard configuration, check that:</li> </ol> |                        |                  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>IF Dev-Config-Id = 0x06A5 THEN Attribute-List:</p> <p>a. attribute-value (ConfigReport → ConfigObjectList (ConfigObject) → Attribute List), this value depends on the attribute Type. The values we have to check are:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Blood glucose Object is present → MDC_PART_SCADA (0x00 0x02), MDC_CONC_GLU_UNDETERMINED_PLASMA (0x72 0x70)</li> <li><input type="checkbox"/> Control solution Object is present → MDC_PART_SCADA (0x00 0x02), MDC_CONC_GLU_CONTROL (0x71 0xD0)</li> </ul> <p>IF Dev-Config-Id = 0x06A5 THEN Attribute-List:</p> <p>b. attribute-value (ConfigReport → ConfigObjectList (ConfigObject) → Attribute List), this value depends on the attribute Type. The values we have to check are:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Blood glucose Object is present → MDC_PART_SCADA (0x00 0x02), MDC_CONC_GLU_UNDETERMINED_PLASMA (0x72 0x70)</li> <li><input type="checkbox"/> Control solution Object is present → MDC_PART_SCADA (0x00 0x02), MDC_CONC_GLU_CONTROL (0x71 0xD0)</li> <li><input type="checkbox"/> Context meal Object is present → MDC_PART_PHD_DM (0X00 0X80), MDC_CTX_T_GLU_MEAL (0x72 0x48)</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure and no other object listed.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |               |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |               |
+| <b>TP label</b>          | Objects for Glucose meter specialization - Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-10417] |               |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | BloodGL 1; M           | DevSenAn 3; R |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The Blood Glucose Numeric Object is supported by a Glucose Meter PHD.</p> <p>[AND]</p> <p>HbA1c, Context Exercise, Context Medication, Context Carbohydrates or Control Solution Numeric Objects can be implemented by the vendor.</p> <p>[AND]</p> <p>PHD should support Device and sensor status annunciation object to transmit these occurrences.</p> <p>[AND]</p> <p>In case that a blood glucose measurement needs to be further associated with meal, sample location, and tester information, the additional Enumeration objects, i.e. Context Carbohydrates, Context Sample Location and Context Tester can be used.</p> |                        |               |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |               |
+| <b>Other PICsS</b>       | C_AG_GL_001, C_AG_GL_002, C_AG_GL_003, C_AG_GL_004, C_AG_GL_005,<br>C_AG_GL_007, C_AG_GL_008, C_AG_GL_009, C_AG_GL_010, C_AG_GL_011,<br>C_AG_GL_012, C_AG_GL_013, C_AG_GL_014, C_AG_GL_015, C_AG_GL_016,<br>C_AG_GL_017, C_AG_GL_018, C_AG_GL_019, C_AG_GL_021                                                                                                                                                                                                                                                                                                                                                                                          |                        |               |
+| <b>Initial condition</b> | The simulated PHG and the PHD are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>3. The PHD responds with a "Remote Operation Invoke   Confirmed Event Report" message</li> </ol>                                                                                                                                                                                                                                                                                                                                          |                        |               |
+
+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.
+
+5. Once the PHD under test sends an extended configuration, check that:
+
+Attribute-List:
+
+a. attribute-value( ConfigReport → ConfigObjectList (ConfigObject)→Attribute List), this value depends on the attribute type. The values we have to check are:
+
+- Blood Glucose Numeric Object is present → MDC\_PART\_SCADA (0x00 0x02),
+  - IF C\_AG\_GL\_014 THEN MDC\_CONC\_GLU\_CAPILLARY\_WHOLEBLOOD (0x71 0xB8)
+  - IF C\_AG\_GL\_015 THEN MDC\_CONC\_GLU\_CAPILLARY\_PLASMA (0x71 0xBC)
+  - IF C\_AG\_GL\_016 THEN MDC\_CONC\_GLU\_VENOUS\_WHOLEBLOOD (0x71 0xC0)
+  - IF C\_AG\_GL\_017 THEN MDC\_CONC\_GLU\_VENOUS\_PLASMA (0x71 0xC4)
+  - IF C\_AG\_GL\_018 THEN MDC\_CONC\_GLU\_ARTERIAL\_WHOLEBLOOD (0x71 0xC8)
+  - IF C\_AG\_GL\_019 THEN MDC\_CONC\_GLU\_ARTERIAL\_PLASMA (0x71 0xCC)
+  - IF C\_AG\_GL\_012 THEN MDC\_CONC\_GLU\_UNDETERMINED\_WHOLEBLOOD (0x72 0x6C)
+  - IF C\_AG\_GL\_013 THEN MDC\_CONC\_GLU\_UNDETERMINED\_PLASMA (0x72 0x70)
+  - IF C\_AG\_GL\_021 THEN MDC\_CONC\_GLU\_ISF (0x71 0xD4)
+- Any of these objects may be present:
+  - IF C\_AG\_GL\_001 THEN Control Solution numeric Object is present → MDC\_PART\_SCADA (0x00 0x02), MDC\_CONC\_GLU\_CONTROL (0x71 0xD0)
+  - IF C\_AG\_GL\_002 THEN HbA1c numeric Object is present → MDC\_PART\_SCADA (0x00 0x02), MDC\_CONC\_HBA1C (0x71 0xDC)
+  - IF C\_AG\_GL\_003 THEN Context Exercise numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_CTX\_T\_GLU\_EXERCISE (0x71 0xE0)
+  - IF C\_AG\_GL\_004 THEN Context Medication numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_CTX\_T\_MEDICATION (0x72 0x04)
+  - IF C\_AG\_GL\_005 THEN Context Carbohydrates numeric Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_CTX\_T\_GLU\_CARB (0x71 0xE4)
+  - IF C\_AG\_GL\_007 THEN Device and Sensor annunciation status Enumeration Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_GLU\_METER\_DEV\_STATUS (0x71 0xD8)
+  - IF C\_AG\_GL\_008 THEN Context Meal enumeration Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_CTX\_T\_GLU\_MEAL (0x72 0x48)
+  - IF C\_AG\_GL\_009 THEN Context Sample Location enumeration Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_CTX\_T\_GLU\_SAMPLELOCATION (0x72 0x34)
+  - IF C\_AG\_GL\_010 THEN Context Tester enumeration Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_CTX\_T\_GLU\_TESTER (0x72 0x5C)
+  - IF C\_AG\_GL\_011 THEN Context Health enumeration Object is present → MDC\_PART\_PHD\_DM (0x00 0x80), MDC\_CTX\_T\_GLU\_HEALTH (0x72 0x1C)
+
+|                           |                                                            |
+|---------------------------|------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure. |
+| <b>Notes</b>              |                                                            |
+
+|                          |                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |               |               |
+|--------------------------|----------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-004                                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |               |               |
+| <b>TP Label</b>          | Blood Glucose Numeric Object - Standard Configuration (1701 or 1702) |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |               |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                          | [ISO/IEEE 11073-10417]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |               |               |
+|                          | <b>Testable items</b>                                                | BloodGL 2; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | BloodGL 4; M  | BloodGL 6; M  |
+|                          |                                                                      | BloodGL 8; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | BloodGL 10; M | BloodGL 12; C |
+|                          |                                                                      | BloodGL 14; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | BloodGL 18; R | BloodGL 20; M |
+|                          |                                                                      | BloodGL 22; C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | BloodGL 24; R | BloodGL 26; R |
+|                          |                                                                      | MeasDatTx 6;M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | BloodGL 31; M | BloodGL 32; M |
+| <b>Test purpose</b>      |                                                                      | Check that:<br>The Blood Glucose Numeric Object contains the attributes specified for Standard Configuration 0x06A5 or 0x06A6.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |               |               |
+| <b>Applicability</b>     |                                                                      | C_AG_OXP_000 AND C_AG_OXP_178 AND (NOT C_AG_OXP_181)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |               |               |
+| <b>Other PICSs</b>       |                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |               |               |
+| <b>Initial condition</b> |                                                                      | The simulated PHG and the PHD under are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |               |               |
+| <b>Test procedure</b>    |                                                                      | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set to 0x06A5 (1701) or 0x06A6 (1702); if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends a Standard Configuration, check that Blood Glucose Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_HANDLE</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x01</li> </ul> </li> <li>b. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_SCADA (0x00 0x02), MDC_CONC_GLU_UNDETERMINED_PLASMA (0x72 0x70)</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00</li> </ul> </li> </ol> </li> </ol> |               |               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• Bit 0 (mss-avail-intermittent(0)), must be set</li> <li>• Bit 1 (mss-avail-stored-data(1)), must be set</li> <li>• Bit 2 (mss-upd-aperiodic(2)), must be set</li> <li>• Bit 3 (mss-msmt-aperiodic(3)), must be set</li> <li>• Bit 9 (mss-acc-agent-initiated(9)), must be set</li> <li>• The other bits have to be 0.</li> </ul> <p>d. Mandatory attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_MILLI_G_PER_DL</li> </ul> <p>e. Mandatory attribute Attribute-Value-Map</p> <p>IF Dev-Config-Id = 0x06A5:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = AttrValMap (sequence of attribute-id(OID-Type) and attribute-length( INT-U16) )</li> <li><input type="checkbox"/> attribute-value.length=&lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value= MDC_ATTR_NU_VAL_OBS_BASIC<br/>MDC_ATTR_TIME_STAMP_ABS</li> </ul> <p>IF Dev-Config-Id = 0x06A6:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = AttrValMap (sequence of attribute-id(OID-Type) and attribute-length( INT-U16) )</li> <li><input type="checkbox"/> attribute-value.length=&lt;variable&gt;</li> </ul> <p>attribute-value= MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_TIME_STAMP_BO</p> <p>f. No other attribute shall be present at configuration.</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                     |                                                      |                        |               |
+|---------------------|------------------------------------------------------|------------------------|---------------|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/GL/BV-005                           |                        |               |
+| <b>TP label</b>     | Blood Glucose Numeric Object- Extended Configuration |                        |               |
+| <b>Coverage</b>     | <b>Spec</b>                                          | [ISO/IEEE 11073-10417] |               |
+|                     | <b>Testable items</b>                                | NumObj 3; C            | NumObj 5; R   |
+|                     |                                                      | NumObj 7; R            | NumObj 8; R   |
+|                     |                                                      | NumObj 12; R           | NumObj 22; R  |
+|                     |                                                      | NumObj 24; R           | BloodGL 5; M  |
+|                     |                                                      | BloodGL 9; M           | BloodGL 15; R |
+|                     |                                                      | BloodGL 25; R          | NumObj 25; R  |
+|                     |                                                      | NumObj 2; M            | NumObj 27; R  |
+| <b>Test purpose</b> | Check that:                                          |                        |               |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | The Blood Glucose Numeric Object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Other PICSs</b>       | C_AG_GL_012, C_AG_GL_013, C_AG_GL_014, C_AG_GL_015, C_AG_GL_016, C_AG_GL_017, C_AG_GL_018, C_AG_GL_019, C_AG_GL_021                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends an Extended Configuration, check that Blood Glucose Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_SCADA (0x00 0x02), followed by one of the next: <ul style="list-style-type: none"> <li>• IF C_AG_GL_014 THEN MDC_CONC_GLU_CAPILLARY_WHOLEBLOOD (0x71 0xB8)</li> <li>• IF C_AG_GL_015 THEN MDC_CONC_GLU_CAPILLARY_PLASMA (0x71 0xBC)</li> <li>• IF C_AG_GL_016 THEN MDC_CONC_GLU_VENOUS_WHOLEBLOOD (0x71 0xC0)</li> <li>• IF C_AG_GL_017 THEN MDC_CONC_GLU_VENOUS_PLASMA (0x71 0xC4)</li> <li>• IF C_AG_GL_018 THEN MDC_CONC_GLU_ARTERIAL_WHOLEBLOOD (0x71 0xC8)</li> <li>• IF C_AG_GL_019 THEN MDC_CONC_GLU_ARTERIAL_PLASMA (0x71 0xCC)</li> <li>• IF C_AG_GL_012 THEN MDC_CONC_GLU_UNDETERMINED_WHOLEBLOOD (0x72 0x6C)</li> <li>• IF C_AG_GL_013 THEN MDC_CONC_GLU_UNDETERMINED_PLASMA (0x72 0x70)</li> <li>• IF C_AG_GL_021 THEN MDC_CONC_GLU_ISF (0x71 0xD4)</li> </ul> </li> </ul> </li> <li>b. Not recommended Supplemental –Types Attribute <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes)</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 3 must be set (mss-msmt-aperiodic(3))</li> </ul> </li> </ul> </li> </ol> </li> </ol> |
+
+- Bit 9 must be set (mss-acc-agent-initiated(9))
+
+- Bit 12 may be set (mss-cat-manual(12)) if the reading is entered manually
+
+d. IF Not recommended attribute Metric-Structure-Small is present
+
+- attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+
+- attribute-type = MetricStructureSmall
+
+- attribute-value.length = <variable>(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8))))
+
+e. IF Not recommended attribute Measurement-Status is present
+
+- attribute-id = MDC\_ATTR\_MSMT\_STAT
+
+- attribute-type = MeasurementStatus (BITS-16)
+
+- attribute-value.length =2 bytes
+
+f. Conditional attribute Metric-Id is present
+
+- attribute-id = MDC\_ATTR\_ID\_PHYSIO
+
+- attribute-type = OID-Type (INT-U16)
+
+- attribute-value.length= 2 bytes
+
+g. IF Not recommended attribute Metric-Id-List is present
+
+- attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+
+- attribute-type = MetricIdList
+
+- attribute-value.length= SEQUENCE OF OID-Type (INT-U16)
+
+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
+
+i. 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 OR  
+MDC\_DIM\_MILLI\_MOLE\_PER\_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
+
+k. IF recommended attribute Base-Offset-Time is present
+
+- attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+
+- attribute-type = BaseOffsetTime
+
+- attribute-value.length = 8 bytes
+
+l. IF Not recommended attribute Relative-Time-Stamp is present
+
+- attribute-id = MDC\_ATTR\_TIME\_STAMP\_REL
+
+- attribute-type = RelativeTime(INT-U32)
+
+- attribute-value.length = 4 bytes
+
+m. IF Not recommended attribute Measure-Active-Period
+
+- attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE
+
+- attribute-type = FLOAT type
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li>n. IF Not recommended Compound-Simple-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_SIMP</li> <li><input type="checkbox"/> attribute-type = SimpleNuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt;</li> </ul> </li> <li>o. IF Not recommended attribute Compound-Basic-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> </li> <li>p. IF Not recommended attribute Compound-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS</li> <li><input type="checkbox"/> attribute-type = NuObsValue</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> </li> <li>q. Not recommended attribute Compound-Nu-Observed-Value <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_SIMP</li> <li><input type="checkbox"/> attribute-type = NuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> </li> <li>r. IF Recommended attribute Accuracy is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                      |                                                                                                       |                        |              |              |
+|----------------------|-------------------------------------------------------------------------------------------------------|------------------------|--------------|--------------|
+| <b>TP Id</b>         | TP/PLT/PHD/CLASS/GL/BV-006                                                                            |                        |              |              |
+| <b>TP label</b>      | HbA1c Numeric Object - Extended Configuration                                                         |                        |              |              |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                           | [ISO/IEEE 11073-10417] |              |              |
+|                      | <b>Testable items</b>                                                                                 | NumObj 3; C            | NumObj 4; M  | NumObj 5; R  |
+|                      |                                                                                                       | NumObj 6; R            | NumObj 7; R  | NumObj 8; R  |
+|                      |                                                                                                       | NumObj 9; R            | NumObj 12; R | NumObj 16; O |
+|                      |                                                                                                       | NumObj 17; O           | NumObj 20; R | NumObj 22; R |
+|                      |                                                                                                       | NumObj 23; R           | NumObj 24; R | NumObj 25; R |
+|                      |                                                                                                       | HbA1c 1; M             | HbA1c 2; M   | HbA1c 3; M   |
+|                      |                                                                                                       | HbA1c 4; M             | HbA1c 5; C   | NumObj 2; M  |
+|                      |                                                                                                       | HbA1c 6; R             |              |              |
+| <b>Test purpose</b>  | Check that:<br>The HbA1c Numeric Object contains the attributes specified for Extended Configuration. |                        |              |              |
+| <b>Applicability</b> | C_AG_OXP_000 AND C_AG_OXP_178 AND C_AG_OXP_181 AND C_AG_GL_002                                        |                        |              |              |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICs</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is in the extended range, if it is not, the simulated PHG must respond with an "unsupported-config" and wait for a new configuration.</li> <li>5. Once the PHD under test sends an extended configuration, check that HbA1c Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_SCADA (0x00 0x02), MDC_CONC_HBA1C (0x71 0xDC)</li> </ol> </li> <li>b. Not recommended Supplemental –Types Attribute <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 3 must be set (mss-msmt-aperiodic(3))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> <li>• Bit 12 may be set (mss-cat-manual(12)) if the reading is entered manually</li> </ul> </li> </ol> </li> <li>d. IF Not recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))</li> </ol> </li> <li>e. IF Not recommended attribute Measurement-Status is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> </ol> </li> <li>f. Conditional attribute Metric-Id is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length= 2 bytes</li> <li><input type="checkbox"/> 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</li> </ol> </li> </ol> </li> </ol> |
+
+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.
+
+g. IF Not recommended attribute Metric-Id-List is present
+
+- attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+- attribute-type = MetricIdList
+- attribute-value.length= SEQUENCE OF OID-Type (INT-U16)
+- 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.
+
+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
+
+i. 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
+
+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
+
+k. Conditional attribute Absolute-Time-Stamp
+
+- attribute-id = MDC\_ATTR\_TIME\_STAMP\_ABS
+- attribute-type = AbsoluteTime
+- attribute-value.length = 8 bytes
+
+l. IF Recommended attribute Base-Offset-Time is present
+
+- attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+- attribute-type = BaseOffsetTime
+- attribute-value.length = 8 bytes
+
+m. Optional attribute Relative-Time-Stamp
+
+- attribute-id = MDC\_ATTR\_TIME\_STAMP\_REL
+- attribute-type = RelativeTime (INT-U32)
+- attribute-value.length = 4 bytes
+
+n. Conditional attribute HiRes-Time-Stamp
+
+- attribute-id = MDC\_ATTR\_TIME\_STAMP\_REL\_HI\_RES
+- attribute-type = HighResRelativeTime
+- attribute-value.length = OCTET STRING (SIZE(8))
+
+o. 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 =<variable>
+
+p. IF PHD supports fixed or variable format MDS event report and it does not support PM-Store THEN Mandatory attribute Basic-Nu-Observed-Value
+
+- attribute-id = MDC\_ATTR\_NU\_VAL\_OBS\_BASIC
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> <li>q. IF Not recommended attribute Compound-Basic-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> </li> <li>r. IF Not recommended attribute Compound-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS</li> <li><input type="checkbox"/> attribute-type = NuObsValue</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> </li> <li>s. Not recommended attribute Compound-Nu-Observed-Value <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_SIMP</li> <li><input type="checkbox"/> attribute-type = NuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> </li> <li>t. Recommended attribute Accuracy <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                      |                                                                                                                  |                        |                |                |
+|----------------------|------------------------------------------------------------------------------------------------------------------|------------------------|----------------|----------------|
+| <b>TP Id</b>         | TP/PLT/PHD/CLASS/GL/BV-007                                                                                       |                        |                |                |
+| <b>TP label</b>      | Context Exercise Numeric Object - Extended Configuration                                                         |                        |                |                |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                      | [ISO/IEEE 11073-10417] |                |                |
+|                      | <b>Testable items</b>                                                                                            | NumObj 3; C            | NumObj 4; M    | NumObj 5; R    |
+|                      |                                                                                                                  | NumObj 6; R            | NumObj 7; R    | NumObj 8; R    |
+|                      |                                                                                                                  | NumObj 9; R            | NumObj 12; R   | NumObj 16; O   |
+|                      |                                                                                                                  | NumObj 17; O           | NumObj 20; R   | NumObj 22; R   |
+|                      |                                                                                                                  | NumObj 23; R           | NumObj 24; R   | NumObj 25; R   |
+|                      |                                                                                                                  | ContextEx 1; M         | ContextEx 2; M | ContextEx 3; C |
+|                      |                                                                                                                  | ContextEx 4; M         | ContextEx 5; M | NumObj 2; M    |
+|                      |                                                                                                                  | ContextEx 6; M         | ContextEx 7; R |                |
+| <b>Test purpose</b>  | Check that:<br>The Context Exercise Numeric Object contains the attributes specified for Extended Configuration. |                        |                |                |
+| <b>Applicability</b> | C_AG_OXP_000 AND C_AG_OXP_178 AND C_AG_OXP_181 AND C_AG_GL_003                                                   |                        |                |                |
+| <b>Other PICSSs</b>  | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                         |                        |                |                |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is in the extended range, if it is not, the simulated PHG must respond with an "unsupported-config" and wait for a new configuration.</li> <li>5. Once the PHD under test sends an Extended Configuration, check that Context Exercise Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x02),<br/>MDC_CTXT_GLU_EXERCISE (0x71 0xE0)</li> </ol> </li> <li>b. Not recommended Supplemental-Types Attribute <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes)</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 3 must be set (mss-msmt-aperiodic(3))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> <li>• Bit 12 must be set (mss-cat-manual(12)) if the reading is entered manually</li> </ul> </li> </ol> </li> <li>d. IF Not recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))</li> </ol> </li> <li>e. IF Not recommended attribute Measurement-Status is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus(BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ol> </li> <li>f. Conditional attribute Metric-Id is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length= 2 bytes</li> <li><input type="checkbox"/> 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.</li> </ol> </li> </ol> </li> </ol> |
+
+- g. 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)
+  - 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.
+- 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
+- i. 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
+- 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
+- k. Conditional attribute Absolute-Time-Stamp
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_ABS
+  - attribute-type = AbsoluteTime
+  - attribute-value.length = 8 bytes
+- l. IF Recommended attribute Base-Offset-Time is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+  - attribute-type = BaseOffsetTime
+  - attribute-value.length = 8 bytes
+- m. Optional attribute Relative-Time-Stamp
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_REL
+  - attribute-type = RelativeTime (INT-U32)
+  - attribute-value.length = 4 bytes
+- n. Conditional attribute HiRes-Time-Stamp
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_REL\_HI\_RES
+  - attribute-type = HighResRelativeTime
+  - attribute-value.length = OCTET STRING (SIZE(8))
+- o. Mandatory attribute Measure-Active-Period
+  - attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE
+  - attribute-type = FLOAT type
+  - attribute-value.length = 4 bytes
+- p. 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 = <variable>
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>q. IF the PHD supports fixed or variable format MDS event report and it does not support PM-Store THEN Mandatory attribute Basic-Nu-Observed-Value</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value= value within the range:[0,100]</li> </ul> <p>r. IF Not recommended attribute Compound-Basic-Nu-Observed-Value is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> <p>s. IF Not recommended attribute Compound-Nu-Observed-Value is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS</li> <li><input type="checkbox"/> attribute-type = NuObsValue</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> <p>t. Not recommended attribute Compound-Nu-Observed-Value</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_SIMP</li> <li><input type="checkbox"/> attribute-type = NuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> <p>u. Recommended attribute Accuracy</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                     |                                                            |                        |                 |
+|---------------------|------------------------------------------------------------|------------------------|-----------------|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/GL/BV-008                                 |                        |                 |
+| <b>TP label</b>     | Context Medication Numeric Object - Extended Configuration |                        |                 |
+| <b>Coverage</b>     | <b>Spec</b>                                                | [ISO/IEEE 11073-10417] |                 |
+|                     | <b>Testable items</b>                                      | NumObj 3; C            | NumObj 4; M     |
+|                     |                                                            | NumObj 6; R            | NumObj 8; R     |
+|                     |                                                            | NumObj 12; R           | NumObj 16; O    |
+|                     |                                                            | NumObj 20; R           | NumObj 22; R    |
+|                     |                                                            | NumObj 24; R           | NumObj 25; R    |
+|                     |                                                            | ContextMed 2; M        | ContextMed 3; M |
+|                     |                                                            | ContextMed 6; M        | NumObj 2; M     |
+|                     |                                                            | ContextMed 8; R        |                 |
+| <b>Test purpose</b> | Check that:                                                |                        |                 |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | The Context Medication Numeric Object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND C_AG_OXP_181 AND C_AG_GL_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Other PICSSs</b>      | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is in the extended range, if it is not, the simulated PHG must respond with an "unsupported-config" and wait for a new configuration.</li> <li>5. Once the PHD under test sends an Extended Configuration, check that Context Exercise Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80),<br/>MDC_CTXT_MEDICATION (0x72 0x04)</li> </ol> </li> <li>b. Not recommended Supplemental –Types Attribute <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 3 must be set (mss-msmt-aperiodic(3))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> <li>• Bit 12 may be set (mss-cat-manual(12)) if the reading is entered manually</li> </ul> </li> </ol> </li> <li>d. IF Not recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8))))</li> </ol> </li> <li>e. Not recommended attribute Measurement-Status <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus(BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ol> </li> <li>f. Mandatory attribute Metric-Id <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> </ol> </li> </ol> </li> </ol> |
+
+- attribute-type = OID-Type(INT-U16)
+- attribute-value.length= 2 bytes
+- attribute-value = One of the following
+  - MDC\_CTXT\_MEDICATION\_RAPIDACTING (0x72 0x08)
+  - MDC\_CTXT\_MEDICATION\_SHORTACTING (0x72 0x0C)
+  - MDC\_CTXT\_MEDICATION\_INTERMEDIATEACTING (0x72 0x10)
+  - MDC\_CTXT\_MEDICATION\_LONGACTING (0x72 0x14)
+  - MDC\_CTXT\_MEDICATION\_PREMIX (0x72 0x18)
+- 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
+- h. 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 OR MDC\_DIM\_MILLI\_L OR MDC\_DIM\_INTL\_UNIT
+- 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
+- j. Conditional attribute Absolute-Time-Stamp
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_ABS
+  - attribute-type = AbsoluteTime
+  - attribute-value.length = 8 bytes
+- k. IF Recommended attribute Base-Offset-Time is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+  - attribute-type = BaseOffsetTime
+  - attribute-value.length = 8 bytes
+- l. Optional attribute Relative-Time-Stamp
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_REL
+  - attribute-type = RelativeTime (INT-U32)
+  - attribute-value.length = 4 bytes
+- m. Conditional attribute HiRes-Time-Stamp
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_REL\_HI\_RES
+  - attribute-type = HighResRelativeTime
+  - attribute-value.length = OCTET STRING (SIZE(8))
+- n. Not recommended attribute Measure-Active-Period
+  - attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE
+  - attribute-type = FLOAT type
+  - attribute-value.length = 4 bytes
+- o. IF Not recommended Compound-Simple-Nu-Observed-Value is present
+  - attribute-id = MDC\_ATTR\_NU\_CMPD\_VAL\_OBS\_SIMP
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = SimpleNuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> p. IF the PHD supports fixed or variable format MDS event report and it does not support PM-Store THEN Mandatory attribute Basic-Nu-Observed-Value <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> q. IF Not recommended attribute Compound-Basic-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> r. IF Not recommended attribute Compound-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS</li> <li><input type="checkbox"/> attribute-type = NuObsValue</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> s. Not recommended attribute Compound-Nu-Observed-Value <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_SIMP</li> <li><input type="checkbox"/> attribute-type = NuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> t. Recommended attribute Accuracy <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+|                 |                                                               |                        |                  |                  |
+|-----------------|---------------------------------------------------------------|------------------------|------------------|------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/GL/BV-009                                    |                        |                  |                  |
+| <b>TP label</b> | Context Carbohydrates Numeric Object - Extended Configuration |                        |                  |                  |
+| <b>Coverage</b> | <b>Spec</b>                                                   | [ISO/IEEE 11073-10417] |                  |                  |
+|                 | <b>Testable items</b>                                         | NumObj 3; C            | NumObj 4; M      | NumObj 5; R      |
+|                 |                                                               | NumObj 6; R            | NumObj 8; R      | NumObj 9; R      |
+|                 |                                                               | NumObj 12; R           | NumObj 16; O     | NumObj 17; O     |
+|                 |                                                               | NumObj 20; R           | NumObj 22; R     | NumObj 23; R     |
+|                 |                                                               | NumObj 24; R           | NumObj 25; R     | ContextCarb 1; M |
+|                 |                                                               | ContextCarb 2; M       | ContextCarb 3; M | ContextCarb 4; C |
+|                 |                                                               | ContextCarb 5; M       | NumObj 2; M      | ContextCarb 6; M |
+|                 |                                                               | ContextCarb 7; R       |                  |                  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>      | Check that:<br>The Context Carbohydrates Numeric Object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND C_AG_OXP_181 AND C_AG_GL_005                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Other PICsS</b>       | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is in the extended range, if it is not, the simulated PHG must respond with an "unsupported-config" and wait for a new configuration.</li> <li>5. Once the PHD under test sends an extended configuration, check that Context Carbohydrates Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value =MDC_PART_PHD_DM (0x00 0x80), MDC_CTXT_GLU_CARBO (0x71 0xE4)</li> </ol> </li> <li>b. Not recommended Supplemental-Types Attribute <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be(mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 3 must be set (mss-msmt-aperiodic(3))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> <li>• Bit 12 may be set (mss-cat-manual(12)) if the reading is entered manually</li> </ol> </li> </ol> </li> <li>d. IF Not recommended attribute Metric-Structure-Small is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8))))</li> </ol> </li> <li>e. Not recommended attribute Measurement-Status <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus(BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ol> </li> <li>f. Mandatory attribute Metric-Id</li> </ol> </li> </ol> |
+
+- attribute-id = MDC\_ATTR\_ID\_PHYSIO
+- attribute-type = OID-Type(INT-U16)
+- attribute-value.length= 2 bytes
+- attribute-value = One of the following
+  - MDC\_CTXT\_GLU\_CARB\_BREAKFAST (0x71 0xE8)
+  - MDC\_CTXT\_GLU\_CARB\_LUNCH (0x71 0xEC)
+  - MDC\_CTXT\_GLU\_CARB\_DINNER (0x71 0xF0)
+  - MDC\_CTXT\_GLU\_CARB\_SNACK (0x71 0xF4)
+  - MDC\_CTXT\_GLU\_CARB\_DRINK (0x71 0xF8)
+  - MDC\_CTXT\_GLU\_CARB\_SUPPER (0x71 0xFC)
+  - MDC\_CTXT\_GLU\_CARB\_BRUNCH (0x72 0x00)
+  - MDC\_CTXT\_GLU\_CARB\_UNDETERMINED (0x71 0xE5)
+  - MDC\_CTXT\_GLU\_CARB\_OTHER (0x71 0xE6)
+  - MDC\_CTXT\_GLU\_CARB\_NO\_ENTRY (0x71 0xE7)
+  - MDC\_CTXT\_GLU\_CARB\_NO\_INGESTION (0x71 0xE9)
+
+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
+
+h. 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\_G
+
+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
+
+j. Conditional attribute Absolute-Time-Stamp
+
+- attribute-id = MDC\_ATTR\_TIME\_STAMP\_ABS
+- attribute-type = AbsoluteTime
+- attribute-value.length = 8 bytes
+
+k. IF Recommended attribute Base-Offset-Time is present
+
+- attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+- attribute-type = BaseOffsetTime
+- attribute-value.length = 8 bytes
+
+l. Optional attribute Relative-Time-Stamp
+
+- attribute-id = MDC\_ATTR\_TIME\_STAMP\_REL
+- attribute-type = RelativeTime (INT-U32)
+- attribute-value.length = 4 bytes
+
+m. Conditional attribute HiRes-Time-Stamp
+
+- attribute-id = MDC\_ATTR\_TIME\_STAMP\_REL\_HI\_RES
+- attribute-type = HighResRelativeTime
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value.length = OCTET STRING (SIZE(8))</li> <li>n. Not recommended attribute Measure-Active-Period <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT type</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> <li>o. IF Not recommended Compound-Simple-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_SIMP</li> <li><input type="checkbox"/> attribute-type = SimpleNuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> </li> <li>p. IF the PHD supports fixed or variable format MDS event report and it does not support PM-Store THEN Mandatory attribute Basic-Nu-Observed-Value <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValue</li> <li><input type="checkbox"/> attribute-value.length = SFLOAT-Type (INT-U16)</li> </ul> </li> <li>q. IF Not recommended attribute Compound-Basic-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> </li> <li>r. IF Not recommended attribute Compound-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_VAL_OBS</li> <li><input type="checkbox"/> attribute-type = NuObsValue</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> </li> <li>s. IF Not recommended attribute Compound-Nu-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_SIMP</li> <li><input type="checkbox"/> attribute-type = NuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> </li> <li>t. Recommended attribute Accuracy <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                 |                                                                         |                        |               |               |
+|-----------------|-------------------------------------------------------------------------|------------------------|---------------|---------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/GL/BV-010                                              |                        |               |               |
+| <b>TP label</b> | Control Solution Numeric Object - Standard Configuration (1701 or 1702) |                        |               |               |
+| <b>Coverage</b> | <b>Spec</b>                                                             | [ISO/IEEE 11073-10417] |               |               |
+|                 | <b>Testable items</b>                                                   | CtrlSol 2; M           | CtrlSol 4; M  | CtrlSol 5; M  |
+|                 |                                                                         | CtrlSol 6; M           | CtrlSol 8; M  | CtrlSol 10; M |
+|                 |                                                                         | CtrlSol 12; M          | CtrlSol 16; R | CtrlSol 18; M |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |               |  |  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--|--|
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | CtrlSol 19; R |  |  |
+| <b>Test purpose</b>      | Check that:<br>The Control Solution Numeric Object contains the attributes specified for Standard Configuration 0x06A5 or 0x06A6.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |               |  |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND (NOT C_AG_OXP_181)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |               |  |  |
+| <b>Other PICSSs</b>      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |               |  |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |               |  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set to 0x06A5 (1701) or 0x06A6 (1702); if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends a standard configuration, check that Control Solution Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_HANDLE</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x02</li> </ul> </li> <li>b. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_SCADA (0x00 0x02), MDC_CONC_GLU_CONTROL (0x71 0xD0).</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 0 (mss-avail-intermittent(0)), must be set</li> <li>• Bit 1 (mss-avail-stored-data(1)), must be set</li> <li>• Bit 2 (mss-upd-aperiodic(2)), must be set</li> <li>• Bit 3 (mss-msmt-aperiodic(3)), must be set</li> <li>• Bit 9 (mss-acc-agent-initiated(9)), must be set</li> <li>• The other bits have to be 0.</li> </ul> </li> </ul> </li> <li>d. Mandatory attribute Metric-Id <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = MDC_CONC_GLU_CONTROL_LEVEL_UNDETERMINED (0x72 0x80)</li> </ul> </li> <li>e. Mandatory attribute Unit-Code <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> </ul> </li> </ol> </li> </ol> |               |  |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_MILLI_G_PER_DL</li> </ul> <p>f. Mandatory attribute Attribute-Value-Map</p> <p>IF Dev-Config-Id = 0x06A5:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = AttrValMap (sequence of attribute-id(OID-Type) and attribute-length( INT-U16) )</li> <li><input type="checkbox"/> attribute-value.length=&lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value= MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_ID_PHYSIO<br/>MDC_ATTR_TIME_STAMP_ABS</li> </ul> <p>IF Dev-Config-Id = 0x06A6:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = AttrValMap (sequence of attribute-id(OID-Type) and attribute-length( INT-U16) )</li> <li><input type="checkbox"/> attribute-value.length=&lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value= MDC_ATTR_NU_VAL_OBS_BASIC MDC_ATTR_ID_PHYSIO<br/>MDC_ATTR_TIME_STAMP_BO</li> </ul> <p>g. IF Recommended attribute Base-Offset-Time is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> <p>h. No other attribute shall be present at configuration.</p> |
+| <b>Pass/Fail criteria</b> | All checked values are specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |               |              |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|--------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-010_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |               |              |
+| <b>TP label</b>          | Control Solution Numeric Object - Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |               |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-10417] |               |              |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | CtrlSol 4; M           | CtrlSol 5; M  | CtrlSol 7; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | CtrlSol 17; M          | CtrlSol 20; R |              |
+| <b>Test purpose</b>      | Check that:<br>The Control Solution Numeric Object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |               |              |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND C_AG_GL_001 AND C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |               |              |
+| <b>Other PICsS</b>       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |               |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |               |              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>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.</li> <li>3. Check that the field Dev-Config-Id is set in the extended range; if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> </ol> |                        |               |              |
+
+4. Once the PHD under test sends an extended configuration, check that Control Solution Object attributes are:
+- a. Mandatory attribute Type
+    - attribute-id = MDC\_ATTR\_ID\_TYPE
+    - attribute-type = TYPE
+    - attribute-value = MDC\_PART\_SCADA (0x00 0x02),  
+MDC\_CONC\_GLU\_CONTROL (0x71 0xD0).
+  - b. Not recommended Supplemental –Types Attribute
+    - attribute-id = MDC\_ATTR\_SUPPLEMENTAL\_TYPES
+    - attribute-type = SupplementalTypeList
+    - attribute-value.length =<variable> (Sequence of TYPE (TYPE.length= 4 bytes
+  - 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 3 must be set (mss-msmt-aperiodic(3))
+      - Bit 9 must be set (mss-acc-agent-initiated(9))
+  - d. IF Not recommended attribute Metric-Structure-Small is present
+    - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+    - attribute-type = MetricStructureSmall
+    - attribute-value.length = <variable>(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))
+  - e. IF Not recommended attribute Measurement-Status is present
+    - attribute-id = MDC\_ATTR\_MSMT\_STAT
+    - attribute-type = MeasurementStatus (BITS-16)
+    - attribute-value.length =2 bytes
+  - f. Mandatory attribute Metric-Id is present
+    - attribute-id = MDC\_ATTR\_ID\_PHYSIO
+    - attribute-type = OID-Type (INT-U16)
+    - attribute-value.length= 2 bytes
+    - attribute-value = One of the following
+      - MDC\_CONC\_GLU\_CONTROL\_LEVEL\_LOW (0x72 0x74)
+      - MDC\_CONC\_GLU\_CONTROL\_LEVEL\_MEDIUM (0x72 0x78)
+      - MDC\_CONC\_GLU\_CONTROL\_LEVEL\_HIGH (0x72 0x7C)
+      - MDC\_CONC\_GLU\_CONTROL\_LEVEL\_UNDETERMINED (0x72 0x80)
+  - g. IF Not recommended attribute Metric-Id-List is present
+    - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIST
+    - attribute-type = MetricIdList
+    - attribute-value.length= SEQUENCE OF OID-Type (INT-U16)
+  - 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
+- i. 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 OR  
+MDC\_DIM\_MILLI\_MOLE\_PER\_L
+- j. IF Recommended attribute Base-Offset-Time is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+  - attribute-type = BaseOffsetTime
+  - attribute-value.length = 8 bytes
+- k. 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
+- l. IF Not recommended attribute Relative-Time-Stamp is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_REL
+  - attribute-type = RelativeTime(INT-U32)
+  - attribute-value.length = 4 bytes
+- m. IF Not recommended attribute Measure-Active-Period
+  - attribute-id = MDC\_ATTR\_TIME\_PD\_MSMT\_ACTIVE
+  - attribute-type = FLOAT type
+  - attribute-value.length = 4 bytes
+- n. IF Not recommended attribute Compound-Simple-Nu-Observed-Value is present
+  - attribute-id = MDC\_ATTR\_NU\_CMPD\_VAL\_OBS\_SIMP
+  - attribute-type = SimpleNuObsValueCmp
+  - attribute-value.length =<variable>
+- o. 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>
+- p. IF Not recommended attribute Compound-Nu-Observed-Value is present
+  - attribute-id = MDC\_ATTR\_NU\_VAL\_OBS
+  - attribute-type = NuObsValue
+  - attribute-value.length = <variable>
+- q. Not recommended attribute Compound-Nu-Observed-Value
+  - attribute-id = MDC\_ATTR\_NU\_CMPD\_VAL\_OBS\_SIMP
+  - attribute-type = NuObsValueCmp
+  - attribute-value.length = <variable>
+- r. IF Recommended attribute Accuracy is present
+  - attribute-id = MDC\_ATTR\_NU\_ACCUR\_MSMT
+  - attribute-type = FLOAT-Type (INT-U32)
+  - attribute-value.length = 4 bytes
+
+|                           |                                                            |
+|---------------------------|------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure. |
+| <b>Notes</b>              |                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                |                |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------|----------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-011                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                |                |
+| <b>TP label</b>          | Device and Sensor annunciation status Enumeration Object - Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                |                |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [ISO/IEEE 11073-10417] |                |                |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | EnumObj 3; R           | DevSenAn 1; M  | DevSenAn 5; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | DevSenAn 6; M          | DevSenAn 7; O  | DevSenAn 8; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | DevSenAn 11; R         | DevSenAn 12; R | DevSenAn 13; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | DevSenAn 15; R         | DevSenAn 21; O | DevSenAn 22; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | DevSenAn 23; R         | DevSenAn 24; R | DevSenAn 25; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | DevSenAn 26; O         | DevSenAn 28; O | DevSenAn 9; O  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | DevSenAn 10; R         | EnumObj 2; R   | EnumObj 4; R   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | EnumObj 5; R           | EnumObj 19; O  | DevSenAn 30; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | DevSenAn 30; R         |                |                |
+| <b>Test purpose</b>      | Check that:<br>Device and Sensor annunciation status Enumeration Object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                |                |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND C_AG_OXP_181 AND C_AG_GL_007                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                |                |
+| <b>Other PICSs</b>       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                |                |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                |                |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is in the extended range, if it is not, the simulated PHG must respond with an "unsupported-config" and wait for a new configuration.</li> <li>5. Once the PHD under test sends an extended configuration, check that all Device and Sensor annunciation status Objects have: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80),<br/>MDC_GLU_METER_DEV_STATUS (0x71 0xD8)</li> </ul> </li> <li>b. IF Not recommended attribute Supplemental-Types is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt;(Sequence of TYPE (TYPE.length= 4 bytes))</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec_Small</li> </ol> </li> </ol> |                        |                |                |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 3 must be set (mss-msmt-aperiodic(3))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> </ul> </li> <li>d. IF Not recommended attribute Metric-Structure-Small is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length = 1byte(INT-U8) + ms-comp-no = 1byte(INT-U8))))</li> </ul> </li> <li>e. Optional attribute Measurement-Status <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus(BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>f. IF Not recommended attribute Metric-Id is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = Only one attribute of Metric-Id and Metric-Id-List shall be present.</li> </ul> </li> <li>g. IF Not recommended attribute Metric-Id is present-List <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIS</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value.length= &lt;variable&gt;(SEQUENCE OF OID-Type (INT-U16))</li> </ul> </li> <li>h. IF Not recommended attribute Metric-Id-Partition is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>i. IF Not recommended attribute Unit-Code is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>j. IF Not recommended attribute Source-Handle-Reference is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>k. IF Recommended attribute Base-Offset-Time is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> </ul> |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>l. Optional attribute Enum-Observed-Value-Simple-OID</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIMP_OID</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>m. IF Not recommended attribute Enum-Observed-Value-Simple-Bit-Str</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIMP_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>n. IF recommended attribute Enum-Observed-Value-Basic-Bit-Str is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>o. IF Not recommended attribute Enum-Observed-Value-Simple-Str is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_STR</li> <li><input type="checkbox"/> attribute-type = EnumPrintableString</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> <p>p. IF Not recommended attribute Enum-Observed-Value is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_VAL_ENUM_OBS</li> <li><input type="checkbox"/> attribute-type = EnumObsValue</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> <p>q. Optional attribute Enum-Observed-Value-Partition</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                          |                                                                                                                                                                 |                        |                  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-012                                                                                                                                      |                        |                  |
+| <b>TP label</b>          | Context Meal Enumeration Object - Standard Configuration 1702                                                                                                   |                        |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                     | [ISO/IEEE 11073-10417] |                  |
+|                          | <b>Testable items</b>                                                                                                                                           | ContextMeal 5; M       | ContextMeal 6; M |
+|                          |                                                                                                                                                                 | ContextMeal 10; M      | EnumObj 4; M     |
+| <b>Test purpose</b>      | Check that:<br>The Context Meal Enumeration Object contains the attributes specified for Standard Configuration 0x06A6.                                         |                        |                  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND C_AG_GL_025 AND (NOT C_AG_OXP_181)                                                                                            |                        |                  |
+| <b>Other PICSSs</b>      |                                                                                                                                                                 |                        |                  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                         |                        |                  |
+| <b>Test procedure</b>    | 1. The simulated PHG receives an association request from the PHD under test.<br>2. The simulated PHG responds with a result = accepted-unknown-config. The PHD |                        |                  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>responds with a "Remote Operation Invoke   Confirmed Event Report" message with an MDC_NOTI_CONFIG event to send its configuration to the PHG.</p> <ol style="list-style-type: none"> <li>3. Check that the field Dev-Config-Id is set 0x06A6 (1702); if it is not, the PHG responds with an "unsupported-config" and waits for a new configuration.</li> <li>4. Once the PHD under test sends a standard configuration, check that Context Meal Object attributes are: <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_HANDLE</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x03</li> </ul> </li> <li>b. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80), MDC_CTXT_GLU_MEAL (0x72 0x48).</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 0 (mss-avail-intermittent(0)), must be set</li> <li>• Bit 1 (mss-avail-stored-data(1)), must be set</li> <li>• Bit 2 (mss-upd-aperiodic(2)), must be set</li> <li>• Bit 3 (mss-msmt-aperiodic(3)), must be set</li> <li>• Bit 9 (mss-acc-agent-initiated(9)), must be set</li> <li>• Bit 12 may be set (mss-cat-manual(12)) if the reading is entered manually</li> <li>• The other bits have to be 0.</li> </ul> </li> </ul> </li> <li>d. IF Recommended attribute Base-Offset-Time is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value-length = 2 bytes</li> </ul> </li> <li>e. Mandatory attribute Enum-Observed-Value-Simple-OID <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ENUM_OBS_VAL_SIMP_OID</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value-length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = One of the following nomenclature values will be used: <ul style="list-style-type: none"> <li>• MDC_CTXT_GLU_MEAL_PREPRANDIAL (0x72 0x4C)</li> <li>• MDC_CTXT_GLU_MEAL_POSTPRANDIAL (0x72 0x50)</li> <li>• MDC_CTXT_GLU_MEAL_FASTING (0x72 0x54)</li> <li>• MDC_CTXT_GLU_MEAL_BEDTIME (0x72 0x74)</li> <li>• MDC_CTXT_GLU_MEAL_CASUAL (0x72 0x58)</li> </ul> </li> </ul> </li> <li>f. No other attribute shall be present at configuration.</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-012_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                  |
+| <b>TP label</b>          | Context Meal Enumeration Object - Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-10417] |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | EnumObj 3; R           | EnumObj 4; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | EnumObj 6; R           | EnumObj 7; R     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | EnumObj 9; R           | EnumObj 2; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | EnumObj 16; O          | EnumObj 17; O    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | EnumObj 21; O          | EnumObj 22; O    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | EnumObj 24; O          | ContextMeal 1; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | ContextMeal 3; M       | ContextMeal 8; R |
+| <b>Test purpose</b>      | Check that:<br>Context Meal Enumeration Object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND C_AG_OXP_181 AND C_AG_GL_008                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                  |
+| <b>Other PICs</b>        | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is in the extended range, if it is not, the simulated PHG must respond with an "unsupported-config" and wait for a new configuration.</li> <li>5. Once the PHD under test sends an extended configuration, check that all Context Meal Enumeration Objects have: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80), MDC_CTXT_GLU_MEAL (0X72 0X48)</li> </ol> </li> <li>b. IF Not recommended attribute Supplemental-Types is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes))</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                        |                  |
+
+- 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))
+- Bit 12 may be set (mss-cat-manual(12))
+
+d. IF Not recommended attribute Metric-Structure-Small is present
+
+- attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+- attribute-type = MetricStructureSmall
+- attribute-value.length = <variable>(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8))))
+
+e. IF Not recommended attribute Measurement-Status is present
+
+- attribute-id = MDC\_ATTR\_MSMT\_STAT
+- attribute-type = MeasurementStatus (BITS-16)
+- attribute-value.length = 2 bytes
+
+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 = Only one attribute of Metric-Id and Metric-Id-List shall be present.
+
+g. IF Not recommended attribute Metric-Id is present-List is present
+
+- attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIS
+- attribute-type = MetricIdList
+- attribute-value.length= <variable>(SEQUENCE OF OID-Type (INT-U16))
+
+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
+
+i. 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
+
+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
+
+k. Conditional attribute Absolute-Time-Stamp
+
+- attribute-id = MDC\_ATTR\_TIME\_STAMP\_ABS
+- attribute-type = AbsoluteTime
+- attribute-value.length = 8 bytes
+
+l. IF Recommended attribute Base-Offset-Time is present
+
+- attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+- attribute-type = BaseOffsetTime
+- attribute-value.length = 8 bytes
+
+m. IF Optional attribute Relative-Time-Stamp is present
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_REL</li> <li><input type="checkbox"/> attribute-type = RelativeTime (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>n. IF Optional attribute HiRes-Time-Stamp is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_REL_HI_RES</li> <li><input type="checkbox"/> attribute-type = HighResRelativeTime</li> <li><input type="checkbox"/> attribute-value.length = OCTET STRING (SIZE(8))</li> </ul> <p>o. IF the PHD supports fixed or variable format MDS event report and it does not support PM-Store then mandatory attribute Enum-Observed-Value-Simple-OID</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIMP_OID</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute.value= One of the following nomenclature value will be used: <ul style="list-style-type: none"> <li>• MDC_CTXT_GLU_MEAL_PREPRANDIAL (0x72 0x4C)</li> <li>• MDC_CTXT_GLU_MEAL_POSTPRANDIAL (0x72 0x50)</li> <li>• MDC_CTXT_GLU_MEAL_FASTING (0x72 0x54)</li> <li>• MDC_CTXT_GLU_MEAL_BEDTIME (0x72 0x74)</li> <li>• MDC_CTXT_GLU_MEAL_CASUAL (0x72 0x58)</li> </ul> </li> </ul> <p>p. IF Optional attribute Enum-Observed-Value-Simple-Bit-Str is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>q. IF Optional attribute Enum-Observed-Value-Basic-Bit-Str is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>r. IF Optional attribute Enum-Observed-Value-Simple-Str is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_STR</li> <li><input type="checkbox"/> attribute-type = EnumPrintableString</li> <li><input type="checkbox"/> attribute-value.length= &lt;variable&gt;</li> </ul> <p>s. IF Optional attribute Enum-Observed-Value is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_VAL_ENUM_OBS</li> <li><input type="checkbox"/> attribute-type = EnumObsValue</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> <p>t. IF Optional attribute Enum-Observed-Value-Partition is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_VAL_ENUM_OBS_VAL_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                   |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-013                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                   |
+| <b>TP label</b>          | Context Sample Location Enumeration Object - Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                   |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-10417] |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | EnumObj 3; R           | EnumObj 4; M      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | EnumObj 6; R           | EnumObj 7; R      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | EnumObj 9; R           | EnumObj 2; M      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | EnumObj 16; O          | EnumObj 17; O     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | EnumObj 21; O          | EnumObj 22; O     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | EnumObj 24; O          | ContxtSamLoc 1; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | ContxtSamLoc 3; M      | ContxtSamLoc 4; R |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Context Sample Location Enumeration Object contains the attributes specified for Extended Configuration.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                   |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND C_AG_OXP_181 AND C_AG_GL_009                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                   |
+| <b>Other PICSs</b>       | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                   |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                   |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is in the extended range, if it is not, the simulated PHG must respond with an "unsupported-config" and wait for a new configuration.</li> <li>5. Once the PHD under test sends an extended configuration, check that all Context Meal Enumeration Objects have: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80),<br/>MDC_CTXT_GLU_SAMPLELOCATION (0x72 0x34)</li> </ul> </li> <li>b. IF Not recommended attribute Supplemental-Types is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes))</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                        |                   |
+
+- 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))
+- Bit 12 may be set (mss-cat-manual(12))
+
+- d. IF Not recommended attribute Metric-Structure-Small is present
+  - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+  - attribute-type = MetricStructureSmall
+  - attribute-value.length = <variable>(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8))))
+- e. IF Not recommended attribute Measurement-Status is present
+  - attribute-id = MDC\_ATTR\_MSMT\_STAT
+  - attribute-type = MeasurementStatus (BITS-16)
+  - attribute-value.length = 2 bytes
+- 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 = Only one attribute of Metric-Id and Metric-Id-List shall be present.
+- g. IF Not recommended attribute Metric-Id-List is present
+  - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIS
+  - attribute-type = MetricIdList
+  - attribute-value.length= <variable>(SEQUENCE OF OID-Type (INT-U16))
+- 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
+- i. 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
+- 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
+- k. IF Recommended attribute Base-Offset-Time is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+  - attribute-type = BaseOffsetTime
+  - attribute-value.length = 8 bytes
+- l. IF Optional attribute Relative-Time-Stamp is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_REL
+  - attribute-type = RelativeTime (INT-U32)
+  - attribute-value.length = 4 bytes
+- m. IF Optional attribute HiRes-Time-Stamp is present
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_REL_HI_RES</li> <li><input type="checkbox"/> attribute-type = HighResRelativeTime</li> <li><input type="checkbox"/> attribute-value.length = OCTET STRING (SIZE(8))</li> </ul> <p>n. IF the PHD supports fixed or variable format MDS event report and it does not support PM-Store then mandatory attribute Enum-Observed-Value-Simple-OID</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_OID</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute.value= One of the following nomenclature value will be used: <ul style="list-style-type: none"> <li>•MDC_CTXT_GLU_SAMPLE_LOCATION_FINGER (0x72 0x38)</li> <li>•MDC_CTXT_GLU_SAMPLE_LOCATION_AST (0x72 0x3C)</li> <li>•MDC_CTXT_GLU_SAMPLE_LOCATION_EARLOBE (0x72 0x40)</li> <li>•MDC_CTXT_GLU_SAMPLE_LOCATION_CTRLSOLUTION (0x72 0x44)</li> <li>•MDC_CTXT_GLU_SAMPLE_LOCATION_OTHER (0x72 0x36)</li> <li>•MDC_CTXT_GLU_SAMPLE_LOCATION_UNDETERMINED (0x72 0x35)</li> </ul> </li> </ul> <p>o. IF Optional attribute Enum-Observed-Value-Simple-Bit-Str is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>p. IF Optional attribute Enum-Observed-Value-Basic-Bit-Str is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>q. IF Optional attribute Enum-Observed-Value-Simple-Str is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_STR</li> <li><input type="checkbox"/> attribute-type = EnumPrintableString</li> <li><input type="checkbox"/> attribute-value.length= &lt;variable&gt;</li> </ul> <p>r. IF Optional attribute Enum-Observed-Value is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_VAL_ENUM_OBS</li> <li><input type="checkbox"/> attribute-type = EnumObsValue</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> <p>s. IF Optional attribute Enum-Observed-Value-Partition is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_VAL_ENUM_OBS_VAL_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|                 |                                                            |                        |
+|-----------------|------------------------------------------------------------|------------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/GL/BV-014                                 |                        |
+| <b>TP label</b> | Context Tester Enumeration Object - Extended Configuration |                        |
+| <b>Coverage</b> | <b>Spec</b>                                                | [ISO/IEEE 11073-10417] |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                    |                    |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|--------------------|
+| <b>Testable items</b>    | EnumObj 3; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | EnumObj 4; M       | EnumObj 5 R        |
+|                          | EnumObj 6; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | EnumObj 7; R       | EnumObj 8; R       |
+|                          | EnumObj 9; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | EnumObj 2; M       | EnumObj 12; R      |
+|                          | EnumObj 16; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | EnumObj 17; O      | EnumObj 20; O      |
+|                          | EnumObj 21; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | EnumObj 22; O      | EnumObj 23; O      |
+|                          | EnumObj 24; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | ContextTester 1; M | ContextTester 2; C |
+|                          | ContextTester 3; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ContextTester 4; R |                    |
+| <b>Test purpose</b>      | Check that:<br>Context Tester Enumeration Object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                    |                    |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND C_AG_OXP_181 AND C_AG_GL_010                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                    |                    |
+| <b>Other PICSSs</b>      | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                    |                    |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                    |                    |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is in the extended range, if it is not, the simulated PHG must respond with an "unsupported-config" and wait for a new configuration.</li> <li>5. Once the PHD under test sends an extended configuration, check that all Context Meal Enumeration Objects have: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80),<br/>MDC_CTXT_GLU_TESTER (0x72 0x5C)</li> </ol> </li> <li>b. IF Not recommended attribute Supplemental-Types is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes))</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length =2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 <ol style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 3 must be set (mss-msmt-aperiodic(3))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> <li>• Bit 12 may be set (mss-cat-manual(12))</li> </ol> </li> </ol> </li> </ol> </li> </ol> |                    |                    |
+
+- d. IF Not recommended attribute Metric-Structure-Small is present
+  - attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+  - attribute-type = MetricStructureSmall
+  - attribute-value.length = <variable>(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8))))
+- e. IF Not recommended attribute Measurement-Status is present
+  - attribute-id = MDC\_ATTR\_MSMT\_STAT
+  - attribute-type = MeasurementStatus (BITS-16)
+  - attribute-value.length = 2 bytes
+- 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 = Only one attribute of Metric-Id and Metric-Id-List shall be present.
+- g. IF Not recommended attribute Metric-Id-List is present
+  - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIS
+  - attribute-type = MetricIdList
+  - attribute-value.length= <variable>(SEQUENCE OF OID-Type (INT-U16))
+- 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
+- i. 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
+- 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
+- k. IF Recommended attribute Base-Offset-Time is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+  - attribute-type = BaseOffsetTime
+  - attribute-value.length = 8 bytes
+- l. IF Optional attribute Relative-Time-Stamp is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_REL
+  - attribute-type = RelativeTime (INT-U32)
+  - attribute-value.length = 4 bytes
+- m. IF Optional attribute HiRes-Time-Stamp is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_REL\_HI\_RES
+  - attribute-type = HighResRelativeTime
+  - attribute-value.length = OCTET STRING (SIZE(8))
+- n. IF the PHD supports fixed or variable format MDS event report and it does not support PM-Store then mandatory attribute Enum-Observed-Value-Simple-OID
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_OID</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute.value= One of the following nomenclature value will be used: <ul style="list-style-type: none"> <li>• MDC_CTXT_GLU_TESTER_SELF (0x72 0x60) OR</li> <li>• MDC_CTXT_GLU_TESTER_HCP (0x72 0x64) OR</li> <li>• MDC_CTXT_GLU_TESTER_LAB (0x72 0x68)</li> </ul> </li> <li>o. IF Optional attribute Enum-Observed-Value-Simple-Bit-Str is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> <li>p. IF Optional attribute Enum-Observed-Value-Basic-Bit-Str is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>q. IF Optional attribute Enum-Observed-Value-Simple-Str is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_STR</li> <li><input type="checkbox"/> attribute-type = EnumPrintableString</li> <li><input type="checkbox"/> attribute-value.length= &lt;variable&gt;</li> </ul> </li> <li>r. IF Optional attribute Enum-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_VAL_ENUM_OBS</li> <li><input type="checkbox"/> attribute-type = EnumObsValue</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> </li> <li>s. IF Optional attribute Enum-Observed-Value-Partition is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_VAL_ENUM_OBS_VAL_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                 |                       |                                                            |               |               |
+|-----------------|-----------------------|------------------------------------------------------------|---------------|---------------|
+| <b>TP Id</b>    |                       | TP/PLT/PHD/CLASS/GL/BV-015                                 |               |               |
+| <b>TP label</b> |                       | Context Health Enumeration Object - Extended Configuration |               |               |
+| <b>Coverage</b> | <b>Spec</b>           | [ISO/IEEE 11073-10417]                                     |               |               |
+|                 | <b>Testable items</b> | EnumObj 3; R                                               | EnumObj 4; M  | EnumObj 5 R   |
+|                 |                       | EnumObj 6; R                                               | EnumObj 7; R  | EnumObj 8; R  |
+|                 |                       | EnumObj 9; R                                               | EnumObj 2; M  | EnumObj 12; R |
+|                 |                       | EnumObj 16; O                                              | EnumObj 17; O | EnumObj 20; O |
+|                 |                       | EnumObj 21; O                                              | EnumObj 22; O | EnumObj 23; O |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                    |                    |                    |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|--------------------|--------------------|
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EnumObj 24; O      | ContextHealth 1; M | ContextHealth 2; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | ContextHealth 3; M | ContextHealth 4; R |                    |
+| <b>Test purpose</b>      | Check that:<br>Context Health Enumeration Object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                    |                    |                    |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND C_AG_OXP_181 AND C_AG_GL_011                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                    |                    |                    |
+| <b>Other PICSs</b>       | C_AG_OXP_041, C_AG_OXP_183, C_AG_OXP_189                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                    |                    |                    |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                    |                    |                    |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is in the extended range, if it is not, the simulated PHG must respond with an "unsupported-config" and wait for a new configuration.</li> <li>5. Once the PHD under test sends an extended configuration, check that all Context Meal Enumeration Objects have: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_DM (0x00 0x80), MDC_CTXT_GLU_HEALTH (0x72 0x5C)</li> </ul> </li> <li>b. IF Not recommended attribute Supplemental-Types is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes))</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ul style="list-style-type: none"> <li>• Bit 0 must be set (mss-avail-intermittent(0))</li> <li>• Bit 1 must be set (mss-avail-stored-data(1))</li> <li>• Bit 2 must be set (mss-upd-aperiodic(2))</li> <li>• Bit 3 must be set (mss-msmt-aperiodic(3))</li> <li>• Bit 9 must be set (mss-acc-agent-initiated(9))</li> <li>• Bit 12 may be set (mss-cat-manual(12))</li> </ul> </li> </ul> </li> <li>d. IF Not recommended attribute Metric-Structure-Small is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (Sequence of (ms-struct.length = 1byte(INT-U8) + ms-comp-no = 1byte(INT-U8)))</li> </ul> </li> <li>e. IF Not recommended attribute Measurement-Status is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus (BITS-16)</li> </ul> </li> </ol> </li> </ol> |                    |                    |                    |
+
+- attribute-value.length = 2 bytes
+- 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 = Only one attribute of Metric-Id and Metric-Id-List shall be present.
+- g. IF Not recommended attribute Metric-Id-List is present
+  - attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIS
+  - attribute-type = MetricIdList
+  - attribute-value.length= <variable>(SEQUENCE OF OID-Type (INT-U16))
+- 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
+- i. 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
+- 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
+- k. IF Recommended attribute Base-Offset-Time is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_BO
+  - attribute-type = BaseOffsetTime
+  - attribute-type.length = 8 bytes
+- l. IF Optional attribute Relative-Time-Stamp is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_REL
+  - attribute-type = RelativeTime (INT-U32)
+  - attribute-value.length = 4 bytes
+- m. IF Optional attribute HiRes-Time-Stamp is present
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_REL\_HI\_RES
+  - attribute-type = HighResRelativeTime
+  - attribute-value.length = OCTET STRING (SIZE(8))
+- n. IF the PHD supports fixed or variable format MDS event report and it does not support PM-Store then 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= One of the following nomenclature value will be used:
+    - MDC\_CTXT\_GLU\_HEALTH\_MINOR (0x72 0x20) OR
+    - MDC\_CTXT\_GLU\_HEALTH\_MAJOR (0x72 0x24) OR
+    - MDC\_CTXT\_GLU\_HEALTH\_MENSES (0x72 0x28) OR
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• MDC_CTXT_GLU_HEALTH_STRESS (0x72 0x2C) OR</li> <li>• MDC_CTXT_GLU_HEALTH_NONE (0x72 0x30)</li> </ul> <ul style="list-style-type: none"> <li>o. IF Optional attribute Enum-Observed-Value-Simple-Bit-Str is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> </li> <li>p. IF Optional attribute Enum-Observed-Value-Basic-Bit-Str is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> <li>q. IF Optional attribute Enum-Observed-Value-Simple-Str is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_STR</li> <li><input type="checkbox"/> attribute-type = EnumPrintableString</li> <li><input type="checkbox"/> attribute-value.length= &lt;variable&gt;</li> </ul> </li> <li>r. IF Optional attribute Enum-Observed-Value is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_VAL_ENUM_OBS</li> <li><input type="checkbox"/> attribute-type = EnumObsValue</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> </li> <li>s. IF Optional attribute Enum-Observed-Value-Partition is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_VAL_ENUM_OBS_VAL_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                          |                                                                                                                                                                                                                                                  |                        |                   |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-016                                                                                                                                                                                                                       |                        |                   |
+| <b>TP label</b>          | PM-Store Attributes for Extended Configuration                                                                                                                                                                                                   |                        |                   |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                      | [ISO/IEEE 11073-10417] |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                            | PMStrObjAtt 1; M       | PMStrObjAtt 5; M  |
+|                          |                                                                                                                                                                                                                                                  | PMStrObjAtt 8; M       | PMStrObjAtt 9; R  |
+|                          |                                                                                                                                                                                                                                                  |                        | PMStrObjAtt 6; M  |
+|                          |                                                                                                                                                                                                                                                  |                        | PMStrObjAtt 12; M |
+| <b>Test purpose</b>      | Check that:<br>PM-Store Object contains the attributes specified for Extended Configuration.                                                                                                                                                     |                        |                   |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND C_AG_OXP_041 AND C_AG_OXP_181                                                                                                                                                                                  |                        |                   |
+| <b>Other PICSs</b>       |                                                                                                                                                                                                                                                  |                        |                   |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                          |                        |                   |
+| <b>Test procedure</b>    | 1. The simulated PHG receives an association request from the PHD under test.<br>2. The simulated PHG responds with a result = accepted-unknown-config.<br>3. The PHD responds with a "Remote Operation Invoke   Confirmed Event Report" message |                        |                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>with an MDC_NOTI_CONFIG event to send its configuration to the PHG.</p> <p>4. The handle for the PM-Store attribute must be:</p> <ol style="list-style-type: none"> <li>Mandatory attribute Handle           <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = must be unique and non-zero. Actual value may be specified by the device specialization.</li> </ul> </li> </ol> <p>5. 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.</p> <p>6. The PHD issues a GET response with the PM-Store attributes it supports:</p> <ol style="list-style-type: none"> <li>Mandatory Store-Capacity-Count           <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STORE_CAPAC_CNT</li> <li><input type="checkbox"/> attribute-type = INT-U32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = See relation with next attribute</li> </ul> </li> <li>Mandatory attribute Store-Usage-Count           <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STORE_USAGE_CNT</li> <li><input type="checkbox"/> attribute-type = INT-U32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = consistent with actual number of segments present and always <math>\leq</math> than Storage-Capacity-Count</li> </ul> </li> <li>Mandatory attribute PM-Store-Label           <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_LABEL_STRING</li> <li><input type="checkbox"/> attribute-type = OCTET STRING</li> <li><input type="checkbox"/> attribute-value.length = &lt;Variable&gt;</li> <li><input type="checkbox"/> attribute-value = Printable ASCII</li> </ul> </li> <li>IF Not Recommended attribute Sample-Period is present           <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_SAMP</li> <li><input type="checkbox"/> attribute-type = RelativeTime</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> </li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                     |                                              |                                                                                         |                 |
+|---------------------|----------------------------------------------|-----------------------------------------------------------------------------------------|-----------------|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/GL/BV-017                   |                                                                                         |                 |
+| <b>TP label</b>     | PM Segment Object for Extended Configuration |                                                                                         |                 |
+| <b>Coverage</b>     | <b>Spec</b>                                  | [ISO/IEEE 11073-10417]                                                                  |                 |
+|                     | <b>Testable items</b>                        | PMStoreObj 8; M                                                                         | PMStoreObj 9; O |
+|                     |                                              | PMStoreObj 11; O                                                                        | PMSegObj 6; M   |
+|                     |                                              | PMSegObj 14; R                                                                          | PMSegObj 15; R  |
+| <b>Test purpose</b> |                                              | Check that:<br>PM-Segment contains the attributes specified for Extended Configuration. |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_178 AND C_AG_OXP_041 AND C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Other PICSs</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>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.</li> <li>2. 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.</li> <li>3. The PHD issues a response with the PM-Segment attributes it supports: <ol style="list-style-type: none"> <li>a. Mandatory attribute Segment-Label <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_SEG_LABEL_STRING</li> <li><input type="checkbox"/> attribute-type = OCTET STRING</li> <li><input type="checkbox"/> attribute-value.length = consistent with value</li> <li><input type="checkbox"/> attribute-value = &lt;printable ASCII&gt;</li> </ol> </li> <li>b. Recommended attribute Segment-Start-BO-Time <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_START_SEG_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ol> </li> <li>c. Recommended attribute Segment-End-BO-Time <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_END_SEG_BO</li> <li><input type="checkbox"/> attribute-type = BaseOffsetTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ol> </li> <li>d. Mandatory attribute Segment-Usage-Count <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SEG_USAGE_CNT</li> <li><input type="checkbox"/> attribute-type = INT-U32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;not relevant in this test&gt;</li> </ol> </li> <li>e. Mandatory attribute PM-Segment-Entry-Map <ol style="list-style-type: none"> <li><input type="checkbox"/> SegmentEntryHeader.value = One of the next must be set: <ul style="list-style-type: none"> <li>• seg-elem-hdr-absolute-time(0)</li> <li>• seg-elem-hdr-relative-time(1)</li> <li>• seg-elem-hdr-hires-relative-time(2)</li> <li>• seg-elem-hdr-bo-time (3)</li> </ul> </li> <li><input type="checkbox"/> SegmEntryElem: &lt; Record the fields for later comparison&gt;</li> </ol> </li> </ol> </li> <li>4. Repeat step 3 and 4 for every Segment.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• All checked values are as specified in the test procedure</li> <li>• Every segm-entry-header must contain one of the time formats</li> <li>• At least one PM-Segment must reference the Common Glucose in its PM-Segm-Entry-Map</li> <li>• If there are more than one PM-Segment, the rest of them must reference one of the objects defined in the spec in its PM-Segm-Entry-Map</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                 |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/GL/BV-017_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                 |
+| <b>TP label</b>           | PM-Segment Object for Extended Configuration.MDS Event Reports                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                 |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-10417] |                 |
+|                           | <b>Testable Items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | PMStoreObj 5; M        | PMStoreObj 6; M |
+| <b>Test purpose</b>       | Check that:<br>Any configuration with a PM Store for persistent storage shall disable PHD-initiated transmission and enable access to PM-Store transmissions                                                                                                                                                                                                                                                                                                                                                   |                        |                 |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_178 AND C_AG_OXP_041 AND C_AG_OXP_181                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                 |
+| <b>Other PICSSs</b>       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                 |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                 |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>The simulated PHG asks for a measurement.</li> <li>Check event reports that are sent by the PHD.</li> </ol> |                        |                 |
+| <b>Pass/Fail criteria</b> | In step 4, the PHD shall not send the data with MDS event reports.                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                 |
+
+|                          |                                                                                                                                                                                                                                                                                                                       |                        |                |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-018                                                                                                                                                                                                                                                                                            |                        |                |
+| <b>TP label</b>          | Communication Model: Association Procedure                                                                                                                                                                                                                                                                            |                        |                |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-10417] |                |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                 | AgProcAs 1; M          | AgProcAs 2; M  |
+|                          |                                                                                                                                                                                                                                                                                                                       | AgProcAs 5; M          | AgProcAs 6; M  |
+|                          |                                                                                                                                                                                                                                                                                                                       | AgProcAs 8; M          | AgProcAs 9; M  |
+|                          |                                                                                                                                                                                                                                                                                                                       | AgProcAs 11; M         | AgProcAs 12; M |
+|                          |                                                                                                                                                                                                                                                                                                                       | AgProcAs 13; M         |                |
+| <b>Test purpose</b>      | Check that:<br>The association procedure data exchange is correct                                                                                                                                                                                                                                                     |                        |                |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178                                                                                                                                                                                                                                                                                         |                        |                |
+| <b>Other PICSSs</b>      | C_AG_OXP_002, C_AG_OXP_017                                                                                                                                                                                                                                                                                            |                        |                |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                               |                        |                |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The PHD sends a message to associate to the simulated PHG, the expected fields sent by the PHD are: <ol style="list-style-type: none"> <li>APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = AarqApdu</li> </ul> </li> </ol> </li> </ol> |                        |                |
+
+- 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=0x40 0x00 0x00 0x00 or 0x20 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)
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field- value = <ul style="list-style-type: none"> <li>• 0x06 0xA5 OR 0x06 0xA6 for Standard Configuration.</li> <li>• &lt;between 0x40 0x00 and 0x7F 0xFF &gt; for Extended Configuration.</li> </ul> </li> </ul> <p>k. data-req-mode-flags (DataReqModeCapab)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = DataReqModeFlags</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li>• If the PHD supports agent-initiated measurement transfer → Bit 15 is set (data-req-supp-init-agent(15))</li> <li>• If the PHD supports requesting objects based on the object handle → Bit 6 will be set (data-req-supp-scope-handle(6)).</li> <li>• If the PHD supports single response → Bit 8 will be set (data-req-supp-mode-single-rsp(8)).</li> <li>• If the PHD supports time unlimited data request → Bit 10 will be set (data-req-supp-mode-time-no-limit(10)).</li> </ul> <p>l. data-req-init-agent-count (DataReqModeCapab)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = INT-U8</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field.value = 0x01</li> </ul> <p>m. data-req-init-manager-count (DataReqModeCapab)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = INT-U8</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field.value = 0x00</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                |                        |  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-019                                                                                                                                                                                                                                                                                                                                                                                     |                        |  |
+| <b>TP label</b>          | PM Segment Object for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                   |                        |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-10417] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                          | PMStrObjMeth 1; M      |  |
+| <b>Test purpose</b>      | Check that:<br>Glucose Meter supports the Clear-Segments method with Confirmed mode                                                                                                                                                                                                                                                                                                                            |                        |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND C_AG_OXP_041 AND C_AG_OXP_071                                                                                                                                                                                                                                                                                                                                                |                        |  |
+| <b>Other PICSSs</b>      |                                                                                                                                                                                                                                                                                                                                                                                                                |                        |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state and the PHD has at least one PM-Segment with data stored.                                                                                                                                                                                                                                                                                  |                        |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Take measurements with the PHD of a value that is stored on a PM-Segment.</li> <li>2. 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.</li> <li>3. The PHD issues a GET response with the PM-Store attributes, record the values of the PMStoreCapab attribute.</li> </ol> |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>4. The simulated PHG shall send a Get-Segment-Info object action with segmSelection set to all-segments to check that there are no Segments in use.</p> <p>5. The simulated PHG sends a Clear-Segment to all segments:</p> <p>a. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> <li><input type="checkbox"/> SegmSelection = all-segments</li> </ul> <p>6. The PHD under test operation response:</p> <p>a. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Response   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_CLEAR</li> </ul> <p>7. Delay</p> <p>8. The simulated PHG sends a request for the PM-Segment Data with SegmSelection = all-segments to obtain all the segments:</p> <p>a. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> SegmSelection = &lt;Instance number of the selected PM-Segment that contained data before the clear-segment action&gt;</li> </ul> <p>9. The PHD issues an action response with the Data</p> <p>a. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Response   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> TrigSegmXferRsp = <ul style="list-style-type: none"> <li>• IF pmsc-clear-segm-remove is NOT set THEN TrigSegmXferRsp = tsxr-fail-segm-empty</li> <li>• ELSE TrigSegmXferRsp = tsxr-fail-no-such-segment</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                      |                                                                                            |                        |  |
+|----------------------|--------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>         | TP/PLT/PHD/CLASS/GL/BV-020                                                                 |                        |  |
+| <b>TP label</b>      | Config Changes Service. Contextual Attribute.                                              |                        |  |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                | [b-ITU-T H.810 (2015)] |  |
+|                      | <b>Testable items</b>                                                                      | Communication 8; M     |  |
+| <b>Test purpose</b>  | Check that:<br>Service component reports configuration changes to future measurements only |                        |  |
+| <b>Applicability</b> | C_AG_OXP_000 AND C_AG_OXP_178 AND C_AG_GL_022                                              |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICSS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Take some measurements with the PHD under test.</li> <li>2. Make a change to the contextual attribute Unit-Code for blood glucose.</li> <li>3. The PHD shall send an MDS event report indicating the new contextual attribute value.</li> <li>4. Take some more measurements.</li> <li>5. Wait for the PHG to receive new event reports from the PHD, which report the measurements from step 4.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHD sends an MDS event report to inform on the contextual attribute that has been changed.</li> <li>• Data has changed accordingly to the new contextual attribute.</li> </ul>                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                                                               |  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-021                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |  |
+| <b>TP label</b>          | Operating State. PHG to PHD Maximum APDU Size                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | CommonCharac 3; M                                             |  |
+|                          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [ISO/IEEE 11073-10417]                                        |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | ComChar 2; M                                                  |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The total size of the response do not exceed of the maximum APDU size established by the specialization</p> <p>[AND]</p> <p>A glucose 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</p>                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |
+| <b>Other PICSS</b>       | C_AG_OXP_041, C_AG_OXP_100                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG issues a "Remote Operation Invoke   Get" command with: <ol style="list-style-type: none"> <li>a. Obj-handle set to 0 (to request for MDS object)</li> <li>b. attribute-id-list.count = 103</li> <li>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</li> </ol> </li> <li>2. Check the response of the PHD.</li> <li>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.</li> <li>4. Check the response of the PHD.</li> </ol> |                                                               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• 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. <ul style="list-style-type: none"> <li>○ 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): <ul style="list-style-type: none"> <li>▪ Pulse oximeter -&gt; 9216 octets</li> <li>▪ Weighing scales -&gt; 896 octets</li> <li>▪ Glucose meter -&gt; 5120 octets or 64512 octets if the PHD supports PM-Store</li> <li>▪ Blood pressure -&gt; 896 octets</li> <li>▪ Thermometer -&gt; 896 octets</li> <li>▪ Independent activity hub -&gt; 5120 octets</li> <li>▪ Cardiovascular -&gt; 64512 octets or 6624 octets if the PHD under test only supports a Step Counter Profile</li> <li>▪ Strength -&gt; 64512 octets:</li> <li>▪ Adherence monitor -&gt; 1024 octets</li> <li>▪ Peak flow -&gt; 2030 octets</li> <li>▪ Body composition analyser -&gt; 7730 octets</li> <li>▪ Basic ECG/Simple ECG -&gt; 7168 octets or 64512 octets if the PHD supports a PM-Store</li> <li>▪ Basic ECG/Heart rate -&gt; 1280 octets or 64512 octets if the PHD supports a PM-Store</li> <li>▪ International normalized ratio -&gt; 896 octets or 64512 if the PHD supports a PM-Store</li> </ul> </li> <li>○ If it responds with a roer, the reason must not be a protocol-violation (23)</li> </ul> </li> <li>• In step 4, the PHD must respond with a rors-cmip-get message.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                          |                                                                                                                                                                                                                                                                                                                              |                        |  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-022                                                                                                                                                                                                                                                                                                   |                        |  |
+| <b>TP label</b>          | Blood Glucose measurement above the capabilities of the device sensor without Device and Sensor Status Annunciation object                                                                                                                                                                                                   |                        |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                  | [ISO/IEEE 11073-10417] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                        | BloodGL 29; M          |  |
+| <b>Test purpose</b>      | Check that:<br><br>In Standard Configurations 1701 (0x06A5) or 1702 (0x06A6), or in an extended configuration that does not include the Device and Sensor Status Annunciation object, a Blood Glucose measurement that is above the capabilities of the device sensor shall be indicated with an observed value of +INFINITY |                        |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND ((NOT C_AG_OXP_181) OR ((C_AG_OXP_181) AND ((NOT(C_AG_GL_007))))))                                                                                                                                                                                                                         |                        |  |
+| <b>Other PICSs</b>       |                                                                                                                                                                                                                                                                                                                              |                        |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                         |                        |  |
+| <b>Test procedure</b>    | 1. Place a blood sample in the device sensor with a blood glucose level above the capabilities of the device sensor and acquire a measurement with the PHD under test.                                                                                                                                                       |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>IF C_AG_OXP_041 = FALSE</p> <p>2. The test tool simulated PHG waits to receive an event report from the PHD under test. The event report shall contain the following value:</p> <p>a. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> event-type = MDC_NOTI_SCAN_REPORT_FIXED (0x0D 0x1D)</li> <li><input type="checkbox"/> obj-handle = 1 (Blood glucose)</li> <li><input type="checkbox"/> obs-val-data = <ul style="list-style-type: none"> <li>• Basic-Nu-Observed-Value = 0x07FE</li> </ul> </li> </ul> <p>IF C_AG_OXP_041 = TRUE</p> <p>3. The test tool simulated PHG issues a GET for the PM-Store object (or objects) and a Get-Segment-Info with SegmSelection set to all-segments. Then, the PHG sends a request to the PM-Segments that contains data. The PHD issues an action response and starts data transfer. An event report with the following values shall be present:</p> <p>a. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> event-type = MDC_NOTI_SEGMENT_DATA (0x0D 0x21)</li> <li><input type="checkbox"/> obj-handle = 1 (Blood glucose)</li> <li><input type="checkbox"/> obs-val-data = <ul style="list-style-type: none"> <li>▪ Basic-Nu-Observed-Value = 0x07FE</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              | The vendor must provide a blood sample (or a simulated blood solution) with a blood glucose level above the capabilities of device sensor.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-022_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |  |
+| <b>TP label</b>          | Blood Glucose measurement above the capabilities of the device sensor with Device and Sensor Status Annunciation object                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-10417] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | BloodGL 31; M          |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>In extended configuration that includes the Device and Sensor Status Annunciation object, a Blood Glucose measurement that is above the capabilities of the device sensor shall be indicated either with an observed value of +INFINITY or by setting the appropriate flag in GlucoseDevStat</p>                                                                                                                                                                                                                  |                        |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND (C_AG_OXP_181) AND (C_AG_GL_007)                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |  |
+| <b>Other PICSSs</b>      | C_AG_OXP_041                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |  |
+| <b>Test procedure</b>    | <p>1. Place a blood sample in the device sensor with a blood glucose level above the capabilities of the device sensor and acquire a measurement with the PHD under test.</p> <p>IF C_AG_OXP_041 = FALSE</p> <p>2. The test tool simulated PHG waits to receive an event report from the PHD under test. The event report shall contain the following values:</p> <p>a. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> event-type = MDC_NOTI_SCAN_REPORT_FIXED (0x0D 0x1D)</li> </ul> <p>with either</p> |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><input type="checkbox"/> obj-handle = 1 (Blood glucose)</p> <p><input type="checkbox"/> obs-val-data =</p> <p>▪ Basic-Nu-Observed-Value = 0x07FE</p> <p>OR</p> <p><input type="checkbox"/> obj-handle = X (Device and Sensor Annunciation)</p> <p><input type="checkbox"/> obs-val-data =</p> <p>▪ Enum-Observed-Value-Basic-Bit-Str = sensor-result-too-high (5)</p> <p>IF C_AG_OXP_041 = TRUE</p> <p>3. The test tool simulated PHG issues a GET for the PM-Store object (or objects) and a Get-Segment-Info with SegmSelection set to all-segments. Then, the PHG sends a request to the PM-Segments that contains data. The PHD issues an action response and starts data transfer. An event report with the following values shall be present:</p> <p>a. Data APDU</p> <p><input type="checkbox"/> event-type = MDC_NOTI_SEGMENT_DATA (0x0C 0x1C)</p> <p>with either</p> <p><input type="checkbox"/> obj-handle = 1 (Blood glucose)</p> <p><input type="checkbox"/> obs-val-data =</p> <p>▪ Basic-Nu-Observed-Value = 0x07FE</p> <p>OR</p> <p><input type="checkbox"/> obj-handle = X (Device and Sensor Annunciation)</p> <p><input type="checkbox"/> obs-val-data =</p> <p>▪ Enum-Observed-Value-Basic-Bit-Str = sensor-result-too-high (5)</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              | The vendor must provide a blood sample (or a simulated blood solution) with a blood glucose level above the capabilities of device sensor.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                          |                                                                                                                                                                                                                                                                                                                                     |                        |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-023                                                                                                                                                                                                                                                                                                          |                        |  |
+| <b>TP label</b>          | Blood Glucose measurement below the capabilities of the device sensor without Device and Sensor Status Annunciation object                                                                                                                                                                                                          |                        |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-10417] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                               | BloodGL 30; M          |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>In Standard Configurations 1701 (0x06A5) or 1702 (0x06A6), or in an extended configuration that does not include the Device and Sensor Status Annunciation object, a Blood Glucose measurement that is below the capabilities of the device sensor shall be indicated with an observed value of -INFINITY</p> |                        |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND ((NOT C_AG_OXP_181) OR ((C_AG_OXP_181) AND ((NOT(C_AG_GL_007))))))                                                                                                                                                                                                                                |                        |  |
+| <b>Other PICSSs</b>      |                                                                                                                                                                                                                                                                                                                                     |                        |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                |                        |  |
+| <b>Test procedure</b>    | <p>1. Place a blood sample in the device sensor with a blood glucose level below the capabilities of the device sensor and acquire a measurement with the PHD under test.</p> <p>IF C_AG_OXP_041 = FALSE</p>                                                                                                                        |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>2. The test tool simulated PHG waits to receive an event report from the PHD under test. The event report shall contain the following value:</p> <p>a. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> event-type = MDC_NOTI_SCAN_REPORT_FIXED (0x0D 0x1D)</li> <li><input type="checkbox"/> obj-handle = 1 (Blood glucose)</li> <li><input type="checkbox"/> obs-val-data = <ul style="list-style-type: none"> <li>▪ Basic-Nu-Observed-Value = 0x0802</li> </ul> </li> </ul> <p>IF C_AG_OXP_041 = TRUE</p> <p>3. The test tool simulated PHG issues a GET for the PM-Store object (or objects) and a Get-Segment-Info with SegmSelection set to all-segments. Then, the PHG sends a request to the PM-Segments that contains data. The PHD issues an action response and starts data transfer. A event report with the following values shall be present:</p> <p>a. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> event-type = MDC_NOTI_SEGMENT_DATA (0x0D 0x21)</li> <li><input type="checkbox"/> obj-handle = 1 (Blood glucose)</li> <li><input type="checkbox"/> obs-val-data = <ul style="list-style-type: none"> <li>▪ Basic-Nu-Observed-Value = 0x0802</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              | The vendor must provide a blood sample (or a simulated blood solution) with a blood glucose level below the capabilities of device sensor.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-023_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |  |
+| <b>TP label</b>          | Blood Glucose measurement below the capabilities of the device sensor with Device and Sensor Status Annunciation object                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [ISO/IEEE 11073-10417] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | BloodGL 32; M          |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>In extended configuration that includes the Device and Sensor Status Annunciation object, a Blood Glucose measurement that is below the capabilities of the device sensor shall be indicated either with an observed value of -INFINITY or by setting the appropriate flag in GlucoseDevStat</p>                                                                                                                                                                                                                                                                                                                           |                        |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND (C_AG_OXP_181) AND (C_AG_GL_007)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |  |
+| <b>Other PICSSs</b>      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |  |
+| <b>Test procedure</b>    | <p>1. Place a blood sample in the device sensor with a blood glucose level below the capabilities of the device sensor and acquire a measurement with the PHD under test.</p> <p>IF C_AG_OXP_041 = FALSE</p> <p>2. The test tool simulated PHG waits to receive an event report from the PHD under test. The event report shall contain the following value:</p> <p>a. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> event-type = MDC_NOTI_SCAN_REPORT_FIXED (0x0D 0x1D)</li> </ul> <p>with either</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> obj-handle = 1 (Blood glucose)</li> </ul> |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><input type="checkbox"/> obs-val-data =</p> <ul style="list-style-type: none"> <li>▪ Basic-Nu-Observed-Value = 0x0802</li> </ul> <p>OR</p> <p><input type="checkbox"/> obj-handle = X (Device and Sensor Annunciation)</p> <p><input type="checkbox"/> obs-val-data =</p> <ul style="list-style-type: none"> <li>▪ Enum- Observed-Value-Basic-Bit-Str = sensor-result-too-low (6)</li> </ul> <p>IF C_AG_OXP_041 = TRUE</p> <p>3. The test tool simulated PHG issues a GET for the PM-Store object (or objects) and a Get-Segment-Info with SegmSelection set to all-segments. Then, the PHG sends a request to the PM-Segments that contains data. The PHD issues an action response and starts data transfer. An event report with the following values shall be present:</p> <p>a. Data APDU</p> <p><input type="checkbox"/> event-type = MDC_ACT_SEG_TRIG_XFER (0x0C 0x1C)</p> <p>with either</p> <p><input type="checkbox"/> obj-handle = 1 (Blood glucose)</p> <p><input type="checkbox"/> obs-val-data =</p> <ul style="list-style-type: none"> <li>▪ Basic-Nu-Observed-Value = 0x0802</li> </ul> <p>OR</p> <p><input type="checkbox"/> obj-handle = X (Device and Sensor Annunciation)</p> <p><input type="checkbox"/> obs-val-data =</p> <ul style="list-style-type: none"> <li>▪ Enum-Observed-Value-Basic-Bit-Str = sensor-result-too-low (6)</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              | The vendor must provide a blood sample (or a simulated blood solution) with a blood glucose level below the capabilities of device sensor.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                                                       |                        |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-024                                                                                                                                                                                                                                                                                                            |                        |
+| <b>TP label</b>          | Control Solution measurement above the capabilities of the device sensor without Device and Sensor Status Annunciation object                                                                                                                                                                                                         |                        |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-10417] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                 | CtrlSol 15; M          |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>In Standard Configuration 1701 (0x06A5) or 1702 (0x06A6), or in an extended configuration that does not include the Device and Sensor Status Annunciation object, a Control Solution measurement that is above the capabilities of the device sensor shall be indicated with an observed value of +INFINITY</p> |                        |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND ((NOT C_AG_OXP_181) OR ((C_AG_OXP_181) AND ((NOT(C_AG_GL_007)))) C_AG_OXP_000 AND C_AG_OXP_178 AND C_AG_GL_024 AND (NOT_C_AG_OXP_181)                                                                                                                                                               |                        |
+| <b>Other PICSSs</b>      |                                                                                                                                                                                                                                                                                                                                       |                        |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                  |                        |
+| <b>Test procedure</b>    | <p>1. Place a Control Solution sample in the device sensor with a blood glucose level above the capabilities of the device sensor and check it with the PHD under test.</p> <p>IF C_AG_OXP_041 = FALSE</p>                                                                                                                            |                        |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>2. The test tool simulated PHG waits to receive an event report from the PHD under test. The event report shall contain the following value:</p> <p>a. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> event-type = MDC_NOTI_SCAN_REPORT_FIXED (0x0D 0x1D)</li> <li><input type="checkbox"/> obj-handle = 2 (Control solution)</li> <li><input type="checkbox"/> obs-val-data = <ul style="list-style-type: none"> <li>• Basic-Nu-Observed-Value = 0x07FE</li> </ul> </li> </ul> <p>IF C_AG_OXP_041 = TRUE</p> <p>3. The test tool simulated PHG issues a GET for the PM-Store object (or objects) and a Get-Segment-Info with SegmSelection set to all-segments. Then, the PHG sends a request to the PM-Segments that contains data. The PHD issues an action response and starts data transfer. A event report with the following values shall be present:</p> <p>a. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> event-type = MDC_NOTI_SEGMENT_DATA (0x0D 0x21)</li> <li><input type="checkbox"/> obj-handle = 2 (Control solution)</li> <li><input type="checkbox"/> obs-val-data = <ul style="list-style-type: none"> <li>• Basic-Nu-Observed-Value = 0x07FE</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              | The vendor must provide a Control Solution with a blood glucose level above the capabilities of the device sensor.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/GL/BV-025                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |
+| <b>TP label</b>          | Control Solution measurement below the capabilities of the device sensor without Device and Sensor Status Annunciation object                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-10417] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | CtrlSol 15; M          |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>In Standard Configuration 1701 (0x06A5) or 1702 (0x06A6), or in an extended configuration that does not include the Device and Sensor Status Annunciation object,, a Control Solution measurement that is below the capabilities of the device sensor shall be indicated with an observed value of -INFINITY</p>                                                                                                                                                                                                                                                |                        |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_178 AND ((NOT C_AG_OXP_181) OR ((C_AG_OXP_181) AND ((NOT(C_AG_GL_007))))))                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |
+| <b>Other PICSSs</b>      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |
+| <b>Test procedure</b>    | <p>1. Place a Control Solution sample in the device sensor with a blood glucose level above the capabilities of the device sensor and check it with the PHD under test.</p> <p>IF C_AG_OXP_041 = FALSE</p> <p>2. The test tool simulated PHG waits to receive an event report from the PHD under test. The event report shall contain the following value:</p> <p>a. Data APDU</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> event-type = MDC_NOTI_SCAN_REPORT_FIXED (0x0D 0x1D)</li> <li><input type="checkbox"/> obj-handle = 2 (Control Solution)</li> </ul> |                        |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><input type="checkbox"/> obs-val-data =</p> <ul style="list-style-type: none"> <li>• Basic-Nu-Observed-Value = 0x0802</li> </ul> <p>IF C_AG_OXP_041 = TRUE</p> <p>3. The test tool simulated PHG issues a GET for the PM-Store object (or objects) and a Get-Segment-Info with SegmSelection set to all-segments. Then, the PHG sends a request to the PM-Segments that contains data. The PHD issues an action response and starts data transfer. A event report with the following values shall be present:</p> <p>a. Data APDU</p> <p><input type="checkbox"/> event-type = MDC_NOTI_SEGMENT_DATA (0x0D 0x21)</p> <p><input type="checkbox"/> obj-handle = 2 (Control solution)</p> <p><input type="checkbox"/> obs-val-data =</p> <ul style="list-style-type: none"> <li>• Basic-Nu-Observed-Value = 0x0802</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes</b>              | The vendor must provide a Control Solution with a blood glucose level below the capabilities of the device sensor.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+# 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-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] PHD PICS and PIXIT Test Tool v7.0.0.0 – Excel sheet v1.12.  
+<https://handle.itu.int/11.1002/2000/12067>
+- [b-PHG PICS & PIXIT] PHG PICS and PIXIT Test Tool v7.0.0.0 – Excel sheet v1.10.  
+<https://handle.itu.int/11.1002/2000/12067>
+- [b-TI] Testable items. Test Tool v7.0.0.0 – Excel sheet v1.9.  
+<https://handle.itu.int/11.1002/2000/12067>
+
+
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.845.3-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..61904c12b802df120c05ae72cd89a3ef2690dd5b
--- /dev/null
+++ b/marked/H/T-REC-H.845.3-201704-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.845.4-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg b/marked/H/T-REC-H.845.4-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ca0dce65df64f4fb10a81b8f87284f793e4b1d3d
--- /dev/null
+++ b/marked/H/T-REC-H.845.4-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.6-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.845.6-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..61904c12b802df120c05ae72cd89a3ef2690dd5b
--- /dev/null
+++ b/marked/H/T-REC-H.845.6-201704-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.845.7-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.845.7-201704-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c7318fb3b40260cb5875ac866d975c50b49262e3
--- /dev/null
+++ b/marked/H/T-REC-H.845.7-201704-I_PDF-E/raw.md
@@ -0,0 +1,1090 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.845.7**
+
+(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 5G: Strength fitness equipment**
+
+Recommendation ITU-T H.845.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                                                                                       | 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        |
+| <b>Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN)</b> | <b>H.820–H.859</b> |
+| 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.7
+
+# Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5G: Strength fitness equipment
+
+## Summary
+
+Recommendation ITU-T H.845.7 provides a test suite structure (TSS) and the test purposes (TP) for strength fitness equipment 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.7 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5G: Device Specializations. Personal Health Device (Strength) (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.7  | 2015-01-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/12268">11.1002/1000/12268</a> |
+| 2.0     | ITU-T H.845.7  | 2016-07-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12944">11.1002/1000/12944</a> |
+| 3.0     | ITU-T H.845.7  | 2017-04-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/13225">11.1002/1000/13225</a> |
+
+## 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, strength fitness equipment, touch area network.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 (TPs) .....              | 8    |
+| A.1 TP definition conventions.....             | 8    |
+| A.2 Subgroup 1.3.7: Strength (ST).....         | 9    |
+| 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 Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5G: Device Specializations. Personal Health Device (Strength) (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_5G_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_5G_v1.2.doc" as a baseline and adds new features included in [b-CDG 2012]: <ul style="list-style-type: none"> <li>• Max APDU size for GM, BCA and ECG</li> </ul>                                                                                                                         |
+| 1.4     | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_PAN-LAN_PART_5G_v1.3.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]: <ul style="list-style-type: none"> <li>• Adds glucose meter BLE</li> <li>• Adds BLE SSP support</li> <li>• Adds NFC new transport</li> <li>• Adds INR device specialization</li> </ul> |
+| 1.5     | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_PLT_PART_5G_v1.4.doc" as a baseline and it adds new features included in Documentation Enhancements: <ul style="list-style-type: none"> <li>• "Other PICS" row added</li> </ul>                                                                                            |
+| 1.5     | 2015-07-01 | Initial release for Test Tool DG2015. This is the same version as "TSS&TP_DG2013_PLT_PART_5G_v1.4.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.6     | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2015_PLT_PART_5G_v1.5.doc" as a baseline and it adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016]                                                                                                                                                                                              |
+
+# **Recommendation ITU-T H.845.7**
+
+# Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5G: Strength fitness equipment
+
+# **1 Scope**
+
+The scope of this Recommendation<sup>1</sup> 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 5G.
+
+- 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
+
+---
+
+<sup>1</sup> 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-10442] IEEE 11073-10442-2015, *Health informatics – Personal health device communication – Part 10442: Device specialization – Strength fitness equipment*.  
+<https://www.iso.org/standard/66212.html>  
+ (Equivalent to the IEEE version:  
+<http://standards.ieee.org/findstds/standard/11073-10442-2008.html>)
+- [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.  
+<https://www.iso.org/standard/54331.html> with  
+<https://www.iso.org/standard/63972.html>
+- [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.  
+<https://www.iso.org/standard/66717.html> with  
+<https://www.iso.org/standard/71886.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                            |
+| DIMLESS | Dimension-less                                        |
+| 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 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.7 (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 <http://handle.itu.int/11.1002/2000/12067>.
+
+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>/<DUT>/<GR>/<SGR>/<XX> – <NNN>). It is specified according to the naming convention defined below:
+  - Each test purpose identifier is introduced by the prefix "TP".
+  - <TT>: 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)
+  - <DUT>: This is the device under test:
+    - PHD: Personal Health Device
+    - PHG: Personal Health Gateway
+  - <GR>: This identifies a group of test cases.
+  - <SGR>: This identifies a subgroup of test cases.
+  - <XX>: This identifies the type of testing.
+    - BV: Valid behaviour test
+    - BI: Invalid behaviour test
+  - <NNN>: 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.7: Strength (ST)
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                        |  |  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------|--|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ST/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                        |  |  |
+| <b>TP label</b>          | Get MDS Object for Strength fitness equipment specialization: Mandatory, Conditional and Optional Attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                        |  |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-10442] |                        |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | StrenMDSClassAttr 1; M | StrenMDSClassAttr 2; M |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | StrenMDSClassAttr 4; R | StrenMDSClassAttr 5; R |  |  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | StrenMDSClassAttr 6; M |                        |  |  |
+| <b>Test purpose</b>      | Check that:<br>The MDS Object contains the attributes specified for a Strength Fitness Personal Health Device (PHD)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                        |  |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_175                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |                        |  |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                        |  |  |
+| <b>Initial condition</b> | The simulated Personal Health Gateway (PHG) and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                        |  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>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.</li> <li>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:<br/> MDS attributes <ol style="list-style-type: none"> <li>Mandatory attribute System-model <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_MODEL</li> <li><input type="checkbox"/> attribute-type = SystemModel</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value = {Manufacturer, Model}</li> </ul> </li> <li>Mandatory attribute Dev-Configuration-Id <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_DEV_CONFIG_ID</li> <li><input type="checkbox"/> attribute-type = ConfigId(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = between &lt; 0x4000 and 0x7FFF &gt;</li> </ul> </li> <li>Recommended attribute Power-Status <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_POWER_STAT</li> <li><input type="checkbox"/> attribute-type = PowerStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = ON_MAINS (0x8000) or ON_BATTERY(0x4000).</li> </ul> </li> <li>Recommended attribute Battery-Level <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_VAL_BATT_CHARGE</li> <li><input type="checkbox"/> attribute-type = INT-U16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;undefined if value&gt;100 &gt;</li> </ul> </li> </ol> </li> </ol> |                        |                        |  |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>e. Recommended attribute Remaining-Battery-Time</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_BATT_REMAIN</li> <li><input type="checkbox"/> attribute-type = BatMeasure</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value = &lt;units shall be set to one of: MDC_DIM_MIN, MDC_DIM_HR, MDC_DIM_DAY &gt;</li> </ul> <p>f. Mandatory attribute System-Type-Spec-List</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SYS_TYPE_SPEC_LIST</li> <li><input type="checkbox"/> attribute-type = TypeVerList</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value =MDC_DEV_SPEC_PROFILE_HF_STRENGTH,1</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                     |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ST/BV-004_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                     |
+| <b>TP label</b>          | MDS-Configuration. Check Objects                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-10442] |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | RepCountAttr 1; O      | ResisAttr 1; O      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | SetAttr 1; O           | ExposAtt 1; O       |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ExGripAttr 1; O        | ExMovAttr 1; O      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        | trenMDSObjEven 1; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>MDS-Configuration-Event shall be sent in Confirmed Mode. Configuration report contains objects declared by the vendor.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                     |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_175                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |                     |
+| <b>Other PICS</b>        | C_AG_OXP_010, C_AG_ST_012, C_AG_ST_030, C_AG_ST_050, C_AG_ST_090, C_AG_ST_113, C_AG_ST_131, C_AG_ST_153                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                     |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                     |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The PHD under test sends an AARQ message to the simulated PHG.</li> <li>2. The simulated PHG issues an AARE message with result "accepted-unknown-config".</li> <li>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: <ol style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = PrstApdu</li> <li><input type="checkbox"/> field-length =2 bytes</li> <li><input type="checkbox"/> field-value =0xE7 0x00</li> </ul> </li> <li>b. invoke-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = InvokeIDType</li> <li><input type="checkbox"/> field-length =INT-U16</li> <li><input type="checkbox"/> field- value=&lt;Not relevant for this test&gt;</li> </ul> </li> <li>c. message</li> </ol> </li> </ol> |                        |                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = roiv-cmip-confirmed-event-report</li> <li><input type="checkbox"/> field-length =two bytes</li> <li><input type="checkbox"/> field- value=0x01 0x01 (EventReportArgumentSimple)</li> </ul> <p>d. obj-handle (EventReportArgumentSimple)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = HANDLE</li> <li><input type="checkbox"/> field-length =INT-U16</li> </ul> <p>e. event-time (EventReportArgumentSimple)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = Relative Time</li> <li><input type="checkbox"/> field-length =INT-U32</li> <li><input type="checkbox"/> field-value = <ul style="list-style-type: none"> <li>• IF NOT C_AG_OXP_010 THEN value = 0xFF 0xFF 0xFF 0xFF</li> </ul> </li> </ul> <p>f. event-type (EventReportArgumentSimple)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = OID-Type</li> <li><input type="checkbox"/> field-length =INT-U16</li> <li><input type="checkbox"/> field- value=0x 0D 0x 1C (MDC_NOTI_CONFIG)</li> </ul> <p>g. config-report-id (ConfigReport)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = ConfigId</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field- value = &lt;Between 0x40 0x00 and 0x7F 0xFF&gt;</li> </ul> <p>h. obj-class ( ConfigReport → ConfigObjectList (ConfigObject))</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = OID-Type</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field-value=Objects that will be checked: <ul style="list-style-type: none"> <li><input type="checkbox"/> Set Object shall be present. <ul style="list-style-type: none"> <li><input type="checkbox"/> IF C_AG_ST_012 THEN Repetition numeric object is present, ELSE it is not present.</li> <li><input type="checkbox"/> IF C_AG_ST_030 THEN Resistance numeric object is present, ELSE it is not present.</li> <li><input type="checkbox"/> IF C_AG_ST_050 THEN Repetition numeric object is present, ELSE it is not present.</li> <li><input type="checkbox"/> IF C_AG_ST_090 THEN Exercise Position enumeration object is present, ELSE it is not present.</li> <li><input type="checkbox"/> IF C_AG_ST_113 THEN Exercise Laterality enumeration object is present, ELSE it is not present.</li> <li><input type="checkbox"/> IF C_AG_ST_131 THEN Exercise Grip enumeration object is present, ELSE it is not present. Movement enumeration object is present, ELSE it is not present.</li> </ul> </li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                 |                                            |                        |                   |
+|-----------------|--------------------------------------------|------------------------|-------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/ST/BV-004_B               |                        |                   |
+| <b>TP label</b> | Repetition Count Numeric Object attributes |                        |                   |
+| <b>Coverage</b> | <b>Spec</b>                                | [ISO/IEEE 11073-10442] |                   |
+|                 | <b>Testable</b>                            | RepCountAttr 2; M      | RepCountAttr 3; R |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                    |                   |                    |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-------------------|--------------------|
+|                          | <b>items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | RepCountAttr 5; R  | RepCountAttr 6; M | RepCountAttr 7; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | RepCountAttr 8; R  | RepCountAttr 9; R | RepCountAttr 10; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | RepCountAttr 11; M |                   |                    |
+| <b>Test purpose</b>      | Check that:<br>The Repetition Count Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                    |                   |                    |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_175 AND C_AG_ST_012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                    |                   |                    |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                    |                   |                    |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                    |                   |                    |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The PHD under test sends an AARQ message to the simulated PHG.</li> <li>2. The simulated PHG issues an AARE message with result "accepted-unknown-config".</li> <li>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.</li> <li>4. Record the handle of the Set object.</li> <li>5. The Repetition Count object shall be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_HF (129)   MDC_HF_REP_COUNT (202)</li> </ol> </li> <li>b. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• bit 0 (mss-avail-intermittent(0)) shall be set.</li> <li>• bit 1(mss-avail-stored-data(1)) shall be set.</li> <li>• bit 2 (mss-upd-aperiodic(2)) shall be set.</li> <li>• bit 3(mss-msmt-aperiodic(3)) shall be set</li> <li>• bit 9 (mss-acc-agent-initiated(9)) shall be set.</li> <li>• The other bits have to be 0.</li> </ol> </li> </ol> </li> <li>a. Mandatory attribute Source-Handle-Reference <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = Handle of the Set object to which this object is associated</li> </ol> </li> <li>c. Not Recommended attribute Supplemental-Types <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =Sequence of TYPE (TYPE.length= 4 bytes)</li> </ol> </li> <li>d. Not Recommended attribute Metric-Structure-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (Sequence of (ms-struct.length =1byte(INT-</li> </ol> </li> </ol> </li> </ol> |                    |                   |                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>U8) + ms-comp-no =1byte(INT-U8)))</p> <ul style="list-style-type: none"> <li>e. Not Recommended attribute Compound-Simple-Nu-Observed-Value <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_SIMP</li> <li><input type="checkbox"/> attribute-type = SimpleNuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; ((SimpleNuObsValueCmp ::= SEQUENCE OF SimpleNuObsValue ; SimpleNuObsValue ::= FLOAT-Type)</li> </ul> </li> <li>f. Not Recommended attribute Compound-Basic-Nu-Observed-Value <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (SimpleNuObsValueCmp ::= SEQUENCE OF BasicNuObsValue ; BasicNuObsValue ::= SFLOAT-Type)</li> </ul> </li> <li>g. Not Recommended attribute Compound-Nu-Observed-Value <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS</li> <li><input type="checkbox"/> attribute-type = NuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (NuObsValueCmp ::= SEQUENCE OF NuObsValue)</li> </ul> </li> </ul> <p>6. IF C_AG_OXP_293:</p> <ul style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ul> <p>7. Wait for the PHD under test and the simulated PHG to reach the Operating state.</p> <p>8. Take a measurement in the PHD.</p> <p>9. Wait until the PHG receives an event report.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• All checked values are as specified in the test procedure.</li> <li>• In step 9, check that only non-negative values are used (for observed values of the Repetition Count object).</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                 |                                      |                                                                                                                                                                                                                                                                                                                                                                                                  |  |                |                |                |                |                |                |                |                |                 |                 |                 |
+|-----------------|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|-----------------|-----------------|-----------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/ST/BV-005           |                                                                                                                                                                                                                                                                                                                                                                                                  |  |                |                |                |                |                |                |                |                |                 |                 |                 |
+| <b>TP label</b> | Resistance Numeric Object attributes |                                                                                                                                                                                                                                                                                                                                                                                                  |  |                |                |                |                |                |                |                |                |                 |                 |                 |
+| <b>Coverage</b> | <b>Spec</b>                          | [ISO/IEEE 11073-10442]                                                                                                                                                                                                                                                                                                                                                                           |  |                |                |                |                |                |                |                |                |                 |                 |                 |
+|                 | <b>Testable items</b>                | <table border="1" style="width: 100%;"> <tr> <td>ResisAttr 2; M</td> <td>ResisAttr 3; R</td> <td>ResisAttr 4; M</td> </tr> <tr> <td>ResisAttr 5; R</td> <td>ResisAttr 6; M</td> <td>ResisAttr 7; M</td> </tr> <tr> <td>ResisAttr 8; R</td> <td>ResisAttr 9; R</td> <td>ResisAttr 10; R</td> </tr> <tr> <td>ResisAttr 11; M</td> <td>ResisAttr 12; M</td> <td>ResisAttr 13; M</td> </tr> </table> |  | ResisAttr 2; M | ResisAttr 3; R | ResisAttr 4; M | ResisAttr 5; R | ResisAttr 6; M | ResisAttr 7; M | ResisAttr 8; R | ResisAttr 9; R | ResisAttr 10; R | ResisAttr 11; M | ResisAttr 12; M |
+| ResisAttr 2; M  | ResisAttr 3; R                       | ResisAttr 4; M                                                                                                                                                                                                                                                                                                                                                                                   |  |                |                |                |                |                |                |                |                |                 |                 |                 |
+| ResisAttr 5; R  | ResisAttr 6; M                       | ResisAttr 7; M                                                                                                                                                                                                                                                                                                                                                                                   |  |                |                |                |                |                |                |                |                |                 |                 |                 |
+| ResisAttr 8; R  | ResisAttr 9; R                       | ResisAttr 10; R                                                                                                                                                                                                                                                                                                                                                                                  |  |                |                |                |                |                |                |                |                |                 |                 |                 |
+| ResisAttr 11; M | ResisAttr 12; M                      | ResisAttr 13; M                                                                                                                                                                                                                                                                                                                                                                                  |  |                |                |                |                |                |                |                |                |                 |                 |                 |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                 |  |  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--|--|
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | ResisAttr 14; M |  |  |
+| <b>Test purpose</b>      | Check that:<br>The Resistance Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                 |  |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_175 AND C_AG_ST_030                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                 |  |  |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                 |  |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                 |  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The PHD under test sends an AARQ message to the simulated PHG.</li> <li>2. The simulated PHG issues an AARE message with result "accepted-unknown-config".</li> <li>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.</li> <li>4. Record the handle of the Set object</li> <li>5. The Resistance object shall be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_HF (129)   MDC_HF_RESISTANCE (203)</li> </ol> </li> <li>b. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• bit 0 (mss-avail-intermittent(0)) shall be set.</li> <li>• bit 1(mss-avail-stored-data(1)) shall be set.</li> <li>• bit 2 (mss-updt-aperiodic(2)) shall be set.</li> <li>• bit 3(mss-msmt-aperiodic(3)) shall be set</li> <li>• bit 9 (mss-acc-agent-initiated(9)) shall be set.</li> <li>• The other bits have to be 0.</li> </ol> </li> </ol> </li> <li>c. Mandatory attribute Unit-Code <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= <ol style="list-style-type: none"> <li>• If the resistance is measured in weight → attribute-value= MDC_DIM_X_G or MDC_DIM_LB</li> <li>• If the resistance is measured in an indexed value → attribute-value = MDC_DIM_DIMLESS</li> </ol> </li> </ol> </li> <li>d. Mandatory attribute Source-Handle-Reference <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = Handle of the Set object to which this object is associated.</li> </ol> </li> <li>e. Optional attribute Unit-Label-String <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_LABEL_STRING</li> <li><input type="checkbox"/> attribute-type = OCTET STRING</li> </ol> </li> </ol> </li> </ol> |                 |  |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value= If the resistance is measured in an indexed value → Label-string may provide additional information.</li> </ul> <p>f. Not Recommended attribute Supplemental-Types</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes))</li> </ul> <p>g. Not Recommended attribute Metric-Structure-Small</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (Sequence of (ms-struct.length = 1byte(INT-U8) + ms-comp-no = 1byte(INT-U8)))</li> </ul> <p>h. Not Recommended attribute Compound-Simple-Nu-Observed-Value</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_SIMP</li> <li><input type="checkbox"/> attribute-type = SimpleNuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (SimpleNuObsValueCmp ::= SEQUENCE OF SimpleNuObsValue ; SimpleNuObsValue ::= FLOAT-Type)</li> </ul> <p>i. Not Recommended attribute Compound-Basic-Nu-Observed-Value</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (SimpleNuObsValueCmp ::= SEQUENCE OF BasicNuObsValue ; BasicNuObsValue ::= SFLOAT-Type)</li> </ul> <p>j. Not Recommended attribute Compound-Nu-Observed-Value</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_SIMP</li> <li><input type="checkbox"/> attribute-type = NuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (NuObsValueCmp ::= SEQUENCE OF NuObsValue)</li> </ul> <p>6. IF C_AG_OXP_293:</p> <ul style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ul> <p>7. Wait for the PHD under test and the simulated PHG to reach the Operating state.</p> <p>8. Take a measurement in the PHD.</p> <p>9. Wait until the PHG receives an event report.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• All checked values are as specified in the test procedure.</li> <li>• In step 9, check that only non-negative values are used (for observed values of the Resistance object).</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |               |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ST/BV-006                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |               |
+| <b>TP label</b>          | Repetition Numeric Object attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-10442] |               |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | RepAttr 2; M           | RepAttr 3; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | RepAttr 5; R           | RepAttr 6; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | RepAttr 8; R           | RepAttr 9; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | RepAttr 11; M          | RepAttr 13; M |
+| <b>Test purpose</b>      | Check that:<br>The Repetition Numeric object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |               |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_175 AND C_AG_ST_050                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |               |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The PHD under test sends an AARQ message to the simulated PHG.</li> <li>2. The simulated PHG issues an AARE message with result "accepted-unknown-config".</li> <li>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.</li> <li>4. Record the handle of the Set object.</li> <li>5. The Repetition object shall be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_HF (129)   MDC_HF_REPETITION (201)</li> </ol> </li> <li>b. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• bit 0 (mss-avail-intermittent(0)) shall be set.</li> <li>• bit 1(mss-avail-stored-data(1)) shall be set.</li> <li>• bit 2 (mss-upd-aperiodic(2)) shall be set.</li> <li>• bit 3(mss-msmt-aperiodic(3)) shall be set</li> <li>• bit 9 (mss-acc-agent-initiated(9)) shall be set.</li> <li>• The other bits have to be 0.</li> </ol> </li> </ol> </li> <li>c. Mandatory attribute Unit-Code <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value= MDC_DIM_X_M or MDC_DIM_X_INCH</li> </ol> </li> <li>d. Mandatory attribute Source-Handle-Reference <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> </ol> </li> </ol> </li> </ol> |                        |               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = Handle of the Set object to which this object is associated. Tested later</li> </ul> <p>e. Not Recommended attribute Supplemental-Types</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes))</li> </ul> <p>f. Not Recommended attribute Metric-Structure-Small</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))</li> </ul> <p>g. Not Recommended attribute Compound-Simple-Nu-Observed-Value</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_SIMP</li> <li><input type="checkbox"/> attribute-type = SimpleNuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (SimpleNuObsValueCmp ::= SEQUENCE OF SimpleNuObsValue ; SimpleNuObsValue ::= FLOAT-Type)</li> </ul> <p>h. Not Recommended attribute Compound-Basic-Nu-Observed-Value</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_BASIC</li> <li><input type="checkbox"/> attribute-type = BasicNuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; SimpleNuObsValueCmp ::= SEQUENCE OF BasicNuObsValue ; BasicNuObsValue ::= SFLOAT-Type)</li> </ul> <p>i. Not recommended attribute Compound-Nu-Observed-Value</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_CMPD_VAL_OBS_SIMP</li> <li><input type="checkbox"/> attribute-type = NuObsValueCmp</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (NuObsValueCmp ::= SEQUENCE OF NuObsValue)</li> </ul> <p>6. IF C_AG_OXP_293:</p> <ul style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ul> <p>7. Wait for the PHD under test and the simulated PHG to reach the Operating state.</p> <p>8. Take a measurement in the PHD.</p> <p>9. Wait until the PHG receives an event report.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• All checked values are as specified in the test procedure.</li> <li>• In step 9, check that only non-negative values are used (for observed values of the Repetition object).</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|              |  |
+|--------------|--|
+| <b>Notes</b> |  |
+|--------------|--|
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/ST/BV-007                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |  |
+| <b>TP label</b>           | Repetition Count Numeric Object and Set object attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-10442] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | RepCountAttr 12; M     |  |
+| <b>Test purpose</b>       | Check that:<br>This object shall use the same timestamp attribute and value as the associated Set object.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |  |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_175 AND C_AG_ST_012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |  |
+| <b>Other PICS</b>         | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The PHD under test sends an AARQ message to the simulated PHG.</li> <li>2. The simulated PHG issues an AARE message with result "accepted-unknown-config".</li> <li>3. The PHD under test sends its configuration to the simulated PHG.</li> <li>4. IF C_AG_OXP_293: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ol style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ol> </li> </ol> </li> <li>5. Record the handle and Attribute-Value-Map of the Set object and the Repetition Count object that is associated to it.</li> <li>6. Take a measurement.</li> <li>7. Wait for the simulated PHG to receive it.</li> </ol> |                        |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 7 if the Repetition Count measurement contains a timestamp it shall be the same (attribute and value) as that for the Set object.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |  |
+
+|                 |                                                     |                   |  |
+|-----------------|-----------------------------------------------------|-------------------|--|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/ST/BV-008                          |                   |  |
+| <b>TP label</b> | Resistance Numeric Object and Set object attributes |                   |  |
+| <b>Coverage</b> | <b>Spec</b>                                         | [IEEE11073-10442] |  |
+|                 | <b>Testable items</b>                               | ResisAttr 15; M   |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>       | Check that:<br>This object shall use the same timestamp attribute and value as the associated Set object.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_175 AND C_AG_ST_030                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Other PICS</b>         | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The PHD under test sends an AARQ message to the simulated PHG.</li> <li>2. The simulated PHG issues an AARE message with result "accepted-unknown-config".</li> <li>3. The PHD under test sends its configuration to the simulated PHG.</li> <li>4. IF C_AG_OXP_293: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ol> </li> <li>5. Record the handle and the Attribute-Value-Map of the Set object and the Resistance object that is associated to it.</li> <li>6. Take a measurement.</li> <li>7. Wait for the simulated PHG to receive it.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 7 if the Resistance measurement contains a timestamp it shall be the same (attribute and value) as that for the Set object.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                          |                                                                                                                                                                                                                                                                                              |                        |  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ST/BV-009                                                                                                                                                                                                                                                                   |                        |  |
+| <b>TP label</b>          | Repetition Numeric Object and Set object attributes                                                                                                                                                                                                                                          |                        |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                  | [ISO/IEEE 11073-10442] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                        | RepAttr 14; M          |  |
+| <b>Test purpose</b>      | Check that:<br>This object shall use the same timestamp attribute and value as the associated Set object.                                                                                                                                                                                    |                        |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_175 AND C_AG_ST_050                                                                                                                                                                                                                                                |                        |  |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                     |                        |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                      |                        |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The PHD under test sends an AARQ message to the simulated PHG.</li> <li>2. The simulated PHG issues an AARE message with result "accepted-unknown-config".</li> <li>3. The PHD under test sends its configuration to the simulated PHG.</li> </ol> |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>4. IF C_AG_OXP_293:</p> <ul style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ul> <p>5. Record the handle and Attribute-Value-Map of the Set object and the Repetition Numeric Object that is associated to it.</p> <p>6. Take a measurement.</p> <p>7. Wait for the simulated PHG to receive it.</p> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 7 if the Repetition measurement contains a timestamp it shall be the same (attribute) as that for the Set object.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |               |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/ST/BV-011                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |               |
+| <b>TP label</b>           | Repetition Object observed values                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |               |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-10442] |               |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | RepAttr 15; M          | RepAttr 16; M |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>If the related Set object has a Measure-Active-Period defined, the timestamp for this object shall fall within the time range defined by the associated Set object's timestamp attribute and lasts for the Measure-Active-Period defined by the related Set object's Measure-Active-Period attribute.</p> <p>[AND]</p> <p>If the Repetition object specifies a Measure-Active-Period, the time period defined by the Repetition object shall fall completely within the time range defined by the associated Set object.</p> |                        |               |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_175 AND C_AG_ST_050                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |               |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |               |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |               |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Take a measurement with the PHD under test.</li> <li>2. Wait for the simulated PHG to receive it. Record the Time-Stamp and the Measure-Active-Period of the Set object and of the Repetition object.</li> </ol>                                                                                                                                                                                                                                                                                         |                        |               |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The Time-Stamp of the Repetition measurement shall fall between the time range defined by the Time-Stamp and the Measure-Active-Period of the Set measurement.</li> <li>• The Measure-Active-Period of the Repetition measurement shall be within the boundaries of the Set one.</li> </ul>                                                                                                                                                                                                               |                        |               |
+
+|       |  |
+|-------|--|
+| Notes |  |
+|-------|--|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |               |               |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ST/BV-012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |               |               |
+| <b>TP label</b>          | Set Enumeration Object attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |               |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [ISO/IEEE 11073-10442] |               |               |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | SetAttr 2; M           | SetAttr 3; R  | SetAttr 4; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | SetAttr 5; R           | SetAttr 6; R  | SetAttr 7; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | SetAttr 8; R           | SetAttr 9; R  | SetAttr 10; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | SetAttr 11; R          | SetAttr 12; M |               |
+| <b>Test purpose</b>      | Check that:<br>The Set Enumeration object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |               |               |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_175                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |               |               |
+| <b>Other PICS</b>        | C_AG_ST_156                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |               |               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |               |               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The PHD under test sends an AARQ message to the simulated PHG.</li> <li>2. The simulated PHG issues an AARE message with result "accepted-unknown-config".</li> <li>3. The PHD under test sends its configuration to the simulated PHG.</li> <li>4. The Set object shall be:           <ol style="list-style-type: none"> <li>a. Mandatory Type               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of partition (NomPartition (INT-U16)) and code (OID-Type)))</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_HF   MDC_HF_SET</li> </ul> </li> <li>b. Not Recommended attribute Supplemental-Types               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes → partition NomPartition (INT-U16) and code (OID-Type)))</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00                   <ul style="list-style-type: none"> <li>• bit 0 (mss-avail-intermittent(0)) shall be set</li> <li>• bit 1 is set(mss-avail-stored-data(1)) shall be set</li> <li>• bit 2 is set(mss-updt-aperiodic(2)) shall be set,</li> <li>• bit 3 is set(mss-msmt-aperiodic(3)) shall be set</li> <li>• bit 9 is set(mss-acc-agent-initiated(9)) shall be set</li> <li>• The other bits have to be 0.</li> </ul> </li> </ul> </li> <li>d. Not Recommended attribute Metric-Structure-Small</li> </ol> </li> </ol> |                        |               |               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;(Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8))))</li> </ul> <p>e. Not Recommended attribute Source-Handle-Reference</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>f. Conditional attribute Measure-Active-Period</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>g. Mandatory attribute Enum-Observed-Value-Simple-OID</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIMP_OID</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = MDC_MUSC_* (See Annex C of [b-ISO/IEEE 11073-10408])</li> </ul> <p>h. Not Recommended attribute Enum-Observed-Value-Simple-Bit-Str</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIMP_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>i. Not Recommended attribute Enum-Observed-Value-Basic-Bit-Str</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-16</li> <li><input type="checkbox"/> attribute-value.length = 2bytes</li> </ul> <p>j. Not Recommended attribute Enum-Observed-Value-Simple-Str</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_STR</li> <li><input type="checkbox"/> attribute-type = EnumPrintableString</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> <p>k. Not Recommended attribute Enum-Observed-Value</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_VAL_ENUM_OBS</li> <li><input type="checkbox"/> attribute-type = EnumObsValue</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> <p>l. Mandatory attribute Enum-Observed-Value-Partition</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                 |                                                 |
+|-----------------|-------------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/ST/BV-013                      |
+| <b>TP label</b> | Exercise Position Enumeration Object attributes |
+
+|                          |                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                 |                 |  |
+|--------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------|--|
+| <b>Coverage</b>          | <b>Spec</b>           | [ISO/IEEE 11073-10442]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                 |                 |  |
+|                          | <b>Testable items</b> | ExeposAtt 2; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | ExeposAtt 3; R  | ExeposAtt 4; M  |  |
+|                          |                       | ExeposAtt 5; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | ExeposAtt 6; M  | ExeposAtt 7; M  |  |
+|                          |                       | ExeposAtt 8; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | ExeposAtt 9; R  | ExeposAtt 10; R |  |
+|                          |                       | ExeposAtt 11; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | ExeposAtt 12; R | ExeposAtt 15; M |  |
+| <b>Test purpose</b>      |                       | Check that:<br>The Exercise Position Enumeration object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                 |                 |  |
+| <b>Applicability</b>     |                       | C_AG_OXP_000 AND C_AG_OXP_175 AND C_AG_ST_090                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                 |                 |  |
+| <b>Other PICS</b>        |                       | C_AG_ST_156                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                 |                 |  |
+| <b>Initial condition</b> |                       | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                 |                 |  |
+| <b>Test procedure</b>    |                       | <ol style="list-style-type: none"> <li>1. The PHD under test sends an AARQ message to the simulated PHG.</li> <li>2. The simulated PHG issues an AARE message with result "accepted-unknown-config".</li> <li>3. The PHD under test sends its configuration to the simulated PHG.</li> <li>4. The Exercise Position object shall be: <ol style="list-style-type: none"> <li>a. Mandatory Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (Sequence of partition (NomPartition (INT-U16)) and code (OID-Type)))</li> <li><input type="checkbox"/> attribute-value= MDC_PART_PHD_HF   MDC_HF_EXERCISE_POSITION</li> </ol> </li> <li>b. Not recommended attribute Supplemental-Types <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes → partition NomPartition (INT-U16) and code (OID-Type)))</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• bit 0 (mss-avail-intermittent(0)) shall be set</li> <li>• bit 1 is set(mss-avail-stored-data(1)) shall be set</li> <li>• bit 2 is set(mss-updt-aperiodic(2)) shall be set</li> <li>• bit 3 is set(mss-msmt-aperiodic(3)) shall be set</li> <li>• bit 9 is set(mss-acc-agent-initiated(9)) shall be set</li> <li>• The other bits have to be 0.</li> </ol> </li> </ol> </li> <li>d. Not Recommended attribute Metric-Structure-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))</li> </ol> </li> <li>e. Mandatory attribute Source-Handle-Reference</li> </ol> </li> </ol> |                 |                 |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = Handle of the Set object to which this object is associated</li> </ul> <p>f. Mandatory attribute Enum-Observed-Value-Simple-OID</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIMP_OID</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = MDC_HF_POSITION_* (See Annex C of [b-ISO/IEEE 11073-10408])</li> </ul> <p>g. Not Recommended attribute Enum-Observed-Value-Simple-Bit-Str</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIMP_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>h. Not Recommended attribute Enum-Observed-Value-Basic-Bit-Str</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>i. Not Recommended attribute Enum-Observed-Value-Simple-Str</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_STR</li> <li><input type="checkbox"/> attribute-type = EnumPrintableString</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> <p>j. Not Recommended attribute Enum-Observed-Value</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_VAL_ENUM_OBS</li> <li><input type="checkbox"/> attribute-type = EnumObsValue</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> <p>k. Not Recommended attribute Enum-Observed-Value-Partition</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                      |                                                                                                                                                                                 |                        |  |
+|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>         | TP/PLT/PHD/CLASS/ST/BV-014                                                                                                                                                      |                        |  |
+| <b>TP label</b>      | Exercise Position Object and Set object attributes                                                                                                                              |                        |  |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                     | [ISO/IEEE 11073-10442] |  |
+|                      | <b>Testable items</b>                                                                                                                                                           | ExeposAtt 14; M        |  |
+| <b>Test purpose</b>  | Check that:<br>The timestamp attribute used for an Exercise Position object instance shall be the same as that which is used for the Set object instance to which it is related |                        |  |
+| <b>Applicability</b> | C_AG_OXP_000 AND C_AG_OXP_175 AND C_AG_ST_090                                                                                                                                   |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICS</b>         | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The PHD under test sends an AARQ message to the simulated PHG.</li> <li>2. The simulated PHG issues an AARE message with the result "accepted-unknown-config".</li> <li>3. The PHD under test sends its configuration to the simulated PHG.</li> <li>4. IF C_AG_OXP_293: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li>❑ The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li>❑ Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ol> </li> <li>5. Record the handle and Attribute-Value-Mpa of the Set object and the Exercise Position object that is associated to it.</li> <li>6. Take a measurement.</li> <li>7. Wait for the simulated PHG to receive it.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 7 if the Exercise Position measurement contains a timestamp it shall be the same (attribute and value) as that for the Set object.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                          |                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                         |  |                 |                 |                 |                 |                 |                 |                 |                 |                  |                  |                  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|------------------|------------------|------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ST/BV-015                                                                                                                                                                                  |                                                                                                                                                                                                                                                                                                                                                                                                                                         |  |                 |                 |                 |                 |                 |                 |                 |                 |                  |                  |                  |
+| <b>TP label</b>          | Exercise Laterality enumeration Object attributes                                                                                                                                                           |                                                                                                                                                                                                                                                                                                                                                                                                                                         |  |                 |                 |                 |                 |                 |                 |                 |                 |                  |                  |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                 | [ISO/IEEE 11073-10442]                                                                                                                                                                                                                                                                                                                                                                                                                  |  |                 |                 |                 |                 |                 |                 |                 |                 |                  |                  |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                       | <table border="1" style="width: 100%; border-collapse: collapse;"> <tr> <td>ExLateAttr 2; M</td> <td>ExLateAttr 3; R</td> <td>ExLateAttr 4; M</td> </tr> <tr> <td>ExLateAttr 5; R</td> <td>ExLateAttr 6; M</td> <td>ExLateAttr 7; M</td> </tr> <tr> <td>ExLateAttr 8; R</td> <td>ExLateAttr 9; R</td> <td>ExLateAttr 10; R</td> </tr> <tr> <td>ExLateAttr 11; R</td> <td>ExLateAttr 12; R</td> <td>ExLateAttr 14; M</td> </tr> </table> |  | ExLateAttr 2; M | ExLateAttr 3; R | ExLateAttr 4; M | ExLateAttr 5; R | ExLateAttr 6; M | ExLateAttr 7; M | ExLateAttr 8; R | ExLateAttr 9; R | ExLateAttr 10; R | ExLateAttr 11; R | ExLateAttr 12; R |
+| ExLateAttr 2; M          | ExLateAttr 3; R                                                                                                                                                                                             | ExLateAttr 4; M                                                                                                                                                                                                                                                                                                                                                                                                                         |  |                 |                 |                 |                 |                 |                 |                 |                 |                  |                  |                  |
+| ExLateAttr 5; R          | ExLateAttr 6; M                                                                                                                                                                                             | ExLateAttr 7; M                                                                                                                                                                                                                                                                                                                                                                                                                         |  |                 |                 |                 |                 |                 |                 |                 |                 |                  |                  |                  |
+| ExLateAttr 8; R          | ExLateAttr 9; R                                                                                                                                                                                             | ExLateAttr 10; R                                                                                                                                                                                                                                                                                                                                                                                                                        |  |                 |                 |                 |                 |                 |                 |                 |                 |                  |                  |                  |
+| ExLateAttr 11; R         | ExLateAttr 12; R                                                                                                                                                                                            | ExLateAttr 14; M                                                                                                                                                                                                                                                                                                                                                                                                                        |  |                 |                 |                 |                 |                 |                 |                 |                 |                  |                  |                  |
+| <b>Test purpose</b>      | Check that:<br>The Exercise Laterality Enumeration object contains the attributes specified for Extended Configuration.                                                                                     |                                                                                                                                                                                                                                                                                                                                                                                                                                         |  |                 |                 |                 |                 |                 |                 |                 |                 |                  |                  |                  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_175 AND C_AG_ST_113                                                                                                                                                               |                                                                                                                                                                                                                                                                                                                                                                                                                                         |  |                 |                 |                 |                 |                 |                 |                 |                 |                  |                  |                  |
+| <b>Other PICS</b>        | C_AG_ST_156                                                                                                                                                                                                 |                                                                                                                                                                                                                                                                                                                                                                                                                                         |  |                 |                 |                 |                 |                 |                 |                 |                 |                  |                  |                  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                     |                                                                                                                                                                                                                                                                                                                                                                                                                                         |  |                 |                 |                 |                 |                 |                 |                 |                 |                  |                  |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The PHD under test sends an AARQ message to the simulated PHG.</li> <li>2. The simulated PHG issues an AARE message with the result "accepted-unknown-</li> </ol> |                                                                                                                                                                                                                                                                                                                                                                                                                                         |  |                 |                 |                 |                 |                 |                 |                 |                 |                  |                  |                  |
+
+config".
+
+3. The PHD under test sends its configuration to the simulated PHG.
+
+4. The Exercise Laterality object shall be:
+
+a. Mandatory Type
+
+- attribute-id = MDC\_ATTR\_ID\_TYPE
+- attribute-type = TYPE
+- attribute-value.length = <variable> (Sequence of partition (NomPartition (INT-U16)) and code (OID-Type)))
+- attribute-value= MDC\_PART\_PHD\_HF | MDC\_HF\_EXERCISE\_LATERALITY
+
+b. 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 → partition NomPartition (INT-U16) and code (OID-Type)))
+
+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)) shall be set
+  - bit 1 is set (mss-avail-stored-data(1)) shall be set
+  - bit 2 is set (mss-updt-aperiodic(2)) shall be set
+  - bit 3 is set (mss-msmt-aperiodic(3)) shall be set
+  - bit 9 is set (mss-acc-agent-initiated(9)) shall be set
+  - The other bits have to be 0.
+
+d. Not Recommended attribute Metric-Structure-Small
+
+- attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+- attribute-type = MetricStructureSmall
+- attribute-value.length = <variable> (Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))
+
+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 = Handle of the Set object to which this object is associated
+
+f. Mandatory attribute Enum-Observed-Value-Simple-OID
+
+- attribute-id= MDC\_ATTR\_ENUM\_OBS\_VAL\_SIMP\_OID
+- attribute-type = OID-Type (INT-U16)
+- attribute-value.length = 2 bytes
+- attribute-value = MDC\_HF\_LATERALITY\_\* (See Annex C of [b-ISO/IEEE 11073-10408])
+
+g. Not Recommended 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
+
+h. Not Recommended attribute Enum-Observed-Value-Basic-Bit-Str
+
+- attribute-id= MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> attribute-type = BITS-16<br><input type="checkbox"/> attribute-value.length = 2 bytes<br>i. Not Recommended attribute Enum-Observed-Value-Simple-Str<br><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_STR<br><input type="checkbox"/> attribute-type = EnumPrintableString<br><input type="checkbox"/> attribute-value.length = <variable><br>j. Not Recommended attribute Enum-Observed-Value<br><input type="checkbox"/> attribute-id= MDC_ATTR_VAL_ENUM_OBS<br><input type="checkbox"/> attribute-type = EnumObsValue<br><input type="checkbox"/> attribute-value.length = <variable><br>k. Not Recommended attribute Enum-Observed-Value-Partition<br><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_PART<br><input type="checkbox"/> attribute-type = NomPartition (INT-U16)<br><input type="checkbox"/> attribute-value.length = 2 bytes |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ST/BV-016                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |  |
+| <b>TP label</b>          | Exercise Laterality Object and Set object attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-10442] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | ExLateAttr 13; M       |  |
+| <b>Test purpose</b>      | Check that:<br>This object's timestamp shall be equal to the timestamp of the associated Set Object                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_175 AND C_AG_ST_113                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |  |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |  |
+| <b>Test procedure</b>    | 1. The PHD under test sends an AARQ message to the simulated PHG.<br>2. The simulated PHG issues an AARE message with the result "accepted-unknown-config".<br>3. The PHD under test sends its configuration to the simulated PHG.<br>4. IF C_AG_OXP_293:<br>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.<br>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.<br>c. IF the mds-time-mgr-set-time bit is set:<br><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and:<br><ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> <ol style="list-style-type: none"> <li>5. Record the handle and the Attribute-Value-Map of the Set object and the Exercise Laterality object that is associated to it.</li> <li>6. Take a measurement</li> <li>7. Wait for the simulated PHG to receive it.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 7 if the Exercise Laterality measurement contains a timestamp it shall be the same (attribute and value) as that for the Set object.</li> </ul>                                                                                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                  |                  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------|------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ST/BV-017                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                  |                  |
+| <b>TP label</b>          | Exercise Grip enumeration Object attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                  |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [ISO/IEEE 11073-10442] |                  |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ExGripAttr 2; M        | ExGripAttr 3; R  | ExGripAttr 4; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | ExGripAttr 5; R        | ExGripAttr 6; M  | ExGripAttr 7; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | ExGripAttr 8; R        | ExGripAttr 9; R  | ExGripAttr 10; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | ExGripAttr 11; R       | ExGripAttr 12; R | ExGripAttr 15; M |
+| <b>Test purpose</b>      | Check that:<br>The Exercise Grip Enumeration object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                  |                  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_175 AND C_AG_ST_131                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                  |                  |
+| <b>Other PICS</b>        | C_AG_ST_156                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                  |                  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                  |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The PHD under test sends an AARQ message to the simulated PHG.</li> <li>2. The simulated PHG issues an AARE message with the result "accepted-unknown-config".</li> <li>3. The PHD under test sends its configuration to the simulated PHG.</li> <li>4. The Exercise Grip object shall be: <ol style="list-style-type: none"> <li>a. Mandatory Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (Sequence of partition (NomPartition (INT-U16)) and code (OID-Type)))</li> <li><input type="checkbox"/> attribute-value= MDC_PART_PHD_HF   MDC_HF_EXERCISE_GRIP</li> </ul> </li> <li>b. Not Recommended attribute Supplemental-Types <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt; (Sequence of TYPE (TYPE.length= 4 bytes → partition NomPartition (INT-U16) and code (OID-Type)))</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> </ul> </li> </ol> </li> </ol> |                        |                  |                  |
+
+- attribute-type = MetricSpecSmall (BITS-16)
+- attribute-value  $\neq$  0x00 0x00
+  - bit 0 (mss-avail-intermittent(0)) shall be set
+  - bit 1 is set (mss-avail-stored-data(1)) shall be set
+  - bit 2 is set (mss-updt-aperiodic(2)) shall be set
+  - bit 3 is set (mss-msmt-aperiodic(3)) shall be set
+  - bit 9 is set(mss-acc-agent-initiated(9)) shall be set
+  - The other bits have to be 0.
+
+#### d. Not Recommended attribute Metric-Structure-Small
+
+- attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+- attribute-type = MetricStructureSmall
+- attribute-value.length = <variable> (Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no =1byte(INT-U8)))
+
+#### 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 = Handle of the Set object to which this object is associated.
+
+#### 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\_GRIP\_\* (See Annex C of [b-ISO/IEEE 11073-10408])
+
+#### g. Not Recommended 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
+
+#### h. Not Recommended attribute Enum-Observed-Value-Basic-Bit-Str
+
+- attribute-id= MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR
+- attribute-type = BITS-16
+- attribute-value.length = 2 bytes
+
+#### i. Not Recommended attribute Enum-Observed-Value-Simple-Str
+
+- attribute-id= MDC\_ATTR\_ENUM\_OBS\_VAL\_SIMP\_STR
+- attribute-type = EnumPrintableString
+- attribute-value.length =
+
+#### j. Not Recommended attribute Enum-Observed-Value
+
+- attribute-id= MDC\_ATTR\_VAL\_ENUM\_OBS
+- attribute-type = EnumObsValue
+- attribute-value.length =
+
+#### k. Not Recommended attribute Enum-Observed-Value-Partition
+
+- attribute-id= MDC\_ATTR\_ENUM\_OBS\_VAL\_PART
+- attribute-type = NomPartition(INT-U16)
+- attribute-value.length = 2 bytes
+
+|                           |                                                            |
+|---------------------------|------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure. |
+| <b>Notes</b>              |                                                            |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |  |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/ST/BV-018                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |  |
+| <b>TP label</b>           | Exercise Grip Object and Set object attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-10442] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | ExGripAttr 14; M       |  |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>The timestamp attribute used for an Exercise Grip object instance shall be the same as that which is used for the Set object instance to which it is related</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |  |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_175 AND C_AG_ST_131                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |  |
+| <b>Other PICS</b>         | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The PHD under test sends an AARQ message to the simulated PHG.</li> <li>2. The simulated PHG issues an AARE message with result "accepted-unknown-config".</li> <li>3. The PHD under test sends its configuration to the simulated PHG.</li> <li>4. IF C_AG_OXP_293: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ol> </li> <li>5. Record the handle and Attribute-Value-Map of the Set object and the Exercise Grip object that is associated to it.</li> <li>6. Take a measurement.</li> <li>7. Wait for the simulated PHG to receive it.</li> </ol> |                        |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 7 if the Exercise Grip measurement contains a timestamp it shall be the same (attribute and value) as that for the Set object.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |  |
+
+|                 |                                                 |                        |  |
+|-----------------|-------------------------------------------------|------------------------|--|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/ST/BV-019                      |                        |  |
+| <b>TP label</b> | Exercise Movement enumeration Object attributes |                        |  |
+| <b>Coverage</b> | <b>Spec</b>                                     | [ISO/IEEE 11073-10442] |  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                 |                 |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------|
+| <b>Testable items</b>    | ExMovAttr 2; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ExMovAttr 3; R  | ExMovAttr 4; M  |
+|                          | ExMovAttr 5; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ExMovAttr 6; M  | ExMovAttr 7; M  |
+|                          | ExMovAttr 8; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ExMovAttr 9; R  | ExMovAttr 10; R |
+|                          | ExMovAttr 11; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | ExMovAttr 12; R | ExMovAttr 15; M |
+| <b>Test purpose</b>      | Check that:<br>The Exercise Movement Enumeration object contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                 |                 |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_175 AND C_AG_ST_153                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                 |                 |
+| <b>Other PICS</b>        | C_AG_ST_156                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                 |                 |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                 |                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The PHD under test sends an AARQ message to the simulated PHG.</li> <li>2. The simulated PHG issues an AARE message with the result "accepted-unknown-config".</li> <li>3. The PHD under test sends its configuration to the simulated PHG.</li> <li>4. The Exercise Movement object shall be: <ol style="list-style-type: none"> <li>a. Mandatory Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (Sequence of partition (NomPartition (INT-U16)) and code (OID-Type)))</li> <li><input type="checkbox"/> attribute-value= MDC_PART_PHD_HF   MDC_HF_EXERCISE_MOVEMENT</li> </ol> </li> <li>b. Not Recommended attribute Supplemental-Types <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt;(Sequence of TYPE (TYPE.length= 4 bytes → partition NomPartition (INT-U16) and code (OID-Type)))</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• bit 0 (mss-avail-intermittent(0)) shall be set</li> <li>• bit 1 (mss-avail-stored-data(1)) shall be set</li> <li>• bit 2 (mss-updt-aperiodic(2)) shall be set</li> <li>• bit 3 (mss-msmt-aperiodic(3)) shall be set</li> <li>• bit 9 (mss-acc-agent-initiated(9)) shall be set</li> <li>• The other bits have to be 0.</li> </ol> </li> </ol> </li> <li>d. Not Recommended attribute Metric-Structure-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt; (Sequence of (ms-struct.length =1byte(INT-U8) + ms-comp-no = 1 byte(INT-U8))))</li> </ol> </li> <li>e. Mandatory attribute Source-Handle-Reference</li> </ol> </li> </ol> |                 |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = Handle of the Set object to which this object is associated</li> </ul> <p>f. Mandatory attribute Enum-Observed-Value-Simple-OID</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIMP_OID</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = MDC_HF_MOVEMENT_* (See Annex C of [b-ISO/IEEE 11073-10408])</li> </ul> <p>g. Not Recommended attribute Enum-Observed-Value-Simple-Bit-Str</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIMP_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>h. Not Recommended attribute Enum-Observed-Value-Basic-Bit-Str</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> <p>i. Not Recommended attribute Enum-Observed-Value-Simple-Str</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_STR</li> <li><input type="checkbox"/> attribute-type = EnumPrintableString</li> <li><input type="checkbox"/> attribute-value.length =</li> </ul> <p>j. Not Recommended attribute Enum-Observed-Value</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_VAL_ENUM_OBS</li> <li><input type="checkbox"/> attribute-type = EnumObsValue</li> <li><input type="checkbox"/> attribute-value.length =</li> </ul> <p>k. Not Recommended attribute Enum-Observed-Value-Partition</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                      |                                                                                                                                                                                    |                        |  |
+|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>         | TP/PLT/PHD/CLASS/ST/BV-020                                                                                                                                                         |                        |  |
+| <b>TP label</b>      | Exercise Movement Object and Set object attributes                                                                                                                                 |                        |  |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                        | [ISO/IEEE 11073-10442] |  |
+|                      | <b>Testable items</b>                                                                                                                                                              | ExMovAttr 14; M        |  |
+| <b>Test purpose</b>  | Check that:<br>The timestamp attribute used for an Exercise Movement object instance shall be the same as that which is used for the Set object instance to which it is associated |                        |  |
+| <b>Applicability</b> | C_AG_OXP_000 AND C_AG_OXP_175 AND C_AG_ST_153                                                                                                                                      |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICS</b>         | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The PHD under test sends an AARQ message to the simulated PHG.</li> <li>2. The simulated PHG issues an AARE message with the result "accepted-unknown-config".</li> <li>3. The PHD under test sends its configuration to the simulated PHG.</li> <li>4. IF C_AG_OXP_293: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ol> </li> <li>5. Record the handle and the Attribute-Value-Map of the Set object and the Exercise Movement that is associated to it.</li> <li>6. Take a measurement.</li> <li>7. Wait for the simulated PHG to receive it.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• In step 7 if the Exercise Movement measurement contains a timestamp it shall be the same (attribute and value) as that for the Set object.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                          |                                                                                                                     |                        |                     |                     |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------|------------------------|---------------------|---------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ST/BV-021                                                                                          |                        |                     |                     |
+| <b>TP label</b>          | Association Request                                                                                                 |                        |                     |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                         | [ISO/IEEE 11073-10442] |                     |                     |
+|                          | <b>Testable items</b>                                                                                               | StrenAssocReq 1; M     | StrenAssocReq 2; M  | StrenAssocReq 3; M  |
+|                          |                                                                                                                     | StrenAssocReq 4; M     | StrenAssocReq 5; M  | StrenAssocReq 6; M  |
+|                          |                                                                                                                     | StrenAssocReq 7; M     | StrenAssocReq 8; M  | StrenAssocReq 9; M  |
+|                          |                                                                                                                     | StrenAssocReq 10; O    | StrenAssocReq 11; M | StrenAssocReq 12; C |
+|                          |                                                                                                                     | StrenAssocReq 13; C    |                     |                     |
+| <b>Test purpose</b>      | Check that:<br>The association procedure data exchange is correct.                                                  |                        |                     |                     |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_175                                                                                       |                        |                     |                     |
+| <b>Other PICS</b>        | C_AG_OXP_017                                                                                                        |                        |                     |                     |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                             |                        |                     |                     |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The PHD under test sends an AARQ message to the simulated PHG.</li> </ol> |                        |                     |                     |
+
+#### 2. The expected fields 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-version = 0x80 0x00 0x00 0x00 (asassoc-version1(0) set) indicates that version 1 of the association protocol is supported.
+- c. 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 shall contain PhdAssociationInformation.
+- d. 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)
+- e. 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).
+- f. 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).
+- g. 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 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
+- h. System-Type
+  - field- type = SystemType
+  - field-length = BITS-32
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> field- value = 0x00 0x80 0x00 0x00 (sys-type-agent)</li> <li>i. System-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = OCTET STRING</li> <li><input type="checkbox"/> field-length = 0x00 0x0A</li> <li><input type="checkbox"/> field- value = &lt; Check with PIXITs &gt;</li> </ul> </li> <li>j. Dev-config-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = ConfigId</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field- value = &lt;between 0x40 0x00 and 0x7F 0xFF&gt;</li> </ul> </li> <li>k. Data-req-mode-flags (DataReqModeCapab) <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = DataReqModeFlags</li> <li><input type="checkbox"/> field-length = BITS-16</li> <li><input type="checkbox"/> If the PHD implements only this Device Specialization: field- value = 0x00 0x01 – Agent-initiated data request/flows</li> </ul> </li> <li>l. Data-req-init-agent-count (DataReqModeCapab) <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = INT-U8</li> <li><input type="checkbox"/> field-length = INT-U8</li> <li><input type="checkbox"/> If the PHD implements only this Device Specialization: field- value = 0x01</li> </ul> </li> <li>m. Data-req-init-manager-count (DataReqModeCapab) <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = INT-U8</li> <li><input type="checkbox"/> field-length = INT-U8</li> <li><input type="checkbox"/> If the PHD implements only this Device Specialization: field- value = 0x00</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|                          |                                                                                                                                                                                 |                        |  |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/ST/BV-022                                                                                                                                                      |                        |  |
+| <b>TP label</b>          | Config Changes Service. Resistance Contextual Attribute.                                                                                                                        |                        |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                     | [ISO/IEEE 11073-10442] |  |
+|                          | <b>Testable items</b>                                                                                                                                                           | NumObj 1; M            |  |
+|                          | <b>Spec</b>                                                                                                                                                                     | [b-ITU-T H.810 (2015)] |  |
+|                          | <b>Testable items</b>                                                                                                                                                           | Communication 8; M     |  |
+| <b>Test purpose</b>      | Check that:<br>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. |                        |  |
+| <b>Applicability</b>     | C_AG_OXP_000 AND C_AG_OXP_175 AND C_AG_ST_030 AND C_AG_ST_154                                                                                                                   |                        |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                 |                        |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                            |                        |  |
+| <b>Test procedure</b>    | 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.                                     |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ol style="list-style-type: none"> <li>2. Make a change to the contextual attribute Unit-Code for Resistance object (grams to pounds, pounds to grams, grams or pounds to DIMLESS, or DIMLESS to grams or pounds).</li> <li>3. The PHD shall send an MDS event report indicating the new contextual attribute value.</li> <li>4. Take some more measurements.</li> <li>5. Wait for the PHG to receive new event reports from the PHD, which report the measurements from step 4.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHD sends an MDS event report to inform about the contextual attribute that has been changed.</li> <li>• Data has changed accordingly to a new contextual attribute.</li> </ul>                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |  |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/ST/BV-023                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |  |
+| <b>TP label</b>           | Config Changes Service. Repetition Contextual Attribute.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [ISO/IEEE 11073-10442] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | NumObj 1; M            |  |
+|                           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [b-CDG 2010]           |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Communication 8; M     |  |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>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.</p>                                                                                                                                                                                                                                                                                                                                                                                                |                        |  |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_175 AND C_AG_ST_050 AND C_AG_ST_155                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>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.</li> <li>2. Make a change to the contextual attribute Unit-Code for Repetition object (meters to inches or inches to meters.)</li> <li>3. The PHD shall send an MDS event report indicating the new contextual attribute value.</li> <li>4. Take some more measurements.</li> <li>5. Wait for the PHG to receive new event reports from the PHD, which report the measurements from step 4.</li> </ol> |                        |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The PHD sends an MDS event report to inform about the contextual attribute that has been changed.</li> <li>• Data has changed accordingly to new contextual attribute.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                |                        |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |  |
+
+|                 |                                               |
+|-----------------|-----------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/ST/BV-024                    |
+| <b>TP label</b> | Operating State. PHG to PHD Maximum APDU Size |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--|--|
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | CommonCharac 3; M                                             |  |  |
+| <b>Test purpose</b>       | Check that:<br>The total size of the response do not exceed of the maximum APDU size established by the specialization                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                               |  |  |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_175                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                               |  |  |
+| <b>Other PICS</b>         | C_AG_OXP_041, C_AG_OXP_100                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                               |  |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                               |  |  |
+| <b>Test procedure</b>     | 1. The simulated PHG issues a "Remote Operation Invoke   Get" command with:<br>a. Obj-handle set to 0 (to request for MDS object)<br>b. attribute-id-list.count = 4087<br>c. 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<br>2. Check the response of the PHD.<br>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.<br>4. Check the response of the PHD.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                                               |  |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• 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 roj (resource-limitation) message, a WARNING will appear. <ul style="list-style-type: none"> <li>○ 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): <ul style="list-style-type: none"> <li>▪ Pulse oximeter → 9216 octets</li> <li>▪ Weighing scales → 896 octets</li> <li>▪ Glucose meter → 5120 octets or 64512 octets if the PHD supports PM-Store</li> <li>▪ Blood pressure → 896 octets</li> <li>▪ Thermometer → 896 octets</li> <li>▪ Independent activity hub → 5120 octets</li> <li>▪ Cardiovascular → 64512 octets or 6624 octets if the PHD under test only supports Step Counter Profile</li> <li>▪ Strength → 64512 octets:</li> <li>▪ Adherence monitor → 1024 octets</li> <li>▪ Peak flow → 2030 octets</li> <li>▪ Body composition analyser → 7730 octets</li> <li>▪ Basic ECG/Simple ECG → 7168 octets or 64512 octets if PHD supports PM-Store</li> <li>▪ Basic ECG/Heart rate → 1280 octets or 64512 octets if the PHD supports PM-Store</li> <li>▪ International normalized ratio → 896 octets or 64512 if the PHD supports PM-Store</li> </ul> </li> <li>○ In case it responds with a roer, the reason must not be protocol-violation (23)</li> </ul> </li> <li>• In step 4, the PHD must respond with a rors-cmip-get message.</li> </ul> |                                                               |  |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                                                               |  |  |
+
+## 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-ETSI 300 406] ETSI ETS 300 406, *Methods for Testing and Specifications (MTS); Protocol and profile conformance testing specifications; Standardization methodology*.
+- [b-ISO/IEC 9646-1] ISO/IEC 9646-1, *Information Technology – Open Systems Interconnection – Conformance testing methodology and framework – Part 1: General concepts*.
+- [b-ISO/IEC 9646-7] ISO/IEC 9646-7, *Information technology – Open Systems Interconnection – Conformance testing methodology and framework – Part 7: Implementation Conformance Statements*.
+- [b-ISO/IEEE 11073-10408] ISO/IEEE 11073-10408-2010, *Health informatics – Personal health device communication – Part 10408: Device specialization – Thermometer*.
+- [b-PHD PICS & PIXIT] Personal Health Device DG2016 PICS and PIXIT excel sheet v1.11.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-PHG PICS & PIXIT] Personal Health Gateway DG2016 PICS and PIXIT excel sheet v1.9.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-TCRL] Test Case Reference List\_DG2016\_v1.11.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-TI] Continua DG2016 PHD Testable items excel sheet v1.8.  
+<http://handle.itu.int/11.1002/2000/12067>
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.8-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg b/marked/H/T-REC-H.845.8-201704-I_PDF-E/e8ba5d4a3a22e24e44f7935ea26afcb0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ca0dce65df64f4fb10a81b8f87284f793e4b1d3d
--- /dev/null
+++ b/marked/H/T-REC-H.845.8-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.8-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.845.8-201704-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a811b704f72bf3b6c6ab28df0c2511350463351e
--- /dev/null
+++ b/marked/H/T-REC-H.845.8-201704-I_PDF-E/raw.md
@@ -0,0 +1,1444 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.845.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: Personal Health Devices interface  
+Part 5H: Independent living activity hub**
+
+Recommendation ITU-T H.845.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        |
+| <b>Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN)</b> | <b>H.820–H.859</b> |
+| 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.8
+
+## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5H: Independent living activity hub
+
+## Summary
+
+Recommendation ITU-T H.845.8 provides a test suite structure (TSS) and the test purposes (TP) for independent living activity hubs 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.8 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5H: Device Specializations. Personal Health Device (Activity Hub) (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.8  | 2015-01-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/12269">11.1002/1000/12269</a> |
+| 2.0     | ITU-T H.845.8  | 2016-07-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12945">11.1002/1000/12945</a> |
+| 3.0     | ITU-T H.845.8  | 2017-04-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/13226">11.1002/1000/13226</a> |
+
+## Keywords
+
+Conformance testing, Continua Design Guidelines, e-health, IEEE 11073 device specialization, independent living activity hub, ITU-T H.810, Personal Health Devices interface, personal area network, personal connected health devices, touch area network.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.8: Activity hub (HUB) .....   | 9    |
+| Bibliography.....                              | 56   |
+
+**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 5H: Device Specializations. Personal Health Device (Activity Hub) (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_3H_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_5H_v1.3.doc" as a baseline and adds new features included in [b-CDG 2012]: <ul style="list-style-type: none"> <li>• Max APDU size for GM, BCA and ECG</li> </ul>                                                                                                                         |
+| 1.5     | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_PAN-LAN_PART_5H_v1.4.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]: <ul style="list-style-type: none"> <li>• Adds glucose meter BLE</li> <li>• Adds BLE SSP support</li> <li>• Adds NFC new transport</li> <li>• Adds INR device specialization</li> </ul> |
+| 1.6     | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance Release 1). It uses "TSS&TP_DG2013_PLT_PART_5H_v1.5.doc" as a baseline and adds new features included in Documentation Enhancements: <ul style="list-style-type: none"> <li>• "Other PICS" row added</li> </ul>                                                                                               |
+| 1.6     | 2015-07-01 | Initial release for Test Tool DG2015. It is the same version as "TSS&TP_DG2013_PLT_PART_5H_v1.5.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.7     | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2015_PLT_PART_5H_v1.6.doc" as a baseline and it adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016]                                                                                                                                                                                              |
+
+## Recommendation ITU-T H.845.8
+
+## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5H: Independent living activity hub
+
+# 1 Scope
+
+The scope of this Recommendation<sup>1</sup> 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 5H.
+
+- 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
+
+---
+
+<sup>1</sup> 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-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-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.  
+<https://www.iso.org/standard/54331.html> with  
+<https://www.iso.org/standard/63972.html>
+- [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.  
+<https://www.iso.org/standard/66717.html> with  
+<https://www.iso.org/standard/71886.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        |
+| 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.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 <http://handle.itu.int/11.1002/2000/12067>.
+
+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>/<DUT>/<GR>/<SGR>/<XX> – <NNN>). It is specified according to the naming convention defined below:
+  - Each test purpose identifier is introduced by the prefix "TP".
+  - <TT>: 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)
+  - <DUT>: This is the device under test:
+    - PHD: Personal Health Device
+    - PHG: Personal Health Gateway
+  - <GR>: This identifies a group of test cases.
+  - <SGR>: This identifies a subgroup of test cases.
+  - <XX>: This identifies the type of testing:
+    - BV: Valid behaviour test
+    - BI: Invalid behaviour test
+  - <NNN>: 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.8: Activity hub (HUB)
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |               |               |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/HUB/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |               |               |
+| <b>TP label</b>          | Get MDS Object for Activity Hub specialization: Mandatory, Conditional and Optional Attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |               |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-10471] |               |               |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | MDSAttr 1; M           | MDSAttr 2; M  | MDSAttr 3; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | MDSAttr 4; M           | MDSAttr 5; O  | MDSAttr 6; O  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | MDSAttr 7; R           | MDSAttr 8; R  | MDSAttr 9; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | MDSAttr 10; M          | MDSAttr 11; M | MDSAttr 12; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | OperaProc1;M           |               |               |
+| <b>Test purpose</b>      | Check that:<br>The Personal Health Device (PHD) supports a Get command that requests all attributes<br>[AND]<br>The MDS Object contains the attributes specified for an independent living activity hub PHD.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |               |               |
+| <b>Applicability</b>     | C_AG_OXP_176 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |               |               |
+| <b>Other PICS</b>        | C_AG_HUB_034                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |               |               |
+| <b>Initial condition</b> | The simulated Personal Health Gateway (PHG) and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |               |               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHG issues a "roiv-cmip-get" command with the handle set to 0 (to request for an MDS object) and an attribute-id-list set to 0 to indicate all attributes.</li> <li>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:<br/> MDS Attributes: <ol style="list-style-type: none"> <li>Mandatory attribute System-model <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_MODEL</li> <li><input type="checkbox"/> attribute-type = SystemModel</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value ={Manufacturer, Model}</li> </ul> </li> <li>Mandatory attribute Dev-Configuration-Id <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_DEV_CONFIG_ID</li> <li><input type="checkbox"/> attribute-type = ConfigId</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;between 0x4000 and 0x7FFF&gt;</li> </ul> </li> <li>Mandatory attribute Date-and-Time</li> </ol> </li> </ol> |                        |               |               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_ABS</li> <li><input type="checkbox"/> attribute-type = AbsoluteTime</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> <p>d. Optional attribute Relative-Time</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_REL</li> <li><input type="checkbox"/> attribute-type = RelativeTime (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ul> <p>e. Optional attribute HiRes-Relative-Time</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_REL_HI_RES</li> <li><input type="checkbox"/> attribute-type = HighResRelativeTime</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> </ul> <p>f. Recommended attribute Power-Status</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_POWER_STAT</li> <li><input type="checkbox"/> attribute-type = PowerStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>IF C_AG_HUB_034= TRUE THEN attribute-value = ON_MAINS (0x8000) and the rest of the bits must not be set</li> <li>ELSE attribute-value = ON_BATTERY(0x4000) Only one of the following may be active: <ul style="list-style-type: none"> <li>• chargingFull(8),</li> <li>• chargingTrickle(9),</li> <li>• chargingOff(10).</li> <li>• The rest of the bits must not be set</li> </ul> </li> </ul> </li> </ul> <p>g. Recommended attribute Battery-Level</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_VAL_BATT_CHARGE</li> <li><input type="checkbox"/> attribute-type = INT-U16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;undefined if value &gt; 100 &gt;</li> </ul> <p>h. Recommended attribute Remaining-Battery-Time</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_BATT_REMAIN</li> <li><input type="checkbox"/> attribute-type = BatMeasure</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value = &lt;units shall be set to one of: MDC_DIM_MIN, MDC_DIM_HR, MDC_DIM_DAY &gt;</li> </ul> <p>i. Mandatory attribute System-Type-Spec_List</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SYS_TYPE_SPEC_LIST</li> <li><input type="checkbox"/> attribute-type = TypeVerList</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes attribute-value = MDC_DEV_SPEC_PROFILE_AI_ACTIVITY_HUB, 1</li> <li><input type="checkbox"/> Attribute System-Type must not be present.</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |  |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/HUB/BV-000_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |  |  |
+| <b>TP label</b>           | Extended Configurations                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |  |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-10471] |  |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | DIM 2; M               |  |  |
+| <b>Test purpose</b>       | Check that:<br>All configurations shall be specified as extended configurations.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |  |  |
+| <b>Applicability</b>      | C_AG_OXP_176 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |  |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |  |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |  |  |
+| <b>Test procedure</b>     | 1. The PHD under test sends an Association Request to the simulated PHG. The expected fields sent by the PHD are: <ul style="list-style-type: none"> <li>a. dev-config-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = ConfigId</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field- value = &lt;between 0x4000 and 0x7FFF&gt;</li> </ul> </li> <li>b. Data-Req-Mode-Capab: <ul style="list-style-type: none"> <li><input type="checkbox"/> field-length = 4 bytes</li> <li><input type="checkbox"/> field- value = 0xXX 0xXX 0x01 0xXX (Agent-initiated)</li> </ul> </li> </ul> 2. The simulated PHG responses with an accepted-unknown-config.<br>3. The PHD sends a configuration event report, with the following fields: dev-config-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field-type = ConfigId</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field- value = &lt;between 0x4000 and 0x7FFF&gt;</li> </ul> 4. The simulated PHG responds with an unsupported-configuration.<br>5. The PHD sends a new configuration event report with a new configuration (if it has more).<br>6. Repeat the last two steps checking all the ConfigId-values until the PHD sends a ReleaseRequest with the reason "no-more-configurations". |                        |  |  |
+| <b>Pass/Fail criteria</b> | All Dev-config-id values are between 0x4000 and 0x7FFF.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |  |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |  |  |
+
+|                     |                                                                                                                                                                                                 |                        |  |  |
+|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|--|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/HUB/BV-001                                                                                                                                                                     |                        |  |  |
+| <b>TP label</b>     | RTC, Set time command and internal clock for Activity Hub                                                                                                                                       |                        |  |  |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                     | [ISO/IEEE 11073-10471] |  |  |
+|                     | <b>Testable items</b>                                                                                                                                                                           | MDSMethod 3; M         |  |  |
+| <b>Test purpose</b> | Check that:<br>For PHDs that contain internal clocks, if the PHD is wall powered or has access to a constant non-diminishing supply of power then this support (Set-Time) shall be implemented. |                        |  |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Applicability</b>      | C_AG_OXP_176 AND C_AG_OXP_006 AND C_AG_HUB_034 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Configuring state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>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.</li> <li>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: <ol style="list-style-type: none"> <li>a. IF Recommended attribute Power-Status is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_POWER_STAT</li> <li><input type="checkbox"/> attribute-type = PowerStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = ON_MAINS (0x8000)</li> </ul> </li> <li>b. Mandatory attribute Mds-Time-Info <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MDS_TIME_INFO</li> <li><input type="checkbox"/> attribute-type = MdsTimeInfo</li> <li><input type="checkbox"/> attribute-value.length =</li> <li><input type="checkbox"/> Sequence of: <ul style="list-style-type: none"> <li>▪ Mds-time-cap-state <ul style="list-style-type: none"> <li>– field-type = MdsTimeCapState</li> <li>– field-length = 2 bytes</li> <li>– field-value = Bit 0 (mds-time-capab-real-time-clock) and Bit 1 (mds-time-capab-set-clock) must be set</li> </ul> </li> <li>▪ Time-sync-protocol <ul style="list-style-type: none"> <li>– field-type = TimeProtocolId</li> <li>– field-length = OID-Type(INT-U16)</li> </ul> </li> </ul> </li> </ul> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                          |                                                                                                                                                                |                        |              |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/HUB/BV-002                                                                                                                                    |                        |              |
+| <b>TP label</b>          | MDS Configuration objects events for Activity Hub                                                                                                              |                        |              |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                    | [ISO/IEEE 11073-10471] |              |
+|                          | <b>Testable items</b>                                                                                                                                          | MDSEvent 1; M          | ConfProc1; M |
+| <b>Test purpose</b>      | Check that:<br>An independent living activity hub sends the MDS-Configuration-Event using a Confirmed event report and it includes the event-info ConfigReport |                        |              |
+| <b>Applicability</b>     | C_AG_OXP_176 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                 |                        |              |
+| <b>Other PICS</b>        | C_AG_OXP_010                                                                                                                                                   |                        |              |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Configuring state.                                                                                         |                        |              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> </ol>                                |                        |              |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>2. The simulated PHG responds with a result = accepted-unknown-config.</p> <p>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:</p> <ul style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = PrstApdu</li> <li><input type="checkbox"/> field-length =2 bytes</li> <li><input type="checkbox"/> field-value =0xE7 0x00</li> </ul> </li> <li>b. invoke-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = InvokeIDType</li> <li><input type="checkbox"/> field-length =INT-U16</li> <li><input type="checkbox"/> field- value=&lt;Not relevant for this test&gt;</li> </ul> </li> <li>c. message <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = roiv-cmip-confirmed-event-report</li> <li><input type="checkbox"/> field-length =two bytes</li> <li><input type="checkbox"/> field- value= 0x01 0x01 (EventReportArgumentSimple)</li> </ul> </li> <li>d. obj-handle (EventReportArgumentSimple) <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = HANDLE</li> <li><input type="checkbox"/> field-length =INT-U16</li> </ul> </li> <li>e. event-time (EventReportArgumentSimple) <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = Relative Time</li> <li><input type="checkbox"/> field-length =INT-U32</li> <li><input type="checkbox"/> field-value = <ul style="list-style-type: none"> <li>• IF NOT C_AG_OXP_010 THEN value = 0xFF 0xFF 0xFF 0xFF</li> </ul> </li> </ul> </li> <li>f. event-type (EventReportArgumentSimple) <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = OID-Type</li> <li><input type="checkbox"/> field-length =INT-U16</li> <li><input type="checkbox"/> field- value=0x 0D 0x 1C (MDC_NOTI_CONFIG)</li> </ul> </li> <li>g. config-report-id (ConfigReport) <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = ConfigId</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field- value = &lt;Between 0x40 0x00 and 0x7F 0xFF&gt;</li> </ul> </li> <li>h. obj-class ( ConfigReport → ConfigObjectList (ConfigObject)) <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = OID-Type</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field- value = One or more of MDC_MOC_VMO_METRIC_ENUM must appear</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                 |                                 |                        |               |
+|-----------------|---------------------------------|------------------------|---------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/HUB/BV-003     |                        |               |
+| <b>TP label</b> | MDS objects events Activity Hub |                        |               |
+| <b>Coverage</b> | <b>Spec</b>                     | [ISO/IEEE 11073-10471] |               |
+|                 | <b>Testable</b>                 | MDSEvent 3; M          | MDSEvent 4; M |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |               |                  |                  |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|------------------|------------------|
+|                           | <b>items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | MDSEvent 6; M | ServiceModel1; M | ServiceModel2; M |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | OperaProc4; M |                  |                  |
+| <b>Test purpose</b>       | Check that:<br>Agent-initiated mode is supported for measurement data transmission and all types of event reports are used in confirmed mode<br>[AND]<br>The PHD sends the MDS-Dynamic-Data-Update-Fixed using a confirmed event report and it includes the event-info ScanReportInfoFixed<br>[OR]<br>The PHD sends the MDS-Dynamic-Data-Update-Var using a confirmed event report and it includes the event-info ScanReportInfoVar<br>[OR]<br>The PHD sends the MDS-Dynamic-Data-Update-MP-Fixed using a confirmed event report and it includes the event-info ScanReportInfoMPFixed<br>[OR]<br>The PHD sends the MDS-Dynamic-Data-Update-MP-Var using a confirmed event report and it includes the event-info ScanReportInfoMPVar |               |                  |                  |
+| <b>Applicability</b>      | C_AG_OXP_176 AND C_AG_OXP_181 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)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |               |                  |                  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |               |                  |                  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |               |                  |                  |
+| <b>Test procedure</b>     | 1. Take measurements for every supported object in the PHD under test.<br>2. Wait to receive every event report and check:<br>a. message<br><input type="checkbox"/> field- type = Event Report<br><input type="checkbox"/> field-length = 2 bytes<br><input type="checkbox"/> 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.                                                                                                                                                                                                                                                   |               |                  |                  |
+| <b>Pass/Fail criteria</b> | Check that every received report is one of the following Data APDU and that it is confirmed:<br><ul style="list-style-type: none"> <li>• MDC_NOTI_SCAN_REPORT_FIXED</li> <li>• MDC_NOTI_SCAN_REPORT_MP_FIXED</li> <li>• MDC_NOTI_SCAN_REPORT_VAR</li> <li>• MDC_NOTI_SCAN_REPORT_MP_VAR</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                  |               |                  |                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |               |                  |                  |
+
+|                 |                                                                  |                        |              |              |
+|-----------------|------------------------------------------------------------------|------------------------|--------------|--------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/HUB/BV-005                                      |                        |              |              |
+| <b>TP label</b> | Get activity data Enumeration Object attributes for Activity Hub |                        |              |              |
+| <b>Coverage</b> | <b>Spec</b>                                                      | [ISO/IEEE 11073-10471] |              |              |
+|                 | <b>Testable items</b>                                            | EnumObj 2; M           | EnumObj 3; M | EnumObj 4; M |
+|                 |                                                                  | EnumObj 5; R           | EnumObj 6; R | EnumObj 7; R |
+
+|                          |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |               |               |
+|--------------------------|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|
+|                          |  | EnumObj 8; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | EnumObj 9; R  | EnumObj 10; R |
+|                          |  | EnumObj 11; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | EnumObj 12; R | EnumObj 13; O |
+|                          |  | EnumObj 14; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | EnumObj 15; R | EnumObj 16; R |
+|                          |  | EnumObj 17; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | EnumObj 18; R | EnumObj 19; R |
+|                          |  | EnumObj 20; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | EnumObj 21; R | EnumObj 22; M |
+|                          |  | EnumObj 23; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |               |               |
+| <b>Test purpose</b>      |  | Check that:<br>Extended enumeration object (that is added by the vendor) contains the attributes specified for Extended Configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |               |               |
+| <b>Applicability</b>     |  | C_AG_OXP_176 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |               |               |
+| <b>Other PICS</b>        |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |               |               |
+| <b>Initial condition</b> |  | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |               |               |
+| <b>Test procedure</b>    |  | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. All Enumeration objects must have: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_AIfollowed by one of the next: <ul style="list-style-type: none"> <li>▪ MDC_AI_TYPE_SENSOR_FALL</li> <li>▪ MDC_AI_TYPE_SENSOR_PERS</li> <li>▪ MDC_AI_TYPE_SENSOR_SMOKE</li> <li>▪ MDC_AI_TYPE_SENSOR_CO</li> <li>▪ MDC_AI_TYPE_SENSOR_WATER</li> <li>▪ MDC_AI_TYPE_SENSOR_GAS</li> <li>▪ MDC_AI_TYPE_SENSOR_MOTION</li> <li>▪ MDC_AI_TYPE_SENSOR_PROPEXIT</li> <li>▪ MDC_AI_TYPE_SENSOR_ENURESIS</li> <li>▪ MDC_AI_TYPE_SENSOR_CONTACTCLOSURE</li> <li>▪ MDC_AI_TYPE_SENSOR_USAGE</li> <li>▪ MDC_AI_TYPE_SENSOR_SWITCH</li> <li>▪ MDC_AI_TYPE_SENSOR_DOSAGE</li> <li>▪ MDC_AI_TYPE_SENSOR_TEMP</li> </ul> </li> </ol> </li> <li>b. Mandatory attribute Supplemental-Types <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length =Sequence of TYPE (TYPE.length= 4 bytes → partition NomPartition (INT-U16) and code (OID-Type))</li> <li><input type="checkbox"/> attribute-value=</li> </ol> </li> </ol> </li> </ol> |               |               |
+
+- TYPE.partition= 0x00 0x82 (NOM\_PART\_PHD\_AI, dec. value 130)
+- TYPE.code= Upper 10 bits are one of MDC\_AI\_LOCATION and the lower bits represent the unique instance of the location. This value denotes sensor location.
+  - MDC\_AI\_LOCATION\_START 1024
+  - MDC\_AI\_LOCATION\_UNKNOWN 1024
+  - MDC\_AI\_LOCATION\_UNSPECIFIED 1088
+  - MDC\_AI\_LOCATION\_RESIDENT 1152
+  - MDC\_AI\_LOCATION\_LOCALUNIT 1216
+  - MDC\_AI\_LOCATION\_BEDROOM 3072
+  - MDC\_AI\_LOCATION\_BEDROOMMASTER 3136
+  - MDC\_AI\_LOCATION\_TOILET 3200
+  - MDC\_AI\_LOCATION\_TOILETMAIN 3264
+  - MDC\_AI\_LOCATION\_OUTSIDETOILET 3328
+  - MDC\_AI\_LOCATION\_SHOWERROOM 3392
+  - MDC\_AI\_LOCATION\_KITCHEN 3456
+  - MDC\_AI\_LOCATION\_KITCHENMAIN 3520
+  - MDC\_AI\_LOCATION\_LIVINGAREA 3584
+  - MDC\_AI\_LOCATION\_LIVINGROOM 3648
+  - MDC\_AI\_LOCATION\_DININGROOM 3712
+  - MDC\_AI\_LOCATION\_STUDY 3776
+  - MDC\_AI\_LOCATION\_HALL 3840
+  - MDC\_AI\_LOCATION\_LANDING 3904
+  - MDC\_AI\_LOCATION\_STAIRS 3968
+  - MDC\_AI\_LOCATION\_HALLLANDINGSTAIRS 4032
+  - MDC\_AI\_LOCATION\_GARAGE 4096
+  - MDC\_AI\_LOCATION\_GARDENGARAGE 4160
+  - MDC\_AI\_LOCATION\_GARDENGARAGEAREA 4224
+  - MDC\_AI\_LOCATION\_FRONTGARDEN 4288
+  - MDC\_AI\_LOCATION\_BACKGARDEN 4352
+  - MDC\_AI\_LOCATION\_SHED 4416
+  - MDC\_AI\_APPLIANCE\_KETTLE 7168
+  - MDC\_AI\_APPLIANCE\_TELEVISION 7232
+  - MDC\_AI\_APPLIANCE\_STOVE 7296
+  - MDC\_AI\_APPLIANCE\_MICROWAVE 7360
+  - MDC\_AI\_APPLIANCE\_TOASTER 7424
+  - MDC\_AI\_APPLIANCE\_VACUUM 7488
+  - MDC\_AI\_APPLIANCE\_APPLIANCE 7552
+  - MDC\_AI\_APPLIANCE\_FAUCET 7616
+  - MDC\_AI\_LOCATION\_FRONTDOOR 9216
+  - MDC\_AI\_LOCATION\_BACKDOOR 9280
+  - MDC\_AI\_LOCATION\_FRIDGEDOOR 9344
+  - MDC\_AI\_LOCATION\_MEDCABDOOR 9408
+  - MDC\_AI\_LOCATION\_WARDROBEDOOR 9472
+
+- MDC\_AI\_LOCATION\_FRONT CUPBOARD DOOR 9536
+- MDC\_AI\_LOCATION\_OTHER DOOR 9600
+- MDC\_AI\_LOCATION\_BED 11264
+- MDC\_AI\_LOCATION\_CHAIR 11328
+- MDC\_AI\_LOCATION\_SOFA 11392
+- MDC\_AI\_LOCATION\_TOILET\_SEAT 11456
+- MDC\_AI\_LOCATION\_STOOL 11520
+
+#### c. Mandatory attribute Metric-Spec-Small
+
+- attribute-id = MDC\_ATTR\_METRIC\_SPEC\_SMALL
+- attribute-type = MetricSpecSmall (BITS-16)
+- attribute-value  $\neq$  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)) is set.
+  - bit 9 (mss-acc-agent-initiated(9)) is set.
+
+#### d. Not recommended attribute Metric-Structure-Small
+
+- attribute-id = MDC\_ATTR\_METRIC\_STRUCTURE\_SMALL
+- attribute-type = MetricStructureSmall
+- attribute-value.length = Sequence of (ms-struct.length = 1byte(INT-U8) + ms-comp-no = 1byte(INT-U8))
+
+#### e. Not recommended attribute Measurement-Status
+
+- attribute-id = MDC\_ATTR\_MSMT\_STAT
+- attribute-type = MeasurementStatus (BITS-16)
+- attribute-value.length = 2 bytes
+
+#### f. Only one attribute of Metric-Id and Metric-Id-List shall be present.
+
+#### g. Not recommended attribute Metric-Id
+
+- attribute-id = MDC\_ATTR\_ID\_PHYSIO
+- attribute-type = OID-Type (INT-U16)
+- attribute-value.length = 2 bytes
+- attribute-value = Only one attribute of Metric-Id and Metric-Id-List shall be present.
+
+#### h. Not Recommended attribute Metric-Id-List
+
+- attribute-id = MDC\_ATTR\_ID\_PHYSIO\_LIS
+- attribute-type = MetricIdList
+- attribute-value.length = <variable> (SEQUENCE OF OID-Type (INT-U16))
+- 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. Not recommended attribute Metric-Id-Partition
+
+- attribute-id = MDC\_ATTR\_METRIC\_ID\_PART
+- attribute-type = NomPartition (INT-U16)
+- attribute-value.length = 2 bytes
+
+#### j. Not recommended attribute Unit-Code
+
+- attribute-id = MDC\_ATTR\_UNIT\_CODE
+
+- attribute-type = OID-Type (INT-U16)
+- attribute-value.length = 2 bytes
+- k. Not recommended attribute Source-Handle-Reference
+  - attribute-id = MDC\_ATTR\_SOURCE\_HANDLE\_REF
+  - attribute-type = HANDLE (INT-U16)
+  - attribute-value.length = 2 bytes
+- l. Recommended attribute Absolute-Time-Stamp
+  - attribute-id = MDC\_ATTR\_TIME\_STAMP\_ABS
+  - attribute-type = AbsoluteTime
+  - attribute-value.length = 8 bytes
+- m. Optional attribute Relative-Time
+  - attribute-id = MDC\_ATTR\_TIME\_REL
+  - attribute-type = RelativeTime (INT-U32)
+  - attribute-value.length = 4 bytes
+- n. Optional attribute HiRes-Relative-Time
+  - attribute-id = MDC\_ATTR\_TIME\_REL\_HI\_RES
+  - attribute-type = HighResRelativeTime
+  - attribute-value.length = 8 bytes
+- o. 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
+- p. 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
+- q. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str
+  - attribute-id = MDC\_ATTR\_ENUM\_OBS\_VAL\_SIM\_BIT\_STR
+  - attribute-type = BITS-32
+  - attribute-value.length = 4 bytes
+- r. Not recommended attribute Enum-Observed-Value-Basic-Bit-Str
+  - attribute-id = MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR
+  - attribute-type = BITS-16
+  - attribute-value.length = 2 bytes
+- s. Not recommended attribute Enum-Observed-Value-Simple-Str
+  - attribute-id = MDC\_ATTR\_ENUM\_OBS\_VAL\_SIM\_STR
+  - attribute-type = EnumPrintableString
+  - attribute-value.length = <variable>
+- t. Not recommended attribute Enum-Observed-Value
+  - attribute-id = MDC\_ATTR\_VAL\_ENUM\_OBS
+  - attribute-type = EnumObsValue
+  - attribute-value.length = <variable>
+- u. Not recommended attribute Enum-Observed-Value-Partition
+  - attribute-id = MDC\_ATTR\_ENUM\_OBS\_VAL\_PART
+
+|                           |                                                                                                                             |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> attribute-type = NomPartition (INT-U16)<br><input type="checkbox"/> attribute-value-length=2 bytes |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                  |
+| <b>Notes</b>              |                                                                                                                             |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/HUB/BV-005_A                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |  |
+| <b>TP label</b>           | Get activity data Enumeration Objects for Activity Hub                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-10471] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EnumObj 1; M           |  |
+| <b>Test purpose</b>       | Check that:<br>The independent living activity hub requires one activity data object for each supported sensor instance                                                                                                                                                                                                                                                                                                                                                    |                        |  |
+| <b>Applicability</b>      | C_AG_OXP_176 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |  |
+| <b>Other PICS</b>         | C_AG_HUB_021, C_AG_HUB_022, C_AG_HUB_023, C_AG_HUB_024, C_AG_HUB_025, C_AG_HUB_026, C_AG_HUB_027, C_AG_HUB_028, C_AG_HUB_029, C_AG_HUB_030, C_AG_HUB_031                                                                                                                                                                                                                                                                                                                   |                        |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                    |                        |  |
+| <b>Test procedure</b>     | 1. Record for later comparison the number of sensors of every type.<br>2. The simulated PHG receives an association request from the PHD under test.<br>3. The simulated PHG responds with a result = accepted-unknown-config.<br>4. 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.<br>5. Check that for every sensor there is one object of the appropriate type. |                        |  |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |  |
+
+|                 |                                                             |                        |               |
+|-----------------|-------------------------------------------------------------|------------------------|---------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/HUB/BV-005_B                               |                        |               |
+| <b>TP label</b> | Get activity data fall sensor Enumeration Object attributes |                        |               |
+| <b>Coverage</b> | <b>Spec</b>                                                 | [ISO/IEEE 11073-10471] |               |
+|                 | <b>Testable items</b>                                       | EnumObj 2; M           | EnumObj 3; M  |
+|                 |                                                             | EnumObj 5; R           | EnumObj 6; R  |
+|                 |                                                             | EnumObj 8; R           | EnumObj 9; R  |
+|                 |                                                             | EnumObj 11; R          | EnumObj 13; O |
+|                 |                                                             | EnumObj 15; R          | EnumObj 16; R |
+|                 |                                                             | EnumObj 18; R          | EnumObj 19; R |
+|                 |                                                             | EnumObj 21; R          | EnumObj 22; M |
+|                 |                                                             |                        | EnumObj 4; M  |
+|                 |                                                             |                        | EnumObj 7; R  |
+|                 |                                                             |                        | EnumObj 10; R |
+|                 |                                                             |                        | EnumObj 14; O |
+|                 |                                                             |                        | EnumObj 17; M |
+|                 |                                                             |                        | EnumObj 20; R |
+|                 |                                                             |                        | EnumObj 23; O |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                 |                 |                 |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------|-----------------|
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | FallSensor 1; M | FallSensor 2; O | FallSensor 3; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | FallSensor 4; M | FallSensor 5; M | FallSensor X; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Activity data enumeration object- Fall sensor contains the attributes specified for Extended Configuration.</p> <p>[AND]</p> <p>A fall detected sensor event is sent whenever a fall has occurred.</p> <p>[AND]</p> <p>If PHD can determine no condition detected event, then a no condition detected sensor event may be sent if this situation occurs.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                 |                 |                 |
+| <b>Applicability</b>     | C_AG_OXP_176 AND C_AG_HUB_021 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                 |                 |                 |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                 |                 |                 |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Configuring state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                 |                 |                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. The Data fall sensor object must be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_AI_TYPE_SENSOR_FALL</li> </ol> </li> <li>b. Mandatory attribute Absolute-Time-Stamp <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_ABS</li> <li><input type="checkbox"/> attribute-type = AbsoluteTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ol> </li> </ol> </li> <li>5. IF C_AG_OXP_293: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ol style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ol> </li> </ol> </li> <li>6. Simulate a fall in each fall sensor with the PHD under test.</li> <li>7. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> </ol> </li> </ol> </li> </ol> |                 |                 |                 |
+
+|                           |                                                                                                                                |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> attribute-value: <ul style="list-style-type: none"> <li>▪ fall-detected(0) bit must be set</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                     |
+| <b>Notes</b>              |                                                                                                                                |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                 |                |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|----------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/HUB/BV-005_C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                 |                |
+| <b>TP label</b>          | Get activity data PERS sensor Enumeration Object attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                 |                |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-10471] |                 |                |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | EnumObj 2; M           | EnumObj 3; M    | EnumObj 4; M   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | EnumObj 5; R           | EnumObj 6; R    | EnumObj 7; R   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | EnumObj 8; R           | EnumObj 9; R    | EnumObj 10; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | EnumObj 11; R          | EnumObj 13; O   | EnumObj 14; O  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | EnumObj 15; R          | EnumObj 16; R   | EnumObj 17; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | EnumObj 18; R          | EnumObj 19; R   | EnumObj 20; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | EnumObj 21; R          | EnumObj 22; M   | EnumObj 23; O  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | PERSSensor 1; M        | PERSSensor 2; O | PERSSensor3; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | PERSSensor4; M         | PERSSensor5; M  | PERSSensorX; M |
+| <b>Test purpose</b>      | Check that:<br>Activity data enumeration object PERS sensor contains the attributes specified for Extended Configuration.<br>[AND]<br>A button-activated sensor PERS sensor event is sent whenever the button is pressed.<br>[AND]<br>If PHD can determine no condition detected event, then a no condition detected sensor event may be sent when button is released.                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                 |                |
+| <b>Applicability</b>     | C_AG_OXP_176 AND C_AG_HUB_022 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                 |                |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                 |                |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Configuring state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                 |                |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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:</li> <li>4. The Data PERS sensor object must be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_AI_TYPE_SENSOR_PERS</li> </ul> </li> <li>b. Mandatory attribute Absolute-Time-Stamp</li> </ol> </li> </ol> |                        |                 |                |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_ABS</li> <li><input type="checkbox"/> attribute-type = AbsoluteTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> <p>5. IF C_AG_OXP_293:</p> <ul style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ul> <p>6. Simulate an emergency with the PHD under test.</p> <p>7. Wait for the simulated PHG to receive the event report:</p> <ul style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value= <ul style="list-style-type: none"> <li>▪ bit 0 (pers-activated(0)) must be set.</li> </ul> </li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|                     |                                                                                                            |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |  |              |              |              |              |              |              |              |              |               |               |               |               |               |               |               |               |               |               |               |               |               |                    |                    |                    |                    |                    |
+|---------------------|------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|--------------------|--------------------|--------------------|--------------------|--------------------|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/HUB/BV-005_D                                                                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |  |              |              |              |              |              |              |              |              |               |               |               |               |               |               |               |               |               |               |               |               |               |                    |                    |                    |                    |                    |
+| <b>TP label</b>     | Get activity data environmental sensor Enumeration Object attributes for Activity Hub                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |  |              |              |              |              |              |              |              |              |               |               |               |               |               |               |               |               |               |               |               |               |               |                    |                    |                    |                    |                    |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                | [ISO/IEEE 11073-10471]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |  |              |              |              |              |              |              |              |              |               |               |               |               |               |               |               |               |               |               |               |               |               |                    |                    |                    |                    |                    |
+|                     | <b>Testable items</b>                                                                                      | <table border="1" style="width: 100%;"> <tr> <td>EnumObj 2; M</td> <td>EnumObj 3; M</td> <td>EnumObj 4; M</td> </tr> <tr> <td>EnumObj 5; R</td> <td>EnumObj 6; R</td> <td>EnumObj 7; R</td> </tr> <tr> <td>EnumObj 8; R</td> <td>EnumObj 9; R</td> <td>EnumObj 10; R</td> </tr> <tr> <td>EnumObj 11; R</td> <td>EnumObj 13; O</td> <td>EnumObj 14; O</td> </tr> <tr> <td>EnumObj 15; R</td> <td>EnumObj 16; R</td> <td>EnumObj 17; M</td> </tr> <tr> <td>EnumObj 18; R</td> <td>EnumObj 19; R</td> <td>EnumObj 20; R</td> </tr> <tr> <td>EnumObj 21; R</td> <td>EnumObj 22; M</td> <td>EnumObj 23; O</td> </tr> <tr> <td>EnvironSensor 1; M</td> <td>EnvironSensor 2; O</td> <td>EnvironSensor 3; M</td> </tr> <tr> <td>EnvironSensor 4; M</td> <td>EnvironSensor 5; M</td> <td>EnvironSensor X; M</td> </tr> </table> |  | EnumObj 2; M | EnumObj 3; M | EnumObj 4; M | EnumObj 5; R | EnumObj 6; R | EnumObj 7; R | EnumObj 8; R | EnumObj 9; R | EnumObj 10; R | EnumObj 11; R | EnumObj 13; O | EnumObj 14; O | EnumObj 15; R | EnumObj 16; R | EnumObj 17; M | EnumObj 18; R | EnumObj 19; R | EnumObj 20; R | EnumObj 21; R | EnumObj 22; M | EnumObj 23; O | EnvironSensor 1; M | EnvironSensor 2; O | EnvironSensor 3; M | EnvironSensor 4; M | EnvironSensor 5; M |
+| EnumObj 2; M        | EnumObj 3; M                                                                                               | EnumObj 4; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |  |              |              |              |              |              |              |              |              |               |               |               |               |               |               |               |               |               |               |               |               |               |                    |                    |                    |                    |                    |
+| EnumObj 5; R        | EnumObj 6; R                                                                                               | EnumObj 7; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |  |              |              |              |              |              |              |              |              |               |               |               |               |               |               |               |               |               |               |               |               |               |                    |                    |                    |                    |                    |
+| EnumObj 8; R        | EnumObj 9; R                                                                                               | EnumObj 10; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |  |              |              |              |              |              |              |              |              |               |               |               |               |               |               |               |               |               |               |               |               |               |                    |                    |                    |                    |                    |
+| EnumObj 11; R       | EnumObj 13; O                                                                                              | EnumObj 14; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |  |              |              |              |              |              |              |              |              |               |               |               |               |               |               |               |               |               |               |               |               |               |                    |                    |                    |                    |                    |
+| EnumObj 15; R       | EnumObj 16; R                                                                                              | EnumObj 17; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |  |              |              |              |              |              |              |              |              |               |               |               |               |               |               |               |               |               |               |               |               |               |                    |                    |                    |                    |                    |
+| EnumObj 18; R       | EnumObj 19; R                                                                                              | EnumObj 20; R                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |  |              |              |              |              |              |              |              |              |               |               |               |               |               |               |               |               |               |               |               |               |               |                    |                    |                    |                    |                    |
+| EnumObj 21; R       | EnumObj 22; M                                                                                              | EnumObj 23; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |  |              |              |              |              |              |              |              |              |               |               |               |               |               |               |               |               |               |               |               |               |               |                    |                    |                    |                    |                    |
+| EnvironSensor 1; M  | EnvironSensor 2; O                                                                                         | EnvironSensor 3; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |  |              |              |              |              |              |              |              |              |               |               |               |               |               |               |               |               |               |               |               |               |               |                    |                    |                    |                    |                    |
+| EnvironSensor 4; M  | EnvironSensor 5; M                                                                                         | EnvironSensor X; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |  |              |              |              |              |              |              |              |              |               |               |               |               |               |               |               |               |               |               |               |               |               |                    |                    |                    |                    |                    |
+| <b>Test purpose</b> | Check that:<br>Activity data enumeration object environmental sensor contains the attributes specified for |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |  |              |              |              |              |              |              |              |              |               |               |               |               |               |               |               |               |               |               |               |               |               |                    |                    |                    |                    |                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>Extended Configuration.</p> <p>[AND]</p> <p>A condition detected event is sent whenever a sensor determines the condition has occurred.</p> <p>[AND]</p> <p>If PHD can determine no condition detected event, then a no condition detected sensor event may be sent if this situation occurs.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Applicability</b>      | C_AG_OXP_176 AND C_AG_HUB_023 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Other PICS</b>         | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Configuring state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. The Data environmental sensor object must be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_AI_TYPE_SENSOR_SMOKE or MDC_AI_TYPE_SENSOR_CO or MDC_AI_TYPE_SENSOR_WATER or MDC_AI_TYPE_SENSOR_GAS</li> </ol> </li> <li>b. Mandatory attribute Absolute-Time-Stamp <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_ABS</li> <li><input type="checkbox"/> attribute-type = AbsoluteTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ol> </li> </ol> </li> <li>5. IF C_AG_OXP_293: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ol style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ol> </li> </ol> </li> <li>6. Simulate an environmental change with the PHD under test.</li> <li>7. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>▪ bit 0 (condition-detected(0)) must be set</li> </ul> </li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|              |  |
+|--------------|--|
+| <b>Notes</b> |  |
+|--------------|--|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |                   |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/HUB/BV-005_E                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                   |
+| <b>TP label</b>          | Get activity data motion sensor Enumeration Object attributes for Activity Hub                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                   |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-10471] |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | EnumObj 2; M           | EnumObj 3; M      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | EnumObj 5; R           | EnumObj 6; R      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | EnumObj 8; R           | EnumObj 9; R      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | EnumObj 11; R          | EnumObj 13; O     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | EnumObj 15; R          | EnumObj 16; R     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | EnumObj 18; R          | EnumObj 19; R     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | EnumObj 21; R          | EnumObj 22; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | MotionSensor 1; M      | MotionSensor 2; O |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | MotionSensor4; M       | MotionSensor5; M  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Activity data enumeration object motion sensor contains the attributes specified for Extended Configuration.</p> <p>[AND]</p> <p>A motion detected event is sent whenever a sensor determines the motion has occurred.</p> <p>[AND]</p> <p>If PHD can determine no condition detected event, motion detected delayed or tamper detected, then a motion detected delayed, tamper detected, or no condition detected sensor events may be sent if the sensor can determine such a status and any of these situations occurs.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                   |
+| <b>Applicability</b>     | C_AG_OXP_176 AND C_AG_HUB_024 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |                   |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                   |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Configuring state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |                   |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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:</li> <li>4. The Data motion sensor object must be:           <ol style="list-style-type: none"> <li>a. Mandatory attribute Type               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_AI_TYPE_SENSOR_MOTION</li> </ul> </li> <li>b. Mandatory attribute Absolute-Time-Stamp               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_ABS</li> <li><input type="checkbox"/> attribute-type = AbsoluteTime</li> </ul> </li> </ol> </li> </ol> |                        |                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p><input type="checkbox"/> attribute-value.length = 8 bytes</p> <p>5. IF C_AG_OXP_293:</p> <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>IF the mds-time-mgr-set-time bit is set:           <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and:               <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ol> <p>6. Simulate a motion with the PHD under test.</p> <p>7. Wait for the simulated PHG to receive the event report:</p> <ol style="list-style-type: none"> <li>Mandatory attribute Enum-Observed-Value-Simple-Bit-Str           <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value= Only one of the following bits can be set:               <ul style="list-style-type: none"> <li>▪ motion-detected(0)</li> <li>▪ motion-detected-delayed(1)</li> <li>▪ tamper-detected(2)</li> </ul> </li> </ul> </li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+|                     |                                                                                                            |                        |                    |
+|---------------------|------------------------------------------------------------------------------------------------------------|------------------------|--------------------|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/HUB/BV-005_F                                                                              |                        |                    |
+| <b>TP label</b>     | Get activity data property exit sensor Enumeration Object attributes for Activity Hub                      |                        |                    |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                | [ISO/IEEE 11073-10471] |                    |
+|                     | <b>Testable items</b>                                                                                      | EnumObj 2; M           | EnumObj 3; M       |
+|                     |                                                                                                            | EnumObj 5; R           | EnumObj 6; R       |
+|                     |                                                                                                            | EnumObj 8; R           | EnumObj 9; R       |
+|                     |                                                                                                            | EnumObj 11; R          | EnumObj 13; O      |
+|                     |                                                                                                            | EnumObj 15; R          | EnumObj 16; R      |
+|                     |                                                                                                            | EnumObj 18; R          | EnumObj 19; R      |
+|                     |                                                                                                            | EnumObj 21; R          | EnumObj 22; M      |
+|                     |                                                                                                            | PropExitSensor3; M     | PropExitSensor4; M |
+|                     |                                                                                                            | PropExitSensor 2; O    | PropExitSensor5; M |
+| <b>Test purpose</b> | Check that:<br>Activity data enumeration object property exit sensor contains the attributes specified for |                        |                    |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | <p>Extended Configuration.</p> <p>[AND]</p> <p>An occupant exit detected event is sent whenever a sensor determines an occupant exiting event has occurred.</p> <p>[AND]</p> <p>If PHD can determine no condition detected event or exit door left open, then an exit door left open or no condition detected sensor event may be sent if the sensor can determine such a status and any of these situations occurs.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Applicability</b>     | C_AG_OXP_176 AND C_AG_HUB_025 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_183, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Configuring state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. The Data exit sensor object must be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_AI_TYPE_SENSOR_PROPEXIT</li> </ol> </li> <li>a. Mandatory attribute Absolute-Time-Stamp <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_ABS</li> <li><input type="checkbox"/> attribute-type = AbsoluteTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ol> </li> </ol> </li> <li>5. IF C_AG_OXP_293: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ol style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ol> </li> </ol> </li> <li>6. Simulate a property exit with the PHD under test.</li> <li>7. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value= Only one of the following bits can be set: <ul style="list-style-type: none"> <li>▪ occupant-exit-property(0)</li> <li>▪ exit-door-left-open(1)</li> </ul> </li> </ol> </li> </ol> </li> </ol> |
+
+|                           |                                                            |
+|---------------------------|------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure. |
+| <b>Notes</b>              |                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                 |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/HUB/BV-005_G                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |                 |
+| <b>TP label</b>          | Get activity data property enuresis sensor Enumeration Object attributes for Activity Hub                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-10471] |                 |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | EnumObj 2; M           | EnumObj 3; M    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | EnumObj 5; R           | EnumObj 6; R    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | EnumObj 8; R           | EnumObj 9; R    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | EnumObj 11; R          | EnumObj 13; O   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | EnumObj 15; R          | EnumObj 16; R   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | EnumObj 18; R          | EnumObj 19; R   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | EnumObj 21; R          | EnumObj 22; M   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | EnurSensor 1; M        | EnurSensor 2; O |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | EnurSensor4; M         | EnurSensor5; M  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Activity data enumeration object enuresis sensor contains the attributes specified for Extended Configuration.</p> <p>[AND]</p> <p>An enuresis detected event is sent whenever a sensor determines the condition has occurred.</p> <p>[AND]</p> <p>If PHD can determine no condition detected event, then a no condition detected sensor event may be sent if this situation occurs.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                 |
+| <b>Applicability</b>     | C_AG_OXP_176 AND C_AG_HUB_026 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                 |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                 |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Configuring state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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:</li> <li>4. The Data enuresis sensor object must be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_AI_TYPE_SENSOR_ENURESIS</li> </ol> </li> <li>b. Mandatory attribute Absolute-Time-Stamp <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_ABS</li> <li><input type="checkbox"/> attribute-type = AbsoluteTime</li> </ol> </li> </ol> </li> </ol> |                        |                 |
+
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                            |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|
+| <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> <p>5. IF C_AG_OXP_293:</p> <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ol> <p>6. Simulate an enuresis with the PHD under test.</p> <p>7. Wait for the simulated PHG to receive the event report:</p> <ol style="list-style-type: none"> <li>Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value= Only one of the following bits can be set: <ul style="list-style-type: none"> <li>▪ enuresis-detected(0)</li> </ul> </li> </ul> </li> </ol> |                                                            |
+| <b>Pass/Fail criteria</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | All checked values are as specified in the test procedure. |
+| <b>Notes</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                                                            |
+
+|                     |                                                                                                                                      |                        |                    |                    |
+|---------------------|--------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|--------------------|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/HUB/BV-005_H                                                                                                        |                        |                    |                    |
+| <b>TP label</b>     | Get activity data property contact closure sensor Enumeration Object attributes for Activity Hub                                     |                        |                    |                    |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                          | [ISO/IEEE 11073-10471] |                    |                    |
+|                     | <b>Testable items</b>                                                                                                                | EnumObj 2; M           | EnumObj 3; M       | EnumObj 4; M       |
+|                     |                                                                                                                                      | EnumObj 5; R           | EnumObj 6; R       | EnumObj 7; R       |
+|                     |                                                                                                                                      | EnumObj 8; R           | EnumObj 9; R       | EnumObj 10; R      |
+|                     |                                                                                                                                      | EnumObj 11; R          | EnumObj 13; O      | EnumObj 14; O      |
+|                     |                                                                                                                                      | EnumObj 15; R          | EnumObj 16; R      | EnumObj 17; M      |
+|                     |                                                                                                                                      | EnumObj 18; R          | EnumObj 19; R      | EnumObj 20; R      |
+|                     |                                                                                                                                      | EnumObj 21; R          | EnumObj 23; O      | EnumObj 22; M      |
+|                     |                                                                                                                                      | ContactSensor 1; M     | ContactSensor 2; O | ContactSensor 3; M |
+|                     |                                                                                                                                      | ContactSensor 4; M     | ContactSensor 5; M | ContactSensor X; M |
+| <b>Test purpose</b> | Check that:<br>Activity data enumeration object contact closure sensor contains the attributes specified for Extended Configuration. |                        |                    |                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>[AND]</p> <p>A closure closed event and closure opened event is sent whenever a sensor determines the condition has occurred</p> <p>[AND]</p> <p>If PHD can determine no condition detected event, then a no condition detected sensor event may be sent if this situation occurs.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Applicability</b>      | C_AG_OXP_176 AND C_AG_HUB_027 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Other PICS</b>         | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Configuring state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. The Data contact/closure sensor object must be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_AI_TYPE_SENSOR_CONTACTCLOSURE</li> </ol> </li> <li>b. Mandatory attribute Absolute-Time-Stamp <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_ABS</li> <li><input type="checkbox"/> attribute-type = AbsoluteTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ol> </li> </ol> </li> <li>5. IF C_AG_OXP_293: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ol style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ol> </li> </ol> </li> <li>6. Simulate a contact closure sensor activation with the PHD under test.</li> <li>7. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = Only one of the following bits can be set: <ul style="list-style-type: none"> <li>▪ contact-opened(0)</li> <li>▪ contact-opened(1)</li> </ul> </li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|              |  |
+|--------------|--|
+| <b>Notes</b> |  |
+|--------------|--|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/HUB/BV-005_I                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                  |
+| <b>TP label</b>          | Get activity data property usage sensor Enumeration Object attributes for Activity Hub                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [ISO/IEEE 11073-10471] |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | EnumObj 2; M           | EnumObj 3; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | EnumObj 5; R           | EnumObj 6; R     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | EnumObj 8; R           | EnumObj 9; R     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | EnumObj 11; R          | EnumObj 13; O    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | EnumObj 15; R          | EnumObj 16; R    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | EnumObj 18; R          | EnumObj 19; R    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | EnumObj 21; R          | EnumObj 22; M    |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | UsageSensor 1; O       | UsageSensor 2; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | UsageSensor 4; M       | UsageSensor 5; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | UsageSensor X; M       |                  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Activity data enumeration object usage sensor contains the attributes specified for Extended Configuration.</p> <p>[AND]</p> <p>A usage started event and usage ended event is sent whenever a sensor determines the condition has occurred.</p> <p>[AND]</p> <p>If PHD can determine no condition detected event or generate events based on violation of timing constraints based on usage or absence, then an expected use start violation, expected use stop violation, absence violation, or no condition detected sensor events may be sent if the sensor can determine such a status and any of these situations occurs.</p>                                                                                                                                                                |                        |                  |
+| <b>Applicability</b>     | C_AG_OXP_176 AND C_AG_HUB_028 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                  |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Configuring state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. The Data usage sensor object must be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_AI_TYPE_SENSOR_USAGE</li> </ul> </li> <li>b. Mandatory attribute Absolute-Time-Stamp</li> </ol> </li> </ol> |                        |                  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_ABS</li> <li><input type="checkbox"/> attribute-type = AbsoluteTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> <p>5. IF C_AG_OXP_293:</p> <ul style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ul> <p>6. Simulate a usage sensor activation with the PHD under test.</p> <p>7. Wait for the simulated PHG to receive the event report:</p> <ul style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = Only one of the following bits can be set: <ul style="list-style-type: none"> <li>▪ usage-started(0)</li> <li>▪ usage-started(1)</li> <li>▪ usage-started(2)</li> <li>▪ usage-started(3)</li> <li>▪ usage-started(4)</li> </ul> </li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+|                 |                                                                                |                        |               |               |
+|-----------------|--------------------------------------------------------------------------------|------------------------|---------------|---------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/HUB/BV-005_J                                                  |                        |               |               |
+| <b>TP label</b> | Get activity data switch sensor Enumeration Object attributes for Activity Hub |                        |               |               |
+| <b>Coverage</b> | <b>Spec</b>                                                                    | [ISO/IEEE 11073-10471] |               |               |
+|                 | <b>Testable items</b>                                                          | EnumObj 2; M           | EnumObj 3; M  | EnumObj 4; M  |
+|                 |                                                                                | EnumObj 5; R           | EnumObj 6; R  | EnumObj 7; R  |
+|                 |                                                                                | EnumObj 8; R           | EnumObj 9; R  | EnumObj 10; R |
+|                 |                                                                                | EnumObj 11; R          | EnumObj 13; O | EnumObj 14; O |
+|                 |                                                                                | EnumObj 15; R          | EnumObj 16; R | EnumObj 17; M |
+|                 |                                                                                | EnumObj 18; R          | EnumObj 19; R | EnumObj 20; R |
+|                 |                                                                                | EnumObj 21; R          | EnumObj 23; O | EnumObj 22; M |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                   |                   |                   |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------------|-------------------|
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | SwitchSensor 1; M | SwitchSensor 2; O | SwitchSensor 3; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | SwitchSensor 4; M | SwitchSensor 5; M | SwitchSensor X; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Activity data enumeration object switch sensor contains the attributes specified for Extended Configuration.</p> <p>[AND]</p> <p>A switch on and switch off event is sent whenever a sensor determines the condition has occurred.</p> <p>[AND]</p> <p>If PHD can determine no condition detected event, then a no condition detected sensor event may be sent if this situation occurs.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                   |                   |                   |
+| <b>Applicability</b>     | C_AG_OXP_176 AND C_AG_HUB_029 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                   |                   |                   |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                   |                   |                   |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Configuring state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                   |                   |                   |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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:</li> <li>4. The Data switch sensor object must be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_AI_TYPE_SENSOR_SWITCH</li> </ol> </li> <li>b. Mandatory attribute Absolute-Time-Stamp <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_ABS</li> <li><input type="checkbox"/> attribute-type = AbsoluteTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ol> </li> </ol> </li> <li>5. IF C_AG_OXP_293: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ol style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ol> </li> </ol> </li> <li>6. Simulate a switch-on or switch-off with the PHD under test.</li> <li>7. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> </ol> </li> </ol> </li> </ol> |                   |                   |                   |
+
+|                           |                                                                                                                                                                                                                                              |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> attribute-value.length = 4 bytes<br><input type="checkbox"/> attribute-value = Only one of the following bits can be set: <ul style="list-style-type: none"> <li>▪ switch-on(0)</li> <li>▪ switch-off(1)</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                              |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                   |                   |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|-------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/HUB/BV-005_K                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                   |                   |
+| <b>TP label</b>          | Get activity data dosage sensor Enumeration Object attributes for Activity Hub                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |                   |                   |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-10471] |                   |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | EnumObj 2; M           | EnumObj 3; M      | EnumObj 4; M      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | EnumObj 5; R           | EnumObj 6; R      | EnumObj 7; R      |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | EnumObj 8; R           | EnumObj 9; R      | EnumObj 10; R     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | EnumObj 11; R          | EnumObj 13; O     | EnumObj 14; O     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | EnumObj 15; R          | EnumObj 16; R     | EnumObj 17; M     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | EnumObj 18; R          | EnumObj 19; R     | EnumObj 20; R     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | EnumObj 21; R          | EnumObj 22; M     | EnumObj 23; O     |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | DosageSensor 1; M      | DosageSensor 2; O | DosageSensor 3; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | DosageSensor 4; M      | DosageSensor 5; M | DosageSensor X; M |
+| <b>Test purpose</b>      | Check that:<br>Activity data enumeration object medication dosage sensor contains the attributes specified for Extended Configuration.<br>[AND]<br>A dosage taken event is sent whenever a sensor determines the condition has occurred.<br>[AND]<br>If PHD can determine no condition detected event or dosage missed, then a dosage missed or no condition detected sensor event may be sent if the sensor can determine such a status and any of these situations occurs.                                                                                |                        |                   |                   |
+| <b>Applicability</b>     | C_AG_OXP_176 AND C_AG_HUB_030 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                   |                   |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                   |                   |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Configuring state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                   |                   |
+| <b>Test procedure</b>    | 1. The simulated PHG receives an association request from the PHD under test.<br>2. The simulated PHG responds with a result = accepted-unknown-config.<br>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.<br>4. The Data dosage sensor object must be: <ul style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> </ul> </li> </ul> |                        |                   |                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_AI_TYPE_SENSOR_DOSAGE</li> </ul> <p>b. Mandatory attribute Absolute-Time-Stamp</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_ABS</li> <li><input type="checkbox"/> attribute-type = AbsoluteTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ul> <p>5. IF C_AG_OXP_293:</p> <ul style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ul> <p>6. Simulate a valid dose or missed dose with the PHD under test.</p> <p>7. Wait for the simulated PHG to receive the event report:</p> <ul style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = = Only one of the following bits can be set: <ul style="list-style-type: none"> <li>▪ dosage-taken(0)</li> <li>▪ dosage-taken(1)</li> </ul> </li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                 |                                                                                     |                        |               |
+|-----------------|-------------------------------------------------------------------------------------|------------------------|---------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/HUB/BV-005_L                                                       |                        |               |
+| <b>TP label</b> | Get activity data temperature sensor Enumeration Object attributes for Activity Hub |                        |               |
+| <b>Coverage</b> | <b>Spec</b>                                                                         | [ISO/IEEE 11073-10471] |               |
+|                 | <b>Testable items</b>                                                               | EnumObj 2; M           | EnumObj 3; M  |
+|                 |                                                                                     | EnumObj 5; R           | EnumObj 6; R  |
+|                 |                                                                                     | EnumObj 8; R           | EnumObj 9; R  |
+|                 |                                                                                     | EnumObj 11; R          | EnumObj 13; O |
+|                 |                                                                                     | EnumObj 15; R          | EnumObj 16; R |
+|                 |                                                                                     | EnumObj 18; R          | EnumObj 19; R |
+|                 |                                                                                     | EnumObj 21; R          | EnumObj 22; M |
+|                 |                                                                                     |                        | EnumObj 23; O |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                 |                 |                |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------|----------------|
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | TempSensor 1; M | TempSensor 2; O | TempSensor3; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | TempSensor4; M  | TempSensor5; M  | TempSensorX; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Activity data enumeration object temperature sensor contains the attributes specified for Extended Configuration.</p> <p>[AND]</p> <p>A high temperature detected and low temperature detected event are sent whenever a sensor determines the condition has occurred.</p> <p>[AND]</p> <p>If PHD can determine no condition detected event or rate of change too fast, then a rate of change too fast or no condition detected sensor event may be sent if the sensor can determine such a status and any of these situations occurs.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                 |                 |                |
+| <b>Applicability</b>     | C_AG_OXP_176 AND C_AG_HUB_031 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                 |                 |                |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                 |                 |                |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Configuring state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                 |                 |                |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. The Data temperature sensor object must be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_AI_TYPE_SENSOR_TEMP</li> </ol> </li> <li>b. Mandatory attribute Absolute-Time-Stamp <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_ABS</li> <li><input type="checkbox"/> attribute-type = AbsoluteTime</li> <li><input type="checkbox"/> attribute-value.length = 8 bytes</li> </ol> </li> </ol> </li> <li>5. IF C_AG_OXP_293: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ol style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ol> </li> </ol> </li> <li>6. Simulate a change of temperature with the PHD under test.</li> <li>7. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> </ol> </li> </ol> </li> </ol> |                 |                 |                |
+
+|                           |                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> attribute-value.length = 4 bytes<br><input type="checkbox"/> attribute-value = Only one of the following bits can be set: <ul style="list-style-type: none"> <li>▪ high-temperature-detected(0)</li> <li>▪ high-temperature-detected(1)</li> <li>▪ high-temperature-detected(2)</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/HUB/BV-006_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |
+| <b>TP label</b>           | Semantic of activity data property exit sensor.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-10471] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | PropExitSensor5;M      |
+| <b>Test purpose</b>       | Check that:<br>If Activity data enumeration property exit sensor object is supported by the PHD, the Enum-Observed-Value-Simple-Bit-Str attribute shall be present.<br>The specific sensor event properties flags are contained in the most significant (high) 16 bits.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |
+| <b>Applicability</b>      | C_AG_OXP_176 AND C_AG_HUB_025 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Simulate a property exit with the PHD under test.</li> <li>2. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value= Only one of the following bits can be set: <ul style="list-style-type: none"> <li>▪ occupant-exit-properly(0)</li> </ul> </li> </ul> </li> </ol> </li> <li>3. Simulate an exit that leaves open the door with the PHD under test.</li> <li>4. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value= Only one of the following bits can be set: <ul style="list-style-type: none"> <li>▪ exit-door-left-open(1)</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                        |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |  |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/HUB/BV-006_B                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |  |
+| <b>TP label</b>           | Semantic of activity data property contact closure sensor.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-10471] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | ContactSensor5;M       |  |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>If Activity data enumeration property exit sensor object is supported by the PHD, the Enum-Observed-Value-Simple-Bit-Str attribute shall be present.</p> <p>The specific sensor event properties flags are contained in the most significant (high) 16 bits.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |  |
+| <b>Applicability</b>      | C_AG_OXP_176 AND C_AG_HUB_027 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Simulate an opening with the PHD under test.</li> <li>2. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = contact-opened(0)</li> </ol> </li> </ol> </li> <li>3. Simulate a closing with the PHD under test.</li> <li>4. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = contact-closed(1)</li> </ol> </li> </ol> </li> </ol> |                        |  |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |  |
+
+|                      |                                                                                                                                                                                                                                                                                        |                        |  |
+|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>         | TP/PLT/PHD/CLASS/HUB/BV-006_C                                                                                                                                                                                                                                                          |                        |  |
+| <b>TP label</b>      | Semantic of activity data property usage sensor.                                                                                                                                                                                                                                       |                        |  |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-10471] |  |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                  | UsageSensor6;M         |  |
+| <b>Test purpose</b>  | <p>Check that:</p> <p>If Activity data enumeration property exit sensor object is supported by the PHD, the Enum-Observed-Value-Simple-Bit-Str attribute shall be present.</p> <p>The specific sensor event properties flags are contained in the most significant (high) 16 bits.</p> |                        |  |
+| <b>Applicability</b> | C_AG_OXP_176 AND C_AG_HUB_028 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                        |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Simulate a correct start of usage with the PHD under test.</li> <li>2. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = usage-started(0)</li> </ol> </li> </ol> </li> <li>3. Simulate a correct ending of usage with the PHD under test.</li> <li>4. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = usage-ended(1)</li> </ol> </li> </ol> </li> <li>5. Simulate an incorrect start of usage with the PHD under test.</li> <li>6. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = expected-use-start-violation(2)</li> </ol> </li> </ol> </li> <li>7. Simulate an incorrect ending of usage with the PHD under test.</li> <li>8. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = expected-use-stop-violation(3)</li> </ol> </li> </ol> </li> <li>9. Simulate a correct start of usage with the PHD under test.</li> <li>10. Do not end it.</li> <li>11. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = absence-violation(4)</li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |  |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/HUB/BV-006_D                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |  |
+| <b>TP label</b>           | Semantic of activity data switch sensor.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-10471] |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | SwitchSensor5;M        |  |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>If Activity data enumeration property exit sensor object is supported by the PHD, the Enum-Observed-Value-Simple-Bit-Str attribute shall be present.</p> <p>The specific sensor event properties flags are contained in the most significant (high) 16 bits.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |  |
+| <b>Applicability</b>      | C_AG_OXP_176 AND C_AG_HUB_029 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Simulate a switch-on with the PHD under test.</li> <li>2. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = switch-on(0)</li> </ul> </li> </ol> </li> <li>3. Simulate a switch-off with the PHD under test.</li> <li>4. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li>attribute-value = switch-off(1)</li> </ul> </li> </ol> </li> </ol> |                        |  |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |  |
+
+|                      |                                                                                                                                                                                                                                                                                        |                        |  |
+|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>         | TP/PLT/PHD/CLASS/HUB/BV-006_E                                                                                                                                                                                                                                                          |                        |  |
+| <b>TP label</b>      | Semantic of activity data dosage sensor.                                                                                                                                                                                                                                               |                        |  |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-10471] |  |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                  | DosageSensor5;M        |  |
+| <b>Test purpose</b>  | <p>Check that:</p> <p>If Activity data enumeration property exit sensor object is supported by the PHD, the Enum-Observed-Value-Simple-Bit-Str attribute shall be present.</p> <p>The specific sensor event properties flags are contained in the most significant (high) 16 bits.</p> |                        |  |
+| <b>Applicability</b> | C_AG_OXP_176 AND C_AG_HUB_030 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                        |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Simulate a valid dose with the PHD under test.</li> <li>2. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = dosage-taken(0)</li> </ol> </li> </ol> </li> <li>3. Simulate a missed dose with the PHD under test.</li> <li>4. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = dosage-missed(1)</li> </ol> </li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/HUB/BV-006_F                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |  |
+| <b>TP label</b>          | Semantic of activity data temperature sensor.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-10471] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | TempSensor5;M          |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>If Activity data enumeration property exit sensor object is supported by the PHD, the Enum-Observed-Value-Simple-Bit-Str attribute shall be present.</p> <p>The specific sensor event properties flags are contained in the most significant (high) 16 bits.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |  |
+| <b>Applicability</b>     | C_AG_OXP_176 AND C_AG_HUB_031 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Simulate high temperature with the PHD under test.</li> <li>2. Wait for the simulated PHG to receive the event report: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = high-temperature-detected(0)</li> </ol> </li> </ol> </li> <li>3. Simulate a low temperature with the PHD under test.</li> <li>4. Wait for the simulated PHG to receive the event report:</li> </ol> |                        |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = low-temperature-detected(1)</li> </ul> <p>5. Simulate a fast changing of temperatures with the PHD under test.</p> <p>6. Wait for the simulated PHG to receive the event report:</p> <p>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = rate-of-change-too-fast(2)</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |               |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/HUB/BV-008                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |               |
+| <b>TP label</b>          | Association Activity Hub PHD                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |               |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-10471] |               |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | MDSMethod 6; M         | AssocRqt1; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | AssocRqt3; M           | AssocRqt4; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | AssocRqt6; M           | AssocRqt7; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | AssocRqt9; M           | AssocRqt11; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | AssocRqt13; M          |               |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>During the association procedure, Activity Hub PHD sends the correct association request to the simulated PHG.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |               |
+| <b>Applicability</b>     | C_AG_OXP_176 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |               |
+| <b>Other PICS</b>        | C_AG_OXP_017                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |               |
+| <b>Test procedure</b>    | <p>1. The PHD sends a message to associate to the simulated PHG, the expected fields sent by the PHD are:</p> <p>a. APDU Type</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = AarqApdu</li> <li><input type="checkbox"/> field-length =2 bytes</li> <li><input type="checkbox"/> field-value =0xE2 0x00.</li> </ul> <p>b. assoc-version</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = AssociationVersion</li> <li><input type="checkbox"/> field-length =BITS-32</li> <li><input type="checkbox"/> field- value=0x80 0x00 0x00 0x00</li> </ul> |                        |               |
+
+- 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 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 =
+    - <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-
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>req-supp-init-agent(15))</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> If the PHD supports requesting objects based on the object handle → Bit 6 will be set (data-req-supp-scope-handle(6)).</li> <li><input type="checkbox"/> If the PHD supports single response → Bit 8 will be set (data-req-supp-mode-single-rsp(8)).</li> <li><input type="checkbox"/> If the PHD supports time unlimited data request → Bit 10 will be set (data-req-supp-mode-time-no-limit(10)).</li> </ul> <p>l. data-req-init-agent-count (DataReqModeCapab)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = INT-U8</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field.value = 0x01</li> </ul> <p>m. data-req-init-manager-count (DataReqModeCapab)</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = INT-U8</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field.value = 0x00</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked attributes have proper values.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/HUB/BV-009_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                |  |
+| <b>TP label</b>          | Activity data Fall sensor Enumeration Object. Heartbeat Operational Status                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [ISO/IEEE 11073-10471] |                |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | EnumObj 24; C          | FallSensor 5;M |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Generic Sensor Health properties flags value: auto-presence-received(16),auto-presence-failed(17)</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                |  |
+| <b>Applicability</b>     | C_AG_OXP_176 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                |  |
+| <b>Other PICS</b>        | C_AG_HUB_033                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Trigger a fall sensor supported by the PHD under test.</li> <li>2. Wait for the event report, check the following attribute: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>▪ IF C_AG_HUB_033 = TRUE, then <ul style="list-style-type: none"> <li>• bit 16 (auto-presence-received) must be set</li> <li>• bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ul> </li> <li>▪ IF C_AG_HUB_033 = FALSE, then <ul style="list-style-type: none"> <li>• bit 16 (auto-presence-received) must <b>not</b> be set</li> <li>• bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ul> </li> </ul> </li> </ul> </li> </ol> </li> </ol> |                        |                |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>3. Wait the time specified by the vendor. In that time an event report must be received by the simulated PHG.</p> <p>4. IF C_AG_HUB_033 = TRUE: Disable or disconnect the sensor (as defined by the vendor) and again wait the specified time. In that time an event report must be received by the simulated PHG, check the following attribute:</p> <p>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must <b>not</b> be set</li> <li>▪ bit 17 (auto-presence-failed) must be set</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |               |  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/HUB/BV-009_B                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |               |  |
+| <b>TP label</b>          | Activity data PERS sensor Enumeration Object. Heartbeat Operational Status                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-10471] |               |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | EnumObj 24; C          | PERSSensor5;M |  |
+| <b>Test purpose</b>      | Check that:<br>Generic Sensor Health properties flags value: auto-presence-received(16),auto-presence-failed(17)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |               |  |
+| <b>Applicability</b>     | C_AG_OXP_176 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |               |  |
+| <b>Other PICS</b>        | C_AG_HUB_033, C_AG_HUB_035                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |               |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Trigger a PERS sensor supported by the PHD under test.</li> <li>2. Wait for the event report, check the following attribute: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str</li> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = <ol style="list-style-type: none"> <li><input type="checkbox"/> IF C_AG_HUB_035 = TRUE, then <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ul> </li> <li><input type="checkbox"/> IF C_AG_HUB_035 = FALSE, then <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must not be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ul> </li> </ol></li> </ol> </li> <li>3. Wait the time specified by the vendor. In that time an event report must be received by the simulated PHG.</li> <li>4. IF C_AG_HUB_035 = TRUE: Disable or disconnect the sensor (as defined by vendor)</li> </ol> |                        |               |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>and wait again the specified time. In that time an event report must be received by the simulated PHG, check the following attribute:</p> <p>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must <b>not</b> be set</li> <li>▪ bit 17 (auto-presence-failed) must be set</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/HUB/BV-009_C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                  |
+| <b>TP label</b>          | Activity data Environmental sensor Enumeration Object. Heartbeat Operational Status                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-10471] |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | EnumObj 24; C          | EnvironSensor5;M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Generic Sensor Health properties flags value: auto-presence-received(16),auto-presence-failed(17)</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |                  |
+| <b>Applicability</b>     | C_AG_OXP_176 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                  |
+| <b>Other PICS</b>        | C_AG_HUB_033, C_AG_HUB_036                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Trigger an Environmental sensor supported by the PHD under test.</li> <li>2. Wait for the event report, check the following attribute: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li><input type="checkbox"/> IF C_AG_HUB_036 = TRUE, then <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ul> </li> <li><input type="checkbox"/> IF C_AG_HUB_036 = FALSE, then <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must not be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ul> </li> </ul> </li> </ul> </li> </ol> </li> <li>3. Wait the time specified by the vendor. In that time an event report must be received by the simulated PHG.</li> <li>4. IF C_AG_HUB_036 = TRUE: Disable or disconnect the sensor (as defined by the vendor) and again wait the specified time. In that time an event report must be received by the simulated PHG, check the following attribute: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str</li> </ol> </li> </ol> |                        |                  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR<br><input type="checkbox"/> attribute-type = BITS-32<br><input type="checkbox"/> attribute-value.length = 4 bytes<br><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must <b>not</b> be set</li> <li>▪ bit 17 (auto-presence-failed) must be set</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                               |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |                 |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/HUB/BV-009_D                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                 |  |
+| <b>TP label</b>          | Activity data Motion sensor Enumeration Object. Heartbeat Operational Status                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                 |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [ISO/IEEE 11073-10471] |                 |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | EnumObj 24; C          | MotionSensor5;M |  |
+| <b>Test purpose</b>      | Check that:<br>Generic Sensor Health properties flags value: auto-presence-received(16),auto-presence-failed(17)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                 |  |
+| <b>Applicability</b>     | C_AG_OXP_176 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                 |  |
+| <b>Other PICS</b>        | C_AG_HUB_033, C_AG_HUB_037                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                 |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                 |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Trigger a Motion sensor supported by the PHD under test.</li> <li>2. Wait for the event report, check the following attribute:           <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value =                   <ul style="list-style-type: none"> <li><input type="checkbox"/> IF C_AG_HUB_037 = TRUE, then                       <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ul> </li> <li><input type="checkbox"/> IF C_AG_HUB_037 = FALSE, then                       <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must not be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ul> </li> </ul> </li> </ul> </li> </ol> </li> <li>3. Wait the time specified by the vendor. In that time an event report must be received by the simulated PHG.</li> <li>4. IF C_AG_HUB_037 = TRUE: Disable or disconnect the sensor (as defined by the vendor) and again wait the specified time. In that time an event report must be received by the simulated PHG, check the following attribute:           <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> </ul> </li> </ol> </li> </ol> |                        |                 |  |
+
+|                           |                                                                                                                                                                                                                                                                         |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> attribute-value.length = 4 bytes<br><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must <b>not</b> be set</li> <li>▪ bit 17 (auto-presence-failed) must be set</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                              |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                         |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                   |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/HUB/BV-009_E                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |                   |  |
+| <b>TP label</b>          | Activity data Property Exit sensor Enumeration Object. Heartbeat Operational Status                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                   |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-10471] |                   |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | EnumObj 24; C          | PropExitSensor5;M |  |
+| <b>Test purpose</b>      | Check that:<br>Generic Sensor Health properties flags value: auto-presence-received(16),auto-presence-failed(17)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                   |  |
+| <b>Applicability</b>     | C_AG_OXP_176 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                   |  |
+| <b>Other PICS</b>        | C_AG_HUB_033, C_AG_HUB_038                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                   |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                   |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Trigger a Property Exit sensor supported by the PHD under test.</li> <li>2. Wait for the event report, check the following attribute:           <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value =                   <ul style="list-style-type: none"> <li><input type="checkbox"/> IF C_AG_HUB_038 = TRUE, then                       <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ul> </li> <li><input type="checkbox"/> IF C_AG_HUB_038 = FALSE, then                       <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must not be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ul> </li> </ul> </li> </ul> </li> </ol> </li> <li>3. Wait the time specified by the vendor. In that time an event report must be received by the simulated PHG.</li> <li>4. IF C_AG_HUB_038 = TRUE: Disable or disconnect the sensor (as defined by the vendor) and again wait the specified time. In that time an event report must be received by the simulated PHG, check the following attribute:           <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str               <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value =</li> </ul> </li> </ol> </li> </ol> |                        |                   |  |
+
+|                           |                                                                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must <b>not</b> be set</li> <li>▪ bit 17 (auto-presence-failed) must be set</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                      |
+| <b>Notes</b>              |                                                                                                                                                                 |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |               |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|--|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/HUB/BV-009_F                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |               |  |
+| <b>TP label</b>          | Activity data Enuresis sensor Enumeration Object. Heartbeat Operational Status                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |               |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [ISO/IEEE 11073-10471] |               |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | EnumObj 24; C          | EnurSensor5;M |  |
+| <b>Test purpose</b>      | Check that:<br>Generic Sensor Health properties flags value: auto-presence-received(16),auto-presence-failed(17)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |               |  |
+| <b>Applicability</b>     | C_AG_OXP_176 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |               |  |
+| <b>Other PICS</b>        | C_AG_HUB_033, C_AG_HUB_039                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |               |  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |               |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. Trigger an Enuresis sensor supported by the PHD under test.</li> <li>2. Wait for the event report, check the following attribute: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li><input type="checkbox"/> IF C_AG_HUB_039 = TRUE, then <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ul> </li> <li><input type="checkbox"/> IF C_AG_HUB_039 = FALSE, then <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must not be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ul> </li> </ul> </li> </ul> </li> </ol> </li> <li>3. Wait the time specified by the vendor. In that time an event report must be received by the simulated PHG.</li> <li>4. IF C_AG_HUB_039 = TRUE: Disable or disconnect the sensor (as defined by the vendor) and again wait the specified time. In that time an event report must be received by the simulated PHG, check the following attribute: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must <b>not</b> be set</li> <li>▪ bit 17 (auto-presence-failed) must be set</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                        |               |  |
+
+|                           |                                                            |
+|---------------------------|------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure. |
+| <b>Notes</b>              |                                                            |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/HUB/BV-009_G                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                  |
+| <b>TP label</b>           | Activity data Contact Closure sensor Enumeration Object. Heartbeat Operational Status                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-10471] |                  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | EnumObj 24; C          | ContactSensor5;M |
+| <b>Test purpose</b>       | Check that:<br>Generic Sensor Health properties flags value: auto-presence-received(16),auto-presence-failed(17)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                  |
+| <b>Applicability</b>      | C_AG_OXP_176 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                  |
+| <b>Other PICS</b>         | C_AG_HUB_033, C_AG_HUB_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Trigger a Contact Closure sensor supported by the PHD under test.</li> <li>2. Wait for the event report, check the following attribute: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li><input type="checkbox"/> IF C_AG_HUB_040 = TRUE, then <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ul> </li> <li><input type="checkbox"/> IF C_AG_HUB_040 = FALSE, then <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must <b>not</b> be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ul> </li> </ul> </li> </ul> </li> </ol> </li> <li>3. Wait the time specified by the vendor. In that time an event report must be received by the simulated PHG.</li> <li>4. IF C_AG_HUB_040 = TRUE: Disable or disconnect the sensor (as defined by the vendor) and again wait the specified time. In that time an event report must be received by the simulated PHG, check the following attribute: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must <b>not</b> be set</li> <li>▪ bit 17 (auto-presence-failed) must be set</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                        |                  |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                |  |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/HUB/BV-009_H                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                |  |
+| <b>TP label</b>           | Activity data Usage sensor Enumeration Object. Heartbeat Operational Status                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | [ISO/IEEE 11073-10471] |                |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | EnumObj 24; C          | UsageSensor6;M |  |
+| <b>Test purpose</b>       | Check that:<br>Generic Sensor Health properties flags value: auto-presence-received(16),auto-presence-failed(17)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                |  |
+| <b>Applicability</b>      | C_AG_OXP_176 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                |  |
+| <b>Other PICS</b>         | C_AG_HUB_033, C_AG_HUB_041                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |                |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Trigger a Usage sensor supported by the PHD under test.</li> <li>2. Wait for the event report, check the following attribute: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = <ol style="list-style-type: none"> <li><input type="checkbox"/> IF C_AG_HUB_041 = TRUE, then <ol style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ol> </li> <li><input type="checkbox"/> IF C_AG_HUB_041 = FALSE, then <ol style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must <b>not</b> be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ol> </li> </ol> </li> </ol> </li> <li>3. Wait the time specified by vendor. In that time an event report must be received by the simulated PHG.</li> <li>4. IF C_AG_HUB_041 = TRUE: Disable or disconnect the sensor (as defined by the vendor) and again wait the specified time. In that time an event report must be received by the simulated PHG, check the following attribute: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = <ol style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must <b>not</b> be set</li> <li>▪ bit 17 (auto-presence-failed) must be set</li> </ol> </li> </ol> </li> </ol> </li> </ol> </li></ol> |                        |                |  |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |                |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                 |  |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|--|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/HUB/BV-009_I                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                 |  |
+| <b>TP label</b>           | Activity data Switch sensor Enumeration Object. Heartbeat Operational Status                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                 |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-10471] |                 |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | EnumObj 24; C          | SwitchSensor5;M |  |
+| <b>Test purpose</b>       | Check that:<br>Generic Sensor Health properties flags value: auto-presence-received(16),auto-presence-failed(17)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |                 |  |
+| <b>Applicability</b>      | C_AG_OXP_176 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                 |  |
+| <b>Other PICS</b>         | C_AG_HUB_033, C_AG_HUB_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                 |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                 |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Trigger a Switch sensor supported by the PHD under test.</li> <li>2. Wait for the event report, check the following attribute: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li><input type="checkbox"/> IF C_AG_HUB_042 = TRUE, then <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ul> </li> <li><input type="checkbox"/> IF C_AG_HUB_042 = FALSE, then <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must <b>not</b> be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ul> </li> </ul> </li> </ul> </li> </ol> </li> <li>3. Wait the time specified by the vendor. In that time an event report must be received by the simulated PHG.</li> <li>4. IF C_AG_HUB_042 = TRUE: Disable or disconnect the sensor (as defined by the vendor) and again wait the specified time. In that time an event report must be received by the simulated PHG, check the following attribute: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must <b>not</b> be set</li> <li>▪ bit 17 (auto-presence-failed) must be set</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                        |                 |  |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                 |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                 |  |
+
+|                 |                                                                              |
+|-----------------|------------------------------------------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/HUB/BV-009_J                                                |
+| <b>TP label</b> | Activity data Dosage sensor Enumeration Object. Heartbeat Operational Status |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                 |  |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|--|
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-10471] |                 |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | EnumObj 24; C          | DosageSensor5;M |  |
+| <b>Test purpose</b>       | Check that:<br>Generic Sensor Health properties flags value: auto-presence-received(16),auto-presence-failed(17)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                        |                 |  |
+| <b>Applicability</b>      | C_AG_OXP_176 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                 |  |
+| <b>Other PICS</b>         | C_AG_HUB_033, C_AG_HUB_043                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                 |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                 |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Trigger a Dosage sensor supported by the PHD under test.</li> <li>2. Wait for the event report, check the following attribute: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = <ol style="list-style-type: none"> <li><input type="checkbox"/> IF C_AG_HUB_043 = TRUE, then <ol style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ol> </li> <li><input type="checkbox"/> IF C_AG_HUB_043 = FALSE, then <ol style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must <b>not</b> be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ol> </li> </ol> </li> </ol> </li> </ol> </li> <li>3. Wait the time specified by the vendor. In that time an event report must be received by the simulated PHG.</li> <li>4. IF C_AG_HUB_043 = TRUE: Disable or disconnect the sensor (as defined by the vendor) and again wait the specified time. In that time an event report must be received by the simulated PHG, check the following attribute: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = <ol style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must <b>not</b> be set</li> <li>▪ bit 17 (auto-presence-failed) must be set</li> </ol> </li> </ol> </li> </ol> </li> </ol> |                        |                 |  |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                 |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                 |  |
+
+|                 |                                                                                   |                        |               |  |
+|-----------------|-----------------------------------------------------------------------------------|------------------------|---------------|--|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/HUB/BV-009_K                                                     |                        |               |  |
+| <b>TP label</b> | Activity data Temperature sensor Enumeration Object. Heartbeat Operational Status |                        |               |  |
+| <b>Coverage</b> | <b>Spec</b>                                                                       | [ISO/IEEE 11073-10471] |               |  |
+|                 | <b>Testable</b>                                                                   | EnumObj 24; C          | TempSensor5;M |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |  |  |  |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|
+|                           | <b>items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |  |  |  |
+| <b>Test purpose</b>       | Check that:<br>Generic Sensor Health properties flags value: auto-presence-received(16),auto-presence-failed(17)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |  |  |  |
+| <b>Applicability</b>      | C_AG_OXP_176 AND C_AG_OXP_181 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  |  |  |
+| <b>Other PICS</b>         | C_AG_HUB_033, C_AG_HUB_044                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |  |  |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |  |  |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. Trigger a temperature sensor supported by the PHD under test.</li> <li>2. Wait for the event report, check the following attribute: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = <ol style="list-style-type: none"> <li><input type="checkbox"/> IF C_AG_HUB_044 = TRUE, then <ol style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ol> </li> <li><input type="checkbox"/> IF C_AG_HUB_044 = FALSE, then <ol style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must <b>not</b> be set</li> <li>▪ bit 17 (auto-presence-failed) must <b>not</b> be set</li> </ol> </li> </ol> </li> </ol> </li> <li>3. Wait the time specified by the vendor. In that time an event report must be received by the simulated PHG.</li> <li>4. IF C_AG_HUB_044 = TRUE: Disable or disconnect the sensor (as defined by the vendor) and again wait the specified time. In that time an event report must be received by the simulated PHG, check the following attribute: <ol style="list-style-type: none"> <li>a. Mandatory attribute Enum-Observed-Value-Simple-Bit-Str <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_BIT_STR</li> <li><input type="checkbox"/> attribute-type = BITS-32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = <ol style="list-style-type: none"> <li>▪ bit 16 (auto-presence-received) must <b>not</b> be set</li> <li>▪ bit 17 (auto-presence-failed) must be set</li> </ol> </li> </ol> </li> </ol> </li> </ol> </li></ol> |  |  |  |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |  |  |  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |  |  |  |
+
+|                 |                                               |                                                               |  |  |
+|-----------------|-----------------------------------------------|---------------------------------------------------------------|--|--|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/HUB/BV-010                   |                                                               |  |  |
+| <b>TP label</b> | Operating State. PHG to PHD Maximum APDU Size |                                                               |  |  |
+| <b>Coverage</b> | <b>Spec</b>                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |  |  |
+|                 | <b>Testable items</b>                         | CommonCharac 3; M                                             |  |  |
+|                 | <b>Spec</b>                                   | [ISO/IEEE 11073-10471]                                        |  |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |               |  |  |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--|--|
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ComCharac2; M |  |  |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>Check that the total size of the response do not exceed of the maximum APDU size established by the specialization</p> <p>[AND]</p> <p>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</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |               |  |  |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_176                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |               |  |  |
+| <b>Other PICS</b>         | C_AG_OXP_041, C_AG_OXP_100                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |               |  |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |               |  |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG issues a "Remote Operation Invoke   Get" command with: <ol style="list-style-type: none"> <li>a. Obj-handle set to 0 (to request for MDS object)</li> <li>b. attribute-id-list.count = 103</li> <li>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</li> </ol> </li> <li>2. Check the response of the PHD.</li> <li>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.</li> <li>4. Check the response of the PHD</li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |               |  |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• 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. <ul style="list-style-type: none"> <li>○ 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): <ul style="list-style-type: none"> <li>▪ Pulse oximeter → 9216 octets</li> <li>▪ Weighing scales → 896 octets</li> <li>▪ Glucose meter → 5120 octets or 64512 octets if the PHD supports PM-Store</li> <li>▪ Blood pressure → 896 octets</li> <li>▪ Thermometer → 896 octets</li> <li>▪ Independent activity hub → 5120 octets</li> <li>▪ Cardiovascular → 64512 octets or 6624 octets if the PHD under test only supports Step Counter Profile</li> <li>▪ Strength → 64512 octets:</li> <li>▪ Adherence monitor → 1024 octets</li> <li>▪ Peak Flow → 2030 octets</li> <li>▪ Body composition analyser → 7730 octets</li> <li>▪ Basic ECG/Simple ECG → 7168 octets or 64512 octets if the PHD supports PM-Store</li> <li>▪ Basic ECG/Heart Rate → 1280 octets or 64512 octets if the PHD supports PM-Store</li> <li>▪ International normalized ratio → 896 octets or 64512 if the PHD supports PM-Store</li> </ul> </li> </ul> </li> </ul> |               |  |  |
+
+|              |                                                                                                                                                                                                                     |
+|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|              | <ul style="list-style-type: none"><li>○ In the case where it responds with a roer, the reason must not be protocol-violation (23)</li><li>• In step 4, the PHD must respond with a rors-cmip-get message.</li></ul> |
+| <b>Notes</b> |                                                                                                                                                                                                                     |
+
+## 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.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-PHG PICS & PIXIT] Personal Health Gateway DG2016 PICS and PIXIT excel sheet v1.9.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-TCRL] Test Case Reference List\_DG2016\_v1.11.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-TI] Continua DG2016 PHD Testable items excel sheet v1.8.  
+<http://handle.itu.int/11.1002/2000/12067>
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.845.9-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.845.9-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bd7c24e83d75a6b1baa7fb4210f76345166390c9
--- /dev/null
+++ b/marked/H/T-REC-H.845.9-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5866ab521163bd4f911ae6e27d0a1cf1f491c665e9b87b7d7076098a143f4bff
+size 3944
diff --git a/marked/H/T-REC-H.845.9-201704-I_PDF-E/raw.md b/marked/H/T-REC-H.845.9-201704-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..bbfa2d5958ffc4872a7addf6378629cde2265f3a
--- /dev/null
+++ b/marked/H/T-REC-H.845.9-201704-I_PDF-E/raw.md
@@ -0,0 +1,1041 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.845.9**
+
+(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 5I: Medication adherence monitor**
+
+Recommendation ITU-T H.845.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.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        |
+| <b>Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN)</b> | <b>H.820–H.859</b> |
+| 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.9
+
+# Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5I: Medication adherence monitor
+
+## Summary
+
+Recommendation ITU-T H.845.9 provides a test suite structure (TSS) and the test purposes (TP) for medication adherence 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.9 is a transposition of Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5I: Device Specializations. Personal Health Device (Adherence 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.9  | 2015-01-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/12270">11.1002/1000/12270</a> |
+| 2.0     | ITU-T H.845.9  | 2016-07-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12946">11.1002/1000/12946</a> |
+| 3.0     | ITU-T H.845.9  | 2017-04-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/13227">11.1002/1000/13227</a> |
+
+## Keywords
+
+Conformance testing, Continua Design Guidelines, e-health, IEEE 11073 device specialization, ITU-T H.810, medication adherence monitor, personal area network, personal connected health devices, Personal Health Devices interface, touch area network.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.1     | Subgroup 1.3.9: Adherence monitor (AM) ..... | 9  |
+|         | 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 Continua Test Tool DG2016, Test Suite Structure & Test Purposes, Personal Health Devices Interface; Part 5I: Device Specializations. Personal Health Device (Adherence 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_5I_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_5I_v1.2.doc" as a baseline and adds new features included in [b-CDG 2012]: <ul style="list-style-type: none"> <li>• Max APDU size for GM, BCA and ECG</li> </ul>                                                                                                                         |
+| 1.4     | 2014-01-24 | Initial release for Test Tool DG2013. This uses "TSS&TP_DG2012_PAN-LAN_PART_5I_v1.4.doc" as a baseline and adds new features included in [b-ITU-T H.810 (2013)]/[b-CDG 2013]: <ul style="list-style-type: none"> <li>• Adds glucose meter BLE</li> <li>• Adds BLE SSP support</li> <li>• Adds NFC new transport</li> <li>• Adds INR device specialization</li> </ul> |
+| 1.5     | 2014-04-24 | TM Lite & Doc Enhancements (Test Tool v4.0 Maintenance release 1). It uses "TSS&TP_DG2013_PLT_PART_5I_v1.4.doc" as a baseline and adds new features included in Documentation Enhancements: <ul style="list-style-type: none"> <li>• "Other PICS" row added</li> </ul>                                                                                               |
+| 1.5     | 2015-07-01 | Initial release for Test Tool DG2015. It is the same version as "TSS&TP_DG2013_PLT_PART_5I_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 this document.                                                                                                                |
+| 1.6     | 2016-09-20 | Initial release for Test Tool DG2016. It uses "TSS&TP_DG2015_PLT_PART_5I_v1.5.doc" as baseline and adds new features included in [ITU-T H.810 (2016)]/[b-CDG 2016]                                                                                                                                                                                                   |
+
+## Recommendation ITU-T H.845.9
+
+## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 5I: Medication adherence monitor
+
+## 1 Scope
+
+The scope of this Recommendation<sup>1</sup> 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 5I.
+
+- 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
+
+---
+
+<sup>1</sup> 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-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>
+- [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.  
+<https://www.iso.org/standard/54331.html> with  
+<https://www.iso.org/standard/63972.html>
+- [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.  
+<https://www.iso.org/standard/66717.html> with  
+<https://www.iso.org/standard/71886.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 |
+| 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.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 <http://handle.itu.int/11.1002/2000/12067>.
+
+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>/<DUT>/<GR>/<SGR>/<XX> – <NNN>). It is specified according to the naming convention defined below:
+  - Each test purpose identifier is introduced by the prefix "TP".
+  - <TT>: 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)
+  - <DUT>: This is the device under test:
+    - PHD: Personal Health Device
+    - PHG: Personal Health Gateway
+  - <GR>: This identifies a group of test cases.
+  - <SGR>: This identifies a subgroup of test cases.
+  - <XX>: This identifies the type of testing:
+    - BV: Valid behaviour test
+    - BI: Invalid behaviour test
+  - <NNN>: 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.1 Subgroup 1.3.9: Adherence monitor (AM)
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                 |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/AM/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                 |
+| <b>TP label</b>          | Get MDS Object for Adherence Monitor specialization: Mandatory, Conditional and Optional Attributes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [ISO/IEEE 11073-10472] |                 |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | MM_MDSAttr1; M         | MM_MDSAttr2; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | MM_MDSAttr4; R         | MM_MDSAttr5; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | MM_MDSAttr7; M         | MM_MDSAttr8; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | MM_GETServ4; M         | MM_OperProc2; M |
+| <b>Test purpose</b>      | Check that:<br>The PHD supports a Get command that requests all attributes<br>[AND]<br>The MDS Object contains the attributes specified for a Medication Monitor PHD.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                 |
+| <b>Applicability</b>     | C_AG_OXP_168 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                 |
+| <b>Other PICS</b>        | C_AG_OXP_181, C_AG_AM_001, C_AG_AM_002, C_AG_AM_003, C_AG_AM_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                 |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>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.</li> <li>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:<br/> MDS Attributes: <ol style="list-style-type: none"> <li>a. Mandatory attribute System-model <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_MODEL</li> <li><input type="checkbox"/> attribute-type = SystemModel</li> <li><input type="checkbox"/> attribute-value.length =&lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value ={Manufacturer, Model}</li> </ul> </li> <li>b. Mandatory attribute Dev-Configuration-Id <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_DEV_CONFIG_ID</li> <li><input type="checkbox"/> attribute-type = ConfigId</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = <ul style="list-style-type: none"> <li>– IF C_AG_AM_001 then attribute-value = 0x1C 0x20</li> <li>– ELSE IF C_AG_AM_002 then attribute-value = 0x1C 0x21</li> <li>– ELSE IF C_AG_AM_003 then attribute-value = 0x1C 0x22</li> <li>– ELSE IF C_AG_AM_004 then attribute-value = 0x1C 0x23</li> <li>– ELSE attribute-value = &lt; between 0x4000 and 0x7FFF</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                        |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>c. Recommended attribute Power-Status</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_POWER_STAT</li> <li><input type="checkbox"/> attribute-type = PowerStatus (BITS-16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value =<br/>ON_MAINS (0x8000) or ON_BATTERY(0x4000)<br/>Only one of the following may be active: <ul style="list-style-type: none"> <li>▪ chargingFull(8),</li> <li>▪ chargingTrickle(9),</li> <li>▪ chargingOff(10).</li> <li>▪ The rest of the bits must not be set</li> </ul> </li> </ul> <p>d. Recommended attribute Battery-Level</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_VAL_BATT_CHARGE</li> <li><input type="checkbox"/> attribute-type = INT-U16</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;undefined if value&gt;100 &gt;</li> </ul> <p>e. Recommended attribute Remaining-Battery-Time</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_BATT_REMAIN</li> <li><input type="checkbox"/> attribute-type = BatMeasure</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;</li> <li><input type="checkbox"/> attribute-value = &lt;units shall be set to one of: MDC_DIM_MIN, MDC_DIM_HR, MDC_DIM_DAY &gt;</li> </ul> <p>f. Mandatory attribute System-Type-Spec_List</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SYS_TYPE_SPEC_LIST</li> <li><input type="checkbox"/> attribute-type = TypeVerList</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes attribute-value =<br/>MDC_DEV_SPEC_PROFILE_AI_MED_MINDER, 1</li> <li><input type="checkbox"/> Attribute System-Type must not be present.</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                    |                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  |                  |               |                  |                    |                   |                   |                   |                 |                 |                  |                 |               |                  |                     |                 |  |  |
+|--------------------|--------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|------------------|---------------|------------------|--------------------|-------------------|-------------------|-------------------|-----------------|-----------------|------------------|-----------------|---------------|------------------|---------------------|-----------------|--|--|
+| <b>TP Id</b>       | TP/PLT/PHD/CLASS/AM/BV-001                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  |                  |               |                  |                    |                   |                   |                   |                 |                 |                  |                 |               |                  |                     |                 |  |  |
+| <b>TP label</b>    | MDS Configuration objects events for Adherence Monitor |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  |                  |               |                  |                    |                   |                   |                   |                 |                 |                  |                 |               |                  |                     |                 |  |  |
+| <b>Coverage</b>    | <b>Spec</b>                                            | [ISO/IEEE 11073-10472]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |  |                  |               |                  |                    |                   |                   |                   |                 |                 |                  |                 |               |                  |                     |                 |  |  |
+|                    | <b>Testable items</b>                                  | <table border="1" style="width: 100%; border-collapse: collapse;"> <tr> <td>MedDispensed1; M</td> <td>StatusRep1; O</td> <td>UserFeedback1; O</td> </tr> <tr> <td>MM_StandConfig1; C</td> <td>MM_StandConfig2;C</td> <td>MM_StandConfig3;C</td> </tr> <tr> <td>MM_StandConfig4;C</td> <td>MM_MDSEvent1; M</td> <td>MM_GenNumObj1;M</td> </tr> <tr> <td>MM_GenNumObj2; O</td> <td>FixedDosage1; M</td> <td>VarDosage1; M</td> </tr> <tr> <td>StatReporter1; O</td> <td>MM_EventRepServ1; M</td> <td>MM_ConfProc1; M</td> </tr> <tr> <td> </td> <td> </td> <td> </td> </tr> </table> |  | MedDispensed1; M | StatusRep1; O | UserFeedback1; O | MM_StandConfig1; C | MM_StandConfig2;C | MM_StandConfig3;C | MM_StandConfig4;C | MM_MDSEvent1; M | MM_GenNumObj1;M | MM_GenNumObj2; O | FixedDosage1; M | VarDosage1; M | StatReporter1; O | MM_EventRepServ1; M | MM_ConfProc1; M |  |  |
+| MedDispensed1; M   | StatusRep1; O                                          | UserFeedback1; O                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |  |                  |               |                  |                    |                   |                   |                   |                 |                 |                  |                 |               |                  |                     |                 |  |  |
+| MM_StandConfig1; C | MM_StandConfig2;C                                      | MM_StandConfig3;C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |  |                  |               |                  |                    |                   |                   |                   |                 |                 |                  |                 |               |                  |                     |                 |  |  |
+| MM_StandConfig4;C  | MM_MDSEvent1; M                                        | MM_GenNumObj1;M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  |                  |               |                  |                    |                   |                   |                   |                 |                 |                  |                 |               |                  |                     |                 |  |  |
+| MM_GenNumObj2; O   | FixedDosage1; M                                        | VarDosage1; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |  |                  |               |                  |                    |                   |                   |                   |                 |                 |                  |                 |               |                  |                     |                 |  |  |
+| StatReporter1; O   | MM_EventRepServ1; M                                    | MM_ConfProc1; M                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  |                  |               |                  |                    |                   |                   |                   |                 |                 |                  |                 |               |                  |                     |                 |  |  |
+|                    |                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  |                  |               |                  |                    |                   |                   |                   |                 |                 |                  |                 |               |                  |                     |                 |  |  |
+|                    |                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  |                  |               |                  |                    |                   |                   |                   |                 |                 |                  |                 |               |                  |                     |                 |  |  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>      | <p>Check that:</p> <p>A Medication Monitor shall send the [MDS-Configuration-Event] using a [Confirmed] event report. The [MDS-Configuration-Event] shall include the event-info [ConfigReport].</p> <p>[AND]</p> <p>Check objects supported by the PHD (standard /extended configuration)</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Applicability</b>     | C_AG_OXP_168 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Other PICS</b>        | C_AG_OXP_010, C_AG_OXP_181, C_AG_AM_001, C_AG_AM_002, C_AG_AM_003, C_AG_AM_004, C_AG_AM_005, C_AG_AM_006, C_AG_AM_007, C_AG_AM_008                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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: <ol style="list-style-type: none"> <li>a. APDU Type <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = PrstApdu</li> <li><input type="checkbox"/> field-length =2 bytes</li> <li><input type="checkbox"/> field-value =0xE7 0x00</li> </ol> </li> <li>b. invoke-id <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = InvokeIDType</li> <li><input type="checkbox"/> field-length =INT-U16</li> <li><input type="checkbox"/> field- value=&lt;Not relevant for this test&gt;</li> </ol> </li> <li>c. message <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = roiv-cmip-confirmed-event-report</li> <li><input type="checkbox"/> field-length =two bytes</li> <li><input type="checkbox"/> field- value=0x01 0x01 (EventReportArgumentSimple)</li> </ol> </li> <li>d. obj-handle (EventReportArgumentSimple) <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = HANDLE</li> <li><input type="checkbox"/> field-length =INT-U16</li> </ol> </li> <li>e. event-time (EventReportArgumentSimple) <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = Relative Time</li> <li><input type="checkbox"/> field-length =INT-U32</li> <li><input type="checkbox"/> field-value = <ul style="list-style-type: none"> <li>• IF NOT C_AG_OXP_010 THEN value = 0xFF 0xFF 0xFF 0xFF</li> </ul> </li> </ol> </li> <li>f. event-type (EventReportArgumentSimple) <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = OID-Type</li> <li><input type="checkbox"/> field-length =INT-U16</li> <li><input type="checkbox"/> field- value=0x 0D 0x 1C (MDC_NOTI_CONFIG)</li> </ol> </li> <li>g. config-report-id (ConfigReport) <ol style="list-style-type: none"> <li><input type="checkbox"/> field- type = ConfigId</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field- value = <ul style="list-style-type: none"> <li>• IF C_AG_AM_001 then attribute-value = 0x1C 0x20</li> <li>• ELSE IF C_AG_AM_002 then attribute-value = 0x1C 0x21</li> </ul> </li> </ol> </li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• ELSE IF C_AG_AM_003 then attribute-value = 0x1C 0x22</li> <li>• ELSE IF C_AG_AM_004 then attribute-value = 0x1C 0x23</li> <li>• ELSE IF C_AG_OXP_181=TRUE then attribute-value = &lt; between 0x4000 and 0x7FFF &gt;</li> </ul> <p>h. obj-class ( ConfigReport → ConfigObjectList (ConfigObject)). To check the objects that are supported by the PHD, Type Attribute will be checked in AttributeList.</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = OID-Type</li> <li><input type="checkbox"/> field-length = INT-U16</li> <li><input type="checkbox"/> field- value = <ul style="list-style-type: none"> <li>• IF C_AG_AM_001 then 1 Fixed Dosage Medication object is present.</li> <li>• ELSE IF C_AG_AM_002 then 1 Fixed Dosage Medication, 1 Status Reporter and 1 User Feedback object are present.</li> <li>• ELSE IF C_AG_AM_003 then 1 Variable Dosage Medication object is present.</li> <li>• ELSE IF C_AG_AM_004 then 1 Variable Dosage Medication, 1 Status Reporter and 1 User Feedback object are present.</li> <li>• ELSE : <ul style="list-style-type: none"> <li>▪ IF C_AG_AM_005 then 1 Fixed Dosage Medication is present, ELSE this object is not present.</li> <li>▪ IF C_AG_AM_006 then 1 Variable Dosage Medication is present, ELSE this object is not present.</li> <li>▪ Exactly one of the fixed dosage medication dispensed numeric object or the variable dosage medication dispensed numeric object shall be supported.</li> <li>▪ IF C_AG_AM_007 then User Feedback is present, ELSE this object is not present.</li> <li>▪ IF C_AG_AM_008 then Status Reporter is present, ELSE this object is not present.</li> </ul> </li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|                 |                                                        |                        |                   |
+|-----------------|--------------------------------------------------------|------------------------|-------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/AM/BV-002                             |                        |                   |
+| <b>TP label</b> | MDS objects events Adherence Monitor & PM-Store Object |                        |                   |
+| <b>Coverage</b> | <b>Spec</b>                                            | [ISO/IEEE 11073-10472] |                   |
+|                 | <b>Testable items</b>                                  | MM_MDSEvent2; M        | MM_MDSEvent3; M   |
+|                 |                                                        | MM_MDSEvent5; M        | MM_MDSEvent6; M   |
+|                 |                                                        | MM_MDSEvent8; M        | MM_MDSEvent9; M   |
+|                 |                                                        | MM_EventRepServ1; M    | MM_OperProc11; M  |
+|                 |                                                        | MM_PMStoreGen1; M      | MM_PMStoreGen2; M |
+|                 |                                                        | MM_OperProc5; M        | MM_OperProc6; M   |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>      | <p>Check that:</p> <p>The PHD sends the MDS-Dynamic-Data-Update-Fixed using a confirmed event report and it includes the event-info ScanReportInfoFixed</p> <p>[AND/OR]</p> <p>The PHD sends the MDS-Dynamic-Data-Update-Var using a confirmed event report and it includes the event-info ScanReportInfoVar</p> <p>[AND/OR]</p> <p>The PHD sends the MDS-Dynamic-Data-Update-MP-Fixed using a confirmed event report and it includes the event-info ScanReportInfoMPFixed</p> <p>[AND/OR]</p> <p>The PHD sends the MDS-Dynamic-Data-Update-MP-Var using a confirmed event report and it includes the event-info ScanReportInfoMPVar</p> <p>[AND]</p> <p>A medication monitor PHD with standard configuration shall use the fixed format data update messages method for transmitting measurement data</p> <p>[AND]</p> <p>A medication monitor PHD with extended configuration may use either fixed or variable format data update messages for transmitting measurement data.</p> <p>[AND]</p> <p>Any configuration that does not include a PM-store object utilizes agent-initiated event reports to transmit all retained observations</p> <p>[AND]</p> <p>Any configuration with a PM-store for longer-term storage shall disable agent-initiated transmission and shall enable access to the PM-store transmissions</p>                                                                                                                                                                                                                                                                                                                                          |
+| <b>Applicability</b>     | C_AG_OXP_168 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Other PICS</b>        | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_041, C_AG_OXP_181, C_AG_OXP_293, C_AG_AM_001, C_AG_AM_002, C_AG_AM_003, C_AG_AM_004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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 the tested configuration is received.</li> <li>5. IF C_AG_OXP_293: <ol style="list-style-type: none"> <li>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.</li> <li>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.</li> <li>c. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ol> </li> <li>6. Record the PHD configuration.</li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>7. Take Measurements for every supported object in the PHD under test.</p> <p>8. Wait to receive every event report and check:</p> <ul style="list-style-type: none"> <li>• IF the PHD does not support PM-Store, THEN MDS-Event Report is sent by the PHD to report the measurements.</li> <li>• IF the PHD supports PM-Store, THEN the PHD shall not send MDS event reports.</li> <li>• For MDS Event Reports: <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = Event Report</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> 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.</li> </ul> </li> </ul>                                                                                                                                                                                                                                                                                                                    |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• Check that every received MDS Event report is a one of the following Data APDU and that it is confirmed.</li> <li>• For Standard Configuration (C_AG_AM_001 or C_AG_AM_002 or C_AG_AM_003 or C_AG_AM_004): the MDS Event Report is sent by the PHD to report measurements for every object. <ul style="list-style-type: none"> <li><input type="checkbox"/> MDC_NOTI_SCAN_REPORT_FIXED</li> <li><input type="checkbox"/> MDC_NOTI_SCAN_REPORT_MP_FIXED</li> </ul> </li> <li>• For an Extended Configuration that does not support the PM-Store object, an MDS Event Report is sent by the PHD to report measurements for every object: <ul style="list-style-type: none"> <li><input type="checkbox"/> MDC_NOTI_SCAN_REPORT_FIXED</li> <li><input type="checkbox"/> MDC_NOTI_SCAN_REPORT_MP_FIXED</li> <li><input type="checkbox"/> MDC_NOTI_SCAN_REPORT_VAR</li> <li><input type="checkbox"/> MDC_NOTI_SCAN_REPORT_MP_VAR</li> </ul> </li> <li>• For an Extended Configuration that supports the PM-Store object, an MDS Event Report is not sent by the PHD to report measurements for objects.</li> </ul> |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                     |                                                                                        |                        |                  |
+|---------------------|----------------------------------------------------------------------------------------|------------------------|------------------|
+| <b>TP Id</b>        | TP/PLT/PHD/CLASS/AM/BV-003                                                             |                        |                  |
+| <b>TP label</b>     | Fixed Dosage Medication Dispensed Object for Standard Configuration (0x1C20 or 0x1C21) |                        |                  |
+| <b>Coverage</b>     | <b>Spec</b>                                                                            | [ISO/IEEE 11073-10472] |                  |
+|                     | <b>Testable items</b>                                                                  | FixedDosage2; M        | FixedDosage3; M  |
+|                     |                                                                                        | FixedDosage5; M        | FixedDosage6; R  |
+|                     |                                                                                        | FixedDosage8; R        | FixedDosage9; R  |
+|                     |                                                                                        | FixedDosage11; R       | FixedDosage12; M |
+|                     |                                                                                        | FixedDosage14; O       | FixedDosage15; O |
+|                     |                                                                                        | FixedDosage17; R       | FixedDosage18; C |
+|                     |                                                                                        | FixedDosage20; C       | FixedDosage21; C |
+|                     |                                                                                        | FixedDosage23; C       | FixedDosage24; C |
+|                     |                                                                                        | FixedDosage26; R       | FixedDosage39; M |
+|                     |                                                                                        |                        | MM_ConfProc2; M  |
+| <b>Test purpose</b> | Check that:                                                                            |                        |                  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | Fixed Dosage Medication Dispensed Numeric Object contains the attributes specified for Standard Configuration (0x1C20 or 0x1C21)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Applicability</b>      | C_AG_OXP_168 AND (C_AG_AM_001 OR C_AG_AM_002) AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is set to 0x1C20 OR 0x1C21. 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 0x1C20 or 0x1C21 is received.</li> <li>5. Once the PHD under test sends a standard configuration, check the Fixed Dosage Medication object.</li> <li>6. The Fixed Dosage Medication object contents shall be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_HANDLE</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x01</li> </ol> </li> <li>b. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_AI, MDC_AI_MED_DISPENSED_FIXED</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• Bit 0 (mss-avail-intermittent(0)) must be set.</li> <li>• Bit 1 (mss-avail-stored-data(1)) must be set.</li> <li>• Bit 2 (mss-upd-aperiodic(2)) must be set.</li> <li>• Bit 3 (mss-msmt-aperiodic(3)) is set.</li> <li>• Bit 9 (mss-acc-agent-initiated(9)) is set.</li> </ol> </li> </ol> </li> <li>d. Mandatory attribute Attribute-Value-Map <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = AttrValMap</li> <li><input type="checkbox"/> attribute-count = 2</li> <li><input type="checkbox"/> attribute-value = (MDC_ATTR_TIME_STAMP_ABS ,8<br/>MDC_ATTR_NU_VAL_OBS_BASIC,2)</li> </ol> </li> </ol> </li> <li>7. Check that no other attributes are present in the initial configuration.</li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |                  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/AM/BV-004                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                  |
+| <b>TP label</b>          | Fixed Dosage Medication Dispensed Object for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [ISO/IEEE 11073-10472] |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | FixedDosage27; M       | FixedDosage28; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | FixedDosage30; O       | FixedDosage31; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | FixedDosage33; R       | FixedDosage34; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | FixedDosage36; R       | FixedDosage37; R |
+| <b>Test purpose</b>      | Check that:<br>Fixed Dosage Medication Dispensed Numeric Object contains the attributes specified for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                  |
+| <b>Applicability</b>     | C_AG_OXP_168 AND C_AG_OXP_181 AND C_AG_AM_005 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |                  |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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.</li> <li>5. Once the PHD under test sends the tested configuration, check the Fixed Dosage Medication object.</li> <li>6. The Fixed Dosage Medication object contents shall be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li>attribute-value = MDC_PART_PHD_AI, MDC_AI_MED_DISPENSED_FIXED</li> </ul> </li> <li>b. IF Not Recommended attribute Supplemental-Types <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;Sequence of TYPE (TYPE.length= 4 bytes)</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> </li> <li>c. IF Not recommended attribute Metric-Structure-Small is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> </li> <li>d. IF Optional attribute Measurement-Status is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> </li> </ol> </li> </ol> |                        |                  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>e. IF Not recommended attribute Metric-Id is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>f. IF Not Recommended attribute Metric-Id-List is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIS</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>g. IF Not recommended attribute Metric-Id-Partition is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>h. IF Not recommended attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>i. IF Not recommended attribute Source-Handle-Reference is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>j. IF Not recommended attribute Relative-Time-Stamp</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_REL</li> <li><input type="checkbox"/> attribute-type = RelativeTime (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>k. IF Not recommended attribute Measure-Active-Period</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>l. IF Not Recommended attribute Accuracy is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                 |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/AM/BV-005                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |                 |
+| <b>TP label</b>          | Variable Dosage Medication Dispensed Object for Standard Configuration (0x1C22 or 0x1C23)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [ISO/IEEE 11073-10472] |                 |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | VarDosage2; M          | VarDosage3; M   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | VarDosage5; M          | VarDosage6; R   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | VarDosage8; R          | VarDosage9; R   |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | VarDosage11; M         | VarDosage12; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | VarDosage14; O         | VarDosage15; O  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | VarDosage17; R         | VarDosage18; C  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | VarDosage20; C         | VarDosage21; C  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | VarDosage23; C         | VarDosage24; C  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | VarDosage26; R         | VarDosage39; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        | MM_ConfProc2; M |
+| <b>Test purpose</b>      | Check that:<br>Variable Dosage Medication Dispensed Numeric Object contains the attributes specified for Standard Configuration (0x1C22 or 0x1C23)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                 |
+| <b>Applicability</b>     | C_AG_OXP_168 AND (C_AG_AM_003 OR C_AG_AM_004) AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                 |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                 |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is set to 0x1C22 OR 0x1C23. 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 0x1C22 or 0x1C23 is received.</li> <li>5. Once the PHD under test sends a standard configuration, check the Variable Dosage Medication object.</li> <li>6. The Variable Dosage Medication object contents shall be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_HANDLE</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x02</li> </ol> </li> <li>b. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_AI, MDC_AI_MED_DISPENSED_VARIABLE</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall</li> </ol> </li> </ol> </li> </ol> |                        |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00           <ul style="list-style-type: none"> <li>• Bit 0 (mss-avail-intermittent(0)) must be set.</li> <li>• Bit 1 (mss-avail-stored-data(1)) must be set.</li> <li>• Bit 2 (mss-upd-aperiodic(2)) must be set.</li> <li>• Bit 3 (mss-msmt-aperiodic(3)) is set.</li> <li>• Bit 9 (mss-acc-agent-initiated(9)) is set.</li> </ul> </li> </ul> <p>d. Mandatory attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = MDC_DIM_MILLI_L</li> </ul> <p>e. Mandatory attribute Attribute-Value-Map</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = AttrValMap</li> <li><input type="checkbox"/> attribute-count = 2</li> <li><input type="checkbox"/> attribute-value = (MDC_ATTR_TIME_STAMP_ABS ,8<br/>MDC_ATTR_NU_VAL_OBS_SIMP,4)</li> </ul> <p>7. Check that no other attributes are present in the initial configuration.</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                    |                        |                |                |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------|----------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/AM/BV-006                                                                                                                                                                                                                                                                                                                                                         |                        |                |                |
+| <b>TP label</b>          | Variable Dosage Medication Dispensed Object for Extended Configuration                                                                                                                                                                                                                                                                                                             |                        |                |                |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                        | [ISO/IEEE 11073-10472] |                |                |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                              | VarDosage27; M         | VarDosage28; R | VarDosage29; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                    | VarDosage30; O         | VarDosage31; R | VarDosage32; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                    | VarDosage33; R         | VarDosage34; M | VarDosage35; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                    | VarDosage36; R         | VarDosage37; R | VarDosage38; R |
+| <b>Test purpose</b>      | Check that:<br>Variable Dosage Medication Dispensed Numeric Object contains the attributes specified for Extended Configuration                                                                                                                                                                                                                                                    |                        |                |                |
+| <b>Applicability</b>     | C_AG_OXP_168 AND C_AG_OXP_181 AND C_AG_AM_006 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                     |                        |                |                |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                    |                        |                |                |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                            |                        |                |                |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> </ol> |                        |                |                |
+
+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 Variable Dosage Medication object.
+6. The Variable Dosage Medication object contents shall be:
+  - a. Mandatory attribute Type
+    - attribute-id = MDC\_ATTR\_ID\_TYPE
+    - attribute-type = TYPE
+    - attribute-value = MDC\_PART\_PHD\_AI, MDC\_AI\_MED\_DISPENSED\_VARIABLE
+  - 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>
+  - c. 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>
+  - d. IF Optional 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>
+  - e. 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>
+  - f. 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>
+  - 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 = <Not relevant for this test>
+  - h. Mandatory recommended attribute Unit-Code
+    - attribute-id = MDC\_ATTR\_UNIT\_CODE
+    - attribute-type = OID-Type(INT-U16)
+    - attribute-value.length = 2 bytes
+    - attribute-value = <Not relevant for this test>
+  - i. IF Not recommended attribute Source-Handle-Reference is present
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> j. IF Not recommended attribute Relative-Time-Stamp <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_REL</li> <li><input type="checkbox"/> attribute-type = RelativeTime (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> k. IF Not recommended attribute Measure-Active-Period <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> l. IF Not Recommended attribute Accuracy is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                      |                                                                                                                             |                        |                   |                   |
+|----------------------|-----------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|-------------------|
+| <b>TP Id</b>         | TP/PLT/PHD/CLASS/AM/BV-007                                                                                                  |                        |                   |                   |
+| <b>TP label</b>      | User Feedback Object for Standard Configuration (0x1C21 or 0x1C23)                                                          |                        |                   |                   |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                 | [ISO/IEEE 11073-10472] |                   |                   |
+|                      | <b>Testable items</b>                                                                                                       | UserFeedback2; M       | UserFeedback3; M  | UserFeedback4; R  |
+|                      |                                                                                                                             | UserFeedback5; M       | UserFeedback6; R  | UserFeedback7; O  |
+|                      |                                                                                                                             | UserFeedback8; R       | UserFeedback9; M  | UserFeedback10 ;R |
+|                      |                                                                                                                             | UserFeedback11 ;R      | UserFeedback12 ;M | UserFeedback13 ;R |
+|                      |                                                                                                                             | UserFeedback14 ;O      | UserFeedback15 ;O | UserFeedback16 ;C |
+|                      |                                                                                                                             | UserFeedback17 ;R      | UserFeedback18 ;C | UserFeedback19 ;R |
+|                      |                                                                                                                             | UserFeedback20 ;C      | UserFeedback21 ;C | UserFeedback22 ;C |
+|                      |                                                                                                                             | UserFeedback23 ;C      | UserFeedback24 ;C | UserFeedback25 ;C |
+|                      |                                                                                                                             | UserFeedback26 ;R      | UserFeedback38; M | MM_ConfProc2; M   |
+|                      |                                                                                                                             |                        |                   |                   |
+| <b>Test purpose</b>  | Check that:<br>User Feedback Numeric Object contains the attributes specified for Standard Configuration (0x1C21 or 0x1C23) |                        |                   |                   |
+| <b>Applicability</b> | C_AG_OXP_168 AND (C_AG_AM_002 OR C_AG_AM_004) AND C_AG_OXP_000                                                              |                        |                   |                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is set to 0x1C21 OR 0x1C23. 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 0x1C21 or 0x1C23 is received.</li> <li>5. Once the PHD under test sends a standard configuration, check the User Feedback object:</li> <li>6. The User Feedback object contents shall be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_HANDLE</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x04</li> </ol> </li> <li>b. Mandatory attribute Type <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_AI, MDC_AI_MED_FEEDBACK</li> </ol> </li> <li>c. Mandatory attribute Metric-Spec-Small <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00 <ol style="list-style-type: none"> <li>• Bit 0 (mss-avail-intermittent(0)) must be set.</li> <li>• Bit 1 (mss-avail-stored-data(1)) must be set.</li> <li>• Bit 2 (mss-upd-aperiodic(2)) must be set.</li> <li>• Bit 3 (mss-msmt-aperiodic(3)) is set.</li> <li>• Bit 9 (mss-acc-agent-initiated(9)) is set.</li> <li>• Bit 12 (mss-cat-manual(12)) is set.</li> </ol> </li> </ol> </li> <li>d. Mandatory attribute Metric-Id-List is present <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO_LIS</li> <li><input type="checkbox"/> attribute-type = MetricIdList</li> <li><input type="checkbox"/> attribute-value = MDC_AI_MED_UF_LOCATION, MDC_AI_MED_UF_RESPONSE</li> </ol> </li> <li>e. Mandatory attribute Attribute-Value-Map <ol style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = AttrValMap</li> <li><input type="checkbox"/> attribute-count = 2</li> <li><input type="checkbox"/> attribute-value = (MDC_ATTR_TIME_STAMP_ABS ,8 MDC_ATTR_NU_CMPD_VAL_OBS_BASIC,8)</li> </ol> </li> </ol> </li> <li>7. Check that no other attributes are present in the initial configuration.</li> </ol> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|              |  |
+|--------------|--|
+| <b>Notes</b> |  |
+|--------------|--|
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                   |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/AM/BV-007_A                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                   |
+| <b>TP label</b>           | User Feedback Object format for Standard Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                   |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [ISO/IEEE 11073-10472] |                   |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | UserFeedback39; M      | UserFeedback23; C |
+| <b>Test purpose</b>       | Check that:<br>User Feedback measurement values are in the right order in event report.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                   |
+| <b>Applicability</b>      | C_AG_OXP_168 AND (C_AG_AM_002 OR C_AG_AM_004) AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                   |
+| <b>Other PICS</b>         | C_AG_OXP_009, C_AG_OXP_014, C_AG_OXP_293                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                   |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                        |                   |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is set to 0x1C21 OR 0x1C23. 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 0x1C21 or 0x1C23 is received.</li> <li>5. Once the PHD under test sends the tested configuration, the simulated PHG sends a "roiv-cmip-get" to get all the attributes of the MDS, record the value of Date-and-Time.</li> <li>6. IF C_AG_OXP_293: <ol style="list-style-type: none"> <li>a. 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.</li> <li>b. IF the mds-time-mgr-set-time bit is set: <ul style="list-style-type: none"> <li><input type="checkbox"/> The PHG moves to Configuring/Sending Set Time substate and: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_009 it issues the Set-Time action command.</li> <li>• IF C_AG_OXP_014 it issues the Set-Base-Offset-Time action command.</li> </ul> </li> <li><input type="checkbox"/> Once its internal time setting operation is completed, the PHD responds to the PHG.</li> </ul> </li> </ol> </li> <li>7. Once the PHD under test is in the Operating state, take a measurement and record the value of the measurement.</li> <li>8. Wait until the PHD under test sends an Event Report to the simulated PHG, the relevant fields are: <ol style="list-style-type: none"> <li>a. event-type = MDC_NOTI_SCAN_REPORT_FIXED</li> <li>b. ScanReportInfoFixed <ul style="list-style-type: none"> <li><input type="checkbox"/> obj-handle = 4</li> <li><input type="checkbox"/> Compound Object Count =2</li> <li><input type="checkbox"/> obs-val-data.value = <ul style="list-style-type: none"> <li>• Time Stamp (8 bytes)</li> <li>• Location (2 bytes)</li> <li>• Response (2 bytes)</li> </ul> </li> </ul> </li> </ol> </li> </ol> |                        |                   |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• The received data must be coherent with that previously recorded.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                   |
+
+|              |                                                                                                                                                                                                                                                                                                                                                       |
+|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|              | <ul style="list-style-type: none"> <li>The Time Stamp must be coherent with that received in the MDS attribute.</li> <li>The data must be received in this exact same order and the Compound value contains two fields, the first one that represents the "relative location" and the second one that is the user response (numeric form).</li> </ul> |
+| <b>Notes</b> |                                                                                                                                                                                                                                                                                                                                                       |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                   |                   |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|-------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/AM/BV-008                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                   |                   |
+| <b>TP label</b>          | User Feedback Object for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                   |                   |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [ISO/IEEE 11073-10472] |                   |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | UserFeedback27; M      | UserFeedback28; R | UserFeedback29; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | UserFeedback30; O      | UserFeedback31; R | UserFeedback32; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | UserFeedback33; R      | UserFeedback34; R | UserFeedback35; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | UserFeedback36; R      | UserFeedback37; R |                   |
+| <b>Test purpose</b>      | Check that:<br>User Feedback Numeric Object contains the attributes specified for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |                   |                   |
+| <b>Applicability</b>     | C_AG_OXP_168 AND C_AG_OXP_181 AND C_AG_AM_007 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                   |                   |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |                   |                   |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |                   |                   |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHG receives an association request from the PHD under test.</li> <li>The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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.</li> <li>Once the PHD under test sends the tested configuration, check User Feedback object:</li> <li>User Feedback Object contents shall be: <ol style="list-style-type: none"> <li>Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_AI, MDC_AI_MED_FEEDBACK</li> </ul> </li> <li>IF Not Recommended attribute Supplemental-Types <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SUPPLEMENTAL_TYPES</li> <li><input type="checkbox"/> attribute-type = SupplementalTypeList</li> <li><input type="checkbox"/> attribute-value.length = &lt;variable&gt;Sequence of TYPE (TYPE.length= 4 bytes)</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> </li> <li>IF Not recommended attribute Metric-Structure-Small is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STRUCTURE_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricStructureSmall</li> <li><input type="checkbox"/> attribute-length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> </li> </ol> </li> </ol> |                        |                   |                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>d. IF Optional attribute Measurement-Status is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_MSMT_STAT</li> <li><input type="checkbox"/> attribute-type = MeasurementStatus</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>e. IF Not recommended attribute Metric-Id is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_PHYSIO</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>f. IF Not recommended attribute Metric-Id-Partition is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_ID_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>g. IF Not recommended attribute Unit-Code</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_UNIT_CODE</li> <li><input type="checkbox"/> attribute-type = OID-Type(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>h. IF Not recommended attribute Source-Handle-Reference is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SOURCE_HANDLE_REF</li> <li><input type="checkbox"/> attribute-type = HANDLE(INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>i. IF Not recommended attribute Relative-Time-Stamp</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_REL</li> <li><input type="checkbox"/> attribute-type = RelativeTime (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>j. IF Not recommended attribute Measure-Active-Period</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>k. IF Not Recommended attribute Accuracy is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_NU_ACCUR_MSMT</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                   |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/AM/BV-009                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                   |
+| <b>TP label</b>          | Status Reporter Object for Standard Configuration (0x1C21 or 0x1C23)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                   |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [ISO/IEEE 11073-10472] |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | StatReporter2; M       | StatReporter3; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | StatReporter5; M       | StatReporter6; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | StatReporter8; R       | StatReporter9; R  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | StatReporter11; R      | StatReporter12; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | StatReporter14; O      | StatReporter15; O |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | StatReporter17; R      | StatReporter18; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | StatReporter20; R      | StatReporter21; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | StatReporter23; C      | StatReporter24; C |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | StatReporter26; R      | StatReporter27; O |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | MM_ConfProc2; M        | StatReporter44; M |
+| <b>Test purpose</b>      | Check that:<br>Status Reporter Enumeration Object contains the attributes specified for Standard Configuration (0x1C21 or 0x1C23)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                        |                   |
+| <b>Applicability</b>     | C_AG_OXP_168 AND (C_AG_AM_002 OR C_AG_AM_004) AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |                   |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                   |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                   |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>4. Check that the field Dev-Config-Id is set to 0x1C21 OR 0x1C23. 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 0x1C21 or 0x1C23 is received.</li> <li>5. Once the PHD under test sends a standard configuration, check the Status Reporter object</li> <li>6. The Status Reporter object contents shall be: <ol style="list-style-type: none"> <li>a. Mandatory attribute Handle <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_HANDLE</li> <li><input type="checkbox"/> attribute-type = HANDLE</li> <li><input type="checkbox"/> attribute-value = 0x00 0x03</li> </ul> </li> <li>b. Mandatory attribute Type <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ID_TYPE</li> <li><input type="checkbox"/> attribute-type = TYPE</li> <li><input type="checkbox"/> attribute-value = MDC_PART_PHD_AI, MDC_AI_MED_STATUS</li> </ul> </li> <li>c. Mandatory attribute Metric-Spec-Small <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_SPEC_SMALL</li> <li><input type="checkbox"/> attribute-type = MetricSpecSmall (BITS-16)</li> </ul> </li> </ol> </li> </ol> |                        |                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-value ≠ 0x00 0x00           <ul style="list-style-type: none"> <li>• Bit 0 (mss-avail-intermittent(0)) must be set.</li> <li>• Bit 1 (mss-avail-stored-data(1)) must be set.</li> <li>• Bit 2 (mss-upd-aperiodic(2)) must be set.</li> <li>• Bit 3 (mss-msmt-aperiodic(3)) is set.</li> <li>• Bit 9 (mss-acc-agent-initiated(9)) is set.</li> </ul> </li> </ul> <p>d. Mandatory attribute Attribute-Value-Map</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_ATTRIBUTE_VAL_MAP</li> <li><input type="checkbox"/> attribute-type = AttrValMap</li> <li><input type="checkbox"/> attribute-count = 2</li> <li><input type="checkbox"/> attribute-value = (MDC_ATTR_TIME_STAMP_ABS ,8<br/>MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR,2)</li> </ul> <p>7. Check that no other attributes are present in the initial configuration.</p> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                   |                   |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|-------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/AM/BV-010                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                   |                   |
+| <b>TP label</b>          | Status Reporter Object for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                   |                   |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-10472] |                   |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | StatReporter28; M      | StatReporter29; R | StatReporter30; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | StatReporter31; O      | StatReporter32; R | StatReporter33; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | StatReporter34; R      | StatReporter35; R | StatReporter36; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | StatReporter37; R      | StatReporter38; R | StatReporter39; R |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | StatReporter40; R      | StatReporter41; O | StatReporter42; O |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | StatReporter43; M      |                   |                   |
+| <b>Test purpose</b>      | Check that:<br>Status Reporter Enumeration Object contains the attributes specified for Extended Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                   |                   |
+| <b>Applicability</b>     | C_AG_OXP_168 AND C_AG_OXP_181 AND C_AG_AM_008 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                        |                   |                   |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                   |                   |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                   |                   |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG receives an association request from the PHD under test.</li> <li>2. The simulated PHG responds with a result = accepted-unknown-config.</li> <li>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.</li> <li>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.</li> <li>5. Once the PHD under test sends the tested configuration, check the Status Reporter object.</li> <li>6. The Status Reporter object contents shall be:</li> </ol> |                        |                   |                   |
+
+- a. Mandatory attribute Type
+  - attribute-id = MDC\_ATTR\_ID\_TYPE
+  - attribute-type = TYPE
+  - attribute-value = MDC\_PART\_PHD\_AI, MDC\_AI\_MED\_STATUS
+- 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>
+- c. 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>
+- d. IF Optional 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>
+- e. 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>
+- f. 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>
+- 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 = <Not relevant for this test>
+- 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 = <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 Not recommended attribute Relative-Time-Stamp is present
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_STAMP_REL</li> <li><input type="checkbox"/> attribute-type = RelativeTime (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> k. IF Not recommended attribute Measure-Active-Period is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_MSMT_ACTIVE</li> <li><input type="checkbox"/> attribute-type = FLOAT-Type (INT-U32)</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> l. IF Not recommended attribute Enum-Observed-Value-Simple-OID is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_SIM_OID</li> <li><input type="checkbox"/> attribute-type = OID-Type (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length = 2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> m. IF Not recommended attribute Enum-Observed-Value-Partition is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id= MDC_ATTR_ENUM_OBS_VAL_PART</li> <li><input type="checkbox"/> attribute-type = NomPartition (INT-U16)</li> <li><input type="checkbox"/> attribute-value.length=2 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> n. IF Optional attribute Context-Key is present <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_CONTEXT_KEY</li> <li><input type="checkbox"/> attribute-type = OCTET STRING(Size(8))</li> <li><input type="checkbox"/> attribute-value.length = 10 bytes</li> <li><input type="checkbox"/> attribute-value = Check against PIXIT( I_AG_OXP_009)</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|                          |                                                                                                                                                                                                               |                        |                    |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/AM/BV-011                                                                                                                                                                                    |                        |                    |
+| <b>TP label</b>          | Adherence Monitor PM-Store object                                                                                                                                                                             |                        |                    |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                   | [ISO/IEEE 11073-10472] |                    |
+|                          | <b>Testable items</b>                                                                                                                                                                                         | MM_PMStoreAttr1; M     | MM_PMStoreAttr2; M |
+|                          |                                                                                                                                                                                                               | MM_PMStoreAttr4; M     | MM_PMStoreAttr3; M |
+| <b>Test purpose</b>      | Check that:<br>PM-Store object contains the specified attributes.                                                                                                                                             |                        |                    |
+| <b>Applicability</b>     | C_AG_OXP_168 AND C_AG_OXP_041 AND C_AG_OXP_000                                                                                                                                                                |                        |                    |
+| <b>Other PICS</b>        |                                                                                                                                                                                                               |                        |                    |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                          |                        |                    |
+| <b>Test procedure</b>    | 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.<br>2. The PHD response must contain: |                        |                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>a. Mandatory Storage-Capacity-Count is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STORE_CAPAC_CNT</li> <li><input type="checkbox"/> attribute-type = INT-U32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> <p>b. Mandatory Storage-Usage-Count is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_METRIC_STORE_USAGE_CNT</li> <li><input type="checkbox"/> attribute-type = INT-U32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> <p>c. Mandatory attribute PM-Store-Label</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_PM_STORE_LABEL_STRING</li> <li><input type="checkbox"/> attribute-type = OCTET STRING</li> <li><input type="checkbox"/> attribute-value.length &lt;= 255 octets</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this Test&gt;</li> </ul> <p>d. IF Not recommended attribute Sample-Period is present</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_PD_SAMP</li> <li><input type="checkbox"/> attribute-type = RelativeTime</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant in this test&gt;</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked values are as specified in the test procedure.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                     |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/AM/BV-012                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                     |
+| <b>TP label</b>          | Adherence Monitor Segment-Data-Event size                                                                                                                                                                                                                                                                                                                                                                                                  |                        |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                | [ISO/IEEE 11073-10472] |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                      | MM_PMStoreEvent3; M    | MM_PMStoreEvent4; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>Segment-Data-Event report size shall be no larger than 1024 octets.</p> <p>[AND]</p> <p>A PM-segment containing data in excess of this size shall transfer its data using multiple Segment-Data-Event reports as described in IEEE Std 11073-20601</p>                                                                                                                                                               |                        |                     |
+| <b>Applicability</b>     | C_AG_OXP_168 AND C_AG_OXP_041 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                             |                        |                     |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                     |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                       |                        |                     |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHG issues a Get-Segment-Info with SegmSelection set to all-segments.</li> <li>2. The simulated PHG sends a request for the PM-Segment Data to one of the PM-Segments that contains data: <ol style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> </ul> </li> </ol> </li> </ol> |                        |                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_ACT_SEG_TRIG_XFER</li> <li><input type="checkbox"/> TrigSegmDataXferReq = &lt;Instance number of the selected PM-Segment that contains the data&gt;</li> </ul> <p>3. The PHD issues an action response:</p> <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> </ul> </li> <li>b. Action = MDC_ACT_SEG_TRIG_XFER <ul style="list-style-type: none"> <li><input type="checkbox"/> TrigSegmDataXferRsp = &lt;Same Instance number&gt;   tsxr-successful (0x00 0x00)</li> </ul> </li> </ul> <p>4. The PHD under test starts Data transfer:</p> <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Invoke   CfmEventReport</li> <li><input type="checkbox"/> Action = MDC_NOTI_SEGMENT_DATA</li> <li><input type="checkbox"/> SegmentDataEvent</li> </ul> </li> </ul> <p>5. The simulated PHG response to transferred data APDU's:</p> <ul style="list-style-type: none"> <li>a. Data APDU <ul style="list-style-type: none"> <li><input type="checkbox"/> Type = Invoke   Confirmed Action,,</li> <li><input type="checkbox"/> HANDLE = obj-handle</li> <li><input type="checkbox"/> Action = MDC_NOTI_SEGMENT_DATA</li> <li><input type="checkbox"/> SegmentDataResult</li> <li><input type="checkbox"/> PHD under test repeats steps 3 and 4 until all the data is transferred</li> </ul> </li> </ul> |
+| <b>Pass/Fail criteria</b> | The size of the Segment-Data-Event (MDC_NOTI_SEGMENT_DATA) cannot exceed 1024 octets.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+|                      |                                                                                                                                                                                                                                                                                                                                                                                           |                        |                    |
+|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|
+| <b>TP Id</b>         | TP/PLT/PHD/CLASS/AM/BV-013                                                                                                                                                                                                                                                                                                                                                                |                        |                    |
+| <b>TP label</b>      | Adherence Monitor PM-Segment                                                                                                                                                                                                                                                                                                                                                              |                        |                    |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                               | [ISO/IEEE 11073-10472] |                    |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                     | MM_PStoreModel1; M     | MM_PStoreModel2; M |
+| <b>Test purpose</b>  | <p>Check that:</p> <p>For every implemented medication monitor object there shall be at least one corresponding segment present if the PM-store is implemented</p> <p>[AND]</p> <p>Each entry shall include one of the time formats in the segm-entry-header so a PHG can correlate entries across the different segments</p> <p>[AND]</p> <p>PM-Segment has the specified attributes</p> |                        |                    |
+| <b>Applicability</b> | C_AG_OXP_168 AND C_AG_OXP_041 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                            |                        |                    |
+| <b>Other PICS</b>    |                                                                                                                                                                                                                                                                                                                                                                                           |                        |                    |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li data-bbox="443 230 1396 315">1. The simulated PHG shall send a Get-Segment-Info action for a PM-Store object with SegmSelection = all-segments to indicate the PM-Segments attributes of all available PM-Segments.</li> <li data-bbox="443 331 1437 2031">2. The PHD issues a "rors-cmip-confirmed-action" response with the PM-Segment attributes it supports: <ol style="list-style-type: none"> <li data-bbox="491 405 1283 645">a. Mandatory attribute PM-Segment-Entry-Map <ol style="list-style-type: none"> <li data-bbox="587 450 1082 472"><input type="checkbox"/> attribute-id = MDC_ATTR_PM_SEG_MAP</li> <li data-bbox="587 495 1034 517"><input type="checkbox"/> attribute-type = PmSegmentEntryMap</li> <li data-bbox="587 539 1283 645"><input type="checkbox"/> attribute-value = SEQUENCE of <ol style="list-style-type: none"> <li data-bbox="635 577 1273 600">▪ segm-entry-header shall include one of the time formats.</li> <li data-bbox="635 622 1098 645">▪ segm-entry-elem-list: Record this value</li> </ol> </li> </ol> </li> <li data-bbox="491 667 1209 862">b. Mandatory attribute Segment-Label is present <ol style="list-style-type: none"> <li data-bbox="587 712 1209 734"><input type="checkbox"/> attribute-id = MDC_ATTR_PM_SEG_LABEL_STRING</li> <li data-bbox="587 757 978 779"><input type="checkbox"/> attribute-type = OCTET STRING</li> <li data-bbox="587 801 1106 824"><input type="checkbox"/> attribute-value.length = consistent with value</li> <li data-bbox="587 846 1090 862"><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ol> </li> <li data-bbox="491 884 1129 1429">c. Mandatory attribute Segment-Start-Abs-Time is present <ol style="list-style-type: none"> <li data-bbox="587 929 1129 952"><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_START_SEG</li> <li data-bbox="587 974 946 996"><input type="checkbox"/> attribute-type = AbsoluteTime</li> <li data-bbox="587 1019 962 1041"><input type="checkbox"/> attribute-value.length = 8 bytes</li> <li data-bbox="587 1064 882 1429"><input type="checkbox"/> attribute-value = <ol style="list-style-type: none"> <li data-bbox="635 1108 778 1131">▪ century =</li> <li data-bbox="635 1153 778 1176">▪ year ≤ 99</li> <li data-bbox="635 1198 778 1220">▪ month ≤ 12</li> <li data-bbox="635 1243 778 1265">▪ day ≤ 31</li> <li data-bbox="635 1288 778 1310">▪ hour ≤ 24</li> <li data-bbox="635 1332 778 1355">▪ minute ≤ 60</li> <li data-bbox="635 1377 778 1400">▪ second ≤ 60</li> <li data-bbox="635 1422 882 1444">▪ sec-fractions ≤ 100</li> </ol> </li> </ol> </li> <li data-bbox="491 1451 1106 1995">d. Mandatory attribute Segment-End-Abs-Time is present <ol style="list-style-type: none"> <li data-bbox="587 1496 1106 1518"><input type="checkbox"/> attribute-id = MDC_ATTR_TIME_END_SEG</li> <li data-bbox="587 1541 946 1563"><input type="checkbox"/> attribute-type = AbsoluteTime</li> <li data-bbox="587 1585 962 1608"><input type="checkbox"/> attribute-value.length = 8 bytes</li> <li data-bbox="587 1630 882 1995"><input type="checkbox"/> attribute-value = <ol style="list-style-type: none"> <li data-bbox="635 1675 778 1697">▪ century =</li> <li data-bbox="635 1720 778 1742">▪ year ≤ 99</li> <li data-bbox="635 1765 778 1787">▪ month ≤ 12</li> <li data-bbox="635 1809 778 1832">▪ day ≤ 31</li> <li data-bbox="635 1854 778 1877">▪ hour ≤ 24</li> <li data-bbox="635 1899 778 1921">▪ minute ≤ 60</li> <li data-bbox="635 1944 778 1966">▪ second ≤ 60</li> <li data-bbox="635 1989 882 2011">▪ sec-fractions ≤ 100</li> </ol> </li> </ol> </li> <li data-bbox="491 2018 1106 2040">e. Mandatory attribute Segment-Usage-Count is present</li> </ol> </li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><input type="checkbox"/> attribute-id = MDC_ATTR_SEG_USAGE_CNT</li> <li><input type="checkbox"/> attribute-type = INT-U32</li> <li><input type="checkbox"/> attribute-value.length = 4 bytes</li> <li><input type="checkbox"/> attribute-value = &lt;Not relevant for this test&gt;</li> </ul> <p>3. Repeat step 1 and 2 for every PM-Store object</p> |
+| <b>Pass/Fail criteria</b> | All checked attributes are as specified in the test procedure.<br>There is at least one segment for every implemented object.                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                        |                   |                   |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|-------------------|
+| <b>TP Id</b>             | TP/PLT/PHD/CLASS/AM/BV-014                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                   |                   |
+| <b>TP label</b>          | Association Adherence Monitor PHD                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |                   |                   |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [ISO/IEEE 11073-10472] |                   |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | MM_AssocReq1 ; M       | MM_AssocReq2 ; M  | MM_AssocReq3 ; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | MM_AssocReq4 ; M       | MM_AssocReq5 ; M  | MM_AssocReq6 ; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | MM_AssocReq7 ; M       | MM_AssocReq8 ; M  | MM_AssocReq9 ; M  |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | MM_AssocReq10 ; M      | MM_AssocReq11 ; M | MM_AssocReq12 ; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | MM_MDSMethod4 ; M      |                   |                   |
+| <b>Test purpose</b>      | Check that:<br>During the association procedure, Medication Monitor PHD sends the correct association request to the simulated PHG                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                        |                   |                   |
+| <b>Applicability</b>     | C_AG_OXP_168 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                        |                   |                   |
+| <b>Other PICS</b>        | C_AG_OXP_002, C_AG_OXP_017                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                        |                   |                   |
+| <b>Initial condition</b> | The simulated PHG and the PHD under test are in the Unassociated state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                        |                   |                   |
+| <b>Test procedure</b>    | <p>1. The PHD sends a message to associate to the simulated PHG, the expected fields sent by the PHD are:</p> <ul style="list-style-type: none"> <li>a. APDU Type <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = AarqApdu</li> <li><input type="checkbox"/> field-length =2 bytes</li> <li><input type="checkbox"/> field-value =0xE2 0x00.</li> </ul> </li> <li>b. assoc-version <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = AssociationVersion</li> <li><input type="checkbox"/> field-length =BITS-32</li> <li><input type="checkbox"/> field- value=0x80 0x00 0x00 0x00</li> </ul> </li> <li>c. data-proto-id <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = DataProtoId(INT-U16)</li> <li><input type="checkbox"/> field-length =2 bytes</li> <li><input type="checkbox"/> field- value=0x50 0x79 (20601)</li> </ul> </li> <li>d. protocol-version <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = Protocol Version</li> </ul> </li> </ul> |                        |                   |                   |
+
+- 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 not 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.
+
+##### j. dev-config-id
+
+- field- type = ConfigId(INT-U16)
+- field-length = 2 bytes
+- field- value =
+  - <0x1C20 or 0x1C21 or 0x1C22 or 0x1C23> 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 only Medication Monitor specialization →Only 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
+
+|                           |                                                                                                                                                                                                                                                                                                                |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <input type="checkbox"/> field.value = 0x01<br>m. data-req-init-manager-count (DataReqModeCapab) <ul style="list-style-type: none"> <li><input type="checkbox"/> field- type = INT-U8</li> <li><input type="checkbox"/> field-length = 2 bytes</li> <li><input type="checkbox"/> field.value = 0x00</li> </ul> |
+| <b>Pass/Fail criteria</b> | All checked attributes have proper values.                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|
+| <b>TP Id</b>              | TP/PLT/PHD/CLASS/AM/BV-015                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                        |
+| <b>TP label</b>           | Get Request Adherence Monitor PHD                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                        |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [ISO/IEEE 11073-10472] |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | MM_OperProc4; M        |
+| <b>Test purpose</b>       | Check that:<br><br>It is not required for a medication monitor PHD to support this capability (Get MDS object using an Attribute-Id-List). If this capability is not implemented, the medication monitor PHD shall respond with a "Remote Operation Error Result" (roer) service message (see ISO/IEEE Std 11073-20601) with the error-value field set to no-such-action (9).                                                                                                                                                                                                                                                          |                        |
+| <b>Applicability</b>      | C_AG_OXP_168 AND C_AG_OXP_000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                        |
+| <b>Other PICS</b>         | C_AG_OXP_100                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                        |
+| <b>Initial condition</b>  | The simulated PHG and the PHD under test are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                        |
+| <b>Test procedure</b>     | 1. The simulated PHG issues a "Remote Operation Invoke   Get" command with <ol style="list-style-type: none"> <li>a. Obj-handle set to 0 (to request for MDS object)</li> <li>b. attribute-id-list.count=1 and a single AVA_Type MDC_ATTR_DEV_CONFIG_ID (0X0A 0X44) to retrieve the mandatory "Dev-Configuration-Id" attribute</li> </ol> 2. The PHD under test responds with: <ul style="list-style-type: none"> <li>• IF C_AG_OXP_100 THEN: with a "rors-cmip-get" service message which contains the "Dev-Configuration-Id"</li> <li>• ELSE: with a "roer" service message with error-value set to no-such-an-action (9)</li> </ul> |                        |
+| <b>Pass/Fail criteria</b> | In step 2 the PHD properly sends the requested attribute or the error (no-such-action) message.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                        |
+
+|                 |                                               |                                                               |
+|-----------------|-----------------------------------------------|---------------------------------------------------------------|
+| <b>TP Id</b>    | TP/PLT/PHD/CLASS/AM/BV-016                    |                                                               |
+| <b>TP label</b> | Operating State. PHG to PHD Maximum APDU Size |                                                               |
+| <b>Coverage</b> | <b>Spec</b>                                   | [ISO/IEEE 11073-20601-2015A] and [ISO/IEEE 11073-20601-2016C] |
+|                 | <b>Testable items</b>                         | CommonCharac 3; M                                             |
+|                 | <b>Spec</b>                                   | [ISO/IEEE 11073-10472]                                        |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                 |                 |  |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------|--|
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | MM_ComModel1; M | MM_ComModel2; M |  |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>The total size of the response do not exceed of the maximum APDU size established by the specialization</p> <p>[AND]</p> <p>A medication monitor PHD implementing only this device specialization shall not transmit any APDU larger than Ntx and shall be capable of receiving any APDU up to a size of Nrx. For this standard, Ntx shall be 1024 octets and Nrx shall be 64 octets.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                 |                 |  |
+| <b>Applicability</b>      | C_AG_OXP_000 AND C_AG_OXP_168                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                 |                 |  |
+| <b>Other PICS</b>         | C_AG_OXP_041, C_AG_OXP_100                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                 |                 |  |
+| <b>Initial condition</b>  | The simulated PHG and the PHD are in the Operating state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                 |                 |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHG issues a "Remote Operation Invoke   Get" command with: <ol style="list-style-type: none"> <li>a. Obj-handle set to 0 (to request for an MDS object)</li> <li>b. attribute-id-list.count = 23</li> <li>c. attribute-id-list: (MDC_ATTR_ID_MODEL, MDC_ATTR_SYS_ID, MDC_ATTR_DEV_CONFIG_ID) repeated 7 times followed by an additional MDC_ATTR_ID_MODEL and MDC_ATTR_SYS_ID</li> </ol> </li> <li>2. Check the response of the PHD.</li> <li>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.</li> <li>4. Check the response of the PHD.</li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                 |                 |  |
+| <b>Pass/Fail criteria</b> | <ul style="list-style-type: none"> <li>• 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.</li> <li>• 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): <ul style="list-style-type: none"> <li>▪ Pulse oximeter → 9216 octets</li> <li>▪ Weighing scales → 896 octets</li> <li>▪ Glucose meter → 5120 octets or 64512 octets if the PHD supports PM-Store</li> <li>▪ Blood pressure → 896 octets</li> <li>▪ Thermometer → 896 octets</li> <li>▪ Independent activity hub → 5120 octets</li> <li>▪ Cardiovascular → 64512 octets or 6624 octets if PHD under test only supports Step Counter Profile</li> <li>▪ Strength → 64512 octets:</li> <li>▪ Adherence monitor → 1024 octets</li> <li>▪ Peak flow → 2030 octets</li> <li>▪ Body composition analyser → 7730 octets</li> <li>▪ Basic ECG/Simple ECG → 7168 octets or 64512 octets if the PHD supports PM-Store</li> <li>▪ Basic ECG/Heart rate → 1280 octets or 64512 octets if the PHD supports PM-Store</li> <li>▪ International normalized ratio → 896 octets or 64512 if the PHD supports PM-Store</li> </ul> </li> </ul> |                 |                 |  |
+
+|              |                                                                                                                                                                                                                     |
+|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|              | <ul style="list-style-type: none"><li>• In the case where it responds with a roer, the reason must not be protocol-violation (23)</li><li>• In step 4, the PHD must respond with a rors-cmip-get message.</li></ul> |
+| <b>Notes</b> |                                                                                                                                                                                                                     |
+
+## 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.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-PHG PICS & PIXIT] Personal Health Gateway DG2016 PICS and PIXIT excel sheet v1.9.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-TI] Continua DG2016 PHD Testable items excel sheet v1.8.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-TCRL] Test Case Reference List\_DG2016\_v1.11.  
+<http://handle.itu.int/11.1002/2000/12067>
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.846-201911-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e4643b8e895116ee86e6e0623108f89da910164e
--- /dev/null
+++ b/marked/H/T-REC-H.846-201911-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f6a763af46bba8aaeb76701c137af2d1bdec60c145e3cd2cfe52bdcfb01acdb8
+size 3635
diff --git a/marked/H/T-REC-H.847-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.847-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bd7c24e83d75a6b1baa7fb4210f76345166390c9
--- /dev/null
+++ b/marked/H/T-REC-H.847-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5866ab521163bd4f911ae6e27d0a1cf1f491c665e9b87b7d7076098a143f4bff
+size 3944
diff --git a/marked/H/T-REC-H.848-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.848-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a713c9d3a38a0b0ded423795a4e6fb9889f1cf7e
--- /dev/null
+++ b/marked/H/T-REC-H.848-201704-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5ac2e2cf21c51a63df761924b63730e9562d1cb9210d5b37a96e62976d508279
+size 4125
diff --git a/marked/H/T-REC-H.850-201911-I_PDF-E/raw.md b/marked/H/T-REC-H.850-201911-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..7bfd5a97d83ee05a8240856d0f4bc8cd0a1a0477
--- /dev/null
+++ b/marked/H/T-REC-H.850-201911-I_PDF-E/raw.md
@@ -0,0 +1,655 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.850**
+
+(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 10: Transcoding for Bluetooth Low Energy:  
+Personal Health Gateway – General  
+requirements**
+
+Recommendation ITU-T H.850
+
+# 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        |
+| <b>Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN)</b> | <b>H.820–H.859</b> |
+| 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
+
+### Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 10: Transcoding for Bluetooth Low Energy: Personal Health Gateway – General requirements
+
+## Summary
+
+Recommendation ITU-T H.850 provides a test suite structure (TSS) and the test purposes (TP) for the general requirements when transcoding 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 is a transposition of clause 3.2 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.
+
+This Recommendation was originally approved as a single part, but due to its large size it was split at publication time into eight sub-parts for easier use, maintenance and expandability:
+
+- ITU-T H.850 with the general requirements;
+- ITU-T H.850.1 with thermometer PHD requirements;
+- ITU-T H.850.2 with blood pressure PHD requirements;
+- ITU-T H.850.3 with heart rate PHD requirements;
+- ITU-T H.850.4 with glucose meter PHD requirements;
+- ITU-T H.850.5 with weighing scales PHD requirements;
+- ITU-T H.850.6 with pulse oximeter PHD requirements;
+- ITU-T H.850.7 with continuous glucose monitoring PHD requirements.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T H.850    | 2015-01-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/12279">11.1002/1000/12279</a> |
+| 2.0     | ITU-T H.850    | 2016-07-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12957">11.1002/1000/12957</a> |
+| 3.0     | ITU-T H.850    | 2017-04-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/13239">11.1002/1000/13239</a> |
+| 4.0     | ITU-T H.850    | 2019-11-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/14120">11.1002/1000/14120</a> |
+
+## 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, personal health gateway, touch area network.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.1 – Whitepaper General requirements (GEN) ..... | 11 |
+|     | Bibliography.....                                            | 19 |
+
+**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.2 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]: <ul style="list-style-type: none"> <li>Adds glucose meter BLE</li> <li>Adds BLE SSP support</li> <li>Adds NFC new transport</li> <li>Adds INR device specialization</li> </ul> |
+| 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: <ul style="list-style-type: none"> <li>"Other PICS" row has been added</li> </ul>                                                                          |
+| 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]: <ul style="list-style-type: none"> <li>Adds WS/BCA BLE device specialization</li> <li>Adds SABTE IEEE device specialization</li> </ul>                                         |
+| 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]: <ul style="list-style-type: none"> <li>Adds PLX BLE device specialization</li> <li>Adds PLX CGM device specialization</li> </ul>                                                 |
+| 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 baseline and corrects minor typos.                                                                                                                                                                                                                    |
+| 1.8     | 2018-10-17 | It uses version 1.7 as a baseline and adds updates due to the inclusion of CGM & PLX BLE profile test cases.                                                                                                                                                                                                                                              |
+
+# Recommendation ITU-T H.850
+
+## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 10: Transcoding for Bluetooth Low Energy: Personal Health Gateway – General requirements
+
+# 1 Scope
+
+The scope of this Recommendation<sup>1</sup> 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 10 – General requirements.
+
+- 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
+
+---
+
+<sup>1</sup> 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.  
+<https://www.iso.org/standard/54331.html> with  
+<https://www.iso.org/standard/63972.html>
+
+- [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.  
+<https://www.iso.org/standard/66717.html> with  
+<https://www.iso.org/standard/71886.html>
+- [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.1 (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 <http://handle.itu.int/11.1002/2000/12067>.
+
+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>/<DUT>/<GR>/<SGR>/<XX> – <NNN>). It is specified according to the naming convention defined below:
+  - Each test purpose identifier is introduced by the prefix "TP".
+  - <TT>: 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)
+  - <DUT>: This is the device under test.
+    - PHD: Personal Health Device
+    - PHG: Personal Health Gateway
+  - <GR>: This identifies a group of test cases.
+  - <SGR>: This identifies a subgroup of test cases.
+  - <XX>: This identifies the type of testing.
+    - BV: Valid behaviour test
+    - BI: Invalid behaviour test
+  - <NNN>: 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.1 – Whitepaper General requirements (GEN)
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                         |  |  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--|--|
+| <b>TP Id</b>              | TP/LP-PAN/PHG/PHDTW/GEN/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                         |  |  |
+| <b>TP label</b>           | Whitepaper. MDS Object - Handle Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |  |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [b-Bluetooth PHDT v1.3] |  |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Common MDS 1; O         |  |  |
+| <b>Test purpose</b>       | Check that:<br>Personal Health Gateway (PHG) does not include MDS Object – Handle Attribute in transcoder output<br>[OR]<br>If PHG includes MDS Object – Handle attribute in transcoder output, then its value shall be set to 0                                                                                                                                                                                                                                                                                                                                                                                                                                         |                         |  |  |
+| <b>Applicability</b>      | C_MAN_BLE_000 AND C_MAN_BLE_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                         |  |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                         |  |  |
+| <b>Initial condition</b>  | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                         |  |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>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).</li> <li>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).</li> <li>3. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.</li> <li>4. Check in PHG transcoder output for the MDS object – Handle attribute</li> </ol> |                         |  |  |
+| <b>Pass/Fail criteria</b> | In step 4, the MDS object – Handle attribute is not present; however, if it is present, its value is 0.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                         |  |  |
+| <b>Notes</b>              | Possible values in typical points of observation after transcoder output are:<br>a) IEEE 11073 Objects and Attributes<br>Handle attribute is not present, or if it is present then:<br><ul style="list-style-type: none"> <li><input type="checkbox"/> Object: MDS object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_HANDLE (2337)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: 0</li> </ul> b) WAN PCD-01 message<br>PCD-01 message does not include segments with a Handle attribute value.                                                                                           |                         |  |  |
+
+|                      |                                                                                                                                                                                                                                                                                         |                         |                  |                  |
+|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------|------------------|
+| <b>TP Id</b>         | TP/LP-PAN/PHG/PHDTW/GEN/BV-001                                                                                                                                                                                                                                                          |                         |                  |                  |
+| <b>TP label</b>      | Whitepaper. MDS Object - System-Model Attribute                                                                                                                                                                                                                                         |                         |                  |                  |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                                                                             | [b-Bluetooth PHDT v1.3] |                  |                  |
+|                      | <b>Testable items</b>                                                                                                                                                                                                                                                                   | Common MDS 2; M         | String Conv 1; M | String Conv 2; M |
+|                      |                                                                                                                                                                                                                                                                                         | MDS Conv 1; M           | MDS Conv 2; M    | MDS Conv 3; M    |
+| <b>Test purpose</b>  | Check that:<br>PHG transcodes Model Number String and Manufacturer Name String characteristics into MDS Object – System-Model attribute<br>[AND]<br>PHG transcodes odd length string by appending a zero (0x00) byte to the end of the string, and incrementing the string length field |                         |                  |                  |
+| <b>Applicability</b> | C_MAN_BLE_000 AND C_MAN_BLE_002                                                                                                                                                                                                                                                         |                         |                  |                  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Initial condition</b>  | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>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).</li> <li>2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are: <ol style="list-style-type: none"> <li>a. Manufacturer name string (0x2A29) <ul style="list-style-type: none"> <li>• Format: utf8s</li> <li>• Value: AT4wireless (string char, odd length)</li> </ul> </li> <li>b. Model number string (0x2A24) <ul style="list-style-type: none"> <li>• Format: utf8s</li> <li>• Value: Mod.12 (string char, even length)</li> </ul> </li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the Manufacturer name string and Model number string characteristics.</li> <li>5. The simulated PHD sends the measurement to the PHG under test.</li> <li>6. Check in PHG transcoder output for the MDS object – System-Model attribute.</li> </ol> |
+| <b>Pass/Fail criteria</b> | In step 6, the MDS object – System-Model attribute is present, its value matches with BLE Manufacturer name string and Model number string characteristics values, and character strings have even lengths (i.e., transcoder appends padding byte 0x00 to odd length strings).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes</b>              | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>System-Model attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: MDS object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_MODEL (2344)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE {manufacturer (OCTET STRING), model-number (OCTET STRING)}. OCTET STRING is restricted to printable ASCII characters (0x20 – 0x7E) and even length (padding with 0x00 character)</li> <li><input type="checkbox"/> Attribute-value: <ol style="list-style-type: none"> <li>i. manufacturer: AT4wireless (string char) or 00 0C 41 54 34 77 69 72 65 6C 65 73 73 00 (hex) [Note that 0x00 0x0C is the string length]</li> <li>ii. model-number: Mod.12 (string char) or 00 06 4d 6f 64 2e 31 32 (hex) [Note that 0x00 0x06 is the string length]</li> </ol> </li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes two segments like these with a System-Model attribute value (check OBX-5 in both segments):</p> <p>OBX ? ST 531969^MDC_ID_MODEL_NUMBER^MDC 1.0.0.a AT4wireless     R</p> <p>OBX ? ST 531970^MDC_ID_MODEL_MANUFACTURER^MDC 1.0.0.b Mod.12     R</p>                                 |
+
+|                     |                                                                                                         |                         |               |               |
+|---------------------|---------------------------------------------------------------------------------------------------------|-------------------------|---------------|---------------|
+| <b>TP Id</b>        | TP/LP-PAN/PHG/PHDTW/GEN/BV-002                                                                          |                         |               |               |
+| <b>TP label</b>     | Whitepaper. MDS Object - System-Id Attribute                                                            |                         |               |               |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                             | [b-Bluetooth PHDT v1.3] |               |               |
+|                     | <b>Testable items</b>                                                                                   | Common MDS 3; M         | MDS Conv 4; M | MDS Conv 5; M |
+| <b>Test purpose</b> | <p>Check that:</p> <p>PHG transcodes System ID characteristic into MDS Object – System-Id attribute</p> |                         |               |               |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Applicability</b>      | C_MAN_BLE_000 AND C_MAN_BLE_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Initial condition</b>  | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>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).</li> <li>2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is: <ol style="list-style-type: none"> <li>a. System ID (0x2A23) <ul style="list-style-type: none"> <li>• Format: uint40, uint24 (64 bits)</li> <li>• Value: 11 22 33 44 AA BB CC DD</li> </ul> </li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read System ID characteristics.</li> <li>5. The simulated PHD sends the measurement to the PHG under test.</li> <li>6. Check in PHG transcoder output for the MDS object – System-Id attribute</li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Pass/Fail criteria</b> | In step 6, the MDS object – System-Id attribute is present and its value matches the BLE System ID characteristic value.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>System-Id attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: MDS object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_SYS_ID (2436)</li> <li><input type="checkbox"/> Attribute-type: OCTET STRING restricted to EUI-64</li> <li><input type="checkbox"/> Attribute-value: 11 22 33 44 AA BB CC DD (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>If the simulated PHD implements a Thermometer profile then the PCD-01 message includes a segment like this with the System-Id attribute value (check OBX-18):</p> <pre>OBX[?][528392^MDC_DEV_SPEC_PROFILE_TEMP^MDC 1     X      122334455AABBCCDD^EUI-64</pre> <p>If the simulated PHD implements a Blood pressure profile then the PCD-01 message includes a segment like this with the System-Id attribute value (check OBX-18):</p> <pre>OBX[?][528391^MDC_DEV_SPEC_PROFILE_BP^MDC 1     X      122334455AABBCCDD^EUI-64</pre> <p>If the simulated PHD implements a Heart rate profile then the PCD-01 message includes a segment like this with the System-Id attribute value (check OBX-18):</p> <pre>OBX[?][528384^MDC_DEV_SPEC_PROFILE_HYDRA^MDC 1     X      122334455AABBCCDD^EUI-64</pre> <p>If the simulated PHD implements a Glucose profile then the PCD-01 message includes a segment like this with the System-Id attribute value (check OBX-18):</p> <pre>OBX[?][528384^MDC_DEV_SPEC_PROFILE_GLUCOSE^MDC 1     X      122334455AABBCCDD^EUI-64</pre> <p>If simulated PHD implements a Weight Scale Profile then PCD-01 message includes a segment like this with System-Id attribute value (check OBX-18):</p> <pre>OBX[?][528399^MDC_DEV_SPEC_PROFILE_SCALE^MDC 1     X      122334455AABBCCDD^EUI-64</pre> <p>If simulated PHD implements a Body Composition Profile then PCD-01 message includes a segment like this with System-Id attribute value (check OBX-18):</p> <pre>OBX[?][528404^MDC_DEV_SPEC_PROFILE_BCA^MDC 1     X     </pre> |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <p>122334455AABBCCDD^EUI-64</p> <p>If simulated PHD implements a Pulse Oximeter Profile then PCD-01 message includes two segments like this with System-Id attribute value (check OBX-18):</p> <p>OBX n  528384^MDC_DEV_SPEC_PROFILE_HYDRA^MDC 1     X     <br/>122334455AABBCCDD^EUI-64.</p> <p>OBX m NM 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC 1.0.0.a 528388^<br/>MDC_DEV_SPEC_PROFILE_PULS_OXIM^MDC     R</p> <p>If simulated PHD implements a Continuous Glucose Monitoring Profile then PCD-01 message includes two segments like these with System-Id attribute value (check OBX-18):</p> <p>OBX n  528384^MDC_DEV_SPEC_PROFILE_HYDRA^MDC 1     X     <br/>122334455AABBCCDD^EUI-64</p> <p>OBX m NM 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC 1.0.0.a 528410^<br/>MDC_DEV_SPEC_PROFILE_CGM^MDC     R</p> |
+|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                         |                  |                  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------|------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/GEN/BV-003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                         |                  |                  |
+| <b>TP label</b>          | Whitepaper. MDS Object - Production-Specification Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                         |                  |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [b-Bluetooth PHDT v1.3] |                  |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | Common MDS 5; M         | String Conv 1; M | String Conv 2; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | MDS Conv 6; M           | MDS Conv 7; M    |                  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG transcodes Serial Number String, Hardware Revision String, Software Revision String and Firmware Revision String characteristics into MDS Object – Production-Specification attribute</p> <p>[AND]</p> <p>PHG transcodes odd length string by appending a zero (0x00) byte to the end of the string, and incrementing the string length field</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                         |                  |                  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                         |                  |                  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                         |                  |                  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                         |                  |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>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).</li> <li>2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are: <ol style="list-style-type: none"> <li>a. Serial number string (0x2A25) <ul style="list-style-type: none"> <li>• Format: utf8s</li> <li>• Value: SN 2468 (string char, odd length)</li> </ul> </li> <li>b. Hardware revision string (0x2A27) <ul style="list-style-type: none"> <li>• Format: utf8s</li> <li>• Value: HW 13579 (string char, even length)</li> </ul> </li> <li>c. Software revision string (0x2A28) <ul style="list-style-type: none"> <li>• Format: utf8s</li> <li>• Value: SW new-vers (string char, odd length)</li> </ul> </li> <li>d. Firmware revision string (0x2A26) <ul style="list-style-type: none"> <li>• Format: utf8s</li> <li>• Value: FW v1.23 (string char, even length)</li> </ul> </li> </ol> </li> <li>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).</li> </ol> |                         |                  |                  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the Serial number string, Hardware revision string, Software revision string and Firmware revision string characteristics.</p> <p>5. The simulated PHD sends the measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output for the MDS object – Production-Specification attribute</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Pass/Fail criteria</b> | In step 6, the MDS object – Production-Specification attribute is present, its value matches with the BLE Serial number string, Hardware revision string, Software revision string and Firmware revision string characteristics values, and character strings have even lengths (i.e., transcoder appends padding byte 0x00 to odd length strings).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Production-Specification attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: MDS object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_PROD_SPECN (2349)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE OF [{spec-type (INT-U16), component-id (PrivateOid), prod-spec (OCTET STRING)}, {...}]. OCTET STRING is restricted to printable ASCII characters (0x20 – 0x7E) and even length (padding with 0x00 character)</li> <li><input type="checkbox"/> Attribute-value: (note that elements order may be different) <ul style="list-style-type: none"> <li>i. Element: <ul style="list-style-type: none"> <li>• spec-type: 1 (dec)</li> <li>• component-id: 0 (dec)</li> <li>• prod-spec: SN 2468 (string char) or 00 08 53 4E 20 32 34 36 38 00 (hex) [Note that 0x00 0x08 is the string length]</li> </ul> </li> <li>ii. Element: <ul style="list-style-type: none"> <li>• spec-type: 3 (dec)</li> <li>• component-id: 0 (dec)</li> <li>• prod-spec: HW 13579 (string char) or 00 08 48 57 20 31 33 35 37 39 (hex) [Note that 0x00 0x08 is the string length]</li> </ul> </li> <li>iii. Element: <ul style="list-style-type: none"> <li>• spec-type: 4 (dec)</li> <li>• component-id: 0 (dec)</li> <li>• prod-spec: SW new-vers (string char) or 00 0C 53 57 20 6E 65 77 2D 76 65 72 73 00 (hex) [Note that 0x00 0x0C is the string length]</li> </ul> </li> <li>iv. Element: <ul style="list-style-type: none"> <li>• spec-type: 5 (dec)</li> <li>• component-id: 0 (dec)</li> <li>• prod-spec: FW v1.23 (string char) or 00 08 46 57 20 76 31 2E 32 33 (hex) [Note that 0x00 0x08 is the string length]</li> </ul> </li> </ul> </li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes four segments like these with Production-Specification attribute value (check OBX-5 in four segments):</p> <p>OBX[? ST 531972^MDC_ID_PROD_SPEC_SERIAL^MDC 1.0.0.a SN 2468     R</p> <p>OBX[? ST 531974^MDC_ID_PROD_SPEC_HW^MDC 1.0.0.b HW 13579     R</p> <p>OBX[? ST 531975^MDC_ID_PROD_SPEC_SW^MDC 1.0.0.c SW new-vers     R</p> <p>OBX[? ST 531976^MDC_ID_PROD_SPEC_FW^MDC 1.0.0.d FW v1.23     R</p> |
+
+|                 |                                                  |
+|-----------------|--------------------------------------------------|
+| <b>TP Id</b>    | TP/LP-PAN/PHG/PHDTW/GEN/BV-004                   |
+| <b>TP label</b> | Whitepaper. MDS Object - Date-and-Time Attribute |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                         |                     |                     |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------|---------------------|
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [b-Bluetooth PHDT v1.3] |                     |                     |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Common MDS 6; M         | Date-Time Conv 2; M | Date-Time Conv 3; M |
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Date-Time Conv 4; M     | Date-Time Conv 5; M | MDS Conv 8; M       |
+| <b>Test purpose</b>       | Check that:<br>PHG transcodes Date Time characteristic into MDS Object – Date-and-Time attribute<br>[AND]<br>PHG transcodes the Bluetooth Date Time characteristic format to Absolute Time format<br>[AND]<br>The fraction of seconds in Absolute Time at transcoder output is 0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                         |                     |                     |
+| <b>Applicability</b>      | C_MAN_BLE_000 AND C_MAN_BLE_002 AND (C_MAN_BLE_001 OR C_MAN_BLE_003<br>OR C_MAN_BLE_007 OR C_MAN_BLE_017 OR C_MAN_BLE_018 OR C_MAN_BLE_040)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                         |                     |                     |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                         |                     |                     |
+| <b>Initial condition</b>  | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                         |                     |                     |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>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).</li> <li>2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is: <ol style="list-style-type: none"> <li>a. Date Time (0x2A08) <br/>Value: April 8th, 2012, 19:45:05 <ol style="list-style-type: none"> <li>i. Field: Year <ul style="list-style-type: none"> <li>• Format: uint16</li> <li>• Value: 2012</li> </ul> </li> <li>ii. Field: Month <ul style="list-style-type: none"> <li>• Format: uint8</li> <li>• Value: 4</li> </ul> </li> <li>iii. Field: Day <ul style="list-style-type: none"> <li>• Format: uint8</li> <li>• Value: 8</li> </ul> </li> <li>iv. Field: Hours <ul style="list-style-type: none"> <li>• Format: uint8</li> <li>• Value: 19</li> </ul> </li> <li>v. Field: Minutes <ul style="list-style-type: none"> <li>• Format: uint8</li> <li>• Value: 45</li> </ul> </li> <li>vi. Field: Seconds <ul style="list-style-type: none"> <li>• Format: uint8</li> <li>• Value: 5</li> </ul> </li> </ol> </li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the Date Time characteristic.</li> <li>5. The simulated PHD sends the measurement to the PHG under test.</li> <li>6. Check in PHG transcoder output for the MDS object – Date-and-Time attribute</li> </ol> |                         |                     |                     |
+| <b>Pass/Fail criteria</b> | In step 6, the MDS object – Date-and-Time attribute is present, its value matches with Date-and-Time characteristic values and the fraction of seconds is set to 0.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                         |                     |                     |
+
+|              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Notes</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Date-and-Time attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: MDS object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_TIME_ABS (2439)</li> <li><input type="checkbox"/> 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)</li> <li><input type="checkbox"/> Attribute-value: <ul style="list-style-type: none"> <li>• century: 20 (hex) or 32 (dec)</li> <li>• year: 12 (hex) or 18 (dec)</li> <li>• month: 04 (hex) or 4 (dec)</li> <li>• day: 08 (hex) or 8 (dec)</li> <li>• hour: 19 (hex) or 25 (dec)</li> <li>• minute: 45 (hex) or 69 (dec)</li> <li>• second: 05 (hex) or 5 (dec)</li> <li>• sec-fractions: 00 (hex) or 0 (dec)</li> </ul> </li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with a Type attribute value (check OBX-5):</p> <p style="padding-left: 40px;">OBX ? DTM 67975^MDC_ATTR_TIME_ABS^MDC 1.0.0.a <br/>20120408194505+0000     R  20120408194505+0000</p> |
+|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                         |  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/GEN/BV-006                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                         |  |
+| <b>TP label</b>          | Whitepaper. MDS Object - Battery-Level Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                         |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [b-Bluetooth PHDT v1.3] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Common MDS 12; M        |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG transcodes Battery Level characteristic into MDS Object – Battery-Level attribute</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                         |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_039                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                         |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                         |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>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).</li> <li>2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is: <ol style="list-style-type: none"> <li>a. Battery level (0x2A19) <ul style="list-style-type: none"> <li>• Format: uint8</li> <li>• Value: 75</li> </ul> </li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the Battery level characteristic.</li> <li>5. The simulated PHD sends the measurement to the PHG under test.</li> <li>6. Check in PHG transcoder output for the MDS object – Battery-Level attribute.</li> </ol> |                         |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Pass/Fail criteria</b> | In step 6, the MDS object – Battery-Level attribute is present and its value matches with the BLE Battery-Level characteristic value.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Battery-Level attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: MDS object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_VAL_BATT_CHARGE (2460)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: 75</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with a Battery-Level attribute value (check OBX-5):</p> <pre>OBX ? NM 67996^MDC_ATTR_VAL_BATT_CHARGE^MDC 1.0.0.a 75 262688^ MDC_DIM_PERCENT^MDC   R  [current_date_time]</pre> |
+
+# 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-ETSI SR 001 262] ETSI SR 001 262 v1.8.1 (2003), *ETSI drafting rules*.  
+<https://docbox.etsi.org/MTS/MTS/10-PromotionalMaterial/MBS-20111118/Referenced%20Documents/Drafting%20Rules.pdf>
+- [b-PHD PICS & PIXIT] PHD PICS and PIXIT Test Tool v7.0.2.0 – Excel sheet v1.13.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-PHG PICS & PIXIT] PHG PICS and PIXIT Test Tool v7.0.2.0 – Excel sheet v1.11.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-TI] PHD Testable items. Test Tool v7.0.2.0 – Excel sheet v1.10.  
+<http://handle.itu.int/11.1002/2000/12067>
+
+
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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.1-202008-I_PDF-E/raw.md b/marked/H/T-REC-H.850.1-202008-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c5cb9581f0c7e4e598f3d806191251b62a1365a4
--- /dev/null
+++ b/marked/H/T-REC-H.850.1-202008-I_PDF-E/raw.md
@@ -0,0 +1,1049 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.850.1**
+
+(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 10A: Transcoding for Bluetooth Low  
+Energy: Personal Health Gateway –  
+Thermometer**
+
+Recommendation ITU-T H.850.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        |
+| <b>Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN)</b> | <b>H.820–H.859</b> |
+| 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.1
+
+# Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 10A: Transcoding for Bluetooth Low Energy: Personal Health Gateway – Thermometer
+
+## Summary
+
+Recommendation ITU-T H.850.1 provides a test suite structure (TSS) and the test purposes (TP) for the transcoding of thermometer data by personal health gateways in the Personal Health Devices (PHD) interface of thermometer device 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.1 is a transposition of clause 3.3 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.1  | 2017-04-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/13354">11.1002/1000/13354</a> |
+| 2.0     | ITU-T H.850.1  | 2020-08-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/14345">11.1002/1000/14345</a> |
+
+## Keywords
+
+Bluetooth Low Energy (BLE), Bluetooth Generic Attribute Profile, Conformance testing, Continua Design Guidelines, data format transcoding, e-health, IEEE 11073-20601, ITU-T H.810, Personal Health Gateway, Personal Health Devices interface, personal area network, personal connected health devices, touch area network, thermometer.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.2 – Whitepaper Thermometer requirements (TH) ..... | 10 |
+|     | 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.3 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]: <ul style="list-style-type: none"> <li>• Adds glucose meter BLE</li> <li>• Adds BLE SSP support</li> <li>• Adds NFC new transport</li> <li>• Adds INR device specialization</li> </ul> |
+| 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: <ul style="list-style-type: none"> <li>• "Other PICS" row has been added</li> </ul>                                                                                |
+| 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]: <ul style="list-style-type: none"> <li>• Adds WS/BCA BLE device specialization</li> <li>• Adds SABTE IEEE device specialization</li> </ul>                                             |
+| 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]: <ul style="list-style-type: none"> <li>• Adds PLX BLE device specialization</li> <li>• Adds PLX CGM device specialization</li> </ul>                                                     |
+| 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.1
+
+### Conformance of ITU-T H.810 personal health devices: Personal Health Devices interface Part 10A: Transcoding for Bluetooth Low Energy: Personal Health Gateway – Thermometer
+
+# 1 Scope
+
+The scope of this Recommendation<sup>1</sup> 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 10A.
+
+- 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
+
+---
+
+<sup>1</sup> 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 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.  
+<https://www.iso.org/standard/54331.html> with  
+<https://www.iso.org/standard/63972.html>
+- [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.  
+<https://www.iso.org/standard/66717.html> with  
+<https://www.iso.org/standard/71886.html>
+
+- [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.2 (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 <http://handle.itu.int/11.1002/2000/12067>.
+
+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 ATest 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>/<DUT>/<GR>/<SGR>/<XX> – <NNN>). It is specified according to the naming convention defined below:
+  - Each test purpose identifier is introduced by the prefix "TP".
+  - <TT>: 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)
+  - <DUT>: This is the device under test.
+    - PHD: Personal Health Device
+    - PHG: Personal Health Gateway
+  - <GR>: This identifies a group of test cases.
+  - <SGR>: This identifies a subgroup of test cases.
+  - <XX>: This identifies the type of testing.
+    - BV: Valid behaviour test
+    - BI: Invalid behaviour test
+  - <NNN>: 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.2 – Whitepaper Thermometer requirements (TH)
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |  |  |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--|--|
+| <b>TP Id</b>              | TP/LP-PAN/PHG/PHDTW/TH/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                         |  |  |
+| <b>TP label</b>           | Whitepaper. Thermometer MDS Object - System-Type Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                         |  |  |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [b-Bluetooth PHDT v1.3] |  |  |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | TH Specific MDS 1; M    |  |  |
+| <b>Test purpose</b>       | Check that:<br>PHG does not include MDS Object – System-Type attribute in transcoder output.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                         |  |  |
+| <b>Applicability</b>      | C_MAN_BLE_000 AND C_MAN_BLE_001 AND C_MAN_BLE_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                         |  |  |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |  |  |
+| <b>Initial condition</b>  | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                         |  |  |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>The simulated PHD is configured with a Thermometer profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).</li> <li>When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.</li> <li>Check in PHG transcoder output for the MDS object – System-Type attribute.</li> </ol> |                         |  |  |
+| <b>Pass/Fail criteria</b> | In step 4, the MDS object – System-Type attribute is not present.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                         |  |  |
+| <b>Notes</b>              | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes<br/>System-Type attribute is not present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: MDS object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_SYS_TYPE (2438)</li> <li><input type="checkbox"/> Attribute-type: TYPE</li> <li><input type="checkbox"/> Attribute-value: &lt;NOT PRESENT&gt;</li> </ul> <p>b) WAN PCD-01 message<br/>PCD-01 message does not include segments with a System-Type attribute value (67974^MDC_ATTR_SYS_TYPE^MDC).</p>                    |                         |  |  |
+
+|                          |                                                                                                                                                                                                                                      |                         |  |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/TH/BV-001                                                                                                                                                                                                        |                         |  |  |
+| <b>TP label</b>          | Whitepaper. Thermometer MDS Object - Dev-Configuration-Id Attribute                                                                                                                                                                  |                         |  |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                          | [b-Bluetooth PHDT v1.3] |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                | TH Specific MDS 2; M    |  |  |
+| <b>Test purpose</b>      | Check that:<br>PHG includes MDS Object – Dev-Configuration-Id attribute in transcoder output.<br>[AND]<br>Dev-Configuration-Id value is set to any value in range of 0x4000 to 0x7FFF (Extended Configuration)                       |                         |  |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_001 AND C_MAN_BLE_002                                                                                                                                                                                    |                         |  |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                      |                         |  |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                   |                         |  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHD is configured with a Thermometer profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> </ol> |                         |  |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ol style="list-style-type: none"> <li>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).</li> <li>3. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.</li> <li>4. Check in PHG transcoder output for the MDS object – Dev-Configuration-Id attribute</li> </ol>                                                                                                                                                                                                                                                                              |
+| <b>Pass/Fail Criteria</b> | In step 4, the MDS object – Dev-Configuration-Id attribute is present and its value is inside the range 0x4000 - 0x7FFF.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Dev-Configuration-Id attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: MDS object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_DEV_CONFIG_ID (2628)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: Any value inside the range 16384 - 32767 (dec) or 0x4000 – 0x7FFF (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>According to Continua DG, the Dev-Configuration-Id shall not be transmitted in the PCD-01 message; therefore it is not possible to check this attribute.</p> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                            |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|
+| <b>TP Id</b>              | TP/LP-PAN/PHG/PHDTW/TH/BV-002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                                            |
+| <b>TP label</b>           | Whitepaper. Thermometer MDS Object - System-Type-Spec-List Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                            |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [b-Bluetooth PHDT v1.3]                    |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Common MDS 15; M      TH Specific MDS 3; M |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>PHG includes MDS Object – System-Type-Spec-List attribute in transcoder output.</p> <p>[AND]</p> <p>System-Type-Spec-List is set to (MDC_DEV_SPEC_PROFILE_TEMP, Version 1)</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                            |
+| <b>Applicability</b>      | C_MAN_BLE_000 AND C_MAN_BLE_001 AND C_MAN_BLE_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                            |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                            |
+| <b>Initial condition</b>  | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                                            |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Thermometer profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>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).</li> <li>3. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.</li> <li>4. Check in PHG transcoder output for the MDS object – System-Type-Spec-List attribute</li> </ol> |                                            |
+| <b>Pass/Fail criteria</b> | In step 4, the MDS object – System-Type-Spec-List attribute is present and its value is (MDC_DEV_SPEC_PROFILE_TEMP, Version 1).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                            |
+| <b>Notes</b>              | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>System-Type-Spec-List attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: MDS object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_SYS_TYPE_SPEC_LIST (2650)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE OF [{type (INT-U16), version (INT-U16)}]</li> <li><input type="checkbox"/> Attribute-value:</li> </ul>                                                                                                                                         |                                            |
+
+|           |                                                                                                                                                                                                                                                                                                                                                                                                                |
+|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <p>b)</p> | <ul style="list-style-type: none"> <li>type: MDC_DEV_SPEC_PROFILE_TEMP or 4104 (dec) or 10 08 (hex)</li> <li>version: 1 (dec) or 00 01 (hex)</li> </ul> <p>WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with a System-Type-Spec-List attribute value (check OBX-5):</p> <p>OBX ? NM 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC 1.0.0.a 528392^<br/>MDC_DEV_SPEC_PROFILE_TEMP^MDC     R</p> |
+|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                         |                      |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/TH/BV-003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                         |                      |  |
+| <b>TP label</b>          | Whitepaper. MDS Object - Reg-Cert-Data-List Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                         |                      |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [b-Bluetooth PHDT v1.3] |                      |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Common MDS 14; M        | Regulatory Conv 1; M |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG transcodes IEEE 11073-20601 Regulatory Certification Data List characteristic into MDS Object – Reg-Cert-Data-List attribute</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                         |                      |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_001 AND C_MAN_BLE_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                         |                      |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                         |                      |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                         |                      |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHD is configured with a Thermometer profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is: <ol style="list-style-type: none"> <li>IEEE 11073-20601 [ISO/IEEE 11073-20601A] Regulatory Certification Data List (0x2A2A) <ul style="list-style-type: none"> <li>Format: reg-cert-data-list (opaque structure)</li> <li>Value: 00 02 00 12 02 01 00 08 08 00 00 01 00 02 80 08 02 02 00 02 80 00 (hex) <ol style="list-style-type: none"> <li>Element: <ul style="list-style-type: none"> <li>auth-body-and-struc-type: <ul style="list-style-type: none"> <li>- auth-body: 02 (hex) auth-body-continua(2)</li> <li>- auth-body-struc-type: 01 (hex). continua-version-struct(1)</li> </ul> </li> <li>auth-body-data: <ul style="list-style-type: none"> <li>- major-IG-version: 08 (hex)</li> <li>- minor-IG-version: 00 (hex)</li> <li>- certified-devices: 80 08 (hex). BLE Thermometer</li> </ul> </li> </ul> </li> <li>Element: <ul style="list-style-type: none"> <li>auth-body-and-struc-type: <ul style="list-style-type: none"> <li>- auth-body: 02 (hex). auth-body-continua(2)</li> <li>- auth-body-struc-type: 02 (hex). continua-reg-struct(2)</li> </ul> </li> <li>auth-body-data: <ul style="list-style-type: none"> <li>- regulation-bit-field: 80 00 (hex). Unregulated device</li> </ul> </li> </ul> </li> </ol> </li> </ul> </li> </ol> </li> <li>The PHG under test initiates a discovery process (Scanning state). It discovers the simulated PHD and it starts a pairing process with the simulated PHD.</li> <li>When the pairing has been completed (Connection state), force the PHG under test to read the IEEE 11073-20601 Regulatory Certification Data List characteristic.</li> </ol> |                         |                      |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>5. The simulated PHD sends the measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output for the MDS object – Reg-Cert-Data-List attribute</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Pass/Fail criteria</b> | 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.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Notes</b>              | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Reg-Cert-Data-List attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: MDS object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_REG_CERT_DATA_LIST (2635)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE OF {auth-body-and-struc-type, auth-body-data}, {...}</li> <li><input type="checkbox"/> Attribute-value: 00 02 00 12 02 01 00 08 08 00 00 01 00 02 80 08 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] <ul style="list-style-type: none"> <li>i. Reg-Cert-Data Element: <ul style="list-style-type: none"> <li>• auth-body-and-struc-type: <ul style="list-style-type: none"> <li>- auth-body: 02 (hex) auth-body-continua(2)</li> <li>- auth-body-struc-type: 01 (hex). continua-version-struct(1)</li> </ul> </li> <li>• auth-body-data: <ul style="list-style-type: none"> <li>- major-IG-version: 08 (hex)</li> <li>- minor-IG-version: 00 (hex)</li> <li>- certified-devices: 80 08 (hex). BLE Thermometer</li> </ul> </li> </ul> </li> <li>ii. Reg-Cert-Data Element: <ul style="list-style-type: none"> <li>• auth-body-and-struc-type: <ul style="list-style-type: none"> <li>- auth-body: 02 (hex). auth-body-continua(2)</li> <li>- auth-body-struc-type: 02 (hex). continua-reg-struct(2)</li> </ul> </li> <li>• auth-body-data: <ul style="list-style-type: none"> <li>- regulation-bit-field: 80 00 (hex). Unregulated device</li> </ul> </li> </ul> </li> </ul> </li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes five segments like these with Reg-Cert-Data-List attribute value (check OBX-5 in five segments):</p> <pre>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 32776     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</pre> |
+
+|                     |                                                                    |                         |  |
+|---------------------|--------------------------------------------------------------------|-------------------------|--|
+| <b>TP Id</b>        | TP/LP-PAN/PHG/PHDTW/TH/BV-004                                      |                         |  |
+| <b>TP label</b>     | Whitepaper. Thermometer Body Temperature Object - Handle Attribute |                         |  |
+| <b>Coverage</b>     | <b>Spec</b>                                                        | [b-Bluetooth PHDT v1.3] |  |
+|                     | <b>Testable items</b>                                              | TH Numeric 1; O         |  |
+| <b>Test purpose</b> | Check that:                                                        |                         |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | PHG does not include Body Temperature Object – Handle Attribute in transcoder output [OR]<br>If PHG includes Body Temperature Object – Handle attribute in transcoder output, then its value shall be different than 0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Applicability</b>      | C_MAN_BLE_000 AND C_MAN_BLE_001 AND C_MAN_BLE_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Initial condition</b>  | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Thermometer profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is: <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0010 (MSB → LSB). Temperature measurement value in units of Celsius, Time Stamp field is included and Temperature Type field is not included</li> </ul> </li> <li>ii. Field: Temperature Measurement Value (Celsius) <ul style="list-style-type: none"> <li>• Format: FLOAT</li> <li>• Value: Not relevant</li> </ul> </li> <li>iii. Field: Temperature Measurement Value (Fahrenheit) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not relevant</li> </ul> </li> <li>v. Field: Temperature Type <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.</li> <li>5. Check in PHG transcoder output for the Body temperature object – Handle attribute</li> </ol> |
+| <b>Pass/Fail criteria</b> | In step 5, the Body temperature object – Handle attribute is not present; however, if it is present then its value is different to 0.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes</b>              | <p>Possible values in typical points of observation after transcoder output are:</p> <ol style="list-style-type: none"> <li>a) IEEE 11073 Objects and Attributes<br/>Handle attribute is not present, or if it is present then: <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Body temperature numeric object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_HANDLE (2337)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: Any value other than 0</li> </ul> </li> <li>b) WAN PCD-01 message<br/>PCD-01 message does not include segments with a Handle attribute value.</li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |                 |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------|
+| <b>TP Id</b>              | TP/LP-PAN/PHG/PHDTW/TH/BV-005                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                         |                 |
+| <b>TP label</b>           | Whitepaper. Body Temperature Object - Type and Metric-Id Attributes 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                         |                 |
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [b-Bluetooth PHDT v1.3] |                 |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | TH Numeric 2; M         | TH Numeric 3; M |
+| <b>Test purpose</b>       | <p>Check that:</p> <p>PHG includes Body Temperature Object – Type attribute in transcoder output.</p> <p>[AND]</p> <p>Type is set to {MDC_PART_SCADA, MDC_TEMP_BODY}</p> <p>[AND]</p> <p>IF Temperature Type field of Temperature Measurement characteristic is not present and Temperature Type characteristic is not present too THEN Body Temperature Object – Metric-Id attribute is set to MDC_TEMP_BODY</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                         |                 |
+| <b>Applicability</b>      | C_MAN_BLE_000 AND C_MAN_BLE_001 AND C_MAN_BLE_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                         |                 |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |                 |
+| <b>Initial condition</b>  | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                         |                 |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Thermometer profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are: <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0010 (MSB → LSB). Temperature Type field is not included</li> </ul> </li> <li>ii. Field: Temperature Measurement Value (Celsius) <ul style="list-style-type: none"> <li>• Format: FLOAT</li> <li>• Value: Not relevant</li> </ul> </li> <li>iii. Field: Temperature Measurement Value (Fahrenheit) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not relevant</li> </ul> </li> <li>v. Field: Temperature Type <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. Temperature type (0x2A1D): This characteristic is not present</li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.</li> <li>5. Check in PHG transcoder output for the Body temperature object – Type and Metric-Id attributes</li> </ol> |                         |                 |
+| <b>Pass/Fail criteria</b> | <p>In step 5, the Body temperature object – Type attribute is present and its value is {MDC_PART_SCADA, MDC_TEMP_BODY}.</p> <p>In step 5, the Body temperature object – Metric-Id attribute is present and its value is MDC_TEMP_BODY.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                         |                 |
+| <b>Notes</b>              | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                         |                 |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <p>Type attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Body temperature object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_TYPE (2351)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}</li> <li><input type="checkbox"/> Attribute-value: <ul style="list-style-type: none"> <li>• partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)</li> <li>• code: MDC_TEMP_BODY or 19292 (dec) or 4B 4C (hex)</li> </ul> </li> </ul> <p>Metric-Id attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Body temperature object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_PHYSIO (2347)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: MDC_TEMP_BODY or 19292 (dec) or 4B 4C (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):</p> <pre>OBX[?] NM 150364^MDC_TEMP_BODY^MDC 1.0.0.a 35.6 268192^ MDC_DIM_DEGC^MDC   R   current_date_time</pre> |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                         |                 |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/TH/BV-006                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |                 |
+| <b>TP label</b>          | Whitepaper. Body Temperature Object - Type and Metric-Id Attributes 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                         |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [b-Bluetooth PHDT v1.3] |                 |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | TH Numeric 2; M         | TH Numeric 3; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Body Temperature Object – Type attribute in transcoder output.</p> <p>[AND]</p> <p>Type is set to {MDC_PART_SCADA, MDC_TEMP_BODY}</p> <p>[AND]</p> <p>IF Temperature Type field of Temperature Measurement characteristic is present THEN PHG transcodes this field into Body Temperature Object –Metric-Id attribute</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                         |                 |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_001 AND C_MAN_BLE_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                         |                 |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                         |                 |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                         |                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Thermometer profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are: <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0110 (MSB → LSB). Temperature Type field is included</li> </ul> </li> <li>ii. Field: Temperature Measurement Value (Celsius) <ul style="list-style-type: none"> <li>• Format: FLOAT</li> <li>• Value: Not relevant</li> </ul> </li> <li>iii. Field: Temperature Measurement Value (Fahrenheit)</li> </ol> </li> </ol> </li> </ol> |                         |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>iv. Field: Time Stamp</p> <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not relevant</li> </ul> <p>v. Field: Temperature Type</p> <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: Several values are checked in this test case</li> </ul> <p>b. Temperature type (0x2A1D): This characteristic is not present.</p> <ol style="list-style-type: none"> <li>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).</li> <li>4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the field Temperature Type set to Armpit (0x01).</li> <li>5. Check in PHG transcoder output for the Body temperature object – Type and Metric-Id attributes.</li> <li>6. The simulated PHD sends the measurement to the PHG under test with the field Temperature Type set to Body (general) (0x02).</li> <li>7. Check in PHG transcoder output for the Body temperature object – Type and Metric-Id attributes.</li> <li>8. The simulated PHD sends the measurement to the PHG under test with field Temperature Type set to Ear (usually earlobe) (0x03).</li> <li>9. Check in PHG transcoder output for the Body temperature object – Type and Metric-Id attributes.</li> <li>10. The simulated PHD sends the measurement to the PHG under test with field Temperature Type set to Finger (0x04).</li> <li>11. Check in PHG transcoder output for the Body temperature object – Type and Metric-Id attributes.</li> <li>12. The simulated PHD sends the measurement to the PHG under test with field Temperature Type set to Gastro-intestinal tract (0x05).</li> <li>13. Check in PHG transcoder output for the Body temperature object – Type and Metric-Id attributes.</li> <li>14. The simulated PHD sends the measurement to the PHG under test with field Temperature Type set to Mouth (0x06).</li> <li>15. Check in PHG transcoder output for the Body temperature object – Type and Metric-Id attributes.</li> <li>16. The simulated PHD sends the measurement to the PHG under test with field Temperature Type set to Rectum (0x07).</li> <li>17. Check in PHG transcoder output for the Body temperature object – Type and Metric-Id attributes.</li> <li>18. The simulated PHD sends the measurement to the PHG under test with field Temperature Type set to Toe (0x08).</li> <li>19. Check in PHG transcoder output for the Body temperature object – Type and Metric-Id attributes.</li> <li>20. The simulated PHD sends the measurement to the PHG under test with field Temperature Type set to Tympanum (ear drum) (0x09).</li> <li>21. Check in PHG transcoder output for the Body temperature object – Type and Metric-Id attributes.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <p>In step 5, the Body temperature object – Type attribute is present and its value is {MDC_PART_SCADA, MDC_TEMP_BODY}, and the Body temperature object – Metric-Id attribute is present and its value is MDC_TEMP_AXILLA.</p> <p>In step 7, the Body temperature object – Type attribute is present and its value is {MDC_PART_SCADA, MDC_TEMP_BODY}, and the Body temperature object – Metric-Id attribute is present and its value is MDC_TEMP_BODY.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|              | <p>In step 9, the Body temperature object – Type attribute is present and its value is {MDC_PART_SCADA, MDC_TEMP_BODY} and Body temperature object – Metric-Id attribute is present and its value is MDC_TEMP_EAR</p> <p>In step 11, the Body temperature object – Type attribute is present and its value is {MDC_PART_SCADA, MDC_TEMP_BODY}, and the Body temperature object – Metric-Id attribute is present and its value is MDC_TEMP_FINGER.</p> <p>In step 13, the Body temperature object – Type attribute is present and its value is {MDC_PART_SCADA, MDC_TEMP_BODY}, and the Body temperature object – Metric-Id attribute is present and its value is MDC_TEMP_GIT.</p> <p>In step 15, the Body temperature object – Type attribute is present and its value is {MDC_PART_SCADA, MDC_TEMP_BODY}, and the Body temperature object – Metric-Id attribute is present and its value is MDC_TEMP_ORAL.</p> <p>In step 17, the Body temperature object – Type attribute is present and its value is {MDC_PART_SCADA, MDC_TEMP_BODY}, and the Body temperature object – Metric-Id attribute is present and its value is MDC_TEMP_RECT.</p> <p>In step 19, the Body temperature object – Type attribute is present and its value is {MDC_PART_SCADA, MDC_TEMP_BODY}, and the Body temperature object – Metric-Id attribute is present and its value is MDC_TEMP_TOE.</p> <p>In step 21, the Body temperature object – Type attribute is present and its value is {MDC_PART_SCADA, MDC_TEMP_BODY}, and the Body temperature object – Metric-Id attribute is present and its value is MDC_TEMP_TYMP.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b> | <p>In step 5, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Type attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Body temperature object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_TYPE (2351)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}</li> <li><input type="checkbox"/> Attribute-value: <ul style="list-style-type: none"> <li>• partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)</li> <li>• code: MDC_TEMP_BODY or 19292 (dec) or 4B 4C (hex)</li> </ul> </li> </ul> <p>Metric-Id attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Body temperature object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_PHYSIO (2347)</li> <li><input type="checkbox"/> Attribute-type: code (INT-U16)</li> <li><input type="checkbox"/> Attribute-value: code: MDC_TEMP_AXILLA or 57380 (dec) or E0 24 (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):</p> <pre>OBX ? NM 188452^MDC_TEMP_AXILLA^MDC 1.0.0.a 35.6  268192^MDC_DIM_DEGC^MDC    R  [current_date_time]</pre> <p>In step 7, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Type attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Body temperature object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_TYPE (2351)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}</li> <li><input type="checkbox"/> Attribute-value: <ul style="list-style-type: none"> <li>• partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)</li> <li>• code: MDC_TEMP_BODY or 19292 (dec) or 4B 4C (hex)</li> </ul> </li> </ul> <p>Metric-Id attribute is present:</p> |
+
+- Object: Body temperature object
+- Attribute-id: MDC\_ATTR\_ID\_PHYSIO (2347)
+- Attribute-type: code (INT-U16)
+- Attribute-value: code: MDC\_TEMP\_BODY or 19292 (dec) or 4B 4C (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):
+
+```
+OBX|?|NM|150364^MDC_TEMP_BODY^MDC|1.0.0.a|35.7|268192^
+MDC_DIM_DEGC^MDC|||R||20120716145210+0000
+```
+
+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: Body temperature 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\_TEMP\_BODY or 19292 (dec) or 4B 4C (hex)
+
+Metric-Id attribute is present:
+
+- Object: Body temperature object
+- Attribute-id: MDC\_ATTR\_ID\_PHYSIO (2347)
+- Attribute-type: code (INT-U16)
+- Attribute-value: code: MDC\_TEMP\_EAR or 57356 (dec) or E0 0C (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):
+
+```
+OBX|?|NM|188428^MDC_TEMP_EAR^MDC|1.0.0.a|35.9|268192^
+MDC_DIM_DEGC^MDC|||R||20120716145310+0000
+```
+
+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: Body temperature 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\_TEMP\_BODY or 19292 (dec) or 4B 4C (hex)
+
+Metric-Id attribute is present:
+
+- Object: Body temperature object
+- Attribute-id: MDC\_ATTR\_ID\_PHYSIO (2347)
+- Attribute-type: code (INT-U16)
+- Attribute-value: code: MDC\_TEMP\_FINGER or 57360 (dec) or E0 10 (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):
+
+OBX|?|NM|188432^MDC\_TEMP\_FINGER^MDC|1.0.0.a|36.1|268192^  
+MDC\_DIM\_DEGC^MDC||||R|||20120716145410+0000
+
+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: Body temperature 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\_TEMP\_BODY or 19292 (dec) or 4B 4C (hex)
+
+Metric-Id attribute is present:
+
+- Object: Body temperature object
+- Attribute-id: MDC\_ATTR\_ID\_PHYSIO (2347)
+- Attribute-type: code (INT-U16)
+- Attribute-value: code: MDC\_TEMP\_GIT or 57384 (dec) or E0 28 (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):
+
+OBX|?|NM|188456^MDC\_TEMP\_GIT^MDC|1.0.0.a|36.3|  
+268192^MDC\_DIM\_DEGC^MDC||||R|||20120716145510+0000
+
+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: Body temperature 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\_TEMP\_BODY or 19292 (dec) or 4B 4C (hex)
+
+Metric-Id attribute is present:
+
+- Object: Body temperature object
+- Attribute-id: MDC\_ATTR\_ID\_PHYSIO (2347)
+- Attribute-type: code (INT-U16)
+- Attribute-value: code: MDC\_TEMP\_ORAL or 57352 (dec) or E0 08 (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):
+
+OBX|?|NM|188424^MDC\_TEMP\_ORAL^MDC|1.0.0.a|36.5|  
+268192^MDC\_DIM\_DEGC^MDC||||R|||20120716145610+0000
+
+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: Body temperature 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\_TEMP\_BODY or 19292 (dec) or 4B 4C (hex)
+
+Metric-Id attribute is present:
+
+- Object: Body temperature object
+- Attribute-id: MDC\_ATTR\_ID\_PHYSIO (2347)
+- Attribute-type: code (INT-U16)
+- Attribute-value: code: MDC\_TEMP\_RECT or 57348 (dec) or E0 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|188420^MDC\_TEMP\_RECT^MDC|1.0.0.a|36.7|  
+268192^MDC\_DIM\_DEGC^MDC||||R||20120716145710+0000
+
+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: Body temperature 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\_TEMP\_BODY or 19292 (dec) or 4B 4C (hex)
+
+Metric-Id attribute is present:
+
+- Object: Body temperature object
+- Attribute-id: MDC\_ATTR\_ID\_PHYSIO (2347)
+- Attribute-type: code (INT-U16)
+- Attribute-value: code: MDC\_TEMP\_TOE or 57376 (dec) or E0 20 (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):
+
+OBX|?|NM|188448^MDC\_TEMP\_TOE^MDC|1.0.0.a|36.9|  
+268192^MDC\_DIM\_DEGC^MDC||||R||20120716145810+0000
+
+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: Body temperature 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\_TEMP\_BODY or 19292 (dec) or 4B 4C (hex)
+
+Metric-Id attribute is present:
+
+- Object: Body temperature object
+- Attribute-id: MDC\_ATTR\_ID\_PHYSIO (2347)
+- Attribute-type: code (INT-U16)
+
+|  |                                                                                                                                                                                                                                                                                                                                            |
+|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <p><input type="checkbox"/> Attribute-value: code: MDC_TEMP_TYMP or 19320 (dec) or 4B 78 (hex)</p> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):</p> <pre>OBX[?] NM 150392^MDC_TEMP_TYMP^MDC 1.0.0.a 37.1  268192^MDC_DIM_DEGC^MDC   R  20120716145910+0000</pre> |
+|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                         |                 |                 |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------|-----------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/TH/BV-007                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                         |                 |                 |
+| <b>TP label</b>          | Whitepaper. Body Temperature Object - Type and Metric-Id Attributes 3                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                         |                 |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [b-Bluetooth PHDT v1.3] |                 |                 |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | TH Numeric 2; M         | TH Numeric 3; M | TH Numeric 4; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Body Temperature Object – Type attribute in transcoder output.</p> <p>[AND]</p> <p>Type is set to {MDC_PART_SCADA, MDC_TEMP_BODY}</p> <p>[AND]</p> <p>IF Temperature Type characteristic is present THEN PHG transcodes this characteristic into Body Temperature Object – Metric-Id attribute</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                         |                 |                 |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_001 AND C_MAN_BLE_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                         |                 |                 |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                         |                 |                 |
+| <b>Initial condition</b> | The PHG under test and the simulated Personal Health Device (PHD) are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                         |                 |                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Thermometer profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are: <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0010 (MSB → LSB). Temperature Type field is not included</li> </ul> </li> <li>ii. Field: Temperature Measurement Value (Celsius) <ul style="list-style-type: none"> <li>• Format: FLOAT</li> <li>• Value: Not relevant</li> </ul> </li> <li>iii. Field: Temperature Measurement Value (Fahrenheit) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not relevant</li> </ul> </li> <li>v. Field: Temperature Type <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. Temperature type (0x2A1D) <ul style="list-style-type: none"> <li>• Type: 8 bit</li> <li>• Value: 0x01 (Armpit)</li> </ul> </li> </ol> </li> <li>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).</li> </ol> |                         |                 |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the Temperature type characteristic.</p> <p>5. The simulated PHD sends the measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output for the Body temperature object – Type and Metric-Id attributes.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Pass/Fail criteria</b> | In step 6, the Body temperature object – Type attribute is present and its value is {MDC_PART_SCADA, MDC_TEMP_BODY}, and the Body temperature object – Metric-Id attribute is present and its value is MDC_TEMP_AXILLA.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Notes</b>              | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Type attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Body temperature object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_TYPE (2351)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}</li> <li><input type="checkbox"/> Attribute-value: <ul style="list-style-type: none"> <li>• partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)</li> <li>• code: MDC_TEMP_BODY or 19292 (dec) or 4B 4C (hex)</li> </ul> </li> </ul> <p>Metric-Id attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Body temperature object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_PHYSIO (2347)</li> <li><input type="checkbox"/> Attribute-type: code (INT-U16)</li> <li><input type="checkbox"/> Attribute-value: code: MDC_TEMP_AXILLA or 57380 (dec) or E0 24 (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with a Type attribute value (check OBX-3):</p> <p style="padding-left: 40px;">OBX ? NM 188452^MDC_TEMP_AXILLA^MDC 1.0.0.a 35.6 268192^MDC_DIM_DEGC^MDC    R   [current_date_time]</p> |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                         |                 |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/TH/BV-008                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                         |                 |
+| <b>TP label</b>          | Whitepaper. Body Temperature Object - Metric-Spec-Small Attribute 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [b-Bluetooth PHDT v1.3] |                 |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | TH Numeric 5; M         | TH Numeric 6; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>When Measurement Interval characteristic is not present then the PHG transcoder sets Body Temperature Object – Metric-Spec-Small attribute to 0xF040 (mss-avail-intermittent, mss-avail-stored-data, mss-upd-aperiodic, mss-msmt-aperiodic, mss-acc-agent-initiated)</p>                                                                                                                                                                                                                                                                                                     |                         |                 |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_001 AND C_MAN_BLE_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                         |                 |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                         |                 |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                         |                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Thermometer profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are: <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                         |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• Value: 0000 0010 (MSB → LSB). Temperature Measurement Value in units of Celsius, Time Stamp field is included and Temperature Type field is not included</li> </ul> <p>ii. Field: Temperature Measurement Value (Celsius)</p> <ul style="list-style-type: none"> <li>• Format: FLOAT</li> <li>• Value: Not relevant</li> </ul> <p>iii. Field: Temperature Measurement Value (Fahrenheit)</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>iv. Field: Time Stamp</p> <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not relevant</li> </ul> <p>v. Field: Temperature Type</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>b. Measurement interval (0x2A21): This characteristic is not present.</p> <p>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).</p> <p>4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test.</p> <p>5. Check in PHG transcoder output for the Body temperature object – Metric-Spec-Small attribute.</p> |
+| <b>Pass/Fail criteria</b> | In step 5, the Body temperature object – Metric-Spec-Small attribute is present and its value is 0xF040.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes</b>              | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Metric-Spec-Small attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Body temperature object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)</li> <li><input type="checkbox"/> Attribute-type: BITS-16</li> <li><input type="checkbox"/> 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</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message does not include segments with a Metric-Spec-Small attribute value.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                               |                         |                 |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/TH/BV-009                                                                                                                                                                                                                                                                                 |                         |                 |
+| <b>TP label</b>          | Whitepaper. Body Temperature Object - Metric-Spec-Small Attribute 2                                                                                                                                                                                                                                           |                         |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                   | [b-Bluetooth PHDT v1.3] |                 |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                         | TH Numeric 5; M         | TH Numeric 6; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>When Measurement Interval characteristic is present and its value is 0 then the PHG transcoder sets Body Temperature Object – Metric-Spec-Small attribute to 0xF040 (mss-avail-intermittent, mss-avail-stored-data, mss-upd-aperiodic, mss-msmt-aperiodic, mss-acc-agent-initiated)</p> |                         |                 |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_001 AND C_MAN_BLE_002                                                                                                                                                                                                                                                             |                         |                 |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                               |                         |                 |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                            |                         |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Thermometer profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are: <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0010 (MSB → LSB). Temperature measurement value in units of Celsius, Time Stamp field is included and Temperature Type field is not included</li> </ul> </li> <li>ii. Field: Temperature Measurement Value (Celsius) <ul style="list-style-type: none"> <li>• Format: FLOAT</li> <li>• Value: Not relevant</li> </ul> </li> <li>iii. Field: Temperature Measurement Value (Fahrenheit) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not relevant</li> </ul> </li> <li>v. Field: Temperature Type <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. Measurement interval (0x2A21) <ul style="list-style-type: none"> <li>• Format: uint16</li> <li>• Value: 0</li> </ul> </li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the Measurement interval characteristic.</li> <li>5. The simulated PHD sends the measurement to the PHG under test.</li> <li>6. Check in PHG transcoder output for the Body temperature object – Metric-Spec-Small attribute.</li> </ol> |
+| <b>Pass/Fail criteria</b> | In step 6, the Body temperature object – Metric-Spec-Small attribute is present and its value is 0xF040.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes</b>              | <p>Possible values in typical points of observation after transcoder output are:</p> <ol style="list-style-type: none"> <li>a) IEEE 11073 Objects and Attributes<br/>Metric-Spec-Small attribute is present: <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Body temperature object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)</li> <li><input type="checkbox"/> Attribute-type: BITS-16</li> <li><input type="checkbox"/> 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</li> </ul> </li> <li>b) WAN PCD-01 message<br/>PCD-01 message does not include segments with a Metric-Spec-Small attribute value.</li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                 |                                                                     |
+|-----------------|---------------------------------------------------------------------|
+| <b>TP Id</b>    | TP/LP-PAN/PHG/PHDTW/TH/BV-010                                       |
+| <b>TP label</b> | Whitepaper. Body Temperature Object - Metric-Spec-Small Attribute 3 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                         |                 |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------|
+| <b>Coverage</b>           | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [b-Bluetooth PHDT v1.3] |                 |
+|                           | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | TH Numeric 5; M         | TH Numeric 6; M |
+| <b>Test purpose</b>       | Check that:<br><br>When Measurement Interval characteristic is present and its value is different than 0 then the PHG transcoder sets Body Temperature Object – Metric-Spec-Small attribute to 0x4040 (mss-avail-stored-data, mss-acc-agent-initiated)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                         |                 |
+| <b>Applicability</b>      | C_MAN_BLE_000 AND C_MAN_BLE_001 AND C_MAN_BLE_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |                 |
+| <b>Other PICS</b>         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                         |                 |
+| <b>Initial condition</b>  | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                         |                 |
+| <b>Test procedure</b>     | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Thermometer profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BLE characteristics. The characteristics of interest for this test case are: <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0010 (MSB → LSB). Temperature measurement value in units of Celsius, Time Stamp field is included and Temperature Type field is not included</li> </ul> </li> <li>ii. Field: Temperature Measurement Value (Celsius) <ul style="list-style-type: none"> <li>• Format: FLOAT</li> <li>• Value: Not relevant</li> </ul> </li> <li>iii. Field: Temperature Measurement Value (Fahrenheit) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not relevant</li> </ul> </li> <li>v. Field: Temperature Type <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. Measurement interval (0x2A21) <ul style="list-style-type: none"> <li>• Format: uint16</li> <li>• Value: 30</li> </ul> </li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the Measurement interval characteristic.</li> <li>5. The simulated PHD sends the measurement to the PHG under test.</li> <li>6. Check in PHG transcoder output for the Body temperature object – Metric-Spec-Small attribute.</li> </ol> |                         |                 |
+| <b>Pass/Fail criteria</b> | In step 6, the Body temperature object – Metric-Spec-Small attribute is present and its value is 0x4040.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                         |                 |
+| <b>Notes</b>              | Possible values in typical points of observation after transcoder output are:<br>a) IEEE 11073 Objects and Attributes<br>Metric-Spec-Small attribute is present:<br><input type="checkbox"/> Object: Body temperature object<br><input type="checkbox"/> Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                         |                 |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                   |
+|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <ul style="list-style-type: none"> <li><input type="checkbox"/> Attribute-type: BITS-16</li> <li><input type="checkbox"/> 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</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message does not include segments with a Metric-Spec-Small attribute value.</p> |
+|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                         |                 |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/TH/BV-011                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                         |                 |
+| <b>TP label</b>          | Whitepaper. Body Temperature Object - Unit-Code Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                         |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [b-Bluetooth PHDT v1.3] |                 |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | TH Numeric 7; M         | TH Numeric 8; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Body Temperature Object – Unit-Code attribute in transcoder output.</p> <p>[AND]</p> <p>IF Temperature Measurement Value (Celsius) field of Temperature Measurement characteristic is present THEN Body Temperature Object – Unit-Code attribute is set to MDC_DIM_DEGC</p> <p>[AND]</p> <p>IF Temperature Measurement Value (Fahrenheit) field of Temperature Measurement characteristic is present THEN Body Temperature Object – Unit-Code attribute is set to MDC_DIM_FAHR</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                         |                 |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_001 AND C_MAN_BLE_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                         |                 |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                         |                 |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                         |                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Thermometer profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is: <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C)</li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value: <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0010 (MSB → LSB). Temperature measurement value in units of Celsius, Time Stamp field is included and Temperature Type field is not included</li> </ul> </li> <li>ii. Field: Temperature Measurement Value (Celsius) <ul style="list-style-type: none"> <li>• Format: FLOAT</li> <li>• Value: 35.6</li> </ul> </li> <li>iii. Field: Temperature Measurement Value (Fahrenheit) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not relevant</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                         |                 |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>v. Field: Temperature Type</p> <ul style="list-style-type: none"> <li>This field is not included</li> </ul> <p>5. Check in PHG transcoder output for the Body temperature object – Unit-Code attribute.</p> <p>6. The simulated PHD sends the measurement to the PHG under test with the following value:</p> <p>a. Temperature measurement (0x2A1C)</p> <p>i. Field: Flags</p> <ul style="list-style-type: none"> <li>Format: 8 bit</li> <li>Value: 0000 0011 (MSB → LSB). Temperature measurement value in units of Fahrenheit, Time Stamp field is included and Temperature Type field is not included</li> </ul> <p>ii. Field: Temperature Measurement Value (Celsius)</p> <ul style="list-style-type: none"> <li>This field is not included</li> </ul> <p>iii. Field: Temperature Measurement Value (Fahrenheit)</p> <ul style="list-style-type: none"> <li>Format: FLOAT</li> <li>Value: 98.1</li> </ul> <p>iv. Field: Time Stamp</p> <ul style="list-style-type: none"> <li>Format: Date and Time</li> <li>Value: Not relevant</li> </ul> <p>v. Field: Temperature Type</p> <ul style="list-style-type: none"> <li>This field is not included</li> </ul> <p>7. Check in PHG transcoder output for the Body temperature object – Unit-Code attribute.</p>                                                                         |
+| <b>Pass/Fail criteria</b> | <p>In step 5, the Body temperature object – Unit-Code attribute is present and its value is MDC_DIM_DEGC.</p> <p>In step 7, the Body temperature object – Unit-Code attribute is present and its value is MDC_DIM_FAHR.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes</b>              | <p>In step 5, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Unit-Code attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Body temperature object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_UNIT_CODE (2454)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: MDC_DIM_DEGC or 6048 (dec) or 17 A0 (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with a Unit-Code attribute value (check OBX-6):</p> <pre>OBX[?][NM][150364^MDC_TEMP_BODY^MDC 1.0.0.a 35.6  268192^MDC_DIM_DEGC^MDC    R  [ current_date_time]</pre> <p>In step 7, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Unit-Code attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Body temperature object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_UNIT_CODE (2454)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: MDC_DIM_FAHR or 4416 (dec) or 11 40 (hex)</li> </ul> <p>b) WAN PCD-01 message</p> |
+
+|  |                                                                                                                                                                                                    |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | PCD-01 message includes a segment like this with a Unit-Code attribute value (check OBX-6):<br>OBX ? NM 150364^MDC_TEMP_BODY^MDC 1.0.0.a 98.1 <br>266560^MDC_DIM_FAHR^MDC   R  20120801095012+0000 |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                         |                     |                     |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------|---------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/TH/BV-012                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                         |                     |                     |
+| <b>TP label</b>          | Whitepaper. Body Temperature Object - Absolute-Time-Stamp Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                         |                     |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [b-Bluetooth PHDT v1.3] |                     |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | TH Numeric 10; M        | Date-Time Conv 2; M | Date-Time Conv 3; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Date-Time Conv 4; M     | Date-Time Conv 5; M |                     |
+| <b>Test purpose</b>      | Check that:<br>PHG transcodes Time Stamp field of Temperature Measurement characteristic into Body Temperature Object - Absolute-Time-Stamp attribute<br>[AND]<br>PHG transcodes the Bluetooth Time Stamp field format to Absolute Time format<br>[AND]<br>The fraction of seconds in Absolute Time at transcoder output is 0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                         |                     |                     |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_001 AND C_MAN_BLE_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                         |                     |                     |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                         |                     |                     |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                         |                     |                     |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Thermometer profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is: <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C)</li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value: <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0010 (MSB → LSB). Temperature measurement value in units of Celsius, Time Stamp field is included and Temperature Type field is not included</li> </ul> </li> <li>ii. Field: Temperature Measurement Value (Celsius) <ul style="list-style-type: none"> <li>• Format: FLOAT</li> <li>• Value: 36.2</li> </ul> </li> <li>iii. Field: Temperature Measurement Value (Fahrenheit) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: August 2nd, 2012, 10:39:27</li> </ul> </li> <li>v. Field: Temperature Type <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                         |                     |                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | 5. Check in PHG transcoder output for the Body temperature object – Absolute-Time-Stamp attribute.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Pass/Fail criteria</b> | In step 5, the Body temperature object – Absolute-Time-Stamp attribute is present, its value matches with the Time Stamp field of the Temperature measurement characteristic and the fraction of seconds is set to 0.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes</b>              | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Absolute-Time-Stamp attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Body temperature object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)</li> <li><input type="checkbox"/> 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)</li> <li><input type="checkbox"/> Attribute-value: <ul style="list-style-type: none"> <li>• century: 20 (hex) or 32 (dec)</li> <li>• year: 12 (hex) or 18 (dec)</li> <li>• month: 08 (hex) or 8 (dec)</li> <li>• day: 02 (hex) or 2 (dec)</li> <li>• hour: 10 (hex) or 16 (dec)</li> <li>• minute: 39 (hex) or 57 (dec)</li> <li>• second: 27 (hex) or 39 (dec)</li> <li>• sec-fractions: 00 (hex) or 0 (dec)</li> </ul> </li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value (check OBX-14):</p> <pre>OBX ? NM 150364^MDC_TEMP_BODY^MDC 1.0.0.a 36.2  268192^MDC_DIM_DEGC^MDC   R  20120802103927+0000</pre> |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                         |                 |  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/TH/BV-013                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                         |                 |  |
+| <b>TP label</b>          | Whitepaper. Body Temperature Object - Simple-Nu-Observed-Value Attribute 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                         |                 |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [b-Bluetooth PHDT v1.3] |                 |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | TH Numeric 11; M        | Float Type 1; C |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG transcodes Temperature Measurement Value field of Temperature Measurement characteristic into Body Temperature Object - Simple-Nu-Observed-Value attribute</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                         |                 |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_001 AND C_MAN_BLE_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                         |                 |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                         |                 |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                         |                 |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Thermometer profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is: <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C)</li> </ol> </li> <li>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).</li> </ol> |                         |                 |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value:</p> <ul style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C) <ul style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0010 (MSB → LSB). Temperature measurement value in units of Celsius, Time Stamp field is included and Temperature Type field is not included</li> </ul> </li> <li>ii. Field: Temperature Measurement Value (Celsius) <ul style="list-style-type: none"> <li>• Format: FLOAT</li> <li>• Value: 35.6</li> </ul> </li> <li>iii. Field: Temperature Measurement Value (Fahrenheit) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not relevant</li> </ul> </li> <li>v. Field: Temperature Type <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> </li> </ul> <p>5. Check in PHG transcoder output for the Body temperature object – Simple-Nu-Observed-Value attribute.</p> <p>6. The simulated PHD sends the measurement to the PHG under test with the following value:</p> <ul style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C) <ul style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0011 (MSB → LSB). Temperature measurement value in units of Fahrenheit, Time Stamp field is included and Temperature Type field is not included</li> </ul> </li> <li>ii. Field: Temperature Measurement Value (Celsius) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Temperature Measurement Value (Fahrenheit) <ul style="list-style-type: none"> <li>• Format: FLOAT</li> <li>• Value: 98.2</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not relevant</li> </ul> </li> <li>v. Field: Temperature Type <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> </li> </ul> <p>7. Check in PHG transcoder output for the Body temperature object – Simple-Nu-Observed-Value attribute.</p> |
+| <b>Pass/Fail criteria</b> | <p>In step 5, the Body temperature object – Simple-Nu-Observed-Value attribute is present and its value matches with the Temperature Measurement Value (Celsius) field of the Temperature measurement characteristic (35.6).</p> <p>In step 7, the Body temperature object – Simple-Nu-Observed-Value attribute is present and its value matches with the Temperature Measurement Value (Fahrenheit) field of the Temperature measurement characteristic (98.2).</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Notes</b>              | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <p style="margin-left: 20px;">Simple-Nu-Observed-Value attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Body temperature object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)</li> <li><input type="checkbox"/> Attribute-type: FLOAT</li> <li><input type="checkbox"/> Attribute-value: FB 36 52 40 (hex) or FC 05 6E A0 (hex) or FD 00 8B 10 (hex) or FE 00 0D E8 (hex) or FF 00 01 64 (hex) or 35.6 (dec)</li> </ul> <p>b) WAN PCD-01 message</p> <p style="margin-left: 20px;">PCD-01 message includes a segment like this with a Simple-Nu-Observed-Value attribute value (check OBX-5):</p> <pre style="margin-left: 40px;">OBX ? NM 150364^MDC_TEMP_BODY^MDC 1.0.0.a 35.6  268192^MDC_DIM_DEGC^MDC    R  [current_date_time]</pre> <p>In step 7, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p style="margin-left: 20px;">Simple-Nu-Observed-Value attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Body temperature object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)</li> <li><input type="checkbox"/> Attribute-type: FLOAT</li> <li><input type="checkbox"/> Attribute-value: FB 95 D7 60 (hex) or FC 0E FB F0 (hex) or FD 01 7F 98 (hex) or FE 00 26 5C (hex) or FF 00 03 D6 (hex) or 98.2 (dec)</li> </ul> <p>b) WAN PCD-01 message</p> <p style="margin-left: 20px;">PCD-01 message includes a segment like this with a Simple-Nu-Observed-Value attribute value (check OBX-5):</p> <pre style="margin-left: 40px;">OBX ? NM 150364^MDC_TEMP_BODY^MDC 1.0.0.a 98.2  266560^MDC_DIM_FAHR^MDC    R  20120802105712+0000</pre> |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                         |                 |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/TH/BV-014                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                         |                 |
+| <b>TP label</b>          | Whitepaper. Body Temperature Object - Simple-Nu-Observed-Value Attribute 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                         |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [b-Bluetooth PHDT v1.3] |                 |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | TH Numeric 11; M        | Float Type 1; C |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG transcodes Temperature Measurement Value field of Temperature Measurement characteristic into Body Temperature Object - Simple-Nu-Observed-Value attribute</p> <p>[AND]</p> <p>PHG assigns the following special values: NaN (0x007FFFFF), NRes (0x00800000), +INFINITY (0x007FFFFFFE) and -INFINITY (0x00800002)</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                         |                 |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_001 AND C_MAN_BLE_002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                         |                 |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                         |                 |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                         |                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Thermometer profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is: <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C)</li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value:</li> </ol> |                         |                 |
+
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0010 (MSB → LSB). Temperature measurement value in units of Celsius, Time Stamp field is included and Temperature Type field is not included</li> </ul> </li> <li>ii. Field: Temperature Measurement Value (Celsius) <ul style="list-style-type: none"> <li>• Format: FLOAT</li> <li>• Value: 35.6</li> </ul> </li> <li>iii. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not relevant</li> </ul> </li> <li>iv. Field: Temperature Type <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>5. Check in PHG transcoder output for the Body temperature object – Simple-Nu-Observed-Value attribute.</li> <li>6. The simulated PHD sends the measurement to the PHG under test with the following value: <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0010 (MSB → LSB). Temperature measurement value in units of Celsius, Time Stamp field is included and Temperature Type field is not included</li> </ul> </li> <li>ii. Field: Temperature Measurement Value (Celsius) <ul style="list-style-type: none"> <li>• Format: FLOAT</li> <li>• Value: 00 7F FF FF (hex). Special value: NaN</li> </ul> </li> <li>iii. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not relevant</li> </ul> </li> <li>iv. Field: Temperature Type <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> <li>7. Check in PHG transcoder output for the Body temperature object – Simple-Nu-Observed-Value attribute.</li> <li>8. The simulated PHD sends the measurement to the PHG under test with the following value: <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0010 (MSB → LSB). Temperature measurement value in units of Celsius, Time Stamp field is included and Temperature Type field is not included</li> </ul> </li> <li>ii. Field: Temperature Measurement Value (Celsius) <ul style="list-style-type: none"> <li>• Format: FLOAT</li> <li>• Value: 00 08 00 00 (hex). Special value: NRes</li> </ul> </li> <li>iii. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> </ul> </li> </ol> </li> </ol> </li> </ol> |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li> <ul style="list-style-type: none"> <li> <ul style="list-style-type: none"> <li> <ul style="list-style-type: none"> <li>• Value: Not relevant</li> </ul> </li> <li>iv. Field: Temperature Type <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> </li> </ul> </li> <li>9. Check in PHG transcoder output for the Body temperature object – Simple-Nu-Observed-Value attribute.</li> <li>10. The simulated PHD sends the measurement to the PHG under test with the following value: <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0010 (MSB → LSB). Temperature measurement value in units of Celsius, Time Stamp field is included and Temperature Type field is not included</li> </ul> </li> <li>ii. Field: Temperature Measurement Value (Celsius) <ul style="list-style-type: none"> <li>• Format: FLOAT</li> <li>• Value: 00 07 FF FE (hex). Special value: +INFINITY</li> </ul> </li> <li>iii. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not relevant</li> </ul> </li> <li>iv. Field: Temperature Type <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> <li>11. Check in PHG transcoder output for the Body temperature object – Simple-Nu-Observed-Value attribute.</li> <li>12. The simulated PHD sends the measurement to the PHG under test with the following value: <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0010 (MSB → LSB). Temperature measurement value in units of Celsius, Time Stamp field is included and Temperature Type field is not included</li> </ul> </li> <li>ii. Field: Temperature Measurement Value (Celsius) <ul style="list-style-type: none"> <li>• Format: FLOAT</li> <li>• Value: 00 08 00 02 (hex). Special value: -INFINITY</li> </ul> </li> <li>iii. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not relevant</li> </ul> </li> <li>iv. Field: Temperature Type <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> <li>13. Check in PHG transcoder output for the Body temperature object – Simple-Nu-Observed-Value attribute.</li> </ul> |
+| <b>Pass/Fail criteria</b> | <p>In step 5, the Body temperature object – Simple-Nu-Observed-Value attribute is present and its value is 35.6.</p> <p>In step 7, the Body temperature object – Simple-Nu-Observed-Value attribute is present and its value is 0x007FFFFF.</p> <p>In step 9, the Body temperature object – Simple-Nu-Observed-Value attribute is present and its value is 0x00800000.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+|              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|              | <p>In step 11, the Body temperature object – Simple-Nu-Observed-Value attribute is present and its value is 0x007FFFFE.</p> <p>In step 13, the Body temperature object – Simple-Nu-Observed-Value attribute is present and its value is 0x00800002.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes</b> | <p>In step 5, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p style="padding-left: 20px;">Simple-Nu-Observed-Value attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Body temperature object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)</li> <li><input type="checkbox"/> Attribute-type: FLOAT</li> <li><input type="checkbox"/> Attribute-value: FB 36 52 40 (hex) or FC 05 6E A0 (hex) or FD 00 8B 10 (hex) or FE 00 0D E8 (hex) or FF 00 01 64 (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p style="padding-left: 20px;">PCD-01 message includes a segment like this with a Simple-Nu-Observed-Value attribute value (check OBX-5):</p> <pre style="padding-left: 40px;">OBX ? NM 150364^MDC_TEMP_BODY^MDC 1.0.0.a 35.6  268192^MDC_DIM_DEGC^MDC    R  [current_date_time]</pre> <p>In step 7, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p style="padding-left: 20px;">Simple-Nu-Observed-Value attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Body temperature object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)</li> <li><input type="checkbox"/> Attribute-type: FLOAT</li> <li><input type="checkbox"/> Attribute-value: 00 7F FF FF (hex) or NaN (note that a decimal value is not allowed)</li> </ul> <p>b) WAN PCD-01 message</p> <p style="padding-left: 20px;">PCD-01 message does not include segments with a Simple-Nu-Observed-Value attribute value (150364^MDC_TEMP_BODY^MDC) because it has a special value and these values are not included in the PCD-01 message.</p> <p>In step 9, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p style="padding-left: 20px;">Simple-Nu-Observed-Value attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Body temperature object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)</li> <li><input type="checkbox"/> Attribute-type: FLOAT</li> <li><input type="checkbox"/> Attribute-value: 00 08 00 00 (hex) or NRes (note that a decimal value is not allowed)</li> </ul> <p>b) WAN PCD-01 message</p> <p style="padding-left: 20px;">PCD-01 message does not include segments with a Simple-Nu-Observed-Value attribute value (150364^MDC_TEMP_BODY^MDC) because it has a special value and these values are not included in the PCD-01 message.</p> <p>In step 11, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p style="padding-left: 20px;">Simple-Nu-Observed-Value attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Body temperature object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)</li> <li><input type="checkbox"/> Attribute-type: FLOAT</li> </ul> |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <p><input type="checkbox"/> Attribute-value: 00 7F FF FE (hex) or +INFINITY (note that a decimal value is not allowed)</p> <p>b) WAN PCD-01 message</p> <p>PCD-01 message does not include segments with a Simple-Nu-Observed-Value attribute value (150364^MDC_TEMP_BODY^MDC) because it has a special value and these values are not included in the PCD-01 message.</p> <p>In step 13, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Simple-Nu-Observed-Value attribute is present:</p> <p><input type="checkbox"/> Object: Body temperature object</p> <p><input type="checkbox"/> Attribute-id: MDC_ATTR_NU_VAL_OBS_SIMP (2646)</p> <p><input type="checkbox"/> Attribute-type: FLOAT</p> <p><input type="checkbox"/> Attribute-value: 00 08 00 02 (hex) or -INFINITY (note that a decimal value is not allowed)</p> <p>b) WAN PCD-01 message</p> <p>PCD-01 message does not include segments with a Simple-Nu-Observed-Value attribute value (150364^MDC_TEMP_BODY^MDC) because it has a special value and these values are not included in the PCD-01 message.</p> |
+|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                         |                     |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/TH/BV-015                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                         |                     |
+| <b>TP label</b>          | Whitepaper. Temperature measurement value                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                         |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [b-Bluetooth PHDT v1.3] |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Float Type 1; C         | Date-Time Conv 1; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | TH Numeric 11; M        | TH Numeric 10; M    |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG processes correctly the Temperature Measurement Value (Celsius), Temperature Measurement Value (Fahrenheit) and Time Stamp fields of Temperature Measurement characteristic</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                         |                     |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_001                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                         |                     |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                         |                     |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                         |                     |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Thermometer profile (device specialization); it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BLE characteristics. The characteristic of interest for this test case is: <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C)</li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), the simulated PHD sends the measurement to the PHG under test with the following value: <ol style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0010 (MSB → LSB). Temperature measurement value in units of Celsius, Time Stamp field is included and Temperature Type field is not included</li> </ul> </li> <li>ii. Field: Temperature Measurement Value (Celsius) <ul style="list-style-type: none"> <li>• Format: FLOAT</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                         |                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• Value: 35.8</li> <li> <ul style="list-style-type: none"> <li>iii. Field: Temperature Measurement Value (Fahrenheit)</li> <li> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iv. Field: Time Stamp</li> <li> <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: August 2nd, 2012, 11:08:25</li> </ul> </li> <li>v. Field: Temperature Type</li> <li> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> </li> </ul> <p>5. Check that the PHG accepts the measurement and decodes its value properly (temperature measurement value, temperature units and time stamp).</p> <p>6. The simulated PHD sends the measurement to the PHG under test with the following value:</p> <ul style="list-style-type: none"> <li>a. Temperature measurement (0x2A1C) <ul style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0011 (MSB → LSB). Temperature measurement value in units of Fahrenheit, Time Stamp field is included and Temperature Type field is not included</li> </ul> </li> <li>ii. Field: Temperature Measurement Value (Celsius) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Temperature Measurement Value (Fahrenheit) <ul style="list-style-type: none"> <li>• Format: FLOAT</li> <li>• Value: 98.2</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: August 2nd, 2012, 11:09:05</li> </ul> </li> <li>v. Field: Temperature Type <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> </li> </ul> <p>7. Check that the PHG accepts the measurement and decodes its value properly (temperature measurement value, temperature units and time stamp).</p> |
+| <b>Pass/Fail criteria</b> | <p>In step 5, the PHG under test shows the following temperature measurement 35.8 °C with the time stamp '2012-08-02 11:08:25'.</p> <p>In step 7, the PHG under test shows the following temperature measurement 97.9F with the time stamp '2012-08-02 11:09:05'.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+## 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*.  
+<https://docbox.etsi.org/MTS/MTS/10-PromotionalMaterial/MBS-20111118/Referenced%20Documents/Drafting%20Rules.pdf>
+- [b-PHD PICS & PIXIT] PHD PICS and PIXIT Test Tool v8.0.0.0 – Excel sheet v1.13.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-PHG PICS & PIXIT] PHG PICS and PIXIT Test Tool v8.0.0.0 – Excel sheet v1.11.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-TI] PHD Testable items. Test Tool v8.0.0.0 – Excel sheet v1.10.  
+<http://handle.itu.int/11.1002/2000/12067>
+
+
+
+## **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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.850.2-202008-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dae48c2379ded5b9f1e128f5132317b798ebeb85
--- /dev/null
+++ b/marked/H/T-REC-H.850.2-202008-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:53c2ef94882ac686e1f8765d417061fa67bba23c2f80e68bff164d97b91be8a5
+size 4144
diff --git a/marked/H/T-REC-H.850.5-202008-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.850.5-202008-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f7bff38b7385414ca4a0881968c632999aaf39a4
--- /dev/null
+++ b/marked/H/T-REC-H.850.5-202008-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e3764245105340b18a282f1a20aa319e8fbbed80c67d35aa8a8fa852c12491af
+size 4150
diff --git a/marked/H/T-REC-H.850.6-202008-I_PDF-E/raw.md b/marked/H/T-REC-H.850.6-202008-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..54ba7b277ecc408abc492d54b76288cdd315fea4
--- /dev/null
+++ b/marked/H/T-REC-H.850.6-202008-I_PDF-E/raw.md
@@ -0,0 +1,3037 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**H.850.6**
+
+(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  
+10F: Transcoding for Bluetooth Low Energy:  
+Personal Health Gateway – Pulse oximeter**
+
+Recommendation ITU-T H.850.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, 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        |
+| <b>Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN)</b> | <b>H.820–H.859</b> |
+| 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.6
+
+### Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 10F: Transcoding for Bluetooth Low Energy: Personal Health Gateway – Pulse oximeter
+
+## Summary
+
+Recommendation ITU-T H.850.6 provides a test suite structure (TSS) and the test purposes (TP) for the transcoding of pulse oximeter 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.6 is a transposition of clause 3.8 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.6  | 2017-04-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/13359">11.1002/1000/13359</a> |
+| 2.0     | ITU-T H.850.6  | 2019-11-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/14121">11.1002/1000/14121</a> |
+| 3.0     | ITU-T H.850.6  | 2020-08-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/14350">11.1002/1000/14350</a> |
+
+## 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, pulse oximeter, touch area network.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.7 – Whitepaper Pulse oximeter requirements (PLX)..... | 11   |
+| Bibliography.....                                                      | 155  |
+
+**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.8 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]: <ul style="list-style-type: none"> <li>• Adds glucose meter BLE</li> <li>• Adds BLE SSP support</li> <li>• Adds NFC new transport</li> <li>• Adds INR device specialization</li> </ul> |
+| 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: <ul style="list-style-type: none"> <li>• "Other PICS" row has been added</li> </ul>                                                                                |
+| 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]: <ul style="list-style-type: none"> <li>• Adds WS/BCA BLE device specialization</li> <li>• Adds SABTE IEEE device specialization</li> </ul>                                             |
+| 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]: <ul style="list-style-type: none"> <li>• Adds PLX BLE device specialization</li> <li>• Adds PLX CGM device specialization</li> </ul>                                                     |
+| 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 PLX 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.6
+
+## Conformance of ITU-T H.810 personal health system: Personal Health Devices interface Part 10F: Transcoding for Bluetooth Low Energy: Personal Health Gateway – Pulse oximeter
+
+## 1 Scope
+
+The scope of this Recommendation<sup>1</sup> 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 10F.
+
+- 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
+
+---
+
+<sup>1</sup> 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.  
+<https://www.iso.org/standard/54331.html> with  
+<https://www.iso.org/standard/63972.html>
+- [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.
+
+<https://www.iso.org/standard/66717.html> with  
+<https://www.iso.org/standard/71886.html>
+
+- [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.7 (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 <http://handle.itu.int/11.1002/2000/12067>.
+
+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>/<DUT>/<GR>/<SGR>/<XX> – <NNN>). It is specified according to the naming convention defined below:
+  - Each test purpose identifier is introduced by the prefix "TP".
+  - <TT>: 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)
+  - <DUT>: This is the device under test.
+    - PHD: Personal Health Device
+    - PHG: Personal Health Gateway
+  - <GR>: This identifies a group of test cases.
+  - <SGR>: This identifies a subgroup of test cases.
+  - <XX>: This identifies the type of testing.
+    - BV: Valid behaviour test
+    - BI: Invalid behaviour test
+  - <NNN>: 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.7 – Whitepaper Pulse oximeter requirements (PLX)
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |  |  |
+|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--|
+| <b>TP Id</b>                                | TP/LP-PAN/PHG/PHDTW/PLX/BV-000                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |  |  |
+| <b>TP label</b>                             | Whitepaper. Pulse Oximeter MDS Object - System-Type Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |  |  |
+| <b>Coverage</b>                             | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [Bluetooth PHDT v1.6] |  |  |
+|                                             | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | PLX Specific MDS 1; M |  |  |
+| <b>Test purpose</b>                         | Check that:<br>PHG does not include MDS object, System-Type attribute in transcoder output.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |  |  |
+| <b>Applicability</b>                        | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                       |  |  |
+| <b>Other PICS</b>                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |  |  |
+| <b>Initial condition</b>                    | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |  |  |
+| <b>Test procedure</b>                       | <ol style="list-style-type: none"> <li>The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>The PHG under test initiates a discovery process (Scanning state), it discovers the simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).</li> <li>When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.</li> <li>Check in PHG transcoder output the MDS object, System-Type attribute</li> </ol> |                       |  |  |
+| <b>Pass/Fail criteria</b>                   | In Step 4, the MDS object, System-Type attribute is not present.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |  |  |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>System-Type attribute is not present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: MDS Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_SYS_TYPE (2438)</li> <li><input type="checkbox"/> Attribute-type: TYPE</li> <li><input type="checkbox"/> Attribute-value: &lt;NOT PRESENT&gt;</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message does not include segments with System-Type attribute value (67974^MDC_ATTR_SYS_TYPE^MDC)</p>             |                       |  |  |
+
+|                          |                                                                                                                                                                                                                                  |                       |  |  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-001                                                                                                                                                                                                   |                       |  |  |
+| <b>TP label</b>          | Whitepaper. Pulse Oximeter MDS Object - Dev-Configuration-Id Attribute                                                                                                                                                           |                       |  |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                      | [Bluetooth PHDT v1.6] |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                            | Common MDS 17; M      |  |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes MDS object, Dev-Configuration-Id attribute in transcoder output.</p> <p>[AND]</p> <p>Dev-Configuration-Id value is set to any value in range of 0x4000 to 0x7FFF (Extended Configuration)</p> |                       |  |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                |                       |  |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                  |                       |  |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                               |                       |  |  |
+| <b>Test Procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is</li> </ol>         |                       |  |  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>discoverable).</p> <ol style="list-style-type: none"> <li>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).</li> <li>3. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.</li> <li>4. Check in PHG transcoder output the MDS object, Dev-Configuration-Id attribute</li> </ol>                                                                                                                                                                                                                                                                                                  |
+| <b>Pass/Fail criteria</b>                   | In Step 4, the MDS object, Dev-Configuration-Id attribute is present, its value is inside the range 0x4000 - 0x7FFF                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <ol style="list-style-type: none"> <li>a) IEEE 11073 Objects and Attributes<br/>Dev-Configuration-Id attribute is present: <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: MDS Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_DEV_CONFIG_ID (2628)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: Any value inside the range 16384 - 32767 (dec) or 0x4000 – 0x7FFF (hex)</li> </ul> </li> <li>b) WAN PCD-01 message<br/>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.</li> </ol> |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |                       |
+|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|
+| <b>TP Id</b>                                | TP/LP-PAN/PHG/PHDTW/PLX/BV-002                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                       |                       |
+| <b>TP label</b>                             | Whitepaper. Pulse Oximeter MDS Object - System-Type-Spec-List Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                       |                       |
+| <b>Coverage</b>                             | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [Bluetooth PHDT v1.6] |                       |
+|                                             | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Common MDS 15; M      | PLX Specific MDS 2; M |
+| <b>Test purpose</b>                         | <p>Check that:</p> <p>PHG includes MDS object, System-Type-Spec-List attribute in transcoder output.</p> <p>[AND]</p> <p>System-Type-Spec-List is set to (MDC_DEV_SPEC_PROFILE_PULS_OXIM, Version 1)</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |                       |
+| <b>Applicability</b>                        | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |                       |
+| <b>Other PICS</b>                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |                       |
+| <b>Initial condition</b>                    | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                       |                       |
+| <b>Test procedure</b>                       | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>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).</li> <li>3. When the pairing has been completed (Connection state) the simulated PHD sends the Measurement to the PHG under test.</li> <li>4. Check in PHG transcoder output the MDS object, System-Type-Spec-List attribute</li> </ol> |                       |                       |
+| <b>Pass/Fail criteria</b>                   | In Step 4, the MDS object, System-Type-Spec-List attribute is present, its value is (MDC_DEV_SPEC_PROFILE_PULS_OXIM, Version 1)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |                       |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <ol style="list-style-type: none"> <li>a) IEEE 11073 Objects and Attributes<br/>System-Type-Spec-List attribute is present: <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: MDS Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_SYS_TYPE_SPEC_LIST (2650)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE OF {type (INT-U16), version (INT-U16)}</li> </ul> </li> </ol>                                                                                                                                                  |                       |                       |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <p><input type="checkbox"/> Attribute-value:</p> <ul style="list-style-type: none"> <li>type: MDC_DEV_SPEC_PROFILE_PULS_OXIM, 4100 (dec) or 10 04 (hex)</li> <li>version: 1 (dec) or 00 01 (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with System-Type-Spec-List attribute value (check OBX-5):</p> <p>OBX ? NM 68186^MDC_ATTR_SYS_TYPE_SPEC_LIST^MDC 1.0.0.a <br/>528388^MDC_DEV_SPEC_PROFILE_PULS_OXIM^MDC     R</p> |
+|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |                      |  |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-003                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |                      |  |
+| <b>TP label</b>          | Whitepaper. Pulse Oximeter MDS Object - Reg-Cert-Data-List Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |                      |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [Bluetooth PHDT v1.6] |                      |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Common MDS 14; M      | Regulatory Conv 1; M |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG transcodes IEEE 11073-20601 Regulatory Certification Data List characteristic into MDS object, Reg-Cert-Data-List attribute</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |                      |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |                      |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |                      |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |                      |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is: <ol style="list-style-type: none"> <li>a. IEEE 11073-20601 Regulatory Certification Data List (0x2A2A) <ul style="list-style-type: none"> <li>• Format: reg-cert-data-list (opaque structure)</li> <li>• Value: 00 02 00 12 02 01 00 08 08 00 00 01 00 02 80 04 02 02 00 02 80 00 (hex) <ul style="list-style-type: none"> <li>i. Element: <ul style="list-style-type: none"> <li>• auth-body-and-struc-type: <ul style="list-style-type: none"> <li>- auth-body: 02 (hex) auth-body-continua(2)</li> <li>- auth-body-struc-type: 01 (hex). continua-version-struct(1)</li> </ul> </li> <li>• auth-body-data: <ul style="list-style-type: none"> <li>- major-IG-version: 08 (hex)</li> <li>- minor-IG-version: 00 (hex)</li> <li>- certified-devices: 80 04 (hex) BTLE Pulse Oximeter</li> </ul> </li> </ul> </li> <li>ii. Element: <ul style="list-style-type: none"> <li>• auth-body-and-struc-type: <ul style="list-style-type: none"> <li>- auth-body: 02 (hex). auth-body-continua(2)</li> <li>- auth-body-struc-type: 02 (hex). continua-reg-struct(2)</li> </ul> </li> <li>• auth-body-data: <ul style="list-style-type: none"> <li>- regulation-bit-field: 80 00 (hex). Unregulated device</li> </ul> </li> </ul> </li> </ul> </li> </ul> </li> </ol> </li> <li>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.</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read IEEE 11073-20601 Regulatory Certification Data List characteristic.</li> </ol> |                       |                      |  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | 5. Check in PHG transcoder output the MDS object, Reg-Cert-Data-List attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Pass/Fail criteria</b>                   | 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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Reg-Cert-Data-List attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: MDS Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_REG_CERT_DATA_LIST (2635)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE OF [{auth-body-and-struc-type, auth-body-data}, {...}]</li> <li><input type="checkbox"/> Attribute-value: 00 02 00 12 02 01 00 08 08 00 00 01 00 02 80 04 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] <ul style="list-style-type: none"> <li>i. Reg-Cert-Data Element: <ul style="list-style-type: none"> <li>• auth-body-and-struc-type: <ul style="list-style-type: none"> <li>- auth-body: 02 (hex) auth-body-continua(2)</li> <li>- auth-body-struc-type: 01 (hex). continua-version-struct(1)</li> </ul> </li> <li>• auth-body-data: <ul style="list-style-type: none"> <li>- major-IG-version: 08 (hex)</li> <li>- minor-IG-version: 00 (hex)</li> <li>- certified-devices: 80 04 (hex). BTLE Pulse Oximeter</li> </ul> </li> </ul> </li> <li>ii. Reg-Cert-Data Element: <ul style="list-style-type: none"> <li>• auth-body-and-struc-type: <ul style="list-style-type: none"> <li>- auth-body: 02 (hex). auth-body-continua(2)</li> <li>- auth-body-struc-type: 02 (hex). continua-reg-struct(2)</li> </ul> </li> <li>• auth-body-data: <ul style="list-style-type: none"> <li>- regulation-bit-field: 80 00 (hex). Unregulated device</li> </ul> </li> </ul> </li> </ul> </li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes five segments like these with Reg-Cert-Data-List attribute value (check OBX-5 in five segments):</p> <pre>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 32772     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</pre> |
+
+|                     |                                                                                                     |                       |  |
+|---------------------|-----------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>        | TP/LP-PAN/PHG/PHDTW/PLX/BV-004                                                                      |                       |  |
+| <b>TP label</b>     | Whitepaper. SpO2 Numeric Object (Spot-Check Measurement) - Handle Attribute                         |                       |  |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                         | [Bluetooth PHDT v1.6] |  |
+|                     | <b>Testable items</b>                                                                               | SpO2 Numeric 1; O     |  |
+| <b>Test purpose</b> | Check that:<br>PHG does not include SpO2 Numeric object, Handle Attribute in transcoder output when |                       |  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | using spot-check measurement mode.<br>[OR]<br>If PHG includes SpO2 Numeric object, Handle attribute in transcoder output, then its value shall be different than 0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 1100 (MSB → LSB). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported.</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0001 (MSB → LSB). Timestamp field is present. Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</li> </ol> |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>5. The simulated PHD sends the measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the SpO2 Numeric object, Handle attribute</p> <p>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <p style="padding-left: 20px;">a) 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 spot-check measurement to PHG under test</p> <p style="padding-left: 20px;">b) Check in PHG transcoder output the SpO2 Numeric object, Handle attribute</p>                                                                                                                           |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the SpO2 Numeric object, Handle attribute is not present or, if it is present then its value is different than 0</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p style="padding-left: 20px;">a) IEEE 11073 Objects and Attributes</p> <p style="padding-left: 40px;">Handle attribute is not present, or if it is present then:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_HANDLE (2337)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: Any value different than 0</li> </ul> <p style="padding-left: 20px;">b) WAN PCD-01 message</p> <p style="padding-left: 40px;">PCD-01 message does not include segments with Handle attribute value</p> |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-005                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |
+| <b>TP label</b>          | Whitepaper. SpO2 Numeric Object (Continuous Measurements) - Handle Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [Bluetooth PHDT v1.6] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | SpO2 Numeric 11; O    |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG does not include SpO2 Numeric object, Handle Attribute in transcoder output when using continuous measurements</p> <p>[OR]</p> <p>If PHG includes SpO2 Numeric object, Handle attribute in transcoder output, then its value shall be different than 0</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                       |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |
+| <b>Test procedure</b>    | <p>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</p> <p>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:</p> <p style="padding-left: 20px;">a. PLX Features (0x2A60)</p> <p style="padding-left: 40px;">i. Field: Supported Features</p> <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0011 0000 (MSB → LSB). Fast and slow response modes are supported (bits 4 and 5).</li> </ul> <p style="padding-left: 40px;">ii. Field: Measurement Status Support</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> |                       |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>iii. Field: Device and Sensor Status Support</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>b. PLX Continuous Measurement (0x2A5F)</p> <p>i. Field: Flags</p> <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0011 (MSB → LSB). SpO2PR-Fast, SpO2PR-Slow fields are present. Measurement Status, Device and Sensor Status and Pulse Amplitude Index fields are not present.</li> </ul> <p>ii. Field: SpO2PR-Normal - SpO2 (%)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>iii. Field: SpO2PR-Normal – PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>iv. Field: SpO2PR-Fast - SpO2 (%)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>v. Field: SpO2PR-Fast - PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>vi. Field: SpO2PR-Slow - SpO2 (%)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>vii. Field: SpO2PR-Slow - PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>viii. Field: Measurement Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>ix. Field: Device and Sensor Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>x. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the SpO2 Numeric object, Handle attribute in all three SpO2 objects (continuous normal, fast and slow).</p> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6,</p> <ul style="list-style-type: none"> <li>• There are three SpO2 objects (for normal, fast and slow measurement modes).</li> <li>• In all three objects, the SpO2 Numeric object, Handle attribute is not present or, if it is present then its value is different than 0</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <p>Handle attribute is not present in SpO2 objects, or if it is present then:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_HANDLE (2337)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: Any value different than 0</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message does not include segments with Handle attribute value</p> |
+|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-006                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |
+| <b>TP label</b>          | Whitepaper. SpO2 Numeric Object (Spot-Check Measurement) - Type Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [Bluetooth PHDT v1.6] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | SpO2 Numeric 2; M     |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes SpO2 Numeric object, Type attribute in transcoder output when using spot-check measurement mode.</p> <p>[AND]</p> <p>Type is set to {MDC_PART_SCADA, MDC_PULS_OXIM_SAT_O2}</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                       |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 1100 (MSB → LSB). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported.</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0001 (MSB → LSB). Timestamp field is present. Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm)</li> </ol> </li> </ol> </li> </ol> |                       |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>iv. Field: Time Stamp</p> <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> <p>v. Field: Measurement Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>vi. Field: Device and Sensor Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>vii. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the SpO2 Numeric object, Type attribute</p> <p>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <p>a) 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 spot-check measurement to PHG under test</p> <p>b. Check in PHG transcoder output the SpO2 Numeric object, Type attribute</p> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the SpO2 Numeric object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_PULS_OXIM_SAT_O2}</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Type attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_TYPE (2351)</li> <li><input type="checkbox"/> Attribute-type : SEQUENCE {partition (INT-U16), code (INT-U16)}</li> <li><input type="checkbox"/> Attribute-value: <ul style="list-style-type: none"> <li>• partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)</li> <li>• code: MDC_PULS_OXIM_SAT_O2 or 19384 (dec) or 4B B8 (hex)</li> </ul> </li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Type attribute (check OBX-3):</p> <p>OBX n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x [value] <br/>262688^MDC_DIM_PERCENT^MDC   R   [current_date_time]</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                     |                                                                            |                       |  |
+|---------------------|----------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>        | TP/LP-PAN/PHG/PHDTW/PLX/BV-007                                             |                       |  |
+| <b>TP label</b>     | Whitepaper. SpO2 Numeric Object (Continuous Measurements) – Type Attribute |                       |  |
+| <b>Coverage</b>     | <b>Spec</b>                                                                | [Bluetooth PHDT v1.6] |  |
+|                     | <b>Testable items</b>                                                      | SpO2 Numeric 12;<br>M |  |
+| <b>Test purpose</b> | Check that:                                                                |                       |  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | PHG includes SpO2 Numeric object, Type attribute in transcoder output when using continuous measurements.<br>[AND]<br>Type is set to {MDC_PART_SCADA, MDC_PULS_OXIM_SAT_O2}                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Feature (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0011 0000 (MSB → LSB). Fast and slow response modes are supported (bits 4 and 5).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Continuous Measurement (0x2A5F) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0011 (MSB → LSB). SpO2PR-Fast, SpO2PR-Slow fields are present. Measurement Status, Device and Sensor Status and Pulse Amplitude Index fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Normal – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: SpO2PR-Fast - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: SpO2PR-Fast - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vi. Field: SpO2PR-Slow - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vii. Field: SpO2PR-Slow - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>viii. Field: Measurement Status</li> </ol> </li> </ol> </li> </ol> |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> ix. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> x. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> 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).<br>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Feature characteristic.<br>5. The simulated PHD sends the Measurement to the PHG under test.<br>6. Check in PHG transcoder output the SpO2 Numeric object, Type attribute in all three SpO2 objects (continuous normal, fast and slow).                                                                                   |
+| <b>Pass/Fail criteria</b>                   | In Step 6, <ul style="list-style-type: none"> <li>There are three SpO2 objects (for normal, fast and slow measurement modes).</li> <li>In all three objects, the SpO2 Numeric object, Type attribute is present and its value is {MDC_PART_SCADA, MDC_PULS_OXIM_SAT_O2}</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes<br/>(To assist manual testing)</b> | Possible values in typical points of observation after transcoder output are:<br>a) IEEE 11073 Objects and Attributes<br>Type attribute is present in all three SpO2 objects: <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_TYPE (2351)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}</li> <li><input type="checkbox"/> Attribute-value: <ul style="list-style-type: none"> <li>partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)</li> <li>code: MDC_PULS_OXIM_SAT_O2 or 19384 (dec) or 4B B8 (hex)</li> </ul> </li> </ul> b) WAN PCD-01 message<br>PCD-01 message includes three segments like this with Type attribute (check OBX-3):<br><pre>OBX n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x [value]  262688^MDC_DIM_PERCENT^MDC     R   [current_date_time]</pre> |
+
+|                          |                                                                                                                                                                                                                                                                    |                       |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-008                                                                                                                                                                                                                                     |                       |  |
+| <b>TP label</b>          | Whitepaper. SpO2 Numeric Object (Spot-Check Measurement) – Supplemental-Types Attribute                                                                                                                                                                            |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                        | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                              | SpO2 Numeric 3; M     |  |
+| <b>Test purpose</b>      | Check that:<br>PHG includes SpO2 Numeric object, Supplemental-Types attribute in transcoder output when using spot-check measurement mode.<br>[AND]<br>Supplemental-Types attribute is set to {MDC_PART_SCADA, MDC_MODALITY_SPOT}.                                 |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                  |                       |  |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                      |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                 |                       |  |
+| <b>Test procedure</b>    | 1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). Simulated PHD also supports the RACP characteristic and has an |                       |  |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <p>identical spot-check measurement temporarily stored.</p> <ol style="list-style-type: none"> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 <b>1100</b> (MSB → LSB). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported.</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0001 (MSB → LSB). Timestamp field is present. Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</li> <li>5. The simulated PHD sends the Measurement to the PHG under test.</li> <li>6. Check in PHG transcoder output the SpO2 Numeric object, Supplemental-Types attribute</li> <li>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN <ol style="list-style-type: none"> <li>a) 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 spot-check measurement to PHG under test</li> <li>b) Check in PHG transcoder output the SpO2 Numeric object, Supplemental-Types attribute</li> </ol> </li> </ol> |
+|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Pass/Fail criteria</b>                   | In Step 6, the SpO2 Numeric object, Supplemental-Types attribute is present and its value is {MDC_PART_SCADA, MDC_MODALITY_SPOT}.<br>If the PHG supports RACP, the same criteria applies to Step 7.b.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Supplemental-Types attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object (Spot-Check measurement)</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_SUPPLEMENTAL_TYPES (2657)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE of SEQUENCE {partition (INT-U16), code (INT-U16)}</li> <li><input type="checkbox"/> Attribute-value: {MDC_PART_SCADA, MDC_MODALITY_SPOT}.</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a facet OBX segment of the SpO2 measurement OBX segment with Supplemental-Types attribute (check OBX-3 and OBX-5):</p> <pre>OBX[n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x [value]] 262688^MDC_DIM_PERCENT^MDC    R  [ current_date_time]  OBX[n CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y  150580^MDC_MODALITY_SPOT^MDC    R</pre> |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |                    |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-009                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |                    |
+| <b>TP label</b>          | Whitepaper. SpO2 Numeric Object (Continuous Measurements) – Supplemental-Types Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                       |                    |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [Bluetooth PHDT v1.6] |                    |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | SpO2 Numeric 13; M    | SpO2 Numeric 14; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG does not include SpO2 Numeric object, Supplemental-Types attribute in transcoder output for the SpO2 continuous measurement object (normal).</p> <p>[AND]</p> <p>PHG includes SpO2 Numeric object, Supplemental-Types attribute in transcoder output for the SpO2 continuous measurement object (fast mode). Supplemental-Types attribute is set to {MDC_PART_SCADA, MDC_MODALITY_FAST}.</p> <p>[AND]</p> <p>PHG includes SpO2 Numeric object, Supplemental-Types attribute in transcoder output for the SpO2 continuous measurement object (slow mode). Supplemental-Types attribute is set to {MDC_PART_SCADA, MDC_MODALITY_SLOW}.</p>                                                                                                                                                                     |                       |                    |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |                    |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |                    |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |                    |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Feature (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0011 0000 (MSB → LSB). Fast and slow response modes are supported (bits 4 and 5).</li> </ul> </li> <li>ii. Field: Measurement Status Support</li> </ol> </li> </ol> </li> </ol> |                       |                    |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p style="padding-left: 40px;">iii. Field: Device and Sensor Status Support</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p style="padding-left: 20px;">b. PLX Continuous Measurement (0x2A5F)</p> <ul style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0011 (MSB → LSB). SpO2PR–Fast, SpO2PR–Slow fields are present. Measurement Status, Device and Sensor Status and Pulse Amplitude Index fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Normal - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: SpO2PR-Fast - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: SpO2PR-Fast - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vi. Field: SpO2PR-Slow - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vii. Field: SpO2PR-Slow - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>viii. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>ix. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>x. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Feature characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the SpO2 Numeric object, Supplemental-Types attribute in all three SpO2 objects (continuous normal, fast and slow).</p> |
+| <b>Pass/Fail criteria</b> | <p>In Step 6,</p> <ul style="list-style-type: none"> <li>• The SpO2 Numeric Object (normal) – Supplemental-Types attribute is not present</li> <li>• The SpO2 Numeric Object (fast response) Supplemental-Types attribute is present and its value is {MDC_PART_SCADA, MDC_MODALITY_FAST}.</li> <li>• The SpO2 Numeric Object (slow response) Supplemental-Types attribute is present and its value is {MDC_PART_SCADA, MDC_MODALITY_SLOW}.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Supplemental Types attribute is not present for SpO2 Numeric Object (normal).</p> <p>Supplemental-Types attribute is present for SpO2 Numeric Object (fast response):</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object (fast response)</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_SUPPLEMENTAL_TYPES (2657)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE of SEQUENCE {partition (INT-U16), code (INT-U16)}</li> <li><input type="checkbox"/> Attribute-value: {MDC_PART_SCADA, MDC_MODALITY_FAST}.</li> </ul> <p>Supplemental-Types attribute is present for SpO2 Numeric Object (slow response):</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object (slow response)</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_SUPPLEMENTAL_TYPES (2657)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE of SEQUENCE {partition (INT-U16), code (INT-U16)}</li> <li><input type="checkbox"/> Attribute-value: {MDC_PART_SCADA, MDC_MODALITY_SLOW}.</li> </ul> <p>b) WAN PCD-01 message</p> <p>For SpO2 Numeric Object (normal)</p> <ul style="list-style-type: none"> <li>• PCD-01 message does not include segments with Supplemental-Types attribute.</li> </ul> <p>For SpO2 Numeric Object (fast)</p> <ul style="list-style-type: none"> <li>• PCD-01 message includes a facet OBX segment of the SpO2 measurement OBX segment with Supplemental-Types attribute (check OBX-3 and OBX-5): <pre>OBX n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x [value]  262688^MDC_DIM_PERCENT^MDC    R  [current_date_time]</pre> <pre>OBX n CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y  150580^MDC_MODALITY_FAST^MDC    R</pre> </li> <li>• For SpO2 Numeric Object (slow) <p>PCD-01 message includes a facet OBX segment of the SpO2 measurement OBX segment with Supplemental-Types attribute (check OBX-3 and OBX-5):</p> <pre>OBX n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.y [value]  262688^MDC_DIM_PERCENT^MDC    R  [current_date_time]</pre> <pre>OBX n CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.y.z  150580^MDC_MODALITY_SLOW^MDC    R</pre> </li> </ul> |
+|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                    |                       |                   |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-010                                                                                                                                                                                                                                     |                       |                   |
+| <b>TP label</b>          | Whitepaper. SpO2 Numeric Object (Spot-Check Measurement) - Metric-Spec-Small Attribute 1                                                                                                                                                                           |                       |                   |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                        | [Bluetooth PHDT v1.6] |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                              | SpO2 Numeric 4; M     | SpO2 Numeric 6; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes SpO2 Numeric object, Metric-Spec-Small attribute in transcoder output when using spot-check measurement mode.</p> <p>[AND]</p> <p>Metric-Spec-Small is set to {0x5040} when the sensor device supports measurement storage.</p> |                       |                   |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                  |                       |                   |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                      |                       |                   |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                 |                       |                   |
+| <b>Test procedure</b>    | 1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it                                                                                                                                                                       |                       |                   |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <p>has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). Simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</p> <ol style="list-style-type: none"><li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:<ol style="list-style-type: none"><li>a. PLX Spot-Check Measurement (0x2A5E)</li><li>b. PLX Feature (0x2A60)<ol style="list-style-type: none"><li>i. Field: Supported Features<ul style="list-style-type: none"><li>• Format: 16 bit</li><li>• Value: 0000 0000 0000 <b>1100</b> (MSB → LSB). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li></ul></li><li>ii. Field: Measurement Status Support<ul style="list-style-type: none"><li>• This field is not included</li></ul></li><li>iii. Field: Device and Sensor Status Support<ul style="list-style-type: none"><li>• This field is not included</li></ul></li></ol></li></ol></li><li>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).</li><li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Feature characteristic.</li><li>5. The simulated PHD sends the Measurement to the PHG under test with the following value:<ol style="list-style-type: none"><li>a. PLX Spot-Check Measurement (0x2A5E)<ol style="list-style-type: none"><li>i. Field: Flags<ul style="list-style-type: none"><li>• Format: 8 bit</li><li>• Value: 0000 0001 (MSB → LSB). Timestamp field is supported. Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li></ul></li><li>ii. Field: SpO2PR-Spot-Check - SpO2 (%)<ul style="list-style-type: none"><li>• Format: SFLOAT</li><li>• Value: Not Relevant</li></ul></li><li>iii. Field: SpO2PR-Spot-Check – PR (bpm)<ul style="list-style-type: none"><li>• Format: SFLOAT</li><li>• Value: Not Relevant</li></ul></li><li>iv. Field: Time Stamp<ul style="list-style-type: none"><li>• Format: Date and Time</li><li>• Value: Not Relevant</li></ul></li><li>v. Field: Measurement Status<ul style="list-style-type: none"><li>• This field is not included</li></ul></li><li>vi. Field: Device and Sensor Status<ul style="list-style-type: none"><li>• This field is not included</li></ul></li><li>vii. Field: Pulse Amplitude Index (%)<ul style="list-style-type: none"><li>• This field is not included</li></ul></li></ol></li></ol></li><li>6. Check in PHG transcoder output the SpO2 numeric object, Metric-Spec-Small attribute</li><li>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN<ol style="list-style-type: none"><li>a) 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 spot-check measurement to PHG under test</li></ol></li></ol> |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | b) Check in PHG transcoder output the SpO2 numeric object, Metric-Spec-Small attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Pass/Fail criteria</b>                   | In Step 6, the SpO2 Numeric Object – Metric-Spec-Small attribute is present and its value is {0x5040} (mss-avail-stored-data  mss-msmt-aperiodic  mss-acc-agent-initiated).<br>If the PHG supports RACP, the same criteria applies to Step 7.b                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes<br/>(To assist manual testing)</b> | Possible values in typical points of observation after transcoder output are:<br>a) IEEE 11073 Objects and Attributes<br>Metric-Spec-Small attribute is present:<br><ul style="list-style-type: none"><li><input type="checkbox"/> Object: SpO2 Numeric Object</li><li><input type="checkbox"/> Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)</li><li><input type="checkbox"/> Attribute-type: BITS-16</li><li><input type="checkbox"/> Attribute-value: 50 40 (hex) or BITS mss-avail-stored-data (1), mss- msmt - aperiodic(3), mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE</li></ul> b) WAN PCD-01 message<br>PCD-01 message does not include segments with Metric-Spec-Small attribute value |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |                   |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-011                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |                   |
+| <b>TP label</b>          | Whitepaper. SpO2 Numeric Object (Spot-Check Measurement) - Metric-Spec-Small Attribute 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |                   |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [Bluetooth PHDT v1.6] |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | SpO2 Numeric 4; M     | SpO2 Numeric 5; M |
+| <b>Test purpose</b>      | Check that:<br>PHG includes SpO2 Numeric Object – Metric-Spec-Small attribute in transcoder output when using spot-check measurement mode.<br>[AND]<br>Metric-Spec-Small is set to {0x1040} when the sensor device does not support measurement storage.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |                   |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |                   |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |                   |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |                   |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The Simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Spot-Check Measurement (0x2A5E)</li> <li>b. PLX Feature (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 0000 (MSB → LSB). Measurement Storage for Spot-check measurements is not supported (bit 2).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> <li>3. The PHG under test initiates a discovery process (Scanning state), it discovers the</li> </ol> |                       |                   |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).</p> <ol style="list-style-type: none"> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Feature characteristic.</li> <li>5. The simulated PHD sends the Measurement to the PHG under test with the following value: <ol style="list-style-type: none"> <li>a. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0000 (MSB → LSB). Timestamp, Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> <li>6. Check in PHG transcoder output the SpO2 Numeric Object – Metric-Spec-Small attribute</li> </ol> |
+| <b>Pass/Fail criteria</b>                   | In Step 6, the SpO2 Numeric Object – Metric-Spec-Small attribute is present and its value is {0x1040} (mss-msmt-aperiodic   mss-acc-agent-initiated).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <ol style="list-style-type: none"> <li>a) IEEE 11073 Objects and Attributes<br/>Metric-Spec-Small attribute is present: <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)</li> <li><input type="checkbox"/> Attribute-type: BITS-16</li> <li><input type="checkbox"/> Attribute-value: 10 40 (hex) or BITS mss-msmt-aperiodic(3), mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE</li> </ul> </li> <li>b) WAN PCD-01 message<br/>PCD-01 message does not include segments with Metric-Spec-Small attribute value</li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                     |                                                                                         |                       |  |
+|---------------------|-----------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>        | TP/LP-PAN/PHG/PHDTW/PLX/BV-012                                                          |                       |  |
+| <b>TP label</b>     | Whitepaper. SpO2 Numeric Object (Continuous Measurements) - Metric-Spec-Small Attribute |                       |  |
+| <b>Coverage</b>     | <b>Spec</b>                                                                             | [Bluetooth PHDT v1.6] |  |
+|                     | <b>Testable items</b>                                                                   | SpO2 Numeric 16; M    |  |
+| <b>Test purpose</b> | Check that:                                                                             |                       |  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | PHG includes SpO2 Numeric Object – Metric-Spec-Small attribute in transcoder output when using continuous measurements.<br>[AND]<br>Metric-Spec-Small is set to {0x0040} (mss-acc-agent-initiated)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Feature (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0011 0000 (MSB → LSB). Fast and slow response modes are supported (bits 4 and 5).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Continuous Measurement (0x2A5F) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0011 (MSB → LSB). SpO2PR-Fast, SpO2PR-Slow fields are present. Measurement Status, Device and Sensor Status and Pulse Amplitude Index fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Normal – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: SpO2PR-Fast - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: SpO2PR-Fast - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vi. Field: SpO2PR-Slow - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vii. Field: SpO2PR-Slow - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>viii. Field: Measurement Status</li> </ol> </li> </ol> </li> </ol> |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> ix. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> x. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> 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).<br>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Feature characteristic.<br>5. The simulated PHD sends the Measurement to the PHG under test.<br>6. Check in PHG transcoder output the SpO2 Numeric Object – Metric-Spec-Small attribute in all three SpO2 objects (continuous normal, fast and slow). |
+| <b>Pass/Fail criteria</b>                   | In Step 6, <ul style="list-style-type: none"> <li>There are three SpO2 objects (for normal, fast and slow measurement modes).</li> <li>In all three objects, the SpO2 Numeric Object – Metric-Spec-Small attribute is present and its value is {0x0040} (mss-acc-agent-initiated).</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes<br/>(To assist manual testing)</b> | Possible values in typical points of observation after transcoder output are:<br>a) IEEE 11073 Objects and Attributes<br>Metric-Spec-Small attribute is present in all three SpO2 objects: <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)</li> <li><input type="checkbox"/> Attribute-type: BITS-16</li> <li><input type="checkbox"/> Attribute-value: 00 40 (hex) or BITS mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE</li> </ul> b) WAN PCD-01 message<br>PCD-01 message does not include segments with Metric-Spec-Small attribute value                                                                                                                                                              |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-013                                                                                                                                                                                                                                                                                                                                                                                                                   |                       |  |
+| <b>TP label</b>          | Whitepaper. SpO2 Numeric Object (Spot-Check Measurement) – Measurement-Status Attribute                                                                                                                                                                                                                                                                                                                                                          |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                      | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                            | SpO2 Numeric 7; M     |  |
+| <b>Test purpose</b>      | Check that:<br>PHG includes SpO2 Numeric Object – Measurement-Status attribute in transcoder output when using spot-check measurement mode.<br>[AND]<br>PHG transcodes the Bluetooth Measurement Status field of the PLX Spot-Check characteristic to 11073 Measurement-Status attribute properly                                                                                                                                                |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                |                       |  |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                               |                       |  |
+| <b>Test procedure</b>    | 1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). Simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.<br>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: |                       |  |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <ol style="list-style-type: none"> <li>a. PLX Spot-Check Measurement (0x2A5E)</li> <li>b. PLX Feature (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 <b>1101</b> (MSB → LSB). Measurement Status support is present (bit 0). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: <b>1111 1111 1110 0000</b> (MSB → LSB). All Measurement Status bits are supported</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Feature characteristic.</li> <li>5. The simulated PHD sends the Measurement to the PHG under test with the following value: <ol style="list-style-type: none"> <li>a. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 00<b>11</b> (MSB → LSB). Measurement Status and Timestamp fields are present. Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: <b>1000 0000 0000 0000</b> (MSB → LSB). Invalid measurement detected (bit 15).</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> <li>6. Check in PHG transcoder output the SpO2 Numeric Object – Measurement-Status attribute</li> <li>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN <ol style="list-style-type: none"> <li>a) 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 spot-check measurement to PHG</li> </ol> </li> </ol> |
+|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+32 Rec. ITU-T H.850.6 (08/2020)
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>remaining fields remain equal to those in step 5. Simulated PHD also deletes all stored records in RACP and stores an identical measurement.</p> <p>21. Check in PHG transcoder output the SpO2 Numeric Object – Measurement-Status attribute</p> <p>22. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <ul style="list-style-type: none"> <li>a) 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 spot-check measurement to PHG under test</li> <li>b) Check in PHG transcoder output the SpO2 Numeric Object – Measurement-Status attribute</li> </ul> <p>23. The simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0000 0000 1000 0000 (MSB → LSB), fully qualified data (bit 7). All remaining fields remain equal to those in step 5. Simulated PHD also deletes all stored records in RACP and stores an identical measurement.</p> <p>24. Check in PHG transcoder output the SpO2 Numeric Object – Measurement-Status attribute</p> <p>25. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <ul style="list-style-type: none"> <li>a) 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 spot-check measurement to PHG under test</li> <li>b) Check in PHG transcoder output the SpO2 Numeric Object – Measurement-Status attribute</li> </ul> <p>26. The simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0000 0000 0100 0000 (MSB → LSB), early estimated data (bit 6). All remaining fields remain equal to those in step 5. Simulated PHD also deletes all stored records in RACP and stores an identical measurement.</p> <p>27. Check in PHG transcoder output the SpO2 Numeric Object – Measurement-Status attribute</p> <p>28. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <ul style="list-style-type: none"> <li>a) 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 spot-check measurement to PHG under test</li> <li>b) Check in PHG transcoder output the SpO2 Numeric Object – Measurement-Status attribute</li> </ul> <p>29. The simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0000 0000 0010 0000 (MSB → LSB), measurement ongoing (bit 5). All remaining fields remain equal to those in step 5. Simulated PHD also deletes all stored records in RACP and stores an identical measurement.</p> <p>30. Check in PHG transcoder output the SpO2 Numeric Object – Measurement-Status attribute</p> <p>31. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <ul style="list-style-type: none"> <li>a) 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 spot-check measurement to PHG under test</li> <li>b) Check in PHG transcoder output the SpO2 Numeric Object – Measurement-Status attribute</li> </ul> |
+| <b>Pass/Fail criteria</b> | <p>In Step 6, the SpO2 Numeric Object – Measurement-Status attribute is present and its set to “invalid” (0x8000). If PHG supports RACP, same criteria applies to 7.b.</p> <p>In Step 9, the SpO2 Numeric Object – Measurement-Status attribute is present and its set to “questionable” (0x4000). If PHG supports RACP, same criteria applies to 10.b.</p> <p>In Step 12, the SpO2 Numeric Object – Measurement-Status attribute is present and its set to “not-available” (0x2000). If PHG supports RACP, same criteria applies to 13.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+|                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                                    | <p>In Step 15, the SpO2 Numeric Object – Measurement-Status attribute is present and its set to “calibration-ongoing” (0x1000). If PHG supports RACP, same criteria applies to 16.b.</p> <p>In Step 18, the SpO2 Numeric Object – Measurement-Status attribute is present and its set to “test-data” (0x0800). If PHG supports RACP, same criteria applies to 19.b.</p> <p>In Step 21, the SpO2 Numeric Object – Measurement-Status attribute is present and its set to “demo-data” (0x0400). If PHG supports RACP, same criteria applies to 22.b.</p> <p>In Step 24, the SpO2 Numeric Object – Measurement-Status attribute is present and its set to “validated-data” (0x0080). If PHG supports RACP, same criteria applies to 25.b.</p> <p>In Step 27, the SpO2 Numeric Object – Measurement-Status attribute is present and its set to “early-indication” (0x0040). If PHG supports RACP, same criteria applies to 28.b.</p> <p>In Step 30, the SpO2 Numeric Object – Measurement-Status attribute is present and its set to “msmt-ongoing” (0x0020). If PHG supports RACP, same criteria applies to 31.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <p><b>Notes<br/>(To assist manual testing)</b></p> | <p>In step 6 (and step 7.b if applicable), possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>80 00</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x [value]  262688^MDC_DIM_PERCENT^MDC  <b>INV</b>  <b>X</b>  [current_date_time]</pre> <p>In step 9 (and step 10.b if applicable), possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>40 00</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x [value]  262688^MDC_DIM_PERCENT^MDC  <b>QUES</b>  <b>R</b>  [current_date_time]</pre> <p>In step 12 (and step 13.b if applicable), possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>20 00</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> |
+
+OBX|n|NM|150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC|m.0.0.x|[value]  
+262688^MDC\_DIM\_PERCENT^MDC||**NAV**||**X**||[current\_date\_time]
+
+In step 15 (and step 16.b if applicable), possible values in typical points of observation after transcoder output are:
+
+#### a) IEEE 11073 Objects and Attributes
+
+Measurement-Status attribute is present:
+
+- Object: SpO2 Numeric Object
+- Attribute-id: MDC\_ATTR\_MSMT\_STAT (2375)
+- Attribute-type: BITS16
+- Attribute-value: **10 00** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):
+
+OBX|n|NM|150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC|m.0.0.x|[value]  
+262688^MDC\_DIM\_PERCENT^MDC||**CAL**||**R**||[current\_date\_time]
+
+In step 18 (and step 19.b if applicable), possible values in typical points of observation after transcoder output are:
+
+#### a) IEEE 11073 Objects and Attributes
+
+Measurement-Status attribute is present:
+
+- Object: SpO2 Numeric Object
+- Attribute-id: MDC\_ATTR\_MSMT\_STAT (2375)
+- Attribute-type: BITS16
+- Attribute-value: **08 00** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):
+
+OBX|n|NM|150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC|m.0.0.x|[value]  
+262688^MDC\_DIM\_PERCENT^MDC||**TEST**||**R**||[current\_date\_time]
+
+In step 21 (and step 22.b if applicable), possible values in typical points of observation after transcoder output are:
+
+#### a) IEEE 11073 Objects and Attributes
+
+Measurement-Status attribute is present:
+
+- Object: SpO2 Numeric Object
+- Attribute-id: MDC\_ATTR\_MSMT\_STAT (2375)
+- Attribute-type: BITS16
+- Attribute-value: **04 00** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):
+
+OBX|n|NM|150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC|m.0.0.x|[value]  
+262688^MDC\_DIM\_PERCENT^MDC||**DEMO**||**R**||[current\_date\_time]
+
+In step 24 (and step 25.b if applicable), possible values in typical points of observation after transcoder output are:
+
+#### a) IEEE 11073 Objects and Attributes
+
+Measurement-Status attribute is present:
+
+- Object: SpO2 Numeric Object
+- Attribute-id: MDC\_ATTR\_MSMT\_STAT (2375)
+- Attribute-type: BITS16
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <p><input type="checkbox"/> Attribute-value: <b>00 80</b> (hex)</p> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x [value]  262688^MDC_DIM_PERCENT^MDC   F   [current_date_time]</pre> <p>In step 27 (and step 28.b if applicable), possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present:</p> <p><input type="checkbox"/> Object: SpO2 Numeric Object</p> <p><input type="checkbox"/> Attribute-id: MDC_ATTR_MSMT_STAT (2375)</p> <p><input type="checkbox"/> Attribute-type: BITS16</p> <p><input type="checkbox"/> Attribute-value: <b>00 40</b> (hex)</p> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x [value]  262688^MDC_DIM_PERCENT^MDC   EARLY   R   [current_date_time]</pre> <p>In step 30 (and step 31.b if applicable), possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present:</p> <p><input type="checkbox"/> Object: SpO2 Numeric Object</p> <p><input type="checkbox"/> Attribute-id: MDC_ATTR_MSMT_STAT (2375)</p> <p><input type="checkbox"/> Attribute-type: BITS16</p> <p><input type="checkbox"/> Attribute-value: <b>00 20</b> (hex)</p> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x [value]  262688^MDC_DIM_PERCENT^MDC   BUSY   X   [current_date_time]</pre> |
+|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                              |                       |  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-014                                                                                                                                                                                                                                                                                               |                       |  |
+| <b>TP label</b>          | Whitepaper. SpO2 Numeric Object (Continuous Measurements) – Measurement-Status Attribute                                                                                                                                                                                                                                     |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                  | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                        | SpO2 Numeric 17; M    |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes SpO2 Numeric Object – Measurement-Status attribute in transcoder output when using continuous measurements.</p> <p>[AND]</p> <p>PHG transcodes the Bluetooth Measurement Status field of the PLX Continuous Measurement characteristic to 11073 Measurement-Status attribute properly</p> |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                            |                       |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                              |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                           |                       |  |
+
+|                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <p><b>Test procedure</b></p> | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Continuous Measurement (0x2A5F)</li> <li>b. PLX Feature (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0011 0001 (MSB → LSB). Measurement Status support is present (bit 0). Fast and slow response modes are supported (bits 4 and 5).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 1111 1111 1110 0000 (MSB → LSB). All Measurement Status bits are supported</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Feature characteristic.</li> <li>5. The simulated PHD sends the Measurement to the PHG under test with the following value: <ol style="list-style-type: none"> <li>a. PLX Continuous Measurement (0x2A5F) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0111 (MSB → LSB). Measurement Status, SpO2PR–Fast and SpO2PR–Slow fields are present. Device and Sensor Status and Pulse Amplitude Index fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Normal - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: SpO2PR-Fast - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: SpO2PR-Fast - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vi. Field: SpO2PR-Slow - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vii. Field: SpO2PR-Slow - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> </ul> </li> </ol> </li> </ol> </li> </ol> |
+|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• Value: Not Relevant</li> </ul> <p>viii. Field: Measurement Status</p> <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 1000 0000 0000 0000 (MSB → LSB). Invalid measurement detected (bit 15).</li> </ul> <p>ix. Field: Device and Sensor Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>x. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <ol style="list-style-type: none"> <li>6. Check in PHG transcoder output the SpO2 Numeric Object – Measurement-Status attribute in all three SpO2 objects.</li> <li>7. Simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0100 0000 0000 0000 (MSB → LSB), questionable measurement detected (bit 14). All remaining fields remain equal to those in step 5.</li> <li>8. Check in PHG transcoder output the SpO2 Numeric Object – Measurement-Status attribute in all three SpO2 objects.</li> <li>9. Simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0010 0000 0000 0000 (MSB → LSB), measurement not available (bit 13). All remaining fields remain equal to those in step 5.</li> <li>10. Check in PHG transcoder output the SpO2 Numeric Object – Measurement-Status attribute in all three SpO2 objects.</li> <li>11. Simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0001 0000 0000 0000 (MSB → LSB), calibration ongoing (bit 12). All remaining fields remain equal to those in step 5.</li> <li>12. Check in PHG transcoder output the SpO2 Numeric Object – Measurement-Status attribute in all three SpO2 objects.</li> <li>13. Simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0000 1000 0000 0000 (MSB → LSB), data for testing (bit 11). All remaining fields remain equal to those in step 5.</li> <li>14. Check in PHG transcoder output the SpO2 Numeric Object – Measurement-Status attribute in all three SpO2 objects.</li> <li>15. Simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0000 0100 0000 0000 (MSB → LSB), data for demonstration (bit 10). All remaining fields remain equal to those in step 5.</li> <li>16. Check in PHG transcoder output the SpO2 Numeric Object – Measurement-Status attribute in all three SpO2 objects.</li> <li>17. Simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0000 0000 1000 0000 (MSB → LSB), fully qualified data (bit 7). All remaining fields remain equal to those in step 5.</li> <li>18. Check in PHG transcoder output the SpO2 Numeric Object – Measurement-Status attribute in all three SpO2 objects.</li> <li>19. Simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0000 0000 0100 0000 (MSB → LSB), early estimated data (bit 6). All remaining fields remain equal to those in step 5.</li> <li>20. Check in PHG transcoder output the SpO2 Numeric Object – Measurement-Status attribute in all three SpO2 objects.</li> <li>21. Simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0000 0000 0010 0000 (MSB → LSB), measurement ongoing (bit 5). All remaining fields remain equal to those in step 5.</li> <li>22. Check in PHG transcoder output the SpO2 Numeric Object – Measurement-Status attribute in all three SpO2 objects.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <p>In Step 6, the SpO2 Numeric Object – Measurement-Status attribute is present in all three SpO2 objects and its set to “invalid” (0x8000)</p> <p>In Step 8, the SpO2 Numeric Object – Measurement-Status attribute is present in all three</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                                    | <p>SpO2 objects and its set to “questionable” (0x4000)</p> <p>In Step 10, the SpO2 Numeric Object – Measurement-Status attribute is present in all three SpO2 objects and its set to “not-available” (0x2000)</p> <p>In Step 12, the SpO2 Numeric Object – Measurement-Status attribute is present in all three SpO2 objects and its set to “calibration-ongoing” (0x1000)</p> <p>In Step 14, the SpO2 Numeric Object – Measurement-Status attribute is present in all three SpO2 objects and its set to “test-data” (0x0800)</p> <p>In Step 16, the SpO2 Numeric Object – Measurement-Status attribute is present in all three SpO2 objects and its set to “demo-data” (0x0400)</p> <p>In Step 18, the SpO2 Numeric Object – Measurement-Status attribute is present in all three SpO2 objects and its set to “validated-data” (0x0080)</p> <p>In Step 20, the SpO2 Numeric Object – Measurement-Status attribute is present in all three SpO2 objects and its set to “early-indication” (0x0040)</p> <p>In Step 22, the SpO2 Numeric Object – Measurement-Status attribute is present in all three SpO2 objects and its set to “msmt-ongoing” (0x0020)</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <p><b>Notes<br/>(To assist manual testing)</b></p> | <p>In step 6, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present in all three SpO2 objects:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>80 00</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like for each SpO2 object this with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x [value] 262688^MDC_DIM_PERCENT^MDC  <b>INV</b>  <b>X</b>  [current_date_time]</pre> <p>In step 8, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present in all three SpO2 objects:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>40 00</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this for each SpO2 object with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x [value] 262688^MDC_DIM_PERCENT^MDC  <b>QUES</b>  <b>R</b>  [current_date_time]</pre> <p>In step 10, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present in all three SpO2 objects:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>20 00</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this for each SpO2 object with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> |
+
+OBX|n|NM|150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC|m.0.0.x|[value]  
+262688^MDC\_DIM\_PERCENT^MDC||**NAV**||**X**||[current\_date\_time]
+
+In step 12, possible values in typical points of observation after transcoder output are:
+
+#### a) IEEE 11073 Objects and Attributes
+
+Measurement-Status attribute is present in all three SpO2 objects:
+
+- Object: SpO2 Numeric Object
+- Attribute-id: MDC\_ATTR\_MSMT\_STAT (2375)
+- Attribute-type: BITS16
+- Attribute-value: **10 00** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this for each SpO2 object with Measurement-Status attribute value (check OBX-8 and OBX-11):
+
+OBX|n|NM|150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC|m.0.0.x|[value]  
+262688^MDC\_DIM\_PERCENT^MDC||**CAL**||**R**||[current\_date\_time]
+
+In step 14, possible values in typical points of observation after transcoder output are:
+
+#### a) IEEE 11073 Objects and Attributes
+
+Measurement-Status attribute is present in all three SpO2 objects:
+
+- Object: SpO2 Numeric Object
+- Attribute-id: MDC\_ATTR\_MSMT\_STAT (2375)
+- Attribute-type: BITS16
+- Attribute-value: **08 00** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this for each SpO2 object with Measurement-Status attribute value (check OBX-8 and OBX-11):
+
+OBX|n|NM|150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC|m.0.0.x|[value]  
+262688^MDC\_DIM\_PERCENT^MDC||**TEST**||**R**||[current\_date\_time]
+
+In step 16, possible values in typical points of observation after transcoder output are:
+
+#### a) IEEE 11073 Objects and Attributes
+
+Measurement-Status attribute is present in all three SpO2 objects:
+
+- Object: SpO2 Numeric Object
+- Attribute-id: MDC\_ATTR\_MSMT\_STAT (2375)
+- Attribute-type: BITS16
+- Attribute-value: **04 00** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this for each SpO2 object with Measurement-Status attribute value (check OBX-8 and OBX-11):
+
+OBX|n|NM|150456^MDC\_PULS\_OXIM\_SAT\_O2^MDC|m.0.0.x|[value]  
+262688^MDC\_DIM\_PERCENT^MDC||**DEMO**||**R**||[current\_date\_time]
+
+In step 18, possible values in typical points of observation after transcoder output are:
+
+#### a) IEEE 11073 Objects and Attributes
+
+Measurement-Status attribute is present in all three SpO2 objects:
+
+- Object: SpO2 Numeric Object
+- Attribute-id: MDC\_ATTR\_MSMT\_STAT (2375)
+- Attribute-type: BITS16
+- Attribute-value: **00 80** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this for each SpO2 object with Measurement-
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <p>Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX[n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x [value]] 262688^MDC_DIM_PERCENT^MDC   F   [current_date_time]</pre> <p>In step 20, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present in all three SpO2 objects:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>00 40</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this for each SpO2 object with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX[n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x [value]] 262688^MDC_DIM_PERCENT^MDC   EARLY   R   [current_date_time]</pre> <p>In step 22, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present in all three SpO2 objects:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>00 20</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this for each SpO2 object with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX[n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x [value]] 262688^MDC_DIM_PERCENT^MDC   BUSY   X   [current_date_time]</pre> |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                       |  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-015                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |  |
+| <b>TP label</b>          | Whitepaper. SpO2 Numeric Object (Spot-Check Measurement) – Unit-Code Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | SpO2 Numeric 8; M     |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes SpO2 Numeric Object –Unit-Code attribute in transcoder output when using spot-check measurement mode.</p> <p>[AND]</p> <p>Unit-Code is set to MDC_DIM_PERCENT</p>                                                                                                                                                                                                                                                                                                                                                                                     |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |  |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60)</li> </ol> </li> </ol> |                       |  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ol style="list-style-type: none"> <li>i. Field: Supported Features           <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 <b>1100</b> (MSB → LSB). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support           <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support           <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> <ol style="list-style-type: none"> <li>b. PLX Spot-Check Measurement (0x2A5E)           <ol style="list-style-type: none"> <li>i. Field: Flags               <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0001 (MSB → LSB). Timestamp field is present. Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%)               <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm)               <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp               <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: Measurement Status               <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status               <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%)               <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> <ol style="list-style-type: none"> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</li> <li>5. The simulated PHD sends the Measurement to the PHG under test.</li> <li>6. Check in PHG transcoder output the SpO2 Numeric Object – Unit-Code attribute</li> <li>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN           <ol style="list-style-type: none"> <li>a) 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 spot-check measurement to PHG under test</li> <li>b) Check in PHG transcoder output the SpO2 Numeric Object – Unit-Code attribute</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the SpO2 Numeric Object – Unit-Code attribute is present and its set to MDC_DIM_PERCENT.</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <ol style="list-style-type: none"> <li>a) IEEE 11073 Objects and Attributes</li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | Unit-Code attribute is present: <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_UNIT_CODE (2454)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: MDC_DIM_PERCENT or 544 (dec) or 02 20 (hex)</li> </ul> b) WAN PCD-01 message<br>PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):<br><pre>OBX n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x [value]<br/>262688^MDC_DIM_PERCENT^MDC    R  [current_date_time]</pre> |
+|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-016                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |  |
+| <b>TP label</b>          | Whitepaper. SpO2 Numeric Object (Continuous Measurements) – Unit-Code Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | SpO2 Numeric 18; M    |  |
+| <b>Test purpose</b>      | Check that:<br><br>PHG includes SpO2 Numeric Object – Unit-Code attribute in transcoder output when using continuous measurements.<br>[AND]<br>Unit-Code is set to MDC_DIM_PERCENT                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Feature (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0011 0000 (MSB → LSB). Fast and slow response modes are supported (bits 4 and 5).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Continuous Measurement (0x2A5F) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0011(MSB → LSB). SpO2PR-Fast, SpO2PR-Slow fields are present. Measurement Status, Device and Sensor Status and Pulse Amplitude Index fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                       |  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>iii. Field: SpO2PR-Normal – PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>iv. Field: SpO2PR-Fast - SpO2 (%)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>v. Field: SpO2PR-Fast - PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>vi. Field: SpO2PR-Slow - SpO2 (%)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>vii. Field: SpO2PR-Slow - PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>viii. Field: Measurement Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>ix. Field: Device and Sensor Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>x. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Feature characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the SpO2 Numeric Object – Unit-Code attribute in all three SpO2 objects (continuous normal, fast and slow).</p> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6,</p> <ul style="list-style-type: none"> <li>• There are three SpO2 objects (for normal, fast and slow measurement modes).</li> <li>• In all three objects, the SpO2 Numeric Object – Unit-Code attribute is present and its set to MDC_DIM_PERCENT.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Unit-Code attribute is present in all three SpO2 objects:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_UNIT_CODE (2454)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: MDC_DIM_PERCENT or 544 (dec) or 02 20 (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this for each SpO2 object with Unit-Code attribute value (check OBX-6):</p> <pre>OBX n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x[[value]] 262688^MDC_DIM_PERCENT^MDC    R    [current_date_time]</pre>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |                     |                     |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|---------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-017                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |                     |                     |
+| <b>TP label</b>          | Whitepaper. SpO2 Numeric Object (Spot-Check Measurement) – Absolute-Time-Stamp Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |                     |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [Bluetooth PHDT v1.6] |                     |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | SpO2 Numeric 9; M     | Date-Time Conv 2; M | Date-Time Conv 3; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Date-Time Conv 4; M   | Date-Time Conv 5; M |                     |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG transcodes Time Stamp field of Spot-Check Measurement characteristic into SpO2 Numeric Object - Absolute-Time-Stamp attribute</p> <p>[AND]</p> <p>PHG transcodes the Bluetooth Time Stamp field format to Absolute Time format</p> <p>[AND]</p> <p>The fraction of seconds in Absolute Time at transcoder output is 0</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |                     |                     |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |                     |                     |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |                     |                     |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                       |                     |                     |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a Spot-Check measurement ready to be sent and it is in Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 1100 (MSB → LSB). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0001 (MSB → LSB). Timestamp field is present. Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: October 12nd, 2015, 10:39:27</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                       |                     |                     |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>v. Field: Measurement Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>vi. Field: Device and Sensor Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>vii. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the SpO2 Numeric Object – Absolute-Time-Stamp attribute</p> <p>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <p>a) 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 spot-check measurement to PHG under test</p> <p>b) Check in PHG transcoder output the SpO2 Numeric Object – Absolute-Time-Stamp attribute</p> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the SpO2 Numeric Object – Absolute-Time-Stamp attribute is present, its value matches with Time Stamp field of Spot-Check Measurement characteristic and fraction of seconds is set to 0.</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Absolute-Time-Stamp attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)</li> <li><input type="checkbox"/> 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)</li> <li><input type="checkbox"/> Attribute-value: <ul style="list-style-type: none"> <li>• century: 20 (hex) or 32 (dec)</li> <li>• year: 15 (hex) or 21 (dec)</li> <li>• month: 10 (hex) or 16 (dec)</li> <li>• day: 12 (hex) or 18 (dec)</li> <li>• hour: 10 (hex) or 16 (dec)</li> <li>• minute: 39 (hex) or 57 (dec)</li> <li>• second: 27 (hex) or 39 (dec)</li> <li>• sec-fractions: 00 (hex) or 0 (dec)</li> </ul> </li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value (check OBX-14):</p> <pre>OBX n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x [value]  262688^MDC_DIM_PERCENT^MDC   R   20151012103927+0000</pre>          |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |                       |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-018                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |                       |
+| <b>TP label</b>          | Whitepaper. SpO2 Numeric Object (Spot-Check Measurement) – Basic-Nu-Observed-Value Attribute 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |                       |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [Bluetooth PHDT v1.6] |                       |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | SpO2 Numeric 10; M    | Short Float Type 1; C |
+| <b>Test purpose</b>      | Check that:<br><br>PHG transcodes SpO2 value of the SpO2PR-Spot-Check field in PLX Spot-Check Measurement characteristic into SpO2 Numeric Object - Basic-Nu-Observed-Value attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                       |                       |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |                       |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |                       |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |                       |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a Spot-Check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 <b>1100</b> (MSB → LSB). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0001 (MSB → LSB). Timestamp field is present. Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 96.0 (%)</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                       |                       |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>vii. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>This field is not included</li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the SpO2 Numeric Object – Basic-Nu-Observed-Value attribute</p> <p>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <p>a) 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 spot-check measurement to PHG under test</p> <p>b) Check in PHG transcoder output the SpO2 Numeric Object – Basic-Nu-Observed-Value attribute</p> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the SpO2 Numeric Object – Basic-Nu-Observed-Value attribute is present and its value matches with the value of the SpO2 subfield of the SpO2PR-Spot-Check field in the PLX Spot-Check Measurement characteristic (96.0%).</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Basic-Nu-Observed-Value attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)</li> <li><input type="checkbox"/> Attribute-type: SFLOAT</li> <li><input type="checkbox"/> Attribute-value: 00 60 (hex) or F3C0 (hex) or 96.0 (dec)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Basic-Nu-Observed-Value attribute value (check OBX-5):</p> <pre>OBX[n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x 96.0  262688^MDC_DIM_PERCENT^MDC   R   current_date_time </pre>                                                                                                                                                                                                                                                         |
+
+|                          |                                                                                                                                                                                                                                                                                         |                       |                    |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-019                                                                                                                                                                                                                                                          |                       |                    |
+| <b>TP label</b>          | Whitepaper. SpO2 Numeric Object (Spot-Check Measurement) – Basic-Nu-Observed-Value Attribute 2                                                                                                                                                                                          |                       |                    |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                             | [Bluetooth PHDT v1.6] |                    |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                   | SpO2 Numeric 10; M    | SpO2 Numeric 20; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG transcodes SpO2 value of the SpO2PR-Spot-Check field in PLX Spot-Check Measurement characteristic into SpO2 Numeric Object - Basic-Nu-Observed-Value attribute</p> <p>[AND]</p> <p>PHG assigns special value NaN (0x07FF) when SpO2 value is unavailable.</p> |                       |                    |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                       |                       |                    |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                           |                       |                    |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                      |                       |                    |
+| <b>Test procedure</b>    | <p>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a Spot-Check measurement ready to be sent and it is in the Advertising state (it is</p>                                                                                             |                       |                    |
+
+discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.
+
+2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
+  - a. PLX Features (0x2A60)
+    - i. Field: Supported Features
+      - Format: 16 bit
+      - Value: 0000 0000 0000 1100 (MSB → LSB). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).
+    - ii. Field: Measurement Status Support
+      - This field is not included
+    - iii. Field: Device and Sensor Status Support
+      - This field is not included
+  - b. PLX Spot-Check Measurement (0x2A5E)
+    - i. Field: Flags
+      - Format: 8 bit
+      - Value: 0000 0001 (MSB → LSB). Timestamp field is present. Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.
+    - ii. Field: SpO2PR-Spot-Check - SpO2 (%)
+      - Format: SFLOAT
+      - Value: 07 FF (hex). Special value: NaN
+    - iii. Field: SpO2PR-Spot-Check – PR (bpm)
+      - Format: SFLOAT
+      - Value: Not Relevant
+    - iv. Field: Time Stamp
+      - Format: Date and Time
+      - Value: Not Relevant
+    - v. Field: Measurement Status
+      - This field is not included
+    - vi. Field: Device and Sensor Status
+      - This field is not included
+    - vii. Field: Pulse Amplitude Index (%)
+      - 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 PLX Features characteristic.
+5. The simulated PHD sends the Measurement to the PHG under test.
+6. Check in PHG transcoder output the SpO2 Numeric Object – Basic-Nu-Observed-Value attribute
+7. IF C\_MAN\_BLE\_042 = TRUE (PHG supports RACP) THEN
+  - a) 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 spot-check measurement to PHG under test
+  - b) Check in PHG transcoder output the SpO2 Numeric Object – Basic-Nu-Observed-Value attribute
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Pass/Fail criteria</b>                   | In Step 6, the SpO2 Numeric Object – Basic-Nu-Observed-Value attribute is present and its value is 0x07FF (NaN).<br>If the PHG supports RACP, the same criteria applies to Step 7.b.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes<br/>(To assist manual testing)</b> | Possible values in typical points of observation after transcoder output are:<br>a) IEEE 11073 Objects and Attributes<br>Basic-Nu-Observed-Value attribute is present:<br><ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)</li> <li><input type="checkbox"/> Attribute-type: SFLOAT</li> <li><input type="checkbox"/> Attribute-value: 07 FF (hex) or NaN (note that a decimal value is not allowed)</li> </ul> b) WAN PCD-01 message<br>PCD-01 message includes a segment like this with Basic-Nu-Observed-Value attribute value (check OBX-5):<br>OBX n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x  <br>262688^MDC_DIM_PERCENT^MDC  NAN  X  [current_date_time] |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |                       |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-020                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |                       |
+| <b>TP label</b>          | Whitepaper. SpO2 Numeric Object (Continuous Measurements) – Basic-Nu-Observed-Value Attribute 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |                       |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [Bluetooth PHDT v1.6] |                       |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | SpO2 Numeric 19; M    | Short Float Type 1; C |
+| <b>Test purpose</b>      | Check that:<br>PHG transcodes SpO2 value of the SpO2PR-Normal field in PLX Continuous Measurement characteristic into SpO2 Numeric Object (Continuous normal response) - Basic-Nu-Observed-Value attribute<br>[AND]<br>PHG transcodes SpO2 value of the SpO2PR-Fast field in PLX Continuous Measurement characteristic into SpO2 Numeric Object (Continuous fast response) - Basic-Nu-Observed-Value attribute<br>[AND]<br>PHG transcodes SpO2 value of the SpO2PR-Slow field in PLX Continuous Measurement characteristic into SpO2 Numeric Object (Continuous slow response) - Basic-Nu-Observed-Value attribute                                                                                                                                        |                       |                       |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |                       |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |                       |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |                       |
+| <b>Test procedure</b>    | 1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).<br>2. The Simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:<br>a. PLX Feature (0x2A60)<br>i. Field: Supported Features<br><ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0011 0000 (MSB → LSB). Fast and slow response modes are supported (bits 4 and 5).</li> </ul> ii. Field: Measurement Status Support<br><ul style="list-style-type: none"> <li>• This field is not included</li> </ul> |                       |                       |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>b. PLX Continuous Measurement (0x2A5F) <ul style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0011 (MSB → LSB). SpO2PR–Fast, SpO2PR–Slow fields are present. Measurement Status, Device and Sensor Status and Pulse Amplitude Index fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 96.0 (%)</li> </ul> </li> <li>iii. Field: SpO2PR-Normal - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: SpO2PR-Fast - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 98.0 (%)</li> </ul> </li> <li>v. Field: SpO2PR-Fast - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vi. Field: SpO2PR-Slow - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 94.0 (%)</li> </ul> </li> <li>vii. Field: SpO2PR-Slow - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>viii. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>ix. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>x. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> </li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Feature characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the SpO2 Numeric Object – Basic-Nu-Observed-Value attribute in all three SpO2 objects.</p> |
+| <b>Pass/Fail criteria</b> | <p>In Step 6,</p> <ul style="list-style-type: none"> <li>• The SpO2 Numeric Object (Continuous measurement normal) – Basic-Nu-Observed-Value attribute is present and its value matches with the value of the SpO2 subfield of the SpO2PR-Normal field in the PLX Continuous Measurement characteristic (96.0%).</li> <li>• The SpO2 Numeric Object (Continuous measurement fast) – Basic-Nu-Observed-Value attribute is present and its value matches with the value of the SpO2 subfield of the SpO2PR-Fast field in the PLX Continuous Measurement characteristic (98.0%).</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ul style="list-style-type: none"> <li>The SpO2 Numeric Object (Continuous measurement slow) – Basic-Nu-Observed-Value attribute is present and its value matches with the value of the SpO2 subfield of the SpO2PR-Slow field in the PLX Continuous Measurement characteristic (94.0%).</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a. IEEE 11073 Objects and Attributes</p> <p>SpO2 Numeric object (Continuous measurement normal):</p> <ul style="list-style-type: none"> <li>Supplemental-types attribute is not present.<br/>Basic-Nu-Observed-Value attribute is present: <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)</li> <li><input type="checkbox"/> Attribute-type: SFLOAT</li> <li><input type="checkbox"/> Attribute-value: 00 60 (hex) or F3 C0 (hex) or 96.0 (dec)</li> </ul> </li> </ul> <p>SpO2 Numeric object (Continuous measurement fast):</p> <ul style="list-style-type: none"> <li>Supplemental-types attribute is present: <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object (fast response)</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_SUPPLEMENTAL_TYPES (2657)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE of SEQUENCE {partition (INT-U16), code (INT-U16)}</li> <li><input type="checkbox"/> Attribute-value: {MDC_PART_SCADA, MDC_MODALITY_FAST}.</li> </ul> </li> <li>Basic-Nu-Observed-Value attribute is present: <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)</li> <li><input type="checkbox"/> Attribute-type: SFLOAT</li> <li><input type="checkbox"/> Attribute-value: 00 62 (hex) or F3D4 (hex) or 98.0 (dec)</li> </ul> </li> </ul> <p>SpO2 Numeric object (Continuous measurement slow):</p> <ul style="list-style-type: none"> <li>Supplemental-types attribute is present: <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object (slow response)</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_SUPPLEMENTAL_TYPES (2657)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE of SEQUENCE {partition (INT-U16), code (INT-U16)}</li> <li><input type="checkbox"/> Attribute-value: {MDC_PART_SCADA, MDC_MODALITY_SLOW}.</li> </ul> </li> <li>Basic-Nu-Observed-Value attribute is present: <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: SpO2 Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)</li> <li><input type="checkbox"/> Attribute-type: SFLOAT</li> <li><input type="checkbox"/> Attribute-value: 00 5E (hex) or F3AC (hex) or 94.0 (dec)</li> </ul> </li> </ul> <p>b. WAN PCD-01 message</p> <p>SpO2 Numeric object (Continuous measurement normal):</p> <p>PCD-01 message includes a segment like this with Basic-Nu-Observed-Value attribute value (check OBX-5):</p> <pre>OBX n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x 96.0  262688^MDC_DIM_PERCENT^MDC   R  [current_date_time]</pre> <p>SpO2 Numeric object (Continuous measurement fast):</p> <p>PCD-01 message includes two segments like these for SpO2 Numeric object (Fast response), with Basic-Nu-Observed-Value attribute and Supplemental-Types attribute values (check OBX-5 in both segments):</p> <pre>OBX n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x 98.0 </pre> |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <p>262688^MDC_DIM_PERCENT^MDC    R  [current_date_time]</p> <p>OBX n CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y </p> <p><b>150580^MDC_MODALITY_FAST^MDC</b>    [obx-11 of the parent]</p> <p>SpO2 Numeric object (Continuous measurement slow):</p> <p>PCD-01 message includes two segments like these for SpO2 Numeric object (Slow response), with Basic-Nu-Observed-Value attribute and Supplemental-Types attribute values (check OBX-5 in both segments):</p> <p>OBX n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x <b>94.0</b> </p> <p>262688^MDC_DIM_PERCENT^MDC    R  [current_date_time]</p> <p>OBX n CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y </p> <p><b>150580^MDC_MODALITY_SLOW^MDC</b>    [obx-11 of the parent]</p> |
+|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |                    |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-021                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                       |                    |
+| <b>TP label</b>          | Whitepaper. SpO2 Numeric Object (Continuous Measurements) – Basic-Nu-Observed-Value Attribute 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |                    |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [Bluetooth PHDT v1.6] |                    |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | SpO2 Numeric 19; M    | SpO2 Numeric 20; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG transcodes SpO2 value of the SpO2PR-Normal field in PLX Continuous Measurement characteristic into SpO2 Numeric Object (Continuous normal response) - Basic-Nu-Observed-Value attribute</p> <p>[AND]</p> <p>PHG transcodes SpO2 value of the SpO2PR-Fast field in PLX Continuous Measurement characteristic into SpO2 Numeric Object (Continuous fast response) - Basic-Nu-Observed-Value attribute</p> <p>[AND]</p> <p>PHG transcodes SpO2 value of the SpO2PR-Slow field in PLX Continuous Measurement characteristic into SpO2 Numeric Object (Continuous slow response) - Basic-Nu-Observed-Value attribute</p> <p>[AND]</p> <p>PHG assigns special value NaN (0x07FF) when SpO2 value is unavailable.</p>                                                                                                                                                                                                                                                                                                                                                                     |                       |                    |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |                    |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |                    |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |                    |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Feature (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0011 0000 (MSB → LSB). Fast and slow response modes are supported (bits 4 and 5).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Continuous Measurement (0x2A5F)</li> </ol> </li> </ol> |                       |                    |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0011 (MSB → LSB). SpO2PR-Fast, SpO2PR-Slow fields are present. Measurement Status, Device and Sensor Status and Pulse Amplitude Index fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 07 FF (hex). Special value: NaN</li> </ul> </li> <li>iii. Field: SpO2PR-Normal - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: SpO2PR-Fast - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 07 FF (hex). Special value: NaN</li> </ul> </li> <li>v. Field: SpO2PR-Fast - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vi. Field: SpO2PR-Slow - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 07 FF (hex). Special value: NaN</li> </ul> </li> <li>vii. Field: SpO2PR-Slow - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>viii. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>ix. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>x. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> <ol style="list-style-type: none"> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Feature characteristic.</li> <li>5. The simulated PHD sends the Measurement to the PHG under test.</li> <li>6. Check in PHG transcoder output the SpO2 Numeric Object – Basic-Nu-Observed-Value attribute for all SpO2 objects.</li> </ol> |
+| <b>Pass/Fail criteria</b>                   | In Step 6, <ul style="list-style-type: none"> <li>• The SpO2 Numeric Object (Continuous measurement normal) – Basic-Nu-Observed-Value attribute is present and its value is 0x07FF (NaN).</li> <li>• The SpO2 Numeric Object (Continuous measurement fast) – Basic-Nu-Observed-Value attribute is present and its value is 0x07FF (NaN).</li> <li>• The SpO2 Numeric Object (Continuous measurement slow) – Basic-Nu-Observed-Value attribute is present and its value is 0x07FF (NaN).</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes<br/>(To assist manual testing)</b> | Possible values in typical points of observation after transcoder output are:<br>a) IEEE 11073 Objects and Attributes<br>SpO2 Numeric object (Continuous measurement normal):                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+- Supplemental-types attribute is not present.
+
+Basic-Nu-Observed-Value attribute is present:
+
+- Object: SpO2 Numeric Object
+- Attribute-id: MDC\_ATTR\_NU\_VAL\_OBS\_BASIC (2636)
+- Attribute-type: SFLOAT
+- Attribute-value: Attribute-value: 07 FF (hex) or NaN (note that a decimal value is not allowed)
+
+SpO2 Numeric object (Continuous measurement fast):
+
+- Supplemental-types attribute is present:
+  - Object: SpO2 Numeric Object (fast response)
+  - Attribute-id: MDC\_ATTR\_SUPPLEMENTAL\_TYPES (2657)
+  - Attribute-type: SEQUENCE of SEQUENCE {partition (INT-U16), code (INT-U16)}
+  - Attribute-value: {MDC\_PART\_SCADA, MDC\_MODALITY\_FAST}.
+- Basic-Nu-Observed-Value attribute is present:
+  - Object: SpO2 Numeric Object
+  - Attribute-id: MDC\_ATTR\_NU\_VAL\_OBS\_BASIC (2636)
+  - Attribute-type: SFLOAT
+  - Attribute-value: Attribute-value: 07 FF (hex) or NaN (note that a decimal value is not allowed)
+
+SpO2 Numeric object (Continuous measurement slow):
+
+- Supplemental-types attribute is present:
+  - Object: SpO2 Numeric Object (slow response)
+  - Attribute-id: MDC\_ATTR\_SUPPLEMENTAL\_TYPES (2657)
+  - Attribute-type: SEQUENCE of SEQUENCE {partition (INT-U16), code (INT-U16)}
+  - Attribute-value: {MDC\_PART\_SCADA, MDC\_MODALITY\_SLOW}.
+- Basic-Nu-Observed-Value attribute is present:
+  - Object: SpO2 Numeric Object
+  - Attribute-id: MDC\_ATTR\_NU\_VAL\_OBS\_BASIC (2636)
+  - Attribute-type: SFLOAT
+  - Attribute-value: Attribute-value: 07 FF (hex) or NaN (note that a decimal value is not allowed)
+
+#### b) WAN PCD-01 message
+
+SpO2 Numeric object (Continuous measurement normal):
+
+PCD-01 message includes a segment like this with Basic-Nu-Observed-Value attribute value (check OBX-5):
+
+```
+OBX|n|NM|150456^MDC_PULS_OXIM_SAT_O2^MDC|m.0.0.x||
+262688^MDC_DIM_PERCENT^MDC||NAN||X||[current_date_time]
+```
+
+SpO2 Numeric object (Continuous measurement fast):
+
+PCD-01 message includes two segments like these for SpO2 Numeric object (Fast response), with Basic-Nu-Observed-Value attribute and Supplemental-Types attribute values (check OBX-5 in both segments):
+
+```
+OBX|n|NM|150456^MDC_PULS_OXIM_SAT_O2^MDC|m.0.0.x||
+262688^MDC_DIM_PERCENT^MDC||NAN||X||[current_date_time]
+```
+
+```
+OBX|n|CWE|68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC|m.0.0.x|y|
+150580^MDC_MODALITY_FAST^MDC|||||[obx-11 of the parent]
+```
+
+SpO2 Numeric object (Continuous measurement slow):
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <p>PCD-01 message includes two segments like these for SpO2 Numeric object (Slow response), with Basic-Nu-Observed-Value attribute and Supplemental-Types attribute values (check OBX-5 in both segments):</p> <pre>OBX n NM 150456^MDC_PULS_OXIM_SAT_O2^MDC m.0.0.x   262688^MDC_DIM_PERCENT^MDC  NAN  X  [current_date_time]</pre> <pre>OBX n CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y  150580^MDC_MODALITY_SLOW^MDC     [obx-11 of the parent]</pre> |
+|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |                     |                   |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|-------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-022                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |                     |                   |
+| <b>TP label</b>          | Whitepaper. SpO2 measurement value (Spot-Check Measurement)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |                     |                   |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [Bluetooth PHDT v1.6] |                     |                   |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Short Float Type 1; C | Date-Time Conv 1; M | SpO2 Numeric 9; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | SpO2 Numeric 10; M    |                     |                   |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG processes correctly the SpO2 value (%) of the SpO2PR-Spot-Check field and the value of the Time Stamp field of the PLX Spot-Check characteristic</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |                     |                   |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                       |                     |                   |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |                     |                   |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |                     |                   |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a Spot-Check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 1100 (MSB → LSB). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0001 (MSB → LSB). Timestamp field is present. Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 96.0 (%)</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp</li> </ol> </li> </ol> </li> </ol> |                       |                     |                   |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: October 12nd, 2015, 10:39:27</li> </ul> <p>v. Field: Measurement Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>vi. Field: Device and Sensor Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>vii. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check that the PHG accepts the measurement and decodes its value properly (SpO2 measurement value, units and time stamp).</p> <p>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <p style="padding-left: 20px;">a) 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 spot-check measurement to PHG under test</p> <p style="padding-left: 20px;">b) Check that PHG accepts the measurement and decodes its value properly (SpO2 measurement value, units and time stamp)</p> |
+| <b>Pass/Fail criteria</b> | <p>In Step 6, the PHG under test shows the following measurement SpO2 = 96.0 (%) with timestamp '2015-10-12 10:39:27'.</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |  |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-023                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |  |
+| <b>TP label</b>          | Whitepaper. Pulse Rate Numeric Object (Spot-Check Measurement) - Handle Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | PR Numeric 1; O       |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG does not include Pulse Rate Numeric Object – Handle Attribute in transcoder output when using spot-check measurement mode.</p> <p>[OR]</p> <p>If PHG includes Pulse Rate Numeric Object – Handle attribute in transcoder output, then its value shall be different than 0</p>                                                                                                                                                                                                                                                                                     |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |  |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                       |  |
+| <b>Test procedure</b>    | <p>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</p> <p>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:</p> <p style="padding-left: 20px;">a. PLX Features (0x2A60)</p> <p style="padding-left: 40px;">i. Field: Supported Features</p> |                       |  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 <b>1100</b> (MSB → LSB). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> <ul style="list-style-type: none"> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> <p>b. PLX Spot-Check Measurement (0x2A5E)</p> <ul style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0001 (MSB → LSB). Timestamp field is present. Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> <ol style="list-style-type: none"> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</li> <li>5. The simulated PHD sends the measurement to the PHG under test.</li> <li>6. Check in PHG transcoder output the Pulse Rate Numeric Object – Handle attribute</li> <li>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN <ol style="list-style-type: none"> <li>a) 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 spot-check measurement to the PHG under test</li> <li>b) Check in PHG transcoder output the SpO2 Numeric Object – Handle attribute</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the Pulse Rate Numeric Object – Handle attribute is not present or, if it is present then its value is different than 0.</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Handle attribute is not present, or if it is present then:</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_HANDLE (2337)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: Any value different than 0</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message does not include segments with Handle attribute value</p> |
+|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-024                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |  |
+| <b>TP label</b>          | Whitepaper. Pulse Rate Numeric Object (Continuous Measurements) - Handle Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | PR Numeric 11; O      |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG does not include Pulse Rate Numeric Object – Handle Attribute in transcoder output when using continuous measurements</p> <p>[OR]</p> <p>If PHG includes Pulse Rate Numeric Object – Handle attribute in transcoder output, then its value shall be different than 0</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                       |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0011 0000 (MSB → LSB). Fast and slow response modes are supported (bits 4 and 5).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Continuous Measurement (0x2A5F) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0011 (MSB → LSB). SpO2PR-Fast, SpO2PR-Slow fields are present. Measurement Status, Device and Sensor Status and Pulse Amplitude Index fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Normal – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                       |  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ul style="list-style-type: none"> <li>• Value: Not Relevant</li> </ul> <p>iv. Field: SpO2PR-Fast - SpO2 (%)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>v. Field: SpO2PR-Fast - PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>vi. Field: SpO2PR-Slow - SpO2 (%)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>vii. Field: SpO2PR-Slow - PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>viii. Field: Measurement Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>ix. Field: Device and Sensor Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>x. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the Pulse Rate Numeric Object – Handle attribute in all three Pulse Rate objects (continuous normal, fast and slow).</p> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6,</p> <ul style="list-style-type: none"> <li>• There are three Pulse Rate objects (for normal, fast and slow measurement modes).</li> <li>• In all three objects, the Pulse Rate Numeric Object – Handle attribute is not present or, if it is present then its value is different than 0</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Handle attribute is not present in SpO2 objects, or if it is present then:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_HANDLE (2337)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: Any value different than 0</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message does not include segments with Handle attribute value</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                 |                                                                                 |                       |  |
+|-----------------|---------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>    | TP/LP-PAN/PHG/PHDTW/PLX/BV-025                                                  |                       |  |
+| <b>TP label</b> | Whitepaper. Pulse Rate Numeric Object (Spot-Check Measurement) - Type Attribute |                       |  |
+| <b>Coverage</b> | <b>Spec</b>                                                                     | [Bluetooth PHDT v1.6] |  |
+|                 | <b>Testable items</b>                                                           | PR Numeric 2; M       |  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Pulse Rate Numeric Object – Type attribute in transcoder output when using spot-check measurement mode.</p> <p>[AND]</p> <p>Type is set to {MDC_PART_SCADA, MDC_PULS_OXIM_PULS_RATE}</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 1100 (MSB → LSB). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0001 (MSB → LSB). Timestamp field is present. Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> <li>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).</li> </ol> |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the Pulse Rate Numeric Object – Type attribute</p> <p>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <p style="padding-left: 20px;">a) 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 spot-check measurement to PHG under test</p> <p style="padding-left: 20px;">b) Check in PHG transcoder output the SpO2 Numeric Object – Type attribute</p>                                                                                                                                                                                                                                                              |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the Pulse Rate Numeric Object – Type attribute is present and its value is {MDC_PART_SCADA, MDC_PULS_OXIM_PULS_RATE}</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p style="padding-left: 20px;">Type attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_TYPE (2351)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}</li> <li><input type="checkbox"/> Attribute-value: <ul style="list-style-type: none"> <li>• partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)</li> <li>• code: MDC_PULS_OXIM_PULS_RATE or 18458 (dec) or 48 1A (hex)</li> </ul> </li> </ul> <p>b) WAN PCD-01 message</p> <p style="padding-left: 20px;">PCD-01 message includes a segment like this with Type attribute (check OBX-3):</p> <p style="padding-left: 40px;">OBX n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x [value] 264864^MDC_DIM_BEAT_PER_MIN^MDC    R  [current_date_time]</p> |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |  |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-026                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |  |
+| <b>TP label</b>          | Whitepaper. Pulse Rate Numeric Object (Continuous Measurements) - Type Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                          |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | SpO2 Numeric 12; M    |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Pulse Rate Numeric Object – Type attribute in transcoder output when using continuous measurements.</p> <p>[AND]</p> <p>Type is set to {MDC_PART_SCADA, MDC_PULS_OXIM_PULS_RATE}</p>                                                                                                                                                                                                                                                                                                   |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |  |
+| <b>Test procedure</b>    | <p>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</p> <p>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:</p> <p style="padding-left: 20px;">a. PLX Features (0x2A60)</p> <p style="padding-left: 40px;">i. Field: Supported Features</p> |                       |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0011 0000 (MSB → LSB). Fast and slow response modes are supported (bits 4 and 5).</li> </ul> <p>ii. Field: Measurement Status Support</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>iii. Field: Device and Sensor Status Support</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>b. PLX Continuous Measurement (0x2A5F)</p> <p>i. Field: Flags</p> <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0011 (MSB → LSB). SpO2PR-Fast, SpO2PR-Slow fields are present. Measurement Status, Device and Sensor Status and Pulse Amplitude Index fields are not present.</li> </ul> <p>ii. Field: SpO2PR-Normal - SpO2 (%)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>iii. Field: SpO2PR-Normal – PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>iv. Field: SpO2PR-Fast - SpO2 (%)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>v. Field: SpO2PR-Fast - PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>vi. Field: SpO2PR-Slow - SpO2 (%)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>vii. Field: SpO2PR-Slow - PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>viii. Field: Measurement Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>ix. Field: Device and Sensor Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>x. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the Pulse Rate Numeric Object – Type attribute in all three Pulse Rate objects (continuous normal, fast and slow).</p> |
+| <b>Pass/Fail criteria</b> | In Step 6,                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ul style="list-style-type: none"> <li>• There are three Pulse Rate objects (for normal, fast and slow measurement modes).</li> <li>• In all three objects, the Pulse Rate Numeric Object – Type attribute is present and its value is {MDC_PART_SCADA, MDC_PULS_OXIM_PULS_RATE}</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Type attribute is present in all three SpO2 objects:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_TYPE (2351)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}</li> <li><input type="checkbox"/> Attribute-value: <ul style="list-style-type: none"> <li>• partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)</li> <li>• code: MDC_PULS_OXIM_PULS_RATE or 18458 (dec) or 48 1A (hex)</li> </ul> </li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes three segments like this with Type attribute (check OBX-3):</p> <p>OBX n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x [value]<br/>264864^MDC_DIM_BEAT_PER_MIN^MDC   R   current_date_time]</p> |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                       |  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-027                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |  |
+| <b>TP label</b>          | Whitepaper. Pulse Rate Numeric Object (Spot-Check Measurement) – Supplemental-Types Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | PR Numeric 3; M       |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Pulse Rate Numeric Object – Supplemental-Types attribute in transcoder output when using spot-check measurement mode.</p> <p>[AND]</p> <p>Supplemental-Types attribute is set to {MDC_PART_SCADA, MDC_MODALITY_SPOT}.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |  |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>PLX Features (0x2A60) <ol style="list-style-type: none"> <li>Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 1100 (MSB → LSB). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                       |  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>b. PLX Spot-Check Measurement (0x2A5E)</p> <ul style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0001 (MSB → LSB). Timestamp field is present. Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the Pulse Rate Numeric Object – Supplemental-Types attribute</p> <p>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <ul style="list-style-type: none"> <li>a) 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 spot-check measurement to PHG under test</li> <li>b) Check in PHG transcoder output the Pulse Rate Numeric Object – Supplemental-Types attribute</li> </ul> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the Pulse Rate Numeric Object – Supplemental-Types attribute is present and its value is {MDC_PART_SCADA, MDC_MODALITY_SPOT}.</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Supplemental-Types attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object (Spot-Check measurement)</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_SUPPLEMENTAL_TYPES (2657)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE of SEQUENCE {partition (INT-U16), code (INT-U16)}</li> <li><input type="checkbox"/> Attribute-value: {MDC_PART_SCADA, MDC_MODALITY_SPOT}.</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a facet OBX segment of the SpO2 measurement OBX segment with Supplemental-Types attribute (check OBX-3 and OBX-5):</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|  |                                                                                                                                                                                                                                 |
+|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | OBX n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x [value]<br>264864^MDC_DIM_BEAT_PER_MIN^MDC    R  [current_date_time]<br><br>OBX n CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y <br>150580^MDC_MODALITY_SPOT^MDC    R |
+|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |                  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-028                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |                  |
+| <b>TP label</b>          | Whitepaper. Pulse Rate Numeric Object (Continuous Measurements) – Supplemental-Types Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [Bluetooth PHDT v1.6] |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | PR Numeric 13; M      | PR Numeric 14; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG does not include Pulse Rate Numeric Object – Supplemental-Types attribute in transcoder output for the Pulse Rate continuous measurement object (normal).</p> <p>[AND]</p> <p>PHG includes Pulse Rate Numeric Object – Supplemental-Types attribute in transcoder output for the Pulse Rate continuous measurement object (fast mode). Supplemental-Types attribute is set to {MDC_PART_SCADA, MDC_MODALITY_FAST}.</p> <p>[AND]</p> <p>PHG includes Pulse Rate Numeric Object – Supplemental-Types attribute in transcoder output for the Pulse Rate continuous measurement object (slow mode). Supplemental-Types attribute is set to {MDC_PART_SCADA, MDC_MODALITY_SLOW}.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |                  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |                  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |                  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0011 0000 (MSB → LSB). Fast and slow response modes are supported (bits 4 and 5).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Continuous Measurement (0x2A5F) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0011 (MSB → LSB). SpO2PR-Fast, SpO2PR-Slow fields are present. Measurement Status, Device and Sensor Status and Pulse Amplitude Index fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Normal - PR (bpm)</li> </ol> </li> </ol> </li> </ol> |                       |                  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>iv. Field: SpO2PR-Fast - SpO2 (%)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>v. Field: SpO2PR-Fast - PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>vi. Field: SpO2PR-Slow - SpO2 (%)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>vii. Field: SpO2PR-Slow - PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>viii. Field: Measurement Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>ix. Field: Device and Sensor Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>x. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in the PHG transcoder output the Pulse Rate Numeric Object – Supplemental-Types attribute in all three Pulse Rate objects (continuous normal, fast and slow).</p> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6,</p> <ul style="list-style-type: none"> <li>• The Pulse Rate Numeric Object (normal) – Supplemental-Types attribute is not present</li> <li>• The Pulse Rate Numeric Object (fast response) Supplemental-Types attribute is present and its value is {MDC_PART_SCADA, MDC_MODALITY_FAST}.</li> <li>• The Pulse Rate Numeric Object (slow response) Supplemental-Types attribute is present and its value is {MDC_PART_SCADA, MDC_MODALITY_SLOW}.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Supplemental Types attribute is not present for Pulse Rate Numeric Object (normal).</p> <p>Supplemental-Types attribute is present for Pulse Rate Numeric Object (fast response):</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object (fast response)</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_SUPPLEMENTAL_TYPES (2657)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE of SEQUENCE {partition (INT-U16), code (INT-U16)}</li> <li><input type="checkbox"/> Attribute-value: {MDC_PART_SCADA, MDC_MODALITY_FAST}.</li> </ul> <p>Supplemental-Types attribute is present for Pulse Rate Numeric Object (slow response):</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object (slow response)</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_SUPPLEMENTAL_TYPES (2657)</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <ul style="list-style-type: none"> <li><input type="checkbox"/> Attribute-type: SEQUENCE of SEQUENCE {partition (INT-U16), code (INT-U16)}</li> <li><input type="checkbox"/> Attribute-value: {MDC_PART_SCADA, MDC_MODALITY_SLOW}.</li> </ul> <p>b) WAN PCD-01 message</p> <p>For Pulse Rate Numeric Object (normal)</p> <ul style="list-style-type: none"> <li>• PCD-01 message does not include segments with Supplemental-Types attribute.</li> </ul> <p>For Pulse Rate Numeric Object (fast)</p> <ul style="list-style-type: none"> <li>• PCD-01 message includes a facet OBX segment of the Pulse Rate measurement OBX segment with Supplemental-Types attribute (check OBX-3 and OBX-5):           <pre>OBX n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x [value]<br/>264864^MDC_DIM_BEAT_PER_MIN^MDC    R  [current_date_time]</pre> <pre>OBX n CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y <br/>150580^MDC_MODALITY_FAST^MDC    R</pre> </li> </ul> <p>For Pulse Rate Numeric Object (slow)</p> <ul style="list-style-type: none"> <li>• PCD-01 message includes a facet OBX segment of the Pulse Rate measurement OBX segment with Supplemental-Types attribute (check OBX-3 and OBX-5):           <pre>OBX n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x [value]<br/>264864^MDC_DIM_BEAT_PER_MIN^MDC    R  [current_date_time]</pre> <pre>OBX n CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.y.z <br/>150580^MDC_MODALITY_SLOW^MDC    R</pre> </li> </ul> |
+|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                       |                 |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-029                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |                 |
+| <b>TP label</b>          | Whitepaper. Pulse Rate Numeric Object (Spot-Check Measurement) - Metric-Spec-Small Attribute 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | [Bluetooth PHDT v1.6] |                 |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | PR Numeric 4; M       | PR Numeric 6; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Pulse Rate Numeric Object – Metric-Spec-Small attribute in transcoder output when using spot-check measurement mode.</p> <p>[AND]</p> <p>Metric-Spec-Small is set to {0x5040} when the sensor device supports measurement storage.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |                 |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |                 |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |                 |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:           <ol style="list-style-type: none"> <li>a. PLX Spot-Check Measurement (0x2A5E)</li> <li>b. PLX Feature (0x2A60)               <ol style="list-style-type: none"> <li>i. Field: Supported Features                   <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 1100 (MSB → LSB). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported.</li> </ul> </li> <li>ii. Field: Measurement Status Support</li> </ol> </li> </ol> </li> </ol> |                       |                 |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>iii. Field: Device and Sensor Status Support</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Feature characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test with the following value:</p> <p>a. PLX Spot-Check Measurement (0x2A5E)</p> <ul style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0001 (MSB → LSB). Timestamp field is present. Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> <p>6. Check in the PHG transcoder output the Pulse Rate Numeric Object – Metric-Spec-Small attribute</p> <p>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <p>a) 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 spot-check measurement to PHG under test</p> <p>b) Check in PHG transcoder output the Pulse Rate Numeric Object – Metric-Spec-Small attribute</p> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the Pulse Rate Numeric Object – Metric-Spec-Small attribute is present and its value is {0x5040} (mss-avail-stored-data  mss-msmt-aperiodic  mss-acc-agent-initiated).</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Metric-Spec-Small attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <ul style="list-style-type: none"> <li><input type="checkbox"/> Attribute-type: BITS-16</li> <li><input type="checkbox"/> Attribute-value: 50 40 (hex) or BITS mss-avail-stored-data (1), mss- msmt - aperiodic(3), mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message does not include segments with Metric-Spec-Small attribute value</p> |
+|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |                 |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-030                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |                 |
+| <b>TP label</b>          | Whitepaper. Pulse Rate Numeric Object (Spot-Check Measurement) - Metric-Spec-Small Attribute 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [Bluetooth PHDT v1.6] |                 |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | PR Numeric 4; M       | PR Numeric 5; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Pulse Rate Numeric Object – Metric-Spec-Small attribute in transcoder output when using spot-check measurement mode.</p> <p>[AND]</p> <p>Metric-Spec-Small is set to {0x1040} when the sensor device does not support measurement storage.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |                 |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |                 |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |                 |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ul style="list-style-type: none"> <li>a. PLX Spot-Check Measurement (0x2A5E)</li> <li>b. PLX Features (0x2A60) <ul style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 0000 (MSB → LSB). Measurement Storage for Spot-check measurements is not supported (bit 2).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> </li> </ul> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</li> <li>5. The simulated PHD sends the Measurement to the PHG under test with the following value: <ul style="list-style-type: none"> <li>a. PLX Spot-Check Measurement (0x2A5E) <ul style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0000 (MSB → LSB). Timestamp, Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> </ul> </li> </ul> </li> </ol> |                       |                 |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>ii. Field: SpO2PR-Spot-Check - SpO2 (%)</p> <ul style="list-style-type: none"> <li>Format: SFLOAT</li> <li>Value: Not Relevant</li> </ul> <p>iii. Field: SpO2PR-Spot-Check – PR (bpm)</p> <ul style="list-style-type: none"> <li>Format: SFLOAT</li> <li>Value: Not Relevant</li> </ul> <p>iv. Field: Time Stamp</p> <ul style="list-style-type: none"> <li>This field is not included</li> </ul> <p>v. Field: Measurement Status</p> <ul style="list-style-type: none"> <li>This field is not included</li> </ul> <p>vi. Field: Device and Sensor Status</p> <ul style="list-style-type: none"> <li>This field is not included</li> </ul> <p>vii. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>This field is not included</li> </ul> <p>6. Check in the PHG transcoder output the Pulse Rate Numeric Object – Metric-Spec-Small attribute</p> |
+| <b>Pass/Fail criteria</b>                   | In Step 6, the Pulse Rate Numeric Object – Metric-Spec-Small attribute is present and its value is {0x1040} (mss-msmt-aperiodic   mss-acc-agent-initiated).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Metric-Spec-Small attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)</li> <li><input type="checkbox"/> Attribute-type: BITS-16</li> <li><input type="checkbox"/> Attribute-value: 10 40 (hex) or BITS mss-msmt-aperiodic(3), mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message does not include segments with Metric-Spec-Small attribute value</p>                                                                                                                                                |
+
+|                          |                                                                                                                                                                                                                                                                  |                       |  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-031                                                                                                                                                                                                                                   |                       |  |
+| <b>TP label</b>          | Whitepaper. Pulse Rate Numeric Object (Continuous Measurements) - Metric-Spec-Small Attribute                                                                                                                                                                    |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                      | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                            | PR Numeric 16; M      |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Pulse Rate Numeric Object – Metric-Spec-Small attribute in transcoder output when using continuous measurements.</p> <p>[AND]</p> <p>Metric-Spec-Small is set to {0x0040} (mss-acc-agent-initiated)</p>                       |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                |                       |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                  |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                               |                       |  |
+| <b>Test procedure</b>    | <p>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</p> |                       |  |
+
+2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:
+  - a. PLX Features (0x2A60)
+    - i. Field: Supported Features
+      - Format: 16 bit
+      - Value: 0000 0000 0011 0000 (MSB → LSB). Fast and slow response modes are supported (bits 4 and 5).
+    - ii. Field: Measurement Status Support
+      - This field is not included
+    - iii. Field: Device and Sensor Status Support
+      - This field is not included
+  - b. PLX Continuous Measurement (0x2A5F)
+    - i. Field: Flags
+      - Format: 8 bit
+      - Value: 0000 0011 (MSB → LSB). SpO2PR-Fast, SpO2PR-Slow fields are present. Measurement Status, Device and Sensor Status and Pulse Amplitude Index fields are not present.
+    - ii. Field: SpO2PR-Normal - SpO2 (%)
+      - Format: SFLOAT
+      - Value: Not Relevant
+    - iii. Field: SpO2PR-Normal – PR (bpm)
+      - Format: SFLOAT
+      - Value: Not Relevant
+    - iv. Field: SpO2PR-Fast - SpO2 (%)
+      - Format: SFLOAT
+      - Value: Not Relevant
+    - v. Field: SpO2PR-Fast - PR (bpm)
+      - Format: SFLOAT
+      - Value: Not Relevant
+    - vi. Field: SpO2PR-Slow - SpO2 (%)
+      - Format: SFLOAT
+      - Value: Not Relevant
+    - vii. Field: SpO2PR-Slow - PR (bpm)
+      - Format: SFLOAT
+      - Value: Not Relevant
+    - viii. Field: Measurement Status
+      - This field is not included
+    - ix. Field: Device and Sensor Status
+      - This field is not included
+    - x. Field: Pulse Amplitude Index (%)
+      - 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 PLX Features characteristic.
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the Pulse Rate Numeric Object – Metric-Spec-Small attribute in all three Pulse Rate objects (continuous normal, fast and slow).</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6,</p> <ul style="list-style-type: none"> <li>• There are three Pulse Rate objects (for normal, fast and slow measurement modes).</li> <li>• In all three objects, the Pulse Rate Numeric Object – Metric-Spec-Small attribute is present and its value is {0x0040} (mss-acc-agent-initiated).</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Metric-Spec-Small attribute is present in all three SpO2 objects:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)</li> <li><input type="checkbox"/> Attribute-type: BITS-16</li> <li><input type="checkbox"/> Attribute-value: 00 40 (hex) or BITS mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message does not include segments with Metric-Spec-Small attribute value</p> |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |  |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-032                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |  |
+| <b>TP label</b>          | Whitepaper. Pulse Rate Numeric Object (Spot-Check Measurement) – Measurement-Status Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | PR Numeric 7; M       |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Pulse Rate Numeric Object – Measurement-Status attribute in transcoder output when using spot-check measurement mode.</p> <p>[AND]</p> <p>PHG transcodes the Bluetooth Measurement Status field of the PLX Spot-Check characteristic to 11073 Measurement-Status attribute properly</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                       |  |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Spot-Check Measurement (0x2A5E)</li> <li>b. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 1101 (MSB → LSB). Measurement Status support is present (bit 0). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support</li> </ol> </li> </ol> </li> </ol> |                       |  |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: <b>1111 1111 1110 0000</b> (MSB → LSB). All Measurement Status bits are supported</li> </ul> <p>iii. Field: Device and Sensor Status Support</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Feature characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test with the following value:</p> <p>a. PLX Spot-Check Measurement (0x2A5E)</p> <ul style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: <b>0000 0011</b> (MSB → LSB). Timestamp and Measurement Status fields are present. Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: October 12nd, 2015, 10:39:27 <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: <b>1000 0000 0000 0000</b> (MSB → LSB). Invalid measurement detected (bit 15).</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> <p>6. Check in PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute</p> <p>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <p>a) 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 spot-check measurement to PHG under test</p> <p>b) Check in PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute</p> <p>8. Simulated PHD sends a Measurement to PHG under test with Measurement Status field set to <b>0100 0000 0000 0000</b> (MSB → LSB), questionable measurement detected (bit 14). All remaining fields remain equal to those in step 5. Simulated PHD also deletes all stored records in RACP and stores an identical measurement.</p> <p>9. Check in PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute</p> |
+|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+10. IF C\_MAN\_BLE\_042 = TRUE (PHG supports RACP) THEN
+  - a) 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 spot-check measurement to PHG under test
+  - b) Check in PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute
+11. Simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0010 0000 0000 0000 (MSB → LSB), measurement not available (bit 13). All remaining fields remain equal to those in step 5. Simulated PHD also deletes all stored records in RACP and stores an identical measurement.
+12. Check in PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute
+13. IF C\_MAN\_BLE\_042 = TRUE (PHG supports RACP) THEN
+  - a) 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 spot-check measurement to PHG under test
+  - b) Check in PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute
+14. Simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0001 0000 0000 0000 (MSB → LSB), calibration ongoing (bit 12). All remaining fields remain equal to those in step 5. Simulated PHD also deletes all stored records in RACP and stores an identical measurement.
+15. Check in PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute
+16. IF C\_MAN\_BLE\_042 = TRUE (PHG supports RACP) THEN
+  - a) 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 spot-check measurement to PHG under test
+  - b) Check in PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute
+17. Simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0000 1000 0000 0000 (MSB → LSB), data for testing (bit 11). All remaining fields remain equal to those in step 5. Simulated PHD also deletes all stored records in RACP and stores an identical measurement.
+18. Check in PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute
+19. IF C\_MAN\_BLE\_042 = TRUE (PHG supports RACP) THEN
+  - a) 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 spot-check measurement to PHG under test
+  - b) Check in PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute
+20. Simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0000 0100 0000 0000 (MSB → LSB), data for demonstration (bit 10). All remaining fields remain equal to those in step 5. Simulated PHD also deletes all stored records in RACP and stores an identical measurement.
+21. Check in PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute
+22. IF C\_MAN\_BLE\_042 = TRUE (PHG supports RACP) THEN
+  - a) 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 spot-check measurement to PHG under test
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>b) Check in PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute</li> </ul> <ol style="list-style-type: none"> <li>Simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0000 0000 1000 0000 (MSB → LSB), fully qualified data (bit 7). All remaining fields remain equal to those in step 5. Simulated PHD also deletes all stored records in RACP and stores an identical measurement.</li> <li>Check in PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute</li> <li>IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN <ol style="list-style-type: none"> <li>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 spot-check measurement to PHG under test</li> <li>Check in PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute</li> </ol> </li> <li>Simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0000 0000 0100 0000 (MSB → LSB), early estimated data (bit 6). All remaining fields remain equal to those in step 5. Simulated PHD also deletes all stored records in RACP and stores an identical measurement.</li> <li>Check in PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute</li> <li>IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN <ol style="list-style-type: none"> <li>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 spot-check measurement to PHG under test</li> <li>Check in PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute</li> </ol> </li> <li>Simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0000 0000 0010 0000 (MSB → LSB), measurement ongoing (bit 5). All remaining fields remain equal to those in step 5. Simulated PHD also deletes all stored records in RACP and stores an identical measurement.</li> <li>Check in PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute</li> <li>IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN <ol style="list-style-type: none"> <li>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 spot-check measurement to PHG under test</li> <li>Check in PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <p>In Step 6, the Pulse Rate Numeric Object – Measurement-Status attribute is present and its set to “invalid” (0x8000). If PHG supports RACP, same criteria applies to 7.b.</p> <p>In Step 9, the Pulse Rate Numeric Object – Measurement-Status attribute is present and its set to “questionable” (0x4000). If PHG supports RACP, same criteria applies to 10.b.</p> <p>In Step 12, the Pulse Rate Numeric Object – Measurement-Status attribute is present and its set to “not-available” (0x2000). If PHG supports RACP, same criteria applies to 13.b.</p> <p>In Step 15, the Pulse Rate Numeric Object – Measurement-Status attribute is present and its set to “calibration-ongoing” (0x1000). If PHG supports RACP, same criteria applies to 16.b.</p> <p>In Step 18, the Pulse Rate Numeric Object – Measurement-Status attribute is present and its set to “test-data” (0x0800). If PHG supports RACP, same criteria applies to 19.b.</p> <p>In Step 21, the Pulse Rate Numeric Object – Measurement-Status attribute is present and its set to “demo-data” (0x0400). If PHG supports RACP, same criteria applies to 22.b.</p> <p>In Step 24, the Pulse Rate Numeric Object – Measurement-Status attribute is present and its set to “validated-data” (0x0080). If PHG supports RACP, same criteria applies to 25.b.</p> <p>In Step 27, the Pulse Rate Numeric Object – Measurement-Status attribute is present and its</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                                    | <p>set to “early-indication” (0x0040). If PHG supports RACP, same criteria applies to 28.b.</p> <p>In Step 30, the Pulse Rate Numeric Object – Measurement-Status attribute is present and its set to “msmt-ongoing” (0x0020). If PHG supports RACP, same criteria applies to 31.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <p><b>Notes<br/>(To assist manual testing)</b></p> | <p>In step 6 (and step 7.b if applicable), possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present:</p> <ul style="list-style-type: none"> <li>❑ Object: Pulse Rate Numeric Object</li> <li>❑ Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> <li>❑ Attribute-type: BITS16</li> <li>❑ Attribute-value: <b>80 00</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x [value]  264864^MDC_DIM_BEAT_PER_MIN^MDC  INV  X  [current_date_time]</pre> <p>In step 9 (and step 10.b if applicable), possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present:</p> <ul style="list-style-type: none"> <li>❑ Object: Pulse Rate Numeric Object</li> <li>❑ Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> <li>❑ Attribute-type: BITS16</li> <li>❑ Attribute-value: <b>40 00</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x [value]  264864^MDC_DIM_BEAT_PER_MIN^MDC  QUES  R  [current_date_time]</pre> <p>In step 12 (and step 13.b if applicable), possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present:</p> <ul style="list-style-type: none"> <li>❑ Object: Pulse Rate Numeric Object</li> <li>❑ Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> <li>❑ Attribute-type: BITS16</li> <li>❑ Attribute-value: <b>20 00</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x [value]  264864^MDC_DIM_BEAT_PER_MIN^MDC  NAV  X  [current_date_time]</pre> <p>In step 15 (and step 16.b if applicable), possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present:</p> <ul style="list-style-type: none"> <li>❑ Object: Pulse Rate Numeric Object</li> <li>❑ Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> </ul> |
+
+- Attribute-type: BITS16
+- Attribute-value: **10 00** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):
+
+OBX|n|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|m.0.0.x|[value]|  
+264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC||**CAL**||R||[current\_date\_time]
+
+In step 18 (and step 19.b if applicable), 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 Numeric Object
+- Attribute-id: MDC\_ATTR\_MSMT\_STAT (2375)
+- Attribute-type: BITS16
+- Attribute-value: **08 00** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):
+
+OBX|n|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|m.0.0.x|[value]|  
+264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC||**TEST**||R||[current\_date\_time]
+
+In step 21 (and step 22.b if applicable), 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 Numeric Object
+- Attribute-id: MDC\_ATTR\_MSMT\_STAT (2375)
+- Attribute-type: BITS16
+- Attribute-value: **04 00** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):
+
+OBX|n|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|m.0.0.x|[value]|  
+264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC||**DEMO**||R||[current\_date\_time]
+
+In step 24 (and step 25.b if applicable), 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 Numeric Object
+- Attribute-id: MDC\_ATTR\_MSMT\_STAT (2375)
+- Attribute-type: BITS16
+- Attribute-value: **00 80** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):
+
+OBX|n|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|m.0.0.x|[value]|  
+264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC||||**F**||[current\_date\_time]
+
+In step 27 (and step 28.b if applicable), possible values in typical points of observation after transcoder output are:
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>00 40</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX[n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x [value]<br/>264864^MDC_DIM_BEAT_PER_MIN^MDC  <b>EARLY</b>  <b>R</b>  [current_date_time]</pre> <p>In step 30 (and step 31.b if applicable), possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>00 20</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX[n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x [value]<br/>264864^MDC_DIM_BEAT_PER_MIN^MDC  <b>BUSY</b>  <b>X</b>  [current_date_time]</pre> |
+|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-033                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |  |
+| <b>TP label</b>          | Whitepaper. Pulse Rate Numeric Object (Continuous Measurements) – Measurement-Status Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | PR Numeric 17; M      |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Pulse Rate Numeric Object – Measurement-Status attribute in transcoder output when using continuous measurements.</p> <p>[AND]</p> <p>PHG transcodes the Bluetooth Measurement Status field of the PLX Continuous Measurement characteristic to 11073 Measurement-Status attribute properly</p>                                                                                                                                                                                                                                                                                                                     |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Continuous Measurement (0x2A5F)</li> <li>b. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features</li> </ol> </li> </ol> </li> </ol> |                       |  |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0011 0001 (MSB → LSB). Measurement Status support is present (bit 0). Fast and slow response modes are supported (bits 4 and 5).</li> </ul> <ul style="list-style-type: none"> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: <b>1111 1111 1110 0000</b> (MSB → LSB). All Measurement Status bits are supported</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Feature characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test with the following value:</p> <ul style="list-style-type: none"> <li>a. PLX Continuous Measurement (0x2A5F) <ul style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0111 (MSB → LSB). Measurement Status, SpO2PR-Fast and SpO2PR-Slow fields are present. Device and Sensor Status and Pulse Amplitude Index fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Normal - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: SpO2PR-Fast - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: SpO2PR-Fast - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vi. Field: SpO2PR-Slow - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vii. Field: SpO2PR-Slow - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>viii. Field: Measurement Status <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: <b>1000 0000 0000 0000</b> (MSB → LSB). Invalid measurement detected (bit 15).</li> </ul> </li> <li>ix. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> </li> </ul> |
+|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>x. Field: Pulse Amplitude Index (%)             <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> <ol style="list-style-type: none"> <li>6. Check in the PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute in all three Pulse Rate objects.</li> <li>7. The simulated PHD sends a Measurement to the PHG under test with the Measurement Status field set to 0100 0000 0000 0000 (MSB → LSB), questionable measurement detected (bit 14). All remaining fields remain equal to those in step 5.</li> <li>8. Check in the PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute in all three Pulse Rate objects.</li> <li>9. The simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0010 0000 0000 0000 (MSB → LSB), measurement not available (bit 13). All remaining fields remain equal to those in step 5.</li> <li>10. Check in the PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute in all three Pulse Rate objects.</li> <li>11. The simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0001 0000 0000 0000 (MSB → LSB), calibration ongoing (bit 12). All remaining fields remain equal to those in step 5.</li> <li>12. Check in the PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute in all three Pulse Rate objects.</li> <li>13. The simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0000 1000 0000 0000 (MSB → LSB), data for testing (bit 11). All remaining fields remain equal to those in step 5.</li> <li>14. Check in the PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute in all three Pulse Rate objects.</li> <li>15. The simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0000 0100 0000 0000 (MSB → LSB), data for demonstration (bit 10). All remaining fields remain equal to those in step 5.</li> <li>16. Check in the PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute in all three Pulse Rate objects.</li> <li>17. The simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0000 0000 1000 0000 (MSB → LSB), fully qualified data (bit 7). All remaining fields remain equal to those in step 5.</li> <li>18. Check in the PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute in all three Pulse Rate objects.</li> <li>19. The simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0000 0000 0100 0000 (MSB → LSB), early estimated data (bit 6). All remaining fields remain equal to those in step 5.</li> <li>20. Check in the PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute in all three Pulse Rate objects.</li> <li>21. The simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0000 0000 0010 0000 (MSB → LSB), measurement ongoing (bit 5). All remaining fields remain equal to those in step 5.</li> <li>22. Check in the PHG transcoder output the Pulse Rate Numeric Object – Measurement-Status attribute in all three Pulse Rate objects.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <p>In Step 6, the Pulse Rate Numeric Object – Measurement-Status attribute is present in all three Pulse Rate objects and its set to “invalid” (0x8000)</p> <p>In Step 8, the Pulse Rate Numeric Object – Measurement-Status attribute is present in all three Pulse Rate objects and its set to “questionable” (0x4000)</p> <p>In Step 10, the Pulse Rate Numeric Object – Measurement-Status attribute is present in all three Pulse Rate objects and its set to “not-available” (0x2000)</p> <p>In Step 12, the Pulse Rate Numeric Object – Measurement-Status attribute is present in all three Pulse Rate objects and its set to “calibration-ongoing” (0x1000)</p> <p>In Step 14, the Pulse Rate Numeric Object – Measurement-Status attribute is present in all three Pulse Rate objects and its set to “test-data” (0x0800)</p> <p>In Step 16, the Pulse Rate Numeric Object – Measurement-Status attribute is present in all</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+**Rec. ITU-T H.850.6 (08/2020)**      81
+
+|                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                                    | <p>three Pulse Rate objects and its set to “demo-data” (0x0400)</p> <p>In Step 18, the Pulse Rate Numeric Object – Measurement-Status attribute is present in all three Pulse Rate objects and its set to “validated-data” (0x0080)</p> <p>In Step 20, the Pulse Rate Numeric Object – Measurement-Status attribute is present in all three Pulse Rate objects and its set to “early-indication” (0x0040)</p> <p>In Step 22, the Pulse Rate Numeric Object – Measurement-Status attribute is present in all three Pulse Rate objects and its set to “msmt-ongoing” (0x0020)</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <p><b>Notes<br/>(To assist manual testing)</b></p> | <p>In step 6, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present in all three Pulse Rate objects:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>80 00</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like for each SpO2 object this with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x [value]  264864^MDC_DIM_BEAT_PER_MIN^MDC  INV  X  [current_date_time]</pre> <p>In step 8, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present in all three Pulse Rate objects:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>40 00</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this for each SpO2 object with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x [value]  264864^MDC_DIM_BEAT_PER_MIN^MDC  QUES  R  [current_date_time]</pre> <p>In step 10, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present in all three Pulse Rate objects:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>20 00</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this for each SpO2 object with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x [value]  264864^MDC_DIM_BEAT_PER_MIN^MDC  NAV  X  [current_date_time]</pre> <p>In step 12, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present in all three Pulse Rate objects:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> </ul> |
+
+- Attribute-type: BITS16
+- Attribute-value: **10 00** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this for each SpO2 object with Measurement-Status attribute value (check OBX-8 and OBX-11):
+
+OBX|n|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|m.0.0.x[[value]]  
+264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC||**CAL**||**R**||[current\_date\_time]
+
+In step 14, possible values in typical points of observation after transcoder output are:
+
+#### a) IEEE 11073 Objects and Attributes
+
+Measurement-Status attribute is present in all three Pulse Rate objects:
+
+- Object: Pulse Rate Numeric Object
+- Attribute-id: MDC\_ATTR\_MSMT\_STAT (2375)
+- Attribute-type: BITS16
+- Attribute-value: **08 00** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this for each SpO2 object with Measurement-Status attribute value (check OBX-8 and OBX-11):
+
+OBX|n|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|m.0.0.x[[value]]  
+264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC||**TEST**||**R**||[current\_date\_time]
+
+In step 16, possible values in typical points of observation after transcoder output are:
+
+#### a) IEEE 11073 Objects and Attributes
+
+Measurement-Status attribute is present in all three Pulse Rate objects:
+
+- Object: Pulse Rate Numeric Object
+- Attribute-id: MDC\_ATTR\_MSMT\_STAT (2375)
+- Attribute-type: BITS16
+- Attribute-value: **04 00** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this for each SpO2 object with Measurement-Status attribute value (check OBX-8 and OBX-11):
+
+OBX|n|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|m.0.0.x[[value]]  
+264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC||**DEMO**||**R**||[current\_date\_time]
+
+In step 18, possible values in typical points of observation after transcoder output are:
+
+#### a) IEEE 11073 Objects and Attributes
+
+Measurement-Status attribute is present in all three Pulse Rate objects:
+
+- Object: Pulse Rate Numeric Object
+- Attribute-id: MDC\_ATTR\_MSMT\_STAT (2375)
+- Attribute-type: BITS16
+- Attribute-value: **00 80** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this for each SpO2 object with Measurement-Status attribute value (check OBX-8 and OBX-11):
+
+OBX|n|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|m.0.0.x[[value]]  
+264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC||||**F**||[current\_date\_time]
+
+In step 20, possible values in typical points of observation after transcoder output are:
+
+#### a) IEEE 11073 Objects and Attributes
+
+Measurement-Status attribute is present in all three Pulse Rate objects:
+
+- Object: Pulse Rate Numeric Object
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <ul style="list-style-type: none"> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>00 40</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this for each SpO2 object with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x[[value]] 264864^MDC_DIM_BEAT_PER_MIN^MDC  <b>EARLY</b>  <b>R</b>  [current_date_time]</pre> <p>In step 22, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Measurement-Status attribute is present in all three Pulse Rate objects:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_MSMT_STAT (2375)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>00 20</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this for each SpO2 object with Measurement-Status attribute value (check OBX-8 and OBX-11):</p> <pre>OBX n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x[[value]] 264864^MDC_DIM_BEAT_PER_MIN^MDC  <b>BUSY</b>  <b>X</b>  [current_date_time]</pre> |
+|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-034                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                       |  |
+| <b>TP label</b>          | Whitepaper. Pulse Rate Numeric Object (Spot-Check Measurement) – Unit-Code Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | PR Numeric 8; M       |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Pulse Rate Numeric Object –Unit-Code attribute in transcoder output when using spot-check measurement mode.</p> <p>[AND]</p> <p>Unit-Code is set to MDC_DIM_BEAT_PER_MIN</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |  |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 <b>1100</b> (MSB → LSB). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                       |  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>iii. Field: Device and Sensor Status Support</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>b. PLX Spot-Check Measurement (0x2A5E)</p> <p>i. Field: Flags</p> <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0001 (MSB → LSB). Timestamp field is present. Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> <p>ii. Field: SpO2PR-Spot-Check - SpO2 (%)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>iii. Field: SpO2PR-Spot-Check – PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>iv. Field: Time Stamp</p> <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> <p>v. Field: Measurement Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>vi. Field: Device and Sensor Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>vii. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the Pulse Rate Numeric Object – Unit-Code attribute</p> <p>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <p>a) 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 spot-check measurement to PHG under test</p> <p>b) Check in PHG transcoder output the Pulse Rate Numeric Object – Unit-Code attribute</p> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the Pulse Rate Numeric Object – Unit-Code attribute is present and its set to MDC_DIM_BEAT_PER_MIN.</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Unit-Code attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_UNIT_CODE (2454)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: MDC_DIM_BEAT_PER_MIN or 2720 (dec) or 0A A0 (hex)</li> </ul> <p>b) WAN PCD-01 message</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|  |                                                                                                                                                                                                                             |
+|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):<br>OBX[n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x[value]<br><b>264864^MDC_DIM_BEAT_PER_MIN^MDC</b>    R  [current_date_time] |
+|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-035                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |
+| <b>TP label</b>          | Whitepaper. Pulse Rate Numeric Object (Continuous Measurements) – Unit-Code Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [Bluetooth PHDT v1.6] |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | PR Numeric 18; M      |
+| <b>Test purpose</b>      | Check that:<br><br>PHG includes Pulse Rate Numeric Object – Unit-Code attribute in transcoder output when using continuous measurements.<br>[AND]<br>Unit-Code is set to MDC_DIM_BEAT_PER_MIN                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                       |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:           <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60)               <ol style="list-style-type: none"> <li>i. Field: Supported Features                   <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0011 0000 (MSB → LSB). Fast and slow response modes are supported (bits 4 and 5).</li> </ul> </li> <li>ii. Field: Measurement Status Support                   <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support                   <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Continuous Measurement (0x2A5F)               <ol style="list-style-type: none"> <li>i. Field: Flags                   <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0011(MSB → LSB). SpO2PR-Fast, SpO2PR-Slow fields are present. Measurement Status, Device and Sensor Status and Pulse Amplitude Index fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%)                   <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Normal – PR (bpm)                   <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: SpO2PR-Fast - SpO2 (%)                   <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                       |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>v. Field: SpO2PR-Fast - PR (bpm)</p> <ul style="list-style-type: none"> <li>Format: SFLOAT</li> <li>Value: Not Relevant</li> </ul> <p>vi. Field: SpO2PR-Slow - SpO2 (%)</p> <ul style="list-style-type: none"> <li>Format: SFLOAT</li> <li>Value: Not Relevant</li> </ul> <p>vii. Field: SpO2PR-Slow - PR (bpm)</p> <ul style="list-style-type: none"> <li>Format: SFLOAT</li> <li>Value: Not Relevant</li> </ul> <p>viii. Field: Measurement Status</p> <ul style="list-style-type: none"> <li>This field is not included</li> </ul> <p>ix. Field: Device and Sensor Status</p> <ul style="list-style-type: none"> <li>This field is not included</li> </ul> <p>x. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>This field is not included</li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the Pulse Rate Numeric Object – Unit-Code attribute in all three Pulse Rate objects (continuous normal, fast and slow).</p> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6,</p> <ul style="list-style-type: none"> <li>There are three Pulse Rate objects (for normal, fast and slow measurement modes).</li> <li>In all three objects, the Pulse Rate Numeric Object – Unit-Code attribute is present and its set to MDC_DIM_BEAT_PER_MIN.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Unit-Code attribute is present in all three Pulse Rate objects:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_UNIT_CODE (2454)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: MDC_DIM_BEAT_PER_MIN or 2720 (dec) or 0A A0 (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this for each Pulse Rate object with Unit-Code attribute value (check OBX-6):</p> <p>OBX n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x[[value]]<br/>264864^MDC_DIM_BEAT_PER_MIN^MDC   R   [current_date_time]</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                     |                                                                                                |                       |                     |
+|---------------------|------------------------------------------------------------------------------------------------|-----------------------|---------------------|
+| <b>TP Id</b>        | TP/LP-PAN/PHG/PHDTW/PLX/BV-036                                                                 |                       |                     |
+| <b>TP label</b>     | Whitepaper. Pulse Rate Numeric Object (Spot-Check Measurement) – Absolute-Time-Stamp Attribute |                       |                     |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                    | [Bluetooth PHDT v1.6] |                     |
+|                     | <b>Testable items</b>                                                                          | PR Numeric 9; M       | Date-Time Conv 2; M |
+|                     |                                                                                                | Date-Time Conv 4; M   | Date-Time Conv 5; M |
+| <b>Test purpose</b> | Check that:                                                                                    |                       |                     |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | <p>PHG transcodes Time Stamp field of Spot-Check Measurement characteristic into Pulse Rate Numeric Object - Absolute-Time-Stamp attribute</p> <p>[AND]</p> <p>PHG transcodes the Bluetooth Time Stamp field format to Absolute Time format</p> <p>[AND]</p> <p>The fraction of seconds in Absolute Time at transcoder output is 0</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a Spot-Check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 <b>1100</b> (MSB → LSB). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0001 (MSB → LSB). Timestamp field is present. Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: October 12nd, 2015, 10:39:27</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> <li>3. The PHG under test initiates a discovery process (Scanning state), it discovers the</li> </ol> |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).</p> <ol style="list-style-type: none"> <li>4. When the pairing has been completed (Connection state), force the PHG to read the PLX Features characteristic.</li> <li>5. The simulated PHD sends the Measurement to the PHG under test.</li> <li>6. Check in PHG transcoder output the Pulse Rate Numeric Object – Absolute-Time-Stamp attribute</li> <li>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN <ol style="list-style-type: none"> <li>a) 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 spot-check measurement to PHG under test</li> <li>b) Check in PHG transcoder output the Pulse Rate Numeric Object – Absolute-Time-Stamp attribute</li> </ol> </li> </ol>                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the Pulse Rate Numeric Object – Absolute-Time-Stamp attribute is present, its value matches with Time Stamp field of Spot-Check Measurement characteristic and fraction of seconds is set to 0.</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Absolute-Time-Stamp attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)</li> <li><input type="checkbox"/> 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)</li> <li><input type="checkbox"/> Attribute-value: <ul style="list-style-type: none"> <li>• century: 20 (hex) or 32 (dec)</li> <li>• year: 15 (hex) or 21 (dec)</li> <li>• month: 10 (hex) or 16 (dec)</li> <li>• day: 12 (hex) or 18 (dec)</li> <li>• hour: 10 (hex) or 16 (dec)</li> <li>• minute: 39 (hex) or 57 (dec)</li> <li>• second: 27 (hex) or 39 (dec)</li> <li>• sec-fractions: 00 (hex) or 0 (dec)</li> </ul> </li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value (check OBX-14):</p> <pre>OBX n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x [value]  264864^MDC_DIM_BEAT_PER_MIN^MDC   R  20151012103927+0000</pre> |
+
+|                     |                                                                                                                                                                                        |                       |                       |
+|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|
+| <b>TP Id</b>        | TP/LP-PAN/PHG/PHDTW/PLX/BV-037                                                                                                                                                         |                       |                       |
+| <b>TP label</b>     | Whitepaper. Pulse Rate Numeric Object (Spot-Check Measurement) – Basic-Nu-Observed-Value Attribute 1                                                                                   |                       |                       |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                            | [Bluetooth PHDT v1.6] |                       |
+|                     | <b>Testable items</b>                                                                                                                                                                  | PR Numeric 10; M      | Short Float Type 1; C |
+| <b>Test purpose</b> | <p>Check that:</p> <p>PHG transcodes PR value of the SpO2PR-Spot-Check field in PLX Spot-Check Measurement characteristic into Pulse Rate Numeric Object - Basic-Nu-Observed-Value</p> |                       |                       |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a Spot-Check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 1100 (MSB → LSB). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0001 (MSB → LSB). Timestamp field is present. Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 90.0 (bpm)</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not relevant</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</li> <li>5. The simulated PHD sends the Measurement to PHG under test.</li> <li>6. Check in PHG transcoder output the Pulse Rate Numeric Object – Basic-Nu-Observed-Value attribute</li> </ol> |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <p>a) 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 spot-check measurement to PHG under test</p> <p>b) Check in PHG transcoder output the Pulse Rate Numeric Object – Basic-Nu-Observed-Value attribute</p>                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the Pulse Rate Numeric Object – Basic-Nu-Observed-Value attribute is present and its value matches with the value of the PR subfield of the SpO2PR-Spot-Check field in the PLX Spot-Check Measurement characteristic (90.0 bpm).</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Basic-Nu-Observed-Value attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)</li> <li><input type="checkbox"/> Attribute-type: SFLOAT</li> <li><input type="checkbox"/> Attribute-value: F3 84 (hex) or 10 09 (hex) or 00 5A (hex) or 90.0 (dec)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Basic-Nu-Observed-Value attribute value (check OBX-5):</p> <pre>OBX[n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x 90.0  264864^MDC_DIM_BEAT_PER_MIN^MDC   R  [current_date_time]</pre> |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |                  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-038                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |                  |
+| <b>TP label</b>          | Whitepaper. Pulse Rate Numeric Object (Spot-Check Measurement) – Basic-Nu-Observed-Value Attribute 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [Bluetooth PHDT v1.6] |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | PR Numeric 10; M      | PR Numeric 20; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG transcodes Pulse Rate value of the PR subfield of the SpO2PR-Spot-Check field in PLX Spot-Check Measurement characteristic into Pulse Rate Numeric Object - Basic-Nu-Observed-Value attribute</p> <p>[AND]</p> <p>PHG assigns special value NaN (0x07FF) when Pulse Rate value is unavailable.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                       |                  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |                  |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |                  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a Spot-Check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 1100 (MSB → LSB). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                       |                  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>measurements is supported (bit 3).</p> <ul style="list-style-type: none"> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> <p>b. PLX Spot-Check Measurement (0x2A5E)</p> <ul style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0001 (MSB → LSB). Timestamp field is present. Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 07 FF (hex). Special value: NaN</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> <ol style="list-style-type: none"> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</li> <li>5. The simulated PHD sends the Measurement to the PHG under test.</li> <li>6. Check in PHG transcoder output the Pulse Rate Numeric Object – Basic-Nu-Observed-Value attribute</li> <li>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN <ol style="list-style-type: none"> <li>a) 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 spot-check measurement to PHG under test</li> <li>b) Check in PHG transcoder output the Pulse Rate Numeric Object – Basic-Nu-Observed-Value attribute</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the Pulse Rate Numeric Object – Basic-Nu-Observed-Value attribute is present and its value is 0x07FF (NaN).</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Basic-Nu-Observed-Value attribute is present:</p> <p><input type="checkbox"/> Object: Pulse Rate Numeric Object</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <ul style="list-style-type: none"> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)</li> <li><input type="checkbox"/> Attribute-type: SFLOAT</li> <li><input type="checkbox"/> Attribute-value: 07 FF (hex) or NaN (note that a decimal value is not allowed)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Basic-Nu-Observed-Value attribute value (check OBX-5):</p> <p>OBX[n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x <br/>264864^MDC_DIM_BEAT_PER_MIN^MDC  <b>NAN</b>  X  [current_date_time]</p> |
+|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |                       |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-039                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                       |                       |
+| <b>TP label</b>          | Pulse Rate Numeric Object (Continuous Measurements) – Basic-Nu-Observed-Value Attribute 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |                       |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [Bluetooth PHDT v1.6] |                       |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | PR Numeric 19; M      | Short Float Type 1; C |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG transcodes Pulse Rate value of the PR subfield of the SpO2PR-Normal field in PLX Continuous Measurement characteristic into Pulse Rate Numeric Object (Continuous normal response) - Basic-Nu-Observed-Value attribute</p> <p>[AND]</p> <p>PHG transcodes Pulse Rate value of the PR subfield of the SpO2PR-Fast field in PLX Continuous Measurement characteristic into Pulse Rate Numeric Object (Continuous fast response) - Basic-Nu-Observed-Value attribute</p> <p>[AND]</p> <p>PHG transcodes Pulse Rate value of the PR subfield of the SpO2PR-Slow field in PLX Continuous Measurement characteristic into Pulse Rate Numeric Object (Continuous slow response) - Basic-Nu-Observed-Value attribute</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |                       |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |                       |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |                       |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                       |                       |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ul style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ul style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0011 0000 (MSB → LSB). Fast and slow response modes are supported (bits 4 and 5).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> </li> <li>b. PLX Continuous Measurement (0x2A5F) <ul style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0011 (MSB → LSB). SpO2PR-Fast, SpO2PR-Slow fields are present. Measurement Status, Device and Sensor Status and Pulse</li> </ul> </li> </ul> </li> </ul> </li> </ol> |                       |                       |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>Amplitude Index fields are not present.</p> <ul style="list-style-type: none"> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Normal - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 90.0 (bpm)</li> </ul> </li> <li>iv. Field: SpO2PR-Fast - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: SpO2PR-Fast - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 91.0 (bpm)</li> </ul> </li> <li>vi. Field: SpO2PR-Slow - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vii. Field: SpO2PR-Slow - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 92.0 (bpm)</li> </ul> </li> <li>viii. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>ix. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>x. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> <ol style="list-style-type: none"> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</li> <li>5. The simulated PHD sends the Measurement to PHG under test.</li> <li>6. Check in PHG transcoder output the Pulse Rate Numeric Object – Basic-Nu-Observed-Value attribute in all three Pulse Rate objects.</li> </ol> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6,</p> <ul style="list-style-type: none"> <li>• The Pulse Rate Numeric Object (Continuous measurement normal) – Basic-Nu-Observed-Value attribute is present and its value matches with the value of the PR field of the SpO2PR-Normal field in the PLX Continuous Measurement characteristic (90.0 bpm).</li> <li>• The Pulse Rate Numeric Object (Continuous measurement fast) – Basic-Nu-Observed-Value attribute is present and its value matches with the value of the PR subfield of the SpO2PR-Fast field in the PLX Continuous Measurement characteristic (91.0 bpm).</li> <li>• The Pulse Rate Numeric Object (Continuous measurement slow) – Basic-Nu-Observed-Value attribute is present and its value matches with the value of the PR subfield of the SpO2PR-Slow field in the PLX Continuous Measurement characteristic (92.0 bpm).</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Pulse Rate Numeric object (Continuous measurement normal):</p> <p>Supplemental-types attribute is not present.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+- Basic-Nu-Observed-Value attribute is present:
+  - Object: Pulse Rate Numeric Object
+  - Attribute-id: MDC\_ATTR\_NU\_VAL\_OBS\_BASIC (2636)
+  - Attribute-type: SFLOAT
+  - Attribute-value: F3 84 (hex) or 10 09 (hex) or 00 5A (hex) or 90.0 (dec)
+
+Pulse Rate Numeric object (Continuous measurement fast):
+
+- Supplemental-types attribute is present:
+  - Object: Pulse Rate Numeric Object (fast response)
+  - Attribute-id: MDC\_ATTR\_SUPPLEMENTAL\_TYPES (2657)
+  - Attribute-type: SEQUENCE of SEQUENCE {partition (INT-U16), code (INT-U16)}
+  - Attribute-value: {MDC\_PART\_SCADA, MDC\_MODALITY\_FAST}.
+- Basic-Nu-Observed-Value attribute is present:
+  - Object: Pulse Rate Numeric Object
+  - Attribute-id: MDC\_ATTR\_NU\_VAL\_OBS\_BASIC (2636)
+  - Attribute-type: SFLOAT
+  - Attribute-value: F3 8E (hex) or 00 5B (hex) or 91.0 (dec)
+
+Pulse Rate Numeric object (Continuous measurement slow):
+
+- Supplemental-types attribute is present:
+  - Object: Pulse Rate Numeric Object (slow response)
+  - Attribute-id: MDC\_ATTR\_SUPPLEMENTAL\_TYPES (2657)
+  - Attribute-type: SEQUENCE of SEQUENCE {partition (INT-U16), code (INT-U16)}
+  - Attribute-value: {MDC\_PART\_SCADA, MDC\_MODALITY\_SLOW}.
+- Basic-Nu-Observed-Value attribute is present:
+  - Object: Pulse Rate Numeric Object
+  - Attribute-id: MDC\_ATTR\_NU\_VAL\_OBS\_BASIC (2636)
+  - Attribute-type: SFLOAT
+  - Attribute-value: F3 98 (hex) or 00 5C (hex) or 92.0(dec)
+
+#### b) WAN PCD-01 message
+
+Pulse Rate Numeric object (Continuous measurement normal):
+
+- PCD-01 message includes a segment like this with Basic-Nu-Observed-Value attribute value (check OBX-5):
+
+OBX|n|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|m.0.0.x|**90.0**|  
+264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC|||R||[current\_date\_time]
+
+Pulse Rate Numeric object (Continuous measurement fast):
+
+- PCD-01 message includes two segments like these for Pulse Rate Numeric object (Fast response), with Basic-Nu-Observed-Value attribute and Supplemental-Types attribute values (check OBX-5 in both segments):
+
+OBX|n|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|m.0.0.x|**91.0**|  
+264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC|||R||[current\_date\_time]
+
+OBX|n|CWE|68193^MDC\_ATTR\_SUPPLEMENTAL\_TYPES^MDC|m.0.0.x.y|  
+**150580^MDC\_MODALITY\_FAST^MDC**|||||[obx-11 of the parent]
+
+Pulse Rate Numeric object (Continuous measurement slow):
+
+- PCD-01 message includes two segments like these for Pulse Rate Numeric object (Slow response), with Basic-Nu-Observed-Value attribute and Supplemental-Types attribute values (check OBX-5 in both segments):
+
+|  |                                                                                                                                                                                                                                                 |
+|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | OBX n NM 149530^MDC_PULS_OXIM_PULS_RATE^MDC m.0.0.x 92.0 <br>264864^MDC_DIM_BEAT_PER_MIN^MDC   R   [current_date_time]<br>OBX n CWE 68193^MDC_ATTR_SUPPLEMENTAL_TYPES^MDC m.0.0.x.y <br>150580^MDC_MODALITY_SLOW^MDC     [obx-11 of the parent] |
+|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |                  |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |                  |
+| <b>TP label</b>          | Whitepaper. Pulse Rate Numeric Object (Continuous Measurements) – Basic-Nu-Observed-Value Attribute 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [Bluetooth PHDT v1.6] |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | PR Numeric 19; M      | PR Numeric 20; M |
+| <b>Test purpose</b>      | Check that:<br><br>PHG transcodes Pulse Rate value of the PR subfield of the SpO2PR-Normal field in PLX Continuous Measurement characteristic into Pulse Rate Numeric Object (Continuous normal response) - Basic-Nu-Observed-Value attribute<br>[AND]<br>PHG transcodes Pulse Rate value of the PR subfield of the SpO2PR-Fast field in PLX Continuous Measurement characteristic into Pulse Rate Numeric Object (Continuous fast response) - Basic-Nu-Observed-Value attribute<br>[AND]<br>PHG transcodes Pulse Rate value of the PR subfield of the SpO2PR-Slow field in PLX Continuous Measurement characteristic into Pulse Rate Numeric Object (Continuous slow response) - Basic-Nu-Observed-Value attribute<br>[AND]<br>PHG assigns special value NaN (0x07FF) when Pulse Rate value is unavailable.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                       |                  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |                  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |                  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0011 0000 (MSB → LSB). Fast and slow response modes are supported (bits 4 and 5).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Continuous Measurement (0x2A5F) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0011 (MSB → LSB). SpO2PR-Fast, SpO2PR-Slow fields are present. Measurement Status, Device and Sensor Status and Pulse Amplitude Index fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%)</li> </ol> </li> </ol> </li> </ol> |                       |                  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>iii. Field: SpO2PR-Normal - PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 07 FF (hex). Special value: NaN</li> </ul> <p>iv. Field: SpO2PR-Fast - SpO2 (%)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>v. Field: SpO2PR-Fast - PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 07 FF (hex). Special value: NaN</li> </ul> <p>vi. Field: SpO2PR-Slow - SpO2 (%)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>vii. Field: SpO2PR-Slow - PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 07 FF (hex). Special value: NaN</li> </ul> <p>viii. Field: Measurement Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>ix. Field: Device and Sensor Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>x. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <ol style="list-style-type: none"> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</li> <li>5. The simulated PHD sends the Measurement to PHG under test.</li> <li>6. Check in PHG transcoder output the Pulse Rate Numeric Object – Basic-Nu-Observed-Value attribute for all Pulse Rate objects.</li> </ol> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6,</p> <ul style="list-style-type: none"> <li>• The Pulse Rate Numeric Object (Continuous measurement normal) – Basic-Nu-Observed-Value attribute is present and its value is 0x07FF (NaN).</li> <li>• The Pulse Rate Numeric Object (Continuous measurement fast) – Basic-Nu-Observed-Value attribute is present and its value is 0x07FF (NaN).</li> <li>• The Pulse Rate Numeric Object (Continuous measurement slow) – Basic-Nu-Observed-Value attribute is present and its value is 0x07FF (NaN).</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Pulse Rate Numeric object (Continuous measurement normal):</p> <ul style="list-style-type: none"> <li>• Supplemental-types attribute is not present.</li> </ul> <p>Basic-Nu-Observed-Value attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulse Rate Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)</li> <li><input type="checkbox"/> Attribute-type: SFLOAT</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+- Attribute-value: Attribute-value: 07 FF (hex) or NaN (note that a decimal value is not allowed)
+
+Pulse Rate Numeric object (Continuous measurement fast):
+
+- Supplemental-types attribute is present:
+  - Object: Pulse Rate Numeric Object (fast response)
+  - Attribute-id: MDC\_ATTR\_SUPPLEMENTAL\_TYPES (2657)
+  - Attribute-type: SEQUENCE of SEQUENCE {partition (INT-U16), code (INT-U16)}
+  - Attribute-value: {MDC\_PART\_SCADA, MDC\_MODALITY\_FAST}.
+- Basic-Nu-Observed-Value attribute is present:
+  - Object: Pulse Rate Numeric Object
+  - Attribute-id: MDC\_ATTR\_NU\_VAL\_OBS\_BASIC (2636)
+  - Attribute-type: SFLOAT
+  - Attribute-value: Attribute-value: 07 FF (hex) or NaN (note that a decimal value is not allowed)
+
+Pulse Rate Numeric object (Continuous measurement slow):
+
+- Supplemental-types attribute is present:
+  - Object: Pulse Rate Numeric Object (slow response)
+  - Attribute-id: MDC\_ATTR\_SUPPLEMENTAL\_TYPES (2657)
+  - Attribute-type: SEQUENCE of SEQUENCE {partition (INT-U16), code (INT-U16)}
+  - Attribute-value: {MDC\_PART\_SCADA, MDC\_MODALITY\_SLOW}.
+- Basic-Nu-Observed-Value attribute is present:
+  - Object: Pulse Rate Numeric Object
+  - Attribute-id: MDC\_ATTR\_NU\_VAL\_OBS\_BASIC (2636)
+  - Attribute-type: SFLOAT
+  - Attribute-value: Attribute-value: 07 FF (hex) or NaN (note that a decimal value is not allowed)
+
+#### b) WAN PCD-01 message
+
+Pulse Rate Numeric object (Continuous measurement normal):
+
+- PCD-01 message includes a segment like this with Basic-Nu-Observed-Value attribute value (check OBX-5):
+
+OBX|n|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|m.0.0.x|  
+264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC||NAN||X||[current\_date\_time]
+
+Pulse Rate Numeric object (Continuous measurement fast):
+
+- PCD-01 message includes two segments like these for Pulse Rate Numeric object (Fast response), with Basic-Nu-Observed-Value attribute and Supplemental-Types attribute values (check OBX-5 in both segments):
+
+OBX|n|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|m.0.0.x|  
+264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC||NAN||X||[current\_date\_time]
+
+OBX|n|CWE|68193^MDC\_ATTR\_SUPPLEMENTAL\_TYPES^MDC|m.0.0.x.y|  
+**150580^MDC\_MODALITY\_FAST^MDC**|||||[obx-11 of the parent]
+
+Pulse Rate Numeric object (Continuous measurement slow):
+
+- PCD-01 message includes two segments like these for Pulse Rate Numeric object (Slow response), with Basic-Nu-Observed-Value attribute and Supplemental-Types attribute values (check OBX-5 in both segments):
+
+OBX|n|NM|149530^MDC\_PULS\_OXIM\_PULS\_RATE^MDC|m.0.0.x|  
+264864^MDC\_DIM\_BEAT\_PER\_MIN^MDC||NAN||X||[current\_date\_time]
+
+OBX|n|CWE|68193^MDC\_ATTR\_SUPPLEMENTAL\_TYPES^MDC|m.0.0.x.y|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |                     |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-041                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                       |                     |
+| <b>TP label</b>          | Whitepaper. Pulse Rate measurement value (Spot-Check Measurement)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |                     |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [Bluetooth PHDT v1.6] |                     |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Short Float Type 1; C | Date-Time Conv 1; M |
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | PR Numeric 10; M      | PR Numeric 9; M     |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG processes correctly the Pulse Rate value (bpm) of the PR subfield of the SpO2PR-Spot-Check field and the value of the Time Stamp field of the PLX Spot-Check characteristic</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |                     |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |                     |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |                     |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                       |                     |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a Spot-Check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 <b>1100</b> (MSB → LSB). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0001 (MSB → LSB). Timestamp field is present. Measurement Status, Device and Sensor Status, and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 90.0 (bpm)</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: October 12nd, 2015, 10:39:27</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status</li> </ol> </li> </ol> </li> </ol> |                       |                     |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li><ul style="list-style-type: none"><li>This field is not included</li></ul></li> <li>vii. Field: Pulse Amplitude Index (%)</li> <li><ul style="list-style-type: none"><li>This field is not included</li></ul></li> </ul> 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).<br>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.<br>5. The simulated PHD sends the Measurement to the PHG under test.<br>6. Check that PHG accepts the measurement and decodes its value properly (Pulse Rate measurement value, units and time stamp).<br>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN <ol style="list-style-type: none"> <li>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 spot-check measurement to the PHG under test</li> <li>Check that the PHG accepts the measurement and decodes its value properly (Pulse Rate measurement value, units and time stamp)</li> </ol> |
+| <b>Pass/Fail criteria</b> | In Step 6, the PHG under test shows the following measurement Pulse Rate = 90.0 (bpm) with timestamp '2015-10-12 10:39:27'.<br>If the PHG supports RACP, the same criteria applies to Step 7.b.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |  |
+| <b>TP label</b>          | Whitepaper. Pulsatile Quality Numeric Object (Spot-Check Measurement) - Handle Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | PQ Numeric 1; O       |  |
+| <b>Test purpose</b>      | Check that:<br><br>PHG does not include Pulsatile Quality Numeric Object – Handle Attribute in transcoder output when using spot-check measurement mode.<br><br>[OR]<br><br>If PHG includes Pulsatile Quality Numeric Object – Handle attribute in transcoder output, then its value shall be different than 0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |  |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |  |
+| <b>Test procedure</b>    | 1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.<br><br>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:<br><ol style="list-style-type: none"> <li>PLX Features (0x2A60) <ol style="list-style-type: none"> <li>Field: Supported Features <ul style="list-style-type: none"> <li>Format: 16 bit</li> <li>Value: 0000 0000 0100 1100 (MSB → LSB). Pulse Amplitude Index field is supported (bit 6). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>Field: Measurement Status Support</li> </ol> </li> </ol> |                       |  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>iii. Field: Device and Sensor Status Support</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>b. PLX Spot-Check Measurement (0x2A5E)</p> <ul style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 1001 (MSB → LSB). Timestamp and Pulse Amplitude Index fields are present. Measurement Status and Device and Sensor Status fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the Pulsatile Quality Numeric Object – Handle attribute</p> <p>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <ul style="list-style-type: none"> <li>a) 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 spot-check measurement to PHG under test</li> <li>b) Check in PHG transcoder output the Pulsatile Quality Numeric Object – Handle attribute</li> </ul> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the Pulsatile Quality Numeric Object – Handle attribute is not present or, if it is present then its value is different than 0</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Handle attribute is not present, or if it is present then:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulsatile Quality Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_HANDLE (2337)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|  |                                                                                                                                                                       |
+|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <input type="checkbox"/> Attribute-value: Any value different than 0<br>b) WAN PCD-01 message<br>PCD-01 message does not include segments with Handle attribute value |
+|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-043                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |  |
+| <b>TP label</b>          | Whitepaper. Pulsatile Quality Numeric Object (Continuous Measurements) - Handle Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | PQ Numeric 9; O       |  |
+| <b>Test purpose</b>      | Check that:<br>PHG does not include Pulsatile Quality Numeric Object – Handle Attribute in transcoder output when using continuous measurements<br>[OR]<br>If PHG includes Pulsatile Quality Numeric Object – Handle attribute in transcoder output, then its value shall be different than 0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:           <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60)               <ol style="list-style-type: none"> <li>i. Field: Supported Features                   <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0111 0000 (MSB → LSB). Fast and slow response modes are supported (bits 4 and 5). Pulse Amplitude Index field is supported.</li> </ul> </li> <li>ii. Field: Measurement Status Support                   <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support                   <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Continuous Measurement (0x2A5F)               <ol style="list-style-type: none"> <li>i. Field: Flags                   <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0001 0011 (MSB → LSB). SpO2PR-Fast, SpO2PR-Slow and Pulse Amplitude Index fields are present. Measurement Status, and Device and Sensor Status and fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%)                   <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Normal – PR (bpm)                   <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: SpO2PR-Fast - SpO2 (%)                   <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                       |  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ul style="list-style-type: none"> <li>• Value: Not Relevant</li> </ul> <p>v. Field: SpO2PR-Fast - PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>vi. Field: SpO2PR-Slow - SpO2 (%)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>vii. Field: SpO2PR-Slow - PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>viii. Field: Measurement Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>ix. Field: Device and Sensor Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>x. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Feature characteristic</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the Pulsatile Quality Numeric Object – Handle attribute.</p> |
+| <b>Pass/Fail criteria</b>                   | In Step 6, the Pulsatile Quality Numeric Object – Handle attribute is not present or, if it is present then its value is different than 0.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Handle attribute is not present, or if it is present then:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulsatile Quality Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_HANDLE (2337)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: Any value different than 0</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message does not include segments with Handle attribute value</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+|                     |                                                                                                                                                                    |                       |
+|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| <b>TP Id</b>        | TP/LP-PAN/PHG/PHDTW/PLX/BV-044                                                                                                                                     |                       |
+| <b>TP label</b>     | Whitepaper. Pulsatile Quality Numeric Object (Spot-Check Measurement) - Type Attribute                                                                             |                       |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                        | [Bluetooth PHDT v1.6] |
+|                     | <b>Testable items</b>                                                                                                                                              | PQ Numeric 2; M       |
+| <b>Test purpose</b> | <p>Check that:</p> <p>PHG includes Pulsatile Quality Numeric Object – Type attribute in transcoder output when using spot-check measurement mode.</p> <p>[AND]</p> |                       |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | Type is set to {MDC_PART_SCADA, MDC_SAT_O2_QUAL}                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0100 1100 (MSB → LSB). Pulse Amplitude Index field is supported (bit 6). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 1001 (MSB → LSB). Timestamp and Pulse Amplitude Index fields are present. Measurement Status and Device and Sensor Status fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> </ol> </li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</li> </ol> |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the Pulsatile Quality Numeric Object – Type attribute</p> <p>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <p style="padding-left: 20px;">a) 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 spot-check measurement to PHG under test</p> <p style="padding-left: 20px;">b) Check in PHG transcoder output the Pulsatile Quality Numeric Object – Type attribute</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the Pulsatile Quality Numeric Object – Type attribute is present and its value is {MDC_PART_SCADA, MDC_SAT_O2_QUAL}</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p style="padding-left: 20px;">a) IEEE 11073 Objects and Attributes</p> <p style="padding-left: 40px;">Type attribute is present:</p> <p style="padding-left: 40px;"><input type="checkbox"/> Object: Pulsatile Quality Numeric Object</p> <p style="padding-left: 40px;"><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_TYPE (2351)</p> <p style="padding-left: 40px;"><input type="checkbox"/> Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}</p> <p style="padding-left: 40px;"><input type="checkbox"/> Attribute-value:</p> <p style="padding-left: 60px;">• partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)</p> <p style="padding-left: 60px;">• code: MDC_SAT_O2_QUAL or 19248(dec) or 4B 30 (hex)</p> <p style="padding-left: 20px;">b) WAN PCD-01 message</p> <p style="padding-left: 40px;">PCD-01 message includes a segment like this with Type attribute (check OBX-3):</p> <p style="padding-left: 60px;">OBX[n NM 150320^MDC_SAT_O2_QUAL^MDC m.0.0.x [value]]<br/>262688^MDC_DIM_PERCENT^MDC     R   current_date_time</p> |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                       |  |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-045                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |  |
+| <b>TP label</b>          | Whitepaper. Pulsatile Quality Numeric Object (Continuous Measurements) - Type Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | PQ Numeric 10; M      |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Pulsatile Quality Numeric Object – Type attribute in transcoder output when using continuous measurements.</p> <p>[AND]</p> <p>Type is set to {MDC_PART_SCADA, MDC_SAT_O2_QUAL}</p>                                                                                                                                                                                                                                                                                                                                                        |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |  |
+| <b>Test procedure</b>    | <p>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</p> <p>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:</p> <p style="padding-left: 20px;">a. PLX Features (0x2A60)</p> <p style="padding-left: 40px;">i. Field: Supported Features</p> <p style="padding-left: 60px;">• Format: 16 bit</p> |                       |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <ul style="list-style-type: none"> <li>• Value: 0000 0000 <b>0111</b> 0000 (MSB → LSB). Fast and slow response modes are supported (bits 4 and 5). Pulse Amplitude Index is supported (bit 6).</li> </ul> <ul style="list-style-type: none"> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> <p>b. PLX Continuous Measurement (0x2A5F)</p> <ul style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 000<b>1</b> 00<b>11</b> (MSB → LSB). SpO2PR–Fast, SpO2PR–Slow and Pulse Amplitude Index fields are present. Measurement Status, and Device and Sensor Status fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Normal – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: SpO2PR-Fast - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: SpO2PR-Fast - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vi. Field: SpO2PR-Slow - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vii. Field: SpO2PR-Slow - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>viii. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>ix. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>x. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Feature characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the Pulsatile Quality Numeric Object – Type attribute.</p> |
+| <b>Pass/Fail criteria</b> | In Step 6, the Pulsatile Quality Numeric Object – Type attribute is present and its value is {MDC_PART_SCADA, MDC_SAT_O2_QUAL}                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Type attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulsatile Quality Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_TYPE (2351)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}</li> <li><input type="checkbox"/> Attribute-value: <ul style="list-style-type: none"> <li>• partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)</li> <li>• code: MDC_SAT_O2_QUAL or 19248(dec) or 4B 30 (hex)</li> </ul> </li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes three segments like this with Type attribute (check OBX-3):</p> <p>OBX n NM 150320^MDC_SAT_O2_QUAL^MDC m.0.0.x[[value]]<br/>262688^MDC_DIM_PERCENT^MDC    R  [current_date_time]</p> |
+|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                       |                 |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-046                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |                 |
+| <b>TP label</b>          | Whitepaper. Pulsatile Quality Numeric Object (Spot-Check Measurement) - Metric-Spec-Small Attribute 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [Bluetooth PHDT v1.6] |                 |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PQ Numeric 3; M       | PQ Numeric 5; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Pulsatile Quality Numeric Object – Metric-Spec-Small attribute in transcoder output when using spot-check measurement mode.</p> <p>[AND]</p> <p>Metric-Spec-Small is set to {0x5040} when the sensor device supports measurement storage.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |                 |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |                 |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |                 |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Spot-Check Measurement (0x2A5E)</li> <li>b. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0100 1100 (MSB → LSB). Pulse Amplitude Index field is supported (bit 6). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> <li>3. The PHG under test initiates a discovery process (Scanning state), it discovers the</li> </ol> |                       |                 |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>simulated PHD and it starts a pairing process with the simulated PHD (Initiating state).</p> <ol style="list-style-type: none"> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</li> <li>5. The simulated PHD sends the Measurement to the PHG under test with the following value: <ol style="list-style-type: none"> <li>a. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 1001 (MSB → LSB). Timestamp and Pulse Amplitude Index fields are present. Measurement Status, and Device and Sensor Status are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> </ol> </li> </ol> </li> <li>6. Check in PHG transcoder output the Pulsatile Quality Numeric Object – Metric-Spec-Small attribute</li> <li>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN <ol style="list-style-type: none"> <li>a) 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 spot-check measurement to the PHG under test</li> <li>b) Check in PHG transcoder output the Pulsatile Quality Numeric Object – Metric-Spec-Small attribute</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the Pulsatile Quality Numeric Object – Metric-Spec-Small attribute is present and its value is {0x5040} (mss-avail-stored-data  mss-msmt-aperiodic  mss-acc-agent-initiated).<br/> If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <ol style="list-style-type: none"> <li>a) IEEE 11073 Objects and Attributes<br/> Metric-Spec-Small attribute is present: <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulsatile Quality Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)</li> <li><input type="checkbox"/> Attribute-type: BITS-16</li> <li><input type="checkbox"/> Attribute-value: 50 40 (hex) or BITS mss-avail-stored-data (1), mss- msmt - aperiodic(3), mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE</li> </ul> </li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+|  |                                                                                                          |
+|--|----------------------------------------------------------------------------------------------------------|
+|  | b) WAN PCD-01 message<br>PCD-01 message does not include segments with Metric-Spec-Small attribute value |
+|--|----------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |                 |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-047                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |                 |
+| <b>TP label</b>          | Whitepaper. Pulsatile Quality Numeric Object (Spot-Check Measurement) - Metric-Spec-Small Attribute 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |                 |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | [Bluetooth PHDT v1.6] |                 |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | PQ Numeric 3; M       | PQ Numeric 4; M |
+| <b>Test purpose</b>      | Check that:<br>PHG includes Pulsatile Quality Numeric Object – Metric-Spec-Small attribute in transcoder output when using spot-check measurement mode.<br>[AND]<br>Metric-Spec-Small is set to {0x1040} when the sensor device does not support measurement storage.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |                 |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |                 |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |                 |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                       |                 |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Spot-Check Measurement (0x2A5E)</li> <li>b. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0100 1100 (MSB → LSB). Pulse Amplitude Index field is supported (bit 6). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</li> <li>5. The simulated PHD sends the Measurement to the PHG under test with the following value: <ol style="list-style-type: none"> <li>a. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 1001 (MSB → LSB). Timestamp and Pulse Amplitude Index fields are present. Measurement Status and Device and Sensor Status fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                       |                 |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ul style="list-style-type: none"> <li>• Value: Not Relevant</li> </ul> <p>iii. Field: SpO2PR-Spot-Check – PR (bpm)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>iv. Field: Time Stamp</p> <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> <p>v. Field: Measurement Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>vi. Field: Device and Sensor Status</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>vii. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>6. Check in PHG transcoder output the Pulsatile Quality Numeric Object – Metric-Spec-Small attribute</p> |
+| <b>Pass/Fail criteria</b>                   | In Step 6, the SpO2 Numeric Object – Metric-Spec-Small attribute is present and its value is {0x1040} (mss-msmt-aperiodic   mss-acc-agent-initiated).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Metric-Spec-Small attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulsatile Quality Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)</li> <li><input type="checkbox"/> Attribute-type: BITS-16</li> <li><input type="checkbox"/> Attribute-value: 10 40 (hex) or BITS mss-msmt-aperiodic(3), mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message does not include segments with Metric-Spec-Small attribute value</p>                                                                                                                                |
+
+|                          |                                                                                                                                                                                                                                                                  |                       |  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-048                                                                                                                                                                                                                                   |                       |  |
+| <b>TP label</b>          | Whitepaper. Pulsatile Quality Numeric Object (Continuous Measurements) - Metric-Spec-Small Attribute                                                                                                                                                             |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                      | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                            | PQ Numeric 11; M      |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Pulsatile Quality Numeric Object – Metric-Spec-Small attribute in transcoder output when using continuous measurements.</p> <p>[AND]</p> <p>Metric-Spec-Small is set to {0x0040} (mss-acc-agent-initiated)</p>                |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                |                       |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                  |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                               |                       |  |
+| <b>Test procedure</b>    | <p>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</p> |                       |  |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <p>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are:</p> <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0111 0000 (MSB → LSB). Fast and slow response modes are supported (bits 4 and 5). Pulse Amplitude Index field is supported (bit 6)</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Continuous Measurement (0x2A5F) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0001 0011 (MSB → LSB). SpO2PR–Fast, SpO2PR–Slow and Pulse Amplitude Index fields are present. Measurement Status and Device and Sensor Status fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Normal – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: SpO2PR-Fast - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: SpO2PR-Fast - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vi. Field: SpO2PR-Slow - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vii. Field: SpO2PR-Slow - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>viii. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>ix. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>x. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> </ol> </li> </ol> <p>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).</p> |
+|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the Pulsatile Quality Numeric Object – Metric-Spec-Small attribute</p>                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Pass/Fail criteria</b>                   | In Step 6, the Pulsatile Quality Numeric Object – Metric-Spec-Small attribute is present and its value is {0x0040} (mss-acc-agent-initiated).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Metric-Spec-Small attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulsatile Quality Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)</li> <li><input type="checkbox"/> Attribute-type: BITS-16</li> <li><input type="checkbox"/> Attribute-value: 00 40 (hex) or BITS mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message does not include segments with Metric-Spec-Small attribute value</p> |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                       |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-049                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |  |
+| <b>TP label</b>          | Whitepaper. Pulsatile Quality Numeric Object (Spot-Check Measurement) – Unit-Code Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | PQ Numeric 6; M       |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Pulsatile Quality Numeric Object – Unit-Code attribute in transcoder output when using spot-check measurement mode.</p> <p>[AND]</p> <p>Unit-Code is set to MDC_DIM_PERCENT</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |  |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0100 1100 (MSB → LSB). Pulse Amplitude Index field is supported (bit 6). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support</li> </ol> </li> </ol> </li> </ol> |                       |  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>b. PLX Spot-Check Measurement (0x2A5E)</p> <ul style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 1001 (MSB → LSB). Timestamp and Pulse Amplitude Index fields are present. Measurement Status and Device and Sensor Status fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in the PHG transcoder output the Pulsatile Quality Numeric Object – Unit-Code attribute</p> <p>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <ul style="list-style-type: none"> <li>a) 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 spot-check measurement to PHG under test</li> <li>b) Check in PHG transcoder output the Pulsatile Quality Numeric Object – Unit-Code attribute</li> </ul> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the Pulsatile Quality Numeric Object – Unit-Code attribute is present and its set to MDC_DIM_PERCENT.</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Unit-Code attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulsatile Quality Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_UNIT_CODE (2454)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: MDC_DIM_PERCENT or 544 (dec) or 02 20 (hex)</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|  |                                                                                                                                                                                                                                                     |
+|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Unit-Code attribute value (check OBX-6):</p> <pre>OBX n NM 150320^MDC_SAT_O2_QUAL^MDC m.0.0.x [value]] 262688^MDC_DIM_PERCENT^MDC    R   [current_date_time]</pre> |
+|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |  |  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-050                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |  |  |
+| <b>TP label</b>          | Whitepaper. Pulsatile Quality Numeric Object (Continuous Measurements) – Unit-Code Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                       |  |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [Bluetooth PHDT v1.6] |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | PQ Numeric 12; M      |  |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Pulsatile Quality Numeric Object – Unit-Code attribute in transcoder output when using continuous measurements.</p> <p>[AND]</p> <p>Unit-Code is set to MDC_DIM_PERCENT</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |  |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |  |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |  |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0111 0000 (MSB → LSB). Fast and slow response modes are supported (bits 4 and 5). Pulse Amplitude Index field is supported (bit 6).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Continuous Measurement (0x2A5F) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0001 0011(MSB → LSB). SpO2PR-Fast, SpO2PR-Slow and Pulse Amplitude Index fields are present. Measurement Status, and Device and Sensor Status fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Normal – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                       |  |  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>iv. Field: SpO2PR-Fast - SpO2 (%)</p> <ul style="list-style-type: none"> <li>Format: SFLOAT</li> <li>Value: Not Relevant</li> </ul> <p>v. Field: SpO2PR-Fast - PR (bpm)</p> <ul style="list-style-type: none"> <li>Format: SFLOAT</li> <li>Value: Not Relevant</li> </ul> <p>vi. Field: SpO2PR-Slow - SpO2 (%)</p> <ul style="list-style-type: none"> <li>Format: SFLOAT</li> <li>Value: Not Relevant</li> </ul> <p>vii. Field: SpO2PR-Slow - PR (bpm)</p> <ul style="list-style-type: none"> <li>Format: SFLOAT</li> <li>Value: Not Relevant</li> </ul> <p>viii. Field: Measurement Status</p> <ul style="list-style-type: none"> <li>This field is not included</li> </ul> <p>ix. Field: Device and Sensor Status</p> <ul style="list-style-type: none"> <li>This field is not included</li> </ul> <p>x. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>Format: SFLOAT</li> <li>Value: Not Relevant</li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the Pulsatile Quality Numeric Object – Unit-Code attribute.</p> |
+| <b>Pass/Fail criteria</b>                   | In Step 6, the Pulsatile Quality Numeric Object – Unit-Code attribute is present and it is set to MDC_DIM_PERCENT.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Unit-Code attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulsatile Quality Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_UNIT_CODE (2454)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: MDC_DIM_PERCENT or 544 (dec) or 02 20 (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this for each SpO2 object with Unit-Code attribute value (check OBX-6):</p> <pre>OBX[n NM 150320^MDC_SAT_O2_QUAL^MDC m.0.0.x [value]  <b>262688^MDC_DIM_PERCENT^MDC</b>    R  [current_date_time]</pre>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+|                 |                                                                                                       |                       |                     |
+|-----------------|-------------------------------------------------------------------------------------------------------|-----------------------|---------------------|
+| <b>TP Id</b>    | TP/LP-PAN/PHG/PHDTW/PLX/BV-051                                                                        |                       |                     |
+| <b>TP label</b> | Whitepaper. Pulsatile Quality Numeric Object (Spot-Check Measurement) – Absolute-Time-Stamp Attribute |                       |                     |
+| <b>Coverage</b> | <b>Spec</b>                                                                                           | [Bluetooth PHDT v1.6] |                     |
+|                 | <b>Testable</b>                                                                                       | PQ Numeric 7; M       | Date-Time Conv 2; M |
+
+|                          | items                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Date-Time Conv 4; M | Date-Time Conv 5; M |  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------------------|--|
+| <b>Test purpose</b>      | Check that:<br>PHG transcodes Time Stamp field of Spot-Check Measurement characteristic into Pulsatile Quality Numeric Object - Absolute-Time-Stamp attribute<br>[AND]<br>PHG transcodes the Bluetooth Time Stamp field format to Absolute Time format<br>[AND]<br>The fraction of seconds in Absolute Time at transcoder output is 0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                     |                     |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                     |                     |  |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                     |                     |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                     |                     |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a Spot-Check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0100 1100 (MSB → LSB). Pulse Amplitude Index field is supported (bit 6). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 1001 (MSB → LSB). Pulse Amplitude Index and Timestamp fields are present. Measurement Status and Device and Sensor Status fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: October 12nd, 2015, 10:39:27</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                     |                     |  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>vii. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the Pulsatile Quality Numeric Object – Absolute-Time-Stamp attribute</p> <p>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <p>a) 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 spot-check measurement to PHG under test</p> <p>b) Check in PHG transcoder output the Pulsatile Quality Numeric Object – Absolute-Time-Stamp attribute</p>                                                                                                                                                                                              |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the Pulsatile Quality Numeric Object – Absolute-Time-Stamp attribute is present, its value matches with Time Stamp field of Spot-Check Measurement characteristic and fraction of seconds is set to 0.</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Absolute-Time-Stamp attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulsatile Quality Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_TIME_STAMP_ABS (2448)</li> <li><input type="checkbox"/> 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)</li> <li><input type="checkbox"/> Attribute-value: <ul style="list-style-type: none"> <li>• century: 20 (hex) or 32 (dec)</li> <li>• year: 15 (hex) or 21 (dec)</li> <li>• month: 10 (hex) or 16 (dec)</li> <li>• day: 12 (hex) or 18 (dec)</li> <li>• hour: 10 (hex) or 16 (dec)</li> <li>• minute: 39 (hex) or 57 (dec)</li> <li>• second: 27 (hex) or 39 (dec)</li> <li>• sec-fractions: 00 (hex) or 0 (dec)</li> </ul> </li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Absolute-Time-Stamp attribute value (check OBX-14):</p> <p>OBX n NM 150320^MDC_SAT_O2_QUAL^MDC m.0.0.x [value]<br/>262688^MDC_DIM_PERCENT^MDC   R  20151012103927+0000</p> |
+
+|                 |                                                                                                 |                       |
+|-----------------|-------------------------------------------------------------------------------------------------|-----------------------|
+| <b>TP Id</b>    | TP/LP-PAN/PHG/PHDTW/PLX/BV-052                                                                  |                       |
+| <b>TP label</b> | Pulsatile Quality Numeric Object (Spot-Check Measurement) – Basic-Nu-Observed-Value Attribute 1 |                       |
+| <b>Coverage</b> | <b>Spec</b>                                                                                     | [Bluetooth PHDT v1.6] |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                 |                       |  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------------|--|
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | PQ Numeric 8; M | Short Float Type 1; C |  |
+| <b>Test purpose</b>      | Check that:<br>PHG transcodes Pulse Amplitude Index value of the PLX Spot-Check Measurement characteristic into Pulsatile Quality Numeric Object - Basic-Nu-Observed-Value attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                 |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                 |                       |  |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                 |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                 |                       |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a Spot-Check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0100 1100 (MSB → LSB). Pulse Amplitude Index field is supported (bit 6). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 1001 (MSB → LSB). Timestamp and Pulse Amplitude Index fields are present. Measurement Status and Device and Sensor Status fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 15.0 (%)</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                 |                       |  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ol style="list-style-type: none"> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</li> <li>5. The simulated PHD sends the Measurement to PHG under test.</li> <li>6. Check in PHG transcoder output the Pulsatile Quality Numeric Object – Basic-Nu-Observed-Value attribute</li> <li>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN <ol style="list-style-type: none"> <li>a) 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 spot-check measurement to the PHG under test</li> <li>b) Check in PHG transcoder output the Pulsatile Quality Numeric Object – Basic-Nu-Observed-Value attribute</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the Pulsatile Quality Numeric Object – Basic-Nu-Observed-Value attribute is present and its value matches with the value of the Pulse Amplitude Index of the PLX Spot-Check Measurement characteristic (15.0 %).</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <ol style="list-style-type: none"> <li>a) IEEE 11073 Objects and Attributes<br/>Basic-Nu-Observed-Value attribute is present: <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulsatile Quality Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)</li> <li><input type="checkbox"/> Attribute-type: SFLOAT</li> <li><input type="checkbox"/> Attribute-value: 00 0F (hex) or F0 96 (hex) or E5 DC (hex) or 15.0 (dec)</li> </ul> </li> <li>b) WAN PCD-01 message<br/>PCD-01 message includes a segment like this with Basic-Nu-Observed-Value attribute value (check OBX-5): <pre>OBX n NM 150320^MDC_SAT_O2_QUAL^MDC m.0.0.x 15.0  262688^MDC_DIM_PERCENT^MDC    R  [current_date_time]</pre> </li> </ol>                                                                                                                                                                                        |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |                  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-053                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |                  |
+| <b>TP label</b>          | Whitepaper. Pulsatile Quality Numeric Object (Spot-Check Measurement) – Basic-Nu-Observed-Value Attribute 2                                                                                                                                                                                                                                                                                                                                                                 |                       |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | [Bluetooth PHDT v1.6] |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                       | PQ Numeric 8; M       | PQ Numeric 14; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG transcodes Pulse Amplitude Index value of the PLX Spot-Check Measurement characteristic into Pulsatile Quality Numeric Object - Basic-Nu-Observed-Value attribute</p> <p>[AND]</p> <p>PHG assigns special value NaN (0x07FF) when SpO2 value is unavailable.</p>                                                                                                                                                                                  |                       |                  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |                  |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                       |                  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                          |                       |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a Spot-Check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of</li> </ol> |                       |                  |
+
+interest for this Test Case are:
+
+#### a. PLX Features (0x2A60)
+
+###### i. Field: Supported Features
+
+- Format: 16 bit
+- Value: 0000 0000 0100 1100 (MSB → LSB). Pulse Amplitude Index field is supported (bit 6). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).
+
+###### ii. Field: Measurement Status Support
+
+- This field is not included
+
+##### iii. Field: Device and Sensor Status Support
+
+- This field is not included
+
+#### b. PLX Spot-Check Measurement (0x2A5E)
+
+###### i. Field: Flags
+
+- Format: 8 bit
+- Value: 0000 1001 (MSB → LSB). Timestamp and Pulse Amplitude Index fields are present. Measurement Status and Device and Sensor Status fields are not present. Device Clock is set.
+
+###### ii. Field: SpO2PR-Spot-Check - SpO2 (%)
+
+- Format: SFLOAT
+- Value: Not Relevant
+
+###### iii. Field: SpO2PR-Spot-Check – PR (bpm)
+
+- Format: SFLOAT
+- Value: Not Relevant
+
+##### iv. Field: Time Stamp
+
+- Format: Date and Time
+- Value: Not Relevant
+
+###### v. Field: Measurement Status
+
+- This field is not included
+
+###### vi. Field: Device and Sensor Status
+
+- This field is not included
+
+###### vii. Field: Pulse Amplitude Index (%)
+
+- Format: SFLOAT
+- Value: 07 FF (hex). Special value: NaN
+
+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 PLX Features characteristic.
+
+5. The simulated PHD sends the Measurement to the PHG under test.
+
+6. Check in PHG transcoder output the Pulsatile Quality Numeric Object – Basic-Nu-Observed-Value attribute
+
+7. IF C\_MAN\_BLE\_042 = TRUE (PHG supports RACP) THEN
+
+a) 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 spot-check measurement to PHG under test
+
+b) Check in PHG transcoder output the Pulsatile Quality Numeric Object – Basic-Nu-Observed-Value attribute
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Pass/Fail criteria</b>                   | In Step 6, the Pulsatile Quality Numeric Object – Basic-Nu-Observed-Value attribute is present and its value is 0x07FF (NaN).<br>If the PHG supports RACP, the same criteria applies to Step 7.b.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Basic-Nu-Observed-Value attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulsatile Quality Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)</li> <li><input type="checkbox"/> Attribute-type: SFLOAT</li> <li><input type="checkbox"/> Attribute-value: 07 FF (hex) or NaN (note that a decimal value is not allowed)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Basic-Nu-Observed-Value attribute value (check OBX-5):</p> <p>OBX[n NM 150320^MDC_SAT_O2_QUAL^MDC m.0.0.x  <br/>262688^MDC_DIM_PERCENT^MDC  NAN  X  [current_date_time]</p> |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                       |                       |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-054                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |                       |
+| <b>TP label</b>          | Whitepaper. Pulsatile Quality Numeric Object (Continuous Measurements) – Basic-Nu-Observed-Value Attribute 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |                       |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | [Bluetooth PHDT v1.6] |                       |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | PQ Numeric 13; M      | Short Float Type 1; C |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG transcodes Pulse Amplitude Index value of the PLX Continuous Measurement characteristic into Pulsatile Quality Numeric Object - Basic-Nu-Observed-Value attribute</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                       |                       |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |                       |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                       |                       |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |                       |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0111 0000 (MSB → LSB). Fast and slow response modes and Pulse Amplitude Index fields are supported (bits 4, 5 and 6).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Continuous Measurement (0x2A5F) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0001 0011 (MSB → LSB). SpO2PR-Fast, SpO2PR-Slow and Pulse Amplitude Index fields are present. Measurement Status and Device and Sensor Status fields are not present.</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                       |                       |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ul style="list-style-type: none"> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Normal - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: SpO2PR-Fast - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: SpO2PR-Fast - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vi. Field: SpO2PR-Slow - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vii. Field: SpO2PR-Slow - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>viii. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>ix. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>x. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 15.0 (%)</li> </ul> </li> </ul> <ol style="list-style-type: none"> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</li> <li>5. The simulated PHD sends the Measurement to the PHG under test.</li> <li>6. Check in PHG transcoder output the Pulsatile Quality Numeric Object – Basic-Nu-Observed-Value attribute.</li> </ol> |
+| <b>Pass/Fail criteria</b>                   | In Step 6, the Pulsatile Quality Numeric object – Basic-Nu-Observed-Value attribute is present and its value matches with the value of the Pulse Amplitude Index field of the PLX Continuous Measurement characteristic (15.0 %).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <ul style="list-style-type: none"> <li>a) IEEE 11073 Objects and Attributes<br/>Basic-Nu-Observed-Value attribute is present: <ul style="list-style-type: none"> <li><li><input type="checkbox"/></li> Object: Pulsatile Quality Numeric Object</li> <li><li><input type="checkbox"/></li> Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)</li> <li><li><input type="checkbox"/></li> Attribute-type: SFLOAT</li> <li><li><input type="checkbox"/></li> Attribute-value: 00 0F (hex) or F0 96 (hex) or E5 DC (hex) or 15.0 (dec)</li> </ul> </li> <li>b) WAN PCD-01 message<br/>PCD-01 message includes a segment like this with Basic-Nu-Observed-Value attribute value (check OBX-5):</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|  |                                                                                                           |
+|--|-----------------------------------------------------------------------------------------------------------|
+|  | OBX[n NM 150320^MDC_SAT_O2_QUAL^MDC m.0.0.x 15.0]<br>262688^MDC_DIM_PERCENT^MDC    R  [current_date_time] |
+|--|-----------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |                  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-055                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                       |                  |
+| <b>TP label</b>          | Whitepaper. Pulsatile Quality Numeric Object (Continuous Measurements) – Basic-Nu-Observed-Value Attribute 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |                  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [Bluetooth PHDT v1.6] |                  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | PQ Numeric 13; M      | PQ Numeric 14; M |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG transcodes Pulse Amplitude Index value of the PLX Continuous Measurement characteristic into Pulsatile Quality Numeric Object - Basic-Nu-Observed-Value attribute</p> <p>[AND]</p> <p>PHG assigns special value NaN (0x07FF) when Pulsatile Quality value is unavailable.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |                  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |                  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |                  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0111 0000 (MSB → LSB). Fast and slow response modes are supported (bits 4 and 5). Pulse Amplitude Index field is supported (bit 6).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Continuous Measurement (0x2A5F) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0001 0011 (MSB → LSB). SpO2PR-Fast, SpO2PR-Slow and Pulse Amplitude Index fields are present. Measurement Status and Device and Sensor Status fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Normal - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: SpO2PR-Fast - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                       |                  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>v. Field: SpO2PR-Fast - PR (bpm)</p> <ul style="list-style-type: none"> <li>Format: SFLOAT</li> <li>Value: Not Relevant</li> </ul> <p>vi. Field: SpO2PR-Slow - SpO2 (%)</p> <ul style="list-style-type: none"> <li>Format: SFLOAT</li> <li>Value: Not Relevant</li> </ul> <p>vii. Field: SpO2PR-Slow - PR (bpm)</p> <ul style="list-style-type: none"> <li>Format: SFLOAT</li> <li>Value: Not Relevant</li> </ul> <p>viii. Field: Measurement Status</p> <ul style="list-style-type: none"> <li>This field is not included</li> </ul> <p>ix. Field: Device and Sensor Status</p> <ul style="list-style-type: none"> <li>This field is not included</li> </ul> <p>x. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>Format: SFLOAT</li> <li>Value: 07 FF (hex). Special value: NaN</li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the Pulsatile Quality Numeric Object – Basic-Nu-Observed-Value attribute.</p> |
+| <b>Pass/Fail criteria</b>                   | In Step 6, the Pulsatile Quality Numeric Object – Basic-Nu-Observed-Value attribute is present and its value is 0x07FF (NaN).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Basic-Nu-Observed-Value attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Pulsatile Quality Numeric Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_NU_VAL_OBS_BASIC (2636)</li> <li><input type="checkbox"/> Attribute-type: SFLOAT</li> <li><input type="checkbox"/> Attribute-value: 07 FF (hex) or NaN (note that a decimal value is not allowed)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Basic-Nu-Observed-Value attribute value (check OBX-5):</p> <p>OBX n NM 150320^MDC_SAT_O2_QUAL^MDC m.0.0.x  <br/>262688^MDC_DIM_PERCENT^MDC  NAN  X  [current_date_time]</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                     |                                                                                                                                                                  |                       |                     |
+|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|
+| <b>TP Id</b>        | TP/LP-PAN/PHG/PHDTW/PLX/BV-056                                                                                                                                   |                       |                     |
+| <b>TP label</b>     | Whitepaper. Pulsatile Quality measurement value (Spot-Check Measurement)                                                                                         |                       |                     |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                      | [Bluetooth PHDT v1.6] |                     |
+|                     | <b>Testable items</b>                                                                                                                                            | Short Float Type 1; C | Date-Time Conv 1; M |
+|                     |                                                                                                                                                                  | PQ Numeric 8; M       | PQ Numeric 7; M     |
+| <b>Test purpose</b> | <p>Check that:</p> <p>PHG processes correctly the Pulse Amplitude Index value (%) and the value of the Time Stamp field of the PLX Spot-Check characteristic</p> |                       |                     |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a Spot-Check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristic of interest for this Test Case is: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0100 1100 (MSB → LSB). Pulse Amplitude Index field is supported (bit 6). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> <li>b. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 1001 (MSB → LSB). Pulse Amplitude Index and Timestamp fields are present. Measurement Status and Device and Sensor Status fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: 15.0 (%)</li> </ul> </li> </ol> </li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read PLX Features characteristic.</li> <li>5. The simulated PHD sends the Measurement to the PHG under test.</li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>6. Check that the PHG accepts the measurement and decodes its value properly (Pulse Amplitude Index value, units and time stamp).</p> <p>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <p style="padding-left: 20px;">a) 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 spot-check measurement to PHG under test</p> <p style="padding-left: 20px;">b) Check that PHG accepts the measurement and decodes its value properly (Pulse Amplitude Index value, units and time stamp)</p> |
+| <b>Pass/Fail criteria</b> | <p>In Step 6, the PHG under test shows the following measurement Pulsatile Quality = 15.0 (%) with timestamp '2015-10-12 10:39:27'.</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b</p>                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| <b>Notes</b>              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |                       |  |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-057                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |  |
+| <b>TP label</b>          | Whitepaper. Device and Sensor Status Enumeration Object (Spot-Check Measurement) - Handle Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | DSS Enumeration 1; O  |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG does not include Device and Sensor Status Enumeration Object – Handle Attribute in transcoder output when using spot-check measurement mode.</p> <p>[OR]</p> <p>If PHG includes Device and Sensor Status Enumeration Object – Handle attribute in transcoder output, then its value shall be different than 0</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040 AND C_MAN_BLE_041                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |  |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 <b>1110</b> (MSB → LSB). Device and Sensor Status field is supported (bit 1). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• Format: 24 bit</li> <li>• Value: Not Relevant</li> </ul> </li> </ol> </li> <li>b. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags</li> </ol> </li> </ol> </li> </ol> |                       |  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0101 (MSB → LSB). Timestamp and Device and Sensor Status fields are present. Pulse Amplitude Index and Measurement Status fields are not present. Device Clock is set.</li> </ul> <ul style="list-style-type: none"> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• Format: 24 bit</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included.</li> </ul> </li> </ul> <ol style="list-style-type: none"> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</li> <li>5. The simulated PHD sends the measurement to the PHG under test.</li> <li>6. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Handle attribute</li> <li>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN <ol style="list-style-type: none"> <li>a) 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 spot-check measurement to PHG under test</li> <li>b) Check in PHG transcoder output the Device and Sensor Status Enumeration Object – Handle attribute</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the Device and Sensor Status Enumeration Object – Handle attribute is not present or, if it is present then its value is different than 0</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <ol style="list-style-type: none"> <li>a) IEEE 11073 Objects and Attributes <p>Handle attribute is not present, or if it is present then:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Device and Sensor Status Enumeration Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_HANDLE (2337)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: Any value different than 0</li> </ul> </li> <li>b) WAN PCD-01 message <p>PCD-01 message does not include segments with Handle attribute value</p> </li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |  |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-058                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |  |
+| <b>TP label</b>          | Whitepaper. Device and Sensor Status Enumeration Object (Continuous Measurements) - Handle Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | DSS Enumeration 5; O  |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG does not include Device and Sensor Status Enumeration Object – Handle Attribute in transcoder output when using continuous measurements</p> <p>[OR]</p> <p>If PHG includes Device and Sensor Status Enumeration Object – Handle attribute in transcoder output, then its value shall be different than 0</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040 AND C_MAN_BLE_041                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                       |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 0010 (MSB → LSB). Device and Sensor Status field is supported (bit 1).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• Format: 24 bit</li> <li>• Value: Not Relevant</li> </ul> </li> </ol> </li> <li>b. PLX Continuous Measurement (0x2A5F) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 1011 (MSB → LSB). SpO2PR-Fast, SpO2PR-Slow and Device and Sensor Status fields are present. Measurement Status and Pulse Amplitude Index fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Normal – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: SpO2PR-Fast - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: SpO2PR-Fast - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                       |  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ul style="list-style-type: none"> <li>• Value: Not Relevant</li> </ul> vi. Field: SpO2PR-Slow - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> vii. Field: SpO2PR-Slow - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> viii. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> ix. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• Format: 24 bit</li> <li>• Value: Not Relevant.</li> </ul> x. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> 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).<br>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.<br>5. The simulated PHD sends the Measurement to the PHG under test.<br>6. Check in PHG transcoder output the Device and Sensor Status Enumeration Object – Handle attribute. |
+| <b>Pass/Fail criteria</b>                   | In Step 6, the Device and Sensor Status Enumeration Object – Handle attribute is not present or, if it is present then its value is different than 0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Notes<br/>(To assist manual testing)</b> | Possible values in typical points of observation after transcoder output are:<br>a) IEEE 11073 Objects and Attributes<br>Handle attribute is not present, or if it is present then:<br><ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Device and Sensor Status Enumeration Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_HANDLE (2337)</li> <li><input type="checkbox"/> Attribute-type: INT-U16</li> <li><input type="checkbox"/> Attribute-value: Any value different than 0</li> </ul> b) WAN PCD-01 message<br>PCD-01 message does not include segments with Handle attribute value                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+|                      |                                                                                                                                                                                                                             |                       |  |
+|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>         | TP/LP-PAN/PHG/PHDTW/PLX/BV-059                                                                                                                                                                                              |                       |  |
+| <b>TP label</b>      | Whitepaper. Device and Sensor Status Enumeration Object (Spot-Check Measurement) - Type Attribute                                                                                                                           |                       |  |
+| <b>Coverage</b>      | <b>Spec</b>                                                                                                                                                                                                                 | [Bluetooth PHDT v1.6] |  |
+|                      | <b>Testable items</b>                                                                                                                                                                                                       | DSS Enumeration 2; M  |  |
+| <b>Test purpose</b>  | Check that:<br>PHG includes Device and Sensor Status Enumeration Object – Type attribute in transcoder output when using spot-check measurement mode.<br>[AND]<br>Type is set to {MDC_PART_SCADA, MDC_PULS_OXIM_DEV_STATUS} |                       |  |
+| <b>Applicability</b> | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040 AND C_MAN_BLE_041                                                                                                                                                         |                       |  |
+| <b>Other PICS</b>    | C_MAN_BLE_042                                                                                                                                                                                                               |                       |  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 <b>1110</b> (MSB → LSB). Device and Sensor Status field is supported (bit 1). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• Format: 24 bit</li> <li>• Value: Not Relevant</li> </ul> </li> </ol> </li> <li>b. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0101 (MSB → LSB). Timestamp and Device and Sensor Status fields are present. Pulse Amplitude Index and Measurement Status fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• Format: 24 bit</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristics.</li> <li>5. The simulated PHD sends the Measurement to the PHG under test.</li> <li>6. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Type attribute</li> </ol> |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <p>a) 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 spot-check measurement to the PHG under test</p> <p>b) Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Type attribute</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the Device and Sensor Status Enumeration Object – Type attribute is present and its value is {MDC_PART_SCADA, MDC_PULS_OXIM_DEV_STATUS}</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Type attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Device and Sensor Status Enumeration Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_TYPE (2351)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}</li> <li><input type="checkbox"/> Attribute-value: <ul style="list-style-type: none"> <li>• partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)</li> <li>• code: MDC_PULS_OXIM_DEV_STATUS or 19532 (dec) or 4C 4C (hex)</li> </ul> </li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Type attribute (check OBX-3):</p> <p>OBX n CWE 150604^MDC_PULS_OXIM_DEV_STATUS^MDC<br/>m.0.0.x [value]     R</p> |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |  |  |  |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-060                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |  |  |  |
+| <b>TP label</b>          | Whitepaper. Device and Sensor Status Enumeration Object (Continuous Measurements) - Type Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |  |  |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | [Bluetooth PHDT v1.6] |  |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | DSS Enumeration 6; M  |  |  |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Device and Sensor Status Enumeration Object – Type attribute in transcoder output when using continuous measurements.</p> <p>[AND]</p> <p>Type is set to {MDC_PART_SCADA, MDC_PULS_OXIM_DEV_STATUS}</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |  |  |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040 AND C_MAN_BLE_041                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                       |  |  |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                       |  |  |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |  |  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0011 0010 (MSB → LSB). Device and Sensor Status is supported (bit 1). Fast and slow response modes are supported (bits 4</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                       |  |  |  |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>and 5).</p> <ul style="list-style-type: none"> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• Format: 24 bit</li> <li>• Value: Not Relevant</li> </ul> </li> </ul> <p>b. PLX Continuous Measurement (0x2A5F)</p> <ul style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 1011 (MSB → LSB). SpO2PR-Fast, SpO2PR-Slow and Device and Sensor Status fields are present. Measurement Status and Pulse Amplitude Index fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Normal – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: SpO2PR-Fast - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: SpO2PR-Fast - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vi. Field: SpO2PR-Slow - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vii. Field: SpO2PR-Slow - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>viii. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>ix. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• Or Format: 24 bit</li> <li>• Value: Not Relevant.</li> </ul> </li> <li>x. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in PHG transcoder output the Device and Sensor Status Enumeration Object – Type attribute.</p> |
+| <b>Pass/Fail criteria</b> | In Step 6, the Pulsatile Quality Numeric Object – Type attribute is present and its value is {MDC_PART_SCADA, MDC_PULS_OXIM_DEV_STATUS}                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Type attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Device and Sensor Status Enumeration Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ID_TYPE (2351)</li> <li><input type="checkbox"/> Attribute-type: SEQUENCE {partition (INT-U16), code (INT-U16)}</li> <li><input type="checkbox"/> Attribute-value: <ul style="list-style-type: none"> <li>• partition: MDC_PART_SCADA or 2 (dec) or 00 02 (hex)</li> <li>• code: MDC_PULS_OXIM_DEV_STATUS or 19532 (dec) or 4C 4C (hex)</li> </ul> </li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Type attribute (check OBX-3):</p> <p style="padding-left: 40px;">OBX n CWE 150604^MDC_PULS_OXIM_DEV_STATUS^MDC <br/>m.0.0.x [value]     R</p> |
+|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |  |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-061                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |  |
+| <b>TP label</b>          | Whitepaper. Device and Sensor Status Enumeration Object (Spot-Check Measurement) - Metric-Spec-Small Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | DSS Enumeration 3; M  |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Device and Sensor Status Enumeration Object – Metric-Spec-Small attribute in transcoder output when using spot-check measurement mode.</p> <p>[AND]</p> <p>Metric-Spec-Small is set to {0x0040} (mss-acc-agent-initiated)</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040 AND C_MAN_BLE_041                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                       |  |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                       |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). The Simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 <b>1110</b> (MSB → LSB). Device and Sensor Status field is supported (bit 1). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• Format: 24 bit</li> <li>• Value: Not Relevant</li> </ul> </li> </ol> </li> <li>b. PLX Spot-Check Measurement (0x2A5E)</li> </ol> </li> </ol> |                       |  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <ul style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 0101 (MSB → LSB). Timestamp and Device and Sensor Status fields are present. Pulse Amplitude Index and Measurement Status fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%)  <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• Format: Date and Time</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>vi. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• Format: 24 bit</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vii. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ul> <ol style="list-style-type: none"> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristics.</li> <li>5. The simulated PHD sends the Measurement to the PHG under test.</li> <li>6. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Metric-Spec-Small attribute</li> <li>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN <ol style="list-style-type: none"> <li>a) 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 spot-check measurement to PHG under test</li> <li>b) Check in PHG transcoder output the Device and Sensor Status Enumeration Object – Metric-Spec-Small attribute</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b>                   | <p>In Step 6, the Device and Sensor Status Enumeration Object – Metric-Spec-Small attribute is present and its value is {0x0040} (mss-acc-agent-initiated).</p> <p>If the PHG supports RACP, the same criteria applies to Step 7.b.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <ul style="list-style-type: none"> <li>a) IEEE 11073 Objects and Attributes <p>Metric-Spec-Small attribute is present:</p> <ul style="list-style-type: none"> <li>❑ Object: Device and Sensor Status Enumeration Object</li> <li>❑ Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)</li> <li>❑ Attribute-type: BITS-16</li> <li>❑ Attribute-value: 00 40 (hex) or BITS mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE</li> </ul> </li> <li>b) WAN PCD-01 message</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+
+|  |                                                                                 |
+|--|---------------------------------------------------------------------------------|
+|  | PCD-01 message does not include segments with Metric-Spec-Small attribute value |
+|--|---------------------------------------------------------------------------------|
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |  |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>             | TP/LP-PAN/PHG/PHDTW/PLX/BV-062                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |  |
+| <b>TP label</b>          | Whitepaper. Device and Sensor Status Enumeration Object (Continuous Measurements) - Metric-Spec-Small Attribute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |  |
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [Bluetooth PHDT v1.6] |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | DSS Enumeration 7; M  |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG includes Device and Sensor Status Enumeration Object – Metric-Spec-Small attribute in transcoder output when using continuous measurements.</p> <p>[AND]</p> <p>Metric-Spec-Small is set to {0x0040} (mss-acc-agent-initiated)</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040 AND C_MAN_BLE_041                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                       |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                       |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0011 0010 (MSB → LSB). Device and Sensor Status is supported. Fast and slow response modes are supported (bits 4 and 5).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• Format: 24 bit</li> <li>• Value: Not Relevant</li> </ul> </li> </ol> </li> <li>b. PLX Continuous Measurement (0x2A5F) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 1011 (MSB → LSB). SpO2PR–Fast, SpO2PR–Slow and Device and Sensor Status fields are present. Measurement Status and Pulse Amplitude Index fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Normal – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: SpO2PR-Fast - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                       |  |
+
+|                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                             | <p>v. Field: SpO2PR-Fast - PR (bpm)</p> <ul style="list-style-type: none"> <li>Format: SFLOAT</li> <li>Value: Not Relevant</li> </ul> <p>vi. Field: SpO2PR-Slow - SpO2 (%)</p> <ul style="list-style-type: none"> <li>Format: SFLOAT</li> <li>Value: Not Relevant</li> </ul> <p>vii. Field: SpO2PR-Slow - PR (bpm)</p> <ul style="list-style-type: none"> <li>Format: SFLOAT</li> <li>Value: Not Relevant</li> </ul> <p>viii. Field: Measurement Status</p> <ul style="list-style-type: none"> <li>This field is not included</li> </ul> <p>ix. Field: Device and Sensor Status</p> <ul style="list-style-type: none"> <li>Or Format: 24 bit</li> <li>Value: Not Relevant.</li> </ul> <p>x. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>This field is not included</li> </ul> <p>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).</p> <p>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</p> <p>5. The simulated PHD sends the Measurement to the PHG under test.</p> <p>6. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Metric-Spec-Small attribute</p> |
+| <b>Pass/Fail criteria</b>                   | In Step 6, the Device and Sensor Status Enumeration Object – Metric-Spec-Small attribute is present and its value is {0x0040} (mss-acc-agent-initiated).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Notes<br/>(To assist manual testing)</b> | <p>Possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Metric-Spec-Small attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Device and Sensor Status Enumeration Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_METRIC_SPEC_SMALL (2630)</li> <li><input type="checkbox"/> Attribute-type: BITS-16</li> <li><input type="checkbox"/> Attribute-value: 00 40 (hex) or BITS mss-acc-agent-initiated(9) set to TRUE and remaining BITS set to FALSE</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message does not include segments with Metric-Spec-Small attribute value</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+|                     |                                                                                                                                                                                                                         |                       |  |
+|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|
+| <b>TP Id</b>        | TP/LP-PAN/PHG/PHDTW/PLX/BV-063                                                                                                                                                                                          |                       |  |
+| <b>TP label</b>     | Whitepaper. Device and Sensor Status Enumeration Object (Spot-Check Measurement) – Enum-Observed-Value-Bit-Str Attribute                                                                                                |                       |  |
+| <b>Coverage</b>     | <b>Spec</b>                                                                                                                                                                                                             | [Bluetooth PHDT v1.6] |  |
+|                     | <b>Testable items</b>                                                                                                                                                                                                   | DSS Enumeration 4; M  |  |
+| <b>Test purpose</b> | <p>Check that:</p> <p>PHG transcodes Device and Sensor Status field of the PLX Spot-Check Measurement characteristic into Device and Sensor Status Enumeration Object - Enum-Observed-Value-Basic-Bit-Str attribute</p> |                       |  |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                          | [AND]<br>PHG transcodes the Bluetooth Device and Sensor Status field of the PLX Spot-Check characteristic to 11073 Enum-Observed-Value-Basic-Bit-Str attribute properly                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040 AND C_MAN_BLE_041                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Other PICS</b>        | C_MAN_BLE_042                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a spot-check measurement ready to be sent and it is in the Advertising state (it is discoverable). The simulated PHD also supports the RACP characteristic and has an identical spot-check measurement temporarily stored.</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Spot-Check Measurement (0x2A5E)</li> <li>b. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0000 <b>1110</b> (MSB → LSB). Device and Sensor Status support is present (bit 1). Measurement Storage for spot-check measurements is supported (bit 2). Timestamp for Spot-Check measurements is supported (bit 3).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• Format: 24 bit</li> <li>• Value: 0000 0000 <b>1111 1111 1111 1111</b> (MSB → LSB). All Device and Sensor Status bits are supported</li> </ul> </li> </ol> </li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</li> <li>5. The simulated PHD sends the Measurement to the PHG under test with the following value: <ol style="list-style-type: none"> <li>a. PLX Spot-Check Measurement (0x2A5E) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 <b>0101</b> (MSB → LSB). Device and Sensor Status and Timestamp field are present. Measurement Status and Pulse Amplitude Index fields are not present. Device Clock is set.</li> </ul> </li> <li>ii. Field: SpO2PR-Spot-Check - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Spot-Check – PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iv. Field: Time Stamp <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>v. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol> </li> </ol> </li> </ol> |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <p>vi. Field: Device and Sensor Status</p> <ul style="list-style-type: none"> <li>• Format: 24 bit</li> <li>• Value: 0000 0000 0000 0000 0000 0001 (MSB → LSB). Extended Display Update Ongoing (bit 0).</li> </ul> <p>vii. Field: Pulse Amplitude Index (%)</p> <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> <p>6. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute</p> <p>7. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <ol style="list-style-type: none"> <li>a) 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 spot-check measurement to PHG under test</li> <li>b) Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute</li> </ol> <p>8. The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0000 0000 0010 (MSB → LSB). Equipment Malfunction (bit 1). All remaining fields remain equal to those in step 5. Simulated PHD also deletes all stored records in RACP and stores an identical measurement.</p> <p>9. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute</p> <p>10. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <ol style="list-style-type: none"> <li>a) 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 spot-check measurement to the PHG under test</li> <li>b) Check in PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute</li> </ol> <p>11. The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0000 0000 0100 (MSB → LSB). Signal Processing Irregularity Detected (bit 2). All remaining fields remain equal to those in step 5. Simulated PHD also deletes all stored records in RACP and stores an identical measurement.</p> <p>12. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute</p> <p>13. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <ol style="list-style-type: none"> <li>a) 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 spot-check measurement to the PHG under test</li> <li>b) Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute</li> </ol> <p>14. The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0000 0000 1000 (MSB → LSB). Inadequate Signal Detected (bit 3). All remaining fields remain equal to those in step 5. Simulated PHD also deletes all stored records in RACP and stores an identical measurement.</p> <p>15. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute</p> <p>16. IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN</p> <ol style="list-style-type: none"> <li>a) 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 spot-check measurement to PHG under test</li> <li>b) Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute</li> </ol> |
+|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+17. The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0000 0001 0000 (MSB → LSB). Poor Signal Detected (bit 4). All remaining fields remain equal to those in step 5. The simulated PHD also deletes all stored records in RACP and stores an identical measurement.
+18. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute
+19. IF C\_MAN\_BLE\_042 = TRUE (PHG supports RACP) THEN
+  - a) 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 spot-check measurement to PHG under test
+  - b) Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute
+20. The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0000 0010 0000 (MSB → LSB). Low Perfusion Detected (bit 5). All remaining fields remain equal to those in step 5. Simulated PHD also deletes all stored records in RACP and stores an identical measurement.
+21. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute
+22. IF C\_MAN\_BLE\_042 = TRUE (PHG supports RACP) THEN
+  - a) 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 spot-check measurement to the PHG under test
+  - b) Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute
+23. The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0000 0100 0000 (MSB → LSB). Erratic Signal Detected (bit 6). All remaining fields remain equal to those in step 5. Simulated PHD also deletes all stored records in RACP and stores an identical measurement.
+24. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute
+25. IF C\_MAN\_BLE\_042 = TRUE (PHG supports RACP) THEN
+  - a) 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 spot-check measurement to the PHG under test
+  - b) Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute
+26. The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0000 1000 0000 (MSB → LSB). Non-Pulsatile Signal Detected (bit 7). All remaining fields remain equal to those in step 5. The simulated PHD also deletes all stored records in RACP and stores an identical measurement.
+27. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute
+28. IF C\_MAN\_BLE\_042 = TRUE (PHG supports RACP) THEN
+  - a) 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 spot-check measurement to the PHG under test
+  - b) Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute
+29. The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0001 0000 0000 (MSB → LSB). Questionable Signal Detected (bit 8). All remaining fields remain equal to those in step 5. The simulated PHD also deletes all stored records in RACP and stores an identical measurement.
+30. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object
+
+- Enum-Observed-Value-Basic-Bit-Str attribute
+- 31. IF C\_MAN\_BLE\_042 = TRUE (PHG supports RACP) THEN
+  - a) 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 spot-check measurement to PHG under test
+  - b) Check in PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute
+- 32. The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0010 0000 0000 (MSB → LSB). Signal Analysis Ongoing (bit 9). All remaining fields remain equal to those in step 5. The simulated PHD also deletes all stored records in RACP and stores an identical measurement.
+- 33. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute
+- 34. IF C\_MAN\_BLE\_042 = TRUE (PHG supports RACP) THEN
+  - a) 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 spot-check measurement to the PHG under test
+  - b) Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute
+- 35. The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0100 0000 0000 (MSB → LSB). Sensor Interference Detected (bit 10). All remaining fields remain equal to those in step 5. The simulated PHD also deletes all stored records in RACP and stores an identical measurement.
+- 36. Check in PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute
+- 37. IF C\_MAN\_BLE\_042 = TRUE (PHG supports RACP) THEN
+  - a) 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 spot-check measurement to the PHG under test
+  - b) Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute
+- 38. The simulated PHD sends a Measurement to PHG under test with Measurement Status field set to 0000 0000 0000 1000 0000 0000 (MSB → LSB). Sensor Unconnected to User (bit 11). All remaining fields remain equal to those in step 5. The simulated PHD also deletes all stored records in RACP and stores an identical measurement.
+- 39. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute
+- 40. IF C\_MAN\_BLE\_042 = TRUE (PHG supports RACP) THEN
+  - a) 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 spot-check measurement to the PHG under test
+  - b) Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute
+- 41. The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0001 0000 0000 0000 (MSB → LSB). Unknown Sensor Connected (bit 12). All remaining fields remain equal to those in step 5. The simulated PHD also deletes all stored records in RACP and stores an identical measurement.
+- 42. Check in PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute
+- 43. IF C\_MAN\_BLE\_042 = TRUE (PHG supports RACP) THEN
+  - a) 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 spot-check measurement to the PHG
+
+140 Rec. ITU-T H.850.6 (08/2020)
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>under test</p> <ol style="list-style-type: none"> <li>Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute</li> </ol> <ol style="list-style-type: none"> <li>The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0010 0000 0000 0000 (MSB → LSB). Sensor Displaced (bit 13). All remaining fields remain equal to those in step 5. The simulated PHD also deletes all stored records in RACP and stores an identical measurement.</li> <li>Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute</li> <li>IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN <ol style="list-style-type: none"> <li>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 spot-check measurement to the PHG under test</li> <li>Check in PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute</li> </ol> </li> <li>The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0100 0000 0000 0000 (MSB → LSB). Sensor Malfunctioning (bit 14). All remaining fields remain equal to those in step 5. The simulated PHD also deletes all stored records in RACP and stores an identical measurement.</li> <li>Check in PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute</li> <li>IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN <ol style="list-style-type: none"> <li>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 spot-check measurement to the PHG under test</li> <li>Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute</li> </ol> </li> <li>The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 1000 0000 0000 0000 (MSB → LSB). Sensor Disconnected (bit 15). All remaining fields remain equal to those in step 5. The simulated PHD also deletes all stored records in RACP and stores an identical measurement.</li> <li>Check in PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute</li> <li>IF C_MAN_BLE_042 = TRUE (PHG supports RACP) THEN <ol style="list-style-type: none"> <li>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 spot-check measurement to the PHG under test</li> <li>Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute</li> </ol> </li> </ol> |
+| <b>Pass/Fail criteria</b> | <p>In Step 6, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “device-extended-update” (0x8000). If PHG supports RACP, same criteria applies to 7.b.</p> <p>In Step 9, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “device-equipment-malfunction” (0x4000). If PHG supports RACP, same criteria applies to 10.b.</p> <p>In Step 12, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “signal-processing-irregularity” (0x2000). If PHG supports RACP, same criteria applies to 13.b.</p> <p>In Step 15, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “signal-inadequate” (0x1000). If PHG supports RACP, same criteria applies to 16.b.</p> <p>In Step 18, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “signal-poor” (0x0800). If PHG supports</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+|                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                                    | <p>RACP, same criteria applies to 19.b.</p> <p>In Step 21, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “signal-low-perfusion” (0x0400). If PHG supports RACP, same criteria applies to 22.b.</p> <p>In Step 24, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “signal-erratic” (0x0200). If PHG supports RACP, same criteria applies to 25.b.</p> <p>In Step 27, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “signal-non-pulsatile” (0x0100). If PHG supports RACP, same criteria applies to 28.b.</p> <p>In Step 30, Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “signal-pulse-questionable” (0x0080). If PHG supports RACP, same criteria applies to 31.b.</p> <p>In Step 33, Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “signal-searching” (0x0040). If PHG supports RACP, same criteria applies to 34.b.</p> <p>In Step 36, Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “signal-interference” (0x0020). If PHG supports RACP, same criteria applies to 37.b.</p> <p>In Step 39, Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “sensor-off” (0x0010). If PHG supports RACP, same criteria applies to 40.b.</p> <p>In Step 42, Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “sensor-unsupported” (0x0008). If PHG supports RACP, same criteria applies to 43.b.</p> <p>In Step 45, Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “sensor-displaced” (0x0004). If PHG supports RACP, same criteria applies to 46.b.</p> <p>In Step 48, Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “sensor-malfunction” (0x0002). If PHG supports RACP, same criteria applies to 49.b.</p> <p>In Step 51, Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “sensor-disconnected” (0x0001). If PHG supports RACP, same criteria applies to 52.b.</p> |
+| <p><b>Notes<br/>(To assist manual testing)</b></p> | <p>In step 6 (and step 7.b if applicable), possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Enum-Observed-Value-Basic-Bit-Str attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Device and Sensor Status Enumeration Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR (2662)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>80 00</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Enum-Observed-Value-Basic-Bit-Str attribute value (check OBX-5):</p> <pre>OBX n CWE 150604^MDC_PULS_OXIM_DEV_STATUS^MDC m.0.0.x 1^device-extended-update(15)     R</pre> <p>In step 9 (and step 10.b if applicable), possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Enum-Observed-Value-Basic-Bit-Str attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Device and Sensor Status Enumeration Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR (2662)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+- Attribute-value: **40 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):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**device-equipment-malfunction(14)**|||||R
+
+In step 12 (and step 13.b if applicable), 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **20 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):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**signal-processing-irregularity(13)**|||||R
+
+In step 15 (and step 16.b if applicable), 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **10 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):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**signal-inadequate(12)**|||||R
+
+In step 18 (and step 19.b if applicable), 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **08 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):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**signal-poor(11)**|||||R
+
+In step 21 (and step 22.b if applicable), 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **04 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):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**signal-low-perfusion(10)**|||||R
+
+In step 24 (and step 25.b if applicable), 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **02 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):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**signal-erratic(9)**|||||R
+
+In step 27 (and step 28.b if applicable), 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **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):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**signal-non-pulsatile(8)**|||||R
+
+In step 30 (and step 31.b if applicable), 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **00 80** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-5):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**signal-**
+
+##### **pulse-questionable(7)|||||R**
+
+In step 33 (and step 34.b if applicable), 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **00 40** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-5):
+
+**OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^signal-searching(6)|||||R**
+
+In step 36 (and step 37.b if applicable), 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **00 20** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-5):
+
+**OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^sensor-interference(5)|||||R**
+
+In step 39 (and step 40.b if applicable), 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **00 10** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-5):
+
+**OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^sensor-off(4)|||||R**
+
+In step 42 (and step 43.b if applicable), 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **00 08** (hex)
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-5):</p> <pre>OBX n CWE 150604^MDC_PULS_OXIM_DEV_STATUS^MDC m.0.0.x 1^sensor-unsupported(3)     R</pre> <p>In step 45 (and step 46.b if applicable), possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Enum-Observed-Value-Basic-Bit-Str attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Device and Sensor Status Enumeration Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR (2662)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>00 04</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-5):</p> <pre>OBX n CWE 150604^MDC_PULS_OXIM_DEV_STATUS^MDC m.0.0.x 1^sensor-displaced(2)     R</pre> <p>In step 48 (and step 49.b if applicable), possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Enum-Observed-Value-Basic-Bit-Str attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Device and Sensor Status Enumeration Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR (2662)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>00 02</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-5):</p> <pre>OBX n CWE 150604^MDC_PULS_OXIM_DEV_STATUS^MDC m.0.0.x 1^sensor-malfunction(1)     R</pre> <p>In step 51 (and step 52.b if applicable), possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Enum-Observed-Value-Basic-Bit-Str attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Device and Sensor Status Enumeration Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR (2662)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>00 01</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-5):</p> <pre>OBX n CWE 150604^MDC_PULS_OXIM_DEV_STATUS^MDC m.0.0.x 1^sensor-disconnected(0)     R</pre> |
+|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                 |                                                                                                                           |
+|-----------------|---------------------------------------------------------------------------------------------------------------------------|
+| <b>TP Id</b>    | TP/LP-PAN/PHG/PHDTW/PLX/BV-064                                                                                            |
+| <b>TP label</b> | Whitepaper. Device and Sensor Status Enumeration Object (Continuous Measurements) – Enum-Observed-Value-Bit-Str Attribute |
+
+|                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |  |  |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|--|
+| <b>Coverage</b>          | <b>Spec</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | [Bluetooth PHDT v1.6] |  |  |
+|                          | <b>Testable items</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | DSS Enumeration 8; M  |  |  |
+| <b>Test purpose</b>      | <p>Check that:</p> <p>PHG transcodes Device and Sensor Status field of the PLX Continuous Measurement characteristic into Device and Sensor Status Enumeration Object - Enum-Observed-Value-Basic-Bit-Str attribute</p> <p>[AND]</p> <p>PHG transcodes the Bluetooth Device and Sensor Status field of the PLX Continuous characteristic to 11073 Enum-Observed-Value-Basic-Bit-Str attribute properly</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |                       |  |  |
+| <b>Applicability</b>     | C_MAN_BLE_000 AND C_MAN_BLE_002 AND C_MAN_BLE_040 AND C_MAN_BLE_041                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |                       |  |  |
+| <b>Other PICS</b>        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                       |  |  |
+| <b>Initial condition</b> | The PHG under test and the simulated PHD are in the Standby state.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                       |  |  |
+| <b>Test procedure</b>    | <ol style="list-style-type: none"> <li>1. The simulated PHD is configured with a Pulse Oximeter Profile (device specialization), it has a continuous measurement (including fast and slow response measurement values) ready to be sent and it is in the Advertising state (it is discoverable).</li> <li>2. The simulated PHD implements several BTLE characteristics. The characteristics of interest for this Test Case are: <ol style="list-style-type: none"> <li>a. PLX Continuous Measurement (0x2A5F)</li> <li>b. PLX Features (0x2A60) <ol style="list-style-type: none"> <li>i. Field: Supported Features <ul style="list-style-type: none"> <li>• Format: 16 bit</li> <li>• Value: 0000 0000 0011 0010 (MSB → LSB). Device and Sensor Status support is present (bit 1). Fast and slow response modes are supported (bits 4 and 5).</li> </ul> </li> <li>ii. Field: Measurement Status Support <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>iii. Field: Device and Sensor Status Support <ul style="list-style-type: none"> <li>• Format: 24 bit</li> <li>• Value: 0000 0000 1111 1111 1111 1111 (MSB → LSB). All Device and Sensor Status bits are supported</li> </ul> </li> </ol> </li> </ol> </li> <li>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).</li> <li>4. When the pairing has been completed (Connection state), force the PHG under test to read the PLX Features characteristic.</li> <li>5. The simulated PHD sends the Measurement to the PHG under test with the following value: <ol style="list-style-type: none"> <li>a. PLX Continuous Measurement (0x2A5F) <ol style="list-style-type: none"> <li>i. Field: Flags <ul style="list-style-type: none"> <li>• Format: 8 bit</li> <li>• Value: 0000 1011 (MSB → LSB). Device and Sensor Status, SpO2PR-Fast and SpO2PR-Slow fields are present. Measurement Status and Pulse Amplitude Index fields are not present.</li> </ul> </li> <li>ii. Field: SpO2PR-Normal - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>iii. Field: SpO2PR-Normal - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> </ul> </li> </ol> </li> </ol> </li> </ol> |                       |  |  |
+
+|  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  | <ul style="list-style-type: none"> <li>• Value: Not Relevant</li> </ul> <ol style="list-style-type: none"> <li>iv. Field: SpO2PR-Fast - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>v. Field: SpO2PR-Fast - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vi. Field: SpO2PR-Slow - SpO2 (%) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>vii. Field: SpO2PR-Slow - PR (bpm) <ul style="list-style-type: none"> <li>• Format: SFLOAT</li> <li>• Value: Not Relevant</li> </ul> </li> <li>viii. Field: Measurement Status <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> <li>ix. Field: Device and Sensor Status <ul style="list-style-type: none"> <li>• Format: 24 bit</li> <li>• Value: 0000 0000 0000 0000 0000 0001 (MSB → LSB). Extended Display Update Ongoing (bit 0).</li> </ul> </li> <li>x. Field: Pulse Amplitude Index (%) <ul style="list-style-type: none"> <li>• This field is not included</li> </ul> </li> </ol>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|  | <ol style="list-style-type: none"> <li>6. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute.</li> <li>7. The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0000 0000 0010 (MSB → LSB). Equipment Malfunction (bit 1). All remaining fields remain equal to those in step 5.</li> <li>8. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute.</li> <li>9. The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0000 0000 0100 (MSB → LSB). Signal Processing Irregularity Detected (bit 2). All remaining fields remain equal to those in step 5.</li> <li>10. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute.</li> <li>11. The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0000 0000 1000 (MSB → LSB). Inadequate Signal Detected (bit 3). All remaining fields remain equal to those in step 5.</li> <li>12. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute.</li> <li>13. The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0000 0001 0000 (MSB → LSB). Poor Signal Detected (bit 4). All remaining fields remain equal to those in step 5.</li> <li>14. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute.</li> <li>15. The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0000 0010 0000 (MSB → LSB). Low Perfusion Detected (bit 5). All remaining fields remain equal to those in step 5.</li> <li>16. Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute.</li> <li>17. The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0000 0100 0000 (MSB → LSB). Erratic Signal</li> </ol> |
+
+|                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                           | <p>Detected (bit 6). All remaining fields remain equal to those in step 5.</p> <ol style="list-style-type: none"> <li>Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute.</li> <li>The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0000 1000 0000 (MSB → LSB). Non-Pulsatile Signal Detected (bit 7). All remaining fields remain equal to those in step 5.</li> <li>Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute.</li> <li>The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0001 0000 0000 (MSB → LSB). Questionable Signal Detected (bit 8). All remaining fields remain equal to those in step 5.</li> <li>Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute.</li> <li>The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0010 0000 0000 (MSB → LSB). Signal Analysis Ongoing (bit 9). All remaining fields remain equal to those in step 5.</li> <li>Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute.</li> <li>The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 0100 0000 0000 (MSB → LSB). Sensor Interference Detected (bit 10). All remaining fields remain equal to those in step 5.</li> <li>Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute.</li> <li>The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0000 1000 0000 0000 (MSB → LSB). Sensor Unconnected to User (bit 11). All remaining fields remain equal to those in step 5.</li> <li>Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute.</li> <li>The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0001 0000 0000 0000 (MSB → LSB). Unknown Sensor Connected (bit 12). All remaining fields remain equal to those in step 5.</li> <li>Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute.</li> <li>The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0010 0000 0000 0000 (MSB → LSB). Sensor Displaced (bit 13). All remaining fields remain equal to those in step 5.</li> <li>Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute.</li> <li>The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 0100 0000 0000 0000 (MSB → LSB). Sensor Malfunctioning (bit 14). All remaining fields remain equal to those in step 5.</li> <li>Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute.</li> <li>The simulated PHD sends a Measurement to the PHG under test with Measurement Status field set to 0000 0000 1000 0000 0000 0000 (MSB → LSB). Sensor Disconnected (bit 15). All remaining fields remain equal to those in step 5.</li> <li>Check in the PHG transcoder output the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute.</li> </ol> |
+| <b>Pass/Fail criteria</b> | <p>In Step 6, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “device-extended-update” (0x8000).</p> <p>In Step 8, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “device-equipment-malfunction” (0x4000).</p> <p>In Step 10, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “signal-processing-irregularity” (0x2000).</p> <p>In Step 12, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “signal-inadequate” (0x1000).</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+**Rec. ITU-T H.850.6 (08/2020)**     149
+
+|                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                                    | <p>In Step 14, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “signal-poor” (0x0800).</p> <p>In Step 16, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “signal-low-perfusion” (0x0400).</p> <p>In Step 18, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “signal-erratic” (0x0200).</p> <p>In Step 20, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “signal-non-pulsatile” (0x0100).</p> <p>In Step 22, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “signal-pulse-questionable” (0x0080).</p> <p>In Step 24, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “signal-searching” (0x0040).</p> <p>In Step 26, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “signal-interference” (0x0020).</p> <p>In Step 28, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “sensor-off” (0x0010).</p> <p>In Step 30, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “sensor-unsupported” (0x0008).</p> <p>In Step 32, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “sensor-displaced” (0x0004).</p> <p>In Step 34, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “sensor-malfunction” (0x0002).</p> <p>In Step 36, the Device and Sensor Status Enumeration Object – Enum-Observed-Value-Basic-Bit-Str attribute is present and it is set to “sensor-disconnected” (0x0001).</p> |
+| <p><b>Notes<br/>(To assist manual testing)</b></p> | <p>In step 6, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Enum-Observed-Value-Basic-Bit-Str attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Device and Sensor Status Enumeration Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR (2662)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>80 00</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Enum-Observed-Value-Basic-Bit-Str attribute value (check OBX-5):</p> <p>OBX n CWE 150604^MDC_PULS_OXIM_DEV_STATUS^MDC m.0.0.x 1^<b>device-extended-update(15)</b>     R</p> <p>In step 8, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p> <p>Enum-Observed-Value-Basic-Bit-Str attribute is present:</p> <ul style="list-style-type: none"> <li><input type="checkbox"/> Object: Device and Sensor Status Enumeration Object</li> <li><input type="checkbox"/> Attribute-id: MDC_ATTR_ENUM_OBS_VAL_BASIC_BIT_STR (2662)</li> <li><input type="checkbox"/> Attribute-type: BITS16</li> <li><input type="checkbox"/> Attribute-value: <b>40 00</b> (hex)</li> </ul> <p>b) WAN PCD-01 message</p> <p>PCD-01 message includes a segment like this with Enum-Observed-Value-Basic-Bit-Str attribute value (check OBX-5):</p> <p>OBX n CWE 150604^MDC_PULS_OXIM_DEV_STATUS^MDC m.0.0.x 1^<b>device-equipment-malfunction(14)</b>     R</p> <p>In step 10, possible values in typical points of observation after transcoder output are:</p> <p>a) IEEE 11073 Objects and Attributes</p>                                                                                                                                                                                                                                                                                                                  |
+
+Enum-Observed-Value-Basic-Bit-Str attribute is present:
+
+- Object: Device and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **20 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):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**signal-processing-irregularity(13)**|||||R
+
+In step 12, 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **10 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):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**signal-inadequate(12)**|||||R
+
+In step 14, 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **08 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):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**signal-poor(11)**|||||R
+
+In step 16, 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **04 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):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**signal-low-perfusion(10)**|||||R
+
+In step 18, 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **02 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):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**signal-erratic(9)**|||||R
+
+In step 20, 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **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):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**signal-non-pulsatile(8)**|||||R
+
+In step 22, 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **00 80** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-5):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**signal-pulse-questionable(7)**|||||R
+
+In step 24, 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **00 40** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-5):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**signal-searching(6)**|||||R
+
+In step 26, 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **00 20** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-5):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**sensor-interference(5)**|||||R
+
+In step 28, 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **00 10** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-5):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**sensor-off(4)**|||||R
+
+In step 30, 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **00 08** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-5):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**sensor-unsupported(3)**|||||R
+
+In step 32, 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 and Sensor Status Enumeration Object
+- Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- Attribute-type: BITS16
+- Attribute-value: **00 04** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-5):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**sensor-**
+
+**displaced(2)** R
+
+In step 34, 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 and Sensor Status Enumeration Object
+- ❏ Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- ❏ Attribute-type: BITS16
+- ❏ Attribute-value: **00 02** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-5):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**sensor-malfunction(1)** R
+
+In step 36, 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 and Sensor Status Enumeration Object
+- ❏ Attribute-id: MDC\_ATTR\_ENUM\_OBS\_VAL\_BASIC\_BIT\_STR (2662)
+- ❏ Attribute-type: BITS16
+- ❏ Attribute-value: **00 01** (hex)
+
+#### b) WAN PCD-01 message
+
+PCD-01 message includes a segment like this with Measurement-Status attribute value (check OBX-5):
+
+OBX|n|CWE|150604^MDC\_PULS\_OXIM\_DEV\_STATUS^MDC|m.0.0.x|1^**sensor-disconnected(0)** R
+
+## 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), *ETSI drafting rules*.  
+<https://docbox.etsi.org/MTS/MTS/10-PromotionalMaterial/MBS-20111118/Referenced%20Documents/Drafting%20Rules.pdf>
+- [b-PHD PICS & PIXIT] PHD PICS and PIXIT Test Tool v8.0.0.0 – Excel sheet v1.13.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-PHG PICS & PIXIT] PHG PICS and PIXIT Test Tool v8.0.0.0 – Excel sheet v1.11.  
+<http://handle.itu.int/11.1002/2000/12067>
+- [b-TI] PHD Testable items. Test Tool v8.0.0.0 – Excel sheet v1.10.  
+<http://handle.itu.int/11.1002/2000/12067>
+
+
+
+
+
+## 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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/H/T-REC-H.850.7-202008-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f7bff38b7385414ca4a0881968c632999aaf39a4
--- /dev/null
+++ b/marked/H/T-REC-H.850.7-202008-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e3764245105340b18a282f1a20aa319e8fbbed80c67d35aa8a8fa852c12491af
+size 4150
diff --git a/marked/H/T-REC-H.860-201404-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.860-201404-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bba8d77f37ceba9a23509057f71199f5b8081dbc
--- /dev/null
+++ b/marked/H/T-REC-H.860-201404-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.860-201404-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg b/marked/H/T-REC-H.860-201404-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..441a2813a0a2c0679f1ed9b04b64b7147e195a4c
--- /dev/null
+++ b/marked/H/T-REC-H.860-201404-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7303c15d1fd930cbfa168e2d2d836864ddda2128c3bfca8ed25ffccac1dd9b7d
+size 269890
diff --git a/marked/H/T-REC-H.860-201404-I_PDF-E/284768c5ee1a05aa1b9ce396f606a040_img.jpg b/marked/H/T-REC-H.860-201404-I_PDF-E/284768c5ee1a05aa1b9ce396f606a040_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ead9a45b1d7c2e0a4b025f0413cf30a605e00e6b
--- /dev/null
+++ b/marked/H/T-REC-H.860-201404-I_PDF-E/284768c5ee1a05aa1b9ce396f606a040_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e20f8ca08bd47443616c30aeb9c1dcebe16c003ffae11424e69d0c5f9250646c
+size 63271
diff --git a/marked/H/T-REC-H.860-201404-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/H/T-REC-H.860-201404-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..54402f58a66ed1888935310bcbc7a283bc66d792
--- /dev/null
+++ b/marked/H/T-REC-H.860-201404-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c32cfc16be2c2540fd97246db89c18b2aaeedde640fc83dc618cf32e1a860786
+size 199249
diff --git a/marked/H/T-REC-H.860-201404-I_PDF-E/4ff00a489baaa34a0c01070de1d613db_img.jpg b/marked/H/T-REC-H.860-201404-I_PDF-E/4ff00a489baaa34a0c01070de1d613db_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5c8a05020a4d777f21d9efbba6f73969f6c99965
--- /dev/null
+++ b/marked/H/T-REC-H.860-201404-I_PDF-E/4ff00a489baaa34a0c01070de1d613db_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:327dc8c5805e92af867b887c8551fe0dc62b2f8735158933d097a6f64e720aeb
+size 100823
diff --git a/marked/H/T-REC-H.860-201404-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg b/marked/H/T-REC-H.860-201404-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a8ba395ba34fca4533c022b83eff2b362e380e1c
--- /dev/null
+++ b/marked/H/T-REC-H.860-201404-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:adabddf07a38e654bba62a3216240d86dfe1b17232aff43bf12288aed2698d6b
+size 92470
diff --git a/marked/H/T-REC-H.860-201404-I_PDF-E/802707b774f2d2973b49cea2020e8453_img.jpg b/marked/H/T-REC-H.860-201404-I_PDF-E/802707b774f2d2973b49cea2020e8453_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6b28ad3401802d257c1e87d1d1d8d3bb5f7724ba
--- /dev/null
+++ b/marked/H/T-REC-H.860-201404-I_PDF-E/802707b774f2d2973b49cea2020e8453_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eaa8ed3f935987b32b00282ffd97d9eeeb0ab48f796aed83c68aef7787107efa
+size 96617
diff --git a/marked/H/T-REC-H.860-201404-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg b/marked/H/T-REC-H.860-201404-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c7f963d2e3e2265181c7e6918110e09e7c245ffc
--- /dev/null
+++ b/marked/H/T-REC-H.860-201404-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1cf8a162ae0366fb89bc8a0ba105d034e4cacb81345ffd0e15d2c3f19c1aeb5e
+size 199777
diff --git a/marked/H/T-REC-H.860-201404-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/H/T-REC-H.860-201404-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9914b172821c310b1e53662d7d7e0fb42dfe9f7f
--- /dev/null
+++ b/marked/H/T-REC-H.860-201404-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b675464b1cf9ce6c2b484e40fe2784936dd162fc07e119c2c5bd29725daa1639
+size 84499
diff --git a/marked/H/T-REC-H.860-201404-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg b/marked/H/T-REC-H.860-201404-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5e343606c7a507801e7beffcbefec5b791c22ff5
--- /dev/null
+++ b/marked/H/T-REC-H.860-201404-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1b07abc7b236bbf302baeb624318121f3a9e373182e1c82a96ebd40f6ef52c83
+size 199616
diff --git a/marked/H/T-REC-H.860-201404-I_PDF-E/db5deafdae53dbc7d5972957f708c691_img.jpg b/marked/H/T-REC-H.860-201404-I_PDF-E/db5deafdae53dbc7d5972957f708c691_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..004e5cd57a6522df1288ba832dd941d01b13552b
--- /dev/null
+++ b/marked/H/T-REC-H.860-201404-I_PDF-E/db5deafdae53dbc7d5972957f708c691_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f9fb7525c8c9a5502ca68cd3bdb54a5f0e919458b1ea9bacd555348064f7683a
+size 68441
diff --git a/marked/H/T-REC-H.860-201404-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg b/marked/H/T-REC-H.860-201404-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a0c78d304a66561a473cd871d5965a9462377c7b
--- /dev/null
+++ b/marked/H/T-REC-H.860-201404-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c01499fdb16bd8de6763f9514621bcf30c4e0094ff692081d11e6459c4f22146
+size 173020
diff --git a/marked/H/T-REC-H.860-201404-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/H/T-REC-H.860-201404-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..74b5e11de57d8b15394a2899c9f379fad36df7b2
--- /dev/null
+++ b/marked/H/T-REC-H.860-201404-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5491381c9b6ffa2039f918fc6ddd30541291582fbd2a7cb01781c8da7808176a
+size 66152
diff --git a/marked/H/T-REC-H.860-201404-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/H/T-REC-H.860-201404-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ce8b18ece5004cb13cc7869a62f04b3dcae48b8a
--- /dev/null
+++ b/marked/H/T-REC-H.860-201404-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4414580c24c8cf2205158523f7e97177f4b40f969680d465a3dfc76c75739b6e
+size 123872
diff --git a/marked/H/T-REC-H.861.1-201803-I_PDF-E/0b8b087a7baa471015d3ffeaa43d9a6c_img.jpg b/marked/H/T-REC-H.861.1-201803-I_PDF-E/0b8b087a7baa471015d3ffeaa43d9a6c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a496770656efc593b03146ad5591b926a5c9a530
--- /dev/null
+++ b/marked/H/T-REC-H.861.1-201803-I_PDF-E/0b8b087a7baa471015d3ffeaa43d9a6c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:31dc8d55304f72512c320d6a8b4b059d1a7da0d056f03065f3d8718e57fe4b84
+size 30201
diff --git a/marked/H/T-REC-H.861.1-201803-I_PDF-E/1145fc59efdc7dacc8d3c715d7ff3248_img.jpg b/marked/H/T-REC-H.861.1-201803-I_PDF-E/1145fc59efdc7dacc8d3c715d7ff3248_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..da607bce00fa77e2fb74ca4157e74dce7bb7b43b
--- /dev/null
+++ b/marked/H/T-REC-H.861.1-201803-I_PDF-E/1145fc59efdc7dacc8d3c715d7ff3248_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5c531fc8c5171464050000957591718d3db96f42b79b28ac5dd464122dc14574
+size 23670
diff --git a/marked/H/T-REC-H.861.1-201803-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/H/T-REC-H.861.1-201803-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..61904c12b802df120c05ae72cd89a3ef2690dd5b
--- /dev/null
+++ b/marked/H/T-REC-H.861.1-201803-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_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.861.1-201803-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/H/T-REC-H.861.1-201803-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..595b49f49e6ee35a73e1ada9e56aec09eea285da
--- /dev/null
+++ b/marked/H/T-REC-H.861.1-201803-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f027155531e0f8e4a30e99fbc7c3c9ae9cdaa8fc20075f0d130d401ce6c6338f
+size 82104
diff --git a/marked/H/T-REC-H.861.1-201803-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg b/marked/H/T-REC-H.861.1-201803-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ef7aeff52d6a3f0461c20d5b52673f10357aa6e5
--- /dev/null
+++ b/marked/H/T-REC-H.861.1-201803-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:37d64ae529076aa357cdb712925fb12009257b823543619f75055c8b8d1d88e5
+size 12217
diff --git a/marked/H/T-REC-H.861.1-201803-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/H/T-REC-H.861.1-201803-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..871497ec4b2e594fb9c30c9b26d17aadabb2c1bd
--- /dev/null
+++ b/marked/H/T-REC-H.861.1-201803-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:228957f187d46064991b4fd254897932a08c4f42b4835cb1cd42b4ff0f56aab1
+size 66024
diff --git a/marked/H/T-REC-H.861.1-201803-I_PDF-E/a430996a9e8993deb0c6b25da234744b_img.jpg b/marked/H/T-REC-H.861.1-201803-I_PDF-E/a430996a9e8993deb0c6b25da234744b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cadfb94f489c17709d66e43a84971c3b85675d97
--- /dev/null
+++ b/marked/H/T-REC-H.861.1-201803-I_PDF-E/a430996a9e8993deb0c6b25da234744b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf4b2e39cabf3b305887e7b261740de5bd25ae84e2db95cfcb121d37ea979361
+size 30002
diff --git a/marked/H/T-REC-H.861.1-201803-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/H/T-REC-H.861.1-201803-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b1547b050445989f57ea6dfb2d794fcaa2a408dd
--- /dev/null
+++ b/marked/H/T-REC-H.861.1-201803-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:59cf8c809dd5754609ebecbd0c3c58257c297feb5efb84e0ffbcaeef833f734d
+size 86251
diff --git a/marked/H/T-REC-H.861.1-201803-I_PDF-E/eb22a8740f7c6a0f6ee98f16d99ed8b9_img.jpg b/marked/H/T-REC-H.861.1-201803-I_PDF-E/eb22a8740f7c6a0f6ee98f16d99ed8b9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..68c0520830302c9a1aa10b57b4bd78794a0535e2
--- /dev/null
+++ b/marked/H/T-REC-H.861.1-201803-I_PDF-E/eb22a8740f7c6a0f6ee98f16d99ed8b9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ba356e97ad21f45a08014357ca4cb49939aca88c858cfa67b138720b09323f10
+size 24662
diff --git a/marked/H/T-REC-H.862.4-202106-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/H/T-REC-H.862.4-202106-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ad639f90cd50b1c187629c7318a79ae29a339bed
--- /dev/null
+++ b/marked/H/T-REC-H.862.4-202106-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d124834722beb8c3b159a69c726a230e44edc9177e0b48a947d19617850fca01
+size 15313
diff --git a/marked/H/T-REC-H.862.4-202106-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/H/T-REC-H.862.4-202106-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7fc0ce00090f66b87404c12debf099b47a838ec0
--- /dev/null
+++ b/marked/H/T-REC-H.862.4-202106-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_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.862.4-202106-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/H/T-REC-H.862.4-202106-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..73a76543c7b1ca95cd8b6568faf59ab3ab2a9be8
--- /dev/null
+++ b/marked/H/T-REC-H.862.4-202106-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f86cf916fc93ceb12b4ce494b1a147d39020947dc799a95b69873a5a00b5e91c
+size 21313
diff --git a/marked/H/T-REC-H.862.4-202106-I_PDF-E/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg b/marked/H/T-REC-H.862.4-202106-I_PDF-E/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..858b26719a3969e0e985253891b6f44afd8bde39
--- /dev/null
+++ b/marked/H/T-REC-H.862.4-202106-I_PDF-E/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b68bbc81615fc91f6343ec41f81950ba8e3957bfe311b5a9d0dedf9affef3b4
+size 19184
diff --git a/marked/H/T-REC-H.862.4-202106-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/H/T-REC-H.862.4-202106-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0c19df486e0e2df2451e1488e8e7eab7ff205e5f
--- /dev/null
+++ b/marked/H/T-REC-H.862.4-202106-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a391ee31823f63eb810f84fe2f2e4839959de2053a0fdf0e4a109c7c8d8d786c
+size 19068
diff --git a/marked/H/T-REC-H.862.4-202106-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/H/T-REC-H.862.4-202106-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7620c378508a7b16866b489f4d145d016cf693f6
--- /dev/null
+++ b/marked/H/T-REC-H.862.4-202106-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:adb79a007f107d56a52598a34b018746d0db8fee7e4361b93bf53238e6b956eb
+size 102785
diff --git a/marked/H/T-REC-H.862.6-202309-I_PDF-E/raw.md b/marked/H/T-REC-H.862.6-202309-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..1bb10c5144cd6b2b0fce1a4b1df8a8e030c8ed4e
--- /dev/null
+++ b/marked/H/T-REC-H.862.6-202309-I_PDF-E/raw.md
@@ -0,0 +1,402 @@
+
+
+# Recommendation**ITU-T H.862.6 (09/2023)**
+
+SERIES H: Audiovisual and multimedia systems
+
+E-health multimedia systems, services and applications –  
+Multimedia e-health data exchange services
+
+---
+
+# **Functional requirements for counselling services based on artificial emotional intelligence**
+
+![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        |
+| 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        |
+| <b>Multimedia e-health data exchange services</b>                                           | <b>H.860-H.869</b> |
+| Safe listening                                                                              | H.870-H.879        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T H.862.6
+
+# Functional requirements for counselling services based on artificial emotional intelligence
+
+## Summary
+
+Recommendation ITU-T H.862.6 proposes service requirements and functional specifications for counselling services based on artificial emotional intelligence (AEI) technologies. This Recommendation proposes a service model for counselling services using several scenarios. At a time when artificial intelligence (AI) technologies are being widely proposed and used, the relevant standards can be an important opportunity to facilitate the development of the technology in the industry.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T H.862.6  | 2023-09-13 | 16          | 11.1002/1000/15635 |
+
+## Keywords
+
+Artificial emotional intelligence, counselling services, functional requirements.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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.....            | 1    |
+| 4 Abbreviations and acronyms .....                       | 1    |
+| 5 Conventions .....                                      | 2    |
+| 6 Background.....                                        | 2    |
+| 7 Services using artificial emotional intelligence ..... | 3    |
+| 7.1 Counselling services .....                           | 3    |
+| 7.2 Education services .....                             | 3    |
+| 7.3 Customer support services.....                       | 3    |
+| 7.4 Mobility services .....                              | 4    |
+| 7.5 Robot services .....                                 | 4    |
+| 8 Functional requirements .....                          | 4    |
+| 8.1 Basic requirements .....                             | 4    |
+| 8.2 Service requirements .....                           | 5    |
+| 9 Functional model for counselling services .....        | 6    |
+| 9.1 User interface.....                                  | 6    |
+| 9.2 Input analyser module .....                          | 6    |
+| 9.3 Short term memory module.....                        | 7    |
+| 9.4 Interaction analyser module .....                    | 7    |
+| 9.5 Knowledge base.....                                  | 7    |
+| 9.6 Conditional logic module .....                       | 7    |
+| 9.7 Behaviour module .....                               | 7    |
+| 9.8 Management interface .....                           | 7    |
+| 9.9 Real-world data (RWD) repository .....               | 7    |
+| 9.10 Real-world evidence (RWE) repository .....          | 8    |
+| Bibliography.....                                        | 9    |
+
+
+
+# Recommendation ITU-T H.862.6
+
+## Functional requirements for counselling services based on artificial emotional intelligence
+
+## 1 Scope
+
+This Recommendation introduces a concept of counselling services based on artificial emotional intelligence, and analyses its common characteristics. This Recommendation also identifies high-level requirements, and presents functional specifications of the services.
+
+The scope of this Recommendation includes:
+
+- Service requirements and future use cases regarding future service needs
+- Functional specifications
+- Identification of technology challenges.
+
+## 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 term 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.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 emotion enabled multimodal user interface:** A multimodal user interface (UI) based on emotion analysis with some properties and illustrations and data.
+
+NOTE – Definition adapted from [b-ITU-T H.862.5].
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+AEI Artificial Emotional Intelligence
+
+CBT Cognitive Behavioural Therapy
+
+IoT Internet of Things
+
+OTT Over-The-Top
+
+|     |                     |
+|-----|---------------------|
+| RWD | Real-World Data     |
+| RWE | Real-World Evidence |
+| UI  | User Interface      |
+
+## 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 Background
+
+Emotion recognition technology has been carried out through facial recognition, speech recognition, gesture recognition and biometrics based on core technologies of artificial intelligence (AI) such as deep learning, neural networks and big data.
+
+Artificial emotional intelligence (AEI) is a technology that combines emotion recognition, emotion generation and emotion augmentation technologies with AI. The challenges for these technologies can be identified as shown in Table 1.
+
+**Table 1 – Technology challenges for AEI**
+
+| Emotion technologies    | Challenges for AEI                                                                                                       | Examples                        |
+|-------------------------|--------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Recognition technology  | It can recognize human emotions through facial expressions, voices, texts, gestures, etc.                                | Multi modal emotion recognition |
+| Generation technology   | It can express emotion through avatar's facial expression, voice, text, gesture, etc. through AI.                        | Lip animation                   |
+| Augmentation technology | It can strengthen the user's emotions through conversations, multimedia contents, Internet of things (IoT) devices, etc. | Haptic devices                  |
+
+The conceptual diagram of a counselling service using AEI is shown in Figure 1.
+
+This Recommendation proposes requirements for counselling services using artificial emotional intelligence technology.
+
+![Conceptual diagram of a counselling service using AEI. The diagram shows five input modalities on the left: Facial expression (represented by an icon), Acoustic features of voice (represented by a waveform), Gesture (represented by four human figures), Dialogue (represented by a speech bubble with 'T e x t'), and Emotion (represented by a vertical stack of seven facial icons). All five inputs point to a central 'Machine learning' node, which is a simple neural network diagram. From this node, an arrow points to the text 'Counselling service based on emotional intent'. A reference code 'H.862.6(23)' is located near the bottom right of the diagram.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg)
+
+Conceptual diagram of a counselling service using AEI. The diagram shows five input modalities on the left: Facial expression (represented by an icon), Acoustic features of voice (represented by a waveform), Gesture (represented by four human figures), Dialogue (represented by a speech bubble with 'T e x t'), and Emotion (represented by a vertical stack of seven facial icons). All five inputs point to a central 'Machine learning' node, which is a simple neural network diagram. From this node, an arrow points to the text 'Counselling service based on emotional intent'. A reference code 'H.862.6(23)' is located near the bottom right of the diagram.
+
+**Figure 1 – Conceptual diagram of a counselling service using AEI**
+
+## 7 Services using artificial emotional intelligence
+
+### 7.1 Counselling services
+
+Artificial emotional intelligence is used in counselling services to recognize various human emotions and sensitivity through biometric information, facial expressions, actions, and voices. By learning the information through an AI algorithm, a personalized emotional ability improvement solution can be presented. It provides advice on appropriate behaviour to users in situations such as interviews through comprehensive analysis of human faces, voices, and gestures. By analysing subtle patterns such as speed and size of voice when talking on the phone, it predicts and informs extreme changes in bipolar mood. It contributes to promoting mutual communication, improving relationships, and restoring relationships by identifying the emotional relationship characteristics of interactions (conversation patterns, language use, etc.) with people around, such as family and friends. When difficult and exhausting emotions are identified from various personal data such as voice, language expression or facial expression, emotional activities such as movies, music or games are recommended to alleviate them. By applying AI technology, it helps to improve emotional and psychological stability and emotional ability by grasping the emotional state through biometric information, facial expressions, images or voice.
+
+### 7.2 Education services
+
+Emotional synthesis technology has been developed for education services based on deep learning that can express various emotions that can control not only emotions such as sadness and happiness, but also the intensity of emotions, such as "a little sad" or "very sad". By applying cross-language learning technology through foreign language AI learning, mutual learning in the other person's mother tongue is possible. Based on the know-how of college entrance exam experts and AI-based emotional recognition technology, it analyses videos to provide feedback on eye contact, facial expressions and likability, and comprehensively provides cover letters and interview consulting to students. Personalized education for learners can be provided through machine learning-based user emotion recognition technology.
+
+### 7.3 Customer support services
+
+For customer support services an over-the-top (OTT) service is a content recommendation service based on emotional analysis that recommends video content by analysing emotions with facial
+
+expressions. It recommends content that suits the user's mood such as joy, sadness or anger, after reading the user's facial expression on the "Scanner search for reading my emotions" option.
+
+### 7.4 Mobility services
+
+In mobility services the core of emotional driving is to provide drivers with optimized interior environment elements such as music, temperature, lighting, vibration, and scent to suit the driver's condition after the vehicle has learnt biometric and current emotional state information based on AI.
+
+### 7.5 Robot services
+
+The intelligent emotional robot industry, which better understands human emotions through emotional analysis, is expected to have growth potential throughout the entertainment, sales, criminal investigation and social activities sectors.
+
+## 8 Functional requirements
+
+### 8.1 Basic requirements
+
+In an emotion-based counselling service, it is important to understand the user's emotion and intention and to sympathize with the conversation.
+
+#### 8.1.1 Emotion recognition
+
+- An emotion-based counselling service is required to include a method for recognizing one or more emotions in order to understand the user's emotional state. For emotion recognition, emotion expression is sensed based on a single or multiple sensors and recognized through a computer program.
+
+NOTE – Human emotions are expressed in various forms such as conversation content, voice, facial expression, gesture, and bio-signals. In addition, these emotions have characteristics of each human being, and it is possible to predict the intention of the conversation partner according to the emotions by gathering these emotional expressions.
+
+- Emotion recognition may be used in counselling services using single or multiple sensors.
+
+Table 2 shows the elements in which emotions are expressed and how to recognize them in general.
+
+**Table 2 – Elements for emotional expressions**
+
+| <b>Data</b>  | <b>Sensor</b> | <b>Method</b>                                                                                                                                     |
+|--------------|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
+| Expression   | Camera        | Recognition of emotional changes by detecting key points on the face                                                                              |
+| Conversation | Speaker       | Conversation text is classified according to emotional change with a document classifier                                                          |
+| Voice        | Speaker       | Recognition of emotional changes based on phonetic characteristics                                                                                |
+| Gesture      | Camera        | Recognition of movement changes expressed according to emotions through the camera                                                                |
+| Biosignal    | Bio-sensor    | Emotion recognition through the electrical signals of the living body that change according to emotions, such as electromyography and brain waves |
+
+#### 8.1.2 Distinguish false emotions
+
+The important thing in a counselling service is to be able to identify exact emotions. In the emotional expression criteria, the recognition of emotional expression depends on the accuracy of the recognizer. False emotion is a case in which conversation content and facial expression are
+
+shown with opposite emotions. In this case, it may be necessary to distinguish between the actual user's emotion and the expressed emotion.
+
+#### **8.1.3 Empathy for users**
+
+- Counselling services are required to be able to empathize with the emotions of others through emotional communication with users.
+
+#### **8.1.4 Understanding intentions based on emotions**
+
+- Intentions appearing in conversations or actions are recommended to be interpreted differently depending on the state of emotion. In order to distinguish between them, it may be necessary to understand the intention according to the emotion.
+
+#### **8.1.5 Monitoring data**
+
+Monitoring data refers to data generated during the interaction between the service bot and the user in the counselling service.
+
+- Preservation of previous state with users  
+Preservation of data from previous interactions with users may provide a way to remember and respond to users. In addition, it may be a basic data for analysing users for effective counselling.
+- Analysis of user data  
+Analysis of data with users may be the basis for effective counselling. Through the analysed data, it is possible to have a conversation tailored to the user's situation.
+
+#### **8.1.6 User avatar**
+
+In a counselling service, there may be cases where the user does not want his or her appearance to be exposed other than that the user's actual appearance is shown to the other party or himself. In this case, an avatar in which the user's emotion, mouth shape, and gesture are synchronized may be used.
+
+### **8.2 Service requirements**
+
+In this clause the requirements for a counselling service using emotion recognition technology are specified.
+
+#### **8.2.1 Tracking continuous emotional changes**
+
+Tracking not only emotional changes at a single point in time but also long-term emotional changes may provide important predictive data for the user's accurate emotional changes and behavioural changes. Consequently it may be necessary to track continuous changes.
+
+- Emotional change at a specific point in time: A single point in time change is recommended to include a recognition error. It is difficult to track the user's daily emotions and changes.
+- Changes over short periods: Integrating emotional changes in a short period rather than emotional recognition at a specific point in time may estimate changes more accurately.
+- Long-term emotional change: Through continuous tracking, additional information such as user propensity may be estimated.
+
+#### **8.2.2 Sentiment management**
+
+In order to provide customized services to users, it is recommended to record and manage users' emotions.
+
+#### 8.2.3 User interaction
+
+– In order to increase the level of satisfaction with the service, the service is required to be provided according to the user's emotion.
+
+Feedback from the service can trigger new user behaviour. This series of actions is called interaction with the user.
+
+## 9 Functional model for counselling services
+
+The functional model for the counselling service is composed of functions for receiving user input through the user interface as shown in Figure 2, and for conversation and interaction with the user. In addition, a part for collecting and managing actual use data for utilizing user data can be added.
+
+![Figure 2 – Functional model. A block diagram showing the functional architecture of a counselling service. It consists of two main vertical columns. The left column represents the management and data layer, containing 'Management interface', 'Feedback', 'Service gateway' (with 'Standards' and 'Security'), and two repositories: 'RWE repository' and 'RWD repository'. Arrows show flow between these components. The right column represents the user interaction and processing layer, starting with 'User interface (Voice, text, facial, gesture, etc.)' at the top. Below it is the 'Input analyser' (Value, Text, Media), 'Short term memory' (Current status, Current Env., Interaction log), 'Analyser' (Interaction analyser, Personalized analyser), 'Knowledge base' (Stable, Logical, Learned, Various AI models, Personalized knowledge), 'Conditional logic' (Knowledge provider, Interaction policy), and 'Behaviour unit'. Arrows show a top-down flow from the user interface through the analyser and memory to the knowledge base and logic, with a feedback loop from the behaviour unit back to the user interface. A large arrow points from the 'Service gateway' in the left column to the 'User interface' in the right column. A small label 'H.862.6(23)' is in the bottom right corner.](7f17c430b9598e4d748a8041457810b3_img.jpg)
+
+Figure 2 – Functional model. A block diagram showing the functional architecture of a counselling service. It consists of two main vertical columns. The left column represents the management and data layer, containing 'Management interface', 'Feedback', 'Service gateway' (with 'Standards' and 'Security'), and two repositories: 'RWE repository' and 'RWD repository'. Arrows show flow between these components. The right column represents the user interaction and processing layer, starting with 'User interface (Voice, text, facial, gesture, etc.)' at the top. Below it is the 'Input analyser' (Value, Text, Media), 'Short term memory' (Current status, Current Env., Interaction log), 'Analyser' (Interaction analyser, Personalized analyser), 'Knowledge base' (Stable, Logical, Learned, Various AI models, Personalized knowledge), 'Conditional logic' (Knowledge provider, Interaction policy), and 'Behaviour unit'. Arrows show a top-down flow from the user interface through the analyser and memory to the knowledge base and logic, with a feedback loop from the behaviour unit back to the user interface. A large arrow points from the 'Service gateway' in the left column to the 'User interface' in the right column. A small label 'H.862.6(23)' is in the bottom right corner.
+
+**Figure 2 – Functional model**
+
+### 9.1 User interface
+
+The user interface plays a role in receiving various information inputs such as voice, gesture, video, and sensor information from the user and passing it to the input analyser module. In the user interface, data is collected multimodally according to available input methods.
+
+### 9.2 Input analyser module
+
+A module for analysing user input into data that can be applied for analysis. This module can include the functions shown in Table 3. By analysing the input, it is possible to detect and track changes in the user's current emotional state and behaviour. Functions of the input analyser module are shown in Table 3.
+
+**Table 3 – Functions of the input analyser module**
+
+| Type    | Function                                             |
+|---------|------------------------------------------------------|
+| Voice   | Converting speech to text or extract speech features |
+| Image   | Extracting facial feature points or analysing images |
+| Gesture | Motion tracking or action estimation                 |
+
+### 9.3 Short term memory module
+
+A module for remembering and processing previous interactions with users in order to provide personalized counselling services. In this module, previous conversations and states with the user are memorized, and consultation is performed by reflecting the current input of the user. For example, if you took some medicine yesterday, the counselling chatbot can ask if there is any change in your condition after taking the medicine yesterday.
+
+### 9.4 Interaction analyser module
+
+A module for analysing the user's intention and predicting the action by utilizing the signal recognition transmitted from the user interface through the user's emotion recognition, gesture recognition, text and sensors.
+
+### 9.5 Knowledge base
+
+The knowledge base includes knowledge for performing the functions of a counselling chatbot and artificial intelligence models (LLM, VAQ, etc.). It also manages personal information for personalized services.
+
+### 9.6 Conditional logic module
+
+This counselling chatbot module is configured to respond to the counselee with a module for providing knowledge and an interaction policy, and includes dialog creation and action creation. The interaction policy is intended to improve the user's emotional state according to the user's emotional state. It conducts a conversation according to cognitive behavioural therapy (CBT) methodology. Alternatively, the type of role providing content can be delivered to the behaviour module.
+
+### 9.7 Behaviour module
+
+The behaviour module determines the movement of the avatar of the counselling chatbot and the operation of the mutually operating sensors according to the counselling status. Avatars on the system can provide a rich user experience through words, facial expressions and gestures.
+
+### 9.8 Management interface
+
+The management interface refers to the user interface that manages consultation contents. This includes data visualization that is reported to counsellors or psychiatrists. In the management interface, the counselling performance of the user can be summarized by reflecting the feedback from the counsellor or psychiatrist, who is the user. It is also possible to reflect back to the service.
+
+### 9.9 Real-world data (RWD) repository
+
+The real-world data (RWD) repository refers to a place where logs of mutual interactions between users and counselling chatbots are accumulated. This repository stores the contents of the conversation between the counselee and the counselling chatbot, changes in the user's emotions, and the counselling effect. It can be used to improve the system.
+
+### **9.10 Real-world evidence (RWE) repository**
+
+Data generated in the real-world evidence (RWE) repository is created by feedback from counsellors or psychiatrists. This data is structured and stored so that the counselling results can be utilized. In addition, this data can be used for purposes such as counselling performance management and research.
+
+## Bibliography
+
+- [b-ITU-T H.862.5] Recommendation ITU-T H.862.5 (2021), *Emotion enabled multimodal user interface based on artificial neural networks.*
+- [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                                                                                              |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                                                                                 |
+| 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/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg b/marked/H/T-REC-H.862.8-202503-I_PDF-E/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fc27219db64d5118eb8b4c50d1fd0ab785346ca6
--- /dev/null
+++ b/marked/H/T-REC-H.862.8-202503-I_PDF-E/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c21c5921a63d1ee4671db1db05388d2ae26c9bb50f4960f77556d2ef3b07f537
+size 122022
diff --git a/marked/H/T-REC-H.862.8-202503-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/H/T-REC-H.862.8-202503-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6949f16cb25b8bdb9e4edf5e8ef340ccf10b3711
--- /dev/null
+++ b/marked/H/T-REC-H.862.8-202503-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:01fbcd8209cea2290834790be5f2bc88841569b5aae220d0e93f85d835e3fe17
+size 122162
diff --git a/marked/H/T-REC-H.862.8-202503-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/H/T-REC-H.862.8-202503-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477
--- /dev/null
+++ b/marked/H/T-REC-H.862.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.862.8-202503-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg b/marked/H/T-REC-H.862.8-202503-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8a74ed8b92febe6fb0adf63469f44a42f2081299
--- /dev/null
+++ b/marked/H/T-REC-H.862.8-202503-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae599bb64274b0283d8572da60c563c93e4a2571fc74cea8e47a717664320511
+size 127652
diff --git a/marked/H/T-REC-H.862.8-202503-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/H/T-REC-H.862.8-202503-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ce6af6287aadcf9391095ec0898d92561816a80d
--- /dev/null
+++ b/marked/H/T-REC-H.862.8-202503-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:31c80bdbe08ce469fe3443b2a7e88854cc775b7e8c22ce8ce71784659092e34e
+size 93057
diff --git a/marked/H/T-REC-H.871-201907-I_PDF-E/61ce9760bffbecba8f5e63310be1ebec_img.jpg b/marked/H/T-REC-H.871-201907-I_PDF-E/61ce9760bffbecba8f5e63310be1ebec_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..371fc277106536b825663c70a2f3077c74279b68
--- /dev/null
+++ b/marked/H/T-REC-H.871-201907-I_PDF-E/61ce9760bffbecba8f5e63310be1ebec_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7611f573d4545a24216943ad4aa65f43e542e8527b51c780313fe1976b9ea951
+size 32392
diff --git a/marked/H/T-REC-H.871-201907-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/H/T-REC-H.871-201907-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5295e5f3b359f1cb7eb589492906ba42372ce460
--- /dev/null
+++ b/marked/H/T-REC-H.871-201907-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.871-201907-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/H/T-REC-H.871-201907-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8bb9940c32a88e15f4cd019312147abf128d8f22
--- /dev/null
+++ b/marked/H/T-REC-H.871-201907-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f67ca915b6d5178c7fcab5078000b04272fc7b1ea6464207e94437887252329c
+size 38676
diff --git a/marked/H/T-REC-H.871-201907-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/H/T-REC-H.871-201907-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6adabefaa5bf0a43bbac8f8fc034e90cf3c93383
--- /dev/null
+++ b/marked/H/T-REC-H.871-201907-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ea865f4c961be3361d45b459e45fb08e2268cf605650e1ea0b253e3587aaab0
+size 38263
diff --git a/marked/H/T-REC-H.871-201907-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/H/T-REC-H.871-201907-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..faf1dc1b844aaeb42ad1515c442d7c06d1d63aa9
--- /dev/null
+++ b/marked/H/T-REC-H.871-201907-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4491cafe379f30a9719cf66a88a318d7c7481c23ef2889c18ae847f8b6f9cad7
+size 45988
diff --git a/marked/H/T-REC-H.871-201907-I_PDF-E/f0d1b18586b17005ffd3fce23280b5a5_img.jpg b/marked/H/T-REC-H.871-201907-I_PDF-E/f0d1b18586b17005ffd3fce23280b5a5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9b0f19f600086547bd743b4fb53a2f072bbabb0c
--- /dev/null
+++ b/marked/H/T-REC-H.871-201907-I_PDF-E/f0d1b18586b17005ffd3fce23280b5a5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:29861f9d84cd6fee82f684f11692fc8e8d92df2189e97e995619e88184a8143b
+size 19768